Database Info

[Q] I think I have done something wrong.

Salutations,
I recently installed a ICS ROM from another site, was meant to be in beta but it crashed and wouldn't reboot unless I removed the battery everytime the screen went off. I thought I would wipe everything and just go back to the stock ROM for a while until all of the ICS builds have matured.
Sadly this wasn't the case, after wiping everything ( I wanted to clean the SD card etc as well ) the phone doesn't boot, remains stuck on HTC logo if it wants to go that far. The LED is flashing orange and I cannot get into HBOOT.
Any help would be greatly appreciated!

The flashing LED light means u got low battery, so I would suggest you charging it.
to get into recovery remove the battery, and then try again. When in recovery wipe cache and dalvik cache and try to reboot.
The screen-off problem I have no idea how to fix, try re-downloading, maybe u got a broken zip. Or just try another ROM.
Sent from my MIUI.us Sensation 4G using xda premium

Make sure you do "supercid" then go ahead and download and run the correct ruu and drivers for your version of sensation problem solved

mendes52309 said:
Make sure you do "supercid" then go ahead and download and run the correct ruu and drivers for your version of sensation problem solved
Click to expand...
Click to collapse
Thanks for the responses, I think I must have wiped the boot partition and messed up the ruu. Problem solved when I downloaded a new ROM on my Mac and moved it onto the SD card and installed it. Got quite worried that I might have soft bricked the device!

Phone keeps rebooting, even in recovery?

Hi. I was toolin' along doing real well on CleanRom 4.5 for several days. Starting yesterday, the phone would randomly reboot itself to the HTC screen. I figured I had a bad app or something. Today, I went to open an app (Draw Something) and the phone froze for a bit. Then it rebooted, and now I cant get it booted back up. I usually never make it past the HTC screen. Got into recovery once but it rebooted in the middle of clearing the cache.
Any advice?

Welp, just made it through cache and dalvik and rebooted in the middle of factory reset. I wonder if I'm doing more harm than good.

Got it recovered and wiped fully, but it still keeps rebooting. Starting to feel like a hardware issue.

hcricket said:
Got it recovered and wiped fully, but it still keeps rebooting. Starting to feel like a hardware issue.
Click to expand...
Click to collapse
Wipe system than factory reset ....than flash a new Rom if u can without it rebooting :crying:

omario8484 said:
Wipe system than factory reset ....than flash a new Rom if u can without it rebooting :crying:
Click to expand...
Click to collapse
Thank you for the reply. I have the battery recharging in recovery right now (which I am thrilled it is doing, lol). What does it do when you wipe /system? Clear off the OS? Would you move a new ROM over to SD card first?

hcricket said:
Thank you for the reply. I have the battery recharging in recovery right now (which I am thrilled it is doing, lol). What does it do when you wipe /system? Clear off the OS? Would you move a new ROM over to SD card first?
Click to expand...
Click to collapse
So when u go into wipe menu in twrp it will show options : cache dalvic cache and external never press external unless u know what you're doing!
So do u have any Rom backups if so try restoring that and if not dl like clean Rom final version 5 and mount it sd in recovery and move that over and for the sake of itright now when your gunna install a new Rom in the wipe menu just choose factory reset ...your using twrp recovery right?

omario8484 said:
So when u go into wipe menu in twrp it will show options : cache dalvic cache and external never press external unless u know what you're doing!
So do u have any Rom backups if so try restoring that and if not dl like clean Rom final version 5 and mount it sd in recovery and move that over and for the sake of itright now when your gunna install a new Rom in the wipe menu just choose factory reset ...your using twrp recovery right?
Click to expand...
Click to collapse
Thank you. I wiped everything, including /system and put CleanROm final 5 on it. Everything looked beautiful but I got to the setup screens and rebooted. I'm back in recovery and charging now. Oddly, it has stopped rebooting from recovery. The only other thing I can think of is a bad sim card? Can that make a phone go crazy?

hcricket said:
Thank you. I wiped everything, including /system and put CleanROm final 5 on it. Everything looked beautiful but I got to the setup screens and rebooted. I'm back in recovery and charging now. Oddly, it has stopped rebooting from recovery. The only other thing I can think of is a bad sim card? Can that make a phone go crazy?
Click to expand...
Click to collapse
What's your battery at?

Removed the SIM card and it froze while booting, with lots of graphical tearing. *sigh*

hcricket said:
Removed the SIM card and it froze while booting, with lots of graphical tearing. *sigh*
Click to expand...
Click to collapse
Keep that simmy in there..now what's your battery ....when does it reboot ...when trying to get into aroma installer?
---------- Post added at 09:28 PM ---------- Previous post was at 09:25 PM ----------
Worst case scenario you can relock the bootloader and run an RUU. But I think u can get out of this without having to do that

I replaced the SIM. Battery at 90% now, was 44% when I started. Fortunately, it is charging from TWRP.
It reboots all over the place - from fastboot, from recovery, from the boot.img, from the lock screen. I made it all the way to Android setup at one point and it rebooted. It most often just gets to the HTC screen and hangs - it reboots the least from recovery, just once in a great while.

hcricket said:
I replaced the SIM. Battery at 90% now, was 44% when I started. Fortunately, it is charging from TWRP.
It reboots all over the place - from fastboot, from recovery, from the boot.img, from the lock screen. I made it all the way to Android setup at one point and it rebooted. It most often just gets to the HTC screen and hangs - it reboots the least from recovery, just once in a great while.
Click to expand...
Click to collapse
Dam so it's actually booting up and your getting to the rom... Umm what'd you do to your phone did u install something bad that's laying around on your sd or idk ! This is weird

omario8484 said:
Dam so it's actually booting up and your getting to the rom... Umm what'd you do to your phone did u install something bad that's laying around on your sd or idk ! This is weird
Click to expand...
Click to collapse
Oy. Add reboot during aroma installer to that list. I just tried to flash again but no go.

hcricket said:
Oy. Add reboot during aroma installer to that list. I just tried to flash again but no go.
Click to expand...
Click to collapse
Hold down your power button until your screen turns black and than see if it's still rebooting

Still no go. Thank you for your help - I've got it to 98% battery, powered it down, and I'm going to the bar, hah hah.

try flashing CM10 instead of a Sense rom. Aroma can cause freezes and reboots on its own. I would also be scared to run the RUU also since your phone freezes randomly. whats was your stock version?

It doesn't sound like you do, but if you installed a custom kernel that is overclocked then it could be that your device can't handle the higher CPU frequency. CleanROM 5 final I don't think has a custom kernel though. It could also be a bad CPU or memory hardware.

denversc said:
It doesn't sound like you do, but if you installed a custom kernel that is overclocked then it could be that your device can't handle the higher CPU frequency. CleanROM 5 final I don't think has a custom kernel though. It could also be a bad CPU or memory hardware.
Click to expand...
Click to collapse
I have had this happen. Viper has stock kernel listed in post 4 I would try flashing that.
Sent from my HTC One X using xda premium

kleeman7 said:
I have had this happen. Viper has stock kernel listed in post 4 I would try flashing that.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I told him to flash a rom that doesn't use aroma. He is getting freezes all the time. TWRP used to freeze up on me all the time after the 2.20 ruu until twrp 2.2.2.0 was released. Phone still has trouble getting into recovery from the bootloader though. He should install CM10 or codefirex without using a custom kernel. Maybe run "fastboot erase cache" in bootloader then wipe cache,dalvik,factory reset,system,external in recovery then flash CM10 or codefirex and gapps. keep it plain until you find issues you can attribute to the rom or to the phone. i have had very few issues with latest builds of jb aosp roms besides some battery stuff.

Well, although I had fully charged it and then powered down, now that I am ready to work on it this AM, it wont start at all. I'm thinking she's gone, captain.
Thank you everyone for the replies.

Cant Flash Any JB Rom????

Cant flash any JB rom always says " installation aborted " install ICS rom works fine though
HELP?

ryanraven said:
Cant flash any JB rom always says " installation aborted " install ICS rom works fine though
HELP?
Click to expand...
Click to collapse
That's weird.
Are you s-off or s-on?
Have you tried multiple ROMS? (Bruce'ss CM10, AOKP, that new minimalist CM10?)
If you've just tried one, start by redownloading the ROM. You will get the instalation aborted error if the ROM.zip is bad.
Also, did you do a full wipe (Not superwipe) from 4EXT? You will need to if going from ICS to JB. But that shouldn't prevent the ROM from installing (it just won't work properly).

//nvm

S-OFF, FUL wipe coming from ISC re-downloaded rom like 6 times and iv'e tried them all they wont install yet ICS rom's will

disable signature checking in recovery

Jonny said:
disable signature checking in recovery
Click to expand...
Click to collapse
Nope still nothing i personally think its the downloads but all ICS roms install fine

ryanraven said:
Nope still nothing i personally think its the downloads but all ICS roms install fine
Click to expand...
Click to collapse
I HATE problems like this because they make absolutely no sense. They are the ones that make you want to lay your phone down on the sidewalk and bash it repeatedly with a cinder block. So I understand your pain!
The worst part is that they almost always have the simpliest sollutions imaginable.
Are you using 4EXT or CWM?
Has a JB rom ever worked on your phone?
Can you install a fresh ICS ROM from scratch (meaning not just restore a nandroid) just to make sure recovery is working properly?
No matter if ICS installed fresh or not, you might try reflashing recovery. Maybe that's what's borked up somehow. Plus it' sone of those thigns that can't make it worse so why not try it?

Skipjacks said:
I HATE problems like this because they make absolutely no sense. They are the ones that make you want to lay your phone down on the sidewalk and bash it repeatedly with a cinder block. So I understand your pain!
The worst part is that they almost always have the simpliest sollutions imaginable.
Are you using 4EXT or CWM?
Has a JB rom ever worked on your phone?
Can you install a fresh ICS ROM from scratch (meaning not just restore a nandroid) just to make sure recovery is working properly?
No matter if ICS installed fresh or not, you might try reflashing recovery. Maybe that's what's borked up somehow. Plus it' sone of those thigns that can't make it worse so why not try it?
Click to expand...
Click to collapse
recovery is fine flashed basic CWM then 4EXT then TouchCWM all work fine installing ICS from scratch but these JB rom's done work and yes i installed Bruce's JB rom last week and worked fine i might just shoot my phone with my Silenced Air Pistol

ryanraven said:
Nope still nothing i personally think its the downloads but all ICS roms install fine
Click to expand...
Click to collapse
check the MD5 then...

Jonny said:
check the MD5 then...
Click to expand...
Click to collapse
MD5 is fine totally wiped phone and memory card and seems to install fine now -.- memory card fault ? but it installed ICS fine

ryanraven said:
MD5 is fine totally wiped phone and memory card and seems to install fine now -.- memory card fault ? but it installed ICS fine
Click to expand...
Click to collapse
That's a thing!
It's stupid, but it's a thing. Formatting the SD card has been known to solve a variety of ROM problems, app problems, and help with male pattern baldness. It's the goofiest thing, but it works randomly.
Glad you're fixed up.

Skipjacks said:
That's a thing!
It's stupid, but it's a thing. Formatting the SD card has been known to solve a variety of ROM problems, app problems, and help with male pattern baldness. It's the goofiest thing, but it works randomly.
Glad you're fixed up.
Click to expand...
Click to collapse
Thanks man kind of annoying wiping the card though i had to back up everything now send all my stuff back not bad though only 2GB of data i will also say i had a 16GB Class 6 the other week which im not joking burnt out randomly using HyperNonSense :/ hard doesn't get recognized by computer or phone anymore.

ryanraven said:
MD5 is fine totally wiped phone and memory card and seems to install fine now -.- memory card fault ? but it installed ICS fine
Click to expand...
Click to collapse
I've not seen this before but maybe tinky1/ganeshp/malybru or any other RC has so it might be worth asking on the #helpmenow IRC channel or posting here
Edit: @Skipjacks was faster...

well after reading all the above
i m confirmed its boot.img issue
try to flash insecured boot img n then flash JB
i had exactly the same issue
then i flashed insecured boot img
if u want i can attach that file in here
cant do it now coz m on my work desk sorry

Can't access media anymore

So I'm not sure when this happened, but I can't access the media on my internal storage anymore. For example, all the songs I've moved to my phone or my pictures I've taken. If I mount the phone in recovery, all the files are still there. When I just plug the phone into the USB (not in recovery), the internal storage comes up, the space is taken up, but the files aren't there. It's weird its like the phone can't access the internal storage when its not in recovery.
I'm S-OFF
Hboot 2.14
latest Viper XL
latest Elemental X kernal
I have been getting android.media.process errors since I upgraded to the latest Viper XL, tried all sorts of fixes like reflashing to no avail. But even while those were going on I could still access my media
Everything was working fine for a while, I'm honestly not sure when this happened. Any help would be appreciated.

Are they correctly named? Like .jpg for pics and such?
Sent from my HTC One XL using XDA Premium 4 mobile app

pandasa123 said:
Are they correctly named? Like .jpg for pics and such?
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I haven't touched the names of them. It looks like it. Basically the internal storage looks different if I just plug in my USB ->My Computer -> internal storage vs if I go to recovery -> mount -> My Computer -> explore the phone

When you upgraded did you do a clean flash?
Sent from my Evita

timmaaa said:
When you upgraded did you do a clean flash?
Sent from my Evita
Click to expand...
Click to collapse
During the Viper installation it gave me the option to do a wipe with installation, and I did that.

Ok, but did you wipe everything? The media force closes suggest a dirty flash possibly.
Sent from my Evita

timmaaa said:
Ok, but did you wipe everything? The media force closes suggest a dirty flash possibly.
Sent from my Evita
Click to expand...
Click to collapse
I remember initially when I was researching the problem, it sounded like a few people got it when they upgraded HBoot and the new ViperXL. It was suggested to just reflash Viper, when that didn't work I did do a factory reset. I'd prefer not to do a factory reset at this point but I will if I have to/when I have time.

Don't do a factory reset through bootloader, that'll corrupt your sd card. If you didn't do a factory reset in TWRP when you flashed the ROM I can't almost guarantee that's what is causing your problem. The correct protocol when flashing a new ROM is to wipe cache/dalvik cache/factory reset/system. Especially when coming from a different base / Android version, which you were.
Sent from my Evita

timmaaa said:
Don't do a factory reset through bootloader, that'll corrupt your sd card. If you didn't do a factory reset in TWRP when you flashed the ROM I can't almost guarantee that's what is causing your problem. The correct protocol when flashing a new ROM is to wipe cache/dalvik cache/factory reset/system. Especially when coming from a different base / Android version, which you were.
Sent from my Evita
Click to expand...
Click to collapse
Could it cause an issue with my media a few weeks down the line?

style2burn said:
Could it cause an issue with my media a few weeks down the line?
Click to expand...
Click to collapse
I'm not disagreeing that there was probably a problem with the flash, but anything less than a factor reset reflash would be nice.

I don't think you have another option. Why the hesitation? I always clean flash and it only takes me like fifteen minutes to set up my ROM.
Sent from my Evita

Currently on the road for a few weeks, can't risk bricking/running into battery issues on the road. Thanks for all the suggestions everyone I guess factor reset -> reflash is my only option

style2burn said:
During the Viper installation it gave me the option to do a wipe with installation, and I did that.
Click to expand...
Click to collapse
I always stay away from the wipe options in AROMA, as they have been known in the past to cause issues. Always flash from TWRP.

[Q] com.androidsystemui crash. Issue appears on clean install and different roms

I have had my phone a month and its been working flawlessly. I've installed a few custom roms on it and I'm comfortable with all the technical side from years of doing this.
What happened is my phone had a random shutdown and on reboot there was a com.androidsystemui error. No problem I thought, so I wiped the phone and restored a backup of the same rom (latest Heisenberg which has been very stable for me) same issue. OK maybe its rom related. So I did a clean install of Slimkat which I have found v stable. Instant reboot on setup. After trying this a few times I took the nuclear option and wiped by entire phone including storage and went through all this again using otg. Same problems.
I can only think its recovery or sim card related? any ideas?

btw I have tried fixing permissions and repairing file system in recovery. Thanks in advance!

parmafran said:
I have had my phone a month and its been working flawlessly. I've installed a few custom roms on it and I'm comfortable with all the technical side from years of doing this.
What happened is my phone had a random shutdown and on reboot there was a com.androidsystemui error. No problem I thought, so I wiped the phone and restored a backup of the same rom (latest Heisenberg which has been very stable for me) same issue. OK maybe its rom related. So I did a clean install of Slimkat which I have found v stable. Instant reboot on setup. After trying this a few times I took the nuclear option and wiped by entire phone including storage and went through all this again using otg. Same problems.
I can only think its recovery or sim card related? any ideas?
Click to expand...
Click to collapse
What recovery are you using? I would consider trying out Philz touch recovery, not sure it will fix it, but its worth a shot anyways.

I have exactly the same bug, with my one (the one with these problems is for a friend) i once had this too, i thougt flashing every image file from stock image has fixed it ill try it in some hours.
BTW i use TWRP v 2.7.1.1 or 2.8.0.1 but this lsat one dont works with multirom for now

I managed to fix it! I used this guide: http://forum.xda-developers.com/one...fs-corrupt-t2879061/post55531560#post55531560

parmafran said:
I managed to fix it! I used this guide: http://forum.xda-developers.com/one...fs-corrupt-t2879061/post55531560#post55531560
Click to expand...
Click to collapse
Thank you very much

Read the full thread. Possibly a latest twrp issue.