Sup guys, can someone show me how to change a recovery img via 1click root method? Right now I'm using Cyanogens 1.4 which is great but would like to upgrade to the new Amon RA's img. Any help would be appreciated.
TTT back up
Using ADB...
from the command prompt...
where you see recovery.img just type in the file name that you have in plasce of it....
adb remount
adb push recovery.img /sdcard/recovery.img
adb shell flash_image recovery /sdcard/recovery.img
adb shell reboot recovery
Hi Guys! I need your Help!
My Kindle fire is stuck on the booting logo, it looks a bit sharper and brighter than usual.
I was running a perfect running stock 6.2.2 firmware with root access.
Those are the steps i did:
went to http://forum.xda-developers.com/showthread.php?t=1410223 and did:
Code:
To install the CWR recovery by DoomLord after gaining root:
Download it, and push it to your Kindle
adb push <filename> /data/local/recovery.img
adb shell dd if=/data/local/recovery.img of=/dev/block/platform/mmci-omap-hs.1/by-name/recovery
Reboot normaly with no boot manager, so:
Did the first part of the thread BurritoRoot3 and tried to perform the "To install the CWR recovery by DoomLord after gaining root:" procedure.
Again it did boot normal.
Went to http://forum.xda-developers.com/showthread.php?t=1414832 and did:
Code:
adb push fbmode /data/local/tmp
adb shell chmod 755 /data/local/tmp/fbmode
adb shell /data/local/tmp/fbmode
adb reboot
it went good, i did reboot the device and now its stuck with kindle fire logo and no adb connection
Any advice please Next i will try this http://forum.xda-developers.com/showthread.php?t=1430038
Hopefully someone can assist.
I was at the same place, stock rom, 6.2.2 with root access via burritoroot2. To add TWRP I used KFU edited to support burritoroot2.
Haha puh, i think i fixed it.
this thread help.
http://forum.xda-developers.com/showthread.php?t=1407254&page=2
You have to look at the kindle fire logo. when its static. you are in fastboot mode.
to boot normal you can just do:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
This should work with 4002 as parameter to re enable fastboot mode.
Soo. question solved
But has anybody an idea how to get to CMW installed in fastboot mode?
//ps. i added vendor id (0x18d1) to adb_usb.ini on windows 7
it is described at the op of cwm under [how to test]:
http://forum.xda-developers.com/showthread.php?t=1454241
Did that process b63 link mentions last night without issue on a KF that has TWRP.
miro101 said:
Haha puh, i think i fixed it.
this thread help.
http://forum.xda-developers.com/showthread.php?t=1407254&page=2
You have to look at the kindle fire logo. when its static. you are in fastboot mode.
to boot normal you can just do:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
This should work with 4002 as parameter to re enable fastboot mode.
Soo. question solved
But has anybody an idea how to get to CMW installed in fastboot mode?
//ps. i added vendor id (0x18d1) to adb_usb.ini on windows 7
Click to expand...
Click to collapse
put cwm in ur fastboot folder
fastboot flash recovery cwm.img
u might needto do fastboot -I 0x1949 flash recovery
make sure u have firefirefire already installed, or flash that at the same time. fastboot flash bootloader u-boot.bin
Sent from my HTC Glacier using xda premium
Hi,
I really need some help on this one. I wiped everything using TWRP recovery in preparation of installing a custom ROM.
I then realised I forgot to transfer the custom rom to my phone! When I went to reboot the system it says "No OS installed! Are you sure you want to reboot?"
No it's stuck on the google logo.
Is there a way to see if any Rom is still installed on on my phone or if it deleted my stock rom also?
I tried to push the rom through adb but it says error read only.
Also USB debugging is not enabled but I can't boot to enable it.
Please help.
Thanks
Go into fastboot and ensure your fastboot devices command shows your s/n. If so then grab the stock image from xda and flash it.
fastboot flash bootloader BOOTLOADERNAME.img
fastboot reboot-bootloader
fastboot flash radio RADIONAME.img
fastboot reboot-bootloader
fastboot -w update IMAGENAME.zip
Alternatively, using ADB.
from command prompt: adb remount
adb push <FILE PATH> /sdcard/0/
Boot into recovery (I use CWM) and then install it.
Thanks for the quick reply.
I managed to solve it by using the instructions in this thread: http://forum.xda-developers.com/showthread.php?t=2010312
It's all in fastboot so I had no problems
Problem solved.
Hi,I just installed android 4.4.3 from 4.4.2 rooted with kernel mat1x v13.5 with the following steps:
adb reboot bootloader
fastboot flash bootloader bootloader-mako-makoz30d.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.02.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Then installed CWM by:
adb reboot bootloader
fastboot flash recovery recovery-clockwork-touch-6.0.4.7.img
fastboot reboot-bootloader
and then I tried to go to recovery mode with:
Code:
fastboot reboot-bootloader
but the command line says:
Code:
<waiting for device>
. If I write:
Code:
fastboot devices
, nothing happens, but if I write:
Code:
adb devices
it does recognizes my phone.
Anyway I went to recovery mode with volume buttons (CWM is properly installed), went to sideload options, USB connected and typed:
Code:
adb sideload UPDATE-SuperSU-v1.99r3.zip
but it says:
Code:
error: device not found
While I'm in Recovery mode (in CWM) adb devices can't find any device.
SDK tools and platform-tools are just updated and PC is just rebooted.
EXTRA INFO: when i go out of CWM it says:
Code:
Root access is missing. Root device? THIS CANNOT BE UNDONE.
and options are
-no
-Yes - Root device (/system/xbin/su)
When I choose Yes it just starts with no problems.
Anything?
oliverm91 said:
Hi,I just installed android 4.4.3 from 4.4.2 rooted with kernel mat1x v13.5 with the following steps:
adb reboot bootloader
fastboot flash bootloader bootloader-mako-makoz30d.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.02.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Then installed CWM by:
adb reboot bootloader
fastboot flash recovery recovery-clockwork-touch-6.0.4.7.img
fastboot reboot-bootloader
and then I tried to go to recovery mode with:
Code:
fastboot reboot-bootloader
but the command line says:
Code:
<waiting for device>
. If I write:
Code:
fastboot devices
, nothing happens, but if I write:
Code:
adb devices
it does recognizes my phone.
Anyway I went to recovery mode with volume buttons (CWM is properly installed), went to sideload options, USB connected and typed:
Code:
adb sideload UPDATE-SuperSU-v1.99r3.zip
but it says:
Code:
error: device not found
While I'm in Recovery mode (in CWM) adb devices can't find any device.
SDK tools and platform-tools are just updated and PC is just rebooted.
EXTRA INFO: when i go out of CWM it says:
Code:
Root access is missing. Root device? THIS CANNOT BE UNDONE.
and options are
-no
-Yes - Root device (/system/xbin/su)
When I choose Yes it just starts with no problems.
Click to expand...
Click to collapse
Try reboot the phone and then reboot to recovery and see if that works. If not, try TWRP recovery.
taodan said:
Try reboot the phone and then reboot to recovery and see if that works. If not, try TWRP recovery.
Click to expand...
Click to collapse
You mean turn off the phone and turn on to recovery? Because I've already done that as I mentioned in the first post.
Not sure but aren't recovery mode and fastboot mode different?
Can you manually boot into fastboot mode on your phone rather than using adb commands?
audit13 said:
Not sure but aren't recovery mode and fastboot mode different?
Can you manually boot into fastboot mode on your phone rather than using adb commands?
Click to expand...
Click to collapse
I just used fastboot to go into recovery with my pc because i'm lazy, I can do it with the mobile, but when i tried I discovered the <waiting for device> error. And I need to use adb coomands to sideload SuperSU. I think i can flash it from the phone, but it still bothers me the fact that there is something wrong, because I use my phone to test personals apks.
oliverm91 said:
I just used fastboot to go into recovery with my pc because i'm lazy, I can do it with the mobile, but when i tried I discovered the <waiting for device> error. And I need to use adb coomands to sideload SuperSU. I think i can flash it from the phone, but it still bothers me the fact that there is something wrong, because I use my phone to test personals apks.
Click to expand...
Click to collapse
Are you using a Windows PC? If you are, boot into task mamager and kill all ADB services. Relaunch the command prompt and try it.
audit13 said:
Are you using a Windows PC? If you are, boot into task mamager and kill all ADB services. Relaunch the command prompt and try it.
Click to expand...
Click to collapse
I am, Windows 8. But this problems happens even after rebooting my PC.
oliverm91 said:
I am, Windows 8. But this problems happens even after rebooting my PC.
Click to expand...
Click to collapse
I assume the drivers load the first time you connect your phone. Does running the command prompt as an admin make a difference?
audit13 said:
I assume the drivers load the first time you connect your phone. Does running the command prompt as an admin make a difference?
Click to expand...
Click to collapse
I use PowerShell as admin
No clue?
Revoke USB debugging authorizations for all the devices from the developer options and try again..
Sent from my Nexus 4 using Tapatalk
Adb and fastboot are two different things. Use adb commands when you're booted into recovery or normally booted. Use fastboot commands when you boot into the bootloader
Sent from my Nexus 5 using XDA Free mobile app
karthi89 said:
Revoke USB debugging authorizations for all the devices from the developer options and try again..
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Did this, but ADB still doesn't recognize my phone while in recovery.
jd1639 said:
Adb and fastboot are two different things. Use adb commands when you're booted into recovery or normally booted. Use fastboot commands when you boot into the bootloader
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Ok, but ADB won't recognize my device when it's on CWM (CWM v6.0.4.7)
I realised that in "device manager" of Windows a yellow triangle appears on "Other devices" -> Nexus 4 (when im in Recovery)
and when I normally boot my phone it appears normally under "Android device" -> android composite adb interface
No clue?
I wanted to sideload "[ROM][Stock+][Nougat-NBD90X]Debloated-Prerooted-Odex-Busybox-Fast & Stable" (as i'm encrypted so needed to wipe) but the radio and bootloader provided in the OP are in the same zip. What adb cmd should i use to flash this zip? will adb sideload <filename.Zip> do the job? i wasn't sure which bootloor img to tell adb to use as the Zip had quite a few img files in there:/ Can i just sideload the rom and vendor to boot? (then copy over to internal and then flash in twrp)
already on TWRP 3.0.2.2
my plan was to
fastboot format userdata
reboot into recover and factory reset?
reboot into fastboot
adb sideload vendor.zip
adb sideload rom.zip
adb sideload radio+BL.zip
will this work?
Thanks
bentez2003 said:
I wanted to sideload "[ROM][Stock+][Nougat-NBD90X]Debloated-Prerooted-Odex-Busybox-Fast & Stable" (as i'm encrypted so needed to wipe) but the radio and bootloader provided in the OP are in the same zip. What adb cmd should i use to flash this zip? will adb sideload <filename.Zip> do the job? i wasn't sure which bootloor img to tell adb to use as the Zip had quite a few img files in there:/ Can i just sideload the rom and vendor to boot? (then copy over to internal and then flash in twrp)
already on TWRP 3.0.2.2
my plan was to
fastboot format userdata
reboot into recover and factory reset?
reboot into fastboot
adb sideload vendor.zip
adb sideload rom.zip
adb sideload radio+BL.zip
will this work?
Thanks
Click to expand...
Click to collapse
Install all zips through TWRP 3.0.2-2, it is compatible with 7.0 encryption.
Sent from my Nexus 5X using Tapatalk