OnePlus One Official Thread v8, Coming soon officially
|
|
 Oct 15 2014, 01:43 PM
Return to original view | Post
#1
|
 
Senior Member
1,719 posts Joined: Jan 2011 
|
QUOTE(ConTechMi @ Oct 15 2014, 12:22 PM) finally got OTA to 38~ no bootloop or any problems?yes i haven't root and battery performance increased~! yay~  I have yet to root as well,. |
|
|
|
|
|
Oct 17 2014, 04:47 PM
Return to original view | Post
#2
|
|
Senior Member
1,719 posts Joined: Jan 2011
|
Hi, would like to ask if anyone with unrooted / unlocked opo facing bootloop after updating? Seeing most people here with bootloop problem are mostly rooted.
Don't dare to update, not willing to go through the process of flashing |
|
|
Oct 18 2014, 12:22 AM
Return to original view | Post
#3
|
|
Senior Member
1,719 posts Joined: Jan 2011
|
QUOTE(ntkiwi5465 @ Oct 17 2014, 06:55 PM) I was the one who got it bricked and bootloops, unrooted and locked. update via OTA. crap. I hate the process of reading and understanding it and proceed to flash this and that.My suggest is back up everything and root that effin' OPO and install custom recovery and root it. Don't ask why, just do it. Good Luck  Too much hassle for me No other way to go about it? |
|
|
Oct 18 2014, 04:19 PM
Return to original view | Post
#4
|
|
Senior Member
1,719 posts Joined: Jan 2011
|
Dear sifus,
After long reads on unlocking and flashing, i've gained several refreshment on the steps. (Stopped rooting and flashing since M7). Only reason why i'm reminding myself is to be prepared for bootloops in future updates. The current 38r have put many in difficulties. Assuming that there will be more updates, i would still have to go through 38r to other updates. I've downloaded oneplus one toolkit to go about the easy way, however, before i decide to lay a foot on it, i do hope that my question can be answered. My device is china version, with cm11s. meaning that directd must have loaded it themselves. Can't differentiate if my bootloader is unlocked or re-locked. (bootloader) Device tampered: true (bootloader) Device unlocked: false (bootloader) Charger screen enabled: false Should I update to 38R if I can get rid of the bootloop issue, or is the current 33r Better in comparison? Should I wait for the next update, which none of us would know how long it would be up? Thanks! |
|
|
Oct 18 2014, 05:19 PM
Return to original view | Post
#5
|
|
Senior Member
1,719 posts Joined: Jan 2011
|
QUOTE(stella_purple @ Oct 18 2014, 05:08 PM) it would be better if you can learn to use the adb and fastboot yourself rather than rely on toolkit since you can know and understand what have been done to your opo. So in another words, you have no issue with updated 38R? Mind if you share whether yours is unlocked with custom recovery? Is this a random bug that affects certain people only?your device bootloader currently is lock, but it have been unlocked before since the device tampered is true. mayb they unlock it to flash cm11s and later relock back. about bootlooping issue in 38r, so far i never experience it and for me 38r is a improvement compared to 33r, especially the power consuming in idle mode. The adb only allows to unlock and flash custom recovery with an option to do the reverse. For custom rom, it would still require manual adb push and flash. QUOTE(Haters_Gonna_H8 @ Oct 18 2014, 05:09 PM) your bootloader is locked. if you unlock, you will lose all of your data, hence, use backup apps such as Titanium Backup, once the backup is done, transfer all the backup files into your pc. then only proceed to unlock bootloader and root oh, i've always thought that titianium backup may work on rooted device only. thanks for the headups! |
|
|
Oct 18 2014, 05:55 PM
Return to original view | Post
#6
|
|
Senior Member
1,719 posts Joined: Jan 2011
|
QUOTE(stella_purple @ Oct 18 2014, 05:33 PM) ya for me 38r no issue at all. mine is unlocked + official twrp + root. about the bootloop issue, i am not sure about it. QUOTE(Haters_Gonna_H8 @ Oct 18 2014, 05:38 PM) it works but on limited functionality. Thanks! on the bootloop, i did state it before in here, it happens randomly, due to some bug on an unused location within the device. dont want to dwell into the technicality of it, but here's the fix, just apply it once you have twrp. dont wait until the bootloop happens enter twrp recovery select advanced select terminal command press the Select button on the bottom right of the screen type this command: make_ext4fs /dev/block/mmcblk0p15 then reboot your device so the command should be done on twrp through the phone not adb, is that correct? just to confirm, Backup -> backup to desktop -> unlock bootloader -> reboot -> flash twrp -> push command -> reboot and update to 38R. Is that correct? |
|
|
Oct 19 2014, 12:17 AM
Return to original view | Post
#7
|
|
Senior Member
1,719 posts Joined: Jan 2011
|
QUOTE(BenSow @ Oct 18 2014, 11:32 PM) Garage sales Have yet to try s5 earphones, but xiaomi 2.1 is very impressive.Guys, Xiaomi Piston 2.1 or Samsung S5 stock earphones or wait for silver bullet? :3 |
|
Topic ClosedOptions
|
| Change to: |  0.0513sec
 1.08
 7 queries
 GZIP Disabled
Time is now: 23rd December 2025 - 01:43 PM |
Quote