We just picked up a pristine unlocked S6 for my wife as a replacement for her beat up old Iphone. The device ran perfectly once it was charged up. I set up WiFi and downloaded a few apps from the Play Store and all seemed perfect. The big UPGRADE message came up, telling me it was due for what I assume was the newly released Android 7 upgrade, and I stupidly said yes. Something must have gone wrong, as the download and install took way less time than I would have thought correct. The phone now bootloops continuously, about every 30 seconds, making it impossible to reach whatever ROM may still be there. I am able to reach Recovery, and Download mode no problem. Numerous wipes and factory resets have done nothing. I downloaded a Lollipop 5.0.2 ZIP, specific to Bell, the MD5 checked out OK. Sammy USB drivers are good. I can connect with Odin but the upload fails right away at sboot.bin.
Am I causing myself problems by trying to flash a stock Bell ROM on an unlocked phone? The ROMS are hard to find and most are stored in pay for use sites that literally take 12 hours to download if the user doesn't set up an account. Any suggestions as to how I can get this back running again, or is it bricked? I've spent about 8 hours on Google and trying everything I could find, and nothing I've come across has worked.
Alternatively, I'm fine with rooting and flashing a custom ROM (I've been doing them for years), though the boss would prefer to stay stock. Trouble is, without access to an existing stable ROM on the phone, I can't see how I can root in the first place. Are some ROMS flashable without rooting, and if so, what are some good ones? Would I simply load them into Odin and flash to the phone?
Thanks in advance.
jp071848 said:
We just picked up a pristine unlocked S6 for my wife as a replacement for her beat up old Iphone. The device ran perfectly once it was charged up. I set up WiFi and downloaded a few apps from the Play Store and all seemed perfect. The big UPGRADE message came up, telling me it was due for what I assume was the newly released Android 7 upgrade, and I stupidly said yes. Something must have gone wrong, as the download and install took way less time than I would have thought correct. The phone now bootloops continuously, about every 30 seconds, making it impossible to reach whatever ROM may still be there. I am able to reach Recovery, and Download mode no problem. Numerous wipes and factory resets have done nothing. I downloaded a Lollipop 5.0.2 ZIP, specific to Bell, the MD5 checked out OK. Sammy USB drivers are good. I can connect with Odin but the upload fails right away at sboot.bin.
Am I causing myself problems by trying to flash a stock Bell ROM on an unlocked phone? The ROMS are hard to find and most are stored in pay for use sites that literally take 12 hours to download if the user doesn't set up an account. Any suggestions as to how I can get this back running again, or is it bricked? I've spent about 8 hours on Google and trying everything I could find, and nothing I've come across has worked.
Alternatively, I'm fine with rooting and flashing a custom ROM (I've been doing them for years), though the boss would prefer to stay stock. Trouble is, without access to an existing stable ROM on the phone, I can't see how I can root in the first place. Are some ROMS flashable without rooting, and if so, what are some good ones? Would I simply load them into Odin and flash to the phone?
Thanks in advance.
Click to expand...
Click to collapse
Just use Samsung smartswitch software to restore firmware.
Your device's model is SM-G920W8, right?
And the only thing you did is flash an firmware via Odin and stuck on sboot.bin?
forumber2 said:
Your device's model is SM-G920W8, right?
And the only thing you did is flash an firmware via Odin and stuck on sboot.bin?
Click to expand...
Click to collapse
He tried to downgrade from marshmallow to lollipop that's why it failed.
sofir786 said:
He tried to downgrade from marshmallow to lollipop that's why it failed.
Click to expand...
Click to collapse
I know that, I want be sure that he/she didn't do anything (like wiping /data) expect trying to downgrade. I'll write my procedure according that for get the device back up and running without any data loss.
And he/she shouldn't use Smart Switch to restore the firmware in first place, it will cause data loss.
forumber2 said:
I know that, I want be sure that he/she didn't do anything (like wiping /data) expect trying to downgrade. I'll write my procedure according that for get the device back up and running without any data loss.
And he/she shouldn't use Smart Switch to restore the firmware in first place, it will cause data loss.
Click to expand...
Click to collapse
Ahh right okay, so using smart switch wipes internal storage? Anyhoo I won't ask too much now don't wanna hijack the post, do your thing
sofir786 said:
Ahh right okay, so using smart switch wipes internal storage? Anyhoo I won't ask too much now don't wanna hijack the post, do your thing
Click to expand...
Click to collapse
Thanks for the quick responses everyone. Apologies, it was very late when I made the OP, and I forgot to mention that I had tried both Kies AND Smartswitch. When I connected the phone while it was bootlooping, and for the brief period while whatever ROM was showing before the reboot, Smartswitch connected with it, but immediately fired back that "USB file transfer is not allowed...". There does seem to be some, or all, of a ROM there, but it is still in the setup stage, which is expected after a full factory reset. I don't have time to go in and enable USB Transfer as it reboots well before I can get into Settings. When I connect while it was in Download mode, SS seems to hang on "Connecting to your device" then fails.
"Your device's model is SM-G920W8, right?
And the only thing you did is flash an firmware via Odin and stuck on sboot.bin?"
SM-G920W8 yes. After the Odin problems, per my original post, I also tried, based on suggestions all over the interweb, a wipe, as well as resorting to a factory reset, through the stock recovery. Nothing worked, the bootloop continues, and the factory reset causes the system to go into setup mode. In the 30 seconds between reboots, I don't have time to get into the ROM to make changes like enabling USB transfer/debugging before it reboots again.
"He tried to downgrade from marshmallow to lollipop that's why it failed"
I assumed, when I first clicked the button and caused the problem, that I was UPGRADING from whatever ROM was properly installed, to Android 7.0/Nougat. This failed and induced the bootloop. I then thought I would try and install Lollipop through Odin, which brings up the sboot.bin fail. From your comment, should I try to find a Nougat 7.0 ROM and do the UPGRADE manually via Odin? Is that more likely to work than a downgrade.
Regarding the comments about data loss, I am not concerned about that, the phone was new and did not contain any data worth saving, it hadn't been set up yet. In any case, I tried a few factory resets, so any data would have been wiped during that action as well.
I'm getting nervous, I seemed to have really borked up this phone, I sure hope you experts can bail me out. ;o(
Thanks again for the help...
jp071848 said:
Thanks for the quick responses everyone. Apologies, it was very late when I made the OP, and I forgot to mention that I had tried both Kies AND Smartswitch. When I connected the phone while it was bootlooping, and for the brief period while whatever ROM was showing before the reboot, Smartswitch connected with it, but immediately fired back that "USB file transfer is not allowed...". There does seem to be some, or all, of a ROM there, but it is still in the setup stage, which is expected after a full factory reset. I don't have time to go in and enable USB Transfer as it reboots well before I can get into Settings. When I connect while it was in Download mode, SS seems to hang on "Connecting to your device" then fails.
"Your device's model is SM-G920W8, right?
And the only thing you did is flash an firmware via Odin and stuck on sboot.bin?"
SM-G920W8 yes. After the Odin problems, per my original post, I also tried, based on suggestions all over the interweb, a wipe, as well as resorting to a factory reset, through the stock recovery. Nothing worked, the bootloop continues, and the factory reset causes the system to go into setup mode. In the 30 seconds between reboots, I don't have time to get into the ROM to make changes like enabling USB transfer/debugging before it reboots again.
"He tried to downgrade from marshmallow to lollipop that's why it failed"
I assumed, when I first clicked the button and caused the problem, that I was UPGRADING from whatever ROM was properly installed, to Android 7.0/Nougat. This failed and induced the bootloop. I then thought I would try and install Lollipop through Odin, which brings up the sboot.bin fail. From your comment, should I try to find a Nougat 7.0 ROM and do the UPGRADE manually via Odin? Is that more likely to work than a downgrade.
Regarding the comments about data loss, I am not concerned about that, the phone was new and did not contain any data worth saving, it hadn't been set up yet. In any case, I tried a few factory resets, so any data would have been wiped during that action as well.
I'm getting nervous, I seemed to have really borked up this phone, I sure hope you experts can bail me out. ;o(
Thanks again for the help...
Click to expand...
Click to collapse
I think Upgrading to nougat via Odin would be best bet @forumber2 has a good set of steps which are easy to follow .
sofir786 said:
I think Upgrading to nougat via Odin would be best bet @forumber2 has a good set of steps which are easy to follow .
Click to expand...
Click to collapse
I did a search under that name, and came across a reference to a great app called SamFirm (not sure if that's what you meant by a good set of steps ;o). I ran SamFirm using SM-G920W8, and tried both Regions BMC (Bell) and XAC (Canada). Downloaded and unzipped, the XAC file name was SM-G920W8_1_20170428185952_f736z32l4i_fac.zip.enc4, and entered the AP, BL, CP and CSC links in Odin. Failed both times with the same Odin message:
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
On the phone, on the Downloading screen, the error was "SECURE CHECK FAIL : (PIT)"
Googling these messages, the general consensus seems to be that these errors indicate an attempt to flash an incorrect ROM, but I'm running out of options for finding a "correct" one.
Thanks again...
jp071848 said:
I did a search under that name, and came across a reference to a great app called SamFirm (not sure if that's what you meant by a good set of steps ;o). I ran SamFirm using SM-G920W8, and tried both Regions BMC (Bell) and XAC (Canada). Downloaded and unzipped, the XAC file name was SM-G920W8_1_20170428185952_f736z32l4i_fac.zip.enc4, and entered the AP, BL, CP and CSC links in Odin. Failed both times with the same Odin message:
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
On the phone, on the Downloading screen, the error was "SECURE CHECK FAIL : (PIT)"
Googling these messages, the general consensus seems to be that these errors indicate an attempt to flash an incorrect ROM, but I'm running out of options for finding a "correct" one.
Thanks again...
Click to expand...
Click to collapse
Samfirm is a great tool to download firmwares. The pit file sets your partition sizes, you need to flash the correct pit file for that firmware otherwise the firmware will fail to flash.
sofir786 said:
Samfirm is a great tool to download firmwares. The pit file sets your partition sizes, you need to flash the correct pit file for that firmware otherwise the firmware will fail to flash.
Click to expand...
Click to collapse
Now we're getting somewhere ;o) I stayed away from PIT files as they seem to be controversial/risky, but the error message I'm seeing would seem to confirm what you're saying. Question is, how do I locate the correct PIT file AND GET IT RIGHT THE FIRST TIME, as I understand that making a mistake with the PIT file can be disastrous.
Thanks so much...
jp071848 said:
Now we're getting somewhere ;o) I stayed away from PIT files as they seem to be controversial/risky, but the error message I'm seeing would seem to confirm what you're saying. Question is, how do I locate the correct PIT file AND GET IT RIGHT THE FIRST TIME, as I understand that making a mistake with the PIT file can be disastrous.
Thanks so much...
Click to expand...
Click to collapse
I think there is a Thread in the general section which has the collection of pit files, you need to make sure the pit file is bmc.
jp071848 said:
Now we're getting somewhere ;o) I stayed away from PIT files as they seem to be controversial/risky, but the error message I'm seeing would seem to confirm what you're saying. Question is, how do I locate the correct PIT file AND GET IT RIGHT THE FIRST TIME, as I understand that making a mistake with the PIT file can be disastrous.
Thanks so much...
Click to expand...
Click to collapse
UPDATE: I found what I assume is the correct PIT file for the G920W8. Also, on another forum, I found the question:
"Okay, according to that guide Odin is smart enough to know the Pit file is in the CSC file, when the re-partition box is checked? ",
so I may not need the PIT file after all? I had always read that when using Odin, Re-partition was always to be left UNCHECKED, but this says otherwise. What further damage could I possibly do if I re-run Odin with the same AP, BL, CP and CSC files as before, but CHECK re-partition. I guess I can't brick it worse than it already is? Or can I?
jp071848 said:
UPDATE: I found what I assume is the correct PIT file for the G920W8. Also, on another forum, I found the question:
"Okay, according to that guide Odin is smart enough to know the Pit file is in the CSC file, when the re-partition box is checked? ",
so I may not need the PIT file after all? I had always read that when using Odin, Re-partition was always to be left UNCHECKED, but this says otherwise. What further damage could I possibly do if I re-run Odin with the same AP, BL, CP and CSC files as before, but CHECK re-partition. I guess I can't brick it worse than it already is? Or can I?
Click to expand...
Click to collapse
I don't think it could go any worse tbh, try it without the pit file and repartition, you can then try the pit file method if it doesn't work
jp071848 said:
UPDATE: I found what I assume is the correct PIT file for the G920W8. Also, on another forum, I found the question:
"Okay, according to that guide Odin is smart enough to know the Pit file is in the CSC file, when the re-partition box is checked? ",
so I may not need the PIT file after all? I had always read that when using Odin, Re-partition was always to be left UNCHECKED, but this says otherwise. What further damage could I possibly do if I re-run Odin with the same AP, BL, CP and CSC files as before, but CHECK re-partition. I guess I can't brick it worse than it already is? Or can I?
Click to expand...
Click to collapse
Moving right along.... I decided to live dangerously by flashing the BMC ROM, obtained through SamFirm, with Odin, with Re-partition checked. In theory, this would have let Odin know that the contents of the PIT file are already inside the CSC file. Sadly, same result "Re-partition Operation Failed". Interestingly, when I click the PIT tab in Odin the popup says "Do not use this tab... Your device will be changed with the PIT in the CSC file", which doesn't appear to be the case.
jp071848 said:
Moving right along.... I decided to live dangerously by flashing the BMC ROM, obtained through SamFirm, with Odin, with Re-partition checked. In theory, this would have let Odin know that the contents of the PIT file are already inside the CSC file. Sadly, same result "Re-partition Operation Failed". Interestingly, when I click the PIT tab in Odin the popup says "Do not use this tab... Your device will be changed with the PIT in the CSC file", which doesn't appear to be the case.
Click to expand...
Click to collapse
That's just a warning more than anything else
jp071848 said:
Moving right along.... I decided to live dangerously by flashing the BMC ROM, obtained through SamFirm, with Odin, with Re-partition checked. In theory, this would have let Odin know that the contents of the PIT file are already inside the CSC file. Sadly, same result "Re-partition Operation Failed". Interestingly, when I click the PIT tab in Odin the popup says "Do not use this tab... Your device will be changed with the PIT in the CSC file", which doesn't appear to be the case.
Click to expand...
Click to collapse
Tried ODIN and included the PIT file I downloaded. Tried with "Re-Partition" on and off, both times failed exactly the same way "Re-partition" Operation Failed"
jp071848 said:
Tried ODIN and included the PIT file I downloaded. Tried with "Re-Partition" on and off, both times failed exactly the same way "Re-partition" Operation Failed"
Click to expand...
Click to collapse
where did you get the pit file from?
look in settings>security>reactivation lock
if its checked/enabled then uncheck it/disable it
fyi, stay away from repartition pit in odin, only for experienced users w/correct files if any
sofir786 said:
where did you get the pit file from?
Click to expand...
Click to collapse
From this 22 page thread here on XDA
https://forum.xda-developers.com/galaxy-s6/general/g920f-pit-file-banded-firmwares-t3118459
There is a specific reference to a Canadian W8 PIT file
SM-G920W8 OYA multi CSC ( BMC BWA ESK FMC GLW KDO MTA RWC TLS VMC VTR )
ZEROFLTE_CAN_BMC.pit
That's the one I unzipped and loaded into Odin.
Related
Well, this is my first pass at this. I believe this is a valid Odin flashable tar. (First time making one)
Let me know if it works.
Disclaimer:
This ROM is untested and should be considered unsafe until someone is able to flash via one of the two methods below. CWM is not yet available. I know that a couple of people have soft bricked their phones which is why I'm making this available to try out. If you don't heed this warning, be prepared to innocently disavow any knowledge of why you are now holding a paperweight as you try to exchange your bricked device...
YOU HAVE BEEN WARNED!
Features:
-Based on the stock UCKD5 system dump obtained from my Infuse
-Rooted
-Busybox
Instructions:
Odin
This should be an Odin flashable file. Just unzip and grab the tar.
If you don't know how to use Odin, search through the forums, there is more than enough info out there.
OR
Heimdall
unzip SGHI997_UCKD5_rooted.zip
tar xvf SGHI997_UCKD5_rooted.tar
heimdall flash --kernel zImage --factoryfs factoryfs.rfs --modem modem.bin --cache cache.rfs --dbdata dbdata.rfs --param param.lfs
Download:
SGHI997_UCKD5_rooted.zip
Sbl.bin, boot.bin, pit.pit are available in additional.zip
efs.rfs in efs.zip
Donations
I have been a quiet lurker for quite awhile. With this new device, I thought I could really contribute from the onset. A number of people have asked where to send donations... Don't feel obligated but if you really want to...
Trying this soon. You are a god among men if this works for me!
Unkrash said:
Trying this soon. You are a god among men if this works for me!
Click to expand...
Click to collapse
you see bricks have there uses. you are the only one that is willing to test this. if you werent bricked you probably wouldnt!
Just wondering, don't I need a PIT file?
Unkrash said:
Just wondering, don't I need a PIT file?
Click to expand...
Click to collapse
hopefully not. as long as you dont repartition it will run. if you still have a brick then maybe that is the next project for someone.
Latest issue:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> cache.rfs
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Not sure if this is still just me or if it's a problem somewhere else.
Edit-It begins loading the cache (I see green!!) and then fails.
I have the following files as well, but they didn't seem to be necessary for Odin or Heimdall...
However, if someone wants them, I can post.
The files are:
Sbl.bin
boot.bin
pit.pit
Maybe try posting up the .pit?
The additional files are attached to the first post.
im gonna try da_dr8's method to change the startup image in param.ifs
wish i had more confidence that the everything works before hand though
So I put the pit file in and the PDA file and it failed after cache, so now I'm stuck at pc2computer screen. No biggie if a brick, I will just return it. but i've tried a jig with no success(assumed it'd work the same as captivate), and random combos of the 3 button combo. Nothing to get back to download mode yet.
Is this still unproven?
fykick said:
So I put the pit file in and the PDA file and it failed after cache, so now I'm stuck at pc2computer screen. No biggie if a brick, I will just return it. but i've tried a jig with no success(assumed it'd work the same as captivate), and random combos of the 3 button combo. Nothing to get back to download mode yet.
Click to expand...
Click to collapse
I got to download mode by taking the battery out, plugging it in usb, holding both volume buttons, and putting the battery back in. A lot of stuff to do, but it works.
Chika Da China Da Chinese Chicken?
Unkrash said:
I got to download mode by taking the battery out, plugging it in usb, holding both volume buttons, and putting the battery back in. A lot of stuff to do, but it works.
Click to expand...
Click to collapse
Ok last edit I swear.
Maybe you should first try to ODIN the stock kernel instead of a system dump.
http://opensource.samsung.com/
Download the source and it has the kernel in it.
Ok. so....just to confirm. *No one* has done an Odin successfully with this phone, correct?
h8rift said:
Ok. so....just to confirm. *No one* has done an Odin successfully with this phone, correct?
Click to expand...
Click to collapse
i have been trying for three days now with no luck i've bricked mine and i can't get it back
i was able to flash mine using heimdall and the files shown above after nothing but failure the past three days trying every version of odin me and H8rift could find... it vibrates randomly now but is working
Realityfalse said:
i was able to flash mine using heimdall and the files shown above after nothing but failure the past three days trying every version of odin me and H8rift could find... it vibrates randomly now but is working
Click to expand...
Click to collapse
that's good to hear. i wonder what the issue is. there may need to be a version designed for the infuse. i heard odin is built with the phone and that you should only use on version on each phone. adam outler said use v1.7 on the captivate even though everything from v1.0 to v1.82 has worked on my captivate.
yea, we're still troubleshooting the vibrates. But, it looks like my dbdata partition that i posted in that Odin .tar was bad first of all. second of all, heimdall appears a little more forgiving than Odin. we'll have to figure out how to get the Odin package working once the vibrate piece is figured out and remedied.
slappyjoker said:
Ok last edit I swear.
Maybe you should first try to ODIN the stock kernel instead of a system dump.
http://opensource.samsung.com/
Download the source and it has the kernel in it.
Click to expand...
Click to collapse
The kernel is fine in the Odin flash. The problem appears to be dbdata or another .rfs parition. Troubleshooting it so it works with heimdall flawlessly first. then moving to Odin.
Thanks a ton to realityfalse for pretty much all his time this evening and his assistance in getting this figured out thus far .
So I have this problem and I've searched this site for 4 hours and can't get help. It keeps asking me to get the new update but I can't because I'm rooted. I'd be happy with just ignoring it but it asks every day and I can't turn it off.
I can't go back to stock via Odin. I get this error:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<OSM> All threads completed. (succeed 0 / failed 1)
I saw it was a drivers problem. So I've uninstalled and re installed the drivers on 2 different machines. One was never connected to the device until I installed the drivers from Samsung. I've tried deleting the drivers from the computer and disabling windows automatic driver downloads and installing again. Still no luck.
So I gave up and tried to install a custom ROM.
Tried 3 different ROMS and all get E:signature verification failed.
Looked up how to fix this and they want me to reinstall CWM. How do I do that? With Odin.
Are you using the correct PIT file and putting the TAR file in the PDA slot? I know its redundant to ask if you already have CWM on it but I have to ask.... Are you using windows xp/7/8? I am aware of a version 3.0 for ODIN here: http://forum.xda-developers.com/showthread.php?t=1347899&page=1 though I am not %100 sure it will work
Here is a link to the official USB drivers too, no harm in reinstalling: http://www.samsung.com/us/support/owners/product/SGH-T769NKBTMB
dispozable said:
Are you using the correct PIT file and putting the TAR file in the PDA slot? I know its redundant to ask if you already have CWM on it but I have to ask.... Are you using windows xp/7/8? I am aware of a version 3.0 for ODIN here: http://forum.xda-developers.com/showthread.php?t=1347899&page=1 though I am not %100 sure it will work
Here is a link to the official USB drivers too, no harm in reinstalling: http://www.samsung.com/us/support/owners/product/SGH-T769NKBTMB
Click to expand...
Click to collapse
Yes they're in the right spots.
Yup, CWM is installed.
Windows 7
Using the Odin that was suggested by the poster. (k0nane)
Before I could post this, I resolved the issue: Kies was running. :silly:
Are you sure you are in download mode?
I am hoping that someone can help. I am a bit of a mild Panic. See I had this wonderful idea, that I could downgrade my phone back to 4.4.4. So I booted into twrp to do a system reset, and am now unable to boot the phone at all (I think I may have deleted the system by mistake.). It comes up to a firmware update failure. I have searched the forums to find a solution and now feel like I am going around in circles. When I try to use ODIN to reload the original firmware I get the following trace:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N915PVPU1ANJL_N915PSPT1ANJL_N915PVPU1ANJL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
According to the searches I have performed, I need to use Odin to flash the PIT file, but I cannot find were to download a copy of the pit file. I thought that I could extract a copy of the pit file from the ROM, but the tools/steps that are given to extract the img files don't seem to work. Does anyone know of where I can obtain a copy of the PIT file so I can reinstall the 4.4.4 Rom?
You'd have to get aomeone with kitkat to create a pit and send it to you... they have to know how. It really isnt hard at all.. but its the issue of findin someone who is willing to help..
I am installing the Android SDK which gives me a virtual android device. I am hoping I can import the ROM for kitkat ad create the PIT file from that.
Well if anyone has a PIT file for this phone they can email to me, that would be Wonderful. I found a android emulator, but I can't run it because i have a crappy built in video cart that only supports OpenGl 1.1.x and the emulation software won't work without version 2.0. So I am kind of stuck right now.
Ok... this is getting bad
Ok, I guess this should have been posted in the Q & A forum... sorry about that. I am really staring to loose hope.. I have been searching for 2 days to find a pit file for the Note Edge. I find pit files for other note series, but no the note edge, and right now, I can't load any firmware on the device, nada. The partition information has been completely corrupted. I don't know if a pit file for another note series, such as note 3 note 4 would work either. I was hoping I could use a virtual android but I can't seem to find a way to load the rom I want on the virtual android to then extract the pit. Any suggestions, aside from jumping off a cliff (no cliffs around), or taking a large hammer to the phone is welcome.
(At least I still have my humor)
PackRatDragon said:
Ok, I guess this should have been posted in the Q & A forum... sorry about that. I am really staring to loose hope.. I have been searching for 2 days to find a pit file for the Note Edge. I find pit files for other note series, but no the note edge, and right now, I can't load any firmware on the device, nada. The partition information has been completely corrupted. I don't know if a pit file for another note series, such as note 3 note 4 would work either. I was hoping I could use a virtual android but I can't seem to find a way to load the rom I want on the virtual android to then extract the pit. Any suggestions, aside from jumping off a cliff (no cliffs around), or taking a large hammer to the phone is welcome.
(At least I still have my humor)
Click to expand...
Click to collapse
Post in Q and A and hope that some kind soul links you with a .pit file..
Make sure to add the instructions to your posts..
In Terminal Emulator type "su"
Then type in "dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=580 skip=2176"
Then look for the .pit in your SD Card..
Good Luck to you sir. I would have posted it if I had KK.
I mean, it's REALLLLLLY DEAD
So I tried to download the pit file, and that pit file failed. I think that the partition table was so screwed up that the only hope was to rebuild it manually. Since I was getting /data errors when I was in twrp, I figured that I would try to create the file structure manually. I used adb shell to get to a bash (command prompt) and issued a make_ext4fs command. It took the command just fine. Then about 30 seconds later, the system shut down, and that was it. The unit will not turn back on. Period, full stop. I took the phone in to the service center and they could not get it to turn on either. Since it is still under warranty and since I have insurance, they are replacing it.
I doubtful that my make_ext4fs command killed it. when I tried to mount /data I got an error that /dev/block/blah blah was not found, and I used that when I entered the make_ext4fs command. So I think something else was seriously wrong with the device. I hope to get the new phone tomorrow or thursday and with any luck, it will still have 4.4 on it.
Thanks for all those that helped.
The one thing no one said about your attempt to downgrade was that when uou went to lollipop you changed the bootloader. You had to to get it installed. Your attempt to go back to KK was going to fail. Ive not yet seen any attempt to go back successful. Did you try reinstalling lollipop? Or were you only trying to get KK? And with as much as happened with your phone they are actually replacing it? You rooted and bricked your phone. That's amazing
PackRatDragon said:
So I tried to download the pit file, and that pit file failed. I think that the partition table was so screwed up that the only hope was to rebuild it manually. Since I was getting /data errors when I was in twrp, I figured that I would try to create the file structure manually. I used adb shell to get to a bash (command prompt) and issued a make_ext4fs command. It took the command just fine. Then about 30 seconds later, the system shut down, and that was it. The unit will not turn back on. Period, full stop. I took the phone in to the service center and they could not get it to turn on either. Since it is still under warranty and since I have insurance, they are replacing it.
I doubtful that my make_ext4fs command killed it. when I tried to mount /data I got an error that /dev/block/blah blah was not found, and I used that when I entered the make_ext4fs command. So I think something else was seriously wrong with the device. I hope to get the new phone tomorrow or thursday and with any luck, it will still have 4.4 on it.
Thanks for all those that helped.
Click to expand...
Click to collapse
That sucks, thats whats up on the replacement.. Would you kindly post the .pit file when you get a chance... assuming that they leave the device on KK.. i still want to give it another go. I would Appreciate it!!
Sent from my SM-N915P using XDA Free mobile app
Yep mine is dead as well flashed the autoroot and then superuser would boot loop then i flashed a 5.0.1 rom and same thing boot loop I am screwed
joselv456 said:
Yep mine is dead as well flashed the autoroot and then superuser would boot loop then i flashed a 5.0.1 rom and same thing boot loop I am screwed
Click to expand...
Click to collapse
What version of android are you on? Did you make a CWM/TWRP backup??
Now on 5.1.1, and no stupid me did not make a backup before i flashed the SUupdate. I guess lesson learned lol
joselv456 said:
Now on 5.1.1, and no stupid me did not make a backup before i flashed the SUupdate. I guess lesson learned lol
Click to expand...
Click to collapse
https://drive.google.com/open?id=0B6opNIGQWcVYY3dybGN5aGY5dU0
Flash this via ODIN see if it works for you...
z31k said:
https://drive.google.com/open?id=0B6opNIGQWcVYY3dybGN5aGY5dU0
Flash this via ODIN see if it works for you...
Click to expand...
Click to collapse
Okay I am downloading currently will update soon:good:
Sorry if noob question but can odin flash img files??
Nope no luck thanks though
joselv456 said:
Yep mine is dead as well flashed the autoroot and then superuser would boot loop then i flashed a 5.0.1 rom and same thing boot loop I am screwed
Click to expand...
Click to collapse
After flashing 5.01 I would've rebooted into recovery and cleared cache and it would boot then.
http://androiding.how/sprint-note-edge-android-5-1-1-ota-update-rolling-out-build-n915pvpu4cofe/ warnings enclosed
So, back to the original issue. If someone updates to LP, and then wants to flash BACK to a KK firmware, even if they have the appropriate KK PIT file, the flash will fail as the bootloader CANT be downgraded?
Hey guys i am very new to this and have done a lot of research and i'm in need of some help, I tried to put new firmware onto my Samsung S7 but it failed, long story short i can't get it to boot up normally now. I can put it into download mode and then the recovery mode.
In Download mode it says this
Product Name: SM-G930F
Current Binary: Samsung Official
System Status: Custom
FRP Lock: On
Secure Download: Enabled
Warranty Void: 0
In Recovery Mode it says
samsung/heroltexx/herolte
7.0/NRD90M/G930FXXU1DQJ1
No Support SINGLE - SKU
Supported API: 3
dm-Verity error ...
E: Failed to mount /system (Invalid Argument)
I have done this in the past and haven't had any issues with it, but no matter what i do i cant get it to boot up. I've tried the kies and smart switch to put the normal firmware back on but it says this device isn't supported and so it wont load it on. I have tried multiple firmwares from sammobile using AP,BL,CP and i did put in the CSC one also at some stage.
I hope this is enough information if i have missed anything please let me know, hopefully someone has some answers or suggestions. Thanks guys
Make sure you are using ODIN 3.12.3 or newer, older versions don't work properly
First off, Kies no longer supports Galaxy S7, actually never did.
What you can try, use odin (latest version 3.12.7 I think), download your firmware and include all 5 files in odin. You cannot ignore CSC file.
So in order, put BL, AP, CP and CSC and... pit file.
In order to have pit file, you need to make o copy of CSC file, change extension of that copy file to .zip, extract files and inside you will find pit file. Include it in odin in Pit card.
Then flash your phone and report back.
*Detection* said:
Make sure you are using ODIN 3.12.3 or newer, older versions don't work properly
Click to expand...
Click to collapse
Yeah i was using an older version but i downloaded the latest one and still no luck
Cholek3 said:
First off, Kies no longer supports Galaxy S7, actually never did.
What you can try, use odin (latest version 3.12.7 I think), download your firmware and include all 5 files in odin. You cannot ignore CSC file.
So in order, put BL, AP, CP and CSC and... pit file.
In order to have pit file, you need to make o copy of CSC file, change extension of that copy file to .zip, extract files and inside you will find pit file. Include it in odin in Pit card.
Then flash your phone and report back.
Click to expand...
Click to collapse
Have not tried this, will give it a shot and get back to you!
Cholek3 said:
First off, Kies no longer supports Galaxy S7, actually never did.
What you can try, use odin (latest version 3.12.7 I think), download your firmware and include all 5 files in odin. You cannot ignore CSC file.
So in order, put BL, AP, CP and CSC and... pit file.
In order to have pit file, you need to make o copy of CSC file, change extension of that copy file to .zip, extract files and inside you will find pit file. Include it in odin in Pit card.
Then flash your phone and report back.
Click to expand...
Click to collapse
No Luck, i tried what you said and this is what happens
https://imgur.com/a/QQGAn
Re-Partition was automatically ticked, should i try it again and have it un-ticked? or have i totally buggered it?
Try different cable and/or USB port and/or even computer.
Your phone is ok-ish. You only have to manage to flash software and should be up and running.
Cholek3 said:
Try different cable and/or USB port and/or even computer.
Your phone is ok-ish. You only have to manage to flash software and should be up and running.
Click to expand...
Click to collapse
Well im glad its alright haha, ill keep trying different things as you suggested! Hopefully i have some luck. Thank you
Okay bit of an update on what i have attempted - Still no luck at all,
Tried different Odin verisons
Tried multiple firmwares all downloaded from SamMobile & Correct country/carrier etc
The BL,CP and CSC all seem to work fine when i do them by themselves or seperately but i can never get AP to work, it always fails at Sys.img and doesn't go any further.. it always fails about 1/4 of the way through
Tried the PIT partition with and without re-partition clicked
Tried different cables and Ports
anyone have anymore suggestions or is it dead
Did you try using Smart Switch on pc and recover software that way?
Cholek3 said:
Did you try using Smart Switch on pc and recover software that way?
Click to expand...
Click to collapse
Yeah, it says device isn't supported.. when i click on emergency software recovery nothing shows up..
I have run out of options. Sorry.
Cholek3 said:
I have run out of options. Sorry.
Click to expand...
Click to collapse
No worries, ill keep trying and report back if i have any success
will91491 said:
Yeah i was using an older version but i downloaded the latest one and still no luck
Click to expand...
Click to collapse
Phone must be in Download Mode for ODIN
Make sure you have downloaded the correct firmware
It could be the internal memory fault. That's why it stops at 1/4 each time.
*Detection* said:
Phone must be in Download Mode for ODIN
Make sure you have downloaded the correct firmware
Click to expand...
Click to collapse
Yeah i know this much, have done it also
Cholek3 said:
It could be the internal memory fault. That's why it stops at 1/4 each time.
Click to expand...
Click to collapse
Might give it a shot at replacing it, its ****ed either way as far as i can see. I've worked on a lot of iPhone diodes/chips so hopefully i can do this one. Will report back in a few weeks
Tried a different PC?
*Detection* said:
Tried a different PC?
Click to expand...
Click to collapse
Thats what I suggested earlier on, but there seems to be loads of other threads recently, where people's phones fails at loading "system" in odin.
im trying to downgrade my note 8 back to android 8 from the one ui closed beta, ive never been able to use my pc to flash my note 8 even though i have all of the correct drivers, ive reinstalled windows, used usb 2.0 ports i have flashed my phone using other peoples computers successfully but id like to make this work because i was able to flash my galaxy s7 just fine with the latest odin 3.13.1
these are the log files ive gotten
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 6321 M
<ID:0/003> SetupConnection..(it just freezes here)]
or
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 6321 M
<ID:0/004> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)(it doesnt have the red FAIL message though which is weird)
Are you using the Mod version? HERE
Did you do a factory reset before trying to Odin back?
kangi26 said:
Are you using the Mod version? HERE
Did you do a factory reset before trying to Odin back?
Click to expand...
Click to collapse
I've used the modded version and it does the same thing, also I havent done a factory reset before trying to Odin back
I'm having the same issue, I cannot go back to CRK1. I have tried 2 different pc's, multiple versions of Odin. I factory reset my phone, still cannot go back to CRK1.
billdauterive23 said:
I've used the modded version and it does the same thing, also I havent done a factory reset before trying to Odin back
Click to expand...
Click to collapse
Did you get it to work? Same thing for me....
jimi_pooh said:
Did you get it to work? Same thing for me....
Click to expand...
Click to collapse
No, I dont know why it wont work because it worked on my s7 using the exact same version of Odin 3.13.1
I got mine back to CRK1 (sort of). I have an unlocked Note 8 (N950U1), I flashed the T-mobile firmware to my phone several months ago, so that made it an (N950U). I took the update last month from T-mobile (CRK1), then updated to the Pie beta DRL6. Upon trying to go back to the T-mobile firmware CRK1, I could not get it to flash with Odin, however something new happened that I had never seen before. My phone went into download mode, it looked normal, it failed in Odin. I held the volume down button and the power button to reboot the phone but it went into upload mode instead and had "unknown error" at the top of the screen. I held the volume down button and the power button and the phone rebooted and everything was still working as it should on the DRL6. No matter which Odin I tried, I had the same outcome. I finally brought my phone to uBreakiFix, after several attemps by them, they finally got it back to CRK1, with a full factory reset (I had done that already), but it was not the T-mobile firmware, it was the unlocked firmware (N950U1). I know that they attempted the T-mobile version first and it would not boot afterwards, that is when they installed the unlocked firmware.
billdauterive23 said:
No, I dont know why it wont work because it worked on my s7 using the exact same version of Odin 3.13.1
Click to expand...
Click to collapse
I ended up going back to CRJ3 then taking the Ota up to CRK1. Something was wrong with my csc file. Got a real error on another computer. Said Odin could not open the pit for CRK1.
billdauterive23 did u make it work. I am on the same boat as u. Cant downgrade back to crk1
d9700380 said:
billdauterive23 did u make it work. I am on the same boat as u. Cant downgrade back to crk1
Click to expand...
Click to collapse
I still haven't, it's not the biggest issue since my phone still works fine I just can't get updates and I was thinking of flashing my phone to the N950U1 firmware and get updates again and maybe at some point get android 9 if they decide to push the update at a decent time
Are u using windows 7 or windoes 10. I find out Odin doesnt like windows 10. If u have a computer with windows 7 try it
d9700380 said:
Are u using windows 7 or windoes 10. I find out Odin doesnt like windows 10. If u have a computer with windows 7 try it
Click to expand...
Click to collapse
I got rid of windows and switched to Ubuntu, I was already going to and I figured that it might fix my issue but I am still thinking about waiting to test but I think it will fix it as long as I can get it to detect my phone(still setting things up as of now) but I was using Windows 10 before and that very well could have been the problem.