Related
Just updated post with more details, I hope someone will find it more useful. As always make sure you have a backup, make a backup of your nv_data.bin BEFORE editing.
I was not able to unlock my phone Froyo 2.2 I9000M phone running I9000UGJK4 firmware by using this official thread http://forum.xda-developers.com/showthread.php?t=761045
and after few hours of searching I found this method which worked for me from first attempt.
I give all the credits for this idea to cursor2010 from http://forum.xda-developers.com/showpost.php?p=8656481&postcount=156
Here are the detailed steps
* Your phone must be rooted (I used SuperOneClick http://forum.xda-developers.com/showthread.php?t=803682) to do this unlocking and busybox from market is installed
* Get the archive file from first post of this topic. The archive contains ADB software which we will use to connect to the phone.
* Turn On USB debugging Application->Settings->Application->Development
* Follow the instructions of STEP 4 from http://www.communityhosting.net/sgsunlock/i9000.html to get your nv_data.bin to your PC
Get your current nv_data.bin file from the /efs directory on your phone. This can be done with ADB. Most often, the nv_data.bin file is not readable and you will get a permission denied message. You'll need to enter the commands manually.
To do this with ADB, from the DOS command prompt you can type:
adb pull /efs/nv_data.bin
If you receive a permission denied error, you can fix it by typing the following commands from an ADB shell (type "adb shell" at the DOS command prompt) or from within a terminal on the phone:
adb shell
su
chmod 777 /efs/nv_data.bin
exit
exit
Then from the DOS command prompt:
adb pull /efs/nv_data.bin
Using Hex editor edit the file ( you can use any hex editor, http://www.logitheque.com/logiciels/windows/utilitaires/editeur_hexadecimal/telecharger/edithexa_9903.htm for example). I personally use UltraEdit.
View attachment 464171
At the offset of 180069H you will see your provider MCC and MNC codes see http://en.wikipedia.org/wiki/Mobile_Network_Code
In my case the code was 30261020404... which is Bell Canada, so I changed 610 to 720 Rogers Canada now the code is 30272020404...
Again the offset in the file is 180069H.
Save the file on the pc.
* Follow the instructions from http://forum.xda-developers.com/showpost.php?p=8182729&postcount=107
Copy your nv_data.bin to temporary folder on your phone:
adb shell "mkdir /sdcard/efs"
adb push nv_data.bin /sdcard/efs
adb shell
su
ls -l -a /efs
If there is an nv_data.bin.md5 file in the directory, all is well. You should continue with these commands:
mv /efs/.nv_data.bak /efs/.nv_data.bakk
mv /efs/.nv_data.bak.md5 /efs/.nv_data.bakk.md5
rm /efs/nv_data.bin
rm /efs/nv_data.bin.md5
rm /efs/.nv2.bak
rm /efs/.nv2.bak.md5
busybox cp /sdcard/efs/nv_data.bin /efs/nv_data.bin
chmod 755 /efs/nv_data.bin
chown radio.radio /efs/nv_data.bin
exit
exit
if you have errors on the chown command, use
chown 1001.1001 /efs/nv_data.bin
If there was no nv_data.bin.md5 file, then something is wrong and you'll need to see other options or reflash again with a known working ROM that generates a new MD5 file when it's missing.
* Reboot the phone, it should not ask any unlock codes or anything, in my case it simply just registered on Rogers network
* Obviously you also need to program your APN settings for Rogers from http://forum.xda-developers.com/showthread.php?t=809003 to make your 3G working. For your own provider please search forum.
I wish it would be much simpler or automated or tested on bigger variety of phones.If somebody could gather the statistics and check if this method is applicable throughout all the versions of I9000, that would be very nice.
Feel free to comment my post.
Phams0 said:
I had problems unlocking too. But the little trick that Happy Hunter posted worked. The phone is now locked to fido instead of bell.
I guess my phone is one of the newer builds. That's why the original unlocking method doesn't work.
I bought it a few days ago from Bell.
Model number: GT-I9000M
Firmware Version: 2.2
Baseband Version: I9000UGJK4
Kernel Version: 2.6.32.9 [email protected] #1
Build number: Froyo.UGJK4
Click to expand...
Click to collapse
in hex editor on phone jump to address look for 00181460 looked in the colums on the right of 00181460 and saw
ff ff ff ff ff ff ff ff 01 00 00 00 so i changed 01 to 00
that will make your phone sim free, u dont have to edit to lock just one network, i already try this tricked while leaving 610 as bell in the nv_data file, after i changed to 00 my rogers sim now work, so i assume it will work with other sims also
in my case this method did not work,
I try something different:
I changed too nv_data.bak and delete nv_data.bin.md5 and nv_data.bak.md5 and now my phone is unlocked
This is such a great written guide, i'd have been a shame to have it get lost inside that unlock topic
so I made it a topic of its own for all the new people trying to unlock Froyo
NOTE: in some HEX editor the offset reads as 181460
bizkopt said:
in my case this method did not work,
I try something different:
I changed too nv_data.bak and delete nv_data.bin.md5 and nv_data.bak.md5 and now my phone is unlocked
Click to expand...
Click to collapse
LOL !!!!
i can't believe it, this is the most ridiculous "lock' ever
i tried it and it truely works
just delete the files and it automatically becomes SIM free, it wont even ask you for the PIN
tried with 3 different SIM cards, all of them can call out and access to 3G
bizkopt said:
in my case this method did not work,
I try something different:
I changed too nv_data.bak and delete nv_data.bin.md5 and nv_data.bak.md5 and now my phone is unlocked
Click to expand...
Click to collapse
there is no friggin way it is that simple...isnt ur imei or some other pertinent info store in the files?
I can confirm this works, been using it for a month to switch vibrants over to Fido and Rogers.
dawen said:
in hex editor on phone jump to address look for 00181460 looked in the colums on the right of 00181460 and saw
ff ff ff ff ff ff ff ff 01 00 00 00 so i changed 01 to 00
that will make your phone sim free, u dont have to edit to lock just one network, i already try this tricked while leaving 610 as bell in the nv_data file, after i changed to 00 my rogers sim now work, so i assume it will work with other sims also
Click to expand...
Click to collapse
This worked great for me. Thanks!
sjavvaji said:
there is no friggin way it is that simple...isnt ur imei or some other pertinent info store in the files?
Click to expand...
Click to collapse
it is really that easy
i couldn't believe it myself either
so does that mean hex editing is unecessary.. since that would seem to inidicate that it would then be locked to whatever provider you change the code too.. So dont bother editing the file,,, just delete the files, as a side does still know when you are roming or not when you do it with this method.. i kinda doubt it?
Sorry for the newbie question. THis is the first time I root android phones.
1. My phone was originally 2.1 and I upgraded it to 2.2
2. I ran superoneclick and I can see "superuser" on my app list (I asume it is rooted)
3. unable to get nv_data.bin so I ran "ADB shell" at the dos prompt
4. when I hit "chmod 777 /efs/nv_data.bin" I got "unable to chmod...operation not permitted".
Please let me know what I can do to unlock. THanks.
try using root explorer in the market.
I managed to use andexplorer to look at the efs directory but it it was empty??
Awesome, just tried this on my 3rd Galaxy S Vibrant which came with JL2. Works brilliantly. Nothing else worked.
Does anyone know if this will survive a flash with a custom ROM?
Thanks
mklo said:
I managed to use andexplorer to look at the efs directory but it it was empty??
Click to expand...
Click to collapse
If you've installed Darky's Rom 8.1 you've most likely lost Root as I had. So do the following:
boot into recovery, go to Advanced Speedmod ULK features > Root/Install Superuser, and select the first option i.e 'Simple: install busybox+su'. If this doesn't work, turn on the phone, open Superuser, forget all the apps, then again boot into recovery and follow the above steps.
Click to expand...
Click to collapse
old post (not relevant anymore):
Same here. Root explorer only shows this:
/efs
5.01MB used, 935K free, r/w
..
Parent Folder.Any ideas?
make sure you are able to see hidden files
I don't want to pollute this thread but can someone be a bit more specific on what to do on the "simple" unlock shown below
bizkopt said:
in my case this method did not work,
I try something different:
I changed too nv_data.bak and delete nv_data.bin.md5 and nv_data.bak.md5 and now my phone is unlocked
Click to expand...
Click to collapse
I.e. "changed too nv_data.bak" means he renamed nv_data.bin to nv_data.bak
OR did he delete nv_data.bin and renamed .nv_data.bak to ny_data.bin?
I don't have nv_data.bak.md5 but I do have .nv_data.bak.md5 should I delete this other file?
(I don't mind the hex editing way but if there is a simpler way I'll try it first)
hey guys i am just wondering would this instruction help getting verizon samsung fascinate to be on sprint network and data working?
i have my fascinate on sprint already but i just never can get the 3G icon to come up
hello, excuse me I am completly new with SGS
where can I find these 2 files ? (internal card ??)
thanks for your reply
I used root explorer to get nv_data.bin on PC. Then got eXchange.rar, putted nv_data.bin from the phone in the same folder with Reparation_nv_data.jar nv_data.binvierge from eXchange.rar, ran Reparation_nv_data.jar, putted some 8 digit random numbers in filed one and two (different ones), copied nv_data.binvierge back to phone, renamed it to nv_data.bin, deleted EVERYTHING from /efs folder BESIDE nv_data.bin and .imei. Then got the battery off from the phone (not turning it off from power button), left like that for 5 seconds, back in, power on...TADA! Phone unlocked
It has to be rooted.
This is a method from razvang in romanian.
Preamble
What I write here is what I did. BUT I am not responsible of damages you could do your phones. Be careful and safe. If you do not know what you are doing, do not do this.
This is not a method to unbrick your phone. Unfortunately, I did not succeed to do that. It is a method to unroot: to cleanse any trace of rooting. In my case, it was to give it back to my store.
The rooting method I used is the "Universal Gingerbread Root (by StoneBoyTony)" I found here: http://forum.xda-developers.com/showthread.php?t=1192122 (scroll down a bit). This method is to root your Gingerbread phone through the recovery mode by unpacking a zip file (keep this file in mind). Thus, this tutorial is concerning this rooting method. I did not try with other rooting methods. So take care.
Code:
something to write
is what you have to type.
something to expect/read
Click to expand...
Click to collapse
is what you should read at your side.
Read before writing. Like students (should) do in classes.
My computer runs Windows XP SP3. Just saying.
This is my first thread. Please, be cool with me
Finally, do not confuse rooting and unlocking.
To root a phone is to allow the user to be a super-user on the phone, which means: to have greeeaaaat powers.
To unlock means to use any carrier with the phone by getting the unlock code.
Hence, to get the unlock code, you often have to root your phone to access to sensible data (cf. stl5 story).
I - Introduction
(= useless blabla but informative)
I bought some Samsung Gio cellphones (Bell prepaid, Canada) at a pretty good price ($80, thanks redflagdeals for the deal!), in order to go with another carrier (Chatr).
Characteristics of the Bell's Samsung Gio prepaid cell:
GT-S5660M
Gingerbread 2.3.4
S5660MUGKG3
GT-S5660DSMBMC
Click to expand...
Click to collapse
For the first one, I retrieved the unlock code through what I call the "stl5 way". It worked without any issue. Cool. Next!
For the second one... Oh snap.
Issues began after getting the unlock code and a rebooting. Kinda weird since I exactly did like the first one. Problems were:
No sound at the Samsung animation
Too many minutes to initialize
When I could reach the pad to call a number, the pad was so laaaaggggyyyy
Fly mode is stuck
No more IMEI (nooooooooooooo)
Doing *#7465625# does not display any information about the network lock, sp/cp lock (it displays labels but no values at all)
Turning off the cellphone was very long too...
...but it was not a shutdown: the cellphone was rebooting, weird
Random warnings (even got a warning from "com.android.phone"!)
Putting another SIM card from another carrier did not even notice me to unlock the phone
And so on. Like some folks, I did not really brick it, but like some others, the phone became... unusable.
What I call the "stl5 way" is the unlocking method which can succeed... or not, it depends. Weird isn't it? Unfortunately, I didn't know.
xda and rfd links which explain the stl5 unlocking method:
http://forum.xda-developers.com/showthread.php?t=1204705
http://forum.xda-developers.com/showthread.php?t=1192122
I absolutely advise against this method. BEWARE.
It seems that the /dev/stl5 partition is madly protected. When we use/read/smurf it, it corrupts some data of the phone which could lead to (partially) brick your phone.
Thus, the safest way (nobody failed) so far to unlock your phone is the "bml5 way":
http://forum.xda-developers.com/showpost.php?p=17148825&postcount=334
http://forum.xda-developers.com/showthread.php?p=17247878
II - Plat de résistance
Ok, you used the stl5 way and your phone just took 80yo: it is slow, forgot a lot of information, and some other symptoms I wrote earlier.
Or you just want to unroot your phone, because it's cool.
If there is still no method to unbrick (or it did not succeed), you can give it back to your store or to use the Samsung warranty. You may have to unroot it (get all chances on your side).
- Tools/weapons you will need:
Android Platform Tools, last version (don't need older ones)
Your Samsung Gio in debugging mode
Samsung Kies
Click to expand...
Click to collapse
Explanations:
Android Platform Tools
Click to expand...
Click to collapse
We will use the "adb" program, in order to use the phone terminal. You can also use an embedded terminal (free ones in the android market) or through ssh. It's your call.
Your Samsung Gio in debugging mode
Click to expand...
Click to collapse
Go to : Menu -> Applications -> Development -> USB debugging (green cross it). It will allow "adb" to be connected to the phone.
Samsung Kies
Click to expand...
Click to collapse
Download it here: www.samsung.com/ca/support/mobilesoftwaremanual/mobilesoftwaremanual.do?page=MOBILE.SOFTWARE.MANUAL
Kies is the iTunes-like by Samsung. This may be needed for your computer to detect your phone. But we do not need to launch it. Just install it but do not launch it while doing your stuff.
Step #1
In a Windows shell, go to your .\android-sdk\platform-tools directory (for the example: C:\Android\android-sdk\platform-tools>). Type:
Code:
> adb shell
This will link the computer to your phone and display a remote Android shell. At this point, you should see something like this:
C:\>Documents and Settings\superpizon>cd C:\Android\android-sdk\platform-tools
C:\Android\android-sdk\platform-tools>adb shell
$
Click to expand...
Click to collapse
($ is the prefix of the Android shell, do not type it)
(> is the one for the Windows shell, do not type it too)
Note : if your phone is not in debugging mode, the Windows shell will write:
error: device not found
Click to expand...
Click to collapse
Step #2
After madly browsing the xda method to unroot my phone, I found this post: http://forum.xda-developers.com/showpost.php?p=17078367&postcount=34. Interesting.
If you open the Universal_GB_ROOT.zip file, you have:
META-INF/
-com/
--google/
---android/
----update-binary
----updater-script
-CERT.RSA
-CERT.SF
-MANIFEST.MF
system/
-app/
--Superuser.apk
-xbin/
--busybox
--sh
--sqlite3
--su
--su-v1
--su-v2
--su-v3
Click to expand...
Click to collapse
If you did not notice, after rooting your phone, an unremovable application appeared in the menu application (the icon is a dead skull): this is the visible part of the iceberg that we want to remove.
Ok, your Android shell is waiting. Let's type:
Code:
$ ls /system/xbin
It should display:
dexdump
busybox
sh
sqlite3
su
su-v1
su-v2
su-v3
Click to expand...
Click to collapse
Happenstance? I don't think so. Now type:
Code:
$ ls /system/app/S*.apk
/system/app/SamsungApps.apk
/system/app/SamsungAppsUNAService.apk
/system/app/SamsungWidget_ProgramMonitor.apk
/system/app/SamsungWidget_StockClock.apk
/system/app/ScreenCaptureService.apk
/system/app/SecDownloadProvider.apk
/system/app/SecurityProvider.apk
/system/app/SelfTest.apk
/system/app/SerialNumberLabelIndicator.apk
/system/app/Settings.apk
/system/app/SettingsProvider.apk
/system/app/SetupWizard.apk
/system/app/Setup_Wizard.apk
/system/app/SisoDrmProvider.apk
/system/app/SnsAccount.apk
/system/app/SnsProvider.apk
/system/app/Stk.apk
/system/app/Street.apk
/system/app/Superuser.apk
/system/app/Swype.apk
/system/app/SystemUI.apk
Click to expand...
Click to collapse
(I wrote S*.apk to shorter this logfile).
Oh god, what did we see? The content of the Universal_GB_ROOT.zip file.
Step #3
What do we do now? Well, let's delete these files. Simply.
Good idea. But not so quick to do.
If you "rm" (*nix remove command) files we pointed at, the shell will answer:
rm failed for /system/app/Superuser.apk, Read-only file system
Click to expand...
Click to collapse
Why? Type:
Code:
$ cat /proc/mounts
You should have (it depends of apps you installed):
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/stl14 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/stl13 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/stl12 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=utf8 0 0
Click to expand...
Click to collapse
As you can see (or guess ^^), /system (where apps are installed) is mounted as ro (read-only).
As you can wonder, there is a "trick" to bypass that. Go being super-user:
Code:
$ su
Then:
Code:
$ mount -o rw,remount /dev/stl12 /system
This command will remount /dev/stl12 to /system in rw (read-write).
Step #4
NOW, you can remove files. But please, do ONLY remove files of the Universal_GB_ROOT.zip file like this way:
Code:
$ rm /system/xbin/busybox
$ rm /system/xbin/sqlite3
$ rm /system/xbin/sh
$ rm /system/xbin/su-v1
$ rm /system/xbin/su-v2
$ rm /system/xbin/su-v3
$ rm /system/xbin/su
$ rm /system/app/Superuser.apk
(obviously, *nix folks would prefer to go into the xbin folder and remove each file to write less).
Remember: 7 files in the xbin/ folder and only one in the app/ folder.
And this is it! Now quit the su role:
Code:
$ exit
And the Android shell:
Code:
$ exit
You are now back to the Windows shell.
Note : we did not umount anything because it is not needed. We did a remount. Thus, the usual mount of /system/stl12 to /system will happen again at startup. No worries.
Reboot your phone and go back to the application menu. The unremovable root application disappeared! *clap clap*
III - Going further
Since this unrooting method works with the "Universal Gingerbread Root (by StoneBoyTony)" (as a recall, you will find here: http://forum.xda-developers.com/showthread.php?t=1192122), this unrooting method may work on other devices (Mini, Ace, Pop, Fit) which have been rooted the same way.
Note we got access to the /system/app folder, where some unremovable applications of your carrier could be located. Take a look here. You will probably be able to remove them!
But you must root your phone
Since Sh is in the root package as well, don't you remove it too?
and after I unroot, I can safely OTA update correct? Or is unrooting necessary for safe OTA update.
Can this rooting method work for the Samsung Admire (SCH-R70)?????
I have tried flashing the Universal_BG_ROOT via recovery but I get stock at signature verification.
Can this other method work?
TriXin said:
Since Sh is in the root package as well, don't you remove it too?
Click to expand...
Click to collapse
True. I forgot to write it down. Thank you.
TriXin said:
and after I unroot, I can safely OTA update correct? Or is unrooting necessary for safe OTA update.
Click to expand...
Click to collapse
Rooting a phone (at least, for Android phones) means to allow user to be super-user => to use great powers on the phone.
I don't understand what do you mean by OTA update. But if the OTA update worked before rooting your phone, then unrooting your phone won't stop the OTA update to work.
marcos.lennis said:
Can this rooting method work for the Samsung Admire (SCH-R70)?????
Click to expand...
Click to collapse
If you used the Universal GB Root method, yes.
marcos.lennis said:
I have tried flashing the Universal_BG_ROOT via recovery but I get stock at signature verification.
Can this other method work?
Click to expand...
Click to collapse
stl5 (blaaaaah) or bml5, you have to root your phone. Check the first post, i say a word about rooting and unlocking. I think you have not made the difference yet.
If I use Root Explorer and remove those files then uninstall Root Explorer, would that work?
lypang said:
If I use Root Explorer and remove those files then uninstall Root Explorer, would that work?
Click to expand...
Click to collapse
I never used Root Explorer.
The goal here is to remove files contained in the zip file. If you can do that, so yes it should work.
I've downloaded the Andriod SDK but I have no idea how to do the adb shell. Where do I type this in? Sorry I'm new to this stuff.
I almost got it but it say's permission denied when I type "su" so I can't delete those files. Any reason why I'm getting this?
nevermind got it working. I had to allow the superuser on the phone.
Although the unroot was successful the phone still seems to be unlock. My sim card still works on it even though it should be locked to a different carrier.
Niitsu said:
I've downloaded the Andriod SDK but I have no idea how to do the adb shell. Where do I type this in? Sorry I'm new to this stuff.
Click to expand...
Click to collapse
Use CMD of windows! and search here for tutorials there are enaugh of it
unroot?
I've rooted my gio (gingerbread 2.3.5) with the update.zip method: http://forum.xda-developers.com/showthread.php?t=1111414. Can I unroot it with this method, or can I unroot it by just uninstalling superuser with titanium backup and then reboot? Maybe someone have another idea?
I have a request with a small donation as a reward. I'm not rich, but I can reward with some beer money.
I have managed to somehow delete my build.prop file while rooted and then managed to un-root my device. Naturally, I rebooted.
My request is for anyone with a bit of extra time to modify zergRush so that it does not look to a build.prop file to verify the android version.
If there are any other ideas on how to root a bricked Fire without a build.prop file, be my guest.
My hope is that once I am able to re-root my device, I will be able to mount /system/ as writeable and then be able to push in a build.prop file. However, obviously, until that happens I cannot put in a build.prop file.
If you have any questions I pretty much let it all out on the "How to unblock your kindle" thread.
If no one is able to do this I would understand. This is obviously beyond my technical expertise but I do appreciate any efforts or even suggestions. Even if there's no attempts made here, it is still shocking how much help is given on this forum.
EDIT: I was able to get my hands on a valid system.img and then flashed the system.img to my system partition. Doing so corrected my build.prop and my device became bootable. Thanks for all the help.
Did it update to 6.2 while in the midst of your needing around?
what does your device do?
Does it show under adb devices?
ajq said:
Did it update to 6.2 while in the midst of your needing around?
Click to expand...
Click to collapse
I updated to 6.2 on Tuesday. I have followed the directions on the "UNBRICK your kindle" thread. I have done that successfully. However, because my build.prop is missing, I can no longer re-root using zergRush. I believe that fastboot as directed in that thread restores the kindle to factory settings. I'm not quite sure if factory settings is 6.2 or if it goes all the way back to 6.0.
death2all110 said:
what does your device do?
Does it show under adb devices?
Click to expand...
Click to collapse
This is the post I created in the "How to unbrick your kindle" thread. It should answer most questions. I can use adb shell on the device but I cannot mount anything and SU responds "permission denied".
----from the other thread----
I am in a similar situation and am trying to work through it. I thought I rooted my device but when I restarted it, it didn't fully load. I've successfully done all of the steps listed in the OP but am still suck in a black screen (it's lit...but it's black) loop.
I believe I have deleted my build.pop file but have a backup listend as build.prop.bak. However, the device is trying to load and is failing. I need to rename my build.prop.bak as the primary build.prop. I have tried to access SU through ADB but am getting "permission denied" almost as if my device wasn't rooted.
I have tried to mount system as RW but I am also getting permission denied.
Any advice. Here is my /system/
:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Admin>cd \KindleFireRoot\files
C:\KindleFireRoot\files>adb shell
adb server is out of date. killing...
* daemon started successfully *
$ cd /system/
cd /system/
$ ls -l
ls -l
drwxr-xr-x root root 1970-01-01 00:00 lost+found
drwxr-xr-x root root 2011-12-01 19:03 app
drwxr-xr-x root shell 2011-12-01 19:03 bin
drwxr-xr-x root root 2011-11-30 01:16 etc
drwxr-xr-x root root 2011-11-30 01:16 fonts
drwxr-xr-x root root 2011-11-30 01:16 framework
drwxr-xr-x root root 2011-11-30 01:16 lib
drwxr-xr-x root root 2011-11-30 01:16 media
drwxr-xr-x root root 2011-11-30 01:16 tts
drwxr-xr-x root root 2011-11-30 01:16 usr
drwxr-xr-x root shell 2011-11-30 01:16 vendor
drwxr-xr-x root shell 2011-12-01 19:03 xbin
-rw-r--r-- root root 2143 2008-08-01 12:00 build.prop.bak
$
EDIT: I have tried to re-root through the method provided as well as superoneclick root, but both have failed because no android system is being recognized. This may have to do with the lack of a proper build.prop on my device.
EDIT2: I figure the above might not be enough information so I will now post what I have done so far to get it bricked, and what I have already tried.
1. I tried the rooting method on rootkindlefire.com and it seemed successful. I then was able to set /system/ as RW via root explorer. I copied a modified build.prop file that is available in the android development forums. However, unfortunately, I believe I may have edited the name of this file or done something wrong in handling it accidentally. Regardless, I pasted this file in the /system/ folder and renamed my original build.prop file to build.prop.bak. I then restarted my kindle fire. Now, it shows the kindle fire screen for a second and then goes black entirely. It is still on (the screen is lit), but the screen is black. It then remains like this until I do a hard reset and then it repeats this process.
2. I have tried to access SU but have been unable to do so. I have been unable to mount system as RW using the instruction a page back. In both situations I get the "permission denied" response from the command line.
3. Everytime I try to root using the method provided in the OP, I get a message saying that it can't find android 2.2 or 2.3
4. I am unable to root again using super click for the same reason.
5. I have otherwise been able to follow all of the steps in the OP successfully, but to no avail. My screen goes black after it shows the kindle fire screen for a couple seconds.
6. Any suggestions would be very very helpful. From my amateur amount of knowledge, it seems to me that I don't have a build.prop in my /system/ but am unable to rename or access my build.prop.bak so that I can set it as the regular bootable build.prop. This is because, even though I thought I had it rooted, I am unable to set the /system/ directory as writable.
7. ANY SUGGESTIONS OR HELP WOULD BE GREAT!
Just as a disclaimer: I acknowledge I'm a moron for not verifying everything when I pushed in a build.prop file into my /system/ folder and restarted. No need to call me names
For those who know a bit more than me...
Would pushing the 6.2 update (or any of the downloadable firmware) to the kindleupdates folder in the sdcard and then rebooting fix my problem? I remember reading that the updates re-writes the build.prop which would fix my situation.
Of course, do you need root permissions to be able to write to the sdcard? I only ask this because I can not get the sdcard to actually show up on my desktop. I would need to push it via terminal or adb shell.
Anyone know if this would work?
I am beginning to realize that I may actually still have root, but since I can't boot up the phone, I can't fill out the superuser access dialog that usually comes up when a program tries to access superuser. I had root before I caused the build.prop problems, but figured that I had somehow lost it when I tried to access SU from ADB. Anyone know of a way to bypass this access dialog?
I checked the root status with OneClickRoot after OTA reported my KF was still rooted (just to be sure) and then re-installed Superuser and pushed the necessary Android APKs back to /system/app and it was working again.
damianarnold said:
I checked the root status with OneClickRoot after OTA reported my KF was still rooted (just to be sure) and then re-installed Superuser and pushed the necessary Android APKs back to /system/app and it was working again.
Click to expand...
Click to collapse
How did you re-install Superuser if you're not able to fully boot up the KF? To be clear, when I try to root with superoneclick it says i'm rooted (and if i try and continue it fails...) but whenever I type in adb shell and then su I get "permission denied."
ejrubin said:
How did you re-install Superuser if you're not able to fully boot up the KF? To be clear, when I try to root with superoneclick it says i'm rooted (and if i try and continue it fails...) but whenever I type in adb shell and then su I get "permission denied."
Click to expand...
Click to collapse
My Fire was fully booted up. Did you remove and reinstall Superuser?
damianarnold said:
My Fire was fully booted up. Did you remove and reinstall Superuser?
Click to expand...
Click to collapse
Don't think our KF were in the same state. I don't have a build.prop to boot my KF into so I can't manage superuser at all (I do, however, have a totally useless build.prop.bak that is sitting there in the directory. ) I have the superuser.apk in there so it seems as though I'm rooted but I still can't get into SU via adb.
Can't get Write access to /System or /SDCard
ejrubin said:
Don't think our KF were in the same state. I don't have a build.prop to boot my KF into so I can't manage superuser at all (I do, however, have a totally useless build.prop.bak that is sitting there in the directory. ) I have the superuser.apk in there so it seems as though I'm rooted but I still can't get into SU via adb.
Click to expand...
Click to collapse
Still having the exact same problem! Was able to get the build.prob.bak pulled from /system but can't rename it and push it back to hopefully get this working again.
I am starting to think I may have to send this KF back soon if I don't get it working again.
Any help anyone can provide would be great.
I'm thinking since we are able to get into fastboot, do any developers know if it is possible to push in a new system.img via fastboot? This would solve our build.prop problems no? Any developers know if this is possible?
I would like to compile zergRush myself, but I don't know how to compile Android binary.
It seems require linux to do so.
Can you adb push to the sdcard?
Sent from my DROID Pro using XDA App
JackpotClavin said:
Can you adb push to the sdcard?
Sent from my DROID Pro using XDA App
Click to expand...
Click to collapse
No , I think the sdcard is not yet mount. Tried cd sdcard and it's not possible.
Is it possible to mount it without root? Cause when we try to mount system folder it's permission denied.
And I'm afraid the system won't run the official update even the patch is inside the sdcard folder.
I think ejrubin's idea on how to fix our bricked kindle fire is completely right , we just need either one of the following :
1. A zergRush binary won't check the build.prop to let us run root and mount the system folder
2. Since we can get into fastboot, I think we need a correct update.zip or system.img to fix it. Any idea to build it from kindle's official update?
Well try "mount sdcard" in the shell. If you can push the update, you can idme bootmode into 0x5001 and it'll take the update in recovery mode
If that doesn't work I'll give a custom zerg a shot
Edit: I got it. If you wanna flash my clockwork build in fastboot and set the fastboot to boot into recovery, you can access your /system through recovery, I do it all the time
It'll be a fastboot flash recovery <the name of the recovery.img I'll post later when I get home>
From there you will have to:
Adb shell
Mount system
Mv /system/build.bak /system/build.prop
Sent from my DROID Pro using XDA App
JackpotClavin said:
Well try "mount sdcard" in the shell. If you can push the update, you can idme bootmode into 0x5001 and it'll take the update in recovery mode
If that doesn't work I'll give a custom zerg a shot
Edit: I got it. If you wanna flash my clockwork build in fastboot and set the fastboot to boot into recovery, you can access your /system through recovery, I do it all the time
It'll be a fastboot flash recovery <the name of the recovery.img I'll post later when I get home>
From there you will have to:
Adb shell
Mount system
Mv /system/build.bak /system/build.prop
Sent from my DROID Pro using XDA App
Click to expand...
Click to collapse
If i just type "mount sdcard" it cannot recognize the command.
if try to mount it with -t and mount it to other folder, it just say permission denied.
Of course I wanna flash your clockwork build!!
Would you mind to guide us with all the step when you're ready? Because I'm quite new to root android machine.
Really thanks for your help!!!!!!!!!!!!!!!!
Yeah **** sorry guys can this wait till tomorrow? Sorry I said tonight, I got side tracked tonight
Sent from my DROID Pro using XDA App
Q&A for [ROOT] Root your LG-G3 easily with PurpleDrake-Lite! [OSX/Linux/Windows!]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
I can't run Purple Drake.
I have unzipped the Purpledrake lite for the LG G3, but I noticed that when i doubleclick on the purple_windows.bat file, the command prompt comes on twice then disappears. I have captured screen to see what the message on the command prompt says.
"./assests/purpledrake_main.sh:line 2: $'\r': command not found.
There are a few lines that are similar to this.
Working great on D855 V10i-SEA-XX.
Thanks!
I have successfully rooted an LG L Fino with PurpleDrake. After trying numerous methods this one was success with no probles whatsoever.
Thanks
Working great on D855 V10L-EUR-XX. :good:
Xrauder said:
I have unzipped the Purpledrake lite for the LG G3, but I noticed that when i doubleclick on the purple_windows.bat file, the command prompt comes on twice then disappears. I have captured screen to see what the message on the command prompt says.
"./assests/purpledrake_main.sh:line 2: $'\r': command not found.
There are a few lines that are similar to this.
Click to expand...
Click to collapse
There's another file called purple_windows which is bigger. That's the one you need.
Envoyé de mon LG-D855 en utilisant Tapatalk
Just wanted to add that the Lite version works on D855 10H too - which is a verison not listed in the spreadsheet
Can I root my G2 mini with PurpleDrake?
LG G3 Purple Drake
So Ive just tried rooting my G3 d855, however I boot up Purple Drake and all I get is what is shown in the attached image. Any Ideas?
ElectroPlug said:
Hi, I tried to root my G3s (D-722) and recording to other users it should work with PurpleDrake but as soon as the phone reboots into that... "Download-Mode" or whatever that is, the program wont recognize the phone anymore. It just says "Waiting for device..." for quite an eternity. What am I doing wrong?
Click to expand...
Click to collapse
had the same issue yesterday while trying to root my brand new lg g3, so I just made it the manual way and it worked great
I'm talking about this :
But, what if I don't want to run your script to root?
Well then, I'd be a little hurt, but you can still do everything the script does manually.
Download the package, and extract it. Open a terminal in the main folder of the archive and run these commands:
Code:
adb reboot --bnr_recovery
adb push ./assets/start_restore /temp/start_restore
adb push ./assets/permaroot.bin /temp/start_restore
adb reboot
That will perma-root you, however there's no protection from doing something stupid or the phone being incompatible. Please be careful!
Click to expand...
Click to collapse
An error occurred while permaroot on LG G3 Beat
I'm using G3 Beat (F470K, Korea Telecom).
PurpleDrake works well before update firmware(F470K10n). After it, Permaroot not works.
While Permaroot,
Code:
ERROR: Something went wrong. Permaroot doesn't appear to have worked, rebooting phone.
Debug information - 'ls -l /system/xbin/su':
/system/xbin/su: No such file or directory
Here is whole logs:
Code:
Welcome to PurpleDrake!
Please ensure your phone is connected, powered on, and USB debugging is properly enabled.
Your phone should be showing your homescreen with no other apps open. This is to ensure a clean state.
When you're ready, press [enter]...
Press [enter] to continue...
Waiting for device... Found device!
Your phone is a [ LG-F470K ] on [ KT ] running SW version [ V10n ] ...
Alright. We're ready to go. We're going to temproot your phone first. Press enter when you're ready!
Press [enter] to continue...
Rebooting phone...
Waiting for device... ... Found device!
Found device, checking if vulnerable...
Yep, performing temproot...
Waiting for system to settle...
Temproot worked, all done here. Moving on...
Alright, now that you're temprooted, you can press CTRL-C here and get
a temproot prompt through 'adb shell /temp/fakesu' if you're so inclined...
However, if you'd like to permaroot, let's continue.
Press [enter] to continue...
Waiting for device... Found device!
Applying permaroot...
Waiting for system to settle...
Checking if it worked...
ERROR: Something went wrong. Permaroot doesn't appear to have worked, rebooting phone.
Debug information - 'ls -l /system/xbin/su':
/system/xbin/su: No such file or directory
------------------------
Debug information - 'ls -l /temp/':
-rw-r--r-- root root 2171 1970-01-01 01:39 br_daemon.log
-rw-r--r-- root root 36 1970-01-01 01:05 brd_ready
-rw-r--r-- root root 2 1970-01-01 01:39 error
-rwsr-sr-x root root 157424 2014-07-12 03:54 fakesu
drwx------ root root 1970-01-01 01:39 hidden
-rw-r--r-- root root 28 1970-01-01 01:05 start_restore_complete
------------------------
Press [enter] to continue...
Is there something to need to fix this error?
Jongmin Kim said:
I'm using G3 Beat (F470K, Korea Telecom).
PurpleDrake works well before update firmware(F470K10n). After it, Permaroot not works.
While Permaroot,
Code:
ERROR: Something went wrong. Permaroot doesn't appear to have worked, rebooting phone.
Debug information - 'ls -l /system/xbin/su':
/system/xbin/su: No such file or directory
Here is whole logs:
Code:
Welcome to PurpleDrake!
Please ensure your phone is connected, powered on, and USB debugging is properly enabled.
Your phone should be showing your homescreen with no other apps open. This is to ensure a clean state.
When you're ready, press [enter]...
Press [enter] to continue...
Waiting for device... Found device!
Your phone is a [ LG-F470K ] on [ KT ] running SW version [ V10n ] ...
Alright. We're ready to go. We're going to temproot your phone first. Press enter when you're ready!
Press [enter] to continue...
Rebooting phone...
Waiting for device... ... Found device!
Found device, checking if vulnerable...
Yep, performing temproot...
Waiting for system to settle...
Temproot worked, all done here. Moving on...
Alright, now that you're temprooted, you can press CTRL-C here and get
a temproot prompt through 'adb shell /temp/fakesu' if you're so inclined...
However, if you'd like to permaroot, let's continue.
Press [enter] to continue...
Waiting for device... Found device!
Applying permaroot...
Waiting for system to settle...
Checking if it worked...
ERROR: Something went wrong. Permaroot doesn't appear to have worked, rebooting phone.
Debug information - 'ls -l /system/xbin/su':
/system/xbin/su: No such file or directory
------------------------
Debug information - 'ls -l /temp/':
-rw-r--r-- root root 2171 1970-01-01 01:39 br_daemon.log
-rw-r--r-- root root 36 1970-01-01 01:05 brd_ready
-rw-r--r-- root root 2 1970-01-01 01:39 error
-rwsr-sr-x root root 157424 2014-07-12 03:54 fakesu
drwx------ root root 1970-01-01 01:39 hidden
-rw-r--r-- root root 28 1970-01-01 01:05 start_restore_complete
------------------------
Press [enter] to continue...
Is there something to need to fix this error?
Click to expand...
Click to collapse
I think that firmware has a lock...
Icaros7 said:
I think that firmware has a lock...
Click to expand...
Click to collapse
Yep, same with you. How about the error logs?
Jongmin Kim said:
Yep, same with you. How about the error logs?
Click to expand...
Click to collapse
The Script cant copy the su.
Im sorry its my think...
If I had saw the script, I would have answer accurately...
Icaros7 said:
The Script cant copy the su.
Im sorry its my think...
If I had saw the script, I would have answer accurately...
Click to expand...
Click to collapse
...Thanks to your reply.
In Temproot, /temp/fakesu seems do not have root access.
Code:
[email protected]:/ $ /temp/root
# id
uid=2000(shell) gid=2000(shell) groups=1003(graphics),1004(input),1007(log),1009(mount),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats) context=u:r:shell:s0
# mount -o remount,rw /system
mount: Operation not permitted
# exit
[email protected]:/ $
Hi
I just bought my LG G3 and is very happy with it so far at least, except for one issue.
I normally do not feel like i need to root my android devices, but seeing that there were some changes in 4.4 that has kept ONE(!) of my apps from working i have so far not updated them from 4.3. Seeing that the G3(and all other phones nowadays) comes with 4.4 as a standard option i have to do something about this.
So, my question is - will purpledrake be good for me since my interest only lies in making that specific app usable? I have(at least at this moment) no interest in installing different roms right and left and tweak it to it's max.
Having a temproot would also be a good solution - is this something the Purpledrake root can do?
Device not detected on OSX
Hey guys,
I've installed R03 on my Mac. Enabled USB debugging on the phone. (Phone LG G3 D855 V10l-AUS-XX).
I open up PurpleDrake which opens up and says Press Enter to Continue. With device plugged in and debugging icon in status bar, the phone is not being detected. just getting . . . . . . . . . . . .
Any help much appreciated.
Cheers
Not working for LG Optimus L90 D415. Below is the output. Also, the script doesn't detect the phone the first run of the script but after exiting it once it will detect it.
Your phone is a [ LG-D415 ] on [ TMO ] running SW version [ V10c ] ...
Alright. We're ready to go. We're going to temproot your phone first. Press enter when you're ready!
Press [enter] to continue...
Rebooting phone...
Waiting for device... ... Found device!
Found device, checking if vulnerable...
ERROR: Your phone is not running a compatible software version. No vulnerable mode detected, rebooting phone.
We tried to temproot you, and it didn't work. This phone isn't vulnerable, it would appear.
Please post on XDA with your phone model, carrier, and SW version in the PurpleDrake thread and someone will take a look .
Click to expand...
Click to collapse
Jongmin Kim said:
...Thanks to your reply.
In Temproot, /temp/fakesu seems do not have root access.
Code:
[email protected]:/ $ /temp/root
# id
uid=2000(shell) gid=2000(shell) groups=1003(graphics),1004(input),1007(log),1009(mount),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats) context=u:r:shell:s0
# mount -o remount,rw /system
mount: Operation not permitted
# exit
[email protected]:/ $
Click to expand...
Click to collapse
It seems it is in the 3001 net_bt_admin or one after it I'm a noob could u please share if u find it works thank u
WHATSAMATTA U ALUMNI
deathsquad737 said:
It seems it is in the 3001 net_bt_admin or one after it I'm a noob could u please share if u find it works thank u
WHATSAMATTA U ALUMNI
Click to expand...
Click to collapse
Thanks to your reply and I will. [emoji1]
ps. They are a groups which is provided for their services; net_bt_admin is used in bluetooth.
Redmi Note 5 global version (model M1803E7SH).
Running MIUI Global 9.5 Stable (9.5.6.0).
Unlocked bootloader.
NOT rooted.
I booted TWRP via Fastboot (without flashing it to recovery) and attempted to overwrite /system/etc/hosts with my own file, which was successful.
Result of running ls -l /system/etc/hosts on TWRP terminal:
Code:
-rw-r----- 1 root root 1587161 2018-06-03 20:55 /system/etc/hosts
However after booting back into system, the previous command now shows me the following:
Code:
-rw-r----- 1 root root 56 2008-12-31 11:00 /system/etc/hosts
If I were to boot into TWRP again, I can clearly see that the file I copied is still there at /system/etc/hosts, so it's like MIUI is grabbing the hosts file from somewhere else instead.
Any ideas that do not involve rooting permanently? I do not wish to root my phone, just block ads via /etc/hosts is all.
You are right, the hosts file in /system/etc is written new on every reboot by MIUI. I´m using AdFree on my Android phones for ages that uses the hosts file to block ads, so I wanted to use this on my Note 5 too. But it didn´t work because of the problem you encountered.
I had to click the option "create and use /data/hosts symlink" in AdFree to get Ad blocking back, this seems to create a shortcut to the hosts file now stored on /data to avoice being overwritten.
Kusie said:
I had to click the option "create and use /data/hosts symlink" in AdFree to get Ad blocking back
Click to expand...
Click to collapse
I don't think I can depend on this solution if I'm not rooted. I'm looking for a rootless solution. For now I'm using DNS66 however that is not a complete solution for me because some of my work is done via VPN.
sagematt said:
Redmi Note 5 global version (model M1803E7SH).
Running MIUI Global 9.5 Stable (9.5.6.0).
Unlocked bootloader.
NOT rooted.
I booted TWRP via Fastboot (without flashing it to recovery) and attempted to overwrite /system/etc/hosts with my own file, which was successful.
Result of running ls -l /system/etc/hosts on TWRP terminal:
Code:
-rw-r----- 1 root root 1587161 2018-06-03 20:55 /system/etc/hosts
However after booting back into system, the previous command now shows me the following:
Code:
-rw-r----- 1 root root 56 2008-12-31 11:00 /system/etc/hosts
If I were to boot into TWRP again, I can clearly see that the file I copied is still there at /system/etc/hosts, so it's like MIUI is grabbing the hosts file from somewhere else instead.
Any ideas that do not involve rooting permanently? I do not wish to root my phone, just block ads via /etc/hosts is all.
Click to expand...
Click to collapse
Just wondering, have you ever solved this?
ne0t said:
Just wondering, have you ever solved this?
Click to expand...
Click to collapse
It cannot be solved, you need root to replace the hosts file and then you can later unroot if you wish and the hosts file will remain modified.