hello everyone,
I recently purchased my galaxy tab in dubai and could not update through kies as i got the following message "This version of device cannot be updated".
Then i flashed xxjq1 along with bootloaders from this thread http://forum.xda-developers.com/showthread.php?t=1073854 and the gt-p1000_mr_PIT.zip files. now everything works fine but the csc and pda fields are empty.
How can i get the pda and csc fields back. I want to flash the dxjpe firmware as this is the 2.3.3 asian version i found. Will this bring my csc and pda fields back to normal. Will this enable me to update future updates via kies.
Aren't you supposed to boot immediately into recovery after you flash the rom? That installs the csc files. Double check the instructions.
so can i go ahead and flash the dxjpe firmware , will this reinstate my csc files, and what pit file i need to use with this.
hopefully it would fix your problem. as for pit for the dxjpe use (GT-P1000_M.PIT)
I got the error when downgrading and flashing signed bootloaders... Rolling back from GB to froyo gave me that error... I suggest unsigning the bootloader then flashing again...
afaque_h said:
hello everyone,
I recently purchased my galaxy tab in dubai and could not update through kies as i got the following message "This version of device cannot be updated".
Then i flashed xxjq1 along with bootloaders from this thread http://forum.xda-developers.com/showthread.php?t=1073854 and the gt-p1000_mr_PIT.zip files. now everything works fine but the csc and pda fields are empty.
How can i get the pda and csc fields back. I want to flash the dxjpe firmware as this is the 2.3.3 asian version i found. Will this bring my csc and pda fields back to normal. Will this enable me to update future updates via kies.
Click to expand...
Click to collapse
Your post no. 1 is confusing. You said you flashed to JQ1 yet the attachment says JM3. Anyway use this (by noxxious) procedure to get into a ROM without rooting then update thru kies.
The attachment showed the message displayed by kies when i wanted to update my gtab after purchasing. Since i could not officially update using kies i opted for manual flashing
Sent from my GT-I9000 using Tapatalk
afaque_h said:
The attachment showed the message displayed by kies when i wanted to update my gtab after purchasing. Since i could not officially update using kies i opted for manual flashing
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
Just follow the link above to downgrade to JK2 which is a version with unsigned bootloader. Then update thru kies. Kies should be able to detect your firmware as upgradable to JPE.
Good luck!
This happened with me after a soft brick. Reboot into recovery and see if CSC is installed, if not do a factory reset. For me flashing a stock firmware fixed it for me.
DarkPal said:
This happened with me after a soft brick. Reboot into recovery and see if CSC is installed, if not do a factory reset. For me flashing a stock firmware fixed it for me.
Click to expand...
Click to collapse
Right, I reminded him a while ago after flashing to immediately go into recovery to get the csc files installed. The JQ1thread has clear instructions.
Don't worry about that other rom yet - by correctly flashing JQ1 you will have the complete system and safe bootloaders. Once that's done, you can go in any direction.
I was wondering if anyone had flashed back to that factory dump someone had put up I saw it floating around here somewhere...
I have flashed stock multiple times, but I didn't use Odin since the same stock firmware is available through Kies and it flashes it pretty much the same way and flawlessly.
I used Odin for other files but since the bootloaders are locked and encrypted I received an error message in red font in the download mode screen, and then Odin was disconnected. Knox counter did not advance in my case, but I did consider the possibility before flashing.
Kies, on the other hand, asks for the phone model and the serial number and then it lets you flash it. I'm assuming it might be generating md5 encryptions based on the phone model and serial number and then phone checks to match those before flashing. (Not sure!)
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
i recently flashed the firmware back on my sg900a and it wouldnt take ...although odin said it was passing on the fifth try I used my three point cable and it passed but I do not have internet data connection except on wi-fi. Any advice or ideas would be greatly appreciated.
chrislatham08 said:
i recently flashed the firmware back on my sg900a and it wouldnt take ...although odin said it was passing on the fifth try I used my three point cable and it passed but I do not have internet data connection except on wi-fi. Any advice or ideas would be greatly appreciated.
Click to expand...
Click to collapse
More info would help. What firmware version did you flash? What version of Odin did you use? Have you checked your APN? What firmware was running on your phone before you flashed back?
dirtydodge said:
More info would help. What firmware version did you flash? What version of Odin did you use? Have you checked your APN? What firmware was running on your phone before you flashed back?
Click to expand...
Click to collapse
I started with the G900AUCU1ANCE and flashed theG900AUCU2AND3 Doungraded the kernal installed towel root then upgraded the kernal and achieved root. now my device has android version 4.42 baseband version G900AUCU2ANG3 My build number is KOT49H G900AUCU1ANCE Is this mismatch the problem?
chrislatham08 said:
I started with the G900AUCU1ANCE and flashed theG900AUCU2AND3 Doungraded the kernal installed towel root then upgraded the kernal and achieved root. now my device has android version 4.42 baseband version G900AUCU2ANG3 My build number is KOT49H G900AUCU1ANCE Is this mismatch the problem?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3077652
Download this NCE file to your desktop, extract it. Flash the tar.md5 file in the AP slot using Odin 3.09. That should fix your problems. However it will reset your phone to stock so save everything that you may want to your desktop from your phone.
thanks dirtydodge
i did as you said it worked YOUR GREAT
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.
I have a rooted t mobile galaxy s6. I wanted to go back to stock so I went to the general sticky and downloaded the latest firmware for my model and followed the guide with odin but it keeps failing. I have the right drivers installed. Any suggestions?
If you can't get it to work through Odin you can restore to out of box (save for tripped Knox) by restoring through Samsung Kies. I have done it several times with a Tmo S6. You will need model number and Serial Number.
Pls show us captured of Odin fail screen...
I had the same problem with ODIN last night.. I think it was because I was trying to flash and old Baseband, while my phone is on the lastest G925TUVS3DOJC. Could this have caused the problem?