I've been using Cromi-X 4.7 since Mid to Late summer for my daily and have had zero issues. Last night however, my TF300 chirped to let me know I had an email, I turned the screen on and then it began bootlooping. I do have access to Recovery, and I've tried wiping and flashing a few other ROMs that I had on my SD card, but they all make it as far as the splash screen then freeze and reboot. So I'm a little confused as to where to go from here.
Recovery: TWRP v2.5.0.0
ww_epad-10.6.1.27.1-20130711
Any advice would be much appreciated. Thanks!
cresco299 said:
I've been using Cromi-X 4.7 since Mid to Late summer for my daily and have had zero issues. Last night however, my TF300 chirped to let me know I had an email, I turned the screen on and then it began bootlooping. I do have access to Recovery, and I've tried wiping and flashing a few other ROMs that I had on my SD card, but they all make it as far as the splash screen then freeze and reboot. So I'm a little confused as to where to go from here.
Recovery: TWRP v2.5.0.0
ww_epad-10.6.1.27.1-20130711
Any advice would be much appreciated. Thanks!
Click to expand...
Click to collapse
If you can use recovery, I suppose you can use fastboot too?
Try the following:
fastboot erase misc
fastboot erase staging
fastboot reboot
If that won't work, look for Buster99's script to erase everything and reflash stock Asus ROM. Fixed issues for a lot of people allowing you a fresh start.
Sent from my TF300T using Tapatalk
f69m said:
If you can use recovery, I suppose you can use fastboot too?
Try the following:
fastboot erase misc
fastboot erase staging
fastboot reboot
If that won't work, look for Buster99's script to erase everything and reflash stock Asus ROM. Fixed issues for a lot of people allowing you a fresh start.
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
Thankyou! I had to re-educate myself on Fastboot but once that was done I was able to try your suggestions. Your first one did not do the trick, but Buster99's got me most of the way. I had to reflash the TWRP near the end of his process to get it to work for me.
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash recovery C:\Users\Jeff\Downloads\twrp-2.5.0.0-JB.blob (THIS IS THE LINE I ADDED)
fastboot -i 0x0B05 flash system C:\Users\Jeff\Documents\WW_epad-user-10.6.1.15.3\blob
fastboot -i 0x0B05 reboot
So maybe my recovery was messed up? At anyrate, it looks like I'm back in action. For anyone who needs to follow how all this was done, there is a good fastboot tutorial here. and here is the link to Buster99's solution.
Thankyou for pointing me in the right direction f69m!
cresco299 said:
Thankyou! I had to re-educate myself on Fastboot but once that was done I was able to try your suggestions. Your first one did not do the trick, but Buster99's got me most of the way. I had to reflash the TWRP near the end of his process to get it to work for me.
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash recovery C:\Users\Jeff\Downloads\twrp-2.5.0.0-JB.blob (THIS IS THE LINE I ADDED)
fastboot -i 0x0B05 flash system C:\Users\Jeff\Documents\WW_epad-user-10.6.1.15.3\blob
fastboot -i 0x0B05 reboot
So maybe my recovery was messed up? At anyrate, it looks like I'm back in action. For anyone who needs to follow how all this was done, there is a good fastboot tutorial here. and here is the link to Buster99's solution.
Thankyou for pointing me in the right direction f69m!
Click to expand...
Click to collapse
Oops, careful!
You are using the wrong recovery.
For the bootloaders coming with 10.6.* ROMs you need to use TWRP -42.
Don't use -jb, that is for the older 10.4.* bootloaders.
Sent from my TF300T using Tapatalk
f69m said:
Oops, careful!
You are using the wrong recovery.
For the bootloaders coming with 10.6.* ROMs you need to use TWRP -42.
Don't use -jb, that is for the older 10.4.* bootloaders.
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
That would explain why I had to reinstall an updated TWRP to access recovery. I know just enough to make my self dangerous
Thank you again.
Related
I to everybody. I bricked my asus tf300t.
When the device power on starts on cwm and i cant shut down because restart on cwm.
I can access to adb, so i've tried to start fastboot whit command
Code:
adb reboot-bootloader
so i've tried to flash to rom stock, but when i start flash the fastboot freeze but windows don't return me any error on cmd.
Any ideas??
Help pls
Aaika said:
I to everybody. I bricked my asus tf300t.
When the device power on starts on cwm and i cant shut down because restart on cwm.
I can access to adb, so i've tried to start fastboot whit command
Code:
adb reboot-bootloader
so i've tried to flash to rom stock, but when i start flash the fastboot freeze but windows don't return me any error on cmd.
Any ideas??
Help pls
Click to expand...
Click to collapse
Your tablet is ****ed up like the ones of many others.... You have to wait for a solution
matt95 said:
Your tablet is ****ed up like the ones of many others.... You have to wait for a solution
Click to expand...
Click to collapse
Mmm i know by myself that my tablet is out. Do you have an idea?
Aaika said:
Mmm i know by myself that my tablet is out. Do you have an idea?
Click to expand...
Click to collapse
I've the same problem. I deleted cwm with this command:
Code:
fastboot -i 0x0b05 erase cache
fastboot -i 0x0b05 erase userdata
fastboot -i 0x0b05 erase recovery
fastboot -i 0x0b05 erase system
and now the device boot and stay block on asus screen, but you can access to fastboot holding Power and Volume -.
Now i'm trying to flash to stock rom.
rizzus said:
I've the same problem. I deleted cwm with this command:
Code:
fastboot -i 0x0b05 erase cache
fastboot -i 0x0b05 erase userdata
fastboot -i 0x0b05 erase recovery
fastboot -i 0x0b05 erase system
and now the device boot and stay block on asus screen, but you can access to fastboot holding Power and Volume -.
Now i'm trying to flash to stock rom.
Click to expand...
Click to collapse
The problem isn't with the recovery, if you flashed the wrong recovery your partition are messed up now and you won't be able to flash anything through fastboot
matt95 said:
The problem isn't with the recovery, if you flashed the wrong recovery your partition are messed up now and you won't be able to flash anything through fastboot
Click to expand...
Click to collapse
But i don't flash anything: i bricked tf300t before start flashing.
When i flash recovery the device won't start. It was only in loop. But the original stock was there.
Can i flash a new recovery? Maybe a TWRP?
UPDATE: before the erases i have the ROM stock and it was starts from fastboot. Can someone, who have the same situation, confirm it?
Inviato dal mio Galaxy Nexus con Tapatalk 2
I just restored from the official google 4.4.2 images and my phone cant get past the Google screen. Please help!
bobyum said:
I just restored from the official google 4.4.2 images and my phone cant get past the Google screen. Please help!
Click to expand...
Click to collapse
You flashed the factory images?
bobyum said:
I just restored from the official google 4.4.2 images and my phone cant get past the Google screen. Please help!
Click to expand...
Click to collapse
Do a data factory reset and wipe the cache both in recovery and reboot bro.
gee2012 said:
Do a data factory reset and wipe the cache both in recovery and reboot bro.
Click to expand...
Click to collapse
Thinking the same thing. But.. I can admit getting in a hurry and flashing the wrong image! :laugh:
I made sure that I was using the right image and it still wont go past the Google screen. Any other ideas?
edit: okay the phone can't even write the recovery to the phone through fastboot! Any other thoughts?
bobyum said:
I made sure that I was using the right image and it still wont go past the Google screen. Any other ideas?
Click to expand...
Click to collapse
Long press the power button force it to reboot. As soon as the screen goes black hold down the volume down button. That will boot you into the bootloader, from there you can get to recovery. Factory reset, wipe cache.
You flashed stock recovery?
If you have stock recovery go to the bootloader like I said earlier. Choose recovery. Then you will see android laying down. Press volume up and power button at the same time. Do a factory reset.
bobyum said:
I made sure that I was using the right image and it still wont go past the Google screen. Any other ideas?
edit: okay the phone can't even write the recovery to the phone through fastboot! Any other thoughts?
Click to expand...
Click to collapse
If you flashed the whole image inclusing userdata.img it should boot usualy, never xperienced it did not personaly. So besides a wipe have no idea bro, you might try to reflash the rom again. Are you using a Toolkit?
gee2012 said:
If you flashed the whole image inclusing userdata.img it should boot usualy, never xperienced it did not personaly. So besides a wipe have no idea bro, you might try to reflash the rom again. Are you using a Toolkit?
Click to expand...
Click to collapse
I did this with the flashh-all.bat provided by the official image. I can't even do that anymore because it just gets stuck when writing the bootloader. Totally out of ideas right now. Is there any way I can reformat the partition through fastboot? Would that help?
bobyum said:
I did this with the flashh-all.bat provided by the official image. I can't even do that anymore because it just gets stuck when writing the bootloader. Totally out of ideas right now. Is there any way I can reformat the partition through fastboot? Would that help?
Click to expand...
Click to collapse
Try this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
After that flash the rom again with flash.all.batt
maybe flash each part individually (not using flashall)
Sent from my Nexus 5 using Tapatalk
gee2012 said:
Try this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
After that flash the rom again with flash.all.batt
Click to expand...
Click to collapse
Unfortunately, it didnt help Still stuck at writing bootloader...
beaver2233 said:
maybe flash each part individually (not using flashall)
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yup, that might work better maybe
hmm so in which order should i flash them in?
edit: I honestly think the flash storage failed. Ill just apply for RMA then. Do you guys know if I bought my phone in early December, will I still be eligible?
bobyum said:
hmm so in which order should i flash them in?
edit: I honestly think the flash storage failed. Ill just apply for RMA then. Do you guys know if I bought my phone in early December, will I still be eligible?
Click to expand...
Click to collapse
How to flash a factory image. Erasing everything in fastboot should have done the trick. Erase everything then do method 2. You have to reboot the bootloader after flashing the bootloader and again after flashing the radio. One year to RMA. .
---------- Post added at 02:14 AM ---------- Previous post was at 01:57 AM ----------
These are the commands I would use. The name of the images for the bootloader and radio are for 4.4.2.
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-m8974a-1.0.25.0.23.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Thanks all for the help! Will try it tomorrow. Hopefully it works
wantabe said:
How to flash a factory image. Erasing everything in fastboot should have done the trick. Erase everything then do method 2. You have to reboot the bootloader after flashing the bootloader and again after flashing the radio. One year to RMA. .
---------- Post added at 02:14 AM ---------- Previous post was at 01:57 AM ----------
These are the commands I would use. The name of the images for the bootloader and radio are for 4.4.2.
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-m8974a-1.0.25.0.23.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Click to expand...
Click to collapse
I'd go one better and look to do a COMPLETE reflash - userdata and all! I'd also rename bootloader-hammerhead-hhz11k.img to bootloader.img and radio-hammerhead-m8974a-1.0.25.0.23.img to radio.img as it means there's less to get wrong! SO, to recap:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash userdata userdata.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot format cache
I'd then boot into the stock recovery and perform a factory reset to make sure everything is in order and then reboot. I've done this exact method a number of times on my Nexus 5 and it works every time
EddyOS said:
I'd go one better and rename bootloader-hammerhead-hhz11k.img and radio-hammerhead-m8974a-1.0.25.0.23.img to just bootloader.img and radio.img to make it easier - less to type out and get wrong!
Click to expand...
Click to collapse
I usually do the same thing too but I left the names as a hint to verify that he had the correct images.
I almost never flash userdata and recovery unless I'm selling a device. I've also never rebooted the bootloader between every image Except after the bootloader and radio images but I agree that your method is covering all the bases!
wantabe said:
I usually do the same thing too but I left the names as a hint to verify that he had the correct images.
I almost never flash userdata and recovery unless I'm selling a device. I've also never rebooted the bootloader between every image Except after the bootloader and radio images but I agree that your method is covering all the bases!
Click to expand...
Click to collapse
As I hardly have any data to backup bar some custom ring tones I always reflash the userdata partition to be thorough. As for the reboots, I've just done it from habit, again just to be thorough. If it still doesn't work after that then it's goosed!
Try using the backup bootloader. Press and hold both volume buttons with the power button. That will take you into the backup bootloader.
Thanks to everyone for helping but I could not even get past writing the bootloader to the phone. I honestly think the flash storage and failed so will be RMAing. Hopefully they will accept it...
after i got my tf700 tablet i unlocked the bootloader and put cwm and cm11 on it, without any problems.
then i tried the same thing on my brothers tf300 i accidentally bricked it, after we bought another one i used the nvflash bricksafe setup on my tf700 so the same thing would not happen to me. then i changed from cwm to philz. later i tried to change the wallpaper in philz and my device froze, so i rebooted and found myself bricked. so i used apx to recover. i got android functionality back but now i have some issues.
1. i cant access recovery, selecting the rck command results in an error: unrecoverable bootloader error (0x00000000)
2. i cant make fastboot flash commands work to reflash a recovery, because the tablet freezes after i hit enter
i have used the "fastboot erase recovery" command too, which seemed to work...
recovery mode usability needs to be restored and possibly a fresh install of the bootloader too.
any help putting it back together either through apx recovery or the android system would be much appriciated!
Did you try to flash the stock blob? Sounds to me like a case for buster99's method:
http://forum.xda-developers.com/showthread.php?t=2179759&page=2
berndblb said:
Did you try to flash the stock blob? Sounds to me like a case for buster99's method:
http://forum.xda-developers.com/showthread.php?t=2179759&page=2
Click to expand...
Click to collapse
Buster99 said:
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
Click to expand...
Click to collapse
thanks for the instructions but i think i will leave this as a last resort as i would rather not have to redo everything i have already done to my device, i hate starting over
A nandroid would have done the trick
Sometimes you have to learn the hard way...
I'm talking about myself: made a nandroid of my CROMi-X installation before flashing CROMBi-KK and then formatted data - without copying the nandroid to microSD - DOH!
Sent from my K00C using Tapatalk
berndblb said:
A nandroid would have done the trick
Sometimes you have to learn the hard way...
I'm talking about myself: made a nandroid of my CROMi-X installation before flashing CROMBi-KK and then formatted data - without copying the nandroid to microSD - DOH!
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
i have a nandroid, on an external source too,
but if you cant get into recovery there is no way to use (or at lease not one that i know)
kirbyonwarpstar said:
i have a nandroid, on an external source too,
but if you cant get into recovery there is no way to use (or at lease not one that i know)
Click to expand...
Click to collapse
In that case, it's easy:
Flash system blob
Flash custom recovery
Restore nandroid
Sent from my K00C using Tapatalk
I buy a tablet tf300t with unlocked bootloader and android version 4.0.3
with CMW 5.5.0.4 make a backup.
after this i try install cm 10.2.1. But system now have a bootloop. I think a have wrong bootloader
now i restore cmw backup, but i have now bootloop too.
Please help my, i try fastboot with 4.2 asus stockrom, but after sending i tablet show write error.
The Tab shows
Failed to process command flash:system error(0x170003)
i make only this:
fastboot -i 0x0B05 flash system blob
should try this? But after this command, tabet have nothing, At the moment, CMW und fastboot running
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
What are now the next step for find a solution for my Bootloop after Asus Sign?
Should try with CMW install Stockrom 4.2. But i read that 4.2 and my CMW 5.5.0.4 are not compatible.
Thank for you support.
buda5767 said:
I buy a tablet tf300t with unlocked bootloader and android version 4.0.3
with CMW 5.5.0.4 make a backup.
after this i try install cm 10.2.1. But system now have a bootloop. I think a have wrong bootloader
now i restore cmw backup, but i have now bootloop too.
Please help my, i try fastboot with 4.2 asus stockrom, but after sending i tablet show write error.
i make only this:
fastboot -i 0x0B05 flash system blob
should try this? But after this command, tabet have nothing, At the moment, CMW und fastboot running
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
What are now the next step for find a solution for my Bootloop after Asus Sign?
Thank for you support.
Click to expand...
Click to collapse
There are a few commands missing from there look in my sig and go to the tf700 nvflash link, skip the nvflash stuff and start at the
fastboot commands... Read the hole thread per the parts the are relevant to you...
Feel free to ask me any questions you have, either there or here....
Thx Josh
help, that is very difficult.
i read that, and think i must erase all before i can make fastboot systen. Are i correct?
with CMW 5.5.0.4 install Asus stockfirm isn't a good idea?
if delete recovery etc. is danger my tablet is very empty, if fastboot than not running ...
buda5767 said:
help, that is very difficult.
i read that, and think i must erase all before i can make fastboot systen. Are i correct?
with CMW 5.5.0.4 install Asus stockfirm isn't a good idea?
if delete recovery etc. is danger my tablet is very empty, if fastboot than not running ...
Click to expand...
Click to collapse
Shoot me an email here [email protected]
We can talk more there and when we find a solution to your issue, we can post our results here....
lj50036 said:
Shoot me an email here [email protected]
We can talk more there and when we find a solution to your issue, we can post our results here....
Click to expand...
Click to collapse
Ok, i send a mail
buda5767 said:
Ok, i send a mail
Click to expand...
Click to collapse
I sent one back
Solution:
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system blob (Asus stock firmware)
If Error
fastboot -i 0x0B05 flash system blob -> Failed to process command flash:system error(0x170003)
then use other Asus stock firmware ( DE 4.0.3)
CLOSED
will it work?
fastboot:
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase radio
fastboot erase userdata
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-m8974a-2.0.50.1.16.img
fastboot reboot-bootloader
fastboot flash recovery recovery-clockwork-6.0.4.5-hammerhead.img
device:
go to recovery
recovery:
install zip from sideload
adb:
adb sideload cm-11-20141008-SNAPSHOT-M11-hammerhead.zip
adb sideload pa_gapps-stock-4.4.4-20141011-signed.zip
adb sideload ElementalX-N5-1.10-cm.zip
recovery:
install zip from sd card
install cm-11-20141008-SNAPSHOT-M11-hammerhead.zip
install pa_gapps-stock-4.4.4-20141011-signed.zip
install ElementalX-N5-1.10-cm.zip
clear cache
clear dalvik
reboot system now
profit?
Thanks in advance.
Don't erase all the partitions. Its worthless in this case
Sent from my Nexus 5 using Tapatalk
Besides the fruitless erasing, why do you want to sideload everything and then again do it in recovery??
- Sent from an IceCold Hammerhead!
vin4yak said:
Besides the fruitless erasing, why do you want to sideload everything and then again do it in recovery??
- Sent from an IceCold Hammerhead!
Click to expand...
Click to collapse
Because he didn't read the sticky threads
Sent from my Nexus 5 using Tapatalk
Apart from the erase and sideload then recovery flash stuff, I don't understand this part:
<flash recovery>
device:
go to recovery
Shouldn't he just do a fastboot reboot-recovery and flash the stuff there? Or its better for some reason to boot into it from the device? I mean I remember when 4.4. went out some people said you just couldn't flash all the stuff without booting at least once because there was some script that the stock recovery had to execute first.. this got fixed already?
RusherDude said:
Apart from the erase and sideload then recovery flash stuff, I don't understand this part:
device:
go to recovery
Shouldn't he just do a fastboot reboot-recovery and flash the stuff there? Or its better for some reason to boot into it from the device? I mean I remember when 4.4. went out some people said you just couldn't flash all the stuff without booting at least once because there was some script that the stock recovery had to execute first.. this got fixed already?
Click to expand...
Click to collapse
Never heard about this before. I've seen many guys over here who have directly flashed as soon as they got their hands on this device.
- Sent from an IceCold Hammerhead!
I remember Artem from AndroidPolice had such problem. Ill try to find the post.
There is sometimes a /system/etc/install-recovery.sh
This is sometimes used in rooted stock ROMs to provide root too.
When you unlock the bootloader, you should reboot bootloader before flashing anything.
Sent from my Nexus 5 using Tapatalk
moralex said:
profit?
Click to expand...
Click to collapse
With that many steps, I think you'll be operating at a loss.