Related
Hoping someone here may have some ideas. ..
Picked up a couple Global's the other day on eBay. Two of the three work great. Was able to get them unlocked, rooted, and band unlocked. They are working great on T-mobile! The issue I'm having is with the third one. When I enter the bootloader, I get nothing but a black backlit screen with no writing. When I attempt to use RSD Lite, I can't get it to recognize the phone at all.
So next I tried booting the phone normally, and then hooking it to the PC. RSD Lite does recognize it that way. When I begin the flash process, the phone attempts to reboot into flash mode, screen goes black, same backlit screen with no writing. I would like to point out that I am doing all this with a 5-wire factory cable, so none of the usual button combo mistakes, undercharged battery issues, etc. apply here. If you have on of these, you don't need a battery in the phone at all. With and without battery, with and without factory cable...hasn't mattered, no bootloader no matter what. The issue is that the bootloader acts as if it just isn't even on the phone. I know there are several ways to reload that consumer replacement to a droid 1, but I haven't found anything for a 2. The other thing limiting what I am able to do is that the phone is running .629, which means no root or CWM, so those couple tricks are out the window at this point also, and because of the bootloader issue I am unable to downgrade using RSD Lite or any of the bootable CD options that usually work for phone stuck on .629.
So at this point I'm figuring the phone is just stuck the way it is, but I thought I'd throw it out there and see if any of you guys had any similar experiences. Thanks
strabo231 said:
Hoping someone here may have some ideas. ..
Picked up a couple Global's the other day on eBay. Two of the three work great. Was able to get them unlocked, rooted, and band unlocked. They are working great on T-mobile! The issue I'm having is with the third one. When I enter the bootloader, I get nothing but a black backlit screen with no writing. When I attempt to use RSD Lite, I can't get it to recognize the phone at all.
So next I tried booting the phone normally, and then hooking it to the PC. RSD Lite does recognize it that way. When I begin the flash process, the phone attempts to reboot into flash mode, screen goes black, same backlit screen with no writing. I would like to point out that I am doing all this with a 5-wire factory cable, so none of the usual button combo mistakes, undercharged battery issues, etc. apply here. If you have on of these, you don't need a battery in the phone at all. With and without battery, with and without factory cable...hasn't mattered, no bootloader no matter what. The issue is that the bootloader acts as if it just isn't even on the phone. I know there are several ways to reload that consumer replacement to a droid 1, but I haven't found anything for a 2.
Click to expand...
Click to collapse
maybe bricked, could try manually installing update.zip from android recovery, if you can get to that
How to enter Android system recovery
Power down the phone.
Slide out the keyboard.
Press and hold the X button on the physical keyboard.
Press the power button.
Once you see a warning sign with an android robot appear, press the Search button on your physical keyboard if you're running froyo/2.4.x firmware. For gingerbread/4.5.x firmware, press Volume Up and Down buttons.
and be sure you are using
How to Enter Bootloader: (used to flash .sbf recovery images)
Power down the phone.
Slide the keyboard out.
Press and hold the up arrow (↑) key.
Press the lock/power button.
Once the SBF loader screen pops up, release the up arrow key.
The other thing limiting what I am able to do is that the phone is running .629, which means no root or CWM, so those couple tricks are out the window at this point also, and because of the bootloader issue I am unable to downgrade using RSD Lite or any of the bootable CD options that usually work for phone stuck on .629.
Click to expand...
Click to collapse
.629 has been rootable since 16 April 2012
just use ezSBF & Root 2.3.4/ 4.5.629
So at this point I'm figuring the phone is just stuck the way it is, but I thought I'd throw it out there and see if any of you guys had any similar experiences. Thanks
Click to expand...
Click to collapse
sd_shadow said:
maybe bricked, could try manually installing update.zip from android recovery, if you can get to that
How to enter Android system recovery
Power down the phone.
Slide out the keyboard.
Press and hold the X button on the physical keyboard.
Press the power button.
Once you see a warning sign with an android robot appear, press the Search button on your physical keyboard if you're running froyo/2.4.x firmware. For gingerbread/4.5.x firmware, press Volume Up and Down buttons.
and be sure you are using
How to Enter Bootloader: (used to flash .sbf recovery images)
Power down the phone.
Slide the keyboard out.
Press and hold the up arrow (↑) key.
Press the lock/power button.
Once the SBF loader screen pops up, release the up arrow key.
.629 has been rootable since 16 April 2012
just use ezSBF & Root 2.3.4/ 4.5.629
Click to expand...
Click to collapse
Ah Shadow! I was hoping you'd see this. Let me clarify a little bit.
1. I am able to get phone to boot into OS. I did try to install the update.zip already but I'm still having the same problem with the boot loader.
2. I know about the easy sbf, and tried that with this particular phone, but because of the problem with the boot loader when easy sbf or RSD Lite switch the phone, or attempt to switch into flash mode, the computer no longer recognizes the phone.
3. I did think about rooting the phone to try to open up a few other options to at least get around the problem. Since it's on .629 already though I'm limited to rooting using easy sbf as far as I've understood, but again since I'm having the issue with the boot loader that hasn't been an option I have been able to successfully use.
4. The power button on the phone isn't working, so I'm unable to use the key combo to access the boot loader; however, I have a factory cable...now I say factory cable not meaning the stock charging cable...but the 5-wire factory cable. Typically with Motorola phones using this cable you simply remove the battery, and then with no battery in the phone hold down both volume buttons and plug the factory cable in and it automatically reverts to the boot loader.
I know that there is a consumer replacement boot loader for the droid 1 to fix issues like this, but I haven't seen one for the two. The other issue is that the replacement is an sbf file which ill be unable to use, and didn't know if that was something that would exist as an update.zip that could be flashed through the stock recovery
don't need power button
with phone off, hold up arrow and connect usb cable
should boot directly to bootloader
sd_shadow said:
don't need power button
with phone off, hold up arrow and connect usb cable
should boot directly to bootloader
Click to expand...
Click to collapse
yeah we're on the same page there. When I do that, instead of getting the bootloader like I normally would, I'm just getting a blank black backlit screen, like the boot loader isn't there. Instead of getting bootlader D0.11 ect, It's just a blank screen. It doesn't matter which method I use to access it, both volume buttons and usb, up arrow and usb, whether there is a battery in the phone or not, I'm still getting the same result. If I boot the phone normally, and then try to let RSD switch it for me, it does it, and then I get the same black screen and the flash mode failure error. Like I said there is a consumer replacement bootloader for the 1 that I've been able to use to fix this problem in the past, but if one exists for the two I haven't been able to locate it. So at this point I have a working OS, a working stock recovery, and no boot loader
think there was a 608 bootloader file, can't remember where i saw it
but it didnt work on 629 anyways
you might be able to root with http://forum.xda-developers.com/showthread.php?p=37438602
Root Droid 2 on Gingerbread 2.3.4 [WINDOWS]
i havent got it to work, but it only takes a few mins to download and run
Sent from my XT862 using xda premium
sd_shadow said:
think there was a 608 bootloader file, can't remember where i saw it
but it didnt work on 629 anyways
you might be able to root with http://forum.xda-developers.com/showthread.php?p=37438602
Root Droid 2 on Gingerbread 2.3.4 [WINDOWS]
i havent got it to work, but it only takes a few mins to download and run
Sent from my XT862 using xda premium
Click to expand...
Click to collapse
Yeah I tried that last night. I saw where you were having problems with it too. I had seen where a few months back there was someone else that was having this issue that you were trying to help walk them through, but the thread kinda died off, so I wasn't sure if there was ever a resolution to it. Ok well thanks for your time. I'll be sure to post an update for people coming behind me if I manage to get anywhere with it.
strabo231 said:
yeah we're on the same page there. When I do that, instead of getting the bootloader like I normally would, I'm just getting a blank black backlit screen, like the boot loader isn't there. Instead of getting bootlader D0.11 ect, It's just a blank screen. It doesn't matter which method I use to access it, both volume buttons and usb, up arrow and usb, whether there is a battery in the phone or not, I'm still getting the same result. If I boot the phone normally, and then try to let RSD switch it for me, it does it, and then I get the same black screen and the flash mode failure error. Like I said there is a consumer replacement bootloader for the 1 that I've been able to use to fix this problem in the past, but if one exists for the two I haven't been able to locate it. So at this point I have a working OS, a working stock recovery, and no boot loader
Click to expand...
Click to collapse
if you are still working on this a Bootloader Only
HS_S_signed_AP_BL_D11_cdma_droid2we_Consumer_replacer.zip
has been posted here http://sbf.droid-developers.org/cdma_droid2/list.php
If you're still looking to root, try Framaroot from here. It worked for me on .629. No idea about the bootloader however . Good luck though!
Hey,
I'm trying to root my T-Mobile LG G2 with stock 4.4.2, but the it just refuses to enter download mode. I've tried the standard method of entering download mode (powering down the phone, holding down the volume button, plugging in the USB cable from my computer), but only the LG logo appears on screen, then the battery percentage appears on screen, and then the phone begins to charge. I've tried using different USB cables and different PCs, but nothing seems to work.
Is there anything I'm doing wrong here? Any extra steps that need to be taken?
Any help would be greatly appreciated!
Try holding up and power and let go of power when the logo shows then push the and hold power again.
alil2cul4u said:
Try holding up and power and let go of power when the logo shows then push the and hold power again.
Click to expand...
Click to collapse
Do you mean hold power and volume up, plug phone in, let go of power and keep holding volume up, and then hold power and volume up again? I tried that, and the LG logo splashes on screen, disappears, splashes again, and then the screen goes black and the LED notification light blinks red. It doesn't pulse, like when it's charging, but it blinks a steady beat. It stops blinking and the phone boots up when I let go of the power and volume up buttons...
STAR8UCK said:
Do you mean hold power and volume up, plug phone in, let go of power and keep holding volume up, and then hold power and volume up again? I tried that, and the LG logo splashes on screen, disappears, splashes again, and then the screen goes black and the LED notification light blinks red. It doesn't pulse, like when it's charging, but it blinks a steady beat. It stops blinking and the phone boots up when I let go of the power and volume up buttons...
Click to expand...
Click to collapse
When I went into download mode, I only held the Volume Up button and plugged in the USB to the pc. I didn't hold power.
Same problem here ! Recieved d802 v20f OTA and after the update my phones refuses to entering download mode.
STAR8UCK said:
Hey,
I'm trying to root my T-Mobile LG G2 with stock 4.4.2, but the it just refuses to enter download mode. I've tried the standard method of entering download mode (powering down the phone, holding down the volume button, plugging in the USB cable from my computer), but only the LG logo appears on screen, then the battery percentage appears on screen, and then the phone begins to charge. I've tried using different USB cables and different PCs, but nothing seems to work.
Is there anything I'm doing wrong here? Any extra steps that need to be taken?
Any help would be greatly appreciated!
Click to expand...
Click to collapse
head1shot said:
Same problem here ! Recieved d802 v20f OTA and after the update my phones refuses to entering download mode.
Click to expand...
Click to collapse
I'm on rooted 20e with custom recovery and I entered download mode no problem. Make sure you're pressing only the Volume Up button when plugging in the USB connected to the computer and hold it until you enter download mode.
did anyone ever get it to go into download mode , I'm trying to get into download mode on my wifes phone to flask 4.2.2 so I can root
Damented said:
did anyone ever get it to go into download mode , I'm trying to get into download mode on my wifes phone to flask 4.2.2 so I can root
Click to expand...
Click to collapse
I'm having the same problem with my LG G2, I can't get into download mode. I've tried holding the power up button and plugging in a USB cable but my phone shows the LG logo and then starts charging the battery, I'm on stock rom, 4.4.2, no custom recovery. Is there a fix for this?
I had a similar problem with my T-Mobile LG G2 where I was rooted and accepted an OTA. It broke root and I couldn't get IOroot or Stumproot to work. Went to flash a downgrade and found the phone wouldn't go into download mode. It was NOT bricked. I finally tried playing around with the LG Mobile Support Tool (B2CAppSetup.exe). Of course it detected that my phone already had the latest firmware from T-Mobile, but then I clicked Options>Upgrade Recovery.
It downloaded for a while then I noticed it had put my phone into download mode (it said "Rooted" in red letters at the bottom). Then it flashed the same firmware over and I immediately tested, it entered download mode right away. But I didn't end up needing that as Stumproot was able to brute force it now after the recovery flash.
Anyway, I couldn't find an answer anywhere else. Most results also have a bricked phone, but that wasn't my issue. This solved my problem and maybe it could work for others.
ratchet26 said:
I had a similar problem with my T-Mobile LG G2 where I was rooted and accepted an OTA. It broke root and I couldn't get IOroot or Stumproot to work. Went to flash a downgrade and found the phone wouldn't go into download mode. It was NOT bricked. I finally tried playing around with the LG Mobile Support Tool (B2CAppSetup.exe). Of course it detected that my phone already had the latest firmware from T-Mobile, but then I clicked Options>Upgrade Recovery.
It downloaded for a while then I noticed it had put my phone into download mode (it said "Rooted" in red letters at the bottom). Then it flashed the same firmware over and I immediately tested, it entered download mode right away. But I didn't end up needing that as Stumproot was able to brute force it now after the recovery flash.
Anyway, I couldn't find an answer anywhere else. Most results also have a bricked phone, but that wasn't my issue. This solved my problem and maybe it could work for others.
Click to expand...
Click to collapse
This was my exact problem! Your solution worked perfectly, I was beating my head against the wall trying to find a way around.
Thanks so much !
ratchet26 said:
I had a similar problem with my T-Mobile LG G2 where I was rooted and accepted an OTA. It broke root and I couldn't get IOroot or Stumproot to work. Went to flash a downgrade and found the phone wouldn't go into download mode. It was NOT bricked. I finally tried playing around with the LG Mobile Support Tool (B2CAppSetup.exe). Of course it detected that my phone already had the latest firmware from T-Mobile, but then I clicked Options>Upgrade Recovery.
It downloaded for a while then I noticed it had put my phone into download mode (it said "Rooted" in red letters at the bottom). Then it flashed the same firmware over and I immediately tested, it entered download mode right away. But I didn't end up needing that as Stumproot was able to brute force it now after the recovery flash.
Anyway, I couldn't find an answer anywhere else. Most results also have a bricked phone, but that wasn't my issue. This solved my problem and maybe it could work for others.
Click to expand...
Click to collapse
Aaaaaaaahhh!!! u are my hero man!, ive been searching everywere and tried everything, im quite new to lg mobile phones, ive used apple and samsung before, but this easy and simple method worked for me, finally ive entered download mode again! :good:
I tried but mine says no problems to fix or somethibg like that
Sent from my LG-D801 using XDA Free mobile app
Thank you! I was pulling my hair out too! Out of desperation I took the g20 update after my phone had gotten real unsteady and rebooting constantly. Like the op I lost root and couldn't get into dl mode to save my life.
Sent from my LG-D801 using XDA Free mobile app
i still cant go to download mode...i tried all above... :crying:
ratchet26 said:
I had a similar problem with my T-Mobile LG G2 where I was rooted and accepted an OTA. It broke root and I couldn't get IOroot or Stumproot to work. Went to flash a downgrade and found the phone wouldn't go into download mode. It was NOT bricked. I finally tried playing around with the LG Mobile Support Tool (B2CAppSetup.exe). Of course it detected that my phone already had the latest firmware from T-Mobile, but then I clicked Options>Upgrade Recovery.
It downloaded for a while then I noticed it had put my phone into download mode (it said "Rooted" in red letters at the bottom). Then it flashed the same firmware over and I immediately tested, it entered download mode right away. But I didn't end up needing that as Stumproot was able to brute force it now after the recovery flash.
Anyway, I couldn't find an answer anywhere else. Most results also have a bricked phone, but that wasn't my issue. This solved my problem and maybe it could work for others.
Click to expand...
Click to collapse
After clicking Options>Upgrade Recovery it said "No upgrade items to fix." Thank you all for what you do at XDA.
verizonwiz said:
After clicking Options>Upgrade Recovery it said "No upgrade items to fix." Thank you all for what you do at XDA.
Click to expand...
Click to collapse
So this program no longer works and I'm having the same problem. I tried to do this with the LG suit which replaced lg mobile support. It just keeps saying I'm already on the latest firmware. Can anyone help?
I was running a lollipop bootloader and since i wanted to upgrade to marshmallow i had to update the bloodloader too, so i flashed a new stock boot.img obtained from a stock rom and soon after that i also flashed twrp, i think i somehow bypassed the new (locked?) bootloader with a custom recovery and now i'm stuck in "Rescue Mode".
Device is now stuck into that mode, i cannot turn it off or enter recovery, as soon as i restart my phone it goes into rescue mode, i have already tried all key combinations and also tried to force install from sdcard, my computer is not recognizing my device either so i can't use adb, i had no idea bricking a device like this was even possible, i'm quite desperate.. please help.
[How i fixed it] I somehow managed to get out of Rescue Mode, what i did wrong was not holding vol down + power long enough, you have to hold them down until phone restarts, that takes about 10 seconds, after that you will feel a vibration and huawei logo will appear, keep holding buttons down for 4-5 more seconds before taking your fingers off, it should then go into fastboot, once you're there adb should work and you will be able to unlock the bootloader if it is not unlocked already, after that you should be able push data to device or flash recovery again. If adb still doesn't work check usb drivers, your best bet is probably downloading HiSuite.
Awesome! :good:
Glad you got it going! I'll close this thread now! But here is your device section for future use, http://forum.xda-developers.com/t/huawei-p8
Cheers!
Please guys I need your help!
Phone model: Lg G Stylo h631 T-Mobile version.
Today I was using my phone and after finishing a call, my phone started to update itself. Then I received a error message. After that, I get stuck with a dead android guy on the screen, and I get the message "no command". I try Different combinations of buttons to solve this problem: Volume Down + Power release and then press the buttons again went the LG logo appear and have no luck. Then I try Volume Up + Power, also have no luck. I think I try almost every possible combination an nothing is working.
If anyone has any idea how to solve this issue please help me. Any help would be appreciated.
(Sorry for my bad English)
Make sure you download or have downloaded and installed the LG drivers from the LG website or any other reliable source or your phone will not be able to recover.
Unplug the phone, take out the battery and once the phone is completely off, replace the battery. Keep the phone powered off and unplugged. Plug a data capable (the usb that came with the phone is best) usb into a PC. Press the VOLUME UP button and HOLD it WHILE plugging the usb into your phone, (The PC should already be connected before plugging in the phone) continue to hold the VOLUME UP button until you pass the LG splash screen and you should then be in DOWNLOAD MODE. From there you can reflash the stock ROM that came with the phone. The stock ROMs are pretty easy to find here on XDA.
If you don't know what flashing a ROM is or means then XDA has plenty of guides for that as well. To return to stock you will need the LG Flash Tool or LG UP depending on which version you want to flash. Marshmalllow uses the LG UP program and Lollipop uses the LG Flash Tool. You can find guides and all the tools\software you will need to fix your phone right here on XDA or a little Google searching.
Moto G7 Power XT1955-5: Stuck in BootLoop at "Unlocked and Can't Be Trusted"
I made several attempts to install twrp-3.4.0-0-ocean to this new Moto G7 Power. I was able to Unlock the Bootloader, and even had TWRP running twice., but after it was rebooted it would never go back to TRWP, it would reboot to the Stock ROM. Then, runnng adb reboot bootloader would bring me back to the stock bootloader page.
Each time it boots, it has displayed the "Your Device Has Been Unlocked and Can't Be Trusted." page, and then would eventually boot. Annoying, but ok. It is what it is.
However, this last attempt to reboot from the stock bootloader has created an endless bootloop to that "Cant Be Trusted" page.
No combos of holding down the down volume for 3 seconds with the power key.. or holding down the power key for 15 or 20 seconds.. nothing works. All it does it turn the screen off for a couple of seconds and then goes back to the "Can't Be Trusted" warning page.
Well.. turns out it does work, it's just finnicky. This video showed me how to do it.. https://www.youtube.com/watch?v=fA0DHvbIlWY
Holding down the Down Volume and Power for several seconds until the screen goes black, release the buttons, then waiting a moment will allow the bootloader to appear.
1- Should I replace the stock rom? If so, how? I can't boot far enough along to run adb push.. and TWRP will not run.
What I cant do now is factory restore the device. Where can I get a stock rom, or any suggestions? I am pretty sure that's what I get for trying to use the xt1955_5.img file from Minimal+adb_fastboot_platform-tools_r29.0.6_2020 on unofficialtwrp.com's how to page, right?
Thanks in advance..
bryangrant4 said:
I made several attempts to install twrp-3.4.0-0-ocean to this new Moto G7 Power. I was able to Unlock the Bootloader, and even had TWRP running twice., but after it was rebooted it would never go back to TRWP, it would reboot to the Stock ROM. Then, runnng adb reboot bootloader would bring me back to the stock bootloader page.
Each time it boots, it has displayed the "Your Device Has Been Unlocked and Can't Be Trusted." page, and then would eventually boot. Annoying, but ok. It is what it is.
However, this last attempt to reboot from the stock bootloader has created an endless bootloop to that "Cant Be Trusted" page.
No combos of holding down the down volume for 3 seconds with the power key.. or holding down the power key for 15 or 20 seconds.. nothing works. All it does it turn the screen off for a couple of seconds and then goes back to the "Can't Be Trusted" warning page.
Well.. turns out it does work, it's just finnicky. This video showed me how to do it.. https://www.youtube.com/watch?v=fA0DHvbIlWY
Holding down the Down Volume and Power for several seconds until the screen goes black, release the buttons, then waiting a moment will allow the bootloader to appear.
1- Should I replace the stock rom? If so, how? I can't boot far enough along to run adb push.. and TWRP will not run.
What I cant do now is factory restore the device. Where can I get a stock rom, or any suggestions? I am pretty sure that's what I get for trying to use the xt1955_5.img file from Minimal+adb_fastboot_platform-tools_r29.0.6_2020 on unofficialtwrp.com's how to page, right?
Thanks in advance..
Click to expand...
Click to collapse
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk
Glad you're out of boot loop.
Recovered from bootloop and "dead" bootloader screen! Tips to recovery
I was able to Rescue the device from periodic BootLoops and a dead end Bootloader screen.
I referenced the information on this thread in the XDA forums, specifically the “Motorala Unbricking Tools” section.
I then tried the "LMSA: Lenovo's Motorola Smart Assistant" thread to find the link to the Lenovo / Motorola download page.
The Rescue software is a bit clunky. Powerful, but clunky.
There are also some cool tools such as Clipboard Copy Text between Device and PC, a Gif Maker, a Ringtone Maker, and a SCREEN RECORDER!!
Back on Track with the Rescue:
-Linux or Mac versions are NOT available; Windoze only.
-You will need at least 2gb of ram in your virtual Windoze7 machine to run it or it will not run in a useful manner.
- Parallels16/Windoze7-64bit worked fine.
-WINE based installs will NOT work.
To run, you will need to enable USB Debugging, although there are two other ways to connect the phone I did not also try. There even appears to be a way to rescue even a truly bricked dead device.
To Rescue your device:
Download, Install, and Run Rescue and Smart Assistant.
The Rescue process will NOT relock your bootloader.
Select the Rescue tab, then select Rescue Now. If you need to backup the device, try the Backup button right next to the Rescue Now button.
The application has some bugs, shortcomings.. here's some heads up to reduce Stress caused by those bugs..
The software will ask you to select the phone you own. The slider dialogue UI is badly done, so you will go back and forth a dozen times before learning how to navigate the menu. It might auto-recognize, but it did not on mine. Good luck!
Next, download the ROM.. the progress bar does not reflect what is actually going on. Once the 2bg down is 100% complete, it will sit there for a LONG TIME doing nothing. Dont kill the app and restart. It's actually busy unpacking the .zip Rom file into a directory tree on your harddrive. Just go eat some lunch, and come back.
Then, a similar issue occurs when you install the ROM. The progress bar is pretty much done, it just sits there doing nothing.. Let it go for a long time.. it's actually doing it's job, and the progress bar is just badly done.
If you are going to use the backup.. TURN OFF YOUR POWERSAVING stuff on both ends. If it is interupted by Power Saving/Sleep mode, the software will start at the beginning. The backup process takes hours, not minutes, so this is not a good result.
Once backed up, if you are moving to a new phone, there is a couple of ways to do that. I am going to perform these functions today or tomorrow, and will update with the results of those efforts.