Long ago, I unlocked my s5830i and installed CWM 5.x, but keeping Samsung's firmware. Long story short, I decided to try a new rom recently. I used CWM to take a backup, wiped and flashed the new rom, and used it a month, before deciding yesterday I preferred the previous rom.
So today I went into CWM, hit "restore", and it started to reflash back as normal, but after erasing the boot partition said there was an error in flashing and stopped. I tried a couple more times, same error. So I retried with my other 2 backups on the sdcard to get at least boot flashed properly, but both of those gave md5 errors. I haven't done more. Right now I have the phone showing the CWM screen, and on a charger so it can't shut down. If it truly doesn't have a valid boot partition then I am scared that any reboot or exit from CWM might leave me with an unbootable phone. Please help, as I have no idea what to do next and terrified I'll lose the device entirely or something.
Things I've tied and information that might help:
I don't want my phone bricked or inaccessible, and I don't want to make it worse by mistake, what can I do?
So today I went into CWM, hit "restore", and it started to reflash back as normal, but after erasing the boot partition said there was an error in flashing and stopped. I tried a couple more times, same error. So I retried with my other 2 backups on the sdcard to get at least boot flashed properly, but both of those gave md5 errors. I haven't done more. Right now I have the phone showing the CWM screen, and on a charger so it can't shut down. If it truly doesn't have a valid boot partition then I am scared that any reboot or exit from CWM might leave me with an unbootable phone. Please help, as I have no idea what to do next and terrified I'll lose the device entirely or something.
Things I've tied and information that might help:
- No evidence of error or issue on the sdcard itself, though I can't rule out the chance it has an issue.
- The /recovery directory was previously copied via USB mass storage to my desktop, and SHA1 verified as accurate on backup. The SD card was formatted at some point. I used sha1 verification to copy /recovery back to the sdcard, today, again using USB mass storage.
- The phone's been plugged into a USB2 port all day, but I'm not sure if that charges it or not, and some people say there is a 70% charge limit otherwise flashing won't wor, could that be the problem? Might my boot partition be ok after all?
- No other sdcard holding device, I could borrow a Galaxy S2 from a friend and change the card then reinsert it, if needed?
- adb + fastboot 1.83 + samsung USB drivers + copies of the /recovery backups are all on still the desktop if needed and all good AFAIK (if they work when at the recovery screen). Don't know if fastboot helps but I have it and it works.
- Two backup subfolders on the desktop have a boot.img file in them (5,242,880 bytes). No idea why the others don't.
I don't want my phone bricked or inaccessible, and I don't want to make it worse by mistake, what can I do?