Related
Hi there,
i have a rooted S4 i9505 with cwm installed.
yesterday i did an update from stock rom 4.3 to 4.4.2 (I9505XXUEMKE) via KIES.
the problem now....I cant turn on the wifi anymore. whenever i try to use the on/off switch for the wifi it instandly switches back to off.
is anyone else experiencing the same problem? has someone already a solution for that, before i will do a factory reset.
SDA1979 said:
Hi there,
i have a rooted S4 i9505 with cwm installed.
yesterday i did an update from stock rom 4.3 to 4.4.2 (I9505XXUEMKE) via KIES.
the problem now....I cant turn on the wifi anymore. whenever i try to use the on/off switch for the wifi it instandly switches back to off.
is anyone else experiencing the same problem? has someone already a solution for that, before i will do a factory reset.
Click to expand...
Click to collapse
hmm - shouldn't really be a problem if you flashed stock, but broken wifi is a symptom reported when flashing old modem on new bootloader, if you have new stock sammy 4.4 then you will surely have new bootloader (check though by putting your phone into download mode and then check for KNOX references - if you got them you got new bootloader, if no then you are on the old one)
Click on the link in my sig for modem - that will take you to a thread that has all the newest modems - have a look through the most recent last 3-4 pages and you will find packages for modems for new bootloader, flash one of these and see what happens - BTW you need to flash in odin with 'reboot' unchecked, then when its finished power off your phone manually then put back into download mode and flash again, then repeat the procedure but this time tick 'reboot' and that should be done. BTW - the tar file goes into 'phone' not csc. You may need to unzip the modem package to get the tar file.
Let us know how you got on
Jimsilver73 said:
hmm - shouldn't really be a problem if you flashed stock, but broken wifi is a symptom reported when flashing old modem on new bootloader, if you have new stock sammy 4.4 then you will surely have new bootloader (check though by putting your phone into download mode and then check for KNOX references - if you got them you got new bootloader, if no then you are on the old one)
Click on the link in my sig for modem - that will take you to a thread that has all the newest modems - have a look through the most recent last 3-4 pages and you will find packages for modems for new bootloader, flash one of these and see what happens - BTW you need to flash in odin with 'reboot' unchecked, then when its finished power off your phone manually then put back into download mode and flash again, then repeat the procedure but this time tick 'reboot' and that should be done. BTW - the tar file goes into 'phone' not csc. You may need to unzip the modem package to get the tar file.
Let us know how you got on
Click to expand...
Click to collapse
ok just to be sure and not bricking my phone..
i went into download mode and it says:
odin mode
product name gt-i9505
current binary custom
system status official
knox kernel lock 0x0
knox warranty void 0x1csb-config-lsb 0x30
write protection enabled
eMMC burst mode enabled
now if i understood right, i have to download
Wifi fix/NON-HLOS - I9505_XXUFNB8_WiFi_FIX
and flash it with odin with the instruction above....
is that correct?
i also found XXUFNB8.... should i rather use this one?
SDA1979 said:
ok just to be sure and not bricking my phone..
i went into download mode and it says:
odin mode
product name gt-i9505
current binary custom
system status official
knox kernel lock 0x0
knox warranty void 0x1csb-config-lsb 0x30
write protection enabled
eMMC burst mode enabled
now if i understood right, i have to download
Wifi fix/NON-HLOS - I9505_XXUFNB8_WiFi_FIX
and flash it with odin with the instruction above....
is that correct?
i also found XXUFNB8.... should i rather use this one?
Click to expand...
Click to collapse
Its correct
SDA1979 said:
ok just to be sure and not bricking my phone..
i went into download mode and it says:
odin mode
product name gt-i9505
current binary custom
system status official
knox kernel lock 0x0
knox warranty void 0x1csb-config-lsb 0x30
write protection enabled
eMMC burst mode enabled
now if i understood right, i have to download
Wifi fix/NON-HLOS - I9505_XXUFNB8_WiFi_FIX
and flash it with odin with the instruction above....
is that correct?
i also found XXUFNB8.... should i rather use this one?
Click to expand...
Click to collapse
you are on the new bootloader so you can flash the complete package - it has everything in it all in one package! - you won't brick your phone even if you flash the wrong modem, that is unless you did some thing real dumb like flash i9500 modem and even then I think its recoverable not that I suggest you try!!
depends where you are in the world - I used NB8 and it worked well for me in the UK - I'm on NB9 now and that seems nice also.
so to be clear flash this:
Combined package
For NewBootloader
GSM_Modem_XXUFNB8_and_LTE_Modem_XXUFNB8
https://mega.co.nz/#!3dR30JiT!cP5WrUCfz9L4h8doY7KTTV6fq4pFL85EkJBG6T-Gqhc
Jimsilver73 said:
you are on the new bootloader so you can flash the complete package - it has everything in it all in one package! - you won't brick your phone even if you flash the wrong modem, that is unless you did some thing real dumb like flash i9500 modem and even then I think its recoverable not that I suggest you try!!
depends where you are in the world - I used NB8 and it worked well for me in the UK - I'm on NB9 now and that seems nice also.
so to be clear flash this:
Combined package
For NewBootloader
GSM_Modem_XXUFNB8_and_LTE_Modem_XXUFNB8
https://mega.co.nz/#!3dR30JiT!cP5WrUCfz9L4h8doY7KTTV6fq4pFL85EkJBG6T-Gqhc
Click to expand...
Click to collapse
hey guys, thank you!!!
the Wi-Fi is working again.
Nonetheless i still have one problem remaining, which i thought it would have been fixed as well.
but, when GPS is turned on, it tries to find the GPS position and the icon on the status bar continues appearing and disappearing permanently (every half of a second).
Beside the fact that it is really annoying having this icon flashing all the time it also causes the display to freeze.
Especially when scrolling from top to the bottom to open the notification area.
It sometimes also lets the system crush completely.
any idea what this could be?
thanks for your effort so far.
SDA1979 said:
hey guys, thank you!!!
the Wi-Fi is working again.
Nonetheless i still have one problem remaining, which i thought it would have been fixed as well.
but, when GPS is turned on, it tries to find the GPS position and the icon on the status bar continues appearing and disappearing permanently (every half of a second).
Beside the fact that it is really annoying having this icon flashing all the time it also causes the display to freeze.
Especially when scrolling from top to the bottom to open the notification area.
It sometimes also lets the system crush completely.
any idea what this could be?
thanks for your effort so far.
Click to expand...
Click to collapse
hmmm......... thats not right!
Suggest you find a stock sammy ROM and flash anew in odin - then root using cf root, then flash recovery - (TWRP is very good :good then go into recovery and wipe cache, dalvik, system and data - reboot and see what happens on nice new shiny sammy stock - if all is good pick the ROM/kernel you want (if you want) and go back to odin to reflash modem.
The only other thing I can think is that you have an app that is messing with gps?? Do the above though and you should be golden :good:
EDIT: don't wipe system unless you planning flashing a different ROM through recovery!
Jimsilver73 said:
hmmm......... thats not right!
Suggest you find a stock sammy ROM and flash anew in odin - then root using cf root, then flash recovery - (TWRP is very good :good then go into recovery and wipe cache, dalvik, system and data - reboot and see what happens on nice new shiny sammy stock - if all is good pick the ROM/kernel you want (if you want) and go back to odin to reflash modem.
The only other thing I can think is that you have an app that is messing with gps?? Do the above though and you should be golden :good:
Click to expand...
Click to collapse
Hi, right way to flash the stock Samsung package, but after flashing a custom recovery, do not wipe system. There's no ROM after that so phone will not boot. And the newest modem is integrated in the stock package, so no need to flash it again.
And another advice: NEVER use Kies to update your phone. It has bricked 3 of mines.:cyclops:
speedwayfan75 said:
Hi, right way to flash the stock Samsung package, but after flashing a custom recovery, do not wipe system. There's no ROM after that so phone will not boot. And the newest modem is integrated in the stock package, so no need to flash it again.
And another advice: NEVER use Kies to update your phone. It has bricked 3 of mines.:cyclops:
Click to expand...
Click to collapse
Oops, well spotted! Yes, don't wipe system unless you have another ROM to flash through recovery. 3 phones bricked from kies huh? I never used it SVD don't think I ever will lol. Good old Sammy stock stuff, tbh that's why I steer well clear of anything stock Sammy unless absolutely necessary and last resort - I look at the farce they have made by forcing us to accept Knox pox!
Jimsilver73 said:
Oops, well spotted! Yes, don't wipe system unless you have another ROM to flash through recovery. 3 phones bricked from kies huh? I never used it SVD don't think I ever will lol. Good old Sammy stock stuff, tbh that's why I steer well clear of anything stock Sammy unless absolutely necessary and last resort - I look at the farce they have made by forcing us to accept Knox pox!
Click to expand...
Click to collapse
my thought was to go into recovery mode and wipe everything and start from beginning in order to exclude that it could depends on some wrong settings or any software already installed....
I updated to 4.4.2 using Mobile Odin and my wifi was borked too.
I did notice after the update that there was a mismatch between my Baseband version (still the old 4.3 XXUEMKE) and the Build number XXUFNB8, and I recall seeing some message during the flashing process that security had blocked the kernel update and Triangle Away might help solve it.
I therefore ran Triangle Away to reset my flash counter, and then used Mobile Odin to have a second go at flashing just the Kernel, Recovery and Modem parts.
This was successful and I now have matching Baseband and Build, both XXUFNB8.
And my wifi now works again...
ok.. after making a factory reset wifi and gps are working fine again.
guess there was some missconfigured third party app...
but now, with a fresh system i do not understand why i am not able to assign a PIN for my lockscreen...
everything is greyed out except PIN and Password.
but even though setting up a PIN, the screen lock is always set to use Swipe......
damn, i shouldnt have updated to 4.4.2.... until now.. only problems with this new build....
SDA1979 said:
ok.. after making a factory reset wifi and gps are working fine again.
guess there was some missconfigured third party app...
but now, with a fresh system i do not understand why i am not able to assign a PIN for my lockscreen...
everything is greyed out except PIN and Password.
but even though setting up a PIN, the screen lock is always set to use Swipe......
damn, i shouldnt have updated to 4.4.2.... until now.. only problems with this new build....
Click to expand...
Click to collapse
Try slimkat 3.2 from here http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/909-jfltexx remember to download gapps and flash after you have flashed ROM. You won't be disappointed
Jimsilver73 said:
Try slimkat 3.2 from here http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/909-jfltexx remember to download gapps and flash after you have flashed ROM. You won't be disappointed
Click to expand...
Click to collapse
hey thanks for your suggestion. but i want to keep using the stock rom. sufficent for my needs....
anyway.. finally i was able to get everything working after flashing the rom with odin again.
Jimsilver73 said:
hmm - shouldn't really be a problem if you flashed stock, but broken wifi is a symptom reported when flashing old modem on new bootloader, if you have new stock sammy 4.4 then you will surely have new bootloader (check though by putting your phone into download mode and then check for KNOX references - if you got them you got new bootloader, if no then you are on the old one)
Click on the link in my sig for modem - that will take you to a thread that has all the newest modems - have a look through the most recent last 3-4 pages and you will find packages for modems for new bootloader, flash one of these and see what happens - BTW you need to flash in odin with 'reboot' unchecked, then when its finished power off your phone manually then put back into download mode and flash again, then repeat the procedure but this time tick 'reboot' and that should be done. BTW - the tar file goes into 'phone' not csc. You may need to unzip the modem package to get the tar file.
Let us know how you got on
Click to expand...
Click to collapse
I feel compelled to express my gratitude for the post. Two days ago i updated from 4.3 to 4.4.2 on my rooted gt-i9505 via KIES and just like that no more wifi. This solution works like charm!!!
:good::good::good::good::good::good:
Good day everyone.
Got a strange problem trying to upgrade my Note 4 (910C) to eRobot 11 (11.1) based on the latest COJ5 base.
After flashing device just does not start up - the black screen with "Galaxy Note 4" hangs and nothing goin on. Bootloops sometimes
I tried eRobot and another custom ROM based on COJ5 - the same result.
COI4 based ROM works fine.
Being flashed via ODIN the COJ5 based ROM works fine.
I have latest TWRP recovery, COJ5 bootloader and already have tried flashing service 4-file ROM.
If anyone got any information that can help - please welcome!
Thanks!
kurkovda said:
Good day everyone.
Got a strange problem trying to upgrade my Note 4 (910C) to eRobot 11 (11.1) based on the latest COJ5 base.
After flashing device just does not start up - the black screen with "Galaxy Note 4" hangs and nothing goin on. Bootloops sometimes
I tried eRobot and another custom ROM based on COJ5 - the same result.
COI4 based ROM works fine.
Being flashed via ODIN the COJ5 based ROM works fine.
I have latest TWRP recovery, COJ5 bootloader and already have tried flashing service 4-file ROM.
If anyone got any information that can help - please welcome!
Thanks!
Click to expand...
Click to collapse
Try flashing a kernel after flashing COJ5 ROM. Clear cache/davlik cache also
http://forum.xda-developers.com/note-4/development/n910c-spacex-kernel-v0-1-auto-root-t3192875
http://forum.xda-developers.com/note-4/development/kernel-suemax-kernel-lite-v1-0-t3221865
dicksteele said:
Try flashing a kernel after flashing COJ5 ROM. Clear cache/davlik cache also
Click to expand...
Click to collapse
Done.
I even tried flashing bootloader via ODIN after flashing ROM.
Got bootloop on Sixperience v5 and erobot 11.1.
kurkovda said:
Done.
I even tried flashing bootloader via ODIN after flashing ROM.
Got bootloop on Sixperience v5 and erobot 11.1.
Click to expand...
Click to collapse
ODIN Flash this
http://forum.xda-developers.com/note-4/development/rom-note-4-mod-t3244665
It should boot up fine. Blow past all the setup.
Boot into Download Mode, ODIN flash TWRP.
https://dl.twrp.me/treltexx/twrp-2.8.7.0-treltexx.img.tar
Boot into recovery then try flashing Six or e-Robot
I have the same phone and I've done this more time that I can count (TODAY !!)
dicksteele said:
ODIN Flash this
http://forum.xda-developers.com/note-4/development/rom-note-4-mod-t3244665
It should boot up fine. Blow past all the setup.
Boot into Download Mode, ODIN flash TWRP.
https://dl.twrp.me/treltexx/twrp-2.8.7.0-treltexx.img.tar
Boot into recovery then try flashing Six or e-Robot
I have the same phone and I've done this more time that I can count (TODAY !!)
Click to expand...
Click to collapse
Done already.
As I've rote - being flashed via ODIN the COJ5 based rom works fine
After flashing this ROM via ODIN I've tried flashing recovery, then geting root by installing prerooted krernel, then flashing custom ROM.
You've missed the point with flashing prerooted kernel, does this matter?
kurkovda said:
Done already.
As I've rote - being flashed via ODIN the COJ5 based rom works fine
After flashing this ROM via ODIN I've tried flashing recovery, then geting root by installing prerooted krernel, then flashing custom ROM.
You've missed the point with flashing prerooted kernel, does this matter?
Click to expand...
Click to collapse
Depends which ROM, and if it has a kernel in install. Looking through most of them, it is included.
How long are you waiting for it to boot? At the Samsung Logo depending on kernel it could take up to 5-10 minutes.
If it's stuck at first Galaxy Note 4 screen, usually that's kernel. My experience anyways. And I've flashed every 5.1.1 ROM here. Multiple times for many of them.
dicksteele said:
Depends which ROM, and if it has a kernel in install. Looking through most of them, it is included.
How long are you waiting for it to boot? At the Samsung Logo depending on kernel it could take up to 5-10 minutes.
If it's stuck at first Galaxy Note 4 screen, usually that's kernel. My experience anyways. And I've flashed every 5.1.1 ROM here. Multiple times for many of them.
Click to expand...
Click to collapse
It stucks on Galaxy Note 4 screen and bootloops sometimes.
ROMs eRobot and sixperience I've flashed has kernels inside, eRobot even has four via Arome, and I've tried each of them
Well, will try your method, thanks a lot for help, will write down about the results!
kurkovda said:
It stucks on Galaxy Note 4 screen and bootloops sometimes.
ROMs eRobot and sixperience I've flashed has kernels inside, eRobot even has four via Arome, and I've tried each of them
Well, will try your method, thanks a lot for help, will write down about the results!
Click to expand...
Click to collapse
Switch off the phone and remove the battery.Wait 2 minutes then re-insert the battery.Then flash the boot loader via odin.
kakkooran said:
Switch off the phone and remove the battery.Wait 2 minutes then re-insert the battery.Then flash the boot loader via odin.
Click to expand...
Click to collapse
Will be able to try this out later this evening, thanks!
kurkovda said:
Will be able to try this out later this evening, thanks!
Click to expand...
Click to collapse
I'm not sure what that will accomplish. The bootloader gets flashed during the stock ROM install I posted.
That's the sboot.bin file that gets flashed in ODIN not the boot.img that is the kernel with TWRP. Big difference.
Try to enter download mode by shutting off mobile (remove battery if it wont work) and enter downloade mode with 3 finger combo.
I had observed sometimes that flashing with odin by entering downloadmode from software will cause problems....
Maybe this will help...
Greetings
HalloSpencer said:
Try to enter download mode by shutting off mobile (remove battery if it wont work) and enter downloade mode with 3 finger combo.
I had observed sometimes that flashing with odin by entering downloadmode from software will cause problems....
Maybe this will help...
Greetings
Click to expand...
Click to collapse
I'm not sure you are speaking about MY problem
Flashing by ODIN causes no problem, they start after flashing ane custom COJ5 ROM via TWRP.
And I use "hardware" method every time I need to get to ODIN mode
Just wanted to make clear that you flashed COJ5 bootloader using "hardware method".... I actualy cant remeber were I read that flashing otherwise can cause problems (without odin failure)....
And yes I was speaking about your problem
dicksteele said:
ODIN Flash this
http://forum.xda-developers.com/note-4/development/rom-note-4-mod-t3244665
It should boot up fine. Blow past all the setup.
Boot into Download Mode, ODIN flash TWRP.
https://dl.twrp.me/treltexx/twrp-2.8.7.0-treltexx.img.tar
Boot into recovery then try flashing Six or e-Robot
I have the same phone and I've done this more time that I can count (TODAY !!)
Click to expand...
Click to collapse
As for me this is wiered but that worked obviously 0_o
The phone is booting up now.
But could you please explain what was wrong with this ROMs, or with my phone, or with me?) And - will I need to repeat all this shaman dances to flash any other ROM?
Anyway, I owe you, thanks a lot!
Does anyone knows what makes N910C COJ5 refuses the downgrade? In theory, the downloading mode that ODIN uses should be controlled by the bootloader, correct? The code in the downloading mode is the one responsible for not allowing downgrades. Why can't we just flash a different bootloader that allows us to downgrade or did samsung created some mechanism to protect the current some parts from COJ5 bootloader from being replaced (I noticed I can flash different bootloaders, but the issue with downgrading persists). If we could completely replace the booloader, this would provide answers for this thread and at least 5 other threads diving in the same issue.
amidsal said:
Does anyone knows what makes N910C COJ5 refuses the downgrade? In theory, the downloading mode that ODIN uses should be controlled by the bootloader, correct? The code in the downloading mode is the one responsible for not allowing downgrades. Why can't we just flash a different bootloader that allows us to downgrade or did samsung created some mechanism to protect the current some parts from COJ5 bootloader from being replaced (I noticed I can flash different bootloaders, but the issue with downgrading persists). If we could completely replace the booloader, this would provide answers for this thread and at least 5 other threads diving in the same issue.
Click to expand...
Click to collapse
They did
amidsal said:
Does anyone knows what makes N910C COJ5 refuses the downgrade? In theory, the downloading mode that ODIN uses should be controlled by the bootloader, correct? The code in the downloading mode is the one responsible for not allowing downgrades. Why can't we just flash a different bootloader that allows us to downgrade or did samsung created some mechanism to protect the current some parts from COJ5 bootloader from being replaced (I noticed I can flash different bootloaders, but the issue with downgrading persists). If we could completely replace the booloader, this would provide answers for this thread and at least 5 other threads diving in the same issue.
Click to expand...
Click to collapse
The bootloader was not the issue in this thread. It was flashing ROMs.
Samsung obviously realized we had way to much freedom our phones and has tightened down the sboot.bin (COJ5 bootloader file)
You will notice in your ODIN flashes when trying to downgrade, that's the file it barfs on.
Which surprises me, that why I bought the 910C to get away from the locked down crap from ATT.
---------- Post added at 01:27 PM ---------- Previous post was at 01:21 PM ----------
kurkovda said:
As for me this is wiered but that worked obviously 0_o
The phone is booting up now.
But could you please explain what was wrong with this ROMs, or with my phone, or with me?) And - will I need to repeat all this shaman dances to flash any other ROM?
Anyway, I owe you, thanks a lot!
Click to expand...
Click to collapse
Good deal. Booting up on a Custom ROM?
I usually flash back to stock every now and then. Never hurts.
I'm running SIMPLROM5c. Running pretty good. I've tried them all. I usually run them a couple of days and see how I like it.
All of the ROMs have their own personality. Just find one that fits yours. I'm finding a stock one like SIMPLROM will probably be my daily one, but I have backups of the others to change whenever my mood changes.
The N5 and S6 features are cool, but I bought a Note 4 because it's a Note 4. If I wanted a Note5 or S6 I would have gotten one.
Now the S7 MAY make me change my mind. we'll see.
kurkovda said:
They did
Click to expand...
Click to collapse
And even if we have the device rooted, we can't overwrite the bootloader because of it is not possible interfere with the environment external to hypervisor (like the bootloader, kernel, etc.) unless someone finds a loophole, right? In this situation, wouldn't it be possible to overwrite the booloader completely if we could access the internal sd card and mounting it in a regular linux environment (similarly to the way people used to extract the xbox 360 using a probe). Could it be possible?
dicksteele said:
Good deal. Booting up on a Custom ROM?
I usually flash back to stock every now and then. Never hurts.
I'm running SIMPLROM5c. Running pretty good. I've tried them all. I usually run them a couple of days and see how I like it.
All of the ROMs have their own personality. Just find one that fits yours. I'm finding a stock one like SIMPLROM will probably be my daily one, but I have backups of the others to change whenever my mood changes.
The N5 and S6 features are cool, but I bought a Note 4 because it's a Note 4. If I wanted a Note5 or S6 I would have gotten one.
Now the S7 MAY make me change my mind. we'll see.
Click to expand...
Click to collapse
Yep, the ROM has booted up and works
I'm a kind of newbe for Note4 and now just want to find out who is who But I've stucked being unable to flash the new base ROM, and unfortunately on my native forum there are just a very few rommakers, and no one could give me some info about this issue.
Now I'll test sixperience, and if it's not as good as I hope will try something else
kurkovda said:
Yep, the ROM has booted up and works
I'm a kind of newbe for Note4 and now just want to find out who is who But I've stucked being unable to flash the new base ROM, and unfortunately on my native forum there are just a very few rommakers, and no one could give me some info about this issue.
Now I'll test sixperience, and if it's not as good as I hope will try something else
Click to expand...
Click to collapse
All the ROMs work great, and there's great support. It all depends on what you looking for in a ROM.
I think there's a little too much expectation from people that think jamming (porting) features from other phones (N5 and S6) is supposed to work perfectly on a Note 4.
A lot of work goes into trying to make it work. But if they want the features that are on that phone to work perfectly, buy that phone.
---------- Post added at 02:00 PM ---------- Previous post was at 01:56 PM ----------
amidsal said:
And even if we have the device rooted, we can't overwrite the bootloader because of it is not possible interfere with the environment external to hypervisor (like the bootloader, kernel, etc.) unless someone finds a loophole, right? In this situation, wouldn't it be possible to overwrite the booloader completely if we could access the internal sd card and mounting it in a regular linux environment (similarly to the way people used to extract the xbox 360 using a probe). Could it be possible?
Click to expand...
Click to collapse
I have read someone suggesting doing a NAND ERASE ALL in ODIN during the firmware flash. That should wipe the hell out of everything.
I'm waiting to hear back if he's done that on the OJ5 bootloader.
I've had my phone from a month, I'm not willing to take that chance yet.
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.
My friend got an old phone from his dad, who had an old custom ROM installed on it, and asked me to return it to the original software.
I used ODIN 3.09 and installed the appropriate ROM which I downloaded from Sammobile.
The phone went into a bootloop, so I wiped the cache and when that didn't work, I wiped all data. After that the phone booted into the Welcome screen and my friend started to configure it. In the middle of the process, the phone rebooted, and now it loads into the Welcome screen, but reboots after a few seconds.
After that I've tried reflashing the software and doing multiple resets, to no avail. Any ideas?
Please let me know of any Ideas. I am very ashamed of damaging my friend's phone.
PS: I should say, I put a bootloader into ODIN the first time I flashed the software because some tutorial recommended it and I haven't seen that requierement in any other tutorial since. Might this be the cause? How could I test that?
What model what firmware what bootloader ??
JJEgan said:
What model what firmware what bootloader ??
Click to expand...
Click to collapse
The phone is a Note 3 N900 UB, the firmware I installed was N900UBSEBQB5, and to be honest, I can't quite tell what the bootloader is, the file I downloaded is just called "bootloader".
the file I downloaded is just called "bootloader
My guess is that's the fault as bootloaders are named same as firmwares
Example >>> BL_N9005ZSUGPJ2
Could be a bootloader for anything .because some tutorial recommended
Have you taken a chance to reflashing the official firmware with ordin , that would be helpful all the time.
After that you should make sure your phone work fine on the official rom .
Then update your Recovery to a third party Rec,like CWM or TWRP .
Next step,flashing an original rom.
larrycn said:
Have you taken a chance to reflashing the official firmware with ordin , that would be helpful all the time.
After that you should make sure your phone work fine on the official rom .
Then update your Recovery to a third party Rec,like CWM or TWRP .
Next step,flashing an original rom.
Click to expand...
Click to collapse
Thats wrong .
Hey there everyone,
I wanted to root my s8 (sm-950f) and when I flashed twrp my phone initially got stuck in Samsung logo. After managing to shut it down I tried to go to recovery mode to wipe everything and perform a factory reset but I can not do it. All that happens is I get to s8 screen and it reads in red on top left of the screen "Only official released binaries are allowed to be flashed" and it keeps resetting itself. I can access download mode but that's it, I can't do anything else. Currently downloading a stock firmware to try and flash it but with the free downloads it's taking its time. Any help appreciated, I really want to unbrick my phone
note: It shows FRP and OEM lock to be off in download mode, i dont even know if i'll even be able to flash a new fw. Do I just have a very expensive brick in my hands now?
nekropok said:
Hey there everyone,
I wanted to root my s8 (sm-950f) and when I flashed twrp my phone initially got stuck in Samsung logo. After managing to shut it down I tried to go to recovery mode to wipe everything and perform a factory reset but I can not do it. All that happens is I get to s8 screen and it reads in red on top left of the screen "Only official released binaries are allowed to be flashed" and it keeps resetting itself. I can access download mode but that's it, I can't do anything else. Currently downloading a stock firmware to try and flash it but with the free downloads it's taking its time. Any help appreciated, I really want to unbrick my phone
Click to expand...
Click to collapse
This must be a international S8... Did you activate oem unlock in developer settings before flashing twrp
([emoji3590]09-09-18[emoji3590])
I'm not sure if it's international, it's most likely a Turkish version.
And yeah to your question
nekropok said:
I'm not sure if it's international, it's most likely a Turkish version.
And yeah to your question
Click to expand...
Click to collapse
But you know for a fact that there's a twrp version for your device.... Not good to do these expensive phones like that without officially having all the facts
([emoji3590]09-09-18[emoji3590])
Well it's too late for that now, I need actual solutions. I also tried smart switch - it doesn't recognize the phone
nekropok said:
Well it's too late for that now, I need actual solutions. I also tried smart switch - it doesn't recognize the phone
Click to expand...
Click to collapse
On the xda thread for your device there aren't no stock roms uploaded to Android host for fast download so you can flash in Odin and start the process of twrp again or just leave it alone you have a S8 it's good money
([emoji3590]09-09-18[emoji3590])
WHEW. Flashing a stock firmware seems to have fixed the issue. Mods can lock the thread.
nekropok said:
WHEW. Flashing a stock firmware seems to have fixed the issue. Mods can lock the thread.
Click to expand...
Click to collapse
You going to give up on twrp
([emoji3590]09-09-18[emoji3590])
I do want to root, but I don't want to approach it without knowing all my facts, do you have any suggestions for guides for Android 9.0?
nekropok said:
I do want to root, but I don't want to approach it without knowing all my facts, do you have any suggestions for guides for Android 9.0?
Click to expand...
Click to collapse
Just look in your device forum everything Is there however your device is a international cause it ends in with the F so twrp does work for your device..... You just need to find the specific one for your model once you have twrp you can install a android 9 custom rom
([emoji3590]09-09-18[emoji3590])
I had same issue as you and was pointed towards this thread may be of some use to you?
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
Problem on my S8
PoochyX said:
This must be a international S8... Did you activate oem unlock in developer settings before flashing twrp
([emoji3590]09-09-18[emoji3590])
Click to expand...
Click to collapse
Sorry but I have a serious problem. I have activated oem and debug usb on developer option, but I can't install TWRP. I have tried with odin, prince cosmy odin, odin patched but FAIL everywhere, please help me, I just want twrp and i want to install a custom rom. thanks in advance everyone. If is a problem answer me here, you can send me a pvt message. I tried it from 3 days with the same FAILS :_(
I had this problem too a year ago but wasn't able to reflash the official firmware, but when I went to Samsung they fixed it for free even though Knox was already tripped
FabiusMod said:
Sorry but I have a serious problem. I have activated oem and debug usb on developer option, but I can't install TWRP. I have tried with odin, prince cosmy odin, odin patched but FAIL everywhere, please help me, I just want twrp and i want to install a custom rom. thanks in advance everyone. If is a problem answer me here, you can send me a pvt message. I tried it from 3 days with the same FAILS :_(
Click to expand...
Click to collapse
are you able to flash the stock firmware on it and get it to boot without TWRP installed?
I am with a stock rom now, The device works fine.