Related
I rooted my HTC Desire CDMA from USCC okay, flashed a Froyo ROM with USCC stuff, and everything was okay. I made a nandroid backup, flashed CyanogenMod 7 RC4 and it seem to work okay, except I was having trouble entering my password when checking voice mail. Anyway, I decided to go back to Froyo. I used ROM Manager to restore the backup and got into ClockworkMod. However, none of the options work. If I go down to recovery, I go to the next screen, but no matter which option I select I end up with a black screen and nothing happens! I can't restore my backup! If I just try to press power on, I end up with the blue CyanogenMod screen and the arrow just goes round and round. Nothing happens. Please, if anyone has any suggestions, it would be greatly appreciated.
I remember hearing that because CM7 is a Gingerbread mod, it must use ClockworkMod v3 and to go back to your Froyo backup you'll need to downgrade to Clockwork Recovery 2.x. I'm not sure if things has changed, though, this was what I read a month or two ago.
Are you by any chance able to fastboot?
Reflash your CWM (if you are using NAND version) or get it again on your SD (if your are using SD version).
The problem is I can't do anything in ClockworkMod (version 2.5). Every option I select gives me a blank screen! I made a nandroid backup before flashing CyanogenMod, but I have no way of getting to my backup if I can't use ClockworkMod. Also, if I try to boot the phone, i just get the CyanogenMod 7 startup screen with the arrow going round and round. It will still be there 30 minutes later. I have to do a battery pull to start over with anything.
I was able to boot my phone after wiping all user data. I would like to use my nandroid backup to return to the previous ROM, but clockworkmod doesn't seem to work. I tried reflashing it in ROM manager and it only downloads a second or so and isn't really doing anything. I'm wondering if clockworkmod is defective. Is there any other way to flash it again without using ROM Manager?
If you are able to fastboot, you could try to restore a nandroid by flashing three files (boot.img, system.img, data.img) from your nandroid backup using:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata data.img
Disclaimer: I've not actually tried this procedure before! I got this info from here
You could use a similar procedure to flash a new ClockworkMod since your recovery may be corrupted: fastboot flash recovery recovery-clockwork-3.0.0.5-vision.img
You can download the image from Koush's website, under HTC G2.
This happened to me yesterday trying out the Alpha Build for the Fascinate. I was getting a dev block error and datadata would not mount. I had to go back to stock on heimdall. I don't know if this helps for your phone, but maybe somone with more knowledge can tell you if this may be happing to you and what the fix is, if that's not a fix for you.
I was running 3.0.1 unlocked/rooted, Tiamat's 1.4.1 kernel. I followed the steps to update to 3.1 from here, and had no issues what so ever. This was earlier this week, and today I was going to run fix permissions in recovery. I used Quick Boot (also tried Reboot to Recovery in ROM Manager) to boot to recovery, and I got to the Android with the exclamation point...
I tried sending the modified 3.0.2.8 recovery listed in the Dev Forums using fastboot commands, and everything went smooth with no errors, but still got the Android/exclamation point.
I tried reflashing recovery via ROM Manager, and it wouldn't pop up anything, so I uninstalled/reinstalled, and the flash of recovery worked. Boom! Recovery is back! So I can do what I need (run fix permissions), and rebooted the device.
I try to reboot into Recovery again, back to Android with exclamation point. Any thoughts here as to why I must do this, and thoughts to what I can try to make Recovery "stay"?
Thanks!
RMarkwald said:
I was running 3.0.1 unlocked/rooted, Tiamat's 1.4.1 kernel. I followed the steps to update to 3.1 from here, and had no issues what so ever. This was earlier this week, and today I was going to run fix permissions in recovery. I used Quick Boot (also tried Reboot to Recovery in ROM Manager) to boot to recovery, and I got to the Android with the exclamation point...
I tried sending the modified 3.0.2.8 recovery listed in the Dev Forums using fastboot commands, and everything went smooth with no errors, but still got the Android/exclamation point.
I tried reflashing recovery via ROM Manager, and it wouldn't pop up anything, so I uninstalled/reinstalled, and the flash of recovery worked. Boom! Recovery is back! So I can do what I need (run fix permissions), and rebooted the device.
I try to reboot into Recovery again, back to Android with exclamation point. Any thoughts here as to why I must do this, and thoughts to what I can try to make Recovery "stay"?
Reflash cmw afterward and it should stay.
Thanks!
Click to expand...
Click to collapse
Use your computer to do this:
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
or alternately, you can use a root file manager such as root explorer to remove the files (I personally just renamed mine so they wouldn't be recognized. I don't like burning bridges).
Re-flash cmw afterward and it should stay.
Thanks! That worked, you the man! I renamed them as well, as I don't want to burn bridges either.
First off, let me start out by saying that the Infinity is running on what is possibly the worst software ever designed. Props, Asus. You've made my life hell until the last second.
So, here's my problem. The tablet was working fine 24 hours ago. I turned it off last night, turned it on this morning, working great on CROMi-Xeno (which is awesome, it actually makes the tablet bearable.) and played on it for a while before turning off again. While playing it, I noticed it lag a little more than usual, so I decided to cold boot it. Booted bootloader, hit cold boot, and.... bootlooping. Awesome. No biggie, I'll just restore a backup. I waited for it to restore, and when it was finished, wiped cache and Dalvik, and.... bootlooping again. I tried wiping system and data. Still bootlooping. I downloaded Asus 's official firmware from their website, and flashed. Bootlooping. Someone help me fix this and get it back to stock firmware, so I can sell it and be done with it once and for all. I will never buy another Asus product again.
greydelta38 said:
First off, let me start out by saying that the Infinity is running on what is possibly the worst software ever designed. Props, Asus. You've made my life hell until the last second.
So, here's my problem. The tablet was working fine 24 hours ago. I turned it off last night, turned it on this morning, working great on CROMi-Xeno (which is awesome, it actually makes the tablet bearable.) and played on it for a while before turning off again. While playing it, I noticed it lag a little more than usual, so I decided to cold boot it. Booted bootloader, hit cold boot, and.... bootlooping. Awesome. No biggie, I'll just restore a backup. I waited for it to restore, and when it was finished, wiped cache and Dalvik, and.... bootlooping again. I tried wiping system and data. Still bootlooping. I downloaded Asus 's official firmware from their website, and flashed. Bootlooping. Someone help me fix this and get it back to stock firmware, so I can sell it and be done with it once and for all. I will never buy another Asus product again.
Click to expand...
Click to collapse
I'm wondering if my version of TWRP is too old or something. Can anyone explain in detail how to update to a newer version of TWRP or install CWM in order for flashing to fully work?
greydelta38 said:
I'm wondering if my version of TWRP is too old or something. Can anyone explain in detail how to update to a newer version of TWRP or install CWM in order for flashing to fully work?
Click to expand...
Click to collapse
what version do you currently have, just download the .blob from twrp's site boot into fastboot and run "fastboot flash recovery *name of blob*.blob"
JoinTheRealms said:
what version do you currently have, just download the .blob from twrp's site boot into fastboot and run "fastboot flash recovery *name of blob*.blob"
Click to expand...
Click to collapse
Yeah - I'm also wondering what bootloader you are running with it.
If you are not current on either flash the bootloader/TWRP package from CROMi-X OP, boot back into system, let it bootloop if it does, boot back into TWRP and reflash the rom.
That seems like it would be the only explanation, but now it won't even boot into recovery. I can get it into fastboot, but as soon as I select recovery image it shows the firmware upgrade symbol and then immediately shows the Android Error symbol, and sticks there until I hard power down. When I'm in fastboot, here's what I'm gonna do:
1. connect fastbooted Infinity to pc with all necessary drivers installed
2. download filename.blob from TWRP's website for the Infinity
3. on command console enter -fastboot flash recovery filename.blob- and it will push the recovery through fastboot hopefully
Is that correct? I'm under the impression that as long as I can get to the fastboot menu, ANYTHING is repairable.
greydelta38 said:
That seems like it would be the only explanation, but now it won't even boot into recovery. I can get it into fastboot, but as soon as I select recovery image it shows the firmware upgrade symbol and then immediately shows the Android Error symbol, and sticks there until I hard power down. When I'm in fastboot, here's what I'm gonna do:
1. connect fastbooted Infinity to pc with all necessary drivers installed
2. download filename.blob from TWRP's website for the Infinity
3. on command console enter -fastboot flash recovery filename.blob- and it will push the recovery through fastboot hopefully
Is that correct? I'm under the impression that as long as I can get to the fastboot menu, ANYTHING is repairable.
Click to expand...
Click to collapse
The command is
fastboot -i 0x0B05 flash recovery filename.blob
Since you can boot into the bootloader, check the version# and make sure you flash a compatible recovery.
Most of the time, as long as you can get into the BL, it's fixable. But to make it unbrickable you need nvFlash. And that's just become possible for or tablet on JB. May be a project for once you got this problem fixed: http://forum.xda-developers.com/showthread.php?t=2455925
I suspect you need to format data to fix the issues (you'll lose everything on the internal sd card) but before you do follow bernd's recommendation and get TWRP on there (you wiped it out when you flashed ASUS stock) and then use the file explorer in TWRP to copy anything important to an external SD and make sure the cromi-x rom is on sd too. Then format data from the wipe menu and reinstall. You'll be back to normal in no time. :good:
BTW You may have got some corruption from turning f-sync off.
berndblb said:
The command is
fastboot -i 0x0B05 flash recovery filename.blob
Since you can boot into the bootloader, check the version# and make sure you flash a compatible recovery.
Most of the time, as long as you can get into the BL, it's fixable. But to make it unbrickable you need nvFlash. And that's just become possible for or tablet on JB. May be a project for once you got this problem fixed: http://forum.xda-developers.com/showthread.php?t=2455925
Click to expand...
Click to collapse
sbdags said:
I suspect you need to format data to fix the issues (you'll lose everything on the internal sd card) but before you do follow bernd's recommendation and get TWRP on there (you wiped it out when you flashed ASUS stock) and then use the file explorer in TWRP to copy anything important to an external SD and make sure the cromi-x rom is on sd too. Then format data from the wipe menu and reinstall. You'll be back to normal in no time. :good:
BTW You may have got some corruption from turning f-sync off.
Click to expand...
Click to collapse
I tried wiping internal before recovery was lost and it didn't work. I suspected that some problems arose from turning fsync off too. I'm pushing TWRP 2.6 to the Infinity now, will try flashing your excellent rom again and see if it takes without bootlooping.
greydelta38 said:
I tried wiping internal before recovery was lost and it didn't work. I suspected that some problems arose from turning fsync off too. I'm pushing TWRP 2.6 to the Infinity now, will try flashing your excellent rom again and see if it takes without bootlooping.
Click to expand...
Click to collapse
You need to specifically format data in twrp not just wipe data. Only formatting will restore the device now once data corruption has occurred.
I originally had Katkiss 4.3 v19 and it was working fine. I then wanted to update to the recent 4.3.1 v27 but when I tried to flash the new ROM, it says that it can't open the zip file and failed. I backed up beforehand, so I wiped the cache and dalvik. I then tried to flash the ROM again, but it still says failed. I went to restore the backup to go back and for some reason, it is also failing.
I have TWRP 2.6.0.0 and I am stuck in recovery where I can't flash anything. Not even when I wanted to flash to stock.
I have the Asus EEE transformer tf101 tablet.
How do I fix this?
Please Help.
Are you trying to flash from Micro SDCard ?
Maybe the card has corrupted - try formatting the card in a PC, then copy #27 back to it, and try flashing again
Or try another MicroSD Card
*Detection* said:
Are you trying to flash from Micro SDCard ?
Maybe the card has corrupted - try formatting the card in a PC, then copy #27 back to it, and try flashing again
Or try another MicroSD Card
Click to expand...
Click to collapse
I did this and it says successful but I don't think it's completely flashed because the last line says E:Unable to mount '/staging'. Plus when I reboot, it just goes back to recovery. I flashed SuperSU but it didn't change anything.
EDIT: Ok. So I tried flashing any rom and it says 'successful', yet it seemed like it flashed the rom too quickly. Afterwards, I'd reboot but it just goes from the Eee transformer logo to twrp recovery. This happens to all of the 'successful' flashes. When I tried to flash the stock rom, it would just say failed.
I really don't know what to do at this point. I tried formatting the SD card, changing the SD card, reinstalling twrp using the EasyRecovery app and I wiped my internal and external data (which I think is the problem and IDK how to recover them). I even tried flashing a new recovery (CWM) and, like the other 'successful' flashes, still goes back to TWRP.
gigases said:
I did this and it says successful but I don't think it's completely flashed because the last line says E:Unable to mount '/staging'. Plus when I reboot, it just goes back to recovery. I flashed SuperSU but it didn't change anything.
EDIT: Ok. So I tried flashing any rom and it says 'successful', yet it seemed like it flashed the rom too quickly. Afterwards, I'd reboot but it just goes from the Eee transformer logo to twrp recovery. This happens to all of the 'successful' flashes. When I tried to flash the stock rom, it would just say failed.
I really don't know what to do at this point. I tried formatting the SD card, changing the SD card, reinstalling twrp using the EasyRecovery app and I wiped my internal and external data (which I think is the problem and IDK how to recover them). I even tried flashing a new recovery (CWM) and, like the other 'successful' flashes, still goes back to TWRP.
Click to expand...
Click to collapse
The /staging/ error is normal, nothing to worry about.
Question, if you shut down the tablet from recovery. Then turn it on with a 3 second power button press, does it go directly to recovery?
If so, this is causing your tablet NOT to finish the flash when it reboots. It needs to reboot normally and you should see the Eee Pad logo with a progress indicator.
If you do have a recovery boot loop, try this. Boot to recovery and go to the Advanced section and open a terminal window.
Code:
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Then reboot normally (not to recovery). Then after it tries to boot not into recovery, boot back to recovery and try restoring your 019 backup.
frederuco said:
The /staging/ error is normal, nothing to worry about.
Question, if you shut down the tablet from recovery. Then turn it on with a 3 second power button press, does it go directly to recovery?
If so, this is causing your tablet NOT to finish the flash when it reboots. It needs to reboot normally and you should see the Eee Pad logo with a progress indicator.
If you do have a recovery boot loop, try this. Boot to recovery and go to the Advanced section and open a terminal window.
Code:
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Then reboot normally (not to recovery). Then after it tries to boot not into recovery, boot back to recovery and try restoring your 019 backup.
Click to expand...
Click to collapse
Yes. When I reboot/shutdown from recovery, it shows the eee pad and nvidia logo on the bottom and then goes to recovery. I did what you said with the terminal window. I also typed in the code. and it says:
5+0 records in
5+0 records out
5 bytes (5B) copied,
0.006015 seconds, 831B/s
Afterwards, I rebooted normally and it still goes back to recovery. It doesn't even go to the 'ASUS' logo where there is a wheel on the bottom.
gigases said:
Yes. When I reboot/shutdown from recovery, it shows the eee pad and nvidia logo on the bottom and then goes to recovery. I did what you said with the terminal window. I also typed in the code. and it says:
5+0 records in
5+0 records out
5 bytes (5B) copied,
0.006015 seconds, 831B/s
Afterwards, I rebooted normally and it still goes back to recovery. It doesn't even go to the 'ASUS' logo where there is a wheel on the bottom.
Click to expand...
Click to collapse
May need to do it from an ADB shell, but adb shell is blocked on TWRP 2.6.X.X for security reasons.
I would suggest flashing TWRP again using EasyFlasher. See my guide here: www.transformerforums.com/forum/asu...nt/31927-frederucos-guide-root-rom-tf101.html . Grab one of the repacked versions with TWRP 2.6 and you should be back in business in no time.
I did everything and it all seemed fine. Now I'm in a bootloop. I used the TWRP 2.6.3.0 EasyFlasher
Okay. I just tried other recoveries (CWM and Rogue) and they seemed to go well. I tried flashing, yet it still does the same thing as before where it goes to the logo and then to the recovery.
gigases said:
I did everything and it all seemed fine. Now I'm in a bootloop. I used the TWRP 2.6.3.0 EasyFlasher
Okay. I just tried other recoveries (CWM and Rogue) and they seemed to go well. I tried flashing, yet it still does the same thing as before where it goes to the logo and then to the recovery.
Click to expand...
Click to collapse
At this point, I would try restoring stock using EasyFlasher. Just download the asus firmware file and leave it as is (do not unzip) and put it in the asusupdate folder in EasyFlasher.
Once you flash back to stock and can boot, then flash TWRP with EasyFlasher and you should be good to go.
frederuco said:
At this point, I would try restoring stock using EasyFlasher. Just download the asus firmware file and leave it as is (do not unzip) and put it in the asusupdate folder in EasyFlasher.
Once you flash back to stock and can boot, then flash TWRP with EasyFlasher and you should be good to go.
Click to expand...
Click to collapse
That did it. I flashed back to stock and it can boot again. I'll flash TWRP again.:fingers-crossed: Thank You
Any time! I have a few EasyFlashers with newer versions of TWRP in the EasyFlasher thread. Start and the end and read backwards to find them.
When I attempt to go to Cofface's Baidu page to download his 5.1 TWRP version, I get a message saying the content is no longer available. Specifically, Google Translate shows "Lol, you visit the page does not exist." Does anyone happen to have a copy they're willing to share? Or is there some issue with the 5.1 version that would suggest that I shouldn't use it? If I shouldn't ask for some reason, I apologize. Otherwise, thanks in advance.
https://yadi.sk/d/5YI63uiAhz5UD/Recovery/TWRP
Thanks very much for the link! I think I must have some deeper problems, as every time I flash this recovery (and another version I found in my old downloads), I just get stuck in a boot loop. I was able to use TWRP when I was on B015, but for some reason, I can't get it to work on B106. I'm using:
fastboot flash recovery c:\android\twrp_cn.img
However, like I said I just get stuck in a boot loop. When I flash the stock recovery, everything starts working again.
wpennhokie said:
Thanks very much for the link! I think I must have some deeper problems, as every time I flash this recovery (and another version I found in my old downloads), I just get stuck in a boot loop. I was able to use TWRP when I was on B015, but for some reason, I can't get it to work on B106. I'm using:
fastboot flash recovery c:\android\twrp_cn.img
However, like I said I just get stuck in a boot loop. When I flash the stock recovery, everything starts working again.
Click to expand...
Click to collapse
Did you unlock your bootloader?
Yes, it is. I was able to run TWRP when I was on B015. The phone is rooted, so I've just been using Titanium Backup to back everything up before I wipe the phone, but it would be nice to take a Nandroid backup instead of having to reinstall from TB.
wpennhokie said:
Yes, it is. I was able to run TWRP when I was on B015. The phone is rooted, so I've just been using Titanium Backup to back everything up before I wipe the phone, but it would be nice to take a Nandroid backup instead of having to reinstall from TB.
Click to expand...
Click to collapse
Thats the same problem I have. I used the other twrp recovery https://mega.nz/#!l5kmUByA!41uExNuasZRgLBML9TTSp8myX-_F6UgQZuE2F2BRZUE
This one worked with out boot loops for me. you can give it a shot.
Thanks for the link! I can now get into TWRP. However (sadly), after I leave TWRP, it reboots directly back to TWRP. I've tried rebooting from TWRP into the system and shutting down, but each time, it just goes straight back to TWRP. I was able to boot into fastboot, so I reflashed the boot.img file, but it still goes straight to TWRP. I actually have had this issue before, and I wasn't ever able to figure it out. Any help would be greatly appreciated, as usual.
wpennhokie said:
Thanks for the link! I can now get into TWRP. However (sadly), after I leave TWRP, it reboots directly back to TWRP. I've tried rebooting from TWRP into the system and shutting down, but each time, it just goes straight back to TWRP. I was able to boot into fastboot, so I reflashed the boot.img file, but it still goes straight to TWRP. I actually have had this issue before, and I wasn't ever able to figure it out. Any help would be greatly appreciated, as usual.
Click to expand...
Click to collapse
I had that exact same problem twice on Kangvip B015. When I would restart it would all of a sudden automatically boot into TWRP every time and never boot into the OS. When that happens, in TWRP make a backup, then Fastboot flash the stock ROM (system, boot, cust, recovery, user data etc) then when it boots do a factory data reset, then reroot, flash TWRP and restore from the backup you made. The OS will boot from your backup. I dunno why this happens, maybe it has something to do with with Kernel.
I've tried it a couple of times now, and I'm still not getting it to boot past TWRP once I flash the recovery. It was able to take a backup with TWRP, but when I restored it, I still had to restore the stock recovery before I could boot into the system. At worst, at this point, I can always flash TWRP, take a backup, flash the stock recovery, and then have my system back. It's a few extra steps, but I think I'll do this until I find a custom ROM that I like. I greatly appreciate the help so far.
wpennhokie said:
Thanks for the link! I can now get into TWRP. However (sadly), after I leave TWRP, it reboots directly back to TWRP. I've tried rebooting from TWRP into the system and shutting down, but each time, it just goes straight back to TWRP. I was able to boot into fastboot, so I reflashed the boot.img file, but it still goes straight to TWRP. I actually have had this issue before, and I wasn't ever able to figure it out. Any help would be greatly appreciated, as usual.
Click to expand...
Click to collapse
Reflash the stock b106 recovery and wipe user data and cache, Then reflash twrp recovery and restore your backup. It should boot then.
To follow up, I tried using the updated version of TWRP that you (mtyler7807) posted in the development thread and following the instructions above. I can flash the recovery, boot into it, and take a backup. After that, as long as I boot into the system, I'm fine. However, once I boot into recovery for the first time after that initial backup, it just reboots into TWRP every time. So, right now, I took a backup a day or so ago, and I've just avoided going back in to TWRP again. I have another X2 on the way (a 32GB version), so I'm hoping that I'll have better luck with that one.
wpennhokie said:
To follow up, I tried using the updated version of TWRP that you (mtyler7807) posted in the development thread and following the instructions above. I can flash the recovery, boot into it, and take a backup. After that, as long as I boot into the system, I'm fine. However, once I boot into recovery for the first time after that initial backup, it just reboots into TWRP every time. So, right now, I took a backup a day or so ago, and I've just avoided going back in to TWRP again. I have another X2 on the way (a 32GB version), so I'm hoping that I'll have better luck with that one.
Click to expand...
Click to collapse
By any chance, did you delete anything from the Cust Folder at any point?
ajsmsg78 said:
By any chance, did you delete anything from the Cust Folder at any point?
Click to expand...
Click to collapse
As far as I know, I have not. I did do a complete wipe of everything (except the SD card) at one point using TWRP, but I've always restored the system using the stock system.img file. Right now, the Cust folder is showing five folders, with several more folders/files underneath. Is there a particular file I should be checking for?
wpennhokie said:
As far as I know, I have not. I did do a complete wipe of everything (except the SD card) at one point using TWRP, but I've always restored the system using the stock system.img file. Right now, the Cust folder is showing five folders, with several more folders/files underneath. Is there a particular file I should be checking for?
Click to expand...
Click to collapse
I don't think so. It's weird how some of us have different problems than others. I've had zero issues with TWRP but lately my screen has been going crazy. My touches don't work, things jump it's like my digitizer is messed up but when I restart everything is fine again. So I reloaded everything and the problem went away. I guess I debloated too much last time.