Related
The Superboot root method boot.img for 2.3.2 is now live thanks to Paul over at Android @ MoDaCo.
"Superboot is a boot.img that when flashed, will root your device the first time you boot (installing su and the superuser APK). No need to flash the system partition, no need to use ADB, no messing with the contents of your data partition, no overwriting the shipped ROM on your device, just flash the boot image using the instructions below and you're done!"
Using Superboot
- Download the zip file and extract
- Connect Nexus S via USB cable (with debugging enabled - Settings->Applications->Development->Check "USB Debuggging")
- Boot into bootloader mode - (Turn on while holding 'volume up')
- WINDOWS - double click 'install-superboot-windows.bat'
- MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-mac.sh' followed by './install-superboot-mac.sh'
- LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-linux.sh' followed by './install-superboot-linux.sh'
*Again, All credit goes to Paul at Android @ MoDaCo*
Cool I'm rooted already but nice to see easier ways of doing it for the noobs. Appreciate the work.
Sent from my Nexus S using Tapatalk
Updated today to 2.3.2 and lost root. Used this and I'm back up and running ! Thank you!!!
Sent from my Nexus S using XDA App
2.3.2
can u do this being rooted or do you have to revert to stock
For some reason this didn't work for me. I tried it twice but each time the phone rebooted I still didn't have root. Do I have to unlock fastboot?
qreffie said:
For some reason this didn't work for me. I tried it twice but each time the phone rebooted I still didn't have root. Do I have to unlock fastboot?
Click to expand...
Click to collapse
i think you would
fastboot
fastboot satus failinvalid command
finally regain root, thank you!!!
qreffie said:
For some reason this didn't work for me. I tried it twice but each time the phone rebooted I still didn't have root. Do I have to unlock fastboot?
Click to expand...
Click to collapse
Yes. These instructions assume you have already unlocked your bootloader.
Sent from my Nexus S using Tapatalk
maybe a noob question: if I just root my Nexus S using this method (no custom rom installation), will I still be able to get OTA updates from google?
dakiz71 said:
maybe a noob question: if I just root my Nexus S using this method (no custom rom installation), will I still be able to get OTA updates from google?
Click to expand...
Click to collapse
Yes. You may have to re-root after updates but your phone will prompt you when OTA updates are available just like normal.
Sent from my Nexus S using Tapatalk
annndrewww said:
Yes. These instructions assume you have already unlocked your bootloader.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Figures. The answer was staring me in the face the whole time. I think I even remember unlocking it last time I rooted this way. I guess I should just leave it permanently unlocked then so it doesn't keep wiping every time I go to root after an update.
Hi,
I can't get it to work on my mac.
When I put the renamed as "superboot" folder on the desktop, I open the terminal and type in:
~/Desktop/superboot/chmod +x install-superboot-mac.sh./install-superboot-mac.sh
it doesn't find that path.
Could somebody help me as a noob?
Thank you!
Am I the only one that did not lose root after the latest 2.3.2 update?
DarkAgent said:
Am I the only one that did not lose root after the latest 2.3.2 update?
Click to expand...
Click to collapse
I used the superboot method for 2.3.1 and also did not lose root in with the 2.3.2 update.
Sent from my Nexus S using Tapatalk
You shouldn't.
P
Windows 7
For me install-superboot-windows is waiting for device long without success :\
No matter ... i had to force my pc recognize Nexus once more
Thank you. This seems simple. I'm stuck with my XP recognizing my Nexus S USB Driver after installing SDK and Google USB Driver even after trying to "update" driver under Device Manager and redirect the directory to Google USB Driver? I'm very confused.
philbs17 said:
Hi,
I can't get it to work on my mac.
When I put the renamed as "superboot" folder on the desktop, I open the terminal and type in:
~/Desktop/superboot/chmod +x install-superboot-mac.sh./install-superboot-mac.sh
it doesn't find that path.
Could somebody help me as a noob?
Thank you!
Click to expand...
Click to collapse
Ok buddy heres what you need to do, on the MAC, this is how i do it.:
DL the .zip in the OP.
Extract it on you're desktop
Rename the Extracted file to Nexus (thats what I name it)
youre device needs to have the bootlader Unlocked.
Open Terminal and type
cd desktop
cd nexus
chmod +x install-superboot-mac.sh (press enter)
./install-superboot-mac.sh (press enter)
then you're done. hope this helps.
Let me know.
Simply amazing! Thanks for the breakdown.
May NOT work for 2.3.3, if attempting on 2.3.3 use old part 1! - Will wipe all data though
Windows ONLY!
Hey guys, rooted my Nexus S today, and decided to write a thorough, detailed guide on how I did it, as none of the guides I had found had everything detailed. I came across a few problems, and all of this is in the guide. I successfully completed it on my Nexus S running 2.3.2, so any version below that will also work.
The original guide was made by AllGamer, and can be found here. I followed this guide, and added things when I found it was needed
The full guide with everything (including links, pictures) can be found on my site, Complete Android.
New info: Upon finding another thread over at XDA (http://forum.xda-developers.com/showthread.php?t=931865) it has been realized that you can root your Nexus S without unlocking the bootloader, and therefore not loosing your data on the SD card. Part 1 for the new method is still the same, but choose the new Part 2!
WARNING: Rooting your device will wipe all data off it, so you will loose EVERYTHING! Make sure you backup all important data first. Only applies to old Part 2 (fastboot oem unlock method), but it is still a good idea to backup important information!
Click to expand...
Click to collapse
What you will need:
Nexus S (obviously)
Android 2.3 SDK
USB Cable
PDAnet (for drivers)
Clockwork Recovery Image
Superuser
Part 1
Download the Android 2.3 SDK (or direct from Google here, 32MB).
Once it has finished downloading, unzip it, and run the SDK manager.
Select whatever components you wish to install, but you MUST make sure you install Google USB Driver (Available packages > Third party Add-ons > Google Inc. Add-ons > Google Usb Driver package, revision 4) otherwise this guide will not work!
We must now install the Google USB Driver, or the phone will not be recognised as a device other than a mass storage device.
Connect your Nexus S to your computer, and put it in USB storage mode.
Put it in USB Debugging Mode (Settings > Applications > Development > USB Debugging)
Windows should now recognise your Nexus S when you plug it in, and ask to install drivers. It probably won’t find anything, so we need to help it manually.
(Installing drivers manually varies between Windows versions, so please refer to http://developer.android.com/sdk/win-usb.html if you are having trouble). Launch Device Manager (you can find it in Control Panel), find Other Devices, and listed under that heading, you should find Nexus S. Right click, and select Update Driver Software. Click Browse my computer for driver software, find your SDK folder, then the google-usb_driver folder inside it, click OK, then Next. This should install the USB driver successfully. Reboot your computer.
Power off your Nexus S, connect it to your computer via USB cable, and boot it into the Bootloader Interface (you can do so by holding down the Power and Volume Up buttons at the same time).
It should say LOCK STATE – LOCKED, in white just above the green Android. You are now ready to move on!
Part 2 - Fastboot oem unlock method - WIPES ALL DATA!
We now need to install PDAnet on our PC so that Windows can see our Nexus S when we are using the Command Prompt. Install PDAnet from here, select Samsung when asked about the Manufacturer, allow the driver to be installed (because the driver is unverified, don’t worry about this!). Follow along with any other instructions. You should be set now.
With the latest SDK version, some tools have been relocated to another directory, so we need to make a copy and move them back. Navigate to the directory where you unzipped the Android SDK file in part 1. Inside it, go to the platform-tools folder, and copy both AdbWinApi.dll and AdbWinUsbApi.dll. Go back to the main Android SDK directory and find the tools folder. Paste these two files in there, and we are all ready to use ‘fastboot oem unlock’ (the rooting command) now.
Open a command prompt window (Start > Run > cmd.exe).
Change to the tools directory within your Android SDK folder by using the following command (without the quotes and replacing *YOUR SDK* with the path to your Android SDK folder) ‘cd c:\*YOUR SDK*\tools’.
Make sure your Nexus S is still in the Bootloader Interface (refer to step 9, part 1 of it isn’t).
Now in the command prompt, type in (without the quotes) ‘fastboot oem unlock’.
Now turn your attention to the phone, and read through the new information displayed on the screen. Using the Volume keys select Yes, then press the Power button. This will WIPE EVERYTHING! I bear no responsibility for any lost data on your phone!
If everything is successful, on your phone, the LOCK STATE should now read UNLOCKED, and on your computer, the command prompt window should say something like this:
Download the Clockwork Recovery image (here if you don’t already have it) to your Android SDK tools folder (*Android SDK*\tools).
Rename the newly downloaded Clockwork Recovery image to ‘recovery.img’ (no quotes).
Now we need to flash it to our Nexus S, so enter this command into the Command Prompt (make sure it is in the Androis SDK tools folder!) ‘fastboot flash recovery recovery.img’ (without the quotes).
If all is successful, the Command Prompt window should look something like this now:
Download the superuser app to the Android SDK tools folder.
Power on your Nexus S, leaving it connected to USB.
Mount the USB storage, and drag and drop the superuser .zip file you just downloaded into the root of the internal SD card (so Computer > *Device Name*, not in any other folders!). It should look something like this:
Power off the Nexus S, and return to the Bootloader Interface (step 9, part 1).
Select Recovery using the Volume buttons, then the Power button.
The phone should reboot into Clockwork Recovery, but if not don’t panic, just repeat steps 9-12, including downloading a new copy of the file (mine only worked the second time around, don’t worry!)
Using the Volume buttons and Power button, select install zip from sdcard.
Select choose zip from sdcard.
Select the su-version#-signed.zip file you downloaded earlier and apply it.
Select yes (there are lots of nos).
Confirm it says something like this: install from sdcard complete
Select Go Back.
Select Reboot. (You will now also have an unlocked padlock when you boot up)
Done! You now have to set up your phone again like when you first got it, but it will be rooted now.
New Part 2 - Does NOT wipe everything - Keeps a locked bootloader
Make sure Part 1 is completed.
Make sure you have downloaded the Clockwork Recovery file and the Superuser file.
Move the Clockwork Recovery file to your tools folder within the Android SDK folder, and rename it to recovery.img (for simplicity).
Connect your Nexus S via USB to your computer and mount it as USB storage. Copy across the Superuser file to the top level of your sdcard. (So the first window you see, not in any other folders. The sdcard is just where all the files are stored, don't worry about it too much for now).
We now need to install PDAnet on our PC so that Windows can see our Nexus S when we are using the Command Prompt. Install PDAnet from here, select Samsung when asked about the Manufacturer, allow the driver to be installed (because the driver is unverified, don't worry about this!). Follow along with any other instructions. You should be set now.
With the latest SDK version, some tools have been relocated to another directory, so we need to make a copy and move them back. Navigate to the directory where you unzipped the Android SDK file in part 1. Inside it, go to the platform-tools folder, and copy both AdbWinApi.dll and AdbWinUsbApi.dll. Go back to the main Android SDK directory and find the tools folder. Paste these two files in there, and we are all ready to use 'fastboot boot' (the boot image command) now.
Open a command prompt window (Start > Run > cmd.exe).
Change to the tools directory within your Android SDK folder by using the following command (without the quotes and replacing *YOUR SDK* with the path to your Android SDK folder) 'cd c:\*YOUR SDK*\tools'.
Make sure your Nexus S is still in the Bootloader Interface (refer to step 9, part 1 of it isn't).
We now need to use the 'fastboot boot' command to load Clockwork Recovery onto our Nexus S. In the command prompt, type in the following (but without the quotes, as always) 'fastboot boot recovery.img'
Once you are in Clockwork Recovery (it may take a couple of tries, don't panic, just redownload Clockwork Recovery, and complete steps 3 and 10, part 2) it should look something like this:
Using the Volume buttons and Power button, select install zip from sdcard.
Select choose zip from sdcard.
Select the su-version#-signed.zip file you downloaded earlier and apply it.
Select yes (there are lots of nos).
Confirm it says something like this: install from sdcard complete
Select Go Back.
Select Reboot.
Done! You should still have all your data present on your phone, and have root access!
Notes
As AllGamer said in his tutorial:
It’s normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you’ll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you’ll need to rename /etc/install-recovery.sh to something thing else
Click to expand...
Click to collapse
Keep this in mind! It's not because you did something wrong
Also, some root apps require BusyBox to be installed, as I found out with Titanium Backup, so once you set up your Nexus S again, head on into the Market, and download BusyBox. It installed fine on my Nexus S this way, and now TB works fine.
I hope this is the best, most thorough guide you will find on rooting the Nexus S. Enjoy! Feedback is appreciated, and I will help out if you need any extra help.
Your guide has been wonderful however I'm stuck on part 2, step 4. I tried writing in the path to my directory and they keep giving me whatever I wrote in the command prompt "is not recognized as an internal or external command, operable program or batch file"
"Change to the tools directory within your Android SDK folder by using the following command (without the quotes and replacing *YOUR SDK* with the path to your Android SDK folder) ‘cd c:\*YOUR SDK*\tools’."
This is how my command prompt looks like when I first open it. "C:\Users\Du>"
and this is what I typed in the command prompt: "Downloads\android-sdk_r09-windows\android-sdk-windows"
^^^I did exactly what you said above and nothing is happening. I don't know whether I'm writing in the directory wrong or what. Please help me out thanks
Your guide is nice, however as shown in distortedloop's stickied Root & Recovery thread, fastboot oem unlock is not required for rooting & flashing. We no longer have to lose all our sdcard data when first rooting and/or flashing a ROM.
Other than that, this seems to be a nice amendment of Allgamer's sticked root & recovery thread. I'm sure it will be useful to many.
STARSCR33M said:
This is how my command prompt looks like when I first open it. "C:\Users\Du>"
and this is what I typed in the command prompt: "Downloads\android-sdk_r09-windows\android-sdk-windows"
^^^I did exactly what you said above and nothing is happening. I don't know whether I'm writing in the directory wrong or what. Please help me out thanks
Click to expand...
Click to collapse
Ok so if you want to change directories in the command prompt, you need to use the command
Code:
cd
So in your case I would type in
Code:
cd c:\Users\Du\Downloads\android-sdk_r09-windows\android-sdk-windows\tools
That way is fool proof, however you could take a shortcut, because you are already in the Users/Du folder (because of how it looks when you first open it), you could just type in
Code:
cd Downloads\android-sdk_r09-windows\android-sdk-windows\tools
Hope that helps
ravidavi said:
Your guide is nice, however as shown in distortedloop's stickied Root & Recovery thread, fastboot oem unlock is not required for rooting & flashing. We no longer have to lose all our sdcard data when first rooting and/or flashing a ROM.
Click to expand...
Click to collapse
I think this way is a cleaner approach personally, but hey choice is good That's what Android is all about
EDIT: New approach added, now there is choice and easyness for all
Other than that, this seems to be a nice amendment of Allgamer's sticked root & recovery thread. I'm sure it will be useful to many.
Click to expand...
Click to collapse
Thanks
Jonathon Grigg said:
I think this way is a cleaner approach personally, but hey choice is good That's what Android is all about
Thanks
Click to expand...
Click to collapse
I'm not sure that wiping all your data pointlessly is "cleaner."
It's not even clear what exactly the oem unlock of the bootloader really does for us, since you can get into clockwork recovery without that step. Once you're in clockwork you pretty much own the phone. I'll be interested to see if someone can use clockwork to flash a new boot image once rooted without the unlock; if so I can't see any reason to unlock the bootloader. That said, mine is unlocked, and I like it that way, but many won't root for fear of losing data on the phone.
Even if you end up having to do the oem unlock in the long run for some activities you want to do, it seems that rooting, then installing Titanium and backing up your apps and app data fully is a better way to go than just losing all your data (any app that doesn't store its data on the sdcard) that can't be backed up without root would be a lot less painful than WIPING everything on the phone, including the sdcard.
It's not worth arguing about, but I think any method that is including the oem unlock step should at least mention that that step can be skipped. How many people will go through the pain of a wipe that they didn't need to because they didn't see that there was an option without it. I guess that's there own fault for not doing enough searching on their own...
Anyways, nice and thorough effort. I'm sure many will benefit from your additions to AllGamer's tutorial.
distortedloop said:
I'm not sure that wiping all your data pointlessly is "cleaner."
It's not even clear what exactly the oem unlock of the bootloader really does for us, since you can get into clockwork recovery without that step.
Click to expand...
Click to collapse
I have been wondering that myself. My guess is that for the average user you don't need to, but maybe it's for real power users who build their own ROM which has been fully modded or something, I'm not sure.
but many won't root for fear of losing data on the phone.
Click to expand...
Click to collapse
I definitely agree with that, and your guide is probably the best way for those people!
Even if you end up having to do the oem unlock in the long run for some activities you want to do, it seems that rooting, then installing Titanium and backing up your apps and app data fully is a better way to go than just losing all your data (any app that doesn't store its data on the sdcard) that can't be backed up without root would be a lot less painful than WIPING everything on the phone, including the sdcard.
Click to expand...
Click to collapse
Exactly, this is one of the better uses for both methods. I already had to wipe my phone twice due to Samsung CS so I'm used to it Although it does give you a chance to clear out the apps you don't need. Doing that I noticed better battery life on my phone.
It's not worth arguing about, but I think any method that is including the oem unlock step should at least mention that that step can be skipped. How many people will go through the pain of a wipe that they didn't need to because they didn't see that there was an option without it.
Click to expand...
Click to collapse
I wasn't going to argue I'm happy to adjust my tut to include something about this, after all it was aimed at more beginners.
EDIT: Added a new part to my tutorial based on your guide, just includes some more detail. Thanks again.
Thanks distortedloop
This is awesome cause i relocked my bootloader i really just needed root. Thanks!
Edit oops lost track of tabs open.
I think we can use this method to unlock oem without wiping data.
boot cw -> full backup -> unlock and flash cw (wipes data) -> restore backup (got ur data back and oem unlocked)
the only problem i can think of is that restoring backup would re-lock oem again but i am not sure of that.
i can't try this right now but if someone could, please give feedback.
Jonathon Grigg said:
I wasn't going to argue I'm happy to adjust my tut to include something about this, after all it was aimed at more beginners.
EDIT: Added a new part to my tutorial based on your guide, just includes some more detail. Thanks again.
Click to expand...
Click to collapse
Nicely done. Thanks.
sam4free said:
I think we can use this method to unlock oem without wiping data.
boot cw -> full backup -> unlock and flash cw (wipes data) -> restore backup (got ur data back and oem unlocked)
the only problem i can think of is that restoring backup would re-lock oem again but i am not sure of that.
i can't try this right now but if someone could, please give feedback.
Click to expand...
Click to collapse
That's what I suggesting a couple of posts above (root without unlock to at least make a backup of user data).
Restoring a titanium backup would not re-lock the phone. A nandroid restore might, depends on what all it imaged and restores, but it's so easy to re-root, that doesn't seem like a big deal.
Jonathon Grigg said:
Download the Android 2.3 SDK (or direct from Google here, 32MB).
Click to expand...
Click to collapse
Looks like you forgot to add the link in your copy pasta.
AtomicPC said:
Looks like you forgot to add the link in your copy pasta.
Click to expand...
Click to collapse
I've been working on it I just wanted to get it up here as soon as I could That's why I mentioned that the full guide is available on my website. I'm going back to school today, so I don't really have too much time for changing links now. Besides, most people on XDA should know how to look at the 'What's needed' part
Sent from my Nexus S using XDA App
Jonathon,
Thank you for posting this detailed guide to rooting without losing your data! I do have a question. As you've probably heard, there are a few updates coming soon and if they are like they were on the N1, they always broke root. So getting root back was tricky unless I "unrooted" before applying the update. Using your method, is it easy to "unroot"? Thanks!
No problems
As for your problem, I never actually had a N1 so I don't exactly know why that would happen. So far from the 2 updates available to NS owners it seems like the OTA update does break root but it appears to be the same to get it back again. Can someone confirm this? I haven't been through an update with my root yet.
As for unrooting, if you haven't unlocked the bootloader (so you have followed the new part 2) I think it is just a case of finding a stock image (I think there's a GRH78 one around here somewhere) and booting into Clockwork Recovery and flashing it. That should remove root and then also give you a notice to install the GRH78C OTA update so you get the latest version.
I think that is what you meant? If you did unlock the bootloader (using the original part 2) then I think you just have to follow the same steps as I mentioned just then but afterwards go back into the bootloader interface and run 'fastboot oem lock' and it should be right.
Sent from my Nexus S using XDA App
Question on Part 2- step 1.
Code:
# We now need to install PDAnet on our PC so that Windows can see our Nexus S when we are using the Command Prompt. Install PDAnet from here, select Samsung when asked about the Manufacturer, allow the driver to be installed (because the driver is unverified, don’t worry about this!). Follow along with any other instructions. You should be set now.
Why above step is required if one already installed USB Driver for Nexus S and "ADB devices" command can find the device ?
On Allgamer thread didnt ask to repeat installing USB driver ?
What purpose for the pdanet driver ?
I dont want to put redundant drivers into my system which may interfere each other during flashing process.
hmanxx said:
Why above step is required if one already installed USB Driver for Nexus S and "ADB devices" command can find the device ?
On Allgamer thread didnt ask to repeat installing USB driver ?
What purpose for the pdanet driver ?
I dont want to put redundant drivers into my system which may interfere each other during flashing process.
Click to expand...
Click to collapse
When I tried to use the fastboot command with my Nexus S connected, it would hang and not do anything, despite leaving it for about 5 minutes. I searched online, and found the PDAnet solution, so I don't know what the difference is exactly. All I found the Google SDK USB drivers to do is enable you to see your device in Device Manager, however you could try it without the PDAnet drivers, and let me know what happens!
Thanks
Thanks for the prompt reply.. I tried out the google driver..it doesnt work under fastboot. I eventually get the fastboot enabled driver..that could explain why the pdanet driver required.
After i installed the fastboot enabled driver, i could test the connectivity under fastboot with "fastboot devices"
thanks going to try out rooting..i just want simple root access..without wiping data is a ++ ..
I managed to run fastboot boot recovery.img...going into clockwork menu..apply the superuser.zip.(for froyo version)..till completion..no word of failure..
However after rebooting, su and SuperUser.apk are not installed.( I used adb to check the system/app and system/bin folder.
Edit- manage to root properly after system mounting .
Just a note..to properly complete the rooting, one need to apply mounting then mount system before applying the Superuser.zip install from sdcard.
Prior to step 11, you may want to add the following steps for folks having problem to get the superuser.zip to install properly.
Originally Posted by droidmage
So all you guys who are having trouble getting root inside the rom, When your in recovery before you flash the superuser.zip file select -- mounts and storage -- then --mount /system -- then flash the .zip file and reboot
Click to expand...
Click to collapse
Thanks for the extra bit of info, I will attempt to add that in when I get a bit more time on my hands. when I did it it seemed to work fine so thanks for discovering that!
Enjoy your rooted phone
Sent from my Nexus S using XDA App
Hello people.
So after a long search, I managed to find the method to install TWRP on my LG Magna H502f V10a.
To do this, he must first root phone with the method: LG ONE CLICK ROOT:
- Install the latest drivers for LG: https://sourceforge.net/projects/av...S51MAN313AP22_ML_WHQL_Ver_3.13.2.exe/download or drivers LG Verzion: https://sourceforge.net/projects/av...S51MAN313AP22_ML_WHQL_Ver_3.13.2.exe/download
- Download LG One Click Root 1.3 (Graphic UI): http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
- Unzip the archive
- Enable Usb debugging on your phone . (General > About phone > Software information, tap Build number seven times and then go to Settings > Developer options and turn on Usb debugging)
- Connect your phone to pc.
- If the phone not Recognize, try to switch entre MTP and PTP options.
- Launch LG ONE CLICK ROOT and be guided to the end of the procedure.
- Once completed you will SUPER SU installed on your device.
- To check the status of root you can download ROOT CHECKER from the play store.
Step 2: UNLOCK THE BOOTLOADER and TWRP INSTALL:
- To do this, first download both files (I specify that it is for the H502f) https://drive.google.com/file/d/0BwmQ3F48xaJjV1lKNUdPQkV2a2M/view
- And download and install TERMINAL EMULATOR from the play store: https://play.google.com/store/apps/details?id=jackpal.androidterm
- Copy both files and uboot.img and recovery.img in the root of the internal memory of the phone
- Go to TERMINAL EMULATOR and run the following commands (after getting the root right):
su
dd if=/storage/sdcard0/uboot.img of=/dev/uboot count=1024
dd if=/storage/sdcard0/recovery.img of=/dev/recovery count=32768
reboot recovery
And you're in TWRP 2.8.7.1 and there you can make a backup just to have a little backup in case pending a Custom ROM which I hope will happen soon.
Thank you.
A small up to raise the thread ... to reach 10 posts
TWRP 3.0.0-0 available here : http://forum.xda-developers.com/android/general/twrp-3-0-0-0-lg-magna-t3319479
Root alternative method
Hey...you can also gain root priviliges by using the Kingroot apk ...Also in my device (Lg H500) instead of TERMINAL EMULATOR, i did use the pc connection and adb shell
(in order to avoid typing)...
But all these are details....The tutorial is 100% correct and confirmed...Cudos
Thank you
awesome! this works for me...
Help!!
Hello, i have a problem with the installation of twrp and unlocking the bootloader. When i type the command "dd if=/storage/sdcard0/uboot.img of=/dev/uboot count=1024" in the emulator, it says, "not valid direcory or location". I tried to change the location of the files, although i am prety sure they are where they are supposed to be. I am desperate
Nice, thank you for your information
Are you about to have:
1- unzip the archive (for both files: uboot.img and recovery.img)?
2- copied the 2 files .img in root of the internal storage memory of phone (not sd card) ?
Aneom7331 said:
Hello, i have a problem with the installation of twrp and unlocking the bootloader. When i type the command "dd if=/storage/sdcard0/uboot.img of=/dev/uboot count=1024" in the emulator, it says, "not valid direcory or location". I tried to change the location of the files, although i am prety sure they are where they are supposed to be. I am desperate
Click to expand...
Click to collapse
Copy both files to the internal storage (storage/emulated/0/) and use these commands
dd if=/storage/emulated/0/uboot.img of=/dev/uboot
dd if=/storage/emulated/0/recovery.img of=/dev/recovery
That works for me.
Sent from my LG-H502 using XDA-Developers mobile app
IT WORKED!
OMG dude it worked!!! Thank you so much!!!:laugh:
[emoji106] thats cool. Glad to help.
Sent from my LG-H502 using XDA-Developers mobile app
No such file
So i entered terminal, and when i enter the command lines it says no such file or directory, and i followed the instructions and copied both files into the internal storage, pleeeeaaaassse help
masteryoda110 said:
So i entered terminal, and when i enter the command lines it says no such file or directory, and i followed the instructions and copied both files into the internal storage, pleeeeaaaassse help
Click to expand...
Click to collapse
[quote name="Aneom7331" post=66276037]Hello, i have a problem with the installation of twrp and unlocking the bootloader. When i type the command "dd if=/storage/sdcard0/uboot.img of=/dev/uboot count=1024" in the emulator, it says, "not valid direcory or location". I tried to change the location of the files, although i am prety sure they are where they are supposed to be. I am desperate [/QUOTE]
Copy both files to the internal storage (storage/emulated/0/) and use these commands
dd if=/storage/emulated/0/uboot.img of=/dev/uboot
dd if=/storage/emulated/0/recovery.img of=/dev/recovery
That works for me.
Sent from my LG-H502 using XDA-Developers mobile app
Hi,
So i've read not just this thread, but also the LG 3 where the LG one click root files come from.
I have the LG Magna - H502Y. It's probably the most "recent" kernel with 3.10.54 version. Anyway, it doesn't work with me. Has anyone tried with this version?
thanx
Thank you, now my lg stock lg magna h502f get TWRP recovery....I have plan to flash Marshmallow, with titeuf15 instruction under link 'http://forum.xda-developers.com/android/general/official-update-to-marshmallow-6-0-lg-t3395098/post67233869#post67233869".
So to continue my task, do I need any task such as Software update(that's security patch) to install?
Or
Should I just do directly in titeuf15's instrctions????
Thz. . .I m beginner in this field...
Just go ahead and follow titeuf15's instruction.
Berong said:
Just go ahead and follow titeuf15's instruction.
Click to expand...
Click to collapse
Thz Berong
Hi, in case I want to relocked it to send it to waranty how do i relock the BL? . Does the LG Pc tool works without a chance of brick??
just flash stock rom again...
Sent from my LG-H502 using XDA-Developers mobile app
Verified Downgraded from ZVA to ZV6 with full root access
LS991 Sprint Only.
QUICK GUIDE & TESTING
(Please read the entire guide before trying anything.)
I nor anyone at XDA is responsible for anything that may happen to your device.
Simply, by taking incentive to change the stock setup provided by the manufacturer for your device; you assume all responsibility for anything that happens.
download LGUP
http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
(Thanks to shakeyabooti)
download LS991ZV6_00.zip and extract to get .tot file with winrar/7zip or any other unzipping program
http://downloads.codefi.re/autoprime/LG/LG_G4/LS991/LS991ZV6/LS991ZV6_00.zip (or google/xda search for mirrors) (Thanks to autoprime)
download LGROOT
http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
(Thanks to Unjustified Dev)
download LG Drivers
http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772 (or google)
(Thanks to Unjustified Dev)
download rootedsystem.ls991.zip and extract to get .img file with winrar/7zip or any other unzipping program
http://forum.xda-developers.com/sprint-g4/general/zv6-root-success-t3205963/page3
(scroll down to parin11's post. #29 and thank you to both parin11 and mswlogo)
-install drivers
-enable oem unlock in developer settings
-plug device in as charge only, switch to mtp to verify drivers are working correctly, then disconnect
--if on mtp then switch to charge only to verify drivers are working correctly, then disconnect
-enable usb debugging
-reconnect and drivers auto install
-disconnect after 2 minutes.
--while you wait;
-for LGUP extract and install _dll version then the second msi.
-for LGROOT extract to a folder to keep things organized
-remove the back cover of your device and leave it off for access to battery pulls.
-power off device
-hold volume up key and plug in your device and keep holding the volume down key until it passes the screen that says download mode.
-open LGUP
-make sure UPGRADE is checked/has a little circle/bullet point
-click in the empty space directly to the right of where it says BIN with the checkmark
-3 dots will appear to the right of the program in the same row that says BIN; which is your browse option
-navigate to LS991ZV6_00.tot and select
-reconfirm your UPGRADE option is checked
-press start and allow the device to fully complete the process.
-your device will boot to the loading screen right before showing the android desktop and "freeze"
-In most if not all new flash scenarios; your device will not boot up until a factory restore and clear cache is done.
-To do this you must simply remove the battery and usb cable from your device AFTER it has hung on the logo for about 3 minutes / 180 seconds.
(Most new devices average a first time boot of up to 150 seconds maximum to be considered fully "loaded")
-With the battery and cable removed; hold the power and volume DOWN button together at the same time.
-insert the battery while holding these buttons together and just wait while holding them and you will see it says booting into recovery.
-once your in the recovery you use the power key to select and the volume keys to navigate.
-navigate to factory restore/reset hit the power button, navigate to "yes" out of all the "no's" and hit the power button again
-it will say its complete and either ask you to go back reboot or return to menu. RETURN TO THE MENU, do not boot up yet.
-Once returned to the main menu you will see it says clear cache. Select and press yes and now you can select reboot; or return to menu then reboot.
Your device will be on ZV6 stock and fully booted after this.
Now this is where it gets kind of odd because my device never actually loaded the rootedsystemls991.img file nor did I run a root script
when attempting to flash it with the steps listed in the other root guides BUT i followed this guide from step one to step 9 (and outlined continuing through the guide)
http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
this allowed all the necessary rooting files to be in the places necessary to execute the root but I did one extra step
I did an adb.exe push rootedsystem.ls991.img /data/local/tmp command as well while the device was on the home screen.
This was so I could basically emulate the command listed by |Unjustified Dev| as it also states to do in the ZV5 guide.
So this is what I did,
-After my device booted up and loaded to the home screen on stock zv6, I opened the LGROOT folder
-held shift and clicked "open command prompt here"
-when cmd opened I ran the following command
adb.exe devices
This allowed me to see that my device was connected to the PC with its generated serial number.
-then i ran the following command
adb.exe push busybox /data/local/tmp/ && adb.exe push lg_root.sh /data/local/tmp && adb.exe push UPDATE-SuperSU-v2.46.zip /data/local/tmp
-After this I applied the command to push the .img file to the same location. This was the "emulated command" I spoke of.
adb.exe push rootedsystem.LS991.ZV6.img /data/local/tmp
-I then added the .img file directly to the Internal Storage / Stock Phone MTP storage
-Afterwards I simply powered off my device, removed the usb cable, held the volume up button, then plugged it back in still holding the volume button until
the text download mode was gone again; and no this is not a timing thing im just saying that again incase anyone forgot how to get into download mode. lol.
-I then ran the ports.bat file included in LGROOT to find the COM port drivers.
-Followed up with this command
Send_Command.exe \\.\COM8 (<--Replace number here with the COM port listed for the "DIAG" portion of the device.)
-Now, still in download mode I executed this command about three times with no avail.
dd if=/data/media/0/rootedsystem.LS991.ZV6.img bs=8192 seek=65536 count=557312 of=/dev/block/mmcblk0
(Which by the way I had the file in both the MTP side of root and in the data/local/tmp)
or you could change it to /data/local/tmp/ like
dd if=/data/local/tmp/rootedsystem.LS991.ZV6.img bs=8192 seek=65536 count=557312 of=/dev/block/mmcblk0
This would possibly solve the issue I was having. So you would have root now.
THIS PART REQUIRES TESTING.
BUT continue reading you'll be shocked.
sidenote:
They state that all you have to do is put the .img file into the root of your Internal Storage / Stock Phone MTP storage
and run the command in download mode but this failed when I tried to execute it.
dd if=/data/media/0/rootedsystem.LS991.ZV6.img bs=8192 seek=65536 count=557312 of=/dev/block/mmcblk0
The command above was the command they listed to be able to restore the device from stock to stock with root access. Please note I tried this command while the phone was turned on in debugging with enable oem unlock on, while in download mode and while in recovery mode all with debugging and enable oem unlock checked with either no response / device detected, or attempts causing the command prompt to show the # symbol after a few seconds of executing the line above which shouldn't happen,
since the size of the file is 4GB... The ENTIRE SYSTEM PARITION. -_-. There is a considerable amount of hangtime here is what I'm saying.
If the dd if=/data/media/0/rootedsystem.LS991.ZV6.img bs=8192 seek=65536 count=557312 of=/dev/block/mmcblk0 command worked for you then great, boot up and enjoy root! BUT.
For those who didnt have luck doing so with the command that failed me above, for some odd reason after pushing both the SuperSU bundle and the entire .img file to /data/local/tmp/ with the files in the internal storage /data/media/0/ as well
trying to only execute the command for the .img (/media/0/ not /local/tmp/) | (not the "fixed" command") and NOT for the SuperSU
eg.
-This was for the image which was the only one I used. (USED)
dd if=/data/media/0/rootedsystem.LS991.ZV6.img bs=8192 seek=65536 count=557312 of=/dev/block/mmcblk0
This was for root only which I did not touch. (NOT USED)
sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
-This caused the device to simply show the # sign almost immediately as I spoke of above.
-I typed in LEAVE and the device booted back up.
-The odd thing I'm speaking about is when I turned the device back on it showed that SuperSU was installed and was requesting to be "updated".
-I chose normal and it asked for a reboot. Rebooted started back up and it asked for root access when I clicked on it.
-Granted and successful.
-Went to the playstore.
-It said update next to SuperSU which was even odder.
-Clicked it and updated it and it got the latest version, asked for one more reboot, started back up, then I opened the app. Everything was normal.
-Downloaded root checker basic, titanium backup, and greenify immediately.
All passed with flying colors.
-There is an error that pops up in titanium backup regarding adding underscores or slashes into modified file directories for backup purposes assumed but
opening greenify ended up picking up this issue and requesting to fix it.
Why not right?
-Heh. It worked.
I have never experienced this type of latency within programming so this is extremely odd and without executing the SuperSU script command or,
a sucessful flash of the .img it just seems too odd, but; there you have it! All of the mods / developers working on this device I would like to hear
your insight on this.
So you have two options. Follow what I did or test the command with /data/local/tmp/ and try your luck flashing stock with root again or just run the root script on stock instead of trying to flash from stock to stock rooted.
Thank you and enjoy your root!
P.S. I didn't end up experiencing this issue since it works perfectly but in the event that SuperSU does not install after trying to flash the .img and getting
the 2 second delay with the # sign appearing immediately and rebooting after 3 attempts I would have personally tested the original adb SuperSU script command recommended for the ZV5 users
which was listed above and is
sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
And for the love of your device. Don't try to update your device from an older version using this method. Ayeeeyiyiy
I will re-test what I stated and make a completely organized guide and video for everyone.
I just wanted to let you all know now to assist the entire community in understanding this device's root process a little more.
Will this work with brand new phone?
This method looks exactly like what I would need if I were to sign up with Sprint and get a brand new G4 from them. I just want to make sure that this method would work on the brand new phone to get root access and possibly flash new ROMs to the device. I have gotten burned before by getting devices that I think would work only to find out I had gotten an unsupported variant. Any knowledge would be greatly appreciated. Thank you.
wow, thanks!
Thanks for all your hard work. This phone has been one of my best and the only thing missing has been root, etc. Chewing over your instructions and thoughts. My confidence level is not quite there to pull the trigger, but i'm getting close. Hoping this is a promising method for those of us on Sprint ZVA. I will continue to do research and watch this thread. Thanks so much for your time, tips and expertise.
brpaaron said:
This method looks exactly like what I would need if I were to sign up with Sprint and get a brand new G4 from them. I just want to make sure that this method would work on the brand new phone to get root access and possibly flash new ROMs to the device. I have gotten burned before by getting devices that I think would work only to find out I had gotten an unsupported variant. Any knowledge would be greatly appreciated. Thank you.
Click to expand...
Click to collapse
As long as its not been updated to zvb. Antirollback implemented on zvb
Still running zv6
I am still running zv6 and never updated. Do I need to update to downgrade to root or can I just skip to after the downgrade?
i am running zv9 i can not stock zv6
I have ZVC can i downgrade to ZV6?
LG G4 LS991.
LG G3 D850 ROM Fulmics 6.6
Recovery TWRP v2.8.7.0 bumped
LS991 ZVD
Hi there does anyone know whether or not it will work on the ls991 zvd update??? Sprint variant
Ls 991 ZVD
Will this method work on ls991 zvd i havent found anything on it
Expo6810 said:
Will this method work on ls991 zvd i havent found anything on it
Click to expand...
Click to collapse
No. Zva or lower. You will brick it.
---------- Post added at 02:28 AM ---------- Previous post was at 02:28 AM ----------
No zva or lower
TheMadScientist420 said:
No. Zva or lower. You will brick it.
---------- Post added at 02:28 AM ---------- Previous post was at 02:28 AM ----------
No zva or lower
Click to expand...
Click to collapse
Is there anything i can do for my zvd
Expo6810 said:
Is there anything i can do for my zvd
Click to expand...
Click to collapse
as far as i know. nothing
new root methods and tweaks come out everyday.
all the good devs as far as i know have stopped developing g4 and moved on due to the locked bootloader d other issues
---------- Post added at 09:24 AM ---------- Previous post was at 09:17 AM ----------
Expo6810 said:
Is there anything i can do for my zvd
Click to expand...
Click to collapse
a root method has been exposed on the g5
intime it may come for the g4 also but not adapted rite now
Expo6810 said:
Is there anything i can do for my zvd
Click to expand...
Click to collapse
Right now i have ZVC software version can i downgrade zv6????
hawzsth said:
Right now i have ZVC software version can i downgrade zv6????
Click to expand...
Click to collapse
no u will brick
TheMadScientist420 said:
no u will brick
Click to expand...
Click to collapse
its already brick any solution...... now its show 9008 no power on ...
hawzsth said:
its already brick any solution...... now its show 9008 no power on ...
Click to expand...
Click to collapse
octoplus box with jtags the only fix
thats a hardbrick
---------- Post added at 08:30 AM ---------- Previous post was at 08:29 AM ----------
Expo6810 said:
Is there anything i can do for my zvd
Click to expand...
Click to collapse
as of rite now no
If I downgrade my zva will it allow me to sim unlock it
Somebody know if can downgrade ZVI to another version
Pls any update on locked bootloader?
Thank you!
Just learned here enough. Thank you!
I just head through UsU thread after reading this; Respectively thanks for the post again! ??
So, I wanted to go back to stock, after trying multiple steps listed here in XDA-dev, and multiple youtube videos and webpages. I will list the erros bellow :
LgUP - "unknown device"... I been having issues with this software since I first attempt to run it. I tried on 2 different computers and have the same issue. Installed the DLL first (like many suggested ) then LGUP and nothing
Flashtools14 - I get the .kdz and attempt to do either "normal" or "CSE" . after comes another window, stating the progress, do not disconnect the phone .. blah blah. After going thru that it stops at 9 % and nothing happens.
After couple of weeks, I thought that if Relocking the bootloader i would be able to go into the "factory Reset" with out booting from TWRP and going back to stock..*stupid move*, and so I did... And here we are with error 1003 MODIFIED
I been looking for answers in order to fix this issue, but they go to the same path... using LGUP or FLASHtools in which both dont work with me
I have this phone
LG G4 H811 Tmobile
Now im trying to see if i can conver a KDZ into a TOT since that process I also know.
If somebody have another method please let me know!
I cant go into recovery since I keep getting the error. pretty much I have a paper weight.
An3ru said:
So, I wanted to go back to stock, after trying multiple steps listed here in XDA-dev, and multiple youtube videos and webpages. I will list the erros bellow :
LgUP - "unknown device"... I been having issues with this software since I first attempt to run it. I tried on 2 different computers and have the same issue. Installed the DLL first (like many suggested ) then LGUP and nothing
Flashtools14 - I get the .kdz and attempt to do either "normal" or "CSE" . after comes another window, stating the progress, do not disconnect the phone .. blah blah. After going thru that it stops at 9 % and nothing happens.
After couple of weeks, I thought that if Relocking the bootloader i would be able to go into the "factory Reset" with out booting from TWRP and going back to stock..*stupid move*, and so I did... And here we are with error 1003 MODIFIED
I been looking for answers in order to fix this issue, but they go to the same path... using LGUP or FLASHtools in which both dont work with me
I have this phone
LG G4 H811 Tmobile
Now im trying to see if i can conver a KDZ into a TOT since that process I also know.
If somebody have another method please let me know!
I cant go into recovery since I keep getting the error. pretty much I have a paper weight.
Click to expand...
Click to collapse
can you try this file place in c: programfiles /lge/lgup/model
ther error you got am not sure what it is this is for LGUP to recognize your phone.
raptorddd said:
can you try this file place in c: programfiles /lge/lgup/model
ther error you got am not sure what it is this is for LGUP to recognize your phone.
Click to expand...
Click to collapse
Hey Raptorddd
we read each other again, i did put those files in the C:/programFiles(x86)/LGelectronics/LGUP/model
Fire up LGUP and still have the same issue Model " uknonw " COM Ports [ COM41, GENESIS]
An3ru said:
Hey Raptorddd
we read each other again, i did put those files in the C:/programFiles(x86)/LGelectronics/LGUP/model
Fire up LGUP and still have the same issue Model " uknonw " COM Ports [ COM41, GENESIS]
Click to expand...
Click to collapse
have done a search with that specific error see if someone fix it. ?
raptorddd said:
have done a search with that specific error see if someone fix it. ?
Click to expand...
Click to collapse
Wich error you mean, the one in LGUP or The modified 1003?, Yes i have done research on both errors, but nothing seems to work.
An3ru said:
Wich error you mean, the one in LGUP or The modified 1003?, Yes i have done research on both errors, but nothing seems to work.
Click to expand...
Click to collapse
sorry i have no idea. maybe pos in thread go back to stock.
So if I understood you correctly you still have download mode?
Then it can be fixed.
If you want I can guide you through..
For this you need any Linux or best would be if just using FWUL ( http://tinyurl.com/FWULatXDA ).
I recommend to use the persistent mode version so your settings and installations survive a reboot / shutdown.
instructions:
Boot FWUL, choose language & login
Download the KDZ file you want to flash (we need to know the path later e.g. /home/android/Downloads/)
Open the folder LG
Connect device in download mode to the PC
Double click "LG laf NG" icon
Type in the new opened terminal:
sudo python2 auth.py
[*]sudo python2 partitions.py --list
If this lists your partitions then we can proceed with flashing.
Download my brand new kdz manager tool into FWUL: (right click and save as)
When you are not using the persistent mode of FWUL: plug in a big USB stick (e.g. 32 GB or more) into FWUL and extract the attached file there
When you are using the persistent mode of FWUL: just extract it in your download folder
You need to know the full path so best is copying the path from the file manager (e.g. /home/android/Downloads/ ) or leave the file manager open there
Open another terminal (black little icon in the panel)
cd and directly behind this paste the path you copied (e.g. cd /home/android/Downloads/ )
press ENTER
bash kdzmanager.sh -x FILLINFULLPATH-TO-DOWNLOADED-KDZ
(e.g. bash kdzmanager.sh -x /home/android/Downloads/h811blablubb.kdz)
once finished type:
bash kdzmanager.sh --test --flash extracteddz/
(just like this as "extracteddz" is the path generated by the kdzmanager)
This will just test flashing and not actually flash. Let me know the results of this (copy & paste output)
if you can't wait the next step would be actually flashing ofc:
WARNING: by default the kdzmanager will not overwrite userdata (which would be like a factory reset) and I would recommend to leave it out always and better choose the LG factory reset menu (after flashing completed) if required. If you still want to flash it use --with-userdata as a parameter (can take a loooong time then btw).
bash kdzmanager.sh --flash extracteddz/
sfX
Sent from my LG-H815 using XDA Labs
steadfasterX said:
So if I understood you correctly you still have download mode?
Then it can be fixed.
If you want I can guide you through..
For this you need Linux or best would be if to just use FWUL ( http://tinyurl.com/FWULatXDA ). I recommend to use the persistent mode version so your settings and installations survive a reboot / shutdown.
First instructions:
Boot FWUL, choose language & login
Download the KDZ file you want to flash
Open the folder LG
Connect device in download mode to the PC
Double click "LG laf NG" icon
Type in the new opened terminal:
sudo python2 auth.py
sudo python2 partitions.py --list
If this lists your partitions then we can proceed with the flashing.
I have to go to now but will go on tomorrow with the rest of the instructions if you want to go this way..
sfX
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Sure man i will do this and try to instal linux or go into your guide. One questions, which version of linux i need !?. I did a quick read on your post, is quite alot information to take, but i will try it!!!
Edit. I was able to download virtual box with extensions. Plug in my lg g4 and make sure that it read it. Double click on LG laf (auth) - * there is no LG laf NG* - termina opens, open new terminal type first command, ask for password - password is different than the ones mentioned in the OP - error : Python2: cant open file 'auth.py' : [Errno 2]\ No such file or directory
An3ru said:
Sure man i will do this and try to instal linux or go into your guide. One questions, which version of linux i need !?. I did a quick read on your post, is quite alot information to take, but i will try it!!!
Edit. I was able to download virtual box with extensions. Plug in my lg g4 and make sure that it read it. Double click on LG laf (auth) - * there is no LG laf NG* - termina opens, open new terminal type first command, ask for password - password is different than the ones mentioned in the OP - error : Python2: cant open file 'auth.py' : [Errno 2]\ No such file or directory
Click to expand...
Click to collapse
use his FWUL dont use linux use that one he provided. also please hit the thanks buttonto my friend steadfsterx.. on lower part right hand side..:good:
raptorddd said:
use his FWUL dont use linux use that one he provided. also please hit the thanks buttonto my friend steadfsterx.. on lower part right hand side..:good:
Click to expand...
Click to collapse
Hey Raptorddd
yeah I use the program he suggest me, im just waiting on him, also thank you for the help! I appreciate it
An3ru said:
Hey Raptorddd
yeah I use the program he suggest me, im just waiting on him, also thank you for the help! I appreciate it
Click to expand...
Click to collapse
It seems you havent downloaded the latest FWUL version v2.0? In v1 there is no LG laf NG.. But we can use that FWUL version as well. it's just very very outdated
If you want to have the best FWUL experience use v2.0 and download the persistent mode version of FWUL (it's the ZIP) and read the FAQ to make the persistent mode available in VirtualBox!
This combo is fantastic
I come back in about 3 hours to complete the guide...
sfX
Sent from my LG-H815 using XDA Labs
steadfasterX said:
It seems you havent downloaded the latest FWUL version v2.0? In v1 there is no LG laf NG.. But we can use that FWUL version as well. it's just very very outdated
If you want to have the best FWUL experience use v2.0 and download the persistent mode version of FWUL (it's the ZIP) and read the FAQ to make the persistent mode available in VirtualBox!
This combo is fantastic
I come back in about 3 hours to complete the guide...
sfX
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Oh yeah, the main download server was a lil confusing but i was able to download it, i will be out. But i will be reading the FAQ and the new set of instructions!!!!
An3ru said:
Oh yeah, the main download server was a lil confusing but i was able to download it, i will be out. But i will be reading the FAQ and the new set of instructions!!!!
Click to expand...
Click to collapse
sorry for any confusion but thx for reporting. I have updated the OP to point to the new versions more clearly.
will come back asap
OK here you go: https://forum.xda-developers.com/showpost.php?p=73756863&postcount=7
let me know how it goes
steadfasterX said:
So if I understood you correctly you still have download mode?
Then it can be fixed.
If you want I can guide you through..
For this you need any Linux or best would be if just using FWUL ( http://tinyurl.com/FWULatXDA ).
I recommend to use the persistent mode version so your settings and installations survive a reboot / shutdown.
instructions:
Boot FWUL, choose language & login
Download the KDZ file you want to flash (we need to know the path later e.g. /home/android/Downloads/)
Open the folder LG
Connect device in download mode to the PC
Double click "LG laf NG" icon
Type in the new opened terminal:
sudo python2 auth.py
[*]sudo python2 partitions.py --list
If this lists your partitions then we can proceed with flashing.
Download my brand new kdz manager tool into FWUL: (right click and save as)
When you are not using the persistent mode of FWUL: plug in a big USB stick (e.g. 32 GB or more) into FWUL and extract the attached file there
When you are using the persistent mode of FWUL: just extract it in your download folder
You need to know the full path so best is copying the path from the file manager (e.g. /home/android/Downloads/ ) or leave the file manager open there
Open another terminal (black little icon in the panel)
cd and directly behind this paste the path you copied (e.g. cd /home/android/Downloads/ )
press ENTER
bash kdzmanager.sh -x FILLINFULLPATH-TO-DOWNLOADED-KDZ
(e.g. bash kdzextract.sh -x /home/android/Downloads/h811blablubb.kdz)
once finished type:
bash kdzmanager.sh --test --flash extracteddz/
(just like this as "extracteddz" is the path generated by the kdzmanager)
This will just test flashing and not actually flash. Let me know the results of this (copy & paste output)
if you can't wait the next step would be actually flashing ofc:
WARNING: by default the kdzmanager will not overwrite userdata (which would be like a factory reset) and I would recommend to leave it out always and better choose the LG factory reset menu (after flashing completed) if required. If you still want to flash it use --with-userdata as a parameter (can take a loooong time then btw).
bash kdzmanager.sh --flash extracteddz/
sfX
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Hey steadfasterX, I download version 2 of the FWUL and still have the same error. as Sudo not found. Am I doing something wrong?! o.o
An3ru said:
Hey steadfasterX, I download version 2 of the FWUL and still have the same error. as Sudo not found. Am I doing something wrong?! o.o
Click to expand...
Click to collapse
you double clicked "LG laf NG" icon ? in this terminal u have to type the auth command
consider to come into IRC instead (channel carbon-user on freenode)
or just by clicking this link: http://webchat.freenode.net/?channels=Carbon-user
sfX
Saw something a few posts back about virtualbox or vmware...
FWIW, Historically, virtualized Linux Guests don't do so well with USB. I've always had to install it natively or use a LiveUSB distro with persistence.
barcodelinux said:
Saw something a few posts back about virtualbox or vmware...
FWIW, Historically, virtualized Linux Guests don't do so well with USB. I've always had to install it natively or use a LiveUSB distro with persistence.
Click to expand...
Click to collapse
VirtualBox plus FWUL works like a charm.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Download my brand new kdz manager tool into FWUL: (right click and save as)
When you are not using the persistent mode of FWUL: plug in a big USB stick (e.g. 32 GB or more) into FWUL and extract the attached file there
When you are using the persistent mode of FWUL: just extract it in your download folder
You need to know the full path so best is copying the path from the file manager (e.g. /home/android/Downloads/ ) or leave the file manager open there
Open another terminal (black little icon in the panel)
cd and directly behind this paste the path you copied (e.g. cd /home/android/Downloads/ )
press ENTER
bash kdzmanager.sh -x FILLINFULLPATH-TO-DOWNLOADED-KDZ
(e.g. bash kdzmanager.sh -x /home/android/Downloads/h811blablubb.kdz)
once finished type:
bash kdzmanager.sh --test --flash extracteddz/
(just like this as "extracteddz" is the path generated by the kdzmanager)
This will just test flashing and not actually flash. Let me know the results of this (copy & paste output)
if you can't wait the next step would be actually flashing ofc:
Click to expand...
Click to collapse
Your tool is far better than this one because your tool has extracted many such partitions of LG G4 H811 20o KDZ which that tool didn't. E.g. PERSISTENT, DEVINFO, MODEMST1, MODEMST2, DRM etc.
rizkhan999 said:
Your tool is far better than this one because your tool has extracted many such partitions of LG G4 H811 20o KDZ which that tool didn't. E.g. PERSISTENT, DEVINFO, MODEMST1, MODEMST2, DRM etc.
Click to expand...
Click to collapse
yea thx!!
and just checkout my new signature
.
steadfasterX said:
yea thx!!
and just checkout my new signature
Click to expand...
Click to collapse
Well. Yet another PhD thesis :good:. There is one thing that I couldn't understand though. At one place you mentioned that Hint: not wiping userdata can occur in a bootloop while at the other place you said WARNING: by default the kdzmanager will not overwrite userdata. Does it mean that flashing can cause bootloop if kdzmanager is used with default options?
Secondly, does it also support TOTs as LGUP does?