Develop Bugs

[Q] Help. I'm stuck in the middle of a root of my evo via linux terminal/ adb

So I'm not fluent in the linux terminal. I'm basically illiterate, deaf and dumb. So here I am trying to root using toasts tutorial, How To Root The HTC EVO ~ Part-1 \0/
the forum won't let me post links yet., and apparently the software here thinks some part of the code I'm posting is a link.
Anyway I'm at this step,
- At this point it will boot into a rooted rom.
- YOU ARE NOW ROOT!!!
- rename the PC36IMG.zip on your sdcard:
- plug your phone into a usb port on your desktop and do:
Click to expand...
Click to collapse
I may be root but I had a problem and had to redo this step... my sdcard was not being recognized. After reflashing/ updating I was able to access it again.
Now this rename the zip file step... I'm thinking if I rename it the code I'm supposed to enter isn't going to work. What should I rename it to?
How should I enter this code? first off my sd card isn't called sdcard it's called an 8 digit number.
I tried this (can't post the code for some reason) without changing the name of the zip file. I'm thinking I don't have the locations right because I know the file is in there.
I need some direction to get to the next step.
Thanks

Mods please move this thread....
to wherever it will get the most or correct exposure. Sorry if I put it in the wrong place.

i have no idea what your doing...i rooted via the unREVOked method...i had to downgrade to 2.1, then actually root...can u send me a PM with what tutorial your following? and also the current info you have for your phone, like what its running (2.1 or 2.2) and stuff of that nature.... we shall see if i can help, not sure but its worth a shot

okay form what i read you have already flashed the .zip. Make sure you clear your data and cache as these will cause boot loops if not cleared. Also you can rename the .zip to anything you want, this just makes it so the bootloader does not try to install the .zip a second time.

oshizzle1991 said:
i have no idea what your doing...i rooted via the unREVOked method...i had to downgrade to 2.1, then actually root...can u send me a PM with what tutorial your following? and also the current info you have for your phone, like what its running (2.1 or 2.2) and stuff of that nature.... we shall see if i can help, not sure but its worth a shot
Click to expand...
Click to collapse
I'm running 2.1. I never upgraded. The tutorial I'm following is in thread #690762 I'll try to pm the link but I don't think they'll let me. I thought unrevoked wasn't a full root. I want to unlock nand. I'm also using Ubuntu here, not windows.
http://forum.xda-developers.com/showthread.php?t=690762

nfaust01 said:
okay form what i read you have already flashed the .zip. Also you can rename the .zip to anything you want, this just makes it so the bootloader does not try to install the .zip a second time.
Click to expand...
Click to collapse
Nice looks like I'm allowed to put up links now... Thanks!
Yes I flashed the .zip my phone called it "updating" when it was going on.
Make sure you clear your data and cache as these will cause boot loops if not cleared.
Click to expand...
Click to collapse
Do I do that from the boot menu?
Also you can rename the .zip to anything you want, this just makes it so the bootloader does not try to install the .zip a second time.
Click to expand...
Click to collapse
I just removed the .zip part. What is the point of the next step, which I couldn't get to work, if I rename the file?
Code:
adb shell mv /sdcard/PC36IMG.zip /sdcard/root-PC36IMG.zip

Well I guess I'm going to start over and wait for the latest unrevoked to come back out. Thanks to everyone that tried to help. "NO ROOT FOR YOU!"

You have a lot to learn....
First of all, don't rename the sdcard, rename pc36img.zip. Just rename it to anything you want so boat loader doesn't recognize it and try to update itself. Next, you aren't utilizing root. You do have a rooted boot loader, but you are still using a protected recovery and rom. Install a custom recovery and flash a new rom so you can be cool.

dkdude36 said:
First of all, don't rename the sdcard, rename pc36img.zip
Click to expand...
Click to collapse
Yes, I know I have a lot to learn. I didn't rename the sdcard, that wasn't possible. I figured part of the problem with getting this to work was the path. My sdcard wasn't called sdcard it was called some 8 digit number. I eventually worked around pushing the file to the sd card by installing the phone as a drive and dragging the file to the sdcard.
Just rename it to anything you want so boat loader doesn't recognize it and try to update itself.
Click to expand...
Click to collapse
After I rebooted and updated/ flashed the file, I renamed the file on the sdcard by removing the .zip. I did this via disk drive on my laptop because I wasn't getting anywhere with the command line.
Again this part didn't make any sense to me, not that most of it does, but what was the point of the next command in the directions if I renamed the file?
Next, you aren't utilizing root. You do have a rooted boot loader, but you are still using a protected recovery and rom. Install a custom recovery and flash a new rom so you can be cool.
Click to expand...
Click to collapse
Right "I have a lot to learn" I thought following the directions in toasts tutorial step by step would have gotten me to that point. I didn't realize I was just supposed to skip stuff when I run into problems. That kinda seems like what your telling me to do. I thought all of the commands were important.

I was hoping you had some follow up insight dkdude.

if you still on 2.1, try this method (just make sure the files aren't corrupted)
http://forum.xda-developers.com/showthread.php?t=741294

[REF][GUIDE]CWM md5 mismatch problem solved

So, many of you probably faced the issue, when you tried to restore your CWM backup, that the recovery says MD5 mistmach, and will do nothing. The problem is now solved, and was solved, so I'm not the one, who made thing possible, I'm just porting this to the V.
So, the problem (in my iterations at least) are based on the /cache/ cannot be mounted error, which is common in the V. For why is that, I simply don't have a clue, but it is present. Because of this, the backup won't be full, and thus, the md5 image won't be made for the recovery, so cannot be recovered as is.
But happily you can make an md5 image from the backup yourself, and thus recover your backup.
WARNING!​
I'm no dev, just someone, that knows linux.
If you follow this path, you do it on your own. I'm not responsible for bricked devices, lost data or whatsoever, including the future the past and the present.​
Click to expand...
Click to collapse
There are three ways for you, to make an md5 sum of the img files, the good and the bad one and also the quoted one:
One (the good)
For this, you will need adb, root, and a working android. Yo don't have it? Here you go.
Go to the directory, were you have adb (or have extracted adb.exe, suggested c:\htc\), then plug in your phone (just for charge, no data connection), open terminal (syntax: cmd) then type in:
adb shell
this will get you to the phone's terminal
if you have # at the end of the line, you are good to go, if not, then type su
The syntaxes needed:
cd /sdcard/clockworkmod/backup/{recovery_timestamped_directory} <- this is from your backup, so you need to fill in appropirate data
md5sum *img > nandroid.md5
Click to expand...
Click to collapse
This will make an md5 image with the name that cwm acknowledges.
Two (the bad one)
So, you'we fired your ROM, cannot even boot, but cwm comes in. Than this is for you. There are programs (e.g. total commander) which can make md5 images. So if you have your backup folder, just go into it (sd card reader is preferred). You will see something like this in it:
.android_secure.vfat.tar
boot.img
data.ext4.tar
{nandroid.md5}
recovery.img
system.ext4.tar
Click to expand...
Click to collapse
sidenote:
If you have the nandroid.md5 and you cannot recover, don't try to recover from it!!!
The image itself is corrup, you have no luck, try RUU. (you can recover if you delete the md5 and create a new, but it is not really recommended)
1.
So, there are 2 .img files, highlight them in totalcommander. go to file->create checksum files
2.
tick in md5, then ok
3.
No, you're not done
open the md5 file in text editor, and remove the * 's from before the file names.
4.
Rename the file to nandroid.md5
5.
Now you're done, go to cwm, then recover.
Three (the quoted one)
Also on the 2nd page you will find an alternative solution for the problem which can help you if you have got busybox installed on your device.
The solution resembles the One type of fix, so with quotes here's the one (thanx for Meeshka for it).
Meeshka said:
For those who keep getting "md5sum not found" both in adb and in android terminql on device:
try instead
# busybox md5sum *img > nandroid.md5
worked for me
Click to expand...
Click to collapse
If I helped, don't hesitate to push the Thanks button.

Thanks... a very useful guide. Bookmarked

WORKED!!! Tho I'm from a different device the first (adb) method saved my AOKP backup!!! Daysaver I'd say!!

I keep getting "md5sum: not found"

Put this in the general android section as it works across most devices. ..
Sent from my One V

Nevell said:
I keep getting "md5sum: not found"
Click to expand...
Click to collapse
if you send me the 2 img files i can create an appropirate md5 image of them, but send the one you did, so I can guess what the problem is.
send them to the email of my usr here, or in pm. and mainly, the md5 image has the name "nandroid.md5" like small caption all the way, even the md5? If it is there where it must, it must work, ad absurd it will be "wrong checksum error", but that is another version.
General android section has this, I have learned this from there, but it had only 1st option, and was "discovered" when cwm had generated wrong md5s, the V, in the V the problem is a tad bit different, but the solution is the same.

I fixed it in adb
Sent from my SPH-L710 using xda premium

Nevell said:
I fixed it in adb
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Can you explain what did you do to fix md5sum: not found error??
please i need it!

thatsgamer said:
Can you explain what did you do to fix md5sum: not found error??
please i need it!
Click to expand...
Click to collapse
Just created an md5sum manualy from the img files with the name of nandroid.md5, because on the V the recovery doesn't creates them because of cache mount problem.
The recovery process will end in an error message, because cache cannot be recovered, but the main thing will be recovered this way.

i have one x and i can't put sdcard in to card reader because one x dose not have sd card... and i cant fix it whit first solution because i cant acces my phone

haky1988 said:
i have one x and i can't put sdcard in to card reader because one x dose not have sd card... and i cant fix it whit first solution because i cant acces my phone
Click to expand...
Click to collapse
See : http://forum.xda-developers.com/showpost.php?p=32248108&postcount=7

unfortunately none of the methods described in the first post have worked for me, at the first one i got an "unable to write, source is read-only" error, and the second one failed from the first try
after almost giving up and beginning to deal with the idea of loosing my backups, i found this topic and in 10 secs it got the job done, now i'm back on my latest cwm backup

CWM showing different versions
-Delete-

maranello69 said:
unfortunately none of the methods described in the first post have worked for me, at the first one i got an "unable to write, source is read-only" error, and the second one failed from the first try
after almost giving up and beginning to deal with the idea of loosing my backups, i found this topic and in 10 secs it got the job done, now i'm back on my latest cwm backup
Click to expand...
Click to collapse
You do know that the first method is exactly like the one you linked right?
Aside that, I'm happy that the community could help you out

Loir can u help me. I can't locate the boot.img inside the downloads for cyanogen mod u provided. Forgive me but can you post a directory to this kernel file? Tks
Sent from my HTC Desire X using xda app-developers app

Thank you so much. You saved my phone.

For those who keep getting "md5sum not found" both in adb and in android terminql on device:
try instead
# busybox md5sum *img > nandroid.md5
worked for me

no * 's
Ken-Shi_Kun said:
So, many of you probably faced the issue, when you tried to restore your CWM backup, that the recovery says MD5 mistmach, and will do nothing. The problem is now solved, and was solved, so I'm not the one, who made thing possible, I'm just porting this to the V.
So, the problem (in my iterations at least) are based on the /cache/ cannot be mounted error, which is common in the V. For why is that, I simply don't have a clue, but it is present. Because of this, the backup won't be full, and thus, the md5 image won't be made for the recovery, so cannot be recovered as is.
But happily you can make an md5 image from the backup yourself, and thus recover your backup.
​
There are two ways for you, to make an md5 sum of the img files, the good and the bad one:
One (the good)
For this, you will need adb, root, and a working android. Yo don't have it? Here you go.
Go to the directory, were you have adb (or have extracted adb.exe, suggested c:\htc\), then plug in your phone (just for charge, no data connection), open terminal (syntax: cmd) then type in:
adb shell
this will get you to the phone's terminal
if you have # at the end of the line, you are good to go, if not, then type su
The syntaxes needed:
This will make an md5 image with the name that cwm acknowledges.
Two (the bad one)
So, you'we fired your ROM, cannot even boot, but cwm comes in. Than this is for you. There are programs (e.g. total commander) which can make md5 images. So if you have your backup folder, just go into it (sd card reader is preferred). You will see something like this in it:
sidenote:
If you have the nandroid.md5 and you cannot recover, don't try to recover from it!!!
The image itself is corrup, you have no luck, try RUU. (you can recover if you delete the md5 and create a new, but it is not really recommended)
1.
So, there are 2 .img files, highlight them in totalcommander. go to file->create checksum files
2.
tick in md5, then ok
3.
No, you're not done
open the md5 file in text editor, and remove the * 's from before the file names.
4.
Rename the file to nandroid.md5
5.
Now you're done, go to cwm, then recover.
If I helped, don't hesitate to push the Thanks button.
Click to expand...
Click to collapse
in 3. it says to remove the * *'s, but i don't see any, so i was wondering should i leave that be or if im doing something wrong.

Beastben13 said:
in 3. it says to remove the * *'s, but i don't see any, so i was wondering should i leave that be or if im doing something wrong.
Click to expand...
Click to collapse
I have done the thing with a legacy tcmd, so there is a probability, that they have modified the md5sum algorithm, so if you don't se the stars don't panic. (also it should do the trick even with stars in the file, but wanted to be sure at the time I wrote the post)

plz provide touch recovery for karbon a9+ plz and ther is bugs in cwm recovery 5.0.2.8 plz

Need Help with development issue for sgh-i467 (ATT galaxy note 8)

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!

Rooting LG H735 G4 Beat

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.

2016 version (new fingerprint scanner, combined sim/sd)

Hey guys,
It seems more and more people are receiving the new version of the P8000:
- Stock Android 6
- New fingerprint scanner that is moved slightly higher and is able to unlock phone from screen-off (I confirm this is working)
- Sim 2 is combined with the micro-sd (I haven't tried whether you can have them both in at the same time)
- Somethings new about the display, since people are reporting errors with it after flashing older roms.
Warning: do NOT flash other roms. We have no way to unbrick the soft bricks yet!
---
Other topics that refer to this version:
http://forum.xda-developers.com/elephone-p8000/general/rom-p8000-t3431571
http://forum.xda-developers.com/elephone-p8000/help/stock-rom-p8000b-t3434477
http://forum.xda-developers.com/elephone-p8000/general/p8000-version-announced-t3346848
---
For development:
- The phone does not come pre-rooted. We have no way to flash custom recovery yet. Any tips for getting root? I've tried such tools as Kingo and vRoot, they don't work.
- We need the blocks file (scatter file) for SP Flash Tools. MTKDroidTools reports "unknown rom structure". Any help? Would love to start working on this.
Looking forward to hearing from others who have this version/who can help me with these questions.
Thanks!
Emile

Nice! Can you provide a dump from /system and /boot maybe?

BlueFlame4 said:
Nice! Can you provide a dump from /system and /boot maybe?
Click to expand...
Click to collapse
I would, if I knew how to. Any pointers?

Emileh said:
I would, if I knew how to. Any pointers?
Click to expand...
Click to collapse
Sure thing. On a rooted device, go into adb shell.
Then use "mount" command to check which partitions are mounted. One should be "/dev/block/platform/mtk-msdc.0/by-name/system" or similar. Use "dd if=/dev/block/platform/mtk-msdc.0/by-name/system of=/storage/emulated/0/system.img bs=1M" to dump the system to the internal sdcard to the file "system.img". If adb complains that bs=1M is an invalid option, try again without that one. A system dump can take some time where you will not get any feedback, so be patient there
Do the same for boot. So "/dev/block/platform/mtk-msdc.0/by-name/boot" should be the way to go for the path. I cannot tell the definite pathes on Android 6.0 but I am rather sure they are more or less like this.
If you run into troubles, just ask

BlueFlame4 said:
Sure thing. On a rooted device, go into adb shell.
Then use "mount" command to check which partitions are mounted. One should be "/dev/block/platform/mtk-msdc.0/by-name/system" or similar. Use "dd if=/dev/block/platform/mtk-msdc.0/by-name/system of=/storage/emulated/0/system.img bs=1M" to dump the system to the internal sdcard to the file "system.img". If adb complains that bs=1M is an invalid option, try again without that one. A system dump can take some time where you will not get any feedback, so be patient there
Do the same for boot. So "/dev/block/platform/mtk-msdc.0/by-name/boot" should be the way to go for the path. I cannot tell the definite pathes on Android 6.0 but I am rather sure they are more or less like this.
If you run into troubles, just ask
Click to expand...
Click to collapse
Thank you for your great instructions! The problem is that we've yet to achieve root on this device. We don't have a custom recovery for this version of the P8000 yet and other 'standard' methods of rooting don't work for me.
(I'm pretty solid in shell, so I'll do this afterwards, but I guess root is actually the first step).
// Edit to say: it does not come pre-rooted

Since the elephone support on facebook didn't realize there are two different versions of the P8000 available, I still need a ROM to unbrick my phone.

flo1k said:
Since the elephone support on facebook didn't realize there are two different versions of the P8000 available, I still need a ROM to unbrick my phone.
Click to expand...
Click to collapse
Ok, we know that, but doesn't really help us
Can you write them an e-mail?

I will do
Edit: OK, see if there will be an answer.

Thank you flo1k!

I have e-mailed as well, and would like to post on the Elephone forum, but don't seem to have access (because of minimum post count, I guess)
Anyone willing to ask for a ROM for the new P8000 on the forum there?

ROM Dump
@BlueFlame4
I can provide ROM dump in two versions:
1) a dump from adress 0000 0000 to 9d80 0000 (apr. 2.5 GB in one file)
2) a readback generated with the scatter.txt of the 'old' 5.1 stock ROM (apr. 2.8 GB seperated in 23 files)

FrauHofrat said:
@BlueFlame4
I can provide ROM dump in two versions:
1) a dump from adress 0000 0000 to 9d80 0000 (apr. 2.5 GB in one file)
2) a readback generated with the scatter.txt of the 'old' 5.1 stock ROM (apr. 2.8 GB seperated in 23 files)
Click to expand...
Click to collapse
The second choice looks promising

Maybe a stupid question
where shall I upload the files - any preferred webspace?
I'm uploading the files - because they contain my NVRAM I send the link as PM as soon as the upload is finished

FrauHofrat said:
Maybe a stupid question
where shall I upload the files - any preferred webspace?
I'm uploading the files - because they contain my NVRAM I send the link as PM as soon as the upload is finished
Click to expand...
Click to collapse
Are you sure we're talking about the same version of the P8000? Cause as far as I know there isn't 5.1 available for this version... Right?
Just checking thank you for your help in any case!! Really looking forward to it.
// edit: ah, you just used the old scatter file. But does that one work for this version?

Emileh said:
Are you sure we're talking about the same version of the P8000? Cause as far as I know there isn't 5.1 available for this version... Right?
Click to expand...
Click to collapse
No, there is only one Firmware available - the mysterious P8000_6.0_20160516.
Btw, this Phone contains a new mainboard model "K06TS-L-V2.0.3" - the 'old' mainboard is moder "K05T...."
// edit: ah, you just used the old scatter file. But does that one work for this version?
Click to expand...
Click to collapse
No, it doesn't work resp. the phone boots with this firmware, but the LCD-driver is the wrong one - the display only shows coloured lines and blurry spots. And there are probabely some more bugs ....

FrauHofrat said:
No, there is only one Firmware available - the mysterious P8000_6.0_20160516.
Btw, this Phone contains a new mainboard model "K06TS-L-V2.0.3" - the 'old' mainboard is moder "K05T...."
No, it doesn't work resp. the phone boots with this firmware, but the LCD-driver is the wrong one - the display only shows coloured lines and blurry spots. And there are probabely some more bugs ....
Click to expand...
Click to collapse
But if the phone boots with the firmware, doesnt that mean that the scatter file of the regular P8000 works? Since it flashes the firmware correctly.

The problem is that I was not able to flash the 'readback files' to the faulty phone.
When selecting 'Only Download' at SP-Flashtool I got the error "PMT... must be download"
When selecting 'Firmware Upgrade" I got some BROM error code
In both cases I used the same scatter,txt which I used to 'readback' the firmware from the working phone
Actually I have to correct my statement in post #15:
I flashed the faulty phone with the last 5.1 stock ROM (160711) - with this stock ROM the phone boots up but LCD (and probably more things) is not working.

I have actually gotten alot further
You have the use the scatter.txt from Android 6.0, which works perfectly fine. I have been able to extract boot.img, system.img and recovery.img that way (using Readback in SP Flash Tools)
Which ones do you need?
They probably flash fine (only thing I've flashed so far are custom recoveries, and although my ported PhilZ starts, I havent gotten it to mount anything.)
A little warning: don't use anything that has anything to do with Android 5.1. Those scatter files don't work

These are great news!
"Which ones do you need?"
Probably all of them

Ok this contains the scatter file, preloader, system.img, boot.img and stock recovery.img
https://ehaffmans.stackstorage.com/index.php/s/uKGKCir0BociydU
You need SP Flash Tools v5, select the scatter file first, then deselect everything, and only select these 4 and manually select the correct files.
Btw, the name of the preloader file is wrong, don't worry. It came from this phone
I am of course not responsible for anything!
Can you guys please confirm this doesn't contain anything personal? Like personal files or IMEI or something. Thanks!