problem: on 3 dif. roms (slim, AOKP) sometimes there is no sound on calls for both sides. more interesting my hung up command take no charge and the call actually hung up after a minute (then it appears 'no network') or on reboot/turn off. this happens randomly on 4.2.2 roms. (and ivv tried 4.2.1 slim also)
on stock 4.2.2 the problem does not exist.
tried to switch back and forth from stock to modified roms but nothing.
what do you guys think?
Make sure you're on the latest bootloader and radio.
Is this ok?
elada22 said:
Is this ok?
Click to expand...
Click to collapse
No, that's an old radio and you probably have the old bootloader as well then.
Here: http://forum.xda-developers.com/showthread.php?t=2147194
i flashed both radio and BL but now it shows:
baseband version: unknown
imei: (blank)
no network at all of course.
should i try and flash the zip file again?
elada22 said:
i flashed both radio and BL but now it shows:
baseband version: unknown
imei: (blank)
no network at all of course.
should i try and flash the zip file again?
Click to expand...
Click to collapse
What??
Try rebooting. Maybe flash again. Never heard of that before..
same result. anything else maybe? back to stock rom?
elada22 said:
same result. anything else maybe? back to stock rom?
Click to expand...
Click to collapse
What rom is that you're using? What is that "du_mako"..?
dirty unicorns
http://forum.xda-developers.com/showthread.php?t=2239428
Hm. I have no clue what could be the issue. Hopefully someone else can chime in.
im going to try and flash the zips separately
wish me luck
edit:
it didnt work
trying flashing back to stock rom
still no imei or baseband
elada22 said:
im going to try and flash the zips separately
wish me luck
edit:
it didnt work
trying flashing back to stock rom
still no imei or baseband
Click to expand...
Click to collapse
Are you using lte? Try switching to 2g if so.
However, htf did your imei get erased..??
flash the factory image should fix it up
the radio you flashed sound lik it was corrupted
not lte.
3g - 2g toggle both available on my carrier. not relevant.
my basebans is gone and so is the imei after flashing radio&bootloader.
take a look at this thread, i think its relevant.
http://forum.xda-developers.com/showthread.php?t=2060780
immunityx said:
flash the factory image should fix it up
the radio you flashed sound lik it was corrupted
Click to expand...
Click to collapse
im flashing this deodexed stock rom but still the same
http://forum.xda-developers.com/showthread.php?t=2010887
Nope that wont do it you need to flsah the factory image not just stock rom, the image contains stock bootloadr and radio and rom,kernel all in one
download here
https://dl.google.com/dl/android/aosp/occam-jdq39-factory-345dc199.tgz
Extract it using winrar or winzip you shoulld see a bat file called flash-all
Boot your phone to bootloader by power button +vol down ill see s the green android
plug your phone up via usb cable to computer and run that flash-all bat file
Are you 100% sure both the radio and bootloader were for the n4 and not another device
immunityx said:
Nope that wont do it you need to flsah the factory image not just stock rom, the image contains stock bootloadr and radio and rom,kernel all in one
download here
https://dl.google.com/dl/android/aosp/occam-jdq39-factory-345dc199.tgz
Extract it using winrar or winzip you shoulld see a bat file called flash-all
Boot your phone to bootloader by power button +vol down ill see s the green android
plug your phone up via usb cable to computer and run that flash-all bat file
Click to expand...
Click to collapse
ivv intalled the drivers like last time from here
http://forum.xda-developers.com/showthread.php?t=1992345
but look at the bat file trying to run....
in bootloader mode it shows the baseband version as the updated one - 48.
more details:
CARRIER INFO: none
SECURE BOOT: enabald
LOCK STATE: unlocked
username8611 said:
Are you 100% sure both the radio and bootloader were for the n4 and not another device
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2147194
elada22 said:
ivv intalled the drivers like last time from here
http://forum.xda-developers.com/showthread.php?t=1992345
but look at the bat file trying to run....
in bootloader mode it shows the baseband version as the updated one - 48.
more details:
CARRIER INFO: none
SECURE BOOT: enabald
LOCK STATE: unlocked
Click to expand...
Click to collapse
Grab the fastboot and adb android files and extract them in the same folder as the flash-all
ACtually i attached it here
Related
\\\\\\\\\\\\warning///////////
It seems that phones batch 1010 and newer dont like this method of going back to stock. If you're caught in a boot loop try flashing the official froyo for Captivate. One source can be found here
\\\\\\\\\\\\warning///////////
Disclaimer: Anything you do with the content found in this thread and the content that this thread links to, is your own choice and you are fully responsible for what happens to your phone.
This method is for ATT Captivate ONLY!
We all know that there is a very often used method of going back to stock found here. The problem is that the ODIN OneClickDownloader contains both boot loaders and param.lfs.
These files, if not flashed correctly or if the connection between phone and PC drops while flashing them, can brick your phone for good. The reason why would this happen is because of unreliable USB drivers.
The purpose of this thread is to give flash addicts/custom ROMs users a more secure way to go back to stock - JF6 - without risking bricking their devices.
Do not use this if you want to send your phone back to ATT or Samsung for warranty!
Use this if you want to go back to stock before flashing a custom ROM.
Use this without worries if you changed your boot screen image or if you flashed the secondary boot loader which allows you to enter download/recovery with key combos.
This package contains NO BOOTLOADERS and NO PARAM.LFS!
Download the package from here
Download Samsung Kies and install it. It will install the latest Samsung drivers.
How to:
Remove sdcard and SIM card from the phone
Extract JF6_secure.zip somewhere.
Boot in Download Mode (see below)
Run Odin3 v1.3.exe
Click on the button PDA
Choose JF6_secure.tar.md5
Click start.
Wait and do not unplug cable until it is finished
How to boot in download mode:
There are 3 methods:
Method 1: (ADB) - from recovery or normally booted with usb debugging on)
Open a cmd prompt/console/shell
adb shell
adb reboot download
Method 2: (KEY COMBO)
Remove the battery, sim card, sdcard if you have one
Insert the battery
Hold both Volume buttons
Plug in the USB cable and continue holding both Volume buttons
Method 3: (JIG)
Link
If moderators believe this does not belong in development, I have nothing against to moving it to General. However, I think the community would appreciate if it would remain here.
Works fine
I used this to flash the latest Continuum 3.5 and everything worked fine. Thanks!
you may want to include the info "FOR ATT i897" phones.
as, well... check my sig!~ i got the rogers i896 covered NO BOOTLOADERS! @@ YAY
Yep, updated, thanks!
Thanks for this and I appreciate all your work.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Success !!
Just used this to go back to stock prior to flashing another ROM. Worked with no problems and only took about 5 minutes. Will use this from now on to avoid the possible brick.
Again, really appreciate you providing this for us.
Still not sure why one would use this over the DG Odin? Maybe someone can clarify?
Here is my scenario. I'm currently on Cognition 3.04 which I flashed from stock. It was my first ROM so I didn't have to go back or do anything with Odin. Now, if I want to flash a new ROM, I plan on using Odin, jut not sure which one???
sircaper said:
Still not sure why one would use this over the DG Odin? Maybe someone can clarify?
Here is my scenario. I'm currently on Cognition 3.04 which I flashed from stock. It was my first ROM so I didn't have to go back or do anything with Odin. Now, if I want to flash a new ROM, I plan on using Odin, jut not sure which one???
Click to expand...
Click to collapse
Here you go again, is in the OP
We all know that there is a very often used method of going back to stock found here. The problem is that the ODIN OneClickDownloader contains both boot loaders and param.lfs.
These files, if not flashed correctly or if the connection between phone and PC drops while flashing them, can brick your phone for good. The reason why would this happen is because of unreliable USB drivers.
Click to expand...
Click to collapse
on top of the read phail, i would add that you dont need to flash stock between roms, you only need to do it after a failed flash or a "no wipe" rom that depends on original files, **which they dont do anymore**. All the good full roms do a wipe before flashing. so there is no point going to stock! hope that clearifies!
icezar1 said:
Here you go again, is in the OP
Click to expand...
Click to collapse
I did read it, just thought there was something I was missing.
I thought there was more to it than people having bad usb ports. You're saying if one does have a bad usb port and flashing gets interrupted, their phone would be bricked with the DG Odin, but with this Odin it would somehow be ok?
sircaper said:
I did read it, just thought there was something I was missing.
I thought there was more to it than people having bad usb ports. You're saying if one does have a bad usb port and flashing gets interrupted, their phone would be bricked with the DG Odin, but with this Odin it would somehow be ok?
Click to expand...
Click to collapse
If you own a computer you definitelly heard about BIOS and you heard that if the BIOS gets screwed (CMOS chip burned or bad BIOS update) you can pretty much throw the motherboard.
Well, imagine that your phone has 3 BIOSs
primary bootloader - boot.bin
secondary bootloader - sbl.bin
hidden partition for system images - param.lfs
and that they are dependent on each other and if one of them gets screwed you wont be able to get to recovery and download mode.
The one click downloader contains all these 3. My package does not.
Get the point?
icezar1 said:
If you own a computer you definitelly heard about BIOS and you heard that if the BIOS gets screwed (CMOS chip burned or bad BIOS update) you can pretty much throw the motherboard.
Well, imagine that your phone has 3 BIOSs
primary bootloader - boot.bin
secondary bootloader - sbl.bin
hidden partition for system images - param.lfs
and that they are dependent on each other and if one of them gets screwed you wont be able to get to recovery and download mode.
The one click downloader contains all these 3. My package does not.
Get the point?
Click to expand...
Click to collapse
Makes sense. Is there ever an instance where those files need to be wiped, though?
sircaper said:
Makes sense. Is there ever an instance where those files need to be wiped, though?
Click to expand...
Click to collapse
Not really. Only if you flashed a boot loader from a different SGS model.
icezar1 said:
Not really. Only if you flashed a boot loader from a different SGS model.
Click to expand...
Click to collapse
Thanks. Appreciate you clearing things up for me.
Trusselo said:
you may want to include the info "FOR ATT i897" phones.
as, well... check my sig!~ i got the rogers i896 covered
Click to expand...
Click to collapse
Does that mean your stock rom doesn't include the boot loaders and param.lfs either? I've been dying to try that one when I switch roms. I hate seeing the ATT logo pop up everytime i turn it on.
Oh yea, I forgot to use this a while ago. Next time I'll use this, I promise. Lol. Btw, is it okay to change the text on the .ini file? I somewhat changed the title to my liking.
WickedNite said:
Oh yea, I forgot to use this a while ago. Next time I'll use this, I promise. Lol. Btw, is it okay to change the text on the .ini file? I somewhat changed the title to my liking.
Click to expand...
Click to collapse
Yes, is OK
Has anyone flashed the three button fix? I really want to. just wanna verify its ok.
likiud said:
Does that mean your stock rom doesn't include the boot loaders and param.lfs either? I've been dying to try that one when I switch roms. I hate seeing the ATT logo pop up everytime i turn it on.
Click to expand...
Click to collapse
take a look here
double RL said:
Has anyone flashed the three button fix? I really want to. just wanna verify its ok.
Click to expand...
Click to collapse
You dont have the 3 button fix?
EDIT: yes, is OK, I tested it. Make sure you run a md5 checksum after putting it on your sdcard
Hi guys, I'm on an i9505 with stock ROM and everything. I had it rooted before and everything was perfect, but then I updated to 4.3, so I had to re-root. When I re-rooted, everything was still there - I just had to re-install Xposed. However, my Wi-Fi is not working anymore. Every time I click on the Wi-Fi to toggle it on, it flashes green, then turns itself off again.
What is the problem here? My build number is JSS15J.I9505XXUEMKF and my baseband versionis I9505XXUEMJ7. I rooted using CF Auto-root for I9505.
Rorschilds said:
Hi guys, I'm on an i9505 with stock ROM and everything. I had it rooted before and everything was perfect, but then I updated to 4.3, so I had to re-root. When I re-rooted, everything was still there - I just had to re-install Xposed. However, my Wi-Fi is not working anymore. Every time I click on the Wi-Fi to toggle it on, it flashes green, then turns itself off again.
What is the problem here? My build number is JSS15J.I9505XXUEMKF and my baseband versionis I9505XXUEMJ7. I rooted using CF Auto-root for I9505.
Click to expand...
Click to collapse
Download and extract then Flash this via odin by seleting phone http://d-h.st/lVI
Repulsa said:
Download and extract then Flash this via odin by seleting phone http://d-h.st/lVI
Click to expand...
Click to collapse
Thanks, I just tried it, but it didn't seem to do anything. Still turning itself off the second I turn it on.
Is it perhaps because my baseband version is not the same as my build number? I don't know much about the details and intricacies of how this stuff works, I only know the basics, but that's an idea that came up.
Or maybe I need the Wifi fix for UEMKF (my build number) rather than UEMJ7 (My baseband version)?
I'm not sure. But just some ideas.
Rorschilds said:
Thanks, I just tried it, but it didn't seem to do anything. Still turning itself off the second I turn it on.
Is it perhaps because my baseband version is not the same as my build number? I don't know much about the details and intricacies of how this stuff works, I only know the basics, but that's an idea that came up.
Or maybe I need the Wifi fix for UEMKF (my build number) rather than UEMJ7 (My baseband version)?
I'm not sure. But just some ideas.
Click to expand...
Click to collapse
Download and Extract ,then Power Off your device completely and wait a few sec and Press and hold Power+Volume down in order to reach download mode and flash it via odin, and go to settings and check your baseband if the flash are okey.
**If you are having the new bootloader XXUD flash http://www.mediafire.com/download/zriv6i5c01lqns6/GSM_Modem_XXUEMFK_and_LTE_Modem_XXUMFK.rar file with odin by selecting phone.
Repulsa said:
Download and Extract ,then Power Off your device completely and wait a few sec and Press and hold Power+Volume down in order to reach download mode and flash it via odin, and go to settings and check your baseband if the flash are okey.
**If you are having the new bootloader XXUD flash http://www.mediafire.com/download/zriv6i5c01lqns6/GSM_Modem_XXUEMFK_and_LTE_Modem_XXUMFK.rar file with odin by selecting phone.
Click to expand...
Click to collapse
Yes I know how to flash. The second link worked, thank you very much sir
Rorschilds said:
Yes I know how to flash. The second link worked, thank you very much sir
Click to expand...
Click to collapse
Glad that helps , Have a nice day sir.
the wifi problem doesn't accour cuz you root your phone it happened to my me and i was not rooted and nor flashed anything. you wake up and boom wifi won't turn on. and i use my mobile data cuz i can not turn on my wifi anymore. some say it's a hardware issue. some say it is a firmware issue. i don't know. i can't solve the problem. even i pay a technician to repair the phone buy they couldnt eighter. so i feel dumb when someone says this worked for me or that solved the issue. i did everything and i have not much money to buy a new one
Hello,
I am unable to connect to any 2.4 Ghz network (tried at home, friend's, hotel's, etc.). While at home, my network will go on and off being displayed in my phone. I can select it and enter my password. Then it will say "Connecting..." but nothing will happen. After that it goes in and out of being in range even though I can be adjacent to my router.
5 Ghz works flawlessly
Bootloader is unlocked
Tried multiple JB and KK Cyanogen based ROMs and stock
I am also unable to connect to any device via bluetooth (if that helps at all, probably going to post about this separately later)
I have searched google and multiple forums. The posts nearest to my issue mention a fix for people who formatted their persist folder (I have not, plus I tried copying it anyways) and a fix using a static IP address. No luck.
If anyone has an idea or can provide a fix, I would really appreciate. I am going insane
Thank you.
brando9 said:
Hello,
I am unable to connect to any 2.4 Ghz network (tried at home, friend's, hotel's, etc.). While at home, my network will go on and off being displayed in my phone. I can select it and enter my password. Then it will say "Connecting..." but nothing will happen. After that it goes in and out of being in range even though I can be adjacent to my router.
5 Ghz works flawlessly
Bootloader is unlocked
Tried multiple JB and KK Cyanogen based ROMs and stock
I am also unable to connect to any device via bluetooth (if that helps at all, probably going to post about this separately later)
I have searched google and multiple forums. The posts nearest to my issue mention a fix for people who formatted their persist folder (I have not, plus I tried copying it anyways) and a fix using a static IP address. No luck.
If anyone has an idea or can provide a fix, I would really appreciate. I am going insane
Thank you.
Click to expand...
Click to collapse
From your Wi-Fi problems, sounds like you're on KK bootloader... are you? (you didn't mention in your post)
Since you're unlocked, try going back to JB bootloader and flash a JBBL based ROM and see if your problem is resolved
rahimali said:
From your Wi-Fi problems, sounds like you're on KK bootloader... are you? (you didn't mention in your post)
Since you're unlocked, try going back to JB bootloader and flash a JBBL based ROM and see if your problem is resolved
Click to expand...
Click to collapse
Sorry, yes KK bootloader. How do I go back to a JB bootloader?
Not sure if using RSD to downgrade changes the bootloader but I did try "Android 4.1.2 Blur_Version.98.30.1.XT907.Verizon.en.US" via http://forum.xda-developers.com/showthread.php?t=2786016
brando9 said:
Sorry, yes KK bootloader. How do I go back to a JB bootloader?
Not sure using RSD to downgrade changes the bootloader but I did try "Android 4.1.2 Blur_Version.98.30.1.XT907.Verizon.en.US" via http://forum.xda-developers.com/showthread.php?t=2786016
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2786016
rahimali said:
http://forum.xda-developers.com/showthread.php?t=2786016
Click to expand...
Click to collapse
Yes, I tried that. Is it worth trying the older firmware too?
brando9 said:
Yes, I tried that. Is it worth trying the older firmware too?
Click to expand...
Click to collapse
thats entirely up to you, i'm happy with what i'm using (in my signature), feel free to try out one of the JB ROMs or one of the JB BL based KitKat ROMs, might like one of them...
No luck with any stock firmware using RSD
brando9 said:
No luck with any stock firmware using RSD
Click to expand...
Click to collapse
I am here man. I will help you for sure
1: download the jellybean FIRMWARE
2: extract is somewhere
3: open XML file with notepad++
4: delete all line which contain GETVAR and OEM
==MUST STEP===
4: also delete the line which contain
GPT.BIN
5: now save it and exit
6: now goto the folder where you extracted the firmware, Now Delete TZ file from folder
--
7: boom it with RSD LITE.
now it will work!! Give a try man!!
livecouk said:
I am here man. I will help you for sure
1: download the jellybean FIRMWARE
2: extract is somewhere
3: open XML file with notepad++
4: delete all line which contain GETVAR and OEM
==MUST STEP===
4: also delete the line which contain
GPT.BIN
5: now save it and exit
6: now goto the folder where you extracted the firmware, Now Delete TZ file from folder
--
7: boom it with RSD LITE.
now it will work!! Give a try man!!
Click to expand...
Click to collapse
Worked! I tried 3 versions but none of them fixed my wifi issue unfortunately. Thanks tho.
brando9 said:
Worked! I tried 3 versions but none of them fixed my wifi issue unfortunately. Thanks tho.
Click to expand...
Click to collapse
No problem have a nice day
Does anyone know any other way to get marshmallow on my rooted device? I have TWRP on there and am trying to side-load, but everytime i click on adb sideload on my phone, the phone disappears from my computer. I have tried many things to no avail. I apologize if this has already been asked elsewhere. TIA!
yandawg said:
Does anyone know any other way to get marshmallow on my rooted device? I have TWRP on there and am trying to side-load, but everytime i click on adb sideload on my phone, the phone disappears from my computer. I have tried many things to no avail. I apologize if this has already been asked elsewhere. TIA!
Click to expand...
Click to collapse
You could use the return to stock tool in the development section and just take the OTA. Then you can just reflash TWRP.
Thanks for the quick response, but I have done that a couple of times and i have received the OTA, but the install always fails. I am using the RTS program that has the file that starts out with CLARK_RETUS_5.1.1_LPH23.116-18.......... Is there another that i should be using? BTW, I am on the European 1572 variant if that matters. Thanks again for the reply!
I've got the same problem, I'm on the 1572 instead of the 1575 and not sure on what to do with the return to stock tool
I just went through this yesterday. I tried the twrp but got no WiFi even with flashing the modem. I tried return to stick and failed the first time. I tried return to stick the second time but flashed the modem file by itself again and then the MM upgrade worked. That is the only thing I did differently.
watmartin said:
I've got the same problem, I'm on the 1572 instead of the 1575 and not sure on what to do with the return to stock tool
Click to expand...
Click to collapse
dont use the return to stock tool for the xt1575 on the xt1572, you need to get the xt1572 firmware from here: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833 get it, and unzip it, then get this: https://drive.google.com/file/d/0BzsA17IjC5k2Y203VklsVDhseDQ/view?usp=sharing and put it in the same directory, make sure you have fastboot installed system wide, otherwise put the files in the same directory as the images, boot the phone into fastboot mode (power + vol down), plug into computer, and run the flash-all batch script, once done, the phone should reboot into stock 5.1.1
nitros12 said:
dont use the return to stock tool for the xt1575 on the xt1572, you need to get the xt1572 firmware from here: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833 get it, and unzip it, then get this: https://drive.google.com/file/d/0BzsA17IjC5k2Y203VklsVDhseDQ/view?usp=sharing and put it in the same directory, make sure you have fastboot installed system wide, otherwise put the files in the same directory as the images, boot the phone into fastboot mode (power + vol down), plug into computer, and run the flash-all batch script, once done, the phone should reboot into stock 5.1.1
Click to expand...
Click to collapse
Could I message you on Skype or something about this? I'm kinda lost... My Skype is ________ if you can. Sorry man...
My apologies. I didn't catch you were on 1572. Was on my way out of the house and answered quickly.
Oaklands said:
My apologies. I didn't catch you were on 1572. Was on my way out of the house and answered quickly.
Click to expand...
Click to collapse
no problem oaklands! Thanks for trying to help out! I believe I have flashed to 5.1.1 alright, but for some reason I can't update. It don't seem like my modem wants to work or something. I flashed a new one and everything. Any thoughts? TIA
I am interesting also,
I have rooted EU version 1572, and cant wait for Marshmallow. Is there a solution to update from Lollipop to Marshamallow right now?
yandawg said:
no problem oaklands! Thanks for trying to help out! I believe I have flashed to 5.1.1 alright, but for some reason I can't update. It don't seem like my modem wants to work or something. I flashed a new one and everything. Any thoughts? TIA
Click to expand...
Click to collapse
I can only tell you the only thing I did differently after returning to stock was to flash the non-hlos.bin file in fastboot a second time. I believe that is the correct file name. I am not at home to verify. That is all it took for me. I would try again. I have seen others that have repeated steps that did not work the first time to have it work the next time.
Keep in mind I am on US 1575 version but I don't see why it wouldn't work for you as long as you have the proper files. I would initially get to 15 or 20% and it would just fail with no error code.
I'm on an N9005. I did not know about Knox when I first got it (came from an S3) and flashed TWRP and Cyanogen (unofficial v13 MM). Funnily enough I tripped Knox 0x1. Since then the phone comes up as custom, etc. and no matter what I do it stays that way, even on completely stock ROM. I have tried Triangle Away but it made no difference (stock rom, rooted with CF Auto Root).
I'm on Arch Linux so I flash everything via Heimdall. Everything else flashes fine, but the bootloader and modem flashes will not stick. I have tried on a Windows PC with Odin as well and didn't work with Odin either. I have tried the trick of flashing and then booting straight back into DL mode and flashing again, but that did not work either.
I have tried flashing the BL/BB on multiple different ROMS, didn't work. I even experimented with flashing the stock rom but with the updated BL/BB files - didn't work and bootlooped so I had to reflash stock. I've tried a different kernel, no difference.
It keeps the original original BL/BB no matter what I do. This phone was originally bought in another country and thus far I have only been able to flash it with the stock rom of that country. If I use my own country's (New Zealand) stock rom, it boot loops.
Could it be refusing this particular BL and BB build? Should I try an older build and see if that works? Or is this a problem related to something else? How can I fix this?
Thanks in advance!
You need to power off the phone completely before flashing them. If doesn't work remove battery for a few seconds then retry. Do not flash with reboot into download mode from rom's power menu.
Sent from my SM-N920C
Thorned_Rose said:
I'm on an N9005. I did not know about Knox when I first got it (came from an S3) and flashed TWRP and Cyanogen (unofficial v13 MM). Funnily enough I tripped Knox 0x1. Since then the phone comes up as custom, etc. and no matter what I do it stays that way, even on completely stock ROM. I have tried Triangle Away but it made no difference (stock rom, rooted with CF Auto Root).
I'm on Arch Linux so I flash everything via Heimdall. Everything else flashes fine, but the bootloader and modem flashes will not stick. I have tried on a Windows PC with Odin as well and didn't work with Odin either. I have tried the trick of flashing and then booting straight back into DL mode and flashing again, but that did not work either.
I have tried flashing the BL/BB on multiple different ROMS, didn't work. I even experimented with flashing the stock rom but with the updated BL/BB files - didn't work and bootlooped so I had to reflash stock. I've tried a different kernel, no difference.
It keeps the original original BL/BB no matter what I do. This phone was originally bought in another country and thus far I have only been able to flash it with the stock rom of that country. If I use my own country's (New Zealand) stock rom, it boot loops.
Could it be refusing this particular BL and BB build? Should I try an older build and see if that works? Or is this a problem related to something else? How can I fix this?
Thanks in advance!
Click to expand...
Click to collapse
Flash bootloader twice without reboot.
Don't let the phone get into OS.
Remove the battery and flash the boot loader twice. It will stick.
Telling from experience
Rosli59564 said:
You need to power off the phone completely before flashing them. If doesn't work remove battery for a few seconds then retry. Do not flash with reboot into download mode from rom's power menu.
Sent from my SM-N920C
Click to expand...
Click to collapse
vishnu vijay said:
Flash bootloader twice without reboot.
Don't let the phone get into OS.
Remove the battery and flash the boot loader twice. It will stick.
Telling from experience
Click to expand...
Click to collapse
Thank you!!!! Pulling the battery was the missing piece!
I was powering off the phone fully before booting into D/L and then flashing (twice over). Removing the battery beforehand has finally made it stick. Thank you muchly! This was driving me nut so really appreciate you taking the time in aswering
Thorned_Rose said:
Thank you!!!! Pulling the battery was the missing piece!
I was powering off the phone fully before booting into D/L and then flashing (twice over). Removing the battery beforehand has finally made it stick. Thank you muchly! This was driving me nut so really appreciate you taking the time in aswering
Click to expand...
Click to collapse
I am glad it worked. Cheers
vishnu vijay said:
Flash bootloader twice without reboot.
Don't let the phone get into OS.
Remove the battery and flash the boot loader twice. It will stick.
Telling from experience
Click to expand...
Click to collapse
Do you know if this still takes effect on new(er) phones? I have an S5 Mini. I'm flashing with Debian heimdall (just param.bin, i'm trying to change the bootlogo). I took out the battery before booting to D/L, and flashed twice (removing battery between flashes). Heimdall reports success, and if I pull the partition with root+dd, I can see my changes. It just doesn't change the logo.:crying: This is driving me crazy,
Thanks in advance,
Hackintosh5
P.S. Please tell me if you think this should be a separate thread!
hackintosh5 said:
Do you know if this still takes effect on new(er) phones? I have an S5 Mini. I'm flashing with Debian heimdall (just param.bin, i'm trying to change the bootlogo). I took out the battery before booting to D/L, and flashed twice (removing battery between flashes). Heimdall reports success, and if I pull the partition with root+dd, I can see my changes. It just doesn't change the logo.:crying: This is driving me crazy,
Thanks in advance,
Hackintosh5
P.S. Please tell me if you think this should be a separate thread!
Click to expand...
Click to collapse
Instead of booting into the OS have you tried booting into recovery.
Volume home and volume plus combo
Usually there are some patches so the OS doesn't overwrite the Recovery.
vishnu vijay said:
Instead of booting into the OS have you tried booting into recovery.
Volume home and volume plus combo
Usually there are some patches so the OS doesn't overwrite the Recovery.
Click to expand...
Click to collapse
No, you've misunderstood. I'm trying to flash a bootlogo to the PARAM (.bin) partition, not recovery. Should I try to make an odin package?
I would ask in your phones forum.
Most of Notes cannot modify param.bin
vishnu vijay said:
Flash bootloader twice without reboot.
Don't let the phone get into OS.
Remove the battery and flash the boot loader twice. It will stick.
Telling from experience
Click to expand...
Click to collapse
i have the same problem just for bootloader. cp is ok.
i've turned off my phone n9005 and pull out battery and turn on n download mode and flashed BL file in BL section twice without reboot and my bootloader didn't change. any suggestion?
titan-computer said:
i have the same problem just for bootloader. cp is ok.
i've turned off my phone n9005 and pull out battery and turn on n download mode and flashed BL file in BL section twice without reboot and my bootloader didn't change. any suggestion?
Click to expand...
Click to collapse
Use Odin 3.04,
Maybe the BL you tryna stick is older than the one you already have?
Flash, reboot & pull off the battery when it begins to load bootanimation.
Do it again for 3 times at least.
I could downgrade to KitKat bootloader this way.
Mohamedkam000 said:
Use Odin 3.04,
Maybe the BL you tryna stick is older than the one you already have?
Flash, reboot & pull off the battery when it begins to load bootanimation.
Do it again for 3 times at least.
I could downgrade to KitKat bootloader this way.
Click to expand...
Click to collapse
doesn't work.
yeas. it's older than my current bootloader.
i did all things with odin 3.04 but didn't change the bootloader.
in odin 3.04 it has an option "phone bootloader update", do i need to check this? default is unchecked.
titan-computer said:
doesn't work.
yeas. it's older than my current bootloader.
i did all things with odin 3.04 but didn't change the bootloader.
in odin 3.04 it has an option "phone bootloader update", do i need to check this? default is unchecked.
Click to expand...
Click to collapse
Of course you need to check it.
Other than that, is the bootloader packed with NON-HLOS.bin or just the *.mbn files?
I mean, is it ~7 MB in size or ~1.7 MB?
You may need to flash a modem file as well to enforce the BL?
If all that didn't work, there's one proved way that will work, use a box (software).
Mohamedkam000 said:
Of course you need to check it.
Other than that, is the bootloader packed with NON-HLOS.bin or just the *.mbn files?
I mean, is it ~7 MB in size or ~1.7 MB?
You may need to flash a modem file as well to enforce the BL?
If all that didn't work, there's one proved way that will work, use a box (software).
Click to expand...
Click to collapse
no it's just mbn files almost 1.7 MB.
i've checked boot loader update and didn't work again. modem got update at the first time but BL doesn't.
what is this? box software?
titan-computer said:
no it's just mbn files almost 1.7 MB.
i've checked boot loader update and didn't work again. modem got update at the first time but BL doesn't.
what is this? box software?
Click to expand...
Click to collapse
Windows software, named Z3X Box, download it and update your bootloader with, it will definitely success.