Have a Note Pro 12.2. Was wanting to install Lineage 16.0 OS on it.
Went into recovery and did a wipe/install.
Was able to root it using Odin.
Downloaded the Lineage files onto an SD card
Downloaded TWRP on the tablet with Google Play
Flashed the boot.img file to recovery
When I try to reboot into recovery, I get a Set Warranty Bit : Recovery on the startup screen and it just hangs there
I think I did originally backup the recovery file, but I cant seem to find it now. Its not on the SD card for the device where I thought it was.
Weirdly,
Booting regularly gets me the same screen
Booting into recovery gets me this screen (obviously)
Booting into bootloader gets me this screen too
I can't seem to power it down either, all key options just seem to loop back to the
bad recovery message.
It no longer 'connects' via USB to my computer either.
Can anyone please help me try to get this back? I can provide any additional info as well.
Im currently trying to find the original firmware for this device, but I haven't been very successful yet.
I would be very grateful for any information or links or help you could offer.
Thank you.
I opened the back just now to pull the battery.
When I replace it, and turn it back on, it goes to the same screen.
You're the second this year to post this problem, and nobody seems to have a fix.
Was thinking of putting a custom rom on mine, but this has put me off that idea.
Revert back to stock
To get your tablet back to a running state and revert everything back to stock, you'll want to use one of these two stock firmwares from the Sammobile site. I picked these two out based on the fact that you said you had a UK device. The firmware in the first link is from 2017, while the second link contains a firmware from 2016.
Personally, I have had no luck getting any of the recent firmware from any of the regions to install on my SM-P905 through ODIN; I get errors about partition sizes. However, installing older firmware from other regions works just fine. Try either of the two links and if the latest one for UK doesn't work, try the other one.
From 2017: https://www.sammobile.com/firmwares/galaxy-note-pro/SM-P905/BTU/download/P905XXSABQC1/127655/
From 2016: https://www.sammobile.com/firmwares/galaxy-note-pro/SM-P905/BTU/download/P905XXUABPG4/89307/
A successful installation of the firmware will reset your bootloader, recovery, and rom back to stock Lollipop. You will be able to use your tablet at that point, although give it a good long time to boot the very first time. This will give you a clean slate to try and install Lineage 16, or any other rom of your choice.
Thanks for the info, Shardsx, I'm downloading them now.
OK, an update.
I let the device power down completely on the Set Warranty Bit : Recovery screen until it died.
I then plugged the tablet into the usb on my desktop, and I was able to press power and the vol down (Recovery screen? It says Odin mode) again, but I havent been able to do much with it through Odin or Kies programs for reflashing the firmware.
If I press power and vol up, I get the same Set Warranty Bit : Recovery screen.
ricosuave95 said:
OK, an update.
I let the device power down completely on the Set Warranty Bit : Recovery screen until it died.
I then plugged the tablet into the usb on my desktop, and I was able to press power and the vol down (Recovery screen? It says Odin mode) again, but I havent been able to do much with it through Odin or Kies programs for reflashing the firmware.
If I press power and vol up, I get the same Set Warranty Bit : Recovery screen.
Click to expand...
Click to collapse
Please elaborate a little on why you haven't been able to do much with it through Odin. In your first step, you said you let the device power down completely until it died, which makes it sound like you drained the battery. You'll want plenty of battery power for this process, so charge your device up. It sounds like you do know how to get into Download/Odin mode, so I won't ask about that. Instead, tell us a little bit more about what you're doing in Odin. Are you loading the firmware using the AP button? Which of the two files are you trying to load? Are you unzipping the firmware file first so that you're flashing the *.tar.md5 file? Are you waiting the appropriate amount of time for the firmware to unpack within Odin before attempting to flash anything? (This step takes a long time too) Are you able to successfully start the firmware upload? What results are you getting? Are you leaving the Odin options as stock when you do this?
I havent had much time to work on it.
Once I do, I'll post and update to it, and your questions.
Thanks
OK, so initially, I let the device die down so that there was nothing left on the battery - I was unable to shut it off. When it would reboot, it always gave me that same Set Warranty Bit : Recovery screen.
I charged it completely, and was able to boot into the download mode, but initially, I couldnt get it to register when I plugged into the USB.
Here is what the recovery/download mode said...
Product Name: Samsing SM-P905
Current Binary: Samsung Official
System Status: Custom
Knox Warranty: Void 0x1 (0)
Qualcomm Secureboot: Enable (CSB)
RP Swerv: S1, T1, R1, A1, P1
Secure Download: Enable
UDC Start
After a few reboots, it did though, and Odin was able to see it.
When I ran Odin, with both firmwares, they both gave me the Invalid EXT4 Image error... I then read online that I probably needed to reflash the PIT file for it.
I tried but was unsuccessful in reading mine off the device using a couple of tools., but I did find one in this thread that I tried... https://forum.xda-developers.com/showthread.php?t=2758925
It didnt seem to work.
I rebooted the device a couple of times, and with one of the firmwares above, it would fail almost immediately with the same EXT4 error, saying something about the volume size being different (40960 vs 204800 ish), the second one, however, seemed to carry on further, almost 3/4 the way through the process before it failed with the same (volume size too big). I think that the PIT I used was incorrect, which is why I was asking for my specific one in another thread. I cant seem to find hardly any PITs for this device.
I also tried using Kies, as after one reboot, it said on screen to use it to recover firmware, but while it did connect to PC via USB, Kies did not detect it, either before the PIT and after.
Heres the Odin error mesage for the second firmware that lasted a while...
<ID:0/003> 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/003> Odin engine v(ID:3.1101)..
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> modem.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Ext4)
<ID:0/003>
<ID:0/003> Complete (Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And the first firmware that failed immediately:
<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/003> Odin engine v(ID:3.1101)..
<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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> boot.img
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Ext4)
<ID:0/003>
<ID:0/003> Complete (Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks to the help from nowheretohide and shardsx, I was able to get my tablet restored to factory... Used Odin and the file provided here:
https://forum.xda-developers.com/showthread.php?t=2758925&page=2
Now, because I obviously messed it up so bad the first time, and am now gun shy, can anyone help me install Lineage 16.0 with a step by step?
ricosuave95 said:
Thanks to the help from nowheretohide and shardsx, I was able to get my tablet restored to factory...
Now, because I obviously messed it up so bad the first time, and am now gun shy, can anyone help me install Lineage 16.0 with a step by step?
Click to expand...
Click to collapse
Don't be gun-shy. You now have almost all the tools to recover from similar issues in the future.
I'm using Odin 3.11 for these instructions. Assumptions I'm making is that you have already downloaded a working version of TWRP for this tablet (remember, the absolute latest versions on the official TWRP site are not compatible with our tablets. Go through the TWRP site and look at the compatibility page for our tablet, or use Valera's custom TWRP).
Step 1: Charge up that tablet.
Step 2: Get into Download mode.
Step 3: Open up Odin. Leave options as default. The one you should really double-check is to make sure that "Re-Partition" is not checked or enabled.
Step 4: Click the AP button and load the TWRP recovery image, and then upload it to your tablet through Odin. Your tablet will reboot automatically reboot. You might as well enter Recovery at this point.
Step 5: I usually store the the ROM images on an external SD card. Inside Recovery, I usually like to do an advanced wipe and wipe out /system /data /cache to . Then, I'll flash the ROM image from the external SD card. After the flash, just reboot the tablet and wait until Android starts up.
I apologize for not providing screenshots. I'm doing this off the top of my head but generally that's what I do to load new ROMs.
The above steps will get you a barebones Android. You'll still have to flash Google's stuff on top if you want to go that way, but basically repeat Step 5 but replace it with the recommended Google packages and that should get you set up pretty good.
I think it was the fact that I used a different version of TWRP. Oops.
Will try again using the correct tools now.
Also, I think Ill go with CRdroid - I'd just like to have a speedier tablet with no Samsung bloatware and maybe a little better battery life, since I replaced the batteries not long ago.
Thank you all!
Got it running with CRdroid, was a little laggier than I liked and some apps were crashing...
Tried lineage 16.0 and found it much better.
Related
Hey folks,
I was trying to root my never before rooted s6 today (64 gb 920 I) using the uni-kernel method using odin for 5.1.1. I put the kernel into AP, and it failed after some seconds thus resulting in the blue screen which says "error has occurred while updating the device software. Use the emergency recovery function in the smart switch PC software."
I tried that and smart switch didn't recognise my device (maybe because USB debugging wasn't on).
Thus I downloaded a stock recovery for my device and I thought I would flash it via ODI. Things go well and the progress bar is 3/4th of the way through on my device and it suddenly says FAIL (shown below). I've tried with ODIN 3.10.6 and with 3.10.7 with the same results
<ID:0/003>Get PIT for Mapping
<ID:0/003> Firmware update Start!!
<ID:0/003> cm.bin <ID:0/003>
sboot.bin
<ID:0/003>NAND Write Start!!
<ID:0/003> cm.bin
<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)
What's unusual about this (to the best of my knowledge through forum search. I could be wrong and this could be common. If so I apologise) is that I've seen help threads about Odin failing at hidden.img or NAND Write Start but not during system.img. Does the fact that it's failed during system.img in particular tell us something?
Also, I can't access stock recovery, just the download section.
No clue why it's doing this. I would appreciate any help possible.
Thanks so much in advance. This means a lot.
Your current phone's firmware CSC should be same or within the region CSC of your downloaded firmware.
Hidden.img do have different partition size per Country/region. If you flash a not supported firmware, it will fail.
I.e., if your from France, just download the France firmware.so that you wont need to flash a pit file for your phone.
You can Search here at forum with keyword galaxy s6 pit file.
Or probably, your pc <> phone connection is unstable. Be sure it is connected properly, the usb cable should be in good performance etc.
I had the same happening. Don't sweat it really, no need to use that Smart Switch thing, Odin should still see the phone anyway, so just go ahead and flash a different image from Sammobile, possibly use one for your country and you'll be good.
hi
hi,
phone came to me with 5.1.1 latest build of EE-UK
G920FXXU3QOJF_G920FEVR3QOJF_EVR
I root with
S6_UniKernel_v8-0001-ODIN
now download mode give strange issue here are pics
http://www.4shared.com/download/IOp...6ae669f7568a293d60885275688d80d795f&lgfp=3000
http://www.4shared.com/download/E9y...a9b8785cf4e8f45a6d864fc174d5cca195f&lgfp=3000
flashing is also giving error in odin3 v3.10
here are logs of flashing
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920FXXU3QOJF_G920FEVR3QOJF_G920FXXU3COJ2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin engine v(ID:3.1005)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> SingleDownload.
<ID:0/010> sboot.bin
<ID:0/010> NAND Write Start!!
<ID:0/010> cm.bin
<ID:0/010> boot.img
<ID:0/010> recovery.img
<ID:0/010> system.img
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I also try to recover with smart switch emergency recovery but failed, it gives me no emergency code
please suggest me as early possible, phone is brand new and just unbox it,
is it some kernel issue with new build ?
urgent help will be highly appreciated,
thanks regards
About the lights... i don't know what to say, it's strange.
Try to reboot to download mode again (Press Volume Down + Power for about 10 seconds to exit and after the screen goes black, press Volume Down + Home + Power to get into download mode again).
Download an Odin flashable custom recovery (TWRP or PhilZ) and flash it using Odin. In options tab of Odin UNCHECK Auto-Reboot. After installing, exit download mode and when the screen goes black again, press and hold Volume Up + Home + Power. Now you should boot into one of the recoveries you have just installed.
Now, download a custom kernel from XDA (it could be arter97 kernel, Adam kernel or any other) and install it in the recovery.
Now you should be able to boot.
P.S.: To install the custom kernel you have to transfer the file into the device somehow. So, if you install PhilZ, use sideload installation (it is located in the Install zip context in PhilZ) for the kernel zip, and if you choose TWRP, connect the phone to the PC, go to Mounts, disable MTP and then reenable it and your PC should now recognize the phone. Then transfer the kernel zip into internal memory and install.
Villa_Man said:
About the lights... i don't know what to say, it's strange.
Try to reboot to download mode again (Press Volume Down + Power for about 10 seconds to exit and after the screen goes black, press Volume Down + Home + Power to get into download mode again).
Download an Odin flashable custom recovery (TWRP or PhilZ) and flash it using Odin. In options tab of Odin UNCHECK Auto-Reboot. After installing, exit download mode and when the screen goes black again, press and hold Volume Up + Home + Power. Now you should boot into one of the recoveries you have just installed.
Now, download a custom kernel from XDA (it could be arter97 kernel, Adam kernel or any other) and install it in the recovery.
Now you should be able to boot.
P.S.: To install the custom kernel you have to transfer the file into the device somehow. So, if you install PhilZ, use sideload installation (it is located in the Install zip context in PhilZ) for the kernel zip, and if you choose TWRP, connect the phone to the PC, go to Mounts, disable MTP and then reenable it and your PC should now recognize the phone. Then transfer the kernel zip into internal memory and install.
Click to expand...
Click to collapse
thanks for reply, I appreciate it
I install "twrp-2.8.7.1-zeroflte.img" than power of phone than boot into recovery, At recovery it shows trwp logo than black screen than logo(bootloop) but there is no recovery menu, I noted that color are showing normal when it shows twrp logo not like when it is download mode(good sign) ,
update: I flash stock recovery than instal twrp and result in successfully boot into twrp, when i try to install adam kernel it gives me error
E: Error executing updater binary in zip '/sdcard/sm-g920f_Adam.Kernel.2.0.cwp.zip
E: Error flashing zip '/sdcard/sm-g920f_Adam.Kernel.2.0.cwp.zip
Update partition details
E:unable to mount ' /system'
....done
than i wipe cache, dalvik cache and system , after that adam kernel successfully installed but problem is still there,
here is pic of in twrp , you can see display is normal
http://www.4shared.com/download/Jeh...c96207d729645cbd9ee34776c82af38e95f&lgfp=3000
nsnobel2 said:
thanks for reply, I appreciate it
I install "twrp-2.8.7.1-zeroflte.img" than power of phone than boot into recovery, At recovery it shows trwp logo than black screen than logo(bootloop) but there is no recovery menu, I noted that color are showing normal when it shows twrp logo not like when it is download mode(good sign) ,
Click to expand...
Click to collapse
Don't use the .img. Install the .tar.md5 of TWRP 2.8.7.2. You can download it if you search for zeroflte on www.twrp.me (devices).
Or you can try arter97's PhilZ Touch Recovery in .tar format.
Thanks villa for your suggestion, I update my 2nd post , pls read and suggest me
nsnobel2 said:
Thanks villa for your suggestion, I update my 2nd post , pls read and suggest me
Click to expand...
Click to collapse
Hmm, I guess the system partition was erased even if it failed in Odin.
Install a Custom ROM (like Arrow ROM or Crisscross which you can find at Edge forums) and it should be ok.
The kernel would have worked if you had the system partition intact.
Villa_Man said:
Hmm, I guess the system partition was erased even if it failed in Odin.
Install a Custom ROM (like Arrow ROM or Crisscross which you can find at Edge forums) and it should be ok.
The kernel would have worked if you had the system partition intact.
Click to expand...
Click to collapse
I already start downloading this custom rom,
http://forum.xda-developers.com/galaxy-s6/development/rom-pure-stock-extralite-v1-0-t3232498
hope this will work,
nsnobel2 said:
I already start downloading this custom rom,
http://forum.xda-developers.com/galaxy-s6/development/rom-pure-stock-extralite-v1-0-t3232498
hope this will work,
Click to expand...
Click to collapse
This is good, too.
I hope you will solve the problems.
Villa_Man said:
This is good, too.
I hope you will solve the problems.
Click to expand...
Click to collapse
net was so slow why so I am replying late, I install this file and after reboot phone shows samsung logo than restart
now what should I do?
Does your phone shows the bootanimation or only SAMSUNG GALAXY S6?
Gesendet von meinem SM-G920F mit Tapatalk
justgamer01 said:
Does your phone shows the bootanimation or only SAMSUNG GALAXY S6?
Gesendet von meinem SM-G920F mit Tapatalk
Click to expand...
Click to collapse
yes it shows "Samsng Galaxy S6 powered by android" and a red line upper left corner " Kernel is not seandroid enforcing"
here is pic you can see some blur
http://www.4shared.com/download/vkP...f010f2355f11851cda264c7acf955eab95f&lgfp=3000
nsnobel2 said:
net was so slow why so I am replying late, I install this file and after reboot phone shows samsung logo than restart
now what should I do?
Click to expand...
Click to collapse
Did you wipe the Cache, Data and System before installing the file?
EDIT: After seeing the last image, I suggest reinstalling the bootloader. Something is not right with those lights.
https://drive.google.com/folderview...sharing&tid=0B40ItdHKfkyQd1hJQXVDU3dDU2c#list
Download this firmware. Before installing it with Odin, go in TWRP and wipe Cache, Dalvik Cache, Data and System. And then close the recovery mode and enter download mode. Be sure to use the latest version of Odin which is 3.10.7 (you can download it here: http://forum.xda-developers.com/attachment.php?attachmentid=3446301&d=1440131361). After checking is everything is set up, put all the files provided in the zip into the correct place and start the operation. And a note, to be sure it will be alright, put the phone on a table or something while doing the operations and do not move the cable while it installs in Odin, it might give you a fail.
P.S.: If at the end it will give you an error at installing the modem, do not panic, restart download mode and install only the CP file which contains modem.bin.
Villa_Man said:
Did you wipe the Cache, Data and System before installing the file?
Click to expand...
Click to collapse
I did not but it ask for during flash the rom,
Dont know what happened but suddenly phone starts and go to main menu, it is normal but when I start the phone same error occurs, no normal start with splash screen and same strange screen in download mode
nsnobel2 said:
I did not but it ask for during flash the rom,
Dont know what happened but suddenly phone starts and go to main menu, it is normal but when I start the phone same error occurs, no normal start with splash screen and same strange screen in download mode
Click to expand...
Click to collapse
I edited my last post, look at the words I added.
Villa_Man said:
Did you wipe the Cache, Data and System before installing the file?
EDIT: After seeing the last image, I suggest reinstalling the bootloader. Something is not right with those lights.
https://drive.google.com/folderview...sharing&tid=0B40ItdHKfkyQd1hJQXVDU3dDU2c#list
Download this firmware. Before installing it with Odin, go in TWRP and wipe Cache, Dalvik Cache, Data and System. And then close the recovery mode and enter download mode. Be sure to use the latest version of Odin which is 3.10.7 (you can download it here: http://forum.xda-developers.com/attachment.php?attachmentid=3446301&d=1440131361). After checking is everything is set up, put all the files provided in the zip into the correct place and start the operation. And a note, to be sure it will be alright, put the phone on a table or something while doing the operations and do not move the cable while it installs in Odin, it might give you a fail.
P.S.: If at the end it will give you an error at installing the modem, do not panic, restart download mode and install only the CP file which contains modem.bin.
Click to expand...
Click to collapse
I have this file in my pc
G920FXXU3COI9_G920FBTU3COJ1_G920FXXU3COI9_HOME.tar.md5
but it is only 1 file not 3 or 4 files including bootloader file? is you file consists of 4 files? and should i use pit file too?
Deleted
System.img cannot complete flash it gives error, flashing stuck here almost 3-4 minutes than failed, here is pic
http://www.4shared.com/download/iCK...10754c07a4a514e5830f94c352d25d5595f&lgfp=3000
I did not use pit file , should I?
update: Just flash csc file and than flash all 4 files again and result was same as you told me that at the end it will give error at installing modem here are logs
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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/010> Odin engine v(ID:3.1100)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Set PIT file..
<ID:0/010> DO NOT TURN OFF TARGET!!
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> SingleDownload.
<ID:0/010> sboot.bin
<ID:0/010> NAND Write Start!!
<ID:0/010> param.bin
<ID:0/010> cm.bin
<ID:0/010> boot.img
<ID:0/010> recovery.img
<ID:0/010> system.img
<ID:0/010> modem.bin
<ID:0/010> Transmission Complete..
<ID:0/010> Now Writing.. Please wait about 2 minutes
<ID:0/010> FAIL!
<ID:0/010>
<ID:0/010> Receive Response from boot-loader
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/010> Removed!!
Click to expand...
Click to collapse
later I install cp file but still failed here are logs
<ID:0/010> 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/010> Odin engine v(ID:3.1100)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> SingleDownload.
<ID:0/010> modem.bin
<ID:0/010> NAND Write Start!!
<ID:0/010> Transmission Complete..
<ID:0/010> Now Writing.. Please wait about 2 minutes
<ID:0/010> FAIL!
<ID:0/010>
<ID:0/010> Receive Response from boot-loader
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
now at phone startup following message shows with yellow triangle
" An error has occurred while updating the device software us the Emergency recovery function in the Smart Switch PC software"
nsnobel2 said:
now at phone startup following message shows with yellow triangle
" An error has occurred while updating the device software us the Emergency recovery function in the Smart Switch PC software"
Click to expand...
Click to collapse
There must be a way to install the modem...
Try to extract the modem.bin from the CP zip and rename it to modem.bin.tar. Try to install it then in the same AP or CP slot in Odin (you can try to install it either on AP or CP and see which one works).
Villa_Man said:
There must be a way to install the modem...
Try to extract the modem.bin from the CP zip and rename it to modem.bin.tar. Try to install it then in the same AP or CP slot in Odin (you can try to install it either on AP or CP and see which one works).
Click to expand...
Click to collapse
I just install that custom rom again and phone is again in menu , PhoneInfo.apk shows following details of softare
Bootloader version:
G920FXXU3COI9
BASEBAND VERSION
G920FXXU3COJ2
PDA
G920FXXU3QOKX
CSC
G920FOJP3QOL1
if u need any details than tell me pls
nsnobel2 said:
I just install that custom rom again and phone is again in menu , PhoneInfo.apk shows following details of softare
Bootloader version:
G920FXXU3COI9
BASEBAND VERSION
G920FXXU3COJ2
PDA
G920FXXU3QOKX
CSC
G920FOJP3QOL1
if u need any details than tell me pls
Click to expand...
Click to collapse
So now your phone works?
Well if now everything is ok, I guess I don't need anything more.
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.
I rooted my phone with odin and i decided later that i wanted to unroot it. So i went into SuperSu and went to settings and tried the full unroot thing. My phone restarted and everything and i went to the root checker and it said i was unrooted. Then, i was still getting the Security notification that always pops up saying " Security Notice: Unauthorized actions have been detected ". So i went to that and i decided to try to factory reset my phone from that screen. So I cleared all the data on the phone and everything and it came back completely reset. The only problem was that I am still getting the notification. I have no idea what to do to get rid of it and i want to completely unroot my phone. I have looked all over the internet for the Galaxy S7 Verizon stock firmware. I can't find the firmware anywhere and its really bugging me having that notification there still. If there is no unroot available for the S7 right now, i was wondering if there is someway i can hide that notification for now to give me peace of mind. Thank you so much in advance.
Parteeajp said:
I rooted my phone with odin and i decided later that i wanted to unroot it. So i went into SuperSu and went to settings and tried the full unroot thing. My phone restarted and everything and i went to the root checker and it said i was unrooted. Then, i was still getting the Security notification that always pops up saying " Security Notice: Unauthorized actions have been detected ". So i went to that and i decided to try to factory reset my phone from that screen. So I cleared all the data on the phone and everything and it came back completely reset. The only problem was that I am still getting the notification. I have no idea what to do to get rid of it and i want to completely unroot my phone. I have looked all over the internet for the Galaxy S7 Verizon stock firmware. I can't find the firmware anywhere and its really bugging me having that notification there still. If there is no unroot available for the S7 right now, i was wondering if there is someway i can hide that notification for now to give me peace of mind. Thank you so much in advance.
Click to expand...
Click to collapse
Hi mate
Just flash a stock rom with odin on top of it
http://www.sammobile.com/firmwares/database/SM-G930V/
back up everything important before you do it ..just in case
Hey, i have a whole new problem now. When i was trying to unroot my phone, i accidentally installed the wrong firmware on to the phone. I turned my verizon phone into a t-mobile phone.
Im not exactly sure what flashing is, but is it where you put the BL, AP, CP, and CSC things into Odin and start it?
I might have already done that because i found the verizon firmware somewhere and when i try to do it in odin. It gives me an error and says fail.
Parteeajp said:
Hey, i have a whole new problem now. When i was trying to unroot my phone, i accidentally installed the wrong firmware on to the phone. I turned my verizon phone into a t-mobile phone.
Im not exactly sure what flashing is, but is it where you put the BL, AP, CP, and CSC things into Odin and start it?
I might have already done that because i found the verizon firmware somewhere and when i try to do it in odin. It gives me an error and says fail.
Click to expand...
Click to collapse
Hi
Yes you need to flash it with Odin
did you downloaded from sammobile?
if not try i from there , follow their instructions :
Extract (unzip) the firmware file
Download Odin v3.11.1
Extract Odin ZIP file
Open Odin v3.11.1
Reboot Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
Connect phone and wait until you get a blue sign in Odin
Add the firmware file to AP / PDA
Make sure re-partition is NOT ticked
Click the start button, sit back and wait few minutes
Usually sammobile has only one tar file ( unzip it just once) , back up you photos and files before just in case
Check this thread is not for your phone but the basics apply to all samsung phones
http://forum.xda-developers.com/galaxy-s7/how-to/official-stock-firmware-update-odin-t3369431
Parteeajp said:
Hey, i have a whole new problem now. When i was trying to unroot my phone, i accidentally installed the wrong firmware on to the phone. I turned my verizon phone into a t-mobile phone.
Im not exactly sure what flashing is, but is it where you put the BL, AP, CP, and CSC things into Odin and start it?
I might have already done that because i found the verizon firmware somewhere and when i try to do it in odin. It gives me an error and says fail.
Click to expand...
Click to collapse
Can you post a pic of the back of the phone showing the model number as SM-G930V and FCC ID. Then take a pic of the bootloader screen and show what what model number it has, if flash successfully it should be showing as SM-G930T. If proven true then it may seem that as the S7 is a Universal Hardware phone (QCOMM that is).
Please Help
I'm not sure if this is the right place to post, but I have a similar problem.
I tried flashing SM-G930U to my SM-G930V.
Odin failed, and I rebooted my phone. It will only reboot to download mode or recovery mode.
- I have tried redownloading files to check for corruption.
- Using different versions of Odin.
- Flashing to the stock files, which also fails.
- Using stock USB cable.
- Using different ports.
It doesn't seem like Odin will flash anything
Benaiah1287: I am in the exact same predicament...
I got the G930U firmware from sammobile and have tried flashing it with Odin versions 3.10, 3.11, and 3.12, all with failure.
My next steps are to try the stock G930V firmware or to see if the Samsung Software Upgrade Assistant can repair.
Benaiah1287 said:
I'm not sure if this is the right place to post, but I have a similar problem.
I tried flashing SM-G930U to my SM-G930V.
Odin failed, and I rebooted my phone. It will only reboot to download mode or recovery mode.
- I have tried redownloading files to check for corruption.
- Using different versions of Odin.
- Flashing to the stock files, which also fails.
- Using stock USB cable.
- Using different ports.
It doesn't seem like Odin will flash anything
Click to expand...
Click to collapse
nitropowrd said:
Benaiah1287: I am in the exact same predicament...
I got the G930U firmware from sammobile and have tried flashing it with Odin versions 3.10, 3.11, and 3.12, all with failure.
My next steps are to try the stock G930V firmware or to see if the Samsung Software Upgrade Assistant can repair.
Click to expand...
Click to collapse
You need to use the prince comsey's modified odin that bypasses SHA verification.
Saga's End
aromerblz said:
You need to use the prince comsey's modified odin that bypasses SHA verification.
Click to expand...
Click to collapse
I hunted down the Comsy version of Odin 3.12 Odin3_v3.12_PrinceComsy.zip (MD5 hash 136E707B39C2E4CDC47820C68065CD5C)
but I still received a failure with the following output:
<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> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and on the phone (Download-mode) display:
DVIF!!
S REV CHECK FAIL : [aboot]Fused 4 > Binary 2
[1] eMMC write fail : aboot
I also tried it without copying the BL file only, as I have also read that this could work, but no dice.
I then tried the stock G930V firmware (for my G930V) with the following result:
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> emmc_appsboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
on reboot it gave me the 'Software Update Failed' screen
I then used the Samsung Repair Utility and after half an hour it was able to restore the original OS. It did give me a new warning about it not being able to make calls until it was set up with a Verizon account, but after reboot it still just has the message "SIM card is not from Verizon Wireless," so I'm assuming it is still in its original "factory unlocked" state.
So, about 8 hours of tinkering later, I cannot recommend trying to flash the SM-G930V at all.
My sole purpose for all this was in trying to get compatibility with Republic Wireless (which claims it supports the unlocked S7 but really means the North American 930U only).
nitropowrd said:
I hunted down the Comsy version of Odin 3.12 Odin3_v3.12_PrinceComsy.zip (MD5 hash 136E707B39C2E4CDC47820C68065CD5C)
but I still received a failure with the following output:
<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> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and on the phone (Download-mode) display:
DVIF!!
S REV CHECK FAIL : [aboot]Fused 4 > Binary 2
[1] eMMC write fail : aboot
I also tried it without copying the BL file only, as I have also read that this could work, but no dice.
I then tried the stock G930V firmware (for my G930V) with the following result:
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> emmc_appsboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
on reboot it gave me the 'Software Update Failed' screen
I then used the Samsung Repair Utility and after half an hour it was able to restore the original OS. It did give me a new warning about it not being able to make calls until it was set up with a Verizon account, but after reboot it still just has the message "SIM card is not from Verizon Wireless," so I'm assuming it is still in its original "factory unlocked" state.
So, about 8 hours of tinkering later, I cannot recommend trying to flash the SM-G930V at all.
My sole purpose for all this was in trying to get compatibility with Republic Wireless (which claims it supports the unlocked S7 but really means the North American 930U only).
Click to expand...
Click to collapse
You are trying to flash a downgraded bootloader version/firmware. Your phone has bootloader v4 and you are trying to flash a v2 firmware. Flashing a v4 or above will work.
aromerblz said:
You are trying to flash a downgraded bootloader version/firmware. Your phone has bootloader v4 and you are trying to flash a v2 firmware. Flashing a v4 or above will work.
Click to expand...
Click to collapse
For anyone keeping up, the source of the 930U with bootloader version 4 is here
...which I found through Fix For Those Who Tried Flashing The g930u Firmware
Too bad I just ordered a G930U instead thinking there was no current release
It appears it was also uploaded to sammobile just yesterday...but I am only assuming because the naming convention does not agree to the guide I found here, and I don't understand the 'PL#' part
nitropowrd said:
For anyone keeping up, the source of the 930U with bootloader version 4 is here
...which I found through Fix For Those Who Tried Flashing The g930u Firmware
Too bad I just ordered a G930U instead thinking there was no current release
It appears it was also uploaded to sammobile just yesterday...but I am only assuming because the naming convention does not agree to the guide I found here, and I don't understand the 'PL#' part
Click to expand...
Click to collapse
thanks a lot. I had 2 S7s. One I was able to flash with G930UUEU2APEH, but the other one couldn't...but I could with the one you posted ( SM-G930U_1_20160921124641_vvcrzx3ej5_fac)
Help please <ID:0/006> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> skip file list for home binary
<ID:0/006> persist.img.ext4
<ID:0/006> Home Binary Download
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> emmc_appsboot.mbn
<ID:0/006> lksecapp.mbn
<ID:0/006> xbl.elf
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
aromerblz said:
You are trying to flash a downgraded bootloader version/firmware. Your phone has bootloader v4 and you are trying to flash a v2 firmware. Flashing a v4 or above will work.
Click to expand...
Click to collapse
I am having the same problem. How do I know the version before trying and failing until I get one that works?
Couldn't the boot loader 'version' be changed/hacked within the (down graded) boot loader so the version check would pass?
I need some troubleshoot tinkering
I have received a Note 10.1 (GT-N8020) from a friend who would appreciate if I could salvage pictures and documents that was on this tablet, and let us not debate his backup options.
Problem with the tablet is it wont boot properly.
It just hangs on the Samsung animation.
As first troubleshoot step my thought was to boot into Recovery and wipe cache and dalvik, just to get it booting. But I simply cannot boot into Recovery. I can only get to ODIN mode.
After several attempts giving up on Recovery, my plan was to flash a new Recovery onto tablet by using ODIN mode, however all attempts both with several different version of ODIN and different version of TWRP fails to be flashed.
Code:
<ID:0/009> 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/009> Odin engine v(ID:3.1401)..
<ID:0/009> File analysis..
<ID:0/009> Total Binary size: 6 M
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> NAND Write Start!!
<ID:0/009> SingleDownload.
<ID:0/009> recovery.img
<ID:0/009> FAIL!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So here I am, feeling stuck.
Either I am thinking there is a defect with the NAND chip, why the tablet must have failed in first place, however I can also find some articles claiming some of Samsung's tablets does not have a Recovery mode/partition, is this true for this model?
I have not reflashed entire tablet, since I need access to whatever data there must be on the tablet.
I also found description on sammobile explaining how to re-install ROM while preserving apps and data, but they keep mentioning ROMs based on 5 files (AP, BL, CP, CSC, HOME_CSC), while I can only find ROMs based on single files (AP)
Link to article (see step 2)
https://www.sammobile.com/samsung/galaxy-note-101/firmware/GT-N8020/CNX/download/N8020XXUDOH1/55623/
Anyone know where I can download such ROM based on 5 files (Samsung official ROM)
Suggestions for any other methods I can try to get the data out of tablet?
Try Philz Recovery instead of TWRP .
Not sure if ADB will work for you .
JJEgan said:
Try Philz Recovery instead of TWRP .
Not sure if ADB will work for you .
Click to expand...
Click to collapse
Philz Recovery tried to flash and fails too
Recover data try ADB .
JJEgan said:
Recover data try ADB .
Click to expand...
Click to collapse
IIRC would that not require USB debugging enabled (which I cannot since it will not boot) and the Android in a running state?
Thanks to the SamFirm tool I managed to find some ROMs configured with CSC_HOME. On first shot it failed to flash these ROMs too. But I will try some more tinkering
I guess your eMMC is locked.
So the only possible solution would be to desolder it and read the data directly out of it.
Whereas the OP gives a link to an "article" at sammobile, that page has since changed and no longer gives any useful instruction for re-flashing while preserving apps and data. However, I believe that the original "step 2" of that page referred to was : "2. Add each file to its respective field in Odin v3.14.4. Use CSC_*** if you want to do a clean flash or HOME_CSC_*** if you want to keep your apps and data."
Probably a bit late for the original poster from 2020 .
Could try flashing with No CSC .
JJEgan said:
Probably a bit late for the original poster from 2020 .
Could try flashing with No CSC .
Click to expand...
Click to collapse
Sure, there's a good chance that the original tablet has since become e-waste, however, there is also some chance that it's sitting in his friend's drawer in the slim hope of a resolution.
However, my clarification about "step 2" is for the benefit of other readers of this thread, since the OP will already know this information.
My own GT-N8020 tablet has the exact same problem. I was able to overcome the flashing difficulty by using the Prince Comsy patched version of Odin 3.12.3 (which disregards spurious USB communications errors that tend to occur).
However, re-flashing without the CSC portion of the firmware doesn't resolve the problem. I can't include the CSC portion as this will clear the data that I need to recover, and I haven't yet been able to find a HOME_CSC alternative.
Joe.