Hi friends, well basically the problem is I got a friends y GT-I9500 and it bootloops over and over with any ROM other than South Africa Rom 4.2.2 and has invalid baseband. It's a cell from a friend of mine I never new which rom was installed on this phone and as soon as I got it I installed the official stock rom from my country which was KIT KAT rom 4.4.2 tried unbranded ARO version first through ODIN, everything went fine, but it got stuck on bootloop.
These were the things I tried.
- stock recovery (I9500UBUGNG1_I9500UUBGNG1_ARO) --> wiping factory data/reset , ---> wiped cache = Same thing bootlooping
Installed another Stock rom KIT KAT from corresponding Carrier (I9500UBUFNC1_I9500TFGFNC1_UFN) , did :
- stock recovery --> wiping factory data/reset , ---> wiped cache = Same thing bootlooping
Downloaded previous builds of stock rom going back to 4.2.2 , installed stock version of 4.2.2 ARO unbranded (I9500UBUBMG1_I9500TFGBMG1_UFN)
- stock recovery --> wiping factory data/reset , ---> wiped cache = Same thing bootlooping
I also tried installed some custom roms , having flashed Philz recovery and installed from there onwards, no luck as well.
So I came across some threads which said the only possible way of downgrading if I had installed 4.4.2 kit kat , was using a South African ROM 4.2.2. So I tried it and to my surprise the phone booted fine without any problems. Honestly I don't remember if I did flash it with the PIT file and re-partition. But I did work . The only problem once inside the OS itself it showed invalid baseband. I suppose this was due to the EFS partition being changed intially by KIT KAT.
So I'm hoping someone might help me out as to know what else to try, because honestly I'm out of all ideas.
Thanks !
When you went into download mode, what was the product name the phone reported?
Strephon Alkhalikoi said:
When you went into download mode, what was the product name the phone reported?
Click to expand...
Click to collapse
mmm I have to check, what do yo uwant me to see what string? I can put it on downlaod mode again.. and get you a screenshot
Screenshot is fine as it will give me what I need to know.
Strephon Alkhalikoi said:
When you went into download mode, what was the product name the phone reported?
Click to expand...
Click to collapse
screenshot attached , please check
Thanks. I just wanted to be sure you didn't get a Frankenstein phone, as there have been a run of these phones appearing in the last few months. Resellers will take SGH-I337 phones (US AT&T Galaxy S4), slap an I9500 or I9505 IMEI on them, and proceed to add firmware for the I9500/I9505 onto them. When the purchaser gets the device and attempts to update it or customize it, they find they can't, as the AT&T S4 bootloader is locked.
Now that I've gotten the explanation out of the way, you need to do the following. 1) Install Wanam's EFS Backup tool to the S4, run it, and backup the hidden partitions on the device. 2) You're going to again install the latest ROM for your region through Odin, but this time you're also going to add an I9500 PIT file to it. The PIT file should be available for download in the S4 forums here and will tell Odin the correct partition layout of the device. Odin will then install the ROM using that partition layout. With luck, it should correct the issues you've been having.
Should you have an issue with no IMEI or no signal after flashing, flash the modem file, which should also be available on the forums, and don't use the PIT file. If that doesn't work, install EFS Backup again and restore the partitions.
Strephon Alkhalikoi said:
Thanks. I just wanted to be sure you didn't get a Frankenstein phone, as there have been a run of these phones appearing in the last few months. Resellers will take SGH-I337 phones (US AT&T Galaxy S4), slap an I9500 or I9505 IMEI on them, and proceed to add firmware for the I9500/I9505 onto them. When the purchaser gets the device and attempts to update it or customize it, they find they can't, as the AT&T S4 bootloader is locked.
Now that I've gotten the explanation out of the way, you need to do the following. 1) Install Wanam's EFS Backup tool to the S4, run it, and backup the hidden partitions on the device. 2) You're going to again install the latest ROM for your region through Odin, but this time you're also going to add an I9500 PIT file to it. The PIT file should be available for download in the S4 forums here and will tell Odin the correct partition layout of the device. Odin will then install the ROM using that partition layout. With luck, it should correct the issues you've been having.
Should you have an issue with no IMEI or no signal after flashing, flash the modem file, which should also be available on the forums, and don't use the PIT file. If that doesn't work, install EFS Backup again and restore the partitions.
Click to expand...
Click to collapse
Ok , thanks for such a complete explanation. It's always nice when someone with knowledge takes the time to go detail by detail explaining everything. This is the way things have to be done, and explained. Ok so let me get things straight
- Wanams Efs backup , I need to install within a working ROM right? It's not through Philz recovery, What should I backup with EFS backup only EFS?. Something I forgot to tell you was I did change some permissions to see if the invalid baseband got fixed, I changed some owner permissions on the EFS folder, you should know about this.
-Then you want me to install latest ROM should that be KIT KAT right?. Unbranded for my region. Yes I know about the PIT file to repartition, I've already done this and still bootlooped with all the rom variants I tried. The only possible way the phone boots and succeeds is with South African ROM 4.2.2 I've tried all previous roms even choosin the apropiate PIT and still bootlooped.
-The only thing I'm left thinking is all these bootloops have something to do with the modem file, which the South African rom 4.2.2 might have a different modem. Which modem should I install I've read the G versions onwards modified the EFS partition.
- Last, how would EFS backup fix the EFS partition if it's only backing it up, Cause i'm thinking as I've initially when I received the phone installed KIT KAT. IT changed the whole partition scheme of efs.
So now that I've gone through every point, can you clear again the steps sorry if I'm so tedious on reviewing again but I needed to clarify bit by bit.
I must have misunderstood you regarding the IMEI. If it's invalid EFS Backup won't help. Also, if you've already ran the PIT file and still get bootloops, you may have to take the device in for servicing. A service center should be able to fix this without too much trouble. Unfortunately, I can't fathom why only one ROM installs, unless the carrier locked down the device so much that upgrades are impossible.
Perhaps one of the other advanced users or developers have a clue?
Strephon Alkhalikoi said:
I must have misunderstood you regarding the IMEI. If it's invalid EFS Backup won't help. Also, if you've already ran the PIT file and still get bootloops, you may have to take the device in for servicing. A service center should be able to fix this without too much trouble. Unfortunately, I can't fathom why only one ROM installs, unless the carrier locked down the device so much that upgrades are impossible.
Perhaps one of the other advanced users or developers have a clue?
Click to expand...
Click to collapse
Hey so many thanks, honestly I don't know what have been wrong with the device. I'm suspeting this has to do with the modem. Could the modem version on the South africa rom be causing the ROM to install fine. But think of this me first installing KIT KAT and have screwed up the efs and as a consequence the IMEI. My only way would be to install kit kat succesfully as the EFS might have changed. Any advices on this?
The modem isn't likely to cause a bootloop. At worst, it's likely to render the cellular and WiFi services unusable until it's flashed again. Screwing the EFS up is where I believe your problems lie. The EFS partition may well be corrupted, which could cause your bootloop. I really think the only way you'll resolve this is by having someone at Samsung take a look at it. You've repeatedly installed ROMs and have had no luck, so installing a ROM again isn't going to help you here.
Related
Hi all. Tried my first root + custom rom installation and i messed up the device..
i had the newest KIES firmware update (phone XXBMA5) and (XXBMA6) and i rooted the device with odin (3.07). That went OK.
Then i installed the CWM recovery with odin and that was OK too.
Then i downloaded the latest Omega Rom (i missread that it supports N8020) and followed the installation instructions to the point where it started installing Omega V2.0 from SDCARD and then it asked me to select device from a list that included only (N8000,N8010,N8013)..
So the situation now is that i have working odin, working CWM and backup of the EFS (img+tar) but no working recovery. i live in Finland and the device is Sonera locked i think, so the stock roms (international) do not work i guess.
KIES has a backup of my Note but i can't even get to a point where KIES discovers the device.
So basically i think i need a working ROM for my model (Note 10.1 4G N8020), or can i recover the original samsung software somehow ?
Any advices ?
Removed
Just a thought, but can't you reflash CWM or the stock recovery?
If you didn't install the rom why do you need to re-install anything. Just powering down and powering up should have left you as was....
Alajarvi84 said:
working CWM .......... but no working recovery.
Click to expand...
Click to collapse
Maybe i'm missing something but isn't CWM your custom recovery?
It doesn't sound like you've actually installed any rom yet.The Omega installer doesn't actually install anything until a few steps after the one you mentioned about the model type.
I'm with ultramag69 on this one. You should still be on a stock rom unless you already wiped your original rom.
Hi again. Problem solved, just had to do emergency thing from KIES. Like i said this was the first time trying root + custom ro install and to be honest it went to ****. Somehow i managed to delete the stock firmware so that is why the recovery gave me (no files). I did make some backup but when tried to restore it said MD5 mismatch or something. At first the KIES emergency recovery could not find the device, but after i switched from CWMcto stock recovery it worked.
So what did i learn from all this ? Nothing, because i am getting too old (tired+lazy ) to do proper investigation. So one could say my strategy is to bang my head to the wall as long as it takes to go trough. Even if i could just go around it
So basically i am now at the point where i started, with stock 4.1.2 rooted. Used the triangle away to wipe the (6) custom installs or something away, but it still says custom in the settings> information. Does this mean that OTA won't work ? Any way around it ? Because i would like to check now and then that is my version of android the newest one..
Could someone recommend a custom ROM for my Note 10.1 4G (LTE) N8020 4.1.2 because the only one i was able to find was the CyanogenMod (or something) and it basically makes the S-Pen (almost) useless. What i would like is the Omega ROM, but like stated before the installation only supported N8000, N8010 & N8013...
Added screenshot from info.
Thanks anyway
What is truly amazing is that i did not brick the device tough..
switch from cwm to stock
Alajarvi84 said:
Hi again. Problem solved, just had to do emergency thing from KIES. Like i said this was the first time trying root + custom ro install and to be honest it went to ****. Somehow i managed to delete the stock firmware so that is why the recovery gave me (no files). I did make some backup but when tried to restore it said MD5 mismatch or something. At first the KIES emergency recovery could not find the device, but after i switched from CWMcto stock recovery it worked.
So what did i learn from all this ? Nothing, because i am getting too old (tired+lazy ) to do proper investigation. So one could say my strategy is to bang my head to the wall as long as it takes to go trough. Even if i could just go around it
So basically i am now at the point where i started, with stock 4.1.2 rooted. Used the triangle away to wipe the (6) custom installs or something away, but it still says custom in the settings> information. Does this mean that OTA won't work ? Any way around it ? Because i would like to check now and then that is my version of android the newest one..
Could someone recommend a custom ROM for my Note 10.1 4G (LTE) N8020 4.1.2 because the only one i was able to find was the CyanogenMod (or something) and it basically makes the S-Pen (almost) useless. What i would like is the Omega ROM, but like stated before the installation only supported N8000, N8010 & N8013...
Added screenshot from info.
Thanks anyway
Click to expand...
Click to collapse
How did you switch from CWM to stock? I have having a problem syncing with kies also using omega rom on n8013.
jjndimp said:
How did you switch from CWM to stock? I have having a problem syncing with kies also using omega rom on n8013.
Click to expand...
Click to collapse
I was not easy, i just tried the download mode over and over again with KIES open in windows and somehow it finally did find my device and offered a emergency restore. That is it, and the device was restored to default "original state".
OMG.... one would think after nearly having bricked your device you would either A) stop messing around with it or, B) read and learn more about what you're wanting to achieve and THEN maybe trying something with the ABSOLUTE certainty that a backup to restore is available to you in case of any mishap!
Moral of story :
Don't do anything until you are absolutely sure you have read EVERYTHING about what you are going to do.
For others wanting to mess with their devices, take heed! You may not be as lucky as OP (or troller) whichever is applicable.
There comes a certain point, that when crossed one does not care what happens to the device at hand. After fighting with my n8020 for several days in a row i couldn't care less, and like said before i dont have the level of enhusiasm like i had when i was younger. Of course i know now what went wrong.. But seriously, these are just overpriced toys, so it's not a matter of life and death.
Sent from my GT-N8020 using XDA Premium HD app
Okay, so recently this week I rooted my Tmobile Galaxy note 3 SM-N900T model. I installed the Xnote Custom Rom and everything was pretty much fine.
This is where the problem started. I have a mobile app Called Odin Mobile, which I used to actually Custom Rom Flash, because I didn't see the option during the Bootloader to where I'm able to Custom Rom flash it from my external card, so I bought the Odin app to help me do it mobile and use CW Recovery to handle it. Now I went to find a wifi patch, because my wifi would NOT work with this Rom at all, I found a patch to install, so I used Odin Mobile Pro to simply just Flash the install on it and hope it would go through after a bit of research. Now my phone I believe is Paperweight softbrick. It doesn't go past the Xnote KitKat Menu of 4.4.2. I can't do anything, even worse my computer isn't reading my phone to where I can just get the files from my phone or external Microsdcard.
What should I do ? I'm pretty helpless at the moment. I even went to try and find a Stock Rom for my Model number which is the Tmobile Model Number: SM-N900TZWETMB Variant, I haven't been able to locate any, my only hope from what I'm reading, is to find a Stock Rom of 4.4.2 with my model and use Odin and hopefully that works, but I'm not able to locate anything, and the internet here is pretty horrible. If there is anything anyone can do to help me I appreciate it.
Snake2594 said:
Okay, so recently this week I rooted my Tmobile Galaxy note 3 SM-N900T model. I installed the Xnote Custom Rom and everything was pretty much fine.
This is where the problem started. I have a mobile app Called Odin Mobile, which I used to actually Custom Rom Flash, because I didn't see the option during the Bootloader to where I'm able to Custom Rom flash it from my external card, so I bought the Odin app to help me do it mobile and use CW Recovery to handle it. Now I went to find a wifi patch, because my wifi would NOT work with this Rom at all, I found a patch to install, so I used Odin Mobile Pro to simply just Flash the install on it and hope it would go through after a bit of research. Now my phone I believe is Paperweight softbrick. It doesn't go past the Xnote KitKat Menu of 4.4.2. I can't do anything, even worse my computer isn't reading my phone to where I can just get the files from my phone or external Microsdcard.
What should I do ? I'm pretty helpless at the moment. I even went to try and find a Stock Rom for my Model number which is the Tmobile Model Number: SM-N900TZWETMB Variant, I haven't been able to locate any, my only hope from what I'm reading, is to find a Stock Rom of 4.4.2 with my model and use Odin and hopefully that works, but I'm not able to locate anything, and the internet here is pretty horrible. If there is anything anyone can do to help me I appreciate it.
Click to expand...
Click to collapse
wish i could help, but after searching i came up empty just like you.
you really need the stock file to even see if this is fixable.
in the future you really should make a backup after installing a custom recovery before flashing anything else, for cases just like this.
Snake2594 said:
Okay, so recently this week I rooted my Tmobile Galaxy note 3 SM-N900T model. I installed the Xnote Custom Rom and everything was pretty much fine.
This is where the problem started. I have a mobile app Called Odin Mobile, which I used to actually Custom Rom Flash, because I didn't see the option during the Bootloader to where I'm able to Custom Rom flash it from my external card, so I bought the Odin app to help me do it mobile and use CW Recovery to handle it. Now I went to find a wifi patch, because my wifi would NOT work with this Rom at all, I found a patch to install, so I used Odin Mobile Pro to simply just Flash the install on it and hope it would go through after a bit of research. Now my phone I believe is Paperweight softbrick. It doesn't go past the Xnote KitKat Menu of 4.4.2. I can't do anything, even worse my computer isn't reading my phone to where I can just get the files from my phone or external Microsdcard.
What should I do ? I'm pretty helpless at the moment. I even went to try and find a Stock Rom for my Model number which is the Tmobile Model Number: SM-N900TZWETMB Variant, I haven't been able to locate any, my only hope from what I'm reading, is to find a Stock Rom of 4.4.2 with my model and use Odin and hopefully that works, but I'm not able to locate anything, and the internet here is pretty horrible. If there is anything anyone can do to help me I appreciate it.
Click to expand...
Click to collapse
Your phone is bricked. You should find a file of the stock rom and flash it via odin. Remember you can flash any note 3 firmware onto any note 3, so I'd recommend you to find the rom file of the international version of your phone (which is the N9005). Remember, if you're able to boot your phone into flashmode, you'll always be able to unbrick/repair it.
|>/\nte said:
Your phone is bricked. You should find a file of the stock rom and flash it via odin. Remember you can flash any note 3 firmware onto any note 3, so I'd recommend you to find the rom file of the international version of your phone (which is the N9005). Remember, if you're able to boot your phone into flashmode, you'll always be able to unbrick/repair it.
Click to expand...
Click to collapse
Okay thank you for the info, I actually fixed my phone not a couple of hours, shortly after this post. What I did was get the latest Clockworkmod, mine was an old version and didn't have the Install option, when I used Odin, I use the updated Version and was able to Wipe my data, then simply Reflash the Custom Rom and solved my problem. Soon as I got my phone on, I instantly went and Nandroid, so.....won't be doing that again.
I actually didn't know I can flash any note 3 firmware on my phone, least the Tmobile versions, good to know. I'll find em and keep on my computer just in case. I still have the wifi problem, so hopefully I can tackle that down and learn to patch my rom.
Snake2594 said:
Okay thank you for the info, I actually fixed my phone not a couple of hours, shortly after this post. What I did was get the latest Clockworkmod, mine was an old version and didn't have the Install option, when I used Odin, I use the updated Version and was able to Wipe my data, then simply Reflash the Custom Rom and solved my problem. Soon as I got my phone on, I instantly went and Nandroid, so.....won't be doing that again.
I actually didn't know I can flash any note 3 firmware on my phone, least the Tmobile versions, good to know. I'll find em and keep on my computer just in case. I still have the wifi problem, so hopefully I can tackle that down and learn to patch my rom.
Click to expand...
Click to collapse
Just to mention it, that doesn't work only for t-mobile samsung phones. As I said, you can flash any note 3 firmware onto any note 3. I recommend the international version because it's generic, and generic firmwares are always the best ones, with as little bloatware as possible.
Hi,
I flashed the new TWRP2.8.6.0 on my N8000 (before I had 2.8.5.x).
Accidently I flashed the "p4noterf" instead of "n8000" version (with Odin 3.09).
When my SIM-card was not detected, I recognized the error.
Then I flashed TWRP 2.86.0 "n8000"-Version, but SIM was still not recognized.
After that I restored different ROMS (OMNI 5.1; CM12..) from which I had backups, including EFS/IMEI and all other stuff.
Also I wiped (factory, cache, dalvik, system, data) and restored the ROMS again (including EFS...).
But whatever I do: SIM is gone / not detected.
I would be grateful for any help/advice :laugh:!
Me too. I was fiddling with my old 10.1 and decided to give it a run on Lollipop 5.1. I updated the CWM to TWRP and sim recognition was lost. IMEI is blank and mobile network is non existent.
Could any kind soul please advise?
Update: Going back to 4.4.2 stock does show the mobile network signal but there is a notification for SIM card to be inserted. IMEI is back but SIM is still not recognised.
3ftguru said:
Update: Going back to 4.4.2 stock does show the mobile network signal but there is a notification for SIM card to be inserted. IMEI is back but SIM is still not recognised.
Click to expand...
Click to collapse
Perhaps yous can try to restore EFS now (once again) - now that you are back to stock.
There is a thread in a German forum that in 1. step going back to stock saved IMEI. Then, as second step to restore EFS brought SIM back again... Hopefully this helps
Best wishes:good:
Tried using EFS Pro to backup and restore again but it didn't work. Interesting enough, my ROM version stated by EFS Pro is pnote and not N8000. So now downloading and flashing a confirmed N8000 stock rom to see if it works.
Update: Another rom still show p4note which means somewhere in EFS the n8000 is replaced with p4note. Anyone got any idea how to edit back?
3ftguru said:
Update: Another rom still show p4note which means somewhere in EFS the n8000 is replaced with p4note. Anyone got any idea how to edit back?
Click to expand...
Click to collapse
Interesting, indeed.
There's a thread on XDA named "Recover your IMEI in 9 steps". I think it's a description of the problem we are faced with or something very close to, at least.
Unfortunately I am not allowed to post links here :crying: If you PM me I can send it to you.
The logic is the same I found in the German thread: go back to Stock and then change/manipulate EFS.
The crucial file in EFS folder seems to be nv_data.bin perhaps the needed information is in there. There is also a ".bak" and ".md5" of this file.
On my working S3 nv_data.bin changes constantly, date of the file is always "new", not older than a few hours. On the non working N8000 the file date is constant and from early April.
I hope to have some time to explore and test something this weekend .
A further idea might be to (also) go back to n8000 stock recovery - perhaps twrp messed something there.
Again, I can not post the link, just seaarch for the term in www.
Back again!
Hi,
finally SIM is back again :good:
1. Flashed n8000 Stock recovery (probably unnecessary, is inculded in stock rom)
2. Flashed Stock ROM; rather old version (4.1.2) from sammobile: N8000XXCMI2_N8000OXACMI2
2a: Got endless boot loop
3. Booted to stock-recovery --> factory reset (or factory wipe?)
4. Booted to sys and SIM was there :laugh:
Ev. it matters which ROM is chosen, probably older ones (close to production date) are the better choice.
@3ftguru: Hope this will work for you too!
UPDATE: DO NOT USE AUTOMATIC UPDATE (OTA by Samsung) after flashing!
This broke my n8000 again, got an endless "Samsung N8000" Start logo after that.
I could not get into recovery, could not shut it down, only bootload was accessible.
Then I flashed same ROM again with odin - nothing changed.
Finally flashed 4.4.2 - and it's back again - SIM o.k., can get into recovery ... ufffffff!
This is the file I used form sammobile: N8000XXUDNE4_N8000OXADNE4
My device type is listed as p4note and not N8000 anymore even after flashing an old 4.1.2 Samsung ROM. Scratching my head on this one.
Anyone knows how to convert back to n8000 for device type?
Same problem. It brokes after installing TWRP.
---------- Post added at 05:47 PM ---------- Previous post was at 05:46 PM ----------
xd_surfer_g said:
Hi,
finally SIM is back again :good:
1. Flashed n8000 Stock recovery (probably unnecessary, is inculded in stock rom)
2. Flashed Stock ROM; rather old version (4.1.2) from sammobile: N8000XXCMI2_N8000OXACMI2
2a: Got endless boot loop
3. Booted to stock-recovery --> factory reset (or factory wipe?)
4. Booted to sys and SIM was there :laugh:
Ev. it matters which ROM is chosen, probably older ones (close to production date) are the better choice.
@3ftguru: Hope this will work for you too!
UPDATE: DO NOT USE AUTOMATIC UPDATE (OTA by Samsung) after flashing!
This broke my n8000 again, got an endless "Samsung N8000" Start logo after that.
I could not get into recovery, could not shut it down, only bootload was accessible.
Then I flashed same ROM again with odin - nothing changed.
Finally flashed 4.4.2 - and it's back again - SIM o.k., can get into recovery ... ufffffff!
This is the file I used form sammobile: N8000XXUDNE4_N8000OXADNE4
Click to expand...
Click to collapse
So do you use TWRP at old ROM?
Have found solution:
1. Install stock ROM (older) - sim will be working
2. Install TWRP 2.6.3.1
3. Flash something - and sim will be working, too
CyanoFresh said:
Have found solution:
1. Install stock ROM (older) - sim will be working
2. Install TWRP 2.6.3.1
3. Flash something - and sim will be working, too
Click to expand...
Click to collapse
doesnt work for me whether i got use pit to repartition or just a 4.0.4 stock rom to flash. The SIM just doesnt get recognised.
Guess I just have to use it as a N8010 instead.
3ftguru said:
doesnt work for me whether i got use pit to repartition or just a 4.0.4 stock rom to flash. The SIM just doesnt get recognised.
Guess I just have to use it as a N8010 instead.
Click to expand...
Click to collapse
Try this 4.4.2 rom:
Thread (Ukrainian language) - http://www.ex.ua/91621823
direct download - http://www.ex.ua/load/171252309
torrent - http://www.ex.ua/torrent/171252309
Flash N8000XXUDNH2_N8000OXEDNH1_N8000XXUDNH2_HOME.tar.md5 by Odin. Try to factory reset. it should work
Thank you so much for this thread an especially for this posting!!!
I had the same problem, maybe flashed a wrong recovery/firmware/rom or whatever but I lost access to the SIM card in my N8000. After I follow your steps below now I'm back in stock rom with SIM-access and can reconfigure my tablet.
xd_surfer_g said:
Hi,
finally SIM is back again :good:
1. Flashed n8000 Stock recovery (probably unnecessary, is inculded in stock rom)
2. Flashed Stock ROM; rather old version (4.1.2) from sammobile: N8000XXCMI2_N8000OXACMI2
2a: Got endless boot loop
3. Booted to stock-recovery --> factory reset (or factory wipe?)
4. Booted to sys and SIM was there :laugh:
Ev. it matters which ROM is chosen, probably older ones (close to production date) are the better choice.
@3ftguru: Hope this will work for you too!
UPDATE: DO NOT USE AUTOMATIC UPDATE (OTA by Samsung) after flashing!
This broke my n8000 again, got an endless "Samsung N8000" Start logo after that.
I could not get into recovery, could not shut it down, only bootload was accessible.
Then I flashed same ROM again with odin - nothing changed.
Finally flashed 4.4.2 - and it's back again - SIM o.k., can get into recovery ... ufffffff!
This is the file I used form sammobile: N8000XXUDNE4_N8000OXADNE4
Click to expand...
Click to collapse
Tried the Ukrainian ROM but still didn't work.
Now I suspect is that I have accidentally made some changes to the EFS or had damaged the SIM port physically. Otherwise I should have been able to achieve the ROM recognizing the sim card.
Sent from my SM-N910G using Tapatalk
Not working
Sim card comeback after i was reinstall rom 4.4.2, but sim card not working when I install cm12.1 .:crying:
Recovery phone
I thing sim card will working if you recovery phone, file recovery boot with odin:
https:// drive.google.com/file/d/0B_SHfdpTGxm6cHhweGRCR05jYlE/view
After reinstall cm 12.1, 13 for Note 10.1 - N8000.
Good luck.
xd_surfer_g said:
Hi,
finally SIM is back again :good:
1. Flashed n8000 Stock recovery (probably unnecessary, is inculded in stock rom)
2. Flashed Stock ROM; rather old version (4.1.2) from sammobile: N8000XXCMI2_N8000OXACMI2
2a: Got endless boot loop
3. Booted to stock-recovery --> factory reset (or factory wipe?)
4. Booted to sys and SIM was there :laugh:
Ev. it matters which ROM is chosen, probably older ones (close to production date) are the better choice.
@3ftguru: Hope this will work for you too!
UPDATE: DO NOT USE AUTOMATIC UPDATE (OTA by Samsung) after flashing!
This broke my n8000 again, got an endless "Samsung N8000" Start logo after that.
I could not get into recovery, could not shut it down, only bootload was accessible.
Then I flashed same ROM again with odin - nothing changed.
Finally flashed 4.4.2 - and it's back again - SIM o.k., can get into recovery ... ufffffff!
This is the file I used form sammobile: N8000XXUDNE4_N8000OXADNE4
Click to expand...
Click to collapse
Hi there, i had flashed cm12.1 for N8000 and didnt backup efs. So even after returning to stock rom, i couldn't find my SIM. My IMEI was lost, and baseband version was showing unknown. So, can I use your method to restore my IMEI and SIM problem? Please reply fast as I need it within a few days. Thank you.
hey all
I did a basic root on my samsung galaxy s6 a few days ago. just installed superSu and gave me root access. after that I installed TWRP which I then used to try and install the xposed framework. From then on my phone is stuck on the samsung screen saying kernel is not seandroid enforcing. I downloaded the stock rom for my phone (sm-g920F on 6.01) and attempted to flash it via odin 3.07 but it always failed after the sboot.
i have searched to try and find a solution but nothing I can find will work. can anyone help?
so i got my s6 working after flashing a full stock firmware i found via a link on this forum (i forget which one...sorry)
it gave me BL_G920FXXU3DPBG_CL7086820_QB8626574_REV02_user_low_ship.tar.md5
AP_G920FXXU3DPBG_CL7086820_QB8626574_REV02_user_low_ship.tar.md5
CP_G920FXXU3DPB6_CL7086820_QB8569466_REV02_user_low_ship.tar.md5
CSC_BTU_G920FBTU3DPB1_CL7140831_QB8460122_REV02_user_low_ship.tar.md5
it also recommended that I flash the pit file ZEROFLTE_EUR_OPEN.pit.
this was all done via the latest version of odin. initially, the flashing failed at cm.bin so I reflashed omitting the bootloader and all seemed to be well.
My phone set up fine and then I realised that it will not recognise my sim...or any sim for that matter. in settings under sim card status...every entry is listed as unavailable. IMEI is unknown as is baseband version.
i realise that I have obviously messed up big time with the initial flashing (uhuh....backup...backup....backup) but I would really like some help to get my phone back up and running as a ...well...phone.
any help or suggestions would be most appreciated.
thanks in advance x
vickstew2000 said:
so i got my s6 working after flashing a full stock firmware i found via a link on this forum (i forget which one...sorry)
it gave me BL_G920FXXU3DPBG_CL7086820_QB8626574_REV02_user_low_ship.tar.md5
AP_G920FXXU3DPBG_CL7086820_QB8626574_REV02_user_low_ship.tar.md5
CP_G920FXXU3DPB6_CL7086820_QB8569466_REV02_user_low_ship.tar.md5
CSC_BTU_G920FBTU3DPB1_CL7140831_QB8460122_REV02_user_low_ship.tar.md5
it also recommended that I flash the pit file ZEROFLTE_EUR_OPEN.pit.
this was all done via the latest version of odin. initially, the flashing failed at cm.bin so I reflashed omitting the bootloader and all seemed to be well.
My phone set up fine and then I realised that it will not recognise my sim...or any sim for that matter. in settings under sim card status...every entry is listed as unavailable. IMEI is unknown as is baseband version.
i realise that I have obviously messed up big time with the initial flashing (uhuh....backup...backup....backup) but I would really like some help to get my phone back up and running as a ...well...phone.
any help or suggestions would be most appreciated.
thanks in advance x
Click to expand...
Click to collapse
Try smart switch. Not sure if it could restore the imei but it could bring the phone back to original csc when you bought it.
Sent from my SM-G925F
Rosli59564 said:
Try smart switch. Not sure if it could restore the imei but it could bring the phone back to original csc when you bought it.
Sent from my SM-G925F
Click to expand...
Click to collapse
i had tried several times to connect to smart switch but it would not recognise my phone. after a lot of faffing about I finally managed to get it to do an emergency recovery and all seems well so far. it even restored my imei number so thanks for that suggestion Rosli. much appreciated xx
When u install xposed did u ude the special wanam version of the framework
Would say whipe cashe and wait a little while for stock roms like 40 minutes after first time install
Hey,
Need some help here and not sure what's gone wrong, I've managed to root and flash custom ROM's before, but for some reason, my S7 now will not let me flash the BL file when trying to restore a stock ROM.
I can flash AP, CP and CSC with no problems, but trying to flash the BL file it gets half way and then the box at the top just goes red and says FAIL!
I've tried wiping everything from TWRP, installing custom ROM's and so forth to try and then restore from - phone is UK on BT Mobile and usually I use the XEU stock rom to reset.
The problem is, I have no carrier signal or IMEI information (I've tried the SIM in a different phone and it's working fine) so I can only presume it's something to do with the BL flash?
Any help is really appreciated!
Ok, well, hours of playing I found a SM-G930F combination firmware to flash (COMBINATION_FA60_G930FXXU2ARA2_BoxWares) - this has gotten me into FACTORY BINARY and lots of factory test / setting modes - phone now has it's IMEI number back AND I was able to receive a call from my girlfriends phone...
This seems to be running on Marshmallow 6.0.1 but obviously is not usable as an OS - so I need help to uprade firmwares in the correct order as trying to flash to 7 or 8 just fails in Odin and I can't seem to install TWRP recovery either from this.
I'm on BT Mobile (I used XEU before without issue - until recently!) so presume that's still the correct version...
Thanks!
Before I say anything DO you have a backup of your EFS folder do that first
Assuming you can only flash the binary 2 combination file firmware ,Samsung has recently updated their bootloader to not allow downgrades , you can only flash Nougat firmware from this year
Hey, I actually found that from some random spanish forum late last night... so I now have the combination rom with a useless (daily) front end / homescreen running android 6.0.1 but believe the bootloader is locked (from the nice little red error messages on startup) to a more recent version.
Supposedly I should be able to flash a `current` stock firmware then... but cannot seem to flash an AP file over this Combination rom install....
I did manage to download APKInstaller and install Kingroot (TWRP flash does not work - you cannot get into recovery anymore) and some other android apps (phone / sms / messenger) so have limited functionality but better than none for now.
No backups.
Boot into download mode , flash only the Sboot ( unzip the tar and make tar with only sboot) from any recent stock rom .
in AP put TWRP , untick the auto reboot.
when it passes( unplug phone ) hold the volume done , home power button till phone reboots (screen goes off) , quickly press volume up ,home and power button , you should be in TWRP
The combination firmware do not allow recovery modifications , it will just go in bootloop
OK, I'll try that when I get home later... lets say it works, what is my course of action then?
I still think I won't be able to flash a rom from Odin just by installing TWRP, so what actions do I need to take in TWRP? complete format ?
Thanks!
In TWRP make a backup of the EFS and Baseband partitions , copy to memory card .
I learned it the hard way , I ended up buying a second S7 with broken LCD so I can use the board
No box or tool can patch the certificate once you on Nougat as of yet
then you can go back to download mode and flash the AP ,CP ,CSC and phone should boot up , Leave the BL
Managed to get into stock recovery somehow (wasn't working before) and can see options for ADB sideloading etc again so that's something I guess lol
Presumably, if I can flash the boot file then twrp, I can then install a custom rom (i originally went from 7.0 up to 8 with Pixel Experience and Lineage, before things went tits up)
I'm guessing it'll be a case of formating data / wiping cache and installing the custom rom - assuming the BL is running 7.0 - or am i going to need to try and flash everything again via Odin (unsuccessful so far and only rom that will install is Combination)? also what about the CSC file...?
The only reason I'm in this predicament is because one of the custom roms somewhere (or google) screwed my IMEI settings, but Combination has brought those back.
you should be able to install any stock firmware from March 2018 onwards without any problems
Hmm ok so the network things I'm on T-Mobile and not BT Mobile lol (presumably because of the EUR flash) not sure if this will have implications when it comes to billing etc (BT bought out EE/T-Mobile but are different businesses still).
So does anyone have a working link to the XEU firmware? XEU-G930FXXS2DRC3-20180329132652 seems to be the filename... I can only find crap sites with 4kb downloads unless you pay $10-$20 lol
Success - in the absence of an upto date firmware from March for XEU - I found and installed the EUR one - BL everything went straight in and I've booted to setup screen now \o/
In Greek.... OK so hopefully I can just change language and wait for the XEU to surface (or is it OK to use the EUR? I have IMEI everything so looking good so far!)
I will probably flash Pixel Experience again unless someone recommends another over this?
Dreamz2k said:
Success - in the absence of an upto date firmware from March for XEU - I found and installed the EUR one - BL everything went straight in and I've booted to setup screen now \o/
In Greek.... OK so hopefully I can just change language and wait for the XEU to surface (or is it OK to use the EUR? I have IMEI everything so looking good so far!)
I will probably flash Pixel Experience again unless someone recommends another over this?
Click to expand...
Click to collapse
As someone said before.. Flash TWRP using ODIN; boot to twrp and make a backup of the EFS partition ONLY. Store the backup in the SD card and then copy it to the pc/dropbox/Drive/whatever. There are no guaranties that you wont loose the IMEI again if you attempt to flash the custom rom again. Then If you want to be on a completely stock rom, reflash the rom using ODIN. If you want to backup the baseband too, do the same procedure again but select only the baseband partition (untick the others)
To download stock roms you can use either the SamFirm tool (google search it.. it is on XDA) or Updato (site). Both of them provide really fast download speeds as there are no caps, and they are free. The files are downloaded straight from Samsung servers.
Sent from my SM-G930F using Tapatalk
Dreamz2k said:
Success - in the absence of an upto date firmware from March for XEU - I found and installed the EUR one - BL everything went straight in and I've booted to setup screen now \o/
In Greek.... OK so hopefully I can just change language and wait for the XEU to surface (or is it OK to use the EUR? I have IMEI everything so looking good so far!)
I will probably flash Pixel Experience again unless someone recommends another over this?
Click to expand...
Click to collapse
i guess i have the same problem like u....cant flash anything...just the combination file like u.....i have the stockrom from march but i cant flash this!! Odin does "Set partition" an do nothing!...
what can i do?