This is kinda noob of me but i have been doing this for some time and cant seem to find the solution.
I was unlocked and rooted and running th3bill's cm10, working great thanks th3bill,when i deceided i wanted to sbf back to 2.3.4 which
i knew was going to relock and unroot but i have been kinda idle and wanted to have some fun. Anyway.....
Long story short rsd failed at some point. sot sure how long but a good 10 mins later. so i pulled the battery and hit the power and it just sits there saying failed to boot 1.and nothing more. when i hold vol down and pwr the screen flashes and goes black. when i hold vol up and pwr it goes to fastboot.
So all i have is fastboot and my bootloader is now locked.
PLEASE Can anyone help!!!!!!!!!!!!!!!!!!!!!
I will continue to search the threads for what i need but im really not finding it so if someone who knows the link or knows how to fix could please point me in the right direction i would gladly buy a box of joe!!
Seriously need help guys!!!!
Still not locating the proper thread!! Really am stuck here!! Fastboot is all i have working!!!
Still Broke and have made now headway. I really want to fix this phone! Could anyone point me in the right direction PLEASE!!!!!!!!
Going from factory electrify 2.3.5 to photon sbf 2.3.4 doesn't work. The boot loader has different security signatures.
The boot loader was attempted to be replaced by the older 2.3.4 boot loader meant for the photon which gave you the failed to boot 1 message.
Instead of sbfing, you probably should have used the recovery to restore your phone to a previous state.
You might be able to recover and see if there's another issue if you have a copy of the mmcblk0p1 from the electrify system you had before. That way, you can flash it through to possibly have your boot loader working again to show all the options you had before. If after that it gives you another failed to boot message follow this info to try and see what is going. ----> http://forum.xda-developers.com/showthread.php?p=28467871
In the meantime, I'll try to help you with the problem by looking around to see what else I can find
Sent from my MB855 using xda premium
Hoslayer13 you are the man!!!
I never did find a way to fix this phone but i did get it fixed!!!! i just kept trying different things and taking pieces from other posts and i think i have it narrowed down to this being the problem and if anyone knows this to be true then they can confirm my theory.....
When i flashed the 2.3.4 sbf it relocked the bootloader. When i flashed the rdl3unlock i would get temp unlock but i wast then doing the oem unlock portion of the post on unlocking so even though it was saying unlocked the bootloader wasnt actually unlocked untill i put in my unlock code. It was after i actually did this that i was able to flash via fastboot teamwins touch recovery, couldnt get any other recovery to take but that one, who knows why but i was able flash my boot img as well and something else but cant remember now what it was cause i got so excited i just started flashing cm10 as soon as i saw recovery working. I'm actually gonna do it again and try to right down what happens. For now the phone is back up and running and no issues. Really wish i had paid better attention on the fix but i didnt. I was on it for the whole weekend and was very frustrated.
Thanks again hoslayer for jumping in with your whelth of knowledge! I owe you a cup or 2 of coffee thats for sure!!
Its nice to see you back up running .
While I wouldn't recommend soft bricking your phone trying to reproduce it, it'll make for a very good troubleshooting guide lol
Sent from my MB855 using xda premium
Related
i dont have very much free time atm. i have a nexus s 4g running cm7 nightly #65... the situation is i was flashing a new rom and ended up hitting my phone off the arm of the chair.. needless to say the battery came out and now im stuck with the cm7 bootloop.. i can hboot but when i try to enter recovery i get a loop on the google screen with the unlocked logo... i have downloaded adb but im not familiar with it at all. my sdk file is under C:\documents and settings\temp\desktop\android-sdk
ive spent all my free time the past week searching for a solution... my phone was used for work and i recieved all my fire calls on it now its usless and about to go out the window and visit verizon.... if someone could help me fix it i will donate. i used to love trying to figure this stuff out but being so rushed around its just frustrating
Might be able to help
A couple questions to start off:
What method did you use to root your phone?
Have you tried flashing the recovery image again or know how to do it on your phone?
I have a Nexus S 3g and pieced together different tutorials for using ADB to flash the recovery image. I just read a tutorial that seems exactly the same for the 4g model. If you can get into the bootloader you might be alright if you just flash the recovery image again from there. But, setting up ADB can be tricky from my experience. Let me know.
Maybe if you follow the guide in the cyanogenmod wiki to install the recovery.
Heres the link:
http://wiki.cyanogenmod.com/wiki/Nexus_S_4G:_Full_Update_Guide
i cant get into recovery it gets stuck looping the bootlogo and if i go threw hboot/recovery it loops the google screen.
fastboot flash recovery recovery-clockwork-3.1.0.1-crespo4g.img... i have this in the sdk file with fastboot. and it just reloads the adb commands when you start adb
that command should work. maybe its how you input it
i highly doubt it if this will work but try fastboot flash recovery "recovery-clockwork-3.1.0.1-crespo4g.img"
Yeah fastboot should work as it is a different partition than the recovery one. And since cm7 flash doesn't touch that partition (I hope) you shouldn't have any problems with it. Make sure you follow the instructions very carefully on that link I posted. Start over if you have to. I've spent hours on things like this, and you will get frustrated but if you keep at it, you'll get it eventually.
it doesnt effect it that it was the kernel flashing when the phone fell? i was running cm7 for awhile before this happened
Sorry Ive been really busy and haven't been able to get on I used the pdanet method I've tried reflashing but still no luck I think I'm doing it wrong
Sent from my HTC Glacier using XDA App
Guess I have a new paper weight. Just ordered a new phone from Verizon
Sent from my HTC Glacier using XDA App
So here is my problem, i've wiped my phone so many times to try out every rom/kernel that is posted. The last time i clicked the wrong file to sbf to unlock it and ended up flashing the 235 electrify pudding sbf. (had them all in the same folder...dumbass)
I was able to get rid of the 108 svf error by flashing the boot.img back to the photon ones via fastboot. But still would get the 106 anytime i went to try and flash the sbf.
I've tried in Ubuntu as well as windows 7 to flash it back but nothing has worked since it wants a 235 sbf, and it locked the bootloader.
So I said screw it and tried flashing the electrify 2.3.5 and it loaded up and everything, but i'm stuck on the activation screen and cant get past it. (tires to activate through Verizon)
The 2.3.5 update also removed the bootloader unlock in fast boot even with the id number.
So as easy as it was to flash it right to the electrify sbf, i think once the sprint 2.3.5 sbf is out i should be able to go back. Or once an unlock is found to unlock the bootloader, i can flash the files via fastboot.
I haven't tried messing around with nvflash, since my computer doesn't show the apx when its in that mode.
Update: Was able to bypass activation by booting in to "Boot Android {No BP}" like on the droid x2.
Did you get bootstrap working?
TrojanZulu said:
So here is my problem, i've wiped my phone so many times to try out every rom/kernel that is posted. The last time i clicked the wrong file to sbf to unlock it and ended up flashing the 235 electrify pudding sbf. (had them all in the same folder...dumbass)
I was able to get rid of the 108 svf error by flashing the boot.img back to the photon ones via fastboot. But still would get the 106 anytime i went to try and flash the sbf.
I've tried in Ubuntu as well as windows 7 to flash it back but nothing has worked since it wants a 235 sbf, and it locked the bootloader.
So I said screw it and tried flashing the electrify 2.3.5 and it loaded up and everything, but i'm stuck on the activation screen and cant get past it. (tires to activate through Verizon)
The 2.3.5 update also removed the bootloader unlock in fast boot even with the id number.
So as easy as it was to flash it right to the electrify sbf, i think once the sprint 2.3.5 sbf is out i should be able to go back. Or once an unlock is found to unlock the bootloader, i can flash the files via fastboot.
I haven't tried messing around with nvflash, since my computer doesn't show the apx when its in that mode.
Update: Was able to bypass activation by booting in to "Boot Android {No BP}" like on the droid x2.
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
Was able to root it via the photon torpedo, even though it says it fails, it wont install the apks from the root program but it is rooted. Just downloaded them off market and ran root updater.
Was able to get system recovery to install and booted in to it just fine. but it soft bricks after i install the skiny4g zip file, boots up the first time all the way to the US Cellular boot screen then resets, and then loops the Moto Dual Core icon. Tried the "Boot Android {No BP}, and same effect, also tried just wiping cache and then wiping the system and still the same results.
Update: Finely got Skinny4G to boot, took 3 tires and the last time i wiped system 2 times in mounts and storage, shows up as sprint and 2.3.4 and its looking at sprint wireless towers, just trying to activate it now.
Phone activated on sprint, 3g works with out any issue, but the wifi and 4g is dead, now i just have to wait for the electrify unlock or 2.3.5 sbf for sprint.
Hey man, i did the same i flashed 235pudding by mistake, so i tried using the 2.3.5 sbf form electrify and it was going great until !switching phone to bp.. something else" then it stopped on 99% and failed to flash... i waited for 5 minutes just to be sure nothing else happened... it didnt
Then i pulled battery and powered the phone again this time it didnt said the "failed to boot 2" but it didnt started it just sits on the motorola dual core logo.
I pulled battery and powered it trying to go into RSD mode and it just doesnt appears :O
I pulled battery and tried to go into fastboot and doesnt appears either.... i just can turn it on and it sits on moto logo.... any help ideas? Tnks
__________________________________
Edit: I pressed vol up and down while power button and it finally appeared RSD mode.... but battery too low to flash, im gonna charge the battery on an external charger for an hour and report later if RSD lite actually recognizes the device.
_____________________________________
YEAH! After charging battery the process completed, im an international user so its not very imporanto to me Spront or US cellular, the phone boots good without my sim... but as soon as i put it in it says " modem did not power up (0)" so...
Does Anyone knows where to go form here?
Thanks
jokersax11 said:
Did you get bootstrap working?
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
Bootstrap install just fine after rooting.
Unbrick yourself
I want to thank Koriotto and everyone else who suggested and or tried the idea of flashing a 2.3.5 rom to save our backs. Now to everyone who has flashed 2.3.5 electrify pudding into their photons:
Disclaimer:
1°This will bootlock your phone until a working pudding for 2.3.5 is released.
2°I have no idea whether this will work with sprint whatsoever since I can't try it out being an "international" user, but at least your phone won't be a total brick. However, my common sense tells me this most likely won't work with Sprint.
3ºThere is a leaked Photon 2.3.5.sbf lurking amid devs, but as far I know it hasn't been released to the public yet. However, in case you do get ahold of it, please provide me the link so that we can try it out and see if we can help the Sprint folks get back to a stock Sprint rom. "Internationals" most likely won't care.
1°Try to get as much juice as you can into your battery.If you can, use someone else's fully loaded battery or charge yours with an universal battery charger (extremely cheap and easy to find). Your phone won't charge while in rsd or fastboot mode.
2°Download and install the appropriate Motorola drivers (x32 or x64 according to your windows flavor)
3°Download Electrify 2.3.5 SBF from here: https://rapidshare.com/#!download|8...19.0-19-release-keys-signed-USC-US.rar|530398
4°Get your device into RSD mode. If your loader says RSD mode, go to step 5. If your loader says nothing or is stuck on "Flashboot", don't worry. Power off your device and then press Volume down + power. The phone will turn on and then off. Then power on normally and you will be on RSD mode. If this doesn't happen the first time you try it, just keep repeating the forementioned process until you get into RSD mode.
5°Flash the SBF file you downloaded with RSD Lite
6°Live to win!
UPDATE: link from Team US Cellular seems to be down. I'll personally upload the file once I get home tonight.
Yeah. Praise US Cellular.
Sprint can I haz 2.3.5 yet?
Thanks so much for unbricking my Photon
Worked like a charm for mine !
Thanks !!!!
firtermish said:
I want to thank Koriotto and everyone else who suggested and or tried the idea of flashing a 2.3.5 rom to save our backs. Now to everyone who has flashed 2.3.5 electrify pudding into their photons:
Disclaimer:
1°This will bootlock your phone until a working pudding for 2.3.5 is released.
2°I have no idea whether this will work with sprint whatsoever since I can't try it out being an "international" user, but at least your phone won't be a total brick. However, my common sense tells me this most likely won't work with Sprint.
1°Try to get as much juice as you can to your battery.If you can, use someone else's fully loaded battery or charge yours with an universal battery charger (extremely cheap and easy to find). Your phone won't charge while in rsd or fastboot mode.
2°Download and install the appropriate Motorola drivers (x32 or x64 according to your windows flavor)
Click to expand...
Click to collapse
the download link doesn't work,would u plz give u a new download link,I need to unbrick my phone.
Thank u.
motiam4 said:
the download link doesn't work,would u plz give u a new download link,I need to unbrick my phone.
Thank u.
Click to expand...
Click to collapse
Original link went went down. Already corrected with one from Team US Cellular. Happy downloading
any updates with unlocking the bootloader for 2.3.5 flashed from sbf?
So i would like to apologize first off by saying i am a complete and total noob in every sense of the word. This is the first time trying to root any phone. ok so heres the deal, the phone powers up... FINALLY... and will load to the homescreen but reboots the device. I used the BAMF ICS rom and put in a PGIMGnewfirmwarepeople.zip... ive tried to do the *#*# but as soon as i bring it up i can only get maybe the * or at best the *# but then it reboots itself. I mess with cars on a daily basis but unlike a car part i cant bang or heat up the phone to get the desired result. i attempted to do this since i saw the video on the rezound redifined 4.0.3 ICS with nova launcher.. it was a video by driodzero?
i have no idea where to go from here... i would greatly appreciate any help anyone can provide
If it is indeed a network bootloop, try booting with the backpate removed. As long as the network signal isn't overly strong it should be able to get you in.
i think that was one of the things i did... i tried to let it boot with the back off, then with the back off and SIM card out... but to no avail. is there a way to somehow cmd prompt the *#*# in order to switch the problem... i dont know if this helps but it is S-ON
No SIM means no signal, which means no network bootloop. Must be another cause. Looking at the Bamf ICS thread, did you upgrade your firmware to ICS properly first. Hmm.
i will go back and look.. the problem is it will not let be go back and down grade img file...
twd420 said:
i will go back and look.. the problem is it will not let be go back and down grade img file...
Click to expand...
Click to collapse
Yeah, S-off is suggested eventually since it allows you to downgrade from the leaks. Risk of perma-brick in certain situations, like flashing a bad download of radios. But it helps more than hurts to have that freedom.
On S-on you also need to make sure the boot.img gets flashed seperate in the bootloader for a given ROM.
thanx i will try the wire trick to get it to S-OFF but right now i cant even get the phone to power up to the home screen
You can check the hboot/radio version in the bootloader to confirm firmware version. See what it says there.
Would attempt a clean reinstall of the ROM if it is indeed on ICS (hboot 2.21 or 2.25) firmware proper.
Then make sure to wipe system, davik-cache and cache, flash ROM twice, the patch Joelz has, and flash the boot.img as a PH98IMG.zip in bootloader. Then boot the ROM up.
i would definitely try that except i can not get it to power on, nor can i get it to charge... i think its bricked, since ive even gone to the standard battery as well as using different chargers. i greatly appreciate your insight
twd420 said:
i would definitely try that except i can not get it to power on, nor can i get it to charge... i think its bricked, since ive even gone to the standard battery as well as using different chargers. i greatly appreciate your insight
Click to expand...
Click to collapse
Did you use ClockworkMod by any chance? My first Rezzy charging capability fried on its own eventually, but aside from hardware failure: that recovery has been reported to have issues when battery drains down...
So today, i went to load up a book in kindle and it crashed a couple times in a row. I figured no biggy, and rebooted the phone (which I can't remember the last time I did, weeks ago).
Upon reboot, for some reason, I'm stuck in a boot loop. I get the white screen with the HTC logo for about 15-30 seconds, it shuts down, repeat. I figured no biggy, everything is stock, I don't care about anything on it, I'll just use the RUU to fix it.
That is where my problem begins. Unforunately, I am updated to 2.95, and the last release RUU is 2.89, so it won't let me install. I can get into hboot, I can use fastboot, so I used fastboot to erase the cache. Anything I select (factory reset, recovery, etc) in hboot just sends me back into the reboot loop. Manually flashing errors out because of the mainver discrepancy. I can't use the low version fix because I'm not rooted, so sure, let's try that... I started the process and unlocked successfully. Now the problem is, any recovery I've installed (4ext from the root thread, CWM5.8 from the boot loop thread) installs fine, but whenever I reboot recovery, again, boot loop. It doesn't matter whether the reboot comes from a fastboot command or selecting recovery reboot from inside hboot.
So, desperate (and somewhat ignorant), I booted up into Linux and tried the unbrick post, and of course, the device never shows up with the battery out, cause it ain't bricked. I was hoping somehow that I could use it to replace hboot, figuring that might be corrupt or something crazy like that (grasping at straws really).
What I really need is a 2.95 RUU, but that hasn't been released, and I figured if that didn't work, something is probably fried hardware wise.
I restored a stock signed recovery, so more or less, right now I'm back exactly where I'm started (other then the fact that my phone is now unlocked) and just not sure where to go from here. Any advice would be helpful. Thanks!
EDIT: I'm a moron, and I forgot to specify, but the phone is sprint. I also don't have any service on it (mainly used as an mp3 player) so I don't have any recourse through them.
I'm almost considering bricking the thing to change the hboot (I haven't done my homework on it yet) any thoughts there? Or is it not something I can do because of my problem?
Sounds like you didn't flash a ROM after getting into recovery.
You need to make sure you're unlocked, and flash a recovery...4ext recovery is highly recommended as it has a setting just to help s on users.
To start and get you up and going, i suggest downloading butterz sense ROM and placing it on your SD card.
Then you need to wipe everything except your SD card
Now flash a new rom, like butterz sense.
Reboot and you should be good
If not you may need to flash boot.IMG in fast boot.
to run an old ruu, you will need to get s off and for that you need a booting ROM.
Good luck!
Sent from my Evo 3D CDMA using xda app-developers app
hossman said:
Sounds like you didn't flash a ROM after getting into recovery.
You need to make sure you're unlocked, and flash a recovery...4ext recovery is highly recommended as it has a setting just to help s on users.
To start and get you up and going, i suggest downloading butterz sense ROM and placing it on your SD card.
Then you need to wipe everything except your SD card
Now flash a new rom, like butterz sense.
Reboot and you should be good
If not you may need to flash boot.IMG in fast boot.
to run an old ruu, you will need to get s off and for that you need a booting ROM.
Good luck!
Sent from my Evo 3D CDMA using xda app-developers app
Click to expand...
Click to collapse
Well, the problem is that I can't get into a recovery after I install it, I'm still caught in the boot loop... but I will try flashing the boot img. Thanks!
If you would like a quicker response/fix check your pm....i can try to help
Sent from my Evo 3D CDMA using xda app-developers app
Well, I did reflash boot.img with no success. I went to relock the phone and was just gonna throw it on the shelf for a couple weeks (as I do have another one), and when I did that using fastboot, it sent the command over and the phone received it, but it gave me a failure message. So now, it doesn't turn on, when I hook it up to the charger, I get the red charging light for about 10 seconds, and very occasionally when I remove the battery and put it back in the HTC logo appears for about 3-5 seconds before the phone cuts off again.
I'm starting to think there was some hardware issue. Since it had a screwy digitizer anyways (and I chose to get another evo for 65 rather then paying 30-35 for the ldc/dig combo), I'm just going to keep it around for parts and maybe play with it another time.
Your offer of help is greatly appreciated however, thank you.
EDIT: It doesn't seem to be truly bricked, or it isn't a recoverable brick... not really seeing the dim red light and the unbrick script doesn't detect it... the phone isn't in emmc mode... but I'm not hugely concerned with it now like I said.
LOL I'm a moron... my battery went dead during the whole recovery thing. Slapped another battery in and I am back to the original problem. Ignore my last post, basically.
At this point, I think that I might be possible that I can't get into recovery because, to the best of my knowledge, the "fast boot" option is ticked in the settings. Unfortunately, I can't get into the phone to change it, so even more chicken/egg stuff. Bleh. I'm still chugging along, any input appreciated. Maybe I can call HTC or Sprint and beg for an RUU?
thatdumbguy said:
LOL I'm a moron... my battery went dead during the whole recovery thing. Slapped another battery in and I am back to the original problem. Ignore my last post, basically.
At this point, I think that I might be possible that I can't get into recovery because, to the best of my knowledge, the "fast boot" option is ticked in the settings. Unfortunately, I can't get into the phone to change it, so even more chicken/egg stuff. Bleh. I'm still chugging along, any input appreciated. Maybe I can call HTC or Sprint and beg for an RUU?
Click to expand...
Click to collapse
Good luck!
So pull the battery, and put it back in.
Hold volume up and then press power.
Does that bring you to boot loader?
Does it say unlocked?
Sent from my Evo 3D CDMA using xda app-developers app
Been on this since last night with no success and have scoured XDA over and over til I'm dizzy with all the acronyms and developer talk lol.
Background: I installed a bad app 8 months ago and had to SBF my phone. I previously rooted my phone but had un-rooted so when it broke 8 months ago, the P4G was unrooted. Didn't do any lock or unlock stuff...whatever that is. So, I did an SBF using: "1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-198_6-CM-release-keys-signed-Sprint-US.sbf" since Sprint couldn't fix my phone. I'm was thinking I was taking it back to stock with this SBF but apparently I was wrong. Anyway, this resulted in:
System Version: 45.3.6.MB855.Sprint.en.US
Android Version: 2.3.4
BaseBand Version: N_01.28.07R
WebTop Version: WT-1.2.0-160
Kernel Version: 2.6.32.9 [email protected] #2
Build Number: 4.5.1A-1_SUN-198_6
ERI Version: 6
PRL Version: 51097
Problem: Everything was working great!!!!!! Until last night. I received an OTA update. When it was done, it rebooted and now all I get is a flashing dual core logo. So, I figure I'll just SBF again...piece of cake right? Nope...I get the SVF:106:1:2 error on the phone. So, I've tried to SBF from 4 different computers using RSDLite 6.1.4 and no dice. I have wiped data/cache/factory reset...no dice.
Can someone please, please, please tell me what the heck I need to do to fix this phone in easy to understand terms lol? I'm in a really bad spot here since my wife is freaking out as we have two handicap kids and I travel. My phone is a life-line...literally!
It seems on XDA, there are many similar cases but there is always a difference which doesn't apply to my phone and to my problem.
I thank you in advance and I think you developers on XDA are amazing in what you do! Ya'll scare the crap outta me with your abilities!
BillyD
No-one can help??? Please??? :crying:
Thanks!
BillyD
Someone may chime in to correct me as I may be wrong, but if the update was for 2.3.5 (which it most likely was) then the sbf's won't work. You can try to boot into recovery mode by pulling the battery and while holding down on the volume key until it says fastboot on the screen. Then keep toggling down until you see Android Recovery then press up on the volume key. It should say entering android recovery mode. Once you're there, press both up and down on the volume key and the menu should pop up. Toggle to wipe data with the volume key then hit the power button. When it's done wipe cache the same way, then reboot. It may work it may not, but that's all I've got.
stonesaber said:
Someone may chime in to correct me as I may be wrong, but if the update was for 2.3.5 (which it most likely was) then the sbf's won't work. You can try to boot into recovery mode by pulling the battery and while holding down on the volume key until it says fastboot on the screen. Then keep toggling down until you see Android Recovery then press up on the volume key. It should say entering android recovery mode. Once you're there, press both up and down on the volume key and the menu should pop up. Toggle to wipe data with the volume key then hit the power button. When it's done wipe cache the same way, then reboot. It may work it may not, but that's all I've got.
Click to expand...
Click to collapse
Thanks and I did try that as well yet forgot to mention it and as well...no dice. Just for the hell of it, I tried to SBF 198_7 thinking it was 2.3.5 (is it?) today. Again, I still get the SVF:106:1:2 error on the phone. Ugh.
I'm wondering...is it my bootloader that is hosed? If so, can I fix that or...do I just go ahead and try unlocking my bootloader (I'm assuming to do this a 'new" boot loader is installed...again, showing my limited knowledge here)?
Thanks!
BillyD
BillyDJJr said:
Thanks and I did try that as well yet forgot to mention it and as well...no dice. Just for the hell of it, I tried to SBF 198_7 thinking it was 2.3.5 (is it?) today. Again, I still get the SVF:106:1:2 error on the phone. Ugh.
I'm wondering...is it my bootloader that is hosed? If so, can I fix that or...do I just go ahead and try unlocking my bootloader (I'm assuming to do this a 'new" boot loader is installed...again, showing my limited knowledge here)?
Thanks!
BillyD
Click to expand...
Click to collapse
There is no 2.3.5 sbf for photon. But you can find one for electrify. You should root your phone and flash some files to work
Look here
http://forum.xda-developers.com/showthread.php?t=1798145
Sent from my Motorola Electrify using Tapatalk 2
198_7 is still 2.3.4. As far as I know, if you've accepted the 2.3.5 update, your bootloader is permanently locked and there is no way to sbf back to 2.3.4. or to unlock the bootloader. If the update is responsible for breaking the phone, then taking it in to Sprint may be your only option. Unfortunately, development has all but stopped on this phone and I doubt it will go any further.
pradeeppk said:
There is no 2.3.5 sbf for photon. But you can find one for electrify. You should root your phone and flash some files to work
Look here
http://forum.xda-developers.com/showthread.php?t=1798145
Sent from my Motorola Electrify using Tapatalk 2
Click to expand...
Click to collapse
Yes, I am now looking for the 1FF-sunfire-user-2.3.5-4.5.1A_SUN_USC_19.0-19-release-keys-signed-USC-US.sbf (Electrify) as this is what seems to work per this post http://forum.xda-developers.com/showthread.php?t=1403322
Can' find this sbf though! Crap...so close but still so far!
Thanks!
BillyD
Grab the lock unlock kit from the compendium under the dev section. It has it
Sent from a crazy mopho by a crazy mofo
Castik said:
Grab the lock unlock kit from the compendium under the dev section. It has it
Sent from a crazy mopho by a crazy mofo
Click to expand...
Click to collapse
Thanks...will do!
BillyD
Thank you XDA!!!!!!!!!!!!
BillyDJJr said:
Thanks...will do!
BillyD
Click to expand...
Click to collapse
Well, once again the devs on this site have saved my phone! Yes, I spent probably 40-48 hours getting it to work, gaining an understanding as well as tracking down software from broken links in the process but in the long run, it's worth it to me. The Photon 4G is a great phone and there is simply no reason for me to get rid of it!
So, I just wanted to drop a note and say thank you XDA! Motorola was useless...Sprint was more useless. This makes me want to learn C and Java programming but I am an IT consultant and no time to switch careers! Great stuff gents...great stuff!
Thank you once again XDA!
BillyD (also BgDaddy)