Database Develop

Backup modem / flash new modem

First, i'd like to thank our atrix hd wise guys for all the knowledge you've put on this forum .
Now to the issue at hand, i'm currently running CM10.2 nightly 05 oct. I've been having modem crashes for weeks now as described in this post:
http://forum.xda-developers.com/showthread.php?t=2385048&page=24
Weird thing is, i only get these crashes when in the area where i work. Back at home i get no modem crashes at all.
My Baseband is MB886_BP_100740.071.65.04P
I'm considering flashing mexico retail modem (which has good user opinions) using the procedure described in this thread:
http://forum.xda-developers.com/showthread.php?t=2233871
I've figured the backup process for the modem should be something like this:
Code:
dd if=/dev/block/mmcblk0p1 of=/storage/sdcard1/modem.bin bs=4096
So, now with the questions:
1. Before proceeding, i'd like to know if this would be a correct backup procedure for my current modem files?
2. Would i be able to restore this newly created modem.bin file with fastboot in case mexican modem doesn't work/solve my problem?
3. From what i've researched, the mexican 4.1.2 modem file should be compatible with CM10.2 JB 4.3, am I correct?
Thanks in advance for any help on this!

From my experience with other phones, modems work regardless of android version. If that backup procedure is correct (which I have no clue if it is), you can restore it by reversing the command.
Sent from my MB886 using xda app-developers app

I went ahead and backed up / flashed a new modem, so to answer my own questions.
1. The backup method for the modem partition was correct.
2. I was able to restore the backup i created.
3. A 4.1.2 modem worked fine on 4.3. I believe tho there could be incompatiblity between ICS and JB for example.
Sadly i haven't been able to solve my modem crash issues, i will report if i find anything. Thanks to the previous user for the input above.

jaweinre said:
I went ahead and backed up / flashed a new modem, so to answer my own questions.
1. The backup method for the modem partition was correct.
2. I was able to restore the backup i created.
3. A 4.1.2 modem worked fine on 4.3. I believe tho there could be incompatiblity between ICS and JB for example.
Sadly i haven't been able to solve my modem crash issues, i will report if i find anything. Thanks to the previous user for the input above.
Click to expand...
Click to collapse
Hi
I mistakenly formatted m7y modem via CWM two days back. How can I restore it, seeing that your process was successful?
Thanks in advance.

How to merge Original ROM and factory modem/radio?

Hopefully, I'm using the right terms...and I'm wondering if the answer is "you can't..." but I find the stock ROM's modem/radio for my Verizon CDMA Moto X offers the best reception by far. However, I really enjoy some of the original ROMs such as CM11, Mokee and Dirty Unicorns.
So...how do I flash the modem/radio that works the best to the ROM I enjoy the most? Possible?
Thanks in advance!

hijax2001 said:
Hopefully, I'm using the right terms...and I'm wondering if the answer is "you can't..." but I find the stock ROM's modem/radio for my Verizon CDMA Moto X offers the best reception by far. However, I really enjoy some of the original ROMs such as CM11, Mokee and Dirty Unicorns.
So...how do I flash the modem/radio that works the best to the ROM I enjoy the most? Possible?
Thanks in advance!
Click to expand...
Click to collapse
Normally the radio is completely untouched when you flash a custom rom like CM11 (don't know about the others)....
Unless the rom includes "NON-HLOS.bin" and "fsg.mbn", you ARE using the stock baseband.
I would guess that you are experiencing the "placebo effect" as in just a difference in the number of bars showing up (but no actual difference in signal dbm levels), but could be mistaken.
Anyways, regardless, all you have to do is AFTER you have flashed the custom ROM, use fastboot to flash the modem files from the STOCK SBF:
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
(you may have to do OTA again after this).
Let us know how it works for you, and if you notice any change...

Perfect, thanks for the detailed reply!
Sent from my XT1060 using XDA Premium 4 mobile app

[Q] Need help! No sound in-call!?

Hi, I have a Samsung Galaxy S4 Active.
When I make a call i get no sound, microphone and earpiece are tested and working properly(I CAN'T HEAR THE PERSON, THE PERSON CAN'T HEAR ME).
Also, no sound when I put it on speaker.
I tried installing another stock rom but the problem persists..
First time it happened I removed battery and that solved the problem, now even removing the battery won't make it work.
Please help...

Nobody??

i537 or i9295?
Version of stock ROM?
Method of flash?
Tried factory reset?

I9295, 4.4.2 Kitkat, tried to flash through Odin.. tried factory reset and no result.
Also, I've wiped everything (data,system,boot,etc..) before flashing with Odin, using a custom recovery.

stefan2012 said:
I9295, 4.4.2 Kitkat, tried to flash through Odin.. tried factory reset and no result.
Also, I've wiped everything (data,system,boot,etc..) before flashing with Odin, using a custom recovery.
Click to expand...
Click to collapse
As you said you have checked the speaker phone and mic and confirm that it works so this eliminates any hardware issues.
Did you do the factory reset from within the phone in settings or through custom recovery. Suggest that you do the factory reset from within the phone in settings (prior backup of your internal sdcard data is required as this will get wiped out) as this solves most software / firmware issues. If still problem persists flash the entire firmware through odin (download from sammobile).

I have the same problem in the service menü i have no issue but when i make a call it doesnt work (sorry for my english)
Is it possible to make a logcat too see whats the Problem ?!

Snuk265 said:
I have the same problem in the service menü i have no issue but when i make a call it doesnt work (sorry for my english)
Is it possible to make a logcat too see whats the Problem ?!
Click to expand...
Click to collapse
Not sure if logcat will show the issue, but yes we can check it out.
Normally these issues arise due to either mismatch in firmware (flashing different modem) or issues in the ROM itself. You can check by flashing entire firmware and if issue still persists then do a factory reset from settings (not cwm) and reflashing the firmware.
Did you flash any firmware files / modem and are you on stock touchwiz or custom ROM

JASONRR said:
Not sure if logcat will show the issue, but yes we can check it out.
Normally these issues arise due to either mismatch in firmware (flashing different modem) or issues in the ROM itself. You can check by flashing entire firmware and if issue still persists then do a factory reset from settings (not cwm) and reflashing the firmware.
Did you flash any firmware files / modem and are you on stock touchwiz or custom ROM
Click to expand...
Click to collapse
OK i know
Factory reset from Rom and cwm or stock recovery dosnt help
Reflash stock rom change anything
I was on the latest tw-rom but at the moment i use official cm11
Thanks for your help

Snuk265 said:
OK i know
Factory reset from Rom and cwm or stock recovery dosnt help
Reflash stock rom change anything
I was on the latest tw-rom but at the moment i use official cm11
Thanks for your help
Click to expand...
Click to collapse
Mic in speaker is a known issue in cm11. This has been fixed in 17.10 version. You can flash the 17.10 version and check
Factory reset from stock recovery only wipes the system and data while factory reset from within phone in settings resets much more than that.
Reflashing only stock ROM will not help... You need to flash the entire firmware through odin .

JASONRR said:
Mic in speaker is a known issue in cm11. This has been fixed in 17.10 version. You can flash the 17.10 version and check
Factory reset from stock recovery only wipes the system and data while factory reset from within phone in settings resets much more than that.
Reflashing only stock ROM will not help... You need to flash the entire firmware through odin .
Click to expand...
Click to collapse
I know that is an present issue in cm11 but dont on stock rom .. And with reflash i mean to flash stock Rom with Odin
Thanks in advance

Snuk265 said:
I know that is an present issue in cm11 but dont on stock rom .. And with reflash i mean to flash stock Rom with Odin
Thanks in advance
Click to expand...
Click to collapse
Ok which firmware (stock ROM) did you flash and can you send me a screenshot of your about from stock Rom

How can I know what modem suits my phone? I've flashed another stock rom from another region(earpiece and mic didn't work before) and the issue is still present.

stefan2012 said:
How can I know what modem suits my phone? I've flashed another stock rom from another region(earpiece and mic didn't work before) and the issue is still present.
Click to expand...
Click to collapse
It is always recommended to flash the modem for your region. ROM's generally are independent of region unless you have flashed the entire firmware. UCNE5 firmware so far seems to be safe and is known to work for most regions.
Which country are you from and which ROM did you flash.

I'm having the same problem, using CM11 or Stock.
Phone worked grate till 2 month ago (bougth on february). Tested different modems, different SIMS.
¿Maybe a hardware problem? ¿Maybe is bootloader/KNOX related? I think this as was using last TW from UK (I9295XXUCNH2), I'm from Argentina.

tasken said:
I'm having the same problem, using CM11 or Stock.
Phone worked grate till 2 month ago (bougth on february). Tested different modems, different SIMS.
¿Maybe a hardware problem? ¿Maybe is bootloader/KNOX related? I think this as was using last TW from UK (I9295XXUCNH2), I'm from Argentina.
Click to expand...
Click to collapse
Flashing modem from a different region/carrier is sometimes known to cause this issue with certain carriers. Recommend that you flash only the modem for your region and carrier (not the entire firmware) and check it out else try flashing the entire firmware.
If mic and speaker is working fine in other apps then it will not be a hardware issue.

JASONRR said:
Flashing modem from a different region/carrier is sometimes known to cause this issue with certain carriers. Recommend that you flash only the modem for your region and carrier (not the entire firmware) and check it out else try flashing the entire firmware.
If mic and speaker is working fine in other apps then it will not be a hardware issue.
Click to expand...
Click to collapse
The S4A is not sold in my country, what modem should i use for Latin America?

tasken said:
The S4A is not sold in my country, what modem should i use for Latin America?
Click to expand...
Click to collapse
hmm..this is a tricky one.. You could try the NE5 modem from my drive to start with and see if it works, though I would recommend that you flash the one that you were on before while it was working properly.

Tested NE5 before posting, same results. Using official 20141018.
Original modem was 4.2.2, is there a modem repository?

tasken said:
Tested NE5 before posting, same results. Using official 20141018.
Original modem was 4.2.2, is there a modem repository?
Click to expand...
Click to collapse
I am not aware of one for i9295, from which region was the original modem and did it work in Argentina

tasken said:
The S4A is not sold in my country, what modem should i use for Latin America?
Click to expand...
Click to collapse
Just one more question? are you using GSM or LTE, you could start by trying GSM mode only. Also just remembered this thread I stumbled upon yesterday which may be useful in unlocking the band used in your country/carrier.
http://forum.xda-developers.com/oneplus-one/general/guide-unlock-aditional-bands-qualcomm-t2877031
Edit: another one which I searched and found today
http://forum.xda-developers.com/cro...ad-progress-please-leave-im-updating-t2871269
Did a little search and you may refer to the below links for the bands for Argentina as well as those on I9295 which could be helpful
http://www.gsmarena.com/network-bands.php3?sCountry=ARGENTINA
http://www.gsmarena.com/samsung_galaxy_s4_active_lte_a-5889.php

[Q] Correct IMEI, but won't connect to Network

Hey guys,
i recently bought an GT-I8190 off eBay. Problem is, it won't connect to any provider's network. It doesn't even find the correct network. It's not a SIM problem, SIM in different phone will find and connect to the right provider.
IMEI is correct though. I flashed cyanogenmod 11 (goldennova) and I8190XXANI4 Baseband. Still not able to connect. I already backed up EFS.
Any suggestions are greatly appreciated!

Hi,
Install by Odin latest stock rom, after restart turn off phone and go to recovery and do factory reset. After this check working connection.
Or here you find solution
http://forum.xda-developers.com/showthread.php?p=45527911
Sent from my GT-I8190 using XDA Free mobile app

eqal said:
Hi,
Install by Odin latest stock rom, after restart turn off phone and go to recovery and do factory reset. After this check working connection.
Or here you find solution
http://forum.xda-developers.com/showthread.php?p=45527911
Sent from my GT-I8190 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for your help. But i think you got me wrong, the problem existed even before i flashed cm. I don't think it has anything to do with cm.
I am on Linux, so i used Heimdall to flash latest Stock ROM. Did a factory reset, from within android and another one from recovery. Didn't help. At least the right provider is shown now, but i still can't connect. Now i am back to where i started, before i flashed cm.
Do you think it would help, if i flash modemFS?
I also checked if my IMEI is stolen here: http://www.amta.org.au/pages/amta/Check.the.Status.of.your.Handset
but I'm in germany, i don't know if their IMEI check is valid for me.
I also tried to repartition during flash, to wipe out all corrupted remainings, but heimdall fails to initialise protocol if i try to repartition. I downloaded my phone's .pit file and used that one.
Thanks in advance!

Still no success.
I tried different ROMs, Stock and Custom, even with repartitioning enabled.
I don't know what to do... must be a problem in one of the files/partitions that aren't touch by a full flash with repart, right?
Please help

Halp

Moootze said:
Halp
Click to expand...
Click to collapse
are you sure is it software or rom problem? maybe its Hardware problem and you should check it in a shop or something? maybe just something inside phone broken during carrier or something.

I'm in the same boat. Have a Swiss factory unlocked phone that I was given by a friend. I decided to flash it to CM11.
I tried initially to do it via the stock recovery but when that failed to due a lack of root I did it via Android Toolkit 1.3.4 which I found through the forum. It loaded the TWRP 2.6.3 recovery and then completed the flash of novafusion CM11 no which I had had already on SD card all by itself pretty much. Before first boot I went in and flashed google apps mini and the "original logo" file that novafusion had under extras.
Upon first boot, there was no cell signal and I've been trying ever since to fix it.
Tried flashing modemfs.zip
Tried flashing versions of stock roms via odin.
Tried the latest I8190N stock rom.
Tried repartitioning via .pit method in odin.
Tried various basebands.
Tried basebands + modemfs
Tried flashing the param/logo file
I'm basically out of ideas...

Real solution to emmc_read/write problems (How to revert back to older bootloader)

I had problems of phone rebooting automatically and showing emc-read error and cannot boot normally and had to remove battery to start my canadian note 4 W8
the way i fixed this **** is by reverting back to 5.0.1 bootloader
the newest bootloader is the cause of all problems for us
you cannot roll back to the old bootloader just by flashing an old bootloader
but luckily i have found a trick to revert back to a older bootloader to replace **** COK3 (Newest for canadian ) bootloader
So to actually roll back to old boot loader you need a full firmware which has capability to format internal storage when it is flashed
i had a 5.1.1 firmware tar but it did not have the capability of formatting internal storage when it is flashed
But i lucky found a older 5.0.1 tar in my harddisk that has the capability which enabled me to go back to old baseband and bootloader and formatted internal storage and now everything fine
Phone flying as before without any reboots emc read error or lags (i think the reason why this tar worked and back flashed the boot loader is because it formatted the internal storage while the tar was being executed)
just to be extra cautious,once you have old boot loader flash recovery and wipe system,cache,dalvik and internal storage
*IMP GO TO WIPE>FORMAT DATA AND TYPE YES
*MAKE SURE TO RE-FLASH JUST 5.1.1 BASEBAND FOR NOTE 5 PORTS AND CM12.1/13 TO HAVE NETWORK
Attaching the error i had and pic of my current setup
FOR PEOPLE WHO STILL CANNOT DOWNGRADE BOOT LOADER YOU CAN TRY PARTITIONING YOU INTERNAL MEMORY TO FIX READ WRITE ERRORS
LINK OF THE FIRMWARE I USED
http://forum.xda-developers.com/note-4/general/ref-stock-firmware-kernel-modem-recovery-t2920452
LINK TO PIT FILES FOR REPARTITIONING
http://forum.xda-developers.com/note-4/orig-development/note-4-pit-files-repartiton-f-g-c-t-w8-t3282641/post64569392#post64569392
Canadians having same issue can now flash this firmware to go back to 5.0.1 bootloader
*i think this would work for Tmobile users too but i am not sure about the risks of cross flashing

i checked my 5.0.1 and 5.1.1 tars and they both have same files so i cant tel which tar you should download for internal storage to be formatted
my most educated guess would be try and download early 5.0.1 builds as samsung must have implemented formatting internal storage when from kitkat to lollipop uograde
And odin 3.10.7

Help Me
Hi,
Can you please help me lookup stock firmware for SM-N910T(T Mobile Note 4) which I can use to rollback my bootloader.
Thank You

Please help me...
I'm using note 4 n910t and have the same problem of your phone before...very lag and auto turn off the phone,can't boot up or error "mmc read fail".
Can't use your firwame for n910t?!. I know that n910t and n910w8 can using same firwame
---------- Post added at 03:53 PM ---------- Previous post was at 03:47 PM ----------
Can you upload you 5.0.1 bootloader and the manual to fix this error?!
I think a lot of people have this issue when update to newest firwame from samsung, and they are watting for a way to fix their phone
Thanks a lots! ^^

I keep getting "auth" fails. I can only flash the 5.1.1 software
Please get back to us asap, it's driving me crazy with my phone consistently rebooting and freezing

McMichael96 said:
I keep getting "auth" fails. I can only flash the 5.1.1 software
Please get back to us asap, it's driving me crazy with my phone consistently rebooting and freezing
Click to expand...
Click to collapse
Flash custom rom first
Maybe a cm 12 build and try again

thiennvbk said:
Please help me...
I'm using note 4 n910t and have the same problem of your phone before...very lag and auto turn off the phone,can't boot up or error "mmc read fail".
Can't use your firwame for n910t?!. I know that n910t and n910w8 can using same firwame
---------- Post added at 03:53 PM ---------- Previous post was at 03:47 PM ----------
Can you upload you 5.0.1 bootloader and the manual to fix this error?!
I think a lot of people have this issue when update to newest firwame from samsung, and they are watting for a way to fix their phone
Thanks a lots! ^^
Click to expand...
Click to collapse
As i said before
just flashing the bootloader doesnt work
U need the full firmware with internal storage wiping capability to return to older bootloader
I will do one thing to help everyone out
Either i will track down the link to download the 5.0.1 firmware i used
Or
I will upload the full 1.7 gb tar firmware
Till then find a older 5.0.1 firmware for your model and try it

Ashwin Prabhunerurkar said:
Flash custom rom first
Maybe a cm 12 build and try again
Click to expand...
Click to collapse
I tried that. Still didn't work. And I have a pretty old copy of 5.0.1. I think it has to do with how T-Mobile/Samsung pushed security policy's to this device. I read up where the last ones actually prevent downgrades.

McMichael96 said:
I tried that. Still didn't work. And I have a pretty old copy of 5.0.1. I think it has to do with how T-Mobile/Samsung pushed security policy's to this device. I read up where the last ones actually prevent downgrades.
Click to expand...
Click to collapse
I checked on samfirmware
And the BOE2 firmware 5.0.1 i have is the last version of 5.0.1 just before 5.1.1 started rolling out
So download the last version of 5.0.1 just before 5.1.1 released

Ashwin Prabhunerurkar said:
I checked on samfirmware
And the BOE2 firmware 5.0.1 i have is the last version of 5.0.1 just before 5.1.1 started rolling out
So download the last version of 5.0.1 just before 5.1.1 released
Click to expand...
Click to collapse
Will the Canadian firmware even work in odin for the t-mobile variant?

McMichael96 said:
Will the Canadian firmware even work in odin for the t-mobile variant?
Click to expand...
Click to collapse
Tmobile roms work out of the box for canadian note 4
But bootloader is on a whole another level
U can easily flash another baseband if phones gets busted but i dont know about bootloader
If you are in warrenty you should give it a try

McMichael96 said:
Will the Canadian firmware even work in odin for the t-mobile variant?
Click to expand...
Click to collapse
It might but u shld download the BEO2 equivalent for tmobile

I don't know if I have this problem or not. A few days ago I installed "[N910TUVU2DOK2] Debloated-Deodexed Stock ROM[Dec-18-2015]" along with TWRP recovery. It has seemed to be OK, but I did have a couple of unexpected random reboots. Today while using the phone, it just froze. It did not reboot. After battery pull, I tried to get into recovery, but nothing but short vibrations every 10 seconds or so.
I have not seen any messages about emmc_. The screen remained black entirely. I was unable to get into download mode or recovery mode. When I plugged in with USB, I was able to get it to recognized on USB and in Odin, but had not idea what mode it was in since the screen was black.
After letting it sit a while, I tried again, and was able to boot into recovery. From there, I was able to reboot into Andriod, and everything seems to be normal again.
Is this the same issue? Should I revert the bootloader? If so, what is the correct bootloader for the TMO Note4 N910TUVU2DOK2 ? I have stock ROM for 5.0.1 (N910TUVU1COD6_N910TTMB1COD6_N910TUVU1COD6_HOME.tar.md5) which contains the file boot.img. But in the first post it says it is not possible to simply flash boot.img with Odin?
The required procedure is this?
1) Flash the 5.01 stock firmware N910TUVU1COD6_N910TTMB1COD6_N910TUVU1COD6_HOME.tar.md5 (including the desired bootloader)
2) Boot into stock firmware
3) Select Factory Reset (to execute the data wipe capability in 5.0.1)
4) Shut down and boot into download mode.
5) Flash TWRP
6) Flash 5.1.1 N910TUVU2DOK2 (previously modified to remove boot.img from the tar.md5 file?)
( would this step 6 cause the full functionality of 5.1.1 to be available, but with the non-broken bootloader?)

Ashwin Prabhunerurkar said:
As i said before
just flashing the bootloader doesnt work
U need the full firmware with internal storage wiping capability to return to older bootloader
I will do one thing to help everyone out
Either i will track down the link to download the 5.0.1 firmware i used
Or
I will upload the full 1.7 gb tar firmware
Till then find a older 5.0.1 firmware for your model and try it
Click to expand...
Click to collapse
That mean I can download last 5.0.1 firwame and use odin to flash??.
I have try one and odin fail because binary. It isn't allow to come back 5.0.1 firwame.
Can you share the link of 5.0.1 firwame that you had been flash over odin?!
Thanks

thiennvbk said:
That mean I can download last 5.0.1 firwame and use odin to flash??.
I have try one and odin fail because binary. It isn't allow to come back 5.0.1 firwame.
Can you share the link of 5.0.1 firwame that you had been flash over odin?!
Thanks
Click to expand...
Click to collapse
Hmm, it's not quite that simple. Just installing 5.0.1 would leave you downgraded to 5.0.1.
There are reasons to move to 5.1.1 (if it works right), so we're trying to determine how to get the BL from 5.0.1 and everything else from 5.1.1.

timg11 said:
Hmm, it's not quite that simple. Just installing 5.0.1 would leave you downgraded to 5.0.1.
There are reasons to move to 5.1.1 (if it works right), so we're trying to determine how to get the BL from 5.0.1 and everything else from 5.1.1.
Click to expand...
Click to collapse
you can flash the 5.0.1 firmware now and then flash a 5.1.1 custom rom
so the bootloader version doesnt matter as long as its lollipop
but for baseband you need 5.1.1 baseband for 5.1.1 roms to have network

thiennvbk said:
That mean I can download last 5.0.1 firwame and use odin to flash??.
I have try one and odin fail because binary. It isn't allow to come back 5.0.1 firwame.
Can you share the link of 5.0.1 firwame that you had been flash over odin?!
Thanks
Click to expand...
Click to collapse
i have a canadian W8 variaant and i am not sure about the risks of cross flashing
Luckly i found the link of the firmware i used
here it is
http://forum.xda-developers.com/note-4/general/ref-stock-firmware-kernel-modem-recovery-t2920452
Download the link in first post

Ashwin Prabhunerurkar said:
you can flash the 5.0.1 firmware now and then flash a 5.1.1 custom rom
so the bootloader version doesnt matter as long as its lollipop
but for baseband you need 5.1.1 baseband for 5.1.1 roms to have network
Click to expand...
Click to collapse
OK, when I flash the 5.1.1 custom ROM, wouldn't that put the bad boodloader back int?
If I want to end up on 5.1.1 N910TUVU2DOK2, Is this procedure correct?
1) Flash the 5.01 stock firmware N910TUVU1COD6_N910TTMB1COD6_N910TUVU1COD6_HOME.tar .md5 (including the desired bootloader)
2) Boot into stock firmware
3) Select Factory Reset (to execute the data wipe capability in 5.0.1)
4) Shut down and boot into download mode.
5) Flash TWRP
6) Flash 5.1.1 N910TUVU2DOK2 (previously modified to remove boot.img from the tar.md5 file?)
( would this step 6 cause the full functionality of 5.1.1 to be available, but with the non-broken bootloader?)
Questions:
1) Why is the bootloader causing problems with random reboots? During the boot process it corrupts memory?
2) is the problem in internal memory or EXT-SD or both?
3) does the 5.1.1 bootloader continue to corrupt the memory? I.E. if the memory corruption was repaired by other means, would it soon be corrupted again by the bootloader?
4) The T-Mobile 5.1.1 stock ROM has been out since August. This seems like a huge bug. Nobody has seen this issue until now? Or is it specific to rooted devices or the Beastmode kernel?

timg11 said:
OK, when I flash the 5.1.1 custom ROM, wouldn't that put the bad boodloader back int?
If I want to end up on 5.1.1 N910TUVU2DOK2, Is this procedure correct?
1) Flash the 5.01 stock firmware N910TUVU1COD6_N910TTMB1COD6_N910TUVU1COD6_HOME.tar .md5 (including the desired bootloader)
2) Boot into stock firmware
3) Select Factory Reset (to execute the data wipe capability in 5.0.1)
4) Shut down and boot into download mode.
5) Flash TWRP
6) Flash 5.1.1 N910TUVU2DOK2 (previously modified to remove boot.img from the tar.md5 file?)
( would this step 6 cause the full functionality of 5.1.1 to be available, but with the non-broken bootloader?)
Questions:
1) Why is the bootloader causing problems with random reboots? During the boot process it corrupts memory?
2) is the problem in internal memory or EXT-SD or both?
3) does the 5.1.1 bootloader continue to corrupt the memory? I.E. if the memory corruption was repaired by other means, would it soon be corrupted again by the bootloader?
4) The T-Mobile 5.1.1 stock ROM has been out since August. This seems like a huge bug. Nobody has seen this issue until now? Or is it specific to rooted devices or the Beastmode kernel?
Click to expand...
Click to collapse
boot loader is the problem
i was using an older version of 5.1.1 bootloader for months and everything was fine but as soon as i upgraded to latest, i started having problems
internal and ext are both fine but just to be safe and start fresh i recommend formatting internal storage
boot loader was not executing internal memory properly hence all the errors,older bootloaders are perfect and you wont face any problems
i haven't faced a single problem in 2 days
there are many versions of 5.1.1 stock roms with different names but i think the latest once is the culprit, so stay away from 5.1.1 recent builds and only flash 5.1.1 base band but try to keep 5.0.1 boot loader.
your procedure seems about right but my tar automatically executed internal memory format and not just factory reset
those are two different things
factory reset formats /data
internal memory formats /system /data /cache etc
so if you tar doesnt support inernal mem format
my suggestion would be to install twrp after 5.0.1 flash and go to wipe>advanced and wipe internal storage
dont flash 5.1.1 again unless you are sure its bootloader is working properly
you just need 5.1.1 baseband to have a well functioning phone

I believe you when you say it works for your variant, but man I don't think it's going to work for our t-mobile variant. Even though they're really similar, I don't believe the Canadian variant got the security policy update that prevents downgrading like we did.