Ok, So I saw ClockworkMod released a recovery 5.5.0.4 for the Asus Transformer TF101 and decided to try it out(Dumb move on my part I admit). Anyways, now it continually boots into Recovery and will not boot into the AndroidOS at all. I've attempted NVFlash only to find out I have a B80 with a Locked Bootloader, thus I cannot use NVFlash. I've also tried reflashing Roach's Recovery as well as Rogue Recovery to no avail it does not seem to work. I'm pretty much as my whit's end here and was wondering if anyone had any possibility of fixing this or do I have a new paperweight?
Any and all Ideas are welcome I've tried looking through various other forums along with searching widely for some form of a fix but yeah...
Thanks
Same thing just happened to me yesterday. I have tried everything. I have a B90 and i cant get out of CWM Recovery. CWM also won't see my micro sd card.
Any help will be greatly appreciated!
Hi guys!
Just about the same thing happened to me yesterday.
I was getting tired of ICS-reboots and instability, so i rooted my TF101, installed RomManager and flashed CWM 5.5.0.4.
When CWM couldn't see my MicroSD I ended up putting the zips on internal memory and flashed both a full wipe script and Android Revolution HD 3.0.1. This worked fine.
However - when I reboot my Transformer, it always reboots into CWM instead of booting normally. To get it to reboot normally, I do the following:
- Power on and then hold [Vol Down] until there is small white print at the top of the screen
- Wait about 5 seconds
- Press [Vol Up] to perform a "cold boot", which basically boots your Transformer normally
I too would like to know how to stop the default CWM-boot.
Hope this helps!
Regards,
Christian
I am having the exact same problem. Flashed clockworkmod through rom manager, installed he latest android revolution, now it won't boot past clockwork mod. Help?
Nice! Installing now. Will report back. Thanks!
How are you getting on ? I also have this problem :-(
Hi again!
Last night I stayed up late trying to fix this - and guess what...it worked!
It took some searching on XDA and Google to find the solution.
Everything you need to flash a working recovery is in the first post of this thread: http://forum.xda-developers.com/showthread.php?t=1530337
I flashed the following recovery: "CWM-based Recovery v5.5.0.4 roach-tf101-r2" (http://forum.xda-developers.com/showthread.php?t=1213723)
At first the command "adb shell" wouldn't work in Windows command prompt. Found out that the Asus adb-drivers were not installed correctly, so I had to update the drivers manually in Windows (downloaded them from Asus' support-site).
I didn't have to push the recovery to the internal memory, as it was already there from my previous attempts.
Fire away if you have any questions!
Edit: And by the way - afterwards I was able to flash Krakd 1.5.2, which I'm running now. ICS can wait for now - I need it to more stable...
Regards,
Christian
Thanks Christian!
chrizz29 said:
Hi again!
Last night I stayed up late trying to fix this - and guess what...it worked!
Click to expand...
Click to collapse
Thank you for the tip! I'll give it a try- I encountered the exact same issue with CWM, plus an extra present... Wifi will not turn on. Still scratching my head over that one, but it's an issue for another thread.
WiFi Not turning on..
codebluechris said:
Thank you for the tip! I'll give it a try- I encountered the exact same issue with CWM, plus an extra present... Wifi will not turn on. Still scratching my head over that one, but it's an issue for another thread.
Click to expand...
Click to collapse
I had the same issue when restoring form a nandroid backup.
The way I fixed it was by doing the following
***DO A FULL WIPE***
--Flashed Rom--first
--wiped data--second
--Advanced restore/restore data only--
--reboot-- done
Wifi working Again.
Hope the helps..
However still Haaving problems with clockwork mod rebooting tried the above post and nothing .....
I got the same problem after play around with ROMManager, following is how to fix it.
Credit goes to here: http://blog.vegeby.nu/post/20159305108/transformer-always-booting-recovery-solution
As Christian mentioned in post #3, press Vol- with Power to boot into Android normally, then do following in either adb or Terminal app:
Step 0:
Code:
su
(to switch to root mode, the prompt should change to #)
Step 1:
Code:
cat /dev/block/mmcblk0p3
this will print something like following
==========
boot-recovery
x......#4r8$)#*0
==========
(5 to 10 lines garbage text except first line)
Make sure the first line is "boot-recovery", if not, DO NOT CONTINUE.
Step 2:
Then, run following command carefully, make sure it is correct:
Code:
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
it should say some thing like 5 bytes write
Step 3: (Optional, you can reboot now, if you are curious, run this step to see/verify the changes we just did)
Then run the cat cmd again:
Code:
cat /dev/block/mmcblk0p3
this will print something like following
==============
boot
recovery
x......#4r8$)#*0
===============
(same garbage text except first line now is only "boot")
Now, a normal reboot should boot to Android by default.
Again, do this at your own risk, if you are not comfortable do this, maybe you can try flash other ROM (like Post #7) see if they overwrite above partition.
Cheers,
xordos
Edit: if the cat cmd cause many garbage chars and even corrupt the display, please try following command to only display first 2 lines:
Code:
cat /dev/block/mmcblk0p3 | head -2
xordos said:
I got the same problem after play around with ROMManager, following is how to fix it.
Credit goes to here: http://blog.vegeby.nu/post/20159305108/transformer-always-booting-recovery-solution
As Christian mentioned in post #3, press Vol- with Power to boot into Android normally, then do following in either adb or Terminal app:
Step 0:
Code:
su
(to switch to root mode, the prompt should change to #)
Step 1:
Code:
cat /dev/block/mmcblk0p3
this will print something like following
==========
boot-recovery
x......#4r8$)#*0
==========
(5 to 10 lines garbage text except first line)
Make sure the first line is "boot-recovery", if not, DO NOT CONTINUE.
Step 2:
Then, run following command carefully, make sure it is correct:
Code:
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
it should say some thing like 5 bytes write
Step 3: (Optional, you can reboot now, if you are curious, run this step to see/verify the changes we just did)
Then run the cat cmd again:
Code:
cat /dev/block/mmcblk0p3
this will print something like following
==============
boot
recovery
x......#4r8$)#*0
===============
(same garbage text except first line now is only "boot")
Now, a normal reboot should boot to Android by default.
Again, do this at your own risk, if you are not comfortable do this, maybe you can try flash other ROM (like Post #7) see if they overwrite above partition.
Cheers,
xordos
Click to expand...
Click to collapse
Worked fine for me, thanks!
Still Stuck
I tried the above, no change. Every reboot goes to recovery.
One thing I noticed, when it boots to recovery it always claims to be 5.5.0.4 even though RomManager claims I'm on 5.8.2.1. I tried rolling to 5.8.2.0 and back, even to 5.5.0.4 and back to 5.8.2.1. but every boot goes to recovery and claims to be 5.5.0.4.
Nomadadon said:
I tried the above, no change. Every reboot goes to recovery.
One thing I noticed, when it boots to recovery it always claims to be 5.5.0.4 even though RomManager claims I'm on 5.8.2.1. I tried rolling to 5.8.2.0 and back, even to 5.5.0.4 and back to 5.8.2.1. but every boot goes to recovery and claims to be 5.5.0.4.
Click to expand...
Click to collapse
Have you tried step 3 to verified the result? the first line changed or not?
Asus TF101 problem
I did the cat of the block device and it throws many pages of binary data. I am pretty sure I saw the boot-recovery go by but it crashed my connectbot.
Nomadadon said:
I did the cat of the block device and it throws many pages of binary data. I am pretty sure I saw the boot-recovery go by but it crashed my connectbot.
Click to expand...
Click to collapse
Oh, i see, can you try following command then:
cat /dev/block/mmcblk0p3 | head -2
(I updated my original post too)
If you still see "boot-recovery" in first line, then it means the "dd" cmd is not successful, please make sure you are root (step 0, su is doing this) when you run the dd. Or you can run command "id" and double check.
TF101
Same think couple pages of binary goes blowing by. If I do head -1 I get "boot-recovery" then write:Broken pipe.
---------- Post added at 03:08 AM ---------- Previous post was at 03:02 AM ----------
I just redid the echo | dd part. hte Head -2 showed boot and boot-recovery as it should. I rebooted and booted into recovery 5.4.0.4 again. After the reboot the "boot" is missing from the block head output.
That part concerns me also, according to rom manager I'm on 5.8.something but every time I boot into recovery I'm in the same 5.4.0.4. it's like I have 2 recoveries chained or something.
Nomadadon said:
Same think couple pages of binary goes blowing by. If I do head -1 I get "boot-recovery" then write:Broken pipe.
---------- Post added at 03:08 AM ---------- Previous post was at 03:02 AM ----------
I just redid the echo | dd part. hte Head -2 showed boot and boot-recovery as it should. I rebooted and booted into recovery 5.4.0.4 again. After the reboot the "boot" is missing from the block head output.
That part concerns me also, according to rom manager I'm on 5.8.something but every time I boot into recovery I'm in the same 5.4.0.4. it's like I have 2 recoveries chained or something.
Click to expand...
Click to collapse
OK, yeah, then your setup is weird, looks like some boot code overwrite that block and set it back to boot-recovery. Maybe you can try clean it up by flashing some ROM and/or cwm again?
TF101
I've tried 3 different roms (on Kang right now). Just this morning I went to latest cm9 (no wifi :<) and back to Kang. Same behavior.
xordos,
thank you very much. finally got it fixed after seeing this!
TF101
Is it possible to rebuild/recreate /dev/block/mmcblk0p3 ?
Robert
Related
Update - 2/21/2011
If you have bricked an HTC EVO this will likely NOT work for you and this is the wrong info to be reading. I have gotten a few emails from this link about EVO 110 errors.
12/26/2010 - This thread is super old now:
If you ran the 1.56 RUU and your phone no longer turns on visit htc.com, go to support, choose Hero (Sprint) and download the 2.1 system update.
Remove battery from your phone and start it up again, then run the exe file that you just downloaded -
http://member.america.htc.com/downlo...2.27.651.6.exe
------All the info below is kept for reference -------
(As of 3/31/2010 - I am 10 for 10 for getting these back and working!! 3/3 of going back to 100% stock)
Edit: I have no longer kept track... its been over a month and I know personally I've done about 15 more of these... with about half being return to stock.
If you need to contact me, PLEASE EMAIL instead of using private messages, it'll probably turn into a google talk chat anyways, so add me on there, [email protected] (Its just easier than having to log in here and reply to private messages, since I get emails on the go as well.)
So you just ran the 1.56 RUU and got a 110 error. Now your screen turns on and stays black and if you plug the phone into USB you see the HTC logo. Unplug it and see the RUU menu.
Like you, I decided to attempt to roll back using the RUU 1.56. I was hit with the 110 error, and nothing but fastboot would work, I was able to launch ./fastboot-mac oem boot to get into the system.
I tried ./fastboot-mac boot image/bootname.img and a billion other things like everyone else who is having the issue, but just like them I had no success. In the second post below are the steps to resolve this issue. This will either take you to your first Nandroid backup or to whatever ROM you choose to flash once you get recovery back. I have not found a way to get back to 100% stock, but at least your phone wont be a brick.
EDIT:As of 3/30/2010 @ 8:30 PM I was able to get my phone completely 100% to stock. I was able to do this by retrieving a Nandroid restore from someone who used flashrec to make their initial backup. This restore does not touch the recovery image but I was able to boot into my recovery then write the HTC recovery back on top of it. I now have 100% un-rooted phone. See Post number 2 for the right way to do this.?
I've helped a few people over log me in now.
I'm willing to continue doing this but it is cutting into my family time, I will do this for a "respectable" amount of money.
Feel like I've helped you??
Buy me some coffee!
(Zip attached includes fix and stock folders. Use the fix folder FIRST to get completely booted. You can use the stock folder if you want to get 100% stock after you have a running unrooted system but have RA recovery.)
Steps to resolve:
(You SHOULD have a Nandroid backup of some sort, if not download a ROM... Fresh1.1??)
1) Boot the phone to black screen
2) Plug phone into PC/MAC - The HTC logo should appear at this point
---- If you've been doing anything else, rerun the RUU and let it fail and reboot to the HTC logo.
3) PC - fastboot oem boot | MAC - ./fastboot oem boot
(Make sure you turn on USB Debugging under Settings --> Applications --> Developer)
4) Root your phone using asroot2
Code:
adb push asroot2 /data/local/
adb shell chmod 0755 /data/local/asroot2
adb shell
/data/local/asroot2 /system/bin/sh
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4775 su
5) This is where your Nandroid backup comes into play.
(Browse to your nandroid folder, find your first backup and copy all of the .img files except system and cache to your SD card root directory)
NOTE: At this point you should dismount the SD card if you mounted inside of Android OS(Sense/Launcher)
6) run adb shell (PC - adb shell | Mac - ./adb shell)
7) type su
8) Run the following commands (if you get out of memory errors, type su again and try once more)
NOTE: Do not copy the "#"'s in the commands, the # just means you are running as SU, as opposed to the "$"
Code:
# flash_image recovery /sdcard/recovery.img
# flash_image boot /sdcard/boot.img
# flash_image misc /sdcard/misc.img
9) now... type reboot recovery
This time you should get your recovery menu, should have been RA or whatever you used... from there I did a complete nandroid restore and my system booted.
Also, after I did this I did try to let it boot without doing a recovery and it wouldnt go anywhere... but I'm fairly impatient... it may have wanted to load. I figured it best to do an entire Nandroid restore though.
-------------------------------------------------------------
100% Stock Configuration Work Around
-------------------------------------------------------------
Non-Rooted Nandroid Backup:
nandroid.7z
I was able to get my phone completely 100% to stock. I was able to do this by retrieving a Nandroid restore from someone who used flashrec to make their initial backup. This restore does not touch the recovery image but I was able to boot into my recovery then write the HTC recovery back on top of it. I now have 100% un-rooted phone. I'm not sure how to go about posting a 127MB file, what do you think it the best place?
After restoring the Nandroid backup I tried this:
Code:
Dustan-Bonneys-MacBook:tools dustanbonney$ ./adb shell
$ su
su: permission denied
Then I rebooted to recovery (I used RA 1.5.2)
Code:
Dustan-Bonneys-MacBook:tools dustanbonney$ ./adb remount
remount succeeded
Dustan-Bonneys-MacBook:tools dustanbonney$ ./adb shell
/ # mount -a
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: No such file or directory
/ # cd /sdcard
/sdcard # flash_image recovery /sdcard/Stock/recovery.img
flashing recovery from /sdcard/Stock/recovery.img
/sdcard # reboot recovery
I was booted to the Triangle and exclamation mark... I pulled the battery and booted up normally.
Stock Kernel - 2.6.27-533ce29d [email protected] )
Stock Build - 1.56.651.2 CL85027 release-keys
Other things that should be mentioned:
If you used RA 1.6.2 - I was unable to get my boot.img or the stock boot.img from the RUU's rom.zip to flash back to the recovery partition. I had to use the RA 1.6.2.img and "flash_image recovery /sdcard/recoverynamegoeshere.img"
It seems that if you've flashed the radio update, the RUU does not write the radio back successfully. Others have had issues going back to the stock radio using the upgrade.zip option as well.
I attempted to use the boot.img, recovery.img, from the RUU's rom.zip with no success. I might try it again. I was able to get to stock recovery (Triangle and exclamation) and to the Hboot menu... but from hboot I had to run the RUU and rebrick the device cause I couldnt get anything at that point, even fastboot oem boot wouldnt load.
There have been times when I get weird issues writing the flash recovery, boot, or misc and when you reboot and load "fastboot oem boot" it wont look like it goes anywhere.... check "adb devices" and your device should be listed. From there do an "adb remount" and then "adb shell" and reflash once more and then "reboot recovery".
If all else fails, I'm available for a small fee.
[email protected]
Anxiously waiting your news. Just encountered this problem today.
Updated ...
imekul said:
Anxiously waiting your news. Just encountered this problem today.
Click to expand...
Click to collapse
Wow! If you've fixed this, I think you're everyone's hero now. We won't have to worry about using the RUU now
I was going to try something similar to this today, but i was unable to brick my phone using the 1.56.651.2 RUU. I was running Flipz updated radio and DamageControl v2.0r2.. The RUU completed successfully..
I was reading over the forum post in http://forum.xda-developers.com/showthread.php?t=645002 and i read that you could boot the system using the command 'fastboot oem boot' I was going to try to use FlashRec to do the work of Flashing the recovery, then booting into recovery and use nandroid.. but you beat me to it! Good work!
I attempted flashing a new recovery image this way with no avail... I also attempted only
Code:
flash_image recovery /sdcard/recovery.img
and still was unable to boot the phone into recovery. I think it had to have been something with doing boot.img and recovery.img at the same time... I dont know what the misc.img does and I'm assuming data.img is userdata... but I did them all and then it worked...
Other users also tried flashrec and with no success... right track though.
chavo2005 said:
I was going to try something similar to this today, but i was unable to brick my phone using the 1.56.651.2 RUU. I was running Flipz updated radio and DamageControl v2.0r2.. The RUU completed successfully..
I was reading over the forum post in http://forum.xda-developers.com/showthread.php?t=645002 and i read that you could boot the system using the command 'fastboot oem boot' I was going to try to use FlashRec to do the work of Flashing the recovery, then booting into recovery and use nandroid.. but you beat me to it! Good work!
Click to expand...
Click to collapse
What do u mean by 3) PC - fastboot oem boot | MAC - oem boot?
blankd3ckskat3r said:
What do u mean by 3) PC - fastboot oem boot | MAC - oem boot?
Click to expand...
Click to collapse
if your using a pc type fastboot oem boot
if your using a mac type ./fastboot oem boot
This!
Thanks Regaw
regaw_leinad said:
if your using a pc type fastboot oem boot
if your using a mac type ./fastboot oem boot
Click to expand...
Click to collapse
Trying this right now.
So far, am getting lots of "mtd: write error" and "mtd: re-read error" Out of memory errors for flashing the recovery image. Guess I'll give this some time, and try to su again and reflash? Or should I kill it as soon as the Out of memory errors pop up and try again?
If you get errors like...
adb shell
su
flash_image recovery .........
(out of memory... etc)
Then...
just su again... so you really su twice
its what I had to do.
imekul said:
Trying this right now.
So far, am getting lots of "mtd: write error" and "mtd: re-read error" Out of memory errors for flashing the recovery image. Guess I'll give this some time, and try to su again and reflash? Or should I kill it as soon as the Out of memory errors pop up and try again?
Click to expand...
Click to collapse
Trying it a second time, and so far am getting a bunch of Out of memory errors. After the first one "finished," I did as you recommended and typed "su" a second time, and then typed the "flash_image recovery /sdcard/recovery.img" command.
So far, looks like it's giving the same errors the second time around.
This second attempt, it ended with "error writing recovery: No space left on device."
Just to be sure, I checked the SD card, and that has over 1 GB of free space.
If you're willing to allow something like logmein.com or some way for me to remote assist you, I would like to try. [email protected] if you're in.
imekul said:
This second attempt, it ended with "error writing recovery: No space left on device."
Just to be sure, I checked the SD card, and that has over 1 GB of free space.
Click to expand...
Click to collapse
Sounds awesome. Thanks. I'll e-mail you now.
Dun Dun Dun... The results are in!
imekul said:
Sounds awesome. Thanks. I'll e-mail you now.
Click to expand...
Click to collapse
dfbonney is the man!!
After a friendly little session on LogMeIn Express, I am good as new! How awesome!!
imekul said:
dfbonney is the man!!
After a friendly little session on LogMeIn Express, I am good as new! How awesome!!
Click to expand...
Click to collapse
We ended up just needing to run
Code:
adb shell
reboot
fastboot oem boot
adb shell
su
//flash commands here
that seemed to do it. so make sure if you're having issues to restart the device and try again!
Edit: Also, we didnt get data.img to work so we only did boot, recovery, and misc.img's
ClockworkMod Touch Recovery 5.8.2.1 by JvS CoRp V5
ChangeLog
V1
Installation Error Fixed
V2
Reboot Loop Fixed
Internal memory install only
V3
Minor Fixes for improve performance
Still Internal Memory
V4
New Version 5.8.1.9
Improve performance
V5
New Version 5.8.2.1
LINK Removed
Work on it
Installation:
Just flash the attached zip from internal memory with 5.5.0.4 .
Tested on TF101G B80 con CM9
For change CWM download and install Recovery Installer APK and run.
Thanks Button is not cost nothing Use it
Usual disclaimer applies: if you brick your tablet, it's not my problem!
Thanks all Android Community.
jvscorp said:
ClockworkMod Recovery touch 5.8.1.8 for TF101 \G by JvS CoRp Original
Installation:
Just flash the attached zip from CWM.
Usual disclaimer applies: if you brick your tablet, it's not my problem!
Click to expand...
Click to collapse
I see you have been lurking around here for 4 years lol.. does this cwm allow flashing from both internal and external sd? great work and thanks. haven't tried it though.
I'm looking forward to trying this.
Kept getting parse error and wouldn't install (STATUS 6). Redownloading and will report back.
Edit: Booted back to CWM with a few fresh d/ls. Same error. Line 1 of 56 is BAD.
Sent from my Transformer TF101 using xda premium
gunz.jones said:
Kept getting parse error and wouldn't install (STATUS 6). Redownloading and will report back.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Me too...
10x
gunz.jones said:
Kept getting parse error and wouldn't install (STATUS 6). Redownloading and will report back.
Edit: Booted back to CWM with a few fresh d/ls. Same error. Line 1 of 56 is BAD.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Same here...
kay_kiat88 said:
I see you have been lurking around here for 4 years lol..
Click to expand...
Click to collapse
4yrs, 7 posts
But,... this looks interesting
kay_kiat88 said:
I see you have been lurking around here for 4 years lol.. does this cwm allow flashing from both internal and external sd? great work and thanks. haven't tried it though.
Click to expand...
Click to collapse
if it does both, and the install issues get resolved, then I'll flash it. Very interested...
same issue as the last official cloclwork release. will not reboot. always bqck to recovery. roach please work ur magic. thnx in advance
jefbal99 said:
if it does both, and the install issues get resolved, then I'll flash it. Very interested...
Click to expand...
Click to collapse
It only read from internal.
Right now I'm getting problems of rebooting back into recovery
baseballfanz said:
It only read from internal.
Right now I'm getting problems of rebooting back into recovery
Click to expand...
Click to collapse
Same here. I have everything stored and backed up to my external SD. Thanks to the OP for our first touch recovery. It does need some fine tuning though. Going back to Rogue for now.
Well you know what's wrong just want to say good work
Running fine now. It would be great if it had the micro SD support...
---------- Post added at 06:25 PM ---------- Previous post was at 06:08 PM ----------
Spoke too soon... It's rebooting into recovery...
I have Rogue CWM in the system memory and i tried to install over this one and didn't work... it goes back again into recovery. Anybody as any idea on how i can get in the OS? or copy Roach CWM in to the system memory?
Any help would be appreciated...
Since people are so interested in touch recovery and especially any recovery with MicroSD support and /sdcard support, then I wonder if anyone has based their take on this on the working MicroSD/Internal version (as linked to by this):
https://github.com/rburrow87/android_device_asus_tf101_recoveryonly
I am guessing that if you know how to add the touch logic to recovery then you might be able to add very similar logic (nothing is ever the same) to this working version I linked to.
It seems odd that people are developing without using both internal and external storage but all work is appreciated.
Managed to get in the OS but i tried to install Roach and Rogue CWM over this one and it doesn't install... always comes up the same...
Any ideas?
SWEagle said:
Managed to get in the OS but i tried to install Roach and Rogue CWM over this one and it doesn't install... always comes up the same...
Any ideas?
Click to expand...
Click to collapse
After you have flash a different recovery DO NOT use the Boot into system.
Instead cold boot into the OS and use Terminal Emulator to type in the following command.
Type : su (give permission if ask, choose YES). You should get a #
Type : echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Type : exit
Type : reboot
Note: Hit "Enter" after each line
baseballfanz said:
After you have flash a different recovery DO NOT use the Boot into system.
Instead cold boot into the OS and use Terminal Emulator to type in the following command.
Type : su (give permission if ask, choose YES). You should get a #
Type : echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Type : exit
Type : reboot
Note: Hit "Enter" after each line
Click to expand...
Click to collapse
Thanks you very much for you response...
Me and a friend of mine use this adb command to stop the bootloot and with this it reach the point of the CWM instalation... now it's working fine...
Type: adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3
isnt touch recovery available through rom manager now? Is that any better?
Tazzaras said:
isnt touch recovery available through rom manager now? Is that any better?
Click to expand...
Click to collapse
Not for the Transformer. The CWM available through ROM Manager doesn't work either.
how do you get out of recorvery. need help
I have problem with CWM v5.8.3.4, while i flash, restore, back, everything it still back to recovery mode, can`t do nothing.
CWM v5.8.3.4 -- Here is your problem, you used ROM manager to update recovery. There are red flags on this pretty much everywhere Dx
You've gotten into the bootloop, see my PERI tool (Link in sig) and try and run the bootloop-fix there, if you can get adb working. You can also try it manually (Again, adb permitting) in roach2010's recovery touch thread, he provides the fix there.
If you can't get adb working at all, you need to NvFlash back to stock, wheelie thread is again in my signature.
Good luck.
--
By the way, you can get back into Android by Cold-booting the system. Hold volume-down, then press power and keep holding volume-down till it boots. Don't press volume-up or anything else, that'll put you back into recovery.
I was tryin` but while i want to flash someting apx turning off and can`t do nothing :/ Erm, how to fix can`t use my tablet about 1 month
Hi,
have you tried coldbooting ?
Hold power and volume down. Should get you out of recovery.
Yes, i do mate, and can`t do nothing. It dont see sd card and tablet memory :/
Okay I have the same problem, i used the cursed Rom Manager and now im stuck in the endless boot cycle, I can cold boot and I have tried to flash roachs cwm but nothing. Ive read where roach gives a code that might fix it, but i have no ideal what to do with that code or how to use it, and i see where thing o doom said the fix is in his signature but im not having much luck with that either. If you could maybe explain to me how im supposed to use roaches code or post the link that explains it here, I would sure appreciate it. Thank you.
Sent from my Transformer TF101 using XDA Premium HD app
Any ideas please? :/
Start an adb shell session with your computer connected, or in a terminal app on your tf, then run roaches fix (type it in) to the terminal app/adb shell session.
"then run roaches fix" u mean write app/adb shell session ?
And now i got another problem:
"E: Can`t mount /sdcard/
Biggest problem for now, i can`t turn on debuging :/
okay I opened terminal emulator on my tablet and typed in roaches fix exactly like it says
adb shell dd if=/dev/block/mmcblk0p3
and this popped up
*daemon not running. starting it now on port 5038*
*daemon started successfully*
error: device not found
255 [email protected]:/ $
what am i doing wrong? thank you so much for your continued help
Ive also tryed the peri and easy recovery with no luck, I think my bigest problem is i dont understand the adb thing, ive tryed searching about it and im lost.
That's the wrong dd command, dd consists of an if=/ then an of=/
Try this.
adb kill-server
adb start-server
adb devices
(you should see the tf, if not, bad drivers/not working connection, fix that first)
adb shell
su (Grant superuser permissions, if you can, and you'll see a # sign)
dd if=/dev/zero of=/dev/block/mmcblk0p3
reboot
Then flash a new recovery by:
Download and extract recoveryblob from recovery.zip
adb kill-server
adb start-server
adb devices
adb push C:\path\to\recoveryblob /sdcard/
adb shell
su (you'll get # sign again)
dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4
reboot
I have to thank you for your patience and continued help with my problem, but with that being said I must inform you that I am still completely lost. Im not a developer and I would not even consider myself remotely knowledgeable in the subject. I was just wanting a nice custom ROM and I had found one with cyanogen mod 9 but I messed up by using the Rom manager and now I'm screwed.
I can cold boot into my tablet, and on my tablet I have this computer emulator program, which i can type in the codes you mentioned, but I'm pretty sure that is not correct. what i need is a program like that on my computer, so far I found this link regarding adb, but I'm not sure if it is right direction.....
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
if this is the wrong direction, can you please point me in the right direction? again I am sorry for my ignorance and when this is all done I will be sure to buy you a freaking case of beer. Thank you
You can run the adb commands on your TF using the emulator app, but you'll need to directly download the recoveryblob used to flash.
Open terminal and run roach's fix (except instead of typing adb shell, you just start from su, then run the dd command from there, since you're already in the tf's 'shell')
so
su
dd if of etc
reboot
Then you'll need to reflash a recovery, so download Team Rouge's Recovery.zip then use ES file explorer app (download that) to extract the file called 'recoveryblob'. Take that file called 'recoveryblob' then copy it out of the downloads folder (still using ES file explorer) hit the favorites button then hit /sdcard/ (You don't need a microSD card to do this, /sdcard/ [For whatever reason ..] is the Internal storage. [/removable/microSD/ is the external]) then paste the recoveryblob right in /sdcard/.
Open up the terminal emulator and run
su
dd if=/sdcard/recoveryblob/ of=/dev/block/mmcblk0p4
reboot
That should give you recovery! (Then you can reflash a ROM or do whatever you need/Enjoy not having to cold-boot everytime)
Sent from my Tf101atron9000 using XDA Premium HD
Im stuck w8ing for You at Skype: )
Thanks for your info. TF now up and running without the need to cold boot. For information, I did not use a Rom Manager to flash the rom, I used CWM to flash the Gummy Rom.
I finally got my tf101 fixed and I learned something new. I just wanted to thank Thing of Doom for all of the help he offered me and without ever asking anything in return. Thanks.....
If anyone wants to know, here's what I did to fix nefem's completely FOUBAR TF101g.
First I tried NvFlash, then right at the flashing stage realized it's a tf101g Sbkv3, so that was out X.x
Then I uninstalled all the drivers and reinstalled them with PERI, got ADB working through recovery.
I had him try and flash a .zip file for a new recovery so I could run Roach's fix, but for whatever reason the CWM wouldn't mount the Internal storage (mmcblk0p7 or /sdcard/) so I manually pushed the recoveryblob to /sdcard/ and it seemed to work, but when I ran dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4 it couldn't mount and find it.
The next thing I tried since internal was acting funky was looking at the log, I noticed that the directory was /system/sbin so I just pushed the recovery to there, adb push recoveryblob /system/sbin, then ran the same dd command with that directory and it worked. Then I just ran roach's fix normally and rebooted, he had rouge recovery!
That was the first part, his internal was still borked for some reason and Rouge couldn't mount it.
I tried various ADB mounts and they all failed, so eventually he put a MicroSD into his phone (or something else) I placed the ARHD superswipe script and a ROM w/ Guevor's kernel on there, then since rouge reads external, superwipe was able to completely format internal storage. From there it was an easy wipe and flash. Once we got a working ROM on there, we noticed that it was still getting stuck at the Eee pad logo (He could cold-boot). So I figured that his bootloader was still messed up, so we took the latest Tf101G stock blob, used the handy Rayman's blob tools to pull out the EBT (bootloader partition) blob, then directly flashed that with dd again through adb: dd if=/sdcard/blob (Removed the EBT extension, important) of=/dev/block/mmcblk0p4
Reboot, and finally it was booting optimally!
It was a tad of trial and error (The internal storage thing really had me confuzzled) but it all got fixed up in the end.
Hope this helps someone somewhere
Thing O Doom said:
If anyone wants to know, here's what I did to fix nefem's completely FOUBAR TF101g.
First I tried NvFlash, then right at the flashing stage realized it's a tf101g Sbkv3, so that was out X.x
Then I uninstalled all the drivers and reinstalled them with PERI, got ADB working through recovery.
I had him try and flash a .zip file for a new recovery so I could run Roach's fix, but for whatever reason the CWM wouldn't mount the Internal storage (mmcblk0p7 or /sdcard/) so I manually pushed the recoveryblob to /sdcard/ and it seemed to work, but when I ran dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4 it couldn't mount and find it.
The next thing I tried since internal was acting funky was looking at the log, I noticed that the directory was /system/sbin so I just pushed the recovery to there, adb push recoveryblob /system/sbin, then ran the same dd command with that directory and it worked. Then I just ran roach's fix normally and rebooted, he had rouge recovery!
That was the first part, his internal was still borked for some reason and Rouge couldn't mount it.
I tried various ADB mounts and they all failed, so eventually he put a MicroSD into his phone (or something else) I placed the ARHD superswipe script and a ROM w/ Guevor's kernel on there, then since rouge reads external, superwipe was able to completely format internal storage. From there it was an easy wipe and flash. Once we got a working ROM on there, we noticed that it was still getting stuck at the Eee pad logo (He could cold-boot). So I figured that his bootloader was still messed up, so we took the latest Tf101G stock blob, used the handy Rayman's blob tools to pull out the EBT (bootloader partition) blob, then directly flashed that with dd again through adb: dd if=/sdcard/blob (Removed the EBT extension, important) of=/dev/block/mmcblk0p4
Reboot, and finally it was booting optimally!
It was a tad of trial and error (The internal storage thing really had me confuzzled) but it all got fixed up in the end.
Hope this helps someone somewhere
Click to expand...
Click to collapse
I am having the same exact problem as him with the same amount of programming expertise....I was woundering if you could walk me through it personally as what you've typed above seems like it's in a different language. Thanks very much in advance.
datfinedude said:
I am having the same exact problem as him with the same amount of programming expertise....I was woundering if you could walk me through it personally as what you've typed above seems like it's in a different language. Thanks very much in advance.
Click to expand...
Click to collapse
Sure if you'd like.
My Skype name is Datfinedude
Sent from my Triumph using xda premium
Hi.
First, I'd like to say I tried searching but no luck.
Second, I'm a total Asus noob. I'm pretty good with my HTC Legend, but I don't quite understand the transformer.
My problem: It boots directly into recovery. I bought it used, and it was rooted and running ARHD. When I bought it the seller showed me how to boot it : Boot it regularly, then select "reboot" in recovery, hold "vol-" and it boots into some sort of "menu" where I should press "vol+" to do a cold boot. This is necessary every time. He claimed that all rooted Transformers were like this; I highly doubt that.
So, is there any way I can make it boot normally?
He got it into a boot-loop, you can try fixing it by running my One-Click PERI tool, and then choosing the 'fix-bootloop' option.
This is not normal for rooted transformers, but is a very common and relatively easy to fix problem.
Thing O Doom said:
He got it into a boot-loop, you can try fixing it by running my One-Click PERI tool, and then choosing the 'fix-bootloop' option.
This is not normal for rooted transformers, but is a very common and relatively easy to fix problem.
Click to expand...
Click to collapse
Downloaded, but ADB doesn't recognize my TF101 (adb devices returns nothing)
Tried installing the supplied .inf , but it isn't supported (Windows echoes "The selected INF-file does not support this installation method") and nothing is changed.
So I guess I need some drivers now..
EDIT: Okay, I got the drivers working thanks to Brk's rootkit.
Ran your tool, with "u" as first argument.
Finished without problems.
Still goes to recovery and not booting Android.
Tried applying the "r" option, still boots into CWM 5.5.0.4.
EDIT2: New touch recovery installed, new ROM flashed but still no instant boot.
Ok good, you got out of the bad CWM.
Now you need to reflash your bad bootloader, goto the asus tf101 site, pick download, android, firmware. Then find the firmware for your Region (it'll be WW I believe)
download blobunpack from either searching 'windows' in rayman's blobtools thread or downloading the blob.zip from my boot splash change guide, take the new firmware, unzip the file called 'blob' to a folder with blobunpack.exe in there, then open cmd and cd to the folder, then run 'blobunpack blob', the blob will now be split into many smaller blobs. What you'll want to do is take the one named blob.EBT, then put it on the root of your transformer's INTERNAL storage (So either adb push blob /sdcard/) or use windows to just place it there.
Then go into adb shell or terminal emulator app and type"
Code:
su (Grant root if it asks)
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
reboot
It will reboot, you'll see a blue bar for just a moment, then it reboots again, and *Hopefully* won't get stuck.
Thing O Doom said:
Ok good, you got out of the bad CWM.
Now you need to reflash your bad bootloader, goto the asus tf101 site, pick download, android, firmware. Then find the firmware for your Region (it'll be WW I believe)
download blobunpack from either searching 'windows' in rayman's blobtools thread or downloading the blob.zip from my boot splash change guide, take the new firmware, unzip the file called 'blob' to a folder with blobunpack.exe in there, then open cmd and cd to the folder, then run 'blobunpack blob', the blob will now be split into many smaller blobs. What you'll want to do is take the one named blob.EBT, then put it on the root of your transformer's INTERNAL storage (So either adb push blob /sdcard/) or use windows to just place it there.
Then go into adb shell or terminal emulator app and type"
Code:
su (Grant root if it asks)
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
reboot
It will reboot, you'll see a blue bar for just a moment, then it reboots again, and *Hopefully* won't get stuck.
Click to expand...
Click to collapse
This pad is bought in the US. So I guess I should go with the US file?
Edit: Went for the US file, extracted blob.EBT, tried your command in the Terminal Emulator (i had to add ".EBT" after if=/sdcard/blob to make it work) but it still didn't- It moved the file, and I typed in "reboot". It rebooted, but no blue bar and I went straight to recovery. Trying again, but I doubt it will be any different.
Edit2: Nope, same sh*t. Getting kinda annoyed now...
No you don't want .ebt
You want the file to jsut be 'blob'
You may want to run roach's fix directly after, run the above, then also type:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p3
Then reboot.
Thing O Doom said:
No you don't want .ebt
You want the file to jsut be 'blob'
You may want to run roach's fix directly after, run the above, then also type:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p3
Then reboot.
Click to expand...
Click to collapse
Oh thank you very much,this worked. The trick was to let the blob be extensionless.
However, I saw no blue bar, but it booted without going into recovery atleast
Glad it's finally working right
Go call the seller and complain >.<
Thing O Doom said:
Glad it's finally working right
Go call the seller and complain >.<
Click to expand...
Click to collapse
I thought it was solved, but no.
This comes back every time something in CWM is flashed - flashed a bootanimation, it came back, i ran your commands and it was solved. Flashed a new kernel now, it came back.
Ran the commands, it went away but I noticed my kernel wasn't changed and I can't overclock... I think I have a bad CWM accually.
You need to reflash a working CWM recovery then, I take it you're on that infernal ROM manager version. I'd flash Rouge XM 1.5 touch
Thing O Doom said:
You need to reflash a working CWM recovery then, I take it you're on that infernal ROM manager version. I'd flash Rouge XM 1.5 touch
Click to expand...
Click to collapse
Tried PERI but apperantly I cant give ADB SU rights, because wrote failed at /dev/block/mmcblk0p4 because of denied permissions.
Can I use dd to flash it like I did previousley?
Edit: I looked at the sauce of PERI and saw that it was flashing using a shell and DD so I entered it in a regular elevated ADB shell. Finally saw that blue bar I've been looking for and I have Team Rouge's (5.0.2.8) 1.5.0 recovery now. Thank you very much.
Actually, the same has happened to be, and i was trying to go back to stock ww, and i seem unable to find some kind of tutorial for that... I will try what was posted here at least to remove that initial loop.
MarkInDaPark said:
Tried PERI but apperantly I cant give ADB SU rights, because wrote failed at /dev/block/mmcblk0p4 because of denied permissions.
Can I use dd to flash it like I did previousley?
Edit: I looked at the sauce of PERI and saw that it was flashing using a shell and DD so I entered it in a regular elevated ADB shell. Finally saw that blue bar I've been looking for and I have Team Rouge's (5.0.2.8) 1.5.0 recovery now. Thank you very much.
Click to expand...
Click to collapse
Running PERI In CWM always gives root access x)
Try doing the fix bootloop function inside cwm.
Nice to see that you figured it out!
Thing O Doom said:
No you don't want .ebt
You want the file to jsut be 'blob'
You may want to run roach's fix directly after, run the above, then also type:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p3
Then reboot.
Click to expand...
Click to collapse
That did the trick for me, my "boot direct to recovery" problem started when I accidentely selected Reboot to recovery under Advanced when I was "on that infernal ROM manager version" of recovery.
im having similar problems ..... Yep i updated CWM via ROM Manager to 5.8.3.4 (although since managed to downgrade it in theory to 5.8.2.1)
only way i can get into full Android is via a cold boot (but then i have no SD card or Wifi support) or by flashing a full new ROM each time I reboot !!!
problem i have is that im on my holidays and have no access to a PC
Google brought up a patched CWM version but even after flashing that in recovery it was still booting straight into CWM.
Well you r on holiday so can't do anything now... when you come back home try easy flasher to unroot and root again by that way you can get rid of that recovery....
Sent from my Transformer TF101 using xda app-developers app
I'm trying to resurrect this device. I can't recall the exact past of it because it's been so long. I am definitely unlocked and had a custom ROM. I'm willing to try anything before smash.
I've tried to hold the reset pinhole for 30 seconds many times with no difference.
My current behavior is:
Power on > ASUS logo > Linux penguins > TWRP 3.0.0-0 logo > Repeat
Behavior is the same with Vol down held.
My only hope is with Power + Vol up. I get to a blank screen and then I can see that my Windows 7 PC can't install the drivers.
I can't see the device in ADB command window which I have some experience with.
I'm guessing that my first order of action is to sort out my drivers issue and something with NV flash?
Thank you in advance.
echardcore said:
I'm trying to resurrect this device. I can't recall the exact past of it because it's been so long. I am definitely unlocked and had a custom ROM. I'm willing to try anything before smash.
I've tried to hold the reset pinhole for 30 seconds many times with no difference.
My current behavior is:
Power on > ASUS logo > Linux penguins > TWRP 3.0.0-0 logo > Repeat
Behavior is the same with Vol down held.
My only hope is with Power + Vol up. I get to a blank screen and then I can see that my Windows 7 PC can't install the drivers.
I can't see the device in ADB command window which I have some experience with.
I'm guessing that my first order of action is to sort out my drivers issue and something with NV flash?
Thank you in advance.
Click to expand...
Click to collapse
APX mode and nvflash won't help you unless you generated your device specific nvflash blobs back when the tablet was still working and you would remember that. It's an involved process.
So you cannot boot into the fastboot screen? It goes directly to the TWRP splash screen?
Does it stay there for any length of time or does it immediately reboot?
berndblb said:
APX mode and nvflash won't help you unless you generated your device specific nvflash blobs back when the tablet was still working and you would remember that. It's an involved process.
So you cannot boot into the fastboot screen? It goes directly to the TWRP splash screen?
Does it stay there for any length of time or does it immediately reboot?
Click to expand...
Click to collapse
No fastboot. TWRP logo remains on the screen for a period of time. Maybe 10 seconds. Tablet is in the electronics recycle pile... Are you saying there's a chance?
echardcore said:
No fastboot. TWRP logo remains on the screen for a period of time. Maybe 10 seconds. Tablet is in the electronics recycle pile... Are you saying there's a chance?
Click to expand...
Click to collapse
Yes. 10 seconds should be plenty to use bootit.ko - with a little practice. You may have to try a few times to get it right, but you can always do the process in several steps: First push the file to the sdcard, insmod it on the next try. Some guy even created a little batch file for the commands because he had very small window in which to run them. This is all Greek to you, I know. But read this and you'll understand:
www.transformerforums.com/forum/tra...my-transformer-tf700-boots-only-recovery.html
If you manage to kick it back into the bootloader I would then flash the Asus firmware in fastboot right away. Since you don't remember what was wrong with it to begin with it would be best to start from a clean slate and that would be with a pure stock tablet. It's easy to flash a recovery and custom rom from there....
Instructions for that are here: https://forum.xda-developers.com/showpost.php?p=72801448&postcount=8
The link for the Asus firmware is broken again. Get it here: https://www.androidfilehost.com/?fid=817550096634791660
Good luck
Edit: And before you ditch it, send it to me. I'll pay for the shipping. PM me if you can't get it to work
berndblb said:
Yes. 10 seconds should be plenty to use bootit.ko - with a little practice. You may have to try a few times to get it right, but you can always do the process in several steps: First push the file to the sdcard, insmod it on the next try. Some guy even created a little batch file for the commands because he had very small window in which to run them. This is all Greek to you, I know. But read this and you'll understand:
www.transformerforums.com/forum/tra...my-transformer-tf700-boots-only-recovery.html
If you manage to kick it back into the bootloader I would then flash the Asus firmware in fastboot right away. Since you don't remember what was wrong with it to begin with it would be best to start from a clean slate and that would be with a pure stock tablet. It's easy to flash a recovery and custom rom from there....
Instructions for that are here: https://forum.xda-developers.com/showpost.php?p=72801448&postcount=8
The link for the Asus firmware is broken again. Get it here: https://www.androidfilehost.com/?fid=817550096634791660
Good luck
Edit: And before you ditch it, send it to me. I'll pay for the shipping. PM me if you can't get it to work
Click to expand...
Click to collapse
Thanks very much! Will let you know. I really appreciate it!
berndblb said:
Yes. 10 seconds should be plenty to use bootit.ko - with a little practice. You may have to try a few times to get it right, but you can always do the process in several steps: First push the file to the sdcard, insmod it on the next try. Some guy even created a little batch file for the commands because he had very small window in which to run them. This is all Greek to you, I know. But read this and you'll understand:
www.transformerforums.com/forum/tra...my-transformer-tf700-boots-only-recovery.html
If you manage to kick it back into the bootloader I would then flash the Asus firmware in fastboot right away. Since you don't remember what was wrong with it to begin with it would be best to start from a clean slate and that would be with a pure stock tablet. It's easy to flash a recovery and custom rom from there....
Instructions for that are here: https://forum.xda-developers.com/showpost.php?p=72801448&postcount=8
The link for the Asus firmware is broken again. Get it here: https://www.androidfilehost.com/?fid=817550096634791660
Good luck
Edit: And before you ditch it, send it to me. I'll pay for the shipping. PM me if you can't get it to work
Click to expand...
Click to collapse
No bootloader : (
Also tried the 2nd command alone upon subsequent boots with the same result.
EDIT AGAIN: Also tried adb shell by itself:
Code:
X:\Program Files\ANDROID\SDK\platform-tools>adb shell
~ # ←[6n
WTH?
Code:
X:\Program Files\ANDROID\SDK\platform-tools>adb push bootit.ko /sdcard/
bootit.ko: 1 file pushed. 1.1 MB/s (27690 bytes in 0.023s)
X:\Program Files\ANDROID\SDK\platform-tools>adb shell insmod /sdcard/bootit.ko
error: closed
echardcore said:
No bootloader : (
Also tried the 2nd command alone upon subsequent boots with the same result.
EDIT AGAIN: Also tried adb shell by itself:
Code:
X:\Program Files\ANDROID\SDK\platform-tools>adb shell
~ # ←[6n
WTH?
Code:
X:\Program Files\ANDROID\SDK\platform-tools>adb push bootit.ko /sdcard/
bootit.ko: 1 file pushed. 1.1 MB/s (27690 bytes in 0.023s)
X:\Program Files\ANDROID\SDK\platform-tools>adb shell insmod /sdcard/bootit.ko
error: closed
Click to expand...
Click to collapse
You are close. Looks as if you were able to push bootit.ko to the sdcard, but let's check the file system
run the command
adb ls /sdcard/
berndblb said:
You are close. Looks as if you were able to push bootit.ko to the sdcard, but let's check the file system
run the command
adb ls /sdcard/
Click to expand...
Click to collapse
Ah-ha! I get this if I execute the command over and over as it boots until right when it reaches the TWRP screen.
Code:
X:\Program Files\ANDROID\SDK\platform-tools>adb ls /sdcard/
000041ff 00000000 38880412 .
000041ed 00000000 38880412 ..
echardcore said:
Ah-ha! I get this if I execute the command over and over as it boots until right when it reaches the TWRP screen.
Code:
X:\Program Files\ANDROID\SDK\platform-tools>adb ls /sdcard/
000041ff 00000000 38880412 .
000041ed 00000000 38880412 ..
Click to expand...
Click to collapse
Mhh, no idea what that is. Definitely not what I hoped for
That command was supposed to list the contents of your internal storage and what I wanted to see was booit.ko
Either the command does not get through or it is dead wrong :cyclops:
Let me think about this a little and you keep trying in the meantime :highfive:
Tried to run the commands just now and the pic shows what I get.
It looks as if your return is similar to the first 2 lines from what I get with the ls command.
Don't know if your sdcard is totally hosed so that the kernel module does not even write to it?
What I do not understand is that the insmod command fails on my tablet. My knowledge is insufficient to interpret "bad address", but I suspect that bootit.ko was created for one of the _that kernels and I'm running Katkiss on this tablet which has a different kernel. Sorry, this is the end of the rope for me. I can use tools but I do not create them and cannot adapt them to a different situation... :crying:
I wonder if a format command would stop the loop and enable you to boot back into the bootloader, but this is complete speculation and a long stretch grasping for straws....
But wth - before you recycle it, try to squeeze this into the adb window (everything behind the # is just commentary, do not use):
Code:
adb shell kill -19 recovery #hoping this will give you some more time, try the commands below without it if it does not work
make_ext4fs /dev/block/mmcblk0p8 #should format the data partition
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1 #clear misc partition of any commands stuck there
echardcore said:
I can't see the device in ADB command window which I have some experience with.
I'm guessing that my first order of action is to sort out my drivers issue and something with NV flash?
Thank you in advance.
Click to expand...
Click to collapse
Any luck in FASTBOOT?
Bootlooped Tf700t
echardcore said:
Thanks very much! Will let you know. I really appreciate it!
Click to expand...
Click to collapse
berndblb said:
Yes. 10 seconds should be plenty to use bootit.ko - with a little practice. You may have to try a few times to get it right, but you can always do the process in several steps: First push the file to the sdcard, insmod it on the next try. Some guy even created a little batch file for the commands because he had very small window in which to run them. This is all Greek to you, I know. But read this and you'll understand:
www.transformerforums.com/forum/tra...my-transformer-tf700-boots-only-recovery.html
If you manage to kick it back into the bootloader I would then flash the Asus firmware in fastboot right away. Since you don't remember what was wrong with it to begin with it would be best to start from a clean slate and that would be with a pure stock tablet. It's easy to flash a recovery and custom rom from there....
Instructions for that are here: https://forum.xda-developers.com/showpost.php?p=72801448&postcount=8
The link for the Asus firmware is broken again. Get it here: https://www.androidfilehost.com/?fid=817550096634791660
Good luck
Edit: And before you ditch it, send it to me. I'll pay for the shipping. PM me if you can't get it to work
Click to expand...
Click to collapse
I'm sorry, but are you saying that we can ship the bootlooped tablet to you and you can fix it?
I think he's saying, before you throw it away, he's take it off your hands and pay the shipping for you to send it do him. But he's keeping it.
NP
chiefkevbe said:
I'm sorry, but are you saying that we can ship the bootlooped tablet to you and you can fix it?
Click to expand...
Click to collapse
Nektopoli said:
I think he's saying, before you throw it away, he's take it off your hands and pay the shipping for you to send it do him. But he's keeping it.
NP
Click to expand...
Click to collapse
I'm saying: Maybe, under certain circumstances and conditions I may be able to help. But I am not going to advertise a "fix your tablet for free" service here. I don't have the means or the time for that.
I'd rather help you learn how to fix it, but if all fails contact me on PM to discuss this.
berndblb said:
I'm saying: Maybe, under certain circumstances and conditions I may be able to help. But I am not going to advertise a "fix your tablet for free" service here. I don't have the means or the time for that.
I'd rather help you learn how to fix it, but if all fails contact me on PM to discuss this.
Click to expand...
Click to collapse
Thanks again for trying to help me here. I've been playing again with no luck. I think I might try on a Linux box or bootable USB. Probably not until the next time I "work" from home lol.
@echardcore when you hold the VOL-DOWN then press the power on button do you even get the bootloader version readout screen? [See PIC of the TF201t bootloader]
NP
Nope. Goes straight to TWRP splash screen even without holding any volume buttons.
echardcore said:
Nope. Goes straight to TWRP splash screen even without holding any volume buttons.
Click to expand...
Click to collapse
Ok, I'd try sending it a reboot command from a PC with fastboot just to see if the tablet will still respond.
NP
It won't if it's not in fastboot mode
Bootit.ko is your best chance. Give it a shot and if you can't get it done I'll give it a shot