Related
WARNING: IN THE EVENT THAT ANYTHING GOES WRONG, I WILL NOT BE HELD ACCOUNTABLE. I CANNOT STRESS THIS ENOUGH!!!
EDIT: I FORGOT, BEFORE CHANGING RECOVERY OR DOING ANYTHING, ALWAYS DO A NANDROID BACKUP!!!
If you have flashed a custom recovery (clockwork, j_r0dd, etc.) but you want to
1) accept OTA updates but cant do so with the custom recovery
2) send your phone for repair and not void your warranty
3) or UNROOT YOUR PHONE,
it should be easy to revert back to your stock recovery that came with your phone.
NOTE: THIS PROCEDURE WILL ONLY WORK IF THERE IS AN AVAILABLE OTA UPDATE FOR YOUR PHONE!!!
YOU WILL HAVE TO RE-ROOT YOUR PHONE IF YOU WANT ROOT ACCESS AFTER UPDATING! DO NOT RE-ROOT IF YOUR PHONE IS TO BE SENT FOR REPAIR!
Step 1) Download the OTA update. (I have a uploaded a sample update zip at
www . sidsoftinc . com / Blur_Version.0.3.9.MB300.Retail.en.03.zip
*remove the spaces)
Step 2) On completion, the phone should reboot and enter recovery mode, using the custom recovery to update. However, this should fail as most custom recoveries prevent original updates. Note the location of the downloaded update (likely at /cache)
Step 3) Power down the phone and enter into recovery mode manually
Step 4) Using ADB, pull the folder containing the update zip to your computer
Code:
adb pull /**storedlocation**/**nameoftheupdate**.zip update.zip
Step 5) Open the update.zip in your adb folder and look for a file called recovery.img (most likely in system folder)
Step 6) Open up the adb shell and flash the new recovery (recommended)
Code:
adb shell
su
flash_image recovery recovery.img
or you can place it in /system and it will be auto-flashed (not recommended)
Code:
adb push recovery.img /system/recovery.img
Step 7 (if possible) Make it permanent by deleting the custom recovery in /system
Code:
adb shell
cd system
su
mount -o rw,remount /dev/block/mtdblock1 /system
rm recovery.img
mount -o ro,remount /dev/block/mtdblock1 /system
exit
exit
Step 8) Reboot the phone and if you see a triangle warning sign, reboot your phone again. You should see your homescreen before it reboots to install the update again. This time, the original recovery will be used.
Once finished, your phone will be upgraded, unrooted and your applications and data will still be retained.
If you wish to install your previously used custom rom again, you must flash the custom recovery and install the rom, again
If I made a mistake, please do inform me. Thank you
I'm trying to do this for the Tmo G2 and I have reverted using another technique but the clockworkmod is still there. I thought it would get removed!
I have no idea how to get rid of it. Can you give me alittle help?
Did your clockworkmod recovery flash itself into your nv ram. If so then no one can help you there. If you have an ota update and pulled it to your pc, send me a coy and I'll see if I can help you. If you can, send me your ota update zip to [email protected].
Sent from my Motorola Backflip using the XDA App
I'm honestly unsure if it flashed to the nv-ram. Possibly, basically if I do a system boot (power +vol down) and select recovery, it will load the HTC green text with white background then go into clockword recovery. I'm not exactly sure why it still does this.
I used the method on this FORUM THREAD to un-root and get back to stock (using the available files there and method 1-a). I'm just unsure why the clockwork recovery is still there. I'm hoping I can still get back to stock recovery. Possibly I just need to flash the stock recovery.img??
Also, I had some troubles initially with ADB, which is why I used the VISIONary method of rooting. I'd love to try out the gfree method since I believe my ADB is working correctly now and test out some other roms to see what I like the most.
I know you are probably in a different time zone that is way ahead of mine........but can't I just reflash the stock or update ota recovery.img in fastboot mode.......OR is this a bad Idea???
Many users have accidently accepted ota updates on custom rims and recoveries. for fastboot, I did mention that flashing stock recovery and update is possible via adb shell.
Sent from my Motorola Backflip using the XDA App
siidheesh said:
Many users have accidently accepted ota updates on custom rims and recoveries. for fastboot, I did mention that flashing stock recovery and update is possible via adb shell.
Sent from my Motorola Backflip using the XDA App
Click to expand...
Click to collapse
I tried flashing the stock recovery but I'm not sure why it didn't work, I had hboot and flash_image. I used the adb shell way as well. It gave me error in partitions or whatever. I don't know what to do.
do you have Blur_Version.0.3.10.MB300.Retail.en.03.sbf file?
I dont happen to have that file, but i do have Blur_Version.0.3.9.MB300.Retail.en.03.zip
if you need it.
Cockwork Mod
I'm pretty green so this may sound really dumb, but can you flash sbf files to your phone via Clockwork Mod, or does it have to be done via RSD Lite. I cannot get RSD to recognize my device in 4.7 or 4.8. Please help.
do you have a stock image for the huawei ascend for cricket or does anyone here have it?
Unrooting......
I download the RECOVERY file you supplied (thank you)
"Blur_Version.0.3.9.MB300.Retail.en.03.zip"
If I reboot into Recovery and just flashed that zip file, would it work that way to unroot?
Provided you are flashing on a MOTOROLA BACKFLIP, yes. However, you might want to flash the AT&T 2.1 update for the backflip instead, if you reside in the US. Flashing back any official firmware unroots your phone
I'm looking to root and unlock my AT&F Motorola Backflip (MB300).. Any suggestions?
Sent from my NexusHD2 using Tapatalk
OTA for Samsung Galaxy Ace is a CFG file, not ZIP
Hello,
Just for interest, I received an OTA for my Samsung Galaxy Ace but it didn't come as a ZIP file - it came as a CFG file (which is not a ZIP, but actually a proprietary package - which I can't remember the name right now).
However, I did find the stock recovery elsewhere in this forum, and I installed it. But that wasn't enough for the OTA to be installed - it still fails.
Corrupted?
siidheesh said:
Step 5) Open the update.zip in your adb folder and look for a file called recovery.img (most likely in system folder)
Click to expand...
Click to collapse
I can't find it. I have an Alcatel Pop C1 4015X. Help?
Trying to unroot Xperia Z2
I am trying to unroot using update files from the Sony Xperia Companion. I found the update files (I think). I used Flashtool to decrypt the FILESET, but there is no recovery.img in the decrypted folder. The folder I decrypted is in Xperia Companion/Sony Mobile Update Engine/localstorage/db/13740270 and that is the only folder that has decryptable files. They are named FILE_8977018 and similar before decryption and various .sin .ta files (examples auto-boot.ta, cust-reset.ta, simlock.ta). Am I using the right decryption to get the recovery.img?
Update on 9/11/11: Thanks to phburks there is now a flashable zip to root the G2X stock rom. He figured out that the update-binary we were using was not compatible with the G2X. He found the compatible binary that allows us to create flashable zip files. Hats off to phburks. This is an unsigned zip and you should not be required to toggle signature verification. Of course the files required to root the phone (su and Superuser.apk) were created by Chainsdd.
There are two flashable zip packages. The first one roots the G2X. You simply flash it with Clockworkmod Recovery. The second zip unroots the phone for those who wish to unroot their device for whatever reason.
After rooting go to the Android Market and get the Busybox installer referenced below. Use that to install and keep Busybox updated.
Root Zip for G2X: http://www.mediafire.com/?92qpr525ztblh8w
Unroot Zip: http://www.mediafire.com/?2vr7cmgg7qcdn14
HOW TO ROOT
1. Install latest Clockworkmod Recovery using NVFlash, if you haven’t already done so.
http://forum.xda-developers.com/showthread.php?t=1056847
2. Download the root zip package referenced above.
3. Put the zip package on your internal or external sd card on your G2X. Do not unzip the package.
4. Turn off phone and boot into Clockworkmod Recovery by pressing volume down and power and hold until the fancy LG (second one) appears.
5. Select install zip from sd card. Select and flash the root zip package. Note: You navigate in Clockwordmod Recovery by using the volume keys up and down and commit the action by pressing the power button.
6. Reboot your phone. You are now rooted.
NOTE: THE FOLLOWING BELOW IS OBSOLETE. IT IS LEFT FOR HISTORICAL PURPOSES ONLY.
Original post made on 9/9/11:
I wanted to run the stock Gingerbread ROM and wanted to root it without flashing a new ROM. I was able to succesfully do it and the instructions are below. I was attempting to make an update.zip to do this but it kept getting a "status 0" error. The original superuser zip by ChainDD also gets this error. So I decided to try and root it using ADB commands while running Clockworkmod Recovery. Here is how I did it. If someone can help me get an update.zip that will install without error in Clockworkmod Recovery to make this easier for people to install it would be much appreciated.
1. Download my G2X root package that includes necessary ADB files (Android SDK install not required) and unzip the contents. The package contains the latest versions of “su” and “Superuser.apk”.
http://www.mediafire.com/?6rdrdfxvdoq9nkv <download link for my root G2X package>
2. Install latest Clockworkmod Recovery using NVFlash, if you haven’t already done so.
http://forum.xda-developers.com/showthread.php?t=1056847
3. Boot into Clockworkmod Recovery by holding down volume down and power until fancy LG logo shows (about ten to fifteen seconds). This is not the first one displayed when the phone powers up. Wait for recovery to start. Just to be safe perform a backup of your device’s current state.
4. Using the recovery menu scroll down to “mounts and storage,” press the power button, scroll down to “mount system” and press the power button.
5. Now that your system is mounted plug your phone into your computer (let drivers install if you have not done before – requires LG USB driver package).
http://bit.ly/qyoAxY <shortened link for direct download from LG server>
6. Open a command prompt windows on your computer. In the command prompt window change to the directory to where you unzipped the G2X root package.
7. Issue the following ADB commands. Do not type the the text in the brackets <>. That is just information on what the command is doing.
adb kill-server
<make sure no conflict with another version of adb server running>
adb devices
<checks to see if phone is connected to adb>
adb push system /system
<make sure you type a space before “/system”>
adb shell chmod 6755 /system/bin/su
adb shell ln -s /system/bin/su /system/xbin/su
<make sure you type a space before “/system/xbin/su ”>
8. System is now rooted. You can unplug the USB cable now.
9. Now in Clockworkmod Recovery choose “unmount system.”
10. Go back to the main menu and choose “reboot system now.”
11. If you want busybox (some root programs such as Titanium Backup require it) on your system go to the Android Market after rebooting your phone and search on “Busybox.” Download and run the Busybox installer by Stephen (Stericson). When you are prompted allow it to have superuser permissions.
http://bit.ly/qIAoXZ <link to Android Market page for Busybox>
12. You are now rooted with a working busybox installation.
13. It is a good idea to go back into recovery and make a backup of your newly rooted system before you start installing and running programs that obtain superuser permissions.
14. Enjoy the power!
Please click the Thanks button if this helped you out.
Reserved for future use.
Much appreciated for the help, but I don't think I will be using it.
Why not just load a rooted GB or xboards GB, same thing isn't it? lol.
Paul Nur said:
Much appreciated for the help, but I don't think I will be using it.
Why not just load a rooted GB or xboards GB, same thing isn't it? lol.
Click to expand...
Click to collapse
This is for people who have been using the phone after applying the update and don't want to start from scratch again. This lets you just root the phone without needing to flash a rom and format the system.
Wow, I've been waiting fire this thanks jboxer.
Sent from my LG-P999 using XDA App
jboxer said:
This is for people who have been using the phone after applying the update and don't want to start from scratch again. This lets you just root the phone without needing to flash a rom and format the system.
Click to expand...
Click to collapse
Ohhhhhhhhhhhhhhh, I got it lol thanks for showing me it from a different angle
still realy no point xboarders is more stable and much faster then stock and all u need to do is flash his rom then go to advanced restore and only restore data ive gotten away with that doesnt always work though
Always good to have more options.
phburks said:
Always good to have more options.
Click to expand...
Click to collapse
Damn straight. Keep it up, jboxer.
Sent from my LG-P999 using xda premium
Very nice! Thanks man, much appreciated.
Sent from my LG-P999 using XDA App
awesome i tried it on another g2x phone running 2.3.3 root the phone so fast plus with no lost data
thread rated 5 stars ^-^
Change Directory
jboxer said:
I wanted to run the stock Gingerbread ROM and wanted to root it without flashing a new ROM. I was able to succesfully do it and the instructions are below. I was attempting to make an update.zip to do this but it kept getting a "status 0" error. The original superuser zip by ChainDD also gets this error. So I decided to try and root it using ADB commands while running Clockworkmod Recovery. Here is how I did it. If someone can help me get an update.zip that will install without error in Clockworkmod Recovery to make this easier for people to install it would be much appreciated.
1. Download my G2X root package that includes necessary ADB files (Android SDK install not required) and unzip the contents. The package contains the latest versions of “su” and “Superuser.apk”.
http://www.mediafire.com/?6rdrdfxvdoq9nkv <download link for my root G2X package>
2. Install latest Clockworkmod Recovery using NVFlash, if you haven’t already done so.
http://forum.xda-developers.com/showthread.php?t=1056847
3. Boot into Clockworkmod Recovery by holding down volume down and power until fancy LG logo shows (about ten to fifteen seconds). This is not the first one displayed when the phone powers up. Wait for recovery to start. Just to be safe perform a backup of your device’s current state.
4. Using the recovery menu scroll down to “mounts and storage,” press the power button, scroll down to “mount system” and press the power button.
5. Now that your system is mounted plug your phone into your computer (let drivers install if you have not done before – requires LG USB driver package).
http://bit.ly/qyoAxY <shortened link for direct download from LG server>
6. Open a command prompt windows on your computer. In the command prompt window change to the directory to where you unzipped the G2X root package.
7. Issue the following ADB commands. Do not type the the text in the brackets <>. That is just information on what the command is doing.
adb kill-server
<make sure no conflict with another version of adb server running>
adb devices
<checks to see if phone is connected to adb>
adb push system /system
<make sure you type a space before “/system”>
adb shell chmod 6755 /system/bin/su
adb shell ln -s /system/bin/su /system/xbin/su
<make sure you type a space before “/system/xbin/su ”>
8. System is now rooted. You can unplug the USB cable now.
9. Now in Clockworkmod Recovery choose “unmount system.”
10. Go back to the main menu and choose “reboot system now.”
11. If you want busybox (some root programs such as Titanium Backup require it) on your system go to the Android Market after rebooting your phone and search on “Busybox.” Download and run the Busybox installer by Stephen (Stericson). When you are prompted allow it to have superuser permissions.
http://bit.ly/qIAoXZ <link to Android Market page for Busybox>
12. You are now rooted with a working busybox installation.
13. It is a good idea to go back into recovery and make a backup of your newly rooted system before you start installing and running programs that obtain superuser permissions.
14. Enjoy the power!
Please click the Thanks button if this helped you out.
Click to expand...
Click to collapse
Hi,
Sorry i'm new on rooting android phone.
on step 6. how i change the directory in the command prompt to go to the g2x root file i saved?
thanks
yogieajuz said:
Hi,
Sorry i'm new on rooting android phone.
on step 6. how i change the directory in the command prompt to go to the g2x root file i saved?
thanks
Click to expand...
Click to collapse
That's a Command Prompt windows on your computer. The easiest way is to open the desired folder in Windows Explorer and then click on the address bar. Highlight the entire location and copy it. Then in your command prompt windows type "cd" a space, right click and paste the copied location and hit return. You will now be in the correct folder in your command prompt windows.
Thank you for quick reply
jboxer said:
That's a Command Prompt windows on your computer. The easiest way is to open the desired folder in Windows Explorer and then click on the address bar. Highlight the entire location and copy it. Then in your command prompt windows type "cd" a space, right click and paste the copied location and hit return. You will now be in the correct folder in your command prompt windows.
Click to expand...
Click to collapse
Thanks jboxer, work like charm....
but when i did back up they said error can not back up image data ???
whats wrong???
never mind, i found out i run out of space on my sd card
@jboxer, I figured out the flashable zip. Just tested it on an unrooted 2.3.3 installation and it worked perfectly. I PM'd you a link to the zip. Please add it to your OP if you'd like. There's no need for me to create a separate thread.
phburks said:
@jboxer, I figured out the flashable zip. Just tested it on an unrooted 2.3.3 installation and it worked perfectly. I PM'd you a link to the zip. Please add it to your OP if you'd like. There's no need for me to create a separate thread.
Click to expand...
Click to collapse
Thanks to phburks for the good work in figuring out why our update zip packages were being rejected by Clockworkmod Recovery. We now have flashable zips to root the G2X (works on stock GB rom) and to unroot it. They are listed in the first post that I have edited.
http://forum.xda-developers.com/showthread.php?p=17398464
Hi,
Last Friday I turned my phone off and when I turned it back on it got stuck on the loading screen and has been like that since.
I tried removing the battery loads, with no joy. I tried factory reset and clearing cache through the recovery menu, still nothing. So now I want to flash it but I'm having trouble.
I can't get the phone to boot so can't use adb to push a file to the sdcard and I'm stuck with fastboot commands (which I'm not that familiar with other than what I've found on here!). I downloaded the OTA update (from links found in these forums) for my phone to take it to 4.0.3 as I thought it was worth doing. I renamed it to update.zip but when I try the command "fastboot update update.zip" I get the message:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
I then tried the full ROM from this thread: http://forum.xda-developers.com/showthread.php?t=1063664
but got the same message.
I don't know what these missing files are, or if I can create them myself! I've found other threads where people said they used replacements found elsewhere but I don't know where to find them!!
I can't find a way to get the update file onto the sdcard so can't use that recovery option.
I'd rather not have to send it back to samsung as that takes two weeks and I'm pretty sure they'd just flash it anyway!
I have the Nexus S still with stock ROM (2.3.6) and unrooted.
Any help will be greatly appreciated!! Ideally I'd like a way to transfer the update file to the sdcard and recover using the phone recovery. Failing that, I'd like to flash it using fastboot.
cheers
First you need to download this : http://www.4shared.com/zip/2L09-JyW/Root_Nexus_S.html
Just unpack , connect your phone and click run.bat....
After that you need : remove install-recovery.sh just in .....
run in windows-> Start->at the search bar write cmd and navigate into your android sdk is installed
For me :
C:/"Programs and Files (x86)"/Android/android-sdk/tools/>adb shell
# rm /system/etc/install-recovery.sh
#exit
or with Root Explorer into system/etc/install-recovery.sh just renam it (ex. : .sh.old)
thanks for the reply.
What will this do exactly?
I thought adb commands only worked when the phone was booted up?
just had a look at the bat. So it seems this will wipe and root the phone adding superuser privelages?
Is this the only way I can get it working again and once I've done this, how do I undo it as to get the stock version of ICS do I not need to be unrooted or will flashing the stock version from the link in my OP automatically unroot the phone and replace the recovery image etc?
thanks again for your help - I'm a bit of a noob when it comes to rooting and ROMs!
Forgot to say, I have GT-i9020 model if it makes any difference.
Skyap said:
Forgot to say, I have GT-i9020 model if it makes any difference.
Click to expand...
Click to collapse
My tools will root your device and installed CWM ...after that you can do anything you want....
I'm now rooted and have cwm recovery. Had some issues transferring files to the sdcard but seem to have moved a couple of files, but when I try to update using them I get...
Finding update package...
Opening update package...
E:Can't open /sdcard/name-of-file.zip
(bad)
Installation aborted.
I get this whether its the full stock ROMs found on here or the update only packages found on here.
Any ideas?
Skyap said:
I'm now rooted and have cwm recovery. Had some issues transferring files to the sdcard but seem to have moved a couple of files, but when I try to update using them I get...
Finding update package...
Opening update package...
E:Can't open /sdcard/name-of-file.zip
(bad)
Installation aborted.
I get this whether its the full stock ROMs found on here or the update only packages found on here.
Any ideas?
Click to expand...
Click to collapse
Trying to mount sdcard into CWM and see what happens.
---------- Post added at 07:37 PM ---------- Previous post was at 07:34 PM ----------
Reboot into recovery.
Go into "mounts and storage"
Select "mount sdcard"
Select "mount USB storage"
Shortly after your SD Card will be mounted on your computer.
please help my sh-12c stuck in boot
hi my sh-12c stuck in boot wont open could you hrelp me to guide ?
i enable su and and i change permission in settings thats all in hope if morelocal2 works but it doesnt work and was not problem to use but , i restart in hope if it work , but it stuck in the boot logo Auuos moving any way to restore ?
Hi.. I installed ICS on my Tab but i receive an wifi error... disconnect unexpectly... After factory reset I tried to instal again ICS stock using Odin but won't boot... My tab is using root... Please help my... I can't use my tab and i'm dead
Catalinq said:
Hi.. I installed ICS on my Tab but i receive an wifi error... disconnect unexpectly... After factory reset I tried to instal again ICS stock using Odin but won't boot... My tab is using root... Please help my... I can't use my tab and i'm dead
Click to expand...
Click to collapse
If you are stuck on the splash screen, the first thing to try is to wipe the cache and dalvik-cache from the recovery menu. A full wipe may also be required, although I would not recommend it until you try the suggestions below.
Use ADB (first install SDK)
HTML:
adb devices
HTML:
adb reboot
P6200
Doesn't start...What to do? I tried to instal a custon rom but same problem... Logo image appear and dead. I can acces download mode and CM6... How to fix this ugly problem?? Thanks
Catalinq said:
Doesn't start...What to do? I tried to instal a custon rom but same problem... Logo image appear and dead. I can acces download mode and CM6... How to fix this ugly problem?? Thanks
Click to expand...
Click to collapse
Bootloops are mainly caused because system files interfering with each other which causes instability and/or crashes at the boot sequence.*To find the cause of a bootloop you have to think about what you did before getting the bootloop.Choose one of the following reasons that caused the bootloop for you and try out its solution.- After flashing a new rom*If you flash a new (base)rom with odin your /data will be kept. This means your old dalvik-cache will be used for the new system files which would result in a bootloop, to fix this problem:1. Start your phone in CWM Recovery2. Go to Advanced3. Choose "Wipe dalvik-cache"4. Now go to "Mounts & Storage"5. Choose "Wipe /cache"6. Reboot your phoneif the problems still exists after doing that and you're sure it's not related to the rom, then you need to do this:1. Start your phone in CWM Recovery2. Now go to "Mounts & Storage"3. Choose "Wipe /data"4. Choose "Wipe /cache"5. Reboot your phone.
ADB can be used to access the phone while booting, be aware that some bootloops make it unable to use ADB since they do not go further then the samsung logo.*The only tricky part about using ADB with bootloops is that you have to do it on the right time, this is just after the Galaxy logo, so just when the bootanimation starts. The easiest way to enter your phone in this part is using a batch script that monitors the state of your device and connects directly when possible.
Using the original cwm zip is the easiest way, since the zip is already created for you, you only need to replace the files with the original rom files. You can get those files from the deodex packages for baseroms which are posted on the forums. If you are using an odexed ROM, you can get your files from system.img.ext4 (open the baserom: *.tar.md5 with Winrar and extract system.img.ext4)Now you can open system.img.ext4 with "DiskInternals Linux Reader". browse to the app/framework directory and extract the needed files from the image file.Once you got the same files as present in the original CWM zip you can easily drag em into the archive, then choose "store" as compression level. Now finally you need to put it on your sdcard and install it.If you don't have an external sdcard or you can't reach your internal sdcard (which is very likely when you have a bootloop), you can use ADB to push the zip to your phone, read about how to use ADB ..
HTML:
@echo off
cd /d %~dp0
echo.
echo Waiting for device...
adb wait-for-device
echo.
adb -d shell stop
adb push mycwmfix.zip /sdcard/mycwmfix.zip
adb reboot recovery
This script will wait for the device to become ready, when it's ready it freeze the device, so the script has more time to push the file (instead of keep rebooting). Then it will push the specified cwmfix zip to your sdcard, and after that it will reboot in recovery so you can install the cwm fix you made.
screen
Screen here
Catalinq said:
Screen here
Click to expand...
Click to collapse
How to fix it?
tab 2
Catalinq said:
How to fix it?
Click to expand...
Click to collapse
we have the same problem did u fix ung tab can u share with me thanks
I have a Samsung galaxy tab 2.One day as I decided to wipe everything,i noticed a message in the recovery mode saying unable to mount efs.I cant open my tablet or anything.After looking on the internet,people were telling me to flash a custom recovery like CWM.In order to do that I need to root my tablet.To root my tablet I need to enable USB debugging,which I can't because I can't access it.Can you help me please?
Shedopen123 said:
I have a Samsung galaxy tab 2.One day as I decided to wipe everything,i noticed a message in the recovery mode saying unable to mount efs.I cant open my tablet or anything.After looking on the internet,people were telling me to flash a custom recovery like CWM.In order to do that I need to root my tablet.To root my tablet I need to enable USB debugging,which I can't because I can't access it.Can you help me please?
Click to expand...
Click to collapse
Boot to download mode and flash CWM or TWRP for your model number via Odin. Then you boot into CWM or TWRP and flash SuperSU.zip to root your device. I suggest TWRP instead of CWM.
Then, if you have TWRP you can use the built in file manager in TWRP to pull a copy of your build.prop file from /system, then copy it to PC then open build.prop in a text editor then find these lines in it:
persist.service.adb.enable=1 persist.service.debuggable=1 persist.sys.usb.config=mtp,adb
Change these lines in your build.prop to match the example above. You may not have all of these lines, change the ones you have and/or type the lines you don't have in for yourself then save the edited build.prop then adb push that copy back to /system to overwrite the existing unedited build.prop. Reboot the device and USB debugging should be enabled.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
Boot to download mode and flash CWM or TWRP for your model number via Odin. Then you boot into CWM or TWRP and flash SuperSU.zip to root your device. I suggest TWRP instead of CWM.
Then, if you have TWRP you can use the built in file manager in TWRP to pull a copy of your build.prop file from /system, then copy it to PC then open build.prop in a text editor then find these lines in it:
persist.service.adb.enable=1 persist.service.debuggable=1 persist.sys.usb.config=mtp,adb
Change these lines in your build.prop to match the example above. You may not have all of these lines, change the ones you have and/or type the lines you don't have in for yourself then save the edited build.prop then adb push that copy back to /system to overwrite the existing unedited build.prop. Reboot the device and USB debugging should be enabled.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
I'm having trouble flashing Supersu.zip.Everytime I flash,i type SU into the Terminal and it always says SU not found.Do I have to use adb from now on in order to replace efs?I also can't find the build.prop file that you are referring to in your comment.Thank you
Shedopen123 said:
I'm having trouble flashing Supersu.zip.Everytime I flash,i type SU into the Terminal and it always says SU not found.Do I have to use adb from now on in order to replace efs?I also can't find the build.prop file that you are referring to in your comment.Thank you
Click to expand...
Click to collapse
You don't flash SuperSU.zip with adb/fastboot.
Move the SuperSU.zip file to your device's internal storage or put it on an external sdcard, then boot into TWRP and choose the "install" option, then browse to where you stored SuperSU.zip and flash it.
In my first reply to you, I didn't say anything about flashing SuperSU.zip in a terminal, I told you to boot into TWRP and flash SuperSU.zip. Pay attention to what is told to you, word for word.
You could have easily done some searching to understand those instructions. Learn to search for answers.
You need to be rooted first, then you can find and edit build.prop.
Build.prop is very easy to find, again, learn how to search for answers.
Build.prop is located in /system/build.prop. It's in system partition, not in your internal storage.
Try using adb pull to get a copy of build.prop then edit the copy, save the copy and adb push it back to its location in /system/build.prop.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE