Q&A for [GUIDE] New Root Method for LG Devices
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.
Before posting, please use the forum search and read through the discussion thread for [GUIDE] New Root Method for LG Devices. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Help
Unjustified Dev said:
Unlocking boot loader if possible
Open a command prompt in LG_Root
Copy fastboot.exe into LG_Root folder found in the attached zip
1.) Start an ADB shell
Code:
adb.exe shell
2.) In ADB shell ask for root permission (Grant shell access via the SuperSU pop-up)
Code:
su
3.) Dump the LAF partition to sdcard (We want to be able to restore Download mode)
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/sdcard/laf.img
4.) Remove LAF partition
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
5.) To exit ADB shell, type "exit" twice in shell
6.) Store the image on our PC
Code:
adb.exe pull /sdcard/laf.img
7.) Go into download mode (It will fail due to the empty LAF partition and will fall back to fastboot)
Detect if the device is connected (Wait for any drivers to install)
Code:
fastboot.exe devices
To unlock the boot loader
Code:
fastboot.exe oem unlock
You may choose to keep fastboot or you can put LAF partition back on for download mode
Code:
fastboot.exe flash laf laf.img
Click to expand...
Click to collapse
When I try to open Send_Command it doesnt open. I have COM 3
Cawos said:
When I try to open Send_Command it doesnt open. I have COM 3
Click to expand...
Click to collapse
More details please. Are you in download mode? Do you have drivers installed? What's the output of the command
Send_Command.exe \\.\COM3
Unjustified Dev said:
More details please. Are you in download mode? Do you have drivers installed? What's the output of the command
Send_Command.exe \\.\COM3
Click to expand...
Click to collapse
Alright so first of all I dont really know all this stuff about android and what not. Yes I am in download mode, and yes I did everything. When I open it, it just closes right away. I also have the other cmd window still open btw Forget what I said, when I put in the command it says
SPECIAL COMMAND : ENTER,LEAVE
Cawos said:
Alright so first of all I dont really know all this stuff about android and what not. Yes I am in download mode, and yes I did everything. When I open it, it just closes right away. I also have the other cmd window still open btw Forget what I said, when I put in the command it says
SPECIAL COMMAND : ENTER,LEAVE
Click to expand...
Click to collapse
That's what it's suppose to say and you should see a # symbol
when you see the # symbol
copy and paste
Code:
sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
it will look like #sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
press enter and your good to go.
Unjustified Dev said:
That's what it's suppose to say and you should see a # symbol
when you see the # symbol
copy and paste
Code:
sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
it will look like #sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
press enter and your good to go.
Click to expand...
Click to collapse
Thanks! But dont I have to download super user or something like that?
Cawos said:
Thanks! But dont I have to download super user or something like that?
Click to expand...
Click to collapse
It's in the folder you've been working in the whole time. The script you just ran took care of everything. When you boot your device you will have supersu installed.
I get to the rooting script part and once I hit enter it tells me that only SuperSU was installed. Can anybody give me some advice to what it is I'm doing wrong?
UnifiedDev37 said:
I get to the rooting script part and once I hit enter it tells me that only SuperSU was installed. Can anybody give me some advice to what it is I'm doing wrong?
Click to expand...
Click to collapse
Could you post a screen shot I need to know exactly what you mean.
Unjustified Dev said:
Could you post a screen shot I need to know exactly what you mean.
Click to expand...
Click to collapse
I must've forgotten to add the image, my bad
UnifiedDev37 said:
I must've forgotten to add the image, my bad
Click to expand...
Click to collapse
That's the correct output , but it looks like you need to push files again. It should work the second time around.
Can this work for the att model?
Sent from my LG-D850 using XDA Free mobile app
southern87 said:
Can this work for the att model?
Sent from my LG-D850 using XDA Free mobile app
Click to expand...
Click to collapse
Let me know, there's no risk in trying it. If it worked for Verizon I would count on it working for AT&T
Unjustified Dev said:
That's the correct output , but it looks like you need to push files again. It should work the second time around.
Click to expand...
Click to collapse
Just tried it again, same output but when I open root checker it tells me that my device doesn't have proper root privileges
Unjustified Dev said:
Let me know, there's no risk in trying it. If it worked for Verizon I would count on it working for AT&T
Click to expand...
Click to collapse
Do i need to have kk or lp installed?
Sent from my LG-D850 using XDA Free mobile app
southern87 said:
Do i need to have kk or lp installed?
Sent from my LG-D850 using XDA Free mobile app
Click to expand...
Click to collapse
Works on both
UnifiedDev37 said:
Just tried it again, same output but when I open root checker it tells me that my device doesn't have proper root privileges
Click to expand...
Click to collapse
Maybe your not copying the full command correctly
when you start Send_Command.exe
copy this you should have 3 files
ls -l /data/local/tmp
if they exist copy and paste
sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
Unjustified Dev said:
Maybe your not copying the full command correctly
when you start Send_Command.exe
copy this you should have 3 files
ls -l /data/local/tmp
if they exist copy and paste
sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
Click to expand...
Click to collapse
I ran ls -l /data/local/tmp and the three files were there but when I copied and pasted sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox it gives same output and still no root
UnifiedDev37 said:
I ran ls -l /data/local/tmp and the three files were there but when I copied and pasted sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox it gives same output and still no root
Click to expand...
Click to collapse
Have you tried exiting download mode and starting over?
Unjustified Dev said:
Have you tried exiting download mode and starting over?
Click to expand...
Click to collapse
I've tried that multiple times
Related
Here comes the latest rooting method that works with 2.0.2.A.0.24 firmware.
Credits to Scotty2 for his psneuter exploit!
1. Download and unpack rootme.tar.bz2
2. Execute ./rootme (linux) or rootme.bat (windows)
3. Done.
---
You may also want to try SuperOneClickv1.5.5-ShortFuse.zip (modified by batman_112 to use the latest exploit).
Cheers,
z
Stop for me at Point 4)
I got back
./ratc: Permission denied
Click to expand...
Click to collapse
after
./ratc
i get ... permission denided
Wow, actually it seems that copying files with adb push via script messes thing up I corrected the instructions, so now it will work for you, but need to copy the files manually.
zdzihu said:
Wow, actually it seems that copying files with adb push via script messes thing up I corrected the instructions, so now it will work for you, but need to copy the files manually.
Click to expand...
Click to collapse
Your link is broken
Try now, I got rid of installation scripts
EDIT: Now it works flawlessly. I still have no clue why copying files with .bat file messes everything up, but manual copying does the job.
why the superone reach the root sometimes so slow?
your method uses the same exploit, and works at first try
check the files plz: Invalid or Deleted File
can't download the ratc-pack --> Invalid or Deleted File
please reup - THX
EDIT: Link is OK now --> THX
Link is OK. Downloading at the moment.
Tried it manually (as described)...
But same problem... :-(
UserX10 said:
Tried it manually (as described)...
But same problem... :-(
Click to expand...
Click to collapse
I just reflashed my phone and it worked for me at 1st attempt.
Could you please got rid of the old files and retry from the beggining?
Cheers!
meta96 said:
after
./ratc
i get ... permission denided
Click to expand...
Click to collapse
Same thing for me
:-( Same Problem
I flashed my X10 with nordic FW and tried it again Step by Step... but "permission denied"... even if i remove and make the tmp directory as described...
Ok, last thing to try... After you copy the files, go with:
Code:
adb shell
chmod 777 /data/local/tmp/*
I added some screenshots to show how the process works for me.
is this a full root? i mean, is root+shell root?
zdzihu said:
Hi guys, I've noticed some people still can't get their phones rooted with SuperOneClick method. So do I, never managed to get it working Here is a simple method of rooting, using the same exploit (rageagainstthecage - credits to author). This is quick and 100% guaranteed to work but I'd rather recommend it to advanced users.
1. Install Android Terminal Emulator from the market http://bit.ly/9B46Nl
2. Download and unpack http://www.mediafire.com/?s0428zxc7n50i28
3. Plug in the phone (usb debugging mode), copy the following files with adb and change permissions:
Code:
adb push ratc /data/local/tmp/ratc
adb push busybox /data/local/tmp/busybox
adb push su /data/local/tmp/su
adb push rootme /data/local/tmp/rootme
adb push superuser.apk /data/local/tmp/superuser.apk
adb shell
chmod /data/local/tmp/*
4. Start Terminal Emulator on your phone and issue those commands:
Code:
cd /data/local/tmp
./ratc
5. Exit out of Terminal Emulator using BACK button.
6. Start any other application and exit out of it using BACK button.
7. Start Terminal Emulator again - note that you're running it as root (#)
8. Issue those commands:
Code:
cd /data/local/tmp
./rootme
Your phone will reboot - and it's done. I suggest installing Busybox from the Market. Hope it helps.
Cheers!
EDIT: Fixed.
Click to expand...
Click to collapse
Finally I was able to root my phone
just one correction, you got to use chmod 777 /data/local/tmp/*
it was not allowing to root otherwise
i kept breaking my head using the "simple" SuperOneCLick but could not show my rage against the machine
thank you for explaining this process for Root.
zdzihu said:
Ok, last thing to try... After you copy the files, go with:
Code:
adb shell
cd /data/local/tmp
chmod 777 *
I added some screenshots to show how the process works for me.
Click to expand...
Click to collapse
chmod 777 *
did it. thanx. btw like your oldstyle-skills
Just saw this thread and wanted to root my phone also...I downloaded the files provided in the first post and extracted onto my PC. When I tried running the adb application, I only get a command window only for a split second and then it disappears. Am I doing something wrong?
Everything works fine until the final step where I write ./rootme in the emulator.
Before the phone reboots, it says something right after, something about superuser.apk.
Once the phone is back on the emulator goes back to $. As well as not being able to download Busybox.
Appreciate your efforts
EDIT: No worries, I managed to get root using SuperOneClick (finally!). It was rather sketchy, would've preferred your way tbh.
I installed the Galaxy S3 Retail Mode found in Google Play but had problems setting it up so I uninstalled it.
Now, I have a folder in /sdcard/ named RetailMode that contains photos used by the RetailMode application. But no matter what I do, I can't delete it. Can't delete any of the photos either.
I tried changing owners and changing permissions but failed. I even tried via adb shell.
Any ideas of how I can delete it?
Thanks in advance!
Beach_Head said:
I installed the Galaxy S3 Retail Mode found in Google Play but had problems setting it up so I uninstalled it.
Now, I have a folder in /sdcard/ named RetailMode that contains photos used by the RetailMode application. But no matter what I do, I can't delete it. Can't delete any of the photos either.
I tried changing owners and changing permissions but failed. I even tried via adb shell.
Any ideas of how I can delete it?
Thanks in advance!
Click to expand...
Click to collapse
Could try running a KIES update or one of the Jellybean OTA's that will wipe the internal sd card
Are you trying to do so as root? If you open a terminal (download Android Terminal from the market) and run:
Code:
su
rm -rf /sdcard/RetailMode
(upper/lower case is important!) what is the output?
Yes. Tried via ConnectBot on the phone and adb. Issued the exact same command you posted.
The reply was: rm failed for -rf, No such file or directory
I wonder what the problem is...
Steve_max said:
Are you trying to do so as root? If you open a terminal (download Android Terminal from the market) and run:
Code:
su
rm -rf /sdcard/RetailMode
(upper/lower case is important!) what is the output?
Click to expand...
Click to collapse
Beach_Head said:
Yes. Tried via ConnectBot on the phone and adb. Issued the exact same command you posted.
The reply was: rm failed for -rf, No such file or directory
I wonder what the problem is...
Click to expand...
Click to collapse
Reboot?
Tried that first. No go.
Since Retail Mode is installed and activated as a Device Administrator, I think it modified some settings. I just don't know what those settings are.
I don't want to re-flash so hopefully someone can help me with this...
kulisap said:
Reboot?
Click to expand...
Click to collapse
first you have to deactivate RetailMode as an administrator. than check if is also disabled in Accessibility also, just in case. than try to delete it. It might work.
Did that already too.
This is so frustrating...
Chaitanyapatel8880 said:
first you have to deactivate RetailMode as an administrator. than check if is also disabled in Accessibility also, just in case. than try to delete it. It might work.
Click to expand...
Click to collapse
only one choice left than... Full wipe...
There has to be another way...
Chaitanyapatel8880 said:
only one choice left than... Full wipe...
Click to expand...
Click to collapse
Had this one before but the app was smart app protector. Deleted it but it left a folder and cant delete it even in the pc. But iwas able to delete it using root explorer.
Sent from my GT-I9300 using Tapatalk 2
Beach_Head said:
Yes. Tried via ConnectBot on the phone and adb. Issued the exact same command you posted.
The reply was: rm failed for -rf, No such file or directory
I wonder what the problem is...
Click to expand...
Click to collapse
Install a BusyBox from the market (if you already have it, reinstall). if "rm" is trying to remove "-rf", it's NOT a standard "rm", which can explain your problems. Then try again.
After having followed the above: Should you get a "permission denied" as root (execute 'whoami' on the console to make sure you're root!)
then the file(s) is most probably flagged as immutable.
Executing the following will then resolve the issue: chattr -iR /sdcard/RetailMode
This is what I get when I issue that command: reading flags on /sdcard/RetailMedia: innapropriate ioctl for device
d4fseeker said:
After having followed the above: Should you get a "permission denied" as root (execute 'whoami' on the console to make sure you're root!)
then the file(s) is most probably flagged as immutable.
Executing the following will then resolve the issue: chattr -iR /sdcard/RetailMode
Click to expand...
Click to collapse
Here is a complete guide for anyone interested in rooting the HTC Droid DNA. The insecure boot image, TWRP recovery, CWM recovery and SuperSU files used in this guide are not my own developments, and their developers have been credited in the end of this post.
I am only writing this as a newbie-friendly guide for everyone, and am providing my own SuperSU, su and busybox installer zip file that includes everything you need for full root.
Unlock the bootloader of your device by visiting the HTC bootloader unlock page. Warning: This will wipe your data.
UPDATE: Thanks to Verizon, the official bootloader unlocking method mentioned above no longer works. Please refer to this method for unlocking the bootloader.
Download ClockworkMod or TWRP recovery for the device and rename it to recovery.img (or keep the existing name and change recovery.img in the command below to that name).
Download the SuperSU and busybox package and put it on your SD card.
Put your phone into bootloader mode and connect it to your PC via USB.
On your computer, make sure you are in the folder where you downloaded the recovery file and use this command to flash the recovery:
Code:
fastboot flash recovery recovery.img
Finally, reboot your device into recovery, flash the SuperSU and busybox package and reboot your device.
You should now have root access.
Credits:
jcase for unlocking the bootloader after Verizon decided to lock it.
dsb9938 for sharing the CWM port and correcting me regarding my previously posted and now removed second method involving his insecure boot image
Dees_Troy for TWRP recovery.
utkanos for CWM port.
Chainfire for developing SuperSU
I have tried to credit everyone involved but if I have missed out on anyone, please do let me know.
thanks for the guide!
just one question though. when you say "Download the SuperSU and busybox package and put it on your SD card.", what do you mean exactly by SD card? doesn't the DNA not have a SD card? sorry if this is a dumb question. i've never rooted a phone before :/
hotmonkas said:
thanks for the guide!
just one question though. when you say "Download the SuperSU and busybox package and put it on your SD card.", what do you mean exactly by SD card? doesn't the DNA not have a SD card? sorry if this is a dumb question. i've never rooted a phone before :/
Click to expand...
Click to collapse
Internal storage would be another name for the SD card.
touretts69 said:
Internal storage would be another name for the SD card.
Click to expand...
Click to collapse
ah okay, thank you
which device do u use on the htc page?
nyjw said:
which device do u use on the htc page?
Click to expand...
Click to collapse
"Other devices", or similar.
Sent from my ADR6425LVW using xda premium
Awesomeness.
The fact that this phone is rooted a week before its even out... simply awesome. I love XDA!
So excited for this phone.
HQRaja said:
Code:
adb shell mount -o remount,rw /system
[LIST=1]
[*] adb push su /system/bin/
adb push Superuser.apk /system/app/
adb push busybox /system/xbin/
adb shell
chmod 06755 /system/bin/su
chmod 0644 /system/app/Superuser.apk
chmod 04755 /system/xbin/busybox
cd /system/xbin
busybox --install /system/xbin/
exit
exit
[*]Reboot your device.
[/LIST]
Click to expand...
Click to collapse
This will not work. You cannot write to /system except in recovery.
This is why I did not publish my initial root method. Using a package and flashing in recovery is the only way to get files on /system without some really gnarly stuff.
D
.
dsb9938 said:
This will not work. You cannot write to /system except in recovery.
This is why I did not publish my initial root method. Using a package and flashing in recovery is the only way to get files on /system without some really gnarly stuff.
D
.
Click to expand...
Click to collapse
Thanks for your response. =)
Based on my understanding (and my experience with Nexus devices), once you boot using an insecure boot image, you have full root access in ADB since it is running adbd as root on the device. You can then successfully write to the /system partition and the changes persist after reboot. While I can confirm that the above will work on any Nexus device as well as any similar device with an unlocked bootloader and fastboot access, I am not 100% sure if that's how it works on HTC devices that have the S-ON flag. Are you referring to S-ON devices in particular here?
HQRaja said:
Thanks for your response. =)
Based on my understanding (and my experience with Nexus devices), once you boot using an insecure boot image, you have full root access in ADB since it is running adbd as root on the device. You can then successfully write to the /system partition and the changes persist after reboot. While I can confirm that the above will work on any Nexus device as well as any similar device with an unlocked bootloader and fastboot access, I am not 100% sure if that's how it works on HTC devices that have the S-ON flag. Are you referring to S-ON devices in particular here?
Click to expand...
Click to collapse
Normally it does work that way. And I was very disappointed that it did not on this phone, as I made the kernel just for that reason.
I think there was an error in the coding where it tells unlock which partitions to remove write protection from. That, or they just wanna make our lives hard for some reason.
Either way, you cannot write to /system while the phone is booted normally without S-Off. Even as root.
D
.
dsb9938 said:
Normally it does work that way. And I was very disappointed that it did not on this phone, as I made the kernel just for that reason.
I think there was an error in the coding where it tells unlock which partitions to remove write protection from. That, or they just wanna make our lives hard for some reason.
Either way, you cannot write to /system while the phone is booted normally without S-Off. Even as root.
D
.
Click to expand...
Click to collapse
Ah I see. Thanks for pointing that out. I'll remove the second method from my guide, since including that would be pointless if that's the case as you can now confirm.
So does this method work? Or not???Im confused with the last few posts. Thanks
suzook said:
So does this method work? Or not???Im confused with the last few posts. Thanks
Click to expand...
Click to collapse
Edited post is fine. He removed the part I was talking about.
D
.
What I want to know most if anyone knows..will the DNA through verizon be unlockable....I'm actually using the RAZR Maxx hd through verizon and Motorola has restricted unlocking the bootloader because of verizon
Sent from my DROID RAZR HD using xda app-developers app
Irish65 said:
What I want to know most if anyone knows..will the DNA through verizon be unlockable....I'm actually using the RAZR Maxx hd through verizon and Motorola has restricted unlocking the bootloader because of verizon
Sent from my DROID RAZR HD using xda app-developers app
Click to expand...
Click to collapse
You can't do any of this stuff without unlocking.
As of right now, it is working.
D
.
How do you do the command in the folder were u downloaded to like the instructions say?
idle0095 said:
How do you do the command in the folder were u downloaded to like the instructions say?
Click to expand...
Click to collapse
Please be more specific.
D
.
idle0095 said:
How do you do the command in the folder were u downloaded to like the instructions say?
Click to expand...
Click to collapse
In command prompt, use the "cd" command. The easiest way to do this is to make a folder at the root of your hard drive (C:\) and place all files you need to flash in here e.g. "C:\android\" Then in command prompt, type in "cd .." and press enter until it displays "C:\". Then type (if you use the same name as the example) "cd android" and it will enter the folder "C:\android\" where you placed the files. Now you can continue with the rest of the guide.
CastleBravo said:
In command prompt, use the "cd" command. The easiest way to do this is to make a folder at the root of your hard drive (C:\) and place all files you need to flash in here e.g. "C:\android\" Then in command prompt, type in "cd .." and press enter until it displays "C:\". Then type (if you use the same name as the example) "cd android" and it will enter the folder "C:\android\" where you placed the files. Now you can continue with the rest of the guide.
Click to expand...
Click to collapse
Or if on Windows, simply: Do the following in folder where files are located.
Shift+Right-Click > Open Command Window Here
I've never had an HTC device before but does using the HTC bootloader unlock is that making it s-off? Also I don't see the DROID dna on the list
Sent from my SCH-I535 using xda premium
hi
im very new in the forum thats my first post
i tried to install an app that required a rebbot in my gt-i9300, i rebooted and i got an pop-up window said that factory mode has crashed.
i searched for days in the internet and i found this thread: http://forum.xda-developers.com/showthread.php?t=1762204&page=53
i did all but my galaxy says that its unable to chmod /efs/FactoryApp/factorymode: no such file or directory
then i realised that i have no efs directory and that i can download one from here http://forum.xda-developers.com/showthread.php?t=888193
so' my question is,
if i will flash it with odin, will the error will dissapear?
and if the answer is yes,
i understand that some people flash it because they have no imei and the phone dont recognize their sim card.
and my fear it can happen to me if ill flash it
some help please?
What app did you try installing?
slaphead20 said:
What app did you try installing?
Click to expand...
Click to collapse
the swapsd app.
but theres no matter what app i installed
i just want to know if i can install the efs directory without problems
so please help me everyone!
You have a backed up EFS on your phone ???
jje
JJEgan said:
You have a backed up EFS on your phone ???
jje
Click to expand...
Click to collapse
yes i have a backup named efs.tar in my root directory
can i restore the folder from it?
arimal199 said:
yes i have a backup named efs.tar in my root directory
can i restore the folder from it?
Click to expand...
Click to collapse
Well, obviously you can. That's what an efs backup is for
Copy the tar file to your PC and download the Android SDK.
Once the Android SDK is installed, open up a command prompt.
Once you're in the command prompt, CD to the directory where the ADB executables and libraries are.
Usually it's here:
Code:
cd C:\android-sdk\platform-tools\
Once you're in the directory where the files are, unpack the TAR file and type the following code:
Code:
adb start-server
adb push <path-to-your-unpacked-TARfile> /efs/
adb kill-server
If you need further assistance, feel free to PM or email me
Hope I could help!
Lg
familyguy59 said:
Well, obviously you can. That's what an efs backup is for
Copy the tar file to your PC and download the Android SDK.
Once the Android SDK is installed, open up a command prompt.
Once you're in the command prompt, CD to the directory where the ADB executables and libraries are.
Usually it's here:
Code:
cd C:\android-sdk\platform-tools\
Once you're in the directory where the files are, unpack the TAR file and type the following code:
Code:
adb start-server
adb push <path-to-your-unpacked-TARfile> /efs/
adb kill-server
If you need further assistance, feel free to PM or email me
Hope I could help!
Lg
Click to expand...
Click to collapse
wow
thanks man ill try it
arimal199 said:
wow
thanks man ill try it
Click to expand...
Click to collapse
oh i forgot
my pc doesnt recognize my galaxy
maybe i can go to someone that already has a adb and see if he can fix it
but really thanks
I believe you'll also need to change files owners and access rights for it to work.
Edit : if you don't have any efs folder, I think your efs partition might not be mounted. Type "mount" in a terminal emulator and check if a line refers to /efs (that should be block 3)
arimal199 said:
oh i forgot
my pc doesnt recognize my galaxy
maybe i can go to someone that already has a adb and see if he can fix it
but really thanks
Click to expand...
Click to collapse
Check out the links in my description. (Win8 help - ADB etc. etc. ...) that works with Windows Vista, 7 and 8. If you need the ADB binaries, in that same thread, you can donate a bit of money to me and I'll license you a program (Always with updated binaries) that installs ADB and fastboot to your system's root. With the click of a button
Lg
Edit: You can also download my universal Android tool kit and with the next update, all the Samsung Galaxy S III variants will be supported and you can easily backup/restore your /efs partition from there (With the Pro version, that is)
spocky12 said:
I believe you'll also need to change files owners and access rights for it to work.
Edit : if you don't have any efs folder, I think your efs partition might not be mounted. Type "mount" in a terminal emulator and check if a line refers to /efs (that should be block 3)
Click to expand...
Click to collapse
i looked in mounts and storage in cwm and saw that efs is not mounted.
can i mount it and it will work?
arimal199 said:
i looked in mounts and storage in cwm and saw that efs is not mounted.
can i mount it and it will work?
Click to expand...
Click to collapse
no i understood' i wasnt at factory mode at all!
all the time i had imei and call function , the only problem was that factory test has stopped.
so, i downloaded titanum backup pro and turned factory test app off.
now my galaxy went back to normal all works as well!
thanks for trying to help guys!
I'm trying to make an AOSP ROM, and while doing so, I now have a dysfunctional bootloader. If your tablet is rooted, please duplicate the boot.img from your system and share it with me. Would very much appreciate.
Instructions:
Use CMD and paste these 2 lines:
adb shell "dd if=/dev/block/platform/soc.0/by-name/boot of=/sdcard/boot.img"
adb pull /sdcard/boot.img
Then from ADB directory, upload to somewhere easily accessible.
Does it matter if we have updated to 7.0 or not? I'm rooted and have updated to 7.0 and would be happy to help.
That would actually be a good idea. The ROM is supposed to be 7.0.0 anyways.
Running the first command comes up as " no such file or directory"
Do you already have ADB?
mr_verystock said:
Do you already have ADB?
Click to expand...
Click to collapse
Yep. I do adb devices to make sure it recognizes the tablet and all is good there.
Maybe so I'm the same page i just open up ADB as normal : open the command prompt in my platform tools. I paste the first line in : adb shell "dd if=/dev/block/platform/soc.0/by-name/boot of=/sdcard/boot.img" I get no file or directory.
Unable to get the dumb file:
adb shell "dd if=/dev/block/platform/soc.0/by-name/boot of=/sdcard/boot.img"
dd: /dev/block/platform/soc.0/by-name/boot: No such file or directory
Edit: does a backup from the recovery could make the task done ? I backup the boot from the TWRP and I get a file of 32Mb with the name: boot.emmc.win
adb shell
cd /dev/block/platform
ls
And tell me the output. I appreciate your help!
mr_verystock said:
adb shell
cd /dev/block/platform
ls
And tell me the output. I appreciate your help!
Click to expand...
Click to collapse
Nothing, it returns an empty result
Unusual... Normally there's soc.0 or msm_sdcc.1.
mr_verystock said:
Unusual... Normally there's soc.0 or msm_sdcc.1.
Click to expand...
Click to collapse
That command never worked for me on this tablet. Yes the default kernels is 32mb.
You can get it from twrp backup as .win and then rename it (if it is not compressed) or use AUT or SuperR's kitchen to obtain it.
Another method would be flashifire>backup.
Im still on MM so I can not help you.
Try these: https://drive.google.com/file/d/0Bz54O_w1LEYpQ1k0aDVHX29NbkE/view?usp=sharing
the rooted files I grabbed from TWRP backup, should be idential to the ones get using dd method.
the stock files I extracted from stock kdz file using WindowsLGFirmwareExtract-1.2.6.1-Release