What Can Something to Help Me? Firmware S3 Mini Me I8190DXALL3 / I8190OLBALL4.Saya Got Problems With Mini S3 / GT-I8150. A Time I Make Mistakes Flash Rom. So the problem appears
1. Baseband Version
AP: I8190DXALL3
CP: XXXX << ==== How Do I Get It Back???
CSC: I8190OLBALL4
2. EFS Formatted
3. Can not Lock Screen (Pattern, PIN, etc.).
4. Wizard Mode Not Appear (The First Time Wizard Appears To Perform Settinga Language, Date and Time, Sing In Account, Etc.)
5. Information Factory Test Appears On Screen (Like That I Attach Images)
How To Solve Such Problems??? Or How to Full Flash Back To Factory Stock Firmware???
I Have Tried Doing Flash Stock Firmware (I8190DXALL3_I8190OLBALL4_HOME.TAR.md5) Via Odin On PDA Or File Using Goldenxx.PIT and Doing Tick Repartition But It's Not Succeed.
Sorry If I'm Not Good English. :angel:
faisalxp said:
What Can Something to Help Me? Firmware S3 Mini Me I8190DXALL3 / I8190OLBALL4.Saya Got Problems With Mini S3 / GT-I8150. A Time I Make Mistakes Flash Rom. So the problem appears
1. Baseband Version
AP: I8190DXALL3
CP: XXXX << ==== How Do I Get It Back???
CSC: I8190OLBALL4
2. EFS Formatted
3. Can not Lock Screen (Pattern, PIN, etc.).
4. Wizard Mode Not Appear (The First Time Wizard Appears To Perform Settinga Language, Date and Time, Sing In Account, Etc.)
5. Information Factory Test Appears On Screen (Like That I Attach Images)
How To Solve Such Problems??? Or How to Full Flash Back To Factory Stock Firmware???
I Have Tried Doing Flash Stock Firmware (I8190DXALL3_I8190OLBALL4_HOME.TAR.md5) Via Odin On PDA Or File Using Goldenxx.PIT and Doing Tick Repartition But It's Not Succeed.
Sorry If I'm Not Good English. :angel:
Click to expand...
Click to collapse
You flash wrong firmware?
Is your phone I8190 or what?
How you tried repartition? What file it was? Errors?
After stock firmware you have to make hard reset(factory reset) that wipe all older files from phone. So back up is needeed if wanna save.
I can give you that WIPE files if wanna. Use with ODIN(pda)
I've had this problem, I solved it by formatting /modem via CWM and flashing modem.bin via Odin in PDA.
But I still have this CP: XXXX issue.
Benzonat0r said:
I've had this problem, I solved it by formatting /modem via CWM and flashing modem.bin via Odin in PDA.
But I still have this CP: XXXX issue.
Click to expand...
Click to collapse
Why you flash just modem.bin? Was it for you country??! It is region -code dependies(country and what telephone network phone can use....) So your problem XXXX means, there is not any....
Did you hard reset after flashing?
Because I flashed a bootloader in there accidentally it was a typo really. So no matter what I did modem didn't work, so I had no choice but to format /modem and flash everything all over again. I think I deleted a file needed to recognize my Baseband version, the phone works normally it just doesn't show any Baseband version.
How To Full Flash Back To Factory Stock Firmware
S3miniFin said:
You flash wrong firmware?
Is your phone I8190 or what?
How you tried repartition? What file it was? Errors?
After stock firmware you have to make hard reset(factory reset) that wipe all older files from phone. So back up is needeed if wanna save.
I can give you that WIPE files if wanna. Use with ODIN(pda)
Click to expand...
Click to collapse
Yes My Phon Is GT-I8190......
Yes I'm Try Repartition But Not Fix The Problem, No Error In Flasing Firmware
I'm Trying Firmware I8190DXALL3_I8190OLBALL4_HOME.TAR.md5 From Indonesia, Because I'm Live In Indonesia
I'm Try All, WIPE.tar.md5 or PARM.tar.md5 (From http://forum.xda-developers.com/showthread.php?t=2030282) Using To Odin and I Try Reset To factory Reset But ALL Not Working.
Note :
Initially I Tried Doing Root And Succeed, Then I Tried Installing CWM Bootloop But, I Already Tried Reset To Factory (Wipe from CWM) But Not Succeed .. After I Serch at XDA Forums I Get File Recovery.tar.md5 (But Different Region) From A Forum GT-I8190. I Tried Odin Flash Via The result Bootloop PDA And Missing, But CP: XXXX Already Being So .... truz I Try Search And Finding Ways To Fix EFP Tools Professional (I Read forum Fixing Problems That Make CP: XXXX Ways restor ) But When I Try Not Succeed And Me One Click on the Format button EFS EFS Before Doing restor .... eventually all Issues My Name Appears In First Post. Furthermore, I Try Download Stock Firmware For Indonesia Namely I8190DXALL3_I8190OLBALL4_HOME.TAR.md5 and I try to Find File goldenxx.PIT, I Try Flash Using ODIN Repartition Checking Using Goldenxx.PIT And using file .. After the Finish Installing Flash Appear Loading Firmware, TPI Tiba2 stop on the way and Tiba2 Sign in to CWM, Emergent statements Missing More Like This "Installing File MD5 Not Suitable, if you'll Continue Installation? Me Try Select" Yes "But After That Go To CWM" I truz My Try Choose Reboot But Can not, Even Log Into CWM Continues (Though I'm not Pressing Power + Menu + UP voume. Boot). Initially One How Can I Boot with Normal (Not Automatically Sign Into CWM) That Make Flash With Recovery.Tar.Md5 Which I Mention Above.
Benzonat0r said:
I've had this problem, I solved it by formatting /modem via CWM and flashing modem.bin via Odin in PDA.
But I still have this CP: XXXX issue.
Click to expand...
Click to collapse
Thank Benz For Information, I Will Try ... Previous I'm Just Trying To mark Repartition And Flash Modem.BIN Of Odin But I Do Not Attempt preemptively Format Via CWM. I'll try it soon. Thank you
S3miniFin said:
Why you flash just modem.bin? Was it for you country??! It is region -code dependies(country and what telephone network phone can use....) So your problem XXXX means, there is not any....
Did you hard reset after flashing?
Click to expand...
Click to collapse
No problem I'm Not Only That, I'm also not intentionally Formatting EFS EFS Of Professional Tools, So Emerging Display In Which I Attach Pictures And Now I Can not Lock Screen (Pattern, PIN, Face Unlock, Etc).
I also Already Tried Flash Firmware I8190DXALL3_I8190OLBALL4_HOME.TAR.md5 (My Region) In PDA And Using File goldenxx.PIT and Ticking Repartition .... But Not Succeed Such Problems Still Appear While I Already Do WIPE Data and Cache (Factory Reset).
What There Ways To Hard Reset addition That I mentioned above??? Please explanation Because I Still A Beginner
Related
On first boot I get
Can not mount / dev/block/stl10 (Invalid argument)
copy_dbdata_media: Can not mount DBDATE
Not Prepared your storage yet, please use UI menu for format and reboot actions
default copy content failed half
wiping / data cache and Does not Seem To fix anything.
Format sdcar unresponsive
HELP any occurrence and brick my phone
criskelo said:
On first boot I get
Can not mount / dev/block/stl10 (Invalid argument)
copy_dbdata_media: Can not mount DBDATE
Not Prepared your storage yet, please use UI menu for format and reboot actions
default copy content failed half
wiping / data cache and Does not Seem To fix anything.
Format sdcar unresponsive
HELP any occurrence and brick my phone
Click to expand...
Click to collapse
Go to Download Mode and flash ROM XWJM8 with pit512 and Re-Partition,after flash XXJPM with pit803 and without Re-Partition-this help
sardor said:
Go to Download Mode and flash ROM XWJM8 with pit512 and Re-Partition,after flash XXJPM with pit803 and without Re-Partition-this help
Click to expand...
Click to collapse
Fixed in a while I explain
My solution
With Odim 1.3, pit 512,
in my case JH2 I9000T GT
But for Europe JM8
Mark Re-partition, phone EFS clear and Phone bootloader Update
Then start
This process started well
JPM Process
Then uncheck re-partition, phone EFSclear and Phone Bootloader Update
JPM Pit 803 and firm JPM
Start
To enjoy
Thanks
criskelo said:
Then uncheck re-partition, phone EFSclear and Phone Bootloader Update
Click to expand...
Click to collapse
Is it normal for T model, or you just use weird and dangerous settings for fun?
Wiping EFS can lead to test-imei number and broken product code. Be sure you haver a backup of that folder before wiping that.
criskelo... I tried this and I didn't get anywhere :/
I had the same issue and it took me 2 hours to resolve (with a lot of pain, lol).
I've simply flashed the XWJM8 version using odin 1.3, no pit file and HENCE no repartition ticked.
It then booted to recovery console, because there was another error (can't remember which one cause I was too excited).
Anyway I did a wipe, cash clear and reformat SD card at the menu and let it boot.
After that I have flashed the latest version XXJPY also without PartitionInformation Table. (PIT). Then all the wipe and format stuff again.
I have now to go from scratch to setup anything again, but hey, at least my phone is alive again.
Some additional info. I also had that connection symbol on the screen with exclamation mark and triangle....so I thought I was done (due to trials with pit 512 which hung), but after removing battery and some trials I was able to enter download mode again....
Why happened that? I DON'T KNOW! I simply wanted to reflash the XXJPY stock rom, this time with pit512 and it lead to the topic of this thread!!!
This su**ed a lot, I didn't even modify something before!!!!
So: Less is even more! Don't fiddle with EFS and bootloader options it worked for me even without a pit!
Thanks to sardor for the initial idea, the XWJM8 seems to be a fixing rom for that when used properly, anyway to load a pit without to tick repartition is not a useful setting!
Well I was a long time reader at this great forum, IMHO the best regarding phone stuff, because there is the most useful knowledge shared.
I hope my first post will save other phones as well from sending it to repair.
Thanks I'm happy again..(let's see how long it'll last..lol...)
bricked my samsung galaxys and recoverd it
Hi I had exact same problem I totally bricked my i9000 Australian Optus version
I used
I9000DTJG4 firmware Australian Optus
With pit 512
And odin3 v1.3
Got all the files from
samfirmware . com / WEBPROTECT - i9000 . htm
Had to sign up but it’s free
However following criskelo's advice I unchecked the re partion box in odin
Even though the site above tells u to check it
And it worked
Thanks for everyone’s help on this thread.
Without you I would have had an expensive paper waited
Also the reason I got here in the first place as because I messed around with lag fix in clockwork recovery when I don’t know anything about it.
I was lucky this time but it’s really not worth playing around with things you doing understand.
sardor said:
Go to Download Mode and flash ROM XWJM8 with pit512 and Re-Partition,after flash XXJPM with pit803 and without Re-Partition-this help
Click to expand...
Click to collapse
I was messing with Darky's Rom which alway cause problems for me and found myself in the same situation as the first post.
What worked for me.
JM8 (2 files = code to PDA - Modem to PHONE) + Repartition + 512pit
after reset different error so goto download mode again then:
JPM + 803pit
Default OS reconfigures, Thank Fook
Awesome, thanks buddy! I have spent too much time trying to fix this phone and it all totally pays off now!
Here is the fix for the Bell firmware:
Background info: I orginally tried the Lagfix and bricked my phone, this is how I finally fixed it...
1. Using Odin v1.82
Put Phone in download mode
Use PDA: I9000UGJH2
Use Phone: Modem.bin
(both files came from samfirmware, I9000UGJH2 download)
Use: 512.pit(also from samfirmware at the bottom of the i9000 page)
Check Re-Partition, Auto-reboot, F. reset time, phone EFS clear and Phone bootloader update. I know everyone above says don't but I tried their way first and it didn't work, I would recommend you do try their way first and if no results try mine.
2. Using Odin v1.82
Put Phone in download mode
Use PDA: I9000UGJL2
Use 803.pit
Check only Auto-reboot, F. reset time
Good luck! I hope you do your happy dance like I did!!
crazycanuckeh said:
Awesome, thanks buddy! I have spent too much time trying to fix this phone and it all totally pays off now!
Here is the fix for the Bell firmware:
Background info: I orginally tried the Lagfix and bricked my phone, this is how I finally fixed it...
1. Using Odin v1.82
Put Phone in download mode
Use PDA: I9000UGJH2
Use Phone: Modem.bin
(both files came from samfirmware, I9000UGJH2 download)
Use: 512.pit(also from samfirmware at the bottom of the i9000 page)
Check Re-Partition, Auto-reboot, F. reset time, phone EFS clear and Phone bootloader update. I know everyone above says don't but I tried their way first and it didn't work, I would recommend you do try their way first and if no results try mine.
2. Using Odin v1.82
Put Phone in download mode
Use PDA: I9000UGJL2
Use 803.pit
Check only Auto-reboot, F. reset time
Good luck! I hope you do your happy dance like I did!!
Click to expand...
Click to collapse
hey how did it worked for you. Not working for me.
did you extracted the tar file? which file did you loaded into the pda tab then ?
Didnt worked for me at all
sardor said:
Go to Download Mode and flash ROM XWJM8 with pit512 and Re-Partition,after flash XXJPM with pit803 and without Re-Partition-this help
Click to expand...
Click to collapse
you saved my phone after me corrupting internal SD! just did my victory dance though hands still shaking a bit
Just thought I would add to what got my phone back running again after having the Can't mount DBDATA error. It's a bell I9000M.
Used Odin 1.3 , Flashed Darky's resurection per his instructions pulled battery once complete, went back into download mode and flashed stock JL2 with Odin , re-partition un-checked and no Pit file and after that my phone was running again.
You can find Darky's Resurection Here!
Can not find the link for the JL2 stock rom but it's in the general section somewhere.
the xxjpu version worked for me
tlick repartition
add 512 pit
tick and add pda
tick and add modem
tick and add csc
go to download mode
connect usb
press start
Need help with Fascinate
Hey guys, I've read the above posts but frankly it's above my skill.
Some how I ended up with the same message that the OP got.
Can someone walk me through the steps to completely fix my phone and get it back to bone stock?
I'm not familiar with PIT and other files. I need someone to hold me hand on this one...
cddt said:
I was messing with Darky's Rom which alway cause problems for me and found myself in the same situation as the first post.
What worked for me.
JM8 (2 files = code to PDA - Modem to PHONE) + Repartition + 512pit
after reset different error so goto download mode again then:
JPM + 803pit
Default OS reconfigures, Thank Fook
Click to expand...
Click to collapse
Was also messing around with darky. decided to go back to 9.5 for now. also got the error, then did what cddt said (thanks!!).
first flash - different error (something about CSC)
for second flash i used JS7 + 803pit + no repartitioning
worked flawlessly Thanks!
Stuck in boot loop
Samdroid_G_S said:
Just thought I would add to what got my phone back running again after having the Can't mount DBDATA error. It's a bell I9000M.
Used Odin 1.3 , Flashed Darky's resurection per his instructions pulled battery once complete, went back into download mode and flashed stock JL2 with Odin , re-partition un-checked and no Pit file and after that my phone was running again.
You can find Darky's Resurection Here!
Can not find the link for the JL2 stock rom but it's in the general section somewhere.
Click to expand...
Click to collapse
Hi,
I have bell sgs and I tried this and since then my phone is on boot loop. I can only go in download but not recovery. IT all started when I installed the boot loader for gingerbread...
Flashing Error - resolved
cddt said:
I was messing with Darky's Rom which alway cause problems for me and found myself in the same situation as the first post.
What worked for me.
JM8 (2 files = code to PDA - Modem to PHONE) + Repartition + 512pit
after reset different error so goto download mode again then:
JPM + 803pit
Default OS reconfigures, Thank Fook
Click to expand...
Click to collapse
Just followed this and it worked a treat thank you
Hi there,
I am having issues the same way. I am unable to do something. Can some explain me the procedure how to do it.
From where can i get the files.
Please help me out
Hi, I have a GSM Samsung Galaxy S here that is running CyanogenMod.
The phone is rebooting at random and getting stuck at the skateboarding CyanDroid during boot.
It still runs sometimes and I can flash other roms through clockwork or ROMManager.
How can I restore it to a factory ROM and firmware?
When I try to use *#1234# to find what firmware it has it, it says "Connection problem or invalid MMI code." does that code only work with stock firmware?
Any help or advice would be greatly appreciated.
Thanks,
ANKh
I would use Odin to reflash to a standard Samsung ROM and start again. Maybe first make a backup of all your data, because that will be lost (internal).
Ankhwatcher said:
Hi, I have a GSM Samsung Galaxy S here that is running CyanogenMod.
The phone is rebooting at random and getting stuck at the skateboarding CyanDroid during boot.
It still runs sometimes and I can flash other roms through clockwork or ROMManager.
How can I restore it to a factory ROM and firmware?
When I try to use *#1234# to find what firmware it has it, it says "Connection problem or invalid MMI code." does that code only work with stock firmware?
Any help or advice would be greatly appreciated.
Thanks,
ANKh
Click to expand...
Click to collapse
download the stock firmware from samfirmware.com .. then flash it using odin ..
Go back to stock (can download stock firmware's from sammobile.com) and then flash another rom it could be a problem from the rom itself
Remember to use .PIT file! and check that repartition is ticked.
Shame Heimdell can't also make an image ready for backup later too,
I'd prefer to do that than downloading from some server I've no clue where it's coming from and might do a megaupload at any point
Erakko said:
Remember to use .PIT file! and check that repartition is ticked.
Click to expand...
Click to collapse
What if I have the I9000M_JL2_JL2_JL2_JL2_UG_BMC.zip containing only the I9000UGJL2_homebinary_add_param.tar file?
Is there any need to tick the repartition option?
i think this is a PDA file and it would be ill advised to tick the repartition option.
But I just need to confirm before restoring from JB CM10
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]
I try to use sam fix tool to get my baseband (unknown) and sim cad imei fixed
i use the tool and choose baseband fix it boot into donwload mode and flash something
after that my note 9 stuck bootloop
i flashed stock frimware using odin and didnt work
i flashed combination file and also got bootloop
i can go to download mode
but whatever i do my phone stuck bootloop
plz need help plz guys
BUT I MADE A EFS BACKUB USING SCRIPT CMD IT CREAT A FLASH FILE CAN BE FLASHED USING ODIN VIA AP
BUT I CAN ACCESS IT RIGHT NOW BECASE I HAVE IT IN MY WORK
IS THAT ABLE TO HELP ME FIX THE PROBLEME[/COLOR]
Make you post readable for everyone using the dark theme and you might get more response.
What exactly did you flash with Odin and what happened, other than it didn't work?
willhemmens said:
Make you post readable for everyone using the dark theme and you might get more response.
What exactly did you flash with Odin and what happened, other than it didn't work?
Click to expand...
Click to collapse
I used a tool to fix baseband the tool reboot my phone into download mode and flash something
i try to boot my phone it get bootloop i try flash stock rom still bootloop
i flashed combination file still bootloop
i think the tool did something to efs partition
Did you complete a backup with TWRP?
willhemmens said:
did you complete a backup with twrp?
Click to expand...
Click to collapse
no i didint flash twrp my device not rooted
devil499 said:
no i didint flash twrp my device not rooted
Click to expand...
Click to collapse
You shouldn't have used any tool.
You could have easily recovered your unknown baseband by simply flashing your stock firmware.
Retry flashing the Stock firmware. But this time, do a wipe cache partition, wipe data/factory reset in recovery mode first.
Use the latest stock firmware that is available for your country/CSC.
If you can find a pit file, include that in odin flash with the stock firmware. Put a checkmark on the "repartition" option.
It's normal for the device to take 5-10 minutes or more during the initial boot.
Sent from my SM-N960F using Tapatalk
Good luck dude when the mention above most really suck having a bricked note 9
jaylence said:
You shouldn't have used any tool.
You could have easily recovered your unknown baseband by simply flashing your stock firmware.
Retry flashing the Stock firmware. But this time, do a wipe cache partition, wipe data/factory reset in recovery mode first.
Use the latest stock firmware that is available for your country/CSC.
If you can find a pit file, include that in odin flash with the stock firmware. Put a checkmark on the "repartition" option.
It's normal for the device to take 5-10 minutes or more during the initial boot.
Sent from my SM-N960F using Tapatalk
Click to expand...
Click to collapse
i have done that but didnt worked
plz help me
i didint find pit file for my device
n960f
HtcOnekid said:
Good luck dude when the mention above most really suck having a bricked note 9
Click to expand...
Click to collapse
i found this post https://forum.xda-developers.com/ga...ide-fix-n950f-efs-failed-to-mount-dm-t3831184
i beg you can you plz help understand it
Extract Stock firmware AP file (rename .md5 to .tar)
this i cant understand wich should i rename or what i do
Rename dqmdbg.img to efs.img (or smallest image must be smaller than 8000 KB). Extract Dqmdbg.img.lz4 so it’s just “Dqmdbg.img” and then rename it to efs.img and put that one in a tar. Other option is downloading a file that’s already made this way if your bootloader is binary 4, Saves you trouble of extracting / renaming: http://www.mediafire.com/file/589wuc...f/efs.tar/file (if you download this file just move onto number 3)
Add file new efs.img into tar archive.
Flash tar as AP file in odin + download mode
Reboot download mode
Flash Combination with odin + nand erase option on Edit: suggest you to flash stock rom first and oem unlock, don't need to wait for 7 days if imei is 0000 skip combination step
Device Should boot into Factory binary
Use IME to restore imei using *#06# (or imei 0000 in stock rom) Edit: This step is not required if efs backup is restored successful
Your device should have dm-verify failed in recovery due to drk error
Continue drk bypass for dm verify error below to continue
willhemmens said:
Make you post readable for everyone using the dark theme and you might get more response.
What exactly did you flash with Odin and what happened, other than it didn't work?
Click to expand...
Click to collapse
What? I'm using desktop. Is there a different view on mobile?
Bricked Note 9 due to efs
devil499 said:
I try to use sam fix tool to get my baseband (unknown) and sim cad imei fixed
i use the tool and choose baseband fix it boot into donwload mode and flash something
after that my note 9 stuck bootloop
i flashed stock frimware using odin and didnt work
i flashed combination file and also got bootloop
i can go to download mode
but whatever i do my phone stuck bootloop
plz need help plz guys
BUT I MADE A EFS BACKUB USING SCRIPT CMD IT CREAT A FLASH FILE CAN BE FLASHED USING ODIN VIA AP
BUT I CAN ACCESS IT RIGHT NOW BECASE I HAVE IT IN MY WORK
IS THAT ABLE TO HELP ME FIX THE PROBLEME[/COLOR]
Click to expand...
Click to collapse
I have the same problem with my note 9. Im looking if anyone can provide me with efs file of N960F Binary 3 so i can get it unbricked again.
I found this website but it has efs files for binary 1 and 2 not 3. Will it still work if i use binary 2 efs?
//frpdone.com/efs-mdm-samsung/
Did u find a solution?
Hi all, I have this A71 that yesterday was working just fine, and today is in bootloop for no reason at all.
The owner was as smart as to keep tons of important stuff on that phone with no backup, so I have this request: is there a way to pull anything out of there?
I can access stock recovery and fastboot.
I am really sorry to hear that you can maybe try to install twrp and recover the files with "adb pull" or accessing the phone storage via a pc (you need to have twrp installed) i don't know any other way besides this. If i helped you make sure to like my response
Solved simply flashing different version of stock ROM.
Was on Andrioid 10, flashing 11 via Odin solved the bootloop issue.
rocciamax said:
Solved simply flashing different version of stock ROM.
Was on Andrioid 10, flashing 11 via Odin solved the bootloop issue.
Click to expand...
Click to collapse
hello did you manage to keep all your data? i'm new i found the correct firmware for my phone , i have samsung odin.... do i just flash? it states that i will loose all info
Yes, everything saved.
Got the firmware from sammobile, flashed with Odin and retained everything: apps, settings, data, photos....
Just be sure to flash the HOME_CSC file and not the plain CSC, or it'll wipe all.
rocciamax said:
Yes, everything saved.
Got the firmware from sammobile, flashed with Odin and retained everything: apps, settings, data, photos....
Just be sure to flash the HOME_CSC file and not the plain CSC, or it'll wipe all.
Click to expand...
Click to collapse
just to make sure that i dont mess up my bro's phone... i would unzip the firm ware and choose the Home_CSC file and put that in the odin csc box and flash... THANK YOU LOADS FOR YOUR HELP!
I flashed all the files: BL, AP, CP and CSC, the latter using the HOME_CSC file.
Once I finish downloading the firmware! I'll let you know! What happens . this is my last shot at this point I tried everything !
Thanks either way for your help!
sadly it didn't work ... the bootloop is still there....
i'm now worried about trying the normal csc and deleting everything without fixing the bootloop.... i wonder if its a mechanical issue