I saw my other thread and someone posted a link to a Vietnamese forum that wouldballow us to use send commands...
http://lgviet.com/forum/threads/huong-send-command-tren-lg-g4-android-6-0-marshmallow.53972/
Requirements:
Zv6 and zv9 tot files
LG UP
Drivers
LG_root.zip
1. Download and Install the LG Drivers and LG Up.
2. Download the ZV6 and ZV9 files
3. backup everything on your phone thats important to you
4. Use LG Up to flash to ZV9 fuly.
5. After Marshmallow has booted for the first time, power it down again and go in download mode once again
6. Use LG UP again this time use the zv6 tot file.
7. Once it gets to 9% immediately disconnect the phone and close LG UP
8. Download and extract LG_root.zip
9. Connect your phone again and run ports.bat
10. Now check which for LGDIAG port
11. Now you can run the Send_command commands.
From what i researched we still do need a modified kernel and other stuff to actually root the device as it wont work on a locked bootloader.
I wish I had waited until there were responses. I tried this, sketchy as it sounded, by unplugging at 9%.
Send_Command still failed and worse still, it broke my download mode. Whenever I reach 9%, I get an 0x2000 error with either ZV6 or ZV9 stock .tot files.
yablokosmonaut said:
I wish I had waited until there were responses. I tried this, sketchy as it sounded, by unplugging at 9%.
Send_Command still failed and worse still, it broke my download mode. Whenever I reach 9%, I get an 0x2000 error with either ZV6 or ZV9 stock .tot files.
Click to expand...
Click to collapse
Weird works fine for me
Why don't you do the kdz or TOT file instead of .img?
It's much easier to run straight aways with flash tool or LGUP
yablokosmonaut said:
I wish I had waited until there were responses. I tried this, sketchy as it sounded, by unplugging at 9%.
Send_Command still failed and worse still, it broke my download mode. Whenever I reach 9%, I get an 0x2000 error with either ZV6 or ZV9 stock .tot files.
Click to expand...
Click to collapse
Awesomeslayerg said:
Weird works fine for me
Click to expand...
Click to collapse
Doesn't work with ZVB. ZVB increases the ARB02 to ARB03. Will no longer work until we get a TOT for ZVB.
Well I don't have the device anymore sorry guys couldn't handle a device with a locked bootloader
Awesomeslayerg said:
Well I don't have the device anymore sorry guys couldn't handle a device with a locked bootloader
Click to expand...
Click to collapse
What phone did u go 2?
donbudafuko said:
What phone did u go 2?
Click to expand...
Click to collapse
Moto x purr edition
Good afternoon,
I wonder if this method works in h815p. If so, what command I use to extract the system.img of my phone? I would like to change the DPI in build.prop and make the flash again. Thank you.
leonardo_hd5 said:
Good afternoon,
I wonder if this method works in h815p. If so, what command I use to extract the system.img of my phone? I would like to change the DPI in build.prop and make the flash again. Thank you.
Click to expand...
Click to collapse
This is exactly what I wanna do; is it possible? If I can just edit my dpi in build.prop and update my hosts file I would be okay without having root...
Really thinking about replacing my G4 though. My phone bootlooped for the 2nd time and they updated to ZVB. ;(
emilyrugburn said:
This is exactly what I wanna do; is it possible? If I can just edit my dpi in build.prop and update my hosts file I would be okay without having root...
Really thinking about replacing my G4 though. My phone bootlooped for the 2nd time and they updated to ZVB. ;(
Click to expand...
Click to collapse
I believe it is possible , I've seen so "custom ROM " marshmallow for you here in sprint . In G4 forum there is almost nothing for those who do not have unlocked bootloader . I wonder how do I do to extract the system.img using send_command .
I managed to pull the system.img to my folder of the phone. I can see the file, but I get an error when copying it to the PC. I used the following code
dd if=/dev/block/mmcblk0 bs=8192 skip=55296 count=529920 of=/data/media/0/system.img
Click to expand...
Click to collapse
When trying to copy by using adb pull , he says I 'm not allowed . The file is in the / sdcard / .
leonardo_hd5 said:
I managed to pull the system.img to my folder of the phone. I can see the file, but I get an error when copying it to the PC. I used the following code
When trying to copy by using adb pull , he says I 'm not allowed . The file is in the / sdcard / .
Click to expand...
Click to collapse
type this command in adb shell prompt:
Code:
chmod 777 /data/media/0/system.img
Agimax said:
type this command in adb shell prompt:
Code:
chmod 777 /data/media/0/system.img
Click to expand...
Click to collapse
That worked! But did this command directly from send_command.exe in download mode , for using the adb he said he did not have permission. Now I can only learn edit the system.img :fingers-crossed:
Hey guys.
This way is super risky, a much saner way would be to
1. backup
2. Flash back down to Lollypop (which I managed on an LG G4 815L),
3. then run what ever you want
4. flash back.
Related
tried to install clockwork recovery and Im getting a FATAL ERROR The MD5sum of the installed recovery and the stored MD5sum do not match! DO NOT REBOOT YOUR PHONE Please contact TheCubed ASAP! So any help here would be appreciated.
I used the new one click root for ginger bread which included the Revo toolkit and i tried to install clockwork recovery using 4.0.0.2-pr1, after it failed with the aboved message i tried the revostock option and got the same message, so what do i do now?
please help me TheCubed!
leppricon said:
tried to install clockwork recovery and Im getting a FATAL ERROR The MD5sum of the installed recovery and the stored MD5sum do not match! DO NOT REBOOT YOUR PHONE Please contact TheCubed ASAP! So any help here would be appreciated.
I used the new one click root for ginger bread which included the Revo toolkit and i tried to install clockwork recovery using 4.0.0.2-pr1, after it failed with the aboved message i tried the revostock option and got the same message, so what do i do now?
please help me TheCubed!
Click to expand...
Click to collapse
Try the 4.0.0.2-pr1 again and again until it goes through. DO NOT REBOOT YOUR PHONE UNTIL IT SUCCEEDS, IT WILL RESULT IN YOU BEING STUCK IN FASTBOOT!!!!!
Try deleting mlk file and reinstalling recovery
Sent from my VS910 4G using XDA App
Installed rom manager
I installed rom manager to use to back up phone it rebooted to run the back up and it got stuck in fast boot, so i did some searching and found the page on fixing that. i used the second posters method instead of thecubed (because he said it was easier and thecubed agreed) and now all i get is an lg start screen. do not follow the other guys post it is for another phone completely i had to find it out the hard way. so any ideas on how i can get back to working phone?
The file you deleted was the mmcbik0p8 backup found on your ext card. When reinstalling the recovery CWM should have rewritten it with the correct version.
Try removing your card and mounting it on a pc go in and manually delete file and try to boot the phone. I had to do this to make my revolution boot.
This is how i fixed it
adrenaline_rush said:
Its not hard to fix at all, you will have to install the Java JDK, Android SDK, and three files AdbWinApi.dll, fastboot.exe, and CWMrecoveryrevolution.img which is the clockwork recovery for our phone.
Here are the files in .rar format.
http://www.mediafire.com/?eb3219cy0lbc71m
Android SDK
Java JDK
The first version should work
1. Install the Android SDK to your C: drive. Make sure the SDK and all the files are in C:\androidSDK. This will make things easier later.
2. Open the SDK and install the additional AndroidSDK platform tools package
3. Install the Java JDK
4. Unzip the .rar to c:/androidSDK/tools
5. Open command prompt, start> type "cmd"> press enter
6. Plug in phone
6. Assuming you placed everything in the right folders, type the following into the command prompt
Code:
cd c:/androidSDK/tools
7. You should now be in the correct folder, paste this command next:
Code:
fastboot erase recovery
then:
Code:
fastboot flash recovery CWMrecoveryrevolution.img
If that succeeds then type the final command:
Code:
fastboot reboot
Hopefully this works and is understandable
Click to expand...
Click to collapse
Don't work
Yeah this method don't work any more I tried yesterday and today with the revolution file. Fast boot does not find the phone. Cmd is <waiting for device>. Going to Verizon tomorrow to get new phone.
Edit: why it doesn't work is because I used the easy method that the other user posted, i did not check the phone version of the flash file, so now my phone has the wrong firmware on it and wont boot. Also it does not get recognized by my pc.
leppricon said:
Yeah this method don't work any more I tried yesterday and today with the revolution file. Fast boot does not find the phone. Cmd is <waiting for device>. Going to Verizon tomorrow to get new phone.
Edit: why it doesn't work is because I used the easy method that the other user posted, i did not check the phone version of the flash file, so now my phone has the wrong firmware on it and wont boot. Also it does not get recognized by my pc.
Click to expand...
Click to collapse
You tried the volume up + power to get to the recovery?
Tried that too.
The only way the Vol. up and power button works if I have the battery out and the usb hooked up, and then the screen says do not detach download in progress. I left it this way for about two hours thinking it would magically fix it self but it didn't. Called Verizon about an hour ago and I going to get my new phone in the afternoon tomorrow. they over-nighting it to me, they said any new tech with 4g they try to get it fixed as fast as possible. I then asked when 4g would be coming to my area he said spring of 2013... lol
Oh, you could have flashed the .tot system file over, but I guess it does take some time to get the program set up, and they're already replacing it..
Tried
I had all the above programs installed and working properly, that is how i got to a non-working phone, I flashed it with the wrong firmware which bricked it. Its not detected in any of the programs because all the programs are looking for a revo and i flashed to something else.
This was posted in the revo fastboot fix thread, I followed it and it bricked my phone.
hello everyone, im pretty sure i was the first one to run into this issue since it happened twice on two different phones. but for an extremely easy fix just look here, believe me it doesn't get any easier than this. this is another way it was explained, but both are pretty much the same. im only posting this in case someone doesn't understand the directions posted by thecubed, not saying the ones i post it are better, just explained differently, not trying to step on anyone's shoes here http://forum.xda-developers.com/show....php?t=1088046
Last edited by zr0ko0l; 23rd June 2011 at 03:03 AM.
this is the reply from thecubed: Dont' worry about my toes
If you've got a better explanation, go for it! I'm not the best at writing instructions.
Still no CWM
I rooted my Revo using adb and zergrush. I'm running v6 and cannot get CWM to work using adb, RevoToolKit or even on a command line on the phone itself. So far all I've done is reload my phone. It stays rooted, but no CWM. Md5's all check out on mmcblk0p14 before I restart, using adb and a terminal on the phone. The checksum is right when I dl the recovery-cwm-pr1.img in the zip, also.
I did do an OTA update after I rooted. Could that be the problem? Should I unroot and reroot?
meandmine said:
I rooted my Revo using adb and zergrush. I'm running v6 and cannot get CWM to work using adb, RevoToolKit or even on a command line on the phone itself. So far all I've done is reload my phone. It stays rooted, but no CWM. Md5's all check out on mmcblk0p14 before I restart, using adb and a terminal on the phone. The checksum is right when I dl the recovery-cwm-pr1.img in the zip, also.
I did do an OTA update after I rooted. Could that be the problem? Should I unroot and reroot?
Click to expand...
Click to collapse
Why run V6 when V7 (aka GingerBread) is out?
meandmine said:
I rooted my Revo using adb and zergrush. I'm running v6 and cannot get CWM to work using adb, RevoToolKit or even on a command line on the phone itself. So far all I've done is reload my phone. It stays rooted, but no CWM. Md5's all check out on mmcblk0p14 before I restart, using adb and a terminal on the phone. The checksum is right when I dl the recovery-cwm-pr1.img in the zip, also.
I did do an OTA update after I rooted. Could that be the problem? Should I unroot and reroot?
Click to expand...
Click to collapse
DId you manually use adb and Zergrush or use a different method? Did you use my all in one package with the root.bat? More info would be greatly appreciated.
Issues activating 4G LTE
Hello all,
First post so woot! but, kind of bad news at the same time. My friend and I were rooting/CWM'ing/ROM'ing his phone and we hit this road block. Everything went find up to the flashing of Gingervolt. It boots up and starts the initial setup sequence, but after the step where it ask for language, it sits and spins it's wheels for a while before saying that it cannot find the SIM card. There is also a small SIM card icon with a question mark next to the signal bar meter. This step is keeping us from being able to move forward and was wondering if there is any hope to get this thing to activate.
Things we've tried:
1) Reboot, restore, wiped all the caches
2) Did a nandroid restore of before we flashed it with Gingervolt
3) Downloaded a stock/rooted ROM (and received the same results)
4) Calling Verizon's activation hotline (told us nothing)
5) Taking out/Putting back the SIM card and seeing if that maybe would reset something. (I guess not)
It would be really cool if I could figure this out so he doesn't have to bring it in to big red :3
Thanks and you all rock!
canti-sama
cantibot said:
Hello all,
First post so woot! but, kind of bad news at the same time. My friend and I were rooting/CWM'ing/ROM'ing his phone and we hit this road block. Everything went find up to the flashing of Gingervolt. It boots up and starts the initial setup sequence, but after the step where it ask for language, it sits and spins it's wheels for a while before saying that it cannot find the SIM card. There is also a small SIM card icon with a question mark next to the signal bar meter. This step is keeping us from being able to move forward and was wondering if there is any hope to get this thing to activate.
Things we've tried:
1) Reboot, restore, wiped all the caches
2) Did a nandroid restore of before we flashed it with Gingervolt
3) Downloaded a stock/rooted ROM (and received the same results)
4) Calling Verizon's activation hotline (told us nothing)
5) Taking out/Putting back the SIM card and seeing if that maybe would reset something. (I guess not)
It would be really cool if I could figure this out so he doesn't have to bring it in to big red :3
Thanks and you all rock!
canti-sama
Click to expand...
Click to collapse
Was 4g turned on when you flashed? If nothing else you can flash the zv7 tot file through lgnspt.
Thanks so much for your quick reply,
I think that is going to be my next option. Thanks for reassuring me that is the right direction! And yes, I did have 4g (It was called LTE, I think it's the same thing.) enabled before flash.
cantibot said:
Thanks so much for your quick reply,
I think that is going to be my next option. Thanks for reassuring me that is the right direction! And yes, I did have 4g (It was called LTE, I think it's the same thing.) enabled before flash.
Click to expand...
Click to collapse
What version were you on before you flashed Gingervolt? If you were on v4 or v6 it will do that.
Sent from my Gingervolt-ed VS910 4G using xda premium
I rooted it with adb following root.bat. I run linux and am a terminal junkie. The rooting went fine. I then dl'ed recovery-cwm-pr1.img and adb'ed it over to the sdcard, ran all the checksums, from adb and on a root terminal on the phone. Then from adb, moved the image file to block mmcblk0p14, ran checksums again from both adb and the terminal on the phone. They both checked out fine, again.
After reboot, it just wiped, no CWM. It might be a permissions problem. I see no execute bit set. Should it be?
This is a response to post #14. I meant to post this with a quote. Instead, I posted a quick reply. Sorry.
meandmine said:
I rooted it with adb following root.bat. I run linux and am a terminal junkie. The rooting went fine. I then dl'ed recovery-cwm-pr1.img and adb'ed it over to the sdcard, ran all the checksums, from adb and on a root terminal on the phone. Then from adb, moved the image file to block mmcblk0p14, ran checksums again from both adb and the terminal on the phone. They both checked out fine, again.
After reboot, it just wiped, no CWM. It might be a permissions problem. I see no execute bit set. Should it be?
Click to expand...
Click to collapse
Not a permission problem, there are a couple of files in there that have to be removed otherwise it blocks it from booting into cwm with the key press combo. You have to boot into cwm using quick boot or the reboot into recovery option in the revotoolkit menu. If you flash GingerVolt you will then have reboot and recovery in the power menu, but also will be able to enter recovery through the button combo.
You will have to push the recovery image again first though.
I will donate to the individual that unbricks my bionic...Plz a lil desperate!!
Hmm.. Maybe some more info. What were you doing when you bricked it? Any of the leaked updates installed?
djr4x4 said:
Hmm.. Maybe some more info. What were you doing when you bricked it? Any of the leaked updates installed?
Click to expand...
Click to collapse
i was back on 886 with updated kernel and radio. wanted to flash the ota but kept failing due to kernel. tried flashing the ota in stock recovery then in cwm to no avail. decided to format somethings in advanced just to see if it would help flash ota but no. after that i rebooted and bam! bricked. thing is i have been in this situatuation before and nothing would restore me except released and 4ever root but now nothing works. no phone going on 24 hours now...
Did the same thing. Used this method. if you can get to the fast boot by holding power and vol down (or power and volume up and down, then selecting fast boot) it will work
http://www.addictivetips.com/mobile/unbrick-motorola-droid-bionic-with-rsd-lite-5-5-guide/
netslum said:
Did the same thing. Used this method. if you can get to the fast boot by holding power and vol down (or power and volume up and down, then selecting fast boot) it will work
http://www.addictivetips.com/mobile/unbrick-motorola-droid-bionic-with-rsd-lite-5-5-guide/
Click to expand...
Click to collapse
rsd didnt work for me ever...i want to try it again but it says that the file is not supported...
got it but still a no go. it fails everytime right away
Is there anyway to flash the fxz file without rsd??maybe fastboot??but it needs to be in IMG format right? anybody?
You can flash individual files from that pacjage in fastboot. Try this.
Fastboot flash /system system.img
Make sure those files are in same folder as fastboot, you have the right drivers and ur in fastboot mode on phone. Do this for every file it will let u. keep ur money tho if this works im not on this forim to get paid. Worse comes to worse pm me a phone number and ill step u thru it over phone.
Sent from my DROID BIONIC using XDA App
Here's some general tips for making RSD Lite work for you. RSD Lite is the only tool that knows how to manipulate FXZ files, as it's Motorola's proprietary file format.
(1) All the files you should need (Either RSD Lite or Fastboot) will come from here: http://briefmobile.com/droid-bionic-receives-fastboot-recovery-files
(2) Running the 32-bit version of the Motorola drivers is recommended. RSD Lite is a native 32-bit app and has a better chance of playing nice if 32-bit Motorola drivers are installed.
(3) When running RSD Lite on Windows Vista or Windows 7, it is also recommended that when you open it that you right-click and choose "Run As Administrator".
(4) After installing the drivers and RSD Lite, reboot and then plug in your Bionic AFTER opening RSD Lite.
From there, you make sure that you start your Bionic in bootloader (aka fastboot) mode and then RSD Lite shouldn't have a problem detecting the device so you can flash in the FXZ file. The best version to use in your situation is the full one that's 685MB.
This is what you need. I personally don't use rsdlite.
http://forum.xda-developers.com/showthread.php?t=1279825
You will boot your phone into fastboot mode then flash it using this utility. Option 1 is what you need to use.
You can also try this: http://droidmodderx.com/bionic/too-easy-unbrick-bionic-with-oneclick-fastboot-restore/
Sent from my DROID BIONIC using Tapatalk
Remember to hit the "Thanks" button when someone helps you!
Terri M said:
You can also try this: http://droidmodderx.com/bionic/too-easy-unbrick-bionic-with-oneclick-fastboot-restore/
Sent from my DROID BIONIC using Tapatalk
Remember to hit the "Thanks" button when someone helps you!
Click to expand...
Click to collapse
i have tried all of those and still no luck. all i can think of is to flash the whole fxz file in fastboot. but it needs to be in .IMG format.
follow the steps in the first post of this thread. should get you back going.
http://www.mydroidworld.com/forums/droid-bionic-forum/9800-how-get-your-phone-back-upgrade-path.html
rgb2448 said:
follow the steps in the first post of this thread. should get you back going.
http://www.mydroidworld.com/forums/droid-bionic-forum/9800-how-get-your-phone-back-upgrade-path.html
Click to expand...
Click to collapse
did this multiple times but heck ill try it again...
brandonaspencer said:
did this multiple times but heck ill try it again...
Click to expand...
Click to collapse
Can you get in fastboot mode? Does it say flash failed? What did you format?
i tried to flash the ota. no go. formatted webtop. stuck in ap mode. says flash failure. at the bottom says invalid sp data and invalid cg webtop. wont flash anything...
You need to use the moto-fastboot.exe and flash the stock webtop partition back to your phone. That is a hacked version of fastboot that supports larger than 256MB partition sizes and will restore your webtop so the phone can boot.
You finally gave enough information about what you actually deleted/formatted and the exact error was so that you could be helped...congrats!
Hint: "moto-fastboot flash webtop grfs.img" from a directory that contains the moto-fastboot.exe and the 2 required .dll files and the grfs.img from the original FXZ.
cellzealot said:
You need to use the moto-fastboot.exe and flash the stock webtop partition back to your phone. That is a hacked version of fastboot that supports larger than 256MB partition sizes and will restore your webtop so the phone can boot.
You finally gave enough information about what you actually deleted/formatted and the exact error was so that you could be helped...congrats!
Hint: "moto-fastboot flash webtop grfs.img" from a directory that contains the moto-fastboot.exe and the 2 required .dll files and the grfs.img from the original FXZ.
Click to expand...
Click to collapse
THank you!
http://dl.dropbox.com/u/7632904/moto-fastboot-win32.zip
That is the moto-fastboot.exe and dll files you need.
I already gave you the syntax to use it above and you already have the FXZ so just put them all together in a folder with the grfs.img and navigate to that folder from command prompt once the phone is booted in fastboot mode and use the command above.
It will proceed to flash the grfs.img in 5 256MB chunks and a 6th smaller chunk and then use moto-fastboot reboot and it should boot normally if you haven't messed up anything else in the meantime.
Good luck!
cellzealot said:
http://dl.dropbox.com/u/7632904/moto-fastboot-win32.zip
That is the moto-fastboot.exe and dll files you need.
I already gave you the syntax to use it above and you already have the FXZ so just put them all together in a folder with the grfs.img and navigate to that folder from command prompt once the phone is booted in fastboot mode and use the command above.
It will proceed to flash the grfs.img in 5 256MB chunks and a 6th smaller chunk and then use moto-fastboot reboot and it should boot normally if you haven't messed up anything else in the meantime.
Good luck!
Click to expand...
Click to collapse
Sir you are a genuis and a scholar! you know there are two different fastboot recoveries?? I needed exactly what you said, so where can I send you the $25?
brandonaspencer said:
Sir you are a genuis and a scholar! you know there are two different fastboot recoveries?? I needed exactly what you said, so where can I send you the $25?
Click to expand...
Click to collapse
Keep it! Learn how to ask better questions with more complete information and tell everyone else to do likewise and you will save us all far more valuable time and effort...seriously.
Happy holidays!
Oh and also share the knowledge you get with others and use the thanks button...it's what this forum is for.
Thanks for the offer, but I'd really rather you just did as I suggested and enjoy your phone and learn to understand it better.
Win, win!
I slept in late or I would have answered, but Cellzealot definitely explained it well.
I had rooted my n6 and than went on to flash cm12 on it .... today it wanted me to update it so i download it and it gives me and option to update....phone reboots now i cant tun it off nor it would go past the google screen. Help please .... is this what a soft brick is ? I tried recovery but ..it only goes upto 35% and the phone reboots for some reason
darshilshah87 said:
I had rooted my n6 and than went on to flash cm12 on it .... today it wanted me to update it so i download it and it gives me and option to update....phone reboots now i cant tun it off nor it would go past the google screen. Help please .... is this what a soft brick is ? I tried recovery but ..it only goes upto 35% and the phone reboots for some reason
Click to expand...
Click to collapse
you have root, you cant update. i mean, itll try and all. but it won't update. if it wont boot back up normally(press the power button for 20 seconds), then youll have to flash the factory img and reroot.
simms22 said:
you have root, you cant update. i mean, itll try and all. but it won't update. if it wont boot back up normally(press the power button for 20 seconds), then youll have to flash the factory img and reroot.
Click to expand...
Click to collapse
Yes i am actuallly trying to do it...my bootloader is unlocked too....but when I try to run flash-all.bat file like the HOW TO ... it doesnot work . Please help me with that . What could i have been doing wrong..My vomputer keeps on saying fastboot is not a valid command
darshilshah87 said:
Yes i am actuallly trying to do it...my bootloader is unlocked too....but when I try to run flash-all.bat file like the HOW TO ... it doesnot work . Please help me with that . What could i have been doing wrong..My vomputer keeps on saying fastboot is not a valid command
Click to expand...
Click to collapse
are you in tbe bootloader? did you start fastboot first?
simms22 said:
are you in tbe bootloader? did you start fastboot first?
Click to expand...
Click to collapse
Ok i got it .... I had to excess the file that had fastbootloader command in it .... Oh well w.e it is working now.... atleast i am learning
Thanks for the help good sir
For future reference, you may need to run the fastboot commands manually. Copy the .img files to your fastboot folder and hold shift while you right click and tell it to open command window from here. Enter the commands in the .bat file 1 by 1. If you get the "No system img file" or error of the sort, google it. I believe it was just using a 7zip program to extract the needed file from one of the zips included in the factory img. This is all of the top of my head, so i'm sorry if i'm a bit off on some of it. As everyone will say, search the forums for the exact method. Good luck and hope you don't have to use it!
THIS IS OLD OUTDATED METHOD AND WILL HAVE NO SUPPORT.
SEE AUTOPRIMES THREAD FOR CURRENT METHOD.
https://forum.xda-developers.com/showthread.php?t=3308227
**************
Here's my "One Click" method to get TWRP onto the G4 H811.
Special thanks to the following:
**Originally script written and tools by avicohh, modified by MicroMod777 to work only on H811.
**Special thanks to Manh_IT and RenaKunisaki for help getting correct flash commands.
**Special thanks to Unjustified Dev for TWRP.
**Special thanks to Team Codefire and vn_mobile for root.
PREREQUISITES:
**Must be on T-Mobile USA LG G4 H811 10H. WILL NOT WORK ON 10N. DO NOT DOWNGRADE TO 10H OR YOU WILL BRICK.
**Must have LG drivers installed and USB debugging enabled
**Windows computer
**OEM Unlocked in Developer Options.
Instructions:
Step 1: Plug phone to computer.
Step 2: Unzip H811-One-Click.zip
Step 3: Press CLICK-HERE-LG-G4-H811-UNLOCK-TWRP.bat to begin
Step 4: Phone will reboot a few times
Step 5: Pull battery after 1 minute only when on screen instructions say so.
Downloads:
****WARNING****ONLY FOR USA T-MOBILE G4 H811****YOU WILL BRICK****WARNING****
---->H811-One-Click.zip
****WARNING****ONLY FOR USA T-MOBILE G4 H811****YOU WILL BRICK****WARNING****
MD5: 7640484c4842cb883a702d0e09d89c9e
Issues: This might take a few tries to run if the LG drivers don't fully install in download mode.
***If you still can't get it to work, uninstall all LG Drivers, reboot and install drivers from here: LG drivers
MANUAL MODE:
Step 1: Copy recovery.img to your internal storage.
Step 2: Pull battery, put back in. Press and hold Volume up and plug cable in. (Enter Download Mode)
Step 3: On your computer open up your Device Manager and look for:
**Ports (COM &LPT)
****LGE Mobile USB Serial Port (COM?)
Look for the port number in COM#! ?=#.
Example:LGE Mobile USB Serial Port (COM3). So mine is port 3.
Step 4: In your One-Click folder press Shift/Right-Click-Mouse and press "Open Command Window Here".
Step 5: Type Send_Command.exe \\.\COM? Make sure the ?=Port number from Step 2.
Example. Mine is Send_Command.exe \\.\COM3
Step 6: Type "id" without quotes and make sure this comes up: uid=0(root) gid=0(root) context=u:r:recovery:s0
Step 7: WARNING, IF YOU GET THIS PART WRONG OR DON'T USE H811 YOU CAN BRICK!
*****Type Flash command only for H811:
dd if=/data/media/0/recovery.img bs=8192 seek=35840 count=5120 of=/dev/block/mmcblk0
Step 8: Type: LEAVE
**Phone will reboot
DONE.....
Enter TWRP:Must be OEM Unlocked in Developer Options.
**In ADB: adb reboot recovert
or...
**Pull battery, put back in. Press and hold volume down/power. When LG Logo appears only let go power for a second and then press again till factory reset screen appears. Do factory reset to boot into TWRP. If you don't see TWRP run program again.
******************************************
To get root flash from TWRP:
Root SuperSU.zip
http://forum.xda-developers.com/showthread.php?t=1538053
Very Nice. Are you using the same TWRP that is in the Original Development forum? Just curious to see if there are any changes such as time fix.
Awesome sauce! First thing I'll do when I get my G4 tomorrow.
for your coffee fund[emoji6]
Transaction ID:38Y91835CE493025B
Sent from my Nexus 5 using Tapatalk
lancemoreland said:
Very Nice. Are you using the same TWRP that is in the Original Development forum? Just curious to see if there are any changes like maybe time fix.
Click to expand...
Click to collapse
Same one, just repackaged for one click!
mawells787 said:
Awesome sauce! First thing I'll do when I get my G4 tomorrow.
for your coffee fund[emoji6]
Transaction ID:38Y91835CE493025B
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Sweet! Thanks so much!
so, i'm a little confused.....do you have to use low effort root first or do you just put your phone in download mode then run this script.?then by installing super su you will gain root?sorry i am so computer illerate.i have followed the low effort root page since day 1, have rooted other phones but like i said ...just not up to speed transferring files,running commands etc. so i have held off trying to root myself even though i am pretty sure i understand the directions.just wondering if this way might be easier,thx in advance for any help in clarifying this for me.
buckless said:
so, i'm a little confused.....do you have to use low effort root first or do you just put your phone in download mode then run this script.?then by installing super su you will gain root?sorry i am so computer illerate.i have followed the low effort root page since day 1, have rooted other phones but like i said ...just not up to speed transferring files,running commands etc. so i have held off trying to root myself even though i am pretty sure i understand the directions.just wondering if this way might be easier,thx in advance for any help in clarifying this for me.
Click to expand...
Click to collapse
No, you don't need low effort root. This is essentially the Nexus way. Just follow instructions and it will flash TWRp. Once you successfully reboot into TWRP. Download SuperSU.zip and flash it and you have root, it's very easy.
Sent from my Nexus 5 using Tapatalk
buckless said:
so, i'm a little confused.....do you have to use low effort root first or do you just put your phone in download mode then run this script.?then by installing super su you will gain root?sorry i am so computer illerate.i have followed the low effort root page since day 1, have rooted other phones but like i said ...just not up to speed transferring files,running commands etc. so i have held off trying to root myself even though i am pretty sure i understand the directions.just wondering if this way might be easier,thx in advance for any help in clarifying this for me.
Click to expand...
Click to collapse
If you want TWRP to flash rom's then you want this!
But you can also use this to get root, by flashing the SuperSu.zip from TWRP. This is way easier than having to download a 5gb system.img, and manually running all the commands for root in the other root thread.
mawells787 said:
No, you don't need low effort root. This is essentially the Nexus way. Just follow instructions and it will flash TWRp. Once you successfully reboot into TWRP. Download SuperSU.zip and flash it and you have root, it's very easy.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks for that good explanation! Guess you posted just before I did!
I just hope no non-H811 person tries to flash this and bricks their device. I put a big warning on OP. But as always somebody always doesn't read OP.
MicroMod777 said:
Thanks for that good explanation! Guess you posted just before I did!
I just hope no non-H811 person tries to flash this and bricks their device. I put a big warning on OP. But as always somebody always doesn't read OP.
Click to expand...
Click to collapse
Anytime. You can only lead a horse to water...
Sent from my Nexus 5 using Tapatalk
thank you both for the quick response.i downloaded the twrp zip ,and opened it with 7 zip,i do have drivers installed and adb enabled and the computer sees the phonealso on t-mo 811h.so was i correct toput the phone in download then open file and click on start?don't need to extract files etc?just don't wanna mess up then be back on here needing help, really want to be able to flash extreme.thx again
buckless said:
thank you both for the quick response.i downloaded the twrp zip ,and opened it with 7 zip,i do have drivers installed and adb enabled and the computer sees the phonealso on t-mo 811h.so was i correct toput the phone in download then open file and click on start?don't need to extract files etc?just don't wanna mess up then be back on here needing help, really want to be able to flash extreme.thx again
Click to expand...
Click to collapse
Just follow OP steps. It will go into download mode on its own.
Sent from my LG-H811 using Tapatalk
micromod...thx again.really appreciate your patience with me and your hard work putting this together, just one more question....dore or after i need to go into developers options and check bootloader unlock and if so before or after?
Do I put the zip file on the phone or the computer? I'm assuming the computer.
buckless said:
micromod...thx again.really appreciate your patience with me and your hard work putting this together, just one more question....dore or after i need to go into developers options and check bootloader unlock and if so before or after?
Click to expand...
Click to collapse
I checked it but not really sure its required.
Uncle Lizard said:
Do I put the zip file on the phone or the computer? I'm assuming the computer.
Click to expand...
Click to collapse
Computer.
Sent from my LG-H811 using Tapatalk
when I do one click recovery does't install and try to boot into to it and it says error
throonis said:
when I do one click recovery does't install and try to boot into to it and it says error
Click to expand...
Click to collapse
Were do you see error? Please explain more.
Sent from my LG-H811 using Tapatalk
"SOLVED" IT WORKED ,on boot screen left hand corner in white lines it says error
throonis said:
on boot screen left hand corner in white lines it says error
Click to expand...
Click to collapse
Do you have H811 and did the md5 match and did you get to the end of the program that said to pull battery?
Sent from my LG-H811 using Tapatalk
I had to run it twice on my phone and five times on my lady's phone, but after erasing data on both phones, trying to get into the recovery that wasn't installed, both are rooted and restored. Don't know why it went that way, but it doesn't much matter now that everything is well. Thanks again.
Uncle Lizard said:
I had to run it twice on my phone and five times on my lady's phone, but after erasing data on both phones, trying to get into the recovery that wasn't installed, both are rooted and restored. Don't know why it went that way, but it doesn't much matter now that everything is well. Thanks again.
Click to expand...
Click to collapse
I think it was the drivers needing to load in download mode. Each time you ran it did it say to pull battery when it finished?
Sent from my LG-H811 using Tapatalk
Hi Guys,
I found this file for unlocking the boot loader officially from the ASUS website, It can unlock the boot loader after the latest update too.
Please note
If you unlock your boot loader you will not be able to get OTA update but you can download and update your phone manually.
Also your warranty will be void.
Your Data (Storage) and phone data will be fully gone so please take a backup.
Try at your own risk!
Dear fusioncoast - can you please link us to the page on the Asus website where you downloaded the tool from?
https://www.asus.com/Phone/ZenFone-5Z-ZS620KL/HelpDesk_Download/
You need to select android as os on the page for the download to become visible.
Hey, you can;t get to the helppage for the 5z anymore I noticed, and this unlock tool just gives me an error (something about network).
Any other way to unlock the bootloader? Or maybe newer version is needed?
Anyone?
hgoor said:
Anyone?
Click to expand...
Click to collapse
Same like Me, and no anyone reply
Yeah that sucks. The phone is still perfect bit now just lying around
hgoor said:
Yeah that sucks. The phone is still perfect bit now just lying around
Click to expand...
Click to collapse
alisyahbana said:
Same like Me, and no anyone reply
Click to expand...
Click to collapse
Ok, so I ran in the same problem. I eventually bricked my phone (not totally, fastboot was still accesible) so I tried to flash this original Asus ROM back.
Everything was fine, the phone worked as original with Android 10.
But then I noticed that when I run the script of the file that I posted above, the state of my phone was unlocked for a couple of seconds, so I imediately closed the command prompt in Windows when that happend (after the script has rebooted the phone once) and it remained unlocked. Then I have proceeded with this guide and it worked like a charm, I have succesfully installed ArrowOS 13 back on my phone without Official Asus Unlocking tool APK.
STEPS FOR UNLOCKING BOOTLOADER WITHOUT ASUS APK
(IT WORKED FOR ME, I DO NOT TAKE ANY RESPONSABILITIES FOR ANY DAMAGE THAT MAY OCCURE)
Please back up any file before proceeding the steps. THEY DO REMOVE USER DATA!
1. Download this: SCRIPT_ASUS_ORIGINAL_UNBRICKING
2. Unzip it, and run flashall_AFT.cmd while in FASTBOOT mode (power+vol up).
Leave it still until is complete (let the script execute itself completly!! It may brick device if disconnected at wrong time)
3. Let the phone start until Welcome screen. You should see original Asus first time boot.
4. Go back in fastboot mode (power+vol up)
5. Run the script again but when you see that the phone is restarting and started back in fastboot with state UNLOCKED imediately close the command prompt window from the computer.
It may brick the device if disconnected at wrong time.
Disconnect it just at the right time as I said (after first reboot in fastboot + on the screen should say state UNLOCKED).
It's better to leave the script run itself again completly if you missed the first restart and repeat the process from step 4 again.
6. Now, the bootloader is unlocked, you can follow normal process: NOOB GUIDE
Please let me know if it worked for you too.
Thanks I will try it: if it doesn't work or brick my phone it's too bad I'll just have it recycled..
hgoor said:
Thanks I will try it: if it doesn't work or brick my phone it's too bad I'll just have it recycled..
Click to expand...
Click to collapse
Awesome. You are welcome! Please let me know if it worked for you too. I used latest TWRP (3.7.0) and ArrowOS 13 Official as the CustomROM.
MrBluie_ said:
Awesome. You are welcome! Please let me know if it worked for you too. I used latest TWRP (3.7.0) and ArrowOS 13 Official as the CustomROM.
Click to expand...
Click to collapse
I'll check that rom out too. Probably going to be this weekend or so.. but many thanks so far!
A new method to unlock bootloader without ASUS APK
Here is a factory ABL (aka bootloader) image file from Android 10 user raw package, it will make bootloader unlock untill flash back to the stock file.
1. download the attach file (ZS620KL_unlock_bootloader.zip)
2. reboot zenfone 5Z to fastboot mode
3. extract the zip file
4. make sure bootloader driver is properly installed and recognized in windows
5. execute 'flash_abl.bat' (it will wipe userdata after that!!!)
6. now your device is bootloader unlocked
hgoor said:
Thanks I will try it: if it doesn't work or brick my phone it's too bad I'll just have it recycled..
Click to expand...
Click to collapse
Did it work?
DemonsterNoob said:
Did it work?
Click to expand...
Click to collapse
Not have yet time for it. Will try today...
sabpprook said:
A new method to unlock bootloader without ASUS APK
Here is a factory ABL (aka bootloader) image file from Android 10 user raw package, it will make bootloader unlock untill flash back to the stock file.
1. download the attach file (ZS620KL_unlock_bootloader.zip)
2. reboot zenfone 5Z to fastboot mode
3. extract the zip file
4. make sure bootloader driver is properly installed and recognized in windows
5. execute 'flash_abl.bat' (it will wipe userdata after that!!!)
6. now your device is bootloader unlocked
Click to expand...
Click to collapse
I must be missing something because all it says is waiting for any device...
I also get a message waiting for device.
How do I get the batch file to run?
However, it worked, I just had to reinstall the drivers,
Thanks
There doesn't seem to be a way to unlock the bootloader for the moment.
MrBluie_ said:
Ok, so I ran in the same problem. I eventually bricked my phone (not totally, fastboot was still accesible) so I tried to flash this original Asus ROM back.
Everything was fine, the phone worked as original with Android 10.
But then I noticed that when I run the script of the file that I posted above, the state of my phone was unlocked for a couple of seconds, so I imediately closed the command prompt in Windows when that happend (after the script has rebooted the phone once) and it remained unlocked. Then I have proceeded with this guide and it worked like a charm, I have succesfully installed ArrowOS 13 back on my phone without Official Asus Unlocking tool APK.
STEPS FOR UNLOCKING BOOTLOADER WITHOUT ASUS APK
(IT WORKED FOR ME, I DO NOT TAKE ANY RESPONSABILITIES FOR ANY DAMAGE THAT MAY OCCURE)
Please back up any file before proceeding the steps. THEY DO REMOVE USER DATA!
1. Download this: SCRIPT_ASUS_ORIGINAL_UNBRICKING
2. Unzip it, and run flashall_AFT.cmd while in FASTBOOT mode (power+vol up).
Leave it still until is complete (let the script execute itself completly!! It may brick device if disconnected at wrong time)
3. Let the phone start until Welcome screen. You should see original Asus first time boot.
4. Go back in fastboot mode (power+vol up)
5. Run the script again but when you see that the phone is restarting and started back in fastboot with state UNLOCKED imediately close the command prompt window from the computer.
It may brick the device if disconnected at wrong time.
Disconnect it just at the right time as I said (after first reboot in fastboot + on the screen should say state UNLOCKED).
It's better to leave the script run itself again completly if you missed the first restart and repeat the process from step 4 again.
6. Now, the bootloader is unlocked, you can follow normal process: NOOB GUIDE
Please let me know if it worked for you too.
Click to expand...
Click to collapse
Worked like a charm for me ....... thanks a bunch for sharing this buddy ...... I am up and running with Arrow OS Android 13 on my Zenfone now ..... cheers
arkanoids said:
Worked like a charm for me ....... thanks a bunch for sharing this buddy ...... I am up and running with Arrow OS Android 13 on my Zenfone now ..... cheers
Click to expand...
Click to collapse
I couldn't do the process because my computer is Linux. I doing it from Windows, is there any need for a driver or something like that?
jak0n said:
I couldn't do the process because my computer is Linux. I doing it from Windows, is there any need for a driver or something like that?
Click to expand...
Click to collapse
You should have the adb platform tools for windows, connect your phone via usb and if you see phone's serial number as output for adb devices .... you are good to go, download the zip from above, follow the steps, for sure your Zenfone 5z would be unlocked ...... I had the latest firmware from asus website installed on my phone.