Hi I have an att m8 unlocked soff wanting to change to dev edition looked it up but alll threads are confusing can someone explain it to me a simple way please
EasIest way...change cid to BS_US001...run the 3.28.1540.5 ruu...done
Jacobz1996 said:
Hi I have an att m8 unlocked soff wanting to change to dev edition looked it up but alll threads are confusing can someone explain it to me a simple way please
Click to expand...
Click to collapse
Do I need to use fastboot or can I do it someway else cus I don't know how to use fastboot
Yes I suggest doing a little reading,to at least get started. No other way that I know of
Jacobz1996 said:
Do I need to use fastboot or can I do it someway else cus I don't know how to use fastboot
Click to expand...
Click to collapse
Couldn't he edited the RUUs android-info.txt to only include the BS_US001 CID essentially to where he won't have to use fastboot OEM writeCID ?
1) Plug phone into computer
2) Reboot into Hboot by restarting phone and quickly holding volume down
3) Select fastboot
4) Open CMD as admin and CD directory to where your ADB and Fastboot files are
5) run command fastboot oem devices to make sure phone is recognized
6) run command fastboot oem write cid BS_US001
7) run command fastboot reboot
8) Run RUU exe file from HTC
9) Done
You must have a folder that contains your fastboot and ADB files in it. Without those you won't get very far.
---------- Post added at 09:28 PM ---------- Previous post was at 09:22 PM ----------
jxcorex28 said:
Couldn't he edited the RUUs android-info.txt to only include the BS_US001 CID essentially to where he won't have to use fastboot OEM writeCID ?
Click to expand...
Click to collapse
Yes, but not as easy, and one really needs to learn this just as we all have, it will make you a better person at the end of the day, I promise. :good:
Its an exe,not the .zip files here and they are encrypted. So long story short no thats not doable.
Agreed folks need to learn at least the very basics of adb and fastboot commands.
jxcorex28 said:
Couldn't he edited the RUUs android-info.txt to only include the BS_US001 CID essentially to where he won't have to use fastboot OEM writeCID ?
Click to expand...
Click to collapse
---------- Post added at 07:46 PM ---------- Previous post was at 07:43 PM ----------
Number 6 is incorrect BS_US001 is correct cid. And as i said above android-info.txt file is encrypted,unless someone decrypts the zip it is not doable.
hack14u said:
1) Plug phone into computer
2) Reboot into Hboot by restarting phone and quickly holding volume down
3) Select fastboot
4) Open CMD as admin and CD directory to where your ADB and Fastboot files are
5) run command fastboot oem devices to make sure phone is recognized
6) run command fastboot oem write cid BS_001
7) run command fastboot reboot
8) Run RUU exe file from HTC
9) Done
You must have a folder that contains your fastboot and ADB files in it. Without those you won't get very far.
---------- Post added at 09:28 PM ---------- Previous post was at 09:22 PM ----------
Yes, but not as easy, and one really needs to learn this just as we all have, it will make you a better person at the end of the day, I promise. :good:
Click to expand...
Click to collapse
OK...good to know...I was able to edit the android-info.txt file from 2.12.1700.1 RUU to only include GOOGL001 and 0P6B17000 without any kind of problems unless the encryption/decryption lays on another level during hboot.
Yeah cannot edit any files in the exe rom.zip, can pull boot.img out but thats it without it saying its corrupted.
jxcorex28 said:
OK...good to know...I was able to edit the android-info.txt file from 2.12.1700.1 RUU to only include GOOGL001 and 0P6B17000 without any kind of problems unless the encryption/decryption lays on another level during hboot.
Click to expand...
Click to collapse
Ahhhh, I gotcha...
My bad on the CID, I knew I was missing part of it.
after i converted to dev edition my m8 battery life is horrible ive factory reset and everything and it still dont work
Jacobz1996 said:
after i converted to dev edition my m8 battery life is horrible ive factory reset and everything and it still dont work
Click to expand...
Click to collapse
There isn't enough info here for this post to be very meaningful in any way.
If you just did the RUU, and the battery life is "horrible" on the first day, its because the battery meter needs to be recalibrated after an RUU or ROM flash (and a factory reset prob doesn't help matter, either). Charge to full, than drain to about 10% or so, in order to set the "high" and "low" battery meter flags. Maybe you've been using the phone longer (and this isn't relevant) but as you've provided no detail or specifics, we can only guess.
Also, if you flashed the new LP Dev Edition RUU, its a new radio. So possibly reverting to an older radio may help. But again, you provide no details, so we don't even know what RUU you used.
For that matter, we don't know if you are using the AT&T network. If not, that may be your issue as well (as the Dev Ed is intended for use on AT&T's network).
Hi yes I am using the Att network and the problem is it's reallly Kathy and battery last like 6 hours with sot of 2 hrs and it says android os and Android system use half the battery
And I used the dev lp ruu
Jacobz1996 said:
Hi yes I am using the Att network and the problem is it's reallly Kathy and battery last like 6 hours with sot of 2 hrs and it says android os and Android system use half the battery
Click to expand...
Click to collapse
I gave a couple suggestions, so try those before typing any more poorly constructed run-on sentences.
Also, I have no idea who Kathy is. She must be a real drain.
I have done what u said and it hasn't worked. I apologize was at work and rushing . The Android os and android system are the ones that are draining the battery the most
Jacobz1996 said:
I have done what u said and it hasn't worked. I apologize was at work and rushing . The Android os and android system are the ones that are draining the battery the most
Click to expand...
Click to collapse
You tried flashing a different radio?
i dont know how to flash a different radio and since its lollipop wouldnt it cause issues if i went to an older radio
Jacobz1996 said:
i dont know how to flash a different radio and since its lollipop wouldnt it cause issues if i went to an older radio
Click to expand...
Click to collapse
Maybe, maybe not. I think some folks have reverted to radios in the past and claim better reception. Some folks have had issues. Its just an idea.
Or you can try the Euro or Asian LP radios. But I'd be surprised if it gave you better results on the AT&T network then the US Dev Ed radio.
http://forum.xda-developers.com/showpost.php?p=58306004&postcount=734
Instructions on how to flash radios on the first post of that same thread.
But you said you tried my suggestions, now you are saying you didn't try this one. So its frustrating to try to help someone when they give incomplete or incorrect information.
Related
Here's my situation. Got this new phone yesterday. I am (was) bootloader unlocked, s-on with htcdev method. Also am (was) using twrp for recovery. Then went looking for some roms... found one, moved it to the phone, wipe, blah, blah, done this before plenty on my old evo shift. Well, there was some problem, rom couldn't be installed, which is no problem for people who do regular nand backups. That was not me. So... stuck at htc screen.
Bottom line, after many hours of different ideas and methods, I've relocked the bootloader, downloaded an ruu, and I'm stuck. In hindsight I sort of backed myself into a corner, because though I supposedly needed to relock to run an ruu, now I can't get at twrp recovery. So I need help running the ruu from fastboot. In my searches, this seems possible, but it's not working for me. The phone is recognized, because when I enter into command "fastboot find devices" or whatever that was, a phone shows up. The .exe itself just won't open though. Tried running as administrator, tried compatibility mode, tried running it from the command line, each time it will give me the blue circley thing for about 5 or 10 seconds and then just do nothing.
I'm just out of ideas, feeling like I'm stuck here.
Remember: currently my screen reads TAMPERED RELOCKED Security Warning I'm in fastboot usb mode. Oh, and I tried to find the ruu to match my Hboot, but it currently shows 1.15.0000, and there is of course no ruu with that code, so I downloaded the newest one (2 point something)
Any help is appreciated
admsteff said:
Here's my situation. Got this new phone yesterday. I am (was) bootloader unlocked, s-on with htcdev method. Also am (was) using twrp for recovery. Then went looking for some roms... found one, moved it to the phone, wipe, blah, blah, done this before plenty on my old evo shift. Well, there was some problem, rom couldn't be installed, which is no problem for people who do regular nand backups. That was not me. So... stuck at htc screen.
Bottom line, after many hours of different ideas and methods, I've relocked the bootloader, downloaded an ruu, and I'm stuck. In hindsight I sort of backed myself into a corner, because though I supposedly needed to relock to run an ruu, now I can't get at twrp recovery. So I need help running the ruu from fastboot. In my searches, this seems possible, but it's not working for me. The phone is recognized, because when I enter into command "fastboot find devices" or whatever that was, a phone shows up. The .exe itself just won't open though. Tried running as administrator, tried compatibility mode, tried running it from the command line, each time it will give me the blue circley thing for about 5 or 10 seconds and then just do nothing.
I'm just out of ideas, feeling like I'm stuck here.
Remember: currently my screen reads TAMPERED RELOCKED Security Warning I'm in fastboot usb mode. Oh, and I tried to find the ruu to match my Hboot, but it currently shows 1.15.0000, and there is of course no ruu with that code, so I downloaded the newest one (2 point something)
Any help is appreciated
Click to expand...
Click to collapse
You can get the RUU here
This will help you get twrp and SuperSU back
It's really just an incompatible ruu? I'm about halfway through downloading the 1.22 version already, I thought I would try. I'll give it a shot, but wouldn't it give an error or something instead of just not responding on my pc?
admsteff said:
It's really just an incompatible ruu? I'm about halfway through downloading the 1.22 version already, I thought I would try. I'll give it a shot, but wouldn't it give an error or something instead of just not responding on my pc?
Click to expand...
Click to collapse
To be honest I have never flashed an RUU but I would think if you flashed the wrong one it could potentially brick your phone.
Thanks, these ruu files are so damn big, it's gonna be a few minutes. We'll see how it goes.
admsteff said:
Thanks, these ruu files are so damn big, it's gonna be a few minutes. We'll see how it goes.
Click to expand...
Click to collapse
You should try uploading them haha good luck.
Wait a minute, I noticed that the link you gave me is for a .zip file, while the one I'm downloading is for a .exe file? Isn't it supposed to be a self-installing program from windows? Do I need to be entering like a fastboot flash command for a zip instead because my phone is in fastboot and not fully booted? I can't believe I forgot the nand backup, this is like a whole wasted day of my life now...
admsteff said:
Wait a minute, I noticed that the link you gave me is for a .zip file, while the one I'm downloading is for a .exe file? Isn't it supposed to be a self-installing program from windows? Do I need to be entering like a fastboot flash command for a zip instead because my phone is in fastboot and not fully booted? I can't believe I forgot the nand backup, this is like a whole wasted day of my life now...
Click to expand...
Click to collapse
Like I said I have never ran an RUU so I'm not sure how it works you could PM om4 or read Don't Panic in the Q&A section
Yeah, problem is the same with the 1.22 ruu. It just wont execcute the program from my pc. Does anybody else have any ideas?
You only had to flash the kernel or bootimg. Seperately since your s-on...look for om4 guide " don't panic"...it should answer all of your questions...as far as the ruu make sure you're on the bootloader fastboot screen when you run it.
Sent from my EVO using xda premium
---------- Post added at 02:40 PM ---------- Previous post was at 02:37 PM ----------
http://forum.xda-developers.com/showthread.php?p=31102864
mrlakadaddy said:
You only had to flash the kernel or bootimg. Seperately since your s-on...look for om4 guide " don't panic"...it should answer all of your questions...as far as the ruu make sure you're on the bootloader fastboot screen when you run it.
Sent from my EVO using xda premium
---------- Post added at 02:40 PM ---------- Previous post was at 02:37 PM ----------
http://forum.xda-developers.com/showthread.php?p=31102864
Click to expand...
Click to collapse
Yes, I realize I dug myself into a hole by relocking. I just didn't want to learn how to put a new img on my phone (of course it was wiped, with a bad rom flashed) without having the thing mounted as a media device in the gui method. I'm sure it would have been quite easy, and that's kind of how the whole thing went, I wasn't scared enough and I just kept doing what I thought was the "easiest" way to get the phone back, and just was a dumbass overall. I read the "don't panic" guide. Maybe I missed something, but I don't think it would have got me out of the specific problem I made, once I was already in it. And I was certainly on fastboot usb when trying to run the ruu, and I had it in the right folder with fastboot.exe, etc.
Anyway, I never got it to work, but I ended up just returning the device to the retailer, and no questions were asked. It was cheating, I know. It could have been done, I was far from bricked, but when the phone is 1.5 days old and I can return it to a person who has no idea why my phone is "stuck", it was just too easy.
Thanks to everyone who tried to help
Hello all,
I'm Beginner with htc, i have problem with boot loop, i have done lot of search in the internet and i applied many procedures but i couldn't resolve the problem.
My phone is :
HTC EVO 3D GSM
SHOOTER_U PVT SHIP S-ON RL
HBOOT-1.53.0007
RADIO-11.25.3504.06_M
OpenDSP-v02.6.0.2226.00.02.02
eMMC-boot
Can i have your helps please?
Thank you very much
Best regards,
Dear beginner, this is HTC One (2013) forum
Sent from my Desire HD using Tapatalk 2
Which rom are you trying to boot? Because you are s-on you need to flash boot.img seperately in fastboot. OR you could use 4EXT recovery with smartflash turned on.
EM|NEM said:
Which rom are you trying to boot? Because you are s-on you need to flash boot.img seperately in fastboot. OR you could use 4EXT recovery with smartflash turned on.
Click to expand...
Click to collapse
Thank you very much for your replay,
Sorry for this late response, i was late because i have post my problem in oder thread at this link ( http://forum.xda-developers.com/showthread.php?p=38896827#post38896827 )
i have use all ruu.exe available in this site ( http://androidfiles.org/ruu/?dir=Shooter ) that have the same radios like my phone but it doesn't completed, the ruu.exe show me the error that my phone is non-compatible with this ruu,
The ruu that i have used from the ()are:
RUU_SHOOTER_U_ICS_35_S_hTC_Asia_WWE_3.28.707.1_Rad io_11.77.3504.00U_11.25.3504.06_M_release_264110_s igned.exe
RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio _11.77.3504.00U_11.25.3504.06_M_release_262714_sig ned.exe
RUU_SHOOTER_U_ICS_35_S_Rogers_WWE_3.28.631.1_Radio _11.77.3504.00U_11.25.3504.06_M_release_262715_sig ned.exe
Please, can you send me a link for any ruu or rom works with my phone described above,?
Thank you very much for your all collaborations and helps,
Best regards,
aagrou said:
Thank you very much for your replay,
Sorry for this late response, i was late because i have post my problem in oder thread at this link ( http://forum.xda-developers.com/showthread.php?p=38896827#post38896827 )
i have use all ruu.exe available in this site ( http://androidfiles.org/ruu/?dir=Shooter ) that have the same radios like my phone but it doesn't completed, the ruu.exe show me the error that my phone is non-compatible with this ruu,
The ruu that i have used from the ()are:
RUU_SHOOTER_U_ICS_35_S_hTC_Asia_WWE_3.28.707.1_Rad io_11.77.3504.00U_11.25.3504.06_M_release_264110_s igned.exe
RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio _11.77.3504.00U_11.25.3504.06_M_release_262714_sig ned.exe
RUU_SHOOTER_U_ICS_35_S_Rogers_WWE_3.28.631.1_Radio _11.77.3504.00U_11.25.3504.06_M_release_262715_sig ned.exe
Please, can you send me a link for any ruu or rom works with my phone described above,?
Thank you very much for your all collaborations and helps,
Best regards,
Click to expand...
Click to collapse
First of all, since you are using a smarphone, you should try and be a bit smart yourself. From a logical standpoint, those ruu have something different: on one says ASIA, on one EUROPE, and on one Rogers (which I can only assume it is linked to the us version, probably CDMA Evo 3D). If you live and bought the phone from Europe, it seems to me you should try the Europe RUU, right? If from Asia, the Asia one and so forth. Simple logic.
Secondly, if you would have read the vast quantity of threads and tutorials about this, you should have started your phone in hboot (Power button+Volume Down), select Fastboot by pressing the Power button, connect your phone to your pc, and in cmd write "fastboot oem lock". Also preferably a full wipe to be done in recovery. Once those steps were performed, the logically chosen RUU would work without any errors
posedatull said:
First of all, since you are using a smarphone, you should try and be a bit smart yourself. From a logical standpoint, those ruu have something different: on one says ASIA, on one EUROPE, and on one Rogers (which I can only assume it is linked to the us version, probably CDMA Evo 3D). If you live and bought the phone from Europe, it seems to me you should try the Europe RUU, right? If from Asia, the Asia one and so forth. Simple logic.
Secondly, if you would have read the vast quantity of threads and tutorials about this, you should have started your phone in hboot (Power button+Volume Down), select Fastboot by pressing the Power button, connect your phone to your pc, and in cmd write "fastboot oem lock". Also preferably a full wipe to be done in recovery. Once those steps were performed, the logically chosen RUU would work without any errors
Click to expand...
Click to collapse
thank you for your replay,
I have done all of that (wip all in recovery, lock my phone, install the ruu.exe). i did that for all the ruu.exe described above but it doesn't work :cryingerror ruu no compatible).
do you know any ruu work on my phone please?
my phone is HTC EVO 3D GSM(described above)
thank you a lot,
best regards
What usb cable are you using, and what usb itself? The ruu will not work on usb 1.1 or 3.0, only on usb 2.0 . If you use a pc, plug it in the back, directly in a usb from a mainboard, not in the front usb or through a hub
Which carrier was your phone on before? Make sure you use the correct RUU for your phone
EDIT: I see its already been explained
EM|NEM said:
Which carrier was your phone on before? Make sure you use the correct RUU for your phone
EDIT: I see its already been explained
Click to expand...
Click to collapse
thank you for your replay.
i don't know which is the first ruu of my phone, because i have got it with a bootloop problem.
do you know the original ruu for my phoene described above?
thank you for you collaborations.
best regards.
Boot into bootloader and run this command in cmd: "fastboot getvar cid"
this should give you your CID. might help in figuring out what your original rom was
---------- Post added at 12:32 AM ---------- Previous post was at 12:16 AM ----------
been googling your prob for a while and there is a possibility you had an arabic rom/firmware.
If you have HTC__J15 cid then run this RUU (the ics one): http://forum.xda-developers.com/showthread.php?t=1282840
EM|NEM said:
Boot into bootloader and run this command in cmd: "fastboot getvar cid"
this should give you your CID. might help in figuring out what your original rom was
---------- Post added at 12:32 AM ---------- Previous post was at 12:16 AM ----------
been googling your prob for a while and there is a possibility you had an arabic rom/firmware.
If you have HTC__J15 cid then run this RUU (the ics one): http://forum.xda-developers.com/showthread.php?t=1282840
Click to expand...
Click to collapse
thank you. i will test that thid night and i inform you tomorow
Best regards,
EM|NEM said:
Boot into bootloader and run this command in cmd: "fastboot getvar cid"
this should give you your CID. might help in figuring out what your original rom was
---------- Post added at 12:32 AM ---------- Previous post was at 12:16 AM ----------
been googling your prob for a while and there is a possibility you had an arabic rom/firmware.
If you have HTC__J15 cid then run this RUU (the ics one): http://forum.xda-developers.com/showthread.php?t=1282840
Click to expand...
Click to collapse
the cid that i got with the command "fastboot getvar cid" is "cid: VODAP304".
Where can i find the the original rom,
thank you a lot,
best regards,
aagrou said:
the cid that i got with the command "fastboot getvar cid" is "cid: VODAP304".
Where can i find the the original rom,
thank you a lot,
best regards,
Click to expand...
Click to collapse
The Europe ruu should work for that cid... Nonetheless, I will look a bit more into it later when I get home, to see if I can find any more details
You probably need a vodafone ruu but i can't seem to find an ICS one
posedatull said:
The Europe ruu should work for that cid... Nonetheless, I will look a bit more into it later when I get home, to see if I can find any more details
Click to expand...
Click to collapse
thank you for your collaboration,
Just for information, i have tested the europe ruu.exe but doesn't work.
Best regards,
Be sure to plug the phone in a usb 2.0 in the computer (one in the back, NOT in the front) to be sure it works properly. Ruus have problems on usb 1.1 and even on 3.0. Also try replacing your data cable, it might be faulty.
If you wiped everything in recovery and then oem locked hboot through adb, the europe ruu should have worked. Since it didnt, i must assume the problem is either with the cable used or with the usb port.
Also an idea might be to try and download the ruu again, maybe there was an error during the download
Theres something else you can try too. download the zip RUU. place this on your sd card and flash in bootloader
EM|NEM said:
Theres something else you can try too. download the zip RUU. place this on your sd card and flash in bootloader
Click to expand...
Click to collapse
thank all for your collaborations,
I have done this but it doesn't work, sorry for all and thank you.
do you know other ruu?
best regards
Well if you cant RUU you should try to get a custom rom to boot. First do these steps:
Unlock your bootloader.
Flash 4EXT recovery in fastboot. Then boot into recovery and turn on smartflash in tools menu.
Download Viper3D rom (the latest one) and transfer it to your sdcard.
Boot into recovery
wipe data/factory reset, wipe cache+dalvik
install viper3d rom. It will take a while, around 10 mins on synergy 4EXT alignment.
reboot and hope it boots
EM|NEM said:
Well if you cant RUU you should try to get a custom rom to boot. First do these steps:
Unlock your bootloader.
Flash 4EXT recovery in fastboot. Then boot into recovery and turn on smartflash in tools menu.
Download Viper3D rom (the latest one) and transfer it to your sdcard.
Boot into recovery
wipe data/factory reset, wipe cache+dalvik
install viper3d rom. It will take a while, around 10 mins on synergy 4EXT alignment.
reboot and hope it boots
Click to expand...
Click to collapse
Thank you,
I have boot loop after installation,
regards,
Ok, so I tired to dabble in custom roms and I got burnt!!!
First things first,
HTC One X+ (International)
Version Main: 1.17.708.1
CID: HTC_622
S-On
HBOOT: 1.35.0000
Radio: 3.1204.168.32
I'm trying to RUU the device back to the stock and then never tinker again!
Can someone please step me through this, all the links I'm finding are dead or the RUU doesn't run.
Many thanks =)
Get hasoons20000 one x+ toolkit it has a link for ruu
Gave this a shot, I cannot find the appropriate RUU for my device.
****...
CJMilsey said:
Gave this a shot, I cannot find the appropriate RUU for my device.
****...
Click to expand...
Click to collapse
What country did you buy it from and what is your CID?
I bought it online (from Asia) The CID is 622 as above.
Addicted2xda said:
What country did you buy it from and what is your CID?
Click to expand...
Click to collapse
Bump
CJMilsey said:
Bump
Click to expand...
Click to collapse
Refer to the posting rules. You should not bump a thread within 24 hours...
You can download the RUU (ENRC2B) from this :
http://forum.xda-developers.com/showthread.php?t=2094118
you need to relock your bootloader before running the RUU
http://www.androidfiles.org/ruu/get...Radio_3.1204.168.32_release_299722_signed.exe
I'm sorry, I must have missed that one :/
I Tried this before but the RUU used didn't work, but I'll try to re-download and go from there.
(RUU_ENRC2B_U_JB_45_hTC_Asia_WWE_1.17.707.1_Radio_3.1204.168.32_release_299722_signed.exe)
Will it be a problem that my phone is 1.17.708.1 and that this is 1.17.707.1 (0.0.001 lower)?
Also, do I need to flash the stock recovery. And If so where would I go about getting it?
You will only have to relock the bootloader again and then (while in fastboot) run the RUU. Remember that you will lose everything on the device.
To relock the bootloader use Hansoon's toolkit. It has all the commands build in for easy use.
"Wrong CID" I'm not sure why this is wrong. 662 came back from fastboot getvar cid, and does indeed correspond to Hong Kong.
What would you advise from here dear sir?
CJMilsey said:
"Wrong CID" I'm not why this is wrong. 662 came back from fastboot getvar cid, and does indeed correspond to Hong Kong.
What would you advise from here dear sir?
Click to expand...
Click to collapse
Are you sure it's a generic HK CID? And not an operator locked one? Maybe you need the RUU from a particular operator.....
Sent from my HTC One X+ using Tapatalk 4 Beta
AndroHero said:
Are you sure it's a generic HK CID? And not an operator locked one? Maybe you need the RUU from a particular operator.....
Sent from my HTC One X+ using Tapatalk 4 Beta
Click to expand...
Click to collapse
I looked up the CID and it's just for HK, the phone came unlock so I doubt it needs a locked RUU. But hey, I've been wrong before.
Is there any reason the phone would not accept the correct RUU?
Okk,
This might seem a bit weird but I had the same issue with my Intl HOX+ and I have given it to hTC and they asked me to shell out aroun 18K to change the motherboard! (Which of course we all know is not required since this is a software issue).
So here is what I did:
1. I relocked the boot loader (I hope you have the unlock_code.bin with you, else get it from hTCDev)
2. Of course it started giving relocked security warning.
3. Again unlocked the boot loader and voila - it booted straight in to Elegancia!
This essentiially happens because unlocking the bootloader formats all the partitions except system and boot (I guess, because my media files were gone...).
See if this gets you through.
But DO IT AT YOUR OWN RISK!
I am talking about International HOX+, I do not know if ATT works in a different way.
Unfortunately that hasn't worked and I'm still stuck with the stall during boot :/
I think my best bet will the RUU, but I just can't get one that will work.
Do you know a ROM that I could side-load onto my device and just use it with that?
Thanks
Addicted2xda said:
Okk,
This might seem a bit weird but I had the same issue with my Intl HOX+ and I have given it to hTC and they asked me to shell out aroun 18K to change the motherboard! (Which of course we all know is not required since this is a software issue).
So here is what I did:
1. I relocked the boot loader (I hope you have the unlock_code.bin with you, else get it from hTCDev)
2. Of course it started giving relocked security warning.
3. Again unlocked the boot loader and voila - it booted straight in to Elegancia!
This essentiially happens because unlocking the bootloader formats all the partitions except system and boot (I guess, because my media files were gone...).
See if this gets you through.
But DO IT AT YOUR OWN RISK!
I am talking about International HOX+, I do not know if ATT works in a different way.
Click to expand...
Click to collapse
I had a small bootloader problem and was just surfing this section.I used your method of relocking and again unlocking and my problem was solved.I found it obligatery for me to thank you.
---------- Post added at 10:30 AM ---------- Previous post was at 10:21 AM ----------
CJMilsey said:
Unfortunately that hasn't worked and I'm still stuck with the stall during boot :/
I think my best bet will the RUU, but I just can't get one that will work.
Do you know a ROM that I could side-load onto my device and just use it with that?
Click to expand...
Click to collapse
I have unbricked mine by efforts of two long days and nights from about same problem. Provide the details and I will try to help you out,
1. can you boot to recovery.
2. If yes.which recovery you use.
3. what were you doing when this happened.
faandrabi said:
I have unbricked mine by efforts of two long days and nights from about same problem. Provide the details and I will try to help you out,
1. can you boot to recovery.
2. If yes.which recovery you use.
3. what were you doing when this happened.
Click to expand...
Click to collapse
1. No recovery works, and by mistake I performed a full erase with TWRP (don't ask me how, I honestly don't know why I did this) so despite all that they don't even exist anymore.
3. I flashed to Boot File as I couldn't get CM10.1 (Lior's HOX+ plug) to install and considered that my solve it. (I was wrong)
From this stuff I'm pretty sure it's broke, but I can get to the boot loader and recovery. Though I ran the appropriate (so I thought) RUU and it didn't work due to CID which stumped me.
CJMilsey said:
1. No recovery works, and by mistake I performed a full erase with TWRP (don't ask me how, I honestly don't know why I did this) so despite all that they don't even exist anymore.
3. I flashed to Boot File as I couldn't get CM10.1 (Lior's HOX+ plug) to install and considered that my solve it. (I was wrong)
From this stuff I'm pretty sure it's broke, but I can get to the boot loader and recovery. Though I ran the appropriate (so I thought) RUU and it didn't work due to CID which stumped me.
Click to expand...
Click to collapse
flash twrp through fasboot as only twrp provides side load option.
when twrp is flashed ,boot to recovery.side load incertcoin rom through hasoons toolkit.
don't worry about 707 or 708 etc.Mine was 707.1 but i am using incertcoin which is 401.3
after falshing incertcoin if it is again in boot loop then
use this command from adb
adb shell
wipe data
and reboot
you will be done.
CJMilsey said:
1. No recovery works, and by mistake I performed a full erase with TWRP (don't ask me how, I honestly don't know why I did this) so despite all that they don't even exist anymore.
3. I flashed to Boot File as I couldn't get CM10.1 (Lior's HOX+ plug) to install and considered that my solve it. (I was wrong)
From this stuff I'm pretty sure it's broke, but I can get to the boot loader and recovery. Though I ran the appropriate (so I thought) RUU and it didn't work due to CID which stumped me.
Click to expand...
Click to collapse
I hope you are on TWRP 2.5? If not update it...
And then use adb sideload
Hi,
I have the exact same problem.. I can get to TWRP recovery and HBOOT and my PC only detects the phone if its in recovery.
my CID is HTC__001.
I am trying to find a working RUU to run..
I tried this one: RUU_ENRC2B_U_JB_45_hTC_Asia_TW_1.14.709.17_Radio_3.1204.167.31_release_291089_signed.exe
(But that didn't work)
Any suggestions?
Thanks in advance.
rmuruga said:
Hi,
I have the exact same problem.. I can get to TWRP recovery and HBOOT and my PC only detects the phone if its in recovery.
my CID is HTC__001.
I am trying to find a working RUU to run..
I tried this one: RUU_ENRC2B_U_JB_45_hTC_Asia_TW_1.14.709.17_Radio_3.1204.167.31_release_291089_signed.exe
(But that didn't work)
Any suggestions?
Thanks in advance.
Click to expand...
Click to collapse
download incertcoin rom from hox+ android development & hasoon toolkit v2.4
boot in recovery
connect to pc
run onex+.exe and side load the rom
after it is done flash boot.img inside rom through fasboot command
and you will be done
So I've explored different options on XDA's site for returning to stock and I guess this is why I'm here. I screwed the hell up. I posted this on Phaded's How-To page, but I figured it would also be best to post this in the general Help & Troubleshooting page.
Here's the best way I can explain my issue. Someone please help.
1. My phone is COMPLETELY formatted. No OS now. Zero data.
2. TWRP is installed as my recovery.
3. I can fastboot and adb (only from the recovery obviously)
4. I moonshined the phone in order to S-Off
5. I tried the method to remove S-Off by Phaded
adb devices (verify device ID is listed)
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
exit
Click to expand...
Click to collapse
When I ran the RUU, I got that error 158 problem. I couldn't flash the HBOOT. downloaded it several times and tried.
6. I flashed it with an AOSP rom and tried the RUU again. No luck.
Now I'm stuck. u_u I tried
adb push "file name" "file directory"
Click to expand...
Click to collapse
so I can drop a zip file in the phone, but it seems to not work. Idk if I did it right. I was hoping to flash a ROM by doing that. smh.
Let me know if there's any other info I can provide. Considering the phone still turns on and I can still get to fastboot and adb, I don't think I'm a lost cause.
Thanks everyone!
UPDATE
I sideloaded a ROM (Carbon) and now I'm up and running. But I still can't RUU it! Figured this detail will help.
I'll keep reading and researching, posting my progress.
Thanks!
Its ok that your'e formatted the main concern would be 1. To be able to turn the phone on and 2. Boot into bootloader and recovery . It sounds like you are able to do both so the term "bricked" doesn't apply here.Okay so first obvious question did you obtain s-off also what bootloader are you on. Also what are you trying to achieve moving forward, going to stock or staying with custom roms, sense or aosp. There is only 1 ruu available for DNA and you need to be relocked to run and have fastboot drivers installed ala HTC sync manager.
Sent from my HTC6435LVW using Tapatalk 4 Beta
xlxcrossing said:
Its ok that your'e formatted the main concern would be 1. To be able to turn the phone on and 2. Boot into bootloader and recovery . It sounds like you are able to do both so the term "bricked" doesn't apply here.Okay so first obvious question did you obtain s-off also what bootloader are you on. Also what are you trying to achieve moving forward, going to stock or staying with custom roms, sense or aosp. There is only 1 ruu available for DNA and you need to be relocked to run and have fastboot drivers installed ala HTC sync manager.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
1. I obtained s-off with moonshine. I used the above command suggested by Phaded and when I put in
fastboot oem lock
Click to expand...
Click to collapse
(or something like that) it says my phone is locked.
2. What do you mean what bootloader? I guess moonshine, cause that's what comes up when I go to my bootloader screen.
3. I trying flashing the ruu and I get this (see image attached) which the suggested fix for error 158 was to flash the hboot 1.15 (or something). But I can't seem to flash it correctly. I can't even find straight forward instructions on how to do it.
Thanks for responding.
The reason I asked about the bootloader version and I'm not 100% sure about this so someone else may need to chime in is that when you ruu you are flashing firmware which includes hboot so if you upgraded hboot before doing s-off or otherwise went up a version then I'm pretty sure the ruu won't downgrade your hboot airgo the error message. Again this might not be true. At this point all that matters is that your s-off and NOT bricked so instead of toying with an ruu I would choose a stock Rom .zip to flash if its truly stock that you want. Your firmware should be up to date if you took 2.06. There is no ruu for 2.06.
Sent from my HTC6435LVW using Tapatalk 4 Beta
What is s-off?
Sent from my Galaxy Nexus using xda premium
93fuelslut said:
What is s-off?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
It means you can write to any partition of your nand (internal memory). This means customs roms, kernels, splash screens, firmware, etc. When you are s-on it is more difficult, I can't get into why too many words it just is. If you're not s-off and you like flashing stuff look into it.
---------- Post added at 12:51 AM ---------- Previous post was at 12:41 AM ----------
xlxcrossing said:
It means you can write to any partition of your nand (internal memory). This means customs roms, kernels, splash screens, firmware, etc. When you are s-on it is more difficult, I can't get into why too many words it just is. If you're not s-off and you like flashing stuff look into it.
Click to expand...
Click to collapse
I'm not finding a solid explanation for error 158 which is disheartening - the best offerings are to change USB ports or restart the ruu. Like I said before you are fine on the software end, you can verify you have up to date firmware by comparing the latest below with what you have.
Baseband (radio) 1.01.04.0308
PRI 2.44_002
As for the hboot, how are you trying to flash it? In recovery?
The hboot needs to match the RUU. You need to find the original hboot . It is in a thread with hboot versions and radio versions.
Link to HBOOT please? and answering your questions
Could someone provide a link for the hboot instructions and flashing?
I think my problem is that moonshine screwed up my phone. I relocked my phone, but when trying to run moonshine again, it doesn't unlock the phone. It just says "WTF: What are you dong" and then it just stops and tells me to hit Enter to exit and the phone is still locked, hence why I think I can't flash HBOOT.
I try and flash HBOOT through recovery. I tried doing fastboot to flash it. Recalling from memory, I think the command was:
fastboot flash "file name.zip"
Click to expand...
Click to collapse
and then it says it can't open the file, unknown error. But I can't find any help guides or how-to's that explain the fix for this.
Thanks! Keep asking questions, cause I don't know what info is relevant.
ibthevivin said:
Could someone provide a link for the hboot instructions and flashing?
I think my problem is that moonshine screwed up my phone. I relocked my phone, but when trying to run moonshine again, it doesn't unlock the phone. It just says "WTF: What are you dong" and then it just stops and tells me to hit Enter to exit and the phone is still locked, hence why I think I can't flash HBOOT.
I try and flash HBOOT through recovery. I tried doing fastboot to flash it. Recalling from memory, I think the command was: and then it says it can't open the file, unknown error. But I can't find any help guides or how-to's that explain the fix for this.
Thanks! Keep asking questions, cause I don't know what info is relevant.
Click to expand...
Click to collapse
Moonshine isn't working because you are still s-off.
My thread has the original hboot and instructions to flash it. You do not flash in recovery. You do not put it on your phone at all. Do not push the file in recovery. Read and follow the instructions in the stock thread.
---------- Post added at 02:04 PM ---------- Previous post was at 02:02 PM ----------
You're doing the command wrong or you renamed it PL83IMG.zip.zip
Please, go in my thread, read each step perfectly and follow. It's really quite simple.
Difference
Is s-off/s-on and being locked/unlocked two different things?
Screenshot
Also here Phaded. I tried different variants of flashing the hboot. I renamed it from PL83IMG.zip to HBOOT.zip. It's not HBOOT.zip.zip cause I know Windows 8 automatically appends the end of the file name with the type extension. As you can see, I boot to fastboot, then run rebootRUU, then I'm trying to flash from there. I got frustrated and tried different things, even unpacking the .zip and trying to flash the .img file.
Thanks for your contribution to the community Phaded.
ibthevivin said:
Could someone provide a link for the hboot instructions and flashing?
I think my problem is that moonshine screwed up my phone. I relocked my phone, but when trying to run moonshine again, it doesn't unlock the phone. It just says "WTF: What are you dong" and then it just stops and tells me to hit Enter to exit and the phone is still locked, hence why I think I can't flash HBOOT.
I try and flash HBOOT through recovery. I tried doing fastboot to flash it. Recalling from memory, I think the command was: and then it says it can't open the file, unknown error. But I can't find any help guides or how-to's that explain the fix for this.
Thanks! Keep asking questions, cause I don't know what info is relevant.
Click to expand...
Click to collapse
Strike.
From my S-Off BadSeed DNA
ibthevivin said:
Also here Phaded. I tried different variants of flashing the hboot. I renamed it from PL83IMG.zip to HBOOT.zip. It's not HBOOT.zip.zip cause I know Windows 8 automatically appends the end of the file name with the type extension. As you can see, I boot to fastboot, then run rebootRUU, then I'm trying to flash from there. I got frustrated and tried different things, even unpacking the .zip and trying to flash the .img file.
Thanks for your contribution to the community Phaded.
Click to expand...
Click to collapse
You need to cd to the directory the file is in, which should be where fastboot.exe is
So if it's in say C:\sdk\
Type cd C:\sdk\
Then run command to fastboot
BOOM!
Alright. Worked. I'll keep you all posted. No one really mentioned in any of the tutorials and how-to's that it is VERY important to make sure to CD to the directory. Like there are developers who say just add it to the PATH in Environment Variables. I figured it was enough, but hey, I was wrong.
Live and learn right?
Thank you Phaded.
So basically my problem was, calling the hboot.zip file is not included under Environmental Variables. I have to intentionally CD to that directory.
Hmm, I must have missed putting in the cd step for the hboot. I'll go edit it.
Hello Everyone,
I know this probably isn't the best place to post this question. I'm limited to not posting in the dev section.
I'm going to post my question and hope someone can help anyway.
I have an HTC One (M7) that seemed to have reception problems. I always thought I just needed to flash a new radio. So I went ahead and S-OFF'd my phone as well as Super CID. I then flashed a new radio & my reception problem seemed to go away. (or so i thought).
I then went ahead and turned my AT&T One into a Google Edition.
I have noticed that my reception problems never really went away. (When I am at home I have full bars. The conversation starts out fine, but about 10 seconds in, the person at the other end can no longer hear me.)
I now suspect this is a problem with the antenna & I have to get my phone back to stock so that I can hopefully switch out for a new one.
I'm just wondering which step I should do first. S-On again (I used REVONE to S-OFF) , CID back to AT&T, or switch back from the GE rom?
Any help would be appreciated.
Thank you,
Dan
demayod said:
Hello Everyone,
I know this probably isn't the best place to post this question. I'm limited to not posting in the dev section.
I'm going to post my question and hope someone can help anyway.
I have an HTC One (M7) that seemed to have reception problems. I always thought I just needed to flash a new radio. So I went ahead and S-OFF'd my phone as well as Super CID. I then flashed a new radio & my reception problem seemed to go away. (or so i thought).
I then went ahead and turned my AT&T One into a Google Edition.
I have noticed that my reception problems never really went away. (When I am at home I have full bars. The conversation starts out fine, but about 10 seconds in, the person at the other end can no longer hear me.)
I now suspect this is a problem with the antenna & I have to get my phone back to stock so that I can hopefully switch out for a new one.
I'm just wondering which step I should do first. S-On again (I used REVONE to S-OFF) , CID back to AT&T, or switch back from the GE rom?
Any help would be appreciated.
Thank you,
Dan
Click to expand...
Click to collapse
If I were returning my phone to Stock, this is the process I would use
Change CID to Stock fastboot oem writecid CWS__001
Run the latest RUU for my phone
then use Revone to lock the bootloader and s-on
I think that's the correct order .. if anyone knows different please chime in
Here's a definitive Guide
http://forum.xda-developers.com/showthread.php?t=2358738
clsA said:
If I were returning my phone to Stock, this is the process I would use
Change CID to Stock fastboot oem writecid CWS__001
Run the latest RUU for my phone
then use Revone to lock the bootloader and s-on
I think that's the correct order .. if anyone knows different please chime in
Here's a definitive Guide
http://forum.xda-developers.com/showthread.php?t=2358738
Click to expand...
Click to collapse
Thanks so much for the response! I appreciate the help. Very informative. I'll read through & hopefully I report back with good news tomorrow morning. :cyclops:
Yay! All done!
Thanks so much for the guide! and the help!
-Dan
clsA said:
If I were returning my phone to Stock, this is the process I would use
Change CID to Stock fastboot oem writecid CWS__001
Run the latest RUU for my phone
then use Revone to lock the bootloader and s-on
I think that's the correct order .. if anyone knows different please chime in
Here's a definitive Guide
http://forum.xda-developers.com/showthread.php?t=2358738
Click to expand...
Click to collapse
I guess I spoke too soon. After completion, I realized that TWRP was still installed, so I flashed the stock recovery. At this point everything seemed fine, but I noticed that the supersu icon was still there. I also noticed that wifi will no longer turn on. Clearly I've done something wrong.
The first time I had used a nandroid backup to restore to stock, then lock, s-on, remove tampered. That is when I realized TWRP was still installed and SuperSu was still there.
This is when I downloaded an RUU that matched my phone, but it errors saying something like "wrong boot version" (I'm not near my home pc to look)
I tried the process again & somehow SuperSu lost binaries. So I unlocked my bootloader again through HTCDev.com This gave me working SuperSu again. And this is where I am stuck.
I wonder if the GE rom changed something so that this process wont work?
demayod said:
I guess I spoke too soon. After completion, I realized that TWRP was still installed, so I flashed the stock recovery. At this point everything seemed fine, but I noticed that the supersu icon was still there. I also noticed that wifi will no longer turn on. Clearly I've done something wrong.
The first time I had used a nandroid backup to restore to stock, then lock, s-on, remove tampered. That is when I realized TWRP was still installed and SuperSu was still there.
This is when I downloaded an RUU that matched my phone, but it errors saying something like "wrong boot version" (I'm not near my home pc to look)
I tried the process again & somehow SuperSu lost binaries. So I unlocked my bootloader again through HTCDev.com This gave me working SuperSu again. And this is where I am stuck.
I wonder if the GE rom changed something so that this process wont work?
Click to expand...
Click to collapse
when you run the RUU did you use the exe or Rom.zip /?
I use the rom.zip and flash in fastboot...
clsA said:
when you run the RUU did you use the exe or Rom.zip /?
I use the rom.zip and flash in fastboot...
Click to expand...
Click to collapse
I used the ruu. I didn't realize you can access a Rom.zip. how can I try that? Thanks!
demayod said:
I used the ruu. I didn't realize you can access a Rom.zip. how can I try that? Thanks!
Click to expand...
Click to collapse
This is the instructions posted by Scotty85
I'm just re-posting it for you
http://androidforums.com/t-one-all-things-root/723061-t-ruu-1-26-502-12-a.html#post5864243
Click to expand...
Click to collapse
here is how you extract rom.zip:
Quote:
the .exe utilities can be finicky,so if you have trouble getting it to run, you can extract "rom.zip" in the following manner:
-start the utility
-check the "i understand" box to move on to the next screen
-hide the utility temporarily out of site
-search your C drive for "rom.zip". you will find it in a temporary location(it will be in a different spot each time you run the utility)
-open the folder location,and transfer rom.zip to a safe location on your PC.
-unhide and cancel the utility,youre done with it.
-rom.zip can be flashed using
adb reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip (yes do this 2 times)
fastboot reboot
Click to expand...
Click to collapse
here are some directions to flash "rom.zip"
if youre working with a booted,operational phone,you can flsh the file in the following manner:
-open a cmd window
-change to adb/fastboot directory
cd c:\foldername
(cd c:\mini-adb if youve used any of my guides )
-place the zip file you want to flash into adb/fastboot directory
-enable usb debug,disable fastboot,plug in phone
-check for connectivity
adb devices (should return serial number)
-boot to fastboot
adb reboot bootloader
-check for connectivity again
fastboot devices
-flash the file
fastboot erase cache
fastboto oem rebootRUU (will put you in ruu mode,black screen silver htc letters)
fastboot flash zip zipfilename.zip (will send and flash the file. dont interupt it while the cmd window shows its writinging,and the green status bar is moving on the phone screen)
*sometimes a file will fail with a pre-update error. this is normal,just enter again:
fastboot flash zip zipfilename.zip
and this time it will finish
-when you get "finished" and "OK"
fastboot reboot-bootloader (takes you back to fastboot)
-reboot back to the OS
fastbooot reboot
you can use this if you dont have an operational phone as well. you just need to manually put the phone in fastboot(select from hboot menu) then skip the "adb" commands and start with fastboot devices
to answer your other question,yes,you will need to re-unlock and re-install recovery after running the RUU. an ruu is designed as an "unroot" solution, or emergency fix,if other attempts have not made the phone operational.
Click to expand...
Click to collapse
clsA said:
This is the instructions posted by Scotty85
I'm just re-posting it for you
Click to expand...
Click to collapse
Thank you for the help, but still no good. I end up with FAILED (remote: 43 main version check fail) after I try to flash the zip.
demayod said:
Thank you for the help, but still no good. I end up with FAILED (remote: 43 main version check fail) after I try to flash the zip.
Click to expand...
Click to collapse
change your CID back to 11111111 and try again
Did you change you MID ?
What is the name of the RUU your using ?
My mid is PN0712000. I think that was always my mid. Don't recall changing it.
My cid is currently CW__001
I've tried: RUU_M7_UL_JB_50_Cingular_1.26.502.12.exe
also tried: RUU_M7_UL_JB_50_Cingular_US_1.26.502.15_Radio_4A.17.3250.20_10.40.1150.04_release_326691_signed_2.exe
I'm currently S-On (could that be an issue?)
I'm unlocked.
clsA said:
change your CID back to 11111111 and try again
Did you change you MID ?
What is the name of the RUU your using ?
Click to expand...
Click to collapse
It worked once I set CID to 11111111 !!
So now I just have to change CID back, reverse S-Off again and change the unlocked and tampered flags?
Yep that should do it
Sent from my HTC One using Tapatalk 4
It did! I'm completely back to stock. I decided to update to the latest RUU that AT&T has released. Just to avoid AT&T wanting me to update to see if it fixes the problem. I know for a fact that it wouldn't fix the problem anyway.
Oddly, my phone told me I was up to date while on the .12 RUU even though I knew the .15 RUU exists. I downloaded the RUU for .15 and it ran fine once I went back to stock after running the .12 rom.zip.
In summary, you saved me from a huge headache! Thanks so much for all the help & kindness.
demayod said:
It worked once I set CID to 11111111 !!
So now I just have to change CID back, reverse S-Off again and change the unlocked and tampered flags?
Click to expand...
Click to collapse
How did you change our CID if you were S-On?
clsA said:
If I were returning my phone to Stock, this is the process I would use
Change CID to Stock fastboot oem writecid CWS__001
Run the latest RUU for my phone
then use Revone to lock the bootloader and s-on
I think that's the correct order .. if anyone knows different please chime in
Here's a definitive Guide
http://forum.xda-developers.com/showthread.php?t=2358738
Click to expand...
Click to collapse
Hi guys this might be the wrong platform for this question ...but can anyone pls help me with the stock cidnum for sprint htc one M8..thanks
larrydadz said:
Hi guys this might be the wrong platform for this question ...but can anyone pls help me with the stock cidnum for sprint htc one M8..thanks
Click to expand...
Click to collapse
Comments: Sprint
modelid:
cid: SPCS_001