Database Info

NANDROID RESTORE WITHOUT FASTBOOT?? - does it really work?

ok so im confused. I was reading the "how to flash cupcake" thread and came across this post by ridli. i tried following the instructions below but they failed, it seems like it works for him. if this truly works then there is no need for fastboot to reflash a nandroid back up. please help. thnx. BTW dudes .8 G build is awesome. (posted from my G1-modded w/root and gloss suite theme)
I tried the below on my G1 using recovery mode from JF-RC33 and i get:
error opening /sdcard/bu/system.img: no such file or directory.
I have checked the sdcard and its there, please help.
ridli said:
You can do the same without linux or any other SO.
1) Download cupcake
2) copy IMG files to a DIR in your SDCARD
3) reboot the phone in recovery mode
4) press ALT+X for go to console
5) #mount -a (for mount all partitions, without this you dont have flash_image becouse it is in /system/bin/)
6) use flash_image for flash the partitions
Code:
#flash_image system /sdcard/<dir>/system.img
#flash_image boot /sdcard/<dir>/boot.img
#flash_image userdata /sdcard/<dir>/data.img
7) #reboot
Optional: Do a backup of the phone with nandroid from the recovery mode, this do a img of system, data and boot partitions of your phone and copy to your sdcard. If you have any problem you can reflash your phone with you img.
Click to expand...
Click to collapse

It didn't work for me either, but it said I could not remount system as r/w because it was busy.
Anyway, I find instructions on how to do it via PC a lot easier. And if your phone would not boot, and you are stuck without backup, you can always pull it with adb.

Karolis:
System shouldn't be busy in recovery mode... also, it shouldn't be mounted if you're trying to write a fs image
And... no, if your phone can't boot, it can't boot. That includes starting adbd.
If you can enter recovery/spl, it's booting just fine.
flak0:
Have you checked the sdcard from the shell in android, or from your computer?
If it's the latter, you should make sure you can access the file from android.
I would recommend that you copy the flash_image binary out of /system (and /data), because you're rewriting that partition

Okay, don't use the forums when on a bad connection... my browser thought it lost connection, and decided to refresh, and send my post again... *Looks for a delete button*

this does not work
just so everyone is clear
DOES NOT WORK!
Note To Self, do not follow tutorials from junior members

arteshiftedscreen said:
this does not work
just so everyone is clear
DOES NOT WORK!
Note To Self, do not follow tutorials from junior members
Click to expand...
Click to collapse
Ummmm actually this does work if you do itcorrectly. Note to self no bashing people that are just trying to help.

so how is it done?
korndub said:
Ummmm actually this does work if you do itcorrectly. Note to self no bashing people that are just trying to help.
Click to expand...
Click to collapse
And could a Gscript or similar be written to do something like this? I'd be psyched to have the option to restore my phone on the fly. And of course, if you could do that, what would stop you from having a Nandroid restore point saved for a number of different builds? I would love that.

Out of curiosity, and I've never tried this method myself, are you just entering the following exactly?
#flash_image system /sdcard/<dir>/system.img
#flash_image boot /sdcard/<dir>/boot.img
#flash_image userdata /sdcard/<dir>/data.img
Click to expand...
Click to collapse
Or are you changing <dir> to the directory of your nandroid backup? Because if you aren't it certainly won't work.

ei8htohms said:
And could a Gscript or similar be written to do something like this? I'd be psyched to have the option to restore my phone on the fly. And of course, if you could do that, what would stop you from having a Nandroid restore point saved for a number of different builds? I would love that.
Click to expand...
Click to collapse
But it would be very unsafe to flash a fs image when the partition is actually mounted and your gscript is probably in it.
the only way is to do it in recovery mode.
one little problem though: i copied flash_image to /cache and chmod, but the shell kept telling me no such file. why is that?

billc.cn said:
But it would be very unsafe to flash a fs image when the partition is actually mounted and your gscript is probably in it.
the only way is to do it in recovery mode.
one little problem though: i copied flash_image to /cache and chmod, but the shell kept telling me no such file. why is that?
Click to expand...
Click to collapse
flash_image is a binary, should not be moved. why did you move it to cache? of course it wont work...

Unfortunately, flash_image does not support writing yaffs2 images. Look in the code, there's no support for writing the OOB data to the NAND. If it was possible I would've integrated backup AND restore in nandroid 2.0, and JesusFrekes recovery image would then also have a restore option. But alas, it's not to be.
Perhaps in a future release I can find a C coder who can add the code to the flash_image source, so that this becomes possible. But I'm not even sure if that can be done (because you need kernel driver support as well).

infernix said:
Unfortunately, flash_image does not support writing yaffs2 images. Look in the code, there's no support for writing the OOB data to the NAND. If it was possible I would've integrated backup AND restore in nandroid 2.0, and JesusFrekes recovery image would then also have a restore option. But alas, it's not to be.
Perhaps in a future release I can find a C coder who can add the code to the flash_image source, so that this becomes possible. But I'm not even sure if that can be done (because you need kernel driver support as well).
Click to expand...
Click to collapse
Can't we just use nandwrite from mtd-utils to do this? I haven't tried it yet (I'll build it for ARM when I get home from work), but it appears to be the right tool for the job. I'm really interested in getting a menu-driven restore in my recovery image.

cyanogen said:
Can't we just use nandwrite from mtd-utils to do this? I haven't tried it yet (I'll build it for ARM when I get home from work), but it appears to be the right tool for the job. I'm really interested in getting a menu-driven restore in my recovery image.
Click to expand...
Click to collapse
Oh that would be sooooooooo sweet!

[Guide] How to gain root on 2.2 for Mac

*******UPDATED 8/31/10 *******
This rooting method was adapted from regaw_leinad's method and toastcfh's method. By following these steps you will successfully downgrade your phone back to android 2.1 in order to gain root.
I don't trust unrevoked as I have had problems with it in the past.

I am not responsible for any damages to your phone.
special thanks to:
regaw_leinad
Sebastian Krahmer
Toastcfh
amon_ra
FILES YOU WILL NEED:
copy and paste into browser
Code:
sdx-downloads.com/sdx/evo/troot/eng-PC36IMG.zip
evo4g.me/downloads//count.php?target=evo-root.zip
files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=recovery-RA-evo-v1.8.0.img
developer.android.com/sdk/index.html
You will need the Android SDK in order to communicate between your computer and your phone. Download it (last link above) and follow the setup instructions that it comes with.
Unzip the contents of the evo-root.zip and put all the files from it into the tools folder located in the android sdk folder.
Rename the eng-PC36IMG.zip to PC36IMG.zip and then put it the tools folder located in the android sdk folder. DO NOT UNZIP IT!

******* PC36IMG.zip md5sum~ fe8aba99893c766b8c4fd0a2734e4738 *******
Move the recovery-RA-evo-v1.8.0.img into the android sdk folder as well.
Make sure usb debugging is enabled on your device. To do so go to Settings > Applications > Development > and make sure the check box is checked.
Plug your phone into the computer. Select "Charge Only" from the notifications bar.
Open up terminal and navigate your way into the android sdk folder.
Code:
cd /
cd asdk
Push all the files onto your phone.
Code:
tools/adb push /asdk/tools/flash_image /sdcard/
tools/adb push /asdk/tools/rageagainstthecage-arm5.bin /data/local/tmp/
tools/adb push /asdk/tools/mtd-eng.img /sdcard/
tools/adb push /asdk/tools/PC36IMG.zip /sdcard/
tools/adb push /asdk/tools/recovery-RA-evo-v1.8.0.img /sdcard/
Note that the PC36IMG.zip will take longer than the other files to transfer to the sdcard because it is a large file.

Now we will make rageagainstthecage.bin executable.
Code:
tools/adb shell
chmod 0755 /data/local/tmp/rageagainstthecage-arm5.bin
You should see this (below) after it has made the change.
Code:
$
Now to use the rooted shell.
Code:
cd /data/local/tmp
./rageagainstthecage-arm5.bin
You will now see some text on your terminal screen describing the exploit. 

Wait for the adb shell to finish the process. At this point it may or may not terminate the current shell session in terminal. If it does then it should look like this:
Code:
users-iMac:asdk user$
If it doesn't it will return to
Code:
$
in that case you need to exit the current session. To do so type
Code:
exit

Now we need initiate a new shell which should now have root permissions.
Enter the following:
Code:
tools/adb shell
and you will see you now have a
Code:
#
instead of
Code:
$
Now we need to flash the mdt-eng.img in order for it to let us install a custom recovery
Code:
adb shell
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image misc /sdcard/mtd-eng.img
That will flash your misc partition with Toast's mtd-eng.img


This should return you to
Code:
#
Now boot into hBoot
Code:
reboot bootloader
This will reboot your phone into hBoot. It will scan for the PC36IMG.img. When it asks yes or no, select yes.
It should then reflash your phone into the engineering build.
When it asks to reboot select yes.
You will need to flash custom recovery in order to be able to flash other custom roms or modifications. I use Amon_RA's recovery because it works great and has NEVER caused me any problems.
Now, open up terminal and get back into the android sdk folder
Code:
cd /
cd asdk
Since we have already pushed the recovery onto the sdcard we only need to flash the recovery onto the phone so that we can use it
Code:
adb shell
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image recovery /sdcard/recovery-RA-evo-v1.8.0.img
Now lets rename that PC36IMG.zip file again
Code:
mv /sdcard/PC36IMG.zip /sdcard/eng-PC36IMG.zip
that way your phone doesn't try to flash it when you go into recovery each time
And last but not least we need to boot into it to flash a custom rom
Code:
reboot recovery
Your phone should then reboot into Amon_RA's recovery and you may now head over to the dev forum to find your new favorite custom rom.

very nice! can anyone confirm this? my buddy wants me to root his 2.2 and i would like to try this.

To make life easier for some people add this to your post mate, and apply it yourself if you would like.
Here is how to add your sdk/tools directory to your .bash_profile file so you won't have to navigate to the folder each time.
Download this so you'll be able to see your hidden files http://www.mediafire.com/?diimft1ninn Run it, check "Show Hidden Files" then click Restart finder. Now, navigate to your home folder (/Users/UserName/) and see if there's a .bash_profile already there. If not, create with textedit.
Now add this to the file: export PATH=${PATH}:/Path/Of/Your/Sdk/Tools/Folder
Mine is /Users/bmxrider4444/Documents/Android/SDK/tools
Now do not save it as rich text. If yours is in rich text, click on "Format" in the menu bar, and click "make plain text". Now save it as .bash_profile and uncheck "if no extension is provided, use .txt".
Now you can go back to Ghost and uncheck "Show all hidden files" and restart finder again (special thanks to ajones7279 for these steps)
Enjoy!
Just as clarification as to what this does, it enables you to run adb commands and other commands without having to navigate to the /android/tools/ folder every time you want to run adb or whatever.

does this work?

seekis said:
At this point we need to push the recovery onto the sdcard
Code:
tools/adb push "location of recovery-RA-evo-v1.8.0.img" /sdcard/
Click to expand...
Click to collapse
This is great! Thanks for the guide - I am planning on rooting my Wife's EVO but have been waiting for an easier method than the other one posted. Question on the above where we write "location of recovery-ra-evo-v1.8.0.img". Is that the exact code, or should we be adding a directory or folder location into this line? I rooted my 2.1 EVO on my Mac a couple months ago and don't remember this step. Once again - very much appreciate the help.
One last question - would it make more sense to have a custom ROM already on your SD Card prior to rooting, so that you can flash it right after you flash AMON-RA for the first time? Probably doesn't matter but thought i'd ask.

^^ same question as above, plus one other n00b question - does this method unlock NAND?
[edit] I was not insinuating that randymac88 is a n00b; I, however, am

seekis said:
I don't trust unrevoked as I have had problems with it in the past.

I am not responsible for any damages to your phone.
Click to expand...
Click to collapse
Don't trust us with the unrevoked 3.x/unrevoked forever application combo that's worked for thousands of users without sideeffects on regaw's post?
You should note to everyone that your method will screw up their PRI, reverting it back to 1.34. By using unrevoked and unrevoked forever, you can keep 1.40.

randymac88 said:
This is great! Thanks for the guide - I am planning on rooting my Wife's EVO but have been waiting for an easier method than the other one posted. Question on the above where we write "location of recovery-ra-evo-v1.8.0.img". Is that the exact code, or should we be adding a directory or folder location into this line? I rooted my 2.1 EVO on my Mac a couple months ago and don't remember this step. Once again - very much appreciate the help.
One last question - would it make more sense to have a custom ROM already on your SD Card prior to rooting, so that you can flash it right after you flash AMON-RA for the first time? Probably doesn't matter but thought i'd ask.
Click to expand...
Click to collapse
Thats not the exact code no. I just put that as a place holder you are suppose to put in the location of where you have the recovery.img. For example, the exact command for me would be:
Code:
/Users/seekis/Downloads/recovery-ra-evo-v1.8.0.img
Don't trust us with the unrevoked 3.x/unrevoked forever application combo that's worked for thousands of users without sideeffects on regaw's post?
You should note to everyone that your method will screw up their PRI, reverting it back to 1.34. By using unrevoked and unrevoked forever, you can keep 1.40.
Click to expand...
Click to collapse
As far as using unrevoked, I stated that I, ME, MYSELF, has had issues with it. not that anybody else has. By all means go and use it if you would like. I will not. It is true that you will loose PRI 1.40, but seeing as how even after installing the OTA from HTC my phone still didn't update it to 1.40, I don't see the issue.

rsage said:
^^ same question as above, plus one other n00b question - does this method unlock NAND?
[edit] I was not insinuating that randymac88 is a n00b; I, however, am
Click to expand...
Click to collapse
i believe it does unlock nand seeing as how i adapted it from toasts method

Hey Seekis - question, I'm stuck here. I keep getting "permission denied", or "operation not permitted" when trying to make the exploit executable at this step:
chmod 0755 /data/local/tmp/rageagainstthecage-arm5.bin
Am I missing something? I've tried a million times and can't seem to get past this. I've successfully pushed all the files onto the sdcard.
I've also have had some trouble finding the exact root path to these files. I've been able to navigate, but I would think a lot of users would have some trouble.
Regardless, many thanks for getting this posted...
EDIT: I pushed the rageagainstthecage file to the sdcard by mistake. Will try again tomorrow.

ok i got rid of that step by moving the file into the android sdk and pushing it with all the other files

Okay now I appear to be in big trouble as I've just messed up my wife's phone, and its probably going to be unusable for a while until I get this figured out (assuming I do!).
I got through most of the process. I flashed the PC36IMG.zip file; however when it asked to reboot, it just dumped me back into the bootloader. Whenever I say reboot, it just takes me back to the bootloader. Pull the battery, same thing - bootloader. Yikes.
I don't know how to get to the next step because I can't get into a booted rom in order to flash the amon-ra recovery. Am I totally effed? Can anyone help me here?
EDIT: Okay reflashed the PC36IMG.zip file, and it rebooted into the stock ROM. Onward! Phew!!

The wife's EVO is now fully rooted running Baked Snack 1.5 w/Netarchy's kernel. Touch and go there for a minute, but it all worked out. No 1.40 PRI, but I don't really care about that right now.
Woot! Thanks Seekis!!

do u have to push the pc36img with adb every time or will drag and drop work or copy and paste work?

FoxHound630 said:
do u have to push the pc36img with adb every time or will drag and drop work or copy and paste work?
Click to expand...
Click to collapse
You can mount the card on your system and copy paste it over as well, yes.

randymac88 said:
Okay now I appear to be in big trouble as I've just messed up my wife's phone, and its probably going to be unusable for a while until I get this figured out (assuming I do!).
I got through most of the process. I flashed the PC36IMG.zip file; however when it asked to reboot, it just dumped me back into the bootloader. Whenever I say reboot, it just takes me back to the bootloader. Pull the battery, same thing - bootloader. Yikes.
I don't know how to get to the next step because I can't get into a booted rom in order to flash the amon-ra recovery. Am I totally effed? Can anyone help me here?
EDIT: Okay reflashed the PC36IMG.zip file, and it rebooted into the stock ROM. Onward! Phew!!
Click to expand...
Click to collapse
Had the same issue. When i first booked into the bootloader i had to select recovery then flash PC36IMG.zip. Then boot loop. Then i went back into the bootloader and it automagically read in the PC36IMG.zip and flashed it, then i got stock 2.1 root. Just a few minutes of "oh crap"

I'm stuck. I got as far as flashing PC36IMG.zip, which was successful, as my phone now runs 2.1, but it doesn't appear I'm rooted. When I go back into the adb shell, I'm getting the $ prompt, and running
Code:
cat /sdcard/flash_image > /data/flash_image
gives me a permission denied error. Help!

atom_jack said:
I'm stuck. I got as far as flashing PC36IMG.zip, which was successful, as my phone now runs 2.1, but it doesn't appear I'm rooted. When I go back into the adb shell, I'm getting the $ prompt, and running
Code:
cat /sdcard/flash_image > /data/flash_image
gives me a permission denied error. Help!
Click to expand...
Click to collapse
i dont know what to tell you other than try again. this happened to me the first time through as well. i dont know why. i just started from the top and it worked the second time through.

seekis said:
i dont know what to tell you other than try again.
Click to expand...
Click to collapse
So after you flash PC36IMG.zip you should automatically get a root (#) prompt when going into the shell? ie, I'll have rooted 2.1 yes?
seekis said:
this happened to me the first time through as well. i dont know why. i just started from the top and it worked the second time through.
Click to expand...
Click to collapse
Aha. Ok, I will keep trying til it gives me a root shell, I guess. I also tried unrevoked3 but that didn't seem to work.

Success!! So, I stupidly assumed that all PC36IMG.zip's were the same, and was using the one from the original 2.2 PC thread. Once I got the correct one, voila!
You might want to post the md5 of the one you are using, so there's no confusion for others. Also, you missed a tiny step when you first start up hboot - you have to select fastboot for it to start scanning for PC36IMG.zip.
Thanks!

[MOD] KENDON ROCKS boot.img with adb remount and rooted adb shell support

All credit goes the Kendon from villainrom he rocks my socks
If you want to be able to use adb with root permissions you need one of these boot.imgs. you use this at your own risk, no matter what! i assume you have adb working, if not, there are guides (also here on the site, might look for one later).
this boot.img is from RUU_Ace_HTC_WWE_1.32.405.6, it might break wifi for other roms. let me know if you have problems, i will try to find the correct boot.img for you then.
Code:
abd490503190fff2c0c7d17ec42a14c1 dhd/boot.img
- get fastboot.exe, put it on your pc in the same directory as adb.exe
- download the proper boot.img for your device, put it in c:\.
- connect your phone via usb, make sure usb debugging is enabled, open a command prompt and type:
Code:
adb reboot bootloader
fastboot boot c:\boot.img
if all goes well and the device boots up you know it works. now do:
Code:
adb reboot bootloader
fastboot flash boot c:\boot.img
this will make it permanent.
you probably need the s-off bootloader for this, as usually the s-on doesn't allow fastbooting or flashing img files.
To get boot.img go here
http://www.villainrom.co.uk/forum/s...with-adb-remount-and-rooted-adb-shell-support
find the same here for the T-Mobile G2/Desire Z: http://www.villainrom.co.uk/forum/showthread.php?3366

Permaroot the gift that keeps giving, this works fine on my DHD just clockwork recovery then CM here we come

testing something now tee hee shh

mikecoffee said:
All credit goes the Kendon from villainrom he rocks my socks
If you want to be able to use adb with root permissions you need one of these boot.imgs.
Click to expand...
Click to collapse
once you get s-off and the write protection has been removed do you really get declined root with adb?
i mean i had root with adb with temp root :S
did you try adb remount and see if that gave you write access to the partition?
slighlty confused as to what this is.
agree with you tho about Kendon, he sure does rock! had a hero and am happy i donated to VR cos they gave that device some life lmfao

Thanks a lot mikecoffee! Working fine here, no ... undesirable results

Don't really need this since I can find myself around the linux command line well enough to mount /system as read-write but thanks all the same. I'm sure some people will find it well handy.

dr.m0x said:
Don't really need this since I can find myself around the linux command line well enough to mount /system as read-write but thanks all the same. I'm sure some people will find it well handy.
Click to expand...
Click to collapse
I also, like to think, i can find myself around with CLI but was having problems with getting system mounted r/w, to be fair it was probably something i had neglected to do late at night, and personally found this boot image helped

has anyone got a mirror for this boot.img? the site seems to be down for me

billington.mark said:
has anyone got a mirror for this boot.img? the site seems to be down for me
Click to expand...
Click to collapse
Hi
the site is up, sorry if its been down not sure why!

dr.m0x said:
Don't really need this since I can find myself around the linux command line well enough to mount /system as read-write but thanks all the same. I'm sure some people will find it well handy.
Click to expand...
Click to collapse
So this is not needed to write to /system? I've done visionary r12 permroot + engineering hboot s-off but still can't write to /system.
mount -o remount,rw /dev/block/mmcblk0p25 /system works (mount shows /system as rw) but I still can't move files to it via terminal emulator nor adb.

[GUIDE] Backup persist partition (save wifi mac, bluetooth mac, sensors data)

Hello guys, this guide is for creating backup of persist partion which is holding important data about sensors, wifi + bluetooth data, imei and other stuff.
Before installing any other custom room, this is best thing to do, lot of custom roms rewrites persist partition with different data than your mobile devices has, you will have problem with calling(missing imei), problems with Wifi and other stuff, i think you get it...
REQUIRED TOOLS:
Code:
[URL="https://drive.google.com/open?id=1LW1CM6gLT9wRyy950rC6GmWAzEbcyfzE"]PersistBackupTool[/URL]
Follow this steps:
Code:
1. Root your device, this is pretty much easy guide: [URL="https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654"]LINK[/URL]
2. After rooting your device, enable Developer options (Go to settings >> System >> About phone >> tap Build number 7 times)
3. Enable usb debugging, go to Settings >> System >> Developer options >> and enable USB debugging
4. Run PersistBackup.bat and wait
5. Your persist partition will be saved in Backup folder.
ENJOY!!!

When I lauch the PersistBackup.exe it tells me "This program was made with an Unlicensed compiler. Please buy the PRO version to distribute your exe. " And then it closes when you press any key.
I guess you missed this in your last compile

VolpeXDA said:
When I lauch the PersistBackup.exe it tells me "This program was made with an Unlicensed compiler. Please buy the PRO version to distribute your exe. " And then it closes when you press any key.
I guess you missed this in your last compile
Click to expand...
Click to collapse
Damn, thanks for the info, will fix it soon!

Does it do the same as the following adb commands?
Code:
adb shell "su -c dd if=/dev/block/mmcblk0p27 of=/sdcard/Download/persistbackup.img"
adb pull /sdcard/Download/persistbackup.img

oreo27 said:
Does it do the same as the following adb commands?
Code:
adb shell "su -c dd if=/dev/block/mmcblk0p27 of=/sdcard/Download/persistbackup.img"
adb pull /sdcard/Download/persistbackup.img
Click to expand...
Click to collapse
Yes it is the same

VolpeXDA said:
When I lauch the PersistBackup.exe it tells me "This program was made with an Unlicensed compiler. Please buy the PRO version to distribute your exe. " And then it closes when you press any key.
I guess you missed this in your last compile
Click to expand...
Click to collapse
Fixed, thanks again for the info!

pulja9 said:
Yes it is the same
Click to expand...
Click to collapse
Cool. I think you'll want to update the OP though. As far as I know, the IMEI data is stored on the modemst1 and modemst2 partitions.

(EDITED, check the end)
First, I've tried with the "adb" commands, but I get "Permission Denied".
So, I decided to try the tool, which still gives me a "Permission Denied", but still prints a sucess message at the end "Persist partition has been successfully backed up! Partition has been saved in Backup folder!"
Not sure if it's my mistake. I'm rooted + USB_debugging.
EDIT:
OK, I've read that for adb "su" to work, you need to have device unlocked, with screen on, and grant permission.
Turns out Magisk was rejecting root permissions to Perfdump automatically.
Should work now. Nevertheless, perhaps you could check why it prints that backup worked when permission was denied. Someone could be fooled there =D
Finally: Thanks for the app

ok, this do the backup! but how to restore it?

jucaftp said:
(EDITED, check the end)
First, I've tried with the "adb" commands, but I get "Permission Denied".
So, I decided to try the tool, which still gives me a "Permission Denied", but still prints a sucess message at the end "Persist partition has been successfully backed up! Partition has been saved in Backup folder!"
Not sure if it's my mistake. I'm rooted + USB_debugging.
EDIT:
OK, I've read that for adb "su" to work, you need to have device unlocked, with screen on, and grant permission.
Turns out Magisk was rejecting root permissions to Perfdump automatically.
Should work now. Nevertheless, perhaps you could check why it prints that backup worked when permission was denied. Someone could be fooled there =D
Finally: Thanks for the app
Click to expand...
Click to collapse
riccetto80 said:
ok, this do the backup! but how to restore it?
Click to expand...
Click to collapse
I will create this week improved tool with gui, and it will have backup, restore and maybe root option.

Suspicious EXE from a junior member.
Why is it not just a script?

pulja9 said:
I will create this week improved tool with gui, and it will have backup, restore and maybe root option.
Click to expand...
Click to collapse
soo this is really work if my mac, bt wiped with rr .,, or i just need to place that original file or i need to flash stock rom and place this backup file

How can I locate the Backup folder to also backup the /persist files in another folder/device?

how to restore?

Sir, can you please help me , i totally messed up my phone , mac address -unavailable, Bluetooth- unavailable , how to get back all , i m on RR latest build , i want to back to stock . Please help me if possible .

pulja9 said:
Hello guys, this guide is for creating backup of persist partion which is holding important data about sensors, wifi + bluetooth data, imei and other stuff.
Before installing any other custom room, this is best thing to do, lot of custom roms rewrites persist partition with different data than your mobile devices has, you will have problem with calling(missing imei), problems with Wifi and other stuff, i think you get it...
REQUIRED TOOLS:
Code:
[URL="https://drive.google.com/open?id=1LW1CM6gLT9wRyy950rC6GmWAzEbcyfzE"]PersistBackupTool[/URL]
Follow this steps:
Code:
1. Root your device, this is pretty much easy guide: [URL="https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654"]LINK[/URL]
2. After rooting your device, enable Developer options (Go to settings >> System >> About phone >> tap Build number 7 times)
3. Enable usb debugging, go to Settings >> System >> Developer options >> and enable USB debugging
4. Run PersistBackup.bat and wait
5. Your persist partition will be saved in Backup folder.
ENJOY!!!
Click to expand...
Click to collapse
Lots of thanks @devs you guys are really awesome

where is my backup? i not found that

I have tried the setup procedure that was in op, however it comes up and says not recognised, can I have a step by step procedure eg do I have to go to EDL mode.
Thanks

enricogrim said:
Hello,
I see that this tool creates a .img file. Can I restore using TWRP?
thank you
Click to expand...
Click to collapse
I don't think so
TWRP recognize ISO as a recovery
I think it's dangerous because backup don't have any instructions for twrp to tell it where recover it, on which partition
Correct me if I'm wrong
Sent from my Mi A1 using Tapatalk

Does anyone know how to restore a backup?
Can we use fastboot? Or tool have restore option?

Question How to pull Build.Prop...

Here's where I'm at. I've got the system to give me the Mount /System option in recovery, now i just need assistance getting the build.prop pulled to my PC. What's the procedure for pulling the build.prop from the Android to PC via ADB while the system is mounted in recovery? Why am I getting one of these two ADB errors?
Error 1: Connect failed: closed.
error 2: Failed to get feature set: no devices or emulators
OR, am I approaching it wrong?
Thanks in advance,
K0mraid3

you dont need to be in recovery to do it via adb....
adb pull /system/build.prop
that will pull it to where evr you run the adb command
which would be
C;\adb more than likely
or you can choose a destination with
adb pull /system/build.prop c:\buildprop
if you create a folder called "buildprop" in the root directory of c:\
at least thats how i remember doing it many years ago, ive been away for a while at her majesties pleasure, so i cant try it currently as im not rooted

gav83collins said:
you dont need to be in recovery to do it via adb....
adb pull /system/build.prop
that will pull it to where evr you run the adb command
which would be
C;\adb more than likely
or you can choose a destination with
adb pull /system/build.prop c:\buildprop
if you create a folder called "buildprop" in the root directory of c:\
at least thats how i remember doing it many years ago, ive been away for a while at her majesties pleasure, so i cant try it currently as im not rooted
Click to expand...
Click to collapse
Thanks, so far, its still for some reason denying me permission when OS is booted. So i just cant quite figure out where im supposed to execute these commands, is my issue. I can boot directly to BL from recovery menu, but i can also mount system. i think maybe i need sto send command for r/w.. will try that now.

Another question, when i mount /system in recovery, does that carry over on boot?

no you can re mount system via adb though
Code:
$ adb shell
$ su
# mount -o rw,remount /system

gav83collins said:
no you can re mount system via adb though
Code:
$ adb shell
$ su
# mount -o rw,remount /system
Click to expand...
Click to collapse
1.Needs root for this command. If he have rooted device then why so much trouble needed. Simply use root explorer to copy
2.Since long Samsung have removed system from proc/mounts still magisk system_root can be used
3.Even with system in mounts you can't do system rw on S22 because of Samsung have implemented extra layer of protection. Even not with magisk system_root too
Indeed as of now there is no method available to make stock system/vendor/product/odm rw on S22 even with root access.
4.To copy file from system rw mount not needed, ro is fine

dr.ketan said:
1.Needs root for this command. If he have rooted device then why so much trouble needed. Simply use root explorer to copy
2.Since long Samsung have removed system from proc/mounts still magisk system_root can be used
3.Even with system in mounts you can't do system rw on S22 because of Samsung have implemented extra layer of protection. Even not with magisk system_root too
Indeed as of now there is no method available to make stock system/vendor/product/odm rw on S22 even with root access.
4.To copy file from system rw mount not needed, ro is fine
Click to expand...
Click to collapse
im yet to root my device so i cant test but what about
Code:
adb root
adb disable-verity
adb reboot
Then
Code:
adb root
adb remount

gav83collins said:
im yet to root my device so i cant test but what about
Code:
adb root
adb disable-verity
adb reboot
Then
Code:
adb root
adb remount
Click to expand...
Click to collapse
Do you got what I meant?
leave it.

dr.ketan said:
WTF
Do you got what I meant?
leave it.
Click to expand...
Click to collapse
look, there is no need for condescension and bad language, a simple "no" would have sufficed

Lol not meant to hurt you! but on which planet WTF is bad language
Here search WTF on xda

dr.ketan said:
1.Needs root for this command. If he have rooted device then why so much trouble needed. Simply use root explorer to copy
2.Since long Samsung have removed system from proc/mounts still magisk system_root can be used
3.Even with system in mounts you can't do system rw on S22 because of Samsung have implemented extra layer of protection. Even not with magisk system_root too
Indeed as of now there is no method available to make stock system/vendor/product/odm rw on S22 even with root access.
4.To copy file from system rw mount not needed, ro is fine
Click to expand...
Click to collapse
So my device is strange. It doesn't have root, but it indeed shows options in recovery to apply updates from ADB, SD Card aswell as boot directly to BL and to Mount /System, but when I'm booted, the OS is denying me permission to "Su" . I have verified that USB debugging is activated. So I'm trying to see if there's a way to pull the build.prop from Recovery since the Mount /System option is available, but my computer refuses to recognize the device in while in recovery, but easily finds it in Download, BL mode. No FRP lock. No accounts on device. But also no option to unlock bootloader. This device in particular is/was a development sample so I have no clue what the current state of the bootloader etc is in terms of being unlocked prior to me working on it.

It'd also worth noting that this device was loaded with Android 11 when I received it. I'm not kidding. So idk what's going on with this FrankenGalaxy

K0mraid3 said:
It'd also worth noting that this device was loaded with Android 11 when I received it. I'm not kidding. So idk what's going on with this FrankenGalaxy
Click to expand...
Click to collapse
K0mraid3 said:
So my device is strange. It doesn't have root, but it indeed shows options in recovery to apply updates from ADB, SD Card aswell as boot directly to BL and to Mount /System, but when I'm booted, the OS is denying me permission to "Su" . I have verified that USB debugging is activated. So I'm trying to see if there's a way to pull the build.prop from Recovery since the Mount /System option is available, but my computer refuses to recognize the device in while in recovery, but easily finds it in Download, BL mode. No FRP lock. No accounts on device. But also no option to unlock bootloader. This device in particular is/was a development sample so I have no clue what the current state of the bootloader etc is in terms of being unlocked prior to me working on it.
Click to expand...
Click to collapse
These options are normal in stock recovery and can be used only for flashing official zip (OTA), To have root access on your recovery, you needs custom one (TWRP) which is in development stage on S22
Without twrp, You needs to root device (must have oem unlock option in development option) to access system files while you are booted to android.
Android 11 on S22? Can you show me screenshot of settings - about phone - software info?

dr.ketan said:
These options are normal in stock recovery and can be used only for flashing official zip (OTA), To have root access on your recovery, you needs custom one (TWRP) which is in development stage on S22
Without twrp, You needs to root device (must have oem unlock option in development option) to access system files while you are booted to android.
Android 11 on S22? Can you show me screenshot of settings - about phone - software info?
Click to expand...
Click to collapse
Thanks for the clear answer, that's kind of what I'm working on is trying to gain root access, but like you said, I need oem unlocking, which isn't on this device. So I'm trying to find a backdoor/vulnerability that will take me even one step closer to atleast finding a way to set ro.secure. prop. Something VERY interesting I did find, is that if you put the device to Debug medium or high via device keystring activity, and play with the key combos, you can get booted into a mode called RDX, if you plug it into your dev system with the right drivers, it's treats the phone as if it were a Disk and shows a bunch of VZW upgrade software ment for PCs. I've installed it but haven't got it working quite yett.

No idea what you have shown in screenshot, I'd asked something else.

dr.ketan said:
No idea what you have shown in screenshot, I'd asked something else.
Click to expand...
Click to collapse
Maybe Heindall will give me better results. I just refuse to believe the manufacturers have outsmarted us all on this.