So the other day I was being an idiot and accidentally selected usa radio band in "Select Radio Band" menu (* # *#4636# * # * menu) and lost my 2g and 3g network, I had 4g only. Fellow redditor linked me a fix which was fastboot commands as following:
adb reboot bootloader
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
Did it using mfastboot because regular fastboot won't work on Windows 10 in my case. That fixed my network problem but apparently messed up my phone in some other way because now I can't install Nougat update, I get this error
http://imgur.com/YsFhdqr. I would really like to avoid rma and being 4 weeks without my phone. Any help would be appreciated. I've tried flashing stock firmware but there I also got errors, probably because Windows 10. Can I try flashing the modem? Something else? Please help. Thanks.
You might have to flash a modem for your device. You messed up the radio partition by deleting the modems. Now anytime you try to flash a stock signed firmware, it detects that the system is modified and thus cannot flash. Is it rooted?
ironbesterer said:
You might have to flash a modem for your device. You messed up the radio partition by deleting the modems. Now anytime you try to flash a stock signed firmware, it detects that the system is modified and thus cannot flash. Is it rooted?
Click to expand...
Click to collapse
What files should I flash then? It is not rooted, completely stock.
Anyone?
ViperX85 said:
What files should I flash then? It is not rooted, completely stock.
Click to expand...
Click to collapse
Just being curious, where did you buy the phone? If it is Amazon (i noticed from Motorola forums that you are from Germany), just return the phone.
yekollu said:
Just being curious, where did you buy the phone? If it is Amazon (i noticed from Motorola forums that you are from Germany), just return the phone.
Click to expand...
Click to collapse
No, bought it in a store. Yes, i'm from Germany.
ViperX85 said:
No, bought it in a store. Yes, i'm from Germany.
Click to expand...
Click to collapse
Just try returning the phone in the store (Saturn?), they usually do not ask questions. And do you have a Insurance?
Whats the error when flashing the stock image? The modem is included in the stock firmware image (NON-HLOS.bin) and therefore should be restorable to stock.
tomparr said:
Whats the error when flashing the stock image? The modem is included in the stock firmware image (NON-HLOS.bin) and therefore should be restorable to stock.
Click to expand...
Click to collapse
http://imgur.com/YsFhdqr
Already flashed NON-HLOS.bin, no luck, still get the same error. Maybe because I flashed it from an older firmware image?
ViperX85 said:
http://imgur.com/YsFhdqr
Already flashed NON-HLOS.bin, no luck, still get the same error. Maybe because I flashed it from an older firmware image?
Click to expand...
Click to collapse
Your screenshot is from the nougat update but you mentioned an error when flashing the stock firmware with fastboot, what was this error? Have you also flashed fsg.mbn, which is the second part of the modem? The older firmware might be the problem, I don't remember if the modem was updated with the security patches. You could also try and flash the system sparsechunks from the older firmware image and then do the update marathon back to the december update.
yekollu said:
Just try returning the phone in the store (Saturn?), they usually do not ask questions. And do you have a Insurance?
Click to expand...
Click to collapse
Yes, Saturn and I was just there asking about rma, will do it next week. I don't have insurance. Would it help more than just rma?
ViperX85 said:
Yes, Saturn and I was just there asking about rma, will do it next week. I don't have insurance. Would it help more than just rma?
Click to expand...
Click to collapse
Back in the day, there was an error with my Moto razr i (entirely my fault and it would not update to JB, and the audio would not automatically switch to headphones). I told them i do not understand why it would not update, they took it for repair after a week they told me they could not repair it and offered me replacement.
Next time, buy your phone from Amazon. It is cheaper than Amazon and if you get an insurance, it covers water damage (not entirely ethical but Amazon does not work that way either )
yekollu said:
Back in the day, there was an error with my Moto razr i (entirely my fault and it would not update to JB, and the audio would not automatically switch to headphones). I told them i do not understand why it would not update, they took it for repair after a week they told me they could not repair it and offered me replacement.
Next time, buy your phone from Amazon. It is cheaper than Amazon and if you get an insurance, it covers water damage (not entirely ethical but Amazon does not work that way either )
Click to expand...
Click to collapse
I was thinking of Amazon but the phone was generally too expensive for me at the moment (bought it last November) so I went to Saturn and bought in rates, 50€/month.
tomparr said:
Your screenshot is from the nougat update but you mentioned an error when flashing the stock firmware with fastboot, what was this error? Have you also flashed fsg.mbn, which is the second part of the modem? The older firmware might be the problem, I don't remember if the modem was updated with the security patches. You could also try and flash the system sparsechunks from the older firmware image and then do the update marathon back to the december update.
Click to expand...
Click to collapse
The error was something in cmd, something about security downgrade can't remember anymore, tried to flash from older firmware, can't find the actual firmware that I have. I think I flashed fsg.mbn but I'm not sure. Can you tell me all the files to flash modem?
ViperX85 said:
The error was something in cmd, something about security downgrade can't remember anymore, tried to flash from older firmware, can't find the actual firmware that I have. I think I flashed fsg.mbn but I'm not sure. Can you tell me all the files to flash modem?
Click to expand...
Click to collapse
Just fsg.mbn and NON-HLOS.bin. The following commands in fastboot should be enough.
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Related
This is a nand that I created with twrp. It is completely stock and unrooted. By restoring this, flashing the stock At&t modem and flashing stock KXE21.187-42 recovery, you will be left with a complete stock unrooted kitkat Moto X XT1095 capable of taking the ota.
Nand bu KXE21.187-42
MD5-e9ce965a3a0370a47effa5005d5a07db
https://mega.co.nz/#!HQUlBKJa!VHsKA4miBIquiHGFVMxz8uxgAAyV0UFCVBWlK-uwDLQ
Stock KXE21.187-42 Recovery
MD5-a5673547c4a78b255cce3c64aa854a2b
https://mega.co.nz/#!SMcxwSbQ!jN2Y8EtryTlKXWgUPYg8Xi7pQihX9TsXd-PjJ6EPfSA
Modem
MD5-d1c083abf3ad22aa53c8a0346a0bf8fc
https://mega.co.nz/#!HAtRiBBC!Q7LmNt2NvPYmhGl8sA7yE3wA1Fdm71B4Kc-Z4Zss-YA
1. Place nand in the backups of your twrp recovery
2. Restore with twrp
3. Factory data/reset
4. Flash At&t modem (fastboot flash modem NON-HLOS.img)
5. Reboot to fastboot mode
6. Flash stock recovery (fastboot flash recovery recovery_victara_KXE21.187-42.img).
7. Reboot
If you want the OTA.... adb sideload (you can find the OTA file on another thread).
IF you follow the directions as I have laid out, you will have a completely stock, unrooted-fresh install of kitkat. You now should be able to safely take the ota using adb sideload.
This has been tried by myself multiple times successfully. This is only for the XT1095 variant. If you are crazy enough to try it on another variant, please post your results.
I am not responsible for anything that happens to your device. I will try and answer any questions as long as I have the time. Hit "thanks" if this helps.
Is it required to flash the att modem if i use tmobile?
Directions are not clear - especially regarding radio
expertzero1 said:
Is it required to flash the att modem if i use tmobile?
Click to expand...
Click to collapse
Yes, it's basically a prerequsite for the ota to flash. If you have no plan on flashing the ota, then you can use the radio of your choice.
Sdobron said:
Directions are not clear - especially regarding radio
Click to expand...
Click to collapse
Not to sure what you are saying.
fastboot flash modem NON-HLOS.img
That's pretty clear to me. Im guessing if you can flash a recovery, you can flash the modem, performed by fastboot.
rsa 329 said:
Not to sure what you are saying.
fastboot flash modem NON-HLOS.img
That's pretty clear to me. Im guessing if you can flash a recovery, you can flash the modem, performed by fastboot.
Click to expand...
Click to collapse
My pure edition, XT1095 came out of the box with T Mobile baseband / modem. Not sure why the ota would need AT&T (also had no issues sideloading the lollipop update)
I am pretty sure it is only required if you used the multitool which has a different modem included. This modem is not compatible with the 5.0 OTA.
nineismine said:
I am pretty sure it is only required if you used the multitool which has a different modem included. This modem is not compatible with the 5.0 OTA.
Click to expand...
Click to collapse
Which modem? The modem I have posted here? If thats what you are talking about you havent any idea what you are talking about.
I have done exactly what ive posted here multiple times. Use any other modem other than this one and the ota will fail.
As far as why people are calling it the att modem confuses me as well.
The multi tool flashes a 55R while this modem flashes 57R.
Sdobron said:
My pure edition, XT1095 came out of the box with T Mobile baseband / modem. Not sure why the ota would need AT&T (also had no issues sideloading the lollipop update)
Click to expand...
Click to collapse
I started this thread to return your XT1095 to stock unrooted, hence the title.
Since there are no factory images at the moment, I posted what worked for me.
Dont comment if you dont agree, but i assure you this method works just fine.
rsa 329 said:
Which modem? The modem I have posted here? If thats what you are talking about you havent any idea what you are talking about.
I have done exactly what ive posted here multiple times. Use any other modem other than this one and the ota will fail.
As far as why people are calling it the att modem confuses me as well.
The multi tool flashes a 55R while this modem flashes 57R.
Click to expand...
Click to collapse
The modem included in the Multitool as I inferred. If you flashed back to stock or used the image from the multitool you get the invalid modem b00 error. After which you have to use the AT&T modem in order for the OTA to complete successfully.
the radio point is mute since graffixnyc posted the stock pure edition modem on his site. The modem image he posted is a direct backup from his brand new Pure Edition
nineismine said:
The modem included in the Multitool as I inferred. If you flashed back to stock or used the image from the multitool you get the invalid modem b00 error. After which you have to use the AT&T modem in order for the OTA to complete successfully.
Click to expand...
Click to collapse
Correct, the modem I have linked was directly from graffix.
holy cow downloads from Mega are crawling for me. I heard a rumor from a friend of a friend that a certain OTA from an un-said company for an un-said device is going out 'very soon' and I want to be 100% stock before it goes out. Just in case it's for the moto X.
can I ask how you got back to 100% stock? In your previous thread (TWRP Backup of Lollipop) you mentioned that you couldn't do a backup of stock. I guess I just want to know that your stock backup of 4.4.4 isn't an un-rooted 4.4.4. I'm looking for never-been-rooted 4.4.4.
got this to work last night.
working great! sideloaded the ota!
flashed the modem after sideloading the ota.
Official factory image is now available from Motorola! https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
edit: deleted, nevermind
holtenc said:
holy cow downloads from Mega are crawling for me. I heard a rumor from a friend of a friend that a certain OTA from an un-said company for an un-said device is going out 'very soon' and I want to be 100% stock before it goes out. Just in case it's for the moto X.
can I ask how you got back to 100% stock? In your previous thread (TWRP Backup of Lollipop) you mentioned that you couldn't do a backup of stock. I guess I just want to know that your stock backup of 4.4.4 isn't an un-rooted 4.4.4. I'm looking for never-been-rooted 4.4.4.
Click to expand...
Click to collapse
My 4.4.4 was rooted, and I just experimented with all the info that everyone was posting the day the 5.0 went live. I was able to unroot and flash a file that 0.0 had posted in the thread that graffix had started. Anyway long story short between that and experimenting with the recovery and modems I was able to get my 4.4.4 to take the OTA with no problems. Since the OTA checks file structure and recovery, modem, etc....I am assuming it is unrooted stock. The way I look at it, If the OTA will flash with my experiment, so should the actual release. That is just my logic anyway.
Thank you for putting this guide together. Everything worked flawlessly. Thank you.
Hey guys, I need a little help to figure out what's going on with my dad's nexus 4.
When he tried to update to the newest version of Lollipop avaiable, the phone entered in a bootloop.
I tried flashing a factory image manually using this guide, but after it was done, the phone booted and it was still in a bootloop (stuck on the colored circles moving). I tried wiping data/factory reset afterwards and the phone remained in a bootloop state.
I also tried using the nexus root toolkit by WugFresh using the option "Flash Stock/Unroot" with the Soft brick/bootloop box checked, but it also didn't solve the problem.
There were no error messages when flashing, and I waited for 30 ~ 45 minutes after each flashing attempt to make sure that the phone was in fact in a bootloop.
I don't know what to do anymore... Can it be a hardware problem?
Did you manually flash the userdata.img file? If not, flash the file and, immediately after flashing the file in fastboot, go into stock recovery, perform a factory wipe, and reboot.
audit13 said:
Did you manually flash the userdata.img file? If not, flash the file and, immediately after flashing the file in fastboot, go into stock recovery, perform a factory wipe, and reboot.
Click to expand...
Click to collapse
I manually flashed the files and did a factory wipe, but it didn't solve the problem.
Did you flash the userdata.img file?
audit13 said:
Did you flash the userdata.img file?
Click to expand...
Click to collapse
yes, I did exactly as you said.
Hmm, usually flashing the userdata file and wiping via stock recovery works. Have you tried different factory images?
audit13 said:
Hmm, usually flashing the userdata file and wiping via stock recovery works. Have you tried different factory images?
Click to expand...
Click to collapse
I tried to downgrade to 5.0 and 4.4.4 , but on both of them I get stucked on the boot animation.
Try 4.1.1? If it works, it is possible that the emmc chip is damaged.
audit13 said:
Try 4.1.1? If it works, it is possible that the emmc chip is damaged.
Click to expand...
Click to collapse
On google's site, the factory images avaiable start from version 4.2.2, I'll try using that.
Okay. Good luck.
audit13 said:
Okay. Good luck.
Click to expand...
Click to collapse
So, I was able to downgrade to 4.2.0 version using the toolkit that I mentioned. The phone seems to be working fine now. What does that mean? Can I try to update to lollipop without fear?
You can try updating via ota updates to kk and LP but, if it gets stuck again on kk, I think the emmc chip is a problem.
audit13 said:
You can try updating via ota updates to kk and LP but, if it gets stuck again on kk, I think the emmc chip is a problem.
Click to expand...
Click to collapse
Okay, thank you very much for the help!
You're welcome. We're all here to help each other out.
Hopefully, you'll be able to upgrade to kk or LP.
audit13 said:
You're welcome. We're all here to help each other out.
Hopefully, you'll be able to upgrade to kk or LP.
Click to expand...
Click to collapse
I couldn't upgrade to 4.3 jellybean. It got stuck on a bootloop. So it means that it is a hardware problem?
Unfortunately, it appears that the emmc chip is damaged.
audit13 said:
Unfortunately, it appears that the emmc chip is damaged.
Click to expand...
Click to collapse
So, nothing I can really do about it?
Not that I know of.
I've gotten no help at all with this. Very unlike this forum. My phone is a kltevew, which is straight talks version of a g900v. I need help, there are lots of great looking Roms that require you to have mm firmware I'd like to try!
Not sure why I'm getting g no responses on this. Surely someone must know something... The only response I got was not only not helpful but jerky and obnoxious. Doesn't anyone know how to upgrade the firmware on my phone? (And no, google has no answers for me on this.. I look everyday)
ddjr said:
Not sure why I'm getting g no responses on this. Surely someone must know something... The only response I got was not only not helpful but jerky and obnoxious. Doesn't anyone know how to upgrade the firmware on my phone? (And no, google has no answers for me on this.. I look everyday)
Click to expand...
Click to collapse
Download it with samfirm http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647 (Model= SM-G900V Region= VZW) or from sammobile http://www.sammobile.com/firmwares/database/SM-G900V/ , do you know how to flash firmware with odin?
I do. Thanks so much for responding. Every time I try with Odin, a few different releases, it always gives me the error message fail. Can it be done with flashfire?
What stands in the log of odin when the flash completes?
Ill have to do it again to see... Be back in a bit!
I think it says FAIL! modem but I'll have to run it again... Brb
Last night I used flash fire to install firmware. That didn't get past the red Verizon logo, so I put twrp on it with Odin. Twrp showed it as dpd1, but it just wouldn't boot. So I wiped it once and flashed a ROM that requires mm firmware. Same thing, justbootloop. So I put stock back on it, then mokee 6.0.1. which works, I'm just not on mm firmware and all the great new roms are still unavailable to me.
ddjr said:
Last night I used flash fire to install firmware. That didn't get past the red Verizon logo, so I put twrp on it with Odin. Twrp showed it as dpd1, but it just wouldn't boot. So I wiped it once and flashed a ROM that requires mm firmware. Same thing, justbootloop. So I put stock back on it, then mokee 6.0.1. which works, I'm just not on mm firmware and all the great new roms are still unavailable to me.
Click to expand...
Click to collapse
Have you enabled the option to flash bootloader on flashfire setting?
What? No, I haven't... but do do right now. Thanks for the tip! Actually, where would I find it?
So would I do it in this order? Flash the dpd1 bootloader, then modem, them rom, then jrkruse patch? All in flash fire?
ddjr said:
So would I do it in this order? Flash the dpd1 bootloader, then modem, them rom, then jrkruse patch? All in flash fire?
Click to expand...
Click to collapse
It's in setting of flashfire...but only do it if odin doesn't work because do it from flashfire is more riskiy...
1)do a backup
2)check the bootloader flash option
3)install the firmware with all the wipe except internal storage(it mean that flashfire delete /data excluding /data/media/0 (sdcard) but include it in your backup copy because you never know )
4)wait till reboot skip setup wizard "spamming" the next button then install the rom with flashfire or twrp
On the flashfire site i found this:
Flash bootloaders
"This setting controls if FlashFire will attempt to flash bootloader partitions. By default, bootloader partitions are only read and never written. Even when enabled, flashing bootloader partitions may not succeed - many devices have protections in place against the bootloaders being overwritten.
Please note that flashing bootloaders is extremely dangerous. Any bug, error, or failure may result in an unrecoverable hard-brick. Do not use this feature unless you know exactly what you are doing.
Due to the danger of this feature, it is automatically turned off every time FlashFire starts. You have to manually re-enable it every time you want to use it.
If you must flash bootloaders, it is advised to use a bootloader-based flashing tool such as fastboot or ODIN to do it, as these are the safest methods. OTAs may also update bootloaders, and though slightly less safe than fastboot/ODIN, it is still much safer than having FlashFire flash bootloader partitions directly."
So i suggest to try to flash the firmware directly from odin first
No dice... still doesn't boot up past the red Verizon logo
ddjr said:
No dice... still doesn't boot up past the red Verizon logo
Click to expand...
Click to collapse
did you install the firmware in the "AP" box on odin? (after you factory reset your phone)
I did. At this point guess I'm lucky I haven't bricked my phone. Ive tried every possible combination, nothing works!
ddjr said:
I did. At this point guess I'm lucky I haven't bricked my phone. Ive tried every possible combination, nothing works!
Click to expand...
Click to collapse
Redownload the firmware extract it again,factory reset your phone,and try to install the firmware,maybe it's a bad download
Should I be flashing a kernel too? Will it even start/boot without the right kernel?
find out if you phone is refurbished. to install stock ROM you would need the main board and boot to be the same model.
if it's not, then you just need to install bootloader/modem without full ROM. look around in xda for bootloader/modem.
In my view:
I have noticed a few of you are reverting to stock and getting hard brick , I believe this cannot be fixed this is after either rooting or after installing stock . This will only happen over ota as it affects ur system partition and modem . Pls do not update on stock ROMs unless you are sure of the software number matching new software , even a carrier software with a letter difference can destroy your phone. Therefore , either don't unlock your phone or don't update via OTA
I got hardbricked device when i was updating an security patch in stock rom, unlocked bootloader...
Any fixes or solution? Blank flash or QFIL files?
CypherPotato said:
Any fixes or solution? Blank flash or QFIL files?
Click to expand...
Click to collapse
If you can still get into fastboot, try flashing TWRP and some custom ROM.
If not, your device is bricked beyond repair.
BtbN said:
If you can still get into fastboot, try flashing TWRP and some custom ROM.
If not, your device is bricked beyond repair.
Click to expand...
Click to collapse
Nope not work.
Hi, I have a S8 that is currently flashed with firmware version G950FXXU3CRGB (July). For research purposes I would like to flash this firmware back to G950FXXU1CRD7 (April). Is this possible? Odin keeps giving failed messaged on either sboot.img or boot.img. I tried building a new AP package which only includes system.img, but this one also fails...
Is it at all possible, or is the bootloader/Download-mode preventing me from downgrading?
thereof said:
Hi, I have a S8 that is currently flashed with firmware version G950FXXU3CRGB (July). For research purposes I would like to flash this firmware back to G950FXXU1CRD7 (April). Is this possible? Odin keeps giving failed messaged on either sboot.img or boot.img. I tried building a new AP package which only includes system.img, but this one also fails...
Is it at all possible, or is the bootloader/Download-mode preventing me from downgrading?
Click to expand...
Click to collapse
You cannot downgrade firmware with a lower bootloader version than what is installed on your phone ie: your current bl is ver 3 and your trying to flash bl ver 1
spawnlives said:
You cannot downgrade firmware with a lower bootloader version than what is installed on your phone ie: your current bl is ver 3 and your trying to flash bl ver 1
Click to expand...
Click to collapse
That's what I expected... I'm guessing this also goes for the system image itself? I don't really care about the bootloader, but I would like the system image to be as close as possible to that of April (especially `init`, `vold`, `blkid` and `zygote`). Otherwise I'm just going to search for a non-updated second hand phone.
thereof said:
That's what I expected... I'm guessing this also goes for the system image itself? I don't really care about the bootloader, but I would like the system image to be as close as possible to that of April (especially `init`, `vold`, `blkid` and `zygote`). Otherwise I'm just going to search for a non-updated second hand phone.
Click to expand...
Click to collapse
This is one of the many reasons why I'm still on nougat ( ver 1 bl )- the inability to downgrade. I would also say going the other way holds true too upgrading the firmware without the upgrading the bootloader version would also cause issues.
I've also heard that doing a complete nandroid backup then upgrading then trying to restore does not work either.