I have flashed many ROMS to my phone and about 3 months ago I flashed MIUI rom v5 simply because I thought it would be cool. I no longer want it, it's just getting boring, so I want another ROM, pretty much any ROM, Cyanogen, Carbon, AOKP, I've tried them all. some won't even flash, it says failed before I can boot up the device so I have to restore back to MIUI. although some do, and there's a problem, there is an error message that keeps popping up when I do anything, I think it says something about a keyboard but it goes away too fast to read it. that wouldnt be such a nuisance if the home button would work. on the MIUI ROM the home button works fine, but on any other ROM that hasn't mysteriously failed, the home button won't do a thing. It's not a problem with the home button either, if I try to go home with PIE controls, it does nothing, nor if I activate software keys. I'm not sure if it's a problem but when I install a ROM other than MIUI, it completely skips the introduction thing, you know, where you set up everything like the wifi and your account and such, it just goes straight to the homescreen and has these problems. I'm installing these ROMS through TWRP which has had many successes, so I can't help but think it's the MIUI ROM that has messed up my device, any help would be appreciated.
Firstly, do you have the HTC One X (Endeavoru) or the HTC One XL / at&t One X (Evita)? What are your bootloader details? I need to see the first five lines. What version of TWRP are you using? What are the full filenames of the ROMs that you've tried? Please answer all above questions, I need as much exact information as possible to help you properly.
There are a few reasons why the ROM installs are failing in TWRP: the ROM isn't meant for your phone, you're using the incorrect version of TWRP (some are very buggy), the download is corrupted, you are on the incorrect firmware version that the ROM installer is checking for. The reason the intro is skipping and you're getting a bunch of errors on ROMs that do install is probably because you haven't installed gapps, or you've installed the wrong gapps.
I'm certain we can fix whatever is wrong, it's most likely something very simple you've missed. As long as you give the information required this should be easy.
Sent from my Evita
Related
I don't know what to do next, and I need my phone. I can answer any questions, but I wouldn't know what to start with. Can someone help??
Quick questions to answer:
1. What Rom were you on prior to flashing?
2. What Rom were you flashing to?
3. What do you see on your screen?
4. Do button presses give any reaction?
1. http://forum.xda-developers.com/showthread.php?t=1136128 v5.0, it's Gingerbread.
2. I was flashing to CM7, but it didn't flash, so I did what was probably a mistake and went straight for http://forum.xda-developers.com/showthread.php?t=1625619&page=1.
3. I see "DevilKernel" Samsung Galaxy S.
4. If I hold down the volume and power buttons, the DevilKernal boot screen will flash. If I keep the power button held down it resets, if I don't it just flashes and nothing else.
By the way, thanks.
Ok, here's what happened:
The first bootloop you were seeing with CM7 is actually a normal occurrence. You usually have to flash CM-based roms twice to get them to "take" (the first time sets up MTD over BML, the second time installs the rom).
What you're seeing now is the devil kernel trying to load up the CM9-based system, but not having all the parts in place.
Thankfully, you're not in that bad of a place. The easiest thing to do right now is to grab an Odin- or Heimdall-based one click Gingerbread stock package without bootloaders. There's a sticky in the Development section that has them, or you can grab the one in my signature.
Flash the one-click, go to recovery, and flash either CM7 twice or TWICS twice.
That should fix you up.
When I tried flashing the CM7, it said it failed. I'm not sure what went wrong. The TWICS I planned on flashing twice, but it got stuck.
Hard to say - it could be something as simple as a bad download of the flash file.
But you think if I Odin it and try TWICS again it'll work?
It should. Doing the Odin one-click will reset everything back to a factory state, which should remove all the obstacles that would normally stand in the way of a successful installation.
Hey man, for that ROM, this theme will work, right?
http://forum.xda-developers.com/showthread.php?t=1095911
I don't know anything about themes. Or this, apparently. I also got into Recovery and installed it twice, I don't really know what's going on.
So you're now fully set up with TWICS, or you're saying that it's still misbehaving?
Also, that theme should work - I had a CM7 theme that I was able to use with a CM9 rom's theme chooser. Wasn't 100%, but it generally worked.
I'm not sure WHAT is going on. The ROM seems to be working fine, I am reinstalling my apps from Titanium Backup and a "Low on space" popup is here, but that makes no sense since it's the same phone, it's a smaller ROM, and a 32gig SD Card. I also just got a text message that was "rejected due to low space".
What is going on??
It seems my phone always is unable to continue once Super Monkey Ball 2 tries to be backed up.
Look around in the cm7 thread for the dbdata full issue. I think there were some suggestions for how to deal with it in there.
Hey all! This is my first post here since i got my htc one S 2 days ago. I have read quite a bit on how to install custom roms and everything.
The very first ROM i installed was the venom viperOneS OTA 2.1.0 and it ran well until i noticed that my camera was not working. Not even through other apps that require camera. All it says is that the camera is unavailable and shuts down the apps. I tried dozens of things to fix the camera, but no luck. Then realised that my microphone didn't work and i couldn't call anybody.
I decided to get my phone back to stock, but it seems to be an extremely difficult process. I downloaded loads of RUU files (including the newest RUU Ville U JB 45) and after re-locking the phone, and running the .exe file i always get an error after its trying to change the signatures saying that this is not the right file for my phone. (When i press 'update' in the installed the current version is blank, not sure if this means anything).
Then i tried an older viperOneS OTA and was left with a bootloop.
Could somebody please help me out on how to get my phone to stock version?
And before you ask if i've wiped my phone before any ROM installation - i have multiple times.
Thank you in advance.
Have an HTC One S S3 (Z560e) that keeps bootlooping no matter which ROM I install. So far PAC, Cyanogen, Carbon, AOKP have all installed and looped. Slimbean failed to install for some reason, I think partitions were too small from what I read.
Not sure why this is, everything else went fine. Not sure if the latest version of TWRP is running on it but I don't know if that's going to affect the install or not regardless.
Any help on the matter? Only additional info I can add is it was bought in China, model numbers are identical to others, only difference I've found is that the "Search" button is replaced by a Weibo button which makes sense given the market. Still, model numbers are the same and Weibo is entirely software.
Thanks,
Auzeras
So after doing a wipe to my phone (was becoming slow) my phone randomly restarts itself for no reason as if it just crashes. I am running the latest version of the beanstalk rom. http://forum.xda-developers.com/showthread.php?t=2091900 I don't have the greatest understanding of flashing, roms, blah blah blah, but managed to get kit kat working for the last year or so, I don't understand why this is happening now, did I choose a bad rom or something? Everything else on the phone works but obviously constant restarts get to be very annoying.
Any help would be appreciated,
thank you!
Infused4life said:
So after doing a wipe to my phone (was becoming slow) my phone randomly restarts itself for no reason as if it just crashes. I am running the latest version of the beanstalk rom. http://forum.xda-developers.com/showthread.php?t=2091900 I don't have the greatest understanding of flashing, roms, blah blah blah, but managed to get kit kat working for the last year or so, I don't understand why this is happening now, did I choose a bad rom or something? Everything else on the phone works but obviously constant restarts get to be very annoying.
Any help would be appreciated,
thank you!
Click to expand...
Click to collapse
Try leaving it turned on in recovery mode (CWM). If it still reboots, then you have a hardware issue. If it stays stable, I would blame the ROM and try a different version or a different distro.
Sent from my MyTouch 4G Slide
joel.maxuel said:
Try leaving it turned on in recovery mode (CWM). If it still reboots, then you have a hardware issue. If it stays stable, I would blame the ROM and try a different version or a different distro.
Sent from my MyTouch 4G Slide
Click to expand...
Click to collapse
Thanks for the reply,
I don't think it is a hardware issue as it never did this when I had Jelly Bean or even the last time I had Kit Kat, never know though! Also, I will try to leave it in recovery and see if it does it but a few questions:
-What is "distro" (does it has to do with the OS of the phone?)
-Is there some ROM you could recommend to me for this phone that is stable.. When I install the beanstalk ROM there are like 10 to choose from, I'm guessing they are all older/newer versions!?
-Finally something I was wondering for the longest time but wasn't sure of is can I go back to say, Jelly Bean? Or is it "irreversible"?
Thanks again, glad there's people out there who can help the noobs like me!
Infused4life said:
Thanks for the reply,
I don't think it is a hardware issue as it never did this when I had Jelly Bean or even the last time I had Kit Kat, never know though! Also, I will try to leave it in recovery and see if it does it but a few questions:
-What is "distro" (does it has to do with the OS of the phone?)
-Is there some ROM you could recommend to me for this phone that is stable.. When I install the beanstalk ROM there are like 10 to choose from, I'm guessing they are all older/newer versions!?
-Finally something I was wondering for the longest time but wasn't sure of is can I go back to say, Jelly Bean? Or is it "irreversible"?
Thanks again, glad there's people out there who can help the noobs like me!
Click to expand...
Click to collapse
Methinks it is the specific ROM. I call the different types of OM out there distributions (or "distros" - in light of what is commonly used in the Linux world), but there may be a better term. It could be the version of Beanstalk you are using, it could be any version of BeanStalk with your phone. Hard to say.
In light of above, I would try CarbonROM. I tried it out briefly, and haven;t had a problem with it (and have heard no issues form the guy I sold the phone to with it installed).
But if you want to go back to JellyBean, there is still a version of 4.2 kicking around (CM 10.1) in the development threads. You can downgrade, at worst you may have to ODIN back to stock. But try to flash in CWM first. I was quite satisfied with that version. My biggest gripe is that the mobile data quick setting didn't work fully (but the long way around did). There is CM 10.2 as well, but I could never get that one installed on my phone (installer would break). Between the two, I would try 10.1 (and if you cannot find a copy, I can dropbox it to you).
5529
joel.maxuel said:
Methinks it is the specific ROM. I call the different types of OM out there distributions (or "distros" - in light of what is commonly used in the Linux world), but there may be a better term. It could be the version of Beanstalk you are using, it could be any version of BeanStalk with your phone. Hard to say.
In light of above, I would try CarbonROM. I tried it out briefly, and haven;t had a problem with it (and have heard no issues form the guy I sold the phone to with it installed).
But if you want to go back to JellyBean, there is still a version of 4.2 kicking around (CM 10.1) in the development threads. You can downgrade, at worst you may have to ODIN back to stock. But try to flash in CWM first. I was quite satisfied with that version. My biggest gripe is that the mobile data quick setting didn't work fully (but the long way around did). There is CM 10.2 as well, but I could never get that one installed on my phone (installer would break). Between the two, I would try 10.1 (and if you cannot find a copy, I can dropbox it to you).
Click to expand...
Click to collapse
YES!
So, after I left the phone in CWM for 25 minutes or so and it being fine I decided to get Carbon as I seen in your "signature" that you had that ROM on your Infuse, it has been good for 2 hours+, looking good! I guess it was the Beanstalk ROM after all.
Thanks for the downgrading information as well, wasn't sure if you could downgrade or what would happen!
Finally, what is flashing? (I could google it but since your here, could you give me a noob friendly definition!?)
Thanks for all your help
Infused4life said:
YES!
So, after I left the phone in CWM for 25 minutes or so and it being fine I decided to get Carbon as I seen in your "signature" that you had that ROM on your Infuse, it has been good for 2 hours+, looking good! I guess it was the Beanstalk ROM after all.
Thanks for the downgrading information as well, wasn't sure if you could downgrade or what would happen!
Finally, what is flashing? (I could google it but since your here, could you give me a noob friendly definition!?)
Thanks for all your help
Click to expand...
Click to collapse
Went to reply about the camera issue and notice it was no longer in the post. Glad you got it sorted.
So flashing, as I understand it, is just another term for installing something via recovery. Not sure of the origin, maybe have something to do with installing to flash memory.
joel.maxuel said:
Went to reply about the camera issue and notice it was no longer in the post. Glad you got it sorted.
So flashing, as I understand it, is just another term for installing something via recovery. Not sure of the origin, maybe have something to do with installing to flash memory.
Click to expand...
Click to collapse
Ah ok, so it's essentially as I thought it was. I thought I was doing something wrong in terms of "flashing" but guess not! Sounds like it should just be called "Installing custom ROM".. !
Yeah, in terms of the camera thing, I'm an idiot and had USB storage turned on *facepalm*, So it wouldn't let me open the camera app!
Infused4life said:
Ah ok, so it's essentially as I thought it was. I thought I was doing something wrong in terms of "flashing" but guess not! Sounds like it should just be called "Installing custom ROM".. !
Yeah, in terms of the camera thing, I'm an idiot and had USB storage turned on *facepalm*, So it wouldn't let me open the camera app!
Click to expand...
Click to collapse
I am not sure if you are still facing the same issue but if you are facing reboots, then considering doing a fresh install after cleaning your internal storage as well since the remnants of the apps from previous installs have caused me problems. Ever since I started doing a fresh install (Factory reset, wiping the cache, wiping the dalvik cache and even the cache partition along with the wiping of the internal storage), there have been no reboot issues.
I'm new to this site, if I'm doing anything noob-esque, let me know.
So I got SunShine, really happy with the purchase on the license because now I can actually use my phone the way I want. That aside, I really wanted to put Android Revolution HD on it because of the HTC Sense-ness incorporated and it seemed like the ROM that would have best suited me. All day I've been tinkering with my phone to get it to work, but no avail. Everytime I reboot after flashing, it just stays on the "HTC One" logo screen. I know you're supposed to wait longer on the first boot, but after waiting several times (twice I waited an hour), it was easy to see something wasn't working. So now I have PAC ROM on there just so I can actually use my phone until I figure out how to do this. PAC ROM works just fine with flashing, so does Cyanogenmod. Even though they are great ROMs, I want ARHD most on my phone. Can anyone tell me what I've done wrong, because I'm not sure what I'm looking for. I was running stock 4.4.3 when I went to flash it. That's what it said to have on the guide, which is why I don't understand what the problem is. I tried ViperOne; the same thing happened - stayed on boot logo. But again, Cyanogenmod and PAC ROM flash no problem.