Related
Hey, I rooted, s-off/hbooted my phone and used Clockworkmod to install a ROM.
Now it won't go away no matter what I've tried and I want to be able to turn my phone off and charge it without seeing that annoying recovery screen.
I've backed up all my apps on to SD, wiped data and factory resetted with CWM and the phones built in factory reset yet it still comes back to haunt me.
What do I need to do to make this go away and revert my phone back to it's original out of box state?
CWM should come with an uninstall guide and a notice of how annoying this is, I see it's quite a widespread problem for everyone trying to calibrate the battery with no clear answer
Install the correct HTC RUU for your desire hd.
prank1 said:
Install the correct HTC RUU for your desire hd.
Click to expand...
Click to collapse
Much appreciated, you get my first thanks.
For anyone else in need here's where I got mine (every other ROM and RUU is there too)
http://forum.xda-developers.com/showthread.php?t=868610
Just to be sure, can I just put the RUU on my storage card and use CWM recovery to install it?
Thanks for the.. thanks lol
I don't know but it really doesn't matter, better if you flash it from bootloader. If you were eng hboot s-off then your dhd will become 100% stock (if you installed the correct htc ruu). If you were radio s-off you will still have s-off afterwards. I don't think this affects warrentee issues as long as you have installed the correct rom.
On another note, I am sure I read somewhere some instructions on how to calibrate your battery and fix this problem. But you may have to do a little searching for it.
Sent from my Desire HD using XDA App
even on stock the phone goes into recovery anyway just it don't show the recovery screen. reason it does so i've read is for the led light to come on lol
spookamiester that link just brings you back to this thread so i've placed a link to all HD files and it has all the RUU files there
http://forum.xda-developers.com/showthread.php?t=841207
just check the first two links for ruu files
and a guide here to install ruu's
http://forum.xda-developers.com/showthread.php?t=864054
spookamiester said:
CWM should come with an uninstall guide and a notice of how annoying this is, I see it's quite a widespread problem for everyone trying to calibrate the battery with no clear answer
Click to expand...
Click to collapse
Maybe I am being simple but I see this posted everywhere as a problem, it in no way affects battery calibration, yes when the phone is turned off and plugged in it boots into recovery (it also does this with the stock ROM) so what? It's still charging and from CW you can then wipe the battery stats which is required to complete your calibration anyway.
What exactly is the problem with it booting into CW when turned off and plugged in
and to answer the question, reflash with the appropriate RUU
Or just flash recovery.img from a stock rom
Is the s-off that stops the receiving of OTA's ?
Sent from my Desire HD using XDA App
ghostofcain said:
Maybe I am being simple but I see this posted everywhere as a problem, it in no way affects battery calibration, yes when the phone is turned off and plugged in it boots into recovery (it also does this with the stock ROM) so what? It's still charging and from CW you can then wipe the battery stats which is required to complete your calibration anyway.
What exactly is the problem with it booting into CW when turned off and plugged in
Click to expand...
Click to collapse
First of all I'd like to thank everyone for the responses, should be able to get things sorted now.
In response to the charging in CWM, I tried it for over an hour after full charge on and the LED remained amber, I turned the phone back on and the battery was at 99% which leads me to believe that it doesn't actually charge in CWM recovery, I tried this on stock and within 10 minutes after full charge on I got the green light off. I've asked in other threads if anyone can confirm the phone charge whilst in CWM but so far no confirmation, just similar results.
I'll keep my eyes pealed for answers but I don't think it works with CWM and can't find a way to charge whilst off without CWM recovery popping up.
spookamiester said:
First of all I'd like to thank everyone for the responses, should be able to get things sorted now.
In response to the charging in CWM, I tried it for over an hour after full charge on and the LED remained amber, I turned the phone back on and the battery was at 99% which leads me to believe that it doesn't actually charge in CWM recovery, I tried this on stock and within 10 minutes after full charge on I got the green light off. I've asked in other threads if anyone can confirm the phone charge whilst in CWM but so far no confirmation, just similar results.
I'll keep my eyes pealed for answers but I don't think it works with CWM and can't find a way to charge whilst off without CWM recovery popping up.
Click to expand...
Click to collapse
I have spent quite a while in recovery and I am fairly sure it's charging I wouldnt be surprised that the green led didn't function though? I don't really see how it wouldn't charge surely it a hardware thing when the power is attached?
Update: I use QtADB to give a GUI interface to ADB, have spent the past 15 minutes monitoring the battery state whilst in Clockwork recovery and it is most defintetly charging so you needn't worry about that
I bought the phone from Hong Kong with stock ROM. Rooted, S-Off and installed CWM but never flashed any ROM. But I have same the problem, screen will boot to recovery when I want to charge. I found there are a lot of DHD guys have the same problem here in China or Hong Kong..... and no solution found in any forum here yet. Some said it's a bug on CWM.
Anyway. I found an alternative myself. Instead of using the DHD original charger, I used the I9000 charger to charge the DHD. It worked perfectly (100% charged) and no recovery screen appeared so far......
Hey guys!
I have the original Desire HD stock ROM but I have clockwork mod recovery.
Could you guys provide a step by step guide on how to remove and replace with original recovery image?
I would really appreciate all the help!
xmoo said:
Or just flash recovery.img from a stock rom
Click to expand...
Click to collapse
I have a file recovery.img. How do I flash it to the DHD?
I'd like to know this as well. I have the Clockwork bootloader installed. It's OK, but I changed my mind - I'd like to keep this phone as close as possible to factory-standard and use a different phone for hacking. Is there a step-by-step guide to reverting a DHD back to normal so I can benefit from the regular OTA updates?
Thanks!
Reflashing the ruu is the hard and long way.
Just download the stock recovery.img which west2cool was good enough to post for me. (Cheers again I didn't really feel like installing windoze just for that).
Then use fastboot - "fastboot flash recovery recovery.img"
dr.m0x said:
Then use fastboot - "fastboot flash recovery recovery.img"
Click to expand...
Click to collapse
And make sure it is FASTBOOT mode. Flashing fails otherwise (unless I did something stupid).
Sorry, I'm a newb at this.
When I boot by doing vol-down + pwr I get a mainly white screen with three Androids skateboarding at the bottom. At the top it says
ACE PVT SHIP S-OFF
HBOOT-0.85.0007
The top option is "FASTBOOT", so I press pwr once to select that.
Next I see four options:
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
I do not see an option to reflash a recover image.
If I go into "RECOVERY", I see the green text on a black background of ClockworkMod v2.5.1.3. There is an option to apply an update.zip, however that's clearly not the same thing as I was instructed to do.
Detailed step by step instructions would be much appreciated!
THANKS!
I'm resurrecting my laptop with ubuntu 10.10 x64 right now (so I can build gingerbread) so can't help until later. If someone doesn't beat me to it, I will up a proper set if instructions along with the links you will need once my laptop is fully functional again.
Sent from my performance enhanced Desire HD
Ok buddy, my lappy lives again
1. Download the recovery.zip posted earlier on in the thread.
2. Extract recovery.img from the recovery.zip (best to extract it somewhere easy like a new folder called c:\fastboot)
3. Download fastboot from here. http://developer.htc.com/adp.html#s2
4. Make sure fastboot.exe and recovery.img are in the same directory (e.g. c:\fastboot)
5. Reboot your phone as you did before (while holding vol down + power)
6. Select fastboot and push the power button
7. Plug your phone into your computer - it should change the message to "FASTBOOT USB"
8. Open a terminal (push start button and type in "cmd" to get one if you don't know how).
9. Type "cd c:\fastboot" and press enter.
10. Type "fastboot flash recovery recovery.img"
11. You should see a message which says something like sending ... send complete ... done.
12. To test: Push the power button on your phone once, push volume down once to highlight recovery, push power button. It should boot you to a screen with a red triangle.
13. Push vol up + power button to bring up the stock recovery menu
14. Push power button to reboot
Hopefully thats detailed enough
So I am totally lost. Have exhausted all my knowledge on these issues, but i will take u guys through my process step by step.
Right now my problem is that i am unable to charge my one x in any way. it will only respond to being connected through my pc and obviously that wont charge very well. My phone will boot to the home screen but will go from being 35% charged to 0% and just reboot. what lead up to this was my installing android revolution 1.2.2 along with the interim clockwork mod. Upon reboot is where all the problems began. I accidently forgot to wipe before installing and now this is where im at. Cant boot into recovery. cant load default recovery because battery is too low. nothing except this impossible battery screw up is all i get. and now oncve i unplug my phone from pc, its shuts down after a few moments with no charge. Im at my wits end guys. anyone know what i can do?
These threads may help:
http://forum.xda-developers.com/showthread.php?t=1596155
http://forum.xda-developers.com/showthread.php?t=1599748
chukwu77 said:
So I am totally lost. Have exhausted all my knowledge on these issues, but i will take u guys through my process step by step.
Right now my problem is that i am unable to charge my one x in any way. it will only respond to being connected through my pc and obviously that wont charge very well. My phone will boot to the home screen but will go from being 35% charged to 0% and just reboot. what lead up to this was my installing android revolution 1.2.2 along with the interim clockwork mod. Upon reboot is where all the problems began. I accidently forgot to wipe before installing and now this is where im at. Cant boot into recovery. cant load default recovery because battery is too low. nothing except this impossible battery screw up is all i get. and now oncve i unplug my phone from pc, its shuts down after a few moments with no charge. Im at my wits end guys. anyone know what i can do?
Click to expand...
Click to collapse
I assume you were on 1.19 software? This happened to a friend yesterday. He ended up fastboot erase cache. Fast boot reboot bootloader. Get into recovery and plug up to ac power. The light comes on for a min. Or so then goes off. When it goes off unplugg it then plug it back in. Keep this up till you have some juice. Then fastboot flash the stock recovery relock bootloader, then get ruu 1.26.707. Run that ruu and it should boot. After that you can flash all the roms you want.
Sent from my HTC One X using XDA
Thanks so much, I will try and let u guys know what is going on. FYI i dont see a fastboot erase cache on my screen so how would i go about doing that?
So i locked my oem back before i could boot stock revocery and stock ruu. anyone know how i would ebable to unlock my oem. ADB doesnt appear to re open it with the unlock command. i get a command error message. And yes the bin file from htc is in the fastboot folder. smh
I cant get a charge and the fastboot wont let me unlock oem or load a new recovery.... what now?
cmon guys, i spent 10 hours trying to fix this yesterday, im close to just chucking this thing into the garbage and going back to my nexus. someone please give a little help. i cant charge the phone so i cant load any stock RUU. fastboot is pretty much useless right now. nothing seems to do anything other than show a list of commands when i try to unlock oem again. im desperate so someone please help
chukwu77 said:
cmon guys, i spent 10 hours trying to fix this yesterday, im close to just chucking this thing into the garbage and going back to my nexus. someone please give a little help. i cant charge the phone so i cant load any stock RUU. fastboot is pretty much useless right now. nothing seems to do anything other than show a list of commands when i try to unlock oem again. im desperate so someone please help
Click to expand...
Click to collapse
I don't know what to tell you bro. If you locked the bootloader before putting stock recovery back on the phone. An ruu won't work anyway. Have you tried fastbooting a system.IMG and a boot.IMG. to see if it might boot? If you have your bin file from when you first unlocked. Try sending that again to unlock. Hopefully someone will pop in and give you a hand.
Sent from my HTC One X using XDA
what commands should i use to try to get it back to normal? everything is saying my battery is too low, which really thats what is keeping me from doing anything to help the situation. I need to charge but none of the threads i have read with steps for charging have worked
chukwu77 said:
what commands should i use to try to get it back to normal? everything is saying my battery is too low, which really thats what is keeping me from doing anything to help the situation. I need to charge but none of the threads i have read with steps for charging have worked
Click to expand...
Click to collapse
Did you do a backup after brick?
I have a copy of the main files... (data.img, system.img and boot.img).
i Use this commands:
Examples
Manual Nandroid restore
Make a Nandroid backup, and copy the folder off your SD card to your desktop.
cd ~/Desktop/path/to/backup/
fastboot flash userdata data.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
MORE INFO HERE.
For the battery... try a charger with little more volts or amperes... you can buy some usb chargers on any electronic store.
thanks i will get on it and let u know what happens. Much appreciated! I did not do a backup after brick but before brick i did. I am using the transformer prime charger its a quad core tablet and it reads as having higher volts/amp than all my others.
your one x stills bricked?
No solution?
Hi all. I hope some kind person here can help me get to the bottom of this.
I unlocked my bootloader earlier from htcdev. I then installed super user.
I wanted to install Leedroid ROM so downloaded the files and used fasboot to install the version of boot.img that comes with it. Problem is that I forgot to transfer over the rom zip file to the device before doing it so now I'm stuck. I know, I just got distracted. My fault I know. I just feel totally sick at the thought of just having bought a £450 to have broken it less than a week later.
(I have successfully rooted my old desire and a wildfire in the past without bother so I do have experience of rooting....just looking like and feeling like an idiot now!)
I had a nandriod backup done from before flashing boot.img and tried to restore.. It says restore was successful but it got stuck on the HTC splash screen. Some help would be mighty appreciated.
The bootloader is now locked again but I think I still have CWM recovery installed however I can't access it any more. The phone boots directly into the bootloader and doesn't attempt to boot.
I've tried unlocking the bootloader again but now it says the battery is too low. I keep trying to turn the phone off in fastboot to let it charge but it just starts up again? Any Ideas?As I said I can't get it to charge so I can't unlock the boot loader again. I've tried running stock 1.29 RUU but again not enough juice.
Just to confirm: My HBOOT is 0.94.0000; The bootloader is relocked.
Any help would be very appreciated, I am at my wits end. Thanks in advance
http://forum.xda-developers.com/showthread.php?t=1546970
Try that. download and extract boot.img and then flash the boot.img that should then work. If not try looking for stock roms that are flashable through clock work mod and get hold of that boot.img. hope this helps
Sent from my HTC One X using XDA Premium HD app
Also if you got cwm you can go into it and charge the phone from there
Sent from my HTC One X using XDA Premium HD app
This is just a thought, maybe when the battery dies the phone will switch off on its own, and then u can charge it.
malcovitch said:
Also if you got cwm you can go into it and charge the phone from there
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for all the replies. Unfortunately, I can no longer access CWM. When I go to recovery it shows the "Quietly Brilliant" Screen then goes to fastboot menu, no CWM?
UPDATE: Ok, I have managed to unlock my bootloader again. In another thread mevorach advised running a batch script that displays the voltage and reboots the phone. Id created this script and waited until the phone charged up enough, then I ran the unlock command again.
I now have access to CWM again. Feels like I'm starting to get somewhere.
mevorach said:
Hi
I have a solution for you
make a batch file :
" @echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
put this file in the directory where you have fastboot.exe adb.exe and all other
files , also put the unlock.bin file that you have from htcdev
put your phone to bootfsatusb , and run the batch file , you will see the voltage
off the battry each time it loop , after an hour or two you will have enough power(~3.68mv) to unlock it , then charge it and do what ever you want
Click to expand...
Click to collapse
cosmicovertones said:
Thanks for all the replies. Unfortunately, I can no longer access CWM. When I go to recovery it shows the "Quietly Brilliant" Screen then goes to fastboot menu, no CWM?
Click to expand...
Click to collapse
That's because of low battery.
have you read this : http://forum.xda-developers.com/showthread.php?t=1609190
which recovery version that you have ? If it is 5.8.3.1, what you can try is:
attach the charger to it's usb.
the phone will boot to bootloader
scroll to power down
it will shut down
don't take out the usb cable/charger from the phone.
if the phone starts again to bootloader
scroll again to power down
(normally it will stay shut down when doing this power down the second time)
let it charge for an hour.
on PC get ready the fastboot command to unlock the bootloader
fastboot flash unlocktoken Unlock_code.bin and enter
status will show waiting for device
connect your phone and power on
and see whether the "low battery" warning still there.
if successful, unlock the phone (choose yes)
when it reboot - hold power + volume down to force it to bootloader
fastboot flash boot boot.img for the nandroid backup that you restore earlier
once done reboot the phone.
---------- Post added at 02:45 PM ---------- Previous post was at 02:43 PM ----------
cosmicovertones said:
UPDATE: Ok, I have managed to unlock my bootloader again. In another thread mevorach advised running a batch script that displays the voltage and reboots the phone. Id created this script and waited until the phone charged up enough, then I ran the unlock command again.
I now have access to CWM again. Feels like I'm starting to get somewhere.
Click to expand...
Click to collapse
that's good.
what you need now is to flash the boot.img for the nandroid backup that you have which you mentioned you restored earlier. without a correct boot.img for your nandroid backup, you will stuck on "quietly brilliant"
Thanks for your reply,
ckpv5 said:
That's because of low battery.
have you read this : http://forum.xda-developers.com/showthread.php?t=1609190
Click to expand...
Click to collapse
Yes, I've gone through all the pages.
ckpv5 said:
which recovery version that you have ? If it is 5.8.3.1, what you can try is:
Click to expand...
Click to collapse
When I managed to get into CWM I realised I was not on the latest, I have now managed to flash 5.8.3.1
ckpv5 said:
attach the charger to it's usb.
the phone will boot to bootloader
scroll to power down
it will shut down
don't take out the usb cable/charger from the phone.
if the phone starts again to bootloader
scroll again to power down
(normally it will stay shut down when doing this power down the second time)
let it charge for an hour.
on PC get ready the fastboot command to unlock the bootloader
fastboot flash unlocktoken Unlock_code.bin and enter
status will show waiting for device
connect your phone and power on
and see whether the "low battery" warning still there.
if successful, unlock the phone (choose yes)
Click to expand...
Click to collapse
I have managed to get to this step.
ckpv5 said:
when it reboot - hold power + volume down to force it to bootloader
fastboot flash boot boot.img for the nandroid backup that you restore earlier
once done reboot the phone.
that's good.
what you need now is to flash the boot.img for the nandroid backup that you have which you mentioned you restored earlier. without a correct boot.img for your nandroid backup, you will stuck on "quietly brilliant"
Click to expand...
Click to collapse
I tried to restore the boot.img that backed up earlier but it is getting stuck at the "quietly brilliant" screen.
I also tried to restore all of the nandroid backup without success.
Any ideas how I can get a working boot.img to flash?
I am currently leaving the phone on the "quietly brilliant" screen (the charge LED is on) to see if I can get enough charge to restore the stock recovery, lock the bootloader and flash the 1.29 europe RUU. Is this a good plan or should I be trying something else?
Based on my experience, when you're not sure which boot.img belongs to which nandroid, a stock boot.img will work.
But if that also fail then the next best thing to do is flash RUU and make sure you have the right official RUU for your phone. Wrong RUU will not work.
Ok, will do. Thanks for the help
I'm trying to leave the phone on charge for a couple of hours, I'll then try flash the boot_signed.img file from the RUU.zip andfailing that I'll try the whole RUU.
Same situation here...
cosmicovertones said:
I'm trying to leave the phone on charge for a couple of hours, I'll then try flash the boot_signed.img file from the RUU.zip andfailing that I'll try the whole RUU.
Click to expand...
Click to collapse
I'm having the exact same problems, and have pretty much done the same steps in my attempts to get the phone back to life. Current status is that it's locked and can't unlock it due to low battery, but that .bat file seems to be helping - battery voltage is going up, so eventually I should be able to do something.
My plan however is to try RUU (tried everything else already, when I had battery and the phone was unlocked and had clockworkmod).
Anyway please keep this thread up to date with your progress.
If you broke your phone in the first week...well, I opened the box of mine 15 minutes before bricking it, hadn't even installed the SIM card (I bought it from an amazon seller and he sent me the Asian version, Thai keyboard and all - that's what started all this).
Ok... so I flashed the boot_signed.img file from the official 1.29 ruu. The phone then rebooted and again froze on the "quietly brilliant" screen. I then locked the bootloader again and rebooted. This time it booted fine
Once booted I left it to charge fully, I then was able to run the 1.29 RUU for my phone.
Next step I unlocked the bootloader again and flashed CWM 5.8.3.1. Performed a nandroid backup and flashed the super user zip file.
It is fully functioning up to this point now.
My next step is to follow ALL the steps (this time lol) to get leedroid one xtreme v5 rom installed again.
I'm getting the phone back to 100% charge before doing the next steps, just incase I need to undo anything I REALLY don't want to run into the low battery issue again.
cfsmp3 said:
I'm having the exact same problems, and have pretty much done the same steps in my attempts to get the phone back to life. Current status is that it's locked and can't unlock it due to low battery, but that .bat file seems to be helping - battery voltage is going up, so eventually I should be able to do something.
My plan however is to try RUU (tried everything else already, when I had battery and the phone was unlocked and had clockworkmod).
Anyway please keep this thread up to date with your progress.
If you broke your phone in the first week...well, I opened the box of mine 15 minutes before bricking it, hadn't even installed the SIM card (I bought it from an amazon seller and he sent me the Asian version, Thai keyboard and all - that's what started all this).
Click to expand...
Click to collapse
As the earlier quote regadring the bat file, you will have enough power(~3.68mv) to unlock it. Once it gets to ~3.689mV you will be able to unlock the phone.
Did you have it unlocked at one point? If so you can use the same unlock file HTC sent you to unlock again.
Once you have it unlocked run the bat script again until the power is around the same level again, then flash cwm 5.8.3.1 through fastboot.
Once you have this you can turn the phone off and plug it into your charger. I had mine plugged in for over an hour. The charge was then enough to flash the boot_signed.img file from the RUU for my phone, and as I said it booted fine.
Hope this all helps, I know exactly how you feel.
My killer mistake was forgetting to transfer the leedroid rom zip to the phone and I wrongly assumed CWM could mount the internal storage as USB to transfer the rom to the phone; like earlier versions.
cosmicovertones said:
Ok... so I flashed the boot_signed.img file from the official 1.29 ruu.
Click to expand...
Click to collapse
Where did you get that file? Digging into %TEMP% or is there an official repository or something?
Why not install the full RUU, by the way, to start over?
Anyway your post gives me hope I'm currently letting the .bat file run - but the plan was to do RUU if at all possible, rather than unlock, add clockworkmod, etc...
I couldn't get it to charge much higher than was required to unlock etc.. so I needed to get CWM installed to get it to charge properly.
Also, I couldnt get the boot_signed.img to flash I assume cause the bootloader is locked.
I got the boot_signed.img by opening the RUU installer but not clicking next just having it open.
Then I got the temp folder on my pc and searched in it for zip files. Only 2 appeared. The rom was called "rom.zip"
I then copied this to my desktop and opened the zip. Then I was able to extract the boot_signed.img file to the fastboot folder on my pc and got it flashed across.
I think you're probably gonna have to unlock the bootloader to fix your problem.
cosmicovertones said:
I couldn't get it to charge much higher than was required to unlock etc.. so I needed to get CWM installed to get it to charge properly.
Click to expand...
Click to collapse
I got some help in IRC on the charge front. Indeed powering off the phone from the FASTBOOT menu *without* having a cable plugged in (otherwise the damn thing won't stay off) puts it in a chargeable state. What I did was plug it in the wall charger for a bit. Then they suggested that when the phone is off you can plug it to the PC and get battery status with adb, which I did - like this:
adb shell cat /sys/class/power_supply/battery/status
adb server is out of date. killing...
* daemon started successfully *
Charging
adb shell cat /sys/class/power_supply/battery/capacity
30
[plugged again to wall charger for a while]
adb shell cat /sys/class/power_supply/battery/capacity
42
So it's looking good. I'll let it charge for a while and once it's done, relock (I just installed cwm again), and try RUU.
cosmicovertones said:
I got the boot_signed.img by opening the RUU installer but not clicking next just having it open.
Then I got the temp folder on my pc and searched in it for zip files. Only 2 appeared. The rom was called "rom.zip"
Click to expand...
Click to collapse
OK, I just did and saved the file somewhere in case it's needed.
We'll see
for the RUU to run successfully you need to flash the stock recovery (to get rid of CWM) and lock the bootloader AFTER you've flashed the boot_signed.img file. This is to get the RUU to run on an unmodified phone.
Once you get that run you can re unlock, flash CWM and super user binaries if you want.
After this experience, I'll be checking and double checking the steps provided in future. What an ass I am!!! ha just goes to prove just cause I was successful on my old htc desire and the gf's wildfire it's no guarantee I know what I'm doing
Also, I've now successfully installed Leedroid One Xtremem V5.1. Just after restoring my apps using titanium backup.
Let me know how you get on
EDIT: I think the reason I had to flash the boot_signed.img file is because I flashed the leedroid boot.img then realised my mistake of not having the rom to flash and to compound the issue relocked the bootloader and the low battery. You might be able to get away with charging and running your RUU. If that fails I would restore stock recovery, lock the bootloader and retry the RUU
cosmicovertones said:
for the RUU to run successfully you need to flash the stock recovery
Click to expand...
Click to collapse
Nope It just needs to be locked, but it was happy to run with cwm installed.
So I got it to work (back to square one, because I still need to change the ROM). I actually did more stuff than needed (because I was trying two approaches as the same time), but in summary:
- That glorious 5 line .bat file works, and allows the battery to charge, so reach a state where you can at least lock/unlock and flash. For me the battery changes from 'low charge' to 'good' at 3615mV.
- You can also turn the phone off from the service menu, but you have to be sure no cable is plugged, or it will turn itself back on in a couple seconds.
- The battery charges if the phone is off, using a wall charger.
- With the phone off, you can still plug in on a PC and find battery status (whether it's charging or not) and current charge (in %) with adb (another command line tool, like fastboot).
- With 30% or more of load, you can run RUU and get the phone back to factory state.
- You can't use a RUU for a different model, if your model is from Asia you need the Asian RUU, you can't just install a European one. You don't like a Vietnamise keyboard? Tough ****.
Anyway, since I know have all the tools and more confidence I'll just go ahead and try again. Starting will a full charge of course
Awesome!! I'm glad you got it to work, and I hope this thread serves as some help for others.
The damn battery charge issue had me worried. That bat file is really a lifesaver!
Thanks for all the info. Hope not to need it but mistakes can be made.
I have an issue that I hope someone can help me with, my daughters Moto G6 Play (Completely stock, 15months old) has just started boot looping from a black screen to Moto blue screen only.
I can move it to boot up screen using (Power and Volume Down) key but it will only stay there a few seconds before it then loops again.
I have tried "Recovery Mode" / "Power off" and they just do the same thing go into loop again.
I thought it was a battery issue, but I think this is a knock on affect of the phone boot looping so much. Also in boot up screen it was stating the battery was NOK
Took it apart and ordered new battery and installed but still the same issue.
Now before this second battery runs out as it wont charge while in this state, I wondered if anyone can help me resurrect it??
I will add its been a few years since I have flashed phones with dev roms etc (HTC One X days...) but I dont think I have even enabled USB debugging in the menu options..
Thanks in advance
Andy
Perchy35 said:
I have an issue that I hope someone can help me with, my daughters Moto G6 Play (Completely stock, 15months old) has just started boot looping from a black screen to Moto blue screen only.
I can move it to boot up screen using (Power and Volume Down) key but it will only stay there a few seconds before it then loops again.
I have tried "Recovery Mode" / "Power off" and they just do the same thing go into loop again.
I thought it was a battery issue, but I think this is a knock on affect of the phone boot looping so much. Also in boot up screen it was stating the battery was NOK
Took it apart and ordered new battery and installed but still the same issue.
Now before this second battery runs out as it wont charge while in this state, I wondered if anyone can help me resurrect it??
I will add its been a few years since I have flashed phones with dev roms etc (HTC One X days...) but I dont think I have even enabled USB debugging in the menu options..
Thanks in advance
Andy
Click to expand...
Click to collapse
Just use my guide, at the bottom of it it has everything you need to reflash stock firmware hold the power and volume down button until you get to the fastboot/ bootloader screen, also since you replaced the battery and did your own repair we still might not be able to help you because there's to many variables of user interference now, and yes Google kind of has made it a bit more complicated to root devices now unfortunately
Thanks for the reply, please can you put a link to your guide?
Perchy35 said:
Thanks for the reply, please can you put a link to your guide?
Click to expand...
Click to collapse
https://forum.xda-developers.com/g6-play/how-to/guide-t3929928
Thanks one last question before I attempt to go ahead, is it possible to "Catch" the phone between boot looping to reflash stock image?
As at the moment there is as I have stated 1/2secs between the boot screen and then it moving to "Moto" screen and then around to black screen again.
Perchy35 said:
Thanks one last question before I attempt to go ahead, is it possible to "Catch" the phone between boot looping to reflash stock image?
As at the moment there is as I have stated 1/2secs between the boot screen and then it moving to "Moto" screen and then around to black screen again.
Click to expand...
Click to collapse
Yes. Hold power and volume down, it'll look a few times and catch, you'll see fastboot. The Android guy and red and white text. May take a few loops
sorry one more thing, how do I find out the image version I need as I was unable to get this from phone before it starting acting up!?
Perchy35 said:
sorry one more thing, how do I find out the image version I need as I was unable to get this from phone before it starting acting up!?
Click to expand...
Click to collapse
Whats the carrier?
The phone was bought direct from Amazon so in my mind a generic model to take any SIM.
Perchy35 said:
The phone was bought direct from Amazon so in my mind a generic model to take any SIM.
Click to expand...
Click to collapse
Here you go. Amazon Jeter Firmware. That's the main folder.
I see there is the latest Android 8 and also an Android 9 version? This was never rolled out though... I will probably just put the following
XT1922-9_JETER_AMZ_8.0.0_OPPS27.91-140-6_cid18_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Perchy35 said:
The phone was bought direct from Amazon so in my mind a generic model to take any SIM.
Click to expand...
Click to collapse
Spaceminer is correct, once you catch that sweet spot with the phone to get it in bootloader/fastboot mode just flash the firmware and you should hopefully be good to go, if you want it rooted my guide covers that to but let's just get you a working phone first before you try to root lol
---------- Post added at 05:56 PM ---------- Previous post was at 05:55 PM ----------
Perchy35 said:
I see there is the latest Android 8 and also an Android 9 version? This was never rolled out though... I will probably just put the following
XT1922-9_JETER_AMZ_8.0.0_OPPS27.91-140-6_cid18_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
You can either flash 8 or 9, what I would do is flash 8 then update it to 9 then if you want it rooted root it
Perchy35 said:
I see there is the latest Android 8 and also an Android 9 version? This was never rolled out though... I will probably just put the following
XT1922-9_JETER_AMZ_8.0.0_OPPS27.91-140-6_cid18_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Hey so out of curiosity did you get it fixed and working?
ninjakira said:
Hey so out of curiosity did you get it fixed and working?
Click to expand...
Click to collapse
Thanks for getting back to me!
I have just started yesterday getting my laptop ready, downloading image file, setting up "minimal adb" and getting motorola ID sorted.
Also can I check that without USB debugging selected this method will override and flash still?
Perchy35 said:
Thanks for getting back to me!
I have just started yesterday getting my laptop ready, downloading image file, setting up "minimal adb" and getting motorola ID sorted.
I am having issue with the last part, getting "The credentials you provided cannot be determined to be authentic" ?
Also can I check that without USB debugging selected this method will override and flash still?
Click to expand...
Click to collapse
Wait what are you needing your Moto id for? The links for the stock firmware are in my guide, just follow the bottom section of it
Oh ok in the guide it states its needed for Windows user, Excerpt below:
Motorola bootloader unlock request here https://motorola-global-portal.custh...-your-device-a
ok just started the process, I cant get past first command at the moment "fastboot oem fb_mode_set" and this is returning "waiting for any device".
I have tried toggling into the boot screen and selecting "Restart bootloader"..
Perchy35 said:
Oh ok in the guide it states its needed for Windows user, Excerpt below:
Motorola bootloader unlock request here https://motorola-global-portal.custh...-your-device-a
Click to expand...
Click to collapse
If you don't have the bootloader unlocked then that is something you can do if you want the phone rooted if not you don't have to unlock the bootloader to flash stock firmware
Perchy35 said:
ok just started the process, I cant get past first command at the moment "fastboot oem fb_mode_set" and this is returning "waiting for any device".
I have tried toggling into the boot screen and selecting "Restart bootloader"..
Click to expand...
Click to collapse
You either didn't install adb minimal or you have a bad cord, type fastboot devices and if nothing pops up saying you have a device in fastboot then it's one of the 2 things I said, extract the contents from the rar or zip file you got from adb minimal download, then install what you extracted
I have installed the adb minimal 1.4.3 (Latest), just tried three different leads with the command fastboot devices and it returns nothing and jumps back to command line when you first start adb minimal for the first time.
I have tried this whilst forcing it to boot screen (power/volume down), same issue.
Perchy35 said:
I have installed the adb minimal 1.4.3 (Latest), just tried three different leads with the command fastboot devices and it returns nothing and jumps back to command line when you first start adb minimal for the first time.
I have tried this whilst forcing it to boot screen (power/volume down), same issue.
Click to expand...
Click to collapse
Sorry been at work and I'm ona break, I totally forgot though you can use Moto smart Assistant for pc to fix this more than likely, so download and useMoto smart Assistant
So I have bricked my phone for the 3rd time, the last 2 times I had to have someone with an authorized account fix it for me cost was 30EUR. Sucks. I have read every post on here and was just going to toss this thing in the trash after flashing and bricking it last night. This morning I came across a thread claiming if you used the SP Flash Tool with some other files that it would work, it didn't for me but in the process I found another thread talking about holding the volume down key while flashing, it did work. Here are the steps and how did I brick it, I flashed the files from MEGATHREAD so preloader was in place, I had working and install TWRP and was in the process of flashing vendor and PE ROM from TWRP. The zip was corrupted and it wiped me out and before rebooting I got the No OS installed message but figured I would to a clean flash of the OEM image from fastboot. Nope it failed and I got the LED light with nothing else, no boot no fastboot and no recovery. Dead. Here is what I did someone please try this.
I am on a Ubuntu box with ADB and Fastboot installed for the system I assume Windows or MAC would work just have those tools working and installed you must or you wouldn't have bricked your phone. I have begonia_global_images_V11.0.6.0.PGGMIXM_20200108.0000.00_9.0_global ROM and I went to the image directory, and typed:
Code:
fastboot devices
fastboot flash boot boot.img
When it was listed in fastboot devices I was like WHAT??? Sure enough it flashed it but do this right before you issue that command ITS IMPORTANT plug in the phone via USB and hold down the volume down key the phone will within a few seconds vibrate then hit the commands. Please see attached image you can see what I did. After that when I unplugged the phone it freaking booted into the OS and I had to set my phone up again but for the most part and this is weird my data was still intact, I don't care but it was nice. I really don't understand this phone at all but I hope others will try this and unbrick it would be awesome.
DC
dcindallas said:
So I have bricked my phone for the 3rd time, the last 2 times I had to have someone with an authorized account fix it for me cost was 30EUR. Sucks. I have read every post on here and was just going to toss this thing in the trash after flashing and bricking it last night. This morning I came across a thread claiming if you used the SP Flash Tool with some other files that it would work, it didn't for me but in the process I found another thread talking about holding the volume down key while flashing, it did work. Here are the steps and how did I brick it, I flashed the files from MEGATHREAD so preloader was in place, I had working and install TWRP and was in the process of flashing vendor and PE ROM from TWRP. The zip was corrupted and it wiped me out and before rebooting I got the No OS installed message but figured I would to a clean flash of the OEM image from fastboot. Nope it failed and I got the LED light with nothing else, no boot no fastboot and no recovery. Dead. Here is what I did someone please try this.
I am on a Ubuntu box with ADB and Fastboot installed for the system I assume Windows or MAC would work just have those tools working and installed you must or you wouldn't have bricked your phone. I have begonia_global_images_V11.0.6.0.PGGMIXM_20200108.0000.00_9.0_global ROM and I went to the image directory, and typed:
When it was listed in fastboot devices I was like WHAT??? Sure enough it flashed it but do this right before you issue that command ITS IMPORTANT plug in the phone via USB and hold down the volume down key the phone will within a few seconds vibrate then hit the commands. Please see attached image you can see what I did. After that when I unplugged the phone it freaking booted into the OS and I had to set my phone up again but for the most part and this is weird my data was still intact, I don't care but it was nice. I really don't understand this phone at all but I hope others will try this and unbrick it would be awesome.
DC
Click to expand...
Click to collapse
Thanks for sharing this. I've had a bricked rn8 pro for 3 weeks now and none of the other fixes worked for me. I'm looking forward to giving this a try when I get home from work. Perhaps I should've tried using my Kali box rather than windoze in my previous attempts.
I'll update with results if interested.
Hi, what exactly you did? Because I'm tired to test any possible method, I've tried disconnecting the battery, Press Volume - while try to flash, and now I'm waiting to prove the method that drain the battery adn then can connect and flash.
Did you flash with Ubuntu? It works? How can you do it If the phone can't enter to fastboot mode?
To what I understood you unlocked it 3 times and in one of those you updated the preloader?
Because if so. spflash unlocks it without asking for the happy account
Yup on Arch Linux and this worked fine
Melon_Bread said:
Yup on Arch Linux and this worked fine
Click to expand...
Click to collapse
What you did? Pls help ):
GERATKDASD said:
What you did? Pls help ):
Click to expand...
Click to collapse
Made sure the device was off completely, held down VOL-DOWN while pluging in phone and had it show up in my fastboot devices. Reflashed the system via fastboot with the begonia_global_images_V11.0.2.0.PGGMIXM_20191201.0000.00_9.0_global system image (flash-all.sh)
Melon_Bread said:
Made sure the device was off completely, held down VOL-DOWN while pluging in phone and had it show up in my fastboot devices. Reflashed the system via fastboot with the begonia_global_images_V11.0.2.0.PGGMIXM_20191201.0000.00_9.0_global system image (flash-all.sh)
Click to expand...
Click to collapse
I will try, thanks
Still not working ): IDK if I don't doing it right, I don't know, I'm tired of this phone ):
GERATKDASD said:
Hi, what exactly you did? Because I'm tired to test any possible method, I've tried disconnecting the battery, Press Volume - while try to flash, and now I'm waiting to prove the method that drain the battery adn then can connect and flash.
Did you flash with Ubuntu? It works? How can you do it If the phone can't enter to fastboot mode?
Click to expand...
Click to collapse
I already tested battery draining, doesnt worked :/
KonahZave said:
I already tested battery draining, doesnt worked :/
Click to expand...
Click to collapse
Holy cow, and then? now who can help us? ): I don't have 30 bucks right now ._.
Sed lyf
GERATKDASD said:
Holy cow, and then? now who can help us? ): I don't have 30 bucks right now ._.
Click to expand...
Click to collapse
I know how bad it is... Im sorry bro, if this guide couldnt help... then only paying. (╯︵╰,)
KonahZave said:
I know how bad it is... Im sorry bro, if this guide couldnt help... then only paying. (╯︵╰,)
Click to expand...
Click to collapse
You guys are NOT reading the method used, the battery isnt even removable on this phone follow the steps listed. You can't see anything happening on your phone just be at a terminal window HOLDING down the volume down key and type (oone handed or whatever) fastboot devices) it works I did it 3 times. Flash the boot.img and it will reboot and be fixed. I am tellng you FOLLOW instructions so many of you don't.
pablo159 said:
To what I understood you unlocked it 3 times and in one of those you updated the preloader?
Because if so. spflash unlocks it without asking for the happy account
Click to expand...
Click to collapse
None of that matters and no the preloader was over written, the point here is it was hard bricked only got the white LED light, then I did exactly what I wrote and it saw the phone in fastboot and it wrote the boot.img and then it rebooted and worked. Period. Worked for me. Someone else tested it worked for them. Try it but follow the directions....
dcindallas said:
You guys are NOT reading the method used, the battery isnt even removable on this phone follow the steps listed. You can't see anything happening on your phone just be at a terminal window HOLDING down the volume down key and type (oone handed or whatever) fastboot devices) it works I did it 3 times. Flash the boot.img and it will reboot and be fixed. I am tellng you FOLLOW instructions so many of you don't.
Click to expand...
Click to collapse
Man, Im not trying this method or such thing, Im not bricked. Im just telling for the dude my old experience with old guides.
dcindallas said:
You guys are NOT reading the method used, the battery isnt even removable on this phone follow the steps listed. You can't see anything happening on your phone just be at a terminal window HOLDING down the volume down key and type (oone handed or whatever) fastboot devices) it works I did it 3 times. Flash the boot.img and it will reboot and be fixed. I am tellng you FOLLOW instructions so many of you don't.
Click to expand...
Click to collapse
Sorry If I look like an annoying guy that don't understant, but litteraly i've tried that, I opened a Terminal window, typed fastboot devices, holding down volume -, but, IDK, how many time I need to press it;
I need to connect phone before hold the button, or vice versa?
GERATKDASD said:
Sorry If I look like an annoying guy that don't understant, but litteraly i've tried that, I opened a Terminal window, typed fastboot devices, holding down volume -, but, IDK, how many time I need to press it;
I need to connect phone before hold the button, or vice versa?
Click to expand...
Click to collapse
Plug the phone in and hold it down the phone will vibrate keep holding it down and try flashing it continue to hold it down until the flash is successful. All I had to do was flash the boot image but others have flashed_all. Hit me on telegram if you need help @dcindallas
dcindallas said:
Plug the phone in and hold it down the phone will vibrate keep holding it down and try flashing it continue to hold it down until the flash is successful. All I had to do was flash the boot image but others have flashed_all. Hit me on telegram if you need help @dcindallas
Click to expand...
Click to collapse
Ok, so, you only need to installed adb and fastboot right? no drivers or other things?