Related
I'd like to update my RAZR i to JB by flashing one of the "Homemade Fastboots", but I can't get the unlock status of this device and so I am a bit afraid the flash process might fail halfway in and the device becoming unusable. I have never played around with things like unlocking or rooting before.
The command found on page 9 of "Unlock the Bootloader on Your RAZR i" is not recognized (see below). The adt-bundle I used was just downloaded today.
C:\RAZR\adt-bundle-windows-x86_64\sdk\platform-tools>fastboot oem getvar all
...
(bootloader) unrecognized oem command
(bootloader) List of oem commands:
(bootloader) system
(bootloader) showtext
(bootloader) partitions
(bootloader) partition
(bootloader) md5
(bootloader) fb_mode_set
(bootloader) fb_mode_clear
(bootloader) blank
(bootloader) build-signature
(bootloader) help
(bootloader) unlock
(bootloader) lock
(bootloader) get_unlock_data
(bootloader) pull
(bootloader) push
(bootloader) dump
(bootloader) bosconsole
(bootloader) prod_fuse
(bootloader) nvm
(bootloader) config
(bootloader) dnx_timeout
(bootloader) proxy
FAILED (remote failure)
finished. total time: 0.240s
Btw, I did get an unlock key through the Motorola website, but the unlock command also doesn't work.
C:\RAZR\adt-bundle-windows-x86_64\sdk\platform-tools>fastboot oem unlock ............
...
(bootloader) Not supported on engineer phone!
FAILED (remote failure)
finished. total time: 0.186s
Does anyone know if the Homemade Fastboots can be loaded on this RAZR i without "bricking" it?
Ok, if unsure about flashing the homemade fastboots, is there any other reasonably safe way to flash a regular JB firmware on this RAZR i that currently has obviously a non-standard firmware?
I am somewhat worried to get another "not supported on this phone" or other error message in the middle of the process of loading another firmware, when I've already gotten beyond the point of no return, and then being stuck with a non-working phone.
Iridium8 said:
(bootloader) Not supported on engineer phone!
Click to expand...
Click to collapse
This mean that your phone is a prototype for test purposes, not a retail phone. (Hope you didn't pay for it...)
A have one of this too. Have you manage to update your phone?
Thanks a lot!
evilinheaven said:
This mean that your phone is a prototype for test purposes, not a retail phone. (Hope you didn't pay for it...)
A have one of this too. Have you manage to update your phone?
Thanks a lot!
Click to expand...
Click to collapse
Hi,
Sorry for the late reply, I didn't check back here recently.
Apparently mine is some kind of retail phone, but with a specially built software version. Since I wanted this phone so badly (and I still believe this it the one phone on the market that suits me best), but I didn't have a chance to go to Europe at the time, I bought this from a store in China that had imported it to there. However, to be able to sell this phone in China they are putting these "specially made" software versions with added Chinese UI language on the phone. Since I couldn't get any useful advise in this forum I later contacted those who sold me this phone and they told me I should be able to put any official 4.0.4 version on it (which would then be upgradable OTA), but also warned me that I could then end up with a sim-locked/net-locked RAZR i. So I didn't pursue this any further. I might try it once I've got my next smartphone, but at the moment I am still very happy with my RAZR i.
Can this be done? I got a Google Play Edition phone and decided I do not like stock Android on this phone. I would like it to be basically a stock developer's edition with Sense and all with working OTAs. Not really familiar with HTC stuff coming from Samsung. My HBOOT is 1.54 and it is S-ON. Can I do what I want?
hjjfffaa said:
Can this be done? I got a Google Play Edition phone and decided I do not like stock Android on this phone. I would like it to be basically a stock developer's edition with Sense and all with working OTAs. Not really familiar with HTC stuff coming from Samsung. My HBOOT is 1.54 and it is S-ON. Can I do what I want?
Click to expand...
Click to collapse
I think you can do that if you get S-Off (use a tool called Rumrunner) and change your CID so you can flash the appropriate RUU. But why stock? The customized ROMs are so much more interesting.
fenstre said:
I think you can do that if you get S-Off (use a tool called Rumrunner) and change your CID so you can flash the appropriate RUU. But why stock? The customized ROMs are so much more interesting.
Click to expand...
Click to collapse
So if I S-Off can I S-On? I think I read somewhere that was required for OTAs to work. I want stock just for the reliability and hassle free nature of it.
hjjfffaa said:
So if I S-Off can I S-On? I think I read somewhere that was required for OTAs to work. I want stock just for the reliability and hassle free nature of it.
Click to expand...
Click to collapse
Oh, I don't know about that. The rumrunner forum post said they don't really know what happens if you S-On after S-Offing, and that you might not be able to S-Off again. I wouldn't chance it.
fenstre said:
Oh, I don't know about that. The rumrunner forum post said they don't really know what happens if you S-On after S-Offing, and that you might not be able to S-Off again. I wouldn't chance it.
Click to expand...
Click to collapse
But I can downgrade to 1.44 and that would allow me to S-On and get OTA updates right? Or am I totally wrong?
Okay so I've unlocked the bootloader, S-OFF'd, changed to superCID, relocked and tried to run the RUU.exe. I keep getting Error 155: UNKNOWN ERROR. Not sure what to do here. I've also tried using the CID BS_US001 and also some combinations involving an unlocked bootloader. All the same error.
hjjfffaa said:
Okay so I've unlocked the bootloader, S-OFF'd, changed to superCID, relocked and tried to run the RUU.exe. I keep getting Error 155: UNKNOWN ERROR. Not sure what to do here. I've also tried using the CID BS_US001 and also some combinations involving an unlocked bootloader. All the same error.
Click to expand...
Click to collapse
You have S-off which is good. I'm going to ask you to use the BS_US001 CID. Try downloading the 1.29.1540.17 zip from HTC Dev. Do a fastboot oem rebootRUU and flash the zip from there. It should prompt you to do this twice.
Sent from my HTC One using XDA Premium 4 mobile app
Okay I have changed back to the BS_US001 CID, bootloader is still re-locked. I am downloading the 1.29.1540.17.zip right now, it'll be done in 50 minutes.
hjjfffaa said:
Okay I have changed back to the BS_US001 CID, bootloader is still re-locked. I am downloading the 1.29.1540.17.zip right now, it'll be done in 50 minutes.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2497712
You can follow that thread if you want to set the phone to locked.
I'm sorry I forgot about the 4.3 zip, use that one if you want to go straight to 4.3. Again, my apologies
Sent from my HTC One
I don't care if it says re-locked (so long as it functions how it should), I just want my Sense ROM. I already have the 4.3 Dev Edition zip, should I try flashing it with fastboot?
I tried flashing the 3.22.1540.1 zip and got this problem, which doesn't seem consistent with the one guide I've seen for this process.
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot flash
zip PN07IMG_M7_UL_JB43_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1133421 KB)...
OKAY [ 53.663s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (status read failed (Too many links))
finished. total time: 60.625s
Click to expand...
Click to collapse
Try 'fastboot erase cache' and 'fastboot reboot-bootloader' before you 'fastboot oem rebootruu' and then run the fastboot flash zip filename.zip'
Sent from my HTC One
The results:
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot erase
cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.065s]
finished. total time: 0.065s
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot reboo
t-bootloader
rebooting into bootloader...
OKAY [ 0.037s]
finished. total time: 0.038s
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot oem r
ebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.049s]
finished. total time: 0.050s
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot flash
zip PN07IMG_M7_UL_JB43_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1133421 KB)...
OKAY [ 53.359s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (status read failed (Too many links))
finished. total time: 60.318s
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>
Click to expand...
Click to collapse
Could this be a result of the 1.54 bootloader?
hjjfffaa said:
The results:
Could this be a result of the 1.54 bootloader?
Click to expand...
Click to collapse
Can you take an image of your bootloader for me real quick
gusto5 said:
Can you take an image of your bootloader for me real quick
Click to expand...
Click to collapse
Here you go.
hjjfffaa said:
Here you go.
Click to expand...
Click to collapse
As far as I can tell you have met all the criteria for running the RUU, I'm not sure why you're running into this. My last suggestion is to try a different USB port. Hopefully someone else will chime in on this if that (which i don't imagine will) does anything at all.
gusto5 said:
As far as I can tell you have met all the criteria for running the RUU, I'm not sure why you're running into this. My last suggestion is to try a different USB port. Hopefully someone else will chime in on this if that (which i don't imagine will) does anything at all.
Click to expand...
Click to collapse
Thanks for all your help. Trying a different USB port.
You were right, it did nothing.
hjjfffaa said:
The results:
Could this be a result of the 1.54 bootloader?
Click to expand...
Click to collapse
You may be right. Let's have you downgrade the Bootloader to 1.44 and then try running the RUU again.
Just remember that you already have the right MID and CID. CID you changed yourself, MID already matches as the Google Play Edition shares the same MID as the Developer edition (and a few other North American HTC Ones).
Here are the (real) results:
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot oem r
ebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.049s]
finished. total time: 0.049s
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot flash
zip hbootRUU.zip
target reported max download size of 1526722560 bytes
sending 'zip' (508 KB)...
OKAY [ 0.250s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 0.516s
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>
Click to expand...
Click to collapse
In 'android-info' I modified to the MID to match mine. Do I need to add the CID to this in order to have it work? I noticed there was not BS_US001 CID listed inside.
hjjfffaa said:
Here are the results:
In 'android-info' I modified to the MID to match mine. Do I need to add the CID to this in order to have it work? I noticed there was not BS_US001 CID listed inside.
Click to expand...
Click to collapse
For this part, and the ruu cid 11111111 might be more effective.
Sent from my Nexus 7 using XDA Premium 4 mobile app
gusto5 said:
For this part, and the ruu cid 11111111 might be more effective.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
All right, should I add it to the android-text file though?
Added the links back since I discovered my issues were related to the firmware not being compatible with the ROM I had been using. I RUU'd to start fresh, did all the updates to current T-Mobile software, then installed twrp followed by a ROM and initially had the same communication issues however, switched to a different ROM and problems solved. Things running smooth, so firmware is good.
Radio 01.01_U11440801_97.04.60111G_F from 3.39.531.7
1 of 2 3.39.531.7 Firmware
2 of 2 3.39.531.7 Firmware
Flashable?
HTC One M9
Fw is flashable, but radio I always stuff inside whatever new fw I plan to use then flash.
We used to be able to flash just the radio.img but I haven't tried in so long I'm not sure you still can.
Camboozle said:
LIke it says, here is the latest t-mob fw and radio
5.29.1700.18 firmware
https://www.dropbox.com/s/iizh3ntbd5gq6y0/5.29.1700.18 firmware.zip?dl=0
baseband 01.01_U11440801_97.04.60111G_F
https://www.dropbox.com/s/f54j6hlqqsq4a25/5.29.1700.18 radio.img?dl=0
Big thanks to Tachi91 for uploading the OTA from which the files were extracted!!!
Click to expand...
Click to collapse
Links not working. Also, how exactly do you flash these?
delete
delete
Not like it matters now as it was removed, but are you sure those were for the m9? Not m8?
Sent from my SM-N920T using Tapatalk
delete
Camboozle said:
Added the links back since I discovered my issues were related to the firmware not being compatible with the ROM I had been using. I RUU'd to start fresh, did all the updates to current T-Mobile software, then installed twrp followed by a ROM and initially had the same communication issues however, switched to a different ROM and problems solved. Things running smooth, so firmware is good.
Radio 01.01_U11440801_97.04.60111G_F from 3.39.531.7
1 of 2 3.39.531.7 Firmware
2 of 2 3.39.531.7 Firmware
Click to expand...
Click to collapse
Firmware works great. I modified mine for no red text and to install TWRP too. Modified to install with any model and CID too. Just gotta remember to fix the file names so fast boot can read the zip files. Other then that everything installed smoothly. :laugh::good: Heres a link to my modified files if anyone is interested. Thanks again Camboozle. :good:
Just for an FYI your first boot may take a while. It will also need to do the rebuild the android database thing too, only about 195 files if your on viper Rom.
Firmware 3.39.531+No Red Text ABOOT+TWRP 3.0.2-0
http://www.mediafire.com/download/s1cgxc55jp8md7u/3.39.531_firmware_No_Red_Text_And_TWRP.zip
MD5
4684cfc5efbee86cf7fbefa0643f4d58
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zip 1_of_2_firmware_3.39.531.7_No_Red_Text_And_TWRP.zip
target reported max download size of 800000000 bytes
sending 'zip' (41772 KB)...
OKAY [ 3.218s]
writing 'zip'...
(bootloader) HOSD CL#591203
(bootloader) Perform pre-update
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 5.491s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zip 1_of_2_firmware_3.39.531.7_No_Red_Text_And_TWRP.zip
target reported max download size of 800000000 bytes
sending 'zip' (41772 KB)...
OKAY [ 3.104s]
writing 'zip'...
(bootloader) HOSD CL#591203
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) Update zip file OK
(bootloader) [email protected]
OKAY [ 5.532s]
finished. total time: 8.640s
C:\Program Files (x86)\Android\android-sdk\platform-tools>
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zip 2_of_2_firmware_3.39.531.7_No_Red_Text_And_TWRP.zip
target reported max download size of 800000000 bytes
sending 'zip' (75885 KB)...
OKAY [ 4.889s]
writing 'zip'...
(bootloader) HOSD CL#591203
(bootloader) GPT is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 6.154s
C:\Program Files (x86)\Android\android-sdk\platform-tools>
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zip 2_of_2_firmware_3.39.531.7_No_Red_Text_And_TWRP.zip
target reported max download size of 800000000 bytes
sending 'zip' (75885 KB)...
OKAY [ 4.915s]
writing 'zip'...
(bootloader) HOSD CL#690290
(bootloader) GPT is up-to-dated. [17408]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) Update zip file OK
(bootloader) [email protected]
OKAY [ 6.391s]
finished. total time: 11.311s
Click to expand...
Click to collapse
If you don't mind me asking, which ROM wasn't playing nice with the new updates?
ineffablepanda said:
If you don't mind me asking, which ROM wasn't playing nice with the new updates?
Click to expand...
Click to collapse
MaximusHD 7.1.0 is the rom I had lots of issues with. It won't let your sim/data connect at the moment - normally best battery life and lightening fast response of ui, they tend to have best benchmarks so its my new fav rom, but going to have to wait for v7.2
LeeDroid works but with some small bugs and hesitations so in need of refinement but when they get it right they get it very right
ViperOneM9 4.3.0 is what I'm using right now. It works beautifully and is just shy of the benchmarks of MaximusHD and feels just as fast. Even though I know they make great stuff I rarely run their roms as I always get lost in all their options, especially the sidebar which I generally disable on install
ineffablepanda said:
If you don't mind me asking, which ROM wasn't playing nice with the new updates?
Click to expand...
Click to collapse
If it was viper rom then it would have been version 4.2.1. Download the new version 4.3.0 and flash that, the new version also had the T-Mobile files included this time too. I did a dirty flash on my phone and everything works fine for me. Wi-Fi calling works for me but voice over LTE is hit or miss lol
^^^ what he said basically lol.
Well seems it has worked but no WiFi calling. will try a ROM reflash.
cknuth said:
Well seems it has worked but no WiFi calling. will try a ROM reflash.
Click to expand...
Click to collapse
I had to reflash viper after updating my firmware. Now my Wi-Fi calling works. That should take care of it. ?
sniper849 said:
I had to reflash viper after updating my firmware. Now my Wi-Fi calling works. That should take care of it.
Click to expand...
Click to collapse
Did you have to wipe when you flash? or did you dirty flash it?
cknuth said:
Did you have to wipe when you flash? or did you dirty flash it?
Click to expand...
Click to collapse
I did a dirty flash. I haven't really noticed any issues. I was on 4.2.1 and dirty flashed 4.3.0.
sniper849 said:
Firmware works great. I modified mine for no red text and to install TWRP too. Modified to install with any model and CID too. Just gotta remember to fix the file names so fast boot can read the zip files. Other then that everything installed smoothly. :laugh::good: Heres a link to my modified files if anyone is interested. Thanks again Camboozle. :good:
Just for an FYI your first boot may take a while. It will also need to do the rebuild the android database thing too, only about 195 files if your on viper Rom.
Firmware 3.39.531.7, With No Red Text A-Boot with TWRP Recovery included. Part 1.
http://www.mediafire.com/download/b..._firmware_3.39.531.7_No_Red_Text_And_TWRP.zip
Firmware 3.39.531.7, With No Red Text A-Boot with TWRP Recovery included. Part 2.
http://www.mediafire.com/download/8..._firmware_3.39.531.7_No_Red_Text_And_TWRP.zip
Click to expand...
Click to collapse
This may be a dumb question but does this include the new radio too or do I need to do something to flash that as well
darock159 said:
This may be a dumb question but does this include the new radio too or do I need to do something to flash that as well
Click to expand...
Click to collapse
It includes the new radio. ?
Im working on getting a better firmware package for everyone to use with the updated TWRP recovery also. Just flashed the one ive been working on to my phone and if all go's well ill upload it and update my links. oh and it will only be a single package too.
If your looking for the stock rom go check out the thread by kc6wke. there are links for the stock MM rom and the full firmware package.
http://forum.xda-developers.com/tmobile-one-m9/development/rom-t-mobile-m9-stock-deodex-6-0-t3324137
I was able to flash both firmware updates and the new official 6.0 Tmo rom. The only problem I've run into is with the now on tap feature. I'm unable to enable or disable the feature under the settings, it's grayed out.
Hi, im having a unlocked xt1058, i just upgraded the phone to last 5.1 OTA, unlocked the BL and installed CM13 without problems at all, now after some researching ive noticed that my gps is bugged and im needing to get back to stock to make it work in CM13, everything cool at this point, just downloaded the latest firmware for my device on my cid and there's where problems started.
I've just downloaded XT1058_GHOST_RETAR_5.1_LPA23.12-15_cid12_CFC.xml from march of 2016, uncompress it on a fastboot folder that ive created for flashing purposes and started the flashing process.
First command i put into the fastboot is fastboot flash partition gpt.bin and the phone BL and fastboot returned to me errors.
From phone:
getvar has-slotartition
getvar partition-typeartition
getvar max-download-size
downloading 32768 bytes
done
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
From cmd:
target reported max download size of 805306368 bytes
sending 'partition' (32 KB)...
OKAY [ 0.247s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.089s
I dont want to start test things without knowing it at all, is the first time im flashing a firmware to my moto x, all the other things ive done was under OTA automation, now im BL unlocked and i think i can mess the phone, can u help me please? ^^
santi1993 said:
Hi, im having a unlocked xt1058, i just upgraded the phone to last 5.1 OTA, unlocked the BL and installed CM13 without problems at all, now after some researching ive noticed that my gps is bugged and im needing to get back to stock to make it work in CM13, everything cool at this point, just downloaded the latest firmware for my device on my cid and there's where problems started.
I've just downloaded XT1058_GHOST_RETAR_5.1_LPA23.12-15_cid12_CFC.xml from march of 2016, uncompress it on a fastboot folder that ive created for flashing purposes and started the flashing process.
First command i put into the fastboot is fastboot flash partition gpt.bin and the phone BL and fastboot returned to me errors.
From phone:
getvar has-slotartition
getvar partition-typeartition
getvar max-download-size
downloading 32768 bytes
done
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
From cmd:
target reported max download size of 805306368 bytes
sending 'partition' (32 KB)...
OKAY [ 0.247s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.089s
I dont want to start test things without knowing it at all, is the first time im flashing a firmware to my moto x, all the other things ive done was under OTA automation, now im BL unlocked and i think i can mess the phone, can u help me please? ^^
Click to expand...
Click to collapse
the only things u need to do to fully working ur gps is
1: fastboot erase modem1
2:fastboot erase modem2 and all fine brou
---------- Post added at 01:09 PM ---------- Previous post was at 01:01 PM ----------
santi1993 said:
Hi, im having a unlocked xt1058, i just upgraded the phone to last 5.1 OTA, unlocked the BL and installed CM13 without problems at all, now after some researching ive noticed that my gps is bugged and im needing to get back to stock to make it work in CM13, everything cool at this point, just downloaded the latest firmware for my device on my cid and there's where problems started.
I've just downloaded XT1058_GHOST_RETAR_5.1_LPA23.12-15_cid12_CFC.xml from march of 2016, uncompress it on a fastboot folder that ive created for flashing purposes and started the flashing process.
First command i put into the fastboot is fastboot flash partition gpt.bin and the phone BL and fastboot returned to me errors.
From phone:
getvar has-slotartition
getvar partition-typeartition
getvar max-download-size
downloading 32768 bytes
done
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
From cmd:
target reported max download size of 805306368 bytes
sending 'partition' (32 KB)...
OKAY [ 0.247s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.089s
I dont want to start test things without knowing it at all, is the first time im flashing a firmware to my moto x, all the other things ive done was under OTA automation, now im BL unlocked and i think i can mess the phone, can u help me please? ^^
Click to expand...
Click to collapse
try this rom https://www.androidfilehost.com/?fid=24052804347831649 and all would be fine
omy4069 said:
the only things u need to do to fully working ur gps is
1: fastboot erase modem1
2:fastboot erase modem2 and all fine brou
---------- Post added at 01:09 PM ---------- Previous post was at 01:01 PM ----------
try this rom https://www.androidfilehost.com/?fid=24052804347831649 and all would be fine
Click to expand...
Click to collapse
Hi @omy4069, thanks for reply!
My problem is that i cannot reflash stock firmware due gpt.bin error, can u gimme some help in that? i was thinking that i maybe can flash the rest of the modules via fastboot but i dont want to brick my phone cuz of flashing a boot.img on a no compatible gpt.bin or somewhat, im cid12.
Thanks afterwards! i want to go back to stock to test some things and being safe of a possible brick testing further roms or recoveries.
omy4069 said:
the only things u need to do to fully working ur gps is
1: fastboot erase modem1
2:fastboot erase modem2 and all fine brou
---------- Post added at 01:09 PM ---------- Previous post was at 01:01 PM ----------
try this rom https://www.androidfilehost.com/?fid=24052804347831649 and all would be fine
Click to expand...
Click to collapse
Hi, the command is fastboot erase modemst1 and modemst2, the ones u guided are wrong.
And the rom is based on CM, im trying to get into stock, ty for the idea, ill try a AOSP rom to try get locked, but my problem atm is another, i cant flash stock firmware.
i having same issue
Downgrade Security version update gpt_main version failed preflash validation failed for GPT
any solution ?
Gsm UK said:
i having same issue
Downgrade Security version update gpt_main version failed preflash validation failed for GPT
any solution ?
Click to expand...
Click to collapse
Nope, atm i resolved flashing stock rom with TWRP and testing modem behaviour without changing boot or gpt.bin
Enviado desde mi Moto X mediante Tapatalk
santi1993 said:
Nope, atm i resolved flashing stock rom with TWRP and testing modem behaviour without changing boot or gpt.bin
Enviado desde mi Moto X mediante Tapatalk
Click to expand...
Click to collapse
the question is how to flash twrp once i flash twrp
i get this error
Code:
C:\D Drive\Software\Motorola\Motorola>fastboot flash recovery openrecovery-twrp-2.8.0.1-ghost.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (8376 KB)...
OKAY [ 0.766s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.181s
phone screen error
invalid image size for partition recovery
Gsm UK said:
the question is how to flash twrp once i flash twrp
i get this error
Code:
C:\D Drive\Software\Motorola\Motorola>fastboot flash recovery openrecovery-twrp-2.8.0.1-ghost.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (8376 KB)...
OKAY [ 0.766s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.181s
phone screen error
invalid image size for partition recovery
Click to expand...
Click to collapse
In which bootloader are u? i mean any of the KK BL or LP BL?
Which is ur variant? Open 3G/4G or Carrier locked?
I can tell u how i get my recovery flashed but we need to share the same procedure, cheers from Argentina.
Gsm UK said:
the question is how to flash twrp once i flash twrp
i get this error
Code:
C:\D Drive\Software\Motorola\Motorola>fastboot flash recovery openrecovery-twrp-2.8.0.1-ghost.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (8376 KB)...
OKAY [ 0.766s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.181s
phone screen error
invalid image size for partition recovery
Click to expand...
Click to collapse
In which bootloader are u? i mean any of the KK BL or LP BL?
Which is ur variant? Open 3G/4G or Carrier locked?
I can tell u how i get my recovery flashed but we need to share the same procedure, cheers from Argentina.
santi1993 said:
In which bootloader are u? i mean any of the KK BL or LP BL?
Which is ur variant? Open 3G/4G or Carrier locked?
I can tell u how i get my recovery flashed but we need to share the same procedure, cheers from Argentina.
Click to expand...
Click to collapse
i really appreciate for your help bro.
Carrier is Verizon XT-1060
and i have try to unlock the boot-loader from moto web getting this message :
your device does not qualify for bootloader unlocking
and i have attach the picture please check the bl version and its on developer version
can u please tell me the procedure ?
Details are here
Code:
fastboot getvar all
(bootloader) version-bootloader: 30BE
(bootloader) version: 0.5
(bootloader) cpu: MSM8960 Pro CS
(bootloader) ram: 2048MB Hynix S4 SDRAM DIE=4Gb
(bootloader) emmc: 32GB Toshiba REV=06 PRV=11 TYPE=17
(bootloader) product: ghost
(bootloader) revision-hardware: 0x8300
(bootloader) radio: 0x2
(bootloader) secure: yes
(bootloader) mid: 026b
(bootloader) serialno: T062005AKG
(bootloader) qe: qe 0/0
(bootloader) unlocked: no
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 805306368
(bootloader) uid: FB1B5A050C000100000000000000
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) sku: 000000000000000
(bootloader) cid: 0xff
(bootloader) iccid: 89148000001024231192
(bootloader) date: 01-01-1970
(bootloader) cust_md5: 83AE0624738C7F5F22FB58BAD66C9981
(bootloader) reason: Key pressed
(bootloader) ro.build.date: Thu Aug 29 12:58:18 CDT 2013
(bootloader) ro.build.id: 13.9.0Q2.X-118-GHOST_GNPO-20
(bootloader) ro.build.tags: release-keys
(bootloader) ro.build.type: userdebug
(bootloader) ro.build.user: hudsoncm
(bootloader) ro.build.version.codename: REL
(bootloader) ro.build.version.incremental: 25
(bootloader) ro.build.version.release: 4.2.2
(bootloader) ro.mot.build.customerid: verizon
(bootloader) ro.product.name: factory_ghost
(bootloader) ro.build.fingerprint[0]: motorola/factory_ghost/ghost:4.2
(bootloader) ro.build.fingerprint[1]: .2/13.9.0Q2.X-118-GHOST_GNPO-20/
(bootloader) ro.build.fingerprint[2]: 25:userdebug/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.164.55.2.ghost_veri
(bootloader) ro.build.version.full[1]: zon.Verizon.en.US
(bootloader) kernel.version[0]: Linux version 3.4.42-xline-eng-g
(bootloader) kernel.version[1]: fd1a699-00143-g19096f2 (hudsoncm
(bootloader) kernel.version[2]: @il93lnxdroid50) (gcc version 4.
(bootloader) kernel.version[3]: 6.x-google 20120106 (prerelease)
(bootloader) kernel.version[4]: (GCC) ) #1 SMP PREEMPT Thu Aug
(bootloader) kernel.version[5]: 29 13:33:33 CDT 2013
Gsm UK said:
i really appreciate for your help bro.
Carrier is Verizon XT-1060
and i have try to unlock the boot-loader from moto web getting this message :
your device does not qualify for bootloader unlocking
and i have attach the picture please check the bl version and its on developer version
Click to expand...
Click to collapse
your bootloader is locked. you can not flash custom recovery with bootloader locked.
if it is verizon, it cannot be unlocked in any way except you have kitkat 4.4.2. then sunshine app may unlock your bootloader. they charge around 25$. google it.
---------- Post added at 01:15 PM ---------- Previous post was at 01:11 PM ----------
santi1993 said:
Nope, atm i resolved flashing stock rom with TWRP and testing modem behaviour without changing boot or gpt.bin
Enviado desde mi Moto X mediante Tapatalk
Click to expand...
Click to collapse
yes. old baseband is doing speaker phone/call problems on marshmallow based custom roms.
flash ATT_XT1058_5.1.0_LPAS23.12-21.7-1_cid1_CFC.xml.zip from following link and it will resolve your issue.
https://yadi.sk/d/MCliEyCPfj7ZZ/MOTO.X1/XT1058/ATT
forbourne said:
your bootloader is locked. you can not flash custom recovery with bootloader locked.
if it is verizon, it cannot be unlocked in any way except you have kitkat 4.4.2. then sunshine app may unlock your bootloader. they charge around 25$. google it.
---------- Post added at 01:15 PM ---------- Previous post was at 01:11 PM ----------
yes. old baseband is doing speaker phone/call problems on marshmallow based custom roms.
flash ATT_XT1058_5.1.0_LPAS23.12-21.7-1_cid1_CFC.xml.zip from following link and it will resolve your issue.
https://yadi.sk/d/MCliEyCPfj7ZZ/MOTO.X1/XT1058/ATT
Click to expand...
Click to collapse
i have 4.2.2 developer version so is there anyway to unlock the bootloader without sunshine ?
Gsm UK said:
i have 4.2.2 developer version so is there anyway to unlock the bootloader without sunshine ?
Click to expand...
Click to collapse
if it is developer edition then it may be already unlocked or can easily be unlocked from motorola. check your device status by going into bootloader.
power down your phone and power it up by holding both volume keys.
forbourne said:
if it is developer edition then it may be already unlocked or can easily be unlocked from motorola. check your device status by going into bootloader.
power down your phone and power it up by holding both volume keys.
Click to expand...
Click to collapse
Phone boot-loader is locked and it cant be unlock via motorola web already try
forbourne said:
your bootloader is locked. you can not flash custom recovery with bootloader locked.
if it is verizon, it cannot be unlocked in any way except you have kitkat 4.4.2. then sunshine app may unlock your bootloader. they charge around 25$. google it.
---------- Post added at 01:15 PM ---------- Previous post was at 01:11 PM ----------
yes. old baseband is doing speaker phone/call problems on marshmallow based custom roms.
flash ATT_XT1058_5.1.0_LPAS23.12-21.7-1_cid1_CFC.xml.zip from following link and it will resolve your issue.
https://yadi.sk/d/MCliEyCPfj7ZZ/MOTO.X1/XT1058/ATT
Click to expand...
Click to collapse
i cant flash any 5.1 firmware cuz my phone is updated via OTA from the last 5.1 gpt.bin, im at 30.BE (sha-34b7ccb from april 22 2015) my device is unlocked but i cannot get any cid12 firmware compatible with my gpt.bin and im having some modem issues, im really in a closed street way, im loving my phone but i cannot flash any firmware on it :S
if your boot loader is already on 30.BE then you must have also flashed updated modem as well. so it shouldn't be modem issue any more.
try AICP 11.0 rom for moto x, if audio is working fine on this rom then it means it is rom related bugs and not your modem issue.
thanks
Gsm UK said:
i really appreciate for your help bro.
Carrier is Verizon XT-1060
and i have try to unlock the boot-loader from moto web getting this message :
your device does not qualify for bootloader unlocking
and i have attach the picture please check the bl version and its on developer version
Click to expand...
Click to collapse
there is a way to unlock the bootloader but it has to be 4.4.4 or lower
kbdaking said:
there is a way to unlock the bootloader but it has to be 4.4.4 or lower
Click to expand...
Click to collapse
no i had around 1500 phones here VERIZON XT-1060 all 4.2.2 i have unlock the boot-loader with sigma box without any problem
but 30 , to 40 phone which is stuck now .. there is no solution to unlock the boot-loader except sunshine i think
Hei
Can somebody help me find correct firmware for me? I want to relock my phone and be able to get updates (reteu) and get back 4g + voLTE.
I was able to relock with SANDERS_NPSS26.116-26-18_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip but i dont think i get updates and 4g + volte dont work.
I have only united states as radio
ZorgX said:
Hei
Can somebody help me find correct firmware for me? I want to relock my phone and be able to get updates (reteu) and get back 4g + voLTE.
I was able to relock with SANDERS_NPSS26.116-26-18_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip but i dont think i get updates and 4g + volte dont work.
I have only united states as radio
Click to expand...
Click to collapse
Here description says its April's patch for European variant..
https://androidfilehost.com/?fid=962339331458990371
E:\moto g5s pluss\platform-tools>fastboot flash boot boot.img
(bootloader) has-slot:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.480s]
Writing 'boot' (bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
Finished. Total time: 0.690s
ZorgX said:
E:\moto g5s pluss\platform-tools>fastboot flash boot boot.img
(bootloader) has-slot:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.480s]
Writing 'boot' (bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
Finished. Total time: 0.690s
Click to expand...
Click to collapse
Since you have updated to june's patch, it is not possible to downgrade on locked bootloader..
Also you can not downgrade bootloader and gpt even on unlocked bootloader.. if you unlock again and flash other partitions, it can be troublesome when updated by OTA as bootloader and gpt will be from newer version..
Here possible safe solution is to flash that firmware, and
wait for future stock firmware for European variant...
ZorgX said:
Hei
Can somebody help me find correct firmware for me? I want to relock my phone and be able to get updates (reteu) and get back 4g + voLTE.
I was able to relock with SANDERS_NPSS26.116-26-18_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip but i dont think i get updates and 4g + volte dont work.
I have only united states as radio
Click to expand...
Click to collapse
u flashed modem erasing commands..... 26-18 is latest for reteu and correct so no worry
if u need help with volte and 4g pm me