Would anyone that is S-OFF be willing to test a TWRP-flashable radio file? I made these yesterday and tried to flash them but it wouldn't change my radio since I'm not S-OFF (yet). Here are the links:
https://www.androidfilehost.com/?fid=23991606952593250 - Radio from firmware version 1.32.651.17
https://www.androidfilehost.com/?fid=23991606952593904 - Radio from firmware version 1.32.651.30
Please let me know if these work or not. As mentioned before, I already tried to flash but nothing changed, so I'm fairly certain the files will have no ill effect. With that being said, as always, flash at your own risk :good: Please make sure you are S-OFF before reporting back!
Thanks to @OMJ for the update-binary
Thanks to @the.emilio for the original idea/zip file template
How do you know a particular radio actually flashed or not?
mswlogo said:
How do you know a particular radio actually flashed or not?
Click to expand...
Click to collapse
Check under Settings->About->Software Info->More and it will show you baseband version. Someone can correct me if I'm wrong, but I believe the radio for 1.32.651.30 will show 1.11.C1144030 as the baseband version.
So the .17 radio should read something different if the flash was successful.
repl1ca said:
Would anyone that is S-OFF be willing to test a TWRP-flashable radio file? I made these yesterday and tried to flash them but it wouldn't change my radio since I'm not S-OFF (yet). Here are the links:
https://www.androidfilehost.com/?fid=23991606952593250 - Radio from firmware version 1.32.651.17
https://www.androidfilehost.com/?fid=23991606952593904 - Radio from firmware version 1.32.651.30
Please let me know if these work or not. As mentioned before, I already tried to flash but nothing changed, so I'm fairly certain the files will have no ill effect. With that being said, as always, flash at your own risk :good: Please make sure you are S-OFF before reporting back!
Thanks to @OMJ for the update-binary
Thanks to @the.emilio for the original idea/zip file template
Click to expand...
Click to collapse
im s-off and ill try it and let you know.
---------- Post added at 06:16 PM ---------- Previous post was at 06:14 PM ----------
repl1ca said:
Check under Settings->About->Software Info->More and it will show you baseband version. Someone can correct me if I'm wrong, but I believe the radio for 1.32.651.30 will show 1.11.C1144030 as the baseband version.
So the .17 radio should read something different if the flash was successful.
Click to expand...
Click to collapse
the .17 radio should be 1.10.x.x.x fyi
---------- Post added at 06:17 PM ---------- Previous post was at 06:16 PM ----------
repl1ca said:
Would anyone that is S-OFF be willing to test a TWRP-flashable radio file? I made these yesterday and tried to flash them but it wouldn't change my radio since I'm not S-OFF (yet). Here are the links:
https://www.androidfilehost.com/?fid=23991606952593250 - Radio from firmware version 1.32.651.17
https://www.androidfilehost.com/?fid=23991606952593904 - Radio from firmware version 1.32.651.30
Please let me know if these work or not. As mentioned before, I already tried to flash but nothing changed, so I'm fairly certain the files will have no ill effect. With that being said, as always, flash at your own risk :good: Please make sure you are S-OFF before reporting back!
Thanks to @OMJ for the update-binary
Thanks to @the.emilio for the original idea/zip file template
Click to expand...
Click to collapse
didnt work for me, im still on the .30 radio :/ thanks tho
edit - im using twrp beta 4 btw, and i was currently on .30 radio and tried .17 flashable zip. Nothing changed :/
does the .17 radios get better signal? I've been having issues dropping signal with .30
deakelem said:
im s-off and ill try it and let you know.
---------- Post added at 06:16 PM ---------- Previous post was at 06:14 PM ----------
the .17 radio should be 1.10.x.x.x fyi
---------- Post added at 06:17 PM ---------- Previous post was at 06:16 PM ----------
didnt work for me, im still on the .30 radio :/ thanks tho
edit - im using twrp beta 4 btw, and i was currently on .30 radio and tried .17 flashable zip. Nothing changed :/
Click to expand...
Click to collapse
Thanks for testing that for me. I guess it's back to the drawing board for this one....
Crawshayi said:
does the .17 radios get better signal? I've been having issues dropping signal with .30
Click to expand...
Click to collapse
There have been reports that the .17 radio works better than the .30 one. I just haven't had a chance to test it yet
repl1ca said:
There have been reports that the .17 radio works better than the .30 one. I just haven't had a chance to test it yet
Click to expand...
Click to collapse
You really don't have to go back to the drawing board.
Place the radio img and Sprint Android-info.txt file in a zip and flash it while in download mode.
Go to my thread and download the zip I have in Post 1. Take the radio img and replace the img that is in the zip.
reboot to download mode
using cmd where your fastboot files are and type:
1. fastboot devices (Make sure your device is seen)
2. fastboot oem rebootRUU
3. fastboot flash zip filename.zip
4. fastboot reboot
can try the sdcard way (rename zip t0 0PJAIMG.zip) through bootloader but might not flash because it will see it as older firmware)
Crawshayi said:
does the .17 radios get better signal? I've been having issues dropping signal with .30
Click to expand...
Click to collapse
I have better luck with .30 here in houston
personally after messing around with it a lot.. i think .17 handles b41 better and .30 has issues with it.. out here in houston b41 is everywhere so that could be why i have better luck with .17 - try them both, depending on your area it could vary.
cheers
btw i made a fastboot flashable .17 radio only zip and its on omj RUU site. he also has a .30 radio only zip too - must be s-off btw
---------- Post added at 12:17 PM ---------- Previous post was at 12:10 PM ----------
repl1ca said:
Thanks for testing that for me. I guess it's back to the drawing board for this one....
Click to expand...
Click to collapse
hit me up or pm me if you want me to test
deakelem said:
I have better luck with .30 here in houston
personally after messing around with it a lot.. i think .17 handles b41 better and .30 has issues with it.. out here in houston b41 is everywhere so that could be why i have better luck with .17 - try them both, depending on your area it could vary.
cheers
btw i made a fastboot flashable .17 radio only zip and its on omj RUU site. he also has a .30 radio only zip too - must be s-off btw
---------- Post added at 12:17 PM ---------- Previous post was at 12:10 PM ----------
hit me up or pm me if you want me to test
Click to expand...
Click to collapse
Here in NJ/NY b41 is everywhere too, I might as well try the .17 radio and see too.
Since disabling B41 I havent had any LTE or 3G issues. i will enable Band 41 and try, maybe the .17 radio does better handling Band 41
schmeggy929 said:
You really don't have to go back to the drawing board.
Place the radio img and Sprint Android-info.txt file in a zip and flash it while in download mode.
Go to my thread and download the zip I have in Post 1. Take the radio img and replace the img that is in the zip.
reboot to download mode
using cmd where your fastboot files are and type:
1. fastboot devices (Make sure your device is seen)
2. fastboot oem rebootRUU
3. fastboot flash zip filename.zip
4. fastboot reboot
can try the sdcard way (rename zip t0 0PJAIMG.zip) through bootloader but might not flash because it will see it as older firmware)
Click to expand...
Click to collapse
A lot of good info here @schmeggy929, thanks! My reason for trying to create this method was for people that were on the go with no access to a PC. I used this method all of the time on my old M7 without issue but it seems with the M9 it might need a different approach (besides using fastboot or dd or some similar method).
I'm wondering if the update-binary in the zip is what is causing it not to flash properly. I'm not familiar with them at all so that might have something to do with it
repl1ca said:
A lot of good info here @schmeggy929, thanks! My reason for trying to create this method was for people that were on the go with no access to a PC. I used this method all of the time on my old M7 without issue but it seems with the M9 it might need a different approach (besides using fastboot or dd or some similar method).
I'm wondering if the update-binary in the zip is what is causing it not to flash properly. I'm not familiar with them at all so that might have something to do with it
Click to expand...
Click to collapse
I may be wrong but I don't remember to being able to recovery flash any firmware zips through recovery. I had all 3 M7, M8, M9. I can't remember about M7, LOL but M8 all firmware was always flashed through fastboot or sdcard bootloader method. I understand your approach in trying to help with PC people, hopefully you can get it to work through TWRP or until a firmware fix is made.
schmeggy929 said:
I may be wrong but I don't remember to being able to recovery flash any firmware zips through recovery. I had all 3 M7, M8, M9. I can't remember about M7, LOL but M8 all firmware was always flashed through fastboot or sdcard bootloader method. I understand your approach in trying to help with PC people, hopefully you can get it to work through TWRP or until a firmware fix is made.
Click to expand...
Click to collapse
THIS is what I was trying to accomplish with the M9. I believe the radio is the only thing (besides kernel & recovery) from firmware that can be flashed through recovery. Everything else, as you stated, will have to be done from fastboot or bootloader.
repl1ca said:
THIS is what I was trying to accomplish with the M9. I believe the radio is the only thing (besides kernel & recovery) from firmware that can be flashed through recovery. Everything else, as you stated, will have to be done from fastboot or bootloader.
Click to expand...
Click to collapse
I have owned the m7, m8 and now m9 and i cant actually remember ever having to mess with the radios on the m7 and m8.. they always worked fine.. that being said I had the n5 and that had radio issues and it also allowed for flashing radios via recovery. Below is the thread i used for radios when i had the n5, perhaps that person can help you accomplish your goal.
http://forum.xda-developers.com/goo...t/modem-nexus-5-flashable-modems-efs-t2514095
NOTE!! those are n5 radios people... not m9.. do not flash them.. the thread was posted as a reference for the OP.
repl1ca said:
THIS is what I was trying to accomplish with the M9. I believe the radio is the only thing (besides kernel & recovery) from firmware that can be flashed through recovery. Everything else, as you stated, will have to be done from fastboot or bootloader.
Click to expand...
Click to collapse
Sounds good to me.
Im a new member to the site, but definitely not new to XDA
Anyone know where I should ask this question? I use my M9 for tethering, and even though it says it is connected to Band 41, nothing works at all data wise when it is connected to Band 41. Not even a PRL or Profile update. Toggling airplane mode, restarting,
Clearing cache/ dalvik nothing works. And its only on Band 41. One thing I did notice, is even when I have weaker signal sometimes while connected to B41, it works some times.. what seems to make the difference in if I have a working data connection or not on Band 41, is TX power.. if it doesn't acquire TX Power, and hold on to it, it will not have a working Band 41 signal.. do you though the .30 radio would help? Im on .17 right now verified by restarting into Download Mode.. any info/advice/help much appreciated! First post ever on XDA! Thanks guys!
I have the same issue with B41 as you do ever since I got the phone. I just disabled that band and have been using only B25 and B26. Have yet to lose connection yet after doing that. Even tethering works fine on 4G. I tried switching radios, but it didn't do much for me. Other say it helps, so YMMV.
My only suggestion is try it out and see if it's better for you in your area.
HTCforME said:
Anyone know where I should ask this question? I use my M9 for tethering, and even though it says it is connected to Band 41, nothing works at all data wise when it is connected to Band 41. Not even a PRL or Profile update. Toggling airplane mode, restarting,
Clearing cache/ dalvik nothing works. And its only on Band 41. One thing I did notice, is even when I have weaker signal sometimes while connected to B41, it works some times.. what seems to make the difference in if I have a working data connection or not on Band 41, is TX power.. if it doesn't acquire TX Power, and hold on to it, it will not have a working Band 41 signal.. do you though the .30 radio would help? Im on .17 right now verified by restarting into Download Mode.. any info/advice/help much appreciated! First post ever on XDA! Thanks guys!
Click to expand...
Click to collapse
This seems to happen to me while band 41 is weak. I was just at o'hare airport where b41 is full bars everywhere and i didn't have a single problem with it all night. It's a known issue im sure almost all of us in here and the other thread have contact sprint about it. I was told by their tech that their data profile provisioning mechanism needs to be updated cause the s6 and the m9 have problems with it.
deakelem said:
This seems to happen to me while band 41 is weak. I was just at o'hare airport where b41 is full bars everywhere and i didn't have a single problem with it all night. It's a known issue im sure almost all of us in here and the other thread have contact sprint about it. I was told by their tech that their data profile provisioning mechanism needs to be updated cause the s6 and the m9 have problems with it.
Click to expand...
Click to collapse
Yes, same here, when I am home and tethering, I have to disable Band 41 otherwise tetherint will not work, I get it to a good area where band 26 or 25 gets really good signal, but then it just connects to Band 41 and then I have no data at all as stated. So , I am forced to disable it as well. Sucks too because 2 weeks ago it was working wonderfully in the exact same spot. Only thing that has changed is the trees in between the house and tower have leaves on them now. Totally blows
HTCforME said:
Yes, same here, when I am home and tethering, I have to disable Band 41 otherwise tetherint will not work, I get it to a good area where band 26 or 25 gets really good signal, but then it just connects to Band 41 and then I have no data at all as stated. So , I am forced to disable it as well. Sucks too because 2 weeks ago it was working wonderfully in the exact same spot. Only thing that has changed is the trees in between the house and tower have leaves on them now. Totally blows
Click to expand...
Click to collapse
This is actually a bit of good news to me, makes me think it can all be sorted with a new radio update verses an actual physical issue with the radio.
Related
AFTER UPDATING TO KIT KAT MY PHONE LOST SIGNAL
HOW TO FIX
________________
You will need to downgrade your modem firmware
I've have included the MJ4 modem firmware in the download link
simple flash with odin
HOW TO FIX AFTER RESET
------------------------------
If you did like me and reset your phone trying to get signal
before you downgrade the modem make sure your phone is flash
you will not have signal yet so double check your work
then ODIN down to MJ4 modem
HOW TO FIX NO DATA CONNECTION & HFA
--------------------------------
Your phone must be rooted
Use root explorer extract files from note3 carrier.zip
and copy and paste all in carrier folder
reset phone and run profile update
https://www.dropbox.com/s/ef90ey40amadkbs/KIT KAT SIGNAL.rar
(invalid fixed)
WRITNG NEW PRL
------------------------------------
PRL HELPER FROM THE PLAYSTORE
credit to insanecain and Alpineman for his HFA FIX
bremos812 said:
AFTER UPDATING TO KIT KAT MY PHONE LOST SIGNAL
HOW TO FIX
________________
You will need to downgrade your modem firmware
I've have included the MJ4 modem firmware in the download link
simple flash with odin
HOW TO FIX AFTER RESET
------------------------------
If you did like me and reset your phone trying to get signal
before you downgrade the modem make sure your phone is flash
you will not have signal yet so double check your work
then ODIN down to MJ4 modem
HOW TO FIX NO DATA CONNECTION & HFA
--------------------------------
Your phone must be rooted
Use root explorer extract files from note3 carrier.zip
and copy and paste all in carrier folder
reset phone and run profile update
https://www.dropbox.com/s/ef90ey40amadkbs/KIT KAT SIGNAL.rar
credit to insanecain and Alpineman for his HFA FIX
Click to expand...
Click to collapse
the md5 is invalid. Downloaded twice.
sorry
rename it modem.tar.md5 from MJ4modem.tar.md5
bremos812 said:
rename it modem.tar.md5 from MJ4modem.tar.md5
Click to expand...
Click to collapse
I need help. I have a phone with a red x on it and i would love to get this working. The link says that nothing is there.
Shyne888 said:
I need help. I have a phone with a red x on it and i would love to get this working. The link says that nothing is there.
Click to expand...
Click to collapse
I have this file too. I posted it in the development section. if you have an invalid Md5 error, remove the .md5 extention because usually, the file was renamed after and changed the checksum. Not safe to do, because there's no verification, but it works
How can i write 3g data on sprint galaxy note 3 over boost
Yesterday i flash my sprint galaxy note 3 kikat 4.4.2 -mj4 but only have calls and texts with no data, anybody knows how can i write 3g data i already use cdma ws 3.7 and 3.9 doesn't work i know this processes very well since 2009 but kitkat has a lot of problems
galaxys3on3g said:
Yesterday i flash my sprint galaxy note 3 kikat 4.4.2 -mj4 but only have calls and texts with no data, anybody knows how can i write 3g data i already use cdma ws 3.7 and 3.9 doesn't work i know this processes very well since 2009 but kitkat has a lot of problems
Click to expand...
Click to collapse
have you tired using DFS? thats what I use to get 3G working on the S4 and most newer samsung phones.
---------- Post added at 11:56 AM ---------- Previous post was at 11:53 AM ----------
bremos812 said:
AFTER UPDATING TO KIT KAT MY PHONE LOST SIGNAL
HOW TO FIX
________________
You will need to downgrade your modem firmware
I've have included the MJ4 modem firmware in the download link
simple flash with odin
HOW TO FIX AFTER RESET
------------------------------
If you did like me and reset your phone trying to get signal
before you downgrade the modem make sure your phone is flash
you will not have signal yet so double check your work
then ODIN down to MJ4 modem
HOW TO FIX NO DATA CONNECTION & HFA
--------------------------------
Your phone must be rooted
Use root explorer extract files from note3 carrier.zip
and copy and paste all in carrier folder
reset phone and run profile update
https://www.dropbox.com/s/ef90ey40amadkbs/KIT KAT SIGNAL.rar
(invalid fixed)
WRITNG NEW PRL
------------------------------------
PRL HELPER FROM THE PLAYSTORE
credit to insanecain and Alpineman for his HFA FIX
Click to expand...
Click to collapse
dropbox link doesnt work
lost signal after flash to boost
im having something of the same issue ,I tryed in stock and kitkatkiller im on NC5 and every time i flash to boost i loose signal ,i flash back to sprint and its back,i noticed when i flash to sprint my PRL goes to 1 insted of 30030 that i use on my htc one, i have tryed flashing different prls and a old modem dont know witch one it was it wasn't labeled and the one in this poast the link is dead,please help,im upgrading from a htcone o boost that is fulling working and can read everything.
I figured it out.the modem is attached to the esn some how that's all I'm going to say.i had to jump throw 20 hoops to get DFS to work properly also.but I'm fully on boost mobile with my note3 .just some fine tweaks to kitkatkiller and I'll b loving it.
justencase6 said:
I figured it out.the modem is attached to the esn some how that's all I'm going to say.i had to jump throw 20 hoops to get DFS to work properly also.but I'm fully on boost mobile with my note3 .just some fine tweaks to kitkatkiller and I'll b loving it.
Click to expand...
Click to collapse
i have the same thing going on over here what did you do to flash it can you pm me what you did ?
U get 4g lte working to?
Sent from my SM-G900P using Tapatalk
is there anyway to just flash a rom and not update the modem?
justencase6 said:
I figured it out.the modem is attached to the esn some how that's all I'm going to say.i had to jump throw 20 hoops to get DFS to work properly also.but I'm fully on boost mobile with my note3 .just some fine tweaks to kitkatkiller and I'll b loving it.
Click to expand...
Click to collapse
I've had this problem for a while.
After MJ4, no radio seem to work for boost.
The only idea that makes sense to me is the NV items.
I'm no expert, just throwing out an idea.
---------- Post added at 10:20 AM ---------- Previous post was at 10:17 AM ----------
rbebber said:
is there anyway to just flash a rom and not update the modem?
Click to expand...
Click to collapse
a "dirty" flash will do it, but it may come with rom issues.
worse case, just Odin the baseband tar.
what rom did you dirty install? I installed bonsai 1.0 over .5 and it just stayed at the note3 screen. Did you have in upgrade the recovery first, or anything like that? ThaNKS.
rbebber said:
what rom did you dirty install? I installed bonsai 1.0 over .5 and it just stayed at the note3 screen. Did you have in upgrade the recovery first, or anything like that? ThaNKS.
Click to expand...
Click to collapse
Most of the time when your rom wont boot, its a kernel issue.
I dirty flashed Freeza's NH7 rom.
I'm inclined to believe our problems stem from "wifi calling".
It was introduced in NC5 if im not mistaken, & thats when boost Note 3's started to have problems.
I've found an interesting anomaly with the modem issue.
after the MJ baseband, all the newer modems flash APNHLOS to our phones.
not sure just yet what it does, or how its attached to the MEID, but that's my find.
Any ideas?
n900p red x no signal fix
n900p red x no signal fix
got it fixed, even though supersu disabled knox, there was still a security issue. I used titanium backup and searched for knox. then I disabled everything that had to do with knox, instantantly t-mobile pop up.
I have a sprint note 3 with boost mobile sim but when I flash darkwolf pure lite rom everything works but sending text anybody had this issue with Sprint roms or know of a fix
I am rooted, TWRP, on 4.3 build 2.22.xx, and I got s-off on firewater even after the newest AT&T update. I installed ViperOne yesterday and thought my phone had froze on the bootscreen, as it just sits on the HTC "This version is for development use only..." screen, for several minutes before the screen just turns off and at that point everything is fine, I just have to unlock it. I went to the Viper IRC to see if anyone could help, but they didn't seem to know what was wrong, seemed to think maybe I was on the wrong hboot version but I've always been on 3.16. So I thought I would ask here to see if anyone had any ideas. Thanks.
Fallen Advocate said:
I am rooted, TWRP, on 4.3 build 2.22.xx, and I got s-off on firewater even after the newest AT&T update. I installed ViperOne yesterday and thought my phone had froze on the bootscreen, as it just sits on the HTC "This version is for development use only..." screen, for several minutes before the screen just turns off and at that point everything is fine, I just have to unlock it. I went to the Viper IRC to see if anyone could help, but they didn't seem to know what was wrong, seemed to think maybe I was on the wrong hboot version but I've always been on 3.16. So I thought I would ask here to see if anyone had any ideas. Thanks.
Click to expand...
Click to collapse
Same for me, i updated my Viper 1.8.0 to 2.1.0 and now booting takes a long time and like described there is no boot animation
Regards,
Thomas
This also happend to me after flashing the latest build of insertcoin.
I thought it was some sort of bug and flashed back to GPE
Don't know about the missing boot animation, but long boot time and hboot 3.16 means you are on 1.XX based firmware. 2.22 based firmware is needed to fix long boot time. For AT&T in particular, 2.22.1540 firmware is recommended.
The firmware issue has been discussed in quite a few threads to this point. But good instructions here:
http://forum.xda-developers.com/showpost.php?p=54408500&postcount=9592
And also, the firmware is packaged with the following ROM, and with great instruction on how to flash (this is the one I used):
http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
redpoint73 said:
Don't know about the missing boot animation, but long boot time and hboot 3.16 means you are on 1.XX based firmware. 2.22 based firmware is needed to fix long boot time. For AT&T in particular, 2.22.1540 firmware is recommended.
The firmware issue has been discussed in quite a few threads to this point. But good instructions here:
http://forum.xda-developers.com/showpost.php?p=54408500&postcount=9592
And also, the firmware is packaged with the following ROM, and with great instruction on how to flash (this is the one I used):
http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
Click to expand...
Click to collapse
I'm on firmware 2.22.401.5 and I still get the ridiculous boot times. Do I need to update the firmware too?
EchelonBarney said:
I'm on firmware 2.22.401.5 and I still get the ridiculous boot times. Do I need to update the firmware too?
Click to expand...
Click to collapse
if you can see this version in Setting - Info - SoftwareInformation then this is wrong. This is not the real firmware version.
I also did an upgrade from Venom 1.8.0 (4.4.2) to Venom 2.1.0 (4.4.3) and Setting - Info - SoftwareInformation showed me 2.22.401.5.
You have to do a manual firmware update or go back to stock rom and let the stock rom do the firmware update.
That means: Wipe in every case!
That solved my problem.
Regards,
Thomas
funfactor71 said:
if you can see this version in Setting - Info - SoftwareInformation then this is wrong. This is not the real firmware version.
I also did an upgrade from Venom 1.8.0 (4.4.2) to Venom 2.1.0 (4.4.3) and Setting - Info - SoftwareInformation showed me 2.22.401.5.
You have to do a manual firmware update or go back to stock rom and let the stock rom do the firmware update.
That means: Wipe in every case!
Click to expand...
Click to collapse
Truth. There is some confusion about "firmware" as the term is a bit vague. In fact "firmware" can mean any software you flash to solid-state type memory; and "firmware" has often been used interchangeably with the ROM.
However, this is not what is being referred to when "updating the firmware package" (or similar recommendation) is discussed in terms of long boot times, broken WiFi, etc. when using a 2.22 based ROM. In fact, these are modules that reside on separate partitions from the ROM, and not touched when a ROM is flashed. These include hboot, radio, media, WiFi, and other modules. And its these software modules that will not play well with a 2.22 based ROM, if the firmware is not up to date.
Looking at software or build number is Settings does not tell you if your firmware is up to date. It simply tells you the software number for the ROM. There is in fact no actual "firmware number" per se; so folks will often refer to the software number that it deployed with (2.22.401, etc.) for lack of a better description/terminology. However, to confirm if the firmware was properly installed, its actually much more useful to look at hboot number and radio baseband. If you are on hboot 3.16, you do not have the updated firmware. The updated firmware will have installed hboot 3.18. The radio will also have been updated, but I'm not personally familiar with all the possible radio numbers associated with the various firmware package (although I suspect the newer firmware packages contain 1.19xxx basebands).
---------- Post added at 10:27 AM ---------- Previous post was at 10:22 AM ----------
EchelonBarney said:
I'm on firmware 2.22.401.5 and I still get the ridiculous boot times. Do I need to update the firmware too?
Click to expand...
Click to collapse
Make sure you firmware is actually updated, per my long-winded comments above.
Also, be aware that 2.22.401 firmware is not recommended for US users, but rather then 2.22.1540:
http://forum.xda-developers.com/showpost.php?p=54408500&postcount=9592
Not sure if this can cause long boot times, but US users have experienced cell connectivity issues using 2.22.401
redpoint73 said:
Don't know about the missing boot animation, but long boot time and hboot 3.16 means you are on 1.XX based firmware. 2.22 based firmware is needed to fix long boot time.
The firmware issue has been discussed in quite a few threads to this point. But good instructions here:
http://forum.xda-developers.com/show...postcount=9592
Click to expand...
Click to collapse
My duhhh. No boot animation is mentioned right in the post I linked:
The issues you will see without the new firmware include long boot times with no boot animations and some users on 9.1 reported wifi and bluetooth issues.
I knew long boot times was an issue, but no boot animation is definitely caused by outdated firmware, also.
redpoint73 said:
...
Not sure if this can cause long boot times, but US users have experienced cell connectivity issues using 2.22.401
Click to expand...
Click to collapse
I am on 2.22.401.4 and I do experience odd 4G issues (phone says it is connected but I get no data.) Switching airplane mode off and on usually fixes the issue. Are you on 2.22.1540? If so, have you experienced any dropouts? I will drop down to that firmware if it could hold a solid connection for my M8. Thanks.
revoltech said:
I am on 2.22.401.4 and I do experience odd 4G issues (phone says it is connected but I get no data.) Switching airplane mode off and on usually fixes the issue. Are you on 2.22.1540? If so, have you experienced any dropouts? I will drop down to that firmware if it could hold a solid connection for my M8. Thanks.
Click to expand...
Click to collapse
I'm on 2.22.1540 and reception is perfect.
Connection issues is a known problem with the "international" firmware 2.22.401, so I highly recommend flashing 2.22.1540.
Some AT&T folks don't even get service on 2.22.401: http://forum.xda-developers.com/att-htc-one-m8/help/service-upgrade-to-firmware-firmware2-t2834076
redpoint73 said:
I'm on 2.22.1540 and reception is perfect.
Connection issues is a known problem with the "international" firmware 2.22.401, so I highly recommend flashing 2.22.1540.
Some AT&T folks don't even get service on 2.22.401: http://forum.xda-developers.com/att-htc-one-m8/help/service-upgrade-to-firmware-firmware2-t2834076
Click to expand...
Click to collapse
Hello again, sorry to threadcrap but I just flash the 2.22.1540 firmware as recommended and all is well. However, I am curious on why the radio version did not downgrade. From the bootloader, the radio list: 1.19.21331147A1.09G which is the same radio version on 2.22.401.4 firmware. Can you please do me a favor and verify your radio version? I have a suspicion that both firmwares carry the same radio version. Thanks!
revoltech said:
Hello again, sorry to threadcrap but I just flash the 2.22.1540 firmware as recommended and all is well. However, I am curious on why the radio version did not downgrade.
Click to expand...
Click to collapse
You may have to flash the firmware twice for everything to install. This is a common issue.
redpoint73 said:
You may have to flash the firmware twice for everything to install. This is a common issue.
Click to expand...
Click to collapse
I installed the 2.22.1540.3 firmware again but it still reports the same radio version, 1.19.21331147A1.09G, and I do see in the CLI output that an radio.img is being flashed onto the device. I downloaded the firmware from mike1986. website. So, does this mean that the 2.22.401.4 firmware and the 2.22.21540.3 share the same radio.img?
This is the stock developer build radio string...compare all number's/letter's... It is possible that radio is unchanged....
revoltech said:
I installed the 2.22.1540.3 firmware again but it still reports the same radio version, 1.19.21331147A1.09G, and I do see in the CLI output that an radio.img is being flashed onto the device. I downloaded the firmware from mike1986. website. So, does this mean that the 2.22.401.4 firmware and the 2.22.21540.3 share the same radio.img?
Click to expand...
Click to collapse
Wonders_Never_Cease said:
This is the stock developer build radio string...compare all number's/letter's... It is possible that radio is unchanged....
Click to expand...
Click to collapse
Thank you for the screenshot. My radio number is identical to the one in the screenshot. There is a possibility that the version number has a slight difference on the 2.22.401.4 which I previously had installed. I appreciate the help :good:
After trying a lot of getting root of my phone Htc desire U. I have found a simple method of rooting 100%.
Please remember S-OFF is required for complete rooting in HTC. or else you will end up in fu*king with your own time.
* I am not responsible for any brick of your phone please!!:angel:
* requires CWM 6.0.3.3 (google for it) and Unlocked bootloader in your phone.
Step 1: Download boot.img attached and flash with fastboot from PC.
Fastboot flash boot boot.img
Step 2: Run rumrunner_proto_0.7.1(google for it) for HTC desire V( works on Desire U also) for S-OFF. (its a bit time consuming.)
Step 3: Flash superuser_3.2rc2_busybox.sip(google for it).
Step 4: reboot
your are done.
The boot.img file also will work for wifi/bluetooth problems on both models as i have seen.
warning : Using s-off method you will get vibrations on boot !
img file
I need img file for htc desire u dual sim. please help me. thank you in advance
Hi,
First of all, I apologize for bumping such an old thread, however I think it is important to do so; I'll explain why.
How to properly get S-OFF on your HTC Desire U (dual sim) (T327w):
Unlock the bootloader of your HTC Desire U (dual sim).
Flash the recovery (CWM v5.8.3.1) to your phone (download).
PERFORM A NANDROID BACKUP OF YOUR PHONE USING THE ABOVE INSTALLED RECOVERY.
This is extremely important, because if something goes wrong later (which it will, YES, confirmed, your phone WILL BECOME UNUSABLE after this method, IF YOU DO NOT TAKE A FULL NANDROID BACKUP BEFOREHAND!
(Read more about why this happens at the end of this post.)
Click to expand...
Click to collapse
Install SuperSU to get root access.
Get ADB and Fastboot for Ubuntu/Linux using:
sudo apt-get install android-tools-adb android-tools-fastboot
Click to expand...
Click to collapse
Then, download the "boot.img" attached to the first post of this thread and flash it to your phone, using:
sudo fastboot flash boot boot.img
Click to expand...
Click to collapse
I used the RumRunner (rumrunner_proto_0.7.1), linux version: (http://rumrunner.us/rumrunner_downloads/rumrunner_proto_0.7.1.tgz), using Ubuntu 16.04 Desktop x86 (32 bit), which is properly installed and NOT a live CD to do this. Don't bother to do this in Windows, its much less of a hassle the way I did it, no need to bother with installing HTC drivers and stuff.
Download the above linked RumRunner (.tgz) to (./Downloads) and extract it. Follow the instructions at http://rumrunner.us/instructions/ religiously!
If you did everything properly and in the EXACT way described here, you will get S-OFF on your HTC Desire U (dual sim), surely. I can confirm this specific method to be working, personally.
Problem:
However, it's not over yet. Once you get S-OFF and boot back into your phone, you will find that Wifi, Bluetooth and even the network (both sims) WILL STOP WORKING. Both of your sim slots will not detect any SIM in either slot and if you try to switch the "Aeroplane Mode" ON, it will become bugged and forever stuck in that state.
This can be fixed in the step mentioned below, so you will be FINE if you had taken a Nandroid backup before doing this, as I had warned. If you are reading this after messing up and you have no backup, don't worry, I'll try to help you people as well.
Note: Using this procedure, as mentioned several times before, you will have a bug PERMANENTLY, which cannot be fixed, wherein, whenever you start the device thereafter, the device will vibrate 7 (seven) times. There are no other repercussions or ill-effects, apart from this.
The Solution:
Either you can try to flash this "boot.img" (download), which would overwrite the one we had flashed earlier. Try to boot your phone and see if the issue is fixed. You should check whether the Wifi, Bluetooth and both the Sim slots are working properly. If not, you should go to the recovery and do a "wipe/full reset" and reboot the phone normally, afterwards. Then, check again.
If that doesn't seem to work for some reason, simply restore the Nandroid backup that I asked you to create, before going through with this. This will SURELY solve the problem for you.
Congratulations, now you have your HTC Desire U (dual sim), S-OFF, rooted and working properly, apart from that minor 7-vibration bug on startup. :good:
Somebody guide me to flash stock rom in HTC desire U dual sim T327w
I have downloaded the RUU file and installed all the drivers including htc sync manager. When I open the RUU wizard it opens and shows loading then I accept the agreement the RUU wizard window closes and nothing happens thereafter. Please guide me I have problem with network on this device.
It is S-on BL locked Unrooted
---------- Post added at 09:00 AM ---------- Previous post was at 08:50 AM ----------
Anyone know about custom rom available for htc desire u
Edesh Kumar said:
Somebody guide me to flash stock rom in HTC desire U dual sim T327w
I have downloaded the RUU file and installed all the drivers including htc sync manager. When I open the RUU wizard it opens and shows loading then I accept the agreement the RUU wizard window closes and nothing happens thereafter. Please guide me I have problem with network on this device.
It is S-on BL locked Unrooted
Click to expand...
Click to collapse
First of all, as you said, you're not rooted, with S-On and on a locked bootloader, so that's pretty much an unaltered state of your phone, why would you even want to "flash stock ROM" in the first place? Please clarify and explain in greater detail to avoid any confusing situations which could lead up to undesirable situations at a later stage.
ParalyticSJ said:
First of all, as you said, you're not rooted, with S-On and on a locked bootloader, so that's pretty much an unaltered state of your phone, why would you even want to "flash stock ROM" in the first place? Please clarify and explain in greater detail to avoid any confusing situations which could lead up to undesirable situations at a later stage.
Click to expand...
Click to collapse
At my home,I got very low singals on this device whereas other smartphones shows no problem at same network.and as you said I am not rooted neither S-off nor BL unlocked .I wanted to know about custom rom because I will look to unlock my device if there is an custom rom available for it.I have played with these things in my xperia M and I didnot had much trouble.I am new for this device.
---------- Post added at 09:31 AM ---------- Previous post was at 09:24 AM ----------
Edesh Kumar said:
At my home,I got very low singals on this device whereas other smartphones shows no problem at same network.and as you said I am not rooted neither S-off nor BL unlocked .I wanted to know about custom rom because I will look to unlock my device if there is an custom rom available for it.I have played with these things in my xperia M and I didnot had much trouble.I am new for this device.
Click to expand...
Click to collapse
I want flash stock rom because I think my device software has different frequency.I think so because I have bought it as second hand Phone.and also it lags so much on 4.0.3.
If you have such problems so let me know if these are hardware problem.
Thanks for your precious time
Edesh Kumar said:
At my home,I got very low singals on this device whereas other smartphones shows no problem at same network.and as you said I am not rooted neither S-off nor BL unlocked .I wanted to know about custom rom because I will look to unlock my device if there is an custom rom available for it.I have played with these things in my xperia M and I didnot had much trouble.I am new for this device.
---------- Post added at 09:31 AM ---------- Previous post was at 09:24 AM ----------
I want flash stock rom because I think my device software has different frequency.I think so because I have bought it as second hand Phone.and also it lags so much on 4.0.3.
If you have such problems so let me know if these are hardware problem.
Thanks for your precious time
Click to expand...
Click to collapse
Unfortunately, no, there are NO (yes, ZERO) custom roms for this phone. Since this was a low end device and also because its a dual sim phone (?), there was a sheer lack of development for this phone. The maximum I can help you with is to attain ROOT + unlocked bootloader + S-OFF for proper, full root access. That's it. Apart from that, there's not much you can do with this phone.
ParalyticSJ said:
Unfortunately, no, there are NO (yes, ZERO) custom roms for this phone. Since this was a low end device and also because its a dual sim phone (?), there was a sheer lack of development for this phone. The maximum I can help you with is to attain ROOT + unlocked bootloader + S-OFF for proper, full root access. That's it. Apart from that, there's not much you can do with this phone.
Click to expand...
Click to collapse
Thanks so much but can you guide me to flash stock rom.this would be enough and if you have this device please let me know that you have any lagging and network problems and also the battery drains a bit faster.
Forgive me if I am asking non-sense
Anyway thanks again for replying.I respect your precious time
---------- Post added at 10:36 AM ---------- Previous post was at 09:50 AM ----------
ParalyticSJ said:
Unfortunately, no, there are NO (yes, ZERO) custom roms for this phone. Since this was a low end device and also because its a dual sim phone (?), there was a sheer lack of development for this phone. The maximum I can help you with is to attain ROOT + unlocked bootloader + S-OFF for proper, full root access. That's it. Apart from that, there's not much you can do with this phone.
Click to expand...
Click to collapse
Please guide me brother.I beg you
ParalyticSJ said:
Unfortunately, no, there are NO (yes, ZERO) custom roms for this phone. Since this was a low end device and also because its a dual sim phone (?), there was a sheer lack of development for this phone. The maximum I can help you with is to attain ROOT + unlocked bootloader + S-OFF for proper, full root access. That's it. Apart from that, there's not much you can do with this phone.
Click to expand...
Click to collapse
Please man tell me if. You know how to flash stock rom.I apologize for replying again and again but I cant find any flashing thread, my RUU wizard closes suddenly.I am very sorry but i don't want to waste your time.
Its about my life.I am unable to take calls.
I would be very thankful to you
Edesh Kumar said:
Thanks so much but can you guide me to flash stock rom.this would be enough and if you have this device please let me know that you have any lagging and network problems and also the battery drains a bit faster.
Forgive me if I am asking non-sense
Anyway thanks again for replying.I respect your precious time
---------- Post added at 10:36 AM ---------- Previous post was at 09:50 AM ----------
Please guide me brother.I beg you
Click to expand...
Click to collapse
Allow me to explain again ... Since you have a locked bootloader + non-rooted + S-On device, you cannot modify anything related to your phone (in its current state). So keeping that point in mind, you are already on stock (since nothing CAN be modified in the state you are, for this phone, and thus nothing has been changed). So that means that you are already on the stock ROM and you don't need to do anything else such as "flashing stock ROM", since you ALREADY have the stock ROM on your phone.
As far as your query about signal issues is concerned, well no, I don't face that issue with my device and neither is there any issue with the battery.
Below, I'm sharing some details of my device, maybe you could compare those with yours and see if that helps:
Phone Name: HTC Desire U dual sim
Android Version: 4.0.3
HTC Sense Version: 4.0
Software Number: 1.07.707.8
HTC SDK API level: 4.20
HTC Extension Version: HTCExtension_403_1_GA_8
Kernel Version: 3.0.16-gf929c72
[email protected]#1
Baseband Version: 1.18.34D.01_20.40.30.42U
Build Number: 1.07.707.8 CL188037 release-keys
Browser Version: WebKit/534.30
Network:
Signal Strength: -73 dBm 20 asu
Mobile Network Type: EDGE:2
Click to expand...
Click to collapse
ParalyticSJ said:
Allow me to explain again ... Since you have a locked bootloader + non-rooted + S-On device, you cannot modify anything related to your phone (in its current state). So keeping that point in mind, you are already on stock (since nothing CAN be modified in the state you are, for this phone, and thus nothing has been changed). So that means that you are already on the stock ROM and you don't need to do anything else such as "flashing stock ROM", since you ALREADY have the stock ROM on your phone.
As far as your query about signal issues is concerned, well no, I don't face that issue with my device and neither is there any issue with the battery.
Below, I'm sharing some details of my device, maybe you could compare those with yours and see if that helps:
Click to expand...
Click to collapse
Thanks for reply the RUU I have downloaded is software version 5.18.502.15
Now I have the software version that you have.
I am confused because settings of phone doesn't show updates but I found the update with higher software version.
One more question that the frequency of US software will work in india also or not.
Forgive my English
Edesh Kumar said:
Thanks for reply the RUU I have downloaded is software version 5.18.502.15
Now I have the software version that you have.
I am confused because settings of phone doesn't show updates but I found the update with higher software version.
One more question that the frequency of US software will work in india also or not.
Forgive my English
Click to expand...
Click to collapse
Absolutely not. The software version you indicated that you wish to update to, is mentioned as being related to:
HTC One X 5.18.502.15
which is definitely not going to be compatible with the HTC Desire U, a fact which is made more evident once both the phones are compared to each other. Even if you assume that "it would fine and compatible", I can tell you one striking difference which guarantees that it will not. For example, if you notice, The HTC One X has just one sim slot, while the HTC Desire U has two.
This "RUU" that you have downloaded is most certainly not compatible with the phone we're discussing in here and I recommend AGAINST attempting to flash that software update. In any case, from what I've heard, you won't be able to flash an incompatible RUU in the first place, since it first checks whether you're applying it to a compatible handset or not. I guess that explains why the "RUU quits on you abruptly" as you described.
Hope that clears all of your doubts, conclusively.
ParalyticSJ said:
Absolutely not. The software version you indicated that you wish to update to, is mentioned as being related to:
HTC One X5.18.502.15
which is definitely not going to be compatible with the HTC Desire U, a fact which is made more evident once both the phones are compared to each other. Even if you assume that "it would fine and compatible", I can tell you one striking difference which guarantees that it will not. For example, if you notice, The HTC One X has just one sim slot, while the HTC Desire U has two.
This "RUU" that you have downloaded is most certainly not compatible with the phone we're discussing in here and I recommend AGAINST attempting to flash that software update. In any case, from what I've heard, you won't be able to flash an incompatible RUU in the first place, since it first checks whether you're applying it to a compatible handset or not. I guess that explains why the "RUU quits on you abruptly" as you described.
Hope that clears all of your doubts, conclusively.
Click to expand...
Click to collapse
Ohh!that's the thing.
The Internet websites fooled me,I downloaded the RUU of desire U according to that website.I was thinking that the RUU of desire u is named something like 'primods mini'.
I know that flashing incompatible rom can even hardbrick the device.Thanks for help.
but RUU should open because I didnot connected the device.
Suppose if I had htc oneX and it quits at that time also even I didn't connected the phone to the pc.
---------- Post added at 03:30 AM ---------- Previous post was at 03:01 AM ----------
ParalyticSJ said:
Allow me to explain again ... Since you have a locked bootloader + non-rooted + S-On device, you cannot modify anything related to your phone (in its current state). So keeping that point in mind, you are already on stock (since nothing CAN be modified in the state you are, for this phone, and thus nothing has been changed). So that means that you are already on the stock ROM and you don't need to do anything else such as "flashing stock ROM", since you ALREADY have the stock ROM on your phone.
As far as your query about signal issues is concerned, well no, I don't face that issue with my device and neither is there any issue with the battery.
Below, I'm sharing some details of my device, maybe you could compare those with yours and see if that helps:
Click to expand...
Click to collapse
As you mentioned some of your device details
The software number matched
The baseband version matched
Kernel version matched
Everything you mentioned matched.
Where do you live brother?
I am asking this because I live in India and if you live in other country.My baseband version should be different and may be software version should also be different.
I had cross flashed the stock rom of xperia M C1905 (other countries)to Xperia M C1904(Indian) and i had the issues of uncommon sound during calls.
And tell me if because of different baseband, something can be done or I have to leave this device.
Thanks for being like a brother.
Edesh Kumar said:
Ohh!that's the thing.
The Internet websites fooled me,I downloaded the RUU of desire U according to that website.I was thinking that the RUU of desire u is named something like 'primods mini'.
I know that flashing incompatible rom can even hardbrick the device.Thanks for help.
but RUU should open because I didnot connected the device.
Suppose if I had htc oneX and it quits at that time also even I didn't connected the phone to the pc.
---------- Post added at 03:30 AM ---------- Previous post was at 03:01 AM ----------
As you mentioned some of your device details
The software number matched
The baseband version matched
Kernel version matched
Everything you mentioned matched.
Where do you live brother?
I am asking this because I live in India and if you live in other country.My baseband version should be different and may be software version should also be different.
I had cross flashed the stock rom of xperia M C1905 (other countries)to Xperia M C1904(Indian) and i had the issues of uncommon sound during calls.
And tell me if because of different baseband, something can be done or I have to leave this device.
Thanks for being like a brother.
Click to expand...
Click to collapse
Is not the Different baseband version make changes? Your device's version and my device's version matches.I think you are from other country than mine(India).
Please clarify my doubts
Edesh Kumar said:
Is not the Different baseband version make changes? Your device's version and my device's version matches.I think you are from other country than mine(India).
Please clarify my doubts
Click to expand...
Click to collapse
Please reply!!!!!!!!!!!!
---------- Post added at 03:21 PM ---------- Previous post was at 03:20 PM ----------
ParalyticSJ said:
Absolutely not. The software version you indicated that you wish to update to, is mentioned as being related to:
HTC One X5.18.502.15
which is definitely not going to be compatible with the HTC Desire U, a fact which is made more evident once both the phones are compared to each other. Even if you assume that "it would fine and compatible", I can tell you one striking difference which guarantees that it will not. For example, if you notice, The HTC One X has just one sim slot, while the HTC Desire U has two.
This "RUU" that you have downloaded is most certainly not compatible with the phone we're discussing in here and I recommend AGAINST attempting to flash that software update. In any case, from what I've heard, you won't be able to flash an incompatible RUU in the first place, since it first checks whether you're applying it to a compatible handset or not. I guess that explains why the "RUU quits on you abruptly" as you described.
Hope that clears all of your doubts, conclusively.
Click to expand...
Click to collapse
Please reply!!!!!!!!
PLEASE
ParalyticSJ said:
Hi,
First of all, I apologize for bumping such an old thread, however I think it is important to do so; I'll explain why.
How to properly get S-OFF on your HTC Desire U (dual sim) (T327w):
Unlock the bootloader of your HTC Desire U (dual sim).
Flash the recovery (CWM v5.8.3.1) to your phone (download).
Install SuperSU to get root access.
Get ADB and Fastboot for Ubuntu/Linux using:
Then, download the "boot.img" attached to the first post of this thread and flash it to your phone, using:
I used the RumRunner (rumrunner_proto_0.7.1), linux version: (http://rumrunner.us/rumrunner_downloads/rumrunner_proto_0.7.1.tgz), using Ubuntu 16.04 Desktop x86 (32 bit), which is properly installed and NOT a live CD to do this. Don't bother to do this in Windows, its much less of a hassle the way I did it, no need to bother with installing HTC drivers and stuff.
Download the above linked RumRunner (.tgz) to (./Downloads) and extract it. Follow the instructions at http://rumrunner.us/instructions/ religiously!
If you did everything properly and in the EXACT way described here, you will get S-OFF on your HTC Desire U (dual sim), surely. I can confirm this specific method to be working, personally.
Problem:
However, it's not over yet. Once you get S-OFF and boot back into your phone, you will find that Wifi, Bluetooth and even the network (both sims) WILL STOP WORKING. Both of your sim slots will not detect any SIM in either slot and if you try to switch the "Aeroplane Mode" ON, it will become bugged and forever stuck in that state.
This can be fixed in the step mentioned below, so you will be FINE if you had taken a Nandroid backup before doing this, as I had warned. If you are reading this after messing up and you have no backup, don't worry, I'll try to help you people as well.
Note: Using this procedure, as mentioned several times before, you will have a bug PERMANENTLY, which cannot be fixed, wherein, whenever you start the device thereafter, the device will vibrate 7 (seven) times. There are no other repercussions or ill-effects, apart from this.
The Solution:
Either you can try to flash this "boot.img" (download), which would overwrite the one we had flashed earlier. Try to boot your phone and see if the issue is fixed. You should check whether the Wifi, Bluetooth and both the Sim slots are working properly. If not, you should go to the recovery and do a "wipe/full reset" and reboot the phone normally, afterwards. Then, check again.
If that doesn't seem to work for some reason, simply restore the Nandroid backup that I asked you to create, before going through with this. This will SURELY solve the problem for you.
Congratulations, now you have your HTC Desire U (dual sim), S-OFF, rooted and working properly, apart from that minor 7-vibration bug on startup. :good:
Click to expand...
Click to collapse
Dear sir , I am Indian HTC desire u , user ! I have unlocked bootloader , have flashed supersu 2.77 , I went through your method for s off but it due don't succed ! .
Error at last
" sanitating ,sunky rumm
[TTTT************************]
Press enter to exit
I did this on windows using !
Rumrunner o.7.1 for HTC desire x ! From official website
There is no rumrunner for desire u or v over their offical site !
I don't have Linux
Please help me to gain S-OFF
Need of s-off is I want to delete company apps and make the phone light !
sp462308 said:
Dear sir , I am Indian HTC desire u , user ! I have unlocked bootloader , have flashed supersu 2.77 , I went through your method for s off but it due don't succed ! .
Error at last
" sanitating ,sunky rumm
[TTTT************************]
Press enter to exit
I did this on windows using !
Rumrunner o.7.1 for HTC desire x ! From official website
There is no rumrunner for desire u or v over their offical site !
I don't have Linux
Please help me to gain S-OFF
Need of s-off is I want to delete company apps and make the phone light !
Click to expand...
Click to collapse
That will not work. You NEED to do this via a linux distribution, preferably Ubuntu, and in the way I did. You are not going to be able to do this via Windows.
ParalyticSJ said:
That will not work. You NEED to do this via a linux distribution, preferably Ubuntu, and in the way I did. You are not going to be able to do this via Windows.
Click to expand...
Click to collapse
Sir I should install Linux on my PC ! Then doing this process will surely help me ??? Have u tried it personally ! Do u still own this device !
sp462308 said:
Sir I should install Linux on my PC ! Then doing this process will surely help me ??? Have u tried it personally ! Do u still own this device !
Click to expand...
Click to collapse
Yes, you need linux installed for this.
And obviously, as should be evident from my earlier posts, I have personally done this successfully. Just follow my earlier posts in a strict manner, do not do anything not mentioned and do exactly what is mentioned and you should be able to do it successfully.
Followed instructions to the T I'm pretty sure, and since then all incoming calls go straight to voicemail.. Now I want to revert back to stock, do the sunshine s off and then try revolution hd again to see if the problem goes away.
homthtrnut said:
Followed instructions to the T I'm pretty sure, and since then all incoming calls go straight to voicemail.. Now I want to revert back to stock, do the sunshine s off and then try revolution hd again to see if the problem goes away.
Click to expand...
Click to collapse
This issue has been reported by a couple folks now (also on Euro based LP ROMs); although I don't think the exact cause and fix has been determined definitely yet. http://forum.xda-developers.com/att-htc-one-m8/help/m8-skydragon-incoming-calls-t3042091
First off, if you have the AT&T version of the M8 and are s-on, you aren't on the right firmware (hboot, radio, and several other critical modules that don't flash with the ROM) for the an recent (Lollipop) version of ARHD. For now, s-off is needed to update to LP firmware; until AT&T releases LP officially by OTA, RUU.
Although I'm not sure its just a firmware issue (so that may or may not fix the issue). "International" ROMs often don't play well with AT&T's network; since the devs (often Euro) don't understand the nuances of AT&T's network. Not to knock those fine devs, but they can't know what they don't know (or can't test, since they aren't on that particular network). Plus, AT&T is probably mostly to blame, as they seem to do some things differently from just about every other carrier in the world.
The quick fix would be return to a stock AT&T ROM, as you have already figured out. You don't need s-off to do that. Restore your nandroid (that you should always make before messing with flashing new ROMs). Or find a stock AT&T ROM corresponding to your firmware, and flash in recovery. Another option is to relock the bootloader and RUU to stock.
Just need to dig in and get it done!
redpoint73 said:
This issue has been reported by a couple folks now (also on Euro based LP ROMs); although I don't think the exact cause and fix has been determined definitely yet. http://forum.xda-developers.com/att-htc-one-m8/help/m8-skydragon-incoming-calls-t3042091
First off, if you have the AT&T version of the M8 and are s-on, you aren't on the right firmware (hboot, radio, and several other critical modules that don't flash with the ROM) for the an recent (Lollipop) version of ARHD. For now, s-off is needed to update to LP firmware; until AT&T releases LP officially by OTA, RUU.
Although I'm not sure its just a firmware issue (so that may or may not fix the issue). "International" ROMs often don't play well with AT&T's network; since the devs (often Euro) don't understand the nuances of AT&T's network. Not to knock those fine devs, but they can't know what they don't know (or can't test, since they aren't on that particular network). Plus, AT&T is probably mostly to blame, as they seem to do some things differently from just about every other carrier in the world.
The quick fix would be return to a stock AT&T ROM, as you have already figured out. You don't need s-off to do that. Restore your nandroid (that you should always make before messing with flashing new ROMs). Or find a stock AT&T ROM corresponding to your firmware, and flash in recovery. Another option is to relock the bootloader and RUU to stock.
Click to expand...
Click to collapse
I can do anything that is new to me with good instructions. I WAS able to unlock, root, and flash a ROM with good success following the steps. What I would like to do now is put it back the way it was, then s off using sunshine, and then go ahead and flash the Revo HD ROM again and whatever else I need to do, maybe the firmware too idk. Before I started anything , I backed it up using HTC SYNC on my laptop. Is that useful in returning it to stock? Or is that just for media and texts and such? Maybe what I should do is check the forum where the Revo users are and see what they say. Sorry if it sounds like Im thinking out loud but Im a noob at forums and flashing. And Im getting burnt out on having a phone that doesnt receive calls properly. Not to mention burnt out from working all day and coming home to try and solve this mystery. OK I wont mention it. Thanks to those who have attempted to give me input here to try to figure this thing out.
Just a lil something to think about...,youll not have dialer, vvm messages,contacts integrated,signal will probably be not as good,and no VoLTE when using euro ROM's. Stand alone vvm app may or may not install from playstore if you use it. My suggestion,flash back to stock,wait alil while and get an official Lollipop release from ATT.
Flash a twrp backup of latest 4.4.4
Flash stock recovery from latest 4.4.4
Steps above will put you back to as close to stock as possible,without relocking bootloader and reflashing the exe ruu file.
homthtrnut said:
What I would like to do now is put it back the way it was, then s off using sunshine, and then go ahead and flash the Revo HD ROM again and whatever else I need to do, maybe the firmware too idk.
Click to expand...
Click to collapse
If you don't flash the firmware, I don't think the above will help you in any way. You'll just be back to where you are now, just with s-off. Which is just a permission/security change; and won't change the functionality of the phone or address the issue with calls.
Either you need to change firmware, or ROM, or both, in order to fix the problem.
Flashed firmware successfully.........darn .zip.zip tricksters!!!! Anyway!
redpoint73 said:
If you don't flash the firmware, I don't think the above will help you in any way. You'll just be back to where you are now, just with s-off. Which is just a permission/security change; and won't change the functionality of the phone or address the issue with calls.
Either you need to change firmware, or ROM, or both, in order to fix the problem.
Click to expand...
Click to collapse
After several attempts getting cannot load error I figured out I needed to back off the .zip from the renamed folder (its already a damn .zip)! duh....so finally got that done. Wondering what to do about relock now. Guess I will have to google it like everything else. Usually throws me right back in here when I do. I found a guy with the exact same problem I was having and it was just cuz he renamed it firmware.zip. Even the dude on youtube tells you to do it! Us noobs are this close to pulling our eyes out from that one!!!! But after trying this and trying that we finally flashted our firmwares on our little precious. Now to see if I can receive calls again. Whats the procedure for unlocking a relocked phone now? Can it now be done by a cmd prompt? Thanks people!
homthtrnut said:
After several attempts getting cannot load error I figured out I needed to back off the .zip from the renamed folder (its already a damn .zip)! duh....so finally got that done.
I found a guy with the exact same problem I was having and it was just cuz he renamed it firmware.zip. Even the dude on youtube tells you to do it! Us noobs are this close to pulling our eyes out from that one!!!! But after trying this and trying that we finally flashted our firmwares on our little precious.
Click to expand...
Click to collapse
Do yourself a huge favor, and turn off the Windows option (if you haven't already) to hide known file extensions. The option is usually enabled by default. I suspect its mainly meant to prevent non-tech savvy PC users from deleting or modifying file extensions and rendering files unusable (or at least not associated with a program to open it).
For most folks who are going to be messing with things like modding phones, and even halfway familiar with the file extensions, the option to hide them is counter-productive and confusing.
The recommendation to rename the file to firmware.zip is valid. This is done since the files are often named things like 4.16.401 to differentiate the firmwares from each other (such as in firmware collections). Technically, you didn't rename the file to firmware.zip (although Windows make it look like you did), you actually named it firmware.zip.zip, even though Windows didn't display it that way.
homthtrnut said:
Wondering what to do about relock now. Guess I will have to google it like everything else. Usually throws me right back in here when I do.
Whats the procedure for unlocking a relocked phone now? Can it now be done by a cmd prompt? Thanks people!
Click to expand...
Click to collapse
To unlock the bootloader again, simply go through the HTCDev.com process to get another unlock bin token, then run the fastboot command with that token again (like you did the first time).
On past devices, it was sometimes possible to reuse the original token (run the fastboot command with it). But an XDA user commented that doesn't work on this device (and that you need to get a new token). But you can always try it, if you want.
Flashed firmware and now stuck in HBOOT! I REALLY NEED HELP NOW
redpoint73 said:
This issue has been reported by a couple folks now (also on Euro based LP ROMs); although I don't think the exact cause and fix has been determined definitely yet. http://forum.xda-developers.com/att-htc-one-m8/help/m8-skydragon-incoming-calls-t3042091
First off, if you have the AT&T version of the M8 and are s-on, you aren't on the right firmware (hboot, radio, and several other critical modules that don't flash with the ROM) for the an recent (Lollipop) version of ARHD. For now, s-off is needed to update to LP firmware; until AT&T releases LP officially by OTA, RUU.
Although I'm not sure its just a firmware issue (so that may or may not fix the issue). "International" ROMs often don't play well with AT&T's network; since the devs (often Euro) don't understand the nuances of AT&T's network. Not to knock those fine devs, but they can't know what they don't know (or can't test, since they aren't on that particular network). Plus, AT&T is probably mostly to blame, as they seem to do some things differently from just about every other carrier in the world.
The quick fix would be return to a stock AT&T ROM, as you have already figured out. You don't need s-off to do that. Restore your nandroid (that you should always make before messing with flashing new ROMs). Or find a stock AT&T ROM corresponding to your firmware, and flash in recovery. Another option is to relock the bootloader and RUU to stock.
Click to expand...
Click to collapse
I picked a version that was made for the cid 001 according to android file host https://www.androidfilehost.com/?w=files&flid=24258 and after numerous attempts to flash I finally got it to go by getting rid of the renamed .zip at the end. ( It was already a zip file) I think a lot of people have had that problem. Anyway I have now a sort of bricked phone that wont leave HBOOT. My son bought an M8 that should be getting here in a day or so and I was wondering if I made a nandroid of that one, maybe it could pull me out of the hole. I still have fastbboot usb so maybe theres a procedure that will get me going again. Can anyone point me? I'll buy you a beer! or 12
homthtrnut said:
I picked a version that was made for the cid 001 according to android file host https://www.androidfilehost.com/?w=files&flid=24258
Click to expand...
Click to collapse
401 firmware is Euro based firmware. AT&T is 501.
homthtrnut said:
Anyway I have now a sort of bricked phone that wont leave HBOOT. My son bought an M8 that should be getting here in a day or so and I was wondering if I made a nandroid of that one, maybe it could pull me out of the hole. I still have fastbboot usb so maybe theres a procedure that will get me going again.
Click to expand...
Click to collapse
Probably making it more complicated than need be. Also, depending on what firmware you now have on the phone, and whether it corresponds to the "new" nandroid, you might not be in any better place than you are now.
I can think of at least 2 (rather simple) ways to get the phone up and running:
1) Flash a stock or custom ROM that corresponds to your firmware. You can adb push the ROM to your phone; or alternately move it to a removable SD using a card reader connected to your computer.
What hboot and radio numbers are currently on the device?
2) Relock the bootloader and RUU back to stock.
hboot and radio numbers currently on m8
redpoint73 said:
401 firmware is Euro based firmware. AT&T is 501.
Probably making it more complicated than need be. Also, depending on what firmware you now have on the phone, and whether it corresponds to the "new" nandroid, you might not be in any better place than you are now.
I can think of at least 2 (rather simple) ways to get the phone up and running:
1) Flash a stock or custom ROM that corresponds to your firmware. You can adb push the ROM to your phone; or alternately move it to a removable SD using a card reader connected to your computer.
What hboot and radio numbers are currently on the device?
2) Relock the bootloader and RUU back to stock.
Click to expand...
Click to collapse
HBOOT-3.19.0.0000 [email protected] OS-3.42.502.1 eMMC-boot 2048MB
homthtrnut said:
HBOOT-3.19.0.0000 [email protected] OS-3.42.502.1 eMMC-boot 2048MB
Click to expand...
Click to collapse
Dude, all you have to do is relock the bootloader using the fastboot command "fastboot oem lock" and download the HTC One M8 file from here http://www.htc.com/us/support/rom-downloads.html . With the phone plugged in to the computer, run the RUU file. It will bring the phone back to the most recent 4.4.4 OTA. Takes ten minutes. You're making this wayyyyyyy harder on yourself than it should be.
homthtrnut said:
HBOOT-3.19.0.0000 [email protected] OS-3.42.502.1 eMMC-boot 2048MB
Click to expand...
Click to collapse
That is the Android 4.4.4 radio. Meaning the 401 firmware you linked and tried to flash didn't take. And it won't with s-on, unless its signed and hacked to accept AT&T's CID (which I don't think there is any 401 firmware that meets those requirements).
Agree with the above response, in that the easiest way to get the phone up and running again is relock the bootloader and RUU to stock.
Since your device is hboot 3.19, you are stuck with s-on and that means you are stuck on KitKat firmware until AT&T releases Lollipop officially.
That also means you can only run ROMs that support 4.4.4 firmware (no LP based Sense ROMs), otherwise you will run into various serious bugs like the call issue on ARHD (or broken WiFi). There are some LP GPE and AOSP ROMs that support the 4.4.4 firmware, if you want to go that route.
Was just starting out, not enough experience.
bford152 said:
Dude, all you have to do is relock the bootloader using the fastboot command "fastboot oem lock" and download the HTC One M8 file from here http://www.htc.com/us/support/rom-downloads.html . With the phone plugged in to the computer, run the RUU file. It will bring the phone back to the most recent 4.4.4 OTA. Takes ten minutes. You're making this wayyyyyyy harder on yourself than it should be.
Click to expand...
Click to collapse
The above phone was eventually returned. Now I have an unlocked, s off M8. With help from PearlyMon I was able to do it all about a month ago. Now I'm just waiting to work up the nerve to flash a customer Rom and also add in the H/K sound feature. Really liked the HD Revolution Rom, I just didn't have the wherewithall to find and install the proper firmware. This time around will be better. On third M8 now. First one, brand new slipped out of workshirt pocket and faceplanted on a tile floor. First damn day! Didn't have the otter box defender case like I should've. 2nd and 3rd ones have been refurbs. So who knows how much use the battery saw before? So I'd like a nice Rom that has built in low battery drain. Every day it seems to drain off a little sooner. Went to black background today to help it out a little. Anyway, haven't been on this forum much since the above problem and thought I'd touch base with you and say thanks. Have a nice one.
I have the same problem as the OP with ATT using any custom ROM since i got the OTA lollipop update in early April. Firmware is 4.28.xx and it appears that no one has been able to work around it without flashing back to 4.16.xx
Anyone come across a ROM that will receive calls on ATT with s-on and 4.28?
jon145 said:
I have the same problem as the OP with ATT using any custom ROM since i got the OTA lollipop update in early April. Firmware is 4.28.xx and it appears that no one has been able to work around it without flashing back to 4.16.xx
Anyone come across a ROM that will receive calls on ATT with s-on and 4.28?
Click to expand...
Click to collapse
Some folks have been having issues with "international" based custom ROMs on AT&T's LTE network. It seems that AT&T has been making some changes to LTE, possibly in preparation for Voice over LTE (VoLTE, which AT&T calls "HD Voice"), that are messing up voice calls on "international" ROMs.
Some folks have this trouble, while others don't. I can only assume its location dependent; and the mentioned "changes" have only been implemented in some areas. I've been running SkyDragon Sense 7 fine on AT&T in my home area of Massachusetts, as well as travelling to a couple other areas (Chicago and Green Bay) with none of the LTE issues.
You might try WNC's ROM here: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
Its based on the Lollipop Developer's Edition ROM, which is intended for use on AT&T's network. He's working on a version based on the AT&T 4.28 update, but its still in testing and not posted yet.
Yeah I've been running the SD 9.0 for several days and no love here in Dallas ... I could speculate for days since D is AT&T's home city.
Thanks for the info, I will definitely keep an eye out for WNC's next release. Does he usually do beta releases?
jon145 said:
Thanks for the info, I will definitely keep an eye out for WNC's next release. Does he usually do beta releases?
Click to expand...
Click to collapse
He has a beta in testing right now. Just ping him, and he will probably send you a link to the test build. Probably the only reason he would say "no" is if he is going to release soon anyway.
redpoint73 said:
Some folks have this trouble, while others don't. I can only assume its location dependent; and the mentioned "changes" have only been implemented in some areas. I've been running SkyDragon Sense 7 fine on AT&T in my home area of Massachusetts, as well as travelling to a couple other areas (Chicago and Green Bay) with none of the LTE issues.
Click to expand...
Click to collapse
Interestingly, I'm in Chicago and did have that problem with SkyDragon. Having reverted back to the stock ROM, everything works again. In my thread, I think you mentioned that you are using the "other GSM" option, rather than the AT&T specific option in AROMA. I wonder if it could be some of these AT&T specific "optimizations" or whatever that could be part of the problem.
rhughes93 said:
Interestingly, I'm in Chicago and did have that problem with SkyDragon. Having reverted back to the stock ROM, everything works again. In my thread, I think you mentioned that you are using the "other GSM" option, rather than the AT&T specific option in AROMA. I wonder if it could be some of these AT&T specific "optimizations" or whatever that could be part of the problem.
Click to expand...
Click to collapse
Interesting, indeed. Did you pick AT&T from the AROMA options? If not, try the "other GSM" option (or whatever its called).
I was just in the Chicago area a few weeks ago to visit family. Not the city proper, but the suburbs of Arlington Heights and Batavia. I was on SD 7.0 at the time (there was no AT&T option for that version, so I had picked the "other GSM"). Everything seemed to be working fine.
redpoint73 said:
Interesting, indeed. Did you pick AT&T from the AROMA options? If not, try the "other GSM" option (or whatever its called).
I was just in the Chicago area a few weeks ago to visit family. Not the city proper, but the suburbs of Arlington Heights and Batavia. I was on SD 7.0 at the time (there was no AT&T option for that version, so I had picked the "other GSM"). Everything seemed to be working fine.
Click to expand...
Click to collapse
So I re-flashed SkyDragon, and I think I was not understanding the difference between AROMA installer and the software itself. When I did it the first time, I think I did select T-mobile with wifi calling in AROMA, but AT&T within the software SIM setup. It did not work. Now after getting the stock ROM working, I re-flashed, chose the Other GSM/WWE/whatever option within AROMA, AT&T within the software, and all is right in the world. I may also try the same with Venom this weekend now that I have good restore options, though I don't recall if it had similar options in AROMA or not.
https://forum.xda-developers.com/verizon-galaxy-s7/development/rom-t3576124
All you have to do is flash the pit file from the tmobile variant. Dump it or find it elsewhere Have yet to see if the tmobile version requires the engineering kernel, testing the verizon right now. For anyone wondering why I'm linking this / posting, it's because s7 development is way too fragmented and I wanted at&t users to be included This is a modified, non root rom. Samsung pay and other apps like pokemon go and snapchat are all working! Thanks a lot @jkruse and @CVertigo1
This was all jrkruse. I did literally nothing except changed a couple things to make it boot on the flat S7.
---------- Post added at 02:23 AM ---------- Previous post was at 02:19 AM ----------
dongdong6968 said:
Have yet to see if the tmobile version requires the engineering kernel, testing the verizon right now.
Click to expand...
Click to collapse
You flashed the zip in my thread? You are running on the factory kernel, right?
Verizon worked but after a reboot on the stock kernel, it requires the eng kernel to boot. It turned on once though. The t mobile needed eng kernel outright.
Another user figured out the problem. You need to uncheck inject root in FlashFire before flashing. I ran into this problem once and forgot to mention it in the OP. Everything should boot normally on Verizon without having to Odin the eng kernel. I'd assume TMobile will also boot normally, but I can't confirm because I don't use TMobile, so I didn't verify it.
I have updated the instructions to mention unchecking inject root.
I'd like to add that you are welcome to put my instructions and zip in your OP. That way everything is all in one place without having to change forums.
Any way to gain root on this? Because I ain't gonna install it unless I can keep root
loganbeck14 said:
Any way to gain root on this? Because I ain't gonna install it unless I can keep root
Click to expand...
Click to collapse
Yes, you can get root with the engineering kernel. But the whole point of this ROM is to be able to have a debloated &/| playstore rom, while still being able to use things like samsung pay, Pokemon Go, snapchat, etc.
dongdong6968 said:
Yes, you can get root with the engineering kernel. But the whole point of this ROM is to be able to have a debloated &/| playstore rom, while still being able to use things like samsung pay, Pokemon Go, snapchat, etc.
Click to expand...
Click to collapse
Honestly I can log in to Snapchat before I root, and I don't play Pokemon go also I just wanted a rom that is at least somewhat compatible with my phone model
followed steps to a t. Using an SM-G930A ATT S7 and on final reboot have the pad lock and then after screen goes black for a few seconds reboots?? what did i do wrong. again i made sure to follow all instructions to a T. had to flash the t-mobile nougat before starting as i received a ext4 error on att rom.
Can anyone help me out?? in order to get my ATT S7 to boot i had to use the Eng. kernel as it wouldn't boot without it. see my previous post
Billy06010 said:
Can anyone help me out?? in order to get my ATT S7 to boot i had to use the Eng. kernel as it wouldn't boot without it. see my previous post
Click to expand...
Click to collapse
Did you do this step?
6) Now click flash firmware and chose AP_G930TUVU4BQB1_CL10376601_QB12449107_REV02_user_ low_ship_MULTI_CERT_meta.tar.md5 SELECT ALL OF THE PARTIONS!!!
As i Said in my earlier post I followed all steps to a t. Had to use the eng kernal to be able to boot after the last step. Does it have to do with the fact that i started from the t mobile firmware?? Only did that because the ATT firmware gave me an ext4 error during first odin step. someone has to be able to help
rarecarpenter said:
Did you do this step?
6) Now click flash firmware and chose AP_G930TUVU4BQB1_CL10376601_QB12449107_REV02_user_ low_ship_MULTI_CERT_meta.tar.md5 SELECT ALL OF THE PARTIONS!!!
Click to expand...
Click to collapse
Billy06010 said:
As i Said in my earlier post I followed all steps to a t. Had to use the eng kernal to be able to boot after the last step. Does it have to do with the fact that i started from the t mobile firmware?? Only did that because the ATT firmware gave me an ext4 error during first odin step. someone has to be able to help
Click to expand...
Click to collapse
Sorry I couldn't help. I also started with the Tmobile firmware, and chose the Playstore version. I remember it rebooting to recovery one time I did it, but I just rebooted and worked out. Good luck.
Playstore version?? of what?? thanks for trying to help I appreciate it alot
rarecarpenter said:
Sorry I couldn't help. I also started with the Tmobile firmware, and chose the Playstore version. I remember it rebooting to recovery one time I did it, but I just rebooted and worked out. Good luck.
Click to expand...
Click to collapse
finally got it working!!! cant seem on either t mobile or verizon version to get wifi calling working any help?? also advanced calling?? Without it im going back to the ATT Firmware