Database Info

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

HELP, did I brick my xoom???

/I had the touch recovery on there and cyanogenmod 10 I think.. worked fine for a year.
Then I wanted to format and start over, so I did a wipe of everything and now anything I try to flash gives me an error, I can still get into the touch recovery but every rom I've tried won't install, keeps saying error.
I'd like to just throw a rom on it and be done, or go back to stock.
Also, when I try to reboot from the touch flash program it tells me its not rooted and would I like to root it now, swipe to confirm or just exit to deny.

Try to rsdlite/sbf to 100% stock
Sent from my dlx using Tapatalk 4

do what? what does that even mean?
thanks

I hope you have your ROM on your sdcard, if so then "Format Data". You'll lose everything on your internal memory but it should solve your ROM errors, considering your ROM isn't the issue to begin with. Especially if you are trying to go from 4.3 back to 4.2. If it's on your internal storage, then you'll need to do alot more searching on how to use adb and fastboot or hope someone is willing to find it for you and post a link.
You might also what to mention what ROMS / version you are trying to install and what version Xoom you have. If you are trying to install the latest EOS Roms they don't work.
And just as every post mentions before flashing something new... do a Nand backup (backup in recovery).
As for your root issues, it's known for 4.3 and has been mentioned many times on these forums. Do some searches about it here or simply go back to 4.2.
The Xoom is pretty hard to brick.

Domunus said:
I hope you have your ROM on your sdcard, if so then "Format Data". You'll lose everything on your internal memory but it should solve your ROM errors, considering your ROM isn't the issue to begin with. Especially if you are trying to go from 4.3 back to 4.2. If it's on your internal storage, then you'll need to do alot more searching on how to use adb and fastboot or hope someone is willing to find it for you and post a link.
You might also what to mention what ROMS / version you are trying to install and what version Xoom you have. If you are trying to install the latest EOS Roms they don't work.
And just as every post mentions before flashing something new... do a Nand backup (backup in recovery).
As for your root issues, it's known for 4.3 and has been mentioned many times on these forums. Do some searches about it here or simply go back to 4.2.
The Xoom is pretty hard to brick.
Click to expand...
Click to collapse
I have nothing on my SD card or Internal Memory, its completely empty!
Every rom I try to flash gives me an error, I tried a few now and it won't work.
I'm at a loss of what to do

I have Twrp recovery ver 2.5.0.0
I tried to flash later version recoveries but I just get an error

what are trying to flash recovery with? should be using fastboot. with an unlocked bootloader, you, quite literally, CANNOT brick the device
also, ignore the idiot who talked about rsd. that would be beyond stupid.
because you can still get into recovery, you can use adb to sideload the ROM.
adb sideload /path/to/ROM.zip
Sent from my Nexus 5

notbrodie said:
what are trying to flash recovery with? should be using fastboot. with an unlocked bootloader, you, quite literally, CANNOT brick the device
also, ignore the idiot who talked about rsd. that would be beyond stupid.
because you can still get into recovery, you can use adb to sideload the ROM.
adb sideload /path/to/ROM.zip
Sent from my Nexus 5
Click to expand...
Click to collapse
Yes I can get into recovery. Where can I read up on how to use adb again?
I'd love to try that.
THANKS

just download the android SDK and pull adb and fastboot executables ( should be in android-tools). as I use Ubuntu, I don't use the SDK any more.
once you have the adb file, if you place it in the same directory as the ROM, you would just need to 1) open command line 2) CD to directory where the files are 3) in Xoom recovery, go to advanced > sideload 4) on computer, type adb sideload ROM.zip
this is will flash the ROM over. do the same thing for gapps. then reboot Xoom
Sent from my Nexus 5

Yea, problem is, what you're saying, makes no sense to me.
I downloaded android SDK installed the 500 meg program.. Now what
also, it seems I cannot get my computer to recognize my xoom.. I downloaded the drivers and all,comes up unknown usb device.
This just really BLOWS!

I went ahead and did some quick searches for you in google. Hope this helps you, if not, do more searches for ADB Sideload xoom rom. If you don't understand something during one of the steps, google it. BTW, you need to update your TWRP if you plan to mess with 4.3.
If you need a visual guide, go to youtube and type in adb sideload. Good luck.
This is a bit old, but it's simplified and may help you setup ADB.
http://www.xoomforums.com/forum/motorola-xoom-hacking-guides/1838-setting-up-adb-windows-7-64-bit-other-windows-platforms.html
This guide may also help you, it's for HTC but obviously change anything HTC related to Xoom. It shows you how to sideload with every detail.
http://forum.xda-developers.com/showthread.php?t=2317985

ok.. does it matter that no matter what I try no computer can recognize my xoom.. Always says unknown device.. I downloaded moto's drivers and everything.
While in recovery and going to mount it still never recognizes my xoom..
Tried in 2 computers, same results

Soft Brick - Please help

Hi All,
I came from flashing Motorola phones and bought a HTC One XL not too long ago - so the HTC flashing is fairly new to me. I have an ATT phone, on stock 4.0.0, Tampered, Unlocked, EVITA PVT SHIP S-ON, installed TWRP v2.5.0.0. Months later (now) I went to actually install a custom ROM and missed something, now my phone has no OS and no files on it. Long story short, I've been reading the threads for hours and my brain if fried, actually just got back from vacation to find my refer went and flooded my house so I'm disheveled right now and brain can't function I shouldn't have tried to flash right now but the phone was acting up (dropping every call, wouldn't pick up calls, etc) and with insurance claims anc contractors calling needed the phone to work so figured I'd flash...bad mistake!
Anyway - I can get to TWRP but when I try to mount the SD card the PC says I need to format and will not allow me to copy any files to phone-I did not format. I am trying to install ViperXL4.2.0. How do I get the file to the phone? Once I get the file to the phone, do I need to do anything else or can I just install using TRWP (do I have to relock or do any other steps?). I know I'm asking a lot but can someone please give me a few pointers/step by step on what to do? Thank you!
Update - I've tried to adb sideload the ROM and when I adb sideload in TRWP I get a "failed" message. Also, when adb command runs I get a "adb server is out of date" and kills program.

The first thing you need to do is flash a different recovery, TWRP 2.5 is full of bugs and has issues with wiping and flashing. Did you perform a factory reset from the bootloader? That's probably what's caused your sd card to become corrupt. Flash TWRP 2.6 and use the wipe menu to wipe the sd card, then you should be able to mount it to your PC and copy the ROM across (you may still need to use Windows to format it first).
The rest of your problems can probably be answered by reading the Evita FAQ thread and the How-To Guide For Beginners thread, both links are in my signature.
PS. We have a Q&A Section for questions [emoji12]
Sent from my Evita

timmaaa said:
The first thing you need to do is flash a different recovery, TWRP 2.5 is full of bugs and has issues with wiping and flashing. Did you perform a factory reset from the bootloader? That's probably what's caused your sd card to become corrupt. Flash TWRP 2.6 and use the wipe menu to wipe the sd card, then you should be able to mount it to your PC and copy the ROM across (you may still need to use Windows to format it first).
The rest of your problems can probably be answered by reading the Evita FAQ thread and the How-To Guide For Beginners thread, both links are in my signature.
PS. We have a Q&A Section for questions [emoji12]
Sent from my Evita
Click to expand...
Click to collapse
Appreciate your help - I'm up and running now.

Glad to help.
Sent from my Evita

Process system isn't responding.

So the other day I allowed my phone to shut-off due to low battery. I plugged it in to charge, when I turned it on it booted up but when the OS finishes loading I get the message "Process system isn't responding. Do you want to close it?"
So I had this problem once before when I went to upgrade firmware. http://forum.xda-developers.com/verizon-htc-one-m8/help/verizon-m8-bricked-updating-to-4-4-3-t2900703
But I have tried what I did before with no luck. I have tried 443 and 444. I have tried everything I can think of. I have tried the stock and custom roms. Factory resets, wipe all partitions excluding my external sd card. tried the fix and format using twrp.
Any tips on where to go from here?

If you've indeed tried everything but formatting the sdcard, try removing the sdcard and then boot the phone. Perhaps there's something on it that's causing problems. Between your factory resets, RUUs, wipes and all, the sdcard seems to be the one common denominator left over after trying each of those things. Just a thought.

robocuff said:
If you've indeed tried everything but formatting the sdcard, try removing the sdcard and then boot the phone. Perhaps there's something on it that's causing problems. Between your factory resets, RUUs, wipes and all, the sdcard seems to be the one common denominator left over after trying each of those things. Just a thought.
Click to expand...
Click to collapse
Probably should have mentioned that the only time I had the SD card in was when I tried having hboot install the 0P6BIMG.zip file.

dab1414 said:
Probably should have mentioned that the only time I had the SD card in was when I tried having hboot install the 0P6BIMG.zip file.
Click to expand...
Click to collapse
Maybe that's the problem. There have been numerous problems flashing the 4.4.4 firmware with the sd card method.
I think you should either run dottat's RUU.exe from here (option 2): http://forum.xda-developers.com/ver...ent/ruu-m8vzw-4-4-4-s-off-onlynewest-t2914914
Or try to re-flash your firmware following the instructions here: http://forum.xda-developers.com/showthread.php?t=2723159
Make sure you fastboot flash the firmware TWICE.

berndblb said:
Maybe that's the problem. There have been numerous problems flashing the 4.4.4 firmware with the sd card method.
I think you should either run dottat's RUU.exe from here (option 2): http://forum.xda-developers.com/ver...ent/ruu-m8vzw-4-4-4-s-off-onlynewest-t2914914
Or try to re-flash your firmware following the instructions here: http://forum.xda-developers.com/showthread.php?t=2723159
Make sure you fastboot flash the firmware TWICE.
Click to expand...
Click to collapse
Let me pile on and suggest you guys start using this version of fastboot/adb for HTC devices. If a second flash is required it will automatically do it for you. No silly games. This is htc's version and has more oem commands for HTC devices.
https://www.androidfilehost.com/?fid=95784891001612150

berndblb said:
Maybe that's the problem. There have been numerous problems flashing the 4.4.4 firmware with the sd card method.
I think you should either run dottat's RUU.exe from here (option 2): http://forum.xda-developers.com/ver...ent/ruu-m8vzw-4-4-4-s-off-onlynewest-t2914914
Or try to re-flash your firmware following the instructions here: http://forum.xda-developers.com/showthread.php?t=2723159
Make sure you fastboot flash the firmware TWICE.
Click to expand...
Click to collapse
I have tried both of these links. But funny thing is I haven't touched the phone in 3 days since I have been out of town. Now today I power it up walk away and when I come back the original problem is no longer there. So I updated the firmware using the RUU.EXE then TWRP then Custom ROM and everything is good. I have no clue what happened or why it suddenly started working when I did nothing to it. Thanks for all the help..