Related
I'm trying to remove the old facebook and twitter apps from my phone.
They're both stored in /system/app folder.
I've tried everything, Titanium Backup, Root Explorer and tried deleting them through adb they just do not go!
Has anyone got any ideas?
You can't remove them. Simples.
Well you can but you have to remove them from recovery using adb when connected to a PC. We don't have full root when the phone is in the OS and the system folder is read only. Recovery gives you write access but then you have to get in from a command prompt.
Look up the development package from HTC and how to use adb if it's that important. You gain nothing by removing those 2 apps btw other than you won't see them anymore.
sbdags said:
You can't remove them. Simples.
Well you can but you have to remove them from recovery using adb when connected to a PC. We don't have full root when the phone is in the OS and the system folder is read only. Recovery gives you write access but then you have to get in from a command prompt.
Look up the development package from HTC and how to use adb if it's that important. You gain nothing by removing those 2 apps btw other than you won't see them anymore.
Click to expand...
Click to collapse
It's just because they were in the /system/app folder so when i tried to download the updates for them they wouldn't install.
But I've got the new versions anyway now so it's all good.
Big props to SAINTH for his guide. Some of my guide is a word for word rip off of his guide. I just copied it and played around to get a simpler way to root. It is still temporary but now when you have "SU" you are messing with the ACTUAL files on the device, NOT a copy on your SD card. Also, programs installed in root mode are still on your device when not in root mode.
I wrote this entire post while tethered to my device using this method.
NOTE: IF SOMEONE COULD GIVE ME A RECOVERY TO FLASH, I THINK WE WOULD HAVE PERMANENT ROOT
OK, I am a dev noob... total noob... please no flaming...
Getting Started: (ONE TIME STUFF)
1) Partition your SD card with at least a 300mb EXT3 partition. I Used gparted in Ubuntu. (ubuntu.com ...download the iso, boot as a live cd, install gparted....google for more details)
2) Download and install from Market: Bar Control. I will explain why in a moment.
3) Download and extract visionroot.zip into your tools directory.
4) Use adb to install programs and transfer files to your device:
On the phone, enable "USB debugging" in Menu -> Settings -> Applications -> Development
On a computer with the Android SDK tools installed and working (adb is included with the SDK, so install the sdk and you will have adb. GOOGLE "adb sdk install" for more details):
adb push busybox /data/local
adb push rage /data/local
adb push root /data/local
adb push rsync /data/local
adb push su /data/local
adb install Term.apk
adb install Superuser.apk
adb shell chmod 755 /data/local/busybox /data/local/rage /data/local/rsync /data/local/root
5) Run Bar Control and select Terminal Emulator to run in the task bar. Early on, when I was playing around with this rooting method, temp root would just disappear. I found it stays if I use Bar Control. I think since Terminal Emulator is in the task bar, android is less likely to kill it. I did this whole post using tethering without root ever going away.
Ok. SETUP stage is now over. From this point on is how you will get root each time you boot up your phone.
Getting Root:
1) On the phone, open "Terminal Emulator" from the taskbar and type:
cd data
cd local
./rage
Wait for it to say "[+] Forked NNNN childs." then press the back button until you are back at the home screen. It will be slow for a bit.
2) Open "Terminal Emulator" again from the task bar and it should force close. It's ok if it doesn't. Just skip to #3.
3) Open "Terminal Emulator" one more time from the task bar and the prompt should display "#". This is the ROOT prompt! You are almost golden now! Then type:
cd data
cd local
./root
You may get some "Killall: Can't kill such and such" messages. Not a problem.
DO NOT hit the back button. You want terminal to keep running. Hit the Home Button.
YOU NOW HAVE ROOT! Superuser should be working too. We may find that we dont need bar control and terminal running. Let me know and I will change my post.
What I've Used Root For So Far
Some people are questioning the value of root without custom ROM's. Here is what i have used ROOT for on this ROM so far:
1) Wireless Tether - this alone is worth it! The 9-5 version from this page works amazingly on the G2:
http://code.google.com/p/android-wifi-tether/downloads/list?can=2&q=NexusOne
2) Uninstall Crapware - I used Titanium to uninstall Web2Go. What a pile of steamy poop. EDIT: The software MAGICALLY reappears after reboot. I can't wait to crack this phone!
3) Back up with Titanium - Most awesome backup program out there. Needs root to work.
good stuff bro ima try this.
this is all well and good, but the point of rooting is the custom roms, we've had a Temp root since day one, but no reason to root it.
yes but
Dalamak said:
this is all well and good, but the point of rooting is the custom roms, we've had a Temp root since day one, but no reason to root it.
Click to expand...
Click to collapse
Yes we did BUT that temp root method didn't allow access to the real files of the device. It accessed copies (simply put I know). This temp root gives ROOT access to the entire device which puts us a GIANT step closer to a permanent solution.
Also, the other temp method couldn't handle installing Apps in one mode and using them in another. Some Apps disappeared at reboot. With this method, Apps that are installed in either mode are always accessible.
Basically I did this for my own device and just wanted to share with others
But of course I thank you for your efforts, you are a god, I meant no disrespect
texasaggie1 said:
Big props to SAINTH for his guide. Some of my guide is a word for word rip off of his guide. I just copied it and played around to get a simpler way to root. It is still temporary but now when you have "SU" you are messing with the ACTUAL files on the device, NOT a copy on your SD card. Also, programs installed in root mode are still on your device when not in root mode.
I wrote this entire post while tethered to my device using this method.
NOTE: IF SOMEONE COULD GIVE ME A RECOVERY TO FLASH, I THINK WE WOULD HAVE PERMANENT ROOT
OK, I am a dev noob... total noob... please no flaming...
Getting Started: (ONE TIME STUFF)
1) Partition your SD card with at least a 300mb EXT3 partition. I Used gparted in Ubuntu.
2) Download and install from Market: Bar Control. I will explain why in a moment.
3) Download and extract visionroot.zip into your tools directory.
4) Use adb to install programs and transfer files to your device:
On the phone, enable "USB debugging" in Menu -> Settings -> Applications -> Development
On a computer with the Android SDK tools (adb) installed and working:
adb push busybox /data/local
adb push rage /data/local
adb push root /data/local
adb push rsync /data/local
adb push su /data/local
adb install Term.apk
adb install Superuser.apk
adb shell chmod 755 /data/local/busybox /data/local/rage /data/local/rsync /data/local/root
5) Run Bar Control and select Terminal Emulator to run in the task bar. Early on, when I was playing around with this rooting method, temp root would just disappear. I found it stays if I use Bar Control. I think since Terminal Emulator is in the task bar, android is less likely to kill it. I did this whole post using tethering without root ever going away.
Ok. SETUP stage is now over. From this point on is how you will get root each time you boot up your phone.
Getting Root:
1) On the phone, open "Terminal Emulator" from the taskbar and type:
cd data
cd local
./rage
Wait for it to say "[+] Forked NNNN childs." then press the back button until you are back at the home screen. It will be slow for a bit.
2) Open "Terminal Emulator" again from the task bar and it should force close. It's ok if it doesn't. Just skip to #3.
3) Open "Terminal Emulator" one more time from the task bar and the prompt should display "#". This is the ROOT prompt! You are almost golden now! Then type:
cd data
cd local
./root
You may get some "Killall: Can't kill such and such" messages. Not a problem.
DO NOT hit the back button. You want terminal to keep running. Hit the Home Button.
YOU NOW HAVE ROOT! Superuser should be working too. We may find that we dont need bar control and terminal running. Let me know and I will change my post.
Click to expand...
Click to collapse
Dalamak said:
But of course I thank you for your efforts, you are a god, I meant no disrespect
Click to expand...
Click to collapse
LOL hahahah thats funny. I'm def not a god at this
Good job man! This will definitely make it seemer on the folks who aren't Linux friendly or lazy folks like me. Oh and btw... you're the futherest thing from a newb! Hahahha! You've been here longer than me. Its rare that I see the real old school guys here anymore. Weren't you in the wizard or tornado sub forum many years ago. You seem familiar...
Oh btw, someone posted a clockwork recovery that was allegedly compatible with the G2 but I don't think anyone had the balls to flash it. Its in the root think tank thread...
Nevermind. I've decided to retract my comment and just try the process to see what happens.
Method worked amazingly well!
Thank you for this!!
Awesome job!
Sent from my T-Mobile G2 using XDA App
Will this work with the 4 click on-device root apk posted in this thread: http://forum.xda-developers.com/showpost.php?p=8535854&postcount=95 ?
Looks like a great guide as only 1 part is required - this allows me to part in my G1 AmonRa Recovery FTW!~111
(Also a great option if you are worried about booting up your G2 after formatting the SD as any progs looking for files there will be disappointed until you can copy them back ...)
Running a continuous Ping in Term now to see if that does the trick ...
EDIT:
Alright! this is awesome!
Q:
IF all we have to do to keep root is to keep the shell open - can't we run a prog or command to prioritize that prog ... like ... i remember that auto taskiller had settings against apps that were in the forgroud, background, background services etc ...
can we fool the OS into thinking this is allways a foreground process even though it's really running in BG ...or somehow give it highest priority?
EDIT 2:
Installed WirelesTeather.apk and ran and installed binaries - SU came up and granted all permission w/o issue - everything looked good.
Didn't open any other programs and decided to test it later, after noticing the AP didn't show I checked Terminal from the taskbar and it was back to $ (was closed by system)
I am running a fish aquarium for livewallpaper - so I'm sure this is why it closed as I'm running more processes at idle ... however, it looks like opening pretty much anything will cause the terminal to close and kill the "temp root'
Running a continuous Ping in Term now to see if that does the trick
FINAL EDIT:
OK! Ran continuous ping, opened Quake 3 - played for a bit - closed it.
Checked Term from the status bar - My Ping is still running !!1111 (IE the shell didn't close and we still have root)
So ... maybe this helps
You are the man. Downloaded. Tested. It works!
Sent from my T-Mobile G2 using XDA App
GREAT WORK!
Got it up and running, and just got 2.26 down, 1.23 up on my laptop off wireless tether.
so since this works directly with system files what happens if you try to metamorph something..will it revert on reboot or stay
Excellent job!
You are a genius! Your guide worked perfectly! I am typing this while tethered to the G2 - I agree with you, getting Root for tethering is worth the hassle of getting Root access! Keep up the great work!
I had been taking the SIM chip from my G2 to G1 (rooted, of course!) for Internet access - No more! Thanks again!
sino8r said:
...
Oh btw, someone posted a clockwork recovery that was allegedly compatible with the G2 but I don't think anyone had the balls to flash it. Its in the root think tank thread...
Click to expand...
Click to collapse
ive tried, several different ways, even ones that had a good chance of bricking, i.e. messing with ruu, and swapping files in the middle of flashing, just to try and get this perm root
texasaggie1 said:
Some people are questioning the value of root without custom ROM's. Here is what i have used ROOT for on this ROM so far:
1) Wireless Tether - this alone is worth it! The 9-5 version from this page works amazingly on the G2:
http://code.google.com/p/android-wifi-tether/downloads/list?can=2&q=NexusOne
2) Uninstall Crapware - I used Titanium to uninstall Web2Go. What a pile of steamy poop.
3) Back up with Titanium - Most awesome backup program out there. Needs root to work.
Click to expand...
Click to collapse
For Wireless Tether, I'm getting an error where it can't start access point. Anyone else have that problem? My computer won't recognize it without it.
EDIT:
Never mind, access point won't start if WiFi is on, and WiFi Tether isn't automatically shutting it off (like I think it's done on other phones), so if anyone else has the problem, turn off WiFi, then run WiFi Tether.
Which Version?
aacrabtree said:
For Wireless Tether, I'm getting an error where it can't start access point. Anyone else have that problem? My computer won't recognize it without it.
EDIT:
Never mind, access point won't start if WiFi is on, and WiFi Tether isn't automatically shutting it off (like I think it's done on other phones), so if anyone else has the problem, turn off WiFi, then run WiFi Tether.
Click to expand...
Click to collapse
Which tethering apk are you using? If you are using the one from the link I provided it should work. I am not having to turn off wifi first for it to work for me.
I am pretty new to this whole android market. I have a stock epic 4g running DI18 and 2.1 update 1, rooted with the one-clicked root available on the sticky note forum[forum.xda-developers.com/showthread.php?t=770388]. It installed superuser and Clockwork Recovery mod 2.5 and i have been able to access that with no problem, even did a system backup. i tried using the remount/unmount feature in this and it read that the filesystem was unmounted and mounted, but i could not figure out how that could operate with the root tools application, because i have to reboot the system and it still reads the same problems. I am not looking to change roms just yet because the SQL benchmark test scores are 49.4 seconds which seem to be enough for me. I am however trying to change the themes, boot animation, and move the cache to SD card. I have downloaded the SetCPU, titanium backup with the available BusyBox in help menu, and Root Tools by Jrummy16. The root tools application works to manage applications, but anytime i try to use any "tweaks or hacks" such as ad blocker, it does not allow it and shows me a screen reading, "unable to remount filesystem read/write." To fix this problem i downloaded android SDK on my windows 32 bit system, and downloaded all of the neccesary drivers. Most of the instructions tell you to access the Command Prompt on the computer and use:
cd\
cd androidsdk\tools
adb devices
The problem is.. once i get the file to read C:\androidSDK\tools, i try to enther adb devices and it reads to me that " 'adb' is not recognized as an internal or external command, operable program or batch file"
I am just trying to get my root tools to work so i can manage my cache and use the ad blocker, and possibly install new roms later. i also tried using the 'su' command and it said it was not recognized.
Few questions:
Is there any steps i missed to be able to develop and change my themes, or is there anything i should have used instead of the programs i used?
Is there a different way to access adb shell on the epic 4g?
Is there another way to change themes/fonts/widgets/scroll animations?
hookinhorns81 said:
I am pretty new to this whole android market. I have a stock epic 4g running DI18 and 2.1 update 1, rooted with the one-clicked root available on the sticky note forum[forum.xda-developers.com/showthread.php?t=770388]. It installed superuser and Clockwork Recovery mod 2.5 and i have been able to access that with no problem, even did a system backup. i tried using the remount/unmount feature in this and it read that the filesystem was unmounted and mounted, but i could not figure out how that could operate with the root tools application, because i have to reboot the system and it still reads the same problems. I am not looking to change roms just yet because the SQL benchmark test scores are 49.4 seconds which seem to be enough for me. I am however trying to change the themes, boot animation, and move the cache to SD card. I have downloaded the SetCPU, titanium backup with the available BusyBox in help menu, and Root Tools by Jrummy16. The root tools application works to manage applications, but anytime i try to use any "tweaks or hacks" such as ad blocker, it does not allow it and shows me a screen reading, "unable to remount filesystem read/write." To fix this problem i downloaded android SDK on my windows 32 bit system, and downloaded all of the neccesary drivers. Most of the instructions tell you to access the Command Prompt on the computer and use:
cd\
cd androidsdk\tools
adb devices
The problem is.. once i get the file to read C:\androidSDK\tools, i try to enther adb devices and it reads to me that " 'adb' is not recognized as an internal or external command, operable program or batch file"
I am just trying to get my root tools to work so i can manage my cache and use the ad blocker, and possibly install new roms later. i also tried using the 'su' command and it said it was not recognized.
Few questions:
Is there any steps i missed to be able to develop and change my themes, or is there anything i should have used instead of the programs i used?
Is there a different way to access adb shell on the epic 4g?
Is there another way to change themes/fonts/widgets/scroll animations?
Click to expand...
Click to collapse
I'm not sure if you had a typo in your original post or if that is how you actually entered the commands on your computer when you tried this, but based on the "paths" you entered, the commands should be:
CD\
CD\androidsdk\tools
adb devices
As for the themes, fonts, etc., there is an app in the market called MetaMorph that will do that for you. You just need to have .zips for it to apply.
There is also a tutorial for MetaMorph "somewhere" in the "Themes" section on XDA. I couldn't find a link to post for you, but I know it's there!
As far as getting in adb if you have windows XP you can go to the tools folder and hold shift and right click it. In the.menu it will say start command prompt here. Click it. Now you are on your tools folder where adb is. Then you can use adb and get into the shell.
Sent From My Evo Killer!
This is for n00bs like myself that had to search around before getting into this and doing it correctly. A lot was copied from the Inc S thread, but felt the instructions were needed here so no need for searching there and crowding their forum with our questions: http://forum.xda-developers.com/showthread.php?t=1039015
Psneuter exploit is working on DInc2, but because /system is locked on s-on phones, we can't copy su and superuser.apk into /system, apps required root access can't work.
The following procedure uses psenuter exploit to gain adb shell root, and then copy su (without privilege control ) and busybox into /sbin (which is on rootfs and in the global PATH list) to gain root access for apps.
The procedure:
1. Install the HTC Sync software or PDANet software to install drivers for your phone to Windows
2. Ensure that the device is in USB Debug mode, go to Settings > Applications > Development and "tick" USB debugging and plug in your phone to your PC
3. Unzip the attached .zip into a directory (like c:\adb)
4. Open a command prompt by going to start > run and running CMD, and cd to the directory where you extracted the .zip (like cd \adb)
5. Type "adb devices" > enter, and ensure that your device has been detected
6. Run the "pushroot.bat" file
7. Type "adb shell /data/local/tmp/getroot" > enter
8. Type "adb shell" > enter
9. You are now in # prompt. Type "/data/local/tmp/pushroot"
After the last step, a new # line appears. That's it! You're temporarily rooted
You have to redo steps 7, 8, 9 once you reboot your phone.
The procedure will have all apps gaining root access.
!!USE ON YOUR OWN RISK!!
Known working programs: Root explorer, Titanium backup, gscript lite, trasproxy 2.04, ...
Some apps check existence of su in /system/xbin , and reject to proceed if the su binary is not exist (like transproxy 3.08). For this kind of apps, this procedure won't help.
I run Bloat Freezer to rid the VZW apps
u can actually use the exact same process as the incS
I said that and linked to the Inc S thread for doing it
I just added in some steps for the issues I ran into, since it was my first time trying to do something like this and so others have a step by step to follow
And also so we have have something for this forum...thanks though
OK, question... if I do a temp root on the DInc2, then restore my wife's Titanium Backup to the new phone, can I also perminantly get rid of the VZW Bloatware, then reboot without Temp Rooting from that point on? (I know I will lose full Backups as well as SetCPU, etc. but will the Bloatware removal cause issues?)
I use Bloat Freeze and the VZW crap never comes back after a reboot when I have the "Alternate Freeze method" checked in the preferences, which is the Titanium Backup method
Maybe I am doing something wrong. I get to step #9 with
$ /data/local/tmp/pushroot and get
mount: operation not permitted
and a few more permission denied lines.
??? thanks in advance
Looks like the getroot did not work/run right, when you do step 8, the shell should start with the '#', not the '$'
Can somebody help me...after the last step, nothing happens. It just starts a new # line.
Posted from my Droid Incredible 2
Disregard. I got it. How can I effectively get rid of the bloatware? I moved a lot of it from system/app to my sdcard, but when I rebooted and lost root, it all reappeared.
Posted from my Droid Incredible 2
xgunther said:
Disregard. I got it. How can I effectively get rid of the bloatware? I moved a lot of it from system/app to my sdcard, but when I rebooted and lost root, it all reappeared.
Posted from my Droid Incredible 2
Click to expand...
Click to collapse
Use Titanium to freeze it. Don't delete it. Freezing works, but if you delete it it will just come back.
Sent from my ADR6350 using XDA App
I have done all the steps correctly up until step 5, well the problem is after typing in adb service, i get an extensively long list of different commands, and then the next step is to type in pushroot.bat, and when i do, heres what i get in return
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: dervice not found
C:\adb>
I dont know the problem...i do have Ongoing HTC Charge. USB Debugging connected. And PdaNet Connect (USB)
What could be the problem?
That should be adb devices, not serices
After that, you should see your device listed. When you typed services, the list you got was basically a help list for adb commands, since you did not type a valid one
Double check to make sure your device is detcted, if it is not, go to Windows' Device Manager and make sure the proper drivers were installed for your DInc
Ah, i appreciate the quick response i really do. I did type in adb devices, and what i got back was
List of devices attached
Afterwards, i did type in "pushroot.bat" and got a reply with again the same thing, error;device not found
In my window's device manager, i do have Android Phone, however the picture is only shown as a hard drive, which idk if that would have any affect. But yes, i didnt install any drivers from windows recommendations, like when i plug it in, the normal driver window pops up, but apart from that, i never did anything else except for the PDAnet 3.0 driver
Am i the only person who tries to delete apps and when the phone is restarted they come right back on.
mykenyc said:
Am i the only person who tries to delete apps and when the phone is restarted they come right back on.
Click to expand...
Click to collapse
You must "freeze" them with bloat freezer or a similar app.
xgunther said:
You must "freeze" them with bloat freezer or a similar app.
Click to expand...
Click to collapse
With only a temp root wouldn't any bloat freezing reset on reboot?
x Eacott said:
Ah, i appreciate the quick response i really do. I did type in adb devices, and what i got back was
List of devices attached
Afterwards, i did type in "pushroot.bat" and got a reply with again the same thing, error;device not found
In my window's device manager, i do have Android Phone, however the picture is only shown as a hard drive, which idk if that would have any affect. But yes, i didnt install any drivers from windows recommendations, like when i plug it in, the normal driver window pops up, but apart from that, i never did anything else except for the PDAnet 3.0 driver
Click to expand...
Click to collapse
Looks like your Dinc2 isn't being detected by your computer, watch you device manager when you plug in your phone and see what all is installed...sounds like that is the issue for you
sixteen2nd said:
With only a temp root wouldn't any bloat freezing reset on reboot?
Click to expand...
Click to collapse
Negative, Freezing works on the temp root after a reset, just make sure if you use Bloat Freeze that you select the alternative freezing option (Titanium Backup method) when you do it
LowFire82 said:
Looks like your Dinc2 isn't being detected by your computer, watch you device manager when you plug in your phone and see what all is installed...sounds like that is the issue for you
Click to expand...
Click to collapse
There are a lot of things that could prevent adb from picking up your device... easiest would be to double-check that you have the USB Debugging option enabled on the device. The next easiest would be to make sure you have the correct drivers installed. I'd recommend using an app like USBDeview to see an extended list of all your installed USB drivers, and then deleting anything related to HTC/Android/adb. You can then reinstall the correct drivers which I believe LowFire mentioned in his OP.
/threadjack
Ahh! OK, I had to do a Master Reset of my wife's Inc2, previously it had TempRoot working.
I followed the instructions from the beginning after it was reset, but I cannot get TempRoot access. MyBackup Pro, Titanium, Root Explorer all say there is no root access. I get the phone listed at adb devices and get no errors running the commands. Anyone have issues gaining root?
xgunther said:
Can somebody help me...after the last step, nothing happens. It just starts a new # line.
Posted from my Droid Incredible 2
Click to expand...
Click to collapse
I have the same issue...just another # line after typing in the string from step 9 and hitting enter
What did you do?
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