Related
I have just rooted my sgs2, and tried to flash a rom using rom manager. When it gets to the boot loader screen I get an error message saying,
Failed to verify whole file signature.
And
Signature verification failed.
What am I doing wrong?
Can somebody please help?
Thanks.
Sent from my GT-I9100 using XDA App
jonesy1 said:
I have just rooted my sgs2, and tried to flash a rom using rom manager. When it gets to the boot loader screen I get an error message saying,
Failed to verify whole file signature.
And
Signature verification failed.
What am I doing wrong?
Can somebody please help?
Thanks.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Flash with ODIN..It might fix it
Thanks il try that.
Sent from my GT-I9100 using XDA App
Agree with last post unless instructions tell you to use rom manger then dont use it .
A clue as to what rom might have helped .
Questions = Q&A section .
jje
Theres a way of turning the verification off let me boot into recovery and refresh my memory
Sent from my GT-I9100 using xda premium
Under install sd card you can toggle image verification. Turn this to off but check the md5 of the rom and make sure its not a corrupt download
Sent from my GT-I9100 using xda premium
I've tried cyanogenmod and miui.
Follow the instructions from here: http://forum.xda-developers.com/showthread.php?t=1176411
Note from the instructions: do not flash from ROM Manager when you're flashing CM7 the for the first time.
hi guys....i'm getting fail to boot 4 message when turning on my phone. it happened after flashing 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_5-CM-release-keys-signed-Sprint-US.sbf coz i had a boot loop after flashing a custom ROM and forgot to wipe data. i got a unlocked phone using deprunlock.sbf. i also tried reflashing 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_5-CM-release-keys-signed-Sprint-US.sbf but when i get to "Switching device to BP Pass through..." its goes to "Error Switching device to BP Pass through.." and fails flashing....need help pls!
Are you able to get in fasboot mode or android recovery? Or is it the standard failed to boot 4 rsd starting error?
Sent from my MB855 using xda app-developers app
mof9336 said:
Are you able to get in fasboot mode or android recovery? Or is it the standard failed to boot 4 rsd starting error?
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
its the standard failed to boot 4 starting rsd mode. can this still be fixed?
Make sure your battery has a good charge( do the usb trick if you have to) and try flashing another sbf. Did you try the derpunlock.sbf
Sent from my MB855 using xda app-developers app
mof9336 said:
Make sure your battery has a good charge( do the usb trick if you have to) and try flashing another sbf. Did you try the derpunlock.sbf
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
sorry but i'm kinda new to Motorola Phones, what is the usb trick?last night i tried flashing the 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-198_7-CM-release-keys-signed-Sprint-US.sbf but had the re-enumerate error coz i ran out of battery. Will try still get a charger today but i'm really intrigued about the usb trick thingy....could you help me out?
Google charge any phone with out a charger. Lot a videos on it
Sent from my MB855 using xda app-developers app
mof9336 said:
Google charge any phone with out a charger. Lot a videos on it
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
ahahahahaha....it looks kinda wierd....but anyways when i get a good charge....what's the next thing i should do?should i flash the 198_7?i tried deprunk last night but didn't work....failed to flash....
G69D said:
ahahahahaha....it looks kinda wierd....but anyways when i get a good charge....what's the next thing i should do?should i flash the 198_7?i tried deprunk last night but didn't work....failed to flash....
Click to expand...
Click to collapse
thanks for your help man....fixed my phone now....thanks a lot!
G69D said:
thanks for your help man....fixed my phone now....thanks a lot!
Click to expand...
Click to collapse
my phone is also showing Failed to boot 2
please share how you managed to restore it.
thanks
portman said:
my phone is also showing Failed to boot 2
please share how you managed to restore it.
thanks
Click to expand...
Click to collapse
I too am getting the failed to boot 2 after the motorola update came out. please explain how to fix this issue please
mrperez83 said:
I too am getting the failed to boot 2 after the motorola update came out. please explain how to fix this issue please
Click to expand...
Click to collapse
go to fastboot mode and find android recovery. wipe date and cache. then reboot your phone. download the 198_7 and flash using RSDLite....that should put you on stock ROM.hope it helps you guys....
Do not flash any sbf, after ota update installation.
how you fixed your phone
G69D said:
thanks for your help man....fixed my phone now....thanks a lot!
Click to expand...
Click to collapse
hi sir,
i have the same error as you had please help me how to fix this and which sbf file i need to download and flash it.......
on starting screen it says "failed to boot error 4"
thank you
G69D said:
its the standard failed to boot 4 starting rsd mode. can this still be fixed?
Click to expand...
Click to collapse
please explain me for fixed failed to boot 4 or please upload file img for fix this trouble
thank's
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.
I had some issues with various roms for unknown reasons, so I kept trying out new roms. Well the problem persisted, and as I was attempting to flash a new Rom, recovery just kind of failed. Whenever I attempt to enter recovery, a titled triangle with and exclamation mark and a droid figure pop up and I have to do a battery wipe. My phone still starts and runs, but I'm currently stuck on a problematic rom with no way of getting to recovery. I'm fairly new to all of this so I have no idea what's happening and I'm ultimately scared of attempting anything and messing up more. So any and all suggestions are beyond welcome.
FoxMarsden said:
I had some issues with various roms for unknown reasons, so I kept trying out new roms. Well the problem persisted, and as I was attempting to flash a new Rom, recovery just kind of failed. Whenever I attempt to enter recovery, a titled triangle with and exclamation mark and a droid figure pop up and I have to do a battery wipe. My phone still starts and runs, but I'm currently stuck on a problematic rom with no way of getting to recovery. I'm fairly new to all of this so I have no idea what's happening and I'm ultimately scared of attempting anything and messing up more. So any and all suggestions are beyond welcome.
Click to expand...
Click to collapse
Have you tried reinstalling CWM?? Or maybe using another recovery....
I had that to after updating to 236 first time had to install recovery couple times to get it to work.
Sent from my HTC One X+ using xda premium
Complication in my situation : I don't have a computer. I can get to one with the needed programs on it, but are you sure this will fix it?
I had that to after updating to 236 first time had to install recovery couple times to get it to work.<br />
<br />
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
So just install cwm multiple times..? Like install it, turn phone on, then install again if problem persists or isn't fixed immediately?
You're looking for some magical recipe that will 100% surely fix your phone. There isn't one. You will just have to play and be creative. You can report back here for more advice if needed.
FoxMarsden said:
So just install cwm multiple times..? Like install it, turn phone on, then install again if problem persists or isn't fixed immediately?
Click to expand...
Click to collapse
Like what ravilov mentioned, its more of a trial and error process and not a 100% quick fix. Not having a computer will make things much more difficult.
I'm not looking for a magic easy route, (though it'd be nice if there was one), I'm just asking for literally any advice on the situation.
Use the android sdk 'fastboot' command to push recovery to the device via USB. This should solve your issue with a borked recovery partition.
Sent from my MB860 using Tapatalk 2
Try ROM manager and install cwm with it free on market install it a few times it will work
Sent from my HTC One X+ using xda premium
markwoo said:
Try ROM manager and install cwm with it free on market install it a few times it will work
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
How do I install cwm on it? I have an idea but I don't want to mess up anymore than I already have
FoxMarsden said:
How do I install cwm on it? I have an idea but I don't want to mess up anymore than I already have
Click to expand...
Click to collapse
In rom manager just follow the prompts.
Sent from my MB860 using Tapatalk 2
jjwatmyself said:
In rom manager just follow the prompts.
Sent from my MB860 using Tapatalk 2
Click to expand...
Click to collapse
Should I do Clockwork Mod Touch, or just cwm recovery?
FoxMarsden said:
Should I do Clockwork Mod Touch, or just cwm recovery?
Click to expand...
Click to collapse
No need for touch. If you ever damage your screen, touch recovery will make it impossible to use. Once you've flashed it with rom manager, you can download th3bill's recovery for Atrix and install over the top of it.
Sent from my MB860 using Tapatalk 2
Thanks man, I got it all fixed yesterday and everything is running fine. Thanks for all your help
I, m having a serious issue. Was trying to flash a Sense ROM on my EvoLTE and noticed that while in recovery (twrp v. 2.6.3.0) it says unable to mount data. And so the install does not proceed. So now im stuck with phone unable to boot up. Would greatly appreciate some help in getting my phone working again. How do i get around this to be able to flash a rom to get it to boot up.? Also noticed a warning saying that the kernel was not installed. Tried installing slimbean, which is what i had before, but since data wont mount, nothing installs.
Sent from my GT-N5110 using xda app-developers app
You're S-ON, I assume?
Captain_Throwback said:
You're S-ON, I assume?
Click to expand...
Click to collapse
Actually I'm S-OFF
wallie71 said:
Actually I'm S-OFF
Click to expand...
Click to collapse
Then VipeRUU and start over.
Thank you Captain for the advise. I was actually able to find a solution. Googled it and found a similar issue. They advised to go into advance wipe in twrp and wipe the specific partition that wouldnt mount. That fixed it for me.
Sent from my EVO using xda app-developers app