Related
[me176c/x] [K013] How to Root and update from .182 to Lollipop release
Stock ROMs up to v.182, all languages
ASUS' Download Center for the MeMo Pad 7 Link is now inaccessible as ASUS has redesigned their site. Even the support page for this tablet no longer has any links to download ROMs/updates. Sad panda. However, the ones below (ASUS' direct links included) still work! I am also in the process of reuploading/rehosting all of these as well, so stay tuned! So far everything is rehosted on Google Drive, and I plan to add more mirrors in the next couple of days. Pleasse bear with my snarkiness, I have been up late and it's now 4am. I must crash now.
Anyway........ Enjoy!!
WW 182 Full ROM
ASUS
Google Drive
WW OTA 191
ASUS
Google Drive
Google Drive (alt)
WW OTA 198
Google Drive
WW OTA 199
Mediafire
Google Drive
WW OTA 201
Google Drive
Zippyshare (ew)
WW Lollipop release
Mediafire
Google Drive
If you have other links to share, especially direct links from ASUS or non-GDrive hosts, please feel free to post them and I will credit you!
(Manually) Flashing Updates
Sometimes (read: often) an update will fail to install and reboot, and then the tablet will claim you're up to date when you check for updates (and we know it's full of crap). So you'll have to manually update yourself, and often, if only works if you start from .182 (or above), and flash each file in consecutive order. So here's how it works. Be sure to read over this before starting, to get an idea of what's in store for you. And to be safe, read it again. And to be doubly-sure, read it AGAIN (I cannot stress this enough).
Obligatory warnings:
Your warranty (expired by now, for sure) is now null and void. Regardless of whether you do this, it's no longer valid either way! :laugh:
I am not liable for any damages to your device (or your brain) that this process may cause. What you do to your device is on you, but if you play it safe and read this all carefully (and read it again! And AGAIN!), you shouldn't have any trouble.
Instructions:
First things first, install your drivers if you haven't already, and set up the Android Platform Tools (adb and fastboot exes and such, also attached to this OP). I highly suggest trying the Latest ADB Fastboot and USB Driver installer tool for Windows by @fawazahmed0 (or the various attached drivers below, if you still somehow have trouble with getting your PC to recognize this dinosaur of a device).
Next, before we continue, make sure USB debugging is enabled on your tablet. Go to Settings > About tablet, and tap on Build Number 7 times, and you'll see a toast, "You are now a developer!" Back out once and scroll down a bit, you'll now see Developer Options. Enter, and near the top you'll see an option for USB debugging, so check that box. Plug in your tablet to the PC, then open a command line interface (Hit Windows Key + R, then type in "cmd" and press enter). Type in "adb devices" (without quotes) and look at your tablet's screen for a prompt. Check the box and tap OK. Now. back in the command prompt, press up and enter on your keyboard (which will repeat that last command), and you'll see your tablet's serial number (a string of letters/numbers) and the word "device" if you did it correctly. Now you're ready for the next part.
1. Install the "RootZenFone-1.4.6.8r.apk" (attached to this OP, below) and run it. Beware, it may have some Chinese text/Engrish. It's fairly simple to figure out though, thankfully.
2. Turn on USB debugging if you haven't already (didn't you read this first? You're already slacking!).
3. Download the zip file(s) you need and rename it update.zip and transfer it to your tablet. Or copy all files to the tablet and rename them (with a file manager of your choice, see next step) as you go.
4. Download a file manager that has root access (such as MiXplorer or Root Browser).
5. Go to / (root) and manually copy your update.zip to the /data folder.
6. Download this command file (also attached below, in a zip) and copy it to the /cache/recovery folder. This must be present each time you install an update via this method, so leave a copy on your device.
7. Back to Windows Command Prompt, run the command, "adb shell" (without quotes, as before), wait a moment for it to reload the server, then type, "su" (again, without quotes). When you type in the "su" command for the first time, it will prompt for SuperSU access on your tablet, similar to how it requested the RSA perms with adb debugging. You must allow this root permission, or the following won't work!Now, type line by line (or better yet, copy and paste into the command prompt (a right click automatically pastes copied text into it, btw):
Code:
adb shell
su
echo 'boot-recovery ' > /cache/recovery/command
echo '--update_package=/data/update.zip' >> /cache/recovery/command
echo '--wipe_cache' >> /cache/recovery/command
echo 'reboot' >> /cache/recovery/command
reboot recovery
In brief, what this means is that you just ordered the "command" file to boot as a "recovery" in order to flash the update package you copied and renamed previously. Thus, the tablet will reboot and commence flashing. At least, I think that's what's happening here. Sorry, I'm no rocket surgeon. All I know, is that it works. However, if you are getting an error during the update process, as mentioned above, you will likely have to flash the next incremental update (the one just above your current version) instead and go from there, flashing each OTA in order using the coded commands above every time. Be sure to rename EACH ZIP to "update.zip" as you do this or the command cannot find the file! Yes, this sounds like a pain, and it is! But this has worked when the direct approach had failed.
Archive folder of everything needed, on Google Drive
ROOT ZenFone FAQ has a translated guide on how to fix ptotential issues with the root process.
Credits:
@plopingo and @jerbear294 for some of the links.
@lethardicus for finding most of the OTA zips again when one weirdly went missing @fawazahmed0 for the driver installer tool
@slayeralive for providing the basis for these instructions
Nice work sub
No need for adb just copy zip ti /data and command file to /cache/recovery and reboot to recovery
@GuyInDogSuit
Update
mirrored OTA 191, 198, 199, 201 & RootZenFone-1.4.6.8r apk => https://drive.google.com/folderview?id=0B5G23fyE72tnLS0yaXlUamVmcXc&usp=sharing#list
@GuyInDogSuit @slayeralive
I've try to update manually but it failed
how to flash .182 if I'm already in .191 ?
slayeralive said:
No need for adb just copy zip ti /data and command file to /cache/recovery and reboot to recovery
Click to expand...
Click to collapse
You don't have to do all the typing anymore?
GuyInDogSuit said:
You don't have to do all the typing anymore?
Click to expand...
Click to collapse
I've try, the tablet show android logo with no command on the screen after reboot without entering command
you did something wrong. command file is just txt file , and echo command in terminal is used for writing text in txt files.try to copy command file and reboot to recovery from terminal emulator with reboot recovery command. I created this method mainly for unbricking read post
http://forum.xda-developers.com/memo-pad-7/general/unbrick-asus-memopad-7-me176c-cx-t2970049
GuyInDogSuit said:
Thanks to @plopingo and @jerbear294 for some of the links.
Click to expand...
Click to collapse
OMG, I can't believe I JUST found this thread.
I have two of these tablets that I use as wall-mounted controllers for HA. One of them accepted the OTA updates and I was able to get it to .201 and keep it rooted. The other one, no matter what I tried, would not pull down anything above the .182 it was running.
This post has EVERYTHING you need to go from whatever all the way to .201 quickly and very easily. I installed 15 Second ADB, the ASUS ADB drivers, and ran through all of the updates. This, my friends, is awesomesauce.
HUGE THANK YOU to @GuyInDogSuit, @plopingo, and @jerbear294!
No luck
im on .182. When I move the files to the directories and reboot to recovery it fails. i get an error. Could this be becuase i had modified the build prop with xblast
peldo123 said:
im on .182. When I move the files to the directories and reboot to recovery it fails. i get an error. Could this be becuase i had modified the build prop with xblast
Click to expand...
Click to collapse
It could. I have made that last year and end up with a bricked tablet...
I had to make a complete reset.
I made a few tries until I get it right and found out that using certain terminal apps don't allow spaces between commands whilst others do... Try commands without breaks if you're using a terminal app. Or try temp cwm to update all the updates at once.
Can't get it to work
Every time i try this procedure this happens:
The tablet restarts after executing the adb shell step.
The tablet starts to update the firmware, but then suddenly throws an error. This happens with both the rom and the update files.
Anyone has any idea how to fix this?
Thx in advance!
kdlannoy said:
Every time i try this procedure this happens:
The tablet restarts after executing the adb shell step.
The tablet starts to update the firmware, but then suddenly throws an error. This happens with both the rom and the update files.
Anyone has any idea how to fix this?
Thx in advance!
Click to expand...
Click to collapse
Did you unzipped the file? You see, there's a zip inside another zip. Unzip the 1st time into root/data folder and rename it to update.zip!
This fixed it! That was a stupid mistake
kdlannoy said:
This fixed it! That was a stupid mistake
Click to expand...
Click to collapse
I'm glad it worked. I once made the same mistake.
I an on 191
there is no /cache/recovery folder
ls /cache
aplogs
backup
lost+found
modemcrash
Should i create /cache/recovery ?
mrseverin said:
I an on 191
there is no /cache/recovery folder
ls /cache
aplogs
backup
lost+found
modemcrash
Should i create /cache/recovery ?
Click to expand...
Click to collapse
Should be safe. I had a recovery folder, but nonetheless I don't see why it would harm anything.
I've had several Android devices. That was the easiest root I've ever done.
bravesoul said:
Did you unzipped the file? You see, there's a zip inside another zip. Unzip the 1st time into root/data folder and rename it to update.zip!
Click to expand...
Click to collapse
Could you give me a little more detail? I can't seem to make it work. Also, I don't have a "data" folder in /root? Can I create one? Thanks. Nevermind, I got it to work.
regele said:
Could you give me a little more detail? I can't seem to make it work. Also, I don't have a "data" folder in /root? Can I create one? Thanks. Nevermind, I got it to work.
Click to expand...
Click to collapse
"/root" isn't a folder. It's the source. For example. When you copy something to a hard drive you are copying to the root of that hard drive. The same goes with the root of the android. So. Copy the unzipped .zip file to root and to inside data folder. Rename it into update.zip and run the commands.
I realise you got it to work, but since this is a community I have explained to others.
Use it if you cannot flash with any flash tool (no root needed)
Note: Use this at your own risk! Use it as a last resort!
I'm not responsable for anything, this may not work with yours
Sorry for my poor english. I tested this method with MY bricked LG F320L, no root, no boot, no many partition pop up, partial
downloadMode (just download mode and can't see the USB logo nor S/W update) then can't flash with KDZ/TOT file,with adb mode
recovery when holding pwr and vol+ ( lucky ), with stock recovery but I have to write adb reboot recovery to get it
what you need (sorry, I'm too lazy to put a direct link, I found all of them in xda):
- Install driver for your device
- .kdz file of your model
- WindowsLGFirmwareExtract-1.2.5.0-Release
- Send_Command.exe and ports.bat (ports.bat is optional if you know the port where your device is plunged can be in LG_root.zip)
This methode needs that you can access to downloadmode or partial downloadmode like me (vol+ and plug USB cable)
1- Run WindowsLGFirmwareExtract
. browse your .kdz file with "Open" button
. click to "Extract KDZ" button and wait until finish
. browse the .dz file abd extract it with the appropriat button
. click to "Extract DZ" button and wait until finish
. select all system files and clic Merge system-bin (you will get system.img in another folder and you don't need all system****.bin)
. copy all files in same folder
2- change extension of all files .bin to .img and remove any numbers
example: aboot156.bin => aboot.img / 1-aboot.bin =>aboot.img
3- Push or copy all files to your device. You have to find also the laf.img of your device, sometime it's not in the KDZ file.
Maybe it's optional, but I'm not sure.
Remember the path, for this tuto I'm using adb and push all files to /data/local/tmp/
You can also copy all files with another method
4- Run Ports.bat
Double click ports.bat (This will give us the COM port in which our device is connected we are looking for the Diag port)
keep in mind the COM of \Device\LG*******DIAG*
5- Go to downloadMode
6- Run send_command.exe in command prompt
type: Send_Command.exe \\.\COM3 if COM3 is the port where your device is pluged
wait for #
flash all .img like this, replace NAME by the name of the file ex: aboot.img replace NAME by aboot
dd if=/data/local/tmp/{NAME}.img of=/dev/block/platform/msm_sdcc.1/by-name/{NAME}
ex: dd if=/data/local/tmp/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Except for backupGPT.img, I don't know what is it. Maybe in this partition:
dd if=/data/local/tmp/backupGPT.img of=/dev/block/platform/msm_sdcc.1/by-name/gpt
personally , I have not flashed this one
If you have finished type: LEAVE
Flash completed
Thank you guy, your tuto saved my device
santatralalaina said:
Use it if you cannot flash with any flash tool (no root needed)
Note: Use this at your own risk! Use it as a last resort!
I'm not responsable for anything, this may not work with yours
Sorry for my poor english. I tested this method with MY bricked LG F320L, no root, no boot, no many partition pop up, partial
downloadMode (just download mode and can't see the USB logo nor S/W update) then can't flash with KDZ/TOT file,with adb mode
recovery when holding pwr and vol+ ( lucky ), with stock recovery but I have to write adb reboot recovery to get it
what you need (sorry, I'm too lazy to put a direct link, I found all of them in xda):
- Install driver for your device
- .kdz file of your model
- WindowsLGFirmwareExtract-1.2.5.0-Release
- Send_Command.exe and ports.bat (ports.bat is optional if you know the port where your device is plunged can be in LG_root.zip)
This methode needs that you can access to downloadmode or partial downloadmode like me (vol+ and plug USB cable)
1- Run WindowsLGFirmwareExtract
. browse your .kdz file with "Open" button
. click to "Extract KDZ" button and wait until finish
. browse the .dz file abd extract it with the appropriat button
. click to "Extract DZ" button and wait until finish
. select all system files and clic Merge system-bin (you will get system.img in another folder and you don't need all system****.bin)
. copy all files in same folder
2- change extension of all files .bin to .img and remove any numbers
example: aboot156.bin => aboot.img / 1-aboot.bin =>aboot.img
3- Push or copy all files to your device. You have to find also the laf.img of your device, sometime it's not in the KDZ file.
Maybe it's optional, but I'm not sure.
Remember the path, for this tuto I'm using adb and push all files to /data/local/tmp/
You can also copy all files with another method
4- Run Ports.bat
Double click ports.bat (This will give us the COM port in which our device is connected we are looking for the Diag port)
keep in mind the COM of \Device\LG*******DIAG*
5- Go to downloadMode
6- Run send_command.exe in command prompt
type: Send_Command.exe \\.\COM3 if COM3 is the port where your device is pluged
wait for #
flash all .img like this, replace NAME by the name of the file ex: aboot.img replace NAME by aboot
dd if=/data/local/tmp/{NAME}.img of=/dev/block/platform/msm_sdcc.1/by-name/{NAME}
ex: dd if=/data/local/tmp/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Except for backupGPT.img, I don't know what is it. Maybe in this partition:
dd if=/data/local/tmp/backupGPT.img of=/dev/block/platform/msm_sdcc.1/by-name/gpt
personally , I have not flashed this one
If you have finished type: LEAVE
Flash completed
Click to expand...
Click to collapse
help please
santatralalaina said:
Use it if you cannot flash with any flash tool (no root needed)
Note: Use this at your own risk! Use it as a last resort!
I'm not responsable for anything, this may not work with yours
Sorry for my poor english. I tested this method with MY bricked LG F320L, no root, no boot, no many partition pop up, partial
downloadMode (just download mode and can't see the USB logo nor S/W update) then can't flash with KDZ/TOT file,with adb mode
recovery when holding pwr and vol+ ( lucky ), with stock recovery but I have to write adb reboot recovery to get it
what you need (sorry, I'm too lazy to put a direct link, I found all of them in xda):
- Install driver for your device
- .kdz file of your model
- WindowsLGFirmwareExtract-1.2.5.0-Release
- Send_Command.exe and ports.bat (ports.bat is optional if you know the port where your device is plunged can be in LG_root.zip)
This methode needs that you can access to downloadmode or partial downloadmode like me (vol+ and plug USB cable)
1- Run WindowsLGFirmwareExtract
. browse your .kdz file with "Open" button
. click to "Extract KDZ" button and wait until finish
. browse the .dz file abd extract it with the appropriat button
. click to "Extract DZ" button and wait until finish
. select all system files and clic Merge system-bin (you will get system.img in another folder and you don't need all system****.bin)
. copy all files in same folder
2- change extension of all files .bin to .img and remove any numbers
example: aboot156.bin => aboot.img / 1-aboot.bin =>aboot.img
3- Push or copy all files to your device. You have to find also the laf.img of your device, sometime it's not in the KDZ file.
Maybe it's optional, but I'm not sure.
Remember the path, for this tuto I'm using adb and push all files to /data/local/tmp/
You can also copy all files with another method
4- Run Ports.bat
Double click ports.bat (This will give us the COM port in which our device is connected we are looking for the Diag port)
keep in mind the COM of \Device\LG*******DIAG*
5- Go to downloadMode
6- Run send_command.exe in command prompt
type: Send_Command.exe \\.\COM3 if COM3 is the port where your device is pluged
wait for #
flash all .img like this, replace NAME by the name of the file ex: aboot.img replace NAME by aboot
dd if=/data/local/tmp/{NAME}.img of=/dev/block/platform/msm_sdcc.1/by-name/{NAME}
ex: dd if=/data/local/tmp/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Except for backupGPT.img, I don't know what is it. Maybe in this partition:
dd if=/data/local/tmp/backupGPT.img of=/dev/block/platform/msm_sdcc.1/by-name/gpt
personally , I have not flashed this one
If you have finished type: LEAVE
Flash completed
Click to expand...
Click to collapse
@santatralalaina
I'm in a similar situation like you. No download, fastboot or recovery and phone is not detected by Windows. As u said PARTIAL Download mode only. I'm not very good with adb also. Could you please guide me about force pushing of the .img files please! Where can I get send command.exe and ports.bat? Could you please attach some screen shot of Step:6. Renaming the file and command is bit confusing for me.
sms473 said:
@santatralalaina
I'm in a similar situation like you. No download, fastboot or recovery and phone is not detected by Windows. As u said PARTIAL Download mode only. I'm not very good with adb also. Could you please guide me about force pushing of the .img files please! Where can I get send command.exe and ports.bat? Could you please attach some screen shot of Step:6. Renaming the file and command is bit confusing for me.
Click to expand...
Click to collapse
Hi, Don't panic! Take a deep breath.
Firstly: What is your phone model?
Secondly: What happen when you plug your phone to your PC?
Finaly: What you have did to try unbricking you phone?
santatralalaina said:
Hi, Don't panic! Take a deep breath.
Firstly: What is your phone model?
Secondly: What happen when you plug your phone to your PC?
Finaly: What you have did to try unbricking you phone?
Click to expand...
Click to collapse
Hi..thanks for the reply....My phone is G2 F320L..Korean version with removable battery and SD card....I tried to install a non compatible ROM..got bricked with only fastboot...Then I try to flash aboot.bin..boot.bin..laf.bin..etc files (which I have extracted from the kdz) through fastboot...during flashing my phone was disconnecting and connecting back again...thats where all the problem started I guess. Now I dont have fastboot also. If i connect my phone to PC.. LG logo comes on the phone screen...on PC it try to detect as LGE android MTP devices and try to install the driver of the same. But the driver installation fails eventually.... At windows device manager it show as LGE Android MTP devices with error code 10...and showing connected to port:COM3....If I try to get in to the download mode..it get stuck at the (.............) download page...it is not going to the page with big USB picture...
My thinking is...Since the device manager is showing that it is connected at COM3.....Can I force flash the boot.img, aboot.img, laf.img etc files with "Send command.exe?
At least I can try to force flash right? If it is possible..may be I will be able to enter in to the download mode:fingers-crossed: Right? Where can I get this "Send command.exe" and how it works?
sms473 said:
My thinking is...Since the device manager is showing that it is connected at COM3.....Can I force flash the boot.img, aboot.img, laf.img etc files with "Send command.exe?
At least I can try to force flash right? If it is possible..may be I will be able to enter in to the download mode:fingers-crossed: Right? Where can I get this "Send command.exe" and how it works?
Click to expand...
Click to collapse
Hello,
It was easy to unbrick the fastboot but now... ok, you are stuck in LG LOGO but after no black screen? can you charge you battery? And if you try to go to RecoveryMode, what's happen? do you have multiple partitions and QHSUSB_DLOAD trying to be instaled? It's also easy to unbrick the QHSUSB and if it is the case, don't use send_command to flash manualy your device.
Maybe, you can force flash. You have to find a solution to push all .img files to your device. If you cannot use ADB, try to put the img files to sdcard.
you can found send_command.exe and ports.bat in this zip file, it's an utilities for having root on LG G2 :
LG_Root.zip
you can use all root command with it!
Added to index thread
[INDEX][LG G2] ROMs, Kernels, Guides and more
can this fix demigod crash handler? it has a partial download mode (located in drivers, but LG Flash Tool gets stuck in 4%)
I have a f320k, and because it died (i await u to answer me and tell me if its possible that it will fix it(
i am currently using a nearly dead battery nexus 5.
reply in ur free time
Well, I need help. how do i copy these files to my device? my device is not located in adb. cant i just flash the files from there place in my pc?
hi - I have t mobile d801 .it has boot loop - show lg logo and then the android robot and then lg logo again.
it does enter download mode(but with the 4 blue dots - but in the device manager cant install the drivers.
when the phone is plugged in to computer normally without download mode' it shows lge phone and drivers in device manager.
I tried to flash kdz bit stuck on 60%. it shows on phone download mode - but not show the firmware update logo.
what should I do?? when I d.mode not the regular d.mode - device isn't detected in pc. so I think this is my main problem.
try with srk tools no luck. its says waiting for device..is there any solution? thanks!
foxyfoxyblah said:
can this fix demigod crash handler? it has a partial download mode (located in drivers, but LG Flash Tool gets stuck in 4%)
I have a f320k, and because it died (i await u to answer me and tell me if its possible that it will fix it(
i am currently using a nearly dead battery nexus 5.
reply in ur free time
Click to expand...
Click to collapse
Hi!
As I known, LG G2 is unbrickable
This method is for last resort because I havn't complete documentation about this!
I've tested it with my own LG F320L only
Try to flash with TOT files or LGUP
Try to repair the download mode http://forum.xda-developers.com/showthread.php?t=2706590
Try to force the QHS_USB to appear then use the appropriate tools http://forum.xda-developers.com/lg-g2/general/file-unbrick-qualcomm-9006-qhsusb-t3056800
Try send_commande before shorting testpoint (it's less dangerous IN MY OPINION)
santatralalaina said:
Hi!
As I known, LG G2 is unbrickable
This method is for last resort because I havn't complete documentation about this!
I've tested it with my own LG F320L only
Try to flash with TOT files or LGUP
Try to repair the download mode http://forum.xda-developers.com/showthread.php?t=2706590
Try to force the QHS_USB to appear then use the appropriate tools http://forum.xda-developers.com/lg-g2/general/file-unbrick-qualcomm-9006-qhsusb-t3056800
Try send_commande before shorting testpoint (it's less dangerous IN MY OPINION)
Click to expand...
Click to collapse
I don't have ADB, so most of these i cant do.
im scared of touching the motherboard....
so im not shorting test point.
santatralalaina said:
Use it if you cannot flash with any flash tool (no root needed)
Note: Use this at your own risk! Use it as a last resort!
I'm not responsable for anything, this may not work with yours
Sorry for my poor english. I tested this method with MY bricked LG F320L, no root, no boot, no many partition pop up, partial
downloadMode (just download mode and can't see the USB logo nor S/W update) then can't flash with KDZ/TOT file,with adb mode
recovery when holding pwr and vol+ ( lucky ), with stock recovery but I have to write adb reboot recovery to get it
what you need (sorry, I'm too lazy to put a direct link, I found all of them in xda):
- Install driver for your device
- .kdz file of your model
- WindowsLGFirmwareExtract-1.2.5.0-Release
- Send_Command.exe and ports.bat (ports.bat is optional if you know the port where your device is plunged can be in LG_root.zip)
This methode needs that you can access to downloadmode or partial downloadmode like me (vol+ and plug USB cable)
1- Run WindowsLGFirmwareExtract
. browse your .kdz file with "Open" button
. click to "Extract KDZ" button and wait until finish
. browse the .dz file abd extract it with the appropriat button
. click to "Extract DZ" button and wait until finish
. select all system files and clic Merge system-bin (you will get system.img in another folder and you don't need all system****.bin)
. copy all files in same folder
2- change extension of all files .bin to .img and remove any numbers
example: aboot156.bin => aboot.img / 1-aboot.bin =>aboot.img
3- Push or copy all files to your device. You have to find also the laf.img of your device, sometime it's not in the KDZ file.
Maybe it's optional, but I'm not sure.
Remember the path, for this tuto I'm using adb and push all files to /data/local/tmp/
You can also copy all files with another method
4- Run Ports.bat
Double click ports.bat (This will give us the COM port in which our device is connected we are looking for the Diag port)
keep in mind the COM of \Device\LG*******DIAG*
5- Go to downloadMode
6- Run send_command.exe in command prompt
type: Send_Command.exe \\.\COM3 if COM3 is the port where your device is pluged
wait for #
flash all .img like this, replace NAME by the name of the file ex: aboot.img replace NAME by aboot
dd if=/data/local/tmp/{NAME}.img of=/dev/block/platform/msm_sdcc.1/by-name/{NAME}
ex: dd if=/data/local/tmp/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Except for backupGPT.img, I don't know what is it. Maybe in this partition:
dd if=/data/local/tmp/backupGPT.img of=/dev/block/platform/msm_sdcc.1/by-name/gpt
personally , I have not flashed this one
If you have finished type: LEAVE
Flash completed
Click to expand...
Click to collapse
i have flashed wrong firmware ..now my phone have same symptoms like urs with partial download mode and no recovery....but i m unable to push files via adb bcz adb debugging is not active and i m getting error that phone not found.....now what can i dooo...plz plz plzzzz help me
I just wrote and shared my experiences. Forcing the qshusb by shorting the right pins in the motherboard is the only solution if you cannot push the img files to your phone with adb, by sdcard, by MTP or something else
santatralalaina said:
I just wrote and shared my experiences. Forcing the qshusb by shorting the right pins in the motherboard is the only solution if you cannot push the img files to your phone with adb, by sdcard, by MTP or something else
Click to expand...
Click to collapse
and how to do that?
Thank you your topic was helped me to find a solution for my phone lg g3
I have done my best to make sure most of the LG G5s out there will work with LGUP.
DISCLAMER: first and foremost, I take NO responsibilities for the possibility of a bricked phone(none whatsoever). if you brick it, it's YOUR fault, not mine.
ALWAYS BACKUP YOUR DATA BEFORE YOU DO ANYTHING
now for the fun bit:
1. Download and extract the LGUP.zip file from here as it contains everything you'll need except the firmwares.
2. To install the drivers for the device, go to the Drivers folder located in LGUP, and select InstallUSB.exe for a 32-bit system, or InstallUSB64.exe for a 64-bit system.
3. Install LGUP_Lab_Frame_Ver_1_11 that is in the LGUP folder
4. Install either the G5x86.reg or the G5x64.reg depending on whether you have a 32 or 64 bit windows installed.
5. Put the "model" folder in the LG Electronics\LGUP folder which will be either in C:\Program Files or C:\Program Files (x86) depending on whether you have a 32 or 64 bit windows installed
6. Put phone in download mode ( Phone off, vol up while plugging in usb from PC), start LGUP
7. Make sure you see a com # and phone model and at the bottom where it says BIN, select it, at which point you should see 3 dot on the right, select it and choose the .tot or .kdz file listed for your device, then hit start and wait for the magic.
Devices supported:
A992
F700K
F700L
F700S
H820
H830
H831
H850
H850TR
H858
H860
H860N
H868
LS992
RS988
US992
VS987
If I have not listed your device, list the exact model name (i.e LGLS992) in the comments below and I will add it for download.
I give creds to autoprime for his good work. If I missed anyone, I am giving you credits and apologizing now for not mentioning you.
Sorry for a questions that may be dumb, but what is this Tool supposed to do?
Sent from my LG-H850 using Tapatalk
Just a program that lets you flash firmware files to the described phone models
gwolfu said:
Just a program that lets you flash firmware files to the described phone models
Click to expand...
Click to collapse
Any possibility of achieving root with this on locked bootloaders?
Sent from my SM-N900T using Tapatalk
ForgottenSolstace said:
Any possibility of achieving root with this on locked bootloaders?
Click to expand...
Click to collapse
From what I understand, as long as the stock firmware is published by LG or the carrier we can inject root.
Veliion said:
From what I understand, as long as the stock firmware is published by LG or the carrier we can inject root.
Click to expand...
Click to collapse
This only if the model support the fastboot oem unlock command.
Without an unlocked bootloader is not possible to obtain root on Marshmallow, the only way would be find an exploit.
Sent from my LG G5 using XDA Labs
A992 in OP is typo.. should be AS992 obviously.
New model you could add:
H820PR
H850K
Thank you!
can i install gapps using this tool？ i have a H868 chinese version, google services are not preinstalled .
Broken Link =(
This is exactly what I needed, but when I attempt to access it, the google drive link is 404'd
Any way we might could convince you to update the info? Thanks so much in advance for your time.
--AmorImpermissus
AmorImpermissus said:
This is exactly what I needed, but when I attempt to access it, the google drive link is 404'd
Any way we might could convince you to update the info? Thanks so much in advance for your time.
--AmorImpermissus
Click to expand...
Click to collapse
all in there
https://1drv.ms/f/s!Au9ppCUF0J7lgZpUFNW-cf8ot0EweA
gwolfu said:
all in there
https://1drv.ms/f/s!Au9ppCUF0J7lgZpUFNW-cf8ot0EweA
Click to expand...
Click to collapse
Thanks a bunch gwolfu. However, what I really need are the LG<model>_DLL.msi files. Specifically, I need it for the RS988. It was listed in the supported devices at the beginning, but can't find it =(
LGUP not working...
Please help.
LGUP not working
I tried all versions LGUP, drivers installed and still does not work.
I have a LG unit G5 Demo and Windows 7 x64.
Can you advise?
Thank you.
milennium said:
Please help.
LGUP not working
I tried all versions LGUP, drivers installed and still does not work.
I have a LG unit G5 Demo and Windows 7 x64.
Can you advise?
Thank you.
Click to expand...
Click to collapse
When you open "Settings" -> "General" tab -> "About phone" -> "Hardware info" what does it have for "Model number?"
Model number: LG-H850
OK looking at the screenshot, I'm wondering if somehow the install got messed up. If you go to:
c:\program files (x86)\LG Electronics\LGUP\Model
What are the contents?
Also, open powershell as an administrator (usually can just type "powershell" from an elevated command prompt) and run this command:
Get-ChildItem -recurse 'HKCU:\Software\LG Electronics\LGUP' | where-object { $_.Property -like "DLL*"}
Then copy/paste the results so I can see them =)
In regedit, go to:
HKCU:\software\LG Electronics\LGUP\Model
Contents is (screen A and B).
Question. They must be unlocked bootloader?
Because my LGG5 be unblocked (Demo Unit).
milennium said:
Contents is (screen A and B).
Question. They must be unlocked bootloader?
Because my LGG5 be unblocked (Demo Unit).
Click to expand...
Click to collapse
You should be able to use the LGUP tool regardless of whether or not you have an unlocked bootloader. You may not be able to flash every kind of *.tot file, but whether or not your phone's bootloader is unlocked will have nothing to do with that error you're getting.
What about the output of the powershell command:
Get-ChildItem -recurse 'HKCU:\Software\LG Electronics\LGUP' | where-object { $_.Property -like "DLL*"}
?
Here is the result Powershell command:
milennium said:
Here is the result Powershell command:
Click to expand...
Click to collapse
OK, so, do the following, and then try to run LGUP with the phone connected, and let's see if it works:
1. Create a blank notepad file
2. Save it as something like h850.reg to your desktop where you can find it easily.
3. With the file still open in notepad, copy/paste the info below info and then save it again.
4. Close the file, then double-click it from your desktop to import it.
I've also attached it as a *.txt file which you can just change the extension to *.reg if that's easier:
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\LG Electronics\LGUP\Model\H850]
"MODEL_NAME"="H850"
"DLL_PATH"="C:\\Program Files (x86)\\LG Electronics\\LGUP\\Model\\H830\\LGUP_H830.dll"
[HKEY_CURRENT_USER\Software\LG Electronics\LGUP\Model\LGH850]
"DLL_PATH"="C:\\Program Files (x86)\\LG Electronics\\LGUP\\Model\\H830\\LGUP_H850.dll"
"MODEL_NAME"="LGH850"
[HKEY_CURRENT_USER\Software\LG Electronics\LGUP\Model2]
[HKEY_CURRENT_USER\Software\LG Electronics\LGUP\Model2\H850]
"DLL_PATH"="C:\\Program Files (x86)\\LG Electronics\\LGUP\\Model\\H830\\LGUP_H850.dll"
[HKEY_CURRENT_USER\Software\LG Electronics\LGUP\Model2\LGH850]
"DLL_PATH"="C:\\Program Files (x86)\\LG Electronics\\LGUP\\Model\\H830\\LGUP_H850.dll"
Installing the H815 Nougat Stock [v29A] on the H818P.
5.1 Installation
1 - Download KDz from 5.1;
2 - Put the phone in download mode and open the LG UP;
3 - Load KDz into the program and start;
4 - I hope to connect, configure and depart for the next procedure.
Root process
1- Download all files;
3 - Download IMG from the V10C BRASIL system or V10D Brasil (check the version of your software), after downloading and downloading the IMG to the internal memory of the device.
4. Install the drivers (if you do not have one) and extract the LG_Root.zip to the LG Root folder;
5- On the device, enable USB Debugging in the Developer Options;
6- In the LG Root folder, right-click pressing shift and click Open Command Window here.
7- Connect the USB cable to the computer and allow debugging;
8- In the open command window type adb.exe devices, so if the device is connected the computer will inform in the window. Example: List of devices attached, LGH818P (letters and numbers), device;
9- Disconnect the USB cable and the device. With it off, press the volume more, plug into the USB port, the device will turn on Download Mode;
10- Go back to the folder, with the device already in Download Mode, double click on the Ports file, it will open another command window, copy the port number that appears in \ Device \ LGANDNETDIAG1 REG_SZ COMxx, note the xx because it is the number of the door, write down the number, then close the window that has been opened;
11- Go back to the command window that you had previously opened, in it copy and paste the command Send_Command.exe \\. \ COMxx and change the xx by the number of its port;
12- Still in the window, type id, a message will appear. Example: uid = (0) root gid = (0) root. If it does not, type again;
13- It's time for root, you should be sure now that you have copied the correct port and that the file from step 2 is in the internal memory. Enter the command
dd if=/data/media/0/system.rooted.H81510c-EU.img bs=8192 seek=55296 count=529920 of=/dev/block/mmcblk0
and hit Enter on your keyboard. It should take about a minute, wait until # appears.
14- After you finish, type LEAVE for your device to reboot. Root is done.
Installing Nougat
1 - Right after Root download the Flash Fire, and install it;
2 - Copy to rom for internal storage, compact even;
3 - Right after pressing the "+" and select the option "Flash ZIP or OTA";
4 - Ira appears to navigate the internal memory, select the rom;
5 - Then select the "Flash" option;
6 - It will restart and soon after starting the installation;
7 - Ready, now just wait;
NOTE: In the LG logo it will take a little, something from 3 to 5 minutes.
DOWNLOADS :
V10C_BRA_root.rar: https://mega.nz/#!Y1lQWDrY!ItgAfCNX7oO1XPLLS9hT3WLDi3MBQ0LOe6vPoMtut-I
V10D_BRA_ROOTED.zip: https://mega.nz/#!Ro8XVBqC!EDbYZ9weJj7Pn3ewLB9hEy6ZjGiRCX_igtt5kPZLADE
Drivers: http://www.lg.com/br/suporte/suporte-celular/lg-H818P
LG Root: https://mega.nz/#!4xNBAIiZ!TR9kHjYMaHKZLg2Fm8ceGffGTMiWSmP8Q0bBxuOkFxQ
Stock Rom: https://lg-firmwares.com/lg-h818p-firmwares/#firmwaresList
LG-H815_Official_v29A.
https://www.androidfilehost.com/?fid=817550096634794247
IF YOU WANT DOWNGRADE 7.0 TO 6.0
SEE ALL HERE
http://raspberryjuntopi.com.br/2017/10/13/off-downgrade-lg-g4-do-nougat-para-o-marshmallow/
https://www.youtube.com/watch?v=9Vk1TJ96eG4&feature=youtu.be
FILE H815 V20o Modded.kdz
you can drop from 7.0 to 6.0 and run the manual modem
The easiest way to get it manually (you need root):
Copy the IMG-file of the modem in the internal storage (do not rename it!)
on your computer, the command ADB line
Execute «adb shell» (without the quotes)
Lift the skin with the command su (again, without quotes)
Then execute the following commands:
dd if = / dev / zero of = / dev / block / platform / bootdevice / by-name / modem
dd if = / sdcard / modem_h818p_20h_gcc.img of = / dev / block / platform / bootdevice / by-name / modem
Finally, restart your phone and it should work.
modem_h818p_20g.img
https://mega.nz/#!e5snTbaL!BYplWw8MAyNFWJ0VrrA4UZjV0Ric3-RxIRUsELZjk1c
6.0
https://mega.nz/#!H8dnXDCL!hqA-yIN3dAeuqHm-H0KltL6rfTJfb0EpVcNJYkkr0GU
hi,
Can I Root & Flash that Nougat ROM on my G4 H818P that is currently on Marsmallow?
thanks
BoyBawang2 said:
hi,
Can I Root & Flash that Nougat ROM on my G4 H818P that is currently on Marsmallow?
thanks
Click to expand...
Click to collapse
NO. you lost signal.
If you try to Flash kdz file but it stops at 9% with error 0x2000 flashing fail .
Try replacing your LGUP dll with this one: LGUP_8994.dll
https://mega.nz/#!b51GGDLL!n42yqpAIaEbgbx8WkoB8DtDAERx3N8tsHhPkC_XDs5M
It's located in this directory:
C:\Program Files (x86)\LG Electronics\LGUP\model\8994
Or this one if you have a 32-bit windows pc:
C:\Program Files\LG Electronics\LGUP\model\8994
And then flash KDZ again
hochocnua said:
NO. you lost signal.
Click to expand...
Click to collapse
Thanks. Can I atleast succeed just on the Rooting part?
BoyBawang2 said:
Thanks. Can I atleast succeed just on the Rooting part?
Click to expand...
Click to collapse
No Root For Marshmallow and Nougat
Sent from my LG-H818 using Tapatalk
Hi, if i flash Nougat this way will I lost network (and dual sim)?
alitavas said:
No Root For Marshmallow and Nougat
Click to expand...
Click to collapse
Thanks. The instructions should have indicated that I should be in Lollipop first before going through the steps.
Future, can i flash firmware h818p normally?
BoyBawang2 said:
Thanks. The instructions should have indicated that I should be in Lollipop first before going through the steps.
Click to expand...
Click to collapse
Sorry - but can you read?
If you read the instructions, you can't miss that Part ?
Yupppiiiii....
Sent from my LG-H870DS using XDA-Developers Legacy app
Please help me...
I successfuly installed nougat on my H818P, but when downgrading i am stuck in download mode, on kdz flashing it always stuck at 25%. In download mode it says modified in red color.
phone is identified as H81529a
esco_448 said:
Please help me...
I successfuly installed nougat on my H818P, but when downgrading i am stuck in download mode, on kdz flashing it always stuck at 25%. In download mode it says modified in red color.
phone is identified as H81529a
Click to expand...
Click to collapse
You must downgrade with kdz file of H815 MM and flash moderm after that.
You must downgrade with kdz file of H815 MM and flash moderm after that.
Click to expand...
Click to collapse
I tried that, It's always showing invalid kdz.
esco_448 said:
I tried that, It's always showing invalid kdz.
Click to expand...
Click to collapse
you need a kdz v20p/MM for H815 and extract dll from it, then replace the old dll from your LGUP dir & and flash your kdz MM for H818.
thank you for the guide
I am using (h815 singapore locked) but I am at europe
1.flashed (H81510C_00_2.kdz -android 5.1) with Lgup
2.flashed rooted (system.rooted.H81510c-EU.img)
3.repated ur guide for nougat
and all works fine for me
thanks
the_naxhoo said:
you need a kdz v20p/MM for H815 and extract dll from it, then replace the old dll from your LGUP dir & and flash your kdz MM for H818.
Click to expand...
Click to collapse
Thanks for your help.
But now it's stucking at 11% (PrimaryGPT step). I am geting this: error message:
Error: Error Code = 0x2000,
Invalid command response
esco_448 said:
Thanks for your help.
But now it's stucking at 11% (PrimaryGPT step). I am geting this: error message:
Error: Error Code = 0x2000,
Invalid command response
Click to expand...
Click to collapse
hm ok, try to extract the dll from your kdz MM H818 and replace the dll again.
Thanks to all, I just restored my device.
I modified H81520p_00_0314.kdz with winhex and replaced H815 with H818P. Used LGUP for flashing.
Can I still use dual sim after 7.0 by h815
Unroot Razer Phone 2
This is the method that I used, I bought a phone that was rooted (little did I know) custom recovery was not installed on my device, but bootloader was unlocked and the phone was rooted. Disclaimer:I am no expert, i just used this method last night (2/2/2019) the Razer guides weren't the best at step by step so I am compiling what I learned from doing this. I am not responsible if you brick or bootloop your phone. You should also do independent research on XDA etc before you attempt this process so you understand the risks. I invite others that know more than me to correct what I may have missed and I will updated the OP.
Step 1
You need a USB C to A cord similar to the one that came with the phone, but Razer says that they don't recommend you use that one because it is designed for quick charge not data transfer so I used one that I bought on Amazon years Ago.
Step 2 you need to download 3 things:
The stock image that can be found here:https://developer.razer.com/razer-phone-dev-tools/factory-images/
You need to download Android SDK
https://developer.android.com/studio/releases/platform-tools.html
You need to download the drivers:
https://dl-ssl.google.com/android/repository/latest_usb_driver_windows.zip
Also open this https://developer.razer.com/razer-p...02.1384856067.1549140743-333350818.1549140743
Unzip all of these files to a new folder on your desktop call it Razer Phone 2 or whatever.
I also went into the phone tapped build number repeatedly to enable developer options and turned on USB debugging.
On the device, go to Settings > About <device>.
Tap the Build number seven times to make Settings > Developer options available.
Then enable the USB Debugging option.
Step 3 you need to Open this PDF courtesy of Razer:
https://s3.amazonaws.com/cheryl-fac...stall_Android_Fastboot_Drivers_on_Windows.pdf
This document loosely tells you how to install the drivers follow through all of the steps they give you
It should be noted you see a reference to “Download Mode” there is no such thing also the easiest way to get to this screen is to turn the phone off plug the USB into the computer with the phone not plugged in then hold volume down and plug the phone into the computer and press the power button holding volume down you should be taken to a screen that looks like this (aka download mode): see the image I attached.
I had an issue when I got to the Have Disk portion once I got to the step I had to drill all the way down to the android_winusb.inf file located inside the usb_driver folder. Once i got that it finally showed me the Android ADB Interface and the following dialogue screens. (if you are scrolling through a screen of Manufacturer -Models looking for something then you are doing it wrong) Once it is installed the device Should not have the Android with a ? on the device manager screen it should now say Android ADB Interface. (this part took me almost 2 hours I got frustrated and had to walk away for a bit so dont give up)
You can test that the drivers have been installed correctly like they say in the document but they left a step out for the not as tech savvy people. The way to do it is to open up a command prompt. You will see the directory that is is pointing to is likely C:\Users\[Insert user Name]. We need to change the directory it is looking at by typing.
Cd C:\Users\[insertusername]\Desktop\razer phone 2\platform-tools
(the command cd changes the directory)
You should see the directory change to be looking specifically at that folder now. Now simply type fastboot devices. The command should run and you should see the serial number of your device in the command prompt. If it does not return this then the drivers are not installed correctly.
(some other guides said you should also run the command adb devices, but I never got that to return anything all it ever told me when i ran it was “List of devices attached” with nothing else.
Step 4
Setting the Environment
Once i got to this step I was a little scared because I have never dealt with this before this allows you to call the ADB commands from the command prompt without having to specify the specific folder these ADB commands are located.
Follow the document referenced above until you get to the step that says click New
Instead we are going to look in the section titled “User Variables for [InsertUsername]
Under this section you will see a variable called PATH click on PATH and click edit. A box should pop up and on the right side it should say New, Edit, Browse, Delete, Move Up, Move Down.
Click on New and specify the folder called platform-tools mine looked like this
C:\Users\[username]\Desktop\razer phone 2\platform-tools
Click on ok the box will close and then click on ok again all the boxes pertaining to the environment variables will close.
Step 5
Test that the environment is set up correctly.
You might remember in step 4 we had to open a command prompt and tell it to look specifically at the platform-tools folder to run the ADB commands. With the environment now set we no longer have to specify the folder to run these commands, we can call them from any directory. To test this open a new command prompt it will likely be pointing to
C:\Users\[Insert user Name]
With the phone still plugged in and in “download mode” and without changing the directory, type
fastboot devices it should return the serial number of the phone if the environment has been properly setup if it has not been properly setup then it will return this error.
fastboot' is not recognized as an internal or external command,
operable program or batch file.
Step 6 (im not sure if this is necessary)
Because I bought my phone used I used rootchecker app to ensure the phone was indeed rooted and “download mode” told me the bootloader was unlocked. I wasnt sure if I needed to unlock the critical partitions, but you will notice in the razer instructions right above flash system image they call for them to be unlocked. I simply opened a command prompt and typed:
fastboot flashing unlock_critical
It said they were already unlocked so I moved forward with flashing the system image.
Step 7
Install the system image
From here I followed the razer instructions when i got to the step:
“Navigate to the unzipped system image directory” you open a command prompt and type
Cd C:\Users\[insertusername]\Desktop\razer phone 2\aura-o-global-2009
What this allows you to do is run the flash_all script.
The flash all script uses the command fastboot which if you remember is in the platform-tools folder this is why we had to add the environment in the previous steps so that once we got to this step the flash_all script could find and run that command. I ran this and had no issues the phone will continue to restart and in the command prompt you will see it pushing all the files to the phone. After about 3-4 minutes the phone was at the Wizard. I continued following the guide to lock the bootloader
Reserved
Duplicate post
my phone is not detected in bootloader mode now. i just want to relock my bootloader and i am stuck now
thank you so much! I was almost giving up trying to fix my phone till i saw your post
LordCandyAndy said:
thank you so much! I was almost giving up trying to fix my phone till i saw your post
Click to expand...
Click to collapse
Same here this post was a god send.
The only issues I keep having is that it keeps saying waiting on device, I have uninstalled and removed everything and then reinstalled everything step by step and I keep getting waiting for device in cmd and ps.
any help would be great.
Thanks for the guide.
flash_all kept failing for me because it wouldn't allow fastboot from the ROM's folder. Copying the contents of my platform-tools (adb) folder into the ROM's folder fixed this issue for me. I'm assuming this is because I didn't set up the environment variables correctly.
Darkann said:
The only issues I keep having is that it keeps saying waiting on device, I have uninstalled and removed everything and then reinstalled everything step by step and I keep getting waiting for device in cmd and ps.
any help would be great.
Click to expand...
Click to collapse
I am having the same issue any help