Hello everyone!
This is a guide dedicated to those who are a bit noobish or new to XDA, so if you're not one, I would advise to stop reading now! (although feedback would be great! )
After my success over at the GSII's boards with over 300,000 thread views all over my threads from all sections, I believe that this board should also get some taste of my how to. I'm going to be explaining step by step what to do and how to do it, while explaining each thing.
Just in case you don't know, a soft brick occurs when you flash a ROM or Kernel, and it doesn't go your way, thus bricking the "soft part", aka Software, of your phone. Therefore, it is easy to recover from. Now, if you poorly flash a ROM and it results in a NAND rw corruption (NAND's read and write function corrupted) it means that it is an issue deeper than a soft brick, but still no reason to be alarmed!
When you can flash a kernel, but you can't flash a ROM due to ODIN errors, that happens because it can't properly read the NAND, but it still can flash a kernel. But you ask, why the kernel? Because flashing a kernel is a bit deeper than flashing a ROM. When you flash a kernel, you're changing/putting new instructions to the hardware, and when flashing a ROM, the instructions that are drewn are different and more "simple" (just pulling and pushing folders without touching partitions), so when flashing, ODIN will say "FAIL" instead of "PASS", or suddenly stopping the flash out of nowhere.
__________________________________________________
IF YOU ONLY HAVE A BOOTLOOP
Wipe data/factory reset and wipe cache. IF THAT DOESN'T WORK, MOVE ON WITH THE GUIDE
__________________________________________________
Let's start with the basic files, downloads and requirements
1) You have to know the basics of ODIN and flashing for starters!
2) Just to be safe, please uninstall Samsung KIES. It usually interferes when flashing with ODIN. You must have the USB drivers from your phone, so don't uninstall them. Only uninstall the program KIES.
Just in case you don't have them, here are the Samsung USB drivers
3) Download ODIN v3.07, the tool that we'll use to flash all the things into our loved Galaxy Note 2 N7100!
4) Download the necessary files : the Recovery Package/ROM and the bootloader will be included in the very package. Android 4.1.2, unbranded, XXDLJ2. When you recover the phone, just update it if you want a newer version!
5) You must have WinRAR to unRAR the Recovery Package and to unzip ODIN.
You can also use 7zip if you'd like.
And that is it! Let's get down to business
__________________________________________________
If your GSII has the folowing symptoms :
Bootloop
Stuck on GNII logo, but already removed the battery to try to fix it
Enters Download mode and Recovery mode
It means that you are soft bricked and is easy to solve.
But if your symptoms are the mentioned above, PLUS the symptoms below
Doesn't flash
Bad flash in odin (FAIL after flashing, or the flashing suddenly stops)
Then it means that you have a bigger issue, such as the aforementioned NAND rw corruption.
It's time to open up ODIN and start reviving your phone!
__________________________________________________
First of all, let's just have a quick glance of how ODIN looks like, and where we should put the files :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As the picture clearly shows, the green rectangle is where you can tick. Those 2 which are ticked must remain that way. And the red one is well... Where you SHOULDN'T touch
ONLY FLASH WITH RE-PARTITION TICKED AND A PIT FILE IF YOU ARE SURE
THAT THE FLASH WILL SUCCEED.
Which means that you CANNOT have a damaged USB, corrupted drivers and such.
When recovering from a soft brick, it is recommended, not mandatory, to have Re-partition ticked with a .PIT file. So you must be extra careful when you are using a .PIT and Re-Partition. And obviously, the red box is the one where you can't and don't want to mess with
But where are the files going, you say?
.PIT -> PIT
BOOTLOADER -> BOOTLOADER (or PDA if flashed alone)
CODE -> PDA
MODEM -> PHONE
CSC -> CSC
***If you have a 1 file .tar package, then flash it in PDA***
There is only 1 way to recover a soft bricked phone. How to recover from a NAND corruption? We'll get on that later on
__________________________________________________
Recovering a soft bricked phone
1) Grab the Recovery Package, and you'll see a bunch of .tar files. Take a look at the names. You'll see CODE, MODEM, CSC (and the .PIT). Put each one in its place (EXCEPT the .PIT, refer to the warning below).
2) Turn off your phone. Enter Download mode by presing Volume Down + Home + Power button.
3) Plug in your phone. It will show you, in a blue box in ODIN, ID:COMx (x being the number displayed, sometimes displays 7, sometimes displays 9)
Now here, take a breath
First try flashing WITHOUT the .PIT and re-partition. And only if it DOESN'T WORK OR FIX then you flash with the .PIT and Re-Partition ticked.
4) Once ready and done all your prayers, press Start. Wait patiently. It usually takes 5-10 minutes to flash.
Have you done everything correctly until now? Then...
Congratulations on recovering your phone!
You deserve some cake afterwards, and some rest
Now, if your problem is the NAND rw coruption, and wasn't fixed by the above fix, then follow these steps :
WARNING : FLASHING A BOOTLOADER IS DANGEROUS. FLASH WITH EXTREME CAUTION.
4) Open the zip you downloaded and find the Bootloader. Flash it as PDA or Bootloader in ODIN. Without ticking Re-Partition
5) Flash the recovery package, like in steps 1-4 (WITH the re-partition ticked and the .PIT file in place) and that will fix any of your issues
6) After you have recovered your phone, I advise you to have your phone completely up to date by browsing and downloading the firmware for your version through SamMobile!
I hope that this guide was helpful, and if it was, hit the thanks button!
Credits mainly go to as i9000, for his amazing collection of ROMS and files
_______________________
Disclaimer
This is to be used as educational information. I am not liable of any damage that may occur to your phone.
I was wondering where I can download the recovery package? I can not seem to find a link pointing in any directions. All the help would be great. I know my way round odin an stuff but, this new problem is an new playing field for me
Buckers1313 said:
I was wondering where I can download the recovery package? I can not seem to find a link pointing in any directions. All the help would be great. I know my way round odin an stuff but, this new problem is an new playing field for me
Click to expand...
Click to collapse
Oh man, I derp'd on there! Apparently I didn't include the DL link
Will fix in a moment!
EDIT : Hmmm, the link was there all along, in the code at least... Now that was weird
Good.
This should go into general imao
this is XXXDDDAAA
Phistachio said:
Oh man, I derp'd on there! Apparently I didn't include the DL link
Will fix in a moment!
EDIT : Hmmm, the link was there all along, in the code at least... Now that was weird
Click to expand...
Click to collapse
Thanks for that. Everytime I extract the files, I don't get anything for odin just a heap of img and bin files. Am i extracting them wrong?
Buckers1313 said:
Thanks for that. Everytime I extract the files, I don't get anything for odin just a heap of img and bin files. Am i extracting them wrong?
Click to expand...
Click to collapse
You shouldn't extract them. You must put the .tar file in each box, CODE -> PDA, etc
The file which you extracted must be put in pda tab. The. Tar.md5 file. You must not extract that.
this is XXXDDDAAA
Phistachio said:
You shouldn't extract them. You must put the .tar file in each box, CODE -> PDA, etc
Click to expand...
Click to collapse
Thanks for your help. my device isnt flashing anything
just hangs at setupconnect and then fails for different reasons. might try my chances with a warranty :S
Buckers1313 said:
Thanks for your help. my device isnt flashing anything
just hangs at setupconnect and then fails for different reasons. might try my chances with a warranty :S
Click to expand...
Click to collapse
Tell me exactly what you're doing, step by step.
Phistachio said:
Tell me exactly what you're doing, step by step.
Click to expand...
Click to collapse
downloaded the zip
unzipped (all correct tar files where there and the pit)
Opened odin and placed each tar and pit file in the correct place.
Phone placed in download mode (the phone is showing in odin as connected)
Pressed start (tried with pit and no pit)
Put simply the phone isn't receiving anything. Usually when I flash with odin the phone and software do there thing. Download mode isn't even showing any signs of being connected. Setupconnection hangs there for a while and then it fails and sometimes it says pit file mapping (or something) and then fails after 10 mins of hanging there.
I have even tried flashing the bootloader by itself and that doesn't work either.
Cheers for all your help to.
Buckers1313 said:
downloaded the zip
unzipped (all correct tar files where there and the pit)
Opened odin and placed each tar and pit file in the correct place.
Phone placed in download mode (the phone is showing in odin as connected)
Pressed start (tried with pit and no pit)
Put simply the phone isn't receiving anything. Usually when I flash with odin the phone and software do there thing. Download mode isn't even showing any signs of being connected. Setupconnection hangs there for a while and then it fails and sometimes it says pit file mapping (or something) and then fails after 10 mins of hanging there.
I have even tried flashing the bootloader by itself and that doesn't work either.
Cheers for all your help to.
Click to expand...
Click to collapse
Try a different USB cable or a different USB port
Phistachio said:
Try a different USB cable or a different USB port
Click to expand...
Click to collapse
Cheers. I have tried different cables, USBs and even computers. I have tried with or without drivers and all the steps you have suggested.
I find it weird that it boots into download mode but just doesn't download. I'm wondering if something else may have stuffed itself?
Buckers1313 said:
Cheers. I have tried different cables, USBs and even computers. I have tried with or without drivers and all the steps you have suggested.
I find it weird that it boots into download mode but just doesn't download. I'm wondering if something else may have stuffed itself?
Click to expand...
Click to collapse
Usually when it's stuck at setupconnection it means that it can't connect to the NAND, more specifically, to r/w to the bootloader. Have you tried flashing JUST the bootloader?
Phistachio said:
Usually when it's stuck at setupconnection it means that it can't connect to the NAND, more specifically, to r/w to the bootloader. Have you tried flashing JUST the bootloader?
Click to expand...
Click to collapse
Yeah same thing happens. First time around it asks for the pit file though. I have tried flashing it as a bootloader and PDA file, but it still just hangs there.
Buckers1313 said:
Yeah same thing happens. First time around it asks for the pit file though. I have tried flashing it as a bootloader and PDA file, but it still just hangs there.
Click to expand...
Click to collapse
Hmm, that's odd You're using ODIN v3 correct?
It's SDS nothing to do, send back to Samsung service; it means motherboard replacing
almaalma74 said:
It's SDS nothing to do, send back to Samsung service; it means motherboard replacing
Click to expand...
Click to collapse
If it was SDS, would the phone be able to boot into download mode?
Phistachio said:
If it was SDS, would the phone be able to boot into download mode?
Click to expand...
Click to collapse
Yeah, it's called as "half" SDS, it is sad but true... My phone had same issues
almaalma74 said:
Yeah, it's called as "half" SDS, it is sad but true... My phone had same issues
Click to expand...
Click to collapse
Will Samsung know that I have put customer roms on it?
Fail to show as connected
I'm trying to flash out of CWM into TWRP but nether the Toolkit nor Odin shows my device as being connected in debug mode or download mode. What's the way ahead on this? I'm just trying to get another boot loader because I've been having issues with CWM failing on ROM installs from zip files. The only ROM I've been able to install is PAC.
Related
Hi!
I have an HSPA+ Galaxy Nexus. It was stuck at the what I believe is called the "Fastboot" screen. It had a yellow warning triangle on it. After trying to flash it with Odin, the screen stopped powering on. Right after I clicked Start in Odin, the graphics on screen started looking weird(Ghosting and weird color lines), so I unplugged it.
Now, when I plug it in, in the Device Manager, a new device called, "OMAP4440" pops up for few seconds, then disappears. Screen shot attached.
Is there anyway to get this back to working order?
OK, I used the program and the link below, and it's back in it's previous state. Now it's stuck on a yellow triangle screen. I can't get it into download or recovery mode.
http://forum.gsmhosting.com/vbb/f63...b-prime-via-usb-cable-freeeeeeeeeeee-1465412/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried to flash it with Odin, but it stays at, "Nand Write Start".
Ok, I finally managed to get it into fastboot and download mode. When I try to flash with Odin, it stops at a write error. When I use the Toolkit v7, it doesn't get past the "writing bootloader".
In fastboot, it says, "NO BOOT OR RECOVERY IMG".
You can get into Fastboot? (open bugdroid w/ volume keys toggling reboot and recovery)
From here, just download the Stock Google Images hosted at their site: (this is the Play Store Variant, use Yakju for international model)
https://developers.google.com/android/nexus/images#takju
and use the fastboot command to update them. They include bootloaders and recovery images. Flash the bootloader FIRST!!! [fastboot flash bootloader]
jj00KKEERR said:
Ok, I finally managed to get it into fastboot and download mode. When I try to flash with Odin, it stops at a write error. When I use the Toolkit v7, it doesn't get past the "writing bootloader".
In fastboot, it says, "NO BOOT OR RECOVERY IMG".
Click to expand...
Click to collapse
Did you install the drivers properly with the toolkit?
With your phone in fastboot mode type"fastboot devices" into command prompt on your computer, if you see a serial number come up then your drivers are working and you should be able to flash.
Try flashing stuff manually via fastboot, tool kits are convenient but its better to do it manually.
There is a guide available I'll find you the link.
Edit: http://forum.xda-developers.com/showpost.php?p=25477039&postcount=1
All credit for this guide goes to efrant
nodstuff said:
Did you install the drivers properly with the toolkit?
With your phone in fastboot mode type"fastboot devices" into command prompt on your computer, if you see a serial number come up then your drivers are working and you should be able to flash.
Try flashing stuff manually via fastboot, tool kits are convenient but its better to do it manually.
There is a guide available I'll find you the link.
Edit: http://forum.xda-developers.com/showpost.php?p=25477039&postcount=1
All credit for this guide goes to efrant
Click to expand...
Click to collapse
+1
Forget the Toolkit, ADB is buggy enough as it is. Fastboot it using good old command prompt.
Lucky for you, your phone can at least turn on. My phone just died and cannot be turned back on for any reason. It's so sad. I just rebooted it. Placed it into my pocket, took it out, and found out it never came back on. Charging it does no good, I've tried all methods there is to think of. It's Dead as can be.
Thanks for the suggestions guys! I set up abd, but every time I try to flash a file it says, "Unknown Partition".
eg, fastboot flash bootloader bootloader.img
lemonspeakers said:
Lucky for you, your phone can at least turn on. My phone just died and cannot be turned back on for any reason. It's so sad. I just rebooted it. Placed it into my pocket, took it out, and found out it never came back on. Charging it does no good, I've tried all methods there is to think of. It's Dead as can be.
Click to expand...
Click to collapse
If it's still recognized by you computer, try:
http://forum.gsmhosting.com/vbb/f63...b-prime-via-usb-cable-freeeeeeeeeeee-1465412/
Mine was completely dead, but it was recognized by the computer.
That's weird...
Try ODIN with a PIT file, that should map all partitions for the phone and the PDA file.
dnlsmy said:
That's weird...
Try ODIN with a PIT file, that should map all partitions for the phone and the PDA file.
Click to expand...
Click to collapse
It fails.
jj00KKEERR said:
If it's still recognized by you computer, try:
http://forum.gsmhosting.com/vbb/f63...b-prime-via-usb-cable-freeeeeeeeeeee-1465412/
Mine was completely dead, but it was recognized by the computer.
Click to expand...
Click to collapse
Nope, Unfortunaetly, It's dead as can be. It can't even turn on. Display is dead, and no vibration to indicate it came on =(
Quite sad how it just died.
jj00KKEERR said:
It fails.
Click to expand...
Click to collapse
Where did you get the pit file from? Are you sure it's the correct one?
I had the attached one on my PC. I can't remember where I got it from, but maybe you could give that one a try. Note: I have never used it myself.
efrant said:
Where did you get the pit file from? Are you sure it's the correct one?
I had the attached one on my PC. I can't remember where I got it from, but maybe you could give that one a try. Note: I have never used it myself.
Click to expand...
Click to collapse
I used a 512 pit from a Samsung Vibrant. I'm trying yours now.
EDIT: It didn't fail, it just doesn't seem to be moving. It's stuck at "NAND Write Start!!"
You HAVE TO use both the phone file AND the pda file.....if you don't have BOTH it won't work.
I have them for cdma but not gsm....sorry.
Search some
n2ishun said:
You HAVE TO use both the phone file AND the pda file.....if you don't have BOTH it won't work.
I have them for cdma but not gsm....sorry.
Search some
Click to expand...
Click to collapse
I haven't seen a phone file before, only PDA. I've checked most, if not all the guides.
jj00KKEERR said:
I haven't seen a phone file before, only PDA. I've checked most, if not all the guides.
Click to expand...
Click to collapse
Try it like this:
1) Download this and extract it.
2) In Odin, make sure the following are checked: Re-Partition, Auto Reboot, F.Reset Time.
3) Use the pit file I uploaded for the PIT.
4) Use CODE_I9250xxxxx_user_ITL41F_163581.tar.md5 for the PDA
5) Use MODEM_I9250xxxxx_REV_00_CL1075373.tar.md5 for the PHONE
6) Use GT-I9250-CSC-MULTI-....tar.md5 for the CSC
7) Reboot into Download mode and plug into your computer.
8) Click Start
Source: http://allphonefirmwares.blogspot.ca/2012/03/how-to-update-firmware-of-samsung-i9250.html
efrant said:
Try it like this:
1) Download this and extract it.
2) In Odin, make sure the following are checked: Re-Partition, Auto Reboot, F.Reset Time.
3) Use the pit file I uploaded for the PIT.
4) Use CODE_I9250xxxxx_user_ITL41F_163581.tar.md5 for the PDA
5) Use MODEM_I9250xxxxx_REV_00_CL1075373.tar.md5 for the PHONE
6) Use GT-I9250-CSC-MULTI-....tar.md5 for the CSC
7) Reboot into Download mode and plug into your computer.
8) Click Start
Source: http://allphonefirmwares.blogspot.ca/2012/03/how-to-update-firmware-of-samsung-i9250.html
Click to expand...
Click to collapse
Where do I find the PHONE and CSC files? They aren't in the download.
jj00KKEERR said:
Where do I find the PHONE and CSC files? They aren't in the download.
Click to expand...
Click to collapse
If they weren't the download, don't worry about them. Just use the pit and pda.
efrant said:
If they weren't the download, don't worry about them. Just use the pit and pda.
Click to expand...
Click to collapse
Thanks! It still gets stuck at Writing NAND. Maybe it has bad NAND?
Sent from my SGH-T769 using Tapatalk 2
Same problem
HELLO DUDE!!
ive have the same problem here, one question, how did u took the nexus out of the yellow warning triangle error?
i would love to have it back to the recovery mode :/
This is my first thread as a user, I have been a lurker for very long time. I have decent understanding of flashing roms on HTC one X and HP touchpad, everything learned from XDA. But I have been facing this weird issue on Unlocked Rogers Galaxy note 2.
My galaxy note 2 was all stock and few days ago when I picked it up while it was charging, phone was hanging on main screen. I simply turned off and since then its stuck in bootloop. I am only getting samsung logo screen. So far everything I have tried, it hasnt resolved the issue.
I have flashed rogers stock 4.1.2 rom from samsung-updates using ODIN, but still its stuck in bootloop. I have tried multiple recoveries Stock, Clockwork and TWRP, phone mostly reboots when I try to do a factory reset. even when I am able to complete factory reset, nothing changes. All recoveries give me errors in line of unable to mount /cache and unable to mount /data.
Right now I have flashed TWRP and it shows unable to mount /cache, and it reboots when I try to do a factory reset.
These are the exact errors
E: unable to mount "cache"
E: can't mount '/cache/recovery/command'
E: can't open '/cache/recovery/command'
E: can't mount '/cache/recovery/log'
E: can't open '/cache/recovery/log'
E: can't mount '/cache/recovery/last_log'
E: can't open '/cache/recovery/last_log'
E: can't mount '/cache/recover/last_install'
E: can't open '/cache/recover/last_install'
Please help.
If nothing else works, can anyone show me a way to hard brick? So I can send in for warranty, coz download mode shows the binary counter?
Thanks
Hi, sounds like you either have a corrupted partition on your phone or a hardware issue. I have had lots of bootloops in the past and was always been able to fix it with flashing stock software with odin. You probily going to send it in for warranrt repair.
Sent from my SGH-I317M using XDA Premium HD app
pterry30 said:
Hi, sounds like you either have a corrupted partition on your phone or a hardware issue. I have had lots of bootloops in the past and was always been able to fix it with flashing stock software with odin. You probily going to send it in for warranrt repair.
Sent from my SGH-I317M using XDA Premium HD app
Click to expand...
Click to collapse
Is there any fix for corrupted partition on note 2? I have seen threads regarding s3 but not note2.
Also if I flash Mr robinsons rom from here
http://forum.xda-developers.com/showthread.php?t=2004650
it should reset the flash counter to 0, So I can send it in for repair.
I believe to fix a bad partition you need the pit file. I think it is in the stock firmware. I have never had a issue where I could not do a factory wipe/reset. You need triangle away app from the play to reset counter. You need to be on stock software, stock recovery, stock kernel but be rooted to use triangle away
Sent from my SGH-I747 using XDA Premium HD app
---------- Post added at 08:20 AM ---------- Previous post was at 08:16 AM ----------
Your issue is most likely hardware related because you were on stock software when you started having problems and you had not flashed any others software and you flashed stock software through odin and did not fix your problems
Sent from my SGH-I747 using XDA Premium HD app
I'd say try flashing a new kernel, and doing a factory reset
Edit...I re read op, and I think pit file also...
Sent from my SGH-I317M using xda premium
If that doesn't work I would definitely try flashing the pit file with the stock firmware in Odin.
Sent from my GT-N7105 using Tapatalk 2
cdshepherd said:
If that doesn't work I would definitely try flashing the pit file with the stock firmware in Odin.
Sent from my GT-N7105 using Tapatalk 2
Click to expand...
Click to collapse
sorry for the late reply, had to leave country for few weeks. So I tried to flash stock rom (redownloaded 4.1.1 from samfirmware) again through ODIN, and its still stuck in bootloop. when I boot into stock recovery after flashing stock rom, I get "E:failed to verify whole file signature, E:signature verification failed."
Format sd card then install latest stock rom with pit file ..it wil help u
nabilsweet007 said:
Format sd card then install latest stock rom with pit file ..it wil help u
Click to expand...
Click to collapse
I havent been able to find the pit file for note 2 i317m at all. If you have links, please share.
Anyone?
prince_f_swords said:
I havent been able to find the pit file for note 2 i317m at all. If you have links, please share.
Click to expand...
Click to collapse
Bump, anyone with pit file or a way to repartition?
Pm for pit
Thanks for the pit file, but Odin gets stuck at "Get pit file for mapping". Any ideas?
Are you putting it in the pit slot in odin?
twanskys204 said:
Are you putting it in the pit slot in odin?
Click to expand...
Click to collapse
yes, here's a screenshot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I know you are having bootloop issues and im not an expert by any means. However, should repartition be checked? I know typically under odin you never want that box checked but maybe in this instance you do.
Sent from my SAMSUNG-SGH-I317 using XDA Premium HD app
cloudraker said:
I know you are having bootloop issues and im not an expert by any means. However, should repartition be checked? I know typically under odin you never want that box checked but maybe in this instance you do.
Sent from my SAMSUNG-SGH-I317 using XDA Premium HD app
Click to expand...
Click to collapse
well I am trying to repartition it by using pit file, as I think the errors in CWM are indicating that partition is messed up.
Ok so you have boot loops check it out,
here is list of what to grab odin version here
http://forum.xda-developers.com/showpost.php?p=33854395&postcount=2
follow those direction just insert your stock instead of cf auto root tar md5
- Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Unzip the attached Odin3-vX.X.zip file
- Download and unzip the CF-Auto-Root-....zip file (see posts below this one)
- If you end up with a recovery.img and cache.img file, you've extracted twice. You need to end up with a .tar.md5 file - don't extract that one
- (USB) Disconnect your phone from your computer
- Start Odin3-vX.X.exe
- Click the PDA button, and select CF-Auto-Root-....tar.md5
- Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue, press the listed button, or run adb reboot download command)
- (USB) Connect the phone to your computer
- Make sure Repartition is NOT checked
- Click the Start button
- Wait for Android to boot
- Done
go to next post and grab cf auto root for i317m, IF your going to attempt to reboot
grab zip fro stock build http://www.hotfile.com/dl/180165074/47da708/I317MVLALJ2_I317MOYAALJ2_RWC.zip.html
and un zip with 7zip
place in odin pda slot as the directions from chainfire's post, remove sd if installed and continue.
when finished let reboot and it will hang on boot ani. pull battery, go into stock recovery and format cache and factory reset, then reboot.
you should be good to go at that point. if not pm me.
riassan said:
Ok so you have boot loops check it out,
here is list of what to grab odin version here
http://forum.xda-developers.com/showpost.php?p=33854395&postcount=2
follow those direction just insert your stock instead of cf auto root tar md5
- Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Unzip the attached Odin3-vX.X.zip file
- Download and unzip the CF-Auto-Root-....zip file (see posts below this one)
- If you end up with a recovery.img and cache.img file, you've extracted twice. You need to end up with a .tar.md5 file - don't extract that one
- (USB) Disconnect your phone from your computer
- Start Odin3-vX.X.exe
- Click the PDA button, and select CF-Auto-Root-....tar.md5
- Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue, press the listed button, or run adb reboot download command)
- (USB) Connect the phone to your computer
- Make sure Repartition is NOT checked
- Click the Start button
- Wait for Android to boot
- Done
go to next post and grab cf auto root for i317m, IF your going to attempt to reboot
grab zip fro stock build http://www.hotfile.com/dl/180165074/47da708/I317MVLALJ2_I317MOYAALJ2_RWC.zip.html
and un zip with 7zip
place in odin pda slot as the directions from chainfire's post, remove sd if installed and continue.
when finished let reboot and it will hang on boot ani. pull battery, go into stock recovery and format cache and factory reset, then reboot.
you should be good to go at that point. if not pm me.
Click to expand...
Click to collapse
Here's what I did, downloaded stock rom I317MVLALJ2_I317MOYAALJ2_RWC
downloaded ODIN 1.85 from chainfire's post
put stock rom into PDA tab, reset time and auto reboot checked
- start flash, it Passed.
then downloaded CF auto root for I317M
- put the phone in download mode again
- put CF auto root to PDA tab, reset time and auto reboot checked
- it passed too
now I cannot get to recovery
- battery out Volume UP+power +Home
- "samsung galxy note II" logo keeps coming back
one thing I remember from before when device was on complete stock, it use to show "Samsung" logo in Bold not "Samsung Galaxy Note II"
any ideas?
prince_f_swords said:
Here's what I did, downloaded stock rom I317MVLALJ2_I317MOYAALJ2_RWC
downloaded ODIN 1.85 from chainfire's post
put stock rom into PDA tab, reset time and auto reboot checked
- start flash, it Passed.
then downloaded CF auto root for I317M
- put the phone in download mode again
- put CF auto root to PDA tab, reset time and auto reboot checked
- it passed too
now I cannot get to recovery
- battery out Volume UP+power +Home
- "samsung galxy note II" logo keeps coming back
one thing I remember from before when device was on complete stock, it use to show "Samsung" logo in Bold not "Samsung Galaxy Note II"
any ideas?
Click to expand...
Click to collapse
Anyone............
Make sure its volume up home then power
As a general FYI, if you think you need to repartition your phone it is also possible that your phone has experienced:
a) A hardware issue, possibly partial or total emmc failure.
b) A mismatch between bootloader (sboot.bin) and trustzone (tz.img) versions. See this post or my MK6 stock thread for some possible options to fix this.
As a step of last resort to recreate the partition table on your phone, a pit file may be what you need. This can be done in either Odin or Heimdall.
Warning - repartitioning your phone may erase all data and might cause other unintended consequences. You assume all risk.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
To use a pit file in Odin, this is typically done as part of a flashing a stock rom package, like the LJ2 or MA4 package for the i317 (or similar package for the i317m). You specify the pit file in the PIT section, make sure the repartition box is checked, and then add the rom package in the PDA section like usual.
If you are running an official 4.3 or later bootloader you will not be able to successfully flash a stock firmware package that contains earlier bootloaders - Odin will hang and you will need to find a different stock package to flash that does not contain a bootloader. (i.e. If you took the the i317 4.3 OTA and are running the MK6 bootloader or a later bootloader, you'll want to avoid UCAMA4)
The attached zip includes pit files for both the i317 and the i317m. The partition mapping is the same for both (see the included analysis files), but the pit files have unique security signatures which are accepted only by the bootloader of the specific model phone for which they are intended. I've tested the file for the i317 and can confirm that it works as intended. The file for the i317m was pulled the same way by an XDA member (thanks @plemen !) with an i317m and I've confirmed it is formatted correctly. It has now been confirmed as working.
If you want to learn a bit more about pit files, check out this thread by Adam Outler:
http://forum.xda-developers.com/showthread.php?t=2540480
Very interested in this, as I need the pit file for my I317. Question about the bootloader, though.... I've never taken an OTA, just flashing CM and OmniROM nightlies (was on 4.4.2 when my phone committed suicide). Should I be safe to use this pit file? And what factory firmware would you recommend to go with it?
pit files should be back in a day or two (I'll be testing over the weekend).
Depending on what happened to your phone it's still highly probable that your pit (partition) data is fine. There's a way to confirm this using Heimdall - when time permits I'll add instructions to post #2. That's a safer first step than attempting a repartition.
As for bootloader and firmware - if you've never taken an OTA, and you're not on a 4.3 bootloader your best bet for stock firmware is UCAMA4. It's a more complete and somewhat newer package than the other option (UCALJ2). You can get this from sammobile, or a mirror copy I have linked in post #2 here:
http://forum.xda-developers.com/showthread.php?t=2589891
that post also has information on a couple apps you can load that will allow you to check which bootloader you have loaded once your phone is operational.
Thanks for doing this! Did you have any luck over the weekend? Looking to re-partition as I'm unable to mount.
anine said:
Thanks for doing this! Did you have any luck over the weekend? Looking to re-partition as I'm unable to mount.
Click to expand...
Click to collapse
I expected a test phone on Saturday that didn't arrive until Tuesday thanks to the USPS getting the day off on Monday. Once I confirm the files work as intended I will repost them.
As for the issue you are having - what partition isn't mounting? Can you provide more detail?
Zen Arcade said:
I expected a test phone on Saturday that didn't arrive until Tuesday thanks to the USPS getting the day off on Monday. Once I confirm the files work as intended I will repost them.
As for the issue you are having - what partition isn't mounting? Can you provide more detail?
Click to expand...
Click to collapse
The Note 2 (ATT) suddenly rebooted and stuck on the "Samsung Galaxy Note 2" screen. A couple reboots and a battery pull did not solve the issue. I even let the phone stay on the screen in the event it needed to do some sort of repair.. but after an hour, nothing changed.
I loaded CWM recovery and got recovery mount errors. Also, I am unable to mount any of the internal file system when attempting from the advanced menu. After a couple of hours of following tutorials I went into download mode and installed the stock ATT rom. It was successful but still did not boot (attempted this twice). I came upon a few suggestions for similar issues that said the PIT file was needed to repartition. I used Beanstalk 4.4.2 before the crash.
Help
anine said:
The Note 2 (ATT) suddenly rebooted and stuck on the "Samsung Galaxy Note 2" screen. A couple reboots and a battery pull did not solve the issue. I even let the phone stay on the screen in the event it needed to do some sort of repair.. but after an hour, nothing changed.
I loaded CWM recovery and got recovery mount errors. Also, I am unable to mount any of the internal file system when attempting from the advanced menu. After a couple of hours of following tutorials I went into download mode and installed the stock ATT rom. It was successful but still did not boot (attempted this twice). I came upon a few suggestions for similar issues that said the PIT file was needed to repartition. I used Beanstalk 4.4.2 before the crash.
Click to expand...
Click to collapse
I desperately need this PIT file as well.. not on 4.3 however..I can get to download mode and into recovery but it spits a bunch of errors about unable to mount /cache etc...
anine said:
The Note 2 (ATT) suddenly rebooted and stuck on the "Samsung Galaxy Note 2" screen. A couple reboots and a battery pull did not solve the issue. I even let the phone stay on the screen in the event it needed to do some sort of repair.. but after an hour, nothing changed.
I loaded CWM recovery and got recovery mount errors. Also, I am unable to mount any of the internal file system when attempting from the advanced menu. After a couple of hours of following tutorials I went into download mode and installed the stock ATT rom. It was successful but still did not boot (attempted this twice). I came upon a few suggestions for similar issues that said the PIT file was needed to repartition. I used Beanstalk 4.4.2 before the crash.
Click to expand...
Click to collapse
The symptoms you describe are similar to those I've seen on the Q&A forum recently. I don't want to be the bearer of bad tidings, but I suspect you have a partial emmc (hardware) failure.
My time during the week is limited so I expect to have testing done this weekend.
terpencar said:
I desperately need this PIT file as well.. not on 4.3 however..I can get to download mode and into recovery but it spits a bunch of errors about unable to mount /cache etc...
Click to expand...
Click to collapse
I had similar issue, and was able to resolve it by following this thread. YOu need to restore factory original by following this thread from XDA.
Please don't forget to Thank
The files provided are only for phone I317 and not I317M
http://www.androidfilehost.com/?fid=23060877490003986
Instructions:
1. Download "back to stock" zip folder I uploaded. It contains all the files needed. No need to search around.
2. Unzip the file and extract the folder to your desktop.
3. Open folder and install Samsung drivers if not already done so.
4. Now make sure you have root and custom recovery on the phone. Turn the phone off. Hold volume up, home and power button at the same time.Wait till u see custom recovery screen and then let go off all the buttons.
5. Once in recovery... delete data, system, cache, dev cache like you want to flash a new rom. Turn the phone off by pulling the battery or see option for power off device under custom recovery.
6. Once the phone is completely off lets get into download mode. Hold volume down, home and power button until you see the screen with an option to press volume up to get into download. Press volume up to enter download mode when asked.
7. Now open odin3.07 I provided in the folder u downloaded. Once open connect your phone via usb. Windows should install device drivers. Once thats done, you should see com## on the Odin software.
8. On odin software you should see button called PDA. Click on it and browse to the file called KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user _low_ship.tar. in the folder provided by me. select it and hit ok. Odin will process the file. It will take max 2 to 3 min.
9. Before you click start on Odin make sure auto reboot and F. reset time is checked only. Everything else unchecked. Click start button. Odin will start flashing the factory firmware. It will take time.
10. Once Odin is done flashing. phone will reboot. Now you can disconnect the usb cable. When phone is fully rebooted, skip all the prompt and get to home screen.
11. Turn the phone off again and get into download mode. Connect usb cable to computer with Odin open. Click Pda and select file called CF-Auto-Root-t0lteatt-t0lteatt-samsungsghi317.tar. Let Odin process it and then click start. Once flashing the root file is done. Phone should reboot to home screen. Now you have root. The reason we need root is to get rid of counter # in download more. It should say zero.
12. Connect your phone to computer while on the home screen. Open phone internal storage and go to download folder and copy Triangle away.apk into it.
13. Go into settings and security and check unknown sources.
14. Go to apps and open application "my file". Go to download folder and select triangle away application to install. install it. Open application application and scroll down and select reset counter option. Make sure your are connected to wifi. Confirm you phone is I317 and triangle away will download the file. Your phone should reboot into some type of reset counter recovery screen. follow the instruction on the screen to reset the counter. After that phone should reboot.
15. Once rebooted uninstall triangle away apk. Now open super user application and scrool down and click fully unroot. When done go into stock recovery and clear data and cache. reboot phone. All done. Your counter is set to zero. Your phone should read normal under settings.
You can update your phone under settings from att servers.
Enjoy.
Thanks to chainfire for his triangle away app and root for our device.
rob_z11 said:
I had similar issue, and was able to resolve it by following this thread. YOu need to restore factory original by following this thread from XDA.
Please don't forget to Thank
The files provided are only for phone I317 and not I317M
Instructions:
1. Download "back to stock" zip folder I uploaded. It contains all the files needed. No need to search around.
2. Unzip the file and extract the folder to your desktop.
3. Open folder and install Samsung drivers if not already done so.
4. Now make sure you have root and custom recovery on the phone. Turn the phone off. Hold volume up, home and power button at the same time.Wait till u see custom recovery screen and then let go off all the buttons.
5. Once in recovery... delete data, system, cache, dev cache like you want to flash a new rom. Turn the phone off by pulling the battery or see option for power off device under custom recovery.
6. Once the phone is completely off lets get into download mode. Hold volume down, home and power button until you see the screen with an option to press volume up to get into download. Press volume up to enter download mode when asked.
7. Now open odin3.07 I provided in the folder u downloaded. Once open connect your phone via usb. Windows should install device drivers. Once thats done, you should see com## on the Odin software.
8. On odin software you should see button called PDA. Click on it and browse to the file called KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user _low_ship.tar. in the folder provided by me. select it and hit ok. Odin will process the file. It will take max 2 to 3 min.
9. Before you click start on Odin make sure auto reboot and F. reset time is checked only. Everything else unchecked. Click start button. Odin will start flashing the factory firmware. It will take time.
10. Once Odin is done flashing. phone will reboot. Now you can disconnect the usb cable. When phone is fully rebooted, skip all the prompt and get to home screen.
11. Turn the phone off again and get into download mode. Connect usb cable to computer with Odin open. Click Pda and select file called CF-Auto-Root-t0lteatt-t0lteatt-samsungsghi317.tar. Let Odin process it and then click start. Once flashing the root file is done. Phone should reboot to home screen. Now you have root. The reason we need root is to get rid of counter # in download more. It should say zero.
12. Connect your phone to computer while on the home screen. Open phone internal storage and go to download folder and copy Triangle away.apk into it.
13. Go into settings and security and check unknown sources.
14. Go to apps and open application "my file". Go to download folder and select triangle away application to install. install it. Open application application and scroll down and select reset counter option. Make sure your are connected to wifi. Confirm you phone is I317 and triangle away will download the file. Your phone should reboot into some type of reset counter recovery screen. follow the instruction on the screen to reset the counter. After that phone should reboot.
15. Once rebooted uninstall triangle away apk. Now open super user application and scrool down and click fully unroot. When done go into stock recovery and clear data and cache. reboot phone. All done. Your counter is set to zero. Your phone should read normal under settings.
You can update your phone under settings from att servers.
Enjoy.
Thanks to chainfire for his triangle away app and root for our device.
Click to expand...
Click to collapse
Thanks.. It just hangs at system.img in odin
Nice job Zen
Sent from my SGH-I317 using XDA Premium 4 mobile app
Pit files are back up and attached to the OP. The i317 pit file is tested and confirmed working.
The i317m file is identical, except for the security signature. I'm currently looking for someone with a healthy i317m willing to test flash the i317m pit file to confirm it works. (I would do this myself, but I don't have an i317m).
Unfortunately it did not work for me. emmc failure suspected. Strange thing is that in ODIN I can still "Successfully" install a ROM.. and even the PIT file succeeded. I still got a logo screen for several minutes.
Fortunately for me, I have an additional mainboard from a otherwise damaged note 2. I'll be swapping that out.
Thank you anyway. Hope your file helps others!
My phone was not booting and stopped at Samsung logo. After the pit file and stock rom, my phone is live again. I am still having issue with storage but at least I have good starting point.
thanks
Works fine on i317m
anine said:
Unfortunately it did not work for me. emmc failure suspected. Strange thing is that in ODIN I can still "Successfully" install a ROM.. and even the PIT file succeeded. I still got a logo screen for several minutes.
Fortunately for me, I have an additional mainboard from a otherwise damaged note 2. I'll be swapping that out.
Thank you anyway. Hope your file helps others!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2626593
qkster said:
http://forum.xda-developers.com/showthread.php?t=2626593
Click to expand...
Click to collapse
See posts #9 and #13 on the thread above for the specific potential solution to try.
Corrupt pit file it says. for note 2 att help
I have a Att note 2 i flash the mj9 firmware using mobile odin first. Then i formatted storage, data, system, and cache. And now its says i have NO ios Installed with is true but when i try flashing another rom in TWRP it fails iv'e try stock ATT, Jedi Rom, MeanBean Rom. now i tryed to flash stock firmware through J Odin but it always say corrupt pit file...Someone Please Help MEE
kumar_420 said:
I have a Att note 2 i flash the mj9 firmware using mobile odin first. Then i formatted storage, data, system, and cache. And now its says i have NO ios Installed with is true but when i try flashing another rom in TWRP it fails iv'e try stock ATT, Jedi Rom, MeanBean Rom. now i tryed to flash stock firmware through J Odin but it always say corrupt pit file...Someone Please Help MEE
Click to expand...
Click to collapse
Err mj9 is verizon haha
Sent from my lightning fast Note II running MeanBean 2.0 SuperCharged
The phone does not boot - just shows "an error has occurred while updating the device software" screen.
I got this issue due to unsuccesful flashing DOH6 firmware via Odin
"Download mode" is available, "Recovery mode" is not
I triyed to flash firmware again, but, unfortunately, have no success.
When it boot in "download mode" it shows:
"ODIN MODE
PRODUCT NAME: SM-G925T
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
FRP LOCK: OFF
Secure Download: Enabled
KNOX WARRANTY VOID: 1 (0x0304)
RP SWREV: B:2 K:2 S:2"
It can only go to download mode when charger or pc is plugged in. Boot loop also only accures when plugged in otherwise no sign of life.
I have tried reflash FW several times with this result:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then tried this method:
originally Posted by samanbabah
Ok everyone. here is the fix for those stuck at Samsung logo after 5.1.1 update thanks to this person "Tuandung.tran". I had to go to a Vietnamese site and download the file that took me 7 hours to download, I had a hard time translating the site since it was in Vietnamese, so now I want to contribute and help others by saving them time with straight forward tutorial on how to fix the problem that they have.
Ok so here it is:
1) download this file and extract it to your PC ==========> https://mega.nz/#!vIEEBQyT!U5AzPE4iR...__4qiFTfkBupp0
2) go to recovery and delete system files and cache
3) go to download mode
4) open Odin on your PC and click AP to add AP_G925TUVU2COF6.tar that you extracted earlier to your PC
5) with Odin still open add BL_G925TUVU2COF6.tar by clicking BL button
6) click start
7) After Odin is finished, it will reboot your phone. just wait a few minutes and you'll be all set.
Here is the result:
Don't know what the "CM" means at the beginning of the last line, it wasn't there before.
Then tried the same without boot img., it started to flash but during flashing system img. failed again.
Without BL and AP everything flashes nicely.
Flashed S6-UniBase_BOG8_v2.tar kernel with no problem, wich made the triangle with the text "an error has occurred while updating the device software" disappear and took me to the samsung powered by android logo, where it loops for several minutes, then goes black.
Flashed g925t_of6_aou_twrp_recovery_v13.tar, but, it gave me the red text "Recovery is not Seandroid Enforcing"
When i flash G925T_Stock_Recovery_ZiDroid.com.tar text disappears, but still can't go to recovery mode.
I still have hope since frp lock is off and there is at least download mode, the phone reacts, still, am kind of stuck here, no idea, how to proceed.
Any help will be greatly appreciated.
Tried this too, with no success:
originally posted by uniphase
If you continue to have boot up problems after flashing any type of newer stock firmware to your phone using Odin and Smart Switch, like I did, you will have to perform something similar to this fix and break up the files in the firmware tarball into the BL and AP tar.md5 files. I split the COF8 firmware from SamMobile and flashed the reconstructed tar.md5 files to the BL and AP sections in Odin, and it worked!
Procedure:
1. Download the latest stock firmware from SanMobile or another source.
2. Rename the filename extension from xxxxx.tar.md5 to xxxxx.tar and open the tar file with WinRAR, 7zip or another utility that can extract tar files.
3. You should see the extracted files below:
- boot.img
- cache.img
- cm.bin
- modem.bin
- recovery.img
- sboot.bin
- system.img
4. Download the attachment in this XDA thread and extract it somewhere.
5. Place the boot.img, system.img, sboot.bin, and cm.bin files in the bin folder, extracted from the attachment in the XDA thread in step 4.
6. Open notepad or another text editor and create this batch file in the same bin folder. Save the filename as convert.bat or whatever you filename you prefer with a .bat extension.
Code:
tar -H ustar -c sboot.bin cm.bin > BL.tar
md5sum -t BL.tar >> BL.tar
mv BL.tar BL.tar.md5
@ECHO off
timeout /t 3 /nobreak @ECHO on
tar -H ustar -c boot.img system.img > AP.tar
md5sum -t AP.tar >> AP.tar
mv AP.tar AP.tar.md5
7. Run the bat file and BL.tar.md5 and AP.tar.md5 will be subsequently created.
8. Open Odin on your PC and click AP to add AP.tar.md5 that was created in Step 7.
9. With Odin still open add BL.tar.md5 by clicking BL button.
10. Click Start.
The phone should be working after the reboot and get past the Samsung Galaxy S6 edge logo!
This method looked very promising, but flashing failed again, just like anything else i've tried so far.
I took the tar files apart and turned out that the two bin files stops flashing immediately, and the system image goes on flashing till a certain point, then flashing fails.
If i leave out these three files, everything goes fine, if any of them is present, flashing fails.
Also tried kies emergency recovery with serial number, but, it went on till 15%, then failed.
Any ideas?
Are you sure it says "RP SWREV: B:2 K:2 S:2" ?
And not "B:3" in there?
It almost sounds like you're on DOI1 firmware, and can't downgrade to DOH6. At least from what I've been seeing elsewhere. Based on all the symptoms, it really, really sounds like you're stuck on DOI1 firmware.
Considering you're pretty much dead-in-the-water at the moment, I might suggest you just download the DOI1 Odin and flash it. If you're not already locked into DOI1 (as mentioned, can't downgrade DOI1 -> older), then you will be after a successful flash/boot.
But hey, if that brings your device back, then so be it, right?
Good luck, friend. I'm still on OH6, so I can't really speak from experience on this one.
Aou said:
Are you sure it says "RP SWREV: B:2 K:2 S:2" ?
And not "B:3" in there?
It almost sounds like you're on DOI1 firmware, and can't downgrade to DOH6. At least from what I've been seeing elsewhere. Based on all the symptoms, it really, really sounds like you're stuck on DOI1 firmware.
Considering you're pretty much dead-in-the-water at the moment, I might suggest you just download the DOI1 Odin and flash it. If you're not already locked into DOI1 (as mentioned, can't downgrade DOI1 -> older), then you will be after a successful flash/boot.
But hey, if that brings your device back, then so be it, right?
Good luck, friend. I'm still on OH6, so I can't really speak from experience on this one.
Click to expand...
Click to collapse
Yea, you are right mate, it is B:3 indeed.
I'm downloading DOI1 as you suggested, gonna flash it and report back.
Really have nothing to loose with a $600 paperweight...
Thanks for your help, i keep up hope and report back soon!
This is probably the main cause of all the "stuck in animation logo" "bootloop" scenarios, downgrading.
Pp.
I have done everything possible to fix this phone. I was sure this was a excellent and sure fix. I pass ODIN ever time and yet still see a blinking logo.
That's Samsung's firmware protection in action, there just improving security on there phones so that stolen phone's can't be re-flashed and activated.
Pp.
pederzen said:
Yea, you are right mate, it is B:3 indeed.
I'm downloading DOI1 as you suggested, gonna flash it and report back.
Really have nothing to loose with a $600 paperweight...
Thanks for your help, i keep up hope and report back soon!
Click to expand...
Click to collapse
I have downloaded and flashed DOI1.
Unfortunately it is no success, though that funky little green line has never got as far as this time...
It also kooks like cm.bin, boot.img, and recovery.img flashes without problem.
It's very promising.
Attempt #1:
Attempt #2:
Attempt #3:
Sometimes process goes almost till the end. It always hangs while system image flashes.
Dodn't understand why it gets stuck at different points though.
After a few more attempts, i decided to try kies recovery again.
I left the PC on for night since the DL of FW is very slow.
It recognised that device needs DOI1 FW.
It failed again and still, leaved me with no recovery number to use for another attempt on another PC, what normally comes up when such a recovering procedure goes down with no success.
ODIN mode sais "Current binary: OFFICIAL" now.
What would be the next move?
Somebody wrote somewhere to install TWRP recovery, try to reboot into and flash a ROM from there.
Frankly, i'm getting out of ideas, i'm no expert in android or linux, at this point all i do is repeating the few methods that i have found so far, in different order wich, apparently gives me no luck.
Maybe some lower level process could wake my little black darling up from her deep sleep?
OMG!!!!View attachment 3502850
Now waiting to see if it boots up...
4 minutes have passed so far...
Well it seems like stuck on the powered by android screen.
26 minutes passed.
OK, flashed again, passed again and still, it is stuck on samsung screen.
This is great progress, i feel like only the last tiny piece is missing from the puzzle...
I wonder how long it can take the phone to boot after a FW reflash.
Anyways i leave it be for the time being, we'll see what happens.
An hour has passed, nothing happens.
Phone is warm feels like it's working on something or maybe only because of charging.
It doesn't seem like a bootloop since the samsung screen is continously on, it doesn't disappeare and come back.
It just stays.
Strange.
I had read in one the threads that one guy in similar kind if situation deleted the cache partition from the tar file, repacked and flashed and it booted up. According to him cache partition was preventing it from booting. May be worth a try..
Sent from my SM-G925T using Tapatalk
Alex9090 said:
I had read in one the threads that one guy in similar kind if situation deleted the cache partition from the tar file, repacked and flashed and it booted up. According to him cache partition was preventing it from booting. May be worth a try..
Sent from my SM-G925T using Tapatalk
Click to expand...
Click to collapse
Sounds like a plan
Give it a shut and report back soon.
Thanks for your help!
PanchoPlanet said:
That's Samsung's firmware protection in action, there just improving security on there phones so that stolen phone's can't be re-flashed and activated.
Pp.
Click to expand...
Click to collapse
Correct me if i'm wrong but if it was Samsung's firmware protection, FRP lock would be ON.
In my case it sais OFF.
Otherwise i agree with you these cases are 95% FW/downgrade related.
@pederzen, that's awesome that you've made progress, but I'm starting to question some things...
Are you sure you've got a good cable, and that it's well-connected to the device? To be sure, maybe snag a different cable, and don't touch it while flashing.
The fact that it's passing the md5 check suggests that the file did not get corrupted upon download, but I'm wonder if something is breaking it while it's flashing? How's your RAM/memory, are you overlocking or anything? Also, you might disable all antivirus/antispyware and disconnect from your network(s)/internet before even opening Odin.
Be sure you've got the correct version of Odin. Last I knew, v3.10.6 was working great for OH6.
Got drivers? Might double-check your device drivers for the device and such. A long shot on this one, because it's usually all-or-nothing.
Maybe just try a different computer if you can.
The fact that it's failing during system partition is the most disturbing thing. I'm doubting that your last "Pass" was actually successful.
@Aou
Tried two computers, several cables still the same.
When flshing hangs, a few seconds pass, unknown USB device sign comes up.
Went to samsung page, DL-ed, installed latest driver.
Now it sais in device manager:
'Device USB\VID_04E8&PID_685D\5&106f75ea&0&4 requires further installation.'
Whether it is connected in Odin mode or in normal mode when the screen with the triangle is on saying that installation went wrong...bla-bla
Checked events after driver installation, it sais:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-UserPnp" Guid="{96F4A050-7E31-453C-88BE-9634F4E02139}" />
<EventID>20001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>7005</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2015-10-12T11:05:28.095021600Z" />
<EventRecordID>7178</EventRecordID>
<Correlation />
<Execution ProcessID="5172" ThreadID="6744" />
<Channel>System</Channel>
<Computer>PUDVAS</Computer>
<Security UserID="S-1-5-18" />
</System>
- <UserData>
- <InstallDeviceID xmlns="http://manifests.microsoft.com/win/2004/08/windows/userpnp">
<DriverName>ssudbus.inf_amd64_6c8cd03f9c562c7a\ssudbus.inf</DriverName>
<DriverVersion>2.11.10.0</DriverVersion>
<DriverProvider>SAMSUNG Electronics Co., Ltd.</DriverProvider>
<DeviceInstanceID>USB\VID_04E8&PID_685D\5&106F75EA&0&4</DeviceInstanceID>
<SetupClass>{36FC9E60-C465-11CF-8056-444553540000}</SetupClass>
<RebootOption>false</RebootOption>
<UpgradeDevice>false</UpgradeDevice>
<IsDriverOEM>true</IsDriverOEM>
<InstallStatus>0x0</InstallStatus>
<DriverDescription>SAMSUNG Mobile USB CDC Composite Device</DriverDescription>
</InstallDeviceID>
</UserData>
</Event>
Maybe those two lines with 'false' at the bottom are supposed to be 'true'.
Might this be the cause of all the problems or, this is normal.
Shall i try to solve this driver issue first?
(If there is an issue at all.)
The rest what you wrote seem to be in working order.
pederzen said:
Correct me if i'm wrong but if it was Samsung's firmware protection, FRP lock would be ON.
In my case it sais OFF.
Otherwise i agree with you these cases are 95% FW/downgrade related.
Click to expand...
Click to collapse
In order to mess with your phone the option should be "on" , that denotes that Samsung's "FRP" with be deactivated and no interference will take place or bricking.
If it's "off" then you run the risk of borking your phone.
Off, no good.
On, ok.
Another thing running Windows 7 on my Asus, my device manager recognises my (stock) phone as a Samsung device.
Pp.
This is what you want in developer options.
Pp.
pederzen said:
@Aou
Tried two computers, several cables still the same.
When flshing hangs, a few seconds pass, unknown USB device sign comes up.
Went to samsung page, DL-ed, installed latest driver.
Now it sais in device manager:
'Device USB\VID_04E8&PID_685D\5&106f75ea&0&4 requires further installation.'
Whether it is connected in Odin mode or in normal mode when the screen with the triangle is on saying that installation went wrong...bla-bla
(snip)
Maybe those two lines with 'false' at the bottom are supposed to be 'true'.
Might this be the cause of all the problems or, this is normal.
Shall i try to solve this driver issue first?
(If there is an issue at all.)
The rest what you wrote seem to be in working order.
Click to expand...
Click to collapse
Well, the fact that you've tried two different computers does narrow things down a tad, except the antivirus/antimalware thing, if you happened to be running the same on both PCs.
As for that specific driver (the CDC one), I've got 2.12.0.0 on my computer, but this is on Win10 at the moment. I could probably check my Win7 installation, but I'm not physically in front of my computer at the moment and can't reboot into Win7 from here.
Usually Samsung Smartswitch (Kies) will force you to get the latest/proper drivers for the device. Do you have the latest version of SmartSwitch?
As for the "false" parts there, that shouldn't matter, I wouldn't think. Odin itself does have an option about rebooting after a successful flash, though.
I believe the behavior you're seeing - where upon an unsuccessful flash you see another device show up - is the device trying to go into some sort of emergency download mode. Like, a more fundamental download mode that Samsung can use to forcefully flash things to the phone to try to revive it. I've had some older Samsung phones do that before upon a bad flash of firmware.
Are you familiar with how to tarball an image for Odin? I'm thinking you might try to re-package only the system.img into a new tarball, and flash that alone. From a CygWin terminal, or in a Linux environment (say hello to VirtualBox and Ubuntu!), you'd do something like this:
Code:
tar -H ustar -c system.img > DOI1_system.tar && md5sum -t DOI1_system.tar >> DOI1_system.tar && mv DOI1_system.tar DOI1_system.tar.md5
Or you could skip the md5 generation and just do:
Code:
tar -H ustar -c system.img > DOI1_system.tar
Of course, the above implies that you extracted the system.img from the Odin package. The .zip file contains the .tar.md5 (of course), and you can use a tool like 7-zip to open that md5'd tarball. You'll probably see warnings/errors about an improper ending to the tarball, but that's because of the md5 hash that's been literally just slapped onto the backside of the tarball. Safe to ignore that.
Let me know if you need me to do this and upload it, but it would take me a little while.
Here is the system.img tar file according to Aou's instructions. You have to unzip it.
System.img
Thank you friends! You guys are wonderful.
I'll give it a shot when i get home this afternoon (EU time)
Let's hope this will give it the final push!
Alex9090 said:
Here is the system.img tar file according to Aou's instructions. You have to unzip it.
System.img
Click to expand...
Click to collapse
Mega requires a key for the download, can you give it please?
Tried 'Don't look back in Anger' but didn' work
Welcome to this easy guide.
Time needed: 15 / 60min (depends on your internet connection)
Ease of operation: Very easy
Don't be fooled by the length of this guide ... the operations to be done are quick and easy.
NB: I state immediately that this procedure does not restore the state of Knox to 0x0 if by chance you have brought it to 0x1.
To date, this is an irreversible process.
In the next lines we will see how to restore our Samsung device to its original factory conditions, after unlocking the Bootloader, rooting and installing various types of custom installations, such as custom OneUI, AOSP or Google ROM.
It may happen that you want to go back to the original firmware of our Samsung, after trying various custom ROMs, after having rooted and modified the recovery, missing with the phone partitions, lost EFS folder or corrupt IMEI. The reasons can be many. This guide is aimed at all those who, with the classic Odin procedure to install the stock rom, are unable to restore the phone to normal operating conditions.
But it can happen to fail in this thing, even using Odin to put back the original software, Odin himself or the phone can crash to the BOOT partition or generate other errors, with VBMeta or generic errors, including partition ones.
So let's see how to solve all the inconveniences due to modding on our Samsungs to 99%. Let's begin!
- MATERIAL REQUIRED:
Latest version of Frija link
Latest version of Odin link
Samsung USB Driver link
File Manager zip (example 7zip) link
PC with Microsoft Windows 7-8-8.1-10-11
USB type C cable
1 - Download the latest stock firmware for our Samsung:
Download the latest version of Frija and once the program has started, enter the model code of your device and the abbreviation of your CSC.
Make sure the "Auto" checkbox is checked.
Once you have checked everything, click on "Check Update" and click on "Download". Wait for it to download.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Once you have downloaded the zip containing the various parts that make up the stock software (see image below), extract it to a folder of your choice. We will have 5 files in total.
2 - Retrieve the original PIT file
To recover the PIT file (partition list) for our device, go to the firmware folder you just downloaded with Frija, locate the "tar.md5" file with the words CSC_OXM_N............., right click on the it and select rename, adding ".zip" at the end to "transform" it into a compressed file that can be opened. This way you will have something like
"CSC_OXM_N975...............REV01_user_low_ship.tar.md5.zip"
Give the Ok and confirm the change of the file extension.
You should now have the same situation as you see in the image below. Total 5 files of which one is a ".zip" files.
Now open the file you just renamed with 7zip, the main window of the 7zip program will open with various files inside:
Now copy the "D2S_EUR_OPEN.pit" file by right clicking and selecting the "copy to ..." item and giving the ok without changing anything. The .PIT file will be copied to the same folder as the previously downloaded firmware.
Once this is done, the folder that appears will look like this (Now, the total files are 6 of which one is a ".zip" files):
Now just put the CSC_OXM ... file back to the previous condition, renaming it one more time and eliminating the ".zip" extension at the end of the name, in order to find an MD5 file again. This will be the file we will have:
"CSC_OXM_N975...............REV01_user_low_ship.tar.md5."
Now we have everything we need. If we have done everything correctly this is the final result (Total 6 files).
3 - Prepare and Configure Odin
Now open the latest version of Odin (as of May 2022 the latest version is 3.14.4), load the corresponding downloaded firmware files in the various slots (BL, AP, CP and CSC) as usual.
In the CSC box, upload the file labeled "CSC_OXM_N975 ............... REV01_user_low_ship.tar.md5."
Did you know that....
The CSC_OXM file is used to restore the internal memory as factory, this will delete all personal data in the phone memory, all applications and data associated with it.
The HOME_CSC_OXM file, on the other hand, will not act in any way on the internal memory. Useful if you want to update while remaining in the same type of ROM. Not recommended if your phone has a Custom ROM installed, as it may not start or give errors in previously installed applications.
If you want to do a clean install of the original ROM, always use the CSC_OMX file!
Click to expand...
Click to collapse
Once this is done, move (still in Odin) to the "Option" tab and check the following items:
Auto Reboot
Nand Erase
Re-partition
F. Reset time
The rest of the items MUST NOT BE SELECTED!
Again in Odin, this time go to the PIT tab, a warning message will appear, give the ok and select the first extracted file which has the unique name "D2S_EUR_OPEN.pit"
If you have done everything right you should have the same situation as the image below:
4 - Return the phone to the original firmware
Connect the USB type C cable to your phone and restart your phone in "Download mode" (check the right combination for your model), or use the Custom Rom to do this, usually all coustom roms or custom recovery offer reboot in Download mode (or Booloader).
In odin in the "Log" tab, you should see the word "Added" with the number of the port to which it is connected (example "0: [COM3]"), if so, press the START key of Odin and wait for the restart (this procedure will delete all data on your device).
If nothing appears, install the Samsung USB drivers and repeat step 4.
5 - Relock the BootLoader
To get rid of that fatal warning message when starting the phone that tells us that the BootLoader is unlocked once and for all, let's put it back in place, relocking the BootLoader.
(Image for demonstration purposes)
Turn off the phone, reconnect the USB cable and immediately press the Volume + and Volume- keys at the same time.
Return to Download mode (albeit a little different), with various options (actually only 3).
In this case, follow the second option (Volume up long press: Device unlock mode) hold down the Volume + key for a few moments until the message "Lock Bootloader?" Appears. To confirm everything, make a single click on Volume + (also in this case the phone will be formatted by the system again) and wait for a complete restart.
6 - Relock OEM (optional but recommended if you want to stick with the Samsung ROM)
Once your phone has restarted and the initial setup is complete, you can also disable the OEM unlock capability and reuse the security features.
To do this, go to Settings / Phone Information / Software Information and tap several times on the wording "Build version" in order to unlock the "Developer options". If prompted, unlock your smartphone with your PIN or sign.
Now go back to the main Settings page, open the Developer Options and check that the "OEM Unlock" item is disabled, otherwise disable it and restart the device.
Well now you have your Samsung with Original firmware again. Enjoy
ExileTM said:
Welcome to this easy guide.
Time needed: 15 / 60min (depends on your internet connection)
Ease of operation: Very easy
Don't be fooled by the length of this guide ... the operations to be done are quick and easy.
NB: I state immediately that this procedure does not restore the state of Knox to 0x0 if by chance you have brought it to 0x1.
To date, this is an irreversible process.
In the next lines we will see how to restore our Samsung device to its original factory conditions, after unlocking the Bootloader, rooting and installing various types of custom installations, such as custom OneUI, AOSP or Google ROM.
It may happen that you want to go back to the original firmware of our Samsung, after trying various custom ROMs, after having rooted and modified the recovery, missing with the phone partitions, lost EFS folder or corrupt IMEI. The reasons can be many. This guide is aimed at all those who, with the classic Odin procedure to install the stock rom, are unable to restore the phone to normal operating conditions.
But it can happen to fail in this thing, even using Odin to put back the original software, Odin himself or the phone can crash to the BOOT partition or generate other errors, with VBMeta or generic errors, including partition ones.
So let's see how to solve all the inconveniences due to modding on our Samsungs to 99%. Let's begin!
- MATERIAL REQUIRED:
Latest version of Frija link
Latest version of Odin link
Samsung USB Driver link
File Manager zip (example 7zip) link
PC with Microsoft Windows 7-8-8.1-10-11
USB type C cable
1 - Download the latest stock firmware for our Samsung:
Download the latest version of Frija and once the program has started, enter the model code of your device and the abbreviation of your CSC.
Make sure the "Auto" checkbox is checked.
Once you have checked everything, click on "Check Update" and click on "Download". Wait for it to download.
View attachment 5628035
Once you have downloaded the zip containing the various parts that make up the stock software (see image below), extract it to a folder of your choice. We will have 5 files in total.
View attachment 5629259
2 - Retrieve the original PIT file
To recover the PIT file (partition list) for our device, go to the firmware folder you just downloaded with Frija, locate the "tar.md5" file with the words CSC_OXM_N............., right click on the it and select rename, adding ".zip" at the end to "transform" it into a compressed file that can be opened. This way you will have something like
"CSC_OXM_N975...............REV01_user_low_ship.tar.md5.zip"
Give the Ok and confirm the change of the file extension.
You should now have the same situation as you see in the image below. Total 5 files of which one is a ".zip" files.
View attachment 5629261
Now open the file you just renamed with 7zip, the main window of the 7zip program will open with various files inside:
View attachment 5628037
Now copy the "D2S_EUR_OPEN.pit" file by right clicking and selecting the "copy to ..." item and giving the ok without changing anything. The .PIT file will be copied to the same folder as the previously downloaded firmware.
View attachment 5629463
Once this is done, the folder that appears will look like this (Now, the total files are 6 of which one is a ".zip" files):
View attachment 5629465
Now just put the CSC_OXM ... file back to the previous condition, renaming it one more time and eliminating the ".zip" extension at the end of the name, in order to find an MD5 file again. This will be the file we will have:
"CSC_OXM_N975...............REV01_user_low_ship.tar.md5."
Now we have everything we need. If we have done everything correctly this is the final result (Total 6 files).
View attachment 5629265
3 - Prepare and Configure Odin
Now open the latest version of Odin (as of May 2022 the latest version is 3.14.4), load the corresponding downloaded firmware files in the various slots (BL, AP, CP and CSC) as usual.
In the CSC box, upload the file labeled "CSC_OXM_N975 ............... REV01_user_low_ship.tar.md5."
Once this is done, move (still in Odin) to the "Option" tab and check the following items:
Auto Reboot
Nand Erase
Re-partition
F. Reset time
The rest of the items MUST NOT BE SELECTED!
View attachment 5628039
Again in Odin, this time go to the PIT tab, a warning message will appear, give the ok and select the first extracted file which has the unique name "D2S_EUR_OPEN.pit"
If you have done everything right you should have the same situation as the image below:
View attachment 5628043
View attachment 5628045
4 - Return the phone to the original firmware
Connect the USB type C cable to your phone and restart your phone in "Download mode" (check the right combination for your model), or use the Custom Rom to do this, usually all coustom roms or custom recovery offer reboot in Download mode (or Booloader).
In odin in the "Log" tab, you should see the word "Added" with the number of the port to which it is connected (example "0: [COM3]"), if so, press the START key of Odin and wait for the restart (this procedure will delete all data on your device).
If nothing appears, install the Samsung USB drivers and repeat step 4.
View attachment 5628041
5 - Relock the BootLoader
To get rid of that fatal warning message when starting the phone that tells us that the BootLoader is unlocked once and for all, let's put it back in place, relocking the BootLoader.
View attachment 5629449
(Image for demonstration purposes)
Turn off the phone, reconnect the USB cable and immediately press the Volume + and Volume- keys at the same time.
Return to Download mode (albeit a little different), with various options (actually only 3).
In this case, follow the second option (Volume up long press: Device unlock mode) hold down the Volume + key for a few moments until the message "Lock Bootloader?" Appears. To confirm everything, make a single click on Volume + (also in this case the phone will be formatted by the system again) and wait for a complete restart.
6 - Relock OEM (optional but recommended if you want to stick with the Samsung ROM)
Once your phone has restarted and the initial setup is complete, you can also disable the OEM unlock capability and reuse the security features.
To do this, go to Settings / Phone Information / Software Information and tap several times on the wording "Build version" in order to unlock the "Developer options". If prompted, unlock your smartphone with your PIN or sign.
Now go back to the main Settings page, open the Developer Options and check that the "OEM Unlock" item is disabled, otherwise disable it and restart the device.
View attachment 5629493
Well now you have your Samsung with Original firmware again. Enjoy
Click to expand...
Click to collapse
Hi there. I tried it and didn't work for me.
Tried with differents CSC too, but my phone doesn't start the system. Just starts the download and recovery mode
It doesn't even show up the charging screen when powered off
Tried so many things and I can't boot my system...
I made a post with the info about what happened:
Need help with semi-bricked Note 10 Plus (SM-N975F) - Stuck on recovery/download mode
Didn't know where to post this exactly, to be honest. This will be a long post I was flashing AOSP roms in the phone. Tried to go back to One UI for the VoLTE thing In one of the AOSP roms I couldn't install it in Lineage Recovery (older version...
forum.xda-developers.com
Please help...
Ok, tell me where you get stuck ... or can you follow the whole guide but then the phone doesn't start?
Is the model number of your Note10+ is SM-N975F?
What original CSC did you have before you root?
RedSpikeJr said:
Hi there. I tried it and didn't work for me.
Tried with differents CSC too, but my phone doesn't start the system. Just starts the download and recovery mode
It doesn't even show up the charging screen when powered off
Tried so many things and I can't boot my system...
I made a post with the info about what happened:
Need help with semi-bricked Note 10 Plus (SM-N975F) - Stuck on recovery/download mode
Didn't know where to post this exactly, to be honest. This will be a long post I was flashing AOSP roms in the phone. Tried to go back to One UI for the VoLTE thing In one of the AOSP roms I couldn't install it in Lineage Recovery (older version...
forum.xda-developers.com
Please help...
Click to expand...
Click to collapse
ExileTM said:
Ok, tell me where you get stuck ... or can you follow the whole guide but then the phone doesn't start?
Is the model number of your Note10+ is SM-N975F?
What original CSC did you have before you root?
Click to expand...
Click to collapse
I followed the full guide, but I got stuck after flashing the firmware in Odin. It shows the screen of "Erasing data", and after that, nothing more
Even after locking again the bootloader
And yes, I ticked what's needed in Odin and used the .pit file
My model it's SM-N975F
The original CSC it's ZTO. Flashed the latest firmware
Ok so with Odin it didn't give you any problem. Let's say he freezes when he does the first boot that does the factory reset. Right?
Well odd, because once the original firmware is installed, I don't see why it should crash on boot ... unless there is a hardware problem in the phone's internal memory.
I know it may sound trivial, but the usb cable you use is good and did you use the latest version of Odin?
Have you checked maybe if the internal memory is right for you. If it is 256Gb or 512Gb
You could try this, if you see that it does not start try to enter the recovery (the original one) and delete everything you can, like cache and do a reset data directly from the recovery. Then try restarting and see if it starts.
If it still doesn't boot, try this thing.
Install TWRP custom recovery and enter once installed.
Go to Wipe Section in TWRP, Repair or Change partition, System and Data, and Changed Ext4 to EXTFAT. And changed back to Ext4. Eventually rerun the guide again.
ExileTM said:
Ok so with Odin it didn't give you any problem. Let's say he freezes when he does the first boot that does the factory reset. Right?
Well odd, because once the original firmware is installed, I don't see why it should crash on boot ... unless there is a hardware problem in the phone's internal memory.
I know it may sound trivial, but the usb cable you use is good and did you use the latest version of Odin?
Have you checked maybe if the internal memory is right for you. If it is 256Gb or 512Gb
Click to expand...
Click to collapse
The USB it's the original from Samsung.
The device is 256GB
ExileTM said:
You could try this, if you see that it does not start try to enter the recovery (the original one) and delete everything you can, like cache and do a reset data directly from the recovery. Then try restarting and see if it starts.
Click to expand...
Click to collapse
Tried this already. Didn't work
ExileTM said:
If it still doesn't boot, try this thing.
Install TWRP custom recovery and enter once installed.
Go to Wipe Section in TWRP, Repair or Change partition, System and Data, and Changed Ext4 to EXTFAT. And changed back to Ext4. Eventually rerun the guide again.
Click to expand...
Click to collapse
I tried this but not in the process of "Do the format and then do the Odin process" so I can try
I'm trying now with USB OTG to know if I can flash the system.img (and know if from there I can solve this)
ExileTM said:
If it still doesn't boot, try this thing.
Install TWRP custom recovery and enter once installed.
Go to Wipe Section in TWRP, Repair or Change partition, System and Data, and Changed Ext4 to EXTFAT. And changed back to Ext4. Eventually rerun the guide again.
Click to expand...
Click to collapse
Tried from reset data on official recovery to doing the change of format in TWRP and the doing all of the process again. No success.
Also tried with USB OTG with system, vendor, product and boot image. Neither
One thing that happened is that when trying to change the system partition to exFAT, it gave an error (system is not mounted) but changed the format to vFAT. Changing it to another option doesn't give that error, so I tried to do with another option and back to ext4.
I don't think it's a physical issue, if turns on, there is some hope at least
There is almost certainly a solution to your problem. (have you tried to do "format data" and typed "yes" in TWRP recovery?). Anyway, it's night at my place now, I'll see tomorrow to think of some other solution.
Tried already. Also tried to format the data with fastboot (Lineage Recovery gives the option to fastboot in Samsung)
I have the exackt same problem with my note10+ with 256GB and dual sim. and the problem you describe is also 100% what i experienced and still have as an issue... If you get to the point where you can solve the issue then please write me my friend. I will do the same ofcourse... btw can you use your pen in TWRP? i can only mark the files but not click them to run...? i have the idea that the TWRP for our model isnt built right somehow..
I assume you haven't solved the problem yet. In these days I have looked around but I have not found much ...
I saw a video, which through the ADB shell a guy was able to find the list of all partitions with the numbers of all the blocks and information and practically managed to rebuild the system partition from scratch, but I don't know if it works on samsung.
This is video:
Then another thing, what procedure did you follow for rooting? You may have had problems during the rooting process.
I followed this guide:
To update the situation
The battery of the phone inflated like a balloon, so I needed to go to a technician. I don't know for sure if that was caused by something physical, but will update when have some news
Ok, let me know if the technician can get you to restart the phone, and out of curiosity, he can bring the knox back to 0.
Hi, I was trying this today and I'm stuck at "An error has occured while updating the device software."
Odin was stuck at product.img for over an hour so I restarted the phone using volume down and power.
I tried again and it keeps getting stuck at product.img while the phone shows this error. Please could you help me out?
I followed all the steps exactly as you said, but I noticed while in download mode that it showed Warranty Void: 1
I did not root the phone, only flashed Pixel Experience and now trying to go back to OneUI
aaaajwedk said:
Hi, I was trying this today and I'm stuck at "An error has occured while updating the device software."
Odin was stuck at product.img for over an hour so I restarted the phone using volume down and power.
I tried again and it keeps getting stuck at product.img while the phone shows this error. Please could you help me out?
I followed all the steps exactly as you said, but I noticed while in download mode that it showed Warranty Void: 1
I did not root the phone, only flashed Pixel Experience and now trying to go back to OneUI
View attachment 5647587
Click to expand...
Click to collapse
Hello, then, the Warranty Void at 1 is triggered when you install a non-original firmware (in this case the PixelExperience), or when you change Recovery (ex: the TWRP) or you run the ROOT.
Any other software that is not in original firmware triggers the Knox to 0x1 irreversibly.
In your specific case, by installing the LineageOS Recovery and the PixelExperence ROM you have triggered the Knox at 0x1.
I am sorry.
Coming to your problem, the model of your phone what it is (ex: SM-N975F) and the CSC (ex: ITV). Did you download the original software for your exact model? Did you extract the PIT file from the original firmware and put it in the Option tab in Odin?
ExileTM said:
Hello, then, the Warranty Void at 1 is triggered when you install a non-original firmware (in this case the PixelExperience), or when you change Recovery (ex: the TWRP) or you run the ROOT.
Any other software that is not in original firmware triggers the Knox to 0x1 irreversibly.
In your specific case, by installing the LineageOS Recovery and the PixelExperence ROM you have triggered the Knox at 0x1.
I am sorry.
Coming to your problem, the model of your phone what it is (ex: SM-N975F) and the CSC (ex: ITV). Did you download the original software for your exact model? Did you extract the PIT file from the original firmware and put it in the Option tab in Odin?
Click to expand...
Click to collapse
Hello, I got it working just now by using a different cable and USB port. The procedure completed and the phone restarted by itself, and now its perfectly fine. Thank you so much for your help.
Yes, the phone is an SM-N975F. Despite Knox being tripped, my banking and payment apps are still working so I'm happy
I'm sure your article will be helpful to many more users. Thank you!
aaaajwedk said:
Hello, I got it working just now by using a different cable and USB port. The procedure completed and the phone restarted by itself, and now its perfectly fine. Thank you so much for your help.
Yes, the phone is an SM-N975F. Despite Knox being tripped, my banking and payment apps are still working so I'm happy
I'm sure your article will be helpful to many more users. Thank you!
Click to expand...
Click to collapse
OK well. Glad it was helpful. Yes, however, until you root all the apps will work. The only one are some applications by Samsung that will no longer work because they are based on the knox.
Otherwise like Google Pay, all banking and account apps, software updates should work smoothly.
Hi, is this guide usable for the S22 snapdragon version? My device is rooted, and I want to back to original firmware.