Related
This post will no longer be updated and is pretty much for the archives at this point. It detailed the rooting process for Linux users right after the Slide was first rooted. Since then, newer, more foolproof methods have been devised. For those rooting their phones today (or any point since T-Mobile's OTA update), please see this link: http://forum.xda-developers.com/showthread.php?t=780213. It says it's Ubuntu-specific, but the instructions there should apply to any GNOME desktop and any other desktop with slight modification. Thanks for the comments on this thread. I hope it helped.
Most of this is not new information, but it's all in one post for the first time. I post it in case Linux (and probably MacOS) users need clarification on the process. It should keep people from having to dig in deep threads to find all the info needed. I only added the loop.sh for Linux and the partitioning information.
For all the following, I assume that the reader knows how his computer works, but not necessarily Android rooting.
Preliminary Information
1. As always, make backups and take notes. You might want to make a list of installed apps you want to reinstall later, for example.
2. Install adb. Download it here: http://developer.android.com/sdk/index.html. adb is a little program distributed as part of the Android software development kit (SDK). Its job is to communicate with the phone from a shell (terminal). To install adb, I strongly suggest you copy the adb file from the tools directory into your system's /usr/local/bin directory. This way, it will always be in your path. If you don't intend to do development work on Android applications, feel free to delete the rest of the SDK after installing adb.
3. Start adb as root. In more traditional Linux distros, this can be done by typing "adb devices" in a root terminal ("su" then "adb devices"). In Ubuntu-based distros, "sudo adb devices" followed by your password should do the trick. You'll get a message about the adb daemon being started. If not, sometimes typing "adb root" or "adb start-server" as root will do the trick.
4. Make sure your phone has "USB Debugging" checked off in Settings > Application > Development
5. It may not make any difference, but I turn off the "disk drive" option, so that my SD card doesn't mount when the phone is plugged in via USB (unless I need it to).
Partitioning the SD Card (Optional)
This is an optional step, as ROMs are coming out now that allow swapsace (virtual memory) and apps2sd (installing applications to the SD-card rather than on the phone's internal memory). Right now, most Slide ROMs support apps2fat32, so the whole card can be left as is (one, big, fat32 partition). If your desired ROM supports apps2sd using an ext2 or ext3 partition, you can save some headache later by doing this step first. If you don't want it, just skip to the next section.
1. Using the package manager for your Linux distro, install parted. GNOME users have a great, graphical frontend to this utility called gparted. KDE users have the KDE Partition Manager available to them. I only have gparted, but the instructions should be similar for all variants. The graphical frontends take a lot of the pain away from using parted (automatically formatting for ext4, for example). For the braver souls, there is a much more detailed tutorial for using vanilla parted from the command line here: http://forum.xda-developers.com/showpost.php?p=4098568&postcount=1.
2. Mount your sd-card, either using the "disk drive" function of the phone, or in an external card reader.
3. Make a backup of your sd-card by simply copying and pasting to a new folder.
4. Start up the partition manager of your choice with root permissions (using gksu or kdesu).
5. Make sure your desktop environment (KDE or GNOME) or a terminal doesn't have a file manager window open to the sd-card partition. You can't unmount a partition that's being accessed.
6. Find out which device node is assigned to the partition by typing "dmesg" in a terminal. The last few lines should tell you how it's assigned. Mine was /dev/sdg1, for example.
7. Using the dropdown menu, select your sd-card partition in parted.
8. Right-click on the partition in the bottom pane of the window and select "unmount".
9. Delete the partition using the same, right-click menu.
10. Now you're left with free space to configure as you see fit. You use the same right-click menu to create partitions.
11. When done, click "apply" and the partition manager will create and format the partitions you've selected.
12. When done, the computer should mount two partitions from the card, one for apps, the other for user data. Copy your backed-up files to the larger partition.
NB: Android phones can work with a smallish ext* partition at the beginning of the card for apps (around 512MB should be more than enough for almost anyone), a super-small swapspace in the middle (no more than 32MB, if any at all--it's up for debate whether the Slide benefits from swapspace at all), and the rest of the card formatted as FAT32 for the "normal" partiton. I'll leave those decisions to those who have the need and desire. Also, whether to use ext2,3, or 4 for the apps partition is a matter for debate, and some kernels for other phones didn't support the newer versions at all. All that is beyond the scope of this howto, mainly because I won't be trying it out.
NB2: Eugene has released Koushik Dutta's recovery scripts that can help automate the partitioning process. It can be done directly from recovery, rather than on the computer. I much prefer the old way, as it gives more flexibility. For reference, the post with instructions is found here: http://forum.xda-developers.com/showpost.php?p=6993132&postcount=1.
Getting root (original HOWTO at: http://forum.xda-developers.com/showpost.php?p=6820344&postcount=1)
The following instructions are "the old way" to gain root. There is a new method found at: http://forum.xda-developers.com/showpost.php?p=7658764&postcount=1 that seems to be a saner process, but I have not tested it as of yet.
1. Download the Slide Root package: http://outboundlink.us/anxo/dr_ta_1...ttp://www.4shared.com/file/IfrPbWG7/Root.html
2. Extract it somewhere convenient (I'm using the Desktop folder here. I'm also renaming the folder "slideroot" to keep things simple).
3. Open a terminal and cd to the slideroot folder you just created.
4. The "loop.bat" file here is of no use to you. Use a text editor to make your own loop.sh file, or edit loop.bat and rename it when you're done. It should contain the following:
Code:
#!/bin/sh
watch -n .50 adb devices;
done
5. Power on the slide while holding down the Volume-down button. This will bring you to the bootloader screen (three droids on skateboards). Plug the Slide in via USB.
6. Just to make sure everything is working correctly, type "adb devices" in the terminal to make sure the system is seeing your phone properly. If so, run your loop.sh by typing "sh loop.sh".
7. Use the Volume-down button on the phone to select "recovery" and press the power button to enter. The terminal will flash a few messages like "offline" and "recovery". When the phone's screen shows an icon of a phone with a red triangle, you know it worked.
8. Press Volume-up and Power together to enter the recovery menu on the phone.
9. Now, back in your terminal, hit "ctrl-C" to cancel the loop.sh script.
10. Type "adb push ota.zip /sdcard/update.zip" and hit enter.
11. Type "adb push update.zip /sdcard" but DO NOT hit enter yet.
12. This step requires some coordination and timing. On the phone, select "run update.zip" and press the power button. When you see a little greenish progress bar at the bottom in the background, hit enter in your terminal.
13. If it worked as planned, the phone will see the keys from the first file you pushed, and then use the file you're pushing now to run clockwork recovery. If not, don't worry. Just repeat. I haven't had to do it more than once yet.
14. Once this is done, reboot the phone from the menu system and wait. You can use "adb devices" in the terminal to see if the phone is detected.
15. Type "adb shell" and look for the "$" prompt. If you type "su" you should get a "#" (root) prompt. Give yourself a pat on the back.
Installing the Engineering ROM (original HOWTO at http://forum.xda-developers.com/showpost.php?p=6821968&postcount=1)
A. Now that your phone is rooted, you can "downgrade" it to the Engineering ROM. This gives a better recovery environment that allows other ROMs to be installed (custom ROMs are signed with the test keys; the original recovery will not install them since it looks for your carrier's keys.)
B. Download two files: http://outboundlink.net/anxo/dr_ta_1/goto.php?DR_id=1359&linkout=http%3A//www.4shared.com/file/OsmF_ZD7/ESPRIMG.html and http://www.4shared.com/file/sz0VO2TL/SlideEng-package.html.
C. I extracted the SlideEng-package.zip, copied the contents inside loose to the Desktop, and copied the ESPRIMG file to my sd card.
1. cd to the Desktop and type "adb push flash_image /data/local" and hit enter.
2. Type "adb push mtd0.img /data/local" and hit enter.
3. Start an adb root shell as above ("adb shell" then "su")
4. Type "cd /data/local"
5. Type "chmod 04755 mtd0.img" and "chmod 04755 flash_image". I didn't change any permissions on the other files in that folder, just in case.
6. Type "./flash_image misc ./mtd0.img" and hit enter.
7. Power off the phone.
8. Holding Volume-down, power the phone back up. The recovery will scan the sd card and automatically detect the update file (from step "C" above) and prompt to install it. Hit Volume-up to install.
9. You're done. Just reboot the phone after the update and you're good to go. The boot process will be a little longer this time around.
Updating the Radio (May be optional) (Original HOWTO at: http://forum.xda-developers.com/showpost.php?p=6856313&postcount=1)
I leave this section here for archive purposes. Since switching the ROM to ChiefzReloaded's OTA in the "Installing a custom ROM" section below, this step is no longer necessary, as it contains the newest radio. Unless you're installing a custom ROM released before the last T-Mobile over-the-air update, feel free to skip this section.
When we downgraded the system to the Engineering ROM, we downgraded our radio as well. The following instructions will bring us back to the stock radio version.
1. Download the following file: http://files.androidspin.com/downloads.php?dir=chiefzreloaded/ROM/&file=Newest_Slide_Radio.zip and copy it to your sd-card.
2. Remember that update.zip way back in the rooting section? The one found in the slideroot package? Copy it to your sd-card as well, if it's not already there. I deleted the one on my sd-card and re-copied it, just in case. It contains the clockwork recovery and can be left on your sd-card for future upgrades.
3. Reboot the phone into recovery (should be easy now.)
4. Select "apply update.zip from sd card" to start clockwork recovery. No looping necessary anymore!
5. From the clockwork menu system, apply the Newest_Slide_Radio.zip file you just copied over.
6. Once that's done, just reboot. The boot process will take longer and you'll see a few crazy icons before the system finally loads up. When all is finished and you're back to the home screen, the phone will pop up a dialog telling you the update was successful.
Installing a Custom ROM (Original HOWTO at: http://forum.xda-developers.com/showpost.php?p=6827968&postcount=1)
For this install, I'm using the new OTA update rooted by ChiefzReloaded. Complete information on this ROM is here: http://forum.xda-developers.com/showpost.php?p=7534163&postcount=1. Like the older SLIDEMEROOT2 I had here before, I picked it because it's mainly the same, stock ROM the phone shipped with, but with root. I had way too many "fast, stable, feature-packed" custom ROMs on other phones that really weren't that fast or stable. I don't want to lose the use of my camera/camcorder to have live wallpapers, for example. These instructions will work for any custom ROM (adjusting for the new ROM in step 1 and 4.)
1. Download the following file: http://db.androidspin.com/androidspin_filedownload.asp?release=330&type=1 and copy it to your sd card.
2. Boot the phone into recovery mode.
3. From the recovery menu, select "apply update.zip from sd card". As stated earlier, this update.zip file contains the clockwork recovery. Applying it like an update will always load clockwork from now on.
4. In the clockwork menu, select "apply any zip from sd card" and select CR_Mod_1.35.531_OTA.zip.
5. Let the update take its course, reboot, wait, and enjoy.
Going Back to Stock (Just in case) (Original HOWTO at: http://forum.xda-developers.com/showpost.php?p=6994424&postcount=1)
There may come a time when you might need your phone just the way it came from the store. It could be that you're tired of custom ROMs, a feature you find you can't live without is broken, or you need to return the phone for warranty purposes. If it gets to that point, here's how:
1. Download the following file: http://outboundlink.net/anxo/dr_ta_1/goto.php?DR_id=1359&linkout=http%3A//www.4shared.com/file/x7HRRsbM/ESPRIMG_2_.html and copy it to your sd-card.
2. Reboot the phone into recovery (just the regular one, not clockwork). The file will be automatically detected.
3. After checking the file, you'll have to hit Volume-Up to confirm the flash.
4. Once done, reboot and the Slide will be good as new.
Very nice!
I kind of wish I would have seen this before I rooted this morning!
I just rooted mine this afternoon. Figured I'd put it up while I still had it in my head.
Excellent summary!
I also wish I'd seen this before muddling through the other guides myself. Thanks for posting it!
Quick question. I plan on rooting my MyTouch Slide within the next couple days. I was just reading over your list and thought I'd try to move the adb file first. After I moved it to /usr/local/bin, and then opened a root terminal. I typed "adb", but nothing came up about a dameon being started. It looked like I had asked for the man page. Any idea why? Or if it started it anyway?
The first time you run adb, do so as root "sudo adb devices", "sudo adb root" or the equivalent. It will start the daemon. A normal user (ie, not superuser) will not have the permissions to start a daemon.
When you run just "adb" without any options, it shows you the command-line options you can use with adb. Most Linux command-line apps work the same way when run without options.
beartard,
huge props to you. this is, by far, the best guide for rooting anything that i have ever used, and certainly for the slide.
as mac osx is a *nix system, this worked great. none of the steps were missing, everything was a normal sized font, and left justified, and took me from the stock to a custom rom flawlessly.
thanks a bunch.
really.
I'm very glad it worked for you. Thanks! Did you have to do anything differently under MacOS? I used to use it before OS X came out. I know the newer versions are based on *nix, but I didn't know how similar they were underneath.
I didn't do very much differently.
I started with "How to get Root" section, as I didn't want to partition my sdcard and already had the SDK installed (obviously, though I really need to look into working with it more, as right now it scares the bejesus out of me).
I used a "do while [1]" style (I love accidentally rhyming) loop.sh file though, mostly because my terminal couldn't understand "watch" for some silly reason.
Your guide was just the one that felt the least like a tween myspace page (no offense to the other guides).
Ok, I am re-rooting my slide after having to get a replacement. I am trying to get it done using the newest ubuntu. I am a newb to ubuntu but I was able to get adb setup. When the device is booted up normally I can adb devices and recognize the device.
When I boot the phone into fast boot and adb it does not find anything. I went ahead and ran the loop.sh file and started recovery And saw the device pop up for a split second so I CTRL-C.
It does the same thing that it did when I rooted my old slide With XP. It saw the device but as soon as I CTRL-C its gone. I can do a battery pull, rerun the loop and boot into recovery and it wont find it.
Is this crap gonna be the same as on windows where you just gotta get lucky and get it to recognize? Sit here for hours on end every day until it gets recognized?????
By the way I am running everything as Root by typing sudo su in terminal before I start.
sultan.of.swing said:
Ok, I am re-rooting my slide after having to get a replacement. I am trying to get it done using the newest ubuntu. I am a newb to ubuntu but I was able to get adb setup. When the device is booted up normally I can adb devices and recognize the device.
When I boot the phone into fast boot and adb it does not find anything. I went ahead and ran the loop.sh file and started recovery And saw the device pop up for a split second so I CTRL-C.
It does the same thing that it did when I rooted my old slide With XP. It saw the device but as soon as I CTRL-C its gone. I can do a battery pull, rerun the loop and boot into recovery and it wont find it.
Is this crap gonna be the same as on windows where you just gotta get lucky and get it to recognize? Sit here for hours on end every day until it gets recognized?????
By the way I am running everything as Root by typing sudo su in terminal before I start.
Click to expand...
Click to collapse
I'm not sure what the problem is, man. I've never had to try more than once using the process above. You're using a new install of ubuntu. Do you have adb from the latest sdk?
Just added the link to a new method for rooting and updated a few minor points.
Updated partitioning info to reflect what's actually going on in the MT3GS world.
Changed custom ROM to ChiefzReloaded's OTA, eliminating the need for the "updating the radio" section.
Beartard, I want to say thank you for taking the time for typing this all out. It worked like a charm with not one problem. I have spread your link to others so they can get the same satisfaction I got from this thread. Thanks again
First off, I can't take credit for this. ninthsense and etherfish discovered the missing information in the ICS files. There are missing permissions for the keyboard backlight in the boot image, and the actual file that controls lights, /system/lib/hw/lights.n1.so is missing some stuff.
This also fixes force-close related freezes by setting the default.prop to insecure and debuggable.
manual method
Now with CWM goodness!
DOWNLOAD LH2 file for official ICS RELEASE
Awesome!
does not work for me...
Worked perfect here, that fixes my only serious issue with the ICS rom.
I'm glad i was of some help . My first significant contribution to android. Will have to get back home to test it.
does not work for me either. used Root Explorer to take the "lights.n1.so" file from download and overwrote it at /system/lib/hw/lights.n1.so, and rebooted several times, and still got nothing
The_Bizzel said:
does not work for me either. used Root Explorer to take the "lights.n1.so" file from download and overwrote it at /system/lib/hw/lights.n1.so, and rebooted several times, and still got nothing
Click to expand...
Click to collapse
Overwriting the file won't work in my opinion. As these files are part of the boot.img and resides inside the ramdisk. So even if you change something in the ramdisk and then reboot you'll return to the original version.
I guess the only way is to flash the boot.img with the files inbuilt in to the ramdisk. So the boot.img posted by "Nardholio" should work.
Mhh just copying the .so file does not work for me to, even after wiping the caches.
I'm going to try this boot.img thing later this day.
Nardholio said:
First off, I can't take credit for this. ninthsense and etherfish discovered the missing information in the ICS files. There are missing permissions for the keyboard backlight in the boot image, and the actual file that controls lights, /system/lib/hw/lights.n1.so is missing some stuff. To fix it, just copy the version from Gingerbread over the ICS version and reboot. Note this requires root. The attached post contains the file you need and an optional boot.img mod that will fix force-close related freezes and will enable the keyboard light to be controlled by third party utilities.
http://forum.xda-developers.com/showpost.php?p=30591025&postcount=42
Click to expand...
Click to collapse
Didn't work for me at first either after I copied and pasted it. But when I went through and opened up a Terminal on my phone to install everything (I always thought I had to use Ubuntu on my computer for it. I don't know why I never even thought of using a Terminal on my phone to do editing on it and all...) and went through the steps on the link (didn't clear my cache), and it all works. Just a heads up for anyone who might be as slow as I was
Both files are required then I guess. Thanks for letting me know.
Sent from my SGH-I927 using xda premium
Nardholio said:
Both files are required then I guess. Thanks for letting me know.
Sent from my SGH-I927 using xda premium
Click to expand...
Click to collapse
confirmed working after both files were pushed. warning to others, do not wipe /dev/block/mmcblk0p9 if you have not verified that boot.img is on /sdcard via terminal emulator or adb shell:
Code:
cd /sdcard
ls
goodluck!
Can anyone help me with this via step by step?
I could use a little help as well
Sent from my SGH-I927 using xda app-developers app
Yea, i could use some help too, after re-writing over the existing file didn't work
OK guys here is the step by step guide :
I'm assuming that you're rooted and are on windows PC :
1. Install root explorer or root browser lite (free) from market. And copy the boot.img and lights.n1.so from keyboard_fix.rar in root of your sdcard(phone).
2. Launch the root explorer and Delete the existing lights.n1.so file from /system/lib/hw (probably you can keep a copy somewhere)
3. Copy the lights.n1.so from your sdcard directory to /system/lib/hw
3. Make sure that the file is presen/copiedt in the directory.
4. Download fastboot.zip file attached to the post and extract it in one of your directory on the pc.
5. Connect your phone through a usb cable and i'm assuming you've the usb drivers for your phone already installed on your pc.
6. Goto command prompt and change to the directory you extracted the zip file into.
7. issue the command "adb shell"
8. You should get a android prompt. Issue the command "su"
9. Issue cd sdcard and then issue "ls". Just to make sure that the boot.img is there.
10. Now issue the following commands:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p9
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p9
11. Reboot and you should get your lights.
Copying the boot.img worked for me
For those who having trouble, look at the Link, posted in the OP
How I did it:
Copy files to sdcard: Use a network enabled file manager or email or drop box (or, or, or) to get boot.img and lights.n1.so to /sdcard
Setup ADB: Google "xda setup adb"
Boot into CWMR: Reboot phone, holding power down (Link: Get CWMR)
Choose in CWMR:
Mounts > Mount sdcard
Mounts > Mound system
Execute Commands on pc
Open Shell/Cmd
Type: adb shell
Type: ls
you should geht a file listening of your root file system
Type: dd if=/dev/zero of=/dev/block/mmcblk0p9
Type: dd if=/sdcard/boot.img of=/dev/block/mmcblk0p9
Type: cp /sdcard/lights.n1.so /system/lib/hw/lights.n1.so
Choose in CWMR:
Wipe Cache
Advanced > Wipe dalvik cache
Reboot system
That was the steps as I remember, no guarantee don't brick your device if you do: use one-click-ics-leak-tool and start from scratch
ninthsense said:
OK guys here is the step by step guide :
I'm assuming that you're rooted and are on windows PC :
1. Install root explorer or root browser lite (free) from market. And copy the boot.img and lights.n1.so from keyboard_fix.rar in root of your sdcard(phone).
2. Launch the root explorer and Delete the existing lights.n1.so file from /system/lib/hw (probably you can keep a copy somewhere)
3. Copy the lights.n1.so from your sdcard directory to /system/lib/hw
3. Make sure that the file is presen/copiedt in the directory.
4. Download fastboot.zip file attached to the post and extract it in one of your directory on the pc.
5. Connect your phone through a usb cable and i'm assuming you've the usb drivers for your phone already installed on your pc.
6. Goto command prompt and change to the directory you extracted the zip file into.
7. issue the command "adb shell"
8. You should get a android prompt. Issue the command "su"
9. Issue cd sdcard and then issue "ls". Just to make sure that the boot.img is there.
10. Now issue the following commands:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p9
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p9
11. Reboot and you should get your lights.
Click to expand...
Click to collapse
Worked! thanks abunch man
LuckRocks said:
Worked! thanks abunch man
Click to expand...
Click to collapse
You are welcome. I also did it just before posting the steps and glad that the biggest bug for the leaked ROM is now fixed.
I see that the lights go off very quickly unless you keep pressing something. It's related to "Touch Key Light Duration" under "display" in the settings. But i see only 1.5 seconds which is set currently and 6 seconds. If i change to 6 it's too much.
Does somebody know how to modify this value according to whatever we need ?
Hello ninthsense,
perfect tutorial, keyboard light is working now.
Thanks,
Mister.Knister
Hummm is their gonna b a flashable zip for this ?
I have a major problem but i think there is a way to fix it, i just cant figure it out. i was adding google wallet on my rooted s3 and when reverting the build.prop file to its original form, i just copied and pasted the backup and renamed it to the original build.prop to replace the new one using root explorer. my phone does not boot up now i get the samsung startup screen and it shuts off. i could get into cwm recovery mode. any way to fix the build.prop without being able to fully boot the phone? i am on a mac but i could have access to a pc tomorrow if i need.
Its simple if u have a backup. I have not heard of anyway of getting to build.prop thru recovery.
Sent from my SAMSUNG-SGH-I747 using xda premium
You need to restore from backup (nandroid) or start over if you don't have a backup..
Did you copy the original file to ur sd card then back over?
Chances are you did.. I did the same thing lol.. And when u do that it doesn't save original permissions of the file.
The reason the wallet post says to use root explorer is because it saves the file in the same folder permissions and all and you can just rename it back.
Sorry dude u are sol.. Restore from back up or flash a new rom and start over.
Sent from my SAMSUNG-SGH-I747 using xda premium
Get into recovery, do a factory reset.
mrhaley30705 said:
Get into recovery, do a factory reset.
Click to expand...
Click to collapse
Any resolution. I have the same problem.
mrhaley30705 said:
Get into recovery, do a factory reset.
Click to expand...
Click to collapse
I don't think that would work, as far as I know a factory reset only wipes data and cache. The build.prop is part of the system, so it will not change.
Sent from my SPH-D710 using xda premium
Permissions probably got reset. Resetting to factory will not change the build.prop. Either re-install the rom or...
Do this. This will reset permissions to the correct value without affecting your data. This is easy once you get the hang of it. I do not know if I'm allowed to post up the adb file or I would.
I'm going to run through a quick setup of the Android SDK so that you can use adb if you choose to go this route. The SDK will be useful all though rooted phone usage, so I suggest you download it and use it. ADB is a very powerful tool. First, Google Android SDK. The first result should be the official site for the Google developer section. Just open that top link and the page should have a huge button that says "Download the SDK for (Windows or Mac or whatever)". Click it. Mac users.. Yours does not actually setup. You need to find the SDK Manager app within that zipped download and run it. Windows users... Run the setup. When it's done it will open the SDK manager. Both Users... Check the box next to the "Android SDK Platform-tools". Bottom Right, Install x Packages. Make sure you take note of the SDK path displayed at the top of the manager. EG. C:\Users\Josh\AppData\Local\Android\android-sdk. Mac users: Yours will be in the downloaded folder that you extracted. All Users: Navigate to that folder via terminal (mac) or cmd.exe (windows). Windows: cd C:\Users\Josh\AppData\Local\Android\android-sdk ... Mac: cd /Users/josh/Downloads/android-sdk/ ... Then navigate to the platform-tools folder that is within the SDK folder. Here is where ADB is located.
Windows instructions:
Download adb.exe, either through the Android SDK or elsewhere. Use Google.
Connect phone to computer via USB.
Boot phone into recovery.
Use cmd.exe (Use Windows key+R, and type cmd in the run window) to navigate to the folder containing adb.
E.g. "cd c:\Users\Josh\Downloads\adb"
Run "adb shell"
This should initiate a shell to the phone allowing you to run commands on the phone. If you get an error, make sure you have the drivers loaded for your phone.
Run "cd /system"
Run "chmod 644 build.prop"
Optional: Run "ls -l" and make sure that the permissions on build.prop show RW-R--R--.
Reboot phone.
Mac Instructions:
Download the adb application, either through the Android SDK or elsewhere. Use Google. Make sure you download the Mac version, not the Windows or Linux version.
Connect phone to Mac.
Reboot phone into recovery.
Open Terminal on Mac. /Applications/Utilities/Terminal.app or use spotlight to find it.
Navigate to folder containing the adb app. E.g. "cd /Users/josh/Downloads/adb/"
Run "adb shell"
This should initiate a shell to the phone allowing you to run commands on the phone.
Run "cd /system"
Run "chmod 644 build.prop"
Optional: Run "ls -l" and make sure that the permissions on build.prop show RW-R--R--.
Reboot phone.
Side note--> twrp recovery has a built in terminal and the ability to copy/paste files from internal and external SD cards. Not so sure about changing permissions easily....but through the built in terminal....might be able to load what you need (plus twrp flashable found in android dev forum) on external SD card with an adapter on a computer. Flash twrp and transfer files or use built in terminal to change perms. Good luck....
I know editing build props with es file explorer will cause That.
Sent from my SAMSUNG-SGH-I747 using xda premium
Fixed it!
Thanks everyone for your help, i feel like an idiot for not replying to anyone i didnt have it set up to notify me of replies, i figured out it was the build prop that was messed up, im not sure how this worked but i figured i would try to root again and flash the root files using the simple root steps using odin and it actually fixed the file and booted up fine! i appreciate everyones help and hope this thread helps other people because i know many people screw this up the same way i did. (i will never do anything like this without doing a nandroid backup again). THANKS AGAIN!
thanks but..
ibanezbass said:
Permissions probably got reset. Resetting to factory will not change the build.prop. Either re-install the rom or...
Do this. This will reset permissions to the correct value without affecting your data. This is easy once you get the hang of it. I do not know if I'm allowed to post up the adb file or I would.
I'm going to run through a quick setup of the Android SDK so that you can use adb if you choose to go this route. The SDK will be useful all though rooted phone usage, so I suggest you download it and use it. ADB is a very powerful tool. First, Google Android SDK. The first result should be the official site for the Google developer section. Just open that top link and the page should have a huge button that says "Download the SDK for (Windows or Mac or whatever)". Click it. Mac users.. Yours does not actually setup. You need to find the SDK Manager app within that zipped download and run it. Windows users... Run the setup. When it's done it will open the SDK manager. Both Users... Check the box next to the "Android SDK Platform-tools". Bottom Right, Install x Packages. Make sure you take note of the SDK path displayed at the top of the manager. EG. C:\Users\Josh\AppData\Local\Android\android-sdk. Mac users: Yours will be in the downloaded folder that you extracted. All Users: Navigate to that folder via terminal (mac) or cmd.exe (windows). Windows: cd C:\Users\Josh\AppData\Local\Android\android-sdk ... Mac: cd /Users/josh/Downloads/android-sdk/ ... Then navigate to the platform-tools folder that is within the SDK folder. Here is where ADB is located.
Windows instructions:
Download adb.exe, either through the Android SDK or elsewhere. Use Google.
Connect phone to computer via USB.
Boot phone into recovery.
Use cmd.exe (Use Windows key+R, and type cmd in the run window) to navigate to the folder containing adb.
E.g. "cd c:\Users\Josh\Downloads\adb"
Run "adb shell"
This should initiate a shell to the phone allowing you to run commands on the phone. If you get an error, make sure you have the drivers loaded for your phone.
Run "cd /system"
Run "chmod 644 build.prop"
Optional: Run "ls -l" and make sure that the permissions on build.prop show RW-R--R--.
Reboot phone.
Mac Instructions:
Download the adb application, either through the Android SDK or elsewhere. Use Google. Make sure you download the Mac version, not the Windows or Linux version.
Connect phone to Mac.
Reboot phone into recovery.
Open Terminal on Mac. /Applications/Utilities/Terminal.app or use spotlight to find it.
Navigate to folder containing the adb app. E.g. "cd /Users/josh/Downloads/adb/"
Run "adb shell"
This should initiate a shell to the phone allowing you to run commands on the phone.
Run "cd /system"
Run "chmod 644 build.prop"
Optional: Run "ls -l" and make sure that the permissions on build.prop show RW-R--R--.
Reboot phone.
Click to expand...
Click to collapse
So the problem with this route was that for some reason the device was not being recognized by adb, i dont know why, i thought it was a driver issue but once i fixed the phone, i was able to get adb access, so i guess that boot error was preventing it from getting recognized (which i didnt understand because my friend screwed up like me the next day and was able to adb.) but finally fixed it a few days later after trying many things and the fix for some reason was a simple process with odin, i think this article shows what i did, i dont remember exactly tho - http://smartphonefix.blogspot.com/2...r-Recover-Bricked-ATT-Galaxy-S3-SGH-I747.html
ibanezbass said:
Permissions probably got reset. Resetting to factory will not change the build.prop. Either re-install the rom or...
Do this. This will reset permissions to the correct value without affecting your data. This is easy once you get the hang of it. I do not know if I'm allowed to post up the adb file or I would.
I'm going to run through a quick setup of the Android SDK so that you can use adb if you choose to go this route. The SDK will be useful all though rooted phone usage, so I suggest you download it and use it. ADB is a very powerful tool. First, Google Android SDK. The first result should be the official site for the Google developer section. Just open that top link and the page should have a huge button that says "Download the SDK for (Windows or Mac or whatever)". Click it. Mac users.. Yours does not actually setup. You need to find the SDK Manager app within that zipped download and run it. Windows users... Run the setup. When it's done it will open the SDK manager. Both Users... Check the box next to the "Android SDK Platform-tools". Bottom Right, Install x Packages. Make sure you take note of the SDK path displayed at the top of the manager. EG. C:\Users\Josh\AppData\Local\Android\android-sdk. Mac users: Yours will be in the downloaded folder that you extracted. All Users: Navigate to that folder via terminal (mac) or cmd.exe (windows). Windows: cd C:\Users\Josh\AppData\Local\Android\android-sdk ... Mac: cd /Users/josh/Downloads/android-sdk/ ... Then navigate to the platform-tools folder that is within the SDK folder. Here is where ADB is located.
Windows instructions:
Download adb.exe, either through the Android SDK or elsewhere. Use Google.
Connect phone to computer via USB.
Boot phone into recovery.
Use cmd.exe (Use Windows key+R, and type cmd in the run window) to navigate to the folder containing adb.
E.g. "cd c:\Users\Josh\Downloads\adb"
Run "adb shell"
This should initiate a shell to the phone allowing you to run commands on the phone. If you get an error, make sure you have the drivers loaded for your phone.
Run "cd /system"
Run "chmod 644 build.prop"
Optional: Run "ls -l" and make sure that the permissions on build.prop show RW-R--R--.
Reboot phone.
Mac Instructions:
Download the adb application, either through the Android SDK or elsewhere. Use Google. Make sure you download the Mac version, not the Windows or Linux version.
Connect phone to Mac.
Reboot phone into recovery.
Open Terminal on Mac. /Applications/Utilities/Terminal.app or use spotlight to find it.
Navigate to folder containing the adb app. E.g. "cd /Users/josh/Downloads/adb/"
Run "adb shell"
This should initiate a shell to the phone allowing you to run commands on the phone.
Run "cd /system"
Run "chmod 644 build.prop"
Optional: Run "ls -l" and make sure that the permissions on build.prop show RW-R--R--.
Reboot phone.
Click to expand...
Click to collapse
Okay, I got the adb shell to run, but I run into this snag:
"Unable to chmod build.prop: Operation not permitted"
Anyone know what this means?
prior to running that command, type su then hit enter
If I made a CWM flashable unedited build.prop from a stock SGS3 rom would that help anyone? It just seems easier than all those ADB commands assuming you can still access recovery.
stratatak7 said:
If I made a CWM flashable unedited build.prop from a stock SGS3 rom would that help anyone? It just seems easier than all those ADB commands assuming you can still access recovery.
Click to expand...
Click to collapse
I'm sure that'll probably helpful to a lot of people. Unfortunately, I'm using the stock recovery so it probably wouldn't help me...
lyrictenor1 said:
I'm sure that'll probably helpful to a lot of people. Unfortunately, I'm using the stock recovery so it probably wouldn't help me...
Click to expand...
Click to collapse
If you're not comfortable with ADB: You should try to flash recovery (recommended TWRP but at this point take anything you can get) from ODIN. I know I've seen it around here somewhere. Once you do that, then flash the attached file.
This will flash in CWM/TWRP etc. I haven't tested it, so send me a PM if it doesn't work and I'll fix it up.
Edit: I've located the proper recovery file for you to flash. It's cwm, but you flash this with ODIN. Download it from here http://k0nane.info/rom/ecm/CWM-Recovery-LTE-SGS3-v5.tar.md5 . ODIN will increase your flash counter, but Chainfire's Triangle Away app takes care of that like it never happened. Odin can be found in the development thread. If you want to automate this process even further just download the qcom toolkit which walks you through the process of installing recovery. I hope this helps.
Lastly, here's the latest TWRP image file with ADB instructions. Short, sweet and simple. http://teamw.in/project/twrp2/104
crammer04 said:
I have a major problem but i think there is a way to fix it, i just cant figure it out. i was adding google wallet on my rooted s3 and when reverting the build.prop file to its original form, i just copied and pasted the backup and renamed it to the original build.prop to replace the new one using root explorer. my phone does not boot up now i get the samsung startup screen and it shuts off. i could get into cwm recovery mode. any way to fix the build.prop without being able to fully boot the phone? i am on a mac but i could have access to a pc tomorrow if i need.
Click to expand...
Click to collapse
_________________________________________________________________________________________________________________
If you got no back up give us your phone information one of us can send you one I have aTT D2att you
?
Its all in my sig get mobile odin bellow, get the tar for which ever recovery you got. I got all three. CWM, CWM Touch and TWRP for d2att (only) if different phone then use other ones.
Thats my build prop im D2att SG3 ok so just make sure. But you can grab mobile odin bellow and fix it.
_________________________________________
Just get mobile odin HERE
and flash your reocvery there CWM, TWRP, CWM TOUCH... all of them latest all in my sig bro
Here is all drop box to get any of the recoverys --------------------> Recoverys Drop Box
Get mobile odin Here along with the s3 kernal extension its all in here -----------------------> Mobile Odin
If you get hardware id missing error install these old samsung dricers this is a bonus, don't update it ----------------> Hardware ID samsung driver fix
__________________________________________________________
S3 build prop here --------------> here
Mobile odin is simple if download zip in my drop box just install it (or get it form market) download the driver you need (in my drop box) or go mobile odin thread and find it if your on a different phone. Rest is simple just load what your going to flash click the OPEN FILE option in mobile odin click tar and run it.
_________________________________________________________
Get android comander. You can mod build prop easy with it its nice GUI for installing programs or uninstalling or backups or moving files around. awesome try out here --------------------------------> ANDROID COMANDER
need anything else?
---------- Post added at 09:42 PM ---------- Previous post was at 09:20 PM ----------
lyrictenor1 said:
Okay, I got the adb shell to run, but I run into this snag:
"Unable to chmod build.prop: Operation not permitted"
Anyone know what this means?
Click to expand...
Click to collapse
Tiy need to remount system Read Write i don't think its a SU problem it could be but normaly you already got su i forget comand in adv its mount system -r i beleive. I dunno I run a script that mounts it for me let me check it out real fast
---------- Post added at 09:48 PM ---------- Previous post was at 09:42 PM ----------
crammer04 said:
So the problem with this route was that for some reason the device was not being recognized by adb, i dont know why, i thought it was a driver issue but once i fixed the phone, i was able to get adb access, so i guess that boot error was preventing it from getting recognized (which i didnt understand because my friend screwed up like me the next day and was able to adb.) but finally fixed it a few days later after trying many things and the fix for some reason was a simple process with odin, i think this article shows what i did, i dont remember exactly tho - http://smartphonefix.blogspot.com/2...r-Recover-Bricked-ATT-Galaxy-S3-SGH-I747.html
Click to expand...
Click to collapse
Just so you no a common problem when doing commands you forget to do it just trying help didn't know fixed
#!/system/bin/sh
busybox mount -o remount,rw /system
My build.prop got messed up while trying to install Google Wallet on my rooted sg3 and my phone became soft bricked. I had to reinstall the stock jellybean ROM with root that I had been running before this happened, through Odin. Solved my problem. Never got wallet to work though.
Sent from my Amazon Kindle Fire2 using xda app-developers app
Would this work on S3 T-Mobile T-999?
stratatak7 said:
If you're not comfortable with ADB: You should try to flash recovery (recommended TWRP but at this point take anything you can get) from ODIN. I know I've seen it around here somewhere. Once you do that, then flash the attached file.
This will flash in CWM/TWRP etc. I haven't tested it, so send me a PM if it doesn't work and I'll fix it up.
Edit: I've located the proper recovery file for you to flash. It's cwm, but you flash this with ODIN. Download it from here http://k0nane.info/rom/ecm/CWM-Recovery-LTE-SGS3-v5.tar.md5 . ODIN will increase your flash counter, but Chainfire's Triangle Away app takes care of that like it never happened. Odin can be found in the development thread. If you want to automate this process even further just download the qcom toolkit which walks you through the process of installing recovery. I hope this helps.
Lastly, here's the latest TWRP image file with ADB instructions. Short, sweet and simple. http://teamw.in/project/twrp2/104
Click to expand...
Click to collapse
I am having the same problem.... as the person above... Will this .Tar file below work for S3 T-Mobile T-999? Can you make one for that phone?
Thanks for your help!!
Boosoth1st said:
I am having the same problem.... as the person above... Will this .Tar file below work for S3 T-Mobile T-999? Can you make one for that phone?
Thanks for your help!!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1746682
Try downloading the toolkit from there. It should contain the necessary T-Mobile files. If you are having an issue, please PM me. Make sure you flash the right one! Be careful and read the whole thread.
Hi guys, this is my second tutorial and in this one I will show you every thing you need to do to flash a custom ROM on the LG-P350. So let's get started.
DISCLAIMER: This is tampering with the system itself and if done incorrectly a simple factory reset will not fix it. It is YOU who is doing this on your phone and I am in no way responsible if any damage happens to your device. (tough it shouldn't if you follow these steps carefully) You have been warned!
WHAT WE NEED :
1.An LG-P350 running stock Froyo
2.LG mobile united drivers, get them from here https://docs.google.com/file/d/0B7Faau7Enf-Bc1hhbWRtTkczNEE/edit?usp=sharing
3.A PC running Windows (can be done on linux too but this guide is based on Windows)
4.A microUSB data cable.
5.The official Android SDK obtained from http://developer.android.com/sdk/index.html Make sure you select the version for your OS (32-bit or 64-bit)
6.USB debugging to be on. Go to Settings>Apps>Development>Turn on USB debugging
7.ADB to be properly set up.
8.Patience to read this thread carefully
1. Root
Ok so what is root? Well simply said rooting gives us the permission to modify parts of the Android system itself. Normally when you try to tamper with it it would simply say that either you don't have the privilege to do so or it would fail. When we have root permissions then you can change anything you want.
Note: Be careful tough, removing or modifying some parts of the system can damage the system and prevent it from working/booting. Always make a nandroid backup (will talk about this later) before editing anything in the system.
Now for the rooting itself.
Most versions of the software for the P-350 can be rooted using gingerbreak, which can be found here http://forum.xda-developers.com/showthread.php?t=1044765 Get the newest version, copy it and install it on your phone and follow the instructions on screen.
For those who prefer some other root method you can also use z4root which can be found here http://forum.xda-developers.com/showthread.php?t=833953 or superoneclick which can be obtained here http://forum.xda-developers.com/showthread.php?t=803682 (For superoneclick you need the USB cable and drivers installed)
2.ADB
Ok so what is ADB? ADB is a short term for Android Debug Bridge. It is one the most essential tools in the Android world and is used for a number of things such as sending commands (which can do anything you imagine with the device), getting various log data etc.
To set it up you will have to get the latest version of the official Android SDK (look for the link in the Introduction). Once you've downloaded the sdk you will get a .zip file you need to extract. I extracted mine to C:\Program Files (x86)\Android\ (so this guide is based on that) but it can really be anywhere. If you decide to put a different directory then adapt the guide to it. Once extracted you will get two folders. Here we only use the sdk one, the other one is for the Eclipse plugin used for application development. Open up the cmd from the start menu and then input these codes.
Code:
cd C:\Program Files (x86)\Android\sdk\platform-tools\ (you adapt this to your case if you didn't extract it there)
adb shell
Do this with your device connected otherwise it's pointless.
NOTE1: In order for adb to recognize your device you must have the drivers installed.
NOTE2: If you are too lazy to type all this every time you can make a .bat script. Open up notepad and copy/paste these codes
Code:
cd C:\Program Files (x86)\Android\sdk\platform-tools\ (adapt to your location)
adb shell
pause
After that just click on File and click Save as. In the window that opened, under file type select all files and on the file name save it as adb.bat
Now whenever you want to use adb you can just double click on the script you made and it will open up adb instantly leaving out the hassle of typing in commands every time.
3.Recovery
Now that we have root it's time for the recovery module.
The recovery allows us to modify parts (or even the entire) system by "flashing" (installing) .zip files prepared by our developer. They can be tweaks,fixes, additional features or even a completely new version of Android. There are a couple of ways to do this and the choice is yours.
Before you do this you need to get a recovery image. We have a couple of them for our device:
1. AmonRa-The very first recovery for our phone. It is outdated and generally not recommended for use. If anyone wants it you can get it here http://forum.xda-developers.com/showthread.php?t=1080911
2. CWM (clockwork mod recovery)- One of the most popular recoveries around. It is a well made piece of software which will make flashing simple and fast. We have a couple of versions for our phone and the links are here:
http://forum.xda-developers.com/showthread.php?t=2075797&highlight=recovery ClockWorkMod 6.0.2.7
http://forum.xda-developers.com/showthread.php?t=1768895&highlight=recovery ClockWorkMod 6.0.1.4
You will also need a flash_image file gotten from https://docs.google.com/file/d/0B7Faau7Enf-BTURDQmp1OWIzVGM/edit?usp=sharing
Method 1: cmd
Ok so this tutorial is from a developer who has retired and who made the original recovery our phone. All credits for that go to him.
Also note that it is recommended to reboot the device prior to flashing to increase the RAM.
1.Copy the .img file and copy the flash_image file to the rood directory of your sd card NOT in some folder. If you got your recovery in a .zip then extract the .img file from it and copy it and the flash_image file to the root of the sd card.
2.Using ADB shell copy these commands into the cmd :
Code:
$ su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
# cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# sync
3.Now flash it:
Code:
$ su
# flash_image recovery /sdcard/*insert image name here*.img Here you should put the name of your .img file without the starts ofc :)
# sync
4.After that if no error occurred you can type this in
Code:
reboot recovery
WARNING: If some sort of error showed up DO NOT type in reboot recovery. This could brick your device. Instead restart the phone and start over.
Method 2: Venkat's toolkit RECOMMENDED
This toolkit does the same from above but it does it automatically without the user having to do anything. You can get it from here http://forum.xda-developers.com/showthread.php?t=1948326 It can also be used for rooting.
It is also recommended to make a nandroid backup of your current system in case you want to go back. Nandroid backup is a complete copy of your system as it is when the backup was made. It backs up EVERYTING not just apps and data, so it is a perfect thing to have if a ROM or a tweak you are trying render the phone unbootable since you can just restore the backup you made and no harm done.
That is recovery. Now you can use it to flash whichever ROM for our device you choose. You can boot to it either by typing in adb/terminal reboot recovery or by pressing the following buttons when the device is turned off: Power + Call + Volume Down. Also don't worry if the touchscreen doesn't work in the recovery. That is normal use the volume up and down buttons to navigate menus and either the menu button(for amon ra) or the call (CWM) to confirm your choice.Use the back/power button to cancel/go back.
4.Flashing
Flashing is a process where we install the entire system or its parts contained in .zip files from the recovery module.
NOTE When you get a flashable .zip package DON'T extract it to the sd card. Copy it as you got it to the root of the sd and then continue.
Now that you've gotten the ROM you desired the process is pretty straight forward. Copy the .zip file you got to the root directory of your sd. Once you've done that, reboot to recovery and make a nandroid backup (if you haven't done so already) and go to the option install zip from sd card. Then choose the .zip you copied and confirm. After it says install complete you can reboot your device.
NOTE 1: Flash only things that are either universal or made for this device. Flashing stuff not made to work on this device could damage it.
NOTE 2: When flashing new ROMs you MUST wipe Dalvik cache,cache and data partitions. It is also recommended to wipe Dalvik cache when flashing kernels.
Those are pretty much all the basics you need to get into the flashing stuff You can find loads of ROMs and other tweaks on the official P-350 forums here on xda http://forum.xda-developers.com/forumdisplay.php?f=1769
You can also find info and development support on our Facebook page https://www.facebook.com/groups/p350development/
Revision 1: Added tutorial for setting up adb, explaining what adb is, as well as an adb script code.
i think this thread need to stick, try to contact mods
A comment on the 'adb' way. Before executing the commands, you might want to cd to where adb.exe is because you will have an error executing the command and the terminal will show 'adb is not a valid command'
Sent from my X8 using xda premium
---------- Post added at 07:09 AM ---------- Previous post was at 07:07 AM ----------
And installing android sdk is optional because there are standalone adb available for download.
Sent from my X8 using xda premium
Ya sticky this thread mods, cuz' i read, Many people stuck at LG Logo or fastboot mode even hard reset when flashing ROM without recovery before..
Sent from my LG-P350 using xda app-developers app
rho57 said:
A comment on the 'adb' way. Before executing the commands, you might want to cd to where adb.exe is because you will have an error executing the command and the terminal will show 'adb is not a valid command'
Sent from my X8 using xda premium
---------- Post added at 07:09 AM ---------- Previous post was at 07:07 AM ----------
And installing android sdk is optional because there are standalone adb available for download.
Sent from my X8 using xda premium
Click to expand...
Click to collapse
It already is set to the adb.exe path that's needed in order for adb to be activated on Windows. That's why we use the cd C:\Program Files (x86)\Android\sdk\platform-tools
And I know but there are a lot of other useful tools as well. And it is most reliable too.
Good job dude
Why complicated more then needed. Just make tut with andking toolkit.
boyan81 said:
Why complicated more then needed. Just make tut with andking toolkit.
Click to expand...
Click to collapse
Not complicated, this is a basic tutorial for those who don't want/can't use his toolkit. It also has some explanations about basic Android terms which you won't find there.
It would be nice if you update the wiki too, as there is an old but yet usable guide which pretty much has the same information written here...
Sent from my GT-S5830M using Tapatalk 2
I fixed it myself and hope the advice can help someone:
A) Some of the mistakes i made during editing of the build.prop file
0. While bootlooping constantly hold volume down+power, it WILL boot to the bootloader after some time!
1. Don't use adb shell then adb pull/push, you don't need the shell here! Just use "adb pull /system/build.prop", notepad++ and "adb push build.prop /system/build.prop" to update the file, then set permissions again with "chmod 644 build.prop" and then "ls -l" to make sure the permissions of build.prop show -RW-R--R--
2. To use adb, get into fastboot->recovery and watch out that /system is mounted
3. Use the UniversalADBDriverSetup.msi to install drivers, then check check and check again that you change the drivers used to the ADB ones, not my htc, not android device. Different states of the phone sometimes activate different drivers (IE i plugged my bootloader phone in, changed drivers, got into recovery, had to change drivers again!)
4. Make a .bak file before you change anything inside android!
5. Avoid AROMA Filemanager, every time i tried to type something my keyboard got stuck and i had problems closing it. Without being able to remove the battery this is a huge risk.
B) Regarding OTA:
To disable the OTA updates i installed the app "MyAndroidTools" and disabled Service->System->Update/Upgrade(german: Aktualisierung)->UpdaterCheckIntranetService
Old Stuff:
Update: Got fastboot connecting, but adb not.
New main question: How to choose the rom i am going to flash?
Device Carrier Region Type Kernel Android Size Description
Device is clear, but Region i get TW and TW Wifi. My android Version before was 4.4.2 and i had the ota upgrade to 1.60.xxxx. Is it safe to not know what carrier, region and type i have and just chose Region TW, Type CRC, Android version 4.4.2 1.54.xxx?
Desire 816 hTC Asia TW CRC 3.4.0 v4.4.2 155 MB 1.54.709.2
Can i use the latest android one instead?
Desire 816 APTG TW MR 3.4.0 v4.4.2 156 MB 1.63.500.1
TLTR: reboot loop after rooting and tampering with the build.prop file, can get into bootloader/recovery, usb drivers wont work, how to edit build.prop/reflash stock with zip/add new build.prop?
My Phone as i remember: TW international HTC 816 single sim android 4.4.2
PC win 7 x86 ultimate
Here is what i did before the bootloop:
Rooted the phone with this instruction: https://www.youtube.com/watch?v=vhUBLhdgSPU
Quote: 1. HTC Sync Manager 2. Install ADB Fastboot 3. Unlock Bootloader 4. CWM Auto-Install via ADB Fastboot / Bootloader 5. ALL IN ONE SuperSU .zip file for Internal Storage (Includes Busybox, Init.d Installer, & Write Protection Removal)
Then i wanted to hide the over the air update by modifying the build.prop with root explorer->Jota Text Editor
(renamed it to build.prop.bak first)
I couldn't save it in /system with Jota so i moved it to the location (editing or savind with wrong permissions caused the loop)
rebooting started the bootloop, every 4 minutes it will start again.
i could enter recovery mode holding down and power for some minutes.
then adb and htc sync didn't detect my phone.
i tried using a file explorer [CWM-APP][1.91] AROMA Filemanager + TERMINAL :: 130903 :: Open Source
from http://forum.xda-developers.com/showthread.php?t=1646108 to rename the file, but the keyboard just hangs and produces garbage. Now my two build.prop files are named somewhat similar to jkdfh(ZG and $§BKGddddd, not build.prop and build.prop.bak
after barely closing the filemanager i am trying to get adb to work to change the filename for good
i boot in recovery and into hboot usb, connect the phone and try adb commands
i am now stuck, as none of the usb drivers i tried work.
i did a recovery->wipe data/factory reset and recovery ->wipe cache partition
i tried 15 sec adb drivers, i tried naked usb adb drivers, right now uninstalling every driver then reinstalling htc sync, reinstalling adb 15 sec 1.4.3 version of the drivers. Didn't find the ADB Driver entrys, so i searched and insalled universaladbdriversetup.msi, activated the "android adb interface" driver, have my phone in "fastboot usb mode", windows recognizes it, htc sync pops up but doesn't find a phone, adb still says device not found...
If i can't get the drivers to work, is there an option to not use usb to flash a stock rom from the sd (install zip)?
How do i decide what stock rom i need, how do i prepare it to be flashed as zip?
Please point me into the right direction.
I think I get it?
So I have a Droid 4.
I'm really bad at the jargon here, so if I may, I'll break it down and ask for explanations like I'm five.
My situation: I've been digging all over the internet for hours trying to figure out how to repair my broken build.prop file, which I edited in hopes of making the Droid 4 Compatible with Cricket Wireless. I am now stuck in Bootloop.
My options: I can easily get into the Android System Recovery menu.
@Kakmnesu: As I understand it, I need to:
1.) "update system from ADB" in the recovery menu.
2.) Run the ADB Command line.
3.) Enter "adb pull system/build.prop". This will, as it were, pull the file out so that it might be replaced.
4.) Have a backup copy of the clean build.prop on the external SD card.
5.) Enter "adb push system/build.prop". This will place the CLEAN build.prop from the SD card into the place of the old one and get rid of the old one completely.
What I don't know:
If my understanding of Item 5 is correct.
How can I tell if /system is mounted, and what do I do if it isn't?
What does setting the permissions do, and do I need to do that?
Any help is appreciated.
@sd_shadow, I've been trying to understand your posts and have been gathering what I think I might need should I have to overhaul the whole OS and start clean: I've noticed in your Droid 4 Repository that you have two files:
cdma_maserati_9.8.2o-72_vzw-18-2_1ff.xml
and
VRZ_XT894_9.8.2O-72_VZW-18.8_CFC.xml.
What is the difference between these, and do I need them both, should I need to just clean everything out?
Thanks so much for any of your help
ninthtale said:
So I have a Droid 4.
I'm really bad at the jargon here, so if I may, I'll break it down and ask for explanations like I'm five.
My situation: I've been digging all over the internet for hours trying to figure out how to repair my broken build.prop file, which I edited in hopes of making the Droid 4 Compatible with Cricket Wireless. I am now stuck in Bootloop.
My options: I can easily get into the Android System Recovery menu.
@Kakmnesu: As I understand it, I need to:
1.) "update system from ADB" in the recovery menu.
2.) Run the ADB Command line.
3.) Enter "adb pull system/build.prop". This will, as it were, pull the file out so that it might be replaced.
4.) Have a backup copy of the clean build.prop on the external SD card.
5.) Enter "adb push system/build.prop". This will place the CLEAN build.prop from the SD card into the place of the old one and get rid of the old one completely.
What I don't know:
If my understanding of Item 5 is correct.
How can I tell if /system is mounted, and what do I do if it isn't?
What does setting the permissions do, and do I need to do that?
Any help is appreciated.
@sd_shadow, I've been trying to understand your posts and have been gathering what I think I might need should I have to overhaul the whole OS and start clean: I've noticed in your Droid 4 Repository that you have two files:
cdma_maserati_9.8.2o-72_vzw-18-2_1ff.xml
and
VRZ_XT894_9.8.2O-72_VZW-18.8_CFC.xml.
What is the difference between these, and do I need them both, should I need to just clean everything out?
Thanks so much for any of your help
Click to expand...
Click to collapse
very little difference in the 2, only need one, either should be fine, but 18.8 is newer and should be better.
But you really should post in the Droid 4 section, and if you want reference this thread and/or mention Kakmnesu
the HTC Desire 816 and the Moto Droid 4 are very different devices, and the fixes may be very different.
---------- Post added at 01:02 PM ---------- Previous post was at 12:50 PM ----------
Cricket uses AT&T GMS network?
may need to see http://forum.xda-developers.com/showthread.php?p=25219819#post25219819
Got it. Thanks! I'll move to that thread because it still didn't work.. :\
After flashing CM-12, Both SIM are not working. Flashed stock L firmware but still problem is there... any solution?
Kakmnesu said:
[...]1. Don't use adb shell then adb pull/push, you don't need the shell here! Just use "adb pull /system/build.prop", notepad++ and "adb push build.prop /system/build.prop" to update the file, then set permissions again with "chmod 644 build.prop" and then "ls -l" to make sure the permissions of build.prop show -RW-R--R--
[...]
Click to expand...
Click to collapse
My issue was a bit like yours, only on my One M7. I screwed up the build.prop (replaced the ViperOne one with a Generic M7 one) and got stuck into a black screen after splash screen. The dreaded soft brick. I don't have ADB on my computer, but thankfully I had a copy of the original build.prop in my internal storage. However I couldn't get it to work after using TWRP to copy the file to /system/ multiple times.
I tried -everything- until a google search guided me to your post. The instructions in bold did the trick. You, sir, have saved me a lot of trouble