Related
I9000 unlock instructions
1. Power on the phone and go to Applications->Settings->About Phone->USB
settings
2. Select Mass Storage
3. Connect the phone to USB cable
4. Swipe down the top notification bar then tap “USB Connected” then select
MOUNT
5. Copy update.zip file to phone mass storage root
6. Power off the phone
7. Press Volume Up+Home+Power on key to start the phone into recovery
mode
8. Go to “apply sdcard:update.zip” using volume keys then select it using
home key
9. Power on the phone then go to Andoid Market and install Terminal
Emulator
10. Run Terminal Emulator
11. Type cat /efs/nv_data.bin >> /sdcard/nv_data.bin into terminal then type
Enter
12. Connect the phone to PC in USB Storage Mode then copy nv_data.bin file
to your pc
13. Open nv_data.bin file with any hex editor (ex. Hex workshop) then go to
address 00181460
14. There are the codes
15. Power on the phone with any unaccepted sim card inside then type in the
first code to unlock the phone
I9000 drivers
I9000 drivers
This solution is is not working for me. The problem is that the Update.zip says:
E: Signature verfication failed
Installation aborted
Any advice? How to install that update.zip package?
cellularhut said:
I9000 unlock instructions
1. Power on the phone and go to Applications->Settings->About Phone->USB
settings
2. Select Mass Storage
3. Connect the phone to USB cable
4. Swipe down the top notification bar then tap “USB Connected” then select
MOUNT
5. Copy update.zip file to phone mass storage root
6. Power off the phone
7. Press Volume Up+Home+Power on key to start the phone into recovery
mode
8. Go to “apply sdcard:update.zip” using volume keys then select it using
home key
9. Power on the phone then go to Andoid Market and install Terminal
Emulator
10. Run Terminal Emulator
11. Type cat /efs/nv_data.bin >> /sdcard/nv_data.bin into terminal then type
Enter
12. Connect the phone to PC in USB Storage Mode then copy nv_data.bin file
to your pc
13. Open nv_data.bin file with any hex editor (ex. Hex workshop) then go to
address 00181460
14. There are the codes
15. Power on the phone with any unaccepted sim card inside then type in the
first code to unlock the phone
Click to expand...
Click to collapse
Fantastic find if it works, my phone is unlocked so I can't test it but thanks a lot for sharing!!! Priceless
N.B. The first 8 steps are the process for rooting your phone, since you need to be root to do step 11. If you already have a rooted phone, start from step 10.
tyxerakias said:
fantastic find if it works, my phone is unlocked so i can't test it but thanks a lot for sharing!!! Priceless
n.b. The first 8 steps are the process for rooting your phone, since you need to be root to do step 11. If you already have a rooted phone, start from step 10.
Click to expand...
Click to collapse
1000000000000000% working tested before post here !!!!!
I am following 100% tutorial but I am unable to unlock my I9000. Look at the screenshot for the error that I encounter.
I have put the update.zip in root of phone memory, root of MicroSD etc but no chance. Do I need to root the phone or what's the problem?
Thanks
erreterr said:
I am following 100% tutorial but I am unable to unlock my I9000. Look at the screenshot for the error that I encounter.
I have put the update.zip in root of phone memory, root of MicroSD etc but no chance. Do I need to root the phone or what's the problem?
Thanks
Click to expand...
Click to collapse
Please read my post above. By doing this, you are rooting your phone.
It seems that the update.zip has not been properly signed, I see that it contains a new busybox, maybe the OP tried to optimise it and failed?
Use the original update.zip from the FAQ (http://www.multiupload.com/JHIFK9K80P) to root your phone, then continue from step 9.
The same happens with the file that I downloaded from your posted link!!!
Whats going wrong here?
Tyxerakias said:
Please read my post above. By doing this, you are rooting your phone.
It seems that the update.zip has not been properly signed, I see that it contains a new busybox, maybe the OP tried to optimise it and failed?
Use the original update.zip from the FAQ (http://www.multiupload.com/JHIFK9K80P) to root your phone, then continue from step 9.
Click to expand...
Click to collapse
No idea. Have you rooted your phone already? Have you installed any mods or firmwares?
No need to root
You dont need to root your phone to get to Step 11. The Terminal Emulator I installed from the Market let me do Step 11 directly.
All I then just did was email the nv_data.bin file to my inbox and later just open it in Textpad.
So, it was a bad tutorial. I tried to go step by step but now I begin from step 11 and everything is OK. My first I9000 unlocked like a charm
Thanks
knkartha said:
You dont need to root your phone to get to Step 11. The Terminal Emulator I installed from the Market let me do Step 11 directly.
All I then just did was email the nv_data.bin file to my inbox and later just open it in Textpad.
Click to expand...
Click to collapse
Huh. Interesting. I would have thought /efs is a protected folder.
I have a Bell one, i asked their staff when i bought my phone if i still on WARRANTY when i unlock the phone by Bell, they said yes.
Anybody know if i will lose my phone WARRANTY after i unlock the phone? Or can i lock it back if my phone have any problem in the future?
Thanks
could somebody point out which value in the address 00181460 says the unlock code?
erreterr said:
The same happens with the file that I downloaded from your posted link!!!
Whats going wrong here?
Click to expand...
Click to collapse
you should put the update.zip file on your internal sd card directory.
i encountered the same error when i put the update.zip file in the external sd card
erreterr said:
So, it was a bad tutorial. I tried to go step by step but now I begin from step 11 and everything is OK. My first I9000 unlocked like a charm
Thanks
Click to expand...
Click to collapse
which of the values in the said address gives the unlock code?
Hi,
I have a NSPRO box and read the unlock code, but as I insert it, it doesn't unlock the phone.
As this didn't work, I tried your method, and the code that showes up is the same as read by NSPRO box, and... it still doesn't work.
Attached is the printscreen of the HEX area where the code is. I've noticed it says "18146D" and not "181460" as your indicated. Could this be the reason why the code doesn't work?
Please help...
Samsung Vibrant SGH-T959 Recovery Mode
I've tried all sorts of button combinations to get the Samsung Vibrant T959 into recovery mode. I think since this device is a T-Mobile phone, the firmware has been modified for VolUp+VolDn+Pwr recovery mode.
As of now, the only way I know how to get the phone into recovery mode is by using the Android SDK and sending off a command: adb reboot recovery
I've been putting together an Android SDK & Rooting tutorial as well as other Samsung Vibrant T959 findings here: jordanpeterson.me/content/t-mobile-samsung-vibrant-sgh-t959
Sorry.. the external references aren't working.. Good spam rules on new users.
Thanks
Jordan
It worked great, althoug the address on my I9000 was 00181462. My suggestion is try to find closest address to the given by the tuturial....
Thanks for everything
Don't need to root the device. Download terminal emulater from Market. Went straight to step 10. Works like a charm. Thanks for the instructions.
Sent from my GT-I9000M using XDA App
My phone settings
firmware version 2.1-update 1
baseband 63.18.55.06PU_6.35.15.14
KERNEL VERSION 2.6.29-36D5CB8D
[email protected] #1
build number 3.35.61.2 cl196735 release-keys
software number 3.35.61.2 browser version webkit 3.1
I have been wanting to install a custom rom on my phone for several months now however no matter what method i try i am unsuccesful closest i have come is using rom manager which allows me to reboot into recovery but once the handset has rebooted home screen and power button just gets me to the triangle on screen and i have to remove battery. all flash recorder methods fail at either back up recovery
or writing flash.
I believe my phone is rooted as i can grant su to rom manager ect and androot tells me i am rooted it is like something resets recovery every time the handset boots into os.
i really have tried every method i have found but dare not try and install anything for fear of recovery not being available to me and i am now wondering if the 2.1 update has blocked something.
please help willing to make donation to any devs that can help me through this as well as the countless others having the same problem
there was one thread here .. try to search it i forget link it can explain you how to root official 2.1 otherwise run RUU & Do downgrade
according to all the programmes i run to check status of root (latest one is under the hood) it lists
Device: htc_hero hero
Root Status: Device routed
ro. build fingerprint: orange_uk/htc_hero/hero/hero:2.1-update1/ERE27/196735:user/release-keys
every programme that requires root access works for me tho i do have to grant it every time for programmes , the clockwork recovery has to be reflashed if phone has been restarted to enable me to access the recovery, and when i do this su pops up telling me it has been granted.
1 method i tried but never got past step backup recovery was this but i get message backup failed could not run command
"HTC Hero Custom Recovery
Step 1:
It's advisable to format the SD Card before do this process. You're going to lose all the information in the SD Card, do a manual backup to your computer of whatever you want, to do it:
Settings -> SD Card & phone storage -> Unmount SD card -> Format SD card
Step 2:
Download the flashrec from http://code.google.com/p/flashrec/
Download the recovery image provided by Paul from http://www.romraid.com/paul/hero/1.2-hero-recovery.zip
Extract the 1.2-hero-recovery.zip to your PC.
Step 3:
Now copy flashrec and recovery-RA-hero-v1.5.2.img (wich is inside the .zip file) directly to your SD card
Step 4:
Use an app installer from Google Market to install flashrec, i used ASTRO, but can be any other.
Step 5:
Once installed, open the program, click the button "Backup Recovery Image" and wait to finish, shouldn't take much time, this will do a backup of your actual recovery and put it in your SDCard with the name recovery-backup.img.
brisuth said:
My phone settings
firmware version 2.1-update 1
baseband 63.18.55.06PU_6.35.15.14
KERNEL VERSION 2.6.29-36D5CB8D
[email protected] #1
build number 3.35.61.2 cl196735 release-keys
software number 3.35.61.2 browser version webkit 3.1
I have been wanting to install a custom rom on my phone for several months now however no matter what method i try i am unsuccesful closest i have come is using rom manager which allows me to reboot into recovery but once the handset has rebooted home screen and power button just gets me to the triangle on screen and i have to remove battery. all flash recorder methods fail at either back up recovery
or writing flash.
I believe my phone is rooted as i can grant su to rom manager ect and androot tells me i am rooted it is like something resets recovery every time the handset boots into os.
i really have tried every method i have found but dare not try and install anything for fear of recovery not being available to me and i am now wondering if the 2.1 update has blocked something.
please help willing to make donation to any devs that can help me through this as well as the countless others having the same problem
Click to expand...
Click to collapse
You're absolutely right, the 2.1 update for the Hero installs a recovery rom reset, so whenever you boot up your phone normally, it reflashes it (or possibly checks that it's not the original and then flashes).
I don't quite remember where this was done anymore, it might have been a script in /system/bin that gets called from init(rc), called something like flash_recovery.sh. Perhaps someone who isn't running a custom rom could help out and pinpoint it for future reference (I am so not going back from cyanogen 6.0
Edit: I grabbed unyaffs and checked out my old nandroids, it's /system/etc/install-recovery.sh, comment out the line in it (add a # at the beginning of the line) and it will not clobber your custom recovery
i have located file but now i feel really stupid as have not got a clue what to edit it with i am assuming it would be some type of txt editor and if u could specify the line i need to edit out or is it the name of the file i am changing,
really am gratefull for you pointing this out i had guessed what was happening just could find nothing to confirm it.
brisuth said:
i have located file but now i feel really stupid as have not got a clue what to edit it with i am assuming it would be some type of txt editor and if u could specify the line i need to edit out or is it the name of the file i am changing,
really am gratefull for you pointing this out i had guessed what was happening just could find nothing to confirm it.
Click to expand...
Click to collapse
It might need to be a text editor that knows not to break unix line endings, but you can copy the file (cat file > /path/to/destination/file) to your sdcard or use adb to pull the file... fairly straightforward I thought.
A big thankyou to duck0 for identifying the problem and botoo for getting me to a happy conclusion with the correct commands
SOLUTION IS HERE USING Console mode from windows using ADB USB DEBUGGING HAS TO BE ENABLED WITH HERO CONNECTED TO PC THEN TYPE THE FOLLOWING
THEN ENTER AFTER EACH COMMAND
anyone needing help setting up adb see this link http://forum.xda-developers.com/showthread.php?t=757233
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
rm /system/etc/install-recovery.sh
Thats it all done next step
INSTALL ROM MANAGER FROM MARKET IT IS FREE
open it and sellect flash alternate recovery image from the bottom, you can use the clockwork recovery but it is not compattable with all roms.
once done turn phone off, boot into recovery home + power choose to exit recovery with reboot shut down once again and if you can enter recovery then everything is sweet.
Hello, im a new to this kind of things. Yesterday I flashed a rom and when I booted the rom up a yellow window poped up, check the attactment how the window looks like. I have tried many solutions on the internet but none of them has worked. My efs folder is also empty, and I didn't make a backup of it i just made a full backup in cwm. I'm hoping that somebody can help me because my S4 is the only phone that I have. Sorry for my bad english.
QuaTiMxi said:
Hello, im a new to this kind of things. Yesterday I flashed a rom and when I booted the rom up a yellow window poped up, check the attactment how the window looks like. I have tried many solutions on the internet but none of them has worked. My efs folder is also empty, and I didn't make a backup of it i just made a full backup in cwm. I'm hoping that somebody can help me because my S4 is the only phone that I have. Sorry for my bad english.
Click to expand...
Click to collapse
Efs folder is not empty.
Use root explorer or file explorer with mount option and do the following:
open file "factorymode" in efs/factoryApp directory, it probabely says "off", change to "on" (yes "on" is the correct setting to turn it off), then save
reboot
sent from my Galaxy
samersh72 said:
Efs folder is not empty.
Use root explorer or file explorer with mount option and do the following:
open file "factorymode" in efs/factoryApp directory, it probabely says "off", change to "on" (yes "on" is the correct setting to turn it off), then save
reboot
sent from my Galaxy
Click to expand...
Click to collapse
I have tried both Root expolorer and root browser none of them dosen't find the files in efs, I have attached some thumbnails of the apps
QuaTiMxi said:
I have tried both Root expolorer and root browser none of them dosen't find the files in efs, I have attached some thumbnails of the apps
Click to expand...
Click to collapse
Can you make a call?.
Any way use this file mansger (go to setting and enable "root explorer" and "mount system folders" ) https://play.google.com/store/apps/...t#?t=W251bGwsMSwyLDEsImNvbS5yaG1zb2Z0LmZtIl0.
sent from my Galaxy
I forgot to say that the lockscreen isn't working, when I press the sleep button the phone turns black but when i press it again it won't ask for my lockscreen code. I can't make calls because the mobile network isn't functional. No luck in that file manager either
QuaTiMxi said:
I forgot to say that the lockscreen isn't working, when I press the sleep button the phone turns black but when i press it again it won't ask for my lockscreen code. I can't make calls because the mobile network isn't functional. No luck in that file manager either
Click to expand...
Click to collapse
and i think that power menu is gone also...
go to efs/imei folder, and make a file called "keystr" (without " ") (it is probably missing)
open "keystr" file and write "on" (without " " ),save. set permission of the file (all ticked).
But unfortunately, i think that your efs partition is corrupted. You must make a backup for this partition after rooting.
Try to flash stock firmware, some reported that it worked
sent from my Galaxy
samersh72 said:
and i think that power menu is gone also...
go to efs/imei folder, and make a file called "keystr" (without " ") (it is probably missing)
open "keystr" file and write "on" (without " " ),save. set permission of the file (all ticked).
But unfortunately, i think that your efs partition is corrupted. You must make a backup for this partition after rooting.
Try to flash stock firmware, some reported that it worked
sent from my Galaxy
Click to expand...
Click to collapse
I managed to get the yellow text away by uninstalling the factorytest apk.
I have tried to install stock firmware trough odin no luck there to. How can I make a backup for this partition?
Now my mobile network works to, I managed to fix it by turning my simcard lock of. The only problem that is left now is the lockscreen and powermenu. I can use the keystr solution and it works but every time I reboot my phone the /efs folder gets empty. Please help me im so confused
Sent from my GT-I9505 using xda app-developers app
Guys i've got the same problem but i dont have a backup :'(
I wanted a fully clean system so i've wiped everythimg and flashed the me8 firmware as pda in odin.
Everything works but i've got no lockscreen and no power menue.
I would be so happy if someone could help me to solve my problem.
I'm using a 9505.
benni2903 said:
Guys i've got the same problem but i dont have a backup :'(
I wanted a fully clean system so i've wiped everythimg and flashed the me8 firmware as pda in odin.
Everything works but i've got no lockscreen and no power menue.
I would be so happy if someone could help me to solve my problem.
I'm using a 9505.
Click to expand...
Click to collapse
Root your phone and see post number 6 in this thread
sent from my Galaxy
I've tried that but it doesnt work for me. Also i've tried to flash a few firmwares but the proplem still exists.
benni2903 said:
I've tried that but it doesnt work for me. Also i've tried to flash a few firmwares but the proplem still exists.
Click to expand...
Click to collapse
Have you tried my solutions? The only problem that is left for me is the lockscreen and powermenu But we need a solution for this problem a permanent solution!
samersh72 said:
Root your phone and see post number 6 in this thread
sent from my Galaxy
Click to expand...
Click to collapse
I can't see the link to the thread
benni2903 said:
I've tried that but it doesnt work for me. Also i've tried to flash a few firmwares but the proplem still exists.
Click to expand...
Click to collapse
It must work, no other solution, be sure that you set "keystr" file permission when you finish
sent from my Galaxy
samersh72 said:
It must work, no other solution, be sure that you set "keystr" file permission when you finish
sent from my Galaxy
Click to expand...
Click to collapse
I got it to work! I followed all the steps and when i was done I edited the keystr file in hex editor so the values was 4f and 4e and all others 00. This solution worked but its not permanent, each time I reboot the phone I have to do the same thing again, is there any permanent solution?
QuaTiMxi said:
I got it to work! I followed all the steps and when i was done I edited the keystr file in hex editor so the values was 4f and 4e and all others 00. This solution worked but its not permanent, each time I reboot the phone I have to do the same thing again, is there any permanent solution?
Click to expand...
Click to collapse
Save the file after editing
sent from my Galaxy
samersh72 said:
Save the file after editing
sent from my Galaxy
Click to expand...
Click to collapse
I save it but each time I reboot the phone the efs folder is empty again
Yeah I have followed your advice but the only way to disable the yellow window is to freeze/uninstall it :/ The permissions are all ticked (0777). Even after a reboot. Tried the solution from post 2 and 6 ...
This wouldnt be so bad but the power menue and the lockscreen are more important. I hope someone can help
Sent from my GT-I9505 using xda app-developers app
I'm so glad... everything works again. Download the android terminal emulatir from the playstore and enter the following commands:
su
echo -n ON > /efs/FactoryApp/factorymode
sync
reboot
This was the only way I was able to get the locksceeen and power menue
Hope that helps you!
Sent from my GT-I9505 using xda app-developers app
benni2903 said:
I'm so glad... everything works again. Download the android terminal emulatir from the playstore and enter the following commands:
su
echo -n ON > /efs/FactoryApp/factorymode
sync
reboot
This was the only way I was able to get the locksceeen and power menue
Hope that helps you!
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Good to hear:thumbup:
This command leads to same result posted in second post
sent from my Galaxy
Hi
I have a problem i get this error : E:failed to mount /efs (Invalid argument)
and the /efs file is empty there is nothing there what do i have to do please help
and the other message i get is ( Factory mode is on )
and sometimes it register the network after some hours it got no service and after flash i got back my network it hapend many times.
Please help.
Click to expand...
Click to collapse
The Phone is Dead now !! anyone can help please
habab said:
Hi
I have a problem i get this error : E:failed to mount /efs (Invalid argument)
and the /efs file is empty there is nothing there what do i have to do please help
and the other message i get is ( Factory mode is on )
and sometimes it register the network after some hours it got no service and after flash i got back my network it hapend many times.
Please help.
Click to expand...
Click to collapse
Read this thread.
vndnguyen said:
Read this thread.
Click to expand...
Click to collapse
i didn't understand this
2- Create a file with a name 'factorymode' on the sdcard, open it, input 'ON' and then save it. Navigate to the efs folder, create the folder with a name 'FactoryApp' (case sensitive). Finally move the file 'factorymode' you have created above to that folder. Reboot the phone to see if the problem still persists?
vndnguyen said:
Read this thread.
Click to expand...
Click to collapse
i have tried that thread still have same problem .
Any help !?!?
..
fffft said:
I'm sure that you find this frustrating. However we are not psychic. Unless you tell us what led up to this and in particular, a step by step, detailed description of what you have tried, how can we discern going on?
What led up to this situation? What exactly have you tried? Step by step, in detail. What exactly is in your /efs folder? Did you create the /efs/FactoryApp/factorymode file as was suggested earlier? Do you have a backup of your /efs partition? Is reactivation lock disabled?
If you actually created the file in the manner described and it didn't succeed and barring something novel in a description of your situation the next step is probably to mount the /efs partition from recovery mode, format it, recreate the /efs folder, remount and reboot so that the efs is rebuilt. But before you do any of that, give us a better description of your situation.
.
Click to expand...
Click to collapse
Hi , i Downloaded a efs backup app and i just pressed on restore before i press on backup , after that the /efs file is empty . i tried to make ( /efs/FactoryApp/factorymode ) with this app : root browser but that didn't work...
i have tried to Flash with many stock room from sammobile but the /efs file still empty .
after reboot i have to connect to Wifi every time i reboot the phone and some time i have Network and some time nott .
..
yes i have backup of the efs ,
the app that i am using just named Root browser with black android pirate icon
.
i maked the directory ( FactoryApp ) then ( file factorymode on the root ) then moved it on FactoryApp , after reboot i find the file emptey again !
and i used this app ( http://forum.xda-developers.com/galaxy-s3/development/efs-samsung-tool-universal-support-t2602325 ) for backup
..
1. i am sorry, my English is so bad !!
2. day 1 , i Downloaded the app Samsung tool and then maked a backup of EFS on External SD-Card ,
3. I maked restore and i had removed the SD-card
4. after that i didn't know that the efs file was damaged , i just installed an room from sammobile ( G900FXXU1ANG9_G900FNEE1ANG5_NEE ) , after the installation was done the phone started but i got an warning massage that says , FactoryMode is on and the wifi was off and only emergency call , i rebooted the phone the wifi was till of but i got back my Network after that i tried many firmware from sammobile
5. o searched on xda and find that it can be the efs but when opened the /efs it was empty.
6. i have the efs-backup on my sd i tried to restore it but nothing happened .
7. i tested that ( Opened this app : https://play.google.com/store/apps/details?id=com.jrummy.root.browserfree ) maked /efs/FactoryApp/ and then file factorymode , ON ) but it can't be moved to FactoryApp when i move or copy it to the folder it is nott there , After rebooting the phone even the FactoryApp directory is deleted .
in my sdcard i found only this ( samsung tool/efs.img )
i tried to make this again
directory ( FactoryApp ) then ( file factorymode on the root ) then moved it on FactoryApp
Click to expand...
Click to collapse
After reastart phone screen is just black !! but the pc is finding it !!! now the phone is dead
..
No i can't boot to anything !! it is just black screen .
No i can't boot to anything !! it is just black screen .
please help me with that.
vndnguyen said:
Read this thread.
Click to expand...
Click to collapse
fffft said:
I'm sure that you find this frustrating. However we are not psychic. Unless you tell us what led up to this and in particular, a step by step, detailed description of what you have tried, how can we discern going on?
What led up to this situation? What exactly have you tried? Step by step, in detail. What exactly is in your /efs folder? Did you create the /efs/FactoryApp/factorymode file as was suggested earlier? Do you have a backup of your /efs partition? Is reactivation lock disabled?
If you actually created the file in the manner described and it didn't succeed and barring something novel in a description of your situation the next step is probably to mount the /efs partition from recovery mode, format it, recreate the /efs folder, remount and reboot so that the efs is rebuilt. But before you do any of that, give us a better description of your situation.
.
Click to expand...
Click to collapse
fffft said:
No problem and your patience is appreciated.
Nothing anomalous is showing up in those details so I think we can safely assume that accidentally pressing the restore button rather than backup button simply corrupted your efs partition. All of those questions were aimed at confirming that with certainty, but I understand that this is a lot of work and frustrating for you too. So we'll proceed on that basis.
An efs.img file is an uncompressed efs backup. So try restoring that with your efs program. I have no idea if it is a valid (working) backup, but you aren't going to cause any further harm by trying to restore it. If that works, great and you're done. If not, then we'll go on to rebuild your efs instead.
To rebuild your efs partition we need a custom recovery. So a few last questions.
You are rooted, correct?
Did you use Towel root or CF-autoroot? (I am trying to discern if you have super su /busybox installed)
Are you able to boot to recovery mode (home + power up + power)?
Do you have a custom recovery installed e.g. TWRP or CWM?
If you can answer yes to all four questions, then go ahead and run the following efs repair script. If not, then you'll need to install a custom recovery first. If you're already rooted but don't have TWRP, then it's just a matter of flashing TWRP with Odin from download mode.
In any event, once you have a custom recovery in place you can run this recovery script.
Download the script here. Copy it to your external SD card. Then boot to recovery mode and install the flashable zip file "Brick_Loop_FIX_afterRestoringBackup.zip" that you copied to your Ext SD card.
Then reboot. If you still have any issues, reboot a second time, then let us know if your phone is working properly again.
Credit to Backachu, I believe for saving me the work of having to write a script for you or describe how to enter the commands manually.
The script comes from this thread. http://forum.xda-developers.com/showthread.php?p=47014662
As an aside, there is a minor mystery there. This comes from a Note 3 thread so when I went to modify it to work with your S5, I found that it was already set up for the S5 rather than the Note 3.. so why it is that way in a Note 3 thread is a mystery. Go figure. But I did check and you can use it the way it is.
.
---------- Post added at 07:43 AM ---------- Previous post was at 07:36 AM ----------
I'm not sure what you mean by "dead". If you can boot to recovery & download mode, don't worry about it for now. Otherwise please elaborate.
.
Click to expand...
Click to collapse
..
fffft said:
Don't panic. I'm sure that we can address the new issue, whatever it is.
I need a little information to determine how to fix it.
I understood that your screen is black after you rebooted. What do you mean by the PC can find it. What message do you see on the PC.. the normal USB message when you connect your phone or something else? If something else, what is the exact message from the PC?
Also please do the following
Disconnect the USB cable and remove your battery from your phone for ten seconds. Then replace the battery.
Now press and keep holding the home button. Then press and hold the volume down button as well, then lastly the power button. Keep holding all three until the phone starts (about ten seconds).
Let me know if you do or don't get to the download mode screen when you do that.
If you don't, try it a second time, just in case you weren't continously holding all three keys to get into download mode.
If you still don't, then we want to ensure that the Kies program is not running (if you have Kies on your computer). Then try going to download mode again in the same manner as above, then plug the phone into your computer with the USB cable and start the Odin 3.09 program and tell me what you see on the Odin screen.
.
Click to expand...
Click to collapse
When i plug it in i get a news USB device named : ZUES Flash Device .
i have tried to Hold Home + Volume - + Power nothing happen.
Odin don't find it , and kies program is not running.
..
Well, first of all.... I made a clean copy of my EFS folder before having this problem but.....using the lovely and simple commands copy and paste and now the files don't have the correct permissions and owners so nothing changes when I copy them back so my question is...
Could you guys please provide me a list with all the N910F EFS files + permissions and owners?
*EDIT*
My IMEI, serial number, baseband..... are all correct.
Thanks:crying:
Have u tried flashing stock rom through odin.Many users have fixed this problem by using the method
Sent from my SM-N910G using XDA Premium 4 mobile app
RISHI RAJ said:
Have u tried flashing stock rom through odin.Many users have fixed this problem by using the method
Sent from my SM-N910G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes, I tried 3 different stock roms, I also downgraded to stock kitkat and then flashed a stock lollipop rom and... same problem.
ANTONIOPS said:
Yes, I tried 3 different stock roms, I also downgraded to stock kitkat and then flashed a stock lollipop rom and... same problem.
Click to expand...
Click to collapse
same problem here also, except, i have original imei intact and can make calls, send sms etc. flashed original firmware through odin and through kies, no luck, efs file 0mb. I have lost finger print scan and my serial number is wrong.
I had a similar problem a while back, came across this info here, the 'dev' files mentioned are for a N910G, just type 'mount' at a terminal to see which 'dev' file the efs partition mounts on. I used Method 1, but Method 2, does essentially the same thing in the end, so which ever you find easiest. Damn saved my phone, I even bought a replacement online before I found this solutionl.
Fix screwed up EFS Partition.
-------------------------------
posted by Steve Lazarus on XDA Dev on 5th October 2013
http://forum.xda-developers.com/showthread.php?t=2471421
(Used METHOD 2 on 09-01-2015, worked a treat, RaSTuS)
(Will try METHOD 1 next time)
METHOD 1
1. Install stock Firmware via Odin then rerun autoroot (to regain root)
2. Install TWRP via Odin, reboot to recovery.
3. Install SuperSU from external SD Card.
4. Do an "adb shell" when phone is in recovery mode to run commands via TWRP.
From the ADB shell: Reset the EFS partition with the following commands:
mke2fs /dev/block/mmcblk0p13 (for N910G Note 4)
mkdir /efs
mount -t ext4 /dev/block/mmcblk0p13 /efs
Do a factory reset, reboot system
Afterwards, no more boot looping, the phone successfully registered on the
mobile network, and my IMEI is there and correct. Seems like the EFS partition
can rebuild itself now I guess...
Gotta love the XDA community !!!
METHOD 2
You can also try just running Commands via TWRP before using Odin to revert to
stock, re-rooting etc..Worked for me while I was doing some restore testing with
Jovy's modded kernel ..Just trying to save you some time..
Using TWRP Terminal Command To Complete this evolution...
1. Reboot to recovery
2. Hit "Advanced" Select "Terminal Command".
3. Hit "Select" (lower right corner) to select root (/) folder.
4. keyboard will open, type in the following commands, make sure you put the
spaces and / where they need to be, it needs to look exactly as outlined.
mke2fs /dev/block/mmcblk0p13 (for N910G Note 4)
Hit Go - The command will run.
Clear the input box, type the following command:
mkdir /efs
Hit Go - The command will run.
Clear the input box, type the following command:
mount -t ext4 /dev/block/mmcblk0p13 /efs
Hit Go - The command will run.
You can now back out of the terminal command, and follow the rest of the
directions.
rastus.rob said:
I had a similar problem a while back, came across this info here, the 'dev' files mentioned are for a N910G, just type 'mount' at a terminal to see which 'dev' file the efs partition mounts on. I used Method 1, but Method 2, does essentially the same thing in the end, so which ever you find easiest. Damn saved my phone, I even bought a replacement online before I found this solutionl.
Fix screwed up EFS Partition.
-------------------------------
posted by Steve Lazarus on XDA Dev on 5th October 2013
http://forum.xda-developers.com/showthread.php?t=2471421
(Used METHOD 2 on 09-01-2015, worked a treat, RaSTuS)
(Will try METHOD 1 next time)
METHOD 1
1. Install stock Firmware via Odin then rerun autoroot (to regain root)
2. Install TWRP via Odin, reboot to recovery.
3. Install SuperSU from external SD Card.
4. Do an "adb shell" when phone is in recovery mode to run commands via TWRP.
From the ADB shell: Reset the EFS partition with the following commands:
mke2fs /dev/block/mmcblk0p13 (for N910G Note 4)
mkdir /efs
mount -t ext4 /dev/block/mmcblk0p13 /efs
Do a factory reset, reboot system
Afterwards, no more boot looping, the phone successfully registered on the
mobile network, and my IMEI is there and correct. Seems like the EFS partition
can rebuild itself now I guess...
Gotta love the XDA community !!!
METHOD 2
You can also try just running Commands via TWRP before using Odin to revert to
stock, re-rooting etc..Worked for me while I was doing some restore testing with
Jovy's modded kernel ..Just trying to save you some time..
Using TWRP Terminal Command To Complete this evolution...
1. Reboot to recovery
2. Hit "Advanced" Select "Terminal Command".
3. Hit "Select" (lower right corner) to select root (/) folder.
4. keyboard will open, type in the following commands, make sure you put the
spaces and / where they need to be, it needs to look exactly as outlined.
mke2fs /dev/block/mmcblk0p13 (for N910G Note 4)
Hit Go - The command will run.
Clear the input box, type the following command:
mkdir /efs
Hit Go - The command will run.
Clear the input box, type the following command:
mount -t ext4 /dev/block/mmcblk0p13 /efs
Hit Go - The command will run.
You can now back out of the terminal command, and follow the rest of the
directions.
Click to expand...
Click to collapse
I tried that and those solutions didn't work because I'm the biggest idiot in this galaxy:laugh:, some time ago I deleted the EFS golden backup in the service menu and I think that's why it didn't rebuild after I erased the main EFS partition but the good thing is that I made a clean backup of it so I can copy the files back to the EFS folder, the thing is that I just copied and pasted them so now all files have root as the owner and I know some of them had system, radio, wifi... as owners but I can't remember which ones, I think I could fix it if I see a list with the files, permissions and owners. Thanks anyway:good::good:
*EDIT*
Oh!! also I forgot to tell you that my imei, baseband, serial number bla, bla, bla are correct.
please help guys i have same problem but my note is n910f
hello ... its my first comment here ... and i whant to ask ...if i have the same phone ...but ... its a n910f ... its working this metods ? please guys i need help ... thx ...
Hi, I have a N910C and my IMEI got changed when i flashed offical lolipop 5.1.1, and now it wont register on any network, the IMEI isn't fake or corrupted i tried imei analyzer and it says its valid but for a 2005 Phone. I tried deleting /efs entirely/ flash diff firmwares / factory reset / clean kies install, nothing worked. my .nv_data.bak/nv_data.bak is missing. Please help
N910F EFS lost
florinhrib said:
hello ... its my first comment here ... and i whant to ask ...if i have the same phone ...but ... its a n910f ... its working this metods ? please guys i need help ... thx ...
Click to expand...
Click to collapse
i'm new too i'm from Algeria, i have a GN4 with no IMEI, i lost the EFS foldier, the wifi and blueth work but no finger print and no health app, please help