Database Info

[Q] boot.img

can someone with root post up a boot.img?
dd if=/dev/block/mmcblk?p?? of=/sdcard/boot.img iirc

If you read the other posts you will see that the boot partition is not exposed to the kernel. There is no way of dumping it like that. We can dump a whole region of the emmc though which contains boot but we have no way yet of knowing the boundaries...
Sent from my HTC Vision using XDA App

Them ASUS guys sure are sneaky! My friend is getting one. Looks like some of my knowledge from the XOOM won't help here.

Scourge1024 said:
Them ASUS guys sure are sneaky! My friend is getting one. Looks like some of my knowledge from the XOOM won't help here.
Click to expand...
Click to collapse
this wont work?
cat /dev/block/platform/sdhci-tegra.3/by-name/boot > /sdcard/boot.img

graffixnyc said:
this wont work?
cat /dev/block/platform/sdhci-tegra.3/by-name/boot > /sdcard/boot.img
Click to expand...
Click to collapse
partitions are hidden, and generated by a "tegrapart" information, which then translates into a MBR block only showing what they want you to see..
a complete tree woult be 12-15 partitions , but like on many other tablets lilke ElocityA7 and newer ones, you got only the system needed ones..
rest can only be written to from bootloader, or exposed if you change the boot.img tegrapart and configure it correctly, if fully supported.

[Q] Will I brick my N5 if I do this?

Update - Yes, the procedure below works. It will not brick my N5.
I have not done much with Google phones so I am a little bit afraid of the risk of bricking my N5. Can someone help me take a look at what I plan to do and advise me whether there is something incorrect?
What I want to do is to remove some APKs and add the su binary to Google's factory image. I downloaded the latest version: hammerhead-ktu84p. Extracted the file system.img and moved it to an Ubuntu Linux virtual machine.
I used the utility simg2img to first de-sparse the system.img file:
sudo simg2img system.img expanded_system.img
Then mounted it on /system:
sudo mount -o loop expanded_system.img /system
I added the su binary to /system/xbin with the right permissions (6755). I also removed some APKs from /system/app.
Then I used make_ext4fs to repack the /system folder into a new system.img file:
sudo make_ext4fs -s -l 1024M -a system system.img /system
Now I would like to use fastboot to flash this new system.img file. Does it sound like I am doing the right things? Any risks with doing so?

The worst secnerio is that android cant boot up from your edited system. You dont have to worry if that happens, you just simply have to flash back the original system from google's rom
Tapatalk-kal küldve az én Nexus 5-el

What the person above said. One of the many cool things us Nexus users benefit is we have factory images and we have fastboot which is cool. You'd have to really really do something nuts to brick a Nexus.
Sent from my Nexus 5 using Tapatalk

Why did you not just flash su into the system
Please fix the F/C on this application. Thx.

Thanks to both of you. This is very assuring. So, off to my experiment.
flashback7 said:
What the person above said. One of the many cool things us Nexus users benefit is we have factory images and we have fastboot which is cool. You'd have to really really do something nuts to brick a Nexus.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse

wxppro said:
Thanks to both of you. This is very assuring. So, off to my experiment.
Click to expand...
Click to collapse
I would just make a ROM zip instead. Easier to edit in case of problems, on device flashable, shareable, etc.
I cant think of one benefit the img has over the zip in your case.

Sounds like a lot of trouble for very little benefit but it can't hurt.

You started saying you don't have much experience with Google. Why are you making it so complicated?
Root is easy. Takes 5 minutes, risk free if done right. What you are doing could potentially go sour.
Unlock bootloader. Flash custom recovery. Install SuperSU. Done.
And to get rid of apps, use titanium backup. Tho freezing is better. They're not big files, and you can simply unfreeze if needed. Can't take an ota if they are gone. And if you uninstall something you shouldn't, you'll be flashing the firmware again.
Keep it simple.

KJ said:
Unlock bootloader. Flash custom recovery. Install SuperSU. Done.
Click to expand...
Click to collapse
Unfortunately everyone just wants to "root without losing data" because its so much of a bother to simply copy your internal storage /sarcasm
Oh and use toolkits because they have "magic" and they're "easy to use".
Because it really is hard to do a few simple steps and avoid a possible, uh, "softbrick"; is what they call it these days?
Sent from my Nexus 5

Lethargy said:
Unfortunately everyone just wants to "root without losing data" because its so much of a bother to simply copy your internal storage /sarcasm
Oh and use toolkits because they have "magic" and they're "easy to use".
Because it really is hard to do a few simple steps and avoid a possible, uh, "softbrick"; is what they call it these days?
Sent from my Nexus 5
Click to expand...
Click to collapse
Ah. Lol
Everyone is different I guess. I don't have much data I care about. Or pics. I put all the important stuff on my PC regularly.
And yeah....use helium or whatever...backup. Move to PC. Then take 5 minutes to unlock and root. Then restore the backup. What's that....15 minutes total? ?
---------- Post added at 07:27 PM ---------- Previous post was at 07:26 PM ----------
Or....risk the brick and do crazy script and hackz stuff I guess.

KJ said:
Ah. Lol
Everyone is different I guess. I don't have much data I care about. Or pics. I put all the important stuff on my PC regularly.
And yeah....use helium or whatever...backup. Move to PC. Then take 5 minutes to unlock and root. Then restore the backup. What's that....15 minutes total? ?
Click to expand...
Click to collapse
Not a good idea to keep important things on your phone anyways, always good to put them on your computer or cloud storage.
And it takes way longer when they avoid fastboot and end up with a "softbrick" which they'll then try to fix with a toolkit, not wanting to learn lol. Then they end up on here making threads.. When it would've taken literally 5 minutes had they read stickies.
Sent from my Nexus 5

Thanks. No, I have not played with Google Nexus phones much. But I have with Samsung phones. The procedure I described above is what I did on Samsung phones. They need to be flashed with ODIN and require the image files. That is how I learned to work with the ext4 image files.
And, yes, I am aware of the custom recovery/flash SuperSU thing. But I would like to know how the system works. So I can make the changes I like. I do not care about the OTA very much. I can just repeat the whole procedure.
What I am not sure is how different Google Nexus phones are from Samsung phones. From the other replies, it seems Google Nexus phones are even easier to work with.
KJ said:
You started saying you don't have much experience with Google. Why are you making it so complicated?
Root is easy. Takes 5 minutes, risk free if done right. What you are doing could potentially go sour.
Unlock bootloader. Flash custom recovery. Install SuperSU. Done.
And to get rid of apps, use titanium backup. Tho freezing is better. They're not big files, and you can simply unfreeze if needed. Can't take an ota if they are gone. And if you uninstall something you shouldn't, you'll be flashing the firmware again.
Keep it simple.
Click to expand...
Click to collapse

[Solved]
A quick update to my experiment:
The procedure works. So, yes, it is very easy to work with Nexus phones. No need to create tar ball files after the image files are packed. I can simply flash the sparse image files using fastboot, easy and straightforward. No issue at all.
It looks like simply adding the su binary no longer works with Android 4.4. As I researched on other threads, it seems sugote is required as well. But like KJ has said, it is easy to root using SuperSU.
Thanks.

what if i just want to extract and repack the system.img? i just want to remove and replace some APKs...
i've been using windows 7, should i use ubuntu?

Gilang555 said:
what if i just want to extract and repack the system.img? i just want to remove and replace some APKs...
i've been using windows 7, should i use ubuntu?
Click to expand...
Click to collapse
Yes, ubuntu is so much easier than Windows. Get a virtual machine and off you go.
Install Android fsutils and you will get simg2img and make_ext4fs tools to get the job done. One tricky thing is the Android branch you need to use. Choose the right version and you will be good. You probably need to try a few times.

wxppro said:
Yes, ubuntu is so much easier than Windows. Get a virtual machine and off you go.
Install Android fsutils and you will get simg2img and make_ext4fs tools to get the job done. One tricky thing is the Android branch you need to use. Choose the right version and you will be good. You probably need to try a few times.
Click to expand...
Click to collapse
hey, i have ubuntu on my laptop and installed fsutils through synaptic package manager, but i don't know what to do...
can u guide me? just to unpack and repack the system.img

Gilang555 said:
hey, i have ubuntu on my laptop and installed fsutils through synaptic package manager, but i don't know what to do...
can u guide me? just to unpack and repack the system.img
Click to expand...
Click to collapse
I just use this
http://andwise.net/?p=403

rootSU said:
I just use this
http://andwise.net/?p=403
Click to expand...
Click to collapse
Hi, recently i wanted to unpack again but i forgot how to do it. And when i go to the site, it is gone.
Can you guide me please...
Sent from my ASUS_T00F using XDA Free mobile app

Can't root h810pr!!!

I flashed the h810pr onto my att g4 and it works amazingly. But, I've done the root method about 10 times, and when ever I enter the last line of code the # just shows up right away, and root doesn't install I've made sure to read everything carefully and no root. Am I doing something wrong? Any help would be appreciated thank you.

russianwaffle said:
I flashed the h810pr onto my att g4 and it works amazingly. But, I've done the root method about 10 times, and when ever I enter the last line of code the # just shows up right away, and root doesn't install I've made sure to read everything carefully and no root. Am I doing something wrong? Any help would be appreciated thank you.
Click to expand...
Click to collapse
I guess you have to install the driver again..in download mode...uninstall then install back..then try the code

Tried that and still no luck.

I've got that problem too. The way i fixed it was to reflash the H810pr brand new. Do not mess with any setting yet. Then enable USB debugging. Make sure you use MTP mode, be certain that the phone itself ask you if you want to install driver. Hit yes, then reinstall the LG driver on your pc. Put the phone in download mode and root. Make sure you run the "send command" line and "id" line as instructed.

Tried that, it still doesnt want to work properly.
Sent from my LG-H810 using XDA Free mobile app

russianwaffle said:
Tried that, it still doesnt want to work properly.
Click to expand...
Click to collapse
Make sure the img file is extracted properly from the rar file that you downloaded.
Also ensure the name of the file on the internal memory matches the name in the flash command.
Perhaps the rooted image didn't download correctly.
Could be a driver or com port issue, but you were able to flash the original image so that shouldn't be the problem.

Ya i was triple checking everything. It seems like a driver problem ill look into ot later.
Sent from my LG-H810 using XDA Free mobile app

russianwaffle said:
I flashed the h810pr onto my att g4 and it works amazingly. But, I've done the root method about 10 times, and when ever I enter the last line of code the # just shows up right away, and root doesn't install I've made sure to read everything carefully and no root. Am I doing something wrong? Any help would be appreciated thank you.
Click to expand...
Click to collapse
If you are still having this problem, make sure the file is on the internal SDcard at the top level (root directory) and not the external sdcard.

Ya I made sure of that too, I don't even own an external sd card. I've just been using on the stock unrooted h810pr, haven't had time to look into the problem. If I figure it out ill post how to fix it just in case someone else has this problem in the future. If anyone has any other suggestions let me know I'll try them this week end.

russianwaffle said:
Ya I made sure of that too, I don't even own an external sd card. I've just been using on the stock unrooted h810pr, haven't had time to look into the problem. If I figure it out ill post how to fix it just in case someone else has this problem in the future. If anyone has any other suggestions let me know I'll try them this week end.
Click to expand...
Click to collapse
Have tried both com?
com 4 or com 3

Be sure to let supersu update before you reboot the phone.

faizalotai said:
Have tried both com?
com 4 or com 3
Click to expand...
Click to collapse
For my phone is always showed up as com6, I've changed the devices com number then tried the new one and nothing.

phineous said:
Be sure to let supersu update before you reboot the phone.
Click to expand...
Click to collapse
That's the thing I never get to that point the phone just won't root. I have no super user nothing. And when I do the process and I send the code to device on the screen with the # nothing happens it's just shows # again with in a second.

russianwaffle said:
That's the thing I never get to that point the phone just won't root. I have no super user nothing. And when I do the process and I send the code to device on the screen with the # nothing happens it's just shows # again with in a second.
Click to expand...
Click to collapse
Did you make sure to rename the file to system.img?

Make sure the image file is on internal storage and you are using the correct image filename in the dd command.

small Request for someone with rooted ATT LG G4

Hello everyone. I need a small BIG favor...someone with a rooted ATT/puertorico LG G4 please run this command
using adb shell terminal
Code:
dd if=/dev/block/mmcblk0 bs=1 count=17408 of=/data/media/0/gpt_backup.img
And post the file here. Trying to make to make a file to unbrick completely dead phone.
Thank you

Sunderwear said:
Hello everyone. I need a small BIG favor...someone with a rooted ATT/puertorico LG G4 please run this command
using adb shell terminal
Code:
dd if=/dev/block/mmcblk0 bs=1 count=17408 of=/data/media/0/gpt_backup.img
And post the file here. Trying to make to make a file to unbrick completely dead phone.
Thank you
Click to expand...
Click to collapse
What partition is MMCBLK0?

mmcblk0 is the internal storage media, the partitions corrospond to the offsets, so mmcblk0p1 0p2 etc, since the phone is in download mode the system isnt mounted fully and you need to calculate the offset to capture the partition with dd.
just an fyi to the op, I was already working on doing this, once im done capturing everything and testing it there will be a guide up

diedemus said:
mmcblk0 is the internal storage media, the partitions corrospond to the offsets, so mmcblk0p1 0p2 etc, since the phone is in download mode the system isnt mounted fully and you need to calculate the offset to capture the partition with dd.
just an fyi to the op, I was already working on doing this, once im done capturing everything and testing it there will be a guide up
Click to expand...
Click to collapse
Thanks a lot for your efforts! Hopefully we have a guide to go back to AT&T stock in the event we mess our devices up!

diedemus said:
mmcblk0 is the internal storage media, the partitions corrospond to the offsets, so mmcblk0p1 0p2 etc, since the phone is in download mode the system isnt mounted fully and you need to calculate the offset to capture the partition with dd.
just an fyi to the op, I was already working on doing this, once im done capturing everything and testing it there will be a guide up
Click to expand...
Click to collapse
mu3g said:
Thanks a lot for your efforts! Hopefully we have a guide to go back to AT&T stock in the event we mess our devices up!
Click to expand...
Click to collapse
This might be a silly question but I would like someone to clarify... Why don't we get everyone to simply back up their system.img before/after rooting using the same method mentioned in the root thread and always keep on the internal storage that way if they soft brick they can just put the device in download move and restore to that? I know if you hard brick your device you have no choice but as long as it boots that should work or was I mislead? I think when you flash the PR firmware then you are committed because all your partitions change right? If I'm wrong I'd really like an explanation just in case I brick my device

Thats correct, once you go to PR the partition table changes. If you have an issue on ATT with a bootloop and have your factory system.img on the internal storage you just drop to download mode and push it with dd
I set up a donate button on the left and am waiting to hear back from mods on what my options are for it.

diedemus said:
Thats correct, once you go to PR the partition table changes. If you have an issue on ATT with a bootloop and have your factory system.img on the internal storage you just drop to download mode and push it with dd
I set up a donate button on the left and am waiting to hear back from mods on what my options are for it.
Click to expand...
Click to collapse
If this is the case, for a soft brick, can we just put the phone in download mode and flash the rooted 10g system image from the root thread using dd....would that work to get out of a soft brick?

mu3g said:
If this is the case, for a soft brick, can we just put the phone in download mode and flash the rooted 10g system image from the root thread using dd....would that work to get out of a soft brick?
Click to expand...
Click to collapse
yeah, I made a backup before I did anything for this. Should be the first line of defense and really should be one of the steps of rooting just so people know that's an option

Hey guys. Apparently I've done exactly what you talk about I regards to flashing the PR system.img to the internal SD card because after bootlooping, my internal SD card was completely full except for less than 1 GB. Is there a tutorial to fix this and flash the rooted system.img for the 810g?
Sent from my ASUS_Z00AD using XDA Premium HD app

Once you are on the pr rom you cant go back to at&t right now. Myself and a couple others are working on a method but I have been extremely busy the past week

Thank you for your hard work! I'll keep checking the thread. I bought a ZenFone 2 in the meantime to hold me over.
Sent from my ASUS_Z00AD using XDA Premium HD app

[Depreciated]Boost Stylo 5.1.1 ZV5 Custom Rom v1

I personally Tested this
Attention if you try this and end up with a brick or your device transforms and tries to destroy you; it's not my fault you did this not me. So just read all of this thread not just the O.P (and read the O.P more then once) to get out of a bind if you reply with "the thread is too long i wont read it please help" don't expect anything short of "there's a search bar use it"
Okay well now, you must be on ZV5 in order to use this system.img
since we of the Boost LG G Stylo don't have the privilege of TWRP because of a pesky locked bootloader and now real way around it....i have edited and tested this stock ZV5 System.img
the things it comes with is Busybox installed (you still need to download the app)
Viper4Android working without having to disable SELinux
rooted and debloated (for the most part)
edited build.prop
Make sure you have a Windows PC
Download the LG Drivers from here
Download this rooted-ZV5-system.img
Place downloaded img to your external SD via adapter or through your phone
Now place SD back into your phone
Reboot your device into download mode
Download this folder and unzip it to your desktop:
Run ports.bat from within the extracted folder, to find your correct port (use the one with: LGVZANDNETDIAG1)
In the LG_Root folder hold shift and right click and choose open command windows here
Type
Code:
Send_Command.exe \\.\COM3
(Make sure your COM port number is correct, it varies)
Type
Code:
dd if=/storage/external_SD/rooted-ZV5-system.img bs=8192 seek=42816 count=327680 of=/dev/block/mmcblk0
you will see a flashing _ line instead of the # let it do it's thing you will know it finished when the # shows back up
Type
Code:
LEAVE
and press enter and let your device reboot

Will this work on the Sprint model?

Ellli said:
Will this work on the Sprint model?
Click to expand...
Click to collapse
It's possible...

Also is there a way for me to make a system.img if I want to go back and recover it?

Ellli said:
Also is there a way for me to make a system.img if I want to go back and recover it?
Click to expand...
Click to collapse
Yes there is but I'm away from my computer at the moment i will give you the command to pull the system.img for sprint tomorrow at the earliest

Ok thanks

V2 change-log Xposed Framework, Deodexing doesn't want to work sadly
Haven't uploaded yet tho

Will this work with metro pcs?

darrick505 said:
Will this work with metro pcs?
Click to expand...
Click to collapse
in theory yes but i wouldn't chance it

Nice. Good Job man. This little phone is finally startin to hum along...thanks for ALL your work!!:good:

Hello Has anyone flashed this on the sprint version?
Thank you

Thank you
Working great so far, was finally able to get some system space cleaned up and truely uninstall bloatware. Now I'm just working on the right sd card format to get Link2SD working.

kwa1dan said:
Working great so far, was finally able to get some system space cleaned up and truely uninstall bloatware. Now I'm just working on the right sd card format to get Link2SD working.
Click to expand...
Click to collapse
use ext 4 and name it sd-ext

Thanks thats what I went with a few hours ago, worked just fine ive been linking the apps through Link2SD now.

Is there an actual features list? I see you said debloated and build.prop edits, I was just wondering what it was exactly that was removed and what edits you did? I just used your root method today on my boost stylo 5.1.1 and it went perfectly! I want to use this too, but don't want to mess anything up. DO I need to factory reset or anything first? Or do I just follow the instructions in the OP? Thanks for all your hard work dude.
EDIT: Did you ever upload V2? Should I just use your guide for adding xposed? There probably isn't much different than a stock img I am guessing?

Rharker85 said:
Is there an actual features list? I see you said debloated and build.prop edits, I was just wondering what it was exactly that was removed and what edits you did? I just used your root method today on my boost stylo 5.1.1 and it went perfectly! I want to use this too, but don't want to mess anything up. DO I need to factory reset or anything first? Or do I just follow the instructions in the OP? Thanks for all your hard work dude.
Click to expand...
Click to collapse
I'll add that in a bit

When I updated to this Rom it came with my mobile data not working. Is there a way I can fix it again? Any build.prop edits can make it work again? Please help me.

MonstaSaleens said:
When I updated to this Rom it came with my mobile data not working. Is there a way I can fix it again? Any build.prop edits can make it work again? Please help me.
Click to expand...
Click to collapse
really?....hmmmm.....when downloading did the download get interrupted at all?

6th_Hokage said:
really?....hmmmm.....when downloading did the download get interrupted at all?
Click to expand...
Click to collapse
No I don't believe so. If it did would it have flashed successfully? Are there any tricks to get it working again? It havnt been working for about a month now.

MonstaSaleens said:
No I don't believe so. If it did would it have flashed successfully? Are there any tricks to get it working again? It havnt been working for about a month now.
Click to expand...
Click to collapse
....possibly a factory reset if that doesn't work flash my completely stock system.img then manually root with my guide