I am trying to flash the radio through fastboot using the command fastboot flash radio radio.img but get this message
sending 'radio' (34557 KB)...
OKAY [ 2.665s]
writing 'radio'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 6.467s
Any idea what i'm doing wrong?
ColSanders0325 said:
I am trying to flash the radio through fastboot using the command fastboot flash radio radio.img but get this message
sending 'radio' (34557 KB)...
OKAY [ 2.665s]
writing 'radio'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 6.467s
Any idea what i'm doing wrong?
Click to expand...
Click to collapse
I've never flashed a radio through Fastboot because I was under the impression that it's not safe to flash a radio outside of HBOOT. I've always flashed radios in HBOOT on my original Incredible as the PB31IMG.zip file. I don't know if it's been proven to be safe in Fastboot or not.
My question for you is why are you trying to flash a radio on the Inc 4G? None have been produced for this phone yet other than the one already installed on the device. I'm not aware of anyone having figured out the RIL yet to produce their own.
As for the error you're getting, it's telling you that your radio image isn't signed. Either you made your own and didn't sign it, or you downloaded/pulled the default radio and it wasn't downloaded correctly.
I'm trying to flash the radio because I changed a setting under phone info that I didn't understand and probably shouldn't have. When looking through the phone info settings, i went to "select radio band" and had the options for 800MHz and 1900MHz. I selected 1900MHz and the option for 800MHz disappeared. I now show no service and can't make calls or send texts. I have tried a factory reset and a new sim card but nothing has helped. I read in other forums that this could fix the problem, but i'm stuck. I also haven't really used adb or fastboot before but have read several tutorials.
ColSanders0325 said:
I'm trying to flash the radio because I changed a setting under phone info that I didn't understand and probably shouldn't have. When looking through the phone info settings, i went to "select radio band" and had the options for 800MHz and 1900MHz. I selected 1900MHz and the option for 800MHz disappeared. I now show no service and can't make calls or send texts. I have tried a factory reset and a new sim card but nothing has helped. I read in other forums that this could fix the problem, but i'm stuck. I also haven't really used adb or fastboot before but have read several tutorials.
Click to expand...
Click to collapse
you also may have to be s-off to flash a radio, but icedragon is correct it's dangerous trying to flash with boot loader, you should flash it with adb
OK, I GOT IT ASS BACKWARDS flash through bootloader not fastboot, sorry about that, i'll be ok when the wind hits me LOL
THIS PHONE IS: PJ53IMG, correct me if i'm wrong, someone
radio needs to be flashed using the PJ53IMG.zip or w.e ours is, it may be that iirc
Aldo101t said:
you also may have to be s-off to flash a radio, but icedragon is correct it's dangerous trying to flash with boot loader, you should flash it with adb
OK, I GOT IT ASS BACKWARDS flash through bootloader not fastboot, sorry about that, i'll be ok when the wind hits me LOL
Click to expand...
Click to collapse
With my original Incredible, I would rename the file PB31IMG.zip as Icedragon suggested. When I downloaded the radio.img file, I was told that I couldn't just rename the file and I don't know what else I would need to do to it to flash through the bootloader.
ColSanders0325 said:
With my original Incredible, I would rename the file PB31IMG.zip as Icedragon suggested. When I downloaded the radio.img file, I was told that I couldn't just rename the file and I don't know what else I would need to do to it to flash through the bootloader.
Click to expand...
Click to collapse
just rename it PJ53IMG, AND put on the root of your sdcard, and boot into the bootloader, it will pick it up and ask to install update. select ok and it will run, remove from card when done. but i don't know if it will run with s-on?????
Aldo101t said:
just rename it PJ53IMG, AND put on the root of your sdcard, and boot into the bootloader, it will pick it up and ask to install update. select ok and it will run, remove from card when done
Click to expand...
Click to collapse
no dont do this,
it doesn't work like that man.
the PJ53IMG.zip needs to have the radio.img in the .zip AND the android-info.txt
u can't just rename a radio.img to a .zip
andybones said:
no dont do this,
it doesn't work like that man.
the PJ53IMG.zip needs to have the radio.img in the .zip AND the android-info.txt
u can't just rename a radio.img to a .zip
Click to expand...
Click to collapse
ok sorry about that, i stand corrected, last thing i want to do is f--k somebodyup
andybones said:
no dont do this,
it doesn't work like that man.
the PJ53IMG.zip needs to have the radio.img in the .zip AND the android-info.txt
u can't just rename a radio.img to a .zip
Click to expand...
Click to collapse
Where can I find the android-info.txt file?
Are these the only 2 files that need to be in the zip?
ColSanders0325 said:
Where can I find the android-info.txt file?
Are these the only 2 files that need to be in the zip?
Click to expand...
Click to collapse
don't know where you can get those, sorry about the mix up, i didn't take in to consideration that you where working with an image file, you can rename a zip to a zip(which i thought you had0)but you can't rename an image file to a zip. you'llhave to find a zip with the radio and such. thank god andy caught that, don't want to mess anyone up,
Related
I have have an htc amaze that is not soff or bootloader unlocked rmember it not .Tbad thing is my volume - button does work it wont let me boot into the bootloader mode to use the recover so i tried to use a regular Ruu to flash the phone . Once it got done it says please get the right update utility and retry flashing. Another thing is my memory card hasn't been working it stoped a month ago . I have been using this RUU RUU_Ruby_Globalive_WWE_1.46.1500.3_Radio_1.10.550L.01v2DC_30.69.550L.10_release_229312_signed
i know its not tmobile but hey on the stickies i dont see one for tmobile AS AN EXE file. If i plug in the phone and flash it i can get into what looks like the bootloader mode but wont let me do anything except for reflashing the phone. Im thinking i can only try to use an original ruu thats a tmobile version, BTW last operating installed was ice cream so that is what i have installed.
1 phone is stock
2 my volume - does not work (cant boot into bootloader )
3 memory card does not work
What?
I can't tell what you are trying to do here, but if it's a question this is the wrong place
Sent from my HTC_Amaze_4G using xda premium
Umm. If I understood right, you should be able to use adb commands to get into bootloader and everything without needing volume buttons. To be honest though is it your memory card? Or the phone won't read them, because if volume buttons aren't working and memory cards aren't either I'd be calling tmobile/htc
Edit: I don't know the adb commands offhand but Google should be able to help you find what you need or this forum could provide the info you need just look around.
Sent from my HTC_Amaze_4G using xda app-developers app
im trying to restore my phone to a working condition this is my problem look, the other thing is when i write comand adb shell it says device not found ????????
i have several phones rooted aside from this phone
my touch 4g
htc vivid
one x
inspire
all working fine
skylinegtrvspec said:
im trying to restore my phone to a working condition this is my problem look, the other thing is when i write comand adb shell it says device not found ????????
i have several phones rooted aside from this phone
my touch 4g
htc vivid
one x
inspire
all working fine
Click to expand...
Click to collapse
Try this command:
fastboot devices
and then tell me if you get a serial number.
ok it sees my device sorry and yes there is a serial number
skylinegtrvspec said:
ok it sees my device
Click to expand...
Click to collapse
Alright, do you have a T-Mobile RUU downloaded? If so, can you tell me where you got it from? I want to verify that you have the right version of the RUU.
I'm going to write a quick program that'll flash the RUU through USB cable, so please wait. If you haven't got the RUU, then please get the correct RUU while I write the script.
RUU:
http://d-h.st/3VD
Be sure to thank Krook6023 for providing this RUU
RUU_Ruby_Globalive_WWE_1.46.1500.3_Radio_1.10.550L .01v2DC_30.69.550L.10_release_229312_signed ive used it once before and it worked now this time it wont . Te ruu that i got was from here
http://forum.xda-developers.com/showthread.php?t=1617644
skylinegtrvspec said:
RUU_Ruby_Globalive_WWE_1.46.1500.3_Radio_1.10.550L .01v2DC_30.69.550L.10_release_229312_signed ive used it once before and it worked now this time it wont . Te ruu that i got was from here
http://forum.xda-developers.com/showthread.php?t=1617644
Click to expand...
Click to collapse
You need a T-Mobile RUU. Download the one I gave you the link to in my last post.
I am, its downloading
skylinegtrvspec said:
I am, its downloading
Click to expand...
Click to collapse
While you wait, could you do a quick fastboot command to prepare for my script?
The command is:
fastboot erase cache
That's all.
When you're done downloading, let us know and then I'll post the script to flash the RUU.
Additional Instructions:
When it's done downloading, please rename the file to PH85IMG
If you do not, the script WILL not work.
ok i will ,its almost done like 5 mins left
ok ready File has been renamed to PH85IMG
and fastboot erase cache has cleared the cache all done
skylinegtrvspec said:
ok i will ,its almost done like 5 mins left
ok ready File has been renamed to PH85IMG
and fastboot erase cache has cleared the cache all done
Click to expand...
Click to collapse
Alright, I've attached the tool. All you need to do is extract the script, and then put the batch file to your desktop. Also, put the PH85IMG.zip file to your desktop, but DO NOT extract it!
After that's done, double click on the RUUFlasher.bat file, and it should automatically start the process. Please make sure your phone is connected to your computer before running the script.
This will take up to 10 minutes, and after it's done, it will reboot your phone, and your phone should be up and running again!
Please post if you get any errors or issues, or just questions about this.
Good Luck!
Just want to know if your phone is a T-Mobile Amaze or not?
Double0EK said:
Just want to know if your phone is a T-Mobile Amaze or not?
Click to expand...
Click to collapse
Look at the picture. It has the T-Mobile logo emblazoned on the top.
did not work ,this is what i did
1 dowlonded the file and did like you said i extract it to the desktop
2 placed the other file PH85IMG in the desktop
3 ran the batch file it started then it stoped nothing happend
skylinegtrvspec said:
did not work ,this is what i did
1 dowlonded the file and did like you said i extract it to the desktop
2 placed the other file PH85IMG in the desktop
3 ran the batch file it started then it stoped nothing happend
Click to expand...
Click to collapse
Give it a minute. It's checking for connection. Try again.
nothing weird ????
look at what i was able to catch, it says fastboot is not recognized as an internal or external command operable program or batch file
i figured out the problem
now the app is working the problem was i did not have in the directory where the fastboot was
it failed look
Device detected!
Now entering RUU mode...
...
(bootloader) Start Verify: 3
(bootloader) Start Verify: 3
(bootloader) erase sector 130560 ~ 131071 (512)
OKAY [ 3.443s]
finished. total time: 3.443s
Now flashing the update! Hang on there!
This will take up to 10 minutes to complete!
DO NOT TOUCH YOUR PHONE!!!
DO NOT UNPLUG THE USB CORD!!!
DO NOT TOUCH ANYTHING!!!
sending 'zip' (498144 KB)...
OKAY [ 57.602s]
writing 'zip'...
(bootloader) adopting the signature contained in this image..
(bootloader) signature checking...
FAILED (remote: 92 supercid! please flush image again immedia
finished. total time: 144.140s
RUU flashed!
The program will now reboot your phone!
Please wait!
Script made by Keylogger_0
Good Luck!
DO NOT CLOSE THIS WINDOW, AS IT MAY
CONTAIN IMPORTANT DIAGNOSTIC INFORMATION!
rebooting...
finished. total time: 3.206s
DO NOT CLOSE THIS WINDOW, AS IT MAY
CONTAIN IMPORTANT DIAGNOSTIC INFORMATION!
Hello,
I have tried to flash a custom ROM to my htc desire x but unfortunetly I am a almost complete noob. I have been using Desire_X_All-In-One_Kit_v2.0 in order to complete the action. The problem is that i have never rooted the fone nor i have put in the recovery into it. So basically i unlocked the bootloader and thought it would all work.Well you know yourselfs it didn't.I have been looking all over the place for a way to get my phone fixed and i found one(ima Junior member can't post links yet ( Re-flash stock ROM (RUU) after bricking a rooted device)) .I have done all the steps but in step5 i get an error
C:\rec>fastboot flash recovery recovery_signed.img
sending 'recovery' (4266 KB)...
OKAY [ 0.795s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.323s
and in step 7 i get Error 140 bootloader error during RUU
Any help here would be greatly appreciated
Regards Kuba
First of all write down all you have written in bootloader screen.
It will be easy to fix it.
nlooooo said:
First of all write down all you have written in bootloader screen.
It will be easy to fix it.
Click to expand...
Click to collapse
How do you mean? do you mean whats written when i enter the bootloader or what have I written in in the terminal ( eg. fastboot flash recovery recovery_signed.img)
Thanks a lot for your quick reply
Bootloader screen, when you enter bootloader.
Also, give me the version of RUU that you have.
nlooooo said:
Bootloader screen, when you enter bootloader.
Also, give me the version of RUU that you have.
Click to expand...
Click to collapse
*****RELOCKED********
PROTO PVT SHIP S-ON RL
HBOOT-1.24.0000
RADIO-1.10.40.23
eMMC-boot
Oct 30 2012, 20:09:09
The most recent RUU i have downloaded is RUU_PROTO_U_ICS_40A_HTC_Europe_1.14.401.1_Radio_10.18.40.05U_1.09.45.201_release_284072_signed
But i have read that FAILED <remote: signature verify fail> error that im getting is related to wrong ruu .I guess you know better
There's a newer release 1.18.401.1 there's a link in Index in my signature, try to download that one and run it with phone booted in fastboot and attached to PC. If that doesn't go will try something else.
nlooooo said:
There's a newer release 1.18.401.1 there's a link in Index in my signature, try to download that one and run it with phone booted in fastboot and attached to PC. If that doesn't go will try something else.
Click to expand...
Click to collapse
Great man!! thanks for help!! Could you just make it clear what i need in the folder with the ruu ?. its Adb.exe AdbWinAp.dll fastBoot.exe and the image file? is there anything else i would need? (as you see i know basically nothing about this)
It's not a folder its exe file, just run it from PC.
nlooooo said:
It's not a folder its exe file, just run it from PC.
Click to expand...
Click to collapse
YOUR Fuc**ng Awsome bruf everything back on track !!.....THank a lot
hlick14 said:
YOUR Fuc**ng Awsome bruf everything back on track !!.....THank a lot
Click to expand...
Click to collapse
That's why I'm here and that's what the thanks button stands for...
Hello Amaze thread. I flashed jose's Dark Glass ROM based off of CM10.1 and one day my phone turned off and wouldn't boot. I went into recovery and it goes into safe mode because the internal memory card is unreadable, tells me to wipe, etc. but it gives me junk errors. My issue is similar to the issue of someone else in another thread http://forum.xda-developers.com/showthread.php?t=1773723(which was resolved)], but I'm not having such an easy time fixing my problem. When I go into the bootloader and try to flash my RUU from mobilicity by changing it's name to PH85IMG, the blue bar fills up, it says "parsing..." but then it goes back to the bootloader. Does anyone know what is going wrong? Thanks in advance to all you helpful people. Sorry if I violated any rules in this post.
Details: S-OFF + bootloader is unlocked
Edit1: I read that my bootloader had to be locked in order to reflash RUU. I relocked it using Hasoon's all-in-one-tool but the zip file would still go back into bootloader after the blue bar fills up. The zip isn't parsing. I also tried using Hasoon's tool to reflash the RUU. Bootloader says re-locked (still s-off) but it still doesn't work. The CMD spits out this:
Code:
sending 'zip' (331249 KB)...
OKAY [ 32.595s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 40.896s
andres8900 said:
Hello Amaze thread. I flashed jose's Dark Glass ROM based off of CM10.1 and one day my phone turned off and wouldn't boot. I went into recovery and it goes into safe mode because the internal memory card is unreadable, tells me to wipe, etc. but it gives me junk errors. My issue is similar to the issue of someone else in another thread http://forum.xda-developers.com/showthread.php?t=1773723(which was resolved)], but I'm not having such an easy time fixing my problem. When I go into the bootloader and try to flash my RUU from mobilicity by changing it's name to PH85IMG, the blue bar fills up, it says "parsing..." but then it goes back to the bootloader. Does anyone know what is going wrong? Thanks in advance to all you helpful people. Sorry if I violated any rules in this post.
Details: S-OFF + bootloader is unlocked
Edit1: I read that my bootloader had to be locked in order to reflash RUU. I relocked it using Hasoon's all-in-one-tool but the zip file would still go back into bootloader after the blue bar fills up. The zip isn't parsing. I also tried using Hasoon's tool to reflash the RUU. Bootloader says re-locked (still s-off) but it still doesn't work. The CMD spits out this:
Code:
sending 'zip' (331249 KB)...
OKAY [ 32.595s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 40.896s
Click to expand...
Click to collapse
In order to flash RUU you will need to be unlocked bootloader because it rejects all time when you try to flash RUU.
So first unlock it and after that try to put ruu on SDcard and then go into recovery .
It will work for sure.
Hit thanks if I helped you !!!
shubham211995 said:
In order to flash RUU you will need to be unlocked bootloader because it rejects all time when you try to flash RUU.
So first unlock it and after that try to put ruu on SDcard and then go into recovery .
It will work for sure.
Hit thanks if I helped you !!!
Click to expand...
Click to collapse
Hi, it still didn't work. Tried it while the bootloader was unlocked and again while it was relocked. It doesn't get past the "parsing" stage. I tried it with two different SD cards already btw and I also checked the MD5 checksum. They match. No luck for me.
andres8900 said:
Hi, it still didn't work. Tried it while the bootloader was unlocked and again while it was relocked. It doesn't get past the "parsing" stage. I tried it with two different SD cards already btw and I also checked the MD5 checksum. They match. No luck for me.
Click to expand...
Click to collapse
Are you sure that your sdcard slot is working ??
Sent from my HTC_Amaze_4G using xda app-developers app
Mobilicity ruu isn't working it's a firmware zip with a update it's not a ruu... And it's not a brick.. Also a ruu can't be flashed from recovery... Flash the t mobile R2 RUU from bootloader and it'll work.
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
HTC preloaded some image files for the "stickers" in the duo effects camera. They are preloaded to /data/preload so you can either flash the zip at the bottom of the second post or manually copy them over to that directory. They (HTC) haven't fully implemented this yet... so you probably won't even notice them missing. The also preload calc and flashlight app this way too.
NOTE- This will work for S-on users provided their current software level is at or below this version. S-off users can user this either way.
OPTION 1)
Rename download file to 0P3PIMG.zip. Make sure you use an SD card formatted to fat32!! (otherwise the phone might not see it) Place file on physical SD card (not internal phone memory)... i repeat physical SD card. Boot up phone to bootloader mode and the phone will auto-detect the file and prompt to install it. Follow any remaining prompts to allow the RUU to flash the software to your phone.
-or-
OPTION 2)
Download file into working fastboot directory. Boot phone to fastboot mode and connect to pc. Type in the following commands.
fastboot oem rebootRUU
fastboot flash zip RUU_T6_Sprint_WWE_1.16.651.4.zip
first time you run this it will be short... so run it a second time
fastboot flash zip RUU_T6_Sprint_WWE_1.16.651.4.zip
The command prompt output will show you details as it flashes each partition and will show you when it has completed. At this time the green bar on the phone will appear 99% of the way across the screen.. Completely normal!~ Issue the next command to kick it out of RUU mode or optionally flash the custom recovery TWRP if you intend to root/flash custom roms and THEN issue the below command to get out of RUU mode.
fastboot reboot
(note) if you just want to reboot back to bootloader you can issue the command fastboot reboot-bootloader This will allow you to boot directly to recovery and start flashing/rooting fun.
I don't own this model phone... so if someone would like to capture the output of the command prompt I would be happy to add it to the OP similar to how I have my VZW ruu threads.
Downloads Do NOT mirror these elsewhere.
RUU Download link
https://www.androidfilehost.com/?fid=23622183712460121
Data preload apps/stickers
https://www.androidfilehost.com/?fid=23622183712460132
RUU Mode TWRP 2.7.1 (must be s-off or unlocked)
https://www.androidfilehost.com/?fid=23622183712460136
Getting error, too many links
I followed the directions, but when I do I get an error: FAILED (status read failed (Too many links))
output:
sending 'zip' (1271836 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOrom parsing start ...
INFOrom parsing finish ...
INFOzip header checking...
INFOzip info parsing...
INFORead zipped android_info fail
FAILED (status read failed (Too many links))
martinoj2009 said:
I followed the directions, but when I do I get an error: FAILED (status read failed (Too many links))
output:
sending 'zip' (1271836 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOrom parsing start ...
INFOrom parsing finish ...
INFOzip header checking...
INFOzip info parsing...
INFORead zipped android_info fail
FAILED (status read failed (Too many links))
Click to expand...
Click to collapse
Did your md5 check out fine?
dottat said:
Did your md5 check out fine?
Click to expand...
Click to collapse
Yes
8f380af56b92ac2c4e3055b9a43b5871 ruu_t6_sprint_wwe_1.16.651.4.zip
martinoj2009 said:
Yes
8f380af56b92ac2c4e3055b9a43b5871 ruu_t6_sprint_wwe_1.16.651.4.zip
Click to expand...
Click to collapse
Do you have an sd card to try it via option 1?
dottat said:
Do you have an sd card to try it via option 1?
Click to expand...
Click to collapse
I'm sure I do, I'll let you know, and thanks for the prompt reply!
martinoj2009 said:
I'm sure I do, I'll let you know, and thanks for the prompt reply!
Click to expand...
Click to collapse
Not a problem. Also, under my android file host I have a mini sdk zip. You try using that on your pc too...it's a newer version of Fastboot/adb. All you have to do is unzip it and use it from wherever you unzip it to.
dottat said:
Not a problem. Also, under my android file host I have a mini sdk zip. You try using that on your pc too...it's a newer version of Fastboot/adb. All you have to do is unzip it and use it from wherever you unzip it to.
Click to expand...
Click to collapse
So I did this, no errors, but when I rebooted it went right into Cyanogenmod. Am I missing a step?
martinoj2009 said:
So I did this, no errors, but when I rebooted it went right into Cyanogenmod. Am I missing a step?
Click to expand...
Click to collapse
How long did it take to run the zip?
dottat said:
How long did it take to run the zip?
Click to expand...
Click to collapse
It takes a while ~5mins, it loads the file, then checks the signature, and then says ROM parsing start (for 5 seconds) and then tells me to press the power button to reboot.
martinoj2009 said:
It takes a while ~5mins, it loads the file, then checks the signature, and then says ROM parsing start (for 5 seconds) and then tells me to press the power button to reboot.
Click to expand...
Click to collapse
You have to do it twice if the first time is short. Sometimes it can only update certain files first.
You are s off right?
dottat said:
You have to do it twice if the first time is short. Sometimes it can only update certain files first.
You are s off right?
Click to expand...
Click to collapse
Lol, shhhh, forgot to S-Off
martinoj2009 said:
Lol, shhhh, forgot to S-Off
Click to expand...
Click to collapse
OK... so if you aren't S-off AND this firmware is older than what you have it will fail. Only S-off can downgrade. You guys don't have a newer RUU yet and there were two OTAs after this one. Definitely S-off that thing while you still can (assuming it's not too late).
@dottat
I have developer edition device and have ruu for it to stock jellyben
But I found that I can't flash the ruu to go back to jellyben from sense 6 firmware and the error was the same as mentioned above in other comments .. android info fail too many links
And after a lot of trials, I found that the rug is fine not damaged so I flashed the firmware if sense 5.5 and then tried the ruu again and it works perfect
So from my point , I think that older jb ruus can't be flashed if u have sense 6 firmware
So only I need tho flash firmware zip of sense 5.5 not the whole system the try the ruu again although both sense 6 and sense 5.5 have hboot 2.49 but I think that the one that came with sense 6 have some modifications
Also I tried to flash from sd card but no go so the only solution is flashing hboot of sense 5.5
Maybe it's the same with Sprint devices but I think that it will be the same
mido.fayad said:
@dottat
I have developer edition device and have ruu for it to stock jellyben
But I found that I can't flash the ruu to go back to jellyben from sense 6 firmware and the error was the same as mentioned above in other comments .. android info fail too many links
And after a lot of trials, I found that the rug is fine not damaged so I flashed the firmware if sense 5.5 and then tried the ruu again and it works perfect
So from my point , I think that older jb ruus can't be flashed if u have sense 6 firmware
So only I need tho flash firmware zip of sense 5.5 not the whole system the try the ruu again although both sense 6 and sense 5.5 have hboot 2.49 but I think that the one that came with sense 6 have some modifications
Also I tried to flash from sd card but no go so the only solution is flashing hboot of sense 5.5
Maybe it's the same with Sprint devices but I think that it will be the same
Click to expand...
Click to collapse
Either way....without being s off you can't downgrade firmware anyways. On my vzw rezound, m7, m8, and t6 I can simply flash ruus up or down all day long.
dottat said:
Either way....without being s off you can't downgrade firmware anyways. On my vzw rezound, m7, m8, and t6 I can simply flash ruus up or down all day long.
Click to expand...
Click to collapse
Yes I know that I should be s-off
And that's why I said I should downgrade first to sense 5.5 firmware then flash the ruu
And I won't be able to downgrade without s-off
So I was writing only about the error when I already have a-off because it took me 2 days till I found this fix after many trials
posted a current RUU for s-off users here...
http://forum.xda-developers.com/htc...rint-ruu-3-02-651-5-s-off-pre-rooted-t2865704
i have some troubles here
im in the HBOOT 2.49 i need to downgrade to the first HBOOT to install this RUU i need to know if make S-OFF with sunshine how to downgrade can any one. explain me how to do it ...dotatt dude u r awesome i always follow ur work and u r the best ...
please help me a little i have the knowledge to do it i just need a direction thx in advance
w1n73rf3ll said:
im in the HBOOT 2.49 i need to downgrade to the first HBOOT to install this RUU i need to know if make S-OFF with sunshine how to downgrade can any one. explain me how to do it ...dotatt dude u r awesome i always follow ur work and u r the best ...
please help me a little i have the knowledge to do it i just need a direction thx in advance
Click to expand...
Click to collapse
IF sunshine doesn't work on your current rom (have you tried running it yet).... you need to unlock your bootloader and flash a 100% stock older rom. Then use that to s-off. Then flash whatever rom you want and sim unlock.
I seem to have confirmation, from HTC and from THIS site: http://www.androidpit.com/what-is-my-firmware-number
... that the software number IS the firmware number on this phone.
BUT ...*if* that's true, then - why is the viper page so concerned with the firmware (mainver) number NOT being available through "fastboot getvar all" with TWRP on the phone?
Wombat Pete said:
I seem to have confirmation, from HTC and from THIS site: http://www.androidpit.com/what-is-my-firmware-number
... that the software number IS the firmware number on this phone.
BUT ...*if* that's true, then - why is the viper page so concerned with the firmware (mainver) number NOT being available through "fastboot getvar all" with TWRP on the phone?
Click to expand...
Click to collapse
Software number is the number of base your ROM is set off. If you update firmware but don't update ROM your software number will not change an match your firmware numbers in bootloader....when wanting to verify firmware numbers I only do it in bootloader. Just what I do.
Tigerstown said:
Software number is the number of base your ROM is set off. If you update firmware but don't update ROM your software number will not change an match your firmware numbers in bootloader....when wanting to verify firmware numbers I only do it in bootloader. Just what I do.
Click to expand...
Click to collapse
Thanks ...I am, however, in the situation described: I've used TWRP and fastboot doesn't show a mainver.
What can I do - what would you do? - to determine firmware number in that case?
Wombat Pete said:
Thanks ...I am, however, in the situation described: I've used TWRP and fastboot doesn't show a mainver.
What can I do - what would you do? - to determine firmware number in that case?
Click to expand...
Click to collapse
You must have been on a old twrp that had a bug that remove os number. So flash the latest twrp an then flash the latest firmware zip an it will show....or you can go to about phone an find your radios an find out what firmware had those radios. Myself I would upgrade twrp flash latest firmware an be good.
Tigerstown said:
You must have been on a old twrp that had a bug that remove os number. So flash the latest twrp an then flash the latest firmware zip an it will show....or you can go to about phone an find your radios an find out what firmware had those radios. Myself I would upgrade twrp flash latest firmware an be good.
Click to expand...
Click to collapse
So... when I do that, it'll replace the older TWRP, yes? I think the latest is 2.8 (here: http://teamw.in/project/twrp2/225)
...BUT then the newbie question: how to determine the latest firmware? What info do I need to provide to figure that out? And thanks once again, it is greatly, greatly appreciated.
Wombat Pete said:
So... when I do that, it'll replace the older TWRP, yes? I think the latest is 2.8 (here: http://teamw.in/project/twrp2/225)
...BUT then the newbie question: how to determine the latest firmware? What info do I need to provide to figure that out? And thanks once again, it is greatly, greatly appreciated.
Click to expand...
Click to collapse
Yea its 2.8.5.0 an just place in fastboot folder an reboot phone to bootloader then in terminal type
Fastboot flash recovery nameoffile.img
That will flash twrp.
Tigerstown said:
Yea its 2.8.5.0 an just place in fastboot folder an reboot phone to bootloader then in terminal type
Fastboot flash recovery nameoffile.img
That will flash twrp.
Click to expand...
Click to collapse
Got that, I've been doing that successfully enough. But you wrote: "flash the latest twrp and then flash the latest firmware zip"
It's the second part of that I'm not entirely sure of - the latest firmware zip ...for 4.4.4? For this phone? You didn't just mean updating TWRP, right? That's the newbie question I'm asking - after I flash the latest TWRP, how do I determine the right (best) firmware zip to flash thereafter?
Wombat Pete said:
Got that, I've been doing that successfully enough. But you wrote: "flash the latest twrp and then flash the latest firmware zip"
It's the second part of that I'm not entirely sure of - the latest firmware zip ...for 4.4.4? For this phone? You didn't just mean updating TWRP, right? That's the newbie question I'm asking - after I flash the latest TWRP, how do I determine the right (best) firmware zip to flash thereafter?
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=95916177934529541
Latest Att firmware zip. Needs to be flash via fastboot have you ever flash firmware before?
Tigerstown said:
https://www.androidfilehost.com/?fid=95916177934529541
Latest Att firmware zip. Needs to be flash via fastboot have you ever flash firmware before?
Click to expand...
Click to collapse
I just rooted the phone, in the process of which i flashed the (older, obviously, with the bug) version of twrp onto the phone. Established SU, etc.. I'm planning to get the latest viper rom on the phone - that's why i need to know the firmware number, because the instructions for getting viper on the phone begin with getting and flashing a Stock Backup and a stock recovery that
(i) corresponding with my current firmware version (newest, but definitely not newer), and
(ii) have the same SKU (x.xx.401.x) as this phone.
So ...I've flashed things,but - no, haven't flashed firmware before.
And any advice will be appreciated!
Wombat Pete said:
I just rooted the phone, in the process of which i flashed the (older, obviously, with the bug) version of twrp onto the phone. Established SU, etc.. I'm planning to get the latest viper rom on the phone - that's why i need to know the firmware number, because the instructions for getting viper on the phone begin with getting and flashing a Stock Backup and a stock recovery that
(i) corresponding with my current firmware version (newest, but definitely not newer), and
(ii) have the same SKU (x.xx.401.x) as this phone.
So ...I've flashed things,but - no, haven't flashed firmware before.
And any advice will be appreciated!
Click to expand...
Click to collapse
That'd how you flash firmware. Via fastboot
Download firmware zip
reboot your phone to bootloader
Place your firmware zip in your fastboot folder
Open CMD terminal on pc in your file you fastboot from.
Plug phone into pc
In terminal first cmd you need is
Fastboot oem rebootRUU
fastboot flash zip nameofyourfile.zip
It should ask you to reflush immediately in your cmd terminal,when it does proceed to next cmd
fastboot flash zip nameofyourfile.zip
Once all is good on your end an your ready to reboot phone use this final cmd
Fastboot reboot-bootloader
Tigerstown said:
That'd how you flash firmware. Via fastboot
Download firmware zip
reboot your phone to bootloader
Place your firmware zip in your fastboot folder
Open CMD terminal on pc in your file you fastboot from.
Plug phone into pc
In terminal first cmd you need is
Fastboot oem rebootRUU
fastboot flash zip nameofyourfile.zip
It should ask you to reflush immediately in your cmd terminal,when it does proceed to next cmd
fastboot flash zip nameofyourfile.zip
Once all is good on your end an your ready to reboot phone use this final cmd
Fastboot reboot-bootloader
Click to expand...
Click to collapse
I'm pretty sure that all makes sense to me - I'll do it tomorrow and report what happens here!
Tigerstown said:
That'd how you flash firmware. Via fastboot
Download firmware zip
reboot your phone to bootloader
Place your firmware zip in your fastboot folder
Open CMD terminal on pc in your file you fastboot from.
Plug phone into pc
In terminal first cmd you need is
Fastboot oem rebootRUU
fastboot flash zip nameofyourfile.zip
It should ask you to reflush immediately in your cmd terminal,when it does proceed to next cmd
fastboot flash zip nameofyourfile.zip
Once all is good on your end an your ready to reboot phone use this final cmd
Fastboot reboot-bootloader
Click to expand...
Click to collapse
Part 1 was successful, part 2 - not.
I put the firmware file in root storage for the phone and in the fastboot directory of the computer, rebooted to fastboot and did what you said, but it failed:
target reported max download size of 1826414592 bytes
sending 'zip' (32221 KB)...
OKAY [ 2.031s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 2.054sI note that the firmware zip file to which you directed me ends in "S-off".
This phone is S-on still. Do I need S-off?
Or is there a firmware zip for S-on?
Or is that not the problem - was I supposed to have booted into TWRP?
Thanks, as ever
Wombat Pete said:
Part 1 was successful, part 2 - not.
I put the firmware file in root storage for the phone and in the fastboot directory of the computer, rebooted to fastboot and did what you said, but it failed:
target reported max download size of 1826414592 bytes
sending 'zip' (32221 KB)...
OKAY [ 2.031s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 2.054sI note that the firmware zip file to which you directed me ends in "S-off".
This phone is S-on still. Do I need S-off?
Or is there a firmware zip for S-on?
Or is that not the problem - was I supposed to have booted into TWRP?
Thanks, as ever
Click to expand...
Click to collapse
Yea s-off is needed..pretty sure I said that in a early post.
Additional info: redid it, tried with TWRP running, terminal didn't respond. So, as I presumed, we meant - have the phone in fastboot.
So I did that again, here's the terminal result:
C:\...FASTBOOTDIRECTORY>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.014s]
finished. total time: 0.017s
C:\...FASTBOOTDIRECTORY>fastboot flash zip ATT444fi
rmwareS_OFF.zip
target reported max download size of 1826418688 bytes
sending 'zip' (32221 KB)...
OKAY [ 2.027s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 4.273s
Tigerstown said:
Yea s-off is needed..pretty sure I said that in a early post.
Click to expand...
Click to collapse
Ah, ok. I'll do that, then.
I'm planning on following these instructions: http://htc-one.wonderhowto.com/how-...-one-m8-install-custom-firmware-mods-0154461/
Wombat Pete said:
Ah, ok. I'll do that, then.
I'm planning on following these instructions: http://htc-one.wonderhowto.com/how-...-one-m8-install-custom-firmware-mods-0154461/
Click to expand...
Click to collapse
Pretty sure that exploit is dead. I would try sunshine here.
http://theroot.ninja/
Tigerstown said:
Pretty sure that exploit is dead. I would try sunshine here.
http://theroot.ninja/
Click to expand...
Click to collapse
Sunshine says: incompatible with the device - this is a known issue, we're working on it.
Any ideas?
Tigerstown said:
Pretty sure that exploit is dead. I would try sunshine here.
http://theroot.ninja/
Click to expand...
Click to collapse
Yes, it's dead, and it doesn't look like Sunshine is going to work on this phone... yet. Unless I change something on it, and I'm having trouble figuring out what. So I can either figure out how to change my phone's contents so that Sunshine likes it better OR wait until Sunshine figures this out, which i think it will, eventually.
BUT...hmmm...is FASTBOOT the only way to get the new firmware onto the device? Can it be done by putting it in the right directory and using the recovery to flash it?
(I'm sure there's a way to get this done! I need a better understanding of what the various things that can be flashed are, of what needs to be flashed how, in what order, and why...)
Wombat Pete said:
Yes, it's dead, and it doesn't look like Sunshine is going to work on this phone... yet. Unless I change something on it, and I'm having trouble figuring out what. So I can either figure out how to change my phone's contents so that Sunshine likes it better OR wait until Sunshine figures this out, which i think it will, eventually.
Click to expand...
Click to collapse
If you are on hboot 3.19, sunshine won't work. If that is your case, there is nothing you can do to change that. You can't downgrade hboot with s-on.
Wombat Pete said:
BUT...hmmm...is FASTBOOT the only way to get the new firmware onto the device? Can it be done by putting it in the right directory and using the recovery to flash it?
(I'm sure there's a way to get this done! I need a better understanding of what the various things that can be flashed are, of what needs to be flashed how, in what order, and why...)
Click to expand...
Click to collapse
What you describe is not possible. The partitions needed to flash (radio, hboot, etc.) are protected unless you s-off. The means of flashing (fastboot, etc) doesnt' change that fact. Only a signed, encrypted firmware will work.
So if you have hboot 3.19, you are stuck with the current firmware until AT&T releases the LP update.
---------- Post added at 10:39 AM ---------- Previous post was at 10:20 AM ----------
Wombat Pete said:
... that the software number IS the firmware number on this phone.
Click to expand...
Click to collapse
Yes and no.
Folks here most commonly refer to the firmware number as being the same as the software number since the "firmware" in fact does not have a "number". "Firmware" (and that term is potentially confusing in itself) is simply a collection of critical modules (partitions?) that get updated with an OTA or RUU, but are not on the system (ROM or software) partition. We essentially refer to firmware numbers by the software it deployed with, simply for lack of anything better to refer to them by.
In fact, the main version (that is missing for you) is a bit irrelevant. On stock device, it will tell you what "firmware number" you are on. But if you start flashing ROMs, that isn't the case anymore. Main version will just then just be changed to read whatever software version (ROM) is on the phone, which will not necessarily correspond to the firmware. For instance, you might have KitKat firmware (say "number" 3.42) on the phone. But flash a Lollipop based ROM, say 4.16 software, and your "main version" will read 4.16, even though your firmware has not changed.
Its more reliable to look at hboot and radio numbers, and then decipher what firmware you are currently on. But even that can be a little misleading. As some folks will then (as I've witnesses) get the mistaken impression that all they need to do is update the hboot. Which is just one of the several "critical" components contained in the firmware zip.
The following post come from another thread the OP had opened. No need for 2 threads on the same subject:good:
Wombat Pete said:
Successfully rooted, busybox installed, all good so far. Now I'd like to move to the latest Viper.
The first real problem: I can't figure out my firmware version. When I run “fastboot getvar all”, the info starts with:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: [email protected]
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
...
THAT IS, no main version information.
I'm new at this, though learning. TWO THINGS I don't quite understand: (i) I saw a recommendation for reverting to the previous recovery... that means just going to the Fastboot menu and hitting recovery? And then would I have to go through the reboot process again to get where I am now? AND (ii) The VIPER page describes the process, which involves flashing a stock backup and a stock recovery and THEN TWRP - I'd love to understand what that's for, why it's necessary before flashing the new ROM.
Not sure how to proceed with without knowing the firmware number. I *DID* determine that hboot 1.55 means 3.xx.xxx.x, which seems to be the case here (the "version-bootloader" line).
I *could* go for S-off, but I'm not sure I need to or even want to.
Soooo.... not sure. IN the phone's OS it says:
Android version: 4.4.4
HTC Sense version: 6.0
Software number: 3.42.502.1
HTC SDK API level: 6.25
Kernel bversion: 3.4.0-g931e842
[email protected] #1
SMT PREEMPT
Build number: 3.42.502.1 CL 441323 release-keys
I thought those numbers (3.42.502.1) were supposed to be clear to the firmware number. Which is consistent with "hboot 1.55 means 3.xx.xxx.x". BUT ...Viper's presumption of "1.54" is throwing me off.
Not ready to proceed, I think, until I figure it out. Any and all help will be appreciated!
Click to expand...
Click to collapse