Related
Is it possible to perm brick your phone? My phone got stuck somewhere in the middle of an Odin flash and I had to pull the plug. Since then I have been stuck at the "Phone...!....Computer" picture.
I can get the downloading "Do not turn off Target!!!" section with the cable plugged in and no battery. I also have it recognized by Samsung PSLite, but when I'm trying to flash the stock rom back on through PSLite it disconnects as soon as it goes to 0%.
Will it make a difference that I have Win7 64bit and the VIA drivers say 32bit on them? I'm pretty sure I have every other driver that's needed.
Any help is GREATLY appreciated. I'm a sad panda without my new phone :-(
Go to the dev section of this forum.
http://forum.xda-developers.com/showpost.php?p=14147928&postcount=3
Follows these directions exactly. Will recovery your phone for you.
Good part is, you are not bricked.
Yeah, I've been following a couple of forums that all show nearly the exact same directions. Been getting stuck on the same area...
I have very little knowledge of any of this other than following instructions (obviously not that well) but something tells me it has to be a driver issue.
The VIA drivers I installed say 32bit and my machine is Win7 64. Also, when I plug the phone in it is recognized by my computer with no errors. Once I start the install and it gets to "VIA download" I get the error - then my computer tells me the device was not recognized. I have to do a full reboot to get my computer to recognize my phone again.
Thanks for the directions
Hey man, if that isnt working for you (which I dont see how.) You can always call tech support and say your phone is not booting, even after you pull the battery out. Just say it stays stuck on the samsung screen. They will send out a new phone. Just saying but it should work regardless. Also try another USB port, see if that solves your issue and make sure you are using the OEM usb cable.
I'm assuming this will work for you. It did for me. I had the same screen.
Download first file.
Odin 1.82
Open Odin then hook up your phone and put into download mode with the battery out. Crucial part here. Put the battery back in. After flash the first file I linked you to but make sure you check the PDA option and do it through PDA only.
Should fix it I do believe.
If you follow that exactly like is says. from start to finish. forgetting that you have ever tried anything before. And still follow it. You will be fine. download everything it says download, and follow the instructions exactly.
Thanks for all the feedback everyone.
I've been trying everything suggested on here except getting a newer version of Odin. When I get in tonight I'll keep trucking along with different tweeks.
The good news is I accepted defeat (Grrr!) and have a warranty replacement on the way. It kills me that I couldn't get this on my own.
I've even installed everything on my laptop with the exact same results. As soon as I get to the downloading portion where it shows 0% the phone disconnects and my computer tells me it is no longer recognized. This was in PSLite. Odin simply says FAIL when I try to flash that method.
I have a week to return the first phone. I'll use that time to get all my drivers in order and get this figured out.
After you put the phone into download mode when it was hooked up to the computer did you put the battery back in? I had the same screen as you and when I tried to use Odin it would just say it failed every time. Put the battery back into your phone after it is in download mode before you try to flash with Odin.
Also for PSLite I had to plug in the phone (in download mode) before starting PSLite (opposite of ODIN).
Odin... OdinOdinOdinOdin!
That was my problem. I was using silly PSLite instead of Odin.
Thanks again everyone for the help! Now to see if I can break her again...
mikepic said:
Odin... OdinOdinOdinOdin!
That was my problem. I was using silly PSLite instead of Odin.
Thanks again everyone for the help! Now to see if I can break her again...
Click to expand...
Click to collapse
Actually PSLite worked for me and not ODIN, but for others ODIN worked. I guess it is good to try both. Too bad both seems so flaky! Rooting on the OG droid was a breeze compared to the charge. The OG droid was indescructible.
elucid said:
Actually PSLite worked for me and not ODIN, but for others ODIN worked. I guess it is good to try both. Too bad both seems so flaky! Rooting on the OG droid was a breeze compared to the charge. The OG droid was indescructible.
Click to expand...
Click to collapse
Then go back to the OG Droid. It takes literally 10 min to root a Droid Charge. If you follow the instructions like we tell you to, its not hard at all.
dragonstalker said:
Then go back to the OG Droid. It takes literally 10 min to root a Droid Charge. If you follow the instructions like we tell you to, its not hard at all.
Click to expand...
Click to collapse
I agree rooting was really easy. Several people have had issues where they needed to restore using and ODIN and it complete fails (this is after using ODIN successfully to flash ROMS, recovery, kernels). See the end of this thread:
http://forum.xda-developers.com/showthread.php?t=1108115
You can blame it on user error, but I can assure you that I didn't do anything that should have caused my /data partiion to not mount. Sometimes things happen and the last thing you want is ODIN failing to flash when you have a brick on your hands.
Hope you fix your phone :] It always pains me to see one of these posts where someone has a bootloop or even a dreadful brick.
Hey ppl! I messed up my phone and I need some help. I have a G2x and I recently rooted it using the root.zip I found on one of the forum threads here. It worked fine and I flashed over to Eagleblood 2.5 and I didn't notice when I downloaded it that it didn't come with the google apps. I couldn't figure out how to get the google apps back into the phone since market wasn't installed. I tried downloading it but the phone kept telling me I don't have an SD Card being that I don't have an external one yet. Yes, I could have just downloaded it on pc and then transfered market apk via usb but I couldn't find the option to activate usb which was weird. Usually when you plug in your usb cable the driod icon pops up. So instead of flashing back using the backup I made on CWM I used nvflash and then used that LG tool to install V21E_00.kdz to install Gingerbread again. That's where everything messed up. I no longer was getting a cell signal and the battery icon had a ? in it. I assumed that the installation went bad to i did the process again with the nvflash and the V21E_00.kdz file. I got the same results again. I managed to get the wifi working again cause it wouldn't connect and downloaded cm7 7.1.0.1 to see if it would fix the problem. I flashed over and got the same results on cm7. No cell signal and battery icon screwed up. I gave up and did a full wipe and tried to install Gingerbread again. This time my pc wasn't reading my phone anymore when I connected it to the usb to use the LG tool to install V21E_00.kdz. Now my phone is in a cm7 boot cycle. If my phone is broken just tell me so I can dump it. My friend warned me about the G2x and I didnt listen cause I was in a hurry to get a nice phone. Any input and help would be greatly appreciated. If you guys need more info on anything please ask. If I can salvage this hunk o' junk I'm getting rid of it.
This phone is unbrickable damn near, have you tried the rom for recovery in development section? It will low level nvflash your phone to GB OTA 2.3.3 good luck.
http://forum.xda-developers.com/showthread.php?p=17258229
Sent from my LG-P999 using xda premium
Great! Thanks for the help. The phone is somewhat alive but I still have no cell signal and my battery icon has a question mark in it again. I was reading on that thread you linked me mentioning to do a firmware upgrade using the kdz file or LG Tool. Do I have to flash the firmware to get the cell signal working and the battery icon to work? If so, where do I get the firmware to flash?
To fix the boot loop cycle just boot back into clockworkmod recovery and do a factory reset, wipe cache, Dalvik cache, and then reboot and give it several minutes (first boot takes a little longer).
Or since you said you have a backup, just boot into clockworkmod, do a factory reset, format /system, and then restore your backup.
Again, the first boot always takes a little longer.
Thanks phburk I managed to get the phone working again with the flash.bat file from the link posted but I still dont have cell signal and battery icon has a question mark in it. I'm trying to download and use the LG Update Tool to see if that flashes the firmware to get the cell signal and battery icon working again.
The LG Update Tool fails at 30%. I can't get wifi on the phone to work and I have no cell signal and battery icon has a question mark still. This phone has to be broken. I see no fix in site for this problem. Anyone want to trade a GS2 for a G2x?
Kolcrok78 said:
The LG Update Tool fails at 30%. I can't get wifi on the phone to work and I have no cell signal and battery icon has a question mark still. This phone has to be broken. I see no fix in site for this problem. Anyone want to trade a GS2 for a G2x?
Click to expand...
Click to collapse
If you have a backup from a working configuration, try restoring that. Before you restore it, boot into clockworkmod and do a factory reset, and then format /system. THEN restore your backup.
After you restore allow the phone to reboot. If you still don't have signal then go to Settings > About Phone and see what it says for Baseband version.
Right now its going to show "unknown" for baseband. Might sound stupid but remove the battery sim card and sdcard for 5 minutes or so and then put them all back in and reboot. Try that after the factory wipes and installing a new rom. I've done that when I saw the "?" And no cell or data...
Sent from my LG-P999 using xda premium
I'll give it a shot. That's all I can do at the moment.
I no longer have a backup. The backup got corrupted that's why I've been trying other methods of restoring my phone. After running backup from CWM, the phone would reboot and stay on a black screen and flash. Screen would go dim then black like the backlight showing a black screen and dim again. That's all it kept doing and would not reboot. I tried doing a kdz flash but the pc wouldn't even recognize my phone when I plugged in the usb. (Yes, the drivers were installed and it was working. Previous to this I have kdz flashed twice. Phone has to be in S/W Update Mode by first pressing power button and as soon as the LG Logo shows up on the screen, let go of the power button and hold volume down.)
This resolved my reboot issue since I couldn't do a kdz flash.
http://forum.xda-developers.com/showthread.php?t=1248644
It got my phone working but still have unknown baseband and a question mark inside my battery icon.
**Update**
I read several threads regarding unknown baseband issue.
I've tried this method:
http://forum.xda-developers.com/archive/index.php/t-1332350.html
Since I already just did the first part by using the flash.bat file all I had to do was use the kdz flash. Unfortunately, my pc is still not recognizing my phone when I plug it in to the usb while in S/W Update Mode. I tried using this method above since the phone doesn't have to be in S/W Update Mode.
Outcome:
The LG Update Tool used in the method above kept stalling at 4%.
I read in another thread that this LG Update Tool doesn't work on Gingerbread. This LG Update Tool only works on Froyo.
So my next option was to use this method and try installing Froyo:
http://forum.xda-developers.com/showthread.php?t=1048274
This method just didn't work period. Since I don't have baseband or wifi working on the phone I can't get into market to download Rom Manager and I can't install File Expert which I have backed up on my pc. I already had the _ExternalSD directory so I made a sub directory /clockworkmod and another subdirectory /backup in the previous subdirectory. Made this on both the External and Internal sd cards and CWM tells me Couldn't open directory - No files found. So installing Froyo this way was out of the question.
I found this thread:
http://forum.xda-developers.com/archive/index.php/t-1037120.html
This is the stock Froyo version before the Gingerbread update as a zip file.
Unfortunately, when I tried to install the zip file from CWM it didn't work. I unzipped the zip file and found 2 .bin files which answers my question why CWM didn't install the zip.
I tried this method as well:
http://forum.xda-developers.com/archive/index.php/t-1332350.html
This method involves the flash.bat file to be done as a prerequisite before flashing to kdz. To my understanding, the flash.bat file fixes the partitions that most likely were screwed up on the phone and the kdz flash fixes the baseband (update/repair). I still haven't been able to get that kdz flash v1e to work simply because my pc won't recognize my phone into the usb when its in S/W Update Mode. I'm leaning towards the LG Update Tool to fix my baseband but I just need to downgrade to Froyo.
Don't know what else to do. I've been at it for 2 days and I'm seriously going to give up and just cancel T-Mobile.
If one of the methods involves installing apps, u can use adb to install them from ur computer without having to copy them to ur phone. But that's if u can get it into usb debugging mode.
Sent from my LG-P999 using XDA App
When you installed the rom, there should've been an extra package for Google apps that you should have flashed along with the rom as well, but you did so many different things, I don't know what to say.
You don't need your backup, it won't fix your baseband if it's corrupted or at all because no one has been able to get this phone to independently flash a baseband and the only way is through running the Gingerbread update either with KDZ or the LG updater.
I also went through hell more than once when I bricked my phone a few times. The first time I spent almost 2 weeks at it until I fixed it with the help of others here.
I also had the KDZ update stop at 4% over and over again which drove me crazy with anxiety. I was desperate so, after a few of those 4% hangups, I decided to reinstall a ROM and kernel just to see if the phone's baseband had installed anyway. Well, what a surprise, it did work.
You should try KDZ update again and, when it stalls at 4%, leave it for about 20 minutes then install a ROM based on Android 2.3.3, such as Weapon 3, fix permissions then reboot. That's what worked for me once. Another time, I did the same but I installed MTK drivers first then ran KDZ which stopped at 4% too but it worked too.
Read post #20 in this thread about how someone else did that successfully: http://forum.xda-developers.com/showthread.php?t=1180177
Here's where the MTK driver is: http://www.4shared.com/file/EqniU1Xt/MCCI_r_Firmware_Update_Driver_.html
Kolcrok78 said:
I'll give it a shot. That's all I can do at the moment.
I no longer have a backup. The backup got corrupted that's why I've been trying other methods of restoring my phone. After running backup from CWM, the phone would reboot and stay on a black screen and flash. Screen would go dim then black like the backlight showing a black screen and dim again. That's all it kept doing and would not reboot. I tried doing a kdz flash but the pc wouldn't even recognize my phone when I plugged in the usb. (Yes, the drivers were installed and it was working. Previous to this I have kdz flashed twice. Phone has to be in S/W Update Mode by first pressing power button and as soon as the LG Logo shows up on the screen, let go of the power button and hold volume down.)
This resolved my reboot issue since I couldn't do a kdz flash.
http://forum.xda-developers.com/showthread.php?t=1248644
It got my phone working but still have unknown baseband and a question mark inside my battery icon.
**Update**
I read several threads regarding unknown baseband issue.
I've tried this method:
http://forum.xda-developers.com/archive/index.php/t-1332350.html
Since I already just did the first part by using the flash.bat file all I had to do was use the kdz flash. Unfortunately, my pc is still not recognizing my phone when I plug it in to the usb while in S/W Update Mode. I tried using this method above since the phone doesn't have to be in S/W Update Mode.
Outcome:
The LG Update Tool used in the method above kept stalling at 4%.
I read in another thread that this LG Update Tool doesn't work on Gingerbread. This LG Update Tool only works on Froyo.
So my next option was to use this method and try installing Froyo:
http://forum.xda-developers.com/showthread.php?t=1048274
This method just didn't work period. Since I don't have baseband or wifi working on the phone I can't get into market to download Rom Manager and I can't install File Expert which I have backed up on my pc. I already had the _ExternalSD directory so I made a sub directory /clockworkmod and another subdirectory /backup in the previous subdirectory. Made this on both the External and Internal sd cards and CWM tells me Couldn't open directory - No files found. So installing Froyo this way was out of the question.
I found this thread:
http://forum.xda-developers.com/archive/index.php/t-1037120.html
This is the stock Froyo version before the Gingerbread update as a zip file.
Unfortunately, when I tried to install the zip file from CWM it didn't work. I unzipped the zip file and found 2 .bin files which answers my question why CWM didn't install the zip.
I tried this method as well:
http://forum.xda-developers.com/archive/index.php/t-1332350.html
This method involves the flash.bat file to be done as a prerequisite before flashing to kdz. To my understanding, the flash.bat file fixes the partitions that most likely were screwed up on the phone and the kdz flash fixes the baseband (update/repair). I still haven't been able to get that kdz flash v1e to work simply because my pc won't recognize my phone into the usb when its in S/W Update Mode. I'm leaning towards the LG Update Tool to fix my baseband but I just need to downgrade to Froyo.
Don't know what else to do. I've been at it for 2 days and I'm seriously going to give up and just cancel T-Mobile.
Click to expand...
Click to collapse
Hello , looking for help to unbrick a partially bricked phone that allows me to turn on and use mostly everything , it seems to reboot itself every once in awhile. I can goto Kies and and try to repair but that doesn't work , also have odin with factory file and that shows Fail every time i try that. Hoping someone can help try to get back to factory settings.
Oh and i have read for 2 days here downloaded files and tried everything i can , but nothing seems to work. And when i restart phone it seems to go back to exactly where i left when it got bad root file or something. In the phone part even after i erase calls , it shows the people that called that day every time it gets restarted.
If anyone can help and walk me through , i'd be greatly appreciated. And i've watched i don't know how many youtube vid's on trying to get this back to factory mode.
Thank you.
just go into download mode and flash stock rom through odin.....
mohit378 said:
just go into download mode and flash stock rom through odin.....
Click to expand...
Click to collapse
I've tried mutiple times and always comes up FAILED.
Tried Kies option also....
Apparantly its stuck in Titanium backup mode and occasionally does a reboot on its own sometimes. But even if i try to reboot after erasing tons of stuff out of it.... it comes back to what it was or how it was. So basically the titanium even though it shows up nowhere in my apps or phone... it keeps reverting my phone back to where it was when it got messed up.....
Try this
redskies4you said:
Hello , looking for help to unbrick a partially bricked phone that allows me to turn on and use mostly everything , it seems to reboot itself every once in awhile. I can goto Kies and and try to repair but that doesn't work , also have odin with factory file and that shows Fail every time i try that. Hoping someone can help try to get back to factory settings.
Oh and i have read for 2 days here downloaded files and tried everything i can , but nothing seems to work. And when i restart phone it seems to go back to exactly where i left when it got bad root file or something. In the phone part even after i erase calls , it shows the people that called that day every time it gets restarted.
If anyone can help and walk me through , i'd be greatly appreciated. And i've watched i don't know how many youtube vid's on trying to get this back to factory mode.
Thank you.
Click to expand...
Click to collapse
I don't know if the fail you get in Odin may be caused by having the wrong settings. I have ran into a few tutorials online that use odin, each one had a specific way. Try running it again with all the options unchecked except for the Auto Reboot. Also make sure you place the correct file(s) in the correct slot. example: any bootloader file goes into the bootloader slot, etc. make sure its checked. Then run again, this may be the only reason your getting a fail, it may have nothing to do with Odin or your phone.
Of course disregard this message if you had already fixed you problem. Also another possible fix would be to use ADB command to push the files to your phone, I suggest looking into it, there is a good amount of info on it online. It could help down the line with future issues to know ADB. Here is a website I found helpful, it is a guide to using ADB sideload to save bricked devices. ------- (android-revolution-
hd.blogspot.com/2013/12/ow-to-use-adb-sideload.html) note: just copy everything after the dashes and in between the parenthesis and paste into url bar on browser. sorry i have to be difficult, first time posting on this site and they wont let me post in a link, but this guide may be the answer to all your phone trouble. Plus I know how you feel, I just bricked my phone too and I know how agravating it is when nothing works.
Good luck and let me know how it goes
Thanks
BAMTek.Inc said:
I don't know if the fail you get in Odin may be caused by having the wrong settings. I have ran into a few tutorials online that use odin, each one had a specific way. Try running it again with all the options unchecked except for the Auto Reboot. Also make sure you place the correct file(s) in the correct slot. example: any bootloader file goes into the bootloader slot, etc. make sure its checked. Then run again, this may be the only reason your getting a fail, it may have nothing to do with Odin or your phone.
Of course disregard this message if you had already fixed you problem. Also another possible fix would be to use ADB command to push the files to your phone, I suggest looking into it, there is a good amount of info on it online. It could help down the line with future issues to know ADB. Here is a website I found helpful, it is a guide to using ADB sideload to save bricked devices. ------- (android-revolution-
hd.blogspot.com/2013/12/ow-to-use-adb-sideload.html) note: just copy everything after the dashes and in between the parenthesis and paste into url bar on browser. sorry i have to be difficult, first time posting on this site and they wont let me post in a link, but this guide may be the answer to all your phone trouble. Plus I know how you feel, I just bricked my phone too and I know how agravating it is when nothing works.
Good luck and let me know how it goes
Click to expand...
Click to collapse
Thanks Bam.... I'm just in need of all stock files Including the PIT file which is like impossible to find it seems to try and get this phone back to factory reset mode..... The phone actually works but anytime it reboots or save anything...ect.... it just reverts back to when it got tripped up. Thanks again for anyone's help.
I'm going to try and encapsulate everything that's going on into this initial thread but I'm sure I'll miss something.
Basically, I undertook to root my phone last night. I followed all the steps in the root thread, and I thought it worked, but then when I went to the root checker to see if I was successful. The test couldn't get a result the first time, and then failed the second time. I've known my phone to be a little temperamental when it comes to stuff like that, so I shrugged it off. Then, everything started running with so much lag that my only option was a reboot. It came back up just fine, but then, apps wouldn't open anymore. Since a reboot fixes everything, I rebooted AGAIN... except no I didn't, because I couldn't move past the white splash screen.
After some time hacking around with TWRP, system restoring my phone and the like, I finally managed to actually load the OS again. I think the phone was rooted at that time, but I don't know for sure, because this was the drawback: I couldn't install ANYTHING. My idea is that the system was rebooted into read-only mode. I tried everything I could think of to revert the system to rewriteable again, but nothing ever panned out. There was just one thing that stood out to me: "Your phone worked properly when it wasn't rooted." So, I got the brilliant idea to use SuperSU to unroot my phone. Stupid, stupid move, because now my phone can't boot past the white splash screen again. As a last ditch effort, I decided that it was time to flash the stock system to the phone. Except I probably did it wrong.
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash recovery system.img
Code:
fastboot flash recovery boot.img
And where I stand now is that my phone will not boot past the white splash screen, and I can no longer access either TWRP or Fastboot.
Is my phone fooked, or can anyone save this?
#1 You can't flash system image via fastboot - it's semi-locked.
#2 You can't use 'flash recovery' command for boot and system images.
#3 For restoring your phone use SP Flash Tool - there's a thread in the General section called 'How to unbrick'.
Try it and let us know.
Cheers
Yeah, I realized afterward that if I were trying to flash the image of the system, I should not have used the "flash recovery" command because I disabled access to the other recoveries, lol. I have tried to use the SP Flash Tool in the past few days, but I could never get any download progress. I think my computer isn't making the VCOM drivers accessible to be able to flash those things to my phone. Do you have any advice on that end? Because I have seen that thread and tried those steps but I'm just not successful.
You should also read all replies to this thread - there are people who solved their problems with SPFT in their own way, that's how I've revived my phone from hardbrick.
Make sure you're phone is disconnected when you start the flash. AFTER you hit the download button in SPFT... then connect your phone...
Fantastic advice from both of you. I'm ready to revive my phone!
Okay, I think I'm making good progress on recovering my phone. I have managed to get back the stock recovery onto my phone, which I then used to install TWRP. But I'm not out of the woods yet. I used fastboot to flash the boot image onto my phone also, but when it came to the system image, I'm having a lot of trouble. The only ROM I can find for the Blu Pure XL is a 7z file. Now, I know how those work, I have 7zip and I extracted it for the system image. When fastboot was available to me, I couldn't push the system image to the phone. Now that I have TWRP and I have no more access to fastboot, I've tried to load the system file onto my phone through my SD card in four different ways:
As a .img file
As a .7z file
As a .zip file that I created by zipping up the image file
As a .zip file that was .7z, but I changed the extension
None of those methods worked. The Blu development thread doesn't point me to a zipped ROM file. One person there said that they had a backup of their files and provided a link, but those images seem to have been removed.
I'm so close, I can see this phone working again in the near future, I just need your help to get me there. Please! :'(
Edit: Also, keep in mind, I'm dumb. I don't think I really did anything super wrong, but I may be missing something ultra obvious. So if you could just keep your answers dumb for me, it would help even more.
I would stop trying to use all of the methods you are using I believe you are slightly confused by them at this time..
At this point what you have done with the random image flashing is get damaged partitions..
Get SPFT. Turn off you phone completely.
Download the full Scatter file for you phone. (put it aside).
Download a file called ALL MTK driver install. ( or something to that effect). Search for it on Google. You will find it. Run it and then reboot your PC completely.. (if you have windows 8 or higher look online on how to install unsigned drivers) --THIS IS THR BIGGEST PROBLEM PEOPLE HAVE--
Extract your full downloaded scatter image to a directory.. (you can download the Gionee E8 image if you want) it is what I am running on my Blu..
Run SPFD read the thread that they pointed out to you. Find the scatter and point SPFD.. Once it is loaded on the program UNCHECK the PRELOADER check box.. (if not you can cause problems) ..
click download and after 10 seconds or so plug in (you completely powered off) phone into the computer..
.Then wait..... and wait... It will tell you it's progress..
Keep trying it, it WILL work.. and ALWAYS unchecked preloaded when flashing with spdf...
I did follow all the steps in the original guide, and I followed the steps that you gave me too, down to using the advanced device manager to remove any MediaTek drivers from the computer and restarting the computer with disabling the driver signature verification, but when I click download, wait, and plug my phone into the computer, just nothing happens. The computer says it's an unrecognized device, and the download never progresses.
I see also that you said keep trying, but every time I try the SPFT, it never sends anything to my phone. And I don't even know how to tell if I'm missing some important step.
OK this happens sometimes. plug the phone in with device manager open.. plug the phone in when it is off..
When it says unrecognized device double click on it really fast( it will disappear fast, try it a couple of times if you don't get it the first time) then hit update driver.. point it to the MTK drivers folder (unzip the MTK drivers folder). It will pick the proper driver. on some computers it loads up so fast it has no time to recognize the driver..
After you load the drivers power off your phone again and follow the instruction I gave.. After you do this once it will load the drivers right after this..
When I double click on the unrecognized device button, it just brings up a notification that my device wasn't recognized because it malfunctioned. I don't have an option to install any drivers.
My problem is finally solved. After starting up SPFT and clicking download, I held Vol - and Power and then connected it, and that pushed the download forward. I got to the Blu animation screen, and it stayed up FOREVER, but then the next time I looked over, it was on the initial setup screen. Good as new.
Thank you guys for all your help. This forum really is an amazing place.
hi,
this is a guide for real helpless people, that got a V20 H918 T-Mobile out of the box and have no idea
what to do, to get TWRP and root. and since on this phone its a REAL hard odyssee if youre not a pro,
and you dont want to spend days and weeks to pick up countless small puzzlepieces to finally get all together up and running, i decided to write this guide. im no pro myself, but with countless hours of reading and try and error, misery, headaches and brainpain, i managed to get this thing running all right with working downloadmode,
newest TWRP-version and 20H oreo 8.0
so far, everything seems working good. ill play around with this version and if i encounter some crap, i will edit this guide later. sadly most "newbie-guides" here, are from pros for advanced users with decent knowledge. so when u start from zero, you dont understand half of what is written. thats why i will keep this guide as simple as possible, with some side explanations. its a lot to read and a lot to do, but this way works!
what we have before starting:
a V20 H918 t-mobile 20H oreo 8.0 with bootloader locked. simply a crippled standard phone.
what we will have after this guide:
a V20 H918 t-mobile 20H oreo 8.0 rooted, with unlocked bootloader, working downloadmode,
and newest TWRP-version.
with twrp u can backup your whole system "as it is", means u fukk up your phone, simply go to twrp-recovery, restore your backup and you have your phone up and running 100% as before all went down the drain. simply and easy. just like a new installation of win10, but in 5 minutes. u can flash custom roms, kernels etc., install all kind of stuff, no need to pay for apps anymore, get rid of obnoxious bloatware, just 100% freedom and the full potential with the V20 (which is the last phone of its kind with exchangable battery, which is why i got myself 3pcs of it )
sidenote: get yourself some extra protection foils so u can change from time to time.
also get yourself 1 or 2 10000mah powerbatterys from aliexpress (perfine) with protective rubbercase, of course, they dont have the printed-on mah, but at least a considerable amount, so that your phone will last at least 3-6 days. my V10 lastet 11 days normal usage with zerolemon powerbattery. unfortunately, these retards refuse to send to europe, and as far as i know, theyre not producing for LG phones anymore, so aliexpress/perfine is whats left.
the rubbercase gives the phone a superior protection, adds a serious amount of weight and will stick in your hand like glue. it is by far less likely to drop out of your hand like these glass-phones for imbeciles. and if it drops, the rubbercase grants excellent protection. my V10 dropped countless times, still working perfect.
but lets get to the guide now.
at first, we will unlock the bootloader. without it, you wont be able to do anything.
unfortunately, LG produces great phones (with great audio!) but terrorizes the users with their strict anti-root attitude. it seems it gets harder everytime to root and unlock the bootloader. i remember back in the days old samsung devices, had been rooted in no time. this one here cost me about 2 weeks.
on this phone, u simply cant hook it up to the pc, and unlock the bootloader with adb. it will be recognized by the pc, but as soon as u enter fastboot, nothing will happen, no command works.
the solution is a FWUL (forget windows use linux) usb-bootstick, with that u boot your
pc into a custom linux (i think) only here u have full access to your phone via fastboot and can unlock the bootloader in no time. it will not work on win10 !
- first, get rufus, a win10 tool, with that u can create boot-usb-sticks.
https://rufus.akeo.ie/
- then get the linux FWUL image (only 15GB version is still up)
https://androidfilehost.com/?w=files&flid=214529
- unzip the linux image to your c drive or your desktop.
- start rufus and select your usb-stick (it should be 30gb+ in size)
be carefull not to chose any other drive or stick (it will get erased completely), better double check.
- select the image you just unziped. (i use 7zip for unzipping)
- leave all other options as they are, press start. when dialog-box pops up, chose DD-mode !
- now waste some time, as it takes a long time to create the bootstick (in my case about 30min)
- when the stick is ready, in my case it couldnt be recognized anymore in win10, its just a raw-drive, that cant be
opened. thats allright. dont worry
- now close down all applications running and insert the created bootstick. (at this time u might consider using a
separate laptop, so you can follow this guide here at pc and use the laptop with linux running, thats what i did)
restart your pc, hit F2 or F8 oder DEL or whatever to enter bios.
select the created stick as bootpriority nr1. so that the system will use this stick as
the first bootmedium to boot from.
- u get to a screen with 9 bootoptions to chose from. chose the first one. it should now boot into linux.
when password request pops up, enter: linux
- u reach the "desktop"
connect your LG V20 H918 20H via usb-c to the pc, which has linux running, make sure that
developer options are unlocked, OEM-unlock and USB-debugging is enabled and u chose picture transfer protocol
(PTP) as transfer-protocol (also in developer options). if PTP doesnt work, try media transfer protocol.
watch your V20, at some point it will ask for confirmation of connection , click OK.
in linux, click on the up-arrow in the most downleft corner and chose "terminal emulator", which is
a pendant to windows shell/command-line.
- here you can execute the adb commands.
first, check if your V20 has been recognized by your pc with linux running.
type: adb devices
it should appear a message like:
* daemon started successfully *
LGH9182bfblablabla device
that means, that your V20 has been recognized correctly. now you can reboot it in fastboot mode.
type: adb reboot bootloader
your V20 screen goes black and seconds after, it restarts in bootloader mode ready for unlocking.
you might get a red warning that your warranty is void if bootloader is unlocked. cool.
type: fastboot oem unlock
wait for response, your bootloader is now unlocked.
u can check by typing: fastboot getvar unlocked
it should say: yes.
the bootloader is now unlocked.
now we will replace the standard recovery with twrp on the phone.
this step will be a little confusing and complicate, just follow the steps, and it will work.
since we cant flash twrp with adb, we have to use the linux bootstick again.
but before, we have to downgrade the 20H version to 10P, bcuz the next stepp will not work with 20H !
so you get the following:
DOWNLOAD H91810P KDZ FILE
https://androidfilehost.com/?w=files&flid=282709
after that, download LGUP (the LG tool for downgrading from 20H to 10P)
and uppercut (dont know what uppercut is for, i just used it instead of running LGUP directly and it worked. its supposed to recognize the phone/driver automatically)
http://downloads.codefi.re/autoprime...sh_Tools/LGUP/
and download the recent LG-usb drivers.
http://tool.cdn.gdms.lge.com/dn/down...=UW00120120425
install LGUP, uppercut and usb-drivers.
connect ur phone to pc in download mode.
turn of phone, press and hold vol.UP button and connect usb cable, small message appears, phone is now in download-mode and waiting.
now run uppercut and hope, that ur phone will be recognized. if not, think about, what kind of restrictions u did to ur system, like OnO-shutup or xpantispy (both great programs to keep win10 from calling home to scum gates) or whatever. in my case, it ONLY worked, after i reset the OnOshutup settings to recommended. so the phone get recognized correctly in LGUP (if not, try laptop or different pc), select upgrade and select the downloaded 10p KDZ file. press start or go, and wait until the procedure is finished.
now your phone is downgraded to 10p.
now we go back to linux, we connect the phone in downloadmode with the pc/laptop where linux is running,
(turn phone off, hold volUP, connect usb-c-cable with linux-pc/laptop, phone will start in download-mode.)
make sure, your laptop/pc has internetaccess.
on the linux-desktop, click on the LG folder, inside, click on LGLAF runningnaked.
a terminal-window opens.
type: git pull
type: git checkout h918-miscwrte
type: ./step1.sh
now we have flashed twrp onto downloadmode. why? i dont know, thats the way it worked for me.
we dont want twrp onto downloadmode, since twrp is a recovery. so the next step is, to flash the newest twrp version for H918 to recovery. at first, we will gather all neccessary downloads, after that, we will flash them one by one. that way, you dont have to get your micro-sd card out of your phone again and again. we put all together on the card, put the card in your phone and we are almost done. for now, have your micro-sdcard connected
with your pc and download the following:
twrp-3.4.0-1-h918.img
from
https://dl.twrp.me/h918/twrp-3.4.0-1-h918.img.html
and put this .img file on micro-sd card.
then download (and put on sd-card):
MAGISK ZIP DOWNLOAD (for root)
https://github.com/topjohnwu/Magisk/...gisk-v16.0.zip
then download original 20H firmware(and put on sd-card)
H918 20H
https://androidfilehost.com/?fid=11410963190603864639
you remember, we have now twrp on downloadmode
for restoring download-mode, download (keep on desktop or c):
H91820h_00_1115.kdz
https://lg-firmwares.com/downloads-file/17076/H91820h_00_1115
then download the firmware extractor:
https://forum.xda-developers.com/attachment.php?attachmentid=3975633&d=1482337024
ok, lets see what we have now:
we have the phone bootloader unlocked and twrp on downloadmode. we can access twrp when we start the phone in downloadmode (hold volUP, and connect usbcable, phone will start now in twrp.)
we dont want twrp on downloadmode, we want twrp as recovery. and we want to restore the original downloadmode. for that we do the following:
unfortunately, the neccessary file for flashing orignal downloadmode is not online anymore, so we have to extract it from the 20H firmware with the firmware extractor (thanks to logical gamer for his guide)
https://forum.xda-developers.com/v20/how-to/guide-h918-restore-laf-partition-t3804728
Extract WindowsLGFirmwareExtract vx.x.x.x. to your desktop, and open it up (preferably in it's own folder).
u might have to install framework 3.5 for it to run.
Select Open across from KDZ/TOT file, and browse to your KDZ (H91820h_00_1115.kdz)
you download previously and double click.
After it loads the kdz check H91820h00.dz, and click Extract KDZ.
Close and re open the program this time Click open across from DZ File in the folder where you placed WindowsLGFirmwareExtract you should see a file called H91820h00.dz Double click to open it.
Check laf_6.bin then click Extract DZ.
put this laf_6.bin on your micro-sdcard. thats your original downloadmode we will flash now.
ok, now we have our micro-sdcard with twrp, magisk, laf_6.bin and H91820h.zip.
put this mirco-sdcard in your phone. start the phone in downloadmode.
it will start in an older twrp-version. in twrp, go to install and select install img
select the twrp 3.4.0.1. img and on the following screen select "recovery"
swipe
this will flash the 3.4.0.1 version of twrp onto recovery.
then go to reboot into recovery. it will now boot into the newly flashed recovery.
then go to wipe, advanced, and select everything EXCEPT micro-sdcard!
this will totally wipe your phone (except twrp), so u can flash the 20H firmware onto a clean phone.
then, go to install, select H91820h.zip. this will flash your original oreo 8.0 firmware.
after that, go to reboot into recovery.
go to install, select magisk. install.
this will root your phone.
after that, reboot into recovery, go to install, select install img, select the laf_6.bin, and select "download"
now the original downloadmode has been restored.
now you can reboot into system, your phone will start as on day1, with new twrp on recovery and root.
i did a complete backup in twrp, so i can get back to a day0 clean install whenever needed. i will do a second backup with twrp with all the stuff installed and working ok and place this on my sd-card. so when things go bad, i always can go back to this state in no time.
congrats, your done. and me too . gonna get a cold one now.
hope this guide will help someone. in case, just drop a like/thanks/or just a short note.
its a long guide, and im no pro, if i made some mistake pls. tell here and i will correct.
thx to all the pro-guys for helping the helpless.
Hi
Im on v20 H918 firmware 10p with bootloader unlocked.
I tried with dirty cow but not works with lafsploit i have a Problem with rufus for create a bootable Linux.
Pendrive is 32 GB i followed your setting but my PC boot only in windows 7.
I succesfully unlocked a h990ds with dirty santa but for this model is not supported.
Can you help me
hi
i tried with dirtycow also, didnt work.
thats why i eventually came to the method i described.
teling by your short description, your next step would be to create a bootable linux-usb-stick, and to find a pc where it will boot correctly. the stick didnt boot on my main pc ( i dont know why, it just canceled with an error),
thats why i had to use the laptop where it worked.
Thanks for the guide man! Very funny and fun to read. I can't wait to turn mine into a 4-day brick like yours. #lastphonewithbatteryrevolution
Sadly I got the dreaded encrypted error at the end though when booting. Everything else worked fine.
After the encrypted error though I formatted and flashed LineageOS 17.1 and then magisk and still keep getting error 1. Even tried Lineage recovery and still same. I think maybe a problem with Magisk 16 itself.
Anyway it works fine just no root.
Edit: Had to flash Magisk 21 and it worked
Thanks for this tutorial. I was able to get my V20 rooted with minimal trouble. The only major trouble was finding a computer that will fully boot into Linux and the only minor issue was locating the UPPERCUT but I was able to find it. Link below.
It's probably worth mentioning that I had to rename laf_6.bin to laf_6.img in order to flash it in TWRP. Also, at the time of writing, the latest version of Magisk is 22.0 but I used Magisk v21.4 instead because it had a zip file (Magisk-v21.4.zip) available for download so that I can flash it via TWRP. Link below.
UPPERCUT link: UPPERCUT: Add Any LG Device to LGUP for TOT/KDZ Flashing (G4|G5|G6|V10|V20|MORE???) | XDA Developers Forums (xda-developers.com)
MAGISK link: Releases · topjohnwu/Magisk · GitHub
cool, glad this guide helped at least a little bit. my v20 still works great, no issues so far. as a side phone for unwanted persons, i still use my v10 with powerakku and rubbercase "brickstyle" every time i hold a regular phone from other people, it feels weird since these phones weigh like nothing, and i have to focus not to slip it out of my hand. i love my bricks
and by now, about 4 month later, reading this whole guide, to me its still strange and hard to follow. there is no way to get through this without reading everything possible about it and become familiar with all the technical terms.
I have a h918 with an unlocked bootloader and it's downgraded to 10p. The shell script fails everytime to a hash check. I've run it 4 separate times with the hashes being the same every time. So it looks like the file has been updated but the hash hasn't.
I'm coming late to the game and it seems most of the guides are out of date. I'd appreciate any help I can get.
Update: It works fine. This is by far the easiest guide to follow that I've found. Many thanks! I did have to follow xstahsie's tip.
xstahsieIt's probably worth mentioning that I had to rename laf_6.bin to laf_6.img in order to flash it in TWRP. Also, at the time of writing, the latest version of Magisk is 22.0 but I used Magisk v21.4 instead because it had a zip file (Magisk-v21.4.zip) available for download so that I can flash it via TWRP. Link below.
I followed the guide after I rooted and installed Lineage OS 18.1. I had to remove LineageOS because it was bad with response, couldn't see hidden wifi, and just ran hot. So I followed your guide and I am in a logo bootloop and get the reminder to lock the bootloader everytime it starts. Any suggestions for getting past the bootloop?
I fixed problem by installing LAF you referenced and then LGUP to 10p kdz. However I noticed two things.
1) Whenever I boot up I have the nag message to my bootloader. Any way to address this?
2) If I try to follow steps above to install 20h, I get a decrypt message in TWRP after I flash 20h and before Magisk. Anyone see this? I didn't encrypt my storage before hand.
memnon79 said:
I fixed problem by installing LAF you referenced and then LGUP to 10p kdz. However I noticed two things.
1) Whenever I boot up I have the nag message to my bootloader. Any way to address this?
Click to expand...
Click to collapse
You're stuck with it, it's just the way it will be from now on.
memnon79 said:
2) If I try to follow steps above to install 20h, I get a decrypt message in TWRP after I flash 20h and before Magisk. Anyone see this? I didn't encrypt my storage before hand.
Click to expand...
Click to collapse
I don't remember seeing that. I probably didn't care if it did show up since it was a new install from scratch anyway.
Does encrypting the phone work after following this guide?
hey there, cant help u with the encryption thing cuz thats far beyond my knowledge. some weeks ago my phone dropped, and a tiny crack on the edge appeared. what i didnt know was that this crack is the beginning of the end of the V20. heres the story short: small crack over time leads to a bigger crack, bigger crack multiplies and u have some more cracks covering the whole screen. also the screen can pop off and hanging loose a little. in my case 4-6 weeks and i have to get out phone 2/3 which i am setting up using this guide now. fortunately i left myself a huge pyle of information on how to do this when starting at 0. over time u forget EVERYTHING u have done, so having these infos is hammering.
lucky me did i save my internal memory of phone 1/3 bcuz 30min later the screen was totally fuqqed up, no access no chance of backupping internal memory.
so heres my recommendation:
DONT drop your phone. even in my case with rubber battery case from aliexpress
(perfine "10000"mah) a 50cm drop cracked the edge of the screen. if that happens, backup your internal memory !!! (just do this on a regular base)
when ur screen gets damaged and u cant enter information or cant see anything anymore on the screen ur internal data is lost. so always have ur internal memory backuped!
and great job LG for producing such a huge pyle of ****. one small drop, screen cracked, bravo, last time i ever bought anything from lg. my V10 dropped like a 1000times, nothing, still up and running. v20, drop, 6weeks later, dead. thanks LG the customers all over the world couldnt wait to use these bull**** crackable glass-screens. great job, -1 customer.
I've tried this on two different computers with two different cables in every USB port on the machines but can't get by the Windows portion. I am using UPPERCUT as the windows box/LGUP reports no device found without it...
Of course UPPERCUT drives windows security mad as it's reported as doing bad things but as I'm using an extra win laptop that will be wiped I disable all of that....
I have three different sourced KDZ files as the one linked wasn't initially reporting any mirrors. Eventually a mirror did pop up for it but by then I had downloaded two others -- all were the same size and one of the three reported from LGUP was bad. Every attempt with the other two failed. Invalid Command response came up a few times... sometimes it just failed at around 80+ percent from the PC side which was 99% on the phone's downloader mode progress bar.
It's very frustrating.... I would like to blame windows but there seem to me plenty here with success... any other ideas?
Also... since it got so far, rebooting at this point just goes to the download mode so I might be hosed... I can force it to the fastboot mode and it is still unlocked so I've been trying to install TWRP onto recovery using the linux/android machine but when I type
fastboot flash recovery twrp.img from the directory where twrp was downloaded I get this:
sending recovery --- okay
writing recovery --- failed remote: unknown command
So... any thoughts?
aloha, at which step are u stuck exactly? did u make your phone being recognized by the win10 pc?
one thing to regard is, that a usb-CHARGING cable possibly wont work, u need a designated media/data-cable.
i had this situation before, where using many different usb cables drove me insane bcuz i simply couldnt establish a proper data connection with phone/pc, it just didnt work. it took me many hours until i realized, that all of the cables i tried were charging cables!
for me the most difficult step was having the phone being recognized by the win-pc, the rest went relatively easy.
dikkbutt said:
aloha, at which step are u stuck exactly? did u make your phone being recognized by the win10 pc?
one thing to regard is, that a usb-CHARGING cable possibly wont work, u need a designated media/data-cable.
i had this situation before, where using many different usb cables drove me insane bcuz i simply couldnt establish a proper data connection with phone/pc, it just didnt work. it took me many hours until i realized, that all of the cables i tried were charging cables!
for me the most difficult step was having the phone being recognized by the win-pc, the rest went relatively easy.
Click to expand...
Click to collapse
The phone is recognized by the PC, no problem. I do have to use UPPERCUT to get LGUP to recognize it though. The step I'm stuck at is applying the downgrade. It gets to various percentages of done-ness and fails. It got far enough that now my only options on the phone are Download mode or fastboot mode. Problem is, I can't seem to get anything to push to recovery so I assume that it's still not properly downgraded.
I've tried a few different cables and keep in mind the cable I used in the linux adb bootloader step worked fine. I don't entirely know what difference there is between a charging and data cable but I do know the main differences in the steps are a> Windows and b> size of transfer.
weird. since im no pro myself, my ideas are limited on this one. there might be some kind of loose contact at the charging port,
that when the phone is moved just a little it looses connection for a second and reconnects again, had that in the past, so try not to touch the phone at all. did u use the 10p kdz file mentioned before? did u make sure it has been downloaded correctly?
if an error occured and there are some % missing... its like faulty ram, hard to detect.
assuming, u did or did not downgrade to 10p, did u try to continue with the linux-step? ---->
---------------------------
on the linux-desktop, click on the LG folder, inside, click on LGLAF runningnaked.
a terminal-window opens.
type: git pull
type: git checkout h918-miscwrte
type: ./step1.sh
now we have flashed twrp onto downloadmode
-----------------------------
maybe uppercut/lgup displayed an error message for no reason, and the downgrade itself went through without a problem in the background.
pcs sometimes do weird things.
if nothing works, try setting up win10 and try on a virgin system. in my case, OnOshutup prevented win10 from recognizing the phone,
or try using a 3rd pc from a friend.
i was able to setup my phone 2/3 using this guide in 30min, no problems at all. (i hope i wrote down, how i solved that simlock issue.....)
no matter what causes the problemin ur case , id be interested to hear what it was.
Thanks! Rooted and Unlocked thanks to this guide!
I tried following other guides using UPPERCUT and it fails to downgrade due to Anti Roll Back. How does this relate to this guide since the last thing I want is for (by design) for it to brick the phone. I have yet to find anything specific saying an unlocked bootloader will bypass the anti rollback check.
Hi As a noob does this keep VoLTE? I have followed this guide and backgrade to 10p was perfect! VoLTE working on a phone that was "new" from china. VoLTE did not work on the 20p rom it had. Also does anyone prefer Phoenix591's h918-20g-prerooted rom to the stock one? I have read a lot but am somewhat confused by varying instruction threads. I want to use this as a daily driver. Thanks