Related
Is there someone here that have bought a norwegian HTC magic.
I need the Norwegian rom and radio..
if it's possible to flash on the voda, I'd like a copy of that one too
I have no clue on how to extract it, but if you would like to enlighten me and it's not too much of a hassle I'll get you a copy from mine.
I doent know how to extract it my self,, but i will think there are people here en XDA dev that knows..
What version RADIO are on the norwegian magic?? because i have problems with the reception on my magic..
Baseband v. 62.52S.20.18U_3.22.20.17
Here is the way to backup your rom.. Can you take a copy of your norwegian rom and upload it..
Quote from another XDAdev forum user
Here's how to do a Nandroid backup:
Firstly, download fastboot.exe, or if you are on Linux, just fastboot. You can get fastboot from HTC's website, here's the link:
http://www.htc.com/www/support/android/adp.html#s2
Save fastboot.exe in just c:\ (the root/beginning of your C: disk).
You need to make sure the USB drivers for the HTC Magic are installed on your computer.
Then you need to download this file, unzip it, and save it to your phone's sdcard:
http://www.droiddeveloper.com/hrbuil...ry-new.img.zip
You must unzip the file, so that you have "recovery-new.img" on the SDCard.
Then, please turn off your HTC Magic, and hold down the Back button (arrow button next to the Search button), whilst turning the phone on.
This will enter Fastboot mode, and the phone should show "SAPPHIRE xxxxx FASTBOOT USB" and some other information.
From your computer, go to a command prompt (Start -> Run -> cmd [enter]), or just Start -> cmd [enter] if on vista.
Type: cd \ (that's CD, space, backslash) then [enter]. This changes your working directory to the root of the c: drive, where we have saved fastboot.exe.
Then type "fastboot devices" and make sure that fastboot on the computer can see your phone. Hopefully it will return a model or serial number of the HTC handset.
If so, please type "fastboot boot recovery-new.img".
This will start your phone up with the modified recovery image, which has Nandroid backup built into it. You should now see the recovery screen on the phone, with some menu options, including "Nandroid Backup".
Please choose to do a Nandroid backup from the menu on the phone. This will create a folder on the phone's sd-card called Nandroid, with some other folders inside, with backups of the system.
You can then choose restart from the Recovery screen and everything will be back to normal.
Please can you do this and send us the files? From your perspective it would be better if you wiped the phone (Factory reset on the phone, Under Settings -> SD card & phone storage -> Factory data reset) before doing this because we don't want your data. Or you could just do it, zip up the files and contact me and I will take your files, restore here, wipe data, then re-zip the files, so nobody will have your information. If you are not happy with that, you could just send us all the files except data.img. I'm sure that would be OK.
Please help me folkz.....Still having problems with the reception here in Norway...
Just have to figure some stuff and I might be able to have a go at it, only problem atm is that I had back surgery 3 days ago and can't have long sessions in front of a computer yet...
but correct me if I am mistaken, but don't I need to root my phone before using nandroid for it to make a complete backup which also includes spl/baseband?
Here is my backup from Norwegian htc magic. I had to use "daldroid-recovery.img" to get it. Let me know how it works.
http://rapidshare.com/files/250022072/norwegian-htc-magic.zip.html
Hi I tried to install your ROM but then my magic will not start so I installed the old ROM again..
To bad don't know what more I can do then.
I followed each one of your steps. I get an error when trying to install the signed zip. "Can't find update script" Can anyone please help me with this.
thank you
I'm doing option 2. I get it signed just get an error "Can't find update script"
This quick guide will teach you how to sign ROMs!
WARNING : YOU WILL NEED AT LEAST A BASE KNOWLEDGE OF HOW TO USE COMMAND PROMPT.
The knowledge of signing ROMs can prove useful to anyone! By knowing how to sign ROMs, you can modify your favorite ROM to add or delete APKs, so when you flash the ROM your favorite apps will be present! Or you can delete apps you don't use so they will not be installed when flashing the ROM!
Before starting, you need a couple of things. First you will need Java SE Development Kit and Java SE Runtime Environment . You can download them HERE.
After you have downloaded and installed both, you will need a very useful tool made by someone at XDA-Developers (if you know who it is please let me know).
Download this tool (attached) and unzip everything inside of it into one common folder. I personally unzipped everything into my Android SDK folder.
Signing
Now run the autosign.bat. You will have to go through commands 1(Set PATH variable for SDK) ,2 (Set CLASSPATH variable for signing tool) and 3 (Install registry entries). They are very easy to use and just follow the instructions. If you are asked to confirm and/or replace a file, always select yes!
Now you are finally ready to sign! There are two options to sign the .zip
1)Find the ROM (.zip) and right click and select "Resign Zip". If you use this option a command prompt box should quickly appear and disappear.
OR
2) Using the Autosign.bat, select option 4, and then write the directory and file name of the ROM. For example,
D:\Android\ROMs\YourROMHere.zip
It will hang for a bit at the part where it says "signing", and then it should say something along the lines of "Successfully completed if no errors above"
If this helped you, comment below!
http://androidforums.com/developer-101/8665-how-signing-roms.html
Anyone...... I know someone knows
You have to zip the contents of the rom, not the rom itself. i.e. if you sign the rom folder, it will be ROM_Signed.zip->ROM->system/data/metainf... you get the picture. Go into the folder you want to zip and then sign, select the contents, and zip them. It will then be ROM_Signed.zip->/system/data/metainf. Then just sign it.
update-script is a script that tells the flash utility what to do. It is located in the zip as part of the following directory structure:
META-INF/com/google/android
The contents can vary. For Darktremor A2SD 2.6.1, here's the contents:
show_progress 0.1 0
copy_dir PACKAGE:system SYSTEM:
show_progress 0.1 10
PACKAGE is used by android to reference the actual zip file, or package file.
SYSTEM is used to represent /system
DATA is used to represent /data
CACHE is used to represent /cache
BOOT is used to represent the boot partition (which is where you flash boot.img)
RECOVERY is used to represent the recovery partition. Never actually seen this used. I guess it used for an update.zip that you would flash via fastboot.
The zip file has to be structured in the same way as the file system on your phone. If you want to install something to, say, /system/bin, you must have a system folder, which in turn has a bin folder.
What I would do is take one of the available ROMs and unzip it. Then look for their update-script. Usually ROM packages are more detailed in the update-script.
If you don't have update-script in your zip file, the flash utility in recovery won't know what to do.
networx2002 said:
I followed each one of your steps. I get an error when trying to install the signed zip. "Can't find update script" Can anyone please help me with this.
thank you
I'm doing option 2. I get it signed just get an error "Can't find update script"
This quick guide will teach you how to sign ROMs!
WARNING : YOU WILL NEED AT LEAST A BASE KNOWLEDGE OF HOW TO USE COMMAND PROMPT.
The knowledge of signing ROMs can prove useful to anyone! By knowing how to sign ROMs, you can modify your favorite ROM to add or delete APKs, so when you flash the ROM your favorite apps will be present! Or you can delete apps you don't use so they will not be installed when flashing the ROM!
Before starting, you need a couple of things. First you will need Java SE Development Kit and Java SE Runtime Environment . You can download them HERE.
After you have downloaded and installed both, you will need a very useful tool made by someone at XDA-Developers (if you know who it is please let me know).
Download this tool (attached) and unzip everything inside of it into one common folder. I personally unzipped everything into my Android SDK folder.
Signing
Now run the autosign.bat. You will have to go through commands 1(Set PATH variable for SDK) ,2 (Set CLASSPATH variable for signing tool) and 3 (Install registry entries). They are very easy to use and just follow the instructions. If you are asked to confirm and/or replace a file, always select yes!
Now you are finally ready to sign! There are two options to sign the .zip
1)Find the ROM (.zip) and right click and select "Resign Zip". If you use this option a command prompt box should quickly appear and disappear.
OR
2) Using the Autosign.bat, select option 4, and then write the directory and file name of the ROM. For example,
D:\Android\ROMs\YourROMHere.zip
It will hang for a bit at the part where it says "signing", and then it should say something along the lines of "Successfully completed if no errors above"
If this helped you, comment below!
http://androidforums.com/developer-101/8665-how-signing-roms.html
Click to expand...
Click to collapse
HeroMeng said:
You have to zip the contents of the rom, not the rom itself. i.e. if you sign the rom folder, it will be ROM_Signed.zip->ROM->system/data/metainf... you get the picture. Go into the folder you want to zip and then sign, select the contents, and zip them. It will then be ROM_Signed.zip->/system/data/metainf. Then just sign it.
Click to expand...
Click to collapse
It took my brain a min, but i got it.
Thanks
********NOTE*********
i have included a few of the tools you will need as attachments to this post. I will not take any credit for these programs as i was not the developer for them... these people work too hard to have anyone steal their credit... please give credit where credit is due!Your nv_data.bin file and its matching nv_data.bin.md5 files are located on your phone in /efs/
All references that i make to "sd card" or "/sdcard/" refer to your phone's internal SD Card, not an external SD card that you may have installed.
I have created a windows batch file that you can run and it will extract your entire /efs/ folder from your phone to your PC. I am currently working on the batch script to move the edited nv_data.bin files back to your/efs/ folder and do the other adb stuff.
attached is the EFS Extractor.zip file that contains the ADB files and the batch script.
The product code for your AT&T Captivate is: SGH-I897ZKAATT
WARNING… I AM NOT RESPONSIBLE IF YOU BREAK YOUR PHONE FOLLOWING ANY OF THESE INSTRUCTIONS
The Attached EFS Extractor.zip file contains the necessary adb file and a couple batch files. "retrieve efs.bat" copies your entire /efs/ folder to your PC in a folder called /efs_bkup/ in the directory where you unzipped the file and ran the batch program from. The file "update nv_data.bat" takes your edited nv_data.bin file from the root directory where you ran the .bat file from and places in in your phone's /efs/ folder and removes the old copies from your phone... when it is done, it will power cycle your phone.
To fix your nv_data.bin, you will have to have access to the following tools:
A hex editor (search google for hex editors, they have tons of them that are free… I use one called HexEdit and i have it attached)
GalaxyS_One-Click_Root_All_Models (available via XDA-Developers... attached)
ADB (Android Debugging Bridge) This is available by getting the Android SDK at the Android Developers Website (http://developer.android.com/sdk/index.html) or if you downloaded the Galaxy S One Click Root, it is in the directory where you unzipped the files.
BusyBox – Search the google market for “BusyBox”. It will appear and will be the free one from stericson (i have included the .apk as an attachement)
Odin One-Click Downloader (available from XDA)… make sure you get the correct one. There are 2 versions. If you batch number is 1008 then you need the one with the 3-button fix, if you batch number is greater than 1008 then you should need the regular one. Your batch number is written on the sticker on your phone under your battery on the left side right under the words “S/N” where your serial number is listed.
Samsung Kies Mini (gotten from Samsung website)
Download the attached EFS Extractor .zip file. It contains everything you need to copy your /efs/ folder to your PC
Now for what you need to do to get your phone’s nv_data.bin back to normal:
Flash back to stock and then do a master clear using Odin One Click
put phone into USB debugging mode and also check the setting to "stay awake"
connect phone to PC and root and install busybox
extract the attached EFS Extractor.zip file and run the "retrieve efs.bat" file. This will copy your entire /efs/ folder from your phone to your PC in a direcotry called ./efs_bkup/
Using the Hex Editor, edit the file ./efs_bkup/efs/nv_data.bin on your PC to have the correct product code SGH-I897ZKAATT. do an ASCII search for "SGH" to locate the line in the file that contains your product key. then save the edited file to ./nv_data.bin (the root directory where you extracted your ZIP file to on your PC)
run the file "update nv_data.bat" to copy your corrected nv_data.bin to your phone's efs folder and chown it and reboot your phone
change USB Settings on phone back to Kies then open Kies Mini and connect phone.
you should now be able to connect to Kies Mini and not have unregistered device... now would be a good time to back_up your /EFS/ folder... you can now either do Odin One-Click and a master clear, or flash a different rom. You should do Odin if you want to use Kies to get updates to be 100% stock to remove your root and busybox.
The general overview what what you need to do is this for those of you that want to know and/or use other tools to do this
Copy your /efs/nv_data.bin file from your phone to your PC
Use a hexeditor to modify the line in the nv_data.bin file that contains the productcode to contain your correct product code
delete any nv_data.* files from your /efs/ folder on your phone
copy the corrected nv_data.bin file from your PC to your /efs/ folder on your phone
busybox chown 1001:1001 /efs/nv_data.bin
reboot phone
Done!
Now, when you backup your /efs/ folder to your PC you may see files like nv_data.bak and nv_data.bak.md5. Using a hexeditor, open the nv_data.bak file and look at the line that has the product code (ASCII values starting wtih SGH)... if the product code in the .bak file is correct, then delete the nv_data.bin and nv_data.bin.md5 from your /efs/ folder on your phone and reboot your phone. Your phone should then create new .bin and .bin.md5 files from the .bak and .bak.md5 files that will have the proper productcode. You can also optionally rename the .bak and .bak.md5 files on your PC to be .bin and .bin.md5 and copy them to your /efs/ folder on your phone.
You can view what Kies is reading your productcode as by opening your windows registry editor Start>Run>regedit[enter]
Connect phone to PC in Kies(Firmware) mode
Navigate to HKEY_CURRENT_USER/Software/Samsung/KiesMini/FUS
Look at the key "PRODUCTKEY" and what it's value is... if it is correct, then you are good. If not, then something went wrong somewhere.
If you have issues please post the issues you are having and I will update as necessary.
Here is a link to a different thread that contains a program and instructions for restoring your unlock codes if that is what you are trying to do. The .jar (java program is written in frech, but it only asks for the codes you want to use for your unlock codes... i did not make this program so I cannot help you with it.
http://forum.xda-developers.com/showpost.php?p=8983897&postcount=103
Tried to trim this down a little as there are a ton of steps, let me know if any of this is incorrect.
1. Flash back to stock rom, and do a master clear using the Odin3 One-Click Downloader by designgears
2. Root using one-click-root and install busybox, turn on usb development mode + stay awake, and connect to your PC.
3. Open a command prompt window and navigate to the directory where you extracted the one-click-root. Run the following commands:
a. adb shell
b. su
c. cp /efs/nv_data.bin /sdcard/nv_data.bin
d. cp /efs/nv_data.bin /sdcard/nv_data.bin.copy (incase there is a problem)
e. rm /efs/nv_data.*
4. Exit your adb.exe window, mount your phone on your PC and navigate to the internal card. Edit the nv_data.bin with a hexeditor (bpsoft.com) and search (ascii) for "SGH-" (without the quotes)
5. It may be something like SGH-I897ZKATOR or SGH-I897ZKATMB. You need to change this to SGH-I897ZKAATT then save the file, and unmount your phone.
6. Disconnect usb data cable from pc to phone, re-enable usb development mode + stay awake, reconnect.
7. Open a command prompt window and navigate to the directory where you extracted the one-click-root. Run the following commands:
a. adb shell
b. su
c. cp /sdcard/nv_data.bin /efs/nv_data.bin
d. busybox chown 1001:1001 /efs/nv_data.bin
8. Power cycle
Hi hansomni. l've been down this road. Were you successfull with creating Nv_data.bak this way and restoring with that. For example editing nv_data.bak and making a corresponding md5 file and only placing those files in your efs folder and restarting your phone
I had problems creating this file. i would always get an incorrect iemi. This is why i recommend using nv_data repair.zip posted in the tmo vibrant unlock thread not only can you recreate the correct product code but also fix the fffffffff for unlock code.
Have you checked this outhttp://forum.xda-developers.com/showpost.php?p=8983897&postcount=103
mattbeau said:
Hi hansomni. l've been down this road. Were you successfull with creating Nv_data.bak this way and restoring with that. For example editing nv_data.bak and making a corresponding md5 file and only placing those files in your efs folder and restarting your phone
I had problems creating this file. i would always get an incorrect iemi. This is why i recommend using nv_data repair.zip posted in the tmo vibrant unlock thread not only can you recreate the correct product code but also fix the fffffffff for unlock code.
Have you checked this outhttp://forum.xda-developers.com/showpost.php?p=8983897&postcount=103
Click to expand...
Click to collapse
yeah... i have been successful using the steps i outlined... like i said in the original post, this is only to get your product code fixed... i don;t have an unlocked phone so i don't know if that program works... i did use it to check it out, but it is written in frech or something and it never copied the "patched" nv_data files back to my phone... i had to do it manually and still the product code from the created files were wrong. Others say that they have had success using it, but i never did. I took a buch of stuff from a buch of posts on this site to compile the guide here for restoring product codes only.
the .bak files are your backup files that get generated sometimes... usually those files have your correct unlock codes and productcode... to restore them, just delete the non .bak files and remove the .bak extension from the backups... then copy them to your /efs/ folder and powercycle and you should be good. you should keep all your orignial files from your /efs/ folder in a safe place though so you have them to fall back on if you need to. I have never had the .bak files in my /efs/ folder so i haven't ever been that lucky.
devz3r0 said:
Tried to trim this down a little as there are a ton of steps, let me know if any of this is incorrect.
1. Flash back to stock rom, and do a master clear using the Odin3 One-Click Downloader by designgears
2. Root using one-click-root and install busybox, turn on usb development mode + stay awake, and connect to your PC.
3. Open a command prompt window and navigate to the directory where you extracted the one-click-root. Run the following commands:
a. adb shell
b. su
c. cp /efs/nv_data.bin /sdcard/nv_data.bin
d. cp /efs/nv_data.bin /sdcard/nv_data.bin.copy (incase there is a problem)
e. rm /efs/nv_data.*
4. Exit your adb.exe window, mount your phone on your PC and navigate to the internal card. Edit the nv_data.bin with a hexeditor (bpsoft.com) and search (ascii) for "SGH-" (without the quotes)
5. It may be something like SGH-I897ZKATOR or SGH-I897ZKATMB. You need to change this to SGH-I897ZKAATT then save the file, and unmount your phone.
6. Disconnect usb data cable from pc to phone, re-enable usb development mode + stay awake, reconnect.
7. Open a command prompt window and navigate to the directory where you extracted the one-click-root. Run the following commands:
a. adb shell
b. su
c. cp /sdcard/nv_data.bin /efs/nv_data.bin
d. busybox chown 1001:1001 /efs/nv_data.bin
8. Power cycle
Click to expand...
Click to collapse
Yeah, looking at it quickly it looks like all the instructions are correct... maybe abbreviated too much... Thanks for that... i will update with instuctions similar.... i have to remember that there are those folks that have never used adb or know what it is. I will credit you in my update tomorrow. I am used to where i work we have people that use computers that don;t know how to power them on and off so they just leave them on all the time... i have to be very specific on my instructions that i tell them so they can understand... a two second task becomes an all-day event. Just something i am used to doing.
I will be working on a dos script (.bat) file that will do most of the adb stuff so then the users only need a few things to do and just let the scripts take care of the rest.
hansonmi said:
yeah... i have been successful using the steps i outlined... like i said in the original post, this is only to get your product code fixed... i don;t have an unlocked phone so i don't know if that program works... i did use it to check it out, but it is written in frech or something and it never copied the "patched" nv_data files back to my phone... i had to do it manually and still the product code from the created files were wrong. Others say that they have had success using it, but i never did. I took a buch of stuff from a buch of posts on this site to compile the guide here for restoring product codes only.
the .bak files are your backup files that get greated sometimes... usually those files have your correct unlock codes and productcode... to restore them, just delete the non .bak files and remove the .bak extension from the backups... then copy them to your /efs/ folder and powercycle and you should be good. you should keep all your orignial files from your /efs/ folder in a safe place though so you have them to fall back on if you need to.
Click to expand...
Click to collapse
You dont even need to change the extenaion of those files if you power cycle your phone with just .Bak files. Your phone will recreate the nv_data.bin and md5 from those .Bak files and create a log file
Yeah i know the java program is in french. But its only asking you what two codes you want to use for unlocking your phone ( ahh google translate)
And yes the first time i tried the program i had trouble too. I think it helps if you have a good busybox version.
Believe me the easier you can make it the better it will be for everyone. Now if we could just get everyone to back up that folder before flashing anything we wouldnt even need to go down that road. Thanks for your help in this. Ill leave this thread alone now sorry if im intruding. Pm me if you need any help
mattbeau said:
You dont even need to change the extenaion of those files if you power cycle your phone with just .Bak files. Your phone will recreate the nv_data.bin and md5 from those .Bak files and create a log file
Yeah i know the java program is in french. But its only asking you what two codes you want to use for unlocking your phone ( ahh google translate)
And yes the first time i tried the program i had trouble too. I think it helps if you have a good busybox version.
Believe me the easier you can make it the better it will be for everyone. Now if we could just get everyone to back up that folder before flashing anything we wouldnt even need to go down that road. Thanks for your help in this. Ill leave this thread alone now sorry if im intruding. Pm me if you need any help
Click to expand...
Click to collapse
Yeah... the problem is that not everyone knew to do it before flashing as a lot of the ROM pages don't say it (I was one of them that never knew about it)... i knew what the java was saying but since i don't have an unlocked phone, i had no way of testing it to see if it worked for me or not... and on top of that it didn't work with restoring my productcode (i know that becuase i couldn't use Kies until i did things manually)... I tell people to rename the files, becuse i am assuming they copy the contents of their /efs/ folder to a PC or something... then they just have to delete the nv_data files from /efs/ on their phone, and rename the .bak files on their PC and copy them back to their phone's /efs/ so they still have a copy of their original files saved on their PC... plus i don't like relying on the phone doing the renaming because if it doesn't no one will know what went wrong...
Working on Windows Batch (.bat) script
I will be working on doing a windows .bat script that will do most of the dirty work for you... it may take a couple days because where i work the end of the year is the busiest time for me and i don't have a lot of time between work during the week.
I will make the script an attachment and will hopefully be able to zip with the abd files to make life a little easier for everyone.
Thanks for the input everyone.
What line
Could someone that has successfully done this post what line in the hex file the product code is found on. All I get is string not found??? Thanks
Worked great, followed steps exactly as outlined didn't have any problems. Thanks again for this, I've been wanting to have a proper backup of efs folder with correct product code, but could never change it back.
Slowazz28 said:
Could someone that has successfully done this post what line in the hex file the product code is found on. All I get is string not found??? Thanks
Click to expand...
Click to collapse
I used hexedit, and if the line number is in first column it begins on line 188010. I did notice when searching a second time to get line number, that I had to have sgh- in all caps, and once i got string not found, I closed program reopened and searched again using caps (SGH-) it worked several times. Hopes this helps.
Big thanks for posting this.
I'll give this a shot prior to flashing Axura 2.5.
Thanks hansonmi! I got it updated with kies. I done it a lil diffent using root explorer to move files around and used hexeditor to edit files and root explorer to copy back.
great guide.
wish this would have been around the first time i ran into this problem as it was a headache when it happened and the threads and advice on fixing were so fragmented within the forum threads.
The only thing i did differently was that i didn't use ADB on a pc at all during the process (I completed the process using both Root Explorer and Terminal Emulator on my phone and copying files to pc via mounting the phone and its storage as disk drives).
(PS before doing any of this i backup up my efs folder first to my external SD using root explorer and then to my pc via mounting the phones storage)
1. I had already copied my nv_data.bin file to external SD when backing up EFS folder.
2. Connected to pc via usb and mounted for storage (with debugging on)
3. copid nv_data to pc
4. used PsPad to edit the nv_data file in accordance with previous instruction in this thread. (I highly recommend PSpad as a hex editor. Its nice that you can switch back and forth between hex and text editor views) See PS in the end for using PSpad hex editor to find the line you need to edit. That seemed to be the only thing that needed clarified.
5. copy nv_data.bin back to the root directory of external sd
6. use root explorer to move newly edited nv_data from external sd back to original EFS folder.
7. Delete the nv_data..bin.md5 file..i left the backup from efs folder
7. delete any nv_data.baks from efs folder
8. Now the use of Termainl Emulator (download from market). Busybox must be installed as well
9. Open terminal emulator execute following commands:
SU
busybox chown 1001:1001 /efs/nv_data.bin
reboot
(reference to step 4 using hex editor)
PS - These are the steps for editing the hex code and starting with step first step assuming you have copied the nv_data.bin to your PC
1. Open PsPad (or other hex editor)
2. Open nv_data.bin in hex editor mode
3. Go to line 188000 (using search modes you will likely have to enter $00188000 or 00188000) Using PsPad you would do the following:
Select SEARCH from top tool bar. Select GOTO LINE.......then enter $00188000
4. You will see yTMB....SGH_i897ZKATMB (or yTOR....SGH-ZKATOR).
5. Replace that first TMB or TOR with ATT then replace ZKATMB or ZKAATOR with KZAATT
6. Save
7. Now you should have a proper nv_data.bin
HBeezy said:
I used hexedit, and if the line number is in first column it begins on line 188010. I did notice when searching a second time to get line number, that I had to have sgh- in all caps, and once i got string not found, I closed program reopened and searched again using caps (SGH-) it worked several times. Hopes this helps.
Click to expand...
Click to collapse
Ok that worked great except when I get to that line it says productcode several times then a bunch of x's then 11 0's but no SGH- so not sure where to put it in at. The 0's start on line 1880f0 and end on line 188100 ??? Appreciate the help
Slowazz28 said:
Ok that worked great except when I get to that line it says productcode several times then a bunch of x's then 11 0's but no SGH- so not sure where to put it in at. The 0's start on line 1880f0 and end on line 188100 ??? Appreciate the help
Click to expand...
Click to collapse
what hex editor are you using?
i recommend downloading the free PSpad Hex/Txt editor.
1. Open your nv_data file using FILE then OPEN IN HEX EDIT
2. use SEARCH from toolbar commands....GOTO LINE from search menu....options after opening in hex edit mode
3. then search for $00188000
you should see the line you need to edit.
The nice thing about PSPAD is that you can also open the binary file in a Text mode. If you have trouble finding it in the hex editor mode try the following.
1. open PSpad. Goto FILE then OPEN (vs. open in hex edit). This will open in a text editor view/mode.
2. goto SEARCH and select INCREMENTAL SEARCH
3. type SGH and search
(you could also do all the hex editing without moving files to pc if you wanted using HEX EDITOR from market...though for most the PC hex editors might be easier)
if you want to use the android hex editor app to do all the editing on your phone...do the following:
THERE ARE 3 Total Lines you will need to edit:
00188008
00188010
00188020
1. Use Root Explorer to copy nv_data.bin from efs folder to the root directory on your external sd.
2. Use Hex Editor App to open the copy from your external SD.
3. One Open click the capacitive menu button and select jump to address
4. Enter 0188008
This will take you to line 00188008
5. Edit the last or 8th Block so it reads 41.
6. Enter 0188010
7. This will take you to line 00188010. Edit the first two blocks of this line. Replace the #'s so that both of the first two blocks contain 54. (look to the text at the right of screen the first two letter should have changed to TT. To recap you need to edit Block 1 and Block 2 of line 0018010:
LINE 0018010
Block 1 = 54
Block 2 = 54
(text @ right should now read TT....SG)
8. Now look down to line 0018020 and look at the line. If you at the line and to the far right text you will see ATOR or ATMB if your nv_is messed up.
9. You may need to edit blocks 2-4. They should read as follows:
LINE 00188020
Block 2 = 41
Block 3 = 54
Block 4 = 54
(the text at the right of your screen should now read AATT....)
10. Save the file and move it back to efs using root explorer.
PS: Here are how the following lines should read (the ones in bold are the only ones you have to edit as line 00188018 will already be correct):
00188008|2e|34|00|00|00|00|ff|41|.4....A
00188010|54|54|00|00|00|00|53|47|TT....SG
00188018|48|2d|49|38|39|37|5a|4b|H-I897ZK
00188020|41|41|54|54|00|00|00|00|AATT....
bames said:
what hex editor are you using?
i recommend downloading the free PSpad Hex/Txt editor.
1. Open your nv_data file using FILE then OPEN IN HEX EDIT
2. use SEARCH from toolbar commands....GOTO LINE from search menu....options after opening in hex edit mode
3. then search for $00188000
you should see the line you need to edit.
The nice thing about PSPAD is that you can also open the binary file in a Text mode. If you have trouble finding it in the hex editor mode try the following.
1. open PSpad. Goto FILE then OPEN (vs. open in hex edit). This will open in a text editor view/mode.
2. goto SEARCH and select INCREMENTAL SEARCH
3. type SGH and search
(you could also do all the hex editing without moving files to pc if you wanted using HEX EDITOR from market...though for most the PC hex editors might be easier)
if you want to use the android hex editor app to do all the editing on your phone...do the following:
THERE ARE 3 Total Lines you will need to edit:
00188008
00188010
00188020
1. Use Root Explorer to copy nv_data.bin from efs folder to the root directory on your external sd.
2. Use Hex Editor App to open the copy from your external SD.
3. One Open click the capacitative menu button and select jump to address
4. Enter 0188008
This will take you to line 00188008
5. Edit the last or 8th Block so it reads 41.
6. Enter 0188010
7. This will take you to line 00188010. Edit the first two blocks of this line. Replace the #'s so that both of the first two blocks contain 54. (look to the text at the right of screen the first two letter should have changed to TT. To recap you need to edit Block 1 and Block 2 of line 0018010:
LINE 0018010
Block 1 = 54
Block 2 = 54
(text @ right should now read AT....SG)
8. Now look down to line 0018020 and look at the line. If you at the line and to the far right text you will see ATOR or ATMB if your nv_is messed up.
9. You may need to edit blocks 2-4. They should read as follows:
LINE 00188020
Block 2 = 41
Block 3 = 54
Block 4 = 54
(the text at the right of your screen should now read AATT....)
10. Save the file and move it back to efs using root explorer.
PS: Here are how the following lines should read (the ones in bold are the only ones you have to edit as line 00188018 will already be correct):
00188008|2e|34|00|00|00|00|ff|41|.4....A
00188010|54|54|00|00|00|00|53|47|AT....SG
00188018|48|2d|49|38|39|37|5a|4b|H-I897ZK
00188020|41|41|54|54|00|00|00|00|AATT....
Click to expand...
Click to collapse
Ok, So my nv_data.bin must be fubared cause I don't even have lines 188008 or 188018. They go by 10's like 188000, 188010, 188020, ect. And the text to the right of line 188010 starts TT....SG not AT....SG
File
I didn't back this up from my first flash to a custom ROM. Stated at the beginning it says this is likely unfixable. I have run Axura, Cog and Perception Roms (not in that order). Not sure if that makes a difference. Is this still fixable? The problem I have (using new market) is apps are either
A) Installed and not showing so on the market
B) I have them installed and they disappear & have to reinstall them from the market only to have them disappear from my phone again
C) Unable to download them (such as Pocket Legends)
Any feedback is appreciated.
Thanks
Slowazz28 said:
Ok, So my nv_data.bin must be fubared cause I don't even have lines 188008 or 188018. They go by 10's like 188000, 188010, 188020, ect. And the text to the right of line 188010 starts TT....SG not AT....SG
Click to expand...
Click to collapse
my bad
the 188010 should start TT i will correct my original.
but you should be able to find lines 188008 an 18 though you wont need to do anything with 18. Did you try looking at it with the android hex editor app from market?
You won't see the 008 and 018 lines if your using a hex editor on PC you will only see the lines by by 10's.
The section you are referring to are for Using Android Hex Editor App on your phone.
-----------------------
if your using a hex editor on your PC you should see the following when corrected:
188000 | FFFF | FFFF | 5245 | 5630 | 2E34 | 0000 | 0000 | FF41 |
188010 | 5454 | 0000 | 0000 | 5347 | 482D | 4938 | 3937 | 5A4B |
188020 | 4141 | 5454 | 0000 | 0000 | 0000 | 0150 | 024E | 034E |
Slowazz28 said:
Could someone that has successfully done this post what line in the hex file the product code is found on. All I get is string not found??? Thanks
Click to expand...
Click to collapse
It really depends on the editor you are using and you have to make sure you are searching for ASCII...
in the edit that i use, it is line 188010
[FIX] Note4 Exynos N910C bootloop problem + Invalid IMEI "Network" problem FIXED!
Hi Guys....First of all, I'd like to CREDIT:-
1- FR34K-B1B0 to whom I owe the idea. Man, you really powered me on :fingers-crossed: :good:
2- h311sdr0id who created Ext4Unpacker tool.
3- lyriquidperfection
for his great EFS Professional tool.
-------------------------------------------------------------------------------------------------
Many members threaded the problem of Note 4 N910C Exynos version bootlooping when they tried to get back to stock 5.1.1 from a custom CM13 ( or any custom based on 6.0 ). I've been suffering the same problem for 2 weeks.
After tons of internet gigs consumed, cups of coffee drunk, and hours wasted :crying: , I found this solution :victory: ; which I really hope it'll help.
Let's start
Phone Status:*Custom rom based on 6.0 // **rooted // *** busybox installed "smart install" // **** TWRP custom recovery.
Computer Requirements: *Win7 or higher "I'm using Win10" // **Samsung USB Drivers // ***adb-Drivers ( download SDK Tools, install "platform tools " and "Google adb Drivers" Packages. To test it, run the command
Code:
adb drivers
in the folder where the packages are installed ) // **** EFS-Professional
STEPS[/FONT]
STEP1: Through TWRP, make a full backup; then copy this backup ( you should find it in the folder /TWRP/BACKUPS/(some no.s)/(your backup name) in your phone's internal storage ) to your computer, rename the backup "6.0". This backup has an EFS folder which isn't compatible with stocks lower than 6.0, but its IMEI is the right one of your phone (keep this in mind).
STEP2: a- In your phone - rooted and having busybox installed - apply USB-Debugging and grant root access to adb (for CM13 Users, it's a feature you can find in Developer options settings)
b- Connect your phone to the computer, then open EFS Professional ( you should receive a msgbox in your phone; check "Always allow this computer"; then click "OK"or whatever..... )
TIP: if you face a problem opening EFS-Prof., try restarting it, if not solved, make sure that: *You allowed the computer (msgbox of the phone)// **Your device is rooted// ***Your device have busybox Pro fully installed.
c- When EFS-Pro loads, choose the 3rd tab "Samsung tools" , surf to "other tools" and choose "Format EFS Folder" then click "Execute"
TIP: If a msgbox appears saying that permission is denied, it doesn't matter at all, only click "Execute" again, it'll tell you "Can't find mount points" this means it's done
d- REBOOT IMMEDIATELY INTO RECOVERY ( NEVER REBOOT INTO SYSTEM TELL YOU END STEP3 )
STEP3: a- In TWRP, wipe all except internal storage and microSD
b- power off your phone after the wipe ( if TWRP asked to install SuperSU, refuse )
c- Open in download mode
d- In Odin, Load the pit file of your phone ( search google for one if you doesn't have any ) then load the stock in AP ( mine is COJ5 Brasil VIVO ). Check "Repartition" then Start.
CONGRATS :victory: :victory: ,YOU'RE NOW ON STOCKUnfortunately , Your IMEI now isn't the one your phone really has, so you're not registered on a network. Don't Panic We're going to solve it .
--------------------------------------------------------------------------------------------------
IMEI FixRequirments: *Your phone on stock 5.1.1 // **The same computer // ***The Backup we made above in STEP1 ( its folder in the computer should be named "6.0" )// ****Root Explorer app for your phone// *****Ext4Unpacker tool for ur computer
STEPS:-
STEP1: Root n' TWRP
STEP2: Full Backup in TWRP
STEP3: Move the backup to your computer, rename it "5.1.1" and save it in the same folder you saved the "6.0" Backup ( keep in mind that this backup "5.1.1" is the one compatible with stocks but having invalid IMEI ). Now you have a main folder containing 2 subfolders called "5.1.1" "6.0" which are the 2 backups
STEP4: In this main folder make a new folder "EFS PORT", inside it make 2 new folders "BASE" & "PORT"
STEP5: Using Ext4Unpacker tool, extract "efs1.emmc.win" of the "5.1.1" backup into the "BASE" folder. In the same method, extract "efs1.emmc.win" of the "6.0" backup into the "PORT" folder. Now you have "EFS PORT" folder containing "BASE"&"PORT" each having an EFS.
STEP6: Delete "imei" folder of "BASE" EFS and replace it with the one in "PORT" EFS.
STEP7: Connect your phone to the computer, Copy the "BASE" folder to it and rename it "efs" (small letters NOT CAPITAL).
STEP8:In your phone; install Root Explorer App. and grant its access to hte root (the msgbox SuperSU will send you)
STEP9:Using root explorer, surf to /efs folder of your phone's root directory ( it'll refuse to delete the folder but its components will be deleted ), then replace it with the one you copied from your computer.
STEP10:Reboot the Phone (don't Panic if it bootloops once or twice)
CONGRATS :victory: :victory: . IT'S FIXED NOW AND NETWORK IS ALIVE AGAIN, ENJOY!
PM ME FOR ANY PROBLEM OR QUESTION------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
HmanA6399 said:
Hi Guys....First of all, I'd like to CREDIT:-
1- FR34K-B1B0 to whom I owe the idea. Man, you really powered me on :fingers-crossed: :good:
2- h311sdr0id who created Ext4Unpacker tool.
3- lyriquidperfection
for his great EFS Professional tool.
-------------------------------------------------------------------------------------------------
Many members threaded the problem of Note 4 N910C Exynos version bootlooping when they tried to get back to stock 5.1.1 from a custom CM13 ( or any custom based on 6.0 ). I've been suffering the same problem for 2 weeks.
After tons of internet gigs consumed, cups of coffee drunk, and hours wasted :crying: , I found this solution :victory: ; which I really hope it'll help.
Let's start
Phone Status:*Custom rom based on 6.0 // **rooted // *** busybox installed "smart install" // **** TWRP custom recovery.
Computer Requirements: *Win7 or higher "I'm using Win10" // **Samsung USB Drivers // ***adb-Drivers ( download SDK Tools, install "platform tools " and "Google adb Drivers" Packages. To test it, run the command
Code:
adb drivers
in the folder where the packages are installed ) // **** EFS-Professional
STEPS[/FONT]
STEP1: Through TWRP, make a full backup; then copy this backup ( you should find it in the folder /TWRP/BACKUPS/(some no.s)/(your backup name) in your phone's internal storage ) to your computer, rename the backup "6.0". This backup has an EFS folder which isn't compatible with stocks lower than 6.0, but its IMEI is the right one of your phone (keep this in mind).
STEP2: a- In your phone - rooted and having busybox installed - apply USB-Debugging and grant root access to adb (for CM13 Users, it's a feature you can find in Developer options settings)
b- Connect your phone to the computer, then open EFS Professional ( you should receive a msgbox in your phone; check "Always allow this computer"; then click "OK"or whatever..... )
TIP: if you face a problem opening EFS-Prof., try restarting it, if not solved, make sure that: *You allowed the computer (msgbox of the phone)// **Your device is rooted// ***Your device have busybox Pro fully installed.
c- When EFS-Pro loads, choose the 3rd tab "Samsung tools" , surf to "other tools" and choose "Format EFS Folder" then click "Execute"
TIP: If a msgbox appears saying that permission is denied, it doesn't matter at all, only click "Execute" again, it'll tell you "Can't find mount points" this means it's done
d- REBOOT IMMEDIATELY INTO RECOVERY ( NEVER REBOOT INTO SYSTEM TELL YOU END STEP3 )
STEP3: a- In TWRP, wipe all except internal storage and microSD
b- power off your phone after the wipe ( if TWRP asked to install SuperSU, refuse )
c- Open in download mode
d- In Odin, Load the pit file of your phone ( search google for one if you doesn't have any ) then load the stock in AP ( mine is COJ5 Brasil VIVO ). Check "Repartition" then Start.
CONGRATS :victory: :victory: ,YOU'RE NOW ON STOCKUnfortunately , Your IMEI now isn't the one your phone really has, so you're not registered on a network. Don't Panic We're going to solve it .
--------------------------------------------------------------------------------------------------
IMEI FixRequirments: *Your phone on stock 5.1.1 // **The same computer // ***The Backup we made above in STEP1 ( its folder in the computer should be named "6.0" )// ****Root Explorer app for your phone// *****Ext4Unpacker tool for ur computer
STEPS:-
STEP1: Root n' TWRP
STEP2: Full Backup in TWRP
STEP3: Move the backup to your computer, rename it "5.1.1" and save it in the same folder you saved the "6.0" Backup ( keep in mind that this backup "5.1.1" is the one compatible with stocks but having invalid IMEI ). Now you have a main folder containing 2 subfolders called "5.1.1" "6.0" which are the 2 backups
STEP4: In this main folder make a new folder "EFS PORT", inside it make 2 new folders "BASE" & "PORT"
STEP5: Using Ext4Unpacker tool, extract "efs1.emmc.win" of the "5.1.1" backup into the "BASE" folder. In the same method, extract "efs1.emmc.win" of the "6.0" backup into the "PORT" folder. Now you have "EFS PORT" folder containing "BASE"&"PORT" each having an EFS.
STEP6: Delete "imei" folder of "BASE" EFS and replace it with the one in "PORT" EFS.
STEP7: Connect your phone to the computer, Copy the "BASE" folder to it and rename it "efs" (small letters NOT CAPITAL).
STEP8:In your phone; install Root Explorer App. and grant its access to hte root (the msgbox SuperSU will send you)
STEP9:Using root explorer, surf to /efs folder of your phone's root directory ( it'll refuse to delete the folder but its components will be deleted ), then replace it with the one you copied from your computer.
STEP10:Reboot the Phone (don't Panic if it bootloops once or twice)
CONGRATS :victory: :victory: . IT'S FIXED NOW AND NETWORK IS ALIVE AGAIN, ENJOY!
PM ME FOR ANY PROBLEM OR QUESTION------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
asalamo alaikum akhi , i'm samir from morroco , i have my note 4 exynos , please show me how to extract efs1.emmc.win in my pc , because i;ve used ext4 unpacker and it gives me nothing just an error message ?
Tried this with Note 5 ported rom on dint work.
anaskhan said:
Tried this with Note 5 ported rom on dint work.
Click to expand...
Click to collapse
Only full wipe using twrp - BUT FIRST MAKE A BACKUP - then load the pit file and the stock rom into odin and flash.
Then root, twrp and Flash cm13 .
Then start running the steps
Sent from my HTC Desire 820s dual sim using Tapatalk
Great tutorial, i'm going to do that. Thanks m8 )
Thanks for great tutorial! :good:
my problem is that I didn't make backup of my cm13
now i have stock COJ5 with invalid IMEI
tried to change it to my IMEI with some apps..it did change but still not registered on network
-----
I have backup of my cm13 efs folder using (EFS☆IMEI☆Backup) but i dont know how to restore it.. any help?
hunter! said:
Thanks for great tutorial! :good:
my problem is that I didn't make backup of my cm13
now i have stock COJ5 with invalid IMEI
tried to change it to my IMEI with some apps..it did change but still not registered on network
-----
I have backup of my cm13 efs folder using (EFS☆IMEI☆Backup) but i dont know how to restore it.. any help?
Click to expand...
Click to collapse
so, using this method : bootloop is fixed & you can go back to stock , but not registered on network !??
or bootloop still not fixed??!!
Sent from my SM-N910C using Tapatalk
hunter! said:
Thanks for great tutorial! :good:
my problem is that I didn't make backup of my cm13
now i have stock COJ5 with invalid IMEI
tried to change it to my IMEI with some apps..it did change but still not registered on network
-----
I have backup of my cm13 efs folder using (EFS☆IMEI☆Backup) but i dont know how to restore it.. any help?
Click to expand...
Click to collapse
Tell me more about the backup u have ....... what's the extension of ur efs backup folder ( it's the name written after the dot like .apk , .exe , ..... )
Sent from my HTC Desire 820s dual sim using Tapatalk
AlStarsKyz said:
Great tutorial, i'm going to do that. Thanks m8 )
Click to expand...
Click to collapse
You are welcome
Good luck[emoji6]
Sent from my HTC Desire 820s dual sim using Tapatalk
Hello @HmanA6399, thanks for this in-depth tutorial, however I cannot get it to work. I've tried following the steps precisely two times now with same result, here's what happens after I do Step 3 (after Odin flash): 1. Phone reboots after download mode into GALAXY NOTE 4 splash screen. 2. Android in the middle and 'Installing System Update' goes to half, then it stops and says 'Erasing...'. 3. Phone reboots into GALAXY NOTE 4 splash screen, boot loops into the same screen once again 5. Stock Samsung recovery comes up, when I try to reboot same thing happens and I end up in recovery. In recovery it says 'dm-verity verification failed...' 'Need to check DRK first...'.
Any thoughts?
Thank you again.
EDIT: Nevermind! I tried flashing again, but I also included stock COJ5 BL in Odin as well, I'm back to stock 5.1.1 FINALLY!!! Thank you for your tutorial, you saved me a lot of nerves on unstable CM13.
ANOTHER EDIT... : I restored my imei from CM13, but still Emergency Calls Only. What to dooo?
Hi bro, my device is N910H and i want to flash it with COJ5 Brazil N910C same as you. Did it will work or i need flash with COJ4 for N910H ? Because N910C and N910H it's EXYNOS but i never flash with different type
HmanA6399 said:
Tell me more about the backup u have ....... what's the extension of ur efs backup folder ( it's the name written after the dot like .apk , .exe , ..... )
Sent from my HTC Desire 820s dual sim using Tapatalk
Click to expand...
Click to collapse
attached...
ahmd gomaa said:
so, using this method : bootloop is fixed & you can go back to stock , but not registered on network !??
or bootloop still not fixed??!!
Sent from my SM-N910C using Tapatalk
Click to expand...
Click to collapse
I didn't use this method.. but bootloop is fixed & i can go back to stock , but not registered on network
Peace..... use the same tool I posted to extract .img files ( efs_backup_.....img / m9kefs1-2-3_backup_......img )
Extract them into one folder " PORT "
And follow the tutorial .... good luck
Sent from my HTC Desire 820s dual sim using Tapatalk
P.s. if you can't ... send me them
[email protected]
This is my email address[emoji1]
quadlt said:
Hello @HmanA6399, thanks for this in-depth tutorial, however I cannot get it to work. I've tried following the steps precisely two times now with same result, here's what happens after I do Step 3 (after Odin flash): 1. Phone reboots after download mode into GALAXY NOTE 4 splash screen. 2. Android in the middle and 'Installing System Update' goes to half, then it stops and says 'Erasing...'. 3. Phone reboots into GALAXY NOTE 4 splash screen, boot loops into the same screen once again 5. Stock Samsung recovery comes up, when I try to reboot same thing happens and I end up in recovery. In recovery it says 'dm-verity verification failed...' 'Need to check DRK first...'.
Any thoughts?
Thank you again.
EDIT: Nevermind! I tried flashing again, but I also included stock COJ5 BL in Odin as well, I'm back to stock 5.1.1 FINALLY!!! Thank you for your tutorial, you saved me a lot of nerves on unstable CM13.
ANOTHER EDIT... : I restored my imei from CM13, but still Emergency Calls Only. What to dooo?
Click to expand...
Click to collapse
How did u restore it ?
Sent from my HTC Desire 820s dual sim using Tapatalk
HmanA6399 said:
How did u restore it ?
Sent from my HTC Desire 820s dual sim using Tapatalk
Click to expand...
Click to collapse
I restored it following your steps, but that didn't work.
HOWEVER If somebody has an old EFS Backup from HERE or another tool of your choice that has efs.img, I used THIS app to restore the old efs.img, rebooted and soon enough I had the little LTE badge up top. All solved and rocking 5.1.1 once again!
I've put the ext4 unpacked amoung the other efs files , and it gives me the same result , please show me how to extract this efs1.emmc.win file
quadlt said:
I restored it following your steps, but that didn't work.
HOWEVER If somebody has an old EFS Backup from HERE or another tool of your choice that has efs.img, I used THIS app to restore the old efs.img, rebooted and soon enough I had the little LTE badge up top. All solved and rocking 5.1.1 once again!
Click to expand...
Click to collapse
Thx for info.
The app is really cool[emoji6]
Sent from my HTC Desire 820s dual sim using Tapatalk
Ok...
followed the steps but didn't work
tried to restore efs using 'Partitions Backup & Restore' app....it works for 10 seconds and then not registered on network again!
any help plz!
HmanA6399 said:
Hi Guys....First of all, I'd like to CREDIT:-
1- FR34K-B1B0 to whom I owe the idea. Man, you really powered me on :fingers-crossed: :good:
2- h311sdr0id who created Ext4Unpacker tool.
3- lyriquidperfection
for his great EFS Professional tool.
-------------------------------------------------------------------------------------------------
Many members threaded the problem of Note 4 N910C Exynos version bootlooping when they tried to get back to stock 5.1.1 from a custom CM13 ( or any custom based on 6.0 ). I've been suffering the same problem for 2 weeks.
After tons of internet gigs consumed, cups of coffee drunk, and hours wasted :crying: , I found this solution :victory: ; which I really hope it'll help.
Let's start
Phone Status:*Custom rom based on 6.0 // **rooted // *** busybox installed "smart install" // **** TWRP custom recovery.
Computer Requirements: *Win7 or higher "I'm using Win10" // **Samsung USB Drivers // ***adb-Drivers ( download SDK Tools, install "platform tools " and "Google adb Drivers" Packages. To test it, run the command
Code:
adb drivers
in the folder where the packages are installed ) // **** EFS-Professional
STEPS[/FONT]
STEP1: Through TWRP, make a full backup; then copy this backup ( you should find it in the folder /TWRP/BACKUPS/(some no.s)/(your backup name) in your phone's internal storage ) to your computer, rename the backup "6.0". This backup has an EFS folder which isn't compatible with stocks lower than 6.0, but its IMEI is the right one of your phone (keep this in mind).
STEP2: a- In your phone - rooted and having busybox installed - apply USB-Debugging and grant root access to adb (for CM13 Users, it's a feature you can find in Developer options settings)
b- Connect your phone to the computer, then open EFS Professional ( you should receive a msgbox in your phone; check "Always allow this computer"; then click "OK"or whatever..... )
TIP: if you face a problem opening EFS-Prof., try restarting it, if not solved, make sure that: *You allowed the computer (msgbox of the phone)// **Your device is rooted// ***Your device have busybox Pro fully installed.
c- When EFS-Pro loads, choose the 3rd tab "Samsung tools" , surf to "other tools" and choose "Format EFS Folder" then click "Execute"
TIP: If a msgbox appears saying that permission is denied, it doesn't matter at all, only click "Execute" again, it'll tell you "Can't find mount points" this means it's done
d- REBOOT IMMEDIATELY INTO RECOVERY ( NEVER REBOOT INTO SYSTEM TELL YOU END STEP3 )
STEP3: a- In TWRP, wipe all except internal storage and microSD
b- power off your phone after the wipe ( if TWRP asked to install SuperSU, refuse )
c- Open in download mode
d- In Odin, Load the pit file of your phone ( search google for one if you doesn't have any ) then load the stock in AP ( mine is COJ5 Brasil VIVO ). Check "Repartition" then Start.
CONGRATS :victory: :victory: ,YOU'RE NOW ON STOCKUnfortunately , Your IMEI now isn't the one your phone really has, so you're not registered on a network. Don't Panic We're going to solve it .
--------------------------------------------------------------------------------------------------
IMEI FixRequirments: *Your phone on stock 5.1.1 // **The same computer // ***The Backup we made above in STEP1 ( its folder in the computer should be named "6.0" )// ****Root Explorer app for your phone// *****Ext4Unpacker tool for ur computer
STEPS:-
STEP1: Root n' TWRP
STEP2: Full Backup in TWRP
STEP3: Move the backup to your computer, rename it "5.1.1" and save it in the same folder you saved the "6.0" Backup ( keep in mind that this backup "5.1.1" is the one compatible with stocks but having invalid IMEI ). Now you have a main folder containing 2 subfolders called "5.1.1" "6.0" which are the 2 backups
STEP4: In this main folder make a new folder "EFS PORT", inside it make 2 new folders "BASE" & "PORT"
STEP5: Using Ext4Unpacker tool, extract "efs1.emmc.win" of the "5.1.1" backup into the "BASE" folder. In the same method, extract "efs1.emmc.win" of the "6.0" backup into the "PORT" folder. Now you have "EFS PORT" folder containing "BASE"&"PORT" each having an EFS.
STEP6: Delete "imei" folder of "BASE" EFS and replace it with the one in "PORT" EFS.
STEP7: Connect your phone to the computer, Copy the "BASE" folder to it and rename it "efs" (small letters NOT CAPITAL).
STEP8:In your phone; install Root Explorer App. and grant its access to hte root (the msgbox SuperSU will send you)
STEP9:Using root explorer, surf to /efs folder of your phone's root directory ( it'll refuse to delete the folder but its components will be deleted ), then replace it with the one you copied from your computer.
STEP10:Reboot the Phone (don't Panic if it bootloops once or twice)
CONGRATS :victory: :victory: . IT'S FIXED NOW AND NETWORK IS ALIVE AGAIN, ENJOY!
PM ME FOR ANY PROBLEM OR QUESTION------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
Thanks brother. .........
When my note succefuly open with stock I felt as I fly.......
You are witty masterful guy..........☺☺☺
---------- Post added at 12:11 PM ---------- Previous post was at 12:10 PM ----------
HmanA6399 said:
Hi Guys....First of all, I'd like to CREDIT:-
1- FR34K-B1B0 to whom I owe the idea. Man, you really powered me on :fingers-crossed: :good:
2- h311sdr0id who created Ext4Unpacker tool.
3- lyriquidperfection
for his great EFS Professional tool.
-------------------------------------------------------------------------------------------------
Many members threaded the problem of Note 4 N910C Exynos version bootlooping when they tried to get back to stock 5.1.1 from a custom CM13 ( or any custom based on 6.0 ). I've been suffering the same problem for 2 weeks.
After tons of internet gigs consumed, cups of coffee drunk, and hours wasted :crying: , I found this solution :victory: ; which I really hope it'll help.
Let's start
Phone Status:*Custom rom based on 6.0 // **rooted // *** busybox installed "smart install" // **** TWRP custom recovery.
Computer Requirements: *Win7 or higher "I'm using Win10" // **Samsung USB Drivers // ***adb-Drivers ( download SDK Tools, install "platform tools " and "Google adb Drivers" Packages. To test it, run the command
Code:
adb drivers
in the folder where the packages are installed ) // **** EFS-Professional
STEPS[/FONT]
STEP1: Through TWRP, make a full backup; then copy this backup ( you should find it in the folder /TWRP/BACKUPS/(some no.s)/(your backup name) in your phone's internal storage ) to your computer, rename the backup "6.0". This backup has an EFS folder which isn't compatible with stocks lower than 6.0, but its IMEI is the right one of your phone (keep this in mind).
STEP2: a- In your phone - rooted and having busybox installed - apply USB-Debugging and grant root access to adb (for CM13 Users, it's a feature you can find in Developer options settings)
b- Connect your phone to the computer, then open EFS Professional ( you should receive a msgbox in your phone; check "Always allow this computer"; then click "OK"or whatever..... )
TIP: if you face a problem opening EFS-Prof., try restarting it, if not solved, make sure that: *You allowed the computer (msgbox of the phone)// **Your device is rooted// ***Your device have busybox Pro fully installed.
c- When EFS-Pro loads, choose the 3rd tab "Samsung tools" , surf to "other tools" and choose "Format EFS Folder" then click "Execute"
TIP: If a msgbox appears saying that permission is denied, it doesn't matter at all, only click "Execute" again, it'll tell you "Can't find mount points" this means it's done
d- REBOOT IMMEDIATELY INTO RECOVERY ( NEVER REBOOT INTO SYSTEM TELL YOU END STEP3 )
STEP3: a- In TWRP, wipe all except internal storage and microSD
b- power off your phone after the wipe ( if TWRP asked to install SuperSU, refuse )
c- Open in download mode
d- In Odin, Load the pit file of your phone ( search google for one if you doesn't have any ) then load the stock in AP ( mine is COJ5 Brasil VIVO ). Check "Repartition" then Start.
CONGRATS :victory: :victory: ,YOU'RE NOW ON STOCKUnfortunately , Your IMEI now isn't the one your phone really has, so you're not registered on a network. Don't Panic We're going to solve it .
--------------------------------------------------------------------------------------------------
IMEI FixRequirments: *Your phone on stock 5.1.1 // **The same computer // ***The Backup we made above in STEP1 ( its folder in the computer should be named "6.0" )// ****Root Explorer app for your phone// *****Ext4Unpacker tool for ur computer
STEPS:-
STEP1: Root n' TWRP
STEP2: Full Backup in TWRP
STEP3: Move the backup to your computer, rename it "5.1.1" and save it in the same folder you saved the "6.0" Backup ( keep in mind that this backup "5.1.1" is the one compatible with stocks but having invalid IMEI ). Now you have a main folder containing 2 subfolders called "5.1.1" "6.0" which are the 2 backups
STEP4: In this main folder make a new folder "EFS PORT", inside it make 2 new folders "BASE" & "PORT"
STEP5: Using Ext4Unpacker tool, extract "efs1.emmc.win" of the "5.1.1" backup into the "BASE" folder. In the same method, extract "efs1.emmc.win" of the "6.0" backup into the "PORT" folder. Now you have "EFS PORT" folder containing "BASE"&"PORT" each having an EFS.
STEP6: Delete "imei" folder of "BASE" EFS and replace it with the one in "PORT" EFS.
STEP7: Connect your phone to the computer, Copy the "BASE" folder to it and rename it "efs" (small letters NOT CAPITAL).
STEP8:In your phone; install Root Explorer App. and grant its access to hte root (the msgbox SuperSU will send you)
STEP9:Using root explorer, surf to /efs folder of your phone's root directory ( it'll refuse to delete the folder but its components will be deleted ), then replace it with the one you copied from your computer.
STEP10:Reboot the Phone (don't Panic if it bootloops once or twice)
CONGRATS :victory: :victory: . IT'S FIXED NOW AND NETWORK IS ALIVE AGAIN, ENJOY!
PM ME FOR ANY PROBLEM OR QUESTION------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
Thanks brother. .........
When my note succefuly open with stock I felt as I fly.......
You are witty masterful guy..........☺☺☺
You will be programmer. ......
Good by bro.
---------- Post added at 12:12 PM ---------- Previous post was at 12:11 PM ----------
HmanA6399 said:
Hi Guys....First of all, I'd like to CREDIT:-
1- FR34K-B1B0 to whom I owe the idea. Man, you really powered me on :fingers-crossed: :good:
2- h311sdr0id who created Ext4Unpacker tool.
3- lyriquidperfection
for his great EFS Professional tool.
-------------------------------------------------------------------------------------------------
Many members threaded the problem of Note 4 N910C Exynos version bootlooping when they tried to get back to stock 5.1.1 from a custom CM13 ( or any custom based on 6.0 ). I've been suffering the same problem for 2 weeks.
After tons of internet gigs consumed, cups of coffee drunk, and hours wasted :crying: , I found this solution :victory: ; which I really hope it'll help.
Let's start
Phone Status:*Custom rom based on 6.0 // **rooted // *** busybox installed "smart install" // **** TWRP custom recovery.
Computer Requirements: *Win7 or higher "I'm using Win10" // **Samsung USB Drivers // ***adb-Drivers ( download SDK Tools, install "platform tools " and "Google adb Drivers" Packages. To test it, run the command
Code:
adb drivers
in the folder where the packages are installed ) // **** EFS-Professional
STEPS[/FONT]
STEP1: Through TWRP, make a full backup; then copy this backup ( you should find it in the folder /TWRP/BACKUPS/(some no.s)/(your backup name) in your phone's internal storage ) to your computer, rename the backup "6.0". This backup has an EFS folder which isn't compatible with stocks lower than 6.0, but its IMEI is the right one of your phone (keep this in mind).
STEP2: a- In your phone - rooted and having busybox installed - apply USB-Debugging and grant root access to adb (for CM13 Users, it's a feature you can find in Developer options settings)
b- Connect your phone to the computer, then open EFS Professional ( you should receive a msgbox in your phone; check "Always allow this computer"; then click "OK"or whatever..... )
TIP: if you face a problem opening EFS-Prof., try restarting it, if not solved, make sure that: *You allowed the computer (msgbox of the phone)// **Your device is rooted// ***Your device have busybox Pro fully installed.
c- When EFS-Pro loads, choose the 3rd tab "Samsung tools" , surf to "other tools" and choose "Format EFS Folder" then click "Execute"
TIP: If a msgbox appears saying that permission is denied, it doesn't matter at all, only click "Execute" again, it'll tell you "Can't find mount points" this means it's done
d- REBOOT IMMEDIATELY INTO RECOVERY ( NEVER REBOOT INTO SYSTEM TELL YOU END STEP3 )
STEP3: a- In TWRP, wipe all except internal storage and microSD
b- power off your phone after the wipe ( if TWRP asked to install SuperSU, refuse )
c- Open in download mode
d- In Odin, Load the pit file of your phone ( search google for one if you doesn't have any ) then load the stock in AP ( mine is COJ5 Brasil VIVO ). Check "Repartition" then Start.
CONGRATS :victory: :victory: ,YOU'RE NOW ON STOCKUnfortunately , Your IMEI now isn't the one your phone really has, so you're not registered on a network. Don't Panic We're going to solve it .
--------------------------------------------------------------------------------------------------
IMEI FixRequirments: *Your phone on stock 5.1.1 // **The same computer // ***The Backup we made above in STEP1 ( its folder in the computer should be named "6.0" )// ****Root Explorer app for your phone// *****Ext4Unpacker tool for ur computer
STEPS:-
STEP1: Root n' TWRP
STEP2: Full Backup in TWRP
STEP3: Move the backup to your computer, rename it "5.1.1" and save it in the same folder you saved the "6.0" Backup ( keep in mind that this backup "5.1.1" is the one compatible with stocks but having invalid IMEI ). Now you have a main folder containing 2 subfolders called "5.1.1" "6.0" which are the 2 backups
STEP4: In this main folder make a new folder "EFS PORT", inside it make 2 new folders "BASE" & "PORT"
STEP5: Using Ext4Unpacker tool, extract "efs1.emmc.win" of the "5.1.1" backup into the "BASE" folder. In the same method, extract "efs1.emmc.win" of the "6.0" backup into the "PORT" folder. Now you have "EFS PORT" folder containing "BASE"&"PORT" each having an EFS.
STEP6: Delete "imei" folder of "BASE" EFS and replace it with the one in "PORT" EFS.
STEP7: Connect your phone to the computer, Copy the "BASE" folder to it and rename it "efs" (small letters NOT CAPITAL).
STEP8:In your phone; install Root Explorer App. and grant its access to hte root (the msgbox SuperSU will send you)
STEP9:Using root explorer, surf to /efs folder of your phone's root directory ( it'll refuse to delete the folder but its components will be deleted ), then replace it with the one you copied from your computer.
STEP10:Reboot the Phone (don't Panic if it bootloops once or twice)
CONGRATS :victory: :victory: . IT'S FIXED NOW AND NETWORK IS ALIVE AGAIN, ENJOY!
PM ME FOR ANY PROBLEM OR QUESTION------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
Thanks brother. .........
When my note succefuly open with stock I felt as I fly.......
You are witty masterful guy..........
You will be programmer. ......
Salam bro.
I have two N4s with broken screens, one of which has USB debugging enabled etc.
I created a TWRP backup of boot, system & data on the one with USB enabled and transferred it over to the other one.
I now can't restore that backup. I have to use TWRP's open recovery script in an ADB shell because the screens are broken. I am using:
Code:
adb shell twrp restore /data/media/0/TWRP/BACKUPS/"serial no"/
but which initially works, then says "no partitions selected for restore".
If I put "SDBM" after the path, it says "setting restore options: SDBM" then the same thing - "no partitions selected for restore".
If I put "SDBM" after "restore" i.e. before the path name it says "Restoring SDBM... Unable to locate backup 'SDBM'"
I can't find any help via google and I'm stuck now - how can I restore a backup with adb shell twrp?
mrmrchoice said:
I have two N4s with broken screens, one of which has USB debugging enabled etc.
I created a TWRP backup of boot, system & data on the one with USB enabled and transferred it over to the other one.
I now can't restore that backup. I have to use TWRP's open recovery script in an ADB shell because the screens are broken. I am using:
Code:
adb shell twrp restore /data/media/0/TWRP/BACKUPS/"serial no"/
but which initially works, then says "no partitions selected for restore".
If I put "SDBM" after the path, it says "setting restore options: SDBM" then the same thing - "no partitions selected for restore".
If I put "SDBM" after "restore" i.e. before the path name it says "Restoring SDBM... Unable to locate backup 'SDBM'"
I can't find any help via google and I'm stuck now - how can I restore a backup with adb shell twrp?
Click to expand...
Click to collapse
From what you wrote, I see that you provided the path to the backup directory instead of to the specific backup directory.
Your path is too short because it does not contain the name of the directory that was created during the backup.
If possible, always try to paste a significant piece of text from the terminal where you performed the action, it really makes it easier to find a solution.
ze7zez said:
From what you wrote, I see that you provided the path to the backup directory instead of to the specific backup directory.
Your path is too short because it does not contain the name of the directory that was created during the backup.
If possible, always try to paste a significant piece of text from the terminal where you performed the action, it really makes it easier to find a solution.
Click to expand...
Click to collapse
Hi, thanks, I got there not long after I posted this HOWEVER adding the specific backup directory now gives me an error about digest verification (I didn't generate an MD5 hash when I made the backup). This is when trying to restore using the same flag that I used to skip MD5 generation when I made the backup.
It asks me to deselect digest verification but I can't do that on the touch screen (as it's broken) and don't know if it's possible to do this via abd?
Thanks!