Some time ago I successfully unlocked my TF700 and installed one of the Cromi-X roms. The machine wasn't improved that much and was still very slow with frequent messages asking if I wanted to wait for apps to respond or to close the app. I thought I would try the "Revisited CROMi-X-ET_v3.0-RC2" rom as that allowed the f2fs file system and I wondered if that would be faster. I installed TWRP version twrp-3.0.0-0-tf700t and did the install of the above rom using TWRP and choosing all the default options which reformatted some of the partitions to f2fs.
On reboot I got the start screen and then after a while a reboot again repeatedly. I tried booting to recovery and just got the Teamwin screen.
I then reinstalled TWRP using fastboot and a USB connection. I have tried twrp-2.8.7.0-tf700t, twrp_tf700t_kang_2.8.7.4, and twrp-3.0.0-0-tf700t and all give error messages when I do a wipe, try to restore a previous backup or try to install a new ROM.
On 2.8.7.0 the log I get from a wipe is:-
E:Unable to find partition size for '/misc'
E:Unable to find partition size for '/staging'
Erimary block device '/dev/block/mmcbblk0p8' for mount point '/data' is not present!
E:Unable to mount '/data'
E:Unable to recreate /data/media folder.
E:Unable to find partition size for '/recovery'
E:Unable to find partition size for '/boot'
Updating partition details...
E:Unable to mount '/system'
E:Unable to mount '/cache'
E:Unable to mount '/data'
...done
E:Unable to mount storage.
E:Unable to mount /data/media during GUI startup.
E:Unable to mount '/cache'
Kernel does not have support for reading SELinux contents.
E:Unable to mount '/cache'
E:Unable to set bootloader message
E:Unable to mount '/cache'
E:Unable to mount '/data/media/TWRP/.twrps when trying to read settings file.
E:Unable to mount '/data'
MTP Enabled
E:Unable to mount '/data'
Updating partition details...
E:Unable to mount '/system'
E:Unable to mount '/cache'
E:Unable to mount '/data'
...done
E:Unable to mount storage.
The twrp_tf700t_kang_2.8.7.4 version gives similar messages except it says failed to unmount system cache and data. The log from twrp-3.0.0-0-tf700t is the same as the kang version except this one says failed to mount the three partitions.
After reading another thread with similar symptom, I tried to format a partition using adb with the shell command:
make_ext4fs /dev/block/mmcblk0p8
this returns Need size of filesystem.
I would be grateful if anyone could help (or is my tablet irretrevably bricked).
What's the version of your bootloader?
Boot to TWRP and run "adb shell dmesg > dmesg.txt" and post the resulting file.
_that said:
What's the version of your bootloader?
Boot to TWRP and run "adb shell dmesg > dmesg.txt" and post the resulting file.
Click to expand...
Click to collapse
I did this some time last week but got no text file for some reason. Repeated it without the redirect to file and copied from the cmd window. It's a very long file however. Do I paste it in here or is there some way of attaching it so you can see it (I'm new to posting in forums)
How do I get the boot loader version?
Thanks for trying to help.
kenhanley said:
Do I paste it in here or is there some way of attaching it so you can see it (I'm new to posting in forums)
Click to expand...
Click to collapse
This forum has a feature to attach files (use the paper clip icon). I'm not sure if new users are allowed to attach files - if not, put your log on pastebin and add the relevant part of the URL to your answer.
kenhanley said:
How do I get the boot loader version?
Click to expand...
Click to collapse
Boot to the bootloader (Power+Volume down), read the small text in the upper left corner.
_that said:
This forum has a feature to attach files (use the paper clip icon). I'm not sure if new users are allowed to attach files - if not, put your log on pastebin and add the relevant part of the URL to your answer.
Boot to the bootloader (Power+Volume down), read the small text in the upper left corner.
Click to expand...
Click to collapse
As far as I can tell with two pairs of reading glasses on (its an age thing), the second line reads
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.10-20130801" R03
Insidentally I just descovered that TWRP only runs once after installing with fastboot. If I power down I have to use fastboot again each time and re-install twrp.
I don't see the paperclip and - sorry to be so ignorant but - how do I logon to pastebin
Regards
Ken
kenhanley said:
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.10-20130801" R03
Click to expand...
Click to collapse
OK, that's the correct version.
kenhanley said:
Insidentally I just descovered that TWRP only runs once after installing with fastboot. If I power down I have to use fastboot again each time and re-install twrp.
Click to expand...
Click to collapse
You need to fully reboot after installing TWRP via fastboot (however you can go directly to the bootloader menu and select RCK, no need to start Android), otherwise it can't access your partitions.
kenhanley said:
As far as I can tell with two pairs of reading glasses on (its an age thing), the second line reads
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.10-20130801" R03
Insidentally I just descovered that TWRP only runs once after installing with fastboot. If I power down I have to use fastboot again each time and re-install twrp.
I don't see the paperclip and - sorry to be so ignorant but - how do I logon to pastebin
Regards
Ken
Click to expand...
Click to collapse
I think I manage to paste into pastebin under title KenHanley demsg. Not sure how you get to see it.
Regards
Ken
Not sure I understand about the reboot after TWRP install. When I install TWR the tablet is sitting with the three icons RCK Android and Wipe Data. After install completes if I press Vol up with the RCK flashing TWRP works. If I reboot straight away TWRP hangs on the start screen or tries to reboot after a time depending on which version I installed. Same thing happens after powering down from running TWRP without the reboot.
Regards
Ken
just realised youasked for pastebin url. It's
pastebin/4Bh8zdXa
regards
Ken
kenhanley said:
Not sure I understand about the reboot after TWRP install. When I install TWR the tablet is sitting with the three icons RCK Android and Wipe Data. After install completes if I press Vol up with the RCK flashing TWRP works. If I reboot straight away TWRP hangs on the start screen or tries to reboot after a time depending on which version I installed. Same thing happens after powering down from running TWRP without the reboot.
Regards
Ken
Click to expand...
Click to collapse
There's your problem, as _that said: You need to reboot after flashing TWRP before you can use it:
Flash TWRP
Reboot into bootloader
Enter TWRP by selecting the RCK icon.
I know you said TWRP hung if you reboot straight away, but that is strange. Describe step by step how you flash TWRP.
OK.
I boot TF700 with vol down pressed. Connect USB to computer running windows 10. Open cmd window. (copy from cmd window below):
C:\adb>fastboot flash recovery twrp-2.8.7.0-tf700t.img
sending 'recovery' (7372 KB)...
OKAY [ 3.418s]
writing 'recovery'...
OKAY [ 6.528s]
finished. total time: 9.951s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.020s
C:\adb>
Holding vol down when typing fastboot reboot. Press Vol up when RCK is flashing. Teamwin screen comes on then briefly flashes off and comes on again and that is as far as it gets.
Same thing happens if instead of typing fastboot reboot I press and hold the TF700 power button to reboot.
If I skip the reboot and press Vol up after the flash has finished TWRP starts up and after a delay I get all the various buttons to Install, Backup, Restore etc.. Then I get the storage not mounted problems
Do not touch any button on the tablet after the recovery flash. Just type fastboot reboot, then hit enter.
After you've seen the Asus logo with a blue bar underneath filling up you can reboot into the bootloader and enter recovery.
Just done that. I get a blue bar when I flash.
After fastboot reboot the screen blanks then the Asus Logo comes up but no bluebar. Eventually after displaying the Asus screen for about 35 seconds the tablet reboots itself in the bootloop I originally mentioned. Booting to recovery gives me the teamwin screen hangup I described above.
I repeated and this time instead of waiting on the Asus screen I rebooted from the Asus screen by pressing and holding power and vol down. Same happens TWRP hangs on Teamwin screen
Sorry I'm causing all this trouble.
Regards
Ken
Never seen that before and I don't have an explanation for it either....
What kind of wipes did you do before flashing the new rom?
Don't know.. maybe @_that has a better idea, but at this point I would flash the Asus firmware in fastboot and start from scratch.....
Hang in there for word from @_that, otherwise I can hook you up with instructions for the fastboot firmware flash
Sent from my ASUS Transformer Pad TF700T using Tapatalk
kenhanley said:
C:\adb>fastboot flash recovery twrp-2.8.7.0-tf700t.img
sending 'recovery' (7372 KB)...
OKAY [ 3.418s]
writing 'recovery'...
OKAY [ 6.528s]
finished. total time: 9.951s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.020s
C:\adb>
Holding vol down when typing fastboot reboot. Press Vol up when RCK is flashing. Teamwin screen comes on then briefly flashes off and comes on again and that is as far as it gets.
Click to expand...
Click to collapse
I think it's crashing due to a corrupted filesystem. Reboot to TWRP, and with the splash screen flashing, run this:
Code:
adb pull /tmp/recovery.log
Post the resulting file.
To reformat /data as f2fs (be careful with this command and press Enter only after double-checking that you got the "p8" right):
Code:
adb shell mkfs.f2fs /dev/block/mmcblk0p8
_that
I posted the recovery log http://pastebin.com/PdZVbEsC title KenHanleyrecoverylog.
Just did the format of /data then installed TWRP again. Reboot still didn't give a blue bar but Yipee The bootloop is gone and I'm into the setup screens for the ROM I flashed that caused all the bother. Thank You
berndblb
I looked on the Asus site for firmware but they don't list the TF700T anymore. I would be grateful if you can point me to the files and instructions for the Asus firmware in case I do need to do a restore to original.
Thanks again to you all for the help
It's not the rom that did it - I'm running it without trouble for months! It was what you did.
http://www.transformerforums.com/fo...e-firmware-tf101-tf201-tf300-tf700-tf701.html
Check out post 2 and download a copy. Who knows when Asus takes it down entirely....
I didn't mean to imply it was the ROM. It seems to be running OK now. I think somehow the formatting of \data went wrong during the install but I can't identify anything I did that could have caused it. Anyway I'm just grateful to you guys for digging me out of the hole I dug for myself. Thanks for the link, I got to the firmware download page OK from that. I'll grab everything I can now while the going is good.
I realize this is an old post, but hopefully ....
I have the same problem except that it will only boot to the splash screen of TWRP3.1.x.
I had KatKiss 7.1 on it and rebooted it and into a loop. I re-flashed TWRP V3 via fastboot and the much discussed blue line was there, a "fastboot reboot" just sent me into the boot loop again. Pwr/Voldn gave me the 3 flashing icons, but selecting recovery just gives me the TWRP loading screen for about 10 seconds or so, then reboots.
I'm assuming I have to start from scratch as well but am a bit confused as to which firmware from asus' site and how to do this.
Strange - I wonder what it is that prevents TWRP from booting....
Did you try the command from above to reformat data to f2fs?
If nothing resolves this you can always flash the stock blob in fastboot.
The firmware is here: https://www.asus.com/support/Download/28/1/0/11/fq2B3oq64av1O95/8/
Download the SKU for your region (most likely WW or US).
Unzip it twice and copy only the blob into your fastboot folder.
Then try this:
Code:
fastboot erase userdata
Now try to boot into TWRP via the buttons
If that did not do it, continue with:
Code:
fastboot erase misc
fastboot erase cache
Again boot into TWRP and see if that did it.
If not continue with this:
Code:
fastboot erase system
fastboot erase recovery
fastboot erase boot
fastboot flash system blob
fastboot reboot
The commands will finish fairly quickly except for erasing data and flashing the blob. Be patient.
If you're not the inquisitive type who wants to find out what the problem is and more the roundhouse-punch-radical type you can also run all the above commands one after the other in one go to get you back to stock. The order is not important as long as you flash the blob last. Before rebooting that is.
That should return you to a stock JB 4.2 system.
Then flash TWRP, format data, convert it to f2fs and finally flash the rom or restore your last nandroid.
Good luck
Related
Hello,
I turned on my Xoom to see "Encryption Unsuccessful" tonight. If i boot into stock recovery and try to factory reset, it cannot mount Cache. If I plug the device into my computer, fastboot can find it but ADB cannot. I have the proper drivers installed. I can't get into my tablet to turn on USB debugging. I just bought an OTG cable to try to fix it, but cannot find the update.zip file that I need. If i try to fastboot oem unlock, it fails. I've tried everything I can find, I've done hours worth of playing/trial and error to no avail. Any help would be fantastic. Truly at a stand still. Please ask with any specifics needed to assist me.
Is it possible to flash to CWM recovery without being able to boot/find it in ADB?
Thank you,
Bradon
>.<
Nearly to the point of offering some sort of payment for assisting me. I'd rather not ship it out, but more than glad to work something out paypal or giftcard wise. This tablet is the only thing keeping my wife entertained, and another tablet is not in the budget.
But u can connect with fastboot to device ?
if yes this should help you
http://forum.xda-developers.com/showthread.php?t=1451655&page=7
http://forum.xda-developers.com/showthread.php?t=1049485
Probably you will lose all data on it ... Why u wanted to encrypt u device ...
I did it too but it was missunderstanding specialy when flashing a lot .
Alright so...
I've used fast boot flash user data, system, recovery and boot. Those are all successful, but if I reboot.. Nothing changes.
I've loaded many zips onto a flash drive with an otg cable, boot into the stock recovery and try to update, unable to verify signature.
Adv will not find the device, reinstalled drivers many times
Rsd will not find the device
Factory reset fails, cannot mount cache and about 10 other cache/recovery errors
Fast boot OEM unlock fails, unable to write a certain 3 letter file
I'm at work right now, so I can post specifics/pics later.
I didn't try to encrypt it, it seemed like a virus that my wife got. She clicks on advertisements, downloads sketchy files/apps.
It is unrooted, stock recovery.
20+ hours of research and trial.. No success.
Can u use this ?
http://forum.xda-developers.com/showthread.php?t=1074979
Use 2 method.
Write response what happend and it does flash recovery .
You have to unlock bootloader
look here simillar problem :
http://forum.xda-developers.com/showthread.php?t=1571827
http://forum.xda-developers.com/showthread.php?t=1952628
And u do not need any special otg cabel - use stock xoom from package. OTG is for host-usb.
Anyway u will have to do it with fastboot , probably /cache partialy encrypted.
Alright, I just followed the CWM recovery guide.
First off, ADB does not find my device, meaning I cannot reboot into the bootloader. I can flash the recovery only after flashing userdata for some reason. After flashing, it says complete though when I reboot nothing changes. The other 2 links, first one I can't use because adb doesn't find my device, and the 2nd one.. I don't think xoom has a "download mode".
Thanks
Ok, so when u push down button in booting u have only recovery ?
U should have fastboot too ... try to press up vol 1 s after booting, then connect to pc, and check in device manager rmb on "My pc"
And ? .... This must working ... Use fastboot.exe in cmd ( in windows 7 ) on Administrator User.
Also, when I first boot up recovery I get
E: failed to mount /cache (invalid argument.)
E: Can't mount /cache/recovery/command
E: Failed to mount /cache (invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (invalid argument)
E:can't mount /cache/recovery/last_log
E:can't open /cache/recovery/last_log
E: Failed to mount /cache (invalid argument)
E:can't mount /cache/recovery/last_install
E:can't open /cache/recovery/last_install
E: Failed to mount /cache (invalid argument)
If i try to factory reset or clear the cache, I get the same message.
U do not understand what u reading, u cant do this from recovery ...
U have partialy crypted storage ... its normal!
1. download fastboot on windows
2. install drivers from
1) Get the Motorola USB drivers MOTODEV > Documentation & Tools > USB Drivers (you need to sign up on their but maybe you can google this and find it as well)
2) Get the Android SDK Android SDK | Android Developers (you only really need the fastboot executable file for your host OS)
Click to expand...
Click to collapse
3. run fastboot protocol on xoom press down vol "find fastboot" if not press top vol in booting - should fastboot protocol ... in output
4. Use fastboot.exe from android sdk - run in in cmd ( Run ad Administrator , right click on cmd)
4. unlock bootloader
5. flash rom boot recovery in *.img format!
This must working...
When I connect it to my PC in fastboot mode, it comes up as "Mot Single ADB Interface"
bcwest said:
When I connect it to my PC in fastboot mode, it comes up as "Mot Single ADB Interface"
Click to expand...
Click to collapse
Is it bad ? - now when u show up "fastboot protocol ... " on xoom run fastboot from android sdk .
Fastboot ran from cmd with admin privileges.
fastboot oem unlock
used volume controls to select yes/i accept
Device unlock operation in progress...
Formatting UDA.
hardware/tegra/core/system/moto/fastboot_sparse.c:324 NvStorMgrFileOpen("UDA"):196624
ERROR: Failed to format UDA.
Error while unlocking device.
unplug mmc card from xoom and try again, where did u get files ... system.img ,recovery.img,boot.img ?
I've tried with both the mSD card in, and out. I got the boot/system/recovery/userdata from the stock image post from XDA.
ok, I didnt tryed this with stock rom, try to change recovery with http://forum.xda-developers.com/showthread.php?t=1074979
reboot and try to get to new recovery.
do this:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img <- from http://forum.xda-developers.com/showthread.php?t=1074979
fastboot flash userdata userdata.img
fastboot erase cache
fastboot erase userdata
fastboot reboot
Which model of xoom u have ? Did u restart xoom after flashing ? Is there any output ? (without up,down vol )
mx600 is the model that I have.
All of the flashing goes through fine
fastboot erase cache fails instantly (Failed to format PDB)
fastboot erase userdata fails instantly (Failed to format PDB)
fastboot reboot
volume down for recovery to see if CWM changes went through
stock android recovery
If I put my mSD card back into the unit, and try to do it all over again..
Flashes go through fine
Cache fails instantly, same error
Erase userdata causes my cmd to hang up, and the xoom sits at "StorMgr Formatting UDA STATUS: | | |"
5 minutes later, still sitting at that message.
Mx600, I restarted the device after flashing everything, If I let it go past the Dual Core Technology big red M, it boots into android but all that I get is the Encryption Unsuccessful screen. It says push restart, but it does nothing.
Which model of xoom u have ? Did u restart xoom after flashing ? Is there any output ? (without up,down vol )[/QUOTE]
Damn, that mean bootloader is locked or he have problem with gpt ?
ok... I'm not sure what will hapend but u can try to lock it again
fastboot oem lock
then reboot
fastboot oem unlock
output ?
Device Lock operation in progress...
Formatting UDA.
hardware/tegra/core/system/moto/fastboot_sparse.c:350 NvStorMgrFileWrite(ff, 0x00004000:00000000):196608
ERROR: Failed to format UDA
Device lock operation FAILED.
Hey,
since apparently a lot have a softbrick for whatever reason i thought i post my findings here as well since it worked for both my TF300t and A700
Originating Thread: http://forum.xda-developers.com/showpost.php?p=44244313
and here my steps:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
My solution
I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back
i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.
Here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer, as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
Click to expand...
Click to collapse
cheers
-Buster
Buster99 said:
Hey,
since apparently a lot have a softbrick for whatever reason i thought i post my findings here as well since it worked for both my TF300t and A700
Originating Thread: http://forum.xda-developers.com/showpost.php?p=44244313
and here my steps:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
cheers
-Buster
Click to expand...
Click to collapse
At this part:
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
Click to expand...
Click to collapse
you put the instructions fo the TF300t, but you said this method also worked for the Acer a700. I know to change the code after -i to 0x0502, for the a700 device ID, but I'm not sure what to use for the system. I've been unable to find a system.img that works, as well. What should I do after erasing the partitions?
Also, usually when I try to flash anything, when fastboot begins the write process (or just before,) the tablet screen starts to slowly jitter (the Acer logo and Bootloader text in the top-left go down about 10 pixels for about a half-second then go back to their original positions.) I've tried multiple guides (can't fastboot boot recovery.img, Magic Value Mismatch error,) and I can't get into adb. Any ideas? It looks like your fix might work somehow.
OMIGHTY1 said:
At this part:
you put the instructions fo the TF300t, but you said this method also worked for the Acer a700. I know to change the code after -i to 0x0502, for the a700 device ID, but I'm not sure what to use for the system. I've been unable to find a system.img that works, as well. What should I do after erasing the partitions?
Also, usually when I try to flash anything, when fastboot begins the write process (or just before,) the tablet screen starts to slowly jitter (the Acer logo and Bootloader text in the top-left go down about 10 pixels for about a half-second then go back to their original positions.) I've tried multiple guides (can't fastboot boot recovery.img, Magic Value Mismatch error,) and I can't get into adb. Any ideas? It looks like your fix might work somehow.
Click to expand...
Click to collapse
When in doubt, disconeect all android devices and issue the command without the ID (usually fastboot/adb use the default id when only 1 device is connected.
"fastboot flash system c:\blob"
The erase worked on my TF300t/A700/Galaxy Nexus.
If you are having flashing probs make shure to switch cable and usb ports &/or try a linux to test.
gl
-Buster
Here's the input and output from that:
C:\android>fastboot flash system c:\blob
error: cannot load 'c:\blob': No error
Click to expand...
Click to collapse
Would I need the stock image in the blob folder, or should it be empty? Should I create it at all?
The screen problem is identical to the problem in this post:
http://forum.xda-developers.com/showthread.php?t=1976209
OMG - Thought My Prime was Dead In The Water...Thanks Buster!
Buster99 said:
Hey,
since apparently a lot have a softbrick for whatever reason i thought i post my findings here as well since it worked for both my TF300t and A700
Originating Thread: http://forum.xda-developers.com/showpost.php?p=44244313
and here my steps:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
cheers
-Buster
Click to expand...
Click to collapse
Was getting the dreaded Option 2 - Unrecoverable Bootloader Error that was supposed to be the ultimate death sign. As a last resort, I tried the steps Buster provided and my Prime is up and running again!
When i turn on tablet, goes straight to recovery, even after have tried rebooting into system, i followed the button combinations to boot into RCK. The version installed of CWM was based in Recovery v6.0.2.3 occurs that after opening CWM immediately below error messages are displayed.
E:Can’t mount /cache/recovery/command
E:Can’t mount /cache/recovery/log
E:Can’t open /cache/recovery/log
E:Can’t mount /cache/recovery/last_log
E:Can’t open /cache/recovery/last_log
And now can’t grab any rom in SD card when I’m forced into recovery. I tried with two kind of SD, 1Gb Sandisk, 4Gb Kingston HC-(4). when I try to mount any partition like /data and /sdcard from “mounts and storage” obtain:
Error mounting /sdcard!, Error mounting /sdcard!, Error mounting /emmc!
Also i download android tools and installed adb universal drivers, from recovery mode, If I type "adb devices" shows a proper reorganization.
List of device attached
0123456789ABCDEF recovery
So every time when start up, even without hitting vol+power key, it goes into the recovery mode.when i type "adb reboot-bootloader",it goes power off.Nothing happen.Please help me.
I unlock the g bootloader got it to root I have the latest cwm recovery been trying different ones also, but some how when I try to install any rom that's out there it won't boot up it only stays on the boot screen . Any ideas
Me too
I have this problem too.
Guys, please search the forum before posting, so your issues would get resolved quickly.
OK, Now towards your problem.
A lot of people are getting the same error and the results from corruptioning of /data. First try factory reset from fastboot, then reboot. If it doesn't help then do a factory reset again and reboot your phone. If doesn't seen to help either then the only option left is to flash stock firmware through PC. Search the forum and you will get the desired result. Beaware that you will end up losing all your apps and SD card data.
forgotter said:
Guys, please search the forum before posting, so your issues would get resolved quickly.
OK, Now towards your problem.
A lot of people are getting the same error and the results from corruptioning of /data. First try factory reset from fastboot, then reboot. If it doesn't help then do a factory reset again and reboot your phone. If doesn't seen to help either then the only option left is to flash stock firmware through PC. Search the forum and you will get the desired result. Beaware that you will end up losing all your apps and SD card data.
Click to expand...
Click to collapse
I have factory reset from fastboot a couple of times also been Goin to stock a few times, been searching everywhere I haven had any luck the phone just been doing the same thing all the time.
I have rooted, install roms, an customized over 20 android devices I have own an never had this problem
chente323 said:
I have factory reset from fastboot a couple of times also been Goin to stock a few times, been searching everywhere I haven had any luck the phone just been doing the same thing all the time.
I have rooted, install roms, an customized over 20 android devices I have own an never had this problem
Click to expand...
Click to collapse
So here's a detailed instruction for you to follow.
1. In fast boot mode connect phone to PC.
2. In CMD (adb) in PC type the command "fastboot devices" without quotes and post the reply to me.
3. In the CMD, type the command "adb erase userdata","adb erase cache" without quotes. (It will wipe all your data and SD card)
4. Now download the firmware (new firmware download it in case there may be issues with the old one you have downloaded) and also TWRP-2.7.0.0.falcon by dhacker. Copy both the files in the adb folder.
5. Rename the twrp-2.7.0.0.falcon.IMG to recovery.img
6. Connect your phone to PC in fastboot mode and flash the recovery by topping command "fastboot flash recovery recovery.img"without quotes.
7. On your phone scroll to recovery option and long press volume up key until the phone vibrates. The phone will boot into recovery.
8. In recovery goto advanced-file manager. And check whether your /datafilleris empty or not (it will be empty)
9. In recovery go to wipe and wipe /system /data /cache. Next reboot your phone to boot loader mode.
10. Flash any firmware from your PC through fastboot. Then reboot your phone.
If it doesn't help either reply to me, there's other workaround too.
forgotter said:
So here's a detailed instruction for you to follow.
1. In fast boot mode connect phone to PC.
2. In CMD (adb) in PC type the command "fastboot devices" without quotes and post the reply to me.
3. In the CMD, type the command "adb erase userdata","adb erase cache" without quotes. (It will wipe all your data and SD card)
4. Now download the firmware (new firmware download it in case there may be issues with the old one you have downloaded) and also TWRP-2.7.0.0.falcon by dhacker. Copy both the files in the adb folder.
5. Rename the twrp-2.7.0.0.falcon.IMG to recovery.img
6. Connect your phone to PC in fastboot mode and flash the recovery by topping command "fastboot flash recovery recovery.img"without quotes.
7. On your phone scroll to recovery option and long press volume up key until the phone vibrates. The phone will boot into recovery.
8. In recovery goto advanced-file manager. And check whether your /datafilleris empty or not (it will be empty)
9. In recovery go to wipe and wipe /system /data /cache. Next reboot your phone to boot loader mode.
10. Flash any firmware from your PC through fastboot. Then reboot your phone.
If it doesn't help either reply to me, there's other workaround too.
Click to expand...
Click to collapse
This is the same thing a friend told me to do we did it had no luck Did it 2 times just in case I dint do it right the first time
Moto g not booting up.
I hope you have an unlocked boot loader.
The first thing you need to find out is that are your phone's partition writable and readable.
1. Download the latest CM11 nightly to your PC rename it to "CM.zip" and extract the contents to adb folder (adb folder should be in C drive i.e. C:/adb ). You will get boot. img , system (folder), and others.
1. connect your phone to PC in fastboot mode.
2.In adb type the below commands one by one without quotes. And let one command get processed before typing other.
"fastboot devices" (in response it must show you something like TJ9*****)
"fastboot erase userdata"
"fastboot erase cache"
"fastboot push C:/adb\system /system/"
"fastboot flash boot boot.img"
"fastboot flash recovery recovery.img"(flash the philz recovery now)
"fastboot push C:/adb\boot.img /data/"(to verify whether /data is writable or not)
"fastboot push C:/adb\boot.img /cache/"(to verify whether /cache is writable or not)
"fastboot push C:/adb\CM.zip /data/media/0/"(to push the CM11rom to sdcard to flash it through recovery)
Then boot your phone to recovery. And see the logs, it should show
/system mounted
/data mounted
/sd-ext error mounting /sd-ext
/cache mounted
If it shows /data can't be mounted or error mounting /data. Then go to wipe and wipe /data and /sdcard and then again push CM.zip to /data/media/0/. If you don't see this error, then choose to wipe to install a new rom. After this remount /system /data /cache and flash the CM11.zip or you can flash stock firmware through mfastboot.
This method will definitely work since I, myself had this very same issue and got it resolved the very same way.
P.S. Try this method and only of you get some error then reply as I an sure it will solve your issue.
forgotter said:
I hope you have an unlocked boot loader and have TWRP(2.7 by dhacker) installed.
The first thing you need to find out is that are your phone's partition writable and readable.
1. Download the latest CM11 nightly to your PC and extract the contents to adb folder. You will get boot. img , system (folder), and others.
1. connect your phone to PC in fastboot mode.
2.In adb type the below commands one by one without quotes. And let one command get processed before typing other.
"fastboot devices" (in response it must show you something like TJ9*****)
"fastboot erase userdata"
"fastboot erase cache"
"fastboot push system /system"
"fastboot flash boot boot. img"
"fastboot flash recovery recovery.img"(flash the philz recovery now)
"fastboot push boot.img /data"(to verify whether /data is writable or not)
"fastboot push boot. img /cache"(to verify whether /cache is writable or not)
"fastboot push CM.zip /data/media/0/"(to push the CM11rom to sdcard to flag it through recovery)
Then boot your phone to recovery. And see the logs, it should show
/system mounted
/data mounted
/sd-ext error mounting /sd-ext
/cache mounted
If it shows /data can't be mounted or error mounting /data.Then go to wipe and wipe /data and /sdcard. If you don't see this error, then chose to wipe to install a new rom. After this remount /system /data /cache and flash the CM11. zip.
This method will definitely work since I, myself had this very same issue and got it resolved the very same way.
P.S. Try this method and only of you get some error then reply as I an sure it will solve your issue.
Click to expand...
Click to collapse
Thanks I will give it a try tomorrow since it's wife phone I don't have it w me now. I'll get back at u let u know if it work
forgotter said:
So here's a detailed instruction for you to follow.
1. In fast boot mode connect phone to PC.
2. In CMD (adb) in PC type the command "fastboot devices" without quotes and post the reply to me.
3. In the CMD, type the command "adb erase userdata","adb erase cache" without quotes. (It will wipe all your data and SD card)
4. Now download the firmware (new firmware download it in case there may be issues with the old one you have downloaded) and also TWRP-2.7.0.0.falcon by dhacker. Copy both the files in the adb folder.
5. Rename the twrp-2.7.0.0.falcon.IMG to recovery.img
6. Connect your phone to PC in fastboot mode and flash the recovery by topping command "fastboot flash recovery recovery.img"without quotes.
7. On your phone scroll to recovery option and long press volume up key until the phone vibrates. The phone will boot into recovery.
8. In recovery goto advanced-file manager. And check whether your /datafilleris empty or not (it will be empty)
9. In recovery go to wipe and wipe /system /data /cache. Next reboot your phone to boot loader mode.
10. Flash any firmware from your PC through fastboot. Then reboot your phone.
If it doesn't help either reply to me, there's other workaround too.
Click to expand...
Click to collapse
Hi forgotter! I have the same problem... won't boot with any ROM. I've followed your instructions but stil stucked on the boot logo. I will try the second method you provided now, hope that works :crying:
@notnowjohn
Didn't know why first method didn't worked for you but the second one would definitely work. If you get any error then reply to me, and yes in my second method post by mistake there are some extra space added after full stop (.) e.g. in boot. img (it is boot.img ) do please avoid that.
forgotter said:
I hope you have an unlocked boot loader and have TWRP(2.7 by dhacker) installed.
The first thing you need to find out is that are your phone's partition writable and readable.
1. Download the latest CM11 nightly to your PC and extract the contents to adb folder. You will get boot. img , system (folder), and others.
1. connect your phone to PC in fastboot mode.
2.In adb type the below commands one by one without quotes. And let one command get processed before typing other.
"fastboot devices" (in response it must show you something like TJ9*****)
"fastboot erase userdata"
"fastboot erase cache"
"fastboot push system /system"
"fastboot flash boot boot. img"
"fastboot flash recovery recovery.img"(flash the philz recovery now)
"fastboot push boot.img /data"(to verify whether /data is writable or not)
"fastboot push boot. img /cache"(to verify whether /cache is writable or not)
"fastboot push CM.zip /data/media/0/"(to push the CM11rom to sdcard to flag it through recovery)
Then boot your phone to recovery. And see the logs, it should show
/system mounted
/data mounted
/sd-ext error mounting /sd-ext
/cache mounted
If it shows /data can't be mounted or error mounting /data.Then go to wipe and wipe /data and /sdcard. If you don't see this error, then chose to wipe to install a new rom. After this remount /system /data /cache and flash the CM11. zip.
This method will definitely work since I, myself had this very same issue and got it resolved the very same way.
P.S. Try this method and only of you get some error then reply as I an sure it will solve your issue.
Click to expand...
Click to collapse
Hi again Sir, I've followed all the instructions, but when I check the logs it says "Can't Mount" of "Can´t open" for everything.
This is what i saw during the proccess
"fastboot devices" (in response it must show you something like TJ9*****) T08830R89M
"fastboot erase userdata" OK
"fastboot erase cache" OK
"fastboot push system /system" Doesnt do anything, show adb commands
"fastboot flash boot boot. img" I deleted the space between . img. Phone says Mismatched partition size (boot)
"fastboot flash recovery recovery.img"(flash the philz recovery now) Phone says Mismatched partition size (Recovery)
"fastboot push boot.img /data"(to verify whether /data is writable or not) Doesnt do anything, show adb commands
"fastboot push boot. img /cache"(to verify whether /cache is writable or not). Again deleted the space between . img. Doesnt do anything, show adb commands
"fastboot push CM.zip /data/media/0/"(to push the CM11rom to sdcard to flag it through recovery) Doesnt do anything, show adb commands
Its anthing more I can do??
Thank you very much! I can believe I brick my phone
notnowjohn said:
Hi again Sir, I've followed all the instructions, but when I check the logs it says "Can't Mount" of "Can´t open" for everything.
This is what i saw during the proccess
"fastboot devices" (in response it must show you something like TJ9*****) T08830R89M
"fastboot erase userdata" OK
"fastboot erase cache" OK
"fastboot push system /system" Doesnt do anything, show adb commands
"fastboot flash boot boot. img" I deleted the space between . img. Phone says Mismatched partition size (boot)
"fastboot flash recovery recovery.img"(flash the philz recovery now) Phone says Mismatched partition size (Recovery)
"fastboot push boot.img /data"(to verify whether /data is writable or not) Doesnt do anything, show adb commands
"fastboot push boot. img /cache"(to verify whether /cache is writable or not). Again deleted the space between . img. Doesnt do anything, show adb commands
"fastboot push CM.zip /data/media/0/"(to push the CM11rom to sdcard to flag it through recovery) Doesnt do anything, show adb commands
Its anthing more I can do??
Thank you very much! I can believe I brick my phone
Click to expand...
Click to collapse
Don't worry your phone is fine.
Whenever adb shows m mismatched partition it's fine and usual.
I understand your problem now, I just think if I your device now , I would have repaired it within minutes. Never mind, follow the below steps .
Download the philz recovery to your PC, flash it through fastboot on your phone. Then go to recovery on your phone immediately and choose wipe-wipe data and sdcard. And then flash the stock firmware through mfastboot or install any ROM through recovery.
Anyone report which step what must i do to solve this prob
sinkadorable said:
Anyone report which step what must i do to solve this prob
Click to expand...
Click to collapse
Read post #7 on page 1.
I cant push system to device. What tools must be i have?
If you can't push system to device don't worry , it's of no use at all because you'll format it before flashing the rom. But if you're flashing through recovery then make sure to push CM. zip to /sdcard/.
You need adb tools on your PC, just search Google for adb tools and download it. You need stock firmware of your phone on PC if you'd flash the rom through mfastboot and you need philz recovery ( to flash it on your phone.)
If you can't get anything or don't understand anything then do search the forum for help because all the things are already mentioned and if i had to answer it mostly would be copy-paste. But still if you need help, I am there. Just post your problem.
pluiz halp!
forgotter said:
If you can't push system to device don't worry , it's of no use at all because you'll format it before flashing the rom. But if you're flashing through recovery then make sure to push CM. zip to /sdcard/.
You need adb tools on your PC, just search Google for adb tools and download it. You need stock firmware of your phone on PC if you'd flash the rom through mfastboot and you need philz recovery ( to flash it on your phone.)
If you can't get anything or don't understand anything then do search the forum for help because all the things are already mentioned and if i had to answer it mostly would be copy-paste. But still if you need help, I am there. Just post your problem.
Click to expand...
Click to collapse
I'm having similar issues as everyone else here. I unlocked my bootloader following Motorola's instructions on their website, then I used Superboot to root the phone (which I don't think worked as CWM and TWRP kept asking to install SU on reboot). After that I put CM 11 M4 on sdcard and flashed.
This is where it went wrong. I rebooted and got a bootloop, so I looked around online and ended up wiping everything and trying again. It still didn't work so I followed instructions to reflash stock firmware, this didn't work either. By this time the phone had been on ages and went dead. Now it won't turn back on and won't register as charging from USB or from wall plug.
I have no idea what to do as nothing worked before hand and now I can't access it to resolve the issue.
I'm panicking atm because I'm contracted to Virgin Mobile in the UK and this voids the warranty. I just don't know what to do D:
jamiethomaswhite said:
I'm having similar issues as everyone else here. I unlocked my bootloader following Motorola's instructions on their website, then I used Superboot to root the phone (which I don't think worked as CWM and TWRP kept asking to install SU on reboot). After that I put CM 11 M4 on sdcard and flashed.
This is where it went wrong. I rebooted and got a bootloop, so I looked around online and ended up wiping everything and trying again. It still didn't work so I followed instructions to reflash stock firmware, this didn't work either. By this time the phone had been on ages and went dead. Now it won't turn back on and won't register as charging from USB or from wall plug.
I have no idea what to do as nothing worked before hand and now I can't access it to resolve the issue.
I'm panicking atm because I'm contracted to Virgin Mobile in the UK and this voids the warranty. I just don't know what to do D:
Click to expand...
Click to collapse
Plug the phone to wall charger and leave it to charge for the whole night, the next when you'd restart the phone it should boot up. Sometimes the phone discharged itself to such a level that it didn't have enough juice left to show the battery charging status even.
After that follow instructions from post #7 on page 1 and paste all output commands you see. Well, the phone should boot up.
forgotter said:
If you can't push system to device don't worry , it's of no use at all because you'll format it before flashing the rom. But if you're flashing through recovery then make sure to push CM. zip to /sdcard/.
You need adb tools on your PC, just search Google for adb tools and download it. You need stock firmware of your phone on PC if you'd flash the rom through mfastboot and you need philz recovery ( to flash it on your phone.)
If you can't get anything or don't understand anything then do search the forum for help because all the things are already mentioned and if i had to answer it mostly would be copy-paste. But still if you need help, I am there. Just post your problem.
Click to expand...
Click to collapse
now my phone was stuck on UBL warning message and cannot enter recovery
when i flash recovery fastboot say Mismatched partition size (Recovery) :crying:
sinkadorable said:
now my phone was stuck on UBL warning message and cannot enter recovery
when i flash recovery fastboot say Mismatched partition size (Recovery) :crying:
Click to expand...
Click to collapse
Mismatched partition size is usual , no need to worry about that. What do you mean by UBL warning message? And yes, after you flash recovery, enter in recovery mode and wipe data and sdcard and then flash any ROM from fastboot.
And if you get into an error or solution doesn't work then post your problem but detailed so I can get to the main cause of the problem.
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
As the title says, I (without thinking) did a factory reset from within the settings menu while using a custom rom. My tablet boots and sits on the attached screen. I cannot access fastboot but while on the screen I have ADB access and can send commands. Also, none of the Volume&Power Buttons combinations will work. Please advise..
Here you go: http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Sent from my K00C using Tapatalk
berndblb said:
Here you go: http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
Thanks for the suggested thread, unfortunately after the "adb shell insmod /bootit.ko" command my tablet simply powers off and does not reboot. I read through the thread and saw that someone else experienced the same but there doesn't seem to be a resolution.
berndblb said:
Here you go: http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
Will this work if I accidentally did wipe davlink in TWRP after I flashed a rom? I can get into TWRP but cant reflash rom and am in boot loop when I try to flash it says MD5 not found
JGuinan007 said:
Will this work if I accidentally did wipe davlink in TWRP after I flashed a rom? I can get into TWRP but cant reflash rom and am in boot loop when I try to flash it says MD5 not found
Click to expand...
Click to collapse
Is that a serious question???
I used red size 6 type in that post to make clear what that trick is NOTfor.....
You must have done a little more than "accidentally wipe Dalvik" my friend. Dalvik would just get rebuild on the next boot if you wiped it.
The message that no MD5 is found is pretty normal if no MD5 is present, but it would not prevent you from flashing the rom.
My wild guess is that you somehow corrupted /data and it won't mount, but I don't really know because your post lacks anything that might be helpful.
Like specific information.
Try again.
Harder.
berndblb said:
Is that a serious question???
I used red size 6 type in that post to make clear what that trick is NOTfor.....
You must have done a little more than "accidentally wipe Dalvik" my friend. Dalvik would just get rebuild on the next boot if you wiped it.
The message that no MD5 is found is pretty normal if no MD5 is present, but it would not prevent you from flashing the rom.
My wild guess is that you somehow corrupted /data and it won't mount, but I don't really know because your post lacks anything that might be helpful.
Like specific information.
Try again.
Harder.
Click to expand...
Click to collapse
I'm still not sure what happened. I was flashing KatKiss-7.1_TF700T_015.zip and left my tablet on my desk. I ran out to the store and came home to my 6yo son holding the tablet and telling me it wasn't working. From what I gathered from what he said was he typed "yes" but wasn't sure what option he picked in TWRP. Going through options I think he picked the option to wipe cache dalvik after the rom was flashed but I am still not 100% sure what happened all I know is I'm stuck on Katkiss boot loop and when I go into TWRP to flash anything else it tells me failed no md5 or something along those lines
JGuinan007 said:
I'm still not sure what happened. I was flashing KatKiss-7.1_TF700T_015.zip and left my tablet on my desk. I ran out to the store and came home to my 6yo son holding the tablet and telling me it wasn't working. From what I gathered from what he said was he typed "yes" but wasn't sure what option he picked in TWRP. Going through options I think he picked the option to wipe cache dalvik after the rom was flashed but I am still not 100% sure what happened all I know is I'm stuck on Katkiss boot loop and when I go into TWRP to flash anything else it tells me failed no md5 or something along those lines
Click to expand...
Click to collapse
jmms1124.
Here is the instructions that I followed that restored my TF700T:
Download and install ADB, Fastboot and the required drivers - Download and run this cool little tool which has it all packed into one: [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.1 - xda-developers (don't forget to hit the Thanks button)
NOTE: at the moment Fastboot seems to have issues with Windows 8
This awesome tool installs the ADB and Fastboot.exe to a folder on your C:\ drive (look for a file titled “adb”) as well as the corresponding drivers. This takes about 15 seconds to install following the prompts.
I installed the device drivers - if you have already tried to connect the tablet to your PC and it's recognised as a portable device you should be ok. If not, download the Asus Sync Utility from their support/downloads site and install it.
Download the latest firmware from Asus (Always make sure that you download the correct SKU version -WW, US etc.) and extract the zip twice so you access the blob file (a blob is a collection of binary data stored as a single entity) – copy and paste this blob file into the previously mentioned “adb” folder on your C:\ drive.
Reset the device with a paperclip/needle (about 2 cm down of the SDcard slot)
Power down the tablet and disconnect it from the keyboard dock.
Connect it to your computer via the original USB cable.
Push and hold the Volume Down key (left side of the rocker) and the Power key until you feel the tablet vibrate twice. Let go when you see the tiny script. Read it and it tells you that your tablet is now in Fastboot mode and you will see three or 4 icons (depending on the bootloader version). Select the USB icon to get into the Fastboot mode.
Your PC should acknowledge that a USB device has been connected (an audible indication) Don’t panic if the device does not appear under “My Computer” (as mine did not either – Fastboot will still communicate with it), you can go into Control Panel/Hardware and Sound/ Device Manager and you may see “Fastboot” icon, expand this and the device will be represented again by the “Fastboot” icon. Right click, select “Properties”, Driver tab and then select “Update Driver” and allow it to search automatically and update from the internet. This should then update and change to Asus icons. You now can be certain that you have the current device drivers.
In Windows Explorer navigate to the folder that contains your adb.exe and fastboot.exe
Win 7 press Shift + right click and select "Open command window here".
In the resulting command prompt screen type the following codes (those in bold):
C:\adb\ (or whatever the path to your fastboot folder is..)
fastboot devices (If that command returns a string of numbers and letters, you are good as gold. If it returns: "No devices found", fastboot is not working - yet - and you have to troubleshoot)
Followed by each in turn of the below, selecting Yes as required and allowing each to complete the process:
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
The resulting screen should look something like this below – NOTE, I did make a couple of typos while I was attempting this which returned some multiple choice garble if this happens recheck you input instructions:
E:\asus>fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 1.979s]
finished. total time: 1.980s
E:\asus>fastboot erase recovery
erasing 'recovery'...
OKAY [ 1.023s]
finished. total time: 1.025s
E:\asus>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 39.623s]
finished. total time: 39.624s
E:\asus>fastboot erase boot
erasing 'boot'...
OKAY [ 0.303s]
finished. total time: 0.304s
E:\asus>fastboot erase misc
erasing 'misc'...
OKAY [ 0.602s]
finished. total time: 0.603s
E:\asus>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 1.459s]
finished. total time: 1.460s
fastboot -i 0x0B05 flash system c:\adb\TF700T\blob - depending where you stored your blob, also this was the first time that I saw the loading bar appear on my tablet.
It will now go through the process of reinstalling your Android stock ROM and you should see the something similar to the following:
E:\asus>fastboot -i 0x0B05 flash system e:\asus\blob
erasing 'system'...
OKAY [ 1.731s]
sending 'system' (800935 KB)...
OKAY [134.276s]
writing 'system'...
OKAY [131.640s]
finished. total time: 267.649s
fastboot -i 0x0B05 reboot
E:\asus>fastboot -i 0x0B05 reboot
rebooting...
finished. total time: 0.020s
E:\asus>
I disconnected and rebooted My Asus TF700T and I now have a fully functioning Tablet with a stock ROM.
It has been reported that after completing this you may have some issues getting back get into recovery, hitting RCK and getting the dreaded dead Android (with a red triangle with an exclamation point in the middle). I have not attempted this but have been led to believe that flashing TWRP 2.7.0.1 via Fastboot works.
All acknowledgement and appreciation for this method should go to Buster99, a Senior Member of XDA Developers
http://forum.xda-developers.com/show...2179759&page=2
And to Snoop05, also a Senior Member of XDA Developers for the awesome ADB/Fastboot/Driver tool.
http://forum.xda- developers.com/showthread.php?t=2588979
To whom I am most grateful for the return of my tablet to a working state, I hope this works for you. Good Luck.
Thanks to Browndog181 for this great instruction he made.
Good luck to bring back live to your tablet.:
Scenic-3.
JGuinan007 said:
I'm still not sure what happened. I was flashing KatKiss-7.1_TF700T_015.zip and left my tablet on my desk. I ran out to the store and came home to my 6yo son holding the tablet and telling me it wasn't working. From what I gathered from what he said was he typed "yes" but wasn't sure what option he picked in TWRP. Going through options I think he picked the option to wipe cache dalvik after the rom was flashed but I am still not 100% sure what happened all I know is I'm stuck on Katkiss boot loop and when I go into TWRP to flash anything else it tells me failed no md5 or something along those lines
Click to expand...
Click to collapse
So you got a little software engineer in the house, eh? :cyclops:
For these little rascals you need Apple devices: Safely locked down so the average user cannot do much damage :laugh:
You can do the buster99 described in the post above, but I would leave that as a last resort.
Sounds to me as if your son formatted something and since nothing exciting happened after typing "yes", he tried pushing some other buttons, interrupting the format and corrupting the partition.
I assume you can still boot into recovery and use it and fastboot is also accessible to you. Correct me if wrong.
Use TWRP's build in file manager to check if you can see the contents of your sdcard. If you can, it was not /data he formatted, but /cache or Dalvik. If so, just format cache, wipe Dalvik and reflash the rom
If /data is not accessible you'll have to format it from the Wipe > Advanced menu. That process takes 1 hour+, so send your son out of the house on a play date or some such....
That you see "md5 not found" probably means the box for "Verify MD5" (or "Check MD5" or something similar, can't remember what the official TWRP had there) is checked on the Install page just before you flash. TWRP will abort the installation if it does not find a MD5 for the zip you are trying to flash if you told it to look for one...
Make sure that is unchecked, then flash the rom.
If none of this works, take screenshots or write down the error messages you get and post them.
Here are pictures of what happens when I try to reflash
View attachment 4004171
View attachment 4004172
View attachment 4004173
View attachment 4004174
View attachment 4004180
Yes, /data and /cache cannot be mounted. Did you format them in TWRP?
Your version of TWRP is pretty outdated. You should update it to 2.8+ at the least, the last version is 3.0.2.
Did 2.7 even support f2fs? Can't remember....
Remember that if you format data you end up with ext4 file system and have to convert to f2fs again.
Sent from my TF700T using Tapatalk
I think i'm sending my son to boarding school. I'm not sure if he formatted them he has no idea what he did I know I can only use external sd to try to flash should I get TWRP 3.0.2 to my extenal sd and flash that or will that not work since it may have to be reformated? and how do I go about that?
JGuinan007 said:
I think i'm sending my son to boarding school. I'm not sure if he formatted them he has no idea what he did I know I can only use external sd to try to flash should I get TWRP 3.0.2 to my extenal sd and flash that or will that not work since it may have to be reformated? and how do I go about that?
Click to expand...
Click to collapse
No man, you have a working recovery now. Fix your problems first, then update the recovery.
BTW, I don't even know if you can properly flash Nougatella with TWRP 2.7. Maybe it's YOU who should be sent to boarding school... :angel:
Ok, so go to Wipe > Format Data, type yes and place the tablet on a high shelf. Leave it alone for an hour plus, this takes a while (and make sure it has enough juice)
Then go to Wipe > Advanced > check Cache and swipe the button. This will take a minute or two
Now go back to the home page, go to Mount and see if it lets you mount data, cache and microSD (check mark next to it). If it does not, reboot into recovery, go to Mount and see if they are mounted now. You are probably ok at this point. If you can mount the partitions you can flash a rom, but I think you should update TWRP first.
I don't believe anyone has made a recovery flashable package for 3.0.2 so flash it in fastboot. If you are not sure how, go to the General section and check out my Beginners Guide - it's all in there.
Once that is done, when you reboot (fastboot reboot), be ready to grab the tablet. Let it buzz once, then push and hold the Volume Down button to get into fastboot again and enter recovery through the RCK icon.
You should now have TWRP 3.0.2 on there.
Now convert data to f2fs (there's another guide in General for that), then flash the rom, gapps and SuperSU.
Enjoy