Related
So far I've had no luck using custom ROMs as it just stays on the htc boot screen and does not work. I can confirm that 'MiUi' does work on my phone - however it is buggy and I don't like it.
I want cyanogenod or either android revolution HD but none of these work.
I thinkit has something to do with the HBOOT being 1.16.000, and the ROM version i'm after is 2.34.981.1 (virgin or optus branded) - am with virgin though in Australia.
I have a custom bootloader/recovery whatever you call it, I wipe the cache, dalvik cache and factory wipe, before installing all ROM's. I can't update to stock ROM either because there is none for hboot 1.16.000
So right now my phone is pretty much a paper weight until I can get it working again.
I prefer custom ROM's if there is any that work, if not I atleast want the stock ROM to work for now so I can use my phone. If someone can help me through the process to get it working it would be greatly appreciated. Thanks.
jakeyo said:
So far I've had no luck using custom ROMs as it just stays on the htc boot screen and does not work. I can confirm that 'MiUi' does work on my phone - however it is buggy and I don't like it.
I want cyanogenod or either android revolution HD but none of these work.
I thinkit has something to do with the HBOOT being 1.16.000, and the ROM version i'm after is 2.34.981.1 (virgin or optus branded) - am with virgin though in Australia.
I have a custom bootloader/recovery whatever you call it, I wipe the cache, dalvik cache and factory wipe, before installing all ROM's. I can't update to stock ROM either because there is none for hboot 1.16.000
So right now my phone is pretty much a paper weight until I can get it working again.
I prefer custom ROM's if there is any that work, if not I atleast want the stock ROM to work for now so I can use my phone. If someone can help me through the process to get it working it would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Hyun is looking for you at revolutionary irc channel.
Sent from my HTC Incredible S using Tapatalk
I know.. I have spoken to him.
jakeyo said:
I know.. I have spoken to him.
Click to expand...
Click to collapse
Any luck? still unable to flash anything?
jakeyo said:
So far I've had no luck using custom ROMs as it just stays on the htc boot screen and does not work. I can confirm that 'MiUi' does work on my phone - however it is buggy and I don't like it.
I want cyanogenod or either android revolution HD but none of these work.
I thinkit has something to do with the HBOOT being 1.16.000, and the ROM version i'm after is 2.34.981.1 (virgin or optus branded) - am with virgin though in Australia.
I have a custom bootloader/recovery whatever you call it, I wipe the cache, dalvik cache and factory wipe, before installing all ROM's. I can't update to stock ROM either because there is none for hboot 1.16.000
So right now my phone is pretty much a paper weight until I can get it working again.
I prefer custom ROM's if there is any that work, if not I atleast want the stock ROM to work for now so I can use my phone. If someone can help me through the process to get it working it would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
If you go to the development section of the HTC Incredible 2 forum, attn1 has a script tool that uses the latest Revolutionary/Unreovked exploit to downgrade the ROMand HBOOT to a version that is supported by Revolutionary.
If you look at the script, it is pretty simple. You would just need to use an older Virgin Mobile RUU.zip instead of the Inc2 version. It looks like the 2.12.981.2 would be the one to try.
Hang on a second, how did you S-off the Hboot 1.16?
I thought you need S-off to be able to flash a custom Rom...
How did you install Miui?
Am I missing something here?
Doesnt matter if you need S-ON or S-OFF, as long as you get permissions to access root files.
Someone installed a custom bootloader so I can install custom ROM's, and it just works.... apparently the radios are locked though.
So, another day gone by and my phone is still not working. I can use MiUi, but I ran out of data on my 3g sim and wifi doesnt work, so now I have no internet on it.
katu2006 said:
Hang on a second, how did you S-off the Hboot 1.16?
I thought you need S-off to be able to flash a custom Rom...
How did you install Miui?
Am I missing something here?
Click to expand...
Click to collapse
I'm pretty sure no soff will cause the issues he is experiencing, though he doesn't seem to be listening
no, you're all just noobs.
It was the boot.img, we swapped it with the MiUi then put back the original one, now it boots up on cyanogenmod7.1 and works completely fine.
Can access root files, can take screenshots, everything is normal.
and I have s-on.
jakeyo said:
no, you're all just noobs.
It was the boot.img, we swapped it with the MiUi then put back the original one, now it boots up on cyanogenmod7.1 and works completely fine.
Can access root files, can take screenshots, everything is normal.
and I have s-on.
Click to expand...
Click to collapse
Yes im a noob that has been using android since 2009..
You seem like a supreme douche.
Weren't you the one who was crying about wanting to go back to his iphone lol
jakeyo said:
no, you're all just noobs.
It was the boot.img, we swapped it with the MiUi then put back the original one, now it boots up on cyanogenmod7.1 and works completely fine.
Can access root files, can take screenshots, everything is normal.
and I have s-on.
Click to expand...
Click to collapse
You're calling us noobs, but you don't even know what was done on your phone...
What's the following sentence supposed to say?
"It was the boot.img, we swapped it with the MiUi then put back the original one"
To get a custom Rom, you actually have to INSTALL it...To get the custom Rom installed, you need CWM recovery. But if you have HBoot 1.16.000, you can't have a custom recovery yet.
In less your "friend" did a downgrade of the HBoot to 1.13.000, it's unlikely that you have CWM recovery on your phone. Even so, to my knowledge HBoot 1.16.000 does a version check and won't let you downgrade it.
So, the question remains, how did you get CWM recovery on your phone?
katu2006 said:
You're calling us noobs, but you don't even know what was done on your phone...
What's the following sentence supposed to say?
"It was the boot.img, we swapped it with the MiUi then put back the original one"
To get a custom Rom, you actually have to INSTALL it...To get the custom Rom installed, you need CWM recovery. But if you have HBoot 1.16.000, you can't have a custom recovery yet.
In less your "friend" did a downgrade of the HBoot to 1.13.000, it's unlikely that you have CWM recovery on your phone. Even so, to my knowledge HBoot 1.16.000 does a version check and won't let you downgrade it.
So, the question remains, how did you get CWM recovery on your phone?
Click to expand...
Click to collapse
This thread is awesome
no, if I hold down power down and power button I see S-ON and HBOOT 1.16.0000
He typed in commands to give it root permissions, not sure exactly as he remote controlled my computer and typed it in. Then yes, he flashes CWM onto the phone then I installed revolutionary.
Firstly, I went onto the HTC dev site (created an account) and followed the steps to unlock the bootloader. In the end, it was successful, and once it's finished it will wipe the phone (AND WILL STILL SAY s-on)
So then the bootloader is now unlocked, and he did various commands in fastboot. My guess is that he installed CWM from there and it just worked.
at first, cyanogenmod would not boot, so he copied the (boot.img that is working) from MiUi and repled it with cyanogenmod's. The phone booted up and worked. Then he put it back how it was and it now works. Strange, but something must've given it a kick.
I'll repeat myself.
HBOOT 1.16.0000
S-ON
Cyanogenmod &.1 (stable)
Full root access
Need I say more to prove it?
As far as I know, I just cannot flash radios, which actually require the S-OFF....
sorry if I come across as rude, just a long day..
Talk to aftab565 he has the same hboot as you and has arhd running. Sounds like your phone was temp rooted and flashed and I would advise against letting people you don't know take remote access of your pc.
Hopefully it works for him I couldn't help.
Just replied to his thread.
And I know I was aware. I had full control though (could press a certain key to disconnect the connection - and only gave a temporary password) He was only typing in CMD things to do with the phone that I've heard of before
(ADB shell, fastboot recovery etc) and in the end worked well. He said my job is done and disconnect himself, so good guy
Didn't take my eyes off the screen either.
jakeyo said:
Just replied to his thread.
And I know I was aware. I had full control though (could press a certain key to disconnect the connection - and only gave a temporary password) He was only typing in CMD things to do with the phone that I've heard of before
(ADB shell, fastboot recovery etc) and in the end worked well. He said my job is done and disconnect himself, so good guy
Click to expand...
Click to collapse
You gotta give props to these guys for donating their time. Every day there's more talk about h-boot 1.16.0000 so I figure if devs want to keep devin there'll be a rev released eventually.
I really appreciate the amount of work hes done, in total I recon he's spent about 6 hours trying to help me getting it to work.
Never left me by myself, he always helped me through every step and was always there if I needed help. I've now got CM7 thanks to him. If he didn't fix it, I would have a useless phone because I couldn't even put on the stock ROM because of my HBOOT im guessing (I did an OTA update to get 1.16.0000 therefore too new to download)
I think SOME of the custom roms do have support for 1.16.0000 and what you only need is the boot file from them to boot up your non-booting ROM then you're all good.
ok, just to put some closure and sanity on this thread.
Firstly I'm probably bettery know as hyuh on #revolutionary, and it was me who was connected to his PC.
I use teamviewer to connect to people remotely, this allows anyone who doesn't like the look of *anything* I do to diconnect me...The user in front of the PC has full control of my session and I remind them to close teamviewer after we're done.
Secondly to those who think you need to be S-OFF to install a custom ROM or custom recovery, this is simply not true in the case of the 1.16 hboot. If you follow the HTC unlock procedure then you will have sufficient access to the phone to do this, it is not S-OFF just an unlock. Your phone will be in state "S-ON unlocked" This allows certain partitions on the emmc to be written to, and this sufficient for custom ROMs.
Really all that is requird is:
Code:
fastboot flash recovery <recovery.img>
then follow the normal flashing procedures.
In jakeyo's case CM7 would not boot, but MIUI would. When I say it would not boot I do not mean a boot loop here, I mean no boot period. At this point I had expected to need to rebuild a boot image for CM7 for him suspecting that HTC had done something different in the new hboot with paritions or the boot image offset.
The reason for flashing the MIUI boot image on top of CM7 was simple, to get to adb in the boot image. However seeing nothing particularly strange in the boot sequence ( other than the mismatch and resulting bootloop) I decided to reflash the CM7 boot image through fastboot.
The phone booted fully this time without issues.
It appears that the boot image simply did not flash properly from recovery the first time but I don't have a vivo to troubleshoot further.
A couple of things:
1. Don't take the OTA for 1.16 hboot if you haven't already done so.
There is currently no unofficial unlock/S-OFF
There is no RUU to fix the phone if you screw up.
There is nothing in the OTA you can't get in other ways.
2. If you're on 1.16 and want custom ROMs and aren't worried about warranty, go ahead and do unlock from HTC, but bear in mind:
There is no RUU, so you can't go back to stock
You can't flash radios
You can't superCID or similar ( but not needed since there is no RUU )
2a. You don't need any existing root method to exist, there is no exploit involved in any of this, this will work irrespective of the current status of a root expoit existing or not.
2b. The phone does not have to be listed by HTC as being supproted. Any phone with a suitable hboot can be unlocked.
if this:
Code:
fastboot oem get_identifier_token
returns an identifier code then the phone can be ulocked.
globatron said:
ok, just to put some closure and sanity on this thread.
Firstly I'm probably bettery know as hyuh on #revolutionary, and it was me who was connected to his PC.
I use teamviewer to connect to people remotely, this allows anyone who doesn't like the look of *anything* I do to diconnect me...The user in front of the PC has full control of my session and I remind them to close teamviewer after we're done.
Secondly to those who think you need to be S-OFF to install a custom ROM or custom recovery, this is simply not true in the case of the 1.16 hboot. If you follow the HTC unlock procedure then you will have sufficient access to the phone to do this, it is not S-OFF just an unlock. Your phone will be in state "S-ON unlocked" This allows certain partitions on the emmc to be written to, and this sufficient for custom ROMs.
Really all that is requird is:
Code:
fastboot flash recovery <recovery.img>
then follow the normal flashing procedures.
In jakeyo's case CM7 would not boot, but MIUI would. When I say it would not boot I do not mean a boot loop here, I mean no boot period. At this point I had expected to need to rebuild a boot image for CM7 for him suspecting that HTC had done something different in the new hboot with paritions or the boot image offset.
The reason for flashing the MIUI boot image on top of CM7 was simple, to get to adb in the boot image. However seeing nothing particularly strange in the boot sequence ( other than the mismatch and resulting bootloop) I decided to reflash the CM7 boot image through fastboot.
The phone booted fully this time without issues.
It appears that the boot image simply did not flash properly from recovery the first time but I don't have a vivo to troubleshoot further.
A couple of things:
1. Don't take the OTA for 1.16 hboot if you haven't already done so.
There is currently no unofficial unlock/S-OFF
There is no RUU to fix the phone if you screw up.
There is nothing in the OTA you can't get in other ways.
2. If you're on 1.16 and want custom ROMs and aren't worried about warranty, go ahead and do unlock from HTC, but bear in mind:
There is no RUU, so you can't go back to stock
You can't flash radios
You can't superCID or similar ( but not needed since there is no RUU )
Click to expand...
Click to collapse
Get a mod to make a hboot sticky there will be floods of this crap further down the road.
I've been struggling with this for over a day now.
I unlocked and rooted my phone just fine (HTC One on Sprint, 4.3) - but when I flashed a ROM, I flashed Maximus HD, which was apparently an International version and not a Sprint one. I think that messed some things up. After trying a few different ROMs on top of that, nothing works.
Each ROM I flash will "install" correctly, but when it boots to the lock screen, upon unlocking it gives me the HTC splash screen.
I'm convinced that my accidental upgrade to hboot 1.55 is rendering it impossible for me to flash any working ROMs - be it stock or otherwise. I can enter Recovery mode, adb sideload, and flash ROMs, but none of them work.
I've tried Superwipe and then Bad Boyz, but it's the same thing. After installation, it sticks at the HTC splash screen.
So, my options are limited. I think I need to find a way to revert my hboot to 1.44 from 1.55 - that way at least the stock RUU is compatible. However, I can't find any way to do this; since I'm S-On, and I can't access any ROM to mess with settings, I have no idea how to do this, or how to flash a workable ROM in order to switch to S-Off.
Anyone have any ideas. I'm seriously distraught. I just bought this phone, and I love it. I'm so sad that I decided to try this rooting/unlocking/ROM flashing business because it's disrupted my sanity.
Any thoughts or ideas will help immensely. I will give more information if needed. Thanks!
WayneQuasar said:
I've been struggling with this for over a day now.
I unlocked and rooted my phone just fine (HTC One on Sprint, 4.3) - but when I flashed a ROM, I flashed Maximus HD, which was apparently an International version and not a Sprint one. I think that messed some things up. After trying a few different ROMs on top of that, nothing works.
Each ROM I flash will "install" correctly, but when it boots to the lock screen, upon unlocking it gives me the HTC splash screen.
I'm convinced that my accidental upgrade to hboot 1.55 is rendering it impossible for me to flash any working ROMs - be it stock or otherwise. I can enter Recovery mode, adb sideload, and flash ROMs, but none of them work.
I've tried Superwipe and then Bad Boyz, but it's the same thing. After installation, it sticks at the HTC splash screen.
So, my options are limited. I think I need to find a way to revert my hboot to 1.44 from 1.55 - that way at least the stock RUU is compatible. However, I can't find any way to do this; since I'm S-On, and I can't access any ROM to mess with settings, I have no idea how to do this, or how to flash a workable ROM in order to switch to S-Off.
Anyone have any ideas. I'm seriously distraught. I just bought this phone, and I love it. I'm so sad that I decided to try this rooting/unlocking/ROM flashing business because it's disrupted my sanity.
Any thoughts or ideas will help immensely. I will give more information if needed. Thanks!
Click to expand...
Click to collapse
Check PM
same problem like TS have
Having the same issues like TS..
Can somebody point me where to look for the answers,the difference is that im on .44 boot
Somebody please
MeiTeS said:
Having the same issues like TS..
Can somebody point me where to look for the answers,the difference is that im on .44 boot
Somebody please
Click to expand...
Click to collapse
Look HERE
I think this is going to need an experienced dev to answer. Its a small question and probably a small answer but I'm going to put all the information I can.
Ok, so my background is that I recently returned my phone stock, the steps I took were:
S-off, flash RUU, root, remove tampered and unlocked flags, unroot, flash stock recovery, lock the bootloader, s-on.
I then OTAed myself up to 4.3 sense 5.5.
My issue is that having returned to stock, my phone has some instabilities like:
1. it randomly restarted once,
2. I can't lock the device (but can power it off so its not the button broken),
3. and once I opened the camera and the camera bit only took a square of the screen, as in it didn't fill up the whole screen, and the camera menus were messed up (when I rotated, half of the menus were cropped out of the screen, but it went back to normal around 15 seconds later).
Anyway, reason I'm posting this is that I have a niggling feeling that, being originally a CID J15 and x.xx.415.x (middle east firmware which has no RUU available) firmware device, I flashed a 401.x (Europe I think) firmware RUU, this is giving my device some issues. Would that be possible? I got the RUU from htc1guru and it listed J15 as one of the suitable CIDs for the RUU. I also, after unrooting, relocking bootloader and s-on, flashed the RUU again, because as far as I know the RUU (something made by HTC officially) will not flash on a CID that it was not made for, and it worked just fine. So, thats not the issue then is it? I can't think of anything else, I didn't even install any apps yet, only whatsapp.
3alaawi said:
I think this is going to need an experienced dev to answer. Its a small question and probably a small answer but I'm going to put all the information I can.
Ok, so my background is that I recently returned my phone stock, the steps I took were:
S-off, flash RUU, root, remove tampered and unlocked flags, unroot, flash stock recovery, lock the bootloader, s-on.
I then OTAed myself up to 4.3 sense 5.5.
My issue is that having returned to stock, my phone has some instabilities like:
1. it randomly restarted once,
2. I can't lock the device (but can power it off so its not the button broken),
3. and once I opened the camera and the camera bit only took a square of the screen, as in it didn't fill up the whole screen, and the camera menus were messed up (when I rotated, half of the menus were cropped out of the screen, but it went back to normal around 15 seconds later).
Anyway, reason I'm posting this is that I have a niggling feeling that, being originally a CID J15 and x.xx.415.x (middle east firmware which has no RUU available) firmware device, I flashed a 401.x (Europe I think) firmware RUU, this is giving my device some issues. Would that be possible? I got the RUU from htc1guru and it listed J15 as one of the suitable CIDs for the RUU. I also, after unrooting, relocking bootloader and s-on, flashed the RUU again, because as far as I know the RUU (something made by HTC officially) will not flash on a CID that it was not made for, and it worked just fine. So, thats not the issue then is it? I can't think of anything else, I didn't even install any apps yet, only whatsapp.
Click to expand...
Click to collapse
Could you provide the following informations? Because then it's easier to determine the reason for the misbehaviour...
-Did you also have these issues with the firmware you got from the RUU, I mean did you also experience these issues without any OTAs?
-Could you post the link to the RUU you used? Because I also RUUed my phone a few days ago with the same procedure.. but actually, I am from Europe
-Did you flash the stock hboot 1.44 before flashing the RUU?
And as far my knowledge goes, the middle east HTC One doesn't have other hardware, it only has a bit different software, so this shouldn't be the cause for the issues..
Other than that:
Unlock your phone, use a custom recovery and flash a different ROM, and if it works in this case, you can exclude other firmware parts than the system...
And maybe you wanna try out one of these RUUs:
http://www.androidruu.com/index.php?developer=M7
Maybe there is one for you
LibertyMarine said:
Could you provide the following informations? Because then it's easier to determine the reason for the misbehaviour...
-Did you also have these issues with the firmware you got from the RUU, I mean did you also experience these issues without any OTAs?
-Could you post the link to the RUU you used? Because I also RUUed my phone a few days ago with the same procedure.. but actually, I am from Europe
-Did you flash the stock hboot 1.44 before flashing the RUU?
And as far my knowledge goes, the middle east HTC One doesn't have other hardware, it only has a bit different software, so this shouldn't be the cause for the issues..
Other than that:
Unlock your phone, use a custom recovery and flash a different ROM, and if it works in this case, you can exclude other firmware parts than the system...
And maybe you wanna try out one of these RUUs:
http://www.androidruu.com/index.php?developer=M7
Maybe there is one for you
Click to expand...
Click to collapse
Hello,
Here's the RUU I flashed:
http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
It didn't flash first and it said on the link I just posted that I may need hboot 1.44 and so I downloaded and flashed that one and then it worked.
I couldn't tell you if I experienced this before the OTA or not because I OTAed one update after the other immediately. What I can say however is that the home and back button seemed less sensitive to touch in the initial builds, but one of the OTAs made it how it always is.
A for unlocking again and flashing a different rom, I guess I could flash a stock 401 4.3 rom and redo the unrooting process. I just found it really odd that I'm having these issues whilst being on full stock, I've only ever had these issues when flashing unreliable roms and kernels. You lost me at "excluding other firmware parts" though. My main concern is that I want zero chance for anyone to know that my devices was rooted once upon a time, so I wouldn't want to compromise that.
3alaawi said:
Hello,
Here's the RUU I flashed:
http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
It didn't flash first and it said on the link I just posted that I may need hboot 1.44 and so I downloaded and flashed that one and then it worked.
I couldn't tell you if I experienced this before the OTA or not because I OTAed one update after the other immediately. What I can say however is that the home and back button seemed less sensitive to touch in the initial builds, but one of the OTAs made it how it always is.
A for unlocking again and flashing a different rom, I guess I could flash a stock 401 4.3 rom and redo the unrooting process. I just found it really odd that I'm having these issues whilst being on full stock, I've only ever had these issues when flashing unreliable roms and kernels. You lost me at "excluding other firmware parts" though. My main concern is that I want zero chance for anyone to know that my devices was rooted once upon a time, so I wouldn't want to compromise that.
Click to expand...
Click to collapse
Ok.. I flashed the zip.. but this really shouldn't be an issue
But with "excluding other firmware parts" I meant.. if you try another ROM and there it works, you should definitely know that the issue is caused by the system and not by hardware or bootloader etc...
Try another ROM and if it works fine, you can try another RUU.. maybe the zip.. and then you can re-unroot your HTC One and then they won't have any chance finding out what you'd done
3alaawi said:
Hello,
Here's the RUU I flashed:
http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
It didn't flash first and it said on the link I just posted that I may need hboot 1.44 and so I downloaded and flashed that one and then it worked.
I couldn't tell you if I experienced this before the OTA or not because I OTAed one update after the other immediately. What I can say however is that the home and back button seemed less sensitive to touch in the initial builds, but one of the OTAs made it how it always is.
A for unlocking again and flashing a different rom, I guess I could flash a stock 401 4.3 rom and redo the unrooting process. I just found it really odd that I'm having these issues whilst being on full stock, I've only ever had these issues when flashing unreliable roms and kernels. You lost me at "excluding other firmware parts" though. My main concern is that I want zero chance for anyone to know that my devices was rooted once upon a time, so I wouldn't want to compromise that.
Click to expand...
Click to collapse
Did it work? Or can I provide more help?
LibertyMarine said:
Did it work? Or can I provide more help?
Click to expand...
Click to collapse
I actually just booted into the bootloader and turned the phone on again. Then I could lock my device again and it seemed stable though I didn't have much time to test it. I just sent it in for repairs earlier today (for another issue, I have the camera tint problem with my device).
I'm guessing the previous times I reset it, it had that option in the power menu on (fast boot or something like that) maybe thats why the problems didn't go away?
Anyway, thanks for your help
Dont't buy HTC. They Thef's .
This is Problem.... Producer send fake updates to destroy all firmware stock too. I Have Desire 626 from ORANGE PL and my phone get update with this same problems. One idea. Dont't buy HTC. They Thef's .
i'm a bit new to android and the whole rooting and ROM so please excuse my ignorance.
two days ago i updated my phone to KitKat 4.4.2 and since then i have almost no WIFI it keeps disconnecting i tried many solutions but non seem to help. Also i have been experiencing crashes from different apps and lets just the phone is not that usable anymore.
HTC One is my favorite phone i ever owned until i updated to 4.4.2.
i read a lot about ROMs, flashing and S-On/Off but it's getting very confusing at this piont specially to which version i might need. so maybe some one cant point me to the right place.
i just want to be able to restore back to 4.3 which was running a lot better then 4.4. is it possible to do so?
if it means i have to install a costume ROM that's fine as long as i can go back to 4.3.
i have HTC One (Europe) bought without a contract.
I got this information from holding the power and Volume down buttons.
--locked--
M7-UL-PVT
S-On RH
HBoot: 1.56
radio 4A.25.3263.21
OS: 4.19.401.11
is there any other info needed?
is it possible to downgrade to 4.3, preferably RUU if not possible then ROOTing.
THANK YOU VERY MUCH IN ADVANCE
Maybe just a heads up if it's possible to downgrade? or if possible with Flashing an older customer ROM?
User1303 said:
i'm a bit new to android and the whole rooting and ROM so please excuse my ignorance.
two days ago i updated my phone to KitKat 4.4.2 and since then i have almost no WIFI it keeps disconnecting i tried many solutions but non seem to help. Also i have been experiencing crashes from different apps and lets just the phone is not that usable anymore.
HTC One is my favorite phone i ever owned until i updated to 4.4.2.
i read a lot about ROMs, flashing and S-On/Off but it's getting very confusing at this piont specially to which version i might need. so maybe some one cant point me to the right place.
i just want to be able to restore back to 4.3 which was running a lot better then 4.4. is it possible to do so?
if it means i have to install a costume ROM that's fine as long as i can go back to 4.3.
i have HTC One (Europe) bought without a contract.
I got this information from holding the power and Volume down buttons.
--locked--
M7-UL-PVT
S-On RH
HBoot: 1.56
radio 4A.25.3263.21
OS: 4.19.401.11
is there any other info needed?
is it possible to downgrade to 4.3, preferably RUU if not possible then ROOTing.
THANK YOU VERY MUCH IN ADVANCE
Click to expand...
Click to collapse
User1303 said:
Maybe just a heads up if it's possible to downgrade? or if possible with Flashing an older customer ROM?
Click to expand...
Click to collapse
a LOT is possible, but you will need to unlock your bootloader, and possibly need S-Off, depending how far you want to go.... the question is, are you really intending to do that?? my first impression would be, probably not
there's a lot of reading and research to do for that (at least if you want to do it right)
as for WiFi, this didn't help: http://android-revolution-hd.blogspot.com/2014/02/how-to-fix-wi-fi-htc-one.html
neither changing the channel on your router
I rooted my phone thinking it would benefit me, like it did on my EVO 3D, however i cannot have been more wrong. First off all the ROMS i tried (CM11, viper, insert coin,) had either a buzzing noise from the top speaker, or the WIFI didn't work. Second i cannot update the firmware using the OTA update. I download it then try to install and all that happens is it boots into TWRP. I just want to know if there is a way to get it back to normal like i just got the phone. I tried finding my Cid and doing the unlocker method, but i didn't find any Cid labeled spcs_004. Is there just an RUU i can run that will get my phone back on track with sprint? I have the Harmon Kardon model of the M8 BTW. Also i never updated my phone since i got it, so i'm on firmware no 1.54.xxx.xx (i don't know the rest of the numbers off hand).
Go to the thread in the link below. Download the 3.31.654.2 RUU to your computer. Connect your phone and computer via USB cable and boot your phone into Fastboot USB mode. Open up a command terminal with your ADB/Fastboot folder, then re-lock your bootloader using the command fastboot oem lock (unless you're S-off). Leave your phone and computer connected and from either Fastboot USB mode or while booted to the Android OS double-click the RUU to start the installer. Follow the prompts on your computer screen to install the RUU. For more info hit the second link in my sig and read the RUU section of that guide.
http://forum.xda-developers.com/showthread.php?t=2729173
Thank you. It worked and my phone is working like i just got it. Big thanks for the quick reply.
D3TH5150 said:
Thank you. It worked and my phone is working like i just got it. Big thanks for the quick reply.
Click to expand...
Click to collapse
Anytime, glad to help :thumbup:
I had the same problem just got my hk m8 rooted it and flashed nocturnal night vision ... had problems with WiFi and the Rom booting up as well as recovery so I ran the 3.31.654.2 RUU and got it running again, problem is I can't get a good signal my calls drop after like 30 seconds all the time... any help would be greatly appreciated I'll donate too
Magnum_Enforcer said:
Anytime, glad to help :thumbup:
Click to expand...
Click to collapse
Oh my gosh. If this helps get me back....
I screwed up and tried to flash ARHD v32 without being s-off and I've been without my M8 for 24 hours. And freaking out for the last nine. I knew it couldn't be that difficult to get back to reality.
BOOM shaka lakka!
I was just getting ready to call Sprint and go into a repair facility with some crazy story about how this all happened.
Thank you!:good::good::good:
Time to do some serious reading before I attempt that again.
Original Sprint CID number?
Magnum_Enforcer said:
Anytime, glad to help :thumbup:
Click to expand...
Click to collapse
Okay so I did originally mess up rooting and flashing my HTC One m8 sprint edition. Since that day I succesfully (After 8 hours of horrible things) got it back to factory reset with the exception of S-off and the super cid. The thing is I dont want the super Cid because i DO want the OTA Update. The problem is I was a noob and forgot to save the original sprint CID number. So long story short. Does anyone have the Sprint CID number. Unless the Super CID number gets OTA updates for Stock. PLease and Thanks
cboy1234 said:
Okay so I did originally mess up rooting and flashing my HTC One m8 sprint edition. Since that day I succesfully (After 8 hours of horrible things) got it back to factory reset with the exception of S-off and the super cid. The thing is I dont want the super Cid because i DO want the OTA Update. The problem is I was a noob and forgot to save the original sprint CID number. So long story short. Does anyone have the Sprint CID number. Unless the Super CID number gets OTA updates for Stock. PLease and Thanks
Click to expand...
Click to collapse
SPCS_001: standard Sprint M8
SPCS_004: Harman/Kardon version M8
I have SuperCID and still receive OTA notifications.
Update to reset stock htc one m8
So after doing more research I found that the image that I grabbed for stock android came from a H/K Edition. In fact the phone identifies itself as the as the Harmon edition ( I got the RUU from here http://forum.xda-developers.com/showthread.php?t=2729173) I was curious as you said that you yourself got OTA updates. Aside from lollipop, which updates did you receive. I only ask because I have heard of phones bricking up after doing an update and then something going wrong because they tampered with their tech. I DO want lollipop, but if it means losing my phone, then it is obviously not worth it.
ALSO looking at that website, I have verified that I got the NON-H/K edition....I am at a loss, I can try flashing it again, but honestly, I hate even looking at fastboot or any bootloader for the time being. Push comes to shove I will go down the rabbit hole again, but I do not want to risk a brick like before.
SIDENOTE: Not sure if its significant, but after flashing that RUU, I lost the weather widget at the top of blinkfeed, It only shows something such as "HIGHLIGHTS" If you would like I can post screen shots.
I am sorry to be such a noob and/or burden, and if you can help i would very much appreciate that if not, could you please direct me to a place where I could figure it out. Possibly a link or a person.
PLEASE AND THANKS!!!
cboy1234 said:
So after doing more research I found that the image that I grabbed for stock android came from a H/K Edition. In fact the phone identifies itself as the as the Harmon edition ( I got the RUU from here http://forum.xda-developers.com/showthread.php?t=2729173) I was curious as you said that you yourself got OTA updates. Aside from lollipop, which updates did you receive. I only ask because I have heard of phones bricking up after doing an update and then something going wrong because they tampered with their tech. I DO want lollipop, but if it means losing my phone, then it is obviously not worth it.
ALSO looking at that website, I have verified that I got the NON-H/K edition....I am at a loss, I can try flashing it again, but honestly, I hate even looking at fastboot or any bootloader for the time being. Push comes to shove I will go down the rabbit hole again, but I do not want to risk a brick like before.
SIDENOTE: Not sure if its significant, but after flashing that RUU, I lost the weather widget at the top of blinkfeed, It only shows something such as "HIGHLIGHTS" If you would like I can post screen shots.
I am sorry to be such a noob and/or burden, and if you can help i would very much appreciate that if not, could you please direct me to a place where I could figure it out. Possibly a link or a person.
PLEASE AND THANKS!!!
Click to expand...
Click to collapse
I don't actually install the OTA I flash the previous version stock rom and download the OTA, then pull it from my phone so the devs can use it to build roms and pull the firmware.
It's pretty hard to brick these devices unless you do something really crazy. As long as you can get to recovery or bootloader it's only soft bricked meaning it can be saved.
I would suggest changing your CID back to stock
Code:
fastboot oem writecid SPCS_001
Then run the latest RUU that will put you where you need to be to take the OTA when it comes.