Related
Hi there guys, first of all thank you all so much for the support here.
I have a problem with my atrix, i googled a lot before posting, but i still can't find a solution:
I have a atrix 4G, unlocked, was running successfully neutrino 2,8 version.
After 2 months of being (almost) fully functional, the phone crashed(i didn't do anything particular at that time, i think that i was browsing google maps) suddenly and now i have continuous boot loop, i get only the classic red dual core logo, with the "unlocked" notification over it, and then after 10-15 sec it reboots.
I try to open it with holding volume down, to enter recovery, nothing happens. It reboots again. The computer doesn't see it, in this case.
I reboot it with holding volume up, says "starting RSD protocol suppport", and pc sees it and i get the cling-clong sound of usb.
I would do the recovery using rsd, but i read that it is not for unlocked devices, is this so? What can i do in this case? Thanks a lot!!!
ergotelis said:
Hi there guys, first of all thank you all so much for the support here.
I have a problem with my atrix, i googled a lot before posting, but i still can't find a solution:
I have a atrix 4G, unlocked, was running successfully neutrino 2,8 version.
After 2 months of being (almost) fully functional, the phone crashed(i didn't do anything particular at that time, i think that i was browsing google maps) suddenly and now i have continuous boot loop, i get only the classic red dual core logo, with the "unlocked" notification over it, and then after 10-15 sec it reboots.
I try to open it with holding volume down, to enter recovery, nothing happens. It reboots again. The computer doesn't see it, in this case.
I reboot it with holding volume up, says "starting RSD protocol suppport", and pc sees it and i get the cling-clong sound of usb.
I would do the recovery using rsd, but i read that it is not for unlocked devices, is this so? What can i do in this case? Thanks a lot!!!
Click to expand...
Click to collapse
You'll probably need to flash a new recovery partition. Check out this thread:
http://forum.xda-developers.com/showthread.php?t=1950307
RaiderDuck said:
You'll probably need to flash a new recovery partition. Check out this thread:
http://forum.xda-developers.com/showthread.php?t=1950307
Click to expand...
Click to collapse
Thanks, but the problem is that this guy can get into the recovery with powering up+holding volume down button, if i understood well.but I can't!
ergotelis said:
Thanks, but the problem is that this guy can get into the recovery with powering up+holding volume down button, if i understood well.but I can't!
Click to expand...
Click to collapse
flasing a recovery is done via fastboot so you don't have to enter recovery but fastboot (hold power and volume down till it shows fastboot, then press up) .
look at this post: http://forum.xda-developers.com/showpost.php?p=33137046&postcount=10
Fix
ergotelis said:
Hi there guys, first of all thank you all so much for the support here.
I have a problem with my atrix, i googled a lot before posting, but i still can't find a solution:
I have a atrix 4G, unlocked, was running successfully neutrino 2,8 version.
After 2 months of being (almost) fully functional, the phone crashed(i didn't do anything particular at that time, i think that i was browsing google maps) suddenly and now i have continuous boot loop, i get only the classic red dual core logo, with the "unlocked" notification over it, and then after 10-15 sec it reboots.
I try to open it with holding volume down, to enter recovery, nothing happens. It reboots again. The computer doesn't see it, in this case.
I reboot it with holding volume up, says "starting RSD protocol suppport", and pc sees it and i get the cling-clong sound of usb.
I would do the recovery using rsd, but i read that it is not for unlocked devices, is this so? What can i do in this case? Thanks a lot!!!
Click to expand...
Click to collapse
hello i had this problem yesterday, it happens in neutrino rom to alot of people!
and btw i could not open recovery either
ill explain what i had to do
i had to use moto-fastboot and install a new recovery, basically your recovery is dead and your rom is unbootable
heres the steps
download the moto drivers and install
http://forum.xda-developers.com/attachment.php?attachmentid=1381183&d=1349549067
then download the motofastboot zip http://forum.xda-developers.com/attachment.php?attachmentid=1381414&d=1349555102
and create a new folder in C: (computer) called Android and then drag the files from the moto zip into android
Then download a new recovery http://www.mediafire.com/?6ww8wrjrdqq9m97
place the recovery.img into the android folder
now you have all the files needed to reflash your new recovery and fix your phone the whole idea is to reinstall recovery so you can access it and wipe and install the rom fresh again
now you need to do these steps
1) Attach your phone to the PC via USB (use a port closest to the power supply)
2) Reboot phone while holding volume down until you see "fastboot"
3) Press volume up to initiate fastboot
4) On your PC click the Start menu, then in the search box type "cmd"
5) In the command prompt type the following commands (no quotes, hit enter after each command)
6a) "cd c:/android"
6b) "moto-fastboot devices"
your CMD promt should show something like this
C:\Users\Me>cd c:/android
c:\Android>fastboot devices
TA20703SX9 fastboot
c:\Android>
now if that has all worked type the following phrases
moto-fastboot erase recovery
moto-fastboot flash recovery recovery-clockwork-6.0.1.4-maguro.img
moto-fastboot reboot
now the phone should reboot, unplug the usb and pull battery out.
put battery back in and then try to boot into recovery like you normally would (power button + Vol Down)
and your new recovery should load!
from here you can wipe your whole system which i would reccomended as your current one is corrupt and install a new rom or reflash your current on onto a clean wipe. if you dont understand how to clean wipe do all of these steps, factory reset, clear cache, clean dalvik cache then go to mounts > storage and format data + format cache + format system
now install new rom and let it boot up, should bootloop a couple of times then start! if not unplug battery from phone and ask for further assitance
Pixelguy said:
1) Attach your phone to the PC via USB (use a port closest to the power supply)
2) Reboot phone while holding volume down until you see "fastboot"
3) Press volume up to initiate fastboot
Click to expand...
Click to collapse
Thank you for your help, the problem is exactly here, i put on the usb, i power up the phone by pressing the volume down, and the phone does nothing,doesn't show the fastboot,and after 10-15 secs starts rebooting again. This is my problem!
The only response from my phone is when powering up, and pressing the volume up, it says "starting rsd protocol support"
Is there any case that my volume down is dead?
ergotelis said:
Thank you for your help, the problem is exactly here, i put on the usb, i power up the phone by pressing the volume down, and the phone does nothing,doesn't show the fastboot,and after 10-15 secs starts rebooting again. This is my problem!
The only response from my phone is when powering up, and pressing the volume up, it says "starting rsd protocol support"
Is there any case that my volume down is dead?
Click to expand...
Click to collapse
unplug usb
remove battery, then put battery back in make sure phone off (no green light)
then hold power button and vol down at the same time for a few seconds
Fastboot should appear in white writing then press up volume and it should say starting rsd protocal or something similiar
then plug in usb and follow the steps i have written above
i do exactly what you said, but doesn't show fastboot. from switched off, if i press volume up with power button, i see the message "starting rsd protocol support" .but no fastboot option!
Is there any chance that you can access adb after bootscreen? than you can use "adb reboot recovery" to get there...
jorno88 said:
Is there any chance that you can access adb after bootscreen? than you can use "adb reboot recovery" to get there...
Click to expand...
Click to collapse
When i start up phone, the only combination possible to stop restarting is by pressing power+vol up to show that with RSD. There is no other option then selectable. Power + volume down does not work, doesn't show anything, has anyone of you experienced this thing?
If the only working option you have is RSD, then I'm afraid you're stuck with having to flash a stock SBF. I hope you know/remember exactly what stock version you had installed before any modding or flashing, because the SBF has to match exactly. Choose wisely and read up as much as you can before flashing.
I have over a year now with custom roms, and i can't remember which version i had. Why do i have to find exactly the version that i had? The latest stock version won't work with rsd? It will make it hard brick?If i manage at least to recover the fastboot menus etc it would be great!
I will later also try to open it, to see if the side button "volume down" is not working,.
I have another question, in your moto atrix, if you press on startup power+vol up, are you also seeing the "starting RSD" etc option??
ergotelis said:
I have over a year now with custom roms, and i can't remember which version i had. Why do i have to find exactly the version that i had? The latest stock version won't work with rsd? It will make it hard brick?If i manage at least to recover the fastboot menus etc it would be great!
Click to expand...
Click to collapse
Yes, flashing a wrong SBF will most likely hardbrick your device.
ergotelis said:
I have another question, in your moto atrix, if you press on startup power+vol up, are you also seeing the "starting RSD" etc option??
Click to expand...
Click to collapse
Can't try right now, but as far as I know, yes, that is a standard way to enter RSD mode.
thank you, so, i know that at least my phone responds to some instructions.
Is there anyone else to suggest me to do anything else?
IN rsd mode, (other than flashing a stock random rom with chance of hardbricking,)the phone can be read by usb, can i do anything there?
ergotelis said:
IN rsd mode, (other than flashing a stock random rom with chance of hardbricking,)the phone can be read by usb, can i do anything there?
Click to expand...
Click to collapse
Sadly no. The RSD mode can only ever be used to flash SBFs. That's it. Nothing less, nothing more.
I will now try to open it to see if vol down is not working well. If it does work, i will select a stock rom 1 year old and i will flash it using rsd, and whatever happens....:good:
I disassembled the phone, the button seems to operate fine(?).
I flashed with RSDlite the 2.3.6 version, the RSD stuck to waiting for phone to restart.
The phone restarted, the "unlocked" logo disappeared.
Starts normally, passes the red motorola logo, shows the graphic of AT&T, and after ~10sec starts restarting again. Bootloop again!
At boot, pressing power+vol up, i can still get the RSD support. Pressing power+vol down does nothing, I don't see any error messages, like the ones in hard brick.
What can i do now, any ideas please!!!
try this
ergotelis said:
I disassembled the phone, the button seems to operate fine(?).
I flashed with RSDlite the 2.3.6 version, the RSD stuck to waiting for phone to restart.
The phone restarted, the "unlocked" logo disappeared.
Starts normally, passes the red motorola logo, shows the graphic of AT&T, and after ~10sec starts restarting again. Bootloop again!
At boot, pressing power+vol up, i can still get the RSD support. Pressing power+vol down does nothing, I don't see any error messages, like the ones in hard brick.
What can i do now, any ideas please!!!
Click to expand...
Click to collapse
Yesterday I had a hard time getting my phone into fastboot mode, after loading a bad SV kernel,it only wanted to start the RSD protocol mode. I eventually got into fastboot by plugging into the wall charger, then removing and installing the battery while holding the vol button. When fastboot appears, unplug the charger to allow sd access.
Thanks for the suggestion, i tried even this,it didn't work. The funny thing is that it shows the battery charging level full screen if i connect the charger, as it starts.
I noticed also that when i press vol down now, it takes longer to start and continue to the moving red logo, it stays for a while stable red,feels like it is thinking whether to start or not lol (if i don't press vol down, on the power up the red moto logo immediately starts the classic "waving" effects)
Anyone having any kind of suggestion?I guess you don't, right?
Hi guys,
I tried to unlock the bootloader of my Nexus 10 before rooting it. Unfortunately, it didn't work and I can't use it anymore (I either have the "Loading X" forever or a dead droid while trying to go to the recovery mode).
I'm used to do that kind of modifications (only on Samsung Galaxy S and S3 though) and I don't know what I did wrong (but I usually flashed with Odin).
Anyway, I used this tool (after enabling the usb debug and allowing unknown sources) : http://forum.xda-developers.com/showthread.php?t=2001868
I installed the drivers on my PC (menu 1 in the tool), then I could see my device in ADB MODE (in the tool menu). I tried to unlock the bootloader (3rd option in the menu) and it was written completed. My device reboots and nothing happens. I can access the fastboot mode (is it the download mode ?).
I have Odin.
Can someone help me to get a working device ?
Thank you very much.
hiveNzin0 said:
Hi guys,
I tried to unlock the bootloader of my Nexus 10 before rooting it. Unfortunately, it didn't work and I can't use it anymore (I either have the "Loading X" forever or a dead droid while trying to go to the recovery mode).
I'm used to do that kind of modifications (only on Samsung Galaxy S and S3 though) and I don't know what I did wrong (but I usually flashed with Odin).
Anyway, I used this tool (after enabling the usb debug and allowing unknown sources) : http://forum.xda-developers.com/showthread.php?t=2001868
I installed the drivers on my PC (menu 1 in the tool), then I could see my device in ADB MODE (in the tool menu). I tried to unlock the bootloader (3rd option in the menu) and it was written completed. My device reboots and nothing happens. I can access the fastboot mode (is it the download mode ?).
I have Odin.
Can someone help me to get a working device ?
Thank you very much.
Click to expand...
Click to collapse
Easy fix. Get to the dead droid recovery menu and then press all 3 buttons on the top. You will get into the blue recovery options. Choose factory reset.
Sometimes unlocking the bootloaders scrambles a few things on this device and it goes into boot loop. After the factory reset, you'll be fine. PM me if you still have issues.
Sent from my Galaxy Nexus using Tapatalk 2
Blueback22 said:
Easy fix. Get to the dead droid recovery menu and then press all 3 buttons on the top. You will get into the blue recovery options. Choose factory reset.
Sometimes unlocking the bootloaders scrambles a few things on this device and it goes into boot loop. After the factory reset, you'll be fine. PM me if you still have issues.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Okay, thank you very much. I didn't know I had to press the 3 top buttons again after the dead droid screen, I thought it failed loading the Recovery Mode.
I have to setup my account etc again so I guess it is safe to say it worked.
Additionally, I tried this method after the recovery : http://forum.xda-developers.com/showthread.php?t=2015467
and it worked fine. My device has an unlocked bootloader and is rooted.
hey if someone could help me im stuck myself, after i had the dead android in recovery mode i tried to flash software with the toolkit in fastboot and now when i go to recovery its just a blank screen till i hold the bottom combo again and it takes me back to fastboot
Blueback22 said:
Easy fix. Get to the dead droid recovery menu and then press all 3 buttons on the top. You will get into the blue recovery options. Choose factory reset.
Sometimes unlocking the bootloaders scrambles a few things on this device and it goes into boot loop. After the factory reset, you'll be fine. PM me if you still have issues.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Hey,
I'm having the same problem. I get to the dead droid instead of recovery and tried hitting all three buttons again but it's just looping again.
Any ideas?
maximepull said:
Hey,
I'm having the same problem. I get to the dead droid instead of recovery and tried hitting all three buttons again but it's just looping again.
Any ideas?
Click to expand...
Click to collapse
It sounds like you didn't actually perform a factory reset. The key combination to get into stock recovery from the dead android screen is Power + Vol-Up. That will bring up the option to factory reset.
So if your powered off or bootlooping, hold the Power + Vol-Up + Vol-Down until you're back in the Bootloader. Use Vol buttons to select Recovery Mode and tap Power. When the droid w/ the Red "!" appears, hold the Power button and quick press the Vol-Up button. This should take you into stock recovery. Select Factory reset. Reboot. After a few minutes, the device should boot normally.
Good luck.
sharksfan7 said:
It sounds like you didn't actually perform a factory reset. The key combination to get into stock recovery from the dead android screen is Power + Vol-Up. That will bring up the option to factory reset.
So if your powered off or bootlooping, hold the Power + Vol-Up + Vol-Down until you're back in the Bootloader. Use Vol buttons to select Recovery Mode and tap Power. When the droid w/ the Red "!" appears, hold the Power button and quick press the Vol-Up button. This should take you into stock recovery. Select Factory reset. Reboot. After a few minutes, the device should boot normally.
Good luck.
Click to expand...
Click to collapse
Ok found a video showing that when you get to that part where there's the dead droid (the red !), you don't press hold hold all three buttons but tap them until the recovery screen shows up.
So finally did that but I still have the same problem.
My initial problem was, I received my N10, open the box, turned it on and it started freezing and rebooting. Can't get past the wifi step.
Tried hard and many times to finally get to enter my gmail account, etc
Updated to 4.3, problem persisted so I figured, maybe the factory flashed a bad rom?
So I unlocked it, rooted it and tried flashing older stock versions, same problem.
Tried flashing CM, same; PA, same...
Tried deactivating location service as suggested elsewhere: same; uninstall chrome: same
Even CM withouf GAPPS wouldnt work
So basically, I have a $500 brick. Completely useless as it freezes every 30 seconds.
Decided not to return the device because although I am Canadian, I live in SE Asia and had a visiting friend bring it to me. Way past the return period and the overall experience would be a real pain in the butt... Don't know what to do. Really hoping Kit Kat will solve it but I have doubts.
What do you think?
Sorry. I don't know enough about these things to give more in depth troubleshooting advice. I just recently got my N10 & unlocked it and based on your original post, I thought that's where you needed help. But it sounds like you got past that and got it unlocked.
Have you tried downloading a factory image directly from Google and installing that? If it's locking up on a fresh install of any ROM, it very well may be a hardware issue. You may have to file a warranty claim if possible.
maximepull said:
Ok found a video showing that when you get to that part where there's the dead droid (the red !), you don't press hold hold all three buttons but tap them until the recovery screen shows up.
So finally did that but I still have the same problem.
My initial problem was, I received my N10, open the box, turned it on and it started freezing and rebooting. Can't get past the wifi step.
Tried hard and many times to finally get to enter my gmail account, etc
Updated to 4.3, problem persisted so I figured, maybe the factory flashed a bad rom?
So I unlocked it, rooted it and tried flashing older stock versions, same problem.
Tried flashing CM, same; PA, same...
Tried deactivating location service as suggested elsewhere: same; uninstall chrome: same
Even CM withouf GAPPS wouldnt work
So basically, I have a $500 brick. Completely useless as it freezes every 30 seconds.
Decided not to return the device because although I am Canadian, I live in SE Asia and had a visiting friend bring it to me. Way past the return period and the overall experience would be a real pain in the butt... Don't know what to do. Really hoping Kit Kat will solve it but I have doubts.
What do you think?
Click to expand...
Click to collapse
sharksfan7 said:
Have you tried downloading a factory image directly from Google and installing that?
Click to expand...
Click to collapse
^ that's your solution. If you dont know how to just pm me
Sent from my Galaxy Nexus using XDA Premium HD app
hi I hope this is posted correctly... I have a nabi 2 running kitkat that was rooted with kingo root and no twrp, everything stock besides that... I deleted something I shouldn't have and when I restarted the tablet it booted fine until it got to the home screen. as of now I have no lock screen to swipe and no home screen. The home button and back button still show and also make a click noise. so I figure to do a factory reboot and everything would be fine... well I was wrong... it still boots but still no home screen.... at times the background will flash and the time and battery will pop up.
So I downloaded nabilabs thinking that would be able to help me and I believe it will but as I found out when I did a factory reset it turned off usb debugging and will not connect now. so with out screen controls how do I turn usb debugging mode on? is there a line I can send to it to connect? thanks for the help in advanced..
I did search around and found a bunch of great software and roms for it but I really haven't found a similar issue or realized that I found something close to my issue.
Do you have a photo? That would make it easier to know what you’re describing
Your firmware may be corrupted.
I put the link to a new ROM here. If you click click the hyperlink it will be at the top of the screen. Use Fastboot to flash that.
Put Fastboot Protocol on by holding down both the volume buttons and the power button, then when the letters on the top left (held in landscape) of the screen pop up, click the volume - (down) button and then click the volume + (up) button. Your computer will now recognize the device in Fastboot. Then you can flash the ROM.
See if that helps.
Hello, world! This is my first time posting on the forums, so I'd appreciate grace where it's due, haha. Anyhow, onto my problem. I have an LG K20 V (model # VS501) with bootloader locked and unrooted. I've been able to boot into recovery by simply running
Code:
adb reboot recovery
but the recovery menu never appears, only the android on its back and the words "No Command". I've read up somewhat on the error but no combination of the volume keys and power button (my device doesn't have a physical home button) seems to ever put me through to the actual recovery menu, only booting the phone up normally or no results. I have read a few places that it could be an issue with the cache (no idea how), so would simply wiping the cache fix it? The internet is sparse on info on my specific device and I've always found the answers I'm looking for on XDA so I'm hoping I'll get one for this problem as well. Thanks in advance!
after pressing the keys:there is a blue screen which shows a killed android and an error signal and says no command?if yes you just have to wait and it will go to recovery mode after a bit
paranoic(d) said:
after pressing the keys:there is a blue screen which shows a killed android and an error signal and says no command?if yes you just have to wait and it will go to recovery mode after a bit
Click to expand...
Click to collapse
Not blue, a black screen. And I don't get to recovery by pressing keys, in fact I've tried and I cant. Only with the adb command. Or are you saying I just need to wait a while longer after pressing the key combinations to get past the error?
well.lg phones are secure so i dont really know from them :/.i have used only sony and samsung devices
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