Code:
C:\Users\Vitaly>adb shell
[email protected]:/ $ su
su
1|[email protected]:/ $ mount -o rw,remount /system
mount -o rw,remount /system
mount: Operation not permitted
1|[email protected]:/ $ whoami
whoami
whoami: unknown uid 2000
4.5.2 root by @p1gl3t
bootloop cause renaming DeviceSoftwareOTAContracts.apk_
and now some panic) why "not permitted" ?
ONYXis said:
Code:
C:\Users\Vitaly>adb shell
[email protected]:/ $ su
su
1|[email protected]:/ $ mount -o rw,remount /system
mount -o rw,remount /system
mount: Operation not permitted
1|[email protected]:/ $ whoami
whoami
whoami: unknown uid 2000
4.5.2 root by @p1gl3t
bootloop cause renaming DeviceSoftwareOTAContracts.apk_
and now some panic) why "not permitted" ?
Click to expand...
Click to collapse
What does logcat say? ps?
su might not work because Android has not started or because of some SELinux related stuff.
p1gl3t said:
What does logcat say? ps?
su might not work because Android has not started or because of some SELinux related stuff.
Click to expand...
Click to collapse
Logcat in attach
ps i have busybox installed if it could help
Solved it by installing Apex through adb and blocked Otter.
but very strange that su didn't work , I almost loaded.
ONYXis said:
Solved it by installing Apex through adb and blocked Otter.
Click to expand...
Click to collapse
Could you please explain in more detail what was the cause of the problem?
Amazon home launcher do not want to launch without DeviceSoftwareOTAContracts.apk.
I installed Apex. Started and rename back this file. Need to be more careful)
ONYXis said:
Code:
C:\Users\Vitaly>adb shell
[email protected]:/ $ su
su
1|[email protected]:/ $ mount -o rw,remount /system
mount -o rw,remount /system
mount: Operation not permitted
1|[email protected]:/ $ whoami
whoami
whoami: unknown uid 2000
4.5.2 root by @p1gl3t
bootloop cause renaming DeviceSoftwareOTAContracts.apk_
and now some panic) why "not permitted" ?
Click to expand...
Click to collapse
Pretty sure you are supposed to rename DeviceSoftwareOTA.apk, NOT DeviceSoftwareOTAContracts.apk Just saying... You may end up with an updated device if you renamed the wrong apk.
ONYXis said:
Amazon home launcher do not want to launch without DeviceSoftwareOTAContracts.apk.
I installed Apex. Started and rename back this file. Need to be more careful)
Click to expand...
Click to collapse
That logcat seemed way more horrific than just a launcher failing to start.
---------- Post added at 11:45 PM ---------- Previous post was at 11:44 PM ----------
GSLEON3 said:
Pretty sure you are supposed to rename DeviceSoftwareOTA.apk, NOT DeviceSoftwareOTAContracts.apk Just saying... You may end up with an updated device if you renamed the wrong apk.
Click to expand...
Click to collapse
You're right about which apk should be renamed. You can also rename otacerts.zip so that the verification fails.
GSLEON3 said:
Pretty sure you are supposed to rename DeviceSoftwareOTA.apk, NOT DeviceSoftwareOTAContracts.apk Just saying... You may end up with an updated device if you renamed the wrong apk.
Click to expand...
Click to collapse
It was special to test ) I already have one brick =) Totally my fault
p1gl3t said:
That logcat seemed way more horrific than just a launcher failing to start.
Click to expand...
Click to collapse
yes. my first impression was same =)
but then saw this - Process com.amazon.kindle.otter (pid 2851) has died. - decided to try
Related
hey guys,
ive just started to learn how to modify apks and use adb.
my problem is that after i pull the file, i modify the icon i want to change, re-sign it and push it back to the phone. after i reinstall, the icons have not changed :S i re-pulled it, and the icons in the drawable_hdpi file are the one i wanted.
also, completely unrelated to that.... in adb when i try to run adb remount, it says permission denied, but im rooted and i even tried running the shell root beforehand aswell.
i ran a search and followed the various instructions from the different threads and forums but im just stuck at that point
thanks guys
kylec said:
also, completely unrelated to that.... in adb when i try to run adb remount, it says permission denied, but im rooted and i even tried running the shell root beforehand aswell.
Click to expand...
Click to collapse
If you're getting permission denied how have you pushed it back?
XperiaX10iUser said:
If you're getting permission denied how have you pushed it back?
Click to expand...
Click to collapse
i push it to the sdcard lol because it wont let me push to the system/app folder nor the data/app folder. i check my screen and a pop up appears saying that superuser granted access, so i have that.
kylec said:
i push it to the sdcard lol because it wont let me push to the system/app folder nor the data/app folder.
Click to expand...
Click to collapse
Then it's no wonder your icons haven't changed if you haven't installed it to the phone.
Try, but keep your phones screen on whilst you try it...
adb shell (enter)
su (enter)
...allow super user access on phone...
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
XperiaX10iUser said:
Then it's no wonder your icons haven't changed if you haven't installed it to the phone.
Try, but keep your phones screen on whilst you try it...
adb shell (enter)
su (enter)
...allow super user access on phone...
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
Click to expand...
Click to collapse
ok i just tried that. when i typed su, it echoed and on my phone it said "unknown has been grandted superuser permissions" so i didnt need to click allow or anything.
then i typed the mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system and got mount: operation not permitted
any ideas?
kylec said:
any ideas?
Click to expand...
Click to collapse
Try...
cd C:\android-sdk-windows\tools
adb shell
su
chmod 4755 /system/bin/sh
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
...and report back.
XperiaX10iUser said:
Try...
cd C:\android-sdk-windows\tools
adb shell
su
chmod 4755 /system/bin/sh
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
...and report back.
Click to expand...
Click to collapse
yup that worked, i got an echo without errors
EDIT: ok after that i then tried to push the apk to the system/app and also the data/app folders, but i got a different error this time.
it said failed to copy .apk permission denied
kylec said:
it said failed to copy .apk permission denied
Click to expand...
Click to collapse
Try, in a terminal on the phone...
su
chmod 4755 /system/bin/sh
I always struggle trying to get permissions after I've first rooted but can never remember the exact sequence, but do know it's a combination of what I've suggested.
XperiaX10iUser said:
Try, in a terminal on the phone...
su
chmod 4755 /system/bin/sh
I always struggle trying to get permissions after I've first rooted but can never remember the exact sequence, but do know it's a combination of what I've suggested.
Click to expand...
Click to collapse
ill give it a try after uni lol. thanks for all the help mate, its awesome having a place to get advice and help
EDIT: finally got it working... i pushed the file to sdcard then used the terminal emulator and used:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
cd sdcard
cat x.apk /data/app/x.apk
and that worked perfectly lol
** This is completely unsupported!!!!!!! **
ALL credit goes to saurik for the root method, Jason A. Donenfeld (zx2c4) for finding the exploit, alpharevx for finding the offsets and initial confirmation on the Transformer Prime and viperboy for finding it and posting it in his thread. I did not research, find, or develop this root method!
Mods, if I've done anything wrong, please feel free to remove this thread.
You will need to know how to use ADB commands, otherwise, use viperMOD PrimeTime!!!!!!!!!!!!!!!!!!!!!!!!.
Downloads:
mempodroid binary
su binary
Root:
adb push mempodroid /data/local
adb push su /data/local
adb shell
chmod 777 /data/local/mempodroid
/data/local/mempodroid 0xd9ec 0xaf47 sh
** You should now be in a remote shell session with root (indicated by #)
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
** IF you have previously rooted your Prime, run the following two commands. They may throw an error that the file a file was not found.
rm /system/bin/su
rm /system/xbin/su
cat /data/local/su > /system/xbin/su
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
rm /data/local/mempodroid
rm /data/local/su
exit
exit
adb reboot
After your Transformer Prime comes up, install Superuser from android market.
HOPEFULLY everyone has learned their lesson and will also install Voodoo Rootkeeper as well!!!!!!!!!!!!!!!!!!!! R
Enjoi!!!!!!!!!!!!!!!
** Feb 21 2012 Edit **
Works on 9.4.2.14
** Feb 09 2012 Edit **
Works on 9.4.2.13
** Jan 25 2012 Edit **
Changed the mount command - thanks viperboy!
Added steps to possibly resolve issues with previously rooted systems
Changed a few steps to be a little bit easier.
**Jan 24 2012 Edit **
Some people are reporting issues with this method. I suspect this is due to previously having root or other altered files. A method that has worked for some is to update to 9.4.2.11.1 and then following the above procedures. Please note, this firmware release is unofficial and at this time THERE IS NO DOWNGRADE PATH.
i keep getting permission denied after
adb shell /data/local/mempodroid 0xd9ec 0xaf47 mount -o remount,rw '' /system
i missed a chmod step, add it just now.
run:
adb shell chmod 777 /data/local/mempodroid
and then pick up right where you left off.
as i am not root nor superuser .. i don't even get access
/ $ cd data
~ $ ls
ls: can't open '.': Permission denied
after this command
adb shell /data/local/mempodroid 0xd9ec 0xaf47 sh
i got [email protected]:/ # but i cant type anything else in the dos windows after it.. can you explain further please
insane111 said:
after this command
adb shell /data/local/mempodroid 0xd9ec 0xaf47 sh
i got [email protected]:/ # but i cant type anything else in the dos windows after it.. can you explain further please
Click to expand...
Click to collapse
click on the window, you should be able to continue typing
/mnt/sdcard/Download $ adb push su /data/local
error: device not found
for some odd reason i cant type anything else after on that window..
after shell with root, i get the #, but i can't type anything afterwards. do i just repeat the process over?
edit: question was already asked, tried clicking on window, doesn't work.
insane111 said:
for some odd reason i cant type anything else after on that window..
Click to expand...
Click to collapse
updating!
10 char
toby77jo said:
/mnt/sdcard/Download $ adb push su /data/local
error: device not found
Click to expand...
Click to collapse
no offense, you may want to just wait for the one click root.
Tairen said:
after shell with root, i get the #, but i can't type anything afterwards. do i just repeat the process over?
edit: question was already asked, tried clicking on window, doesn't work.
Click to expand...
Click to collapse
updated, should be working now.
hehe that is fine .. not offended
se1000 said:
updated, should be working now.
Click to expand...
Click to collapse
thank you very much sir.. it work...
insane111 said:
thank you very much sir.. it work...
Click to expand...
Click to collapse
NICE!!!!!!!!!!!!!!!!!!!!
hmm did everything on your post, and rebooted. already had SU so i just opened up an app that requires root (titanium backup) and it says it wasn't able to attain root?
edit: confirmed with root checker that i still don't have root
Tairen said:
hmm did everything on your post, and rebooted. already had SU so i just opened up an app that requires root (titanium backup) and it says it wasn't able to attain root?
edit: confirmed with root checker that i still don't have root
Click to expand...
Click to collapse
Try re-installing superuser? When I was rooted before, sometimes superuser wouldn't prompt me for SU on occasion too.
se1000 said:
Try re-installing superuser? When I was rooted before, sometimes superuser wouldn't prompt me for SU on occasion too.
Click to expand...
Click to collapse
ahh i see the problem..
cat /data/local/su > /system/xbin/su
sh: cannot create /system/xbin/su: Read-only file system
how do i proceed?
Tairen said:
ahh i see the problem..
cat /data/local/su > /system/xbin/su
sh: cannot create /system/xbin/su: Read-only file system
how do i proceed?
Click to expand...
Click to collapse
Looks like something went wrong on the first mempodroid command. Go back and start from the begining just in case. Shouldn't hurt anything.
se1000 said:
Looks like something went wrong on the first mempodroid command. Go back and start from the begining just in case. Shouldn't hurt anything.
Click to expand...
Click to collapse
Sounds good, will try again and update!
How can I do this without a sd card... thanks in advance.
Sent from my LG-VM670 using Tapatalk
Flash the recovery image?
Root
Adb push a flash_image binary to /system/bin or xbin
adb push recovery.image to /cache or something
flash_image recovery /cache/recovery.img
I'm trying to flash the recovery without a SD card, because my phone can't mount a SD card anymore. So I'm using the recovery here http://www.lg-phones.org/lg-optimus-v-custom-recovery.html and Flash_image to flash it, but I need ADB codes to do so. I'm not very good with ADB, so I need the ones without the flash_image recovery /sdcard/ recovery-thunderc-v-1.2.0-GNM.img /sdcard/ part. :/
Curiousn00b said:
I'm trying to flash the recovery without a SD card, because my phone can't mount a SD card anymore. So I'm using the recovery here http://www.lg-phones.org/lg-optimus-v-custom-recovery.html and Flash_image to flash it, but I need ADB codes to do so. I'm not very good with ADB, so I need the ones without the flash_image recovery /sdcard/ recovery-thunderc-v-1.2.0-GNM.img /sdcard/ part. :/
Click to expand...
Click to collapse
It the same thing as tvall has mentioned but I will make it more easy for you.
As mentioned in the link that you have provided, just do this instead:
A) Type in 'adb remount'
B) Copy recovery-thunderc-v-1.2.0-GNM.img to platform-tools directory where android SDK is installed.
C) Do a 'adb push recovery-thunderc-v-1.2.0-GNM.img /system/xbin'
[Now the recovery image is inside your phones memory @/system/xbin location]
Following are the existing steps from the link: Modified step is made bold.
1) mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
2) cat /sdcard/flash_image > /system/bin/flash_image
3) chmod 755 /system/bin/flash_image
4) mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
5) mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
6) flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
7) reboot recover
tvall said:
Flash the recovery image?
Root
Adb push a flash_image binary to /system/bin or xbin
adb push recovery.image to /cache or something
flash_image recovery /cache/recovery.img
Click to expand...
Click to collapse
developer++ said:
It the same thing as tvall has mentioned but I will make it more easy for you.
As mentioned in the link that you have provided, just do this instead:
A) Type in 'adb remount'
B) Copy recovery-thunderc-v-1.2.0-GNM.img to platform-tools directory where android SDK is installed.
C) Do a 'adb push recovery-thunderc-v-1.2.0-GNM.img /system/xbin'
[Now the recovery image is inside your phones memory @/system/xbin location]
Following are the existing steps from the link: Modified step is made bold.
1) mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
2) cat /sdcard/flash_image > /system/bin/flash_image
3) chmod 755 /system/bin/flash_image
4) mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
5) mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
6) flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
7) reboot recover
Click to expand...
Click to collapse
Thanks alot guys, I really appreciate it, but I get stuck at
C:\android-sdk\platform-tools>adb remount
remount succeeded
C:\android-sdk\platform-tools>adb push recovery-thunderc-v-1.2.0-GNM.img /system
/xbin
cannot stat 'recovery-thunderc-v-1.2.0-GNM.img': No such file or directory
C:\android-sdk\platform-tools>
I'm starting to learn more, as I knew alot back when I first rooted my phone. As time went by..... easier ways were made.
Help plz.
EDIT: Been messing around with it, but still no go. This is what I got. Keep in mind I messed with some stuff if it doesn't look right..... :s
C:\android-sdk\platform-tools>adb remount
remount succeeded
C:\android-sdk\platform-tools>adb shell
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
# chmod 755 /system/bin/flash_image
chmod 755 /system/bin/flash_image
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
mv: can't rename '/system/etc/install-recovery.sh': No such file or directory
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
# flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
failed with error: -1
error reading /system/xbin/recovery-thunderc-v-1.2.0-GNM.img header# flash_image
recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
failed with error: -1
error reading /system/xbin/recovery-thunderc-v-1.2.0-GNM.img header# /system/xbi
n/flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
/system/xbin/flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
/system/xbin/flash_image: permission denied
#
Bump...
Sent from my LG-VM670 using Tapatalk
I have made inline comments. Just take note of it.
Curiousn00b said:
C:\android-sdk\platform-tools>adb remount
remount succeeded
C:\android-sdk\platform-tools>adb push recovery-thunderc-v-1.2.0-GNM.img /system
/xbin
cannot stat 'recovery-thunderc-v-1.2.0-GNM.img': No such file or directory
Click to expand...
Click to collapse
Here the 'recovery-thunderc-v-1.2.0-GNM.img' file should be present inside the C:\android-sdk\platform-tools directory. Also check if the spelling is correct.
Curiousn00b said:
C:\android-sdk\platform-tools>adb remount
remount succeeded
C:\android-sdk\platform-tools>adb shell
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
# chmod 755 /system/bin/flash_image
chmod 755 /system/bin/flash_image
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
mv: can't rename '/system/etc/install-recovery.sh': No such file or directory
Click to expand...
Click to collapse
This error came because there is no file called 'install-recovery.sh' inside /system/etc. This is fine since you are anyways not going to use that file.
Curiousn00b said:
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
# flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
failed with error: -1
error reading /system/xbin/recovery-thunderc-v-1.2.0-GNM.img header# flash_image
recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
failed with error: -1
error reading /system/xbin/recovery-thunderc-v-1.2.0-GNM.img header# /system/xbi
n/flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
/system/xbin/flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
/system/xbin/flash_image: permission denied
#
Click to expand...
Click to collapse
This part I am not that clear but it might be that the recovery 'recovery-thunderc-v-1.2.0-GNM.img' is corrupt or may be 'flash_image' is corrupt. You can also check for the amount of free memory by typing in 'df' and 'free' respectively. df would give you phone memory stats and free would give you RAM stats. Verify if anything is too low.
For the last permission denied error do a 'ls -l' at /system/xbin and check for the permissions.
I will look around to see if I can get some clues till then, lets wait for someone who can help you better.
[ADVICE: Since you are playing around with system binaries make sure you take a backup of /system/bin atleast.]
developer++ said:
I have made inline comments. Just take note of it.
Here the 'recovery-thunderc-v-1.2.0-GNM.img' file should be present inside the C:\android-sdk\platform-tools directory. Also check if the spelling is correct.
This error came because there is no file called 'install-recovery.sh' inside /system/etc. This is fine since you are anyways not going to use that file.
This part I am not that clear but it might be that the recovery 'recovery-thunderc-v-1.2.0-GNM.img' is corrupt or may be 'flash_image' is corrupt. You can also check for the amount of free memory by typing in 'df' and 'free' respectively. df would give you phone memory stats and free would give you RAM stats. Verify if anything is too low.
For the last permission denied error do a 'ls -l' at /system/xbin and check for the permissions.
I will look around to see if I can get some clues till then, lets wait for someone who can help you better.
[ADVICE: Since you are playing around with system binaries make sure you take a backup of /system/bin atleast.]
Click to expand...
Click to collapse
I tried again about 8 hours ago. I got through everything with no error, but when I got to recovery, it was still the old one. I'll try again once I get home.
Sent from my LG-VM670 using Tapatalk.
Other option (if your phone is rooted)
Install RomManager and install CWM or alternative.
If you're not rooted you need to do that first.
After that you can flash any recovery you want and you don't need to mess with adb
You can try to flash a recovery via LGMDP. I've flashed CWM 4.0 by this way.
_Arjen_ said:
Other option (if your phone is rooted)
Install RomManager and install CWM or alternative.
If you're not rooted you need to do that first.
After that you can flash any recovery you want and you don't need to mess with adb
Click to expand...
Click to collapse
Rom manager bricks the Optimus.
Dan_Jacques said:
You can try to flash a recovery via LGMDP. I've flashed CWM 4.0 by this way.
Click to expand...
Click to collapse
Sent from my LG-VM670 using Tapatalk
I got it flashed, thanks to Jerryscript.
Sent from my LG-VM670 using Tapatalk
Curiousn00b said:
Rom manager bricks the Optimus.
Sent from my LG-VM670 using Tapatalk
Click to expand...
Click to collapse
well most time i did it via rom manger and all time it was a sucess ,still lgmdp is good option but rom manger does it quiet easily just make sure u ahve a good internet connection so that its not disrupted when downloading better connected via wifi orelse better to go wth lgmdp method
Curiousn00b said:
I got it flashed, thanks to Jerryscript.
Sent from my LG-VM670 using Tapatalk
Click to expand...
Click to collapse
You can share the solution and provide a link so that in the future if someone has the same problem he can visit this thread and get things sorted out.
Edit the title of the thread to SOLVED
developer++ said:
You can share the solution and provide a link so that in the future if someone has the same problem he can visit this thread and get things sorted out.
Edit the title of the thread to SOLVED
Click to expand...
Click to collapse
I never found out how to change the thread name.
And ill edit the post tomorrow. I also have another question.
Sent from my LG-VM670 using Tapatalk
Can someone with a sd card, and adb, test this out? I don't want to test it out, cause without a sd card mounter, if it doesn't work, I'm screwed. If it doesn't work, I'm sure you have a nandroid on your sd card, hopefully. Please and thank you.
http://www.addictivetips.com/mobile/how-to-install-a-rom-to-an-android-phone-device-without-sd-card/
Sent from my LG-VM670 using Tapatalk
"Operation not permitted"
What is causing this? I really want to push some files to my EVO.
Help
I have done it previously on other Roms i have flashed. I am currently on Goodies 1.5.
typhoonikan said:
"Operation not permitted"
What is causing this? I really want to push some files to my EVO.
Help
I have done it previously on other Roms i have flashed. I am currently on Goodies 1.5.
Click to expand...
Click to collapse
I believe the adb binary has to be replaced with one that has permission to do this, it is often disabled in stock builds.
an easy way around this is
adb shell
su
mount -o remount rw, /system
modplan said:
I believe the adb binary has to be replaced with one that has permission to do this, it is often disabled in stock builds.
an easy way around this is
adb shell
su
mount -o remount rw, /system
Click to expand...
Click to collapse
I typed just as you did. No help.
My results as copy and pasted:
c:\Android>adb shell
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount rw, /system
mount -o remount rw, /system
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
c:\Android>adb remount
remount failed: Operation not permitted
typhoonikan said:
I typed just as you did. No help.
My results as copy and pasted:
c:\Android>adb shell
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount rw, /system
mount -o remount rw, /system
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
c:\Android>adb remount
remount failed: Operation not permitted
Click to expand...
Click to collapse
What I posted remounts the system partition read/write. No need to adb remount after that, you can write to /system at that point.
Hi all, i added some files into the system directory of my kindle fire hdx 7'.. when i restarted it is stuck in a boot loop on the animated Kindle Fire boot screen, i can ADB onto it, and i attempted to remove the files, but "ADB su" isn't working for me, and I'm unable to access the system directory over ADB... and i don't have custom recovery.
Any ideas on this one? is there a way of restoring the Kindle?
Thanks
osmorgan said:
Hi all, i added some files into the system directory of my kindle fire hdx 7'.. when i restarted it is stuck in a boot loop on the animated Kindle Fire boot screen, i can ADB onto it, and i attempted to remove the files, but "ADB su" isn't working for me, and I'm unable to access the system directory over ADB... and i don't have custom recovery.
Any ideas on this one? is there a way of restoring the Kindle?
Thanks
Click to expand...
Click to collapse
what you get on
Code:
adb shell
su
?
thanks for the reply. when i
adb shell
su
Click to expand...
Click to collapse
it returns to 1:[email protected] where it should show [email protected] any ideas?
osmorgan said:
thanks for the reply. when i
it returns to 1:[email protected] where it should show [email protected] any ideas?
Click to expand...
Click to collapse
after that use
Code:
mount -o rw,remount /system
if you wil get permission denied you need to do hard reset from recovery and try again
after that you could change files in /system
great, i will try this later.. any guides on doing a hard reset?? keeping in mind that i don't have custom recovery..
thanks again.
osmorgan said:
great, i will try this later.. any guides on doing a hard reset?? keeping in mind that i don't have custom recovery..
thanks again.
Click to expand...
Click to collapse
you could get into stock recovery by holding power+volume up
all of this suggesting that you are at 4.5.2 and rooted
for 3.2.X hard reset will delete su - file
You're a star. Thanks. I'll get onto this after work.
ONYXis said:
you could get into stock recovery by holding power+volume up
all of this suggesting that you are at 4.5.2 and rooted
for 3.2.X hard reset will delete su - file
Click to expand...
Click to collapse
No luck :/ was unable to mount, and hard reset via recovery still results in boot loop :/ any other ideas?
Could you post output?
and pls what is your firmware and root method?
Seems no way to recover(sorry
How do I provide the output? I was 4.5.2 and rooted with CVE
copy-paste output from cmd
like:
Code:
adb shell
su
....
ahh i see what you mean.. ive run s uagian after factory reset and its now giving me the root prompt! great! im just about to follow this guys steps
http://forum.xda-developers.com/showthread.php?t=2793253
thanks for your help.. i may be back.
any idea if this method works with stock recovery?
ONYXis said:
copy-paste output from cmd
like:
Code:
adb shell
su
....
Click to expand...
Click to collapse
nope.. that didnt work for me.. do you know how i can push a deb to reflash?
Pls post output to see that exactly doesn't work.
to use that manual you need to use 4.5.3 bin btw
I see, I was having permissions errors when pushing the file to the sdcard, I had mounted the data partition. I am unable to write anything as shell user, but fine as root. Any ideas?
Thanks
adb shell
[email protected]:/ $ su
[email protected]:/ # mount -o rw,remount /cache
[email protected]:/ # mkdir /cache/recovery
mkdir failed for /cache/recovery, File exists
[email protected]:/ # echo install /cache/kindleupdate.bin > /cache/recovery/openrecoveryscript
[email protected]:/ # chmod 0777 /cache/recovery/openrecoveryscript
[email protected]:/ # exit
[email protected]:/ $ exit
Mac-miniownloads $ adb push update-kindle-13.4.5.3_user_453011120.bin /cache/kindleupdate.bin
failed to copy 'update-kindle-13.4.5.3_user_453011120.bin' to '/cache/kindleupdate.bin': Permission denied
What do you think?
ONYXis said:
what you get on
Code:
adb shell
su
?
Click to expand...
Click to collapse
ONYXis said:
Pls post output to see that exactly doesn't work.
to use that manual you need to use 4.5.3 bin btw
Click to expand...
Click to collapse
osmorgan said:
Mac-miniownloads $ adb push update-kindle-13.4.5.3_user_453011120.bin /cache/kindleupdate.bin
failed to copy 'update-kindle-13.4.5.3_user_453011120.bin' to '/cache/kindleupdate.bin': Permission denied
What do you think?
Click to expand...
Click to collapse
You cant do this at that way
you need :
Code:
adb push update-kindle-13.4.5.3_user_453011120.bin /sdcard/update.zip
adb shell
su
mount -o remount,rw /cache
cd /sdcard
cp update.zip /cache
chmod 777 /cache
chmod 777 /cache/recovery
cd /cache/recovery
echo "--update_package=/cache/update.zip" > command
exit
exit
adb reboot recovery
thank you but i still get permissions issues -
failed to copy 'update-kindle-13.4.5.3_user_453011120.bin' to '/sdcard/update.zip': Permission denied
ONYXis said:
You cant do this at that way
you need :
Code:
adb push update-kindle-13.4.5.3_user_453011120.bin /sdcard/update.zip
adb shell
su
mount -o remount,rw /cache
cd /sdcard
cp update.zip /cache
chmod 777 /cache
chmod 777 /cache/recovery
cd /cache/recovery
echo "--update_package=/cache/update.zip" > command
exit
exit
adb reboot recovery
Click to expand...
Click to collapse
osmorgan said:
thank you but i still get permissions issues -
failed to copy 'update-kindle-13.4.5.3_user_453011120.bin' to '/sdcard/update.zip': Permission denied
Click to expand...
Click to collapse
Hmm....Strange. Are you see Fire as mtp device on you Pc (for Mac you need https://www.android.com/filetransfer/)?
If "yes" - try to copy update.zip manual into Fire's internal storage.