Any help would be greatly appreciated. I recently flashed the new TRWP using fastboot. Went fine. I then tried to wipe and flash the newest version of KatKiss. I thought it also went fine but after reboot, it bootloops TWRP. I can tell the tablet to boot Android, but it just hangs. Then when I try to boot back into TWRP, it starts the bootloop all over again. Here is what it's doing during bootloop.
Running OpenRecoveryScript
E:Could not mount /data and unable to find crypto footer.
E:Unable to mount '/data'
E:Unable to recreate /data/media folder.
Updating partition details...
E:Unable to mount '/data'
...done
E:Unable to mount storage.
E:Unable to mount /data/media during GUI startup.
Full SELinux support is present.
E:Unable to mount /data/media/TWRP/.twrps when trying to read settings file.
Processing AOSP recovery commands...
E:Unable to mount '/data'
-- Wiping DATA Partition...
Formatting Cache using make_ext4fs function.
After about 1 minute it will follow with...
E:Unable to mount '/data'
-- Data Partition Wipe Complete!
Done processing script file
It will then reboot within 3 seconds after displaying the last line, and begin it all over again.
I'm hoping someone can tell me what options I have at this point. Would I be able to return to stock using fastboot and ASUS's blob from their website? Again, any help is greatly appreciated!
Solved.
I had already figured on buying a new tablet regardless, so I figured I'd go ahead and try to recover using fastboot. It did work. I noticed this post had a few views, and on the chance there were other people having the same issue, I'll post how I did it. I recommend using Windows 7 for this.
Download the appropriate firmware from ASUS's website. (WW, US, CN, JP etc...) Unzip the file twice until you have the META-INF folder and blob file. I placed both of these into a folder named "TF300t" directly on the C drive.
Install your device drivers, I used the Google SDK drivers.
Boot into fastboot.
Run these commands...
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\TF300t\blob (Again, this is where I saved my blob file.)
You should see something along these lines, when flashing your system...
C:\>fastboot -i 0x0B05 flash system c:\TF300t\blob
erasing 'system'...
OKAY [ 1.665s]
sending 'system' (800931 KB)...
OKAY [142.128s]
writing 'system'...
OKAY [155.462s]
finished. total time: 299.255s
When it's finished, run the last command...
fastboot -i 0x0B05 reboot
From this point, you should be booted back into stock.
Recreate the partition
anim0sity said:
I had already figured on buying a new tablet regardless, so I figured I'd go ahead and try to recover using fastboot. It did work. I noticed this post had a few views, and on the chance there were other people having the same issue, I'll post how I did it. I recommend using Windows 7 for this.
Download the appropriate firmware from ASUS's website. (WW, US, CN, JP etc...) Unzip the file twice until you have the META-INF folder and blob file. I placed both of these into a folder named "TF300t" directly on the C drive.
Install your device drivers, I used the Google SDK drivers.
Boot into fastboot.
Run these commands...
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\TF300t\blob (Again, this is where I saved my blob file.)
You should see something along these lines, when flashing your system...
C:\>fastboot -i 0x0B05 flash system c:\TF300t\blob
erasing 'system'...
OKAY [ 1.665s]
sending 'system' (800931 KB)...
OKAY [142.128s]
writing 'system'...
OKAY [155.462s]
finished. total time: 299.255s
When it's finished, run the last command...
fastboot -i 0x0B05 reboot
From this point, you should be booted back into stock.
Click to expand...
Click to collapse
anim0sity
What happened if you dont have the blob???
I had a tab, i complete erase all the partition and i cannot install any app, always had error 963
How i can recreate all the partition of my tablet?
It running android 5 lollipop
Regards,
Shouldn't be any reason you don't have the blob file. You can download it straight from ASUS's website. When you download it, it comes in a zip file. You have to extract it twice. So unzip the original zip file downloaded, then unzip the file you get from unzipping the original. From there, you should have the blob file needed to flash your tablet back to stock using fast boot / sdk tools.
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
anim0sity said:
Shouldn't be any reason you don't have the blob file. You can download it straight from ASUS's website. When you download it, it comes in a zip file. You have to extract it twice. So unzip the original zip file downloaded, then unzip the file you get from unzipping the original. From there, you should have the blob file needed to flash your tablet back to stock using fast boot / sdk tools.
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
Click to expand...
Click to collapse
Hi Anim0sity
I downloaded the package and starting doit the process
H:\android-sdk\platform-tools>fastboot devices
015d15b4fc481208 fastboot
H:\android-sdk\platform-tools>fastboot erase system
_
Now is hanging here what i can do it??
Thanks
successful
Hi
After many tries and plug the usb cable in the back of my tower i successful install the firmware
Regards,
HI to rstore to stock using twrp, is it as simple as downloading the file to the tablet, unziping once then flashing the resulting file, or is it a bit more difficult than that?
Related
Hello everybody,
Before telling you about my issue, i should mention that i am a complete newbie regarding flashing kernels. This was my first try, and it didn't work out too well.
I needed to test the USB OTG/Host Functionality for a project at work, and i read that it was possible to enable it on the Nexus S by flashing a custom kernel (kernel_usbhost_build5_icsnexuss from sztupy). It's probably worth mentioning that prior to this i updated the phone to Android 4.0.3.
So i started this morning by rooting it, unlocking the bootloader and installing CWM.
At that point i realized that the recovery mode wasn't accessible : the graphics of the droid with an open belly appears for half a second, and then it gives me the black screen treatment for about a minute before rebooting.
However since there are other ways to flash kernels, i figured i could do without recovery so i didn't look more into it.
I then flashed the kernel using fastboot with this command :
Code:
C:\Program Files\Android\android-sdk\tools>fastboot flash:raw boot H:\data\Downloads\kernel_usbhost_build5_icsnexuss\kernel\zImage
creating boot image...
creating boot image - 3446784 bytes
sending 'boot' (3366 KB)...
OKAY [ 0.422s]
writing 'boot'...
OKAY [ 0.500s]
finished. total time: 0.922s
From the trace i figured that all went well, but when i reboot it stays blocked on the splash screen with the Google logo. Since then i tried flashing several other kernels, without any success. Also tried to flash an update.zip (both ICS and GB) over fastboot but i get this error :
Code:
C:\Program Files\Android\android-sdk\tools>fastboot update H:\data\Downloads\upd
ate.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
So to sum it up i now only have access to the bootloader, without recovery mode.
Before you all jump on me, i know what i did is bad habits (i should have tested the kernel before flashing it), i did it in a hurry without checking i had all sufficient knowledge, and to be honest i would probably have been more careful if was doing it on my personal device.
Truth is now i'm really desperate because i turned my company issued phone into a brick and don't have the slightest idea what to do about it...
Is there any guru out there who knows how i could get out of this ?
Thanks a lot !
Download clockworkmod recovery and use fastboot to flash it.
Fastboot flash recovery yourfilename.img
Enter recovery and mounts and storage and mount USB storage
Transfer the kernel you want to your SD card. The one you flashes isn't a kernel I'm almost sure.
Try a different one.
Then transfer a rom to your SD card.
Factory reset/full wipe, then go to mounts and storage and format everything except your sdcard.
DO NOT FORMAT YOUR SD CARD!!!
Once that is done go to install zip from sdcard and flash the rom and then the kernel and reboot. Should be fine then. Keep me posted.
..
Election Day said:
The image you need would be this ClockworkMod img. Save it somewhere, cd to the sdk/platform-tools/ directory and then do:
Code:
fastboot flash recovery /path/to/saved/file/recovery-clockwork-5.0.2.0-crespo.img
Just drag and drop the file in your terminal, after typing the space after "recovery".
Furthermore, what nodstuff said.
Click to expand...
Click to collapse
Ha ha oops! Forgot that part!
I usually just cd to the one where I have recovery saved!
..
Thanks a lot for answering so quickly !
I'll give it a try on Monday, let you know how it goes.
Election Day said:
Yes, you can also do that, of course. In that case you'd have to provide the full path for fastboot. Or maybe you don't have to on Windows? I don't really use that operating system to be honest.
In that case it would be something like:
Code:
C:\Program Files\Android\android-sdk\tools\fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
Looking at OP's quotes that is probably the most logical way in this case, you're right.
Click to expand...
Click to collapse
No I just cd to downloads (where recovery file would be) in terminal, type: fastboot flash recovery xxxxxx img
And that's it.
I set the path to fast boot and adb in environmental variables in device manager.
Maybe that's why.
..
Just tried out your tips, worked like a charm !
However I had to wipe everything twice before it would let me update to 4.0.3, I would get this weird error :
file_getprop: failed to stat "/system/build.prop": No such file or directory
Anyway now I'm back on ICS and, following your advice, i found another kernel to flash : Matr1x. No problem with this one, now I can test USB OTG.
Thanks again, you guys rule !
Hello all.
I erased system partition in asus fonepad7 me175cg dual sim with fastboot erase system
now i cant flash it.
i tried:
fastboot flash system system.zip before erasing /data errors:invalid argument after erasing /data errors: file exists
fastboot flash update system.zip errors: unable to rename file /cache/update.zip: cross-device linkE:unable to write fi
E:unable to write file: /cache/update.zip
fastboot flash system firmware.zip errors: E:zlib memory/data/corruption error failed:File exists
fastboot flash update firmware.zip
and i renamed the system.zip to img, erros like zip.
(i made system.zip from firmware downloaded from asus)
(the firmware is in this link)
when i turn my device on, it loops on intel logo.
what i do now?
surry for bad english
__________________________________________________ _________-
I dont like sex with non-partner. because i think it makes me like animals
......
is there any way?
Which file exists?
Which partition i should erase for delete exist file?
__________________________________________________ _________
I dont like sex with non-partner. because i think it makes me like animals
nexus 5
android 4.4.2
bootloader version: HHZ11K
Secure boot: enabled
unlocked
rooted
encrypted (i have set a pattern to unlock)
TWRP 2.6.3.4
Xposed module (not sure which version or if it is relevant at all)
xprivacy (not sure which version or if it is relevant at all)
suddenly, while i was surfing twitter, the phone restarted and attempted to install an update (not sure if it was 4.4.3 or Lollipop).
The phone went into bootloop.
My concern here , for now, is not how to fix it. I just need to retrieve my data (contacts, pics, calendar,...).
I held the power button and volume down to load into bootloader. from there i started TWRP. I was greeted with "please enter your password". I entered my pattern following the below arrangement
1 2 3
4 5 6
7 8 9
after several attempts which always ended with "Password failed. Please try again" i hit "cancel". This took me to the main TWRP screen.
I was worried about my data so i tried to copy everything to my pc through "adb pull sdcard/ C:\test" through terminal but i only got two folders namely "sys" and "tmp" but none of my personal data
In TWRP i touched "mount" to find the following..
"Select Partition to Mount:"
[ ] System
[ ] Cache
[ ] Persist
[ ] firmware
[ ] USB-OTG
below them there is a line that says "Storage: Internal Storage (0 MB)"
below that it says "Decrypt Data". If i touch it, it asks to enter my password. Again, i enter my password and it says password failed.
The log has this:
Updating Partition details...
E:Unable to mount ' /cache'
E:Unable to mount ' /persist'
E:Unable to mount storage
E:Unable to mount ' /cache'
E:Unable to mount ' /cache'
E:Failed to decrypt data.
I think that i need to update TWRP to 2.8.2.0 at least in order to decrypt my data as previous versions don't support decryption and/or pattern passwords. Am i right?
if so, how can i update TWRP to the latest version ?
I tried flashing 2.8.4.0 through fastboot with no luck. I have tried the following during the flashing process:
1) flashed it and then tried starting TWRP immediately.
2) flashed it and then restarted bootloader and then tried starting TWRP
3) flashed it and then started system, which took me into bootloop, shutdown phone
and restart into bootloader then tried starting TWRP.
No matter what i do it always goes back to 2.6.3.4 :crying:
I tried to update it from within TWRP. I pushed TWRP 2.8.4.0 which was in zip format (jjd-openrecovery-twrp-2.8.4.0-hammerhead.zip which i took from this thread ) to the main directory "/". Then inside TWRP i went to install, choose the zip file, swiped right to confirm flash to only get the following:
at the top it says "Zip install complete"
then in like a feedback window this is written:
E : Mount : unable to find partition for patch '/jj
error flashing zip 'jjd-openrecovery-twrp-2.8.
updating partition details...
E:Unable to mount ' /cache'
E:Unable to mount ' /persist'
E:Unable to mount storage
finally at the bottom it says Failed (in red)
no need to say that it is still stuck on 2.6.3.4
Am i heading in the right direction ? if yes how can i update TWRP?
If not, Is there any other way to retrieve my data ?
Is it possible to fix this thing with out a wipe and keep my data intact?
Help plz
have you tried flashing only the cache partition through fastboot?
Thanks for your reply
I downloaded the factory image for nexus 5 from "developers dot google dot com/android/nexus/images#hammerhead" (version 4.4.2 (KOT49H) )
I kept extracting the zip file until I arrived at cache.img
copied it to the folder fastboot.exe is located in
run the command
Code:
fastboot flash cache cache.img
through terminal while in fastboot mode
i got the following:
erasing 'cache'...
OKAY [ 0.125s]
sending 'cache' (13348 KB)...
OKAY [ 0.671s]
writing 'cache'...
FAILED (remote: flash write failure)
finished. total time: 0.983s
I started the phone, it passed by the bootloop but then i got a message that says:
Unfortunately, google search has stopped
Unfortunately, the process com.google.process.gapps has stopped
Unfortunately, Google play has stopped
and couple of other similar messages
then i'm greeted with android setup screen (as if I'm running the phone for the first time; choosing language, time ...etc
while I'm in the middle of the setup process, the phone restarts. and it keeps happening again and again
Is there anything else I can do ?
crobh said:
Thanks for your reply
I downloaded the factory image for nexus 5 from "developers dot google dot com/android/nexus/images#hammerhead" (version 4.4.2 (KOT49H) )
I kept extracting the zip file until I arrived at cache.img
copied it to the folder fastboot.exe is located in
run the command
Code:
fastboot flash cache cache.img
through terminal while in fastboot mode
i got the following:
erasing 'cache'...
OKAY [ 0.125s]
sending 'cache' (13348 KB)...
OKAY [ 0.671s]
writing 'cache'...
FAILED (remote: flash write failure)
finished. total time: 0.983s
I started the phone, it passed by the bootloop but then i got a message that says:
Unfortunately, google search has stopped
Unfortunately, the process com.google.process.gapps has stopped
Unfortunately, Google play has stopped
and couple of other similar messages
then i'm greeted with android setup screen (as if I'm running the phone for the first time; choosing language, time ...etc
while I'm in the middle of the setup process, the phone restarts. and it keeps happening again and again
Is there anything else I can do ?
Click to expand...
Click to collapse
That means it's borked. You have to RMA it with Google or send it to LG repair.
BirchBarlow said:
That means it's borked. You have to RMA it with Google or send it to LG repair.
Click to expand...
Click to collapse
I have bought it from google directly but I live overseas.
Tried the local LG maintenance center, they guy there didn't seem knowledgeable on the issue. He said he can try formating it and it might work again but has no idea of recovering the pics and other personal data.
I'm starting to lose hope :crying:
new attempt
I tried wiping cache from twrp and then starting the system. this happen:
Google logo for few minutes
then the four circles merging into white circle animation
then three message pops up,one by one, saying
"Android us upgrading" at the top in blue (this stays in all three messages)
and below it, it says
starting apps
upgrading contacts database
finishing boot
and then it returns to the four circles and then the messages again and again and again
Try flashing just the system.img.
Wakamatsu said:
Try flashing just the system.img.
Click to expand...
Click to collapse
So i extracted System.img from 4.4.2 (KOT49H) and then through terminal while in fastboot i wrote
Code:
fastboot flash system system.img
and the result was..
erasing 'system'...
OKAY [ 0.140s]
sending 'system' (702500 KB)...
OKAY [ 24.866s]
writing 'system'...
FAILED (remote: flash write failure)
finished. total time: 25.178s
What could be the reason for this ?
Sounds like yet another corrupted emmc. The usual test for this is to try locking the bootloader. If nothing happens and it reverts to unlocked it's dead. You could try the lg service but I have no idea if they would accept a warranty /rma
Sent from my Nexus 5 using XDA Free mobile app
Hello !
Well, after long research and testing some solutions, I create this post because I'm stuck at one point.
So, after a wipe in the fasboot mode, my TF700 get stuck into a bootloop with no access to recovery (The more I can have is 5 second with the TWRP splashscreen before rebooting). The ROM that was installed on my tablet is Cromi-kk.
I followed this help thread : http://forum.xda-developers.com/transformer-tf300t/help/guide-t2854495 and I'm stuck at the last point
Code:
fastboot -i 0x0B05 flash system boot.blob
Here is what it said on my computer :
Code:
[email protected]:~$ sudo fastboot -i 0x0B05 flash system boot.blob
erasing 'system'...
OKAY [ 2.355s]
sending 'system' (800927 KB)...
but nothing is moving on the computer, and the tablet is still displaying the fastboot screen...
So I really don't know what to do now, I hope one of you can have a solution
Thank you in advance !
Heck! I cannot believe this went undetected for so long!!! @lj50036
Hey Josh, have a look at this and make the edit! LMAO
@nhibel: Assuming you are trying to flash the stock blob in fastboot and you extracted the stock rom zip twice and put the file called just "blob" into your fastboot folder, the command to flash the stock blob is
Code:
fastboot -i 0x0B05 flash system blob
Nothing is happening because fastboot cannot find a file named boot.blob. Which makes sense since it does not exist. Unless you unpacked the blob.....
I don't think it's because of that. On the help thread it is said to rename the blob file into boot.blob, what I've did ^^
I tried again with renaming the file to blob, but it's the same, nothing is happening :/
Code:
[email protected]:~$ sudo fastboot -i 0x0B05 flash system blob
[sudo] Mot de passe de camille*:
erasing 'system'...
OKAY [ 2.431s]
sending 'system' (800927 KB)...
Maybe you can try the BUSTER99 way to access your bootloader.
http://forum.xda-developers.com/showthread.php?t=2179759&page=6
This was ones the sollution for my TF700T.
Good luck.
Scenic-3
nhibel said:
I don't think it's because of that. On the help thread it is said to rename the blob file into boot.blob, what I've did ^^
I tried again with renaming the file to blob, but it's the same, nothing is happening :/
Code:
[email protected]:~$ sudo fastboot -i 0x0B05 flash system blob
[sudo] Mot de passe de camille*:
erasing 'system'...
OKAY [ 2.431s]
sending 'system' (800927 KB)...
Click to expand...
Click to collapse
Show me a screenshot of your fastboot folder with "show extensions" enabled and make sure the blob is not named blob.blob.
I probably would start from scratch: Delete all blobs from the fastboot directory, extract the blob from Asus firmware, drag it "as is" into fastboot directory and use the fastboot flash system blob command
Here is some good news !
At first, I was trying to flash the blob from a Linux computer, but it wasn't working. So I tried again from another computer, which running on Windows 10. Again, it didn't work, exactly the same than on the Linux computer.
Finally, I tried something else. When I was looking for solutions at the beggining of my problem, I've dowloaded a twrp.blob, but I was unable to flash it at this time. I just tried again, and thank of the help of the help thread, I finally succeeded to flash TWRP (I had to try 2 times before the flash succeeded), and I should be able now to flash a rom !
Well, I lost everything that was on my device, but it works !
Thank you so much for spending some time to help me !
berndblb said:
Heck! I cannot believe this went undetected for so long!!! @lj50036
Hey Josh, have a look at this and make the edit! LMAO
@nhibel: Assuming you are trying to flash the stock blob in fastboot and you extracted the stock rom zip twice and put the file called just "blob" into your fastboot folder, the command to flash the stock blob is
Code:
fastboot -i 0x0B05 flash system blob
Nothing is happening because fastboot cannot find a file named boot.blob. Which makes sense since it does not exist. Unless you unpacked the blob.....
Click to expand...
Click to collapse
I am confused ??
Thx Josh
So was I. Never mind. Didn't realise you instructed to rename the blob... @[email protected]
Sent from my K00C using Tapatalk
I can't flash or boot TWRP. I get the following error.
What can I do? without losing data?
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot "C:\Program Files (x86)\Minimal ADB and Fastboot\twrp.img"
downloading 'boot.img'...
OKAY [ 0.784s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.835s
Help.
Hey! I've run over the similar issues while trying to port ubuntu touch.
try switching slots by using 'fastboot --set-active=a' reboot. If it worked, go to TWRP (don't change slots or wipe storage) and dirty flash stock 9, then change slot and flash stock 9 again.
If it didn't work:
Grab https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665, unzip it, then unzip images.zip
and open visible .bat file (flash all or something similar in name).
You can copy all fastboot flash * commands and execute them in your terminal.
NOTE: it uses \r instead of \n because the script was written on windows, so executing in by 'bash flashall.bat' will cause errors.
This has worked for me, I was able to boot into TWRP and continue porting
(I've tested this on op6t)
mrcyjanek said:
Hey! I've run over the similar issues while trying to port ubuntu touch.
try switching slots by using 'fastboot --set-active=a' reboot. If it worked, go to TWRP (don't change slots or wipe storage) and dirty flash stock 9, then change slot and flash stock 9 again.
If it didn't work:
Grab https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665, unzip it, then unzip images.zip
and open visible .bat file (flash all or something similar in name).
You can copy all fastboot flash * commands and execute them in your terminal.
NOTE: it uses \r instead of \n because the script was written on windows, so executing in by 'bash flashall.bat' will cause errors.
This has worked for me, I was able to boot into TWRP and continue porting
(I've tested this on op6t)
Click to expand...
Click to collapse
Switching slots helped me. I can get into TWRP after a botched Magisk 22 update. Thanks.
What do you mean "dirty flash stock 9?" And, does that mean all my data will be erased?