The transformer is the first android device I've owned and I bought it off someone who had previously rooted it. Ive had it for a week and finally decided I wanted to unroot it. So i did my homework, got the adb up and running and followed this thread: http://forum.xda-developers.com/showthread.php?p=14050214&posted=1#post14050214 as a guide for unrooting it. Well like I said there I... pushed the asus firmware blob with no problem then typed "adb shell" to get to root and copied and pasted "dd if=/data/local/blob of=/dev/block/mmcblk0p4" and pressed enter. Upon reboot, I saw the progress bar fill up and then the Transformer rebooted. Now it is in a continual loop where it restarts (and my windows xp recognizes it), makes a click noise, shows the 'EEE Pad-with-the-ASUS-logo-below' start up screen, then after about ten seconds restarts to the home screen, then repeats the process all over again. If i try to start in recovery mode it attempts it enter it (shows a progress bar), then switches to an image of a triangle with an orange exclamation point in it next to the android logo. I seriously think I'm fuc*ed. I knew I shouldn't have tried this. AND I REALLY NEED HELP! please I'm begging anyone. I've only had the thing for a week!
Were you on a custom rom before trying to revert or just rooted stock?
Have you tried wiping data? You can hold volume down + power an in 5 seconds it will suggest wipe the data. But before that you should better try "adb shell" while your device in boot loop and root device again to fix it or "adb logcat" to find out what's broken. It will not work if you wipe your data as adb will be disabled, which is your best friend now. You are pretty close to brick.
Sent from my Transformer TF101 using Tapatalk
lordgodgeneral said:
Were you on a custom rom before trying to revert or just rooted stock?
Click to expand...
Click to collapse
Yeah, MoDaCo Custom Rom the latest version...
Thats probably the problem. I don't know if the stock recovery plays well with custom roms. Did you make a nandroid after you rooted before you flashed madaco? It may be best to reflash the CWM blob and restore to as close to stock as you can before reflashing the stock recovery blob.
ivan.volosyuk said:
Have you tried wiping data? You can hold volume down + power an in 5 seconds it will suggest wipe the data. But before that you should better try "adb shell" while your device in boot loop and root device again to fix it or "adb logcat" to find out what's broken. It will not work if you wipe your data as adb will be disabled, which is your best friend now. You are pretty close to brick.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
Well it won't stay on long enough for me to try anything. My computer is recognizing it as new hardware when it boots as an Asus Android MTP Device. I have all the drivers installed so no problem there, or at least there shouldn't be. But when I attempt to use adb to "see" the connected devices by typing "adb devices" in the prompt its returning a blank:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Eric Moss>CD C:\AndroidSDK\platform-tools
C:\AndroidSDK\platform-tools>adb devices
List of devices attached
After I determined adb was not finding the device. I tried to wipe datam but no luck...this was last night. I think I'm screwed.
lordgodgeneral said:
Thats probably the problem. I don't know if the stock recovery plays well with custom roms. Did you make a nandroid after you rooted before you flashed madaco? It may be best to reflash the CWM blob and restore to as close to stock as you can before reflashing the stock recovery blob.
Click to expand...
Click to collapse
Yeah I have the nandroid backup on my computer right now and on my microSD, but it was taken before I updated the custom ROM to its latest versioun. I bought the Transformer from someone who already rooted it so I didn't have the opportunity to create a nandroid backup pre-rooting. Problem is when I boot into recovery mode all I get is a grayed out progress bar for a few seconds at most, and then the image of the exclamation point within the triangle pops up. I cant even access CWM in order to reflash it...
I guess about the only other thing you can try is to unpack the update on your micro sd card (manually apply the update), and see if rebooting into the stock recovery picks up the asus update and applies it
lordgodgeneral said:
I guess about the only other thing you can try is to unpack the update on your micro sd card (manually apply the update), and see if rebooting into the stock recovery picks up the asus update and applies it
Click to expand...
Click to collapse
Tried that too...still get the exclamation point. It's like it doesn't even recognize anything on the MicroSD.
HOw about booting into clockwork recovery from your microsd card? Then loading a rom.
thaddyusmaximus said:
HOw about booting into clockwork recovery from your microsd card? Then loading a rom.
Click to expand...
Click to collapse
With the CWM zip file on my microSD and attempting to boot into recovery, I still get the exclamation point. It's booting into the stock recovery mode instead of CWM...why? I do not know. Does it matter what file system the card is using, ie FAT, FAT32, etc.
Not sure what's going on with the boot loops.
I reset mine following steps 6-11 (what I wrote in the other thread) and had no problem. Might be something to do with the latest firmware.
The only thing I did different (and should have mentioned) was to restore the original nandroid you made right after rooting.
Not sure if it'll help but try using the 8.2.3.9 firmware. Extract and rename US_epad_user-8.2.3.9.zip to EP101_SDUPDATE.ZIP and put it in the root of your microsd. Power off the transformer and reboot. See if it applies. If it doesn't try going to recovery and see it applies there. Other than that not sure what could be done. Maybe wait for someone who knows more about Android to reply.
http://www.megaupload.com/?d=7MHBZY46
http://forum.xda-developers.com/showpost.php?p=13365642&postcount=105
I got stuck the first time I did mine too this way.
Make sure you hold down vol down + power until you see the eeepad logo then let go of power but keep holding down.
It should give you a little writing at the top to press vol up for recovery and you have 5 seconds to do it.
Otherwise it'll just sit at the exclamation point.
Let us know if that helps
jrizk07 said:
I got stuck the first time I did mine too this way.
Make sure you hold down vol down + power until you see the eeepad logo then let go of power but keep holding down.
It should give you a little writing at the top to press vol up for recovery and you have 5 seconds to do it.
Otherwise it'll just sit at the exclamation point.
Let us know if that helps
Click to expand...
Click to collapse
Yeah I get to the point where i get the writing at the top that says press vol up for recovery. I press the volume up button and get an image of a grayed out progress bar for a few seconds. That image then jumps to an image of the Android robot logo with an exclamation within a triangle next to it. I have another working transformer with me (not the one I am trying to bring back to stock), and when I boot to recovery mode I get the exact same greeting, so the unrooted one is obviously reacting in the expected manner. If I put anything on the micro sd card, such as updates, or cwm, the tablet I am attempting to unroot does not recognize it. I'm guessing because it lost root during the unrooting process...not sure though.
I'm not expert, but what I think needs to be done is this:
Take an official ASUS blob. Unpack the blob to get each specific partitions' data. Repack (if needed?) each separate partition as a blob (much like our CWM_BLOB which is just the recovery). Then, in theory, you could use 'dd' to write the partitions back to their respective partition (mmcblk0p7 appears to be /system, for example).
Flashing the ASUS zip in CWM fails on assert stuff. Using the entire blob and dd back to /dev/block/mmcblock0p4 doesn't work because you are trying to write over 500MB of data into the recovery partition which I am sure isn't that large.
Partitions:
Code:
cat /proc/partitions
major minor #blocks name
179 0 31256576 mmcblk0
179 1 524288 mmcblk0p1
179 2 542208 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 542208 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 512 mmcblk0p6
179 7 29616640 mmcblk0p7
179 8 7772160 mmcblk1
179 9 7771136 mmcblk1p1
/proc #
In short: The asus blob contains several partitions, and needs to be split out and flashed separately.
Edit: By the way sorry, but I don't think this will help you. You would need access to 'dd' on the eeePad.
sirmx said:
I'm not expert, but what I think needs to be done is this:
Take an official ASUS blob. Unpack the blob to get each specific partitions' data. Repack (if needed?) each separate partition as a blob (much like our CWM_BLOB which is just the recovery). Then, in theory, you could use 'dd' to write the partitions back to their respective partition (mmcblk0p7 appears to be /system, for example).
Flashing the ASUS zip in CWM fails on assert stuff. Using the entire blob and dd back to /dev/block/mmcblock0p4 doesn't work because you are trying to write over 500MB of data into the recovery partition which I am sure isn't that large.
Partitions:
Code:
cat /proc/partitions
major minor #blocks name
179 0 31256576 mmcblk0
179 1 524288 mmcblk0p1
179 2 542208 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 542208 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 512 mmcblk0p6
179 7 29616640 mmcblk0p7
179 8 7772160 mmcblk1
179 9 7771136 mmcblk1p1
/proc #
In short: The asus blob contains several partitions, and needs to be split out and flashed separately.
Edit: By the way sorry, but I don't think this will help you. You would need access to 'dd' on the eeePad.
Click to expand...
Click to collapse
Yeah I cant access DD without using ADB correct? And I am having problems with that so...This seemed a little over my head anyways. But thanks for trying!
fullthrottleenergy said:
Not sure what's going on with the boot loops.
I reset mine following steps 6-11 (what I wrote in the other thread) and had no problem. Might be something to do with the latest firmware.
The only thing I did different (and should have mentioned) was to restore the original nandroid you made right after rooting.
Not sure if it'll help but try using the 8.2.3.9 firmware. Extract and rename US_epad_user-8.2.3.9.zip to EP101_SDUPDATE.ZIP and put it in the root of your microsd. Power off the transformer and reboot. See if it applies. If it doesn't try going to recovery and see it applies there. Other than that not sure what could be done. Maybe wait for someone who knows more about Android to reply.
http://www.megaupload.com/?d=7MHBZY46
http://forum.xda-developers.com/showpost.php?p=13365642&postcount=105
Click to expand...
Click to collapse
That's seems the only option left. Theoretically, it is possible to restore using nvflash if you manage to get sbk key from Asus support, but this is completely unexplorered territory for Transformer. I recovered my GTablet this way. Try to contact Asus support?
Sent from my Transformer TF101 using Tapatalk
Looks like you still have a chance:
http://forum.xda-developers.com/showthread.php?t=1093403
Make sure you did the right thing with the sdcard update zip, check file name and extension.
Sent from my Transformer TF101 using Tapatalk
You have to dl stock fw and name it in a specific way in microsd root and use stock recovery to flash. There is a tut about unrooting in dev section
Sent from my Transformer TF101
Related
I hope my post will help somewhat those buddies who had the same problem or who will probably have this problem in future.
I had the problem that my gtablet couldn't power on after I did Nvflash. I'd been frustrated in the past week for searching the internet to find the way out.
The similar problem that tcrews had. (http://forum.xda-developers.com/showthread.php?t=903684)
Also some posts I browsed:
http://forum.xda-developers.com/showthread.php?t=999287
http://forum.xda-developers.com/showpost.php?p=10951417&postcount=1
http://forum.xda-developers.com/showthread.php?t=927006
http://forum.xda-developers.com/showthread.php?t=971608
http://forum.xda-developers.com/showthread.php?t=938706
I am grateful to tcrews and a lot of other buddies for their inputs which saved me lots of time, though i didn't find a right solution from their posts. Acidburn89's solution in tcrews's post (page 9) didn't work out for me either.I don't know whether tcrews solved his problem in acidburn89's method.
I tried all the methods I could find and nothing worked out for me. The only way I can turn the tablet on is to follow tcrews's post on rebooting the tablet by using nvflash (nvflash --bl bootloader.bin --download 9 recovery.img --go)
Some background of bricking my gtablet:
1.my gtab had CWM0.8.and was running rom "zpad clean 3.0" (before that it was TNTL, not any problem)
2.one week ago, I was trying to flash a rom from a chinese website, which was modified from the official malata zpad rom. This was the problem started from. After flashing (nvflash method),the tab was rebooting and stuck at "Tegra II" logo and couldn't never start with the new rom. At this moment, i could still power on and off the tab.
3.next I flashed my tab by following this link (http://forum.xda-developers.com/showthread.php?t=861950) After flashing it, the tab couldn't not reboot, and could not power on. Every time I pressed the power button, it just went to the APX mode authomatically
(with black screen).Only using the above-mentioned method (from tcrews) I could start the tab.
The solution I finally tried out: (Take out your sdcard from the tab if you have one in it)
1.Have these two files ready: recovery-stock.img (download the attached recovery-stock.zip and change zip to img), and original gtablet update.zip. I copied this original update.zip file from my gtab and saved in my pc, i think you can also find links in this forum for the original gtablet roms,like this http://forum.xda-developers.com/showpost.php?p=9837354&postcount=3 (not sure whether these are same as I extracted from my gtab originally, if not working, I can upload my rom for downloading)
2.Copy recovery-stock.img into the nvflash folder.
3.Start the tab by nvflash (tcrews' method)
4.Mount/Activate USB conncetion, and copy the original update.zip into the tablet internal sdcard.
5.(Not sure this step is a must or not). Download cwmod-internal.zip in the line http://forum.xda-developers.com/showthread.php?t=865245, extract it and copy the folder "recovery" including the command file to the sdcard.
6.Power off the tab.
7.Power on to make sure you enter APX mode (you will see the black screen, but hear a bing sound)
8.Type in the Dos Command: nvflash --bl bootloader.bin --download 9 recovery-stock.img --go
9.Press and hold the Volume + on the Gtablet and press enter on the PC to execute the above line. You will see it starts to installing the original rom..(about 3 minutes)..and then power off autmotically after finishing flashing ! Dont worry.
10.Repeat step 7 and 8, and press enter (do NOT hold volume +!)
11.The tab will start to the TnT like the original one you had, and Magic now: you can turn off and turn on the tab NORMALLY!!
I tried this method with and without CWM. Both worked. So don't worry whether you tab has CWM or original recovery. My advice: flash your favorite rom using sdcard method instead of nvflash. If you want to nvflash it, save all the files we have used for possilbe repeation of our above job to get your tab back to life!!
I've received a lot of information and help from xda-development before, and hope my first post could contribute to our community a little bit.
Just noticed that idocinthebox has the same idea of correcting recovery.img in this post:
http://forum.xda-developers.com/showthread.php?t=994046
Master
Wow. I followed every instruction to a 'T' and was bricked for the past 6 hours with the APX boot loop.
Finally I stumbled across your thread and was 'reborn' into my G Tablet.
Thank you so much for taking the time to post this. It saved me from wasting even more sleep. (smile)
Well done! If this helps anybody mash the thanks button ;-) ^^^^^^^^^^^
Exact same issue
Can you provide your stock update.zip file? I have not been able to find a file that works for me. So far I have repeated this process many times with many update.zip fules but its still wont start on its own.
I can fin a update.zip.... can you posted here?
Thanks.
I follow this thread but still my gtab is power on APX (only). I was using the stock 3588 and went to the new 4349... start to having issues decided to go back to 3588 using the nvflash. it worked at the first time (until I had the tablet on) As you turned of and turned on, just a black screen (apx) and the only way to get it back is running the nvflash again but if I turned off have to do it again.
Please help!!!!
I can't figure it out on my own.
The solution I finally tried out: (Take out your sdcard from the tab if you have one in it)
1.Have these two files ready: recovery-stock.img (download the attached recovery-stock.zip and change zip to img), and original gtablet update.zip. I copied this original update.zip file from my gtab and saved in my pc, i think you can also find links in this forum for the original gtablet roms,like this http://forum.xda-developers.com/show...54&postcount=3 (not sure whether these are same as I extracted from my gtab originally, if not working, I can upload my rom for downloading)
*** could you posted your original (stock rom) update.zip? The one above mention is not in zip format. I did a zip format but still not working.
2.Copy recovery-stock.img into the nvflash folder. (i did that)
3.Start the tab by nvflash (I did that)
4.Mount/Activate USB conncetion, and copy the original update.zip into the tablet internal sdcard.
*** the only way I could put the update.zip in the internal sdcard on the tablet was after nvflash the tablet power up, then I plug a usb drive (with update.zip in it) and copy to the internal sdcard... i did not plug the tablet to the computer.
5.(Not sure this step is a must or not). Download cwmod-internal.zip in the line http://forum.xda-developers.com/showthread.php?t=865245, extract it and copy the folder "recovery" including the command file to the sdcard.
*** I did that the same way above mention from a usb drive.
6.Power off the tab.
7.Power on to make sure you enter APX mode (you will see the black screen, but hear a bing sound)
8.Type in the Dos Command: nvflash --bl bootloader.bin --download 9 recovery-stock.img --go
9.Press and hold the Volume + on the Gtablet and press enter on the PC to execute the above line. You will see it starts to installing the original rom..(about 3 minutes)..and then power off autmotically after finishing flashing ! Dont worry.
10.Repeat step 7 and 8, and press enter (do NOT hold volume +!)
11.The tab will start to the TnT like the original one you had, and Magic now: you can turn off and turn on the tab NORMALLY!!
6,7,8,9,10,11 **** I did all but at the end still my tablet only work with nvflash unless I never turned off!!!
that download is corrupt...
Err it's the img ranamed... by bad..
Naysses and jettajon:
I uploaded the original update.zip I extracted from my G-tab. Try it to see whether it can help u.
w w w.mediafire.com/?fywhca6fi514toq
(remove space between "w"s)
I have the same problem, however your solution didn't fix it...Not sure what went wrong but I followed your directions exactly
Citi said:
I have the same problem, however your solution didn't fix it...Not sure what went wrong but I followed your directions exactly
Click to expand...
Click to collapse
I ran across this post http://forum.xda-developers.com/showthread.php?t=1010659 which says that the BCT part of the nvflash isn't the same for all the GTablets and that's my experience.
I couldn't get nvflash_gtablet_2010110500.zip (from the dropbox repository of nvflash files) to work, but nvflash_gtablet_46_2010112600.zip worked fine.
The problem was that I couldn't get CM7 installed on my GTablet, but then I hacked the gtablet.cfg file to swap partitions 7 and 8 by merely cutting and pasting the partition 8 (name=OGO stuff) and putting it before the partition 7 (name=BLO stuff) to match the order of the gtablet.cfg in nvflash_gtablet_2010110500.zip.
Now CM7 has installed and seems to be working fine for me.
BTW- I didn't nvflash the CWM recovery since I was trying to minimize the number of things I was messing with. I assume it'll work, but I already had CWM installed on the internal emmc (SDCARD2) so really didn't even need to nvflash it.
Nope, I have tried both files and neither worked for me
kaluna00 said:
Wow. I followed every instruction to a 'T' and was bricked for the past 6 hours with the APX boot loop.
Finally I stumbled across your thread and was 'reborn' into my G Tablet.
Thank you so much for taking the time to post this. It saved me from wasting even more sleep. (smile)
Click to expand...
Click to collapse
guobug you are a hero
same thing happened to me
and because of you it works!!!
( followed the steps and used your updat.zip)
BUT I have another problem
when I tried to install CW
it says "Can't open sdcard/recovery.log"
now I dont know what to do
because I want to install another rom
I think there is something corrupted in the device after apx boot loop
You are a life saver. Worked like a charm. Have been reading through 50 million threads the last 3 days, and happened to find this one. Absolutely amazing. Thanks.
In step 8 I don't know where to type the code in, which Dos command, the dos command window which nvflash step opened( and I didn't press enter to close that window), or I have to open a new one( or make a new .bat file with the code).
I do it and cann't see it install the original rom( "You will see it starts to installing the original rom..(about 3 minutes)..and then power off autmotically after finishing flashingtes" as you wrote in step 9)
So I still cann't fix my problem.
Please help me!
guobug said:
8.Type in the Dos Command: nvflash --bl bootloader.bin --download 9 recovery-stock.img --go
Click to expand...
Click to collapse
Do I manually open the Dos Command, or should this open on it's own... I'm opening Command Prompt, and pasting what you're saying to use. I'm getting
"nvflash is not recognized as an internal or external command, operable program or batch file."
Obviously I'm doing something wrong.
BrandonJay21 said:
Do I manually open the Dos Command, or should this open on it's own... I'm opening Command Prompt, and pasting what you're saying to use. I'm getting
"nvflash is not recognized as an internal or external command, operable program or batch file."
Obviously I'm doing something wrong.
Click to expand...
Click to collapse
That error means the command 'nvflash' is not in the path for the windows command line.
Where do you type the DOS command at? Thanks.
when I hold the volume up and hit enter on the keyboard I get a bad command prompt. What am I doing wrong?
Ok so here are the files and the process for restoring the DELL STREAK 7 WIFI ONLY using NVFLASH. This post is a collection of the info I used to restore after I went to DJ_Steves ROM but forgot to do a NANODROID backup.
AGAIN THESE ARE THE WIFI ONLY FILES!
Thanks to:
illdill for the detailed NVFlash procedure.
solidsnake66 for uploading the stock wifi files.
Chemus for the altered restore.bat file
Follow these steps and you will be back to stock.
If for some reason it fails post details of what went wrong or search the forum based on what failed for you and I assure you there is a answer out there.
I am not responsible for any damage caused by this process.
If you need to do a factory restore of any kind it will not work if your battery is below 50% so make sure your battery is charged before you start this process!
Restoring the Streak 7 using NVFlash
(Windows Only Instructions) If you’re a Linux user, you should be able to 'translate' this yourself.
This is for those who cannot use fastboot or adb. If you can successfully use these tools, DO NOT use NVFlash. You will lose all your data on your device. Do not proceed with these instructions if you are not expecting to lose all personal data on the device.
Step 1) APX Drivers – To work in NVFlash mode you need to install the drivers for the nvidia boot-recovery device. Power off your device and disconnect it from the computer. Hold down the Volume up & down buttons while plugging in the USB cable. (Or leave the USB cable attached and hold the pinhole ‘power off’, hold down the volume Up & Down and release the pinhole ‘power off’.) (The volume button seems like a rocker switch, but you can hold down both sides at once)
Your computer should now recognize the Streak 7 as an APX device. Manually install it using the nvidia boot-recovery drivers.
NVFlash
http://www.4shared.com/file/SewzEdtV/nvflash.html
Nvidia Boot-Recovery Drivers
http://www.4shared.com/file/-utyTYcJ/usbNvidiaBootdriver.html
Step 2) Install NVFlash. For ease of function simply create a folder on your C:\ drive called ‘nvflash’. Download the nvflash zip and extract it to the nvflash folder.
Step 3) Download the stock wifi files here: http://www.multiupload.com/96WH2O4OCD (Takes about 30 minutes. Use direct download via multiupload NOT THE DOWNLOAD FILE VIA RAPIDSHARE) Put these files in the C:\nvflash folder.
Step 4) Open the restore.bat file and delete everything from it. Then copy the following into that file:
HTML:
.\nvflash.exe --bct flash.bct --setbct --bl bootloader.bin --configfile flash.cfg --rawdevicewrite 0 1536 p2.img --rawdevicewrite 1536 256 p3.img --rawdevicewrite 1792 1024 p4.img --rawdevicewrite 2816 256 p5.img --rawdevicewrite 3072 1024 p6.img --rawdevicewrite 4096 256 p7.img --rawdevicewrite 9216 8192 p8.img --rawdevicewrite 17408 8192 p9.img --rawdevicewrite 25600 8192 p10.img --rawdevicewrite 33792 172032 p11.img --rawdevicewrite 205824 57344 p12.img --rawdevicewrite 263168 8192 p13.img --rawdevicewrite 271360 286720 p14.img --rawdevicewrite 558080 1048576 p15.img --rawdevicewrite 1606656 8192 p16.img --rawdevicewrite 1614848 8192 p17.img --rawdevicewrite 1623040 8192 p18.img --rawdevicewrite 1631232 8192 p19.img --rawdevicewrite 1639424 8192 p20.img --rawdevicewrite 1647616 8192 p21.img --rawdevicewrite 1655808 6103040 p22.img --rawdevicewrite 7758848 8192 p23.img --rawdevicewrite 7767040 8192 p24.img
Save and close the restore.bat file.
Step 5) Unplug your streak from the computer and power off. Hold down the Vol up and Vol down buttons and then plug in the usb cable. Your computer should recognize your device. (Note if you already left it in this state from Step 1 you do not need to do it over again.)
Step 6) Launch (double-click) the Restore.bat file from the C:\nvflash folder. This batch command will begin copying the partitions to the device. Wait patiently as your device is being restored. This will take anywhere from 30 minutes to an hour. Just be patient as it is worth it.
Once the comand prompt window disappears that means the process is complete.
Power on the device. It will take a while to load so it will stay on the dell logo. If after 5-10 minutes the dell logo is still there use the pin hold next to the sd card to power off the device.
Do a factory restore by holding down the volume up button and the power button. This will bring you to the screen where you can do a factory reset. One will be user data only and the other will be user data and internal and external tablet storage . When I did this I personally had to do both for it to work.
Finally check to see if you are still rooted using gingerbreak. If it gives you the option to unroot then unroot. Some people have had success with just the process above others still have root access after the process. Double check using gingerbreak.
********* ONLY PROCEED IF AFTER YOU COMPLETE THE PROCESS ABOVE YOU STILL HAVE CWM RECOVERY INSTALLED WHEN ATTEMPTING TO DO A FACTORY RESET ON USER DATA AND INTERNAL AND EXTERNAL TABLET STORAGE *********
So I had a buddy of mine tell me he had an issue where he was unable to get CWM Recovery removed as it still showed up when he attempted to do a factory reset.
So I did the unthinkable and rooted my device and flashed CWM recovery to my DS7(WIFI ONLY). I was unable to get it removed. I tried going to DJ_Steves ROM and I tried flashing back to stock with the process above, NO LUCK! Well about 8 hours later I finally have it figured out. I assume many people will have CWM recovery on their system and would probably run into this same issue so I did the hard work for you. Please read below:
Please continue at your own risk as I am not responsible for bricked devices or any other issues that may come from the following process.
Step 1) Download the two files below and extract them to a folder on your desktop. If possible extract them to a new folder with the file names "NVFlashStep1" for the first file and "NVFlashStep2". This ensures you execute the correct files in the correct order.
NVFlashStep1:
http://www.multiupload.com/VWS33DCNPO
NVFlashStep2:
http://www.multiupload.com/8R43CZ3GCC
Step 2) Power off your device and ensure the usb is disconnected from the computer. Hold down the Vol. Up and Volume Down buttons at the same time while plugging the usb cable back into the computer. The computer should recognize your device.
Step 3) Open the "NVFlashStep1" folder and click on the "restore.bat" file. This should bring up a cmd prompt window and the files should begin to transfer. The cmd prompt window will disappear when the process is complete.
Please be patient as this will take anywhere from 40mins to an hour or more depending on the speed of your usb.
Step 4) Use the pin hole next to the sdcard slot to turn the device off. Hold the Vol. Up and power button to enter recovery. Select factory reset(User data and internal and external storage.) This should bring you to the recovery menu where you can only hold down power to do a factory wipe or hit Vol. Up to power off. If this is the case then you are ready for the next step.
If for some off chance you don't get this screen and you still get booted into CWM recovery then make sure you completed all steps correctly as this has been verified numerous times on two separate devices.
Step 5) Open up the folder "NVFlashStep2" and click the "restore.bat" file. The files should begin transferring over. Now this is where your patience will be NEEDED. This process can take anywhere from 1-2 hours depending on the speed of your usb. So make sure you are prepared and ready to wait around. The cmd prompt window will disappear when the process is complete.
Step 6) After everything is completed...Use the pin hole button next to the sdcard slot to power off your device. Then simply hold the power button down until the dell logo appears. The first boot may take 3-5 minutes.
- If it takes longer simply go into recovery by hold the Vol. Up and power button and selecting factory restore(User data and internal and external storage) this should bring you into the recovery menu where you can only hold down power to do a factory wipe or hit Vol. Up to power off. Hit the power button and wait for the factory wipe to finish.
- Once completed reboot and you have a stock Dell streak 7 wifi only no CWM recovery, no root, just plain old stock.
If this works please give thanks to all who contributed to this post.
I'm going to give it a try.. It will be after work though. Thanks for all the effort! It is appreciated..
I have used this site for a while to help me with tech stuff and I finally joined up. I know how it is to love technology so much and I know how it is to hate it : ) so if I can help others out I will. Keep me updated on if it works for you.
Well, it won't boot into anything but CWR and then it shows up in device manager as Android Composit ADB Interface.
I owe you big time! I kept messing with it till I got it to show up in device manager where I could install the nv boot recovery drivers. Then ran the restore.bat and 40 minutes later.. BAM! It is restored. I can't thank you enough! I'm about to leave with the guard for Afghanistan and this streak will be my life line. Thank you!
Rword69 said:
I owe you big time! I kept messing with it till I got it to show up in device manager where I could install the nv boot recovery drivers. Then ran the restore.bat and 40 minutes later.. BAM! It is restored. I can't thank you enough! I'm about to leave with the guard for Afghanistan and this streak will be my life line. Thank you!
Click to expand...
Click to collapse
Glad this worked for you. Just to be clear when you boot into recovery and attempt to factory restore(User and internal/external data) it no longer goes into the cwm recovery but instead it now goes into the stock recovery?
On a more important note thank you for your service. I hope you have a safe tour.
Sent from my Dell Streak 7 using xda premium
Other than not being able to boot into any recover.. it works fine. I'm new to this Streak. I know how to do most of this on my Droid 1. This just a little different.
Well, 2 seconds using search I found how to do it. Yeah it boots into "starting Fastboot USB download protocol".. Is that what you meant?
Rword69 said:
Other than not being able to boot into any recover.. it works fine. I'm new to this Streak. I know how to do most of this on my Droid 1. This just a little different.
Click to expand...
Click to collapse
When you hold the vol. up and the power button you dont get any recovery screen? Yeah the streak is different to me as well just learning as I go. If you are unable to boot into recovery do a factory reset from the settings>privacy>factory data reset. Then attempt to boot to recovery again. If you can't boot to recovery I don't think the honeycomb uodate from dell will show up in when they send it out.
Sent from my Dell Streak 7 using xda premium
The instructions to get to that screen said hold vol down button.. That is where I got that Fastboot USB download protocol menu. When I did your suggestion and did vol up I got the recovery menu, not CWM. Very cool. Thanks again!
It isn't rooted now though which is fine. I don't think I will bother re-rooting it this time unless I run into something that requires it..
Rword69 said:
It isn't rooted now though which is fine. I don't think I will bother re-rooting it this time unless I run into something that requires it..
Click to expand...
Click to collapse
Yeah this process will ensure that the dell OTA honeycomb update will come to you. The OTA process checks the recovery image at least that is how I understand it. No expert on Android but having 100% stock is best bottom line.
Sent from my Dell Streak 7 using xda premium
Yeah, I can tell you I won't be putting rom manager on here.
Rword69 said:
Yeah, I can tell you I won't be putting rom manager on here.
Click to expand...
Click to collapse
Yeah same here : ) I think I will deal with the stock rom for a while.
Sent from my Dell Streak 7 using xda premium
So, these are the instructions for the wi fi version. What are the instructions for the t mobile version?
Sent from my VS910 4G using XDA App
I know this sounds dumb, but I cant extract the files from the stock ROM to be able to roll back. Can someone please inform me????
After reflash i get different service tag and mac address! why?
konikg said:
After reflash i get different service tag and mac address! why?
Click to expand...
Click to collapse
I noticed the same thing...is there a utility to reset the service tag? Or can re-flashing with another ROM take care of that? I tried to flash to the latest HoneyStreak, but the service tag still shows up incorrectly (not sure about the MAC, but I would think that wouldn't change)
Got stuck in the cwm loop, panic'd because i have sold my streak and was returning it back to stock
Found this thread and it saved my life
thank you
chiefy009 said:
Got stuck in the cwm loop, panic'd because i have sold my streak and was returning it back to stock
Found this thread and it saved my life
thank you
Click to expand...
Click to collapse
Was in a similar situation but I wasn't stuck on the loop.
I tried restoring from honeystreak originally and all I could find were the tmobile images. I tried restoring using those and was successful but still had CWM and was running a the tmobile image on a wifi only DS7. After a couple nights of digging, I found the wifi only files but still had the problem with CWM (not in the loop but could not remove it). I'm restoring now to trade the device and I ran into this thread. I noticed there are a couple more img files than I had originally (p23-p24) and when I was done restoring, CWM was gone!
In short, thanks for this thread. Now it's pretty much factory restored.
Hi. I dropped my TF a few days ago and now the power button stops working. I want to RMA it but it is rooted. Is there any way to unroot the TF without using the power button? thanks.
Get Reboot to Recovery (or from the market here or use the donate version to thank them for getting you out of your jam).
Just curious, where would you RMA it in IDN? How much was it there in Rp?
Thanks for the info. Do I need to have CWM installed first? I didn't install CWM before and I don't think I can do it now. (sorry for noob questions) I bought it in the US. Do they have international warranty or something? I don't think I can spend that much time away from my TF. They sell it here for US $699 net price.
Warranties don't usually apply outside the country of sale, but I haven't read the terms on the ASUS one so I could be wrong. I am certain it doesn't cover physical damage from being dropped, though. I've heard other stories on here that they sent in a damaged device and ASUS offered a repair quote, so you might get lucky and be offered a new bezel with buttons cheap.
I'm sorry, but does it need CWM? and how do I install it without the power button?
Check out the unroot thread on the dev section. Hope it works out.
Even if you did have cwm recovery, you need a working power button to make selections in cwm.
Sent from my Transformer TF101 using Tapatalk
Anything that uses recovery or nvflash won't work because of the power button... you need the staging partition!
You can do it by copying a stock blob to the staging partition. The TF will do all the flashing for you
You do need adb and root, but no power buttons.
Here's the 1 click method!
Be sure ADB is installed on your PC. There are threads on how to do this all over XDA.
Be sure your battery is charged.
Download a stock firmware from the ASUS website. Be sure to match your country code (WW, TW, US, etc.)
Unzip the firmware. It should create an ASUS/Update/some.zip. Unzip the some.zip file too.
If this went well you should be looking at a giant blob! ~500M or so. No kidding- the file will be called "blob"
Use ADB to push the blob to your TF or just copy it to your SD card. Your choice.
Code:
adb push blob /data/local/
Connect your TF to your PC and type "adb shell" to start a shell.
Type these commands into the shell
Now the magic happens....
Code:
su
dd if=/data/local/blob of=/dev/block/mmcblk0p4
reboot
Be sure to get the dd command correct. The last three characters are zero-pee-four. If you pushed/saved the blob somewhere else, you'll have to adjust the "if=" to match the path.
Your TF should reboot and it will flash the stock rom. You'll see a blue progress bar that will flash quickly, but still take longer than you think it should. Be patient. Your TF will reboot automatically.
You can now delete the blob file from your TF.
Thanks. I'll try and let you know.
Did this work for you? I'm in the same boat. I have CWM and latest Revolver installed. Would there be any other steps besides those mentioned here if I have CWM installed?
gee one said:
Anything that uses recovery or nvflash won't work because of the power button... you need the staging partition!
You can do it by copying a stock blob to the staging partition. The TF will do all the flashing for you
You do need adb and root, but no power buttons.
Here's the 1 click method!
Be sure ADB is installed on your PC. There are threads on how to do this all over XDA.
Be sure your battery is charged.
Download a stock firmware from the ASUS website. Be sure to match your country code (WW, TW, US, etc.)
Unzip the firmware. It should create an ASUS/Update/some.zip. Unzip the some.zip file too.
If this went well you should be looking at a giant blob! ~500M or so. No kidding- the file will be called "blob"
Use ADB to push the blob to your TF or just copy it to your SD card. Your choice.
Code:
adb push blob /data/local/
Connect your TF to your PC and type "adb shell" to start a shell.
Type these commands into the shell
Now the magic happens....
Code:
su
dd if=/data/local/blob of=/dev/block/mmcblk0p4
reboot
Be sure to get the dd command correct. The last three characters are zero-pee-four. If you pushed/saved the blob somewhere else, you'll have to adjust the "if=" to match the path.
Your TF should reboot and it will flash the stock rom. You'll see a blue progress bar that will flash quickly, but still take longer than you think it should. Be patient. Your TF will reboot automatically.
You can now delete the blob file from your TF.
Click to expand...
Click to collapse
So this can be used as a way to return a tablet to stock or potentially un-softbrick a tablet?
Sent from my DROIDX using XDA App
This will flash the stock firmware in the blob. If you are softbricked, it might work if you can get to adb.
gee one said:
This will flash the stock firmware in the blob. If you are softbricked, it might work if you can get to adb.
Click to expand...
Click to collapse
Is there any mode that adb does work on? (From Clockwork, APX mode(?), etc.)
Sent from my DROIDX using XDA App
You might try using the dock?
I'm not sure if i can actually select anything with the dock(like using the power button), but if i boot into cwm with the dock connected i can use the arrow keys to scroll up and down. Worth a look anyway.
infazzdar said:
Is there any mode that adb does work on? (From Clockwork, APX mode(?), etc.)
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
If it's enabled, you can use adb in the regular system and recovery. It won't work in apx mode/nvflash.
The tricky part is that sometimes, it's not enabled, and that time is usually when you need it to be. You can enable through the system settings or by changing flags in the boot or recovery images.
Ok, so I used this method to root, http://forum.xda-developers.com/show...&postcount=310
I then took a nandroid immediately after rooting. I then installed the latest version of CWM 6.0.1.3 (I used Rom Manager to install it which may have been my mistake).
I was then going to be in the process of installing a custom ROM so I went to wipe data / factory reset, but it just sat there and did nothing. I then tried to boot and I got stuck at the ASUS screen (second screen after the EEPC pad page thingy). It just sits there.
CWM doesn't recognize anything (can't mount SD card so I can't restore whatsoever.. When I try to restore it says:
E:unknown volume for path [/sdcard]
E:Can't mount /sdcard
I'm not quite sure what to do next. I obviously messed up somewhere. I'm guessing ROM manager didn't flash CWM correctly. I'm newer to Android and this is only my second device that I'm attempting to flash... not sure what to do. Please help if you can, if not, guess I'll be buying the new google tablet... shouldn't have done this before my trip to hong kong heh.
-----
EDIT: I can't cold boot either
So I can get into APX mode, I downloaded nvflash and ran the download.bat, but still nothing, it just sits at the eee pad screen and does nothing.
I tried this: http://www.youtube.com/watch?v=VMHXeYMgPy4 (with the TF101), when I run the download.bat, it just disconnects the device and nothing happens.
When I run that bat file manually I get this error message.
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
patmann03 said:
I tried this: http://www.youtube.com/watch?v=VMHXeYMgPy4 (with the TF101), when I run the download.bat, it just disconnects the device and nothing happens.
When I run that bat file manually I get this error message.
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
Click to expand...
Click to collapse
I'm guessing this means my version is too new for AXP recovery... darn that's no good. I can't tell what version my transformer is, the sticker on the back is too hard to read (maybe because it's really late), and all of the other stickers I pealed off today... heh.
I tried getting adb to work, but I'm not quite sure how. I believe I have the drivers installed, but I have a feeling I messed up the SD card on my device so much that even adb can't recocgnize it.
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/ I followed this guide..
Ok, I can get into adb mode and can push items to my device, anyway to restore this way?
Ok, flashed a new recovery. I'm able to access my sd card (external). I found my restore, however, when I went to restore my backup it restored the system, but got an error formatting data...
Used this tool to install new recovery. http://www.androidauthority.com/tra...-3-root-custom-recovery-one-click-tool-97173/
trying to use the same too to unroot...
Get this..
Run? Close if you want to cancel.
Press any key to continue . . .
List of devices attached
3889240415f5497 recovery
If you see your device here this will work, if not fix adb.
Press any key to continue . . .
running fix...
dd: writing '/dev/block/mmcblk0p3': No space left on device
4097+0 records in
4096+0 records out
2097152 bytes (2.0MB) copied, 0.512550 seconds, 3.9MB/s
rebooting tab, if at any step it doesn't reboot turn off and turn back on
Once back into an adb possible state continue...
Press any key to continue . . .
Pushing new recovery...
1328 KB/s (4599884 bytes in 3.380s)
Running wolf's exploit...
mv: can't rename '/data/local/tmp': No such file or directory
Going...
ln: /data/local/tmp: No such file or directory
Done!
Now lets reboot your TF again...
Continue when back into ADB again...
Press any key to continue . . .
Ok, this saved my ass. http://forum.xda-developers.com/showthread.php?t=1688012
Hi. I wanted to update my tablet, so I've downloaded CROMBi-KK rom and the newest TWRP recovery. I've put all the files on microsd and installed the recovery. Then I wanted to wipe everything from my tablet, so I went to wipe, did the factory reset and started the data partition wipe. Nothing was happening after a long time, so I did a stupid thing and reset the device. Since then I can't mount /data and Internal storage. Is there a way to format the whole device and restore the filesystem or something? I have deleted the data and sdcard folders from the root and made them again. Didn't help. Please let me know how to fix it.
LEGOracer69 said:
Hi. I wanted to update my tablet, so I've downloaded CROMBi-KK rom and the newest TWRP recovery. I've put all the files on microsd and installed the recovery. Then I wanted to wipe everything from my tablet, so I went to wipe, did the factory reset and started the data partition wipe. Nothing was happening after a long time, so I did a stupid thing and reset the device. Since then I can't mount /data and Internal storage. Is there a way to format the whole device and restore the filesystem or something? I have deleted the data and sdcard folders from the root and made them again. Didn't help. Please let me know how to fix it.
Click to expand...
Click to collapse
You may want to go back to twrp and "Format" your data partition. You must leave it alone until it finishes it job and it could take up to 4-5 hours according to some users. Please plug your device in with your AC plug in to ensure that your device is not shutting down during this format. Please capture the messages from your screen if it reports data can not be mounted. I am very sure someone here can help you out with this issue, good luck...:fingers-crossed:
If the format LMK suggested won't work due to /data not mounting, let's do some diagnostics.
Boot to recovery and check if you adb access with
Code:
adb devices
If you get a string of numbers and letters you have adb access.
To list the devices partitions run this:
Code:
adb shell cat /proc/partitions > partitions.txt
Post the resulting text file.
The Adb didn't work, so I've done it from the recovery and saved it on microsd. Maybe I don't have the right drivers, the list of devices was empty.
Code:
major minor #blocks name
179 0 31039488 mmcblk0
179 1 786432 mmcblk0p1
179 2 438272 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 835584 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 512 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 28924416 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 8192 mmcblk0p10
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
179 48 15449088 mmcblk1
179 49 15444992 mmcblk1p1
LEGOracer69 said:
The Adb didn't work, so I've done it from the recovery and saved it on microsd. Maybe I don't have the right drivers, the list of devices was empty.
Code:
major minor #blocks name
179 0 31039488 mmcblk0
179 1 786432 mmcblk0p1
179 2 438272 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 835584 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 512 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 28924416 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 8192 mmcblk0p10
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
179 48 15449088 mmcblk1
179 49 15444992 mmcblk1p1
Click to expand...
Click to collapse
That all looks good which is good ...
I think I have a good idea what is going on and a solution ....
What twrp version on you running ?
Thx Josh
TWRP 2.6.3-that3 By that http://forum.xda-developers.com/devdb/project/dl/?id=4576 - Download
LEGOracer69 said:
TWRP 2.6.3-that3 By that http://forum.xda-developers.com/devdb/project/dl/?id=4576 - Download
Click to expand...
Click to collapse
Ok, we are going to need a but more info ....
bootloader version?
A PC with adb and fastboot working ..... :good:
If you need some help with installing adb and fastboot on a windows PC take a look here .
http://forum.xda-developers.com/showpost.php?p=54946014&postcount=3
Let us know ....
Thx Josh
lj50036 said:
Ok, we are going to need a but more info ....
bootloader version?
A PC with adb and fastboot working ..... :good:
If you need some help with installing adb and fastboot on a windows PC take a look here .
http://forum.xda-developers.com/showpost.php?p=54946014&postcount=3
Let us know ....
Thx Josh
Click to expand...
Click to collapse
When I boot to the bootloader, I can see this in the left upper corner:
Code:
Key driver not found.. Booting OS
Android cardhu-user bootloader <1.00e> released by "WW_epad-10.6.1.14.10-20130801" A03
Starting Fastboot USB download protocol
I didn't get adb to work yet. I tried to install ASUS_Android_USB drivers on my PC but it doesn't want to install.
LEGOracer69 said:
When I boot to the bootloader, I can see this in the left upper corner:
Code:
Key driver not found.. Booting OS
Android cardhu-user bootloader <1.00e> released by "WW_epad-10.6.1.14.10-20130801" A03
Starting Fastboot USB download protocol
I didn't get adb to work yet. I tried to install ASUS_Android_USB drivers on my PC but it doesn't want to install.
Click to expand...
Click to collapse
Ok so we need to get this issue taken care of first ....
When you plug the tablet into your PC, in device manager does the device show up at all ?
Make sure the tab is on the same screen your showing in the code post
It does as an Unknown device.
Yes! I got the ADB and fastboot to work!
First, I've installed the Asus fastboot drivers
Then I've connected my device to the PC while being in bootloader and installed ASUS_Android_USB from the rooting thread through device manager. That's how I got the fastboot working.
Then I started the recovery and installed Universal Naked Driver the same way. That's how I got ADB working.
LEGOracer69 said:
Yes! I got the ADB and fastboot to work!
First, I've installed the Asus fastboot drivers
Then I've connected my device to the PC while being in bootloader and installed ASUS_Android_USB from the rooting thread through device manager. That's how I got the fastboot working.
Then I started the recovery and installed Universal Naked Driver the same way. That's how I got ADB working.
Click to expand...
Click to collapse
So let move on now, from the bootlaoder screen what is the output of.. (Make sure you open CMD window as admin)
Code:
fastboot devices
and from recovery what is the output of this commad ..
Code:
adb devices
Thx Josh
The result from fastboot devices is:
015d29955a1c0a10 fastboot
Click to expand...
Click to collapse
Now the adb:
List of devices attached
015d29955a1c0a10 recovery
Click to expand...
Click to collapse
@LEGOracer69
Now you need to go to the asus website and get the correct zip files for your tablet
You have a "WW" SKU this is important that you get the correct SKU ..
There will be 2 zip files we will need with a "WW" SKU ending in
14.8 & 14.10
Let me know when you get these 2 zips ..
Thx Josh
I've downloaded these files from this website. File names are: WW-epaduser10_6_1_14_10_UpdateLauncher.zip and (the same) 14_8
LEGOracer69 said:
I've downloaded these files from this website. File names are: WW-epaduser10_6_1_14_10_UpdateLauncher.zip and (the same) 14_8
Click to expand...
Click to collapse
Ok, once they are downloaded upzip one of them to its own folder then there will be another zip unzip that one as well ..
There will be a file called blob that is the one we need. rename the blob that comes out of 14.10 to
14.10.blob
and do the same for the other one, move these files into the same directory as your fastboot.exe ....
Let me know if you need any more info as of this point ....
Thx Josh
Let me know if you need any more info as of this point ....
Thx Josh
Click to expand...
Click to collapse
I've done that, but I've never really used fastboot and I don't want to mess this up. I assume I have to go to bootloader mode and somehow install the blob files. I don't really know how.
LEGOracer69 said:
I've done that, but I've never really used fastboot and I don't want to mess this up. I assume I have to go to bootloader mode and somehow install the blob files. I don't really know how.
Click to expand...
Click to collapse
No worries at all ...
Shoot me an email we can use G+ to have a screenshare [email protected]
Thx Josh
@LEGOracer69
Can you add "SOLVED" to the thread title
Hey XDA we had to do what was talked about in the thread and we used this guide ....
http://forum.xda-developers.com/transformer-tf700/help/guide-t2853546
We did not have to use the bootit.ko as we had fastboot access so we skipped to the
fastboot erase system command
and went from there ...
Thx Josh