Database Develop

Soft bricked N7000. How to?

Tried everything I could with Odin and phone still stuck in a start loop.
I was downgrading from checkROM to official firmware ZSLA2 with CWM (I wanted to keep ROOT, so I selected "Keep CF-Root kernel") due to stability issues, after restarting the phone got into the start loop.
I flashed with Odin official ZSLA2 with the same result (looped start). I flashed XXKKA (again looped start). During the flashing process, Odin says the flashing was successful. By the way, both ROMS are tar.md5 files.
I tried to remove the battery for over 30 minutes and charge it for 2 hours, tried re-partition in Odin (it's my understanding that with a stock rom, it creates a clean installation), but Odin fails to start the process.
What else can I do?
I am sorry if this has previously asked, but I've been searching for over 2 hours and nothing similar came. Somebody mentioned to use a PIT file in addition, but the other person who got his phone soft bricked didn't solve the problem either. As downloading a ROM is time consuming and I've got many problems with upload sites in china (cannot access to most of them), I would thank any help in regards this issue.

Sounds like your kernel isn't talking properly to your ROM.
A fresh start is your best bet. Flash a stock rom and kernel from Odin and reroot it with CF-Root.
What files are you putting into Odin? There should be a total of 4.
I'd also avoid the use of a .pit file. I haven't even seen the mention of one in all my time on the Note forum. I really don't think Samsung uses them the way they used to. (I used to have to flash one all the time when testing roms on the original galaxy tab.)

I am using official ROM N7000ZSLA2_N7000ZSLA2_N7000XLA4_HOME.tar.md5 into PDA and also tried ROM N7000XXKKA_N7000XEUKK3_N7000XXKK5_HOME.tar.md5, which I used successfully in the past to make root into my phone.
Does it really make a difference to flash 4 separate files instead of a full pack? Where can I find an official ROM with pda radio and kernel separated? Just untar the ROM?

btyork said:
I'd also avoid the use of a .pit file. I haven't even seen the mention of one in all my time on the Note forum. I really don't think Samsung uses them the way they used to. (I used to have to flash one all the time when testing roms on the original galaxy tab.)
Click to expand...
Click to collapse
Oh, they do come into the Note; I flashed the Beta ICS, and one of the things they mention is to use the PIT file for the 16GB version, instead of the 32GB that comes with the leaked ROM. Unfortunately I deleted that ROM, and donwloading it is painfully slow and also wouldn't necessarily solve my problem as I couldn't even make a phone call.

True - the .pit file can change the size of the partition data... But that's not your problem. If the .pit file was the problem - you'd boot, but have 0 storage space (or something else wonky pertaining to your disk size.)
Open the tar up and make sure it has all the files in it. Should be 5.
I've attached a screenshot of the 5 file names. Make sure they are all in the .tar you are flashing.

Even i had similar problem after flashing Stock ROM using Odin (PC). Only thing i did is just rebooted in recovery and Wipe/factory Reset and Wipe cache. everything went fine.

btyork said:
True - the .pit file can change the size of the partition data... But that's not your problem. If the .pit file was the problem - you'd boot, but have 0 storage space (or something else wonky pertaining to your disk size.)
Open the tar up and make sure it has all the files in it. Should be 5.
I've attached a screenshot of the 5 file names. Make sure they are all in the .tar you are flashing.
Click to expand...
Click to collapse
This are the files I am flashing:
Sorry, I am new user and still cannot post screen captures. I do have more than the 5 files.
In XXKKA I have:
Boot
Cache
Factoryfs
Hidden
Modem
param.lfs
Sbl
zImage
In ZSLA2:
Cache
Factoryfs
Hidden
Modem
zImage
btyork said:
Even i had similar problem after flashing Stock ROM using Odin (PC). Only thing i did is just rebooted in recovery and Wipe/factory Reset and Wipe cache. everything went fine.
Click to expand...
Click to collapse
I can only enter into Download mode, not recovery mode.
Odin is full wipe, right? What the hell am I doing wrong?

N7000xxla1_n7000oxala1_oxa
http://hotfile.com/dl/141060546/b0c7420/N7000XXLA1_N7000OXALA1_OXA.rar.html
download this firmware, it's gonna take awhile but worth a try..
try flashing this rom using PC odin.
pit: Q1_20110914_16GB.pit
pda: CODE_N7000XXLA1_CL868264_REV02_user_low_ship.tar.md5
phone: MODEM_N7000XXLA1_REV_05_CL1093393.tar.md5
csc: GT-N7000-MULTI-CSC-OXALA1.tar.md5
check re-partition, auto reboot, F. reset time.
let me know if it works!
Han

choihan06 said:
download this firmware, it's gonna take awhile but worth a try..
try flashing this rom using PC odin.
pit: Q1_20110914_16GB.pit
pda: CODE_N7000XXLA1_CL868264_REV02_user_low_ship.tar.md5
phone: MODEM_N7000XXLA1_REV_05_CL1093393.tar.md5
csc: GT-N7000-MULTI-CSC-OXALA1.tar.md5
check re-partition, auto reboot, F. reset time.
let me know if it works!
Han
Click to expand...
Click to collapse
Well, I finally managed to get my phone back. I was getting a lot of corrupted ROMS. I couldn't download your ROM as well; I managed to install the Beta ICS 4.0.3 which comes with a PIT for repartition, as I think the problem was that my booting partition was screwed.
Problem now is: that rom screws the phone and the keyboard, but at least I have my phone back.
Thank you

mrfan said:
Well, I finally managed to get my phone back. I was getting a lot of corrupted ROMS. I couldn't download your ROM as well; I managed to install the Beta ICS 4.0.3 which comes with a PIT for repartition, as I think the problem was that my booting partition was screwed.
Problem now is: that rom screws the phone and the keyboard, but at least I have my phone back.
Thank you
Click to expand...
Click to collapse
I have just recently dowloaded and installed the rom without problem. What do you mean by corrupted rom?
Sent from my GT-N7000 using xda premium

I too bricked my phone but after reading this guide (ABD wouldn't recognise my device so I couldn't follow it) I understood the partitions had become messed up.
I read somewhere about the PIT files.
I ODINed the ABYSS Kernal and PIT (Q1_20110914_16GB-patched) for my 16gb n7000 ticked the repartition box. It booted into CWM recovery and I used the restore and bingo.

Fix The problem
I had the same problem, the device got into start loop. JUST DO A FULL WIPE..! and the device should start normally. I worked for me.... :good:
Sent from my GT-N7000 using xda premium[/QUOTE]

[Q] Is my GT-I8190L unflashable?

Hi good day,
I have a Samsung S3 Mini Latin version and i was wondering if it can't be flashed because i tried multiple flash files. I used Odin, Z3X and FuriousGold and it didn't flash. It said successful but when the phone rebooted it came back to the same data it had. Nothing changed at all. Can someone help me on this.
Thanks! :good:

Vision Electronics said:
Hi good day,
I have a Samsung S3 Mini Latin version and i was wondering if it can't be flashed because i tried multiple flash files. I used Odin, Z3X and FuriousGold and it didn't flash. It said successful but when the phone rebooted it came back to the same data it had. Nothing changed at all. Can someone help me on this.
Thanks! :good:
Click to expand...
Click to collapse
what files you flash?

I flashed the Pit, Bootloader, PDA, Modem and CSC and still nothing it just returns to the previous data the phone had.

Vision Electronics said:
I flashed the Pit, Bootloader, PDA, Modem and CSC and still nothing it just returns to the previous data the phone had.
Click to expand...
Click to collapse
you use the odin v3.09?

KwstPap said:
you use the odin v3.09?
Click to expand...
Click to collapse
I used Odin v1.83, v3.07, v3.09 & v3.10.0. Still got the same result i don't know if the phone needs to be wiped completely but i'm afraid the phone will die on me.

With Odin, all I can flash is a stock rom and a rooted stock rom. Any stock rom with recovery in it would fail. Once I got a root stock rom on it, I used a terminal app to write TWRP to the recovery block. From there I could flash other roms. Back everything up that is unique to our phone like IMEI as soon as you can just in case. Make sure you have copies elsewhere like your pc. You might wipe your internal, external sdcard or both by accident. I'm stuck with f2fs on my system drive, no way to reformat and no way to flash a rom that can use f2fs.
So the recovery block is locked and I think bootloader and possibly another area as well. Blocked as far as Odin, but not from the phone once it is running.

Odin Stuck On NAND Write Start?

I rooted my phone and wanted to flash back to stock so I can update with the OTA and re-root, but I downloaded the zip for the AT&T tar files and everything seemed to pass MD5 checks and went okay, but as soon as I hit Start, the program just continues to say NAND Write Start for over 20 minutes, and won't flash, how do I go about re-trying this without bricking my device? It's still plugged in atm in download mode.

What version of Odin are you using? I had this problem because I had v3.10 and the s6 is not compatible with that version, you have to have v3.10.6.

Mine did that, I closed odin, reopened, put each .md5 file in right section (AP in AP, BL in BL, CSC in CSC, ect) and it worked

If Odin is having trouble flashing to your phone. Here is some simply tips and tricks to try.
1. Try flashing everything except for the bootloader .
2. Try running Odin as admin.
3. Try upgrading to the newest Odin available.
4. If all else fails, open Samsung Kies, and go to emergency recovery, put your model # and serial # in, and it will flash your phone to stock for you, then you can try again.
5. Also make sure all of the correct drivers are installed for your phone, sometimes Windows can be bad about that. Try getting drivers from samsung directly.
6. Try a new USB Cable, as crazy as that is, I have had some not work, and others work fine.
7. Try a different USB Port on the PC, or restart the PC.
I hope this helps.

I tried just flashing the ROM and CSC and it flashed just fine, I left out the CP file, what is that? Everything seems fine just flashing the ROM and CSC, but do I need to flash the CP file too, for anything?

CSC is the consumer software customization and is specific to geographical region and carriers. It contains the software packages specific to that region, carrier branding and also APN settings for data connection, MMS etc for your service provider.
I hope this helps

I didnt get it. Do you mean to put each .md5 file in all sections? ? Please help me
_Dennis_ said:
Mine did that, I closed odin, reopened, put each .md5 file in right section (AP in AP, BL in BL, CSC in CSC, ect) and it worked
Click to expand...
Click to collapse
Please help me out. I am having same problem NAND WRITE stuck.

Solved
Thanks everyone for your post. But what I did is, just downloaded the Odin v3.10.6......that worked with S6. And I guess S6 is not compatible to other earlier versions of odin. So better try with Odin v3.10.6.

Nand write start fail solved
I have solved using Odin3 v3.10.7 with firmware VZW-G920VVRU4BOK7-20151211140939 and Windows 7 for Galaxy S6 SM-G920V

NAND stucked
kishor1995 said:
Thanks everyone for your post. But what I did is, just downloaded the Odin v3.10.6......that worked with S6. And I guess S6 is not compatible to other earlier versions of odin. So better try with Odin v3.10.6.
Click to expand...
Click to collapse
can u tell the steps u did? to do it

Help
I am having the same issue and I have done everything suggested here but still is NAND fail. Any ideas

bonniegertz said:
I am having the same issue and I have done everything suggested here but still is NAND fail. Any ideas
Click to expand...
Click to collapse
Were you finally able to get it to work?

Its working!
Zoide_ said:
Were you finally able to get it to work?
Click to expand...
Click to collapse
Yes, I gave up but a friend of mine found a thread that talks about using Kies to bring it back to factory default. You need to know the serial # and IMEI # If you can find this information, you can reset it using Kies.

Had the same problem. Used Odin 3.10.6
But before all this, I connected phone with debugging enabled in windows and authorized it, the problem never resurfaced

SM-920T stuck on logo screen

I messed up
Tried to unroot my N5 and ended up bricking it.
I dont have original backup (pc formatted) so i tried flashing another 920T ROM to it but it keepos failing.
When i flash Noble_Kernel_Auto-Root and philz_touch i get a pass on each. Just trying differentways to get in.
I try sideloading and adb says success but nothing happens on the phone.
I've already done a factory reset so nothing to save here, I just want to get it up and running.
I've done quite a bit of reading on here but i know i need help.
Using Odin 3.09, 3.10.6 &.7
Any help appreciated.

BallheadTampa said:
I messed up
Tried to unroot my N5 and ended up bricking it.
I dont have original backup (pc formatted) so i tried flashing another 920T ROM to it but it keepos failing.
When i flash Noble_Kernel_Auto-Root and philz_touch i get a pass on each. Just trying differentways to get in.
I try sideloading and adb says success but nothing happens on the phone.
I've already done a factory reset so nothing to save here, I just want to get it up and running.
I've done quite a bit of reading on here but i know i need help.
Using Odin 3.09, 3.10.6 &.7
Any help appreciated.
Click to expand...
Click to collapse
Why didn't you use the recovery to make a backup so you could easily restore it when something like this happens?
Download the correct firmware for your phone and then extract it so all of the files are able to be put in the slots on Odin (BL, PA etc etc) because you have to flash them like that now.

MrMike2182 said:
Why didn't you use the recovery to make a backup so you could easily restore it when something like this happens?
Download the correct firmware for your phone and then extract it so all of the files are able to be put in the slots on Odin (BL, PA etc etc) because you have to flash them like that now.
Click to expand...
Click to collapse
Thanks for the reply. Newbie dumbass move i guess. still learning.
Question...when i extract the files, will i have to load them individually to their correct slots or do i just select one file and it auto populates ?
On another note, i managed to sideload a zip just now but nothing came of that.

BallheadTampa said:
Thanks for the reply. Newbie dumbass move i guess. still learning.
Question...when i extract the files, will i have to load them individually to their correct slots or do i just select one file and it auto populates ?
On another note, i managed to sideload a zip just now but nothing came of that.
Click to expand...
Click to collapse
You have to put them all in the respective slots individually but at the same time so they flash 1 after the other..
Try getting the firmware from here.
https://samsung-firmware.org/model/SM-N920T/
Also, follow my guide here but use your firmware and not Verizon!
http://forum.xda-developers.com/ver.../downgrade-to-lollipop-5-1-1-verizon-t3368250

MrMike2182 said:
You have to put them all in the respective slots individually but at the same time so they flash 1 after the other..
Try getting the firmware from here.
https://samsung-firmware.org/model/SM-N920T/
Also, follow my guide here but use your firmware and not Verizon!
http://forum.xda-developers.com/ver.../downgrade-to-lollipop-5-1-1-verizon-t3368250
Click to expand...
Click to collapse
Thank you.
Ill be back (Schwarzeneggar voice)

BallheadTampa said:
Thank you.
Ill be back (Schwarzeneggar voice)
Click to expand...
Click to collapse
Ok, so I'm back......after trying several things which i'll list step by step for someone else who may be frustrated
I got the zip you linked to but i couldn't get the individual files for loading. all i saw was N920Txxxx.md5 and it kept failing when i hit start. (was loading it in AP)
I then deleted the .md5 extension and it became a .tar in Winrar format.
I extracted the files and got the sboot.bin to load in CP, this got a PASS.
Still stuck on logo after reboot.
Next i loaded the .tar file in CSC and Voila ! Wrote, got PASS, phone rebooted and now works fine.
My hat off to you MrMike2182 :good:
Now i'm going to look up how to clear the Knox counter.

[SOLVED ] HELP!!! Lost IMEI & Hard bricked Note =8 SM-N950F/DS

HELP!!! Lost IMEI & Hard bricked Note 8 SM-N950F/DS.
I flashed back my Note8 via Kies3 to stock rom, while updating the process got stuck at 24%. I left it overnight but the phone kept looping to the Installing Update screen then to recovery and on and on.
Then I flashed TWRP recovery through odin and wiped dalvik cache, cache, data and factory reset. The same thing kept on happening but instead of stock recovery it now ends up on TWRP recovery. Then I flashed dm-noverity. After that the phone booted up but there is no IMEI and phone signal. Please help.

mohiminul said:
HELP!!! Lost IMEI & Hard bricked Note 8 SM-N950F/DS.
I flashed back my Note8 via Kies3 to stock rom, while updating the process got stuck at 24%. I left it overnight but the phone kept looping to the Installing Update screen then to recovery and on and on.
Then I flashed TWRP recovery through odin and wiped dalvik cache, cache, data and factory reset. The same thing kept on happening but instead of stock recovery it now ends up on TWRP recovery. Then I flashed dm-noverity. After that the phone booted up but there is no IMEI and phone signal. Please help.
Click to expand...
Click to collapse
Hey. Try download your phone firmware from Sammobile the correct make N950F then use Odin to flash the firmware.
http://www.**********.com/download-odin-tool-for-samsung-galaxy-devices-all-versions/
Hope this helps
---------- Post added at 03:43 PM ---------- Previous post was at 03:41 PM ----------
AwesomeARC said:
Hey. Try download your phone firmware from Sammobile the correct make N950F then use Odin to flash the firmware.
http://www.**********.com/download-odin-tool-for-samsung-galaxy-devices-all-versions/
Hope this helps
Click to expand...
Click to collapse
Try this link
https://m.wikihow.com/Recover-a-Bricked-Samsung-Galaxy
Hope it helps

AwesomeARC said:
Hey. Try download your phone firmware from Sammobile the correct make N950F then use Odin to flash the firmware.
http://www.**********.com/download-odin-tool-for-samsung-galaxy-devices-all-versions/
Hope this helps
---------- Post added at 03:43 PM ---------- Previous post was at 03:41 PM ----------
Try this link
https://m.wikihow.com/Recover-a-Bricked-Samsung-Galaxy
Hope it helps
Click to expand...
Click to collapse
Brother I have tried the above method as per your suggestion but no result.

mohiminul said:
Brother I have tried the above method as per your suggestion but no result.
Click to expand...
Click to collapse
Try
https://www.fonepaw.com/bricked/fix-bricked-android-phone.html

You need Combination file to fix it

lost emei
this happened to me. I lost imei and could not make calls. what network were you on. I downloaded software for that network from sammobile and installed via odin, the imei returned and I was able to make calls again. I think what happened in my case was I rooted phone and put a rom on it. in aroma I selected t mobile America so it installed the file for that. I was on o2. my phone was unlocked. it did not recognise my simcard

Flash different modems
Hi
It has happened to me too many times with different phones including note 8
Just flash different modems and bootloaders to find the proper one.
androidfilehost .com/?w=files&flid=221868
*:Remove the space bofore .com
You can use both odin and twrp but if you want to stay stocked try odin mode.
If none of the above files worked for you look for other modems.

Odd that you can connect note 8 to kies3.. and not switch..
Sent from my SM-N950F using Tapatalk

I have literally tried everything. No results . I have possibly narrowed down the problem. My bootloader (OEM) is locked. If it was unlocked I could have flashed TWRP and then dm-verity no encrypt mod. Anyone with any suggestions. @holifo I got hold of a few combination files but none of them seems to boot beyond the screen FACTORY BINARY.

mohiminul said:
I have literally tried everything. No results . I have possibly narrowed down the problem. My bootloader (OEM) is locked. If it was unlocked I could have flashed TWRP and then dm-verity no encrypt mod. Anyone with any suggestions. @holifo I got hold of a few combination files but none of them seems to boot beyond the screen FACTORY BINARY.
Click to expand...
Click to collapse
Have you tried this one COMBINATION_FA71_N950FXXU1AQK2
While flashing combination file you need to flash HOME_CSC_OXM with it

mohiminul said:
I have literally tried everything. No results . I have possibly narrowed down the problem. My bootloader (OEM) is locked. If it was unlocked I could have flashed TWRP and then dm-verity no encrypt mod. Anyone with any suggestions. @holifo I got hold of a few combination files but none of them seems to boot beyond the screen FACTORY BINARY.
Click to expand...
Click to collapse
Jtag

holifo said:
Have you tried this one COMBINATION_FA71_N950FXXU1AQK2
While flashing combination file you need to flash HOME_CSC_OXM with it
Click to expand...
Click to collapse
Flashed COMBINATION_FA71_N950FXXU1AQK2 Factory binary from 2 sources along with HOME_CSC_OXM. No improvement. :crying:

so your phone is soft bricked. Its less of an issue since you have access to:
-recovery
-dl mode
go to updato.com and grab about 3 different stock firmwares.
1-the oldest one compatible with your phone you can find. forget about your region just be sure its an early FW and its for N950F. f or ds dosent matter.
2-again same as above but try one from south America.
3- same as #1 but from france or north west europe region.
before flashing, enter recovery and wipe data and cashes.
after wipe dont let the phone boot, have it go straight to DL mode.
now use latest odin and flash the firmwares above. if one of the flashes fail in odin Check your cables and usb port if any of the firmware flashes get stuck or give errors. Be sure to flash all BL AP CP and CSC files. for csc I think HOME csc has the pit file so you might also want to try repartition/bootloader update option if nothing else works. Since your phone is probably out of warranty by now.( might want to check if you can simply get it fixed before trying anything of the above first)
edit:
i saw you said having used kies 3 to do the emergency recovery. Im not sure how that were possible. do you mean smartswitch? if you have not used it, then go dl it and do the recovery from smartswitch. I dont even think kies support the note 8.

Ask him - https://forum.xda-developers.com/an...x-box-free-t3648947/post73222755#post73222755

mohiminul said:
Flashed COMBINATION_FA71_N950FXXU1AQK2 Factory binary from 2 sources along with HOME_CSC_OXM. No improvement. :crying:
Click to expand...
Click to collapse
And this file is flashed via odin til the end - with green PASS? Strange.
Hi mate, i know your feelings.
Ok, i just can tell about my issue. I was on a QK6 custom rom with a QKG bl/modem and fell back in jail So i had to flash stock but only the AP (QK6 bc QKG was at work :angel and CSC file. It booted up with the data of the custom rom and worked quite good. Except the gallery. So i decided to flash the QK6 bl/modem. The flash with odin crashed at the bootloader part. The phone booted without connections, no imei, no baseband...an exclusiv paperweight.
I tried a lot all a disaster. I searched for imei repair with the intencion to pay a lot of money but nothing. Even imei gurus said it's impossible for now to fix the imei for the note 8 with knox 0x1 by software.
Last thing i thought before i went crying to bed was the incomplet flash of the bootloader. So i downloaded over night the whole QKG package and flashed it in the morning.
AND all was fine again. I think the culprit is the Bootloader you can't downgrade from QKG. In the Iron Rom thread are the same issues after flashing the QK6 Bootloader with the rom over a QKG bootloader - all have lost there imei and baseband. They also fixed it than by flashing QKG BL (and modem).
This was my story and i hope it would help to fetch your problem.

I have same problem with your case, its made me sick 1 day but here is my success solution worked like charms !!
1. Download newest stock firmware via SAMFIRM ( for me i used XXVN code) extract it you will have AP and CSC using on this case
2. Download BL and CP via this link: (remove space before .com) You will have BL and CP
androidfilehost .com/?w=files&flid=244051
3. Open Odin chose BL, CP download from Androidfilehost. AP and CSC form stock firmware
Flash them and your Note will be back !! Reply me if u success !!
Ps: This case will upgrade ur blootloader to BRA2
And i heard that cant be rooted again, however my Note 8 is undead so im gonna sell it away better than bricked
Good luck from VietNam

Nice !!!! Its worked !! after i got check fail device 3, binary 2. I could flash ap,cp,csc but BL so now my Note is back to stock
Cheer

mohiminul said:
HELP!!! Lost IMEI & Hard bricked Note 8 SM-N950F/DS.
I flashed back my Note8 via Kies3 to stock rom, while updating the process got stuck at 24%. I left it overnight but the phone kept looping to the Installing Update screen then to recovery and on and on.
Then I flashed TWRP recovery through odin and wiped dalvik cache, cache, data and factory reset. The same thing kept on happening but instead of stock recovery it now ends up on TWRP recovery. Then I flashed dm-noverity. After that the phone booted up but there is no IMEI and phone signal. Please help.
Click to expand...
Click to collapse
Does the imei appear as uknown? or a bunch of zeros?

THORMUNZ said:
Does the imei appear as uknown? or a bunch of zeros?
Click to expand...
Click to collapse
The post you are responding to is 5 months old !
Just saying...
Sent from my Galaxy Note 8 using XDA Labs

THORMUNZ said:
Does the imei appear as uknown? or a bunch of zeros?
Click to expand...
Click to collapse
It used to come as unknown. I figured out a solution. Used https://drive.google.com/file/d/1qI8L3y1GkSlQu_Q03dsZr0DfBkb0ZRcs/view?usp=sharing this combination rom and this eng_boot https://1drv.ms/u/s!Aq07ytE0dzjkhv0iFXiB216r10pAvw
my phone booted to factory repair mode and then just went to IME option and dialed *06#