Hi All,
I just updated my N4 and N5 to lollipop via fastboot. I fastboot flash recovery then go into CWM 6.0.4.5 and sideload SuperSU 1.94. All seems fine at this point. I can reboot to the bootloader from CWM and go back to CWM ok. However, if I boot the system normally, both CWM and root are lost. Not sure if I'm missing something? It's been awhile since I've done anything with these devices, but they were previously running kitkat with CWM and rooted without issue. Thanks, Thomas.
twsnnva said:
Hi All,
I just updated my N4 and N5 to lollipop via fastboot. I fastboot flash recovery then go into CWM 6.0.4.5 and sideload SuperSU 1.94. All seems fine at this point. I can reboot to the bootloader from CWM and go back to CWM ok. However, if I boot the system normally, both CWM and root are lost. Not sure if I'm missing something? It's been awhile since I've done anything with these devices, but they were previously running kitkat with CWM and rooted without issue. Thanks, Thomas.
Click to expand...
Click to collapse
Outdated recovery and root.
New way to root N5 is Chainfire autoroot. Use that. It patches the kernel and injects SuperSU.
Related
I tried using superboot to root my nexus s, but ended up with having a stuck google screen upon reboot.
Is there anyway I can recover my phone to the original state. I can get into the boot screen by pressing up volume and the power button and I have downloaded an original rom; however, I don't know how to upload this rom
into the phone.
I unlocked the bootloader, and have the android SDK installed. I do have a response when I use the command "fastboot devices"
Is there any possible way to save my phone? Please help, Thanks in advance
is there a recovery image saved under the recovery option?
Hey I'm having the exact same problem as the OP.
I don't have a recovery image saved in recovery, so I tried to flash the latest CWM recovery image through adb, but the device isn't found.
My phone was rooted, then upgraded to 2.3.4, then got 2.3.6 OTA, but lost root. Tried to root with Superboot and now my phone's stuck.
How can I get my phone to work again?
ri ch said:
Hey I'm having the exact same problem as the OP.
I don't have a recovery image saved in recovery, so I tried to flash the latest CWM recovery image through adb, but the device isn't found.
My phone was rooted, then upgraded to 2.3.4, then got 2.3.6 OTA, but lost root. Tried to root with Superboot and now my phone's stuck.
How can I get my phone to work again?
Click to expand...
Click to collapse
You have to flash CWM using fastboot, not adb.
fastboot flash recovery recovery.img
Once you have the custom recovery flashed you can flash superuser in CWM to get root back or just flash one of the custom ROMs that include superuser.
Yes, I did exactly that.
I really have no idea what I'm doing so I'm extremely grateful for people who do.
Thanks
I am in the same boat as these other chaps. After installing the 2.3.6 OTA update I tried to root with Superboot and now my Nexus S just sits on the Google screen with the open padlock.
I've tried installing CWM recovery, as well as the boot.recovery.img that comes with Superboot, and it seems to install successfully. After rebooting my phone still sits on the Google screen, however.
Am I doing something wrong here (I'd previously rooted with few problems)?
EDIT: I should mention that after flashing the .img I'm trying to boot into recovery - at this point it just sits on the Google screen.
EDIT 2: Never mind, I sorted it. I tried using a different recovery.img (from this thread) and I was then able to get into recovery and restore a backup.
Hi Guys,
I have installed paranoid android cm10 last night. I was good but gmail was force closing, so I tried to install latest version thru goo manager app. I have installed recovery which it told me to get it but once i reboot my phone into recovery its no more moving a head. all I see is teamwin wallpaper and system reboots... any help is greatly appreciated.
Thanks
/bin/ said:
Hi Guys,
I have installed paranoid android cm10 last night. I was good but gmail was force closing, so I tried to install latest version thru goo manager app. I have installed recovery which it told me to get it but once i reboot my phone into recovery its no more moving a head. all I see is teamwin wallpaper and system reboots... any help is greatly appreciated.
Thanks
Click to expand...
Click to collapse
It probably didn't flash a kexec recovery. Just boot into recovery and flash a non kexec ROM ...hopefully you have one sitting on your SD card. If not your have to get one there or dd a kexec recovery with adb and reboot with the ROM you currently have installed
I guess he can't even get into recovery, as he said all he sees is wallpaper. He used TWRP recovery, which is NOT Kexec enabled. In order to flash CM, you needed to flash CWM 6.0.1.0. Now, basically your only choice is to either adb the cwm recovery, or just reflash stock using odin (easier option), flash cwm, then reinstall CM.
Vorfidus said:
I guess he can't even get into recovery, as he said all he sees is wallpaper. He used TWRP recovery, which is NOT Kexec enabled. In order to flash CM, you needed to flash CWM 6.0.1.0. Now, basically your only choice is to either adb the cwm recovery, or just reflash stock using odin (easier option), flash cwm, then reinstall CM.
Click to expand...
Click to collapse
It's odd his recovery won't open I wonder if goo flashed the incorrect version.
I successfully rooted my Verizon Galaxy S4. My root checker verifies this. However when I go to install CWM Recovery and I give it permission and everything and select boot into recovery it boots the phone into download mode. The same happens with TWRP recovery in GooManager. I am just stuck and not sure how to proceed. I have also tried flashing CWM Recovery via ODIN but that fails as well.
ChaoranWang said:
I successfully rooted my Verizon Galaxy S4. My root checker verifies this. However when I go to install CWM Recovery and I give it permission and everything and select boot into recovery it boots the phone into download mode. The same happens with TWRP recovery in GooManager. I am just stuck and not sure how to proceed. I have also tried flashing CWM Recovery via ODIN but that fails as well.
Click to expand...
Click to collapse
i think verizon locked the bootloader on their s4, i you might have to use the "Scary" Safestrap. but if a CWM image has been built already then there has to be a way to flash it, try snooping around zedomax's method http://galaxys4root.com/galaxy-s4-root/how-to-root-galaxy-s4/
You should do more research before you started. What your doing is a sure way for a brick. Only if your on mdk can you proceed as your doing. If your not you need to install safestrap.
Sent from my SCH-I545 using Tapatalk
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.