Related
I will try to explain me clearly
My phone is working normally and I can restore nandroid without issues
I'm actually with my V29 KK TW and work without issues
BUT If i flash aosp or cm rom, just afeter enter pin code, the screen becomes black like problem with proximity sensor
I can put my hand in front, it doesn't change, If I push the buttons, sometimes the screen appears and disappears immediately
and the more strange is I have this problem with the RR 5.3.9 I had flashed before without issue and can restore a nandroid I have done with it...
I have done a clean flash of my KK TW V29 without issue....
first I have made a FULL wipe include internal storage and flash stock NI4 rom but without any changes
someone got an idea???
thank's
I have flashed successfully 2 QS L differents versions but can't with CM roms (euphoria, tema, RR...)
is there a reason to that
This is x-files troubles, personally I reflash stock LP with Odin and all is good now
I have try back with RR 5.3.9 and got same problem but if I restore nandroid from 5.3.9 it's working without issues...WTF!!!!!!!!!!!!
i try to flash L stock rom with odin root, complete wipe (except ext sdcard)
I run masik script wipe and ael cleaner, format boot, system data
It seem's it begin when I flash arter kernel or the UKM (universal kernel manager) to run civ kernel..
so i try to uninstall ukm but allways without succes
I flashed 4.4 c-rom without issues, so I flashed back KK rom with odin and back to my V29 kk rom
look my signature to have details on my config
thank's for the help..
So...first question:
Did you ever take the official lollipop update from samsung?
Second Question:
What country are you in, and carrier do you use?
Please message me the following details from the sticker inside the device under the battery, so I can grab the Service files from samsung for you!
I've flashed OB1 with odin and flash back after 2 weeks NI4 and the last I try was this N9005XXUFNG2_N9005OXXFNG3_XEF (Open France) (No-wipe)
the flash goes well but doesn't change my BL and modem, before that I was with NI4 BL and NI3 modem and now still with that
I use sosh carrier (orange) in france
will send you the details from sticker
@rayman95 This is what i have found out!!! From my understanding, You took the Lollipop bootloader when you installed the OC1 Package. if you want to completely restore to "Earlier Version", WHICH this may not be possible due to a SAMSUNG new coding issue, You would need to have the complete 4 Files software to repair your device.... As well as using all the following checkboxes in ODIN:
Auto-Reboot
Re-Partition
F. Reset Time
NAND Erase ALL
Phone Bootloader Update
I Attempted to download your files for the device, but Kies will Not "Initialize" for download, and it will give you an Error if you plug the device into Kies3 i believe because you device is ROMMed.
IF you want to try Kies to restore AND it begins "DOWNLOADING", You can copy the Tmp****.tmp.zip that is created when the progress indicator hits 85% in Kies.
The File location on Win7 is "C:\Users\*Your Screen Name HERE*\AppData\Local\Temp"
If you Have the 4 Part file for NI2, try flashing in ODIN wioth the Above Checkboxes selected!!
Kies don t let me dl any files and gave me some error but don't remember exactly what... but not important because you give me good files.....after that I hope flashing again cm12.1.....
Thank so again chief....
Everything was fine until I flashed CM13 unofficial.
Now, my bootloader is updated to 6.0 (COJ5 something or COH4), I can't revert to something prior to that: odin fails at sboot.bin NAND write start fail.
-While this issue has occured to many others than me, I'm the only one who can't even boot into CM13 or AOSP based ROMs, even after pushing different variants of ROMs several times through ADB, bootloops are still persistent.
-Any other 5.1.1 Official ROM that's not COJ5 or COH4 fails to flash at odin. COJ5/COH4 ROMS flash succesfully, but the phone doesn't boot past the samsung text.
-I have tried flashing various COH4 ROMS along with their AP,BL,CSC etc, everything flashes succesfully apart from the bootloader file, and after that it's the same samsung text brick. I couldn't find the PIT files (bootloader csc n such) for COJ5..
Is there a place I can find a backed up EFS partion ?file? and restore it myself? Would this get me out of the****hole i'm currently in?
What can I do about this...
Nortabun said:
Everything was fine until I flashed CM13 unofficial.
Now, my bootloader is updated to 6.0 (COJ5 something or COH4), I can't revert to something prior to that: odin fails at sboot.bin NAND write start fail.
-While this issue has occured to many others than me, I'm the only one who can't even boot into CM13 or AOSP based ROMs, even after pushing different variants of ROMs several times through ADB, bootloops are still persistent.
-Any other 5.1.1 Official ROM that's not COJ5 or COH4 fails to flash at odin. COJ5/COH4 ROMS flash succesfully, but the phone doesn't boot past the samsung text.
-I have tried flashing various COH4 ROMS along with their AP,BL,CSC etc, everything flashes succesfully apart from the bootloader file, and after that it's the same samsung text brick. I couldn't find the PIT files (bootloader csc n such) for COJ5..
Is there a place I can find a backed up EFS partion ?file? and restore it myself? Would this get me out of the****hole i'm currently in?
What can I do about this...
Click to expand...
Click to collapse
Hi, this may help you http://forum.xda-developers.com/note-4/help/fix-note4-exynos-n910c-bootloop-problem-t3312161
mangui said:
Hi, this may help you http://forum.xda-developers.com/note-4/help/fix-note4-exynos-n910c-bootloop-problem-t3312161
Click to expand...
Click to collapse
Yea i came across this, but there was one tiny problem
how on earth am i supposed to root, get busybox, and apply usb debugging on my phone while it has no functional ROM?
and how on earth am i supposed to transfer a backup from my ROMless phone?
Do you have a pit file for repartition
If so, access twrp , wipe everything including your internal storage. Then boot into download mode.
In the computer, load the pit file and your stock coj5 into Odin 3.10 , tick "repartition" and "Nand Erase All"then click start.
Back to your phone - which now should be boot looping - access the stock recovery and wipe. Root - try using a different root method like chainfire's Odin autoroot - then twrp ur phone. Flash cm13 then start running the steps I threaded ( [fix] note 4 exynos bootloop problem ...... )
PM me for what you get
Sent from my HTC Desire 820s dual sim using Tapatalk
Hi everyone,
I am running stock G920FXXU4DPIL (6.0.1) and I want to go back to stock G920FXXU3COI9 (5.1.1).
When I try to flash G920FXXU3COI9 with Odin, it fails at sboot.bin with error "sw rev check fail device 4 binary 3", which is quite normal because Samsung prevents flashing older bootloader over newer bootloader.
So I extracted the content of the stock firmware, removed sboot.bin, cm.bin, modem.bin and repacked a new .tar using android unified toolkit.
Then I flashed the resulting file with Odin.
Flashing worked but now I am stuck at Samsung logo. I cannot enter recovery either.
Only way to soft unbrick the phone is flash stock G920FXXU4DPIL again.
Why ??
I also want to go back to 5.1.1 as I don't like MM and N is also not too stable. so I have struggled alot tried 15 different firmwares from all regions but no luck all of them fails at sboot.bin device 5 binary 4 at last I flashed lollipop based zips and they also stuck at bootlogo. There is a combination firmware 5.1.1 with engineered bootloader which allow you to downgrade but fingerprint sensor don't work .
qasim799 said:
I also want to go back to 5.1.1 as I don't like MM and N is also not too stable. so I have struggled alot tried 15 different firmwares from all regions but no luck all of them fails at sboot.bin device 5 binary 4 at last I flashed lollipop based zips and they also stuck at bootlogo. There is a combination firmware 5.1.1 with engineered bootloader which allow you to downgrade but fingerprint sensor don't work .
Click to expand...
Click to collapse
So do you know where I can find SM-G920F engineering bootloader?
I have searched hundreds of pages and it's nowhere to be found :'(
Thanks!
qasim799 said:
I also want to go back to 5.1.1 as I don't like MM and N is also not too stable. so I have struggled alot tried 15 different firmwares from all regions but no luck all of them fails at sboot.bin device 5 binary 4 at last I flashed lollipop based zips and they also stuck at bootlogo. There is a combination firmware 5.1.1 with engineered bootloader which allow you to downgrade but fingerprint sensor don't work .
Click to expand...
Click to collapse
How do you mean not too stable? It works perfectly! I installed CYV version, not a single glitch since install. Everything works like a charm and battery is muvh better than on MM. Plus it has some pretty awesome options.
OK i managed to find a combination firmware:
COMBINATION_OXA_FA50_G920FXXU4APF1_OXA4APF1_CL6658768_QB10183466_REV02
However there is a pit file inside. Does this mean I have to repartition the device?
Seems tricky since I want to be able to flash a stock firmware afterwards.
Can I extract and flash only sboot.bin from combination firmware?
From my understanding, once I have the engineering bootloader, it will let me flash an older one...
couitchy said:
OK i managed to find a combination firmware:
COMBINATION_OXA_FA50_G920FXXU4APF1_OXA4APF1_CL6658768_QB10183466_REV02
However there is a pit file inside. Does this mean I have to repartition the device?
Seems tricky since I want to be able to flash a stock firmware afterwards.
Can I extract and flash only sboot.bin from combination firmware?
From my understanding, once I have the engineering bootloader, it will let me flash an older one...
Click to expand...
Click to collapse
there is no problem with it. You can go back to any MM or N firmware.
---------- Post added at 01:06 PM ---------- Previous post was at 01:04 PM ----------
ilDuceo said:
How do you mean not too stable? It works perfectly! I installed CYV version, not a single glitch since install. Everything works like a charm and battery is muvh better than on MM. Plus it has some pretty awesome options.
Click to expand...
Click to collapse
Maybe I"m fed up from N grace ux as before N was released i was using note 7 grace ux port. Lollipop is so responsive if you used it then you can feel that is pretty obvious.
It worked!
I flashed COMBINATION_OXA_FA50_G920FXXU4APF1_OXA4APF1_CL6658 768_QB10183466_REV02 to get the engineering bootloader rev4.
Then I tried to flash G920FXXU3COI9_G920FOXA3COJ1_G920FXXU3COI9_HOME but it failed at sboot.bin device 4 binary 3 which prooves that even engineering bootloader prevents downgrade.
Then I tried to flash G920FXXU3COI9_G920FOXA3COJ1_G920FXXU3COI9_HOME without sboot.bin, cm.bin and modem.bin => it worked (not stuck at Samsung logo anymore).
My fingerprint scanner is not working but baseband is here (IMEI ok).
So I have kind of a "hybrid Lollipop" G920FXXU3COI9_G920FXXU4BPF1 but that's ok for what I wanted to do
EDIT: CF-Auto-Root-zeroflte-zerofltexx-smg920f doesn't seem to work when using engineering bootloader => I guess I'll have to find a new way to root the phone :-S
so any good way to do it ? because nougat is bad
Finally I got it rooted using TWRP and flashing SuperSU
So, to sum up, here is what I did to downgrade from stock G920FXXU4DPIL (6.0.1) to stock G920FXXU3COI9 (5.1.1):
(my guess is it will also work with Nougat)
1. Find combination firmware with engineering bootloader matching your current bootloader revision (mine was 4) - unfortunately this step may not be free
2. Find stock firmware you want to downgrade to (even if it is packed with an older sboot.bin bootloader)
3. Extract stock firmware, remove sboot.bin, cm.bin and modem.bin
4. Repack stock firmware to tar (with android unified toolkit for example) without the 3 .bin files
5. Flash combination firmware with Odin
6. Let it boot once and then go back to Odin
7. Flash repacked stock firmware with Odin
Additional steps to get root:
8. Download SuperSU (flashable zip)
9. Download TWRP
10. Flash TWRP with Odin
11. Enter recovery (TWRP) and flash SuperSU
Voilà !
Does it work with G925F (edge) too? Because I really want to downgrade to 5.1.1 as well because it was the best version for the Galaxy S6 and S6 edge in my opinion.. Battery life was VERY good, design was pretty amazing... and Samsung is blocking the downgrade (which is very STUPID!)
Okay I downgraded my S6 edge sucessfully to 5.1.1!
I missed that old UI soo mucchh thanks for your guidance
halloo7 said:
Does it work with G925F (edge) too? Because I really want to downgrade to 5.1.1 as well because it was the best version for the Galaxy S6 and S6 edge in my opinion.. Battery life was VERY good, design was pretty amazing... and Samsung is blocking the downgrade (which is very STUPID!)
Click to expand...
Click to collapse
Actually there is a reason Samsung doesn't want you to downgrade bootloader: I noticed that every bootloader update usually comes with modem/baseband update, which implies some modifications in the /efs partition as well. An older bootloader would then be unable to read new /efs partition, resulting in a null IMEI. That is why the correct way to downgrade is to flash the old system files but keeping current modem/baseband.
The real stupid thing here is that the stock MM bootloader prevents stock LP image to boot. Fortunately the engineering bootloader can bypass this
halloo7 said:
Okay I downgraded my S6 edge sucessfully to 5.1.1!
I missed that old UI soo mucchh thanks for your guidance
Click to expand...
Click to collapse
Cool !
:good:
Sometimes I get a Kernel Problem. The phone crashes randomly after the downgrade. How to fix this?
the only thing i want now is a way to make fingerprint sensor work. If anybody know something about it please reply.
qasim799 said:
the only thing i want now is a way to make fingerprint sensor work. If anybody know something about it please reply.
Click to expand...
Click to collapse
I think fingerprint sensor is somehow related to something inside cm.bin (cryptography management). As long as we don't get cm.bin matching both bootloader version and system image version at the same time, I don't see a way to make it work :crying:
couitchy said:
I think fingerprint sensor is somehow related to something inside cm.bin (cryptography management). As long as we don't get cm.bin matching both bootloader version and system image version at the same time, I don't see a way to make it work :crying:
Click to expand...
Click to collapse
i flashed latest cm.bin from nougat it boots up but fingerprint sensor is still not working and with engineering bootloader, the rom crashes at certain apps and get really snapier when unlocking phone with pin or pattern. So i am back to nougat i gave up downgrading almost downloaded whole sammobile 5.1.1 firmwares non of them is having a B:5 K:2 S:2 bootloader I was expecting such rom because on Verizon S6 , there is a 5.1.1 firmware that successfully allows to get down with same latest sboot.bin and i still believe there is a firmware like that for our model too but it is really hard to find it.
couitchy said:
Finally I got it rooted using TWRP and flashing SuperSU
So, to sum up, here is what I did to downgrade from stock G920FXXU4DPIL (6.0.1) to stock G920FXXU3COI9 (5.1.1):
(my guess is it will also work with Nougat)
1. Find combination firmware with engineering bootloader matching your current bootloader revision (mine was 4) - unfortunately this step may not be free
2. Find stock firmware you want to downgrade to (even if it is packed with an older sboot.bin bootloader)
3. Extract stock firmware, remove sboot.bin, cm.bin and modem.bin
4. Repack stock firmware to tar (with android unified toolkit for example) without the 3 .bin files
5. Flash combination firmware with Odin
6. Let it boot once and then go back to Odin
7. Flash repacked stock firmware with Odin
Additional steps to get root:
8. Download SuperSU (flashable zip)
9. Download TWRP
10. Flash TWRP with Odin
11. Enter recovery (TWRP) and flash SuperSU
Voilà !
Click to expand...
Click to collapse
I've tried flashing the firmware without the binfiles but It just gets stuck on file analysis.
Greetings to anyone who reads this.
I'm from India and I've been using Jio network for a while without any data service problems. But due to weak signal in my area I switched to Vodafone network (4G) and now my mobile data speed is very low ( it won't exceed 20 kBps even when I get a strong signal ) and this happens only on Custom ROMs. I'm getting good speed in stock rom but after I flash any custom ROM my mobile data almost stops working.
So for now I've got no other way than to stick with the stock ROM which is really annoying...
Any help would be really appreciated!
Solution
Jerome Marshall said:
Greetings to anyone who reads this.
I'm from India and I've been using Jio network for a while without any data service problems. But due to weak signal in my area I switched to Vodafone network (4G) and now my mobile data speed is very low ( it won't exceed 20 kBps even when I get a strong signal ) and this happens only on Custom ROMs. I'm getting good speed in stock rom but after I flash any custom ROM my mobile data almost stops working.
So for now I've got no other way than to stick with the stock ROM which is really annoying...
Any help would be really appreciated!
Click to expand...
Click to collapse
First use the stock rom with june security patch on the moto g4 xda thread. On that post many commands are given to flash stock rom but use only the flash modem commands to flash modem firmware. Then without doing a wipe flash custom rom and applicable gapps. It would then work. I had the same problem as you are having. I got it solved by the above method.
k4k said:
First use the stock rom with june security patch on the moto g4 xda thread. On that post many commands are given to flash stock rom but use only the flash modem commands to flash modem firmware. Then without doing a wipe flash custom rom and applicable gapps. It would then work. I had the same problem as you are having. I got it solved by the above method.
Click to expand...
Click to collapse
Thanks for your reply.
But the above method doesn't seem to work for me. Here is what I did,
1. Flash the modem ( NON-HLOS.bin ) from the stock ROM ( build no: NPJ25.93-14 )
2. Flash latest rr build and gapps via twrp
3. Turned on the phone but still I had the same issue
4. Re-flash modem (NON-HLOS.bin)
Still I'm facing the same data issue.
Jerome Marshall said:
Thanks for your reply.
But the above method doesn't seem to work for me. Here is what I did,
1. Flash the modem ( NON-HLOS.bin ) from the stock ROM ( build no: NPJ25.93-14 )
2. Flash latest rr build and gapps via twrp
3. Turned on the phone but still I had the same issue
4. Re-flash modem (NON-HLOS.bin)
Still I'm facing the same data issue.
Click to expand...
Click to collapse
If this is the case try engineering mode on your moto g4 plus by dialing *#*#2486#*#* and then changing the radio power of your device. Try other relevant settings too. Maybe it works. And if it doesn't work still then contact jleeblanch on rr official thread. He may have a solution.
Jerome Marshall said:
Thanks for your reply.
But the above method doesn't seem to work for me. Here is what I did,
1. Flash the modem ( NON-HLOS.bin ) from the stock ROM ( build no: NPJ25.93-14 )
2. Flash latest rr build and gapps via twrp
3. Turned on the phone but still I had the same issue
4. Re-flash modem (NON-HLOS.bin)
Still I'm facing the same data issue.
Click to expand...
Click to collapse
U need to fully flash stock, run stock to make sure GPS, WiFi, 4g data works--only then do u wipe /system, /data, /cache and then flash custom ROM. This is because flashing custom ROMs only overwrite /system, /data, and the original stock rom fastboot flashing overwrite much more partitions including modem and its config files. Thus, custom ROMs can then use these files to make sure 2g, 3g, 4g, WiFi, voice, data, SMS, MMS, GPS all work correctly.
Hello,
I recently I unlocked my Moto X Style XT1572 and I have tried 3 different roms, but non of them boot successfully, every rom is just showing boot-animation and won't boot successfully, I have tried crdroid, resurrectionremix, official LineageOS 14.1 and now in my computer device name is XT1575?? and after re installation of few roms, internal storage is wiped automatically, only twrp folder left, all rom zips gone . . . .
Also recently display is changed in service center, I have changed 3 diffrent twrp versions latest twrp had an issue of error status 7 then I changed twrp to twrp-3.0.2-0-clark, I tried to install rom without gapps, but no success, then I tried to install with gapps. . no success at all, just show's boot-animation all time. . . . evey time I flased roms, all time I wiped delvik/art, data, system, cache. . .
Got this error while installing crdroid rom mount: failed to mount /dev/block/bootdevice/by-name/modem at /firmware device or resources busy but rom install successfully but wont boot . . .
Anyone explain whats wrong with my XT1572??
You need to downgrade the baseband. From Nougat to MM.
https://forum.xda-developers.com/moto-x-style/general/guide-flashing-stock-firmware-t3637235
fastboot flash modem NON-HLOS.bin
fastboot flash modem NON-HLOS.bin (Flash twice, if Prevalidation Error)
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
@razor17
dzidexx said:
You need to downgrade the baseband. From Nougat to MM.
https://forum.xda-developers.com/moto-x-style/general/guide-flashing-stock-firmware-t3637235
fastboot flash modem NON-HLOS.bin
fastboot flash modem NON-HLOS.bin (Flash twice, if Prevalidation Error)
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
@razor17
Click to expand...
Click to collapse
I am trying to install Nougat roms. . still I have to downgrade baseband?
Yes.
There isn't custom for N baseband. @razor17
You should read some threads before.
dzidexx said:
Yes.
There isn't custom for N baseband. @razor17
You should read some threads before.
Click to expand...
Click to collapse
Thank you so much @dzidexx my device boot successfully after flashing baseband , but why this error still show's in recovery "mount: failed to mount /dev/block/bootdevice/by-name/modem at /firmware device or resources busy"
razor17 said:
Thank you so much @dzidexx ...why this error still show's in recovery "mount: failed to mount /dev/block/bootdevice/by-name/modem at /firmware device or resources busy"
Click to expand...
Click to collapse
I don't know why but they are since I remember - 1st stable custom N. Not only MXP/S has it.
And what if i dont want to take a risk of downgrading to MM is there any other way to do so and are there any roms available or will be available based on N baseband.......please let me know thanks.
This is the only one for right now.
https://forum.xda-developers.com/showpost.php?p=74224484&postcount=901
razor17 said:
Hello,
I recently I unlocked my Moto X Style XT1572 and I have tried 3 different roms, but non of them boot successfully, every rom is just showing boot-animation and won't boot successfully, I have tried crdroid, resurrectionremix, official LineageOS 14.1 and now in my computer device name is XT1575?? and after re installation of few roms, internal storage is wiped automatically, only twrp folder left, all rom zips gone . . . .
Also recently display is changed in service center, I have changed 3 diffrent twrp versions latest twrp had an issue of error status 7 then I changed twrp to twrp-3.0.2-0-clark, I tried to install rom without gapps, but no success, then I tried to install with gapps. . no success at all, just show's boot-animation all time. . . . evey time I flased roms, all time I wiped delvik/art, data, system, cache. . .
Got this error while installing crdroid rom mount: failed to mount /dev/block/bootdevice/by-name/modem at /firmware device or resources busy but rom install successfully but wont boot . . .
Anyone explain whats wrong with my XT1572??
Click to expand...
Click to collapse
I had that problem when going from stock 7.0 back to Lineage OS 14.1. The issue for me was that the new modem firmware in stock 7.0 stopped the Lineage OS install dead. It looped on the logo indefinitely. Even though Lineage OS is 7.1.2 the included modem firmware was still from marshmallow 6.0. No stock modem firmware is available to fix this yet without a stock flashable 7.0 image (not OTA). To reinstall Lineage OS I had to downgrade from stock 7.0 to stock 6.0 and then reflash Lineage OS 14.1 and OpenGApps.
ptn107 said:
I had that problem when going from stock 7.0 back to Lineage OS 14.1. The issue for me was that the new modem firmware in stock 7.0 stopped the Lineage OS install dead. It looped on the logo indefinitely. Even though Lineage OS is 7.1.2 the included modem firmware was still from marshmallow 6.0. No stock modem firmware is available to fix this yet without a stock flashable 7.0 image (not OTA). To reinstall Lineage OS I had to downgrade from stock 7.0 to stock 6.0 and then reflash Lineage OS 14.1 and OpenGApps.
Click to expand...
Click to collapse
I have done everything, I flashed stock firmware, everything working good but after hour my phone is completely dead, I have no idea what happened xD
Mine always shows that on rom flashes. Wireless works fine.
ptn107 said:
I had that problem when going from stock 7.0 back to Lineage OS 14.1. The issue for me was that the new modem firmware in stock 7.0 stopped the Lineage OS install dead. It looped on the logo indefinitely. Even though Lineage OS is 7.1.2 the included modem firmware was still from marshmallow 6.0. No stock modem firmware is available to fix this yet without a stock flashable 7.0 image (not OTA). To reinstall Lineage OS I had to downgrade from stock 7.0 to stock 6.0 and then reflash Lineage OS 14.1 and OpenGApps.
Click to expand...
Click to collapse
Downgrading from Stock7.0 to Stock6.0 is dangerous as it becomes brick in the future.
Since Motorola does not support downgrading, bootloader will be corrupted after OTA upgrade from 6.0 to 7.0.
TA1513 said:
Downgrading from Stock7.0 to Stock6.0 is dangerous as it becomes brick in the future.
Since Motorola does not support downgrading, bootloader will be corrupted after OTA upgrade from 6.0 to 7.0.
Click to expand...
Click to collapse
Although it only becomes a brick if you downgrade, then update to ota in the future right? I thought it wasn't dangerous if you were only going the custom ROM route
dzidexx said:
You need to downgrade the baseband. From Nougat to MM.
https://forum.xda-developers.com/moto-x-style/general/guide-flashing-stock-firmware-t3637235
fastboot flash modem NON-HLOS.bin
fastboot flash modem NON-HLOS.bin (Flash twice, if Prevalidation Error)
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
@razor17
Click to expand...
Click to collapse
which one is for USA?
EDIT: I'm guessing I flashed the wrong one, because I cant get any service now.... CLARK_RETUS_6.0_MPHS24.49-18-8_cid9_subsidy-DEFAULT_CFC.xml
Well, finally got Lineage official nighty to boot. Lots of issues though, when I reboot my battery will lose 30% each time, then when it gets to about 20ish percent the phone gets stuck on the bootloader is unlocked screen, holding the power button finally reboots it but then the phone says "no sim installed", I guess this is why I thought I had no service before. Something is real messed up.
Spencervb256 said:
Although it only becomes a brick if you downgrade, then update to ota in the future right? I thought it wasn't dangerous if you were only going the custom ROM route
Click to expand...
Click to collapse
You are correct. It only becomes a problem if you were to re-upgrade to 7 via the official OTA after downgrading stock to stock. I made a twrp backup of the official 7 release for the xt1575 so I will never need to go with an official update ever. You can flash custom roms from 6 to 7 and back again if you wish. This was the last official update anyway.
Custom rom for moto x style XT1572
Recently i unlocked the bootloader of my XT1572. As same as mentioned above i tried 3 nougat rom. But it failed. Atlast i flashed CM 13 into my phone. It loaded successfully. First it was all fine. But now a days it having some issues. Can anyone please please suggest a stable rom for moto XT1572..........................?