Hello xda comunity, I request your help.
I have a H815 V10d. I have root access but the bootloader still locked, so no custom recovery
Changed DPI from 640 to 540 using this app. Rebooted and... stuck in bootloop with LG's logo
I have the original build.prop file backup, any way I could restore it? Maybe ADB or something?
Thanks for your help.
That happens because the App is not saving your build prop properly and it is now screwed. You can probably fix it by booting into stock recovery and doing and ADB push command to push the stock build prop back.
But why are you using an app. If you are, use TexDroider for DPI changes. It requires root.
If you are unrooted, just use the ADB command to change it safely and securely without screwing with your build.prop file.
Related
Hi.
I have an app, which replaces the sotck fonts with the patched ones. This tools just executes commands via exec.
Today received my One. It is unlocked, custom recovey is flashed and also Trickdroid Custom rom is flashed.
When I replace the fonts (it does not matter via app or via adb shell) the changes are made. I can see it on the console.
But after I reboot the phone, the fonts are restored. What is the problem? I'm new to htc. I've heared about Permanent root and not modifiable system partition but I thought this was only for some locked older devices?
Lado
From what I've seen, once the phone is fully booted the system 'partition' must be mirrored into a r/w section of memory. This allows you to overwrite system files temporarily (until reboot) but the changes are lost when the OS is mirrored again on reboot.
Sent from my Tricked out 2.4.0 HTC One via xda-developers application
herrlado said:
Hi.
I have an app, which replaces the sotck fonts with the patched ones. This tools just executes commands via exec.
Today received my One. It is unlocked, custom recovey is flashed and also Trickdroid Custom rom is flashed.
When I replace the fonts (it does not matter via app or via adb shell) the changes are made. I can see it on the console.
But after I reboot the phone, the fonts are restored. What is the problem? I'm new to htc. I've heared about Permanent root and not modifiable system partition but I thought this was only for some locked older devices?
Lado
Click to expand...
Click to collapse
It is ok
I had the same thing
All you need to do is change the fonts via recovery with a flashable zip
Thats it
Sent from my HTC One using Tapatalk 2
How would you change back to the default fonts ?
Sent from my HTC One using xda app-developers app
So I have resolved the problem. As mentioned above, it must be flashed in the recovery mode with an update.zip
Thanks to all.
Lado
I have done this before but I used what seems to be a different version of freegee (didn't have the option to backup efs or flash TWRP) so I unlocked my device and after it had completed I rebooted and then powered down. I put my phone in to CWM and flashed the stock debloated ROM. After flashing this ROM I was stuck in a bootloop. I ended up using LG Tool to get it back to stock. I thought it must have been a random once off issue so I tried again with Freegee, same thing happened, only this time no matter what I do I can not get LG Tool to fix the issue as it keeps giving me the error of low battery even though it is at full capacity. I then tried to use BC2 to flash a kdz file and I get the same error. I have since tried factory resetting, sideloading different recoveries, ROMs and basebands without boot. I have tried to use LG Tool about 50 times and it is not working. I have changed USB ports, reinstalled drivers etc, just keeps giving me that error. Yes I have set permission in the app and I am using Windows 7
uppon2 said:
I have done this before but I used what seems to be a different version of freegee (didn't have the option to backup efs or flash TWRP) so I unlocked my device and after it had completed I rebooted and then powered down. I put my phone in to CWM and flashed the stock debloated ROM. After flashing this ROM I was stuck in a bootloop. I ended up using LG Tool to get it back to stock. I thought it must have been a random once off issue so I tried again with Freegee, same thing happened, only this time no matter what I do I can not get LG Tool to fix the issue as it keeps giving me the error of low battery even though it is at full capacity. I then tried to use BC2 to flash a kdz file and I get the same error. I have since tried factory resetting, sideloading different recoveries, ROMs and basebands without boot. I have tried to use LG Tool about 50 times and it is not working. I have changed USB ports, reinstalled drivers etc, just keeps giving me that error. Yes I have set permission in the app and I am using Windows 7
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=48205695&postcount=13
atifsh said:
http://forum.xda-developers.com/showpost.php?p=48205695&postcount=13
Click to expand...
Click to collapse
Thank you, I will use that if I ever get LG Tool to stop throwing me the low battery warning. What a stupid program to not give you the option to bypass it. Surely there is a way I can do this. My battery is at 99%. I just flashing madmack hacked and lockified recovery and now I can't even get in to recovery to do sideloads. I am running out of options, my only way is to get LG Tool or B2C to work
EDIT* I have recovery back. GRR why is this stupid message about low battery keep popping up
uppon2 said:
Thank you, I will use that if I ever get LG Tool to stop throwing me the low battery warning. What a stupid program to not give you the option to bypass it. Surely there is a way I can do this. My battery is at 99%. I just flashing madmack hacked and lockified recovery and now I can't even get in to recovery to do sideloads. I am running out of options, my only way is to get LG Tool or B2C to work
EDIT* I have recovery back. GRR why is this stupid message about low battery keep popping up
Click to expand...
Click to collapse
have not tested this from cm rom but works from any stock. bytheway i have optimus G not pro
from recovery adb push rom.zip (your rom)
adb push rom.zip /sdcard/0
(0 required for cwm and cm10.2)
flash that rom
enable debugging
run lgflash tool one that supports large files or the online one it will pass the battery and auto restart in download mode there it will give error just unplug replug and retry and it will be flashed this time.
atifsh said:
have not tested this from cm rom but works from any stock. bytheway i have optimus G not pro
from recovery adb push rom.zip (your rom)
adb push rom.zip /sdcard/0
(0 required for cwm and cm10.2)
flash that rom
enable debugging
run lgflash tool one that supports large files or the online one it will pass the battery and auto restart in download mode there it will give error just unplug replug and retry and it will be flashed this time.
Click to expand...
Click to collapse
I am unsure what this is but I am interested? Thanks, I ended up doing what I was trying to do in the first place and IT WORKED
To anybody that faces the same issue:
in recovery sideload install madmacks TWRP file attached below
after that is installed flash CM11 using the same sideload
The command in adb is adb sideload (your file name in here without the brackets.zip) You must include .zip
It is strange because it didn't work the first 3 times I flashed the ROM and on the fourth it worked, so keep trying
i can fix bootloop to cwm or recovery just 2 minutes. but u have to backup your stock recovery fírst before install cwm or twrp.
so thiss step to solve after u have boot loop. that u need to restore back your stock recovery on mmcblk0p28 then reboot. you will stuck at factory software repair. keep ur fone connected with the computer and type adb reboot. then u can boot into android os. and final step. u reinstall your custom recovery again and Enjoy. this fixing not for newbie and im typing it on my fone. someone can make automation script to help People solve it im lazy
Sent from my Optimus G Pro using Tapatalk
thaiminhan said:
i can fix bootloop to cwm or recovery just 2 minutes. but u have to backup your stock recovery fírst before install cwm or twrp.
so thiss step to solve after u have boot loop. that u need to restore back your stock recovery on mmcblk0p28 then reboot. you will stuck at factory software repair. keep ur fone connected with the computer and type adb reboot. then u can boot into android os. and final step. u reinstall your custom recovery again and Enjoy. this fixing not for newbie and im typing it on my fone. someone can make automation script to help People solve it im lazy
Sent from my Optimus G Pro using Tapatalk
Click to expand...
Click to collapse
Thanks for trying to help. I am not running stock and can not get a stock ROM to work (with locked bootloader obviously)
LG Tool is requesting for a TOT file which the E988 doesn't have, I have tried using E98810D_00.kdz file in the software field but it is not recognising the cab file. The DLL file is recognised but I don't know what else to do from there.
LG Mobile Support Tool keeps failing on me due to low battery error which as you can see, I have been trying my hardest to get it to work. Battery is at 99% but it still won't flash! - I am stuch with a custom ROM and a dodgy unlocked bootloader due to the latest release FreeGee.
I tried the old file you attached but it fails to download the image file to unlock my bootloaders, I guess because it is already unlocked.
What I need now is to find a way to relock my bootloader that doesn't involve LG Tool/LG Mobile Tool and then try the old FreeGee app again. Or I find a way to get passed this stupid battery warning
uppon2 said:
I have done this before but I used what seems to be a different version of freegee (didn't have the option to backup efs or flash TWRP) so I unlocked my device and after it had completed I rebooted and then powered down. I put my phone in to CWM and flashed the stock debloated ROM. After flashing this ROM I was stuck in a bootloop. I ended up using LG Tool to get it back to stock. I thought it must have been a random once off issue so I tried again with Freegee, same thing happened, only this time no matter what I do I can not get LG Tool to fix the issue as it keeps giving me the error of low battery even though it is at full capacity. I then tried to use BC2 to flash a kdz file and I get the same error. I have since tried factory resetting, sideloading different recoveries, ROMs and basebands without boot. I have tried to use LG Tool about 50 times and it is not working. I have changed USB ports, reinstalled drivers etc, just keeps giving me that error. Yes I have set permission in the app and I am using Windows 7
Click to expand...
Click to collapse
i have same problem with you, anyone have solution??
kuwir said:
i have same problem with you, anyone have solution??
Click to expand...
Click to collapse
Check this
http://forum.xda-developers.com/showthread.php?p=48225776
Sent from my LG-E980 using XDA Premium HD app
kuwir said:
i have same problem with you, anyone have solution??
Click to expand...
Click to collapse
First try to use LG Mobile Tool. All files and instructions found here CLICK ME
If that doesn't work the follow the instructions I posted earlier and it will get your phone booting again. As for getting back to stock and unlocking the bootloaders without causing kernel issues, I am still waiting for a response from Seth. He has been making a lot of changing as this is a known problem. The latest version is supposed to work like it used to now.
uppon2 said:
I am unsure what this is but I am interested? Thanks, I ended up doing what I was trying to do in the first place and IT WORKED
To anybody that faces the same issue:
in recovery sideload install madmacks TWRP file attached below
after that is installed flash CM11 using the same sideload
The command in adb is adb sideload (your file name in here without the brackets.zip) You must include .zip
It is strange because it didn't work the first 3 times I flashed the ROM and on the fourth it worked, so keep trying
Click to expand...
Click to collapse
Thanks! This worked 100%. Something's really up with the freegee CWM, totally useless. Had 3 days of a headache till I saw this post. I used to be a CWM guy, now TWRP all the way...! The interface is touch based and much easier to handle than CWM. Best of all it doesn't go into a bootloop! Cheers! :good::good:
I changed it to an unsupported number via ROM Toolbox. I'm no longer able to do anything, as the UI crashes instantly. I can't just replace the official firmware via download mode and Odin to fix this, correct?
Yes, but in the future before changing stuff like that I would take a nandroid.
Joeful said:
I changed it to an unsupported number via ROM Toolbox. I'm no longer able to do anything, as the UI crashes instantly. I can't just replace the official firmware via download mode and Odin to fix this, correct?
Click to expand...
Click to collapse
Yep ur power screwed. Just start over with a new installation. As HughesNet suggested, always Nandroid first before messing with things like DPI.
You should be able to revert through ADB. Search for which file has the dpi setting. Change it back to stock and push with ADB. You can also try terminal in TWRP
Any suggestions on values and procedures on adjusting DPI?
Hi,
I have ZE551ML. I rooted using method 2 (temporary CWM). Before installing the latest OTA, I did full unroot in SuperSU and uninstalled Xposed. I proceeded with the normal OTA. Upon restart, it was stuck in bootloop. I can get to fastboot and select recovery mode there. My main problem is I can't see the device in ADB. Whenever I type adb devices, I just keep getting "list of devices attached" and my device is nowhere there. I'm pretty sure I have the Intel drivers and ADB tools since I used the same PC in flashing/rooting this device and an older Zenfone 5.
Is there any way I can unbrick my phone. Or is there any way I can fix the ADB not showing my device?
Jaymz123 said:
Hi,
I have ZE551ML. I rooted using method 2 (temporary CWM). Before installing the latest OTA, I did full unroot in SuperSU and uninstalled Xposed. I proceeded with the normal OTA. Upon restart, it was stuck in bootloop. I can get to fastboot and select recovery mode there. My main problem is I can't see the device in ADB. Whenever I type adb devices, I just keep getting "list of devices attached" and my device is nowhere there. I'm pretty sure I have the Intel drivers and ADB tools since I used the same PC in flashing/rooting this device and an older Zenfone 5.
Is there any way I can unbrick my phone. Or is there any way I can fix the ADB not showing my device?
Click to expand...
Click to collapse
maybe u didn't remove xposed framework files, that's the reason for bootloop/brick
Siddk007 said:
maybe u didn't remove xposed framework files, that's the reason for bootloop/brick
Click to expand...
Click to collapse
you mean the modules like greenify?
Jaymz123 said:
you mean the modules like greenify?
Click to expand...
Click to collapse
no, not modules. xposed framework which u installed using installxposedframework.bat from pc
Ok, I was able to recover my phone by flashing the pre-rooted system.img (method 1). I want to sideload the whole stock firmware but my problem remains. If I boot my phone normally, adb devices command shows my phone. But whenever I go to fastboot either by typing adb reboot bootloader or by holding ON/vol up, my phone is not showing up in ADB, therefore I can't sideload anything.
Is there any way I can unroot or revert back to a stock ROM? I'm kind afraid to unroot in SuperSU because I bootlooped yesterday (might have been the xposed though as suggested by Skid). Is there any stock system.img out there?
Jaymz123 said:
Ok, I was able to recover my phone by flashing the pre-rooted system.img (method 1). I want to sideload the whole stock firmware but my problem remains. If I boot my phone normally, adb devices command shows my phone. But whenever I go to fastboot either by typing adb reboot bootloader or by holding ON/vol up, my phone is not showing up in ADB, therefore I can't sideload anything.
Is there any way I can unroot or revert back to a stock ROM? I'm kind afraid to unroot in SuperSU because I bootlooped yesterday (might have been the xposed though as suggested by Skid). Is there any stock system.img out there?
Click to expand...
Click to collapse
Put the update file onto your sd card, rename to MOFD_SDUPDATE.zip.
Reboot and it should update as long as the pre-root image was 19.40.22 .
Reflash TWRP if the bootloader is unlocked and you have a rooted phone with custom recovery...
Yes it works, and yes I did it yesterday exactly like that...
I have a 64gb 2.3ghz 551ML with unlocked bootloader. Don't know if the unlocked bootloader might be the factor that allows this to work...
I just went on and made full unroot from SuperSU. It went smoothly. I guess the one that caused my bootloop was the uinstalled xposed framework.
Bootloader is locked now. The only problem I have now is the ADB thing. My phone is not detected when in recovery but works just fine when normally booted. I have the latest USB driver from Intel and the other one from ASUS. I also have installed ADB installer, the one with the blue screen and where you press Y few times to install.
Hi, i have a xiaomi mi 6. The bootloader is unlocked, officially.
My question is: can i relock the bootloader after i moved two apps as a system apps? The applications only work that way, or with root privileges. Those two app is needed to enable or disable android services.
I use banking apps, which detect rooted or unlocked phones. Safetynet need to
pass. Keeping root or magisk is not an option for me. Beside safetynet, those banking apps have their own custom detecting sistem, which magisk can't hide.
I have stock recovery now , root is removed (unrooted).
On my old sony z3 that procedures worked, dose is work on mi 6 too? Or it will brick the device.? A bricked device with locked bootloader is a nightmare...
I want a locked bootloader to be able to use fingerprint and use all of my banking apps. But i need to enable/disable services at any time.
Hi,
From what I heard, if you relock the bootloader, you won't be able to unlock it again as xiaomi won't give you the right to unlock phone twice. So it's a bad idea.
Lork Scorguar said:
Hi,
From what I heard, if you relock the bootloader, you won't be able to unlock it again as xiaomi won't give you the right to unlock phone twice. So it's a bad idea.
Click to expand...
Click to collapse
Thanks for replying.
If you get permission to unlock officially, you cand unlock and relock as many times as you want.
Absolutely not. If you made a modification of the system, dm-verity will notice it, and the phone will be stuck in a bootloop.
Boot in custom recovery and move the app in system.. You dont need root for that. Just un-encrypted phone and TWRP.
Main problem will be, how you get the files from the apk. You could install it on another phone (which is rooted), make the app a system app and then get the folders of said app, which you can copy via adb to your Mi6. And in recovery mode you can mount system as rw.
OR
TWRP has a feature to make any app a system app (dunno)
OR
someone can make you flashable zip file for TWRP.
thE_29 said:
Boot in custom recovery and move the app in system.. You dont need root for that. Just un-encrypted phone and TWRP.
Main problem will be, how you get the files from the apk. You could install it on another phone (which is rooted), make the app a system app and then get the folders of said app, which you can copy via adb to your Mi6. And in recovery mode you can mount system as rw.
OR
TWRP has a feature to make any app a system app (dunno)
OR
someone can make you flashable zip file for TWRP.
Click to expand...
Click to collapse
Thanks man, but converting app to system app is not a problem. I can do that with root or with twrp, as you mentioned.
The problem is relocking the bootloader after i moved app as a system app and disabled some services.
G4B33 said:
Absolutely not. If you made a modification of the system, dm-verity will notice it, and the phone will be stuck in a bootloop.
Click to expand...
Click to collapse
Will dm-verity prevent my phone from booting if i flash no-dm-verity patch or disable dm-verity from twrp?
After i disabled it, flash stock recovery and relock?