Database Info

[Q] Idiotically deleted framework-res.apk, bricked my N1

Hi there,
I am such an idiot, I deleted the framework-res.apk from /system/framework/ and rebooted. You all know what had to happen: the Nexus with FRF91 won't boot anymore.
So I am asking for help: Is there any way to restore (i.e. put a stock framework-res.apk) in that folder? I have ADB tools and stuff installed.
Or is there any way to access the sdcard without booting the system? I could put an update.zip there and apply it.
Of course, I'd rather not delete my apps and stuff but still better than a bricked phone.
Any help would be great. Thanks a lot.

try this:
1. put a copy of framework-res.apk in your sdk/tools folder (this can be taken from a copy of the rom that you have installed at the moment)
2. boot your phone like usual; when the bootscreen appears, enter this into a command window directed at your adb (SDK/tools is the tools folder in my adb):
Code:
cd/
cd SDK/tools
adb reboot recovery
adb remount
adb push framework-res.apk /system/framework/framework-res.apk
adb reboot
this should put it into the correct folder and reboot the phone. give it a little time, whenever I flash a new FW-res it seems to take a little longer than when I have not to boot up. I have a desire, I am only presuming thats where it needs to go

Thank you very much for your answer.
Code:
adb reboot recovery
worked flawlessly when the boot animation was showing. Although it took quite a while until the device was recognized.
Now the Android dude with the exclamation mark is on the screen (recovery). Right now the device is not recognized. Therefore I cannot execute
Code:
adb remount
or any other adb commands.
This was one of my initial questions: how do I get to access the file-system from recovery?
Btw: is there any difference from manually (trackball + powerbutton) going to recovery to using adb?
Thanks

can you get into the green recovery screen by executing the .bat file after doing the reboot/recovery? I find sometimes it can take up to five tries to push the files correctly.
if you can do that, then you can execute the rest pretty easily.
you can even turn it into a 'mass storage device' to put an update.zip on the sdcard
edit: this one was the recovery I was meaning.
the other way to get into that is
Code:
How to boot in Recovery Mode
Boot the phone while holding down the VOLUMEDOWN-key.
Navigate to RECOVERY with the the VOLUMEDOWN-key.
Press the POWER-key to select.
anything other than the information above and I can't be much use, this is about as far as my adb and android knowledge extends sorry.
GL

yes, I do get the recovery screen but I cannot execute adb commands from there. Any hints?

Well, if you can't access terminal (console) from recovery, try fastboot, and reflash the whole firmware WITHOUT wiping. That should do the trick!

Ok, will try to do that. What I've done so far is copied update-nexusone-FRF91-stock-noradio-signed.zip to the sdcard's root, renamed it to update.zip and tried to install it via the stock bootloader (recovery with Volume UP + Powerbutton). This failed. Am I using a wrong Rom? Should I try to install this via fastboot?

wouldnt hurt. my next suggestion would then be an untouched rom (maybe 2.1 so you dont have a problem with the bootloader changing versions)

wouldn't fastboot allow me to copy the file to the system? I found this command for fastboot:
Code:
flash <partition> [ <filename> ] write a file to a flash partition
I think I will just have to flash the system-image:
Code:
fastboot flash XXX YYY - This will flash XXX partitionn with YYY image.
e.g: fastboot flash system system_update.img will flash/update your system partition with an image called system_update
Taken from http://forum.xda-developers.com/showthread.php?t=619153
Correct?
Then I need to find a system.img

Sorry for this double-post but I guess you guys don't come back, otherwise...
Can anyone provide a system.img for me? I've just tried the one from the stock PASSIMG_Passion_Google_WWE_1.01.1700.1_ERD79_release_signed.zip but received
Code:
sending 'system' (116663 KB)... OKAY
writing 'system'... INFOs
FAILED (remote: signature verify fail)
Edit: I have a LOCKED bootloader

can you either try using a stock rom rather than a cooked one, or try resigning the rom you are trying to flash?
Sent from my HTC Desire using XDA App

I have also accidentally deleted my framework-res.apk, and my X10 won't boot (duh). Now When I use the command "adb remount", I get the error message: "remount failed: Operation not permitted". How do I push framework-res.apk to my phone now?

I thought I was using a stock rom with
PASSIMG_Passion_Google_WWE_1.01.1700.1_ERD79_relea se_signed.zip
update-nexusone-FRF91-stock-noradio-signed.zip
How does resigning work? I guess there are tools for this. Never used a cooked rom so far.

signing roms: http://androidforums.com/developer-101/8665-how-signing-roms.html
try signing it again, then installing it.
the -signed extension to me sounds like someone dl'd the original, edited and resigned it (eg: to remove the radio). This edit may have been the reason why they are failing the verification. I dont know enough about the difference between fastboot and recovery to know any other reasons why it might fail in there.
this may be why it is not working in FASTBOOT
back to ADB, if you try it via that method and it fails, try killing the adb task in task manager, then try again. for me adb works after that more often than not.

nzdcoy said:
signing roms: http://androidforums.com/developer-101/8665-how-signing-roms.html
try signing it again, then installing it.
the -signed extension to me sounds like someone dl'd the original, edited and resigned it (eg: to remove the radio). This edit may have been the reason why they are failing the verification. I dont know enough about the difference between fastboot and recovery to know any other reasons why it might fail in there.
this may be why it is not working in FASTBOOT
back to ADB, if you try it via that method and it fails, try killing the adb task in task manager, then try again. for me adb works after that more often than not.
Click to expand...
Click to collapse
Okay, signing worked for the zip file. But the system.img is still not working.
What do you mean with adb? What should I do? I guess the problem is that the system is not fully booted and I don't get root at that stage.

which rom have you tried to flash in FASTBOOT? I would expect PASSIMG_Passion_Google_WWE_1.01.1700.1_ERD79_relea se_signed.zip to work since it is a stock rom, but the other one looks like it has been repackaged.
knox420 said:
Ok, will try to do that. What I've done so far is copied update-nexusone-FRF91-stock-noradio-signed.zip to the sdcard's root, renamed it to update.zip and tried to install it via the stock bootloader (recovery with Volume UP + Powerbutton). This failed. Am I using a wrong Rom? Should I try to install this via fastboot?
Click to expand...
Click to collapse
can you try doing this with the PASSIMG_Passion_Google_WWE_1.01.1700.1_ERD79_relea se_signed.zip one?
if possible try doing it without resigning the zip first.

Alright, none of this worked. I tried it all but in the end I had to realize I lack too much knowledge.
I wiped everything and reinstalled Cyanogen Mod 6 RC3. System's up and running.
Thanks for any help, though.

Or is there any way to access the sdcard without booting the system? I could put an update.zip there and apply it.
Click to expand...
Click to collapse
You mean get the card out of the phone and plug into a card reader?

cryshop said:
You mean get the card out of the phone and plug into a card reader?
Click to expand...
Click to collapse
What I meant -back in the days- was that I wanted to access the card while still in the phone. From the bootloader. Now this is possible with ClockworkMod or AmonRa Recovery.
Thanks anyway

[ADB] Trying to backup - Birck? Hope not

Hi! I was trying to backup my Orange Monte Carlo following a Portuguese tutorial but I'm stuck in the middle and I've got no help! Hope you can provide some! These are the steps I followed (translated)
1 - Install ADB Made Easy;
2 - Open cmd;
3 - Activate cellphone debug mode;
4 - Connect via usb (without mass storage) and install drivers if request [it was requested and i installed];
5 - Run adb devices, it should show your device [it did];
6 - Run adb reboot bootloader, your cellphone will boot in Fastboot, wich is an Android image without menus [correct until here];
7 - Run fastboot devices, your device yor a question mark(?) should show up (advance to next step), else you miss drivers [step not completed];
cmd says 'fastboot' is not recognized as a command. Now my phone is stuck connected to the computer with an adriod pick and I have no clue on what to do next!

Don't know where you were going with this but to reboot your phone just pull the battery ..
Not bricked

shanman-2 said:
Don't know where you were going with this but to reboot your phone just pull the battery ..
Not bricked
Click to expand...
Click to collapse
Thank you! Do you have any idea why the last command doesn't work? I believe it has something to do with file location... I'm trying to backup my Monte Carlo. Next steps were to "fastboot boot recovery.img" and then backup.

It should be in the platform-tools directory of the android-sdk. Verify that it's there...if so cd to that directory and it should work

I already fixed it for myself, thanks! Now I can't seem to be able to install clockwork!
Doing <<fastboot boot "C:\Users\R&J\Downloads\recovery.img">> reboots the device but doesn't enter recovery.
Doing <<fastboot flash recovery "C:\Users\R&J\Downloads\recovery.img">> , <<fastboot reboot>> and <<adb wait-for-device reboot recovery>> results the phone entering android's default recovery (no acess to backup feature).
Any way to help? Thank you!

The first command <<fastboot flash recovery "C:\Users\R&J\Downloads\recovery.img">> is trying to write the recovery.img you downloaded to a recovery partition on your device. It may not be overwriting the original recovery.
try changing permissions by doing
adb shell
su
chmod 777 /recovery
then try to flash again

Lol it seems like I have been luck enough to solve my own problems, I have sucessfully installed ClockworkMod Recovery 4.0.1.4 unofficial MoDaCo Edition using a bat file . Now I can't seem to find a way to flash recovery back to stock. I though this was an option inside the modded recovery. Any tips? Thanks again!
EDIT: I have the stock recovery file . God... this tutorials I'm folowing aren't that noob friendly...

HELP. Battery died, now phone will not get past HTC Logo Screen

I have been running AOKP. I have tried booting the phone numerous time and have had no luck. Power+Vol down doesn't get me anywhere either, it is just stuck on the "htc quietly brilliant - This build is for devlopment purposes only. Do not distribute outside of HTC ......"
Is it possible being only on this screen to use adb to clear cache, or is the phone toast? How can the battery dying kill the phone on the next boot?

SilentLunatic said:
I have been running AOKP. I have tried booting the phone numerous time and have had no luck. Power+Vol down doesn't get me anywhere either, it is just stuck on the "htc quietly brilliant - This build is for devlopment purposes only. Do not distribute outside of HTC ......"
Is it possible being only on this screen to use adb to clear cache, or is the phone toast? How can the battery dying kill the phone on the next boot?
Click to expand...
Click to collapse
Have you charged it? I know it sounds obvious lol... but you never know.
And try to see if you can get adb initializing by booting your phone, letting it sit at the bootsplash for 10 seconds or so, and then in a command prompt type "adb devices" and see if you get your device's serial number back.

rohan32 said:
Have you charged it? I know it sounds obvious lol... but you never know.
And try to see if you can get adb initializing by booting your phone, letting it sit at the bootsplash for 10 seconds or so, and then in a command prompt type "adb devices" and see if you get your device's serial number back.
Click to expand...
Click to collapse
Will def try. I did get it booted into CWM. It says it cannot mount the sd card. I do not know how to push a file to it if I can't mount it. I cannot see the AOKP.zip file I used either when I try to "choose update from zip".
Trying the adb now though. Will be back with results.

SilentLunatic said:
Will def try. I did get it booted into CWM. It says it cannot mount the sd card. I do not know how to push a file to it if I can't mount it. I cannot see the AOKP.zip file I used either when I try to "choose update from zip".
Trying the adb now though. Will be back with results.
Click to expand...
Click to collapse
Is the CWM recovery that you have the one with the fixed adb?
Go to command prompt and when in CWM run adb devices.
If you get your device, to mount your sdcard then run this:
adb shell mount /sdcard
Then try pushing the update.zip again.
If that doesn't work, then from CWM and adb again, reboot into bootloader (adb reboot bootloader), get into fastboot mode (wait till it says "fastboot usb"), and then run the RUU.

rohan32 said:
Is the CWM recovery that you have the one with the fixed adb?
Go to command prompt and when in CWM run adb devices.
If you get your device, to mount your sdcard then run this:
adb shell mount /sdcard
Then try pushing the update.zip again.
If that doesn't work, then from CWM and adb again, reboot into bootloader (adb reboot bootloader), get into fastboot mode (wait till it says "fastboot usb"), and then run the RUU.
Click to expand...
Click to collapse
X:\Android SDK\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT24LW304682 device
X:\Android SDK\platform-tools>adb shell mount /sdcard
- exec '/system/bin/sh' failed: No such file or directory (2) -
Guess I'm going to try the RUU now...

SilentLunatic said:
X:\Android SDK\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT24LW304682 device
X:\Android SDK\platform-tools>adb shell mount /sdcard
- exec '/system/bin/sh' failed: No such file or directory (2) -
Guess I'm going to try the RUU now...
Click to expand...
Click to collapse
RUU cannot update the phone. Encountered Error [155]
Currently sitting on the black htc logo screen when it's trying to flash the stock image.

SilentLunatic said:
RUU cannot update the phone. Encountered Error [155]
Currently sitting on the black htc logo screen when it's trying to flash the stock image.
Click to expand...
Click to collapse
I wanted to note that I did re-lock the bootloader.

Fixed! Beat the phone on the desk, ran for the 5th time and it worked. Flashing TWRP now and back to AOKP I come. Mods please close this thread, and HUGE thanks to rohan32.

Help tf101g

hello peopleI need your help without any information someone deleted all my files tf101g
TF101G entering recovery mode with cwm
cwm 5.5.0.4 but this does not allow me to upgrade from external sd card. I tried to flash from w7 with some programs, wheelie, nvflash, tubuntu, oneclickrecovery among others.
adb shell
exec ' system bin sh' failed no such file or directory 2
pushing something. permission denied
NVFLASH
rcm version 0x4 command send failed (usb write failed)
can someone help me

Since you have a TF101G, NVFlash is not an option.
Does your device show up as an ADB device in windows when you boot to recovery?
Another thought- if you hold VOL DOWN and POWER for 12-15 seconds and release when you see the white text (and don't hit vol up to enter RCK), does it boot up?
If so, you just have a recovery bootloop and can boot using this method until we fix it.
If not, back to my first thought - if it shows in the device manager, update the drivers using the naked drivers 0.72.
Then try typing "adb devices" at a command prompt and see if it is recognized via USB.
If so, push your firmware using the following:
adb push firmware.zip /sdcard/
If that succeeds, you should be able to flash the firmware from recovery.

frederuco said:
Since you have a TF101G, NVFlash is not an option.
Does your device show up as an ADB device in windows when you boot to recovery?
Another thought- if you hold VOL DOWN and POWER for 12-15 seconds and release when you see the white text (and don't hit vol up to enter RCK), does it boot up?
If so, you just have a recovery bootloop and can boot using this method until we fix it.
If not, back to my first thought - if it shows in the device manager, update the drivers using the naked drivers 0.72.
Then try typing "adb devices" at a command prompt and see if it is recognized via USB.
If so, push your firmware using the following:
adb push firmware.zip /sdcard/
If that succeeds, you should be able to flash the firmware from recovery.
Click to expand...
Click to collapse
when i try
adb push firmware.zip /sdcard/
adb push firmware.zip /sdcard/ permission denied

Try fixing permissions in CWM. I think it is under advanced.

[Q] Cant get to recovery mode

Hello,
I'm trying to get the timeshift video mod working on my Z1 C6603, android version 4.2.2. The last step is to install the mod via recovery mode, which I can't boot to. I've tried the power + volume button method but it boots the phone into safe mode. Any ideas how I could get to recovery mode?

varsketis said:
Hello,
I'm trying to get the timeshift video mod working on my Z1 C6603, android version 4.2.2. The last step is to install the mod via recovery mode, which I can't boot to. I've tried the power + volume button method but it boots the phone into safe mode. Any ideas how I could get to recovery mode?
Click to expand...
Click to collapse
Yes, no problem!
If you're rooted (which I expect that you probably are), just open up (or download and install if you need to) Terminal Emulator and execute this command:
Code:
su
reboot recovery
Alternatively, if you don't have/don't want Terminal Emulator, if you connect your device to your PC via ADB, this command will get you into recovery mode, too:
Code:
adb shell
reboot recovery
Hope this helps! :good:

ИΘΘK¡€ said:
Yes, no problem!
If you're rooted (which I expect that you probably are), just open up (or download and install if you need to) Terminal Emulator and execute this command:
Code:
su
reboot recovery
Alternatively, if you don't have/don't want Terminal Emulator, if you connect your device to your PC via ADB, this command will get you into recovery mode, too:
Code:
adb shell
reboot recovery
Hope this helps! :good:
Click to expand...
Click to collapse
Thanks for your help.
Yes, the phone is rooted.
Terminal Emulator only rebooted the phone after a long pause and ADB tool says "operation not permitted". It's a work phone so it might have theft protection which blocks me from accessing recovery mode. Anything else I could try?

Try
adb reboot recovery

varsketis said:
Thanks for your help.
Yes, the phone is rooted.
Terminal Emulator only rebooted the phone after a long pause and ADB tool says "operation not permitted". It's a work phone so it might have theft protection which blocks me from accessing recovery mode. Anything else I could try?
Click to expand...
Click to collapse
Try:
Code:
adb shell
su
reboot recovery

root-expert said:
Try:
Code:
adb shell
su
reboot recovery
Click to expand...
Click to collapse
Hi,
Phone gets rebooted normally after doing this. Maybe it needs to get a custom recovery installed?

varsketis said:
Hi,
Phone gets rebooted normally after doing this. Maybe it needs to get a custom recovery installed?
Click to expand...
Click to collapse
When you type "su" does it changes the $ symbol to # ?
If you have # means that you have root access if not you don't have...

@varsketis, yes, a custom recovery should resolve your problem. I'd recommend either ClockworkMod or TWRP (TeamWin Recovery Project).
@root-expert, if varsketis didn't have root, when he executed these commands:
Code:
su
reboot recovery
-OR-
Code:
adb shell
su
reboot recovery
...he would have gotten an "Access denied" error. However, since he was able to get his device to reboot in some way or another using the shell, it means that he does have a root shell (#) usable.