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

[Q] Pushing recovery to device using ADB... please help!

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

My Rooted N5, & Android 4.4.2

Hey guys, I have a rooted N5 with CF Auto Root. I have been trying to do a update to 4.4.2. however, every time I download it and go to install, I get a error upon reboot, The update doesn't install. I'm still rather new with rooting phones. I was hoping someone could give me some insight on how to install this? I had a friend tell me its possible to manually install the update if I could locate the files?
Thanks!

Hi,
Take a look here: [INFO] Nexus 5 OTA Help-Desk, read closely

viking37 said:
Hi,
Take a look here: [INFO] Nexus 5 OTA Help-Desk, read closely
Click to expand...
Click to collapse
Ahh, excellent, thank you! However I'm a bit confused on what ADB Sideload is and how to use it. XD

ItsStormy said:
Ahh, excellent, thank you! However I'm a bit confused on what ADB Sideload is and how to use it. XD
Click to expand...
Click to collapse
Install the android-sdk platform- tools, look here for how to https://www.google.nl/url?sa=t&rct=...OWoMssTikMpokJ6TtwEND5A&bvm=bv.61190604,d.bGQ.
Then put the rom/OTA you want in the platform-tools folder, reboot in recovery and select adb sideload and then in cmd type `adb sideload namerom.zip` to flash the zip.

Ooops, got it sorted, thanks guys!

ItsStormy said:
Hi again, so I've gone over the tutorials. However when I attempt to go through the steps within http://forum.xda-developers.com/showthread.php?t=2523217 - I keep getting the error 'adb' is not recognized as an internal or external command, operable program or batch file. What am I doing wrong?
Thanks!
Click to expand...
Click to collapse
You have not created a path, look here http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/ item 5, 6 and 7.

Okay, so apparently thats only a issue if my phone isnt rooted judging by the first tutorial, it states I should follow section B.
1) Download the OTA.zip and copy to your phone.
2) Boot into recovery.
3) Flash the OTA just like you would a ROM.
4) Reboot.
However, When I boot into Recovery Mode, I get a error stating No Command.

ItsStormy said:
Okay, so apparently thats only a issue if my phone isnt rooted judging by the first tutorial, it states I should follow section B.
1) Download the OTA.zip and copy to your phone.
2) Boot into recovery.
3) Flash the OTA just like you would a ROM.
4) Reboot.
However, When I boot into Recovery Mode, I get a error stating No Command.
Click to expand...
Click to collapse
Do you have a custom recovery? choose B. If on stock recovery boot in a custom recovery by placing the custom recovery.img in fastboot folder and type in cmd `fastboot boot namerecovery.img`, let it load and flash the OTA in recovery and boot up.

gee2012 said:
Do you have a custom recovery? choose B. If on stock recovery boot in a custom recovery by placing the custom recovery.img in fastboot folder and type in cmd `fastboot boot namerecovery.img`, let it load and flash the OTA in recovery and boot up.
Click to expand...
Click to collapse
Eh. I don't believe so, or I'm not entirely sure, I'm sorry.

ItsStormy said:
Eh. I don't believe so, or I'm not entirely sure, I'm sorry.
Click to expand...
Click to collapse
If you have stock recovery there should stand 3e recovery on top, if so reboot into bootloader and do what i wrote in the prior post. Or sideload the OTA with adb in stock recovery.

Thanks for the help gee2012
I leave you in good hands :good:

I've followed the steps for system variables.
C:\Program Files (x86)\Android\android-sdk;C:\Android-adb
However, I'm still receiving adb is not recognized from the terminal.
Any idea what I might be doing wrong? I'm sorry about noobing this thread up.

ItsStormy said:
I've followed the steps for system variables.
C:\Program Files (x86)\Android\android-sdk;C:\Android-adb
However, I'm still receiving adb is not recognized from the terminal.
Any idea what I might be doing wrong? I'm sorry about noobing this thread up.
Click to expand...
Click to collapse
Dumb question, but is adb.exe in the android-adb folder?

jd1639 said:
Dumb question, but is adb.exe in the android-adb folder?
Click to expand...
Click to collapse
Now that you mention it, apparently not. I did however find this. And it is either in that location. I went into AVD Manager, but I don't see anywhere where I can install ''Android SDK Platform-tools"
The adb tool has moved to platform-tools/
If you don't see this directory in your SDK,
launch the SDK and AVD Manager (execute the android tool)
and install "Android SDK Platform-tools"
Please also update your PATH environment variable to
include the platform-tools/ directory, so you can
execute adb from any location.

ItsStormy said:
I've followed the steps for system variables.
C:\Program Files (x86)\Android\android-sdk;C:\Android-adb
However, I'm still receiving adb is not recognized from the terminal.
Any idea what I might be doing wrong? I'm sorry about noobing this thread up.
Click to expand...
Click to collapse
Best is to install the sdk straight to the C drive, so C:\android-sdk and not in a folder. The path vaiables to add would be \android-sdk\platform-tools.

Problem [BOOTLOADER]

Describing my problem :
Since yesterday my OPO did some random reboots. I was running Paranoid Android and it worked perfectly...
Yesterdayevening after it rebooted another time, my OPO didn't start at all... It seems that my bootloader won't load the OS.
This morning, I did a complete wipe and I've put the stock ROM from the CM site back on my OPO ( XNPH33R signed boot).
-Fastboot works
-Recovery works
-Bootloader won't load OS. ( only the One Plus logo pops up (not the bootanimation)). After that it reboots over and over...
Update 1 17:30 5/10/2014 :
I'm in a bootloop, I have no ROM. I have the TWRP recovery. And the bootloader is LOCKED.
So I tried to unlock the bootloader with the toolkit for the OnePlus one. ( I tried it also manually with cmd).
----WHAT IT DOES in CMD/ Phone-------
In CMD : " OKAY [0.012 s]
Finished. total time : 0.012 s
OPO : It opens up my TWRP recovery but it does not unlock the bootloader
Update 2 19:52 5/10/2014 :
I've been able to unlock the bootloader...
with the command " fastboot oem device-info" , I received :
Bootloader tampered : True
Bootloader unlocked : False ( because the toolkit only did " fastboot oem unlock " , I did an adb sideload with a zip "OnePlusOne-OnlyBootloaderToggle" from the thread
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912. Now my bootloader is back UNLOCKED.
I hope the bootloop will stop when I do a factory / reset.
10:40 6/10/2014 :
I tried several times to flash stock roms from the official site / from the forum. None of them 'work'.
Can someone please help me?? He still bootloops!!! How frustrating thazt is,I tried everything from threads on the forum. Nobody is ansering my thread. Any reason for that ?

My suggestion is this: grab one of the recovery flashable versions of CM11S from here, boot into your TWRP recovery and use adb to push the ROM zip to your phone, then use the install function in TWRP to flash it.
To push the zip to your phone you first need to put it in your adb/fastboot folder (wherever you have adb.exe and fastboot.exe located on your PC), make sure your phone is booted into TWRP and connected to your PC, open a command prompt from within your adb/fastboot folder (shift + right click anywhere in the folder, then select open command prompt here), and issue this command:
Code:
adb push <name of file.zip> /sdcard/
*Please note the '<' and '>' symbols are not included in the command.
From there just flash the ROM like you would flash any other ROM.
Transmitted via Bacon

Failure with E:
timmaaa said:
My suggestion is this: grab one of the recovery flashable versions of CM11S from here, boot into your TWRP recovery and use adb to push the ROM zip to your phone, then use the install function in TWRP to flash it.
To push the zip to your phone you first need to put it in your adb/fastboot folder (wherever you have adb.exe and fastboot.exe located on your PC), make sure your phone is booted into TWRP and connected to your PC, open a command prompt from within your adb/fastboot folder (shift + right click anywhere in the folder, then select open command prompt here), and issue this command:
Code:
adb push <name of file.zip> /sdcard/
*Please note the '<' and '>' symbols are not included in the command.
Transmitted via Bacon
Click to expand...
Click to collapse
Pushing the zip into sdcard :good:
Installing the zip gives a message about E:
example :
something with E: path
E: unable to wipe
E: error executing updater binary in zip 'sdcard/cm11.0... .zip
Proberly more

Are you sure you're attempting to flash one of the recovery flashable zips? What's the full filename?
Transmitted via Bacon

timmaaa said:
Are you sure you're attempting to flash one of the recovery flashable zips? What's the full filename?
Transmitted via Bacon
Click to expand...
Click to collapse
cm-11.0-XNPH33R-bacon-signed
Links
1. Recovery flashable zips of the complete ROMz:
XNPH22R
XNPH25R
XNPH33R
From your link
EDIT-----
1. I had flashed the stock recovery back.
2. Did a factory reset
3. Wiped cache
4. Wiped media
5. Flashed TWRP back
6. ADB push zip in /sdcard/
7. Flashed the zip SUCCESSFUL after these steps
I still have a bootloop

Have you tried to format your internal sd card and flash your zip. Remember if you format though you will lose everything on your sdcard. Make sure you backup everything first if you want to try this. Also if you do this you will have to push your zip back to the phone

Who can even solve this?...
playya said:
Have you tried to format your internal sd card and flash your zip. Remember if you format though you will lose everything on your sdcard. Make sure you backup everything first if you want to try this. Also if you do this you will have to push your zip back to the phone
Click to expand...
Click to collapse
My internal storage was already formatted. I just have the TWRP and the zip on my phone.
[Q] In the TWRP recovery menu in 'Advanced' what has to be between Copy Log to SD and Terminal Command? There is a blank spot ,there should be button normally?
How is it even possible i have nothing but the recovery and the zip and I still got a bootloop...
Is there somebody that knows something else that i can try?
Is it possible to flash perhaps with odin?

VictorByttebier said:
My internal storage was already formatted. I just have the TWRP and the zip on my phone.
[Q] In the TWRP recovery menu in 'Advanced' what has to be between Copy Log to SD and Terminal Command? There is a blank spot ,there should be button normally?
How is it even possible i have nothing but the recovery and the zip and I still got a bootloop...
Is there somebody that knows something else that i can try?
Is it possible to flash perhaps with odin?
Click to expand...
Click to collapse
definitely not odin thats Samsung my friend. Partition SD Card is whats missing in TWRP for you. I asked about formatting internal because a similar thing happened to my friend. We had to format internal then adb push recovery and rom and all was well again. If you have tried this recently then my bad but if you have not it wont hurt to try it again in that order
format internal
adb push recovery
adb push rom
reboot
Take a look in here as well http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061

Bootloop fixed
It finally worked!!! How weird that i already found a zip like on the thread but with XNPH33R and also with the persist and recovery.img and flash-all etc... but it didn't work.
Now i just have to update from the settings
At beginning I was convinced that a bootloop could be fixed with factory/reset would do it. Like it always worked on my previous smartphone.
Thank you playya and timmaaa for the responses!:good: You are awesome! See me sitting here with a

Accidentaly formatted all partions

I accidentally formatted all partition and now only have a TWRP. The TWRP only shows the start screen when i go to recovery.
Adb devices show me the device detected. I did a adb push and moved the stock rom 5.1.11 and my twrp recovery to the sdcard using the command adb push. I am struck here because i cannot get to the twrp screen which gives you option to install/wipe etc.
Can somebody please guide me if there is a way to recover or install the .zip files I have copied to sdcard. Thanks in advance

You need to fastboot flash the default stock rom, and then re root/install TWRP etc etc

Thank you for your response. Will that be adb fastboot flash stock.zip ? I am not sure if this would mess it up hence please confirm. Also, will it work if i use the fastboot to install twrp again and then flash the stock rom using its menu.

SachinGopal said:
Thank you for your response. Will that be adb fastboot flash stock.zip ? I am not sure if this would mess it up hence please confirm. Also, will it work if i use the fastboot to install twrp again and then flash the stock rom using its menu.
Click to expand...
Click to collapse
You need to go to this thread... https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Download the version of OOS you want (5.1.11) and unzip the contents in to a folder and run the flash-all.bat file and let it install to all partitions. Just follow this instructions in the thread and you will be fine.

Thank you so much for your response, but when I run this command I am getting " Waiting for device" option. I am only able to boot into twrp. I see the teamwin loading screen and its struck there. I am able to run adb commands and adb device shows the device details. I was also able to push the stock rom.zip through adb push command to /sdcard.
D:\OnePlus6Oxygen_22_OTA_015_all_1808102118_770880-FASTBOOT>flash-all-partitions-fastboot.bat
Do you want to wipe all the data ( Reccomended )[Y/N]?y
< waiting for any device >

Thank you so much it worked when I tried. Grateful . Will donate the Dev for that bat script.

SachinGopal said:
Thank you so much for your response, but when I run this command I am getting " Waiting for device" option. I am only able to boot into twrp. I see the teamwin loading screen and its struck there. I am able to run adb commands and adb device shows the device details. I was also able to push the stock rom.zip through adb push command to /sdcard.
D:\OnePlus6Oxygen_22_OTA_015_all_1808102118_770880-FASTBOOT>flash-all-partitions-fastboot.bat
Do you want to wipe all the data ( Reccomended )[Y/N]?y
< waiting for any device >
Click to expand...
Click to collapse
You need to be in fastboot mode.
Either adb reboot bootloader from inside android or from a powered off phone, hold Volume Up and power on.