Related
Make sure your battery has a decent amount of charge in it, you don't want to run out of juice in the middle of this.
You will need to have the android sdk installed, as you will need to use the adb tool.
Windows users will need to install HTC Sync in order to get the usb driver for the phone installed.
Part 1: In which we find that the Evo spreads easier than a Thai whore during tourist season
Code:
adb shell "rm /data/local/rights/mid.txt"
adb shell "ln -s /dev/mtd/mtd1 /data/local/rights/mid.txt"
adb reboot
Part 2: In which we find that engineers have no personality, but they make one hell of a bootloader
Put the files from Toast's Part 2, for nand unlock onto the sdcard (PC36IMG.zip, mtd-eng.img, recovery.img, flash_image)
then (after making sure the sdcard is remounted to the phone if you used disk mode to xfer the files):
Code:
adb shell "cat /sdcard/flash_image > /data/local/rights/flash_image"
adb shell "chmod 755 /data/local/rights/flash_image"
adb shell "/data/local/rights/flash_image misc /sdcard/mtd-eng.img"
adb reboot bootloader
When asked if you want to update, say yes. Relax for a while, the update takes some time.
When the phone eventually boots back up:
Part 3: In which I find the whore, and make her install a custom recovery
Code:
adb shell "cat /sdcard/flash_image > /data/flash_image"
adb shell "chmod 755 /data/flash_image"
adb shell "/data/flash_image recovery /sdcard/recovery.img"
After this you should be fully rooted with nand unlock.
I highly recommend going through Whitslack's Starting Over method to bring your software and radios up to date.
You're done.
Pity this only came to light a few days before people are going to be upgrading to a new OTA.
No, this will not work for anyone who updated to 2.2.
epic!!! 789
niice!
Nice Find!
At least now people can be rooted prior to the new OTA!
damn it!
___
Sweet! Wish I had that method starting out. Lol.
Sent from my PC36100 using XDA App
does this method really work??
BAttitude7689 said:
does this method really work??
Click to expand...
Click to collapse
Yes it does.
ok, so i have no idea how that works... care to go into it alittle bit more?
khshapiro said:
ok, so i have no idea how that works... care to go into it alittle bit more?
Click to expand...
Click to collapse
The init scripts chmod 777 mid.txt on boot (this means that anyone can do anything to the file basically). By removing the file and linking it to mtd1, the chmod now makes mtd1 accessible by everyone after a reboot, which means that you can go directly to toast's part2 which starts with flashing mtd-eng.img.
Incidentally it appears the droid eris guys have been using this flaw to their advantage for a while as well ;D.
So no, really? What is "root?"
You do fine work, sir
posting in a legendary thread
Couldn't you then just use wits "start over" method for part two to make the process even shorter?
netarchy said:
Part 1:
Code:
adb shell rm /data/local/rights/mid.txt
adb shell ln -s /dev/mtd/mtd1 /data/local/rights/mid.txt
adb reboot
Click to expand...
Click to collapse
What would be more interesting is for someone on the new OTA non-root to see if this exists in the Froyo release. I'll look around for a posting of the OTA update non-rooted and try it on my smashed phone. At least I won't care if that thing looses root.
Could we get a "The easiest 1.47.651.1 root method with nand unlock" for dummies? I have no clue what to do with this code.
You need to use an ADB shell for this using the Android SDK....
I tried to use the Evo-Recovery shell and received permission denied errors.
I am not a DEV by any means, and do not claim any credit for any of this. However, for people who need help, this may offer some assistance -- this is definitely the easiest root method out there.
1. Download and Install Android SDK - Learn Here
http://forum.xda-developers.com/showthread.php?t=694250
2. Open up a Command Prompt by holding windows button & pressing R or by pressing Run and typing CMD.
3. Navigate your way in DOS to the Android SDK folder, then to the Tools Folder
4. Then enter in the code in part 1. After each line press enter...the line will repeat below it.
5. Follow Toasts Part 2 -- Link: http://forum.xda-developers.com/showthread.php?t=701835 -- Video found here: http://www.youtube.com/watch?v=tUXTB0eydwE.
5A. Because you didn't do Toast's Part 1 of Root first (you used an exploit provided by the OP), you will NOT have a NAND Backup. Put the Custom ROM you want to load on your SD card, and after unlocking NAND protection and doing the wipes, load it from the custom recovery in lieu of restoring your NAND backup.
6. You're now rooted w/ NAND Unlocked!
7. I would then suggest going here, and running this so you have a fully rooted, stock ROM with all your radio/wimax up to date: http://forum.xda-developers.com/showthread.php?t=715915.
Anyone know if this method will work on an unrevoked3'd Evo? I am trying to acquire full root and I was going to use SimpleRoot today but if this will work...
Thank you for this! Question about number part 7. YOu suggest running the fully rooted stock 1.47.651.1 afterwards. Would it be a bad idea to Just run the fully rooted stock froyo 3.23.651.3 or even any other custom rom for that matter? i.e OMJ's EVO 2.2 Custom rom? Thanks
regulator207 said:
Couldn't you then just use wits "start over" method for part two to make the process even shorter?
Click to expand...
Click to collapse
No because you need the engineering hboot to flash it since it's not signed by HTC.
Should work on 1.32 or 1.47. Nice.
Someone should test if this still works in the new 2.2 update. Good chance it does.
damit!
justinisyoung said:
damn it!
___
Click to expand...
Click to collapse
Hey! That's what I was gonna say!
Ive been trying to get TWRP loaded on to my TF300T on 4.2.1 using this guide but on the fastboot its stuck on waiting for device. The device is recognised in the Terminal but have no luck flashing the recovery. Is there any other methods for flashing a recovery I can use on linux or advice.
Im running Xubuntu 13.04
mackay508 said:
Ive been trying to get TWRP loaded on to my TF300T on 4.2.1 using this guide but on the fastboot its stuck on waiting for device. The device is recognised in the Terminal but have no luck flashing the recovery. Is there any other methods for flashing a recovery I can use on linux or advice.
Im running Xubuntu 13.04
Click to expand...
Click to collapse
Is your OS 32 or 64-bit? If it's 64, you may need to have both ia32-libs and ia32-libs-dev installed for fastboot to work properly. Also, did you get the android-tools packages from the repos? I'm not sure about the *buntus, but on Debian, they're in the unstable repos. Make sure you have the newest versions (trust me; it matters).
If you want to do it via ADB, you could do this:
Code:
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4
Make sure the recovery image is on your internal storage if you do it that way.
I recommend trying to get fastboot working, and use ADB as a last resort.
Its 32-bit, I used fastboot for my N4 so unsure why its not working just now. I tried the method you said but think i may ahve done it wrong it completed the operation but got the Android on its back with the red triangle :/
First time i got :-
1|[email protected]:/ # dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4
12896+0 records in
12896+0 records out
6602752 bytes transferred in 5.185 secs (1273433 bytes/sec)
Then after that i got :-
127|[email protected]:/ $ dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4
/dev/block/mmcblk0p4: cannot open for write: Permission denied
ry.img’: No such file or directory <
/system/bin/sh: dd:: not found
127|[email protected]:/ $ dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4
/dev/block/mmcblk0p4: cannot open for write: Permission denied
1|[email protected]:/ $
mackay508 said:
Its 32-bit, I used fastboot for my N4 so unsure why its not working just now. I tried the method you said but think i may ahve done it wrong it completed the operation but got the Android on its back with the red triangle :/
First time i got :-
1|[email protected]:/ # dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4
12896+0 records in
12896+0 records out
6602752 bytes transferred in 5.185 secs (1273433 bytes/sec)
Then after that i got :-
127|[email protected]:/ $ dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4
/dev/block/mmcblk0p4: cannot open for write: Permission denied
ry.img’: No such file or directory <
/system/bin/sh: dd:: not found
127|[email protected]:/ $ dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4
/dev/block/mmcblk0p4: cannot open for write: Permission denied
1|[email protected]:/ $
Click to expand...
Click to collapse
Stupid question probably, but is your tablet unlocked?
Also, for the second one, you weren't logged in as root. You need to be root to write the image.
Linux 101:
- If you see a dollar sign ($) in the terminal, you're a normal, unprivileged user
- If it's a pound sign (#), you're root.
Also, like I said before, the version of Fastboot matters. Way back in August, I soft-bricked my tablet, and fastboot gave me the same problem it's giving you, even though I had used fastboot on my tablet before that. Months later, I found the fastboot in the Debian repos. I'm not sure what the difference was between the versions, but the new one from the repos worked perfectly, and I was able to get my tablet working again.
EndlessDissent said:
Stupid question probably, but is your tablet unlocked?
Also, for the second one, you weren't logged in as root. You need to be root to write the image.
Linux 101:
- If you see a dollar sign ($) in the terminal, you're a normal, unprivileged user
- If it's a pound sign (#), you're root.
Also, like I said before, the version of Fastboot matters. Way back in August, I soft-bricked my tablet, and fastboot gave me the same problem it's giving you, even though I had used fastboot on my tablet before that. Months later, I found the fastboot in the Debian repos. I'm not sure what the difference was between the versions, but the new one from the repos worked perfectly, and I was able to get my tablet working again.
Click to expand...
Click to collapse
Yeah I unlocked it using the unlocker app and have the this device is unlocked at the boot screen. Forgot the su part :/ what i get for using the up button haha. Yeah it came up with grant superuser access on my tablet, I deleted and reinstalled fastboot the other day to see if it would help but it didnt. Might have to wait until i can access a Windows laptop :/
Sorry I couldn't help. Those are the most common problems/solutions I've seen and personally experienced. And I have no idea why dd didn't work in ADB Shell. I would check the recovery image and try again. Check out adb --help to see if there are any other options available. I'm not overly familiar with ADB.
You could also flash the recovery while booted into Android using Terminal Emulator. That's how I usually flash recoveries. Just use the dd method from the ADB Shell instructions. Just skip the first command, starting ADB Shell, and start at su.
Oh, and I completely missed it earlier, but make sure that the recovery you're using ends in -42.img or - 42.blob. If you use one with -JB, you could brick your tablet. I don't know why the guy giving instructions in your link said to use -JB, but there have literally been dozens of bricked tablet threads here because people flashed a -JB recovery on a 4.2 bootloader. -JB recoveries should only be used with the 4.1 bootloader.
EndlessDissent said:
Sorry I couldn't help. Those are the most common problems/solutions I've seen and personally experienced. And I have no idea why dd didn't work in ADB Shell. I would check the recovery image and try again. Check out adb --help to see if there are any other options available. I'm not overly familiar with ADB.
You could also flash the recovery while booted into Android using Terminal Emulator. That's how I usually flash recoveries. Just use the dd method from the ADB Shell instructions. Just skip the first command, starting ADB Shell, and start at su.
Oh, and I completely missed it earlier, but make sure that the recovery you're using ends in -42.img or - 42.blob. If you use one with -JB, you could brick your tablet. I don't know why the guy giving instructions in your link said to use -JB, but there have literally been dozens of bricked tablet threads here because people flashed a -JB recovery on a 4.2 bootloader. -JB recoveries should only be used with the 4.1 bootloader.
Click to expand...
Click to collapse
Thanks for the help anyway, yeah just glad i read up on the recoveries before hand incase it worked and i got bricked. Ill try using the terminal and see if that works
Hi. I have to flash a TWRP backup and can't do it thorugh custom recovery due I have a Yotaphone (the phone with a LCD screen by one side and a eInk screen by the other side) and the LCD screen is broken, so I have to use fastboot or adb (as far I know). I cannot even install a ROM because it needs the LCD screen for the first start.
The question if I can do it, cause I know it could be problems with formats.
(I asked this on Yotaphone specific xda forum but no one answered)
Thanks
eReader Fan said:
Hi. I have to flash a TWRP backup and can't do it thorugh custom recovery due I have a Yotaphone (the phone with a LCD screen by one side and a eInk screen by the other side) and the LCD screen is broken, so I have to use fastboot or adb (as far I know). I cannot even install a ROM because it needs the LCD screen for the first start.
The question if I can do it, cause I know it could be problems with formats.
(I asked this on Yotaphone specific xda forum but no one answered)
Thanks
Click to expand...
Click to collapse
You would probably have better luck flashing the stock firmware or have someone with the same device create an adb backup then restore it via adb.
Or if you know which individual .img files you need, have them pull a copy of whichever individual .img files you need(for example: system, boot, etc) then fastboot flash them or use adb shell to dd the .imgs back onto your device in the partitions they belong in.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
@Droidriven ,you are right about it would be easy to fash a stock rom, but the LCD screen is necessary for that due the first boot. Maybe I am a little lucky 'cause I live with person who has the same device as me.
I tried the adb backup -all but it seems to just make a backup of the personal data.
Making a dd backup patition would be the better, but for some reason my device isn't recognized as a MTP device and can only connect in PTP. Tried to change the configuration on the phone but still only works with PTP, and I think in PTP mode doesn't have a mounted folder where I can make this stuff.
What I don't know how to do is the dd within the adb shell. It will work connected in PTP mode?
eReader Fan said:
@Droidriven ,you are right about it would be easy to fash a stock rom, but the LCD screen is necessary for that due the first boot. Maybe I am a little lucky 'cause I live with person who has the same device as me.
I tried the adb backup -all but it seems to just make a backup of the personal data.
Making a dd backup patition would be the better, but for some reason my device isn't recognized as a MTP device and can only connect in PTP. Tried to change the configuration on the phone but still only works with PTP, and I think in PTP mode doesn't have a mounted folder where I can make this stuff.
What I don't know how to do is the dd within the adb shell. It will work connected in PTP mode?
Click to expand...
Click to collapse
Is USB debugging enabled?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Yes, debuggind mode is on. In PTP mode, adb sees my device correctly, in MTP mode appears like ???????
I think maybe the answer is where that you mentioned about "adb shell". As long as I can't see the phone mounted in MTP mode it's the only way I see. Now I am searching for the way on pointing the dd output file outside the adb shell. So the process is:
BACKUP:
-adb shell > dd partitions saving them outside the phone
FLASHING:
-fastboot partition by partition
Another problem I have is to know which partion is each, 'cause with "mount" I don't get so much information and with "cat /proc/partitions" only have 13 partitions with their size and no more info. I am looking what to "adb push" that can help me. Maybe install busybox.
Trying to backup&restore without MTP, without access to the recovery nor SDcard... Harder is impossible!!!
eReader Fan said:
I think maybe the answer is where that you mentioned about "adb shell". As long as I can't see the phone mounted in MTP mode it's the only way I see. Now I am searching for the way on pointing the dd output file outside the adb shell. So the process is:
BACKUP:
-adb shell > dd partitions saving them outside the phone
FLASHING:
-fastboot partition by partition
Another problem I have is to know which partion is each, 'cause with "mount" I don't get so much information and with "cat /proc/partitions" only have 13 partitions with their size and no more info. I am looking what to "adb push" that can help me. Maybe install busybox.
Trying to backup&restore without MTP, without access to the recovery nor SDcard... Harder is impossible!!!
Click to expand...
Click to collapse
This command in adb shell or Terminal Emulator should give you your partitions and names(obviously you'd type "su" then press enter then run this command)
ls -l /dev/block/platform/msm_sdcc.1/by-name/
The part with "msm.sdcc.1" might be different for your device. If that command doesn't work I'll help you find what needs to go in that part of the command for your device.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
su is not found inside the adb shell, and I found this is cause is not rooted. I have to do it through TWRP in android 6.
As I said, I have two devices of my model so I hope I find time tomorrow for doing it. I also hope to can flashing it to the other device in fastboot mode or some way it doesn't need the main screen (remember I have a LCD screen and a eInk)
I will say something when I do the root. Thanks
Finally did it!
It appears each partitions clearly with the "ls" command you give to me. The question now is how to dd outside the phone. Have I to mount the pc inside the shell or what?
eReader Fan said:
Finally did it!
It appears each partitions clearly with the "ls" command you give to me. The question now is how to dd outside the phone. Have I to mount the pc inside the shell or what?
Click to expand...
Click to collapse
adb shell should work to dd, you just need to make absolutely certain that you are dd-ing the correct .img to the correct partition(mmcblk0xx), the partition number would go where the xx is.
For example, my recovery.img would be flashed to mmcblk018(the number of my recovery partition.
If you dd an .img to the wrong partition, you'll brick the device, the command has to be exactly correct, no margin for error or easy fix if you get it wrong.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
I know all this stuff, but first I need to make the .img of each partition, and I though with adb shell I could do a dd to outside the phone. The TWRP backup I have isn't .img files, they are .win files.
I searched again if its possible to do that and all I found is the xda thread about doing a workaround with adb forward and busybox. If there is no more options I will do that.
What I thought to do is create a backup of the needed partitions and save them in the userdata free space. I think this have to be possible, but as I cannot use the LCD screen I have to do the backup where I do not have to pass thorugh the first boot configuration, cause it is did in the LCD screen. Which partitions have I to backup? Only system and boot? Or there is another tool for creating .img backups?
EDIT: Also found the twrp adb possibilities (http://www.pocketables.com/2014/10/using-twrps-new-adb-interface.html) but have the same problems than with dd
I frequently modify boot and recovery partitions from within terminal app. Here's what I do to grab the boot partition for example(you likely want BusyBox installed first)
cat /dev/block/bootdevice/by-name/boot >boot.img
or
dd if=/dev/block/bootdevice/by-name/boot of=boot.img
Make changes, then reverse the commands to write back. I think cat gives you a more verbatim copy for initially cloning a partition. I have had success with both.
The question that brought me here is what happens if i flash all partitions from a firmware archive and attempt to upgrade a whole system this way from twrp recovery.....
I want to root my phone and remove any bloatware. Can I do this with a stock A11 or custom Rom and still have the cameras and infrared range finder work properly? Does anyone know of any ROMs built specifically for the Power Armor 13?
Use the "temporary ROOT" method, will say put a matching SU-binary into phone's /data/local/tmp directory and then by means of ADB
make use of it:
Code:
adb devices
adb push <FULL-PATH-OF-SU-BINARY-ON-PC> /data/local/tmp
adb shell "chmod 0677 /data/local/tmp/su"
adb shell "/data/local/tmp/su -c '<COMMAND-WHAT-REQUIRES-SUPERUSER-RIGHTS-HERE>'"
jwoegerbauer said:
Use the "temporary ROOT" method, will say put a matching SU-binary into phone's /data/local/tmp directory and then by means of ADB
make use of it:
Code:
adb devices
adb push <FULL-PATH-OF-SU-BINARY-ON-PC> /data/local/tmp
adb shell "chmod 0677 /data/local/tmp/su"
adb shell "/data/local/tmp/su -c '<COMMAND-WHAT-REQUIRES-SUPERUSER-RIGHTS-HERE>'"
Click to expand...
Click to collapse
Thank you. I didn't know there was such a thing as a temp root. Do you have any advise on getting a ompatible rom for my hardware?
jwoegerbauer said:
Use the "temporary ROOT" method, will say put a matching SU-binary into phone's /data/local/tmp directory and then by means of ADB
make use of it:
Code:
adb devices
adb push <FULL-PATH-OF-SU-BINARY-ON-PC> /data/local/tmp
adb shell "chmod 0677 /data/local/tmp/su"
adb shell "/data/local/tmp/su -c '<COMMAND-WHAT-REQUIRES-SUPERUSER-RIGHTS-HERE>'"
Click to expand...
Click to collapse
Hi,
Can you please give me a hand with the method you mentioned?
1. the SU binary should be the supersu binary as zip file or the folder from the zip file?
2. could you please give me an example of how this string would look like if the file was for example in partition C?
adb push <FULL-PATH-OF-SU-BINARY-ON-PC> /data/local/tmp
I tried patching the boot image with Magisk and using ADB to install it but the phone is stuck on the start screen .
Thanks in advance!
I managed to root the phone permanently. However, I accidentally formatted the NVRAM partition. Could someone send me one?
Any updates?
FutureCrusader said:
Any updates?
Click to expand...
Click to collapse
I managed to do it quite easily. I will make a detailed tutorial this week.
denis9rafael said:
I managed to do it quite easily. I will make a detailed tutorial this week.
Click to expand...
Click to collapse
Thanks, appreciate it, mine is coming in this week so excellent timing lol
denis9rafael said:
I managed to root the phone permanently. However, I accidentally formatted the NVRAM partition. Could someone send me one?
Click to expand...
Click to collapse
Use the MauiMETA aka ModemMETA 10.2124.0
The software can restore your IMEIs but you need know How use that.
lopestom said:
Use the MauiMETA aka ModemMETA 10.2124.0
The software can restore your IMEIs but you need know How use that.
Click to expand...
Click to collapse
Because I messed up the first time I did it and had to format all with SP FlashTool, I had to restore the IMEI. I will post instructions on that too.
If you root with Magisk the boot image, it will put it in a reboot loop. I found on another forum a file that you have to flash first via adb.
It took me a week and reinstalling the software 5 times before I managed to find all I needed . Now it takes 10 minutes max to set it up.
FutureCrusader said:
Thanks, appreciate it, mine is coming in this week so excellent timing lol
Click to expand...
Click to collapse
I have created a complete guide on how to permanently root the phone using Magisk.
Please find it below:
How to root Ulefone Power Armor 13! Now with TRP recovery and Magisk included
Hello, Below is a guide on how to root Ulefone Power Armor 13 using Magisk, changing/restoring IMEI etc. Before you continue, I take no responsibility for any bricked devices. *Note: Before you begin, make sure you install the latest software...
forum.xda-developers.com
Hello,
I am trying to figure out how to either inject a custom bootloader like Clover onto my Nvidia Shield, or to Modify the existing EFI bootloader itself or with a modification to a Recovery program such as TWRP in order to be able to use a custom bootloader to select "Boot From Usb"
I figure I oughta make a backup, but I do not know how to backup my bootloader either....
I think I understand how to look at the shield's partitions now to find the one with the bootloader, I'm just nervous to proceed...
I have been researching for a week and have learned amazing tidbits of knowledge on the sublayers of the shield, and a lot of its partitions...
I was able to install a custom OS, modified GAPPS, and root on my shield, I am just hung up on this final part....
If anyone would care to share even a bread crumb where to start, I Would Be Ever So Grateful
Download Clover EFI Bootloader - MajorGeeks
Clover EFI Bootloader can boot OS X, Windows, and Linux on Mac or PC with UEFI or BIOS firmware.
www.majorgeeks.com
Root Nvidia Shield TV Pro 2019 Version
THIS IS OUTDATED https://forum.xda-developers.com/t/bootmod-root-your-shield-in-1-minute-2015-2017-2019.4524873/ REPLACES THIS IF YOU WANT ANDROID OR USE THIS GUIDE...
forum.xda-developers.com
I forgot to ask, IS THERE A PULL COMMAND FROM FASTBOOT, TO COPY PARTITIONS? MY GOOGLE FU IS SUPER BUT MAN I AM HAVING A HARD TIME FINDING EXACTLY WHAT I'M LOOKING FOR :-(
jenneh said:
I forgot to ask, IS THERE A PULL COMMAND FROM FASTBOOT, TO COPY PARTITIONS? MY GOOGLE FU IS SUPER BUT MAN I AM HAVING A HARD TIME FINDING EXACTLY WHAT I'M LOOKING FOR :-(
Click to expand...
Click to collapse
Typically partions get 1:1 bitwisely copied to PC by dd command ( AFAIK it's present in every Android distribution ) what can be achieved by means of ADB.
Example - for Windows PC only:
Code:
adb devices
adb exec-out "dd if=[BLOCK-NAME-OF-PARTITION-HERE] bs=4096" > C:\[NAME-OF-BACKUP-FILE-HERE]
jwoegerbauer said:
Typically partions get 1:1 bitwisely copied to PC by dd command ( AFAIK it's present in every Android distribution ) what can be achieved by means of ADB.
Example:
Code:
adb devices
adb exec-out "dd if=[BLOCK-NAME-OF-PARTITION-HERE] bs=4096" > C:\[NAME-OF-BACKUP-FILE-HERE]
Click to expand...
Click to collapse
Thank You! That is thinking outside the box haha I kept trying to do it through fastboot knowing there is very limited amount of commands, not realizing that Would Never Work. I appreciate Your Time! I will try adb now!!! It's so funny, it seems like such a simple answer but sometimes we see so many paths, it's hard to know which one to take...
jwoegerbauer said:
Typically partions get 1:1 bitwisely copied to PC by dd command ( AFAIK it's present in every Android distribution ) what can be achieved by means of ADB.
Example - for Windows PC only:
Code:
adb devices
adb exec-out "dd if=[BLOCK-NAME-OF-PARTITION-HERE] bs=4096" > C:\[NAME-OF-BACKUP-FILE-HERE]
Click to expand...
Click to collapse
Hello! May I pry your mind for a moment?
I ran this command on my shield "fastboot erase system" except instead of running it directly in the command line on windows,
I made a batch file for it, and when I ran the batch, it succeeded but it did something strange, it printed this message inside the batch
"
{\rtf1\ansi\deff0\nouicompat{\fonttbl{\f0\fnil\fcharset0 Calibri;}}
{\*\generator Riched20 10.0.19041}\viewkind4\uc1
\pard\sa200\sl276\slmult1\f0\fs22\lang9 fastboot erase system\par
fastboot erase boot\par
\par
}
"
It completely deleted the two commands i had in there and pasted that instead... do you know what that is by any chance or Why it did that? o.o It is fascinating!
I can not understand what you are doing: For me it is complete confusion.
jwoegerbauer said:
I can not understand what you are doing: For me it is complete confusion.
Click to expand...
Click to collapse
No worries, thank you for your time, Seriously. That ADB suggestion was Exactly what I Needed... Have a beautiful day!