I want convert my M9 Hima_Whl Sprint To Other version,developer editio for example,but cant flash any RUU because flash failed,i have unlocked bootloader and S-Off Supercid.
I want recover my phone trying flashing other RUU,because im make downgrade from 7.0 to 6.0 and get "Unknow Imei And Baseband" and cant make calls o send sms.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PD.My M9 its rare,because this version is not for sale,its a prototype device,but its functional.
In short, you can not. Attempting to use any firmware not made specifically for a CDMA model (like yours) will almost certainly damage your phone, possibly irreparably.
You can read about the why of this in the readme thread, particularly in device conversion section (post #4) and RUU section (post #5).
computerslayer said:
In short, you can not. Attempting to use any firmware not made specifically for a CDMA model (like yours) will almost certainly damage your phone, possibly irreparably.
You can read about the why of this in the readme thread, particularly in device conversion section (post #4) and RUU section (post #5).
Click to expand...
Click to collapse
Thanks a lot....But,can help me to repair imei and baseband? or can put a link for a thread for repair this error? only want recover my device.
Panzer_88 said:
Thanks a lot....But,can help me to repair imei and baseband? or can put a link for a thread for repair this error? only want recover my device.
Click to expand...
Click to collapse
Hmm. Let's put a hold on flashing anything until we understand what has been done. Could you walk through the steps of what you've done with your phone?
- what is the current state (bootloader locked/unlocked, S-ON/S-OFF, rooted/unrooted, OS/firmware version)?
- what is the current CID & MID?
computerslayer said:
Hmm. Let's put a hold on flashing anything until we understand what has been done. Could you walk through the steps of what you've done with your phone?
- what is the current state (bootloader locked/unlocked, S-ON/S-OFF, rooted/unrooted, OS/firmware version)?
- what is the current CID & MID?
Click to expand...
Click to collapse
i got unknow imei and baseband after downgrade from android 7.0 to 6.0
My bootloader is Unlocked and S-off latest version of firmware sprint 3.41.651.41 6.0 Unrooted
have supercid 11111111 and mid 0PJA20000
Panzer_88 said:
i got unknow imei and baseband after downgrade from android 7.0 to 6.0
My bootloader is Unlocked and S-off latest version of firmware sprint 3.41.651.41 6.0 Unrooted
have supercid 11111111 and mid 0PJA20000
Click to expand...
Click to collapse
Okay, so you need to read the readme thoroughly, specifically the first five posts. Yes, it's a lot. Yes, it's worth spending the 1/2 hour to familiarize yourself with what you're doing.
Essentially your only hope is to try to restore your phone to stock. You are fortunate in that there is a RUU executable (not zip file, though you could follow the instructions later in the readme thread to create your own) provided for your device from Sprint.
In it's current state - with the CID and MID combination you have - the RUU executable will not recognize your phone as compatible and will refuse to install. You'll need to change the CID to match your SKU (651) in order to apply the RUU.
Since you've attempted to flash an incompatible RUU, this may not fix your phone. But it's your only shot, short of paying someone to take a look at your phone (see the readme thread).
---------- Post added at 12:46 AM ---------- Previous post was at 12:26 AM ----------
I've gone ahead and extracted the RUU zip from the Sprint RUU executable. I'm happy to share the file with you from my Google drive (I'm uploading now) - but in the meantime I'd like to re-iterate my exhortation to read through at least the first five posts of the readme thread.
Panzer_88 said:
i got unknow imei and baseband after downgrade from android 7.0 to 6.0
My bootloader is Unlocked and S-off latest version of firmware sprint 3.41.651.41 6.0 Unrooted
have supercid 11111111 and mid 0PJA20000
Click to expand...
Click to collapse
Supercid is no longer recognised. You MUST use a proper cid with a matching mid.
To update to nougat you will probably need to reset back to stock and take the ota if it exists. Be very careful about flashing firmware and roms. CDMA phones may not agree with gsm firmware and roms.
Beamed in by telepathy.
shivadow said:
Supercid is no longer recognised. You MUST use a proper cid with a matching mid.
To update to nougat you will probably need to reset back to stock and take the ota if it exists. Be very careful about flashing firmware and roms. CDMA phones may not agree with gsm firmware and roms.
Beamed in by telepathy.
Click to expand...
Click to collapse
I change te cid to the original,can flash the ruu,all process ok,but can recover the baseband and the imei!
Im try with fastboot getvar all and can see the baseband and imei its ok,but in the device say Unknow
computerslayer said:
Okay, so you need to read the readme thoroughly, specifically the first five posts. Yes, it's a lot. Yes, it's worth spending the 1/2 hour to familiarize yourself with what you're doing.
Essentially your only hope is to try to restore your phone to stock. You are fortunate in that there is a RUU executable (not zip file, though you could follow the instructions later in the readme thread to create your own) provided for your device from Sprint.
In it's current state - with the CID and MID combination you have - the RUU executable will not recognize your phone as compatible and will refuse to install. You'll need to change the CID to match your SKU (651) in order to apply the RUU.
Since you've attempted to flash an incompatible RUU, this may not fix your phone. But it's your only shot, short of paying someone to take a look at your phone (see the readme thread).
---------- Post added at 12:46 AM ---------- Previous post was at 12:26 AM ----------
I've gone ahead and extracted the RUU zip from the Sprint RUU executable. I'm happy to share the file with you from my Google drive (I'm uploading now) - but in the meantime I'd like to re-iterate my exhortation to read through at least the first five posts of the readme thread.
Click to expand...
Click to collapse
Im changed to original cid and flashed the ruu again,but cant recover the imei and baseband...With fastboot getvar all can see the imei and base and its ok...
Mmm....One friend have another M9 same of my phone,its the same(M9 Prototype) Can dump all system Rom from this phone? Same device HimaWhl and its updated to android 7.0 and work fine.
Another thing.
Have a battery drain and overheated device after to downgrade.
Related
I was lucky enough to have a s-off/supercid unit, was previously on a carrier ROM then flashed the 1.29.401.7 RUU. So today I see .11 has been released OTA and go to update. It downloads fine, verifies the update then this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've tried it three times upon three reboots and same message. I'm not sure if it is HTCDev unlocked but it isn't rooted
Have any other s-off owners encountered this? If not, then move along and ignore me...
Where did you get an s-off/supercid handset from?
farnsbarns said:
Where did you get an s-off/supercid handset from?
Click to expand...
Click to collapse
Basically got a pre-retail unit from a local carrier
P1n3apqlExpr3ss said:
Basically got a pre-retail unit from a local carrier
Click to expand...
Click to collapse
How did you wangle that? Did they send it by mistake?
farnsbarns said:
How did you wangle that? Did they send it by mistake?
Click to expand...
Click to collapse
Got chosen to write a series of posts about the One X for a blog sponsored by the carrier, part of that is a free phone. Oh and I'm sure the fact we got it a week or two ahead of the local launch helped as well
Might be best you stop trying to do any updates bro, and make yourself known to the good folks in this thread
http://forum.xda-developers.com/showthread.php?t=1604300
PS, can you post screen shot of your fastboot screen??
777ace said:
Might be best you stop trying to do any updates bro, and make yourself known to the good folks in this thread
http://forum.xda-developers.com/showthread.php?t=1604300
PS, can you post screen shot of your fastboot screen??
Click to expand...
Click to collapse
Posted in that thread many times offering any help, noticed a post in there replying to another guy with s-off and apparently we're not much help anyway
I see. All good, just thought you might have held the holy grail...
Actually, you could be of help. Send me your phone and I'll send mine, that'd be a HUGE help!!
Well the thing is. Your phone maybe SuperCID but the SN still belongs to a branded phone. Maybe this makes the confusen... Just wait for the full RUU and flash that one.
Hmz, just checked the firmware.zip and seen this command: erasebcid: 1
NVM, this command is also present in older OTA.
xmoo said:
Well the thing is. Your phone maybe SuperCID but the SN still belongs to a branded phone. Maybe this makes the confusen... Just wait for the full RUU and flash that one.
Click to expand...
Click to collapse
What do you mean by SN?
Going to try and get someone I know to try and replicate it, s-off with Asia unlocked unit
Just got this reply from HTC. Firstly I am not rooted (at least last time I checked). Secondly I am going to check whether it is HTCDev unlocked when I get home. Does being HTCDev unlocked mean I cannot get OTA updates?
Thanks for contacting HTC.
We understand that you have some concern with regard to updating your phone’s software. Please allow us to discuss your concern and assist you.
HTC manufactures each Android phone to the exact specifications as set by Google, the platform’s developer. The partner mobile operators who distribute a said phone model then customize the software for use in their respective networks. This is why the phone’s warranty is automatically void if the default phone software has been modified in any way.
Based on your email, you have rooted your phone and installed custom or modified software. In this case, please understand that you will not be able to receive or install the latest software that will be release by your dealer. Any updates you will be receiving will come from the developer of the modified software. If you want to update your HTC One X software, please contact the developer of the European RUU.
The only way you can restore the phone’s original software is to go through your dealer where you purchased the phone or its authorized service center and have it reinstalled for a fee. This is needed so you can download and install the latest software released by your dealer. Please be advised that according to the dealer’s terms and conditions, any modification to the default phone software automatically voids the warranty. However, if you have the software reinstalled by an authorized service center, you will still have a shorter service warranty in effect (the standard warranty being already voided).
Important: Please be advised that HTC distributes handsets through our partner mobile operators which we have contracts with. Our partner mobile operators also determine the software and specifications for the particular handset model they are distributing. Any queries regarding repair, assessments, replacements, upgrades and warranty claims are best discussed with your authorized dealer. Please be reminded to back up your phone’s data before going to your dealer.
Click to expand...
Click to collapse
P1n3apqlExpr3ss said:
Just got this reply from HTC. Firstly I am not rooted (at least last time I checked). Secondly I am going to check whether it is HTCDev unlocked when I get home. Does being HTCDev unlocked mean I cannot get OTA updates?
Click to expand...
Click to collapse
No, it does not.
Sent from my HTC One X using xda premium
^ Thought that might be the case. I am locked and I am not rooted, yet this occurs.
Plus my reply to HTC's above message ^^^
Hi,
In reply to your reply... my One X is s-off/SuperCID, meaning I can flash whatever RUU I wish and it should get OTA updates for that region, as it did (except it fails). As far as I am concerned there is no trace on the phone linking it back to Telecom NZ at all, except possibly the IMEI - does this affect the installation of OTA updates?
I have not HTCDev unlocked, nor rooted the phone. It is merely s-off, thanks to HTC most likely. Within the bootloader it says I am locked, not unlocked or relocked, and apps like superuser or mybackup root do not work - as expected. The 1.29.401.7 RUU is signed by HTC and comes from HTC themselves, it isn't something from a custom ROM developer, the RUU I ran - and currently have on my phone - is 100% stock Android 4/Sense 4.0.
What I am trying to say, I effectively have an unlocked European One X (that is s-off) yet fails to install European OTAs because apparently I have "modified software". Doesn't sound right if you ask me.
Cheers
Click to expand...
Click to collapse
You're emailing first line support at HTC, who probably have NO idea what being S-OFF is, and are just going to give you a generic answer to anything you send them. Don't waste your time
You said you changed your CID to HTC__001 in a past post - have you changed it back to Super CID? If not, do it and try again
Otherwise, just flash the RUU. And for the record there's someone in the UK with an S-OFF handset who got .11 OTA with no issues (and has never changed the CID at any point)
According to CIDGetter I am still SuperCID, scrolling down to ro.aa.maincid is HTC_001, the update region I presume, so I have no need to change it back to SuperCID
Would really prefer update OTA (or flash the update.zip, how do I do this? Im sure I've downloaded it enough times) since I can't be bothered unlocking and rooting for titanium backup
Good to hear it's perhaps just me then
You don't need to unlock to backup, there's a thread in general on how to do it via adb
Cheers for the tip, forgot about that
As for the guy that did manage to update, was he originally HTC_001 (update region) anyway? I still haven't ruled out that carrier and asia phones will have trouble once s-off is achieved, they flash the EU RUU and expect OTA updates only to get the same problem as me
Nope, he's never touched it so it was always 11111111 - the ro.aa.maincid is irrelevent as it's not the CID
Try this:
1. Connect in fastboot
2. Run 'fastboot getvar cid' and see what comes up
If it's 11111111 you have Super CID, if it's HTC_001 it's not a real CID, if it's HTC__001 then you have the unbranded EU CID
P1n3apqlExpr3ss said:
According to CIDGetter I am still SuperCID, scrolling down to ro.aa.maincid is HTC_001, the update region I presume, so I have no need to change it back to SuperCID
Would really prefer update OTA (or flash the update.zip, how do I do this? Im sure I've downloaded it enough times) since I can't be bothered unlocking and rooting for titanium backup
Good to hear it's perhaps just me then
Click to expand...
Click to collapse
Think it's meant to be HTC__001 not HTC_001 ie 2 underscores.
Maybe this could be the reason?
I wanted to unlock my DHD's bootloader and flash a custom rom on it with the S-On method which require me to manually flash the boot everytime i flash a rom.
But i was unable to unlock my bootloader due to i was unable to get the identifier token from fastboot... I check on HTC dev website and it require me to upgrade my bootloader, yet again... failed!
I also tried the bootloader unlocking tool and it automatically download PD9810000_Ace_Sense30_S_hboot_2.00.0029 RUU for me and the result also same as the one i downloaded from HTC dev
Here are some pictures:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am on HBOOT version 2.00.0027, not sure if it was the latest though
Currently i m using 3.13.707.4
As i know the previous owner did unlock and flash a custom rom on it before, and later he send it back to HTC service centre to flash it back to stock gingerbread
Any help / suggestions are appreciated and welcomed
Should download a RUU and reflash the phone?
did you already tried flashing it with different method...
you can read a guide in here..., this thread guide for htc sensation thread, but the guide is the same as for dhd too (but don't rename it like PG58IMG.zip for DHD..because this name code for sensation only, for DHD just rename it PD98IMG.zip)
just read guide especially at step 4.1 and 4.4, 4.4.1, 4.4.2
hope this help..and good luck..
JJeamy said:
did you already tried flashing it with different method...
you can read a guide in here..., this thread guide for htc sensation thread, but the guide is the same as for dhd too (but don't rename it like PG58IMG.zip for DHD..because this name code for sensation only, for DHD just rename it PD98IMG.zip)
just read guide especially at step 4.1 and 4.4, 4.4.1, 4.4.2
hope this help..and good luck..
Click to expand...
Click to collapse
Thanks for your reply bro... now should i flash the RUU which contains the full ROM or just with the HBOOT?
boonwuilow said:
Thanks for your reply bro... now should i flash the RUU which contains the full ROM or just with the HBOOT?
Click to expand...
Click to collapse
no..you don't needed flashing a full RUU...
just upgrade file firmware / hboot from the htc site that you're already download it..(this is will update it your hboot to version 2.00.0029)
you can try it in two way method..
1. flashing it PD98IMG.zip with fastboot method...
2. flashing it that loaded PD98IMG.zip file via bootloader from your sdcard..
JJeamy said:
no..you don't needed flashing a full RUU...
just upgrade file firmware / hboot from the htc site that you're already download it..(this is will update it your hboot to version 2.00.0029)
you can try it in two way method..
1. flashing it PD98IMG.zip with fastboot method...
2. flashing it that loaded PD98IMG.zip file via bootloader from your sdcard..
Click to expand...
Click to collapse
Ok i will try that later...
So basically the bootloader that can't support HTC dev unlock (or those that require a further update) are those without the "LOCKED" or "RELOCKED" status right?
And is the AAHK2 by Phiber2000 safe to unlock, s-off and root my phone?
http://forum.xda-developers.com/showthread.php?t=2367322
boonwuilow said:
Ok i will try that later...
So basically the bootloader that can't support HTC dev unlock (or those that require a further update) are those without the "LOCKED" or "RELOCKED" status right?
And is the AAHK2 by Phiber2000 safe to unlock, s-off and root my phone?
http://forum.xda-developers.com/showthread.php?t=2367322
Click to expand...
Click to collapse
yap..when htc launching the latest ota update (full RUU for DHD) just had a version of bootloader 2.00.0027, that time the htc itself is not yet officially opening/launching for supporting unlocking the bootloader..because of that..the version 2.00.0027 is not yet support for unlocking..and that's why don't have a state of LOCKED in the top of that bootloader too..so to unlocking you must update bootloader first to 2.00.0029 from that website..
AAHK2 is a simple way to fully rooting and had eng hboot for your DHD...i think that's a safe too..provide it if you follow all step carefully and follow all the rules that are required from that script it self...and because i've already using that script for 6 DHD..all the result is success..even with some of that DHD had some of little troubled while running that script..but i'm still can handle it..
just a advice from me...before you begin running that script..just read carefully and understand it all inside that thread (especially about a branded sdcard that are mentioned in there thread)..and prepared all stuff that are required..
good luck...
boonwuilow said:
I wanted to unlock my DHD's bootloader and flash a custom rom on it with the S-On method which require me to manually flash the boot everytime i flash a rom.
But i was unable to unlock my bootloader due to i was unable to get the identifier token from fastboot... I check on HTC dev website and it require me to upgrade my bootloader, yet again... failed!
I also tried the bootloader unlocking tool and it automatically download PD9810000_Ace_Sense30_S_hboot_2.00.0029 RUU for me and the result also same as the one i downloaded from HTC dev
Here are some pictures:
I am on HBOOT version 2.00.0027, not sure if it was the latest though
Currently i m using 3.13.707.4
As i know the previous owner did unlock and flash a custom rom on it before, and later he send it back to HTC service centre to flash it back to stock gingerbread
Any help / suggestions are appreciated and welcomed
Should download a RUU and reflash the phone?
Click to expand...
Click to collapse
If your build vesion is not supported to update the bootloader, you will need create a goldcard in order to flash a RUU with a build version that supports unlocking. That is the way...takes time and S-OFF is a better option IMO
JJeamy said:
yap..when htc launching the latest ota update (full RUU for DHD) just had a version of bootloader 2.00.0027, that time the htc itself is not yet officially opening/launching for supporting unlocking the bootloader..because of that..the version 2.00.0027 is not yet support for unlocking..and that's why don't have a state of LOCKED in the top of that bootloader too..so to unlocking you must update bootloader first to 2.00.0029 from that website..
AAHK2 is a simple way to fully rooting and had eng hboot for your DHD...i think that's a safe too..provide it if you follow all step carefully and follow all the rules that are required from that script it self...and because i've already using that script for 6 DHD..all the result is success..even with some of that DHD had some of little troubled while running that script..but i'm still can handle it..
just a advice from me...before you begin running that script..just read carefully and understand it all inside that thread (especially about a branded sdcard that are mentioned in there thread)..and prepared all stuff that are required..
good luck...
Click to expand...
Click to collapse
glevitan said:
If your build vesion is not supported to update the bootloader, you will need create a goldcard in order to flash a RUU with a build version that supports unlocking. That is the way...takes time and S-OFF is a better option IMO
Click to expand...
Click to collapse
I have successfully unlock the bootloader by the method @JJeamy show me, thank you very much for guiding me on how to unlock it :good::good::good:
Actually the process isn't very hard just go to HTC dev and download the bootloader that match your build number and manually flash the update by using fastboot and proceed to unlock the phone as instructed on htc dev
boonwuilow said:
I have successfully unlock the bootloader by the method @JJeamy show me, thank you very much for guiding me on how to unlock it :good::good::good:
Actually the process isn't very hard just go to HTC dev and download the bootloader that match your build number and manually flash the update by using fastboot and proceed to unlock the phone as instructed on htc dev
Click to expand...
Click to collapse
glad to hear that...and congrats.. :good:
Awesome
@JJeamy
I'm proud that you wrote that much,if i was in your place i would only redirects @boonwuilow to that chinese software the one i told you easy way to unlock bootloader.
Yesterday I bought this HTC One M8, but it feels like a downgrade next to my OPO. So I want to return it. Problem is that I unlocked the bootloader with HTCdev, made it s-off with firewater and rooted it. Is there an easy way to make everything stock again? Im on cm11 now but ive made a backup of the stock rom after I rooted it. So I can go back to that point. But how can I make my phone s-on and lock the bootloader?
EddyOS made a guide in the general section that you can follow "Return to 100% stock" or something similar to that. It's written for international unbranded versions but it'll be mostly the same for any device. Just download the correct nandroids(which you already have as mentioned) and recovery. You'll have to use the method in Scotty's thread(It's linked in that guide from EddyOS) to reset the "Tampered/Modified" text. Scotty also has a thread which will help with the locking of bootloader, to show it as "locked" and not "relocked". To go back S-ON you should use code in fastboot mode: fastboot oem writesecureflag 3 <<<Though it's generally not recommended to do this and return to S-ON as it might throw out a security flag on the device, could even brick it. Some people had success with it some not, I won't recommend it but it's your choice ultimately. Which is why I showed the command to do it but I take no responsibility for it either way.
Flash your stock backup before root and than fastboot flash stock recovery followed by relocking your bootloader. It's been said in other threads that some devices shipped S-off so I wouldn't worry to much about that (my opinion)
Alright so ill keep it s-off but I removed the tampered banner and locked the bootloader, but I still have SuperSU and root acces it seems. Is there a way to remove that?
Iniesta89 said:
Alright so ill keep it s-off but I removed the tampered banner and locked the bootloader, but I still have SuperSU and root acces it seems. Is there a way to remove that?
Click to expand...
Click to collapse
Your S-off so grab a stock non rooted ruu and use the external sdcard method or fastboot method
http://forum.xda-developers.com/showthread.php?t=2824048
Hi Jball thanks for your help. Ive been looking through thisfollowing thread but im not sure which one to choose. Ive got a Vodafone branded one with CID VOAPE17 HBOOT 3.16.0.0000
http://forum.xda-developers.com/showthread.php?t=2701376
jball said:
Your S-off so grab a stock non rooted ruu and use the external sdcard method or fastboot method
http://forum.xda-developers.com/showthread.php?t=2824048
Click to expand...
Click to collapse
My radio is 1.15.2133156.UA13G
What region are you in
Im in the Netherlands
jball said:
What region are you in
Click to expand...
Click to collapse
Im in the Netherlands
Can you take a screenshot of your about phone in settings
---------- Post added at 02:29 PM ---------- Previous post was at 02:14 PM ----------
@lniesta89
Post #3 has your OTA update witch should set you back to complete stock
http://forum.xda-developers.com/showthread.php?t=2696514
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
jball said:
What region are you in
Click to expand...
Click to collapse
jball said:
Can you take a screenshot of your about phone in settings
---------- Post added at 02:29 PM ---------- Previous post was at 02:14 PM ----------
@lniesta89
Post #3 has your OTA update witch should set you back to complete stock
http://forum.xda-developers.com/showthread.php?t=2696514
Click to expand...
Click to collapse
Jesus christ, this is annoying af. I downloaded the zip, unzipped it. Put the folder in my TWRP map and when I try to restore it in TWRP i dont see anything.... wtf am i doin wrong?
Iniesta89 said:
Jesus christ, this is annoying af. I downloaded the zip, unzipped it. Put the folder in my TWRP map and when I try to restore it in TWRP i dont see anything.... wtf am i doin wrong?
Click to expand...
Click to collapse
TWRP uses your phones serial in patch, that's why you cannot see the backup when trying to restore.
Do the following...Boot to TWRP, Backup, choose something small like boot, swipe to backup.
Reboot to OS, open a file explorer and look for TWRP\BACKUPS\SH***\2014-11-16---\
Delete all files from here and put there the downloaded files.
Reboot to TWRP and try to restore now. You should be able to see your backup
And it doesn't help you to download the OTA.zip that is provided in post 3 of that thread, it's not a nandroid backup it's an OTA update and it will NOT take you back to stock. You need all the system files etc from a nandroid backup(1+ GB) vs OTA.zip(couple of MB's) huge difference. That you can find in the collection of stock backups thread made by MrHofs, it's also in the general section.
Hi guys,
My friend has given me his HTC One M8 Bell to fix.
It's seems to be stuck in fastboot with S-ON
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As far as I know, he had cyanogenmod and twrp installed and was trying to return his phone to stock (not sure why) and installed the wrong RUU.
How can I repair his phone?
I'm researching as best as I can, but everything I'm finding requires S-OFF and I doubt he has the BIN file....
Thanks in advance.
eboy_gb said:
Hi guys,
My friend has given me his HTC One M8 Bell to fix.
It's seems to be stuck in fastboot with S-ON
As far as I know, he had cyanogenmod and twrp installed and was trying to return his phone to stock (not sure why) and installed the wrong RUU.
How can I repair his phone?
I'm researching as best as I can, but everything I'm finding requires S-OFF and I doubt he has the BIN file....
Thanks in advance.
Click to expand...
Click to collapse
You shouldn't need S-OFF if you are using the correct RUU... so that could be the first thing you could try.
Another would be to unlock the phone through fastboot, then re-flash custom recovery... through custom recovery flash a nandroid of stock HTC Sense. Then through fastboot again flash stock recovery. Then wait for all the OTA updates to arrive.
Once you have installed all OTA updates you have two choices....relock the device, or use it stock while keeping the bootloader unlocked for future flashing goodness.
Kyuubi10 said:
You shouldn't need S-OFF if you are using the correct RUU... so that could be the first thing you could try.
Another would be to unlock the phone through fastboot, then re-flash custom recovery... through custom recovery flash a nandroid of stock HTC Sense. Then through fastboot again flash stock recovery. Then wait for all the OTA updates to arrive.
Once you have installed all OTA updates you have two choices....relock the device, or use it stock while keeping the bootloader unlocked for future flashing goodness.
Click to expand...
Click to collapse
UPDATE - I got S-OFF back on the phone and booted into recovery. From there, I decided to simply reboot the system, but now I'm stuck at the Cyanogenmod splashscreen. So back to TWRP....
I don't really understand what RUU's are. The last HTC I had was Desire-Z....
eboy_gb said:
UPDATE - I got S-OFF back on the phone and booted into recovery. From there, I decided to simply reboot the system, but now I'm stuck at the Cyanogenmod splashscreen. So back to TWRP....
I don't really understand what RUU's are. The last HTC I had was Desire-Z....
Click to expand...
Click to collapse
Well...from what the image you pasted in the OP showed you had no system to reboot into. So that was definitely a wrong move.
Notice the OS - "empty space".....well that is not a good sign.
If you can access TWRP the download a nandroid of stock, and follow the advice I already gave above.
Flash stock nandroid 4.25/4.20, from TWRP, then from fastboot flash stock recovery.
Reboot and wait for OTA updates.
All is well, got the running properly now - thanks everyone!
eboy_gb said:
All is well, got the running properly now - thanks everyone!
Click to expand...
Click to collapse
Great!! Remember to add [SOLVED] in the title, so others know that here they can find solutions to common problems
Kyuubi10 said:
Well...from what the image you pasted in the OP showed you had no system to reboot into. So that was definitely a wrong move.
Notice the OS - "empty space".....well that is not a good sign.
Click to expand...
Click to collapse
Incorrect. OS being empty was caused by a bug in some earlier versions of TWRP. Nothing to be too concerned about at all.
xunholyx said:
Incorrect. OS being empty was caused by a bug in some earlier versions of TWRP. Nothing to be too concerned about at all.
Click to expand...
Click to collapse
Uhm....never knew it was an actual bug, i run across it once when i corrupted my system quite a few months.
Do u know the process to recreate the bug... Trying to see if it was the same bug which i experienced, or a variation thereof.
Sent from my htc_m8 using XDA Labs
Kyuubi10 said:
Uhm....never knew it was an actual bug, i run across it once when i corrupted my system quite a few months.
Do u know the process to recreate the bug... Trying to see if it was the same bug which i experienced, or a variation thereof.
Click to expand...
Click to collapse
Corrupting system won't affect the OS number on the bootloader screen. "OS" is a bit misleading, it actually indicates the firmware number, not the ROM version.
The bug is easily reproduced by flashing certain TWRP versions (not sure exactly which ones). Its very common. We see this pop up by folks almost on a daily basis (OS number blank) especially folks using older TWRP versions.
---------- Post added at 09:31 AM ---------- Previous post was at 09:28 AM ----------
Kyuubi10 said:
Great!! Remember to add [SOLVED] in the title, so others know that here they can find solutions to common problems
Click to expand...
Click to collapse
Additionally, its not clear whether your suggestion is what actually worked for him (and exactly what nandroid build, etc.). OP should post the solution that worked, 1) for benefit of "helpers" like you, to confirm your fix is what worked; and 2) for the benefit of others that may run into the same issue.
---------- Post added at 09:35 AM ---------- Previous post was at 09:31 AM ----------
Kyuubi10 said:
Well...from what the image you pasted in the OP showed you had no system to reboot into. So that was definitely a wrong move.
Notice the OS - "empty space".....well that is not a good sign.
Click to expand...
Click to collapse
The phone would not boot since the bootloader was relocked. This is what happens when you relock by definition, as relocking expects RUU to be run.
---------- Post added at 09:41 AM ---------- Previous post was at 09:35 AM ----------
eboy_gb said:
I don't really understand what RUU's are. The last HTC I had was Desire-Z....
Click to expand...
Click to collapse
RUU existing for the Desire Z (I had the same phone); and in fact for as long as HTC has been making Android devices.
RUU = ROM Update Utility
Its usually a Windows executable (although the zip format can be extracted to work with fastboot flash, or put right on an SD card) that will completely re-image the phone to stock firmware and software. You need to run the RUU that matches the phones carrier version (CID) and model (MID), and not all versions have RUU. Otherwise, the RUU will fail and not install anything.
RUU also requires a locked or relocked bootloader (although this requirement is bypassed with s-off).
RUU will also wipe any user data on the phone (including internal storage "media").
Hello, guys!
I write here for help as HTC's customer support can't help me!
As title tell you I am unable to update firmware.
Everytime I receive notification that an update is available and that I should update my firmware.
Unfortunely, I get error
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To be honest, I am using original version and didn't even tried another version on my HTC
Practically, I don't understand why currently version which I never changed can tell me that I am using a modified version
In order to solve this problem I tried to factory reset, but without any success
Would be very glad if someone could help me!
Thank you!
EDIT: I am sorry for my worst English! I hope you understand what I wrote here. Thanks!
Winserity said:
To be honest, I am using original version and didn't even tried another version on my HTC
Practically, I don't understand why currently version which I never changed can tell me that I am using a modified version
Click to expand...
Click to collapse
The phone's software has almost certainly been modified, if not by you then a previous owner or seller. What was the condition of the phone when you bought it (from another user, 3rd party vendor, etc.)?
We'll need a lot more info, in order to help you. Do you know how to use fastboot?
Do you know how to get to the bootloader screen? If so, does it say UNLOCKED, LOCKED or RELOCKED near the top?
Does it say s-on or s-off?
What number does it say for OS number? If nothing, what does it say for hboot number and radio baseband number?
Winserity said:
In order to solve this problem I tried to factory reset, but without any success
Click to expand...
Click to collapse
Factory reset won't do anything in this case. Factory reset just wipes user data, and doesn't touch the OS/system.
---------- Post added at 02:42 PM ---------- Previous post was at 02:41 PM ----------
Winserity said:
I am sorry for my worst English! I hope you understand what I wrote here. Thanks!
Click to expand...
Click to collapse
Your English is fine so far! :good:
redpoint73 said:
The phone's software has almost certainly been modified, if not by you then a previous owner or seller. What was the condition of the phone when you bought it (from another user, 3rd party vendor, etc.)?
We'll need a lot more info, in order to help you. Do you know how to use fastboot?
Do you know how to get to the bootloader screen? If so, does it say UNLOCKED, LOCKED or RELOCKED near the top?
Does it say s-on or s-off?
What number does it say for OS number? If nothing, what does it say for hboot number and radio baseband number?
Factory reset won't do anything in this case. Factory reset just wipes user data, and doesn't touch the OS/system.
---------- Post added at 02:42 PM ---------- Previous post was at 02:41 PM ----------
Your English is fine so far! :good:
Click to expand...
Click to collapse
My sister bought it as a gift new HTC M8 from Amazon Store United States.
Bootloader screen give me this information:
*** Software status: Official ***
*** UNLOCKED ***
M8_UL PVT SHIP S-OFF
CID-11111111
HBOOT-3.19.0.0000
RADIO-1.25.214500021.06G
OpenDSP-v48.2.2-00564-M8974_FO.1211
OS-4.16.401.10
eMMC-boot 2048MB
Jan 15 2015,22:51:08.1
Winserity said:
My sister bought it as a gift new HTC M8 from Amazon Store United States.
Bootloader screen give me this information:
*** Software status: Official ***
*** UNLOCKED ***
M8_UL PVT SHIP S-OFF
CID-11111111
HBOOT-3.19.0.0000
RADIO-1.25.214500021.06G
OS-4.16.401.10
Click to expand...
Click to collapse
The phone is definitely not in factory stock condition. It's highly modified, having had it's bootloader unlocked, s-off, and made SuperCID. Possibly (probably?) modified by the seller, in order to remove any region or carrier branding.
You can probably use the Euro RUU to update the OS software/firmware. Use the instructions and files from here: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
I'd have to see more info to be sure. If you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
redpoint73 said:
The phone is definitely not in factory stock condition. It's highly modified, having had it's bootloader unlocked, s-off, and made SuperCID. Possibly (probably?) modified by the seller, in order to remove any region or carrier branding.
You can probably use the Euro RUU to update the OS software/firmware. Use the instructions and files from here: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
I'd have to see more info to be sure. If you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Click to expand...
Click to collapse
If the bootloader is UNLOCKED (for S-On device only), relock it with commands:
fastboot oem lock
fastboot reboot-bootloader
Click to expand...
Click to collapse
Is this step required if I have S-OFF and UNLOCKED?
I am sorry for asking such dumb asks! I just want to be sure at all!
EDIT:
Look there
Winserity said:
Is this step required if I have S-OFF and UNLOCKED?
I am sorry for asking such dumb asks! I just want to be sure at all!
Click to expand...
Click to collapse
It's not a dumb question. Others have been confused by the wording in the guide regarding relocking the bootloader.
You do not need to relock the bootloader. S-off bypasses the requirement for bootloader to be locked/relocked when running RUU. In other words, with s-off the RUU will run fine regardless of whether the bootloader is unlocked or locked.
I recommend you leave the bootloader unlocked, as it gives you more options if anything goes wrong.
Thanks for posting the getvar data. Either you knew how to do that already, or you are learning quickly! The info confirms that you should be able to use the RUU. It also appears to have been the US T-Mobile version (model ID 0P6B13000) that was modified to remove the carrier branding, and "convert" it to Euro version.
Unfortunately, I am unable to extract from RUU zip
I receive this kind of error
C:\Users\xxevi\Desktop\0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip: The archive is corrupt
C:\Users\xxevi\Desktop\0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip: Checksum error in C:\Users\xxevi\Desktop\0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed\dzdata_32g.img. The file is corrupt
EDIT:
Used function "Repair archive" and I am able to extract.
If there will be new information regarding my issue I will post there
EDIT 2:
After "FAILED" it automatically restart the same procedure
Still waiting for about 25-30 minutes
Is this ok?
EDIT 3:
To be honest, I am feeling scared x(
Can someone confirm that my phone isn't broke?
It's still showing "send `zip` ... (1687274KB)" more than a hour
Why is it taking too long?
Update:
Used OS Windows 7 and I flushed this RUU, but after fastboot reboot my HTC doesn't seems to switch on Android
Screenshot:
Right now, my HTC stucks at a white screen where is shown HTC One logo
Maybe it sounds dumb, but I can't even switch off phone.
I am able only to restart phone using Power + Volume UP
No any setup started after fastboot reboot
Winserity said:
Unfortunately, I am unable to extract from RUU zip
I receive this kind of error
C:\Users\xxevi\Desktop\0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip: The archive is corrupt
C:\Users\xxevi\Desktop\0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip: Checksum error in C:\Users\xxevi\Desktop\0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed\dzdata_32g.img. The file is corrupt
EDIT:
Used function "Repair archive" and I am able to extract.
Click to expand...
Click to collapse
It doesn't say anywhere in the instructions to extract anything! Follow the instructions exactly, and don't make up steps!
The zip is an encrypted archive. It's encrypted with HTC's encryptions keys, and there is no way for you to decrypt it (and there isn't any reason to!). That is why Windows thinks it is "corrupt" - but don't worry it isn't. You just flash the RUU, as is, and it will do the rest. Extracting anything will break the signature, and cause it to fail signature check (will not install).
---------- Post added at 09:13 AM ---------- Previous post was at 09:09 AM ----------
Error 90 is normal. It needs to be run twice as indicated. The message "flush again immediately" is a strange typo which HTC has maintained over numerous RUUs on different devices - it should say "flash again immediately. You need to run the command again to flash the RUU zip.
It's not completely clear for your description, if you extracted anything from the RUU zip and tried to flash it. Hopefully you didn't. Please describe in full detail, all the steps you performed, with the exact file names, commands, etc.
In the final I didn't extracted archive ZIP. But as you said I tried to repair archive cause I saw "The file is corrupt."
Anyway, I gave my HTC to one of my friend working right now on my HTC.
Tomorrow I will let you know if my problem is solved
Until that time I have to tell you thank you very much!
I really appreciate your attention to my issue
Winserity said:
Anyway, I gave my HTC to one of my friend working right now on my HTC.
Tomorrow I will let you know if my problem is solved
Click to expand...
Click to collapse
Do you have reason to believe your friend has more knowledge of this specific device than we do (or you doing the steps, with our guidance)?
Because HTC devices can be very nuanced (lots of differences from other Android devices). If he doesn't have specific experience with HTC devices (and even better, the M8 specifically) he might not be able to help, or even make the problem worse.
My friend solved problem by installing firmware version 6.12.1540.4
He used a ROM utility to solve this problem.
Wasn't easy for him at all, but in final I am glad
Now, I have last version installed for my HTC M8
Thanks for your help, redpoint73!
Wish everyone to avoid HTC phone problems =)
Hi all please I do need help on this same issue. I cannot install updates. I get the msg I am using a modified version of the software. Even though I never modified it myself but bought it that way, I tried to unroot it with an app I installed, but it says it's not even rooted. My phone is HTC Desire Eye and it's presently running on 4.4.4 Kitkat. Your assistance will be appreciated. Also I am less of a technical guy, so pls guide me on every step I may need to solve this like a newbie.
Thanks guys!