Hello, First time Poster here, please bare with me...
I really shouldn't of touched this.....
I have an Atrix w/ the newest updates to it, and attempted to unlock the phone. Using the guide from atrix4ghacks.com Everything started well, then it failed while writing to the device. Now, when I attempt to boot, I get the message
SVF:405;1:2
Failed to boot 0x1000
1- RSD
2-Fastboot
3-NVflash
4- BP HW Bypass RSD
5-BP HW Bypass QC DLOAD
6-BP HW Bypass & Boot AP
7-BP HW Bypass BP only
8- BP SW Bypass RSD
9- Andriod recovery
10- Boot Andriod (no BP)
11- Device UID
12- Console
13- Early USB
14- BP tools
I can get into fastboot, though I honestly am not sure what to do from there. I have the fastboot s/w downloaded, along with the gingerbread OS. When I tried to execute the command via Command prompt. I keep getting unknown command errors (yes, directories within the command are good).
Did I just kill my phone?
I have found a few posts here related to this, though I havent found what seems to be a solid answer to a "fix" for this. I would highly appreciate if someone could try to help me with this.
Sorry, I have broken a noob rule (was pretty late when I watched the video), I thank you all in advanced for any help
STOP!!! YOU HAVEN"T KILLED YOUR PHONE JUST YET!
BUT IF YOU SBF YOU WILL!!!
Go into fastboot and repeat all of the unlock commands, reboot and your phone should boot fine after that.
Ok, I will give that a shot!
Hopefully this will work. THANK YOU!
Ok, is there a way to force charge this?
I had it hooked up and when I was going to execute the flash, it gave the message of battery too low to flash.... Will just leaving it plugged in be ok? or is there a button function I can do that will ensure it charges the unit?
Thanks again
Grumbles said:
Ok, is there a way to force charge this?
I had it hooked up and when I was going to execute the flash, it gave the message of battery too low to flash.... Will just leaving it plugged in be ok? or is there a button function I can do that will ensure it charges the unit?
Thanks again
Click to expand...
Click to collapse
Ugh... from what I heard the battery won't charge while in fastboot mode. You need a standalone charger or a different battery.
So, it doesn't let you get into fastboot at all, huh?
I was afraid of that- I think ive found the solution to that on this link:
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
That is def. something I can do, and will try. Otherwise, to answer your question. The PC sees the device- It is then the device that says battery is too low to flash (on any mode you choose). Once that message is shown, it wont allow me to access it at all.
Worse to worse, I will take a trip to the att store, or somewhere close to see if they have a wall or base charger. If the doc has a separate power connector, I may try that...
Grumbles said:
I was afraid of that- I think ive found the solution to that on this link:
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
That is def. something I can do, and will try. Otherwise, to answer your question. The PC sees the device- It is then the device that says battery is too low to flash (on any mode you choose). Once that message is shown, it wont allow me to access it at all.
Worse to worse, I will take a trip to the att store, or somewhere close to see if they have a wall or base charger. If the doc has a separate power connector, I may try that...
Click to expand...
Click to collapse
The factory cable would allow you to use the phone without the battery, but it might take more money and time to make then you think.
From what I understand, RSD threw you an error when you were flashing bootloader unlock.
Anyway, you need to find a way to charge your battery and they do the fastboot unlock commands.
If that doesn't work you need to reflash the pudding SBF, (make sure you install the drivers Windows x64 version here prior to flashing and that your phone is recognized in RSDlited)
Get the correct pudding file from here: http://forum.xda-developers.com/showthread.php?t=1136261
Use instructions here (start at step 1) : http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
Note that after pudding is flashed successfully and you do the unlock commands, you will get a failed to boot error (seems like what you have now). You need to redo the unlock commands in fastboot and it will fix the problem.
Good luck.!
Alright!
Got the cable completed and works!
So, battery situation is handled, now to follow your steps
THANK YOU! I will report back and let you know.
Ok,
Clearly I am doing something wrong here.....
I followed the instructions using the newest Pudding_preroot.sbf file, and the RSD software sees the device (as a SE flash not a NS if that matters) and will start the flashing process.
Everything works to plan until the phone does its reboot(99$ executed), gives the fail to boot message again. Then wants to start back up in RSD mode.... The RSD application on the otherhand, it seems like its trying to switch the phone to"BP passthrough mode" I do not see that exact option, and after it failed while rebooting to RSD. I tried to move it to fastboot, BP HW Bypass RSD, and finally BP SW bypass RSD... All with the same failure on the RSD screen:
"Failed Flashing Process. Phone (0000): Error switching to BP Pass through mode (0x70BE); phone connected"
I have a funny feeling that this part is obvious, for that I am sorry for my ignorance.
I am pretty sure this thing is toast...
After getting nowhere after step 12, and multiple attempts to install the pudding_preroot file. I did some searching around and found multiple atrix users that would get the same issues. From the flash showing up as SE rather than NE, to the constant failing during the flash via RSD lite, with the same failure errors.
I noticed a "NV flash" option, and found this link that could establish a recovery USB driver to the phone. Do you think this maybe my next best route?
http://forum.xda-developers.com/showthread.php?t=1123429
My factory cable is good, so that option IS open..... Though I am starting to think this is toast.
We cannot use NVFlash unless we get the SBK (signature file). Currently, we do not have it. Motorola does, so plead to them
OK, well now it decided to only mount itself as a unknown APX device... Not sure the whats or whys there. Nothing has changed since the last failures?
Hey man, I think RSD shows the flashing process as failed since it can't fully reboot the phone.
Go into fastboot mode and try doing the unlock commands. (try this twice if ita fails after the first time).
In the worst case scenario if unlocking fails no matter what, you can flash a complete 2.3.4 rom via SBF and that should get you back up and running.
Let us know how it goes.
Remember, if you can get into RSD or fastboot - the phone isn't bricked yet!
Related
was going from gingerblur 2.5 on 1.56 then sbf to 1.83 and now it just says that after flashing.
tried to sbf 1.23 and 56 and same thing
am i doing something wrong?
in the rsdlite it sees the phone but says n/a for everything
Please HELP
Updated: I tried again fresh start on different computer and it worked!
must have been error in download, unzip, or there is something conflicting on my pc
hi i have same problem , went i flash OLYFR_U4_1.8.3_SIGNED_OLPSATTSPE_P013_HWolympus_1g_Service1FF.sbf ,
always after finish and rebooting then failed to boot 4 error raise,
i have use other computer to flash and the result is same failed to boot 4
i have install
- RSD Lite and 5.0
- Handset_USB_Driver_32_v4.9.0
plz can anyone help me ?
Sbf 4.1.26 or 4.1.57, then OTA to 4.1.83, root, sideload enable, flash CWM, flash GingerBlur.
bullghost said:
hi i have same problem , went i flash OLYFR_U4_1.8.3_SIGNED_OLPSATTSPE_P013_HWolympus_1g_Service1FF.sbf ,
always after finish and rebooting then failed to boot 4 error raise,
i have use other computer to flash and the result is same failed to boot 4
i have install
- RSD Lite and 5.0
- Handset_USB_Driver_32_v4.9.0
plz can anyone help me ?
Click to expand...
Click to collapse
i have the same problem
aaurnab said:
i have the same problem
Click to expand...
Click to collapse
please help
CaelanT said:
Sbf 4.1.26 or 4.1.57, then OTA to 4.1.83, root, sideload enable, flash CWM, flash GingerBlur.
Click to expand...
Click to collapse
thanks bro, i thinks that's the best way to update till 4.1.83,
here a little experience i have done
first time i try flash sbf 4.1.83 failed with that error booting,
and pull battery and back again to turn off the phone, and i flash the 1.26
then success with sim card inside,
iam not happy with failing on flash 4.1.83, then i thought the 4.1.83 sbf file is corrupt then i redownload again , after finish download,
i do the second time flashing with new 4.1.83 sbf
this second time is so frustrated, couz it fail again with same error.
until i have success full recover my atrix i do over 10 time flashing
and changing between computer and my notebook
and changing from windows 7 and windows XP
flashing random sbf from 1.83 and 1.26
the lasting i lost my hope , then suddenly the flash was success, WTF ,
lasting i remember is i pull the battery and pull out the sim card , then put back the battery, and do the flash,
the last time i flash 1.26 sbf
i thing
there is something no right with driver or RSD Lite not sync or missing something
until now iam still don't know how to solve it ,
pls anyone can find out what the problem and how to solve it
After about 4-5 hours and 7-8 tries using sfb method to upgrade to 1.83, I finally have a working phone again.
As to how I got stuck on the:
boot fail 4
starting RSD
and in RSD Lite, the phone's device name showing up as "SE Flash Olympus"
I decided to do a few things.
1. Go download the newest USB drivers. the 2.00.52 is what you should be on. If you can't find them, go to Motorola website and get MotoHelper 5.0 or whatever..install and then update your drivers. Restart your pc and keep trying to update your drivers until you get to USB 2.00.52 drivers.
2. USE THE ORIGINAL DATA CABLE THAT CAME WITH THE PHONE.
3. Make sure the connections are not loose at all (could've been why mine was messing up)
4. If you already have motohelper installed...go to the 'driverinstaller.exe' change operation mode to clean and reinstall, make sure the phone is unplugged. and click on start. (note, this part will be anywhere from 2 - 5 minutes depending on speed of your computer)
5. Restart RSD Lite, make sure you're using the latest one, and 'Run as administrator'.
**Go to config>Flash/Flex options... > only "check" Restart after Flexing..**
6. Now, I learned this the hard way...and many forums have it up there... GET YOUR BATTERY TO ABOVE 80% or IT WILL FAIL. (I had to go to a friend's at midnight to charge my battery from his atrix...hahaha)
7. Now turn your phone on again and it'll go to the "failed to boot 4 starting RSD" ...
8. Next, plug it in to your USB cable and click "Show Device" and then click once under the "USB 1 line" to view the device information at the top left. (Everything should be N/A except for your bootloader and you will also read "NS Flash Olympus now, instead of the SE Flash Olympus)
9. Put that '1.83_pudding.sfb' file in the "C:\ " directory to avoid any further complications.
10. Select the "...." browse to the '1.83_pudding.sfb' file and click start. It should work.... Now if it doesn't work... try and try again...
What I did was switched back and forth from 1.23 to 1.83... when I got mine to work, the device was registering as "SE Flash Olympus".
And for the longest time under bootloader, it would register as N/A...I finally decided to switch cables and it worked... once again, make sure to follow these:
* Full battery/80% above
* Stock Atrix USB cable
* 2.00.52 USB drivers
* RSD Lite 5.3.1
EDIT: GOOD LUCK! PM me if you need more assistance as those forward to XDA app
vash8806 said:
After about 4-5 hours and 7-8 tries using sfb method to upgrade to 1.83, I finally have a working phone again.
As to how I got stuck on the:
boot fail 4
starting RSD
and in RSD Lite, the phone's device name showing up as "SE Flash Olympus"
I decided to do a few things.
1. Go download the newest USB drivers. the 2.00.52 is what you should be on. If you can't find them, go to Motorola website and get MotoHelper 5.0 or whatever..install and then update your drivers. Restart your pc and keep trying to update your drivers until you get to USB 2.00.52 drivers.
2. USE THE ORIGINAL DATA CABLE THAT CAME WITH THE PHONE.
3. Make sure the connections are not loose at all (could've been why mine was messing up)
4. If you already have motohelper installed...go to the 'driverinstaller.exe' change operation mode to clean and reinstall, make sure the phone is unplugged. and click on start. (note, this part will be anywhere from 2 - 5 minutes depending on speed of your computer)
5. Restart RSD Lite, make sure you're using the latest one, and 'Run as administrator'.
**Go to config>Flash/Flex options... > only "check" Restart after Flexing..**
6. Now, I learned this the hard way...and many forums have it up there... GET YOUR BATTERY TO ABOVE 80% or IT WILL FAIL. (I had to go to a friend's at midnight to charge my battery from his atrix...hahaha)
7. Now turn your phone on again and it'll go to the "failed to boot 4 starting RSD" ...
8. Next, plug it in to your USB cable and click "Show Device" and then click once under the "USB 1 line" to view the device information at the top left. (Everything should be N/A except for your bootloader and you will also read "NS Flash Olympus now, instead of the SE Flash Olympus)
9. Put that '1.83_pudding.sfb' file in the "C:\ " directory to avoid any further complications.
10. Select the "...." browse to the '1.83_pudding.sfb' file and click start. It should work.... Now if it doesn't work... try and try again...
What I did was switched back and forth from 1.23 to 1.83... when I got mine to work, the device was registering as "SE Flash Olympus".
And for the longest time under bootloader, it would register as N/A...I finally decided to switch cables and it worked... once again, make sure to follow these:
* Full battery/80% above
* Stock Atrix USB cable
* 2.00.52 USB drivers
* RSD Lite 5.3.1
EDIT: GOOD LUCK! PM me if you need more assistance as those forward to XDA app
Click to expand...
Click to collapse
People 51_OLL iron-4.5.2A-lite 5.6 rsd 49_SIGNED_STABLE45LAOLYMPGBPERAR_P011_A026_M001_HWpd_Service1FF with ... and my error:
"Failde to boot 4"
rsd starting mode
I am reading is the battery problem that has to be for 80 %+...
If I turn on the power but the volume key + I fastboot protocol enters
If it lights only the error:
"Failde to boot 4" starting mode rsd
I can do twice the iron sbf with 2.3.6 official stock continues to give me the same error.
Lei may be because the battery is not 100% so fails.
How do I charge if the wall charger no load and light me alone with the legend:
"Failde to boot 4" rsd starting mode.
It can be for this, because this is not a 100% Bateias??
Another query may be that by command fastboot mode can be fixed??
I was following this video on instruction on unlocking my atrix on youtube titled "Motorola Atrix: Unlock and Upgrade to GB - Unlock P1"
My atrix was already updated to 2.3.4
Now Using RSD Lite.. idk what happened, the process failed.. and everytime I turn on my phone, it tells me "OS not found" or something like that.
It says:
SVF:105:1:2
Failed to boot 0x1000
NO OS detected, going to RSD mode in 5 seconds
Press a key to stop count down
Available Modes are:
1.RSD
2. Fastboot
3. NvFlash
4. BP HW Bypass RSD
5. BP HW BYPASS QC DLOAD
6. BP HW Diag & Boot AP
7. BP HW Bypass BP Only
8. BP SW Bypass RSD
9. Android Recovery
10. Boot Android (No BP)
11. Device UID
12 console=ttyS0, 115200n8
13. Early USB Enumeration
14. BP Tools
Can someone please help my get my phone working again.. I can't even live like a day without my phone. Is my phone hardbricked or is there any way to revive it?
Any help would be appreciated.
Thanks
try the next step
Just continue the fastboot commands and you should be fine, same thing happen to me
Sent from my MB860 using XDA App
Javi97100 said:
Just continue the fastboot commands and you should be fine, same thing happen to me
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Which fastboot commands, because I tried to use the ones such
fastboot flash preinstall preinstall.img
fastboot reboot
but nothing worked.
Try this
fastboot oem unlock
(Then it will give you a code, and type it again with code at the end)
Then when phones says unlocked
Type
fastboot reboot
Sent from my MB860 using XDA App
cpatel90 said:
Now Using RSD Lite.. idk what happened, the process failed.. and everytime I turn on my phone, it tells me "OS not found" or something like that.
It says:
SVF:105:1:2
Failed to boot 0x1000
Click to expand...
Click to collapse
Guys, where do you get the courage to do the unlock process that bricked so many phones without reading instructions?
When flashing pudding over OTA 2.3.4, Failed to boot is a common error.
You need to redo the fastboot unlock commands and all will be fine.
This is explained in the pudding thread, and gets explained every day again and again with each new thread that newbies create.
xploited said:
Guys, where do you get the courage to do the unlock process that bricked so many phones without reading instructions?
When flashing pudding over OTA 2.3.4, Failed to boot is a common error.
You need to redo the fastboot unlock commands and all will be fine.
This is explained in the pudding thread, and gets explained every day again and again with each new thread that newbies create.
Click to expand...
Click to collapse
Also if you do some looking around you'll find this http://forum.xda-developers.com/showthread.php?t=1182871 which I think was a SUPER easy way to unlock my bootloader and I didn't run into any of the issues that so many have ran into.
From unlocked/rooted GB Atrix
thanks for the help guys.. but i think its over for my phone.
it doesn't even turn on anymore. the green light comes on for one second and turns back off. i think i'll just have to get a new phone.
cpatel90 said:
thanks for the help guys.. but i think its over for my phone.
it doesn't even turn on anymore. the green light comes on for one second and turns back off. i think i'll just have to get a new phone.
Click to expand...
Click to collapse
You weren't a hard brick. You just didn't complete the steps. Did you do something else to it since your initial post? Sounds like your battery is drained, which means you need to charge it externally.
cpatel90 said:
thanks for the help guys.. but i think its over for my phone.
it doesn't even turn on anymore. the green light comes on for one second and turns back off. i think i'll just have to get a new phone.
Click to expand...
Click to collapse
uhh... sounds like your battery is drained. find someone who can charger your battery (another Atrix owner, or a Droid X owner) and try again PROPERLY.
you were trying to flash PREINSTALL to your phone? that is NOT the OS. that roots your phone once it's already installed. you need to install the SYSTEM.img and related files. you really need to read the entire guide as it so far looks like you didn't read anything.
you need to use moto-fastboot to flash System images, not regular fastboot.
http://forum.xda-developers.com/showthread.php?t=1138092
use these images and this guide, which coincidentally warns you NOT to RSD from the stock 2.3.4 and is stickied at the top of the dev forum.
http://forum.xda-developers.com/showthread.php?t=1160408
i seem to have hard bricked my atrix, doing the same thing.. well, my brother did anyway. but i somehow forced it to download mode. and re-flashed it. Works perfectly.
caleb4992 said:
i seem to have hard bricked my atrix, doing the same thing.. well, my brother did anyway. but i somehow forced it to download mode. and re-flashed it. Works perfectly.
Click to expand...
Click to collapse
that's a soft brick.
svf :105.1:2
failed to boot 0x1000
show this..........
i cant to move it to android recovery cause there no option to move
after showing this error automatically switch off my phone.....
any solution
bivrat said:
svf :105.1:2
failed to boot 0x1000
show this..........
i cant to move it to android recovery cause there no option to move
after showing this error automatically switch off my phone.....
any solution
Click to expand...
Click to collapse
Yea, thats a hard brick
Sent from my MB860 using XDA App
bivrat said:
svf :105.1:2
failed to boot 0x1000
show this..........
i cant to move it to android recovery cause there no option to move
after showing this error automatically switch off my phone.....
any solution
Click to expand...
Click to collapse
bivrat,
You've asked this same thing maybe like 5 times already and each time we've told you that there is no fix and you have to get a new phone.
Need urgent reply
Guys.. i have a favour to ask!
m in a search for a second hand moobile and found this ATRIX 4G unlocked edition which has run into this problem!
"A recent Over The Air upgrade 2.3.6 to the phone (which should have been avoided on a rooted phone) has made the phone non working.
The phone does not boot, and displays the message:
Failed to Boot 1...
Entering RSD Mode."
Guys please let me know if this coud be fixed or not, as i am in a real mood to buy this one!
bivrat said:
svf :105.1:2
failed to boot 0x1000
show this..........
i cant to move it to android recovery cause there no option to move
after showing this error automatically switch off my phone.....
any solution
Click to expand...
Click to collapse
Did you try the Unlock v4.2 app from this site? Option 3 of the menu very well might fix it for you. Well worth a shot if you haven't tried it yet.
PC will not identify phone in RSD or fastboot. I have tried all drivers I can find, have uninstalled and reinstalled all software, the drivers install in each mode but RSDlite or the official moto software updater will not ID the phone when connected...
I have tried 64 and 32 windows and 3 different cables just to be sure....
Anyone have an idea what to do? I have locked an unlocked this thing once before the 4.5.91 update and again after. I used the official Motorola Software Updater to "update" back to locked stock and have had this issue ever since then....
Fixed: Belkin USB print and storage drivers had to be removed.
* delete * 10 chars
anyone??????????????
Simple question, do you have debugging turned on? I was having a similar problem, when i realized it was off I totally face palmed myself
Yesy I have tried everything I can think of... the issue is before booting into android not after... something is blocking my phone from getting picked up by RSDlite and the moto update tool... everything in android functions fine, i have turned USB debug on and off both.
I was able to root through fastboot with no issues so it is ok, but I will be d*&$^d if I can get rsd running so I can unlock... it's not like this is new to me I have unlocked this thing twice before...
halfevildruid said:
I was able to root through fastboot with no issues so it is ok, but I will be d*&$^d if I can get rsd running so I can unlock... it's not like this is new to me I have unlocked this thing twice before...
Click to expand...
Click to collapse
You are trying to unlock the same atrix?
Once it's unlock, it remains!
Even if it doesn't show it at booting(maybe disapeared after installing a rom..)
Sent from my MB860 using XDA App
Nope. I am definately locked again. I flashed the official motorola GB software update over my existing GB software to attempt to revert to locked and stock again. It worked but now I am unable to unlock. RSDlite AND the same Moto update do not see my phone in RSD mode.
halfevildruid said:
Nope. I am definately locked again. I flashed the official motorola GB software update over my existing GB software to attempt to revert to locked and stock again. It worked but now I am unable to unlock. RSDlite AND the same Moto update do not see my phone in RSD mode.
Click to expand...
Click to collapse
Actually, once a bootloader is unlocked, its unlocked for good. By reflashing to stock, all that you did was copy over pudding (the SBF file that you flashed when you unlocked the bootloader). This hides the "Unlocked" text in the top corner. To reshow this text and regain access to locked fastboot features, you must reflash pudding via the "Unlock SBF file" available here:
briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
Im not sure why you can't get into RSD mode. Try the following:
- Insure that your volume buttons work
- Unplug phone, take out battery
- wait 10 seconds
- reinsert battery
- hold down UP (not down, I made that mistake once) volume button firmly
- press and hold power button
- phone should say "Starting RSD Mode"
To enter Fastboot mode do the same steps as above, only press the down volume button instead. When the word "FastBoot" appears, press the up volume button.
I can get into rsd and fastboot on the phone. The driver in rsd installs as se flash where it used to install as nf flash. Fastboot is working fine, I was able to reroot.
The problem is rsd does not identify my device and allow me to flash. I am thinking it is in the se flash driver instead of the previous nf flash driver.
Anyone have an opinion?
Sent from my MB860 using Tapatalk
SOLVED!!!
So I figured it out! As it happens I picked up a new Belkin 750 router with networked USB support a few days back for my ext drive and printer. Apperently the Belkin drivers were the culprit! After uninstalling them everything picked up and ran like it should. Some of you devs and folks creating guides should note this in the posts so we can give folks a heads up in case it happens to them. I am sure this will happen to someone else.
after flashing 1FF-sunfire-user-2.3.5-4.5.1A_SUN_USC_19.0-19-release-keys-signed-USC-US i get failed to boot 4
tried http://androidforums.com/4545287-post3.html with no rezult
tried to flash SBF: 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_5-CM-release-keys-signed-Sprint-US , rds lite 5.6 writes - waiting for re-enumeration,
phone writes - svf : 106:1:2 sec_exeption: b655, eddc, eb
plus nothing hepens when i try to power on phone with vol-, vol+ and both keys
i have already delete rsd and drivers and reinstall them
please help me
you cant flash 2.3.4 on a phone with 2.3.5. it does not work. not sure where to start but can you get to fastboot or rsd mode?
---------- Post added at 07:59 PM ---------- Previous post was at 07:49 PM ----------
also was your bootloader unlocked? any customizations at al re.....recovery or rom etc....can you give a lttle more info.
If I understand correctly you are no longer able to get to rsd mode (power and vol +) when booting correct? If so you are pretty much S.O.L. When you flashed the 2.3.4 sbf it tried to revert your locked bootloader back to 2.3.4 which is a no-no on a locked 2.3.5. Your best bet is to start coming up with a good excuse and take it back to sprint.
Truely need more info. I just a week ago did the same thing to an electrify. I at this time cant tell you the exact steps i took took fix it but it can be fixed. You are not completly screw as of yet and if you look around you will find all you need to fix this but it comes from different sources and some of the info was for different phones but worked on the photon which made it work on the electrify.
Like i said the given info is not enough to give you what you need to do and although the mopho and electrify are similar in almost every way there are a few things that differ.
I dont believe that your "S.O.L." because i just did the same thing and brought it back.
Open a command prompt as administrator and plug your phone into you computer and see if its recognized by fastboot or adb or rsd lite.
hoslayer13 was helping me with this issue and had a lot of info that helped. maybe he will chime in who knows.
More info!!!!!
After the phone says failed to boot 4 if you leave it at that screen for about a minute does it say "starting rsd mode" under failed to boot 4? If so your best bet would be to follow the steps here: (http://forum.xda-developers.com/showthread.php?t=1798145) as long as you originally started with a Photon running 2.3.5. I you can flash via rsd, make sure you remove your sd and sim card. For some reason it seams to work better. Also plug the USB cable directly to the computer (no hubs, no usb extension cables) they can cause issues with rsd. I hope you've already resolved the issue and I'm giving you advice you don't need.
@ rhewins2268. That is exactly the reason I asked "If I understand correctly you are no longer able to get to rsd mode (power and vol +) when booting correct?" If he can boot to rsd then the link I provided is a fix. Which by the looks of it may be what he was trying to do in the first place considering the electrify sbf he mentions is the first step in bringing a Photon back to stock, or back from a soft brick. You are correct more info would be helpful, but by reading what he did it sounds like more than likely he was on 2.3.5 which is an unlock-able bootloader (for the time being) and trying to downgrade (SBF: 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_5-CM-release-keys-signed-Sprint-US) on a locked 2.3.5 bootloader can and more than likely will perma brick the photon. If when booting he can not see the boot options, i.e. fastboot, android recovery, rsd mode etc. he's bricked. There is no way to flash anything if the device has no, or a corrupted bootloader to start those processes.
So my question is that is it possible to flash China rom to global version and get OTA upgrade to android 12 as I heard china devices are getting zui 13?
It's available here. If you attempt to flash it, make a .qcn backup of your nv data first. You can attempt to flash it with these instructions (7th post), only if you have all the drivers necessary for both LMSA/RSA & QPST/QFIL and know how to set it up correctly (firehose config needs to be set to not erase; you will need to set storage type to ufs).
Problem is i cant unlock the bootloader yet cause adb devices command doesnt show up the phone. Tried couple of drivers but didnt work.
You don't need to unlock your bootloader as it will most likely be relocked once you flash it. Do you have these (not just for OnePlus8, for all Qualcomm devices)?
Ok I was able to connect and unlock bootlader. I am downloading China rom now and will try flashing using the instructions. Hopefully it doesn't get bricked.
Make a backup of your nv data (QCN) first. Then do both edit 1 & edit 2 of the instructions posted and make sure to do it carefully, or if you're brave enough do only edit 2.
So I followed the instructions and after flash it went black screen. It doesn't boot or get detected by RSA. Only thing I can do is QFIL detects COM6 port when connected
Force shut it down, hold power until screen flashes on. You forgot to check "Reset after downloading". If that doesn't work you will need to use the other firehose protocol (lite) and that should restore it to a booting state.
&(*) said:
Force shut it down, hold power key for until screen flashes on.
Click to expand...
Click to collapse
I think its in EDL mode cause nothing else happens. Do you use telegram or whatsapp?
Holding power doesn't do anything? It should at least shutdown and reboot and if the screen briefly flashes then yes it is in EDL. You will need to flash it back to Global or whatever was previously on it. Did you unlock the bootloader first or not? That might have been the issue.
Nope nothing happening when holding shutdown. When I hold for 15 sec then it resets phone but always black screen. I can understand that it reset from QFIL cause COM port gets disconnected then reconnects. I think its hardbricked now and there is no QFIL rom I could find so have to take service center then...
bukeyolacan said:
Nope nothing happening when holding shutdown. When I hold for 15 sec then it resets phone but always black screen. I can understand that it reset from QFIL cause COM port gets disconnected then reconnects. I think its hardbricked now and there is no QFIL rom I could find so have to take service center then...
Click to expand...
Click to collapse
Okay, try flashing it again with the firehose config option checked "Reset after Downloading". You used EDL to flash it the first time, right? If you still get a black screen you will need to flash the original Global firmware back onto it. You state that RSA doesn't find it? Did you unplug and plug it back in or leave it plugged in?
One other thing you might of forgot to change, storage type to UFS.
I tried firehose flash many times but keep getting sahara fail error or process fail. Storage type was always ufs I never touched it
Use firehose lite and check to see if device manager shows any yellow exclamations now.
Tried lite now, there is android device in device manager with yellow
Is it possible for you to connect remotely via teamviewer or do you know someone that can fix if I pay?
You can fix it. Just try updating the driver automatically and see if it finds it first
&(*) said:
You can fix it. Just try updating the driver automatically and see if it finds it first
Click to expand...
Click to collapse
I think its out of my level now, would need some help with it
The driver package you installed will read the USB ID and should find it within DriverStore. Right click on the android device that has the exclamation and update the driver.