Develop Bugs

[GUIDE] Fix an unflashable or soft bricked N7100!

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.

Flashing 5.1.1. DOH 6 failed, bootloop, no recovery mode, ODIN wont flash

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

HELP: I accidentally wiped OS off my phone in TWRP

I'm a newbie with this.. I got my Nexus 5x a few weeks ago. With the instruction of someone else i unlocked the boot loader and rooted my phone. then i had an issue with boot looping after some customization on my phone. so i attempted to wipe all that stuff off my phone is TWRP and i accidentally checked system. Now what do i do? Now i don't really know what a rom is or adb side loader or something like that.. i need some simple and clear instructions to get my phone working again. preferably without having to root all over again (that was exhausting and quite difficult, lots of trial and error).. but if it won't be rooted anymore, it's better than nothing. Please help!!

starlitserenity said:
I'm a newbie with this.. I got my Nexus 5x a few weeks ago. With the instruction of someone else i unlocked the boot loader and rooted my phone. then i had an issue with boot looping after some customization on my phone. so i attempted to wipe all that stuff off my phone is TWRP and i accidentally checked system. Now what do i do? Now i don't really know what a rom is or adb side loader or something like that.. i need some simple and clear instructions to get my phone working again. preferably without having to root all over again (that was exhausting and quite difficult, lots of trial and error).. but if it won't be rooted anymore, it's better than nothing. Please help!!
Click to expand...
Click to collapse
just copy some rom , twrp can access mtp

Apayah said:
just copy some rom , twrp can access mtp
Click to expand...
Click to collapse
again , i dont know what a rom is or where to find one and i have no idea what mtp is.

starlitserenity said:
again , i dont know what a rom is or where to find one and i have no idea what mtp is.
Click to expand...
Click to collapse
when you in twrp , just plug it into your pc

starlitserenity said:
I'm a newbie with this.. I got my Nexus 5x a few weeks ago. With the instruction of someone else i unlocked the boot loader and rooted my phone. then i had an issue with boot looping after some customization on my phone. so i attempted to wipe all that stuff off my phone is TWRP and i accidentally checked system. Now what do i do? Now i don't really know what a rom is or adb side loader or something like that.. i need some simple and clear instructions to get my phone working again. preferably without having to root all over again (that was exhausting and quite difficult, lots of trial and error).. but if it won't be rooted anymore, it's better than nothing. Please help!!
Click to expand...
Click to collapse
Heinsbergs guide here describes how to return to stock
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Scroll down to "10. How To Flash The Factory Images (And Return To Stock)"

Darke5tShad0w said:
Heinsbergs guide here describes how to return to stock
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Scroll down to "10. How To Flash The Factory Images (And Return To Stock)"
Click to expand...
Click to collapse
again, i cant do that . my OS is completely wiped. i went to #10 - the instructions cant be followed, i cant get onto my phone except into twrp.

Apayah said:
when you in twrp , just plug it into your pc
Click to expand...
Click to collapse
when i connect my phone to my computer and am in twrp, then what?

starlitserenity said:
again, i cant do that . my OS is completely wiped. i went to #10 - the instructions cant be followed, i cant get onto my phone except into twrp.
Click to expand...
Click to collapse
You only removed system you should still be able to get into bootloader.
Turn phone off, hold the volume down button then power button.
Should go to a screen with a android man laying down and it saying fastboot mode in red.

Darke5tShad0w said:
You only removed system you should still be able to get into bootloader.
Turn phone off, hold the volume down button then power button.
Should go to a screen with a android man laying down and it saying fastboot mode in red.
Click to expand...
Click to collapse
then what? the instructions are too complicated for me :S and i dont understand most of the terms

starlitserenity said:
then what? the instructions are too complicated for me :S and i dont understand most of the terms
Click to expand...
Click to collapse
You are now in fastboot mode and bootloader is still unlocked?
Download and install this http://www.wugfresh.com/nrt/
Wait for it to load the try auto detect on the window that pops up, if that doesn't work select "nexus 5x" and then on the next one choose the one ending with "mhc19q" click next/continue.
then on the next window click download and update all dependances.
What for it to do its thing then on the next window click on "flash stock + unroot", click ok,
{
"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 ok. It will download the latest factory image and do its thing. What happens after this you will need to describe to me as I have not used this toolkit.

@starlitserenity, I can help you get an OS back onto your phone. It's very simple even though you may be a NOOB. It's OK. As long as you have access to a PC and Internet you are OK because you can still access TWRP. Here is a list of steps:
1) go to forum.xda-developers.com/nexus-5x/development
2) scroll down to the ROM labeled
"Pure Nexus"
3)In the first post (Original Post), scroll down and click on "Downloads & Changelog" You will be redirected to AFH (Android File Host) to download the ROM/OS
4)Scroll down just a little and you will see a Green Box with files/ROMs. Click on the newest one labeled
pure_Nexus_bullhead-6.0.1-20160407.
After you click on the ROM file, a new screen will appear with a Green Box that says "Begin Download".
5) Click on " Begin Download"
Once you click the "Begin Download" box, you will see below another Green Box that says "primary download". Click on the " Primary Download " box to begin downloading your new ROM/OS.
6) Go back to the Pure Nexus original post/first post and click on the link labeled "Highly Suggested Gapps"
You will be redirected to Android File Host again to download your Gapps(GoogleApps). Scroll down just a little to the Green Box again and select
PureNexus_Dynamic_Gapps_6.x.x_4-7-16.zip and click on the link.
7) A new screen will appear with a Green Box that says "Begin Download"
Click on the "Begin Download" box and just below another Green Box will appear that says "primary download".
Click on the " primary download " and this will download you Gapps.
8) Once both of your files have finished downloading onto your PC, boot your 5x into TWRP and connect it to your PC and let the drivers install so your Nexus is recognized by your PC.
9) Now that your 5x is recognized by your PC while booted into TWRP, you will need to move the 2 downloaded files from your PC's download folder to the internal storage of your 5x.
10) Now that you have moved both downloaded files to your Nexus 5x internal storage you will need to reboot your recovery. Select the home button in TWRP, select reboot, then select reboot recovery to reboot TWRP. This will all TWRP to recognize the two new files that were moved to your Nexus internal storage.
11) Unplug your Nexus from your PC. On your device, go to the TWRP home screen and select wipe, then swipe to factory reset. Now you are ready to install your new ROM and Gapps
12) Now that you have wiped the 5z again, select the TWRP home button. Next, select "Install". Navigate to your SD card/internal storage to locate the two files we moved to your Nexus from your PC. Select the file that says
pure_nexus_bullhead-6.0.1-20160407
Once selected you will be directed to a new TWRP screen and you will see a box to click on that says " Add More Zips" Click this box and navigate to the SD card/internal storage and select the 2nd file that says PureNexus_Dynamic_GApps_6.x.x_4-7-16.zip. Once you have selected the file you will be directed to another TWRP screen with a swipe button to install the ROM file and the Gapps file. Swipe the button to begin the installation.
13) Once the installation is complete, you will see a box that says wipe cache/dalvik. Select this box, wipe cache/dalvik, then select reboot system.
14) Once your device boots you will proceed to the setup wizard just like when your Nexus 5x was new out of the box. Go through the setup wizard to setup your device and once completed, reboot, and you will be back to normal with a pretty sweet custom ROM called Pure Nexus.
Sent from my Nexus 6 using XDA-Developers mobile app

-__-

Use power+volume button. You will get thishttp://www.androidcentral.com/sites/androidcentral.com/files/styles/large_wm_brw/public/article_images/2014/11/nexus-manual-update-01.jpg?itok=wEfVvztj.
Then flash nexus factory images. and go stock. You can skip flashing recovery or you can flash recovery again. You will lose root access. you have to flash supersu again

Update? We're you able to install a new ROM and get your 5x back up and running?
Sent from my Nexus 6 using XDA-Developers mobile app

Partly bricked... SM-N975F

Hey guys.. Ive been a visitor in XDA forums for quite a while... And i been running root and custom FW with more or less every samsung from S2 and up...
But i just got my self a note10+ (atleast thats what ive been told) and i wanted to root it up and throw a custom FW on it to run in Samsung Dex...
So i succeded updating the FW. I unlocked the bootloader in dev. options. and unlocked it again in download mode by holding the vol. up. key!
But since then i had problems... every time i run a FW in Odin... Then if i dont get a error saying
SW REV. CHECK FAIL(BOOTLOADER) DEVICE: B BINARY 7
pit_flash_binary - Unsupported version
Then i succeds but when its going to erase everything after the reboot from download mode then it starts up and stops right after... And then i can only go recovery mode and download mode... How do i just write the correct firmware and have it start up like normal... just wanna undo it all... Do i need some kind of samsung support software in windows? and how do i know if it is a note10+ ... Even though download mode says SM-N975F... But still i get error when i flash a FW downloaded with Frija for that model...
Hope to get some help

oh btw... it connects as this when im in download mode:
"Checking Connected Devices: SAMSUNG Mobile USB Modem #2 ( COM12 )"
is that normal?

bump?

Hey there,
SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 8 BINARY 7
Click to expand...
Click to collapse
This, as far as I understand just means that the bootloader on your phone is on a newer version than the one in the firmware you're trying to flash. Usually flashing just stops there.
Then i succeds but when its going to erase everything after the reboot from download mode then it starts up and stops right after...
Click to expand...
Click to collapse
You COULD try to simply boot into recovery and wipe the device once, the phone would usually do that on its own but sometimes fails. Mind describing what exactly happens?
how do i know if it is a note10+ ... Even though download mode says SM-N975F...
Click to expand...
Click to collapse
For that, you either need the original packaging or just trust on what Odin-mode is telling you.
But still i get error when i flash a FW downloaded with Frija for that model...
Click to expand...
Click to collapse
I kinda don't trust Frija. For me, Bifrost always worked like a charm. Use it to download the firmware for your SM-N975F and give it your correct region code.
For flashing, some people use Heimdall, I think Odin is pretty simple (as far as simplicity in modding goes).
By the way, if all fails, you could try installing LineageOS 19.1, throw in openGAPPS for Googles apps and Magisk/Lygisk for root (if needed).
Good luck and have fun!
Cheers!

I found out i got EXACKLY the same issue as the guy writing on this thread:
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
Nic0_ said:
You COULD try to simply boot into recovery and wipe the device once, the phone would usually do that on its own but sometimes fails. Mind describing what exactly happens?
Click to expand...
Click to collapse
Already tryed still nothing... But what happens after a 100% succes in Odin is:
Then it reboots and after a few secs it says "Erasing device" for like 0.5 sec... And then it only goes black screen... At black screen then i can only go download mode if i press both volume buttons at the same time for 1 sec. Or recovery mode if i press vol up and power. And thats only if i have a USB-C connected ofcourse.
And whats the issue is... when it stops erasing the device... Why does it stops after 0.5 secs? it normally goes like 2-5 secs ... But also ... After it stops and in black screen... If i continue into download mode and open up the bootloader then...
{
"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 been around TWRP, Original recovery and Lineage recovery... But as the guy writes on the other thread. Then it shows 0 MB on the data partition, and i have to format it before it shows up again with 223 (or something)GB again...

Hey there,
Could you try switching file systems around? TWRP lets you format your partitions with stuff like ext4, f2fs and some other file systems. On several custom ROMs, the file system sometimes is the difference between a system working or bootlooping.
Good luck and have a nice day.
Cheers!

Already tryed exfat and f2fs and then back to ext4

I might have found a solution

I tried to update firmware N9750 android 11 to android 12 with (Ap file + odin patched). I don't flash bl ,cp,csc files . the phone screen shows a software error, need to open the smart switch software on the computer to recover. I open the smart switch on the computer and it does not recognize the phone. odin patched still recognizes the phone is connected. i reset odin and flashed 1 BL file. phone booted again with bootloader + AP file is android12. and modem and csc are android 11
1: Try flash combination firmware?
2 : Try download firmware stock new bootloader
Download odin patched
Try flash firmware files one by one
restart phone go download mode flash file BL ..done
restart phone go download mode flash file AP
restart phone go download mode flash file CP
restart phone go download mode flash file CSC
If ok flash full 5 file
sorry my english is not good

someone could help please?
S20 FE bootloop after security update
So I never posted here but I usually pass by some topics so sorry for any mistake in creating this discussion. Today I deleted some stuff from my S20 FE and downloaded via OTA the march security update in my device, then I was caught by surprise...
forum.xda-developers.com

Question Red Warning and UnWorking Lockscreen. HELP

{
"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"
}
Hello, dear owners of this beautiful device.
After an unsuccessful attempt to get root, such a warning appeared, plus the ability to lock the screen disappeared. As a result, I didn't get root either and problems arose)
Could you show the instructions how to fix everything step by step and get root? Thanks)

Hey, so I have the same problem as you. I was installing the patched boot.img file when I rebooted, but there was no magsik app. After I tried to flash the same file again, except I put in some vbmeta file because some website said so, now my phone's files are corrupted. I got into fastboot mode and put through recovery mode, and did a data wipe and one final reboot, but even that did work because it said my phone is corrupt. The last thing I will try is to install TWRP, remove the old data, and install the update to restore the previous ROM files. I'll let you know if anything works. Just try ur methods and let me know if they worked. Sure is an expensive paperweight if it doesn't work...

redmgicUSER8 said:
Hey, so I have the same problem as you. I was installing the patched boot.img file when I rebooted, but there was no magsik app. After I tried to flash the same file again, except I put in some vbmeta file because some website said so, now my phone's files are corrupted. I got into fastboot mode and put through recovery mode, and did a data wipe and one final reboot, but even that did work because it said my phone is corrupt. The last thing I will try is to install TWRP, remove the old data, and install the update to restore the previous ROM files. I'll let you know if anything works. Just try ur methods and let me know if they worked. Sure is an expensive paperweight if it doesn't work...
Click to expand...
Click to collapse
did anything happen?

Stusick said:
Did anything happen?
Click to expand...
Click to collapse
Nothing yet... I'm trying to contact the support team. They can only do so much remotely

i have this error also what should i do?
the phone not boot up
the red warning are stuck

yakir150 said:
i have this error also what should i do?
the phone not boot up
the red warning are stuck
Click to expand...
Click to collapse
Your boot loader must be unlock
Reboot to recovery, choose English when you see "Wipe data" type
adb reboot sideload
Once your phone boots into sideload mode (When you see the two error line at the bottom of the screen) type
adb sideload NX729J-update.zip
When the transfer is successful ( with a transfer of 2.0 display) you can wipe the data twice with the first and second options and reboot the phone. If you are lucky, the phone will boot

[email protected] said:
Your boot loader must be unlock
Reboot to recovery, choose English when you see "Wipe data" type
adb reboot sideload
Once your phone boots into sideload mode (When you see the two error line at the bottom of the screen) type
adb sideload NX729J-update.zip
When the transfer is successful ( with a transfer of 2.0 display) you can wipe the data twice with the first and second options and reboot the phone. If you are lucky, the phone will boot
Click to expand...
Click to collapse
okay i try it and still no luck the same problem

yakir150 said:
okay i try it and still no luck the same problem
Click to expand...
Click to collapse
Download global V3.19 rom from: https://rom.download.nubia.com/Europe&Asia/NX729J/V319/NX729J.zip
Download QPST and QFIL flash tool from: https://www.mediafire.com/file/220h5xaxi1gd55m/QPST_2.7.496.zip/file. Install the driver (provided in the download) and these two programs.
You could then flash this rom V3.19 using QFIL flash tool. If you can flash this rom successfully your phone will work.

[email protected] said:
Download global V3.19 rom from: https://rom.download.nubia.com/Europe&Asia/NX729J/V319/NX729J.zip
Download QPST and QFIL flash tool from: https://www.mediafire.com/file/220h5xaxi1gd55m/QPST_2.7.496.zip/file. Install the driver (provided in the download) and these two programs.
You could then flash this rom V3.19 using QFIL flash tool. If you can flash this rom successfully your phone will work.
Click to expand...
Click to collapse
my phone is eu and using 4.18
can i use 3.19?
it's ok?

yakir150 said:
okay i try it and still no luck the same problem
Click to expand...
Click to collapse
For QFIL, use Flat Build and in the configuration use ufs. Good luck!

yakir150 said:
my phone is eu and using 4.18
can i use 3.19?
it's ok?
Click to expand...
Click to collapse
Your version V4.18 will be replaced by V3.19. This V3.19 version can be flashed through edl mode. I could not find V4.18 in this format. The two roms are very similar. They are both global roms.

[email protected] said:
Your version V4.18 will be replaced by V3.19. This V3.19 version can be flashed through edl mode. I could not find V4.18 in this format. The two roms are very similar. They are both global roms.
Click to expand...
Click to collapse
okay i will try and let you know
thank you very much

yakir150 said:
okay i try it and still no luck the same problem
Click to expand...
Click to collapse
If QFIL does not work, you need to do side load the rom multiple times again then it might work!

turn off the red rm8 notification (Your device is broken. It is unreliable and may not work)
- enter command on PC: adb reboot "dm-verity enforcing"
- on phone for rooted device with termux: reboot "dm-verity enforcing"

izsdeaman said:
turn off the red rm8 notification (Your device is broken. It is unreliable and may not work)
- enter command on PC: adb reboot "dm-verity enforcing"
- on phone for rooted device with termux: reboot "dm-verity enforcing"
Click to expand...
Click to collapse
The command on PC shows "Too many arguments." The Termux one works. Thanks!

[email protected] said:
Your boot loader must be unlock
Reboot to recovery, choose English when you see "Wipe data" type
adb reboot sideload
Once your phone boots into sideload mode (When you see the two error line at the bottom of the screen) type
adb sideload NX729J-update.zip
When the transfer is successful ( with a transfer of 2.0 display) you can wipe the data twice with the first and second options and reboot the phone. If you are lucky, the phone will boot
Click to expand...
Click to collapse
Tahnk you very very very much.