i had Moto Photon but i had unfortunately flashed USC 2.3.5 and made it electrify and then I was using it as is, but recently to flast mof 2.3.5 I mistakenly flashed radio 198_7, and tried various roms but dint work as sometimes wifi error or no signal issue. so I am again trying to flashing 2.3.5USC but somehow the flashing fails, Please tell me which radio i should flash so that at least I will come back usable phone. HELP PLEASE
This is not development thread. After moving the thread by moderator, I am willing to help you.
Please do not make new thread with this problem, just wait for moving.
http://forum.xda-developers.com/showthread.php?p=29366503
Flash 198_7 radio, if you have still problems, flash 198_7 libmoto_ril.so.
If you have problems with wifi, flash 254_13 modules and 254_13 boot.img
peetr_ said:
This is not development thread. After moving the thread by moderator, I am willing to help you.
Please do not make new thread with this problem, just wait for moving.
http://forum.xda-developers.com/showthread.php?p=29366503
Flash 198_7 radio, if you have still problems, flash 198_7 libmoto_ril.so.
If you have problems with wifi, flash 254_13 modules and 254_13 boot.img
Click to expand...
Click to collapse
Thanks Peetr..
I had flashed USC2.3.5 sbf but i am stuck at initial wizard where it shows android icon, but after touching its not moving ahead and main thing is the signal is not receiving. so i flashed 2.3.5sv2_198_7_radio.sbf but still stuck at same wizard. also I am unable to enter bootstrap recovery. only thing i can do via RSD lite.
Also I want MOF2.3.5 on my photon
Reflash full sbf one more time, wipe data in recovery and connect to wifi, to pass the setup wizard.
flashing failed
As I cant enter bootstrap or android recovery i couldnt wipe data, but
1>Entered RSD protocol Support by pressing power and vol up together and
2>started flashing
1FF-sunfire-user-2.3.5-4.5.1A_SUN_USC_19.0-19-release-keys-signed-USC-US
3>after some process of flashing of 6/7 mins, now it says that Failed Flashing process interface bp error.
I restarted the phone and it took time to boot
after it booted with USC logo, immediately i received some error saying before the android wizard
sorry, the application text messaging process com.motorola.conversation has stopped unexpectldy and after that
touch to android to begin, but even after touching nothing happens except it shows that i have touched and network signal shows red mark
also got suggestion poll schedukar service error.
I guess this USC2.3.5 has not flashed correctly, how can i wipe data as I dont have any idea how to enter recovery
suhaspatwa said:
As I cant enter bootstrap or android recovery i couldnt wipe data, but
1>Entered RSD protocol Support by pressing power and vol up together and
2>started flashing
1FF-sunfire-user-2.3.5-4.5.1A_SUN_USC_19.0-19-release-keys-signed-USC-US
3>after some process of flashing of 6/7 mins, now it says that Failed Flashing process interface bp error.
I restarted the phone and it took time to boot
after it booted with USC logo, immediately i received some error saying before the android wizard
sorry, the application text messaging process com.motorola.conversation has stopped unexpectldy and after that
touch to android to begin, but even after touching nothing happens except it shows that i have touched and network signal shows red mark
also got suggestion poll schedukar service error.
I guess this USC2.3.5 has not flashed correctly, how can i wipe data as I dont have any idea how to enter recovery
Click to expand...
Click to collapse
enter the recovery manually. turn the phone off. press vol down and power until fastboot appears. press vol down until you see android recovery. press vol up to select. wipe away.
yes, android recovery mode entered but it shows failed triangle yellow-exclamation android icon, is there any other way?
Once in recovery when you see the yellow triangle push vol up and vol down together and the options will appear. Select factory reset. Then power button
wow Great morning, I did not know this.
Thanks I can do factory reset now. After this I will reflash USC2.3.5 again as peetr suggested.
again flashing failed, But booted successfully in usc2.3.5
1>Flashin USC2.3.5 failed, Interface BP: Error sending JUMP command Device API Error: 0xE003003F Address: 0x800000 Command: JUMP
2> After failed flash, I rebooted the phone.finished the wizard and wifi setup , now i am on usc2.35.
3> now how can i get MOF2.3.5 rom
photon with usc2.3.5 -->Mof2.3f
I will move to http://forum.xda-developers.com/showthread.php?p=29366503
for further ROM flashing..
THANK YOU ALL WHO HELPED ME IN UNBRICKING THIS FONE
Related
Hello,
I have a rooted and BL unlocked atrix.
Tried to use rom manager to install CWM. Tried to go into recovery but now it is saying: "Failed to boot 2" and under that "Starting RSD mode".
I have pulled battery and no luck.
Please help
Well cant enter fastboot either. Was going to try to flash tenfar's CWM but when i hold down the power and vol down key it it displays the before mentioned error and turns the phone off a millisecond later.
Good news however is that RSD still picks up the phone. I will go home and try to flash the pudding sdf again and see if i can get it to boot up that way. If anyone else has any ideas, let me know please.
flashed pudding using rsd lite and it booted up. Lost root but apps stayed.
Hi. Yesterday i had a problem installing a recovery from Cyanogenmod rom and i got the message of fast booting. I found a tutorial saying how to repair it and i followed it without any problem.
But now, when i boot the phone, y reach the "Android" bootanimation and it stays like that forever. What can be happening now? I had Cyanogen from Mik and flashed a stock froyo (now trying a stock gb, maybe that´s the problem)
Can i save the phone?
Greetings.
After flashing the stock GB, the phone remains the same, staying in the Android bootlogo for ever
Any idea?
You have to wipe data.
Via normal Android recovery? Because when i access to it it shutdowns :S
Yes, but after factory reset, phone should reboot.. For you it only shuts down?
Let´s see, i followed the tutorial and flashed a stock gingerbread (before a stock froyo).
Then, when i access the recovery , a little image with a box, a droid and a bar appears, but then it only reboots. There, when Android bootanimation shows, the phone stays like that for ever and i need to quit the battery.
Edit: I accesed the recovery, but i can´t push any option, only go up and down.
strange.. the bar need to load till end and then the phone reboots.
maybe you have to wait for longer at bootanimation? because the first boot takes longer.
if not, try to flash ROM again, with kdz.
Edit: the menu button doesn't work?
I flashed like 3 different roms and waited in one of them 7 hours to boot. When it access the recovery it appears a warning button and this:
Finding update package
Opening Update Package
Veryfing update package
E: Failed to read footer from /cache/ (is a directory)
E:signature verification failed
Installation Aborted
Click to expand...
Click to collapse
No, in that recovery i can only go up and down, any other button works. If i push home, the recovery dissapear, but then if i push it again it appears again. That menu offers the option to wipe data but i can´t do it.
Are you able to wipe everything?
data, cache, dalvik cache and battery stats.
No, that menu doesn´t work. I only can wipe cache and factory reset.
It appears the rom is well-flashed, but when it reaches the android logo it goes in a loop.
then wipe data and cache.
It resurrected! :O
I flashed a stock Movistar rom from America and it booted normally! Thank god
But i don´t understand why booted now and not later. Also, i couldn´t do anything it the recovery. Anyway, i can root it again because it´s a froyo.
Thank you.
Greetings!
yeah, it's strange that it didn't boot earlier with other ROMs.
anyway, congratz
GL
Yeah, it´s weird. I´m returning it back to Cyanogenmod 7+francokernel like it was before the brick. I know what made it: install ClockWorkMod Recovery, so i´ll stay with the old recovery i had.
Greetings!
AgumonDX said:
I flashed like 3 different roms and waited in one of them 7 hours to boot. When it access the recovery it appears a warning button and this:
Finding update package
Opening Update Package
Veryfing update package
E: Failed to read footer from /cache/ (is a directory)
E:signature verification failed
Installation Aborted
No, in that recovery i can only go up and down, any other button works. If i push home, the recovery dissapear, but then if i push it again it appears again. That menu offers the option to wipe data but i can´t do it.
Click to expand...
Click to collapse
well dude
if you would have just toggled the signature verification off
you would have no problem installing the ROM
viv_jen said:
well dude
if you would have just toggled the signature verification off
you would have no problem installing the ROM
Click to expand...
Click to collapse
Well I dont know how we turn off signature verification. I faced an idential issue using v10E firmware from this link. KDZ update was not able to find the phone in emergency mode. Second time I tried, it did flash the f/w fine.
I got the triangle with an exclamation mark and a droid below. Recovery menu (pressing HOME button) was useless as I could not select any option with any of the hard keys.
This is how I solved it - rebooted once to recovery mode(volumen DOWN + Home), and face a progress bar for a few seconds - rebooted automatically to the LG sign. This time phone booted fine!
Sorry i did not have the kernel or most information about the phone but ill explain the problem if anyone can help out it'd be a blessing
i have a U.S cellular Motorola electrify running 2.3.5 ( which recently found out was unrom-able)
i got it rooted using one touch method--
Then not thinking -- ( ive rooted and installed roms on other phones never a Motorola) didn't know it needed a unlocked bootloader to function and get roms installed.
i knew i needed a clockworkmod on the phone and i read about the app that boots into clockworkmod bootstrap--apk
did that and it worked--
here is the problem..
didn't install the bootloader.. and tried installing Cyanogenmod10 unofficial rom from photon development forum
rebooted-- got Failed to Start2- starting rsd mode -- if i dont press anything
if i press down it says NV recovery but does nothing
if i press UP it goes into Starting usd recovery ( sorry not exact words not with my phone at the moment)
ive been reading guides.. downing the lock unlock from the bricked guide.. RSD lite would read the phone in the usd recovery
try flashing the offical us cellular back but get an error
wont show up in command prompt
not sure what to do.. please help its hard to function without a phone i hope its not fully bricked
Can you get into fast boot by pressing power and volume-down? If so, you just need to wipe everything using "fastboot -w" and rebooting into RSD mode to flash the uscc sbf.
When you flashed cm10, the kernel is not compatible with the bootloader you're on.
If anyone has the 2.3.5 electrify boot.img, you could probably flash it through fastboot if it'll let you
Sent from my sunfire using xda premium
hoslayer13 said:
Can you get into fast boot by pressing power and volume-down? If so, you just need to wipe everything using "fastboot -w" and rebooting into RSD mode to flash the uscc sbf.
When you flashed cm10, the kernel is not compatible with the bootloader you're on.
If anyone has the 2.3.5 electrify boot.img, you could probably flash it through fastboot if it'll let you
Sent from my sunfire using xda premium
Click to expand...
Click to collapse
Thank you for the reply.. when I press volume down and boot on it says " nv flash mode" then turns off unless hooked in a computer then just stays on that screen
If I press volume up and turn on it says fast boot protocol support and Is half recognized in rsd ITE
If I just power no volume press on it says failed to boot 2 starting RSS mode..
I'm sort of new to everything and need more details.. tryed wiping using fast boot u downloaded but gives error.. same with flashing yes cellular sbf in RSd lite trying all 3 button combos that work
Please I need this phone working.. I messed up someone's phone saying I could put cm10 it for Christmas! Any help would be awesome
So I was playing around with Jelly Bean on my RAZR MAXX and I believe I ended up soft bricking the device. I know that took all of 12 hrs. Anyways how can I fix this?
Edit: I went into the system files to install a different gallery app and eventually when I restarted my phone I got the "encryption unsuccessful" message and asked me to do a factory reset, let's just say that didn't go well it kept popping up, but I am able to get to the fastboot menu.
You're kind of in a pickle right now, then.
DON'T go trying this please, but I believe on ICS, you could fastboot back and have it fail, and then use the update.zip or something like that? I'd go ask Mattlgroff. He may be able to hook you up with an UnstuckJB type deal or something.
I'm pretty much stuck in flashboot
Thanks, all the screen says is:
AP Fastboot Flash Mode (S) (Flash Failure)
0A.74
eMMC Info: Size 16G
To return to normal mode- first press power key to power down
Device is LOCKED, Status Code: 0
Battery OK
OK to Program
Transfer Mode:
USB Connected
Last night I tried to flash ICS with RSD Lite but it failed when it tried to flash the boot.img (I know bad idea)
Any thoughts?
mas11 said:
Thanks, all the screen says is:
AP Fastboot Flash Mode (S) (Flash Failure)
0A.74
eMMC Info: Size 16G
To return to normal mode- first press power key to power down
Device is LOCKED, Status Code: 0
Battery OK
OK to Program
Transfer Mode:
USB Connected
Last night I tried to flash ICS with RSD Lite but it failed when it tried to flash the boot.img (I know bad idea)
Any thoughts?
Click to expand...
Click to collapse
I had a softbrick boot loop.
Flast boot .211 ICS. Then go back into stock recovery. Attempt to install the update. It will fail with a status 7. Wipe cache and factory reset. Install the update again. Worked for me. Unfortunately you will lose root access. No knowing when we will be able to get it back as none of the current methods work.
priddyma said:
I had a softbrick boot loop.
Flast boot .211 ICS. Then go back into stock recovery. Attempt to install the update. It will fail with a status 7. Wipe cache and factory reset. Install the update again. Worked for me. Unfortunately you will lose root access. No knowing when we will be able to get it back as none of the current methods work.
Click to expand...
Click to collapse
See my issue is when I try to fast boot .211 ICS it fails at the boot image
I am going to make aflashable zip so you can use it on 2. system and don't loose the ability to downgrade.
Fixed (for the most part)
So I lost my root and for some reason every time I turn off the phone and restart it brings up the AP Fastboot menu, but I just choose the option to boot normally. Thanks for all the help everyone priddyma's method worked even though the .211 ICS boot image failed.
Hello,
I am having a similar problem with the same error.
I am on Jellybean and was trying to downgrade by to ICS.
and I guess I corrupted the OS from what what I understand.
need some help getting out of this. Thanks in Advance.
I have already tried the following:
1. clear the cache.
2. full wipe and restore
EDIT: NVM all I had to do is select normal boot and it booted up normally.
EDIT2 : I can get past the error screen but whenever I reboot the error screen reappears.
I just recently joined the rooting community a few days ago. I started by rooting my phone with petes rooting tool, and then sbf'd the phone back to android 2.3.4 before installing boot strap recovery on the phone. I was able to successfully flash the cyanogen 10 mod, with many exceptions. The first of these exceptions is that the phones keyboard did not work at all (unable to active phone, unable to do anything really), so I decided to look this up. I tried almost everything except installing a new gapps which I was in the process of doing when I hit a major roadblock. The problem I ran into was that when I re-installed the bootstrap recovery on the cyanogen 10 rom to get to the recovery mode in order to flash the gapps file, the phone became stuck on the M (dual core) boot screen. I was however able to access the boot menu (power+volume down), and tried to sbf the phone back to android 2.3.4 so that it would hopefully fix all of my stupidity. Little did I know that this would just increase my unluckiness with the rooting process, and the phone now will not boot into the boot screen. When I hold down (volume down+power) the phone simply flahes a screen and then will do nothing until I pop the battery out. After that, i tried simply turing the hone on by holding down just the power button, and it boot to a screen which displays "failed to boot 2" and then below that "starting RSD mode". From this screen I have tried to sbf to android 2.3.4, and also to android 2.3.5 multiple times, and every time it pops up with either an error on the computer, or "sec_exception: febe, 4e, 4e" and then an error on the computer. ANY HELP WOULD BE GREATLY APPRECIATED!!!! I AM OUT OF OPTIONS AT THIS POINT, AND AM STARTING TO PANIC! HELP ME!
Failed to boot, sounds like hardware failure
but you can try ezSBF, link in my list, might work.
sd_shadow's [Collection] of Links for Droid X2
Sent from my Clear using xda premium
vernon428 said:
I just recently joined the rooting community a few days ago. I started by rooting my phone with petes rooting tool, and then sbf'd the phone back to android 2.3.4 before installing boot strap recovery on the phone. I was able to successfully flash the cyanogen 10 mod, with many exceptions. The first of these exceptions is that the phones keyboard did not work at all (unable to active phone, unable to do anything really), so I decided to look this up. I tried almost everything except installing a new gapps which I was in the process of doing when I hit a major roadblock. The problem I ran into was that when I re-installed the bootstrap recovery on the cyanogen 10 rom to get to the recovery mode in order to flash the gapps file, the phone became stuck on the M (dual core) boot screen. I was however able to access the boot menu (power+volume down), and tried to sbf the phone back to android 2.3.4 so that it would hopefully fix all of my stupidity. Little did I know that this would just increase my unluckiness with the rooting process, and the phone now will not boot into the boot screen. When I hold down (volume down+power) the phone simply flahes a screen and then will do nothing until I pop the battery out. After that, i tried simply turing the hone on by holding down just the power button, and it boot to a screen which displays "failed to boot 2" and then below that "starting RSD mode". From this screen I have tried to sbf to android 2.3.4, and also to android 2.3.5 multiple times, and every time it pops up with either an error on the computer, or "sec_exception: febe, 4e, 4e" and then an error on the computer. ANY HELP WOULD BE GREATLY APPRECIATED!!!! I AM OUT OF OPTIONS AT THIS POINT, AND AM STARTING TO PANIC! HELP ME!
Click to expand...
Click to collapse
im not completely sure why you sbf'd after rooting the first time? no need for that. i would read up a bit more if you do get it working, watch tomsgt123 's videos on youtube so you know what youre doing. and you used the Gapps for cm10.1 not our version. that is why keyboard didnt work. read read read.
after reading abain, i guess you were on 2.3.5. and thats why you sbf'd. but rooting was not needed before sbf. hope you have better luck next time .
flash will fail if battery is too low, should be a low battery error though, but maybe not every time.
if it is low battery, you will need a charged battery or a tbh programing adapter
link to TBH adapter and dx2 external charger in my list
Sent from my XT862 using xda premium
Lorenzo VonMatterhorn said:
im not completely sure why you sbf'd after rooting the first time? no need for that. i would read up a bit more if you do get it working, watch tomsgt123 's videos on youtube so you know what youre doing. and you used the Gapps for cm10.1 not our version. that is why keyboard didnt work. read read read.
after reading abain, i guess you were on 2.3.5. and thats why you sbf'd. but rooting was not needed before sbf. hope you have better luck next time .
Click to expand...
Click to collapse
Do you have any advice on where I should go from here then? My phone is basically a useless hunk of technology until i can get it to boot back into cyanogen 10, or sbf it back to an android operating system. The RSD mode always fails when I try to normally sfd, but i have not tried EZ sbf yet..... any other suggestions?
vernon428 said:
I just recently joined the rooting community a few days ago. I started by rooting my phone with petes rooting tool, and then sbf'd the phone back to android 2.3.4 before installing boot strap recovery on the phone. I was able to successfully flash the cyanogen 10 mod, with many exceptions. The first of these exceptions is that the phones keyboard did not work at all (unable to active phone, unable to do anything really), so I decided to look this up. I tried almost everything except installing a new gapps which I was in the process of doing when I hit a major roadblock. The problem I ran into was that when I re-installed the bootstrap recovery on the cyanogen 10 rom to get to the recovery mode in order to flash the gapps file, the phone became stuck on the M (dual core) boot screen. I was however able to access the boot menu (power+volume down), and tried to sbf the phone back to android 2.3.4 so that it would hopefully fix all of my stupidity. Little did I know that this would just increase my unluckiness with the rooting process, and the phone now will not boot into the boot screen. When I hold down (volume down+power) the phone simply flahes a screen and then will do nothing until I pop the battery out. After that, i tried simply turing the hone on by holding down just the power button, and it boot to a screen which displays "failed to boot 2" and then below that "starting RSD mode". From this screen I have tried to sbf to android 2.3.4, and also to android 2.3.5 multiple times, and every time it pops up with either an error on the computer, or "sec_exception: febe, 4e, 4e" and then an error on the computer. ANY HELP WOULD BE GREATLY APPRECIATED!!!! I AM OUT OF OPTIONS AT THIS POINT, AND AM STARTING TO PANIC! HELP ME!
Click to expand...
Click to collapse
mine did the fail to boot thing back in september, i have to get a new x2. Try using a different computer, good luck
vernon428 said:
Do you have any advice on where I should go from here then? My phone is basically a useless hunk of technology until i can get it to boot back into cyanogen 10, or sbf it back to an android operating system. The RSD mode always fails when I try to normally sfd, but i have not tried EZ sbf yet..... any other suggestions?
Click to expand...
Click to collapse
With it powered off, hold power and volume up . See if you can get it into rsd mode . If so, sbf from there . Hope it works .
Lorenzo VonMatterhorn said:
With it powered off, hold power and volume up . See if you can get it into rsd mode . If so, sbf from there . Hope it works .
Click to expand...
Click to collapse
I can get into RSD mode, and the phone seems to SBF okay, until the SBF on the computer displays "failed", and the phone displays an error message. I am also using a fully charged battery during the whole process (my friend has the same phone so i swap batteries out with him to charge).
vernon428 said:
I can get into RSD mode, and the phone seems to SBF okay, until the SBF on the computer displays "failed", and the phone displays an error message. I am also using a fully charged battery during the whole process (my friend has the same phone so i swap batteries out with him to charge).
Click to expand...
Click to collapse
and you tried EZsbf?
try ezSBF
if you can't get it to work, you can go back, try using rsd lite, and look for Driver issues