Database Info

Nandroid Backup, HELP

Hello everyone,
I have succesfully rooted my Sprint Hero, I am even using a cache app that you have to be rooted to use so I KNOW I am rooted. The only problem is NO MATTER WHAT I try I can not successfully flash the recovery img. It shows as flashing ok but when I go to boot in recovery it either flashes the HTC sign real quick then dies or stays on the HTC screen and doesnt do anything. Ive literally been trying this for 2 days now! Ive rerooted 10 times, Ive tried as many different recovery imgs for CDMA that I could find and I STILL get the same result. I even switched sd cards!! Could there be a problem with my phone thats not allowing it to work? Someone please help this is driving me nuts! Im ready to return the phone and get a new one just to try it,LOL!!PPlease help??

What images have you tried?

Just ones Ive found around the internet. Most of them were recovery-RA-heroc-v1.2.3.img

How are you trying to install it?
Flashrec?
flash_image?

Anyone??? Please?????Im about to return it and try again Id hate to find out it was something simple cuz this Hero has been perfect except for this problem, which is pretty useless to have it rooted if I cant flash, And I wont be able to update if sprint has an update also correct??

packetlss said:
How are you trying to install it?
Flashrec?
flash_image?
Click to expand...
Click to collapse
I follow f directions online that I go into cmd and get to the root and type" flash_image recovery /sdcard/recovery-RA-heroc-v1.2.3.img, when I hit enter all that happens is it shows exactly what I typed AGAIN then just #
So it will look like this:
#flash_image recovery /sdcard/recovery-RA-heroc-v1.2.3.img
flash_image recovery /sdcard/recovery-RA-heroc-v1.2.3.img
#
Then when I type reboot recovery it just reboots and shuts off, so Ill pull the battery and try the hardware method power volume down and it does THE SAME thing or it will just stay stuck on the HTC screen.

Do it like that.
then then use the:
"reboot recovery" command on the # prompt. See if that helps.

packetlss said:
Do it like that.
then then use the:
"reboot recovery" command on the # prompt. See if that helps.
Click to expand...
Click to collapse
Ya I did that, same thing happened. ):

One last try.
Redownload the the image from this post: http://forum.xda-developers.com/showthread.php?t=581521
Download md5sum.exe from this site: http://www.etree.org/md5com.html
Save it in them in same folder as you have the adb command in.
Then from the command line run:
md5sum recovery-RA-heroc-v1.2.3.img
It should output something like this:
0bdcea0f2c734035ba960d76aba0fa6a *recovery-RA-heroc-v1.2.3.img (Don't forget to copy it to the sdcard again )
Bolded text is the checksum of the file, it should match perfectly or your image is damaged.
If the checksum is the same, try flashing it again.

ahh i see clearer now.....
yes as suggested in the last thread you posted in... do a sprint RUU and try agian... this will put you at a known good baseline.... follow steps exactly...
as a added measure to cancel the option of bad sd card, get an external micro sd card reader and format it in windows as fat32

johnsongrantr said:
ahh i see clearer now.....
yes as suggested in the last thread you posted in... do a sprint RUU and try agian... this will put you at a known good baseline.... follow steps exactly...
as a added measure to cancel the option of bad sd card, get an external micro sd card reader and format it in windows as fat32
Click to expand...
Click to collapse
I actually already formatted to fat32,lol. How do I flash RUU??? To start over?

packetlss said:
One last try.
Redownload the the image from this post: http://forum.xda-developers.com/showthread.php?t=581521
Download md5sum.exe from this site: http://www.etree.org/md5com.html
Save it in them in same folder as you have the adb command in.
Then from the command line run:
md5sum recovery-RA-heroc-v1.2.3.img
It should output something like this:
0bdcea0f2c734035ba960d76aba0fa6a *recovery-RA-heroc-v1.2.3.img (Don't forget to copy it to the sdcard again )
Bolded text is the checksum of the file, it should match perfectly or your image is damaged.
If the checksum is the same, try flashing it again.
Click to expand...
Click to collapse
Where do I input that? Once I get in root?
I did adb shell
$su
#md5sum recovery-RA-heroc-v1.2.3.img
it says md5sum not found

No, md5sum in run before you do the adb shell command (it's a normal PC program).

aaron130 said:
Where do I input that? Once I get in root?
I did adb shell
$su
#md5sum recovery-RA-heroc-v1.2.3.img
it says md5sum not found
Click to expand...
Click to collapse
windows command line not adb shell.... make sure you are in the directory in which you downloaded md5sum

obdcea0f2c734035ba960d76aba0fa6a *recovery-RA-heroc-v1.2.3.img
thats what happened Good??

That is the correct checksum.
Try and flash that one.

Nope Same DAM thing it gets stuck at htc or htc then quits and shuts off

I'm out of ideas then. Could be that it's broken, unless someone else has the same problem. (Haven't seen any of that though).

packetlss said:
I'm out of ideas then. Could be that it's broken, unless someone else has the same problem. (Haven't seen any of that though).
Click to expand...
Click to collapse
Thx Im flashing the RUU now. Thx for your help though I appreciate it alot!!

[Q] Asus TF101 Transformer Stuck Booting to Only Recovery

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

How To Root An AT&T HTC One X [No Longer Working]

This root was rendered unusable at this time due to AT&T disabling the Ready2Go app installation feature. Working on a work around now.
Original content:
http://www.androidpolice.com/2012/0...the-att-htc-one-x-on-version-1-85-or-earlier/

Hope you get your One X soon dude!
Confirmation number: 8PH11891CA483914J

In! Thanks Justin!
Billy

Damn, thanks a lot!

jcase said:
Now comes the timing critical part, you have to use ATT Ready2Go to Download "AT&T Mark the Spot", and interrupt the install process right after the download has finished. Easiest way is to reboot the device, but we have found other ways to do it.
Click to expand...
Click to collapse
OK, so when exactly do we reboot? There is no download status bar or whatnot, and I have rebooted right when it says install started to no avail. Do we have to do it before that point?
<---Not a noob, just crappy at timing.

id10terrordfw said:
OK, so when exactly do we reboot? There is no download status bar or whatnot, and I have rebooted right when it says install started to no avail. Do we have to do it before that point?
<---Not a noob, just crappy at timing.
Click to expand...
Click to collapse
You need to reboot right after the download is done. I haven't had a chance to do this in person, I just found it in the firmware and asked others to test for confirmation. Hopefully someone can chime in and tell us what visual indicators show when to do the reboot.
Some testers got it first try, some took 3-4 tries.

id10terrordfw said:
OK, so when exactly do we reboot? There is no download status bar or whatnot, and I have rebooted right when it says install started to no avail. Do we have to do it before that point?
<---Not a noob, just crappy at timing.
Click to expand...
Click to collapse
I'm with you on this one. I've been trying this for last hour but to no avail. The minute it says in status bar that it's installing, I tried command. I tried when I press finish on phone and LTE signals go up and down and even tried as soon as I was done with att site but can't get it to work. I've restarted 20 times and this startup sounds I think is now annoying other people in the office

jcase said:
You need to reboot right after the download is done. I haven't had a chance to do this in person, I just found it in the firmware and asked others to test for confirmation. Hopefully someone can chime in and tell us what visual indicators show when to do the reboot.
Some testers got it first try, some took 3-4 tries.
Click to expand...
Click to collapse
Hah, well now I just feel dumb as I am on try 10 or so. I must not be able to hit the timing right at all. I'll keep at it, as I am constant as the northern star.

Don't feel dumb, it is very timing critical, with few real indicators of when to pull it off.
Maybe xfinrodx or designgears can chime in on this one

noobsquared said:
I'm with you on this one. I've been trying this for last hour but to no avail. The minute it says in status bar that it's installing, I tried command. I tried when I press finish on phone and LTE signals go up and down and even tried as soon as I was done with att site but can't get it to work. I've restarted 20 times and this startup sounds I think is now annoying other people in the office
Click to expand...
Click to collapse
Turn your ringer off, it will silence the startup sound. At least I can help with that!

id10terrordfw said:
Turn your ringer off, it will silence the startup sound. At least I can help with that!
Click to expand...
Click to collapse
Thanks, but everytime I do factory reset...it comes back on?
I might be doing something dumb.
After I get permission denied error, I try to start at the process of tryping:
Code:
adb shell ln -s /data/local.prop /data/install/com.att.android.markthespot.apk
but when I do that after uninstalling AT&T Mark the spot, it gives me erorr:
link failed File exists
So I do a factory reset and then try again from scratch.
Is there an easier way to repeat the process?
Edit: I figured it out, just delete the file like this:
Code:
adb shell rm -r /data/install/com.att.android.markthespot.apk
Hope that's the right way of doing it.
Thank you.

I have been deleting the file from data/install
adb shell
cd data/install
rm com.att.android.markthespot.apk
exit
then repeat the process...i'm in double digits on attempts...going to have to walk away from it for a bit.

going on 10x for me and still nothing. Any suggestions?

id10terrordfw said:
OK, so when exactly do we reboot? There is no download status bar or whatnot, and I have rebooted right when it says install started to no avail. Do we have to do it before that point?
<---Not a noob, just crappy at timing.
Click to expand...
Click to collapse
No worries. Here's the way I did it back when I did it:
Open 2 cmd windows
adb devices on both (to make sure daemon is running)
In first shell type adb reboot but do not execute (obviously!)
In second window, cd /data/install
Enter ls -l
Now tell Ready2Go to install.
In that second window SPAM "up arrow - enter" to repeatedly execute ls -l. Observe the .apk file growing in size. When it stops growing it's probably done downloading (It is 3801413 bytes as of today). Go back to that first window IMMEDIATELY and hit enter on that adb reboot you typed in. It's a small apk so you need to be fast.
This was my method. Hopefully it works for you!

noobsquared said:
Thanks, but everytime I do factory reset...it comes back on?
I might be doing something dumb.
After I get permission denied error, I try to start at the process of tryping:
Code:
adb shell ln -s /data/local.prop /data/install/com.att.android.markthespot.apk
but when I do that after uninstalling AT&T Mark the spot, it gives me erorr:
link failed File exists
So I do a factory reset and then try again from scratch.
Is there an easier way to repeat the process?
Edit: I figured it out, just delete the file like this:
Code:
adb shell rm -r /data/install/com.att.android.markthespot.apk
Hope that's the right way of doing it.
Thank you.
Click to expand...
Click to collapse
Um, why are you doing a factory reset?
---------- Post added at 12:11 PM ---------- Previous post was at 12:10 PM ----------
xfinrodx said:
No worries. Here's the way I did it back when I did it:
Open 2 cmd windows
adb devices on both (to make sure daemon is running)
In first shell type adb reboot but do not execute (obviously!)
In second window, cd /data/install
Enter ls -l
Now tell Ready2Go to install.
In that second window SPAM "up arrow - enter" to repeatedly execute ls -l. Observe the .apk file growing in size. When it stops growing it's probably done downloading (I think it was around 5MB but it's been a while). Go back to that first window IMMEDIATELY and hit enter on that adb reboot you typed in. It's a small apk so you need to be fast.
This was my method. Hopefully it works for you!
Click to expand...
Click to collapse
I will give that a shot, and I should have thought of that. Thanks!

xfinrodx said:
No worries. Here's the way I did it back when I did it:
Open 2 cmd windows
adb devices on both (to make sure daemon is running)
In first shell type adb reboot but do not execute (obviously!)
In second window, cd /data/install
Enter ls -l
Now tell Ready2Go to install.
In that second window SPAM "up arrow - enter" to repeatedly execute ls -l. Observe the .apk file growing in size. When it stops growing it's probably done downloading (It is 3801413 bytes as of today). Go back to that first window IMMEDIATELY and hit enter on that adb reboot you typed in. It's a small apk so you need to be fast.
This was my method. Hopefully it works for you!
Click to expand...
Click to collapse
Good advice, was the first person to test it for me. I confirmed it with 4 users before posting, and all got it eventually.

id10terrordfw said:
I will give that a shot, and I should have thought of that. Thanks!
Click to expand...
Click to collapse
I was the first one I'm aware of who used this exploit a couple weeks ago. I won't claim that the process is clean, but it should work for you if you do it the way I intended the instructions to read... Good luck!

Thanks for all the help but I think this red bull is not working today.
Here is what I did:
First CMD:
Code:
adb shell
cd /data/install
ls -l <- it only gives me the file name..it doesn't tell me the size.
Also, I delete the file and run the first command in second CMD and right after that I see this in ls -l:
[email protected]:/data/install $ ls -l
ls -l
lrwxrwxrwx shell shell 2012-05-25 12:16 com.att.android.markthesp
ot.apk -> /data/local.prop
Second CMD:
Execute:
Code:
adb shell ln -s /data/local.prop /data/install/com.att.android.markthespot.apk
Wait to execute:
Code:
adb reboot

xfinrodx said:
No worries. Here's the way I did it back when I did it:
Open 2 cmd windows
adb devices on both (to make sure daemon is running)
In first shell type adb reboot but do not execute (obviously!)
In second window, cd /data/install
Enter ls -l
Now tell Ready2Go to install.
In that second window SPAM "up arrow - enter" to repeatedly execute ls -l. Observe the .apk file growing in size. When it stops growing it's probably done downloading (I think it was around 5MB but it's been a while). Go back to that first window IMMEDIATELY and hit enter on that adb reboot you typed in. It's a small apk so you need to be fast.
This was my method. Hopefully it works for you!
Click to expand...
Click to collapse
Great Idea !!!.... If you could post the exact size of the file , we can probably try to script it...( I have an idea in mind as mentioned below , but not sure if it works the way I intended in android )
for Ex:
szie=`ls -l /data/install/com.att.android.markthespot.apk | awk '{print $4}'`
while [ "$szie" -lt <size-of-apk> ];do
echo "waiting......"
done
adb reboot

dharani1234 said:
Great Idea !!!.... If you could post the exact size of the file , we can probably try to script it...( I have an idea in mind as mentioned below , but not sure if it works the way I intended in android )
for Ex:
szie=`ls -l /data/install/com.att.android.markthespot.apk | awk '{print $5}'`
while [ "$szie" -lt <size-of-apk> ];do
echo "waiting......"
done
adb reboot
Click to expand...
Click to collapse
If you can get a working script, that was reliable I would love to post it in the OP. To get an idea of the size, you could install the app, and do adb shell ls -l /data/app/<filename>

Recovery Problem.

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

TF101 booting into Recovery

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