Database Info

Need help restoring device, big problem, read inside

Could someone please help me with this? I have posted a thread over on Android Forums with all the problems.
http://androidforums.com/asus-eee-p...restoring-device-big-problem-read-inside.html
Also, I have posted on here in the past about this, but I honestly am a giant noob at android and did not know what they were telling me to do.
Any help would be really great, thanks!

Since you can still boot your OS, you should be in good shape.
Try installing GooManager from the Play Store.
After installed, open it and grant root permissions.
Next, tap the menu key in the top right (3 stacked boxes) and then choose the Install OpenRecovery Script. This will install TWRP recovery which is far superior to any CWM I have ever run.
See if that installs properly (if yes, you will end up in TWRP recovery during a reboot)
TWRP allows you to see the internal and external memory to flash new ROMs.

frederuco said:
Since you can still boot your OS, you should be in good shape.
Try installing GooManager from the Play Store.
After installed, open it and grant root permissions.
Next, tap the menu key in the top right (3 stacked boxes) and then choose the Install OpenRecovery Script. This will install TWRP recovery which is far superior to any CWM I have ever run.
See if that installs properly (if yes, you will end up in TWRP recovery during a reboot)
TWRP allows you to see the internal and external memory to flash new ROMs.
Click to expand...
Click to collapse
I will try this out when I get home. Thank you. I will report back with what happens.
Edit: Also congratulations on 100 thanks.

format your micro SD and only put the ROM you want in it. Now install twrp as other guy said and reboot into twrp recovery in go to wipe and wipe (dalvik, cache, internal memory, system and everything else expect micro SD). Then do a clean installation of ROM and you should be good to go.. if that doesn't work then try easy flash
Sent from my Transformer using xda app-developers app

frederuco said:
Since you can still boot your OS, you should be in good shape.
Try installing GooManager from the Play Store.
After installed, open it and grant root permissions.
Next, tap the menu key in the top right (3 stacked boxes) and then choose the Install OpenRecovery Script. This will install TWRP recovery which is far superior to any CWM I have ever run.
See if that installs properly (if yes, you will end up in TWRP recovery during a reboot)
TWRP allows you to see the internal and external memory to flash new ROMs.
Click to expand...
Click to collapse
This did not work, I still boot into cwm when the device restarts after downloading it.

Here is another thing to try:
If you can boot and want to try TWRP, here is another way to install it so long as you are rooted:
Download the 2.3.2.3 blob from HERE
Place the recovery blob in the /sdcard/ directory. We are going to pretend the downloaded file is called TWRP.blob
Open a terminal window and enter these commands
Code:
su
cd /sdcard/
ls
dd if=TWRP.blob of=/dev/block/mmcblk0p4
reboot recovery
the ls will tell you if the blob is indead where it is supposed to be, if it can be seen, you should be good to go on to the dd command, if you don't see the file, do not procede.
Make sure to change TWRP.blob to the actual name and location of the file you downloaded
Let me know how it goes

frederuco said:
Here is another thing to try:
If you can boot and want to try TWRP, here is another way to install it so long as you are rooted:
Download the 2.3.2.3 blob from HERE
Place the recovery blob in the /sdcard/ directory. We are going to pretend the downloaded file is called TWRP.blob
Open a terminal window and enter these commands
Code:
su
cd /sdcard/
ls
dd if=/TWRP.blob of=/dev/block/mmcblk0p4
reboot recovery
the ls will tell you if the blob is indead where it is supposed to be, if it can be seen, you should be good to go on to the dd command, if you don't see the file, do not procede.
Make sure to change TWRP.blob to the actual name and location of the file you downloaded
Let me know how it goes
Click to expand...
Click to collapse
I cannot connect the device to my computer at all. I have usb debugging enabled and everything. It freezes for a couple of seconds when I plug the device in, and then says that installing the drivers has failed in windows. I am trying to run adb and it says no devices are connected.

BloodyRory said:
I cannot connect the device to my computer at all. I have usb debugging enabled and everything. It freezes for a couple of seconds when I plug the device in, and then says that installing the drivers has failed in windows. I am trying to run adb and it says no devices are connected.
Click to expand...
Click to collapse
You don't need to do this on your PC, so long as you can boot you can do it on your tablet.

frederuco said:
You don't need to do this on your PC, so long as you can boot you can do it on your tablet.
Click to expand...
Click to collapse
Ah, sorry, long time since I've done this. Alright, well I've gotten into terminal emulator and I've typed that exactly, switching over my directory to my microsd though and changing the file name to the exact one. I'm getting a "cannot open for read: No such file or directory" error when I do this. I have also tried moving the file to /sdcard/ and I have named the file twrp.blob, and neither of these have helped.

Did you issue the su command and get a popup for root access?

frederuco said:
Did you issue the su command and get a popup for root access?
Click to expand...
Click to collapse
Yes, that was the first thing I did. I did exactly as you said. I've tried changing file names, changing directories and everything but for some odd reason I'm getting the same error.
Edit: and yes, I'm changing those when I enter them in terminal as well.

Strange.
I'll have to troubleshoot this in a bit. I'll let you know what I find.

frederuco said:
Strange.
I'll have to troubleshoot this in a bit. I'll let you know what I find.
Click to expand...
Click to collapse
Thank you. Here is an image of what I have typed in case it is an error on my part.
http://i.imgur.com/lyJU8MR.jpg

Nope, error is on my part. Remove the "/" after the if=
It should be
dd if=TWRP.blob of=/dev/block/mmcblk0p4
Will update the other posts above.

frederuco said:
Nope, error is on my part. Remove the "/" after the if=
It should be
dd if=TWRP.blob of=/dev/block/mmcblk0p4
Will update the other posts above.
Click to expand...
Click to collapse
And it appears that I am still in clockworkmod when the device boots up.

BloodyRory said:
And it appears that I am still in clockworkmod when the device boots up.
Click to expand...
Click to collapse
Try a normal reboot at the end instead of reboot recovery and see if that works.
If not, run through this and download one of the flashable .zip files (it is version 2.2.X.X) and see if that works. If so, then run through GooManager to get the 2.3.2.3.

Guide to fix TWRP or CWM bootloop

This is how i fix my TF300TG stuck on recovery. I hope the steps descried below will help.
Long story, short:
For some reasons, seems like the WIPE command from TWRP and CWM recovery screw the partitions.
No partitions or microSD card can be mounted.
The tablet is now booting only in recovery mode or in fastboot mode (the screen with three icons - RTK, Android and WIPE) instead of Android.
IMPORTANT:
If your tablet reboot in fastboot mode DONT WIPE IT AGAIN! Just skip step 4.
First of all, MAKE SURE YOR BATTERY IS CHARGED!
Recharge your tablet for at least two hours.During the flashing process the tablet doesn`t charge.
Use the original Asus USB cable that came with the tablet or a high quality replacement cable. Cheap cables can and will cause problems.
Use a laptop or desktop with known good USB ports. If you have problems, try a diferent computer, some USB chips can cause troubles.
Disable the antivirus or screensaver, sleep etc...
1.Download these files:
from ASUS website: http://www.asus.com/Tablets_Mobile/ASUS_Transformer_Pad_TF300TG/#support
Drivers&Tools, on the OS tab select Android
click on Utilities and download latest version of ASUS PC Sync (you will need this for drivers)
click on Firmware and download the lastest available (you will need this for BLOB file)
Minimal ADB and Fastboot: http://d-h.st/gbx
install ASUS PC Sync and Minimal ADB and Fastboot (on fastboot installer check the box that make a shortcut to desktop)
unzip the firmware file downloaded from ASUS site
you will get a second zip file, unzip this one too
the folder unzipped from the second one contain a file called blob
copy or move the folder to the root of your drive C: or D: or whatever drive letter you have
2.Installing drivers:
connect your tablet to PC
you will get a message about Windows couldnt find driver bla...bla, ignore it and keep your tablet plugged
IMPORTANT: even if you previously installed ASUS PC Sync or other drivers and Windows recognize your tablet, you still need to change the driver.
right-click on My Computer-Properties and click Device Manager
find the Asus Android device - should be with an exclamation mark on it (the driver is not installed sign)
right-click on it and choose:
Update Driver Software..., Browse my computer for driver software, Let me pick from a list of device drivers on my computer, Have disk, Browse
go to C:\Program Files or Program Files (x86), ASUS, ASUS Android USB Drivers, Android and select android_winusb.inf
Asus Android Composite ADB interface will appear in the list of device drivers - don`t hit next yet!
uncheck Show Compatible Hardware and select Asus Android Bootloader Interface from the list, now hit next
3.ADB mode:
open Minimal ADB and Fastboot from desktop - from this point, keep it open
type: adb devices - and you should see some numbers under the List of device attached - thats your tablet
if you can`t see the tablet, try this command: adb start-server
4.Booting to "fastboot":
there are two ways to do this:
a) from adb window type: adb reboot bootloader
or
b) reset and hold vol-down (didn`t work for me, but maybe will work for someone else)
the three icons will appear on screen - NOW YOU ARE IN FASTBOOT MODE
if none of the above work try this:
in adb window type: adb reboot
wait until the tablet enter in recovery menu and type in adb window:
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3
adb reboot bootloader
5. Flasing the blob
the credits for this part goes to buster99. He is the one who figured out the right commands for formatting partitions and flashing back the OS
here is his post: http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
here we go, one at the time in adb window:
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system x:\your blob folder\blob (here you enter the path to your blob file, must end with blob, to point at the file)
fastboot -i 0x0B05 reboot
THE FLASH SYSTEM COMMAND WILL TAKE SOME TIME
be pacient and wait until the progress bar is 100% full on the tablet and you get the command prompt back in the adb window.
After reboot, the Android is back on.
Cheers and good luck!!

A big thank you alexhosu,
several months ago that my tablet was blocked, but I still kept hope
a solution would be found. I'm really happy for you and thank you again for sharing.
Long live XDA

me too
Thanks from me too; was enjoying 5.0 (timduru) on my TF300 when I went to upgrade and idiotically managed to get into a TWRP bootloop(interrupted a format of \data and then used 'wipe' from the boot screen by mistake...)
Your solution has saved my tablet
Am now carefully reinstalling Katkiss

Thanks
This saved my (veggie) bacon too, something went wrong when flashing new ROM (most likely user error - e.g. my fault). Tablet woud go into an eternal boot wouldn't finish booting, nandroid recovery did the same. Used this technique and have a working stock ROM from which I intend to reinstall TimDuru's Lollipop.
Thanks again

Followed the instructions.. Worked well, but getting error 963 when installing/updating anything in Play Store. Seems to be related to storage permissions. Some users are suggesting using format instead of erase. What's the difference? Could that help.
I did factory reset, reflashed and used fix permissions in TWRP but no luck...
alexhosu said:
This is how i fix my TF300TG stuck on recovery. I hope the steps descried below will help.
Click to expand...
Click to collapse

Big thanks from me.
I killed my tablet with an accidental restore to factory defaults while in cm12, an got stuck in an endless bootloader boot loop.
my tablet came back too life at the end of section 4 after adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3.
although getting adb to talk to the tablet was a fluke.
I just kept trying to send "adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3" while the tablet was loading (boot looping)

6 months of believing my tablet was dead, after letting CM12 do its own update thing, and now, thanks to the above instructions, I'm back online and its working with the stock rom.
Thank you so much for this. No idea why I couldn't find these instructions before, then I just gave up, back in business now!

Thanks a lot for your guide, this is what helped me fortunately unbrick my device, i was stuck in a boot loop with a broken recovery

Another tablet saved. Know your work is appreciated.

i have the same problem, the system doesn't pass the ASUS logo, i tired to log into fastboot (reset + volume down) and i was able to see the three icons but adb doesn't recognize my device. i see the drivers are correctly installed but no working adb. Any help is highly appreciated.

ajeevlal said:
i have the same problem, the system doesn't pass the ASUS logo, i tired to log into fastboot (reset + volume down) and i was able to see the three icons but adb doesn't recognize my device. i see the drivers are correctly installed but no working adb. Any help is highly appreciated.
Click to expand...
Click to collapse
Did you try entering "fastboot devices" or just "adb devices"? adb wont find your device in the bootloader, but using fastboot commands should unless it truly is not connecting for some reason.

Act32.97 said:
Did you try entering "fastboot devices" or just "adb devices"? adb wont find your device in the bootloader, but using fastboot commands should unless it truly is not connecting for some reason.
Click to expand...
Click to collapse
yeah Fastboot devices worked but it was not letting me flashing the rom, when i push the blob file it says 'sending' and stays in the same state for days.

ajeevlal said:
yeah Fastboot devices worked but it was not letting me flashing the rom, when i push the blob file it says 'sending' and stays in the same state for days.
Click to expand...
Click to collapse
I would try moving the blob to the root of the C drive and try the 7th command "fastboot -i 0x0B05 flash system C:\blob" just to make sure sometime of file permission type issue isn't happening on the pc side. Other than that the only kind of issue I think it could be would have to be the connection with the drivers, although if erasing the partition's works fine, I don't really see what could be going on.

I followed all the steps and delete, but when loading the file update.blob I get this error:
C: \ Users \ mikel> C: \ Users \ mikel \ Android \ android-sdk \ platform-tools \ fastboot flash system update.blob
error: can not load 'update.blob'
Can someone help me out?

TF300T KissKat
Theziggy said:
This saved my (veggie) bacon too, something went wrong when flashing new ROM (most likely user error - e.g. my fault). Tablet woud go into an eternal boot wouldn't finish booting, nandroid recovery did the same. Used this technique and have a working stock ROM from which I intend to reinstall TimDuru's Lollipop.
Thanks again
Click to expand...
Click to collapse
Hey, I know that I'm a couple years late on this. But, I was just given a Asus Transformer TF300T, and attempted to install the Kisskat custom rom. I unlocked the device with little issues. Rooted with little issues. But when it came to flashing the rom. I get his error saying that "no MD5 file found" and holds it there for a couple of minutes. Then gives me the failed install. My only option is to boot into recovery and restore the stock JB 4.2. If you could point me in the right direction, I would greatly appreciate it. I've searched the forum for someone with a similar issue, and couldn't find it. I hope that I'm not alone on this one. It would kill me to be stuck with the stock rom.

Hi i made a format data from TWRP recovery, and now i am in a recovery loop and got error of mount partitions, i can access to recovery and the screen with 3 icons, but when i plug to my pc it shows as uknown usb, i install the drivers but dosent reconose as a fastboot device, in minimal adb when i write fastboot devices the result is empty pleace help me.

Muito obrigado!
I know this must seem odd, being such an old thread and all but, after several years adding apps and changing ROMs on my wife's TF300T (my gift!) only these past weeks I had the need to search for help, after installing nougatella 7.1, which I did with success, only to stumble on endless logo loops and loading processes without conclusion. Don't get me wrong, the ROM looks great and it wasn't that hard to install but, after two weeks or so, gave me this problem and after correcting it and installing again the ROM, I got in trouble again...
After some five hours googling and trying different stuff, I finally found this thread and twenty minutes ago (around 2:AM) my ASUS returned to its (Jellybean) life!
Alexhosu, thank you so very much for such a detailed, yet easy to follow guide and, if you happen to come to Portugal on vacation and visit Setúbal, I'll have a bottle of Moscatel waiting for you!
Many thanks to Droidbound (who got me off the hook the first time the tablet went nuts!), and also Kevinthefixer, Gtanner00 and some other very inteligent, patient and thoughtful people, and all the guys who shared their difficulties and in a way helped me find the people with the fix.
For anyone interested in trying this method, I would say that it's paramount that you should stick exactly with what is asked and should pay real atention to what is the correct ROM update to download and use. If anyone needs help with translation to Portuguese, just say so.
Again, thank you so much for this!
JMonteiro

alexhosu said:
This is how i fix my TF300TG stuck on recovery. I hope the steps descried below will help.
if none of the above work try this:
in adb window type: adb reboot
wait until the tablet enter in recovery menu and type in adb window:
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3
adb reboot bootloader
5. Flasing the blob
Click to expand...
Click to collapse
Thanks for your help :good: and I'm sorry for my basic English, but here is another tablet saved. Your instructions were clear and my tablet is working.
I hope this information helps, based in the next link (user sszyman): https://forum.xda-developers.com/showthread.php?t=2275035&page=9
in which he recommends using the following commands too:
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p2
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p8
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p1
With these commands and "adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3" I was able to solve my Bootloop problem.
Honestly I don't know which of the commands worked, I used all several times.

No fastboot, TWRP flickering screen

Hello people,
First of all, I'm not an expert so pardon on that.
I had a MicroSD card in my tablet and it was partitioned using GParted, 2 partitons - fat32 and ext4. I erased the whole tablet with Wipe option in TWRP and installed move2sd.zip.
Anyway... When I pressed Reboot to recovery, tablet restared, showed TWRP and screen went on and off showing TWRP logo, like it was trying to load TWRP. Now... Since I installed that .zip file it might have written some code to use MicroSD card as boot? I reinstalled TWRP by flashing it via fastboot and was able to enter TWRP again.
Now the stupid part... Since it read 0mb on internal card (tablet), I wanted to fix it by formating Data... It didnt do the trick cause /data and other folders couldn't have been found. That's where I restarted the tablet and pressed Wipe data on the screen with 3 icons (RCK, Android, Wipe data)... Since then I only see 2 screens - bootup screen with Asus logo and message: Device is unlock and the next screen is TWRP and it flickers again, goes on and off just as if it was trying to load TWRP.
I cannot reflash recovery cause there is no fastboot?
I just hope this is not an expensive paper...

djakolis said:
Hello people,
First of all, I'm not an expert so pardon on that.
I had a MicroSD card in my tablet and it was partitioned using GParted, 2 partitons - fat32 and ext4. I erased the whole tablet with Wipe option in TWRP and installed move2sd.zip.
Anyway... When I pressed Reboot to recovery, tablet restared, showed TWRP and screen went on and off showing TWRP logo, like it was trying to load TWRP. Now... Since I installed that .zip file it might have written some code to use MicroSD card as boot? I reinstalled TWRP by flashing it via fastboot and was able to enter TWRP again.
Now the stupid part... Since it read 0mb on internal card (tablet), I wanted to fix it by formating Data... It didnt do the trick cause /data and other folders couldn't have been found. That's where I restarted the tablet and pressed Wipe data on the screen with 3 icons (RCK, Android, Wipe data)... Since then I only see 2 screens - bootup screen with Asus logo and message: Device is unlock and the next screen is TWRP and it flickers again, goes on and off just as if it was trying to load TWRP.
I cannot reflash recovery cause there is no fastboot?
I just hope this is not an expensive paper...
Click to expand...
Click to collapse
You can still enter RCK ??

Not that this helps your situation, so apologies.
Just started getting the screen flicker/lines randomly when handeling it. So my guess was just the loosining of something internally.
I`m also freecarding it. So that hadden`t crossed my mind.
Time for a tear down vid I guess.
Best of luck tho.

I'll make a quick video. Be right back to you...
Edit: I cannot post a video due to XDA rules, but you can search for it: TF700 no fastboot, recovery stuck (search for recent uploads, d jakolis is my username on YouTube) If you guys cannot find it, I can email the link to you.

As you can see in the video, there is not much left to do with the tablet.
However, when I selected Wipe Data on bootloader, did it wipe kernel too? I'm asking this cause I had installed data2sd.zip along with its corresponding kernel.
What would happen if someone else with the same device installed the custom ROM on MicroSD card and handed me his MicroSD card to pop in my tablet? Would it boot off it? Would I be able to enter Android and maybe somehow re-flash recovery and stock kernel along with stock ROM?

You should still be able to connect via adb. Try adb pull /tmp/recovery.log and adb logcat.

_that said:
You should still be able to connect via adb. Try adb pull /tmp/recovery.log and adb logcat.
Click to expand...
Click to collapse
Tried adb pull /tmp/recovery.log and got recovery.txt file.
Adb logcat showed this: /sbin/sh: exec: line 1: logcat: not found

djakolis said:
Tried adb pull /tmp/recovery.log and got recovery.txt file.
Adb logcat showed this: /sbin/sh: exec: line 1: logcat: not found
Click to expand...
Click to collapse
Looks like your /data partition is not formatted properly. Try this (don't type "#" and the following comment):
Code:
adb shell # connect to a shell on the device
killall -19 recovery # suspend the recovery so that it doesn't interfere with formatting
make_ext4fs /dev/block/mmcblk0p8 # format /data
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1 # remove "wipe data" request
reboot

Wow... I don't know what to say. I'm looking at the fastboot screen! :highfive:
I didn't type the last line of your code because it rebooted itself after format data was complete - make_ext4fs... Is there any consequence for not typing the last line?
Alright, I'm in recovery right now. Question: What is installed on the tablet right now? If anything... May I proceed with installing stock ROM and maybe do nvflash process to have an unbrickable device?
P.S. What does it take to learn all these things? I'm curious cause I like coding, so if you feel happy to share it, I'm all ears.

djakolis said:
Wow... I don't know what to say. I'm looking at the fastboot screen! :highfive:
I didn't type the last line of your code because it rebooted itself after format data was complete - make_ext4fs... Is there any consequence for not typing the last line?
Click to expand...
Click to collapse
Maybe the "killall -19" stuff didn't work and the recovery was not suspended, so it may have somehow determined that the wipe was finished and initiated a reboot.
djakolis said:
Alright, I'm in recovery right now. Question: What is installed on the tablet right now? If anything... May I proceed with installing stock ROM and maybe do nvflash process to have an unbrickable device?
Click to expand...
Click to collapse
What is installed? Whatever recovery, kernel and ROM you installed last. No other apps since you just formatted /data.
Since the nvflash (flatline) process saves only BCT, bootloader, partition table and unlock token (basically all the stuff you need to get fastboot working on a hard bricked tablet), you can do that now.
djakolis said:
P.S. What does it take to learn all these things? I'm curious cause I like coding, so if you feel happy to share it, I'm all ears.
Click to expand...
Click to collapse
Lots of reading here, lots of googling and more reading. Experience with Linux on PCs helps too.

where can i wirte this codes i dont know , can anyone help me??? i have same problem

i can not connect device also in adb mode pc didnt accept the drivers

y3akup said:
i can not connect device also in adb mode pc didnt accept the drivers
Click to expand...
Click to collapse
If you can still enter recovery (which one do you have?) you can use the build in Terminal.
Otherwise you have to get the adb drivers installed and working. There is no other way if you do not have a working recover and cannot get into fastboot.
Try this tool: http://forum.xda-developers.com/showthread.php?t=2588979
Once you get the drivers installed boot the tablet to recovery and post what you get with this command:
Code:
adb devices

berndblb said:
If you can still enter recovery (which one do you have?) you can use the build in Terminal.
Otherwise you have to get the adb drivers installed and working. There is no other way if you do not have a working recover and cannot get into fastboot.
Try this tool: http://forum.xda-developers.com/showthread.php?t=2588979
Once you get the drivers installed boot the tablet to recovery and post what you get with this command:
Code:
adb devices
Click to expand...
Click to collapse
i tried this tool before but still in the device manager page i have transformer device with yellow flag

y3akup said:
i tried this tool before but still in the device manager page i have transformer device with yellow flag
Click to expand...
Click to collapse
You need to install the drivers - right click on the yellow ? and choose install drivers
Use these ones here:
http://www.androidfilehost.com/?fid=23329332407571009
http://www.androidfilehost.com/?fid=2332933240

now i have
0123456789ABCDEF recovery
but commands that from other posts didnt work

y3akup said:
now i have
0123456789ABCDEF recovery
but commands that from other posts didnt work
Click to expand...
Click to collapse
Try this command only:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1
Copy and paste it into your cmd window

sorry but it says dd is not inside or outsite command and bla bla i cant translate directly but like this
is not recognized as an internal or external command, operable program or batch file

berndblb said:
Try this command only:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1
Copy and paste it into your cmd window
Click to expand...
Click to collapse
now i could enter the recovery and nearly ten times i installed rom but still it couldnt open twrp and bootloader numbers i checked but i think i did something wrong what can i do now??

y3akup said:
now i could enter the recovery and nearly ten times i installed rom but still it couldnt open twrp and bootloader numbers i checked but i think i did something wrong what can i do now??
Click to expand...
Click to collapse
Splendid!
Now - did you a full wipe in TWRP before installing the rom? Select the Wipe option and swipe the button. Then re-install the rom.
On the last page of the Aroma installer you have the option of saving the installation log. Do it.
Then back to TWRP, go to Advanced and also save the recovery log.
If the ROM still doesn't boot, post both of those logs.
Also try to capture a logcat of the boot process
Code:
adb logcat -v long > logcat.txt
Post that one too.

[Q] TWRP in a start-loop on my TF700

With the latest version of TWRP (2.8.5.0) I installed that zombi 5.02 rom a few days ago. It was running VERY slow, so I went back into TWRP a few hours ago and figured I would clean up the device and then re-install the rom.
So I used TWRP to wipe the device clean (I selected every partition to wipe, which I suspect is what the problem is). After doing this, I ran the install of the rom which seemed to run fine (although oddly, it seemed to install too fast, as opposed to when I installed it before).
Once I rebooted the device, I saw a quick message about a missing partition, and then it booted into TWRP recovery. but here is where the problem started. TWRP loads as far as you see the blue curtain background with test "teamwin" and then the screen clears for a sec, and then the blue curtain background appears again with the "teamwin" text.
This repeats forever. I can't get it to stop doing this.
I booted into fastboot, and via adb I re-installed the 2.8.5.0 twrp blob file. No errors during the install at all, however after rebooting the device, I am having the exact same issue.
I've tried re-installing twrp 3 times this way, but no matter what I do, I cannot get twrp to get out of this boot cycle.
It is odd that I can install twrp via adb over and over, yet it still has the same problem as before.
Even if i messed up by wiping every partition, why would the TWRP install succeeed, yet the program not run?
Anybody have an idea as to what I can do in order to get twrp back up and running? And if I do, is there something else I need to do to get all the partitions back up, or in theory will installing a rom re-create everything as needed?
Thanks for any help you guys can provide!

gbako said:
Once I rebooted the device, I saw a quick message about a missing partition, and then it booted into TWRP recovery. but here is where the problem started. TWRP loads as far as you see the blue curtain background with test "teamwin" and then the screen clears for a sec, and then the blue curtain background appears again with the "teamwin" text.
This repeats forever. I can't get it to stop doing this.
Click to expand...
Click to collapse
While TWRP is in the restart loop, you can try this on your connected PC:
Code:
adb pull /tmp/recovery.log
adb shell cat /proc/partitions > partitions.txt
The first gets TWRP's log file from which we should be able to see why it fails to start, the second gets a list of all partitions to see if mmcblk0p1 to ...p8 or ...p10 are there.

_that said:
While TWRP is in the restart loop, you can try this on your connected PC:
Code:
adb pull /tmp/recovery.log
adb shell cat /proc/partitions > partitions.txt
The first gets TWRP's log file from which we should be able to see why it fails to start, the second gets a list of all partitions to see if mmcblk0p1 to ...p8 or ...p10 are there.
Click to expand...
Click to collapse
--
I retrieved the logs as you suggested. I did this twice because after I retrieved the logs, I was looking at the partitions.log file and saw that only 3 partitions appeared. I know there should be more partitions (I don't know what they are called, but I know there should be more). So I was playing around with the fastboot.exe command, and I saw a command (fastboot -w). It said this command "erases userdata and cache". Well, it looked like something good to try, so I ran the command I've attached a file to this post called "fastboot.txt" that shows the output of this command.
Anyways, after doing this (thinking maybe this would do something), I went back into fastbook, and re-installed TWRP once again. Then I rebooted the tablet, and viola! It booted into twrp. Think I was so smart, I figured I would try to install my rom once again, so I started the installer of the rom, but at the very first screen of the installer where it shows device information, I saw what was obviously an issue. System size was showed as -1 MB, and Data Size was also shown as -1 MB. Not looking good, I exited the installer which puts me back into TWRP, and now I see a bunch of error messages about missing partitions.
On a hunch, I rebooted the tablet (back into reovery), and now I am back to the same thing, where TWRP will constantly load the blue curtain backgroud, show the word "teamwin" and then clear the screen, and repeat the process endlessly. So I now re-ran the two commands to retreive the partition info and the recovery log. The recovery log doesn't make much sense to me, but interestingly the partition log now shows a whole bunch more partitions. However, TWRP is once again back to it's boot loop.
So rather than re-trying my silly "fastbook -w" attempt, I will post this message, provide the request log info, and hope one of the experts here have a kind suggestion for me to try
Thanks guys for any help!
P.S. All the logs are in the ZIP file. I also attached a pic I took of the zombi rom installer, showing the partition size being -1 MB
The files "partitions1.txt" and "recovery1.log" are the files I retrieved from the tablet prior to using that "fastboot -w" command, the "partitions2.txt" and "recover2.log" are the files I retrrieved from the tablet after running that command, re-installing twrp and then having it go back into it's endless boot loop.

gbako said:
The files "partitions1.txt" and "recovery1.log" are the files I retrieved from the tablet prior to using that "fastboot -w" command, the "partitions2.txt" and "recover2.log" are the files I retrrieved from the tablet after running that command, re-installing twrp and then having it go back into it's endless boot loop.
Click to expand...
Click to collapse
Your logs indicate a problem with the "cache" partition. TWRP seems to crash after "Full SELinux support is present", and the next thing it does is trying to mount the cache partition. Your Fastboot log indicates a problem with cache too.
Try this:
Code:
adb shell make_ext4fs /dev/block/mmcblk0p2
(make sure you get the "p2" right *before* you press Enter!)
If this doesn't help, I also need the kernel log - do this after the previous command failed or within the first 3 minutes of a fresh boot into TWRP:
Code:
adb shell dmesg > dmesg.txt

That worked! Tablet works once again!
_that said:
Your logs indicate a problem with the "cache" partition. TWRP seems to crash after "Full SELinux support is present", and the next thing it does is trying to mount the cache partition. Your Fastboot log indicates a problem with cache too.
Try this:
Code:
adb shell make_ext4fs /dev/block/mmcblk0p2
(make sure you get the "p2" right *before* you press Enter!)
If this doesn't help, I also need the kernel log - do this after the previous command failed or within the first 3 minutes of a fresh boot into TWRP:
Code:
adb shell dmesg > dmesg.txt
Click to expand...
Click to collapse
---
That worked! Shortly after running that "adb shell make_ext4fs /dev/block/mmcblk0p2" command you had suggested, the tablet rebooted it self and the last ROM I had installed in it automatically booted up. It acted as though I had just installed it, so I went thru the standard setup (enter Google ID, etc...). The rom still runs pretty horribly (very slow and sluggish), but that's an issue with the rom hehe I am also able to boot back into TWRP without any problems. It seems that partition was the problem.
Thank you very much for your help; much appreciated!

I had the same problem with my TF700T with an endless loop in the TWRP start screen. I found an unkown device in my device manager called "TRANSFORMER" and i installed the Universal_Naked_Driver. Now i had access with ADB and i could clean the cache with the command here. Now my TF700T is back to life. Thanks a lot !

I seem to have a similar problem. The pad started having random reboots but it managed to fully boot. Since yesterday it is in the reboot loop. When trying to boot into twrp 2.8.7.4 it shows the teamwin screen for a short while and then reboots again.
I pulled the files requested above:
recovery.log
partitions.txt
dmesg.txt
I also tried:
Code:
adb shell make_ext4fs /dev/block/mmcblk0p2
which shows:
Code:
C:\adb>adb shell make_ext4fs /dev/block/mmcblk0p2
Creating filesystem with parameters:
Size: 448790528
Block size: 4096
Blocks per group: 32768
Inodes per group: 6848
Inode size: 256
Journal blocks: 1712
Label:
Blocks: 109568
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/27392 inodes and 3534/109568 blocks
However the recommended steps don't seem to help in my case.
I'll attach the log files. (If I can find the attachment icon that is)
Thanks for any help you guys can provide!

Rom and bootloader version please. To attach the logs use your browser to access XDA

Hi berndblb,
thanks for the quick reply.
Rom version is : KatKiss-6.0_TF700T_022.zip
Boot loader taken from the fastboot screen: Android cardhu-user bootloader <1.00e> released by "ww_epad-10.6.1.14.10-20130801" A03
As to attaching the files I think I'm blind as I'm not seeing the option to do so.
Looks like this is only an issue in this threat as I do have the icon in other posts.

Yeahh I think I got it.
After much trying various recommendations I did
fastboot erase misc
fastboot erase userdata
This allowed me finally to go into recovery without a reboot.
I could flash the new KatKiss-6.0_TF700T_024.zip and now the pad is on it's first startup. So far so good. Crossing fingers.
Is it possible that a recently installed app could cause such a problem?

Cathrin said:
Yeahh I think I got it.
After much trying various recommendations I did
fastboot erase misc
fastboot erase userdata
This allowed me finally to go into recovery without a reboot.
I could flash the new KatKiss-6.0_TF700T_024.zip and now the pad is on it's first startup. So far so good. Crossing fingers.
Is it possible that a recently installed app could cause such a problem?
Click to expand...
Click to collapse
Hard to say... Could be...
I am not very good at reading logs but the only problem I see in dmsg is a failure to set cpu frquency. Were you running Zombi-Pop? Looks as if you were running a _that kernel at least. Did you overclock?

berndblb said:
Hard to say... Could be...
I am not very good at reading logs but the only problem I see in dmsg is a failure to set cpu frquency. Were you running Zombi-Pop? Looks as if you were running a _that kernel at least. Did you overclock?
Click to expand...
Click to collapse
I think my very first upgade to 5.1.1. lolli pop has been a Zombi-Pop and a overclocking yes. But since then only the KatKiss versions.
At least everything works fine again now.
So thanks for the help.

Looks like I have this constantly boot to twrp issue. It doesn't stay into twrp long enough to do anything.
adb pull /tmp/recovery.log
Gives me error: Protocol fault (couldnt read status: no error
adb shell cat /proc/partitions > partitions.txt
Gives me the same error above.
adb shell make_ext4fs /dev/block/mmcblk0p2
Gives me filesystem with parameters----created filesystem with 11/27392 inodes and 3534/109568 blocks
fastboot erase misc
Gives me waiting for device
I was on Katkiss 22 before this happened.
Any help would be appreciated.

Hi Isham.padron,
yes that sounds familiar.
I could only get the logs with adb shell or put when I hit return at a very specific moment.
It did fetch the files only when the blue teamwin window has been shown.
Though my recovery.log always looked a bit too short as if the reboot was coming in the way.
for me in the end only fastboot erase userdata did the trick. Everything else failed.

fastboot erase userdata cause it to wait but then nothing happens. ADB seems to be more responsive. IDK, I loved my TF700 and Katkiss gave it new life.

If you get 'waiting for device' your pc does not recognize the tablet. You may have to install fastboot drivers. Check the entry in Device Manager. How does the tablet show up?

In device manager is shows up as ADB. That kind of explains it. I'm using a windows 10 pro machine and I installed ADB/Fast boot with this http://forum.xda-developers.com/showthread.php?t=2588979
Are there issues with Win 10? I dont know how to proceed.
When I do the vol up(left) and power combo and it boots into twrp and then reboots regardless. I don't have the option screen anymore

Did you disable driver verification in Windows before running the tool? Otherwise they probably did not install properly. Windows is a pain with drivers and Win 8 and 10 are very finicky with fastboot...
Although if you have the adb composite interface showing up that's kinda good news. Watch the tablet and Device Manager at the same time and try to get a feeling for when the adb connection is there. Try to hit enter on the already typed 'adb devices' command and see what you get.
This could be tricky and rake many tries but you want to try is to push a small file to the tablet (bootit. ko) and then ins is that file to kick the tablet back into the bootloader. Probably your only chance..
Read this: http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Good luck!

I am able to do this.
adb push bootit.ko /
results are (27690 bytes in .023s)
When I run "adb shell insmod bootit.ko" I get Error : protocol fault (no status)
I see that on windows it starts installing MTP USB but then it fails when the reboot happens. Tablet continues to reboot.

Any ideas? I miss the TF700

How to transfer Recovery file to the phone? (Serious problem)

I have LineageOS 16.0
I used MutiROM before, uninstalled it, but MultiROM Recovery is still installed.
Today I downloaded update for LineageOS but I got "Updater process ended with ERROR: 7"
Now I can't boot to OS because it boots straight to recovery.
The solution is to flash normal recovery and flash LineageOS zip.
But I can't transfer Recovery.img to my OnePlus One.
While I'm in Recovery, ADB is not working and there's no option to enable it.
And while I'm in Fastboot, PC can't see any fastboot devices.
It's not the PC's fault because it can recognize my Xiaomi Redmi Note 7 in both ADB and Fastboot mode.
So basically I need a way to transfer Recovery.img from PC to OnePlus One.
I can access only TWRP and Fastboot.
I can't do anything over USB cable.
OnePlus One doesn't have microSD card slot so I can't do it that way.
And I tried plugging in USB OTG drive and it phone can't recognize it. It won't even send the power to OTG drive.

eldin90 said:
And I tried plugging in USB OTG drive and it phone can't recognize it. It won't even send the power to OTG drive.
Click to expand...
Click to collapse
Use a low current flash drive, e.g. Transcend JetFlash 380 32 GB USB 2.0 OTG [200mA].

ze7zez said:
Use a low current flash drive, e.g. Transcend JetFlash 380 32 GB USB 2.0 OTG [200mA].
Click to expand...
Click to collapse
I don't think that'll work.
Phone doesn't give power to USB devices at all.
I tried plugging in multiple devices that used to work before (2 different USB thumb drives, both directly via micro USB port and via micro USB to USB 2.0 adapter, tried plugging in another phone, mouse, gamepad, micro USB to Ethernet adapter)
All those stuff used to work before while phone was on. But now they don't get power at all.
I don't know could it be because of Recovery?
I haven't tried plugging in OTG devices while in Recovery before.

eldin90 said:
While I'm in Recovery, ADB is not working and there's no option to enable it.
And while I'm in Fastboot, PC can't see any fastboot devices.
Click to expand...
Click to collapse
After entering:
Code:
adb devices
what you see in recovery mode?
---edit---
Use the USB 2.0 port on your PC.

ze7zez said:
After entering:
Code:
adb devices
what you see in recovery mode?
---edit---
Use the USB 2.0 port on your PC.
Click to expand...
Click to collapse
I don't see anything when I enter adb devices.
When I use any other phone I can see it after entering adb devices. But when I use OnePlus One I can't see anything.
And I only have USB 2.0 ports on my PC.

eldin90 said:
I have LineageOS 16.0
I used MutiROM before, uninstalled it, but MultiROM Recovery is still installed.
Today I downloaded update for LineageOS but I got "Updater process ended with ERROR: 7"
Click to expand...
Click to collapse
Are you sure you have an unmounted system partition before installing the ROM?
This message is the result of a mismatch between the build.prop entry from ROM and the TWRP installer script.

ze7zez said:
Are you sure you have an unmounted system partition before installing the ROM?
This message is the result of a mismatch between the build.prop entry from ROM and the TWRP installer script.
Click to expand...
Click to collapse
System partition is unmounted.
MultiROM TWRP gives me that error only when flashing some ROMs.
And it gives it to those ROMs always, no matter what I do.
Problem is that I only have LineageOS 16.0 zip on the phone and I don't have any other recoveries besides that MultiROM recovery.
Is there any way to boot the OS?
It worked fine before I tried to update it and it looks like all system files are still there.
I guess that failed update shouldn't had deleted any system files because it failed before it started doing anything.
I don't know what's making phone boot directly into recovery.
It won't even try to boot OS.
It goes straight into recovery every time.

eldin90 said:
System partition is unmounted.
MultiROM TWRP gives me that error only when flashing some ROMs.
And it gives it to those ROMs always, no matter what I do.
Problem is that I only have LineageOS 16.0 zip on the phone and I don't have any other recoveries besides that MultiROM recovery.
Is there any way to boot the OS?
It worked fine before I tried to update it and it looks like all system files are still there.
I guess that failed update shouldn't had deleted any system files because it failed before it started doing anything.
I don't know what's making phone boot directly into recovery.
It won't even try to boot OS.
It goes straight into recovery every time.
Click to expand...
Click to collapse
There should always be an original ROM for installation and several recovery versions in the phone's memory.
Now you have the use of restoring rom.
Clear the cache. First, try to recover only the Boot, and if that doesn't help, the entire backup.
You also have a powerful tool in TWRP in the form of a terminal and busybox commands, so act.

ze7zez said:
There should always be an original ROM for installation and several recovery versions in the phone's memory.
Now you have the use of restoring rom.
Clear the cache. First, try to recover only the Boot, and if that doesn't help, the entire backup.
You also have a powerful tool in TWRP in the form of a terminal and busybox commands, so act.
Click to expand...
Click to collapse
I tried wiping Cache and Dalvik / ART Cache
Still boots directly to recovery.
I don't have any backups or recovery installations on phone's memory.
I only have backup from 2 months ago that contains only boot and cache.
I restored it but it still boots directly to recovery.
What terminal commands should I use to fix this?

eldin90 said:
I tried wiping Cache and Dalvik / ART Cache
Still boots directly to recovery.
I don't have any backups or recovery installations on phone's memory.
I only have backup from 2 months ago that contains only boot and cache.
I restored it but it still boots directly to recovery.
What terminal commands should I use to fix this?
Click to expand...
Click to collapse
Since you don't maintain software hygiene, it's probably no better with hardware.
Clean the USB socket without damaging the connection. Clean the Vol- key in several ways.
Check if Odin can see the connection.
I have nothing more to add.

ze7zez said:
Since you don't maintain software hygiene, it's probably no better with hardware.
Clean the USB socket without damaging the connection. Clean the Vol- key in several ways.
Check if Odin can see the connection.
I have nothing more to add.
Click to expand...
Click to collapse
I work at coal coke industry and this happened about a month ago.
While I was charging the phone, coke dust inside the phone started burning and melted charger and USB socket together.
Guy from repair shop opened the phone and replaced USB socket with another one.
Is it possible that he didn't connected it correctly to the motherboard?
Or USB socket that he put wasn't exactly the same as the one that was originally there?
After he fixed it, we only tested can it charge the phone.
I haven't tried connecting phone to PC since then.
Anyways, is it possible to do something with terminal?
There has to be a file or something that's telling the phone to boot straight into recovery, right?
Can I remove or modify that file if it exists so phone boots into OS instead of recovery?
Vol- button isn't the problem.
It worked fine until I tried to update the OS.
And I can boot to Fastboot by holding Power and Vol+ buttons.

eldin90 said:
I work at coal coke industry and this happened about a month ago.
While I was charging the phone, coke dust inside the phone started burning and melted charger and USB socket together.
Guy from repair shop opened the phone and replaced USB socket with another one.
Is it possible that he didn't connected it correctly to the motherboard?
Or USB socket that he put wasn't exactly the same as the one that was originally there?
After he fixed it, we only tested can it charge the phone.
I haven't tried connecting phone to PC since then.
Anyways, is it possible to do something with terminal?
There has to be a file or something that's telling the phone to boot straight into recovery, right?
Can I remove or modify that file if it exists so phone boots into OS instead of recovery?
Vol- button isn't the problem.
It worked fine until I tried to update the OS.
And I can boot to Fastboot by holding Power and Vol+ buttons.
Click to expand...
Click to collapse
Using md5sum check the phone ROM.zip of your Lineage you tried to install. Then check the ROM.zip checksum on the server and compare the checksums. You will learn about the quality of the file.
If someone undertook to replace the usb socket, it is obvious that you should check not only the charging lines, but also the data transmission line.
From that I would repair the OPO.

ze7zez said:
Using md5sum check the phone ROM.zip of your Lineage you tried to install. Then check the ROM.zip checksum on the server and compare the checksums. You will learn about the quality of the file.
If someone undertook to replace the usb socket, it is obvious that you should check not only the charging lines, but also the data transmission line.
From that I would repair the OPO.
Click to expand...
Click to collapse
I did sha256 checksum and it's exactly the same as on the server
https://mirrorbits.lineageos.org/fu...16.0-20191118-nightly-bacon-signed.zip?sha256

Mount System partition
Code:
mount /system
and show:
Code:
grep twrp /tmp/recovery.log
Code:
ls -l /data/media/
Code:
ls -l /data/media/0/
Code:
grep lineage /system/build.prop
Code:
cd /
find . -name recovery*
find . -name *.zip
find . -name *.img
It's not everything. When you're finished we'll go on.

ze7zez said:
Mount System partition
Code:
mount /system
Click to expand...
Click to collapse
I did that
ze7zez said:
and show:
Code:
grep twrp /tmp/recovery.log
Click to expand...
Click to collapse
imageupload
ze7zez said:
Code:
ls -l /data/media/0/
Click to expand...
Click to collapse
This one only shows files and folders from internal memory. Nothing important there
ze7zez said:
Code:
ls -l /data/media/
Code:
grep lineage /system/build.prop
Click to expand...
Click to collapse
ze7zez said:
Code:
cd /
find . -name recovery*
find . -name *.zip
find . -name *.img
It's not everything. When you're finished we'll go on.
Click to expand...
Click to collapse

1. Change /sdcard/recovery.log to a unique name.
2. Make Advanced -> Copy Log (Include Kernel Log)
3. Change /sdcard/recovery.log to a unique name.
4. Make a full backup ROM if you haven't already done so.
5. Wipe -> Advanced Wipe: Dalvik, System, Data, Cache
6. Install lineage without "Reboot after installation is complete".
7. Show messages from the installation terminal.
8. Make Advanced -> Copy Log (Include Kernel Log)
9. Change /sdcard/recovery.log to a unique name.
10. Reboot -> System
??

I did all steps.
After wiping everything and trying to install LineageOS zip I get this (same as before)
When I tried to reboot, TWRP warned me that there are no OS installed. Phone still boots straight to recovery.

eldin90 said:
I did all steps.
After wiping everything and trying to install LineageOS zip I get this (same as before)
When I tried to reboot, TWRP warned me that there are no OS installed. Phone still boots straight to recovery.
Click to expand...
Click to collapse
You have twrp installed for Oneplus 3 (E3004) and you want to upload a ROM for Oneplus One.

ze7zez said:
You have twrp installed for Oneplus 3 (E3004) and you want to upload a ROM for Oneplus One.
Click to expand...
Click to collapse
I have installed TWRP that I downloaded from here
https://forum.xda-developers.com/oneplus-one/development/mod-multirom-v26-t2835738/amp
It's says it's for OnePlus One.
And I used to flash Ubuntu Touch and some older Resurrection Remix and CyanogenMod ROMs with it.

eldin90 said:
I have installed TWRP that I downloaded from here
https://forum.xda-developers.com/oneplus-one/development/mod-multirom-v26-t2835738/amp
Click to expand...
Click to collapse
This is impossible because your TWRP is release 3.1.1-0, which was created after 2017-05-17, which is much later than TWRP from the page you provided.
Show:
Code:
grep fingerprint /sdcard/recovery.log