Related
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
Has anyone been able to do this yet? I don't feel like rooting anymore since all I use root for is to use AdAway and getting OTA updates is just a PITA with having to RUU, restore all my stuff, just takes forever.
Apparently you can adb push a modded hosts file in TWRP and I've done so successfully, but everytime I reboot phone it reverts back to the stock hosts file (1 KB) and none of my changes are made.
I'm not pushing to the wrong place. I can do a adb pull immediately after and it retrieves the modified hosts file I want, it just doesn't stay that way after I reboot.
The process I'm doing:
Boot into TWRP
ADB pull stock hosts file
ADB push modded hosts file
CHMOD 0644 using TWRP file manager
Reboot
Test in browser/apps
Doesn't work
Boot back into TWRP
ADB pull hosts file
It's reverted back to stock 1KB unmodified
Anyone with more experience pls chime in, would be greatly appreciated.
cauqazn said:
Has anyone been able to do this yet? I don't feel like rooting anymore since all I use root for is to use AdAway and getting OTA updates is just a PITA with having to RUU, restore all my stuff, just takes forever.
Apparently you can adb push a modded hosts file in TWRP and I've done so successfully, but everytime I reboot phone it reverts back to the stock hosts file (1 KB) and none of my changes are made.
I'm not pushing to the wrong place. I can do a adb pull immediately after and it retrieves the modified hosts file I want, it just doesn't stay that way after I reboot.
The process I'm doing:
Boot into TWRP
ADB pull stock hosts file
ADB push modded hosts file
CHMOD 0644 using TWRP file manager
Reboot
Test in browser/apps
Doesn't work
Boot back into TWRP
ADB pull hosts file
It's reverted back to stock 1KB unmodified
Anyone with more experience pls chime in, would be greatly appreciated.
Click to expand...
Click to collapse
Are you just unlocked?
Sent from my HTC6545LVW using Tapatalk
I am sure its possible via TWRP but you will have to mount system first otherwise you are just flashing into the TWRP system itself.
But the moment you modify /system/ (Even mounting it) your device will no longer accept OTA.
dottat said:
Are you just unlocked?
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
Yes, unlocked only.
Electronic Punk said:
I am sure its possible via TWRP but you will have to mount system first otherwise you are just flashing into the TWRP system itself.
But the moment you modify /system/ (Even mounting it) your device will no longer accept OTA.
Click to expand...
Click to collapse
I see. I mounted system before doing all of that. Meh, I guess I'm just going to have to root.
I went down this same path but ended up rooting so I could run AdAway. Easy enough to restore stock system image and recovery once the OTA comes out. With luck that process won't disturb the encrypted /data partition.
Hi,
i tried to block OS Updates by changing ro.build.version.number in build.prop as mentioned here: http://www.aftvnews.com/how-to-bloc...k-by-setting-a-custom-fire-os-version-number/
Pulled the stock build.prop to my windows PC, edited it with notepad++ and copied back to my FireTV Stick´s /system folder. Rebooted and its stuck at boot now. After the Splash screen (white amazon text) its showing a blank screen.
Well, later in the comments of the aftvnews guide i found out i had to change permission of build.prop for it to work so i tried via adb but got an Error: Read-only file system.
Long story short:
Is there a way to get my FireTV Stick running again or is it bricked?
Edit: Is it possible to flash one of these bin files found here:http://www.aftvnews.com/amazon-fire-tv-fire-tv-stick-software-update-history/ ?
If you were editing the build.prop file you must of been rooted, why don't you just push the unedited build.prop from your pc to your stick? Assuming you had adb enabled and can connect through adb.
Try with USB plugged in and the easiest way to do it would be adblink.
Ive noticed an older version has options to mount the system rw if rooted, I think it was a couple of version ago.
I tried pushing the file back on the Stick but always getting Read-only filesystem error. Remounting /system didnt work also: Permission denied. Then tried adbLink 2.04, says filesystem mounted r/w but i am still unable to push build.prop (same error as always: Read-only filesystem)
Pushing with adbLink seems to not work either, although adbLink saying pushing file was successfull.
Root seems to be broken somehow? running su command in adb shell only gives me "1|[email protected]" , shouldnt it be "[email protected]"?
Run the windows version of Kingo root with USB plugged in. Try a few times if it fails.
Also give king root pc version a go.
Unfortunately no luck either. Even after 20+ runs.
Can't understand how that has happened of you had root, yoi should still be able to adb su into it.
Sorry I couldn't help
I've often used twrp to allow rootless (no SuperSU/magisk) edits via adb push/pull in the past. I tried doing this on my pixel 2 Xl on 8.1 and there are a few abnormalities:
1. Build.prop is under /system/system/build.prop
2. Changes I make there seem to be persisting across reboots, but the setting itself isn't having an impact.
Is there something I'm doing wrong? I know I can just root it, but I hate the idea of running some guys code and having potential safety net and app issues on an ongoing basis as things get upgraded. Just to enable making one change to build.prop.
Bumping this. After using Magisk to root, I used a file explorer to edit my build.prop and added a command to disable the nav bar. This method works perfectly fine. However, with Magisk causing random reboots on a daily basis, I'm looking to get rid of Magisk, for the time being.
After removing Magisk (root) my phone boots up just fine but the command in the build.prop to disable the nav bar no longer works, so the Nav bar shows up. When I ADB Pull my build.prop, I'm seeing that the command line I added is there. But without root the system won't apply the command.
As soon as I re-install Magisk and reboot, the nav bar is gone again. So I essentially need to figure out how to get the build.prop edit to continue being used by the system without Magisk.
I tried editing the build.prop permissions by using ADB Shell and setting the appropriate permission with "chmod 644 /system/system/build.prop but it just keeps erroring out.
Any ideas?
Hey folks,
Last night I was editing a file located under "data/system/users/0/settings_ssaid.xml" and upon rebooting my phone, it's been stuck in a boot loop. I have an original copy saved in a different folder, but unable to access anything to replace it.
Is there any specific fastboot command I can run to swap the files (adb push, pull etc)? Only boot slot A is giving me an issue, and I was reading flashing system.img would be able to help, but I don't wanna do anything I'm unsure will wipe any of my data where I'd have to start over unless I've recovered some of that data first.
If I do have to flash any stock images, pls post the instructions for clarity.
Thanks in advance.
Assuming adb can actually access your device, while it's stuck in a boot loop (test this by running 'adb devices' and see if you receive a response)
You can run the following command to list all the files in your specific folder.
adb shell ls FILEPATH
Every file in your specific folder will be listed. You can then do the following to pull/push your file
adb pull FILEPATH
adb push FILENAME FILEPATH
Of course you need to place the file that you want to push in your ADB folder.
Mind though, that simply replacing your edited file with the backup might not solve your bootloop.
You can always look up available commands here
adb shell ls - Android ADB Shell Commands Manual
Morgrain said:
Assuming adb can actually access your device, while it's stuck in a boot loop (test this by running 'adb devices' and see if you receive a response)
Click to expand...
Click to collapse
Yes, I can access adb and my device while it's booting up, but once it reboots I lose connection. Unless I can interrupt the process I'd have to be very quick in my typing to copy files lol.
Even with the few seconds I have to type some commands to access the directory of the file I edited, I do get a permission denied error.
Would swapping to Slot B during boot allow me into the system, or even flashing the system.img file?
RetroTech07 said:
Yes, I can access adb and my device while it's booting up, but once it reboots I lose connection. Unless I can interrupt the process I'd have to be very quick in my typing to copy files lol.
Even with the few seconds I have to type some commands to access the directory of the file I edited, I do get a permission denied error.
Would swapping to Slot B during boot allow me into the system, or even flashing the system.img file?
Click to expand...
Click to collapse
No because your file is on /data.
The issue is that you can't push your file to /scard since (I guess) you can't even get beyond to the point where /sdcard is mounted.
So copying it from /sdcard will likely be too late in the boot process.
Pushing directly into /data does not work either as you would have to be root. In the old days you could run and in root mode but I'm not sure that is still possible.
Factory reset will work.
On devices with separate recovery partition it would be possible to change recovery to allow adb access to /data so then push old file via recovery... But I would not know how to do that on Pixel as recovery is s part of the boot partition.
So effectively, it's likely you're only solution is to do a full firmware flash along with wipe.
I would first try a full flash removing the -w to avoid the wipe. It may work.
TonikJDK said:
I would first try a full flash adding the -w to avoid the wipe. It may work.
Click to expand...
Click to collapse
Probably a typo, but I think you meant you need to "remove" the -w to avoid a wipe.
Lughnasadh said:
Probably a typo, but I think you meant you need to "remove" the -w to avoid a wipe.
Click to expand...
Click to collapse
Thank you! My post is fixed.
TonikJDK said:
I would first try a full flash removing the -w to avoid the wipe. It may work.
Click to expand...
Click to collapse
Ok, I'm rooted so to be sure I don't mess anything up, lol can you list the steps just as a precaution?
Obviously I'd be in fastboot / recovery mode, then perform a flash-all but remove the -w so as to not erase my data?
Once the system boots, all of my texts and setup should remain as is, or do I have to go and recover it?
Would I be able to install the OS again on the inactive slot to recover data, or does that not work that way?
RetroTech07 said:
Would I be able to install the OS again on the inactive slot to recover data, or does that not work that way?
Click to expand...
Click to collapse
Nope ... there is only 1 data partition, so even when you flash the OS to the inactive slot, it would still use the same data partition. Moreover, it is then likely to upgrade/convert some files on /data which might result in not being able to go to the previous version in the old slot.
RetroTech07 said:
Ok, I'm rooted so to be sure I don't mess anything up, lol can you list the steps just as a precaution?
Click to expand...
Click to collapse
See https://forum.xda-developers.com/t/...thout-wiping-data-and-retaining-root.4356065/
so, unfortunately doing a full flash without wiping data didn't work. I'm almost inclined to believe that if TWRP was available for the P6/P, that I could go and push the file I had saved back into the directory of where it was and save myself from this mess.
I'm kicking myself because I'm usually backing up my data before I modify any system files, but this one time I hadn't done so and I had Google's backup turned off at the time, so I'm gonna have to lose some text messages over the last few days with some folks I enjoy speaking to. I do have some saved from late last week, but nothing from the weekend up until now.
As you said you can access ADB while booting, why not push/remove/replace the file while booting, even if this takes multiple boots to perform all commands, it should work assuming you can also use SU, if you can't, none of the below will work.
Code:
adb push <backup file location> /sdcard
adb shell
su
rm data/system/users/0/settings_ssaid.xml
cp /sdcard/settings_ssaid.xml /data/system/users/0/
chmod 600 data/system/users/0/settings_ssaid.xml
I don't know why it's affecting your boot though, there's a .fallback file that the system should fall back to when the system notes that this file is corrupt.
If the above doesn't work, and you could try:
Code:
adb shell
su
rm data/system/users/0/settings_ssaid.xml
cp /data/system/users/0/settings_ssaid.xml.fallback /data/system/users/0/settings_ssaid.xml
If that doesn't work, try:
Code:
adb shell
su
rm data/system/users/0/settings_ssaid.xml
And reboot, but again, I don't know why you're bootlooping from this, that file shouldn't be integral to booting.
Also, if you need to back up your data, why not just boot to boot_b, if it's not causing you issues? You really shouldn't have to reset your device to fix one problem - you could do a /data & /sdcard pull while booted to boot_b, or just run something like Titanium & SMS backup/restore.
DanielF50 said:
As you said you can access ADB while booting, why not push/remove/replace the file while booting, even if this takes multiple boots to perform all commands, it should work assuming you can also use SU, if you can't, none of the below will work.
Code:
adb push <backup file location> /sdcard
adb shell
su
rm data/system/users/0/settings_ssaid.xml
cp /sdcard/settings_ssaid.xml /data/system/users/0/
chmod 600 data/system/users/0/settings_ssaid.xml
I don't know why it's affecting your boot though, there's a .fallback file that the system should fall back to when the system notes that this file is corrupt.
If the above doesn't work, and you could try:
Code:
adb shell
su
rm data/system/users/0/settings_ssaid.xml
cp /data/system/users/0/settings_ssaid.xml.fallback /data/system/users/0/settings_ssaid.xml
If that doesn't work, try:
Code:
adb shell
su
rm data/system/users/0/settings_ssaid.xml
And reboot, but again, I don't know why you're bootlooping from this, that file shouldn't be integral to booting.
Also, if you need to back up your data, why not just boot to boot_b, if it's not causing you issues? You really shouldn't have to reset your device to fix one problem - you could do a /data & /sdcard pull while booted to boot_b, or just run something like Titanium & SMS backup/restore.
Click to expand...
Click to collapse
I appreciate the help but I can't go back as I've already wiped everything minutes before you sent this. If I had the above commands sooner I would have loved to try, although I'm not really sure why this became an issue in the first place. I tried booting to slot B, using both patched and normal boot images but it wasn't working, unless I did something wrong.
All I remember is installing an app to edit UDID for individual apps that I've used in the past, but because it wasn't identifying root properly, to which I'm assuming is an Android 12 issue, I decided to follow instructions for manually editing such IDs in the file I edited in my OP.
After I rebooted, I remember the main system about to start and seeing the Google boot logo with a percentage # go all the way up to 90%, then that's where the boot loop started. My guess at this point is either the app or the file I edited caused an issue, because I did nothing else up until that point. What's odd, is that after I formatted the whole system and rebooted, I saw the same percentage appear on screen after installing the same app to see if that was the issue, but it booted fully just fine.
I was going to just keep fighting this and keep the phone the way it was until I could maybe fix everything, but figured there's nothing I could do at this point since trying a flash of everything failed. I was up until 5am last night and it's almost 4 am with me trying to fix this. I feel defeated and upset because I don't believe I had to wipe this in the first place, and could have likely saved all of my data. I didn't have Google's backup option turned on and hadn't backed up my text messages because I was dumb. I'm more upset with myself than the phone honestly.
RetroTech07 said:
I appreciate the help but I can't go back as I've already wiped everything minutes before you sent this. If I had the above commands sooner I would have loved to try, although I'm not really sure why this became an issue in the first place. I tried booting to slot B, using both patched and normal boot images but it wasn't working, unless I did something wrong.
All I remember is installing an app to edit UDID for individual apps that I've used in the past, but because it wasn't identifying root properly, to which I'm assuming is an Android 12 issue, I decided to follow instructions for manually editing such IDs in the file I edited in my OP.
After I rebooted, I remember the main system about to start and seeing the Google boot logo with a percentage # go all the way up to 90%, then that's where the boot loop started. My guess at this point is either the app or the file I edited caused an issue, because I did nothing else up until that point. What's odd, is that after I formatted the whole system and rebooted, I saw the same percentage appear on screen after installing the same app to see if that was the issue, but it booted fully just fine.
I was going to just keep fighting this and keep the phone the way it was until I could maybe fix everything, but figured there's nothing I could do at this point since trying a flash of everything failed. I was up until 5am last night and it's almost 4 am with me trying to fix this. I feel defeated and upset because I don't believe I had to wipe this in the first place, and could have likely saved all of my data. I didn't have Google's backup option turned on and hadn't backed up my text messages because I was dumb. I'm more upset with myself than the phone honestly.
Click to expand...
Click to collapse
Ah damn, I was too late!
The 90% thing sounds like the November Google Play services updated - mine updated yesterday and I got the same thing when I rebooted, maybe something between the two got corrupt.
Yeah, I get that, I've had more than my fair share of self inflicted (and not so self inflicted) problems that have lost me data but you live and you learn I suppose