Hello,
is there a way to boot an external boot.img or recovery.img via adb? The idea is to keep the xoom unmodified, but boot an unlocked bootloader/recovery to perform a system backup.
Is there a way? On my old htc magic I could install a custom ROM this way:
fastboot boot recoverym.img
while recoverym.img was a modified (open) recovery system.
After installing the custom ROM via nandroid I had my original recovery on the htc untouched.
I tried that command with the xoom (and several open recoveries for the xoom) what gave me an error message.
Any ideas?
Thanks in advance!
Chris
Related
All, I'm trying to port clockworkmod recovery to the T-Mobile MyTouch Q (lgec800). I have completed all steps and am at the point where I need to test it to correctly modify recovery.fstab and BoardConfig.mk. I can't use flash_image through terminal on the phone, my understanding is because the partitions are emmc. I have successfully used dd command to flash my first modded recovery, however the phone won't boot into the recovery. Upon telling it with adb command or an app, it boots into main logo, goes black, then back to main logo and hangs. Battery pull and boot brings it back to normal. Also, I don't believe my phone has hboot or fastboot, as no amount of commands in terminal on phone or from computer get it to boot into those. Was wondering if someone can answer some questions for me.
1.) I am correct that I should be using original boot.img for the port and not recovery.img? I haven't found documentation specifying and why.
2.) I am correct in flashing the modded recovery(originally the stock boot.img) into the recovery partition?
3.) Is the recovery.zip output only flashable w/ hboot?
I tried making the cwm recovery port with the original recovery.img and flashing that to the recovery partition, same thing happens.
Anyone have any ideas?
Sent from my LG-C800 using XDA App
Is there maybe a way to read/write to the recovery partition from an external system, such as through ADB? Is the CWM port small enough to fit in the recovery partition? If there were, then forcing a CWM port for the C800 ought to work...
I have problems installing CyanogenMod on my HTC One S. When I install it, it gets stuck to boot loop. I was able to recover stock rom using backup I made. I have tried installing twice.
What I have been able to do:
- Unlock bootloader via HTCDev
- Install ClockworkMod
How I try to install CM:
1. I copy zip downloaded from here to phone: download.cyanogenmod.org/get/jenkins/50987/cm-10.2.0-ville.zip
2. I shutdown my phone by long pressing power button.
3. I boot to bootloader by pressing volume down and power.
4. I connect the USB cable (It doesn't boot to recovery otherwise, I don't know why. If I don't connect USB cable it instead boots to black screen.)
5. I select recovery and phone boots to ClockworkMod
6. I select wipe data/factory reset
7. I select install from zip and select the CyanogenMod zip
8. Phone says Installing update... and succeeds in it
9. I select reboot system now
10. Phone is now stuck in boot loop
What do I do wrong?
You are s-on right? You need to flash boot.img from cm-10.2 zip. Just extract the boot.img and flash it via fastboot
Sent from my HTC One S
I'm having the same problem on the C2 variant, except I'm stuck on boot animation. I did flash the boot image found in the zip file.
Anyone having the same problem?
ka_55 said:
You are s-on right? You need to flash boot.img from cm-10.2 zip. Just extract the boot.img and flash it via fastboot
Sent from my HTC One S
Click to expand...
Click to collapse
Yes I have S-ON. If I flash boot.img via fast boot will I be able to restore stock ROM if I want to? How is that done? Do I flash boot.img from my backup via fast boot?
sarcome said:
I'm having the same problem on the C2 variant, except I'm stuck on boot animation. I did flash the boot image found in the zip file.
Anyone having the same problem?
Click to expand...
Click to collapse
I don't know anything about c2 variant. Sorry
Scintillo said:
Yes I have S-ON. If I flash boot.img via fast boot will I be able to restore stock ROM if I want to? How is that done? Do I flash boot.img from my backup via fast boot?
Click to expand...
Click to collapse
I'm not sure %100 if you wil be able to restore stock rom since i didn't try with s-on, but if you have boot.img in that backup, you might need to flash it after restoring process and you should be fine
Sent from my HTC One S
Okay so I tried to flash cyanogenmod 11 for the first time on this moto G (US). It bootlooped and I tired to reflash it again and it did the same. There was no way of returning to stock because I had not made a backup. So I tried to flash stock in the bootloader and that didn't work. I went into the recovery and it said 'cant mount /sdcard. So go back into the bootloader and format the sdcard and that doesn't work (which I returned to the recovery to see it not working). I go back and flash twrp thinking that recovery would have something to help me flash a new rom and now I don't even have a working recovery. It takes me straight back to the bootloader and every time I flash a recovery it says Mismatched partition size (recovery) and I am unable to boot into it.
I have no clue on what to do at this point and I need help.
also it says invalid "boot image header!" in red letters
http://forum.xda-developers.com/showthread.php?t=2542219
Install full factory image with fastboot.
P.Kosunen said:
http://forum.xda-developers.com/showthread.php?t=2542219
Install full factory image with fastboot.
Click to expand...
Click to collapse
Alright thankyou!
I got everything to work again but I still can't flash roms. They just bootloop :S
It could be too big recovery install with fastboot causes problem, every recovery cwm/twrp i tried to install with fastboot fails.
http://forum.xda-developers.com/showpost.php?p=49559872&postcount=234
Twrp_MotoG_signed_010814_163615.zip
Download vocoderisms TWRP build, extract "recovery.img" from it.
After you have kitkat installed and working:
Option 1, use TWRP without install:
Boot to bootloader (adb reboot bootloader), boot twrp (fastboot boot recovery.img) and install rom from there.
Option 2, install TWRP (have not tested):
Upload twrp zip to phone (adb push Twrp_MotoG_signed_010814_163615.zip /sdcard/), boot to bootloader (adb reboot bootloader), boot twrp (fastboot boot recovery.img), install Twrp_MotoG_signed_010814_163615.zip.
Misterowl said:
Okay so I tried to flash cyanogenmod 11 for the first time on this moto G (US). It bootlooped and I tired to reflash it again and it did the same. There was no way of returning to stock because I had not made a backup. So I tried to flash stock in the bootloader and that didn't work. I went into the recovery and it said 'cant mount /sdcard. So go back into the bootloader and format the sdcard and that doesn't work (which I returned to the recovery to see it not working). I go back and flash twrp thinking that recovery would have something to help me flash a new rom and now I don't even have a working recovery. It takes me straight back to the bootloader and every time I flash a recovery it says Mismatched partition size (recovery) and I am unable to boot into it.
I have no clue on what to do at this point and I need help.
Click to expand...
Click to collapse
https://docs.google.com/file/d/0B2LP8tI1Xwu4MGtPTlpVcVQxN0k/preview this cwm worked for me
You do know flashing stock again removes root, so it has to be rerooted again ?
aradalien said:
You do know flashing stock again removes root, so it has to be rerooted again ?
Click to expand...
Click to collapse
Yes I am very aware and followed through with root with that outcome.
kieranc88 said:
https://docs.google.com/file/d/0B2LP8tI1Xwu4MGtPTlpVcVQxN0k/preview this cwm worked for me
Click to expand...
Click to collapse
CWM doesn't work it. It boots up (Im used cyanogenmod) the cyanogenmod boot animation but just stays there.
P.Kosunen said:
It could be too big recovery install with fastboot causes problem, every recovery cwm/twrp i tried to install with fastboot fails.
http://forum.xda-developers.com/showpost.php?p=49559872&postcount=234
Twrp_MotoG_signed_010814_163615.zip
Download vocoderisms TWRP build, extract "recovery.img" from it.
After you have kitkat installed and working:
Option 1, use TWRP without install:
Boot to bootloader (adb reboot bootloader), boot twrp (fastboot boot recovery.img) and install rom from there.
Option 2, install TWRP (have not tested):
Upload twrp zip to phone (adb push Twrp_MotoG_signed_010814_163615.zip /sdcard/), boot to bootloader (adb reboot bootloader), boot twrp (fastboot boot recovery.img), install Twrp_MotoG_signed_010814_163615.zip.
Click to expand...
Click to collapse
I've flashed twrp too and came out with the same outcome.
stuck in fastboot
Misterowl said:
Okay so I tried to flash cyanogenmod 11 for the first time on this moto G (US). It bootlooped and I tired to reflash it again and it did the same. There was no way of returning to stock because I had not made a backup. So I tried to flash stock in the bootloader and that didn't work. I went into the recovery and it said 'cant mount /sdcard. So go back into the bootloader and format the sdcard and that doesn't work (which I returned to the recovery to see it not working). I go back and flash twrp thinking that recovery would have something to help me flash a new rom and now I don't even have a working recovery. It takes me straight back to the bootloader and every time I flash a recovery it says Mismatched partition size (recovery) and I am unable to boot into it.
I have no clue on what to do at this point and I need help.
Click to expand...
Click to collapse
Exactly i am also facing same problem....
mobile unable to instal firmware...
still i am searching for solution ...
guys plz help me
I thought I am the only one with this problem..After mailing the phone to SC and got it back after 2 months, the phone still looks the same, just like they did nothing to fix it.
I have a N5 rooted and with custom recovery.
I plan to install the factory image via fastboot.
I don't want to lose my userdata, so I plan to extract the different .img files and flash them one by one (except userdata.img)
Can I not flash recovery.img so I can keep my custom recovery?
What are the .img files that I must flash for keeping my files, settings and my custom recovery?
Thank you on advance. You are the best!
I flashed the system and boot img's
Then booted into recovery and wiped caches
Then flashed the modified kernel for root and supersu 2.19 before booting and I've kept data and recovery fine
This boot img - http://forum.xda-developers.com/showthread.php?p=56702681
Sent from my Android 5.0 Nexus 5
Do I need other kernel for being able to root? I was only thinking of installing superSu for getting my root back.
Then, the only .img that I need to flash are the system.img and the boot.img. Am I right?
Thank You!
You need the other kernel, cf-autoroot does this for you.
Recently I decided to try flashing a custom rom onto my old phone, a Gionee F103 Pro. Since it is quite obscure it isn't officially supported by twrp, but I managed to find an unofficial build. I unlocked the bootloader and flashed twrp using fastboot, and according to the console it was successful. When I booted my phone twrp began to load, but then there were multiple 'unable to mount' and 'failed to mount' errors and it rebooted. This has been repeating for almost an hour now. It's unresponsive to any button presses, and it won't show up on the device manager either. The only way I've got it to stop was by removing the battery. I've tried fastboot mode, recovery mode and regular boot but they all end up the same. I'd be grateful if anyone could could help me fix this.
Thanks!
fibonazi said:
Recently I decided to try flashing a custom rom onto my old phone, a Gionee F103 Pro. Since it is quite obscure it isn't officially supported by twrp, but I managed to find an unofficial build. I unlocked the bootloader and flashed twrp using fastboot, and according to the console it was successful. When I booted my phone twrp began to load, but then there were multiple 'unable to mount' and 'failed to mount' errors and it rebooted. This has been repeating for almost an hour now. It's unresponsive to any button presses, and it won't show up on the device manager either. The only way I've got it to stop was by removing the battery. I've tried fastboot mode, recovery mode and regular boot but they all end up the same. I'd be grateful if anyone could could help me fix this.
Thanks!
Click to expand...
Click to collapse
Can you flash a copy of stock recovery.img via fastboot?
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Can you flash a copy of stock recovery.img via fastboot?
Click to expand...
Click to collapse
I tried to boot my phone into fastboot but it goes straight to twrp instead. My PC doesn't seem to detect it either.
fibonazi said:
I tried to boot my phone into fastboot but it goes straight to twrp instead. My PC doesn't seem to detect it either.
Click to expand...
Click to collapse
If there is a LineageOS ROM or some other custom ROM available for your device, try flashing a ROM.
If that doesn't work...
Flash a copy of stock recovery.img via TWRP. TWRP has the ability to flash .img files.
Or, if you can find a copy of your stock recovery that has been converted into a TWRP flashable .zip, you can flash that .zip via TWRP then reboot the device into recovery mode to see if it boots stock recovery.
If you can't get that to work, TWRP has a terminal emulator built in, you can try flashing stock recovery.img using dd commands in the TWRP terminal. You'll have to research your devices partition structure to get the correct dd command to make sure that the recovery gets flashed to the correct partition.
I'm only saying to do all of this because it seems that screwing with the recovery partition caused the issue, maybe, restoring/repairing the recovery partition might fix the issue.
If not, you'll have to find a fix that involves flashing your stock firmware or stock system.img.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
If there is a LineageOS ROM or some other custom ROM available for your device, try flashing a ROM.
If that doesn't work...
Flash a copy of stock recovery.img via TWRP. TWRP has the ability to flash .img files.
Or, if you can find a copy of your stock recovery that has been converted into a TWRP flashable .zip, you can flash that .zip via TWRP then reboot the device into recovery mode to see if it boots stock recovery.
If you can't get that to work, TWRP has a terminal emulator built in, you can try flashing stock recovery.img using dd commands in the TWRP terminal. You'll have to research your devices partition structure to get the correct dd command to make sure that the recovery gets flashed to the correct partition.
I'm only saying to do all of this because it seems that screwing with the recovery partition caused the issue, maybe, restoring/repairing the recovery partition might fix the issue.
If not, you'll have to find a fix that involves flashing your stock firmware or stock system.img.
Click to expand...
Click to collapse
Actually, the problem I'm having is that twrp runs into an error and shuts down before I can do anything on it. It is stuck in an endless boot loop and is unresponsive to any button or screen presses. I have a lineage os rom, but I don't have any way to flash it right now. Is there any way to make it responsive again? Or any way to connect it to a pc?