Hey, I flashed the latest Energy rom and I completely lost audio from my device, phone calls are muted aswell (mic+audio). Video are laggy or fastforwarded. Using fau123 kernel since my phone can`t boot when using stock kernel.
EDIT: I think I have an hypothesis concerning my problem. Do you guys think that when I flashed the rom the xml file with the audio profiles and video codecs got messed up or not flashed? I'm going to try to s-off and reflash using the bootloader. But the HTC Amaze has a different hardware configuration (the battery is not placed at the same place) than the T-Mobile one...
duykhang524 said:
Hey, I flashed the latest Energy rom with beats audio and I completely lost audio from my device, phone calls are muted aswell (mic+audio). Video are laggy or fastforwarded. Using fau123 kernel since my phone can`t boot when using stock kernel.
Click to expand...
Click to collapse
try reflashing with a complete wipe.
i dont think ive ever heard anyone else have this problem before
I tried wiping and changing rom still didn't work D: Tried Android Revolution HD and both Energy rom x.x
duykhang524 said:
I tried wiping and changing rom still didn't work D: Tried Android Revolution HD and both Energy rom x.x
Click to expand...
Click to collapse
Try going back to stock
sent from my NRGized Amaze,
powered by faux kernel v.19
were you on ICS or GB before the flash?
I was on gb I am not able to got to stock since videotron does't have the ruu for Gb and I can't boot when I flash the stock ICS OTA with ext4 and can't flash it with bootloader aswell
I think I'm going to try to push the xml files from the Videotron ota in system/etc of my amaze 4G with the energy rom
duykhang524 said:
I was on gb I am not able to got to stock since videotron does't have the ruu for Gb and I can't boot when I flash the stock ICS OTA with ext4 and can't flash it with bootloader aswell
Click to expand...
Click to collapse
uh, pal, stock ota's are flashed thru stock recovery, not custom recoveries or bootloader try using hasoons tool to flash stock recovery (not sure if videotron is even in there?) and load up your ota that way. alternatively, you could super cid and flash whatever you want.
I'm not able to supercid my phone it's stuck with the VIDEO001 CID... And in the stock recovery I had an error every time I pressed on the install zip from sd card and the phone just rebooted...
Go back to stock videotron GB via the exe file, make sure your bootloader is relocked and the device is in fastboot mode before you try to, after that, follow my guide on updating via the ota file, your bootloader will need to be locked.
duykhang524 said:
Hey, I flashed the latest Energy rom and I completely lost audio from my device, phone calls are muted aswell (mic+audio). Video are laggy or fastforwarded. Using fau123 kernel since my phone can`t boot when using stock kernel.
EDIT: I think I have an hypothesis concerning my problem. Do you guys think that when I flashed the rom the xml file with the audio profiles and video codecs got messed up or not flashed? I'm going to try to s-off and reflash using the bootloader. But the HTC Amaze has a different hardware configuration (the battery is not placed at the same place) than the T-Mobile one...
Click to expand...
Click to collapse
i have the exact same problem but im running speed rom 8.0
Related
So im on das bamf 2.0 with the mr2 radio flashed, i could load the rom and use my phone.But then i decided to unroot the phone, so i flashed the stock rom which worked before and took me back to being on stock and unrooted.But, now when i flashed it said Main Version is lower, in red letters. I now have no root with s-on as well. My phone wont boot because apparently one of the boot images i flashed didnt want to get unflashed. I cant do anything in the bootloader that wont end up with it rebooting the bootloader. I do not have usb debugging on because of the fact that i it FLASHED the pgio5mg or whatever it is that you call it, flashed = turning off usb debugging. Should i try to get a new one from big red? what if they get on to me and not give me a new phone thanks to it saying security warning?
Is there any way for me to be able to use my phone again, whether its getting rooting again or downloading an official gingerbread rom, if thats even out yet?
PLEASE HELP IM ONLY 2 MONTHS IN MY CONTRACT!
Also, at the top of bootloader it says SECURITY WARNING.
u have the wrong radio for the stock phone. u need the MR1 radio. since u still have the PG05IMG on your card it is stuck in boot loop. u need access to a card reader so u can remove that file. that will take care of the boot loop. then just install the MR1 radio.
also if u go to verizon as is, they will not honor your warranty.
lostnuke said:
u have the wrong radio for the stock phone. u need the MR1 radio. since u still have the PG05IMG on your card it is stuck in boot loop. u need access to a card reader so u can remove that file. that will take care of the boot loop. then just install the MR1 radio.
also if u go to verizon as is, they will not honor your warranty.
Click to expand...
Click to collapse
You just saved me from a life time of nightmares! But that didnt work, pio5mg or not im stuck in a fruit loop!
The first step after flashing pg05img.zip is to remove it from your sdcard.
Sent from my CM7 ThunderBolt using XDA Premium App
That didnt worrrrrrrk, i flashed the default froyo rom which is , like 23 MB, and it loaded it, but nothing happened it just returned me to bootloader menu!
As long as there is no file named pg05img.zip on the root of your sdcard, you can get into recovery from hboot. Are you able to get into recovery?
From what I understand, if you have the wrong radio for your ROM, the only side effect is that you'll have no signal from verizon. It sounds to me like you just need to reflash the ROM to get the phone to boot properly.
XxJakems28xX said:
That didnt worrrrrrrk, i flashed the default froyo rom which is , like 23 MB, and it loaded it, but nothing happened it just returned me to bootloader menu!
Click to expand...
Click to collapse
The default FroYo ROM and NO ROM for that matter is 23MB! Should be 300ishMB for Sense based ROMs.
Mustang302LX said:
The default FroYo ROM and NO ROM for that matter is 23MB! Should be 300ishMB for Sense based ROMs.
Click to expand...
Click to collapse
^^ what I was about to say.
The radios are close to 23MB but not the roms.
BTW, @OP, doesn't sound like you followed the directions when going back to stock as the security warning was one of the disclaimers.
http://forum.xda-developers.com/showthread.php?t=1009423
sorry i meant to say the defualt froyo radio is around 23 mb, i will try to flash this huge rom again, but now i have to wait like three hours cuz every time i try to flash the rom it says BATTERY VOLTAGE IS TOO LOW, and i cannot go to recovery it just takes me back to the hboot crap. I never read that tutortial guess i shouldve, i couldve sworn all you had to do was flash the defualt rom, DANG IT, i think that since i was on gingerbread this piece of shi doesnt want to flash the froyo rom, the fact that im now unrooted it doesnt want me to downgrade, god im never rooting again!
I rooted my phone by using the 3 click method by the unrevoked teem or whatever they are, i downgraded using the downgradepgoi5mg zip file found inside the folder, i dont know if that hepls but i hope it does.
I'm a little lost. Let me explain what just happened.
1st 3D was having reboots randomly and BSOD.. so I replaced it.
Picked up new 3D today.
It's Hboot 1.50.000 (oh noez)
I unlock via HTC method
(( Now with HTC's method it's my understanding that you can flash a custom recovery and roms, but you're locked on the Kernel that came with your phone and thus no aosp roms/kernels OR if you're trying to flash a sense rom but the rom has a higher kernel than the one on your phone - you're still up the creek))
After unlocking with HTC's method I promptly went into TWRP, wiped everything without a nand backup because if it screws up i'm using my upgrade lol. I then flashed Eternity 3.0 R39.. to my surprise it worked fine. I didn't test if I could OC.
I then rebooted into recovery through power button and then installed the current miui rom, immediately followed by the Anthrax AOSP kernel.. to my surprise I got no errors of any sort, booted up fast as hell, restored SetCPU and Oc'd to 1.8 just fine.. been going for about 15-20 minutes now just like normal.
I THOUGHT I WASN'T SUPPOSED TO BE ABLE TO DO THIS GUYS
saboture said:
I'm a little lost. Let me explain what just happened.
1st 3D was having reboots randomly and BSOD.. so I replaced it.
Picked up new 3D today.
It's Hboot 1.50.000 (oh noez)
I unlock via HTC method
(( Now with HTC's method it's my understanding that you can flash a custom recovery and roms, but you're locked on the Kernel that came with your phone and thus no aosp roms/kernels OR if you're trying to flash a sense rom but the rom has a higher kernel than the one on your phone - you're still up the creek))
After unlocking with HTC's method I promptly went into TWRP, wiped everything without a nand backup because if it screws up i'm using my upgrade lol. I then flashed Eternity 3.0 R39.. to my surprise it worked fine. I didn't test if I could OC.
I then rebooted into recovery through power button and then installed the current miui rom, immediately followed by the Anthrax AOSP kernel.. to my surprise I got no errors of any sort, booted up fast as hell, restored SetCPU and Oc'd to 1.8 just fine.. been going for about 15-20 minutes now just like normal.
I THOUGHT I WASN'T SUPPOSED TO BE ABLE TO DO THIS GUYS
Click to expand...
Click to collapse
I bet you got a refurb that someone previously rooted. If they used revolutionary then you retain S-off even on hboot 1.50 when the refurb facility repaired the device. Why don't you check if you're S-off?
It was S-On. That was the first thing I checked while walking out of the store. S-On 1.50.000
How strange. Hopefully people will keep coming to the thread and ask the right question. With the right question, the right answer will come to shed some light on what is special about your scenario.
Unfortunately that will not be me, because I have hboot 1.4, thus have less knowledge on the HTC unlock method.
Hopefully this has happened to someone else. I'm not sure why it happened. :O
saboture said:
I'm a little lost. Let me explain what just happened.
1st 3D was having reboots randomly and BSOD.. so I replaced it.
Picked up new 3D today.
It's Hboot 1.50.000 (oh noez)
I unlock via HTC method
(( Now with HTC's method it's my understanding that you can flash a custom recovery and roms, but you're locked on the Kernel that came with your phone and thus no aosp roms/kernels OR if you're trying to flash a sense rom but the rom has a higher kernel than the one on your phone - you're still up the creek))
After unlocking with HTC's method I promptly went into TWRP, wiped everything without a nand backup because if it screws up i'm using my upgrade lol. I then flashed Eternity 3.0 R39.. to my surprise it worked fine. I didn't test if I could OC.
I then rebooted into recovery through power button and then installed the current miui rom, immediately followed by the Anthrax AOSP kernel.. to my surprise I got no errors of any sort, booted up fast as hell, restored SetCPU and Oc'd to 1.8 just fine.. been going for about 15-20 minutes now just like normal.
I THOUGHT I WASN'T SUPPOSED TO BE ABLE TO DO THIS GUYS
Click to expand...
Click to collapse
umm i have hboot 1.50 unlocked htc method and i can flash any rom or kernal i want by just booting into recovery through fastboot its an extra step that takes about 10 seconds with a copy and paste of 2 commands from dos prompt
Yeah, I'm not sure why there's this myth that you can't flash kernels with 1.5, just need to load recovery in fastboot. Only limit I know of for 1.5 is that I can't use boot manager (if I'm wrong, let me know because I would love to use it). Either way, doesn't sound like OP was flashing through fastboot, which is odd.
Sent from my HTC Evo 3D using XDA App
saboture said:
After unlocking with HTC's method I promptly went into TWRP, wiped everything without a nand backup because if it screws up i'm using my upgrade lol. I then flashed Eternity 3.0 R39.. to my surprise it worked fine. I didn't test if I could OC.
I THOUGHT I WASN'T SUPPOSED TO BE ABLE TO DO THIS GUYS
Click to expand...
Click to collapse
Sounds like after unlocking with htc method you never disconnected your phone from PC and directly booted recovery from fastboot when you flashed TWRP .
So there's nothing new, i guess.
Every hboot1.50 user can flash kernels whether it is sense kernel or AOSP......
You can also use Flash image GUI to flash custom kernels from within the running android environment too.
So far JUST using HTC's unlock method I'm able to do the following
Flash custom roms through recovery like normal
Flash custom kernels through recovery like normal
Perform Nandroid backups/restores of EVERYTHING
UNABLE TO FLASH A CUSTOM SPLASH SCREEN
I thought this was going to be horrible going from a 1.40.000 device to 1.50.000 but honestly it's exactly like when I used Revolutionary to unlock my 1.40.000 device. And yes - I did leave my USB cable hooked up from start to finish. Hopefully other people will see this thread.
I tried Flash GUI and I couldn't get it to work for me so I guess I'm grateful. I'll check if I can install a splash screen once I post this and edit with the update.
saboture said:
I'm a little lost. Let me explain what just happened.
1st 3D was having reboots randomly and BSOD.. so I replaced it.
Picked up new 3D today.
It's Hboot 1.50.000 (oh noez)
I unlock via HTC method
(( Now with HTC's method it's my understanding that you can flash a custom recovery and roms, but you're locked on the Kernel that came with your phone and thus no aosp roms/kernels OR if you're trying to flash a sense rom but the rom has a higher kernel than the one on your phone - you're still up the creek))
After unlocking with HTC's method I promptly went into TWRP, wiped everything without a nand backup because if it screws up i'm using my upgrade lol. I then flashed Eternity 3.0 R39.. to my surprise it worked fine. I didn't test if I could OC.
I then rebooted into recovery through power button and then installed the current miui rom, immediately followed by the Anthrax AOSP kernel.. to my surprise I got no errors of any sort, booted up fast as hell, restored SetCPU and Oc'd to 1.8 just fine.. been going for about 15-20 minutes now just like normal.
I THOUGHT I WASN'T SUPPOSED TO BE ABLE TO DO THIS GUYS
Click to expand...
Click to collapse
You can flash kernels through fastboot. But you stated that you booted into recovery using power button, so it doesn't sound like you used fastboot....
You didn't use the flashimage GUI app, did you?
Sounds strange to me. Did you check the kernel In settings after you flashed? Don't think Its possible for stock kernel to support miui, but I suppose its possible.
Either way, you had something happen that shouldn't have. Either got a kernel to flash in a way that it shouldn't have, or got a rom to run on a kernel that shouldn't be compatible.
Another possible thing....I wonder if the 2.08.651.3 update did something that allows for you to flash kernels now. We know it wasn't possible on the .2 software, has anyone tried it with. 3. Doubt it made a difference as it was supposed to be a security update only.
Who knows. Ill give it a shot tomorrow to see if I can flash kernels without fastboot or flashimage GUI.
Sent from my PG86100 using XDA App
If you can flash a splash or radio then you should seek out a dev and let them know. They would probably have you do some tests. Might help achieve s off on 1.50
Sent from my PG86100 using XDA App
thos25 said:
You didn't use the flashimage GUI app, did you?
Click to expand...
Click to collapse
I tried it but when I booted into miui I got stuck at the boot screen. Miui boots in about 30 seconds or so on a fresh install but I was there for over 10 minutes.
Right now my phone is flashing Eternity 3.0 - R39 followed by Anthrax kernel. I'll let you guys know in a sec.
Edit: Well, the kernel flashed successfully but I'm freezing in the middle of the boot screen. Gonna try another kernel
Okay while booting Eternity 3.0 R39 I froze up mid boot screen. I remembered seeing a post about it freezing and I found it here and did what he said to do and it all works fine now. This is after I flashed rom+kernel in recovery then rebooted.
saboture said:
I tried it but when I booted into miui I got stuck at the boot screen. Miui boots in about 30 seconds or so on a fresh install but I was there for over 10 minutes.
Right now my phone is flashing Eternity 3.0 - R39 followed by Anthrax kernel. I'll let you guys know in a sec.
Edit: Well, the kernel flashed successfully but I'm freezing in the middle of the boot screen. Gonna try another kernel
Click to expand...
Click to collapse
Yeah. I have trouble with flashinage GUI as well. Funny thing is my issues with it were with miui as well.
Sent from my PG86100 using XDA App
saboture said:
Okay while booting Eternity 3.0 R39 I froze up mid boot screen. I remembered seeing a post about it freezing and I found it here and did what he said to do and it all works fine now. This is after I flashed rom+kernel in recovery then rebooted.
Click to expand...
Click to collapse
Good stuff. Did you check to see if you can flash radio or splash?
Sent from my PG86100 using XDA App
thos25 said:
Good stuff. Did you check to see if you can flash radio or splash?
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
I'm unable to flash a splash, and I've never flashed a radio before.
But as of right now I can flash kernels/recoveries/roms from TWRP. I'll try flashing a bootscreen with Rom Toolbox real quick just for extra measure.
Edit: can flash custom boot screens. One thing I cant seem to do though is take screenshots with screenshot it. When it saves it's always corrupted and wont let me transfer the screenshot to anything.
From what I gather, the questions you have answered still haven't shed any light as to whether your phone is behaving in a matter that is the same anyone else in your situation would experience? If it is still in fact behaving different than what we would expect it to I think the suggestion given to you to contact a Dev would be best. You may end up and be able to help the community achieve a more comprehensive solution to the root process.
Sad Panda said:
From what I gather, the questions you have answered still haven't shed any light as to whether your phone is behaving in a matter that is the same anyone else in your situation would experience? If it is still in fact behaving different than what we would expect it to I think the suggestion given to you to contact a Dev would be best. You may end up and be able to help the community achieve a more comprehensive solution to the root process.
Click to expand...
Click to collapse
Yeah, I was thinking the same thing.
Sent from my HTC Evo 3D using XDA App
could it be possible htc updated their unlock process to allow access to the boot.img without using fastboot?
ok. so I finally got around to trying to flash a kernel without using fastboot to see if it would work.
It did not. Like others have reported, it will say that the flash is successful, but when I go into the "about phone" menu, it did not change.
I have CM7 (secretpartymeow) on it now with stock (as in whatever kernel came with the ROM) kernel. Tried flashing infected Anthrax (aosp). No luck.
It is indeed looking more and more like your phone is a bit of an anomoly. I would suggest contacting one of the devs over at TeamWin to let them know what you are able to do.
I've had bluetooth streaming problems with EVERY ICS custom ROM that I've tried before and after 3.11.605.22, and while on the stock RUU itself. I want to get back to a GBE based ROM, on stock firmware but I wonder how it's going to work after having flashed the 3.11.605.22 RUU.
Has anyone gone back? Is it even possible to get back to the previous firmware, or am I SOL?
I assume that a simple nandroid restore is now out of the question (and probably won't fix the bluetooth problem) given the firmware changes with the RUU
nukeboyt said:
I've had bluetooth streaming problems with EVERY ICS custom ROM that I've tried before and after 3.11.605.22, and while on the stock RUU itself. I want to get back to a GBE based ROM, on stock firmware but I wonder how it's going to work after having flashed the 3.11.605.22 RUU.
Has anyone gone back? Is it even possible to get back to the previous firmware, or am I SOL?
I assume that a simple nandroid restore is now out of the question (and probably won't fix the bluetooth problem) given the firmware changes with the RUU
Click to expand...
Click to collapse
it actually is just that simple, flash your GB nandroid and/or ROM the GB kernel.
you will need to flash this file after flashing back to your nandroid/ROM in order for rom to see SD card.. same fix was applied with old firmware to have sd seen on ics roms. its just doing the reverse.
http://www.mediafire.com/?3b1t2y9i11onm41
andybones said:
it actually is just that simple, flash your GB nandroid and/or ROM the GB kernel.
you will need to flash this file after flashing back to your nandroid/ROM in order for rom to see SD card.. same fix was applied with old firmware to have sd seen on ics roms. its just doing the reverse.
http://www.mediafire.com/?3b1t2y9i11onm41
Click to expand...
Click to collapse
Similar situation. Completely unacceptable power draw is frying my battery on the leak. I'm afraid I'm going to cook my phone, and USB charge can't keep up with the drain unless I put it in airplane mode. I have good nandroid backups of the current OTA release (released February, I think?) but I don't know where to get suitable GB kernel or how to install it. Can you explain?
andybones said:
it actually is just that simple, flash your GB nandroid and/or ROM the GB kernel.
you will need to flash this file after flashing back to your nandroid/ROM in order for rom to see SD card.. same fix was applied with old firmware to have sd seen on ics roms. its just doing the reverse.
http://www.mediafire.com/?3b1t2y9i11onm41
Click to expand...
Click to collapse
Thanks. I'll have to give it a try. So you say I should flash a previous backup / ROM from recovery, then flash the kernel (if it doesn't flash as a part of the ROM installation)
nukeboyt said:
Thanks. I'll have to give it a try. So you say I should flash a previous backup / ROM from recovery, then flash the kernel (if it doesn't flash as a part of the ROM installation)
Click to expand...
Click to collapse
yea do the exact same thing you would do as if you are on still on the old firmware.
the ONLY thing you do differently, is flash the .zip file I attached in my other post anything AFTER flashing the new GB ROM/ and/or old backup.. and kernel(in hboot) if not included in ROM.
I installed the CLEANrom tapped edition rom after wiping everything as instructed. It boots and initially I had issues with wifi working, but that seems to be working after flashing a stock kernel. Now if I try to play anything with sound or change the volume using rockers or in the phone itself it forces a reboot.
Any ideas?
Thanks
You are probably on old firmware and need to flash the patch
http://www.myandroidfiles.com/Downloads/Rezound/3.14.605.5/GB%20Firmware%20Patch.zip
Sent from my Rezound
Still having issues
Thanks for the reply. I actually ended up flashing it back to the rom that I had. I also made sure I flashed it to the original recovery as well which is amon ra. The rom I flashed it back to was the clean rom standard 4.4.
Unfortunately, I'm having the same problem no. If I go into the dialer and hit a number it freezes and force reboots. If I hit the volume rocker, it freezes and force reboots. It just force reboots for almost everything except for texting and going into apps.
any thoughts? The 4.4 worked fine on the firmware that's on here, and I did do the wipe and reset before I installed back. Maybe I bricked it?
Definitely not bricked. You wouldn't be able to even boot if bricked. What firmware are you on?
Here is some information
CleanROM standard 4.4
htc sense version 3.6
android version 4.0.3
kernel 3.0.16
I think the hboot was 2.11 or something like that.
Yeah, I figured it's not totally bricked. It should be on ICS. The issues started when I removed my old rom and put on this tapped edition clean rom which was listed as a good rom to use in the rezounds rom options. Kinda stupid that it would create this whole mess if it actually was a working rom. Maybe it shouldn't be listed... lol
Mr. Lando said:
CleanROM standard 4.4
htc sense version 3.6
android version 4.0.3
kernel 3.0.16
I think the hboot was 2.11 or something like that.
Yeah, I figured it's not totally bricked. It should be on ICS. The issues started when I removed my old rom and put on this tapped edition clean rom which was listed as a good rom to use in the rezounds rom options. Kinda stupid that it would create this whole mess if it actually was a working rom. Maybe it shouldn't be listed... lol
Click to expand...
Click to collapse
Even though your on ics, it looks like your on gb firmware. Search for the gb patch for ics and flash in recovery and problem solved
2.11 hboot is gb firmware, 2.21 or up is ics firmware
Mr. Lando said:
The issues started when I removed my old rom and put on this tapped edition clean rom which was listed as a good rom to use in the rezounds rom options. Kinda stupid that it would create this whole mess if it actually was a working rom. Maybe it shouldn't be listed... lol
Click to expand...
Click to collapse
It runs just great on the correct firmware lulz
Correct Process for Updating firmware
Hello,
You stated that 2.11 in the hboot indicates gb firmware. Do you know a link to the correct thread that would give me the appropriate process for updating the FW one that will work with the CLEANrom 1.4 dev version? I got the wifi working again after flashing the "old firmware patch" and then reloading CLEANrom 4.4 everything went back to normal. However, I hate sense and I would like something without it which is what the dev version provides, but if I cannot get wifi working then it's kind of useless. When I say "if I cannot get wifi working" what I am indicating is that when I try to run the cleanrom dev version 1.4 WIFI gets stuck on "turning on" but never turns on and eventually just says "error" with no further details. I searched through forum feeds and found a few forums that hinted on steps, but many people have seemed to be confused by this issue in the past and perhaps it is related to firmware as you said.
Thanks
i would wipe everything again, reflash the rom, and then immediately the patch. that should fix everything. key thing is flash the patch before booting the rom. ive flashed the patch after rebooting before and had things go haywire. not a promise that it will work, just letting you know what ive run into
Scosler has everything listed in the op for the rom, and all files are there as well. There's a bunch of different instructions for however your phone is set up.
Sent from my Rezound
Continuing...
Hi,
Not to sound like a total idiot here, and I probably do, but you had mentioned I should update the firmware so that hboot indicates 2.21 or higher. Is there an easy process for this or a thread I can turn to so that I can be sure it's updated. I believe I already did the step you mentioned.
I wiped/reset ----> flashed the 1.4 rom ----> ran the PH98IMG.zip----> then boot ----> then no PROFIT. wifi will not work. Maybe it's firmware after all. I don't know how I ended up on gb, I had a friend walk me through this the first time and I'm pretty technical. I used the automated tool by that one guy to flash the amonra recovery and I thought that was 2.21 or higher, but maybe I'm wrong.
If s on and on 2.11 hboot Method 4:
-Copy ROM to SD Card AND PH98IMG.zip AND GB Firmware Patch to ROOT of SD Card
-Reboot to recovery
-wipe data / Factory Reset
-Flash ROM
-Flash GB Fimrware Patch
-Use Developer Menu to reboot to bootloader and flash the boot.img file in the PH98IMG.zip
-Reboot
-Profit!
Based on what you typed you didn't flash the firmware fix...
Mr. Lando said:
Hi,
Not to sound like a total idiot here, and I probably do, but you had mentioned I should update the firmware so that hboot indicates 2.21 or higher. Is there an easy process for this or a thread I can turn to so that I can be sure it's updated. I believe I already did the step you mentioned.
I wiped/reset ----> flashed the 1.4 rom ----> ran the PH98IMG.zip----> then boot ----> then no PROFIT. wifi will not work. Maybe it's firmware after all. I don't know how I ended up on gb, I had a friend walk me through this the first time and I'm pretty technical. I used the automated tool by that one guy to flash the amonra recovery and I thought that was 2.21 or higher, but maybe I'm wrong.
Click to expand...
Click to collapse
If i were you i would either s-off or flash one of the ics leak ruu's. that will help. there are many ways to solve your problem but those are your best bets
My issue is resolved. Thanks for all of your help and insight.
Sent from my ADR6425LVW using XDA
Care to share what you did? I am having exact same issue . . .
nvm - resolved: applied GB Patch right after ICS ROM flash (who would have known - I was kind of ignoring those GB patch instructions, since they did not apply to ICS).
Looking for a compatible rom for an htc one m7wls (sprint) running twrp 2.6.3 I have tried several and cant seem to find any that are compatible. Secondly do I have to flash the unzipped boot.img file that's with the rom after I flash the rom? I have tried viper, beanstalk, android revolution and cant seem to find any to get my phone back up and working again, it has no os on it at the moment. Thanks for all your help any suggestions and help would be awesome
Tommyboy77 said:
Looking for a compatible rom for an htc one m7wls (sprint) running twrp 2.6.3 I have tried several and cant seem to find any that are compatible. Secondly do I have to flash the unzipped boot.img file that's with the rom after I flash the rom? I have tried viper, beanstalk, android revolution and cant seem to find any to get my phone back up and working again, it has no os on it at the moment. Thanks for all your help any suggestions and help would be awesome
Click to expand...
Click to collapse
Unless you are S-Off (not just HTC Dev unlocked) then you will need to fastboot flash the boot.img in fastboot mode as well. Any of those roms should work fine if installed correctly. Just make sure that you have the appropriate firmware installed as well to make sure that the touch and other functions work properly. This means if you're original stock system was 4.2.2 and you are installing a 4.3 or 4.4.2 rom (at least Sense based) then you will need to install the firmware package as well for that update. How you install that depends on S-Off or HTC Dev unlocked, I believe.
hello
es0tericcha0s said:
Unless you are S-Off (not just HTC Dev unlocked) then you will need to fastboot flash the boot.img in fastboot mode as well. Any of those roms should work fine if installed correctly. Just make sure that you have the appropriate firmware installed as well to make sure that the touch and other functions work properly. This means if you're original stock system was 4.2.2 and you are installing a 4.3 or 4.4.2 rom (at least Sense based) then you will need to install the firmware package as well for that update. How you install that depends on S-Off or HTC Dev unlocked, I believe.
Click to expand...
Click to collapse
Well I installed the ecliptic custom rom and it installed correctly however I can not text or use the phone features just wifi works.....I accidentally erased the os before I put the custom rom on.....could you help me figure out how to know what sprint stock rom I can go back to stock on ? I was told in order to get my calling and text features back I need to reload a sprint stock rom then go back to a custom rom if I wished however I just need to know what sprint stock rom I can use. thanks for all your help
es0tericcha0s said:
Unless you are S-Off (not just HTC Dev unlocked) then you will need to fastboot flash the boot.img in fastboot mode as well. Any of those roms should work fine if installed correctly. Just make sure that you have the appropriate firmware installed as well to make sure that the touch and other functions work properly. This means if you're original stock system was 4.2.2 and you are installing a 4.3 or 4.4.2 rom (at least Sense based) then you will need to install the firmware package as well for that update. How you install that depends on S-Off or HTC Dev unlocked, I believe.
Click to expand...
Click to collapse
If you could please send me a link to the correct sprint m7wls sprint stock rom I can use to get back to root to get phone working that woujld be awesome....so after adb pushing the zip to my internal sed card I can use twrp to install it I take it? then flash the included boot .img with the rom after flashing the rom to get it to work correct right?? just want to make sure im doing the right thing instead of going in circles.
Tommyboy77 said:
Well I installed the ecliptic custom rom and it installed correctly however I can not text or use the phone features just wifi works.....I accidentally erased the os before I put the custom rom on.....could you help me figure out how to know what sprint stock rom I can go back to stock on ? I was told in order to get my calling and text features back I need to reload a sprint stock rom then go back to a custom rom if I wished however I just need to know what sprint stock rom I can use. thanks for all your help
Click to expand...
Click to collapse
Weird that that one isn't working, but just shoot for a regular Sprint based custom rom like Bad Boyz and you should be fine. What was your previous firmware/OS before you wiped it? Which baseband are you using? Which version of the rom are you trying to use now? What recovery are you using? What happens when you try to make a call or text - error code or message? But either way, if you load a regular or custom Sprint based rom and update your PRL and Profile, then you should be fine to switch back to another rom, if wanted. This is why it's always good to both make a nandroid, and to save it in a save space, if needed, for times like this.
---------- Post added at 01:05 PM ---------- Previous post was at 12:53 PM ----------
Tommyboy77 said:
If you could please send me a link to the correct sprint m7wls sprint stock rom I can use to get back to root to get phone working that woujld be awesome....so after adb pushing the zip to my internal sed card I can use twrp to install it I take it? then flash the included boot .img with the rom after flashing the rom to get it to work correct right?? just want to make sure im doing the right thing instead of going in circles.
Click to expand...
Click to collapse
You are correct about adb pushing the zip to internal, flashing, then fastboot flashing the boot.img to finish. I can't make a suggestion of which rom to use without knowing what you were using before though so everything will match up and work properly (firmware, baseband, OS, etc).
Hello
es0tericcha0s said:
Weird that that one isn't working, but just shoot for a regular Sprint based custom rom like Bad Boyz and you should be fine. What was your previous firmware/OS before you wiped it? Which baseband are you using? Which version of the rom are you trying to use now? What recovery are you using? What happens when you try to make a call or text - error code or message? But either way, if you load a regular or custom Sprint based rom and update your PRL and Profile, then you should be fine to switch back to another rom, if wanted. This is why it's always good to both make a nandroid, and to save it in a save space, if needed, for times like this.
---------- Post added at 01:05 PM ---------- Previous post was at 12:53 PM ----------
You are correct about adb pushing the zip to internal, flashing, then fastboot flashing the boot.img to finish. I can't make a suggestion of which rom to use without knowing what you were using before though so everything will match up and work properly (firmware, baseband, OS, etc).
Click to expand...
Click to collapse
Well I tried installing bad boyz 5514 and the old version 5512.....then I flash the boot img.....it installs fine however when it gets to unlock the screen it sneds me in a reboot...happened for both versions any ideas whats wrong?
Tommyboy77 said:
Well I tried installing bad boyz 5514 and the old version 5512.....then I flash the boot img.....it installs fine however when it gets to unlock the screen it sneds me in a reboot...happened for both versions any ideas whats wrong?
Click to expand...
Click to collapse
Might need to do another factory reset. But I've already said repeatedly that it is important to know what the original firmware / software was on the phone before it started having issues and its because of troubleshooting issues like this as well as it is just important on most HTC phones to have these things matching properly between the firmware and OS as well as the radio.
hello
es0tericcha0s said:
Might need to do another factory reset. But I've already said repeatedly that it is important to know what the original firmware / software was on the phone before it started having issues and its because of troubleshooting issues like this as well as it is just important on most HTC phones to have these things matching properly between the firmware and OS as well as the radio.
Click to expand...
Click to collapse
I completely erased my entire phone including the os and don't know what firmware software was on the phone to begin with was stock sprint....so I don't know what firmware was on there or os or radio
Tommyboy77 said:
I completely erased my entire phone including the os and don't know what firmware software was on the phone to begin with was stock sprint....so I don't know what firmware was on there or os or radio
Click to expand...
Click to collapse
Then it is recommended to run the newest RUU to make sure your partitions, OS, radio, and firmware are all properly matched. Once that happens, you can just fastboot flash a recovery back and then redo whatever 4.4 rom you want at that stage. Yea, it sucks to have to do the extra steps, but some things you just have to do to make sure everything works properly. It never pays to cut corners when you need your phone to function correctly.
http://forum.xda-developers.com/showthread.php?t=2658910