Database Info

[Q] No Rom, Unable to load on to SD-Ext, Errors when attempting to flash via fastboot

I hate to post this but after 3 days of trying to get this damned phone serviceable I am seeking higher powers.
I have viewed just about every thread I can, and everytime i think I'm getting close only to be disappointed.
I was attempting to root a Rogers HTC One X for a friend. Ive rooted 3 other devices prior to this one without issue and constantly custom rom my own device (HTC Raider).
As of now, I CAN: Boot to Hboot (1.11.000), Flash Custom Recovery (Have tried TWRP and CWM, can enter successfully cant do much else), flash things via fastboot.
I CANNOT boot to OS. Its apparently gone. so as such, i have no access to the SD-ext. I CAN mount USB in TWRP but while it shows up in windows as a storage device, I CANT see it on the phone, so i cant flash it. I CANNOT mount in CWM.
I have attempted to RUU via fastboot. I have gotten errors for signature, size and model. Even the stock, non-root one (1.94) stated that the size is incorrect. Im also seeing alot of Errors regarding android-info.txt.
I really desperately need to get this running. Which ever rom. i dont care. If i can get stock, fine, if not Custom rom/kernel.
My biggest issue is not having access to the sd-ext and this phone, for some stupid reason, does not have a microSD slot, which would have made this whole issue alot easier.
I dont know if im missing a file or a step. Im really not sure where to go next.
If you have files that will work and can tell me how to do it, I will forever be in your debt.
It seems to me that i SHOULD be able to run fastboot update xxx.zip and just have it fix it but thats when im getting the android-info.txt errors.
If i could manually flash the 3 files through fastboot (system and boot more than recovery), i would think it would work but nooooooo.
Is there any way any of you know how to get me to atleast being able to see my sd-ext on both windows and TWRP so i can flash it that way? ANYTHING?

So, Got it up and running with Team Nocturnals Rom.
What I had to do was wipe SD and caches in TWRP. Flashed CWM from fastboot. Wiped SD and cache AGAIN. Flashed back to TWRP. Wiped SD and Cache. Rebooted to fastboot. Flashed the boot.IMG. Rebooted to recovery. Mounted USB. Windows detected it. Formatted to fat32. Copied the .zip to SD and installed. Problem solved.
Stock 2.20 Rom that's around didn't work, deodexed rooted stock didnts, nor did Android Revolution HD.
I still thank all of you, because even though I got this working myself, it was bits and pieces of every other thread that got me to that point. Thank you all.
Sent from my HTC Velocity 4G X710s using xda app-developers app

Kesler84 said:
So, Got it up and running with Team Nocturnals Rom.
What I had to do was wipe SD and caches in TWRP. Flashed CWM from fastboot. Wiped SD and cache AGAIN. Flashed back to TWRP. Wiped SD and Cache. Rebooted to fastboot. Flashed the boot.IMG. Rebooted to recovery. Mounted USB. Windows detected it. Formatted to fat32. Copied the .zip to SD and installed. Problem solved.
Stock 2.20 Rom that's around didn't work, deodexed rooted stock didnts, nor did Android Revolution HD.
I still thank all of you, because even though I got this working myself, it was bits and pieces of every other thread that got me to that point. Thank you all.
Sent from my HTC Velocity 4G X710s using xda app-developers app
Click to expand...
Click to collapse
Ummmm android revolution is for the international one x.... Maybe that's how u f'd it up in the first place? Idk just be careful the threads are kinda similar ...

No, I didn't even touch Revolution until it was already not working. I was originally just rooting the stock. It wasn't until it softbricked that I attempted any customs.
Sent from my HTC Velocity 4G X710s using xda app-developers app

[Q] Semi-bricked tf300t

I'll preface this by saying the following:
I know there are a lot of brick guides out there, and most are relatively easy to get out of. I've worked myself into a bit of a pickle, though.
It started when I noticed that there was an update available through the CM updater. I figured, what the hell, I'm running a nightly and this is likely to be a stable release, so I went ahead and downloaded it. I got home and checked the get.cm page, and sure enough, a new, stable build had recently been released. Being the diligent soul that I am, I made sure to do a full backup before I installed the .zip. Everything worked out just fine, the backup went swell, the update finished without problems, and then I rebooted my device.
All I see is the Asus splash screen. It just stays there. So I think, no big deal, it just didn't work out like I wanted, I'll go format my data (which I didn't do the first time around, in hopes that everything would carry over) and install again. The same thing happens. I haven't started panicking yet, since I still have 3 backups (1 older Jellybean, and one much older ICS). None of them work. I wipe everything that I can think might help. Data, system, cache, dalvik, you name it. Nothing was working, and I was starting to freak out. Then I decided to try to get some action through fastboot, hoping that I could push a .zip that wasn't the CM10 update that had started everything. In my search for a push command, I thought it would be a good idea to try a wipe from fastboot. This wiped everything. Not only the system, boot, etc. partitions, but also my personal partition that had all of my data. This in itself isn't a big problem, but it also left the partitions unformatted. Now I have a device that is devoid of data and can't do anything but get into CWM and fastboot.
What the hell can I do? Am I doomed? Is there no way to get out of the hole I've dug myself into?
tl;dr failed update, things got really real, really fast.
Specs before the initial update
ROM: CM10 nightly, Jellybean 4.1.x
CWM: 5.5.0.4
Kernel Version (?): 9.4.3.30-20120604 (I'm not sure with this, it says something about "android carhu-user" before it)

same thing just happened to me. Im going to download another version of CM and try that. It might just be that.

DerangedLoofah said:
same thing just happened to me. Im going to download another version of CM and try that. It might just be that.
Click to expand...
Click to collapse
That's the thing, though, I have no idea how I'm supposed to get it to my device now...

http://forum.xda-developers.com/showthread.php?t=1989076
Have you tried this? I was just thinking about it because I can't reflash my recovery and thought this may be the way to start over.

OK I downloaded the us jb update and extracted to my external SD card and flashed it in recovery after wipes. Everything is good now.
Edit: flash recovery in fast boot.
Sent from my SCH-I535 using Tapatalk 2

Glad you got it!

nitsuj79 said:
Glad you got it!
Click to expand...
Click to collapse
DerangedLoofah managed to get it, but I still haven't had any luck.

DerangedLoofah said:
OK I downloaded the us jb update and extracted to my external SD card and flashed it in recovery after wipes. Everything is good now.
Edit: flash recovery in fast boot.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
How did you flash it in fastboot? I can't figure out how to get to something that's on the external SD card. What were the exact commands you used?

1. Download any software from this topic http://forum.xda-developers.com/show....php?t=1697227
2. Unpack it one so you have a zip without UpdateLauncher
3. Rename the zip to EP201_768_SDUPDATE.zip
4. Put on a sdcard into the root (the sdcard should be clean, no other files)
5. Boot you tablet to RCK (Volume down + power, then volume up)
6. Let the magic begin!!! Take some minutes.
Attention! JB user pleas choose a JB ROM, don't flash ICS ROM on JB bootloader.
You tried this method with no love? I was able to flash stock pretty easily doing this.

nitsuj79 said:
1. Download any software from this topic http://forum.xda-developers.com/show....php?t=1697227
2. Unpack it one so you have a zip without UpdateLauncher
3. Rename the zip to EP201_768_SDUPDATE.zip
4. Put on a sdcard into the root (the sdcard should be clean, no other files)
5. Boot you tablet to RCK (Volume down + power, then volume up)
6. Let the magic begin!!! Take some minutes.
Attention! JB user pleas choose a JB ROM, don't flash ICS ROM on JB bootloader.
You tried this method with no love? I was able to flash stock pretty easily doing this.
Click to expand...
Click to collapse
Does that work with CWM? I don't have the stock bootloader on it.

This works only if you didn't flash custom recovery, it is the best method for locked devices. But you can still flash any stock ROM from CWM (but I suggest to use TWRP, you can install it from external sd). And you can push the ROM to internal memory via adb. I think you can install stock ROM via fastboot too, I am not sure, but the command fastboot update should help.

I managed to get it working again. If you can get to fastboot, push a bootloader that supports an external SD cards (like TWRP) and then from that install one of the official ASUS firmwares. From there, you have to root again, but it's better than having a device that won't boot at all.

Help! I did something to my phone!

Hello there, I have a htc one xl on At&t rooted... it has the hboot 1.14. Everything was fine until yesterday when I tried to flash AOKP. I used flash image gui to flash the boot.img then rebooted to TWRP and wiped rom, wiped everything, then installed the .zip for the boot.img I flashed... It would say android is upgrading and cycled through all the apps but stopped at starting apps... wouldnt go past it for 6 hours. I rebooted and tried to reflash the boot.img, but computer didnt recognize phone, and TWRP showed there was nothing on the sdcard

Juts mount your sd in recovery and drag a Rom over from your computer

J3susisl0rd7 said:
Hello there, I have a htc one xl on At&t rooted... it has the hboot 1.14. Everything was fine until yesterday when I tried to flash AOKP. I used flash image gui to flash the boot.img then rebooted to TWRP and wiped rom, wiped everything, then installed the .zip for the boot.img I flashed... It would say android is upgrading and cycled through all the apps but stopped at starting apps... wouldnt go past it for 6 hours. I rebooted and tried to reflash the boot.img, but computer didnt recognize phone, and TWRP showed there was nothing on the sdcard
Click to expand...
Click to collapse
Sounds like the initial problem was just a bad flash/download. It happens.
Try unplugging your phone, shutting down and restarting into bootloader, then hooking it up.

You flashed an incompatible kernel it sounds like.
Make sure you try flashing the kernel within the ROM
Sent from my One X using Tapatalk 2

Hello everyone! Thanks for the replies. Sorry for the rushed post earlier, was on the way out the door after trying for a while to figure something out. I'd love to send a rom to it, but TWRP shows that I have 0 mb available of storage, and the computer says I must format it to access files or something. I may have forgotten to mention- I think i flashed rohan kernel b6 improperly... used flash image gui then went to recovery and clicked it and hit install ... it hung at installing for a while, and upon reboot the starting apps problem happened, followed by no rom being on there, only being able to access TWRP, and ... well, above things. If I formatted it would I be able to put twrp and everything back on it necessary to make the thing function properly? Orr.... Thanks for any help!
God bless!
P.S. Forgot to add- Not sure why I thought I needed to try to "install" rohan kernel later on in TWRP lol
P.S.S I tried to mount sd card in twrp, nomatter how many times i try to select it it wont work

Yeah just format it and then it'll show up as a drive for you then you can send a rom to it.
Sent from my HTC One XL using xda premium

thejosh86 said:
Yeah just format it and then it'll show up as a drive for you then you can send a rom to it.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
I'm sorry- I really don't understand what I'm going to lose if I format, like... apparently all my data is somewhere in the air now lol, but will I not lose any important things the phone needs to run? TWRP? Will the bootloader still be unlocked?
And, if above "issues" aren't "issues", then will the following steps be correct?
1. Send ROM to phone
2. Throw fastboot.exe and adb thing into a folder with the ROM/ boot.img
3. CMD prompt to flash
4. Magic
?
Thanks so much and sorry to be a pain here if this isn't that big of an issue! I was afraid I bricked the thing, but I was holding on to hope that I didn't since it seemed like a good thing that it would still boot to TWRP.
Also- not sure if this is an issue, I tried to hit adb sideload in TWRP just messing around with options, and it said it couldn't mount the SD card.... so.... yeah, is that an issue?

Whatever data you had on the sd card is gone anyway. You need to reformat to use it.
Formatting the sd card won't affect your /system files or recovery, which are stored on a different area, or cause you to lose root.

You guys are awesome. Thanks so much!
And, as you get a lot: Sorry... for being a noob. lol

[Q] Need help with getting back to stock, made multiple errors

So I think I made some mistakes upgrading to Cyanogenmod 10.1 -- here's what I did:
I used Hasoon2000's HTC One X All-in-One Kit to unlock my bootloader via the xfactor exploit and the HTCDev method. Then I flashed a custom kernel and cyanogenmod 10.1. It's very buggy, reboots constantly, disconnects from AT&T's data network on a whim, etc. Someone suggested that the problem was that I didn't upgrade my hboot first. I'm currently on hboot 1.14, and after running the all-in-one kit, I now have supercid.
After that, I got the bright idea that maybe I could upgrade to a jelly bean firmware (hboot) after the fact. I followed a guide for upgrading hboot at guidingtech.com. Of course, since my cid is now 11111111, I couldn't verify that my cid was correct, but being a noob, I decided to try anyway. I got through to this command: fastboot flash zip firmware.zip, but that failed. I couldn't flash the new firmware. So I though, "Oh well, I'll just keep using my phone as is until I can figure out how to get back to stock." But then I got stuck in a boot loop where all I could do was get back to the bootloader. I used hasoon's kit to force my phone into recovery to try wiping dalvik/cache. I managed after some finagling to boot back into my broken cyanogen 10.1, but now that phone can't access internal storage. So I can't easily just flash a new rom. I suspect the internal storage is corrupted?
I know many of these questions have been answered piece-by-piece, but I don't know how all of these actions combine. Is it easy to get back to stock now? Can I use an RUU to do so? Can I use an RUU with supercid? Any help would be appreciated.

ddevil5 said:
I followed a guide for upgrading hboot at guidingtech.com.
Click to expand...
Click to collapse
Never even heard of that website. Where did you dig that up? I'd caution against using guides and mods from random websites. At a minimum, other websites are often poorly organized, and might get you installing a mod for the quad core One X, which may lead to a brick. Lots of websites just steal content from XDA, anyway. All you need is here, so may as well get it straight from the source.
I'll agree that you probably did a lot of needless, and possibly dangerous steps. I don't recommend trying anything else, unless an experienced user here tells you to do it. Playing with a smartphone is not a trial-and-error activity for n00bs.
Sounds like you corrupted your SD card by trying to do a factory reset in hboot. You should be able to connect the phone to a PC, go to Device Manager, and it should give you the option to format the SD. Format it FAT32, and that particular issue should be resolved.
Can you get into recovery?
What hboot version does it say you are on now?
What kernel did you try to flash? I would have just tried to revert to the stock CM10 before you did all this other stuff. I don't think what you were experiencing originally was related to hboot version.

redpoint73 said:
Never even heard of that website. Where did you dig that up? I'd caution against using guides and mods from random websites. At a minimum, other websites are often poorly organized, and might get you installing a mod for the quad core One X, which may lead to a brick. Lots of websites just steal content from XDA, anyway. All you need is here, so may as well get it straight from the source.
I'll agree that you probably did a lot of needless, and possibly dangerous steps. I don't recommend trying anything else, unless an experienced user here tells you to do it. Playing with a smartphone is not a trial-and-error activity for n00bs.
Sounds like you corrupted your SD card by trying to do a factory reset in hboot. You should be able to connect the phone to a PC, go to Device Manager, and it should give you the option to format the SD. Format it FAT32, and that particular issue should be resolved.
Can you get into recovery?
What hboot version does it say you are on now?
What kernel did you try to flash? I would have just tried to revert to the stock CM10 before you did all this other stuff. I don't think what you were experiencing originally was related to hboot version.
Click to expand...
Click to collapse
I do get prompted to format my drive whenever I plug in my phone. If I format the internal storage will that erase my rom?
I do admit, I'm a total noob, and I should have done a lot more research before messing around with the guts of my phone. I'm on hboot 1.14. I honestly don't know which kernel I tried to flash. My friend suggested to me what I used. It was from an official cyanogenmod guide for flashing 10.1 to my AT&T One X.
Now that I understand how woefully unprepared I was, I'd like to get back to how my phone came out of the box, if that's possible.

ddevil5 said:
I do get prompted to format my drive whenever I plug in my phone. If I format the internal storage will that erase my rom?
Click to expand...
Click to collapse
No, it just formats the SD partition (think of it as a virtual SD card). Anything that was on it will be gone, but its corrupted anyway, so its already gone. The partition with the ROM will not be formatted, nor will hboot, recovery, or radio partition.
Can you get into recovery? If so, after the SD is formatted, mount the SD memory USB, move the CM 10.1 zip file to the SD. Reflash in TWRP, reboot and see what happens. Don't flash a custom kernel, just use the stock CM10.1 kernel (flashes automatically when you flash the ROM).

redpoint73 said:
No, it just formats the SD partition (think of it as a virtual SD card). Anything that was on it will be gone, but its corrupted anyway, so its already gone. The partition with the ROM will not be formatted, nor will hboot, recovery, or radio partition.
Can you get into recovery? If so, after the SD is formatted, mount the SD memory USB, move the CM 10.1 zip file to the SD. Reflash in TWRP, reboot and see what happens. Don't flash a custom kernel, just use the stock CM10.1 kernel (flashes automatically when you flash the ROM).
Click to expand...
Click to collapse
So, what about hboot? Does that need to be upgraded from 1.14 to be compatible with jelly bean?

ddevil5 said:
So, what about hboot? Does that need to be upgraded from 1.14 to be compatible with jelly bean?
Click to expand...
Click to collapse
Absolutely not. Heck, I'm on hboot 1.09, and running Jellybean without a glitch.
That's why I mentioned, I doubt hboot has anything to do with it, and leave it alone.

redpoint73 said:
No, it just formats the SD partition (think of it as a virtual SD card). Anything that was on it will be gone, but its corrupted anyway, so its already gone. The partition with the ROM will not be formatted, nor will hboot, recovery, or radio partition.
Can you get into recovery? If so, after the SD is formatted, mount the SD memory USB, move the CM 10.1 zip file to the SD. Reflash in TWRP, reboot and see what happens. Don't flash a custom kernel, just use the stock CM10.1 kernel (flashes automatically when you flash the ROM).
Click to expand...
Click to collapse
Argh, the problems keep mounting. Whenever I plug it in, I can't even access usb storage. I hit "turn on usb storage" and I get a spinning circle. The only way I can mount anything is if I go into TWRP and use the mount menu. And it give me four tick boxes: 1. mount system 2. mount data 3. mount cache and 4. mount sd card.
Unfortunately the only check box I can't check is the sd card. I can mount the other three. And then I get prompted in Windows to format. But in that case, I obviously will format everything I don't want to format. So I feel kinda stuck.
What about using an RUU? Can that help me get back to stock? My ultimate goal is just to go back to stock. Maybe I'll ROM again in the future but right now, I just want my phone back in a fully functional package!

Any other help out there? I can't get anywhere with this problem.

ddevil5 said:
Argh, the problems keep mounting. Whenever I plug it in, I can't even access usb storage. I hit "turn on usb storage" and I get a spinning circle. The only way I can mount anything is if I go into TWRP and use the mount menu. And it give me four tick boxes: 1. mount system 2. mount data 3. mount cache and 4. mount sd card.
Unfortunately the only check box I can't check is the sd card. I can mount the other three. And then I get prompted in Windows to format. But in that case, I obviously will format everything I don't want to format. So I feel kinda stuck.
Click to expand...
Click to collapse
Did you try to format the SD like I previously mentioned? It won't mount in TWRP (or with the phone fully booted) if its still corrupted. It sounds like you just need to format it. Your problems are mounting, its just the same problem as before, that you haven't fixed yet.
---------- Post added at 09:25 AM ---------- Previous post was at 09:21 AM ----------
ddevil5 said:
What about using an RUU? Can that help me get back to stock? My ultimate goal is just to go back to stock. Maybe I'll ROM again in the future but right now, I just want my phone back in a fully functional package!
Click to expand...
Click to collapse
I think using the RUU to go back stock is just a lot of extra unnecessary work. You wanted to be rooted and be able to flash custom ROMs to begin with, so let's keep it that way.
I don't think it would be that hard to get up and running again (without running the RUU). You just need to do it right.

redpoint73 said:
Did you try to format the SD like I previously mentioned? It won't mount in TWRP (or with the phone fully booted) if its still corrupted. It sounds like you just need to format it. Your problems are mounting, its just the same problem as before, that you haven't fixed yet.
---------- Post added at 09:25 AM ---------- Previous post was at 09:21 AM ----------
I think using the RUU to go back stock is just a lot of extra unnecessary work. You wanted to be rooted and be able to flash custom ROMs to begin with, so let's keep it that way.
I don't think it would be that hard to get up and running again (without running the RUU). You just need to do it right.
Click to expand...
Click to collapse
But how do I format it when my computer won't recognize it?

ddevil5 said:
But how do I format it when my computer won't recognize it?
Click to expand...
Click to collapse
It won't read it as an Android device, or it won't read it at all.
Does it still come up as a bulk storage device or something like that?

bump. Any options for me?

Do you know what adb and fastboot is. It sounds like the prob you having is actually simple to fix. You need to make sure twrp is on your device for recovery for starters if not than flash it through fastboot. Make sure you have HTC drivers ok. You can download HTC sync then uninstall it and it will leave drivers on pc or go to HTC website and get them. 1hr of googling and appling what you learn should get you back on track, if not you need to find a mentor to hold your hand and show you, it may seem overwelming but you will get it.
Sent from my HTC One X using xda premium

I have the same issue right now. i can not mount my sd card at all. im running the cm 10.1. i had to ADB sideload my rom to bring my phone back and now i cant load my gapps. any help would be great! my phone works but no apps etc.

artsonex said:
i have the same issue right now. I can not mount my sd card at all. Im running the cm 10.1. I had to adb sideload my rom to bring my phone back and now i cant load my gapps. Any help would be great! My phone works but no apps etc.
Click to expand...
Click to collapse
fixed my own issue! Just follow the steps above and you should be good!!
Nothing big

[Q] TWRP no/OS on Verizon Galaxy S3

I am a "NOOB" and I completely apologize if this has been discussed previously. My daughter has a Galaxy S3 that someone installed TWRP on it. She tried to update the phone because it gave her the status to do so. Somehow she has wiped everything except TWRP and I have no idea what to do in order to get a OS back on the device. Can someone please help and I really need the information explained to me in the simplest terms. Thanks

In twrp, if you click "restore" does it list anything on either internal or external memory? If so, just restore it and don't update.
Sent from my Slim GS3

dpeeps74 said:
In twrp, if you click "restore" does it list anything on either internal or external memory? If so, just restore it and don't update.
Sent from my Slim GS3
Click to expand...
Click to collapse
It doesn't show anything.

Did you try reboot system?

Odin flash VRBMB1. You'll need a access to Windows for this to work. This will return you to out of the box stock rom.

Do what Slimsnoop suggested. Its for the best
Sent from my SCH-I535 using Tapatalk 4

lol
It just means the SYSTEM was wiped. Just download a small ROM like CM10.1 and flash it. Reboot.
Have had this happen a lot. For a fast fix You will have to load ROM on the external SD card, then when you flash it check the directory where the ROM is stored on the external SD and flash it. Reboot. No need to flash gapps if you don't plan on keeping that ROM.
If you plan on keeping it just download the ROM you want and flash.

SlimSnoopOS said:
Odin flash VRBMB1. You'll need a access to Windows for this to work. This will return you to out of the box stock rom.
Click to expand...
Click to collapse
Ok so this just happened to me and I turned to this awesome site for help. I had switched from CWM to TWRP and installed the img file, when it rebooted into recovery it told me there was no OS installed. I flashed the above referenced file with Odin... when it rebooted though, I had everything I thought I had lost. No stock rom, it was still running cm10 with all my apps and themes, everything.
I'm confused. I'm not a total newbie to this kind of stuff, but I'm by far no expert. I'm just curious if TWRP didn't recogonize anything so it assumed there was no OS installed?

Easy way around this. Happens to me all the time
what you are gonna have to do it download a compatible rom from your computer to a micro sd card. Put the micro sd card in your phone. Go into twrp and select the rom and flash from external sd.