I think I soft bricked my a500. I made a backup using thor's recovery 1.6 and when i tried to restore, it complained of md5 error. So what I did was to make a new nandroid.md5 by deleting the old one and doind md5sum. It was able to do the recovery but it will not boot past the acer logo.
I can still see the stuff when I adb in recovery, especially /data/media but not booting past the acer logo. What can I do? Is there a boot log or something I can look at?
************* udpate there seems to be boot log file that I can find. I have installed 3.2 rooted stock via the recovery after wiping everything. It did not work. Changing another sdcard worked. So it seems that it was a bad sdcard that was causing the problem.
If mods see this, might want to delete this thread Cheers
Related
So I followed the guide to root with s=off and it seemed to work fine and I installed clockworkmod v3.0.0.5 through ROM Manager and had made 2 nandroid backups and everything seemed to be working great.
Then I tried to install CM7 RC1 through ROM Manager, thinking if anything went wrong I'd be able to restore the nandroid backups.
Something went wrong and I ended up stuck with the CM7 skateboarder animation infinitely repeating. So after pulling the battery I was able to boot into recovery. It looked like the stock recovery, but after selecting factory reset it went into Clockworkmod. From there I restored my backup, and everything seemed to work fine.
But when I reboot it just gets stuck forever at the MyTouch4G logo (the first one that comes up immediately on power up, not the second, round logo.
I've tried to restore both backups but always get stuck at the same screen.
Right now I need to get the phone working as fast as possible, hopefully to one of my backups (but if I can get it working I've also got MyBackup Pro and Titanium backups of my data and apps).
Can someone tell me what's the best way to get this working again and hopefully if it's possible to successfully restore my nandroid backup?
Thanks!!
Current:
Rom Manger (v3.0.1.0)
Recovery (v3.0.0.5)
When you go in Recovery from bootloader what color is the text green (2.x) or orange (3.x)? Keep in mind if your using 3.0.0.5 which has Recovery 2.5.1.2 then you can't flash CM7 as you need to use 2.5.1.4(Recovery) or 3.0.0.5(Recovery).
If you meet the basic requirement as you still have the rom on your SDCard. I want you to go in Recovery via bootloader. Then go in format and wipe /system, /data. Then go back in advance wipe dalvik and from main screen wipe cache, then do full factory wipe it will remount all. Once this is done select Install zip files> Choose zip files> Find and run the rom> select yes.
When you load for the first time give it some time as it will take few min but if it takes more than 5min than ya its in bootloop. If you get to the part here then it should be working but if you get stuck in mytouch 4g logo then it won't load. Now if you have green(2.x) text then what you need to do is install the Recovery 3.0.0.6.zip though Recovery as you won't be able to access Rom Manager and then try to flash CM7RC1. Let me know if you have any problem or its hard to understand. I know people always get Rom Manager and Recovery version number confused and the whole problem get started.
It says "ClockworkMod Recovery v3.0.0.5" at the top and bottom and has orange text on a black background (highlight line is white text on orange background).
This morning I managed to get it to boot by flashing PD15IMG.zip from HBOOT (took me a while to figure out I have to keep holding both down and power to get to HBOOT, just holding down and releasing power took me to ClockworkMod which wouldn't install the file).
Then I set up my account and downloaded MyBackup Pro which I used to restore visionary+ and rom manager to re-root and re-install clockworkmod then I rebooted into recovery and tried to restore my nandroid backup.
Same problem, stuck in the boot logo. So seems like these nandroid backups are useless.
Is there any way I can recover the backups? At this point I don't have much time to play with CM7 so I'd rather just get my phone back to where it was and play with CM7 a bit later when I have more time. If necessary I'll just go back to PD15IMG and manually restore using MyBackup Pro, but that backup isn't quite as fresh and it's a pain to restore the widgets, etc.
I'll try doing the wipes you suggested and see if that will bring back my backup...
Thanks!
To be clear:
ClockworkMod Recovery 3.0.0.5 -- the orange text version -- CANNOT be used with Stock ROMs, or any other Froyo-based ROM. Not backup, not restore, and not install. It is only for Gingerbread-based ROMs, like CM7.
Froyo and Gingerbread versions of Android use different filesystem structures. CWMR 3.0.0.5 is for EXT4 filesystems, which the Froyo kernel cannot mount.
At boot up, the Froyo kernel tries to mount /system, and fails, because /system is in EXT4 format that it doesn't understand. So the Froyo kernel crashes, reboots .... and fails again. And again.
That explains it. Thanks.
So I installed ClockWorkMod 3.0.0.6 and used that to restore my last nandroid backup (even though it was made in 3.0.0.5) and that seems to have worked!
CM7 does look quite nice. I look forward to playing with it when I have more time.
Thanks for your help!
Hi there. Thought I'd finally get around to rooting my Glacier, making progress but hit a roadblock.
ROM Manager app is stuck on "Error while downloading from server.", so I flashed clockwork recovery 3.0.2.4 with fastboot shell, ROM Manager still thinks recovery isn't installed and gives me the same download error when I try to manual override.
In recovery, attempting to start a backup gives me the error in the title, that is, "Error while backing up boot image!" and halts.
I could probably continue on to flashing cyanogenmod 7 and gapps, but I'm not comfortable doing that without a backup handy.
Android ver. 2.21, eng SPL (85.2007), 3.0.2.4 ClockworkMod recovery.
Can anyone help?
If it were me, I would download a fresh copy of CWM from here and flash it via fastboot. I bet then you'll be able to successfully make a Nandroid. If not, try formatting your SD card.
Downloaded that and re-flashed to no avail. Backed up SD card, formatted it, and for some reason it started working then.
Ah well, at least I have a backup. Thanks!
Had an odd error with the md5 checksums changing, too.. pushed them with adb, used md5sum, they were correct. Rebooted into recovery and they had changed again. Had to push and verify from recovery in order to install.
It ended up working though, so no complaints.
The easiest workaround I found to this problem was to boot into recovery mode using Quick Boot and follow these steps in the cwm boot screen: apply update from sdcard, install /sdcard/update.zip, reboot into recovery, backup and restore, and BACKUP. Worked for me and I didn't have to reformat my sd card, deleting everything on it.
Hi,
I would like to remind you that, CWM v3.x above are no longer support amend scripting which is used in Froyo ROM. Instead it used edify scripting which is used in Gingerbread ROM.
When you are on Froyo and try to use the latest CWM, it will not work, and you will encounter a problem just like you said.
My self, i use the CWM v.2.5.x, on my fascinate, and it can make backup successfully, although i never try the restore function yet.
I was wondering if someone can help me get back to Stock US Wifi. I tried flashing the system.img from a US.img with
if=/sdcard/system.img of=/dev/block/mmcblk0p3
but after reboot it just sits there in the acer logo. Am I missing something?
Where did you get that .img file?
I have a similiar issue. Except I am rooted with CWM and was trying to install Virtuosa 1.0.3. After following all the directions and attempting to update, "it said it instalation aborted - 'file name(cant remember the exact one) is bad."
So I figured since I had just wiped everything that I would use my CWM restore and at least get my programs and icons back where they were before the wipe so that I could check out other options.
When I went to resore, it said MD5 sums do not match. So I decided at that point to just reboot and start over.
When I did so, the tab never (and has still not) made it past the Acer logo.
Since I have CWM working, can someone please point me to the correct URL that would contain the file I need to reboot?? Also, it says my /data file is corrupt. How do I fix this before trying to restore the system with said file - or will that full recovery do it for me?
I got this error when I restore a full backup in CWM.
I explain better:
I made a full nandroid backup & a full titanium backup on my old PB G100W, then I received a brand new tablet from Acer.. Now I would restore back all my apps & data, so I made downgrade from HC 3.2.1 to HC 3.0.1 unstable, root, recovery 1.3.4, updated recovery to 1.7.3 touch and flashed Tegraowners v169.
I restored apps by Titanium and everything was ok, but 2 apps (Opera and a game weren't work properly). Tried something to solve it, but nothing.
I decided to restore my last nandroid backup from cwm 1.7.3, but nothing, restoring boot ok, restoring system ok, restoring data works for a while, almost at the end stops and give me back "Error while restoring /data!".
Maybe my backup could be corrupted or maybe it's a internal storage issue.
So I made a real format (data/media enabled) -> /format system.
Retried, nothing, get back the same error.
Flashed back recovery 1.3.4 by thor and retried restoring, works for a while, then stops again.
I tried another nandroid backup, different from the first one (of 1 week before), same procedure, and stops and the same point.
So, I got two corrupted backup or I'm missing something?
EDIT:
Solved!
I tried so much methods that I bricked the tab, but solved with TimmyDean's method, unbricked, reflashed and then (I don't know how) all Titanium backup were working and no issues.
Maybe the solution on titanium back is reboot a few times.
SOLVED!
3 things possible.
1. You had corrupted data when you did the recovery.
2. Your recovery image is messed up.
3. Thor 1.7.3 is flakey. See number 2.
I'm betting on 3.
Just a hunch. Seems CWM 1.7.2+ has issues on some tablets. This is known in the XDA bootloader forums. Sorry you didn't hear about this, but I would advise ver 1.7 or one of the other options. A pity your recovery image is no good.
Rule of thumb. After making a recovery image, you should always restore it to make sure it is good. Not take it for granted that it works.
Moscow Desire said:
3 things possible.
1. You had corrupted data when you did the recovery.
2. Your recovery image is messed up.
3. Thor 1.7.3 is flakey. See number 2.
I'm betting on 3.
Just a hunch. Seems CWM 1.7.2+ has issues on some tablets. This is known in the XDA bootloader forums. Sorry you didn't hear about this, but I would advise ver 1.7 or one of the other options. A pity your recovery image is no good.
Rule of thumb. After making a recovery image, you should always restore it to make sure it is good. Not take it for granted that it works.
Click to expand...
Click to collapse
I got some freezes on 1.7.3, a few in flashing/wiping time.. Then, I restored 1.3.4 recovery, and it worked fine.
I had to update the old version to 1.7.3 for tegraowners v169 flashing, so I made it. On reboot, it wasn't work anymore.. In recovery mode the screen was blinking, no way to get out. In normal boot the tab got stuck on Acer logo, in recovery mode blinked.
Used the unbricking method with new recovery image (the same 1.7.3 touch) and all went fine.
Rebooted, flashed, restored by titanium and no issues.
Faith mistery!
Thanks for answering master Moscow
Sent from my Packard Bell [email protected]_rv3 using Tapatalk
Hello xda developers!
My thinkpad tablet has been stuck in a bootloop for about two weeks now, and after trying some of the solutions posted on the forums without success I am hoping that someone here can help me restore it to working condition.
The tablet is the 16GB WE model with 3G and it had the last software update from lenovo installed when the problem occurred, the 132 if I am not mistaken. The Android version was 4.0.3. I rooted the tablet about 1 week before the problem occurred and everything seemed fine.
What I have tried so far:
Wipe Cache
Wipe Data/Factory Reset
Reset Button
nvflash - quits because of a failed usb write?(even when run with root/admin rights...)
I only have the stock recovery installed and I cannot flash a nandroid backup from it. And I cannot install CWM recovery because I have no access to adb in the current condition of the tablet.
Any help would be greatly appreciated!
I'm having the same problem, but with diferent conditions, it was with koshu's CM10 rom and CWM recovery for about 3 weeks, and yesterday it got stuck in the boot.
What i tried:
- Wipe data/cache.
- Re-fash the ROM.
- Restore a nandroid backup of the original ICS ROM.
- Restore with the ICS dump posted by MasterofComputers.
Any one knows what could be the problem?
Another question, where i can download the OTA files from the lenovo site, i looked everywere and didn't found it.
nanogennari said:
I'm having the same problem, but with diferent conditions, it was with koshu's CM10 rom and CWM recovery for about 3 weeks, and yesterday it got stuck in the boot.
What i tried:
- Wipe data/cache.
- Re-fash the ROM.
- Restore a nandroid backup of the original ICS ROM.
- Restore with the ICS dump posted by MasterofComputers.
Any one knows what could be the problem?
Another question, where i can download the OTA files from the lenovo site, i looked everywere and didn't found it.
Click to expand...
Click to collapse
There are no real Update files. It uses small packs which only work if the former small ones are all installed in the right order
http://download.lenovo.com/slates/think/tablet1/
These are here
Any progress?
Sent from my Galaxy Nexus using Tapatalk 2
nanogennari said:
I'm having the same problem, but with diferent conditions, it was with koshu's CM10 rom and CWM recovery for about 3 weeks, and yesterday it got stuck in the boot.
Click to expand...
Click to collapse
Same problem here, also while using Koshu's CM10 ROM. But I don't think that's it is related or caused by that ROM, since OP is having the problem with the stock ROM.
The CM10 boot animation loops, suddenly freezes followed by the tablet vibrating and rebooting. I can enter recovery but reflashing didn't help. No solution so far.
Flow_ said:
Same problem here, also while using Koshu's CM10 ROM. But I don't think that's it is related or caused by that ROM, since OP is having the problem with the stock ROM.
The CM10 boot animation loops, suddenly freezes followed by the tablet vibrating and rebooting. I can enter recovery but reflashing didn't help. No solution so far.
Click to expand...
Click to collapse
Since you have cwm you can flash the format zip in the cm10 thread, which will clear everything and should fix the issue. Then reflash cm10.
da_reeseboy said:
Since you have cwm you can flash the format zip in the cm10 thread, which will clear everything and should fix the issue. Then reflash cm10.
Click to expand...
Click to collapse
Thanks for the hint about data-format.zip. But that didn't solved the problem for me. Instead I had to run e2fschk on the /data partition. I occurred to me that I was unable to keep /data mounted rw. This is usually an indication of a corrupted filesystem.
1. Boot into recovery
2. Use these commands after you get a shell with `adb shell`
Code:
umount /data
e2fsck /dev/block/mmcblk0p10
3. reflash the ROM
That solved the boot loop for me.
Hi.
We are discussing on the Lenovo Forum about bricked Thinkpad Tablets and for the moment we got some attention from Lenovo moderators and technical people.
http://forums.lenovo.com/t5/ThinkPa...1-Errors-on-Recovery-Menu/td-p/1055573/page/2
If you have a Thinkpad Tablet that can not be restores because :
1) The "factory reset" is not working (keeps looping on the Lenovo Animation)
or
2) The "Android system recovery <3e>" is not working. You can not access it (freeze on Booting Recovery Kernel Image") or if you can access it is showing errors and can not be used.
Please visit the forum and post your problem. And send to the Lenovo user NINE your problem description.
http://forums.lenovo.com/t5/ThinkPa...1-Errors-on-Recovery-Menu/td-p/1055573/page/2
I can not guarantee that Lenovo will solve our problems, but we have to take the opportunity to show them the problems we are having.
Regards
Martin
BOOT LOOP FIXed
put it into new THREAD
Hi.
If anybody have errors on the Recovery Menu you can ask Lenovo for "extended Coverage".
You need to contact your "Lenovo support in your country for assistance" and if they don't know about the "extended coverage", contact Mark from the Lenovo with a Personal Message thought their forum.
Please check: http://forums.lenovo.com/t5/ThinkPad-slate-tablets/Thinkpad-Tablet-1-Errors-on-Recovery-Menu/m-p/1459057#M28111%C2%A0 to see if you fit their conditions.
I hope this helps you.
Regards
Martin