Made a mistake, will pay someone to help me fix. {Fixed} - Galaxy Note 3 Q&A, Help & Troubleshooting

I'll cut right to the chase, I've soft-bricked my Note 3 (sm-9005). I bought it off Newegg and received it Friday. I proceeded to use Chainfire's root, and then installed TWirp which worked without incident. My problem started after I installed X-Note. My system was unstable, had no sound and would make calls but not receive them. (I'm in USA, on AT&T network).
I know I should have made a backup but I didn't. (Im a Samsung fan, have owned the Note 1, Galaxy 3, and now the International Note 3). I went to sammobile and the started to realize I was in trouble. (I don't know the original CSC) It was not printed on the box, and on the back of the phone my info is the same as The guys in this thread: http://forum.xda-developers.com/showthread.php?t=2628435.
Long story short. I've tried multiple stock recoveries. Some are stuck in a bootloop (at the Samsung screen). Some will appear to work but have no sound, camera doesn't work, etc. I can still get iinto Download mode, can even reflash Twirp after screwing up. When I try other custom roms they either bootloop or half way work (no sound, crashes, etc.)
I know NewEgg won't take this phone back, and honestly since i'm still able to access it via odin I dont want to send it in IF someone here can help me get it back, and I'll pay someone $100.00 via PayPal if they can.
I have TeamViewer / Skype, or will get whatever you need to help me Via / video call, over the phone, etc.
It is 10:00am (CST) right now. I will be back here at 12:30pm (2.5 Hours) I hope someone is willing to help me with this issue. 2 days working with this and i'm at my end.

If anyone is willing to help please let me know I'll keep this page open and will be refreshing it often, in the mean time I'll keep searching forums.

Was it JB or KK when got it?
Maybe you're trying to run a KK rom when you have a JB bootloader still?
Is the knox tripped?

MystaMagoo said:
Was it JB or KK when got it?
Maybe you're trying to run a KK rom when you have a JB bootloader still?
Is the knox tripped?
Click to expand...
Click to collapse
Is on KK 4.2.2 Bootloader from Factory. I'm sure Knox was / is tripped because I had used ChainFire's root Friday night after getting the phone. Things went bad when I tried to flash X-Note yesterday.
I have reinstalled a Polish Rom (N9005XXUEND3_N9005XEOEND2_N9005XXUENC2_HOME), and it's booting up, but no sound at all, camera, etc. Also just checked, No modem, (IMEI or BaseBand) even though I flashed the above file thru Odin 3.7 [But WiFi, GPS works]
Edit #2: Downloading UK recovery firmware now.
Not that this will help, I do NOT remember anything about the country code, but /I can tell you the sticker on the back has some spanish on it, and when I started the welcome screen Friday I had to change the language from Spanish to English.
Heres a picture of the Sticker, sorry for the bad quality.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

What do you mean by no modem / IMEI. If it doesn't show any IMEI number with Sim card inserted than it's probably due to corrupt EFS. Do you have a backup of EFS?
Envoyé de mon GT-N5120 en utilisant Tapatalk

LuMe96 said:
What do you mean by no modem / IMEI. If it doesn't show any IMEI number with Sim card inserted than it's probably due to corrupt EFS. Do you have a backup of EFS?
Envoyé de mon GT-N5120 en utilisant Tapatalk
Click to expand...
Click to collapse
No I didn't make an EFS backup When I had my Note 1 there was never any mention about EFS on any rom I flashed and they all worked without issue, but i'm having a heck of a time.
Right it's showing Unknown BaseBand / or Imei under system / about.
With the UK rom it seems stable / not crashing, wifi works and I can surf, but No Cellular service, or sound, or camera.

hello there, as far as i know , csc is just customer service code or something like that, just bloatware and other stuff loaded for a specified region, an example, my device is for UAE, csc is xsi or something like that, but whats installed on the device is the polish firmware and the device is functioning properly
from what you stated that you had no idea which firmware version was installed prior to flashing the custom rom,
the following steps (may) be helpful for you
search the forums for these separate files and flash them separately, start with the modem/baseband as this is more important than sound and camera at the current time being
modem:
http://www.4shared.com/file/4YUQQVkYce/REPACK_DXUENE3_MODEM.html (credit goes to @SERGiooooo and those who extracted to files)
to flash modem go into download mode on the device and in odin select CP and unselect autoreboot, then reboot manually again to download mode and repeat and select autoreboot this time (flash it twice)
then you need to search for a compatible or recommended bootloader for your rom and flash it
and finally do a standard wipe and reinstall a rom of your choice which is compatible with your device
please keep in mind that you should only flash roms which are made for your variant( n9005 rom for n9005 and n900 for n900 and so on)
also keep in mind that some roms from sammobile.com wont be compatible (eg: hong kong nf1 is not compatible with other n9005's because of the diffrent pit )
make sure your device is 32gb n9005 and re download the rom again
finally, may i suggest to try this rom (stock based de-odexed based on ne4 and all the extra files like bootloaders and modems are included separately) and hope it solves the sound and other issues as well
http://forum.xda-developers.com/showthread.php?t=2649176
apologies for the details, this is just a suggestion coz I had the same issue with the IMEI and baseband problem
and always always do backups

I flashed singapore (NE4) stock rom (supposed to be international) from sammobile. After that, when I tried to go back to older modem my imei would be unknown, sound was messed up, and dialer would take a long time to start, but after flashing singapore modem back my imei would be there again.
It looks like that samsung is trying to block flashing of older versions of anything... Try that singapore rom (which is almost the latest available, and should flash latest everything bl, pda, csc, phone) and see if it works.

ciribic said:
I flashed singapore (NE4) stock rom (supposed to be international) from sammobile. After that, when I tried to go back to older modem my imei would be unknown, sound was messed up, and dialer would take a long time to start, but after flashing singapore modem back my imei would be there again.
It looks like that samsung is trying to block flashing of older versions of anything... Try that singapore rom (which is almost the latest available, and should flash latest everything bl, pda, csc, phone) and see if it works.
Click to expand...
Click to collapse
Downloading Now. IF you are my savior give me your PayPal Address and you'll be $100 richer. Quck question, first time I flash using Odin, just put .tar in PDA then flash, right? If I need to just flash the modem back, how do I do that?

jb0nd38372 said:
Downloading Now. IF you are my savior give me your PayPal Address and you'll be $100 richer. Quck question, first time I flash using Odin, just put .tar in PDA then flash, right? If I need to just flash the modem back, how do I do that?
Click to expand...
Click to collapse
Yes ap/pda for the whole rom, cp for modem, bl for bootloader
Good luck

Bnjalal said:
Yes ap/pda for the whole rom, cp for modem, bl for bootloader
Good luck
Click to expand...
Click to collapse
Sent you A PM, you fixed it, Just need your PayPal address. Do you have any ideas why I can't flash other roms? X-Note got me in this mess, and from what I understand it's supposedly a great rom.

You fixed it!!!!
Bnjalal said:
Yes ap/pda for the whole rom, cp for modem, bl for bootloader
Good luck
Click to expand...
Click to collapse
PM Sent, your $100 is waiting.

Easy with the money and carefully with flashing.
Yes, put it in pda, make sure that only auto reboot and f.reset time are checked, nothing else. Modem is included in the rom. If you are flashing only modem you put it in phone field. The thing is I'm not sure You'll be able to go back to old modem after you flash this one (NE3), when I tried flashing my old modem it messed up things, and flashing whole older ROM would skip flashing modem because it would detect newer already there.
Put your phone in download mode (make sure that battery is at least 60%)
Start Odin and open tar file in pda, wait a minute or two till md5 is checked when it says it's checked an ok connect your phone. I'll assume you installed samsung drivers previously. Wait a few moments here because windows might install drivers (if you have never connected your phone while in dl mode). Now there shoud be device added in ID:COM field in Odin and it should be blue/green. now you can press start.

jb0nd38372 said:
PM Sent, your $100 is waiting.
Click to expand...
Click to collapse
Sir i believe that @ciribic is the one who suggested to download the ne4 singapore stock international rom and i replied instead of him on which selection to choose in odin please verify that as i dont want to take credit on other persons work
And please accept my apologies if I caused any confusion as i was only trying to help you through the process in any means possible

Sorry
Bnjalal said:
Sir i believe that @ciribic is the one who suggested to download the ne4 singapore stock international rom and i replied instead of him on which selection to choose in odin please verify that as i dont want to take credit on other persons work
And please accept my apologies if I caused any confusion as i was only trying to help you through the process in any means possible
Click to expand...
Click to collapse
ciribic said:
Easy with the money and carefully with flashing.
Click to expand...
Click to collapse
You both helped me. I am thankful to have it back up and working. I don't understand why on my Note 1 (AT&T locked), I was able to flash every rom on that forum with no issues; Every Rom on this forum gives me BAD issues, could I have got a bad phone or something? (It was new in box, ordered from Newegg.com), but could it be defective somehow?

@ciribic I sent you a PM,
OP allow me to clear any misunderstanding with fellow members and please give all credit to him as I did nothing
now back to your question , you probably flashed roms based on recent stock TW roms and those require you to be on recent bootloaders and modems, reason for this difference is that rom builders take into consideration that the user does not want to trip his KNOX flag and may use other methods to flash the rom without using custom recovories like TWRP/CWM (ex mobile odin, safestrap) so most custom roms come without modems and bootloaders and if you unzip the x-note rom you will see that there are no bootloaders and modems included if im not mistaken
Now to get rid of any OCD related to the your device whether its faulty or not, try flashing back x-note <after> you make a complete backup in TWRP(my personal favorite) and im 95% sure that you will not have these issues anymore

ciribic said:
I flashed singapore (NE4) stock rom (supposed to be international) from sammobile. After that, when I tried to go back to older modem my imei would be unknown, sound was messed up, and dialer would take a long time to start, but after flashing singapore modem back my imei would be there again.
It looks like that samsung is trying to block flashing of older versions of anything... Try that singapore rom (which is almost the latest available, and should flash latest everything bl, pda, csc, phone) and see if it works.
Click to expand...
Click to collapse
ciribic said:
Easy with the money and carefully with flashing.
Yes, put it in pda, make sure that only auto reboot and f.reset time are checked, nothing else. Modem is included in the rom. If you are flashing only modem you put it in phone field. The thing is I'm not sure You'll be able to go back to old modem after you flash this one (NE3), when I tried flashing my old modem it messed up things, and flashing whole older ROM would skip flashing modem because it would detect newer already there.
Put your phone in download mode (make sure that battery is at least 60%)
Start Odin and open tar file in pda, wait a minute or two till md5 is checked when it says it's checked an ok connect your phone. I'll assume you installed samsung drivers previously. Wait a few moments here because windows might install drivers (if you have never connected your phone while in dl mode). Now there shoud be device added in ID:COM field in Odin and it should be blue/green. now you can press start.
Click to expand...
Click to collapse
Bnjalal said:
@ciribic I sent you a PM,
OP allow me to clear any misunderstanding with fellow members and please give all credit to him as I did nothing
now back to your question , you probably flashed roms based on recent stock TW roms and those require you to be on recent bootloaders and modems, reason for this difference is that rom builders take into consideration that the user does not want to trip his KNOX flag and may use other methods to flash the rom without using custom recovories like TWRP/CWM (ex mobile odin, safestrap) so most custom roms come without modems and bootloaders and if you unzip the x-note rom you will see that there are no bootloaders and modems included if im not mistaken
Now to get rid of any OCD related to the your device whether its faulty or not, try flashing back x-note <after> you make a complete backup in TWRP(my personal favorite) and im 95% sure that you will not have these issues anymore
Click to expand...
Click to collapse
Making that Twirp Backup as I type this, got an SD card just for that purpose now. TBH, I could care less about warranty because it won't cover Water damage, drops, misuse and that's where 99% of my past problems have happened. Knox is annoying to no end, I just got through running System Uninstaller to pull all the knox libraries / apk's and modules out.
I think i'll just stick a better optimized / open kernel on it and launcher, and call it quits. I'm 42, after these past 2 days, I feel 82.

good decision and hope u enjoy your new phone :good:

Related

[GUIDE] Manually up- or downgrade firmware

Responsibility
I am not responsible for your bricked devices, dead ad-card or anything else you did because of this guide. It is up to you, to read this guide carefully and to inform you also on other places, so that you know what you are doing and what are the risks.
If you have fear to brick your Note then better wait and take your time. The official OTA update will also came in some days.
If something goes wrong then don't hesitate and post it here. I - and surly others - will try to help you.
Upgrade
I didn't want to wait for the next OTA update to MK1 (which include user management and other improvements). So, I start to update manually and because I didn't find clearly answers here in the forum, I make afterwards this guide.
This guide should work for all different kind of 10.1 Notes Edition 2014 (WiFi only, GSM, LTE) so long you download the corresponding, correct firmware for your Note version. I did it for a P600 (WiFi only) and it works without any issues.
Results
Updated to newest firmware (MK1)
Normally you don't lose your data and configuration just as by a OTA update. But make however a backup of everything for the case something goes wrong and you have to made a factory reset!
Still everything is working what I use. I didn't and can't test everything and maybe something is not longer working because of the region switch.
The warranty bit is still 0 (after the update):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Preparation
First we need the firmware, we want to flash to our Note. I got mine from here: Sammobile but you can get it also from here: Samsungis.
You can find a list of all firmwares for your Note model by searching. In the list I choose the newest one for the MK1 update also it is for a different region. Until now I didn't see any issues because of this region switch.
Issue is maybe that you can't download here the firmware because both sides use hotfile for file hosting. Here you can use the pCloud service. I did it and from there I could download the file.
Next we need some tools: Odin (I use version 3.09) and maybe a Samsung usb driver (I got mine because of an earlier installed Kies). There are many places where you can find Odin but I got mine from here: Odin 3.09 (xda).
If you don't have a Windows computer in your reach then there are also tools for MacOS and Linux but I didn't test any of them!
A Samsung USB driver which by example is installed when you install the Kies application from Samsung.
Upgrading
There are many good tutorials for using the Odin application. Therefore I will only describe in a nutshell what I did. When you search for a more detailed guide then you can use one of them: Samsungsi: Using Odin, rootSU (xda): Odin flash guide. They also exists in other languages, you are free to use a search tool.
Start Odin as administrator
Connect the Note via USB too the computer and check that Odin got a connection: One of the ID:COM fields should contain the port number and also the background should be blue (or yellow if you use an older Odin version).
Press the AP (PDA in older versions) button to add the downloaded firmware (tar.md5). In the message box you should see (depending from your Odin version):
Code:
...
<OSM> Please wait...
<OSM> (*) is valid
<OSM> Checking MD5 finishes Successfully...
<OSM> Leave CS..
(*) the filename of your firmware download.
Power-off the Note and wait for 1 minute (I didn't understand this step but found it in some guides)
Hold the power and volume down button pressed until you see the triangle screen.
Press the volume up button to go to the download mode (Odin mode):
New press the Start button in Odin and wait until flash is down. Be very carefully here!
And no, I don't have any photos to show what happens now. Look into other more detailed Odin guides.
At the end the Note reboot by his own and the update is done :laugh:
When something goes wrong then look in the tutorials, how to solve it.
Downgrade
A downgrade works in the same way with Odin. So, you can download an older firmware and flash it in the same way with Odin.
You can here also use Kies to recover an old firmware and Kies download the correct version for you. I try this with the current Kies version 3 for Windows and MacOS and with both it works.
Special thanks to
xda for his great community
Sammobile for the firmware
beanstown106, bigbiff, nrage23 and many others here in the forum for their knowledge and help
lap777 for correction on this guide
rootSU for his Odin guide
F.A.Q
Will the warranty bit change to 1?
As you can see above mine is still 0. I also expect this because with this guide we flash a by Samsung signed firmware. But I read also in other guides for other devices that in some cases the bit is increased to 1. So, don't be surprised when this happens.
Can I get system status 'Official' back?
Yes, with both methods from above, you got current binary: 'Samsung Official' and system status: 'Official' back after you flash a custom recovery or ROM. Only the warranty bit will in this case stay 1.
I would have thought the AP button (PDA?), not CP (Phone/modem?). Sorry, I'm new at this
lap777 said:
I would have thought the AP button (PDA?), not CP (Phone/modem?). Sorry, I'm new at this
Click to expand...
Click to collapse
We are all new to this and you are right. Next time I write my guide in parallel.
PS. The guide is corrected.
I’m wandering if i can flash different regional version and donot trigger knox?
yobyzal said:
I’m wandering if i can flash different regional version and donot trigger knox?
Click to expand...
Click to collapse
I, like others, did it (the MK1 is only for some regions available) and didn't trigger knox. Like I said, this firmwares (from the sources above) are the original ones which are still signed by Samsung. If you flash something with a custom recovery or already rooted than this will not be the case and you will trigger knox.
PS. If you have also an P600: I flash "P600UEUBMK1_P600XARBMK1_HOME.tar.md5" which is for region "Cellular south" which is surly not "Luxembourg".
PPS. And until now I didn't have any other problem because of the different region.
PPPS. In the meantime I rooted my Note and trigger therefore knox. But also this seems no problem for me. I can still flash the stock firmware and got then OTAs (set bit is still set to 1). And the warranty will be still given for 6 month in Europa. Only extra guaranties by Samsung will be maybe a problem. And here I didn't care.
I can confirm that the method provided in this guide has updated my Galaxy Note 10.1 (2014 German Edition) to firmware version MK1 without triggering Knox. Warranty bit still 0.
sbeanie said:
I can confirm that the method provided in this guide has updated my Galaxy Note 10.1 (2014 Edition), German Edition, to firmware version MK1 without triggering Knox. Warranty bit still 0.
Click to expand...
Click to collapse
Congratulations. And German Edition is the original edition for your device, right?
yobyzal said:
Congratulations. And German Edition is the original edition for your device, right?
Click to expand...
Click to collapse
Yes my device was bought in Germany.
my p600was tripped by just flashing the stock firmware again using Odin.
moom999 said:
my p600was tripped by just flashing the stock firmware again using Odin.
Click to expand...
Click to collapse
What did you mean with "again"? (a) you flash it again and then it was tripped or (b) it was already tripped and after flashing was not changed?
b) will be normal because this flag will stay on 1 for ever
I flashed yesterday without tripping Knox.
Maybe I should try this too. Tired of waiting for OTA. Samsung support gave me a generic "we are looking into this matter" reply so my guess is they are totally clueless about eta of MK1 in Europe and probably don't even understand what I'm talking about...
Elim said:
What did you mean with "again"? (a) you flash it again and then it was tripped or (b) it was already tripped and after flashing was not changed?
b) will be normal because this flag will stay on 1 for ever
Click to expand...
Click to collapse
I flashed the stock firmware again then it was tripped
Now I flashed different regional version and the result shows that WARRANTY BIT still be zero.:victory:
home button problem
Is anyone else having problems with their home button not working? I press the home button and it doesnt take me to my "home screen" but it will wake up and return back to the screens from the app drawer. If anyone else has the same problem let me know if you have came to a solution. Thanks
osbrandon said:
Is anyone else having problems with their home button not working? I press the home button and it doesnt take me to my "home screen" but it will wake up and return back to the screens from the app drawer. If anyone else has the same problem let me know if you have came to a solution. Thanks
Click to expand...
Click to collapse
Way to bump a 5 month old thread with a completely unrelated problem. Good work.
osbrandon said:
Is anyone else having problems with their home button not working? confused
Click to expand...
Click to collapse
Yes, you seem to be a little bit confused because this topic has nothing do with your question and otherwise this question is already asked many times.
Stock firmware includes the stock recovery?
Which is the correct Country/Carrier for the US?
Elim said:
What did you mean with "again"? (a) you flash it again and then it was tripped or (b) it was already tripped and after flashing was not changed?
b) will be normal because this flag will stay on 1 for ever
Click to expand...
Click to collapse
Will this work or have you heard if it working for the new Verizon LTE model...mine came with 442 and would like to downgrade so I can root & custom recovery? But I dont see US firmware listed by Samsung lloks like they remvoed it.

[Q] Note 3 Live demo unit N900x Please help me

I have Samsung galaxy note 3 N900x
live Demo Unit
And they contain Samsung Retail Mode
And have downloaded the software through Odin V3.09 N9005XXUBMI7_N9005OJVBMI2_N9005XXUBMI6_HOME. Tar
But when you start re-operating and not work only restart and open then restart
What is the solution Please help me and can i download the software for samsung galaxy note 3 live demo unit n900x
Is there a copy Software runs it
And be compatible with Note3 n900x live demo unite
Please help me
http://forum.xda-developers.com/attachment.php?attachmentid=2401639&d=1384849574
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Lol so you have a not for sale demo unit..... and you want to flash a Rom on it. Cool
Sent from my ??????? Note 3
N900X Demo Unit unbrick
deeznutz1977 said:
Lol so you have a not for sale demo unit..... and you want to flash a Rom on it. Cool
Sent from my ??????? Note 3
Click to expand...
Click to collapse
Here my pack for bring back demo unit to work.
h__ps://cloud.mail.ru/public/99b243c8a2bb/n900x
This is mix from demo BL and Emirates firmware.
Works everything except GSM and GPS (There is no modem parts on the board)
Just flash it by Odin 3.07 or 3.09
If free memory will be about 19GB, do the full wipe and reflash.
hi
Brappa said:
Here my pack for bring back demo unit to work.
h__ps://cloud.mail.ru/public/99b243c8a2bb/n900x
This is mix from demo BL and Emirates firmware.
Works everything except GSM and GPS (There is no modem parts on the board)
Just flash it by Odin 3.07 or 3.09
If free memory will be about 19GB, do the full wipe and reflash.
Click to expand...
Click to collapse
hi brappa, i have in my hands a i9200x demo unit, i have a tool called spt that comes with the firmwares form support in parts so i flashed i9200XXUAME7, without the modem part,
all is ok, but i only have 2.38gb, so i tried the only pit i have found of 16gb, and bricked it, made a backup pit from another i9200x, and flashed to the bricked, and all ok, so how can i know the real memory capability of the demo unit, 8gb 16 or 32, can you help me, or should i install twrp or cwm and try a rom, for the galaxy mega.
thank you very much indeed for your attention
atv
oh
atv said:
hi brappa, i have in my hands a i9200x demo unit, i have a tool called spt that comes with the firmwares form support in parts so i flashed i9200XXUAME7, without the modem part,
all is ok, but i only have 2.38gb, so i tried the only pit i have found of 16gb, and bricked it, made a backup pit from another i9200x, and flashed to the bricked, and all ok, so how can i know the real memory capability of the demo unit, 8gb 16 or 32, can you help me, or should i install twrp or cwm and try a rom, for the galaxy mega.
thank you very much indeed for your attention
atv
Click to expand...
Click to collapse
and when i run app2sd this is the msg
this device does not have a real primary external storage, or the primary external storage is emulated.
moving app to sd function may not be supported by this device.
Brappa said:
Here my pack for bring back demo unit to work.
h__ps://cloud.mail.ru/public/99b243c8a2bb/n900x
This is mix from demo BL and Emirates firmware.
Works everything except GSM and GPS (There is no modem parts on the board)
Just flash it by Odin 3.07 or 3.09
If free memory will be about 19GB, do the full wipe and reflash.
Click to expand...
Click to collapse
Work perfect in a Live unit Note 3
Thanks You!!!!!! :victory:
Brappa said:
Here my pack for bring back demo unit to work.
h__ps://cloud.mail.ru/public/99b243c8a2bb/n900x
This is mix from demo BL and Emirates firmware.
Works everything except GSM and GPS (There is no modem parts on the board)
Just flash it by Odin 3.07 or 3.09
If free memory will be about 19GB, do the full wipe and reflash.
Click to expand...
Click to collapse
Hello,
sorry but I'm little unclear;
so this demmo unit is like all other demmo units from Samsung?
If the IMEI is repaired still the gsm won't work because the radio part is missing from the mainboard ilke is in i9300?
You mentioned about the modem part missing from the mainboard.
Is different in the case of N990x?
Thanks!
MarianG said:
Hello,
sorry but I'm little unclear;
so this demmo unit is like all other demmo units from Samsung?
If the IMEI is repaired still the gsm won't work because the radio part is missing from the mainboard ilke is in i9300?
You mentioned about the modem part missing from the mainboard.
Is different in the case of N990x?
Thanks!
Click to expand...
Click to collapse
In this case all the same.
Modem part is missing on the board.
There is special modem part in demo firware with fake modem software, which allows android to work in normal phone mode.
Because of missing modem part original firmware hangs and reboots.
i just flash the o2 german firmware 4.4.2 and it works for me..stop booting, storage is a bout 15 gb...everything work only the gsm not work.,.but i see that post http://forum.gsmhosting.com/vbb/f258/i9300x-live-demo-unit-working-gsm-solved-1686313/ and some guy make it work his i9300 demo unit...is there a way to do that?
---------- Post added at 08:41 AM ---------- Previous post was at 08:39 AM ----------
or any body please tell me what parts of the mainboard are missin...in my mainboard only where i connect the anntena is missing...
Mr
Brappa said:
Here my pack for bring back demo unit to work.
h__ps://cloud.mail.ru/public/99b243c8a2bb/n900x
This is mix from demo BL and Emirates firmware.
Works everything except GSM and GPS (There is no modem parts on the board)
Just flash it by Odin 3.07 or 3.09
If free memory will be about 19GB, do the full wipe and reflash.
Click to expand...
Click to collapse
Dear brappa,
I also have Samsung Galaxy Note 3, I flashed it with a real firmware, not the set is restarting continoiusly,
which file should i use ( 1.3gb or 50mb) as mentioned by you.
Thanks in advance
I got the same problem... If u can tel me what files should i use plz...
edited original firmware note 3 live demo unit
I got mine working again after real firmware flash, got an unknown baseband. After lots of search came by this ://cloud.mail.ru/public/99b243c8a2bb/n900x, flash it with the 4 files and voila everything going back to normal n even dectect simcard but still no imei so no network... Enjoy
[email protected] said:
I got mine working again after real firmware flash, got an unknown baseband. After lots of search came by this ://cloud.mail.ru/public/99b243c8a2bb/n900x, flash it with the 4 files and voila everything going back to normal n even dectect simcard but still no imei so no network... Enjoy
Click to expand...
Click to collapse
Please a little advice would be useful .After i flashed with odin 3.0.7 this emirates rom i have the same problems like some users reported .It` s restarting continuosly and i cannot enter recovery mode only donloading mode.
I placed the AP_N9005XXUDMJ7_2019540_REV03_user_low_ship_MULTI_CERT.tar.md5 which i extracted from the archive (2.2 gb after extraction ) at PDA section as i previous did with other devices ....and the pit file at pit section .Auto reboot ,repartion,f reset time marked.
And after that all seemed to be succesful but i don`t know why isn`t working and i only get the neverending reboots.
You said .flash it with the 4 files ,but what is the exact procedure ....i only placed 2 file .....where should i place the other 2 !?
Thanks in advance.Kind regards
leo_hacker82 said:
i just flash the o2 german firmware 4.4.2 and it works for me..stop booting, storage is a bout 15 gb...everything work only the gsm not work.,.but i see that post http://forum.gsmhosting.com/vbb/f258/i9300x-live-demo-unit-working-gsm-solved-1686313/ and some guy make it work his i9300 demo unit...is there a way to do that?
---------- Post added at 08:41 AM ---------- Previous post was at 08:39 AM ----------
or any body please tell me what parts of the mainboard are missin...in my mainboard only where i connect the anntena is missing...
Click to expand...
Click to collapse
Did you use the O2 German firmware 4.2.2 in your Live Demo Unit ? if it works perfectly for you , can you please share that firmware ?
---------- Post added at 11:38 PM ---------- Previous post was at 11:35 PM ----------
Brappa said:
Here my pack for bring back demo unit to work.
h__ps://cloud.mail.ru/public/99b243c8a2bb/n900x
This is mix from demo BL and Emirates firmware.
Works everything except GSM and GPS (There is no modem parts on the board)
Just flash it by Odin 3.07 or 3.09
If free memory will be about 19GB, do the full wipe and reflash.
Click to expand...
Click to collapse
Thank you very much for this firmware, just a small question , is it Android 4.4.2 ?
brayann16k said:
Did you use the O2 German firmware 4.2.2 in your Live Demo Unit ? if it works perfectly for you , can you please share that firmware ?
---------- Post added at 11:38 PM ---------- Previous post was at 11:35 PM ----------
Thank you very much for this firmware, just a small question , is it Android 4.4.2 ?
Click to expand...
Click to collapse
So here is my saga with demo unit.
I got phone with demo firmware on it few weeks ago. I flashed latest Germany firmware and had various hangs/reboots whenever i try to play some video (in youtube app, in facebook app, in browser) , or record video with camera.
So i started to flash random custom roms, and was pretty satisfied ( had smallest number of reboots) with CM 11. But still this hangs were happening, usually when i leave phone on charger or not use it much.
Than i came to this thread and i tried to flash this 4 files. But i couldnt because it is 4.3 based rom and i couldnt flash bootloader.
Odin gives me an error on the beginning of flashing. So i tried to flash 3 files without bootloader and after odin finished i was stuck in bootloop.
The only solution to get phone back working is to flash stock firmware from sammyfirmware including with .pit file and repartition.
But now i have other problem, bunch of reboots, even on custom roms. Camera gives "Warning: Camera Failed!" I tried few stock roms and few custom roms and not luck with camera.
So my questions are:
Is there anywhere Live Demo Unit Firwmare that i can flash on phone to revert it back?
Is there any regular firmware that have this 4 files separated ( Bootloader, PDA, Phone, CSC) or how to make one, to try to get at least this camera working, as im thinking that flashing them separately broke my camera?
Anyone else got Live Demo Unit working with some stock rome without this reboots/hangs?
[/COLOR]
ul71m0 said:
So here is my saga with demo unit.
I got phone with demo firmware on it few weeks ago. I flashed latest Germany firmware and had various hangs/reboots whenever i try to play some video (in youtube app, in facebook app, in browser) , or record video with camera.
So i started to flash random custom roms, and was pretty satisfied ( had smallest number of reboots) with CM 11. But still this hangs were happening, usually when i leave phone on charger or not use it much.
Than i came to this thread and i tried to flash this 4 files. But i couldnt because it is 4.3 based rom and i couldnt flash bootloader.
Odin gives me an error on the beginning of flashing. So i tried to flash 3 files without bootloader and after odin finished i was stuck in bootloop.
The only solution to get phone back working is to flash stock firmware from sammyfirmware including with .pit file and repartition.
But now i have other problem, bunch of reboots, even on custom roms. Camera gives "Warning: Camera Failed!" I tried few stock roms and few custom roms and not luck with camera.
So my questions are:
Is there anywhere Live Demo Unit Firwmare that i can flash on phone to revert it back?
Is there any regular firmware that have this 4 files separated ( Bootloader, PDA, Phone, CSC) or how to make one, to try to get at least this camera working, as im thinking that flashing them separately broke my camera?
Anyone else got Live Demo Unit working with some stock rome without this reboots/hangs?
Click to expand...
Click to collapse
I have a perfectly stable note 3 demo unit. If you are aware of any method to backup the full rom without rooting or unlocking bootloader I would send you the files. I am scared to root or unlock the bootloader because if I softbrick my phone I wouldn't be able to restore my phone without the stock rom and I cannot find a reliable stock rom online....I am a noob so please use noob (simple) language in reply
fahim1040 said:
[/COLOR]
I have a perfectly stable note 3 demo unit. If you are aware of any method to backup the full rom without rooting or unlocking bootloader I would send you the files. I am scared to root or unlock the bootloader because if I softbrick my phone I wouldn't be able to restore my phone without the stock rom and I cannot find a reliable stock rom online....I am a noob so please use noob (simple) language in reply
Click to expand...
Click to collapse
Hi Fahim, thank you for your offer, do you have unit with demo software?
After a lot of flashing i found some combination that works for me, im still not sure what i did, but it was really anoying to download and flash so many firmwares.
I got my camera working normal, and only freeze im getting is when going to video mode, and usually only when device is just turned on. The are 50% chances to get reboot when using video on fresh booted device. Im not sure how to fix this but it is acceptable for me to have or like this.
Than again i would like to have rock stable device and i currently only way, that i know, to backup your current room is with custom recovery...
I will research a bit on this and let you know if i find easier way, but rooting and recovery are really simple 2 minute process.
Just to confirm you have SM-N9005? When i take off back of the phone in down left corner on plastic under the battery it writes SM-N9005 and same model is written on screen while booting the device.
Thanks again for your effort.
Sent from my Nexus 7 using Tapatalk
ul71m0 said:
Hi Fahim, thank you for your offer, do you have unit with demo software?
After a lot of flashing i found some combination that works for me, im still not sure what i did, but it was really anoying to download and flash so many firmwares.
I got my camera working normal, and only freeze im getting is when going to video mode, and usually only when device is just turned on. The are 50% chances to get reboot when using video on fresh booted device. Im not sure how to fix this but it is acceptable for me to have or like this.
Than again i would like to have rock stable device and i currently only way, that i know, to backup your current room is with custom recovery...
I will research a bit on this and let you know if i find easier way, but rooting and recovery are really simple 2 minute process.
Just to confirm you have SM-N9005? When i take off back of the phone in down left corner on plastic under the battery it writes SM-N9005 and same model is written on screen while booting the device.
Thanks again for your effort.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
true..my demo unit is as stable as a rock.haven't had any issues with it. I do not know which firmware is in it. When switching the device on, it displays Samsung galaxy note iii sm-n9005 and in the back under the battery it says sm-n900x..I do not want to unlock the bootloader and root without backing up the ROM. As I said I am a newbie to android so I am scared to root. btw if I do want to root what files do I use?..I can only find the files and instruction for rooting a n9005 not n900x.
few question though..
1)do you think a regular note 3 firmware with the radio/modem files of my device make a stable demo unit? As far as I know the phone boot loops when a ordinary n9005 firmware is installed because it cannot find the gsm/cdma/hspa modem.
2)Is it going to be possible to flash the modem files separately for overwriting the stock modem files after installing a ordinary n9005 firmware. how?
3)are the kernels, pit files and modem/radio files included in a firmware and also nandroid backup or does one have to flash them separately.
fahim1040 said:
true..my demo unit is as stable as a rock.haven't had any issues with it. I do not know which firmware is in it. When switching the device on, it displays Samsung galaxy note iii sm-n9005 and in the back under the battery it says sm-n900x..I do not want to unlock the bootloader and root without backing up the ROM. As I said I am a newbie to android so I am scared to root. btw if I do want to root what files do I use?..I can only find the files and instruction for rooting a n9005 not n900x.
few question though..
1)do you think a regular note 3 firmware with the radio/modem files of my device make a stable demo unit? As far as I know the phone boot loops when a ordinary n9005 firmware is installed because it cannot find the gsm/cdma/hspa modem.
2)Is it going to be possible to flash the modem files separately for overwriting the stock modem files after installing a ordinary n9005 firmware. how?
3)are the kernels, pit files and modem/radio files included in a firmware and also nandroid backup or does one have to flash them separately.
Click to expand...
Click to collapse
It is really few click process to root and install custom recovery. And than with it you can do nandroid backup and play with custom roms. But my advice is leave it as is because its hard to find rock stable rom, its just not worth it. If i just knew i would have never do it.
If you want to root i have uploaded all the files that you will need here:
https://dl.dropboxusercontent.com/u/61307734/odin + cf-root + twrp.zip
In that archive there are:
- Odin307.zip - You will need to unzip this and start Odin3 v3.07.exe
- CF-Auto-Root-hlte-hltexx-smn9005.tar.md5 this is file that you will use for rooting no need to uncompress anything
- openrecovery-twrp-2.7.2.0-hltetmo-4.4.img.tar this is file that you will use for custom recovery, again no need to uncompress anything
So if you want guide how to root here are steps taken from original thread:
- Download archive that i linked above and unzip it
- (USB) Disconnect your phone from your computer
- Start Odin3-vX.X.exe
- Click the PDA button, and select CF-Auto-Root-....tar.md5
- Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue, press the listed button, or run adb reboot download command)
- (USB) Connect the phone to your computer
- Make sure Repartition is NOT checked
- Click the Start button
- Wait for Android to boot
- Done (if it took you more than 30 seconds, you need practise!)
And for custom recovery, steps are pretty much the same as above you just use twrp file instad of cf-auto-root here is original thread again here are steps:
- Extract the archive i attached here
- (USB) Disconnect your phone from your computer
- Start Odin3-vX.X.exe
- Click the PDA button, and select openrecovery-twrp-2.7.2.0-hltetmo-4.4.img.tar
- Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue, press the listed button, or run adb reboot download command)
- (USB) Connect the phone to your computer
- Make sure Repartition is NOT checked
- Click the Start button
- Wait for Android to boot
- Done (if it took you more than 30 seconds, you need practise!)
After you have done this 2 things you will have rooted phone with custom recovery and than you can create nandroid backup before you start playing with custom roms.
To enter recovery mode you will turn off phone, then hold VolUp+Home+Power to boot into recovery mode and there you just select Backup. And just to be safe select all partritions:
- Boot
- Recovery
- System
- Data ( this one you will skip when creating backup for me because i dont need your data )
- Cache
- EFS
- Modem
And than just slide do backup and wait it to finish and reboot it to system. You will have folder called TWRP next time you attach your device to a computer, and in it there is subfolder backup where you backup files are stored. Than you can use dropbox or something like https://www.wetransfer.com/ to share file with me.
If you need any help with this PM me i will be glad to help you with whole process, but its pretty simple, i have done it lots of times so far no problems.
No need to worry friends I found a simple solution but sim card not work..
And ur firmware is 4.3 and u can use everything mx player youtube camera xposed module and wanam xposed..
No problem at all..

[GUIDE] Baseband/Radio "stuck" and not updating? Here's how to fix it!

Okay, so I've had this issue for a few months now where no matter what I tried, I could not update my Baseband. I tried everything I could think of - flashed the full stock Rom, used mobile ODIN, flashed twice, etc. but no matter what, the baseband would stick to the old one. I tried googling and looking around but the same tricks as above were posted again and again to no avail.
I eventually found the answer, it was a single post buried in a thread on here. As I keep seeing posts from other users with the same issue, I figured I'd write a quick guide so that hopefully those searching for the problem will find it.
So to reiterate - you've just updated to a new firmware (custom or otherwise) but your radio (aka baseband) has not changed. You then try to flash the radio directly but it still won't change. What gives?
Well to fix it, you're going to need the following:
Odin 3.07
Triangle Away (Thanks to Chainfire, as always)
A Method of rooting your device (I'm leaving this up to you as it's a warranty voiding experience and I presume you know how to do that by this point).
An official Samsung firmware containing the radio you want to update to
If you're currently on an AOSP based ROM, then I have bad news - you'll need to flash back to touchwiz to do this. Once you're done, you can flash back though.
Remember to make a backup of all your data, as you will be doing a lot of flashing here.
Note: You may be able to fix your stuck radio problem without flashing back to a completely stock firmware and cutting corners elsewhere, however I wanted this guide to be bulletproof, deviating slightly may produce different results. If all else fails, follow each step below exactly!
Remember: This guide is specifically for those of you who have tried other methods and are still stuck on an old baseband. If you're just looking how to flash your radio, there are easier and less involved methods that don't require any wiping - I strongly advise you to try those first.
Okay, by this point I'm going to assume you've done all your backups and are ready to start flashing.
Step 1: Reboot your phone into DOWNLOAD mode (aka Odin). To do this, hold down POWER, VOL-DOWN and HOME at the same time until you see the following screens:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Remember to let go of the above buttons and press "volume up" to continue.
Step 2: Open up Odin 3.07, click on the "PDA" button and select the stock firmware file you have downloaded (file should have a ".tar.md5" extension, if you downloaded a .zip file you'll need to extract it but DO NOT EXTRACT MORE THAN THIS, you want a single .tar.md5 file).
Step 3: With your phone connected to your PC running ODIN, click "start". This will take a few mins, so be patient.
Step 4: Root. Now your phone should be rebooting into some pretty awful stock Samsung firmware. Boo. However this is a necessary evil. Here you need to root your phone. CF-Auto-Root is my preferred method but this trips Knox so do what you feel is best.
Step 5: Install and run Triangle Away. Triangle Away requires a Stock samsung kernel, which is why you've just flashed a full Samsung firmware. Triangle away requires root, which is why you've just performed Step 4.
Step 6: Install the Stock Firmware. Again.
That's right, repeat steps 2 and 3 once more to flash that stock Samsung firmware all over again. Except this time, your system is reporting that it's "official" and TriangleAway has cleared some flags that were preventing the updated radio from installing. When your phone reboots, your radio should have updated.
You're done! From here, you can do whatever you like - flash another custom ROM (you're still rooted at this point), wipe and restore a backup you made earlier, switch to AOSP or whatever. Personally, I would go buy Chainfire a beer as TriangleAway is what makes this all possible.
Nice....it helped me :good:
Thanks :highfive:
neoKushan said:
Okay, so I've had this issue for a few months now where no matter what I tried, I could not update my Baseband. I tried everything I could think of - flashed the full stock Rom, used mobile ODIN, flashed twice, etc. but no matter what, the baseband would stick to the old one. I tried googling and looking around but the same tricks as above were posted again and again to no avail.
I eventually found the answer, it was a single post buried in a thread on here. As I keep seeing posts from other users with the same issue, I figured I'd write a quick guide so that hopefully those searching for the problem will find it.
So to reiterate - you've just updated to a new firmware (custom or otherwise) but your radio (aka baseband) has not changed. You then try to flash the radio directly but it still won't change. What gives?
Well to fix it, you're going to need the following:
Odin 3.07
Triangle Away (Thanks to Chainfire, as always)
A Method of rooting your device (I'm leaving this up to you as it's a warranty voiding experience and I presume you know how to do that by this point).
An official Samsung firmware containing the radio you want to update to
If you're currently on an AOSP based ROM, then I have bad news - you'll need to flash back to touchwiz to do this. Once you're done, you can flash back though.
Remember to make a backup of all your data, as you will be doing a lot of flashing here.
Note: You may be able to fix your stuck radio problem without flashing back to a completely stock firmware and cutting corners elsewhere, however I wanted this guide to be bulletproof, deviating slightly may produce different results. If all else fails, follow each step below exactly!
Okay, by this point I'm going to assume you've done all your backups and are ready to start flashing.
Step 1: Reboot your phone into DOWNLOAD mode (aka Odin). To do this, hold down POWER, VOL-DOWN and HOME at the same time until you see the following screens:
Remember to let go of the above buttons and press "volume up" to continue.
Step 2: Open up Odin 3.07, click on the "PDA" button and select the stock firmware file you have downloaded (file should have a ".tar.md5" extension, if you downloaded a .zip file you'll need to extract it but DO NOT EXTRACT MORE THAN THIS, you want a single .tar.md5 file).
Step 3: With your phone connected to your PC running ODIN, click "start". This will take a few mins, so be patient.
Step 4: Root. Now your phone should be rebooting into some pretty awful stock Samsung firmware. Boo. However this is a necessary evil. Here you need to root your phone. CF-Auto-Root is my preferred method but this trips Knox so do what you feel is best.
Step 5: Install and run Triangle Away. Triangle Away requires a Stock samsung kernel, which is why you've just flashed a full Samsung firmware. Triangle away requires root, which is why you've just performed Step 4.
Step 6: Install the Stock Firmware. Again.
That's right, repeat steps 2 and 3 once more to flash that stock Samsung firmware all over again. Except this time, your system is reporting that it's "official" and TriangleAway has cleared some flags that were preventing the updated radio from installing. When your phone reboots, your radio should have updated.
You're done! From here, you can do whatever you like - flash another custom ROM (you're still rooted at this point), wipe and restore a backup you made earlier, switch to AOSP or whatever. Personally, I would go buy Chainfire a beer as TriangleAway is what makes this all possible.
Click to expand...
Click to collapse
No need this,too complicated。
Only turn off the phone, then remove the battery ,
install it
and get into download model ,
Flash the radio.
that you can update the baseband
nforce4 said:
No need this,too complicated。
Only turn off the phone, then remove the battery ,
install it
and get into download model ,
Flash the radio.
that you can update the baseband
Click to expand...
Click to collapse
Thanks, but unfortunately that didn't work for me.
neoKushan said:
Thanks, but unfortunately that didn't work for me.
Click to expand...
Click to collapse
Turn off your phone manually. Leave it for 10 sec, dont need to remove battery, Put the modem on Phone, NOT PDA connect your phone and flash it. It is simple.
IzArsha said:
Turn off your phone manually. Leave it for 10 sec, dont need to remove battery, Put the modem on Phone, NOT PDA connect your phone and flash it. It is simple.
Click to expand...
Click to collapse
Believe me when I say that I tried that, I tried just about everything before it would finally stick. Removing battery, leaving it off for 10s+ (I did this numerous times as TriangleAway demands it due to the risk if bricking your phone and one time left it off/unplugged for a good 20mins to no avail). There was some kind of write protection in place, Mobile ODIN (yeah tried that as well) mentioned it when trying to flash the Radio - hence why TriangleAway is needed.
Before it got "Stuck", I had manually updated my Modem a few times without issue. I've had the Note 3 since launch and voided Knox within about 2 days of getting it - believe me, I've been there and done that
Nothing worked for me also until I tried this method...
Sent from my SM-N9005 using XDA Premium 4 mobile app
Here's what I don't like, and what I "Do" Like...
Like....
1) A post in the proper forum that seems to help a few people fix their issue when other methods didn't seem to work.
Dislike...
1) Somebody coming in touting their own method (which may or may not work for a particular user). This, believe it or not, only adds to confusion when a person looks for an answer. Now there are different methods in the same thread topic.
2) 2 pages of back and forth arguing as a result of the above ^^^
So, I'll delete all posts concerning this debate on procedures.
Folks, don't go poaching other users threads please. If they provide a solution that helps a few users, then that is GREAT!!! Not all normal solutions work for all users. Stick around long and you will discover this on your own one day.
Cleaned thread, please don't make me come back and do it again.
MD
Thanks Moscow. I apologise for what happened, I didn't mean to cause a fuss.
To show there's no hard feelings, I've updated the OP with a warning that this is specifically for those who are still stuck after trying out other methods. Hopefully that's enough to keep everyone happy.
neoKushan said:
Thanks Moscow. I apologise for what happened, I didn't mean to cause a fuss.
To show there's no hard feelings, I've updated the OP with a warning that this is specifically for those who are still stuck after trying out other methods. Hopefully that's enough to keep everyone happy.
Click to expand...
Click to collapse
Much better. I didn't mean to start an argument... But it happened somehow.
Good detailed guide however. See you around XDA.
I'm having Baseband: Unknown issue, and flashing different modems are not changing it.
Can this method help ?
thanks
MuhammadZeeshan7 said:
I'm having Baseband: Unknown issue, and flashing different modems are not changing it.
Can this method help ?
thanks
Click to expand...
Click to collapse
Hmm, I really don't know man. I've not seen that error before so I can't comment. Perhaps this can help?
neoKushan said:
Hmm, I really don't know man. I've not seen that error before so I can't comment. Perhaps this can help?
Click to expand...
Click to collapse
I've done almost every method, but not yours. BTW I don't have any other triangle icon except the yellow triangle at the start of Download mode.
MuhammadZeeshan7 said:
I'm having Baseband: Unknown issue, and flashing different modems are not changing it.
Can this method help ?
thanks
Click to expand...
Click to collapse
Unpack the tar file, and flash just the modem.bin into phone (not pda) in Odin.
not working on SM-N900w8
Didn't work on my note 3 sm-n900w8, modem still previous version :crying:
any other suggestion please?
jsecruzvalencia said:
Didn't work on my note 3 sm-n900w8, modem still previous version :crying:
any other suggestion please?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=53632129&postcount=1
In the first box.

"Not registered on network" SM-N910F

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Help me out guys.
Recently, I updated my phone to the BOD2 ROM as repackaged by @_alexndr. I have always used his repackaged ROMs since BOB4 days and its always went super well so I doubt its the cause of my issue.
I updated bootloader to BOD2 and the repacked BOC4 modem respectively. It worked well, super fast, I received call, sent SMS and used data until the following day when my network services just stopped working.
Can't send SMS, can't make calls, cant use data. I've changed sim cards to other networks but its the same thing. "Emergency call only".
In addition to that, this message is always sent to my most recently contacted person via SMS although it never goes through.
I have gone back to KitKat to see if it will solve it but it didn't. I tried different modems but it won't work. I'm not back on the BOD2 firmware.
What can I do please?
Your IMEI is correct?
Sent from my SM-N910G using xda premium
dr.ketan said:
Your IMEI is correct?
Sent from my SM-N910G using xda premium
Click to expand...
Click to collapse
Yeah. Checked my IMEI. It matches the one on the box of the phone. My serial number is also matching with the one on the box.
On the status section of the phone, it says
Voice: Out of service / Data: Out of service
SleemLDJ said:
Help me out guys [...]
Click to expand...
Click to collapse
Unfortunately, anyway - it looks like EFS and/or related ID partitions damage. It usually happen for users with root and/or custom recovery, e.g. immediately after flashing a ZIP file. Fortunately, users with root can easy backup EFS + related ID partitions and easy restore it in such emergency case.
1. If you rooted your phone in the past and created the backup of all sensitive ID partitions - just restore it using same tool as you used for backup
2. If you never rooted your phone and still have KNOX 0x0 - the best way is warranty repair in an authorized service center (with a high probability - on the spot). Authorized services have tools to rebuild all sensitive partitions. Do not forget to flash your original ROM before you go to the service center
You have written that it occured after a few days after ROM/modem flashing, so in my opinion it is not related to ROM/modem you flashed
_alexndr said:
Unfortunately, anyway - it looks like EFS and/or related ID partitions damage. It usually happen for users with root and/or custom recovery, e.g. immediately after flashing a ZIP file. Fortunately, users with root can easy backup EFS + related ID partitions and easy restore it in such emergency case.
1. If you rooted your phone in the past and created the backup of all sensitive ID partitions - just restore it using same tool as you used for backup
2. If you never rooted your phone and still have KNOX 0x0 - the best way is warranty repair in an authorized service center (with a high probability - on the spot). Authorized services have tools to rebuild all sensitive partitions. Do not forget to flash your original ROM before you go to the service center
You have written that it occured after a few days after ROM/modem flashing, so in my opinion it is not related to ROM/modem you flashed
Click to expand...
Click to collapse
Yes I have rooted in the past and I have a custom recovery to flash your repacked version of stock ROMs.
However I don't have an EFS backup or any other backup. Does the EFS reset to default if I use Odin or Samsung's official way of flashing a firmware using kies?
My Knox is also (0x1)4 which means warranty will probably mess me over.
SleemLDJ said:
Yeah. Checked my IMEI. It matches the one on the box of the phone. My serial number is also matching with the one on the box.
On the status section of the phone, it says
Voice: Out of service / Data: Out of service
Click to expand...
Click to collapse
If IMEI is correct and you have no Network then there are some possibilities
1.try different sim card
2.rarely physical damage to sim tray
3.network setting - checkout this
setting - more - mobile network - Network mode - set to Auto
Sometime if you set to wcdam/lte and you are on area where service not available this can happen
4.network locked - confirm by talking to your operator.
5.rarely modem issue. - try flashing stock ROM and factory reset
If your IMEI is correct nothing wrong with efs don't try to manipulate in any way but to be safer make your EFS backup earliest if you haven't yet.
Sent from my SM-N910G using xda premium
dr.ketan said:
If IMEI is correct and you have no Network then there are some possibilities
1.try different sim card
2.rarely physical damage to sim tray
3.network setting - checkout this
setting - more - mobile network - Network mode - set to Auto
Sometime if you set to wcdam/lte and you are on area where service not available this can happen
4.network locked - confirm by talking to your operator.
5.rarely modem issue. - try flashing stock ROM and factory reset
If your IMEI is correct nothing wrong with efs don't try to manipulate in any way but to be safer make your EFS backup earliest if you haven't yet.
Sent from my SM-N910G using xda premium
Click to expand...
Click to collapse
I have tried all those options apart from contacting my operator. I don't see a reason why it should ne network locked.
I checked my IMEI using SWAPPAs ESN and it's clean.
SleemLDJ said:
Yes I have rooted in the past and I have a custom recovery to flash your repacked version of stock ROMs.
However I don't have an EFS backup or any other backup. Does the EFS reset to default if I use Odin or Samsung's official way of flashing a firmware using kies?
My Knox is also (0x1)4 which means warranty will probably mess me over.
Click to expand...
Click to collapse
I thought that you have tried with flashing firmware using Odin (you wrote that you have tried KK - I thought that it was pure stock)
Try as @dr.ketan said, but in my opinion you should start with p.5 and then perform wipe data
If it will help - DO NOT FORGET TO MAKE EFS/ID BACKUP devil never sleeps
If it will not help - I heard that paid EFS/ID repair isn't expensive
_alexndr said:
I thought that you have tried with flashing firmware with Odin (you wrote that you have tried KK (I thought that it war pure stock) [emoji14]
Try as @dr.ketan said, but in my opinion you should start with p.5 + wipe data
If it will help - DO NOT FORGET TO MAKE EFS/ID BACKUP [emoji14]
Click to expand...
Click to collapse
Sorry I meant I have flashed back stock KitKat with Odin but I haven't tried kies. My bad. I resorted to stock kitkat unrooted
last night but still the same thing.
One more thing. One possibility is your modem may not updated. I have seen some cases where rom is not having latest modem can cause this but again never seen that with intact IMEI.
Best way is go with latest stock ROM with odin and factory reset using stock recovery (you will lose Int SD data )
Sent from my SM-N910G using xda premium
SleemLDJ said:
Sorry I meant I have flashed back stock KitKat with Odin but I haven't tried kies. My bad. I resorted to stock kitkat unrooted
last night but still the same thing.
Click to expand...
Click to collapse
So try to flash the newest Lollipop, maybe it is not possible to revert back from BOD2 (with the newest modem) to KK? I'm not sure, just suppose.. Remember - power off your phone for a few seconds and then go directly to DM, otherwise it is possible that modem will not be flashed correctly (as @dr.ketan mentioned already)
Try this, due to fast mirrors:
>> N910FXXU1BOD2_N910FOXA1BOC3_alexndr.7z << (ultra packed using 7-Zip)
It is pure stock BOD2 with OXA multi CSC package. Read THIS THREAD for more info
_alexndr said:
it is possible that modem will not be flashed correctly (as @dr.ketan mentioned already)
Click to expand...
Click to collapse
Just side note.
One condition I am sure fail to flash BL Modem though Odin give message 'Passed' successfully.
If user select to put device in download mode using 4/5way reboot menu/Select reboot to download mode from recovery and flash BL Modem
Only it applies correctly if entered download mode with three button combo.
dr.ketan said:
One more thing. One possibility is your modem may not updated. I have seen some cases where rom is not having latest modem can cause this but again never seen that with intact IMEI.
Best way is go with latest stock ROM with odin and factory reset using stock recovery (you will lose Int SD data )
Sent from my SM-N910G using xda premium
Click to expand...
Click to collapse
I reverted with the stock KitKat that came with the phone yesterday with Odin. It wiped the internal storage and it also reverted the modem from bod2. It didn't work with the old modem either.
I'll try latest lollipop ROM for btu to see if anything changes
_alexndr said:
So try to flash the newest Lollipop, maybe it is not possible to revert back from BOD2 (with the newest modem) to KK? I'm not sure, just suppose.. Remember - power off your phone for a few seconds and then go directly to DM, otherwise it is possible that modem will not be flashed correctly (as @dr.ketan mentioned already)
Try this, due to fast mirrors:
>> N910FXXU1BOD2_N910FOXA1BOC3_alexndr.7z << (ultra packed using 7-Zip)
It is pure stock BOD2 with OXA multi CSC package. Read THIS THREAD for more info
Click to expand...
Click to collapse
This is exactly what I've always been using and I'm on BOD2 right now. I'm a huge follower of your work.
I'm not sure if anyone can identify the problem from this.
Whenever I turn the phone on, this jargon is always trying to send itself to my most recent contact on SMS.
I have this same problem with my n910F device, it started yesterday and I couldn't call or text anyone, but data over mobile still worked. Now I can't even use data anymore. I have tried flashing different roms and stock rom with odin, but it hasn't helped. IMEI is still intact and everything... Carrier couldn't help either.
I have same issue. imei is correct as well as serial number. but even tho its connecting with data in 4G is not able to register to network and connect on gsm. very weird
---------- Post added at 10:02 AM ---------- Previous post was at 09:58 AM ----------
were u guys on UK EE network or T-mobile or Orange. wondering if csc name EVR or BTU can cause this
starcraw36 said:
I have same issue. imei is correct as well as serial number. but even tho its connecting with data in 4G is not able to register to network and connect on gsm. very weird
---------- Post added at 10:02 AM ---------- Previous post was at 09:58 AM ----------
were u guys on UK EE network or T-mobile or Orange. wondering if csc name EVR or BTU can cause this
Click to expand...
Click to collapse
I am on EE with no problems. Was using EVR, but now on BTU.
Sent from my SM-N910F
do u know where i can find a fast download for EVR baseband?
starcraw36 said:
do u know where i can find a fast download for EVR baseband?
Click to expand...
Click to collapse
Afraid not. The only place is Sam mobile.

Galaxy S4 Play Edition (GT-I9505G) and Lineage OS 15.1

Hello folks,
I have Galaxy S4, Play Edition, GT-I9505G, currently running SlimROM 7.1.2 build 1.17 (dated 20180115) and baseband version I9505GUEUDNL3.
Last stock I had on this phone was Android 5.0. If there was any OTA after that, I didn't install it.
(Sam Mobile does not list this device, hence no way of knowing firmwares, but https://forum.xda-developers.com/wiki/Samsung_Galaxy_S_4/GT-I9505G lists mine as the last firmware.)
I have been trying to install Lineage 15/Oreo ROMs and with every ROM I am getting Error 7, which is supposedly Recovery error but every time I have used the recovery recommended by the ROM administrator. So its definitely not a recovery issue in my case.
I was wondering, those with same device, managed to install Oreo ROM, what is your baseband version? Most likely, this is the culprit, but to be sure, I would like to know at least one person with same device and different baseband version that managed to install Oreo ROM.
This page (https://forum.xda-developers.com/galaxy-s4/i9505g-develop/odin-images-i9505g-t3271624) list a lot of stock ROMs. Mine is half way through. Hence, I would like to see someone with newer baseband running Oreo ROM.
Many thanks in advance.
Did you check the updater script to ensure the phone's model # is included?
audit13 said:
Did you check the updater script to ensure the phone's model # is included?
Click to expand...
Click to collapse
Yes. All the ROMs I tried were for I-9505 of which I-9505G is a variant. I also removed that part of the script, just in case, but the same error occurred.
fuzzychicken said:
Yes. All the ROMs I tried were for I-9505 of which I-9505G is a variant. I also removed that part of the script, just in case, but the same error occurred.
Click to expand...
Click to collapse
Maybe you need to add the gt-i9505g to the list rather than removing it.
audit13 said:
Maybe you need to add the gt-i9505g to the list rather than removing it.
Click to expand...
Click to collapse
It was already there, so the ROMs were compatible but I removed just in case, thought if it is not working with the model number in it, maybe I can try without it, as recommended on some other blog posts on the web.
I guess the only other thing would be to try different versions of TWRP.
audit13 said:
I guess the only other thing would be to try different versions of TWRP.
Click to expand...
Click to collapse
I am sorry, thats what I said in the OP. I have tried every possible version of TWRP that was recommended for those ROMs and the error keep showing up. That indicates that its not recovery that is causing the problem.
Only thing left I can think of would be to flash the latest stock ROM, factory wipe, flash twrp, then wipe, and then flash the custom ROM.
audit13 said:
Only thing left I can think of would be to flash the latest stock ROM, factory wipe, flash twrp, then wipe, and then flash the custom ROM.
Click to expand...
Click to collapse
That is what I am thinking but I am not too sure which is the latest stock ROM.
https://forum.xda-developers.com/galaxy-s4/i9505g-develop/odin-images-i9505g-t3271624 On this page, there are loads of stocks. Mine is half way through. Its I9505GUEUDNL3_FULL. Assuming that the list goes down as newer stocks, esp looking at the last 3 alpha-numerics, should I be flashing I9505GUEUDPF1_FULL?
If I flash, I9505GUEUDPF1_FULL will it write new bootloader and baseband? If yes, do I have to go through whole unlock bootloader thing? or just flash twrp via Odin and go ahead with newer ROM? This is the most sticky part as I don't remember how I did it in the past. I just don't touch something I am not very clear understanding on, but this time I would like to update to Oreo, primarily for security purpose and the cash is tight so if I brick this, I wouldn't be very happy to buy another device. Hence trying to dot all i's and cross all t's.
Thanks for all help in advance.
Flashing a stock ROM with Odin will update the bootloader and modem.
The bootloader is not locked and has never been locked on the gt-i9505.
audit13 said:
Flashing a stock ROM with Odin will update the bootloader and modem.
The bootloader is not locked and has never been locked on the gt-i9505.
Click to expand...
Click to collapse
Thank you.
Let me put it in steps, pls correct me if I am wrong.
1. Flash I9505GUEUDPF1_FULL using Odin. Once rebooted, confirm if newer baseband is present. Check if the calls and data works.
2. Flash TWRP recovery using Odin (it will revert to stock recovery, right?) If not, alls good as it is.
3. Install ROM of choice.
There is no data on the phone, I reflashed SlimROM after all attempts of Oreo failed.
Anything tricky stuff in between?
Thanks in advance.
To prevent the stock recovery from overwriting twrp, uncheck everything in Odin except for reset time, flash twrp, when you see the word "reset" in the status window, remove the usb cable from phone, remove the battery, replace the battery, boot into twrp.
audit13 said:
To prevent the stock recovery from overwriting twrp, uncheck everything in Odin except for reset time, flash twrp, when you see the word "reset" in the status window, remove the usb cable from phone, remove the battery, replace the battery, boot into twrp.
Click to expand...
Click to collapse
I am very sorry to be a PITA, mate, but I really need help here.
As per the suggestions, I tried flashing various images. In every image I flashed, the calling and wifi worked but cell data didn't work in any of those versions. Still I tried flashing Oreo with them but the error persisted. So probably, its something beyond I can do it with my little knowledge.
So finally, to give up I tried going to back to where I was before all this, to baseband version, I9505GUEUDNL3. I flashed NL3 image linked in the post https://forum.xda-developers.com/galaxy-s4/i9505g-develop/odin-images-i9505g-t3271624 through Odin. While the OS shown in about phone is 5.0, the baseband version is stuck at OJ1, where the data does not work.
Any idea how I can go back to NL3 where data worked flawlessly?
Many thanks in advance.
Edit: I flashed NL3 modem from https://forum.xda-developers.com/showthread.php?t=2452034 but still the issue persists. I have nandroid backups from the very first time when I flashed another ROM. If I use that to restore, will it restore all the issues?
The bootloader and modem should be flashed in tandem to maintain compatibility with each other. Data may not be working due to a mismatch.
Flash the latest stock ROM from sammobile.com, updato.com, or samsung-firmware.org.
audit13 said:
The bootloader and modem should be flashed in tandem to maintain compatibility with each other. Data may not be working due to a mismatch.
Flash the latest stock ROM from sammobile.com, updato.com, or samsung-firmware.org.
Click to expand...
Click to collapse
Thank you.
Can you pls take a look at this thread? https://forum.xda-developers.com/galaxy-s4/i9505g-develop/odin-images-i9505g-t3271624 Supposedly, these are factory images. I tried these images and my best guess is, they have right bootloader and modem. None of the sites you suggested carry stock images for GT-I9505G (Play Edition). They have GT-I9505 though.
What I tried so far.
- Flashed images linked above. Didn't work
(at one point, I even got OTA, when I was on OE1 baseband, it updated to OJ1. So in theory, in this OTA, it should fix this mismatch bootloader and modem, right?) When things didn't change after this update. I tried to flash NL3 image.
- Flashed NL3 image which I had. The baseband remained at OJ1. This was odd to me. So flashed NL3 modem. The issue persisted.
- I had taken nandroid backup before I started flashing custom ROMs. I tried to restore that back up through a custom recovery, TWRP. No help.
Screenshot of that backup, if it tells you anything
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- I have EFS Backups, but I don't quite remember how I took that backup.
Screenshot attached. Any idea if this can be used to restore everything in one shot. I don't know if EFS contains bootloader as well.
You mentioned I should flash stock ROM. Assuming that ROM images linked on the XDA thread above are untouched, shouldn't that fix the issue? If not, is there any possibility one can find bootloader images (if such thing exists) because modem images are available in another thread. One can pick and choose a combination to flash. I am just speculating. I have no idea if such a thing can be done.
Thank you so much. Really appreciate you sticking around to share the ideas.
P.S. - Is there any option where you can delete both bootloader and modem just before flashing the stock ROM via Odin or TWRP?
There is no need to deal with the EFS at this moment as long as the phone is showing the correct IMEI and MAC address.
Yes, those look like factory images and you should try the latest ROM which is PF1. It's possible that the phone was running a newer bootloader than the one found in the NL3 ROM. Some boot loaders cannot be downgraded.
You cannot delete the bootloader from the phone. Without a bootloader, the phone would function. It's similar to the BIOS of a PC.
It is not TWRP that's the problem - it's the size of your system / user partitions on the 9505g.
@side said he would have a fix in version 4 OptLos for this.
His solution is not something I will be implementing in Resurrection Remix however.
audit13 said:
There is no need to deal with the EFS at this moment as long as the phone is showing the correct IMEI and MAC address.
Yes, those look like factory images and you should try the latest ROM which is PF1. It's possible that the phone was running a newer bootloader than the one found in the NL3 ROM. Some boot loaders cannot be downgraded.
You cannot delete the bootloader from the phone. Without a bootloader, the phone would function. It's similar to the BIOS of a PC.
Click to expand...
Click to collapse
So I flashed PF1 stock ROM, both bootloaders and modems are PF1. Made sure over the full day yesterday, there is no update and the problem persists. Can't flash Oreo and no cell phone data. Now, my interest in Oreo has pretty much died and only hoping to find a tweak to fix cell phone data. Fixed APN, made a factory reset just to be sure that its not the issue, tried SIM card in the different phone and other SIM in my phone that its not the SIM or the network thats the cause. So far I have not managed to find out what made the phone lose cell phone data.
Buff99 said:
It is not TWRP that's the problem - it's the size of your system / user partitions on the 9505g.
@side said he would have a fix in version 4 OptLos for this.
His solution is not something I will be implementing in Resurrection Remix however.
Click to expand...
Click to collapse
Dang man, your comment came a little late after I managed to fcuk up my phone very well trying to install Oreo. It will be great if you folks can make this comment in OP of the respective ROMs so that next I9505G user won't mess it up royally the way I did. If I remember correctly, I read both the threads start to the end and I didn't find any comment on this issue of I9505G.
Thanks both of you for chiming in and trying to help. If there is any idea to fix the loss of cell phone data, that will be of great help.

Categories

Resources