Problem restoring NAND backup - Droid Eris Android Development

Hi guys. I am having a problem restoring my nandroid backup. I get the error "Error : run 'nandroid - mobilesh restore' via adb " Any ideas anyone?
Sent from my ERIS using XDA App

Rather than have folks on the other side of the internet guess at what the trouble might be, you should just look in the recovery log - where the exact error that occurred will be reported.
There is a menu item in Amon_RA under "Other" for copying the recovery log file to the root of the SD card.
Note that the recovery log file is volatile, so you must perform this copy operation in the same recovery boot session that the error occurs in. (I am presuming that the error is repeatable.)
bftb0

agg009 said:
Hi guys. I am having a problem restoring my nandroid backup. I get the error "Error : run 'nandroid - mobilesh restore' via adb " Any ideas anyone?
Sent from my ERIS using XDA App
Click to expand...
Click to collapse
Is your battery charged? Your get that error if battery is low, try plugging it in for 15/20 mins, than give it a try ...

Did you happen to rename it with spaces?
Sent from my ERIS using XDA App

I did not rename it, I had it plugged in whilst doing the recovery and I didn't even know about the log. I'll try It again when I get to work. Thanks.
Sent from my ERIS using XDA App

I had this happen once when I cleared the cache and tried to restore. Boot up normally then boot to Amon and try the restore without wiping.

Related

Nandroid backup

I have a problem, I am running FR007 and I can't get Clockwork to make a working backup. If I try to restore from the backup it gives MD5 error. I also tried using Rom Manager and it gives me the android with the triangle error. What do I need to do to get a working backup.
Try titanium backup or Astro File Manager.
tbone22 said:
I have a problem, I am running FR007 and I can't get Clockwork to make a working backup. If I try to restore from the backup it gives MD5 error. I also tried using Rom Manager and it gives me the android with the triangle error. What do I need to do to get a working backup.
Click to expand...
Click to collapse
Out of curiosity, when you turn off your phone or, restart it, whatever it is that you do to get into clockwork...do you have your phone plugged in with the usb cable?
Yeah I get into clockwork and do a android backup but if I try to restore I get an,error. MD5 something. Titanium and astrology don't do android do they.
Sent from my HTC Liberty using XDA App
tbone22 said:
Yeah I get into clockwork and do a android backup but if I try to restore I get an,error. MD5 something. Titanium and astrology don't do android do they.
Sent from my HTC Liberty using XDA App
Click to expand...
Click to collapse
lol @ astrology. damn auto correct lol. anyway, you didn't pay attention to my question. do you have your phone hooked up to usb when you are rebooting to go into clockwork?
Yeah auto correct gets me alot. And no I don't have anything hooked to the phone when I try to backup.
Sent from my HTC Liberty using XDA App
are you renaming the backup folder?
No. It won't sync with HTC sync either if that helps.
Sent from my HTC Liberty using XDA App
same thing happened to me for almost all of my backups, i think it was because i put in a custom kernel. I switched back and it started to work again.

Help installation aborted and won't restore nand!

Hey I was trying to update a friends mytouch 32a to cm6.1 rc1 from 5.8 through rom manager she downloaded it fine checked all the boxes and it downloaded and it went into clockworkmod and the installation aborted do to SD card not mounting then she tried to reboot but it would then she tried to nand restore but it failed to install boot then she tried to advanced restore but its not booting and unfortunately she dosnt have accces to a computer right now or another rom to install and she is texting me with another phone right now so I'm not there any help I would really appreciated it
Sent from my HERO200 using XDA App
She's going to need to manually download a new ROM and flash it from Clockworkmod. Holy run-on sentence btw.
That's the problem though her laptop is getting worked we tried advanced restore and everything but it gets stuck on boot
Sent from my HERO200 using XDA App
She could always pop her SD card into another phone, use that phone to download the ROM, and then move it back. Or, she could borrow and friends computer or go to a library. Either way.....
Sent from my HTC Magic using Tapatalk
Update... after about 200texts back and forth I was finally able to get her to go to partitions menu and format boot system data and cache so then after two more attempts of running nandroid it finally restored I have never had a nandroid fail to restore boot it was the weirdest thing and the format boot was my last resort but thank God it worked lol and I have s serious headache
Sent from my HERO200 using XDA App
Bierce22 said:
Hey I was trying to update a friends mytouch 32a to cm6.1 rc1 from 5.8 through rom manager she downloaded it fine checked all the boxes and it downloaded and it went into clockworkmod and the installation aborted do to SD card not mounting then she tried to reboot but it would then she tried to nand restore but it failed to install boot then she tried to advanced restore but its not booting and unfortunately she dosnt have accces to a computer right now or another rom to install and she is texting me with another phone right now so I'm not there any help I would really appreciated it
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Bierce22 said:
Update... after about 200texts back and forth I was finally able to get her to go to partitions menu and format boot system data and cache so then after two more attempts of running nandroid it finally restored I have never had a nandroid fail to restore boot it was the weirdest thing and the format boot was my last resort but thank God it worked lol and I have s serious headache
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
How about adding a period here and there.

rooting problem in defy+

hi all I tried rooting defy+ using superoneclick 2.3 and was successful. i then backed up user apps using titanium backup.then i tried the unrooting option in superoneclick. when unrooting was in progress superoneclick stopped responding & crashed.i tried again but its stopping in middle,a message data/local/tmp/bomh file not found at step 1 and stops responding.i checked if its still rooted but getting message you're phone is not rooted when using root explorer.now i am not able root it again too getting same file not found.
can some help me to rectify this issue.
Sent from my MB526 using xda app-developers app
jackajay said:
hi all I tried rooting defy+ using superoneclick 2.3 and was successful. i then backed up user apps using titanium backup.then i tried the unrooting option in superoneclick. when unrooting was in progress superoneclick stopped responding & crashed.i tried again but its stopping in middle,a message data/local/tmp/bomh file not found at step 1 and stops responding.i checked if its still rooted but getting message you're phone is not rooted when using root explorer.now i am not able root it again too getting same file not found.
can some help me to rectify this issue.
Sent from my MB526 using xda app-developers app
Click to expand...
Click to collapse
try rooting after data wipe from stock recovery
If not then you'll have to flash a stock sbf
thekguy said:
try rooting after data wipe from stock recovery
If not then you'll have to flash a stock sbf
Click to expand...
Click to collapse
how to do data wipe,will i lose all installed app data?. i hv nandroid backup will it help in any ways.kindly brief me.
thanx,
jj
Sent from my MB526 using xda app-developers app
jackajay said:
how to do data wipe,will i lose all installed app data?. i hv nandroid backup will it help in any ways.kindly brief me.
thanx,
jj
Sent from my MB526 using xda app-developers app
Click to expand...
Click to collapse
If you have a nandroid backup, just restore it. If you were rooted when you backed up, you will be rooted again.
Factory reset - power up while holding Volume Down, then press Vol-Up and Vol-Down together when you see the little Android icon. This is stock recovery. Then select Wipe Data and cache. Yes you will lose all your data and apps.
_ossie_ said:
If you have a nandroid backup, just restore it. If you were rooted when you backed up, you will be rooted again.
Factory reset - power up while holding Volume Down, then press Vol-Up and Vol-Down together when you see the little Android icon. This is stock recovery. Then select Wipe Data and cache. Yes you will lose all your data and apps.
Click to expand...
Click to collapse
thanks for the info,will restoring nandroid backup too will result in lost of apps & data?
for restoring nandroid backup boot to recovery then select back & recovery then select restore from backup option. this is the step right?
Sent from my MB526 using xda app-developers app
If you have a full nandroid backup, then restoring will not lose your apps
Sent from my MB526 using xda premium
i selected backup(full) option when taking backup & its size is 0.98gb is it a full nandroid right?
also do i hv to do anything to more other than clicking unroot button in superoneclick?
Sent from my MB526 using xda app-developers app
Ya its fine
Sent from my MB526 using xda premium
If you have BL7 it could be the problem. The solution here seems to work though.
http://forum.xda-developers.com/showthread.php?t=1542956
pls find the error i am getting while trying to root.
i tried to boot in recovery by pressing power button wihile holding vol key down i could see android symbol(android mascot) with exclamatory mark.how to go to cmw recovey from there i couldnt see any menu?
jackajay said:
pls find the error i am getting while trying to root.
i tried to boot in recovery by pressing power button wihile holding vol key down i could see android symbol(android mascot) with exclamatory mark.how to go to cmw recovey from there i couldnt see any menu?
Click to expand...
Click to collapse
You probably can't get into CWM recovery now (you are not rooted at the moment). When you see exclamation mark just press vol - and + simultaneously. Then you will get into stock recovery. Just wipe data from here (factory reset) and try again with rooting.
i google for the issue i am getting /data/local/tmp/boomsh file not found. i could see many cases where people have reported the problem. can anyone say if there is any solution for this or only factory reset is the only option. if i do factory reset will i be able to be back on track. i dont want to lose my datas
Pls help me solve this issue also i would like to thank all of you for giving me information whenever asked.
Thanks a lot,
jj
jackajay said:
i google for the issue i am getting /data/local/tmp/boomsh file not found. i could see many cases where people have reported the problem. can anyone say if there is any solution for this or only factory reset is the only option. if i do factory reset will i be able to be back on track. i dont want to lose my datas
Pls help me solve this issue also i would like to thank all of you for giving me information whenever asked.
Thanks a lot,
jj
Click to expand...
Click to collapse
Only one note: as far as you have TB of your apps + data, you will be able to get them back after successful root.
If you need your sms messages, then backup them with any SMS backup app from GooglePlay
If you have your contacts synced with google account, they will be back after new sync.
It will take some time but most important data will be safe to restore.
And for next time: make a nandroid backup before any bigger changes in the system - then you will be able to get back quite fast with all system settings.
When resetting the system do not erase your SD card.
So sorry for bad news but probably resetting the system is now probably best step to do. If it doesn't work next step would be flashing of full sbf.
i have a nandroid backup but couldn't able to get into custom recovery since my phone is not rooted now.i took nandroid back couple of days before when i managed to root my mobile.
Sent from my MB526 using xda app-developers app
jackajay said:
i have a nandroid backup but couldn't able to get into custom recovery since my phone is not rooted now.i took nandroid back couple of days before when i managed to root my mobile.
Sent from my MB526 using xda app-developers app
Click to expand...
Click to collapse
Then you loose nothing.
- Wipe data/factory reset
- try to root
- if successfull install 2nd init and restore from nandroid backup (all) - then you shall have a phone in a state that you had before
- if not successful, then give me your current kernel (settings>about phone) and I'll try to show you which sbf from a list I send in message should be the best. Then you will root it, install 2ndinit, restore nandroid backup or flash any CMxxx and restore from your TB backup.
my defy+ info,please find me a suitable SBF.
System version-45.0.891.MB526.AsiaRetail.en.03
model number-MB526
android version-2.3.4
Baseband version-EPU93_U_00.60.00
Kernal [email protected]#1
build number-4.5.1-134_DFP-891
Thanks,
jj
jackajay said:
my defy+ info,please find me a suitable SBF.
System version-45.0.891.MB526.AsiaRetail.en.03
model number-MB526
android version-2.3.4
Baseband version-EPU93_U_00.60.00
Kernal [email protected]#1
build number-4.5.1-134_DFP-891
Thanks,
jj
Click to expand...
Click to collapse
Here's the link to all sbfs for defy and defy plus
http://forum.xda-developers.com/showthread.php?t=966537
Enjoy
Sent from my alienware lappy
Sent from my HTC Wildfire S A510e using xda premium
vedang81 said:
Here's the link to all sbfs for defy and defy plus
http://forum.xda-developers.com/showthread.php?t=966537
Enjoy
Sent from my alienware lappy
Sent from my HTC Wildfire S A510e using xda premium
Click to expand...
Click to collapse
I couldnt find the SBF corresponding to my stock ROM in that link you have provided.
Can someone help me find the 4.5.1-134_DFP-891 SBF since i cant find it in the list of SBF's shared by vedang81
jackajay said:
Can someone help me find the 4.5.1-134_DFP-891 SBF since i cant find it in the list of SBF's shared by vedang81
Click to expand...
Click to collapse
Maybe some other forums have the file, just try any other BL6, with numbers 4.5.1-134_DFP from 125 up to 161.
Just try and give feedback.

Stuck on Starting Apps

So I was playing Family Fued last night on my phone and pressed the home button. After doing so, my phone screen turned black and became unresponsive so I held the power button and rebooted. Upon booting the phone got stuck on the boot animation.
So I tried dirty flashing my ROM, gapps, and kernel. The phone booted then got stuck on the Starting Apps toast with a continuous progress wheel. I tried a combination of wiping caches and dirty flashing to no avail. I was running francos kernel with -75 UV, but flashed a kernel without UV to be sure. I'm still unable to get past the starting apps toast when I restore to the backup I made.
I just want to get it to boot so I can retrieve some important text messages. Any help is appreciated. Thanks in advance.
Sent from my Nexus 4 using xda premium
If you're getting as far as the starting apps dialog, you should be able to get a logcat of the boot process, which will go a long way in diagnosing the problem, and if it is recoverable.
I'm thinking either a framework file got corrupted, or even more likely, your data partition is corrupted and upon bootup, dalvik can't write to /data/dalvik-cache while attempting to "optimize" apps, and it therefore hangs.
This is all just conjecture of course, and I could be completely wrong, but a log will surely help.
JsChiSurf said:
If you're getting as far as the starting apps dialog, you should be able to get a logcat of the boot process, which will go a long way in diagnosing the problem, and if it is recoverable.
I'm thinking either a framework file got corrupted, or even more likely, your data partition is corrupted and upon bootup, dalvik can't write to /data/dalvik-cache while attempting to "optimize" apps, and it therefore hangs.
This is all just conjecture of course, and I could be completely wrong, but a log will surely help.
Click to expand...
Click to collapse
How would I pull the log cat? Also, is there a way I could salvage corrupted data?
Sent from my Nexus 4 using xda premium
nbeebe24 said:
How would I pull the log cat? Also, is there a way I could salvage corrupted data?
Click to expand...
Click to collapse
You need to stream the output of logcat via (assuming windows) your command prompt console using adb:
adb logcat > log.txt
Then upload the log.txt file for review. That's the best place to start and see what it says.
JsChiSurf said:
You need to stream the output of logcat via (assuming windows) your command prompt console using adb:
adb logcat > log.txt
Then upload the log.txt file for review. That's the best place to start and see what it says.
Click to expand...
Click to collapse
Okay I'll pull the log when I get home. Are you able to read those?
Sent from my Nexus 4 using xda premium
I've read a logcat or two in my day
Sent from my Nexus 4 using xda app-developers app
JsChiSurf said:
I've read a logcat or two in my day
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Do I have to wait until the cursor in the command prompt stops blinking to give you the log?
nbeebe24 said:
So I was playing Family Fued last night on my phone and pressed the home button. After doing so, my phone screen turned black and became unresponsive so I held the power button and rebooted. Upon booting the phone got stuck on the boot animation.
So I tried dirty flashing my ROM, gapps, and kernel. The phone booted then got stuck on the Starting Apps toast with a continuous progress wheel. I tried a combination of wiping caches and dirty flashing to no avail. I was running francos kernel with -75 UV, but flashed a kernel without UV to be sure. I'm still unable to get past the starting apps toast when I restore to the backup I made.
I just want to get it to boot so I can retrieve some important text messages. Any help is appreciated. Thanks in advance.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
The last time I was stuck in Starting APps, I did a factory data reset in Recovery Mode, and it worked.
Here's what I got so far http://pastebin.com/pf3b5gc8
opticaldh said:
The last time I was stuck in Starting APps, I did a factory data reset in Recovery Mode, and it worked.
Click to expand...
Click to collapse
That defeats the purpose of trying to recover my text messages. It boots fine from other back ups and fresh installs but not from the particular backup I started a thread about.
Sent from my Nexus 4 using xda premium
Titanium backup pro allows you to restore text message from android backups.
Not sure if the free version does it but I did find two other apps that are free that you can try.
1)app extractor (found on google play)
2) nand manager http://forum.xda-developers.com/showthread.php?p=35367320#post35367320
Sent from my Nexus 4 using xda app-developers app
Titanium or any other app, at this point, won't do any good at this point since the phone won't boot up all the way
The logs definitely show things look pretty FUBAR'ed. Though not optimistic, the first thing I'd try is to reboot to recovery and click 'fix permissions' via the 'Advanced' tab (assuming TWRP), and see if that does anything.
If that doesn't help any, and you don't care about trying to continue down the path of getting the ROM to boot, and all you do care about (mostly) is saving your text messages, assuming they are still there, what I would do is, from recovery, adb pull the data folder where the mms/sms/call log database is stored, do a full wipe, install a fresh rom, and then after first boot, reboot back to recovery and restore the data you pulled (this is all titanium is doing anyway).
You could even make a nandroid of your current bad setup if the above didn't work for some reason.
To get the current data for mms/sms/calls, first, reboot to recovery:
Code:
adb reboot recovery
Via your command prompt, make a directory in the same folder from where you are running adb, and then change into it, as follows:
Code:
mkdir com.android.providers.telephony
cd com.android.providers.telephony
Then, while still in recovery mode, pull your data:
Code:
adb pull /data/data/com.android.providers.telephony .
After you've successfully pulled your data, wipe the phone completely, install your new ROM, gapps, etc, and let it boot up completely, then reboot back to recovery again. Once back up in recovery, push the data back to the phone.
(make sure you are still inside the 'com.android.providers.telephony' directory you created via your command prompt)
Code:
adb push . /data/data/com.android.providers.telephony
That should restore you previous database, cache, etc.
Reboot the phone and cross your fingers
That's what I was essentially suggesting, but I didn't know how to manually do it.
From his current ROM that works he could use tb or the other two apps to restore just his SMS from his nandroid backup
Sent from my Nexus 4 using xda app-developers app
marsdta said:
That's what I was essentially suggesting, but I didn't know how to manually do it.
From his current ROM that works he could use tb or the other two apps to restore just his SMS from his nandroid backup
Click to expand...
Click to collapse
Problem is, he doesn't have a current ROM that works.
But, he could first wipe and install a fresh ROM all together, and then install Titanium, and use it to restore the above referenced data from a Nandroid.
Though, he'd FIRST have to/want to Nandroid the current bad ROM in order to make sure the nandroid has the most current data, else any new text messages would be lost since the previous nanadroid.
After doing all of that, it'd be much simpler/quicker to just follow the instructions provided above
All of this, of course, is based on bailing on the current ROM, but for the sake of challenge, I'd love to try and get it going as well, based on making changes and following the impact via logcat.
Well I feel dumb. I mixed up a couple threads that were talking about the same thing. Only in the other they did have a nandroid.
I should not be responding when I'm half asleep.
Edit - maybe I didn't mix up but its now I've only been up maybe for a bit. Had to drive brother to school. But reread his op and this caught my eye " I'm still unable to get past the starting apps toast when I restore to the backup I made."
So he does have a current nandroid of the bad ROM?
Sent from my Nexus 4 using xda app-developers app
marsdta said:
Well I feel dumb. I mixed up a couple threads that were talking about the same thing. Only in the other they did have a nandroid.
I should not be responding when I'm half asleep.
Click to expand...
Click to collapse
No worries, the concept / principle is still sound We're all here to help!
JsChiSurf said:
No worries, the concept / principle is still sound We're all here to help!
Click to expand...
Click to collapse
Now I'm getting "Error while restoring /system" when I try to restore my derped backup
nbeebe24 said:
Now I'm getting "Error while restoring /system" when I try to restore my derped backup
Click to expand...
Click to collapse
Why are you trying to restore your derped backup? Did you already wipe and update to a fresh ROM?
JsChiSurf said:
Why are you trying to restore your derped backup? Did you already wipe and update to a fresh ROM?
Click to expand...
Click to collapse
Yes, I'm already running a fresh install. I'm a little confused by your instructions above. Which setup am I pulling the telephony data from? The bad nandroid?
Sent from my Nexus 4 using xda premium
nbeebe24 said:
Yes, I'm already running a fresh install. I'm a little confused by your instructions above. Which setup am I pulling the telephony data from? The bad nandroid?
Click to expand...
Click to collapse
Last I read, you never got past the starting apps dialog, so all of my instructions are based on the fact that that's where you're at.
If you've already make a nandroid of the bad version and are up and running on a new ROM, this process changes.
In this case, what I would do is pull the the data partition nandroid file (in your TWRP/BACKUPS folder), "data.ext4.win", off of your sdcard, add the ".tar" extension (this is all these files are):
data.ext4.win.tar
Then open the above file with WinRAR, navigate to the same /data/data/com.android.providers.telephony/ folder referenced in my previous instructions and pull the content out of the .tar.
Then, go into recovery and use adb to push the contents of the "/data/data/com.android.providers.telephony" that you extracted from the .tar file and push back to your phone.
Or, if you use titanium, as mentioned above, you could try and extract it right out of the nandroid file directly while the new ROM is running.

PLEASE HELP. Boot loops to recovery

I installed the HORSEMAGEDDON ROM and it worked - for the most part. But it kept giving me annoying errors about different apps that were attempting to update every time I turned it on. So I tried to restore my backup that I had made with CWM 6.0.2.8. However the backup apparently did not restore properly because it now boot loops back into CWM any time I try to start it. I get the errors:
E:Can't open cache/recovery/log
E:Can't open cache/recovery/log
E:Can't open cache/recovery/last_log
E:Can't open cache/recovery/last_log
So I tried to reflash HORSEMAGEDDON but it still loops back into the CWM recovery screen.
I have wiped everything according to the instructions on the HORSEMAGEDDON thread.
HELP!! This happened to me on another U8800-51 phone and I wound up hard bricking it trying to get back to stock.
Anybody???
Does anybody have any ideas on how I can fix this?
Did you wipe cache/dalvik cache?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
iheartsamsung said:
Did you wipe cache/dalvik cache?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Yes. I did a wipe of data and factory reset as well.
What I would do is get an SD card with a custom rom on it and try installing it from recovery menu
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Obviously you have been having problems with that rom, so go with something different.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
iheartsamsung said:
Obviously you have been having problems with that rom, so go with something different.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Okay. Here is what I did step by step:
1. I was on Stock 2.2.2 Froyo and flashed HORSEMAGEDDON successfully. But I had some errors related to updates since it was such an old ROM the updates were all for much newer versions of the apps tied to 4.x.x.
2. I attempted to restore my backup made with CWM 6 to return to the stock. It said it completed successfully but when I rebooted it just looped into the recovery screen with the error messages posted in my first post.
3. So I tried to reflash HORSEMAGEDDON and it said it completed successfully. But it still bootloops into recovery.
4. I can access most of the features of the recovery. I can access the pink screen and swap recovery versions. I can access my SD card from my PC when I mount it from recovery.
5. Yes, I did do full wipes with each attempt to reflash.
The ROM was not the problem. It worked and worked well other than update issues for apps. It was only after attempting to restore to stock I ran into issues.
The problem appears to be something was corrupted when I tried to restore my backup, even though it said it completed successfully.
So if I try to flash yet another custom ROM, even if I could find one I trust given all of the version issues etc., I don't think it would act any differently. But if somebody can recommend one I am all ears. Keep in mind I have a -51 phone so it will have to be for that or the PRO.
Given that, how can I get back to stock? Am I the only person who has ever had this problem? I don't believe that is the case, so somebody must know how to fix it or can point me to a procedure to repair the internal memory.
Help!!
I'm new at xda so it's not letting me post an external link. Google "bootlooping" and the first one in list is from xda, just follow the instructions
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Thanks but.....
iheartsamsung said:
I'm new at xda so it's not letting me post an external link. Google "bootlooping" and the first one in list is from xda, just follow the instructions
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
None of the fixes on this link seem to apply to my situation.
When I said "bootloop" I may have misused the term. What happens is I power up, it goes to logo screen for about 10 seconds, shuts down and restarts to logo screen then goes into recovery after about 5 seconds. From other info that I have found it is due to a corrupt bootloader and I need to reflash the bootloader. Problem is, reflashing the bootloader i.e. CWM, does no good at all.
I am also hampered by lack of info specific to the -51 model. And I cannot find a copy of the stock ROM anywhere that is for the -51.
So essentially I am screwed. All of that said, I have found a new phone for $40.00 so all is not lost. It's a U8800 but not the -51 or PRO. I don't plan on customizing it, I'll just stick with stock. After trashing two phones even after following the advice to "BACKUP" I think enough is enough. Backing up did me no good whatsoever in both cases.
In my estimation, the culprit is CWM, or at least the versions I used.
If anybody has any advice I'm all ears.

Categories

Resources