Would really love some help. I flashed the recovery from the CM site. Now when it boots is shows the Cyanoboot screen, and it only boots to recovery from EMMC. Even after side-loading the CM13 zip for acclaim it still just boots to recovery. Any ideas how to get out of recovery?!?!
I also tried to "adb sideload" a different recovery (CWM) but it fails to install, saying "E: footer is wrong, E: signature verification failed"
I can only get into adb sideload mode, as "adb devices" says my device is "UNAUTHORIZED", and can't boot to CM at all.
Anything (other than CM zip) I try to flash from ADB sideload within CM recovery fails due to signature verification. Seems like its checking for updates signed by CM. Ugh, not seeing a way out of this.
If your device boot-loops to recovery, see http://forum.xda-developers.com/showthread.php?p=21381141#post21381141 (including in particular post #9 of that thread) for potential cause and solution.
digixmax said:
If your device boot-loops to recovery, see http://forum.xda-developers.com/showthread.php?p=21381141#post21381141 (including in particular post #9 of that thread) for potential cause and solution.
Click to expand...
Click to collapse
Thanks for the thread. I think that helps understand the issue, however I'm kind of in a "catch-22" since I don't have adb shell access, i can't write a new recovery image. And since I can't write a new recovery image, im stuck with the Custom CM recovery that won't do anything but flash official builds. The developer, Chris, has been looking into an option to help me out of this, hopefully he comes up with it
srgibbs99 said:
Thanks for the thread. I think that helps understand the issue, however I'm kind of in a "catch-22" since I don't have adb shell access, i can't write a new recovery image. And since I can't write a new recovery image, im stuck with the Custom CM recovery that won't do anything but flash official builds. The developer, Chris, has been looking into an option to help me out of this, hopefully he comes up with it
Click to expand...
Click to collapse
If the current recovery that the tablet boots to is functioning you can try to use it to flash zip files for a new recovery or flashable_bootloop_fix.
If the recovery is not functioning, you should use a bootable SD card containing a SD-based recovery to flash them.
digixmax said:
If the current recovery that the tablet boots to is functioning you can try to use it to flash zip files for a new recovery or flashable_bootloop_fix.
Click to expand...
Click to collapse
The current recovery (Cyanogenmod recovery) boots, but it seems to only be able to flash ZIPs signed by CM. And doing that hasn't changed any behavior.
digixmax said:
If the recovery is not functioning, you should use a bootable SD card containing a SD-based recovery to flash them.
Click to expand...
Click to collapse
I've tried a bootable SD card, but the Cyanoboot doesn't give me a chance to choose any options...it just loads EMMC recovery immediately every time.
srgibbs99 said:
....
I've tried a bootable SD card, but the Cyanoboot doesn't give me a chance to choose any options...it just loads EMMC recovery immediately every time.
Click to expand...
Click to collapse
Many NTs can boot off SD card only from a power-off state and with insertion of a powered USB cable.
If this still does not help, see note (i) of http://forum.xda-developers.com/showthread.php?t=2692403
digixmax said:
Many NTs can boot off SD card only from a power-off state and with insertion of a powered USB cable.
If this still does not help, see note (i) of http://forum.xda-developers.com/showthread.php?t=2692403
Click to expand...
Click to collapse
Nice! Thanks for the tips. I was able to create a bootable SD card and then flash a working recovery! Up and running on CM13, not bad so far. Seem way more stable than CM12 was.
Related
hi all,
I have followed MikeyCiggz's post:http://forum.xda-developers.com/showthread.php?t=1233154&page=2, thanks MIkeyCiggz first!
But I cannot find a suitable bootable recovery image for evo 3d:-(. I have tried twrp 1.0.3, twrp 1.1.1, twrp 2.0, it seemed that twrp image file is not bootable. I have tried:
dd if=./twrp-1.1.1.img of=/dev/mmcblk01 bs=1M
but the sd card it not bootable.
I have searched google but find nothing...so anyone can give any hints that where can I download the bootable recovery image, both twrp and cwm is ok. thanks in advance!
I don't have the answer to your question but, I don't think you should put ./ in the if= section. Your not executing the file.
Sent from my PG86100 using Tapatalk
megabiteg said:
I don't have the answer to your question but, I don't think you should put ./ in the if= section. Your not executing the file.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
./ means the current directory, ./twrp-1.1.1.img means twrp-1.1.1.img in the current directory
Anyone tried twrp 2.0 with bootable sdcard? please share your success story, thanks!
subaochen said:
hi all,
I have followed MikeyCiggz's post:http://forum.xda-developers.com/showthread.php?t=1233154&page=2, thanks MIkeyCiggz first!
But I cannot find a suitable bootable recovery image for evo 3d:-(. I have tried twrp 1.0.3, twrp 1.1.1, twrp 2.0, it seemed that twrp image file is not bootable. I have tried:
dd if=./twrp-1.1.1.img of=/dev/mmcblk01 bs=1M
but the sd card it not bootable.
I have searched google but find nothing...so anyone can give any hints that where can I download the bootable recovery image, both twrp and cwm is ok. thanks in advance!
Click to expand...
Click to collapse
Never heard of copying the recovery image directly onto the sdcard and then booting off of it.
As my understanding of the boot process goes, recovery mode will only load the recovery image for the specific recovery partition. Recovery mode doesn't search the device for recovery images in any random partition.
The link you provided had no directions or evidence to support it being possible. Perhap if there is more information on this process, it might seem more feasible.
hope that helps! good luck!
joeykrim said:
Never heard of copying the recovery image directly onto the sdcard and then booting off of it.
As my understanding of the boot process goes, recovery mode will only load the recovery image for the specific recovery partition. Recovery mode doesn't search the device for recovery images in any random partition.
The link you provided had no directions or evidence to support it being possible. Perhap if there is more information on this process, it might seem more feasible.
hope that helps! good luck!
Click to expand...
Click to collapse
I think a bootable recovery sdcard maybe the same as the command:
fastboot boot recovery.img
the above command should boot into recovery despite of the recovery partition on the inner storage of the phone. Is that right?
subaochen said:
I think a bootable recovery sdcard maybe the same as the command:
fastboot boot recovery.img
the above command should boot into recovery despite of the recovery partition on the inner storage of the phone. Is that right?
Click to expand...
Click to collapse
The above command will send the recovery.img located on the host computer, through the host computer's fastboot binary and USB connection to the device which is also in fastboot mode and will then temporarly booted into the transferred recovery image on the device.
Never heard of fastboot boot a full sdcard?
Not sure how that deals with sdcard ..
Okay,
So I've had my HTC One S for a while now, and just decided to unlock/root/flash custom ROM tonight. Well, I think I got to tired, and I made a few mistakes.
Everything went well initially. I was able to unlock the bootloader, flash new recovery (clockwork), root the phone and install the stable Cyanagen HTS One S built. Cyanagen never booted past the intro animation screen though. I cleared cashe, dalvik cache, and did a factory reset, and then reflashed the rom. Again, nothing.... just got stuck.
I was pretty tired at this point. Long story short, I accidentally formatted the originally rom/google pack file from the "sd card." Now I can't reflash a rom or anything. It's just going around in circles.
I tried doing a "./fastboot update <filename.zip>" but it just gave me an error about not having any android.txt or something like that. Through some of the research I did, it seems you can't actually update a ROM through fastboot? Is that true? If not, what did I do wrong? I'm on a mac btw...
I was then thinking about "adb" but I don't really know much of anything about it. I booted my phone into recovery mode, then went to install zip from side load, and then type "./adb sideload <filename.zip>" in my terminal window. It started to do something, but in the end, it said device not found.
I'm super tired, I've been up all night trying to "unbrick" my phone. I now am coming to the masses in hopes that I'm just too "newby" at this and I'm missing something stupid. Is there a way to flash a new rom on my phone—and for me to hope that that does the trick and lets me boot up that bad boy.
Oh yea. I forgot the biggest mistake yet! I forgot to do a backup of my device before the new ROM was flashed originally! A lot of stupid mistakes. That's why you don't do these kinds of projects for the first time late at night/early in the morn I guess.
Any help would be greatly appreciated. Thanks everyone in advance.
Dd you flash the boot image from the zip file using fastboot.
If not:
Extract the rom zip on your computer which also has fastboot installed on it. Then copy the boot image to the folder where your fastboot is. Then enter into the folder which contains fastboot and the boot image and type fastboot devices after plugging in your device in fastboot mode thorough the bootloader. It should display your phone serial in the command window. Then type fastboot flash boot boot.img then reboot with cm installed and it should work.
Sent from my HTC One using Tapatalk 4 beta
**Press the thanks button if I have helped you.
up user got right. flash boot.img from rm then reboot and fash rom in cwm.
Sent from my WT19i using xda app-developers app
Boom. That seemed to work. Up and running CM. Thanks!
WildfireDEV said:
Dd you flash the boot image from the zip file using fastboot.
If not:
Extract the rom zip on your computer which also has fastboot installed on it. Then copy the boot image to the folder where your fastboot is. Then enter into the folder which contains fastboot and the boot image and type fastboot devices after plugging in your device in fastboot mode thorough the bootloader. It should display your phone serial in the command window. Then type fastboot flash boot boot.img then reboot with cm installed and it should work.
Sent from my HTC One using Tapatalk 4 beta
**Press the thanks button if I have helped you.
Click to expand...
Click to collapse
more problems
Okay. Maybe I need to start a new thread. I'm having some issues. The phone is up and running in CM. I can make/receive calls.
The problem now? CM is not recognizing my built in internal storage on my HTC One S. There is no actual sd card slot on the HTC One S—There are multiple slots for internal storage, and it doesn't seem to be recognizing that space at all. So, I can't use my camera for example.... and my available space for new apps is very limited (should be 32gb if I remember correctly...)
Also, when it did boot, it didn't go into the normal "set up your google account" that android normally goes into. I did add account in settings, but it doesn't seem to be syncing all my contacts/etc/etc.
Any other thoughts on what else I need to do to get my device working as it actually should? Thanks for all the help again.
WildfireDEV said:
Dd you flash the boot image from the zip file using fastboot.
If not:
Extract the rom zip on your computer which also has fastboot installed on it. Then copy the boot image to the folder where your fastboot is. Then enter into the folder which contains fastboot and the boot image and type fastboot devices after plugging in your device in fastboot mode thorough the bootloader. It should display your phone serial in the command window. Then type fastboot flash boot boot.img then reboot with cm installed and it should work.
Sent from my HTC One using Tapatalk 4 beta
**Press the thanks button if I have helped you.
Click to expand...
Click to collapse
... I should mention
Based on my initial message—I did "format SD" at one point when I was attempting to get CM to boot properly initially. Hopefully that didn't jack things up further... When I boot into recover, I'm unable to create a backup or anything like that—it just gives an error when attempting to mount the "sd card."
Any thoughts? Oye. Last time I do late night work on my only phone.
tylermoney said:
Okay. Maybe I need to start a new thread. I'm having some issues. The phone is up and running in CM. I can make/receive calls.
The problem now? CM is not recognizing my built in internal storage on my HTC One S. There is no actual sd card slot on the HTC One S—There are multiple slots for internal storage, and it doesn't seem to be recognizing that space at all. So, I can't use my camera for example.... and my available space for new apps is very limited (should be 32gb if I remember correctly...)
Also, when it did boot, it didn't go into the normal "set up your google account" that android normally goes into. I did add account in settings, but it doesn't seem to be syncing all my contacts/etc/etc.
Any other thoughts on what else I need to do to get my device working as it actually should? Thanks for all the help again.
Click to expand...
Click to collapse
further discovery
Okay, so I did another factory reset just in case—it looks like the factory reset wasn't able to do exactly what it needed either. I saw an error in the formatting of the SD in that process as well. A message like "android-secure" or something like that.
"Error mounting /sdcard/ .android_secure!
"Skipping format..."
tylermoney said:
Based on my initial message—I did "format SD" at one point when I was attempting to get CM to boot properly initially. Hopefully that didn't jack things up further... When I boot into recover, I'm unable to create a backup or anything like that—it just gives an error when attempting to mount the "sd card."
Any thoughts? Oye. Last time I do late night work on my only phone.
Click to expand...
Click to collapse
Fixed it
Okay. So a couple of things here. Thought you guys may like to be updated on the progress, as it is positive.
1) How I fixed the SD card mounting issue
• I tried re-flashing other recoveries, and tried reformatting the sc card from that (using TWRP vs Clockwork currently)—that DID NOT work
• I was able to get the drive to be recognized by osx (not mountable though—had to attempt to mount through recovery)—I then reformatted to a Mac OS Extended (Journaled) format—when I next plugged my phone into the usb port connected to my computer, it stated that the "sd card (there isn't really one...)" was damaged, and asked if I'd like to reformat it—I did, and Valhalla.
2) I realized that I had forgotten to re-flash gapps after the initial re-flash of CM10—which is why my startup wizard never came about and I was unable to sync to my google account... blah blah. So, I flashed google apps, then cyanogen 10, and here we are.
Going to attempt a nightly later on this week probably. Going to keep stable for a few days. Hah.
I guess we can consider this a closed case for now. Thanks.
Hi,
I'm currently trying to install CyanogenMod onto my HTC One X+, but keep running into problems.
I unlocked the bootloader, and installed TWRP v2.8.7.0.
I went into recovery fine, and used "adb push" to push cm-11-20150906-NIGHTLY-enrc2b.zip onto the device and install it through TWRP.
I then tap "reboot" but it always tells me that "No OS Installed", and rebooting into the bootloader to flash the boot.img and erase the cache doesn't seem to fix this issue.
I've tried a few different versions of recoveries, like CyanogenMod's recovery, but still can't seem to get it to install any OS. Always just get stuck on the HTC logo.
Am I missing an important step, or something? Thanks for your time.
hmm...sounds correct. just try it again.
1. boot into bootloader
2. flash the boot.img from the zip you want to install (for cm11 i recommend to flash nik3rs kernel http://forum.xda-developers.com/showthread.php?t=2012320)
3. reboot into recovery
4. select wipe from twrp menu
5. install the zip
6. reboot
why dont you try cm12? much better performance!
.
el-Loko said:
hmm...sounds correct. just try it again.
1. boot into bootloader
2. flash the boot.img from the zip you want to install (for cm11 i recommend to flash nik3rs kernel http://forum.xda-developers.com/showthread.php?t=2012320)
3. reboot into recovery
4. select wipe from twrp menu
5. install the zip
6. reboot
Click to expand...
Click to collapse
Ok, I tried again.
I went into the bootloader and flashed boot.img.
Then went into recovery, and did a factory reset via the wipe menu.
Then used "adb push" to push cm-11.zip to my /sdcard/.
Then I installed the zip without any issues.
But then when restarting, it still warned me no OS was installed.
Booting anyways just got me stuck at the HTC logo.
I then tried again, this time flashing the kernel with Nik3r's file.
And then doing all the same stuff as before, but still getting the no OS was installed message and stuck on the HTC logo.
Perhaps it's the ROM I'm using? I'm not sure why it's telling me "no OS is installed" right after installing one.
el-Loko said:
why dont you try cm12? much better performance!
Click to expand...
Click to collapse
I actually can't find a ROM for CM12. I just grabbed the latest from http://download.cyanogenmod.org/?device=enrc2b.
KindDino said:
Ok, I tried again.
I went into the bootloader and flashed boot.img.
Then went into recovery, and did a factory reset via the wipe menu.
Then used "adb push" to push cm-11.zip to my /sdcard/.
Then I installed the zip without any issues.
But then when restarting, it still warned me no OS was installed.
Booting anyways just got me stuck at the HTC logo.
Click to expand...
Click to collapse
I never used "adb push" to push the ROM installation .zip onto my phone.
If you've made a nandroid backup, then go back to stock and give it a try to transfer the .zip in normal USB/Phone mode.
Afterwards repeat the process as described above.
When I flashed my last CM11 ROM, I used CWM as recovery and I flashed the boot.img after full wipe and rom/gapps installation.
After flash process I restarted the phone into bootloader and flashed the boot.img via adb. Then first normal reboot of the phone.
Worked without any issues...
KindDino said:
I actually can't find a ROM for CM12. I just grabbed the latest from http://download.cyanogenmod.org/?device=enrc2b.
Click to expand...
Click to collapse
http://forum.xda-developers.com/htc...ent/rom-cyanogenmod-12-international-t2948462
Njoatun said:
I never used "adb push" to push the ROM installation .zip onto my phone.
If you've made a nandroid backup, then go back to stock and give it a try to transfer the .zip in normal USB/Phone mode.
Afterwards repeat the process as described above.
Click to expand...
Click to collapse
Sadly, I didn't know to make a backup when I started, so I cannot go back to stock at this time.
Njoatun said:
When I flashed my last CM11 ROM, I used CWM as recovery and I flashed the boot.img after full wipe and rom/gapps installation.
After flash process I restarted the phone into bootloader and flashed the boot.img via adb. Then first normal reboot of the phone.
Worked without any issues...
http://forum.xda-developers.com/htc...ent/rom-cyanogenmod-12-international-t2948462
Click to expand...
Click to collapse
I tried with TWRP again and actually decided to write down the entire log for installing the zip, maybe that'll help. It does say some things about errors, unsure if they're actual bad, or not, as it does succeed.
Of course after installing the zip, I selected 'Reboot' then 'Reboot into Bootloader', then used 'fastboot flash' to flash the boot.img with the boot.img from within the cm-12.zip.
Code:
Installing '/sdcard/cm-12.zip'..
Check for MD5 file..
Skipping MD5 check: no MD5 file found
could not detect filesystem for /dev/block/platform/sdhci-tegra.3/by-name/APP, assuming ext4
mount: failed to mount /dev/block/platform/sdhci-tegra.3/by-name/APP at /system: Invalid argument
unmount of /system failed; no such volume
Patching system image unconditionally...
could not detect filesystem for /dev/block/platform/sdhci-tegra.3/by-name/APP, assuming ext4
mount: failed to mount /dev/block/platform/sdhci-tegra.3/by-name/APP at /system: Invalid argument
unmount of /system failed: no such volume
script succeeded: result was [0.200000]
Updating partition details...
E:unable to mount '/system'
E:unable to mount '/cache'
...done
I tried CWM a few days ago while attempting this ( as it's linked in the CyanogenMod wiki ), and I just attempted it again with it and still cannot get past the logo.
Here is the log from CWM.
Code:
-- Installing: /sdcard/cm-12.zip
Finding update package...
OPening update package...
Installing update...
detected filesysystem extr4 for /dev/block/platform/sdhci-tegra.3/by-name/APP
Patching system image unconditionally...
detected filesysystem extr4 for /dev/block/platform/sdhci-tegra.3/by-name/APP
script succeeded: result was [0.200000]
Install from sdcard complete.
When rebooting back into the bootloader, I got an error about lost root access. I selected yes.
Code:
Root access possibly lost. Fix? THIS CAN NOT BE UNDONE.
- No
- Yes - Fix root (/system/xbin/su)
Seems like you've wiped your internal SD card partition, if it's unable to detect the ext4 format.
It's mentioned under Post 2 http://forum.xda-developers.com/showthread.php?t=2066390
If so... Search the forum for a solution. Never had this issue. Good luck
Njoatun said:
Seems like you've wiped your internal SD card partition, if it's unable to detect the ext4 format.
It's mentioned under Post 2 http://forum.xda-developers.com/showthread.php?t=2066390
If so... Search the forum for a solution. Never had this issue. Good luck
Click to expand...
Click to collapse
I read the post, and maybe I did wipe my SD Card. I have no idea on how to fix that, and I'll have to research more.
I would like to just use Hasoon2000's toolkit but sadly can't find a working download for it.
Same problem here! Nothing is working. It is saying no OS. Always booting into fastboot mode. Someone help. I have a Moto G3 1540
---------- Post added at 11:27 AM ---------- Previous post was at 11:18 AM ----------
Follow these steps and recover your device.
1. Unlock your bootloader if you have it locked
2. Boot into TWRP
3. Go to Wipe
4. Go to Advanced
5. Select everything except USB - OTG and SD Card
6. Boot into fastboot
7. Download the stock image of your phone
8. Flash it to your phone ( Please find it online)
9. After flashing do not reboot!!!
10. Download Cyanogenmod recovery and flash it to your device.
11. Boot into the newly installed recovery.
12. Go into Apply Update
13. Go into Apply Update from ADB
14. Sideload the Cyanogenmod using the command adb sideload filename.zip ( Replace filename with the name of your zip)
15. After Sideloading, boot into fastboot mode.
16. In fastboot mode, Select BP Tools.
17. Boom! Your device will start booting
Hope this helps you:good::good:
I had the same issue - here's how I went about this...
KindDino said:
Hi,
I'm currently trying to install CyanogenMod onto my HTC One X+, but keep running into problems.
I unlocked the bootloader, and installed TWRP v2.8.7.0.
I went into recovery fine, and used "adb push" to push cm-11-20150906-NIGHTLY-enrc2b.zip onto the device and install it through TWRP.
I then tap "reboot" but it always tells me that "No OS Installed", and rebooting into the bootloader to flash the boot.img and erase the cache doesn't seem to fix this issue.
I've tried a few different versions of recoveries, like CyanogenMod's recovery, but still can't seem to get it to install any OS. Always just get stuck on the HTC logo.
Am I missing an important step, or something? Thanks for your time.
Click to expand...
Click to collapse
I have a Nexus 7 2013 that I commonly use as both my daily driver (tablet-only) and as my ROM-testing guinea-pig. I had AOSP Android 7 installed before I wiped everything, due to an issue with Google Play (which I just couldn't fix for the life of me). When I went to flash a new ROM (AOSP Android 7.1.1), TWRP claimed that there was 'No OS'. This would mean that you definitely wiped everything - possibly including the partitions. My guess is:
If there are no partitions (esp. System, Recovery, Boot, Cache, etc.), the data meant for them may still get written to the device's storage. But the bootloader/kernel won't recognize where to pass the torch to when it's time for the system/userspace to come in.
In order to get this back , you may need either:
A) a ROM that has images for at least the System, Cache, and Boot partitions (add your own recovery if need-be).
B) a Stock ROM from the manufacturer's website, which tends to come with all of these images ready in the .zip
Once you flash one of those, you should confirm that your bootloader is unlocked. Once that is done, flash the ROM of your dreams
I hope this helped...
TWRP bootloop
el-Loko said:
hmm...sounds correct. just try it again.
1. boot into bootloader
2. flash the boot.img from the zip you want to install (for cm11 i recommend to flash nik3rs kernel http://forum.xda-developers.com/showthread.php?t=2012320)
3. reboot into recovery
4. select wipe from twrp menu
5. install the zip
6. reboot
why dont you try cm12? much better performance!
.
Click to expand...
Click to collapse
I have quite same issue.
I have TWRP 3.0.3 (that's the only version that i found and works) on my Doogee X9 Pro (MTK chip inside).
But after flashing successfully a ROM it still reboots to the recovery. (I tried it with 3 different ROMs.)
Any idea what else should/could try?
Hey guys. I'm a newbie and need help as fast as possible. Thanks in advance..
So my problem initially was that since rooting my OnePlus X, I couldn't flash the new OTA patch. Error showing up was "error executing binary".
Kéno40 replied on my post here http://forum.xda-developers.com/one...2-0-coming-t3300825/post65214913#post65214913 to reinstall recovery. I got the twrp image from the official site for my device and flashed it. Since then, its stuck in Bootloop. Everytime I try to reboot in any mode, it shows up TWRP.
What I have tried -
I've made a backup on my SD but when I tried to go back to a previous version of TWRP and came back to the new, it isn't showing up in recovery anymore. Though the file is still there in my SD card consuming 5GB space.
I tried this command - make_ext4fs /dev/block/mmcblk0p15 Didn't work.
I've tried wiping cache/dalvik-cache...seriously, I wiped my whole Internal by wiping /data. Didn't work. I even wiped /system losing the OS and then using the recovery to get it back...still no hope.
So..in short, I'm screwed. Badly. Need help asap.
Any suggestions are appreciated. Please don't ask me why I did what I did, just help me out if possible. Meanwhile I think I'll start downloading OOS 2.2.0 full ROM, just in case. But I hope I don't have to.
Edit : I flashed TWRP both in Boot and Recovery..is this happening because of that?
choubeyaakash77 said:
Hey guys. I'm a newbie and need help as fast as possible. Thanks in advance..
So my problem initially was that since rooting my OnePlus X, I couldn't flash the new OTA patch. Error showing up was "error executing binary".
Kéno40 replied on my post here http://forum.xda-developers.com/oneplus-x/general/oos-2-2-0-coming-t3300825/post65214913#post65214913 to reinstall recovery. I got the twrp image from the official site for my device and flashed it. Since then, its stuck in Bootloop. Everytime I try to reboot in any mode, it shows up TWRP.
What I have tried -
I've made a backup on my SD but when I tried to go back to a previous version of TWRP and came back to the new, it isn't showing up in recovery anymore. Though the file is still there in my SD card consuming 5GB space.
I tried this command - make_ext4fs /dev/block/mmcblk0p15 Didn't work.
I've tried wiping cache/dalvik-cache...seriously, I wiped my whole Internal by wiping /data. Didn't work. I even wiped /system losing the OS and then using the recovery to get it back...still no hope.
So..in short, I'm screwed. Badly. Need help asap.
Any suggestions are appreciated. Please don't ask me why I did what I did, just help me out if possible. Meanwhile I think I'll start downloading OOS 2.2.0 full ROM, just in case. But I hope I don't have to.
Edit : I flashed TWRP both in Boot and Recovery..is this happening because of that?
Click to expand...
Click to collapse
If you can enter in fastboot mode, flash the recovery from fastboot command. Flash blu_sparks recovery, it's better
seems you can still go to TWRP recovery? just flash the OOS 2.2.0 full ROM.
choubeyaakash77 said:
Edit : I flashed TWRP both in Boot and Recovery..is this happening because of that?
Click to expand...
Click to collapse
Obviously...
You told the phone to boot to TWRP by flashing it to 'Boot' and that's exactly what is happening.
Just reflash your ROM and you're good to go.
choubeyaakash77 said:
Kéno40 replied on my post here http://forum.xda-developers.com/one...2-0-coming-t3300825/post65214913#post65214913 to reinstall recovery. I got the twrp image from the official site for my device and flashed it. Since then, its stuck in Bootloop. Everytime I try to reboot in any mode, it shows up TWRP.
Click to expand...
Click to collapse
If you didn't know what you were doing, why ask before doing it?
You always have to flash the recovery .img from fastboot mode via adb. Not flashed by twrp.
Reference thread :
http://forum.xda-developers.com/oneplus-x/general/discussion-how-to-root-oneplus-x-t3242830
Maybe, just flash from adb the OLD recovery.
From this recovery, reinstall your Save.
Then install new recovery via ADB.
Or flash full ROM, then reflash, VIA ADB, the OLD recovery.
Then same as above. Restora + new recovery.
Boot your phone into fastboot mode, connect it to the PC, in adb directory, open cmd promote, type
fastboot flash recovery twrp. img
Click to expand...
Click to collapse
(replace twrp. img to the recovery img you downloaded, and put it under the adb directory). Or you can type
fastboot boot twrp.img
Click to expand...
Click to collapse
, the phone will then boot into the recovery you downloaded, where you can flash a new rom. DON'T flash recovery from recovery!
---------- Post added at 03:11 PM ---------- Previous post was at 03:00 PM ----------
And if you want restore the backup on th sdcard, you might need change the storage location to sdcard in TWRP recovery,
Thanks all you guys. I'm back on with OOS 2.2.0. Had to download the complete ROM and flash it through TWRP.
I didn't wanted to download a whole almost 1 GB zip, so I tried to search for the original OxygenOS boot.img to flash it to boot. It might have worked if I hadn't completely wiped out my OS by wiping /system. Plus its almost impossibe to find that file online...
Anyway, had a nice experience screwing things up and getting back up better than before. Had fun. Learned stuff...so probably I'm not a newbie to rooting anymore.
Thanks guys for your support.
Here's the ROM I downloaded (for future reference) : https://www.androidfilehost.com/?fid=24389512218017971
Boot into your recovery [Vol+ and Power]
Connect your phone to your PC
Execute the following fastboot command on your PC (More informations on fastboot)
Code:
fastboot continue
Your phone will start right away. :good:
FixFaier said:
Boot into your recovery [Vol+ and Power]
Connect your phone to your PC
Execute the following fastboot command on your PC (More informations on fastboot)
Code:
fastboot continue
Your phone will start right away. :good:
Click to expand...
Click to collapse
fking hell.
this helped me a lot.
thx man :good:
Thank you so much. For now just gonna be content witht the stock rom.
Hello, fellow Android hackers.
Short: I am trying to install CM on a L21, but fail booting into TWRP (getting only stock recovery).
What I did, working with a brand-new phone:
Unlock bootloader.
Flash TWRP 3.0.2.
Boot to TWRP. It worked.
Try flashing CM, which failed due to some failed assert. Googling revealed a thread on these forums which suggested I had to do a stock update to Marshmallow first.
Downloaded the update through EMUI's updater.
The updater booted to TWRP which aborted the installation because of a failed zip signature check.
I disabled signature checking and ran the installation again. It succeeded.
Tried to directly install CM over it. I got the error message stating I couldn't flash on top of incompatible data.
At this point, I probably should just have wiped system and flash CM, but for some reason I decided to boot to stock.
Here is where it all seems to have gone wrong.
Try to flash and boot to TWRP, like in steps 13 to 18.
Push the B340 UPDATE.APP to /sdcard/dload.
Start the phone using power + vol down + vol up.
I have verified that the phone is on B340 and the builtin updater won't find further updates.
(I have repeated this step and the following ones countless times.)
Boot to bootloader and flash TWRP. Yes, the command succeeds.
Code:
…$ sudo fastboot flash recovery twrp-3.0.2-0-kiwi.img
target reported max download size of 266338304 bytes
sending 'recovery' (45202 KB)...
OKAY [ 1.418s]
writing 'recovery'...
OKAY [ 0.641s]
finished. total time: 2.059s
fastboot reboot
adb reboot recovery # boots to stock recovery
Boot to bootloader and flash TWRP.
Hold power + vol up
I read that the duration holding the keys matters, so I tried this very often, but I always got to one of two different stock recoveries.
Factory reset and cache wipe with one of the two stock recoveries.
I also considered crushing the phone on the wall on multiple occasions, but then decided it would not help me with my goal.
Okay.
L21 with B340, how u boot to TWRP? -_-
Also, the two stock recoveries have the menu options "Download latest version and recovery, Reboot, Shutdown" and "Reboot, Wipe data/factory reset, Wipe cache partition".
I humbly thank everyone in advance who might have some contributions to share.
ok . as i understand ,
First Charge Ur Phone Up To 50%+
Second : Go Back To Stock L 5.0.1
Third : download The latest Nightly Version OF CM + Recovery Rom | Recovey
Forth : Flash Recovery Only Throw ADB if u got any error please Attach here if success Go to step 5
Fifth : Shut Down And HOLD Volume-up + Power As soon u see Honor logo Release Power But Keep Volume Rocked Pressed !
Last : Install The Cm After U already copy To SD Card .
Gd Luck ! .
i will presume that you are on stock recovery,
now go to honor 5x repository and download b320 firmware
now place it in dload folder and flash
now boot to bootlader and try flashing twrp
then do not directly boot to revovery
just do fastboot reboot
then now do adb reboot recovery
youl be with twrp and forst things first ,compulsarily do a backup
then now assuming that you have transfered layest cm to sd card,
first goto wipe , then select all except internal and external sd cards , then wipe
now install, you should be good to go,
i had your issue when i was on b34p, but b320 is a great base and supports all custom roms..try it
(I am sorry for not answering sooner, but I have a lot on my plate right now. :/ )
Thanks for the replies.
Romiui said:
ok . as i understand ,
First Charge Ur Phone Up To 50%+
Second : Go Back To Stock L 5.0.1
Third : download The latest Nightly Version OF CM + Recovery Rom | Recovey
Forth : Flash Recovery Only Throw ADB if u got any error please Attach here if success Go to step 5
Fifth : Shut Down And HOLD Volume-up + Power As soon u see Honor logo Release Power But Keep Volume Rocked Pressed !
Last : Install The Cm After U already copy To SD Card .
Gd Luck ! .
Click to expand...
Click to collapse
2: As I understood it I only had to upgrade to M in the first place to be able to install CM. The downgrade will not undo whatever happened there?
3: I am not sure that I understand what you're trying to say, but I know of no way to flash recoveries via ADB. The point is that, as posted in the OP, flash via fastboot allegedly succeeds and as soon as I boot to the recovery, I'm back to stock.
thilak devraj said:
i will presume that you are on stock recovery,
now go to honor 5x repository and download b320 firmware
now place it in dload folder and flash
now boot to bootlader and try flashing twrp
then do not directly boot to revovery
just do fastboot reboot
then now do adb reboot recovery
youl be with twrp and forst things first ,compulsarily do a backup
then now assuming that you have transfered layest cm to sd card,
first goto wipe , then select all except internal and external sd cards , then wipe
now install, you should be good to go,
i had your issue when i was on b340, but b320 is a great base and supports all custom roms..try it
Click to expand...
Click to collapse
Thanks. I actually tried the dload method with B140 after writing this post, but it doesn't seem to work—same with B330 (the repo doesn't contain a B320 for L21). As far as I can tell, the dload install appears pretends to work fine: I'm getting a successful archive verification, an install meter and no error message. But the OS is not replaced.
I am uncertain if I need an actual microSD card—different sources seem to suggest different things here—but I generally would assume that, if there was no valid image in the right place, I would be getting an error message.
I am fine with whatever suggestion that wouldn't result in a brick. Data loss is fine, there's nothing on it.
A dumb question but do you disconnect the phone from PC or Mac after flashing twrp, firing fastboot reboot and quickly press power and vol up to boot to twrp.
If you already did that, try unlocking command once more and then try flashing it...
You can also try
Fastboot boot twrp_kiwi.img
To boot directly to twrp without flashing.
Hope any of it works.
ksdug said:
(I am sorry for not answering sooner, but I have a lot on my plate right now. :/ )
Thanks for the replies.
but I know of no way to flash recoveries via ADB.
D
Click to expand...
Click to collapse
All recoveries can be Flashed throw Fast-boot ADB Boss .
ksdug said:
(I am sorry for not answering sooner, but I have a lot on my plate right now. :/ )
Thanks for the replies.
2: As I understood it I only had to upgrade to M in the first place to be able to install CM. The downgrade will not undo whatever happened there?
3: I am not sure that I understand what you're trying to say, but I know of no way to flash recoveries via ADB. The point is that, as posted in the OP, flash via fastboot allegedly succeeds and as soon as I boot to the recovery, I'm back to stock.
Thanks. I actually tried the dload method with B140 after writing this post, but it doesn't seem to work—same with B330 (the repo doesn't contain a B320 for L21). As far as I can tell, the dload install appears to work fine: I'm getting a successful archive verification, an install meter and no error message. But the OS is not replaced.
I am uncertain if I need an actual microSD card—different sources seem to suggest different things here—but I generally would assume that, if there was no valid image in the right place, I would be getting an error message.
I am fine with whatever suggestion that wouldn't result in a brick. Data loss is fine, there's nothing on it.
Click to expand...
Click to collapse
glad you did it
thilak devraj said:
glad you did it
Click to expand...
Click to collapse
I rephrased that part as it was unclear. I didn't manage to pull off a downgrade.
muradulislam said:
A dumb question but do you disconnect the phone from PC or Mac after flashing twrp, firing fastboot reboot and quickly press power and vol up to boot to twrp.
If you already did that, try unlocking command once more and then try flashing it...
Click to expand...
Click to collapse
I did, but to no avail. Reunlocking had no effect either.
muradulislam said:
You can also try
Fastboot boot twrp_kiwi.img
To boot directly to twrp without flashing.
Hope any of it works.
Click to expand...
Click to collapse
I love you. I had totally forgotten about that. Using the boot command I managed to install CM, but I still cannot replace the stock recovery. Maybe I'll try letting CM write its own recovery with its next update, but I guess I'll leave it at that. The only downside is that my dad now needs me for doing updates. :/
Thanks very much.
ksdug said:
I rephrased that part as it was unclear. I didn't manage to pull off a downgrade.
I did, but to no avail. Reunlocking had no effect either.
I love you. I had totally forgotten about that. Using the boot command I managed to install CM, but I still cannot replace the stock recovery. Maybe I'll try letting CM write its own recovery with its next update, but I guess I'll leave it at that. The only downside is that my dad now needs me for doing updates. :/
Thanks very much.
Click to expand...
Click to collapse
wait......
you couldnt make it?? ok right now were are you at??
how to boot Honor 5x into TWRP
I know this is an old post, but since I tried for nearly a week to get my Honor 5x to boot in TWRP when pushing volume up + power button, I just wanted to post how I finally got it working, just in case anyone else should have the same problem...
1. First, I downloaded the latest stock rom. On my Honor 5x Android 5 (Lollipop) was installed, so I downloaded an Android 6 (marshmallow) stock rom. Make sure to get the correct version for your region (e.g. C432 for Europe). I found the correct rom file by simply googeling. If you are in a boot loop or do not have a working android on your phone, read instructions below.
2. I un-zipped the rom file and copied the update.app to my sd card to folder "dload"
3. I booted regularly into Android and started the update installation from the settings, where I could select option to install from SD card.
4. once that was done, i enabled USB debugging in developer tools and booted into TWRP from ADB with command
fastboot boot twrp-3.1.0-0-kiwi.img
5. Then, I installed SuperSu (SuperSU-v2.82-201705271822.zip)
6. Then, I flahed TWRP directly FROM TWRP. To do so, I clicked "Install" button, clicked "Install Image" and then selected TWRP file (which i copied to my SD card earlier). BE CAREFUL TO FLASH TWRP as Revovery (NOT boot). Actually, I first flashed twrp-3.0.0-0-kiwi.img, then directly after flashed twrp-3.0.2-0-kiwi.img and then I flashed twrp-3.0.0-1-kiwi.img (you see I was kind of desperate...). After that, from TWRP I booted into bootloader and again flashed twrp image from PC using adb:
fastboot flash recovery twrp-3.1.1-0-kiwi.img
7. from ADB, I again booted into TWRP
fastboot boot twrp-3.1.1-0-kiwi.img
8. ... where I once more installed TWRP.
After that I clicked reboot and selected to boot into Recovery. Then it finally worked.
After endless tries to get my phone to boot into TWRP when pushing volume up and power button, I am not sure which of the above steps made the difference. I think the important part is to update to the latest android version.
BTW: my first problem was I bricked my phone by trying to install lineageos from TWRP 3.1.1.1 and was in an endless bootloop. Here is how I got a regular android running:
I booted into bootloader (power + vol DOWN) and flashed the following files from adb (i got the files by extracting an android stock rom with Huawei Update Extractor (HuaweiUpdateExtractor_0.9.9.3.zip)):
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cust cust.img
Hope this helps...
It's better to post in a new thread, that will be more helpful for you