no phone function on my Galaxy S - Galaxy S I9000 General

My details are as follows:
pda i9000ddjg4
phone i9000ddjg4
I downloaded Kalpik and Doc rom and flashed with clockworkmod. I was not satisfied with it and moreover it changed my product code. In Kies I used to get message that my firmware cannot be upgraded. Therefore I copied two files from my original backed up efs folder to the new Efs folder. The files were copied using busybox and terminal emulator. The files were nv_data.bin and nv_data.bin.md5. I got the original product code after rebooting but instead of the phone operator symbol now I get a blue circle . Again I restored, using rom manager, my phone from a previous backup(from my original firmware). But again the same problem. I used Odin and flashed the ddjg4 firmware. That also has not helped. Can somebody guide me how to get back the phone fuction?

Check this thread out:
http://forum.xda-developers.com/showthread.php?t=780509
**IF YOUR SIMCARD DOESN'T WORK AFTER THIS, EXECUTE THE FOLLOWING**
- adb shell
- su
- busybox chown 1001:1001 /efs/nv_data.bin
- reboot
You can also do this from the Terminal Emulator if you don't have ADB on your PC! Like this:
-su
-chown 1001:1001 /efs/nv_data.bin
-reboot
I hope it's easy to follow my steps, it works guaranteed.
Click to expand...
Click to collapse

It worked a charm. My Simcard now works. Thanks a million.

Oh I did not see that when I lost phone functionality when I did it.
Can I use this method to trick KIES?
Although the regedit hack would be easier I guess.

RambJoe said:
Oh I did not see that when I lost phone functionality when I did it.
Can I use this method to trick KIES?
Although the regedit hack would be easier I guess.
Click to expand...
Click to collapse
The hack only tricks Kies, your phone still has the wrong productcode after flashing. Mine did at least. Went from european JM2 to JM8 and then to scandinavian JP6. Had some troubles with it so used the registry hack to go back to the official european JM2. It worked, but in the registry it still listed as a scandinavian JM2. Don't know what the difference is (except for different Samsung Apps).

Related

If u have a hard time trying to unlock your phone after flashing JPC rom

for those of u having a very very hard time trying to unlock the phone after flashing the JPC rom , u must do this :
7. My Phone asks me for a Unlock Code. Product Code has changed to KOR. What to do?
- Your Phone have to be rooted! Busybox is required!
- Start->Run-> cmd
- Change to your SDK\tools Directory e.g cd C:\Program Files (x86)\Android SDK\tools
- adb shell
- su
- cd /efs
- ls -al
If now nv_data.bak AND nv_data.bak.md5 are displayed, do the next few steps marked with (a)
If now .nv_data.bak AND .nv_data.bak.md5 are displayed (dot before filenames), do the next few steps marked with (b).
(a)- mv nv_data.bin nv_data.jpc
(a)- mv nv_data.bin.md5 nv_data.jpc.md5
(a)- mv nv_data.bak nv_data.bin
(a)- mv nv_data.bak.md5 nv_data.bin.md5
(a)- reboot
(b)- mv nv_data.bin nv_data.jpc
(b)- mv nv_data.bin.md5 nv_data.jpc.md5
(b)- mv .nv_data.bak nv_data.bin
(b)- mv .nv_data.bak.md5 nv_data.bin.md5
(b)- reboot
Now your Phone shouldn´t ask for a Code.
after that u can unlock ur phone with the methods shown in this thread . even the unlock android apk works ! very good job developers ty. BAD BAD samsung setting us such a trap.
For me this method didn't work. following exact steps in (b), still asking Network Code, 00000000 was the extracted code but didn't work though.
So after 2 days of struggling this is what I did:
Note that some users warned that if the bak files are corrupted the system will recreate empty files, probably losing IMEI, but this was not my case
1. Flash by Odin to JM7 (I don't think the version matters as long is 2.1)
2. at this time Product code change back from KOR to original ORO, but still asking code
3. root
4. moving back /efs files active to bak, the system will recreate new ones due to moving, so no more active files
mv nv_data.bin .nv_data.bak
mv nv_data.bin.md5 .nv_data.bak.md5
at this time I can see a new nv_data.bin with a smaller size
5. reboot
now working, not asking code
Thanks for the Thread... Might just need it in a few hours
adi_g_s said:
For me this method didn't work. following exact steps in (b), still asking Network Code, 00000000 was the extracted code but didn't work though.
So after 2 days of struggling this is what I did:
Note that some users warned that if the bak files are corrupted the system will recreate empty files, probably losing IMEI, but this was not my case
1. Flash by Odin to JM7 (I don't think the version matters as long is 2.1)
2. at this time Product code change back from KOR to original ORO, but still asking code
3. root
4. moving back /efs files active to bak, the system will recreate new ones due to moving, so no more active files
mv nv_data.bin .nv_data.bak
mv nv_data.bin.md5 .nv_data.bak.md5
at this time I can see a new nv_data.bin with a smaller size
5. reboot
now working, not asking code
Click to expand...
Click to collapse
and did you manage to get the JPC back and unlocked then? I have managed to fix the SIM Network Unlock code problem in a similar way, but using a MoDaCo modded froyo ROM, based on JP3. Now I am considering getting back to JPC, because I saw some nice things in there, but afraid I might get into the same problem. How can we fix this problem and STILL be on JPC?
NOTE: I have tried to use the .apk to get the unlock code now in JP3 rom and with no network unlock and the result is:
Unlock code: NULL
Unfreeze code: NULL
Probably that means that my sgs is unlocked, but how can we find the unlock code, so we can use it in JPC after flash?
ionutz6 said:
and did you manage to get the JPC back and unlocked then? I have managed to fix the SIM Network Unlock code problem in a similar way, but using a MoDaCo modded froyo ROM, based on JP3. Now I am considering getting back to JPC, because I saw some nice things in there, but afraid I might get into the same problem. How can we fix this problem and STILL be on JPC?
Click to expand...
Click to collapse
I think you can use JPC as long as you keep it rooted. If it gets locked, you can do the above procedure (adb shell) and restore the nv_data files
If you need to know how to flash it already rooted, check the "JPC root inside" thread or the "Doc's RomMod JPC" thread. I'm going to test this myself tonight or tomorrow
Cheers m8s
Phk
Phk said:
I think you can use JPC as long as you keep it rooted. If it gets locked, you can do the above procedure (adb shell) and restore the nv_data files
If you need to know how to flash it already rooted, check the "JPC root inside" thread or the "Doc's RomMod JPC" thread. I'm going to test this myself tonight or tomorrow
Cheers m8s
Phk
Click to expand...
Click to collapse
I have tried pretty much ALL things found here in XDA related to JPC last night, in the 10-hour period when I was struggling to bring my sgs back to life. I have upgraded to JPC, rooted it, tried to use several methods to find the unlock code, tried the FAQ#7 from the HOWTO thread, did 1000 other things, nothing worked, Unlock code still present. Perhaps I missed some steps although I don;t think so. I've also downgraded to 2.1 JM6 and tried to get the unlock code here, no go. Still SIM Unlock Code required. Finally I have solved it by upgrading it to a froyo modded rom from modaco, already rooted and then applying the FAQ#7 instructions. Now I am in froyo JP3 (the modded rom from modaco) and pretty scared to try anything else, although I would very much like to get to JPC, since I saw some pretty nice enhancements.
Any thoughts based on this painful story?
adi_g_s said:
For me this method didn't work. following exact steps in (b), still asking Network Code, 00000000 was the extracted code but didn't work though.
So after 2 days of struggling this is what I did:
Note that some users warned that if the bak files are corrupted the system will recreate empty files, probably losing IMEI, but this was not my case
1. Flash by Odin to JM7 (I don't think the version matters as long is 2.1)
2. at this time Product code change back from KOR to original ORO, but still asking code
3. root
4. moving back /efs files active to bak, the system will recreate new ones due to moving, so no more active files
mv nv_data.bin .nv_data.bak
mv nv_data.bin.md5 .nv_data.bak.md5
at this time I can see a new nv_data.bin with a smaller size
5. reboot
now working, not asking code
Click to expand...
Click to collapse
so should i understand that you are now on JM7? How do you get back to JPC?
ionutz6 said:
and did you manage to get the JPC back and unlocked then? I have managed to fix the SIM Network Unlock code problem in a similar way, but using a MoDaCo modded froyo ROM, based on JP3. Now I am considering getting back to JPC, because I saw some nice things in there, but afraid I might get into the same problem. How can we fix this problem and STILL be on JPC??
Click to expand...
Click to collapse
yes now i am on jpc ,and if it decides to ask for a code i have the codes now.
ionutz6 said:
so should i understand that you are now on JM7? How do you get back to JPC?
Click to expand...
Click to collapse
yes I'm on JM7, now the unlock.apk gives me Unlock Code:NULL
I'm hoping that my phone is unlocked now, so Froyo will not ask the code anymore
but IMEI was rewritten by with value 004999... and I have trouble with Market, cannot download.
how to recover my IMEI now?
Many many many thanks
adi_g_s said:
For me this method didn't work. following exact steps in (b), still asking Network Code, 00000000 was the extracted code but didn't work though.
So after 2 days of struggling this is what I did:
Note that some users warned that if the bak files are corrupted the system will recreate empty files, probably losing IMEI, but this was not my case
1. Flash by Odin to JM7 (I don't think the version matters as long is 2.1)
2. at this time Product code change back from KOR to original ORO, but still asking code
3. root
4. moving back /efs files active to bak, the system will recreate new ones due to moving, so no more active files
mv nv_data.bin .nv_data.bak
mv nv_data.bin.md5 .nv_data.bak.md5
at this time I can see a new nv_data.bin with a smaller size
5. reboot
now working, not asking code
Click to expand...
Click to collapse
Finaly I have my phone back. just had to do something else.
I have to edit the file efs/imei/mps_code.dat and change de "KOR" to "TMN". Then I rename the files as mentioned, and my phone came to life.
adi_g_s you're a hero.
adi_g_s said:
yes I'm on JM7, now the unlock.apk gives me Unlock Code:NULL
I'm hoping that my phone is unlocked now, so Froyo will not ask the code anymore
but IMEI was rewritten by with value 004999... and I have trouble with Market, cannot download.
how to recover my IMEI now?
Click to expand...
Click to collapse
I have the exact same behaviour, with Unlock code: NULL, IMEi starting with 004999.. etc. The only thing is that download from market is working ok.
would you care to upgrade now to JPC and see if it requests the unlock code again? I don;t believe that the fact that it looks unlocked now will mean after installing JPC you will have the same condition. Mine was unlocked before trying JPC, as far as I know.
man, i am confused...
I want to give the method by adi_g_s a try but im afraid if I reflash back to JPC it might forever lock my phone.. the unlock APK also sees it as null/null. Right now im with JPC and its unlocked..
adi_g_s said:
For me this method didn't work. following exact steps in (b), still asking Network Code, 00000000 was the extracted code but didn't work though.
So after 2 days of struggling this is what I did:
Note that some users warned that if the bak files are corrupted the system will recreate empty files, probably losing IMEI, but this was not my case
1. Flash by Odin to JM7 (I don't think the version matters as long is 2.1)
2. at this time Product code change back from KOR to original ORO, but still asking code
3. root
4. moving back /efs files active to bak, the system will recreate new ones due to moving, so no more active files
mv nv_data.bin .nv_data.bak
mv nv_data.bin.md5 .nv_data.bak.md5
at this time I can see a new nv_data.bin with a smaller size
5. reboot
now working, not asking code
Click to expand...
Click to collapse
If i flash back to 2.1 and I still get the KOR product code.. I wont be doing the other extra steps right ?
and If i flash back to JPC, should I expect my phone to be asking for an unlock code again ?
EDIT:
and I made a backup of my:
nv_data.bak
nv_data.bin
nv_data.bin.md5
nv_data.jpc
nv_data.jpc.md5
all of these are from POST JPC, so I guess im ready to screw around and flash to JM7 and see if i can get my product code back and if not I can just relfash to JPC again and restore these files so it wont be asking for an unlock code anymore right ?
adi_g_s said:
yes I'm on JM7, now the unlock.apk gives me Unlock Code:NULL
I'm hoping that my phone is unlocked now, so Froyo will not ask the code anymore
but IMEI was rewritten by with value 004999... and I have trouble with Market, cannot download.
how to recover my IMEI now?
Click to expand...
Click to collapse
There is a file in /efs/imei/ folder that contains the imei. if you have a original box perhaps you find there imei written, and that way you can try editing that file and place your original IMEI.

Step by Step for Rooting Rogers Captivate (I896)

Hey Guys
So one of the biggest questions I have seen in the last couple weeks since the Rogers captivate was released is how to root. I figured I would write a nice tutorial for everyone to make it easier!
Method 1: SuperOneClick
This is the easiest way, however most people have not been able to achieve root using this. Try this first if no luck move to method 2. Instructions on how to root using SuperOneClick can be found here
Method 2: Manual Root using ADB and Terminal
This one takes more time and not as easy to do as you have to do everything manually. But haven't heard of any problems with it yet
Step 1: Install <PDANet> Drivers. Just download the file and install. Select Samsung drivers. No need to actually install PDAnet on the Captivate you just need the drivers from the install. Follow the instructions with the installer to properly install the drivers.
Step 2: Download <Andriod SDK>.
- Extract the Android SDK .Zip file to C:\AndroidSDK (this should name the new folder created AndroidSDK in the C directory.
- Go to your start menu and search cmd or click run and type in cmd to open command prompt
- Type the following into command prompt, hitting enter at the end of each line
cd C:\AndroidSKD\Tools
adb devices
- You should see a serial number pop up. This is the serial number of your phone. This means ADB is set up
Step 3: Download <RageagainsttheCage Rooting Files>
- Extract them to the c:\AndroidSDK\tools\ folder. HAS TO BE IN THIS FOLDER FOR THE FOLLOWING COMMANDS TO WORK
Step 4: Unplug phone if it is plugged in. Then, on the phone, go to Settings > Applications > Development and make sure USB Debugging is Checked ON.
Step 5: Plug phone back in to computer. Make sure SD are not mounted
Step 6: Reopen Command prompt if not open. In the command prompt enter the following, pressing enter at the end of each line
cd c:\androidsdk\tools\
adb devices
adb push Superuser.apk /sdcard/
adb push su /sdcard/
adb push rageagainstthecage-arm5.bin /data/local/tmp/
adb shell chmod 0755 /data/local/tmp/rageagainstthecage-arm5.bin
Step 7: On the phone, go to Marketplace and download Terminal Emulator
Step 8: Leaving the phone plugged in, open the Terminal Emulator on the phone. Type the following, pressing enter at the end of each line
cd /data/local/tmp
./rageagainstthecage-arm5.bin
Step 9: WAIT. It will take a full minutes for the rage root to install. When finished you will see "Forked Childs". DO NOT DO ANYTHING TILL YOU SEE THIS. Terminal will allow you to type as it goes back to $ while it is installing BUUT DO NOT DO ANYTHING JUST WAIT(Cannot stress this enough)
Step 10: once "Forked Childs" appears, exit the Terminal App, and then reopen it. Instead of $ you should now see #. If not redo Step 7. Otherwise continue.
Step 11: Type the following hitting enter at the end
cat /proc/mounts
This should bring up a list (Easiest to view in landscape mode. Look for the following
/dev/block/XXXXXXXXXX /system YYYY ro 0 0 (the XXXXXXXXX part should be different depending on which device you have. The YYYY part will either be; ext2, ext3 or yaffs2 or something similar. )
My YYYY was rtf , not sure if it will be the same for everyone (though i assume it is)
Step 12: Now in the terminal window, using the info from above, enter the following, hitting enter at the end of each line (Be sure to enter spaces where needed as below)
mount -o rw,remount -t YYYY /dev/block/XXXXXXXXXX /system
cat /sdcard/Superuser.apk > /system/app/Superuser.apk
cat /sdcard/su > /system/bin/su
chmod 4755 /system/bin/su
mount -o ro,remount -t YYYY /dev/block/XXXXXXXXXX /system
exit
Step 13: Close terminal window if still open. Check your app drawer and, assuming everything was completed properly, you should see Superuser. If not redo Step 12, again watching for spaces and using the correct info from Step 11.
ACKNOWLEDGEMENTS
I, in no way shape or form, came up with the above method or tools. This method was modified from and composed from the method decribed over at Theunlockr.com for ease of use and to root the Captivate specifically. I big thanks go out to those guys!
ORINGAL LINK CAN BE FOUND HERE
WARNING
I am not responsible for any damage doone to the phone or its file system as a result of this tutorial. It is for educational purposes only. You have been warned!
THANK YOU!
No other method was working for me (not SuperOneClick, not these ADB instructions). Sure enough, using Terminal Emulator, I was able to get #. I wasn't able get this through adb, nor was I through SuperOneClick (infinite loop @ "mount" command).
I noticed a few things:
-When I compared filesizes from your provided Rage Root files, to the ones that were included in this thread (which also come with SuperOneClick—and which I was unable to get working), I noticed major differences. This gave me hope!, as I'd tried everything else that I knew how to prior to this point.
-My "XXXXXXXXXX" was actually only 4 characters: "stl6".
-My "YYYY" was only 3 characters ("rfs").
-SuperUser showed up on my applist without even requiring a reboot.
THANKS AGAIN
I shall now attempt to apply a lagfix; I will report back with results.
--Bah: no luck. RyanZA's OCLF V2.2+ returns error:
Could not mount /dev/block/mmcblk0p2 onto /dbdata/rfsdata: mount: No such file or directory
--OCLF V1+ returns error:
Could not create /data/linux.ex2 - dd: can't open '/data/linux.ex2': Permission denied
Uh-oh.
PhrProfess said:
THANK YOU!
No other method was working for me (not SuperOneClick, not ). Sure enough, using Terminal Emulator, I was able to get #. I wasn't able get this through adb, nor was I through SuperOneClick (infinite loop @ "mount" command).
I noticed a few things:
-When I compared filesizes from your provided Rage Root files, to the ones that were included in this thread[/url] (which also come with SuperOneClick—and which I was unable to get working), I noticed major differences. This gave me hope!, as I'd tried everything else that I knew how to prior to this point.
-My "XXXXXXXXXX" was actually only 4 characters: "stl6".
-My "YYYY" was only 3 characters ("rfs").
-SuperUser showed up on my applist without even requiring a reboot.
THANKS AGAIN
I shall now attempt to apply a lagfix; I will report back with results.
--Bah: no luck. RyanZA's OCLF V2.2+ returns error:
Could not mount /dev/block/mmcblk0p2 onto /dbdata/rfsdata: mount: No such file or directory
--OCLF V1+ returns error:
Could not create /data/linux.ex2 - dd: can't open '/data/linux.ex2': Permission denied
Uh-oh.
Click to expand...
Click to collapse
Yup same problem here. I was able to root it manually a few days ago, but have as of yet been unable to lag fix it.
Strange. After I rooted I had no problem using RyanZa's Lagfix. Your still using the stock rom after rooted correct?
deacfire said:
Strange. After I rooted I had no problem using RyanZa's Lagfix. Your still using the stock rom after rooted correct?
Click to expand...
Click to collapse
Correct. I've tested out quite a few apps from the market, though.
When I mount my device, I notice that there are some files on my internal SDCard:
-su
-Superuser.apk
-nv_data.bin
-busybox (why is this there, I uninstalled that)
-update.zip
...and some folders:
-layar
-twc-cache
-Android -» data -» com.cooliris.media
-Android -» data -» com.google.android.apps.maps
-svox
...These all have subdirectories.
Not knowing what a default internal SD directory ought to look like, I wonder: Could any of these be causing a conflict? I read that some said not to have any apps installed on the SDCard while trying to mess around (with ROMs, I think), so I tried removing what I could, and then rebooting (and some folders respawned), and reapplying the fix—no dice. I've since replaced all of the folders and the files.
Stock rom here as well.
Hrmm not quite sure why lag fix isn't working for you guys. Just a quick question, in RyanZa One Click, is "Un-Root Device" green?
I still have no problems applying RyanZa Lag Fix to my Captivate as I had to redo it last night after i switched back to the Rogers stock rom after testing Cog 2.2. My guess, and it is just a guess, is that the root never applied properly. Have you tried rerooting the device?
deacfire said:
Hrmm not quite sure why lag fix isn't working for you guys. Just a quick question, in RyanZa One Click, is "Un-Root Device" green?
I still have no problems applying RyanZa Lag Fix to my Captivate as I had to redo it last night after i switched back to the Rogers stock rom after testing Cog 2.2. My guess, and it is just a guess, is that the root never applied properly. Have you tried rerooting the device?
Click to expand...
Click to collapse
Thought I might give you some info as well since i've been messing with mine for about a week now. I was able to root the device, oneclick did not work originally for this and I used ADB method similar to what you had here. After this I went for the lag fix, everything was green like it was supposed to be, installed the ext2 tools no problem and then get the same error about unable to mount when applying lag fix.
At this point I used OCLF to unroot the device and it did, I then used the oneclick to re-root which it did this time, in terminal I can su properly and again all the tools are green in OCLF. Tried to lagfix and failed again so I started making some changes manually based on the error messages that were out put. Created the folder it was trying to mount to for instance and then set the permission to this to 777 that would allow world write access, this allowed it to create the new partition in ext2 but when mounting the loopback device it fails saying it doesn't exist (which it doesn't I looked) so while I did get a bit further the lag fix still fails. I would gladly apply the lag fix manually through the terminal if I knew everything that was being done to re-format the partitions for ext3 but I can't seem to find that info anywhere.
Next best thing I would guess is to install a stock rom from rogers from someone else and see if there are any differences, I'm guessing based on the devices in the /dev folder that there are more then one image on the devices some set up more similar to AT&T that the lag fix will work on.
mrprefect said:
Thought I might give you some info as well since i've been messing with mine for about a week now. I was able to root the device, oneclick did not work originally for this and I used ADB method similar to what you had here. After this I went for the lag fix, everything was green like it was supposed to be, installed the ext2 tools no problem and then get the same error about unable to mount when applying lag fix.
At this point I used OCLF to unroot the device and it did, I then used the oneclick to re-root which it did this time, in terminal I can su properly and again all the tools are green in OCLF. Tried to lagfix and failed again so I started making some changes manually based on the error messages that were out put. Created the folder it was trying to mount to for instance and then set the permission to this to 777 that would allow world write access, this allowed it to create the new partition in ext2 but when mounting the loopback device it fails saying it doesn't exist (which it doesn't I looked) so while I did get a bit further the lag fix still fails. I would gladly apply the lag fix manually through the terminal if I knew everything that was being done to re-format the partitions for ext3 but I can't seem to find that info anywhere.
Next best thing I would guess is to install a stock rom from rogers from someone else and see if there are any differences, I'm guessing based on the devices in the /dev folder that there are more then one image on the devices some set up more similar to AT&T that the lag fix will work on.
Click to expand...
Click to collapse
Try the stock rom in the main Rogers Captivate forum. It is one i used to go from Cog 2.2 back to stock and it applied the root and lag fix without a hitch. Give it a try and let us know!
deacfire said:
Try the stock rom in the main Rogers Captivate forum. It is one i used to go from Cog 2.2 back to stock and it applied the root and lag fix without a hitch. Give it a try and let us know!
Click to expand...
Click to collapse
Happen to have a link right to the forum? so many threads to search through...
I'm new to the whole android thing though I've been working with linux for years but its a bit of a learning curve coming from a blackberry.
also what are you using to flash your device?
I'm having the same problem. Let me know if you somehow fix it.
Sent from my SAMSUNG-SGH-I896 using XDA App
I was finally able to get my last night.
Turns out my first root attempt was a failure. I had to unroot via an update.zip method as i did not have the permissions to remove the files from terminal.
Once unrooted i then did the update.zip method for the I897, and modified the script to look for I896 instead. It worked flawlessley. I am now getting the pop-up asking for root permissions. I had never seen it work previously.
I was then able to install OCLF without any problems. (and it popped up asking for root)
I am now rooted and lag fixed. Previous quadrant score was at 860's and i pulled a 2285 last night after the OCLF.
Can you please tell us how to modify script and how to flash back to stock..I need to return my phone and superuse app wont go away after unrooting and factory reset
inningsdefeat500 said:
Can you please tell us how to modify script and how to flash back to stock..I need to return my phone and superuser app wont go away after unrooting and factory reset
Click to expand...
Click to collapse
Well i cannot help you flash back to stock as i don't quite know how to do that yet myself. But i can help you unroot, re-root, and lag fix.
I have found the files again and uploaded them to rapid share with the necessary modifications.
Download THIS FILE and once downloaded, rename it to update.zip Be careful not to name it update.zip.zip by accident.
Place the file into the root of your sdcard.
Shutdown the phone with the power button, or pull the battery out and put it back in.
Enter recovery mode:
While holding the volume up and volume down buttons press and hold the power button until you see the white text that says SGH-I896, then release the power button only.
When in recovery mode use the volume down key to highlight reinstall packages, then press the power button. It should say completed and reboot the phone.
Once the phone has rebooted, do the exact same thing again, only use THIS FILE instead. Dont forget to rename the file again!
Then install the OCLF from market. Install the EXT2 tools first. Then run the lag fix installer.
I assume you already know how to enter recovery mode, but this way someone else searching for a fix will have all the info at their disposal here.
EDIT!!!
Some mirrors for the files
For the UN-Root files go HERE
For the ROOT files go HERE
Hi all i am very lost here....i have tried for hours the last few days on how to root this i896 with the super one click method with no luck....anyways i was speaking to my brother earlier and he has done it with his bell vibrant no problem....anyways what i want to know is what is the purpose of rootindg the phone? I thought it was for downloading 3rd party apps or whats the purpose for superuser? The reason why i am asking is that i can download 3rd party apps already...i allow them on my application settings and download a app downloader and works fine? Im lost someone please help.
Sent from my SAMSUNG-SGH-I896 using XDA App
dandroid123 said:
Hi all i am very lost here....i have tried for hours the last few days on how to root this i896 with the super one click method with no luck....anyways i was speaking to my brother earlier and he has done it with his bell vibrant no problem....anyways what i want to know is what is the purpose of rootindg the phone? I thought it was for downloading 3rd party apps or whats the purpose for superuser? The reason why i am asking is that i can download 3rd party apps already...i allow them on my application settings and download a app downloader and works fine? Im lost someone please help.
Sent from my SAMSUNG-SGH-I896 using XDA App
Click to expand...
Click to collapse
Take a look here. It answered alot of my questions.
http://www.androidcentral.com/rooting-it-me-some-qa
Also, if you only follow the second half of my post above you should be able to root it as well.
Thanks deacfire! The one click wouldn't work for me but the second method did.
I am having a really annoying problem though. The superuser.apk that you included just gave me a black screen. So I updated it to this one: http://forum.xda-developers.com/showthread.php?t=682828&highlight=no+apps+in+list
Which is newer. But now it just says "no apps in list". Tried installing it from the zip, tried from the market no different.
I do have apps that require superuser: ROM Manager, Root Explorer, Adfree. They all work, also have titanium backup but its is telling me it needs root access.
How can I fix this, it is a major issue.
EDIT:Thanks impulser91!! That work and was SUPER easy! Should probably get posted in the original post.
when i copy update.zip into the /sdcard and then try hitting reinstall packages, it results in an error and aborts. any suggestions?
Nevermind....it worked MUAHAHAHAHAHAH LET THE FUN BEGIN!
Sweet, 2 users. Not bad for under 10 posts
I'm glad its working for others. I had one heck of a time finding the right combination of files and process's for the I896. I am an IT professional and it took me a few days of fumbling around all the I896 and I897 posts.
Anyways, glad to hear it worked, and i hope other people find it useful as well. I will keep the originals, so if the links go down someone just PM me and i will load them somewhere else.
impulser91 said:
Well i cannot help you flash back to stock as i don't quite know how to do that yet myself. But i can help you unroot, re-root, and lag fix.
I have found the files again and uploaded them to rapid share with the necessary modifications.
Download and once downloaded, rename it to update.zip Be careful not to name it update.zip.zip by accident.
Place the file into the root of your sdcard.
Shutdown the phone with the power button, or pull the battery out and put it back in.
Enter recovery mode:
While holding the volume up and volume down buttons press and hold the power button until you see the white text that says SGH-I896, then release the power button only.
When in recovery mode use the volume down key to highlight reinstall packages, then press the power button. It should say completed and reboot the phone.
Once the phone has rebooted, do the exact same thing again, only use THIS FILE instead. Dont forget to rename the file again!
Then install the OCLF from market. Install the EXT2 tools first. Then run the lag fix installer.
I assume you already know how to enter recovery mode, but this way someone else searching for a fix will have all the info at their disposal here.
Click to expand...
Click to collapse
I could just about kiss you.... but I won't
Thanks for the update files they worked like a charm. I had a similar issue where the device didn't seem to be properly rooted, though it didn't give me any issues with most things when applying the lagfix it would die.
applied both your unroot and then root and it worked flawlessly the first time, lagfix then ran with no issues and my quadrant scores are 2250 now.
Not sure what you did exactly, I've tried rooting from update.zip from oneclick and neither worked I ended up rooting with the ADB and though it seemed to work it apparently did not.
Thanks again

MultiCSC OXXJK2 - Asian MultiCSC

ok i know, another attempt to learn something from seniors:
Just downloaded the 'GT-P1000-CSC-MULTI-OXXJK2.tar.md5 *' from samfirmware.com attempt to flash asian multicsc and after unzipping, see the tar.md5 extension and feel something have to do with the 'signed' thingy every one now fear of.
This tar.md5 contains 3 files: cache.rfs, dbdata.rfs & moveinand.mst
May i know will i face problem if i flash this csc with Roto's JME firmware?
I just try flashed my tab to the newest asian rom == ZHKA1 with the CSC u mentioned .....
After reboot.......
Do u think I being signed?
HA...HA....HA....
It still unsigned and can flash any rom I like..
I just test it with SGT bootloader check..!!!
So, just go on, without this CSC, the tab even can't boot!!!!!
MY FIRST FLASH in Galaxy TAB...
the mentioned CSC didnt work with Roto's JME flash which i applied to my SGT. Odin1.7 reported checksum not right or something like that and halt the flash. so i am using CPW from JME multiCSC that came with Roto's.
I will try when gingerbread 2.3 is ready for SGT. btw, you're from HK/China to use that ZHKA1?
I from Hong Kong, haven't flash Roto JPE before as it have protected bootloader issue.
Just follow the guide of Chainfire to asure the ROM is safe before flash. I think your tab have be protected as the post stated by Chainfire.
Sent from my GT-P1000 using XDA App
rainbow ng said:
I just try flashed my tab to the newest asian rom == ZHKA1 with the CSC u mentioned .....
After reboot.......
Do u think I being signed?
HA...HA....HA....
It still unsigned and can flash any rom I like..
I just test it with SGT bootloader check..!!!
So, just go on, without this CSC, the tab even can't boot!!!!!
MY FIRST FLASH in Galaxy TAB...
Click to expand...
Click to collapse
Check Fus also notified me of KA1 version available, but could you kindly explain step by step how you upgraded your FW please?
smaragdhk said:
Check Fus also notified me of KA1 version available, but could you kindly explain step by step how you upgraded your FW please?
Click to expand...
Click to collapse
he....he.... "Fus" mean what??
I am not expert, just share my experience to see if it helpful.
When I 1st flash I9000, I lost much thing, like APN (can't use 3G), CSC code( no Samsung Apps to download, market link, can't use KIES to update offical rom, IMEI no), and some app which need password and username as I forgot that anyway. So try to backup everything is the must before you flash, as mentioned by Rotohammer and Chainfire.
Go to your APN setting and write down everything for u to get your 3G connection.
Use Z4Root to root your device and make a full backup with "Titianium Backup".
Use SGS tools to backup ur product code, something like nv_data.bin etc.
Use root explorer to copy the /efs
Use Chainfire root if u can to make a nandroid backup of your current ROM, it is highly recommended in case your TAB being bricked can easily recover to the current stage without pain.
after everything backuped, copy all the file to your computer or external SD card and remember to unmount it.
Flash is simple , backup is painful but MUST do if u don't want to post "my TAB is bricked, help me pls" in the forum. (In actual case , it is really difficult for u to brick your TAB or I9000 permenant if u are not a developer like Chainfire as they always try to make something experimental on the phone that why they are so respective!
Flash procedure:
1. stop the KIES running in your computer, (front or background running is not allowed), terminate it by task manager of window if u don't know how.
2. start the Odin v1.7
click the re-partition box, click the pit and choose p1.pit, click the PDA and choose the ROM file u want to flash,in me case is KA1, which should with .tar as extension, click the CSC and choose the CSC u want to use.
3. power off you TAB , remove SIM and SDcard, press the volume down and the power buttons together for a few seconds, a nice yellow android robot appear on the skin, release the buttons and connect to the computer asap.
4. the Odin window will appear a yellow box if it detect the phone, then click the start button.
5. everything will go on automatically , no need to do anything and pls don't, be patient . The whole process of flashing about 3 to 7 minutes, then the TAB reboot to fresh new ROM.
p.s. if any thing go wrong or missing berfore u connect the phone to computer, just close all restart again, do not click any thing not mentioned. If the phone hv any problem long press the power button for 8 second will reboot. if u failed (odin will tell u), and see "phone-!-computer" ,just re- start the odin again and plug in the phone, u will see the yellow box and click start , the flashing process wil restart once again.
hope helpful. ;-)
Sent from my GT-P1000 using XDA App
rainbow ng said:
Flash procedure:
1. stop the KIES running in your computer, (front or background running is not allowed), terminate it by task manager of window if u don't know how.
2. start the Odin v1.7
click the re-partition box, click the pit and choose p1.pit, click the PDA and choose the ROM file u want to flash,in me case is KA1, which should with .tar as extension, click the CSC and choose the CSC u want to use.
3. power off you TAB , remove SIM and SDcard, press the volume down and the power buttons together for a few seconds, a nice yellow android robot appear on the skin, release the buttons and connect to the computer asap.
4. the Odin window will appear a yellow box if it detect the phone, then click the start button.
5. everything will go on automatically , no need to do anything and pls don't, be patient . The whole process of flashing about 3 to 7 minutes, then the TAB reboot to fresh new ROM.
Click to expand...
Click to collapse
Are you able to root this? I did the same as you before, but error is not enough space for superuser.apk sigh, if you have any info, perhaps enlightening me
EDIT: Nevermind Put in su, busybox, and superuser.apk into /system/app through linux mount, in the process I removed usual stuffs that I dont need Cool!
fastcx said:
EDIT: Nevermind Put in su, busybox, and superuser.apk into /system/app through linux mount, in the process I removed usual stuffs that I dont need Cool!
Click to expand...
Click to collapse
use adb shell
rootsh
mount /system
cd app
ls ~~ to see what is inside and choose some unwanted app
rm
exit
exit
and now u gain space in /system and can install su
Sent from my GT-P1000 using XDA App
rainbow ng said:
use adb shell
rootsh
mount /system
cd app
ls ~~ to see what is inside and choose some unwanted app
rm
exit
exit
and now u gain space in /system and can install su
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
Already rooted it yesterday but thanks anyway, i just edit the factory.rfs in linux b4 I flash it into my tab instead now I dont need to remove anything after flash
fastcx said:
i just edit the factory.rfs in linux b4 I flash it into my tab instead now I dont need to remove anything after flash
Click to expand...
Click to collapse
Out of interest, do you use this Linux shell command ?
#mount -o loop factoryfs.rfs /mnt/rfs
On Mac OS X terminal I normally use the following commands, but I don't think modifications can be written back to the RFS archive:
#sudo mkdir /Volumes/rfs
#sudo hdiutil attach -imagekey diskimage-class=CRawDiskImage -nomount factory.rfs
#sudo mount_msdos /dev/disk{n} /Volumes/rfs
I use Ubuntu for most of my Android hacking, so I guess I will also start using Linux to look inside RFS archives, and to modify them directly

<RESOLVED> [HELP]N7100_IMEI 0049xx_SN 0000.._Service State "out of service"

<RESOLVED> [HELP]N7100_IMEI 0049xx_SN 0000.._Service State "out of service"
Hi Guys. I got this issue after upgrading my Note II to the latest OMEGA ROM v17. After doing the upgrade I was able to use it for a couple of hours and then I realized though there is a signal I am not receiving any internet data (internet icon was gone). I restarted the phone, switch to flight mode back and forth, switch on/off data, but still no luck. I soon realized also that I am not receiving any SMS or call. I thought it was just my carrier so I called them and made a complaint like hell. They said that my line should be fine. From there I started reading for all possible reasons why I am getting this issue. I then found out that my IMEI that is showing on the phone is different on the sticker attached on the battery compartment. Serial number on the phone is 000000000. Service state is "Out of service" though it detects from which network my SIM is. I have tried to flash different custom ROMs and several stock ROMs, but with no go. Tried also different methods on restoring EFS and still no luck. Stupid me, I don't have any backup EFS file or a copy of a nand backup. I was able to get out of the factory mode, wifi and everything else are working except for not receiving any call or SMS because of the bad IMEI, SN, and the Service state "Out of service". I have read some fixes on other threads from a different android phones, but with no avail in fixing mine. I know there's a lot of thread of the same issue, but I want to create my own so I can make sure that people who got ideas on how to fix this is just referring to my "own" issue which will be easier for me to monitor the thread.
So I have tried the following:
- flashed different custom ROMs - no good
- flashed several stock ROMs - no good
- tried EFS Professional.exe - no good
- tried N7100_EFS_Backup_Restore_WIN - no good
- tried ARIZAPatch.apk - no good
- tried SGS tools - no good
- tried com.helroz.GSII_Repair_102.apk - no good
- tried NV-items_reader_writer.exe - I don't know how to make it work
- restored old EFS Backup - no good
- able to find an old NANDroid backup (when it was still working before), flashed it - no good
They say helps the modem from the topic http://forum.xda-developers.com/showthread.php?t=2333216
### --- XXDME4 modem --- ### fix IMEI - -unknown modem
on the XXDME6 base - you can not install old modems,
because it will cause for unknown modem & imei status.
Solution flash - XXDME4 modem
XXDME4 modem
flash via TWRP / CWM
ATTACHED FILES
modem XXDME4 .zip - [Click for QR Code] (4.84 MB, 1209 views)
Click to expand...
Click to collapse
tried that still no go
red_hanks said:
...
Click to expand...
Click to collapse
Read this
victorator said:
Read this
Click to expand...
Click to collapse
Tried that mate but no luck.
in /efs folder contains files *.bak?
aaleo said:
in /efs folder contains files *.bak?
Click to expand...
Click to collapse
yup
move the following files in a backup folder somewhere to your internal SD card
.nv_core.bak,
.nv_core.bak.md5,
.nv_data.bak,
.nv_data.bak.md5,
nv_data.bin,
nv_data.bin.md5
moving them they will be deleted from the efs folder
Reboot.
Now you will have the generic IMEI.
aaleo said:
move the following files in a backup folder somewhere to your internal SD card
.nv_core.bak,
.nv_core.bak.md5,
.nv_data.bak,
.nv_data.bak.md5,
nv_data.bin,
nv_data.bin.md5
moving them they will be deleted from the efs folder
Reboot.
Now you will have the generic IMEI.
Click to expand...
Click to collapse
I have tried that method but it just made my note2 switch to factory mode. Sorry to ask but have you tried that method on your own or you just copy pasted that from somewhere showing that you're willing to help but no certainty if that really works or will just mess up something?
I did it. I did not have IMEI (0000000000) I think you can help it. The last thing that comes to mind to flash the original firmware from sammobile.com through odin.
---------- Post added at 04:39 PM ---------- Previous post was at 04:23 PM ----------
You can restore files via adb
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p3 /efs
cp /mnt/sdcard/.nv_core.bak /efs/.nv_core.bak
cp /mnt/sdcard/.nv_core.bak.md5 /efs/.nv_core.bak.md5
cp /mnt/sdcard/.nv_data.bak /efs/.nv_data.bak
cp /mnt/sdcard/.nv_data.bak.md5 /efs/.nv_data.bak.md5
cp /mnt/sdcard/nv_data.bin /efs/nv_data.bin
cp /mnt/sdcard/nv_data.bin.md5 /efs/nv_data.bin.md5
aaleo said:
I did it. I did not have IMEI (0000000000) I think you can help it. The last thing that comes to mind to flash the original firmware from sammobile.com through odin.
---------- Post added at 04:39 PM ---------- Previous post was at 04:23 PM ----------
You can restore files via adb
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p3 /efs
cp /mnt/sdcard/.nv_core.bak /efs/.nv_core.bak
cp /mnt/sdcard/.nv_core.bak.md5 /efs/.nv_core.bak.md5
cp /mnt/sdcard/.nv_data.bak /efs/.nv_data.bak
cp /mnt/sdcard/.nv_data.bak.md5 /efs/.nv_data.bak.md5
cp /mnt/sdcard/nv_data.bin /efs/nv_data.bin
cp /mnt/sdcard/nv_data.bin.md5 /efs/nv_data.bin.md5
Click to expand...
Click to collapse
Just tried original firmware but same thing. I am getting frustrated now..
Stupid idea. Maybe it's in the sim card is broken. There is another test for?
aaleo said:
Stupid idea. Maybe it's in the sim card is broken. There is another test for?
Click to expand...
Click to collapse
SIM card is ok. Read my explanation on post #1.
Was able to find an old EFS backup of mine dated January 2013. Tried to restore it but still same issues.
red_hanks said:
Was able to find an old EFS backup of mine dated January 2013. Tried to restore it but still same issues.
Click to expand...
Click to collapse
Read this: http://forum.xda-developers.com/showthread.php?t=2332913
The Stability update on which is based the rom has some changes in the kernel and the efs folder. Maybe that thread can help you out....hope it does....:good:
red_hanks said:
Tried that mate but no luck.
Click to expand...
Click to collapse
Just wondering, did you tried Kies Emergency restore???
Sent from my GT-N7100 using xda premium
find someone who has a SGN2 ,back up the image of efs partition 20mb , open it with a compiler on your pc, change the IMEI to same as yours on the box , recompile and restore.
hagba said:
find someone who has a SGN2 ,back up the image of efs partition 20mb , open it with a compiler on your pc, change the IMEI to same as yours on the box , recompile and restore.
Click to expand...
Click to collapse
Wow sounds complicated lol hope this don't happen to me!
Sent from my GT-N7100 using xda app-developers app
glevitan said:
Read this: http://forum.xda-developers.com/showthread.php?t=2332913
The Stability update on which is based the rom has some changes in the kernel and the efs folder. Maybe that thread can help you out....hope it does....:good:
Click to expand...
Click to collapse
Done with this with no luck.
aspot72 said:
Just wondering, did you tried Kies Emergency restore???
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Not sure how to do that, never use Kies before
hagba said:
find someone who has a SGN2 ,back up the image of efs partition 20mb , open it with a compiler on your pc, change the IMEI to same as yours on the box , recompile and restore.
Click to expand...
Click to collapse
Like what I have said, found an old backup of mine and it doesn't work. So it's pointless to try this.
I was sleepless (haha) trying to find solution for this. I came across this site and tried the app there. But as you can see on the image below, the button to change the IMEI is grayed out. There is not clear instructions on the site so it is kinda hard what to do in times like that. The app might be for a specific device but if it recognized the IMEI on my phone then it should be able to change it.

Just purchaced a Note 3 verizon, Pls suggest best practices to Root & unlock

Hello good peoples of Xda ,
I just purchased a Note 3 verizon I believe 900v on swappa It will arive in the next few day's and I want to get all my ducks in a row by that I mean aquire all the root and unlocking tools nessary for a best practices root and if nessary unlocking of my boot loader.
Goals for root are mostly to debloat the phone and hotspot mod's for no hassle teathering.
I may dip my toes into custom rom for this phone but mostly I am just looking for a clean lean experiance for my note 3. I have been pouring over the many many pages of the various rooting guids and I am just not sure witch method to use is the safest / most reliable .
thank you for your time and helpful suggestions.
This is what I have found so far.
ArabicToolApp : Root for lolipop
Odin3 v3.12.3 : flash tool is this latest ? best to use ?
Samsung usb drivers v1.5.45.0 : are these the proper drivers to install ?
You should start by figuring out which firmware release it has on it.
If it has PL1 (the newest security release, circa 2017/01/15), there will be no rooting for you... unless you manage to create a new exploit.
OB6 and OF1 - (one of) the yemen tool(s)**
NK1 - no root available ( and can't be rolled backwards w/ Odin, only NK1 or higher )
NJ6 - no root available? ( Try towelroot, or you can downgrade to NC4 using Odin )
MI9/MJ7/MJE/NC2(leak)/NC4 - Towelroot v3
For which bootloader unlock binary to use, see here.
Can't help you out with USB drivers, I don't remember what I used. afaik, they will either work 100% or not work at all, so you just need to get something working.
I've never used anything but Odin 3.0.9. Can't tell you if the version you mention is "better".
good luck
** i've never rooted OB6 or OF1, so can't give you any advice about which to use. Feel free to read the related threads. In my (casual) reading of those threads, it is nearly impossible to intuit out why some people have problems and others do not. Mostly because the reporting is not sufficiently detailed.
bftb0 said:
You should start by figuring out which firmware release it has on it.
Click to expand...
Click to collapse
Your right, after thinking about my post I realized there were 2 many variables that I need to know before I ask for help. So once I recieve the phone and if it's fully functional I will find out what firmware it has and what the cid it has and will post a follow up if I need help.
P.S thank you for the concise jist of what is and is not possible with the various firmware's.
Recieved my phone.
I got my note 3 and boy is it just a wonderful device. SM-900v running OF1 firmware, and My Cid is 15 so is all good.
procedurs completed.
I got root from useing the yemem tool.
and have tryed some debloating removed the NFL apk as a test with Tit.backup.
dissabled ota updates, I made a copy of the update.zip (that was downloaded with out me asking it too. I assume that this update.zip is the new PL4 firmware )and deleted it. renamed the fota.apk's with a .bak
not really sure if I should unlock the the bootloader I would love to have twerp.
Could anyone point me at a good debloating script ?
LOVE LOVE LOVE my note 3.
I also have a zero lemon battery/case combo on the way.
PL1 not PL4
See here. Might be dated - stuff tends to move around from release to release.
You should probably also freeze SDM.* and SysScope.* (in addition to LocalFOTA)**
There is a small permanent downside to unlocking - the blowing of the Knox Warranty Flag means that you will never be able to use Knox Secure containers, even if you did a full stock flash with Odin. Not sure how important this is to folks using the phone as a personal device (as opposed to a corporate device).
Operating with a rooted-stock device with a locked bootloader usually progresses through a customary arc - especially with new rooters, but also with experienced folks - where the user one day does some incremental mod that boot-loops the Android UI. At that point there is no means to reverse the small change. (You can't get in via "adb" as it's daemon isn't started yet, and even if it were, the fact that it is in secure mode means that you would have to have a stable UI in order to confirm the connection.) As there is no rooted secondary boot available (i.e., a custom recovery), there is no way to perform repairs, and a trip back to Odin is in store for the owner. Worse yet, a backup has never been made... so all customizations are all lost and must be re-created completely from scratch.
** this is a good idea if you unlock and install a custom recovery: (although TWRP may detect it and emasculate it automatically)
Code:
su
chmod 0000 /system/bin/install-recovery.sh
bftb0 said:
PL1 not PL4
Click to expand...
Click to collapse
Right PL1 ok.
Well I decided in for a penney in for a pound and have sucessfully unlocked my boot loader, had no issues.
my question now is how do I install twerp I have downloaded
twerp-3.0.2-0-hltevzw-4.4
and twerp 3.0.2-1-hlte.img.tar
I think I need to install the tar file.
but I don't know how. I have odin but not sure if that is the right program to use. I think I read where somone installed twerp with flashify or somthing like that.
What should I do ?
Truck'nfool said:
Right PL1 ok.
Well I decided in for a penney in for a pound and have sucessfully unlocked my boot loader, had no issues.
my question now is how do I install twerp I have downloaded
twerp-3.0.2-0-hltevzw-4.4
and twerp 3.0.2-1-hlte.img.tar
I think I need to install the tar file.
but I don't know how. I have odin but not sure if that is the right program to use. I think I read where somone installed twerp with flashify or somthing like that.
What should I do ?
Click to expand...
Click to collapse
man up and use a root prompt command line. It's a single command.
Code:
dd of=/dev/block/mmcblk0p15 if=/sdcard/twrp-3.0.2-0-hltevzw-4.4.img bs=2048
( assuming that you put the twrp .img file in the /sdcard folder. If it was in the download folder, then if=/sdcard/Download/twrp-3.0.2-0-hltevzw-4.4.img )
Note there are absolutely, positively no spaces anywhere in "mmcblk0p15". Critically important.
The above command writes a raw binary data (the .img file) to the 15th partition of the mmcblk0 device - the flash memory chip. You can do this with boot images (such as custom recoveries) or a few other binary images, but typically not with ext4 or other filesystems.
Note this command could be extremely dangerous if you made a mistake. If you were to write data someplace else it could be a permanent disaster. So cut-n-paste to be safest (without a new-line), and then double- and triple- check the command for typos before you hit the enter key.
FYI, you can see what the partition mapping is by doing a folder listing
Code:
ls -ld /dev/block/platform/*1/by-name/*
The partitioning scheme varies from android device to android device; but on the SM-N900V the recovery partition is the 15th partition. (On other devices it might be something different).
bftb0 said:
man up and use a root prompt command line. It's a single command.
dd of=/dev/block/mmcblk0p15 if=/sdcard/twrp-3.0.2-0-hltevzw-4.4.img bs=2048
Click to expand...
Click to collapse
are you talking about adb ?
So somthing like
adb shell
su
dd of=/dev/block/mmcblk0p15 if=/sdcard/twrp-3.0.2-0-hltevzw-4.4.img bs=2048
???
Truck'nfool said:
are you talking about adb ?
So somthing like
adb shell
su
dd of=/dev/block/mmcblk0p15 if=/sdcard/twrp-3.0.2-0-hltevzw-4.4.img bs=2048
???
Click to expand...
Click to collapse
That works.
Or a terminal emulator.
All you need is to put the file on your (internal, pseudo-) /sdcard, "su", and "dd".
For extra credit, make sure to compute a file checksum (e.g. "md5sum") every time you copy the original .img file to a new location and especially prior to flashing. That safeguards against a bad copy operation, crappy flash memory, etc.
Stock ROMs might not have a "md5sum" binary in /system/bin, but since you are rooted you could install a private busybox in someplace like /data/local/bin. I prefer to use a busybox which is SELinux-cognizant, e.g. v1.23.1 here as busybox_full_selinux_1.23.1.zip Note that I don't "install" this .zip so that stuff in /system/bin or /system/xbin get overwritten, but instead just keep it in a private area all on it's own.
Steps.
0) extract the "busybox" binary from the .zip file and get a copy to your SD card. Then
Code:
su
mkdir -p /data/local/bin
chmod 755 /data/local/bin
cp /sdcard/busybox /data/local/bin/
chmod 755 /data/local/bin/busybox
cd /data/local/bin
./busybox --install -s /data/local/bin
This allows it to be used as needed in a terminal/console shell.
e.g. using ls
1) Explicitly: /data/local/bin/ls -lZ *
2) Implicitly "as a last resort":
export PATH="${PATH}"':/data/local/bin'
ls -lZ *
3) Implicitly "as preferred":
export PATH='/data/local/bin:'"${PATH}"
ls -lZ *
I am now have root, unlocked bootloader and twrp Whoot!!
Well I now have twrp installed thank you vary much for all your help and direction I sincerly appreciate your assistance.
I installed termux and after updating the packages sucessfully used dd to install twrp.
1st thing I am going to do a full system backup.
No developer love for N900V not good

Categories

Resources