Database Users

[Q] can't get into custom recovery

hi im new to the whole nexus 7 scene just got it today and its also my first nexus device. came from a highly locked down dx2 then to htc and now im trying this. i used the nexus root toolkit v1.5.5 to unlock and root and flash custom recovery. but when i hold power down+volume down i get into the boot loader and i choose recovery then GOOGLE splash screen comes up and it does absolutly nothing while no usb chord plugged in. with usb chord it stays at the google splash screen for but a moment then just boots into android.
i tried the advance utilities and flash the cwm that way but same results. im still on 4.1.0 jrn84d. what am i doing wrong? i don't fully understand adb so if there is quite litteraly a step by step please give me a link or write it down if no such link exists. my last hdd that had adb all setup and ready crashed so its not setup and i was talking to someone who helped me get it going. all i know is i need to use command prompt but getting it into adb and then using it to push and get into cwm i have no clue.
i would love to make a nandroid and then install a kernal to gget the full power out of this thing. it is unlocked and rooted already.

They using ROM Manager app to install CWM and also boot into recovery. Will work for sure as long as you're rooted.
Sent from my SPH-L710 using xda app-developers app

dante32278 said:
They using ROM Manager app to install CWM and also boot into recovery. Will work for sure as long as you're rooted.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
If you follow the steps correctly, it should have a custom recovery installed. check if your rom is actually rooted.

EDIT: What the hell are you doing on 4.1.0? I thought factory stock was 4.1.1.
Use this:
http://forum.xda-developers.com/showthread.php?t=1809195
Get GooManager from the play store. It can download and install TWRP recovery which I prefer. GooManager will let you reboot into recovery too.
Sent from my Paranoid Nexus 7 using XDA Premium

cakessi said:
EDIT: What the hell are you doing on 4.1.0? I thought factory stock was 4.1.1.
Use this:
http://forum.xda-developers.com/showthread.php?t=1809195
Get GooManager from the play store. It can download and install TWRP recovery which I prefer. GooManager will let you reboot into recovery too.
Sent from my Paranoid Nexus 7 using XDA Premium
Click to expand...
Click to collapse
lol i dunno just came with it. its the 16gb version dunno why it came with 4.1.0 but it did. and when i installed rom manager i flashed cwm with that then choose to boot into recover that way and it worked. i am unlocked and rooted and now have a nandroid. have yet to try going to cwm with power+volume down being pressed i will give it a shot later on and make another nandroid before i accept the update im being propted for.
ty guys for the help.

There was a bug that required the N7 to be connected to a PC-USB connection before it would work. They didn't fix the bug until 4.1.2.
Your best bet, if you can boot into Android, is to download a Reboot-to-Recovery app or use CWM or GooManager to reset into recovery. If you are boot looping, throw a USB connection into the mix when trying to do it. I believe it is VolDown+Power+USB connection. Drivers may also be a factor.

Thanks for the reply. I finally updated it. Had to do three updates though. First to 4.1.1 then to 4.1.2 and then to 4.2. I have a nandroid at 4.1.0 so if I need to do anything I'm just going back. I used ota root keeper and the cwm that's from rom manager allows you to choose to protect your custom recovery as well as root. But I don't know if that was working in tandem with ota root keeper since I made sure to back it up first before I did anything.
Sent from my Nexus 7 using xda app-developers app

Flash issues

I'm on twrp 2.6.3.0 and anytime I try and flash a new 4.4 ROM the install fails.
Sent from my Nexus 4 using xda app-developers app

wrong advice, my mistake... thanks for the reminding simms22.

But I wanna stay rooted
Sent from my Nexus 4 using xda app-developers app

You don't have to unroot. Just download and flash TWRP 2.6.3.2. On that build, they fixed the issues of 4.4 ROMS incorrectly flashing. Using it myself with no problems. Its in Original Android Development if I'm not mistaken

Flashing 4.4 Factory Image issues
Currently on my Nexus 4.
Android 4.3 Unlocked and Rooted
Kernel Version: 3.4.0-perf-gf43c3d9
Build: JWR66Y
Baseband: M9614A-CEFWMAZM-2.0.1700.84
Using ClockWorkMod Recovery v6.0.4.3, when trying to flash the 4.4 factory image .zip file on the SD Card I keep getting an "Installation Aborted" error after "Installing update..." step and the red Triangle on the android figure.
When attempting to sideload using stock recovery, getting a "Signature Verification Failed"
Any Suggestions? Thanks

darkfire2040 said:
I'm on twrp 2.6.3.0 and anytime I try and flash a new 4.4 ROM the install fails.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
If you haven't already tried it, under Mount uncheck system, that solved the problem for me.

Yeah I wanna stay in twrp so I will try flashing the latest. The error I'm getting is. Error while trying to update binarys
Sent from my Nexus 4 using xda app-developers app

will_chrome said:
you've got to unroot and back to stock rwcovery 1st if I'm not mistake. the guide to flash stock rom can be found in http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
wtf??? never ever give advice on android ever again!
op, all you have to do is update your recovery to twrp latest(v.2.6.3.3). flash your rom, flash your 4.4 gapps, and flash the latest supersu then reboot.

simms22 said:
all you have to do is update your recovery to twrp latest(v.2.6.3.3). flash your rom, flash your 4.4 gapps, and flash the latest supersu then reboot.
Click to expand...
Click to collapse
I will chime in on this one. I too have had constant failures with TWRP trying to flash ROMs lately. I'm running 2.6.3.3 and everything results in failure. I've tried the unchecking of system mount, multiple downloads with verified MD5s, sideloads, etc. Nothing is working.
Sent from my Nexus 4 using Tapatalk

ph37rd said:
I will chime in on this one. I too have had constant failures with TWRP trying to flash ROMs lately. I'm running 2.6.3.3 and everything results in failure. I've tried the unchecking of system mount, multiple downloads with verified MD5s, sideloads, etc. Nothing is working.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
next time you flash, after it fails, boot into the bootloader from the recovery. then, from the bootloader, go into the recovery again and flash.

simms22 said:
next time you flash, after it fails, boot into the bootloader from the recovery. then, from the bootloader, go into the recovery again and flash.
Click to expand...
Click to collapse
Recognizing your knowledge and experience so asking you to explain why that works. Does something in the internals get reset?
Sent from my Nexus 4 using Tapatalk

ph37rd said:
Recognizing your knowledge and experience so asking you to explain why that works. Does something in the internals get reset?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
ill be honest, i dont know why. but i do know that it has worked for many. the alternative, which works 100% of the time, would be to delete your recovery, then flash it again. btw, did it work for you?

simms22 said:
ill be honest, i dont know why. but i do know that it has worked for many. the alternative, which works 100% of the time, would be to delete your recovery, then flash it again. btw, did it work for you?
Click to expand...
Click to collapse
I won't be able to experiment for a couple of weeks. I do know that I've wiped my phone four times or more in the last week with the 4.3 and 4.4 factory images and either manually or using one of the tool kits have added TWRP custom recovery and rooted the phone. Each time trying to flash a ROM it would result in a failure.
Next time I get the chance, I'll give your suggestion a shot and let you know. Are there logs I can capture that might prove useful?
Sent from my Nexus 4 using Tapatalk

ph37rd said:
I won't be able to experiment for a couple of weeks. I do know that I've wiped my phone four times or more in the last week with the 4.3 and 4.4 factory images and either manually or using one of the tool kits have added TWRP custom recovery and rooted the phone. Each time trying to flash a ROM it would result in a failure.
Next time I get the chance, I'll give your suggestion a shot and let you know. Are there logs I can capture that might prove useful?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
na. really the only 100% working fix is to delete the recovery, then reflash.

simms22 said:
na. really the only 100% working fix is to delete the recovery, then reflash.
Click to expand...
Click to collapse
So essentially I've done that with each factory image installed, correct? I'll have to read up on ADB and Fastboot to get the commands to remove the existing recovery. Will be a good way to kill some time (such the life I lead, being envious is not good for your soul)...
Sent from my Nexus 4 using Tapatalk

ph37rd said:
So essentially I've done that with each factory image installed, correct? I'll have to read up on ADB and Fastboot to get the commands to remove the existing recovery. Will be a good way to kill some time (such the life I lead, being envious is not good for your soul)...
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
no, you just flashed the next version of the recovery over the last. occasionally, something doesnt want to update in the partition, so clearing the previous recovery before flashing the new one will take car of it.

simms22 said:
no, you just flashed the next version of the recovery over the last. occasionally, something doesnt want to update in the partition, so clearing the previous recovery before flashing the new one will take car of it.
Click to expand...
Click to collapse
OK that confuses me. If using fastboot to place a new boot loader, radio, recovery and ROM are onto the phone and I have to 'fastboot flash recovery recovery.img' to replace the stock recovery that doesn't wipe out the stock recovery? Fabulous sentence structure.
Sent from my Nexus 4 using Tapatalk

[Q] Can I flash twrp via my current recovery? (Cwm)

Okay so today I ran into a problem trying to flash 3.99 rc2 paranoid android via clockworkmod I didn't see that flashing it using cwm would cause baseband issues and now I have to flash the 4.3 radio but apperantly I need twrp for that so since I do not have a computer and goomanager won't download the latest twrp I was wondering if I can just download the latest version of twrp and flash it using clockwork mod? I know it sounds weird haha flashing a recovery via a recovery but anyways a quick reply would be thankfull
Sent from my Nexus 4 using xda app-developers app

i never use a pc for android, use recovery tools from the market and choose twrp, download and it will reboot to flash, thats it. very convenient

Use this app and choose your recovery tool that you want.
Recovery Tools. look for it in the market.
I'm using this tool and it's great.

Hey thanks guys that really helped! did and now have twrp although it didn't download the latest one it downloaded 2.6.3.0 but still works!
Sent from my Nexus 4 using xda app-developers app

OsSkates1996 said:
Okay so today I ran into a problem trying to flash 3.99 rc2 paranoid android via clockworkmod I didn't see that flashing it using cwm would cause baseband issues and now I have to flash the 4.3 radio but apperantly I need twrp for that so since I do not have a computer and goomanager won't download the latest twrp I was wondering if I can just download the latest version of twrp and flash it using clockwork mod? I know it sounds weird haha flashing a recovery via a recovery but anyways a quick reply would be thankfull
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Its not weird man its a zip file you should download and flash it like you would flash anything else. Simple no need to over think it man just go to TWRP thread and download the zip file of the latest which is 2.6.3.3 I believe. Also the thread name has a paperclip at the end of it so click on it and you will see all attached files within the thread. There you will see all of the TWRP zips... Download latest one and thats it..
Also are you sure you had the latest CWm since I find it hard to believe there is a version that wont work

playya said:
Its not weird man its a zip file you should download and flash it like you would flash anything else. Simple no need to over think it man just go to TWRP thread and download the zip file of the latest which is 2.6.3.3 I believe. Also the thread name has a paperclip at the end of it so click on it and you will see all attached files within the thread. There you will see all of the TWRP zips... Download latest one and thats it..
Also are you sure you had the latest CWm since I find it hard to believe there is a version that wont work
Click to expand...
Click to collapse
Yes I'm %100 positive I had latest and the only version of cwm that would not cause issues was the version right before the 6.0.4.3 which I believe is the number if I remember correctly but all is good now I used that app I was recommended and flashed twrp using that and flashed the radio and am now on beanstalk with no problems but I will flash the latest version of twrp now that I know I can haha thanks for the info on that
Sent from my Nexus 4 using xda app-developers app

[Q] Recovery Mode

Long story short: I want cm on the S4 after using it on the HD+, but CWM isn't booting up.
I've seen problems regarding simply accessing the recovery mode like needing to use the buttons twice after powering on, but the thing is that after getting to do this, for whatever reason, the phone boots up with the default recovery option (Android system recovery <3e>).
Some background on the phone would be that it is rooted, about one year ago when I bought it. I fear that I might have flashed something back then, but I don't have any of the files. To add, I sadly don't remember the method, but I can give some device info:
View attachment 2870784
The next and last thing would be that ROM manager says I have CWM installed and even with the reboot option of the app, it takes me to the default recovery.
View attachment 2870785
Any similar experiences on how to deal with this? I'd at least have a means to access CWM.

Are you sure you're still rooted? If you're not sure I would re-flash root using motochopper
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Are you sure you're still rooted? If you're not sure I would re-flash root using motochopper
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Well, yes. I do have things like tethering and su on the phone, plus root checking apps from the store say its rooted.

ROM Manager is crap. It says I have CWM 6.0.4.7 installed but when I boot into recovery it says 6.0.4.4.
I've been looking for a way to manually install the latest Touch version of CWM but so far I've come up with nothing. Maybe if you flash TWRP (via Goo Manager app) you'll then be able to flash CWM back over it. Sometimes it takes 2 or 3 tries for Goo Manager to successfully flash the recovery.

Even better, I figured out how to flash CWM touch. The loki_tool downloaded here can patch any compatible img file and then flash your recovery directly.
https://github.com/djrbliss/loki
The readme was very helpful.

snakecharmer23 said:
Even better, I figured out how to flash CWM touch. The loki_tool downloaded here can patch any compatible img file and then flash your recovery directly.
The readme was very helpful.
Click to expand...
Click to collapse
Thanks for the link! It was really easy to follow.

Another "software not authorized by ATT" plead for help

Reaching out for some help... I'm stuck at this point. I need to get a recovery working. Preferably cwm at this point. All other questions I found when searching were users on previous versions of Android and honestly the whole baseband build thing confuses it. I can still boot to the normal phone and use it as usual but I do want to get a working recovery again.
Device: I337 / Rooted
Android: 4.4.4
Baseband: I337UCUAMF3
Rom: Cyanogenmod Nightly 8/6/14
Kernel: 3.4.0-cyanogenmod-g433243c / [email protected] #1 / Wed Aug 6 2014
I was on TWRP and tried flashing to CWM with Rashr. I did this because TWRP was not compatible with the new CM nightlies.
Recovery now only boots to: "System software not authorized by ATT has been found on your phone"
Is there a way I can get a working recovery going now?
Help is appreciated.
Thanks.

did you flash loki-doki after CWM and before reboot?
I never had issues with TWRP 2.5.0.2 and have latest Cm M9--

rugmankc said:
did you flash loki-doki after CWM and before reboot?
I never had issues with TWRP 2.5.0.2 and have latest Cm M9--
Click to expand...
Click to collapse
No I'm totally unfamiliar with Loki as I've never had to deal with it. I never had any issues before this. I guess the TWRP that I had it was already built in?
Is that still an option now? ROM Manager is showing that I have both CWM and TWRP on my phone. I'd be fine with getting rid of TWRP and just using CWM. If I reload CWM in ROM Manager could I then do Loki?
Thanks.

RiG14LA said:
No I'm totally unfamiliar with Loki as I've never had to deal with it. I never had any issues before this. I guess the TWRP that I had it was already built in?
Is that still an option now? ROM Manager is showing that I have both CWM and TWRP on my phone. I'd be fine with getting rid of TWRP and just using CWM. If I reload CWM in ROM Manager could I then do Loki?
Thanks.
Click to expand...
Click to collapse
You're probably going to have to use Odin and start all over again. If you're able to use twrp or cwm recovery you're on mdl firmware. You can get that at sammobile.com. Extract it with 7-zip or winrar and use the .tar.md5 in Odin. You'll have to re-root and put your custom recovery back on. Back everything up before starting as Odin will wipe your device.
Sent from my Nexus 5 using XDA Free mobile app

Here is the loki zip flashable in recovery.
https://www.dropbox.com/sh/yhrq0tia8512rj9/AAB3C9mLkMe_WeHQgP4QHiKra/loki-doki.zip
I haven't used or kept up with CWM for several years. So, don't know if it loki's a rom/kernel if dev hasn't loki'd rom/kernel.
You can Google loki-doki. But it is how we on MDL can flash custom roms/recoveries/kernels and those above MDL can't. It bypasses Sammy's security and allows kernel to flash. Newer builds are locked down and no similar exploit has been developed yet for them.
Once you get sorted as jd mentioned, use it right before you reboot. Doesn't hurt even if rom/kernel is not loki'd.
:good::good:
BTW, you didn't have issues before bc most att roms esp TW are loki'd--

jd1639 said:
You're probably going to have to use Odin and start all over again. If you're able to use twrp or cwm recovery you're on mdl firmware. You can get that at sammobile.com. Extract it with 7-zip or winrar and use the .tar.md5 in Odin. You'll have to re-root and put your custom recovery back on. Back everything up before starting as Odin will wipe your device.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
rugmankc said:
Here is the loki zip flashable in recovery.
https://www.dropbox.com/sh/yhrq0tia8512rj9/AAB3C9mLkMe_WeHQgP4QHiKra/loki-doki.zip
I haven't used or kept up with CWM for several years. So, don't know if it loki's a rom/kernel if dev hasn't loki'd rom/kernel.
You can Google loki-doki. But it is how we on MDL can flash custom roms/recoveries/kernels and those above MDL can't. It bypasses Sammy's security and allows kernel to flash. Newer builds are locked down and no similar exploit has been developed yet for them.
Once you get sorted as jd mentioned, use it right before you reboot. Doesn't hurt even if rom/kernel is not loki'd.
:good::good:
BTW, you didn't have issues before bc most att roms esp TW are loki'd--
Click to expand...
Click to collapse
Thanks guys.
So it seems like I have no choice but to start over completely since I can't get into recovery to flash Loki. Which sucks since I have no idea about the current procedures for rooting and getting recovery. It was pretty messy when I first got my S4 last year.
I almost want to just leave my phone as is and wait to buy a nexus 6 :cyclops:

RiG14LA said:
Thanks guys.
So it seems like I have no choice but to start over completely since I can't get into recovery to flash Loki. Which sucks since I have no idea about the current procedures for rooting and getting recovery. It was pretty messy when I first got my S4 last year.
I almost want to just leave my phone as is and wait to buy a nexus 6 :cyclops:
Click to expand...
Click to collapse
It's not so bad. Use Odin to get your system up and running again. Then use this to root and get a custom recovery on http://forum.xda-developers.com/showthread.php?p=41892523
Sent from my Nexus 5 using XDA Free mobile app

Yes it just takes studying. I used Mottochopper also, very good. When you are done, I do recommend TWRP 2.5.0.2. Also, if you are flashing kernels always wipe caches before rebooting.
Sent from my SGH-I337 using Tapatalk

if it has mf3 baseband i'm pretty sure you will have to use safestrap and a touchwiz rom. no cyanogen or cwm or twrp.

OP has MDL build his radio "baseband" is mf3. He can flash any radio he wants after rooted.
Sent from my SGH-I337 using Tapatalk

iateshaggy said:
if it has mf3 baseband i'm pretty sure you will have to use safestrap and a touchwiz rom. no cyanogen or cwm or twrp.
Click to expand...
Click to collapse
He's using twrp and cm. Baseband is most likely from the cm version here's on.
Sent from my Nexus 5 using XDA Free mobile app

rugmankc said:
Yes it just takes studying. I used Mottochopper also, very good. When you are done, I do recommend TWRP 2.5.0.2. Also, if you are flashing kernels always wipe caches before rebooting.
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
I just remembered I made a recovery backup in Rashr before trying to go to CWM. So I restored that in Rashr and am now back on TWRP 2.7.0.1.
This is great but I still want to be able to flash the new CM11 nightlies and TWRP isn't compatible with CMs new kernel.
Are you guys familiar with this situation?

RiG14LA said:
I just remembered I made a recovery backup in Rashr before trying to go to CWM. So I restored that in Rashr and am now back on TWRP 2.7.0.1.
This is great but I still want to be able to flash the new CM11 nightlies and TWRP isn't compatible with CMs new kernel.
Are you guys familiar with this situation?
Click to expand...
Click to collapse
When did that start. As I said I flashed M9 a few days ago with 2.5.0.2.
Sent from my SGH-I337 using Tapatalk

rugmankc said:
When did that start. As I said I flashed M9 a few days ago with 2.5.0.2.
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
The 8/8 or 8/9 nightly.
Another question...what would happen if I flash CWM with TWRP? Would CWM just over write TWRP and be my active recovery?

RiG14LA said:
The 8/8 or 8/9 nightly.
Another question...what would happen if I flash CWM with TWRP? Would CWM just over write TWRP and be my active recovery?
Click to expand...
Click to collapse
Yes I change recoveries as needed but have been on current for awhile. Read up on flashing CWM to be sure you know of any issues and exact steps. If it is a zip no issues should be encountered. Never liked to use Rom MGR.
Sent from my SGH-I337 using Tapatalk

Read last 7 pages of cm11 thread. They talked about changing updater script of cm rom. If you flash CWM recovery zip remember to flash loki before rebooting. Uncheck sig check in twrp before flashing CWM. You can't restore twrp nandroid with CWM and vice versa. They list a flashable CWM zip there too.
Sent from my SGH-I337 using Tapatalk
---------- Post added at 11:42 PM ---------- Previous post was at 11:39 PM ----------
Also, My M9 milestone seems to be last stable build--many reboots etc on recent nightlies. But, that is part of the game with nightlies. As I "age" I need more stable roms--less stress--
---------- Post added at 11:43 PM ---------- Previous post was at 11:42 PM ----------
RiG14LA said:
I just remembered I made a recovery backup in Rashr before trying to go to CWM. So I restored that in Rashr and am now back on TWRP 2.7.0.1.
Click to expand...
Click to collapse
Oh, the salvation of nandroids--:good::good:
I used an app like Rashr long time ago, but didn't like it. Maybe not a bad idea to have it and keep a backup just in case--