Database Users

[Q] Stock AU A500

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

USA 1.141.07 update fix with. .img's

Crsdr37 said:
Alright Guys in the USA. I will be posting the .img files to fix your device or update your device to 1.141.07 if you have either used the chinese update fix or some other various fix that left you with a different boot image. The instructions are simple.
1. Connect your tablet to the computer via USB. Put the boot.img and the system.img on your SD Card. Also put the Update.zip then use a file explorer to move the update.zip to the root of your SD card. Which is external SD. If you use Astro. (Alternatively you can just take your SD card out and put it in your computer to put the update.zip.)
2. You need to first push the boot.img
-Open ADB type su then hit enter. (your device will prompt for superuser you must select allow) Then enter the command below.
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p2 (hit Enter)
3. Then push the system.img
dd if=/sdcard/system.img of=/dev/block/mmcblk0p3
4. Force shutdown your device when those finish (as your screen may not turn on.)Then hold volume - and the power button "until the green android comes up very important do not let them go just because the device turns on" to start the update.zip. Let it finish (Your device will reboot when it completes.
5. Enjoy the fact your device is back to stock and you can now update when future updates release.
To push the files you will need adb shell. If you dont know what that is look it up, It is part of the android development kit. Second these 2 commands will push the files to their proper mount block. You must push the boot.img first then the system.img These files are for the USA update 1.141.07
http://www.megaupload.com/?d=TNDCAYC8 - System.img -MD5-2b4e2fea567ac883bb483fc96b1fdc9d
http://www.mediafire.com/?7b5llkk8bnmnd23 -Update.zip
http://www.mediafire.com/?3qahjh3twi6jc9t -Boot.img -MD5-4477d6739dd1e3b3ba1dbf94be7fe8f0
Here are 2 Mirrors To download the boot.img you will need to download both as the uploader made it a 2 part file making it easier for some countries to download. Give thanks yo ardatdat if these came in handy.
http://www.zshare.net/download/91195486183633a0/
http://www.zshare.net/download/9119547812fdf5fa/
I will check periodically on this thread if anyone has questions or needs Help. Guve a huge shout out to deckofficer54 as he is a co-worker and friend that dumped these files for me when I screwed my system up.
Click to expand...
Click to collapse
** Alright guys I am just posting this link for when you just do the update.zip because you are already on 1.104.05_COM_GEN1 and you have a different kernel then the update.zip, What will happen is when you reboot the tablet from just doing the update.zip you may have WIFI error. These files should resolve that issue. Once again they are only if you have WIFI Error on reboot. To install these you will need some type of file explorer that has rw access to the file system. I rec. Root Explorer. To install these follow these instructions.
1. Copy both modules to your SD card does not matter where.
2. With your File Explorer/Manager Copy both of these files. (Root Explorer will let you multi-select if you hit the menu button.)
3. Navigate to System/Lib/Modules.
4. **This step is very important- You must Mount your System for RW access. If you don't they will not copy. Once you have RW just hit the paste button and then reboot your device.
5. **This step is for anyone still having wifi error after reboot. (Stop being lazy lol and just do all the steps. From the top by mounting the boot.img and system.img that way your device is 100% stock there for no checksum issues.
http://forum.xda-developers.com/attachment.php?attachmentid=601473&d=1305842073 - This is the wifi modules Download Link.
Thank you thor2002ro for posting these on your kernel modules thread. Which is found here for anyone having any other issues.
http://forum.xda-developers.com/showthread.php?t=1058713
Happy Updating
​
Alright guys here is the list of supporters thus far for the unbricking and or updating of your tablet. If I missed someone let me know.
Supporters:
Euclid's Brother -Awesome tool to flash the images Making your lives easier one click at a time. If you want an easier way download these images and use this app https://market.android.com/details?id=com.interphaze.Acer_ROM_Flasher
bhageman -Donation
aerichards1977 -Donation
Sent from my PC36100 using XDA Premium App

thanks so much for this. to verify my build number is 1.141.07_COM_GEN1 is that right?

Success! This worked like a charm! I didn't have to use the recovery img I just used the update.zip.
After update:
Kernel: g9b3ce2b
Build: Acer_A500_1.141.07_COM_GEN1
Good work and thanks!
edit: Actually I guess I do have one issue right now. After the update my wifi stopped working. When I go to the wifi settings I see "Error" under Wi-Fi and the check box is grayed out so that it can't be clicked. Any help?

Had a German 1.112 build i guess, bricked it and revocered it with Acer_A500_1.122.01_EMEA_GEN5. Used boot and system image and then updated and it really works!!! Thank you very very very much!!!
EDIT1: I even not lost my settings and can set the language to German too!!
EDIT2: Root gone (as expected), used Gingerbreak (tab version) and everything works fine.

phone.ds said:
Had a German 1.112 build i guess, bricked it and revocered it with Acer_A500_1.122.01_EMEA_GEN5. Used boot and system image and then updated and it really works!!! Thank you very very very much!!!
Click to expand...
Click to collapse
Your Very Welcome. Took me some time to get all the files but this **** works like a frickin charm. I wish it wasnt such a pain in the ass but hey its fixed.

ryutsuke said:
Success! This worked like a charm! I didn't have to use the recovery img I just used the update.zip.
After update:
Kernel: g9b3ce2b
Build: Acer_A500_1.141.07_COM_GEN1
Good work and thanks!
edit: Actually I guess I do have one issue right now. After the update my wifi stopped working. When I go to the wifi settings I see "Error" under Wi-Fi and the check box is grayed out so that it can't be clicked. Any help?
Click to expand...
Click to collapse
well the only thing I can think of it either the lib modules for wifi are messed up in which case I can post a link with them or the kernel is different. I would use the 2 .img that I posted then use the update zip. That way the images replace your kernel which is always the root cause of wifi errors.

here is a link to the wifi lib modules. You need to use something like root explorer. To mount the system as rw. Then navigate to system/lib/modules and copy those two files into there with the system mounted as rw. Reboot and see if it fixes the issue!!
http://www.megaupload.com/?d=OKU671AP

futty said:
thanks so much for this. to verify my build number is 1.141.07_COM_GEN1 is that right?
Click to expand...
Click to collapse
Yes you are now stock and able to update when they release 3.1

dont we need to flash flexrom.img to be 100% stock?

The flexrom was flashed with the update zip
Sent from my A500 using XDA Premium App

confirmed working as well.

Crsdr37 said:
here is a link to the wifi lib modules. You need to use something like root explorer. To mount the system as rw. Then navigate to system/lib/modules and copy those two files into there with the system mounted as rw. Reboot and see if it fixes the issue!!
Click to expand...
Click to collapse
Am I missing something or did you maybe forget the link =P

Ah **** lol give me 1 second
http://www.megaupload.com/?d=OKU671AP
Sent from my A500 using XDA Premium App

Did those libs help at all?a like I said if they don't the only fix I I now would be to go back to the german or chinese update then flash both. Img then update.
Sent from my A500 using XDA Premium App

Image updates
Maybe some file corruption?! Loaded per the directions and on boot got error:
"Secure Boot Image LNX checksum fail"
Going back to the Chinese Rom.

You get that only when do don't do all three'. Once you reboot after pushing the 2 images. You have to hold down the volume - and the power button it will then run the update zip to complete.
Sent from my A500 using XDA Premium App

Crsdr37 said:
Yes you are now stock and able to update when they release 3.1
Click to expand...
Click to collapse
thanks so much again. you are a god i bet you helped millions by doing this

That was my intentions I came from the evo forums. Everybody there helps each other. Im just hoping people here pick it up and start helping when people have questions.
Sent from my A500 using XDA Premium App

ryutsuke said:
Success! This worked like a charm! I didn't have to use the recovery img I just used the update.zip.
After update:
Kernel: g9b3ce2b
Build: Acer_A500_1.141.07_COM_GEN1
Good work and thanks!
edit: Actually I guess I do have one issue right now. After the update my wifi stopped working. When I go to the wifi settings I see "Error" under Wi-Fi and the check box is grayed out so that it can't be clicked. Any help?
Click to expand...
Click to collapse
Did you ever get wifi working
Sent from my A500 using XDA Premium App

tomlogan1 said:
Maybe some file corruption?! Loaded per the directions and on boot got error:
"Secure Boot Image LNX checksum fail"
Going back to the Chinese Rom.
Click to expand...
Click to collapse
Were u able to get past the checksum error?
Sent from my A500 using XDA Premium App

[Q]How to extract CPUID from bricked A500

My partner has a bricked A500. It will NOT boot so any utilities utilising adb/dmesg fail. I can boot into fastboot mode (v0.03.11-ICS) but fastboot returns USB write errors stating invalid partition format "." So, I assume I have to use nvFlash to re-write the partition table but this still requires the SBK that I can not generate as I do not know what my CPUID is.
I have read so many threads all offering tweaked variations of the same process but I haven't found as yet a definitive how-to on re-creating your CPUID/SBK on a bricked device as they all assume you either know your CPUID or the tablet stills boots so you can retrieve it easily.
Does anyone have any links to resources to assist? I currently can boot into fastboot and APXmode. Attempts to factory reset seem to kick off OK but then fail with errors erasing data/cache etc... I have both windows/linux and the tablet is recognized in APX/fastboot mode on both OS's.
Thanks

1- download the attached file
2- go to linux
3- install GCC , lsUSB , Libusb-1.0.x , libusb-1.0-dev (from “Ubuntu software center” )
4- drag and drop the APX.c file in your desktop
5- connect your tablet to the computer (through mini USB) and put it in APX mode
6- Now on computer fire up “Terminal” and type this code
Code:
cd Desktop
sudo su
gcc apx.c -o apx -lusb-1.0
7- a new file should appear in your desktop
8- keep typing :
Code:
./apx
it will return to you the UID (AKA: CPUID)
DONE

Error: Failed to open device
Dr.GM said:
1- download the attached file
2- go to linux
3- install GCC , lsUSB , Libusb-1.0.x , libusb-1.0-dev (from “Ubuntu software center” )
4- drag and drop the APX.c file in your desktop
5- connect your tablet to the computer (through mini USB) and put it in APX mode
6- Now on computer fire up “Terminal” and type this code
Code:
cd Desktop
sudo su
gcc apx.c -o apx -lusb-1.0
7- a new file should appear in your desktop
8- keep typing :
Code:
./apx
it will return to you the UID (AKA: CPUID)
DONE
Click to expand...
Click to collapse
Many thanks for the walkthrough.. n sorry for being such a noob!
My A500 is bricked, and not flashing through update.zip method.. dint have my cpuid so decided to follow your guide.. installed Ubuntu on my windows pc, installed all the additional packages you just mentioned, but after the last command of ./apx it returns with Error: Failed to open device !!!
Now What? can there be ANY way or ANYTHING i can do to get over with this LLAAAST step? pretty pretty please!?
Thanks in Advance!

dishoom said:
Many thanks for the walkthrough.. n sorry for being such a noob!
My A500 is bricked, and not flashing through update.zip method.. dint have my cpuid so decided to follow your guide.. installed Ubuntu on my windows pc, installed all the additional packages you just mentioned, but after the last command of ./apx it returns with Error: Failed to open device !!!
Now What? can there be ANY way or ANYTHING i can do to get over with this LLAAAST step? pretty pretty please!?
Thanks in Advance!
Click to expand...
Click to collapse
Put your device in APX mode, manually. Then get it.
Sometimes, if you leave it in what you think is APX mode, for a certain amount of time, you may not be able to connect to it. So do it fresh.

Moscow Desire said:
Put your device in APX mode, manually. Then get it.
Sometimes, if you leave it in what you think is APX mode, for a certain amount of time, you may not be able to connect to it. So do it fresh.[/QUOTE
Hmm thanks.. Meanwhile I did the code tweak as digested here: http://forum.xda-developers.com/showthread.php?t=2331151
And got my cpuid as 0x00000042dfd497
Hope this is what I needed? Although the characters are 14 if I exclude 0x?
Thanks again mate!
Click to expand...
Click to collapse

dishoom said:
Moscow Desire said:
Put your device in APX mode, manually. Then get it.
Sometimes, if you leave it in what you think is APX mode, for a certain amount of time, you may not be able to connect to it. So do it fresh.[/QUOTE
Hmm thanks.. Meanwhile I did the code tweak as digested here: http://forum.xda-developers.com/showthread.php?t=2331151
And got my cpuid as 0x00000042dfd497
Hope this is what I needed? Although the characters are 14 if I exclude 0x?
Thanks again mate!
Click to expand...
Click to collapse
Well, if I'm not mistaken, it should be 16. You can try it either way.
Click to expand...
Click to collapse

SUCCESS!!
I finally managed to unbrick my tab, SPECIAL thanks to @Moscow Desire, @eppeP, @civato and @srbeen.. here's what i did, thought it might help someone else like me!
Booted my PC in Ubuntu, to extract the CPUID, as i didnt have it saved. for that i used instructions from this post: http://forum.xda-developers.com/showthread.php?t=1751978
Nevertheless, i couldnt completely follow it till unbricking, as somehow things didnt quite work out as expected. Expecially, the UID i recovered was as i quoted above, filled with many zeroes.. i got the correct one after tweaking with apx.c file as advised here: http://forum.xda-developers.com/showthread.php?t=2331151 because i later realized i was using a 32-bit system.
After recovering my UID, downloaded the "V8-UNL-ICS-HC-bootloader-MULTI-cwm.zip" thing, given here: http://forum.xda-developers.com/showthread.php?t=1622425 .. its a simplified form of nvflash, and is easier to operate for less techno ppl like me. Booted to windows, downloaded and extracted it, and edited the v8.bat file to remove any cls commands and see what this thing does. Then, opened the command prompt with Administrative rights, and run the V8.bat file... Once my tab was unbricked, i could easily flash any update.zip package i wanted!!
Sounds easy! but believe me, its easier said than done! took me over a week to complete the whole process as i tried almost EVERYTHING as anyone suggested in ANY post to unbrick my tab! but nevertheless, got the result finally and thats what matters!
Guys, the devs at xda, You ROCK!! :good::good:

dishoom said:
I finally managed to unbrick my tab, SPECIAL thanks to @Moscow Desire, @eppeP, @civato and @srbeen.. here's what i did, thought it might help someone else like me!
Booted my PC in Ubuntu, to extract the CPUID, as i didnt have it saved. for that i used instructions from this post: http://forum.xda-developers.com/showthread.php?t=1751978
Nevertheless, i couldnt completely follow it till unbricking, as somehow things didnt quite work out as expected. Expecially, the UID i recovered was as i quoted above, filled with many zeroes.. i got the correct one after tweaking with apx.c file as advised here: http://forum.xda-developers.com/showthread.php?t=2331151 because i later realized i was using a 32-bit system.
After recovering my UID, downloaded the "V8-UNL-ICS-HC-bootloader-MULTI-cwm.zip" thing, given here: http://forum.xda-developers.com/showthread.php?t=1622425 .. its a simplified form of nvflash, and is easier to operate for less techno ppl like me. Booted to windows, downloaded and extracted it, and edited the v8.bat file to remove any cls commands and see what this thing does. Then, opened the command prompt with Administrative rights, and run the V8.bat file... Once my tab was unbricked, i could easily flash any update.zip package i wanted!!
Sounds easy! but believe me, its easier said than done! took me over a week to complete the whole process as i tried almost EVERYTHING as anyone suggested in ANY post to unbrick my tab! but nevertheless, got the result finally and thats what matters!
Guys, the devs at xda, You ROCK!! :good::good:
Click to expand...
Click to collapse
Speaking for the rest of the mentions, you are most welcome.

Unpack stock System.img?

Hello Moto
I've just downloaded Verizon Jelly Bean 4.1.1 by "Firmware Team".
Just to play with it a little, extract apks and test them on Galaxy SII Skyrocket.
The thing is i'm having a hard time opening system.img.
Now i've tried LinuxReader, Unyaffs and ext2explore/read but none of these can open it, they all say that it's an unrecognized image.
Do you guys know how to properly open a stock moto System.img?

lingowistico said:
Hello Moto
I've just downloaded Verizon Jelly Bean 4.1.1 by "Firmware Team".
Just to play with it a little, extract apks and test them on Galaxy SII Skyrocket.
The thing is i'm having a hard time opening system.img.
Now i've tried LinuxReader, Unyaffs and ext2explore/read but none of these can open it, they all say that it's an unrecognized image.
Do you guys know how to properly open a stock moto System.img?
Click to expand...
Click to collapse
Google for a tool called simg2img (I used the python script that appears in get first few results, there should be other versions as well). That will unpack the image into a plain ext4 image that you can mount with any Linux pc (I recommend using a virtual machine if you have windows or mac).
Happy hacking!
Sent from my XT907

aslomagic, did you try this with the firmware lingowistico is talking about? I also tried before to unpack system.img from this package, and system.img.ext4 from ICS package, and another ICS soft for XT897, and all of them give "Bad magic" error in simg2img. All of those softs are published by the same "Firmware Team" - maybe that's the case? I also tried dsixda kitchen (which also uses simg2img, but anyway...) and it also didn't work. Might be also some custom Motorola's approach to system.img....
Could you possibly help? Thanks.

micx_pl said:
aslomagic, did you try this with the firmware lingowistico is talking about? I also tried before to unpack system.img from this package, and system.img.ext4 from ICS package, and another ICS soft for XT897, and all of them give "Bad magic" error in simg2img. All of those softs are published by the same "Firmware Team" - maybe that's the case? I also tried dsixda kitchen (which also uses simg2img, but anyway...) and it also didn't work. Might be also some custom Motorola's approach to system.img....
Could you possibly help? Thanks.
Click to expand...
Click to collapse
Well, I know for a fact that those images are packed ext4, but I haven't tried specifically with that one.
Now that you mention, I think I remember signed images (like those ones) have some additional header, maybe that needs to be removed with an hex editor, or with dd of you like
If I get a chance, I'll try and report back...
Sent from my XT907

aslomagic said:
Well, I know for a fact that those images are packed ext4, but I haven't tried specifically with that one.
Now that you mention, I think I remember signed images (like those ones) have some additional header, maybe that needs to be removed with an hex editor, or with dd of you like
If I get a chance, I'll try and report back...
Click to expand...
Click to collapse
Ok, I tried, and yes, it complains it cannot find the magic (again, I'm using the python script). I modified the script to look for the magic value in the first 50Mb of the file, and if it finds it, it starts unpacking from there. Python scripts are very easy to play with
It seems to work for me, but I don't have a linux vm handy to see if it mounts correctly (I'm currently on a mac). micx_pl, can you give it a try and let me know?
I had to zip the file even though it's very small because the forum won't let me upload a .py file... who knows, just unzip it.

Holy cow! It works! You're the master I was looking for such solution everywhere, and was stunned to see barely few topics with similar problem, and no solution at all. Thanks!

micx_pl said:
Holy cow! It works! You're the master I was looking for such solution everywhere, and was stunned to see barely few topics with similar problem, and no solution at all. Thanks!
Click to expand...
Click to collapse
You're welcome, glad I could help!
Sent from my XT907

aslomagic said:
Ok, I tried, and yes, it complains it cannot find the magic (again, I'm using the python script). I modified the script to look for the magic value in the first 50Mb of the file, and if it finds it, it starts unpacking from there. Python scripts are very easy to play with
It seems to work for me, but I don't have a linux vm handy to see if it mounts correctly (I'm currently on a mac). micx_pl, can you give it a try and let me know?
I had to zip the file even though it's very small because the forum won't let me upload a .py file... who knows, just unzip it.
Click to expand...
Click to collapse
HOLY $#!+ THANKS!!! I've been trying to decompress the moto images for awhile and have never been able to do it until now

Would it be possible to modify make_ext4fs to re-sparse the image and copy the original signature?

Q9Nap said:
Would it be possible to modify make_ext4fs to re-sparse the image and copy the original signature?
Click to expand...
Click to collapse
You're welcome to try ... my guess is that it could be made to work if the image was an official, originally signed image that was unpacked by the script above or equivalent, but if you want to modify it, re-pack it and re-attach the signature, most likely the signature won't match the content. But I may be wrong, so if somebody is willing to try, best of luck to you
If your goal is just to create a packed image, but not necessarily signed (needs bootloader unlock), then I'd say it's definitely possible, search around here.

aslomagic said:
You're welcome to try ... my guess is that it could be made to work if the image was an official, originally signed image that was unpacked by the script above or equivalent, but if you want to modify it, re-pack it and re-attach the signature, most likely the signature won't match the content. But I may be wrong, so if somebody is willing to try, best of luck to you
If your goal is just to create a packed image, but not necessarily signed (needs bootloader unlock), then I'd say it's definitely possible, search around here.
Click to expand...
Click to collapse
i'm sure you're right about the signature not working on a modified image; it was just wishful thinking. the idea of course would be to inject superuser.apk and su, which wouldn't be necessary on a bootloader unlocked device.
for bootloader unlocked devices though, the ability to repack a modified image does give you another way to build custom roms. here's the code to unpack and repack images with simg2img.py and make_ext4fs:
Code:
mkdir system
./simg2img.py system.img.ext4 system.raw
sudo mount -t ext4 -o loop system.raw system/
#make changes, then:
wc -c system.raw #lists size in bytes of system.raw
sudo make_ext4fs -s -l 1234567890 -a system system.img system/ #where 1234567890 is output from wc -c
sudo umount system
rm -rf system
i've used this proecess with samsung system images, should work for moto images now too (bootloader unlocked, of course)

Yep, it's a good cheat sheet reference
Besides, on razr m and hd at least, you can also use this with safestrap without unlocking the bootloader.

aslomagic said:
Besides, on razr m and hd at least, you can also use this with safestrap without unlocking the bootloader.
Click to expand...
Click to collapse
Not sure what you mean by this; do you mean you could mount a modified system.img with safestrap? I guess it's possible since safestrap uses a system.img on the emmc, interesting idea

Q9Nap said:
Not sure what you mean by this; do you mean you could mount a modified system.img with safestrap? I guess it's possible since safestrap uses a system.img on the emmc, interesting idea
Click to expand...
Click to collapse
Yes, that's what I mean, more or less. You don't need safestrap to just mount it (use the terminal and "mount"), but you can use it to boot from it and try it.
I did this to try the Telstra image that pjcons dumped, which is pre-rooted and not signed (there it's no official signed image to date), and with a few tricks it worked without me having to unlock the bootloader.
Sent from my XT907

aslomagic said:
Google for a tool called simg2img (I used the python script that appears in get first few results, there should be other versions as well). That will unpack the image into a plain ext4 image that you can mount with any Linux pc (I recommend using a virtual machine if you have windows or mac).
Happy hacking!
Sent from my XT907
Click to expand...
Click to collapse
hello, i cant find anything on the basics of how this works, could you point me somewhere that explains it step by step or do one here. sorry of the noob question

TheWhiteChallenger said:
hello, i cant find anything on the basics of how this works, could you point me somewhere that explains it step by step or do one here. sorry of the noob question
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1588461

CNexus said:
http://forum.xda-developers.com/showthread.php?t=1588461
Click to expand...
Click to collapse
Thanks for the link I need to go learn Linux now. Lol I dontbgt the virtual machine thing at all. Its basically a Linux emulator right?
Sent from my XT1080 using XDA Premium 4 mobile app

TheWhiteChallenger said:
Thanks for the link I need to go learn Linux now. Lol I dontbgt the virtual machine thing at all. Its basically a Linux emulator right?
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No need to
http://sourceforge.net/projects/androidicsjbext/

CNexus said:
No need to
http://sourceforge.net/projects/androidicsjbext/
Click to expand...
Click to collapse
oh damn it. ok first i do appreciate the help. but that sucked. that was the frist program i tryed and it gives me "unknown file format" have i just been screwing up from the begining?

Root ANY LG G4 Variant 100% Success Directives | Root Injection | Less Bricks

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) ?