Becool0130 said:
Stock Nandroid for T-Mobile USA:
https://mega.co.nz/#!gpIFGR7L!c5o74Ex6k3wkVlWKWgSrJBrguShtjHXeB6YQPmoqAmM
Click to expand...
Click to collapse
Made this easier for people to find. Send thanks to Becool0130. http://forum.xda-developers.com/showpost.php?p=40745177&postcount=55
To get rid of the write protection on /system, boot up after restore then flash a custom kernel.
For those of you who hate Superuser like me, here is a zip that replaces Superuser with SuperSU.
That would be me the OP says to give thanks to
Here's the direct link to the nandroid download:
Stock Nandroid for T-Mobile USA (TWP Rooted) :
https://mega.co.nz/#!gpIFGR7L!c5o74Ex6k3wkVlWKWgSrJBrguShtjHXeB6YQPmoqAmM
Sent from my HTC One using xda premium
I don't need it but there have been many users inquiring about it. Thanks for the good work!
Sent from my HTC One using Tapatalk 2
AdVanceYourself said:
I don't need it but there have been many users inquiring about it. Thanks for the good work!
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Mega keeps freezing up on me, it gets to like 75% and the page freezes, I tried with ie and chrome, same problem. Can the op or someone else please upload to uploaded?
veliksam said:
Mega keeps freezing up on me, it gets to like 75% and the page freezes, I tried with ie and chrome, same problem. Can the op or someone else please upload to uploaded?
Click to expand...
Click to collapse
Restart your pc and try again please. Actually you can download this directly to your phone too
Sorry to say but this works for everyone else just fine so it's hard to troubleshoot.
Sent from my HTC One using xda premium
Thanks, I'll try again after a restart.
Update: Managed to download it with chrome (didn't restart).
Btw, can anyone tell me how to extract the kernel and make it a zip for flashing via cwm? Also what name is the kernel file? Reason I need this is because I flashed a non stock kernel and incase I want to go back to the stock I want to have it. I haven't seen a stock tmo kernel yet. Thanks
Sent from my HTC One using Tapatalk 2
veliksam said:
Thanks, I'll try again after a restart.
Update: Managed to download it with chrome (didn't restart).
Btw, can anyone tell me how to extract the kernel and make it a zip for flashing via cwm? Also what name is the kernel file? Reason I need this is because I flashed a non stock kernel and incase I want to go back to the stock I want to have it. I haven't seen a stock tmo kernel yet. Thanks
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Ill be the first to admit I don't have a clue. Took me ages to figure out how to do a nandroid
veliksam said:
Thanks, I'll try again after a restart.
Update: Managed to download it with chrome (didn't restart).
Btw, can anyone tell me how to extract the kernel and make it a zip for flashing via cwm? Also what name is the kernel file? Reason I need this is because I flashed a non stock kernel and incase I want to go back to the stock I want to have it. I haven't seen a stock tmo kernel yet. Thanks
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Boot.img. You can use Titanium backup or Nandroid Manager to extract it.
cant boot into recovery with this nandroid
Hey everyone, I had a nandroid but didnt backup my recovery on my tmobile HTC one so I downloaded this nandroid and flashed the recovery from it but for some reason I cant boot into recovery, when i press power + volume down it goes into fastboot says tampered relocked and security warning but when i choose bootloader then recovery it just shows the htc logo screen then goes back to the hboot screen. Can anyone help me figure out what is going on?
It works, restored via CWM. Factory reset through settings doesn't work though, probably because it isn't stock recovery. Although, I recommend making a new image OP, your gmail is attached to it still .
Does anyone have the stock tmobile recovery image?
Edit: Found in the dev section under the Dump thread, sorry missed that there was a recovery.img there.
air2k57 said:
It works, restored via CWM. Factory reset through settings doesn't work though, probably because it isn't stock recovery. Although, I recommend making a new image OP, your gmail is attached to it still .
Click to expand...
Click to collapse
I have the oddest luck with restoring this same nandroid I made!! LOL -_-
I've tried to with TWP recovery. Rebooted and tried but it doesnt flash. It takes me back to the same screen really.
I've downloaded CWM recovery and having probs recognizing it there. Wont recognize my TWP backups.
Any step by step instructions? Yea.. the irony in that right?
formula84 said:
Does anyone have the stock tmobile recovery image?
Edit: Found in the dev section under the Dump thread, sorry missed that there was a recovery.img there.
Click to expand...
Click to collapse
I'm not sure if he changed out the recovery in the op or not, so if it doesn't work for u send me a PM and I'll give u a link to the proper tmo recovery.
Team-Noctural.com/androidtechy.com/droidnow.com.
Not working
Becool0130 said:
That would be me the OP says to give thanks to
Here's the direct link to the nandroid download:
Stock Nandroid for T-Mobile USA (TWP Rooted) :
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Could you please reload or fix the link? I clicked on your link and it kept saying that the file was unavailable. Thanks for your hard work!
Becool0130 said:
I have the oddest luck with restoring this same nandroid I made!! LOL -_-
I've tried to with TWP recovery. Rebooted and tried but it doesnt flash. It takes me back to the same screen really.
I've downloaded CWM recovery and having probs recognizing it there. Wont recognize my TWP backups.
Any step by step instructions? Yea.. the irony in that right?
Click to expand...
Click to collapse
Hmm, I have no luck seeing that backup in TWRP, but CWM sees it fine. Just have to make sure you have it in the right directory. Make a backup of your current Rom and it is going to create a directory for you, if you delete the old one . Then, throw your backup in there, following same naming scheme .
Sorry it took so long to reply!
SmiLey497 said:
Made this easier for people to find. Send thanks to Becool0130. http://forum.xda-developers.com/showpost.php?p=40745177&postcount=55
To get rid of the write protection on /system, boot up after restore then flash a custom kernel.
For those of you who hate Superuser like me, here is a zip that replaces Superuser with SuperSU.
Click to expand...
Click to collapse
It works! Thank you so much.
thanks for the good work！！
Does anyone have a mirror? Link is dead now.
Nevermind. Got it from mugetsu
Becool0130 said:
That would be me the OP says to give thanks to
Here's the direct link to the nandroid download:
Stock Nandroid for T-Mobile USA (TWP Rooted) :
https://mega.co.nz/#!gpIFGR7L!c5o74Ex6k3wkVlWKWgSrJBrguShtjHXeB6YQPmoqAmM
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Question - I have been trying to go back to Stock to see if I can get 4G again (i am stuck on Edge ever since I rooted and put AOKP 4.1.2 ROM on - currently on)... given my phone info below, can someone tell me if I should be OK with flashing this tmobile stock zip ????? Please help..
I have HTC ONE S - Tmobile U.S - Tampered / Unlocked.
HBOOT 1.13
version: 0.5
version-bootloader: 1.13.0000
version-baseband: 1.13.50.05.31
version-cpld: None
version-microp: None
version-main:
serialno: *******
imei: *******
product: vle
platform: HBOOT-8960
modelid: PJ4010000
cidnum: HTC__001
battery-status: good
battery-voltage: 3894mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-d92cc658
hbootpreupdate: 11
gencheckpt: 0
DroidLuvver said:
Question - I have been trying to go back to Stock to see if I can get 4G again (i am stuck on Edge ever since I rooted and put AOKP 4.1.2 ROM on - currently on)... given my phone info below, can someone tell me if I should be OK with flashing this tmobile stock zip ????? Please help..
I have HTC ONE S - Tmobile U.S - Tampered / Unlocked.
HBOOT 1.13
version: 0.5
version-bootloader: 1.13.0000
version-baseband: 1.13.50.05.31
version-cpld: None
version-microp: None
version-main:
serialno: *******
imei: *******
product: vle
platform: HBOOT-8960
modelid: PJ4010000
cidnum: HTC__001
battery-status: good
battery-voltage: 3894mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-d92cc658
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
Have u tried just flashing the latest tmo radio and why is ur hboot 1.13 and ur Cid HTC_001? Those alone tell me that u r not using a T-Mobile HTC One.
androidtechy.com/Team-nocturnal/droidnow.com
http://forum.xda-developers.com/showthread.php?p=43332271
T- Mobile 1.27.531.8 and 1.27.531.11 stock and rooted roms
Related
The basic problem I have is that the software won't apply to my phone correctly.
Software number: 1.02.605.6. Should show 2.01.605.11
Any help would be awesome.
Here is more information that I think could be useful. Please request any additional information or clarification.
I delocked, then I ran the new RUU, then unlocked it back up. I got to the point of basically having everything stock, and it showed the new 2.01.605.11 software number, but obviously I wanted everything back, so I flashed my nand backup using amon ra. I must have missed something because I'm basically back to the same spot I used to be which was that the update would randomly shut my phone down and end on this error "E:Error in /cache/fumo/OTAPkg.zip" in the recovery screen and i'd have to battery pull to make things restart..
I'm not sure if it's different now, but my baseband version shows:
0.95.00.1118r, 0.95.00.1223r
i know the first one is the new baseband. I do not have the 5 signal bars though, although I did when everything was stock for a minute before i started messing with things again.
ON the bootloader screen it shows hboot v2.11
So I think i'm really close just missing something. Is it not cool to just flash my old recovery file that i made before starting this stuff? Did I include too much information when I created it(check too many boxes).. I'm not even sure how to ask this question to be honest.
When I try to do the update itself at this point, it will download and start to apply, and then give me the same error like this one.
'E:Error in /cache/fumo/OTAPkg.zip'
Since doing everything I currently cannot use wifi, it shows "error" in the settings menu which I know is similiar to other errors people have gotten.
I would greatly appreciate any help and explanation!
Have you tried relocking your phone and doing a factory reset via the bootloader? The OTA will pop up once factory reset. This is how to applied the OTA with ease, hope this helps!
I actually did a factory reset before any of this. I should have included that in the OP. Honestly I think it was still locked when I factory reset, but I know it worked in some form because I no longer had amon-ra recovery. I'm like right on the verge of understanding all this kernal stuff on another level but obviously not there yet since I can't figure this OTA out.
So you were rooted debloated but otherwise stock, and you just relocked *which means its still rooted right?* and then factory reset, then the update will apply.. then you unlock it again.. and then you can flash back to your debloated nand backup?
Maybe i'm not understanding flash and recover.. can i not use those interchangeably?
Could my problem be that I did the factory reset before locking it back up? I thought with some methods factory reset wasn't necessary (RUU resets things regardless)..
I believe I relocked, did a factory reset, then once stock rom loaded up I downloaded and installed update. After installing the OTA was when I unlocked again, thats odd I believe once re-locked you lose root access and doing a factory reset will grant you stock unrooted rom. Try deleting the OTA zip from the sd card and redownload. The wifi not working means you had a kernel installed, reinstall stock kernel from NilsP thread and make sure to use Scott's flash tool to flash the boot.img from the kernel. You can get the boot.img from kernel in the PH98IMG.zip which resides in the kernel folder.
You might as well run the RUU for 2.01.605.11. It is the update and will probably fix everything for you. It will get you back to stock, you will just have to unlock the phone after you run the RUU and then reinstall Amon Ra to get root back.
thurst0n said:
I delocked, then I ran the new RUU
Click to expand...
Click to collapse
I've already run the new RUU.
And then you did a restore of a nandroid. Your mainver is now updated and your are trying to run an older mainver, probably why you are having so many issues. Rerun the RUU and act like it is a brand new phone that you just picked up. if you want to run a rom, install from scratch.
richii0207 said:
I believe I relocked, did a factory reset, then once stock rom loaded up I downloaded and installed update. After installing the OTA was when I unlocked again, thats odd I believe once re-locked you lose root access and doing a factory reset will grant you stock unrooted rom. Try deleting the OTA zip from the sd card and redownload. The wifi not working means you had a kernel installed, reinstall stock kernel from NilsP thread and make sure to use Scott's flash tool to flash the boot.img from the kernel. You can get the boot.img from kernel in the PH98IMG.zip which resides in the kernel folder.
Click to expand...
Click to collapse
Ok Im going to sort of "Start over soon" if I can't finnegal a way here shortly.
But I swear it showed 'relocked' in bootloader, and i was still rooted. Relocking it forces everything back to stock, but it sitll shows the updated radio, and hboot2.11
I really don't think I ever flashed a kernal unless you count amon-ra as being a kernal. Again i'm new to this and some of the terminology confuses, me so explanation to the steps helps too.
EmerikL said:
And then you did a restore of a nandroid. Your mainver is now updated and your are trying to run an older mainver, probably why you are having so many issues. Rerun the RUU and act like it is a brand new phone that you just picked up. if you want to run a rom, install from scratch.
Click to expand...
Click to collapse
Ok so basically you're saying I can't have my cake and eat it too? I will have to reset my phone up with apps and settings etc.. I don't use a ROM, I just froze and uninstalled many many things, and installed other things etc..
Is the 'E:Error in /cache/fumo/OTAPkg.zip' caused by the mainver discrepency?
I was trying to prevent starting from scratch, but I suppose backing up from my nandroid is essentially flashing a rom.. right?
Would it possible to achieve my old setup using TI as opposed to amon-ra recovery?
thurst0n said:
Ok so basically you're saying I can't have my cake and eat it too? I will have to reset my phone up with apps and settings etc.. I don't use a ROM, I just froze and uninstalled many many things, and installed other things etc..
Is the 'E:Error in /cache/fumo/OTAPkg.zip' caused by the mainver discrepency?
I was trying to prevent starting from scratch, but I suppose backing up from my nandroid is essentially flashing a rom.. right?
Would it possible to achieve my old setup using TI as opposed to amon-ra recovery?
Click to expand...
Click to collapse
I restored a nand I made before the OTA after I accepted the OTA so it can be done. I wasn't having any issues, certainly not the one you are having. My software says 1.02.605.6 since flashing the older ROM but I still show the new radios listed in baseband, and I'm not getting that error. My mainver is at 2.x. You can check what mainver your phone is on in fastboot using the following command:
fastboot getvar all
But that error is not really a mainver error, at least not like the ones that have been happening. That file you mentioned the error about is the OTA update and your phone seems to be trying to run it or something. I think what is happening is that you are restoring your nand cache and there's a trace of the OTA in there so your phone wants to run the OTA. I would bet that if you delete the OTAPkg.zip file you'll be fine. Either it's there and your phone is trying to run it or your phone thinks it's there and it's not. You might want to look in settings and see what it says about having an update.
Also, wipe your cache and dalvik cache in recovery and see if that fixes it. Especially if that OTA file isn't there, then it must be something else in your cache that wants to run the update.
If that doesn't work, then RUU again and then try restoring your nand without the cache checked. Or if you made a nand right after the RUU restore that. If you didn't, make one after you get RUU and rooted in case you need to revert back. I'm kicking myself cuz I was so excited to get my phone back how I wanted it I forgot to make one myself after I RUU'd today and of course I didn't realize it until right after I confirmed I wanted to flash the custom ROM.
feralicious said:
I restored a nand I made before the OTA after I accepted the OTA so it can be done. I wasn't having any issues, certainly not the one you are having. My software says 1.02.605.6 since flashing the older ROM but I still show the new radios listed in baseband, and I'm not getting that error. My mainver is at 2.x. You can check what mainver your phone is on in fastboot using the following command:
fastboot getvar all
But that error is not really a mainver error, at least not like the ones that have been happening. That file you mentioned the error about is the OTA update and your phone seems to be trying to run it or something. I think what is happening is that you are restoring your nand cache and there's a trace of the OTA in there so your phone wants to run the OTA. I would bet that if you delete the OTAPkg.zip file you'll be fine. Either it's there and your phone is trying to run it or your phone thinks it's there and it's not. You might want to look in settings and see what it says about having an update.
Also, wipe your cache and dalvik cache in recovery and see if that fixes it. Especially if that OTA file isn't there, then it must be something else in your cache that wants to run the update.
If that doesn't work, then RUU again and then try restoring your nand without the cache checked. Or if you made a nand right after the RUU restore that. If you didn't, make one after you get RUU and rooted in case you need to revert back. I'm kicking myself cuz I was so excited to get my phone back how I wanted it I forgot to make one myself after I RUU'd today and of course I didn't realize it until right after I confirmed I wanted to flash the custom ROM.
Click to expand...
Click to collapse
Getvar All shows this
Code:
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.11.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.01.605.11
(bootloader) serialno: 000000
(bootloader) imei: 000000000
(bootloader) product: vigor
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH9810000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4184mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bc948b45
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I need to go to work now, but I appreciate everyones help in this! I must be looking in the wrong spot or it's not there, cuse the OTApkg.zip i cannot find at the moment, i swear i've downloaded it like 20 times over the past 2 weeks haha
feralicious said:
I restored a nand I made before the OTA after I accepted the OTA so it can be done.
Click to expand...
Click to collapse
Same here.
thurst0n said:
Getvar All shows this
Code:
< waiting for device >
(bootloader) version-bootloader: 2.11.0000
(bootloader) version-main: 2.01.605.11
I need to go to work now, but I appreciate everyones help in this! I must be looking in the wrong spot or it's not there, cuse the OTApkg.zip i cannot find at the moment, i swear i've downloaded it like 20 times over the past 2 weeks haha
Click to expand...
Click to collapse
First of all, I would edit your post and delete your serial number and imei as I believe that is sensitive info.
So you are updated based on what you posted, did you check your baseband in settings? That will confirm your radio update. I would try wiping your cache and dalvik cache in recovery. I do think there's some trace of that update and your phone is trying to update but that file isn't there so it errors out.
After you wipe power down, pull battery and then reboot. Hopefully that fixes it.
Then go into settings and see if it shows any updates available for you.
Sent from my ADR6425LVW using Tapatalk
Hi guys,
Guys have a big problem. Okay so I have an HTC ONE Google PLay Edition, that I have managed to get the bootloader unlock. I think I was able to also root but not fully sure. So fast foward today I get the OTA update for the 4.4 and all hell breaks lose. I install it and restart and all i get is blue screen so it wont load. This is also affecting me to be able to connect to my computer because it wont recognize my phone(which was working before this happen) with ADB. BTW, my phone does show S-ON. Can you all please help .Thanks!
FYI also tried wiping using TWRP to wipe my phone and it doent work.
Debizzle said:
Hi guys,
Guys have a big problem. Okay so I have an HTC ONE Google PLay Edition, that I have managed to get the bootloader unlock. I think I was able to also root but not fully sure. So fast foward today I get the OTA update for the 4.4 and all hell breaks lose. I install it and restart and all i get is blue screen so it wont load. This is also affecting me to be able to connect to my computer because it wont recognize my phone(which was working before this happen) with ADB. BTW, my phone does show S-ON. Can you all please help .Thanks!
FYI also tried wiping using TWRP to wipe my phone and it doent work.
Click to expand...
Click to collapse
can get to the bootloader (power+vol down) and get to fastboot USB then run fastboot getvar all and post the results or no
clsA said:
can get to the bootloader (power+vol down) and get to fastboot USB then run fastboot getvar all and post the results or no[/QUOTE
Do i run that command in ADB? If soo ADB is not working for me. Thanks in advance.
Click to expand...
Click to collapse
Debizzle said:
clsA said:
can get to the bootloader (power+vol down) and get to fastboot USB then run fastboot getvar all and post the results or no[/QUOTE
Do i run that command in ADB? If soo ADB is not working for me. Thanks in advance.
Click to expand...
Click to collapse
Ahh here it goes:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.07.1700.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36SW912603
(bootloader) imei: 354439050673690
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4283mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.049s
Click to expand...
Click to collapse
something is odd your version number is not the new version 3.58.1700.5
o and edit you post to remove the serialno nand imei
clsA said:
Debizzle said:
the commands run from a command prompt in a folder that contain adb and the fastboot.exe's do you have this folder ?
Click to expand...
Click to collapse
Yes I do have that folder and I also posted the results from the command prompt in recent comments.
Click to expand...
Click to collapse
Debizzle said:
clsA said:
Yes I do have that folder and I also posted the results from the command prompt in recent comments.
Click to expand...
Click to collapse
do you want to try a factory reset ? you could loose everything on the phone
Click to expand...
Click to collapse
clsA said:
Debizzle said:
do you want to try a factory reset ? you could loose everything on the phone
Click to expand...
Click to collapse
Thats fine, I called my self doing that through the bootloader and using twrp(wipe) but that doesnt work. So ill wait for you to tell me how.
Click to expand...
Click to collapse
Debizzle said:
clsA said:
Thats fine, I called my self doing that through the bootloader and using twrp(wipe) but that doesnt work. So ill wait for you to tell me how.
Click to expand...
Click to collapse
you have already tried the factory reset in the bootloader ?
I think the problem is taking the OTA with TWRP installed ..it's not good
Click to expand...
Click to collapse
clsA said:
Debizzle said:
you have already tried the factory reset in the bootloader ?
Click to expand...
Click to collapse
Yes, btw I dont have an os on the phone at least thats what twrp tells me. Perhaps because I wiped everything but the internal storage.
Click to expand...
Click to collapse
Debizzle said:
clsA said:
Yes, btw I dont have an os on the phone at least thats what twrp tells me. Perhaps because I wiped everything but the internal storage.
Click to expand...
Click to collapse
well you can try and sideload a rom back to the phone from twrp
do you need instructions for sideloading, by the way how did you get twrp back on the phone did it never leave or did you reflash it
do you have a rom or backup on the phone already ?
Click to expand...
Click to collapse
clsA said:
Debizzle said:
well you can try and sideload a rom back to the phone from twrp
do you need instructions for sideloading, by the way how did you get twrp back on the phone did it never leave or did you reflash it
Click to expand...
Click to collapse
Yes I will need those instruction if you dont mind. And the twrp never left. Btw how how are we going to sideload if ADB doesnt work?
Oh can you provided a link to a stock 4.3 google play edition rom that i can still recieve ota updates. Thanks so much for your help!!
Click to expand...
Click to collapse
Debizzle said:
clsA said:
Yes I will need those instruction if you dont mind. And the twrp never left. Btw how how are we going to sideload if ADB doesnt work?
Oh can you provided a link to a stock 4.3 google play edition rom that i can still recieve ota updates. Thanks so much for your help!!
Click to expand...
Click to collapse
adb will work in twrp just not in the bootloader
damn that won't work you need s-off... hold on
download that and I'll post the sideload steps
Set the device into ADB sideload mode. In TWRP you do this by going to Advanced then ADB Sideload.
From the command line, type adb sideload rom.zip
make sure the rom.zip is in the same folder as adb
it takes a few min to copy it over
Click to expand...
Click to collapse
conscious nripter
clsA said:
Debizzle said:
adb will work in twrp just not in the bootloader
Stock(non-rooted) 4.3 RUU Zip: http://d-h.st/8NQ
Mirror: https://mega.co.nz/#!vQgGDIrL!Y9nLRV...MHsPB0qwV7tcX8
MD5: 976ae068b29367025a30178f5eb4099d
download that and I'll post the sideload steps
Click to expand...
Click to collapse
Ok got that downloaded!! Question based on my reading it seems the OTA didnt work because of the S-on? What do you think? Like I said all I did was unlock my bootloader and tried to root last night and everything was good. Tried to get the 4.4 ota and explosion!! Lol
Click to expand...
Click to collapse
Debizzle said:
clsA said:
Ok got that downloaded!! Question based on my reading it seems the OTA didnt work because of the S-on? What do you think? Like I said all I did was unlock my bootloader and tried to root last night and everything was good. Tried to get the 4.4 ota and explosion!! Lol
Click to expand...
Click to collapse
yeah you had 2 problems s-on and custom recovery
here's the rom you need to sideload to your phone the other was a RUU that requires s-off sorry about that
http://forum.xda-developers.com/showthread.php?t=2353033
here's the stock recovery to go with your rom
https://www.dropbox.com/s/rns2nj5hn7lwjln/recovery.img
to flash it fastboot flash recovery recovery.img
Click to expand...
Click to collapse
clsA said:
Debizzle said:
yeah you had 2 problems s-on and custom recovery
here's the rom you need to sideload to your phone the other was a RUU that requires s-off sorry about that
http://forum.xda-developers.com/showthread.php?t=2353033
here's the stock recovery to go with your rom
https://www.dropbox.com/s/rns2nj5hn7lwjln/recovery.img
to flash it fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Ok cls Im getting cannot read sideload in the twrp. On the ADB sideload is saying "starting ADB sideload feature. Its like my computer is not connecting with my phone. It was connecting just fine before this stuff happen.
Click to expand...
Click to collapse
Hold the power button do 10-15 seconds and do a hard reboot and retry
Does adb devices show your phone when your in twrp?
Sent from my HTC One using Tapatalk 4
clsA said:
Hold the power button do 10-15 seconds and do a hard reboot and retry
Does adb devices show your phone when your in twrp?
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
Tried that but my phone is not showing. However does show in device manager as android usb device "my htc".
Ok
Let's try again tomorrow I'm exhausted
Sent from my HTC One using Tapatalk 4
clsA said:
Ok
Let's try again tomorrow I'm exhausted
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
Ok man thanks for all your help it much appreciated!!
Hello,
I hope someone can help me urgently.
I've HTC AMAZE 4G , I do not know its bricked or no
Currently showing HTC logo with black background and 4 Triangle in corners. ( Image attached )
I just tried to root mobile ( Unlocked successfully , Then tried to S-Off it NOT successful, SuperCID also successful , Recovery Update also successful )
After all, wiped all data from Recovery.
Still all is fine and bootloader and recovery will appear when i need them( when pressing Volume down and power )
I just ReLocked bootloader , then installed one of stuck roms ( can not remember exact name, i just downloaded some HTC AMAZE Stuck rom from websites , But i'm sure that rom not customized )
After that installiation, all steps passed with "OK" result. only one of them ( I think ERROR WAS: nfc not reposnded...or something like it )
Then rebooted phone.
After that! HTC logo with 4 Triangle in corners coming up.
I can not access recovery or bootloader page when pressing Volume down and power button.
I only can run fastboot commands.
For example:
C:\adb-fastboot>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.92.0000
INFOversion-baseband: N/A
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOserialno: SH28SVF01437
INFOimei: 357265045498225
INFOproduct: ruby
INFOplatform: HBOOT-8260
INFOmodelid: PH8510000
INFOcidnum: HTC__044
INFObattery-status: good
INFObattery-voltage: 4012mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: RUU
INFOcommitno-bootloader: dirty-b411d064
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.503s
I also tried to install rom via fastboot and also Android rom installer utility.
Here is result from Fastboot:
FAILED (remote: 12 signature verify fail)
I also tried to install boot.img or recovery.img or system.img and all of them same result: FAILED (remote: 12 signature verify fail)
Also tried from Android utility ( Rom installer .exe ):
Error : Invalid Model ID or etc..
Anyway, Its emergency issue and need to fix this phone.
Please help if someone have some experience with this issue.
Thanksssssssssss
I have the same problem 6 mounths ago... I think (not sure ) you must flash the boatloader.... flash boot_signed.img with the boot_signed.bat ... It works for me . Do u have them ?!
thelordofkings97 said:
I have the same problem 6 mounths ago... I think (not sure ) you must flash the boatloader.... flash boot_signed.img with the boot_signed.bat ... It works for me . Do u have them ?!
Click to expand...
Click to collapse
Hi,
Thanks for reply,
Tried it already, and tried again:
C:\adb-fastboot>fastboot flash boot boot_signed.img
sending 'boot' (3812 KB)... OKAY [ 0.809s]
writing 'boot'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 1.325s
At all receiving FAILED (remote: 12 signature verify fail) for all image or rom installiation via fastboot
Your thread is now in the HTC Amaze 4G > Amaze 4G Q&A, Help & Troubleshooting section. Here you may find people offering more help.
Please be sure to post any questions you may have in the approiate location. To find out how, please take a few moments and read THIS.
Thank you
First of all your amaze is S-on you said earlier it was s-off second flash a ruu through the boot loader
Sent from my HTC_Amaze_4G using Tapatalk
Ok now i understand your problen yor boot loader is old version you did not read the instructions right you were to flash another ph85img then your boot loader would have upgraded now you should try to flash a latest t-mobile ruu
Sent from my HTC_Amaze_4G using Tapatalk
---------- Post added at 01:07 AM ---------- Previous post was at 01:05 AM ----------
And try again if you dont understand an instruction you should searc for a video on youtube if still not understanding post a question in related thread and wait for soneone to answer but never do something opposite
Sent from my HTC_Amaze_4G using Tapatalk
your CID says ''INFOcidnum: HTC__044'' means its the amaze asian version..find the GB asian ruu and flash it you cant flash any other RUU without S-OFF
TonyStark said:
Your thread is now in the HTC Amaze 4G > Amaze 4G Q&A, Help & Troubleshooting section. Here you may find people offering more help.
Please be sure to post any questions you may have in the approiate location. To find out how, please take a few moments and read THIS.
Thank you
Click to expand...
Click to collapse
Hi,
Sorry about it, Thanks for note.
ravike14 said:
your CID says ''INFOcidnum: HTC__044'' means its the amaze asian version..find the GB asian ruu and flash it you cant flash any other RUU without S-OFF
Click to expand...
Click to collapse
Hi,
Thank you!
I'll try it and will report here.
Hello,
I just tried with ASIA ROM " RUU_Ruby_hTC_Asia_WWE_1.60.707.3_R_Radio_1.13.550L.13DC_30.69b.550L.101_release_253820_signed.exe '
Signatore Error PASSED ,installation process started.
But finally received NFC FAIL-PU Error.
Partition Update Fail.
Please check attachment images.
Let me know if you have any idea.
Thanks.
thelordofkings97 said:
I have the same problem 6 mounths ago... I think (not sure ) you must flash the boatloader.... flash boot_signed.img with the boot_signed.bat ... It works for me . Do u have them ?!
Click to expand...
Click to collapse
Hello
If you have boot and recovery image files( that files fixed the issue for you, please send them to me )
Thanks
ill try to find it
ourquestinc said:
Hello
If you have boot and recovery image files( that files fixed the issue for you, please send them to me )
Thanks
Click to expand...
Click to collapse
your file is corrupt
you see asian ruu is hard to find i have a zip file but my evo is very slow right now so cant upload and the link i have forgotten but i will search so wait.
Muneeb Saeed said:
your file is corrupt
you see asian ruu is hard to find i have a zip file but my evo is very slow right now so cant upload and the link i have forgotten but i will search so wait.
Click to expand...
Click to collapse
Hello,
I've downloaded it from: http://persianhtc.net
If you can please upload it in one of sharing websites or etc...Also let me know exact size of .exe file and exact name.
Thanks
Any idea?
the internet
ourquestinc said:
Any idea?
Click to expand...
Click to collapse
the name is same as yours but has PH85Img_ in the start and zip in the end i cand upload right now i dont have a login i might have to upload in dropbox or google drive but it will be up tonight or tommorow morning the internet in pakistan is very slow right now.
Ok im getting a 50 kb upload speed now ill upload it tonight and post the link.
Sent from my HTC_Amaze_4G using xda app-developers app
Dear Friend.
If You need Ruby all stock RUU
All here
http://www.androidruu.com/?developer=Ruby
Thanks
Sent from my HTC One XL using xda app-developers app
I checked there is no gb asian ruu i have uploaded mine on google drive ruu if hee wants it hee will msg me actually hes been gone for a day or two i sent him pms but hee didnt respond
Sent from my HTC_Amaze_4G using xda app-developers app
Hello,
Thanks for replies and sorry for the delay,
As i said, I just found right RUU from: http://persianhtc.net/index.php?dir=Amaze 4G(Ruby)/rom/original/EXE/
"RUU_Ruby_hTC_Asia_WWE_1.60.707.3_R_Radio_1.13.550L.13DC_30.69b.550L.101_release_253820_signed.exe"
Installed it, Signature Errors solved, But see attached images.
Any solution?or idea?
Give me your bootloader details.
Sent from my HTC One XL using xda app-developers app
hi lol guys
i have htc amaze x715e inst
i need custom rom like viper rom
rom
nokia alkng said:
hi lol guys
i have htc amaze x715e inst
i need custom rom like viper rom
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2167596
pbergonzi said:
http://forum.xda-developers.com/showthread.php?t=2167596
Click to expand...
Click to collapse
dear sir
s -off not slove with me
no prob
after flash viper rom
wifi not work
please help
viper?
nokia alkng said:
dear sir
s -off not slove with me
no prob
after flash viper rom
wifi not work
please help
Click to expand...
Click to collapse
What is "not slove?"
Which viper rom did you flash?
What happens with wifi?
pbergonzi said:
What is "not slove?"
Which viper rom did you flash?
What happens with wifi?
Click to expand...
Click to collapse
i use this [ROM] Viper Amaze 2.0.2 [Aroma][ Android 4.0.4 | ICS | Sense 4.1][4/15/2014]
but wifi not working
wifi not working
nokia alkng said:
i use this [ROM] Viper Amaze 2.0.2 [Aroma][ Android 4.0.4 | ICS | Sense 4.1][4/15/2014]
but wifi not working
Click to expand...
Click to collapse
Do proper wipe (data/factory reset and "format all partitions except sdcard") to re-flash rom and then re-flash. After launch again, check wifi settings to see if there are available networks.
You already upgraded phone to ICS I think, or rom wouldn't have flashed.
pbergonzi said:
Do proper wipe (data/factory reset and "format all partitions except sdcard") to re-flash rom and then re-flash. After launch again, check wifi settings to see if there are available networks.
You already upgraded phone to ICS I think, or rom wouldn't have flashed.
Click to expand...
Click to collapse
mmmmmmm
in fact befor install wip data and no available wifi networks
pbergonzi said:
Do proper wipe (data/factory reset and "format all partitions except sdcard") to re-flash rom and then re-flash. After launch again, check wifi settings to see if there are available networks.
You already upgraded phone to ICS I think, or rom wouldn't have flashed.
Click to expand...
Click to collapse
could u gave me correct rom
pbergonzi said:
Do proper wipe (data/factory reset and "format all partitions except sdcard") to re-flash rom and then re-flash. After launch again, check wifi settings to see if there are available networks.
You already upgraded phone to ICS I think, or rom wouldn't have flashed.
Click to expand...
Click to collapse
after flash viper rom
wifi error
wifi error
nokia alkng said:
after flash viper rom
wifi error
Click to expand...
Click to collapse
Go in your About Phone and give the kernel and Android Version and software, etc.
Did you upgrade the phone from GB to ICS?
pbergonzi said:
Go in your About Phone and give the kernel and Android Version and software, etc.
Did you upgrade the phone from GB to ICS?
Click to expand...
Click to collapse
good day bro
thanx
is these enugh
C:\android>cd c:\Android
C:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.92.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) serialno: SH289VF00271
(bootloader) imei: 357265045299516
(bootloader) product: ruby
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH8510000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3747mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-b411d064
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.502s
C:\android>fastboot oem readcid
...
(bootloader) cid: HTC__044
OKAY [ 0.006s]
finished. total time: 0.008s
C:\android>
please help thanx
phone
nokia alkng said:
good day bro
thanx
is these enugh
please help thanx
Click to expand...
Click to collapse
Can you still launch android into any rom at all?
pbergonzi said:
Can you still launch android into any rom at all?
Click to expand...
Click to collapse
yap viper rom
but now make auto fast restart
pbergonzi said:
Can you still launch android into any rom at all?
Click to expand...
Click to collapse
I think I bricked my phone...
now make auto restart
rom for you
nokia alkng said:
yap viper rom
but now make auto fast restart
Click to expand...
Click to collapse
If it bootloops, it's not bricked--brick does nothing at all, not even bootloop.
Go into recovery, perform "wipe data/factory reset" and "format all partitions except scared." Download this rom and copy to sdcard, then flash this rom the same way you flashed the viper rom:
http://d-h.st/His
Let me know what happens.
pbergonzi said:
If it bootloops, it's not bricked--brick does nothing at all, not even bootloop.
Go into recovery, perform "wipe data/factory reset" and "format all partitions except scared." Download this rom and copy to sdcard, then flash this rom the same way you flashed the viper rom:
http://d-h.st/His
Let me know what happens.
Click to expand...
Click to collapse
oky
this rom ruu.exe u mean flash it using twrp recovery ??
and after that flash viper rom
exe
nokia alkng said:
oky
this rom ruu.exe u mean flash it using twrp recovery ??
and after that flash viper rom
Click to expand...
Click to collapse
Just run the exe on your windows computer and see if asks you to connect the phone or if you have to connect the phone first with adb or whatever it asks. Just run the exe and see what happens. Search the forum for more information on it--I don't have time right now. DON'T flash viper after using this--just use this to get your phone stable and then see if you want to do something else with the phone, but FIRST at least get the phone stable. Maybe you will want to keep it that way and not flash anything until you become more familiar the process by reading the threads. The important thing right now is to get your phone back to stable working phone, NOT experimentation.
pbergonzi said:
Just run the exe on your windows computer and see if asks you to connect the phone or if you have to connect the phone first with adb or whatever it asks. Just run the exe and see what happens. Search the forum for more information on it--I don't have time right now. DON'T flash viper after using this--just use this to get your phone stable and then see if you want to do something else with the phone, but FIRST at least get the phone stable. Maybe you will want to keep it that way and not flash anything until you become more familiar the process by reading the threads. The important thing right now is to get your phone back to stable working phone, NOT experimentation.
Click to expand...
Click to collapse
again aloot thanx
in fact i need arabic rom
next
is this rom ruu.exe correct with s-on phone ??
pbergonzi said:
Just run the exe on your windows computer and see if asks you to connect the phone or if you have to connect the phone first with adb or whatever it asks. Just run the exe and see what happens. Search the forum for more information on it--I don't have time right now. DON'T flash viper after using this--just use this to get your phone stable and then see if you want to do something else with the phone, but FIRST at least get the phone stable. Maybe you will want to keep it that way and not flash anything until you become more familiar the process by reading the threads. The important thing right now is to get your phone back to stable working phone, NOT experimentation.
Click to expand...
Click to collapse
ERROR (156): IMAGE ERROR :crying::crying::crying::crying:
nokia alkng said:
again aloot thanx
in fact i need arabic rom
next
is this rom ruu.exe correct with s-on phone ??
Click to expand...
Click to collapse
are you there
Hi guys,
I can't install OTA update. It says that my phone may be running a modified version of its system software. So can someone help me please.
Here is the info:
INFOversion: 0.5
INFOversion-bootloader: 3.16.0.000
INFOversion-baseband: 1.15.2133156
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.54.401.5
INFOversion-misc: PVT SHIP S-OFF
INFOserialno: HT45WWM07657
INFOimei: ****************
INFOimei2: Not Support
INFOmeid: 00000000000000
INFOproduct: m8_ul_ca
INFOplatform: hTCBmsm8974
INFOmodelid: 0P6B12000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 0mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: ab0efa49
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.047s
You need to restore the stock ROM for the phone's original CID/MID in order to install an OTA.
Based on your main version number (with "401" in it) you are running a stock or custom ROM based on the Euro ROM.
My CID is 11111111. I think, my phone is an at&t variant "ul_ca". So, if I install the stock rom at&t, it will be sim-locked? Anyway, I can't install a custom recovery on my phone .
rvaaness said:
My CID is 11111111. I think, my phone is an at&t variant "ul_ca".
Click to expand...
Click to collapse
I take back what I said earlier. SuperCID should be okay.
Stock ROM won't relock the SIM.
You need to re-install the stock ROM to OTA. But you might find it easier to just RUU (which will also update your phone to the latest version) rather than searching around for the right stock ROM; as long as you don't mind your data being wiped (which the RUU will do).
rvaaness said:
Anyway, I can't install a custom recovery on my phone .
Click to expand...
Click to collapse
Is your bootloader unlocked?
Fastboot/adb connectivity?
The bootloader is unlocked. But I can't access to recovery. Trying to install different custom recovery, and the phone stuck on it.
Sent from my HTC One_M8 using XDA Free mobile app
rvaaness said:
The bootloader is unlocked. But I can't access to recovery. Trying to install different custom recovery, and the phone stuck on it.
Click to expand...
Click to collapse
Fastboot erase cache, the try installing recovery again. Use current version TWRP (version 2.8)
Fastboot erase cache. And try to install to twrp.
Always recovery boot stuck.
Sent from my HTC One_M8 using XDA Free mobile app
Try running the Lollipop RUU to update the phone.
As long as you don't mind your data being wiped (RUU will wipe your data), the RUU is a better/cleaner install anyway.
I have read somewhere that we must change the cid matching with the RUU. So, I will lose the superCID, right?
Sent from my HTC One_M8 using XDA Free mobile app
rvaaness said:
I have read somewhere that we must change the cid matching with the RUU. So, I will lose the superCID, right?
Click to expand...
Click to collapse
SuperCID is fine. SuperCID by definition passes any CID check. Its only if you are on another carrier's CID, that you need to change it (to match what the RUU is looking for).
Hello,
I was very afraid to do the update by RUU because I had already brick my htc one m8. But finally, I done it. Everything was working but at the step 5/7, my computer said that the fastboot stop working. BUT I rebooted my phone and the ROM at&t works until now. Is it normal? Or must I re-install the RUU? Thank you for your reply.
rvaaness said:
I was very afraid to do the update by RUU because I had already brick my htc one m8. But finally, I done it. Everything was working but at the step 5/7, my computer said that the fastboot stop working. BUT I rebooted my phone and the ROM at&t works until now. Is it normal? Or must I re-install the RUU? Thank you for your reply.
Click to expand...
Click to collapse
Since it seems the RUU didn't run to completion, I'd run it again. Its not uncommon for this to happen.
If you check the hboot number, main version, etc. I have a feeling these have not changed, and that the steps executed successfully involved just pushing the files to the phone (and not actually installing them). But that is just a guess, as I don't know off had what step is what.
Ok. I understand now. But... Now, when I am checking the software update, there is no upadate available however my android version is 4.4.2.
Sent from my HTC One_M8 using XDA Free mobile app
rvaaness said:
Ok. I understand now. But... Now, when I am checking the software update, there is no upadate available however my android version is 4.4.2.
Click to expand...
Click to collapse
You typically won't get OTA updates on the AT&T version M8 unless you are connected to the AT&T network. This is a AT&T specific requirement (other versions will update fine regardless of carrier).
Did you get the original OTA (Post #1) over the network; or did you put the file on the phone yourself manually?
In any case, you can RUU to update all the way up to the latest version Android 5.0, no need to mess with OTAs at all.
I received the OTA by network, and can't put it on my phone manually as I said I can't access to a custom recovery.
I fear to use RUU, in case all steps will be not finished, and I think that maybe last time it was just a chance. Am I wrong?
Sent from my HTC One_M8 using XDA Free mobile app
rvaaness said:
I fear to use RUU, in case all steps will be not finished, and I think that maybe last time it was just a chance. Am I wrong?
Click to expand...
Click to collapse
I already mentioned, that the RUU not running fully the first time is fairly common.
Anything has a small chance to brick the phone (so be aware of the risks and consequences). But this is the official RUU meant for your device. Its one of the safest things around.
Ok. Thank you. But now, I have another problem. A big problem!
My phone was fallen, the screen is not broken, but the phone doesn't turn on. When I plug the charger, the LED is red and there is a picture of charging empty battery. Already try:
1- Push the Power + Volume Up
2- Push the Power + Volume Down
3- Push the Power + Volume Up + Volume Down during 1-2 minutes
Everything is not working. The LED just turn to green and after the same screen battery charging.
Do you think that it is the motherboard? Thank you for the reply.
rvaaness said:
My phone was fallen, the screen is not broken, but the phone doesn't turn on. When I plug the charger, the LED is red and there is a picture of charging empty battery. Already try:
1- Push the Power + Volume Up
2- Push the Power + Volume Down
3- Push the Power + Volume Up + Volume Down during 1-2 minutes
Everything is not working. The LED just turn to green and after the same screen battery charging.
Do you think that it is the motherboard? Thank you for the reply.
Click to expand...
Click to collapse
Try holding combo 1 for a minute or so.
Also, try combo 1 and 2 with and without the charger plugged.
Combo 3 is not a valid combo on this phone, that I am aware. No point in trying it.
Mobo? Maybe. Can be any number of things since you dropped it.