Related
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
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.
I've searched, but the only similar problems either solely involved Windows or ended in a return/RMA. I'm really hoping someone can help me.
Story: I restored a backup using TWRP 2.2.1.3 (ICS). I'm honestly not sure which ROM it was, could have been stock. I was actually restoring it to find out what it was. Before the restore, I wiped data, cache, dalvik cache, and system. The restore went perfectly, no errors or anything out of the ordinary. When I rebooted into the system, it hung on the initial bootsplash. I waited a few minutes before giving up and booting back into recovery. I rebooted by holding down the power button for a while (30 seconds maybe?) and held Volume Down as the tablet booted.
Problem: Instead of the message to press Volume Up to boot into recovery, it just went directly to the screen that comes up after waiting where it counts down the cold boot time and gives you three options - except now, I only have two: Wipe Data and Fastboot. Great, at least I have fastboot. Right? Wrong, apparently. Selecting that option shows the message "Starting Fastboot USB download protocol", but the command
Code:
./fastboot devices
returns a blank line. Likewise,
Code:
./fastboot -i 0x0B05 flash recovery ./openrecovery-twrp-2.2.1.3-tf300t.blob
returns "<waiting for device>".
Attempted troubleshooting: I tried rebooting the device and starting fastboot while attached via USB, and I've tried starting fastboot before plugging in the USB cable. I tried rebooting to the system and using ADB at the hanging bootsplash. There was no ADB access. I've tried restarting the computer while the tablet is plugged in and in fastboot mode.
OS: Debian Testing; ia32-libs, ia32-libs-dev, and ia32-libs-gtk installed
Kernel: 3.5.2 from Debian repos + BFS + BFQ, self-compiled
Previous ROM: Blackbean 8/15
Other: I have not flashed the JB OTA yet (restoring the backup was actually in preparation for the JB OTA; I wanted to see if I had a rooted stock backup). I did not flash the JB version of TWRP. I have used ADB and Fastboot on my tablet successfully in the past on the same computer.
I hope I didn't forget anything relevant. If I think of something else, I'll post it.
Edit: Possible progress? I selected the Wipe Data option, and it loaded TWRP and wiped data. Unfortunately, it immediately attempted to boot the system, which just hung on the initial splashscreen. So, I still have a recovery. I just need a way to boot into it. I'll keep messing around, I guess.
Bump, plus an update.
I realized I should probably run lsusb to see if the computer is actually detecting the tablet. This is the output of "lsusb -v". The output is the same whether the tablet is in Fastboot mode or hanging at the bootsplash. ADB still won't recognize the connected device while on the bootsplash. Interestingly, the iProduct seems to be labeled "Fastboot" in both cases, but fastboot doesn't recognize the tablet either.
Code:
Bus 002 Device 004: ID 0b05:4daf ASUSTek Computer, Inc.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0b05 ASUSTek Computer, Inc.
idProduct 0x4daf
bcdDevice 0.00
iManufacturer 1 ASUSTeK COMPUTER INC.
iProduct 2 Fastboot
iSerial 3 00000
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 32mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 66
bInterfaceProtocol 3
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 66
bDeviceProtocol 3
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0001
Self Powered
I'm really hoping this can help someone. If my computer is recognizing the tablet, there may be some way to bruteforce the tablet into recovery or something, I think.
you may have adb available during the wipe process, you can try to push an install instruction to /cache/recovery/command
Code:
install_package=path to your rescue zip
you could also try to delete /cache/recovery/command and may end up looking at the recovery UI
you would have to be very lucky for this to work
if TWRP uses an external executable to format partitions you could also try to attack that with chmod -x /sbin/mke2fs
and try to get an error screen to display, or replace it with a script that goes in the an endless loop so you have enough
time to
Code:
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
untermensch said:
you may have adb available during the wipe process, you can try to push an install instruction to /cache/recovery/command
Code:
install_package=path to your rescue zip
Click to expand...
Click to collapse
Yeah, I tried that, actually, but forgot to add it to my attempted troubleshooting list. I ran "adb devices" before the wipe so it would be able to detect it ASAP, but I got nothing. It just sat on "<waiting for device>" during the whole process.
you could also try to delete /cache/recovery/command and may end up looking at the recovery UI
you would have to be very lucky for this to work
if TWRP uses an external executable to format partitions you could also try to attack that with chmod -x /sbin/mke2fs
and try to get an error screen to display, or replace it with a script that goes in the an endless loop so you have enough
time to
Code:
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
Click to expand...
Click to collapse
I'm assuming this part depends on the first part working. I'll fiddle with it when I get home from work in the morning.
This is so aggravating. I had no idea that restoring a backup could do this. And it's even more frustrating that my computer can see the tablet at a low level but can't seem to interface with it in userspace.
My next step was going to be to try to PM Asus_USA and Gary Key to see if they had any ideas, but I'm sure they would just tell me they can't help and I need to RMA it.
I may try to contact AndroidRoot.mobi to see if they've seen this or have any ideas, but I'm not sure how willing they would be to help, even if they could. If anyone besides Asus_USA can help, it's them. It may be my last hope before RMA.
i have the same problem ecept it wont even leave the asus logo screen when it first starts up can get into recovery fastboot adb apx nothing i cant even get a wipe device i installed the new jelly bean on mine and something whent wrong cause keyboard wifi ect. was malfunctioning so i factory restored it no help tried wiping data in recovery and now its stuck if any one has any ideas for us thanks
I'm sorry but i saw your title and just want to say thank God I'm not the only one! Good luck and i feel your pain. Gnex myself
*This Jedi master be a Ninj-ESS*
ditto
i flashed cwm touch with fastboot but didn't read the tread properly, it was for stock JB, so now it's stuck on asus boot logo with "this device is unlocked" text up top and when i press power + vol down it's stuck on " starting bootloader kernel image" :crying:
I'm going to lurk your thread. Different device and everything but if you figure something in adb maybe I can use it too.
I don't have any other bootloader except stock, my pad was rooted....
I tried the update and it failed, rebooted and ICS popped back up and I received a message stating that the update failed and ICS was being restored.
I put a copy of the update file in the CACHE folder and tried to update again - this event failed as well, but now my computer won't recognize my pad, and the USB option doesn't show up on the stock recovery (pic below).
Checked device manager and the ASUS PAD is showing error code 10 (device stopped)... downloaded new drivers, rebooted computer, tried to figure out how to load Motorola drivers ( http://forum.xda-developers.com/showthread.php?t=1685540 ), but nothing worked.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Looks like we have similar problems... Hope we don't have to send the pads in to get fixed.
I have gnex and same thing almost. I did a restore from job to pics and its like adb installs drivers backwards.
Sent from my Galaxy Nexus using xda app-developers app
newowner said:
I don't have any other bootloader except stock, my pad was rooted....
I tried the update and it failed, rebooted and ICS popped back up and I received a message stating that the update failed and ICS was being restored.
I put a copy of the update file in the CACHE folder and tried to update again - this event failed as well, but now my computer won't recognize my pad, and the USB option doesn't show up on the stock recovery (pic below).
Checked device manager and the ASUS PAD is showing error code 10 (device stopped)... downloaded new drivers, rebooted computer, tried to figure out how to load Motorola drivers ( http://forum.xda-developers.com/showthread.php?t=1685540 ), but nothing worked.
Looks like we have similar problems... Hope we don't have to send the pads in to get fixed.
Click to expand...
Click to collapse
Hmmm... I was gonna focus on getting fastboot to work, personally. I'll try some things with ADB and the wipe data option like untermensch suggested, too. Maybe there's some kind of exploit we can use to get to the point that we can use untermensch's exploit. I'm gonna compile a new kernel in the morning with USB debugging enabled and see if I can get anything useful from the logs.
Be aware, though, that if anything good comes about, it will be Linux-centric since that's my preferred OS, and I don't really know anything about Windows, especially the changes since XP.
Edit: I see you have the "Android" option. If you select that, what happens? Does the OS boot? Can you access ADB?
EndlessDissent said:
Hmmm... I was gonna focus on getting fastboot to work, personally. I'll try some things with ADB and the wipe data option like untermensch suggested, too. Maybe there's some kind of exploit we can use to get to the point that we can use untermensch's exploit. I'm gonna compile a new kernel in the morning with USB debugging enabled and see if I can get anything useful from the logs.
Be aware, though, that if anything good comes about, it will be Linux-centric since that's my preferred OS, and I don't really know anything about Windows, especially the changes since XP.
Edit: I see you have the "Android" option. If you select that, what happens? Does the OS boot? Can you access ADB?
Click to expand...
Click to collapse
The pad is stuck in boot... with the logo and the rotating circle.
newowner said:
The pad is stuck in boot... with the logo and the rotating circle.
Click to expand...
Click to collapse
Does ADB work for you? I would expect it to at that point in the boot process, but I'm no expert.
How do I get ADB to work with out being connected to the device? The device is not recognized by my computer.
EndlessDissent said:
Does ADB work for you? I would expect it to at that point in the boot process, but I'm no expert.
Click to expand...
Click to collapse
Sent from my DROID RAZR using Tapatalk 2
newowner said:
How do I get ADB to work with out being connected to the device? The device is not recognized by my computer.
Sent from my DROID RAZR using Tapatalk 2
Click to expand...
Click to collapse
What do you mean it's not recognized by the computer? Did you install the drivers for the device? When the tablet is connected to the computer, does anything show up in Device Manager?
mikeseguin said:
i flashed cwm touch with fastboot but didn't read the tread properly, it was for stock JB, so now it's stuck on asus boot logo with "this device is unlocked" text up top and when i press power + vol down it's stuck on " starting bootloader kernel image" :crying:
Click to expand...
Click to collapse
Same thing here ...
with this message :
Device not seen by the PC ... no usb connection ...
adb devices show nothing ...
EndlessDissent said:
What do you mean it's not recognized by the computer? Did you install the drivers for the device? When the tablet is connected to the computer, does anything show up in Device Manager?
Click to expand...
Click to collapse
Pad is hooked up to computer, via usb, and device manager reads "error code 10 (device stopped)"
Computer has been rebooted, drivers have been reloaded/updated, computer rebooted again, and the pad drivers still don't properly install.
newowner said:
Pad is hooked up to computer, via usb, and device manager reads "error code 10 (device stopped)"
Computer has been rebooted, drivers have been reloaded/updated, computer rebooted again, and the pad drivers still don't properly install.
Click to expand...
Click to collapse
Well, if it shows up in Device Manager, the computer sees it, but I don't know exactly what that error means. I have no idea if it's a driver issue. What drivers have you tried? Did you use the Asus drivers? The universal drivers (I've seen some on XDA; look for "naked universal" drivers)? Others have used Motorola drivers when the Asus ones didn't work.
I really don't know why your tablet would boot all the way to the animation but without ADB access. That's why I think (and hope) it might be a driver issue.
dude, I fixed mine! I had to manually input the driver stuff into the setup.inf file in the drivers folder of sdk because it wasnt in there!! check your hardware id under device manager and then check it against the inf file.
Uh?
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
So, i'm having a widely discussed Nexus 5 problem - can't switch WIFI on. I was on 4.4.4 version, so I thought that maybe switching to 5.0.1 may solve it. It didn't plus now it reboots everytime it locks. I flashed the stock with Nexus Root Toolkit v1.9.9. What should I do? Thinking about switching to Paranoid Android, but I don't think that it will solve the initial problem (not being able to turn on WIFI). It just shows that it's turning it on, but never actually turns the WIFI on. The problem has persisted for a long time and I don't really remember when it started.
Oh, and I usually don't mess around with androids, this is my first time flashing a phone. I did it only because I couldn't use the wifi to update.
Any help will be appreciated.
sebreens
P.S. Here's the log from root toolkit.
Information: Checking ADB Status
adb devices
List of devices attached
0676cca30ace3b61 device
ADB Status: Device Connected
Information: Rebooting your device into bootloader mode...
adb reboot bootloader
Information: Checking Fastboot Status
fastboot devices
0676cca30ace3b61 fastboot
Fastboot Status: Device Connected
Information: Booting modified boot.img to enable running privileged commands...
fastboot boot "C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data\Modified_Boot\modified_boot_hammerhead_5.0.1_LRX22C.img"
Information: Waiting for your device...
Information: Device Detected
Information: Pushing 'reset tamper flag' zip to your device...
adb push "C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data\ResetTamperFlag\cwm-Nexus.BootUnlocker.zip" "/sdcard/Download/cwm-Nexus.BootUnlocker.zip"
adb push "C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data\ResetTamperFlag\openrecoveryscript" "/cache/recovery/openrecoveryscript"
Information: Rebooting your device into bootloader mode...
adb reboot bootloader
Information: Checking Fastboot Status
fastboot devices
0676cca30ace3b61 fastboot
Fastboot Status: Device Connected
Information: Booting TWRP Temporarily...
fastboot boot "C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data\Recovery_Custom\TWRP\openrecovery-twrp-2.8.1.0-hammerhead.img"
Information: Relocking bootloader and reseting tamper flag...
Information: Waiting for your device...
Information: Device Detected
Information: Deleting 'reset tamper flag' zip from your device...
adb shell rm "/sdcard/Download/cwm-Nexus.BootUnlocker.zip"
Click to expand...
Click to collapse
Have you already tried a factory reset?
1atabey1 said:
Have you already tried a factory reset?
Click to expand...
Click to collapse
Yes, didn't solve anything. It doesn't reboot until it fades+locks. It is kinda odd + couldn't find anything on google.
I have never been a friend of toolkits, so I'd try to manually download the stock image from the google website and then flash it over fastboot doing a factory reset right before, or, if you have a recent backup of all your Data on the Device, simply run the batch file which is included in the archive.
There are plenty of tutorials on how to do this here on xda, you should find something if you search for it.
I can't post links at the moment, since I've lost my old xda Account, but you should find them quite easily.
Oh, and when it reboots, it doesn't ask for the pin password. When I reboot it normally it does tho.
So I finally manually flashed stock, factory wiped and did everything i found on the basic tutorials here.
OKAY [ 30.945s]
writing 'system'...
OKAY [ 66.316s]
erasing 'userdata'...
OKAY [ 12.928s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 29236371456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7137786
Block groups: 218
Reserved block group size: 1024
Created filesystem with 11/1785856 inodes and 156120/7137786 blocks
malloc: Not enough space
Cannot generate image.
FAILED ()
finished. total time: 116.020s
Press any key to exit...
what does this error mean? obv it has enough space. The phone still works normally except for the thing that when it locks it reboots, resulting in almost constantly rebooting when left alone - thus draining the battery in a couple of hours.
Any help appreciated,
sebreens