Related
Hey,
Im on nexus i9023 with NSCollab rom and netarchy
Today i decided i wanted to try Cyanogen mod and downloaded it throug rommanager, al good up until that point!
Download was complete and i selected to contineu with the rom, it asked me if i wanted to backup my current rom and wipe cache/dalvik wich i said yes to!
Then it shutdown and stayed on the Google logo with the unlocked lock , i left it hanging to see what would happen but it just remained like it was stuck, so i decided to pull the battery and fired up again, all seems back to normal still running NSCollab!
But i cant get into Clockwork recovery anymore, it always shows the Google logo as said before, as we all need CWR, can you guys tell me what to do or what is going on?
Thnx!
If you can't get into CWR through the bootloader, just flash it again using fastboot like you did the first time.
deejaylobo said:
If you can't get into CWR through the bootloader, just flash it again using fastboot like you did the first time.
Click to expand...
Click to collapse
or just flash the recovery in rom manager again
bringonblink said:
or just flash the recovery in rom manager again
Click to expand...
Click to collapse
did this, didnt help, still stuck on logo!
ROM Manager has never worked right for me when I try updating CWR.
Can you explain exactly what happens when you try to get into recovery from the bootloader? Your phone reboots and is stuck on the Google logo? Or do you get a message along the lines of "no recovery img"? or what?
deejaylobo said:
ROM Manager has never worked right for me when I try updating CWR.
Can you explain exactly what happens when you try to get into recovery from the bootloader? Your phone reboots and is stuck on the Google logo? Or do you get a message along the lines of "no recovery img"? or what?
Click to expand...
Click to collapse
Yeah stuck on google logo without message!
I reflashed the recovery image through command, like when first setting up CWR, and it worked, i have recovery back!
Thnx!
After unboxing my Nexus 5, here's what I did:
1. Booted into bootloader
2. fastboot oem unlock
3. Flashed TWRP v2.6.3.0
4. Booted to recovery
The screen that greeted me says "Please Enter Your Password".
I can hit the cancel button below this which takes me to the normal TWRP screen. I then pushed SuperSU to /sdcard, but when I flash it it fails because it's unable to mount /cache or storage.
When I reboot to the system, it takes an awfully long time (approximately 30s) to progress past the "Google" screen, and then it just seems to sit on the booting animation forever.
Any help?
EDIT: Solved my own problem.
Hit cancel at the password screen, then go into Wipe and then do a factory reset by swiping. Then go back into Wipe and press the 'Format data' button. You have to type 'Yes', and it will take a few seconds. After that everything should work normally.
You forgot to reboot after OEM unlock
Sent from my Nexus 7 using Tapatalk
mattrb said:
You forgot to reboot after OEM unlock
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Ah, that might explain it. So after you do an OEM unlock, you need to reboot back into the bootloader? Or reboot into the system? And then you flash recovery?
Niksko said:
After unboxing my Nexus 5, here's what I did:
1. Booted into bootloader
2. fastboot oem unlock
3. Flashed TWRP v2.6.3.0
4. Booted to recovery
The screen that greeted me says "Please Enter Your Password".
I can hit the cancel button below this which takes me to the normal TWRP screen. I then pushed SuperSU to /sdcard, but when I flash it it fails because it's unable to mount /cache or storage.
When I reboot to the system, it takes an awfully long time (approximately 30s) to progress past the "Google" screen, and then it just seems to sit on the booting animation forever.
Any help?
EDIT: Solved my own problem.
Hit cancel at the password screen, then go into Wipe and then do a factory reset by swiping. Then go back into Wipe and press the 'Format data' button. You have to type 'Yes', and it will take a few seconds. After that everything should work normally.
Click to expand...
Click to collapse
Thanks so so much for your informative edit. I had the exact same issue, solved it perfectly for me. Cheers
Haha at least i wasn't the only one to do this! I guess you need to boot up the device after a oem unlock before you try to flash the recovery... who knew haha
Thanks for the solution!
Now, i have a issue, i did this also and i didn't reboot. My phone seems to be stuck in a boot loop. Should i go threw the motions of flashing a ruu to it?
super-6-1 said:
Now, i have a issue, i did this also and i didn't reboot. My phone seems to be stuck in a boot loop. Should i go threw the motions of flashing a ruu to it?
Click to expand...
Click to collapse
If you don't have anything on the phone. Just flash the factory image, and everything will be good as new.
joshyth said:
If you don't have anything on the phone. Just flash the factory image, and everything will be good as new.
Click to expand...
Click to collapse
awesome doing that now.
mattrb said:
You forgot to reboot after OEM unlock
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Did this after unlocking my new n7 2013. found this solution, worked like a charm! thanks!
I have this error..but i can't wipe "E:Unable to mount storage."
Polv89 said:
I have this error..but i can't wipe "E:Unable to mount storage."
Click to expand...
Click to collapse
Same error here. Did you solved it?
Uwe303 said:
Same error here. Did you solved it?
Click to expand...
Click to collapse
I have this error..too
"E:Unable to mount storage."
any idea ?
-------------------
EDIT : I flashed twrp-2.6.3.4 and then everything was fine
Uwe303 said:
Same error here. Did you solved it?
Click to expand...
Click to collapse
Matrix_19 said:
I have this error..too
"E:Unable to mount storage."
any idea ?
-------------------
EDIT : I flashed twrp-2.6.3.4 and then everything was fine
Click to expand...
Click to collapse
Were you guys flashing or restoring?
I've came across this too, all i did was manually mount/unmount storage as well as system.
But updating recoveries is always best
same prblm
i have the same prblm here on my xperia z but when i do the factory reset by swiping it gave "failed" again ,what can i do !could anyone help me plz!
hssn a said:
i have the same prblm here on my xperia z but when i do the factory reset by swiping it gave "failed" again ,what can i do !could anyone help me plz!
Click to expand...
Click to collapse
You should discuss your issue in the Xperia Z sections.
This happened to me, and caused me a real rough time flashing anything. I bought the phone used, and since I've never used the function, I didn't know what was happening. The previous owner encrypted it. Really messed me up. After I realized it, I managed to wipe everything and restore stock 4.4.2.
Sent from my cell phone telephone....
---------- Post added at 12:27 PM ---------- Previous post was at 12:26 PM ----------
Might not be the same issue for you...but it sure sounds similar.
Sent from my cell phone telephone....
:cyclops: thx genius !! just trying to ask here because many ppl have the same prblm , and this isnt about "sony"
Matrix_19 said:
I have this error..too
"E:Unable to mount storage."
any idea ?
-------------------
EDIT : I flashed twrp-2.6.3.4 and then everything was fine
Click to expand...
Click to collapse
Happened to me a few times...I just kept rebooting to recovery until it mounted.
Niksko said:
EDIT: Solved my own problem.
Hit cancel at the password screen, then go into Wipe and then do a factory reset by swiping. Then go back into Wipe and press the 'Format data' button. You have to type 'Yes', and it will take a few seconds. After that everything should work normally.
Click to expand...
Click to collapse
Many thanks from me too!
I've got the described problem by attempting to install a KK ROM on my Xoom. After the TWRP update I also got this "Enter password" dialogue.
Your solution helped very much.
I had the same problem. all you need to do is to set your screen lock to none.(go to settings, security, screen lock, and then select none)
Really hope someone can help me on this. I clicked on update and now it shows 12.0-YNG1TAS17L
And when I boot the phone into recovery, it goes to a new screen of Cyanogen Recovery, it is totally different than TWRP that I have in on my phone.
I already make sure the phone "update Cyanogen Recovery" is unchecked. But no matter now many times I reboot, reset the phone. It goes to that new recovery screen.
Now I can't root my phone at all. I tried android-sdk-windows.....etc. It will not work.
Tried install it from recovery, it saids install failed.
IS there a way I can use TWRP instead?
Thanks
benzso63 said:
I already make sure the phone "update Cyanogen Recovery" is unchecked.
Click to expand...
Click to collapse
Well, you should have checked that BEFORE the update, not after.
benzso63 said:
IS there a way I can use TWRP instead?
Click to expand...
Click to collapse
Yes, there are many ways. Check custom recovery installation.
benzso63 said:
Really hope someone can help me on this. I clicked on update and now it shows 12.0-YNG1TAS17L
And when I boot the phone into recovery, it goes to a new screen of Cyanogen Recovery, it is totally different than TWRP that I have in on my phone.
I already make sure the phone "update Cyanogen Recovery" is unchecked. But no matter now many times I reboot, reset the phone. It goes to that new recovery screen.
Now I can't root my phone at all. I tried android-sdk-windows.....etc. It will not work.
Tried install it from recovery, it saids install failed.
IS there a way I can use TWRP instead?
Thanks
Click to expand...
Click to collapse
Use fastboot or a toolkit to reinstall TWRP, after it installs reboot back into TWRP, dont reboot the whole system and TWRP will stick. Otherwise TWRP will be overwritten with the stock recovery.
benzso63 said:
Really hope someone can help me on this. I clicked on update and now it shows 12.0-YNG1TAS17L
And when I boot the phone into recovery, it goes to a new screen of Cyanogen Recovery, it is totally different than TWRP that I have in on my phone.
I already make sure the phone "update Cyanogen Recovery" is unchecked. But no matter now many times I reboot, reset the phone. It goes to that new recovery screen.
Now I can't root my phone at all. I tried android-sdk-windows.....etc. It will not work.
Tried install it from recovery, it saids install failed.
IS there a way I can use TWRP instead?
Thanks
Click to expand...
Click to collapse
Read the FAQ:
http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
XDA Moderator
Transmitted via Bacon
Bro, I followed this instructions. Did everything I could but still boot up with stock recovery. It is stuck. I don't know what to do .
As you can see the screen shot when I tried push the superSu to it, it saids error: device not found.
All previous steps I followed without error.
But end up still showing stock recovery.
Heisenberg said:
Read the FAQ:
http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
XDA Moderator
Transmitted via Bacon
Click to expand...
Click to collapse
I did but it saids device not found.
gsmyth said:
Use fastboot or a toolkit to reinstall TWRP, after it installs reboot back into TWRP, dont reboot the whole system and TWRP will stick. Otherwise TWRP will be overwritten with the stock recovery.
Click to expand...
Click to collapse
benzso63 said:
Bro, I followed this instructions. Did everything I could but still boot up with stock recovery. It is stuck. I don't know what to do .
As you can see the screen shot when I tried push the superSu to it, it saids error: device not found.
All previous steps I followed without error.
But end up still showing stock recovery.
Click to expand...
Click to collapse
You haven't followed the instructions there, from what I can see you've issued the "fastboot reboot" command after flashing the recovery, which you're not meant to do, you're meant to force a reboot directly into recovery with the power + volume down combo.
Hi Heisenberg, I got the problem solved by using the toolkit. Now I got my TWRP back and rooted. Thanks for the info.
Heisenberg said:
You haven't followed the instructions there, from what I can see you've issued the "fastboot reboot" command after flashing the recovery, which you're not meant to do, you're meant to force a reboot directly into recovery with the power + volume down combo.
Click to expand...
Click to collapse
Hi.
Last year I tried to root my Honor 8... i failed. I've managed to unlock it but i did not root it (idk why, i just followed a tutorial but nothing happens as it should).
My phone was JUST unlocked. Not rooted. I just had this beautiful message when I boot it "Your device has been unlocked and can't be trusted. Visit blablabla......."
So I wanted to recover it... but i couldn't, using android or the huawei recovery thing.
So I decided to follow some tutorials (big mistake, i know nothing about this world). I tried to flash the stock rom...
I downloaded "Huawei Multi Tool by MT" and I "flashed stock eRecovery images from an online database" (choosing a randon version)
It worked but now, I have this message "Type password to decrypt storage" every time I boot my phone. I already tried to take out my SD card, to reset factory from the recovery (did it many times)... nothing works.
I can try every password, it says that "the password is correct but data is corrupt so you have to reset" ......................
im afraid of losing my phone right now
I had FRD-L09C432B394
Android Nougat
EMUI 5.1
If you could please help me or send me a link, because i tried several tutorials but ... none correspond to my situation, my version etc.
Thanks !!
Best thing I can think of to do off the top of my head is flash twrp and flash magisk. Then install titanium backup to backup all your apps. It is going to require you to read and learn a bit, but not doing so is what put you in this spot to begin with.
Ok but... How? I think I can't access to bootloader. I can only access to this HUAWEI recovery thing if i press power for a long a time, and if i don't, it asks the password..
Something to do with my pc with USB connected?
btw i dont need to "backup my apps"... i dont mind if i lose all my data. i want it.
hyc72 said:
Ok but... How? I think I can't access to bootloader. I can only access to this HUAWEI recovery thing if i press power for a long a time, and if i don't, it asks the password..
Something to do with my pc with USB connected?
btw i dont need to "backup my apps"... i dont mind if i lose all my data. i want it.
Click to expand...
Click to collapse
Yes, holding down Volume Down while your device is connected to PC will boot it to Fastboot mode. Flash TWRP (search this forum for the link) and the inatall the same FRD-L09C432B394 firmware files (update.zip and the rest) through TWRP. Once done, reboot your device to recovery (this time it will boot to stock recovery) and perform a full factory reset.
I just had the same issue, I rebooted in recovery mode by pressing "volume up" and the built in recovery told me the partition was corrupted and asked if I wanted to format it
So over the past day I had rooted my oneplus 7 pro and all was going well until I decided to delete the netflix stock application. Then I restarted my phone from holding the power button and pressing restart and then I booted into fastboot. Everytime I pressed start it would send me back to fastboot but I was able go to twrp recovery. Stupidly, I wiped the whole phone thinking I had no other options. Then after that, I found a setting in advanced that allowed me to leave recovery mode I think? Whatever it was, I was booted back into the oneplus start screen and reset up my phone. Then I tried to re-root my phone and couldn't get it to work because it said the magisk zip file was corrupt. Then I just decided to give up and go back to stock.
Little did I no, you are NOT supposed to relock the bootloader, because that is exactly what I did. After doing that, I got a message saying my phone was corrupt and I looked up quick solution and it said to press my volume buttons and power buttons. Now my phone won't even turn on. I am freaking out right now, knowing that my phone is probably bricked and I am going to have to pay probably a third of what I even paid for this phone to get it fixed. When I plug my phone into my pc the device is shown as "QUSB_BULK_CID:0404_SN:3BB285D7". If any of you guys can help, I'm all ears.
edit: I meant I locked oem/bootloader. Also, I got the phone to power on. It is in a bootloop where the oneplus logo shows up and then it gives me the message "Your device is corrupt. it can't be trusted and will not boot"
edit 2: After two hours, I finally fixed it. I downloaded the MSM tool and found the qualcomm drivers and after a few trial and errors, I finally got it to work
gotdiamonds99 said:
So over the past day I had rooted my oneplus 7 pro and all was going well until I decided to delete the netflix stock application. Then I restarted my phone from holding the power button and pressing restart and then I booted into fastboot. Everytime I pressed start it would send me back to fastboot but I was able go to twrp recovery. Stupidly, I wiped the whole phone thinking I had no other options. Then after that, I found a setting in advanced that allowed me to leave recovery mode I think? Whatever it was, I was booted back into the oneplus start screen and reset up my phone. Then I tried to re-root my phone and couldn't get it to work because it said the magisk zip file was corrupt. Then I just decided to give up and go back to stock.
Little did I no, you are NOT supposed to relock the bootloader, because that is exactly what I did. After doing that, I got a message saying my phone was corrupt and I looked up quick solution and it said to press my volume buttons and power buttons. Now my phone won't even turn on. I am freaking out right now, knowing that my phone is probably bricked and I am going to have to pay probably a third of what I even paid for this phone to get it fixed. When I plug my phone into my pc the device is shown as "QUSB_BULK_CID:0404_SN:3BB285D7". If any of you guys can help, I'm all ears.
edit: I meant I locked oem/bootloader. Also, I got the phone to power on. It is in a bootloop where the oneplus logo shows up and then it gives me the message "Your device is corrupt. it can't be trusted and will not boot"
edit 2: After two hours, I finally fixed it. I downloaded the MSM tool and found the qualcomm drivers and after a few trial and errors, I finally got it to work
Click to expand...
Click to collapse
U probably should have flashed stock firmware before relocking the bootloader
As long as you can boot into fastboot you should be good. Make sure you have correct drivers etc etc. Boot into fastboot and just boot into twrp, don't flash. Wipe data, system, vendor, dalv, cache. Recheck on what to delete and what order because it has to be the correct things and I might be mixed up off the top of my head, delete them in twrp. Then boot back into twrp after all that and reflash your custom rom. Take note if your ****s bricked you wont be able to install the zip via regular twrp swipe, you will have to use twrp sideload feature with adb and install from pc and install it that way. If that doesn't work at all just do a complete reflash of stock firmware via fastboot. Reflashing custom should work though I got mine out of a brick this way. As long as fastboots working you can get out of anything. Also Linux is 100x better than other OSs for this stuff.
cuNezzar said:
As long as you can boot into fastboot you should be good. Make sure you have correct drivers etc etc. Boot into fastboot and just boot into twrp, don't flash. Wipe data, system, vendor, dalv, cache. Recheck on what to delete and what order because it has to be the correct things and I might be mixed up off the top of my head, delete them in twrp. Then boot back into twrp after all that and reflash your custom rom. Take note if your ****s bricked you wont be able to install the zip via regular twrp swipe, you will have to use twrp sideload feature with adb and install from pc and install it that way. If that doesn't work at all just do a complete reflash of stock firmware via fastboot. Reflashing custom should work though I got mine out of a brick this way. As long as fastboots working you can get out of anything. Also Linux is 100x better than other OSs for this stuff.
Click to expand...
Click to collapse
OK here's the order. Boot into twrp, don't flash.
Wipe -> ADVANCED -- select system + vendor -> SWIPE TO WIPE
reboot bootloader
fastboot boot back into twrp
-- then --
Format data, Wipe cache & dalvik-cache
Flash ROM.
Then reboot system. Boom.
Remember you will most likely have to flash the ROM via sideload. As transferring will not work in a bricked phone.
cuNezzar said:
As long as you can boot into fastboot you should be good. Make sure you have correct drivers etc etc. Boot into fastboot and just boot into twrp, don't flash. Wipe data, system, vendor, dalv, cache. Recheck on what to delete and what order because it has to be the correct things and I might be mixed up off the top of my head, delete them in twrp. Then boot back into twrp after all that and reflash your custom rom. Take note if your ****s bricked you wont be able to install the zip via regular twrp swipe, you will have to use twrp sideload feature with adb and install from pc and install it that way. If that doesn't work at all just do a complete reflash of stock firmware via fastboot. Reflashing custom should work though I got mine out of a brick this way. As long as fastboots working you can get out of anything. Also Linux is 100x better than other OSs for this stuff.
Click to expand...
Click to collapse
I don't know if u realize this but he said that he relocked the bootloader after installing twrp and root
Austinredstoner said:
I don't know if u realize this but he said that he relocked the bootloader after installing twrp and root
Click to expand...
Click to collapse
Austinredstoner said:
I don't know if u realize this but he said that he relocked the bootloader after installing twrp and root
Click to expand...
Click to collapse
Damn forgot about that. Yeah In that case its most likely bricked to hell OP with no method of recovery as far as I know.