Database Users

[TUT] How To Create DUMP out of Stock Rom ( UP NOW )

Hello .
Posting a tutorial on how to create a dump out of your stock rom, in case you delete some apps or modify some settings.
ALRIGHT LETS START:
STEP ONE:
Alright, so you want to make a backup of your phone software, but dont know what to do. Its simple, download the package the Android SDK from google and copy it to C:\ drive. Once you have download it, make sure you have Java installed in your system or else it will not work. After everything is done, open the program and install these two packages:
1. Android SDK Tools, revision 6
2. USB Driver package, revision3 ([COLOR="Red"IMP: Its important that the USB driver installed shows up as Composite Android Debug Device, else it wont work. ][/COLOR]
What Android SDK ?? Read about it here: [url]http://developer.android.com/sdk/index.html[/url]
Why Android SDK ? Because: it has the [COLOR="red"]android debug shell[/COLOR] which you require before communicating with your android phone. So download it ! From here:
STEP TWO:
Download Busybox from here : http://rapidshare.com/files/407238531/busybox What is Busybox ?? Read about it here: http://www.busybox.net/
MD5 Signature: C5B76280434EEF49310AD8F1810B10B2
STEP THREE:
One you have downloaded busybox, copy it to the C:\ drive of your computer and then follow the next step. The next step is to open the Command Prompt ( type cmd in the Run prompt ) if using Vista right click on "Run as Administrator".
Assuming you are the root of C:\
Type: C:\cd android-sdk-windows
-> then
Type: C:\android-sdk-windows\ cd tools
-> if you have android debug shell and USB drivers properly installed
Type: adb devices
Now your device will show up as a binary number .. Success ! if it doesn't show up you need to install the drivers again or something else is wrong.
STEP FOUR:
Now once your device shows up, we will need to download the busybox from the computer to the phone. Since we can write anything in the /data/local portion of the android system we will copy the busybox file to the android device.
Type: adb push busybox /data/local/busybox
Once it has been copied to your device issue this command.
Type: adb shell This coomand is issued to go to your mobile's terminal where you can issue commands internally to the phone.
--> then
Type: cd /sdcard This command is given inorder to go to the sdcard ( i.e the internal storage of your phone )
--> then
Type: chmod 755 /data/local/busybox This command is issued to set user -rwxrwxr-x permissions to the file.
--> then
Finally, issue this command.
Type: /data/local/busybox tar cvf Samsung.tar /system This command is given to copy and tar the system folder where all the stock applications and programs are and to create a dump of that system folder.
STEP FIVE:
Job Done !!
The Samsung.tar file can be copied to the computer now. Have fun.

this is perfect, as i want to create a dump of my original ROM

A dump is simply a backup of your original ROM right?

thats good news if it is indeed a a backup of the stock firmware.
i want to back up my warranty firmware!

OrionTC said:
thats good news if it is indeed a a backup of the stock firmware.
i want to back up my warranty firmware!
Click to expand...
Click to collapse
it is only a backup of your stock apps and driver if so however it doesnt convert the files into a flashable rom version.

is there a way for us to backup the firmware?? (not just stock apps)

tids2k said:
it is only a backup of your stock apps and driver if so however it doesnt convert the files into a flashable rom version.
Click to expand...
Click to collapse
So this is not a tutorial of how you back up your stock rom but how you back up your stock apps and stock drivers?

droidwi said:
So this is not a tutorial of how you back up your stock rom but how you back up your stock apps and stock drivers?
Click to expand...
Click to collapse
Correct. We most likely won't be able to actually perform a complete backup until Nandroid works on the handset.

Too bad, the title was very promising but what you show is just an backup archive of the system.
BTW, there is no guarantee that restoring it will produce a usable phone, because kernel, datas, modem baseband etc won't be restored too !
But this can be useful to restore some file after a mistake done on /system files.

supercurio said:
Too bad, the title was very promising but what you show is just an backup archive of the system.
BTW, there is no guarantee that restoring it will produce a usable phone, because kernel, datas, modem baseband etc won't be restored too !
But this can be useful to restore some file after a mistake done on /system files.
Click to expand...
Click to collapse
im working on creating a stock rom ... may be some happy results and happy faces. who knows . keep sticked !

uploading dump again .. please wait.

So, Can i just select this dump in Odin and it will recover to stock firmware. Quite confused here.
The file size is 275 megs , so is it only for apps? Have you flashed with this dump. Nice work so far. THanks.
Edit: Just realised the dump option in Odin is for dumping my rom , not loading one.
So stuck with this until Samsung update. Huh!

Is this the same procedure as making a backup /efs?
I've been searching the forum for hours and this is the only thing I could find that looked anything like it.

This won't work
No, no and no !!
This procedure will not backup your stock ROM.
A complete rom consists in:
- a primary bootloader.
- a secondary bootloader.
- an initrd image with the kernel.
- a rootfs (the /system partition).
- an efs partition.
- a binary radio firmware.
There is no known method to backup all the flash partitions and transform them into proper files that can be reflashed with Odin or Heimdall.

Plinn said:
No, no and no !!
This procedure will not backup your stock ROM.
A complete rom consists in:
- a primary bootloader.
- a secondary bootloader.
- an initrd image with the kernel.
- a rootfs (the /system partition).
- an efs partition.
- a binary radio firmware.
There is no known method to backup all the flash partitions and transform them into proper files that can be reflashed with Odin or Heimdall.
Click to expand...
Click to collapse
+1.. The thread is misleading.. This doesn't accomplish anything! You really think people in the "Android Development" section don't know about tar?

Did anyone already managed to get the built-in dump function from Odin working?
With Odin v1.3 there was the possibility to decide whether to dump AP RAM or AP NAND (followed by an ID).
With Odin v1.52 you can't choose this anymore. It will only dump AP NAND.
But my first attempts were unfortunately not very promising

Best way to create image backup

Here is the situation:
I will be getting a Brand new fresh untouched A500 later in the week as a replacement for my faulty one (Micros SD slot no longer working).
I want to make a full backup of some sort to share with the XDA community. I am in Australia and know that a number of people are looking for a copy of this rom to restore back to original for whatever reason.
I believe it should be shipped with 1.016.04_Com_Gen1.
I have had experience using CWM and rooting on this device and have flashed several roms to my device in the past. I can also do a full backup in CWM. I also have a working adb.
What format does the community really want, and how do I go about creating it.
I am willing to help other by providing this rom, but want to know the best format to supply it in and get it right first go.
Step by Step instructions required please. We have a week to sort this out before I get the unit.
Cheers,
Michael.

Trinnity66 said:
Here is the situation:
I will be getting a Brand new fresh untouched A500 later in the week as a replacement for my faulty one (Micros SD slot no longer working).
I want to make a full backup of some sort to share with the XDA community. I am in Australia and know that a number of people are looking for a copy of this rom to restore back to original for whatever reason.
I believe it should be shipped with 1.016.04_Com_Gen1.
I have had experience using CWM and rooting on this device and have flashed several roms to my device in the past. I can also do a full backup in CWM. I also have a working adb.
What format does the community really want, and how do I go about creating it.
I am willing to help other by providing this rom, but want to know the best format to supply it in and get it right first go.
Step by Step instructions required please. We have a week to sort this out before I get the unit.
Cheers,
Michael.
Click to expand...
Click to collapse
I ll wait for it, mine was on that firmware...

Thinking this is probably the best way:
Backup the first 0x680000 bytes of mmcblk0 and all partitions (except cache + data) with dd:
dd if=/dev/block/mmcblk0 bs=512 count=13312 of=/mnt/external_sd/dumps/mmcblk0_start
dd if=/dev/block/mmcblk0p1 of=/mnt/external_sd/dumps/p1
dd if=/dev/block/mmcblk0p2 of=/mnt/external_sd/dumps/p2
dd if=/dev/block/mmcblk0p3 of=/mnt/external_sd/dumps/p3
dd if=/dev/block/mmcblk0p5 of=/mnt/external_sd/dumps/p5
dd if=/dev/block/mmcblk0p6 of=/mnt/external_sd/dumps/p6
dd if=/dev/block/mmcblk0p7 of=/mnt/external_sd/dumps/p7
Comments???

Agreed. Also make a CWM backup after that for convenience. After trial and error I found it does restore properly too as long as you don't forget about the recovery.img (has to be restored from acer recovery installer app)
On my thread CWM always gave checksum error for the others unfortunately.

I'll be waiting to see how you go with this. I was one of those who stupidly/ impatiently updated using the leaked acer update before understanding the need for a backup of my original. :-(

Got the tablet
I got the new tablet today and have backed up the rom and put it here for all to share:
http://www.megaupload.com/?d=CQRC5CPC
Enjoy!

Trinnity66 said:
I got the new tablet today and have backed up the rom and put it here for all to share:
http://www.megaupload.com/?d=CQRC5CPC
Enjoy!
Click to expand...
Click to collapse
ACER_A500_1.016.04_COM_GEN1
thanks for that
what kind of backup is this ?? ( ADB or CWM )
I asked, because it's nearly 300MB bfore commiting to download
and personally, I would preferred CWM method of restoring.
P.S ... did you get any update notification afterwards ?

These are CWM created image files. Cache and data removed.
No update notification received as yet.

nevermind

Trinnity66 said:
I got the new tablet today and have backed up the rom and put it here for all to share:
http://www.megaupload.com/?d=CQRC5CPC
Enjoy!
Click to expand...
Click to collapse
downloaded this ROM, copied onto the CWM backup directory, when i try to restore using CWM, it complains about MD5 mismatch.
is this the correct way to restore?

CWM not working when backing the image as it should like on the phones, I tried and doesn't restore the image.
Sent from my SPH-D700 using XDA App

I'm having trouble with my CWM also,i backed-up 3 different roms,but when i go to restore them,the superuser denies permission for all my apps.I have to reinstall the rom over the top to get the root permissions to work correctly.

How to root stock 3.2

Ok, after messing around with 3.2 I decided to fix the rooting issues without downgrading. The problem with downgrading is it requires a SDCard and requires you to install a couple of programs and then to install an update.zip from the sdcard. I could not get half my ACER's to read and mount a sdcard, and some ACER's I have located in a remote office and trying to walk someone through the process was too painful. I tweaked the the downgrade tool's images to install 3.2 with root instead of downgrading it and jumping through hoops. All I did to the stock image is to copy the ash shell over to /system/xbin/su and set the sticky bit. Everything else is stock.
Update posted here, read thead http://forum.xda-developers.com/showpost.php?p=20654298&postcount=129
New version V4
-- The instructions are in a PDF document inside the download --
== Version V4 ==
-- Added /system/subin/su which is a backup (backdoor) root in case an OTA deletes the /system/xbin/su
-- Set permissons on the su root(#) tool so OTA's shouldn't be able to break it.
-- Added drivers for XP
Summary:
Version V4 is the same as V3 with the only difference being that there is a NEW backdoor script which has some additional features to protect root(#) from getting broken when you do an OTA. I also applied these to this flash image so you wouldn't have to add the additional protection yourself. V4 also has the drivers for XP included. However, when taking an OTA you should also install the backdoor for additional protection. However, you cannot leave the backdoor installed as it turns off sound. So having a little more protection just might save your root in case you take an OTA and forget to install the backdoor.
Download it here: http://www.multiupload.com/NS0X5TK4D1
Alternative download location:
http://depositfiles.com/files/c6pr69ri6
http://www.fileserve.com/file/s2wCQpN/root-3.2.1-V4.7z
http://www.filesonic.com/file/jTA7AMN
http://www.filejungle.com/f/vRnfK5/root-3.2.1-V4.7z

Which 3.2 update is it ? Fully working, no issues ? Good job. Is it power + volume down or volume up to go into recovery ? And is it possible to flash a custom kernel like Honeyvillain on this stock ROM ?
Thx

Has anybody ( including OP) tried this method?

It is the 3.2 OTA for WiFi that my Tablet picked up. It is total stock other than making a SU from the ash shell and putting it into /system/xbin.
Fully works, no issues, have used it on 8 ACER 500's with no issues.
To enter recover it is the left side of the volume button which is volume (-) oopps NOT (+) as I indicated.

Hah, saying Vol +/- is not intuitive on this device since when in landscape, Vol + is the "right" side, but in portrait mode Vol + is the "top" side.

no go
Hi, i can see my iconia uid from adb ( already installed in my pc) but
not from test.cmd, in the extracted package. Any ideas?
REPEATED STEPS 1-4 ( PER INSTRUCTIONS) ON 2 PC'S RUNNING W XP. SO FAR "NO GO" TEST.CMD CANNOT FIND PATH.... AND DOTNETDETECTER, THEREFORE, DOES NOT WORK.

will this wipe all the data on the tablet?
---------- Post added at 04:19 PM ---------- Previous post was at 03:40 PM ----------
JUGOMAN said:
Hi, i can see my iconia uid from adb ( already installed in my pc) but
not from test.cmd, in the extracted package. Any ideas?
Click to expand...
Click to collapse
same here i run the setup file and it installs but after i run test.cmd and it cant find it

Sorry about the test.cmd not working. The script just calls adb.exe to make sure it is working and I have it installed in another directory that I did not include. I posted, to the original message an attachment, it is called fix-Test.7z that fixes the test.cmd. You should be able to just unzip it into the directory you created and run the test. The archive includes the adb.exe and dll's so the test.cmd should work. If you have adb.exe working you really don't the test.cmd, but I found out when talking someone through it (over the phone) this made sure that adb.exe was installed and they had the tablet USB Debugging turned on.
And it is a quick and easy way to get the serial number which you need to flash it.
Thanks,
Let me know if you have any more issues.

does anyone know if flashing it this way will delete all your data on the tablet?

NO GO2
The attchment does fix the test.cmd "problem" but the next step, Dotnetdetecter, does not work. It re-installs the driver (?) then error "adb is old" or something like that. All packages in my computer's ADB are up to date. I think that the "target" directory in the DONETDETECTER IS NOT CORRECT. ANY IDEAS? btw GOOD WORK!!!!!

Many thanks for this. It is really easy like this. Keep up the great work.

UPDATE
Installed, booted, but no root. Previous rom( acer update) was3.2 Gen 2, now 3.2 Gen 1. was worth a try.. Thank you... tablet is working just fine, just no root

jimmkd84 said:
does anyone know if flashing it this way will delete all your data on the tablet?
Click to expand...
Click to collapse
Yea. I've never done this before so I'm wondering the same thing.
Also
Idk about this test thing but if u type 'adb devices' it'll show you which devices (if any) are connected. I always use that as a test when i use the adb to install apks.

bad adb
NO GO2 WROTE
The attchment does fix the test.cmd "problem" but the next step, Dotnetdetecter, does not work. It re-installs the driver (?) then error "adb is old" or something like that. All packages in my computer's ADB are up to date. I think that the "target" directory in the DONETDETECTER IS NOT CORRECT. ANY IDEAS? btw GOOD WORK!!!!!
Not sure what that would be. I just use the adb.exe and dlls that are in the fix.zip. Maybe you have a different version loaded?

ROOT IS NOT in the apps. It is in the adb shell.
What this does is allows you to connect to the device using adb.exe shell and you will get the $ prompt.
at the $ prompt type su and press enter. You will get # and be in su mode.
Now you can do whatever you would like. What would that be, you might ask? Well you could do the following:
1. mount system as rw
2. Push your favorite su tools to the device so they are listed in the apps (busybox etc).
Again this gets you to 3.2 with the ability to have a SU when connected via the adb shell. I left the building of the tools and custom CW to you guys to do as you wish. Here's something else you could do.
1. Shell to it, and issue the SU
2. Mount system as rw
3. Push your favorite tools to where you want (busybox etc)
4. Take the recovery.img (in the zip) and dd dump it to the recovery partition. This will put clockwork on the device (1.5).
a. You should probably run itsmagic too.
5. Get everything the way you want it.
6. Reboot to recovery and CW will load.
7. Now with CW 1.5 loaded, you can build and make copies of your ACER and make them available to anyone you like. CW 1.5 does NOT require an external SDCARD.
Sorry, if I did not make it clear that this is just a SU that you have to use from the command line. If someone wants to give me the links to a SU apk, busybox, etc they'd like included I'd do it. It would only take a few minutes as I got hundreds of these ACER's to flash for our company. I just wanted to get SU, but what the heck, I could build it out if someone would like it that way. ACER really pee'd me off with this, and guess what? They left the ability to gain root in the 3.2 100. Why the 'Sam Heck' did they change the 500 3.2 so you cannot get root?
So, anything I can do to help let me know. Also, If you never want ACER to send you another update I can tell you how to fix that too. All you have to do is the following:
1. Get to the adb shell $
2. type su to get the # prompt
3. Now mount system as rw by doing the following:
a. mount -t rfs -o remount,rw system /system
4. Now rename the update tool by doing the following:
a. mv /system/app/FDUpdater.apk /system/app/FDUpdater.apk.old
mv /system/app/FWupdateService.apk /system/app/FWupdateService.apk.old
5. To get OTA then just reverse the process if you ever want ACER and their OTA to break your fleet of ACER Tablets by pushing silly updates that they think you want then you can undo it. The last I knew, I owned these ACER Tablets and I don't take kindly to them changing something that I do NOT WANT CHANGED. They should be sued, matter of fact, I think they are violating federal laws by destroying data on MY tablets. Anyway, off my soapbox.

i have re run the new test.cmd and is working now, and have successfully run dotnetdetector but i dont want to proceed until someone can confirm if doing this will wipe all data on the tablet
appreciate it, great work btw dev!
---------- Post added at 05:05 PM ---------- Previous post was at 04:39 PM ----------
did this wipe the data on it?

Hello, may i use this procedure on my A501?
Thanks

I did NOT test on the 501 so I do not know. If it was me, I would take the 501 stock images and put them in the kitchen and root them and then replace the ones in my zip with those or better yet, use CW to flash it in.
I think the ACER 501 has cell phone data connection doesn't it? I don't think the stock for WiFi only would be a good idea.
What ACER did on the 3.2 update (my opinion) was removed the Gingerbreak exploit and they removed the adb root exploit (they left the adb root exploit in on the 100). This is what many OEM's did, however many allow you to flash your own easier than ACER seems to want to let us. So if you got 3.2 NON-ROOTED loaded then there is no way to 'hack' out a root (just yet).
So how do you root it? You have to make a custom ROM and flash it. Now ASUS/Motorola/Samsung/Toshiba all allow you to flash your own ROM if you know what you are doing.
ACER seems to hide how to put the tablet into flash mode (if someone knows please let me know). Even if you did flash it they do want those ROMS running so they take each partition and calculate the MD5Sum and write it to, I think, partition #7. Therefore, if you do figure out how to flash in a new boot image or system image the tablet will not boot because the MD5Sums will not match (if you brick your tablet this way you are fubar). Fortunately, someone wrote a tool called itsmagic which you can run to tell the tablet to rebuild these. But if you fubar brick it before you get itsmagic run, I don't know how you get into flash mode using the keys so you'd be up a creek.
So, the 411 skinny on rooting an ACER with 3.2 is to get 3.2 off the device. Fortunately, they made an earlier flashing tool to flash in 3.0. I would guess this leaked out as a way for people to reflash to stock when they have issues.
Once you are on 3.0, you now can use Gingerbreak or the adb root exploit to root it. Once rooted, you can get CW loaded. CW allows you to install your own ROM's. Without CW you can only install ROM's signed by ACER and without ROOT you cannot install CW.
So, if you flash to the 3.0 now you are 'back to the future' in 3.0, you can root and install CW so you can now install a custom ROM from your SDCard.
What I would do is go get the STOCK ROM from ACER for your 501 device.
Once you have the stock ROM, you can use the kitchen tools to unzip the ACER ROM and root it to your liking. Now, re-zip it, but you cannot sign it with an ACER certificate so it will only install using CW. No, big deal because you got 3.0 loaded with CW. You boot to recovery CW and then run the update from your SDCard that you built in your kitchen.
This isn't really that hard to do if you're willing to read some documentation.

I have no idea if it wipes it clean totally. It does walk you through the setup again (like it was new out of the box) so I would assume most things would be wiped. I would back it up and not take the chance because it is best to be backed up.

Just a note here. It says fully stock execpt root? i don't think that's entirely accurate. I believe that it's still downgrading the bootloader, otherwise you'd never be able to get CWM to run, as itsmagic doesn't work with the new bootloader. So your left with stock 3.2 ROM with adb/su abilities and pre 3.2 bootloader.
On another note, I believe step 17 is not needed. CWM run's itsmagic automatically on every boot. So just booting CWM and then rebooting to android should suffice.

Wolf's ultimate flash and downgrade guide (NO ROOT NEEDED) (root opportunity for .21)

WARNING
This method will not work on any JB rom available, apparently google has patched the exploit.​
Note that downgrading method for unrooted devices is highly experimental and may turn your device into worthless brick. Read this WHOLE thread carefully before you start doing anything with your Transformer.
MOD EDIT: It is reported that this method doesn't work with the new Jelly Bean firmwares on the TF201 and the TF300T,
Sorry, but I will not be able to support you between 3rd and 15th of May because I have to pass my final exams.
However feel free to post your questions in this topic I am sure that somebody will be able to help you.​
Click to expand...
Click to collapse
Description​Method 1 - Rooted Devices
This method allows you to flash any update released by ASUS without need for custom recovery.
ROOT is required to unlock mmcblk0p4 write access for dd.
Method 2 - UnRooted Devices
This method allows you to flash any update released by ASUS, no mater for SKU etc.
It uses file linking trick to unlock mmcblk0p4 write access even when su is not present.
Method 3 - UnRooted Devices - Recommended
This method allows you to directly flash the recovery even on unrooted device. This may be used next to root your TF by prepared su package.
It uses file linking trick to unlock mmcblk0p4 write access.
Click to expand...
Click to collapse
Disclaimer​
Despite both methods have been confirmed (by myself) to work, the whole process of flashing mmcblk0p4 with dd brings high risk of bricking device by for example file system corruption.
I do not take any responsibility for damaged or bricked devices. Before flashing you have to assume the risk and chances of geting bricked.
Under no circumstances should you brake cmd during blob file is flashed by dd. If that happens do not reboot. PM me and go on IRC
Click to expand...
Click to collapse
Requirements​
BLOB file (look at links box at the bottom for few)
ADB enabled
Root acces (only method 1)
Click to expand...
Click to collapse
Notes​Sorry for the mistakes, but English is not my native language PM me if you find any so I will be able to correct them.
Before posting a question look into FAQ maybe it have been already answered.
Guide is inspired by Turge who wrote similar article for TFP (link here). However whole 2nd method was invented and described by me.
Thanks go to:
Code:
[CENTER]
AndroidRoot.mobi - for RazorClaw
ViperBoy - for viperMOD rooting tool
jcase - for NachoRoot
sparkym3 - for his ICS rooting methods
Roach2010 - for all his work
sbiriguda - who inspired me to dig around symlinking
[/CENTER]
Click to expand...
Click to collapse
Instructions - Method 1 - Rooted​1. Upload the BLOB file to internal storage of your tab. (mounted as /sdcard)
2. Connect tablet to the computer and start ADB session.
3. When you will be in adb shell execute following comands:
Code:
su
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
4. The command prompt will be empty as wnen nothing happen, do not panic wait until the end of the process. DO NOT INTERRUPT (it will take apx.3-10 min)
5. When you see the following message:
Code:
1066806+1 records in
1066806+1 records out
546204969 bytes transferred in 250.309 secs (2182122 bytes/sec)
(the numbers in resulted message may be diffrent but it has to have the same structure)
You can safety reboot the device by exiting shell and executing :
Code:
adb reboot
6. Once rebooted you will see ASUS EeePAD flashing progress bar. Be patient and wait till the end.
7. Tablet will reboot itself and start loading new system. (as it is first boot it may take few minutes)
8. Be happy from your new firmware.
ADDITIONAL OPTIONAL STEP
In some cases flashing previous firmware leaves data partition intact.
I suggest to clean it by booting with [vol down] and [power] pressed (you will see the info about the rom). Than wait until the screen with android and wipe data appear. Select wipe by switching with [vol down] and accepting with [vol up] pressed two times. It mostly happen when downgrading to HC from ICS.
Click to expand...
Click to collapse
Instructions - Method 2 - UnRooted​1. Upload the BLOB file to internal storage of your tab. (mounted as /sdcard)
2. Connect tablet to the computer and start ADB shell session.
3. When you will be in adb shell execute following commands:
Code:
mv /data/local/tmp /data/local/tmp.bak
ln -s /dev/block/mmcblk0p4 /data/local/tmp
exit
4. Now reboot your tab through:
Code:
adb reboot
5. Once you see ASUS loading screen you should be able to start ADB shell session again (if not just wait), than (in shell) execute:
Code:
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
6. The command prompt will be empty as wnen nothing happen, do not panic wait until the end of the process. DO NOT INTERRUPT (it will take apx.3-10 min)
7. When you see the following message:
Code:
1066806+1 records in
1066806+1 records out
546204969 bytes transferred in 250.309 secs (2182122 bytes/sec)
(the numbers in resulted message may be diffrent but it has to have the same structure)
You can safety reboot the device by exiting shell and executing :
Code:
adb reboot
8. Once rebooted you will see ASUS EeePAD flashing progress bar. Be patient and wait till the end.
9. Tablet will reboot itself and start loading new system. (as it is first boot it may take few minutes)
10. Be happy from your new firmware.
ADDITIONAL OPTIONAL STEP
In some cases flashing previous firmware leaves data partition intact.
I suggest to clean it by booting with [vol down] and [power] pressed (you will see the info about the rom). Than wait until the screen with android and wipe data appear. Select wipe by switching with [vol down] and accepting with [vol up] pressed two times. It mostly happen when downgrading to HC from ICS.
Click to expand...
Click to collapse
Instructions - Method 3 - UnRooted
This will definitely not work with Transformer Prime continue only if you are owner of TF101 of TF101G​
1. Upload the RECOVERYBLOB file to internal storage of your tab. (mounted as /sdcard)
2. Connect tablet to the computer and start ADB shell session.
3. When you will be in adb shell execute following commands:
Code:
mv /data/local/tmp /data/local/tmp.bak
ln -s /dev/block/mmcblk0p4 /data/local/tmp
exit
4. Now reboot your tab through:
Code:
adb reboot
5. Once you see ASUS loading screen you should be able to start ADB shell session again (if not just wait), than (in shell) execute (some times it gets longer, but do not panic it is normal):
Code:
dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4
6. The command prompt will be empty as when nothing happen, do not panic wait until the end of the process. DO NOT INTERRUPT (it will take apx.3-10 min)
7. When you see the following message:
Code:
8860+1 records in
8860+1 records out
4536396 bytes transferred in 1.718 secs (2640509 bytes/sec)
(the numbers in resulted message may be different but it has to have the same structure)
You can safety reboot the device by exiting shell and executing :
Code:
adb reboot
8. Once rebooted you will see ASUS EeePAD flashing progress bar. Be patient and wait till the end.
9. Tablet will reboot itself and start loading new system. (as it is first boot it may take few minutes)
10. Be happy from your new recovery.
ADDITIONAL - ROOTING
11. Download this SU + Superuser.apk package and place it on internal memory or microsd
12. Boot to recovery. (turn off your TF and than boot with [vol down]+[power] pressed, once you see the letters identifying the system press [vol up]
13. Now you should be in custom recovery. Select 'Install from zip file' and then select the file on desired location internal or external.
14. Once flashing is done go back and select 'Reboot system'
15. Now you got freshly rooted Transformer. ENJOY
Click to expand...
Click to collapse
BLOBs​
BLOB file can be extracted from any update file. It is contained inside XX_epad-user-x.x.x.x.zip achive. Where XX (e.g WW or TW) refers to SKU of firmware and x.x.x.x to its version (e.g 9.2.2.3)
Or you can pick up a few here
Now they are ziped to reduce the sizes (MD5 value shows the control sum of each blob not zip) (sorry for hostings but I don't have space on dropbox any more, you may register to increase) (if you know faster mirror PM me)
NEW MIRROR SITE WITH ALMOST ALL FIRMWARES HERE
TF101/G BLOBs (Transformer)
Honeycomb
WW 8.6.6.19 - MD5: D63D60F6C71F5B614B338244D3788735 - or mirrors (1 2)
WW 8.6.6.23 - MD5: 1227F19BC4415661CACB05A483504953 - or mirrors (1 2)
Ice Cream Sandwich
US 9.2.1.11 - MD5: 4F6069430B20C35C8833F50DFA0FE0FD - or mirrors (1 2)
WW 9.2.1.17 - MD5: 5C78C28C31888943AB67CCE4B4448319
US 9.2.1.17 - MD5: 380CA6399374FF5F84154509365A83F7 - or mirrors (1 2)
TW 9.2.1.17 - MD5: CA52E4AD670DFFA29DC1CBA04A0A4164 - or mirrors (1 2)
WW 9.2.2.3 - MD5: 5D5A44069346C4D7D2740E4100520692 - or mirrors (1 2)
TW 9.2.2.3 - MD5: pending
TF201 BLOBs (Transformer Prime)
Honeycomb
WW 8.8.3.33 - MD5: 5136E579FAEDDFE15F6AAE623B6CB67D - (or mirrors 1 2)
Ice Cream Sandwich
WW 9.4.2.11 - MD5: B2668A3387924B19A91F74ABF5DBE4E8 - (mirror)
US 9.4.2.14 - MD5: EF2E635BD6921BFA9D01FC0E4DD0644B - (mirror)
WW 9.4.2.15 - MD5: 55122257B30E9376DF463F3C1A8BA702 - (or mirror 1 )
WW 9.4.2.21 - MD5: 1129DC2643BD0F5DC6C07B9A1B619548 - (or mirror 1 )
RECOVERYBLOBs (only for TF101)
Rburrow's Rogue XM Recovery (mirror) - MD5: 6EE759A84ED02F0D95A029EC245CFDC5 - thread​
Click to expand...
Click to collapse
Hope it will help
Results​Confirmed to work on both TF101/G (ASUS Transformer) and TF201 (ASUS Transformer Prime)
However keep in mind that TFP have to be locked in order to use second method otherwise you may brick your device.
It probably can be used with slider as well
I also confirmed that it is possible to root any official OTA (on TF101/G) by flashing recoveryblob containing custom recovery and than update.zip with su and superuser app.
Proven that Method 2 also work with 9.2.1.21 update to downgrade the software and reroot device. - thanks alvin612.
Method 2 may also work on locked Transformer Prime however be careful and read warning and disclaimer in this thread.
Click to expand...
Click to collapse
Click 'Thanks' if I helped you

Let me just say this: you are a freaking genius. I didn't even think of symlinking /dev/block/mmcblk0p4 to /data/local/tmp so it would change ownership and permissions on reboot. This is f*ing brilliant!
Moreover, if you have a blob for CWM you can also use the second method to install it on an unrooted device and then root it using the customary update.zip with su and superuser.apk (yes, even on 9.2.2.3 TF101Gs).
Again, great job!

A big **sigh**, finally a solution for non-root users/ non-NVflash-ables to get back. I am rooted and will always be as long as the expliot is there but this should help many, many non-rooted people that are frustrated with ICS.
Many thanks.

Worth more than just using the thankometer - thanks for this.
Sent from my Transformer TF101 using XDA

absolute genius!!!!! Thanks

Just GENIUS
you are genius bro thank u so much for this guide. I'll try it tomorrow bcuz it's late " 1:00 am " and report back later.
Thanks again
Edit: I couldn't wait until tomorrow so i said let's try it but something happened and now my tab is bricked ( Stuck on EEE Pad screen )

hearts king101 said:
you are genius bro thank u so much for this guide. I'll try it tomorrow bcuz it's late " 1:00 am " and report back later.
Thanks again
Edit: I couldn't wait until tomorrow so i said let's try it but something happened and now my tab is bricked ( Stuck on EEE Pad screen )
Click to expand...
Click to collapse
OK, easy come on #asus-transformer at webchat.freenode.net will try to manage something.

OMG you saved my transformer!!!
Long story short, my tablet, as of 20mins ago, was in such an awkward status:
- has su and superuser.apk in /system/xbin
- all root checker apps say I'm NOT rooted
- on stock recovery but stock images put on external SD card won't get recognized
- whenever an app requests root, it got automatically denied by SuperUser.
and I saw this post....I'm back on 9.2.17 stock now!!
Thanks a million! ln -s...genius!!

Nice exploit! I knew there was a way!

alvin612 said:
Long story short, my tablet, as of 20mins ago, was in such an awkward status:
- has su and superuser.apk in /system/xbin
- all root checker apps say I'm NOT rooted
- on stock recovery but stock images put on external SD card won't get recognized
- whenever an app requests root, it got automatically denied by SuperUser.
and I saw this post....I'm back on 9.2.17 stock now!!
Thanks a million! ln -s...genius!!
Click to expand...
Click to collapse
Did you start off with 9.2.1.21? Or just fixing your botched 9.2.1.17?

kevchaps said:
Did you start off with 9.2.1.21? Or just fixing your botched 9.2.1.17?
Click to expand...
Click to collapse
9.2.1.21.
I messed up the rooting and recovery after ota from .17 to .21
Sent from my Transformer TF101 using XDA Premium HD app

You are genius wolf
It worked . Yes Yes Yes Yes Yes
THANK YOU SO MUCH WOLF​
FYI: I copied 3 files named ( EP101_SDUPDATE, EP101-SDUPDATE, EP101SDUPDATE ) so i don't know which one worked bcuz i tried the 1st name yesterday but didn't work .

alvin612 said:
9.2.1.21.
I messed up the rooting and recovery after ota from .17 to .21
Sent from my Transformer TF101 using XDA Premium HD app
Click to expand...
Click to collapse
Great that it worked for you.
When I get a new data cable, i think I will be headed back to honeycomb.

Sorry for asking! but Is 'rooted method 1' give any benefit over using CWM to flash stock ROM?

warlord234 said:
Sorry for asking! but Is 'rooted method 1' give any benefit over using CWM to flash stock ROM?
Click to expand...
Click to collapse
Nope, I described it to show the differences between rooted and unrooted methods

Sorry for asking. If I use this method on my tf101 to roll back to HC will it solve reboot and SoD problems?

Im trying method 2 and it wont let me adb shell after reboot.

Rodriger said:
Sorry for asking. If I use this method on my tf101 to roll back to HC will it solve reboot and SoD problems?
Click to expand...
Click to collapse
It should, that depends whether you had such issues on HC. If you did not than by downgrading you should get rid of them.
steven178s said:
Im trying method 2 and it wont let me adb shell after reboot.
Click to expand...
Click to collapse
After 1st reboot? Maybe give it a try after full bootup.

wolf849 said:
It should, that depends whether you had such issues on HC. If you did not than by downgrading you should get rid of them.
Click to expand...
Click to collapse
Should I try it if flashing stock HC by CWM didn't helped solve reboots and SoDs?

Thank you very much, i'm back on 8.6.6.23 from 9.2.2.23. The only thing i had, after the flashing Android want not boot. I made a wipe and everything is ok.
Thank you again.

How to do full system backup to PC?

Before I handing in my OnePlus 6T for repair, I want to create a full system backup and reset the phone to factory defaults. Afterwards, I want to restore the original state. My phone is rooted with Magisk.
How do I do a full system backup?
What I tried:
adb backup -apk -obb -shared -all -system: This finishes, but at 5.5GB, even if compressed, the backup file is suspiciously small. According to the settings app, my phone uses 55GB of storage, so ten times that!
OK, so I thought adb root needs to be run before. However, that doesn't work: adbd cannot run as root in production builds
So I installed the adb_root module. But now when I run the above backup command, then it simply quits. No backup is created.

feklee said:
Before I handing in my OnePlus 6T for repair, I want to create a full system backup and reset the phone to factory defaults. Afterwards, I want to restore the original state. My phone is rooted with Magisk.
How do I do a full system backup?
What I tried:
adb backup -apk -obb -shared -all -system: This finishes, but at 5.5GB, even if compressed, the backup file is suspiciously small. According to the settings app, my phone uses 55GB of storage, so ten times that!
OK, so I thought adb root needs to be run before. However, that doesn't work: adbd cannot run as root in production builds
So I installed the adb_root module. But now when I run the above backup command, then it simply quits. No backup is created.
Click to expand...
Click to collapse
Do you have TWRP on your device? If so, just backup everything with it and copy the TWRP backup folder elsewhere.
ALSO (with the help of PC) copy the /sdcard (emulated sdcard; media storage). TWRP itself does not do that.
Done.
The reinstall TWRP in your device and restore everything. And copy back /sdcard
By the way, this is not Magisk related. For more information, better ask in your device specific section.

wilsonhlacerda said:
Do you have TWRP on your device? If so, just backup everything with it and copy the TWRP backup folder elsewhere.
Click to expand...
Click to collapse
Thanks for pointing me in the right direction! Here's how I proceeded in the end:
Downloaded TWRP for my device.
Rebooted the phone into fastboot mode by pressing volume down plus the power button and following the menu displayed on the phone. Note the process of entering fastboot mode varies from phone to phone.
Connected the phone to the PC, then booted TWRP from the Windows command line (cmd.exe):
Code:
fastboot boot twrp-3.4.0-0-fajita.img
I installed fastboot as part of the Chocolatey package adb.
In TWRP, I entered my password, then selected Backup.
Backed up all partitions to internal storage. See also the TWRP FAQ: What should I back up in TWRP?
Note that not all partitions need to be backed up, and in fact, according to the TWRP FAQ, it may be a bad idea to restore certain partitions. Still, it doesn’t hurt to have the backup of all of them.
Not included is /data/media (internal storage). This needs to be backed up separately. See the TWRP FAQ: What is EXCLUDED from a TWRP backup?
With TWRP running, I connected the phone via USB to my PC. Then I moved the following folder to my PC, which contains the TWRP backup of the phone:
Code:
This PC\OnePlus A6013\Internal Storage\TWRP
This step is not strictly necessary as in the following step I did back up the entire internal storage. However, it makes the next step execute faster as less data needs to be copied. The next step does not give feedback about progress.
For backing up internal storage I decided on the method found in Tadej Janež’s article Backing up Android's /data/media (i.e. internal storage) using adb and TWRP. From the Windows command line I ran:
Code:
adb exec-out "tar --create data/media/0 2>/backup-errors.txt | gzip" >internal_storage.tar.gz
After completion, to check for errors, I ran (no errors):
Code:
adb shell cat /backup-errors.txt
To leave TWRP, I rebooted the phone. Note that it is not necessary to install TWRP.
Restoration still needs to be tested.
By the way, this is not Magisk related. For more information, better ask in your device specific section.
Click to expand...
Click to collapse
I thought there was a Magisk way of doing a full system backup, making use of root privileges. Now I know better.

you can also try Migrator of vr25.
{Mod Edit: TG link removed}
https://github.com/VR-25/migrator

Just use Migrate
End of story.....

datsoy said:
you can also try Migrator of vr25.
{Mod Edit: TG link removed}
https://github.com/VR-25/migrator
Click to expand...
Click to collapse
Thanks! This looks nice, but I already backed up with TWRP. The idea was to get a 1:1 binary backup, and the backup did work. However, I am running into issues during restore of the Data partition: Error 255 when trying to restore Data