Database Info

trying to get cm10, or hydro

Hello, ill start out by saying that ive had quite a few android devices in the past. I usually root them and install custom roms so i am familiar with most commands. I got my new tf300t from newegg when they had their special online. I proceeded to download the OTA update to JB. I then downloaded the bootloader unlock apk from asus and got that done. Then i flashed CWM recovery 5.5.0.4. All working well. Then flashed super user which worked well also. Once i tried to flash the latest cm10 nightly i got stuck at the boot screen. I can still load recovey just fine and get into fastboot without issues. I have tried using another recovery and it flat wouldnt boot. Luckily i was able to flash cwm recovery back and its still booting. I have tried wiping everything before applying the nightly, and after. Both fail to boot
I have also tried mounts and storage within CWM recovery and i am unable to get either internal or external storage to show up on my PC. If i wanted to try the hydro rom which i have downloaded, how do i get the zip file to my internal memory without pc access......
any ideas where i should look next? I know there are quite a few threads with people having issues and i appreciate any response.

So all i have access to is really recovery and fastboot. I have tried flashing a couple boot files via fastboot and now i seem to be in a boot loop as opposed to stuck at the asus logo. recovery and fastboot are still accessible......ears wide open as far as to where i should look next. thanks for any tips or advice!

a brand new tf300t that wont boot is not a good thing I'm sure i screwed up somewhere, i only hope that with access to recovery and fastboot i can get this tab to boot again.

Check you pm

thanks for the response Krab, i replyed to your PM as well

So i found a method of pushing a zip file through ADB and that seems to work well for getting my rom files to the sd card. I copied the hydro rom over and installed it via recovery. Same story boot loop. I then tried a third rom with high hopes and no change. Anyone have any ideas whats going on with my tablet? I'm willing to try just about anything to get this thing working again.

found another thread where they suggested downloading the asus firmware, which i already had and then extracting the blob file from that. I then attempted to flash the blob file from the asus firmware via fastboot with fastboot -i 0x0B05 flash system blob...it appeared to start flashing and then gave me this error:
failed to process command flash:system error 0x170003
no luck that route....

I had the same problem stuck on the Asus screen after attempting to flash custom ROM. the method you describe worked for me.... might of been a bad download i would try to re download the latest xxxx.17 firmware. had to do it twice both times was successful flash system blob
Sent from my ASUS Transformer Pad TF300T using xda premium

alaskan84 said:
found another thread where they suggested downloading the asus firmware, which i already had and then extracting the blob file from that. I then attempted to flash the blob file from the asus firmware via fastboot with fastboot -i 0x0B05 flash system blob...it appeared to start flashing and then gave me this error:
failed to process command flash:system error 0x170003
no luck that route....
Click to expand...
Click to collapse
well i tried the exact same command again, and it worked this time! well it successfully flashed, and im getting the anmiated asus logo as i type!
Im booted into the OS Now!!! So, im wondering if i can now try to flash a cm10 rom, or if i should stay away at this point?

Really frustrated, phone keeps booting to recovery after failing to boot to rom

Hi all, I've been trying for the past 8 hours(you can imagine how frustrated i am right now) to install HatkaXL(http://forum.xda-developers.com/showthread.php?t=2075783) for so long now and I have literally no idea where to go. I was only just trying to switch from cleanrom to Hatka. And I've ended up with absolutely no progress since 8 hours have passed. Actually, i've probably lost progress because i accidentally wiped my data without backing up. Here's what i've done so far:
i'm under AT&T, hboot-1.14, any other info i'll be glad to share. it's rooted and currently unlocked of course.
1. Used fastboot flash boot boot.img to no avail
2. Re-locked bootloader, ran an RUU(i made sure it was compatible), unlocked it and tried to flash HatkaXL froma fresh start
3. Wiped data, cache, etc. then flashed the rom(which still didnt work)
4. flashed TWRP, rebooted, went into TWRP, wiped data, cache, etc. and then flashed HatkaXL
What the problem is that my one x won't go past the HTC screen with all that red developmental font. It'll boot and then go to the screen, stay there for about 10 seconds and then turn off. Then it'll start up again 10 seconds later to boot back to TWRP.
At one point, i encountered a boot loop where it actually went past the red developmental font screen and to the HTCtm Beats Audio and then it just restarted from there. However, now that issue disappeared and it's just booting to recovery after shutting down.
Now that's where I was thinking that maybe since it's booting directly to TWRP that would mean that I would have to go into cmd and 'fastboot flash boot boot.img' right? I did exactly that, one, twice, three times, even with fastboot erase cache.
i can't even remeber everything i did because i'm so tired since i've been up through the night reading throug threads, trying to fix this damn thing.
I would really really appreciate it if anyone could help me out here because i've never been this lost when it came to technology lol.

It sounds like you were on the right track, I am lost why it failed for you?
Can you install cleanrom again? eg is it just HatkaXl that is not working? Perhaps your download is bad or the ROM is simply broken and you need to report it to the dev?
When you were flashing the boot.img did it say success? Did you triple check you are extracting the correct boot.img to the correct folder?
Just to be clear to install ROM's I often do:
1)wipe data and system
2)install ROM
3)fastboot flash boot boot.img

twistedddx said:
It sounds like you were on the right track, I am lost why it failed for you?
Can you install cleanrom again? eg is it just HatkaXl that is not working? Perhaps your download is bad or the ROM is simply broken and you need to report it to the dev?
When you were flashing the boot.img did it say success? Did you triple check you are extracting the correct boot.img to the correct folder?
Just to be clear to install ROM's I often do:
1)wipe data and system
2)install ROM
3)fastboot flash boot boot.img
Click to expand...
Click to collapse
Thanks for the response. Yep, every time i flash the boot.img, it's always a success. i also mae sure it's the correct one.
sending 'boot' (6156 KB)...
OKAY [ 0.933s]
writing 'boot'...
OKAY [ 1.475s]
finished. total time: 2.413s
Click to expand...
Click to collapse
I just tried to install cleanrom 5.1 again and it's not working either. Actually, it's stuck at the red developmental font screen this time so atleast it's not immediately rebooting to go to TWRP.
UPDATE: It's working! CleanROM! Thank you so much man! I'll be back to ask you another question. Gotta go real quick.

Correct me if I'm wrong but clean Rom 5.1 flashes the boot img for you I didn't see you flashing the boot.img the other times successfully so yes it won't get past that HTC screen

a box of kittens said:
Correct me if I'm wrong but clean Rom 5.1 flashes the boot img for you I didn't see you flashing the boot.img the other times successfully so yes it won't get past that HTC screen
Click to expand...
Click to collapse
I also noticed this. Op, a few things to remember when flashing boot.img.
The boot.img needs to be extracted from the rom you are flashing.
The phone must be in bootloader, plugged in to pc and in fastboot usb mode. (the phone will say fastboot usb.
The boot.img must be in the folder with the fast boot and adb programs.
I have more than just a feeling you were doing something wrong
Sent from my One X using xda app-developers app

Thanks for the responses guys, you guys are saving me lots of stress and time.
a box of kittens said:
Correct me if I'm wrong but clean Rom 5.1 flashes the boot img for you I didn't see you flashing the boot.img the other times successfully so yes it won't get past that HTC screen
Click to expand...
Click to collapse
You are correct that clean rom 5.1 flashes it for you, which is through its AROMA installer. However, HatkaXL also uses the AROMA installer, and there's a line in the installation screen where it says "flashing boot.img." - both ROMs have that line. Interestingly, it worked when I followed twistedddx's order so I'm going to try that again.
exad said:
I also noticed this. Op, a few things to remember when flashing boot.img.
The boot.img needs to be extracted from the rom you are flashing.
The phone must be in bootloader, plugged in to pc and in fastboot usb mode. (the phone will say fastboot usb.
The boot.img must be in the folder with the fast boot and adb programs.
I have more than just a feeling you were doing something wrong
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Yup, I have those in the same folder correctly. I always extract the boot.img from the rom zip into the folder with both fastboot and adb(how else would I able to have fastbooted in the first place?), always made sure the phone was in bootloader, plugged in, and in fastboot usb.
edit: I wiped, then installed hatkaXL, then fastboot flash boot boot.img, and now it starts, it gets past the red developmental screen, INTO the HTC Onetm beats audio screen, turns off and then restarts again through the whole process. it's jst looping now.
edit2: Flashed ViperXL, that's working. I guess HatkaXL just isn't for my phone.. sigh. I hope this thread helps anyone else.

devfrost said:
Thanks for the responses guys, you guys are saving me lots of stress and time.
You are correct that clean rom 5.1 flashes it for you, which is through its AROMA installer. However, HatkaXL also uses the AROMA installer, and there's a line in the installation screen where it says "flashing boot.img." - both ROMs have that line. Interestingly, it worked when I followed twistedddx's order so I'm going to try that again.
Yup, I have those in the same folder correctly. I always extract the boot.img from the rom zip into the folder with both fastboot and adb(how else would I able to have fastbooted in the first place?), always made sure the phone was in bootloader, plugged in, and in fastboot usb.
edit: I wiped, then installed hatkaXL, then fastboot flash boot boot.img, and now it starts, it gets past the red developmental screen, INTO the HTC Onetm beats audio screen, turns off and then restarts again through the whole process. it's jst looping now.
edit2: Flashed ViperXL, that's working. I guess HatkaXL just isn't for my phone.. sigh. I hope this thread helps anyone else.
Click to expand...
Click to collapse
Could be a kernel issue.. Try flashing stock kernel after flashing rom?... That's all I can think of. Also, I don't know if you do but I always wipe cache, dalvik, system, and then factory reset in twrp and I've never had any issues with any roms.
Sent from my One X using xda app-developers app

[Q] HTC J Butterfly Half Bricked

Hi, so i got my phone last week. And yesterday, I decided to try and flash some custom roms on it. My device is pretty funny, I live in Hong Kong and when i bought my device, they have done S-OFF, unlocked bootloader, even custom recovery with twrp AND cwm. Now the default recovery was twrp, I tried flashing some roms, tried different ones, my device doesn't acccept them, after installing the rom, my device boots, shows the red text, stuck there for around 15 seconds and it reboots itself into the same state. So I used my twrp backup and flashed the recovery to cwm to give it a shot, the results are the same. And then at point, i booted up into recovery and it says Entering Recovery, and it gets stuck there forever. I can't boot into the system either. I tried using fastboot clear the cache, reflash the two different recoveries, no luck. I can get into bootloader and nothing else. Tried using HBOOT CL99IMG.zip method, but my phone just doesnt accept the roms. Any ideas?
Thankyou, any help would be greatly appreciated.

Any ideas? Anyone? Because all i need to do is to boot into twrp recovery. However, when i try to boot recovery it just says entering recovery, with the htc screen, and stays there forever. Any Suggestions?

Did you try "fastboot erase cache" command ?
Try to flash the boot.img included in your rom.zip with "fastboot flash boot boot.img"

Kroutnuk said:
Did you try "fastboot erase cache" command ?
Try to flash the boot.img included in your rom.zip with "fastboot flash boot boot.img"
Click to expand...
Click to collapse
Yea I did, apparently i got something. I mixed some files from the HTL21 Taiwan zip thingy, with the signed rom. I am able to boot into the os. However once I unlock it it crashes. Recovery still doesnt work :/
Anyways, thanks for the suggestion Appreciate it.

UPDATE: Now the phone isn't accepting anything from fastboot :/
It all says FAILED <remote:not allowed>
This is getting nuts lol

The fastboot is activated in the settings in your rom ?

Not sure about that, probably no :/ but thats the only rom i can get working
I can see it fastboot devices tho

anyone else? anymore ideas? :/

ok, so I got my phone kinda working. I used the htc butterfly toolkit, somehow flashing the X920e recoveries can make it work. I then restored from my previous backup with twrp, which contains system, data, boot. but when i boot into the system, it says loading widget, everything works fine for a while, then it suddenly crashes. I have tried restoring the system with only system and boot without data, still no luck. any ideas?? i have attached my log
any help will be greatly appreciated, thanks
http://www.filedropper.com/traces

[Q] RAZR HD system corrupt after flash.

Hey guys,
I've been using this website as reference for years but never had an issue I hadn't already seen asked.
I've been looking for weeks for a solution to this and haven't found anything.
I tried to flash cm10.1 over my stock 4.1.2 and corrupted the system.
It was booting directly to AP Fastboot and showing an error about not calling the ROM properly.
I tried reflashing using RSD Light 5.7 but every time it tried to flash the system it said the phone returned failed.
So I upgraded RSD to v6.1 and tried again. This time the phone says it flashed properly but it freezes during the droid boot logo.
I've tried using the utility and it gives me the same results.
I can get into factory recovery and I've performed several hard resets. But the phone still freezes whenever it tries to load the system.
I'm using a Motorola Factory Cable on a high speed USB port.
Any ideas why I'm stuck in a soft brick that I can't flash out of?

ShiningRaven said:
Hey guys,
I've been using this website as reference for years but never had an issue I hadn't already seen asked.
I've been looking for weeks for a solution to this and haven't found anything.
I tried to flash cm10.1 over my stock 4.1.2 and corrupted the system.
It was booting directly to AP Fastboot and showing an error about not calling the ROM properly.
I tried reflashing using RSD Light 5.7 but every time it tried to flash the system it said the phone returned failed.
So I upgraded RSD to v6.1 and tried again. This time the phone says it flashed properly but it freezes during the droid boot logo.
I've tried using the utility and it gives me the same results.
I can get into factory recovery and I've performed several hard resets. But the phone still freezes whenever it tries to load the system.
I'm using a Motorola Factory Cable on a high speed USB port.
Any ideas why I'm stuck in a soft brick that I can't flash out of?
Click to expand...
Click to collapse
Format system via any of the custom recoveries before flashing your new ROM - this will wipe out any leftover problems completely & should let you start 100% fresh with a new ROM.

tzlot said:
Format system via any of the custom recoveries before flashing your new ROM - this will wipe out any leftover problems completely & should let you start 100% fresh with a new ROM.
Click to expand...
Click to collapse
I lost my root when I originally got stuck in fastboot. And I can't boot up the phone until I can get it fixed.

ShiningRaven said:
I lost my root when I originally got stuck in fastboot. And I can't boot up the phone until I can get it fixed.
Click to expand...
Click to collapse
Can you get back into fastboot now? If so
Use fastboot to flash a custom recovery (CWM, TWRP or OUDHS)
use the recovery to factory reset, wipe cache/dalvic, AND format system (sometimes in the advanced menu)
then flash rom of your choice.
If you can't get fastboot working you'll need smarter help than I can give you... but the format system step clears out all kinds of gremlins.

I can get into fast boot but I don't have an unlocked boot loader to flash anything custom.

ShiningRaven said:
I can get into fast boot but I don't have an unlocked boot loader to flash anything custom.[/QUOTE
If you can get into fastboot then you should be able to unlock b/l with this toolkit I used it and it worked for me you can also flash rom with it its in the orginial development thread
http://forum.xda-developers.com/showthread.php?t=2154995
Click to expand...
Click to collapse

ShiningRaven said:
So I upgraded RSD to v6.1 and tried again. This time the phone says it flashed properly but it freezes during the droid boot logo.
I've tried using the utility and it gives me the same results.
I can get into factory recovery and I've performed several hard resets. But the phone still freezes whenever it tries to load the system.
I'm using a Motorola Factory Cable on a high speed USB port.
Any ideas why I'm stuck in a soft brick that I can't flash out of?
Click to expand...
Click to collapse
Had the same problem after a fastboot via the utility. Try powering your phone down completely and leaving it off for about 5-10 min. This can be tricky with the hardware buttons so if you have access to TWRP that will help as it has a power off option. You might also try flashing again via the utility. I believe that's what I had to do, but the power down method is what a friend suggested based of his experience with the same exact problem you documented.

FIXED!!!
OK first I want to thank everybody who responded. I got tied up with work and kind of forgot about this project for a few days.
Repeated uses of the Utility and RSD both left me stuck with the phone freezing every time it tried to load the system into memory.
I had checked out the toolbox before but I didn't think I could do much from a locked bootloader.
After your suggestion jmcdonald I tried it again. It says my device isn't available to be unlocked so I tried downgrading back to ICS.
The toolbox says that it failed but it must have fixed something because the phone booted back up to android 4.1.2 stock!
So far I have bricked a lot of phones and learned a lot about ADB in the process of fixing them but I've never had one I was so certain was bricked permanently. But now it seems to be working fine, I'm scared to try rebooting in now.
Definatly going to unlock the bootloader pronto.
Thanks again jmcdonald!

[Q] Hard bricked or what?

Hello, everyone.
So basically this is my issue. One day at work my Moto G restarted randomly and has been stuck in a bootloop ( boot animation cycles infinitely ).
I can access fastboot, booting to recovery freezes on TWRP logo.
My phone is rooted, unlocked and etc. I have tried flashing stock firmware, no changes, not even my custom boot logo and animation don't change.
I have tried using fastboot to erase everything and format but formatting fails saying this filesystem cannot be formatted.
I can access my files by booting into another recovery using fastboot boot recovery.img ( tried with PhilZ ) although it shows everything as it was before this all this ( all files gone, only directories left ).
I noticed that I could use ADB while stuck at TWRP logo. I tried pushing roms and using booted PhilZ to find them but they never appear, I can only push to /tmp, anything else doesn't exists although is shown through booted PhilZ.
I have tried using mkfs.ext4 to format my filesystem, everything went as it should but nothing changed.
TL;DR Bootloop, recovery does not open, fastboot flashing does nothing, adb push doesn't push anything
What the hell is going on with my phone? Any ideas people?

Somehow, your file system can't be accessed....was your phone encrypted?

itouchables said:
Somehow, your file system can't be accessed....was your phone encrypted?
Click to expand...
Click to collapse
It wasn't, I never encrypted it.
Also fastboot getvar all shows that my partition type is RAW.
Shouldn't it be F2FS or EXT4?
Maybe anyone has a proper partition mount point list for the Moto G?
I would try mkfs.ext4 formatting every possible mount point (cache,data,system and etc)
For example dev/block/mmcblk0p38
I found a Moto X mount point list but I have no clue if it's the same or not

Aequus.Mihi said:
Hello, everyone.
So basically this is my issue. One day at work my Moto G restarted randomly and has been stuck in a bootloop ( boot animation cycles infinitely ).
I can access fastboot, booting to recovery freezes on TWRP logo.
My phone is rooted, unlocked and etc. I have tried flashing stock firmware, no changes, not even my custom boot logo and animation don't change.
I have tried using fastboot to erase everything and format but formatting fails saying this filesystem cannot be formatted.
I can access my files by booting into another recovery using fastboot boot recovery.img ( tried with PhilZ ) although it shows everything as it was before this all this ( all files gone, only directories left ).
I noticed that I could use ADB while stuck at TWRP logo. I tried pushing roms and using booted PhilZ to find them but they never appear, I can only push to /tmp, anything else doesn't exists although is shown through booted PhilZ.
I have tried using mkfs.ext4 to format my filesystem, everything went as it should but nothing changed.
TL;DR Bootloop, recovery does not open, fastboot flashing does nothing, adb push doesn't push anything
What the hell is going on with my phone? Any ideas people?
Click to expand...
Click to collapse
Hi! did you find a solution?!

Oliverrlh said:
Hi! did you find a solution?!
Click to expand...
Click to collapse
No. Turns out my phone memory chip was corrupted due to flashing

Aequus.Mihi said:
No. Turns out my phone memory chip was corrupted due to flashing
Click to expand...
Click to collapse
I think I might have a similar situation. Can you give me an advice on how to confirm this?
The only difference in the circumstances is that my fiance's moto g has a custom recovery on it then she tired to install the 5.1 update. Then it would boot into the OS and after while would shut down then go to the recovery. I thought I had solved the issue by doing a factory reset. Everything was going fine until I turn it off. Now I get the boot animation and then a black screen. I can get the load screen on the custom recovery but that is it The computer can still recognize the phone.
Does this sound like your situation?

Icon000 said:
I think I might have a similar situation. Can you give me an advice on how to confirm this?
The only difference in the circumstances is that my fiance's moto g has a custom recovery on it then she tired to install the 5.1 update. Then it would boot into the OS and after while would shut down then go to the recovery. I thought I had solved the issue by doing a factory reset. Everything was going fine until I turn it off. Now I get the boot animation and then a black screen. I can get the load screen on the custom recovery but that is it The computer can still recognize the phone.
Does this sound like your situation?
Click to expand...
Click to collapse
That's the same situation I was in.
Even if you try to flash another ROM, it will never install.
You can't modify any files because the memory is ****ed.
I sold the phone for parts and bought a S4