Ok, I screwed up....
Flashed the New ICS leak after relocking bootloader via PH
I was on a custom ROM and the flash failed miserably.
My phone will only boot into the bootloader and it shows Tampered and Relocked
I tried reflashing the last RUU in PH format and get an error saying Hboot version is older.
Anyone know how to get this phone to boot? Not how I wanted to start my Sat. morning at all.......
Wondering if someone can repack the latest RUU into a zip with a modified main version? I can only flash through fastboot and cannot Unlock the bootloader.
Scott has a tutorial for getting through this in the OP of ICS 4.0 Clean ROM
I'd think you would first want to unlock again. Then bootloader to recovery and restore the backup you made before trying to flash.
Got it unlocked again. I had to generate another Unlock code, my screw up somehow killed the original.
Issue resolved
Irieone said:
Got it unlocked again.
Click to expand...
Click to collapse
you need to chose factory reset , the first time after flashing a custom recovery then you can reboot into recovery after that. At least that was the experience of a few of us.
I'm back in business, but permanently branded. ( I think)
My bootloader still reads ***TAMPERED*** at the top. If anyone knows how to clear this, please let me know...
Irieone said:
I'm back in business, but permanently branded. ( I think)
My bootloader still reads ***TAMPERED*** at the top. If anyone knows how to clear this, please let me know...
Click to expand...
Click to collapse
from my reading last night it seems that this will go away once having the stock recovery back on the device, it only shows with a custom (amon ra, CWM) recovery.
andybones said:
from my reading last night it seems that this will go away once having the stock recovery back on the device, it only shows with a custom (amon ra, CWM) recovery.
Click to expand...
Click to collapse
Hmmm, it never said that until I botched flashing the new ICS leak. I spend a lot of time in the bootloader and never once saw it say tampered.
Irieone said:
Hmmm, it never said that until I botched flashing the new ICS leak. I spend a lot of time in the bootloader and never once saw it say tampered.
Click to expand...
Click to collapse
well that is because I am assuming you never installed a leaked firmware before...
you tampered with your bootloader, lol, so I guess it's letting you know.
I'm sure when I upgrade to the leak I'll have it too. not worried about it personally.
so installing the leak makes your bootloader say tampered? im sorta glad i held off on installing for right now.
Ok, I thought things were cool and they are not. I have my phone up and running. I was able to restore a backup I had...
Here is the catch tho, my phone will not read/access internal or external storage at all. My recovery will read storage
What to do now?
Irieone said:
Ok, I thought things were cool and they are not. I have my phone up and running. I was able to restore a backup I had...
Here is the catch tho, my phone will not read/access internal or external storage at all. My recovery will read storage
What to do now?
Click to expand...
Click to collapse
You can't restore backups on the new firmware.. I spent 6 hours last night into this morning figuring that out the hard way...Did you make a backup of the stock rom after you ran the RUU ? If so then just flash your backup and realize you have to wait for the roms to get updated. If you didn't the only way I can think of is to relock and rerun the RUU and don't restore backups.
Ouch, I don't have a backup of the stock rom.
Do you have a link to the last RUU? The link is dead in football's thread.
Wonder if I can flash Scott's new 4.0 ROM? I think I will try that...
[[/URL]
Irieone said:
Ouch, I don't have a backup of the stock rom.
Do you have a link to the last RUU? The link is dead in football's thread.
Click to expand...
Click to collapse
here is the one I downloadedhttp://lts.cr/Be5_ for the latest RUU. Unfortunately, once you flashed the new RUU you can't go back with the last RUU. The new one upgraded the hboot and I don't think you can downgrade.
you just need to rerun the same RUU you just did that is all and just wait for the rom you like to be updated.. most devs already have one in the works or out already
---------- Post added at 11:16 AM ---------- Previous post was at 11:02 AM ----------
Irieone said:
Ouch, I don't have a backup of the stock rom.
Do you have a link to the last RUU? The link is dead in football's thread.
Wonder if I can flash Scott's new 4.0 ROM? I think I will try that...
Click to expand...
Click to collapse
Good idea Scott's should work just fine .. just mount usb in recovery in order to get the Rom on the SD card .
Did you flash the RUU twice? That worked for me.
From here. http://forum.xda-developers.com/showthread.php?t=1550358 on your root sdcard rename the zip and flash it twice.
Scott's ROM keeps crashing and the phone reboots..
I will try flashing the RUU zip file again I guess..
You relocked the phone and change the file to PH98IMG correct?
My bootloader looked normal after the second flash. but then said tampered once i flashed a recovery.
Flyhalf205 said:
My bootloader looked normal after the second flash. but then said tampered once i flashed a recovery.
Click to expand...
Click to collapse
Were you on a custom ROM when your flashed?
Irieone said:
Were you on a custom ROM when your flashed?
Click to expand...
Click to collapse
At the time yes. Probably why I flashed it twice. But the RUU is used in HBOOT so it shouldn't have mattered if there is a custom recovery at the time.
Ok, I am doing this now
Irieone said:
Ok, I thought things were cool and they are not. I have my phone up and running. I was able to restore a backup I had...
Here is the catch tho, my phone will not read/access internal or external storage at all. My recovery will read storage
What to do now?
Click to expand...
Click to collapse
There is a zip floating around from Scott that you need to flash for your SD card. Check the development area
Related
I asked this in another thread but didnt get an answer...
This morning, I checked my system updates and got the OTA for ICS. It downloaded fine, and I hit install now. My phone powered off like it should have, and when it came back on my screen has has a weird green X in the middle of the screen. Is this normal? should I keep waiting? I didnt think it should have takin this long, and Ive never seen this weird X before...can someone please help...
Are you rooted/Bootloader unlocked?
Dark Nightmare said:
Are you rooted/Bootloader unlocked?
Click to expand...
Click to collapse
yes, both actually. Ive never flashed any roms or anything though, just stuck with the stock cuz I was scared to mess things up...lol
Unroot, restore stock recovery then relock the bootloader, then try again. It won't allow the update with an unlocked bootloader.
Dark Nightmare said:
Unroot, restore stock recovery then relock the bootloader, then try again. It won't allow the update with an unlocked bootloader.
Click to expand...
Click to collapse
To be completely honest, I have NO IDEA how to do that. I had Binery walk me through the rooting process, and I dont know how to restore it..
papeshfoo said:
To be completely honest, I have NO IDEA how to do that. I had Binery walk me through the rooting process, and I dont know how to restore it..
Click to expand...
Click to collapse
Use the Amaze toolkit, it has everything as a button, do it in this order and you should be fineL
1. restore stock recovery
2. relock the bootloader (oem_relock)
3. retry updating.
Dark Nightmare said:
Use the Amaze toolkit, it has everything as a button, do it in this order and you should be fineL
1. restore stock recovery
2. relock the bootloader (oem_relock)
3. retry updating.
Click to expand...
Click to collapse
thanks, one more question, where do I get the toolkit?
Here ya go: http://forum.xda-developers.com/showthread.php?t=1493905
Dark Nightmare said:
Here ya go: http://forum.xda-developers.com/showthread.php?t=1493905
Click to expand...
Click to collapse
thank you sir...
Welcome buddy ^_^
Hey Dark, I flashed the stock recovery, relocked the bootloader, ran the update again and now I get a phone pic with a red triangle and exclamation mark...any ideas?
Download one of the GB stock RUU files, rename it and place it on your external sd card and reboot into HBoot, it should automatically detect the file and take your entire phone back to complete stock, there shouldn't be any stops from updating.
Stock RUU thread: http://forum.xda-developers.com/showthread.php?t=1617644
rename the file to PH85IMG.zip when you place in on your sd card.
Dark Nightmare said:
Unroot, restore stock recovery then relock the bootloader, then try again. It won't allow the update with an unlocked bootloader.
Click to expand...
Click to collapse
As I posted in another thread, I have an unlocked bootloader with no other mods done, and I flashed the OTA without a problem.
great, I dont have and SD card...lol
Awe man, what's not stock on your current set up? Maybe we can just restore files. Don't you have a nandroid backup?
Dark Nightmare said:
Awe man, what's not stock on your current set up? Maybe we can just restore files. Don't you have a nandroid backup?
Click to expand...
Click to collapse
well, when I unlocked my bootloader I used the HTC site, then I had Binery help me with root. he came up with a one-click root while we were doing it. After that I haven't done anything else to it besides get rid of the bloat cuz that's the only reason I wanted root.
Everything should be fine then, stock recovery, stock rom, locked bootloader, tried re-downloading the update?
Dark Nightmare said:
Everything should be fine then, stock recovery, stock rom, locked bootloader, tried re-downloading the update?
Click to expand...
Click to collapse
I just did a factory reset, re-downloaded the update, Im about to try the install now. I did notice one thing though when I was using Hasoon, I think it said Failed when I flashed the stock recovery...
Yep, The update failed to install again.
What radio is on the new OTA update? Can someone who has done the update, post?
No clue where recovery files go on the amaze or we could do it via recovery, just retry flashing stock recovery, if not we'll have to wait until someone pulls the file and makes a zip file to flash it, did you try flashing the recovery using the tool while the phone was in fastboot? That's probably a requirement.
Hey folks..so I want to start flashing kernels and yes I know I probably should have gone s-off way sooner but I want to do it now. I've been rooting and romming my phones for a while but this whole s-off procedure continued to scare the crap out of me. But..I don't want to limit my choices when it comes to roms and kernels so I guess I'll do it anyway.
However, I am currently running RUU 4.03.605.2 with Vigor360 1.1 s modified kernel.
Can I still go s-off even though I am now running the global leak (or is it now impossible) and if so, can someone point me in the right direction?
Thank you kind gents n ladies!
I've heard of several people being successful on 4.03.605.2 with the 3.14.605.5 ControlBear version.
Only other advice I can offer is don't give up, try different wires if you're having trouble, and pay attention to the troubleshooting page if you decide you want back out and try again later. I've S-OFF'ed three Rezounds. The first took 3 days, the second 2 minutes, and the third 30 minutes.
dplane said:
Hey folks..so I want to start flashing kernels and yes I know I probably should have gone s-off way sooner but I want to do it now. I've been rooting and romming my phones for a while but this whole s-off procedure continued to scare the crap out of me. But..I don't want to limit my choices when it comes to roms and kernels so I guess I'll do it anyway.
However, I am currently running RUU 4.03.605.2 with Vigor360 1.1 s modified kernel.
Can I still go s-off even though I am now running the global leak (or is it now impossible) and if so, can someone point me in the right direction?
Thank you kind gents n ladies!
Click to expand...
Click to collapse
i did s-off with viper's rom and the .5. i was on global too, don't let it scare you or you will not get it. i couldn't get the timing for the life of me. first two hours was a hassle, then i had to get my other battery(thought i bricked my phone) then i relized that they had a metrnome with the correct timing and it worked the first time. but use a different memory card. all of these things can be found under the s-off instructions.:good:
its really easy man you can do it. i reccemend using speaker wire as its more pliable than a paperclip.. if you need help i can walk you thru it on gtalk. just pm me for me gtalk. otherwise. goodluck and yes the 3.14.605.5 ControlBear version is the correct one just lock your bootloader, run the full ruu agan( 4.03.605.2), flash amonRA, then flash this in recovery (https://docs.google.com/file/d/0B0ZJtM40GdJ0MEpGeG1ZWi0yNDA/edit) to gain root on stock global, download root checker from the app store to be sure you got root before you begin. then boot phone and check usb debugging, connect your phone to the comp(within the stock rom), start control bear.. make sure to back up EVERYTHING as it could all get wiped. (internal sd, external sd, and your nandroid if you so choose) i reccemend using a spare sd card if you have one.. ive only done my phone but it took me all of 2 trys.. i got weird errors a couple times (other than "error: still sober" got that once) if you do just run control bear again
Thanks for the responses and moral support folks!
Collin, I may have to hit you up for that assistance soon, I'd rather be safe then sorry so I might feel better if I have someone to "hold my hand"
May not get around to it til Sat afternoon or Sunday though.
famouscollin said:
its really easy man you can do it. i reccemend using speaker wire as its more pliable than a paperclip.. if you need help i can walk you thru it on gtalk. just pm me for me gtalk. otherwise. goodluck and yes the 3.14.605.5 ControlBear version is the correct one just lock your bootloader, run the full ruu agan( 4.03.605.2), flash amonRA, then flash this in recovery (https://docs.google.com/file/d/0B0ZJtM40GdJ0MEpGeG1ZWi0yNDA/edit) to gain root on stock global, download root checker from the app store to be sure you got root before you begin. then boot phone and check usb debugging, connect your phone to the comp(within the stock rom), start control bear.. make sure to back up EVERYTHING as it could all get wiped. (internal sd, external sd, and your nandroid if you so choose) i reccemend using a spare sd card if you have one.. ive only done my phone but it took me all of 2 trys.. i got weird errors a couple times (other than "error: still sober" got that once) if you do just run control bear again
Click to expand...
Click to collapse
I'm working with the same situation as the OP. You posted a link to a second recovery to flash after Amon Ra, I've tried that link and it forces me to request access. Which recovery is it and is there another link or are you able to give me access to that one?
Hey guys.
I am a complete newb with most this stuff.
I am not sure how I look at RUU I have. I will say that my phone was pretty much stock through the official ICS release.
Currently I have CM9 flashed as my rom.
Is there anyway I can S-OFF my phone?
Sax1031 said:
Hey guys.
I am a complete newb with most this stuff.
I am not sure how I look at RUU I have. I will say that my phone was pretty much stock through the official ICS release.
Currently I have CM9 flashed as my rom.
Is there anyway I can S-OFF my phone?
Click to expand...
Click to collapse
If you haven't already, I would say start by checking out unlimited.io They have all the basic details about how to achieve S-OFF. Without knowing more specifics about your setup it would be hard someone to give a more specific answer.
neowisdom1031 said:
If you haven't already, I would say start by checking out unlimited.io They have all the basic details about how to achieve S-OFF. Without knowing more specifics about your setup it would be hard someone to give a more specific answer.
Click to expand...
Click to collapse
Yea I have went there.
I have the program downloaded. I am on Gray's CM9 rom.
Followed all the instructions. When the program runs it goes like this:
Starting up....
Connecting to device....
Searching device.....
Found device......
Backing up.....
Permission denied.....
Transferring backups....
Secondary backup FAILED!!
Press ENTER to exit.
like I said my phone was stock till the official ICS update released. After that I unlocked the boot loader and just recently flashed my first rom, through Amon Ra.
If I could kindly ask you what info you need, and possibly how to access the info, to help me out. Do I need to flash a stock rom back?
---------- Post added at 08:27 PM ---------- Previous post was at 07:29 PM ----------
I hope to god my hboot was stock. As I am running a previous RUU.
Hopefully once I do this, I will be able to S-OFF.
Sax1031 said:
Yea I have went there.
I have the program downloaded. I am on Gray's CM9 rom.
Followed all the instructions. When the program runs it goes like this:
Starting up....
Connecting to device....
Searching device.....
Found device......
Backing up.....
Permission denied.....
Transferring backups....
Secondary backup FAILED!!
Press ENTER to exit.
like I said my phone was stock till the official ICS update released. After that I unlocked the boot loader and just recently flashed my first rom, through Amon Ra.
If I could kindly ask you what info you need, and possibly how to access the info, to help me out. Do I need to flash a stock rom back?
---------- Post added at 08:27 PM ---------- Previous post was at 07:29 PM ----------
I hope to god my hboot was stock. As I am running a previous RUU.
Hopefully once I do this, I will be able to S-OFF.
Click to expand...
Click to collapse
If you're able to flash back to stock that would be the best place to start for S-OFF
neowisdom1031 said:
If you're able to flash back to stock that would be the best place to start for S-OFF
Click to expand...
Click to collapse
I flashed back to the first ICS RUU.
I think I know why it said permission denied. Because I didn't have actual root access.
At the point of trying the wire trick.
Edit: Achieved S-OFF. Thanks so much guys. Going from 3 days ago of flashing my first rom. To having to relock the device, run the first ICS Ruu, then doing the wire trick. Hell of a learning curve on these things. Thanks everyone for all the help.
Just a quick update. I was able to achieve S-Off while using this specific RUU. It took a few time flashing the RUU and a rooted rom to finally get it but it is possible with this RUU.
neowisdom1031 said:
Just a quick update. I was able to achieve S-Off while using this specific RUU. It took a few time flashing the RUU and a rooted rom to finally get it but it is possible with this RUU.
Click to expand...
Click to collapse
Fwiw I also was able to go s-off using this ruu and flashing supersu from a temporary amon ra. Not as tough as it thought.
Sent from my ADR6425LVW using xda app-developers app
.
Did you put the Juopunutbear executable and files into the same folder
that Android fastboot, adb, and other files are located?
michaelbsheldon said:
Did you put the Juopunutbear executable and files into the same folder
that Android fastboot, adb, and other files are located?
Click to expand...
Click to collapse
It shouldn't matter. ControlBear has its own versions of everything it needs.
Sent from my HTC Rezound using Tapatalk 2
So this is what i've done and its failing with the error: "Secondary backup FAILED!!"
-I reset everything by using the RUU 4.03.605.2.
-I then set the debugging mode, unlocked the bootloader
-Put AmonRa3.15 as my recovery
-Flashed the CWM SuperSU.
-Confirmed root access by using TitaniumBackup.
-Started the ControlBearRelease_vigor_ICS_3.14.605.5 for the ICS leak process.
-Then I get the fun error Secondary backup FAILED!!.
I'm using the latest version of JuopunutBear 0.4. Help?
-------------update---------------
So I re-flashed the full RUU and went through all the steps and still same outcome. "Secondary backup Failed!". I read that only version .1 may work if this error occurs?
=-\
Izeltokatl said:
So this is what i've done and its failing with the error: "Secondary backup FAILED!!"
-I reset everything by using the RUU 4.03.605.2.
-I then set the debugging mode, unlocked the bootloader
-Put AmonRa3.15 as my recovery
-Flashed the CWM SuperSU.
-Confirmed root access by using TitaniumBackup.
-Started the ControlBearRelease_vigor_ICS_3.14.605.5 for the ICS leak process.
-Then I get the fun error Secondary backup FAILED!!.
I'm using the latest version of JuopunutBear 0.4. Help?
-------------update---------------
So I re-flashed the full RUU and went through all the steps and still same outcome. "Secondary backup Failed!". I read that only version .1 may work if this error occurs?
=-\
Click to expand...
Click to collapse
i s-offed with the global ruu and and this version of control bear https://docs.google.com/file/d/0B0ZJtM40GdJ0SmVBbm40anJpRTg/edit ia got a few wierd errors but just started it up again and all went well..also make sure you have htc sync uninstalled from your computer
famouscollin said:
i s-offed with the global ruu and and this version of control bear https://docs.google.com/file/d/0B0ZJtM40GdJ0SmVBbm40anJpRTg/edit ia got a few wierd errors but just started it up again and all went well..also make sure you have htc sync uninstalled from your computer
Click to expand...
Click to collapse
Ya that's the exact same version I have, not really sure what to do? I re-did everything back to RUU again to no avail.
Izeltokatl said:
Ya that's the exact same version I have, not really sure what to do? I re-did everything back to RUU again to no avail.
Click to expand...
Click to collapse
you can try backing up your sd cards and partition them before you start the control bear process, and your sure you have root access correct? via rootchecker, tatanium backup or somethin gand usb degugging checked? if your still having issues look for apophis' thread named "so you need assistance, WE ARE HERE TO HELP" post in that thread im sure he can help you walk thru it..
When I bought my rezound used it had a constant boot loop issue. That's why I got it fairly cheap. I immediayly ran the global ruu hoping it would boot. It still boot looped. I was able to unlock, flash recovery and install newts xxx. I have tried to boot other romsand they give me issues too. Is there any way I can s off in my current configuration because I am pretty confident another ruu from my sd card just won't boot. Has anyone had success being on a custom Rom w global firmware hboot 2.27?
I know this has been posted before, but my particular circumstance after reading through many threads has not been covered (as far as i know). I normally flash A LOT of new roms because i'm a bit of a ROM junkie and am always interested in all of you wonderful developers creations. So after flashing may 1000th rom, CM10.1, many times and getting bootloops, i decided to give up and restore the fully functional CM10 I was using prior. Well, after MANY numerous ways of restoring my back up, others roms, stock OEM RUU's/Zips, and bootloader NOTHING will get my phone to get past the WHITE HTC LOGO SCREEN!!!
I at one point couldn't access or mount my internal SD, o kept getting an error message so I connected it to windows and it was recognized and windows prompted me to format the internal SD card because it was "corrupted", so I did and tried flashing again through all the above methods and STILL NOTHING. Now every time i boot into recovery, it sometimes takes 50+ seconds to load or if it does load quicker it says i'm in "safe mode" or "enable 4EXT'S ADVANCED SETTINGS". I'm sorry that this si lengthy, but i'm stumped. Can anyone help me????
When I was on evervolv all my partitions were corrupted according to 4ext. No rom would flash. The only way I was able to recover was to downgrade to an official T-Mobile GB RUU. Once I did that everything was fine and dandy again. Hopefully if you do the same it works for you.
Thank you, I am going to try this today and see if it helps. Did you just put the RUU on the root of the external SD or was it and exe file??
Thanks again for your help!!!
PeterC18st said:
When I was on evervolv all my partitions were corrupted according to 4ext. No rom would flash. The only way I was able to recover was to downgrade to an official T-Mobile GB RUU. Once I did that everything was fine and dandy again. Hopefully if you do the same it works for you.
Click to expand...
Click to collapse
silvertero said:
Thank you, I am going to try this today and see if it helps. Did you just put the RUU on the root of the external SD or was it and exe file??
Thanks again for your help!!!
Click to expand...
Click to collapse
No the ruu should be a zip file not an exe. The ruu's I used are for T-Mobile.
Since your S-Off you should be able to do downgrade and upgrade at will. Sounds like your partitions are messed up. Also make sure your SuperCID as well.
Downgrade your amaze to a GB RUU 1.43.531.3
Check MD5 SUMS
Rename it to PH85IMG.zip
Place on your External SD CARD
Reboot phone into bootloader
Let Phone find update and apply update
Let Phone reboot
If that worked and your able to use your phone
Repeat Steps 1 - 8 and use ICS RUU 2.14.531.3 instead of the GB RUU.
You can't flash an ICS Rom if your firmware is still GB.
Also if you want to get the latest update from T-Mobile that address wifi calling and updates your Firmware and Radio for better battery life and reception follow my guide here
PeterC18st said:
Since your S-Off you should be able to do downgrade and upgrade at will.
Click to expand...
Click to collapse
I am having the exact problem as OP but I am S-on, what extra steps do I need to take? Thanks for your help.
EDIT: Since I can't allegedly go backwards from JB/ICS to GB when S-on, the only solution I was able to arrive to on my own accord was to format the internal SD in 4ext. Once I did that 4ext was able to see both internal and ext sd and I was able to flash to my heart's content. I think it was a misaligned partition or something. Fortunately everything on the internal SD was backed up already but in the future is there an easier way to do this without formatting sdcard? I re-locked my phone and tried to flash the latest T-Mobile Stock ICS RUU by renaming it to PH85IMG.zip and letting the bootloader flash it but I still got stuck at the white HTC screen at boot.
rbross3030 said:
I am having the exact problem as OP but I am S-on, what extra steps do I need to take? Thanks for your help.
EDIT: Since I can't allegedly go backwards from JB/ICS to GB when S-on, the only solution I was able to arrive to on my own accord was to format the internal SD in 4ext. Once I did that 4ext was able to see both internal and ext sd and I was able to flash to my heart's content. I think it was a misaligned partition or something. Fortunately everything on the internal SD was backed up already but in the future is there an easier way to do this without formatting sdcard? I re-locked my phone and tried to flash the latest T-Mobile Stock ICS RUU by renaming it to PH85IMG.zip and letting the bootloader flash it but I still got stuck at the white HTC screen at boot.
Click to expand...
Click to collapse
ive got the same thing going on, mine is s-on boot loader unlocked. i dont have super cid. ive tried the stock ruu t-moblie gb. in boot loader it reads it but afterwards nothing. ive even tried relocking the bootloader and trying that way, that way is a little differnt. if you relock bootloader then it will force itself in fastboot every time you try to turn it on or plug usb in from your pc. but you cant get into 4ext recovery.fastboot will read that ph85img.zip. and will try to update, but it fail and say cid incorect. but if you unlock your bootloader agein then your can get back into 4ext, but then your just at square one agein. idk im sumped. if any one can help that would be a life saver.
metalclark said:
ive got the same thing going on, mine is s-on boot loader unlocked. i dont have super cid. ive tried the stock ruu t-moblie gb. in boot loader it reads it but afterwards nothing. ive even tried relocking the bootloader and trying that way, that way is a little differnt. if you relock bootloader then it will force itself in fastboot every time you try to turn it on or plug usb in from your pc. but you cant get into 4ext recovery.fastboot will read that ph85img.zip. and will try to update, but it fail and say cid incorect. but if you unlock your bootloader agein then your can get back into 4ext, but then your just at square one agein. idk im sumped. if any one can help that would be a life saver.
Click to expand...
Click to collapse
You have 2 options here
1. check your cid version download the appropriate ruu for it I've posted a unbranded version ruu in krooks thread and run it while the bootloader is locked..
2. Go to 4ext download a FLASHABLE ROM a gb rom NOT a ruu and flash it from 4ext and turn on smart flash before doing it ...
Either way you get a working device
Sent from my HTC_Amaze_4G using xda premium
ravike14 said:
You have 2 options here
1. check your cid version download the appropriate ruu for it I've posted a unbranded version ruu in krooks thread and run it while the bootloader is locked..
2. Go to 4ext download a FLASHABLE ROM a gb rom NOT a ruu and flash it from 4ext and turn on smart flash before doing it ...
Either way you get a working device
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
i wil try the second one.first and see what it does. i cant find that thread, can you put a link up for it?
thanx
metalclark said:
i wil try the second one.first and see what it does. i cant find that thread, can you put a link up for it?
thanx
Click to expand...
Click to collapse
it's pretty much that no threads i'm afraid :/ just flash 4ext then put the rom.zip in your ext sd card then go to tools and enable smart flash since your s on then go to install from sd card>>choose zip from sd card>> then select your zip and flash it if you stuck in a bootloop flash faux kernel while enabling smart flash or flash the stock kernel with aio kit
your welcome i prefer the thanks button tho
ravike14 said:
it's pretty much that no threads i'm afraid :/ just flash 4ext then put the rom.zip in your ext sd card then go to tools and enable smart flash since your s on then go to install from sd card>>choose zip from sd card>> then select your zip and flash it if you stuck in a bootloop flash faux kernel while enabling smart flash or flash the stock kernel with aio kit
your welcome i prefer the thanks button tho
Click to expand...
Click to collapse
ok so it didnt work. i have downloaded caprom its a gb rom and the newst faux kernal. tryed flashing it in 4ext, but it aborts it every time. but now ive tried flashing it thru aio kit. but its looking for the img.file. the faux kernal that was downloaded didnt come in a img.file. but im dowloading the stock kernal i fount and see what happens. scrach that. i forgot for a moment about exstracting it to get the img.file. srry
metalclark said:
ok so it didnt work. i have downloaded caprom its a gb rom and the newst faux kernal. tryed flashing it in 4ext, but it aborts it every time. but now ive tried flashing it thru aio kit. but its looking for the img.file. the faux kernal that was downloaded didnt come in a img.file. but im dowloading the stock kernal i fount and see what happens. scrach that. i forgot for a moment about exstracting it to get the img.file. srry
Click to expand...
Click to collapse
ok so the stock t-mobile kernal worked with the caprom. so farno bugs. everything is working perfectly. i will keep this in mind if it happens agein lol. thanx a bunch man.
metalclark said:
ok so the stock t-mobile kernal worked with the caprom. so farno bugs. everything is working perfectly. i will keep this in mind if it happens agein lol. thanx a bunch man.
Click to expand...
Click to collapse
glad to hear and yea faux kernel is kinda tricky lol
ravike14 said:
glad to hear and yea faux kernel is kinda tricky lol
Click to expand...
Click to collapse
i have a question. im trying to s-off. i cant find a link to download the aio for it. you wouldnt happen to have a link for it would you?
thanx.
metalclark said:
i have a question. im trying to s-off. i cant find a link to download the aio for it. you wouldnt happen to have a link for it would you?
thanx.
Click to expand...
Click to collapse
Well all the inks are taken down sure you can try the Ubuntu version it's safe than the windows version according to the devs
Sent from my HTC_Amaze_4G using xda premium
ravike14 said:
Well all the inks are taken down sure you can try the Ubuntu version it's safe than the windows version according to the devs
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
i wonder why there all down? sadly im not to familiar with ubuntu. i tried to use it a few months ago, to see if i can resurrect my galaxy player 5.0.
but i had no luck with it.
metalclark said:
i wonder why there all down? sadly im not to familiar with ubuntu. i tried to use it a few months ago, to see if i can resurrect my galaxy player 5.0.
but i had no luck with it.
Click to expand...
Click to collapse
noo need to know bout anything all you have to do is run the programme and s off and your done with it
ravike14 said:
noo need to know bout anything all you have to do is run the programme and s off and your done with it
Click to expand...
Click to collapse
i finally got the time to do all this. but i cant seem to get the program to run in ubuntu, i have no idea were the termal cmd is?? any ideas
metalclark said:
i finally got the time to do all this. but i cant seem to get the program to run in ubuntu, i have no idea were the termal cmd is?? any ideas
Click to expand...
Click to collapse
there's the dash board or something similar to that cant remember when you open you get the search option type terminal in the search bar
Still no luck in getting past the splash screen
Well it's been a while since I've posted back on this thread, but I have tried everything that was suggested and i STILL can't get the phone to boot past the HTC Splash screen. I tried flashing many different RUU zips (all renamed PH85IMG) as well as custom ROMS (gingerbread and ICS based) and nothing gets the phone to boot up! They install, but after the phone reboots it's still a no-go. I just don't know what to do anymore. The only thing i can think of is my bootloader is still unlocked, could that have anything to do with this? Like I said earlier my phone is S-ON which makes things more difficult. I'm really hopeless for a solution.
I even mounted the internal and external SD's to the computer and reformatted them. Still doesn't help. Also, my recovery, which is 4EXT, always says i'm in "safe mode" and i have to do something to put it in advanced mode? Please someone help!:crying:
Help
silvertero said:
Well it's been a while since I've posted back on this thread, but I have tried everything that was suggested and i STILL can't get the phone to boot past the HTC Splash screen. I tried flashing many different RUU zips (all renamed PH85IMG) as well as custom ROMS (gingerbread and ICS based) and nothing gets the phone to boot up! They install, but after the phone reboots it's still a no-go. I just don't know what to do anymore. The only thing i can think of is my bootloader is still unlocked, could that have anything to do with this? Like I said earlier my phone is S-ON which makes things more difficult. I'm really hopeless for a solution.
I even mounted the internal and external SD's to the computer and reformatted them. Still doesn't help. Also, my recovery, which is 4EXT, always says i'm in "safe mode" and i have to do something to put it in advanced mode? Please someone help!:crying:
Click to expand...
Click to collapse
I'm having a similar problem only once i get to recovery it won't recognize any of my storage internal or ex, I did a full wipe, i tried reformating the storage from 4ext but it said that there was an error. i cant push anything from the all in one from hasoon because it cant find my phone. im kinda running out of ideas
So I'm currently on Flyhalf's CM10.1 (S-ON), and I checked the recommended firmware/radios for the ROM and realized I'm outdated. It calls for Hboot 2.26 and radio 2.23.10.0123r, 2.23.10.0124r. but I'm on 2.25 and 1.22.10.0421r/1.22.10.0424r. I just updated to the latest version of the rom and I keep getting random bootlooping as well as the rom being way more unstable than the previous build I was on for about 4 months.
So, I'm trying to use Wildhorse's guide to updating firmware through RUU in hopes that it will solve my problems and it just plain isn't working. I've put the RUU in my external SD as PH98IMG, waited for my battery to charge to 90%, shut off the phone, pulled the battery, then gone into Hboot to flash it but I keep getting "No Image or Wrong Image" and it just goes back to the main Hboot screen every single time. Can anyone explain to me why this is happening even though I'm following everybody's directions exactly? I've been searching through the forums for about 2 hours now and I can't get an answer.
I'm still kind of new to HTC devices and how they work, so if anyone could help me figure this out I'd be very thankful.
BrahManty said:
So I'm currently on Flyhalf's CM10.1 (S-ON), and I checked the recommended firmware/radios for the ROM and realized I'm outdated. It calls for Hboot 2.26 and radio 2.23.10.0123r, 2.23.10.0124r. but I'm on 2.25 and 1.22.10.0421r/1.22.10.0424r. I just updated to the latest version of the rom and I keep getting random bootlooping as well as the rom being way more unstable than the previous build I was on for about 4 months.
So, I'm trying to use Wildhorse's guide to updating firmware through RUU in hopes that it will solve my problems and it just plain isn't working. I've put the RUU in my external SD as PH98IMG, waited for my battery to charge to 90%, shut off the phone, pulled the battery, then gone into Hboot to flash it but I keep getting "No Image or Wrong Image" and it just goes back to the main Hboot screen every single time. Can anyone explain to me why this is happening even though I'm following everybody's directions exactly? I've been searching through the forums for about 2 hours now and I can't get an answer.
I'm still kind of new to HTC devices and how they work, so if anyone could help me figure this out I'd be very thankful.
Click to expand...
Click to collapse
You are on a leaked firmware, the currently available RUUs are all older than that, and you can't go back when you are S-ON. You need to S-OFF then you can RUU back to 3.14.605.12 and then OTA back up to the current 4.5.605.14
acejavelin said:
You are on a leaked firmware, the currently available RUUs are all older than that, and you can't go back when you are S-ON. You need to S-OFF then you can RUU back to 3.14.605.12 and then OTA back up to the current 4.5.605.14
Click to expand...
Click to collapse
Okay, I was really hoping that wasn't the case. I hate to ask for more help, but I don't really understand how I'm supposed to get S-Off when I need to be on the stock RUU to do it, and I can't get on the stock RUU because I need to be S-Off to do so...
I hope I'm not stuck this way. Technically I'm on all the same software as I was yesterday, but now I'm getting random reboots all the time as well as bootloops that either go on for ten minutes or never end. I was on a build of CM10.1 from may with Amon Ra recovery, then tried to flash the newest TWRP that requires the new firmware (didn't realize I was on older firmware) and it bricked my phone. So I put on an older CWM recovery, tried to backup and it froze in the middle of every backup it tried to make. Put on an old TWRP, backups worked, so I flashed the newest version of CM10.1 (again not knowing I didn't have newest firmware) and that's when the bootlooping/rebooting started. I recovered to the old version of CM10.1 and the issue didn't go away, so now I'm just trying to figure out what I can do to get my phone in a usable state again.
BrahManty said:
Okay, I was really hoping that wasn't the case. I hate to ask for more help, but I don't really understand how I'm supposed to get S-Off when I need to be on the stock RUU to do it, and I can't get on the stock RUU because I need to be S-Off to do so...
I hope I'm not stuck this way. Technically I'm on all the same software as I was yesterday, but now I'm getting random reboots all the time as well as bootloops that either go on for ten minutes or never end. I was on a build of CM10.1 from may with Amon Ra recovery, then tried to flash the newest TWRP that requires the new firmware (didn't realize I was on older firmware) and it bricked my phone. So I put on an older CWM recovery, tried to backup and it froze in the middle of every backup it tried to make. Put on an old TWRP, backups worked, so I flashed the newest version of CM10.1 (again not knowing I didn't have newest firmware) and that's when the bootlooping/rebooting started. I recovered to the old version of CM10.1 and the issue didn't go away, so now I'm just trying to figure out what I can do to get my phone in a usable state again.
Click to expand...
Click to collapse
Hey, wait a sec... :laugh:
My bad, I just double checked, and with that Hboot/radio combination you are on stock ICS firmware already! Just RUU version 3.14.605.12, that should work without issues if done correctly and you should be back to pure ICS and can then allow the OTA to upgrade you in a few steps to 4.5.605.14
acejavelin said:
Hey, wait a sec... :laugh:
My bad, I just double checked, and with that Hboot/radio combination you are on stock ICS firmware already! Just RUU version 3.14.605.12, that should work without issues if done correctly and you should be back to pure ICS and can then allow the OTA to upgrade you in a few steps to 4.5.605.14
Click to expand...
Click to collapse
Oh, thank god. Hahah. I didn't remember ever flashing any leaked firmware before, so I was kind of confused there. I figured I may have done it somewhere in the unlocking/rooting process and just couldnt remember. Okay, thanks again for the help. RUU's have always confused me with the way they work. I should be stable in no time hopefully.
And now I'm having more issues... I can't use the Rom Updater because somethings wrong with my usb connection. I can plug it in and transfer files and such, but trying to use any ADB commands results in "Device not found" and the Rom Updater says it can't connect to my device either. My HTC Drivers are up to date, so I'm not sure why this is happening. Is there any way I can just get the PH98IMG.zip for 3.14.605.12 instead of having to use the RUU?
Not really sure what you are trying to run, I didn't think there was a 3.14.605.12 executable RUU, but use this page and instructions and grab the file: http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/
Remember you will need to RELOCK the bootloader if I am not mistaken it is possible to hard brick if you don't!
Then copy to external SD card, name the file PH98IMG.zip (beware of the Windows "double zip" issue), verify MD5 on the SDcard, then reboot into hboot and go. Do it twice!!! Let it boot up and sit for about 10 minutes to calm down, then remove the PH98IMG.zip file from the SD card. Everything should be smooth sailing from there...
You should then be S-ON, completely stock. You will need to unlock again to do anything more
acejavelin said:
Not really sure what you are trying to run, I didn't think there was a 3.14.605.12 executable RUU, but use this page and instructions and grab the file: http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/
Remember you will need to RELOCK the bootloader if I am not mistaken it is possible to hard brick if you don't!
Then copy to external SD card, name the file PH98IMG.zip (beware of the Windows "double zip" issue), verify MD5 on the SDcard, then reboot into hboot and go. Do it twice!!! Let it boot up and sit for about 10 minutes to calm down, then remove the PH98IMG.zip file from the SD card. Everything should be smooth sailing from there...
You should then be S-ON, completely stock. You will need to unlock again to do anything more
Click to expand...
Click to collapse
Strange, re-locking the bootloader was all I needed to get the RUU to update in my bootloader. No one else said to do that in any of the instructions, but I did it and immediately it started updating with the PH98IMG that I was originally trying to flash (from here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331).
I'm back to stock now, but firmware is 4.03.605.2, not 4.03.605.14. Is that going to be an issue or can I go right ahead with re-unlocking the bootloader and flashing recovery/roms?
BrahManty said:
Strange, re-locking the bootloader was all I needed to get the RUU to update in my bootloader. No one else said to do that in any of the instructions, but I did it and immediately it started updating with the PH98IMG that I was originally trying to flash (from here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331).
I'm back to stock now, but firmware is 4.03.605.2, not 4.03.605.14. Is that going to be an issue or can I go right ahead with re-unlocking the bootloader and flashing recovery/roms?
Click to expand...
Click to collapse
Well, I have some good news and bad news...
Bad news is you are now on a leaked firmware and will have to S-OFF to go up or down in versions unless a full RUU is released for the current OTA of 4.5.605.14...
Good news is you are the global leak, and you can use the JuopunutBear S-OFF exploit from http://unlimited.io/index.htm just as if you were on the original ICS release. Also, you can S-OFF and use most ROMs and recoveries as you are now on a global mode firmware.
acejavelin said:
Well, I have some good news and bad news...
Bad news is you are now on a leaked firmware and will have to S-OFF to go up or down in versions unless a full RUU is released for the current OTA of 4.5.605.14...
Good news is you are the global leak, and you can use the JuopunutBear S-OFF exploit from http://unlimited.io/index.htm just as if you were on the original ICS release. Also, you can S-OFF and use most ROMs and recoveries as you are now on a global mode firmware.
Click to expand...
Click to collapse
Lol, all right, I would have tried to get the right firmware on there but my phone got so buggy that it wouldn't even boot into the rom anymore. So I couldn't get it on the SD card and I had to make do with what I had on there. At this point, I'm just glad the phone is usable again and I might leave it stock for a while. Thank you so much for all your help, I couldn't have figured this out without you!
BrahManty said:
Lol, all right, I would have tried to get the right firmware on there but my phone got so buggy that it wouldn't even boot into the rom anymore. So I couldn't get it on the SD card and I had to make do with what I had on there. At this point, I'm just glad the phone is usable again and I might leave it stock for a while. Thank you so much for all your help, I couldn't have figured this out without you!
Click to expand...
Click to collapse
Cool, glad you got it working.
That firmware is actually pretty decent and rock solid stable, you shouldn't have any more software related issues... Plus you can root/ROM like normal from that version, the radios may be slightler lower than most recommended versions, but they should work fine. If you do decide to go the ROM route again, I would suggest going S-OFF before starting, it will just make it easier in the long run.
Hey, just wanted to ask some questions as a follow-up since this seems to be the most relevant (and active) thread to my issue:
Long story short, got a new (to me) Rezound. It was running CM10, from the forthnightly thread. New SIM card from Verizon and I was getting data, but the no mobile network found error. After reading the threads I could find on the error, went with the suggestion of a wipe and so I did. A few too many beers while reading thru the forums, and I did the wipe a bit too thoroughly. Now I have a no OS found, and instead of thinking I know what I'm doing I'd like to ask to make sure I understand this correctly.
Currently, the phone is S-OFF, with TWRP 2.5.0.0. It's saying I'm not rooted, but then again no OS to be rooted. The dump from my bootloader is as follows:
*** TAMPERED ***
*** LOCKED ***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.28.0000
RADIO-2.23.10.0123r/2.23.10.0124r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Sep 20 2012, 17:40:22
Click to expand...
Click to collapse
After checking this thread and this one here it looks like the following applies:
* I can just run the regular RUU (executable) to load a stock image without having to revert back to S-ON first.
* I will have to re-unlock the bootloader thru htcdev after RUUing
* I'll need to reinstall TWRP
Is this right? Am I missing anything?
JoeKamel said:
Hey, just wanted to ask some questions as a follow-up since this seems to be the most relevant (and active) thread to my issue:
Long story short, got a new (to me) Rezound. It was running CM10, from the forthnightly thread. New SIM card from Verizon and I was getting data, but the no mobile network found error. After reading the threads I could find on the error, went with the suggestion of a wipe and so I did. A few too many beers while reading thru the forums, and I did the wipe a bit too thoroughly. Now I have a no OS found, and instead of thinking I know what I'm doing I'd like to ask to make sure I understand this correctly.
Currently, the phone is S-OFF, with TWRP 2.5.0.0. It's saying I'm not rooted, but then again no OS to be rooted. The dump from my bootloader is as follows:
After checking this thread and this one here it looks like the following applies:
* I can just run the regular RUU (executable) to load a stock image without having to revert back to S-ON first.
* I will have to re-unlock the bootloader thru htcdev after RUUing
* I'll need to reinstall TWRP
Is this right? Am I missing anything?
Click to expand...
Click to collapse
You should be able to just boot into twrp and flash a rom
Sent from my ADR6425LVW using xda premium
izzaeroth said:
You should be able to just boot into twrp and flash a rom
Click to expand...
Click to collapse
Okay, that's good to know. For now though, if I just wanted to get my phone working, make sure there's not a SIM issue and such I could go back to a stock image without worrying? I just would rather do a lot more reading and make sure I understand what I'm doing before I try to put a rom on and screw things up further.
JoeKamel said:
Okay, that's good to know. For now though, if I just wanted to get my phone working, make sure there's not a SIM issue and such I could go back to a stock image without worrying? I just would rather do a lot more reading and make sure I understand what I'm doing before I try to put a rom on and screw things up further.
Click to expand...
Click to collapse
No doubt its good to be cautious when you are s-off. If you are just wanting plain jane stock then you could just flash a ruu from boot loader.
Sent from my ADR6425LVW using xda premium
izzaeroth said:
No doubt its good to be cautious when you are s-off. If you are just wanting plain jane stock then you could just flash a ruu from boot loader.
Click to expand...
Click to collapse
Okay, so if I go with the image here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331
Would I still need to relock the bootloader since I'm S-OFF or can I just flash that from TWRP and go from there?
JoeKamel said:
Okay, so if I go with the image here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331
Would I still need to relock the bootloader since I'm S-OFF or can I just flash that from TWRP and go from there?
Click to expand...
Click to collapse
Honestly I don't remember if you would have to relock to flash that in boot loader sine you are s-off, but I do know it won't flash from recovery
Sent from my ADR6425LVW using xda premium
izzaeroth said:
Honestly I don't remember if you would have to relock to flash that in boot loader sine you are s-off, but I do know it won't flash from recovery
Click to expand...
Click to collapse
Recovery as in HBoot or TWRP? Because I still have TWRP. I can get the windows executable RUU for ICS if need be.
JoeKamel said:
Recovery as in HBoot or TWRP? Because I still have TWRP. I can get the windows executable RUU for ICS if need be.
Click to expand...
Click to collapse
Recovery = twrp
Sent from my ADR6425LVW using xda premium
izzaeroth said:
Honestly I don't remember if you would have to relock to flash that in boot loader sine you are s-off, but I do know it won't flash from recovery
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
S-off is S-off... installing a RUU wont change that, it may set you back to 'Locked", but you are S-off so it doesn't matter, you can stay locked&s-off and its no different than unlocked/S-off.
If you are going back to stock and are S-off I would use the Global Mode Leak (4.3.605.2) available on AndroidPolice and flash in Hboot... rename file to PH98IMG.zip and place in root of SD card (how it gets there is a irrelevant) then reboot into Hboot, confirm and wait.
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app
Well I don't have any signal. I booted CM11 snapshot. Since it did say I could with S-On. Now, my sim card is not detected? Also my internal storage is detected in phone but when connected to pc cannot see size of storage, I can see external. So with no internal cant boot into TWRP
daddyodizzel said:
Well I don't have any signal. I booted CM11 snapshot. Since it did say I could with S-On. Now, my sim card is not detected? Also my internal storage is detected in phone but when connected to pc cannot see size of storage, I can see external. So with no internal cant boot into TWRP
Click to expand...
Click to collapse
sorry to hear that. im also experiencing the same issue. kind of. i lost signal. and with cyanogenmod rom 12 its telling me sim card is not detected. this issue of mine came up after i ruu'ed firmware upgrade and install a lollipop rom. hope someone chimes in with a fix
simpl3lang said:
sorry to hear that. im also experiencing the same issue. kind of. i lost signal. and with cyanogenmod rom 12 its telling me sim card is not detected. this issue of mine came up after i ruu'ed firmware upgrade and install a lollipop rom. hope someone chimes in with a fix
Click to expand...
Click to collapse
I've tried running the RUU from htc website. Tried to flash backups from here, nothing.... Also tried flashing the 0p6bimg.zip and it tells me Hboot Version is older! Update fail! Device halted due to Large Image fail!..... I just want my phone to work at this point lol
daddyodizzel said:
I've tried running the RUU from htc website. Tried to flash backups from here, nothing.... Also tried flashing the 0p6bimg.zip and it tells me Hboot Version is older! Update fail! Device halted due to Large Image fail!..... I just want my phone to work at this point lol
Click to expand...
Click to collapse
This is a known issue with the latest version OS. Are you s off or on?
dottat said:
This is a known issue with the latest version OS. Are you s off or on?
Click to expand...
Click to collapse
I am S-ON, this is the rom I tried to flash. http://forum.xda-developers.com/showthread.php?t=2743574 which in the comments towards the end it stated that I didn't needed to be S-OFF... but then again its the internet... I got too excited and forgot to nandroid backup, I don't mind going S-off but what's happening is in my about device, I have no imei and such. So sunshine tells me about the kernel.
daddyodizzel said:
I am S-ON, this is the rom I tried to flash. http://forum.xda-developers.com/showthread.php?t=2743574 which in the comments towards the end it stated that I didn't needed to be S-OFF... but then again its the internet... I got too excited and forgot to nandroid backup, I don't mind going S-off but what's happening is in my about device, I have no imei and such. So sunshine tells me about the kernel.
Click to expand...
Click to collapse
So the problem is the new firmware and the way apns are now controlled. You can try flashing a lower version 100% stock sense Rom (not ruu since you cannot downgrade firmware). Once on lower stock Rom try sunshine. If you can get s-off you can then downgrade your firmware and try cm again.
dottat said:
So the problem is the new firmware and the way apns are now controlled. You can try flashing a lower version 100% stock sense Rom (not ruu since you cannot downgrade firmware). Once on lower stock Rom try sunshine. If you can get s-off you can then downgrade your firmware and try cm again.
Click to expand...
Click to collapse
Could you pin point me towards the required rom, if it's not too much to ask.
Edit: I flashed a ATT_1.58_STOCKED_DEODEXED, and everything is back and running! About to go get S-OFF then MAKE an nandroid, and then upgrade to lollipop! Yay!
daddyodizzel said:
Could you pin point me towards the required rom, if it's not too much to ask.
Edit: I flashed a ATT_1.58_STOCKED_DEODEXED, and everything is back and running! About to go get S-OFF then MAKE an nandroid, and then upgrade to lollipop! Yay!
Click to expand...
Click to collapse
Good on ya mate! Sorry for the delay.. had to fly someone somewhere this afternoon.
dottat said:
Good on ya mate! Sorry for the delay.. had to fly someone somewhere this afternoon.
Click to expand...
Click to collapse
No problem, I actually was like.... Oh yeah left lol but hey sometimes you got the hard way. Let me get your opinion, I love cyanogenmod UI, I currently have the skydragon lollipop rom with htc sense... Hate the UI of sense. I had flash CM12 nightly but sd card weren't mounting when connected to pc, could I get the skydragon rom GPE from the regular htc one m8 development section?
daddyodizzel said:
I've tried running the RUU from htc website.
Click to expand...
Click to collapse
RUU will work as long as you relock bootloader, right RUU for your CID, and you are not trying to "downgrade" (run lower RUU with hboot number lower than what is currently on the phone).
redpoint73 said:
RUU will work as long as you relock bootloader, right RUU for your CID, and you are not trying to "downgrade" (run lower RUU with hboot number lower than what is currently on the phone).
Click to expand...
Click to collapse
I got it fixed after I flashed a deoxed stock rom. Finally made backup. S-OFF and currently on Eragon ROM.
daddyodizzel said:
I got it fixed after I flashed a deoxed stock rom. Finally made backup. S-OFF and currently on Eragon ROM.
Click to expand...
Click to collapse
Sounds great. My previous post was as much for general information, as much as it was for this "specific case". And in fact, now that you have s-off you don't need to relock the bootloader to run RUU in the future, nor does the version check apply.