Database Info

OBSOLETE.

In the event something happens to your phone, -I'm- not responsible for the damages to it, you are. The end. I've personally tested this method and it works flawlessly.
This tutorial entails gaining full root access on your Evo. That means we -will- be unlocking NAND. But most importantly, we'll be doing it all without the use of a computer. Needless to say, this is going to take a while, especially if you don't have access to a wifi signal. The PC36IMG.zip files are rather hefty and are going to take at least 30 minutes to download. So I suggest you start downloading both of them now.​
Prerequisites: Download Astro File Manager from the market. Open it up, hit the menu key on your phone, select more, select preferences, then scroll down and make sure Enable Browser Download is checked.
This is a template for you guys that'll explain to you how to move a file to the root of your SD card using Astro File Manager.
The files that you've downloaded from the links below are going to be located in the Downloads folder that is on the root of your SD card.
Unless you're using a browser like Xscope or Dolphin, then you'd have to navigate to the particular browser's folder that you're using, open it up and find the downloads folder in there.
When you first open the Astro File Manager app, you're going to be staring at what is the actual root of your SD card. Remember that.
Code:
When I tell you to move something to the root of your SD card, you're going to:
Locate and open the appropriate download folder that contains the file I am referring to.
Long press on the file.
Select Edit.
Select Move.
Press the Back key on your phone 'til you've reached the root of your SD card in Astro File Manager.
Click the Menu key on your phone.
Select Edit.
Select Paste.
When I tell you to rename a file you're going to:
Long press on the file.
Select Edit.
Select Rename.
Rename it accordingly and select done.
Step 1. Download this file http://link.geekfor.me/rootedromzip and move it to the root of your SD card.
Step 2. Power down your phone.
Step 3. Hold down the Volume Down and Power key simultaneously and keep holding it down until you've reached a white screen with 3 android dudes on skateboards.
Step 4. It's going to give you some options, whether or not to install the PC36IMG.zip, select yes (volume up is yes) for any prompt you get.
Step 5. Once you've rebooted you will officially have root access. Just not full root access, we still need to unlock NAND.
Step 6. Navigate to the root of your sd card and rename the PC36IMG.zip file whatever you want, doesn't matter. Just don't name it update. You can even delete it if you want.
Step 7. Download the mtd-eng.zip file here. - http://forum.xda-developers.com/attachment.php?attachmentid=342668&d=1276481802 And the flash_image.zip file here. - http://forum.xda-developers.com/attachment.php?attachmentid=342667&d=1276481776
Step 8. Navigate to the root of your SD card and locate both of the .zip files you just downloaded. Open them, and long press on the files inside of them, then select Edit, then Copy, navigate back to the root of your SD card, press menu, select Edit, and then paste. Do the same thing for both files.
Step 9. Open up the Android Market and download the terminal emulator app by Jack Palevick, it's free.
Step 10. Open the terminal emulator app and type in these commands exactly as they are written. If you get an error, try again.
Note: After each line is completed, hit enter. A # sign means you've run the commands successfully.
Code:
[B]su
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image misc /sdcard/mtd-eng.img[/B]
Step 11. Download the new PC36IMG.zip file here -http://sdx-downloads.com/sdx/evo/troot/eng-PC36IMG.zipand move it to the root of your SD card, then rename it to "PC36IMG.zip" because the is named eng-PC36IMG.zip, which is wrong. Then power down your phone.
Step 12.
Hold volume down and power to boot into hboot.
- It should now find and verify the PC36IMG.zip on the root of your sdcard. It'll show a blue status bar on the top right of the screen.
- After a minute or so it will ask u if u wanna flash Select YES.
- After it flashes the PC36IMG.zip it will ask if you wanna reboot. Select YES.
Click to expand...
Click to collapse
Step 13. Once your phone has rebooted, download the recovery.img file here - http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=recovery-RA-evo-v1.7.0.1.img Then move it to the root of your SD card and rename it "recovery.img"
Step 14. Still know how to use terminal emulator? Open it up and type in these commands.
Code:
[B]su
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image recovery /sdcard/recovery.img[/B]
You now have full root access as well as a legit recovery.
If you want to flash a ROM or the newest radio and you don't know how to do that, there's already guides for that. So I won't include that in my tutorial, just click here. http://forum.xda-developers.com/showthread.php?t=710513
ALL CREDIT GOES TO THESE GUYS! toastcfh, keishou, maejrep, Paul, Amon_Ra, Koush, TheBiles, and anybody else I forgot.
PLEASE NOTE THE DONATION SUGGESTION IN MY SIGNATURE.
I must look like a douche what with the bold CAPS asking to note the donation link in my signature, which used to be a link to Dr. Cloverdale's paypal, not mine. Just thought I'd clear that up.

Reserved.
10 char

Great Work!!
Wow, great work!! Seems easy enough to me. I have a quick question as i haven't rooted yet and don't know all it entails.
First, you say after this method that we have a "legit recovery"...does that mean if i hard reboot, that there is a rooted, nand unlocked image you put there already that will flash with a hard reset? And if so, what image did you use? (or is it exactly the same as stock but rooted)
Second, some of the other quides state we need to root, then unlock, then flash a custom recovery...it looks as if you have all 3 steps included right?
Finally, is there anything else you recommend i do after i complete root using your method?? I am looking forward to maximizing this phone!!
Thanks for this guide!!! Can't wait to try it out.

adeyo said:
Wow, great work!! Seems easy enough to me. I have a quick question as i haven't rooted yet and don't know all it entails.
First, you say after this method that we have a "legit recovery"...does that mean if i hard reboot, that there is a rooted, nand unlocked image you put there already that will flash with a hard reset? And if so, what image did you use? (or is it exactly the same as stock but rooted)
Second, some of the other quides state we need to root, then unlock, then flash a custom recovery...it looks as if you have all 3 steps included right?
Finally, is there anything else you recommend i do after i complete root using your method?? I am looking forward to maximizing this phone!!
Thanks for this guide!!! Can't wait to try it out.
Click to expand...
Click to collapse
Legit, as in the most legit recovery on the scene, that being Amon_RA's.
Yup, got all three covered in that order.
Here's a link that shows you an in-depth guide on how to flash ROM's and what-have-you. http://forum.xda-developers.com/showthread.php?t=710513
No problem, man. Let me know how it goes for ya'.

Does this method still work with the latest OTA patch on 6/28/10?

Aren't you supposed to have Superuser Permissions after flashing the first ROM?

and you do get super permissions after you flash a CUSTOM rom....

what's your definition of 'CUSTOM'? This isn't my first time rooting, I unrooted lastnight and decided to try this method to see if it would work. I know for a fact that during the original rooting process the first PC36IMG you flash, you have Superuser permissions. And the second one that is flashed is the ROM to unlock NAND. However, doing this method, after flashing the first PC36IMG, I do not have Superuser permissions

However, it does seem that this method works. So I'm happy. It's good to know that I don't have to rely on a computer to root my phone now. Now the only thing I need to do, is figure out how to UNroot my phone without a computer.

Android believer, did you update to the ota update yesterday? Do you know if this works with the ota v1.47.651.1?
Sent from my Evo using XDA App

gordon1hd1 said:
Does this method still work with the latest OTA patch on 6/28/10?
Click to expand...
Click to collapse
I would assume it doesn't, as this is still toastcfh's method of rooting except it's done without a computer.

@ neckface
Hope you're not tired of hearing from me. First, thanks mass for this.
You say this is Toasts method without computer. I'm on the orig stock ROM, no 1.47 update. I WANT to do the update (for better battery mainly). I want to do whitslacks method. He says you need eng hboot 76.2000. He says use Toasts part 2 to get that.
Should I : use this to get eng hboot, then go to whitslacks for the 1.47 update? You seem to have a pretty good grip on this, so I thought I'd ask your opinion.
(if this is still Toastcfhs method, are these links to the same files he has posted? Meaning, will this get me eng-Hboot 76.2000? )
Thanks a lot.

anybody
Really interested in this. Anyone have success with this from 1.32 SW, and does it give you hboot 76.2000 ?
Thanks in advance.
Scott

OK i must be the dumb one
I have already used the "Unrevoked method" so I thought I could just skip to the Nand unlock. Now the phone(EVO) will not allow me access to my sdCard...and..will not read when I plug it up to my USB PC(windows) instead of it coming up as android like it use to it comes up as Qualcomm CDMA Technologies MSM(new found hardware wizard)....and the phone can only charge when the phone is powered off. Its like the usb is not responding and I can not have access to the SD card via teh device..i need advice

Thank you
Thank you,
I don't know if it was the wrong recovery.img or what, but I could not do a nand unlock. This worked great and did it all off the phone..... Awsome

Rooting & Unlocking my Rogers Captivate SGH-I896

Thanks to the wonderful information here on this site, I was able to root and unlock my Canadian Samsung Captivate S a.k.a. Rogers Captivate SGH-I896.
Us Canadian phone owners know that our phones are slightly different than what you guys in the states got. Those differences were significant enough to cause me trouble in unlocking my phone (my main priority) and which eventually got me to the realization that I would need to end up rooting my phone.
So here is what I did to root and unlock my phone. Yes, most of this information is found in the SGH-I896 wiki but I'm going to put more detailed instructions here to share my knowledge/experience. Also, note the stock Rogers ROM is Android 2.1 software version I896UXJI2.
Do go to http://www.communityhosting.net/sgsunlock/ and click on the Unlock Instructions for the Captivate. My instructions below follow the general gist of these original instructions but I simplified a few steps to reflect the differences I experienced when unlocking my SGH-i896.
Of course, the caveat always is in play - any attempts on your part to follow my instructions to root/unlock your phone is at your own risk and peril. I take no responsibility for any damages you cause to your own personal device.
With that out of the way, here's what I did!
Chapter 1 - FAIL!
First thing I tried was the SGS unlock tool along with the Windows script that extracts the unlock code. Don't even bother trying - it doesn't work because our phone is different! Then I started tinkering with adb, getting into the shell and poking around. First thing I noticed that in the adb shell, you do not have read access in the /efs directory! Hmm, looks like I need root access to get to the files in here!
I also installed Terminal Emulator on my phone to see if I could get into the /efs directory - same result. The shell user didn't have the elevated privileges to get into that directory.
So poking around, there's talk of the z4root app. Unfortunately, by the time I find this app it's no longer listed in the Android Marketplace. I try downloading it straight off of the thread above, but it wouldn't install! It said that my device was not supported.
This stumped me for a while since I couldn't side load z4root off of the site. Then doing some more reading, I learned how I could run the z4root.apk file off of a file manager.
Chapter 2 - Root!
I mounted my phone in mass storage mode and saved z4root.apk onto it. Then using a file manger, I navigated to the location where I saved it and installed it with no problems! Once installed, I launched the app and it what it needed to do to root my phone.
Chapter 3 - Extracting nv_data.bin!
Now that I have root access, I can now get nv_data.bin out of the /efs directory and place it onto the SD card for easy extraction onto my PC.
You can either do the following steps either using Terminal Emulator on the phone itself (which is just like opening up a command-line shell) or connecting your phone in debug mode and using "adb shell" on your computer. I did use both methods to type in commands to my phone. Using "adb shell" was easier to type on a real keyboard but I had no problems in either environment.
So without further ado, here are the commands I typed in. Please note that when you see "$" this is the regular user shell prompt and "#" is the super user shell prompt. Also, my comments and explanations are italicized.
Start either shell and you'll get this prompt:
$ su type the command su at the dollar sign prompt and press enter. This will turn on "super user" mode.
# This is the new prompt identifying su mode. To exit this mode, you can type the command exit and you'll get back to the $. Type exit again, and you'll quit/close the shell. Don't do it now as we just got started.
# cd /efs This will "change directory" into the efs directory where all the goodies reside![/efs]
# ls -l -a This will list out all of the details of what is in this directory. You'll see something similar below
drwxrwxrwx root root 2005-01-01 16:33 .android
-rwx------ radio radio 32 2010-12-12 07:06 nv_data.bin.md5
-rw-rw-rw- radio radio 1743 2010-10-25 15:08 nv.log
-rwx------ radio radio 1048576 2010-10-25 15:08 .nv2.bak
-rw-rw-rw- radio radio 1 2010-10-25 15:08 .nv_state
-rwx------ radio radio 2097152 2010-12-12 07:06 nv_data.bin
-rwx------ radio radio 32 2010-10-25 15:08 .nv2.bak.md5
drwxrwxrwx radio radio 2010-10-25 14:37 imei
-rwx------ radio radio 2097152 2010-10-25 15:08 .nv_data.bak
-rwx------ radio radio 32 2010-10-25 15:08 .nv_data.bak.md5
If you see something like the above, you're good to go! If you get permission denied or something like that, you didn't root your phone. Assuming all is good, we need to make a place to copy the nv_data.bin file
# cd /sdcard This will change directory to the sdcard directory. When you mount your Android's internal storage, you have access to this as a removable drive.
# mkdir efs_backup This will make a directory on your internal sd card called efs_backup
# busybox cp -d -r /efs /sdcard/efs_backup This calls the copy command and will copy all of the files and directory structure in the /efs directory and put it in the /sdcard/efs_backup directory.
Chapter 4 - Generating the new nv_data.bin
Now you can exit super user and the shell.
Mount your phone as a drive on your computer. Go to http://www.communityhosting.net/sgsunlock/ and submit your nv_data.bin file to this site. You can choose an unlock and unfreeze code, but according to the SGH-I896 wiki, the unlock/unfreeze codes will not work however your phone will be unlocked and you can use any SIM in it.
You'll be prompted to download and save it on your computer. Make a new directory on your phone's SD internal card called "efs_unlocked" and save your downloaded nv_data.bin file in this directory. Safely remove and unmount your phone and get back into a shell.
Chapter 5 - Putting it back together
$ ls /sdcard/efs_unlocked You should see the file nv_data.bin listed in this directory. If you don't see the output similar to the one below, STOP! Find the new nv_data.bin file before moving on!
nv_data.bin If you see this file listed, you're good to go!
$ su
# rm /efs/nv* remove all files in the efs directory that start with "nv"
# rm /efs/.nv* remove all hidden files starting with ".nv"
# busybox cp /sdcard/efs_unlocked/nv_data.bin /efs This will copy the modified nv_data.bin file into the /efs directory
# chmod 700 /efs/nv_data.bin Set the read-write-execute permissions on nv_data.bin.
# chown radio.radio /efs/nv_data.bin Change ownership and group membership both to radio
# reboot
If all goes well, you've wiped out all the nv_data files and copied over the new nv_data.bin file. As the phone boots up, it will rebuild the necessary data files. My phone booted up normally. Hopefully yours will too.
Get back into the shell - time to check a few more things.
$ su
# ls -l -a /efs
drwxrwxrwx root root 2005-01-01 16:33 .android
-rwx------ radio radio 32 2010-12-12 07:06 nv_data.bin.md5
-rw-rw-rw- radio radio 1743 2010-12-12 15:08 nv.log
-rwx------ radio radio 1048576 2010-12-12 15:08 .nv2.bak
-rw-rw-rw- radio radio 1 2010-12-12 15:08 .nv_state
-rwx------ radio radio 2097152 2010-12-12 07:06 nv_data.bin
-rwx------ radio radio 32 2010-12-12 15:08 .nv2.bak.md5
drwxrwxrwx radio radio 2010-10-25 14:37 imei
-rwx------ radio radio 2097152 2010-12-12 15:08 .nv_data.bak
-rwx------ radio radio 32 2010-12-12 15:08 .nv_data.bak.md5
If you see an nv_data.bin.md5 file like in the example above, then things are in good shape! If there is no nv_data.bin.md5 file, then the original instructions say that you need to reflash your ROM with another version that does rebuild the file. Mine worked so I didn't have to worry about using a different ROM. Also, according to the official instructions at Step 9 it says to make .bak backup copies of the nv_data.bin and nv_data.bin.md5 files. I did not as these files were re-built during the reboot process.
# busybox cp -d -r /efs /sdcard/efs_unlocked Makes a copy of your new files back onto your internal sd card.
# reboot recovery Your phone should now reboot into recovery mode. Follow the instructions on the recovery mode menu and choose the "delete cache data" and then reboot your phone.
Finale
Congratulations! You've now rooted and unlocked your phone! I did test my phone with a Telus SIM card in it. I didn't do a full test - just checked to see if it got any bars of cell reception and of course it did. My phone did not ask for an unlock code either.
I recommend you copy your efs_original and efs_unlocked directories and store them somewhere safe as an off-phone backup.
I'd also like to thank the Android developers who spent their hard earned time, money and effort to make these tools for us to use! All I want to accomplish with this post is a record of what to do for those of us with the current issue Rogers Captivate S.
Without these tools, we'd be stuck with just "regular phones"
Good luck unlocking and rooting your phones
LaterZ!
Darren!!

Hi HO! Great post!

Didnt work for me...
everything executed as said but when finally rebooted the phone it didnt get unlocked instead it keeps booting over and over...
STUCK

Now i am at the boot loop. It keeps booting as soon as lock screen comes up i touch the screen or connect usb cable it turns off.
dont know if i bricked my phone.!!!!!
please help anyone
P.S. i already did odin3 to put stock rom since i can get in download mode but no help

These were pretty much exact steps I used to unlock my Rogers Captivate. Good write up.
Sent from my SAMSUNG-SGH-I896 using XDA App

asadsheraz said:
Now i am at the boot loop. It keeps booting as soon as lock screen comes up i touch the screen or connect usb cable it turns off.
dont know if i bricked my phone.!!!!!
please help anyone
P.S. i already did odin3 to put stock rom since i can get in download mode but no help
Click to expand...
Click to collapse
If you can still get into download mode, it's fixable. If Odin didn't work try Heimdall, few people were successful flashing stock back to Rogers Captivate with it. You might have to restore your original nv_data.bin from the backup manually.
Sent from my SAMSUNG-SGH-I896 using XDA App

sshvetsov said:
If you can still get into download mode, it's fixable. If Odin didn't work try Heimdall, few people were successful flashing stock back to Rogers Captivate with it. You might have to restore your original nv_data.bin from the backup manually.
Sent from my SAMSUNG-SGH-I896 using XDA App
Click to expand...
Click to collapse
I did make backup but how do I access the internal SD to restore backup? Since computer wont detect phone either as it keeps restarting.

Hmm, good question. I usually make a backup of my things to computer. When you patched the nv_data.bin file, didn't you pull it with adb? Perhaps you still have that file around someplace?
Sent from my SAMSUNG-SGH-I896 using XDA App

sshvetsov said:
Hmm, good question. I usually make a backup of my things to computer. When you patched the nv_data.bin file, didn't you pull it with adb? Perhaps you still have that file around someplace?
Sent from my SAMSUNG-SGH-I896 using XDA App
Click to expand...
Click to collapse
No... i was using the android terminal emulator to make backup and what not. Didn't copy it to computer but even if I did how'd I put it back since I cant access the internal SD....

Did it get stuck in the reboot loop after the first reboot?

asadsheraz said:
No... i was using the android terminal emulator to make backup and what not. Didn't copy it to computer but even if I did how'd I put it back since I cant access the internal SD....
Click to expand...
Click to collapse
You might need it later, after you restore your phone with Odin or Heimdall.
Sent from my SAMSUNG-SGH-I896 using XDA App

sshvetsov said:
You might need it later, after you restore your phone with Odin or Heimdall.
Sent from my SAMSUNG-SGH-I896 using XDA App
Click to expand...
Click to collapse
it just wont come up. Even after trying both restoring procedures it keeps booting over and over.
Also yes it started the boot loop from the first boot

Thank you SOOOOO MUCH Penphoe ! I've been trying to unlock my Rogers Captivate i896 for 2 weeks now, and it's now done thanks to you!
I just followed every step using a terminal emulator on my phone. I now works with a Telus and a european SIM card.

SUCCESS!
I am on Rogers with a Galaxy S Captivate which I bought a couple days prior.
THIS SOLUTION WORKS! THANK YOU SO MUCH!

Works like a charm!!!
I have I896 Galaxy S Captivate (purchased and locked for Rogers)
Just make sure you understand and do every step right.

sent it back to samsung after the boot loop issue.
on their website it shows tech replaced TIB.
Does anyone know what that is?

European Sim Issue
I completed this procedure a few days before the posting and everything worked in Canada on the rogers network.
I needed to root and unlock the phone for a trip to France over the holidays.
Once arriving in France, and using Rogers sim, the voice phone calls would not work, only a weird static in the background when someone talked. Text messages and data seemed to function. I used this same sim with an unlocked blackberry in the past with no issues.
I have tried using an SFR sim with the phone now and the same issue, text messaging and data works but the voice calls still do not function, connection is made but nothing can be heard.
Has anyone made a phone call with a European sim card after completing the unlocking? Most people say they register with the network and did not try a voice call.
Any suggestions?
Is there a procedure to re-lock the phone?

Rickets said:
I completed this procedure a few days before the posting and everything worked in Canada on the rogers network.
I needed to root and unlock the phone for a trip to France over the holidays.
Once arriving in France, and using Rogers sim, the voice phone calls would not work, only a weird static in the background when someone talked. Text messages and data seemed to function. I used this same sim with an unlocked blackberry in the past with no issues.
I have tried using an SFR sim with the phone now and the same issue, text messaging and data works but the voice calls still do not function, connection is made but nothing can be heard.
Has anyone made a phone call with a European sim card after completing the unlocking? Most people say they register with the network and did not try a voice call.
Any suggestions?
Is there a procedure to re-lock the phone?
Click to expand...
Click to collapse
I've used this method on my Rogers Captivate and am successfully using it in Indonesia (voice, data, sms) with local SIM.
I doubt just the unlock would cause the problem you're describing. Did you by any chance flash any custom firmware or modem.bin?
I haven't tried to re-lock my phone, I'm guessing it would be almost the same procedure, but instead of pushing patched nv_data.bin file you would have to restore your original, unpatched nv_data.bin file from backup.

sshvetsov said:
I've used this method on my Rogers Captivate and am successfully using it in Indonesia (voice, data, sms) with local SIM.
I doubt just the unlock would cause the problem you're describing. Did you by any chance flash any custom firmware or modem.bin?
I haven't tried to re-lock my phone, I'm guessing it would be almost the same procedure, but instead of pushing patched nv_data.bin file you would have to restore your original, unpatched nv_data.bin file from backup.
Click to expand...
Click to collapse
Thanks for the response, i have not attempted any custom firmware of modem.bin changes.
Did you use sgsunlock or the method posted in this string? SGSunlock would not work when i attempted.
http://forum.xda-developers.com/showthread.php?t=831569
Found the link to this via mobilesyrup
http://mobilesyrup.com/forum/showthread.php?t=4355
This is the orginal posting i used to unlock the i896 after rooting with z4root
When the unlock was completed the EFS folder had a file called nv_data.bin.md5, what is the purpose of this file? It seems to be created when the phone is rebooted after applying the new nv_data.bin. What files were in the original EFS folder before applying the unlock? Did the *.md5 files exist?

Rickets said:
Thanks for the response, i have not attempted any custom firmware of modem.bin changes.
Did you use sgsunlock or the method posted in this string? SGSunlock would not work when i attempted.
http://forum.xda-developers.com/showthread.php?t=831569
This is the orginal posting i used to unlock the i896 after rooting with z4root
When the unlock was completed the EFS folder had a file called nv_data.bin.md5, what is the purpose of this file? It seems to be created when the phone is rebooted after applying the new nv_data.bin. What files were in the original EFS folder before applying the unlock? Did the *.md5 files exist?
Click to expand...
Click to collapse
The method in the thread you're linking to is for Froyo (Android 2.2), but aside from few small OS specific difference it is exactly the same as the sgsunlock web site and the original post of this thread. I used the instructions from http://www.communityhosting.net/sgsunlock/ site (not SGS Unlock app from the market) on my Rogers Captivate, since they are for Eclair (Android 2.1), and they worked perfectly. This thread just adds details on how to root your Rogers Captivate with z4root before you unlock it.
md5 file contains the hash/checksum of the nv_data.bin file, it is generated on restart. I'm not sure exactly what is the purpose of that file, but I'm guessing it is there to make sure that nv_data.bin file is not corrupt or has been modified.
There were several files in the /efs folder, from my memory: nv_data.bin, nv_data.bin.md5, .nv_data.bak, .nv_data.bak.md5, imei, nv.log and maybe a couple more. Most of them are deleted during the unlock procedure and regenerated on restart. The most important of them is nv_data.bin. This is the file you patch to unlock your phone, and I'm guessing this is the file you would have to restore to re-lock it.

[Q] how can i relock my bootloader ?

unlocked my bootloader running official stock
would like to lock it so i can upgrade and flash a rom.
i saw this thread : http://forum.xda-developers.com/showthread.php?t=1675312
but the only problem is that i didnt save my original files
so the question is, how can i relock my bootloader ?

I believe the command for it was fastboot oem lock but please check the q and a section the answer is there
Sent from my HTC One X using Tapatalk 2

The_Zodiac said:
unlocked my bootloader running official stock
would like to lock it so i can upgrade and flash a rom.
i saw this thread : http://forum.xda-developers.com/showthread.php?t=1675312
but the only problem is that i didnt save my original files
so the question is, how can i relock my bootloader ?
Click to expand...
Click to collapse
The only original file you need is the Unlock_code.bin. They emailed this to you, that's the only way you can get the file. So if you did not delete the email, you can just go and download it again from your email. If you did delete it, it's most likely still in your email's trash bin.
BTW you do not need any original files to relock. Just boot back into fastboot usb mode and do as they said in the thread "fastboot oem lock"

I still have the file that htc emailed me. But in the instructions it list needing to move 2 other files to the android folder you create.
So basically just move the unlock.bin to that folder and follow the instructions as normal?
Sent from my HTC One X using xda premium

Are you talking about these 3 files adb.exe, AdbWinApi.dll, fastboot.exe? Really he shouldnt have said to move them. You can leave them where they are at. On your PC navigate to C:\Android\platform-tools and they should all be there still. Look and see if they are. If they are not, then I can send them to you.
If they are still there, then you just navigate to that directory in CMD prompt and follow his instructions. Where he says to navigate to C:\Android you instead navigate directly to C:\Android\platform-tools in cmd. Does that make sense?

NguyenHuu said:
Are you talking about these 3 files adb.exe, AdbWinApi.dll, fastboot.exe? Really he shouldnt have said to move them. You can leave them where they are at. On your PC navigate to C:\Android\platform-tools and they should all be there still.
Click to expand...
Click to collapse
I never had a directory called C:\android\platform-tools. I could not get any fastboot commands to work without having those 3 other files in the same directory as the Unlock_code.bin I was trying to push. Which is why I told them to put them together, to avoid the same issue I was having.

freshleysnipes said:
I never had a directory called C:\android\platform-tools. I could not get any fastboot commands to work without having those 3 other files in the same directory as the Unlock_code.bin I was trying to push. Which is why I told them to put them together, to avoid the same issue I was having.
Click to expand...
Click to collapse
if you update your SDK to the latest you will see. Everyone should update their sdk once every month or so. you put your unlock file in that folder too, it's same instructions they tell you, but instead of moving those files out, you keep them there and you move your unlock file in. so you don't break the SDK for future stuff.

NguyenHuu said:
Are you talking about these 3 files adb.exe, AdbWinApi.dll, fastboot.exe? Really he shouldnt have said to move them. You can leave them where they are at. On your PC navigate to C:\Android\platform-tools and they should all be there still. Look and see if they are. If they are not, then I can send them to you.
If they are still there, then you just navigate to that directory in CMD prompt and follow his instructions. Where he says to navigate to C:\Android you instead navigate directly to C:\Android\platform-tools in cmd. Does that make sense?
Click to expand...
Click to collapse
I never had that folder created if you could send them to me that would be awesome
Sent from my HTC One X using xda premium

The_Zodiac said:
I never had that folder created if you could send them to me that would be awesome
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
sure you can download it here http://www.mediafire.com/?dn8py7ww4rsbi5e
Just extract it to the same folder in that other thread then to keep it simple.

NguyenHuu said:
sure you can download it here http://www.mediafire.com/?dn8py7ww4rsbi5e
Just extract it to the same folder in that other thread then to keep it simple.
Click to expand...
Click to collapse
Thanks for the help I'll give it a shot when I get home from work
Sent from my HTC One X using xda premium

Root 2.20 ThinkTank [Absolutely NO off-topic discussion]

It's that time again kids.
I Ran the 2.220 RUU on my HOX today just to see if ANYTHING we used to be able to do would work.
/data/local is still write protected so the easy ways won't work.
I do have a question regarding write protection on partitions though. Do any of the low level tools we have contain the ability to push files to write protected partitions? Or change the condition of said partitions, even temporarily?
I'm sure this has been tried but I've never tried it so I'm asking.

DOH asking MOD to move

I'm no dev by any means, so I may sound stupid here.
But I was messing around with some stuff yesterday and noticed that, even though data/local is WP, you can still create a new directory within data/local, like data/local/temp, and then that new directory you can write to and copy files to (I had tried playing around with the debugfs root stuff)
Like I said, probably worthless, just an observation.

GuyIncognito721 said:
I'm no dev by any means, so I may sound stupid here.
But I was messing around with some stuff yesterday and noticed that, even though data/local is WP, you can still create a new directory within data/local, like data/local/temp, and then that new directory you can write to and copy files to (I had tried playing around with the debugfs root stuff)
Like I said, probably worthless, just an observation.
Click to expand...
Click to collapse
so if you changed the debugfs script to point to /data/local/temp did it get you temp root?

gunnyman said:
so if you changed the debugfs script to point to /data/local/temp did it get you temp root?
Click to expand...
Click to collapse
All the files were pushed successfully, but upon reboot (part of the script) I got an error with something along the lines of "failed to load filesystem".
After some reading in the GS3 forums, I think it might have something to do with /data and /system being on different partitions?

It's a start. Did the files you put in data/local/temp stay after the reboot?

gunnyman said:
so if you changed the debugfs script to point to /data/local/temp did it get you temp root?
Click to expand...
Click to collapse
gunnyman said:
It's a start. Did the files you put in data/local/temp stay after the reboot?
Click to expand...
Click to collapse
Yup

Ok then I think we have something to work with. Time for smarter folks than me to chime in

Maybe I'm ignorant but wouldn't that created folder have different permissions than a folder that was existing?
So anything in that folder would not be able to execute anything
Sent from my HTC One X using Tapatalk 2

Let me go back on what I said.
You cannot create a new dir in data/local as you get permission denied. However, you can write/push to data/local/tmp, and those files persist after reboot.

superchilpil said:
Maybe I'm ignorant but wouldn't that created folder have different permissions than a folder that was existing?
So anything in that folder would not be able to execute anything
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
I dunno, that's what this thread is for

GuyIncognito721 said:
Let me go back on what I said.
You cannot create a new dir in data/local as you get permission denied. However, you can write/push to data/local/tmp, and those files persist after reboot.
Click to expand...
Click to collapse
Anyways, this is what is output after editing the dirs to point to /data/local/tmp and rebooting:
Step 2 - Rooting...
For this step, ignore any error messages that say "File not found"
debugfs 1.42 (29-Nov-2011)
/dev/block/mmcblk0p33: Permission denied while opening filesystem
debugfs: rm: Filesystem not open
debugfs: rm: Filesystem not open
debugfs: cd: Filesystem not open
debugfs: write: Filesystem not open
debugfs: set_inode_field: Filesystem not open
debugfs: set_inode_field: Filesystem not open
debugfs: set_inode_field: Filesystem not open
debugfs: rm failed for /data/local//tmp/tmp, No such file or directory
failed on '/data/local/tmp/tmp.bak' - No such file or directory
Rebooting...
Once your devices has finished restarting,
Press any key to continue . . .
Waiting for device to be detected...
******
Can someone running 1.85 firmware copy and paste your output when you run 'mount' via adb shell?

OK I'll go ahead and chime in here since I've spent at least 40 hours trying to find root on 2.20....
1.) /data/local is not WP. We just aren't allowed to be there, just like 1.85
2.) /data/local/tmp is shell writeable just like 1.85
3.) The 1.85 exploit (WR directory in redbend) is patched and unuseful
4.) debugfs won't do anyone any good as the block device is not WR. That app is only useful if the OEM left the block device WR or you can trick the system into making the block device WR via a symbolic link attack or something similar.
5.) "mount" outpout isn't useful for debugfs as debugfs opens the actual block device. If you want to see those permissions, simply "ls -l /dev/block/mmcblk*".
Gunny - did you actually run the 2.20 RUU? You probably didn't want to do that.

Yeah I did. It's okay. I never flash radios and know how to push a boot.img via fast boot.

gunnyman said:
Yeah I did. It's okay. I never flash radios and know how to push a boot.img via fast boot.
Click to expand...
Click to collapse
My concern is that likely any hope for s-off is going to involve pushing/breaking hboot, which you are now unable to do.

I thought about that too. I'm okay with what I did. No biggie.

Has anyone tried
adb push root.method /iHox/or_else
Sent from my SPH-L710 using xda premium

gunnyman said:
I thought about that too. I'm okay with what I did. No biggie.
Click to expand...
Click to collapse
Cool.
Sent from my HTC One X using xda app-developers app

beaups said:
Cool.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
besides the time will come where you can't GET a phone with the older HBoot anymore.

I am still on 1.85, so please let me know if you need any help in testing / any info
From beast called HTC One X

HELP!!!! BOOTLOOP atrix 2

im stuck in a loopboot on my ME865 after installing 4.2.2 from this http://forum.xda-developers.com/showthread.php?t=2121029
i flashed the rom but didnt flash the gapps because it said to do it after with built in recovery but i didnt know how to so i used this http://forum.xda-developers.com/showthread.php?t=1346977
which got me into the loop boot i can boot into fastmode
PLEASE HELP ME!!!!!!

DaFrenchTaco said:
im stuck in a loopboot on my ME865 after installing 4.2.2 from this http://forum.xda-developers.com/showthread.php?t=2121029
i flashed the rom but didnt flash the gapps because it said to do it after with built in recovery but i didnt know how to so i used this http://forum.xda-developers.com/showthread.php?t=1346977
which got me into the loop boot i can boot into fastmode
PLEASE HELP ME!!!!!!
Click to expand...
Click to collapse
Well, first, turn off the phone and charge it so you don't loose battery.
Second, never install another recovery on top of an existing one without knowing what you are doing - ask first.. (You get into the built-in recovery on that cm10.1 by tapping the volume down button at the end of the red moto logo when the lights come on).
Next, you could possibly fix your system with adb and switching some files.. but that would take a lot of explaining if you are not familiar with it.. plus, you might not get adb recognized during the bootloop.
So, you need to use the FXZ files for your phone/region... Or, just flash the system.img only.. See here: http://forum.xda-developers.com/showpost.php?p=41436876&postcount=1106 - and see the link linked there.
EDIT: If you can get adb recognized, you might be able to just run these few lines to fix things from the command prompt:
Code:
adb shell
su
mount -o rw,remount /system
rm /system/bin/hijack
sh /system/bin/finalize_release
exit

alteredlikeness said:
Well, first, turn off the phone and charge it so you don't loose battery.
Second, never install another recovery on top of an existing one without knowing what you are doing - ask first.. (You get into the built-in recovery on that cm10.1 by tapping the volume down button at the end of the red moto logo when the lights come on).
Next, you could possibly fix your system with adb and switching some files.. but that would take a lot of explaining if you are not familiar with it.. plus, you might not get adb recognized during the bootloop.
So, you need to use the FXZ files for your phone/region... Or, just flash the system.img only.. See here: http://forum.xda-developers.com/showpost.php?p=41436876&postcount=1106 - and see the link linked there.
EDIT: If you can get adb recognized, you might be able to just run these few lines to fix things from the command prompt:
Code:
adb shell
su
mount -o rw,remount /system
rm /system/bin/hijack
sh /system/bin/finalize_release
exit
Click to expand...
Click to collapse
do you know any other place to download the zip file
and wheres the fxz folder supposed to be

DaFrenchTaco said:
do you know any other place to download the zip file
and wheres the fxz folder supposed to be
Click to expand...
Click to collapse
Look here
http://forum.xda-developers.com/showthread.php?t=2176124
Make sure you install the correct firmware otherwise you will brick.
And next time please search before posting. This has been asked a number of times before
Sent from my MB865 using XDA Premium HD app

nikhJ said:
Look here
http://forum.xda-developers.com/showthread.php?t=2176124
Make sure you install the correct firmware otherwise you will brick.
And next time please search before posting. This has been asked a number of times before
Sent from my MB865 using XDA Premium HD app
Click to expand...
Click to collapse
No. Those are only MB865. And those are only for gingerbread..
The 4.0.4 ME865 ones are here: http://forum.xda-developers.com/showthread.php?t=1934874
Also, it's a little outdated, but see here too: http://forum.xda-developers.com/showthread.php?t=1909319
Which should all lead you here: http://sbf.droid-developers.org/edison/list.php
Sent from my manta ray

alteredlikeness said:
No. Those are only MB865. And those are only for gingerbread..
The 4.0.4 ME865 ones are here: http://forum.xda-developers.com/showthread.php?t=1934874
Also, it's a little outdated, but see here too: http://forum.xda-developers.com/showthread.php?t=1909319
Which should all lead you here: http://sbf.droid-developers.org/edison/list.php
Sent from my manta ray
Click to expand...
Click to collapse
sorry for asking u so much stuff but i lost without help
ok so it says i have to edit it with the moto android depacker but i dont see any tutorials on how to do that
would it boot up if i use this hack to install the honk kong boot img on to it or would mess my device since its on "4.2.2." http://forum.xda-developers.com/showthread.php?p=35000737

DaFrenchTaco said:
sorry for asking u so much stuff but i lost without help
ok so it says i have to edit it with the moto android depacker but i dont see any tutorials on how to do that
would it boot up if i use this hack to install the honk kong boot img on to it or would mess my device since its on "4.2.2." http://forum.xda-developers.com/showthread.php?p=35000737
Click to expand...
Click to collapse
I am very confused at what you want to do. That link is only to root your device. But, if you are bootlooping, you need to replace your system.img.
You should download the entire SBF/FXZ zip file for your device/region/firmware. Then unzip it into a folder on your computer (best if it's close to C:\ with spaces in the path). Are you using a Windows OS on your computer?
Then, grab the restore-to-ics_win-batch.zip AND the restore-ics-system-only.bat.txt (remove the .txt extension) attached in this post: http://forum.xda-developers.com/showpost.php?p=36834775&postcount=108
Mix those files in with the big FXZ files that you just unzipped. Then run the .bat file to flash the system.img only. If that doesn't work, then open the other .bat file (use Notepadd++ or similar), check that everything that is being flashed is actually in your folder and has the same name... and flash the entire FXZ. If none of that helped, then you probably flashed the wrong files to your phone.
Just flashing the system.img only is probably the safest.. Because if it's wrong, you can just flash another one. The other files in the FXZ package can mess up your phone if they are not for your specific device.
EDIT: If you still did not flash anything else, you could try to use adb... Get that restore-to-ics_win-batch.zip that I linked above.. Unzip it to your desktop. Power on your phone so it bootloops and connect with USB. Open a command prompt on the restore-to-ics_win-batch folder by holding down shift and right-click. Then type adb devices - if it returns a number with the word "device" (not the word "offline"), then you can try to use those adb codes I posted in my previous post. Otherwisem you need to use fastboot and flash fxz or system only.

alteredlikeness said:
I am very confused at what you want to do. That link is only to root your device. But, if you are bootlooping, you need to replace your system.img.
You should download the entire SBF/FXZ zip file for your device/region/firmware. Then unzip it into a folder on your computer (best if it's close to C:\ with spaces in the path). Are you using a Windows OS on your computer?
Then, grab the restore-to-ics_win-batch.zip AND the restore-ics-system-only.bat.txt (remove the .txt extension) attached in this post: http://forum.xda-developers.com/showpost.php?p=36834775&postcount=108
Mix those files in with the big FXZ files that you just unzipped. Then run the .bat file to flash the system.img only. If that doesn't work, then open the other .bat file (use Notepadd++ or similar), check that everything that is being flashed is actually in your folder and has the same name... and flash the entire FXZ. If none of that helped, then you probably flashed the wrong files to your phone.
Just flashing the system.img only is probably the safest.. Because if it's wrong, you can just flash another one. The other files in the FXZ package can mess up your phone if they are not for your specific device.
EDIT: If you still did not flash anything else, you could try to use adb... Get that restore-to-ics_win-batch.zip that I linked above.. Unzip it to your desktop. Power on your phone so it bootloops and connect with USB. Open a command prompt on the restore-to-ics_win-batch folder by holding down shift and right-click. Then type adb devices - if it returns a number with the word "device" (not the word "offline"), then you can try to use those adb codes I posted in my previous post. Otherwisem you need to use fastboot and flash fxz or system only.
Click to expand...
Click to collapse
can not load "system.img" i went in and edited the the text to C:\system.img but it wont work
i tried the other one didnt work is the path supposed to be = C... or =C... what i mean is there a space or not
is the bat file scripted to work with me865 or only with mb865 flashing that sbf/fxz
and is the sbf/fxz file supposed to be unzipped and in a folder
or compressed

DaFrenchTaco said:
can not load "system.img" i went in and edited the the text to C:\system.img but it wont work
i tried the other one didnt work is the path supposed to be = C... or =C... what i mean is there a space or not
is the bat file scripted to work with me865 or only with mb865 flashing that sbf/fxz
and is the sbf/fxz file supposed to be unzipped and in a folder
or compressed
Click to expand...
Click to collapse
Unzip the sbf/fxz - all the files in a single folder, on your desktop or in the root of your C:\ drive (like C:\ InlineFlashing_Edison_XX-XX-XX_CFC_P3_APBP.xml - where that is the name of the folder)
Then put the .bat file and other files from my restore_to_ics zip and the restore_system_only .bat in that same folder.
Then, connect with USB while in AP fastboot mode, see if it says "OK to program", then double-click the restore-ics-system-only.bat

alteredlikeness said:
Unzip the sbf/fxz - all the files in a single folder, on your desktop or in the root of your C:\ drive (like C:\ InlineFlashing_Edison_XX-XX-XX_CFC_P3_APBP.xml - where that is the name of the folder)
Then put the .bat file and other files from my restore_to_ics zip and the restore_system_only .bat in that same folder.
Then, connect with USB while in AP fastboot mode, see if it says "OK to program", then double-click the restore-ics-system-only.bat
Click to expand...
Click to collapse
thank u so much is it safe to root and install cm10 with bootstrap?
and how do you enter cmw in cm10.1?
THX

Sorry to intrude with my following off-topic statement, but that was a lot of detailing you did there altered. xD Great job and it'll serve well to assist others who need the same solution.
Now on-topic;
Yes it's okay to root with any of the ICS root methods available.
Sent from the Ace's MB865 using xda app-developers app

Aceofzeroz said:
Sorry to intrude with my following off-topic statement, but that was a lot of detailing you did there altered. xD Great job and it'll serve well to assist others who need the same solution.
Now on-topic;
Yes it's okay to root with any of the ICS root methods available.
Sent from the Ace's MB865 using xda app-developers app
Click to expand...
Click to collapse
yeah true that this is a very detailed guide/thread i hope my problem will help all the others now that i know how it feels to mess up a two day old phone

alteredlikeness said:
No. Those are only MB865. And those are only for gingerbread..
The 4.0.4 ME865 ones are here: http://forum.xda-developers.com/showthread.php?t=1934874
Also, it's a little outdated, but see here too: http://forum.xda-developers.com/showthread.php?t=1909319
Which should all lead you here: http://sbf.droid-developers.org/edison/list.php
Sent from my manta ray
Click to expand...
Click to collapse
Ah..sorry my bad..Forgot his phone was me865..

Question about the original problem
DaFrenchTaco said:
im stuck in a loopboot on my ME865 after installing 4.2.2 from this http://forum.xda-developers.com/showthread.php?t=2121029
i flashed the rom but didnt flash the gapps because it said to do it after with built in recovery but i didnt know how to so i used this http://forum.xda-developers.com/showthread.php?t=1346977
which got me into the loop boot i can boot into fastmode
PLEASE HELP ME!!!!!!
Click to expand...
Click to collapse
Did you solve this? I have the same problem...
---------- Post added at 10:17 PM ---------- Previous post was at 10:01 PM ----------
alteredlikeness said:
No. Those are only MB865. And those are only for gingerbread..
The 4.0.4 ME865 ones are here: http://forum.xda-developers.com/showthread.php?t=1934874
Also, it's a little outdated, but see here too: http://forum.xda-developers.com/showthread.php?t=1909319
Which should all lead you here: http://sbf.droid-developers.org/edison/list.php
Sent from my manta ray
Click to expand...
Click to collapse
I encounter the same issue. I am not able to see the device in ADB.exe, but I am able to see in FASTBOOT.exe
Can I flash in FASTBOOT.exe?
Thank you

pa 3.60 problem from altered likeness
I tried to install Paranoid android 3+ from the link from altered likeness which was successful but the problem started after rebooting .The animation goes on forever and the first time the reboot gave me a message stating updating android system . Any solution to get back would be of a lot of help .I also have the recovery of my stock 4.0.4 done using CWM .

Same problem extension
Hi....
I faced the same problem and now after following the procedure facing a new prob.
Things I did
1. Upgraded from ICS to CM10.1--->Success
2. Forgot to install GAPPS ..so installed Atrix2Strap.apk (Bootloop problem started)
3. Flashed my atrix 2 with the procedure mentioned in the link by alteredlikeness.(Overcame the bootloop problem)
Now the problem is
I'm getting the lock screen but when I try to unlock it stays unresponsive.
How do I solve this. Please Help me out

Thnks guys
kyashwanth said:
Hi....
I faced the same problem and now after following the procedure facing a new prob.
Things I did
1. Upgraded from ICS to CM10.1--->Success
2. Forgot to install GAPPS ..so installed Atrix2Strap.apk (Bootloop problem started)
3. Flashed my atrix 2 with the procedure mentioned in the link by alteredlikeness.(Overcame the bootloop problem)
Now the problem is
I'm getting the lock screen but when I try to unlock it stays unresponsive.
How do I solve this. Please Help me out
Click to expand...
Click to collapse
Thanks guys for the wonderful tutorial...
Solved the issue by inserting a sim card into the phone.
Now I'm on CM 10.1