So it says it cannot backup my boot image. Scoured the web buy couldn't find anything. Any fixes?
Sent from my SAMSUNG-SGH-I777 using XDA
"Smithers, release the hounds..."
I dun goofed didn't I?
Sent from my SAMSUNG-SGH-I777 using XDA
I had the same issue, backup would hang, I tried internal and the real SD card backups. all hung around 98%
I ended up flashing another modem down from LC5 (kk6 i think) and backup worked, then it stopped working again. My thought is it was a false positive. I ended up flashing another kernel version and I could then backup via CWM.
So give that a whirl.
Sounds like it should work ill get to it when I'm near a computer thanks!
Sent from my SAMSUNG-SGH-I777 using XDA
Related
I am new to this so I need help. Got impatient with verizon a few weeks back and downloaded and flashed my phone with Odin using ED01 build of Froyo for Verizon Samsung Fascinate. Everything was great, the phone was rooted and had CWM Voodoo lagfix recovery 2.5.1.x. Verizon releases Froyo finally and I decided to flash my phone back to Verizon Stock using DL09-leak zip. It loaded fine and starts fine. The only thing is now my phone is stuck with zero memory showing in the internal memory. I can't add apps or do anything. There isn't even enough memory to keep the initial setup setting. I have to enter them each time the phone is powered up. Someone tell me how to fix this problem. There are no apps on the phone above stock apps. I even backed up my SD card and reformatted it to be sure there was nothing on it mucking up the system. Same result.
Had Nandroid backups which when restored had lost apps from previous and also no memory. Can't even download terminal emulator to do command lines, even if I understood them.
It's a voodoo problem. Flash DI01 full Odin package and it will be fixed.
Sent from my SCH-I500 using XDA App
where to find this?
http://forum.xda-developers.com/showthread.php?t=867648
Sent from my SCH-I500 using XDA App
Had the same issue. Used the D101 and fixed. Since then re-rooted and running the cm7 rom and kernels. Kept the d101 in my computer with odin just in case.
Sent from my SCH-I500 using XDA Premium App
You ROCK
thanks to iwasaperson and adrenalyne. You ROCK!!. My phone went back to stock and now is updating to 2.2. Now that I can fix it.... Should have lots of fun!!!!
You're welcome
Sent from my SCH-I500 using XDA App
Could a flashed modem be responsible for why my phone dies when its been on a lock screen for a while or will it be the rom.?
Sent from my GT-I9100 using xda premium
Most probably it's the ROM.
I think that something in the ROM it's the guilty, maybe if you try fix permissions
Why not back up with Titanium, do a CWM backup and try flashing a new ROM? You would be able to go straight back if you wanted by restoring the CWM backup.
Thanks guys in the end I went with a restore from an earlier backup works OK probably the from.
Sent from my GT-I9100 using xda premium
Ok, so I was installing the ubthrottle script and it didn't go as well as planned. I have lost root access. Superuser.apk is still there so if I try to reroot the phone it fails at the end because the apk still exsists. I can't get to the BSR so I can't restore any of my backups. Obviously I will probably have yo sbf and start over. The only bad thing about all of that is the only internet access I have is via my phone and don't have an sbf locally so when I download it, it takes a huge ammount of data. Anyways if there is another solution let me know
trafalger888 said:
Ok, so I was installing the ubthrottle script and it didn't go as well as planned. I have lost root access. Superuser.apk is still there so if I try to reroot the phone it fails at the end because the apk still exsists. I can't get to the BSR so I can't restore any of my backups. Obviously I will probably have yo sbf and start over. The only bad thing about all of that is the only internet access I have is via my phone and don't have an sbf locally so when I download it, it takes a huge ammount of data. Anyways if there is another solution let me know
Click to expand...
Click to collapse
Strange. You are sure you can't access say /data w/ es file explorer?
Have you tried to put the bsr.apk on your sdcard and run it from there?
Sent from my DROID X2 using XDA App
Yes...I tried everything that I could...nothing would work short of doing the sbf. That being said I did that rerooted and whatnot and back hapilly on cm7...I'm sure I did something wrong somewhere installing that script but for the life of me can't figure it out
Sent from my MB870 using xda premium
At least you're back up and running.
Sent from my DROID X2 using XDA App
Luckily, it sounds like you didn't lose anything, but that's why, whenever you're going to flash something, it's always good to nandroid first so you can get back to where you were before.
iBolski said:
Luckily, it sounds like you didn't lose anything, but that's why, whenever you're going to flash something, it's always good to nandroid first so you can get back to where you were before.
Click to expand...
Click to collapse
Understood but I couldn't even boot into BSR at all only thing I could boot to was Android Recovery. I completely lost all root access and could not flash any of the backups that I had made at all.
Sent from my MB870 using xda premium
trafalger888 said:
Understood but I couldn't even boot into BSR at all only thing I could boot to was Android Recovery. I completely lost all root access and could not flash any of the backups that I had made at all.
Sent from my MB870 using xda premium
Click to expand...
Click to collapse
I guess what I was trying to say was, before you flashed the mod onto your phone, boot into BSR, nandroid backup and then flash it. I'm assuming you had to boot into BSR to flash the mod? Not familiar with the mod you were talking about.
Anyways, once you SBFed back and rooted, you would have been able to reinstall SBR and then nandroid recover your previous installation. That's what I meant.
Anyways, glad to see you're back up and running.
Sorry for the misunderstanding on my part...and it was the script that motcher had posted to ubthrottle it was handled with a scripter not the bsr
Sent from my MB870 using xda premium
But either way yes good to be back up and running
Sent from my MB870 using xda premium
are u sure u had the correct busybox installed?
something u could try if that happens again is to see if u are able to update ur busybox version. I think I read somewhere that when root got "lost" people either updated the superuser binary from within superuser app or reinstalled busybox.
Sent from my DROID X2 using Tapatalk
Just realized that I never answered your question...the only thing I had done was changed the version of busybox according to the and I'm sure I did something wrong there and that's why
Sent from my MB870 using xda premium
Sent from my SAMSUNG-SGH-I777 using xda premium
I am not sure what's wrong I have a root I have cwm but I still can't flash anything threw my phone just keeps saying signature failure
Sent from my SAMSUNG-SGH-I777 using xda premium
Stop using rom manager.
Sent from my SGH-I777 using Tapatalk 2
Than what do i do? Just use cwm? It says same thing
Sent from my SAMSUNG-SGH-I777 using xda premium
You fail. Hard. Read the stickies before thinking you know what to do.
I do know what to do . I had flashed back to stock completely. And everything seemed OK straight stock then I rooted it and I couldn't get it to work so I reflashed cwm but for some reason it is still giving me this problem. I have read over and over. I've returned to stock. Tryed entropy 512 kernel cleared cache davlik factory reset all of it. I've been customizing phones for a year now and am just wanting to get into developing or atleast learning. O just never came across this before that o couldn't fix by one of the above methods. I'm sorry if.I.am not.to.your standard or a pro but I like to think I.know what I'm doing. As this is only my second post as a question I figured it be legit.
Sent from my SAMSUNG-SGH-I777 using xda premium
the kernel contains the recovery....
flash entropy's daily driver, then reboot to recovery
STOP USING ROM MANAGER
your question has been answered a thousand times on here....and explained in extreme detail...you should read a little more
Yes i know it does but it still wouldnt work. I figured it ojt last nigbt i had a extra bootloader file which wouldnt let me reset the counter and on top of it my phone wouldnt fully cwm becaise i had a recovery file back up it kept reverting back to. I wiped everyrhing again even sd and this time i was able to flash. Sorry to bother you but i didnt see anyrhong anout tjis imparticulaur
Sent from my SAMSUNG-SGH-I777 using xda premium
Flash back to stock completely again, then use Mobile Odin to flash Entropy's DD. It's the easiest way.
Stop touching yourself. Or this is gonna keep happening.
Sent from my SGH-I777
Hahaha yes thank you mattdm i fixed it but next time i will try this way i actually just got movile odin so learning its in and outs now. And if i keep touchibg myself i cant be succesful at this ? damn
Sent from my SAMSUNG-SGH-I777 using xda premium
I have a MoPho with unlocked bootloader running 2.3.4 and everytime I try to flash back to my saved stock backup from any custom rom I keep getting an "error while flashing boot image" I tried to do an advanced restore and picked the files one at a time but I keep getting the same result. Can someone please help, thank you in advance...
Sent from my MB855 using xda app-developers app
Are you restoring using the same utility you did the nandroid backup with? Joker recovery vs twrp vs cwm recovery
Sent from my MB855 using Tapatalk 2
I created the back up using cwm and trying to restore through cwm...
Sent from my MB855 using xda app-developers app
Stray2thaB said:
I created the back up using cwm and trying to restore through cwm...
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
Are you using a working recovery? Jokers? Twrp? Photon3? Or the ROM manager one? ROM manager version does not work.
Sent from my MB853 using XDA
As far as I know, I am using Clockworkmod Recovery v5.0.2.8. I've tried Rom Manager but I usually get an error while trying to perform a NANDroid backup...
Sent from my MB855 using xda app-developers app
Stray2thaB said:
As far as I know, I am using Clockworkmod Recovery v5.0.2.8. I've tried Rom Manager but I usually get an error while trying to perform a NANDroid backup...
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
as mentioned previously the ROM Manager one DOES NOT WORK. 5.0.2.8 DOES NOT WORK! you NEED to user Jokers, TWRP or the 5.0.2.7-photon3 recoveries ONLY. you can find the working recoveries on my site. choose which one suits you best! don't use Jokers V4 because it won't flash google apps properly.
http://www.motosunfire.com/clockworkmod-recovery/
Ok thanks a lot, I will try the two you just recommended...
Sent from my MB855 using xda app-developers app
OK I downloaded the TWRP recovery you had suggested, I backed up my current from but when I tried to restore a different from I keep getting an error "the process com.android.phone has stopped working" and I have no service now...
Sent from my MB855 using xda app-developers app
Stray2thaB said:
OK I downloaded the TWRP recovery you had suggested, I backed up my current from but when I tried to restore a different from I keep getting an error "the process com.android.phone has stopped working" and I have no service now...
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
alright? well that doesn't say alot? as you could be using any one of 20 different ROMs. which are you using?
na7q said:
alright? well that doesn't say alot? as you could be using any one of 20 different ROMs. which are you using?
Click to expand...
Click to collapse
I am running cm7, or rather was running cm7 coz now my phone is stuck in the boot loop limbo. Kept getting the error "com.android.phone stopped working" and I was unable to make or receive calls all day. So I thought relocking and unlocking the bootloader would do the trick but now I'm stuck on a rock and a hard place. Sssoooooo, do you have any tricks up your sleeves I could use, I would really appreciate it...
I've been able to run a hand full of fastboot commands to bring my phone back out of limbo, I am past the boot image and able to activate with the sprint network. Thank you all who took the liberty of viewing my post, I appreciate the help...
Stray2thaB said:
I am running cm7, or rather was running cm7 coz now my phone is stuck in the boot loop limbo. Kept getting the error "com.android.phone stopped working" and I was unable to make or receive calls all day. So I thought relocking and unlocking the bootloader would do the trick but now I'm stuck on a rock and a hard place. Sssoooooo, do you have any tricks up your sleeves I could use, I would really appreciate it...
Click to expand...
Click to collapse
Stray2thaB said:
I've been able to run a hand full of fastboot commands to bring my phone back out of limbo, I am past the boot image and able to activate with the sprint network. Thank you all who took the liberty of viewing my post, I appreciate the help...
Click to expand...
Click to collapse
hmmm... CDMA user? or GSM? i remember that bug being around in the very early builds of CM7. are you on the latest nightly or stable release?
i might also recommend changing some build prop info (which could be causing this?) to make sure it tells the radio to operate in the correct mode. gsm or cdma. if you look for ro.telophony.default_network=? the ? should be a 4 for CDMA or a 7 for GSM. change to your liking. then reboot. this was an issue in CM9 for the longest time and this is how it was resolved. it's possible it could be the same for CM7.
another option is to of course start over. wipe the cache,data,system partitions, possibly even twice. flash cm7. twice to be safe. then gapps. twice to be safe. then give it another shot.
other than that it might be a bad download or a bad build. so try another if it doesn't work. hope this helps you!
CDMA user, for now I am able to have my phone back on, but I will probably steer away from CM7 AND perhaps try CM10. All I keep finding is an unofficial release, is this the only one there is?
Sent from my MB855 using xda app-developers app
Stray2thaB said:
CDMA user, for now I am able to have my phone back on, but I will probably steer away from CM7 AND perhaps try CM10. All I keep finding is an unofficial release, is this the only one there is?
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
there will never be any officials releases unless somehow Motorola decides they want to give us drivers/source for ICS or JB. which is never. unless we get a leak.