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.
Hi all,
I'm currently running Temasek's CM12 by Kornfed, great rom, but I wanted to update my bootloader and modem to the latest version BNL7, as I'm currently still on ANG2.
I can't however seem to flash the damn thing, tried Odin and says the flash is ok, but i'm still on my old bootloader and modem. With Mobile Odin i get an error "Memory Protection In Place" so i guess i'm missing something.
Any1 else having or had this problem?
g900m
Im having somethimg similar to that. Im using mobileodin 4.20 and cant update modem. Everything is in new update except modem have just tries it 3 times and still on old modem.. but mine doesnt show anything about errors
I have read that having Knox tripped blocks modem updates, which you would of tripped Knox by flashing CyanogenMod.
The obvious thing to do is to download the official BNL7 rom flash it via Odin using a PC and your then have the BNL7 bootloader and modem, flash a custom recovery+ temasek rom. Job done!
vuittion said:
The obvious thing to do is to download the official BNL7 rom flash it via Odin using a PC and your then have the BNL7 bootloader and modem, flash a custom recovery+ temasek rom. Job done!
Click to expand...
Click to collapse
Last time i tried it didn't boot, this time i left the battery out for a bit and now it boots just fine and everything seems to be updated ^^
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.
Everytime I try to boot into system, it freezes and then restarts. I just flashed lollipop OC4 rom through FlashFire? Help please
safwanz1 said:
Everytime I try to boot into system, it freezes and then restarts. I just flashed lollipop OC4 rom through FlashFire? Help please
Click to expand...
Click to collapse
Did you uninstall safestrap before you use flashfire?
Do you use the rooted lolli rom mentioned in the guide or the custom lolli rom. If you use custom lolli, is that rom mentioned that it is flashfire compatible?
I understand you are on NC1 bootloader so in order to OC4 working properly, OC4 bootloader need to be flashed via odin.
If you try everything and did not work, go back to NB1 and start from there. Use the NB1 firmware that I mentioned before.
sway8966 said:
Did you uninstall safestrap before you use flashfire?
Do you use the rooted lolli rom mentioned in the guide or the custom lolli rom. If you use custom lolli, is that rom mentioned that it is flashfire compatible?
I understand you are on NC1 bootloader so in order to OC4 working properly, OC4 bootloader need to be flashed via odin.
If you try everything and did not work, go back to NB1 and start from there. Use the NB1 firmware that I mentioned before.
Click to expand...
Click to collapse
So dude, when I went into download mode, everytime I tried to place that ALLAT&T file into the AP slot, it would cause Odin to freeze and not respond. Naturally, I got angry and decided to reboot into system and magically, I could use the OS again. Now I think I'm going to flash the bootloader like you said
safwanz1 said:
So dude, when I went into download mode, everytime I tried to place that ALLAT&T file into the AP slot, it would cause Odin to freeze and not respond. Naturally, I got angry and decided to reboot into system and magically, I could use the OS again. Now I think I'm going to flash the bootloader like you said
Click to expand...
Click to collapse
I am sure you did extract the .md5 from the .rar. The latest odin is Version 3.10.7 but I am using version 3.10.6 for that .md5 and it went well too. Try with different odin then.
sway8966 said:
Did you uninstall safestrap before you use flashfire?
Do you use the rooted lolli rom mentioned in the guide or the custom lolli rom. If you use custom lolli, is that rom mentioned that it is flashfire compatible?
I understand you are on NC1 bootloader so in order to OC4 working properly, OC4 bootloader need to be flashed via odin.
If you try everything and did not work, go back to NB1 and start from there. Use the NB1 firmware that I mentioned before.
Click to expand...
Click to collapse
sway8966 said:
I am sure you did extract the .md5 from the .rar. The latest odin is Version 3.10.7 but I am using version 3.10.6 for that .md5 and it went well too. Try with different odin then.
Click to expand...
Click to collapse
Right dude, I just flashed the NC1 flasher and then i tapped reboot, now it's been on the custom unlock screen for a few minutes, what should I do?
Now i rebooted the device and I cant get into system or safestrap.
safwanz1 said:
Right dude, I just flashed the NC1 flasher and then i tapped reboot, now it's been on the custom unlock screen for a few minutes, what should I do?
Now i rebooted the device and I cant get into system or safestrap.
Click to expand...
Click to collapse
Wow, NC1 flasher is to use safestrap in lollipop. It only flash the NC1 kernel.
Are you in Kitkat or lollipop. If you were in your lollipop you need to update your lollipop bootloader.
As I said before, if your phone went to softbrick just flash the NB1 firmware via odin.
I swear, you are a legend, an absolute god. The amount of help and experience you have given me, if only I could pay you (I'm 15, so I can't make a PayPal yet) Right now I'm on Albe95's Note 5 port rom.
SOLVED! Edit end of the post.
Hello guys i'm having a weird problem,
I had installed the S6 Portc 5.0.1 for a almost a year without any problem but recently i had to go Stock NB1 for testing a SIM CARD Carrier that i was getting "Invalid SIM Card" and it was the same thing, no biggies, perphas that carrier is not compatible with this phone, i tried a couple of guide thinking my phone was not "full" unlocked and ended it up locking the phone instead, lol. Anyway, i managed to unlock it again, so i go ahead and try to update my TW to OK2 and now i can't? Any ROM that i flash trough FlashFire o SafeStrap fails at installing(FF: Hangs at booting, SS: it yells something like symlinks errors). Odin Stock install correctly and Update through to stock recovery like NB1 to NJ4 and so on installs good too.
What do you guys think? I was thinking about to one more time to ODIN Stock NB1 Rooted but with a PIT aswell to see if that fixes my problem but i'm really scared of using the PIT file.
Things i have tried:
* NB1 to NC1: TR>SuperSU>Stock OK2 with FF = Hangs no install
* NB1 to NC1: TR>SuperSU>Stock OK2 with SS = Symlinks errors no install
* ODIN Stock NB1 Root = Good, installs correctly
* OTA's NB1 to OK2 = Good, but no SuperSU, Custom Roms and VERY SLOW Install process.
* OTA's NB1 to OK2 = KingRoot > SS > Custom ROM = Sysmlink error no install
* PIT File + Stock NB1 Stock Rooted ODIN = Good, Tried to install OK2 Keep Root with FF = Hangs, no install.
I'm out of ideas...
EDIT: That's the log from FF attached.
Solution: Yes! Solved! After all the struggle someone posted this interesting post. I tried to install that version and didn't help because the app closed it self everytime i tried to open it... BUT it turns out chainfire put a timebomb to February 01 2017 in this version (v0.53) (You can read it here) So, i changed my time/date before that time and voila! Everything went smooth! Woohoo!. Thank you guys.
So you're on NB1? I would wipe the the phone clean then just take the OTA to the latest firmware and update that way then try installing a ROM.
StoneyJSG said:
So you're on NB1? I would wipe the the phone clean then just take the OTA to the latest firmware and update that way then try installing a ROM.
Click to expand...
Click to collapse
I already tried that sadly, didnt work. i can't install anything that is not stock.
EDIT: Even the OK2 Stock from muzniz through FF doesnt install
Does these phone have a locked bootloader? If it does, only custom roms based on a stock ROM will work afaik.
audit13 said:
Does these phone have a locked bootloader? If it does, only custom roms based on a stock ROM will work afaik.
Click to expand...
Click to collapse
It's a S6 Port based on TW ROM, it's a TW ROM. I tried OK2 with FF/SS that i previously installed a year ago without any problem but know fails, i don't know why.
This one: https://forum.xda-developers.com/galaxy-s4-att/general/how-to-update-to-i337oc3-5-0-1-keeproot-t3075814
and this one: https://forum.xda-developers.com/galaxy-s4-att/development/port-albe95-s6-port-4-6-updt-30-10-15-t3241212
The custom ROM has to be based on a stock att s4 ROM, not a port from another Samsung ROM.
audit13 said:
The custom ROM has to be based on a stock att s4 ROM, not a port from another Samsung ROM.
Click to expand...
Click to collapse
Thank you for the help but:
* I had this ROM in my phone before, it's compatible with I337 Locked Bootloader you can check the description.
* I still can't install the other ROM that's specific for ATT I337 (The OK2 Rooted Keep linked in my previous post). It's like Stock with Root ready.
I understand now.
Could it possibly be a hardware issue? I'm not sure since I don't have an att s4.
Edit: Congratulations on your success and sharing your solution.