I have a rooted Sprint G2 and got the notification to update to KitKat, but when I did it restarted and said:
Code:
[15209250] -- reset --
[15209260] -- portcharge --
[15209320] fastboot: processing commands
[15367550] -- reset --
[15367550] EP1/out FAIL nfo=40 pg0=f913600
[15367560] -- reset --
[15367560] -- portcharge --
[15367570] usb_read() trasaction failed
[15367630] fastboot: oops!
[15372860] -- reset --
[15372870] -- portcharge --
And it does this every time I plug it into the computer. I also can't access download mode. I've looked through many tutorials but haven't found success with any of them yet. Am I at a point of no return or is there hope? Any help is greatly appreciated. Thanks!
try a different port on your computer then do (also make sure you have all the drivers installed on computer) (also make sure you have adb and fastboot installed
http://forum.xda-developers.com/showthread.php?t=2477595
(make sure you use sprint files though)
gpitner said:
I also can't access download mode.
Click to expand...
Click to collapse
This is his biggest issue
jcwxguy said:
try a different port on your computer then do (also make sure you have all the drivers installed on computer) (also make sure you have adb and fastboot installed
http://forum.xda-developers.com/showthread.php?t=2477595
(make sure you use sprint files though)
Click to expand...
Click to collapse
so this is useless if he can't even access Download mode to use the flashtool
OP can you access twrp? if you can you can flash this file http://www.rwilco12.com/Files/Garwynn%20Projects/LS980/ZVAtoZVC/ZVCRadio_Full.zip (Thank @garwynn for this if this works) and you should have download mode back if not then you are beyond my knowledge and will need help from a more knowledgeable person
No unfortunately I can't. The same, or very similar thing happened two weeks ago when I was trying to flash TWRP but after the phone ran out of battery and I plugged it back in, it turned on no problem. That didn't happen this time though, so I'm really stuck.
I thought I was bricked also and couldn't get into download mode. This is how I was able to use the flash tool. Vol down and power to get into recovery. You should get an error. Then power off the phone completely. Plug into usb to connect to computer. Then vol up and power for download mode. Make sure you have already installed the driver.
Hope this helps.
kleen3r said:
I thought I was bricked also and couldn't get into download mode. This is how I was able to use the flash tool. Vol down and power to get into recovery. You should get an error. Then power off the phone completely. Plug into usb to connect to computer. Then vol up and power for download mode. Make sure you have already installed the driver.
Hope this helps.
Click to expand...
Click to collapse
I just tried your method and it keeps going back to the same screen. I forgot to mention that I only get those lines of code when I plug my phone into the computer, but when my phone restarts the only code present is:
Code:
[470] Fastboot mode started
[520] udc_start()
Jbcarrera said:
This is his biggest issue
so this is useless if he can't even access Download mode to use the flashtool
Click to expand...
Click to collapse
the point of that thread is to flash the laf partition using fastboot, (which is download mode).
here is a laf.img
http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware/zv8_partitions/laf.img
(might also need to flash the boot.img
http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware/zv8_partitions/boot.img
*in cmd prompt, go to the folder where you have fastboot (copy both laf.img and boot.img to same folder), then do fastboot flash laf.img and fastboot flash boot.img.
( cd C:\Program Files (x86)\Minimal ADB and Fastboot ) (just an example)
once flashed, you should be able to get into download mode.
Ive had the exact screen you have had before, and this is what i had to do to get download mode to work.
gpitner said:
I just tried your method and it keeps going back to the same screen. I forgot to mention that I only get those lines of code when I plug my phone into the computer, but when my phone restarts the only code present is:
Code:
[470] Fastboot mode started
[520] udc_start()
Click to expand...
Click to collapse
I have to have Android SDK tools installed right?
Yes, you will need the SDK tools installed.
Just wanted to point out something real quick here, I see up a couple posts back, you pushed the power button for D/L mode but you do not hit the power button at all to get into D/L mode, you only need to hold VOL+ and plug the USB into the computer, this starts download mode. Once you get D/L mode back.
I had a very similar problem, when I flashed D801 rom on my LS980, I believe what I did was, to flash .boot as jcwxguy suggested but I think I also flashed .recovery both in fastboot mode with ADB and that brought back my D/L mode, here is a guide, http://forum.xda-developers.com/showthread.php?t=2131284 , go to FLASHING YOUR FILES IN FASTBOOT. best of luck!
So i flashed both files, thank you by the way, and they both flashed just fine but I still can't get into download mode. Here's the corresponding output on the phone and also what command prompt showed.
Code:
[5376060] fastboot: getvar:partition-type:laf
[5376180] fastboot: getvar:max-download-size
[5376440] fastboot: download:00f00000
[5376980] fastboot: flash:laf
[5377030] partition_get_size 33554432 bytes
[5416180] fastboot: getvar:partition-type:boot
[5416280] fastboot: getvar:max-download-size
[5416490] fastboot: download:00a00000
[5416870] fastboot: flash:boot
[5416930] partition_get_size 16777216 bytes
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
same procedure, flash the recovery partition, http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware/zv8_partitions/recovery.img
So I have myself a little conundrum. The phone's battery is dead so when it charges enough to turn on and install the update it dies halfway through the installation. Is there anyway to keep it from installing the update so it can charge enough?
Man, wish I could help out here but not sure about that one, maybe someone more knowledgeable out there knows a way out of this?
Nevermind, I was able to use a charger at my university that has a higher voltage output for quicker charging and it worked. My phone is fully functional. Thank you too everybody who helped and provided the appropriate files, you have no idea how happy I am!
cool, glad to hear you got it worked out. Congrats :good:
Related
Hello everyone! I have a big problem on my LG G3 D855.
I was updating my device for android L (5.0 20e) when I was updating the power went out in my house, and the computer and the phone is turned off, and since then, nothing happens to my G3 D855.
Now my device does not turn over, only appears the logo of LG and then gets a white letters with the following wording:
[510] fastboot mode started
[600] - reset -
[860] fastboot: processing comands
need some help, my device is new, has only 1 week of use, and I made that big bull****! Help me please. I'm desperate.
My device, the computer is recognized as:
ADB interface - Fastboot interface (USB Google ID)
Sorry for my bad english, I'm using Google translator!
http://forum.xda-developers.com/showthread.php?t=2785089
tarroyo said:
http://forum.xda-developers.com/showthread.php?t=2785089
Click to expand...
Click to collapse
does not work , as I already said , my device is stuck in fastboot mode, does not go into download mode
My pc hang while I was flashing a stock rom via LG Flashtool... everything was gone in the phone exept "Firmware Update/download mode". No matter which buttons I press during boot (up/down volume, power etc.) I was returned into this! I struggled with flashing using LG Flashtool with no sucess... somtimes I got error and it didn't even start, and sometimes it did start "flashing" but went VERY slow in the % and before it got anywhere near 100%, I got error and the process was aborted. I finally found info about Win8.1 beeing the source of the flashing problems and downgraded to Win7 and woah, flashing now went with speed and was sucessful. For a while there I totally thought my phone was dead...
Ehm... so you only get these white fastboot letters? Strange, you might be even deeper into the **** that I was xD
But I guess if fastboot work you could try to flash the needed files with fastboot flash commands... look here: http://forum.xda-developers.com/showpost.php?p=57296088&postcount=573
This was the only window I could get to when my phone was "half-dead":
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
schoolsux said:
My pc hang while I was flashing a stock rom via LG Flashtool... everything was gone in the phone exept "Firmware Update/download mode". No matter which buttons I press during boot (up/down volume, power etc.) I was returned into this! I struggled with flashing using LG Flashtool with no sucess... somtimes I got error and it didn't even start, and sometimes it did start "flashing" but went VERY slow in the % and before it got anywhere near 100%, I got error and the process was aborted. I finally found info about Win8.1 beeing the source of the flashing problems and downgraded to Win7 and woah, flashing now went with speed and was sucessful. For a while there I totally thought my phone was dead...
Ehm... so you only get these white fastboot letters? Strange, you might be even deeper into the **** that I was xD
But I guess if fastboot work you could try to flash the needed files with fastboot flash commands... look here: http://forum.xda-developers.com/showpost.php?p=57296088&postcount=573
This was the only window I could get to when my phone was "half-dead":
Click to expand...
Click to collapse
I wonder what the fastboot commands to play the laf.img and boot.img into the device
PabloHenrick said:
I wonder what the fastboot commands to play the laf.img and boot.img into the device
Click to expand...
Click to collapse
You can simply "fastboot boot iaf.img", then reflash .kdz with flashtool.
YaDr said:
You can simply "fastboot boot iaf.img", then reflash .kdz with flashtool.
Click to expand...
Click to collapse
Device NOT leaves the fastboot screen , and NOR goes into download mode , how do I '' Simply flash " fastboot boot iaf.img " then reflash .kdz with FlashTool .
PabloHenrick said:
Device NOT leaves the fastboot screen , and NOR goes into download mode , how do I '' Simply flash " fastboot boot iaf.img " then reflash .kdz with FlashTool .
Click to expand...
Click to collapse
Ummm.. You download iaf.img (There was a complete partition dump of G3 on this forum, use search) or extract it from .KDZ (tons of guides on that), you install adb (again, tons of guides and simple installers), you install LG drivers (and again, it's been discussed like million times over, just search for it...), you issue a "adb fastboot boot iaf.img" command from terminal. That's all, really. Then your phone goes into download mode, and you reflash stock .kdz from there.
YaDr said:
Ummm.. You download iaf.img (There was a complete partition dump of G3 on this forum, use search) or extract it from .KDZ (tons of guides on that), you install adb (again, tons of guides and simple installers), you install LG drivers (and again, it's been discussed like million times over, just search for it...), you issue a "adb fastboot boot iaf.img" command from terminal. That's all, really. Then your phone goes into download mode, and you reflash stock .kdz from there.
Click to expand...
Click to collapse
need to download the LAF.img or iaf.img and also the boot.img. I can not find! the one who found it, have a password, and I can not use the password they gave me, which is the LGViet.com always gives wrong password. you could make that up for me?
HAHAHA, Happy New Year!
While trying to root my redmi 1s, i accidentally pressed a wrong button due to which it seemed like if recovery is no longer functioning.
The mobile is getting struck at mi logo and is not proceeding forward.
Pressing volume down+power button successfully opens fastboot screen. Earlier when I was connecting it to mi suite on pc, i was able to flash. But due to incomplete charged battery, flashing procedure stopped. After the recent windows update, mi pc suite is recognizing the android but is not able to flash it. It pops out a dialogue box saying "cant flash the device". Any idea what can i do now?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
akshat2119 said:
While trying to root my redmi 1s, i accidentally pressed a wrong button due to which it seemed like if recovery is no longer functioning.
The mobile is getting struck at mi logo and is not proceeding forward.
Pressing volume down+power button successfully opens fastboot screen. Earlier when I was connecting it to mi suite on pc, i was able to flash. But due to incomplete charged battery, flashing procedure stopped. After the recent windows update, mi pc suite is recognizing the android but is not able to flash it. It pops out a dialogue box saying "cant flash the device". Any idea what can i do now?
Click to expand...
Click to collapse
If your phone boots into fastboot, then try installing twrp recovery and then flash the rom you wish.
vicky romero said:
If your phone boots into fastboot, then try installing twrp recovery and then flash the rom you wish.
Click to expand...
Click to collapse
but how to flash twrp via fastboot. i.e. which software would recognize fastbooting android?
akshat2119 said:
but how to flash twrp via fastboot. i.e. which software would recognize fastbooting android?
Click to expand...
Click to collapse
Flashing twrp is done by fastboot using adb tools. First install the USB drivers of your phone. You can simply google them. Then go to this link https://drive.google.com/open?id=0B_43Fi9T_yqvUy1jOWk0cnJyZEk
and download the four files in the adb folder. Now download the latest twrp image i.e, twrp 3.0.0-0 from this link
https://dl.twrp.me/armani/
keep the adb tools i.e, the four files you had downloaded and the twrp image in the same folder. Rename the twrp 3.0.0-0 to recovery.img. Now hold shift key and press right click on your mouse. From there select open command window here. Now open fastboot and connect your phone through Usb and type this code
Code:
fastboot devices
This is to check wheather your device is connected or not. If it's connected then it will show some code. After that type this code
Code:
fastboot flash recovery recovery.img
That's it twrp will be flashed right away. Then you can flash MIUI or any other custom rom.
Thank you
vicky romero said:
Flashing twrp is done by fastboot using adb tools. First install the USB drivers of your phone. You can simply google them. Then go to this link https://drive.google.com/open?id=0B_43Fi9T_yqvUy1jOWk0cnJyZEk
and download the four files in the adb folder. Now download the latest twrp image i.e, twrp 3.0.0-0 from this link
https://dl.twrp.me/armani/
keep the adb tools i.e, the four files you had downloaded and the twrp image in the same folder. Rename the twrp 3.0.0-0 to recovery.img. Now hold shift key and press right click on your mouse. From there select open command window here. Now open fastboot and connect your phone through Usb and type this code
Code:
fastboot devices
This is to check wheather your device is connected or not. If it's connected then it will show some code. After that type this code
Code:
fastboot flash recovery recovery.img
That's it twrp will be flashed right away. Then you can flash MIUI or any other custom rom.
Click to expand...
Click to collapse
A big thank you. I owe you for helping out. By the way after installing recovery I tried downloading rom(both armani which was earlier working and miui official). The script gets sideloaded successfully but again the operating system is not loading. ie mobile is still struck in bootloader
akshat2119 said:
A big thank you. I owe you for helping out. By the way after installing recovery I tried downloading rom(both armani which was earlier working and miui official). The script gets sideloaded successfully but again the operating system is not loading. ie mobile is still struck in bootloader
Click to expand...
Click to collapse
Flash this firmware before installing the rom. It'll fix the bootloops.
https://www.androidfilehost.com/?fid=24052804347850305
Thanks @fefifofum for this flashable zip.
Does anyone have the MSMTOOL for LE2120? bricked my phone when trying to patch the boot.img to magisk version...
Now totally stuck... even adb commands to restore does not work...
danjcxie said:
Does anyone have the MSMTOOL for LE2120? bricked my phone when trying to patch the boot.img to magisk version...
Now totally stuck... even adb commands to restore does not work...
Click to expand...
Click to collapse
What did you do to try to patch it? Why are you in adb? Does fastboot work?
craznazn said:
What did you do to try to patch it? Why are you in adb? Does fastboot work?
Click to expand...
Click to collapse
Patched the boot.img using magisk and then flashed it. After patching, it totally cant boot and can only boot to bootloader.
tried alot of version of MSMtool and it will always fail with param preload error...
Then tried manually recover via extracting the payload using python then using adbtools to wipe and flash but it will also fail because some img files are unable to flash over to the phone...
Any other solutions?
U not able to flash boot the stock boot.img?
i am able to flash the stock boot.img to the phone but some critical img files will come out with
FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
You need to be in fastbootd,
Code:
fastboot reboot fastboot
craznazn said:
You need to be in fastbootd,
Code:
fastboot reboot fastbootd
Click to expand...
Click to collapse
Nope not working too...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
danjcxie said:
Nope not working too...
View attachment 5281163
Click to expand...
Click to collapse
Sorry, fastboot reboot fastboot (without the d)
@danjcxie
To be honest, I would download the rom and boot with the recovery image instead, I'll upload the image collection...
Will post a link here once it's up.
Actually, just noticed there isn't a recovery image, so boot to the default boot.img using fastboot, then see if the storage shows on your computer, copy the latest default rom over to the main storage folder then then go into Settings > System > System Updates and use the cog to do a local update using the rom zip.
That should re-install everything back to default, you might get lucky and still have all your data
My collection is for the Europe build FYI:
OP9P_Image_Collection_BA_11.2.3.3.zip | by djsubterrain for OnePlus 9 Pro
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
MD5 : 00227014483b4913a2624fac6f492434
So you would reboot the phone into fastboot mode by holding vol up during boot
Once you are in fastboot mode connect the phone to your computer
Test that the computer can see it properly using fastboot devices
You should see a number returned, if so then your computer is recognising the phone, if you don't then try installing the latest drivers from here
If fastboot can see the device properly then copy the default boot.img to the same folder as your fastboot.exe and type the following :
fastboot boot boot.img
You should see a message saying it's transferring it to the phone, then it should boot the phone using it, it's slower than a normal boot but, if everything else on the phone is ok, then you should see it booted and it should accept your lock method
Once you get into the phone using that boot.img, try connecting the phone to your computer and see if it's recognised, if it is then copy over the latest stock rom to your main storage folder, then go to Settings > System > System Updates and use the cog to do a local update using the rom zip
I'm guessing it should let you because it will see a difference between your boot image and the one from the rom.
MSM tool for LE2125 - 11.2.2.2.LE15AA
User Type of Others for login MSM Tool for LE2125 - 11.2.2.2.LE15AA Drivers Mirrors: (provided by @djsubterrain) MSM Tool : https://sourceforge.net/projects/djsubterrain/files/OnePlus 9 Pro/OP9P_MSM_Tool.zip/download MD5 ...
forum.xda-developers.com
New problem... After i did fastboot reboot fastboot, it shows low battery whole day and is unable to charge totally... it has been charging the whole day now and totally cant turn on at all.
it keeps showing the lightning sign in the centre of the circle keeps blinking and dies off
danjcxie said:
New problem... After i did fastboot reboot fastboot, it shows low battery whole day and is unable to charge totally... it has been charging the whole day now and totally cant turn on at all.
it keeps showing the lightning sign in the centre of the circle keeps blinking and dies off
View attachment 5281971
Click to expand...
Click to collapse
Turn it off and try charging it
Also "fastboot reboot fastboot" isn't a valid command, there is an adb command "adb reboot bootloader" but that can only be run from within your rom from when you are in recovery with the phone connected
See here :
Fastboot Commands: A Beginner’s Guide
With this guide of ours, you'll be able to learn all the fastboot commands and their syntax. We've also posted some hidden commands which you never knew.
android.tutorials.how
#To reboot your device
fastboot reboot
#To reboot your device to fastboot mode
fastboot reboot-bootloader
Click to expand...
Click to collapse
djsubterrain said:
Turn it off and try charging it
Click to expand...
Click to collapse
Yup tried. Everytime you just plug in the charging cable, it will just auto boot up and show the charging sign
danjcxie said:
Yup tried. Everytime you just plug in the charging cable, it will just auto boot up and show the charging sign
Click to expand...
Click to collapse
Yeah that symbol isn't what I get, I get a blue lightning sign with the percentage underneath. Are you running OxygenOS or ColorOS?
I think it might be time for you to contact OnePlus support
djsubterrain said:
Turn it off and try charging it
Also "fastboot reboot fastboot" isn't a valid command, there is an adb command "adb reboot bootloader" but that can only be run from within your rom from when you are in recovery with the phone connected
See here :
Fastboot Commands: A Beginner’s Guide
With this guide of ours, you'll be able to learn all the fastboot commands and their syntax. We've also posted some hidden commands which you never knew.
android.tutorials.how
Click to expand...
Click to collapse
Wtf are you talking about. fastboot reboot fastboot is literally the only way to get into fastbootd if you can't get to recovery or boot normally.
Regarding battery, that I'm not sure, hopefully someone can help
craznazn said:
OP
Wtf are you talking about. fastboot reboot fastboot is literally the only way to get into fastbootd if you can't get to recovery or boot normally.
Regarding battery, that I'm not sure, hopefully someone can help
Click to expand...
Click to collapse
OK, firstly, who the hell do you think you're talking to?
Secondly, did you look at the link I posted?
djsubterrain said:
OK, firstly, who the hell do you think you're talking to?
Secondly, did you look at the link I posted?
Click to expand...
Click to collapse
Who the hell are you? Why the hell are you linking "tutorials.how"?
fastboot/fastboot.cpp - platform/system/core - Git at Google
android.googlesource.com
Lines 2178, source tells you to reboot fastbootd by reboot fastboot.
Show me it's not a valid command, go on
craznazn said:
Who the hell are you? Why the hell are you linking "tutorials.how"?
fastboot/fastboot.cpp - platform/system/core - Git at Google
android.googlesource.com
Lines 2178, source tells you to reboot fastbootd by reboot fastboot.
Show me it's not a valid command, go on
Click to expand...
Click to collapse
Go ahead and help the guy solve his problem.
Just remember it's fastboot, not fastbootd.
Now, how do you block people on here again?
danjcxie said:
Does anyone have the MSMTOOL for LE2120? bricked my phone when trying to patch the boot.img to magisk version...
Now totally stuck... even adb commands to restore does not work...
Click to expand...
Click to collapse
use the MSM Tool with the latest drivers
QDLoader HS-USB Driver_64bit_Setup
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
danjcxie said:
Does anyone have the MSMTOOL for LE2120? bricked my phone when trying to patch the boot.img to magisk version...
Now totally stuck... even adb commands to restore does not work...
Click to expand...
Click to collapse
This just worked for me minutes ago
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com
i downloaded Indian Variant LE2121 while my phone is LE2120 ant it worked
Hi all, forgot to charge my HTC 10 last night and it went dead. I always take care of my battery this is the first time I have had this happen. I even run battery limiter and max 80% charge the phone. Anyways so I charged it for 10 minutes or so and tried to boot and was just stuck in bootloop. If I keep the phone charging it just keeps restarting and not getting past the HTC logo and red letters. If I hold down both volume buttons I can get the white menu that shows reboot, reboot to bootloader, download mode, recovery mode ddr test, ddr test looping, power down.
My phone is rooted and I had TWRP on there, If I pick any option from above on the white screen back to bootloop. No clue what happened. I also noticed that one the white screen it says software status official not sure if that was like that before.
I tried connected to the PC, and while I hear the windows 10 ding, when I run adb and check for devices I get nothing.
I also tried holding down all 3 buttons to reset the battery, all that I get is rebooting multiple times every 15 seconds or so. When I plug my charge cord in (also used another one just in case), the orange charge light does not come on either.
Any thoughts or ideas would be much appreciated.
Fastboot works ? If yes then you can at least backup or even flash another rom
So I was able to connect the phone to the pc and I tried to flash the stock oreo .ruu and I am getting a less then 30% battery message. I can't believe the battery on the phone just fully died out of the blue like this. I haven't had any battery issues at all. Going to put in a new battery this weekend.
So I spent about 3hr putting a new battery into the phone, what a nightmare. Booted up same issue boot loop. When hooking up to the PC to try and flash the ruu I am getting the less then 30% message.
Anyone have any idea or other solution to try and get this phone working again?
Hmmm seems like hardware failure.
TWRP hardly works, android does not boot, phone does not charge, as the worst case, it seems your EMMC storage chip is sadly, broken.
Have you tried clicking 'flash' in twrp? Will it crash? If clicking 'flash' works please send me the size of 'internal storage', and if it is 0, say goodbye to your phone.
LR7875 said:
Hmmm seems like hardware failure.
TWRP hardly works, android does not boot, phone does not charge, as the worst case, it seems your EMMC storage chip is sadly, broken.
Have you tried clicking 'flash' in twrp? Will it crash? If clicking 'flash' works please send me the size of 'internal storage', and if it is 0, say goodbye to your phone.
Click to expand...
Click to collapse
My phone is S-off (via sunshine) and unlocked. I had TWRP 3.2 something ircc. But I cant' get into twrp. I am going to try to flash the stock image via the zip file on sd method and report back.
Well that didn't work. Is it common for the EMMC storage chip to go bad on these phones? I have taken such good care of this thing too.
cloves said:
Well that didn't work. Is it common for the EMMC storage chip to go bad on these phones? I have taken such good care of this thing too.
Click to expand...
Click to collapse
IDK about HTC, but as far as I know, tens, if not hundreds or thousands, of galaxy S3 phones, had their EMMC dead and no one say they were abused. So EMMC dying on a phone is extremely rare, but not impossible.
Have you tried EDL (emergency download mode)?
And can you send me what failed when flashing update.zip?
Hi LR, never heard of EDL for HTC phones, interesting. So via adb I was able to at least get something going. I can see the phone if ID if I type fastboot devices. I was roughly following this xda link
Then I took the .img files from 3.16.617.2_FULL-WIPE_firmware folder I downloaded and put them into my adb folder, and I was able to at least flash two things. Using the fastboot command in adb I used "fastboot flash boot boot_signed.img" and got OKAY also got OKAY from "fastboot flash recovery recovery_signed.img"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Still bootlooping. Only screen I have access to is that white screen mentioned earlier.
What if you flash TWRP as recovery and fastboot reboot recovery?
Thanks for the suggestion. I am going to have to read up on that this week. With twrp ircc I have to get it on zip and then put on the sd card and then try to flash via cmd correct? I originally had twrp on my phone before it stopped working.
cloves said:
Thanks for the suggestion. I am going to have to read up on that this week. With twrp ircc I have to get it on zip and then put on the sd card and then try to flash via cmd correct? I originally had twrp on my phone before it stopped working.
Click to expand...
Click to collapse
you mean adb sideload?
Hi LR, so I did somewhere work this weekend combing the forums. One option I came across since I have fastboot commands working is to use fastboot to flash the RUU but I can't make it work.
Thread location: At the end of the thread its not very clear, seemed it worked for at least one person
I can't access to Download Mode, I can't flash RUU, Don't Charge, Brick Phone
Hey Guys, I did a factory reset and the phone went don't: I can't access to Download Mode. It doesn't charge I Can't flash RUU (Because I can't access to the download mode) I Can't access to the recovery. It is stuck in this white...
forum.xda-developers.com
I was able to run the following commands successfully "fastboot getvar all" and could see basic phone info.
Then ran "fastboot flash recovery twrp-3.2.1-3_CPTB-20180307-01-pme.img"
that worked:
Sending 'recovery' (56384 KB) OKAY [ 1.489s]
Writing 'recovery' OKAY [ 0.850s]
Thread mentions this:
RUU_Decrypt_Tool RUU.zip
fastboot reboot-bootloader
fastboot flash hosd hosd_signed.img from Decrypt Folder
I downloaded the tool and decrypted the RUU. I was able to flash "fastboot flash hosd hosd_signed.img"
after that in the fastboot white menu I clicked down to reboot into recovery and still bootloop.
Seems this is a common issue on these phones if the battery is run down to zero. XDA search function leaves a lot to be desired. Most of my finds have been via google and still none of the finds have final results
I had installed in this phone a custom rom a few months back for my friend. Yesterday he told me that the device froze when he was browsing the phone gallery app, and a few minutes later the phone rebooted and couldn't pass the mi logo (so the system wasn't loading I guessed, because the logo of the ROM wasn't showing). I tried to enter TWRP, but even there the phone would get stuck on the TWRP splash page and rebooted back to the MI logo. So I tried to reinstall TWRP (I have still access to fastboot mode) and, after, a newer version, but the problem was the same. I tried booting a recovery image without installing it (fastboot boot twrp.img) and the problem was similar, but instead of rebooting to the MI logo, the phone would get stuck on the TWRP logo. I tried with OrangeFox recovery too, but same problem. I read in another post that it may be a problem with the /data partition, so I (fastboot erase userdata) and tried again the above recovery installation, but it didn't work. I, then, tried to wipe all partion via fastboot, and tried the command "fastboot erase system -w", but it didn't work either. So I tried the way to restore the phone with MiFlash tool, I found the firmware I needed, I flashed it, and after ~4s it gave me the error "failed to write partiton" (see image).
Spoiler: Image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried with another firmware (this time based on Oreo instead of Nougat), same error. I searched a solution for this error, but I found nothing helpful. Now I have the phone working (=it can power on) and can access to fastboot, but don't know what to do. Can someone out there, with maybe a clearer idea of what's going on, help me? Thanks in advance
Update:
I found out that the problem is flashing this file "gpt_both0.bin" (which is the partition table). Every firmware that I tried failed to flash when trying to fastboot this file. So I tried to remove the line (
Code:
fastboot %* flash partition "%~dp0images\gpt_both0.bin" || @echo "Flash tz error" && exit /B 1
) from the flash_all.bat and everything was flashed without errors, but the phone won't start, so this file is necessary. Flashing it separately gave me the same error (failed to write partition). So, I ask again for help, hoping that someone will come to save me
I have same issue. Did you get any working method?
amitkr.xda said:
I have same issue. Did you get any working method?
Click to expand...
Click to collapse
No, I'm still getting the error and trying to test all that comes to my mind. Maybe one day something will work
TheMagicWafer said:
No, I'm still getting the error and trying to test all that comes to my mind. Maybe one day something will work
Click to expand...
Click to collapse
Does your phone go in fastboot? Mine doesn't, but is recognised as QHSBULK 9008, also it's not recognised in adb devices or mi tool
amitkr.xda said:
Does your phone go in fastboot? Mine doesn't, but is recognised as QHSBULK 9008, also it's not recognised in adb devices or mi tool
Click to expand...
Click to collapse
Yes, my phone goes into fastboot. The name QHSBULK 9008 sounds like the phone goes in edl mode. I'm not sure, but searching around I found out it's the name of the phone when it's recognised as by it's qualcomm drivers, or something similar
TheMagicWafer said:
Yes, my phone goes into fastboot. The name QHSBULK 9008 sounds like the phone goes in edl mode. I'm not sure, but searching around I found out it's the name of the phone when it's recognised as by it's qualcomm drivers, or something similar
Click to expand...
Click to collapse
How can I boot in fastboot? It's not going in fastboot or anything
amitkr.xda said:
How can I boot in fastboot? It's not going in fastboot or anything
Click to expand...
Click to collapse
Only (hardware) method possible is to hold the power button and the volume down(-) button simultaneously and wait for the fastboot screen/logo
TheMagicWafer said:
Only (hardware) method possible is to hold the power button and the volume down(-) button simultaneously and wait for the fastboot screen/logo
Click to expand...
Click to collapse
Nothing works, it's just blank screen, no vibrate, no logo nothing
amitkr.xda said:
Nothing works, it's just blank screen, no vibrate, no logo nothing
Click to expand...
Click to collapse
I'm sorry, but I'm not an expert and I can't help you any further. If one day I find a solution, be sure I'm going to write it here
have u try Miui Nougat Global with clean all and lock option? if yes, looks like your emmc has died
Avisadius said:
have u try Miui Nougat Global with clean all and lock option? if yes, looks like your emmc has died
Click to expand...
Click to collapse
Already tried, and it gave me the same error. I really hope it's not a motherboard issue, because a replacement is not worth it. Thanks anyway