Hello!
I post here since I have many question mostly related to the CSC which seems to lock everything up right now. BIG Thanks to the XDA community which is the most expert about Android on the web!
I have a French Note 3 4G already rooted with URDLV without tripping Knox.
Please, I want to :
- upgrade my firmware (from MI7 to ... ??? I have Mobile Odin already)
- be able to change the CSC to find a ROM more adapted to my local network (Thailand). I lost the connection many times because of that.
WATCH OUT! There is only the exynos version in Thailand so I don't know which ROM (Malaysia, Vietnam ??) would be the best.
My CSC is N9005BOGBMI3_BOG. I have currently the MI7 version (AP : N9005XXUBMI7). I froze Knox with Titanium.
So, how..
- can I change of ROM without tripping KNOX ?
- can I install CRMW without tripping KNOX ?
- update my phone without tripping KNOX ?
- change my modem/RILS without tripping....... KNOX!?
- can I send a insulting email to Samsung in order to clearly express what I think about their new policy!!
I already downloaded this ROM (BOG-N9005XXUDMJ7-20131121184400) can I flash it and how ?
Thank you very very much and merry Xmas!!
Nemorensis32 said:
...
So, how..
- can I change of ROM without tripping KNOX ?
- can I install CRMW without tripping KNOX ?
- update my phone without tripping KNOX ?
- change my modem/RILS without tripping....... KNOX!?
- can I send a insulting email to Samsung in order to clearly express what I think about their new policy!!
I already downloaded this ROM (BOG-N9005XXUDMJ7-20131121184400) can I flash it and how ?
...
Click to expand...
Click to collapse
0) Backup your current EFS! Is your phone unlocked? Did you have any problems as a result of EU region-lock? Also note that changing the CSC will not make any change in how the modem works, so no change in signal quality.
1) Flash that MJ7 with Mobile Odin PRO - read details in the specific thread that explains how you can use MOP to upgrade and keep root (and knox 0x0). MJ7 will improve and fix a lot of things.
2) No, at this point ANY kernel or recovery that is not signed my Samsung WILL trip Knox
3) You keep updating using MOP
4) Modem will be updated automatically when you do 1) and 3)
5) You can, but I doubt it will make any difference.
xclub_101 said:
0) Backup your current EFS! Is your phone unlocked? Did you have any problems as a result of EU region-lock? Also note that changing the CSC will not make any change in how the modem works, so no change in signal quality.
1) Flash that MJ7 with Mobile Odin PRO - read details in the specific thread that explains how you can use MOP to upgrade and keep root (and knox 0x0). MJ7 will improve and fix a lot of things.
2) No, at this point ANY kernel or recovery that is not signed my Samsung WILL trip Knox
3) You keep updating using MOP
4) Modem will be updated automatically when you do 1) and 3)
5) You can, but I doubt it will make any difference.
Click to expand...
Click to collapse
Thanks for your answer ! However, a little precision please . The ROM you told to flash doesn't have the same original CSC than I had. Is it possible to do that ?
Other thing, I was talking about changing my modem/RIL in order to get a better hook where I live (each modem are customed in order to work as well as possible with each local related network).
And just now, I use an app called EFS to backup my EFS and then my NVRAM. I lost my connexion.... Not SIM inserted it says!! :'( :'(
Nemorensis32 said:
Thanks for your answer ! However, a little precision please . The ROM you told to flash doesn't have the same original CSC than I had. Is it possible to do that ?
Other thing, I was talking about changing my modem/RIL in order to get a better hook where I live (each modem are customed in order to work as well as possible with each local related network).
And just now, I use an app called EFS to backup my EFS and then my NVRAM. I lost my connexion.... Not SIM inserted it says!! :'( :'(
Click to expand...
Click to collapse
The second/newer ROM that you listed had the same region/carrier as the 1st that you listed (and which I assumed it was the original one) = BOG (which I believe is a French carrier). Of course the newer one is not the same version, it is a newer one for that same region/carrier. Of course all assuming that I understood correctly and that your initial CSC region/carrier was BOG.
The change in modem is more carrier-specific than region-specific, in the very first step I would recommend avoiding that, see first how the new BOG modem does under your current conditions.
Hmm, the EFS backup is just a read and should not result in such problems - the app probably tried to do something like unmounting the partition. Just fully reboot the phone and as long as no destructive write was done to that partition things should be back to your previous state (and assuming that the app indeed unmounted the EFS partition then it is very likely it also made a good backup).
xclub_101 said:
The second/newer ROM that you listed had the same region/carrier as the 1st that you listed (and which I assumed it was the original one) = BOG (which I believe is a French carrier). Of course the newer one is not the same version, it is a newer one for that same region/carrier. Of course all assuming that I understood correctly and that your initial CSC region/carrier was BOG.
The change in modem is more carrier-specific than region-specific, in the very first step I would recommend avoiding that, see first how the new BOG modem does under your current conditions.
Hmm, the EFS backup is just a read and should not result in such problems - the app probably tried to do something like unmounting the partition. Just fully reboot the phone and as long as no destructive write was done to that partition things should be back to your previous state (and assuming that the app indeed unmounted the EFS partition then it is very likely it also made a good backup).
Click to expand...
Click to collapse
Now I'm confused.
You talk about BOG as a carrier when I talk about CSC. Indeed, this is the same CARRIER but it seems to not be the same CSC since it didn't appeared in sammobile web while I search for all ROMs based on this CSC.
About the IMEI, my main problem now. I just reflashed a ROM modified by VEGA. It still bootloops !!!
I heard on that topic that we could wipe our EFS partition since the phone is able to rebuild it itself but I doubt about my own understanding here.. Maybe I could use in ODIN the option "Phone EFS clear" ?? http://forum.xda-developers.com/showthread.php?t=2471421
Please, I would really appreciate some help here!!
EDIT : Here is the damn software with what I bricked my phone. Maybe the comments can help you or anyone willing to save my all new phone. That's Xmas ... lol
https://play.google.com/store/apps/details?id=nl.boris.efs
Nemorensis32 said:
Now I'm confused.
You talk about BOG as a carrier when I talk about CSC. Indeed, this is the same CARRIER but it seems to not be the same CSC since it didn't appeared in sammobile web while I search for all ROMs based on this CSC.
About the IMEI, my main problem now. I just reflashed a ROM modified by VEGA. It still bootloops !!!
I heard on that topic that we could wipe our EFS partition since the phone is able to rebuild it itself but I doubt about my own understanding here.. Maybe I could use in ODIN the option "Phone EFS clear" ?? http://forum.xda-developers.com/showthread.php?t=2471421
Please, I would really appreciate some help here!!
EDIT : Here is the damn software with what I bricked my phone. Maybe the comments can help you or anyone willing to save my all new phone. That's Xmas ... lol
https://play.google.com/store/apps/details?id=nl.boris.efs
Click to expand...
Click to collapse
You should have not used a program that was not specifically reported to work on Note 3, even more so with a program that does not seem to have so great feedback (there are a number of other ways to backup your EFS, searching for those around would have helped).
1) what is your current Odin status?
2) try to go to Samsung recovery, wipe data and cache from there, then go to download mode and try to write again the URDLV version that previously worked.
xclub_101 said:
You should have not used a program that was not specifically reported to work on Note 3, even more so with a program that does not seem to have so great feedback (there are a number of other ways to backup your EFS, searching for those around would have helped).
1) what is your current Odin status?
2) try to go to Samsung recovery, wipe data and cache from there, then go to download mode and try to write again the URDLV version that previously worked.
Click to expand...
Click to collapse
Today I am sick. It made me probably sloppy on that one.. Yesterday I spent one day to root my phone without doing a mistake and without disturbing anyone on any forum. I handled it.
Concerning Odin, in Odin mode on the mobile I have everything good. I managed to reflash my Vega ROM from yesterday but I still get bootloops.
I have one line of code (still in Odin mode on my n9005 ) : RP SWREV S1, T1, R1, A1, P1
On my PC, Odin worked obviously fine. No error and the status is <ID:0/004> Added!!
Do I really have to flash a stock ROM ? I really fear to lose my root and reduce the possibilities of fixing my phone. Yesterday, since the tuto for URDLV didn't work, I packed a TAR with a mix of my original files and the modified files and it worked fine.
I try to wipe now... :'(
Thanks
I get bootloops during the setup of the "first launch". ....
"the system process doesn't respond. Do you want to quit ?"
PS: I installed the VEGA repacked with the original files missing to make a complete ROM.
Nemorensis32 said:
...
Concerning Odin, in Odin mode on the mobile I have everything good. I managed to reflash my Vega ROM from yesterday but I still get bootloops.
I have one line of code (still in Odin mode on my n9005 ) : RP SWREV S1, T1, R1, A1, P1
On my PC, Odin worked obviously fine. No error and the status is <ID:0/004> Added!!
Do I really have to flash a stock ROM ? I really fear to lose my root and reduce the possibilities of fixing my phone. Yesterday, since the tuto for URDLV didn't work, I packed a TAR with a mix of my original files and the modified files and it worked fine.
I try to wipe now... :'(
Thanks
Click to expand...
Click to collapse
It is still good great that the EFS program did not trigger knox! (but of course there still is the major question about what the program did).
I never said to write stock, I said the URDLV ROM, the one generated by Universal Root De La Vega and which worked OK for you previously.
The point was that wiping before Odin might fix some of the bootloops.
That being said the OLD original stock ROM, the same one that came inside your phone (and which you should have used as base for your original URDLV) should not create any knox problem. You will lose root but you should be able to gain it back by repeating the exact sequence from URDLV. And when stuff like this is happening wipe before Odin just to be certain.
xclub_101 said:
It is still good great that the EFS program did not trigger knox! (but of course there still is the major question about what the program did).
I never said to write stock, I said the URDLV ROM, the one generated by Universal Root De La Vega and which worked OK for you previously.
The point was that wiping before Odin might fix some of the bootloops.
That being said the OLD original stock ROM, the same one that came inside your phone (and which you should have used as base for your original URDLV) should not create any knox problem. You will lose root but you should be able to gain it back by repeating the exact sequence from URDLV. And when stuff like this is happening wipe before Odin just to be certain.
Click to expand...
Click to collapse
I CAN'T get it back since I have a constant bootloop. I can't copy the URDLV files on my internal SD . The phone reboots ! Anyway, my computer doesn"t detect my phone either. Never.
On the buggy software I used, you have two options . One for EFS and one for NVRAM. I press both of them with one reboot each. Maybe it is the NVRAM which is buggy ?
I hate that developper who put his warning at the END of the presentation of his software.... (my fault too... )
Nemorensis32 said:
I CAN'T get it back since I have a constant bootloop. I can't copy the URDLV files on my internal SD . The phone reboots ! Anyway, my computer doesn"t detect my phone either. Never.
On the buggy software I used, you have two options . One for EFS and one for NVRAM. I press both of them with one reboot each. Maybe it is the NVRAM which is buggy ?
I hate that developper who put his warning at the END of the presentation of his software.... (my fault too... )
Click to expand...
Click to collapse
Let me get a better idea of what is happening:
- you went to recovery and wiped data and cache
- you went to download mode and from Odin you wrote the URDLV-generated tar.md5
- you restarted and you got bootloops?
xclub_101 said:
Let me get a better idea of what is happening:
- you went to recovery and wiped data and cache
- you went to download mode and from Odin you wrote the URDLV-generated tar.md5
- you restarted and you got bootloops?
Click to expand...
Click to collapse
No, I have bootloops since I pressed the two options in "Efs by BORIS.X.1" app. First, the option "EFS backup" (I got a reboot but I thought it was normal), secondly, "NVRAM backup" (I got a second reboot). Since then, my phone keep rebooting. I reflashed with my former VEGA ROM, Then I did the wiped everything and flashed again. Always with Odin. I kept all that time to have bootloops and (I forgot to repeat it!) no connexion/no data.
Hope it's clear enough now..
Btw, I don't manage to use EFS pro. It can't find my phone (and my computer neither..)
What happened!! :/
(I have to go to a short meeting/dinner right now. I'll be right back) . I don't see any solution on internet yet.
Thank you so much for helping me.
ok. I'm back.
Any solution ?
ok. I'm back.
Any solution ?
Nemorensis32 said:
ok. I'm back.
Any solution ?
Click to expand...
Click to collapse
At this point I have no idea what that EFS program did
Also I wonder if you had Reactivation lock ON - but I assume you did not.
The only other that I can think of is to:
- wipe again everything in recovery
- write in Odin the original Samsung ROM that you had on the phone; ideally this should revert things to something close to your original state (but that is not 100% certain - the original ROM might not be "full wipe" and certain partitions might be left with some content).
Ok. Thanks. Il will wait for someone else. Or maybe open a new topic. Merry christmas.
Related
Hi everyone,
please don't laugh at me but I am into big troubles here thanks to my crazy cat who (suffering some sort of playing attack) jumped on the table, kicked my phone and ripped out the USB cable in the middle of flashing a new modem
So now, when I switch on my device (N9005XXUBMJ1 build) and swipe the lockscreen, I get this pop-up:
Process system isn't
responding.
Do you want to close it?
[Wait] [OK]
Click to expand...
Click to collapse
Apart from that I also get bootloops every 20 or 30 seconds, unknown baseband, no sound, no signal.
I tried literally everything from cache/full wipe to flashing N9005XXUBMI7 and J1 stock (there is J3 available for my country but I refrain from it due to the locked bootloader), flashing different modems (N9005XXUBMI6, J1 and J2) with different cables and Odin versions, booting in Flight mode with SD and/or SIM card removed and battery taken out..... everything without success.
My guess is that there is some issue with the EFS folder and when I try to open the dialer (Phone) I get a FC preventing me from seeing if my IMEI is still there (I reckon it's not).
I can boot into Recovery/Download but that's it. I was wondering whether there is a chance to ADB sideload something in Recovery mode as I do have a copy of my EFS folder (not sure, tough, if it's functional) and, in theory, even a backup of my EFS using Samsung Note 3 EFS Backup/Restore although the programme seems to be useless.
Of course, I searched the forums for all kinds of solutions but I couldn't find anything that helped me restoring full functionality to my device.
The thing is that I want to keep my Knox 0x0 in case I do need to bring my device to a Service Center so flashing any custom ROM is not an option right now.
I would be very grateful for help and any hints/suggestions are highly appreciated.
Thanks a lot in advance!
Chalao said:
Hi everyone,
please don't laugh at me but I am into big troubles here thanks to my crazy cat who (suffering some sort of playing attack) jumped on the table, kicked my phone and ripped out the USB cable in the middle of flashing a new modem
So now, when I switch on my device (N9005XXUBMJ1 build) and swipe the lockscreen, I get this pop-up:
Apart from that I also get bootloops every 20 or 30 seconds, unknown baseband, no sound, no signal.
I tried literally everything from cache/full wipe to flashing N9005XXUBMI7 and J1 stock (there is J3 available for my country but I refrain from it due to the locked bootloader), flashing different modems (N9005XXUBMI6, J1 and J2) with different cables and Odin versions, booting in Flight mode with SD and/or SIM card removed and battery taken out..... everything without success.
My guess is that there is some issue with the EFS folder and when I try to open the dialer (Phone) I get a FC preventing me from seeing if my IMEI is still there (I reckon it's not).
I can boot into Recovery/Download but that's it. I was wondering whether there is a chance to ADB sideload something in Recovery mode as I do have a copy of my EFS folder (not sure, tough, if it's functional) and, in theory, even a backup of my EFS using Samsung Note 3 EFS Backup/Restore although the programme seems to be useless.
Of course, I searched the forums for all kinds of solutions but I couldn't find anything that helped me restoring full functionality to my device.
The thing is that I want to keep my Knox 0x0 in case I do need to bring my device to a Service Center so flashing any custom ROM is not an option right now.
I would be very grateful for help and any hints/suggestions are highly appreciated.
Thanks a lot in advance!
Click to expand...
Click to collapse
do you have cwm
jaythenut said:
do you have cwm
Click to expand...
Click to collapse
No, unfortunately I don't. There is just stock recovery and no way to install CWM right now with all the FCs and bootloops.
I am also afraid that flashing anything but stock will trip Knox (now it is still 0x0) which, in case I need to bring my device to one of Sammy's Service Centres for repair, would not be good to have.
Any educated guesses of whatelse I could try?
What about flashing new MJ6 firmware? This could help
Don Mueang said:
What about flashing new MJ6 firmware? This could help
Click to expand...
Click to collapse
No it won´t help. I have exatly the same problem as u and i dunno how to fix it. I tried it with custom roms = no success. i tried to fix my problem with new samsung firmware = no success. Don´t think about flashing custom firmware, my knox is cause of that on 0x1 now.
I made also a thread about this issue, follow this link http://forum.xda-developers.com/showthread.php?t=2517945. and u will find a possible solution there.
I tried the possible solution but somehow i get
List of devices attached
66ee6420 offline.
Maybe im doing some mistakes or im just to noobie for adb stuff. (never used it before)
Try it and tell me if it works for u.
Good luck, i need it too.
My device is now in Samsung service center, the symptoms are the same like you, the only difference is that my baseband is ok, I can do a call.
Max One said:
No it won´t help. I have exatly the same problem as u and i dunno how to fix it. I tried it with custom roms = no success. i tried to fix my problem with new samsung firmware = no success. Don´t think about flashing custom firmware, my knox is cause of that on 0x1 now.
I made also a thread about this issue, follow this link http://forum.xda-developers.com/showthread.php?t=2517945. and u will find a possible solution there.
I tried the possible solution but somehow i get
List of devices attached
66ee6420 offline.
Maybe im doing some mistakes or im just to noobie for adb stuff. (never used it before)
Try it and tell me if it works for u.
Good luck, i need it too.
Click to expand...
Click to collapse
Well, flashing TWRP might be the only solution to the problem apart from sending the device in to Samsung Customer Service for repair. The thing is that it will void my warranty as you noticed yourself given that flashing any custom ROM trips Knox to 0x1. So I consider TWRP an absolutely last resort if everything else fails, although I can't imagine that it will be able to restore EFS if you didn't make a backup of it before at some point (which I did, but the tool seems to be crap and useless --> be warned at this point, DO NOT try any EFS backup/restore with this tool).
Regarding the adb stuff (on which I am not an expert neither), did you try to adb connect 66ee6420 assuming you have USB debugging enabled on your device?
Anyways, I also found out that my CSC is missing as well apart from the baseband so I tried to flash in Odin stock modem and CSC together. Didn't help unfortunately. So if anyone has some more suggestions what to do you are welcome to let us know please! Seems there are more fellow users with the same or similar problem....
Anyone out there who has an idea how to deal with the "Process system isn't responding" error without flashing TWRP or another custom ROM (reasons explained above)?
All reasonable hints or suggestions or educated guesses are appreciated! Thanks.
Update
"Firmware upgrade and initialisation" in Kies doesn't work neither. Only two options at this point seem to either flash custom recovery and hope for the best or send it in for repair.
Will try my luck with Samsung Service Plaza in Delhi (India) and see if they can fix the LTE version :fingers-crossed:
Chalao said:
"Regarding the adb stuff (on which I am not an expert neither), did you try to adb connect 66ee6420 assuming you have USB debugging enabled on your device
Click to expand...
Click to collapse
Yes i tried it. Im getting always now
List of devices attached
66ee6420 unauthorized instead of offline after installing latest adb version
My pc wants to install the "Samsung Mobile MTP device" driver but its impossible cause that damn phone keeps rebooting every 30 seconds.
Chalao said:
"Firmware upgrade and initialisation" in Kies doesn't work neither
Click to expand...
Click to collapse
Yeah i tried that too, but the results ends in an error dunno exactly what the name of the error was.
Process "system" not responding / EFS gone
Hi all,
first of all hello to everybody, this is my first post to xda. I'm from Germany and a former iPhone user. Now i got my Note 3, but came really fast into trouble..
having the same issue here right now with my Galaxy Note 3 N9005 and can't get any results. Unfortunately i have no backup of my efs and the efs folder on my phone is empty
I still get into downlad same as recovery mode but nothing helps. Flashed the phone via Odin several times with no results.
I tried to fix the problem with the adb shell commands but my phone still has problems with the system process. As international user i have the problem that v2.6.3.2 neither 2.6.3.1 is available for download. I tried with v2.6.3.8
I read something about a 3-parted firmware, is this maybe a possibility?
I'm sorry I didn't post to the TWRP-Thread, but i have an insufficient amount of posts
Hope you can help me, I'm pretty frustrated atm
Lavalio
Lavalio said:
Hi all,
first of all hello to everybody, this is my first post to xda. I'm from Germany and a former iPhone user. Now i got my Note 3, but came really fast into trouble..
having the same issue here right now with my Galaxy Note 3 N9005 and can't get any results. Unfortunately i have no backup of my efs and the efs folder on my phone is empty
I still get into downlad same as recovery mode but nothing helps. Flashed the phone via Odin several times with no results.
I tried to fix the problem with the adb shell commands but my phone still has problems with the system process. As international user i have the problem that v2.6.3.2 neither 2.6.3.1 is available for download. I tried with v2.6.3.8
I read something about a 3-parted firmware, is this maybe a possibility?
I'm sorry I didn't post to the TWRP-Thread, but i have an insufficient amount of posts
Hope you can help me, I'm pretty frustrated atm
Lavalio
Click to expand...
Click to collapse
Willkommen im Club :laugh:
28826566 37
Ziemlicher Dreck - pretty crappy
Hope somebody got an idea
I have the same issue.. happened the first day i've got the phone..
sometimes its okay but when I reboot it often hangs or boots up and then I get the system process issue with a black background and no signal..
Scheiße.. does anyone find a solution? IM STUCK all afternoon/night with this problem. Some guy told first to flash pit than the stock firmware... but no help. Where da fack i can find the pit for 32gb n9005
SOLUTION !!!!! http://forum.xda-developers.com/showpost.php?p=46205598&postcount=1
theresident said:
SOLUTION !!!!! http://forum.xda-developers.com/showpost.php?p=46205598&postcount=1
Click to expand...
Click to collapse
Wont work for me.
http://forum.xda-developers.com/showthread.php?t=2507403
Try with flashing this
Solution.
PREPARE:
NON-HLOS.bin <- extracted from original firmware
boot.img <- extracted from original firmware
cache.img.ext4 <- created by Universal RDLV
hidden.img.ext4 <- extracted from original firmware
modem.bin <- extracted from original firmware
recovery.img <- extracted from original firmware
system.img.ext4 <- created by Universal RDLV
HOW TO:
install cygwin64 (with all default)
start it once
go to c:/cygwin/home/<username_u_have>
put mentioned files there
in cygwin:
tar -H ustar -c NON-HLOS.bin boot.img cache.img.ext4 hidden.img.ext4 modem.bin recovery.img system.img.ext4 > DMJ7.tar
md5sum -t DMJ7.tar >> DMJ7.tar
mv DMJ7.tar DMJ7.tar.md5
-> flash generated file
You can later thank Killberty for the solution.
When it comes to Knox bull**** you don't have to worry. In order for Samsung Service to refuse to repair your phone (in future) with 0x1 they have to prove that YOU caused the problem/damage. The can't just say bye bye when they see 0x1. I'm talking from my own experience. Never had any problems with sending the phone back to service with custom roms, binary, knox 0x1 and so on... Phones can die even if you don't root or flash anything, you know it and they do. Just stand up for yourself and demand explanation to how the phone got bricked just because your rooted it. In THIS case it was your fault. Good luck!
Flowbax said:
Solution.
PREPARE:
NON-HLOS.bin <- extracted from original firmware
boot.img <- extracted from original firmware
cache.img.ext4 <- created by Universal RDLV
hidden.img.ext4 <- extracted from original firmware
modem.bin <- extracted from original firmware
recovery.img <- extracted from original firmware
system.img.ext4 <- created by Universal RDLV
HOW TO:
install cygwin64 (with all default)
start it once
go to c:/cygwin/home/<username_u_have>
put mentioned files there
in cygwin:
tar -H ustar -c NON-HLOS.bin boot.img cache.img.ext4 hidden.img.ext4 modem.bin recovery.img system.img.ext4 > DMJ7.tar
md5sum -t DMJ7.tar >> DMJ7.tar
mv DMJ7.tar DMJ7.tar.md5
-> flash generated file
You can later thank Killberty for the solution.
When it comes to Knox bull**** you don't have to worry. In order for Samsung Service to refuse to repair your phone (in future) with 0x1 they have to prove that YOU caused the problem/damage. The can't just say bye bye when they see 0x1. I'm talking from my own experience. Never had any problems with sending the phone back to service with custom roms, binary, knox 0x1 and so on... Phones can die even if you don't root or flash anything, you know it and they do. Just stand up for yourself and demand explanation to how the phone got bricked just because your rooted it. In THIS case it was your fault. Good luck!
Click to expand...
Click to collapse
Np guys
EDIT: this does not rly help for restoring EFS - just having latest firmware and root with camer and wifi working...
i read in some thread you can just delete EFS and it would restore itself ( NO WARRANTY for this)
leave a 'thanks' if i helped
SM-N9005 URDLV 0x0
XDA Developers 4 premium app
Hi! :crying:
I had the bad idea to use this software (EFS by BORIS.X.1 ) and I didn't see the warning at the END of the presentation of the soft...
I clicked on "backup EFS". The phone reboots straight away. (I thought it was maybe normal).
I clicked on "backup NVRAM". The phone reboots again.
Actually, since that, my phone is almost dead. I could boot but after a few second I got a reboot. --> bootloop.
I did a hard reset via the Android recovery. I reflashed my VEGA ROM (packed with the other missing files from the original stock ROM, so I guess it's full wipe anyway).
I did it many times. Nothing changed. On the top of that I can not access to my WIFI, 3G, on voice (SIM NOT FOUND).
I don't know what to do anymore. I have a MI7 rooter 0x0 phone and I would like to keep it so!!
Please help me since I just bought that phone and spent all the day before to manage the URDLV properly.
:angel: Merry Christmas and thank you in advance! :highfive:
Nemorensis32 said:
Hi! :crying:
I had the bad idea to use this buggy software (EFS by BORIS.X.1 ) and I didn't see the warning at the END of the presentation of the soft...
I clicked on "backup EFS". The phone reboots straight away. (I thought it was maybe normal).
I clicked on "backup NVRAM". The phone reboots again.
Actually, since that, my phone is almost dead. I could boot but after a few second I got a reboot. --> bootloop.
I did a hard reset via the Android recovery. I reflashed my VEGA ROM (packed with the other missing files from the original stock ROM, so I guess it's full wipe anyway).
I did it many times. Nothing changed. On the top of that I can not access to my WIFI, 3G, on voice (SIM NOT FOUND).
I don't know what to do anymore. I have a MI7 rooter 0x0 phone and I would like to keep it so!!
Please help me since I just bought that phone and spent all the day before to manage the URDLV properly.
:angel: Merry Christmas and thank you in advance! :highfive:
Click to expand...
Click to collapse
Your EFS is corrupted by the sounds of it, can you check settings > general > about device and see if your baseband says "Unknown"? If so then...
Only guarantee to unbrick and get your baseband back properly (without EFS back up) is using a custom recovery (tripping KNOX) and using This - used it myself and it does work - But it only works on the N9005
Aside from that, I'm not 100% sure myself without an EFS backup as to how to fix..Good luck
radicalisto said:
Your EFS is corrupted by the sounds of it, can you check settings > general > about device and see if your baseband says "Unknown"? If so then...
Only guarantee to unbrick and get your baseband back properly (without EFS back up) is using a custom recovery (tripping KNOX) and using This - used it myself and it does work - But it only works on the N9005
Aside from that, I'm not 100% sure myself without an EFS backup as to how to fix..Good luck
Click to expand...
Click to collapse
Thank you. Yes, I know that tip but, before making that step, I want to be sure this is only the EFS :
That's the thing! I can't use my phone and access to the menu "state of the phone". It always reboots before. I have also a error message telling "the process SYSTEM doesn't respond. Do you want to terminate it ?" And most of my softs just crash, even contact. I can't dial on my phone!!
Can we say it's only a EFS problem ? In which proportion the soft I used would have damage my phone ??
Thanks
Nemorensis32 said:
Thank you. Yes, I know that tip but, before making that step, I want to be sure this is only the EFS :
That's the thing! I can't use my phone and access to the menu "state of the phone". It always reboots before. I have also a error message telling "the process SYSTEM doesn't respond. Do you want to terminate it ?" And most of my softs just crash, even contact. I can't dial on my phone!!
Can we say it's only a EFS problem ? In which proportion the soft I used would have damage my phone ??
Thanks
Click to expand...
Click to collapse
Yup sounds like an EFS issue, mine done the same with System not responding - I flashed the .zip in custom recovery and it fixed it straight away.
radicalisto said:
Yup sounds like an EFS issue, mine done the same with System not responding - I flashed the .zip in custom recovery and it fixed it straight away.
Click to expand...
Click to collapse
What did you do to brick your phone ?
Nemorensis32 said:
What did you do to brick your phone ?
Click to expand...
Click to collapse
I was messing around with custom kernels, constant rebooting every 60seconds. Managed to check my baseband which said unknown, so went into TWRP and flashed the EFS fix and it booted straight up, baseband back, 3G signal etc
The good thing would be to get an adaptation of this script for Odin !!
i had the efs issue yesterday, exactly as described.
was playing with custom kernels, phone suddenly rebooted and baseband was gone.
i restored mine from a twrp backup.
Nemorensis32 said:
Thank you. Yes, I know that tip but, before making that step, I want to be sure this is only the EFS :
That's the thing! I can't use my phone and access to the menu "state of the phone". It always reboots before. I have also a error message telling "the process SYSTEM doesn't respond. Do you want to terminate it ?" And most of my softs just crash, even contact. I can't dial on my phone!!
Can we say it's only a EFS problem ? In which proportion the soft I used would have damage my phone ??
Thanks
Click to expand...
Click to collapse
Unless we learn more about what that program was trying to do (presumably from the author of the program?) the only other FACT that we know is that writing a custom recovery is GUARANTEED to trip your knox flag; just writing your original Samsung ROM has a good chance to NOT trip knox; if you apply the first then you can never try the 2nd and keep knox, while if you apply the 2nd method and it does not work you still can use the 2nd or something else.
xclub_101 said:
Unless we learn more about what that program was trying to do (presumably from the author of the program?) the only other FACT that we know is that writing a custom recovery is GUARANTEED to trip your knox flag; just writing your original Samsung ROM has a good chance to NOT trip knox; if you apply the first then you can never try the 2nd and keep knox, while if you apply the 2nd method and it does not work you still can use the 2nd or something else.
Click to expand...
Click to collapse
Here's another alternative.
I'll let you know soon!
http://forum.xda-developers.com/showpost.php?p=48818814&postcount=85
Nemorensis32 said:
Here's another alternative.
I'll let you know soon!
http://forum.xda-developers.com/showpost.php?p=48818814&postcount=85
Click to expand...
Click to collapse
To have some script that can be written in Odin would be nice - as long as it does not trip knox. Something which might be a little more complex than it sounds.
Well Asansam can do it with just a rooted device, no need for custom recovery.
So find one with an Asansam box, and just run the "Restore PB" command.
Ratata82 said:
Well Asansam can do it with just a rooted device, no need for custom recovery.
So find one with an Asansam box, and just run the "Restore PB" command.
Click to expand...
Click to collapse
Hum, where I live I will not find one...
SM-N900A
Im having the same problem
i used that program to back Efs
Boris.x.1 and it sent my note 3 into a bootloop
is there anything i can do to fix this
and i cant find a SM-N900A stock firmware to reflash
it is a rooted phone
thank you
Note 3 duos SM-N9002 have same problem after backup internal nvram, help me
I want to flash an Aussie ROM on my HK 32GB n9005. I've been doing some reading and what I think I need to do is as follows...
ghibli3's thread at http://forum.xda-developers.com/showthread.php?t=2550823 specifically addresses this issue and thanks to those contributing there and elsewhere.
Now to check I understand what they are saying before I brick my phone.
I have these:
CSB_signed_HLTE_EUR_OPEN_32G_0718.pit
CSB_signed_HLTE_EUR_OPEN_32G_0805.pit
ghibli3-N9005.pit
ratcom-N9005.pit
I also used ghibli3's N9005-SaveMyPit from http://forum.xda-developers.com/attachment.php?attachmentid=2426123&d=1385903491 to get a copy of my current pit.
I have my original HK MI7 stock, a HK stock MK2 (used to root my phone originally using RDLV) and both an MI7 and MJ7 Aussie ROMs.
So... here is what I think I need to do... Please let me know if this is correct or tell me how to do it better.
Using Odin and with phone in DL mode, USB Debugging on, Samsung drivers and ADB setup on PC...
1. Load a PIT file in [PIT] in Odin and tick [Re-Partition] then [Start]
(1st question, do I reboot the phone or just go to the next step?)
2. Follow RDLV steps to flash the Aussie MJ7 to root the phone.
(2nd question, should I drop back to the MI7 version for the root operation? I don't think it is needed as when I rooted my phone with HK version, I had HK MI7 on the phone and used HK MK2 to root it)
(3rd question, I have Kies 3 on my PC - should I uninstall it before doing any of this or might it be helpful to have it still installed?)
OK, so no comments so far... let's try a slightly different approach.
(4th question, Can I load the PIT into Odin, tick [Re-Partition] and add in the VEGA version of the AP (from RDLV) and then flash them as one?
Journyman16 said:
OK, so no comments so far... let's try a slightly different approach.
(4th question, Can I load the PIT into Odin, tick [Re-Partition] and add in the VEGA version of the AP (from RDLV) and then flash them as one?
Click to expand...
Click to collapse
For using PIT file, you need to add the PIT to Odin when you flash so it'll repartition as it's flashing. However, don't take that as a solid cause I am not 100% sure myself as I haven't messed with PIT files (yet) - but from what I have read that is how it is done. - Have a scan through the HK bricked (solved) threads to be doubley sure cause yeah, it's easy to end up with a brick
Thanks for that. Kinda what I was planning to do but I'm not sure if I do the PIT flash first then do the rest or if I do it all as one process. I'll check out that thread... been looking anywhere I could find a PIT reference.
Well, that was fun... not.
I tried the PIT files with NAND erase all, re-partition f. reset time and Auto reboot all ticked - it failed - I got a systemconnection error. I tried again with each of the PITs listed above except ratcom's - his is from an MJ7 build and I was unsure if that would trip Knox or not.
2 hours pass, with me looking all around XDA and trying a variety of things. Incidentally I think maybe the systemconnect thing might be related to not restarting the phone to get the error screen. It seems Odin can do things when that screen is on that it can't do in plain Download mode. At least, on mine, the eventual fix worked only AFTER I had the error screen (shows the hone pic and a PC pic)
I didn't try flashing CWM. Nor doing anything that might add an MJ7 or KK bootloader. If I trip Knox I want it to be by my choice, not because I can't fix something.
But clearly I am doing something wrong in trying to repartition my phone - none of the PIT flashes worked. None of the flash ROM's worked. I looked around for a MJ3 or less ROM with the 4 files - figured I could get that I could try using a PIT for the right CSC and those files and solve both issues at once.
I tried my MK1 HK Vega image and no go. So I sat and thought it through and realised that last time I had problems I had the error screen NOT download mode so I rebooted the phone and Voila! up popped the error screen. Odin promptly flashed my HK MK1 version and now I am restoring my apps from the extSDcard. Got a bit of setup work to do but it's up and running again.
But I will have to trip Knox now - I'm sick of not having a Nandroid backup that could just restore everything where it was instead of me having to manually put things back as they were.
Any ideas as to what I did wrong?
Journyman16 said:
Well, that was fun... not.
I tried the PIT files with NAND erase all, re-partition f. reset time and Auto reboot all ticked - it failed - I got a systemconnection error. I tried again with each of the PITs listed above except ratcom's - his is from an MJ7 build and I was unsure if that would trip Knox or not.
2 hours pass, with me looking all around XDA and trying a variety of things. Incidentally I think maybe the systemconnect thing might be related to not restarting the phone to get the error screen. It seems Odin can do things when that screen is on that it can't do in plain Download mode. At least, on mine, the eventual fix worked only AFTER I had the error screen (shows the hone pic and a PC pic)
I didn't try flashing CWM. Nor doing anything that might add an MJ7 or KK bootloader. If I trip Knox I want it to be by my choice, not because I can't fix something.
But clearly I am doing something wrong in trying to repartition my phone - none of the PIT flashes worked. None of the flash ROM's worked. I looked around for a MJ3 or less ROM with the 4 files - figured I could get that I could try using a PIT for the right CSC and those files and solve both issues at once.
I tried my MK1 HK Vega image and no go. So I sat and thought it through and realised that last time I had problems I had the error screen NOT download mode so I rebooted the phone and Voila! up popped the error screen. Odin promptly flashed my HK MK1 version and now I am restoring my apps from the extSDcard. Got a bit of setup work to do but it's up and running again.
But I will have to trip Knox now - I'm sick of not having a Nandroid backup that could just restore everything where it was instead of me having to manually put things back as they were.
Any ideas as to what I did wrong?
Click to expand...
Click to collapse
2nd link in my signature.
Follow it to step 6. Then flash whatever ROM you want. Make sure your phone is 32 gigs or more. Won't work on 16 gb version.
So this gets a bit strange now... I downloaded Phone Info from Play Store and ran it. I did that because I noticed I was having Wifi issues - it was working but kept thinking it was off - I'd click it to turn it on and the button wouldn't go green, but I had signal in the Notification bar. Going to Recovery to clear cache showed it was now applying CSC-code as BTU instead of TGY, so SOMETHING worked when I was doing the PITs.
So, Phone Info shows my Region Code as BTU, my CSC country as UK/IRE and my CSC Country ISO as GBBut I have a mix of ROM info:
Bootloader: ZHUBMI7
Baseband: ZHUDMJ9
PDA: XXUDMK2
CSC: OXADMK2
So, PDA and CSC are from a UK MK2 I tried to use early on and failed with, while BL and BB are from the original HK MI7 (BL) and the HK MK1 I rooted with.
So my question is now, can I now flash a BTU or other normal ROM onto my phone, using the RDLV process to make sure I get root and don't trip Knox?
IIRC I think the process works up to MK2 (and certainly does to MK1 as that what I used originally) so I should be able to DL (say) XXUBMJ1 to use for the BL and use XXUDMK2 for the root process. (i.e. the same as I did using HK MI7 for the BL and HK MK1 for the root process)
3 questions:
1. Is it the PDA that determines the partition Hong Kong users have such problems with? Or is it the Bootloader?
2. Can anyone think of a reason why this would not work? (now my CSC is BTU)
3. Could I now use an Aussie ROM to run the RDLV process?
FeralFire said:
2nd link in my signature.
Follow it to step 6. Then flash whatever ROM you want. Make sure your phone is 32 gigs or more. Won't work on 16 gb version.
Click to expand...
Click to collapse
Thanks for the Reply.
For now I'd prefer to stay away from KK ROMs - too many people having issues, and the prevention of returning to 4.3 is, to me, a killer until Samsung get the bugs out. Given that many people are doing OK with KK, I think it is unlikely Samsung will do much about the bugs until a larger number of people have problems and start bombarding their support lines.
Plus, on 4.3 I have a very fast phone that gives more than 2 days use even with fairly heavy use (for me) and up to 4 days for light use. Why make an irreversible change when the phone is doing well already? For me the next step is custom recovery - I don't like not having a Nandroid BU and several times now after restoring apps I find I need to fix permissions - without custom recovery that means a laborious uninstall/reinstall from Play Store, one app at a time. Pisses me off...
I find it interesting that Samsung are clearly using users such as XDA members as their testing area, while at the same time shutting down the activities we like to do. (Custom ROMs etc) I say clearly using us because otherwise there is no excuse for the regularity of leaked ROMs - Samsung pass it on to us to try and I would bet, have staff watching us to see what issues we have.
So it seems a bit counter-productive to work so hard to lock the phones so we can't play with them.
Journyman16 said:
Thanks for the Reply.
For now I'd prefer to stay away from KK ROMs - too many people having issues, and the prevention of returning to 4.3 is, to me, a killer until Samsung get the bugs out. Given that many people are doing OK with KK, I think it is unlikely Samsung will do much about the bugs until a larger number of people have problems and start bombarding their support lines.
Plus, on 4.3 I have a very fast phone that gives more than 2 days use even with fairly heavy use (for me) and up to 4 days for light use. Why make an irreversible change when the phone is doing well already? For me the next step is custom recovery - I don't like not having a Nandroid BU and several times now after restoring apps I find I need to fix permissions - without custom recovery that means a laborious uninstall/reinstall from Play Store, one app at a time. Pisses me off...
I find it interesting that Samsung are clearly using users such as XDA members as their testing area, while at the same time shutting down the activities we like to do. (Custom ROMs etc) I say clearly using us because otherwise there is no excuse for the regularity of leaked ROMs - Samsung pass it on to us to try and I would bet, have staff watching us to see what issues we have.
So it seems a bit counter-productive to work so hard to lock the phones so we can't play with them.
Click to expand...
Click to collapse
You need the international pit file in your phone. Flashing the CSC file will put that pit in your phone. It won't touch the bootloader or the system files.
FeralFire said:
You need the international pit file in your phone. Flashing the CSC file will put that pit in your phone. It won't touch the bootloader or the system files.
Click to expand...
Click to collapse
Unfortunately, PIT's don't seem to come easy. As above I have about 4 of them I tried. There seems a bit of a disconnect between what the AP/CP/CSC are and what the files in a ROM are e.g. in XXUBMH1 there's boot.img, recovery.img, system.img.ext4, userdata.img.ext4, persdata.img.ext4, persist.img.ext4 and in XXUBMI7 there's sbl1.mbn, aboot.mbn, rpm.mbn, tz.mbn, sdi.mbn, NON-HLOS.bin, boot.img, recovery.img, system.img.ext4, modem.bin, cache.img.ext4, hidden.img.ext4
While I've been around a while now, this seems to be a blank spot for me at present - how do I flash a CSC? From reading it seems some ROM.s come with 4 or 5 files, e.g. see attachment - but I haven't been able to find one yet. (the one in the pic was hosted on Hotfiles which is now defunct thanks to the Almighty USA draconian control freaks. )
Update: I think I have found a copy of it so I can try that when it finishes DL'ing.
Other than that, anyone know of where there might be another such ROM to DL? Also if I am flashing a CSC file do I flash the PIT as well (i.e. at the same time) or do the PIT first?
Which Odin options get ticked for a PIT? I tried [F. Reset Time] [Re-Partition] [Auto Reboot] [Nand Erase All] previously and it didn't seem to work. I saw a recovery type post that suggested ticking [Phone EFS Clear] but seems to me that is a tick towards Brick - and the Recovery being offered was to a KK ROM anyway.
FeralFire said:
2nd link in my signature.
Follow it to step 6. Then flash whatever ROM you want. Make sure your phone is 32 gigs or more. Won't work on 16 gb version.
Click to expand...
Click to collapse
FeralFire said:
You need the international pit file in your phone. Flashing the CSC file will put that pit in your phone. It won't touch the bootloader or the system files.
Click to expand...
Click to collapse
I just looked at your post again - I realise I might have a wrong idea. Although the leaked ROM is KK, I was assuming flashing the CSC would upgrade my phone - is that the case or can I use your 6 steps just to change my PIT and then do the 4.3 RDLV process to have a root 4.3 phone?
Downloading it now - started with the torrent but that's running slow; I will let it run to completion to maybe help some others get it faster but I've got the Storage Cow one running as well. We'll see which one arrives first Either way I'll leave it seeding.
Journyman16 said:
I just looked at your post again - I realise I might have a wrong idea. Although the leaked ROM is KK, I was assuming flashing the CSC would upgrade my phone - is that the case or can I use your 6 steps just to change my PIT and then do the 4.3 RDLV process to have a root 4.3 phone?
Downloading it now - started with the torrent but that's running slow; I will let it run to completion to maybe help some others get it faster but I've got the Storage Cow one running as well. We'll see which one arrives first Either way I'll leave it seeding.
Click to expand...
Click to collapse
Yeah, you should be able to.
I tried flashing the MK2 ROM after flashing that CSC. It worked perfectly. But then I upgraded to kitkat. So I can't test JB stuff anymore.
FeralFire said:
Yeah, you should be able to.
I tried flashing the MK2 ROM after flashing that CSC. It worked perfectly. But then I upgraded to kitkat. So I can't test JB stuff anymore.
Click to expand...
Click to collapse
Well, it let me flash the vega BTU MK2 ROM but now there's a wifi problem. Still waiting for cygwin to download so I can RDLV on the XSA ROM. There seems to be some kind of conflict between BTU and Australian settings. Says to turn on wireless and actually finds my SSID's but then doesn't connect properly. le sigh...
Well it's been coming up to 24 hours with no phone but I seem to have found my way.
The problem seems to have been a mismatch between BL, CSC and PIT. In trying to get off the Hong Kong set up I wound up with a ZHU BL, BTU CSC and XSA CP and AP. It worked but I had no wifi. tried a few things to get it working and in trying to flash an XSA CSC (I think it was XSA) I got the Knox bit change. With no wifi I thought maybe the problem was the BUT-based CP needed changing. In trying to fix that, somehow I triggered Knox
I tried DL & Install of Omega 6 (it's a 4.3 - not ready to go KK yet) but although it completed nicely (so many ROM's got hidden or system errors in Odin) the phone didn't start. I tried installing Philz so I could run things from the extSDcard but an XSA wouldn't work nor would anything I had below MJ7. Last Phone Info view I had I still had a ZHU CP, even though AP and CSC were XSA-based.
Finally I got the MJ7 ROM from http://forum.xda-developers.com/sho...9005xxudmj7-pre-rooted-knox-free-odex-bl-free and it did the trick.
It's been a learning experience but I'd be happier if I knew for sure both what triggered the Knox bit (I was being very careful about it) and why some of the other ROM installs simply didn't work.
Resurrecting this one because I'm looking for info on flashing my 32G HK Note 3, but it came with KK pre-installed. So I'm not sure what differences I have to be aware of. Any tips?
For whoever still experiences issues with HK 32GB n9005 devices, After wasting half a day on that crap, i was able to flash N9005ZSUGOK2_N9005OZSGOK2_TGY from sammobile coupled with the PIT attached.
sm-n900
sm-900 and pit
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:
It started when I was trying Swapper 2 from the Play Store. Will, I guess I should read the comment, but I didn't. And yes, it corrupted my EFS and my phone was stuck at the Samsung boot logo. I have tried many method I can search over XDA, but non works. (I'm not sure about this one, which I only find while writing this guide.)
This is by far the easiest method for me, and it doesn't involve Linux, which was a pain since I haven't use Linux in years. I had to VM one for some of the XDA method, which didn't work at end of the day.
1. Flash the firmware with ODIN (original firmware) with original version that you had before. Not the custom ROM, but the original firmware version.
2. Recover with EFS with the EFS image attached in the thread. I used kTool as it faster and easier than any other tool. (Yes, I tried them all...)
3. Download Chimera Tool and buy their cheapest license (or whatever you want) which is €12.90.
That it. Yes you pay, but it the easiest, and most time saving. I spent a week Googling, trying all this various method over ADB, and no, non works. And for Samsung to repair, which they refuse and simply want to change a board and charge me US$ 200 for it, I rather pay €12.90 and do it myself. If you still have problem connection to the network after restoring IMEI, please read post 3.
FAQ
If you need the ODIN, you can find theme over here. Myself I've always used version 3.07. And as always under options you only need the 'Auto Reboot' and 'F. Reset Time' checked. Whether it a modem or stock ROM, click on 'PDA' choose the correct file and than click on start.
Q: Won't flash the EFS image I provide means I'm getting your IMEI?
A: I've wondered this as well. If it were so simple, there wouldn't be so many thread on recovering and so may people cry for help... (I'm included). As my last resort before I buy Chimera Tool's license, I flashed over my bro's S3 EFS, which I didn't want to, as I said it was a last resort. And as it turned out, I didn't get his IMEI. Instead I got his phones' Update S3 product code and serial number. And that was it. IMEI has changed from my previous 'NULL' to the infamous generic 004999010640000.
Q: Why do I still need to do EFS recovery if Chimera Tool can restore it.
A: I've experiment this myself, as I also absolutely did not want my bro's EFS. But unfortunately Chimera can only restore the IMEI and serial number, not rest of the missing files in the EFS folder. If I repartition the EFS folder and using Chimera to restore my IMEI, it would show the correct IMEI but still refuse to connect to the network. And it will have the annoy overly showing my CSC and other bunch of info on my homescreen, as if my EFS is still corrupt.
Q: Does Chimera need some special box?
A: No, a normal USB cable will work. That pretty much means standard ADB command would work, but unfortunately I can't find any info on that. I wish I did, so I don't need to get the Chimera Tool but there was no other way for me. I was also sceptical at first, as I read over many forums and they say it impossible with some sort of service box/tool. I gambled, and luckily it worked out.
Q: Where does the EFS image go for kTool?
A: Sorry, don't remember. Google it, or use the backup option first than overwrite the EFS.IMG file. That what I did.
Q: Now that I got my IMEI back, how do I back it up?
A. Use kTool again? Personally I use TWRP, as I think it the easiest. Since you can do it at a recovery level. No trying of ODIN the OS for corrupt OS before restoring the EFS. In any case, Chimera would still be function for the next couple of month and you can still mess around until than.
Q: Why the need of ODIN the original firmware?
A: I was on a custom TW ROM and Chimera didn't work. Maybe CM and other custom ROM will will work, you can give it a try. But this is how I did it and I know it works.
EFS / Baseband(modem)
It easy to criticize a member and simply tell him use the 'search function', but without realize sometimes the article will help you the most, simply just doesn't come up. Murphy's law. I was on stock 4.1.2 and after restore IMEI and EFS, the phone indicate it register on the network, but I couldn't make calls or connect to the net. This is a vary good article regarding EFS, and sadly it didn't come up easily on my search result. I came across it after I fixed the issue with tones of Googling and was searching for a different topic. But I understand people that desperate need to solve the problem quick (like I was) simply spent hour reading over hundreds of post under that article is just testing a persons sanity. So I'm going to summarised some of the stuff along with my experience. First thing you need to know:
- EFS v2 Basebands (modem) was introduced at Android 4.3 and can read EFS partition v2 and EFS v1
- EFS v1 Basebands (modem) CANNOT read EFS v2, ONLY EFS v1
If you phone is still under warranty and cannot connect to network, the best way is to stay on stock firmware and use TriangleAway to reset the flash counter and sent back to Samsung. With your IMEI number correctly showing, Samsung has absolutely no excuse on not fixing it. If you are no longer warranty, read on.
Q: My IMEI is now showing correctly but I still cannot make calls!
A: This is where the Ariza Patch kicks in. If you are on stock fimware 4.1.2, you need the Ariza Patch to fix the baseband. But after long reading over plenty post, it seems once this patch has been done, it irreversible. So beware. Before you try this patch, you may want to try update to the stock 4.3 firmware and see if it solves the problem before applying the patch.
Q: I'm on stock 4.3, now what?
A: If you still have problem connecting to the network, you need a patched modem (baseband) file. You can find them here. I think this is from the original author who did it. Instead of searching over the forums and files scatter all over the place, I'm pretty sure I dug the link out of XDA while reading through. Someone please tell me if it isn't and provide the the proper link. I'll fix it.
Q: I was on stock 4.1.2 and went to a custom 4.3 ROM, what fix shall I apply?
A: This was my scenario. And I was kind of desperate as well since I just fix my IMEI and was expect the phone to work. I wish I could come across the article on top earlier. I would've tried stock 4.3 first instead of applying the Ariza patch. Any ways, I was on stock 4.1.2 and it didn't work, so I tried a modified 4.3 TW ROM. I wish the OP would mention the EFS thing, which he didn't. I'm not blaming him or anything, but seriously not everyone keep in track of what happening with Android. The OP should mention about the EFS thing or simply post a link such as the topic above and just let people know instead of wasting hours on figuring out why it wasn't working. What I did was, after using the mod 4.3 TW ROM, the IMEI went crazy. So I thought it was corrupt again, so I ODIN back the stock 4.1.2 TW. Than I applied the Ariza patch, wolla, I could call and browse again. So I decide to give the mod 4.3 TW ROM another try. To my surprise, the IMEI still went crazy. So after more Googling only I found out because I wasn't on stock 4.3, my baseband would still 4.1.x. I tried the modem (baseband) patch which for some reason still did not work for me. So I decide to keep the stock 4.1.2 baseband and simply use a custom kernel that could read EFS v1 and v2 - Boeffla Kernel. Remember to download the 4.3 kernel not the 4.1.x! That it, you should now have a working phone.
I just use SA manager .It will backup EFS & MODEM .store it in Ext SD .If EFS corrrrupted just install SA mgr back & restore .
Most important is backup and its very simple process
u need HKCtool to backup efs both img and tar files first of all.
if this is not possible u need a stock rom and odin .after installing stock rom the efs will be repaired.
nainaabd said:
I just use SA manager .It will backup EFS & MODEM .store it in Ext SD .If EFS corrrrupted just install SA mgr back & restore .
Most important is backup and its very simple process
Click to expand...
Click to collapse
Didn't try SA manager as I was in a rush and looking specifically for Samsung phones only. But it definately somehting I want to try if I get a Sony phone. Though I still prefer at a recover level. It just so simple.
keenimo said:
u need HKCtool to backup efs both img and tar files first of all.
if this is not possible u need a stock rom and odin .after installing stock rom the efs will be repaired.
Click to expand...
Click to collapse
TAR file is just a compressed version of IMG file.
im in nairobi kenya, unfortunately i can not buy the chimera tool because we dont have the necessary paying methods. anyone who can lend me theirs please? my S3 has the generic imei, repair would cost 15k here, which is too much. anybody that can help will be highly appreciated.
TNCS said:
It started when I was trying Swapper 2 from the Play Store. Will, I guess I should read the comment, but I didn't. And yes, it corrupted my EFS and my phone was stuck at the Samsung boot logo. I have tried many method I can search over XDA, but non works. (I'm not sure about this one, which I only find while writing this guide.)
This is by far the easiest method for me, and it doesn't involve Linux, which was a pain since I haven't use Linux in years. I had to VM one for some of the XDA method, which didn't work at end of the day.
1. Flash the firmware with ODIN (original firmware) with original version that you had before. Not the custom ROM, but the original firmware version.
2. Recover with EFS with the EFS image attached in the thread. I used kTool as it faster and easier than any other tool. (Yes, I tried them all...)
3. Download Chimera Tool and buy their cheapest license (or whatever you want) which is €12.90.
That it. Yes you pay, but it the easiest, and most time saving. I spent a week Googling, trying all this various method over ADB, and no, non works. And for Samsung to repair, which they refuse and simply want to change a board and charge me US$ 200 for it, I rather pay €12.90 and do it myself. If you still have problem connection to the network after restoring IMEI, please read post 3.
Click to expand...
Click to collapse
you can also downgrade to 4.0.4 and do flash i9300 efs.tar via odin 3.07 but first backup your EFS with helroz's app from here https://market.android.com/details?id=com.boiteoutilssgshelroz&feature=search_result or use any other efs backup maker
But YOU NEVER NEED TO RESTORE EFS after a flash or whenever, just in case you have an issue with it.
if u have 0049xxxx or 00xxxx imei just flash I9300XXUNA7 or any latest android 4.3 and that's it you have your unknown baseband and null imei fixed aka efs corrupt issue.
Warning!!!!
i am not responsible if you get any damage to your device as per my experience i have fixed many i9300's efs and didn't get any problem .
Good luck!
(CHANGE THE ATTACHED FILE'S EXTENSION TO .md5)
Xubair91 said:
you can also downgrade to 4.0.4 and do flash i9300 efs.tar via odin 3.07 but first backup your EFS with helroz's app from here https://market.android.com/details?id=com.boiteoutilssgshelroz&feature=search_result or use any other efs backup maker
But YOU NEVER NEED TO RESTORE EFS after a flash or whenever, just in case you have an issue with it.
if u have 0049xxxx or 00xxxx imei just flash I9300XXUNA7 or any latest android 4.3 and that's it you have your unknown baseband and null imei fixed aka efs corrupt issue.
Warning!!!!
i am not responsible if you get any damage to your device as per my experience i have fixed many i9300's efs and didn't get any problem .
Good luck!
(CHANGE THE ATTACHED FILE'S EXTENSION TO .md5)
Click to expand...
Click to collapse
From what I understand, that still under the condition of prior having an EFS back-up first, right? My guide is for people who doesn't. Like in my situation, where the app screwed up the EFS partition and I had no back-ups.
If you really want in details - Swapper 2 moved the EFS partation on to my ext SD card and format the EFS partition. I was in a flat panic with the soft-brick froze at the Samsung boot logo, assume the SWAP was on the ext SD and screwed it up than format the ext SD. Well, boom, without expectation the app would do something like that and had no prior experience with EFS - no back-ups of EFS at all. And no, full nandroid back-up from CWM does not contain EFS, I've tried that. This isn't some normal scenario of incompatibility between kernel/ROM and EFS/Modem. This is recovery guild for corruption of EFS with NO back-ups.
trying ....
mezo_mmm said:
trying ....
Click to expand...
Click to collapse
And how did it go? The suspense it killing me .