My wife and I both have rezounds and I've decided to flash countershrike 2.4. Both are unlocked and amon-ra 3.15 flashed. When I loaded countershrike on mine the first time, it never got past the first boot animation (waited for well over an hour). Eventually, after flashing an AOKP rom, then flashing countershrike again, it finally came up.
On my wife's, I cannot find any combination of steps that gets past the initial boot animation. I have tried re-flashing multiple times, wiping data, cache, dalvik cache and system and nothing works. I tried flashing the AOKP ROM as well and it was stuck on the first boot animation as well.
I'm pretty much at a total loss as to what steps to take next.
Are you s-on or s-off?
Sent from my Rezound using xda premium
zac41189 said:
Are you s-on or s-off?
Sent from my Rezound using xda premium
Click to expand...
Click to collapse
both are s-on
btt423 said:
both are s-on
Click to expand...
Click to collapse
This might sound stupid but are you manually flashing boot.img?
Sent from my Rezound using xda premium
zac41189 said:
This might sound stupid but are you manually flashing boot.img?
Sent from my Rezound using xda premium
Click to expand...
Click to collapse
doesn't sound crazy at all. I've done it both ways... letting it pick up the PH***.zip file and flashing the boot.img manually.
btt423 said:
doesn't sound crazy at all. I've done it both ways... letting it pick up the PH***.zip file and flashing the boot.img manually.
Click to expand...
Click to collapse
Using "fastboot flash boot boot.img"? That's weird.. With a clean install and boot being flashed it should boot up without any problems. Haven't ever experienced that before.
Sent from my Rezound using xda premium
Have you tried redownloading the rom? Also you could try using TWRP recovery or the updated CWM recovery, and see if those work.
jon7701 said:
Have you tried redownloading the rom? Also you could try using TWRP recovery or the updated CWM recovery, and see if those work.
Click to expand...
Click to collapse
This, I've had similar problems before and it was because the entire file didn't download
zac41189 said:
Using "fastboot flash boot boot.img"? That's weird.. With a clean install and boot being flashed it should boot up without any problems. Haven't ever experienced that before.
Sent from my Rezound using xda premium
Click to expand...
Click to collapse
yeah, I used "fastboot flash boot boot.img"
jon7701 said:
Have you tried redownloading the rom? Also you could try using TWRP recovery or the updated CWM recovery, and see if those work.
Click to expand...
Click to collapse
I haven't tried redownloading, but I did verify the MD5, so I got the whole file. I haven't tried other recoveries, so I'll give that a shot this evening. The same recovery and rom downloads worked successfully on my phone, though.
You might want to try an earlier version of the kernel. I've had good luck w/ 1.7rc1 and Countershrike, which you can find the download link for in prdog's post here (post #1460)...
http://forum.xda-developers.com/showthread.php?p=33944782&highlight=1+7rc1#post33944782
Is the kernel flashing successfully? I had issues with a test version of the PH98IMG I had made early on having a parsing error in hboot. I haven't heard of it as an issue in a release version, but I want to make sure it didn't creep in.
shrike1978 said:
Is the kernel flashing successfully? I had issues with a test version of the PH98IMG I had made early on having a parsing error in hboot. I haven't heard of it as an issue in a release version, but I want to make sure it didn't creep in.
Click to expand...
Click to collapse
This is my first time flashing a ROM, so how would I check to see if the kernel flashed correctly?
shrike1978 said:
Is the kernel flashing successfully? I had issues with a test version of the PH98IMG I had made early on having a parsing error in hboot. I haven't heard of it as an issue in a release version, but I want to make sure it didn't creep in.
Click to expand...
Click to collapse
I'm going to try again this evening... want to verify the steps I need to take. Is the following correct?
Unlock device
Flash custom recovery (maybe try TWRP this time?)
Copy ROM zip to sdcard
Reboot into recovery
Wipe data
wipe cache
wipe dalvik-cache
wipe system
Flash ROM zip
Flash gapps zip
Reboot into bootloader
Flash boot.img
Reboot
When you flash the ROM, select the S-ON option and it should put a PH98IMG.zip on your SD card. When you reboot into the bootloader it will be in fastboot mode. Press the power button to select the BOOTLOADER option and it will go into the bootloader section where it should pick up the PH98IMG and offer you the option to flash it. Press VolUp and it should flash it.
btt423 said:
both are s-on
Click to expand...
Click to collapse
Why
Related
So I was walking my girlfriend through rooting her new Evo3D, and we couldn't get the phone to get past the 'MI' logo, so I figured it was a kernel thing. After four kernels and two versions of MIUI I realized that it wasn't the issue, it was the hboot.
She didn't back up, she has only had it since last night. I now know what I need to do to flash the ROM, but how can I get her back to stock so I can get the app needed?
Any help?
She has HBOOT 1.5, right?
Go back to the folder where you did all the rooting. Get the stock MIUI kernel (boot.img from the flashable zip) and place it in that folder. Open up a cmd and navigate to that folder.
Boot her phone into fastboot mode. (Vol down + power while the phone is off. Hit power button to select fastboot once it goes into bootloader) Plug the phone into the computer via USB
Type 'fastboot flash boot boot.img' in the kernel. If it successfully flashes, you are done! MIUI should boot up now that it has the appropriate kernel. You will need to do this for any ROM you flash.
As long as you have a recovery, just flash whatever rom you want through fastboot and the kernel will stick.
Or just download a stock rooted rom and flash that the same way you just tried to flash MIUI. It will work since you still have the original kernel.
Sent from my PG86100 using XDA App
flonker said:
As long as you have a recovery, just flash whatever rom you want through fastboot and the kernel will stick.
Or just download a stock rooted rom and flash that the same way you just tried to flash MIUI. It will work since you still have the original kernel.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Well, ROM's cant be flashed through fastboot. The ROM is flashed through recovery. Then you go to fastboot and flash the kernel with my guide above. After that, everything should be working fine.
yousefak said:
She has HBOOT 1.5, right?
Go back to the folder where you did all the rooting. Get the stock MIUI kernel (boot.img from the flashable zip) and place it in that folder. Open up a cmd and navigate to that folder.
Boot her phone into fastboot mode. (Vol down + power while the phone is off. Hit power button to select fastboot once it goes into bootloader) Plug the phone into the computer via USB
Type 'fastboot flash boot boot.img' in the kernel. If it successfully flashes, you are done! MIUI should boot up now that it has the appropriate kernel. You will need to do this for any ROM you flash.
Click to expand...
Click to collapse
Hopefully this works! Shes at church right now but I will have her do this ASAP and I'll report back!
(Awesome response time BTW)
Roms are flashed through fastboot just by loading your recovery into fastboot.
I never flash roms and kernels separately. Just go into fastboot, load your recovery, and flash as you normally would.
Sent from my PG86100 using XDA App
I had something similar when flashing MIUI. if you boot the recovery.img from fastboot it should work. you may want to re download just in case of a bad download.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
I'm having the same problem as epicchase. have attempted to flash miui many times. at first i tried to do it through my recovery. it didn't work. then i tried to use the fast boot method and flash it from the recovery that i opened from fast boot. i'm quite frustrated. it just wont boot miui, is it the kernel, i'm new to rooting in general but i think i know what i'm doing. i have spent who knows how many hours trying everything i can. i tried flashing the boot.img and the ROM separately. I have successively flashed android revolution hd, but that's no fun, its nearly the same as the stock ROM any suggestions would be appreciated. it boots but i guess it must be a boot loop but idk all i know is it freezes in the middle of the boot animation.
ps. i am rooted using the htc official method (unfortunately) and am s-on)
redstrike120 said:
I'm having the same problem as epicchase. have attempted to flash miui many times. at first i tried to do it through my recovery. it didn't work. then i tried to use the fast boot method and flash it from the recovery that i opened from fast boot. i'm quite frustrated. it just wont boot miui, is it the kernel, i'm new to rooting in general but i think i know what i'm doing. i have spent who knows how many hours trying everything i can. i tried flashing the boot.img and the ROM separately. I have successively flashed android revolution hd, but that's no fun, its nearly the same as the stock ROM any suggestions would be appreciated. it boots but i guess it must be a boot loop but idk all i know is it freezes in the middle of the boot animation.
ps. i am rooted using the htc official method (unfortunately) and am s-on)
Click to expand...
Click to collapse
Did you do a full wipe before you flashed? Find Virus's Superwipe tool (.zip), boot to recovery with fastboot, flash the superwipe.zip, then flash MIUI.
Twolazyg said:
Did you do a full wipe before you flashed? Find Virus's Superwipe tool (.zip), boot to recovery with fastboot, flash the superwipe.zip, then flash MIUI.
Click to expand...
Click to collapse
I will try that tonight thanks very much in advance
Sent from my PG86100 using XDA App
Twolazyg said:
Did you do a full wipe before you flashed? Find Virus's Superwipe tool (.zip), boot to recovery with fastboot, flash the superwipe.zip, then flash MIUI.
Click to expand...
Click to collapse
well it didn't work it did the same exact thing. I've been giving it about 10 mins to attempt to boot is that long enough? I'm new to non sense roms I've only ever used sense, is there something I'm forgetting to do that is different for non sense roms. *frustration* (and i thought i was beginning to understand this)
---------- Post added at 09:43 PM ---------- Previous post was at 08:46 PM ----------
okay well i tried to flash cyanogenmod 7 still no dice. I must be an idiot, sorry for being a noob.
this is what im doing.
im placing the .zip on root of my sd card. then opening my cmd.
i then type " cd c:\android" (i saved the recovery image in a folder named android) it says
"c:\android" just as it should i then type "fastboot boot recovery.img"
it restarts my phone in recovery
i press install .zip from sd card then click wipe cache and dalvik cache it goes and does its work
i then select the superwipe.zip it says flash compete however it says error or something but i just kind of ignored it.
i then select my miui.zip that i got from www.miui.us
i then select install .zip files the first thing that comes up is "md5 check fail- ignoring" and the continues and flashes (i have no clue what that part means but i continue anyway)
i select reboot and it starts to boot my phone i get the white screen with green htc.
i then get the miui boot animation for anywhere from 2-5 seconds and then it freezes.
i sit and nearly just stare at it and the clock. i wait at least 5 mins but have waited up to 30 mins.
the boot animation never restarts i just freezes there making me think it is not a boot loop (however the definition of an actual bootloop is slightly vague to me.)
anyway thanks for reading and if you have any suggestions i will be very happy for now im just gonna run my android revolution hd rom.
If superwipe isn't working, fastboot to recovery, go to the wipe menu, not install a zip, wipe dalvik, cache, and factory reset. Don't do the factory reset in android, do it in recovery. I'm guessing you got a corrupt download of superwipe, I would redownload it and try it again if I were you.
Try using this one.
Twolazyg said:
If superwipe isn't working, fastboot to recovery, go to the wipe menu, not install a zip, wipe dalvik, cache, and factory reset. Don't do the factory reset in android, do it in recovery. I'm guessing you got a corrupt download of superwipe, I would redownload it and try it again if I were you.
Try using this one.
Click to expand...
Click to collapse
Yayyyy perfect thankyou sooooo much I'm speechless thank you so much!!! it flashed like it was mardi gras.
Sent from my HTC EVO 3D using XDA App
this process doesnt work for me, i have been trying it for 2 mnoths..No avail, is there anyone who can make this work?
EVO 3D HBOOT 1.5
rcquartz said:
this process doesnt work for me, i have been trying it for 2 mnoths..No avail, is there anyone who can make this work?
EVO 3D HBOOT 1.5
Click to expand...
Click to collapse
What didn't work for you?
rcquartz said:
this process doesnt work for me, i have been trying it for 2 mnoths..No avail, is there anyone who can make this work?
EVO 3D HBOOT 1.5
Click to expand...
Click to collapse
make sure your phone is actually rooted if it is hboot 1.5 make sure to use htvdev.com
make sure you have a recovery image
hi sorry if this is already out there been searching for 4 hours now i went to restore my rom from 4ext and it never went to the rom it just keep loading now i seen it say system is in safe mode and to format it did that and rebooted recovery now after a hour of trying i switched to cwm recovery and now it does the same i go into it and after i format or try to install the phone reboots and trys to load but no rom is on it to do that now idk if anyone can help but please if you can guide me around this problem thank you and this is my first post and first time ever stuck
Can't tell you the exact steps, but.... If you can copy a new ROM to the sd card, can you flash that in recovery? Or, you may have to go back and flash a stock RUU via hboot and re-root. Those are a couple of emergency steps I've had to do in the past.
drowe said:
Can't tell you the exact steps, but.... If you can copy a new ROM to the sd card, can you flash that in recovery? Or, you may have to go back and flash a stock RUU via hboot and re-root. Those are a couple of emergency steps I've had to do in the past.
Click to expand...
Click to collapse
im going to try ruu now
kmd612 said:
im going to try ruu now
Click to expand...
Click to collapse
also no matter what i do in recovery it just restarts by it self and starts over thats why i can flash any thing and i noticed if i do a full wipe it does not do system
Are you using format all except SD card in 4ext? Cwm will not format boot or system partitions.
Sent from my Thunderbolt using Tapatalk 2
I did do that in 4ext and soon as it started it would reboot then try to boot up finally had to use a ruu and start all over and it worked thanks for all the help and earlier when I tryed a ruu it would fail but finally worked
Sent from my ADR6400L using xda app-developers app
OK, so I successfully S-Off'd this phone using DirtyRacun. I backed up the stock functioning ROM, then went to flash Viperlte 2.2.0. Went through all the Aroma installer options, then went to flash. It breezed through the install process, leaving the phone without any operating system on it (Recovery didn't actually flash anything). Tried both CWM and TWRP, and same results each time.
So, I decided to simply try flashing the boot.img in the downloads for Viperlte 2.2.0 via fastboot, and after doing that, the phone still won't boot, and now whenenver I try to reboot into recovery, recovery flashes for a second, and then screen goes blank and boot loops.
Tried reflashing the stock boot.img and reflashed recoveries, same results each time. I'm at a loss. I don't understand what got messed up by fastboot flashing the boot img.
Any help is greatly appreciated!
Boostjunky said:
OK, so I successfully S-Off'd this phone using DirtyRacun. I backed up the stock functioning ROM, then went to flash Viperlte 2.2.0. Went through all the Aroma installer options, then went to flash. It breezed through the install process, leaving the phone without any operating system on it (Recovery didn't actually flash anything). Tried both CWM and TWRP, and same results each time.
So, I decided to simply try flashing the boot.img in the downloads for Viperlte 2.2.0 via fastboot, and after doing that, the phone still won't boot, and now whenenver I try to reboot into recovery, recovery flashes for a second, and then screen goes blank and boot loops.
Tried reflashing the stock boot.img and reflashed recoveries, same results each time. I'm at a loss. I don't understand what got messed up by fastboot flashing the boot img.
Any help is greatly appreciated!
Click to expand...
Click to collapse
how did you install recovery, the first time you must use adb and flash the recovery.img.
command is: fastboot flash recovery(what ever here).img example: fastboot flash recovery recovery-clockwork-touch-6.0.2.9-fireball.img
Ok, have the phone booting again (flashed ruu, then reflashed the dirtyracun hboot). Question still remains, why did I start bootlooping recovery after flashing the boot.img? And why wouldn't the Rom actually flash in recovery?
Again, any insight is appreciated.
Boostjunky said:
Ok, have the phone booting again (flashed ruu, then reflashed the dirtyracun hboot). Question still remains, why did I start bootlooping recovery after flashing the boot.img? And why wouldn't the Rom actually flash in recovery?
Again, any insight is appreciated.
Click to expand...
Click to collapse
flash the rom then the boot img then boot.
Aldo101t said:
how did you install recovery, the first time you must use adb and flash the recovery.img.
command is: fastboot flash recovery(what ever here).img example: fastboot flash recovery recovery-clockwork-touch-6.0.2.9-fireball.img
Click to expand...
Click to collapse
Yeah, did that. I was in recovery (TWRP) when I tried flashing Viperlte, but it never flashed the Rom after selecting all the options in Aroma. It stated that it did, but there's no way it did. It took less than a second to go from "installing" to "complete".
So, something is funky there.
Boostjunky said:
Yeah, did that. I was in recovery (TWRP) when I tried flashing Viperlte, but it never flashed the Rom after selecting all the options in Aroma. It stated that it did, but there's no way it did. It took less than a second to go from "installing" to "complete".
So, something is funky there.
Click to expand...
Click to collapse
what version of twrp are you using
---------- Post added at 08:47 PM ---------- Previous post was at 08:45 PM ----------
for what it's worth some of the guys had problems, and went back to 2.3.3 and solved the problem, I've never had a problem and i'm running 2.4.4
also you must wipe cache,dalvic, data/factory reset,system
Aldo101t said:
what version of twrp are you using
---------- Post added at 08:47 PM ---------- Previous post was at 08:45 PM ----------
for what it's worth some of the guys had problems, and went back to 2.3.3 and solved the problem, I've never had a problem and i'm running 2.4.4
Click to expand...
Click to collapse
I was on the latest release of TWRP (2.4.4.0). I have a recovery log from when it wouldn't flash the ROM. I'll spare the unnecessary strings, and just post the error itself:
error: file_write: write: I/O error
Installer Error (Status 1)
Edit: Just to add, I just successfully flashed SuperSU on the stock ROM using the same TWRP version (2.4.4.0).
Boostjunky said:
I was on the latest release of TWRP (2.4.4.0). I have a recovery log from when it wouldn't flash the ROM. I'll spare the unnecessary strings, and just post the error itself:
error: file_write: write: I/O error
Installer Error (Status 1)
Edit: Just to add, I just successfully flashed SuperSU on the stock ROM using the same TWRP version (2.4.4.0).
Click to expand...
Click to collapse
well, I don't know for sure i'd try 2.3.3 and see what happens
Aldo101t said:
well, I don't know for sure i'd try 2.3.3 and see what happens
Click to expand...
Click to collapse
I appreciate the suggestions. I'll give a few things a try.
Looks like it was the recovery, afterall. Flashed 2.3.3.0, and the ROM is currently flashing as we speak.
Thanks again!
Boostjunky said:
Looks like it was the recovery, afterall. Flashed 2.3.3.0, and it's currently flashing as we speak.
Thanks again!
Click to expand...
Click to collapse
anytime
Aldo101t said:
what version of twrp are you using
---------- Post added at 08:47 PM ---------- Previous post was at 08:45 PM ----------
for what it's worth some of the guys had problems, and went back to 2.3.3 and solved the problem, I've never had a problem and i'm running 2.4.4
also you must wipe cache,dalvic, data/factory reset,system
Click to expand...
Click to collapse
Hmmm, what's going on here? Aldo101t, do aroma installers work for you on 2.4.4.0? I wonder if its a simple reboot after flashing recovery problem. I need a way to reproduce this.
Sent from my Incredible 4G LTE using Tapatalk 2
mdmower said:
Hmmm, what's going on here? Aldo101t, do aroma installers work for you on 2.4.4.0? I wonder if its a simple reboot after flashing recovery problem. I need a way to reproduce this.
Sent from my Incredible 4G LTE using Tapatalk 2
Click to expand...
Click to collapse
I confirm aroma not working on 2.4.4.0 at least on my end.
http://img716.imageshack.us/img716/3192/1362812254888.png
mdmower said:
Hmmm, what's going on here? Aldo101t, do aroma installers work for you on 2.4.4.0? I wonder if its a simple reboot after flashing recovery problem. I need a way to reproduce this.
Sent from my Incredible 4G LTE using Tapatalk 2
Click to expand...
Click to collapse
well, i'm not sure. when i tried to flash viper 2.2 i had a problem, but i can't remember what i did now. i used the same recovery, got it installed, i think i restored a stock rom then reflashed viper and it worked, but i'm not sure.
it's been awhile since i've tried to flasn with aroma, so
i just tried flashing viper 2.2, DID NOT WORK, so i miss spoke.sorry
I have also had problems with aroma on several builds of twrp and several builds of cwm. I'm currently on cwm touch and if it fails to install (goes from 7% to done in a few seconds) just try it again till it flashes. Also seems to help me if zips are on the ext SD card. Not sure what's up with this but that's how I got it to work. Seems to be an aroma thing. Regular zips have no problems flashing.
Sent from my Incredible 4G LTE using xda premium
Hello,
I was attempting to install Meanbeam.
Evo -LTE of course. I did the back up and the factor wipe then in TWRP, choice install and selected the rom from the sd card. The problem is that it has be "installing" now for about an hour and a half. It appears to be froze.
The last two lines are installing update... and formatting and mounting partition...
S- on. I was attempting to following Mikeys directions for S on phones.
At this point is there anything I can do or just let the phone sit longer?
Thanks
Edit. I was able to get it to abort. (somehow, I am not entirely sure) haha
Were you able to get your issue resolved?
Sent from my EVO using xda premium
If your device is not in an S-Off state, I believe you'll have to flash the MeanBean boot.img booter via the fastboot command. This is what I had to do after achieving an unlocked bootloader and installing a custom recovery, such as TWRP or ClockworkMOD.
SkedAddled said:
If your device is not in an S-Off state, I believe you'll have to flash the MeanBean boot.img booter via the fastboot command. This is what I had to do after achieving an unlocked bootloader and installing a custom recovery, such as TWRP or ClockworkMOD.
Click to expand...
Click to collapse
MeanBean has a kernel installer built in to facilitate ROM flashing when S-on. You have to flash the ROM zip twice, once to flash the ROM, then again to flash the kernel (boot.img).
Sent from my EVO using xda premium
FinZ28 said:
MeanBean has a kernel installer built in to facilitate ROM flashing when S-on. You have to flash the ROM zip twice, once to flash the ROM, then again to flash the kernel (boot.img).
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Thanks Guys.
I was able to get it to cancel out of the stuck install screen, I am not exactly sure what I pushed to get it to that, but.
I had an older version of TWRP.
I rooted a while ago and was just getting around to flashing a new rom.
Once i upgraded to the new TWRP the install went perfectly.
Hey guys I am in some need for help. I am trying out the 4.4 ROM over in the dev thread and ran into an issue. My phone sticks at the "This build is for development purposes only etc" screen when attempting to boot to the ROM. Bellow are the steps ive done
1) Flash the recovery.img that was posted
2) Flash ROM from new CWM recovery
3) Wipe data/cache and dalvik
4) Reboot
I have pulled battery and still no resolve. I can still get into fastboot and recovery, just wont load the ROM (sticks at the HTC quietly brilliant screen)
Please help!
Thank you
grayson.mott said:
Hey guys I am in some need for help. I am trying out the 4.4 ROM over in the dev thread and ran into an issue. My phone sticks at the "This build is for development purposes only etc" screen when attempting to boot to the ROM. Bellow are the steps ive done
1) Flash the recovery.img that was posted
2) Flash ROM from new CWM recovery
3) Wipe data/cache and dalvik
4) Reboot
I have pulled battery and still no resolve. I can still get into fastboot and recovery, just wont load the ROM (sticks at the HTC quietly brilliant screen)
Please help!
Thank you
Click to expand...
Click to collapse
Why are you wiping after you flash the rom?
Just flash the rom, flash Gapps,...reboot.
If I remember correctly, I needed to pull the boot.img from the 4.4 tiKtaK Alpha ROM and flash it with Fastboot to get the ROM running.
santod040 said:
Why are you wiping after you flash the rom?
Just flash the rom, flash Gapps,...reboot.
Click to expand...
Click to collapse
I wrote that out of order, sorry. I have wiped data/cache then flashed the ROM. Any ideas? It is stuck on the HTC quietly brilliant screen. I verified the files were downloaded properly.
grayson.mott said:
I wrote that out of order, sorry. I have wiped data/cache then flashed the ROM. Any ideas? It is stuck on the HTC quietly brilliant screen. I verified the files were downloaded properly.
Click to expand...
Click to collapse
Try just going back into recovery again, don't wipe anything, reflash the rom and Gapps.
If you are not s-off, then yes you will have to fastboot flash the boot image as mentioned above.
triseal1 said:
If I remember correctly, I needed to pull the boot.img from the 4.4 tiKtaK Alpha ROM and flash it with Fastboot to get the ROM running.
Click to expand...
Click to collapse
Awesome man thanks trying now... was the command syntax fastboot flash bootloader boot.img ?
grayson.mott said:
Awesome man thanks trying now... was the command syntax fastboot flash bootloader boot.img ?
Click to expand...
Click to collapse
Yeah it still is getting stuck at the HTC screen. I do have S=Off so that explains that.
santod040 said:
Try just going back into recovery again, don't wipe anything, reflash the rom and Gapps.
If you are not s-off, then yes you will have to fastboot flash the boot image as mentioned above.
Click to expand...
Click to collapse
Ok so I booted into CWM recovery and flashed the rom and then gapps. After a reboot it is still getting stuck on the quietly brilliant issue. Could I have an older radio or something? I came from a 10.1 nightly. Thanks for the help.
grayson.mott said:
Ok so I booted into CWM recovery and flashed the rom and then gapps. After a reboot it is still getting stuck on the quietly brilliant issue. Could I have an older radio or something? I came from a 10.1 nightly. Thanks for the help.
Click to expand...
Click to collapse
That's definitely possible.
I would suggest hunting down the latest available radio for your device and falshing it if you aren't on it already.
I see Andy has posted these, I don't know if you guys have anything newer or not...
santod040 said:
That's definitely possible.
I would suggest hunting down the latest available radio for your device and falshing it if you aren't on it already.
I see Andy has posted these, I don't know if you guys have anything newer or not...
Click to expand...
Click to collapse
Dang yeah im on current radio (1.53.06.0919). I'm stumped, I just tried the whole process over Locked bootloader, then unlocked, fastbooted cwm recovery and flashed rom + gapps. It keeps hanging at the htc screen, what are my options?
Ok for now im rolling to stock via RUU. I relocked the boot loader to do so.
grayson.mott said:
Ok for now im rolling to stock via RUU. I relocked the boot loader to do so.
Click to expand...
Click to collapse
Did you verify that you had a complete download?
Check the md5 sum of the file you downloaded against what's on the server.
I know you already reverted, but that's the only other thing I can suggest really.
grayson.mott said:
Dang yeah im on current radio (1.53.06.0919). I'm stumped, I just tried the whole process over Locked bootloader, then unlocked, fastbooted cwm recovery and flashed rom + gapps. It keeps hanging at the htc screen, what are my options?
Click to expand...
Click to collapse
Silly question, but are you sure you have the correct gapps? Maybe flash just the rom and see if you can complete the boot process. Then install gapps.
J