Related
As you may know, some Android games especially most Gameloft games are not compatible with the Kindle Fire. So in efforts to find a way to make certain Gameloft games to work such as Modern Combat 2 and Shrek Kart and others, I resorted to editing my build.prop in the systems folder to make my device compatible with the apps. So I copied the original build.prop file, renamed it, and saved it to my SD Card folder. I took the copy I made and I then replaced it with the build.prop from HTC Glacier. (I never knew what could possibly happen) So then to apply those settings you have to reboot the device. I rebooted the Kindle and now it won't boot up. It get's to the Kindle Fire screen when booting up but after several seconds it just shows a black screen. No physical damage has been incurred to it but I feel like my stupid mistake of modding the build.prop resulted in the Kindle Fire unable to boot up correctly. It also isn't recognized by the PC when I hook it up to a USB cable. So far I've found nothing that could help to solve this. I've seen a Factory Default Settings Cable which is a special cable to reverts the device to its factory default settings but I'm not too sure if that would work. I'm in desperate need of help as in I use my Kindle Fire for everyday work and play. Thanks.
EDIT: I've tried adb push and renaming and moving the build.prop into the /system/ but returns that it is a Read-File System Only. Also adb shell and su doesn't work as in it ends up with segmentation fault. I've tried to zergRush root it and permanently root it using KFU but it ends up with 'Cannot Access Package Manager. Is System running?' Also the mount -o rw,remount.....command doesn't work either as it says Permission Denied. All of this would be easy to accomplish if only it ADB allowed me to write onto the /system file.
EDIT**: The biggest issue I'm faced with is the permission settings that prevent my from editing anything. You cannot simply change it from RO to RW because apparently the ADB is not rooted. And I also can't root it because problems exist when accessing either Package Manager or Activity Manager. What I need is a way to access the /system files without a root (non-rooted). Either that or enable fastboot because I cannot access that either. On a reply on the second page is the resulting lines when changing bootmodes on the KFU.
Don't know how to fix your problem, but just wondering, did you just completely replace the kindle fire build.prop with the HTC glacier? Because you can't do that, it will, as you have learned, mess up your device.. Your supposed to edit the build.prop and just change a few things. Next time read up on the subject before deciding to mod the device you use everyday...
the cable you'r talking about is a "factory cable" it forces the kf to fastboot mode - it don't restore any settings !
you need fastboot mode to install fff (firefirefire - custom bootloader) and twrp (recovery)
do you allready have installed fff & twrp (or cwm) ?
if you have twrp installed and booted into then you have adb command available and can copy back the original build.prop
Did you remember to restore the read/write permissions to build.prop? It should be set to 644.
As already stated, your not supposed to replace the whole file, build.prop tells android which device you have, so now Android thought and configured itself to different hardware config. which is not available to it. Adb seems like the only option.
I should have really looked more into it before modifying the build.prop. I replaced the ENTIRE build prop with the build.prop of HTC Glacer. (I know, i know I was stupid) And referring to the factory cable, I don't think I'll resort to that: too time consuming. In regards to the last person that posted before me who said that my only option was ADB could you elaborate? Thanks for all your feedback.
gococogo321 said:
I should have really looked more into it before modifying the build.prop. I replaced the ENTIRE build prop with the build.prop of HTC Glacer. (I know, i know I was stupid) And referring to the factory cable, I don't think I'll resort to that: too time consuming. In regards to the last person that posted before me who said that my only option was ADB could you elaborate? Thanks for all your feedback.
Click to expand...
Click to collapse
Your going to have to use adb to basically remove the HTC Glacier build.prop and replace it with the original build.prop.
For example:
Adb remount <- allows you to mount system as rw
Adb pull /path-to-original/build.prop
Adb push build.prop /system
Adb shell chmod 644 /system/build.prop <- sets permissions to rwrr
Adb reboot
Sent from my Kindle Fire using xda premium
You dont have access to recovery? Either TWRP or CWM?
daggy1985 said:
Your going to have to use adb to basically remove the HTC Glacier build.prop and replace it with the original build.prop.
For example:
Adb remount <- allows you to mount system as rw
Adb pull /path-to-original/build.prop
Adb push build.prop /system
Adb shell chmod 644 /system/build.prop <- sets permissions to rwrr
Adb reboot
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
I tried doing that but it says something like Access Denied or Read-Only File System when i try to push the build.prop into it.
gococogo321 said:
I tried doing that but it says something like Access Denied or Read-Only File System when i try to push the build.prop into it.
Click to expand...
Click to collapse
Did you use the 'adb remount' command? Sometimes, when attempting to push a file to the system, I get the 'read-only file system' and I have to issue adb reboot followed by adb remount and then push the file again. It seems after a time the mount system as read write automatically goes back to read-only.
Sent from my ADR6400L using xda premium
Have you got TWRP or ClockworkMod?
Because you could flash a new rom then.
abd - root mode
Perhaps, running adb in root mode will
allow you to push the original build.prop
back. Then execute "adb remount / rw" to mount the
root directory as read/write. Hopefully you will be able to push
it then follow daggy1985's instructions.
* In Win 7, type "cmd " at the 'SEARCH/RUN' and hold
shift + ctrl while hitting 'Enter' to put yourself
in Admin mode which apparently makes adb work in root mode when you launch it.
* Xda-dev is the coolest site for Android that I have seen. Kudo's to everyone participating.
sum1nil said:
Perhaps, running adb in root mode will
allow you to push the original build.prop
back. Then execute "adb remount / rw" to mount the
root directory as read/write. Hopefully you will be able to push
it then follow daggy1985's instructions.
* In Win 7, type "cmd " at the 'SEARCH/RUN' and hold
shift + ctrl while hitting 'Enter' to put yourself
in Admin mode which apparently makes adb work in root mode when you launch it.
* Xda-dev is the coolest site for Android that I have seen. Kudo's to everyone participating.
Click to expand...
Click to collapse
Thanks but I have actually been running it from Administrator from the very beginning. I've used Kindle Fire Utility KFU and it says that ADB Server is Online and my Bootmode is 4000 but it says ADB root: No. And whenever I choose any bootmode whether it be Normal, Fastboot, or Recovery, it always shows this:
***********************************************
* Activating Normal (4000) *
***********************************************
Installing BurritoRoot, Courtesy of Jcase of TeamAndIRC!
1393 KB/s (1164225 bytes in 0.816s)
Error: Could not access the Package Manager. Is the system running?
Activating BurritoRoot...
Error type 2
android.util.AndroidException: Can't connect to activity manager; is the system
running?
Elevating the Shell...
* daemon not running. starting it now *
* daemon started successfully *
/data/local/tmp/BurritoRoot3.bin: permission denied
mount: Operation not permitted
mount: Operation not permitted
failed to copy 'files\rbfb' to '/system//rbfb': Read-only file system
Unable to chmod /system/rbfb: No such file or directory
Unable to chmod /system/rbfb: No such file or directory
mount: Operation not permitted
mount: Operation not permitted
***********************************************
* Root Activated *
***********************************************
The kindle is successfully running in root mode.
<idme> Invalid permission
reboot: Operation not permitted
Same goes for the Temp Burrito Root and installing FFF and TWRP. It always shows something about cannot access Package manager. I have no clue what the Package Manager even does but apparently I cannot find a solution to that.
I think you need to get a factory programming cable like we talked about on gtalk. I'm confident that will fix this.
Sent from my DROIDX using Tapatalk
I used android commander for windows, mounted system in TWRP and used android commander to copy a new working build.prop to the right place.
With a cable from my htc desire.
would make a little test:
issue "adb shell"
if you get a error message your up to a factory cable because the system shell is messed up and you have no possibility to get to fastboot mode to install fff & twrp
if you get a $ or # prompt you can resume and try "mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system" to mount system in read/write mode
daggy1985 said:
Your going to have to use adb to basically remove the HTC Glacier build.prop and replace it with the original build.prop.
For example:
Adb remount <- allows you to mount system as rw
Adb pull /path-to-original/build.prop
Adb push build.prop /system
Adb shell chmod 644 /system/build.prop <- sets permissions to rwrr
Adb reboot
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
hey, I've tried to remount my rooted galaxy y, fall in for same problem.but there show this message; "remount failed: Operation not permitted"
my device's usb debugging mode was off in last entire.
what I have to do now?
how did u edit build.prop in the first place if u don't have root and this might help
http://yaseminavcular.blogspot.com/2012/01/how-to-get-bricked-kindle-fire-back-to.html?m=1
Sent from my R800i using Tapatalk
Hi ,
I wanted to modify the build.prop on my nexus4 , and i requested r/w permissions , i was using es file explorer, and the only way to do this , was to remount the partition from R/O to R/W , then it let me modify the file , and change permissions on that file, but i forgot to re-mount the partition as R/O before rebooting my phone. now it wont boot up , and i dont know how to change the permissions back to R/O , or how to fix this issue.
Hope this makes any sense. Thanks
Ikran said:
Hi ,
I wanted to modify the build.prop on my nexus4 , and i requested r/w permissions , i was using es file explorer, and the only way to do this , was to remount the partition from R/O to R/W , then it let me modify the file , and change permissions on that file, but i forgot to re-mount the partition as R/O before rebooting my phone. now it wont boot up , and i dont know how to change the permissions back to R/O , or how to fix this issue.
Hope this makes any sense. Thanks
Click to expand...
Click to collapse
All the mount point are reset upon reboot, so it won't be affecting your system or whatsoever. However, the problem seems due to permission of your build.prop or it could be the settings that you added to the build.prop
If you have custom recovery installed, try Fix permissions. If it doesn't work, you can either re-flash the ROM or use adb to push back original build.prop into /system.
ksilver89 said:
All the mount point are reset upon reboot, so it won't be affecting your system or whatsoever. However, the problem seems due to permission of your build.prop or it could be the settings that you added to the build.prop
If you have custom recovery installed, try Fix permissions. If it doesn't work, you can either re-flash the ROM or use adb to push back original build.prop into /system.
Click to expand...
Click to collapse
i replaced( overwrite) the modified build.prop that i had on the phone with the original build.prop file, then rebooted the phone. and now it wont start up at all. i have a custom recovery from the nexus tool kit ( i think its cwm) . but that one works only if i can connect my phone to the pc , then boot in recovery mode, which i cant, since the phone wont start now. only recovery that i have now is that with a dead droid, which i can bypass and after that i got 4 options reboot , wipe or format, install files abd something and another option. i would gladly reflash my phone if you can tell me how
What modifications have you done to the build.prop?
Sent from my Nexus 4 using Tapatalk 4
Ikran said:
i replaced( overwrite) the modified build.prop that i had on the phone with the original build.prop file, then rebooted the phone. and now it wont start up at all. i have a custom recovery from the nexus tool kit ( i think its cwm) . but that one works only if i can connect my phone to the pc , then boot in recovery mode, which i cant, since the phone wont start now. only recovery that i have now is that with a dead droid, which i can bypass and after that i got 4 options reboot , wipe or format, install files abd something and another option. i would gladly reflash my phone if you can tell me how
Click to expand...
Click to collapse
No fix can be done without a PC now, unless you have a nandroid backup (clearly you don't have it right now).
Hold vol down + power key to enter bootloader mode. Connect the phone to your PC.
1. If your bootloader is locked, unlock the bootloader.
Code:
fastboot oem unlock
This is important, if you don't format the cache, all your data will be wiped upon reboot!
Code:
fastboot format cache
2. Download & flash cwm or twrp. Boot into recovery.
3. Use fix permissions.
OR
Mount system partition with the recovery interface. Then run this adb command on your PC.
Code:
adb shell chmod 644 /system/build.prop
adb reboot
andyabc said:
What modifications have you done to the build.prop?
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
i had this line there qemu.hw.mainkeys=1 , but i replaced the build.prop which had this line in, with the original build.prop, rebooted the phone , and now it wont boot up ( as i said, in doing this i have mounted the system partition from ES File Explorer from R/O to R/W, and forgot to turn them back to R/O before reboot) so my guess is that this happened because i didnt remounted back the partition with R/O permissions
Ikran said:
i had this line there qemu.hw.mainkeys=1 , but i replaced the build.prop which had this line in, with the original build.prop, rebooted the phone , and now it wont boot up ( as i said, in doing this i have mounted the system partition from ES File Explorer from R/O to R/W, and forgot to turn them back to R/O before reboot) so my guess is that this happened because i didnt remounted back the partition with R/O permissions
Click to expand...
Click to collapse
You don't really need that since you already have softkeys anyway.
The remount is not the case at all, the issue is either the permissions or the property itself.
Which recovery do you have?, if you have TWRP then you can fix it for sure with it's special feature.
Sent from my Nexus 4 using Tapatalk 4
occupied icinme
andyabc said:
You don't really need that since you already have softkeys anyway.
The remount is not the case at all, the issue is either the permissions or the property itself.
Which recovery do you have?, if you have TWRP then you can fix it for sure with it's special feature.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
i think i have twrp but i could boot into it only when the phone was connected to the pc and from the nexus 4 tool kit
Ikran said:
i think i have twrp but i could boot into it only when the phone was connected to the pc and from the nexus 4 tool kit
Click to expand...
Click to collapse
Then you are just booting to it (not flashed) but anyway one you get on there you have to TWRP, Advanced and then Terminal command.
Go to the system folder and type the following commands IF you have the backup:
rm build.prop
mv build.prop.bak build.prop
Sent from my Nexus 4 using Tapatalk 4
ksilver89 said:
No fix can be done without a PC now, unless you have a nandroid backup (clearly you don't have it right now).
Hold vol down + power key to enter bootloader mode. Connect the phone to your PC.
1. If your bootloader is locked, unlock the bootloader.
Code:
fastboot oem unlock
This is important, if you don't format the cache, all your data will be wiped upon reboot!
Code:
fastboot format cache
2. Download & flash cwm or twrp. Boot into recovery.
3. Use fix permissions.
OR
Mount system partition with the recovery interface. Then run this adb command on your PC.
Code:
adb shell chmod 644 /system/build.prop
adb reboot
Click to expand...
Click to collapse
but how can i run these commands since my phone wont boot up so i can connect it to my pc ? and my bootloader is unlocked + rooted nexus
Ikran said:
but how can i run these commands since my phone wont boot up so i can connect it to my pc ? and my bootloader is unlocked + rooted nexus
Click to expand...
Click to collapse
Go to the bootloader, it has Fastboot from there.
EDIT: Oh you where talking about ADB, try using the method I posted on the previous page.
Sent from my Nexus 4 using Tapatalk 4
Ikran said:
but how can i run these commands since my phone wont boot up so i can connect it to my pc ? and my bootloader is unlocked + rooted nexus
Click to expand...
Click to collapse
From my understanding, this is your current situation and phone setup, correct me if I'm wrong.
Bootloader: Booted
Recovery: Stock/Original
ROM: Running, but now Bootloop <-- You are here.
Now, because it is now in the "ROM" states, the animation continues to play on and on, you need to turn OFF your phone, just hold the power button for more than 8 secs until the screen goes off.
IF holding the power button doesn't work, hold VOLUME DOWN + POWER key for more than 8 secs instead.
IF your phone already turned off, you can skip this step.
After you power down your phone, hold VOLUME DOWN + POWER key, your phone will enter "Bootloader" mode.
Bootloader: Fastboot <--- You are here.
Recovery: Stock/Original
ROM: Not Running
Now you can connect your phone to your PC with USB cables. Go to android-sdk\platform-tools folder, hold Shift + Right click and select Open command window here, enter this command:
Code:
fastboot devices
IF you don't see your device in the list, your PC will need "driver" to communicate with your phone, download it here: http://developer.android.com/sdk/win-usb.html
Open Device Manager, update the driver.
There, you need to get a custom recovery, get either TWRP or CWM, because you need them to run the SHELL command. Get them installed and boot into recovery.
Bootloader: Booted to recovery
Recovery: CWM/TWRP <--- You are here.
ROM: Not Running
In the command window, now type "adb shell" and enter.
Try the command posted by andyabc, reboot.
ksilver89 said:
From my understanding, this is your current situation and phone setup, correct me if I'm wrong.
Bootloader: Booted
Recovery: Stock/Original
ROM: Running, but now Bootloop <-- You are here.
Now, because it is now in the "ROM" states, the animation continues to play on and on, you need to turn OFF your phone, just hold the power button for more than 8 secs until the screen goes off.
IF holding the power button doesn't work, hold VOLUME DOWN + POWER key for more than 8 secs instead.
IF your phone already turned off, you can skip this step.
After you power down your phone, hold VOLUME DOWN + POWER key, your phone will enter "Bootloader" mode.
Bootloader: Fastboot <--- You are here.
Recovery: Stock/Original
ROM: Not Running
Now you can connect your phone to your PC with USB cables. Go to android-sdk\platform-tools folder, hold Shift + Right click and select Open command window here, enter this command:
Code:
fastboot devices
IF you don't see your device in the list, your PC will need "driver" to communicate with your phone, download it here: http://developer.android.com/sdk/win-usb.html
Open Device Manager, update the driver.
There, you need to get a custom recovery, get either TWRP or CWM, because you need them to run the SHELL command. Get them installed and boot into recovery.
Bootloader: Booted to recovery
Recovery: CWM/TWRP <--- You are here.
ROM: Not Running
In the command window, now type "adb shell" and enter.
Try the command posted by andyabc, reboot.
Click to expand...
Click to collapse
In TWRP there is a Terminal Command menu where you can do commands from so you can do modification's to the OS.
Sent from my Nexus 4 using Tapatalk 4
It is worth mentioning that the command "fastboot oem unlock" will actually erase all the personal data (should also include sdcard folder) and make it a blank phone! Use with cautions!
andyabc said:
In TWRP there is a Terminal Command menu where you can do commands from so you can do modification's to the OS.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
so the phone when i turn it on, the logo from google appears and under that the unlocked lock , next, the 4 colored lines of nexus should appear . my phone doesnt gets to that, after the image of google disappears , its just a black screen , think is that bootloop you were saying.
BUT i managed to install cwm 6.0.3.5 on the phone and i am able to boot into recovery now . twrp wouldnt load for some reason, just frozen on the google logo when it was suppose to load .
so at this point i am here as you said:
Bootloader: Booted to recovery
Recovery: CWM/TWRP <--- You are here. ( cwm 6.0.3.5 )
ROM: Not Running
in cmd i did: adb devices >result:
C:\Program Files (x86)\WugFresh Development\data>adb devices
List of devices attached
00765833628b346b recovery
after that: adb shell > result :
C:\Program Files (x86)\WugFresh Development\data>adb shell
~ # adb shell chmod 644 /system/build.prop
adb shell chmod 644 /system/build.prop
/sbin/sh: adb: not found
~ # chmod 644 /system/build.prop
chmod 644 /system/build.prop
chmod: /system/build.prop: No such file or directory
~ # cd /system
cd /system
/system # chmod 644 build.prop
chmod 644 build.prop
chmod: build.prop: No such file or directory
/system # chmod 644 /system/build.prop
chmod 644 /system/build.prop
chmod: /system/build.prop: No such file or directory
/system # adb shell chmod 644 /system/build.prop
adb shell chmod 644 /system/build.prop
/sbin/sh: adb: not found
Ikran said:
after that: adb shell > result :
C:\Program Files (x86)\WugFresh Development\data>adb shell
~ # adb shell chmod 644 /system/build.prop
adb shell chmod 644 /system/build.prop
/sbin/sh: adb: not found
~ # chmod 644 /system/build.prop
chmod 644 /system/build.prop
chmod: /system/build.prop: No such file or directory
~ # cd /system
cd /system
/system # chmod 644 build.prop
chmod 644 build.prop
chmod: build.prop: No such file or directory
/system # chmod 644 /system/build.prop
chmod 644 /system/build.prop
chmod: /system/build.prop: No such file or directory
/system # adb shell chmod 644 /system/build.prop
adb shell chmod 644 /system/build.prop
/sbin/sh: adb: not found
Click to expand...
Click to collapse
Great, you're almost there. Now in the CWM, there is a menu item called "Mount and storage", you need to mount /system partition in order for the command to work.
Tips: If you already run "adb shell", you are already "inside" the shell, so you don't need to type "adb" anymore. Notice the #? Just use chmod directly.
Tips 2: If you successfully corrected the permission but it didn't work, you will have to replace the build.prop with your original one.
ksilver89 said:
Great, you're almost there. Now in the CWM, there is a menu item called "Mount and storage", you need to mount /system partition in order for the command to work.
Tips: If you already run "adb shell", you are already "inside" the shell, so you don't need to type "adb" anymore. Notice the #? Just use chmod directly.
Tips 2: If you successfully corrected the permission but it didn't work, you will have to replace the build.prop with your original one.
Click to expand...
Click to collapse
thanks it worked, i had to mount the /system partition for the shell command to work, the phone booted up now, and it works, but for some reason everything is wiped from the phone i had some backup , i will see if i can restore anything from it. if not c'est la vie.
Thanks again
Guys, I have a similar kind of issue,
After flashing a Custom ROM in my Nexus 4, my phone is stuck on a bootloop, \
I have tried flashing almost everything, but still the bootloop exists,
If someone is willing to help me,
Just reply to this my "Yes" and I shall elaborate my whole issue here,
Thank you.
Rockstar600 said:
Guys, I have a similar kind of issue,
After flashing a Custom ROM in my Nexus 4, my phone is stuck on a bootloop, \
I have tried flashing almost everything, but still the bootloop exists,
If someone is willing to help me,
Just reply to this my "Yes" and I shall elaborate my whole issue here,
Thank you.
Click to expand...
Click to collapse
Yes, maybe.
Nuu~ said:
Yes, maybe.
Click to expand...
Click to collapse
Okay,
Let me quote my problem,
I also posted it on MSkip's Toolkit thread,
I did search but wasn't able to find a proper solution,
I was on a 4.3, with latest TWRP installed,
I flashed a ROM that was 4.2.2 after I flashed the phone was not booting up, and was stuck on Google logo,
I did wipe in the TWRP and even re-installed the ROM, had the same issue again,
So, I thought to flash 4.2.2 Google Factory Image via this toolkit,
I downloaded the Factory Image from Google and placed it in the folder which says "Put factory image here"
Followed all the procedures, and flashed the 4.2.2 factory image in my phone,
Now the phone is stuck on the X logo,
I tried going into the stock recovery and did a factory reset, but again the same thing,
The phone isn't booting up,
Also one thing i noticed, while the phone is booting the "Google" logo stays around a minute, and then the X boot animation appears,
Any clue what to do??
I tried pushing the factory image via toolkit several times, but again I'm stuck at the same boot animation,
Please help me regarding this,
I'm at work, trying to search and find information as much as I can,
I can now boot on 4.2.2 but in settings the phone says that the base band is unknown, IMEI is gone,
And I cannot even see the internal storage when I connect my phone to PC.
Here is what I'm facing.
Also check this,
I got this error too, unable to post the image so posting the link http://imageshack.us/photo/my-images/9/jys1.jpg
{
"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"
}
If you need any other details, please just do ask me, I will try my best to answer you properly.
Thank you.
Not sure if this will help anyone else, but I searched forever trying to figure out how to write into the system folder using Terminal Emulator on the Note 3 to no avail. I found a slew of posts that said to type "mount -o rw,remount /system" to achieve this. When I used this command it didn't return any errors so I assumed it worked, however no files ended up being copied and pasted to the location I wanted. I found numerous other examples that were supposed to enable writing to the system as well, but none of them worked. I finally figured out how to get it to work on my Note 3 by typing "mount" in terminal emulator and noticing that at the very beginning of the string that was returned was "rootfs". So if you are wanting write to your system using Terminal Emulator on the VZW Note 3 here is what ended up working for me:
Code:
mount -o remount,rw rootfs
to return to read only enter:
Code:
mount -o remount,ro rootfs
I wanted to figure this out because a bug in TWRP v2.6.3.0 maimed my efs partition and bricklooped my phone. Even flashing the Stock Developer tar by Beans wouldn't bring it out of the brickloop. I was able to get out of the brickloop by following this thread, but even though my phone booted up and the IMEI # was correct, my /efs folder was missing in action. This caused odd things to happen like my lock screen not functioning and the power button instantly turning the phone off instead of bringing up the power menu. I discovered this was because the phone was placed into something called "factory mode" and that to fix it you needed to edit some files in the efs folder, which were completely missing on my device. Member js0uth graciously sent me his efs folder from his Developer Note 3 and when I copied it to my phone it began to function normally again (big shout out to js0uth!). However, this folder was completely deleted once again after a reboot. So now you can see why I was looking for a way to copy these files using Terminal Emulator. I ended up making a Tasker profile with the Secure Settings plugin that automatically copies the files from my ext SD card to my system folder on boot of the device. In order to mount, copy/paste the files while retaining the correct permissions from the folder that js0uth sent me, and unmount the system I had the set up my Secure Settings command as follows:
Code:
mount -o remount,rw rootfs;cp -Rpf /storage/extSdCard/efs/* /efs/;mount -o remount,ro rootfs
So now I have a livable workaround for my problem until I can discover a way for the phone to rebuild my own /efs folder.
Edit: See radionerd's post for a permanent fix to this issue and be sure to hit thanks under his name if it helps you.
I did the same to my DE. Corrupted EFS about a month ago after a few flashes using TWRP 2.6.3.0. Boot loops for 28 hours of hell until I followed your tracks to the trick that deleted my corrupted EFS folder, and created a new empty folder. I guess this would wipe out IMEI, Mac, and more in models that store phone specific data in EFS. We lucked out I've read that our phones have that info in a few other folder not EFS
Since wiping EFS I have run stock ROM, CM11, and now bean V6. I didn't see the factory mode popup until recently. I noticed that the screen will flash when leaving or entering cell service.
My corrupted EFS was 3MB. I'm curious what's the size of the EFS folder from js0uth?
Were you able to enter the factory mode on string? something like this?
Code:
# echo -n ON > /efs/FactoryApp/factorymode
this is from an S3
Thanks for documenting your steps to recovery.
radionerd
radionerd said:
My corrupted EFS was 3MB. I'm curious what's the size of the EFS folder from js0uth?
Click to expand...
Click to collapse
It's 1.04 MB. Sorry for taking so long to respond. I thought I had it set up to send instant emails for replies to this thread, but apparently I didn't.
radionerd said:
Were you able to enter the factory mode on string? something like this?
Code:
# echo -n ON > /efs/FactoryApp/factorymode
this is from an S3
Click to expand...
Click to collapse
Setting the Factorymode folder to ON is actually what disables that mode. Seems backwards I know, but when it's set to OFF (or if the folder is completely missing as in my case) that warning message will display. If that folder is intact on your phone then you should be able to use a string to disable or enable Factorymode.
It got worse before it got better
bodieism said:
It's 1.04 MB. Sorry for taking so long to respond. I thought I had it set up to send instant emails for replies to this thread, but apparently I didn't.
No worries, I went from an annoyance of no lock screen to bricked for over 6 weeks. This happened after trying to do an EFS backup.
I've learned a lot since back then, My DE is back 100%, EFS is repaired. I think we ran the same script which actually points to the wrong mount in our phones. It brought us out of bootloops, but efs was pointed to block12. Qualcom snapdragon Note-3's use mmblk0p11 to load /efs.
If you still have to load the tasker script, I think I figured out an easy fix to rebuild your original efs folder.
I would backup mounts first, delete /efs folder. Then run the original script, but this time change from 12 to 11.
Code:
adb shell
su
mke2fs /dev/block/mmcblk0p11
mkdir /efs
mount -t ext4 /dev/block/mmcblk0p11 /efs
Bet that would do the trick
Here is my thread
Click to expand...
Click to collapse
^ That did do the trick! :good:
Phone is back to 100% working order :highfive:
Hello guys and gals,
my wife managed to break her screen on the SM-G900F Model from germany and she got her a new phone. The problem is now that she has some data on the phone she needs (like the google e-mail what she has forgotten the name of) and some other stuff. I want to enable usb debugging over recovery and mirror the screen on my pc (i did that once on my old Galaxy S3 Neo).
I was searching on this forums for a sollution to enable usb debugging over recovery https://forum.xda-developers.com/showthread.php?t=2697523.
I managed to flash the recovery, but adb still does not recognise the phone while in recovery mode. I am running out of options and i really need help of some dev to decompile the kernel, edit the init-rc, and to recompile the kernel, so i could flash it on the phone. I was looking at some guides, but i just don't get it how to do that
Click to expand...
Click to collapse
It would help if someone has some user friendly guide to do that, so i would try that on my own.
I hope there is someone who can help me.
Stock Rom version: G900FXXS1CPLV_G900FDBT1CPJ1_G900FXXU1CPJ1_HOME.tar.md5
Click to expand...
Click to collapse
Hi,
Why not using latest TWRP custom recovery instead of trying old/outdated and not officially supported CWM?
I have no problem with accessing to ADB from latest TWRP.
TomyVk said:
Hello guys and gals,
my wife managed to break her screen on the SM-G900F Model from germany and she got her a new phone. The problem is now that she has some data on the phone she needs (like the google e-mail what she has forgotten the name of) and some other stuff. I want to enable usb debugging over recovery and mirror the screen on my pc (i did that once on my old Galaxy S3 Neo).
I was searching on this forums for a sollution to enable usb debugging over recovery https://forum.xda-developers.com/showthread.php?t=2697523.
It would help if someone has some user friendly guide to do that, so i would try that on my own.
I hope there is someone who can help me.
Click to expand...
Click to collapse
Boot to TWRP recovery
Then enter these commands in a terminal/cmd window on pc
If you're not rooted leave out the su from below - think it should still work
Assuming you have Samsung USB drivers & adb setup on pc
Code:
adb shell
su
mount -o remount,rw /system
cd /
echo "persist.service.adb.enable=1" >> default.prop
echo "persist.service.debuggable=1" >> default.prop
echo "persist.sys.usb.config=mtp,adb" >> default.prop
echo "persist.service.adb.enable=1" >> /system/build.prop
echo "persist.service.debuggable=1" >> /system/build.prop
echo "persist.sys.usb.config=mtp,adb" >> /system/build.prop
This will enable adb but you still may face unauthorized as you get a prompt on phone screen to allow adb & to accept connection - you maybe able to manually send the rsa key but you will have to Google that if you face that problem - it will depend on Android version
ADB should be enabled in latest twrp recovery so pull the build.prop edit it then push it back setting correct permissions
However if you are simply copying files just enter twrp & you will be able to see all your phone files via USB connection on your pc
Obviously with Google email you would need to boot the phone so try the above to enable adb debugging in normal boot
TheFixItMan said:
Boot to TWRP recovery
Then enter these commands in a terminal/cmd window on pc
If you're not rooted leave out the su from below - think it should still work
Assuming you have Samsung USB drivers & adb setup on pc
Code:
adb shell
su
mount -o remount,rw /system
cd /
echo "persist.service.adb.enable=1" >> default.prop
echo "persist.service.debuggable=1" >> default.prop
echo "persist.sys.usb.config=mtp,adb" >> default.prop
echo "persist.service.adb.enable=1" >> /system/build.prop
echo "persist.service.debuggable=1" >> /system/build.prop
echo "persist.sys.usb.config=mtp,adb" >> /system/build.prop
This will enable adb but you still may face unauthorized as you get a prompt on phone screen to allow adb & to accept connection - you maybe able to manually send the rsa key but you will have to Google that if you face that problem - it will depend on Android version
ADB should be enabled in latest twrp recovery so pull the build.prop edit it then push it back setting correct permissions
However if you are simply copying files just enter twrp & you will be able to see all your phone files via USB connection on your pc
Obviously with Google email you would need to boot the phone so try the above to enable adb debugging in normal boot
Click to expand...
Click to collapse
Well, i have flashed the latest twrp recovery twrp-3.2.3-0-klte.img.tar over odin. It flashed without problems.
But the same problem persists, when i boot in to recovery mode adb does not recognise th phone in recovery mode.
When i type adb shell i just get a "error: device not found" from adb
I have installed the newest samsung drivers over Kies3.
TomyVk said:
Well, i have flashed the latest twrp recovery twrp-3.2.3-0-klte.img.tar over odin. It flashed without problems.
But the same problem persists, when i boot in to recovery mode adb does not recognise th phone in recovery mode.
When i type adb shell i just get a "error: device not found" from adb
I have installed the newest samsung drivers over Kies3.
Click to expand...
Click to collapse
How do you know twrp booted if you can't see the screen?
TWRP will have adb support so as long as twrp booted it will work
Once you have flashed twrp in odin you must boot into twrp as soon as the phone restarts for twrp to stick - if you switched the device off or the phone booted normally you will have to reflash twrp - if you can't see the screen that maybe an issue
TheFixItMan said:
How do you know twrp booted if you can't see the screen?
TWRP will have adb support so as long as twrp booted it will work
Once you have flashed twrp in odin you must boot into twrp as soon as the phone restarts for twrp to stick - if you switched the device off or the phone booted normally you will have to reflash twrp - if you can't see the screen that maybe an issue
Click to expand...
Click to collapse
Oh, that might be the problem. What do i have to do after the flashing to boot in to twrp?
The same key combination as for the recovery mode or something else, or do i just disable automatic reboot in odin?
TheFixItMan said:
How do you know twrp booted if you can't see the screen?
TWRP will have adb support so as long as twrp booted it will work
Once you have flashed twrp in odin you must boot into twrp as soon as the phone restarts for twrp to stick - if you switched the device off or the phone booted normally you will have to reflash twrp - if you can't see the screen that maybe an issue
Click to expand...
Click to collapse
TomyVk said:
Oh, that might be the problem. What do i have to do after the flashing to boot in to twrp?
The same key combination as for the recovery mode or something else, or do i just disable automatic reboot in odin?
Click to expand...
Click to collapse
As soon as the device restarts & the Samsung logo appears (that you can't see) hold Vol up home button & power button
Can try disabling auto restart then pull the battery after flash & then hold the button combo to start
TheFixItMan said:
As soon as the device restarts & the Samsung logo appears (that you can't see) hold Vol up home button & power button
Can try disabling auto restart then pull the battery after flash & then hold the button combo to start
Click to expand...
Click to collapse
Thank you, it worked. I will now try to enable the usb debugging
TheFixItMan said:
Boot to TWRP recovery
Then enter these commands in a terminal/cmd window on pc
If you're not rooted leave out the su from below - think it should still work
Assuming you have Samsung USB drivers & adb setup on pc
Code:
adb shell
su
mount -o remount,rw /system
cd /
echo "persist.service.adb.enable=1" >> default.prop
echo "persist.service.debuggable=1" >> default.prop
echo "persist.sys.usb.config=mtp,adb" >> default.prop
echo "persist.service.adb.enable=1" >> /system/build.prop
echo "persist.service.debuggable=1" >> /system/build.prop
echo "persist.sys.usb.config=mtp,adb" >> /system/build.prop
This will enable adb but you still may face unauthorized as you get a prompt on phone screen to allow adb & to accept connection - you maybe able to manually send the rsa key but you will have to Google that if you face that problem - it will depend on Android version
ADB should be enabled in latest twrp recovery so pull the build.prop edit it then push it back setting correct permissions
However if you are simply copying files just enter twrp & you will be able to see all your phone files via USB connection on your pc
Obviously with Google email you would need to boot the phone so try the above to enable adb debugging in normal boot
Click to expand...
Click to collapse
When i try to mount the system partition i just get this:
mount -o remount,rw /system
mount: can't find /system in /proc/mounts
TomyVk said:
When i try to mount the system partition i just get this:
mount -o remount,rw /system
mount: can't find /system in /proc/mounts
Click to expand...
Click to collapse
You might have a problem of when twrp starts it asks you to swipe to allow system modifications but you can't see that
See if are able to do an adb screen cast that allows you to control the screen via adb then you can fully get into twrp
Or see if you can simply pull the build.prop & default.prop to pc & edit it & push it back
TheFixItMan said:
You might have a problem of when twrp starts it asks you to swipe to allow system modifications but you can't see that
See if are able to do an adb screen cast that allows you to control the screen via adb then you can fully get into twrp
Or see if you can simply pull the build.prop & default.prop to pc & edit it & push it back
Click to expand...
Click to collapse
When i type ls in the shell i get this
Code:
ls
boot init.rc sdcard
cache init.recovery.hlthchrg.rc seapp_contexts
charger init.recovery.qcom.rc selinux_version
data init.recovery.service.rc sepolicy
default.prop init.recovery.usb.rc service_contexts
dev license sideload
efs modem sys
etc oem system
external_sd proc tmp
file_contexts property_contexts twres
file_contexts.bak recovery ueventd.qcom.rc
firmware res ueventd.rc
fstab.qcom root usbstorage
init sbin vendor
The system folder is empty tho. I have pulled the default.prop to my pc and pushed it back, created the build.prop and pushed it in to the system folder.
After i did that i typed exit and then adb reboot. Still no usb debugging. I checked the files again and the default.prop was back to the original, and the build.prop from the system folder was gone after the reboot. I don't know what i am doing wrong. I even have root access....
TomyVk said:
When i type ls in the shell i get this
Code:
ls
boot init.rc sdcard
cache init.recovery.hlthchrg.rc seapp_contexts
charger init.recovery.qcom.rc selinux_version
data init.recovery.service.rc sepolicy
default.prop init.recovery.usb.rc service_contexts
dev license sideload
efs modem sys
etc oem system
external_sd proc tmp
file_contexts property_contexts twres
file_contexts.bak recovery ueventd.qcom.rc
firmware res ueventd.rc
fstab.qcom root usbstorage
init sbin vendor
The system folder is empty tho. I have pulled the default.prop to my pc and pushed it back, created the build.prop and pushed it in to the system folder.
After i did that i typed exit and then adb reboot. Still no usb debugging. I checked the files again and the default.prop was back to the original, and the build.prop from the system folder was gone after the reboot. I don't know what i am doing wrong. I even have root access....
Click to expand...
Click to collapse
System isn't mounted which is why you can't access it - you need to swipe to enable system modification when you first start twrp which you can't see hence I said see if are able to control screen from pc
Make sure you set the correct permissions for the file - 644 or rw-r-r
TheFixItMan said:
System isn't mounted which is why you can't access it - you need to swipe to enable system modification when you first start twrp which you can't see hence I said see if are able to control screen from pc
Make sure you set the correct permissions for the file - 644 or rw-r-r
Click to expand...
Click to collapse
File permissions are correct, i have checked them as soon i saw that it wont work.
i have tried to mirror the screen over adb with
https://www.xda-developers.com/scrcpy-control-android-on-pc/
http://marian.schedenig.name/2014/07/03/remote-control-your-android-phone-through-adb/
and i was checking on google arround, nothing works. It also seems like that the touch screen is broken...
Anyone knows maybe annother option to mount the system?
TomyVk said:
File permissions are correct, i have checked them as soon i saw that it wont work.
i have tried to mirror the screen over adb with
https://www.xda-developers.com/scrcpy-control-android-on-pc/
http://marian.schedenig.name/2014/07/03/remote-control-your-android-phone-through-adb/
and i was checking on google arround, nothing works. It also seems like that the touch screen is broken...
Anyone knows maybe annother option to mount the system?
Click to expand...
Click to collapse
No other than the commands I've given you
TheFixItMan said:
No other than the commands I've given you
Click to expand...
Click to collapse
Means the only chance would be to pull a rom and edit it so that adb is enabled and flash it on the device....
Well, i think i got a new hobby xD
I've now tried in several ways to change /system/build.prop (phone rooted) but I had no luck.
Method 1: BuildProp Editor
I've tried using this app to change the file, the save succeeds, but after rebooting, the "original" file is restored and the changes are lost.
Method 2: Remounting the filesystem
I've tried remounting the filesytem:
Code:
$ adb shell mount
/dev/block/dm-4 on / type ext4 (ro,seclabel,relatime,block_validity,discard,delalloc,barrier,user_xattr,acl,i_version)
...
Code:
$ adb shell su -c mount -o rw,remount /
$ adb shell mount
/dev/block/dm-4 on / type ext4 (rw,seclabel,relatime,block_validity,discard,delalloc,barrier,user_xattr,acl,i_version)
...
After making my changes, if I try to remount with ro access, it fails. After rebooting the changes are lost again.
Method 3: Modify system.img
I've tried changing the file in the system.img, repacking the super.img file and flash it as single AP file, same result, the changes are lost. I've tried to decompress the super.img and remount it (just to check the changes were still there) and indeed they were.
What am I doing wrong?
Is there any way to achieve this?
I've found a good description of how the system and Magisk work:
- https://topjohnwu.github.io/Magisk/details.html
- https://topjohnwu.github.io/Magisk/guides.html
hello, i am trying to modify build.prop to disable knox and enable multiuser but changes are not persistent, have you found a solution with magisk?
use notepad ++ to modify buildprop on pc. connect phone while off and while phone is booting push file to phone (repeatedly) theres a small window where you can inject during boot...takes awhile sometimes to hit it right. ive dont it on samsungs and lg.