I dropped skyraider 3.0 onto my phone and now the phone wont take any other rom. I tried cm6, virtuous, and the leaked 2.2 stock rom and none of them get past the boot animation. After a few tries skyraider decided that it was going to nuke my rom manager which now force closes like a mother ****er. Every time I go to open it it instantly force closes.
I tried the guide to downgrade from the 2.2 ota to 2.1 but that **** didn't work, I assume because the process was made for an unrooted 2.2 stock rom. So, does anyone have any ideas how I can get this ****ing skyraider off of my phone or how I can get back to factory 2.2/2.1 so I can start over again?
inb4 nandroid backup, didn't back up because I loaded SR onto the phone once I rooted it so my nandroid backup is skyraider.
Are you wiping data and cache partitions in recovery before flashing?
Sent from my ADR6300 using XDA App
yes i am, why in the **** can't i just say yes to this question and post it? When I do it says that my message entered is too short... this should do.
Such language is uncalled for on this forum.
Sorry, I'll watch the vulgar language. Anyway, I finally got my phone to load the leaked 2.2ota but I still have root access and what have you but I can't get any other Rom to load. When I try to download and apply a Rom from Rom manager instead of booting into recovery it boots to a screen with a little android robot with a error triangle. If I tap the power button recovery comes up but it says that it failed to read update.zip. any ideas on how to revert to uprooted 2.1 so I can just start over to how to get one of these other roms working.l?
dontcallmepete said:
Sorry, I'll watch the vulgar language. Anyway, I finally got my phone to load the leaked 2.2ota but I still have root access and what have you but I can't get any other Rom to load. When I try to download and apply a Rom from Rom manager instead of booting into recovery it boots to a screen with a little android robot with a error triangle. If I tap the power button recovery comes up but it says that it failed to read update.zip. any ideas on how to revert to uprooted 2.1 so I can just start over to how to get one of these other roms working.l?
Click to expand...
Click to collapse
Check out this post. http://forum.xda-developers.com/showthread.php?t=768295
I tried it and it didn't work, everything went fine until I tried to flash mtd.img with the adb shell. When I jump into adb shell from my windows machine it comes back with $ user control rather than #, which isn't root access so it wouldn't let me flash the image. Which sucks because the phones rooted :/
So it looks like i'm back to square one, anyone know how I can unroot?
Hello all,
I'm sorry if this is the wrong place to post, but I thought I'd give it a try.
I own a Desire myself and the rooting / flashing a new ROM process was pretty easy so I thought I can help a friend out and put a custom ROM on his new Motorola Defy. Turns out I sucked at it. *ahem*
Right, the problem is as follows:
I got the brand new device, used SuperOneClick to root it, tried ROM Manager to install ClockworkMod CWM and it said Defy isnt supported in ROM Manager. So I google'd and it came up with this [german] (not allowed to post links), which basically gave me CWM.zip with an apk in it, which installed "System Recovery" and gave me the option to "Install System Recovery" and Reboot into Recovery - successfully bootet into CWM 2.5.1.8 , alright.
I did a nandroid backup and then wiped everything, selected the ROM on the sdcard to install MIUI 1.9.9 ROM, which worked fine. After it finished installing, I chose reboot system now.
Now what happens is:
I try to boot normally: I Only get the Motorola logo on screen and nothing ever happens
I boot into recovery like I used to know (Power + VolDown), I get a screen with a yellow exclamation mark and the android robot on it. Figured out that both volume keys take me to Android System Recovery Utility. I wiped everything again, that didn't help. I tried giving it the CWM.zip as an update.zip but it refuses that because it's apparently not properly signed. I can't do anything else in there. It also gives me a couple of errors "E: Can't moint CACHE:recovery/command" (/caller, /log)
Please, can anybody help me out? It seems I can't boot any ROM from it right now, nor do I know how to get CWM back in to at least even restore the nandroid backup (which I still have).
I would love to, at the end of the day, have a rooted device with CWM running and MIUI 1.9.9. If that doesn't work, at least can I restore the CWM backup somehow to have to stock ROM running?
I would really appreciate any help very much and realize I may be in over my head, it just seemed too easy on the Desire I previously used. Thanks a lot!
I am a relatively newbie at rooting, but hopefully I am not as hosed as I think I am. Using the Zedomax Epic Touch Kernel method (http://www.youtube.com/watch?v=2qVcB9ktEwQ&feature=related), I rooted my Sprint SGS2. However, had trouble flashing Clockwork Mod. Recovery 3e requires signature verification for flashing external files, so it's puking when I try. Throws error can't read file signature, hard stop. SO, had the brilliant (?) idea to try replacing the ROM with Max's new one: SPH-D710_Zedomax_EpicTouchKernel-v2.tar. Flashed that, and now when I boot into recovery it gives me error (exclamation point inside triangle w android dude). However, when I then hold down power button for several seconds it actually _then_ goes into Clockwork Mod (orange menu). So something not quite right, plus install is a bit buggy (sometimes phone calls don't release when hang up and need to reboot phone, battery draining way too fast), so, should I try something from the ClockworkMod Recovery, have I gotten around my signature verification issue, how far do I need to backup to unwind this? Want to get a full Recovery going so I can start flashing ROMs. Big thanks to whoever thinks they can help...
Axilarry said:
I am a relatively newbie at rooting, but hopefully I am not as hosed as I think I am. Using the Zedomax Epic Touch Kernel method (http://www.youtube.com/watch?v=2qVcB9ktEwQ&feature=related), I rooted my Sprint SGS2. However, had trouble flashing Clockwork Mod. Recovery 3e requires signature verification for flashing external files, so it's puking when I try. Throws error can't read file signature, hard stop. SO, had the brilliant (?) idea to try replacing the ROM with Max's new one: SPH-D710_Zedomax_EpicTouchKernel-v2.tar. Flashed that, and now when I boot into recovery it gives me error (exclamation point inside triangle w android dude). However, when I then hold down power button for several seconds it actually _then_ goes into Clockwork Mod (orange menu). So something not quite right, plus install is a bit buggy (sometimes phone calls don't release when hang up and need to reboot phone, battery draining way too fast), so, should I try something from the ClockworkMod Recovery, have I gotten around my signature verification issue, how far do I need to backup to unwind this? Want to get a full Recovery going so I can start flashing ROMs. Big thanks to whoever thinks they can help...
Click to expand...
Click to collapse
Try the Epic Touch forum, you may have better luck.
My unrooted, stock Nexus 7 was on 4.4. I received an OTA notification about 5.0.1 so accepted the upgrade. After the reboot and seeing the Android with the open stomach, it fails with Error against the Android. All I can do is long power off/volume up to power off and then power on again. It then reverts back to 4.4.
After about an hour I received another 5.0.1 update, went the same process and received the same error.
Does anybody know what that could be? I guess I could factory reset the device there is nothing on the tablet that hasn't been saved in my Google account anyway.
Thanks
Wanted to say I experienced the same thing earlier today, except I didn't get an immediate second chance at the OTA. I have the wifi-only version of the N7 2013, and it is also not rooted.
Browsed around the net and various places to see if others had this issue, but no luck. Not really sure what the problem is unless the download got messed up somehow?
Same issue here. Download the update. It shows verified. Reboots, starts to flash and then the android error
Reboot and it is still 5.0
Happy to report that when I got another crack at the ota the update went fine. Still confused as to what could've caused the problem though.
Well it killed my N7 it seems. Got the error message then shut itself down. Now it won't boot up no matter what I do. Any ideas?
My update just stays in the notification area. After the failure I just power the tablet off with long press of the power button and volume up.
I am stock, rooted and unlocked. I used the WUGS toolkit to flash the stock recovery assuming that this is all that was necessary for the OTA to be recognized and accepted. After flashing back to stock recovery, I rebooted the device and told the OTA to update. It starts going through the process and dies with "Error!" and reboots back into 5.0. I tried using the WUGS toolkit to ADB sideload, but I have not been able to get it to work. At some point, it actually got into the Stock Recovery, but ADB wasn't able to contact the device (that only happened once). Every other time, it goes through the script and shows the Android on it's back with the exclamation mark, and below it says "no command."
The device works, but it's frustrating. I wish there was just a way to fastboot the OTA, or just do it via TWRP.
I'm anxious to hear how others work through this, as it appears that I'm not the only one.
kendoori said:
I am stock, rooted and unlocked. I used the WUGS toolkit to flash the stock recovery assuming that this is all that was necessary for the OTA to be recognized and accepted. After flashing back to stock recovery, I rebooted the device and told the OTA to update. It starts going through the process and dies with "Error!" and reboots back into 5.0. I tried using the WUGS toolkit to ADB sideload, but I have not been able to get it to work. At some point, it actually got into the Stock Recovery, but ADB wasn't able to contact the device (that only happened once). Every other time, it goes through the script and shows the Android on it's back with the exclamation mark, and below it says "no command."
The device works, but it's frustrating. I wish there was just a way to fastboot the OTA, or just do it via TWRP.
I'm anxious to hear how others work through this, as it appears that I'm not the only one.
Click to expand...
Click to collapse
Tried sideloading the factory image?
Sent from my Nexus 5 using XDA Free mobile app
Since my N7 is a secondary device (my main device is a N5 which received the Lollipop upgrade fine), I might just leave it on KitKat rather than muck around with sideloading Lollipop. KitKat works fine for me at the moment. But it's really annoying that a stock N7 cannot get an OTA upgrade and goes into an Android error state.
I was on 5.0 rooted with TWRP and got the same error trying to take the OTA. So I downloaded the rooted rom found here http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22c-t2960745 , used Wugfresh's NRT 1.9.9 to update the bootloader, and then dirty flashed the 5.0.1 rom with TWRP. Painless and fast with no loss of data or anything.
Same problem! I managed to workaround the issue by using fastboot replacing system.img boot.img recovery.img with stock ones!
chrismast said:
Tried sideloading the factory image?
Click to expand...
Click to collapse
Are you suggesting that I blow away what's installed and just update by doing a fresh install? would prefer to not do that.
I did download razor-lrx21p-factory-ba55c6ab.tgz (the 5.0 factory image) and extract the recovery.img for it, and fastboot flashed it, and the no matter what I end up in the Recovery bootloop with the android on it's back and exlamation point and "No command."
kendoori said:
Are you suggesting that I blow away what's installed and just update by doing a fresh install? would prefer to not do that.
I did download razor-lrx21p-factory-ba55c6ab.tgz (the 5.0 factory image) and extract the recovery.img for it, and fastboot flashed it, and the no matter what I end up in the Recovery bootloop with the android on it's back and exlamation point and "No command."
Click to expand...
Click to collapse
If I am not wrong, there is a way of flashing the factory image without wipe by modifying one of the scripts, never did it though myself.
Sent from my Nexus 5 using XDA Free mobile app
Turns out I was using the wrong key sequence for Recovery to get past that screen. Holding down Vol Up + Power for 3 seconds, then just pressing Power gets you to the right place. Am still having issues with OTA, as the system believes something was altered (install-recovery.sh). Others are saying that the way to do this is as described here: http://forum.xda-developers.com/showpost.php?p=57271130&postcount=423
kendoori said:
Turns out I was using the wrong key sequence for Recovery to get past that screen. Holding down Vol Up + Power for 3 seconds, then just pressing Power gets you to the right place. Am still having issues with OTA, as the system believes something was altered (install-recovery.sh). Others are saying that the way to do this is as described here: http://forum.xda-developers.com/showpost.php?p=57271130&postcount=423
Click to expand...
Click to collapse
jep, that's what I was saying earlier: factory image. For the 5.0.1 update you only need system.img and boot.img, at least that way it worked for me and my N7 2013 is running fine so far.
I dont get 5.0 on my nexus 7 2013, wifi, 32 Gb(flo, ktu84p)
I had stock rooted Rom, u Used tweaks like softkeiz etc. then I unrooted, locked boot loader and flashed stock recovery. Android lollypop rollout was about 2 months ago, but I don't get 5.0 ota. Now I'm running 4.4.4 stock rom , locked boot loader and I unrooted it with super user unroot option. Can somebody help me why I don't get my ota?? Thanks ^^
I know that's wrong thread, I didn't find thread for my question .
I just got my update!!!!!
German8835 said:
I had stock rooted Rom, u Used tweaks like softkeiz etc. then I unrooted, locked boot loader and flashed stock recovery. Android lollypop rollout was about 2 months ago, but I don't get 5.0 ota. Now I'm running 4.4.4 stock rom , locked boot loader and I unrooted it with super user unroot option. Can somebody help me why I don't get my ota?? Thanks ^^
I know that's wrong thread, I didn't find thread for my question .
Click to expand...
Click to collapse
Oh man! It's crasy, I was waiting so long, and exactly on this day when I write to thread I get my update!
EDIT: Never mind. I tried to do it via sideload, and it complained that the /System was too full. I rebooted, compared it to another Nexus 7, and the size was the same and free space was the same (and the other one updated fine). for the heck of it, I tried sideloading again, this time I formatted the cache first (no reason, just a thought) and that time it sideloaded correctly. So I'm up to date now... Weird.
I have the same issue. did a factory image install to 5.0. Now I get the update notification for 5.0.1 (as expected).
When I try to install it, it reboots, then I get "error" - have tried 3 times now. A reboot gets me back in the tablet, but am still at 5.0. This is my kid's tablet, so I have no need to root it or install a new rom, just want the dumb update to work correctly...
Jason
JasonJoel said:
EDIT: Never mind. I tried to do it via sideload, and it complained that the /System was too full. I rebooted, compared it to another Nexus 7, and the size was the same and free space was the same (and the other one updated fine). for the heck of it, I tried sideloading again, this time I formatted the cache first (no reason, just a thought) and that time it sideloaded correctly. So I'm up to date now... Weird.
I have the same issue. did a factory image install to 5.0. Now I get the update notification for 5.0.1 (as expected).
When I try to install it, it reboots, then I get "error" - have tried 3 times now. A reboot gets me back in the tablet, but am still at 5.0. This is my kid's tablet, so I have no need to root it or install a new rom, just want the dumb update to work correctly...
Jason
Click to expand...
Click to collapse
That is indeed strange...If you are pure stock it should work I guess? You could still try to sideload the 5.0.1 as well (did the same as I did not want to wait for OTA). You can do it without full wipe, just wipe cache in the process. (You need only to flash system and boot.img, wipe cache, reboot). Nevertheless let me know if you get the "error" solved, would be interested to know.
newkydawg said:
I was on 5.0 rooted with TWRP and got the same error trying to take the OTA. So I downloaded the rooted rom found here http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22c-t2960745 , used Wugfresh's NRT 1.9.9 to update the bootloader, and then dirty flashed the 5.0.1 rom with TWRP. Painless and fast with no loss of data or anything.
Click to expand...
Click to collapse
I was skeptical but this worked when I was having a similar problem to the OP Thanks. I have no idea how 5.0.1 is different though.
So the old ROM I was on (a super outdated Android Revolution) needed to be updated because my battery was draining a lot and I figured I would update everything. Apparently I flashed a bad or wrong version of TWRP, so I can't get into recovery. It just sits there trying to get into recovery but it keeps failing. Then I tried using MultiRom recovery and installing that through the app in the play store. Now my phone won't go into recovery and just boot loops. I can get into the HBOOT menu but I can't get into recovery or boot the device at all. Does anyone have any ideas to get a working recovery or working ROM? I already backed up my pictures and videos and stuff, but I forgot to transfer my titaniumbackup files I've been trying to look around and see how to fix it but I don't want to do something that will cause more damage than I've already done. I did all this to update my firmware so that I can use the newer ROMs. Anyway if anyone has any ideas I'm all ears.
Thanks in advance.
You didn't mention whether or not you are S-off and/or bootloader unlocked.
Since you already have a custom ROM, you must have unlocked your bootloader at some point, so if it is STILL unlocked, just reflash the correct recovery from fastboot. If it is not, unlock it with HTCdev first, then reflash the correct recovery.
Alternately, if you just want the phone fixed, you can always re-run the AT&T RUU - though that will trash any files you have on the phone.
Yeah that's what I did yesterday thanks for the response!