Hi,
I wanted to flash the just released lollipop image so I unlocked my phone and updated TWRP from 2.8.0.1 to 2.8.1.0. Then I started Recovery and it was doing some werid thing in a list (was too fast), then rebooted. Recovery came up again (only the image of TWRP) and a restart again. Since then always when I try to go into recovery the starting image will show up, after 2-3 secs it gets black for half a second, then the image will show up again. This is a permanent loop. I flashed back to the old recovery but nnothing, still the same (and this one worked before!).
Hopefully someone of you knows whats wrong.
Thanks,
S3cret
reflash twrp recovery. but to correct you on your mistake before you do it, factory imgs are not flashable via any recovery, you can only flash them via fastboot.
I reflashed recovery several times now. I just thought being on the latest recovery version would be good. I know how to flash the lollipop image via fastboot, but I still need recovery for root.
I locked and unlocked the bootloader again and the same happened. Recovery started, doing some weird things and then the loop again.
Edit: Ok, I fixed it, somehow, I dont rly know how...
TWRP only starts after flashing it on my device. After a reboot, it doesn't work.
vercety974 said:
TWRP only starts after flashing it on my device. After a reboot, it doesn't work.
Click to expand...
Click to collapse
exactly the same here
Yup, dead Android with red warning triangle appears...
My stock recovery is broken after fastbooting the latest 5 image. Shows a red triangle above the laying down android.
How are we supposed to fix this?
Moreover, I've just reflashed the entire rom, and can't access the stock recovery. But the stock recovery seems to work beacause I can to factory reset via the settings menu, backup and restore.... Maybe it is the new security policy from google, to avoid that a thief make a factory reset directly from the recovery ?
So we can't navigate in the stock recovery anymore ?
Highway 55 said:
After fastboot flashing the .img files you need to (WITHOUT REBOOTING) flash custom recovery, TWRP etc... After that from the bootloader reboot into TWRP or whatever. When your in the custom recovery you need to adb push a permissive stock kernel or custom kernel as well as suspersu.zip. Again, without rebooting into the system, flash the kernel first then supersu. Now you can reboot into the system. ?
Click to expand...
Click to collapse
vercety974 said:
Moreover, I've just reflashed the entire rom, and can't access the stock recovery. But the stock recovery seems to work beacause I can to factory reset via the settings menu, backup and restore.... Maybe it is the new security policy from google, to avoid that a thief make a factory reset directly from the recovery ?
So we can't navigate in the stock recovery anymore ?
Click to expand...
Click to collapse
Yes I think it does have to do with the new selinux security stuff. I don't know the specifics. Maybe you want to refer to this thread. http://forum.xda-developers.com/showthread.php?p=56538538 @rootSU knows far more than I do. [emoji6]
Highway 55 said:
Yes I think it does have to do with the new selinux security stuff. I don't know the specifics. Maybe you want to refer to this thread. http://forum.xda-developers.com/showthread.php?p=56538538 @rootSU knows far more than I do. [emoji6]
Click to expand...
Click to collapse
It is exactly as he said in the post you linked.
Flash TWRP recovery and immidiately after run auto root. Then TWRP recovery will survive system boots.
Related
Hey guys, flashed this camera mod http://forum.xda-developers.com/showthread.php?t=2516061
and am now stuck in a boot loop. my huge mistake was i didn't make a backup on CWN when i installed it, since i'm a massive noob.
I'd post this in the thread for the mod, but new accts can't post in developer forum (to prevent threads like these, probably).
anyone know a quick solution to this? i've dalvik wiped, factory resetted, wiped cache partition.
edit: i also don't know how to get the stock camera ROM back on the device since it doesn't show up in my windows explorer. if i knew that, it'd be easy to go back to stock.
stealth0wnz said:
Hey guys, flashed this camera mod http://forum.xda-developers.com/showthread.php?t=2516061
and am now stuck in a boot loop. my huge mistake was i didn't make a backup on CWN when i installed it, since i'm a massive noob.
I'd post this in the thread for the mod, but new accts can't post in developer forum (to prevent threads like these, probably).
anyone know a quick solution to this? i've dalvik wiped, factory resetted, wiped cache partition.
edit: i also don't know how to get the stock camera ROM back on the device since it doesn't show up in my windows explorer. if i knew that, it'd be easy to go back to stock.
Click to expand...
Click to collapse
If you can get back to the boot loader (hold down power button and volume down) and recovery (choice in bootloader menu), you are fine. I did the same thing. you can adb push the stock file (in his developer thread) and then flash it with custom recovery.
Here is a link showing how to adb push - http://forum.xda-developers.com/showthread.php?t=1667929
If that doesn't work, you can always flash back stock...... Unfortunately have had to do this more than once and have learned my lesson on backups.
Speedbal
Hope that helps.
speedbal said:
If you can get back to the boot loader (hold down power button and volume down) and recovery (choice in bootloader menu), you are fine. I did the same thing. you can adb push the stock file (in his developer thread) and then flash it with custom recovery.
If that doesn't work, you can always flash back stock...... Unfortunately have had to do this more than once and have learned my lesson on backups.
Speedbal
Hope that helps.
Click to expand...
Click to collapse
I guess you gotta learn this stuff at some point, thanks for your help! i forgot that you could push files!
now a brand new issue is that anytime i flash ANYTHING to the phone, adb doesn't see the device anymore.
anyone know what's up with that?
URGENT
I did the camera mod too and happened to kill my phone trying to get a camera back on it. It boot loops bc now there is no os. Tried installing Cm-12.1 on my N910P and its now getting a "Error updating binary zip" on TWRP. I have no idea what to do. I have wiped the phone several times. Tried using odin and it failed when the phone was up and running, now it still fails any rom. Please help. I have pushed thru adb, odin, im out of options on my end. no backup either. Looking for a stock twrp recovery file for any note4 dont care anymore
SteveRogers1776 said:
I did the camera mod too and happened to kill my phone trying to get a camera back on it. It boot loops bc now there is no os. Tried installing Cm-12.1 on my N910P and its now getting a "Error updating binary zip" on TWRP. I have no idea what to do. I have wiped the phone several times. Tried using odin and it failed when the phone was up and running, now it still fails any rom. Please help. I have pushed thru adb, odin, im out of options on my end. no backup either. Looking for a stock twrp recovery file for any note4 dont care anymore
Click to expand...
Click to collapse
New nightlies of CM12.1 needs the bootloader to be updated to newer version (HHZ12H).
Following the link to flashable zip of new bootloader: https://www.androidfilehost.com/?fid=23991606952613145 (Credit to @mo976)
Flash it in recovery
Wipe the cache
Reboot into bootloader and select recovery.
Flash CM12.1 rom.
I just tried what you recommended . Maybe I'm doing it wrong but I'm still getting "error updating binary zip" when trying to load anything on twrp
Hello guys, having a bit of a dilemna here as only took the plunge to root today and is my first time in doing so. What I have done is updated to 4.4.2 KitKat OTA and then rooted my moto g. I used the superboot method and got the horrible pink screen and had to manually install supersu, however the device is rooted and obviously the bootloader is unlocked. I then proceeded to put everything back on my phone and then encrypted my phone.
However, I tried to get into recovery (stock) and was fronted with the on its back android with its belly open and red "!" in a triangle. I got this before I even unlocked to bootloader. Anyhow, I wanted to use a custom recovery so I could manage different ROMs in ROM manager etc, so I flashed CWM6046-MotoG44.img (CMW ver. 6.0.4.6) and all was swell.... until i wanted to make a backup.
I did a little searching around and was stumped until I found a post suggesting that CMW couldnt mount storage because the device was encrypted.
What I would like to know if at all possible; what would be the best course of action to take, as im unsure what will/could brick/break my device and as its encrypted I dont think adb commands are pushed as when flashing the recovery image, my device was listed in fastboot devices but not adb devices.
Should I flash a stock image and go from there, put everything back on yada yada yada and NOT encrypt the device, or....
Should I do a factory reset? will this brick my device/lose root access? or will I be able to re root?
I really appreciate any input you guys can give me, and for the meantime im just going to leave my device as it is and not flash anything else,
Many thanks and best regards,
voosh
Anybody have any ideas?
Can anybody help me here. Need to get this sorted so I can flash a custom ROM. Thanks
Bump...................
voosh710 said:
Hello guys, having a bit of a dilemna here as only took the plunge to root today and is my first time in doing so. What I have done is updated to 4.4.2 KitKat OTA and then rooted my moto g. I used the superboot method and got the horrible pink screen and had to manually install supersu, however the device is rooted and obviously the bootloader is unlocked. I then proceeded to put everything back on my phone and then encrypted my phone.
However, I tried to get into recovery (stock) and was fronted with the on its back android with its belly open and red "!" in a triangle. I got this before I even unlocked to bootloader. Anyhow, I wanted to use a custom recovery so I could manage different ROMs in ROM manager etc, so I flashed CWM6046-MotoG44.img (CMW ver. 6.0.4.6) and all was swell.... until i wanted to make a backup.
I did a little searching around and was stumped until I found a post suggesting that CMW couldnt mount storage because the device was encrypted.
What I would like to know if at all possible; what would be the best course of action to take, as im unsure what will/could brick/break my device and as its encrypted I dont think adb commands are pushed as when flashing the recovery image, my device was listed in fastboot devices but not adb devices.
Should I flash a stock image and go from there, put everything back on yada yada yada and NOT encrypt the device, or....
Should I do a factory reset? will this brick my device/lose root access? or will I be able to re root?
I really appreciate any input you guys can give me, and for the meantime im just going to leave my device as it is and not flash anything else,
Many thanks and best regards,
voosh
Click to expand...
Click to collapse
When you get the dead android hold power button for ten seconds then tap the power button,that should get you into stock recovery ,then navigate to wipe data factory reset ,you shouldn't lose root but you will lose da ta and apps
Thanks for the reply but I have already installed the cwm custom recovery. Should I add that I'm still able to access device, my problem mainly is getting rid of encryption as I can't use cwm while device is encrypted and can only do so by factory reset or flashing a stock ROM, but unsure of which option to take. Many thanks and best regards
kieranc88 said:
When you get the dead android hold power button for ten seconds then tap the power button,that should get you into stock recovery ,then navigate to wipe data factory reset ,you shouldn't lose root but you will lose da ta and apps
Click to expand...
Click to collapse
https://docs.google.com/file/d/0B2LP8tI1Xwu4MGtPTlpVcVQxN0k/preview try this cwm it worked for me,I'm not too clued up on encryption but I'm guessing you can't read/write to phones system to easily with it on so I'd guess it conflicts with root
---------- Post added at 06:10 PM ---------- Previous post was at 06:08 PM ----------
kieranc88 said:
When you get the dead android hold power button for ten seconds then tap the power button,that should get you into stock recovery ,then navigate to wipe data factory reset ,you shouldn't lose root but you will lose da ta and apps
Click to expand...
Click to collapse
voosh710 said:
Thanks for the reply but I have already installed the cwm custom recovery. Should I add that I'm still able to access device, my problem mainly is getting rid of encryption as I can't use cwm while device is encrypted and can only do so by factory reset or flashing a stock ROM, but unsure of which option to take. Many thanks and best regards
Click to expand...
Click to collapse
So when you boot to recovery can you access recovery options or do you get dead robot
kieranc88 said:
https://docs.google.com/file/d/0B2LP8tI1Xwu4MGtPTlpVcVQxN0k/preview try this cwm it worked for me,I'm not too clued up on encryption but I'm guessing you can't read/write to phones system to easily with it on so I'd guess it conflicts with root
---------- Post added at 06:10 PM ---------- Previous post was at 06:08 PM ----------
So when you boot to recovery can you access recovery options or do you get dead robot
Click to expand...
Click to collapse
I did get a dead robot. So I flashed CWM custom recovery. I now get the cwm recovery and options, but I can't make a backup becausey filesystem is encrypted, so would like to know the best way to decrypt by means of flashing a new or ROM or simply doing a factory reset within tho phones menus.
Many thanks
voosh710 said:
I did get a dead robot. So I flashed CWM custom recovery. I now get the cwm recovery and options, but I can't make a backup becausey filesystem is encrypted, so would like to know the best way to decrypt by means of flashing a new or ROM or simply doing a factory reset within tho phones menus.
Many thanks
Click to expand...
Click to collapse
OK,you need to boot into cwm and choose the wipe data factory reset option from cwm, I tried to wipe my phone before from the phones menu and because it had a custom recovery it didn't work,but if you boot cwm-wipe data/factory reset it will remove encryption.
Any luck???
kieranc88 said:
Any luck???
Click to expand...
Click to collapse
Sorry, I fell asleep lol was a long day.
Going to try it now and will keep you posted, Cheers.
EDIT - Didnt work - failed to mount storage because "android secure"
Factory reset within the phone also didnt work - The phone reset and the android with the blue thing in its stomach was stuck in a loop, probably because of custom recovery.
Is there a stock recovery I can flash to factory restore the phone?
EDIT 2 - Flashed this recovery - http://forum.xda-developers.com/showthread.php?t=2578243
Now when I boot into recovery it just boots into the phone regularly. When performing a factory reset now the android doesnt even appear and the phone boots regularly again, still encrypted
voosh710 said:
Sorry, I fell asleep lol was a long day.
Going to try it now and will keep you posted, Cheers.
EDIT - Didnt work - failed to mount storage because "android secure"
Factory reset within the phone also didnt work - The phone reset and the android with the blue thing in its stomach was stuck in a loop, probably because of custom recovery.
Is there a stock recovery I can flash to factory restore the phone?
EDIT 2 - Flashed this recovery - http://forum.xda-developers.com/showthread.php?t=2578243
Now when I boot into recovery it just boots into the phone regularly. When performing a factory reset now the android doesnt even appear and the phone boots regularly again, still encrypted
Click to expand...
Click to collapse
I kinda guessed that would happen because its not stock recovery,have u got a us version or international(is it xt1032 or xt1034?
kieranc88 said:
I kinda guessed that would happen because its not stock recovery,have u got a us version or international(is it xt1032 or xt1034?
Click to expand...
Click to collapse
Its a unlocked retail UK version, not sure if its xt1032 or xt1034 because I renamed it to Moto G.
voosh710 said:
Its a unlocked retail UK version, not sure if its xt1032 or xt1034 because I renamed it to Moto G.
Click to expand...
Click to collapse
You've got the same as mine,OK if that didn't work it might be because its jellybean, this is a recovery for the us version but its a KitKat recovery but worst that can happen is it won't boot to recovery, flash it and if doesn't work I'll see can I extract the recovery image from my phone, try it and get back to me asap fastboot flash recovery recovery.IMG
https://www.dropbox.com/s/66br4aiyzipu6x9/recovery.img
kieranc88 said:
You've got the same as mine,OK if that didn't work it might be because its jellybean, this is a recovery for the us version but its a KitKat recovery but worst that can happen is it won't boot to recovery, flash it and if doesn't work I'll see can I extract the recovery image from my phone, try it and get back to me asap fastboot flash recovery recovery.IMG
https://www.dropbox.com/s/66br4aiyzipu6x9/recovery.img
Click to expand...
Click to collapse
Flashed and still boots regularly .
voosh710 said:
Flashed and still boots regularly .
Click to expand...
Click to collapse
In the command line is it saying recovery sent
kieranc88 said:
In the command line is it saying recovery sent
Click to expand...
Click to collapse
Sent and finished ok
voosh710 said:
Sent and finished ok
Click to expand...
Click to collapse
How many times have you flashed it,try flashing two three timees
kieranc88 said:
How many times have you flashed it,try flashing two three timees
Click to expand...
Click to collapse
Actually, looking at the device it says "hab check failed for recovery"
However the other one (jellybean one i think that I linked to) never.
tried flashing 5 or 6 times no luck
Try this link to restore to 4.3 then ota to 4.4 again http://www.modaco.com/topic/366786-how-to-flash-to-the-standard-uk-rom/
Hey guys.
I just got a very nice condition used TF700T. I am trying to get recovery to install so I can flash a rom. I used the Transformer Toolkit to unlock it, which worked, it says device unlocked when booting.
But I absolutely cannot get it to Root, or flash recovery. If I try using debugfs root generic 2.3 it fails to write everything. If I try to flash any recovery with the toolkit it downloads and says flashing but just sits at about 25%, it boots my device into the screen that says usb fastboot mode with the three icons that say RCK Android and factory wipe. If I click the RCK it says rebooting and then goes to android mascot installing icon, but then the one with an X and error appears. What on earth am I doing wrong?
Is it the latest 4.2 update locking me out? Can I downgrade? I just can't get anything to root or flash recovery no matter what I do. I feel a little defeated being a long time member and 3 phone habitual rom flasher :crying:\
Any ideas what i'm missing?
benjmiester said:
Hey guys.
I just got a very nice condition used TF700T. I am trying to get recovery to install so I can flash a rom. I used the Transformer Toolkit to unlock it, which worked, it says device unlocked when booting.
But I absolutely cannot get it to Root, or flash recovery. If I try using debugfs root generic 2.3 it fails to write everything. If I try to flash any recovery with the toolkit it downloads and says flashing but just sits at about 25%, it boots my device into the screen that says usb fastboot mode with the three icons that say RCK Android and factory wipe. If I click the RCK it says rebooting and then goes to android mascot installing icon, but then the one with an X and error appears. What on earth am I doing wrong?
Is it the latest 4.2 update locking me out? Can I downgrade? I just can't get anything to root or flash recovery no matter what I do. I feel a little defeated being a long time member and 3 phone habitual rom flasher :crying:\
Any ideas what i'm missing?
Click to expand...
Click to collapse
What custom recovery are you installing? You may want to try with fastboot or adb method to flash your custom recovery which doesn't require rooted device, good luck....
LetMeKnow said:
What custom recovery are you installing? You may want to try with fastboot or adb method to flash your custom recovery which doesn't require rooted device, good luck....
Click to expand...
Click to collapse
Well I tried TWRP 2.7.1.1 I believe and also CWM , and Phil's custom touch CWM that all three are options to flash with the all in one ADB Toolkit app via USB from windows (http://forum.xda-developers.com/showthread.php?t=2094746)
How do I do the Fastboot method? I read about that, but have no idea how the process goes. I'm ok with skipping root and going straight to recovery and a rom because I can just flash superuser after if the rom isn't rooted already.
benjmiester said:
Well I tried TWRP 2.7.1.1 I believe and also CWM , and Phil's custom touch CWM that all three are options to flash with the all in one ADB Toolkit app via USB from windows (http://forum.xda-developers.com/showthread.php?t=2094746)
How do I do the Fastboot method? I read about that, but have no idea how the process goes. I'm ok with skipping root and going straight to recovery and a rom because I can just flash superuser after if the rom isn't rooted already.
Click to expand...
Click to collapse
I wanted to try an app I used to get twrp onto my LG G2 for the first time called "flashify" that worked like a charm. I just installed the app, downloaded the twrp file and flashed it then it reboots to recovery, but it requires root as far as I know. Does unlocking the boot loader allow things like this?
benjmiester said:
I wanted to try an app I used to get twrp onto my LG G2 for the first time called "flashify" that worked like a charm. I just installed the app, downloaded the twrp file and flashed it then it reboots to recovery, but it requires root as far as I know. Does unlocking the boot loader allow things like this?
Click to expand...
Click to collapse
Unlocked bootloader is allowed you to install the custom recovery so you can install the custom ROM, I believed..... You can check this guide out to see if you can setup your fastboot/adb. It is very easy to follow for the beginners, good luck....:fingers-crossed:
http://forum.xda-developers.com/showthread.php?t=2688891
benjmiester said:
I wanted to try an app I used to get twrp onto my LG G2 for the first time called "flashify" that worked like a charm. I just installed the app, downloaded the twrp file and flashed it then it reboots to recovery, but it requires root as far as I know. Does unlocking the boot loader allow things like this?
Click to expand...
Click to collapse
Once you unlocked the bootloader you can flash a custom recovery and after that - the sky's the limit.
Flashify works great, and it is a wonderful tool as long as you're able to boot into Android.
My problem with Flashify and Goomanager and TwrpManger is that it saves users from setting up a proper ADB/fastboot connection from PC to tablet.
As long as you can boot Android, these apps are great. But what if you can't? Once the tablet doesn't boot it's so much harder (and often too late) to get the correct drivers installed for ADB and fastboot.
So if you flash your recovery with any of those apps still make sure you have access with ADB and fastboot from your PC.
You will regret it if you don't - I (almost) guarantee it.
That's an excellent point. Thanks. I did actually get the Fastboot method to work. The problem was that I kept clicking into RCK recovery when I ws supposed to just leave it on that screen to push twrp instead. I got recover and just got done doing a backup. I'm about the flash my first rom (http://forum.xda-developers.com/showthread.php?t=2672751). Do we need to do factory reset / wipe data/system etc? The instructions on the ROM post say to just flash it from twrp so I'm guessing it has a built in wipe feature during install?
benjmiester said:
That's an excellent point. Thanks. I did actually get the Fastboot method to work. The problem was that I kept clicking into RCK recovery when I ws supposed to just leave it on that screen to push twrp instead. I got recover and just got done doing a backup. I'm about the flash my first rom (http://forum.xda-developers.com/showthread.php?t=2672751). Do we need to do factory reset / wipe data/system etc? The instructions on the ROM post say to just flash it from twrp so I'm guessing it has a built in wipe feature during install?
Click to expand...
Click to collapse
The instructions in the OP actually say that you have to do a full wipe (Factory Wipe) in TWRP coming from a different rom base. Which would be you unless you had a version of CROMBi-KK installed prior to this.
It's the default selection under the Wipe menu in TWRP. Just do that and then flash the rom and your ok.
Do not use the Factory Reset option from Settings or the Wipe Data option from the BL menu! Do this in TWRP only!
Cool thanks. I figured so because that's the norm with roms on all my phones. Thanks a lot for the help guys. So happy to be get KK running on my new toy!
Just wanted to update. KK 4.4.3 rom flashed and booted in. It's much nicer. The stock was a little laggy, and KK breathed a lot of new life into my ancient single core 1.0 ghz Galaxy S that I use as a music player so I figured it would help make the tab real nice and snappy too. Gotta go now, much fun to be had!!
Hi guys, I flashed the latest factory image, then flashed the latest TWRP but can access it 1 out of 10 tries.. What am I doing wrong? Is it a faulty replacement phone? Never had this issue with my other nexus 5 (same recovery file but lollipop and not marshmallow) and now I have this problem.. Tried to riflashato the factory image 5 times, boot to recovery without installing but nothing changed.. Thanks in advance!
If you just just flashed TWRP, then booted into Android, then reboot into recovery.. Android will overwrite TWRP with the stock recovery.
a hammerhead wrote this.
beekay201 said:
If you just just flashed TWRP, then booted into Android, then reboot into recovery.. Android will overwrite TWRP with the stock recovery.
a hammerhead wrote this.
Click to expand...
Click to collapse
Never happened before.. How can I prevent this? Sometimes I can't even boot to twrp after flashing and not rebooting to android..
carlese said:
Never happened before.. How can I prevent this? Sometimes I can't even boot to twrp after flashing and not rebooting to android..
Click to expand...
Click to collapse
do you finde fix
slavisa037 said:
do you finde fix
Click to expand...
Click to collapse
Downloaded twrp again and used flashify..
carlese said:
Downloaded twrp again and used flashify..
Click to expand...
Click to collapse
This is not really a fix, since to use Flashify one needs to be rooted already.
What I did to work around this was reflash LMY48M. After reflashing that, fastboot correctly boots/flashes twrp.
I've read that the issue arises when trying to boot and/or flash twrp with MRA56K installed, AND the device is connected to USB.
Ok, i got some of problems here, i tryied to root my Nexus 5 with other Android 6 version, it was the first one launched after development version. Now i have MRA58K version.
Problem 1 : I have no stock recovery, i first rooted original version of Marshmallow with CWM and i soft bricked, so no backup, no factory images. Installed MRA58K and there is no stock recovery, thanks god i can use bootloader. I can install TWRP, but i want to install the old recovery, Tell me how to do it.
Problem 2: Actual version of Marshmallow ask me to install a patch, but when installing i got stuck in TWRP, it cant install it (yes, android was rooted, but i installed twrp before root, and the update were before it.)
Thanks.
You can flash a stock ROM using the flash-all file in a command prompt. This will install stock ROM with stock recovery. Make sure the phone has an unlocked bootloader and you should be fine.
Official OTA updates cannot be installed with a custom recovery.
I tryied 3 times to install OS with flash-all. All the problems start after i installed CWM and try to root the phone, but after that, i used a stock rom image that was different build than actually one.
I`m not sure yet who`s fault is.
Any ideas?
I don't recommend using CWM, only TWRP.
After you flash TWRP always boot into it, and since you're flashing a custom recovery I'm going to assume you don't care about OTA's, swipe to allow system to be mounted. TWRP will automatically patch the system to survive android trying to overwrite it. Reboot into TWRP a second time to be safe. TWRP should stick from now on until you flash over it or restore stock system partition.
Yes, now i have TWRP as recovery, but i want to replace it with stock recovery.
Problem is, when i upload stock recovery and try to boot in recovery mode, i got the green dead android with red triangle.
But after TWRP uploading and booting in recovery mode, TWRP is there..
I really don`t know what`s wrong.
Flash stock recovery, select recovery from the fastboot menu, hold the power button and press volume up button.
Hello everyone.
I had a problem flashing TWRP on my Google Nexus 5, or better the problem comes when I try to enter the recovery.
I followed this pattern from stock android 6.0.1 with august security patch:
1) unlock bootloader
2) downloaded lastest TWRP (3.0.2 hammerhead) recovery from the official website
3) flash it with "fastboot flash recovery recovery.img"
Until this point everything's alright but then when I unplug my phone from the laptop and click on enter recovery something strange happens.
I can see the TWRP boot image but as soon as I go in I see tons of errors related to "cannot mount ..." and some partitions name like /data, /cache, and then starts the bootloop without let me any chance to do something. Sorry but I can't see every error beacuse this happen too fast.
Any idea on what is going on?
I've tried the TWRP 3.0.1 but is the same shuold I go down or maybe I have to change it beacuse of compatibily issues with the monthly patches?
Thank you for your help, I hope I explained my problem clearly.
After unlocking the bootloader, phone wipe all data? Did you reboot after unlocking bootloader?
audit13 said:
After unlocking the bootloader, phone wipe all data? Did you reboot after unlocking bootloader?
Click to expand...
Click to collapse
No I've just unlocked and then tryied to flash the recovery without wipe.
But data is already wiped by unlocking the bootloader isn't it?
Anyway thanks for your reply as soon as I can I'll try what you have written.
Yes, the data should be automatically wiped. Try TWRP 2.87. If the phone still doesn't boot into TWRP, reflash stock recovery, flash userdata.img, immediately boot into stock recovery using the button combo without rebooting, perform a factory wipe, reboot into fastboot, and flash TWRP again.
audit13 said:
Yes, the data should be automatically wiped. Try TWRP 2.87. If the phone still doesn't boot into TWRP, reflash stock recovery, flash userdata.img, immediately boot into stock recovery using the button combo without rebooting, perform a factory wipe, reboot into fastboot, and flash TWRP again.
Click to expand...
Click to collapse
Thank you so much for telling me to flash the 2.8.7, i've choosen the 2.8.7.1 without success (it did't flash i don't know why) but then after another wipe all I've flashed the 2.8.7.0 and it seems to work.
The only thing I would like to ask now is: I'm going to flash superSU and elementalX over stock AOSP (I don't want custom ROM for now) and can this recovery cause problem because of it is not the last update?
Thank you again for the answer!
I have not tried 2.87 with Elemental X. The only way to determine whether it will work would be to try it. I recommend creating a nandroid backup before flashing Elemental so you can restore if something goes wrong.
TWRP Restore problem
Hi, I have an issue with the resotre of TWRP...
Here's what I did:
-Downloaded the latest OTA image https://developers.google.com/android/nexus/ota
-Downloaded latest SuperSU http://download.chainfire.eu/supersu-stable
-Downloaded latest ElementalX http://elementalx.org/devices/nexus-5/
-reboot to TWRP
Choose OTA, then SuperSU, then ElementalX
Luunch the restore..
And my screen is "blocked" from 5 hours on Install Zip 1 of 3.
"blocked" means doesn't move to the Zip2 but the clock is moving... the screen is locking itself after few seconds and I am able to unlock it...
Any idea how to exit properly ?
I have rebooted...deleted all my music... (I think that the issue may come from insufficient disk space) and relaunched...
Will see...
download Nexus Root Toolkit-type in google Nexus Root Toolkit - and watch from yuotoube how it work's
good luck
hunter-dz said:
download Nexus Root Toolkit-type in google Nexus Root Toolkit - and watch from yuotoube how it work's
good luck
Click to expand...
Click to collapse
My N5 was already rooted... and it's the second time that I update the OTA using directly TWRP... and for the August patch it has worked fine.
I don't know what's happen now...
kevtuning said:
My N5 was already rooted... and it's the second time that I update the OTA using directly TWRP... and for the August patch it has worked fine.
I don't know what's happen now...
Click to expand...
Click to collapse
Download thé nrt and i Will teach how to root ur n5
And type in Google nrt n5 xda
audit13 said:
I have not tried 2.87 with Elemental X. The only way to determine whether it will work would be to try it. I recommend creating a nandroid backup before flashing Elemental so you can restore if something goes wrong.
Click to expand...
Click to collapse
Now I can confirm that I was able to flash the lastest SuperSU and ElementalX with TWRP 2.8.7.0 without any problem, so thank you again for your help.
kevtuning said:
Hi, I have an issue with the resotre of TWRP...
Here's what I did:
-Downloaded the latest OTA image https://developers.google.com/android/nexus/ota
-Downloaded latest SuperSU http://download.chainfire.eu/supersu-stable
-Downloaded latest ElementalX http://elementalx.org/devices/nexus-5/
-reboot to TWRP
Choose OTA, then SuperSU, then ElementalX
Luunch the restore..
And my screen is "blocked" from 5 hours on Install Zip 1 of 3.
"blocked" means doesn't move to the Zip2 but the clock is moving... the screen is locking itself after few seconds and I am able to unlock it...
Any idea how to exit properly ?
Click to expand...
Click to collapse
Hi, I've have successfully installed the last OTA update but not with zip file, instead I downloaded the factory image and flashed with fastboot boot.img and system.img (also vendor.img if you have one) then rebooted into TWRP and installed the lastest ElementalX and SuperSU.
I'm not sure but I think that factory image zip file are not installable via recovery but only with the flash-all that comes with them. This script use fastboot to flash everything you need of the factory image
You can find this procedure on the ElementalX website, here is the link hope it can help out: http://elementalx.org/how-to-install-android-monthly-security-updates/
Finally... I installed CM13 and ElementalX... in some minutes ...
I suppose the the problem was in my zip file...