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.
Related
Is it possible to change the lockscreen to the default android, i'm new to android nd still tryna get a hold of things. Thanks
-------------------------------------
Sent via the XDA Tapatalk App
lakeside00 said:
Is it possible to change the lockscreen to the default android, i'm new to android nd still tryna get a hold of things. Thanks
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
you can remove the HtcLockScreen.apk from /system/app/ and it will default to the stock android one. Problem is that is suffers from the same fate as many others where the slder is up/down and the time is jummbeled on the left side.
Oh and of course to remove/rename the file in /system/app/ you must be rooted and in recovery mode.
I'm working on how to fix the screen. Flipz did it for android 2.0 but it isn't the same fix in 2.1. If I get more info I'll post back.
I tried to remove HtcLockScreen.apk via adb but I don't think we have system write access yet. even through adb. someone correct me if I'm wrong but I believe this is true.
Edit: As said above... you have to be in recovery. I stand corrected. don't listen to me!
edit #2: tried it in recovery... couldn't even remount. I don't think I did anything wrong...
gmelchert said:
I tried to remove HtcLockScreen.apk via adb but I don't think we have system write access yet. even through adb. someone correct me if I'm wrong but I believe this is true.
Edit: As said above... you have to be in recovery. I stand corrected. don't listen to me!
edit #2: tried it in recovery... couldn't even remount. I don't think I did anything wrong...
Click to expand...
Click to collapse
LOL! love the step by step edits...
I have a script that makes it easy, it is just a modified version of Toast's. It cuts it down to one command input instead of three.
Any way here are the steps:
With phone on plug it into your computer. Open two command windows. Navigate one to the folder you have downloaded toasts recovery script to.
1) In the window that is at evo-recovery> type: adb reboot recovery
This boots you in to the stock recovery
2)in the same window type windows-recovery.bat (adjust for your OS)
This gets you into Amon-RA's recovery
3) Wait for the phone to get the new recovery screen. In the other command window type: adb shell mount -a
Step 3 can be adb remount or you can type adb shell then at the # type #mount -t yaffs2 -o remount,rw /dev/block/mtdblock4 /system
Any way after that point you can exit adb shell back to the command prompt and push/pull anything to /system
unfortunately you can't see it right away and have to wait for reboot. Also this limits some of the apps that we can install because some will need to write to /system and cannot once rebooted.
Hello, I rooted with unrevoked and then flashed the rom liberated_aria_FR006_signed.
I booted through clockwork and mounted /system /data /sdcard and then connected to my pc via usb, through the command prompt and adb I tried:
cp /sdcard/hosts /data/data/hosts
rm /system/etc/hosts
ln -s /data/data/hosts /system/etc/hosts
when I do rm /system/etc/hosts it says:
rm: can't remove '/system/etc/hosts': Directory not empty
What's wrong? Is /system not full perms through clockwork or is it a unrevoked root problem.
Thanks!
G226 said:
Hello, I rooted with unrevoked and then flashed the rom liberated_aria_FR006_signed.
I booted through clockwork and mounted /system /data /sdcard and then connected to my pc via usb, through the command prompt and adb I tried:
cp /sdcard/hosts /data/data/hosts
rm /system/etc/hosts
ln -s /data/data/hosts /system/etc/hosts
when I do rm /system/etc/hosts it says:
rm: can't remove '/system/etc/hosts': Directory not empty
What's wrong? Is /system not full perms through clockwork or is it a unrevoked root problem.
Thanks!
Click to expand...
Click to collapse
Lol...the error tells you exactly what's wrong...but kinda weird since the hosts is a file not a directory...so I can only assume that there are some permission issues...navigate to the /system/etc directory and do a "ls -al" and see what the permissions are for the hosts file...it'll be on the left side of the results of the ls.
Sent From My HTC Aria Using XDA App
Oh fyi...I'm dumb...are you already rooted? I dunno much about adb but you MIGHT have to run the above command through a terminal program on your phone...
Sent From My HTC Aria Using XDA App
I'm rooted but it's through unrevoked as mentioned, does that give me the proper permissions if I adb through clockwork recovery?
If not what would? I'll do a "ls -al" in a little.
G226 said:
I'm rooted but it's through unrevoked as mentioned, does that give me the proper permissions if I adb through clockwork recovery?
If not what would? I'll do a "ls -al" in a little.
Click to expand...
Click to collapse
I'm not sure...as I said im not too familiar with adb...I do know if you have a terminal program on your phone just open it, type the following:
su
cd /system/etc
ls -al
Once you so the ls, if you aren't familiar with *nix, you'll see the following:
-rw-r--r-- 1 root root 25 Aug 1 2008 hosts
Along with a bunch of other lines similar to this, this is the line I'd like to see though
Sent From My HTC Aria Using XDA App
Thanks for the help so far, I did what you said and after doing "ls -al" it said :
-al: No such file or directory
If I do a plain "ls" command it'll list all the files/folders in the system dir.
G226 said:
Thanks for the help so far, I did what you said and after doing "ls -al" it said :
-al: No such file or directory
If I do a plain "ls" command it'll list all the files/folders in the system dir.
Click to expand...
Click to collapse
1 are you doing this in adb or terminal?
2 are you typing "ls -al" with a space? And "al" as in alpha lima?
3 are you in the etc directory?
Sent From My HTC Aria Using XDA App
I did as you instructed, used the terminal program app and tried these commands through there, I'll try adb.
Thanks.
Well the only reason I asked was because ls -al is a legit command lol...I dunno of another way to view the permissions of files...I also don't know if there is a way or not through adb, Google may be your friend in regards to that...
Sent From My HTC Aria Using XDA App
This may be related to busybox on the phone. Can you do an "echo $PATH" from the adb shell and paste the results here?
So from the command prompt you would enter "adb shell" this should give you a new prompt like this #. At this prompt type "echo $PATH" without the quotes. Maybe you do not need all these instructions, sorry.
I see this all the time, from all the noobs (myself included)
First off the ARIA still has S-ON security, so if you are writing to /system/ you _NEED_ to be properly booted into recovery - otherwise you will not have write permissions. its in the FAQ but still completely overlooked. There is a post about this every day i swear.
STEP 1) UNPLUG THE USB <----- CRITICAL
STEP 2) POWER DOWN THE PHONE <----- AFTER STEP 1!!!!!!
STEP 3) HOLD VOLUME DOWN + PRESS POWER to load hboot
STEP 4) SELECT recovery to start clockwork
STEP 5) partitions --> mount --> /system/
STEP 6) connect USB
STEP 7) adb shell
edit: if you shortcut into recovery by just leaving the USB plugged in while you power down - you will not have full permissions.
dexmix said:
I see this all the time, from all the noobs (myself included)
First off the ARIA still has S-ON security, so if you are writing to /system/ you _NEED_ to be properly booted into recovery - otherwise you will not have write permissions. its in the FAQ but still completely overlooked. There is a post about this every day i swear.
STEP 1) UNPLUG THE USB <----- CRITICAL
STEP 2) POWER DOWN THE PHONE <----- AFTER STEP 1!!!!!!
STEP 3) HOLD VOLUME DOWN + PRESS POWER to load hboot
STEP 4) SELECT recovery to start clockwork
STEP 5) partitions --> mount --> /system/
STEP 6) connect USB
STEP 7) adb shell
edit: if you shortcut into recovery by just leaving the USB plugged in while you power down - you will not have full permissions.
Click to expand...
Click to collapse
3 sleepless nights later and dexmix comes to the rescue. This drove me crazy man, I just could not find the answer. Thanks!! Bed time!
I decided to put together a nice, straightforward tutorial on how to root and unlock your device. I have recently joined the Android scene myself, and the XDA forums have been invaluable to my learning process. I did hit a few brick walls in the process (and nearly bricked my phone as well) before I finally achieved a 100% working, rooted, unlocked ROM installation. So, I just wanted to put together a short, easy to follow guide on rooting and unlocking, which will (hopefully) avoid you extra time / headache.
Note: It is quite possible (though not certain) that you may lose your current data after the unlock process, so make sure to make a backup before you proceed.
Pre-Requisites:
- Atrix 4G (AT&T)
- Any firmware up to 4.5.91 (which is currently the latest official - as of 8/4/11)
- A Windows PC
- Current Motorola drivers for your device installed on your PC
Required Files:
Android Root and Unlock (2011-08-04).zip
This archive contains Fastboot, ADB, Tenfar's ClockWorkMod, Pudding (v2), and RSD Lite 5.3.1 (which is all you'll need). I put it together into one package to save you a bit of time, but all the credit goes to the original devs / creators.
Step 1 - Unlock the Bootloader
Extract the provided archive into a folder on your PC. Let's assume this is "C:\Atrix\".
Install RSD Lite 5.3.1 program on your Windows machine.
Make sure the latest Motorola USB drivers for your Atrix are installed on your PC.
Run the RSD Lite program on your PC.
Power down your Atrix and connect to your PC via USB.
Power on your Atrix, and immediately hold the Volume Down button until you see a menu pop up. This will be a text menu which will appear at the top of your screen, and the first option you'll see will be "Fastboot". Cycle the menu by pressing the Volume Down button until you get to the "RSD" menu option. Press the Volume Up button to launch the RSD support on your Atrix.
You should now see the phone appear in the RSD Lite program interface on your PC (in the bottom menu). Click on it. You should see some data about your Atrix appear in the Device Properties pane.
Hit the "..." button in the RSD Lite program to bring up the file menu and select the "4547-fix-try2.sbf" (included in the archive above). This is Pudding. It will unlock your Atrix in just a moment.
Hit the "Start" button. RSD Lite will flash your phone. This process will be fairly quick, and your Atrix will reboot once or twice. After your Atrix boots back into Android, power down your phone and close the RSD Lite program on your PC (ignore the warning... the process is complete... if it wasn't complete, you would not be able to boot up into Android).
Power down your Atrix once again. Leave it connected to your PC via USB. Power it on again and hold the Volume Down key to get to the boot menu (as before). This time, select the "Fastboot" option by pressing the Volume Up button.
Open up the Command Prompt on your PC (Run 'cmd', or browse for it in your 'Accessories' application menu) and go to C:\Atrix\ (or the directory where you extracted the provided archive).
Type in the following command:
fastboot oem unlock
You will see a message pop up with a warning about unlocking your device. Assuming you are here, you don't care about this, so just make note of the device id that the message provides.
Type in the command again, this time with the device id:
fastboot oem unlock ### ,
where ### is the device id you noted above.
Type:
fastboot reboot
That's it! Your device now has an unlocked bootloader.
Step 2 - Flash the ClockWorkMod
ClockWorkMod ("CWM") will allow you to make backups of your current system, as well as install mods and ROMs.
Reboot your Atrix.
Hold the Volume Down button as the device powers up to get to the boot menu. (You should be familiar with this by now.)
Select the "Fastboot" option from the menu by pushing the Volume Up button.
Type the following command from the command prompt on your PC (assuming you're still in the C:\Atrix\ directory, or the directory where you extracted the provided archive):
fastboot flash recovery recovery-en-goapk-0630-1029.img
Type into the command prompt:
fastboot reboot
You're done. You will now be able to launch CWM from the boot menu by selecting the "Android Recovery" option. Again, the boot menu cycles with the Volume Down key, and you make a selection with the Volume Up key. If you selected the wrong option, just pull your battery and try again.
Step 3 - Root Your Device
Rooting will give you the "Superuser" program in Android and allow you to provide superuser permissions to apps.
Reboot your device. As it powers on, hold the Volume Down button to get into the boot menu. Select the "Fastboot" menu option using the Volume Up key.
Type the following commands into the command prompt on your PC (assuming you're still in the C:\Atrix\ directory, or where you extracted the provided archive):
fastboot flash preinstall preinstall.img
fastboot reboot
Wait until your device boots fully into Android.
On the command prompt on your PC, type in the following commands, sequentially (executing each one-by-one, i.e., hitting the enter key after each):
adb shell
/preinstall/dosu
/bin/mount -o remount,rw /system
cp /preinstall/su /system/bin/
chmod 6755 /system/bin/su
PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk
Done! You should now see the "Superuser" program as one of your Android's apps.
You are now unlocked, rooted and have CWM installed! You are ready to mod / ROM your Atrix.
what if...? At step 4 always get permission denied after
/preinstall/dosu ?
Rgds
antoniolcrd said:
what if...? At step 4 always get permission denied after
/preinstall/dosu ?
Rgds
Click to expand...
Click to collapse
Keep typing commands. It'll look like an error but keep going.
Sent from my MB860 using XDA App
Maybe out of luck...
check this pls:
C:\tools>adb shell
$ /preinstall/su
/preinstall/su
Permission denied
$ /bin/mount /system -o remount,rw
/bin/mount /system -o remount,rw
/bin/mount: permission denied
$ cp /preinstall/su /system/bin/su
cp /preinstall/su /system/bin/su
cp: /system/bin/su: Read-only file system
$ chmod 6755 /system/bin/su
chmod 6755 /system/bin/su
Unable to chmod /system/bin/su: Read-only file system
$
This is one of the most n00b friendly guides I ever read. I can picture each step in my head as I read the instructions.
EDIT: This can go either way. I find it easier just to flash a ROM that's pre-rooted after unlocking the BL and installing CWM when it comes to step 3.
Did you run through steps 1-3 as well?
The second command should be "/preinstall/dosu".
antoniolcrd said:
check this pls:
C:\tools>adb shell
$ /preinstall/su
/preinstall/su
Permission denied
$ /bin/mount /system -o remount,rw
/bin/mount /system -o remount,rw
/bin/mount: permission denied
$ cp /preinstall/su /system/bin/su
cp /preinstall/su /system/bin/su
cp: /system/bin/su: Read-only file system
$ chmod 6755 /system/bin/su
chmod 6755 /system/bin/su
Unable to chmod /system/bin/su: Read-only file system
$
Click to expand...
Click to collapse
No way.
Nickel3ack said:
Did you run through steps 1-3 as well?
The second command should be "/preinstall/dosu".
Click to expand...
Click to collapse
I´ve tried this command also. Pls check:
C:\tools>adb shell
* daemon not running. starting it now *
* daemon started successfully *
$ /preinstall/dosu
/preinstall/dosu
bash: groups: command not found
[email protected]:/# /bin/mount/system -o remount,rw
/bin/mount/system -o remount,rw
bash: /bin/mount/system: Not a directory
[email protected]:/# cp /preinstall/su /system/bin/su
cp /preinstall/su /system/bin/su
cp: cannot create '/system/bin/su': Read-only file system
[email protected]:/# chmod 6755 /system/bin/su
chmod 6755 /system/bin/su
chmod: /system/bin/su: Read-only file system
[email protected]:/#
Holy Crap I Think I'm Bricked
Ok guy, I just knew this was gonna happen.
Step one, part 8. After my phone rebooted my Atrix says:
failed to boot 0x1000
No OS detected, going to RSD mode in 5 seconds
Okay, now what? LOL HELP!
Don't Panic
sonnyjame5902 said:
Ok guy, I just knew this was gonna happen.
Step one, part 8. After my phone rebooted my Atrix says:
failed to boot 0x1000
No OS detected, going to RSD mode in 5 seconds
Okay, now what? LOL HELP!
Click to expand...
Click to collapse
No... don't worry. It's not a brick. Worst case you can restore the stock ROM.
1st Thing to try:
Basically, just wait a bit after it says "failed to boot"... don't press anything... then a menu will pop up. Before it can go to RSD, press the Volume Down key to get to Fastboot. Press Volume Up to get into Fastboot. Continue with steps 11-15. If this unlocks the bootrom, your error should disappear and you'll have your fully functional Android back.
2nd thing to try:
Just wait a bit after it says "failed to boot"... don't press anything... then a menu will pop up. Let the phone go into RSD. Go back to the RSD Lite program on your PC and repeat the Unlock process. Hopefully this time it will work.
3rd thing to try:
If not.... go to the Firmwares Superthread here on XDA and download the ROM appropriate for your carrier. Flash it onto your device via RSD (same method for flashing as above, except select the SBF you downloaded from the thread). This will get your device back into operation at least (you will lose all your data tho, so I'd try the other 2 methods first).
Friggin Cheers Mate! Got it all set up with option 2, and now I'm rooted and SU! And they said it couldn't be done after the Gingerbread OTA update! Bollocks!
You should recheck your steps, cause I can't get CWM without being rooted. Cannot use root explorer to delete install.recovery. sh without superuser permission.
Dell2 said:
You should recheck your steps, cause I can't get CWM without being rooted. Cannot use root explorer to delete install.recovery. sh without superuser permission.
Click to expand...
Click to collapse
The method for CWM described here is to flash the CWM directly to your recovery partition. All it needs is for the device to have an unlocked bootloader. You don't need to be rooted for this. Rooting only affects the way your Android OS permissions apps. You'll definitely need to be rooted to install CWM via ROM Manager or Titanium Backup. This is not that method.
can i just root with step 3 or do i have to unlock first?
Just out of curiosity I see in the OP that this should not affect data - what evidence is there of this being the case with 4.5.91 OTA?
This unlock method modifies the boot sectors only. Your data is basically untouched. The method is actually well documented here on XDA. I just made this brief guide to be noob friendly. It actually summarizes a few working techniques. I unlocked and rooted by own, new AT&T Atrix using this method, which had the 4.5.91 OTA.
Anyway, not sure why people think they are bricking their phones. As long as the device turns on and you can get to the boot menu and back into RSD mode, you can always flash a stock ROM and be back to a functioning device. Only thing you risk losing is your data in any case.
Nickel3ack said:
This unlock method modifies the boot sectors only. Your data is basically untouched. The method is actually well documented here on XDA. I just made this brief guide to be noob friendly. It actually summarizes a few working techniques. I unlocked and rooted by own, new AT&T Atrix using this method, which had the 4.5.91 OTA.
Anyway, not sure why people think they are bricking their phones. As long as the device turns on and you can get to the boot menu and back into RSD mode, you can always flash a stock ROM and be back to a functioning device. Only thing you risk losing is your data in any case.
Click to expand...
Click to collapse
This is just the first time I've read about being able to work on 4.5.91 without wiping the user data, so I was curious how this method differed from the others that were out there (mrramirezusa and the original pudding). Thanks for the info.
Really dumb question, but before I start, do I want my USB connection to be USB Mass STorage, None, WIndows Media Sync, or Motorola Phone Portal?
im getting error when i click start button it gives error of failed flashing
jeffhwitz said:
Really dumb question, but before I start, do I want my USB connection to be USB Mass STorage, None, WIndows Media Sync, or Motorola Phone Portal?
Click to expand...
Click to collapse
For RSD, none.
EDIT
Now having done this I can say it doesn't make any difference because this is all done outside of the Android Operating System.
Well, I did it and I did irritatingly lose everything in my /data. Luckily I've got everything backed up. Came from the 4.5.91 OTA and other than rooted was totally stock. Did give me a failed to boot 0x1000, pulled batt, restarted and did fastboot, did the unlock successfully (i.e. didn't flash any additional files so per the posts no reason I should have lost everything but I still did).
So, it does seem like more often than not doing this from the real actual unmodified OTA will cause a loss of user data as has been stated even though sometimes it doesn't seem to.
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
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