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
Good evening guys!
Alright so I have this huge mess on my i535 right now where the signal for CDMA (bars) and mobile internet is just total crap.
It all started I guess when I had my phone on CM 10.2 (stable) when the signal would NEVER go past 3x. I thought that was just some error on the phone. The way I flashed the CM 10.2 was some bullcrap because I wasn't getting a certain instruction right where SuperSU/User was playing some Whack-A-Mole game where it would pop in and pop out. Because of all this bullcrap I didn't even think to use EZ Unlock to unlock the bootloader, although I think I didn't see it in the Play Store at the time and some of the Youtube videos I was watching didn't mention it. Eventually all was well though, and although 3x was slow looking back, the ROM was really stable with some minor crashing.
Earlier this past week though, I was tired and clicked away on an update to CM 10.2.1 and then another Cyanogenmod update pops up to the CM 11 snapshot. Just trying to get notifications to go away and I dirty flashed it to CM 11 by the Cyanogenmod updater and got an "Update 7" error when installing it, so I just went back into my downloads folder and re-flashed it to 10.2.1. Being in CM 10.2.1, I wasn't getting anything in terms of reception and later found out the problem was that the SIM wasn't checked under mobile networks in the settings tab, but this had resulted in my phone not getting mobile data past 1x.
Now fast forward to today and I update my CWM because of the "Update 7" error and re-flashed it to CM 11, only to find that there were times that the bars would go up to 5 and the LTE would flair up, but then it would crash down; I messed with both the Global LTE (there was a little more successes in this one in terms of the number of time LTE and better bars popped up, but didn't use it because I was scared to see if I was gonna get charged with Data Roaming) and Regular CDMA LTE (kept having 1x and bars would go up and down...), which is where it's at right now.
Okay, so then I re-flashed it to Verizon's 4.3 (finally Verizon is giving us i535 some love! right?) in an attempt to clean flash it but I had put in the VRALEC bootchain in first and softbricked me out of the recovery partition where it gave me that "Take back to Verizon store" yellow triangle warning and it was stuck for a long time at the Verizon logo until I odin'd a stock recovery 6mb tar and w00t, my phone is back, BUT I still have the same figity signals as the CM 11 and all. At this point though, my triangle count is at 4. Also in this state, my Google Play was acting hell-ish (I also got this in CM 11 too, but didn't care too much for it before); I kept getting this "Error retrieving... [RPC:S-3]" when trying to install apps and I did force stop and clear the info, but it wouldn't work. I've also gotten the RPC:S-7 too. Right now, after my mobile and signal bars being finicky as hell, it's sort of stabilized for 4 minutes (longest it's been ) to 4/5 bars with 4G LTE, but I don't know how long this will stay for.
So being very descriptive and maybe loosing some of you, here's the questions for the tl;dr for the questions.
- How can I get this reception to stabilize? It's never been this bad when my phone was stock around here. (now done with this long blob, the 1x has appeared again!)
- Any other ways on getting that RPC:S-3/S-7 in Google Play Store to go away?
- I'm planning on going to CM 11, once it gets a stable release. Kitkats are too irresistible, pun intended... Can someone please set the stone in how I should go about rooting and unlocking the bootloader? Some of the guides I used months ago were a little outdated, and I'm concerned that the old practices are over with.
Rezey said:
Good evening guys!
Alright so I have this huge mess on my i535 right now where the signal for CDMA (bars) and mobile internet is just total crap.
that the old practices are over with.
Click to expand...
Click to collapse
As I understood, you flash a stock 4.3 rom? Stock 4.3 rom locked the bootloader so no more CM11 or any custom rom for you unless you need to flash safestrap, but after this you only can flash TW custom rom. OK, now back to your issue. Since you already on factory stock rom, I would do a factory reset, the Odin a full factory 4.3 stock rom again with a PIT file and I think you should be back to normal unless CM10 is really messup your efs (a few people have this issue when flashing CM rom).
buhohitr said:
As I understood, you flash a stock 4.3 rom? Stock 4.3 rom locked the bootloader so no more CM11 or any custom rom for you unless you need to flash safestrap, but after this you only can flash TW custom rom. OK, now back to your issue. Since you already on factory stock rom, I would do a factory reset, the Odin a full factory 4.3 stock rom again with a PIT file and I think you should be back to normal unless CM10 is really messup your efs (a few people have this issue when flashing CM rom).
Click to expand...
Click to collapse
Hey, thanks for the reply!
A little update; last night I used SUA.exe with Kies drivers which re-flashed it with the factory Verizon's 4.3 and factory reset it, but now my phone will not get any sort of internet bands up and it's stuck on voice roaming which lead me to put my phone on airplane mode so that hidden charges wouldn't sneak up on me. I've even set my Mobile Network options to CDMA-LTE-EVO, but it will not get off of it.
I was just about to go onto one of the other threads and just re-root my phone, until you had told me about the locked bootloader... I'll look more into the safestrap, but this is irritating.
As with the PIT file, do I have to Odin all the VRALEC and other (I've seen a couple of odin to stock and I know rooting requires this) bootchains, to PIT file, and then 4.3? I'm not sure how that step goes... And if it did mess up my efs, what's my next step? I mean I think the i535 might be under warranty, but I'm at 4 triangle counts and I can't get those away unless if I get root permission, but I feel like having a locked bootloader might restrict me from rooting my phone, but I can be just worrying too much...
I wanna also put another update that I did flash the phone with a 16gb pit (which my phone is) file I found on another thread, but it still did not do anything. When I did use the pit file I had some security error on my phone which was in ODIN mode the first time and ODIN just kind of stood there, so then I closed it out and did again, to find that the error popped up again, but I ODIN ran through another flash. I had re-partition checked too...
I did a Wipe2 because I couldn't get the Dalvik cache cleared through Samsung's recovery partition, so I'm probably gonna get my phone rooted in the next hour and put another update because with root I'm gonna at least triangle away my phone.
Rezey said:
I wanna also put another update that I did flash the phone with a 16gb pit (which my phone is) file I found on another thread, but it still did not do anything. When I did use the pit file I had some security error on my phone which was in ODIN mode the first time and ODIN just kind of stood there, so then I closed it out and did again, to find that the error popped up again, but I ODIN ran through another flash. I had re-partition checked too...
I did a Wipe2 because I couldn't get the Dalvik cache cleared through Samsung's recovery partition, so I'm probably gonna get my phone rooted in the next hour and put another update because with root I'm gonna at least triangle away my phone.
Click to expand...
Click to collapse
You still don't under stand 4.3 rom. Once you on it the way to go back to stock rom is using full stock 4.3 and pit file. No boot chain, no once click root etc...If you want to root, you need to use saferoot. Let see if you can get back to a normal 4.3 stock with locked boot loader first. Check out this link. http://forum.xda-developers.com/showthread.php?t=2586319 . Just follow it and see if you can get back to a normal phone and there is a link on that thread for you to use saferoot to root.
buhohitr said:
You still don't under stand 4.3 rom. Once you on it the way to go back to stock rom is using full stock 4.3 and pit file. No boot chain, no once click root etc...If you want to root, you need to use saferoot. Let see if you can get back to a normal 4.3 stock with locked boot loader first. Check out this link. http://forum.xda-developers.com/showthread.php?t=2586319 . Just follow it and see if you can get back to a normal phone and there is a link on that thread for you to use saferoot to root.
Click to expand...
Click to collapse
Actually I used the Verizon utility tool from that very thread to clean root back to 4.3 and had Google Play connection error, Voice-roaming only, and no mobile data whatsoever.
I also just did saferoot on my phone and triangle'd away all my counters but yet still nothing. Did I fry my sim card? And with voice roaming always on, won't this put charges on my bill?
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,
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?