Database Users

Rooting ideas and discussion

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.

Fire HD 8 recovery

So im working on trying to get twrp up on the HD 8 but i need a backup of someones elses recovery. Its located at /dev/block/mmcblk0p7

Update please if you have root, go to adb then type adb shell and then su. after that just run this command dd if=/dev/block/mmcblk0p7 of=/storage/sdcard1/recovery.img, if you want it to go somewhere else then just change the part that says storage/sdcard1(for example if you want it to go to the device storage then just remove the 1) the recovery image should then be on your sd card. please then attach or send the recovery image to me. Thank you

Hi, please find attached the recovery file!

coopmaster said:
Update please if you have root, go to adb then type adb shell and then su. after that just run this command dd if=/dev/block/mmcblk0p7 of=/storage/sdcard1/recovery.img, if you want it to go somewhere else then just change the part that says storage/sdcard1(for example if you want it to go to the device storage then just remove the 1) the recovery image should then be on your sd card. please then attach or send the recovery image to me. Thank you
Click to expand...
Click to collapse
Hi, please find attached the recovery file!

schr01 said:
Hi, please find attached the recovery file!
Click to expand...
Click to collapse
Thank you so much. I needed that so I can compare also because I changed mine and I should have backed it up first.

Any luck on compiling twrp?

madsc13n41s4 said:
Any luck on compiling twrp?
Click to expand...
Click to collapse
would not matter, there is no way to use it
Sent from my KFFOWI using XDA Labs

coopmaster said:
So im working on trying to get twrp up on the HD 8 but i need a backup of someones elses recovery. Its located at /dev/block/mmcblk0p7
Click to expand...
Click to collapse
How die you Figure Out where located?

thebrainkafka said:
How die you Figure Out where located?
Click to expand...
Click to collapse
i think i was following some link i found that explains where the recovery normally is. PM if you want to talk more about it.

How can we dump the img we need?

So I did the step to here.But do not know how to get system.img/boot.img/bootloader.img(most want).Any developers help?

jackzhu said:
So I did the step to here.But do not know how to get system.img/boot.img/bootloader.img(most want).Any developers help?
Click to expand...
Click to collapse
You could try this not sure if it work haven't tried yet use terminal emulator
Run this first and it will list your img you want
ls -al /dev/block/platform/soc/1da4000.usfhc/by-name
dd if=/dev/block/platform/soc/1da4000.ufshc/by-name (the img you want) of=/sdcard/ (your img)
You can use this command to dump any partition updated command

tattedup said:
You could try this not sure if it work haven't tried yet use terminal emulator
Run this first and it will list your img you want
ls -al /dev/block/platform/soc/1da4000.usfhc/by-name
dd if=/dev/block/platform/soc/1da4000.ufshc/by-name (the img you want) of=/sdcard/ (your img)
You can use this command to dump any partition updated command
Click to expand...
Click to collapse
You mean xxx_a.img is same as xxx_b.img?

jackzhu said:
You mean xxx_a.img is same as xxx_b.img?
Click to expand...
Click to collapse
If you flash the stock restore from invisiblek yes the a and b img should be the same, I think not positive not much knowledge on a and b partitions. But what I got from invisiblek's post is that is correct.

tattedup said:
If you flash the stock restore from invisiblek yes the a and b img should be the same, I think not positive not much knowledge on a and b partitions. But what I got from invisiblek's post is that is correct.
Click to expand...
Click to collapse
Thank you, I will dump it for try .

jackzhu said:
Thank you, I will dump it for try .
Click to expand...
Click to collapse
I'm sure I get the boot.img. do you know which is/are bootloader.img?

[needed]persist backup of moto g5 plus which is not bricked yet

Hey guys as you know that we are able to get back volte successfully in Moto g5 plus by restoring PERSIST BACKUP.
So I think MAYBE persist partition got corrupted during flashing back stock.
But that backup is from MOTO G4 PLUS ,and some user facing a problem that whenever they reboot volte and imei again gone,and Everytime they have to restore efs (maybe because of that persist partition)so I am requesting you ,can someone please pull out persist backup of STOCK MOTO G5 PLUS WITH WORKING VOLTE (OR G5 PLUS WHICH IS NOT BRICKED YET).
I AM ATTACHING A TWRP FOR TAKING BACKUP WHICH IS MADE BY DEVELOPER.
SO YOU HAVE TO JUST GO IN TO BACKUP AND TAKE BACKUP OF PERSIST PARTITION
You can download twrp from below link.
https://potterroms.ddns.net/TWRP/twrp-3.2.1-1-potter_persist.img
I am not responsible for any brick/damage caused during you taking backu

Alright, so I got a Persist backup using the partition backup & restore app. I don't use VoLTE, but my IMEI hasn't become zero. I'm on Oreo. It's saved as a .img file. If this is helpful I'll upload the file. @akshu2697

thedr34m13 said:
Alright, so I got a Persist backup using the partition backup & restore app. I don't use VoLTE, but my IMEI hasn't become zero. I'm on Oreo. It's saved as a .img file. If this is helpful I'll upload the file. @akshu2697
Click to expand...
Click to collapse
I would definitely love to give it a go. I've had to restore my EFS every reboot since I tried installing Pixel Experience. I'd love to not have to remember anymore!
telegram @bcraw

thedr34m13 said:
Alright, so I got a Persist backup using the partition backup & restore app. I don't use VoLTE, but my IMEI hasn't become zero. I'm on Oreo. It's saved as a .img file. If this is helpful I'll upload the file. @akshu2697
Click to expand...
Click to collapse
Yes,it will be helpful,can you please upload that file.?

akshu2697 said:
Yes,it will be helpful,can you please upload that file.?
Click to expand...
Click to collapse
There you go.

thedr34m13 said:
There you go.
Click to expand...
Click to collapse
i will try ,
thank you so much brother

akshu2697 said:
i will try ,
thank you so much brother
Click to expand...
Click to collapse
No problem. Happy to help. If there's a way to get a better backup, tell me and I'll try.

thedr34m13 said:
No problem. Happy to help. If there's a way to get a better backup, tell me and I'll try.
Click to expand...
Click to collapse
sorry brother ,
i tried your backup,but this backup isn't working,
we need twrp persist backup as i have posted on the thread of volte.

akshu2697 said:
sorry brother ,
i tried your backup,but this backup isn't working,
we need twrp persist backup as i have posted on the thread of volte.
Click to expand...
Click to collapse
Not sure how to backup persist in twrp. Couldn't find instructions anywhere. If you find instructions, tell me and I'll upload the backup.

thedr34m13 said:
Not sure how to backup persist in twrp. Couldn't find instructions anywhere. If you find instructions, tell me and I'll upload the backup.
Click to expand...
Click to collapse
sure,i'll do

DELETED

With a lot of research, I was able to dump the persist partition using adb. My dump will do no good, as I have only been able to get persist back by OP's method. We need someone to dump who has not flashed an oreo rom. Ok, that being said, here is how.
Make sure your phone is rooted.
Make sure usb debugging is enabled.
Boot phone into recovery.
Open adb with phone connected to pc.
Code:
adb devices
You should see your device listed.
Code:
adb shell
You should get ~# and something like a backward arrow [6N. That was mine yours may differ. If you have ~$ instead of ~# you are not rooted properly. If you used magisk you may have to add the sudo module.
Code:
ls -al /dev/block/platform/soc/7824900.sdhci/by-name
This will give you a list of all partitions. Look through them and find one described as persist. Mine was this:
Code:
lrwxrwxrwx 1 root root 21 Jan 1970 persist -> /dev/block/mmcblk0p30
We are interested in the address /dev/block/mmcblk0p30.
We need to type in
Code:
dd if=/yourMountingPoint of=/yourDestination/partitionType
where /yourMounting point is the persist address, if like mine /dev/block/mmcblk0p30. /your destination will be where you want to save it, and partition type should be persist.img.
My command was this
Code:
dd if=/dev/block/mmcblk0p30 of=/external_sd/persist.img
This will give us a proper persist .img file.

Here it is.
I clean flash stock rom (potter_NPNS25.137-93-4) before getting the persist file, was on crDroid 7.1 before. I don't know if volte is working because we don't have it on my country, but I never flashed Oreo before and never lost imei or 4g/lte, so it should be fine.
Hope it helps us and use at your own risk.
https://drive.google.com/drive/folders/1bqdxheka3jKG76AXdEExIdhG81D3agLM

[email protected] said:
With a lot of research, I was able to dump the persist partition using adb. My dump will do no good, as I have only been able to get persist back by OP's method. We need someone to dump who has not flashed an oreo rom. Ok, that being said, here is how.
Make sure your phone is rooted.
Make sure usb debugging is enabled.
Boot phone into recovery.
Open adb with phone connected to pc.
Code:
adb devices
You should see your device listed.
Code:
adb shell
You should get ~# and something like a backward arrow [6N. That was mine yours may differ. If you have ~$ instead of ~# you are not rooted properly. If you used magisk you may have to add the sudo module.
Code:
ls -al /dev/block/platform/soc/7824900.sdhci/by-name
This will give you a list of all partitions. Look through them and find one described as persist. Mine was this:
Code:
lrwxrwxrwx 1 root root 21 Jan 1970 persist -> /dev/block/mmcblk0p30
We are interested in the address /dev/block/mmcblk0p30.
We need to type in
Code:
dd if=/yourMountingPoint of=/yourDestination/partitionType
where /yourMounting point is the persist address, if like mine /dev/block/mmcblk0p30. /your destination will be where you want to save it, and partition type should be persist.img.
My command was this
Code:
dd if=/dev/block/mmcblk0p30 of=/external_sd/persist.img
This will give us a proper persist .img file.
Click to expand...
Click to collapse
How to restore this file brother.?

N1vBruno said:
Here it is.
I clean flash stock rom (potter_NPNS25.137-93-4) before getting the persist file, was on crDroid 7.1 before. I don't know if volte is working because we don't have it on my country, but I never flashed Oreo before and never lost imei or 4g/lte, so it shoud be fine.
Hope it helps us and use at your own risk.
https://drive.google.com/drive/folders/1bqdxheka3jKG76AXdEExIdhG81D3agLM
Click to expand...
Click to collapse
Thank you sooo much brother.
Thank you for your support.

akshu2697 said:
How to restore this file brother.?
Click to expand...
Click to collapse
Aren't you the OP of this? I thought you needed a way to dump the original partitions, and I provided the method with step by step to do so. I've never coded for android systems, but I'm very familiar with close cousin linux, so I suppose I could investigate and learn. However I would think whomever developed the G4 plus method could use the above dump for our phone. I guess I assumed it was you who discovered this method. I'll dig into it further when I get some time, but getting the clean persist dump was what was asked to do.

I was able to write the above persist.img file by:
1. transfer persist.img to my external_sd
2. booting into twrp
3. opening terminal
4. entering
Code:
dd if=/external_sd/persist.img of=/dev/block/mmcblk0p30
However, this placed my EMEI to 0, and I had to restore my saved efs with moto g4 + persist to get signal back. But remember, I had problem with efs every time I reboot, so my case may not be typical of those of you whose moto g4+ persist was working fine for. I would be curious if N1vBruno's persist was at the same address as mine, namely
Code:
/dev/block/mmcblk0p30

Guys who have restored their VoLTE, does your IMEI match the one that came with your phone or has it changed to something else?
I'm just being curious as I thought using someone else's persist backup would restore his IMEI to your phone, or was it efs?
Please correct me if I'm wrong.

psychopac said:
Guys who have restored their VoLTE, does your IMEI match the one that came with your phone or has it changed to something else?
I'm just being curious as I thought using someone else's persist backup would restore his IMEI to your phone, or was it efs?
Please correct me if I'm wrong.
Click to expand...
Click to collapse
It is efs.

[email protected] said:
I would be curious if N1vBruno's persist was at the same address as mine, namely
Code:
/dev/block/mmcblk0p30
Click to expand...
Click to collapse
Yes,
Code:
persist -> /dev/block/mmcblk0p30
psychopac said:
I'm just being curious as I thought using someone else's persist backup would restore his IMEI to your phone, or was it efs?
Click to expand...
Click to collapse
I hope not lol

i need persist.img partition. my 6t all sensor broken.

I accidentally flashed persist partition on another phone.
As a result, all sensors are not working now.
I haven't backed up that partition.???
Therefore i would like to ask someone to backup persist partition and share the image file with me.

parklrain said:
I accidentally flashed persist partition on another phone.
As a result, all sensors are not working now.
I haven't backed up that partition.
Therefore i would like to ask someone to backup persist partition and share the image file with me.
Click to expand...
Click to collapse
How can I do a backup for you?

see attach, unzip and flash using dd command

foobar66 said:
see attach, unzip and flash using dd command
Click to expand...
Click to collapse
Thanks!
But I don't know how to use the dd command.
Can I use fastboot command to flash?

abenssss said:
How can I do a backup for you?
Click to expand...
Click to collapse
I don't know exactly how, but you can use dd command to back up.
I don't know the exact file path.

foobar66 said:
see attach, unzip and flash using dd command
Click to expand...
Click to collapse
Thank you very much!
The img.persist file was renamed to Persist.img, and the bootloader flash using the fastboot command, and the sensor returned to normal.
My cell phone is alive.
Thank you!!

parklrain said:
Thank you very much!
The img.persist file was renamed to Persist.img, and the bootloader flash using the fastboot command, and the sensor returned to normal.
My cell phone is alive.
Thank you!!
Click to expand...
Click to collapse
i have the same problem. Which code do you type in the shell?

foobar66 said:
see attach, unzip and flash using dd command
Click to expand...
Click to collapse
for what type of phone?