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
Hello friends, I need your help...
Since i did a Dalvik-Cache clean on my phone, it got stuck on the bootlogo...
I can't find anywhere the stock rom and the scatter file to try amend this with SPTool since I dont have CWM or TWRP.
If there is a way to just get my files, pictures and music back will be enough help...
:crying:
Since no one bothered to help me, I managed to find a solution.
Will share here what i done.
1- Downloaded adb and put at C:/adb
2- Downloaded my phone usb/adb drivers.
3- Put my phone into factory mode by holding Volume-down key and power
4- By doing previous step and connecting the usb cable on the phone to pc, is possible to use adb commands
5- Used the command = adb pull /storage/sdcard0 C:/adb/Phone-Files (Can't start "adb shell" otherwise file/folder copy is blocked) from the cmd at the adb folder
6- Waited a hour and half to get everything from my phone to the folder = C:/adb/Phone-Files
I'm on my way to learn how to fix the Dalvik-Cache deletion.
Maybe getting the stock rom somewhere and using pull may solve... :fingers-crossed:
Ok, so this happened...
I was editting my build.prop so I could get apps that were unusable with my phone. So i downloaded the build.prop for the device that could run it, but instead of just changing the Moto G one, I replaced it on accident!
Every time I try to reboot it, the screen pops up for a little bit, but then fades to a pink screen then to black. I can't access the main part of my phone at all! I can still get into recovery mode, however. The main issue is the build.prop file, right?
I have a backup build.prop on my computer, but when I try to use adb to put in in, it doesn't recognize it. The phone also can't hold onto and battery charge anymore, either.
I need help to put my backup build.prop in. Please and thank you!
EDIT: I found out I can still sideload things, but I don't know if it will fix it.
1. Download TWRP 2.8.4.0 from HERE. and place it in the folder where you have ADB/Fastboot.
2. Try booting into the bootloader, then in your Fastboot Window, type fastboot flash recovery [recovery.img] where recovery.img is the name of the TWRP file.
3. You should now have flashed TWRP on your phone. Next, in the Bootloader, navigate down to RECOVERY using VOL DOWN then select it using VOL UP
4. In TWRP, go to Mount. Then, type in adb push file /sdcard/ where file is the name of the build.prop file
4. In TWRP, go to advanced, then select File Manager. Navigate to the folder that contains Build.prop and delete the file.
5. In the file manager, navigate to the /sdcard/ directory and copy the build.prop file to wherever it should be.
Let me know how that works out for you
Hello all.
I know there are many threads of this kind but nothing worked for me. So Please help!
I unlocked my bootloader, installed TWRP and flashed SuperSU binaries. Everything was working fine.
Then I wanted to flash cm12 nightly. So i downloaded the zip file and also the Gaaps.zip file. I transfered them to the phone and booted to recovery.
1. Then instead of wiping cache i wiped the whole system i.e factory data reset. So then i tried reboot it says NO OS INSTALLED! do you want to continue? After that "Your phone is not rooted. Install SuperSU? As i don't have the SuperSU files so it just reboots to the bootscreen and stays there. I can go to the recovery and fastboot mode.
2. then i booted to recovery and went to adb sideload. I have the ADB files on my desktop and pasted the ROM.zip file to the folder.
3. Then i tried the command adb sideload ROM.zip with my phone connected. But then a lot of coding appears in the cmd window and phone stays at adb sideload.
4. When i connect my phone to my pc in recovery It comes up as "One" in the disk drives. I open it and it has a folder named TWRP and inside thata file. Nothing else. The good thing is I have a nandroid backup of my device when it had SuperSU binaries.
*the "One disappears when I go to ADB sideload in my phone*
So can I transfer the backup to my phone in a separate folder named "Backups" and install it via restore in TWRP? Or do have to do something else?
Please help! Please! :crying:
You're already getting help for this here:
http://forum.xda-developers.com/showthread.php?t=3044924
Transmitted via Bacon
Hello guys! Hope I can find my salvation here. Hehe
I've been coding my Windows App that functions much like a custom recovery but I came into a problem which is bugging me
since last week. I can't seem to push files to my phone through adb. I have no idea why it wont work because pull is working fine, and shell as well. I tried remounting the file system as rw but still no luck. Hope you can help me out guys
My phone's Specification:
-Spreadtrum SC7731
-Running Android 5.1
My environment:
-Windows 10
-adb installed
-device drivers installed.
PS: If you are wondering why make a recovery that runs in PC while you can just have it in your phone?
-Unfortunately, I got a problem with that. I ported TWRP for my phone, but touch wont work which makes it useless.
Please help me sensei's!
Unlock the bootloader, flash a custom recovery (CMW for exmpl), put the root package at the root dir of the sdcard, now boot the phone into recovery mode and select install zip from sdcard then reboot
On pc, write the following command : "adb remount"
Gratzz you're now rooted and able to push files into system partition ��
Root at your own risk. Unlocking the bootloader makes you lose the warranty and will wipe your data .. So take a backup.
FinnTheHuman. said:
Unlock the bootloader, flash a custom recovery (CMW for exmpl), put the root package at the root dir of the sdcard, now boot the phone into recovery mode and select install zip from sdcard then reboot
On pc, write the following command : "adb remount"
Gratzz you're now rooted and able to push files into system partition ��
Root at your own risk. Unlocking the bootloader makes you lose the warranty and will wipe your data .. So take a backup.
Click to expand...
Click to collapse
Reread the OP. :fingers-crossed::fingers-crossed: I'm on Spreadtrum phone which means no source(yet.. or forever). I don't really know if you just misinterpreted the post or just trying to acquire post count. :3