I flashed midnight ROM. put the AOSP theme over it. Flashed the newest MAC Kernel, and that's when it started happening.
I decided to factory reset and flash the ROM again, tried to restart. same thing.
restored a backup (after factory restting), no dice.
Wiped boot/data/system, factory resetted, wiped both caches and reflashed midnight ROM. Still nothing.
Tried to flash CM9 (after factory resetting and stuff) and it still won't go past the HTC screen no matter how long I wait.
What's wrong? Am I half bricked?
I'm using the Evo V with S OFF on downgraded HBOOT.
You need to downgrade your radios as well to flash aosp roms. Run an older RUU, which will set you back to stock, flash your recovery and then flash midnight again
Sent from my PG86100 using xda app-developers app
beneath-a-burning-turtle said:
You need to downgrade your radios as well to flash aosp roms. Run an older RUU, which will set you back to stock, flash your recovery and then flash midnight again
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
I've flashed all these ROMs with no problems before. I already have my radios upgraded (I basically turned my phone into a Evo 3D).
RedDeadDorito said:
I've flashed all these ROMs with no problems before. I already have my radios upgraded (I basically turned my phone into a Evo 3D).
Click to expand...
Click to collapse
Gotta go in the opposite direction with radios, downgrade. It'll make older roms compatible again.
Sent from my PG86100 using xda app-developers app
beneath-a-burning-turtle said:
Gotta go in the opposite direction with radios, downgrade. It'll make older roms compatible again.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
So basically, upgrade my HBOOT (since stock is on a upgraded one) again and flash a stock ROM then downgrade again?
I was thinking of doing this, but why did this problem come up in the first place?
I can't do it because I don't have an extra SD card around. If I put the hboot upgrade on my SD card, the bootloader won't start up because it gives you the option to install it or not install and either way, it turns the phone off.
Got it figured out. When I flashed a different kernel, it broke the other kernel or something. I had to flash the ROM's kernel separately. I don't know why.
I'm not sure why, but it did. Anyways, it seems to be working now!
RedDeadDorito said:
Got it figured out. When I flashed a different kernel, it broke the other kernel or something. I had to flash the ROM's kernel separately. I don't know why.
I'm not sure why, but it did. Anyways, it seems to be working now!
Click to expand...
Click to collapse
Glad that you got a solution and that you were also detailed in your response. Perhaps someone in the future that sets aside the time to research and read will be able to either get themselves out of a mess - or - possible avoid one. Cheers!
Related
I have loaded this radio then I booted into recovery and tried to install Das BAMF Sense 3.0 RC4.9 from zip and the download starts then about halfway though it goes back to the bootloader screen with the android guys skateboarding. It has fastboot highlighted with the only options being bootloader,reboot,reboot bootloader, and power down. I have tried to reboot, boot back into recovery and restore but it keeps going back to this screen...any idea's??
s00paSold3r said:
I have loaded this radio then I booted into recovery and tried to install Das BAMF Sense 3.0 RC4.9 from zip and the download starts then about halfway though it goes back to the bootloader screen with the android guys skateboarding. It has fastboot highlighted with the only options being bootloader,reboot,reboot bootloader, and power down. I have tried to reboot, boot back into recovery and restore but it keeps going back to this screen...any idea's??
Click to expand...
Click to collapse
Well, if you can get into the bootloader you are not bricked. Go to Jcase's stock recovery thread and get the rooted stock PG5... to load in hboot. It will essentially get you back to rooted Froyo and then you can reflash the recovery and whatever rom you want.
Or I believe you can rename a ROM to PG5... and flash it in recovery as well, although I've never tried that method.
Sent from my ADR6400L using Tapatalk
I've never heard of anyone flashing a rom through hboot by renaming it to pg05img or whatever it is. I wouldn't try that without evidence of out working
Sent from my ADR6400L using Tapatalk
You. said:
I've never heard of anyone flashing a rom through hboot by renaming it to pg05img or whatever it is. I wouldn't try that without evidence of out working
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
I have. I've just never tried it. It's not something I've ever had to do.
I still would advise caution though.
Sent from my ADR6400L using Tapatalk
I've tried it and it works! Be careful, I would recommend using the stock rooted PC05img that was in the first post, it usually works, you just have to noodle with the 4g settings after.
thanks guys, I am a happy camper. I am loading the stock rom as we speak....Man I lost sleep and could not work.
I've tried it and it works! Be careful, I would recommend using the stock rooted PC05img that was in the first post, it usually works, you just have to noodle with the 4g settings after.
Click to expand...
Click to collapse
I knew I wasn't nuts, lol. Back when I had the Inspire it was a pretty common thing.
Sent from my ADR6400L using Tapatalk
P.S. @ sOOpasold3r, if you want to wait until about 10pm EST, I can send you the exact radio that will work and it will bring everything in to working order for you.
s00paSold3r said:
thanks guys, I am a happy camper. I am loading the stock rom as we speak....Man I lost sleep and could not work.
Click to expand...
Click to collapse
Good luck. Rooted stock usually does the trick. Just be sure to name it correctly. I always screw that part up, lol.
htcdesirezgeorge said:
P.S. @ sOOpasold3r, if you want to wait until about 10pm EST, I can send you the exact radio that will work and it will bring everything in to working order for you.
Click to expand...
Click to collapse
sure here's my email address [email protected]
I got the stock rom loaded back up.. now I need to reflash CWM
s00paSold3r said:
I got the stock rom loaded back up.. now I need to reflash CWM
Click to expand...
Click to collapse
Good! Yes, I would reflash cwm. Also redownload the rom you want to flash and verify the md5.
Sent from my ADR6400L using Tapatalk
ok chris, I think I have the MR2 Radio on my phone's SD card, if I do, I'll email it earlier.
i have a rezound that i have unlock and rooted..
i have been trying to flash roms on the phone but it gets stuck at the white htc screen.. i have been reading some of the threads and im not sure if i understand if im doing something wrong.. when i try to flash a rom i get into recovery the clear factory reset,clear cache,clear dalvtik.... install the the rom from the external sd card. once its done i get into fastboot and install the PH89IMG.ZIP. onces thats done i reboot and thats when i get stuck... im very new to this... i have tried to install clockworkmod on the phone .. the only why that i get into recovery is using the rezound tool kit 2.0. i dont think that,that has anything to do with it but i could be wrong... somebody please help me....
bakerboy81 said:
i have a rezound that i have unlock and rooted..
i have been trying to flash roms on the phone but it gets stuck at the white htc screen.. i have been reading some of the threads and im not sure if i understand if im doing something wrong.. when i try to flash a rom i get into recovery the clear factory reset,clear cache,clear dalvtik.... install the the rom from the external sd card. once its done i get into fastboot and install the PH89IMG.ZIP. onces thats done i reboot and thats when i get stuck... im very new to this... i have tried to install clockworkmod on the phone .. the only why that i get into recovery is using the rezound tool kit 2.0. i dont think that,that has anything to do with it but i could be wrong... somebody please help me....
Click to expand...
Click to collapse
don't use clockwork, use the amon recovery.
Use among ra recovery. Other that, how long have you let it sit at that screen? Sometimes it takes several minutes, just be patient.
Also, what rom, and are you on the new leaked firmware?
I could remote into team viewer on your computer and flash amon ra recovery on your phone and walk you through installing a Rom and kernel for you if you want.
But to properly wipe, it should be data, cache, dalvic cache, and system
Sent from my ADR6425LVW using xda premium
http://forum.xda-developers.com/showthread.php?t=1425091
that thread helped me alot, do lots of reading before you flash anything. also make sure you have the correct kernel for the rom your using.
i have tried using amon recovery and i get the same result.... i have let it sit for about 10 mins and nothing happens... im trying to flash scottsrom ics.. the latest one....
bakerboy81 said:
i have tried using amon recovery and i get the same result.... i have let it sit for about 10 mins and nothing happens... im trying to flash scottsrom ics.. the latest one....
Click to expand...
Click to collapse
Have you ran the leaked ruu and have the new firmware?
Sent from my ADR6425LVW using Tapatalk 2 Beta-5
ijustwantmydock said:
Have you ran the leaked ruu and have the new firmware?
Sent from my ADR6425LVW using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
he doesn't need to be on the leaked ruu to use the ics roms. he can flash the old firmware patch too.
I have tried to find the leak ruu but I don't know where to find it and how to install it. I was reading about it earlier but I'm still a little iffy on how to do it ..
Sent from my ADR6425LVW using XDA
bakerboy81 said:
I have tried to find the leak ruu but I don't know where to find it and how to install it. I was reading about it earlier but I'm still a little iffy on how to do it ..
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
just be aware if you use it, your hboot will say "tampered" and you cannot roll back to GB firmware. if your new to this, id do alot of reading before attempting it. if you want a good GB based rom look into chingy's rom.
http://forum.xda-developers.com/showthread.php?t=1420513
mighty_markus12 said:
he doesn't need to be on the leaked ruu to use the ics roms. he can flash the old firmware patch too.
Click to expand...
Click to collapse
He can so that but its not supported by Scott so if he has any problems he wont get help.
Just because you are against flashing the leaked firmware doesn't make it bad.
To the OP, if you are uncomfortable with relocking your phone to flash the new firmware I would try one of the gb roms. The update for ICS should be anyday now.
Sent from my Rezound using Tapatalk
nrfitchett4 said:
He can so that but its not supported by Scott so if he has any problems he wont get help.
Just because you are against flashing the leaked firmware doesn't make it bad.
To the OP, if you are uncomfortable with relocking your phone to flash the new firmware I would try one of the gb roms. The update for ICS should be anyday now.
Sent from my Rezound using Tapatalk
Click to expand...
Click to collapse
he can also use rezrom which supports the old firmware with a patch. and we have no clue when the ota will be out. i never told him not to flash the ruu but if he doesn't know what he is doing i recommend he reads up alot. stop trying to contradict everything i say in every thread, it's getting annoying.
OP i sent you a pm.
are u sure that your kernel is being flashed in Fastboot? because thats what usually causes freeze ups
yojoe600 said:
are u sure that your kernel is being flashed in Fastboot? because thats what usually causes freeze ups
Click to expand...
Click to collapse
+1 to this
Need to get my ten post over with so I don't need to do image verifications
Ok, I thought I knew what I was doing. Unfortunately, wine had a factor in my issue... I have a rooted Evo 4g LTE. S-on Hboot 1.15. I was using Clockwork Recovery. I probably should have been using TWRP, from what I've read. When I first got the phone, I was over zealous, and flashed a Mod before saving a recovery. I hated it. So I flashed back to Stock ROM (jewel 1.22.651.3). I wanted to try out a Jelly Bean ROM so I flashed codefireX CM10. It worked but when the phone loaded it kept saying "phone error" and wouldn't let me click okay. So I rebooted into recovery and flashed my previous rom. I was a little tipsy, so I tried it again... It still didnt work... Rebooted into revovery, and this time I cleared cache, cleared davaik cache, and did a factory reset... Then, It wouldn't recover my saved rom. I must have cleared everything again, that I remember, now it won't load into Clockwork. I've tried everything I can think. I tried RUU, No luck. I tried flashing through Fastboot, No luck. Tried Well, I really have researched everything I could think about Boot loops... I'm stuck .... Everything I try seems to have a step missing or issue with my phone because its S-on and I relocked it through abd because RUU needs to be lock on.. I read I may have to flash a new kernel. I'm in over my head. I had to revert to using my Palm Pre. (which I loved for many years, But I really miss my EVO!) PLEASE HELP. :crying:
Check out om4's guide in general, it will tell u all you need to know...good luck.
Sent from my EVO using xda premium
Your issue is that you need a different kernel for CM10, and it needs to pushed in before you flash the ROM(because you're S-on and hboot 1.15).
This will help: http://forum.xda-developers.com/showthread.php?t=1847860
I stopped reading once I read you was using clockwork.
Sent from my EVO using xda premium
shook187 said:
I stopped reading once I read you was using clockwork.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Yeah... I realize now after research... I installed it through ROM manager. Not again. Ugh
shook187 said:
I stopped reading once I read you was using clockwork.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Im now using TWRP. Everythings working again. Thank you.
So I have been using Neo's AOSP Rage Rom since about 1.4, and haven't encountered any serious problems (besides some hiccups such as the Trebuchet FC problem in 1.7, although everyone had that). Now, after I have flashed 1.8, I am unable to turn on my Wifi. I checked my md5s, I did 3 clean flashes, and I also flashed the rom with and without the inverted gapps pack.
My Rezound is currently S-ON, and I have no plans to go S-OFF unless necessary.
I'm not sure if this is a kernel problem, or if it's the wifi module, or perhaps something else, but I figured I should ask here first to see if there were others with he same problem.
Most likely kernel, try flashing Snuzzo's kernel
Sent from my ADR6425LVW using xda app-developers app
Squirrel1620 said:
Most likely kernel, try flashing Snuzzo's kernel
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
I've tried that and it didn't help. I tried both of his kernels without success. My problem may be hardware related though. I can't switch back to sense based from without bootlooping. Same thing with flashing ruu.
aftafoya said:
I've tried that and it didn't help. I tried both of his kernels without success. My problem may be hardware related though. I can't switch back to sense based from without bootlooping. Same thing with flashing ruu.
Click to expand...
Click to collapse
If your running an ruu and still boot looping, then something else is wrong. It's gotta be a hardware problem, time for an insurance return
Sent from my ADR6425LVW using xda app-developers app
Well... I figured out what I was doing wrong, which was that I forgot to re-flash the boot.img that came with the Neo's rom. I suppose I forgot to re-flash it because it never said you had to, but I remembered that the rom was intended for S-OFF, and I'm S-ON, so that never occurred to me.
So, yeah, it was basically the kernel.
After I did a clean wipe and flash of Rage again, and flashed the boot.img in the bootloader, everything worked.
Lucasonic said:
Well... I figured out what I was doing wrong, which was that I forgot to re-flash the boot.img that came with the Neo's rom. I suppose I forgot to re-flash it because it never said you had to, but I remembered that the rom was intended for S-OFF, and I'm S-ON, so that never occurred to me.
So, yeah, it was basically the kernel.
After I did a clean wipe and flash of Rage again, and flashed the boot.img in the bootloader, everything worked.
Click to expand...
Click to collapse
Glad to see it works. Yeah so go s off your phone! Lol its worth it
Sent from my ADR6425LVW using xda app-developers app
I've got the same issue. Except wifi, gps, and bluetooth won't turn on. Also, I keep getting the message that my SD card is damaged. I pulled the boot file from the ROM, zipped it, and named it PH89IMG.
So far, everything else seems to work, but this isn't really working for me. Any suggestions?
Are you on ICS firmware or GB firmware? If you are on GB still and trying to flash ICS rom, wifi and sdcard won't work until you flash the old firmware patch.
Sent from my Rezound using Tapatalk 2
Squirrel1620 said:
Glad to see it works. Yeah so go s off your phone! Lol its worth it
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
I second that notion. I've been on 1.8 for a while and I feel like it's been the best version so far (I'm S-OFF). 1.9 is out now, so I'll be trying that later tonight.
Performing S-OFF isn't that bad. I thought it was fun - just follow the directions and you should be fine (like anything else).
Everytime I go to make a call or receive a call the phone force closes and then signal drops off. I have flashed new kernals and have done a clean Rom install and problem continues. Any help would be greatly appreciated.
Sent from my HTC6435LVW using xda app-developers app
saabguy93 said:
Everytime I go to make a call or receive a call the phone force closes and then signal drops off. I have flashed new kernals and have done a clean Rom install and problem continues. Any help would be greatly appreciated.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Try reflashing a kernel. Might try stock first, then maybe Elkay's or dsb's writeable.
In case you're doing it a different way, try flashing it this way: flash the boot.img using the Flash Image GUI app. Then flash the corresponding modules for that specific boot.img kernel (can't mix and match) in Recovery.
If that doesn't help the situation, you may need to flash a different radio.
HTH!
saabguy93 said:
Everytime I go to make a call or receive a call the phone force closes and then signal drops off. I have flashed new kernals and have done a clean Rom install and problem continues. Any help would be greatly appreciated.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
have you tried a completly different rom?
.torrented said:
have you tried a completly different rom?
Click to expand...
Click to collapse
I have relocked my bootloader. Loaded the stock RUU and then Unlocked again, rerooted and installed Viper Rom and still same Issue.
saabguy93 said:
I have relocked my bootloader. Loaded the stock RUU and then Unlocked again, rerooted and installed Viper Rom and still same Issue.
Click to expand...
Click to collapse
Have you tried a different SIM.
Sent from my HTC6435LVW using xda app-developers app
Perhaps you accidentally flashed your radio partition? Reflash your radio and you'll probably be good to go. Either that or like someone else said try a different sim card.
Bigandrewgold said:
Have you tried a different SIM.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I put the SIM in my Nexus and I dont have any problems at all.
saabguy93 said:
I put the SIM in my Nexus and I dont have any problems at all.
Click to expand...
Click to collapse
Like the other guy said, try flashing a radio.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
Like the other guy said, try flashing a radio.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Flashed the new radio and still a no go. I keep getting "com.android.phone" force close when i go to dial a number.
Run the RUU again but this time try and just booting into android from the RUU and trying to use your phone
saabguy93 said:
Flashed the new radio and still a no go. I keep getting "com.android.phone" force close when i go to dial a number.
Click to expand...
Click to collapse
If you are getting com.android.phone fcs. then reflash ruu, DL' a rom of choice on your computer and transfer using ADB push (will take a second) . reboot to bootloader. flash boot.img, boot to recovery, flash modules, then flash custom rom. when phone reboots, wait about 45 seconds before running setup. If this process still does not work, please report back. Or PM me or another RC so we can figure it out for you in a quick manner.
Well this morning I switched to CWM recovery and loaded Digital Dream 1.5 and I'm back working. Thanks for everyone's help.
Sent from my HTC6435LVW using xda app-developers app
saabguy93 said:
Well this morning I switched to CWM recovery and loaded Digital Dream 1.5 and I'm back working. Thanks for everyone's help.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Yeah so it was a rom issue then
Sent from my HTC6435LVW using XDA Premium HD app
Not a Rom issue, I've had the problem on viper and hatka, both before and after soff and new radio. New kernel, old kernel.
I'm getting ready to try stock 1.15 before I ruu.. will report back.
Edit: Fresh off RUU, with the old radios flashed before the RUU. Still no change. Tried turning phone off, remove sim card, phone on, try to use cell connection (obvious failure), phone off, insert sim card and boot. Still no good. About to try above method using CWM and Digital Dream, as soon as it downloads.
Edit 2: Still no such luck. After digging through system logs, there's quite a few errors pertaining to the radio, IccCard, and RIL. One that particularly caught my eye was an error that there stated Ril_get_icc_status returned an error, and it should never return an error. Unfortunately, I didn't get a capture on the time I saw that, the radio reset which Su to reset which caused catlog to reset. Still have quite a few errors pertaining to SIM problems as well. I am way over my head after this point. I can interpret java, and linux.. but not so much understand when they're mixed together in Android.
http://www.pastebin.ca/2317800 This is logcat capture I got of the radio log. Unknown technology doesn't sound good to me....
http://db.tt/nbYfqEkb A full system log as soon as I could save after the force close. Couple things here and there.
I suppose if I can't get it fixed in a day or two.. off Verizon for a replacement. What's the purpose of a phone if I can't make phone calls on it?
Sent from my HTC6435LVW using xda premium
Unless an error loops continually, its okay.
Have you tried to manually select a different network? I'm not quite sure how to do it on a sense rom, but I do know that when I was messing around within my CM10 build and changed to the wrong network type, I lost 4G data in sense. I reflashed CM10, selected a different network and then flashed back and it was working.
Have no fear...
THE MAN IS HERE!!!
OK guys honestly if it's up to me, we should all be scared ****less if we were relying on me. I bought a DNA with this problem to see if I could fix it and so far I've relocked, run the RUU twice (executable 1.15) unlocked and flashed recovery and done clean rom installs, kernels, switched to every network mode imaginable. I took my sim out of my DNA working perfectly so I know the sim is good in a different DNA.
I just flashed the 2.04 radios and I'm going to see what that does. I promise I'm going to give this issue my everything though because I gave a lot for this phone that's otherwise NIB condition and MINT. OK and the radios didn't help
CharliesTheMan said:
Have no fear...
THE MAN IS HERE!!!
OK guys honestly if it's up to me, we should all be scared ****less if we were relying on me. I bought a DNA with this problem to see if I could fix it and so far I've relocked, run the RUU twice (executable 1.15) unlocked and flashed recovery and done clean rom installs, kernels, switched to every network mode imaginable. I took my sim out of my DNA working perfectly so I know the sim is good in a different DNA.
I just flashed the 2.04 radios and I'm going to see what that does. I promise I'm going to give this issue my everything though because I gave a lot for this phone that's otherwise NIB condition and MINT. OK and the radios didn't help
Click to expand...
Click to collapse
Any luck figuring this out? I have the same issue and have tried radios, kernels, ROMs, RUU, and am still getting the same error message.
jc332986 said:
I was having "com.android.phone" issues. I relocked then ran the RUU. It didn't fix the error. I unlocked, tried to go Into recovery and there was no recovery. I flashed cwm recovery, flashed busy box/superuser, and rebooted. I flashed cubed kernel. The fix for the phone was to fix permissions with system write capabilities. I'm not sure why the RUU didn't put the phone all the way back to stock.
Click to expand...
Click to collapse
spjoneser said:
I had this problem with my first DNA, warrantied it out after trying all the same things, flashing different roms, RUUing. After replacement I came across a thread somewhere and found that someone had fixed the same problem by simply fixing permissions before doing anything else, sounds like once you flash something else you're screwed.
Anyone try that first?
Click to expand...
Click to collapse
Anyone have an idea about the permissions described here?
same issue
dragonstalker said:
If you are getting com.android.phone fcs. then reflash ruu, DL' a rom of choice on your computer and transfer using ADB push (will take a second) . reboot to bootloader. flash boot.img, boot to recovery, flash modules, then flash custom rom. when phone reboots, wait about 45 seconds before running setup. If this process still does not work, please report back. Or PM me or another RC so we can figure it out for you in a quick manner.
Click to expand...
Click to collapse
This is driving me crazy I have same issue mine won't make or receive calls after I did s-off get same message com.androd.phone fcs. I re-locked phone then flashed original rom. Turned on phone still have same problem. So at that point I flashed kernalls h-boot and radios booted still same problem. Then I decided to re-flash RUU rom still same problem. Please help don't know what to do next.:crying:
jimmydee62 said:
This is driving me crazy I have same issue mine won't make or receive calls after I did s-off get same message com.androd.phone fcs. I re-locked phone then flashed original rom. Turned on phone still have same problem. So at that point I flashed kernalls h-boot and radios booted still same problem. Then I decided to re-flash RUU rom still same problem. Please help don't know what to do next.:crying:
Click to expand...
Click to collapse
I'm in the same boat with you my friend :crying:...Can someone please help us. PLEASE!!!