Related
Hello, i do full wipe..then ROM flash regular as normal everyday ROM flash. But now i cant go into boot animation it just stay on Google logo.
i have lates TWRP 2.5.0. I can go into recovery, flash ROM, i can do anything in recovery without error message. I can do full wipe system, cache, dalvik,data then flash ROM but no matter what ROM i flash it just does not boot
i try restore backup, wipe all, fix permissions, flash other ROM, flash stock 422rooted with bussibox from bixie but nothing helps. I flashing on USB key mouned on OTG cable.
Im waiting 5-10min. then pull battery. I dont know what to do more to get it working
please help
EDIT: restoring data give me message "cant mount /data" but after reboot i can mount
EDIT2: after flashing regular ROM /system is empty.. its normal? im using TWRP file manager
Flash stock factory images through fastboot, then start over. Try another recovery version (like twrp 2.4.4.0 or cwm), even though I haven't experienced any issues.
Sent from my Galaxy Nexus using Tapatalk 4 Beta
beekay201 said:
Flash stock factory images through fastboot, then start over. Try another recovery version (like twrp 2.4.4.0 or cwm), even though I haven't experienced any issues.
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
easyst way is thrue GNEX toolkit right? any mirror? goo.im have problems and i cant download it
EDIT:after ROM install it say Updating partition details...
E: Unable to mount " /data
Have you successfully installed Factoty Images like beekay201 suggested? It seems like you haven't. Please do thst and verify the phone is working well before flashing anything else.
You can do it with toolkit, or witb fastboot commands manually it doesn't matter.
My Gnexi said:
Have you successfully installed Factoty Images like beekay201 suggested? It seems like you haven't. Please do thst and verify the phone is working well before flashing anything else.
You can do it with toolkit, or witb fastboot commands manually it doesn't matter.
Click to expand...
Click to collapse
still preparing for it downloading requred files in tookit...
its weird becouse i can install ROM without any FAILED message. but if i restore some backup it say FAILED when restoring data..
ok looks like it booting. Hope nothing more will screw up. THANKS for all you help guys ill ask more if something gues wrong.
:good:
castaway1 said:
ill ask more if something gues wrong.
:good:
Click to expand...
Click to collapse
Please don't. I'm sure your future problems have already been discussed and solved. Please search before posting.
U.O.E.N.O
Hey I've been a long time lurker just haven't posted in forums because I haven't made enough posts Lol.
Well my question is in regards to paranoid android 4.3/3.94.
I've seen lots of people with same issue I havent figured out a fix.
Every 4.3 ROM I flash works fine, until reboot then I get stuck at Google screen. Can't backup or restore. Can't even reflash a 4.2.2. I HAVE to do a full wipe SD card and all, then use adB to sideload a rom.. I've flashed the newest primeD04 boot loader or whatever it is. Still the exact same issue.
I have twrp 4.2.2 I believe , maybe 4.2.0. If that helps..
Please help me I need to be on 4.3 .. And have had to do a full wipe more than 5 times Lol...
antwong45157 said:
Hey I've been a long time lurker just haven't posted in forums because I haven't made enough posts Lol.
Well my question is in regards to paranoid android 4.3/3.94.
I've seen lots of people with same issue I havent figured out a fix.
Every 4.3 ROM I flash works fine, until reboot then I get stuck at Google screen. Can't backup or restore. Can't even reflash a 4.2.2. I HAVE to do a full wipe SD card and all, then use adB to sideload a rom.. I've flashed the newest primeD04 boot loader or whatever it is. Still the exact same issue.
I have twrp 4.2.2 I believe , maybe 4.2.0. If that helps..
Please help me I need to be on 4.3 .. And have had to do a full wipe more than 5 times Lol...
Click to expand...
Click to collapse
sooo you are on latest bootloader latest radio , allways full wipe and it still does that? try doing a full wipe from CWM recovery and flash it again, btw are you on maguro verizon or sprint?
Woodyy said:
sooo you are on latest bootloader latest radio , allways full wipe and it still does that? try doing a full wipe from CWM recovery and flash it again, btw are you on maguro verizon or sprint?
Click to expand...
Click to collapse
I'm on toro. Verizon galaxy nexus.
Well to flash a 4.3 ROM.. I went into TWRP.. team in recovery program. Click factory reset, wipe system, cache and davlik.
Then flash 4.3 ROM, gapps and reboot.
After everything loads I try to reboot and I get stuck at Google screen... I have yet to wipe EVERYTHING because I just figured out how to use adb to side load zips.
Gonna try FULL WIPE SD card and everything then flash 4.3 using adb.
I'm on newest boot loader with fk01 and fk02 radios... Are those newest radios ?
antwong45157 said:
I'm on toro. Verizon galaxy nexus.
Well to flash a 4.3 ROM.. I went into TWRP.. team in recovery program. Click factory reset, wipe system, cache and davlik.
Then flash 4.3 ROM, gapps and reboot.
After everything loads I try to reboot and I get stuck at Google screen... I have yet to wipe EVERYTHING because I just figured out how to use adb to side load zips.
Gonna try FULL WIPE SD card and everything then flash 4.3 using adb.
I'm on newest boot loader with fk01 and fk02 radios... Are those newest radios ?
Click to expand...
Click to collapse
Yep those are the latest radios for verizon, i am on maguro, no problems here... but it seams that there are lots of problems on verizon with 4.3 roms.
---------- Post added at 09:33 PM ---------- Previous post was at 09:25 PM ----------
antwong45157 said:
I'm on toro. Verizon galaxy nexus.
Well to flash a 4.3 ROM.. I went into TWRP.. team in recovery program. Click factory reset, wipe system, cache and davlik.
Then flash 4.3 ROM, gapps and reboot.
After everything loads I try to reboot and I get stuck at Google screen... I have yet to wipe EVERYTHING because I just figured out how to use adb to side load zips.
Gonna try FULL WIPE SD card and everything then flash 4.3 using adb.
I'm on newest boot loader with fk01 and fk02 radios... Are those newest radios ?
Click to expand...
Click to collapse
Try to use latest CWM recovery and then full wipe from recovery, reinstall latest flashable bootloader, reboot in recovery again and flash again PA 3.94 and gaps without ADB sideload
Woodyy said:
sooo you are on latest bootloader latest radio , allways full wipe and it still does that? try doing a full wipe from CWM recovery and flash it again, btw are you on maguro verizon or sprint?
Click to expand...
Click to collapse
Woodyy said:
Yep those are the latest radios for verizon, i am on maguro, no problems here... but it seams that there are lots of problems on verizon with 4.3 roms.
---------- Post added at 09:33 PM ---------- Previous post was at 09:25 PM ----------
Try to use latest CWM recovery and then full wipe from recovery, reinstall latest flashable bootloader, reboot in recovery again and flash again PA 3.94 and gaps without ADB sideload
Click to expand...
Click to collapse
Going to try to side load first with twrp. If all else fails gonna try cwm recovery
Tried to side load with adb... No luck. Worked flawlessly until I rebooted then stuck on the Google screen. Please help!
*
*
*
antwong45157 said:
Tried to side load with adb... No luck. Worked flawlessly until I rebooted then stuck on the Google screen. Please help!
*
*
*
Click to expand...
Click to collapse
Ok, i want some info cuz i am allso confused).
1. what rom do you flash with adb sideload PA 3.94?
2. you said you cant flash 4.2.2 anymore?
3. if you use adb sideload you have the android sdk installed
4. if second and third point are true then use adb to wipe everything from the phone and download stock 4.2.2 img and flash from windows adb command prompt.
Woodyy said:
Ok, i want some info cuz i am allso confused).
1. what rom do you flash with adb sideload PA 3.94?
2. you said you cant flash 4.2.2 anymore?
3. if you use adb sideload you have the android sdk installed
4. if second and third point are true then use adb to wipe everything from the phone and download stock 4.2.2 img and flash from windows adb command prompt.
Click to expand...
Click to collapse
I tried flashing paranoid android 3.94 which is android 4.3 with adb. Hoping it would work different . Nope same result.
I am able to get back on 4.2.2 using adb. I'm on 4.2.2 typing this message . I just need to find out why I can't get on 4.3 with getting stuck at boot screen
This is probably a silly question , but is your bootloader locked I have the gnex toro and it can get testy at times also try flashing this ROM its what I'm currently on and it works great no issues its stock rooted 4.3 follow the steps in the post
http://rootzwiki.com/topic/36706-ro...stock-android-43-jwr66v-no-bugs/#entry1031982
Sent from my Nexus 7 using xda app-developers app
Jewveeski said:
This is probably a silly question , but is your bootloader locked I have the gnex toro and it can get testy at times also try flashing this ROM its what I'm currently on and it works great no issues its stock rooted 4.3 follow the steps in the post
http://rootzwiki.com/topic/36706-ro...stock-android-43-jwr66v-no-bugs/#entry1031982
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I believe my boot loader is unlocked. When. I reboot I see he unlocked lock. But I did flash the new boot loader so maybe I would have to re unlock it? I will try the ROM you posted
Seems like a lot of the time people who are having this stuck at Google screen issue have flashed the new boot loader. Or am I just imagining things?
toro, toro!
itslels said:
Seems like a lot of the time people who are having this stuck at Google screen issue have flashed the new boot loader. Or am I just imagining things?
toro, toro!
Click to expand...
Click to collapse
I had the issue when I tried to go directly from 4.2.2 to a 4.3 custom. The only thing that cleared it up was flashing stock 4.3 from google. After that, no more problems.
Hmm wonder what could be causing it. I did have this issue going from 4.2.2 to 4.3. Every 4.3 ROM I have flashed has booted.
toro, toro!
I solved my problem after reflashing the new boot loader and a new ROM reboot. Then power off. Battery pull then I wiped cache. I'm not sure exactly what the issue was but now I can load up any 4.3 ROM without a problem )
antwong45157 said:
I solved my problem after reflashing the new boot loader and a new ROM reboot. Then power off. Battery pull then I wiped cache. I'm not sure exactly what the issue was but now I can load up any 4.3 ROM without a problem )
Click to expand...
Click to collapse
i have the same fuking problem , what did you do ?
antwong45157 said:
I solved my problem after reflashing the new boot loader and a new ROM reboot. Then power off. Battery pull then I wiped cache. I'm not sure exactly what the issue was but now I can load up any 4.3 ROM without a problem )
Click to expand...
Click to collapse
Gz dude enjoy 4.3
antwong45157 said:
I solved my problem after reflashing the new boot loader and a new ROM reboot. Then power off. Battery pull then I wiped cache. I'm not sure exactly what the issue was but now I can load up any 4.3 ROM without a problem )
Click to expand...
Click to collapse
Thanks, I followed this and finally managed to get to 4.3
http://forum.xda-developers.com/showthread.php?t=2389721
Oh no... I installed PA 3.94 yesterday and everything seemed great. I didn't have any issues booting the first time (although it took a while), but now I'm afraid to reboot my phone in case it gets stuck at the boot screen like you guys are describing.
EDIT: I did a reboot when I got home and it booted up fine, although I felt like it took longer than on previous versions.
oynoy said:
Oh no... I installed PA 3.94 yesterday and everything seemed great. I didn't have any issues booting the first time (although it took a while), but now I'm afraid to reboot my phone in case it gets stuck at the boot screen like you guys are describing.
Click to expand...
Click to collapse
Gotta be able to reboot your phone brother lol. Give it a shot. If it locks up there is always a way to fix the issue... Good luck. Best wishes
FIX for issue getting stuck on google screen after 4.3 reboot
I don't know if anyone has posted this elsewhere. I had the same problem yesterday - after a lot of playing around this is how I fixed it:
***Note1: you need adb and fastboot.
***Note2: make external backup of things (i.e. photos) you want to keep using adb.
Procedure:
1. Download 4.2.2 image from google (can't post link because of spam prevention rules - you can search for "google developers nexus images")
2. extract files to location of choice
3. Download latest custom recovery image of your choice. I prefer TWRP (latest 2.6)
3. reboot to recovery, do a full factory reset (wipe everything, you will lose all your storage).
4. Reboot to bootloader (from phone off, power plus volume rocker).
5. flash stock image via fastboot (change names and paths acordingly):
Code:
fastboot devices (make sure fastboot can see your device)
adb reboot bootloader
fastboot flash bootloader bootloader-toro-<current_ver>.img
fastboot reboot-bootloader
fastboot flash radio /path/to/radio-toro-<current_ver>.img
fastboot reboot-bootloader
fastboot flash radio-cdma /path/to/radio-cdma-toro-<current_ver>.img
fastboot reboot-bootloader
fastboot -w update /path/to/image-mysid-<version>.zip
5. After this last step, the phone should reboot.
6. Go through the phone setup process.
7. power off, and boot to bootloader
8. flash custom recovery:
Code:
fastboot flash recovery /path/to/custom-recovery.img
9 reboot to recovery. TWRP will ask you if you want to root when you reboot to system.
10. Phone rooted and like new!
I think that is all - you can flash your ROM of choice after this!
I've seen this problem mentioned in a few threads but not seen any definitive fix.
My current install :
Stock NPD35K system, vendor, bootloader
Xceede's v8.01 kernel
TWRP 3.02 v6.0
Encrypted data partition
I currently get bootloops every time I boot into TWRP. After using TWRP and attempting to reboot it will then bootloop into recovery refusing to boot the system.
I have found it can be fixed by rebooting into fastboot and the "fastboot reboot" command. But this is frustrating if I don't have a laptop handy.
This happens every time I need to boot into recovery to install or update via TWRP. Is anyone else getting the same bootloops and has anyone found a permanent fix?
Thanks guys.
Sent from my Nexus 6P using Tapatalk
Hi Jake,
I had exactly the same issue since NPD35K except the fastboot reboot solution did not work for me.
What i could find was that if you flash the default vendor, recovery and cache partition via fastboot and then put off the tablet, it should after all of this boot correctly to the system.
Cheers,
Mathieu
You are not alone ..
I had the recovery bootloop once myself.
I did the "fastboot reboot" command and since then the Pixel C is booting fine again.
Did several installations afterwards .. no problems anymore.
Just once ..
But if you get it every reboot this a real problem.
Right now I am not able to help you .. just don't know the root cause and how to fix it.
As it looks like, it helps if you go back to stock recovery, like mentioned above.
I can not confirm this .. as I don't have the problem.
Good luck !
Thanks for the advice guys.
As I said it only bootloops immediately after boating into TWRP (even if I don't install anything), if I reboot from system it's fine.
At the moment I prefer to keep TWRP installed and reboot from fastboot if I need to use TWRP. I don't see an advantage to installing the stock recovery. It would be great to pinpoint what's causing this though.
Sent from my Pixel C using Tapatalk
I'm still getting this TWRP bootloop. I've tried several versions - 3.0.0, 3.0.21, 3.0.23. I've tried numerous times re-flashing stock using NRT and then flashing the recovery again. I've also tried fastboot-reboot.
I'm on stock 7.1.1 - NMF26H. If i need to install a different version for this to work I can do that.
Is there perhaps some particular version of TWRP that everyone but me is using? Or are there some specific versions of other files that I also need to flash along with TWRP? From what I've read if I get past this once that's probably it.
Thanks
badwiring said:
I'm still getting this TWRP bootloop. I've tried several versions - 3.0.0, 3.0.21, 3.0.23. I've tried numerous times re-flashing stock using NRT and then flashing the recovery again. I've also tried fastboot-reboot.
I'm on stock 7.1.1 - NMF26H. If i need to install a different version for this to work I can do that.
Is there perhaps some particular version of TWRP that everyone but me is using? Or are there some specific versions of other files that I also need to flash along with TWRP? From what I've read if I get past this once that's probably it.
Thanks
Click to expand...
Click to collapse
Pls install latest bootloader and latest factory image via fastboot, manually.
Pls use latest fastboot binaries from Google.
Pls install 3.0.2-23 via fastboot as well.
Reboot directly into TWRP and not into system in between.
Install SuperSu.zip v2.79 in TWRP.
Reboot into system.
The first time the system will boot twice .. it's normal.
followmsi said:
Pls install latest bootloader and latest factory image via fastboot, manually.
Pls use latest fastboot binaries from Google.
Pls install 3.0.2-23 via fastboot as well..
Click to expand...
Click to collapse
Thank you. I'll try this today. If I use s tool like NRT to flash "stock" to the device, does that cover what's described in the first step - latest bootloader and latest factory image - or is there something else I need to flash at that step?
Thanks
badwiring said:
Thank you. I'll try this today. If I use s tool like NRT to flash "stock" to the device, does that cover what's described in the first step - latest bootloader and latest factory image - or is there something else I need to flash at that step?
Thanks
Click to expand...
Click to collapse
Maybe your problem is related to the tool itself
For this reason I recommend to use the official google fastboot tool for complete flashing of factory image including bootloader.
To have a proper base to continue ..
Good luck !
EDIT: .. no need to wipe data here. Just a fresh system, vendor, cache and boot image from factory image.
followmsi said:
Maybe your problem is related to the tool itself
For this reason I recommend to use the official google fastboot tool for complete flashing of factory image including bootloader.
To have a proper base to continue ..
Good luck !
Click to expand...
Click to collapse
I think that answers my question - the original factory image including the bootloader.
I'll try it in a few hours. Thank you very much!
That worked! I was currently on stock 7.1.1 so I tried it first without re-flashing, although I was prepared to go back to that step if it didn't work.
First I downloaded SuperSU 2.79 and copied the ZIP to my device.
I used Minimal ADB and Fastboot (which I think is taken from the official Google source) and flashed recovery-twrp-3.0.2.23.followmsi-ryu.img.
Then I rebooted into recovery - not system - and flashed SuperSU.
Finally I rebooted into system.
The Google logo appeared for a moment and then it booted again (exactly as you said.) Then it booted normally.
Finally! Thank you very much! Hopefully this will help someone else too. It can be the smallest detail we miss that makes the difference.
badwiring said:
That worked! I was currently on stock 7.1.1 so I tried it first without re-flashing, although I was prepared to go back to that step if it didn't work.
First I downloaded SuperSU 2.79 and copied the ZIP to my device.
I used Minimal ADB and Fastboot (which I think is taken from the official Google source) and flashed recovery-twrp-3.0.2.23.followmsi-ryu.img.
Then I rebooted into recovery - not system - and flashed SuperSU.
Finally I rebooted into system.
The Google logo appeared for a moment and then it booted again (exactly as you said.) Then it booted normally.
Finally! Thank you very much! Hopefully this will help someone else too. It can be the smallest detail we miss that makes the difference.
Click to expand...
Click to collapse
You are welcome ..
``
tried numerous times to flash TWRP to my Pixel C 8.0.0 (OPR1.170623.032, Nov 2017) every time with bootloop in to recovery...
most recently hoping twrp-3.2.0-0-dragon would work
---------- Post added at 07:44 PM ---------- Previous post was at 07:29 PM ----------
tried to reflash ryu-opr1.170623.032-factory-020f1cf9's boot.img and it still bootlooped.
Tried to flash the recovery and now its bootlooping into stock recovery. Any ideas?
for a stock google device, this things a nightmare to work with compared to my nexus devices
So as the title says, after flashing cm14. 1 can't go into recovery anymore, it just a black screen. I tried to use flashify but nothing, a couple of apps show that I have twrp 3.0.2.1 but can't get into it... Help?
Cheers
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Which thread is this from please?
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Yeah man im in the same boat, if i get time ill try this twrp recovery. Where did that recovery come from?, it seems like the CM recovery for 14.1 nightly high jacks the recovery partition (i call it that,i dont know the term for it)
Sent from my ONEPLUS A3000 using Tapatalk
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Hw4ng3r said:
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Click to expand...
Click to collapse
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Thanks a lot guys, that did the trick, and done with flashify
JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
@JKMB888 it does work 100% is as simple as flashing the TWRP. Actually, i installed it with CM 14.1 running just fine
Sent from my ONEPLUS A3000 using Tapatalk
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Edit: I found the solution, i had a pattern lock screen and i removed it!
HC4Life said:
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Click to expand...
Click to collapse
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
GrandMasterB said:
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
Click to expand...
Click to collapse
Look at my edited reply...
m4manusraj said:
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Click to expand...
Click to collapse
actually flashify did the trick for me as I had no access to a pc for the time
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
i am facing just the same situation with cm14.1 nightly and can't boot into recovery
i tried flashing the recovery image provided by you i.e. twrp-3.0.2-22-oneplus3.img but i face the same problem again
when i go into the recovery all i see is a black screen with a white notification light on and it remains there untill i switch off my phone manually using the power button
i tried facing the problem when i installed the cm14.1 nightly
i was unable to login snapchat as i device was rooted as said by the message on snapchat
so i decided to unroot my device via supersu FULL UNROOT option
after a reboot i successfully logged into snapchat
then i tried to root it again
i went into recovery to flash the supersu zip
and since then i have been unable to see the twrp recovey
please help me
This thread is a life save. Tried everything and it drove me nuts not getting into recovery.
THANK YOU!
gangangan2 said:
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
Click to expand...
Click to collapse
Thank you so much it's work for me now..
After I got the recovery back, I flashed CM13 again and ARM64 6.0 Nano Gapps for my Oneplus 3, but I'm getting an error after the "preparing apps' screen is loaded saying that - unfortunately the process android.process.media has stopped one plus 3 boot and then the phone switches off.
Any solution to this? I've already tried flashing different versions of CM13.
Thank you!! I was looking for hours.
This link fixed the problem!
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Hey, guys. I'm pretty sure I bricked my phone and there's no way to get out.
So I was on CM13 official builds on my OP3. Then, on the OTA update system they have, I got moved onto the CM14.1. I downloaded from here and went into my twrp recovery to flash. I made a clean flash and then proceeded to go back to system. I thought everything was ok until I realised I hadn't flashed a gapps package which I pretty much need to survive as all my contacts backups etc. are on there. I powered off my phone and went to go back into the recovery after downloading gapps 7.1 micro. It went past the *You're device can not be trusted'* and then went to the oneplus screen. After that, it stayed like that for about 30 secs and powered off. At first, I thought I messed something up and tried again. I repeated that for about 3 times and it didn't work. I tried going into the normal system and coming back to recovery and it didn't work still. In fact, now I can't even get into system. Now, i can only boot up to fastboot, where my computer still doesn't realise my phone is plugged in.
Anyone got any ideas on how to fix this? I wouldn't say I'm a noob at this because I have flashed many times before but I'm relatively new to the scene. I didn't see this thread before i ripped my hair out and i think wrecked my phone @JKMB888
EDIT: I sorted it out with help from Naman Bhalla's unbrick thread and this. A certain combo works and now I'm on CM14.1 enjoying life
**When i will get all of the information needed,i will edit this thread and make it as simple for reaching the objective for everyone,as possible.**
Recently i got an OTA update for my nexus 5x device,a security patch form june 2017.
I`ve rooted it with this tutorial: https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
My question is: In order to install that OTA i need to follow "11. How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact)" section from Heisenberg`s tutorial or this "9. How To Update To A New Build Of The Stock ROM" section of the same tutorial?.On the "9. update the build of a stock rom" it says no data will be wiped yet this statement of google offical site still concerns me : "Warning: Installing this factory image will erase all data from the device. While it may be possible to restore certain data backed up to your Google Account, apps and their associated data will be uninstalled. Before proceeding, please ensure that data you would like to retain is backed up to your Google Account."
So what`s the safest way to OTA update your rooted device?Please provide some explanations.
ionut15 said:
**When i will get all of the information needed,i will edit this thread and make it as simple for reaching the objective for everyone,as possible.**
Recently i got an OTA update for my nexus 5x device,a security patch form june 2017.
I`ve rooted it with this tutorial: https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
My question is: In order to install that OTA i need to follow "11. How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact)" section from Heisenberg`s tutorial or this "9. How To Update To A New Build Of The Stock ROM" section of the same tutorial?.On the "9. update the build of a stock rom" it says no data will be wiped yet this statement of google offical site still concerns me : "Warning: Installing this factory image will erase all data from the device. While it may be possible to restore certain data backed up to your Google Account, apps and their associated data will be uninstalled. Before proceeding, please ensure that data you would like to retain is backed up to your Google Account."
So what`s the safest way to OTA update your rooted device?Please provide some explanations.
Click to expand...
Click to collapse
It is very simple actually. Here's a quick lesson for you to try out. Download any factory image then examine the flash-all.sh script inside the zip. Find the line command that begins with "-w." This command will cause the entire phone to be wiped when the script is executed, as Google highlights.
You can edit and remove the entire -w line to leave your internal storage intact. However, TWRP will be replaced because this script installs each partition including the stock recovery.
I don't believe my guide could be any clearer. Manually entering the commands for each partition, as my guide states, does not wipe the device. With fastboot, the primary ways to wipe the device are: executing the flashall script for a factory image, flash the userdata.img, issue fastboot format userdata, or lock/unlock the bootloader.
Follow my guide to update
Sent from my Nexus 5X using Tapatalk
@SlimSnoopOS thank you,very clear response
ionut15 said:
@SlimSnoopOS thank you,very clear response
Click to expand...
Click to collapse
Also, make sure to flash root and any other mods BEFORE booting up once you update.
My pleasure! That's why this great place exists and I'm always happy to pass on information that I've learned.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Also, make sure to flash root and any other mods BEFORE booting up once you update.
My pleasure! That's why this great place exists and I'm always happy to pass on information that I've learned.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Can i ask what are the cons of not doing so? I would flash the factory img that will lead to replacing custom recovery with the stock one and cancelling my root.After flashing it,i asumme that my phone will boot up,so i need to power it off again and proceed to install recovery and root again via adb.How can i install them before the phone will be booting up?
Sent from my Nexus 5X using Tapatalk
I always followed this guide here: http://elementalx.org/how-to-install-android-monthly-security-updates/
Here's the quick summary:
Download the newest factory update for your device
Extract all files
Update system boot vendor bootloader radio
Flash whatever root and/or kernel you want.
Wipe cache/dalik
Reboot
Worked like a charm, and only took me ~10 or so minutes once I knew what I was doing.
crazyates said:
I always followed this guide here: http://elementalx.org/how-to-install-android-monthly-security-updates/
Here's the quick summary:
Download the newest factory update for your device
Extract all files
Update system boot vendor bootloader radio
Flash whatever root and/or kernel you want.
Wipe cache/dalik
Reboot
Worked like a charm, and only took me ~10 or so minutes once I knew what I was doing.
Click to expand...
Click to collapse
in the tutorial provided by @SlimSnoopOS at point "11" it says to enter these commands in adb cmd "fastboot erase cache
fastboot flash cache C:\bullhead\images\cache.img" but i didn`t get the cache file with the factory.img.So i just skip erasing the cache then flashing it or i have to download from somewhere else?
ionut15 said:
Can i ask what are the cons of not doing so? I would flash the factory img that will lead to replacing custom recovery with the stock one and cancelling my root.After flashing it,i asumme that my phone will boot up,so i need to power it off again and proceed to install recovery and root again via adb.How can i install them before the phone will be booting up?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
It is just a time saving step. If you manually install each partition excluding recovery.img, you can still boot directly into TWRP from bootloader to flash root and now TWRP will persist. This is more relevant on Nougat and newer, this didn't happen on Marshmallow.
Installing a OTA/factory image will always override every partition including TWRP recovery. But if you manually install each image except recovery, upon booting into the phone the stock recovery will replace TWRP. To get root now you will need to: boot into bootloader, flash TWRP, then boot into TWRP to flash your mods afterwards. Make sense?
ionut15 said:
in the tutorial provided by @SlimSnoopOS at point "11" it says to enter these commands in adb cmd "fastboot erase cache
fastboot flash cache C:\bullhead\images\cache.img" but i didn`t get the cache file with the factory.img.So i just skip erasing the cache then flashing it or i have to download from somewhere else?
Click to expand...
Click to collapse
Please do not erase cache. Skip this step when using Nougat and newer. I have to update this part of the guide.
Sent from my Nexus 5X using Tapatalk
ionut15 said:
in the tutorial provided by @SlimSnoopOS at point "11" it says to enter these commands in adb cmd "fastboot erase cache
fastboot flash cache C:\bullhead\images\cache.img" but i didn`t get the cache file with the factory.img.So i just skip erasing the cache then flashing it or i have to download from somewhere else?
Click to expand...
Click to collapse
Cache doesn't matter. In TWRP, if you "wipe cache", it just formats the /cache volume, which is all you'll ever need to do. There should be no need to manually flash anything into the cache volume (it rebuilds itself automatically).
crazyates said:
Cache doesn't matter. In TWRP, if you "wipe cache", it just formats the /cache volume, which is all you'll ever need to do. There should be no need to manually flash anything into the cache volume (it rebuilds itself automatically).
Click to expand...
Click to collapse
Thank you,managed to update the security patch and works just fine.
Sent from my Nexus 5X using Tapatalk
crazyates said:
Cache doesn't matter. In TWRP, if you "wipe cache", it just formats the /cache volume, which is all you'll ever need to do. There should be no need to manually flash anything into the cache volume (it rebuilds itself automatically).
Click to expand...
Click to collapse
Thank you again for your time and devotion.You cleared off all of my doubts.Furthermore i hope someone who's in my situation could find this topic helpful.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
It is just a time saving step. If you manually install each partition excluding recovery.img, you can still boot directly into TWRP from bootloader to flash root and now TWRP will persist. This is more relevant on Nougat and newer, this didn't happen on Marshmallow.
Installing a OTA/factory image will always override every partition including TWRP recovery. But if you manually install each image except recovery, upon booting into the phone the stock recovery will replace TWRP. To get root now you will need to: boot into bootloader, flash TWRP, then boot into TWRP to flash your mods afterwards. Make sense?
Please do not erase cache. Skip this step when using Nougat and newer. I have to update this part of the guide.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thank you again for your time and devotion.You cleared off all of my doubts.Furthermore i hope someone who's in my situation could find this topic helpful.
Sent from my Nexus 5X using Tapatalk
If you want install OTA updates while your device is rooted, use Flashfire.
AFK269 said:
If you want install OTA updates while your device is rooted, use Flashfire.
Click to expand...
Click to collapse
its a straight-forward method,unfortunately my system partition was changed and flashfire can't flash ota.
Sent from my Nexus 5X using Tapatalk
ionut15 said:
its a straight-forward method,unfortunately my system partition was changed and flashfire can't flash ota.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Then flash factory images with adb fastboot commands