Related
Htc raider/vivid rooted ok
1. Unlock bootloader by htcdev
2. Coppy file PH39IMG.zip on root sdcard
http://dl.dbank.com/c0fwbgxr2w
Phone rooted ok.
I'm assuming that's a rooted stock rom that obviously wont unlock the bootloader. but it installs like an official update?
Yeah... What is this?
Sent from my HTC PH39100 using xda premium
Lol k hope it works but unlocked bootloader hmmmm??? Someone should try
Sent from my HTC PH39100 using xda premium
the bootloader on the bell htc raider is unlocked correct?
erik10002 said:
the bootloader on the bell htc raider is unlocked correct?
Click to expand...
Click to collapse
It's unlockable via the htcdev website. Doesn't come unlocked.
rquinn19 said:
It's unlockable via the htcdev website. Doesn't come unlocked.
Click to expand...
Click to collapse
do i use S710d (China Telecom) 3.06.1401.0 or will it automaticly detect my phone and still be able to do the unlock even though my specific phone is not on the green list?
erik10002 said:
do i use S710d (China Telecom) 3.06.1401.0 or will it automaticly detect my phone and still be able to do the unlock even though my specific phone is not on the green list?
Click to expand...
Click to collapse
No need to flash anything, just follow the instructions on the htcdev site.
sent from HTC Raider on Bell LTE
Can anyone test if this runs on a vivid?
Sent from my HTC PH39100 using xda premium
This rom was Reprinted from bbs.xda.cn（china）
gtkansan said:
Can anyone test if this runs on a vivid?
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
I attempted this on my vivid. But it failed reading...
Error Code: 170
CID Not Allowed
I will try again tomorrow after my exams
Sent from my HTC PH39100 using XDA App
I meant flashing the file without the unlock
Sent from my HTC PH39100 using xda premium
MODEL ID incorrect
update fail!
that was the error i got, (zip file in root of sd) i have a bell raider and have unlocked the bootloader, i will try a few more things and report back
update: tried extracting the files from the zip and putting them on my sd card and also tried on my internal, just put the zip on my internal as well and still nothing!
Anyone with a vivid attempt to flash this?
edit. Nm
Sent from my HTC PH39100 using xda premium
erik10002 said:
MODEL ID incorrect
update fail!
that was the error i got, (zip file in root of sd) i have a bell raider and have unlocked the bootloader, i will try a few more things and report back
update: tried extracting the files from the zip and putting them on my sd card and also tried on my internal, just put the zip on my internal as well and still nothing!
Click to expand...
Click to collapse
Same thing here.
hmmm...
The zip tried to load twice from hboot.
I tried the recovery option and rec'd the red triangle.
Ended up with correct time on home widget, but 4 hrs ahead in upper right menu.
So I flashed the Cingular ruu and back to normal.
I notice the img file is about 11 MB smaller than the ruu.
I attempted on Tuesday and again today to unlock bootloader, getting the same message as others above.
Here is the whole message you receive.
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: 170.
Error Reason: CID Not Allowed.
Big Dawg 23 said:
I attempted on Tuesday and again today to unlock bootloader, getting the same message as others above.
Here is the whole message you receive.
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: 170.
Error Reason: CID Not Allowed.
Click to expand...
Click to collapse
We have to wait. It took almost a month I think for the Amazed 4G.
Just long enough so that the people who got it on day-one are out of the return/exchange period
---------- Post added at 10:47 AM ---------- Previous post was at 10:44 AM ----------
Still downloading, but does this zip make any changes to the hboot? If so, has someone tried to do the htcdev unlock after running this?
Just wondering out loud, but even if hboot is updated...not sure if that would change the identifier token...
tried flashing through CWM just to see what happens! FAIL
Hey,
I couldn't find any help regarding this one:
I have unlocked my bootloader using the htcdev site (i am aware of the warranty issues).
So i've got this super sexy device, with unlocked bootloader, RUU 1.16.000, S-ON CWM recovery and root access.
I've tried to install the Revolution HD rom (3 times now) and after each time i got stuck at the HTC logo screen, not the one that says"quietly brilliant", but the one the says only "HTC". So luckily (again) i've done nandroid and used it to get my operator's ROM back.
So i've got 2 questions:
1) am i a failure ? what am i doing wrong?
2) is it possible to remove all the annoying operator's apps? and how? (fastboot/adb...)
3) What the heck is Goldcard?
Thanks a lot,
amitizle said:
Hey,
I couldn't find any help regarding this one:
I have unlocked my bootloader using the htcdev site (i am aware of the warranty issues).
So i've got this super sexy device, with unlocked bootloader, RUU 1.16.000, S-ON CWM recovery and root access.
I've tried to install the Revolution HD rom (3 times now) and after each time i got stuck at the HTC logo screen, not the one that says"quietly brilliant", but the one the says only "HTC". So luckily (again) i've done nandroid and used it to get my operator's ROM back.
So i've got 2 questions:
1) am i a failure ? what am i doing wrong?
2) is it possible to remove all the annoying operator's apps? and how? (fastboot/adb...)
3) What the heck is Goldcard?
Thanks a lot,
Click to expand...
Click to collapse
1) There is a sticky in this forum. Search it for your reference.
2) You cant remove the apps cause it is located in /system/app. You might wanna try deleting them using a file manager
3) As far as I know, for incredible s, its used for downgrading hboot 1.16/2.00 to 1.13 (there is a thread somewhere around this forum) so that it could be s-off'd using revolutionary.io
Hope this helps! ^^
Sent from my HTC Incredible S using XDA App
Wow i somehow missed it...
http://forum.xda-developers.com/showthread.php?t=1435136
There is an answer there.
Sorry for posting this
And thanks a lot!
Uninstall system apps with titanium backup(market app)
Edit: goldcard is for flashing HTC signed roms from other carriers
amitizle said:
Hey,
I couldn't find any help regarding this one:
I have unlocked my bootloader using the htcdev site (i am aware of the warranty issues).
So i've got this super sexy device, with unlocked bootloader, RUU 1.16.000, S-ON CWM recovery and root access.
I've tried to install the Revolution HD rom (3 times now) and after each time i got stuck at the HTC logo screen, not the one that says"quietly brilliant", but the one the says only "HTC". So luckily (again) i've done nandroid and used it to get my operator's ROM back.
So i've got 2 questions:
1) am i a failure ? what am i doing wrong?
2) is it possible to remove all the annoying operator's apps? and how? (fastboot/adb...)
3) What the heck is Goldcard?
Thanks a lot,
Click to expand...
Click to collapse
If you dont want to downgrade and s-off your phone you need to manualy flash boot.img via fastboot after you flashed the rom.
"Fastboot flash boot boot.img"
Sent from my HTC Incredible S using XDA App
I guess I should start by telling you my progress and why I can't just go through the guide on this site.
Before I discovered this site, successfully unlocked my bootloader using the official site. Then I googled around and found a guide to root the phone. I'll try to post the link later, I'm in a hurry and on my phone. The root failed, saying it couldn't copy files or something like that. I tried again with superoneclick, but it always freezes at step five and I have to exit.
Then I found this site. The guide said I have to re-lock my bootloader before continuing, so I follow the directions and do that, only to find out It wants me to unlock it again using the method I did before. Now this is where I need help, and why I need my own thread. When I tried to lock my loader again, there was a line that said FAILED in the cmd. because of this I am unsure if I really am locked or not, and I'm afraid of doing anything else until I know for sure.
How can I find out whether I'm locked or not? I'm sure I can figure out the rest once I know for sure.
sugarshock said:
I guess I should start by telling you my progress and why I can't just go through the guide on this site.
Before I discovered this site, successfully unlocked my bootloader using the official site. Then I googled around and found a guide to root the phone. I'll try to post the link later, I'm in a hurry and on my phone. The root failed, saying it couldn't copy files or something like that. I tried again with superoneclick, but it always freezes at step five and I have to exit.
Then I found this site. The guide said I have to re-lock my bootloader before continuing, so I follow the directions and do that, only to find out It wants me to unlock it again using the method I did before. Now this is where I need help, and why I need my own thread. When I tried to lock my loader again, there was a line that said FAILED in the cms. because of this I am unsure if I really am locked or not, and I'm afraid of doing anything else until I know for sure.
How can I find out whether I'm locked or not? I'm sure I can figure out the rest once I know for sure.
Click to expand...
Click to collapse
Turn your phone off. Pull your battery. Turn on your phone by holding volume down + the power button. You will be booted to the bootloader screen. It will say at the top whether you are "unlocked" or "re-locked". Re-locked = locked.
The reason you need to re-lock your bootloader is because the RUU (stock ROM flash) requires it. The you have to once again unlock the bootloader and then you can root. The RUU also updates the HBOOT for you if you want some custom ICS ROMs.
I am trying to relock my bootloader to flash RUU. When I relock, it gives the security warning, and won't go past bootloader. You have to have the phone on to update the RUU.
krustmother said:
I am trying to relock my bootloader to flash RUU. When I relock, it gives the security warning, and won't go past bootloader. You have to have the phone on to update the RUU.
Click to expand...
Click to collapse
That's fine hook it up to your computer with it at the bootloader screen it will go into fastboot USB mode when you do this then run the ruu
Sent from my HTC PH39100 using Tapatalk 2
Thanks a lot, jerrycoffman45.
Is anyone familiar with this error? I searched but didn't find.
:~/android$ sudo ./fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (Protocol error))
It appears to do it anyway, as it says relocked on the bootloader screen.
krustmother said:
Thanks a lot, jerrycoffman45.
Is anyone familiar with this error? I searched but didn't find.
:~/android$ sudo ./fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (Protocol error))
It appears to do it anyway, as it says relocked on the bootloader screen.
Click to expand...
Click to collapse
it is a common error i have seen it too aslong as it now says relocked you are good to go
help!!!
ok i'm stuck. i have relocked my phone but when it reboots it gets stuck at the relock fastboot screen. i am freaking out!!!
kainniak03 said:
ok i'm stuck. i have relocked my phone but when it reboots it gets stuck at the relock fastboot screen. i am freaking out!!!
Click to expand...
Click to collapse
It will do that if you relock it. Unlock it again and it should boot up
Sent from my HTC PH39100 using Tapatalk 2
help!!!
it is stuck at the boot screen. just says HTC
Ok what all have you done and are you on att
Sent from my HTC PH39100 using Tapatalk 2
help!!!
just following the directions for htc vivid aio kit by hasoon 2000 v2.1. i installed the htc drivers, registered at htcdev, got my token id and submitted it then unlocked bootloader. i then flashed wcxs cwm (gb/ics). thats all. oh and i'm on att.
kainniak03 said:
just following the directions for htc vivid aio kit by hasoon 2000 v2.1. i installed the htc drivers, registered at htcdev, got my token id and submitted it then unlocked bootloader. i then flashed wcxs cwm (gb/ics). thats all. oh and i'm on att.
Click to expand...
Click to collapse
Ics or gb and I am on my way home so give me about 45 min
Sent from my HTC PH39100 using Tapatalk 2
jerrycoffman45 said:
Ics or gb and I am on my way home so give me about 45 min
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
ics
Ok I got about 10 min till my kids get out of school are you trying to put a custom rom on your phone or just root it
Sent from my HTC PH39100 using Tapatalk 2
just root it. i feel so damn stupid.
It happens ok download the ruu from htc if you havnt yet relock your bootloader and leave your phone hooked up to your computer and run the ruu this will return you to stock ics then go to wildchilds site and regester you can't download anything until you have 10 post and you can't see the vivid section till you register in the att ics rom op is a video that will show you how to root with wcs recovery
Sent from my HTC PH39100 using Tapatalk 2
---------- Post added at 04:12 PM ---------- Previous post was at 03:32 PM ----------
ok i am home let me know if you need more help
I am having an issue that I have not seen before and could not find any resolve thru XDA or Google. I am attempting to restore the 64G Developer Edition with the RUU from HTC Dev and I keep getting the 155 error. I even have attempted to install thru CWM the .zip. Still no avail.
I am currently rooted, and have CWM installed. The device is obviously Bootloader unlock. What I was able to find is that it possibly could be a issue that it is bootloader unlocked as some posts suggest to have you bootloader locked to install RUU, but that is obviosely not a posibility with the dev ed.
So what am I doing wrong, or what is the issue. I have confirmed that I was using the correct RUU.
Help Appreciated
UPDATE
Ok, I figured out how to avoid the RUU 155 error. It seems that HTC for some dumb reason, although for a unlocked developer edition, we still have to lock the bootloader to utilize the RUU. Here are the steps I have done.
Although it is straight forward and easy to do, issues could always arise. I do not take any responsibility if things go wrong. Educate yourself first before attempting anything. If you do not know what you are doing, then don't do it.
Before Starting.
Make sure you have the latest HTC Drivers. You can use hasoon2000 HTC All-In-One Toolkit to complete that. That can be found at HTC One All-In-One Toolkit
Get the appropriate RUU from HTC Dev
1. Lock your bootloader through by booting into hoot and then going into fastboot and issuing the command fasboot oem lock.
2. Once locked, reboot your system.
3. Open RUU and follow onscreen instructions.
Notice, this will delete all of the files on the system so do this on your own cognition
4. Let the RUU do its thing. If you get an error during the process, such as 152, simply try again. I had it happen once. The phone was stuck on the black HTC screen with four triangles with exclamation points in each corner. If this happens you will not be able to reboot your phone. Simply relaunch RUU and it should reinstall it. If you get error 155 again, then you have not re-locked your bootloader.
3.Once you have successfully reinstalled the rom, you have to register with the HTC Dev to re-unlock your bootloader if that is what you want. The easiest to do this I found was by using the HTC One All-In-One Toolkit. It is a great tool and will help you with majority of things that I have mentioned above, including locking your bootloader. Follow the steps on the toolkit and you'll be all set. The Toolkit can be found here HTC One All-In-One Toolkit
If you found this helpful, click thanks. Also hit thanks to hasoon2000 for creating the toolkit.
Gotta re lock your bootloader
fastboot oem lock
I got relock it even though it came unlocked? How would I unlock it again since I don't have the tokens from HTC development, or is the ruu gonna do that by itself.
Sent from my HTC One using Tapatalk 2
I was having same issues as OP. After using the lock command, the update got longer. The black HTC screen even got as far as a progress bar. Well I now got ERROR 152 saying I should get the correct RUU. I am sure I have the right one, because there is only ONE developer edition RUU file from htcdev.com
Problem now is, I have the black HTC screen with warning signs on each corner.
One thing I saw on a video is you are supposed to restore to the same version? I had updated OTA Z(1.29.1540.16) to the latest which I cant get an RUU for. The RUU available is 1.29.1540.3 no other available. What do I do now? HTC One Dev Edition stuck on black screen with warning signs on all corners.
All I can see now is a scren that says:
***TAMPERED***
***RELOCKED***
bunch of numbers and letters in green and
RUU in orange
schn1tt3r said:
I was having same issues as OP. After using the lock command, the update got longer. The black HTC screen even got as far as a progress bar. Well I now got ERROR 152 saying I should get the correct RUU. I am sure I have the right one, because there is only ONE developer edition RUU file from htcdev.com
Problem now is, I have the black HTC screen with warning signs on each corner.
One thing I saw on a video is you are supposed to restore to the same version? I had updated OTA to the latest which I cant get an RUU for. What do I do now? HTC One Dev Edition stuck on black screen with warning signs on all corners.
Click to expand...
Click to collapse
When I was doing it, the first time I got the 152 error. I simply just redid it and it accepted it on the second try. Trying relaunching RUU that you have and try the install again. That's at least how it worked with me.
Bosnazmaj said:
When I was doing it, the first time I got the 152 error. I simply just redid it and it accepted it on the second try. Trying relaunching RUU that you have and try the install again. That's at least how it worked with me.
Click to expand...
Click to collapse
Did you get that black HTC screen with warning signs on each corner? I am re-running the RUU, hope it works or I just lost $650.
EDIT: You used RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.exe right? Were you already OTA updated? I wonder why htcdev web says BrightstarUS for the dev edition instead of something else...
EDIT2: Its on that black screen with loading thing again... still exclamation marks on every corner... hope this works or else it won't be a nice first experience with Android coming from iOS lol and I've jailbroken and tinkered on those devices for so long.
---------- Post added at 08:31 PM ---------- Previous post was at 08:21 PM ----------
Yeah 2nd attempt the same error 152. I just lost $650 right?
The green bar goes all the way to the end, it sends it all, but it doesnt reboot. It just gets error. What else can I try? Device isnt even 3 days old.
Did it a third time, after Updating Radio, thats where the error appears.
schn1tt3r said:
Did you get that black HTC screen with warning signs on each corner? I am re-running the RUU, hope it works or I just lost $650.
EDIT: You used RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.exe right? Were you already OTA updated? I wonder why htcdev web says BrightstarUS for the dev edition instead of something else...
EDIT2: Its on that black screen with loading thing again... still exclamation marks on every corner... hope this works or else it won't be a nice first experience with Android coming from iOS lol and I've jailbroken and tinkered on those devices for so long.
---------- Post added at 08:31 PM ---------- Previous post was at 08:21 PM ----------
Yeah 2nd attempt the same error 152. I just lost $650 right?
The green bar goes all the way to the end, it sends it all, but it doesnt reboot. It just gets error. What else can I try? Device isnt even 3 days old.
Did it a third time, after Updating Radio, thats where the error appears.
Click to expand...
Click to collapse
What was the software version that it came with. Was it with the most recent one? I think 1.29.401.16 one?
Bosnazmaj said:
What was the software version that it came with. Was it with the most recent one? I think 1.29.401.16 one?
Click to expand...
Click to collapse
It came with the .3 and I did OTA to .16
The RUU you can get online from their web is only .3
===============================
Ok so... that black HTC screen accepts "fastboot" commands.
I downloaded the .ZIP version of the Developer Edition OS.
I went in command prompt, I typed
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip PN07IMG_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.zip
****GOT AN ERROR*****
Code:
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
.... so again:
fastboot flash zip PN07IMG_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.zip
10 minutes later
fastboot reboot
Oh my was I happy to see the white HTC Startup.
I also have same phone de it shouldnt be tamperd relocked it should be only relocked
Sent from my HTC One using xda app-developers app
I find it funny now far Computer OS's have come and yet we always have to go back to good old DOS Command Prompt to fix things.
BTW, my phone now has bootloader RELOCKED due to the fastboot oem lock command, should I send the phone back just like that or unlock bootloader before sending it back?
I guess to Unlock bootloader again, I have to follow same instructions as if it were an AT&T version right? Did you UNLOCK yours again OP?
U sending it back to HTC?
Sent from my HTC One using Tapatalk 2
Bosnazmaj said:
U sending it back to HTC?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Yes, that is the reason I was doing all this restoring. I had ROOTed it to install AdAway. Ads is the only major drawback when compared to iOS (this is my first Android). When you see a gray image on my phone, there are 3 sort of water drops. Like between the touch screen and LCD.
Well, I am exchanging it actually. I like the HTC One a lot. It has a tiny gap, but I dont care about that much, the weird discoloration on the sceen, though, I do mind.
That makes sense.
Sent from my HTC One using Tapatalk 2
Bosnazmaj said:
I am having an issue that I have not seen before and could not find any resolve thru XDA or Google. I am attempting to restore the 64G Developer Edition with the RUU from HTC Dev and I keep getting the 155 error. I even have attempted to install thru CWM the .zip. Still no avail.
I am currently rooted, and have CWM installed. The device is obviously Bootloader unlock. What I was able to find is that it possibly could be a issue that it is bootloader unlocked as some posts suggest to have you bootloader locked to install RUU, but that is obviosely not a posibility with the dev ed.
So what am I doing wrong, or what is the issue. I have confirmed that I was using the correct RUU.
Help Appreciated
UPDATE
Ok, I figured out how to avoid the RUU 155 error. It seems that HTC for some dumb reason, although for a unlocked developer edition, we still have to lock the bootloader to utilize the RUU. Here are the steps I have done.
Although it is straight forward and easy to do, issues could always arise. I do not take any responsibility if things go wrong. Educate yourself first before attempting anything. If you do not know what you are doing, then don't do it.
Before Starting.
Make sure you have the latest HTC Drivers. You can use hasoon2000 HTC All-In-One Toolkit to complete that. That can be found at HTC One All-In-One Toolkit
Get the appropriate RUU from HTC Dev
1. Lock your bootloader through by booting into hoot and then going into fastboot and issuing the command fasboot oem lock.
2. Once locked, reboot your system.
3. Open RUU and follow onscreen instructions.
Notice, this will delete all of the files on the system so do this on your own cognition
4. Let the RUU do its thing. If you get an error during the process, such as 152, simply try again. I had it happen once. The phone was stuck on the black HTC screen with four triangles with exclamation points in each corner. If this happens you will not be able to reboot your phone. Simply relaunch RUU and it should reinstall it. If you get error 155 again, then you have not re-locked your bootloader.
3.Once you have successfully reinstalled the rom, you have to register with the HTC Dev to re-unlock your bootloader if that is what you want. The easiest to do this I found was by using the HTC One All-In-One Toolkit. It is a great tool and will help you with majority of things that I have mentioned above, including locking your bootloader. Follow the steps on the toolkit and you'll be all set. The Toolkit can be found here HTC One All-In-One Toolkit
If you found this helpful, click thanks. Also hit thanks to hasoon2000 for creating the toolkit.
Click to expand...
Click to collapse
Thank you. This was very helpful.
Glad I could help
Sent from my HTC One using Tapatalk 2
schn1tt3r said:
It came with the .3 and I did OTA to .16
The RUU you can get online from their web is only .3
===============================
Ok so... that black HTC screen accepts "fastboot" commands.
I downloaded the .ZIP version of the Developer Edition OS.
I went in command prompt, I typed
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip PN07IMG_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.zip
****GOT AN ERROR*****
Code:
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
.... so again:
fastboot flash zip PN07IMG_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.zip
10 minutes later
fastboot reboot
Oh my was I happy to see the white HTC Startup.
Click to expand...
Click to collapse
THANK YOU MAN!!!!!!!! You just saved me. I had the same problem except I had OTA .17 and trying to flash .16. My device was all jacked up but it's back to original.
Bosnazmaj said:
I am having an issue that I have not seen before and could not find any resolve thru XDA or Google. I am attempting to restore the 64G Developer Edition with the RUU from HTC Dev and I keep getting the 155 error. I even have attempted to install thru CWM the .zip. Still no avail.
I am currently rooted, and have CWM installed. The device is obviously Bootloader unlock. What I was able to find is that it possibly could be a issue that it is bootloader unlocked as some posts suggest to have you bootloader locked to install RUU, but that is obviosely not a posibility with the dev ed.
So what am I doing wrong, or what is the issue. I have confirmed that I was using the correct RUU.
Help Appreciated
.........
Click to expand...
Click to collapse
Bosnazmaj - thank you for this wonderful write-up & knowledge. I have a Dev edition myself. Sometime ago, I got into charging issues. Initially, assuming it to be software issues, I thought I'd run the RUU. So, like you, I too figured out that I have to lock my bootloader. Ran the RUU....long story short, found out that I have to give my phone for repairs (turned out to be a hardware issue).
So, the point I am trying to make is that, if we unlock the bootloader, certain apps (like flashlight, sound recorder etc) seems to get deleted. While this, on it's own, might not sound too alarming....the problem is, if these apps are not present, then the OTA does not & will not get applied as the OTA says that these apps have to be present. I am not sure how to unlock the bootloader without losing any apps.
Any knowledge / information on this is MOST appreciated.
Actually I used titanium backup to back those apps that disappear during root before I unlocked anything. Then once I rooted and unlocked I just restored them back with titanium and all was fine. But in reality you don't want to so an ota when you are rooted as you might loose root.
Sent from my HTC One using Tapatalk 2
Can't you re-unlock the phone using following command without going through the HTCDev website mess?
Code:
fastboot oem unlock
Just a heads up. I was able to return to stock using the RUU without locking the bootloader. It took a while to figure it out.
I went from ARHD 31 to A stock rom (m7_stock_dev_1.29.1540.16_signed_052313.zip) found on an old thread, also had to find a stock recovery that would work (i think it was the one liked in the ARHD thread) and used the revone S-off method, then applied the latest RUU from the htc dev site .and it installed and the bootloader remained unlocked.
I had to get this thing ready for someone who bought it. They asked if i could return it to stock with S-off. It was a pain in the but, but got it working
Hi so basically my One M8 for Sprint is COMPLETELY BRICKED! The phone cannot be repaired as far as I know because it is not S-Off and I can only boot into boot loader.
Alright so here's the situation, I am going to setup a repair and my options are:
1. I send the phone in and they repair the phone.
2. I pay $20, ship my phone and after DIAGNOSTICS they send me a replacement phone NOT the original one.
3. I pay $30 BUT they ship me the phone first and can charge me full price if they reject my claim without my approval.
What do you guys think would be the best option? and what should I say is the reason I need the repair? Should I just say something like the speakers are not clear or the headphone jack doesn't work?
When I spoke with the rep it sounded like they are more concerned about any hardware defects rather than software but she did say any unauthorized software usage will result in denied repair.
Also, keep in mind the phone will only boot into BOOTLOADER and has the "Tampered" "Relocked" and "Security Warning" banner.
Thankyou.
YungMoola15 said:
Hi so basically my One M8 for Sprint is COMPLETELY BRICKED! The phone cannot be repaired as far as I know because it is not S-Off and I can only boot into boot loader.
Alright so here's the situation, I am going to setup a repair and my options are:
1. I send the phone in and they repair the phone.
2. I pay $20, ship my phone and after DIAGNOSTICS they send me a replacement phone NOT the original one.
3. I pay $30 BUT they ship me the phone first and can charge me full price if they reject my claim without my approval.
What do you guys think would be the best option? and what should I say is the reason I need the repair? Should I just say something like the speakers are not clear or the headphone jack doesn't work?
When I spoke with the rep it sounded like they are more concerned about any hardware defects rather than software but she did say any unauthorized software usage will result in denied repair.
Also, keep in mind the phone will only boot into BOOTLOADER and has the "Tampered" "Relocked" and "Security Warning" banner.
Thankyou.
Click to expand...
Click to collapse
If you can boot into the bootloader your m8 is NOT COMPLETELY BRICKED !..... you can try unlocking the bootloader again, reflashing a custom recovery and a rom.
He will need to pull the boot.img from the Rom since he is not s off.
Your phone is not bricked. By any chance did you do a backup before flashing a new Rom??
Sent from my HTC6525LVW using XDA Premium HD app
rider5512 said:
If you can boot into the bootloader your m8 is NOT COMPLETELY BRICKED !..... you can try unlocking the bootloader again, reflashing a custom recovery and a rom.
Click to expand...
Click to collapse
lucky_strike33 said:
He will need to pull the boot.img from the Rom since he is not s off.
Your phone is not bricked. By any chance did you do a backup before flashing a new Rom??
Sent from my HTC6525LVW using XDA Premium HD app
Click to expand...
Click to collapse
OMG You guys just gave me so much hope. If you one of you guys could please me I am willing to compensate for your time. I was an iPhone user previous to this so I am not too knowledgeable but I can definitely follow directions. I had a M7 a year ago and similar thing happened to it but I was able to fix it with the RUU but not this time.
If you guys could just look over my previous thread to give you an idea of whats going on i would much appreciate it.
http://forum.xda-developers.com/htc...-isnt-sprint-m8-factory-t2819981/post54300608
lucky_strike33 said:
He will need to pull the boot.img from the Rom since he is not s off.
Your phone is not bricked. By any chance did you do a backup before flashing a new Rom??
Sent from my HTC6525LVW using XDA Premium HD app
Click to expand...
Click to collapse
There are no backup. Please help me
YungMoola15 said:
There are no backup. Please help me
Click to expand...
Click to collapse
I believe there is a backup for you to use here : http://forum.xda-developers.com/showthread.php?t=2736048
The problem is you relocked the bootloader (as mentioned in your other post).
Have you try to get unlock_code from HTC ? I don't remember whether you can re-unlock the phone without a proper OS but worth a try.
What's your CID as I can't find it in other post.
YungMoola15 said:
There are no backup. Please help me
Click to expand...
Click to collapse
Go to this link here and find the link to the 1.54.651.10 RUU (do not do this if you updated to the most recent update that added WiFi calling or if you have a Harman/Kardon version. There are links to the HK RUU's at this same link). Follow the instructions listed at that link to run the RUU. Afterwards your phone should be working fine.
This thread here may also be useful to you.
ckpv5 said:
I believe there is a backup for you to use here : http://forum.xda-developers.com/showthread.php?t=2736048
The problem is you relocked the bootloader (as mentioned in your other post).
Have you try to get unlock_code from HTC ? I don't remember whether you can re-unlock the phone without a proper OS but worth a try.
What's your CID as I can't find it in other post.
Click to expand...
Click to collapse
Damn F, the bootloader was unlocked before and also had TWRP recovery. My dumbass unrooted it. Here is the info:
YungMoola15 said:
Damn F, the bootloader was unlocked before and also had TWRP recovery. My dumbass unrooted it. Here is the info:
Click to expand...
Click to collapse
Nothing showing
Magnum_Enforcer said:
Nothing showing
Click to expand...
Click to collapse
Magnum_Enforcer said:
Go to this link here and find the link to the 1.54.651.10 RUU (do not do this if you updated to the most recent update that added WiFi calling or if you have a Harman/Kardon version. There are links to the HK RUU's at this same link). Follow the instructions listed at that link to run the RUU. Afterwards your phone should be working fine.
This thread here may also be useful to you.
Click to expand...
Click to collapse
I am really sorry but I can't post right away because XDA hasn't approved me so I only post 5 minutes between.
Don't I have to S-off for the SD card method?
Here's the pic
YungMoola15 said:
I am really sorry but I can't post right away because XDA hasn't approved me so I only post 5 minutes between.
Don't I have to S-off for the SD card method?
Here's the pic
Click to expand...
Click to collapse
You shouldn't, no. But you can also run it from your PC. Hit the second link in my sig and scroll down to the RUU section. I have instructions posted there on how to run the RUU from your PC.
Magnum_Enforcer said:
You shouldn't, no. But you can also run it from your PC. Hit the second link in my sig and scroll down to the RUU section. I have instructions posted there on how to run the RUU from your PC.
Click to expand...
Click to collapse
Hi i am probably an idiot but is there a RUU for my phone? From the pic I uploaded do you know which ruu version I need? Since I am not S-off it has to be the exact version and the instruction you gave said:
"To run a RUU, simply download the RUU you wish to install to your PC, then connect your phone and PC via USB cable. Once connected, simply double-click the RUU file on your computer to start the installer, then follow the on-screen instructions. Normally, a RUU is run while the phone is booted to the OS but alternatively, can be run while the phone is connected to the computer via Fastboot USB mode. If your device is S-on you will need to relock your bootloader to run a RUU. Use the command "fastboot oem lock" to relock your bootloader (without quotation marks)."
But even after relocking my bootloader and using the 1.54.654.9 RUU .exe I get the error 131 on stage 1/7 Sending Signature. Please see the attached pics. BTW you don't know how much I appreciate your help and you will be compensated.
YungMoola15 said:
Hi i am probably an idiot but is there a RUU for my phone? From the pic I uploaded do you know which ruu version I need? Since I am not S-off it has to be the exact version and the instruction you gave said:
"To run a RUU, simply download the RUU you wish to install to your PC, then connect your phone and PC via USB cable. Once connected, simply double-click the RUU file on your computer to start the installer, then follow the on-screen instructions. Normally, a RUU is run while the phone is booted to the OS but alternatively, can be run while the phone is connected to the computer via Fastboot USB mode. If your device is S-on you will need to relock your bootloader to run a RUU. Use the command "fastboot oem lock" to relock your bootloader (without quotation marks)."
But even after relocking my bootloader and using the 1.54.654.9 RUU .exe I get the error 131 on stage 1/7 Sending Signature. Please see the attached pics. BTW you don't know how much I appreciate your help and you will be compensated.
Click to expand...
Click to collapse
Use the RUU for the 1.54.651.10 update as I previously mentioned. This update is newer than the current software version you have. You can upgrade while S-on, you just can't go backwards (unless you're S-off). The RUU can be found in this post along with installation instructions. Try the install method that's mentioned in the post and then if that doesn't work try the PC method. If using the PC method make sure you see "Fastboot USB" hightlighted in red above the bootloader menu screen prior to running the RUU. This means that your phone and PC are properly connected.
You may also find this guide useful.
Magnum_Enforcer said:
Use the RUU for the 1.54.651.10 update as I previously mentioned. This update is newer than the current software version you have. You can upgrade while S-on, you just can't go backwards (unless you're S-off). The RUU can be found in this post along with installation instructions. Try the install method that's mentioned in the post and then if that doesn't work try the PC method. If using the PC method make sure you see "Fastboot USB" hightlighted in red above the bootloader menu screen prior to running the RUU. This means that your phone and PC are properly connected.
You may also find this guide useful.
Click to expand...
Click to collapse
I am in the process of doing the SD Card method (Transferring the file) I will update you. Thank you so much for helping me I really appreciate it brother.
YungMoola15 said:
I am in the process of doing the SD Card method (Transferring the file) I will update you. Thank you so much for helping me I really appreciate it brother.
Click to expand...
Click to collapse
Glad to help. Use that method and disregard my instructions for using the PC method and you should be good to go.
I had to get some clarification from OMJ regarding that RUU. Just follow his instructions in his thread.
Magnum_Enforcer said:
Glad to help. Use that method and disregard my instructions for using the PC method and you should be good to go.
I had to get some clarification from OMJ regarding that RUU. Just follow his instructions in his thread.
Click to expand...
Click to collapse
DUDE YOU ARE A F$#KING LEGEND! I've had the phone for a week and finally today when I was ready to send it for warranty and list it on eBay you came to the rescue.
YungMoola15 said:
DUDE YOU ARE A F$#KING LEGEND! I've had the phone for a week and finally today when I was ready to send it for warranty and list it on eBay you came to the rescue.
Click to expand...
Click to collapse
Glad to help:good:
YungMoola15 said:
DUDE YOU ARE A F$#KING LEGEND! I've had the phone for a week and finally today when I was ready to send it for warranty and list it on eBay you came to the rescue.
Click to expand...
Click to collapse
You should have solved your problem earlier should you post this in correct device forum :silly:
Get the latest firmware RUU unlock bootloader fastboot reboot RUU make sure rename zip file to firmware.zip put in platform tools folder in sdk......once in bootloader type command fastboot oem rebootRUU .......phone will reboot with black screen and HTC logo.......type fastboot flash firmware firmware.zip let it's do it's thing....once done fastboot reboot should fix temp brick
Sent from my 831C using XDA Premium 4 mobile app