Related
ok, i recently got galaxy nexus.
it took me 6 hours to unlock it and root it. (yes i'm a total noob.. i followed the guide exactly but my computer won't install the drivers and took me more than 10 tries to finally do it).
so my nexus is rooted and running 4.0.2 NON yakuju build.
now i want to update to 4.0.4 yakuju build without losing root.
what's the simplest idiot-proof method of doing this?
i searched all over but couldn't find a simple guide.
please help me, thank you.
dlxowhd said:
ok, i recently got galaxy nexus.
it took me 6 hours to unlock it and root it. (yes i'm a total noob.. i followed the guide exactly but my computer won't install the drivers and took me more than 10 tries to finally do it).
so my nexus is rooted and running 4.0.2 NON yakuju build.
now i want to update to 4.0.4 yakuju build without losing root.
what's the simplest idiot-proof method of doing this?
i searched all over but couldn't find a simple guide.
please help me, thank you.
Click to expand...
Click to collapse
Geez 6 hours...it takes me no more than 10 minutes to unlock and root. By the way this is a question so next time you might want to stick this in the Q&A threads.
Anyway, if your unlocked you should have a recovery or something on your phone to flash ROMS, I think there is a stock rooted ZIP floating around you can use to update. But use the search and browse the development threads I'm sure you will find something.
---------- Post added at 10:37 AM ---------- Previous post was at 10:31 AM ----------
dlxowhd said:
ok, i recently got galaxy nexus.
it took me 6 hours to unlock it and root it. (yes i'm a total noob.. i followed the guide exactly but my computer won't install the drivers and took me more than 10 tries to finally do it).
so my nexus is rooted and running 4.0.2 NON yakuju build.
now i want to update to 4.0.4 yakuju build without losing root.
what's the simplest idiot-proof method of doing this?
i searched all over but couldn't find a simple guide.
please help me, thank you.
Click to expand...
Click to collapse
Did a search off IMM7k6 and found the following link. Hope that helps. Trust me searching is your friend
http://forum.xda-developers.com/showthread.php?t=1630349&highlight=imm76k
thanks but my phone is not verizon.
i got it from wind mobile... one that needs sim card inside..
is there a guide for wind mobile galaxy nexus?
Just use OTA RootKeeper to backup SU and restore it after you update.
ok i downloaded ota root keeper.
but how do i update to 4.0.4 YAKUJU?
sorry but i need a step by step instruction..
Now that you have the drivers installed, updating to anything should be easy. If you lose root, then just use the GNex toolkit to get it back. Using the toolkit, it should take somewhere around 90 seconds to root your phone.
ok that's good,
but is there a clear step-by-step instruction on how to go from 4.0.2 non-yakuju to 4.0.4 yakuju without losing root?
because all this is pretty confusing to me.
i need a step by step guide... for example:
step 1: go here and download this file
step 2: connect your phone to your pc
step 3: put this file into ...
etc..
dlxowhd said:
ok i downloaded ota root keeper.
but how do i update to 4.0.4 YAKUJU?
sorry but i need a step by step instruction..
Click to expand...
Click to collapse
If you want to switch to yakju 4.0.4, see here.
If you want to update your non-yakju build to 4.0.4, see if the update is available here.
To root, after either method (given your bootloader is unlocked), follow method 1 here.
thank you efrant,
so if i understand correctly, i should follow your 2nd link and just skip the 1st link, right?
and how do i find out what version mine is?
i know it's not official yakju but i don't know if it's yakjuxx or yakjukkk or something else.
dlxowhd said:
thank you efrant,
so if i understand correctly, i should follow your 2nd link and just skip the 1st link, right?
Click to expand...
Click to collapse
No, that's not what I was saying.
I was saying if you want to convert to yakju, follow the first link. You will be on yakju and 4.0.4. I would recommend this.
If you do not want to switch to yakju (i.e., you want to keep your current non-yakju build), then see if the 4.0.4 update is available for your build in the second link.
dlxowhd said:
and how do i find out what version mine is?
i know it's not official yakju but i don't know if it's yakjuxx or yakjukkk or something else.
Click to expand...
Click to collapse
Look in this file and see what it says: /system/build.prop
ok,
i definately want yakju so i will follow the 1st link and ignore the 2nd link.
my phone just ran out of battery so i will have to go home first then charge it and try it out!
if i get stuck or screw up, please help me!
thank you so much.
hi,
ok i'm stuck.
i'm doing the part C of your guide.
you said extract the file and there should br 6 files ending with .img.
so i got those 6 files and put them into a folder (i named the folder 'yakju').
but where does this folder go?
do i put this folder onto my phone's sd card? or do i just leave it on my pc (they are inside my 'document' folder).
then your guide says : 8) Open a command prompt in the same directory and do the following:
but where do i open a command prompt?
in C:\android-sdk-windows\platform-tools?
dlxowhd said:
hi,
ok i'm stuck.
i'm doing the part C of your guide.
you said extract the file and there should br 6 files ending with .img.
so i got those 6 files and put them into a folder (i named the folder 'yakju').
but where does this folder go?
do i put this folder onto my phone's sd card? or do i just leave it on my pc (they are inside my 'document' folder).
then your guide says : 8) Open a command prompt in the same directory and do the following:
but where do i open a command prompt?
in C:\android-sdk-windows\platform-tools?
Click to expand...
Click to collapse
Everything stays on your PC. You need to put the files from the attachment in the same folder as the .img files. Then you open a command prompt in THAT directory.
Did you read the whole post before starting like it was stated at the beginning?
Sent from my Galaxy Nexus using Tapatalk 2
ok i open the command prompt in that directory and when i type 'fastboot devices', it says 'fastboot is not recognized as an internal or external command, operable program or batch file'.
dlxowhd said:
ok i open the command prompt in that directory and when i type 'fastboot devices', it says 'fastboot is not recognized as an internal or external command, operable program or batch file'.
Click to expand...
Click to collapse
That's probably because you didn't unzip the files in the attachment into the same directory.
Sent from my Galaxy Nexus using Tapatalk 2
ok, i followed your download link, and downloaded 'Factory Images "yakju" for Galaxy Nexus "maguro"'
then i got 'yakju-imm76i-factory-8001e72f.tar' file... but your guide says .tgz file?
so maybe i downloaded a wrong file.
anyway, then i unzipped it with 7zip and i got this folder called 'yakju-imm76i-factory-8001e72f'
inside that folder, i get this file 'yakju-imm76i-factory-8001e72f' with no file extension.
then i upzipped that file with 7zip and i get this folder named 'yakju-imm76i'.
inside that folder, i have bootloader-maguro-primela03.img, flash-all.sh, flash-base.sh, radio-maguro-i9250xxla02.img and image-yakju-imm76i.zip.
so i unzip image-yakju-imm76i.zip and i get this folder called image-yakju-imm76i and inside that folder i have 5 files : userdata.img, android-info.txt, boot.img, recovery.img, and system.img..
so where do i open a command prompt?
right now my folder structure/tree looks like this:
libraries -> documents -> yakju-imm76i-factory-8001e72f -> yakju-imm76i-factory-8001e72f~ -> yakju-imm76i -> image-yakju-imm76i
ok i think i may have found the problem.
your guide says: '2) Download the attachment from this post and extract the contents to the directory created in step 1.'
but there is no actual link.
can you please verify?
Lol. Think of the bright side guys. At least you're not doing it for him. You'd probably be getting calls at 4am. No offense op. First time is the hardest. But after the first the learning curve is easier.
let it be.
hi @rbiter.
can you please verify?
efants' guide says "'2) Download the attachment from this post and extract the contents to the directory created in step 1.''
but there is no actual link... right?
Scroll down and download that. Extract those files, platform tools into the folder you just made. That platform tools will be very important from here on out.
let it be.
I absolutely do not understand the flashing firmware. I'm att, on 3.19, supercid, rooted, s-off with no access to a computer. I read in some places you don't need one and I see that some people say you do, idk. I'm absolutely lost on it. All I know is to put the zip in the root of my file. I'm not certain on what zip, I know to reboot into fastboot to flash and update but afterward, I read You have to flash a dev rom or something. Idk. I'm still obviously new at the unlocked thing but I'm really good at understanding how to do most things on here or I wouldn't be where I'm at now. Help please!!!!!!
Blundog said:
I absolutely do not understand the flashing firmware. I'm att, on 3.19, supercid, rooted, s-off with no access to a computer. I read in some places you don't need one and I see that some people say you do, idk. I'm absolutely lost on it. All I know is to put the zip in the root of my file. I'm not certain on what zip, I know to reboot into fastboot to flash and update but afterward, I read You have to flash a dev rom or something. Idk. I'm still obviously new at the unlocked thing but I'm really good at understanding how to do most things on here or I wouldn't be where I'm at now. Help please!!!!!!
Click to expand...
Click to collapse
You want Lollipop firmware I suppose? Do you know your MID? What carrier and country? I can hook you up. I'd ask for you firmware version that you have now, but I assume you don't know. If you do, that would be all the info I need.
Blundog said:
I absolutely do not understand the flashing firmware. I'm att, on 3.19, supercid, rooted, s-off with no access to a computer. I read in some places you don't need one and I see that some people say you do, idk. I'm absolutely lost on it. All I know is to put the zip in the root of my file. I'm not certain on what zip, I know to reboot into fastboot to flash and update but afterward, I read You have to flash a dev rom or something. Idk. I'm still obviously new at the unlocked thing but I'm really good at understanding how to do most things on here or I wouldn't be where I'm at now. Help please!!!!!!
Click to expand...
Click to collapse
because you are in super cid, and s-off so you can flash any FW , you can refer thread Firmware Flashing without the panic attacks...
Instructions:
1. Download firmware of choice in above links
2. Rename firmware to 0P6BIMG.zip (the first character is a zero, NOT A LETTER O)
3. Put renamed firmware.zip on your external_SD
4. Boot into your bootloader and make sure your in hboot and let it update its firmware.
5. No PC, no adb, no fastboot, no terminal is needed, just a root explorer to rename and transfer the renamed firmware file to external_sd
6. After you have updated your firmware, make sure to remove the 0P6BIMG.zip from your external_sd because it will ask to update your firmware everytime your reboot to your bootloader which it is technically supposed to do but its unnecessary after you have done it once (unless you are planning on flashing firmware again).
7.Profit!
Huntervn said:
because you are in super cid, and s-off so you can flash any FW , you can refer thread Firmware Flashing without the panic attacks...
Instructions:
1. Download firmware of choice in above links
2. Rename firmware to 0P6BIMG.zip (the first character is a zero, NOT A LETTER O)
3. Put renamed firmware.zip on your external_SD
4. Boot into your bootloader and make sure your in hboot and let it update its firmware.
5. No PC, no adb, no fastboot, no terminal is needed, just a root explorer to rename and transfer the renamed firmware file to external_sd
6. After you have updated your firmware, make sure to remove the 0P6BIMG.zip from your external_sd because it will ask to update your firmware everytime your reboot to your bootloader which it is technically supposed to do but its unnecessary after you have done it once (unless you are planning on flashing firmware again).
7.Profit!
Click to expand...
Click to collapse
Yeah.....He still needs to know the info I asked him about.
Plus when he said "place it in the root of my file" shows he already looked at that thread or one similar. He doesn't understand it, so by sending him back to the thread, you're not really helping him much.
I'm not trying to rag on you, I'm just trying to help you to help others.
xunholyx said:
Yeah.....He still needs to know the info I asked him about.
Plus when he said "place it in the root of my file" shows he already looked at that thread or one similar. He doesn't understand it, so by sending him back to the thread, you're not really helping him much.
I'm not trying to rag on you, I'm just trying to help you to help others.
Click to expand...
Click to collapse
I appreciate the help. I was able to update my firmware first try. I vaguely remembered watching my friend do it to 4.4.4 a while back and when I started doing it I would remember but couldn't have gotten started without help on here. Now, I'm attempting to update twrp. I'm on 2.8.3 and need it to 2.8.4. I've downloaded flashify and have terminal emulator up but not sure where to go from here?
Blundog said:
I appreciate the help. I was able to update my firmware first try. I vaguely remembered watching my friend do it to 4.4.4 a while back and when I started doing it I would remember but couldn't have gotten started without help on here. Now, I'm attempting to update twrp. I'm on 2.8.3 and need it to 2.8.4. I've downloaded flashify and have terminal emulator up but not sure where to go from here?
Click to expand...
Click to collapse
Ha! I did it. Thanks for the help guys, much appreciated
Blundog said:
I appreciate the help. I was able to update my firmware first try. I vaguely remembered watching my friend do it to 4.4.4 a while back and when I started doing it I would remember but couldn't have gotten started without help on here. Now, I'm attempting to update twrp. I'm on 2.8.3 and need it to 2.8.4. I've downloaded flashify and have terminal emulator up but not sure where to go from here?
Click to expand...
Click to collapse
Don't use flashify. Download this onto your phone. It's the official TWRP 2.8.4.0
Rename it to "twrp.img" (no quotes) and move it from downloads onto the root of your internal storage using a file explorer. (I recommend ES File Explorer) By root of, I mean not in a folder, just on the internalSD.
Open terminal emulator and type:
su (hit enter)
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p43 (hit enter and don't screw up that command, copy and paste recommended)
That will bring you up to the newest version.
EDIT: I saw you solved your issue while I was trying to respond. :good:
xunholyx said:
Don't use flashify. Download this onto your phone. It's the official TWRP 2.8.4.0
Rename it to "twrp.img" (no quotes) and move it from downloads onto the root of your internal storage using a file explorer. (I recommend ES File Explorer) By root of, I mean not in a folder, just on the internalSD.
Open terminal emulator and type:
su (hit enter)
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p43 (hit enter and don't screw up that command, copy and paste recommended)
That will bring you up to the newest version.
EDIT: I saw you solved your issue while I was trying to respond. :good:
Click to expand...
Click to collapse
Yeh, thanks for the help. I didn't use flashify, I used the app, actually. At first it said unsuccessful but I rebooted into recovery and it was updated. A little weird but whatevr works, I guess. So if I put the. IMG on the root of my sdcard I can't use hboot ?
Blundog said:
Yeh, thanks for the help. I didn't use flashify, I used the app, actually. At first it said unsuccessful but I rebooted into recovery and it was updated. A little weird but whatevr works, I guess. So if I put the. IMG on the root of my sdcard I can't use hboot ?
Click to expand...
Click to collapse
Yes! That happens to me too. I almost always use the TWRP Manager app, and it almost always crashes, but I think the crash only happens when it tries to get back into the app after the flash. It's buggy, but it works. After the crash, the new version is always installed.
Talk about mini heart attack! Awesome!!
hi, tried to search everywhere but to no avail soo far.. does anyone knows if there is an existing root guide for LG G4 Beat? its sort of a diff model but there's no sub for it so i guess ill put it at here since its still under G4 family.. :/
Do you have Android 5.0 or 5.1 installed?
First of all. Before you start to try root, download the kdz file for your phone.
The kdz is needed if something went wrong (e.g. phone not booting).
You can use the LG Flash Tool to flash the kdz to a bricked phone.
Use this link with your IMEI:
Code:
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=IMEI
If it works, please post the download link for the "kdz".
Or better post the output too, but delete your IMEI!
Your link will only work if you type:
csmgdl.lgmobile.com/dn/downloader.dev?fileKey=
and then add the rest of your url instead of the given link.
It's worth trying. You need to get a partition layout. Then @autoprime will give a full command to run in DL mode for dumping the system image, and flashing it once it's been injected with root. I can inject it for you once you have the system.img dump.
I wrote an guide how you can extract the GPT and calculate the dd parameters:
[How to] Determine dd Parameters For All LG G4 Models
http://forum.xda-developers.com/g4/h...lg-g4-t3184867
Do you know how to work with linux?
Please post the outputs of gdisk into a HIDE and CODE tag. Thank you.
Maybe you are a advanced user and can Inject root yourself with the autoroot.sh method (Inject_Root_G4.zip)?
Or do you need help?
I think you have Android 5.1.1 installed, so it is not possible to use Kingroot to root your device. Is that right?
dominik-p said:
I wrote an guide how you can extract the GPT and calculate the dd parameters:
[How to] Determine dd Parameters For All LG G4 Models
http://forum.xda-developers.com/g4/h...lg-g4-t3184867
Do you know how to work with linux?
Click to expand...
Click to collapse
Wow, thanks for that guide! I've been trying to figure out how to find the right dd params forever.
tabp0le said:
Wow, thanks for that guide! I've been trying to figure out how to find the right dd params forever.
Click to expand...
Click to collapse
Pleasure.
I think some people also knew how to do it, but no one wanted to write a guide.
AND ALWAYS CONSIDER:
You can brick your phone if you don't know what you are doing.
Backup your files before you change anything.
i think i got the link for the KDZ.. but when i
dominik-p said:
Do you have Android 5.0 or 5.1 installed?
First of all. Before you start to try root, download the kdz file for your phone.
The kdz is needed if something went wrong (e.g. phone not booting).
You can use the LG Flash Tool to flash the kdz to a bricked phone.
Use this link with your IMEI:
[CODEcsmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=IMEI[/CODE]
If it works, please post the download link for the "kdz".
Or better post the output too, but delete your IMEI!
Your link will only work if you type:
csmgdl.lgmobile.com/dn/downloader.dev?fileKey=
and then add the rest of your url instead of the given link.
Click to expand...
Click to collapse
ok i think i did it correctly.. heres the link
downloader.dev?fileKey=FWDEYI0132FMAUI263CCLO1/H73510b_00.kdz (had to cut it short cuz forum would not let me post new link :/ csmgdl.lgmobile.com/dn/ was before 'downloader')
heres the output file..
<response req_cmd="auth_model_check" status="OK">
<auth_model_check><result>OK</result>
<esn>-----MYIMEI----</esn>
<model>LGH735</model><suffix>ASEATS</suffix><msn>508KPUU032390</msn><esn_date/>
<sw_version>H73510B_00</sw_version>
<sw_url>fileKey=FWDEYI0132FMAUI263CCLO1/H73510b_00.kdz</sw_url> pkg03.lime.gdms.lge.com/dn/downloader.dev?
<sw_locale_url/><sw_recommand_uri/><app_version/><app_url/>
<cs_em_flag>N</cs_em_flag>
<cs_em_uri>N</cs_em_uri>
<chip_type>EG</chip_type>
<prod_type>2</prod_type>
<buyer>SEA</buyer>
<file_name>H73510b_00.kdz</file_name>
</auth_model_check></response>
and yes its 5.1..
would be nice if theres a step by step guide cuz last phone i tired rooting was prolly galaxy tab and it was wayy easier :/
Ok, well done. Is 10b the same version as currently installed on your device?
Some other details would be interesting:
Do you have an unbranded device?
Where did you buy it / where do you live? (country)
Are you an advanced user? Do you know how to work with linux?
The next steps will be:
Calculate your dd parameters and backup your system partition into a img file. Read my guide:
[How to] Determine dd Parameters For All LG G4 Models
http://forum.xda-developers.com/g4/h...lg-g4-t3184867
Please post the outputs of gdisk into a HIDE and CODE tag.
Post your calculated dd parameters, so that we can verify it.
IMPORTANT: Keep the original (unchanged) system.img on your computer (zip it).
Then:
Copy the img file to a linux system and mount it. Create a testfile (test.txt) on the mounted system partition.
Copy the img file back to your phone and try to "dd" it back over your system partition.
Check if you see the testfile on your system partition.
If that worked you have successfully overwritten your system partition.
Then:
Try to inject root with the Inject_Root_G4.zip on your linux system.
Copy the new img file to your phone and "dd" it over your system partition.
Please ask if you are not 100% sure what to do.
You are responsible for what you are doing with your device.
Backup all your data (photos, videos, messages...) before going one step further.
dominik-p said:
Ok, well done. Is 10b the same version as currently installed on your device?
Some other details would be interesting:
Do you have an unbranded device?
Where did you buy it / where do you live? (country)
Are you an advanced user? Do you know how to work with linux?
The next steps will be:
Calculate your dd parameters and backup your system partition into a img file. Read my guide:
[How to] Determine dd Parameters For All LG G4 Models
http://forum.xda-developers.com/g4/h...lg-g4-t3184867
Please post the outputs of gdisk into a HIDE and CODE tag.
Post your calculated dd parameters, so that we can verify it.
IMPORTANT: Keep the original (unchanged) system.img on your computer (zip it).
Then:
Copy the img file to a linux system and mount it. Create a testfile (test.txt) on the mounted system partition.
Copy the img file back to your phone and try to "dd" it back over your system partition.
Check if you see the testfile on your system partition.
If that worked you have successfully overwritten your system partition.
Then:
Try to inject root with the Inject_Root_G4.zip on your linux system.
Copy the new img file to your phone and "dd" it over your system partition.
Please ask if you are not 100% sure what to do.
You are responsible for what you are doing with your device.
Backup all your data (photos, videos, messages...) before going one step further.
Click to expand...
Click to collapse
what do u mean 10b?
not really unbranded i guess? its a mid-tier version of the LG G4.. this is the phone.. http://www.lg.com/sg/mobile-phones/lg-G4-Beat
dont think its out at the US yet
bought it at Singapore as i recontacted my phone
nope i dont know how to use linux and im %100 not sure what to do :crying:
Ok so you are not a advanced user?
10b is the version of the kdz file. Goto Settings->Phone info->software version on your phone and post your software version.
First of all: It is not possible to root your phone without linux!
You don't have to install a linux on your computer (physically) but at least in an virtual environment (virtualbox, vmware player) or as a live distribution.
What you can do without linux is try to extract the GPT.
Which OS is installed on your computer (Win 7, 8, 10)?
Download the LG_Root.zip from
http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
It contains the Send_Command.exe
You need this tool to open a special console when your phone is in download mode.
Do you know this tool and how to enter the download mode?
dominik-p said:
Ok so you are not a advanced user?
10b is the version of the kdz file. Goto Settings->Phone info->software version on your phone and post your software version.
First of all: It is not possible to root your phone without linux!
You don't have to install a linux on your computer (physically) but at least in an virtual environment or as a live distribution.
What you can do without linux is try to extract the GPT.
Which OS is installed on your computer (Win 7, 8, 10)?
Download the LG_Root.zip from
http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
It contains the Send_Command.exe
You need this tool to open a special console when your phone is in download mode.
Do you know this tool and how to enter the download mode?
Click to expand...
Click to collapse
no im not an advanced user..
its software version is : V10b-SEA-XX
so i guess its a 10b?
im using windows 7 right now
Yes you have 10b installed now.
The XX means that it is unbranded.
SEA means southeast asia.
Win 7 is fine. Send_Command will work.
Download the zip from the above-mentioned thread.
Then:
Power off your device
When the device is powered off, hold volume up and insert a USB cable connected to the PC
Wait for the drivers to install
Click to expand...
Click to collapse
and follow the steps 7-9.
dominik-p said:
Yes you have 10b installed now.
The XX means that it is unbranded.
SEA means southeast asia.
Win 7 is fine. Send_Command will work.
Download the zip from the above-mentioned thread.
Then:
and follow the steps 7-9.
Click to expand...
Click to collapse
so i just download it, put it at desktop and skip all the methods till 6-9? do i have to enable developer mode before doing it?
No you don't need developer mode.
But it is no problem if you enabled it.
Are you able to open the console with Send_Command.exe?
dominik-p said:
No you don't need developer mode.
But it is no problem if you enabled it.
Are you able to open the console with Send_Command.exe?
Click to expand...
Click to collapse
i opened send_command.exe but it just closes back.. mine is at COM1 but idk how to change it
Update: it says NOTE: Do not attempt this on devices with 5.1.1 , at the time this method was posted it worked on many firmware 5.0.2 should i still go for it? im using 5.1.1
We won't follow the guide. We will do it like here:
http://forum.xda-developers.com/g4/orig-development/root-tmo-vzw-intl-variants-soon-root-lg-t3164765
(You will also find the thread is linked there.)
The thread is just a good help for the Send_Command tool.
You don't have to change the COM port.
Are you in download mode? Do you see the "Firmware Update" screen?
Use the ports.bat and note the "netdiag" COM port.
Inside of LG_Root folder hold shift and right click a blank space you should see "Open command window here"
Click to expand...
Click to collapse
Then enter:
Code:
Send_Command.exe \\.\COM#
Replace # with your number.
dominik-p said:
We won't follow the guide. We will do it like here:
http://forum.xda-developers.com/g4/orig-development/root-tmo-vzw-intl-variants-soon-root-lg-t3164765
(You will also find the thread is linked there.)
The thread is just a good help for the Send_Command tool.
You don't have to change the COM port.
Are you in download mode? Do you see the "Firmware Update" screen?
User ports.bat and note the "netdiag" COM port.
Then enter:
Code:
Send_Command.exe \\.\COM#
Replace # with your number.
Click to expand...
Click to collapse
Yup its in download mode i have the firmware update on my screen.. still to no avail i also installed LG driver and restarted.. opened send_command.exe it just closes back
or do i just enter the script after the # after special command? at because im now at this part http://i.imgur.com/fre9Z9l.png just that when i double-click send command it just closes back
dreamnoob said:
Yup its in download mode i have the firmware update on my screen.. still to no avail i also installed LG driver and restarted.. opened send_command.exe it just closes back
or do i just enter the script after the # after special command? at because im now at this part http://i.imgur.com/fre9Z9l.png just that when i double-click send command it just closes back
Click to expand...
Click to collapse
are you opening send command from the command prompt?
Do NOT double click on the Send_Command.exe
READ again:
Inside of LG_Root folder hold shift and right click a blank space you should see "Open command window here"
Click to expand...
Click to collapse
Then enter "Send_Command.exe \\.\COM#"
dominik-p said:
Do NOT double click on the Send_Command.exe
READ again:
Then enter "Send_Command.exe \\.\COM#"
Click to expand...
Click to collapse
oh okay means im on the right path..
so now i just do this as follows?
Type "id" and press enter (no quotes).
You should get back some text starting with "uid=(0)root gid=(0)root". If not, press CTRL-C, and do step 9 again (the application sometimes doesn't respond on the first command).
Run the command specified in the section below titled 'Commands to Run' to flash the rooted system image.
After a few minutes of sitting, you should get back a "#" prompt. This indicates the process has finished.
Type "LEAVE" (no quotes) and press enter. Your phone should reboot, and your phone will be rooted.
[OBSOLETE THREAD]
This thread is obsolete. A solution was found, which is posted here:
http://forum.xda-developers.com/g4/help/method-to-root-lg-g4s-model-h735-lg-g4-t3248030
Please use the new thread for discussions.
------------------------
Original thread:
------------------------
Hi,
I have been trying to root the LG G4S (H735), also known as "LG G4 Beat".
I tried two things:
Approach 1
I tried the method posted by konsolen in this thread:
http://forum.xda-developers.com/g4/general/lg-g4s-world-root-lg-devices-t3231759
but it didn't work for me. I tried several times with varying approaches, but the boot process always gets stuck on the LG logo.
Approach 2
I also tried to inject the root as suggested in this thread for the G4:
http://forum.xda-developers.com/g4/help/rooting-lg-h735-g4-beat-t3192491
I've used the Inject_Root_G4.zip from this link, which I believe is the same shared elsewhere:
https://mega.nz/#!BIxUzbqI!nt2YnGnGQlSiBQ-Ar-c-q7oDMIEsg6xd0Kmek-q0clg
And I get the same problem - stuck on the LG logo when booting.
For anyone who wants to reproduce Approach 2 to maybe find a solution:
1. Start up LGFlashTool2014. You can follow instructions in thread by konsolen (see Approach 1 above). You can use his .kdz file as well. Important: Pull out your USB cable as soon as the green letters COMX (with a number instead of X) appear on the phone. My flashtool actually didn't display the progress percentage, but apparently this at 9%. It doesn't matter if you don't see the percentage though, I've verified with this KDZ image that if you pull the cable at the very moment the green letters appear, nothing is corrupted. The phone will still display 0%. Leave it as it is after you unplugged the cable.
2. Kill your flash tool with the windows task manager. After it closed, you can plug the phone back in and open a windows command line in the folder where your Send_Command.exe is (you can download the package in konsolen's instructions which contains Send_Command.exe as well).
3. Open the console to your phone with
Code:
Send_Command.exe \\.\COMX.
(with your number instead of X)
You will have to do steps 1-3 every time you want to get this console, for example to run all the dd commands below.
4. Calculate the dd parameters and backup your system partition into a .img file. There is an excellent guide by dominik-p for how to determine your individual dd parameters:
http://forum.xda-developers.com/g4/help/how-to-determine-dd-parameters-lg-g4-t3184867
5. Keep a copy of your system.img somewhere safe, you can use it to restore your system if something goes wrong. So don't use this original in the next steps!
6. Copy the .img file to a linux system and mount it. I'm guessing who is trying this knows how to do this. Anything you change in the folder you mounted the image on, will be saved in the image. You can then use this updated image to overwrite your original system partition, again with dd (as described in the thread by dominik-p) using your parameters. So here's the crucial bit: You get root access to your system files via linux. When you know the right things to mess with, you can root your phone with the updated image. Injecting the root as done in step 8 is one way to change the system on the G4 in order to root it.
7. [Optional] If you are new to this, you may want to do a simple test before you continue.
Create a testfile (test.txt) on the mounted system partition. Then copy the .img file back to your phone and try to "dd" it back over your system partition.
Then, check if you see the test file on your system partition -- you may have to reboot the phone after the dd command (and log back in with Send_Command.exe) in order to see the updates.
8. Inject root with the Inject_Root_G4.zip on the mounted folder of the image on your linux system. You can follow instructions (Step 2) here:
http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586
9. Copy the new img file to your phone and "dd" it over your system partition, using your own dd parameters.
10. Reboot the phone (you can also just type LEAVE in the Send_Command.exe console).
Now, it should be rooted - if it worked for you!
If it worked for you, that's great. It didn't for me, it got stuck on the LG logo in the boot process again. So I had to write my original system.img back onto my system partition to get the phone back.
I did get the following errors in Step 8 above, though I did try anyway to use the resulting image. The errors may have something to do with my problem, but it may also be because the inject root is for the G4, not the G4s.
Code:
sudo ./autoroot.sh
cp: cannot create regular file ‘operatingtable/lib64/libsupol.so’: No such file or directory
chmod: cannot access ‘operatingtable/lib64/libsupol.so’: No such file or directory
chcon: cannot access ‘operatingtable/lib64/libsupol.so’: No such file or directory
chmod: cannot access ‘operatingtable/bin/app_process64_original’: No such file or directory
chcon: cannot access ‘operatingtable/bin/app_process64_original’: No such file or directory
chmod: cannot access ‘operatingtable/bin/app_process_init’: No such file or directory
chcon: cannot access ‘operatingtable/bin/app_process_init’: No such file or directory
If anyone finds a solution to this, or has any ideas what could be tried, I would be very interested to hear it. I'm new to rooting phones and don't have much experience beyond what I did in the last days.
Cheers
Jennifer
jen.magnolis said:
4. Calculate the dd parameters and backup your system partition into a .img file. There is an excellent guide by @dominik-p for how to determine your individual dd parameters:
http://forum.xda-developers.com/g4/help/how-to-determine-dd-parameters-lg-g4-t3184867
Click to expand...
Click to collapse
Happy that my guide has helped you
As I said here:
http://forum.xda-developers.com/g4/help/rooting-lg-h735-g4-beat-t3192491/page5
Everyone who is interested to inject root must edit the autoroot.sh from the inject.zip and use the correct files from SuperSU
More information about the files:
https://su.chainfire.eu
Maybe you have to use other files. Not the files from the inject.zip
Download the Update-SuperSU zip from http://download.chainfire.eu/supersu
Copy the files you need to the "su" folder of the extracted inject.zip
For information which files are needed read the "update-binary" file from the SuperSU zip.
(located here META-INF/com/google/android/update-binary)
Good luck everyone :good:
Thanks again for the links! I'll try again soon, when I get time for it, and report the results here
By the way, here's the ls -lR of my system.
Ok, no problem, take your time.
I've got also lot of other work to do...
I just read your system.txt (thanks)
According to these lines:
Code:
lrwxr-xr-x. 1 root 2000 13 Aug 24 02:05 app_process -> app_process32
-rwxr-xr-x. 1 root 2000 13588 Aug 24 02:05 app_process32
It seems that the firmware is 32 bit.
More info about your firmware is in /system/build.prop
So you have to take the right lines from update-binary and copy them and edit the autoroot.sh
Please don't ask me which lines. It's a bit difficult... (you have to understand the logic in update-binary)
Then copy the files from the right folder (arm?) to the "su" folder.
Sorry. I'm out now here for the next time. I have a H815 and happy with it.
I think you will find the solution. :good:
Custom Recoverys
Hi All
Are there any custom recovery's for the G4 beat/G4s
Thanks
Thanks dominik-p for your help. Good luck with your other work, don't worry I won't distract you with asking questions You already helped a lot.
benji5688, you can check for official firmware (.kdz file) on this link, pasting your IMEI instead of YOUR-IMEI in the link below.
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=YOUR-IMEI
I did not find any for mine there, but I did find it on
http://devtester.ro/projects/lg-firmwares/
Which brought me to this link where I could find mine:
http://pkg02.azure.gdms.lge.com/dn/downloader.dev?fileKey=FW703UV132GQAUP7A0ED99N/H73510c_00.kdz
but you should look for your specific model.
jen.magnolis said:
Hi,
I have been trying to root the LG G4S (H735), also known as "LG G4 Beat".
I tried two things:
Click to expand...
Click to collapse
LOL
I did the exact same thing as you, and really the EXACT, I also contacted dominik-p for the same problem you got with the bs. LOL
Was about to do the same thing you did here too just told that to dominik-p lol.
You post is great, well detailled. Hope someone found something
But got something different. my phone is the LGH731 LG G4 Vigor from Videotron in Canada.
If someone need files or system.img LINK
That's not the exact same thing as the post owner but i'm pretty sure the root method will be. (DON'T use this system.img to inject in you H735) it's from a H731 and they don't have the same partition size.
Ha, that's funny, and you got the same problem of course (frozen logo boot).
We will find a solution. It's just a matter of time. I'm a bit pressed for work in the next days but I'll get back into it around mid week. I think the main problem was, as I suspected and also as dominik-p pointed out, we've been using the wrong inject files. And the G4s is 32 bit so obviously it won't work with 64 bit libs.
First thing I'll try is using the other files from the link dominik-p shared. I'll also read the guide and try to understand which files need to be changed to gain root access in general, i.e. learn the basics of how to root. Then I think/hope I'll be able to fix this. And finally get to move all my stuff onto SD and get my storage back
Meanwhile, if you get any new results, let me know.
Cheers
jen.magnolis said:
Ha, that's funny, and you got the same problem of course (frozen logo boot).
We will find a solution. It's just a matter of time. I'm a bit pressed for work in the next days but I'll get back into it around mid week. I think the main problem was, as I suspected and also as dominik-p pointed out, we've been using the wrong inject files. And the G4s is 32 bit so obviously it won't work with 64 bit libs.
First thing I'll try is using the other files from the link dominik-p shared. I'll also read the guide and try to understand which files need to be changed to gain root access in general, i.e. learn the basics of how to root. Then I think/hope I'll be able to fix this. And finally get to move all my stuff onto SD and get my storage back
Meanwhile, if you get any new results, let me know.
Cheers
Click to expand...
Click to collapse
Yes i'm trying this today (the 32-64 bits thing)
Custom recovery
What does this file do though?
Is it a custom recovery or is it the stock rom?
Thanks Benji
benji5688 said:
What does this file do though?
Is it a custom recovery or is it the stock rom?
Thanks Benji
Click to expand...
Click to collapse
It's the stock ROM. It can be used for recovery, depending what your problem is. If you destroyed your ROM by trying to root, you can recover with this.
If you mess with something in your system partition (where the Android OS is installed), you'd need a copy of your individual system partition (like a "backup") to restore. This highly depends on your phone/version, so you have to do this backup yourself. You can follow the instructions with the dd parameters, linked to from the main thread.
Are there any custom recoverys
Hi
Are there any custom recovery available, I want to get Xposed.
Can anyone make one?
Thanks for all the help
benji5688 said:
Hi
Are there any custom recovery available, I want to get Xposed.
Can anyone make one?
Thanks for all the help
Click to expand...
Click to collapse
I far as I know to get Xposed you need to be rooted... Well there is no root method availaible, well you can try the methods that Jen explained here but I doubt they will work... if yes, you lucky ****
Is the g4s running marshmallow? Is so you would need to use a compatible su install.
Sent from my VS986 using XDA Free mobile app
larsdennert said:
Is the g4s running marshmallow? Is so you would need to use a compatible su install.
Sent from my VS986 using XDA Free mobile app
Click to expand...
Click to collapse
No the problem is really just changing the 64 bits command to make then use the 32 bits ones
I manage everything except this one
Code:
chcon --reference=operatingtable/bin/app_process32 operatingtable/bin/app_process64_original
I agree with xsteacy, this will most likely not work, that's why we opened this discussion
We just have to find the right files to use (instead of the 64 bit ones).
I will get back onto the subject by Wednesday when I have time.
I solved it! My phone is rooted
I asked someone to test my script before I post the results. Hang on there, tomorrow I'll post the solution.
Good times!
jen.magnolis said:
I solved it! My phone is rooted
I asked someone to test my script before I post the results. Hang on there, tomorrow I'll post the solution.
Good times!
Click to expand...
Click to collapse
0.0 OH!?
Ok I'm putting it out there for others to test as well.
Please report if it worked so I can take this into account before updating the main thread instructions.
In the attached .zip file there is a README with instructions.
Note: Thanks goes to @konsolen who shared instructions on how to open the COM port on the H735.
The script in konsolens post is essentially the upater-binary script of the SuperSU package, but with a few modifications.
That may have been necessary on konsolens phone, but it didn't work on mine. For me, using the original script worked.
However, the zip file has to be extracted manually with busybox before the updater-binary script is started. I am not
sure if busybox absolutely needs to be in the /sbin folder, but that's where I saw elsewhere that it belonged, so
I moved it over there in my script. I haven't tested this with busybox being elsewhere.
Thanks goes also to @dominik-p for sharing the link to excellent documentation and for his instructions on how
to make a backup (with dd) of your system, in case anything goes wrong.
UPDATE: I did all commands in root_lgh375.sh manually when I found it already worked, so please report if all is good with the script, but I think it should be, it only does what I did manually.
Congratulations @jen.magnolis
Well done
I just downloaded to my XT1575 and I don't know which directory it downloaded to? Any ideas?
glfngmble said:
I just downloaded to my XT1575 and I don't know which directory it downloaded to? Any ideas?
Click to expand...
Click to collapse
/data/data/org.lineageos.updater/app_updates
jhedfors said:
/data/data/org.lineageos.updater/app_updates
Click to expand...
Click to collapse
Thank You.
There is no folder /app_updates. There is just a folder named "files", but this folder is completely empty.
By the way: I got this file structure on my G4: \Android\data\org.lineageos.updater\files.
I had to manually download the package and install it manually in recovery, but the updater says still to update the current version.
rigattoni said:
There is no folder /app_updates. There is just a folder named "files", but this folder is completely empty.
By the way: I got this file structure on my G4: \Android\data\org.lineageos.updater\files.
I had to manually download the package and install it manually in recovery, but the updater says still to update the current version.
Click to expand...
Click to collapse
/data/data/org.lineageos.updater/app_updates
The updater does not recognize what version is installed, just if the update is in the folder.
jhedfors said:
/data/data/org.lineageos.updater/app_updates
The updater does not recognize what version is installed, just if the update is in the folder.
Click to expand...
Click to collapse
If this is reduced to this single folder I can say that my G4 has no folder with this name.
The download completed and the updater asks for updating the unit.
The G4 restarts into recovery mode and nothing happens. Manual search for the downloaded files have not been successful.
I restarted my G4 and searched manually with root rights (just to be sure the files are not hidden in non root search) and I could not find any update file.
The lineage updater still shows to update the phone, even that there whether is a folder named "/data/org.lineageos.updater/app_updates"
nor a file in the "\data\org.lineageos.updater\files.
So... is this an issue with the updater, ROM or is this just not implemented complete?
I have no issues to manually install anything by console or TWRP or what ever else.
Once again: The update file(s) seem to be lost in transit. They are not stored on the system.
The updater still shows the install button even if there is nothing to install.
rigattoni said:
If this is reduced to this single folder I can say that my G4 has no folder with this name.
The download completed and the updater asks for updating the unit.
The G4 restarts into recovery mode and nothing happens. Manual search for the downloaded files have not been successful.
I restarted my G4 and searched manually with root rights (just to be sure the files are not hidden in non root search) and I could not find any update file.
The lineage updater still shows to update the phone, even that there whether is a folder named "/data/org.lineageos.updater/app_updates"
nor a file in the "\data\org.lineageos.updater\files.
So... is this an issue with the updater, ROM or is this just not implemented complete?
I have no issues to manually install anything by console or TWRP or what ever else.
Once again: The update file(s) seem to be lost in transit. They are not stored on the system.
The updater still shows the install button even if there is nothing to install.
Click to expand...
Click to collapse
Are you sure you are looking in the right folder? Your stated path shows :
"\data\org.lineageos.updater"
Was that just a typo?
This where it is in my device:
"/data/data/org.lineageos.updater/app_updates" (note the nested "data" in "data")
Also, I think that if it shows "install" it means that it has been downloaded (and exist), otherwise it would show "download".
jhedfors said:
Are you sure you are looking in the right folder? Your stated path shows :
"\data\org.lineageos.updater"
Was that just a typo?
This where it is in my device:
"/data/data/org.lineageos.updater/app_updates" (note the nested "data" in "data")
Also, I think that if it shows "install" it means that it has been downloaded (and exist), otherwise it would show "download".
Click to expand...
Click to collapse
Shame on me... I searched with root rights and could not find the folder.... Seems I need new glasses.
But the folder is there and yes, the download is in there.
So single issue is, why the updater does not call the update automatically for flashing the update.
rigattoni said:
Shame on me... I searched with root rights and could not find the folder.... Seems I need new glasses.
But the folder is there and yes, the download is in there.
So single issue is, why the updater does not call the update automatically for flashing the update.
Click to expand...
Click to collapse
Hmmm... TWRP should be able to handle the script created by the updater. You may want to check on the G4 forum to see if others have the same issue.
jhedfors said:
Hmmm... TWRP should be able to handle the script created by the updater. You may want to check on the G4 forum to see if others have the same issue.
Click to expand...
Click to collapse
the guys in the G4 forum are mostly connected to the unofficial version. a complete manual installation is required.
But there are some rumors in the German forum, who are using the official LineAgeOS version, where the updater script is not working.
I´ll wait for the next update in a week... may be it´s just a minor issue which will be fixed soon.
is it possible to change that path?
The path *HAS* been changed.
It's now downloading OTA updates to /data/lineageos_updates
Which a pain in the ass, because TWRP already doesn't automatically handle the script as expected on my Note3, and, I'd already gotten used to having to go to /data/data/org.lineageos.updates.
Hrmph.
darrylhadfield said:
The path *HAS* been changed.
It's now downloading OTA updates to /data/lineageos_updates
Which a pain in the ass, because TWRP already doesn't automatically handle the script as expected on my Note3, and, I'd already gotten used to having to go to /data/data/org.lineageos.updates.
Hrmph.
Click to expand...
Click to collapse
Thank you!!!! :victory::victory::victory: It works!!
rarmz said:
Thank you!!!! :victory::victory::victory: It works!!
Click to expand...
Click to collapse
Happy to help!
Now, if I can just get the attention of whoever the device maintainer is, for the Note3, to figure out the TWRP scripting issue...