Related
Hey guys,
well this is my first post, and it's a help post! Normally i wanted to introduce myself because I want to start hacking / developing android apps etc. ... so I first had to get in touch with adb and so (I am no unix / programming newbie, study Media Informatics (BSc. 7th. semester).
So here is the problem...
The thing I was testing is how does the Android react with editing hosts and ads... Well I knew already that my Desire has no option to enter the system area! (And yes, I bought lots of apps, Launcher PRO, root explorer, SetCPU (even I knew I could get this here before), Beautiful Widgets and some more, etc. because I know what kinda work is behind all that Apps...
So I checked if my phone is connected in Recovery Mode, Developercheck in system done... Want to edit hosts files manually, so I had to create a symlink and save that host files elsewhere... so lets go...
adb devices -> wee here it is! lets go!
opend that adb shell and went on...
adb#mount /sdcard
adb#mount /system
adb#cp /system/etc
adb#cp hosts /sdcard/etc/hosts
adb#rm -r hosts
adb#ln -s /sdcard/etc/hosts hosts
adb#exit
adb reboot
All fine ... was waiting for the reboot... saw the htc logo, got a vibra check... and well, this is since then the problem... I see the htc logo, get the vibra check, and whoops, reboot!
If I go into the boot loader menu, it takes a while and then I see for a short time some lines which say sth. like "wrong image" or "image not found" ... dno how to pause, the clockwork error log doesnt help here much!
So... WHAT can I do to get my Desire back working?!
Aw, maybe usefull information... got a O2 Desire (Germany) and working atm on x64 Win7 machine...
=(
Greetings from germany
ctb
PS: At least I take it with some humor, even if I have no other mobile to use!
Oh and maybe that will help ...
factory reset doesnt work!
cache wipe didnt help
wiping davik also not...
Any ideas? (Loading atm the original RUU and will try that!)
Or is the last hope the next O2 Shop? *grin*
creativeby said:
Hey guys,
well this is my first post, and it's a help post! Normally i wanted to introduce myself because I want to start hacking / developing android apps etc. ... so I first had to get in touch with adb and so (I am no unix / programming newbie, study Media Informatics (BSc. 7th. semester).
So here is the problem...
The thing I was testing is how does the Android react with editing hosts and ads... Well I knew already that my Desire has no option to enter the system area! (And yes, I bought lots of apps, Launcher PRO, root explorer, SetCPU (even I knew I could get this here before), Beautiful Widgets and some more, etc. because I know what kinda work is behind all that Apps...
So I checked if my phone is connected in Recovery Mode, Developercheck in system done... Want to edit hosts files manually, so I had to create a symlink and save that host files elsewhere... so lets go...
adb devices -> wee here it is! lets go!
opend that adb shell and went on...
adb#mount /sdcard
adb#mount /system
adb#cp /system/etc
adb#cp hosts /sdcard/etc/hosts
adb#rm -r hosts
adb#ln -s /sdcard/etc/hosts hosts
adb#exit
adb reboot
All fine ... was waiting for the reboot... saw the htc logo, got a vibra check... and well, this is since then the problem... I see the htc logo, get the vibra check, and whoops, reboot!
If I go into the boot loader menu, it takes a while and then I see for a short time some lines which say sth. like "wrong image" or "image not found" ... dno how to pause, the clockwork error log doesnt help here much!
So... WHAT can I do to get my Desire back working?!
Aw, maybe usefull information... got a O2 Desire (Germany) and working atm on x64 Win7 machine...
=(
Greetings from germany
ctb
PS: At least I take it with some humor, even if I have no other mobile to use!
Click to expand...
Click to collapse
you should of done a nandroid in recovery first you could always try a hard reset, you could try removing the symlink too, im not sure if you should symlink to the sd card like that, maybe you should of used /data/ect/hosts or something like that.
*edit* sorry i didnt see you tried a hard reset an ruu will defo work, but its a bit extreme, your rooted arnt you? just flash the same rom from recovery
So you can access recovery? Just flash a new rom. Because you messed with /system a factory reset won't fix it. Or do a nandroid if you have one.
Hehe thanks for the replies!
Well, the idead of that nandroid backup came up in the second i rebooted... was to late! *giggle*
Okay so I have to learn how to flash a new rom... lets get it on! Hehehe!!!
Any recommendations for good roms?!
saw that coming!
creativeby said:
Hehe thanks for the replies!
Well, the idead of that nandroid backup came up in the second i rebooted... was to late! *giggle*
Okay so I have to learn how to flash a new rom... lets get it on! Hehehe!!!
Any recommendations for good roms?!
saw that coming!
Click to expand...
Click to collapse
theres only 2 worth having, auraxtsence for bling, and leedroid for stability
Weeeeeeeeeee it works again!!
Wow thank you so much for your help guys!
btw: leedroid rocks!
Hey guys,
I was using Sandvolds ICS for some weeks, but since yesterday my phone won't work anymore. I was starting a bike tour, but GPS on Endomondo didn't really work. So I restarted my phone. When I boot it'll show the white screen with green HTC logo, then it'll show the Evervolv animation and this animation will be displayed until I remove the battery, one time I had it running for half an hour.
I tried to boot the phone without sd card and could boot, but after "optimising" apps it kept on crashing because, as it appears, the system data is partly on the sd card.
Now I don't know what to do, what would you recommend? I'd probably just wipe everything and reinstall a backup, but - I don't have a backup
wipe everythin and reflash another rom/same rom...............
2012katas said:
wipe everythin and reflash another rom/same rom...............
Click to expand...
Click to collapse
i guess that'll work, but could anyone recommend another, more time-saving possibility?
greets to india!
Tourist06 said:
Hey guys,
I was using Sandvolds ICS for some weeks, but since yesterday my phone won't work anymore. I was starting a bike tour, but GPS on Endomondo didn't really work. So I restarted my phone. When I boot it'll show the white screen with green HTC logo, then it'll show the Evervolv animation and this animation will be displayed until I remove the battery, one time I had it running for half an hour.
I tried to boot the phone without sd card and could boot, but after "optimising" apps it kept on crashing because, as it appears, the system data is partly on the sd card.
Now I don't know what to do, what would you recommend? I'd probably just wipe everything and reinstall a backup, but - I don't have a backup
Click to expand...
Click to collapse
I got the same situation with you dude!!
I'm now using beta 0.17.1, but after this afternoon everything was wrong.
Then I did a full wipe and installed the latest version of Sandvolds ICS,
It's good and normal before I activate a2sd, but after that
everything went wrong again.
And finally I tried HTC DESIRE-AOKP-milestone6 v2,
It is working normally with INT2EXT, but not very smooth and stable.
actually i don't know what's going on right now :crying:
UserMatty said:
I got the same situation with you dude!!
I'm now using beta 0.17.1, but after this afternoon everything was wrong.
Then I did a full wipe and installed the latest version of Sandvolds ICS,
It's good and normal before I activate a2sd, but after that
everything went wrong again.
And finally I tried HTC DESIRE-AOKP-milestone6 v2,
It is working normally with INT2EXT, but not very smooth and stable.
actually i don't know what's going on right now :crying:
Click to expand...
Click to collapse
hi everybody..i've got the same problem..everything was ok until yesterday with the latest release of the sandvold ics rom..when my phone shutted down for low battery,i put it on charge..after that,i booted it up,and it still remain on the evervolv logo...so i tried to wipe cache,wipe partition,factory reset and format and repartition the sd card..reinstall the rom..and eveything was ok the first time..after that,i enabled the a2sd,and it strucked another time..so i did everything again from the beginning,but this time i enabled the a2sd without any problem..so i started to download from the market all the stuff that i needed,and everything was fine..so i rebooted the phone..and here we go again..strucked!but the worst thing is that without the sd,the phone boot without any problem!now..i bought the sd a week ago..it's a new one..i don't think that it's an sd problem..or also the first times it won't be able to boot up and everything..also i would't be able to install the rom!..so..any suggestion?
Cesk87 said:
hi everybody..i've got the same problem..everything was ok until yesterday with the latest release of the sandvold ics rom..when my phone shutted down for low battery,i put it on charge..after that,i booted it up,and it still remain on the evervolv logo...so i tried to wipe cache,wipe partition,factory reset and format and repartition the sd card..reinstall the rom..and eveything was ok the first time..after that,i enabled the a2sd,and it strucked another time..so i did everything again from the beginning,but this time i enabled the a2sd without any problem..so i started to download from the market all the stuff that i needed,and everything was fine..so i rebooted the phone..and here we go again..strucked!but the worst thing is that without the sd,the phone boot without any problem!now..i bought the sd a week ago..it's a new one..i don't think that it's an sd problem..or also the first times it won't be able to boot up and everything..also i would't be able to install the rom!..so..any suggestion?
Click to expand...
Click to collapse
maybe you can temporarily try DESIRE-AOKP-milestone6 v2
it's also a good choice! and a good rom also.
Hey,
I have the same problem! I also have Sandvolds ICS rom and it gets stuck on the Evervolv loading screen.
It loads up flawlessly without my SD card but then all my stuff is gone.
Any way to backup my data? (EDIT: Nevermind that question, I used backup from recovery)
BTW, SD card works, I can mount it from recovery mode.
Guys, what you say doesn't make me happy!
Maybe it's worth mentioning that I was NOT using the latest version of ICS, but I had no problems for weeks. I'm already waiting for the new Nexus phones, one of them will save me a lot of time and trouble updating to the newest OS and software
Good luck everyone, and please tell us if you manage making your phone working again
tried updating to latest ics via 4ext - fail! i could watch the evervolv animation for hours
Possible Solution
Looking in the Sandvold's thread a lot of people have been claiming that the bootloops is caused by the most recent version of Google Play 3.9.16. Apparently just deleting that will let you boot fine.
AceShinobi said:
Looking in the Sandvold's thread a lot of people have been claiming that the bootloops is caused by the most recent version of Google Play 3.9.16. Apparently just deleting that will let you boot fine.
Click to expand...
Click to collapse
The solution is here: http://forum.xda-developers.com/showthread.php?t=1944766
For me didn't work, but I want to try again and apply the solution directly on the first boot.
AceShinobi said:
Looking in the Sandvold's thread a lot of people have been claiming that the bootloops is caused by the most recent version of Google Play 3.9.16. Apparently just deleting that will let you boot fine.
Click to expand...
Click to collapse
Thanks for your hint, but after a few steps, I was stuck. After downloading the SDK (not mentioned in the tutorial) I experienced problems in the following steps, here is where I had problems
- cd Program Files(x86)/Android/android-sdk/platform-tools/ - I had to enter cd AppData\Local\Android/android-sdk/platform-tools/
- adb shell - command didn't work - I entered adb resulting in lots of text on my screen
- cd /data/data/ - the shell didn't accept this
Tourist06 said:
- cd /data/data/ - the shell didn't accept this
Click to expand...
Click to collapse
Probably because there is no folder /data/data? Have you followed the instructions in this thread? That should work.
Tourist06 said:
Thanks for your hint, but after a few steps, I was stuck. After downloading the SDK (not mentioned in the tutorial) I experienced problems in the following steps, here is where I had problems
- cd Program Files(x86)/Android/android-sdk/platform-tools/ - I had to enter cd AppData\Local\Android/android-sdk/platform-tools/
- adb shell - command didn't work - I entered adb resulting in lots of text on my screen
- cd /data/data/ - the shell didn't accept this
Click to expand...
Click to collapse
Seems like an adb fault.
If you type: adb get-state and adb get-serialno you have in output the infos of your Desire?
freakymonkey said:
Seems like an adb fault.
If you type: adb get-state and adb get-serialno you have in output the infos of your Desire?
Click to expand...
Click to collapse
adb shell will return device not found, adb get-serialno and adb-get-state return unknown
Using 4ext, I mounted system and sd-card
I also tried dietwice's tip (http://forum.xda-developers.com/showpost.php?p=33073702&postcount=8), but at step 3, cd /system/app , it says path not found. I'm no guru, so I don't really know what to do now.
Sorry about the fonts, it's a mess^^
Tourist06 said:
[...] I mounted system and sd-card [...]
Click to expand...
Click to collapse
You need to mount "system" and "USB storage". You have to be connected to your computer.
gartenriese said:
You need to mount "system" and "USB storage". You have to be connected to your computer.
Click to expand...
Click to collapse
Exactly, you have to mount more or less everything, depends on what kind of a2sd you have.
In my case, I had to mount everything because of "standard app2sd"; my "vending" are in /system, /data and /sdext.
Just to be sure, you have to undestand if the phone is connected to the computer. To check this try to write:
...../platform-tools/adb kill-server (press enter)
...../platform-tools/adb start-server (press enter)
NOW plugin your HTC Desire (in Recovery mode) to the computer and digit:
...../platform-tools/adb devices
Should appear at least your Deside (on the right side of the phone code will appear the word"recovery")
If this appear, you can prooced with "adb shell" or all other commands required for the procedure.
I had the same bootloop problem, it was easy to remove all the Play Store files.
Hope helping you.
Mat
Tourist06 said:
adb shell will return device not found, adb get-serialno and adb-get-state return unknown
Using 4ext, I mounted system and sd-card
I also tried dietwice's tip (http://forum.xda-developers.com/showpost.php?p=33073702&postcount=8), but at step 3, cd /system/app , it says path not found. I'm no guru, so I don't really know what to do now.
Sorry about the fonts, it's a mess^^
Click to expand...
Click to collapse
gartenriese said:
You need to mount "system" and "USB storage". You have to be connected to your computer.
Click to expand...
Click to collapse
I think that Tourist06 can't resolve with mounting /system or something else, because he has a problem with adb (adb don't talks with his device).
Have you followed this guide for installing adb?
@freakymonkey: I followed the guide, seemed to work! If I enter the shell I no more need to enter the whole path, entering "adb" will produce text. Please have a look at the following screenshot, hope you can confirm this.
@matteo.rex, no success, here's a screenshot
A pop-up appeared saying there were unidentified devices.
Thanks for your help, guys! My phone isn't working for the sixth day now
Tourist06 said:
A pop-up appeared saying there were unidentified devices.
Click to expand...
Click to collapse
Uhm, this is the problem maybe.
First question: is the phone charging when you plugin it to the pc? (I had a problem with the cable...solved changing it)
Second: could be not an ADB installation problem, but a Driver Installation problem. Check this thread to download it: http://forum.xda-developers.com/showthread.php?t=654047
If typing "ADB" a list of command appear, this mean that it work.
Windows, after the driver installation, have to recognize you Desire also during Recovery, not only during common use.
I hope it could help you!
Let us know!
p.s. I use ADB over Ubuntu, but the work is the same.
I messed up my build.prop and now my tablet (10.1) won't boot. Is there any way to fix build.prop in download or recovery mode?
Using the "apply update from ADB" option in recovery doesn't seem to permit normal adb commands like pull and push.
greenmaze said:
I messed up my build.prop and now my tablet (10.1) won't boot. Is there any way to fix build.prop in download or recovery mode?
Using the "apply update from ADB" option in recovery doesn't seem to permit normal adb commands like pull and push.
Click to expand...
Click to collapse
first you need same build.prop from same device. ask your friend use xda.
ask them to give you build.prop
after getting build.prop
use adb delete your first build.prop
and then push your build.prop(which you got from your friend)
to /system/
just press me thank if i helped you
greenmaze said:
I messed up my build.prop and now my tablet (10.1) won't boot. Is there any way to fix build.prop in download or recovery mode?
Using the "apply update from ADB" option in recovery doesn't seem to permit normal adb commands like pull and push.
Click to expand...
Click to collapse
Whenever you mess up with system files like build.prop, a backup of that file is automatically created in the same location with .bak extension. So if you want you can use aroma file manager to find that file and rename it to build.prop, set permissions and that's it !
Thanks for the help. The problem is that I can't get any adb commands to work (i.e. push or pull) in recovery mode. The devices command lists the tablet with the name "sideload". Am I doing something wrong?
Sent from my Nexus 5 using Tapatalk
To elaborate a little more, whenever I try an adb command I get the following message:
Code:
error: closed
Is there another way to get the tablet into a mode where it will accept adb commands?
AbhiLP said:
... So if you want you can use aroma file manager to find that file and rename it to build.prop, set permissions and that's it !
Click to expand...
Click to collapse
I wasn't sure what Aroma Filemanager was so I looked it up. Unfortunantly I'm unable to get Aroma Filemanager to work. I downloaded the zip to a SD card, booted into recovery, selected "apply update from ADB" and then selected the Aroma zip file. Some messages scroll on the screen and then tablet reboots. If I try sideloading the Aroma zip I get this output:
Code:
Finding update package...
Opening update package...
Verifying update package...
E: footer is wrong
E: signature verification failed
Finding update package...
Opening update package...
Verifying update package...
E: footer is wrong
E: signature verification failed
Installation aborted.
Fixed it
I finally fixed my problem. I pieced together information from various posts to get me there. In case someone else runs into a similar issue, here's what I had to do:
Install TWRP via Odin. You won't find a TWRP for 10.1 WiFi model (SM-T520) on the TWRP website. I found a link in another thread for TWRP that works: http://goo.im/devs/OpenRecovery/picassowifi
Boot into recovery and copy /system/build.prop to an SD card.
Fix* the build.prop issue on a PC (or anything else than can edit the file on the SD card)
Back in TWRP, copy the build.prop file from the SD card over the /system/build.prop file.
* I'm not even sure my build.prop file was messed up. I performed the steps above and still the tablet wouldn't boot. Remembering that I had changed the permissions on the build.prop file (back when my tablet was still working), I went back into TWRP and changed the build.prop file permissions back to 744. After rebooting my tablet powered up normally. So after all of this it might have just been that the file permissions on build.prop were wrong -- I'm surprised this would prevent the tablet from booting... but what do I know.
greenmaze said:
I finally fixed my problem. I pieced together information from various posts to get me there. In case someone else runs into a similar issue, here's what I had to do:
Install TWRP via Odin. You won't find a TWRP for 10.1 WiFi model (SM-T520) on the TWRP website. I found a link in another thread for TWRP that works: http://goo.im/devs/OpenRecovery/picassowifi
Boot into recovery and copy /system/build.prop to an SD card.
Fix* the build.prop issue on a PC (or anything else than can edit the file on the SD card)
Back in TWRP, copy the build.prop file from the SD card over the /system/build.prop file.
* I'm not even sure my build.prop file was messed up. I performed the steps above and still the tablet wouldn't boot. Remembering that I had changed the permissions on the build.prop file (back when my tablet was still working), I went back into TWRP and changed the build.prop file permissions back to 744. After rebooting my tablet powered up normally. So after all of this it might have just been that the file permissions on build.prop were wrong -- I'm surprised this would prevent the tablet from booting... but what do I know.
Click to expand...
Click to collapse
Can't access SD here, when mounting in CWM it mounts as a CD Rom and can't access it, never seen this...
I always recommend to flash the whole rom using odin if you don't have a custom recovery
greenmaze said:
* I'm not even sure my build.prop file was messed up. I performed the steps above and still the tablet wouldn't boot. Remembering that I had changed the permissions on the build.prop file (back when my tablet was still working), I went back into TWRP and changed the build.prop file permissions back to 744. After rebooting my tablet powered up normally. So after all of this it might have just been that the file permissions on build.prop were wrong -- I'm surprised this would prevent the tablet from booting... but what do I know.
Click to expand...
Click to collapse
Thanks for posting your solution(s) when you found them! I had done some manual editing on my build.prop after copying it to my computer and after replacing it on the device I forgot to reset the permissions. Luckily I came across your thread.
Thanks again for posting your solution!
Second thanks for sharing your solution too Greenmaze! My HTC M8 booted to a blank non-responsive screen after modifying the build.prop file. I found out how to go back into recovery mode from another thread below and then fix the build.prop permission from this thread.
http://forum.xda-developers.com/htc...ter-download-mode-t2853100/page2#post62490577
Basically, I had find a way to get into recovery mode by holding down the power button and volume up button at the blank screen and then exactly after 10 seconds, switch from pressing the volume up to volume down button before the HTC logo white screen shows while still holding down the power button. Then I use TWRP to chmod the sytem/build.prop permission to 0744 to fix the original boot issue.
T-Ching said:
Second thanks for sharing your solution too Greenmaze! My HTC M8 booted to a blank non-responsive screen after modifying the build.prop file. I found out how to go back into recovery mode from another thread below and then fix the build.prop permission from this thread.
http://forum.xda-developers.com/htc...ter-download-mode-t2853100/page2#post62490577
Basically, I had find a way to get into recovery mode by holding down the power button and volume up button at the blank screen and then exactly after 10 seconds, switch from pressing the volume up to volume down button before the HTC logo white screen shows while still holding down the power button. Then I use TWRP to chmod the sytem/build.prop permission to 0744 to fix the original boot issue.
Click to expand...
Click to collapse
Oh ok, so your HTC is a Samsung Galaxy Tab Pro. Really interested on how you managed that....
Sent from my MB860 using XDA Free mobile app
Build.prop permission boot problem is a generic android issue.
Build.prop permission boot problem is a generic android issue. I added how to go back into recovery specifically for HTC M8 since that was another hard to find solution also in order to fix the build.prop issue. Just being helpful since this solution worked for my M8 and I found it on this Samsung device thread and the other solution on a M8 thread. Don't want people to just get half the fix.
LG Pro Lite D680
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Boot On Charge
Non-generic feature for commercial purposes
URGENT NEED! - WILL DONATE
What we need:
I am looking for an urgent solution to boot-on-charge LG D680 cell phone, I am asking for help to developers who have experience on this area. The subject is related to unlock the bootlaoder, fastboot and custom rom. I understand the task is not simple, I am looking forward to donate whoever hacks the non generic feature.
What we do:
We provide video service through LG D680 cell phone (Also known as LG Pro Lite D680), the phone has 3G connection and is plugged to the power supply when is working.
Problem:
Most of the day the phone is plugged and working properly, however when the weekend comes the cell phone is unplugged and the energy is completely consumed. Currently, when the power is back to the cell phone we need to start the cell phone MANUALLY by pressing the power on button.
Goal:
We need the phone to be booted into the OS automatically when is plugged into the power USB cable (the phone initial status is powered off).
Possible Solutions / Alternatives:
Unlock the bootloader and run fastboot command fastboot oem off-mode-charge 0.
Continue our research, based on the steps described below (see LG D680 experience)
Replace charge animation with boot file command /system/bin/reboot (see Huawei experience below replacing ipod file).
Finding a custom ROM that already contains a Boot on Charge behaviour.
Finding a custom ROM that at least has “Power On Schedule” feature (AOSP certificate permissions level).
Finding a generic Android vestion with “Power On Schedule”.
Cellphone specifications:
PLATFORM
OS - Android OS, v4.1.2 (Jelly Bean), upgradаble to v4.4.2 (KitKat)
Chipset - Mediatek MT6577
CPU - Dual-core 1 GHz Cortex-A9
GPU - PowerVR SGX531
Previous work and research:
We did this "boot on charge" research in two types of cell phones. One is HUAWEI G730 and the other is LG D680. Fortunately, it worked fine in G730, but we haven’t the same results up to now on LG D680.
In Huawei G730, we replaced charging animation located at /system/bin/ipod with an ipod file containing “/system/bin/reboot” and worked like charm!
LG D680, we could not find the animation file, but we found that it might be inside the boot image. We did some research in order to modify it, but we got blocked (someone might continue our steps if useful).
HUAWEI G730 Extended Procedure:
Since this phone has a Mediatek chipset, the “battery animation” app is running on /system/bin folder. Is running with the filename ipod. The main task is to exchange ipod content (which is originally binary) to an ipod file with this content: /system/bin/reboot.
So, create a brand new file called ipod, and wrote the line in there. We transferred the file to the phone via adb push, as shown in next steps below.
Copy procedure: So, we set our phone to USB Debugging Mode, then we connected it to the PC, and run the following script:
adb shell mkdir /storage/sdcard0/carga/ (We created a folder to store files being pushed from the PC to the phone)
adb push ipod /storage/sdcard0/carga/ (We are pushing the file to the storage folder within the phone)
adb shell "su -c 'mount -o rw,remount -t ext4 /dev/block/mmcblk0p5 /system'" (This step is very important, here we remount the /system folder with read-write permissions. Only doing this we will be able to copy programmatically the “hacked” file ipod to /system/app. Look out that we used mmcblk0p5 because the system folder is mapped there in this phone. You can check this running cat /proc/dumchar_info)
adb shell "su -c 'chattr -i /system/bin/ipod'" (doing this we took out immutability to the original file ipod)
adb shell "su -c 'cp /system/bin/ipod /storage/sdcard0/carga/ipod.old'" (just creating a backup file from the original ipod)
adb shell "su -c 'rm /system/bin/ipod'" (here we are removing original ipod file)
adb shell "su -c 'cp /storage/sdcard0/carga/ipod /system/bin/'" (now we copy the new file ipod to the destination folder)
adb shell "su -c 'chmod 755 /system/bin/ipod'" (change the permission ro rwx-rx-rx)
adb shell "su -c 'mount -o ro,remount -t ext4 /dev/block/mmcblk0p5 /system'" (we remount the /system folder with read-only permissions)
adb shell "su -c 'reboot'" (Finally we reboot the phone)
RESULT: Whenever you plug in the phone to the charger when it is off, it will try to boot on the battery animation, but instead, it will be redirected to a “reboot” command, which in turn will be redirecting execution to the O.S.
LG D680 Procedure:
We found that this phone also has a Mediatek chipset. Moreover, it also has a file called ipod within /system/bin. But in this case, the bootloader image doesn’t call ipod whenever it displays the battery animation. So we had to check where is mapped the boot image on the phone by executing adb shell "cat /proc/dumchar_info". As the picture shows, the boot image (bootimg) is mapped in /dev/block/mmcblk0, from offset 0x1200000, and with size 0x900000.
We tried the following steps, in order to test if we were able to download / upload booting without bricking the phone:
We copy bootimg partition to boot.img by doing adb shell "su -c dd if=/dev/block/mmcblk0 of=/storage/sdcard0/boot.img bs=1024 skip=18432 count=9216’. (Skip and Count are measured on KBytes, and those values are offset and size translated from hexa to dec).
Then we did the inverse operation by executing: adb shell "su -c dd if=/storage/sdcard0/boot.img of=/dev/block/mmcblk0 bs=1024 seek=18432”
RESULT: The phone WASN’T bricked, and reboot normally (obviously without any change on bootimg).
Because these steps worked, we went even further, this time by unpacking and repacking boot.img file. The steps done were:
Same as (b)
We pulled boot.img file from the phone to a folder within the PC, and then we unpacked the image with bootimg.exe as the picture shows below. One interesting fact is that the pulled file sized almost 9MB.
Then we repacked it without any change inside the image, as the picture shows below. The “repacked” image is now on file “boot-new.img”, but its size is almost 7.4MB. We don’t know why we have this difference.
Same as step (ii) on (b).
RESULT: The phone resulted in a SECURITY_ERROR. It is weird because we didn’t change anything. We didn’t tried further since we are not able to unpack-repack the same image, and loading it successfully.
Edited: The security error can be avoided please follow the just below instructions.
Avoid Security Error:
In order to avoid the security error above mentioned, you need to edit the default.prop file (located at /bootimg/initrd)
Change the value from 1 to 0.
FastBoot Note LG:
Fastboot is a solution performing these commands, the problem is that the bootloader is locked for these operations on the generic vesion:
fastboot oem unlock
fastboot oem off-mode-charge 0
fastboot oem lock
fastboot reboot
The command "adb reboot bootloader" does not enter on fastboot upon reboot. There seems to be an opened option while booting on "Download Mode". What I did find out is that when you go into "Download Mode" a new ADB Device is detected on my computer however no driver matched the device. I assume fastboot could be avilable on Download Mode. I have been suggested by romulocarlos to Install the drivers on LG's website however did not work out.
Files:
For making the tests your will need the system.img, boot.img images files. If you brick your phone and want to un-brick the phone please follow this guide [Guide] LG G PRO LITE- Unroot/Unbrick - flash official factory firmware. Currently we are using this kdz image.
Forum:
G Pro Lite D680 Android Development at Android General.
XDA considered the case and opened a new forum for the phone. Thanks very much laufersteppenwolf (aka Wolf), MikeChannon (forum moderator) and svetius.
Conclusion:
We have reached this spot and need help from more advanced hackers. As you guys can see, we have been working hard to trying to hack the boot-on-charge feature on the D680 however has not been yet possible. There is no precedent on this phone on custom CWM & TWRP and custom roms yet therefore the is no out of the box solution as on many other phones (i.e. cyanogen list). We have also tried XDA University practices with no results.
I am ready to donate whoever would help us in solving this problem, its an urgent matter that needs to be solved as soon as possible. I will reward a developer by making a donation.
Appreciate very much the help in advance and reading.
Best,
Jose
Well, it's not that easy without having the actual device, but it'd help quite a bit if you could upload a system dump as well as the boot.img
laufersteppenwolf said:
Well, it's not that easy without having the actual device, but it'd help quite a bit if you could upload a system dump as well as the boot.img
Click to expand...
Click to collapse
Hi laufersteppenwolf,
Congratulations for your achievements and career, amazing.
I am hereby sharing two link resoruces to download what you have asked for, system.html containing the system.img and boot.html containing boot.img. Please let me know if you have problems downloading.
I understand the side effects of not having the cellphone by your side, hope we can mitigate it with the image files you are asking. As extended solution I can open a vnc session or whatever remote tool you can consider.
Thanks so much for the answer and support.
Best,
Jose
JoseVigil said:
Hi laufersteppenwolf,
Congratulations for your achievements and career, amazing.
I am hereby sharing two link resoruces to download what you have asked for, system.html containing the system.img and boot.html containing boot.img. Please let me know if you have problems downloading.
I understand the side effects of not having the cellphone by your side, hope we can mitigate it with the image files you are asking. As extended solution I can open a vnc session or whatever remote tool you can consider.
Thanks so much for the answer and support.
Best,
Jose
Click to expand...
Click to collapse
I am DL'ing the files now, but please use another hoster, as 4shared is not allowed on XDA
laufersteppenwolf said:
I am DL'ing the files now, but please use another hoster, as 4shared is not allowed on XDA
Click to expand...
Click to collapse
Hi laufersteppenwolf,
Thanks for clarifying, I was not aware 4shared was not allowed. I am changing the hosting and updating the link.
Cheers,
Jose
Alright, what I have done so far is I have unpacked the boot image and the ramdisk, edited the ramdisk so it shoud execute /system/bin/reboot when the phone boots because of the charger. Then I repacked both and signed the boot.img again so the bootloader would accept it.
The result, however, is a bootloop. I am just not yet sure whether it is caused by a "false alarm" (the ramdisk always thinking the phone is being booted because of a plugged in charger) or caused by either the bootloader or other low-level security checks. But I also doubt that, as the bootloader seems to accept the repacked image (doesn't show the security error screen).
But I currently do not have any logs, which is why all this is wild guessing. So the highest priority now is to get some proper logs so I know what's going on
laufersteppenwolf said:
Alright, what I have done so far is I have unpacked the boot image and the ramdisk, edited the ramdisk so it shoud execute /system/bin/reboot when the phone boots because of the charger. Then I repacked both and signed the boot.img again so the bootloader would accept it.
The result, however, is a bootloop. I am just not yet sure whether it is caused by a "false alarm" (the ramdisk always thinking the phone is being booted because of a plugged in charger) or caused by either the bootloader or other low-level security checks. But I also doubt that, as the bootloader seems to accept the repacked image (doesn't show the security error screen).
But I currently do not have any logs, which is why all this is wild guessing. So the highest priority now is to get some proper logs so I know what's going on
Click to expand...
Click to collapse
Hi Wolf,
Great advance! Keep the great work up .
I have made some modifications on the original post. Yes you are right, the bootloader friendly accepts the original image and we have figured out the security error. We have found on our end that you need to edit the default.prop file (located at /bootimg/initrd) and set ro.secure to value 0. I also added the files to the post (yet to change the server origin on the boot.image though), added the kdz image to unbrick. Also appended the new forum for the phone.
I appreciate that you have favored to create the forum for the G Pro Lite D680 Android Development. Its great that we can help the community with our achievements.
Best,
Jose
JoseVigil said:
Hi Wolf,
Great advance! Keep the great work up .
I have made some modifications on the original post. Yes you are right, the bootloader friendly accepts the original image and we have figured out the security error. We have found on our end that you need to edit the default.prop file (located at /bootimg/initrd) and set ro.secure to value 0. I also added the files to the post (yet to change the server origin on the boot.image though), added the kdz image to unbrick. Also appended the new forum for the phone.
I appreciate that you have favored to create the forum for the G Pro Lite D680 Android Development. Its great that we can help the community with our achievements.
Best,
Jose
Click to expand...
Click to collapse
ro.secure doesn't trigger the security checks, this prop is only for other things like adb on early boot, enabling adb remount, adb as root by default,...
I also set ro.secure to 0 in the builds I sent you, so that's not the cause of the issue
@JoseVigil
I have some pretty good news The phone now does exactly what you want it to do, as soon as you plug in the charger, the phone boots into offline charging mode, but then directly reboots again into the normal system.
The reboot is not that nice, but it's by far the easiest, as well as safest, way to do it.
Turns out, LG did a pretty sloppy job, giving me adb access to the device when in offline charging mode, giving me the chance to read which process is running and patching the binary to run my hack before actually executing the binary. And that's it. A few lines of bash code and you're good to go
Now my question, do you want me to write a tiny script to do all the work patching the system, or shall I just explain what to do?
laufersteppenwolf said:
@JoseVigil
I have some pretty good news The phone now does exactly what you want it to do, as soon as you plug in the charger, the phone boots into offline charging mode, but then directly reboots again into the normal system.
The reboot is not that nice, but it's by far the easiest, as well as safest, way to do it.
Turns out, LG did a pretty sloppy job, giving me adb access to the device when in offline charging mode, giving me the chance to read which process is running and patching the binary to run my hack before actually executing the binary. And that's it. A few lines of bash code and you're good to go
Now my question, do you want me to write a tiny script to do all the work patching the system, or shall I just explain what to do?
Click to expand...
Click to collapse
You are the man Wolf!
Its great that you have been able to find a workaround.
Yes, ideally both. I would appreciate if you can write the script so we can run it on our rooted phones pragmatically and a brief description of what it does (comprehensive from reading the script too) with implementation steps to reproduce too.
With the script I will do the proper test on my end and provide you feedback in case we have an issue. I will place the donation the coming week early on right after the test, I will be pleased that you get your reaward .
Once that, I think It would be pertinent though that we can expose how far we have reached with our research. If you agree, we can set the ground for someone (either me or you or anyone) to get a bootable customized boot image and unlock the door for CM.
I would love to see this running on CM. But I also know we have to be realistic, as you mentioned, this could be a hell of a work to have a working custom recovery, the device tree and blobs with kernel (almost XDA University I have not been able to deal with too).
It has been a lot of fun and a pleasure to know you and interact with you. I hope this is our first experience.
Thanks very much for the great work.
Best,
Jose
JoseVigil said:
You are the man Wolf!
Its great that you have been able to find a workaround.
Yes, ideally both. I would appreciate if you can write the script so we can run it on our rooted phones pragmatically and a brief description of what it does (comprehensive from reading the script too) with implementation steps to reproduce too.
With the script I will do the proper test on my end and provide you feedback in case we have an issue. I will place the donation the coming week early on right after the test, I will be pleased that you get your reaward .
Once that, I think It would be pertinent though that we can expose how far we have reached with our research. If you agree, we can set the ground for someone (either me or you or anyone) to get a bootable customized boot image and unlock the door for CM.
I would love to see this running on CM. But I also know we have to be realistic, as you mentioned, this could be a hell of a work to have a working custom recovery, the device tree and blobs with kernel (almost XDA University I have not been able to deal with too).
It has been a lot of fun and a pleasure to know you and interact with you. I hope this is our first experience.
Thanks very much for the great work.
Best,
Jose
Click to expand...
Click to collapse
Alright, in the attachment I have uploaded the script, including all needed files in order to execute it. The script will also tell you what it's about to do before doing it, so in case you run into issues, you know where to look into
So, what the installer script is going to do:
It will first of all push a script temporarily to the internal sdcard, then it will back up /system/bin/rtcd to /system/bin/rtcd_original, as we need to execute it later again. Next it will copy the script over from the sdcard to /system/bin/rtcd, replacing the original binary (and setting the correct permissions to both modified files). As the last step it will delete the temp file from the sdcard again.
That's all the installer script does.
The actual "magic" is inside the script being pushed to /system. It gets executed before starting chargemon and reads out the devices boot mode. If the boot mode is charger, it executes /system/bin/reboot. Otherwise it executes the original binary in /system/bin/rtcd_original.
And that's about it As simple as it could only be
Regarding further development, up until now, every device I own received a werewolf kernel, and I'm not planning on making an exception for this phone
I will definitely keep on looking into it, though it will not be as high on my priorities list as this workaround was
I will most likely open a new thread in the next couple of days, stating my findings regarding the phone/boot image/bootloader.
@JoseVigil @laufersteppenwolf
I'm New In Rom Developing . But I Think This Can Help You To Find Security Checks
I need lg g pro lite dual d686 custom twrp recovery i cant find anywhere plz provide working recovery link for d686 as iam new it seems custom recovery for specific d686 dosnt exits so share tested link for d686
Sent from my LG-D686 using xda Forums PRO
Hello I need boot on charge on my LG E460 with MTK. I done ipod change, rctd replace from laufersteppenwolf file without results. I can't went into fastboot mode of course to set oem mode charge for 0
Phone have root, bootloader unlock, busybox and supersu. Any suggestions?
Maxjimme said:
I need lg g pro lite dual d686 custom twrp recovery i cant find anywhere plz provide working recovery link for d686 as iam new it seems custom recovery for specific d686 dosnt exits so share tested link for d686
Sent from my LG-D686 using xda Forums PRO
Click to expand...
Click to collapse
TWRP RECOVERY
http://forum.xda-developers.com/optimus-g-pro/d680-development/d686-unsecured-boot-img-twrp-2-8-7-x-t3163144
Same Problem here with LG E460. Is there a solution for fastboot mode with this device?
hi, do you think this script could work on a LG G Pro 2 ?
hi guys, any chance i could get this working on a chinese mediatek device running kitkat 4.4.2 ??
Hi there!
So, anybody who updated to android 10 knows about the annoying suggestions appearing in settings, which at the moment can't be dismissed or swiped away. Clearing the data of Settings Suggestions app can "fix" the issue momentarily but it'll come back again. Seems like the issue is about suggestions.xml file (/data/data/com.android.settings.intelligence/shared_prefs/suggestions.xml) not updating the boolean values correctly.
Examples:
Code:
<boolean name="com.android.settings/com.android.settings.wallpaper.StyleSuggestionActivity_is_dismissed" value="false" />
Code:
<boolean name="com.android.settings/com.android.settings.wallpaper.WallpaperSuggestionActivity_is_dismissed" value="false" />
The above lines must be changed from "false" to "true" in order for the suggestions to be dismissed but root is required to access and edit the suggestions.xml file i mentioned above. However, i managed to discover a rootless way of doing that by creating an adb data only backup of Settings Suggestions app. I used adb backup extractor to extract the backup file and edit suggestions.xml, restored the edited backup file via adb restore and the suggestions were gone. I've tried the method twice just to be sure and it's working.
I'm attaching the zip containing the edited backup file that you guys can restore using "adb restore data.ab" command.
NOTE: The restore process won't work on old adb drivers so make sure you use the latest platform tools before trying.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Sapper Morton said:
Could you also include a backup of this boolean?
Code:
<boolean name="com.google.android.gm/com.google.android.gm.setup.AccountSetupFinalGmailSuggestions_is_dismissed" value="true" />
Click to expand...
Click to collapse
There you go!
Can you please explain step by step how to do this? Do I have to download a certain app or connect my phone into a pc/laptop?
THEGEEK2015 said:
Can you please explain step by step how to do this? Do I have to download a certain app or connect my phone into a pc/laptop?
Click to expand...
Click to collapse
1 - Make sure you have the latest adb drivers.
2 - Extract the attached zip and put "data.ab" in the same folder were the adb executable is.
3 - Enable usb debugging in your device
4 - Connect the device and execute "adb restore data.ab" in adb
eltonb said:
1 - Make sure you have the latest adb drivers.
2 - Extract the attached zip and put "data.ab" in the same folder were the adb executable is.
3 - Enable usb debugging in your device
4 - Connect the device and execute "adb restore data.ab" in adb
Click to expand...
Click to collapse
I'm afraid that by replacing our data.ad with the one provided by you, will cost the loss of our app data.
Is there a toolkit to help us edit data.ad?
jolas said:
I'm afraid that by replacing our data.ad with the one provided by you, will cost the loss of our app data.
Is there a toolkit to help us edit data.ad?
Click to expand...
Click to collapse
As u can notice, the backup is a mere 2 kb file. It's a backup of only the Settings Suggestions app data, which is responsible for the suggestions in settings. However, if u are not comfortable using my backup, adb backup extractor is the tool you need....
Just wanna clarify if this needs root or not
Bro, Thanks a lot for your work and even big thanks for sharing! I have one more bug that I saw only a few people mentioning. I have sent it to Xiaomi also but there's no response. So here is the deal. I see the font and display size as 'big' on the lockscreen, when I have kept settings of both to 'small'. I have to go to settings and do some back n forth to get the uniform results. It turns back after I restart the device. Do you know or could you please find any solution to it? Thanks again!
@amnher Nope, only adb
@tejas1903 In my case, when i change the display size, certain elements like the power menu revert back to their original size after locking the phone (lock screen isn't affected though). I noticed it only happens when i use fingerprint unlock, which means getting rid of the fingerprints and keeping pin/password/pattern only as a method of unlocking fixes the issue in my case. I don't know if we are affected by the same bug, you can test it by removing the fingerprint and see for yourself. It's a pitty, when the first android 10 update came i thought the suggestion bug would be fixed by the 2nd update, yet here we are on the 4th one. Xiaomi really takes it's time in fixing the bugs however i still hope for a future bug free release....
eltonb said:
@amnher Nope, only adb
@tejas1903 In my case, when i change the display size, certain elements like the power menu revert back to their original size after locking the phone (lock screen isn't affected though). I noticed it only happens when i use fingerprint unlock, which means getting rid of the fingerprints and keeping pin/password/pattern only as a method of unlocking fixes the issue in my case. I don't know if we are affected by the same bug, you can test it by removing the fingerprint and see for yourself. It's a pitty, when the first android 10 update came i thought the suggestion bug would be fixed by the 2nd update, yet here we are on the 4th one. Xiaomi really takes it's time in fixing the bugs however i still hope for a future bug free release....
Click to expand...
Click to collapse
Okay will try.. and Thanks again!
New suggestion appeared today "Set Night Light Schedule".
OP updated.
eltonb said:
@amnher Nope, only adb
@tejas1903 In my case, when i change the display size, certain elements like the power menu revert back to their original size after locking the phone (lock screen isn't affected though). I noticed it only happens when i use fingerprint unlock, which means getting rid of the fingerprints and keeping pin/password/pattern only as a method of unlocking fixes the issue in my case. I don't know if we are affected by the same bug, you can test it by removing the fingerprint and see for yourself. It's a pitty, when the first android 10 update came i thought the suggestion bug would be fixed by the 2nd update, yet here we are on the 4th one. Xiaomi really takes it's time in fixing the bugs however i still hope for a future bug free release....
Click to expand...
Click to collapse
1. So if i disable adb it will stay?
2. And I suppose factory reset will revert?
amnher said:
1. So if i disable adb it will stay?
2. And I suppose factory reset will revert?
Click to expand...
Click to collapse
1. Yes
2. Yes
Can u make any guide, how to read your backup file? i dont like to restore your backup!
[GS] said:
Can u make any guide, how to read your backup file? i dont like to restore your backup!
Click to expand...
Click to collapse
ADB Backup Extractor is a tool that's used to pack and unpack adb backups.
thanks for your work, but new suggestion appears: on body detection
its like if you turn off one thing another opens
but thanks for your help
gamernayeem said:
thanks for your work, but new suggestion appears: on body detection
its like if you turn off one thing another opens
but thanks for your help
Click to expand...
Click to collapse
I'll keep the backup file updated with any new suggestion that appears until Xiaomi fixes it, if they do. I haven't encountered this one yet, which means i don't know the corresponding boolean to add to the suggestions.xml. If you manage to find it you can post it right here. If you can't, you can also post a data backup of your Settings Suggestions app using the following command (and i'll find it myself):
adb backup -f data.ab -noapk com.android.settings.intelligence
eltonb said:
I haven't encountered this one yet, which means i don't know the corresponding boolean to add to the suggestions.xml. If you manage to find it you can post it right here. If you can't, you can also post a data backup of your Settings Suggestions app using the following command (and i'll find it myself):
adb backup -f data.ab -noapk com.android.settings.intelligence
Click to expand...
Click to collapse
It should be this line:
Code:
<boolean name="com.google.android.gms/com.google.android.gms.trustagent.discovery.OnbodyPromotionActivity_is_dismissed" value="true" />
Btw, thank you very much, this is also a problem for Mi A2 since the android 10 update and your workaround worked great for me too.
birdflesh said:
It should be this line:
Code:
<boolean name="com.google.android.gms/com.google.android.gms.trustagent.discovery.OnbodyPromotionActivity_is_dismissed" value="true" />
Btw, thank you very much, this is also a problem for Mi A2 since the android 10 update and your workaround worked great for me too.
Click to expand...
Click to collapse
You're welcome! Mi A3, Mi A2, Mi A2 Lite and some other Nokia phones seem to have this issue. Thanks for posting the On Body Detection boolean, however since my "suggestions.xml" has no such line and i added it manually, i don't know if it'll work.... So, i'm attaching a test backup file which @gamernayeem or anyone who has the On Body Detection suggestion can try and see if it works. I'll update the OP then
Thanks man, i use your ideea to mi A2lite with andro Q, with same problem. I have a question: in the process of unpacking you use linux or just windows?