Related
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
I have installed the 5.5.0.4 recovery from Koush via Rom Manager. That recovery is broken and it will not let me flash another recovery. I am asking someone who knows how to push a different custom recovery ( like rogue recovery http://bit.ly/ADptUO ) to the device using ADB, to write a step by step guide with all the commands and necessary files to do so. This will help many people who are stuck in the same situation that I have found myself in. Any help will be appreciated, thank you.
This might get you part of the way there. There might be something in there about flashing a new recovery too.
http://forum.xda-developers.com/showthread.php?t=1530337
gee one said:
This might get you part of the way there. There might be something in there about flashing a new recovery too.
http://forum.xda-developers.com/showthread.php?t=1530337
Click to expand...
Click to collapse
It says to type the command though ADB while in CWR... my device does not show up in ADB while in recovery.
If you have access to the rom, you can copy your new recovery to the internal sdcard. You can also type the command in the rom with adb or terminal, but be careful since anything that you have in the staging partition will flash after you type the commands and then reboot. So, 1) copy rom to the internal sdcard, 2) reboot to recovery, 3) flash new recovery (nothing will happen yet) 4) reboot to the rom) 5) type commands in adb 6) reboot 7) then make a step by step guide for the next person.
sent from my cyanogen(mod) vision
So basically I found out just today we have Cyanogenmod 10.2 >.<
I downloaded the Joilaroi version, flashed it in TWRP 2.6xx and then suddenly "E: Error in updating binary script" did a bit of googling and found out that it's a common problem with TWRP > 2.3.3.0
So I was about to downgrade it to 2.3.3.0 or temp boot into CWM. Connected my phone to my laptop and went to bootloader, then did Adb devices....the list was empty.
Reinstalled HTC drivers, used different USB port...nothing.
TL;DR : Phone doesn't get recognized in Bootloader mode, Can't flash ROM, Can't replace recovery. Help!
AIndoria said:
So basically I found out just today we have Cyanogenmod 10.2 >.<
I downloaded the Joilaroi version, flashed it in TWRP 2.6xx and then suddenly "E: Error in updating binary script" did a bit of googling and found out that it's a common problem with TWRP > 2.3.3.0
So I was about to downgrade it to 2.3.3.0 or temp boot into CWM. Connected my phone to my laptop and went to bootloader, then did Adb devices....the list was empty.
Reinstalled HTC drivers, used different USB port...nothing.
TL;DR : Phone doesn't get recognized in Bootloader mode, Can't flash ROM, Can't replace recovery. Help!
Click to expand...
Click to collapse
Why don't you flash with terminal emulator?
Just put recovery.img in the root of your sdcard
Open terminal type
su
cd sdcard
flash_image recovery recovery.img
That's it
Sent from my gt-1900 using xda premium
Taha Haq said:
Why don't you flash with terminal emulator?
Just put recovery.img in the root of your sdcard
Open terminal type
su
cd sdcard
flash_image recovery recovery.img
That's it
Sent from my gt-1900 using xda premium
Click to expand...
Click to collapse
That's what I'm doing now but I need a proper solution :/ Basically Windows won't recognize my phone through fastboot. I'd rather not keep installing CM9 again and again after a failed flash, you know?
AIndoria said:
That's what I'm doing now but I need a proper solution :/ Basically Windows won't recognize my phone through fastboot. I'd rather not keep installing CM9 again and again after a failed flash, you know?
Click to expand...
Click to collapse
install htc drivers and make dure you cleared the all registry and files from your previous installation and connect your device
open cmd and go to the folder where you placed adb and type command
adb kill-server =>it will close all adb processes running at that time
adb start-server => it will start new adb process
adb devices=> to reconize your device
if it shows your device then through fastboot command flash the recovery
but make sure you have all neccessary binary files in that folder for adb and fastboot
hit thanks if helped
AIndoria said:
That's what I'm doing now but I need a proper solution :/ Basically Windows won't recognize my phone through fastboot. I'd rather not keep installing CM9 again and again after a failed flash, you know?
Click to expand...
Click to collapse
You can try installing the newer Drivers.
Else your usb port may be broken. that is also a possiblity
Does adb push work in recovery or fastboot mode. I've seen a lot of forms use this method but it did not work for me. In recovery mode the device is not been recognized when i type in adb devices, it throws no devices found. but all the adb commands works fine during normal run.
blackuse said:
Does adb push work in recovery or fastboot mode. I've seen a lot of forms use this method but it did not work for me. In recovery mode the device is not been recognized when i type in adb devices, it throws no devices found. but all the adb commands works fine during normal run.
Click to expand...
Click to collapse
You need to enable ADB mode in recovery for it to work.
fastboot is for bootloader mode only.
Adb push works in recovery, not fastboot. You need to get the drivers installed while your in recovery. Ate you on Windows pc? Open device manager and you'll see a device with an exclamation make on it. You need to installs the drivers for that. Go to browse for drivers and there will be an option to install from a list on the computer. Find the android adb drivers
Sent from my Nexus 5 using XDA Free mobile app
Just a note:
adb doesn't work in stock recovery other then when using adb sideload.
Custom recoveries support all adb commands.
El Daddy said:
Just a note:
adb doesn't work in stock recovery other then when using adb sideload.
Custom recoveries support all adb commands.
Click to expand...
Click to collapse
Good point
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Adb push works in recovery, not fastboot. You need to get the drivers installed while your in recovery. Ate you on Windows pc? Open device manager and you'll see a device with an exclamation make on it. You need to installs the drivers for that. Go to browse for drivers and there will be an option to install from a list on the computer. Find the android adb drivers
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
i did as per ur instruction and now it shows the device in adb devices but i'm not able to perform any commands. i use CWM.
blackuse said:
i did as per ur instruction and now it shows the device in adb devices but i'm not able to perform any commands. i use CWM.
Click to expand...
Click to collapse
Please elaborate on "i'm not able to perform any commands"
rootSU said:
Please elaborate on "i'm not able to perform any commands"
Click to expand...
Click to collapse
only "adb devices" works when i use adb push it does not throw any error but the file is not found in the device.Is there any restriction to the commands used in the recovery mode.
blackuse said:
only "adb devices" works when i use adb push it does not throw any error but the file is not found in the device.Is there any restriction to the commands used in the recovery mode.
Click to expand...
Click to collapse
Put the file you're trying to push in the same folder as abd.exe. Open a command window in that folder. It's sounds like you have a path issue and adb is not finding the file
Sent from my Nexus 5 using XDA Free mobile app
blackuse said:
only "adb devices" works when i use adb push it does not throw any error but the file is not found in the device.Is there any restriction to the commands used in the recovery mode.
Click to expand...
Click to collapse
Could you screenshot the cmd prompt please?
the adb push works fine in normal run. but none of the command seems to work during recovery.adb commands works fine even in fastboot mode
blackuse said:
the adb push works fine in normal run. but none of the command seems to work during recovery.adb commands works fine even in fastboot mode
Click to expand...
Click to collapse
What recovery are you using? If you're using cwm, it mounts /sdcard incorrectly as /data/media instead of /data/media/0
Mount data and ls /data/media
Sent from my Nexus 5 using Tapatalk
rootSU said:
What recovery are you using? If you're using cwm, it mounts /sdcard incorrectly as /data/media instead of /data/media/0
Mount data and ls /data/media
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
YES i'm using CWM . "Mount data and ls /data/media" how do I do that
blackuse said:
YES i'm using CWM . "Mount data and ls /data/media" how do I do that
Click to expand...
Click to collapse
in recovery, go to "mounts and storage" and press "mount data".
Then in command prompt type
Code:
adb shell
to get into adb shell
Then type
Code:
ls /data/media
Thats LS in lower case and yes, it is case sensitive.
This will list the contents of /data/media - which is the location cwm uses as /sdcard. This hasn't been /sdcard since android 4.1.2 though.... I bet ls lists all those missing files you've been pushing.
This is one reason you should use either Philz or TWRP. Antiquated settings in CWM
blackuse said:
YES i'm using CWM . "Mount data and ls /data/media" how do I do that
Click to expand...
Click to collapse
Instead of push /sdcard use push /data/media
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Instead of push /sdcard use push /data/media
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thats the same.. push /data/media/0
Although just change recovery from cwm and continue to use /sdcard
Otherwise Nandroid backups will go missing too
Sent from my Nexus 5 using Tapatalk
rootSU said:
Thats the same.. push /data/media/0
Although just change recovery from cwm and continue to use /sdcard
Otherwise Nandroid backups will go missing too
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i tried out lots of adb push commands and finally understood "/sdcard/" which is supposed to be "/data/media/0/" is still "/data/media/ in CWM and yes all my CWM nanodroid backups are located in "data/media/CWM". how do i permanently make CWM to use "/data/media/0/" for sdcard
and i assume adb reboot does not work in recovery mode
blackuse said:
i tried out lots of adb push commands and finally understood "/sdcard/" which is supposed to be "/data/media/0/" is still "/data/media/ in CWM and yes all my CWM nanodroid backups are located in "data/media/CWM". how do i permanently make CWM to use "/data/media/0/" for sdcard
and i assume adb reboot does not work in recovery mode
Click to expand...
Click to collapse
You can't with cwm. Use philz or twrp though twrp won't be compatible with your existing backups.
Sent from my Nexus 5 using Tapatalk
I wiped the system thinking it was part of the system factory reset in TWRP but i didnt know that it would result in it saying NO OS INSTALLED. i read other similar threads about this problem but dont exactly understand what to do and how to restore my phone. i have a nandroid backup but its on my pc and not the internal storage on the phone. im fairly new to this so those replying, please explain exactly what to do. Im so scared about what to do now :crying::crying::crying:
Don't be scared its common and very, very easy to fix
Now I don't use TWRP so I have no idea of the directory structure so I can't advise you exactly.
But what you will essentially do is use adb push to get the files on your phone.
Click the link in my signature to go to the sticky roll up thread. All the important threads are linked there. Y
In that thread you'll quickly find my adb info thread. This should be most of what you need to know
Sent from my Nexus 5 using Tapatalk
First relax, your phone is not ruined. I assume you have a custom recovery. You're going to have to either side load a rom zip using adb or adb push a rom zip onto your phone and flash it in recovery.
Edit, OP you'll want to push the rom to /sdcard/Download. That'll put it into the folder twrp defaults to look for it.
Sent from my Nexus 5 using XDA Free mobile app
Well, you have three pretty easy options.
TWRP supports ADB commands, but the stock Google driver won't work. If you install the Universal ADB Driver you should be able to push your backup to your device (adb push [file location on your computer] [where to push on your phone])
http://www.koushikdutta.com/post/universal-adb-driver
You could also flash a ROM through adb sideload. Download a ROM zip to your computer, then in TWRP choose Advanced -> ADB Sideload. Then run "adb sideload [zip file]" to sideload the ROM you downloaded.
Last, you can restore to the Nexus Factory Image.
https://developers.google.com/android/nexus/images
All of these options will require you to have the Android SDK setup on your computer. The link for the factory images has instructions on how to get that installed.
raptir said:
]
All of these options will require you to have the Android SDK setup on your computer. The link for the factory images has instructions on how to get that installed.
Click to expand...
Click to collapse
Luckily its easier install adb and fastboot than the ask method. Just go to the thread mentioned earlier and use the 15 second installer
OP, no matter what you'll need run that installer
Sent from my Nexus 5 using Tapatalk
All these guys have it spot on! I just wanted to mention that when you install a ROM system gets wiped automatically as this is a parameter in the zip's updater-script.
So in other words there is really no reason to wipe system manually. Just let the install process do it for you. If u wipe system manually and then you realize you do not have a ROM zip or a nandroid only ADB can save you. So this way you can save yourself a headache
raptir said:
Well, you have three pretty easy options.
TWRP supports ADB commands, but the stock Google driver won't work. If you install the Universal ADB Driver you should be able to push your backup to your device (adb push [file location on your computer] [where to push on your phone])
\
You could also flash a ROM through adb sideload. Download a ROM zip to your computer, then in TWRP choose Advanced -> ADB Sideload. Then run "adb sideload [zip file]" to sideload the ROM you downloaded.
Last, you can restore to the Nexus Factory Image.
All of these options will require you to have the Android SDK setup on your computer. The link for the factory images has instructions on how to get that installed.
Click to expand...
Click to collapse
I downloaded everything and ran the flash-all . bat file but its currently been on < waiting for device > for a while now. i think it didnt detect the phone although it is connected through the USB :/
thauri said:
I downloaded everything and ran the flash-all . bat file but its currently been on < waiting for device > for a while now. i think it didnt detect the phone although it is connected through the USB :/
Click to expand...
Click to collapse
Did you or did you not read my adb and fastboot thread?
And WHY are you going for the last resort first???
You really need to chill out and read things because I don't think you're thinking straight
Sent from my Nexus 5 using Tapatalk
raptir said:
Well, you have three pretty easy options.
TWRP supports ADB commands, but the stock Google driver won't work. If you install the Universal ADB Driver you should be able to push your backup to your device (adb push [file location on your computer] [where to push on your phone])
You could also flash a ROM through adb sideload. Download a ROM zip to your computer, then in TWRP choose Advanced -> ADB Sideload. Then run "adb sideload [zip file]" to sideload the ROM you downloaded.
Last, you can restore to the Nexus Factory Image.
All of these options will require you to have the Android SDK setup on your computer. The link for the factory images has instructions on how to get that installed.
Click to expand...
Click to collapse
rootSU said:
Luckily its easier install adb and fastboot than the ask method. Just go to the thread mentioned earlier and use the 15 second installer
OP, no matter what you'll need run that installer
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
yeah i did download the 15 second ADB installer but my computer isnt detecting the phone connected when i ran the flash-all . bat file.
1) you need to read the whole of my thread. There are drivers to install
2) Still dont understand why you're running flashall bat when you can just adb push your backup to your sdcard. You know you lose all your data when you do that?
Sent from my Nexus 5 using Tapatalk
rootSU said:
1) you need to read the whole of my thread. There are drivers to install
2) Still dont understand why you're running flashall bat when you can just adb push your backup to your sdcard. You know you lose all your data when you do that?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
ok yes im reading your thread and doing the ADB commands. i have a question though, the multi-line input for the code to ADB push goes in cmd right? how is that possible?
Yes
Type one line, press enter, type another line, press enter
Sent from my Nexus 5 using Tapatalk
rootSU said:
Yes
Type one line, press enter, type another line, press enter
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
when i press enter after adb shell and mount data, it says data failed : Device or Resource busy
thauri said:
when i press enter after adb shell and mount data, it says data failed : Device or Resource busy
Click to expand...
Click to collapse
If "mount data" shows device or resource busy, then that usually means it is already mounted.
rootSU said:
If "mount data" shows device or resource busy, then that usually means it is already mounted.
Click to expand...
Click to collapse
i did everything but in the last part, it doesnt transfer the recovery files to the phone
Edit: The files are transferring successfully but only one at a time.
EDIT 2: All the necessary files were transferred but the TWRP recovery mode isnt detecting it as a restore option
Messing up is scary but it's a great opportunity to learn. I think you'll get through this just fine.
thauri said:
i did everything but in the last part, it doesnt transfer the recovery files to the phone
Edit: The files are transferring successfully but only one at a time.
EDIT 2: All the necessary files were transferred but the TWRP recovery mode isnt detecting it as a restore option
Click to expand...
Click to collapse
It must be in the exact location twrp needs to see it.
Sent from my Nexus 5 using Tapatalk
rootSU said:
It must be in the exact location twrp needs to see it.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I did, I put it in the backup folder in TWRP where all the other backups usually were
thauri said:
I did, I put it in the backup folder in TWRP where all the other backups usually were
Click to expand...
Click to collapse
Take a new backup, then delete everything in the new backup folder and move everything from your old backop into the new backup folder,
So for example
Code:
adb shell
mount /data
cd /data/media/0/TWRP/backups
ls
^^ This should list the contents... You should see your old backup and your new backup (which will be mostly empty).
Lets pretend your new backup folder is 22222222 and your old backup folder is 11111111
Code:
rm -Rf 222222222/*
mv 111111111/* 222222222
The first command is a remove (recursive) of the contents of the new backup. second command mvs contents of old backup into new backup folder,
Try that.
I don't know TWRP so my assumptions of the path may be incorrect
Someone else posted twrp default path as /sdcard/downloads - try that.