root methods? - Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting

Anybody know of any root methods yet? Loving this tab, but I would like wanam and full mwc. Then its game on for me! Willing to donate to anybody that has a working method.
Mods: sorry, I believe this should be under q&a, please move if correct, thank you

I'm willing to donate too so bring it on!

Have you guys tried Kango Root?

Chainfire released root for Note 12.2:
http://forum.xda-developers.com/showpost.php?p=50498424&postcount=235
Verstuurd vanaf mijn GT-I9505G met Tapatalk

maarten1055 said:
Chainfire released root for Note 12.2:
http://forum.xda-developers.com/showpost.php?p=50498424&postcount=235
Verstuurd vanaf mijn GT-I9505G met Tapatalk
Click to expand...
Click to collapse
Thanks!

If anyone tries it, please report back the results and steps to do it. I don't really want to destroy my 750.00 tablet unless we know for sure

So far it has worked for a couple people and not worked for others. It didn't work for me. However, my tablet is not destroyed I just flashed the original recovery linked in Chainfire's thread and all is well. Except for not being rooted :/ sob.
---------- Post added at 12:20 PM ---------- Previous post was at 12:19 PM ----------
And this thread has instructions:
http://forum.xda-developers.com/showthread.php?t=2656551

KestrelX said:
So far it has worked for a couple people and not worked for others. It didn't work for me. However, my tablet is not destroyed I just flashed the original recovery linked in Chainfire's thread and all is well. Except for not being rooted :/ sob.
---------- Post added at 12:20 PM ---------- Previous post was at 12:19 PM ----------
And this thread has instructions:
http://forum.xda-developers.com/showthread.php?t=2656551
Click to expand...
Click to collapse
I had the same problem with getting stuck at cache.img. After a few failed attempts I switched usb ports and used Odin 3 v3.07 and it worked great. Hope this helps someone else.

With that version of Odin, did you leave F. Reset Time checked on? It's off with the version of Odin posted in ChainFire's thread.
---------- Post added at 11:15 PM ---------- Previous post was at 11:07 PM ----------
I unchecked F. Reset Time and ran it, and it worked!!! Thank you so much BYE BYE BLOATWARE.

Can anyone try:
http://forum.xda-developers.com/showpost.php?p=50547230&postcount=20

emwno said:
Can anyone try:
http://forum.xda-developers.com/showpost.php?p=50547230&postcount=20
Click to expand...
Click to collapse
Odin3-v1.85
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Odin3 v3.09
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
Won't go any further

Dang, I've tried every combination I can think of with no luck. I've used Odin 3.09 and 3.07, both with F. Reset Time flag on and off with no luck. I've even switched USB ports and rebooted my pc, still nothing. :crying:

KCRickSS said:
Dang, I've tried every combination I can think of with no luck. I've used Odin 3.09 and 3.07, both with F. Reset Time flag on and off with no luck. I've even switched USB ports and rebooted my pc, still nothing. :crying:
Click to expand...
Click to collapse
I had the same problem and then I extracted with 7 zip instead of winzip and bam! It worked.
Sent from my SM-P900 using Tapatalk

No problems using Chainfires CF. I have donated appropriately as well. Very glad to have it! Enjoying it since....

Are you guys on SM-P900 (Wifi)? I've tried alternative unzippers with no impact. The MD5 always checks out in ODIN anyway, so I don't think that is the problem. Seems like the fact that it hangs when pushing cache.img (or right after) would point to something but I have no idea what it might be. I've now tried another computer also with the same result. I'm really wondering why there is an inconsistency with it - usually not the case.
---------- Post added at 05:08 PM ---------- Previous post was at 04:19 PM ----------
Ok, well that was screwy. I decided to try to download the SMP905 file and give it a try, even though I'm on SMP900. Not surprisingly, it failed. This time it hung when pushing recovery.img. I quickly stopped it and went straight back to ODIN and went ahead to try the same SMP900 file I've been trying all along. BINGO - it worked that time!
Officially, I'm just sharing this and am not recommending this approach for anyone (not responsible for bricks, etc. etc.). But I'm happy it finally worked, one way or the other.

Worked for me..just need twrp support now..no luck with goo manager
Sent from my SM-P900 using Tapatalk

markklok said:
Odin3-v1.85
Won't go any further
Click to expand...
Click to collapse
Try this one, the previous might have been corrupt or something. Flash with odin and let me know if you can boot into cwm.

KestrelX said:
With that version of Odin, did you leave F. Reset Time checked on? It's off with the version of Odin posted in ChainFire's thread.
---------- Post added at 11:15 PM ---------- Previous post was at 11:07 PM ----------
I unchecked F. Reset Time and ran it, and it worked!!! Thank you so much BYE BYE BLOATWARE.
Click to expand...
Click to collapse
Turning off F. Reset Time using Odin 3.09 worked for me too.

emwno said:
Try this one, the previous might have been corrupt or something. Flash with odin and let me know if you can boot into cwm.
Click to expand...
Click to collapse
Will try it when i get home from work.

Same result:
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
won't go any further then that

Related

[REPACKED] CWM + ROOT + BUSYBOX|Odin flashable EI22 system with ec05 modem

Rooted, contains busybox installed to /system/xbin and CWM 3.1.0.1 Everything else is untouched.
You must install Superuser.apk from the market or the root won't work. The superuser.apk is not included because I am keeping the stuff untouched and minimal as possible.
Also, install ei22 modem in recovery : http://db.tt/12aolm4A
Download: http://www.mediafire.com/?opnq0n0pau8cu01
mirrors:
http://www.hammerbrain.com/SPH-700/SPH-D700-EI22-EC05-MODEM-8gb-REL-ROOTED.TAR.zip
Repacked: Odin didn't like mac's resource fork, **** you apple. did it from Linux VM using vmware fusion
Gave it a shot since I needed to update the wife's phone. However, it failed
Here's what Odin had to say about it:
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> ./._cache.rfs
<ID:0/012> NAND Write Start!!
<ID:0/012>
<ID:0/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
D`Nyed said:
Gave it a shot since I needed to update the wife's phone. However, it failed
Here's what Odin had to say about it:
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> ./._cache.rfs
<ID:0/012> NAND Write Start!!
<ID:0/012>
<ID:0/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
fixed in the repack
Just used this to get my phone set up before going to work - the repack works great, thanks for the easy-deployment package noobnl.
noobnl said:
Repacked: Odin didn't like mac's resource fork, **** you apple. did it from Linux VM using vmware fusion
Click to expand...
Click to collapse
I love the bold sentence !!!!!
downloading repack, will try it tonight
great job
Thanks noobnl!!!
Mirror
this is odex right?
faceless said:
this is odex right?
Click to expand...
Click to collapse
Yes. 10 char
I was waiting for this all day yesterday
Sent from my SPH-D700 using xda premium
manual thank you
Can I ask a question? It seems no one has been able to put together:
[ODIN][+CWM][+EI22 w/Modem][+Root]
Could you tell us non-dev types what the complication is in that specific endeavor?
Thank You!
Worked like a charm!
edufur said:
Can I ask a question? It seems no one has been able to put together:
[ODIN][+CWM][+EI22 w/Modem][+Root]
Could you tell us non-dev types what the complication is in that specific endeavor?
Click to expand...
Click to collapse
I may be mistaken (changes are happening fast right now), but I believe we have not been able to get our hands on the full EI22 modem, just the delta based off of EC05. So we don't have anything that can be Odined (requires the full bin because it doesn't matter what is already there, just overwrites it completely)
Sent from my SPH-D700 using XDA App
Awesome work as always! Could you do a deodexed one so we could apply nociq patch? That would be awesome.
Only thing I would need to apply is the keyboard fix then.
styles420 said:
I may be mistaken (changes are happening fast right now), but I believe we have not been able to get our hands on the full EI22 modem, just the delta based off of EC05. So we don't have anything that can be Odined (requires the full bin because it doesn't matter what is already there, just overwrites it completely)
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
you nailed it
noobnl
Thanks for this. Do you know if the epic odex/deodex tool would work with this?
http://forum.xda-developers.com/showthread.php?t=927742
hammerbrain said:
Yes. 10 char
Click to expand...
Click to collapse
cool, thanks for the answer.
rsage said:
noobnl
Thanks for this. Do you know if the epic odex/deodex tool would work with this?
http://forum.xda-developers.com/showthread.php?t=927742
Click to expand...
Click to collapse
+1 on this. I want to apply the noCIQ fix as well as change the mail, text, aqnd media icons, then re-odex.
Flashed this in Odin from a fresh EC05 install. Set up all my apps and stuff, the font switcher I use said busybox wasnt installed. I installed it again (even though the busybox installer from the market warned me it was already installed), rebooted my phone, stuck on samsung screen and had to re-flash the rom
stuck at factoryfs.rfs tried different cables, different USB ports, no help

[Help] I soft bricked my phone, i am desperate.

I am so lost as to what to do next, i really need guidance.
I am offering a bitcoin tip or a paypal tip to whomever helps me get my phone to work ASAP.
So i was attempting to root my phone [GALAXY S6 - SM-G920F]
Got the file from: https://autoroot.chainfire.eu/ which should've matched my Phone.
First attempt failed, got back into my phone everything is fine. Tried the same thing again, failed this time i get this message:
An error has occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software." The logs for the times it has failed:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-zeroflte-zerofltexx-smg920f.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
Tried connecting with Kies and Smart switch, none can find the device just keeps buffering and for smart switch it just say it's not supported. I am able to get into downloading mode, but that's it.
Got newest Kies, odin 3 v.10.7.exe however on my first go i noticed i had odin3 v.10.6 but now i got the latest i believe. After reading around i decided to try to fix it back to normal, so i downloaded my countries [sweden] firmware this one: http://www.sammobile.com/firmwares/confirm/57869/G920FXXU3COI9_G920FVDS3COI6_VDS/
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004>
<ID:0/004> Get PIT for mapping..
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
And now i am here, i am truely nervous that i wont be able to get it to work.
Please Xda your my only hope. All i wanted was to free up space on my phone.. That's it.. :crying:
Ps. Worth mentioning, sometimes my usb is not recongnized and it flickers on and off (connectiong) but seems
to be fine most of the times and during the odin trials.
To root your phone, couldn't you simply flash twrp and then unikernel, like the guides say?
However, I'd try doing the following:
First of all, download the stock firmware for your version from samfirmware, then flash it via Odin (make sure the versione you download is the same you had before, or at least a more recent one).
From your logs, the problem seems to be pit file, so try reading here http://forum.xda-developers.com/showthread.php?t=1916936
If not, completely delete odin and download it again, maybe trying with a different firmware.
If everything goes well, let it boot into setup wizard, then you will able to root it again, this time following the standard procedure with odin:
- Make sure "Auto reboot" flag is NOT checked;
- Flash the twrp odin-flashable file (can't post links here, but you'll find them in General section);
- Manually reboot into recovery (Hold power+home+volume up).
- Once you're into twrp, flash unikernel and reboot.
Your phone will be rooted
Nicolò98 said:
To root your phone, couldn't you simply flash twrp and then unikernel, like the guides say?
However, I'd try doing the following:
First of all, download the stock firmware for your version from samfirmware, then flash it via Odin (make sure the versione you download is the same you had before, or at least a more recent one).
From your logs, the problem seems to be pit file, so try reading here http://forum.xda-developers.com/showthread.php?t=1916936
If not, completely delete odin and download it again, maybe trying with a different firmware.
If everything goes well, let it boot into setup wizard, then you will able to root it again, this time following the standard procedure with odin:
- Make sure "Auto reboot" flag is NOT checked;
- Flash the twrp odin-flashable file (can't post links here, but you'll find them in General section);
- Manually reboot into recovery (Hold power+home+volume up).
- Once you're into twrp, flash unikernel and reboot.
Your phone will be rooted
Click to expand...
Click to collapse
I just begain with youtubing easy way to root and i just said download odin, get the right firmware plug in an click odin.
That has failed and it's bricked, however i have tried to get my countries firmware, it didint work and produced my last log that i posted.
I am downloading another one there is two for Sweden however the other one says Sweden tre which is an operator over here and not one that i use so i doubt that will work?
i will attempt to download it but it takes 3h due to the limited speed at sammmobile.
So summarize, the sweden firmware from sammobile failed ;_;
What i do is, put phone in download mode, open odin, get the AP [Sweden from sammomobile] it finds it and press start, quickly after it says failed and i am back to square one.
I was reading the link you gave me about the pit files, it appears the error could be related to me having the wrong firmware?
I am seriously offering a bitcoin tip or a paypal tip to whomever helps me get my phone to work.
There are firmwares here for VDS.
Uninstall Kies and reboot your PC before using Odin.
blud7 said:
There are firmwares here for VDS.
Uninstall Kies and reboot your PC before using Odin.
Click to expand...
Click to collapse
Should i try all of those or just take the latest?
3H download, jesus my fiber is crying.
If you were on 5.1.1, then get 5.1.1
You can try the file you dl before. Just uninstall Kies before using Odin.
WaDoDem said:
Should i try all of those or just take the latest?
3H download, jesus my fiber is crying.
Click to expand...
Click to collapse
You dont need to download another rom dude...the problem is your usb dont get recognized and after a while it will disconnect...it happened to me aswell...searched on youtube did an easy fix and then i flashed stock rom with odin and joined marshmallow beta...
Tldr: search on youtube a fix for usb not recognized...i dont have a link sorry you have to search it by yourself its an easy fix..
Is it OK to flash with the latest stock roms? G920FXXU3? or should I flash only G920FXXU2? they are both 5.1.1 anyway.. If i flash with G920FXXU3, can i downgrade it to G920FXXU2? thanks for any help
anthonyrv03 said:
Is it OK to flash with the latest stock roms? G920FXXU3? or should I flash only G920FXXU2? they are both 5.1.1 anyway.. If i flash with G920FXXU3, can i downgrade it to G920FXXU2? thanks for any help
Click to expand...
Click to collapse
You're fine with either.
@WaDoDem
First of all, calm down. Believe me it's harder than you think to brick S6 in a not fixable way
If Odin doesn't flash official roms or you just cant suffer a slow a** download speed from SamMobile :
1. Press and hold all of 4 buttons on your device. (Volume up + Volume Down + Home + Power) your device will reboot.
2. As soon as device reboots release volume up and hold other 3 three. (Power + Home + Volume Down). Your device should boot into downloading mode.
3. Download this :
https://dl.twrp.me/zeroflte/twrp-2.8.7.2-zeroflte.img.tar.html
4. Connect your phone to your pc and flash above file with Odin. As soon as flashing process finishes, hold Power+Home + Volume Up. Now your device will boot into TWRP recovery.
5. Wait for drivers to be installed. Your pc should show phone's internal storage as connected device. If not, go to TWRP Mount section and enable MTP mode. (Or if it's enabled, disable and re enable it )
6. Download this rom :
http://forum.xda-developers.com/gal...rom-2013266107-arrow-rom-v1-0-0-fast-t3212318
And this kernel:
http://forum.xda-developers.com/gal...nified-development/kernel-vindicator-t3156281
Then put them on your phone.
7. Wipe system,data,cache and dalvik cache from twrp.
8. Install Arrow Rom first and then flash Vindicator Kernel.
9.Reboot, first boot can take up to 15 minutes
10.Continue celebrating new year [emoji14]
Sent from my SM-G920I using Tapatalk
sometimes if odin not working i restart my computer and put my mobile in downloadmode again and than i try again,most of the time it worked.....
If you think you can't find a wat at all, Samsung will help u. Download smartswitch to your PC and you can click in top corner emergency reinstall (or something like that) just put your serial number (as found on your backside of the phone)
4. Connect your phone to your pc and flash above file with Odin. As soon as flashing process finishes said:
Odin cant find the tar file.
I got odin 3V3.10.7 in options auto reboot and f. reset time are all bocked in is that right?
On files to download i am able to do, ap,cp,csc,bl neither of those help to find the recovery image that i am supposed to start?
Click to expand...
Click to collapse
Damientju said:
If you think you can't find a wat at all, Samsung will help u. Download smartswitch to your PC and you can click in top corner emergency reinstall (or something like that) just put your serial number (as found on your backside of the phone)
Click to expand...
Click to collapse
I cannot use recovery since none of the numbers i have on the back of my phone matches the one i need to enter.
i tried device initialization that led to FAILED TO UPDATE DUE TO AN ERROR.
and then smart switch recommends emergency software recovery the one you were talking about but i dont know how to get my code.
I assumed you meant to input my phones IMEI however that did not prove to be correct.
WaDoDem said:
I cannot use recovery since none of the numbers i have on the back of my phone matches the one i need to enter.
i tried device initialization that led to FAILED TO UPDATE DUE TO AN ERROR.
and then smart switch recommends emergency software recovery the one you were talking about but i dont know how to get my code.
I assumed you meant to input my phones IMEI however that did not prove to be correct.
Click to expand...
Click to collapse
Relax, flip your phone and on the bottom you'll see (barely visible) text. The last line it says: 'S/N:'
The code after is your serial number. So not your IMEI
The same code is found on the stickers you'd got with your phone
Damientju said:
Relax, flip your phone and on the bottom you'll see (barely visible) text. The last line it says: 'S/N:'
The code after is your serial number. So not your IMEI
The same code is found on the stickers you'd got with your phone
Click to expand...
Click to collapse
When i go to Smart switch Emergency Software recovery and input my S/N R58G52AMP1J
it says:
''Unable to find the recovery code. Check the recovery code in the PC's Emergency Software Recovery menu, or contact the samsung service center.''
When i did Device initialization used my model nr and S/N: R58G52AMP1J, halfway through completing the process, the first one did 100% then the next loading didint start got the error and that re-directed me to try Emergency Software Recovery.
WaDoDem said:
When i go to Smart switch Emergency Software recovery and input my S/N R58G52AMP1J
it says:
''Unable to find the recovery code. Check the recovery code in the PC's Emergency Software Recovery menu, or contact the samsung service center.''
When i did Device initialization used my model nr and S/N: R58G52AMP1J, halfway through completing the process, the first one did 100% then the next loading didint start got the error and that re-directed me to try Emergency Software Recovery.
Click to expand...
Click to collapse
HI
i know your problem , irecently f*cked my phone
I was bare worried however i was able to fix itnw
Download Both file and flash the pit first
and flash the Firmware
And make sure your using ODIN Odin v3.10.7
IF its fix let me know
[email protected] said:
HI
i know your problem , irecently f*cked my phone
I was bare worried however i was able to fix itnw
Download Both file and flash the pit first
and flash the Firmware
And make sure your using ODIN Odin v3.10.7
IF its fix let me know
Click to expand...
Click to collapse
This is the log from when i failed to start/flash the PIT. seconds later my usb was un recognised.
<ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1100)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006>
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
yes
Nicolò98 said:
To root your phone, couldn't you simply flash twrp and then unikernel, like the guides say?
However, I'd try doing the following:
First of all, download the stock firmware for your version from samfirmware, then flash it via Odin (make sure the versione you download is the same you had before, or at least a more recent one).
From your logs, the problem seems to be pit file, so try reading here http://forum.xda-developers.com/showthread.php?t=1916936
If not, completely delete odin and download it again, maybe trying with a different firmware.
If everything goes well, let it boot into setup wizard, then you will able to root it again, this time following the standard procedure with odin:
- Make sure "Auto reboot" flag is NOT checked;
- Flash the twrp odin-flashable file (can't post links here, but you'll find them in General section);
- Manually reboot into recovery (Hold power+home+volume up).
- Once you're into twrp, flash unikernel and reboot.
Your phone will be rooted
Click to expand...
Click to collapse
If Odin says no PIT, he'll need to Odin the PIT file for his device first then Odin the factory firmware.
PS...I'm just browsing threads and stopped here, hopefully to help. I'll keep reading. lol
---------- Post added at 04:43 PM ---------- Previous post was at 04:41 PM ----------
WaDoDem said:
This is the log from when i failed to start/flash the PIT. seconds later my usb was un recognised.
<ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1100)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006>
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Click to expand...
Click to collapse
Did you get the appropriate PIT file for your devices Internal storage? It does matter whether its the 32 64 or 128GB version.
sd_N said:
If Odin says no PIT, he'll need to Odin the PIT file for his device first then Odin the factory firmware.
PS...I'm just browsing threads and stopped here, hopefully to help. I'll keep reading. lol
---------- Post added at 04:43 PM ---------- Previous post was at 04:41 PM ----------
Did you get the appropriate PIT file for your devices Internal storage? It does matter whether its the 32 64 or 128GB version.
Click to expand...
Click to collapse
I just downloaded and tried the pit that above user posted.
https://drive.google.com/folderview...sharing&tid=0B40ItdHKfkyQd1hJQXVDU3dDU2c#list
It's a Galaxy s6 32GB.

Help! Poor GSM signal and 4G/LTE after latest OTA update

Hi, I used this s6 (G920F) for more than a year without any issues. Few weeks ago I got an OTA update and since then the phone rarely goes to 4G mode (it almost always used to be in 4G), often stays 'out of coverage' and drains much more juice from the battery. I confirmed the phone is faulty by swapping the SIM over to another phone. This is the currrent config: AP: G920FXXS4DPG6, CP: G920FXXS4DPG3, CSC: G920FOJV3DPF3. Country code XSG, Status: Official, Knox: 0x0.
I already tried these:
Factory reset, Factory reset and wipe in recovery mode. Nil fix.
Emergency recovery/Re-initialise using SmartSwitch. It re-installed the same firmware with the same issues. Nil fix.
Numerous attempts to flash the previous firmware (G920FXXU3DPER_G920FOJV3DPF3_G920FXXU3DPF2_HOME.tar.md5) using Odin3.11.1 with this result:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1101)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Flashed the current firmware using Odin (Passed), wiped in recovery, boot up, the same issues..
Has anyone experienced similar issue? Got any fix? I am out of warranty and have no problem rooting etc. if I must.
My primary intention was to restore the previous stock firmware, but it seems the bootloader will not allow this. Is there any workaround to bypass this block?
Could someone please help? Thanks!
faurionutz said:
If your build is from july you can't downgrade, it can be a software problem only if your phone has been unlocked before update
Click to expand...
Click to collapse
Sorry, didnt get that fully. It's international version, 100% stock no mods, no SIM or carrier lock.
You can't flash the previous firmware. You can try flashing the latest firmware through odin and check if it makes a difference.
http://updato.com/firmware-archive-select-model?record=FB17A3034FAD11E6B055FA163EE8F90B.
Download this firmware and flash it.
faurionutz said:
Samsung has blocked downgrade since july 2016, so if you want to flash same version but older by release you will not succed, there is no way to flash older version at the moment
Trimis de pe al meu SM-G920F folosind Tapatalk
---------- Post added at 02:16 PM ---------- Previous post was at 01:42 PM ----------
Imei and serial number are ok?
Trimis de pe al meu SM-G920F folosind Tapatalk
Click to expand...
Click to collapse
Yes, IMEI and S/N are intact.
azz06 said:
You can't flash the previous firmware. You can try flashing the latest firmware through odin and check if it makes a difference.
http://updato.com/firmware-archive-select-model?record=FB17A3034FAD11E6B055FA163EE8F90B.
Download this firmware and flash it.
Click to expand...
Click to collapse
Tried it a few days ago, no luck. It flashed good, but booted up to the same problems.
What if I root and use a custom recovery? Will I be able to flash the previous firmware?
Leju said:
Tried it a few days ago, no luck. It flashed good, but booted up to the same problems.
What if I root and use a custom recovery? Will I be able to flash the previous firmware?
Click to expand...
Click to collapse
Nope. I'm afraid you're stuck with the latest version. You could try a custom kernal like Space-X and see if it solves your problem
Thanks, will try and post back
Can I flash another stock firmware newer than current, from another region/CSC..? If so, could you suggest one? I see many other regions already got August updates. Hope the updated FW would fix my problem. I am impatient coz I have holidays planned for next week. Worried about travel with broken phone!
I sent a mail to Samsung about the issue, they want me to give it to the service center, I dont think I should.
Regards

SM-G920 LIVE DEMO UNIT won't boot.

It stays on the booting screen flashing. "Samsung galaxy s6 live demo unit". I can't get it to boot hence can't set the usb debugging on to flash another firmware. What is there to do ?
EDIT: Managed to enter recovery mode and clear cache + do a factory reset. That not only did not solve anything but now i can't get into recovery or download mode at all. That "Samsung galaxy s6" thing flashes only when the phone is charging !
Alright, it has to be charging in order to get into recovery/download mode. Now, what shall i do ? What ROM should i flash since this is a SM-G920X ? Please help me, i couldn't find any useful information on google. Even if there was a suitable firmware to flash, the device is not recognized in odin. What shall i do ?
I had some problems with my account and i had to post from that other one. I downloaded samsung drivers and the phone is now recognized in odin but i cant flash the sm-g920 firmware, it fails just on start. Please help me out of this.
EDIT : FOUND THIS http://forum.xda-developers.com/galaxy-s6/general/g920x-master-thread-guides-firmwares-t3267738 . I think it will be a great help.
Alright, i tried flashing that verified ready-to-flash ROM that was provided there and it failed at around 40%. Now i cant flash it again, it stay locked at
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
I dont know what to do next.
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Second time it fails.. I dont know why.
---------- Post added at 09:05 PM ---------- Previous post was at 08:42 PM ----------
I flashed that ready-to-go ROM successfully and now it boots further to that "welcome" screen but i encounter a big yellow triangle with an black exclamation mark in middle and a 'dead' android bot behind it. What should i do next ?
IMPORTANT NOTE : The phone won't show any kind of life unless it's CHARGING.
Can anyone really help me a little, what's up with this device ? Should i hope or try any further cause i really dont know what to do
Everything you guys need to know to get off the mess you created is here in this thread.
http://forum.xda-developers.com/galaxy-s6/general/g920x-master-thread-guides-firmwares-t3267738
Read and make sure you know what you're dealing with first, then start flashing ROMs!
I noticed the link was already found and posted by the OP in a later edit. Thanks.
One more thing i wanted to add is you can only flash a ROM that matches with your bootloaders. Since the LDU bootloader is Android 5.1.1 at the latest, you cannot flash Android 6. I suggest, if you manage to update bootloaders from 5.0.1 to 5.1.1, getting the latest 5.1.1 from sammobile, removing the *.bin files, and flash in ODIN.
Sent from my SM-G920F using XDA-Developers mobile app
Thanks god someone is willing to help me out of this ! I read the entire thread multiple times and i really really want to get out of this mess.
I took that ready-to-go ROM he provided there cause of the fact alone i have no clue what a unix machine is hence i can't remove these .bin files listed there. Also, i have no clue what bootloader this phone has or what that means in the first place, but i flashed a 5.1.1 one ( I guess) that i found on that thread successfully.
I would be extremely grateful if you could help me remove these files on my own or provided a 5.1.1 rom with these files removed.
Pure curiosity. Why does the phone 'play' dead when i'm trying to power it while not being charged ?
---------- Post added at 11:18 PM ---------- Previous post was at 10:20 PM ----------
Meh.. i seem to cant flash any ROM anymore. It would just fail mid-process saying "Removed".
Well if you're a windows user you can install Cygwin and use the commands, if you're a MAC user just open up terminal and use:
- to rename the md5 file to tar for unpacking:
mv filename.tar.md5 filename.tar
- to untar (extract) the tar file:
tar -xf filename.tar
- delete the .bin files:
rm *.bin
- repack the .img files into a tar:
tar -cf newfilename.tar *.img
- create md5:
md5sum -t newfilename.tar >> newfilename.tar
- add the md5 file extension so ODIN will recognize it:
mv newfilename. tar newfilename.tar.md5
now you have your "newfilename.tar.md5" to load into the "AP" of your ODIN and flash it.
I've zipped the one I just made while I typed up the commands in cygwin for you to make sure they worked. Uploading, but it's going to take a while. I will check back in ~hour to see if it timed out or not.
Ok download it, unzip it, and load the "G920FXXU3COI9_G920FXEU3COJ2_G920FXXU3COI9.tar.md5" in the AP segment of Odin. Try it first and if it didn't work again, since you've done multiple flashes, it won't be a bad idea to check "nand erase all" one time in ODIN options.
Link removed. Please use link in my next post.
Im extremely grateful for your help, i will try to flash this one and if it won't work i'll check nand erase. I guess i can't screw it more than it already is.
EDIT : No success flashing either way.
---------- Post added at 06:05 AM ---------- Previous post was at 05:50 AM ----------
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Erase...
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> modem.bin
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> modem.bin
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
That's a log, 3 flash attempts in a row, different messages though.
In that g920x master thread it is said so " The only preparation required is the removal of the modem, bootloader, PIT, and related partitions.". I couldn't help but realize that while the flash was going on it still went through modem.bin, is that alright ? I have no idea myself, just trying to figure out why i can't this damned thing to work.
Ah I see the modem file in there. Sorry about that, although it seems that it flashed just fine. I would think the modem file will be there but not get used. But at any rate, I've redone the whole process from the original factory file, and i'm uploading now, no bin files this time! ETA 35 minutes ...
https://drive.google.com/open?id=0B31Omryqpl4nd2NLTG5nY3JxUk0
It still won't flash. I don't know what to do next.
Commodore 64 said:
Well if you're a windows user you can install Cygwin and use the commands, if you're a MAC user just open up terminal and use:
- to rename the md5 file to tar for unpacking:
mv filename.tar.md5 filename.tar
- to untar (extract) the tar file:
tar -xf filename.tar
- delete the .bin files:
rm *.bin
- repack the .img files into a tar:
tar -cf newfilename.tar *.img
- create md5:
md5sum -t newfilename.tar >> newfilename.tar
- add the md5 file extension so ODIN will recognize it:
mv newfilename. tar newfilename.tar.md5
now you have your "newfilename.tar.md5" to load into the "AP" of your ODIN and flash it.
I've zipped the one I just made while I typed up the commands in cygwin for you to make sure they worked. Uploading, but it's going to take a while. I will check back in ~hour to see if it timed out or not.
Ok download it, unzip it, and load the "G920FXXU3COI9_G920FXEU3COJ2_G920FXXU3COI9.tar.md5" in the AP segment of Odin. Try it first and if it didn't work again, since you've done multiple flashes, it won't be a bad idea to check "nand erase all" one time in ODIN options.
Link removed. Please use link in my next post.
Click to expand...
Click to collapse
Help me figure out the exact commands i have to type in cygwin for a filename. What do i have to do to let that terminal know where my file is located, cause i guess you have to mention the location.
Just write the exact command i have to write with the "Filename.tar" in cygwin while filename is located on desktop.
By the way, im requesting them cause i tried the commands you provided and i can't figure out how to use them.
"[email protected] ~
$ tar --delete --file[AP_G920XZCU1BOI2_LLK_CL5369277_QB6240453_REV02_user_low_ship] hidden.img
tar: unrecognized option '--file[AP_G920XZCU1BOI2_LLK_CL5369277_QB6240453_REV02_user_low_ship]'
Try 'tar --help' or 'tar --usage' for more information.
[email protected] ~
$ tar --delete--file[AP_G920XZCU1BOI2_LLK_CL5369277_QB6240453_REV02_user_low_ship] hidden.img
tar: unrecognized option '--delete--file[AP_G920XZCU1BOI2_LLK_CL5369277_QB6240453_REV02_user_low_ship]'
Try 'tar --help' or 'tar --usage' for more information.
"
I typed the exact commands for you already. I put each command under the line that starts with a dash - which tells you what that following command is doing.
Did the file flash and go through on Odin? You probably know you need to reboot the phone freshly back to download mode every time it is connected to Odin or else you'll get a flash error. So open Odin put phone in DL mode and connect USB. If you disconnect USB, you shouldn't just plug it back in, you'll need to reboot the phone into DL mode again!
I think what it is about Cygwin that you're struggling with is that, cygwin isn't given permission to go out of its own folder environment and edit files in other places, such as your desktop. That is a good thing and we wanna keep it that way for security reasons so you don't accidentally damage the OS or delete other files/folders.
So what you'll do is copy the file you want to manipulate by cygwin to home directory of cygwin, and then it will see it and be able to edit it. Something like c:\cygwin\home\[Windows Username] depending on where you installed Cygwin. And yes you can change its home directory to somewhere else on your PC, but that is really not with in the scope of this thread.
Sent from my SM-G920F using XDA-Developers mobile app
Commodore 64 said:
I typed the exact commands for you already. I put each command under the line that starts with a dash - which tells you what that following command is doing.
Did the file flash and go through on Odin? You probably know you need to reboot the phone freshly back to download mode every time it is connected to Odin or else you'll get a flash error. So open Odin put phone in DL mode and connect USB. If you disconnect USB, you shouldn't just plug it back in, you'll need to reboot the phone into DL mode again!
I think what it is about Cygwin that you're struggling with is that, cygwin isn't given permission to go out of its own folder environment and edit files in other places, such as your desktop. That is a good thing and we wanna keep it that way for security reasons so you don't accidentally damage the OS or delete other files/folders.
So what you'll do is copy the file you want to manipulate by cygwin to home directory of cygwin, and then it will see it and be able to edit it. Something like c:\cygwin\home\[Windows Username] depending on where you installed Cygwin. And yes you can change its home directory to somewhere else on your PC, but that is really not with in the scope of this thread.
Sent from my SM-G920F using XDA-Developers mobile app
Click to expand...
Click to collapse
I am a total noob. I cant figure it out really, it may be your way of explaining too but i cant. Just do that, write the exact command you write to remove hidden.bin from the "Filename.tar" which is located in cygwin local director.
---------- Post added at 06:05 PM ---------- Previous post was at 05:54 PM ----------
Commodore 64 said:
Well if you're a windows user you can install Cygwin and use the commands, if you're a MAC user just open up terminal and use:
- to rename the md5 file to tar for unpacking:
mv filename.tar.md5 filename.tar
- to untar (extract) the tar file:
tar -xf filename.tar
- delete the .bin files:
rm *.bin
- repack the .img files into a tar:
tar -cf newfilename.tar *.img
- create md5:
md5sum -t newfilename.tar >> newfilename.tar
- add the md5 file extension so ODIN will recognize it:
mv newfilename. tar newfilename.tar.md5
now you have your "newfilename.tar.md5" to load into the "AP" of your ODIN and flash it.
I've zipped the one I just made while I typed up the commands in cygwin for you to make sure they worked. Uploading, but it's going to take a while. I will check back in ~hour to see if it timed out or not.
Ok download it, unzip it, and load the "G920FXXU3COI9_G920FXEU3COJ2_G920FXXU3COI9.tar.md5" in the AP segment of Odin. Try it first and if it didn't work again, since you've done multiple flashes, it won't be a bad idea to check "nand erase all" one time in ODIN options.
Link removed. Please use link in my next post.
Click to expand...
Click to collapse
Wow, im unbelievably dumb. I just figured out ! You wrote the commands i have to use, one by one. Im so ashamed of myself now. I thought there are some commands i could use not at all they are meant to be used in that order, im so sorry for wasting your time.
I'm afraid i'll still have to bother you one more time
$ tar -xf AP_G920XZCU1BOI2_LLK_CL5369277_QB6240453_REV02_user_low_ship.tar
tar: AP_G920XZCU1BOI2_LLK_CL5369277_QB6240453_REV02_user_low_ship.tar: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
Steps i went through : 1. moved the ROM to C:\cygwin64\filename.tar (renamed it manually, not via command)
2. Wrote tar -xf filename.tar and i got that error you can see there.
---------- Post added at 06:10 PM ---------- Previous post was at 06:05 PM ----------
I GOT IT RIGHT, GOD. I am really sorry to waste your time. Finally, i understood, i read it all once again and i understood. I had to copy the tar file to cygwin64/home/User/. I am extremely grateful and i hope i will get my device to work.
I'm really sorry you had to dealt with such a noob though. I thank you again for your help.

Weird! Difference between Model written on the phone and shown in download mode!

Hi guys, I was about to root my new N915F so I was searching for the right file to use with Odin but I faced a weird problem!
I bought it as a N915F from third-party seller on eBay.
On the box, in the setting/about and underneath the battery it say N915F,
Yet when I enter the download mode, it says N915P!!
I have no idea if even this is possible! Please help I am currently soft-bricked it. Non of these files worked for me:
CF-Auto-Root-tblte-tbltexx-smn915f.tar.md5
CF-Auto-Root-tbltespr-tbltespr-smn915p.tar.md5
So I am seeking to flash the original firmware with Odin but I don't know which firmware I should go with. N915F or N915P?
Any advice?
-----------------------
p.s. Kies does not verify my model & S/N either. I Live in Australia and need a firmware to work here properly.
Flashing firmware also failed. This is the Odin log:
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and the Phone screen:
Odin mode (High speed)
Product name: SM-N915P
Current binary: Custom
System Status: Official
Reactivation Lock: Off
Knos warranty void: 0x1 (4)
Qualcomm secureboot: Enable (CSB)
RP SWREV: S1, T3, R1, A4, P1
SECURE DOWNLOAD: ENABLE
ODIN: flash write failure
That's a Sprint phone. Either the seller got confused or otherwise sold you the wrong device. It's probably not going to work well with the band's you have in Australia. Flash through Odin the stock P software and return it for a F version.
---------- Post added at 12:22 AM ---------- Previous post was at 12:19 AM ----------
Just reread your post. If it says F under the battery then it should be an F. Not sure why it's showing P. Try flashing Mickey's TWRP for the F through Odin. If you can't get it to work use PayPal protection and return it, say it was bricked on arrival.
---------- Post added at 12:23 AM ---------- Previous post was at 12:22 AM ----------
And i reread your logs.... Your bootloader is locked. Return it.
JeremySS said:
That's a Sprint phone. Either the seller got confused or otherwise sold you the wrong device. It's probably not going to work well with the band's you have in Australia. Flash through Odin the stock P software and return it for a F version.
---------- Post added at 12:22 AM ---------- Previous post was at 12:19 AM ----------
Just reread your post. If it says F under the battery then it should be an F. Not sure why it's showing P. Try flashing Mickey's TWRP for the F through Odin. If you can't get it to work use PayPal protection and return it, say it was bricked on arrival.
---------- Post added at 12:23 AM ---------- Previous post was at 12:22 AM ----------
And i reread your logs.... Your bootloader is locked. Return it.
Click to expand...
Click to collapse
Thanks Jeremy for your quick answer. The error was for N915F rom. I tried N915P rom and it worked! seems my bootloader isn't locked (Thank god!) but there is another problem. after flashing with N915p, it didn't worked with my simcard! Like you mentioned before, I assumed that It's not unlocked to my operator. After a while it automatically upgraded a security patch for Android 6.0.1 via wifi and now I can use my simcard without problem.
The problem is it does not go further than 3G! not even H+ nor 4G and this is a nightmare for me. It also heats up a bit.
I have a couple of questions hanging in my mind. Considering that I cannot flash N915F and I cannot root -it doesn't let me so-, what happens If I use a custom N915p rom, with built-in root? using odin I mean.
And my second question is can I do flashing Mickey's TWRP for the F through Odin if I'm not rooted?
No matter what ROM you flash, your bands are going to be mostly incompatible in Australia. They sold you the wrong phone, I'd save yourself some headaches and return it.

Categories

Resources