Database Develop

[Q] how can i write /sdcard/update.zip in recovery mode

I was trying to update the status bar on my i9000m/JH2. I must have done something wrong when zipping, signing, or zipaligning the file. I was able to apply the update.zip without any errors through recovery mode. But when i rebooted, I was met with continuous force close windows. I had my original backed up and wanted to place that into /sdcard and then simply run it from recovery mode to 'undo' the damage i did.
/sdcard appears empty when I run abd to my phone while in recovery mode. If i attempt to push a file to it, i get 'permission denied'. Do i need to manually mount /sdcard in recovery mode to be able to overwrite /sdcard/update.zip (can this be done)?

*snip*
On sec...

nudge nudge

Reflash is only option now. Recommend in future you leave recovery update.zip on SD card and use root explorer to copy over new f/w. That way if no good you can recover easier.
Sent from my GT-I9000M using XDA App

If u get adb running why not just push it then ?
adb shell stop
adb push framework-res.apk /system/framework/framework-res.apk
adb shell start

lgkahn said:
Reflash is only option now. Recommend in future you leave recovery update.zip on SD card and use root explorer to copy over new f/w. That way if no good you can recover easier.
Sent from my GT-I9000M using XDA App
Click to expand...
Click to collapse
I ended up reflashing shortly after it happened. I'll look into root explorers.

Daneshm90 said:
If u get adb running why not just push it then ?
adb shell stop
adb push framework-res.apk /system/framework/framework-res.apk
adb shell start
Click to expand...
Click to collapse
I was able to get adb running, but I didn't see /system when listing. Did i need to mount it?

onaquest said:
I was able to get adb running, but I didn't see /system when listing. Do i need to mount it?
Click to expand...
Click to collapse
/system should still be already mounted. Otherwise u wudnt see a homescreen.
Just try the commands.

Daneshm90 said:
/system should still be already mounted. Otherwise u wudnt see a homescreen.
Just try the commands.
Click to expand...
Click to collapse
One other detail is that the phone wasn't rooted At the time I thought that might have been preventing me from seein /system.
This is all educational for me, I was wondering what other options I had before reflashing. Thanks for all the input guys. I ended reflashing with Odin a few days ago.

[Q] How to fix wrong CHMOD permissions on /system

Inadvertanty I performed a 'chmod 644 /system' in an attempt to move my email.apk file over to the apps directory. Obviously this should have been a '777' but now the phone just reboots into recovery mode and will not get past it.
Is there any way to mount the filesystem and reissue the correct chmod command, or do I have to reinstall the OS?
Thanks!
Samsung Captivate
Serendipity VII-2

Try the Serendipity VII Q&A.
Sent from my SAMSUNG-SGH-I897 using Tapatalk

texasagent said:
Inadvertanty I performed a 'chmod 644 /system' in an attempt to move my email.apk file over to the apps directory. Obviously this should have been a '777' but now the phone just reboots into recovery mode and will not get past it.
Is there any way to mount the filesystem and reissue the correct chmod command, or do I have to reinstall the OS?
Thanks!
Samsung Captivate
Serendipity VII-2
Click to expand...
Click to collapse
Using adb (and your phone in recovery, with the /system partition mounted):
adb root
adb shell
chmod 777 /system
exit
adb reboot
Hopefully that should get you there.

Thanks jmtheiss. That allowed me to get back in to change the permissions, however it still won't get past recovery mode after each reboot. Its strange that even after mounting /system, it doesn't contain a directory called 'app' anymore (or any subdirectories for that matter), just a handful of files. Looks like I have bigger issues.
Guess it's back to reloading the ROM again...
Thanks for your help!!
TexasAgent

Please post in the right sections. Should have been in Q&A

Bricked, Need ADB push to recover, how mount?

Title says it all. While trying to learn some theme tricks, I must have screwed something up in the framework, because I'm stuck in a boot-loop after rebooting.
Thanks to Aria's post, which describes an easy way to make an easy ADB shortcut, I'm all set to go with ADB... but how can I force my cell to mount my computer when it's turned off? I just need to push my backup onto my phone, because I copied my CWM backup onto my pc and deleted it from my cell to make more room for videos. Stupid, I know
Any ideas? Thanks!

Nevermind, I fixed it through CWM by flashing a .zip of part of the framework that I changed, and it rebooted fine after that. From there I could mount my device.
Still, I'd be curious to know how to mount a device that cannot boot properly, if anyone knows a way.

how did you fix it i am stuck on lg logo when i boot i would really appreciate any help you could give

Komodo Rogue said:
Nevermind, I fixed it through CWM by flashing a .zip of part of the framework that I changed, and it rebooted fine after that. From there I could mount my device.
Still, I'd be curious to know how to mount a device that cannot boot properly, if anyone knows a way.
Click to expand...
Click to collapse
You can mount the system like this. If it's in a bootloop and ADB is enabled, this'll work.
adb shell
su
mount -o remount,rw /dev/block/stl9 /system
exit
exit
Sent from my LG Thrill 4G

[Q] Need help restoring my KFSOWI

Hey everyone,
first off, I have my Kindle for a few weeks now and it's my first Androit device. I started reading into rooting and adb commands only a few days ago, so please excuse me if I'm not writing accurately with some terms. Additionally, I could not find a similar problem via searching.
Here's my problem (I'll try to be as detailed as possible):
I rooted my KFSOWI running 11.3.1.0 yesterday using Moronigs rooting method. It went well and I had full root access (typing su in an adb shell resulted in an # and all that).
Today I wanted to edit the framework-res.apk to exchange some images. Stupid as I tend to be I wanted to rename the original file and then paste my modified one. The device started giving out various crashes, telling me that lots of apps stopped working. Only then I realised that the file is needed to run the system. Unfortunately the Kindle had shut down at some point and when I boot it now it only gives me a black screen (although the backlight is still on).
Here's what I tried so far:
1. I wanted to adb push the modified file to the system/framework folder, but it tells me that the folder is read-only.
2. So I wanted to change permissions but it seems I don't have root access anymore (I don't even get the # output in the adb-shell after typing su).
3. I tried installing the package via adb but it says "Error: COuld not access package manager. Is the system running?"
I guess it doesn't boot up the package manager and root access. You guys have any idea what I can do right now? Seems like a lost cause to me. And if so, can I try sending it back via warranty?
Any help is very much appreciated. And thanks for all the great work on these forums.

Does nobody have an idea? Would be very sad if I couldn't use it anymore. Although I'm the only one to blame. Does someone have experience on sending it back to amazon for warranty? As far as I know rooted devices lose their warranty.. :-/

Karelian_ said:
Hey everyone,
first off, I have my Kindle for a few weeks now and it's my first Androit device. I started reading into rooting and adb commands only a few days ago, so please excuse me if I'm not writing accurately with some terms. Additionally, I could not find a similar problem via searching.
Here's my problem (I'll try to be as detailed as possible):
I rooted my KFSOWI running 11.3.1.0 yesterday using Moronigs rooting method. It went well and I had full root access (typing su in an adb shell resulted in an # and all that).
Today I wanted to edit the framework-res.apk to exchange some images. Stupid as I tend to be I wanted to rename the original file and then paste my modified one. The device started giving out various crashes, telling me that lots of apps stopped working. Only then I realised that the file is needed to run the system. Unfortunately the Kindle had shut down at some point and when I boot it now it only gives me a black screen (although the backlight is still on).
Here's what I tried so far:
1. I wanted to adb push the modified file to the system/framework folder, but it tells me that the folder is read-only.
2. So I wanted to change permissions but it seems I don't have root access anymore (I don't even get the # output in the adb-shell after typing su).
3. I tried installing the package via adb but it says "Error: COuld not access package manager. Is the system running?"
I guess it doesn't boot up the package manager and root access. You guys have any idea what I can do right now? Seems like a lost cause to me. And if so, can I try sending it back via warranty?
Any help is very much appreciated. And thanks for all the great work on these forums.
Click to expand...
Click to collapse
At this point, I would send it back to Amazon. all they will check for is physical damage and send it back to China. I hear some people bricking their tablet several times and getting a replacement. Thing is that Amazon's warranty questions are only water damage and did you drop it questions. So you don't even have to BS them to get a replacement.

If you have a fast boot cable you might restore it. Now it's not the cable that came with Kindle, it's a special programming cable that will put it into fast boot mode.
Sent from my Amazon Kindle Fire2 using xda app-developers app

braider said:
If you have a fast boot cable you might restore it. Now it's not the cable that came with Kindle, it's a special programming cable that will put it into fast boot mode.
Sent from my Amazon Kindle Fire2 using xda app-developers app
Click to expand...
Click to collapse
There are no exploits for this boot loader yet. Don't think a fastboot cord will do much at the time.
Sent from Nexus 7 flo running SinLess ROM 4.2.2 using xda app-developers app

Did noone come up with a solution, because i did the same thing, with the framework-res.apk
i can make a fastboot cable if itll do any good without an unlocked bootloader. could i possibly push the most recent update.bin from amazon and restore the device to stock???
---------- Post added at 04:06 AM ---------- Previous post was at 03:10 AM ----------
i wouldnt take bricked for an answer and i found a fix
what i did was make sure the kindle was connected to adb and typed the following
adb reboot
adb wait-for-device shell su
the shell managed to snag the SU file and displayed # before the device looped thru all of the boot apps over and over, but then CMD froze.
so i tried this
adb reboot
adb wait-for-device shell su mount -o remount,rw -t ext4 /dev/block/platform/omap/omap.hsmmc.1/by-name/system /system
and in one line got root access and remounted the system as RW
my problem was that framework-res APK was replaced with ZIP so all i had to do was rename it
# cp /system/framework/framework-res.zip /system/framework/framework-res.apk
and success!!
# exit
$ exit
adb reboot
and she booted right up!!!!

First response so please be kind. My KFSOWI is stuck in the bootloop too. I have a factory cable and can get into fastboot but don't have any factory images to restore. Anyone have any ideas?

Do you get any adb access? I don't think casebook will be any help until someone unlocks the bootloader
Sent from my KFSOWI using XDA Premium 4 mobile app

[Q] Can't unlock the unlockscreen

i tried to install swype custom keyboard and it was a fail and when i rebooted as required after install i can't type in my password to unlock the screen because it says swype has stopped and i could just remove the app but i can't unlock my screen because i can't type in my password i tried ADB to remove the the app but that didn't work because it is a system app and it keeps on saying i don't have permission when i try the remove command and i tried to run the root command and su command on adb so i could remove it but it didn't work even though my kindle is rooted so now what do i do that is a alternative to a factory reset ( last choice )

You have to mount system as read-write before you rm anything on it. Run this first: /
Code:
su
mount -o rw,remount /system
rm oathandorfilenamegoeshere
that should do the trick
Sent from my Amazon Kindle Fire HD using Tapatalk

stunts513 said:
You have to mount system as read-write before you rm anything on it. Run this first: /
Code:
su
mount -o rw,remount /system
rm oathandorfilenamegoeshere
that should do the trick
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
it didn't work it said not permitted can you give me some ideas of what i might have done wrong

darth45013 said:
it didn't work it said not permitted can you give me some ideas of what i might have done wrong
Click to expand...
Click to collapse
if you mounted the system with read-write permissions i don't see any reason you wouldnt be able to do that short of not su-ing into root first.
Technically you can just restore the system partition without touching the userdata, i know srt wouldnt touch it but not sure about kffa, and you should be able to throw it into fastboot with
Code:
adb shell "su -c 'reboot bootloader'"

stunts513 said:
if you mounted the system with read-write permissions i don't see any reason you wouldnt be able to do that short of not su-ing into root first.
Technically you can just restore the system partition without touching the userdata, i know srt wouldnt touch it but not sure about kffa, and you should be able to throw it into fastboot with
Code:
adb shell "su -c 'reboot bootloader'"
Click to expand...
Click to collapse
sends back error device not found

darth45013 said:
sends back error device not found
Click to expand...
Click to collapse
hows that possible, you were already able to access a adb shell before this.

stunts513 said:
hows that possible, you were already able to access a adb shell before this.
Click to expand...
Click to collapse
its the only command that does it to

Then don't run it that way, try it this way:
Code:
adb shell
su
reboot bootloader
I just combined them for convenience last time so try running it like that.
Sent from my Amazon Kindle Fire HD using Tapatalk

h i will have to re try tomorrow also is their a way to open the default keyboard or set it to default via adb

Might be a configuration file that could be pulled and edited on a PC, most android apps I see have a database of some sorts, I have had to analyze a few of them to figure out some things before for a friend.
Sent from my Amazon Kindle Fire HD using Tapatalk

i have found the adb command for changeing defaults but i don't know how to use it for kindle fire hd

stunts513 said:
Might be a configuration file that could be pulled and edited on a PC, most android apps I see have a database of some sorts, I have had to analyze a few of them to figure out some things before for a friend.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Does anyone know the adb shell commands to change the default keyboard could really use them or I will have to do a factory reset

How do I do a factory reset on my kindle? I'm having the same issue with keyboard not comin up on lockscreen
Sent from my SPH-D710 using Tapatalk