Related
Sometimes my I5500 won't turn on.
This has already happened 2 times (with two different firmwares I5500XWJPL and I5503TTLPJP9). The phone shows absolutely no signs of life - screen is black, no sounds, nothing.
I tried everything: pressing VolumeDown+Center+Power, VolumeDown+Home+Power, with or without battery/SIM/charger/SD. Tried removing battery for 30 minutes, charging battery in external charger.
Sometimes when charger is connected, it shows green battery on the screen, but still won't boot.
Last times I spent several hours fiddling with it until it finally turned on..
Can someone tell my if there is a fast way to revive the phone next time this happens?
Maybe your arm11boot is damaged, but still partly working. You need replace that partition. I saw arm11boot partition image in one Russian FW. I can't remember actual name. You can try that, but caution. You might brick your phone compleatly!
sorry for reviving this thread.
but I got the same problem now. Tried to use ROM Manager to install CWM Recovery (following a blogpost explaining how to install a Custom ROM on the SG5). Might have accidentally clicked a different CWM Rec. version than I thought I did. However, ROM manager showed a message, telling me that CWMR was installed correctly.
So I wanted to boot into CWMR up to flash my device with the latest CyanogenMod 7 port from MADTeam. Used the "boot into recovery" option from ROM manager for that purpose. The next thing I know is my phone not reacting to anything.
Tried all methods mentioned afore (Vol- + Home + Power / Vol- + Center + Power, with/w.o. SD card and/or battery inserted). Screen keeps being off, no sign of life, phone wont even do anything when plugged to my PC or a charger.
The phone has been rooted properly before and was running Stock 2.1. Houston, we've got a problem.
Rigardi said:
sorry for reviving this thread.
but I got the same problem now. Tried to use ROM Manager to install CWM Recovery (following a blogpost explaining how to install a Custom ROM on the SG5). Might have accidentally clicked a different CWM Rec. version than I thought I did. However, ROM manager showed a message, telling me that CWMR was installed correctly.
So I wanted to boot into CWMR up to flash my device with the latest CyanogenMod 7 port from MADTeam. Used the "boot into recovery" option from ROM manager for that purpose. The next thing I know is my phone not reacting to anything.
Tried all methods mentioned afore (Vol- + Home + Power / Vol- + Center + Power, with/w.o. SD card and/or battery inserted). Screen keeps being off, no sign of life, phone wont even do anything when plugged to my PC or a charger.
The phone has been rooted properly before and was running Stock 2.1. Houston, we've got a problem.
Click to expand...
Click to collapse
Take your battery out, put it back in and turn your phone on, then it will boot up into recovery mode. I also have this problem from time to time, sometimes it boots into recovery, sometimes not and i have to remove/replace the battery.
I actually thought that this might be a useful feature for say - if you wanted to upgrade a friends phone to cyanogenmod in the pub, for example.
did try that. now even had the battery removed for about an hour. put it back in. still no reaction on pressing the power button or one of the combinations that should put it into recovery or download mode. no sign of life when plugging the phone to my computer or the charger.
I do fear the worst, though I dont know how ROM manager was actually able to brick the phone that badly.
Rigardi said:
did try that. now even had the battery removed for about an hour. put it back in. still no reaction on pressing the power button or one of the combinations that should put it into recovery or download mode. no sign of life when plugging the phone to my computer or the charger.
I do fear the worst, though I dont know how ROM manager was actually able to brick the phone that badly.
Click to expand...
Click to collapse
In that case then this also happened to me - While exploring the rom manager application after first ever flashing my phone i accidentally selected the wrong phone model from the 'flash clockworkmod recovery' option and my phone was gone forever. Perhaps your problem is similar.
(Luckily it was under warranty and they replaced it. The method worked so well in fact it happened 'accidentally' a second time i acquired a 3rd i5500 out of the box )
bought mine already used, so no chance for a warranty replacement :/
gonna give it a shot with a usb jig now, maybe i can get the thing into d/l mode with that, so I can revive it with odin.
Rigardi said:
bought mine already used, so no chance for a warranty replacement :/
gonna give it a shot with a usb jig now, maybe i can get the thing into d/l mode with that, so I can revive it with odin.
Click to expand...
Click to collapse
what about the Emergency DLoad Mode, which is not the Download Mode? Did you try it?
{ brvsn ~ CM7 on GT-I5500 ~ Tapatalk }
how do I access emergency d/l mode?
UPDATE
I actually CAN get download mode (or what I assume it to be) running by pressing Vol- + Menu + Power (while Vol- + Home + Power wont do anything, nor does the USB jig that arrived today). Took me some time to discover this, as this doesnt seem to be the usual 3-button-combination used. BUT: while the phone is now recognized by my PC, it wont show anything on the screen.
Odin (tried 4.28 and 4.43 on both win7 x64 and x32 and everyting related to Kies shut down) does now detect my phone. However, it always gets stuck at "Setup Connection" when I try to flash the stock rom or CWMR. Tried different approaches (from starting DL-mode with the phone being connected to my PC to separately starting DL mode and then connecting, starting it up with the battery already being in place, starting it up with sliding the battery in place while holding the 3 buttons etc.), none of them gets me further so far.
Another hint I found was setting the Baud-rate of the Samsung mobile modem to 203400, but this, unfortunately, didnt change anything.
Anyone got a lead on how to get Odin finally started properly?
Rigardi said:
UPDATE
I actually CAN get download mode (or what I assume it to be) running by pressing Vol- + Menu + Power (while Vol- + Home + Power wont do anything, nor does the USB jig that arrived today). Took me some time to discover this, as this doesnt seem to be the usual 3-button-combination used. BUT: while the phone is now recognized by my PC, it wont show anything on the screen.
Odin (tried 4.28 and 4.43 on both win7 x64 and x32 and everyting related to Kies shut down) does now detect my phone. However, it always gets stuck at "Setup Connection" when I try to flash the stock rom or CWMR. Tried different approaches (from starting DL-mode with the phone being connected to my PC to separately starting DL mode and then connecting, starting it up with the battery already being in place, starting it up with sliding the battery in place while holding the 3 buttons etc.), none of them gets me further so far.
Another hint I found was setting the Baud-rate of the Samsung mobile modem to 203400, but this, unfortunately, didnt change anything.
Anyone got a lead on how to get Odin finally started properly?
Click to expand...
Click to collapse
ops, sorry: I miss your previous message!!
Now I got it and read this last post.. let some time to think about it, I'll replay soon.. but, generally speaking, at this point there's not so much you can do..
If you can get it into Download or Recovery mode, then you should be fine.
Sent from my GT-I5500 using XDA App
Rigardi said:
UPDATE
I actually CAN get download mode (or what I assume it to be) running by pressing Vol- + Menu + Power (while Vol- + Home + Power wont do anything, nor does the USB jig that arrived today). Took me some time to discover this, as this doesnt seem to be the usual 3-button-combination used. BUT: while the phone is now recognized by my PC, it wont show anything on the screen.
Odin (tried 4.28 and 4.43 on both win7 x64 and x32 and everyting related to Kies shut down) does now detect my phone. However, it always gets stuck at "Setup Connection" when I try to flash the stock rom or CWMR. Tried different approaches (from starting DL-mode with the phone being connected to my PC to separately starting DL mode and then connecting, starting it up with the battery already being in place, starting it up with sliding the battery in place while holding the 3 buttons etc.), none of them gets me further so far.
Another hint I found was setting the Baud-rate of the Samsung mobile modem to 203400, but this, unfortunately, didnt change anything.
Anyone got a lead on how to get Odin finally started properly?
Click to expand...
Click to collapse
download mode is Vol - / Central Button / Power..
Im aware of that. However, Vol- + Menu + Power is the only key combination that the phone will react upon.
Anyway. Brought it to a mobile phone shop on friday, called them on monday and according to them, the phone should be fixed by tomorrow, wednesday. Seems like ROM manager has done damage that cant be undone without knowing how to handle a JTAG device. But at least its not completely broken. Learning that will cost me 25 Euros, though.
One final update to this: Got the phone back today, they were indeed able to fix it.
Conclusion:
While installing a non-fitting CWM-Recovery through ROM Manager will make your Galaxy 5 unfixable via Odin, it still can be saved by making proper use of a JTAG.
Rigardi said:
One final update to this: Got the phone back today, they were indeed able to fix it.
Conclusion:
While installing a non-fitting CWM-Recovery through ROM Manager will make your Galaxy 5 unfixable via Odin, it still can be saved by making proper use of a JTAG.
Click to expand...
Click to collapse
... for only 25 €!!!
{ brvsn ~ CM7 on GT-I5500 ~ Tapatalk }
Hi all,
after successfully unlocking the bootloader and flashing CyanogenMod 10.1.0 RC2 boot.img via fastboot from Linux, I couldn't manage to boot the tablet again.
I tried several things (Emma, Flashtool, etc.) in order to relock the bootloader and/or flash a stock ROM, but I only could put the device into fastboot mode.
Things are getting possibly worse now: the red notification light is still, I can't neither reboot (pressing Power+VolumeUp for 5 seconds) nor halt (Power+VolumeUp for 10 seconds)...
What a mess! Anyone can suggest me how to fix this situation, please?
Alberto
This is why u shouldn't mess with your tablet.just use it as it came, not worth the hassle
bibe74 said:
Hi all,
after successfully unlocking the bootloader and flashing CyanogenMod 10.1.0 RC2 boot.img via fastboot from Linux, I couldn't manage to boot the tablet again.
I tried several things (Emma, Flashtool, etc.) in order to relock the bootloader and/or flash a stock ROM, but I only could put the device into fastboot mode.
Things are getting possibly worse now: the red notification light is still, I can't neither reboot (pressing Power+VolumeUp for 5 seconds) nor halt (Power+VolumeUp for 10 seconds)...
What a mess! Anyone can suggest me how to fix this situation, please?
Alberto
Click to expand...
Click to collapse
ash6783 said:
This is why u shouldn't mess with your tablet.just use it as it came, not worth the hassle
Click to expand...
Click to collapse
This answer is about as helpful as a heart attack lol
I can assure you that even us dev's run into issues like this, I soft bricked my new tab 5 times today (still trying to figure out this recovery/no recovery thing sony is doing lol).
Aberto, I had/did the exact thing today, first off I'm guessing you have a wifi only like I do right? Those roms/boot imgs won;t work it seems, Im learning as fast as I can so I can get a port for Baked for this tab, I own the wifi only so its my first priority.
Here's what I did, took allot of patience, so be prepared to try a bunch of times!
1. Unplug the usb cable
2. hold both vol + and - (I know this is not documented but stick with me here), then press and hold the power button until the led flashed "white" "3 times" (u will see one white flash, then after about another 20 seconds a second set of white flashes will begin, it will blink 3 times)
3. Plug in the usb cable
4. Make sure you have emma/drivers setup, since this is a windows only (boo!) tool you should here the usb device plug notifiction that it detected the "S1 Service Sony Mobile Communications AB"
This only lasts about 1 minute before it will go back to red led, launch emma and restore a stock image from sony, after its done, unplug the device, and hold power, it should come back to life!
Thanks nycbjr, I tried this morning before getting to work and I could "unlock" the red notification light.
This evening I'll try to get further in the process of resuscitating my tablet.
Thanks for the tips!
Alberto
nycbjr said:
Alberto, I had/did the exact thing today, first off I'm guessing you have a wifi only like I do right? Those roms/boot imgs won;t work it seems, Im learning as fast as I can so I can get a port for Baked for this tab, I own the wifi only so its my first priority.
Click to expand...
Click to collapse
Yep, I have a SGP312 (wifi only, 32 GB)
nycbjr said:
This answer is about as helpful as a heart attack lol
I can assure you that even us dev's run into issues like this, I soft bricked my new tab 5 times today (still trying to figure out this recovery/no recovery thing sony is doing lol).
Aberto, I had/did the exact thing today, first off I'm guessing you have a wifi only like I do right? Those roms/boot imgs won;t work it seems, Im learning as fast as I can so I can get a port for Baked for this tab, I own the wifi only so its my first priority.
Here's what I did, took allot of patience, so be prepared to try a bunch of times!
1. Unplug the usb cable
2. hold both vol + and - (I know this is not documented but stick with me here), then press and hold the power button until the led flashed "white" "3 times" (u will see one white flash, then after about another 20 seconds a second set of white flashes will begin, it will blink 3 times)
3. Plug in the usb cable
4. Make sure you have emma/drivers setup, since this is a windows only (boo!) tool you should here the usb device plug notifiction that it detected the "S1 Service Sony Mobile Communications AB"
This only lasts about 1 minute before it will go back to red led, launch emma and restore a stock image from sony, after its done, unplug the device, and hold power, it should come back to life!
Click to expand...
Click to collapse
Thanks! I just saved my Tablet Z's life by your method!
It seems like no kernel I can flash now (SGP312 32GB WiFi) I flashed CWM-Based Recovery 6.0.3.2 twice, and m SGP312 died twice
yt92 said:
Thanks! I just saved my Tablet Z's life by your method!
It seems like no kernel I can flash now (SGP312 32GB WiFi) I flashed CWM-Based Recovery 6.0.3.2 twice, and m SGP312 died twice
Click to expand...
Click to collapse
you are welcome! Im working with doomlord on getting recovery working foir the sgp311/12..
btw baked blackbean 9 is booting on the z tab.. few days I'll release it
nycbjr said:
... after its done, unplug the device, and hold power, it should come back to life!
Click to expand...
Click to collapse
You saved my tablet's life too! I could manage to restore Sony's factory ROM, and finally I can use it!
Thanks again nycbjr!
hmz
Glad I found this topic, but so far I can't get it to work.
Situation is the same I guess, red light, tried to flash the wrong img to my wifi only modell.
When I press all 3 buttons at the same time, the first white blink shows up after about 5secs, then there is a 3 blink sequence also in white after another 3-5secs. If I plugin the usb cable still holding down the buttons, no usb device is recognized, nothing happens..
If I keep holding down the buttons a 3 white blink sequence shows up again, followed by a white/red quick blink, then after 5 secs another 3 white blink sequence starts again, followed by a white7red combo et cetera. As soon as I release the buttons it turns to a constant red again.
Any more ideas or should I just keep trying?
defy0815 said:
Glad I found this topic, but so far I can't get it to work.
Situation is the same I guess, red light, tried to flash the wrong img to my wifi only modell.
When I press all 3 buttons at the same time, the first white blink shows up after about 5secs, then there is a 3 blink sequence also in white after another 3-5secs. If I plugin the usb cable still holding down the buttons, no usb device is recognized, nothing happens..
If I keep holding down the buttons a 3 white blink sequence shows up again, followed by a white/red quick blink, then after 5 secs another 3 white blink sequence starts again, followed by a white7red combo et cetera. As soon as I release the buttons it turns to a constant red again.
Any more ideas or should I just keep trying?
Click to expand...
Click to collapse
Normally it is the follows:
Hold Vol+ and Power.
1x blink = Reboot (doesn't help you in this case)
after holding it longer
3x blink = Shut down (device is switched off and in a defined state)
Drink a beer
open flash-tool and prepare the firmware to flash
Hold Vol- and plug the device to the computer
If the led turns green the firmware will flash
If not check what the flash-tool says in which state the device is
If the led turns red maybe the battery is to empty?!?
I don't know about the red led, but thanks for the hint.
Pressing only vol down when pluggin in the usb seems to have changed something. I tried power+vol down before but that didn't help.
Now flashtool seems to be working, it says it's flashing, but it seems to take ages. I'll let it keep on working for now (running since 10mins, but after "checking header" and "flashing data" there is no progress anymore...yet). I'll report back
I canceled it after 2h with no progress...damnit.
Does anyone have another suggestion?
defy0815 said:
I canceled it after 2h with no progress...damnit.
Does anyone have another suggestion?
Click to expand...
Click to collapse
With Flashtool it didn't work, but with EMMA it works! YES!
Thanks!
This also saved my tablet's life.
defy0815 said:
I canceled it after 2h with no progress...damnit.
Does anyone have another suggestion?
Click to expand...
Click to collapse
Hi, try flashing again with Emma but use a different USB cable i had a similar issue where the flash started then seemed to freeze so tried a different cable and it worked.
Edit: lol seems i missed your post where you tried again with Emma -_- glad you got it sorted though
UserX10 said:
Normally it is the follows:
Hold Vol+ and Power.
1x blink = Reboot (doesn't help you in this case)
after holding it longer
3x blink = Shut down (device is switched off and in a defined state)
Drink a beer
open flash-tool and prepare the firmware to flash
Hold Vol- and plug the device to the computer
If the led turns green the firmware will flash
If not check what the flash-tool says in which state the device is
If the led turns red maybe the battery is to empty?!?
Click to expand...
Click to collapse
you need a big kiss from someone thanks a million :good::good::good::good::good::good::good:
This worked for me, albeit after trying the first part (holding VOL+, VOL- & POWER) intermittently for 2 days.
What seemed to get the table/battery to reset was I connected the USB cable to the charger on a wall outlet on the second day. When I plugged in the cable the Red LED came on and stayed there. After an hour it was still red so I removed the cable and tried 1) pressing VOL+ & POWER (about 3 seconds), then 2) VOL- & POWER (about 3 seconds) and after a while the red LED went off.
Then I tried the VOL+, VOL- & POWER and it started blinking white once, then white again after a while, and I was able to continue with the instructions.
Thanks!
Dear Sir/Mdm,
This is Linn Myanmar and I am from Myanmar, Stayed in Singapore, working as an engineer.
I just bought my phone (Elephone S8) one week before and I tired rooting with tutorials from XDA forum (using flash tool, driver).
Yes, the phone has been rooted properly as root checker said and I tried installing Updated SuperSU from setting>About Phone>System Update>Local Updates>Updated SuperSU.zip.
After that the phone has rebooting with logo and never show any result and the phone just happened the screen on and off repeatedly until now.
So that please help me how to solve this and get back to its normal operation. I've tried long pressing on power button, long pressing on power button+volume up button, long pressing on power button+volume up button+volume down button quite many time, but those doesn't work and the phone hasn't come back it's normal operation.
Help me please.
With Best Regards,
Linn Myanmar
Linn Myanmar said:
Dear Sir/Mdm,
This is Linn Myanmar and I am from Myanmar, Stayed in Singapore, working as an engineer.
I just bought my phone (Elephone S8) one week before and I tired rooting with tutorials from XDA forum (using flash tool, driver).
Yes, the phone has been rooted properly as root checker said and I tried installing Updated SuperSU from setting>About Phone>System Update>Local Updates>Updated SuperSU.zip.
After that the phone has rebooting with logo and never show any result and the phone just happened the screen on and off repeatedly until now.
So that please help me how to solve this and get back to its normal operation. I've tried long pressing on power button, long pressing on power button+volume up button, long pressing on power button+volume up button+volume down button quite many time, but those doesn't work and the phone hasn't come back it's normal operation.
Help me please.
With Best Regards,
Linn Myanmar
Click to expand...
Click to collapse
Hi Linn
How did you solve your problem?
Hi have exactly the same problem at this moment and, as you, I tried everything (except the hammer but it was close...)
Really need a solution for this!
I like the phone but this way I have to buy another one and other brand for sure...
Thanks (from Portugal)
I suppose you both solved this, one war or other, but maybe someone else looks for a solution to this.
As the S8 is a MTK-phone, it's never really "dead" until it's defective. You can always revive it. So stay cool.
All you need is a Windows-PC with working VCOM-drivers, the SP-Flash-Tool and a ROM. You can get all that on www.elephone.hk/downloads (at least until today... if it's no longer there, you need to google for all that).
The problem is to shut the phone off.
Of course you can just let it boot-loop until the battery is empty, if you can take the time.
Otherwise there's no simple and foolproof way to shut it off if it's in loop.
Try everything you can imagine with the three buttons. Especially pressing the power-button for "ages". Try pressing any volume-button simultaneously, too. I had my S8 bricked to bootloop several times yesterday and today, while fiddling around with all ROMs I could find.
Sooner or later I got the phone to shut off. I somehow got it into the testing-menu, too, which is yellow and chinese and which won't help you.
I even somehow managed to boot into recovery several times, which offers "shutdown"-option. I have the impression that the S8 enters recovery eventually when it fails to boot often enough, but that's just a guess.
Anyway, once the phone is off, you have won.
Start the SP-Flash-Tool, load the scatter-file from your desired ROM (which is probably 20171018), unplug the phone, press "download", and then plug the phone to USB. You might have to press vol+ oder vol- while plugging it in, but if it's recognized, the SP Flash Tool will start flashing the ROM and your phone is up and running again.
Problem solved
I think this is too complex anyway.
The battery was empty after some days.
It was too bad lose so many information but I had to live with that.
So, finally the hammer solve the problem in less then a second...
Thank you very much. Is nice to know there are people helping to solve some problems.
Amorinix
Please also find all required files for rooting the Elephone S8 at:
https://www.mediafire.com/file/k1ldc..._root.rar/file
I hope this helps.
To turn phone off, hold all 3 buttons for about 15 seconds the phone will look like it's powering down but then restart after about 2 seconds just KEEP holding all 3 buttons and it will power off properly. In other words hold all 3 buttons for about 45 secs to power down if in a boot loop. Once powered down hold volume down whilst plugging into USB to flash.
Noticed quite a few threads re this, have had the prob myself.
Found a simple fix, while trying different things...
Hold ALL buttons down at once (vol dn + vol up + pwr button). Keep them held down for about a min or two. Phone will respond and you'll be able to shut it off. It takes a while to respond.
Cheers
Thank you!
I've added this to the US998 Pie KDZ thread. That KDZ is very wonky. It's the only Pie people have problems flashing. Probably because LG has not yet released Open Market US998 and the one we are using is technically for U.S. Cellular US998.
I had no trouble flashing it myself -- on my backup V30+(former LS998) going straight from Nougat (never updated, it was my backup phone) to Pie through Dev Patched LGUP Refurbish mode. But lots of other people seem to have problems.
On my daily phone, I'm still on rooted stock Oreo with Magisk and Xposed mods.
AsItLies said:
Noticed quite a few threads re this, have had the prob myself.
Found a simple fix, while trying different things...
Hold ALL buttons down at once (vol dn + vol up + pwr button). Keep them held down for about a min or two. Phone will respond and you'll be able to shut it off. It takes a while to respond.
Cheers
Click to expand...
Click to collapse
Hi, @AsItLies, I have tried but my phone still keeps bootloop, so could you please describe it more detailed? Can you enter fastboot or rec then? If possible, please come to see this: Help! bootloop per 5 sec, cannot enter rec, download or fastboot
zacox123 said:
Hi, @AsItLies, I have tried but my phone still keeps bootloop, so could you please describe it more detailed? Can you enter fastboot or rec then? If possible, please come to see this: Help! bootloop per 5 sec, cannot enter rec, download or fastboot
Click to expand...
Click to collapse
I think it's pretty clear, what I did and it worked in my situation(s):
There are 3 buttons right? Vol up, Vol dwn, and pwr.
Press all 3, at the same time, keep them pressed until the phone responds. It can take quite a while.
The last time I used this was after flashing LOS17, but then flashed a 19.x version of Magisk... (that's the wrong version of Magisk for Q Roms btw), resulting in phone stuck on boot logo, wouldn't budge.
I honestly have never tested exactly 'how long' it takes to respond, just that it does eventually respond and are then able to get to recovery etc. I can say time wise, if you hold them down and no response after a few minutes, then it's probably not going to work in your situation.
good luck
AsItLies said:
I think it's pretty clear, what I did and it worked in my situation(s):
There are 3 buttons right? Vol up, Vol dwn, and pwr.
Press all 3, at the same time, keep them pressed until the phone responds. It can take quite a while.
The last time I used this was after flashing LOS17, but then flashed a 19.x version of Magisk... (that's the wrong version of Magisk for Q Roms btw), resulting in phone stuck on boot logo, wouldn't budge.
I honestly have never tested exactly 'how long' it takes to respond, just that it does eventually respond and are then able to get to recovery etc. I can say time wise, if you hold them down and no response after a few minutes, then it's probably not going to work in your situation.
good luck
Click to expand...
Click to collapse
Oh, I'm just a little confused if you are talking about powering off/shutting down the phone entirely or instead changing the status of logo sticking and then shutting off with extra operation. My phone was suffering automatic reboot per 5 second, so I cannot recognize any other response than that. Thanks for your patience, but I just want to know something more to see if this method works when the phone is almost bricked. It seems you could enter rec or at least download mode, so maybe you had performed force reboot.
Hope further confirmation.
zacox123 said:
Oh, I'm just a little confused if you are talking about powering off/shutting down the phone entirely or instead changing the status of logo sticking and then shutting off with extra operation. My phone was suffering automatic reboot per 5 second, so I cannot recognize any other response than that. Thanks for your patience, but I just want to know something more to see if this method works when the phone is almost bricked. It seems you could enter rec or at least download mode, so maybe you had performed force reboot.
Hope further confirmation.
Click to expand...
Click to collapse
Hmmm I think you may be over thinking this a bit. All that happens (for me) is the phone responds (it gets out of the loop). Then, do whatever you want (shut down, recovery, etc etc).
I wouldn't suggest trying to reboot system again, as you already know that won't work...
All I can say is, if you tried the above and held the buttons, and nothing happened, then I don't know what else you can do. Sorry. Hopefully you can find a way.
Just in case someone is having problems entering download mode while in this bootloop, I'll explain how I applied AsltLies method:
First I held all buttons at the same time, no matter how many times the phone restarted, I still held them
After a while, a white screen with the MEID or IMEI info showed up, this is when the phone stopped bootlooping and I released the buttons.
Then, I CONNECTED the phone to the pc, after that I held VOL UP+POWER BUTTON, this would make the screen go black eventually, and when that happened, I inmediately released the power button but not the VOL UP button, and the phone entered into fully working download mode.
I hope this helps someone.
Dr_Roo said:
Just in case someone is having problems entering download mode while in this bootloop, I'll explain how I applied AsltLies method:
First I held all buttons at the same time, no matter how many times the phone restarted, I still held them
After a while, a white screen with the MEID or IMEI info showed up, this is when the phone stopped bootlooping and I released the buttons.
Then, I CONNECTED the phone to the pc, after that I held VOL UP+POWER BUTTON, this would make the screen go black eventually, and when that happened, I inmediately released the power button but not the VOL UP button, and the phone entered into fully working download mode.
I hope this helps someone.
Click to expand...
Click to collapse
Thanks. Added your notes to the Recovery Post in US998 Pie KDZ thread.
https://forum.xda-developers.com/showpost.php?p=81728547&postcount=641
dr_roo said:
just in case someone is having problems entering download mode while in this bootloop, i'll explain how i applied asltlies method:
First i held all buttons at the same time, no matter how many times the phone restarted, i still held them
after a while, a white screen with the meid or imei info showed up, this is when the phone stopped bootlooping and i released the buttons.
Then, i connected the phone to the pc, after that i held vol up+power button, this would make the screen go black eventually, and when that happened, i inmediately released the power button but not the vol up button, and the phone entered into fully working download mode.
I hope this helps someone.
Click to expand...
Click to collapse
thank you so much omg lifesafer
Hi there friends I think I have managed to brick my so far but this lovely Xperia.
After testing flashing a lineage recovery to then install magisk which was fine I read about the SEA firmware unlocking VoLTE so I flashed that one with newflasher and it ran fine (although didn't unlock 4G) but then I decided to install magisk again and flashed the lineage recovery to boot_b (which was the active slot) and rebooted into recovery and my device does not come back. It is off and if I connect it the notification light just blinks red slowly. It does not appear in lsusb and I have tried holding vol up + power, vol down + power, vol up + vol down + power, for up to 30 seconds, it just won't come back to life
anybody else run into this and how did you revive it? Hope someone can help me
video of what it does when I connect:
(I'm trying with volume up here)
tomatoketchup said:
Hi there friends I think I have managed to brick my so far but this lovely Xperia.
After testing flashing a lineage recovery to then install magisk which was fine I read about the SEA firmware unlocking VoLTE so I flashed that one with newflasher and it ran fine (although didn't unlock 4G) but then I decided to install magisk again and flashed the lineage recovery to boot_b (which was the active slot) and rebooted into recovery and my device does not come back. It is off and if I connect it the notification light just blinks red slowly. It does not appear in lsusb and I have tried holding vol up + power, vol down + power, vol up + vol down + power, for up to 30 seconds, it just won't come back to life
anybody else run into this and how did you revive it? Hope someone can help me
video of what it does when I connect:
(I'm trying with volume up here)
Click to expand...
Click to collapse
Have you tried using xperia companion?
Mangtas_666 said:
Have you tried using xperia companion?
Click to expand...
Click to collapse
yeah it keeps waiting for the device. it never connects. tried multiple cables
Use bewflasher and just hold the vol down. And you should see a green led light and you're good to go
bountyman334 said:
Use bewflasher and just hold the vol down. And you should see a green led light and you're good to go
Click to expand...
Click to collapse
nope the green light is not coming up. it was previously, that's how I flashed the SEA firmware. it only blinks red and it doesn't establish an USB connection
tomatoketchup said:
nope the green light is not coming up. it was previously, that's how I flashed the SEA firmware. it only blinks red and it doesn't establish an USB connection
Click to expand...
Click to collapse
Keep it under charge a lot. Happened to me and it was at low level of charge, and it needed 4 hour to show again a light different from red. I never ever again start something under 90% charge.
Also don't charge connected to PC, it was too slow and from that state maybe you need 20 hours XD
Evil_Sephiroth said:
Keep it under charge a lot. Happened to me and it was at low level of charge, and it needed 4 hour to show again a light different from red. I never ever again start something under 90% charge.
Also don't charge connected to PC, it was too slow and from that state maybe you need 20 hours XD
Click to expand...
Click to collapse
I charged it overnight with its wall charger and it didn't snap out of it
tomatoketchup said:
I charged it overnight with its wall charger and it didn't snap out of it
Click to expand...
Click to collapse
I feel sorry for you brother...such a nice device...OK let's talk what happened, the state now your device is in is called hardbrick and it had a corrupted bootloader or no boot loader, but your device is still alive, in your PC in device manager it lists as Qs USB mode with some number after it like qsusb9008...now this device can only be brought to life with the help of a blankflash file which can flash your boot loader in snapdragon service mode...actually no snapdragon can be hardbricked permanently now you need appropriate blankflash file for your device.. Please don't open the device if some repairmen suggests to do JTAG nothing is necessary all you need is blankflash file which is shared to only Sony testers groups.... Who tests ROMs before release and they hardbrick so they share those files to them.... Please don't loose hope....it takes time but certainly it can be bought back to life... And dont try any flashing utility as there is no functional boot loader on it now and nothing will work...Sony won't provide that for sure and they will say then can only solve by mother board replacement ,don't believe therm your device is perfect it only needs blankflash file as it entered into final safe mode... I ain't regular on XDA if you need any info contact me via my mail [email protected] g ma I'll .com
Any updates on this? I'm having the same issue and looking for help from the community!
tomatoketchup said:
Hi there friends I think I have managed to brick my so far but this lovely Xperia.
After testing flashing a lineage recovery to then install magisk which was fine I read about the SEA firmware unlocking VoLTE so I flashed that one with newflasher and it ran fine (although didn't unlock 4G) but then I decided to install magisk again and flashed the lineage recovery to boot_b (which was the active slot) and rebooted into recovery and my device does not come back. It is off and if I connect it the notification light just blinks red slowly. It does not appear in lsusb and I have tried holding vol up + power, vol down + power, vol up + vol down + power, for up to 30 seconds, it just won't come back to life
anybody else run into this and how did you revive it? Hope someone can help me
video of what it does when I connect:
(I'm trying with volume up here)
Click to expand...
Click to collapse
smmate3 said:
Any updates on this? I'm having the same issue and looking for help from the community!
Click to expand...
Click to collapse
I bought an Xperia 1 IV.