Related
I figured since getting a replacement A500 and updating to Acer_A500_1.139.04_COM_GEN1 I would update this post with the images.
System.img - http://www.fileserve.com/file/gvemmYd
Flexrom.img - http://www.fileserve.com/file/Suq5yBG
Boot.img - http://www.fileserve.com/file/sSjqpME
Hope this helps anyone.
Kernel Information: Linux localhost 2.6.36.3 #1 SMP PREEMPT Wed May 11 22:11:55 CST 2011 armv7l GNU/Linux
103 views and no-one is able to do it? I am sure there are quite a few Aussies on this forum. :-(
i would if i knew how
splinter6 said:
i would if i knew how
Click to expand...
Click to collapse
Here is your "knew how"... jejeje
You have to ROOT your A500 first... then use terminal emulator and type SU (this will give it Super User Access) then use the following commands:
dd if=/dev/block/mmcblk0p3 of=/sdcard/system.img
dd if=/dev/block/mmcblk0p6 of=/sdcard/flexrom.img
This will give you the actual system image (first command)
Second command gives you the partition where the update information is located.
Let me know if you need help rooting, its really easy, just remember to have your tablet in PORTRAIT not landscape or Gingerbreak will FORCE CLOSE!!!
Hope this helps... jejeje
I got a replacement A500 from JB HiFi. I will update to Acer_A500_1.139.04_COM_GEN1 then create a system.img.
This would be much appreciated! I'm in Australia, and having some issues too. Thanks again.
koprofile said:
This would be much appreciated! I'm in Australia, and having some issues too. Thanks again.
Click to expand...
Click to collapse
I'm at work today. Will hopefully get the system.img uploaded this evening, should take ~2 hours being 600MB and all. :-(
I'm not sure if the flexrom.img is needed though.
that would be appreciated as i have an issue of not being able to update after rooting and NO BACKUP
eliousneo said:
that would be appreciated as i have an issue of not being able to update after rooting and NO BACKUP
Click to expand...
Click to collapse
Here is the untouched Acer_A500_1.139.04_COM_GEN1 system.img.
http://www.fileserve.com/file/gvemmYd
thank you really appreciate it...
question 2 im a noob to all this so could you please let me know how ot install is
i know that it may sound like a dumb question but i have not got a clue.
I only rooted my a500 to be able to install apps to sd and that was a dissapointing move otherwise i think i may keep it stock from now on
thanking you in advance
eliousneo said:
thank you really appreciate it...
question 2 im a noob to all this so could you please let me know how ot install is
i know that it may sound like a dumb question but i have not got a clue.
Click to expand...
Click to collapse
You should be able to just copy the image onto your A500 and run the following as root: dd if=/dev/block/system-1.139.04.img of=/sdcard/mmcblk0p3
Be careful though, I honestly haven't tested the image but it should be fine.
Sent from my A500 using Tapatalk
so that means use command line and copy image onto SD card?
Sounds simple enough just gotta wait for 8 hours for download
Than again juzman very helpfull
Juzman said:
You should be able to just copy the image onto your A500 and run the following as root: dd if=/dev/block/system-1.139.04.img of=/sdcard/mmcblk0p3
Be careful though, I honestly haven't tested the image but it should be fine.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
We ALL should start using the MD5 checksum to rule out corrupted file size produced by online downloading
UnicornKaz said:
We ALL should start using the MD5 checksum to rule out corrupted file size produced by online downloading
Click to expand...
Click to collapse
I used the fsum utility on Windows and believe I created an MD5 checksum: 3A0AF183D5E582CBEA1D1F6BC7A61EA6
Will we need the flexrom as well when flashing this system image?
Also, this thread contains some original kernel modules: http://forum.xda-developers.com/showpost.php?p=13974214&postcount=62
Will the modules linked there be compatible with this current AU system image in the event of gps/wifi issues?
Thanks again!
Juzman said:
I used the fsum utility on Windows and believe I created an MD5 checksum: 3A0AF183D5E582CBEA1D1F6BC7A61EA6
Click to expand...
Click to collapse
Is that definitely the correct md5 checksum? I've downloaded the file twice and both times I get an md5 of 850d68aac56169b211a4913de7e4e8e9
Can anyone else confirm?
mapaz04 said:
Here is your "knew how"... jejeje
You have to ROOT your A500 first... then use terminal emulator and type SU (this will give it Super User Access) then use the following commands:
dd if=/dev/block/mmcblk0p3 of=/sdcard/system.img
dd if=/dev/block/mmcblk0p6 of=/sdcard/flexrom.img
This will give you the actual system image (first command)
Second command gives you the partition where the update information is located.
Let me know if you need help rooting, its really easy, just remember to have your tablet in PORTRAIT not landscape or Gingerbreak will FORCE CLOSE!!!
Hope this helps... jejeje
Click to expand...
Click to collapse
Can you say what terminal emulator to use or which is the best one to use?
urdaddi said:
Can you say what terminal emulator to use or which is the best one to use?
Click to expand...
Click to collapse
I used Better Terminal Emulator (with the extensions installed). Make sure after installing the extensions (after the prompt) to go into options, select root by default, then type exit (or CTRL-D) to close the terminal so it reinitializes with all the extensions (the icon on the taskbar must be gone). Afterwards do your stuff. After flashing the system.img the tablet might reboot (show the android boot logo) and cycle. Just power down holding the button long enough, and power back on, then flash the other img.
Hi Me again
dd if=/sdcard/system.img of=/dev/block/mmcblk0p3
I did the above thingy and it just extracted mmcblk0p3 into sdcard
How do i install it ??
i cant just run it so i presume there is some kind of command or something in terminal?
Is it possible to get the flexrom too?
Thanks
Okay, I am attempting to #unlockthedroid, but first I will need dumps from "/dev/block". What I'm trying to do is pull off @CrashXXL methods of rooting with Write Protect=1 but allowing the potential of unlocking bootloader with Sunshine. And I don't want it to be done randomly, so this is what we'll need to do in order to get that dump:
Requirements:
Rooted
Bootloader Unlocked
Firmware to be at 4-21. It's easier for me. Or if you have anything below, it'll probably work too.
Willing to spend time; this'll take a VERY long time. So you'll need to leave your phone overnight or whatever it takes for it to finish copying.
Instructions:
Turn on ADB in settings. (If done already, next step)
Get ADB and Fastboot on your computer. (If done already, next step)
Go to ADB directory
adb shell
Click to expand...
Click to collapse
dd if=/dev/block/mmcblk0p38 of=/(any directory)/(name your file anything - just remember the location combination)
Click to expand...
Click to collapse
When done, exit ADB
adb pull /(directory)/(file name)
Click to expand...
Click to collapse
Submit the file from the ADB folder to your own Google Drive, Mega, or Dropbox. Wherever you wish.
Files we currently need:
Droid Mini mmcblk0p5, 0p13, 0p33
Droid Ultra mmcblk0p5, 0p13, 0p33
Droid Maxx mmcblk0p5, 0p13, 0p33
There is also a certain block I don't know the mmc block number to, so when someone knows where partitions.mbn is then we'll be one step closer to getting my phone flashed and tested.
Thanks in advanced!
P.S.: Staff, please move this somewhere correct if where it is right now it's not.
mr_verystock said:
Okay, I am attempting to #unlockthedroid, but first I will need dumps from "/dev/block". What I'm trying to do is pull off @CrashXXL methods of rooting with Write Protect=1 but allowing the potential of unlocking bootloader with Sunshine. And I don't want it to be done randomly, so this is what we'll need to do in order to get that dump:
Requirements:
Rooted
Bootloader Unlocked
Firmware to be at 4-21. It's easier for me. Or if you have anything below, it'll probably work too.
Willing to spend time; this'll take a VERY long time. So you'll need to leave your phone overnight or whatever it takes for it to finish copying.
Instructions:
Turn on ADB in settings. (If done already, next step)
Get ADB and Fastboot on your computer. (If done already, next step)
Go to ADB directory
When done, exit ADB
Submit the file from the ADB folder to your own Google Drive, Mega, or Dropbox. Wherever you wish.
Files we currently need:
Droid Mini mmcblk0p5, 0p13, 0p33
Droid Ultra mmcblk0p5, 0p13, 0p33
Droid Maxx mmcblk0p5, 0p13, 0p33
There is also a certain block I don't know the mmc block number to, so when someone knows where partitions.mbn is then we'll be one step closer to getting my phone flashed and tested.
Thanks in advanced!
P.S.: Staff, please move this somewhere correct if where it is right now it's not.
Click to expand...
Click to collapse
various dumps https://yadi.sk/d/UnLW2G54f5Gbx
Thanks for the SU6-7 and 5-24 dumps! But just a question: can you dump for earlier versions? I can probably get it to run Sunshine and onto the bootloader unlock. Thanks though!
mr_verystock said:
Thanks for the SU6-7 and 5-24 dumps! But just a question: can you dump for earlier versions? I can probably get it to run Sunshine and onto the bootloader unlock. Thanks though!
Click to expand...
Click to collapse
I do not think that this would work, yes You can flash the 4-21 (all bootloader partitions + kernel + system) in the QLOAD mode, as You have access to the whole flash memory.
But the trusted boot chain will not let you boot earlier bootloader and system when a newer one was already there. Phone needs to be bootloader unlocked, to boot into any version.
It's worth trying. And plus, you never know what you can find if you try...
question is it possible to get a system dump from the following version -4.2.2-SU1-15-3 trying to unbrick my device and i need certain files from that version thanks been trying to do this for a while and no one seems to wanna help out
mr_verystock said:
It's worth trying. And plus, you never know what you can find if you try...
Click to expand...
Click to collapse
I think You can get all you need from the original FXZ file.
You can get all the bootloader partitions from the motoboot.img, see my post here.
Additionally You can extract the system partition with the simg2img tool from here, but this would be the original, not the rootet image,so You would need to insert the su binary by yourself.
pizmak said:
I think You can get all you need from the original FXZ file.
You can get all the bootloader partitions from the motoboot.img, see my post here.
Additionally You can extract the system partition with the simg2img tool from here, but this would be the original, not the rootet image,so You would need to insert the su binary by yourself.
Click to expand...
Click to collapse
If this is the method it would've been done already... But no, motoboot.img cannot be extracted for all it's worth. It has aboot, gpt, and many other parts we need to create a complete set of unbricking and/or bootloader-necessary files.
happysteve11c said:
question is it possible to get a system dump from the following version -4.2.2-SU1-15-3 trying to unbrick my device and i need certain files from that version thanks been trying to do this for a while and no one seems to wanna help out
Click to expand...
Click to collapse
Sigh... I wish, my friend. I know what you want, but nobody's willing to provide it because of. @CrashXXL is nice enough to provide the unbricking files but nobody is willing to dump for SU1.
mr_verystock said:
If this is the method it would've been done already... But no, motoboot.img cannot be extracted for all it's worth. It has aboot, gpt, and many other parts we need to create a complete set of unbricking and/or bootloader-necessary files.
Click to expand...
Click to collapse
it actually is as easy as this, the motoboot.img file is just the bootloader partition images put into one file plus a 1024 bytes header. I have extracted these image and compared them with the dumps from my own phone and they are identical, so this motoboot is not compressed or encrypted.
If You still do not believe me just check for yourself, dump for example the aboot partition from your phone and compare it with the motoboot image from the FXZ file for your firmware version, I think you will find the aboot image inside the motoboot image at some 512bytes aligned offset (you can get the offset from the header, see the description in my post linked above)
Edit: I have added my code I wrote to extract the motoboot image to this thread
happysteve11c said:
question is it possible to get a system dump from the following version -4.2.2-SU1-15-3 trying to unbrick my device and i need certain files from that version thanks been trying to do this for a while and no one seems to wanna help out
Click to expand...
Click to collapse
Not sure if you or anyone can do anything with it but I have a twrp backup of the boot and system from su1-15. Let me know if anyone wants it.
Sent from my XT1080 using XDA Free mobile app
@mr_verystock are you still working on this?
Yes, I'm working on it. But I'm dealing with school, along with patching up a broken computer which I am planning to use for my daily driver. So currently I'm installing Linux, to do a mbn split.
Oh, and I kinda messed up my Droid Maxx while doing this... Don't worry, it's a backup, I have a Droid Mini as main.
WOHOO!!!!!!!!!
Is it rooted?
What version of Android are you on?
Ya still working on this?
Hey man. I have a (probably useless) Droid Mini "dev" edition (on su6-7). Today, I will be receiving a droid maxx on 4.4 (idk if its 19.5.3 or 19.6.3 yet) and i will be unlocking it with sunshine. if you still need files/help, i can help. (when you do start work on this again). my sincere hope, aside from a bootloader unlock for the folks on 4.4.4) is that somehow this will help the Turbo folks. (mofo root is good, but bl unlock is better). let me know if and when i can help man.
Hey, yeah, please let me know if you need anything once you get started again. I have a droid ultra that I just bought off groupon for $80.
YYUSSSSSSSSSS!!!!!!!!!!!!!!!!!!!!! Thank you VERY MUCH!!!!
Great thing I have a Droid Mini. Can you dump cid.mbn for 4.4? That's the file I want to mess with currently after you unlocked.
me or him, broheim?
edit: duh, me. ill have it pulled and uploaded tomorrow around noon
Is it uploaded to a hosting site or not?
i never saw any reply dude. i can upload what i have...but my mini is on 4.4.4. i have a maxx on 4.4, but no dice on that build. i thought for a moment i was crazy. if it helps you to have either or both, i will pull them right now and throw up a link to my drive.
Hm... I can't do anything with the 4.4.4 one, I'll take the Maxx on 4.4 cid.mbn. Sorry if there were any confusion!!!
I just had an idea. What if someone roots a system.img by extracting it from a kdz and then mounting it in linux copying the root files setting the permissions and then flashing that with download mode? A simple
Code:
dd if=/data/local/tmp/system.img of=/dev/block/platform/??????/by-name/system
should do the trick to flash the system.img file replacing the ?????? with the correct directory.
Just a thought.
Wouldn't you have to have read/write access in order to push the system.img?
Impossible,without root.
Sent from my LG-D802 using Tapatalk
l33tlinuxh4x0r said:
I just had an idea. What if someone roots a system.img by extracting it from a kdz and then mounting it in linux copying the root files setting the permissions and then flashing that with download mode? A simple
Code:
dd if=/data/tmp/system.img of=/dev/block/platform/??????/by-name/system
should do the trick to flash the system.img file replacing the ?????? with the correct directory.
-
Click to expand...
Click to collapse
Dennisg34 said:
There's already a thread to discuss root. Please search before posting, thanks.
Sent from my G4 using your mom
Click to expand...
Click to collapse
I think both of the previous threads discussing root have been closed. I haven't seen another - did I miss it?
Already tried something similar. Requires root unless you're one of the lucky few who have such advanced knowledge of hacking bootloaders/exploits....which I unfortunately am not. LOL
rfarrah said:
I think both of the previous threads discussing root have been closed. I haven't seen another - did I miss it?
Click to expand...
Click to collapse
Apologies, I forgot they were.
Hello,
It is possible to rooter lg g4 with : V10B LGH815
thank you :fingers-crossed:
dydyfr said:
Hello,
It is possible to rooter lg g4 with : V10B LGH815
thank you :fingers-crossed:
Click to expand...
Click to collapse
Yes, look in the developer section.
It is possible to dd to partitions using download mode. The only real problem is that the root method would be huge having to include a system.img.
l33tlinuxh4x0r said:
It is possible to dd to partitions using download mode. The only real problem is that the root method would be huge having to include a system.img.
Click to expand...
Click to collapse
Additionally, you'd need a separate one for every carrier/variant.
I guess if it worked though, who cares how many we need or how big they are. Except with dd, one typo and you've got yourself a brick.
tabp0le said:
Additionally, you'd need a separate one for every carrier/variant.
I guess if it worked though, who cares how many we need or how big they are. Except with dd, one typo and you've got yourself a brick.
Click to expand...
Click to collapse
very true.
tabp0le said:
Additionally, you'd need a separate one for every carrier/variant.
I guess if it worked though, who cares how many we need or how big they are. Except with dd, one typo and you've got yourself a brick.
Click to expand...
Click to collapse
l33tlinuxh4x0r said:
very true.
Click to expand...
Click to collapse
Though...wouldn't it still be able to get into download mode? I could be wrong, but that's not on the system partition from my understanding.
I'm on linux and am familiar with dd (I'm a distro-hopper and have no optical drive, so everything gets dd'ed onto usb drive).
Wouldn't we have to specify a block size on that? I know at least on linux distro, if block size isn't specified, I end up in non-boot.
geoff5093 said:
Yes, look in the developer section.
Click to expand...
Click to collapse
Good
Thank's
Sent from my Iconia A3-A20 FHD using XDA Free mobile app
Th3Bill said:
Though...wouldn't it still be able to get into download mode? I could be wrong, but that's not on the system partition from my understanding.
I'm on linux and am familiar with dd (I'm a distro-hopper and have no optical drive, so everything gets dd'ed onto usb drive).
Wouldn't we have to specify a block size on that? I know at least on linux distro, if block size isn't specified, I end up in non-boot.
Click to expand...
Click to collapse
Actually you are correct. The laf partition is the download mode. Flashing recovery is where we have to worry about losing download mode. (I never understood why, but at least with the G2 download mode broke when flashing custom recovery without a certain patch)
The previous root threads were locked because peopel wouldn't stay on topic after multiple warnings...
Eagle1337 said:
The previous root threads were locked because peopel wouldn't stay on topic after multiple warnings...
Click to expand...
Click to collapse
Correction, they were closed per OP request
This one is now clean, lets try to stay on topic,
If anyone feels the urge to regurgitate further horse crap... we'll see what happens
l33tlinuxh4x0r said:
It is possible to dd to partitions using download mode. The only real problem is that the root method would be huge having to include a system.img.
Click to expand...
Click to collapse
How can you confirm being able to dd to partitions using download mode? In download mode isn't the dd running from /system/bin that is mounted as ro. How could you replace /system while it is mounted and running dd from it?
gbgadgets said:
How can you confirm being able to dd to partitions using download mode? In download mode isn't the dd running from /system/bin that is mounted as ro. How could you replace /system while it is mounted and running dd from it?
Click to expand...
Click to collapse
linux loads commands that you are in the process of running into ram. You can even delete a file that you are running and still be able to use it until you close it. Once you close it is when the problem would occur but by that time you would already have the new file in place. Also do NOT run a
Code:
dd if=/dev/zero of=/dev/block/platform/??????/by-name/system
just skip that step otherwise you would lose the ability to dd.
Go directly for a
Code:
dd if=/data/local/tmp/system.img of=/dev/block/platform/??????/by-name/system
also to get a system.img instead of extracting from a kdz you could run
Code:
dd if=/dev/block/platform/??????/by-name/system of=/data/local/tmp/system.img
docfreed said:
Wouldn't you have to have read/write access in order to push the system.img?
Click to expand...
Click to collapse
you can push to /data/local/tmp using adb without root.
Hi everyone. As I found out there's root for the G4 but doing this isn't easy especially if your variant is hard to find or has less users. This may result in you waiting for longer than you should. This thread is for those who can take things into their own hands and do it themselves. The tools are available everywhere but I'll give you the best order and steps. I'm using the China LG G4 H818 Dual SIM variant but this method is UNIVERSAL FOR ALL LG G4s.
The process will involve extracting a system image, injecting root and reflashing this image. Most of the steps are effortless and need just copy and paste with keen eyes. Do it slowly. You need an Ubuntu installation for step 2 of this 3-step tutorial. I used universal USB installer and put in on my 8GB USB. Anywhere will do so far as it boots&works. Beware this thread is not dumb-proof but this will not wipe your data or void your warranty if done successfully.
Step 1 -> Getting the proper system image.
Check here and skip to step 3 if you have your rootedsystem.img
>Don't worry because this doesn't require searching. It is from your device. Every device has a system partition and this method will pull it out as an image without root required.
1--Make sure all drivers are installed properly. I'll not be talking about this. We're on XDA not kindergarten.
2--Download the LG_root file or send command file from here and extract it. US Carrier specific check here
3--Put your device in download mode and connect it to your PC.
4--Open(double-click duh) port.bat and make sure to write down the number after com. There maybe different com numbers but choose the com on the DIAG1 line and write down that number. This is important.
5--Hold shift and right-click in any empty space in the extracted folder. Choose open command windows here.
6-- In that copy and paste this
Code:
[FONT=Lucida Console][COLOR=#ff8c00]Send_Command.exe \\.\COM[/COLOR][COLOR=#00ff00][*insert your number here][/COLOR][/FONT]
7--Now you're in send command mode. Nothing looks different on your phone but that's ok. It should just remain in download mode.
8-- On the computer screen in the window you now see #.
9--Now in this post copy the Backup system to internal storage command specific to your device model number. Check in you settings >general >about if in doubt. This is the most important step. Copy the whole line of code. Highlight with your mouse, select everything on the line and copy.
10--You didn't come all this way to fail so do it. Remember it is device model specific.
11-- Paste it in the command window and hit enter. It should take a while so wait until you see#reappear.
12--Now typeLEAVEall in capital letters. Your device will reboot. Check using the file manager if you have a file called system.img in your internal storage. If yes step 2 is next and you did well. If no repeat it and follow the steps properly. Make sure drivers are installed especially windows 10/8/8.1 users. Check device manager
Step 2 -> Root injection.
1--Prepare your Ubuntu USB or virtual machine or computer.
2--Download inject_root zip from here and extract.
3--Copy the system.img from your phone to the extracted inject_root folder on your PC.
4-Reboot into Ubuntu.
5--Here open a terminal.
6--Gain root access on Ubuntu by typing or copy and paste sudo -i
7--You should either be asked for your password which you have to enter or if you used a USB drive like me you'll see the name change to[email protected]
8--Navigate to the inject_root folder by using cd commands. This can also be done by typing cd then [space] then dragging and dropping the folder into the terminal and hitting enter.
9--You'll now see the name in the terminal become longer with the name of the folder in it.
10--Now type chmod +x autoroot.sh
11--Hit enter then sudo ./autoroot.sh
12--If you get any thing like command not recognized or something of the sort use sudo sh autoroot.sh
-That worked for me.
13--If you're successful the name of the file should change from system.img torootedsystem.img
-Please note don't rename the files. Leave them as they are.
14--Now go back to Windows let's finish this.
Step 3 ->Root
1--Transfer the rootedsytem.img to your phones internal storage.
2--Put your phone in download mode and connect it to your PC.
3--Get into send command mode as in step one.
-Put your device in download mode and connect it to your PC.
-Open port.bat and make sure to write down the number after com. There maybe different com numbers but choose the one that has DIAG1 on the same line as it. Note it down this is important.
-Hold shift and right click in any empty space in the extracted folder. Choose open command windows here.
- In that copy and paste this
Send_Command.exe \\.\COM[*insert your number here]
-Now you're in send command mode. Nothing looks different on your phone but it's find. It should just remain in download mode.
4-Now grab your command to flash system.img line of code from this post. It isn't the same as step one. Copy that an paste in the command window. Make sure it is for your device. They are model specific.
5--This should take a while so wait until you see the # again.
6--After thatLEAVEand upon reboot you should have root.
To Un-root just flash a KDZ file compatible with your device here.
Testimonies
Spudnubs said:
Rooted H812 10g for my fellow Canadians. Enjoy!
https://www.androidfilehost.com/?fid=24052804347821979
Click to expand...
Click to collapse
Wildsheep said:
This root method works for my G4 purchased in Singapore (H815 SEA)
Click to expand...
Click to collapse
luongquang said:
Thanks to @hackarchive, H818p10f done with tut.
Click to expand...
Click to collapse
player911 said:
Fantastic. This method will also ease devs for future rooted firmwares. I really cannot see LG being able to patch this, since this is basically a 3rd party LG Flashing tool. If they block this method, then their own tool will ultimately die with it.
Click to expand...
Click to collapse
GavTheStoner said:
Fantastic! I had almost given up hope of root on my EE LG G4. Have just used this method and now rooted perfectly!
hackarchive You rock! Have a thanks!
Click to expand...
Click to collapse
articular said:
everything worked fine and i successfully got my g4 rooted
my variant is H815TR
all steps easy only the ubuntu part was a bit hard especially for a windows user ( finding an ubuntu version and usb install etc. not root injection part)
ty ty ty again )
Click to expand...
Click to collapse
rirozizo said:
if it were for me to decide if we should delete the low effort root method, i'd totally delete it.
"The more 'manual', the better"
Click to expand...
Click to collapse
Moe5508 said:
Only method that roots my device successfully...I updated to 10e of the H815P and using this method (and only this!0 I was able to root my phone...ah felt so good...
The other 1-click rooting methods I came across in other parts of this forum just fail on the G4...
Click to expand...
Click to collapse
Marshmallow and root situation read here
Hit thanks if you appreciate. Hope I helped.
Credits to them whom without this won't be possible :good:
Thecubed
Team Codefire
ManhIT
This is a good method, thanks for writing this up.
I would like to add a few points....
I recommend you do keep your original system.img on your phones regular internal storage. If you encounter any boot issues you can then re-enter download mode and write the original system.img over the top of the failed root attempt. Use the same command from "step 3: root" but replace rootedsystem.img with system.img. This should still be on your phone from step 1 and will recover your phone from a failed root injection attempt. Note that it will not recover your phone if you messed up the dd command and overwrote other partitons. Be sure to use the right dd command and cut n paste to prevent seek/offset typeos.
I also recommend that you keep a backup of your system.img on your pc. When you run autoroot.sh in step 2 the copy on your pc will be renamed and patched. I suggest copying system.img somewhere else first, or re-copy it off your phone.
Additional credits to blog.lvu.kr. This is the blog of the hobbyist who reverse engineered the download mode protocol, created send_command.exe and gave it to the world. Kudos to you.
How is this any easier than the original method....if anything this requires even more work
kyle1867 said:
How is this any easier than the original method....if anything this requires even more work
Click to expand...
Click to collapse
It's for those who have rare variants.
psycho_asylum said:
It's for those who have rare variants.
Click to expand...
Click to collapse
Then you should probably take out the claim that this method is easier from the OP
Can this be used to inject Xposed as well for those of us with locked BLs.
djkinetic said:
Can this be used to inject Xposed as well for those of us with locked BLs.
Click to expand...
Click to collapse
No, we need to wait for a custom recovery.
psycho_asylum said:
No, we need to wait for a custom recovery.
Click to expand...
Click to collapse
Just used flash fire it worked rocking xposed now on 810!
djkinetic said:
Just used flash fire it worked rocking xposed now on 810!
Click to expand...
Click to collapse
Oh nice! I wasn't adventurous enough to try it. I'll make a system backup and give it a whirl!
Very nice thread, thank you. The steps were short, few, and fairly concise.
I was waiting for something like this where I could modify my own image and I wouldn't have to wipe everything or replace it with a new image.
One thing you might want to mention is that if your phone is encrypted, you'll need to unencrypt it first.
Can anyone link me to some instructions on how to disable OTA updates for an unlocked/international H815T?
kyle1867 said:
How is this any easier than the original method....if anything this requires even more work
Click to expand...
Click to collapse
This is what XDA is all about. It tells you how to inject root into your OWN system image. it's the opposite of spoon feeding. it's about teaching members how to do things for themselves. Too many people come here expecting to be spoon fed and have thigns done for them. This thread teaches people how to do their own work, while learning something at the same time.
Good work OP! :good:
the_scotsman said:
This is what XDA is all about. It tells you how to inject root into your OWN system image. it's the opposite of spoon feeding. it's about teaching members how to do things for themselves. Too many people come here expecting to be spoon fed and have thigns done for them. This thread teaches people how to do their own work, while learning something at the same time.
Good work OP! :good:
Click to expand...
Click to collapse
Thanks. I guess people don't know what XDA is about. Seeing noobs and others trying to spit on hard work when I used my time and device as Guinea pig. Also people don't know this is almost brick-proof because the system image if from their devices. Unless they use wrong commands but all here is just copy and paste. They see lot's of text and get cold feet. Anyways will be updating the OP with system images. If yours is available please share. If you see your image available and you have drivers and LG_root downloaded proceed to step 3.
The only downside is that I have to drag out my windows laptop instead of doing everything on the ubuntu machine I use at work.
But if that's the biggest of my problems then I don't really have a problem
hi, thx for this tutorial, looks good
when flashing back the rooted img,does it wipe everything ? apps, data ... etc
thx
EDIT: just correct me if im wrong
using this method WILL NOT wipe everything on my device cause im rooting my system with everything on it
correct ???
must make sure before i go ahead
thx
How to calculator extractly bs/seek/count ?
Is there a possibility of any personal data being written to /system on a phone during normal use? I can provide 10c Optus AU (carrier 505-02) if I can be sure its not identifying, but ive been using the phone a couple of weeks.
Download link:
https://www.androidfilehost.com/?fid=24052804347799013
optiplex2012 said:
using this method WILL NOT wipe everything on my device cause im rooting my system with everything on it
correct ???
Click to expand...
Click to collapse
correct.
---------- Post added at 06:01 PM ---------- Previous post was at 05:29 PM ----------
djkinetic said:
Can this be used to inject Xposed as well for those of us with locked BLs.
Click to expand...
Click to collapse
HTCuser90 said:
How to calculator extractly bs/seek/count ?
Click to expand...
Click to collapse
I would also like to know this. You can resolve system by running the following. Note that this is for the H815T and is not the same on all variants.
# ls -lZ /dev/block/bootdevice/by-name/system
You'll get something like:
lrwxrwxrwx root root ubject_r:block_device:s0 system -> /dev/block/mmcblk0p47
Which tells you the actual block device (partition its on).
And you can see the size of that with:
# cat /proc/partitions
where you see:
major minor #blocks name
<snip>
259 15 4239360 mmcblk0p47
<snip>
However I dont know how to identify how large a block is or how to calculate the start offset in the main partition.
ok, it worked great
wasnt easy, since im not so familiar with using ubuntu, but all is ok
the explanation of the how to... was great and nothing lost
my H815L is now rooted
thx guys
djkinetic said:
Just used flash fire it worked rocking xposed now on 810!
Click to expand...
Click to collapse
I know it's kind of going off topic, but I figured I'd mention that Flash Fire doesn't work on VS986. It just goes to a black screen and sits there forever. I left it sit for almost an hour. I saw elsewhere it has something to do with automount, I'll have to mess with it further.
hackarchive said:
Hit thanks if you appreciate. I spent hours trying to root so hope I helped.
Click to expand...
Click to collapse
Appreciated but you should include a way to unroot (undo) as well, ie how do we get back to stock (if required) ?
Can someone with rooted stock OK3 (and OK3 bootloaders) please do the following for me?
-busybox dd if=/dev/block/mmcblk0 of=/sdcard/unbrick.img bs=1024 count=81920
-alternatively you can run this file in recovery which will dump the necessary files to /sdcard/Unbrick_files/: https://androidfilehost.com/?fid= 23578570567721355
-Upload the unbrick.img and send it to me
here are the guides that I am following (which have some precedent for working with SGS5):
http://forum.xda-developers.com/showpost.php?p=47911843&postcount=165
http://forum.xda-developers.com/showthread.php?t=2345860
http://forum.xda-developers.com/verizon-galaxy-note-3/general/howto-recover-hard-brick-t2834419
I recently bricked my phone by accidentally flashing a BOD5 bootloader over a rooted OK3 (and OK3 bootloader) system. This obviously led to a hard brick, and I'm trying to see if I can fix it. Thanks.
I can't confirm or deny if the debrick procedure works on the S5, but I made a debrick.img just in case. I'm on the BOD5 bootloader, so my debrick.img won't help you.
I do have helpful information to add, though. I'm not sure where the busybox part came from, but the path you posted is wrong for the S5. The internal storage is sdcard0, and external storage is extSdCard. The fist command needs to be su, and the second command needs to be:
dd if=/dev/block/mmcblk0 of=/storage/sdcard0/debrick.img bs=1024 count=131072 for internal storage.
dd if=/dev/block/mmcblk0 of=/storage/extSdCard/debrick.img bs=1024 count=131072 for external storage.
CVertigo1 said:
I can't confirm or deny if the debrick procedure works on the S5, but I made a debrick.img just in case. I'm on the BOD5 bootloader, so my debrick.img won't help you.
I do have helpful information to add, though. I'm not sure where the busybox part came from, but the path you posted is wrong for the S5. The internal storage is sdcard0, and external storage is extSdCard. The fist command needs to be su, and the second command needs to be:
dd if=/dev/block/mmcblk0 of=/storage/sdcard0/debrick.img bs=1024 count=131072 for internal storage.
dd if=/dev/block/mmcblk0 of=/storage/extSdCard/debrick.img bs=1024 count=131072 for external storage.
Click to expand...
Click to collapse
jrkruse helped me out a lot and I was able to get my hands on an OK3 unbrick.img. IT WORKS. You're right about me posting the wrong code. The file that he used to get me the unbrick.img included the following code:
#!/sbin/sh
mkdir -p /external_sd/Unbrick_Files/;
dd if=/dev/block/mmcblk0 of=/external_sd/Unbrick_Files/200MB.img bs=4096 count=50000;
busybox gzip /external_sd/Unbrick_Files/*;
mv /external_sd/Unbrick_Files/200MB.img.gz /external_sd/Unbrick_Files/Unbrick_IMG.gz;
chmod -R 777 /external_sd/Unbrick_Files
the file is available here:
http://forum.xda-developers.com/attachment.php?attachmentid=3609202&d=1452712258
Hariiiii said:
the file is available here:
http://forum.xda-developers.com/attachment.php?attachmentid=3609202&d=1452712258
Click to expand...
Click to collapse
you have linked the unbrick-creator.zip rather than the BOK3 unbrick.img
I am almost in the same situation as you. Can you please write the steps and the link for the BOK3.img ?
I think this is the correct link to the BOK3 unbrick img. You'll have to scroll down to the mediafire link
http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370/page11
Flash the file using win32diskimager.exe onto a microSD and boot into download mode.
Hope that works.
Also, if anyone has a rooted OG5, I would really appreciate an OG5 debrick.img!
Does booting from the SD card work on the S5? I bricked my S5 a few months back and had to get a replacement. It would have been nice to know that it would boot from SD.
CVertigo1 said:
Does booting from the SD card work on the S5? I bricked my S5 a few months back and had to get a replacement. It would have been nice to know that it would boot from SD.
Click to expand...
Click to collapse
Yes it does work, I can personally confirm it.
That's great!!! I'm assuming you were on the BOE1 bootloader, right?
CVertigo1 said:
That's great!!! I'm assuming you were on the BOE1 bootloader, right?
Click to expand...
Click to collapse
Yeah, that one is still used for the OK3 firmware, yeah?
Thanks for confirming that I did that right guys
jjdavis699 said:
Thanks for confirming that I did that right guys
Click to expand...
Click to collapse
Dammit sorry I should've thanked you personally. You pretty much were the direct reason I was able to unbrick. I know jkruse thanked you for the file but I probably also should have posted because the file was for me...
Hariiiii said:
Dammit sorry I should've thanked you personally. You pretty much were the direct reason I was able to unbrick. I know jkruse thanked you for the file but I probably also should have posted because the file was for me...
Click to expand...
Click to collapse
It's fine mate. Just enjoy your reinvigorated phone. I just did the file as something to waste a little time. Glad to see its working fine.