[Q] Defy keeps rebooting after showing M logo - Defy General

I flashed my phone which had the new US OTA update with defy_2.21boot_only.sbf and now it keeps rebooting after 1 or 2 min (with the M logo). The phone is NOT rooted and does not have clockworkmod recovery yet. HELP!

Pull battery,
put battery back in holding the VOL-Down until the android pops up...
press VOL-Up and VOL-Down at the same time.
Next screen is for wiping and updating.
Wipe Data/Cache
When done, go to REBOOT and hold down the VOL-Up to go into Flash mode. and flash with RSD 4.9
http://www.multiupload.com/ZZ4TU8W7UQ (This is for US T-mobile.)
You should be good to go...

Thanks for your advice jeffokada81; but when loading the file, the Start button is grayed out. The only sbf file that enable the Start button is the Chinese JDGC_U6_0.26.0_SIGNED_USAJRDNPRCB1B50AA02F.0R_JORDANGCCORE_P011_A023_HWp3_Service1FF and... after flashing, the phone restarts; the screen turns black but RSD's status shows as "connected". Still need HELP!

The phone is now back in service!!!
For those of you that have the same problem, I boot my computer to Xp (rather than W7, run as Admin) RSD 4.9 flashes the file that it did not in W7. The phone is now back in service! Thanks for your quick response Jeff!

Yea, IDK why, but RSD never quite worked for me in W7 either. Maybe because Motorola still has all their employs on XP, so they have had no need to make it compatible with W7.

ttld1oh1 said:
For those of you that have the same problem, I boot my computer to Xp (rather than W7, run as Admin) RSD 4.9 flashes the file that it did not in W7. The phone is now back in service! Thanks for your quick response Jeff!
Click to expand...
Click to collapse
Could you specify which sbf did you flash?
thanks

I have no problem with RSD Lite on W7 64bit. Try reinstall or check for update.
Maybe try change SBF file name, sometimes the file name is to long for some system.
Sent from my MB526 using Tapatalk

Related

Defy doesn't boot

Hello all
Today i've got a problem:
My defy boot but it stops at the red "M" of Motorola.
I tried to flash a new rom with rsdlite but the defy isn't recognize in bootloader.
The "wipe data" return an error => error mouting /data!
Am I totally ****ed ?
Thx
Wipe data should work, try to install the last version of drivers and install another rom, and pray.
First of all, did you flashed a SBF before the phone stuck on M??, if yes, try wiping data on stock recovery, are entering properly to the booloader mode??(POWER + VOL +)
First , thx.
I tried the wipe data but apparently, the "data" doesn't exist or the phone doesn't get the permission to wipe it => "error moutin /data!"
I tried to flash a new rom by "VOLUM UP + POWER" but rsd lite 5.3.1 or 5.6 don't recognize the phone. I've got the drivers.
EDIT: And in the stock recovery the wipe data works but do nothing.
I have the same problem and what i did!
1) pull out the battery and put it back(and let it of)(must be charged)
2)start rsdLite4.9
3)sellect the sbf(with shorter name)
4)conect the phone in of mode (rsd recognize like xxxx3630)
5)start the instalation
(I use ...3.4.2_179-002 and it works great any time)
instalation works good and the phone starts it self
Ok I'll try that, but before the phone doesn't start, I had charging problems and the phone wasn't recognize in USB. So I think this won't do anything.
I try it
charge in other phone!
or use McGuyver method!:
find other charger, cut the head and you will see 2 wires
oue red and one black, red is +pole, black is -pole
pull out the battery and conect red to +pole on battery and black to -pole
let it for two hours to charge(can try after one hour)
then try to flash SBF!
Ok.
What do you mean by "connect the phone if on mode" ?
Ised "of mode"
means it is stopt
just put the battery in the phone and conect without start it in botloader
Ok thx but when I connect it the phone starts and goes to the "M" and isn't detected :s
start in botloader mode if you can! (volup+power)
Give it first "wipe data factory reset" from recovery stock
try to see if it start normaly with old SBF olready flashed
if not, start in botloadermode and flash SBF
It doesn't start with the old sbf.
I'm waiting for the battery (charging in an other defy).
EDIT:
Not detected by rsd lite. I tried to detect an other defy with the same battery andit works well. So I think my phone is definitely dead :/ You don't think so ?
no i do not!
what sbf are you flashed
sent from "My Precious" MB525 using XDA App
Ok
I took this version : 3_3.4.2_164-003 Androïd 2.2.2
(the first of this page : http://forum.frandroid.com/topic/54848-rom-stock-android-froyo/)
try this SBF
did you chec the sdcard(could be a problem with it)
RSDlite 4.9 View attachment 894277
Yep I already format the sdcard.
Ok try this one, but does the SBF change the detection of the defy in rsd ?
EDIT: the link seems to be broken :s
my nik is yahoo id
call me
It will be a little bit difficult 'cause i'm french :s
Do you have a other link for the sbf ?
http://www15.zippyshare.com/v/45995480/file.html
View attachment 894304
Thx I try this one
EDIT: Defy is still undetected :s
ps: My friend's defy is detected
I don't understand... Maybe an hardware problem :/

[Q] Flash mode not working properly.

So after my comedy of errors that was my playing around yesterday, I got my phone working again. Now I want to try again (and quit before the point that I broke it yesterday). However in fixing it I upgraded to 253 firmware, and I want to go back to 434. however I open up FlashTool get my ftf ready to flash, turn the phone off. Next step is volume down and plug in the USB cable, but instead of the light coming up green, it flashes green then immediately red (or possibly vice versa) then the light goes off, but FlashTool still thinks it's connected and in flash mode until I remove the cable. The battery has been a little bit drained through all of this. so I'm going to pump it up overnight and try again in the morning and hope that it just won't enter flash mode under X% battery, but if that's not the case has anyone ever run into this previously? or have any suggestions?
I have a locked bootloader, and it cannot be unlocked so fastboot options are out of the question. However it is worth noting that when I hold the volume up and plug in the USB cable, the blue light does stay on and I can gather info using FlashTool.
Villain of Brandon said:
So after my comedy of errors that was my playing around yesterday, I got my phone working again. Now I want to try again (and quit before the point that I broke it yesterday). However in fixing it I upgraded to 253 firmware, and I want to go back to 434. however I open up FlashTool get my ftf ready to flash, turn the phone off. Next step is volume down and plug in the USB cable, but instead of the light coming up green, it flashes green then immediately red (or possibly vice versa) then the light goes off, but FlashTool still thinks it's connected and in flash mode until I remove the cable. The battery has been a little bit drained through all of this. so I'm going to pump it up overnight and try again in the morning and hope that it just won't enter flash mode under X% battery, but if that's not the case has anyone ever run into this previously? or have any suggestions?
I have a locked bootloader, and it cannot be unlocked so fastboot options are out of the question. However it is worth noting that when I hold the volume up and plug in the USB cable, the blue light does stay on and I can gather info using FlashTool.
Click to expand...
Click to collapse
U want to flash 434 back right? So u need to enter flash mode which is volume up + connect to PC.
Sent from my BlackBerry 9900 using Tapatalk
Volume up does fastboot, volume down does flash mode. When I hold volume down the problem is the LED flashes Green, then immediately red then turns off and then will not continue flashing.
Villain of Brandon said:
Volume up does fastboot, volume down does flash mode. When I hold volume down the problem is the LED flashes Green, then immediately red then turns off and then will not continue flashing.
Click to expand...
Click to collapse
My bad, sorry. U flash using flashtool or pc companion? Have u try with latest version of flashtool beta6?
Sent from my BlackBerry 9900 using Tapatalk
I was downloading the windows version before I called it a night, because the ubuntu one is giving me a funny error I didn't feel like throubleshooting at 4am. that seems to have it fixed the problem though
Same problem
Villain of Brandon said:
I was downloading the windows version before I called it a night, because the ubuntu one is giving me a funny error I didn't feel like throubleshooting at 4am. that seems to have it fixed the problem though
Click to expand...
Click to collapse
Can you tell me how did you solve the problem? Because right now I'm having the sam thing on my ZL... I'm trying it with the newst flashtool, the light is green and turns into red and nothing happens...
Do a hard reset on it (using the button on the back), don't turn it on and follow the Flashtools flashing process
1.- Open Flashtools
2.- Flash mode > Flashmode > Select the FTF you just downloaded (The one of 700+MB) > Flash
3.- Connect your Phone in Flash mode (It will start flashing).
4.- Boot your phone and you're ready to go.
When selecting the FTF just select it and leave everything as it is and make sure that you have installed the drivers for flashing (
They are where found you installed Flashtools
In a folder called Drivers, open the .exe and Install these:
- Fastboot drivers
- Flashmode drivers
- Xperia Z and SO-02E drivers
If stills doesn't works I can't help any far as that, but I would suggest you that If you are able try to flash it on another computer (It might sound silly but It could actually work ), also make sure that you're running the latest Flashtool which is v0.9.11.0 and can be found here: http://androxyde.github.io/
That is quiet normal, green appears...red or whatever....out, flashmode connected, look into flashtool.....fine, no light on the phone....flash, but have an eye into flashtool after 1 or 2 minutes if you don't start flashing your phone disconnects automatically...and will stay on charging only.
nukharma said:
That is quiet normal, green appears...red or whatever....out, flashmode connected, look into flashtool.....fine, no light on the phone....flash, but have an eye into flashtool after 1 or 2 minutes if you don't start flashing your phone disconnects automatically...and will stay on charging only.
Click to expand...
Click to collapse
It would be fine, but tha flashtool displays some kind of instructions when it asks you to connect your phone in flashmode, and I connect it holding down the volume down key + connect AND then that instructions window should close automatically BUT that is just not happening. I've tried it 30 times already, all the drivers on, flashtool recognizes my phone when i start it... It is just not getting in flashmode! Is there any other way to flash the phone without flashmode??? I can get in fastboot I think, because if I press the volume up key while connecting the blue led is on, so it works.
I'm ready to donate for someone who can help me to get this phone work!
phone software version: 1266-7597_10.1.A.0.287 GENERIC - userdebug
File System Version: Global-LTE_10.1.A.0.278
S1 boot version: 1264-2309 S1_Boot_APQ_8064_LA1.2_9
ETS Software version: 1269-3849_5
SIM lock: here is everything 0 and no [X]
This is what I have right now in my phone. And one more thing that I was searching for and gugled it and cant find answer
ROOTING STATUS: unknown If I'm right there should be a text like Bootloader unlock allowed:Yes or No... not unknown
Anyway thx for your reply!
what version of Flashtool are you using? If it is the newest from the Androxyde's site, that wouldn't work for me either, you need to use the beta release. There should be a link above to the thread where they update the beta releases.
faragorn said:
It would be fine, but tha flashtool displays some kind of instructions when it asks you to connect your phone in flashmode, and I connect it holding down the volume down key + connect AND then that instructions window should close automatically BUT that is just not happening. I've tried it 30 times already, all the drivers on, flashtool recognizes my phone when i start it... It is just not getting in flashmode! Is there any other way to flash the phone without flashmode??? I can get in fastboot I think, because if I press the volume up key while connecting the blue led is on, so it works.
I'm ready to donate for someone who can help me to get this phone work!
phone software version: 1266-7597_10.1.A.0.287 GENERIC - userdebug
File System Version: Global-LTE_10.1.A.0.278
S1 boot version: 1264-2309 S1_Boot_APQ_8064_LA1.2_9
ETS Software version: 1269-3849_5
SIM lock: here is everything 0 and no [X]
This is what I have right now in my phone. And one more thing that I was searching for and gugled it and cant find answer
ROOTING STATUS: unknown If I'm right there should be a text like Bootloader unlock allowed:Yes or No... not unknown
Anyway thx for your reply!
Click to expand...
Click to collapse
Ok guess there isn't a link so here's the thread where they update the beta releases http://forum.xda-developers.com/showthread.php?p=39416182
Help
Guys, is there a way you can quit Flash Mode? I got stuck on it. The thing is my internet connection is to slow so i cancelled the "Update Service" by sony process, but the Xperia Z (C6603) is still stuck on Flash Mode. Can't get it out of there. It won't charge...
Im hopeless. Pls help me.
faragorn said:
It would be fine, but tha flashtool displays some kind of instructions when it asks you to connect your phone in flashmode, and I connect it holding down the volume down key + connect AND then that instructions window should close automatically BUT that is just not happening. I've tried it 30 times already, all the drivers on, flashtool recognizes my phone when i start it... It is just not getting in flashmode! Is there any other way to flash the phone without flashmode??? I can get in fastboot I think, because if I press the volume up key while connecting the blue led is on, so it works.
I'm ready to donate for someone who can help me to get this phone work!
phone software version: 1266-7597_10.1.A.0.287 GENERIC - userdebug
File System Version: Global-LTE_10.1.A.0.278
S1 boot version: 1264-2309 S1_Boot_APQ_8064_LA1.2_9
ETS Software version: 1269-3849_5
SIM lock: here is everything 0 and no [X]
This is what I have right now in my phone. And one more thing that I was searching for and gugled it and cant find answer
ROOTING STATUS: unknown If I'm right there should be a text like Bootloader unlock allowed:Yes or No... not unknown
Anyway thx for your reply!
Click to expand...
Click to collapse
I have the same problem
I am on unlocked bootloader Xperia L i tried everyting but no help......drivers and all are fine
Just making sure you are doing it correctly you turn off the phone, hold the volume down Jerry and then connecting the usb cable?
Sorry for digging. I hope it helps other people.
You have problem with drivers. You need to turn off driver signature enforcement - search google for "testsigning on". Apply it in cmd, reboot pc. Then install flashtool drivers (fastboot and flashmode, then reboot for being sure) and then try to flash. Cheers
I have Sony M4 aqua fastboot mode is working but flash mode the light is green but flash tool cant recognise it nothing happens

LG G Pro E988 stuck on the Logo screen

I have just flash the custom 5.0.2 ROM using philz touch 6.48.4.
After I flashed the ROM, I reboot to the philz recovery and flashed back to cwm 6.0.4.8.
However, the device stuck on the LG logo screen.
I have try to enter Download mode/Emergence mode/Hard reset mode/Recovery, but all of them I cannot go into.
Please help! Thank you for your helping!!
pchuen said:
I have just flash the custom 5.0.2 ROM using philz touch 6.48.4.
After I flashed the ROM, I reboot to the philz recovery and flashed back to cwm 6.0.4.8.
However, the device stuck on the LG logo screen.
I have try to enter Download mode/Emergence mode/Hard reset mode/Recovery, but all of them I cannot go into.
Please help! Thank you for your helping!!
Click to expand...
Click to collapse
Your boot loader is broken. Gonna have to get to the down load mode and reinstall either the or the stock. You can probably flash the recovery with .IMG file with lg flashing tool. Nerdy blond's twrp is one of those files that you can use. You can even try installing it first with the adb shell command, you can get the instructions at the same place where you download.
http://forum.xda-developers.com/showthread.php?t=3144369
hawkwind212 said:
Your boot loader is broken. Gonna have to get to the down load mode and reinstall either the or the stock. You can probably flash the recovery with .IMG file with lg flashing tool. Nerdy blond's twrp is one of those files that you can use. You can even try installing it first with the adb shell command, you can get the instructions at the same place where you download.
http://forum.xda-developers.com/showthread.php?t=3144369
Click to expand...
Click to collapse
Thank you for replying.
I cannot do anythings since I cannot enter into download mode.
I pressed volume key + and - and insert the usb cable to computer. There is nothing happened, computer dose not show the devices attached and the phone stay in the LG logo screen.
Also, I cannot use adb commands to force the phone enters into download mode as it shows nothings under "List of devices".
Is there any methods I can go into the download mode???
Thank you!
pchuen said:
Thank you for replying.
I cannot do anythings since I cannot enter into download mode.
I pressed volume key + and - and insert the usb cable to computer. There is nothing happened, computer dose not show the devices attached and the phone stay in the LG logo screen.
Also, I cannot use adb commands to force the phone enters into download mode as it shows nothings under "List of devices".
Is there any methods I can go into the download mode???
Thank you!
Click to expand...
Click to collapse
If your phone shows LG start screen, it should go into Download mode. I had similar problem few days ago while I was testing some kernel patches, it just froze on the LG screen. Solution was to unplug it, remove it's battery, SIM & SD (you don't have to remove SIM & SD, I just work that way) , make sure it's off, return battery back, press Vol + & Vol - at the same time and plug-in the USB cable.
Before that, make sure you have installed LG Unified driver (can be obtained via LG's software from support site), because without that Windows won't recognise your device.
After that, once you make your phone usable with Freegee/whatever you use to install initial recovery, flash official TWRP, because others are too old - that Philz CWM is old but still working with Lollipop but not work good and is tends to lock itself into a bootloop if you use hardware keys to enter; that other one, from GPRO_recovery APK is not supported and not working well (for me since day one), so it should be replaced as soon as possible.
Also, I can suggest you to flash your phone from stock 4.1 (not KitKat), root, flash recovery via freegee and after reboot update to latest official TWRP via Flashify.
hawkwind212 said:
Your boot loader is broken. Gonna have to get to the down load mode and reinstall either the or the stock. You can probably flash the recovery with .IMG file with lg flashing tool. Nerdy blond's twrp is one of those files that you can use. You can even try installing it first with the adb shell command, you can get the instructions at the same place where you download.
http://forum.xda-developers.com/showthread.php?t=3144369
Click to expand...
Click to collapse
ShadySquirrel said:
If your phone shows LG start screen, it should go into Download mode. I had similar problem few days ago while I was testing some kernel patches, it just froze on the LG screen. Solution was to unplug it, remove it's battery, SIM & SD (you don't have to remove SIM & SD, I just work that way) , make sure it's off, return battery back, press Vol + & Vol - at the same time and plug-in the USB cable.
Before that, make sure you have installed LG Unified driver (can be obtained via LG's software from support site), because without that Windows won't recognise your device.
After that, once you make your phone usable with Freegee/whatever you use to install initial recovery, flash official TWRP, because others are too old - that Philz CWM is old but still working with Lollipop but not work good and is tends to lock itself into a bootloop if you use hardware keys to enter; that other one, from GPRO_recovery APK is not supported and not working well (for me since day one), so it should be replaced as soon as possible.
Also, I can suggest you to flash your phone from stock 4.1 (not KitKat), root, flash recovery via freegee and after reboot update to latest official TWRP via Flashify.
Click to expand...
Click to collapse
Thank you for your detail reply.
I have tried to reinstall the LG driver and try to enter download mode again.
The screen is still stuck on LG logo and I cannot find the device in hardware manager (cannot recognize it).
I cannot do anythings until it can recognize it.
(Is it the bootloader is broken? and can I fix it?)
Thank you very much and waiting for your reply soon.:good:
pchuen said:
Thank you for your detail reply.
I have tried to reinstall the LG driver and try to enter download mode again.
The screen is still stuck on LG logo and I cannot find the device in hardware manager (cannot recognize it).
I cannot do anythings until it can recognize it.
(Is it the bootloader is broken? and can I fix it?)
Thank you very much and waiting for your reply soon.:good:
Click to expand...
Click to collapse
Which version of Windows are you using? It should be displayed under Serial ports in Device manager (named something like LGE Serial device) and LGFlashTool should recognise it immediately. I can't make you a screenshot/check for real name because I'm running Linux right now and can't reboot.
Also, try with another cable/port, remove all other android drivers you may have (Samsung's, Google's...) and disable antivirus.
ShadySquirrel said:
Which version of Windows are you using? It should be displayed under Serial ports in Device manager (named something like LGE Serial device) and LGFlashTool should recognise it immediately. I can't make you a screenshot/check for real name because I'm running Linux right now and can't reboot.
Also, try with another cable/port, remove all other android drivers you may have (Samsung's, Google's...) and disable antivirus.
Click to expand...
Click to collapse
It does not work on Windows 7 and XP.
I did not find any LGE XXX under Serial ports part.
Thank you!
pchuen said:
It does not work on Windows 7 and XP.
I did not find any LGE XXX under Serial ports part.
Thank you!
Click to expand...
Click to collapse
Hm.... Phone shows that it have entered download mode? Black screen, centered gray message and "DOWNLOAD MODE" red text?
ShadySquirrel said:
Hm.... Phone shows that it have entered download mode? Black screen, centered gray message and "DOWNLOAD MODE" red text?
Click to expand...
Click to collapse
No... nothing happens, just showing LG logo...
pchuen said:
No... nothing happens, just showing LG logo...
Click to expand...
Click to collapse
OK, it doesn't enter download mode. So, step by step:
- remove battery and leave it for 15-30 seconds, return battery
- press Vol+ and Vol- at the same time and keep them pressed,
- plug USB cable in while keys are pressed
It should immediately put you into download mode, with no LG screen, just black screen with gray box and red text I've described to you.
ShadySquirrel said:
OK, it doesn't enter download mode. So, step by step:
- remove battery and leave it for 15-30 seconds,
- press Vol+ and Vol- at the same time and keep them pressed,
- plug USB cable in while keys are pressed
It should immediately put you into download mode, with no LG screen, just black screen with gray box and red text I've described to you.
Click to expand...
Click to collapse
I understand what download mode screen is.
I followed your methods, bur I still cannot enter it and the computer cannot recognize that.
Sorry for disturbing :crying:
pchuen said:
I understand what download mode screen is.
I followed your methods, bur I still cannot enter it and the computer cannot recognize that.
Sorry for disturbing :crying:
Click to expand...
Click to collapse
So, whatever you try to do, phone just shows LG logo, not even a message in an upper left corner?
I'm running out of ideas. I have exact same variant (E988) but only time it didn't want to enter download mode this way was when cable I was using was broken...
ShadySquirrel said:
So, whatever you try to do, phone just shows LG logo, not even a message in an upper left corner?
I'm running out of ideas. I have exact same variant (E988) but only time it didn't want to enter download mode this way was when cable I was using was broken...
Click to expand...
Click to collapse
I have changed the cable, but it is the same.

Boot loop after OTA upgrade

Hi everyone, today my Elephone p8000 with stock rom (no root nor recovery installed) proposed me an OTA update, and I did it.
After installing the update the phone is stuck at the boot animation logo. If I boot in factory mode (volume down + power button) I am presented with a bunch of options in Chinese, which I don't understand. If I go in recovery mode (volume down + power button) it says "no command".
What can I do? What are my options? Is it bricked?
Yup mine too. Mine has root, with no custom recovery. Get the same boot loop and the sad open Android 'no command'.
Haven't had a chance to dig around for a solution but I suspect it is a case of using the flash tool to wipe and load a standard ROM? Hopefully an easier way.
kevvyboy said:
Yup mine too. Mine has root, with no custom recovery. Get the same boot loop and the sad open Android 'no command'.
Haven't had a chance to dig around for a solution but I suspect it is a case of using the flash tool to wipe and load a standard ROM? Hopefully an easier way.
Click to expand...
Click to collapse
Damn. I had huge problems with the flash tool in the past (I don't have a Windows PC) and the idea of spending the weekend trying to get the damn thing work is not a fun one.
Got this issue too this morning on way to work, I guess my phones useless today until I get home to try and flash it.
seem to be able to get to the boot select screen but nothing is different anyway, also managed to get into a "PCBA" mode that did a load of tests to the phone but thats it.
it now just died, not powering on, think its bricked :crying:
skea said:
it now just died, not powering on, think its bricked :crying:
Click to expand...
Click to collapse
Probably just out of power. Try charging it for a while and/or download and flash entire rom using sp flash except for data-partition so as you don't lose your data.
pitrus- said:
Probably just out of power. Try charging it for a while and/or download and flash entire rom using sp flash except for data-partition so as you don't lose your data.
Click to expand...
Click to collapse
thanks it was out of power lol
I just had the same problem. Did you solved it?
Like, exactly the same... Crazy
Another one
My p8000 also in bootloop after ota update. Only have an old vista PC w8ll dust it off tonight and see what happens
mines doing the same i thought it was too good to be true and it was lol
Cannot get pc (win 10) to install all the drivers, PC cannot see the phone so unable to run flash tool.
Suggestions? I presume the ROM cannot be flashed through the recovery (standard)?
EDIT: Driver package installed by disabling 'driver verification' setting in Windows. Phone only recognised as a MTP USB Device in devide manager, and flash tool does not seem to want to do anything. Might try this on a Win 7 laptop tomorrow. HJow you guys getting on with this?
Success - I Have a Working Phone
(or, How Chest Pains and Rage Focused the Mind)
So. This is what worked for me. Win 10. P8000 bootloop.
1) put p8000 into recovery, chose 'power off'. (I couldn't seem to stop it rebooting using the power button)
2) installed driver pack by disabling the Windows install signed drivers only setting. Rebooted. This turns the setting back on, but the drivers have alrwady been installed, no issue with that.
3) installed the flash tool. Brief panic at Chinese chars, located English. Calmed down.
4) loaded flash tool, with ROM ready to go.
5) this is the biggie, this is what brought it all together.........connected the powered down p8000 via USB and IMMEDIATELY hit the download button in the flash tool - ie BEFORE a new instance of USB bing-bong-device-connected sound.
6) once all downloaded, disconnect phone, reboot. Took an extended time (few mins) to boot, enough time to almost start swearing under my breath, but it just needed some patience.
Now, what I spent some time unsuccessfully trying to fix - needlessly as it turns out - was what my phone appeared under 'Device Manager'. It still lists it as an MTP USB Device under the 'Portable Devices' submenu. It did not seem to matter, as long as all the driver were installed.
I wish you all the best of luck in solving your issues, hopefully some of what I wrote can be helpful.
pitrus- said:
download and flash entire rom using sp flash except for data-partition so as you don't lose your data.
Click to expand...
Click to collapse
I have the same boot loop after ota. I did no backup before, so data partition contains my apps right ?
I never used the flash tool , where should I start , any good link for beginners ?
I read some things about the flash options months ago, must I disable/uncheck some options ?
Thanks for help.
same issue
Hi everyone!
I've got the same issue: I allowed the OTA update to 20151105 firmware release from previous version (20150725), after the upgrade, the phone keeps in a bootloop with a new colored Elephone logo.
I can't find a valid set of drivers, I tried a lot over the night, but windows don't recognize the phone.
PLEASE some kind soul could link a valid driver package to use SP tool ?
thanks a lot in advance!
mr..speed said:
I have the same boot loop after ota. I did no backup before, so data partition contains my apps right ?
I never used the flash tool , where should I start , any good link for beginners ?
I read some things about the flash options months ago, must I disable/uncheck some options ?
Thanks for help.
Click to expand...
Click to collapse
kevvyboy said:
Success - I Have a Working Phone
(or, How Chest Pains and Rage Focused the Mind)
So. This is what worked for me. Win 10. P8000 bootloop.
1) put p8000 into recovery, chose 'power off'. (I couldn't seem to stop it rebooting using the power button)
2) installed driver pack by disabling the Windows install signed drivers only setting. Rebooted. This turns the setting back on, but the drivers have alrwady been installed, no issue with that.
3) installed the flash tool. Brief panic at Chinese chars, located English. Calmed down.
4) loaded flash tool, with ROM ready to go.
5) this is the biggie, this is what brought it all together.........connected the powered down p8000 via USB and IMMEDIATELY hit the download button in the flash tool - ie BEFORE a new instance of USB bing-bong-device-connected sound.
6) once all downloaded, disconnect phone, reboot. Took an extended time (few mins) to boot, enough time to almost start swearing under my breath, but it just needed some patience.
Now, what I spent some time unsuccessfully trying to fix - needlessly as it turns out - was what my phone appeared under 'Device Manager'. It still lists it as an MTP USB Device under the 'Portable Devices' submenu. It did not seem to matter, as long as all the driver were installed.
I wish you all the best of luck in solving your issues, hopefully some of what I wrote can be helpful.
Click to expand...
Click to collapse
kevvyboy said:
Success - I Have a Working Phone
(or, How Chest Pains and Rage Focused the Mind)
So. This is what worked for me. Win 10. P8000 bootloop.
1) put p8000 into recovery, chose 'power off'. (I couldn't seem to stop it rebooting using the power button)
2) installed driver pack by disabling the Windows install signed drivers only setting. Rebooted. This turns the setting back on, but the drivers have alrwady been installed, no issue with that.
3) installed the flash tool. Brief panic at Chinese chars, located English. Calmed down.
4) loaded flash tool, with ROM ready to go.
5) this is the biggie, this is what brought it all together.........connected the powered down p8000 via USB and IMMEDIATELY hit the download button in the flash tool - ie BEFORE a new instance of USB bing-bong-device-connected sound.
6) once all downloaded, disconnect phone, reboot. Took an extended time (few mins) to boot, enough time to almost start swearing under my breath, but it just needed some patience.
Now, what I spent some time unsuccessfully trying to fix - needlessly as it turns out - was what my phone appeared under 'Device Manager'. It still lists it as an MTP USB Device under the 'Portable Devices' submenu. It did not seem to matter, as long as all the driver were installed.
I wish you all the best of luck in solving your issues, hopefully some of what I wrote can be helpful.
Click to expand...
Click to collapse
pretty much did the same thing and it worked!! Cheers!! (also had the rage and it took ages to find english on the tool lol :laugh: )
when you get the android with the "no command" message, let go of the volume and power buttons. Then hold the POWER BUTTON for 1-2 seconds and TAP VOLUME UP while still holding the power button. this will open the recovery options
omg!!
disabling the Windows install signed drivers only setting!!
i thought we wouldnt have to do things like this since Windows 95
Lol
Worked for me
Had I only found this tutorial before yesterday... it took me hours to figure this out.
I can, however, now confirm this works.
Regarding point 5):
(i) Power down phone (ii) start flash tool/go to download tab (iii) select scatter file (iv) hit "download" with no phone attached (v) attach the powered down phone
...and things will be fine. Doing anything fast is not required.
The point is to install SP_Drivers_v2.0 first, as described here. After this, everything goes smooth.
kevvyboy said:
Success - I Have a Working Phone
(or, How Chest Pains and Rage Focused the Mind)
So. This is what worked for me. Win 10. P8000 bootloop.
1) put p8000 into recovery, chose 'power off'. (I couldn't seem to stop it rebooting using the power button)
2) installed driver pack by disabling the Windows install signed drivers only setting. Rebooted. This turns the setting back on, but the drivers have alrwady been installed, no issue with that.
3) installed the flash tool. Brief panic at Chinese chars, located English. Calmed down.
4) loaded flash tool, with ROM ready to go.
5) this is the biggie, this is what brought it all together.........connected the powered down p8000 via USB and IMMEDIATELY hit the download button in the flash tool - ie BEFORE a new instance of USB bing-bong-device-connected sound.
6) once all downloaded, disconnect phone, reboot. Took an extended time (few mins) to boot, enough time to almost start swearing under my breath, but it just needed some patience.
Now, what I spent some time unsuccessfully trying to fix - needlessly as it turns out - was what my phone appeared under 'Device Manager'. It still lists it as an MTP USB Device under the 'Portable Devices' submenu. It did not seem to matter, as long as all the driver were installed.
I wish you all the best of luck in solving your issues, hopefully some of what I wrote can be helpful.
Click to expand...
Click to collapse
What if no Windows?
Edit: Never mind, I got myself a windows computer and succeeded. Thanks for all the orientation!
Hi all,
Thanks a lot for posting a solution to this problem so quickly. I am affected by the same issue. Looking to buy some LSD to better enjoy the psychtrip my phone seems to be stuck in. Also looking to fix the phone.
Unfortunately, I'm running Ubuntu 14.04 LTS. I did find a guide to use the flash tool on Ubuntu, but my phone does not seem to connect. I'm guessing this has something to do with that pack of drivers 2.0, for which I have no equivalent. I would really appreciate any ideas!
I might end up returning my phone to Amazon, though. It's only been a few days since I've had it, and you can imagine that although I was really liking it, I'm beginning to change my mind.
Your advice?
EDIT: I am getting the following error message:
BROM ERROR: S_COM_PORT_OPEN_FAIL (1013)
[COM]: Failed to open COM port.
[HINT]:
I did some googling, but didn't find anything worth mentioning.
yslsl said:
Had I only found this tutorial before yesterday... it took me hours to figure this out.
I can, however, now confirm this works.
Regarding point 5):
(i) Power down phone (ii) start flash tool/go to download tab (iii) select scatter file (iv) hit "download" with no phone attached (v) attach the powered down phone
...and things will be fine. Doing anything fast is not required.
The point is to install SP_Drivers_v2.0 first, as described here. After this, everything goes smooth.
Click to expand...
Click to collapse
Ahh good stuff. Connect phone last after hitting download - thanks for the heads up. Got my wife's p8000 today so will be doing some flashing later.
Cheers!

Arc S stuck on Legacy Xperia boot logo

Hey guys, so my Xperia Z's screen broke and the touch is unresponsive, so I took out my old Arc S out of the box and decided to boot it up, apparently I had gotten a new phone because this one had a booting problem.
Things I know:
It's been rooted, bootloader is unlocked, current ROM is Legacy Xperia, can't go into CWM recovery, connecting phone to PC and trying to flash new kernel won't work because flashtool doesn't recognize the device.
In device manager the phone comes up as an unknown device, downloaded the drivers from Sony's site, no luck, get error message saying "this file is not compatible with your version of Windows" or something.
I'm on W10 64bit.
So basically I'm kinda stuck, tried Google and other forums and nothing, I can't seem to get anywhere.
Could you guys help me out?
EDIT: Tried installing Android Studio, launching cmd from /appdata/roaming/android/sdk/platform-tools but when I enter the command line it says "waiting for device".
So I'm thinking this has to do with my PC not detecting my phone in fastboot mode or anyother mode.
This seems like a corrupted /system partition. First off, try another cable. Your current one might not be working (happened to me, kept reporting that it "did not recognize the device"). If that does not work, let's start with the basic troubleshooting steps. Does your phone boot info fastboot (turn off your phone, disconnect USB cable, hold menu button, reconnect USB while holding)? If it does, run "fastboot erase system" (I'm assuming you have the fastboot drivers installed and fastboot.exe in the working directory), and try booting into the recovery.
If not, let's try flashmode (turn off phone, disconnect USB, hold back button, reconnect while holding). If that works, just start up Flashtool (Download), wait for it to do its thing (sync), download the latest 4.1.B.0.587 ICS .ftf file from here. Once done, exit Flashtool, and go to the "drivers" folder. Install the flashmode drivers. Go back to Flashtool now.
In Flashtool, click the flash icon in the top-right of the program, and on the top you will find the working directory. Click the button on the right to it and select the directory where you downloaded the .ftf file. A new entry will show up in the menu on the left side. Click on it. Flashtool will prepare the file for flashing and instruct you how to connect your phone in flashmode. Be patient, this process may take a while. Once done (Flashtool will tell you), disconnect the phone, take the battery out for 5 seconds and put it back in, and then boot up the phone. The "SONY" logo should show up, followed by the "XPERIA" logo.
Set your phone up, and have fun flashing!
P.S. If you have any problems with your PC not recognizing your device while in USB Debugging (ADB says no devices), this worked for me.
bsevcenk said:
This seems like a corrupted /system partition. First off, try another cable. Your current one might not be working (happened to me, kept reporting that it "did not recognize the device"). If that does not work, let's start with the basic troubleshooting steps. Does your phone boot info fastboot (turn off your phone, disconnect USB cable, hold menu button, reconnect USB while holding)? If it does, run "fastboot erase system" (I'm assuming you have the fastboot drivers installed and fastboot.exe in the working directory), and try booting into the recovery.
If not, let's try flashmode (turn off phone, disconnect USB, hold back button, reconnect while holding). If that works, just start up Flashtool (Download), wait for it to do its thing (sync), download the latest 4.1.B.0.587 ICS .ftf file from here. Once done, exit Flashtool, and go to the "drivers" folder. Install the flashmode drivers. Go back to Flashtool now.
In Flashtool, click the flash icon in the top-right of the program, and on the top you will find the working directory. Click the button on the right to it and select the directory where you downloaded the .ftf file. A new entry will show up in the menu on the left side. Click on it. Flashtool will prepare the file for flashing and instruct you how to connect your phone in flashmode. Be patient, this process may take a while. Once done (Flashtool will tell you), disconnect the phone, take the battery out for 5 seconds and put it back in, and then boot up the phone. The "SONY" logo should show up, followed by the "XPERIA" logo.
Set your phone up, and have fun flashing!
P.S. If you have any problems with your PC not recognizing your device while in USB Debugging (ADB says no devices), this worked for me.
Click to expand...
Click to collapse
Hey man thank you so much for replying to the thread.
So I feel like a dumbass, multiple times I've read about changing cables, guess what, that's all it took.
So basically I changed the cable and instead of "unrecognized device" I got "S1 fastboot device", after that I installed the adb drivers for the Xperia Arc and voilà, it recognized as an adb device.
Onto platform-tools folder, cmd, flashed the kernel for Cyanogen 10, finally got into recovery and now after a full system wipe I'm flashing CM.
I'll let you know how it turns out.
Thanks a bunch!
Wolfarm141 said:
Hey man thank you so much for replying to the thread.
So I feel like a dumbass, multiple times I've read about changing cables, guess what, that's all it took.
So basically I changed the cable and instead of "unrecognized device" I got "S1 fastboot device", after that I installed the adb drivers for the Xperia Arc and voilà, it recognized as an adb device.
Onto platform-tools folder, cmd, flashed the kernel for Cyanogen 10, finally got into recovery and now after a full system wipe I'm flashing CM.
I'll let you know how it turns out.
Thanks a bunch!
Click to expand...
Click to collapse
Glad to know I helped!
Everything works fine now! Thanks sooo much!

Categories

Resources