I read that the Cricket Galaxy S5 (G900AZ) is a rebranded AT&T S5 (G900A). Has anyone tried ODIN flashing the stock AT&T rom on the Cricket model?
For instance, i have read people flashing the Tmobile S5 stock rom on the MetroPCS version and it works fine even though the model numbers are slightly different. It changes the phone into the Tmobile version.
spydc said:
I read that the Cricket Galaxy S5 (G900AZ) is a rebranded AT&T S5 (G900A). Has anyone tried ODIN flashing the stock AT&T rom on the Cricket model?
For instance, i have read people flashing the Tmobile S5 stock rom on the MetroPCS version and it works fine even though the model numbers are slightly different. It changes the phone into the Tmobile version.
Click to expand...
Click to collapse
Did you ever get an answer to this?
NO, but....
The Cricket S5 is indeed a rebranded AT&T model. I have both of those models including a LA G900M (TTT.) Major difference is nowhere near as much bloatware, and most importantly an unlocked bootloader. The only advantage would be upgrading to MM if you want stock, since the January update still has it on LP. You're better off trying a LA stock ROM though (I say this because they use the same custom recovery) But cutom ROM's can take you there as far as 7.1 Nougat right now.
I just recently rooted my Cricket model with CF Auto-root (klteaio), flashed the latest TWRP (klte) recovery and installed Xposed Framework (by dkcldark... wanam custom won't work.) Had a little of lag first couple of days, but I guess that's to be expected. Hope this helps in some way.
gello924 said:
The Cricket S5 is indeed a rebranded AT&T model. I have both of those models including a LA G900M (TTT.) Major difference is nowhere near as much bloatware, and most importantly an unlocked bootloader. The only advantage would be upgrading to MM if you want stock, since the January update still has it on LP. You're better off trying a LA stock ROM though (I say this because they use the same custom recovery) But cutom ROM's can take you there as far as 7.1 Nougat right now.
I just recently rooted my Cricket model with CF Auto-root (klteaio), flashed the latest TWRP (klte) recovery and installed Xposed Framework (by dkcldark... wanam custom won't work.) Had a little of lag first couple of days, but I guess that's to be expected. Hope this helps in some way.
Click to expand...
Click to collapse
Wait, it has an unlocked bootloader on the rebranded G900A?
Vesnyx said:
Wait, it has an unlocked bootloader on the rebranded G900A?
Click to expand...
Click to collapse
This gives me an idea.... What if we use flashfire to flash G900AZ firmware on the G900A (including the UNLOCKED BOOTLOADER)
Sent from my Amazon KFGIWI using XDA Labs
AptLogic said:
This gives me an idea.... What if we use flashfire to flash G900AZ firmware on the G900A (including the UNLOCKED BOOTLOADER)
Click to expand...
Click to collapse
You could always try it. I don't know exactly how well it will work.
You would have to be rooted FIRST on the G900A in order for FlashFire to work. If i remember correctly anything already on LP can't be rooted or downgraded back to KK.
---------- Post added at 11:30 PM ---------- Previous post was at 11:12 PM ----------
Y'know what would be really nice???: Seeing that android updates are only good for 2yrs on a particular model after its initial released, and the given the fact that most carries plans are only 2yrs; wouldn't it be nice if (for sake of argument in THIS thread) AT&T would release a firmware for their phones, that would unlock the bootloader and possibly SIM unlock the phone as well. I mean after 2yrs the device is paid for and quite frankly no longer belongs to them. I hate the idea of being forced to either get a new device once my plan has expired or use MY phone with the carrier its branded under. Of course it probably has everything to with them making their money from those of us who can't do without having a new device every year.
So I can pull a copy of the G900AZ engineering firmware I found, but I doubt we'll be able to flash it. What is was thinking is that we use beaups CID changer to make our device into one similar to the cricket wireless one. Since it is essentially a dev edition of our phone.
You cant just flash a unlocked bootloader to a locked bootloader phone. A specific explout must be developed to defeat the bootloader. Simply shashing over it will never work.
The G900AZ is just a rebranded version of the G900A though. I don't think there are any glaring differences like there would be from G900T to G900A. If the aboot does flash then it would be a simple unlock.
@NavSad @AptLogic
If you wanna try this, here's a link to their firmwares:
https://www.sammobile.com/firmwares/database/SM-G900AZ/
You'd most likely need to extract the correct files and be on the correct versions before flashing these.
Apparently, something similar happened with the T-Mobile Galaxy S6, where the MetroPCS firmware was flashed on the T-mobile firmware.
Vesnyx said:
The G900AZ is just a rebranded version of the G900A though. I don't think there are any glaring differences like there would be from G900T to G900A. If the aboot does flash then it would be a simple unlock.
@NavSad @AptLogic
If you wanna try this, here's a link to their firmwares:
https://www.sammobile.com/firmwares/database/SM-G900AZ/
You'd most likely need to extract the correct files and be on the correct versions before flashing these.
Apparently, something similar happened with the T-Mobile Galaxy S6, where the MetroPCS firmware was flashed on the T-mobile firmware.
Click to expand...
Click to collapse
I tried ODINing the G900AZTUU3BOG3 firmware, and it immediately returned a SECURE CHECK FAIL: aboot
I'll try using FlashFireon it tomorrow during my batch of tests.
AptLogic said:
I tried ODINing the G900AZTUU3BOG3 firmware, and it immediately returned a SECURE CHECK FAIL: aboot
I'll try using FlashFireon it tomorrow during my batch of tests.
Click to expand...
Click to collapse
Just so I can get an idea of what everyone's fuse values are, do you mind telling me what you see after RP SWREV in Download Mode.
NavSad said:
Just so I can get an idea of what everyone's fuse values are, do you mind telling me what you see after RP SWREV in Download Mode.
Click to expand...
Click to collapse
Mine are S1, T1, R1, A2, P1. I'm on Lollipop 5.0 with with ability to downgrade to NCE.
Also @AptLogic, maybe try through stock recovery, just as a precautionary measure.
P l e a s e do not try this
So I tried using FlashFire to flash the G900AZ firmware and I HARD BRICKED MY PHONE.
If anyone wants to give me advice on how to unbrick it PLEASE DO because I have to put all my development on hold indefinitely until I can unbrick it or buy a new one (which isn't likely because I don't have the cash for that right now).
AptLogic said:
So I tried using FlashFire to flash the G900AZ firmware and I HARD BRICKED MY PHONE.
If anyone wants to give me advice on how to unbrick it PLEASE DO because I have to put all my development on hold indefinitely until I can unbrick it or buy a new one (which isn't likely because I don't have the cash for that right now).
Click to expand...
Click to collapse
Try using a debrick image.
NavSad said:
Try using a debrick image.
Click to expand...
Click to collapse
I can't get the phone to boot, not even into Download Mode
AptLogic said:
I can't get the phone to boot, not even into Download Mode
Click to expand...
Click to collapse
Does it show up as qualcomm qhusb hulk when connected to your pc in device manager?
NavSad said:
Does it show up as qualcomm qhusb hulk when connected to your pc in device manager?
Click to expand...
Click to collapse
I took the battery out of the phone and hooked it up to my computer and its showing up as "RELINK HS-USB QDLoader 9008 (COM14)" in device manager
AptLogic said:
I took the battery out of the phone and hooked it up to my computer and its showing up as "RELINK HS-USB QDLoader 9008 (COM14)" in device manager
Click to expand...
Click to collapse
I would try this method:
Grab a sdcard
Grab a debrick image here:https://www.androidfilehost.com/?fid=457095661767140194
Then put the sdcard in your computer and use Win32 DiskImager to write to the sdcard. After that, put the sdcard in your phone and boot into Download Mode.
If your phone isn't fixable using this method you'd have to try JTAG.
NavSad said:
I would try this method:
Grab a sdcard
Grab a debrick image here:UPLOADING
Then put the sdcard in your computer and use Win32 DiskImager to write to the sdcard. After that, put the sdcard in your phone and boot into Download Mode.
If your phone isn't fixable using this method you'd have to try JTAG.
Click to expand...
Click to collapse
Is the debrick image just the first 200MB of the phone's data?
Related
Hello!
I'm currently stationed in Singapore and bought a Moto X about a month or so ago from eBay. While I am anxiously waiting for my Moto X to receive the 4.4 update, I realised that the system version (after the previous camera update) is 139.12.35.ghost_row.AmericaMovil.en.PR, which I found to be a Latin America version after some searching on the forums and Googling here and there.
I also found this thread, where OP said that they can be flashed over to either the T-Mobile version. Does this continue to work for the 4.4 updates by T-Mobile or AT&T, and would there be anything else required for flashing? (I saw something about flashing new radios and all, but was quite confused by contradicting explanations and suggestions :/)
Thanks in advance!
// EDIT:
To add on after a bit of searching, I realised that I am allowed to unlock my bootloader, despite claims from the original retailer on eBay that the phone came from AT&T (which is notorious, even here, for their stance on bootloader unlocking). What gives?
I got the same Moto X from a buddy yesterday. I did a lot of searching and also discovered the thread about the phone being flashed to t- mobile.
I fooled the steps on another thread titled " Return to stock 100%" out something like that...
I downloaded the correct Att firmware and with the use of RSDLite, I successfully flashed my Moto X to ATT.... it took less than 10 minutes. And as soon as it booted up, I got hit with the "update available" message ( kit Kat)
Sent from my XT1058 using Tapatalk
Thanks for the information!
I've successfully upgraded my phone to the Verizon version (minus all the bloatware that I hastily blasted off), with root and TWRP. So this is what I did, for future reference:
It seems that AmericaMovil versions are not bound by the AT&T's locked bootloader policies, and other Latin America versions are probably free from the restriction too. So I managed to get my hands on the Motorola Fastboot and unlocked my bootloader. TWRP was installed (remember to use 2.6.3.1 and above for 4.4 support), and then flashed the Verizon system dump available here. Root was installed by TWRP.
After getting on the device and setting things up, I rebooted to recovery to remove lots of bloatware (available in /system/app and /system/priv-app). Had to remove some of them through Titanium Backup as the file names were not always indicative that it came from Verizon. I made the extra step of killing the god-awful boot animation that they had by replacing it with this.
And... that concludes my experience with this, I suppose.
I've been looking through a few threads and I am not comfortable enough to flash the T-Mobile rom over my AmericanMovil one yet.
I can't seem to find step by step instructions on how to do this.. Would anyone like to explain it from the ground up?
My understanding
1) unlock bootloader
2) flash a recovery like twrp or cmw
3) flash the rom that is given in the OG post here http://forum.xda-developers.com/showthread.php?t=2477180
4) this should now give us the t-mobile version of things and we should be able to do the standard OTA from there?
[Q] So can this all be done without ever having to root the phone?
alternetconcept said:
I've been looking through a few threads and I am not comfortable enough to flash the T-Mobile rom over my AmericanMovil one yet.
I can't seem to find step by step instructions on how to do this.. Would anyone like to explain it from the ground up?
My understanding
1) unlock bootloader
2) flash a recovery like twrp or cmw
3) flash the rom that is given in the OG post here http://forum.xda-developers.com/showthread.php?t=2477180
4) this should now give us the t-mobile version of things and we should be able to do the standard OTA from there?
[Q] So can this all be done without ever having to root the phone?
Click to expand...
Click to collapse
I'm not too sure whether flashing via TWRP/CMW will allow you to get OTA, unfortunately. Which is why I went straight for the Verizon system dump. But yes, you can change firmware without ever having to root the phone. Heck, I think there's a guide on restoring mentioned by @plmiller0905 below that will allow you to do it without unlocking the bootloader, even.
RagnaParadise said:
I'm not too sure whether flashing via TWRP/CMW will allow you to get OTA, unfortunately. Which is why I went straight for the Verizon system dump. But yes, you can change firmware without ever having to root the phone. Heck, I think there's a guide on restoring mentioned by @plmiller0905 below that will allow you to do it without unlocking the bootloader, even.
Click to expand...
Click to collapse
I believe the bootloader does have to be unlocked in order to flash a different firmware.
Sent from my XT1058 using Tapatalk
RagnaParadise said:
I'm not too sure whether flashing via TWRP/CMW will allow you to get OTA, unfortunately. Which is why I went straight for the Verizon system dump. But yes, you can change firmware without ever having to root the phone. Heck, I think there's a guide on restoring mentioned by @plmiller0905 below that will allow you to do it without unlocking the bootloader, even.
Click to expand...
Click to collapse
Yeah after doing so more reading.. (at least the way I'm willing to do it) is to just unlock my bootloader and then using RSD Lite (Which i still have no idea what that is / where it is) flash an SBF found here (http://sbf.droid-developers.org/ghost_rcica/list.php)
I guess following this video somewhat http://www.youtube.com/watch?v=Fr0JHSAXJDI#t=15
Does that sound right?
Should I flash the TMO_RETAIL_XT1053_4.2.2-13.9.0Q2.X-116-X-17-57_MR1_CFC.xml.zip
Or just jump straight to the 4.4 version TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_CFC.xml.zip
??
As far as I know, the use of RSD Lite doesn't require an unlocked bootloader (at least, that's what it shows in the video you showed me anyway), especially since these are images supposedly signed by Motorola themselves. Let me know if you've found something else?
As for your question on which to flash... I'm not sure, but you'd skip a lot of the hassle if you could flash 4.4 straight, so how about trying that?
RagnaParadise said:
As far as I know, the use of RSD Lite doesn't require an unlocked bootloader (at least, that's what it shows in the video you showed me anyway), especially since these are images supposedly signed by Motorola themselves. Let me know if you've found something else?
As for your question on which to flash... I'm not sure, but you'd skip a lot of the hassle if you could flash 4.4 straight, so how about trying that?
Click to expand...
Click to collapse
Rsdlite is a shell for a flash boot flash supposedly with an XML doing all the steps together. Just makes it easier.
You need unlocked boot loader only to flash an image that doesn't match your current boot loader. So if you have a. At&t phone you can only flash at&t images by rsdlite. But if you unlock your amerimovil phone you can flash any xt1058 image I think. So amerimovil could take say a rogers or at&t or telcel image. Not sure if T-Mobile image will work on a full rsdlite flash as it is an xt1053 image. I think you can flash most of a T-Mobile image by twrp but not by rsdlite not sure
sleepyguy007 said:
Rsdlite is a shell for a flash boot flash supposedly with an XML doing all the steps together. Just makes it easier.
You need unlocked boot loader only to flash an image that doesn't match your current boot loader. So if you have a. At&t phone you can only flash at&t images by rsdlite. But if you unlock your amerimovil phone you can flash any xt1058 image I think. So amerimovil could take say a rogers or at&t or telcel image. Not sure if T-Mobile image will work on a full rsdlite flash as it is an xt1053 image. I think you can flash most of a T-Mobile image by twrp but not by rsdlite not sure
Click to expand...
Click to collapse
So if I flash the at&t image found here (http://sbf.droid-developers.org/ghost_rcica/list.php), would it come pre-loaded with all the bloatware AT&T has even though I'm not using AT&T network?
alternetconcept said:
So if I flash the at&t image found here (http://sbf.droid-developers.org/ghost_rcica/list.php), would it come pre-loaded with all the bloatware AT&T has even though I'm not using AT&T network?
Click to expand...
Click to collapse
yes of course. think about it like if you took a dell windows 7 install CD , and put it on an HP. all the dell customizations would still be there.
obviously since you have unlocked bootloader, once you do the RSDlite you can always flash twrp, and superuser, and delete all that stuff. but then you wouldn't get updates again. i dont think the at&t image is really THAT bad. though i've heard the rogers one is better (though maybe not 4.4 yet)
sleepyguy007 said:
yes of course. think about it like if you took a dell windows 7 install CD , and put it on an HP. all the dell customizations would still be there.
obviously since you have unlocked bootloader, once you do the RSDlite you can always flash twrp, and superuser, and delete all that stuff. but then you wouldn't get updates again. i dont think the at&t image is really THAT bad. though i've heard the rogers one is better (though maybe not 4.4 yet)
Click to expand...
Click to collapse
Yeah unfortunately that's what I thought. Hence why I would of liked to flash the t-mobile image but I'm going to hold off until someone that is a bit more adb savvy then myself tries it out. I wouldn't know what to do if I ended up soft bricking my phone
Well it didn't take long to try it out myself...
It worked out!
I used this thread here http://forum.xda-developers.com/showthread.php?t=2446515
I downloaded the Tmobile 4.4 Image and used RSD.
All you have to do is unlock your BL. (Note: I was completely bone stock with NO root and NO special recovery like CMW or TWRP)
Have all the proper drivers installed, enable USB debugging in developer settings on the phone
Go into Fastboot on the phone
Plug in the phone and just follow the video
I do not take any responsibitliy if you brick your phone. It is fairly easy process and took only a few mins.
Hope this helps!
- deleted because I was sleepy enough not to notice that replies were done on the next page -_- -
alternetconcept said:
I've been looking through a few threads and I am not comfortable enough to flash the T-Mobile rom over my AmericanMovil one yet.
I can't seem to find step by step instructions on how to do this.. Would anyone like to explain it from the ground up?
My understanding
1) unlock bootloader
2) flash a recovery like twrp or cmw
3) flash the rom that is given in the OG post here http://forum.xda-developers.com/showthread.php?t=2477180
4) this should now give us the t-mobile version of things and we should be able to do the standard OTA from there?
[Q] So can this all be done without ever having to root the phone?
Click to expand...
Click to collapse
I've been doing some research on this since yesterday and I've been hesitant on doing it. I saw in your last post that you successfully flashed the TMO 4.4 ROM on your AmericaMovil phone, so I have a few questions for you before I go ahead and do the same:
1. Can you please confirm that your model is XT1058 and not XT1053?
2. Does the TMO ROM have the TMO boot logo and any TMO bloatware?
3. Does the TMO ROM have the Tethering & portable hotspot option under Settings > More?
4. Does the TMO ROM have the Mass Storage option under Settings > Storage > | > USB computer connection?
5. Have you been having any radio problems since you flashed the TMO ROM?
I wonder if I install the ROM in here http://forum.xda-developers.com/showthread.php?t=2477180 using RSDLite, would I get the OTA update to 4.4? The reason I want to install this ROM is because it only flashes system and boot.img without flashing bootloader, modem, logo etc... and I know the XT1058 radio is different from the XT1053 radio, so I've been reluctant to flash a full XT1053 ROM on my XT1058 phone.
But what I also would like to know is if an OTA update would flash a full ROM or not. In other words, if I flash the ROM above and then OTA update to 4.4 and the OTA update flashes the full ROM including the radio, I might as well flash the full 4.4 immediately.
What do you or anyone else think?
I'll answer to the best of my ability. heh
mschumacher69 said:
1. Can you please confirm that your model is XT1058 and not XT1053?
Click to expand...
Click to collapse
Mine was an XT1058, and has been flashed to XT1060. (I didn't notice that T-Mo had a 4.4 ROM on the list, so I went straight for the flashable ZIP for Verizon instead. silly me.)
mschumacher69 said:
2. Does the TMO ROM have the TMO boot logo and any TMO bloatware?
Click to expand...
Click to collapse
At least according to this article, the TMO version shouldn't have any bloatware.
mschumacher69 said:
4. Does the TMO ROM have the Mass Storage option under Settings > Storage > | > USB computer connection?
Click to expand...
Click to collapse
There's no reason why there shouldn't be; I'm seeing it on my Verizon version.
mschumacher69 said:
5. Have you been having any radio problems since you flashed the TMO ROM?
Click to expand...
Click to collapse
I can't say for sure if you'll face any problems, but I flashed the T-Mo radio provided here with my Verizon ROM, and I had no problems connecting to my network in Singapore.
--
I can't answer the rest unfortunately. Sorry. Hope I've helped.
RagnaParadise said:
I can't answer the rest unfortunately. Sorry. Hope I've helped.
Click to expand...
Click to collapse
Thank you for your answers!
Regarding Mass Storage, the reason I'm asking is because I don't have it on my AmericaMovil ROM.
The ROM is basically exactly what you get when you buy the T-Mobile version.
I figured the radios are nearly identical from the AT&T version and the T-Mobile version so my XT1058 is running on the XT1053 radios. There is no bloatware. tethering is there but I'm not sure if t-mobile will allow it. There is NO tmobile logo that comes up on boot. USB connect to computer is there.
As for the radio section again.. I was getting only EDGE in my house before I switched to this ROM (Meaning when I was on the ORIGINAL XT1058 image) and I am still getting only EDGE in my house.. Unfortunately I haven't left my house since yesterday flashing the image but when I'll be back at work in NYC and should see '4G/LTE' over there.
We'll see.
alternetconcept said:
The ROM is basically exactly what you get when you buy the T-Mobile version.
I figured the radios are nearly identical from the AT&T version and the T-Mobile version so my XT1058 is running on the XT1053 radios. There is no bloatware. tethering is there but I'm not sure if t-mobile will allow it. There is NO tmobile logo that comes up on boot. USB connect to computer is there.
As for the radio section again.. I was getting only EDGE in my house before I switched to this ROM (Meaning when I was on the ORIGINAL XT1058 image) and I am still getting only EDGE in my house.. Unfortunately I haven't left my house since yesterday flashing the image but when I'll be back at work in NYC and should see '4G/LTE' over there.
We'll see.
Click to expand...
Click to collapse
Thanks for ur reply! Which network are you on right now?
mschumacher69 said:
Thanks for ur reply! Which network are you on right now?
Click to expand...
Click to collapse
I've always been on T-mobile network. Both when i was on original XT1058 AmericanMovil system version and still on T-mobile when I switched the image to XT1053.
Back on my Nexus 4 though.. I would have HSPA+ in my house.. So I thought it was a bit odd that as soon as I received this phone that I wasn't getting anything other than EDGE..
I went to load MOFOROOT onto droid turbo, the cable go unplugged in middle of process.
Turbo has been stuck in bootloop ever since.
Using windows 8 and I have used every resource to try and get the phone to connect to computer so I can reload stock ROM.
The drivers will not load to the phone.
I have read just about every thread regarding droid turbo/maxx and cannot find a similar problem/solution.
I have used USBDeview. - attached
I have done partition clean.
I have wiped/factory reset
I have tried RSD Lite - which will not find the device
I have tried connecting it to PC through recovery mode.
ADB cant find device.
All in all how do i get stock rom onto phone when computer can't load drivers to it?
[quote name="jerney307" post=59961038]After cable got unplugged while flashing moforoot. I have tried to put stock ROM back on through boot loader.
I get stuck on your step #4. Says devices not found.
I am able to see my phone though usb deview as fastbook quark S... or while in recovery mode as xt1254. (see attached)
I have uninstalled/reinstalled drivers mulitple times but it will not take to my phone/computer.
I have used USBDeview.
I have done partition clean.
I have wiped/factory reset
I have tried RSD Lite - which will not find the device
I have tried connecting it to PC through recovery mode.
I have tried everything. Still at a stand still. Help would be greatly appreciated. I would much rather donate someone on here than to pay 200$ to insurance a new phone.[/QUOTE]
You have a droid turbo you have to flash back using rsd lite, I believe the rsd version you have doesn't detect your phone, uninstall it and use the one on my thread http://forum.xda-developers.com/showthread.php?t=3063470, also download your phones firmware (verizon) and your phone will be detected and it will flash
tried it
I have downloaded both from that site and no luck.
jerney307 said:
I have downloaded both from that site and no luck.
Click to expand...
Click to collapse
you need to use Verizon Stock Kitkat /// VRZ_XT1254_KDF21.128-15_15_CFC_SVC.xml.zip
turn off your phone and put it on fastboot mode (power and volume down 2 seconds) and then plug it on pc
it should be detected by rsd lite 6.2.4
select the phone and then select the firmware VRZ_XT1254_KDF21.128-15_15_CFC_SVC.xml.zip
and click on uncompress and flash
that should get your phone working.
also make sure you have motorola device manager for the proper fastboot drivers https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
do it
Complete - no luck
Okay so i went and uninstalled all the previous stuff i had. drivers/rsd lite etc
Reinstalled everything that you gave me and where the plan deviated was at "uncompress and flash"
I could uncompress only because rsd will not see my phone.
i made sure to download drivers and all.
Something is not right here, it seems like it would be easy.. but nothing will see my phone
ive attached some screenshots
Update - still not fixed
okie here's the update.
I borrowed a win 7 laptop from a friend and tried everything again.
Still, RSD will not see my phone and computer says no drivers available.
Anyone have ideas?
jerney307 said:
okie here's the update.
I borrowed a win 7 laptop from a friend and tried everything again.
Still, RSD will not see my phone and computer says no drivers available.
Anyone have ideas?
Click to expand...
Click to collapse
its just a driver issue... what drivers are you installing? When you install them, is windows using them (device manager should not be saying unknown/generic usb device)?
firmware help
Help I have droid turbo xt1254 it stuck in boot loop have no TWRP no cwm no custom recovery, However, I know how to flash I have all RSDLite, right Device Manager, adb fasboot stuff, all stuff transfers good but I don't find the right firmware, as it says this message:
(bootloader) Invalid signed image (bootloader) Preflash validation failed
Mobile Specs:
BL: moto-apq8084-70.96 )sha-b624508
Baseband: MDM9625_41.51.07.22.04R QUARK-CUST
Serial#: ZX1F24DNVV
CPU: APQ8084 ES1.1
Device is locked. Status COde: 0
can anybody help me???
kr12 said:
Help I have droid turbo xt1254 it stuck in boot loop have no TWRP no cwm no custom recovery, However, I know how to flash I have all RSDLite, right Device Manager, adb fasboot stuff, all stuff transfers good but I don't find the right firmware, as it says this message:
(bootloader) Invalid signed image (bootloader) Preflash validation failed
Mobile Specs:
BL: moto-apq8084-70.96 )sha-b624508
Baseband: MDM9625_41.51.07.22.04R QUARK-CUST
Serial#: ZX1F24DNVV
CPU: APQ8084 ES1.1
Device is locked. Status COde: 0
can anybody help me???
Click to expand...
Click to collapse
This is the thread below you should start with. This thread you are posting in is from 3 years ago, with different firmware. "Moforoot" was only with Kitkat, and was BEFORE Sunshine bootloader lock came along (November 2015).
Read post #1 CAREFULLY of the thread below. You will need Sunshine ($25) to unlock your bootloader. Depending on the firmware version you are on (you left that out), you may need to use a powerful temp root tool to allow Sunshine to run properly. But if you need to use it, it is ONLY a temp root and it NOT a substitute for unlocking your bootloader to obtain permanent root.
[GUIDE] How to unlock your bootloader, install TWRP and gain root access
https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
Again, read carefully, and if you have any questions then ask them in that thread.
ChazzMatt said:
This is the thread below you should start with. This thread you are posting in is from 3 years ago, with different firmware. "Moforoot" was only with Kitkat, and was BEFORE Sunshine bootloader lock came along (November 2015).
Read post #1 CAREFULLY of the thread below. You will need Sunshine ($25) to unlock your bootloader. Depending on the firmware version you are on (you left that out), you may need to use a powerful temp root tool to allow Sunshine to run properly. But if you need to use it, it is ONLY a temp root and it NOT a substitute for unlocking your bootloader to obtain permanent root.
[GUIDE] How to unlock your bootloader, install TWRP and gain root access
https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
Again, read carefully, and if you have any questions then ask them in that thread.
Click to expand...
Click to collapse
THanks so much for getting me in the right thread. I was busy these last days, and I'm new here, had no idea where to go........
BTW, I think u didnt understAND my question. I think I dont need to unlock bootloader, I might be wrong, but my question was which firmware I need to use. and I am in bootloop anyway, so i wonder if it is possible to download sunshine and how do i download sunshine in bootloop? (cant turn on mobile at all)
If u have any idea if anybody can figure out what firmware should i use, that would be the best help.
THanks
kr12 said:
THanks so much for getting me in the right thread. I was busy these last days, and I'm new here, had no idea where to go........
BTW, I think u didnt understAND my question. I think I dont need to unlock bootloader, I might be wrong, but my question was which firmware I need to use. and I am in bootloop anyway, so i wonder if it is possible to download sunshine and how do i download sunshine in bootloop? (cant turn on mobile at all)
If u have any idea if anybody can figure out what firmware should i use, that would be the best help.
THanks
Click to expand...
Click to collapse
The most recent stock Verizon Motorola Droid Turbo XT1254 firmware is here:
https://forum.xda-developers.com/showthread.php?t=3569334
I thought you wanted unlocked bootloader and TWRP. If not, just flash firmware from that thread.
You have to flash with RSDlite or ADB.
Sent from my official open market LG US998 V30+
kr12 said:
THanks so much for getting me in the right thread. I was busy these last days, and I'm new here, had no idea where to go........
BTW, I think u didnt understAND my question. I think I dont need to unlock bootloader, I might be wrong, but my question was which firmware I need to use. and I am in bootloop anyway, so i wonder if it is possible to download sunshine and how do i download sunshine in bootloop? (cant turn on mobile at all)
If u have any idea if anybody can figure out what firmware should i use, that would be the best help.
THanks
Click to expand...
Click to collapse
you do need the correct firmware to go back to stock or you will have the problem you are experiencing, since you arent sure which firmware you were on you could try the newest firmware and work backwards from there https://firmware.center/firmware/Motorola/Droid Turbo (XT1254)/Stock/
ChazzMatt said:
The most recent stock Verizon Motorola Droid Turbo XT1254 firmware is here:
https://forum.xda-developers.com/showthread.php?t=3569334
I thought you wanted unlocked bootloader and TWRP. If not, just flash firmware from that thread.
You have to flash with RSDlite or ADB.
Sent from my official open market LG US998 V30+
Click to expand...
Click to collapse
Thanks so much for the link. Thatss like something i was looking for. But i tried with that firmware and bunch of others, none of them worked. (I will list them)so can u pls specifically tell me which one i need based on the info i gave?
I would definitely love the unlocked bootloader and twrp (who wont) but i am in such position right now with not even a good firmware, cant go to recovery, dont have any apps installed, so right now i need like either just turning on the mobile or one on one help on the unlocking bootloader.
Thanks so much for replyinh.
---------- Post added at 05:08 PM ---------- Previous post was at 04:42 PM ----------
firmwares i used with no success
QUARK_VERIZON_6.0.1_MCG24.251-5_cid2_subsidy-1FF.xml
QUARK_VERIZON_6.0.1_MCG24.251-5_cid2_subsidy-DEFAULT_CFC.xml
QUARK_VERIZON_6.0.1_MCG24.251-5-5_cid2_subsidy-DEFAULT_CFC.xml
quark_verizon-user_LCF23.80_release-keys_firmware_upgrade_SVC.xml
VRZ_XT1254_KDF21.128-15_15_CFC_SVC.xml
VRZ_XT1254_SU4TL-44_44_CFC.xml
kr12 said:
Thanks so much for the link. Thatss like something i was looking for. But i tried with that firmware and bunch of others, none of them worked. (I will list them)so can u pls specifically tell me which one i need based on the info i gave?
I would definitely love the unlocked bootloader and twrp (who wont) but i am in such position right now with not even a good firmware, cant go to recovery, dont have any apps installed, so right now i need like either just turning on the mobile or one on one help on the unlocking bootloader.
Thanks so much for replyinh.
---------- Post added at 05:08 PM ---------- Previous post was at 04:42 PM ----------
firmwares i used with no success
QUARK_VERIZON_6.0.1_MCG24.251-5_cid2_subsidy-1FF.xml
QUARK_VERIZON_6.0.1_MCG24.251-5_cid2_subsidy-DEFAULT_CFC.xml
QUARK_VERIZON_6.0.1_MCG24.251-5-5_cid2_subsidy-DEFAULT_CFC.xml
quark_verizon-user_LCF23.80_release-keys_firmware_upgrade_SVC.xml
VRZ_XT1254_KDF21.128-15_15_CFC_SVC.xml
VRZ_XT1254_SU4TL-44_44_CFC.xml
Click to expand...
Click to collapse
That is part of the problem -- all those firmwares you tried to install. Each one has a certain version of bootloader and you cannot downgrade to older bootloaders. With locked bootloader, there's no way to downgrade to older firmware without bricking your phone. (There is a way with an unlocked bootloader, but that's not this discussion.)
1) this thread below is about using Sunshine to unlock your bootloader, and gives all the instructions. Furthermore, Sunshine dev has participated in that thread. Yes, part of the process (depending on firmware you are on) is to use a temp root to allow Sunshine to work. That's where it can get complicated. Sunshine costs $25.
[GUIDE] How to unlock your bootloader, install TWRP and gain root access
https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
2) If you don't want to do that then you need to just install the very latest firmware, not some older firmware. You can't downgrade to older firmware with locked bootloader. With a locked bootloader it will brick your phone trying to install older firmware. This is the newest Verizon Motorola firmware:
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5-5
https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3569334
Those are your only two options.
Searching via cell isn't great for me at the moment. I've found a few threads with lollipop files to use in Odin. But I haven't read anything that says it's simple to flash them and downgrade properly from Marshmallow to Lollipop. Is there a tutorial/file thread already on here that I am missing via search? Is this something I can do without rooting?
Da hell is that chipmunk woman
Sammobile doesn't have the stock 5.1 firmware.. is that an omen against downgrading?
Most of the posts ive read are indicating Marshmallow is not able to be downgraded, bootloader locked.. looks like a dead end
It's a different boot loader, will not be able to downgrade. There is no root option at this time as well.
johnkirchner said:
It's a different boot loader, will not be able to downgrade. There is no root option at this time as well.
Click to expand...
Click to collapse
sorry, but i disagree. i just flashed from 6.0.1 to 5.1.1 using odin and firmware found here on XDA. I have no problems with phone so far.
At the time of my post months ago, this was not possible. It is very possible now, I have also done it.
gooch1006 said:
sorry, but i disagree. i just flashed from 6.0.1 to 5.1.1 using odin and firmware found here on XDA. I have no problems with phone so far.
Click to expand...
Click to collapse
This is for the AT&T model, I haven't been able to crack into mine. I have battery issues since marshmallow and want to go back to 5.1.1 as well... where did you get the files, and what process did you use?
Downgrade instructions can be found here:
http://forum.xda-developers.com/showthread.php?p=67323522
johnkirchner said:
Downgrade instructions can be found here:
http://forum.xda-developers.com/showthread.php?p=67323522
Click to expand...
Click to collapse
Thanks for the link, i had searched without luck on my own.
https://forum.xda-developers.com/att-galaxy-s5/general/guide-merry-christmas-heres-t3516196
following this guide for rolling back to LP, work for me downgrade from MM and getting root on LP.
Mine didn't... version DPH4, october 1, 2016 security patch, odin gave me an error something like level 4 > 3 and didn't start the reflash process. I was able to reflash the same 6.0.1 and its not the same as what was on there, so maybe the ota updates had a problem? I'm still locked out of downgrading.
Mine also from DPH4 oct 1, 2016. Having issue with lte, i cant receive call but i can make call. So im rollback to COI5 and follow the instruction from page 2. Get odin 3.11.1 to flash BL,AP,etc. Have you try with other usb cable?
kecel said:
Mine also from DPH4 oct 1, 2016. Having issue with lte, i cant receive call but i can make call. So im rollback to COI5 and follow the instruction from page 2. Get odin 3.11.1 to flash BL,AP,etc. Have you try with other usb cable?
Click to expand...
Click to collapse
i had that issue at one point, i just flashed the CSC and CP again and it worked.. Idk if it's that simple for you guys tho..
g900a downgrade from 6.0.1 to 5.1.1
djs2571 said:
This is for the AT&T model, I haven't been able to crack into mine. I have battery issues since marshmallow and want to go back to 5.1.1 as well... where did you get the files, and what process did you use?
Click to expand...
Click to collapse
i also have the at&t model, but used some info in this post: https://forum.xda-developers.com/att-galaxy-s5/general/guide-merry-christmas-heres-t3516196
i used odin to flash full OI5 firmware, minus the bootloader file. Only use the AP, CP, and CSC files. the bootloader is the same. and really, i had already flashed the PA2 build earlier that day i remember now. would probably do that first. flashing the PA2, i used all four files, BL, AP, CP, and CSC . they both flashed the first time, if they dont then try a different cable first. usually that is my issue.
so , i flashed from 6.0.1 down to 5.1.1 pa2, then down to oi5. still have no problems other than getting root..... im focusing on bootloader now, i have unlocked them on htc's before, but havent tried any other phone yet. the work continues tonight.
Removed because SM-G935U is bootloader locked. Please close this thread.
travis82 said:
This is for the U.S. Unlocked variant. SM-G935U
Flash twrp via odin: https://www.androidfilehost.com/?fid=385035244224389793
Rom (bloated) + Kernel: re-doing rom
no-verity-opt-encrypt-2.1.zip: https://www.androidfilehost.com/?fid=385035244224381666
Flash twrp via odin, Boot up in to twrp, format data partition, flash the rom that you copied to your phones sd or microsd card, than flash no-verity because I forgot to fix it in your kernels ramdisk.
This is a test our devies are exactly the same minus the dual sim card part. Please post back and let me know O the rom is pre rooted and the kernel is permissive too.
Click to expand...
Click to collapse
Crossing my fingers that something good will come of this though I am a bit skeptical.
Hi there. I TEST it on my G935T but not with out some issue. Flashing the rom TRIPS QUALCOMM SECURITY BOOT, the BINARY GOES CUSTOM. To BOOT the phone, you'll have to FLASH THE US SM-G935 Samsung_G935x_QC_Rooted_BOOT Tar file for the phone to BOOT. That FILE changes the BINARY from CUSTOM to OFFICIAL and BOOT up. Next issue, the PHONE randomly REBOOT WHILE THE WI-FI ON. Turn off the WIFI and skip through everything, and you'll be ok after that. The PHONE I used to FLASH THE ROM HAVE NO SIM CARD IN IT, So I don't know if you'll get RANDOM REBOOTS AS IT CONNETED TO LTE. As for the ROM, it LOOKS FAIRLY AS STOCK G935U FIRMWARE. I compared it with my G935T RUNNING STOCK OFFICIAL G935U FIRMWARE, it LOOKS THE SAME EXCEPT FOR THE VOICEMAIL APP and the phone SAY CUSTOM. IT WOULD OF WORK, it just have to prepared different to FLASH USING FLASHFIRE app. Just a little bit more TWEAKS AND IT WILL RUN ON ALL US SNAPDRAGON SM-G935 MODELS.
Okay so what's all been debloated? Also had issues with twrp recently when I downloaded it through the play store. Next question is SU removed when doing a hard reset? Otherwise than those of definitely want to run it. Let me set up an account here, I have some questions like removing knock and stuff like that but if you could answer what I asked it'd be great.
\_○RD_b€rU$ said:
Okay so what's all been debloated? Also had issues with twrp recently when I downloaded it through the play store. Next question is SU removed when doing a hard reset? Otherwise than those of definitely want to run it. Let me set up an account here, I have some questions like removing knock and stuff like that but if you could answer what I asked it'd be great.
Click to expand...
Click to collapse
It says this is a bloated ROM, and download directly from the links provided for the best chance of it working. There is a reason they provide the downloads sometimes.
Ok so let me get this strait. That bootimage sets the status to official? is that because its a stock kernel? The wifi can be fixed with a default.prop edit so can secure storage. Give me more info on that boot tar you guys have to use. Maybe I can modify it with my kernel blob so it boots through still.
G935U Int unlocked users, did you use crom.apk to unlock your bootloaders? If so I can compile a kernel for YOU when I get the time. But if you used crom.apk than unlocked your bootloaders, than in dev options have oem unlock checked still, that top rom and kernel should boot up. The wifi issues, you can fix by editing default.prop, secure storage also.
So I really need you G935U users to speak up like I had to tell the dual sim guys. Does this work on SM-G935U? :
Download and install S6-Crom.apk, it will allow the bootloader to be unlocked for the S7 Edge SM-G9350:
http://forum.xda-developers.com/attachment.php?attachmentid=3270074&d=1429412423
NOTE: You must Enable Developer Options in Settings and turn on OEM Unlock!!!
travis82 said:
This is for the U.S. Unlocked variant. SM-G935U
Flash twrp via odin: https://www.androidfilehost.com/?fid=385035244224389793
Rom (bloated): https://www.androidfilehost.com/?fid=457095661767106988
Kernel permissive: https://www.androidfilehost.com/?fid=457095661767106995
no-verity-opt-encrypt-2.1.zip: https://www.androidfilehost.com/?fid=385035244224381666
Flash twrp via odin, Boot up in to twrp, format data partition, flash the rom that you copied to your phones sd or microsd card, than flash no-verity because I forgot to fix it in your kernels ramdisk.
This is a test your devies are exactly the same minus the dual sim card part. Please post back and let me know O the rom is pre rooted and the kernel is permissive too.
Click to expand...
Click to collapse
Can Twrp be flashed on a Tmobile s7Edge flashed with the U firmware?????
travis82 said:
G935U Int unlocked users, did you use crom.apk to unlock your bootloaders? If so I can compile a kernel for YOU when I get the time. But if you used crom.apk than unlocked your bootloaders, than in dev options have oem unlock checked still, that top rom and kernel should boot up. The wifi issues, you can fix by editing default.prop, secure storage also.
So I really need you G935U users to speak up like I had to tell the dual sim guys. Does this work on SM-G935U? :
Download and install S6-Crom.apk, it will allow the bootloader to be unlocked for the S7 Edge SM-G9350:
http://forum.xda-developers.com/attachment.php?attachmentid=3270074&d=1429412423
NOTE: You must Enable Developer Options in Settings and turn on OEM Unlock!!!
Click to expand...
Click to collapse
Well, I can't speak for the genuine 935U, but I tried it on my SM-G935R4 (US Cellular) and it force-closes upon opening. If it helps at all, I'm not running the stock USCC ROM, but rather the Verizon-based Stang5.0litre custom ROM that can be found over in the Verizon S7E forum. I've successfully used the 935U firmware on this phone also. Kinda makes me think it's not gonna work on a real 935U either, but I dunno.
(Oh and yeah, I've been wondering about TWRP too - Can we really flash it through Odin despite the bootloader lock?)
The G935U bootloader cannot be unlock nor can any USA S7 models that I know of. I tried to flash the twrp after installing the s6-crom.apk , but twrp won't flash and the s6-crom.apk keeps FC.
Sent from my SM-G935U using Tapatalk
Than what model is the unlocked single sim s7 edge snapdragon?
It's the SM-G935U it has sim unlocked but has a locked bootloader.
Sent from my SM-G935U using Tapatalk
travis82 said:
Than what model is the unlocked single sim s7 edge snapdragon?
Click to expand...
Click to collapse
I believe there's a Chinese version with snapdragon that's G9300 not G930U
Kernel no funciona el enlace
---------- Post added at 05:32 AM ---------- Previous post was at 05:26 AM ----------
Does not work the link to the amigo kernel, you can pass it to me please? Best regards!
travis82 said:
G935U Int unlocked users, did you use crom.apk to unlock your bootloaders? If so I can compile a kernel for YOU when I get the time. But if you used crom.apk than unlocked your bootloaders, than in dev options have oem unlock checked still, that top rom and kernel should boot up. The wifi issues, you can fix by editing default.prop, secure storage also.
So I really need you G935U users to speak up like I had to tell the dual sim guys. Does this work on SM-G935U? :
Download and install S6-Crom.apk, it will allow the bootloader to be unlocked for the S7 Edge SM-G9350:
http://forum.xda-developers.com/attachment.php?attachmentid=3270074&d=1429412423
NOTE: You must Enable Developer Options in Settings and turn on OEM Unlock!!!
Click to expand...
Click to collapse
We don't have unlocked bootloaders crom apk force closes on opening it
Has anyone tried this on the G935U with success or can this device be rooted?
This doesn't work for the SM-G935U the crom.apk force closes without it we cannot unlock bootloader
Sent from my SM-G935U using Tapatalk
Twrp doesn't flash thru Odin. I have eng bootloader installed but Odin freezes at start. How long should it take to start to flash?
Any update on this
I've tried loading twrp through odin but keep getting a fail. I'm rooted and was wondering if it's easier to just add it through adb? Or would it be possible to flash it through the terminal emulator? I'd really like to get exposed on my phone lol I'm Currently on a 935A with the 935U firmware Rooted
Hi guys,
I (and some of my friends) had a problem with XT1254:
1. We updated to 6.0.1 via recovery with update.zip. This process had successfully done.
2. Several felt something wrong with new 6.0.1 system, so they re-updated via recovery again (still the same update.zip). This made the system dead. They could not enter system, except bootloader and recovery. The problem is that source system needs to be Lollipop SU4TL-49 so the re-update process will fail.
3. I did like them and tried to find the solution from old methods:
- tried to downgrade to 5.1;
- tried to flash new 6.0.1 system.img;
- deleted some lines in "updater-script" and tried to sideload via recovery;
but all failed because of "invalid signed image" (for both RSD and fastboot). The partion, boot, kernel have been the newest ones.
4. I tried to downgrade my XT1060 to Kitkat (another mine), and it also failed with flashing system.img. I had to flash the Lollipop's system.img and the problem solved.
Conclusion:
1. Unlock bootloader and flash TWRP will solved the problem for XT1254. The phone could not boot to system so buying a unique key is the only solution (but how to buy?).
2. Wait for the 6.0.1 flash file (xml) then flash via RSD. Several security patches from Verizon may lock the downgrade process.
3. Can some one give other solutions?
Thanks guys!!!!
mr_5kool said:
Hi guys,
I (and some of my friends) had a problem with XT1254:
1. We updated to 6.0.1 via recovery with update.zip. This process had successfully done.
2. Several felt something wrong with new 6.0.1 system, so they re-updated via recovery again (still the same update.zip). This made the system dead. They could not enter system, except bootloader and recovery. The problem is that source system needs to be Lollipop SU4TL-49 so the re-update process will fail.
3. I did like them and tried to find the solution from old methods:
- tried to downgrade to 5.1;
- tried to flash new 6.0.1 system.img;
- deleted some lines in "updater-script" and tried to sideload via recovery;
but all failed because of "invalid signed image" (for both RSD and fastboot). The partion, boot, kernel have been the newest ones.
4. I tried to downgrade my XT1060 to Kitkat (another mine), and it also failed with flashing system.img. I had to flash the Lollipop's system.img and the problem solved.
Conclusion:
1. Unlock bootloader and flash TWRP will solved the problem for XT1254. The phone could not boot to system so buying a unique key is the only solution (but how to buy?).
2. Wait for the 6.0.1 flash file (xml) then flash via RSD. Several security patches from Verizon may lock the downgrade process.
3. Can some one give other solutions?
Thanks guys!!!!
Click to expand...
Click to collapse
me too
i updated to 6.0.1 via recovery with update.zip. This process had successfully done and re-updated via recovery again (still the same update.zip) and i factory reset tin recovery so it stuck screen 'erasing...'They could not enter system, except bootloader and recovery vesersion (6.0.1),can not into apply update sdcard , it turn e:\unkown volum path [sdcard]... and I did like them and tried to find the solution from old methods:
- tried to downgrade to 5.1;
- tried to flash new 6.0.1 system.img;
but all failed because of "invalid signed image" (for both RSD and fastboot). The partion, boot, kernel have been the newest ones.
Conclusion:
1. Unlock bootloader and flash TWRP will solved the problem for XT1254. The phone could not boot to system so buying a unique key is the only solution (but how to buy?).
2. Wait for the 6.0.1 flash file (xml) then flash via RSD. Several security patches from Verizon may lock the downgrade process.
3. Can some one give other solutions?
longbin said:
1. Unlock bootloader and flash TWRP will solved the problem for XT1254. The phone could not boot to system so buying a unique key is the only solution (but how to buy?).
2. Wait for the 6.0.1 flash file (xml) then flash via RSD. Several security patches from Verizon may lock the downgrade process.
3. Can some one give other solutions?
Click to expand...
Click to collapse
1. I have never heard of anyone selling bootloader unlock keys for the XT1254. If you want to unlock your bootloader, Sunshine is your only option, and as of right now it will only work on lollipop builds. If your phone is on marshmallow, Sunshine will not work. If your phone cannot boot, it won't work no matter what build you're on.
2. If your phone is bricked and on marshmallow, waiting for the full firmware package is your only option. However, a downgrade to a previous firmware with a locked bootloader isn't, and has never been, possible.
mr_5kool said:
Conclusion:
1. Unlock bootloader and flash TWRP will solved the problem for XT1254. The phone could not boot to system so buying a unique key is the only solution (but how to buy?).
2. Wait for the 6.0.1 flash file (xml) then flash via RSD. Several security patches from Verizon may lock the downgrade process.
3. Can some one give other solutions?
Thanks guys!!!!
Click to expand...
Click to collapse
unlock the bootloader and install TWRP BEFORE doing any updates, while still on Lollipop. That is the only safe, logical answer. An unlocked bootloader -- especially with custom recovery -- will let you do lot of things and is more forgiving of mistakes than a locked bootloader.
We keep telling people that and they won't believe us.
---------- Post added at 10:37 AM ---------- Previous post was at 10:32 AM ----------
TheSt33v said:
If your phone is bricked and on marshmallow, waiting for the full firmware package is your only option. However, a downgrade to a previous firmware with a locked bootloader isn't, and has never been, possible.
Click to expand...
Click to collapse
Right. Several people who didn't like Lollipop but preferred the original Kitkat "speed", "battery life" or whatever successfully downgraded back to 4.4.4 -- but only AFTER they unlocked their bootloader. Even then you have to make sure you don't flash the old gpt.bin in ADB, but downgrading is possible with an UNlocked bootloader.
Even when flashing XT1250 firmware over XT1254 or vice versa, it CAN be done with a locked bootloader, but if you mess something up you are in big trouble. UNlocked bootloader? Just do it again, correcting your mistake the next time.
---------- Post added at 10:43 AM ---------- Previous post was at 10:37 AM ----------
TheSt33v said:
1. I have never heard of anyone selling bootloader unlock keys for the XT1254.
Click to expand...
Click to collapse
There was a guy on some website who was selling some Verizon keys a long time ago, known as "the Chinaman". He disappeared.
China Middleman Back??
http://forum.xda-developers.com/moto-x/moto-x-qa/china-middleman-t2751177
dschill said:
Well the china man added me back on skype today. And sadly said that he can no longer get the codes and refunded my 45$ via paypal.
Heres a little bit of the skype transcipt
[12:08:22 PM] live:dschillinrecovery: k i just got the refund
[12:08:25 PM] live:dschillinrecovery: so you cant get the code any more?
[12:12:41 PM] VIP-UNLOCK: No time to deal with the accident, we default to a refund
[12:13:08 PM] VIP-UNLOCK: Sorry, goodbye
[12:13:32 PM] live:dschillinrecovery: Its alright. Thanks for the refund though. Let me know if you can ever get the codes again
Guess the best we can do for now is to wait for jcase and sunshine to release the 3.0 version.
Click to expand...
Click to collapse
and another thread discussing same guy:
http://forum.xda-developers.com/moto-x/general/4-1-vzw-att-moto-maker-bootloader-t2680651
The process seems to involve sending approximately $45 to a Chinese middle-man via eBay and another website, along with your IMEI and cell phone number, and you will receive an unlock code.
It seems like this is all one guy handling this process. Turnaround time seems to be 24-48 hours beginning to end.
Click to expand...
Click to collapse
Theory was that someone with access to Motorola's engineering software had a side business going. You know they unlock their bootloaders for testing and such. Someone with access to that software could make some money if they made sure they covered their tracks.
Also people who visited China were able to buy unlocked bootloader Droid Turbos well before Sunshine was released. One guy posted in this forum. In that case, it was probably pilfering some phones from the factory -- but again with unlocked bootloaders. So, there is some software out there somewhere, just kept under wraps.
Haha the Chinaman? Really? Sounds like an evil arms dealer from a 90's action movie. Man, if only the magic official bootloader unlocking software was leaked. That would be like Christmas times infinity.
TheSt33v said:
Haha the Chinaman? Really? Sounds like an evil arms dealer from a 90's action movie. Man, if only the magic official bootloader unlocking software was leaked. That would be like Christmas times infinity.
Click to expand...
Click to collapse
I updated my post to include XDA links. I can't find any examples of Droid Turbos being unlocked via this eBay "purchase" only other Verizon phones, but there are the legitimate reports of unlocked Droid Turbos for sale in China in the year prior to Sunshine being released November 2015. One guy even posted on here because he was trying to install CM12.1 at the time on his BOOTLOADER UNLOCKED Droid Turbo he had purchased in China.
Note the Chinese middleman guy was charging $45 for bootloader unlock at the time, and Sunshine only charges $25.
xml flash file is the last solution =))
@ChazzMatt: I think it's impossible to cross flash 1250 to 1254, but 1254 can flash to 1250
Doesn anybody know how much does usually takes for Verzion ( or whoever does it ) to release xml sbf firmware file? And do they release every? I need latest MCG24 or at least system file (s) is enough.
I have everything except system files, if anybody can provide system files or knows hot to convert ones from ota , I can make complete fastboot xml zip.
EDIT: System from OTA is not enough. If somebody can provide system / backup from MCG24 phone, I might be able to make it.
mr_5kool said:
@ChazzMatt: I think it's impossible to cross flash 1250 to 1254, but 1254 can flash to 1250
Click to expand...
Click to collapse
No, people have done both. One guy messaged me on Hangouts telling me what he did, so I know it can be done.
ChazzMatt said:
No, people have done both. One guy messaged me on Hangouts telling me what he did, so I know it can be done.
Click to expand...
Click to collapse
Can you give little more info on this. Changed cid? Unlocked bootloader? Maybe we can use x1250 xml fastboot files until they release Marshmallow fastboot. I need one for backup , I know I'll brick the phone sooner or later , as guys above did lol..
Yes, unlocked bootloader and you don't flash the XT1254 bootloader. This was before Sunshine, and he converted XT1250 to XT1254 with unlocked bootloader.
We chatted over a few days, while he tried to find an XT1250, ordered one, then it arrived. Then he flashed the Verizon firmware. Here's the relevant portion of what he wrote:
Flashed the Verizon radio and 5.1 FW (firmware)
The only problem I have right now is upload speeds are super slow.
gonna try wiping the radio and re-writing the radio
Click to expand...
Click to collapse
I then asked him a couple of questions and he answered this:
Yes I flashed the Verizon Radio to the device
not the bootloader image, for obvious reasons
I wanted 5.1, so I didn't test until I had the VZW 5.1 with my SIM card
I'm going to try an reflash soon, and then get a new SIM just in case
I hope Verizon doesn't give me any trouble getting a new SIM at my local store
Click to expand...
Click to collapse
I didn't hear from him anymore after that, so guess everything turned out OK. This in August 2015, was about a month after 5.1 was released for the Droid Turbo XT1254 (XT1250 was still on 4.4.4) but before Sunshine released their bootloader unlock for the XT1254 in November 2015.
ChazzMatt said:
Yes, unlocked bootloader and you don't flash the XT1254 bootloader. This was before Sunshine, and he converted XT1250 to XT1254 with unlocked bootloader.
We chatted over a few days, while he tried to find an XT1250, ordered one, then it arrived. Then he flashed the Verizon firmware. Here's the relevant portion of what he wrote:
I then asked him a couple of questions and he answered this:
I didn't hear from him anymore after that, so guess everything turned out OK. This in August 2015, was about a month after 5.1 was released for the Droid Turbo XT1254 (XT1250 was still on 4.4.4) but before Sunshine released their bootloader unlock for the XT1254 in November 2015.
Click to expand...
Click to collapse
Yeah but we're talking about vice-versa here, flashing xt1250 Firmware to xt1254 .
Flashing xt1254 firmware to xt1250 with unlocked bootloader doesn't seem like a big deal, it should be possible anyway..
Ej?iSixo said:
Yeah but we're talking about vice-versa here, flashing xt1250 Firmware to xt1254 .
Flashing xt1254 firmware to xt1250 with unlocked bootloader doesn't seem like a big deal, it should be possible anyway..
Click to expand...
Click to collapse
That's been done, too. I didn't know that was the question.
One guy didn't want Verizon bloatware and his solution was to flash the "pure" Motorola firmware from the XT1250 over his XT1254.
Yes, he had unlocked bootloader and could have just uninstalled the bloatware. I'm not saying it was logical, I'm just telling you what he did.
So there's no question these two phones are exactly the same device, with exactly the same FCC ID.
The issue is the XT1250/XT1254 being flashed needs to the other needs an unlocked bootloader. And you can't downgrade (gpt.bin) when you flash.
So, for the purposes of this thread that information doesn't help you, if your XT1254 bootloader isn't unlocked.
mr_5kool said:
Hi guys,
I (and some of my friends) had a problem with XT1254:
1. We updated to 6.0.1 via recovery with update.zip. This process had successfully done.
2. Several felt something wrong with new 6.0.1 system, so they re-updated via recovery again (still the same update.zip). This made the system dead. They could not enter system, except bootloader and recovery. The problem is that source system needs to be Lollipop SU4TL-49 so the re-update process will fail.
Conclusion: Wait for the 6.0.1 flash file (xml) then flash via RSD.
Thanks guys!!!!
Click to expand...
Click to collapse
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5
https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3531571