I'm having a problem flashing both the AOKP (rohan - milestone 6.2) and CM9 (vinvinvinster - alpha 5) builds to my phone. I appear to be experiencing the same issue with both so I was hoping someone could help. I managed to flash both properly, but when I try to start my phone, both get hung in the boot animation forever. No restarts, just plays the boot animation on a loop. Has anyone else experienced this, or is there some way I can gather more info about what is happening? Any ideas? Thanks.
theplagiarist said:
I'm having a problem flashing both the AOKP (rohan - milestone 6.2) and CM9 (vinvinvinster - alpha 5) builds to my phone. I appear to be experiencing the same issue with both so I was hoping someone could help. I managed to flash both properly, but when I try to start my phone, both get hung in the boot animation forever. No restarts, just plays the boot animation on a loop. Has anyone else experienced this, or is there some way I can gather more info about what is happening? Any ideas? Thanks.
Click to expand...
Click to collapse
Just a few questions about your situation...
1. What carrier are you on? I just have to get this out of the way first to rule out that you don't have an international version.
2. Did you do a factory reset before flashing?
3. Bootloader unlocked? (again...this is just to rule this out)
4. What recovery are you using? CWM or TWRP?
5. Have you tried flashing any other roms? CleanROM? Nocturnal? If so, have you had any issues with those booting?
stnguyen09 said:
Just a few questions about your situation...
1. What carrier are you on? I just have to get this out of the way first to rule out that you don't have an international version. AT&T. Flashed the Evita version of both.
2. Did you do a factory reset before flashing? Yes. Have gone through several installs of the stock RUU in between tries.
3. Bootloader unlocked? (again...this is just to rule this out) Yep.
4. What recovery are you using? CWM or TWRP? TWRP
5. Have you tried flashing any other roms? CleanROM? Nocturnal? If so, have you had any issues with those booting? The only one I got to boot was the RebelROM Senseless one.
Click to expand...
Click to collapse
Answers in the quote.
theplagiarist said:
Answers in the quote.
Click to expand...
Click to collapse
Darn you for not having the international version and making this super easy =P
Just for clarification...since you have to relock your bootloader to run the RUU, you are definitely unlocking again before you try flashing, right? Again, not trying to patronize, just rule stuff out.
Maybe you could pull a logcat from hboot and see if it contains any information? I'm not even sure if you can do that but maybe someone else can chime in on this.
theplagiarist said:
I'm having a problem flashing both the AOKP (rohan - milestone 6.2) and CM9 (vinvinvinster - alpha 5) builds to my phone. I appear to be experiencing the same issue with both so I was hoping someone could help. I managed to flash both properly, but when I try to start my phone, both get hung in the boot animation forever. No restarts, just plays the boot animation on a loop. Has anyone else experienced this, or is there some way I can gather more info about what is happening? Any ideas? Thanks.
Click to expand...
Click to collapse
When you go to install CM or AOKP ROM do you wipe /system before install? When I came from a Sense Based ROM I had to wipe /system before installing a AOSP ROM or it would hang at the HTC screen.
So steps should be
1: load into recovery
2: do a factory wipe and then manually wipe /system
3: Install CM or AOKP then reboot
4: after the ROM loads up reboot to recovery again and install GAPPS
This is exactly what I did when coming from CleanROM to a AOSP ROM.
stnguyen09 said:
Darn you for not having the international version and making this super easy =P
Just for clarification...since you have to relock your bootloader to run the RUU, you are definitely unlocking again before you try flashing, right? Again, not trying to patronize, just rule stuff out.
Maybe you could pull a logcat from hboot and see if it contains any information? I'm not even sure if you can do that but maybe someone else can chime in on this.
Click to expand...
Click to collapse
Yeah I have been unlocking every time. No problem I'd probably ask the same questions.
P_Dub_S said:
When you go to install CM or AOKP ROM do you wipe /system before install? When I came from a Sense Based ROM I had to wipe /system before installing a AOSP ROM or it would hang at the HTC screen.
So steps should be
1: load into recovery
2: do a factory wipe and then manually wipe /system
3: Install CM or AOKP then reboot
4: after the ROM loads up reboot to recovery again and install GAPPS
This is exactly what I did when coming from CleanROM to a AOSP ROM.
Click to expand...
Click to collapse
I will give this a try. I may just grit my teeth and live with sense until the kernel is available and more stable/full featured stuff starts coming out
Thanks to everyone.
Related
Please help. When i first received my HTC One X, i had it rooted and the boot loader unlocked. TWRP recovery is also installed. The first thing i did was flash Clean Rom 3 LE and it booted up and was working perfectly. A few days later, i attempted to flash Cm9 alpha4 and after telling TWRP to reboot, it would just sit at the HTC screen for over twenty minutes. I tried restoring my backup and re downloading the file but it still failed. At this point i had just thought that it must be an issue with the rom on my phone, so i downloaded aokp rom from rootzwiki. I did a factory reset and cleared my caches, but it would then get stuck at the HTC screen, and then proceed to the recovery as if i had never flashed the rom. Any help is really appreciated. Thank you
If nothing else work, you can run one of the RUUs. But it will wipe data, and you will need to root, unlock bootloader (?) and install recovery again.
Thanks, but I am able to plug my phone into my mac and get to the recovery via terminal. I can then flash Clean rom and it will boot up and work fine. I'm wondering if this is an issue flashing any non-Sense based roms.
I've Flashed miui and cm9 and aokp with no problems. Did you flash the ones found in our development section? The ones in the International section won't work.
Try redownloading the zips. Make sure you wipe everything a couple times.
In the TWRP recovery wipe menu select cache, factory reset, and system then install CM9. This should fix your problem.
I flashed the ones found in our development section. Is there any extra step that I have to take. I did a factory reset, cleared my cache and dalvik cache, and then flashed the rom. I then cleared my cache and dalvik cache and then rebooted.
AMDERS17 said:
I flashed the ones found in our development section. Is there any extra step that I have to take. I did a factory reset, cleared my cache and dalvik cache, and then flashed the rom. I then cleared my cache and dalvik cache and then rebooted.
Click to expand...
Click to collapse
I don't think it's casuing the problem but the 2nd cache and dalvik clearning aren't necessary.
P_Dub_S said:
In the TWRP recovery wipe menu select cache, factory reset, and system then install CM9. This should fix your problem.
Click to expand...
Click to collapse
Still not working, but thank you for the advice. If it helps any, its stuck at the first HTC screen where it tells you in red that the software is for development purposes only.
AMDERS17 said:
Still not working, but thank you for the advice. If it helps any, its stuck at the first HTC screen where it tells you in red that the software is for development purposes only.
Click to expand...
Click to collapse
it just sits there?
that's odd.
if you connect it to your computer can you get a logcat?
type adb logcat from command prompt.
gunnyman said:
it just sits there?
that's odd.
if you connect it to your computer can you get a logcat?
type adb logcat from command prompt.
Click to expand...
Click to collapse
When i enter the command, this is what i get:
- exec '/system/bin/sh' failed: No such file or directory (2) -
Ive never taken a logcat before, so Im sure i must have done something wrong
AMDERS17 said:
When i enter the command, this is what i get:
- exec '/system/bin/sh' failed: No such file or directory (2) -
Click to expand...
Click to collapse
is adb in your path?
gunnyman said:
is adb in your path?
Click to expand...
Click to collapse
It is, but does my phone need to be on, because it is stuck at the HTC screen
Ok. Flash a rom you know works. Get the phone running then do a fresh download of cm9 alpha 4. Before you install it do a backup in recovery in case it's borked again.
gunnyman said:
Ok. Flash a rom you know works. Get the phone running then do a fresh download of cm9 alpha 4. Before you install it do a backup in recovery in case it's borked again.
Click to expand...
Click to collapse
Doing that now
Re downloaded the file and flashed it but it is still stuck at the HTC booting screen
AMDERS17 said:
Re downloaded the file and flashed it but it is still stuck at the HTC booting screen
Click to expand...
Click to collapse
stupid question is your bootloader locked?
gunnyman said:
stupid question is your bootloader locked?
Click to expand...
Click to collapse
It is. I was a able to flash Clean Rom. Im pretty stumped as to what the problem is.
AMDERS17 said:
It is. I was a able to flash Clean Rom. Im pretty stumped as to what the problem is.
Click to expand...
Click to collapse
if it's LOCKED that's probably your problem. Unlock it. There's no reason to re-lock it anyway.
gunnyman said:
if it's LOCKED that's probably your problem. Unlock it. There's no reason to re-lock it anyway.
Click to expand...
Click to collapse
Sorry. I read your other post wrong. It is unlocked. lol
I've been having a problem with phone calls putting them on speaker. The volume of the external speaker is comparable to the volume of the ear piece. This is only in calls, music and notifications seem to be fine. It was fine before I rooted, but seems to be goofed up on JB roms. I rooted with the brand new 2.20 root method. I tried things like Volume+ and nothing seems to make a difference. I've tried all the basic things like wiping cache/dalvick. What are the chances it's a bad device?
you already posted this in the roms thread. someone probably saw it so why make a thread? wipe and reflash. you also can't blame root because you flashed another rom. on first root, unlock, recovery flashing i always "fastboot erase cache", then wipe literally everything in twrp, then flash my rom. you could first try "fastboot erase cache" in bootloader then wipe cache/dalvik then fix permissions before doing the above and see if that fixes it.
DvineLord said:
you already posted this in the roms thread. someone probably saw it so why make a thread? wipe and reflash. you also can't blame root because you flashed another rom. on first root, unlock, recovery flashing i always "fastboot erase cache", then wipe literally everything in twrp, then flash my rom. you could first try "fastboot erase cache" in bootloader then wipe cache/dalvik then fix permissions before doing the above and see if that fixes it.
Click to expand...
Click to collapse
yes, i posted it there because at the time i thought the problem was specific to that rom (i think it started with the codename rom). but after being on more than one rom (i'm now on the jb build 4) i don't think it is. or it may be specific to jb roms. i'm not sure. i thought i would ask before i just go flashing away... i'm also wondering if anybody else is having this problem.
i followed you all the way till "fix permissions", is this another tab in twrp?
with all the changes right now with CM10 which is base for alot of jb roms its hard to determine the cause. unless you are using a jb aosp build before the kernel changes which is basically anything after 10/01 then you might have some unique issues.
fix permissions is under advanced
Speaking of kernels, I haven't gotten any kernels to successfully flash with either ROM. For instance rohans kernel to oc. Flashed it with his ROM. Won't take.
So basically what you're saying is wipe caches with fastboot, go into twrp, erase everything, reflash, then fix permissions?
Sent from my One X using xda app-developers app
ck4794 said:
Speaking of kernels, I haven't gotten any kernels to successfully flash with either ROM. For instance rohans kernel to oc. Flashed it with his ROM. Won't take.
So basically what you're saying is wipe caches with fastboot, go into twrp, erase everything, reflash, then fix permissions?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
use the stock kernel that comes with your rom for now. reboot in to bootloader and "fastboot flash boot boot.img" the kernel(ie boot.img) from ur current rom. then run "fastboot erase cache" then boot into recovery. wipe cache/dalvik then go into advanced and fix permissions.
if that doesnt work then wipe everything and reflash your rom and gapps if its aosp rom, then rewipe cache/dalvik and reboot.
Didn't work, but sandy just knocked out the power so I think this can wait a while haha
Sent from my One X using xda app-developers app
ck4794 said:
Speaking of kernels, I haven't gotten any kernels to successfully flash with either ROM. For instance rohans kernel to oc. Flashed it with his ROM. Won't take.
So basically what you're saying is wipe caches with fastboot, go into twrp, erase everything, reflash, then fix permissions?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I respectfully suggest you stay away from custom kernel for now until you are a little more familiar with your device, especially if you're playing with jb/cm10 based roms stay with the kernel that came with. The devs will not support any issues that arise from flashing a custom kernel on top of a their roms.
Crappyvate said:
I respectfully suggest you stay away from custom kernel for now until you are a little more familiar with your device, especially if you're playing with jb/cm10 based roms stay with the kernel that came with. The devs will not support any issues that arise from flashing a custom kernel on top of a their roms.
Click to expand...
Click to collapse
i will definitely take this under consideration
DvineLord said:
use the stock kernel that comes with your rom for now. reboot in to bootloader and "fastboot flash boot boot.img" the kernel(ie boot.img) from ur current rom. then run "fastboot erase cache" then boot into recovery. wipe cache/dalvik then go into advanced and fix permissions.
if that doesnt work then wipe everything and reflash your rom and gapps if its aosp rom, then rewipe cache/dalvik and reboot.
Click to expand...
Click to collapse
did this and still a no go... no volume on speaker phone during a call. wiped everything and reflashed rom with stock kernel, wiped again, fixed permissions. all other volumes seem to be appropriate.
ck4794 said:
did this and still a no go... no volume on speaker phone during a call. wiped everything and reflashed rom with stock kernel, wiped again, fixed permissions. all other volumes seem to be appropriate.
Click to expand...
Click to collapse
relock bootloader and ruu...if that does not do it you have a hardware issue.
i'm not questioning your logic, but for my own knowledge can you explain this a little better for me? not the process but the reasoning? to my understanding an ruu basically strips the phone back to some previous state, depending on the ruu you chose, and reverts it back to stock. what purpose does re locking the bootloader serve here? would i need a new unlock code or would the unlock code i got from the first time i unlocked it still work?
also let me make sure i have this process down, relock, ruu, unlock, flash? am i missing any steps in there? like will i need to reflash my recovery?
ck4794 said:
i'm not questioning your logic, but for my own knowledge can you explain this a little better for me? not the process but the reasoning? to my understanding an ruu basically strips the phone back to some previous state, depending on the ruu you chose, and reverts it back to stock. what purpose does re locking the bootloader serve here? would i need a new unlock code or would the unlock code i got from the first time i unlocked it still work?
also let me make sure i have this process down, relock, ruu, unlock, flash? am i missing any steps in there? like will i need to reflash my recovery?
Click to expand...
Click to collapse
here is the logic.
1. you need to relock bootloader to run ruu
2. ruu bring you back to vanilla stock everything, allowing you to evaluate your hardware/software issue. If your speaker works it was some kind of corruption if doesn't it you know you have a hardware problem.
Unlock code stays the same.
That's also why you should always do a clean install/full wipe/factory reset when you experiment with different roms (aosp/sense)
Crappyvate said:
here is the logic.
1. you need to relock bootloader to run ruu
2. ruu bring you back to vanilla stock everything, allowing you to evaluate your hardware/software issue. If your speaker works it was some kind of corruption if doesn't it you know you have a hardware problem.
Unlock code stays the same.
Click to expand...
Click to collapse
thanks for being patient with me man, i appreciate it. i'll give this a go a little later this evening and post back results.
ck4794 said:
thanks for being patient with me man, i appreciate it. i'll give this a go a little later this evening and post back results.
Click to expand...
Click to collapse
good luck. :highfive:
[STOCK] AT&T RUU_Evita_UL_Cingular_US-1.85.502
am i ok to run this ruu even though i came from 2.20 when i rooted?
ck4794 said:
[STOCK] AT&T RUU_Evita_UL_Cingular_US-1.85.502
am i ok to run this ruu even though i came from 2.20 when i rooted?
Click to expand...
Click to collapse
http://dl3.htc.com/application/htc_o...s_08022012.exe
Crappyvate said:
http://dl3.htc.com/application/htc_o...s_08022012.exe
Click to expand...
Click to collapse
bad link
ck4794 said:
bad link
Click to expand...
Click to collapse
what...i just tested it ?? hold on
http://forum.xda-developers.com/showpost.php?p=29766409&postcount=3
Crappyvate said:
what...i just tested it ?? hold on
http://forum.xda-developers.com/showpost.php?p=29766409&postcount=3
Click to expand...
Click to collapse
i saw some where i think that this ruu would get me back to square one, unrooted. is there anything like that i should know about before i run this ruu? also i've never run an ruu, is it one of those i put it on my c: drive run it and it will do the work?
Looking for some input on clean ROM on the TF300T,
This is my second time trying to install it and both times it was successful, however as soon as the boot image loads up it stays stuck loading... I did download the file again thinking it may have been corrupted.
It has been sitting there loading for 20 minutes now.
I am using cwm the latest version and I did not install a kernel still running stock
Any ideas on what could cause this?
chibra said:
Looking for some input on clean ROM on the TF300T,
This is my second time trying to install it and both times it was successful, however as soon as the boot image loads up it stays stuck loading... I did download the file again thinking it may have been corrupted.
It has been sitting there loading for 20 minutes now.
I am using cwm the latest version and I did not install a kernel still running stock
Any ideas on what could cause this?
Click to expand...
Click to collapse
CWM has issues on this unit. Many, many complaints. I use twrp. If you decide to use twrp be sure to choose JB and tf300t version.
Clean ROM is freaking amazing! Seriously just do it I love the mods I can make for it too! Can't wait till I get my volume long press seek mod done! Love this device!
Sent from my SGH-T999
"So I put my phone into airplane mode and threw it... worst transformer ever. -.-" -My friend
tobdaryl said:
CWM has issues on this unit. Many, many complaints. I use twrp. If you decide to use twrp be sure to choose JB and tf300t version.
Click to expand...
Click to collapse
I initially when i first rooted intalled Twrp however i was not able to flash anything at all with it, it would give me errors.... that is the only reason i went to cwm.... I was able to make backups and restores with but ROMs flashing would just fail
chibra said:
I initially when i first rooted intalled Twrp however i was not able to flash anything at all with it, it would give me errors.... that is the only reason i went to cwm.... I was able to make backups and restores with but ROMs flashing would just fail
Click to expand...
Click to collapse
OK. It was just a suggestion since the problem you are experiencing is usually cleared by using twrp.
oryhight sullivan
tobdaryl said:
OK. It was just a suggestion since the problem you are experiencing is usually cleared by using twrp.
Click to expand...
Click to collapse
i m going to give twrp another shot...
i installed http://tinyw.in/5foT
JB version for the TF300T
This is the Rom i m trying to install
http://forum.xda-developers.com/showthread.php?t=2049322
Kernel is still stock and i ve left it that way through the aroma installer
Everytime i flash and reboot i get a boot loop
chibra said:
i installed http://tinyw.in/5foT
JB version for the TF300T
This is the Rom i m trying to install
http://forum.xda-developers.com/showthread.php?t=2049322
Kernel is still stock and i ve left it that way through the aroma installer
Everytime i flash and reboot i get a boot loop
Click to expand...
Click to collapse
I'm sorry it is hard to tell since you have chosen an older twrp to install. The current is five versions later and was updated as the kernels were updated to account for changes. The rom you are flashing is based on 10.4.4.25.
chibra said:
i installed http://tinyw.in/5foT
JB version for the TF300T
This is the Rom i m trying to install
http://forum.xda-developers.com/showthread.php?t=2049322
Kernel is still stock and i ve left it that way through the aroma installer
Everytime i flash and reboot i get a boot loop
Click to expand...
Click to collapse
Use TWRP 2.4.1.0
You are using a very old version of TWRP that has bugs with AROMA installer. So that is most likely where your issues are.
What ROM are you ccoming from? What boot loader are you on.
Sounds to me like you need to upgrade your boot loader and possibly do a full wipe - make sure you are on latest TWRP first otherwise you could brick if you use an older recovery!
sbdags said:
What ROM are you ccoming from? What boot loader are you on.
Sounds to me like you need to upgrade your boot loader and possibly do a full wipe - make sure you are on latest TWRP first otherwise you could brick if you use an older recovery!
Click to expand...
Click to collapse
Wise words. Nobody likes to listen to me so im glad someone else suggested it!
elesbb said:
Use TWRP 2.4.1.0
You are using a very old version of TWRP that has bugs with AROMA installer. So that is most likely where your issues are.
Click to expand...
Click to collapse
Updated the TWRP to the version you mentioned still stuck in boot loop.
sbdags said:
What ROM are you ccoming from? What boot loader are you on.
Sounds to me like you need to upgrade your boot loader and possibly do a full wipe - make sure you are on latest TWRP first otherwise you could brick if you use an older recovery!
Click to expand...
Click to collapse
The only ROM i was able to flash that was fully functioning is cm10.1,
i have also flashed PA 2.9 but had some bugs i couldn't stand (screen rotation not working, extended desktop with no pie)
as for boot loader it says 1.00e by "US _Epad-10.4.2.20-20121228" A03
I just updated the TWRP as recommended on the other post (v2.4.1.0)
on every flash i wipe dalvik / Cache / Factory reset.
Before attempting to boot into Clean Rom i also followed the steps on screen saying to wipe cache and dalvik.
I m hoping PA releases a 3.0 for this device and/or i m able to get Clean rom running
chibra said:
The only ROM i was able to flash that was fully functioning is cm10.1,
i have also flashed PA 2.9 but had some bugs i couldn't stand (screen rotation not working, extended desktop with no pie)
as for boot loader it says 1.00e by "US _Epad-10.4.2.20-20121228" A03
I just updated the TWRP as recommended on the other post (v2.4.1.0)
on every flash i wipe dalvik / Cache / Factory reset.
Before attempting to boot into Clean Rom i also followed the steps on screen saying to wipe cache and dalvik.
I m hoping PA releases a 3.0 for this device and/or i m able to get Clean rom running
Click to expand...
Click to collapse
If you are coming from cm10.1 you will definitely need to do a full wipe as it is non stock. It does say this in the first post. You only do a dalvik and cache wipe when upgrading from the same ROM or in CROMI's case from stock.
Do a data wipe in recovery, make sure you have a titanium backup or equivalent if you want to restore apps.
Success!!!
It worked perfectly fine after i install the back up i did before i flashed my 1st costume rom,
I rooted made a back up at stock/rooted... It just would not install from a full wipe,
it install fine once i flashed that specific backup and dirty flashed then wiped dalvik and cache before booting.
I just flashed the pacman nightly over cm11 using philz recovery. and my phone keeps trying to boot up. I get the moto logo for a few seconds then it goes blank and comes back up.
not sure where to begin fixing this. Ive tried to get back into recovery but cant.
any help would be appreciated
oscar the grouch said:
I just flashed the pacman nightly over cm11 using philz recovery. and my phone keeps trying to boot up. I get the moto logo for a few seconds then it goes blank and comes back up.
not sure where to begin fixing this. Ive tried to get back into recovery but cant.
any help would be appreciated
Click to expand...
Click to collapse
You dirty flashed it over CM11? You didn't wipe system, data, cache and dalvik? I always do that, even when I'm flashing an AOSP-based ROM over another AOSP-based ROM.
The only time I won't do this is if I'm flashing say CM11 over CM11.
If you dirty flashed, that might be your problem, but I don't know for sure as I don't use PacMan ROM.
I didn't dirty flash. Cm11 was on there before. I used philz wipe forfor new rom like I always do.
I can get into the fastboot menu. Is there something I can do there to reflash cm11?
oscar the grouch said:
I didn't dirty flash. Cm11 was on there before. I used philz wipe forfor new rom like I always do.
I can get into the fastboot menu. Is there something I can do there to reflash cm11?
Click to expand...
Click to collapse
Not sure then. I always use TWRP to wipe and flash. Could be an issue with the ROM itself or you got a bad download. You might want to try and download the ROM again to ensure it wasn't a bad download.
figured it out. must have had something happen to the recovery file.
in fast boot i flashed a new recovery image and was able to boot into recovery.
Maybe you have the JB bootloader and you flashed a KitKat bootloader based CM11 build... That could explain why your phone is not booting properly.
If nothing works you just can flash a STOCK FIRMWARE to begin again.
The phone has stock kitkat. How can I confirm?
joel_sinbad said:
Maybe you have the JB bootloader and you flashed a KitKat bootloader based CM11 build... That could explain why your phone is not booting properly.
Click to expand...
Click to collapse
That's a no-go. You won't be able to flash a KK-based ROM on a system with a JB Bootloader. The device will abort the installation immediately with a friendly reminder. At least the XT926. Been there, tried that.
^ agree. My atrix HD has a jbbl and I can Confirm this
So I am a complete noob to this whole rooting, s-off, custom rom experience. So far I have managed to unlock my boot loader and gain s-off thanks to all the awesome peeps on this forum. I tried installing Liquid smooth and I got stuck in what I assume was a boot loop. It would boot and simply just reshow the boot animation. Managed to get into recovery and flash back to a backup I made. What would cause this to happen to me? My Htc is currently on android version 4.4.2 with a software number of 1.55.605.2. Do I need to somehow get my android version up to 4.4.4 in order to use Liquid smooth (or any rom for that matter). Or is there something else that I may have done wrong? Any suggestions or help is greatly appreciated.
GarnerArms said:
So I am a complete noob to this whole rooting, s-off, custom rom experience. So far I have managed to unlock my boot loader and gain s-off thanks to all the awesome peeps on this forum. I tried installing Liquid smooth and I got stuck in what I assume was a boot loop. It would boot and simply just reshow the boot animation. Managed to get into recovery and flash back to a backup I made. What would cause this to happen to me? My Htc is currently on android version 4.4.2 with a software number of 1.55.605.2. Do I need to somehow get my android version up to 4.4.4 in order to use Liquid smooth (or any rom for that matter). Or is there something else that I may have done wrong? Any suggestions or help is greatly appreciated.
Click to expand...
Click to collapse
This has occasionally happened to me with some ROM's and well the issue could depend on a lot of things, the most simplest solution that works a lot of the time is to clear your cache & dalvik cache and reboot.
Also by "reshow the boot animation" do you mean it just endlessly loads the boot animation or it shows the old one? Did you wipe your /data partition when you installed the ROM or did it automatically do it for you? If not and the cache wiping didn't solve your problem you could always attempt doing that and then freshly installing it again and re-trying. If by any chance neither of these worked for you then could you please provide a bit more detail as to what you do when you're flashing the ROM? If you've managed to solve you problem then you don't need to bother with providing any further information.
Edit: I went to the thread and read a bit more on it just to insure I wasn't instructing you to do the wrong thing and I noticed it has a GAPPS package to flash, did you follow all of the instructions correctly e.g full wipe, flash gapps, reboot and waited at least 5 minutes (max usual = 10 minutes)?
S1L3nTShaDoWz said:
This has occasionally happened to me with some ROM's and well the issue could depend on a lot of things, the most simplest solution that works a lot of the time is to clear your cache & dalvik cache and reboot.
Also by "reshow the boot animation" do you mean it just endlessly loads the boot animation or it shows the old one? Did you wipe your /data partition when you installed the ROM or did it automatically do it for you? If not and the cache wiping didn't solve your problem you could always attempt doing that and then freshly installing it again and re-trying. If by any chance neither of these worked for you then could you please provide a bit more detail as to what you do when you're flashing the ROM? If you've managed to solve you problem then you don't need to bother with providing any further information.
Edit: I went to the thread and read a bit more on it just to insure I wasn't instructing you to do the wrong thing and I noticed it has a GAPPS package to flash, did you follow all of the instructions correctly e.g full wipe, flash gapps, reboot and waited at least 5 minutes (max usual = 10 minutes)?
Click to expand...
Click to collapse
Yeah it would show the Liquid Smooth boot animation then the name Liquid Smooth, then it would just continuously blink the name Liquid Smooth. Sometimes it would go completely black, vibrate, then reboot to the Htc screen and then to the Liquid Smooth animation. Not sure if that is helpful. I would like to try again though. I did do a factory wipe through twrp before I tried installing them. I didn't do the GApps that way, I just simply included it with the Liquid Smooth zip and flashed them both at the same time. I read through the thread and didn't see that is how to properly do it. Thanks. So just to reiterate, do a full wipe, flash GApps, reboot and wait for 5 minutes, then enter back into twrp and then flash Liquid smooth?
GarnerArms said:
Yeah it would show the Liquid Smooth boot animation then the name Liquid Smooth, then it would just continuously blink the name Liquid Smooth. Sometimes it would go completely black, vibrate, then reboot to the Htc screen and then to the Liquid Smooth animation. Not sure if that is helpful. I would like to try again though. I did do a factory wipe through twrp before I tried installing them. I didn't do the GApps that way, I just simply included it with the Liquid Smooth zip and flashed them both at the same time. I read through the thread and didn't see that is how to properly do it. Thanks. So just to reiterate, do a full wipe, flash GApps, reboot and wait for 5 minutes, then enter back into twrp and then flash Liquid smooth?
Click to expand...
Click to collapse
No no sorry if I confused you or said that wrong, wipe, flash Liquid Smooth & flash the GApps (Same way as before will work as long as its after the ROM) then wipe your cache/dalvik cache(best do this before and after flashing) and attempt booting into it.
Tell me the results of this once you've tried it.
Another question is why does a Rom like Liquid Smooth require GApps to be flashed but another Rom like SinLess doesn't. Is it because one is a aosp? Also when they show the Rom version 4.4.X does that mean it will work with 4.4.2 as well as 4.4.4? Sorry for the basic questions, I try searches but a lot of times come up with nothing.
GarnerArms said:
Another question is why does a Rom like Liquid Smooth require GApps to be flashed but another Rom like SinLess doesn't. Is it because one is a aosp? Also when they show the Rom version 4.4.X does that mean it will work with 4.4.2 as well as 4.4.4? Sorry for the basic questions, I try searches but a lot of times come up with nothing.
Click to expand...
Click to collapse
Some ROM's simply require it and others don't. On the ROM versions, whatever version the ROM you are flashing is based off of is the ROM version. So if Liquid Smooth is 4.4.4 then that means it is based off of the 4.4.4 update for either another edition of the device (Sometimes since Verizon doesn't release anything timely) or YOUR version (Verizon in this case) of the device.
Thanks bud. Followed your directions and boom it worked. Time to play with some custom Roms!