Related
Can someone with 4.08.605.2 check your build.prop file (located in /system/) and post the line that starts from "ro.build.fingerprint"? If you are rooted it is accessible via Root Explorer.
Thanks.
If you check the differences, it's the updated one. Don't feel like selecting text on my phone right now, its a pain.
http://review.cyanogenmod.com/#change,10280
JoeSchmoe007 said:
Can someone with 4.08.605.2 check your build.prop file (located in /system/) and post the line that starts from "ro.build.fingerprint"? If you are rooted it is accessible via Root Explorer.
Thanks.
Click to expand...
Click to collapse
Code:
ro.build.fingerprint=verizon_wwe/inc/inc:2.3.4/GRJ22/185897.2:user/release-keys
Thanks you cmlusco
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'm hoping someone here can help me with a small favor. I want to write an update package for someone that is having a CWM boot loop issue that CWM itself isn't clearing correctly on the Nitro. I've already written the same package for the Spectrum as that is the phone I have. Can someone who can currently boot into android on the Nitro and has root access please do this command and post the corresponding file in adb?
su
dd if=/dev/block/mmcblk0p25 of=/sdcard/misc.img
The file I need (misc.img) should be on the root of the SD card once this is finished.
Thanks in advance.
neph81 said:
I'm hoping someone here can help me with a small favor. I want to write an update package for someone that is having a CWM boot loop issue that CWM itself isn't clearing correctly on the Nitro. I've already written the same package for the Spectrum as that is the phone I have. Can someone who can currently boot into android on the Nitro and has root access please do this command and post the corresponding file in adb?
su
dd if=/dev/block/mmcblk0p25 of=/sdcard/misc.img
The file I need (misc.img) should be on the root of the SD card once this is finished.
Thanks in advance.
Click to expand...
Click to collapse
Doing it now
Sent from my LG-P930 using XDA
https://www.box.com/shared/5ae03c2053bb25c0a840
there you go!
Sent from my LG-P930 using XDA
is the misc.img identical across all the ROMs?
Before I saw this thread, I had already uploaded my misc partition here: http://forum.xda-developers.com/showpost.php?p=28617084&postcount=16
The imgs aren't bytewise identical for whatever reason, so try both I guess.
scott0 said:
is the misc.img identical across all the ROMs?
Click to expand...
Click to collapse
got the answer elsewhere, thx anyhoo!
neph81 said:
I'm hoping someone here can help me with a small favor. I want to write an update package for someone that is having a CWM boot loop issue that CWM itself isn't clearing correctly on the Nitro. I've already written the same package for the Spectrum as that is the phone I have. Can someone who can currently boot into android on the Nitro and has root access please do this command and post the corresponding file in adb?
su
dd if=/dev/block/mmcblk0p25 of=/sdcard/misc.img
The file I need (misc.img) should be on the root of the SD card once this is finished.
Thanks in advance.
Click to expand...
Click to collapse
what is the misc.img for?
First, I'm not a developer... but I have compiled a few roms from scratch in the past following tutorials. I would consider myself an avid android user, not a developer.
I recently got root access for my device with a locked bootloader... thanks to @K1979C20 pointing out that kingroot v4.1 finally works on our kitkat 4.4.2 device. I then removed kingroot and installed supersu using an app called "supersu me". I now have full root access, but no custom recovery due to the locked bootloader.
I was able to use @Chainfire flashfire beta app to do a backup of all my device partitions (I did not do data or cache, but can if needed).
I'm wondering if the backup can be used to create an Odin flash able package for others to use to gain root access on their device, because the kingroot process apparently works for some, but not for others...
If not Odin flashable, what other options could my files be used for to create a rooted rom that can be installed on others sgh-i467 devices.
Would it be helpful to do a full dump of all partitions? If so, any help figuring out the partition structure and process of dumping it would be appreciated.
I'm willing to do the work on this as time permits... just looking for someone with experience to point me in the right direction.
These are the files I saved in my flashfire backup
Ok now I'm not a developer at all but I'll try to help you out! Ok below is the partitions layout for our device. Now we don't need a copy of the bootloader because in the ota-update they gave us the sboot.bin and the tz.img which is the bootloader! But what we do need is the kernel (the boot.img), the recovery.img, the modem.bin, the param.bin and the system.img. But I'm not sure that even if you manage to pull these from the system that we will be able to flash them using odin cause with us having a locked bootloader if the images aren't signed by AT&T it won't allow the device to boot. But you can do it anyways and anyone willing to try can give it a shot! I would but my wife has taken over my Note 8 to use to play her games and she won't let me risk it cuz she will loose all her data! But to do the system pulls the way I know is to download Terminal Emulator for Android from the play store and make sure you have the latest Stericson Busybox installed and open the Terminal Emulator and type su the hit enter and grant it root access. Now use the following commands to pull the files but don't use the ( ) marks ok!
(busybox dd if=/dev/block/mmcblk0p8 of=/sdcard/param.bin)
(busybox dd if=/dev/block/mmcblk0p9 of=/sdcard/boot.img)
(busybox dd if=/dev/block/mmcblk0p10 of=/sdcard/recovery.img)
(busybox dd if=/dev/block/mmcblk0p13 of=/sdcard/modem.bin
(busybox dd if=/dev/block/mmcblk0p20 of=/sdcard/system.img)
If you wanna pull the cache.img, hidden.img, and tombstones.img you can but that's up to you. When you finish if you will put the into a zip file and upload them to like drive or dropbox or whatever you use and send me a link I'll try to talk my wife into letting me test it. I'll put the sboot.bin and tz.img from the ota-update with it.
mmcblk0p1: bota0
mmcblk0p2: bota1
mmcblk0p3: efs
mmcblk0p4: m9kefs1
mmcblk0p5: m9kefs2
mmcblk0p6: m9kefs3
mmcblk0p7: carrier
mmcblk0p8: param
mmcblk0p9: boot
mmcblk0p10: recovery
mmcblk0p11: ota
mmcblk0p12: cdma
mmcblk0p13: modem
mmcblk0p14: tombstones
mmcblk0p15: tdata
mmcblk0p16: hidden
mmcblk0p17: reserved1
mmcblk0p18: reserved2
mmcblk0p19: cache
mmcblk0p20: system
mmcblk0p21: userdata
@RootSuperSU I am working on this now... THANKS will post a link in a while and pm you
EDIT: I have extracted all of the files, but it's gonna be a bit before it is all uploaded. I have 100mbps download speed, but the upload speed is a whole different issue...
EDIT #2: try this link for the files you requested https://onedrive.live.com/redir?resid=7FBDBF9B2D3ACDA5!4928&authkey=!AAiZqsqu3y_s5dk&ithint=file,zip
OR try this one if that doesn't work: https://drive.google.com/file/d/0B3w-dFE5Q3FOUlp3bVhMS2lFYjA/view?usp=sharing
@RootSuperSU
Just so I learn the process... how would I extract the sboot.bin and tz.img? Even if you don't need these from me, I'd like to do it so I can learn the process... it's the old "teach a man to fish" addage. Based on what I have read elsewhere, I taking a guess and wondering if:
Would bota0 be where to extract the sboot.bin?
Would bota1 be where to extract the tz.img?
If these are the correct locations, presumably the same type of code is used to extract them as the other files I did above?
dandroid7 said:
@RootSuperSU
Just so I learn the process... how would I extract the sboot.bin and tz.img? Even if you don't need these from me, I'd like to do it so I can learn the process... it's the old "teach a man to fish" addage. Based on what I have read elsewhere, I taking a guess and wondering if:
Would bota0 be where to extract the sboot.bin?
Would bota1 be where to extract the tz.img?
If these are the correct locations, presumably the same type of code is used to extract them as the other files I did above?
Click to expand...
Click to collapse
I'm not sure about those 2 files! I don't know which files are what that is why I didn't say to pull those mainly! I wish I knew.
Ok developer gurus... i tried using romdump via terminal emulator... i'm getting the following message... I have edited permissions on the romdump file, but cant get it to dump the files... it looks like it is opening the script, but its giving me this error...
Any advice?
I'm trying to do a full romdump vs the partial stuff i have already harvested... wanting to make sure i get everything in the right format.
@dandroid7 I'm not sure if you noticed but boot.img and recovery.img are the exact same size. From what I can tell is that we can't get a real dump of either because of the locked bootloader.
@TMartin
hmmmm, I didn't notice that. but now I see what you are saying. Could be operator error on my part in how I extracted the stuff (see post #3) - or it could be as you say because of the locked bootloader. either way - I don't have the knowledge to say which it is (if either).
I'd really like to learn more about how to properly do this stuff... I have been googling and reading a lot - but not making much progress. It would be awesome to pick the brain of a developer or two who could give me some pointers. I don't mind doing the work - I just need some direction.
I guess we will see if anyone else posts more ideas... meanwhile - I'll keep reading and experimenting.
dandroid7 said:
@TMartin
hmmmm, I didn't notice that. but now I see what you are saying. Could be operator error on my part in how I extracted the stuff (see post #3) - or it could be as you say because of the locked bootloader. either way - I don't have the knowledge to say which it is (if either).
I'd really like to learn more about how to properly do this stuff... I have been googling and reading a lot - but not making much progress. It would be awesome to pick the brain of a developer or two who could give me some pointers. I don't mind doing the work - I just need some direction.
I guess we will see if anyone else posts more ideas... meanwhile - I'll keep reading and experimenting.
Click to expand...
Click to collapse
Hey I don't know what they are talking talking about we can't do rom dumps with locked bootloader because I have unpacked the modem.bin, param.bin, boot.img and recovery.img you sent me successfully with no problems using only my Note 8! I haven't been able to find away to unpack the system.img tho cause I don't have a computer but I am working on trying to find away!
Just trying to learn here... what do you use to unpack the .bin and .img files on the tablet? Not that I know what I'm doing, but I'd like to see what's in the files for the sake of learning.
Additionally... I have a decent computer... so if given a bit of direction, I could unpack the system.img file, put it in a zip file, and post a link to whatever you need for it.
Let me know if you want me to do so.
RootSuperSU said:
Hey I don't know what they are talking talking about we can't do rom dumps with locked bootloader because I have unpacked the modem.bin, param.bin, boot.img and recovery.img you sent me successfully with no problems using only my Note 8! I haven't been able to find away to unpack the system.img tho cause I don't have a computer but I am working on trying to find away!
Click to expand...
Click to collapse
I've tried multiple ways and can't get anything to mount and extract. I'd love to know how you pulled them. Do you have them uploaded anywhere?
TMartin said:
I've tried multiple ways and can't get anything to mount and extract. I'd love to know how you pulled them. Do you have them uploaded anywhere?
Click to expand...
Click to collapse
dandroid7 managed to follow my directions in post #3 on this thread and he managed to do all the pulls. He has them on his ondrive uploaded. Check and read the posts man!
dandroid7 said:
Just trying to learn here... what do you use to unpack the .bin and .img files on the tablet? Not that I know what I'm doing, but I'd like to see what's in the files for the sake of learning.
Additionally... I have a decent computer... so if given a bit of direction, I could unpack the system.img file, put it in a zip file, and post a link to whatever you need for it.
Let me know if you want me to do so.
Click to expand...
Click to collapse
I used the ZArchiver Pro app I bought on the PlayStore to unpack the modem.bin and the param.bin. It's a file manager and has features kinda like 7zip for Windows. Jus open the app and go to the .bin files long press on them and open as archive. Here is a link to the app on my Drive storage.
https://drive.google.com/file/d/0B-Zg_yh4ytvLYkNINVBpZThQQlE/view?usp=docslist_api
For the boot.img and recovery.img I used a app called Unpack Repack Img. You have to make a folder called unpack on the root of your sdcard and place your boot.img on the root of your sdcard also then use the app to unpack. For the recovery.img same app and same way but you will have to rename it to boot.img for the app to do it. But it doesnt work on repacking the images. Here is that app. https://drive.google.com/file/d/0B-Zg_yh4ytvLQ3RLa2I1bWl2OFU/view?usp=docslist_api
Now if you wanna use Android Image Kitchen for Windows/Linux/Mobile to unpack and repack the boot.img and recovery.img then just go check out this thread below for the downloads and information on how to install and use.
http://forum.xda-developers.com/showthread.php?t=2073775&page=1
Now for the system.img since you have a computer I would check out this thread for what seems to be an easy way to unpack it.
http://forum.xda-developers.com/showthread.php?t=2294909&page=1
or
You can look here at this thread for another way to unpack the system.img. Apparently this has Chainfire's Tools he uses to:
* Extract/repacking zip/.tar.md5 ROM files
* Unpacking/mounting/repacking ext4 sparse partition image files
* Unpacking/repacking boot image files
in LINUX OS
http://forum.xda-developers.com/showthread.php?t=2600364&page=1
For a better and more complete guide with step by step and pics on how to get the list of partitions and how to get the dumps using a computer with adb commands or using a Terminal Emulator app on your device go check out this thread!
http://forum.xda-developers.com/showthread.php?t=2450045&page=1
Be sure to go to the OP of each thread. That's the short term for Original Post if you didn't know. I hope this all helps yall out on how to do this stuff! Really all you had to do was Google Search this and just look for the XDA links section. Normally they are some of the 1st links given. But I'm glad to help anybody cause I know how difficult it can be trying to figure out all this stuff. I've only been into this for the past 2 or 3 years. I wish I knew alot more. I hope to be able to get a good computer and maybe compile my own custom roms and kernels and recoveries for my devices!
[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