[Q] Android won't boot after modifying system file - Android Q&A, Help & Troubleshooting

This is (nearly) my first post, so hi all !
Before I start with anything else: I searched a lot and found a lot of things, but I'm so newbie that I'm afraid to do anything because I don't quite understand what I'm about to do.
Oh, and I don't speak english natively so forgive me if I make any horrific mistakes :angel:
With all that said, let's begin with my problem...
I have a HUAWEI Y300-0100, and it comes with a funny feature: every time it can't connect to WIFI a popup message appears saying that if you switch to data plan charges may apply.
I am constantly switching between WIFI/no-WIFI zones so that message really bothered me, and I searched a way to disable it.
Presumably, the only way to do that is by modifying a system file called "build.prop". I already had my phone rooted so doing so wasn't very hard.
I used Jota+ to change a setting from "true" to "false" (ro.config.hw******), and saved the file in the root of the SD card. Then, with ES File Explorer, I renamed the "build.prop" in /system to "build.prop.bak" and copied there the "build.prop" I previously saved in the SD root.
All seemed to be fine, except that after rebooting my phone it could not get past the HUAWEI logo.
Android recovery mode seems to work, but I don't know how to use a lot of its options nor I want to do a Factory Reset if there's a better alternative.
Is there a way to modify system files before booting Android? I really would like to try to delete the "build.prop" file and rename the "build.prop.bak" back to "build.prop".
Does any of that make any sense? What do you recommend me to do?
Thank you very much for your help!

From within recovery open adb
adb pull /system/build.prop /some/location/on/PC
Now edit build.prop back to how it was
adb push build.prop /system
adb reboot
Sent from my Nexus 4 using Tapatalk 2

demkantor said:
From within recovery open adb
adb pull /system/build.prop /some/location/on/PC
Now edit build.prop back to how it was
adb push build.prop /system
adb reboot
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Thank you for your response!
I managed to restore the original build.prop, but the phone still doesn't boot.
..Maybe that wasn't the problem. I guess I'll factory reset...
--------------------------
After that it STILL doesn't boot. I have no idea what happened, I did nothing strange apart from editing that file :crying:

If you changed something in /system factory reset won't work
Try either fixing permissions in recovery or
adb chmod 644 /system/build.prop
Sent from my Nexus 4 using Tapatalk 2

demkantor said:
If you changed something in /system factory reset won't work
Try either fixing permissions in recovery or
adb chmod 644 /system/build.prop
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Nothing fixes it... I give up.

Next time be sure to make a backup before you modify
For now wipe clean and install a new ROM or return to stock
Sent from my Nexus 4 using Tapatalk 2

Install a new rom
Sent from my GT-I9100G using xda app-developers app

Related

[Q] Trying to replace a system apk

Hi,
I'm attempting to replace Email.apk on my miui rom. This is the method I am using:
Code:
adb push Email.apk /sdcard/
adb shell
su
rm /system/app/Email.apk
rm /system/app/Email.odex
mount -o rw,remount /dev/block/mmcblk0p9 /system
cp /sdcard/Email.apk /system/app
reboot
When the phone has rebooted, my changes do not take affect. To check, I pulled the /system/app/Email.apk back, and found it to be the original version.
Can anyone tell me what I'm doing wrong here?
Thanks,
Have figured this out...
adb appears to send some kind of cached version over. Renaming the file before transferring forced adb to use the correct file, and all is well.
jimhaddon said:
Have figured this out...
adb appears to send some kind of cached version over. Renaming the file before transferring forced adb to use the correct file, and all is well.
Click to expand...
Click to collapse
How? I like to know too, guide step by step....thanks
You mean renaming the original file first to any name then copy the moded file with the original name ?
If that what u mean , so I better to delete the original one first then but enstead my moded file . Is that right ?
Sent from my GT-I9100 using XDA App
Just use something like root explorer, no need for adb...
Joey2o11 said:
Just use something like root explorer, no need for adb...
Click to expand...
Click to collapse
I tried to use root explorer to change phone.apk, it didnt work.. i changed the file but it kept on crashing all the time ...
Sent from my GT-I9100 using XDA App
hielo_te said:
I tried to use root explorer to change phone.apk, it didnt work.. i changed the file but it kept on crashing all the time ...
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
You'll get lots of FCs until you reboot the phone then it should be fine.

Asus boot logo after Wipe no Launcher :(

Hi all,
happened to me a mishap.
I had done a full wipe but forgot to push the stock launcher back on it, well now the launcher is missing and I can not do anything.
Would have otherwise update the Asus HC recorded but do not know how that should go without Launcher
Who has an advice what I could do?
sorry, trying to understand...
Had you done some sort of modification that removed the stock launcher? There isn't any reason why the stock launcher wouldn't be present. Can you try another factory reset using vol up + power? i don't recall exactly what the sequence is.
Its ok,
my english is not the best.
I delete the stock launcher with a script and forgot to restore it.
And then i do a factory resett..........
No Launcher anymore.........
A Androiddevice without an launcher become a bootloop or something similar
Did you uninstall the APK "launcher2.apk" and it's odex "launcher2.odex"?
I made that mistake and what i had to do was use ADB to install a 3rd party launcher (I found an APK for launcher pro and used that) and then once I had a working launcher, I downloaded Root explorer (I was rooted) and moved the "Launcher2.apk" and "launcher2.odex" into the /system/app folder. From there, I rebooted and everything was gravy
It is essential to include both the .apk and the .odex. Also, you have to have the files from the same build version you are. (You can't use an odex from 8.8.3.29 on a tablet running 8.8.3.33)
does ADB see your device? If so maybe you can push launcher API back to /system/app then set the permissions and you should be all set.
Sent from my Transformer Prime TF201 using xda premium
bscotth said:
Did you uninstall the APK "launcher2.apk" and it's odex "launcher2.odex"?
I made that mistake and what i had to do was use ADB to install a 3rd party launcher (I found an APK for launcher pro and used that) and then once I had a working launcher, I downloaded Root explorer (I was rooted) and moved the "Launcher2.apk" and "launcher2.odex" into the /system/app folder. From there, I rebooted and everything was gravy
It is essential to include both the .apk and the .odex. Also, you have to have the files from the same build version you are. (You can't use an odex from 8.8.3.29 on a tablet running 8.8.3.33)
Click to expand...
Click to collapse
Yes i uninstall the launcher2_apk and odex file.
ADB dont see my device.
I think its a mistake in the USB driver.
I pluged the prime in and MTP doesnt install correctly.
cooper1988 said:
Hi all,
happened to me a mishap.
I had done a full wipe but forgot to push the stock launcher back on it, well now the launcher is missing and I can not do anything.
Would have otherwise update the Asus HC recorded but do not know how that should go without Launcher
Who has an advice what I could do?
Click to expand...
Click to collapse
cooper1988, what you have to do is download a new launcher in your pc, put it in your sd card and apply it with the recovery mode in "apply any zip from sd".
ajmdve said:
cooper1988, what you have to do is download a new launcher in your pc, put it in your sd card and apply it with the recovery mode in "apply any zip from sd".
Click to expand...
Click to collapse
prime doesnt have a recovery (locked bootloader)
Power + Vol D --> Wipe or boot Android
well, then you might try flashing a new rom. sorry but if your pad doesnt have recovery, the it is the only way i see.
ajmdve said:
well, then you might try flashing a new rom. sorry but if your pad doesnt have recovery, the it is the only way i see.
Click to expand...
Click to collapse
won't it try to flash whatever image is on the sd card with that combo, effectively a hard reset?
Year
ADB show my device.
But i cant push the apk to /system/app or /data/app
failed to copy 'launcher.apk' to '/data/app/launcher.apk': Permission denied
a hard reset is not useful in this case because the launcher in not in the system folder anymore. he have to flash the pad with odin or any other method alike.
cooper1988 said:
Year
ADB show my device.
But i cant push the apk to /system/app or /data/app
failed to copy 'launcher.apk' to '/data/app/launcher.apk': Permission denied
Click to expand...
Click to collapse
I believe you have to mount /system in order to do that push
c:\android-sdk\platform-tools>adb shell mount /system
mount: permission denied
i dont have root on the prime and nachoroot doesnt work ( i have hc)
c:\android-sdk\platform-tools>adb push nachoroot.bin /data/local/
1140 KB/s (15182 bytes in 0.013s)
c:\android-sdk\platform-tools>adb shell chmod 777 /data/local/nachoroot.bin
chmod: permission denied
a hard reset wont do anything
tdrussell said:
won't it try to flash whatever image is on the sd card with that combo, effectively a hard reset?
Click to expand...
Click to collapse
a hard reset wont do anything, because it restores all by default, but, if the launcher isn't in the system folder, the phone wont make it appear from nowhere.
he should flash a new rom using odin or some other tools alike.
I am in a similar situation I am stuck in a boot loop! Not able to get passed the asus logo loading sign!
I can not get in ADB because of dumb asus sync I still need to try using ADB on linux! Because that does not need the asus sync
Sent from my PC36100 using Tapatalk
how it happens?
Wordlywisewiz said:
I am in a similar situation I am stuck in a boot loop! Not able to get passed the asus logo loading sign!
I can not get in ADB because of dumb asus sync I still need to try using ADB on linux! Because that does not need the asus sync
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
how it happens?
ajmdve said:
how it happens?
Click to expand...
Click to collapse
Well idrk either the system apps I froze or the changing the build.prop (added enable. Facelock) but even after I had done that I had rebooted Atleast twice
But maybe it only checks those things on a kernel panic
Sent from my PC36100 using Tapatalk
you rebooted twice and it starts completelly or it always get stuck in the boot logo?
cooper1988 said:
c:\android-sdk\platform-tools>adb shell mount /system
mount: permission denied
i dont have root on the prime and nachoroot doesnt work ( i have hc)
c:\android-sdk\platform-tools>adb push nachoroot.bin /data/local/
1140 KB/s (15182 bytes in 0.013s)
c:\android-sdk\platform-tools>adb shell chmod 777 /data/local/nachoroot.bin
chmod: permission denied
Click to expand...
Click to collapse
before you did factory reset , u removed the launch apk right ? so you had root before you did factory reset , you should still have it now , because factory wipe does not remove root.

Replacing SystemUI.apk in ADB

So I flashed the wrong .zip and now SystemUI.apk is force-closing. Rather than reflash the ROM I'm just going to replace SystemUI.apk using adb (I happen to have the ROM unzipped on my laptop), but want to make sure I have the procedure right.
Reboot to recovery
Then
adb shell
su
rm system/app/SystemUI.apk
exit
And then to push the SystemUI.apk
just
adb push SystemUI.apk system/app/SystemUI.apk
reboot
Do I need to mount system as writable before all of this?
Yes I believe you do
You could put the system.apk into a flashable zip by itself and flash that tho
Less room for error
Sent from my ADR6425LVW using Tapatalk 2
superchilpil said:
Yes I believe you do
You could put the system.apk into a flashable zip by itself and flash that tho
Less room for error
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Thanks.
Now I'm wondering if the permissions will be all mucked up if I just push the file. Is there a way to set permissions in adb?
never mind, got it, chmod 644 system/app/SystemUI.apk
Worked too!
tekhna said:
Thanks.
Now I'm wondering if the permissions will be all mucked up if I just push the file. Is there a way to set permissions in adb?
Click to expand...
Click to collapse
There is, I can't remember the command off the top of my head
Sent from my ADR6425LVW using Tapatalk 2
Adb remount will mount as rrw and you don't have to set permissions the folder already has it. You can also just use a root file explorer app to place it in their
Sent from my ADR6425LVW using XDA
tekhna said:
So I flashed the wrong .zip and now SystemUI.apk is force-closing. Rather than reflash the ROM I'm just going to replace SystemUI.apk using adb (I happen to have the ROM unzipped on my laptop), but want to make sure I have the procedure right.
Reboot to recovery
Then
adb shell
su
rm system/app/SystemUI.apk
exit
And then to push the SystemUI.apk
just
adb push SystemUI.apk system/app/SystemUI.apk
reboot
Do I need to mount system as writable before all of this?
Click to expand...
Click to collapse
hi, i have the same problem. i flashed the wrong zip from here http://forum.xda-developers.com/showthread.php?t=2526039&page=2 and now when i put the usb cable into the pc to backup from nexus root toolkit, it says that driver are not installed, and when i make the test for the drivers systemui crash. so i cant go back to stock rom or restore backup. any ideas? please help me

[Q] SGPT12, modified build.prop, won't boot anymore!

hi,
I still have adb access,
already tried to adb-push of the original build.prop backup back in place, it is actually uploaded, but won't boot anyway.
backup done by build.prop editor, and file pop and push from a linux machine (so no CRLF thing for sure).
attaching snapshot of logcat.txt
... *HELP*
thank you
the problem was in the file permissions. i had to remove write permissions to the group. (rw-r--r--)
You can fix permissions using adb
Sent from my GT-S5830 using xda premium
the.fuzzy.guy said:
hi,
I still have adb access,
already tried to adb-push of the original build.prop backup back in place, it is actually uploaded, but won't boot anyway.
backup done by build.prop editor, and file pop and push from a linux machine (so no CRLF thing for sure).
attaching snapshot of logcat.txt
... *HELP*
thank you
Click to expand...
Click to collapse
First of all DO NOT WIPE DATA / FACTORY RESET
This will remove adb access. Depending how far you can boot, do you get adb in recovery or normal. Can you use adb shell? If you can you can us adb shell chmod 644 /system/build.prop
EDIT:
Failing that try to install a zip. Sell my links for both current and older zips

URGENT: Build.prop deleting itself after each reboot

got an urgent and important question.. please urgent help required.!!!
I edited something in build.prop and restarted. phone goes blank after boot. Tried adb.. [build.prop not found] restored a backup of build.prop into system via adb but after reboot, same thing again and adb shows [build.prop not found again]..!! Can anyone help..?? Also didn't make nandroid backup..
Is there anyway to get the phone running again without losing any data..??
URGENT..!!
Are you either hitting fix permissions in recovery or using adb to chmod the build.prop after pushing it? If not this will happen.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Categories

Resources