Related
So I was trying to troubleshoot an SMS issue with AOSP 1.6 so I decided to flash back to Fresh 1.0. I also performed a wipe/factory reset. Fresh would not boot - it would just endlessly loop through the boot process, crashing at various points. I tried Fresh 1.1. Same problem. I re-downloaded Fresh 1.0 to make sure my file was not corrupt, flashed that, and have the same problem.
So I decided to start trying to recover from my various backups. What do you know - every single one is corrupt. From adb I see:
Code:
Verifying backup images...
boot.img: OK
cache.img: OK
data.img: FAILED
misc.img: OK
recovery.img: OK
system.img: FAILED
md5sum: WARNING: 2 of 6 computed checksums did NOT match
On every single one. Even if I make a backup and immediately try to restore it I see this error. I also tried backups of my backups and each of those failed as well. Any way to force these to restore?
So I checked my SD card with various tools - no problems found.
So now I'm left unable to flash 1.5 or restore from or make any backups.
Does anyone have any ideas what could be wrong or what I should do to fix it? What other information could I provide?
honestly I would try to RUU and reroot and then try flashing a backup it may not be that the backups are corupt put that something isnt letting it read that part of the backup correctly.
gthing said:
So I was trying to troubleshoot an SMS issue with AOSP 1.6 so I decided to flash back to Fresh 1.0. I also performed a wipe/factory reset. Fresh would not boot - it would just endlessly loop through the boot process, crashing at various points. I tried Fresh 1.1. Same problem. I re-downloaded Fresh 1.0 to make sure my file was not corrupt, flashed that, and have the same problem.
So I decided to start trying to recover from my various backups. What do you know - every single one is corrupt. From adb I see:
Code:
Verifying backup images...
boot.img: OK
cache.img: OK
data.img: FAILED
misc.img: OK
recovery.img: OK
system.img: FAILED
md5sum: WARNING: 2 of 6 computed checksums did NOT match
On every single one. Even if I make a backup and immediately try to restore it I see this error. I also tried backups of my backups and each of those failed as well. Any way to force these to restore?
So I checked my SD card with various tools - no problems found.
So now I'm left unable to flash 1.5 or restore from or make any backups.
Does anyone have any ideas what could be wrong or what I should do to fix it? What other information could I provide?
Click to expand...
Click to collapse
Have you tried to use the RUU to return to complete sock and then just re-root? The RUU does not depend on your SD card, just in case that is the culprit. There is a link on my sig. If not that would be my next step.
wtphoto said:
honestly I would try to RUU and reroot and then try flashing a backup it may not be that the backups are corupt put that something isnt letting it read that part of the backup correctly.
Click to expand...
Click to collapse
Beat me to it.
But a quick thread hijack real quick. I see in your sig you have a horizontal fresh nexus hybrid bootscreen. care to share the source. Sounds cool.
Back on track after this I promise
rockcrawler said:
Beat me to it.
But a quick thread hijack real quick. I see in your sig you have a horizontal fresh nexus hybrid bootscreen. care to share the source. Sounds cool.
Back on track after this I promise
Click to expand...
Click to collapse
give me a min and I will post a flashable zip in the theme sticky
now back to the helping.
Trying to flash RUU from the Fresh blog now. For some reason it is failing to see my phone when it is trying to flash. Could it be because I am in recovery mode?
gthing said:
Trying to flash RUU from the Fresh blog now. For some reason it is failing to see my phone when it is trying to flash. Could it be because I am in recovery mode?
Click to expand...
Click to collapse
Yes. Boot into whatever ROM you can and then try again.
I assume that you have had the ADB drivers working before?
gthing said:
Trying to flash RUU from the Fresh blog now. For some reason it is failing to see my phone when it is trying to flash. Could it be because I am in recovery mode?
Click to expand...
Click to collapse
no this has been brought up a few times you need to make sure you have the most recent sdk installed then copy and paste the adb.exe, adbwinapi.dll and the fastboot.exe into the ruu file then try again.
wtphoto said:
no this has been brought up a few times you need to make sure you have the most recent sdk installed then copy and paste the adb.exe, adbwinapi.dll and the fastboot.exe into the ruu file then try again.
Click to expand...
Click to collapse
+1 on this,
Someone should update the ruu thread to include this.
Installed the adb driver (no, I didn't have it previously) and copied the files from the latest SDK. No luck still but I'm going to keep trying.
you could also try booting into fastboot and trying it who knows it might be becuase you are in recovery just poer off and hold volume down and power at the same time to get into fastboot and try it that way.
wtphoto said:
you could also try booting into fastboot and trying it who knows it might be becuase you are in recovery just poer off and hold volume down and power at the same time to get into fastboot and try it that way.
Click to expand...
Click to collapse
That did it! Flashing now! Thanks!
EDIT: Maybe I spoke too soon. The flasher is stuck at "erasing user data..." and is showing 0% and the phone is showing the htc boot screen. I don't know if it's safe to cut it off and start over or not.
Windows had to increase virtual memory in the middle of the operation and I think it jacked things up ....
np glad to help.
Yea ... it seems to be getting stuck on "Erasing user data...." not sure what to try next.
unfortunatly thats the extent of the knowledge that I have I would try contacting gbhil or toast or fresh or one of the other devs to see what they say.
Pull battery, do a factory reset (BACK+HOME+POWER) & then attempt to reflash RUU.
gu1dry said:
Pull battery, do a factory reset (BACK+HOME+POWER) & then attempt to reflash RUU.
Click to expand...
Click to collapse
No luck... I give up for tonight...
gthing said:
No luck... I give up for tonight...
Click to expand...
Click to collapse
That really sucks.
same thing
The same thing happened to me when i tried to flash gumbo 1.5c. I flashed RUU and then re-rooted that resolved my issue..
Turns out my problem was that I was trying to flash the RUU from a virtual machine. I'm used to being able to flash WM roms from a Windows VM but apparently it doesn't work with the Android tools. I could also not use the auto-rooter from the VM.
I had to track down a Windows machine () and then was able to get everything flashed and running without too much trouble.
Thanks for everyone's help on this. My phone is now back up and running and I was able to confirm the problem I was having: AOSP 1.6 radio is incompatible with the airave and will cause you to not be able to send SMS messages.
After following his two step process, thanks MT, I still have CWM installed after returning to stock. I did this today 3-22-12 so I doubt it was the old file he talks about in the thread. Any help would be appreciated.
Regards,
-Trevor
Edit- I would like to get CWM off.
whhs41 said:
After following his two step process, thanks MT, I still have CWM installed after returning to stock. I did this today 3-22-12 so I doubt it was the old file he talks about in the thread. Any help would be appreciated.
Regards,
-Trevor
Edit- I would like to get CWM off.
Click to expand...
Click to collapse
Hey that's just the stock rom has nothing to do with recovery..to return to stock flash the file you mentioned in the title boot into cwm wipe data/factory reset boot back up grab the all in one program and select unroot and I believe that removes cwm been a few weeks since I have done it.
Sent from my Galaxy Nexus using xda premium
Thy the following link this has tools to do what you want. They are not too hard to use this is how I both rooted my phone and and installed CWM.
Guys, I hope that you can help me with my problem.
I tried to make a ordinary backup, usin CWM. It went fine this time. Sometimes it has occured problems with doing a backup also.
The problems come when I try to restore that backup. When I it starts, and then closes. The log says "MD5 error", I don't remember if it is exaktly that, but it is something similar.
Does anyone of you have any solution on this problem?
Thank you!
Best Regards
Jimmy
I'm having the same problem.
Can't create a backup. Error while backing up system or sometimes error while backing up data?
I'm running darky rom, note core kernel and cwm touch 5.0.0.4.
I want to try out Paranoid android but don't have a backup to fall back on!
Sent from my GT-N7000 using xda premium
MinnesotaVikings1961 said:
Guys, I hope that you can help me with my problem.
I tried to make a ordinary backup, usin CWM. It went fine this time. Sometimes it has occured problems with doing a backup also.
The problems come when I try to restore that backup. When I it starts, and then closes. The log says "MD5 error", I don't remember if it is exaktly that, but it is something similar.
Does anyone of you have any solution on this problem?
Thank you!
Best Regards
Jimmy
Click to expand...
Click to collapse
I sure hope you arent thinking of doing a nandroid of an ICS rom?
Belfia said:
I sure hope you arent thinking of doing a nandroid of an ICS rom?
Click to expand...
Click to collapse
I'm not trying to do a nandroid. I'm just trying to do a backup using Clockworkmod Recovery.
MinnesotaVikings1961 said:
I'm not trying to do a nandroid. I'm just trying to do a backup using Clockworkmod Recovery.
Click to expand...
Click to collapse
That sounds like a nandroid backup to me. Do NOT restore any nandroid backups in CWM on stock ICS roms/kernels.
Use Abyss kernel. Flash it. Reboot Recovery. Restore nandroid.
The actual backup should work in CWM though.
Please if you dont mind, would you explain why its not a good idea to recover the nandroid backup with an ICS kernel and so on....will this produce a bad emmc?
Currently I'm on PA Rom, I also couldn't make a nandroid backup , it says error while backing up image of /sdcard/.android_secure/
Any suggestion would be appreciated , thanks.
slide200sx said:
Please if you dont mind, would you explain why its not a good idea to recover the nandroid backup with an ICS kernel and so on....will this produce a bad emmc?
Click to expand...
Click to collapse
There is a chance of triggering the EMMC_CAP_EREASE command when under heavy I/O load
Hello...Please help me out with this!
I recently wanted to try this custom rom AOKP and it didn't work so I had already backed up the original rom and I was on CWM menu and I clicked restore.. On that menu I accidently clicked "Free unused Data"... I tried to restore but it says "Error restoring System" I tried to connect to my computer so that I can atleast install the CM 10.1.. But my computer doesn't detect the device! Any idea? Please Help I'm desperate need of a solution!
Thanks in advance
~Nicholas Nick
Have you tried To install Stock Rom using Odin ?
Fixed it!
MoNsTeRmUk said:
Have you tried To install Stock Rom using Odin ?
Click to expand...
Click to collapse
Nope! But I fixed it! For those who want to know how here it is... I had clockworkmod so I used ADB Bundle and used the commands to
copy and paste in downloads... I downloaded AOKP and copied it by ADB and I installed it... It worked!
xneonnick said:
Nope! But I fixed it! For those who want to know how here it is... I had clockworkmod so I used ADB Bundle and used the commands to
copy and paste in downloads... I downloaded AOKP and copied it by ADB and I installed it... It worked!
Click to expand...
Click to collapse
Good news ^_^
i am trying to revert my phone back to stock. there are no RUU's available for my phone but have found a nandroid cwm. how do i use this? what should i do.
sorry if this is a silly question.
blaze0121 said:
i am trying to revert my phone back to stock. there are no RUU's available for my phone but have found a nandroid cwm. how do i use this? what should i do.
sorry if this is a silly question.
Click to expand...
Click to collapse
well, technically, you unzip the CWM backup on your PC, which would give you a "backup folder" (usually yyyy-mm-dd.hh.mm.ss), then you put this (adb push) into /data/media/clockworkmod/backup/yyyy-mm-dd.hh.mm.ss, and then choose RESTORE in CWM recovery.
EDIT: if you are going from the updated firmware 2.xx back to a 1.xx ROM, your touchscreen drivers won't work, and you'll need to use an OTG cable + mouse to be able to make it work!!