Hi,
After flashing the MJ6 ROM with the Universal root de la vega method (I have the old bootloader from MJ1) and flash the MJ4 modem, the camera and and wifi were not working, I tried to downgrade the modem to MJ2 with Odin to give a try.
However now I'm facing several boot loops (on first notification model screen) and when the Note succeed in corectly booting, I have an FC from system process, and some others applications.
I tried to check the phone parameters and saw that baseband was "unknown", but didn't succeed to see the screen where the IMEI is displayed because the phone is rebooting automaticaly when I try to access to this screen.
The phone is very instable : sometimes I'm not able to access to parameters with the tactil button.
In all cases the phone is auto rebooting after several minutes.
I tried several things withoot result :
- Wipe cache + factory reset
- Flash several modems
- Flash MI7 stock ROM with Odin
> no change
Actually I have :
- baseband unknown
- boot looping
- no wifi
- no sound
- no root
- acces to download mode and stock recovery is OK.
As someone have some cloues to help me?
Crystal7_Magic said:
Hi,
After flashing the MJ6 ROM with the Universal root de la vega method (I have the old bootloader from MJ1) and flash the MJ4 modem, the camera and and wifi were not working, I tried to downgrade the modem to MJ2 with Odin to give a try.
However now I'm facing several boot loops (on first notification model screen) and when the Note succeed in corectly booting, I have an FC from system process, and some others applications.
I tried to check the phone parameters and saw that baseband was "unknown", but didn't succeed to see the screen where the IMEI is displayed because the phone is rebooting automaticaly when I try to access to this screen.
The phone is very instable : sometimes I'm not able to access to parameters with the tactil button.
In all cases the phone is auto rebooting after several minutes.
I tried several things withoot result :
- Wipe cache + factory reset
- Flash several modems
- Flash MI7 stock ROM with Odin
> no change
Actually I have :
- baseband unknown
- boot looping
- no wifi
- no sound
- no root
- acces to download mode and stock recovery is OK.
As someone have some cloues to help me?
Click to expand...
Click to collapse
I'm pretty sure your Knox warranty void has been tripped... Flash the MJ6 stock firmware. You have the new bootloader now anyway, that's why you are in the bootloop.. I had the same problem and when I checked and found warranty void triggered I figured can't hurt.
Flashed stock MJ6 firmware. Baseband comes back, all thos little things not working get fixed. I then flashed CF-root as the warranty void was 0x1...
It seems if you flash the Modem.bin file you are stuck, you need to flash the MJ6 firmware to fix....
ultramag69 said:
I'm pretty sure your Knox warranty void has been tripped... Flash the MJ6 stock firmware. You have the new bootloader now anyway, that's why you are in the bootloop.. I had the same problem and when I checked and found warranty void triggered I figured can't hurt.
Flashed stock MJ6 firmware. Baseband comes back, all thos little things not working get fixed. I then flashed CF-root as the warranty void was 0x1...
It seems if you flash the Modem.bin file you are stuck, you need to flash the MJ6 firmware to fix....
Click to expand...
Click to collapse
I had the same pb ..... and flash MJ6 full and now it's OK .... so I rooted ... Knox 1 ....but everything OK I am happy
Ok, but normaly I always have the old bootloader because I do not have flash the MJ6 stock > It has been modified with universal root de la vega before flashing with Odin, and my flag is still on 0x0.
> So normaly the MJ6 I flashed should not contain the new bootloader.
It will be troublesome for me if flashing a stock MJ6 is needeed as I do not want to trigger the Knox flag.
I always have the solution to return my Note to my seller for refund, so I'm seeking for a way which do not trigger Knox
ultramag69 said:
I'm pretty sure your Knox warranty void has been tripped... Flash the MJ6 stock firmware. You have the new bootloader now anyway, that's why you are in the bootloop.. I had the same problem and when I checked and found warranty void triggered I figured can't hurt.
Flashed stock MJ6 firmware. Baseband comes back, all thos little things not working get fixed. I then flashed CF-root as the warranty void was 0x1...
It seems if you flash the Modem.bin file you are stuck, you need to flash the MJ6 firmware to fix....
Click to expand...
Click to collapse
LIPA said:
I had the same pb ..... and flash MJ6 full and now it's OK .... so I rooted ... Knox 1 ....but everything OK I am happy
Click to expand...
Click to collapse
Finaly I have decided to flash the MJ6 stock ROM and everything go ok.
I still have my knox 0x0 but will trigger to 0x1 if I try to root by now : hard decision.
Thanks for your help you two
Crystal7_Magic said:
Finaly I have decided to flash the MJ6 stock ROM and everything go ok.
I still have my knox 0x0 but will trigger to 0x1 if I try to root by now : hard decision.
Thanks for your help you two
Click to expand...
Click to collapse
Mate, I modified with root de la vega myself but it seems the new bootloader got through....
Where can I find the MJ6 firmware
ultramag69 said:
Mate, I modified with root de la vega myself but it seems the new bootloader got through....
Click to expand...
Click to collapse
It will be strange, because I succedeed to root the Note withoot triggering Knox
You have to be sure that you do not have take update from OTA or official stock ROM when you was on ROM before MJ3 (if you take stock MJ3 bootloader is altered)
yazzie said:
Where can I find the MJ6 firmware
Click to expand...
Click to collapse
You can find it on Sammobile website (create an account is needed to access to download section)
http://www.sammobile.com/firmwares/1/?model=SM-N9005&pcode=0#firmware
After flashing the MJ6 stock firmware to recover my baseband, I have juste noticed that wifi is not properly working.
> Wifi is blocked on activation
> Sometime the Note succeed to activate wifi and show me networks which are available, however when I'm trying to connect to one of them I got a freeze then wifi go back to activating statuts.
Any explanation?
SM-N900W8 Boot Loop
Has anyone else resolved this issue. Phone was rooted with "CF-Auto-Root-hltecan-hlteub-smn900w8" and used TWRP 2.6.3.0. Upon doing a restore with TWRP, the phone is now in this crazy loop. Phone boots but always fails prior to seeing home screen. Tried going to SamMobile and restoring original Rogers firmware with no resolution.
Any help is most appreciated.
ultramag69 said:
Mate, I modified with root de la vega myself but it seems the new bootloader got through....
Click to expand...
Click to collapse
thanks a million. i had the same problem, following my ordeal with samsung on region sim lock.
i tried the mj6, it seemed too work, for now.
will root it and see how that goes. thanks once again
Ahmads001 said:
thanks a million. i had the same problem, following my ordeal with samsung on region sim lock.
i tried the mj6, it seemed too work, for now.
will root it and see how that goes. thanks once again
Click to expand...
Click to collapse
If you flashed the stock MJ6 then you have the new anti-root bootloader. ANY attempt to root will end in Warranty void being triggered...
Unfortunately this is a problem that hasn't been fixed yet. Just a heads up to let you know you will probably trigger the warranty void.
Then again Designgears is back developing RDLV again so it might be updated soon... :fingers-crossed:
ultramag69 said:
If you flashed the stock MJ6 then you have the new anti-root bootloader. ANY attempt to root will end in Warranty void being triggered...
Unfortunately this is a problem that hasn't been fixed yet. Just a heads up to let you know you will probably trigger the warranty void.
Then again Designgears is back developing RDLV again so it might be updated soon... :fingers-crossed:
Click to expand...
Click to collapse
thanks again for usual insight.
unfortunately, the bootloop problem was back after a restart yesterday. took several loops (about 30 mins) before it started up. i had to reflash with the latest stock N9005XXUDMJ7_N9005OJVDMJ4_KSA. now im scared to restart the phone for any reason, since i cant tell if it will entre bootloop again - it gets worse with every reset.
Since the knox already tripped 0x1, i still desire to root it ASAP.
So,
1. how do i get rid of this bootloop menace, PERMANENTLY
2. how do i safely root the phone (SM-N9005)
will appreciate a lot of help.
Ahmads001 said:
thanks again for usual insight.
unfortunately, the bootloop problem was back after a restart yesterday. took several loops (about 30 mins) before it started up. i had to reflash with the latest stock N9005XXUDMJ7_N9005OJVDMJ4_KSA. now im scared to restart the phone for any reason, since i cant tell if it will entre bootloop again - it gets worse with every reset.
Since the knox already tripped 0x1, i still desire to root it ASAP.
So,
1. how do i get rid of this bootloop menace, PERMANENTLY
2. how do i safely root the phone (SM-N9005)
will appreciate a lot of help.
Click to expand...
Click to collapse
As Knox is tripped use cf-autoroot found in the original android developement section of the Note 3 forum. This will give you root...
I would also try a different region rom, I used MJ7 from the UK. It didn't cause any issues.
I had bootloops and found going to wifi, clicking on menu button, advanced.& unticking "Scanning always available" seemed to fix my bootloops but this was for my MJ1 firmware.
Otherwise can't really help anymore tonight. Gotta go to work tomorrow and its 2am here in Oz....
ultramag69 said:
As Knox is tripped use cf-autoroot found in the original android developement section of the Note 3 forum. This will give you root...
I would also try a different region rom, I used MJ7 from the UK. It didn't cause any issues.
I had bootloops and found going to wifi, clicking on menu button, advanced.& unticking "Scanning always available" seemed to fix my bootloops but this was for my MJ1 firmware.
Otherwise can't really help anymore tonight. Gotta go to work tomorrow and its 2am here in Oz....
Click to expand...
Click to collapse
thanks, and good morning.
will be back later (sorry some of us -docs- dont actually have the 'day/night' thing).
will try the wifi thing, and see what happens.
once again, thanks
Same problem here :
- Supposed to be MK2 rom (N9005XXUDMK2) and was rooted
- Recovery and download mode are OK
- Flashed several time with ODIN, including modem.bin from the same archive
- Obviously Knox is 0x01
But phone is still unuseable ....Boots up, pass the intial setting. Then error message about system not responding and reboot ...
Any help would be appreciated
Follow this it'll fix it http://forum.xda-developers.com/showthread.php?p=47014662
Sent from my SM-N9005 using XDA Premium 4 mobile app
You saved my day !!! Thanks
Crystal7_Magic said:
After flashing the MJ6 stock firmware to recover my baseband, I have juste noticed that wifi is not properly working.
> Wifi is blocked on activation
> Sometime the Note succeed to activate wifi and show me networks which are available, however when I'm trying to connect to one of them I got a freeze then wifi go back to activating statuts.
Any explanation?
Click to expand...
Click to collapse
I have the same problem
You solved your problem?
Thanks
sbdz said:
I have the same problem
You solved your problem?
Thanks
Click to expand...
Click to collapse
Hi,
Unfortunately for you no, I made a swap with a brandnew one with the seller.
Hi,
I am plannning to sell my i9500 model. I was using Arrow Rom V11 (4.3 without knox) before deciding this. In order to give valid warranty phone to the buyer, I ventured into installing stock 4.3 rom on the phone. As I a, from India, I have downloaded Indian 4.3 stock firware from Sammobile and flashed through ODIN. When the flashsin is done, the I am getting this "UID Inconsistent" message and along with many other"process stopped" messgaes. so I am not even abnle to get into settings menu to do a factory reset.
I read somewhere that "finxing permissions" through TWRP will solve the problem. But that will create another problem to me i.e lost warranty. (As i have already flashed 4.3 stock, Knox is set in).Hence I am not sure what to do make the phone function normally?
I want to keep installing custom recovery as last option. Btw, I am not able to get into recoverymode (even stock recovery) by pressing volume up+power+home buttons. When I try that phone flashes andorid symbol momentaorly and then reboots.
It will be great if you can offer some help! thanks in advance!!!
1. Ur warranty is void (Knox 0x1) -> No warranty in some country, in others yes.
2. Install TWRP and fix perms for solve ur problems
3. Reboot and take a look if all is correct
4. Reflash STOCK ROM for let ur phone like STOCK (but with knox actived -> no solution for that atm)
So after flashing a few things, something went wrong big time. Phone barely makes it to the lock screen and when it does, it says System is not responding and then automatically reboots. In that brief time I see the dreaded no signal icon.
Have tried restoring stock firmware via Odin and it still leads to the same lock screen issue every time (used this very same file to restore to stock before without any issues). To add salt to the wound, my SD card got corrupted (stupid SanDisk I should have learned from past experiences) which is where I kept my EFS backup. This is on a N900W8, with Knox tripped 0x1 so no chance of warranty.
Do I have quite the expensive paperweight on my hands here now? It seems so but hopefully there is a light at the end of the tunnel for me
VinceThePrince said:
So after flashing a few things, something went wrong big time. Phone barely makes it to the lock screen and when it does, it says System is not responding and then automatically reboots. In that brief time I see the dreaded no signal icon.
Have tried restoring stock firmware via Odin and it still leads to the same lock screen issue every time (used this very same file to restore to stock before without any issues). To add salt to the wound, my SD card got corrupted (stupid SanDisk I should have learned from past experiences) which is where I kept my EFS backup. This is on a N900W8, with Knox tripped 0x1 so no chance of warranty.
Do I have quite the expensive paperweight on my hands here now? It seems so but hopefully there is a light at the end of the tunnel for me
Click to expand...
Click to collapse
Out of curiosity, did you have the new bootloader or the old and did you try to dowgrade the firmware?
If you did it might be part of the problem...
Reflash MJ7 in ODIN and that should fix it but you will now have new bootloader that will trip Knox counter when rooted.
ultramag69 said:
Out of curiosity, did you have the new bootloader or the old and did you try to dowgrade the firmware?
If you did it might be part of the problem...
Reflash MJ7 in ODIN and that should fix it but you will now have new bootloader that will trip Knox counter when rooted.
Click to expand...
Click to collapse
No I have not tried downgrading, the Odin firmware I use was always the latest MJ4
Since you've tripped KNOX try this link it'll fix your efs issues.
http://forum.xda-developers.com/showthread.php?p=47014662
It does work, bailed me out and many others. You'll have to go with a custom recovery though to be able to use it. Just boot into download, install custom recovery then flash the zip fix and you're sorted.
Sent from my SM-N9005 using XDA Premium 4 mobile app
I've made a bit of a mess and I need help please. My s4 is softbricked, but as softbricks go, it's rather hard.
I have an early S4 i9505 bought from Carphone Warehouse (UK, unlocked, pre knox). I rooted it, installed TBackup, greenify and got it how I wanted it. Then I downloaded a stock firmware from Sammobile and tested to see if I could get it back to 'warranty' condition, which was a success.
Confident that I could obtain warranty if I needed it, I re-rooted it, installed TB and greenify, and it ran sweetly for months from that point onwards.
I read about the arrival of updates (and knox) and concluded I didn't need them. It was working, leave it alone.
Then out of the blue, my nice stable machine broke. I didn't change anything I was aware of to cause it.
No normal boot.
No recovery.
Download only.
Using Odin, I tried allsorts, eventually getting the same Sammobile firmware to run.
2 days later, it broke again, same as before, but worse!?
Then I tried all sorts of stuff downloading no end of things trying to get it to boot or even go into recovery. The most promising approach was to reload the firmware along with a .pit file, but still no joy. I've lost track of the other things I tried, but I've been doing it for a week, so a lot has been done. In desperation, I even tried downloading the latest firmware, so I now have signs of knox of the odin page.
I now have the following symptoms:
Booting into recovery brings up the blue 'booting recovery' message then just blackness.
Normal boot is exactly the same as above.
Unpowered conection to my laptop gives a 5 second boot loop featuring the buzz only.
I can reliably boot into download and download stuff with Odin and change the little Odin page status messages. After (foolishly) trying the latest firmware, these messages say
ODIN MODE
PRODUCT NAME GT-I9505
CURRENT BINARY Samsung Official
SYSTEM STATUS Official
KNOX KERNEL LOCK 0x0
KNOX WARRANTY VOID 0x0
CSB-CONFIG-LSB 0x30
WRITE PROTECTION: enable
eMMC BURST MODE enabled
Please can anyone give me some advice on what else I could try?
Thanks
Steve
Wrinklespots said:
ODIN MODE
PRODUCT NAME GT-I9505
CURRENT BINARY Samsung Official
SYSTEM STATUS Official
KNOX KERNEL LOCK 0x0
KNOX WARRANTY VOID 0x0
CSB-CONFIG-LSB 0x30
WRITE PROTECTION: enable
eMMC BURST MODE enabled
Please can anyone give me some advice on what else I could try?
Thanks
Steve
Click to expand...
Click to collapse
If anything else is not working (especially, if you're unable to go to recovery) I'd call sammy service center. Your download mode says that you did not rooted your phone, and knox is untouched either.
spamtrash said:
If anything else is not working (especially, if you're unable to go to recovery) I'd call sammy service center. Your download mode says that you did not rooted your phone, and knox is untouched either.
Click to expand...
Click to collapse
Thanks for looking spamtrash.
I was wondering if I could get away with that. It does look good from the Odin display, but the flash counter must have a pretty high number in it by now! Won't that show up somewhere?
Do you think it does actually have a fault on it, rather than just some software that's messed up and needs tweaking?
Thanks
Steve
Wrinklespots said:
Thanks for looking spamtrash.
I was wondering if I could get away with that. It does look good from the Odin display, but the flash counter must have a pretty high number in it by now! Won't that show up somewhere?
Do you think it does actually have a fault on it, rather than just some software that's messed up and needs tweaking?
Thanks
Steve
Click to expand...
Click to collapse
1. Are you able to go to recovery mode?
2. Assuming that your previous communicates were taken from the screen in download mode - you're clean.
If answer for 1 is: NO, and assuming 2: do not bother the flash counter. Flash counter does not means you messed with custom ROMs, it just means amount of the ROM update tries. As they are unable to prove that the counter was not increased by failed KIES updates, you're safe.
To go deeper, service will have to flash and wipe your phone.
One thing: remove your sd card prior to giving/sending it out.
Try a different usb cable.I was in same boat as you (after stupidly thinking mobile odin pro liked modems).
Luckily I had an unused cable off my tab 3.
SOLVED:
Finally got Odin to work! Tried it on an actual PC laptop and not my vmware macbook. It failed at 99% the first time so tried another USB port and it went up and passed! this is on 4.4.2. I guess the main reason why the other firmwares would fail was because I originally tried to flash odin 4.4.2 but at this point I had no idea about knox and that you cannot go back in firmwares. So my last attempt was to push 4.4.2 after looking into the phones info saying it was on I337MVLUFNC1 bootloader. I was starting to think I had bricked this phone! sound works and calls working fine! whoop!
some history on the device:
- S4 was on Beanstalk 4.4.2, rooted.
- phone was starting to freeze up on this ROM so
- decided to go back to stalk Rogers rom via ODIN
- tried Odin v 3.09/v3.07/3.04 all failed
- tried different cables and two different computers. failed
- So then I decided to load TWRP back in from ODIN = Pass!, I get into recovery and load up a backup. This works but had NO sound or video playback and calls wont go through/freeze phone in call app.
- more tinkering, thinking it was maybe the Kernel/Modem. I download different Kernel/modm for the phone and sound still didnt work.
- Tried Firnware I337MVLUEMK6_I337MOYAEMK6_RWC, as well as the current I337MVLUAMG1_I337MOYAAMG1_RWC both were downloaded from sammobile.com
- tried kies and it cant connect to phone or does anything.
Phone errors:
-top corner of display shows:
Odin mode
product name: sgh-I337M
Current Binary: Samsung official
System status: Custom
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x1
CBS - Config - LSB: 0x30
Write Protection: Enabled
eMMC Burst mode enabled
Currently:
- I can load TWRP anytime.
- I can also reload backups, install roms but sound, video, phone calls, mic dont work. some roms are super laggy as well.
- so phone is still useless atm.
ill try Odin again and copy the fail script.
it fails immediatly after system write.
iv searched knox trip, and some people have gotten stock firmware back on their device. but i have no way of doing so since odin fails horribly.. To my understanding if Knox has been tripped then you cannot downgrade firmware. but iv been trying to get 4.3 or even 4.4.2 on it and it fails.
actually i shouldnt say i tried to get 4.3 on it, because it seems i did get it on the phone at one point but then it had absolutly no signal. It would have signal for maybe 3 minutes then it drops it completely. tried APN settings and still wouldnt kick it. only thing I didnt try on that attempt was load up a different modem. which i should have.. but now cant even get that rom back on here as my sister deleted it..
any help would be appreciated.
Alright so im back on a backup from my other S4, running ok. signal is fine and wifi works. only thing is upon boot up i get:
- Unfortunately, Google Dialer has stopped.
- unfortunately, the process android.process.acore has stopped.
-unfortunately, the process android.process.meida has stopped.
i can hit ok many times but it keeps popping up.
so im still unable to do anything. i can still navigate through the phone but the pop ups come often.
UPDATE:
- Did a factory data reset within the phone and I dont get the pop ups anymore. but the Sound is still not working
one thing that's weird is when I use the app Phone Info the Sales Code (aka Region Code) is: ATT, but my working s4 with the same ROM says VMC under Region code? is this making my sisters phone not function properly? or maybe this is why I cannot flash stock rogers through odin because the phone is thinking its an ATT device and not a Rogers one?
Just wondering, since Knox is tripped am I able to still use Odin to flash to stock? Just want to clarify that before I waste more time with odin .
Iv tried rogers 4.2.2, 4.3 and pretty sure iv tried 4.4.2. But I'm going to download it and try that one again.
Phone was previously on 4.3 without signal. So I'm guessing that's the very least I can load up since Knox is tripped correct? I shouldn't have issues flashing Odin 4.4 stock rogers?
Just wondering why it fails once its writing to system..