So basically I deleted TW Recovery and put on the stock stuff... Now i am boot looped but i can get into stock recovery and FTM... I had root... I don't know for sure now... SU command in abd doesn't return a denied but it doesnt update commands to # either...
So far that's about all i know... I have no mount in id... pushing tw rcovery img returns missing an apk... pushing the full apk returns invalid apk...
Related
my magic is TIM's G2
the rom is myhero 2.0.5 but the recovery is too old, so i want to flash the recovery to Amon's recovery 1.5.2.
but when i flash_image recovery /sdcard/recovery.img
some error type. all is "out of memory". then i open the phone, i can't into the recovery.
it's so bay. now i can flash 1.2.3H into my Magic, i want flash 1.5.2, help please.
It won't work if you only type that. I assume you're using a terminal emulator. I'm pretty sure you only forgot the mount command, but I'll go trough everything to be sure.
All you need to to is to flash the recovery image again. As you're having MyHero, I assume you're having a 32A. Therefore, make sure you have the recovery-RA-sapphire-v1.5.2H.img, not the recovery-RA-sapphire-v1.5.2G.img.
Copy the file to the root of your SD, no need to rename it.
Open up your terminal emulator, and type:
Code:
su
You should get a root request, accept it. Then type in:
Code:
mount -a
Don't worry if you're getting errors here, that's normal. Lastly, type in the following.
Code:
flash_image recovery /sdcard/recovery-RA-sapphire-v1.5.2H.img
It's just normal to get errors here too. Or, at least I do.
Start your phone in recovery, and it should work.
tks
i will try later
YES YOU NEED TO READ THIS WHOLE POST, PROB MORE THEN ONCE TO MAKE SURE YOU GOT IT. YES I KNOW HOW LONG IT IS, I TYPED IT!
the reason i call it a semi-brick is because a true brick can bot be recovered with out opening the case.
first go here and read this for info: http://forum.xda-developers.com/showthread.php?t=838484
now since your here im going to assume that its too late.
*things you will need.
copy of cwm recovery. get it here (the manual install link): http://forum.xda-developers.com/showpost.php?p=9145724&postcount=28
adb installed and working.
a known good rom, or nandroid backup. here is one: http://forum.xda-developers.com/showthread.php?t=836042 (use odex one)
a wpthis.ko for YOUR specfic kernel (run (adb shell cat /proc/version) that will tell you what kernel you have)
*first thing we need to know is, are you s-off or s-on now?
if your s-off just boot into clockwork mod recovery, wipe the phone and flash a known good rom and be done with it. if you dont have cwm recovery installed. boot into fastboot (vol down+power) you must have the sdk/adb installed and working, and type fastboot flash recovery LocationOfRecovery.img (where LocationOfRecovery.img= where you have the recovery, ie c:\android\recovery.img). once thats installed follow instructions above.
*if you are s-on:
will the phone boot into android? if so your not bad off.
if you want to unroot to return the phone, follow the unroot thread here: http://forum.xda-developers.com/showthread.php?t=835971
if you dont want to unroot then you have a couple of different options. if you have cwm recovery still installed, just follow instructions above and flash a known good rom. ive been told that boot.img (kernel) wont flash if you are s-on. the way to fix this (temporarily) is boot into recovery, but before you flash run these commands:
(put wpthis.ko in sdk folder)
adb remount
adb push wpthis.ko /data/local/wpthis.ko (specific for your kernel)
adb shell
# insmod /data/local/wpthis.ko (should get same function not implemented error as when u rooted first time)
then proceed to flash the rom. once booted into android skip down to, "now to get back to s-off"
*if you have stock or eng-recovery installed.
will the phone attempt to boot android at all? where is it stuck at?
a good min after it starts to try to boot, type these commands:
adb remount
adb shell
if you can get in shell then theres still hope. back out shell for a second and start here:
put the cwm recovery.img and wpthis.ko in your sdk folder
adb remount
adb push wpthis.ko /data/local/wpthis.ko (specific for your kernel)
adb push recovery.img /data/local/recovery.img
adb shell
# insmod /data/local/wpthis.ko (should get same function not implemented error as when u rooted first time)
# dd if=/data/local/recovery.img of=/dev/block/mmcblk0p21 (now wait a min or 2 to give it time to finish)
#sync (give it another min or to just to be safe)
#reboot recovery
at this point you should be in cwm recovery. follow instructions above for flashing with s-on.
*if you cannot get into shell while booting, but have eng-recovery installed, there might be some options.(however this is all theory)
boot into recovery-
if you are on linux using adb, you can try taking sh from /system/bin folder of any custom rom, chmod 0755 it, then push it to /system/bin and adb shell might work.
windows-
boot into recovery.
a system.img compatible with your installed kernel pushed may work. put the system.img into the sdk folder.
adb push system.img /data/block/mmcblk0p25
then reboot and see where you are. if that dont work, grab the modified miscnew.img here: http://www.4shared.com/file/pUPfrGi-/mmcblk0p17.html
rename it misc.img put it in sdk folder and
adb push misc.img /dev/block/mmcblk0p17
then reboot into bootloader with PC10IMG.zip on root of sdcard and it should run though. if it does your fully stock and get to start all over again.
*if you cannot get into shell, and you have stock recovery, im sorry your pretty screwed. as of right now the only thing thats gonna bring it back is a full img/update signed from htc thats equal to or higher then the version currently on the phone. (well and jtag of course)
*well now you've done one of the steps above. your booted into android, you have perm root, and cwm recovery installed, just still s-on. dont worry your almost there!
first take that wpthis.ko for you kernel and push it, and the eng hboot.
adb push wpthis.ko /data/local/
adb push hboot-eng.img /data/local
then from adb shell, or terminal root prompt:
# insmod /data/local/wpthis.ko (again you should get the function not implemented error)
NOW REMEMBER THIS NEXT STEP COULD MEAN DEATH FOR YOU G2 IF TYPED WRONG, AND AFTER ALL THIS HARD WORK!
# dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18
wait a few mins to be sure its done.
# sync
wait a few more just cause.
reboot, you should now be s-off, cwm recovery installed, and free to do whatever you want. just dont go screwing it up again
* as new methods are discovered, or ones here are proven wrong, i will update as necessary. as of the writing post, 2 devices that i know of have been saved!
good luck!
wpthis.ko for bacon bits.03 kernel: http://www.4shared.com/file/OAcd1bix/wpthis-263221-cyanogenmod.html
Kit-Kat OTA came out for my Nexus 4 today and I went to apply it but during the install it errored out and the phone subsequently enters a boot loop. I can get into a recovery shell and attempt to push the update via sideload but I get an error:
Symlinks and permissions...
set_metadata_recursive: some changes failed
E:Error in /tmp/update.zip
(Status 7)
Installation aborted
I'm 99% sure there's a binary in /system/xbin/ or /system/bin/ thats set immutable (chattr +i) causing this to fail but I can't launch an adb shell from recovery to fix this. Can anybody help me out here?
ykram said:
Kit-Kat OTA came out for my Nexus 4 today and I went to apply it but during the install it errored out and the phone subsequently enters a boot loop. I can get into a recovery shell and attempt to push the update via sideload but I get an error:
Symlinks and permissions...
set_metadata_recursive: some changes failed
E:Error in /tmp/update.zip
(Status 7)
Installation aborted
I'm 99% sure there's a binary in /system/xbin/ or /system/bin/ thats set immutable (chattr +i) causing this to fail but I can't launch an adb shell from recovery to fix this. Can anybody help me out here?
Click to expand...
Click to collapse
Are you using stock recovery to do this?
You pretty much explained why, but if you had rooted the phone it could fail due to other reasons too.
If you have an unlocked bootloader then you can boot TWRP (not install, but boot by fastboot boot twrp.img), it have its own terminal and you can go in and chattr -i that file.
Or with unlocked bootloader you just "fastboot format system" and flash the full system.img from the factory image. Or use TWRP to flash a stock rom.
I don't see how else you could have ran a chattr command to the /system without root. But without an unlocked bootloader you pretty much only have the choice of factory reset or unlock the bootloader in which both will wipe all data. But I'm pretty sure beside fastboot erase and format, not even factory reset in recovery could get rid of an immutable file. There is no adb access in stock recovery beside adb sideload signed packages (otherwise every android phones will be very unsecure).
eksasol said:
Are you using stock recovery to do this?
You pretty much explained why, but if you had rooted the phone it could fail due to other reasons too.
If you have an unlocked bootloader then you can boot TWRP (not install, but boot by fastboot boot twrp.img), it have its own terminal and you can go in and chattr -i that file.
Or with unlocked bootloader you just "fastboot format system" and flash the full system.img from the factory image. Or use TWRP to flash a stock rom.
I don't see how else you could have ran a chattr command to the /system without root. But without an unlocked bootloader you pretty much only have the choice of factory reset or unlock the bootloader in which both will wipe all data. But I'm pretty sure beside fastboot erase and format, not even factory reset in recovery could get rid of an immutable file. There is no adb access in stock recovery beside adb sideload signed packages (otherwise every android phones will be very unsecure).
Click to expand...
Click to collapse
Unfortunately, you're correct. I was rooted at one point and had an old 'su' binary around that was immutable, completely forgotten about. My bootloader is stock atm and I'm still stuck on 'no command' I'm accepting the inevitability that I'll have to wipe and start over but I'm not even sure how to flash the factory firmware now since I'm either stuck in a 'Google' boot loop or I get 'no command'.
Any suggestions?
ykram said:
Unfortunately, you're correct. I was rooted at one point and had an old 'su' binary around that was immutable, completely forgotten about. My bootloader is stock atm and I'm still stuck on 'no command' I'm accepting the inevitability that I'll have to wipe and start over but I'm not even sure how to flash the factory firmware now since I'm either stuck in a 'Google' boot loop or I get 'no command'.
Any suggestions?
Click to expand...
Click to collapse
When you see no command that is normal. To bring up the stock recovery menu, while holding Power first, press Volume Up.
Google bootloop have nothing to do with flashing factory image since it required using fastboot in fastboot mode (not in recovery), aka the bootloader menu. Links in my signature have instructions to flash factory image.
eksasol said:
When you see no command that is normal. To bring up the stock recovery menu, while holding Power first, press Volume Up.
Google bootloop have nothing to do with flashing factory image since it required using fastboot in fastboot mode (not in recovery), aka the bootloader menu. Links in my signature have instructions to flash factory image.
Click to expand...
Click to collapse
Cool, gotch ya. Many thanks for the response and help.
Hey!
I have tried installing cwm after doing towelroot. I am using terminal and used the command:
Code:
flash_image recovery /sdcard/recovery.img
but it ends up doing nothing. I have the proper binaries and I did chmod 777 so the command should work. But when I do:
Code:
reboot recovery
I boot into Android recovery 3e. Also after executing the command should I get any output or should it go straight to next line? Any help would be appreciated.
We have a locked bootloader which really prevents the us from replacing the stock kernel and recovery. The only working recovery we have is safestrap. Read more on the all things AT&T thread.
Sent from my SGH-I337 running GPE using Tapatalk
Oh wow can't believe i forgot that.
Tl;dr - 1) download zip from asus 2) download tethered recovery 3) copy the zip to the sd card 4) run tethered recovery utility 5) install via twrp/cwm menus
I am creating this thread to document my experience with a failed update and being stuck in a brick state with the seemingly random but present permission denied error when trying to fastboot flash. Most of this is not new, but rather a collection of existing resources with a focus on a specific, uncommon issue(s)
Tomorrow I will edit this message with links to the threads and posts which got me going again today. This is currently a workaround to restore the system, the bootloader is still falling.
Recommended reading:
-ansebivi's wonderful ota flash guide - links all the major files, lays out all the theory
-the official tethered recovery thread, my missing link
-thebugruss's permission denied thread, alludes to the magic system recovery properties of tethered recovery and had some great information
- all the other xda and Google hits that reference these errors
I had been putting off the .137 ota update for a while and finally decided to let in download and install. My z551 was not rooted and had a locked boot loader. the update failed and re booted back into .97 without issues for a few minutes before turning off. When I rebooted, I was stuck in the wonderful boot loop. Reading through the boot loop recovery section of the ota thread, I start top down and found my fastboot would not properly install anything. Error permission denied. Then I tried the adb sideload which failed with a cannot read error on the pc. Finally I went to try the install via zip in the external storage, but recovery would not start. Instead the ZenFone either fell back to fast boot our started at the powered by Android screen. Many posts referenced wiping the cache via fast boot, ask permission denied fire me. Having seen some success discussion with vampirefo tethered recovery, I was able to at least get back to recovery and poke around adb shell. Adb shell here had no root privileges and could not even read /sdcard, but at least usage-wise my /data looked whole, /system was empty and /recovery did not look right. Adb sideload failed in this recovery, wiping the caches here did nothing, the install from zip menu options did not work. Encouraged by the process, I found the latest stock tethered recovery utility updated back in July and trying twrp instead of cwm I was finally able to get install from zip working. Side load did not work under twrp, but gave a different error than stock and cwm
I never wiped /data and had a found all my settings and and data intact. Fastboot still gives permission denieddenied errors, but that will have to be fixed another day.
From all my reading, there doesn't seem to be a common reason for permission debuted in fast boot (threads exist of rooted, un rooted, never rooted, locked and unlocked bootloader). At least one post indicated a result of the ww fastboot on a cn or tw device. For most, permission denied still allows for some writing. My current guess is that each subsequent attempt and failure corrupted system and recovery
Next steps:
Perform a property nand backup in twrp
Check if my fast boot matches my phone sku
Fix fastboot (preferably without unlocking the bootloader, but definitely i will need to root to investigate
-f
permission denied
fg said:
Tl;dr - 1) download zip from asus 2) download tethered recovery 3) copy the zip to the sd card 4) run tethered recovery utility 5) install via twrp/cwm menus
I am creating this thread to document my experience with a failed update and being stuck in a brick state with the seemingly random but present permission denied error when trying to fastboot flash. Most of this is not new, but rather a collection of existing resources with a focus on a specific, uncommon issue(s)
Tomorrow I will edit this message with links to the threads and posts which got me going again today. This is currently a workaround to restore the system, the bootloader is still falling.
Recommended reading:
-ansebivi's wonderful ota flash guide - links all the major files, lays out all the theory
-the official tethered recovery thread, my missing link
-thebugruss's permission denied thread, alludes to the magic system recovery properties of tethered recovery and had some great information
- all the other xda and Google hits that reference these errors
I had been putting off the .137 ota update for a while and finally decided to let in download and install. My z551 was not rooted and had a locked boot loader. the update failed and re booted back into .97 without issues for a few minutes before turning off. When I rebooted, I was stuck in the wonderful boot loop. Reading through the boot loop recovery section of the ota thread, I start top down and found my fastboot would not properly install anything. Error permission denied. Then I tried the adb sideload which failed with a cannot read error on the pc. Finally I went to try the install via zip in the external storage, but recovery would not start. Instead the ZenFone either fell back to fast boot our started at the powered by Android screen. Many posts referenced wiping the cache via fast boot, ask permission denied fire me. Having seen some success discussion with vampirefo tethered recovery, I was able to at least get back to recovery and poke around adb shell. Adb shell here had no root privileges and could not even read /sdcard, but at least usage-wise my /data looked whole, /system was empty and /recovery did not look right. Adb sideload failed in this recovery, wiping the caches here did nothing, the install from zip menu options did not work. Encouraged by the process, I found the latest stock tethered recovery utility updated back in July and trying twrp instead of cwm I was finally able to get install from zip working. Side load did not work under twrp, but gave a different error than stock and cwm
I never wiped /data and had a found all my settings and and data intact. Fastboot still gives permission denieddenied errors, but that will have to be fixed another day.
From all my reading, there doesn't seem to be a common reason for permission debuted in fast boot (threads exist of rooted, un rooted, never rooted, locked and unlocked bootloader). At least one post indicated a result of the ww fastboot on a cn or tw device. For most, permission denied still allows for some writing. My current guess is that each subsequent attempt and failure corrupted system and recovery
Next steps:
Perform a property nand backup in twrp
Check if my fast boot matches my phone sku
Fix fastboot (preferably without unlocking the bootloader, but definitely i will need to root to investigate
-f
Click to expand...
Click to collapse
Asus Memo Pad 8 181c... I got tablet with WW-3.1.23.150 & have done consecutive updates through a thread on XDA (tablet would not update) starting with a full firmware flash using CWM Tethered recovery of the .172, & flashing two OTA's offered on same thread of .183 & .189. I eventually got a link for an Asus download through Asus Memo Pad G+ community to get the .191. Trying to do a system.img & boot.img pull I get the permission denied part just trying to do a ls -al /dev/block/platform/dw_mmc/by-name is getting me "Permision Denied", just trying to get mount points!
Does this mean I have something corrupted?
zach
Did you have a lock screen password enabled before you got bricked?
That would prevent any flashing. You have to somehow disable that.
Sent from my ASUS_Z00AD using XDA Premium HD app