Database Info

[Q] Is it bricked or hardware?

Hey.
So i bought a tf101 and it was never rooted before if you believe the previous owner. I used easyflasher to install, then installed cm10.
So yesterday i was going to bed, open the tablet and boff. Just died.
I could enter the APX mode (i saw it popped up when i connected it to the computer) but nothing else. So since it was late i thought i'l do the unbrick with easyflasher today.
Now i can't even enter APX mode.
So how do i know if it's bricked or hardware issues? Cause i've got ½ year of guarantee left on it.
EDIT: I can now enter APX mode for some reason, tried the unbrick on easyflash. Im using the WW SKU version. The easyflasher seems to have trouble cause the "wheele.exe" get's closed everytime after it uploaded the bootloader to 100%. But the installation still says it's done and no other errors shows up. But still not able to boot anything on the device.

One way to know if it's "dead" or not is this:
- Power off the device completely (hold the power button for 5 seconds and make sure it's not detected in your computer)
- Make sure ADB is installed (download)
- Run "adb logcat" (without the quotes - see this for more details)
- Boot the device
ADB should say something like "waiting for device..." when you run logcat, and when you boot up you should start seeing the booting process in ADB. If it boots (basically adb will just print stuff forever), then you can probably start suspecting hardware, like the screen for instance. If it stalls during boot, let us know where and what's the error message; it could be corruption somewhere or something alike. If you get nothing at all then I would suspect hardware failure of some sort that's more serious than the screen. If you want to bypass the screen as possible culprit, plug it into HDMI, however you may not get any signal until it's fully booted.
Edit: What's your exact model?

Lethe6 said:
One way to know if it's "dead" or not is this:
- Power off the device completely (hold the power button for 5 seconds and make sure it's not detected in your computer)
- Make sure ADB is installed (download)
- Run "adb logcat" (without the quotes - see this for more details)
- Boot the device
ADB should say something like "waiting for device..." when you run logcat, and when you boot up you should start seeing the booting process in ADB. If it boots (basically adb will just print stuff forever), then you can probably start suspecting hardware, like the screen for instance. If it stalls during boot, let us know where and what's the error message; it could be corruption somewhere or something alike. If you get nothing at all then I would suspect hardware failure of some sort that's more serious than the screen. If you want to bypass the screen as possible culprit, plug it into HDMI, however you may not get any signal until it's fully booted.
Edit: What's your exact model?
Click to expand...
Click to collapse
This is just wierd. Now it will boot, but only if it's in the charger... When i plug it out it dies. The battery says 76% and haven't moved so the battery seems dead?
And i've got the b50.
This is how it looks when i use easyflasher when it's on APX mode (as it was when i flashed recovery with easyflash). But when i boot up the tablet with charger it's still cw10.
{
"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"
}

Are you using the APX drivers suggested in the Easy Flasher post? If wheelie closes chances are it's not doing anything to your device at all, which would explain why you still boot CM10. For problems with EF I suggest posting in their thread, I never really had issues so I can't troubleshoot the issue further.
If you're using the drivers maybe there's a hardware related issue, like the internal SD for instance. I've seen some posts here where people have to keep it plugged to USB but I haven't followed them, you can probably find them through a search of this section.

Lethe6 said:
Are you using the APX drivers suggested in the Easy Flasher post? If wheelie closes chances are it's not doing anything to your device at all, which would explain why you still boot CM10. For problems with EF I suggest posting in their thread, I never really had issues so I can't troubleshoot the issue further.
If you're using the drivers maybe there's a hardware related issue, like the internal SD for instance. I've seen some posts here where people have to keep it plugged to USB but I haven't followed them, you can probably find them through a search of this section.
Click to expand...
Click to collapse
I've installed the drivers as wanted by EF. I can browse the internal SD without any problems so i'm not sure about that. Anyway to test that?
I think im gonna download some other rom right to the tablet and try install it. Otherwise i have to go and buy a sd-card thingy for the computer so i can try install stock rom that way i guess.
edIt: Installed Team EOS 4 *JELLYBEAN MR1* but diden't make any diffrence. Now i just need to try get stock and un-root so i can send it to asus :/

So i kinda got it to work out. I think.
I could keep the tablet alive after a while using the keyboard dock after having it being charged for about 10 min. So i had do unistall the "normal" drivers which i could not accsess before and then i worked to make normal rom with easyflash.
But question is:
Is the WW SKU right one for me (im from sweden.)?
Does the recovery go back to orignal also? When i tried to accses recovery all i got was the android green guy who had something wrong with his stomach. Means im back to orginial recovery?
Cause im gonna go back to the store as warranty issue, but i'd like to make it looked as much as possible that it was never rooted or had diffrent roms the the orgiinal.

Yup the WW firmware is the one for non-US non-Asian and will bring recovery back to stock. You now have a 100% stock device unless you re-rooted it.

Lethe6 said:
Yup the WW firmware is the one for non-US non-Asian and will bring recovery back to stock. You now have a 100% stock device unless you re-rooted it.
Click to expand...
Click to collapse
I downloaded some "check if rooted" app an it says it was not properly rooted which i guess means there is no root existing. Ty for your help man, been awsome. Just hope i won't get charged by asus somehow

Yeah hope so too! Let us know how it ends up going

Worse comes to worse, use PERI http://forum.xda-developers.com/showthread.php?t=1681155
Sent from my Transformer using Tapatalk HD

Lethe6 said:
Yeah hope so too! Let us know how it ends up going
Click to expand...
Click to collapse
So, just wanna update the thread.
The battery was dead so switched it myself after buying one for 50-60 dollars on ebay. Was quite easy, only painful part was putting on the thing around the screen with the power button etc so it would work.

Sweet, glad you got it fixed

[Q] XT926 Stuck on Bootloader/Eye

Hey guys, my phone is stuck on the Droid BL with the eye thing on it. I tried to post a picture, but since this is a new account it won't let me. The phone is completely stock, no CWM, no root, no ANYTHING. I know I can factory reset it to try and make it work again, but I need the pictures from it for the previous owner. Is there any way to recover anything, or will I have to wipe to stock to have it work again?

ExPwN said:
Hey guys, my phone is stuck on the Droid BL with the eye thing on it. I tried to post a picture, but since this is a new account it won't let me. The phone is completely stock, no CWM, no root, no ANYTHING. I know I can factory reset it to try and make it work again, but I need the pictures from it for the previous owner. Is there any way to recover anything, or will I have to wipe to stock to have it work again?
Click to expand...
Click to collapse
power + vol up and down
then go to recovery
then vol up and down and select factory reset

billycar11 said:
power + vol up and down
then go to recovery
then vol up and down and select factory reset
Click to expand...
Click to collapse
Obviously you didn't read my post. I KNOW I can do that, but I need the pictures for the previous owner. I'm not an idiot.

okay when booting hold both volume + and - that should get you in safe mode you can tell by the watermark on the bottom.
{
"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"
}
also if this does work you can sbf with rsd lite and delete the part of the script that says user data and get var this will keep all the data on the phone and only re flash the system

billycar11 said:
okay when booting hold both volume + and - that should get you in safe mode you can tell by the watermark on the bottom.
View attachment 2744200
also if this does work you can sbf with rsd lite and delete the part of the script that says user data and get var this will keep all the data on the phone and only re flash the system
Click to expand...
Click to collapse
Thanks, I'll try it when I get home

billycar11 said:
okay when booting hold both volume + and - that should get you in safe mode you can tell by the watermark on the bottom.
View attachment 2744200
also if this does work you can sbf with rsd lite and delete the part of the script that says user data and get var this will keep all the data on the phone and only re flash the system
Click to expand...
Click to collapse
Ok so I'm not sure when I hold the buttons. If I hold all three while booting it takes me to the boot mode selection menu. Also, what is sbf and rsd lite? I've never done anything with this phone before.

ExPwN said:
Ok so I'm not sure when I hold the buttons. If I hold all three while booting it takes me to the boot mode selection menu. Also, what is sbf and rsd lite? I've never done anything with this phone before.
Click to expand...
Click to collapse
http://www.talkandroid.com/guides/beginner/how-to-boot-your-android-phone-or-tablet-into-safe-mode-for-troubleshooting/
You don't push all three just the volume up and down buttons

billycar11 said:
http://www.talkandroid.com/guides/beginner/how-to-boot-your-android-phone-or-tablet-into-safe-mode-for-troubleshooting/
You don't push all three just the volume up and down buttons
Click to expand...
Click to collapse
It didn't work. Still stuck on the eye. I guess I'll tell her they're gone unless there's something else I can try?

ExPwN said:
It didn't work. Still stuck on the eye. I guess I'll tell her they're gone unless there's something else I can try?
Click to expand...
Click to collapse
i may be able to help, i have a couple questions.
-do you know how it got stuck like this? any details may be helpful
-if i give you a modified one click script to use, do you know how to put the phone into fastboot and have the moto drivers setup on your pc to use it?
sorry if thats a dumb question, but this will go faster if i know what you know.

bweN diorD said:
i may be able to help, i have a couple questions.
-do you know how it got stuck like this? any details may be helpful
-if i give you a modified one click script to use, do you know how to put the phone into fastboot and have the moto drivers setup on your pc to use it?
sorry if thats a dumb question, but this will go faster if i know what you know.
Click to expand...
Click to collapse
She said that it just rebooted itself while she was on an app one day, and it was fine for a day, then it died and it wouldn't boot back up. She said she got it to boot ONCE (WHY THE **** DIDN'T SHE BACK IT UP THEN) and then she rebooted and it wouldn't start.
Yes I know how to do FB and I do have the moto drivers already.

ExPwN said:
She said that it just rebooted itself while she was on an app one day, and it was fine for a day, then it died and it wouldn't boot back up. She said she got it to boot ONCE (WHY THE **** DIDN'T SHE BACK IT UP THEN) and then she rebooted and it wouldn't start.
Yes I know how to do FB and I do have the moto drivers already.
Click to expand...
Click to collapse
ok, im uploading the file, it will be about an hour.
its not guaranteed to work but i think it will. i removed the wiping commands so it should reflash everything stock but not touch the data partition, again not guaranteed but i removed the commands.
ill post back when its done.

bweN diorD said:
ok, im uploading the file, it will be about an hour.
its not guaranteed to work but i think it will. i removed the wiping commands so it should reflash everything stock but not touch the data partition, again not guaranteed but i removed the commands.
ill post back when its done.
Click to expand...
Click to collapse
So what am I doing, flashing a modified firmware?

ExPwN said:
So what am I doing, flashing a modified firmware?
Click to expand...
Click to collapse
no, its 100% stock. its just going to re-flash the key partitions and should not touch data which is a different partition. im hoping you just have a corrupt file that will be replaced by the re-flash.
if this doesnt work, i have one more idea to use rsd, but i will have to give you another modified file.
im optimistic the utility will work though and we wont have to try rsd.

bweN diorD said:
no, its 100% stock. its just going to re-flash the key partitions and should not touch data which is a different partition. im hoping you just have a corrupt file that will be replaced by the re-flash.
if this doesnt work, i have one more idea to use rsd, but i will have to give you another modified file.
im optimistic the utility will work though and we wont have to try rsd.
Click to expand...
Click to collapse
So what do I use to flash this firmware? Odin or something else?

ExPwN said:
So what do I use to flash this firmware? Odin or something else?
Click to expand...
Click to collapse
no, its a 1 click utility. you just put the phone into ap fastboot, connect to your pc, then open the utility and follow the instructions. its very simple. i removed everything from the utility except the option you need.

bweN diorD said:
no, its a 1 click utility. you just put the phone into ap fastboot, connect to your pc, then open the utility and follow the instructions. its very simple. i removed everything from the utility except the option you need.
Click to expand...
Click to collapse
Sweet, thanks!

ExPwN said:
Sweet, thanks!
Click to expand...
Click to collapse
ok mediafire is not playing nice today and restarted my upload.
lets do this another way.
download this file http://www.mediafire.com/view/vda0q55kocydsci/WindowsUtility.bat
then download this one http://www.mediafire.com/download/ucae9ljgfpda2jc/DROID_RAZR_HD_Utility_1.34.rar
extract the second file to your desktop (its already in a folder), inside near the bottom is a "windows utility" file, delete it then copy the first file i posted in its place.
next follow the instructions in my other post to flash then double click the windowsutility file to start the utility and follow the instructions.

bweN diorD said:
ok mediafire is not playing nice today and restarted my upload.
lets do this another way.
download this file http://www.mediafire.com/view/vda0q55kocydsci/WindowsUtility.bat
then download this one http://www.mediafire.com/download/ucae9ljgfpda2jc/DROID_RAZR_HD_Utility_1.34.rar
extract the second file to your desktop (its already in a folder), inside near the bottom is a "windows utility" file, delete it then copy the first file i posted in its place.
next follow the instructions in my other post to flash then double click the windowsutility file to start the utility and follow the instructions.
Click to expand...
Click to collapse
It just says waiting on device

ExPwN said:
It just says waiting on device
Click to expand...
Click to collapse
hmm, thats not good
your on the fastboot screen? phone should have a bunch of text including "device is locked, status code(some number)" should also say on the phone "usb-connected" etc etc
latest moto drivers?
try a different usb port, usb 2 port not 3
try a different usb cable
one of those items is usually the problem

bweN diorD said:
hmm, thats not good
your on the fastboot screen? phone should have a bunch of text including "device is locked, status code(some number)" should also say on the phone "usb-connected" etc etc
latest moto drivers?
try a different usb port, usb 2 port not 3
try a different usb cable
one of those items is usually the problem
Click to expand...
Click to collapse
I used a different cable. The one I was using was charge only for some reason. I'm waiting for it to finish now

Idol 3- Stuck In Bootloop After Flashing boot.img

Idol 3 Bootloop
I need your assistance
Hi, I have read through all of the posts and tried to find a solution with no luck.
I tend to always go one step too far with my hacking and playing/experimenting.
Alcatel One Touch Idol 3 5.5 6045K
It was booting into TWRP fine.
Then I wrote the non-functioning boot.img (which I thought was the backup of my pre-rooting version) on top of the working twrp recovery image.
So instead of installing the boot.img to the boot partition, I installed it to the recovery partition by mistake.
So now...
My phone just keeps booting and booting.
Alcatel Screen appears
The SuperSU installer starts
runs through its steps
Done!
Cleaning Up....
Will reboot in 10 seconds....
And starts all over again.
adb does not find any devices anymore
I am wondering if it possible at all to format the external sd card so that the phone will boot directly from there.
I have one single ray of hope ( maybe ) . The phone will boot into download mode. (Power off, hole power, volume up and volume down to activate)
The challenge I have now is the USB driver that was working now does not recognize the phone.
I have tried fastboot and I have also tried the OnDemand script. No luck.
I read that the download mode is used for flashing firmware and roms (most likely by the manufacturer)
Has anyone been able to install a rom using the download method successfully?
I am on Windows 10 All-in-One PC
Thanks in advance for any assistance you can provide.
N101BL

More Info
No ideas anyone?
Here is some more info. Hopefully it helps.
So this is what my screen looks like when the phone is turned on. I can only turn it off if it is not plugged in to usb or power.
{
"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"
}
This is the Download Mode. (Power off - then hold power button, volume up, and volume down. Let go when splash screen starts)
Download mode makes a connection sound on my PC so I know something is being recognized.
The phone stops bootloop and waits for something?
This is what appears in Devices and Printers Windows
These are the USB Properties for the USB Driver.
I am thinking that maybe there is a secret usb driver that Telus uses or Alcatel uses to push the firmware or rom onto the phone. Not just the default Alcatel usb driver. (not sure)
Even if I could somehow push a ne SuperSu.zip or my original backup files, everything would be good.
Any ideas would be amazing. I know the trials and tribulations of working with a new product. Hopefully you experts can decode this one.
Thank you.
N101BL (Kevin)

CAN YOU GO TO RECOVER YMODE? turn off your phone, hold power and volupe up together, release after the phone vibrates...you should go to recovery mode.

No Recovery Mode
DallasCZ said:
CAN YOU GO TO RECOVER YMODE? turn off your phone, hold power and volupe up together, release after the phone vibrates...you should go to recovery mode.
Click to expand...
Click to collapse
Sadly no. That would be too easy. I occidentally wrote the not working boot image over top of the working recovery image. (Yes I know, I am an idiot. I knew I was doing it at the time, but I hit reboot anyway. That's when the loop started.)

You need a bunch of files in order to flash anything while the device is in download mode. Search in baidu for 'tct msm8939 qpst'. You will find info (and the necessary files) for m3g. The device has identical hardware as 6045, but I don't know where the similarities end. Your device can become completely unusable when you play with these tools (QPST, QFIL etc.), but I'm sure that you are aware of this. Good luck.

what about off warranty repair by alcatel service in your country?

N101BL said:
Sadly no. That would be too easy. I occidentally wrote the not working boot image over top of the working recovery image. (Yes I know, I am an idiot. I knew I was doing it at the time, but I hit reboot anyway. That's when the loop started.)
Click to expand...
Click to collapse
The loop you described doesn't sound like it has anything to do with recovery...you described what happens when you FLASH the boot.img used to root the device instead of just booting it. This will result in the infinate loops. The recovery partition is not used at all until you actually try to go in it by holding down up arrow while it's booting...I would try this several times to ensure you can't get into recovery because if you can get there you can restore your device. If you can not, then it's a paperweight and you should send it off for replacement because it doesn't look like any way to flash it using "download mode" is going to come out anytime soon.
---------- Post added at 08:22 AM ---------- Previous post was at 08:20 AM ----------
petrov.0 said:
You need a bunch of files in order to flash anything while the device is in download mode. Search in baidu for 'tct msm8939 qpst'. You will find info (and the necessary files) for m3g. The device has identical hardware as 6045, but I don't know where the similarities end. Your device can become completely unusable when you play with these tools (QPST, QFIL etc.), but I'm sure that you are aware of this. Good luck.
Click to expand...
Click to collapse
Perhaps the chinese version of the idol 3 that was just released will lead to access to some of the config files we need.

famewolf said:
Perhaps the chinese version of the idol 3 that was just released will lead to access to some of the config files we need.
Click to expand...
Click to collapse
Probably but the files must be released in the wild first. I do searches in baidu from time time in case that something interesting pops up. I also must to admit that the translation of these sites is awful in most cases

Update
Well I sent my phone back.. Fortunately it was under warranty!
But now another hopefully minor issue with the replacement phone.
Please see this thread and post if you know what I am missing. I really appreciate your time and efforts!
http://forum.xda-developers.com/idol-3/help/valid-backup-file-t3199797
famewolf said:
The loop you described doesn't sound like it has anything to do with recovery...you described what happens when you FLASH the boot.img used to root the device instead of just booting it. This will result in the infinate loops. The recovery partition is not used at all until you actually try to go in it by holding down up arrow while it's booting...I would try this several times to ensure you can't get into recovery because if you can get there you can restore your device. If you can not, then it's a paperweight and you should send it off for replacement because it doesn't look like any way to flash it using "download mode" is going to come out anytime soon.
---------- Post added at 08:22 AM ---------- Previous post was at 08:20 AM ----------
Perhaps the chinese version of the idol 3 that was just released will lead to access to some of the config files we need.
Click to expand...
Click to collapse

PLEASE HELP! Attempted to root, now stuck on boot screen. Verification fail/mismatch

I'm brand new to LG devices & was using this threads instructions
http://forum.xda-developers.com/tmobile-lg-g5/development/root-h830-t3384526
I tried rooting using a TOT file in LG UP. However, when I opened lgup it said I needed to download the driver for it to work. But I had downloaded the h830 DLL and the mobile drivers, and the program launched and saw my device so I just continued.
After it opened, I just selected the TOT file and started, it finished, and now I can't get past the boot screen. There's red language at the upper left saying 680,730,780 boot verification fail, 830-cause mismatch_sig_len, 880,930
Ive read and downloaded things for hours now trying to figure out how to get it back to stock. I've downloaded the 4.9gb tot file that's linked in that thread for going back to stock, but all I can find is people saying use lgup to flash the file.
My question is, how do I accomplish that if I can't get past this screen? I can't get it back in the bootloader. I can't get it to be recognized by the pc. And lgup still says it needs the driver when I open it, and it doesn't see the phone either. Please help. I've had this phone all of 1 day.
BTW, I uninstalled lgup and the driver and DLL, rebooted, then reinstalled the DLL and driver first, before reinstalled lgup and it still says it needs the driver.

Anyone?
I never used adb to unlock the bootloader before trying to flash. I thought I only had to check oem unlock and USB debugging in developer options because I was trying to use iroot first.
My main problem is my phone starts up but doesn't get past the LG logo. It shows the boot verification error, mismatch_sig_len then immediately reboots and does it again. How do I reflash the stock TOT file in this state?
Is it just a driver issue, and my phone should be seen by lgup even in this bootloop? Or do I have to get it back into bootloader? If so, how?
Please don't disregard if I sound like a total idiot. I do have experience flashing with galaxy devices. I just didn't do enough research before I tried this one.

Have a look at LG Flash.

im stuck in pretty much the same spot as you. you can press up during that boot loop to go back to download mode, but when i run LGUP again with the "stock" version, there is an error a few seconds in. that says error code 0x81000402 tot antirollback version is smaller than device version. Thats all i got for today, hopefully some one will be able to help us out.
as for lg flash, i found the program but im not sure what to do with it, do you have any instruction, or directions for how to use it?
one thing i noticed, was i was doing all fo this with lg up version 1.11, not 1.14. that might have caused our problems, check to see wich version you used. but in the end i downloaded lg bridge and simply had it update my phone. it could read my phone when it was in download mode, that you get to by pressing the up volume button. ended up without root, but it was no longer in a bootloop.

konchar said:
im stuck in pretty much the same spot as you. you can press up during that boot loop to go back to download mode, but when i run LGUP again with the "stock" version, there is an error a few seconds in. that says error code 0x81000402 tot antirollback version is smaller than device version. Thats all i got for today, hopefully some one will be able to help us out.
as for lg flash, i found the program but im not sure what to do with it, do you have any instruction, or directions for how to use it?
one thing i noticed, was i was doing all fo this with lg up version 1.11, not 1.14. that might have caused our problems, check to see wich version you used. but in the end i downloaded lg bridge and simply had it update my phone. it could read my phone when it was in download mode, that you get to by pressing the up volume button. ended up without root, but it was no longer in a bootloop.
Click to expand...
Click to collapse
Please browse the thread and/or the guides section first. It's there. Being self-sufficient never hurt anyone.

konchar said:
im stuck in pretty much the same spot as you. you can press up during that boot loop to go back to download mode, but when i run LGUP again with the "stock" version, there is an error a few seconds in. that says error code 0x81000402 tot antirollback version is smaller than device version. Thats all i got for today, hopefully some one will be able to help us out.
as for lg flash, i found the program but im not sure what to do with it, do you have any instruction, or directions for how to use it?
one thing i noticed, was i was doing all fo this with lg up version 1.11, not 1.14. that might have caused our problems, check to see wich version you used. but in the end i downloaded lg bridge and simply had it update my phone. it could read my phone when it was in download mode, that you get to by pressing the up volume button. ended up without root, but it was no longer in a bootloop.
Click to expand...
Click to collapse
Thank you for this post. Just knowing that someone who had the same issue as me was able to get the phone back to stock successfully made me not so anxious.
My main issue the other night when I was trying to fix the phone, was I couldn't get it back into download mode. I had the phone connected to the computer, and was disconnecting the battery and connecting it again while holding volume up, with the cable always connected. Tonight, I just help volume up while plugging in the cable instead, and was able to get it into download mode.
I then ran into the same anti rollback issue. But I'm now using LG Bridge to go back to stock.
I think what we need to do to get root, is enable USB debugging and check oem unlock. Then use the sdk tools with the command prompt window... Adb reboot bootloader>Fastboot oem unlock, then try flashing the root tot file with latest version of lgup.
As long as I know I can get back to stock, I won't be so scared about attempting the root again. Lol.
TH4N1X said:
Please browse the thread and/or the guides section first. It's there. Being self-sufficient never hurt anyone.
Click to expand...
Click to collapse
Come on man. Some of us have spent hours searching what to do, and are running into unforseen issues and just need a little guidance. I'm all for searching threads to get your information, but when your hours or days in and running into walls, regardless of the reason... It's ok to ask for help. Not everyone has the same knowledge and skill level with this stuff. I've only ever used Odin to flash stuff to galaxy phones before... All this LG stuff is brand new to me.

Ok relax, in order to have your device recognized by your pc you must now put it in d/l mode (with power off, hold volume down and power until d/l mode starts) then run LG UP and try to downgrade. If that gives you the all to well known anti-rollback error then you need to download the hacked version of lg up (forget what it's called but it's in one of the rooting threads) and then downgrade. I struggled with the same thing a while back. My memory just isn't so good but I'm confident you'll figure it out.

@SaintCity86
autoprime said:
Repacked LG's original installer with @ieatacid's patched EXE.
Should make installing it all even easier... no more EXE switch.. just install and use (hopefully).
I made sure to add ieatacid's name, paypal and this thread in the Setup EXE.. this way ieatacid's name will always be attached to the LG Flash install rather than the loose LGFlash.exe getting passed around like the old megalock.dll.
Added LGUP and LG Flash directions and downloads to my All-in-One G5 Thread here.
{
"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"
}
MD5 (Setup_LGFlashTool_2.0.1.6-ieatacid.zip) = 7e2a5a6c74ac3d54a707c7fcde831655
MD5 (Setup_LGFlashTool_2.0.1.6.exe) = 6d0f8a4ad4bc01157a9c7c16f3a7c574
Download Setup_LGFlashTool_2.0.1.6-ieatacid.zip
Click to expand...
Click to collapse
Second page, 7th post on it (17th in total). It's also stickied in the Guides, News, & Discussion section.
http://forum.xda-developers.com/showpost.php?p=66683763&postcount=17
You can also try different versions of LG UP and if it fails go for the LG Flash. You can find software to flash here: http://lg-firmwares.com/lg-h830sv-firmwares/. Only flash KDZs from the TMO region. If you succeed in going back to stock, you can get recovery and root by using the Dirty COW exploit.
One more thing:
SaintCity86 said:
Tonight, I just help volume up while plugging in the cable instead, and was able to get it into download mode.
Click to expand...
Click to collapse
That's how you actually get into download mode. Battery pulling is for getting out of it.

So I managed to get it back to stock by using LGBridge and updating. And I've been using the 3 step guide in this thread:
https://forum.xda-developers.com/tm...p-step-guides-rooting-t-mobile-lg-g5-t3388272
All seemed to be going fine, but when I put my phone is is debugging and checked oem unlock then plugged it into my laptop (64bit windows 7), it failed to install 2 parts of the initial driver. MTP and another one I can't remember. But it is recognized by the computer when it's on.
However, when I boot into fastboot, it's only showing up as an android device with no driver. And I can't figure out which driver to get for the life of me. Idk if I'm running into issues because it's a 64bit system or what. Do you Have any suggestions where I can look to get this resolved?
TH4N1X said:
That's how you actually get into download mode. Battery pulling is for getting out of it.
Click to expand...
Click to collapse
Yeah I'm aware. It's the same for Samsung galaxy devices which I've developed on for years....my issue was I had the phone plugged into the computer and was pulling the battery to turn it off and just plugging the battery back in holding vol up, with the cord still plugged in. I didn't realize there was a difference. I thought I just couldn't get into download mode.

djerick3 said:
Ok relax, in order to have your device recognized by your pc you must now put it in d/l mode (with power off, hold volume down and power until d/l mode starts) then run LG UP and try to downgrade. If that gives you the all to well known anti-rollback error then you need to download the hacked version of lg up (forget what it's called but it's in one of the rooting threads) and then downgrade. I struggled with the same thing a while back. My memory just isn't so good but I'm confident you'll figure it out.
Click to expand...
Click to collapse
UPPERCUT ?? thats the one your looking for

bassmek2 said:
UPPERCUT ?? thats the one your looking for
Click to expand...
Click to collapse
Yup that's it

get into download mode open device manager look for device with explanation mark right click and search for driver or u can show it where the driver is look for the folder where driver installed should be an lg folder C:\Program Files (x86)\LG Electronics\LG Mobile Driver if you don't have that folder then you haven't installed driver package download uppercut and get your kdz file I've had a few problems with a couple of kdz files I've downloaded they wouldn't install i think the file you need is H83020a_00_1107.kdz make sure when u go to flash that you have it in upgrade mode or else it will give you an error

SaintCity86 said:
Anyone?
It shows the boot verification error, mismatch_sig_len then immediately reboots and does it again.
Click to expand...
Click to collapse
Good day!
How did you solve your problem?
I have same trouble with my LG H830. When i try to boot in DL mode, appears small icon Dowload Mode and the phone restarting again with error:
[870] Boot verification fail!!
[920] cause : MISMATCH_SIG_LEN
How did you boot to download mode?
Thanks.

Trouble rooting UMX U683CL

I'm having so much trouble with this process, I think at least in part because it's a no-name brand with no manufacturer website for resources, but also most guides I'm finding on the rooting process are very much "draw the rest of the owl". Lots of "okay now do this with this file" without explaining how to do that or where to get the file, which leads me to my current problem. I'm trying to follow the guide here. Where I'm stuck is "GPT file from your firmware or backup". No idea how to obtain that. I have the firehose programmer file, I think; the main guide I'm following to try and root my phone, here, says I need prog_emmc_ufs_firehose_Sdm660_ddr.elf, which I've downloaded. I have all the drivers, I have QFiL, I have QPST, I have Qualcomm GPTtool, and I don't really understand what to do with any of them or why it's not working. What I need, based on the main guide I'm using, is rawprogram0.xml and patch0.xml. But I need the GPT file to generate those? I'm so far over my head with this, I just want my phone rooted and working. Also, tried the secondary method at the bottom of the main guide (second link), and got this result:
{
"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"
}
Edit, because apparently XDA is all about posterity and doesn't like threads on completely different problems if they're the same person and the same phone: I did finally get to the point of rooting it. The major problem I have now is that it will only boot to fastboot mode. I can get it into recovery mode, but I get the dead android with "no connection" under it, and I've tried everything the internet has suggested to get past that, and it won't. Additionally, any fastboot command (apart from "fastboot devices") I try in ADB returns "FAILED (remote: 'unknown command'). I don't know how to get it into EDL mode from fastboot. I've tried every button combo possible, and the only one that does anything different is power + volume up, which changes it to a bright white screen. At this point I just want to do a hard reset so I can take another go at the rooting process, but the phone doesn't seem to want to allow me to. I would appreciate any help with this; I don't have a working phone at the moment because of these issues.

use linux, no rawprogram0.xml needed (you can however generate rawprogram0.xml with this)
https://github.com/bkerler/edl

I don't have Linux, I don't want Linux, but that link might be useful if I reach the point where I can try rooting again. So far out of six places, no one has been able to help yet.

QFIL is a pain. linux is easier when it comes to usb connection, no need to worry about drivers.
the link itself contain bootable iso you could run from pendrive. however it's possible to install python and run everything on windows, too.
for EDL mode try these methods
- power off device, hold both Volume keys and plug in usb-cable
or
- fastboot oem reboot-edl
or
- DIY deep flash cable
or
- test point method
once in EDL mode you can flash little kernel which contains fastboot instruction set, brings fastboot back to life.
with that EDL tool one can enable OEM unlock, then unlock bootloader from fastboot. once unlocked, flash phhusson's or AndyYan's GSI or whatever ROM and U683CL firmware from one of the U683CL threads.
it's good you already have working firehose loader for this device, device can be unbricked and rooted easy.

In looking up how I might find the test points for this phone, I found a video on factory resetting this exact model, which contained the revelation that to get past the "no connection" android, I needed to hold the power button and TAP volume up once, rather than hold it like I've tried before. So I got into recovery mode, but I wiped the data and the cache and it's still only booting into fastboot. If I hold the two volume buttons and then plug it into the computer, I get the white screen, so maybe that's EDL mode as the phone stands right now? QPST's detecting it now, at least, as Q/QCP-XXX (Sahara Download). So I guess I'll try reflashing. I think I still have the stock firmware somewhere, but do I need a ROM as well?

I have/had this device, I was able to root no issues. It's a junk device and I quickly quit working on it but I think I posted stuff for it on here at one point

somnomania said:
In looking up how I might find the test points for this phone, I found a video on factory resetting this exact model, which contained the revelation that to get past the "no connection" android, I needed to hold the power button and TAP volume up once, rather than hold it like I've tried before. So I got into recovery mode, but I wiped the data and the cache and it's still only booting into fastboot. If I hold the two volume buttons and then plug it into the computer, I get the white screen, so maybe that's EDL mode as the phone stands right now? QPST's detecting it now, at least, as Q/QCP-XXX (Sahara Download). So I guess I'll try reflashing. I think I still have the stock firmware somewhere, but do I need a ROM as well?
Click to expand...
Click to collapse
stock firmware is the rom

for QPST/QFIL you need rawprogram0.xml and Qualcomm HS-USB QDLoader 9008 Drivers.
with ROM i mean android boot + system partition (+ vendor maybe).
with firmware I mean bootloader, tee, baseband, modem, sim, wifi, touch, sound, etc (various partitions).
the former one can be replaced with custom ROM or GSI, or just use stock ROM. the latter is important for unbricking. usually it's all together bundled in full stock ROM/firmware download.

PizzaG said:
stock firmware is the rom
Click to expand...
Click to collapse
Thank you.
I have all of that, and I'm still having issues. With QFIL, I'm getting Sahara fail, process fail, and flash information is not filled. Now I can't even get it to detect the phone, after multiple attempts and disconnecting and reconnecting and closing QFIL and reopening it and moving files, it's like it got tired or something. And I attempted the GitHub thing, but I'm stuck on installing because CMD tells me when I put in "pip3 install -r requirements.txt" that "pip3" isn't recognized as anything. I think that method is too much for me anyway, I don't understand most of what it says past the installation part.

I don't know about windows but try pip.exe and pip3.exe
Code:
%USERPROFILE%\AppData\Local\Programs\Python\Python39\Scripts\pip.exe install -r path\to\requirements.txt
usage is quite simple, but you need to connect device in EDL mode before a certain timeout. try with battery removed and both volume keys. linux no need for drivers or rawprogram0.xml
this is how I read recovery partition off device (on linux)
Code:
python edl r recovery recovery.img
Spoiler: example
Code:
[email protected]:/media/xubuntu/18CC6C07CC6BDE0E/src/edl$ python3 edl.py --loader='/media/xubuntu/18CC6C07CC6BDE0E/Android/Backup/citrus/POCO M3 - Redmi 9T nfc - Redmi 9 Power - Redmi note 9 4G/prog_firehose_ddr.elf' --memory=UFS r recovery recovery.img