Related
So I took the plunge and have removed peep and learn more from the phone, all working well so far. don't want to push my luck and remove more.
How did you managed it? I'm guessing you have root access or something?
yes rooted and booted loads of bits i want to remove but not sure what effect they would have on the system.
adb shell rm /system/app/Learn*
adb shell rm /system/app/com.htc.Twitt*
I managed to remove learnmore and the Stocks app and its widget. No discernable bad effects. I used Root Explorer successfully to do this, thought I havent managed to get Root Explorer to Copy and paste either to or from the device (Yup I know its read only, but Root Explorer, when working correctly, allows you to toggle R/w and R/0 ).
Daisy xxx
Dayzee said:
I managed to remove learnmore and the Stocks app and its widget. No discernable bad effects. I used Root Explorer successfully to do this, thought I havent managed to get Root Explorer to Copy and paste either to or from the device (Yup I know its read only, but Root Explorer, when working correctly, allows you to toggle R/w and R/0 ).
Daisy xxx
Click to expand...
Click to collapse
Daisy! Quick question?? how did you manage to get root explorer to work. It seems to for-close on me all the time!
Dayzee said:
I havent managed to get Root Explorer to Copy and paste either to or from the device
Click to expand...
Click to collapse
It's now working here. I used the update.zip mentioned here to gain "adb remount" ability for an unrelated issue and a side-effect is that Root Explorer now copies/pastes as expected.
Maybe a little tutorial on how to uninstall apps ??
I remove "rosie" to get back old style android look : its blazing fast and all htc's applications still works.
I used the Update.zip from Pauls Method at MoDaCo (Should go in the wiki if Paul says its OK?) and then was able to copy from /data/app/ to my SD Card using Linda File Manager whilst in "adb remount" (link via usb, then use command prompt to get to the adb directory and type "adb remount" then use the Linda File manager to do the bizz.)
Haven't tried removing anything or putting anything in yet, cos I really don't know whayt I'm doing. I just want to know HOW it can be done really. :0)
Dayzee
minogue said:
Daisy! Quick question?? how did you manage to get root explorer to work. It seems to for-close on me all the time!
Click to expand...
Click to collapse
I don't get force closes, but it certainly doesn't work for me as it should. Pressing the buttons to change from R/W to R/O usually says Busy: cannot remount - also any "copy" seems to go ok but the "paste" never works.
I've got Root Explorer 1.4 I think. Also tried it with adb remount but it didn't seem to work either.
Daisy xx
NisseGurra said:
I remove "rosie" to get back old style android look : its blazing fast and all htc's applications still works.
Click to expand...
Click to collapse
I want to do this but worried I might get the "force close error" when opening the peoples application when using the standard android UI. Its happened a few times when I set Home as my default application, reverted back to Touchflo and it been working great.
Removing Rosie completely will also remove the black look that HTC put in the ROM? Or is that something that is fixed by theming? (Like the top bar being black on the Hero, but white on the Magic)
Edit:
Well I went ahead and gave Rosie the boot, allong with some other HTC widget stuff (which becomes obsolete when you remove Rosie) I used Root Explorer to delete the files (adb shell rm wouldn't work :-\)
All I need now is the default white bar at the top instead of the HTC Black one
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.
Ok I successfully unlocked ZVD (KitKat 4.4.2) and thought I should share my steps in case anyone else was having the same issues as me which was mostly the systemui and home processes crashing on a loop.
First insert the SIM card you would like to use in the LS980. Then download and flash the stock firmware LS980ZVC_12.zip with the LG Tool -> http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware
Download the ZVD update - > http://www.mediafire.com/download/s5dqwo1cbe68ckb/LS980ZVC_12-LS980ZVD_19_update.zip (Do not flash this OTA update from a rooted rom or custom recovery!)
After flashing ZVC, set the phone to charge only and enable USB debugging by becoming a developer. Go to About Phone->Software Information and keep clicking "Build number" until it says you are a developer. Then go back to the main settings and you will now see "Developer options" and can enable USB debugging in there.
After enabling USB debugging choose charge only and when the RSA Key fingerprint window pops up make sure you check "Always allow from this computer" and then click OK.
Next using the ADB tools, reboot into recovery mode to apply the ZVD update.
Code:
adb reboot recovery
Select "apply update from ADB" with the volume buttons then press the power button. Wait 5 seconds then enter the following command.
Code:
adb sideload path_to_file/LS980ZVC_12-LS980ZVD_19_update.zip
After the update finishes select "reboot system now".
Next turn on airplane mode and root the phone using IO Root -> http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869
Next install SuperSU and BusyBox. Make sure you open SuperSu to update the SU binary and open BusyBox and install the busybox files.
*OPTIONAL INSTALL TWRP*
Next use ADB to install AutoRec -> http://forum.xda-developers.com/showthread.php?t=2715496.
Code:
adb install path_to_file\LS980_AutoRec.apk
Open AutoRec and flash the new patched kernel and recovery and then reboot. If you get white lines after rebooting, read the warning the OP has posted for the fix. I suggest here you take the time to make a backup and copy the EFS to your computer just in case.
*knock code feature will no longer work
*flash this kernel to enable knock code again and much more - > http://forum.xda-developers.com/showthread.php?t=2725023
*OPTIONAL END*
Now using ADB again, enter the following commands.
Code:
adb pull /system/build.prop
adb shell
su
After entering "su" check your phone to grant SuperUser permission to ADB. Aftering granting su to ADB, exit adb shell.
Code:
exit
exit
Next using Total Commander and the files from here -> http://forum.xda-developers.com/showthread.php?t=2655133 copy all the contents of the "carrier" folder to your phones "/carrier/" directory and choose "overwrite all". I like to delete the "legal.db" first this way I know the copy was successful when I see the new file listed. Do not delete any other files before copying the files over since we want to keep the file and folder permissions and owners of the originals. If Total Commander fails to copy the files over to the phone then you can use a root explorer app to do so.
Now edit the build.prop that you pulled from the phone with a program like Notepad++ since it will save the file for use with linux and not windows. Do not edit the build.prop or copy it back to the phone with any apps on the phone, this is what was causing the crashes for me.
Change the following lines
Code:
ro.carrier=unknown
ro.build.target_operator=SPR
persist.service.crash.enable=0
ro.telephony.default_network=10
telephony.lteOnCdmaDevice=1
to
Code:
ro.carrier=spr
ro.build.target_operator=spr
persist.service.crash.enable=1
ro.telephony.default_network=0
telephony.lteOnCdmaDevice=0
*ro.carrier and ro.build.target_operator can bet set to "TMO", "ATT", or "spr".
*"TMO" and "ATT" do not correctly display the signal strength in the status bar.
Save the build.prop and use ADB to push it to the sdcard.
Code:
adb push build.prop /sdcard/
Now here is where we have to manually mount the system partition as RW and copy the build.prop over since all the root explorer apps seem to also cause the crashing issue.
Code:
adb shell
su
mount -o remount,rw /system
cp /sdcard/build.prop /system/
mount -o remount,ro /system
reboot
After the phone reboots it should be unlocked. Verify with Radio Switcher that your preferred network type is "WCDMA preferred", if not then change it to "WCDMA preferred". Now add your APN using Tweakker APN INTERNET MMS. If your APN doesn't stick, delete /data/data/com.android.providers.telephony/databases/telephony.db and reboot then add your APN again.
*To remove Bloatware add ".bak" to the following system applications names located in /system/app/ and /system/priv-app/ folders.
Activation.apk
OmaDmclient.apk
SPR_Skyfire_Observer.apk
SPR_Skyfire_Toolbar.apk
SprintExtensionProvider.apk
SprintID.apk
SprintTouch.apk
Vtt-Sprint.apk
xtra_t_app.apk
Zone-Sprint.apk
WIFIOffloader.apk
Click to expand...
Click to collapse
*To fix the issue of the com.android.phone process crashing when you don't dial a 1 in front of the number edit the /data/data/com.android.providers.settings/databases/settings.db file with a SQLlite editor and change in the "system" table "assist_dial" and "assist_dial_init_db_check" to "0". If you don't see those 2 rows then you can add them instead.
Code:
adb shell
su
cp /data/data/com.android.providers.settings/databases/settings.db /sdcard/settings.db
exit
exit
adb pull /sdcard/settings.db
sqlite3 settings.db
UPDATE system SET value='0' WHERE name='assist_dial';
UPDATE system SET value='0' WHERE name='assist_dial_init_db_check';
.exit
adb push settings.db /sdcard/
adb shell
su
cp /sdcard/settings.db /data/data/com.android.providers.settings/databases/settings.db
chown system:system /data/data/com.android.providers.settings/databases/settings.db
reboot
*To disable OTA updates and notifications rename the following files
/etc/security/otacerts.zip
/system/app/LGFOTA.apk
Click to expand...
Click to collapse
to
/etc/security/otacerts.zip.bak
/system/app/LGFOTA.apk.bak
Click to expand...
Click to collapse
*To replace the Sprint boot/shutdown animations and sounds with the LG default ones download these files -> https://www.mediafire.com/folder/cmb6jn7z7osmf/LG_G2_Boot_Animation
copy and overwrite the following files to /system/media/
bootanimation_sprint.zip
shutdownanimation_sprint.zip
Click to expand...
Click to collapse
copy and overwrite the following files to /system/media/audio/ui/
PowerOff_Sprint.ogg
PowerOn_Sprint.ogg
Click to expand...
Click to collapse
*LG G3 Theme for G2 -> https://play.google.com/store/apps/details?id=com.lge.launcher2.theme.rocketg3&hl=en
Thanks to all those people who contributed to this. :victory:
Thanks for the guide, working find for me and LS980, mms msg not working, propably i have error on APN settings, and signal bar min or max signal is 1 bar only....
MakisPgr said:
Thanks for the guide, working find for me and LS980, mms msg not working, propably i have error on APN settings, and signal bar min or max signal is 1 bar only....
Click to expand...
Click to collapse
Info and fix about the 1 signal bar bug is located in the guide above. Your mms issue is most likely a APN mistake. Make sure your data is working.
Sent from my LG-LS980 using XDA Premium 4 mobile app
This method worked on my ATT sim card I dont need to dial a 1 in front of #. but didnt work on my Lycamobile simcard and pageplus. still need to dial 1 infront of nuber.
thanks.
来自我的 LG-LS980 上的 Tapatalk
Can you attach a logcat of it crashing when you dial please
Sent from my LG-LS980 using XDA Premium 4 mobile app
jsergio123 said:
Info and fix about the 1 signal bar bug is located in the guide above. Your mms issue is most likely a APN mistake. Make sure your data is working.
Sent from my LG-LS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes you are right about 1 bar signal, didn't notice, and i fix my mistake settings on APN and mms now works perfectly ... Thank you very much
jsergio123 said:
Can you attach a logcat of it crashing when you dial please
Sent from my LG-LS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
sorry, I dont know where is it.
ahqiu said:
sorry, I dont know where is it.
Click to expand...
Click to collapse
adb logcat > logcat.txt
Sent from my LG-LS980 using XDA Premium 4 mobile app
Updated the OP for latest ZVD update from Sprint.
Added SQLite instructions.
Also confirmed working myself.
Updated the OP to include the files and instructions to replace the sprint boot/shutdown animations and sounds
Do you know if I would be able to install a custom rom after this? Also, I had the issue before with cloudys rom that would cause app force closing and restarts, should I expect the same this way?
Thanks a bunch
If you want to use a custom asop rom don't follow my guide instead just follow this guide after flashing your rom of choice.
http://forum.xda-developers.com/showthread.php?t=2827043
@jergio123
Do you think this would work to unlock additional bands on the Sprint LGG2 LS980 for T-Mobile USA?
http://forum.xda-developers.com/cro...ad-progress-please-leave-im-updating-t2871269
I guess the only way to find out would be to attempt it. I only quickly looked through the thread but good find.
Is there suppose to be a custom folder inside the carrier folder I copied over to root directory? After rebooting my device I've notice this custom folder that's not inside the original carrier folder I extracted ?
There should be a "cust" folder, I'm not sure if that is the folder you're referring to.
Will cloudys g3 ROM work with this unlock method?
I'm pretty sure cloudys rom is already unlocked and only requires you to change the radio with radio switcher and add your APN
Don't work
Hello, i can't unlock with this method. In the end, when i turn on the phone unlocked, the phone give me an error and always appear "com.android.phone".
I don't understand this part:
"Now edit the build.prop that you pulled from the phone with a program like Notepad++ since it will save the file for use with linux and not windows. Do not edit the build.prop or copy it back to the phone with any apps on the phone, this is what was causing the crashes for me."
I need edit "built.prop" or not? How?
I'm using the phone in Portugal (gsm carrier), i need to do this part?
Sorry but i really confused.
Thank you
Follow the guide step by step, I don't know how much clearer I can make it.
If you're getting process crashes then you must either restore the system partition from backup or start fresh by re-flashing with the LG tool.
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
Anybody knows how to enable third-party apps to access SD Card? Things that were working under 5.1 are not under 6.0 anymore.
Well, it seems Google is really retarded regarding SD Card access, changing API every other version:
http://stackoverflow.com/questions/32129716/how-does-storage-access-change-on-android-6
Radek Hulán said:
Anybody knows how to enable third-party apps to access SD Card? Things that were working under 5.1 are not under 6.0 anymore.
Click to expand...
Click to collapse
i used the old Kitkat fix for my brief period on 6.0, but i rolled back to 5.1 for the time being, battery drain was too much.. here
Well, not going to root my device to gain basic features such as being able to delete photos Camera app put on SD card.
This is insane.
(connect phone with USB debugging)
adb reboot bootloader
fastboot boot twrp.img
** TWRP: MOUNT > SYSTEM
** TWRP: Advanced > File > "chmod 775" on system/build.prop
adb pull /system/build.prop %USERPROFILE%
** EDIT FILE, set ro.lge.adoptable_storage=true
adb push %USERPROFILE%\build.prop /system/build.prop
adb shell
chmod 644 /system/build.prop
exit
adb reboot
Now you can format SD card as internal storage and use it for data
Thanks Radek for this!!!
Radek Hulán said:
(connect phone with USB debugging)
adb reboot bootloader
fastboot boot twrp.img
** TWRP: MOUNT > SYSTEM
** TWRP: Advanced > File > "chmod 775" on system/build.prop
adb pull /system/build.prop %USERPROFILE%
** EDIT FILE, set ro.lge.adoptable_storage=true
adb push %USERPROFILE%\build.prop /system/build.prop
adb shell
chmod 644 /system/build.prop
exit
adb reboot
Now you can format SD card as internal storage and use it for data
Click to expand...
Click to collapse
interesting. i see on some lines there are twrp. so this method can only be used with G4 variants that has twrp? CMIIW
i'd really like to try this on my H818P but there's no TWRP for the variant yet...
Good work mate
Requires root ?
It does not require root, but you must have unlocked bootloader.
Odesláno z mého LG-H815 pomocí Tapatalk
Radek Hulán said:
(connect phone with USB debugging)
adb reboot bootloader
fastboot boot twrp.img
** TWRP: MOUNT > SYSTEM
** TWRP: Advanced > File > "chmod 775" on system/build.prop
adb pull /system/build.prop %USERPROFILE%
** EDIT FILE, set ro.lge.adoptable_storage=true
adb push %USERPROFILE%\build.prop /system/build.prop
adb shell
chmod 644 /system/build.prop
exit
adb reboot
Now you can format SD card as internal storage and use it for data
Click to expand...
Click to collapse
can you explain me what do you mean with
* TWRP: MOUNT > SYSTEM
** TWRP: Advanced > File > "chmod 775" on system/build.prop
adb pull /system/build.prop %USERPROFILE%
** EDIT FILE, set ro.lge.adoptable_storage=true
i dont know it, thanks
Continue working this metod?
Sorry for me bad english xD
[email protected] said:
can you explain me what do you mean with
* TWRP: MOUNT > SYSTEM
** TWRP: Advanced > File > "chmod 775" on system/build.prop
adb pull /system/build.prop %USERPROFILE%
** EDIT FILE, set ro.lge.adoptable_storage=true
i dont know it, thanks
Click to expand...
Click to collapse
Download TWRP for LG G4, run it:
https://twrp.me/devices/lgg4h815.html
In TWRP, select Mount > System, from menu, and continue according to these instructions.
ADB is part of Android SDK tools:
http://developer.android.com/sdk/index.html#Other
I don't know if it is the same problem but I believe it is, so my problem is that I can transfer files from SD to internal but it doesn't work the other way around, I don't want to unlock my bootloader so is there anything else I can do? Thanks
any idea why the G4 is stuck at the Tmobile screen after:
Using the ES root browser and changing the file build.prop manually ( ro.lge.adoptable_storage=true), got the stuck tmobile starts creen
then running the adb commands as per the instructions, then also changing the permission using TWIRP
Nazdar Radku,
the solution is known feature of MM (adopt external storage), but biggest dissadvantage of this, is that you cannot use SD card in other devices anymore - not only in PC using some reader, but not even in other LG-ie your lg g4 broke....no way to get your data back. For some reason LG didnt include this functionality of MM yet. 2nd disadvantage is slowing down your device, as acces, R/W ops are quite slower. And I agree with googles approach to SD card - they want to "protect" users is foolish - you cannot protect stupid people, they should make it as default but keep option for advanced users to access storage as before KK for advanced user as it could be done with KK & LP using that media_rw grp hack.
coolmaster121 said:
any idea why the G4 is stuck at the Tmobile screen after:
Using the ES root browser and changing the file build.prop manually ( ro.lge.adoptable_storage=true), got the stuck tmobile starts creen
then running the adb commands as per the instructions, then also changing the permission using TWIRP
Click to expand...
Click to collapse
I don't think you should ever use a file browser to modify your build.prop. Something about the file being truncated. The modified build.prop ends up being a different size/structure or something along those lines. You should use a dedicated build.prop editor app, or adb commands only. If you had done that chances are you wouldn't have any problems.
IF you have a custom recovery you may be able to restore your original prop file through it in order to get it to boot.
rick09 said:
I don't think you should ever use a file browser to modify your build.prop. Something about the file being truncated. The modified build.prop ends up being a different size/structure or something along those lines. You should use a dedicated build.prop editor app, or adb commands only. If you had done that chances are you wouldn't have any problems.
IF you have a custom recovery you may be able to restore your original prop file through it in order to get it to boot.
Click to expand...
Click to collapse
I resolved the issue by basically booting back in to TWIRP, flashing the stock image again. (didnt loose any files as I didnt do a wipe)
Then ran through the commands from the previous post. But the "set" did not work for me. I then downloaded the build.prop file to the desktop using the "get" command and edited it with wordpad, saved and then sent over the edited file, followed the rest of the permissions and it worked fine then.
Good that you got it figured out but you did it the hard way! All you have to do is download https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
Make a backup in the app just in case, then find the entry, make your changes, and reboot. All done on your device.
rick09 said:
Good that you got it figured out but you did it the hard way! All you have to do is download https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
Make a backup in the app just in case, then find the entry, make your changes, and reboot. All done on your device.
Click to expand...
Click to collapse
Just tried, it, does not seem to work. it changes the value, says I need to restart, but after restart it goes back to false
Lg G4 SD card as internal storage
Can someone tell me a little more detail on this im new to this and trying to figure it out for myself what software do I need and how to do this to my 2 lg G4's