Hope some of these amazing minds at xda can help.
When i install a custom recovery image from rom manager or my computer, it works fine. In the recovery, i can successfully restart the recovery in the advanced menu. But when i reboot after installing, it dissapears.
It also does this even if i havent entered the custom recovery after i install/flash the recovery image and do a reboot. There is something going on at bootup, but im not sure what it is. My guess is the android system denies the recovery image because it does not think it has the privelages- though im probably wrong.
I have tried to do a nandroid restore and a factory reset, but it still wount work. i have tried re root twice and still nothing. But a thing i noticed when doing a nandroid restore is that it fails to find a file and skips it.
Please help, and if you cant.... try. I AM DESPERATO!
Related
After installing openscript recovery TWRP 2.2.1 via goo manager and then realize the recovery could not mount system or install any zip. I then try to revert back to team rogue xm recovery 1.5.0 with sucess by installing the recovery zip in TWRP (although some error due to system unable to mount). Got pretty happy that I'm able to revert back to rogue recovery but now faces this STUCK in automatic rebooting to recovery everytime I've try to reboot. I wipes everything completed 3x and install new rom but can't ever boot pass the recovery. I have yet to revert back to stock via softbrick method and figure I should ask for help first before unroot and unlock to start from scratch. below is an image of when ever I booted my xoom. Thanks for any help.
Oh, I've search first but noon seem to have the same problem as mine.
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
Using ROM Manager and the latest version of CWM I tried installing today's (12-08) nightly build of CM11 to try it out. After doing a complete backup and then wipe data/cache the install failed. I'm not sure why but it said it was aborted and to check log and report the error to ROM Manager.
After that it asked if I wanted to reboot and I wanted to make sure I restored from my backup so I backed out of the screen but then it booted up on its own. It did not get past the S3 loading screen with the CM Android/alien guy it just turned off, back to that screen again and then back into recovery.
At this point I went to recover from my backup file and it said MD5 mismatch and won't load. I've since tried wiping data/cache/dalvik cache all manually and then boot up, or wipe everything and try to install the rom again... every time it just loops back to recovery mode. The last time I tried installing the rom again it told me I might have lost root access and asked if I wanted to repair it... I'm not sure what that means.
Any suggestions? I am lost at this point. I have no experience with ADB (I'm not sure if that's my only option) but I've used ODIN mode a few times. Easiest solution would be best.
bejahu said:
Using ROM Manager and the latest version of CWM I tried installing today's (12-08) nightly build of CM11 to try it out. After doing a complete backup and then wipe data/cache the install failed. I'm not sure why but it said it was aborted and to check log and report the error to ROM Manager.
After that it asked if I wanted to reboot and I wanted to make sure I restored from my backup so I backed out of the screen but then it booted up on its own. It did not get past the S3 loading screen with the CM Android/alien guy it just turned off, back to that screen again and then back into recovery.
At this point I went to recover from my backup file and it said MD5 mismatch and won't load. I've since tried wiping data/cache/dalvik cache all manually and then boot up, or wipe everything and try to install the rom again... every time it just loops back to recovery mode. The last time I tried installing the rom again it told me I might have lost root access and asked if I wanted to repair it... I'm not sure what that means.
Any suggestions? I am lost at this point. I have no experience with ADB (I'm not sure if that's my only option) but I've used ODIN mode a few times. Easiest solution would be best.
Click to expand...
Click to collapse
I had the exact same issue when trying to flash that same CM11 nightly build but with TWRP...
I just pulled the battery took my SD card out and reinserted it and I just kept booting into recovery and turning the phone off until it let me reflash a rom or backup. Obviously this isnt the most legitimate solution but that could work for you! It did for me!...
This could have been caused by needing an update of CWM or TWRP to better support 4.4 perhaps?
Badouken said:
I had the exact same issue when trying to flash that same CM11 nightly build but with TWRP...
I just pulled the battery took my SD card out and reinserted it and I just kept booting into recovery and turning the phone off until it let me reflash a rom or backup. Obviously this isnt the most legitimate solution but that could work for you! It did for me!...
This could have been caused by needing an update of CWM or TWRP to better support 4.4 perhaps?
Click to expand...
Click to collapse
I tried that to no avail. I unfortunately had to revert to stock unrooted via ODIN mode and it got me to boot back up. I can just reroot now. Luckily I made a backup with Titanium and uploaded it to my Google Drive.
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.
Hey guys. I'm a bit of a newbie at androids. I bought a Moto G, and I decided to root it.
I realized that the android was not unlocked, so I went through a small progress to try get it unlocked so I could install a custom recovery. I chose CWM.
I went through a tutorial on how to install CWM, and I installed it. I used the MotoTool to push Superuser to my android, and was able to install the zip.
It all went wrong when I tried to exit out of CWM.
I selected "Reboot" and it loaded the screen up to CWM again...a bit odd. So I'm trying to reboot so I can use my phone properly, and nothing is working.
What I've tried :
-----> Clearing dalvik cache and cache with CWM -
I tried this and it still didn't work.
-----> Loading into my AP Fastboot with CWM and trying to power off and on from there
Still didn't work and loaded into CWM.
----->Flashing my bootloader
Made it worse. I can't even power up my phone anymore.
In conclusion, my phone is hard-bricked, and I can't even power it up. If anyone has any solutions, it would be extremely helpful. Please feel free to comment or reply if you need more info about my device.