Hi all,
i upgraded to the new BL and KK.
After that i always get secSetupWizard has stopped working.
Regardless of using X-Note Rom or the stock N9005XXUENB4_N9005DBTENB1_DBT or N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_OXX. (always a complete wipe of all partitions (system, data, cache) before flashing the firmwares with odin 3.0.9)
When booting the up the phone and when hitting the finish button of the configuration assistant the secSetupWizard is forceclosing and all begins again (endless loop). The only way to use my phone again is to delete the apk in the system partition.
After that everything is working fine. No other apps are forceclosing etc...
Everything is fine after deleting the SecSetupWizard2013.apk in system\app
Does s.o else have the same problem? Can s.o tell me how to fix it?
Since you've came from a custom ROM you may have messed up your partitions, Reflash CWM or TWRP and wipe /system then reflash stock you should be OK. - Failing that, find a pit file and repartition when you flash Stock
I did always a full wipe before flashing with Odin.
Flashing original fw work (no need for a pit file and repartitioning with Odin)
Gesendet von meinem SM-N9005 mit Tapatalk
nobody any other idea?
now i did also repartitioning but nu success. regardless which rom i flash (stock, custom rom etc..) complete full wipe (internal sdcard, cache, dalivk cache, system, data, data/media), then a odin flash with stock rom --> same result -> loop at setup wizard. the only way to pass this wizard is to delete the app in twrp from the system partition.
Hundsbuah said:
Hi all,
The only way to use my phone again is to delete the apk in the system partition.
After that everything is working fine. No other apps are forceclosing etc...[/B]
Click to expand...
Click to collapse
Hi,
I have the same problem as you, can you tell me how you removed the apk?
i removed the apk in recovery with adb shell
Hi all,
i had to use "Clear Phone EFS" in Odin to get my 9005 back working - i thought: "Hey no problem i have multiple EFS backups..."
But now even if i restore my backup in TWRP or via the Windows Batch Backup Script, my Baseband and EMEI and EMEISV is still "unkown"
Can s.o tell me the steps i need to do, to rewrite my Baseband and EMEI with my available EFS backups?
What i have:
- EFS Professional
- 2 different EFS backups in TWRP
- 2 windows back tool EFS backups (i mean this script: http://forum.xda-developers.com/showthread.php?t=2447342)
- Working WIFI
- Working BT
- Stock N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_OXX file(s)
- Stock N9005XXUENB4_N9005DBTENB1_N9005XXUENB1_HOME file(s)
- Stock N9005XXUENB7_N9005DBTENB2_DBT file(s)
- Odin + 9005 PIT Files
- Correct SerialNumber in DeviceInformation->Status
I'm on the new Bootloader and KitKat OS
Thank you very much for all your help!
Best regards,
Chris
PROBLEM SOLVED!
Look here http://forum.xda-developers.com/showpost.php?p=51152510&postcount=4
Hundsbuah said:
Hi all,
i had to use "Clear Phone EFS" in Odin to get my 9005 back working - i thought: "Hey no problem i have multiple EFS backups..."
But now even if i restore my backup in TWRP or via the Windows Batch Backup Script, my Baseband and EMEI and EMEISV is still "unkown"
Can s.o tell me the steps i need to do, to rewrite my Baseband and EMEI with my available EFS backups?
...
Click to expand...
Click to collapse
On the N9005 the IMEI is no longer on the EFS partition (mmcblk0p11) but instead in some other partition - I think mainly in MS1 (mmcblk0p12) with something else (backup?) in MS2 (mmcblk0p13). There might be something else in mmcblk0p17, mmcblk0p18 and mmcblk0p19.
If you do not have any backup (including a larger "debrick backup" - search for that post) you can try to see which one of the partitions I listed above was supposed to be the backup of what; and if that fails there is a more complex procedure described somewhere in a thread on XDA - involving manually hex-editing your SN and IMEI from under the battery or the original box of the phone.
xclub_101 said:
On the N9005 the IMEI is no longer on the EFS partition (mmcblk0p11) but instead in some other partition - I think mainly in MS1 (mmcblk0p12) with something else (backup?) in MS2 (mmcblk0p13). There might be something else in mmcblk0p17, mmcblk0p18 and mmcblk0p19.
If you do not have any backup (including a larger "debrick backup" - search for that post) you can try to see which one of the partitions I listed above was supposed to be the backup of what; and if that fails there is a more complex procedure described somewhere in a thread on XDA - involving manually hex-editing your SN and IMEI from under the battery or the original box of the phone.
Click to expand...
Click to collapse
ok thank you - bad news
Ill try this guide: (Can this guide be used with KK 4.4.2 ?)
http://forum.xda-developers.com/showthread.php?t=2567133
What about the "unkown baseband"? How can this be fixed?
Ok a managed it to get all back working, incl. baseband, emei etc (but you need a twrp efs backup with all 3 efs partitions --> simply a twrp backup)
If some others have the same problem, here you go:
I think some other partition was corrupted and thats why the twrp efs restore didnt worked (just a twrp efs restore).
I did following: (you need a efs backup!!!)
Folow exactly this guide http://forum.xda-developers.com/showthread.php?t=2567133: and do all partitions, DONT! skip the efs partitions (we have a twrp backup)
Now some further steps are needed:
IMPORTANT:
1) When you put in back your battery, boot back into twrp and restore your TWRP EFS Backup!! Dont boot in the OS!!!!
2) Then reflash with odin a stock based rom without any other checkboxes (NO EFS PHONE CLEAR, NO NAND ERASE ALL!!!!), just a normal odin stock rom flash
3) Let the phone reboot into OS and YES: Baseband working again, EMEI working again
Bro whats a twrp efs backup?
Team win recovery Project. Its a revovery and a twrp efs Backup is a Backup from the 3 efs partitions in twrp
Gesendet von meinem SM-N9005 mit Tapatalk
Hundsbuah said:
Ok a managed it to get all back working, incl. baseband, emei etc (but you need a twrp efs backup with all 3 efs partitions --> simply a twrp backup)
If some others have the same problem, here you go:
I think some other partition was corrupted and thats why the twrp efs restore didnt worked (just a twrp efs restore).
I did following: (you need a efs backup!!!)
Folow exactly this guide http://forum.xda-developers.com/showthread.php?t=2567133: and do all partitions, DONT! skip the efs partitions (we have a twrp backup)
Now some further steps are needed:
IMPORTANT:
1) When you put in back your battery, boot back into twrp and restore your TWRP EFS Backup!! Dont boot in the OS!!!!
2) Then reflash with odin a stock based rom without any other checkboxes (NO EFS PHONE CLEAR, NO NAND ERASE ALL!!!!), just a normal odin stock rom flash
3) Let the phone reboot into OS and YES: Baseband working again, EMEI working again
Click to expand...
Click to collapse
Will a TWRP boot ,data and system backup work as well for restoring baseband? I have the same problem -> http://forum.xda-developers.com/showthread.php?t=2796948&page=6
No u need an efs backup
Gesendet von meinem SM-N9005 mit Tapatalk
Hundsbuah said:
No u need an efs backup
Gesendet von meinem SM-N9005 mit Tapatalk
Click to expand...
Click to collapse
So have I run out of options? Please have a look at my thread. The last few posts especially . Any help would be appreciated.
Please help sm-n900
Hundsbuah said:
Ok a managed it to get all back working, incl. baseband, emei etc (but you need a twrp efs backup with all 3 efs partitions --> simply a twrp backup)
If some others have the same problem, here you go:
I think some other partition was corrupted and thats why the twrp efs restore didnt worked (just a twrp efs restore).
I did following: (you need a efs backup!!!)
Folow exactly this guide http://forum.xda-developers.com/showthread.php?t=2567133: and do all partitions, DONT! skip the efs partitions (we have a twrp backup)
Now some further steps are needed:
IMPORTANT:
1) When you put in back your battery, boot back into twrp and restore your TWRP EFS Backup!! Dont boot in the OS!!!!
2) Then reflash with odin a stock based rom without any other checkboxes (NO EFS PHONE CLEAR, NO NAND ERASE ALL!!!!), just a normal odin stock rom flash
3) Let the phone reboot into OS and YES: Baseband working again, EMEI working again
Click to expand...
Click to collapse
just went to the above mentioned link but none of the multiupload files link work.
could you upload the NOTE 3 - Fix soft bricked.rar and the Samsung drivers.
I want to extract the NOTE 3 - Fix soft bricked.rar and modify it for use in sm-n900
Sorry I don't have these files anymore try to get them from the thread owner
Gesendet von meinem SM-N9005 mit Tapatalk
Hundsbuah said:
Ok a managed it to get all back working, incl. baseband, emei etc (but you need a twrp efs backup with all 3 efs partitions --> simply a twrp backup)
If some others have the same problem, here you go:
I think some other partition was corrupted and thats why the twrp efs restore didnt worked (just a twrp efs restore).
I did following: (you need a efs backup!!!)
Folow exactly this guide http://forum.xda-developers.com/showthread.php?t=2567133: and do all partitions, DONT! skip the efs partitions (we have a twrp backup)
Now some further steps are needed:
IMPORTANT:
1) When you put in back your battery, boot back into twrp and restore your TWRP EFS Backup!! Dont boot in the OS!!!!
2) Then reflash with odin a stock based rom without any other checkboxes (NO EFS PHONE CLEAR, NO NAND ERASE ALL!!!!), just a normal odin stock rom flash
3) Let the phone reboot into OS and YES: Baseband working again, EMEI working again
Click to expand...
Click to collapse
Hi, I have the same problem as you did, my baseband is showing unknown and the imei is showing null. This happened when I was installing a different modem via ODIN. I do have a EFS backup, however, it was done with philz recovery instead of TWRP and has 4 files ('efs.ext4.tar'; 'efs.ext4.tar.a'; 'nandroid.md5'; and 'recovery.log'). Are these the same that you would get with a TWRP?
I also have another efs backup that I did which is one file only, 'efs_20140531_122400.img'. Would I be able to use this for anything?
The phone is an N9005 on Kitkat.
Thanks for any help in advance and please let me know if you need any other info.
Cheers
--------------------------
Just to let you know,
I had tried flashing flash latest full UK NF4 system before and it didn't work. However, desperate as I was, I went again and gave it another shot and incredibly enough, it worked!!!! Phone is back together again!!!! Yeeahh!!! There goes an incredible load off my shoulders. I guess I did something in between that actually helped, we may never know.
Cheerio
Hundsbuah said:
Hi all,
i had to use "Clear Phone EFS" in Odin to get my 9005 back working - i thought: "Hey no problem i have multiple EFS backups..."
But now even if i restore my backup in TWRP or via the Windows Batch Backup Script, my Baseband and EMEI and EMEISV is still "unkown"
Can s.o tell me the steps i need to do, to rewrite my Baseband and EMEI with my available EFS backups?
What i have:
- EFS Professional
- 2 different EFS backups in TWRP
- 2 windows back tool EFS backups (i mean this script: http://forum.xda-developers.com/showthread.php?t=2447342)
- Working WIFI
- Working BT
- Stock N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_OXX file(s)
- Stock N9005XXUENB4_N9005DBTENB1_N9005XXUENB1_HOME file(s)
- Stock N9005XXUENB7_N9005DBTENB2_DBT file(s)
- Odin + 9005 PIT Files
- Correct SerialNumber in DeviceInformation->Status
I'm on the new Bootloader and KitKat OS
Thank you very much for all your help!
Best regards,
Chris
PROBLEM SOLVED!
Look here http://forum.xda-developers.com/showpost.php?p=51152510&postcount=4
Click to expand...
Click to collapse
Hi Hundsbuah,
I upgraded my Note 3 9005 Hong Kong Version 32 GB from Jelly Bean to KitKat without taking backup of EFS and now I have IMEI Null and Baseband unknown. I found backup of other user's note3 EFS at "http://forum.xda-developers.com/showthread.php?t=2447342". So, if I tried EFS restore from above link will it resolve my IMEI null and baseband unknown issue?
Regards,
Asif
hey guys, how do you restore with TWRP?
Every time i restore i get so many problems, sometime it doesn't boot, and most of the time(when it boots) media stopped or UI stopped.. etc..etc
I am using TWRP 2.7.0.0
I want to restore my officia kitkat without any problem
btw I didn't backup data just boot and system and i wiped all before restoring....
*Should i flash modem or something????
I am using optimusRS pro2 v4.3 my mobile: D802
Please help.............. Thanks in advance for the help
Hi Everybody,
I'm really disappointed. For the second Times, I've corrupted my EFS partition. IMEI is empty, as the baseband...
The first time that I had this problem, I could restore the EFS using the fabulous fix from Fireasusman : http://forum.xda-developers.com/showthread.php?p=47014662#post47014662
But this time, It didn't work.... I'm really really sad.
Before trying to restore the stock firmware ( My problem was coming when i tried to restore stock firmware before to sell it) i made a Nandroid backup with TWRP recovery. I've an EFS/MODEM backup in this Nandroid.
When I reboot into recovery, and go to restore, I can select EFS, and it seems restore It. It wrote : Restoring 2 partitions/Restoring EFS/restoring EFS2/restoring EFS3/EFS Done/Restoring Modem/ Modem Done...
But after reboot the problem is Still There...
I'm really Angry, I lost 400$ and I don't understand why my Nandroid Restore of EFS failed...
I also try to flash modem with ODIN but it still Failed.
Note: I was an temasek CM12 (android lollipop).
Thank you very much for every help.
1. Flash STOCK ROM and take a look how it works. Sometimes only flashing it recovers the EFS folder.
2. Next time use this APP for backup/restore your EFS.
Really thanks for your help.
But i've allready try to restore stock ROM. At least twice. But efs is still corrupt. And the phone never arrive to boot...
About how many time I can consider that flash stock ROM will not repair my EFS partition ?
I've allready done twice...
Ok... I solved my problem.
As I explain in first post, I'had a EFS backup with a Nandroid Backup. But when I restore with TWRP, the problem was still there. No pin, No baseband etc...
I only delete the EFS folder using root explorer. I reboot, and it was OK. EFS folder was rebuilt automatically.... No more complicated than that...
Good finding
pystolero said:
Ok... I solved my problem.
As I explain in first post, I'had a EFS backup with a Nandroid Backup. But when I restore with TWRP, the problem was still there. No pin, No baseband etc...
I only delete the EFS folder using root explorer. I reboot, and it was OK. EFS folder was rebuilt automatically.... No more complicated than that...
Click to expand...
Click to collapse
Because the IMEI is not stored in the EFS folder.
i recently backup my grand 2 stock rom via cwm. and flashed twrp recovery to flash aditya v3 rom. but now i aagin flash same cwm version and restoring my backed up rom. but when system respore completed, data restoring start. its show error while restoring data. that's why i flash cm12.1 by mukulsani and backup this rom via twrp to check. but in twrp same problem again. when system restore completed, data restoring its say error.
what is the problem? help me. plz