YOU HOLD MYSELF AND XDA FREE FROM ANY LIABILITY. FLASH AT YOUR OWN RISK
Pulled the radio for the Unreleased Droid Maxx 4.4.3 Update. Radio Version 2323.038.123.00r For those who need to reflash or want the baseband without updating.
INSTALLATION:
1) Download the Files here http://fs1.d-h.st/download/00132/FBi/4.4_19.6.3%20radio.zip
2) Reboot into bootloader
3) Open a command prompt and type these commands
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
4) Verify all commands were successful
5) Verify correct baseband version in about phone
6) Profit. Thank baby jesus.
Thanks for sharing. I don't think I'll flash it unless there's some dramatic improvements over the current baseband you've noticed.
Sent from my Nexus 5 using Tapatalk
[4.4.3]Radio]MSM8960PRO_BP_2323.038.123.00r
[4.4.3]Radio]MSM8960PRO_BP_2323.038.123.00r - Droid Mini works fine...
Topsnake said:
4.4.3 Radio
4.4 Radio 19.6.3
Click to expand...
Click to collapse
I'm on 4.2.2, could I install the 4.4.3 radio? Where can I find the 4.2.2 radio (12.15.15) files in case I need to go back?
distortedloop said:
Thanks for sharing. I don't think I'll flash it unless there's some dramatic improvements over the current baseband you've noticed.
Click to expand...
Click to collapse
I would also like to know if this patch might improve GPS signal.
tutorialbs said:
I'm on 4.2.2, could I install the 4.4.3 radio? Where can I find the 4.2.2 radio (12.15.15) files in case I need to go back?
I would also like to know if this patch might improve GPS signal.
Click to expand...
Click to collapse
+1
tutorialbs said:
I'm on 4.2.2, could I install the 4.4.3 radio? Where can I find the 4.2.2 radio (12.15.15) files in case I need to go back?
I would also like to know if this patch might improve GPS signal.
Click to expand...
Click to collapse
chuck864 said:
+1
Click to expand...
Click to collapse
Yes you can install the radio if on 4.2.2. I have attached the stock 4.2.2 files here for you guys. If I recall correctly the baseband controls GPS so yes an improvement can be made.
Topsnake said:
Yes you can install the radio if on 4.2.2. I have attached the stock 4.2.2 files here for you guys. If I recall correctly the baseband controls GPS so yes an improvement can be made.
Click to expand...
Click to collapse
Thanks, very much appreciated and thanks for this upgrade Installed without issue.
I watched my network signal strength numbers for a few minutes before and after. It seems reception is very slightly better, at least for this one location I very briefly tested in. I didn't have a good way to tell if GPS is better or not.
Before upgrade:
Droid MAXX (Rooted, locked bootloader)
4.2.2 (12.15.15)
Baseband radio (MSM8960BP_2323.024.95.00R)
best
1x= 91dbm
4G= 110dbm
avg
1x= 94dBm
4G= 114dBm
worst
1x= 97
4G= 117After upgrade:
Droid MAXX (Rooted, locked bootloader)
4.2.2 (12.15.15)
Baseband (MSM8960PRO_BP_2323.038.123.00R)
best
1x= 89dbm
4G= 108dbm
avg
1x= 92dbm
4G= 114dbm
worst
1x= 97dbm
4G= 117dbm
Command results:
Code:
C:\XT1080JB>adb reboot bootloader
C:\XT1080JB>fastboot flash modem NON-HLOS.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'modem' (53804 KB)...
OKAY [ 3.594s]
writing 'modem'...
OKAY [ 2.359s]
finished. total time: 5.953s
C:\XT1080JB>fastboot erase modemst1
(bootloader) Variable not supported!
erasing 'modemst1'...
OKAY [ 0.406s]
finished. total time: 0.406s
C:\XT1080JB>fastboot erase modemst2
(bootloader) Variable not supported!
erasing 'modemst2'...
OKAY [ 0.414s]
finished. total time: 0.422s
C:\XT1080JB>fastboot flash fsg fsg.mbn
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'fsg' (1220 KB)...
OKAY [ 0.336s]
writing 'fsg'...
OKAY [ 0.781s]
finished. total time: 1.117s
C:\XT1080JB>fastboot reboot
rebooting...
finished. total time: 0.000s
C:\XT1080JB>
Topsnake, just to let you know the link you posted for the 4.4 radios directs me to the 4.4.2 radios, I was able to get the stock 4.4 radios from your other thread, but I just wanted to let you know so you could update this thread.
im on 4.4 with unlocked bootloader can i flash it
I'm on latest 4.4.4 with locked bootloader and I was able to flash it.
I need this 4.2.2 radio... anyone still have it?
Related
Hello all, Let me start this off first by saying I am in no way shape or form a developer. I am just providing the Guide/Steps to install only the new radio without needing the Engineering Hboot. It also skips the steps of reflashing your boot.img and recovery image that get over written if you flash the firmware.zip
Items you will need before installing radio
-ADB and Fastboot connectivity
-S-OFF
-Radio.zip in file location that you will be executing the fastboot commands (ie. c/DNA/DNA Unclock/)
Thanks to lazarus2297 for compiling the radio zip into a fashable form to eliminate the need to reflash BOOT/Recovery
Radio ZIp- http://dl.dropbox.com/u/30538029/radio.zip
STEP 1- Verify ADB connectivity with your PC
C:\android\DNA Unlock>adb devices
List of devices attached
FA2B9S503169 device
STEP 2- Rebot Bootloader
C:\android\DNA Unlock>adb reboot bootloader
STEP 3- execute Fastboot OEM RebootRUU command
C:\android\DNA Unlock>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.159s]
finished. total time: 0.160s
STEP 4- Fastboot Flash radio.zip
C:\android\DNA Unlock>fastboot flash zip radio.zip
sending 'zip' (18514 KB)...
OKAY [ 1.989s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[radio] unzipping & flushing...
(bootloader) [RUU]UZ,radio,0
(bootloader) [RUU]UZ,radio,9
(bootloader) [RUU]UZ,radio,18
(bootloader) [RUU]UZ,radio,27
(bootloader) [RUU]UZ,radio,36
(bootloader) [RUU]UZ,radio,41
(bootloader) [RUU]UZ,radio,50
(bootloader) [RUU]UZ,radio,59
(bootloader) [RUU]UZ,radio,68
(bootloader) [RUU]UZ,radio,73
(bootloader) [RUU]UZ,radio,82
(bootloader) [RUU]UZ,radio,87
(bootloader) [RUU]UZ,radio,95
(bootloader) [RUU]UZ,radio,100
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,36
(bootloader) [RUU]WP,radio,73
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
OKAY [ 6.913s]
finished. total time: 8.904s
STEP 5- Reboot
C:\android\DNA Unlock>fastboot reboot
rebooting...
finished. total time: 0.047s
STEP 6 VERIFY BASEBAND
Thanks to JCase, DSB, Beaups and all the real developers who made S-OFF possible on the DNA
Thanks for the guide. Now we've got to try out some other radios too. The one that came with the OTA seems to have better connectivity, but that doesn't mean there are no others that are better. Any idea which ones would work?
orangechoochoo said:
Thanks for the guide. Now we've got to try out some other radios too. The one that came with the OTA seems to have better connectivity, but that doesn't mean there are no others that are better. Any idea which ones would work?
Click to expand...
Click to collapse
no clue noone else has a similar phone until the M7 comes out... the TBOLT/Evo used to have interchangeable radios but we had to flash CDMA and LTE radios separate because they are different bands...
I"m just sticking with Official radios
I took the OTA, and now have S-Off, can I still use this?
EchoX860 said:
I took the OTA, and now have S-Off, can I still use this?
Click to expand...
Click to collapse
Since you have the OTA you have the new radio.
Was told these steps would eliminate my Wifi issues.
EchoX860 said:
Was told these steps would eliminate my Wifi issues.
Click to expand...
Click to collapse
Do you still have the wifi issues?
EchoX860 said:
Was told these steps would eliminate my Wifi issues.
Click to expand...
Click to collapse
If you took the OTA, then you already have these radios.
Your WiFi issues are likely related to improper flashing of kernel/modules. When you flashed your last ROM, what kernel did you use? The 2 most popular around here are DSB's Cubed kernel, and Elkay's kernel.
You must unzip the kernel files into their own dedicated folder so you can access them.
These kernels come with a 'modules' zip file that must be flashed separately in recovery before everything will function correctly. If you're only flashing the boot.img, then there is your problem.
To flash the boot.img, you should use the IMG Flash GUI app (in Android), or via fastboot, and then immediately reboot to recovery and flash the modules.
I always also wipe cache and Dalvik cache too.
Sent from my HTC DNA
i used the eng hboot and flashed the radio fine. the wifi improved alot and i no longer need to wait for youtube to buffer lol
Sent from my HTC6435LVW using xda app-developers app
Since you took the OTA, I don't think custom kernels are compatible with it. In the development forum someone posted the new kernel and modules, flash those to fixyour WiFi issues.
Does anyone know if this radio will help GSM ?
maxtcee said:
Does anyone know if this radio will help GSM ?
Click to expand...
Click to collapse
I'm testing that now on tmo , signal is a little stronger but I haven't visited the areas I usually run into major problems. As long as it stops dropping completely I'm happy. Mostly.
Tapatalked from my HTC DNA
You can't flash this radios in hboot?
Sent from my HTC6435LVW using Tapatalk 2
You were right, I flashed the Dice Kernel, but stock modules. Stupid mistake, but it works great now.
So will i be able to run the old kernels with the new radio.img without any problems? i know, flash the boot.img in fastboot and the modules in recovery afterwards
Thank you very much for this! Any chance to post the original radios this way, too (or if someone has a link) in case reception and data speeds are actually worse with the newer radios? That way we can flash back if need be
ML417 said:
So will i be able to run the old kernels with the new radio.img without any problems? i know, flash the boot.img in fastboot and the modules in recovery afterwards
Click to expand...
Click to collapse
Yes, I'm running my phone like that right now. The radio seems better but I didn't do a before and after speed test.
orangechoochoo said:
Yes, I'm running my phone like that right now. The radio seems better but I didn't do a before and after speed test.
Click to expand...
Click to collapse
The updated radio seems to have helped my wifi speeds. Not sure about 4g though since my speeds vary from 15 to 50 depending on the time of day
Sent from my HTC6435LVW using xda app-developers app
I love the fact that we can now pick and choose which things to install.
Does anyone have the md5 of the radio . zip?
Sent from my HTC6435LVW using Tapatalk 2
Edit dfownloads removed as the host started serving malware.
I dont have these files anymore, sorry, please dont ask for them
For other HTC devices supported by FacePalm, please see this thread: http://forum.xda-developers.com/showthread.php?t=2155069
Welcome to Facepalm S-Off for modern HTC phones.
Credits and terms:
Exploit by beaups, full guide, testing, and concept by jcase and beaups. Thanks to dsb9938 and dr_drache for support and testing. Thanks also to all of the regulars at teamandirc. Additional thanks to indirect for Evo LTE testing.
Both beaups and jcase will collect the applicable active bounties. Further donations are greatly appreciated and can be sent to:
beaups - [email protected] - http://forum.xda-developers.com/donatetome.php?u=711482
jcase - [email protected] - http://forum.xda-developers.com/donatetome.php?u=2376614
dsb9938 - [email protected] - http://forum.xda-developers.com/donatetome.php?u=2963256
dr_drache - [email protected] - https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=6LRSY8MT8P3A6
You can also come by irc for support or just to say thanks: #FacePalm http://chat.andirc.net:8080/?channels=facepalm
While this process shouldn’t be too risky, bricks can happen. None of us will be accountable. If you are worried, don’t do it.
This is a pretty simple method, however, you will need to have a working adb and fastboot environment. This method will work on any operating system that supports adb and fastboot. You should understand how to use a terminal window in your O/S. If you don’t understand adb and fastboot, you probably don’t need S-off.
Lastly, the work herein should not be stolen, repackaged, one clicked, bat’d, etc. soffbin3 is not GPL and may not be reused, integrated into other work, reposted, or redistributed without our permission.
For this to work, you must be rooted and have superCID (unlock/custom recovery is optional), see the threads below for help and information regarding obtaining superCID, unlock, root, etc. Note these threads are provided for convenience only. Please look for support for them in each respective thread if you need it, do NOT clutter this thread with support requests regarding obtaining superCID and/or root! If you try this process without superCID, it will not work, and you may have issues!:
SuperCID for HTC Evo 4G LTE:
Code:
adb shell
su
echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
1)
Code:
adb reboot bootloader
2)
Code:
fastboot oem rebootRUU
(wait for black HTC Screen)
3)
Code:
fastboot flash zip PJ7510000-EvoLTE.zip
After a while, You should see the following error “FAILED (remote: 92 supercid! please flush image again immediately)”
7) Immediately issue the following command:
Code:
fastboot boot EvoLTE-rescue.img
(this is fastboot boot, NOT fastboot flash!)
8) Allow device to boot (may not fully boot on some custom roms)
Code:
adb reboot bootloader
9) You should see what you are looking for!
If you need help or just care to say thanks, join us on IRC: #FacePalm http://chat.andirc.net:8080/?channels=facepalm
Enjoy.
Took me all of 2 minutes to get s-off.
Extra info: This works on 3.16 firmware and subsequently 3.15 as well.
Indirect said:
Took me all of 2 minutes to get s-off.
Extra info: This works on 3.16 firmware and subsequently 3.15 as well.
Click to expand...
Click to collapse
Probably worked on 3.16 for you as you already had supercid, I'm guessing the recent 3.16 update prevents changing the CID.
I dont think so because we've never used CID on this phone before. Only way to find out is to test.
Thanks for bringing this to the evo lte! I have windows 8 so this is gonna make it much easier compared to dirtyracun, thanks!
Thread cleaned. Going forward let's see about keeping it respectful in here.
You guys are freaking awesome thanks to all involved
Sent from my PoS MoPho
This is super easy! You guys rock. Thanks 4 this
Sorry for the stupid question, but what is supercid.?
Sent from my EVO using Tapatalk 2
Chocorico said:
Sorry for the stupid question, but what is supercid.?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Pretty sure it's that first 3 lines of code - makes your phone believe it has older firmware so you can flash older RUUs/updates. Swear there used to be a thread for it around here somewhere.
Help! I'm bricked.
C:\android-sdk-windows\platform-tools>fastboot devices
HT25KS405806 fastboot
C:\android-sdk-windows\platform-tools>adb reboot bootloader
C:\android-sdk-windows\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.059s]
finished. total time: 0.062s
C:\android-sdk-windows\platform-tools>fastboot flash zip PJ7510000-EvoLTE.zip
sending 'zip' (35863 KB)...
OKAY [ 2.435s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
FAILED (remote: 92 supercid! please flush image again immediately)
finished. total time: 3.450s
C:\android-sdk-windows\platform-tools>fastboot boot EvoLTE-rescue.img
downloading 'boot.img'...
OKAY [ 0.853s]
booting...
OKAY [ 0.005s]
finished. total time: 0.862s
Then my phone never booted back up.
Hold power for 40 seconds, nothing in that should be causing bricks.
EDIT:
Apparently you were not bricked, we can only support stock roms, can't control how it behaves on AOSP, given it should still work, but it might not until you do a reboot. Please next time confirm that you are bricked before posting that you are.
[23:24:30] <BB15> I'm actually not bricked. I got it to boot back up and I'm s-off, but now I get prompted to activate my phone
BB15 said:
Help! I'm bricked.
C:\android-sdk-windows\platform-tools>fastboot devices
HT25KS405806 fastboot
C:\android-sdk-windows\platform-tools>adb reboot bootloader
C:\android-sdk-windows\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.059s]
finished. total time: 0.062s
C:\android-sdk-windows\platform-tools>fastboot flash zip PJ7510000-EvoLTE.zip
sending 'zip' (35863 KB)...
OKAY [ 2.435s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
FAILED (remote: 92 supercid! please flush image again immediately)
finished. total time: 3.450s
C:\android-sdk-windows\platform-tools>fastboot boot EvoLTE-rescue.img
downloading 'boot.img'...
OKAY [ 0.853s]
booting...
OKAY [ 0.005s]
finished. total time: 0.862s
Then my phone never booted back up.
Click to expand...
Click to collapse
jcase said:
Hold power for 40 seconds, nothing in that should be causing bricks.
EDIT:
Apparently you were not bricked, we can only support stock roms, can't control how it behaves on AOSP, given it should still work, but it might not until you do a reboot. Please next time confirm that you are bricked before posting that you are.
[23:24:30] I'm actually not bricked. I got it to boot back up and I'm s-off, but now I get prompted to activate my phone
Click to expand...
Click to collapse
Yeah, I wasn't bricked. After waiting for some time for my phone to reboot after running FacePalm I unplugged the USB and held the power button and it booted right up. Rebooted the bootloader and verified that I was s-off. Then I ran into the activation problem. Just flashed MeanBean and ran through the activation, now all is good. Your work on this is much appreciated.
Thankkssssss S-off already
Chocorico said:
Sorry for the stupid question, but what is supercid.?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
mildlydisturbed said:
Pretty sure it's that first 3 lines of code - makes your phone believe it has older firmware so you can flash older RUUs/updates. Swear there used to be a thread for it around here somewhere.
Click to expand...
Click to collapse
here you go:
[SUPERCID] SuperCID For EVO LTE(Ruu to older firmware(not hboots))
So for clarity, the superCID commands are run from the phone while booted? or in bootloader? It looks from the way its written thats its meant to be done while the device is booted
Edit:
Thanks OCN
Finally have s-off!!!!
Thx to Facepalm S-Off I now have s-off. Finally,after a long year and a half of trying to get s-off.....
I must have been doing a few things wrong this whole time or Facepalm S-Off has done it right...
Rxpert said:
So for clarity, the superCID commands are run from the phone while booted? or in bootloader? It looks from the way its written thats its meant to be done while the device is booted
Edit:
Thanks OCN
Click to expand...
Click to collapse
I ran it while booted. No issues.
Sent from my EVO using Tapatalk 2
Fantastic job.
Already S off but props given.
Very nice.
Wow, this was incredibly easy. Soff in less than 2 minutes. I just followed the directions and flashed stock rom to be safe. $$ coming to you guys on payday!!
I tried to update my droid version from 4.0.4 (6.16.211.XT912.Verizon.en.US) to the latest JB but now I'm currently stock with these in my phone's display:
Invalid Flash Mode (S) (Boot Failure)
0A.77
eMMC Info: Size 16G
To return to normal mode - first press power key to power down
Device is LOCKED. Status Code: 0
Battery OK
OK to Program
Transfer Mode:
USB Connected
Invalid CG OTV (CG: system): Invalid SP Data
Invalid CG HAB (CG: system, status: 0x0056)
Invalid CG OTV (CG: system)
Please help me, I don't know what to do anymore :crying:
Are you sure you came from ICS? If yes, please post the EXACT JB firmware Version you tried to flash.
Gesendet von meinem XT910 mit Tapatalk 4
dtrail1 said:
Are you sure you came from ICS? If yes, please post the EXACT JB firmware Version you tried to flash.
Gesendet von meinem XT910 mit Tapatalk 4
Click to expand...
Click to collapse
Umm, i'm not sure what you mean with ICS, this is actually my first android phone. When it was still working, the android version was 4.0.4 (6.16.211.XT912.Verizon.en.US).
This happened after I tried to follow this http://forum.xda-developers.com/showthread.php?t=2192467. I wanted to update it to JB, and then root it afterwards. But this already happened after doing option 2.
This is just a part of the process, when I followed what was instructed in that post I posted earlier. Im concern about the writing 'devtree'... INFOPreflash validation failure part what could have caused this?
sending 'mbm' (512 KB)... OKAY [ 0.076s]
writing 'mbm'... OKAY [ 1.206s]
rebooting into bootloader... OKAY [ 0.264s]
< waiting for device >
sending 'mbmloader' (42 KB)... OKAY [ 0.018s]
writing 'mbmloader'... OKAY [ 0.299s]
sending 'mbm' (512 KB)... OKAY [ 0.214s]
writing 'mbm'... OKAY [ 0.468s]
rebooting into bootloader... OKAY [ 0.262s]
< waiting for device >
erasing 'cache'... OKAY [ 0.033s]
sending 'logo.bin' (854 KB)... OKAY [ 0.096s]
writing 'logo.bin'... OKAY [ 0.256s]
sending 'devtree' (512 KB)... OKAY [ 0.257s]
writing 'devtree'... INFOPreflash validation failure
FAILED (remote: )
sending 'system' (262144 KB)... OKAY [ 30.025s]
writing 'system'... OKAY [ 20.647s]
sending 'system' (262144 KB)... OKAY [ 32.498s]
writing 'system'... OKAY [ 21.544s]
sending 'system' (130816 KB)... OKAY [ 14.586s]
writing 'system'... OKAY [ 10.794s]
sending 'boot' (8192 KB)... OKAY [ 1.048s]
writing 'boot'... INFOPreflash validation failure
FAILED (remote: )
sending 'recovery' (9216 KB)... OKAY [ 1.124s]
writing 'recovery'... INFOPreflash validation failure
FAILED (remote: )
sending 'preinstall' (262144 KB)... OKAY [ 39.146s]
writing 'preinstall'... OKAY [ 22.889s]
sending 'preinstall' (262144 KB)... OKAY [ 35.470s]
writing 'preinstall'... OKAY [ 21.680s]
sending 'preinstall' (98304 KB)...
i really hope i can get some help with this T_T
Just to add, the motorola model is XT909 (at least that was what is at the back of the phone "sticker")
This is the best I can find....
http://forum.xda-developers.com/showthread.php?t=2267264
Sent from my XT907 using xda app-developers app
ezknives said:
This is the best I can find....
http://forum.xda-developers.com/showthread.php?t=2267264
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Hi ezknives,
I've seen that post as well, the problem is I really am at a lost on how to do it myself. I am pretty much ignorant on Android phones.
Bump!
Research how to do an SBF. It will return you to some version of stock Moto android. Probably ICS. At least at that point you will have a working phone.
ras0787 said:
Research how to do an SBF. It will return you to some version of stock Moto android. Probably ICS. At least at that point you will have a working phone.
Click to expand...
Click to collapse
I tried looking into some tutorials about SBF, and a SBF file is needed. I don't have any clue where to get my hands on that.
navisomar said:
I tried looking into some tutorials about SBF, and a SBF file is needed. I don't have any clue where to get my hands on that.
Click to expand...
Click to collapse
Have you tried this .http://forum.xda-developers.com/showthread.php?t=1900012
coefficientoffriction said:
Have you tried this .http://forum.xda-developers.com/showthread.php?t=1900012
Click to expand...
Click to collapse
I read about that but my question regarding that post is that the droid razr utility version, the fifth step in the instruction (5th - download and flash the XT912 fastboot file <-- Dont have any clue how to do this operation) and the line after the PLS READ which says "The only way to power up your phone is by entering BP TOOLS" <-- I also dont know or understand what this means. Sorry if I sound so hopeless and stupid asking all this.
navisomar said:
I read about that but my question regarding that post is that the droid razr utility version, the fifth step in the instruction (5th - download and flash the XT912 fastboot file <-- Dont have any clue how to do this operation) and the line after the PLS READ which says "The only way to power up your phone is by entering BP TOOLS" <-- I also dont know or understand what this means. Sorry if I sound so hopeless and stupid asking all this.
Click to expand...
Click to collapse
Flashing fastboot files is done through RSDLite. Its the Motorola Firmware flashing tool which can flash SBF or Fastboot files to your device.
There are many guides for that process. Search it.
Since the process requires you to delete your CID (customer unique Id), The phone shows an error of missing CID. To bypass the error, you need to boot through recovery by entering into BP Tools. Google it and you'll have a better understanding. However this can be fixed using Boot Menu Manager but thats another story
Once you delete your CID, you cannot restore it if you haven't backed it up since CID is unique to every phone. However in order to flash a firmware other than your region you need to delete it as it cannot be done without deleting the CID.
There's no problem in asking. Feel free to clear all your doubts before beginning.
neo.ank said:
Flashing fastboot files is done through RSDLite. Its the Motorola Firmware flashing tool which can flash SBF or Fastboot files to your device.
There are many guides for that process. Search it.
Since the process requires you to delete your CID (customer unique Id), The phone shows an error of missing CID. To bypass the error, you need to boot through recovery by entering into BP Tools. Google it and you'll have a better understanding. However this can be fixed using Boot Menu Manager but thats another story
Once you delete your CID, you cannot restore it if you haven't backed it up since CID is unique to every phone. However in order to flash a firmware other than your region you need to delete it as it cannot be done without deleting the CID.
There's no problem in asking. Feel free to clear all your doubts before beginning.
Click to expand...
Click to collapse
Thanks for clearing this up for me. I will then begin reading on these pointers you've mentioned and get back here if ever something comes up that I don't fully understand.
hi. my htc amaze is softbreaked and i need RUU to flash it . i don't know CID . How do I know which RUU i download ? i tested all i have file but did not answer.
pourya-man said:
hi. my htc amaze is softbreaked and i need RUU to flash it . i don't know CID . How do I know which RUU i download ? i tested all i have file but did not answer.
Click to expand...
Click to collapse
Maybe you can find your CID this way:
http://forum.xda-developers.com/showthread.php?t=1548090
pbergonzi said:
Maybe you can find your CID this way:
http://forum.xda-developers.com/showthread.php?t=1548090
Click to expand...
Click to collapse
thank's :laugh:
CID is HTC__044
Which RUU do I get?
pourya-man said:
thank's :laugh:
CID is HTC__044
Which RUU do I get?
Click to expand...
Click to collapse
If you are capable enough to flash your phone, you are capable of searching.
I searched, and without any certainty of what you did do or should do, found this link:
http://forum.xda-developers.com/showpost.php?p=41310223&postcount=135
If this link is helpful to you, be certain to use proper instructions for what you want to do.
Let me repeat that, "Be certain to use proper instructions for what you want to do."
thank my friend . problem fixed
Glad for you--you're getting pretty good at this.
Hello again . i s-off amaze and updated to ics but can't flash recovery
log :
---------------------------------------------------------------------------------------------------------------------------------
E:\Application\Android\Phone\HTC\01 Fastboot>"E:\Application\Android\Phone\HTC\0
1 Fastboot\Flash Recovery.bat"
E:\Application\Android\Phone\HTC\01 Fastboot>fastboot flash recovery recovery.im
g
sending 'recovery' (5502 KB)... OKAY [ 1.264s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 1.580s
---------------------------------------------------------------------------------------------------------------------------------
hboot is locked . i can't unlock it with Unlock_code.bin file.
What is the solution?
you need to get a new Unlock_code.bin file from htcdev.com, Something has changed older code won't work.
i have been trying to flash a new firmware to my htc one m8 but i get this error
C:\Users\kenny\Desktop\fastboot_adb>fastboot flash zip firmware.zip
sending 'zip' (30216 KB)...
OKAY [ 1.780s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 2.280s
i am s-off it the phone is relocked and the firmware is the 3.28.401.9 -firmware for the android L 5.0 rom
can some one tell me what im doing wrong ?
Wubzie said:
i have been trying to flash a new firmware to my htc one m8 but i get this error
C:\Users\kenny\Desktop\fastboot_adb>fastboot flash zip firmware.zip
sending 'zip' (30216 KB)...
OKAY [ 1.780s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 2.280s
i am s-off it the phone is relocked and the firmware is the 3.28.401.9 -firmware for the android L 5.0 rom
can some one tell me what im doing wrong ?
Click to expand...
Click to collapse
Which version on m8 do you have? It says model id check failed which means it's looking for a different cid
Sent from my HTC One_M8 using Tapatalk
Cannot flash anything with bootloader "relocked" and also whatever firmware your trying to flash,your MID model id is wrong for firmware your trying to flash. Figure out what model id is in the firmware and make sure yours is listed.
Wubzie said:
i have been trying to flash a new firmware to my htc one m8 but i get this error
C:\Users\kenny\Desktop\fastboot_adb>fastboot flash zip firmware.zip
sending 'zip' (30216 KB)...
OKAY [ 1.780s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 2.280s
i am s-off it the phone is relocked and the firmware is the 3.28.401.9 -firmware for the android L 5.0 rom
can some one tell me what im doing wrong ?
Click to expand...
Click to collapse
Wonders_Never_Cease said:
Cannot flash anything with bootloader "relocked" and also whatever firmware your trying to flash,your MID model id is wrong for firmware your trying to flash. Figure out what model id is in the firmware and make sure yours is listed.
Click to expand...
Click to collapse
ok ill unlock it , also i know the cid is CW__001. i know there is a thread of firmwares for the 5.0 android L rom that are compatible dose some one have the link?
if not its cool ill just troll around till i fined it
Are you not supposed to do fastboot oem rebootRUU and then do that?
Just wondering myself.
Sammy Eli said:
Are you not supposed to do fastboot oem rebootRUU and then do that?
Just wondering myself.
Click to expand...
Click to collapse
yes you are, but my prob i guess is that my cid is not matching up to my firmware. and the only one that i can fined that works with Android L 5.0 is the 3.28.401.9 and thats the one i have but it dose not work for me and im on cid : CW__001
i have been thinking about changing to super cid but idk if that would work.
Wubzie said:
ok ill unlock it , also i know the cid is CW__001. i know there is a thread of firmwares for the 5.0 android L rom that are compatible dose some one have the link?
Click to expand...
Click to collapse
Any 3.x firmware should work.
For AT&T's network, you will likely have the best results with 3.28.1540, which is found on Wonders_Never_Cease's ROM thread: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
Since its the Dev Edition firmware (meant for use on AT&T) you won't even need to change CID/MID.
But be aware for any "international" based ROM (even on the proper firmware), there is a chance for some issues on AT&T's network (most commonly, broken Google services on LTE).
I'm having the same problem with my friends AT&T HTC One m8. I'm with verizon and had no issues whatsoever. However, he wanted to try SkyDragon's new Lollipop ROM, so he found the appropriate firmware, flashed it, flashed the 5.0 ROM, and everything was good. However, after finding several things about said ROM that he didn't like, he now wants to go back to a 4.4.4 Sense based ROM, but can't. We've tried flashing different firmwares, and kept getting error code 41. Then, after reading through this thread, I downloaded the 3.28.1504...(or something like that) firmware and attempted to flash. This time I got the error code 42. customer id check fail. What the heck is going on? He's tried flashing ViperOne 3.2.1, and after selecting all his preferences in Aroma, it fails, and will not flash. The only ROM other that 5.0 he's been able to flash is CM11. He's wanting to go back to Sense, but it's looking to be impossible. Has anyone had similar issues and found a way through this? Please Help!!!
blkhrt13 said:
I'm having the same problem with my friends AT&T HTC One m8. I'm with verizon and had no issues whatsoever. However, he wanted to try SkyDragon's new Lollipop ROM, so he found the appropriate firmware, flashed it, flashed the 5.0 ROM, and everything was good. However, after finding several things about said ROM that he didn't like, he now wants to go back to a 4.4.4 Sense based ROM, but can't. We've tried flashing different firmwares, and kept getting error code 41. Then, after reading through this thread, I downloaded the 3.28.1504...(or something like that) firmware and attempted to flash. This time I got the error code 42. customer id check fail. What the heck is going on? He's tried flashing ViperOne 3.2.1, and after selecting all his preferences in Aroma, it fails, and will not flash. The only ROM other that 5.0 he's been able to flash is CM11. He's wanting to go back to Sense, but it's looking to be impossible. Has anyone had similar issues and found a way through this? Please Help!!!
Click to expand...
Click to collapse
What does "appropriate firmware" mean exactly? It would be 3..28.401 firmware if you are going by the Skydragon thread. But you really need to be specific if you want us to help properly.
If the phone's CID was changed to flash the 3.28.401, then you need to change it back to AT&T's CID to flash 3.28.1540 firmware.
Failure to flash Viper is probably not related. Fastboot erase cache, and re-install TWRP by fastboot (update, if the present version is old) will clear up fail to flash issues a great majority of the time. Also, you can try another Sense software 3.x custom ROM.
redpoint73 said:
What does "appropriate firmware" mean exactly? It would be 3..28.401 firmware if you are going by the Skydragon thread. But you really need to be specific if you want us to help properly.
If the phone's CID was changed to flash the 3.28.401, then you need to change it back to AT&T's CID to flash 3.28.1540 firmware.
Failure to flash Viper is probably not related. Fastboot erase cache, and re-install TWRP by fastboot (update, if the present version is old) will clear up fail to flash issues a great majority of the time. Also, you can try another Sense software 3.x custom ROM.
Click to expand...
Click to collapse
He was actually able to fix it. He found firmware that cleared all his issues up...at least I think that's what he did. Anyway he can flash pretty much anything he wants now. Lol. But thank you for your reply.