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?
Related
Did you get the message: Magic Value Mismatch:-.-.-.-.-.-?!
After flashing a new recovery it happens sometimes.
GREEN ZONE
Are you able to go to the recocery menu(power + vol up)? If not, go to BLUE ZONE. If yes, follow these steps
1. check whether you have copied your rom as "update.zip" to your SD card's root directory
2. Go to recovery menu and install update.zip
BLUE ZONE
You may did something wrong while flashing a new recovery. Here is the right method:
1. go back to fastboot mode(power+power+power+vol up) and type these commands on your PC
2. fastboot erase userdata
3. fastboot erase system
4. fastboot erase cache
5. fastboot erase linux
6. fastboot erase recovery
7. fastboot flash recovery recovery.img (change path, if recovery.img is not in the same directory as fastboot.exe)
8. fastboot reboot
Are you able now to go to the recovery menu? If yes, go to GREEN ZONE and follow steps. If not, go to ORANGE ZONE.
ORANGE ZONE
Are able to unpack the update.zip and find the system.img and boot.img files? If not, then go to RED ZONE. If yes, copy these 2 files to the directory where the fastboot.exe is, run these commands:
1. fastboot erase recovery
2. fastboot flash recovery recovery.img
3. fastboot -w
4. fastboot erase linux
5. fastboot erase system
6. fastboot flash system system.img
7. fastboot flash linux boot.img
8. fastboot reboot
ROM is installed. Enjoy it!
RED ZONE
Make sure, that you copied the same recovery.img to fastboot folder, that you had flashed before to your tablet.
Type this command in recovery mode:
1. fastboot boot recovery.img
This command will run the recovery from your PC. After the recovery menu is booted, go to GREEN ZONE and enjoy your ROM!
If this was helpful to you, please do not hesitate to click on Thanks!
Lol, nice to see my post copy/pasted without any links indicated. Anyway, I hope It's helpful for ppl.
Tried following these steps, however, I'm still getting this error... followed this thread
http://forum.xda-developers.com/showthread.php?t=1470823
installed recovery successfully (via fastboot), and update seems to install fine, until I reboot and get the "Magic Value Mismatch" again..
Any ideas?
yellowumbrella said:
Tried following these steps, however, I'm still getting this error... followed this thread
http://forum.xda-developers.com/showthread.php?t=1470823
installed recovery successfully (via fastboot), and update seems to install fine, until I reboot and get the "Magic Value Mismatch" again..
Any ideas?
Click to expand...
Click to collapse
So you installed the recovery via fastboot. Did you manage to boot into recovery mode?
I had that issue, that I couldn't boot into recovery mod from my Folio, by pressing power+Up button. Thats why I added the RED ZONE method. Its like booting recovery from your PC. (fastboot boot recovery.img). All the times I wanna upgrade my current ROM, I have to do this step, because the power+up does not work, and the Folio skips booting in recovery and wanna do normal booting. However there is no Rom installed on machine, so I get the magic value mismatch message.
So try to boot recovery from your PC, but be sure you have copied to your fastboot folder the same recovery, that you flashed onto the tablet.
I hope it was helpful. If something is not clear, feel free to ask.
Hi there, thanks for the answer.
I am able to install recovery images via fastboot.
Device is showing up as a question mark with >fastboot devices
but recovery installs fine. CWM gives a series of e: can't opne/mount /cache errors.
Foliomod 1.4 installs no problem, thanks to the method here
http://forum.xda-developers.com/showthread.php?t=1458876
yellowumbrella said:
Hi there, thanks for the answer.
I am able to install recovery images via fastboot.
Device is showing up as a question mark with >fastboot devices
but recovery installs fine. CWM gives a series of e: can't opne/mount /cache errors.
Foliomod 1.4 installs no problem, thanks to the method here
http://forum.xda-developers.com/showthread.php?t=1458876
Click to expand...
Click to collapse
Are you able to wipe cache from recovery? And what else errors are listed?
One more thing, try to flash your boot.img and system.img via fastboot as written above.
If I follow this
http://forum.xda-developers.com/showthread.php?t=1458876
and let it install cwm v 3, I get the cache error and cannot wipe or mount via recovery.
If I follow the ICS thread, and flash the new cwm v5 via fastboot, I don't get the cache error, but the rom simply won't start. If I open the package, there is a boot.img, but not a system.img, just a system folder...
I could try flashing boot.img, but I don't see how that could help
yellowumbrella said:
If I follow this
http://forum.xda-developers.com/showthread.php?t=1458876
and let it install cwm v 3, I get the cache error and cannot wipe or mount via recovery.
If I follow the ICS thread, and flash the new cwm v5 via fastboot, I don't get the cache error, but the rom simply won't start. If I open the package, there is a boot.img, but not a system.img, just a system folder...
I could try flashing boot.img, but I don't see how that could help
Click to expand...
Click to collapse
Well just to see it clear. So you are able to install Foliomod 1.4, so your Internal storage is not broken.
When I get home, I will check the system folder of ICS rom. There are some method to create system.img from an unpacked folder...
So, in CWM 5.5.0.4 you manage to install Zip from SD card, ROM and GAPPS as well, but the Rom does not boot?!
yup, that's exactly it.
Haven't tried installing Gapps since I can't even get the rom to boot.
I have a perfectly working tablet with foliomod 1.4, and I did get honeycomb to run but some apps crashed so I reverted back to foliomod.
with CWM CWM 5.5.0.4 everything seems to work great, except at reboot, nothing happens (somehow, I no longer even get the magic value mismatch)
------------------
PS. not sure if this is at all relevant, but I cannot fastboot from win7, I'm fastbooting in either ubuntu or xp via VirtualBox, and the device, when calling >fastboot devices shows up as ?????????? (ubuntu) and ? (xp)... :\
yellowumbrella said:
yup, that's exactly it.
Haven't tried installing Gapps since I can't even get the rom to boot.
I have a perfectly working tablet with foliomod 1.4, and I did get honeycomb to run but some apps crashed so I reverted back to foliomod.
with CWM CWM 5.5.0.4 everything seems to work great, except at reboot, nothing happens (somehow, I no longer even get the magic value mismatch)
------------------
PS. not sure if this is at all relevant, but I cannot fastboot from win7, I'm fastbooting in either ubuntu or xp via VirtualBox, and the device, when calling >fastboot devices shows up as ?????????? (ubuntu) and ? (xp)... :\
Click to expand...
Click to collapse
Try to install gapps as well. Maybe it helps...
nope, no luck even with gapps installed..
just a blank screen..
sigh
yellowumbrella said:
nope, no luck even with gapps installed..
just a blank screen..
sigh
Click to expand...
Click to collapse
Have you tried all the roms? ICS Alpha 1,2,3 and 4?
Tried 3 and 4, didn't bother trying earlier ones, as it seems the latest ones work for most users
yellowumbrella said:
nope, no luck even with gapps installed..
just a blank screen..
sigh
Click to expand...
Click to collapse
Hmmm strange. I ask it for you on developers forum. What you can still do, is to check the steps, that you did them correctly. In most of the cases users forget something, or do some steps incorrectly.
Try to erase userdata, cache, system, linux and recovery in fastboot. You mentioned you had problem with fastboot under Win7. Problem may occur, in case of not proper erasing.
Thanks, I'll give it another try tonight.
Fastboot in win7 is simply not seeing the device. It shows up in XP and Ubuntu, but as "??????" - not sure if that could be a symptom.
I'll post a reply as soon as I've tried, and let you know how it went.
yellowumbrella said:
Thanks, I'll give it another try tonight.
Fastboot in win7 is simply not seeing the device. It shows up in XP and Ubuntu, but as "??????" - not sure if that could be a symptom.
I'll post a reply as soon as I've tried, and let you know how it went.
Click to expand...
Click to collapse
For me it works perfectly on Win7. After Installing SDK and JDK the in the devicemanager it is shown as an Unknown device. Simply add the driver manually to it.
Download driver from attachment.
Copy it to SDK\USB_driver folder
That works for me. After its done, the Folio is shown as "Fastboot" in device manager. But connect the tablet in fastboot mode to your PC before you add driver manually to it.
Thanks for that.
Tried it, still not working in win7. It shows up correctly in device manager, but fastboot itself just doesn't want to see it...
I've attached a screenshot for you
EDIT: screenshot gets resized, but it shows device manager listing
NVIDIA Android Fastboot Device
and a terminal with fastboot not seeing the device
yellowumbrella said:
Thanks for that.
Tried it, still not working in win7. It shows up correctly in device manager, but fastboot itself just doesn't want to see it...
I've attached a screenshot for you
EDIT: screenshot gets resized, but it shows device manager listing
NVIDIA Android Fastboot Device
and a terminal with fastboot not seeing the device
Click to expand...
Click to collapse
When You have win7, You have run the console as admin!
Or copy the complete Fastboot folder to another Destination like c:\temp...
Thanks stefannsv, tried it, still not showing...
But I can access fastboot on another platform, so I assume it's not an issue, I can just switch over to another OS to flash
no go, followed both this original post (tried all steps except orange, cause the rom I'm trying to install has a system folder, not a system.img)
Last method I tried was:
1) boot into fastboot
2) boot cwm-recovery-5.5.0.4.img directly from PC
3) wipe data/factory reset
4) wipe cache partition
5) install zip from SD card and chose the alpha 4 release
installing update...
then back to recovery, reboot and voilà... magic value mismatch again (it had disappeared for a while... )
Also, when booting into CWM 3.0.0.5, I get a series of "E: Can't mount/cache/recovery" type errors.. could this be related?
booting directly into recovery from PC doesn't alllow me to install any ROMS, not even foliomod 1.4 which works if using puppet13th's method
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
Hi.
I unlocked the phone correctly via CMD.
Then, I flashed recovery VIA cmd too.
After that, I booted to recovery and the screen showed vertically half blurred screen after it booted into TWRP.
Finally, tried to install the rom unsuccessfully as TWRP didn’t detect any file in the SDCARD path. Some issue "mount sd card failed" related.
Tried, sideloading another zip file just in case but it says something about "closed device".
Now I cannot flash anything and I cannot reboot normally as It seems to be everything erased.
I can access fastboot and TWRP (although I cannot flash or side load anything...)
What could I do?
Flash this twrp https://dl.twrp.me/x2/twrp-3.2.1-0-x2.img
Boot into twrp
Wipe data partition
Install any rom you want
Heyyo, unfortunately adb sideload is currently broken on x2 official builds.
I'd recommend using...
adb push NameOfROM.zip /sdcard
That will push the ROM to your Sdcard folder. Same can be repeated for Gapps
I wanted to get rid of the Chinese bloatware that came with the phone and decided to install the xiaomi.eu rom.
This is what I did;
unlock the bootloader
downloaded TWRP from official website (3.2.1-0)
installed TWRP with adb, reboot into TWRP with VolUp+Power buttons combination
factory reset and clean data partition
reboot
PROBLEM 1: stuck at MI logo... I said "whataver" and reboot into TWRP
plugged into PC, and transferred rom into internal memory manually
PROBLEM 2: I couldn't push with adb because the device is not recognised in fastboot
in TWRP press install, try to install rom zip
PROBLEM 3: get error 7 message "This package is for device gemini.."
I say "whatever" and download global stable rom from MIUI
did another system data cache clean, tried to install rom
PROBLEM 4: "unmount of /firmware failed: no such volume" "mount:failed to mount /dev/block/bootdevice/by-name/sec at /firmware: invalid argument"
It says "scripting succeeded: result was [1.000000] Updating partition details...done", but when I reboot I'm stuck at the MI logo again!
Any help is very appreciated!
tryhardernow said:
I wanted to get rid of the Chinese bloatware that came with the phone and decided to install the xiaomi.eu rom.
This is what I did;
unlock the bootloader
downloaded TWRP from official website (3.2.1-0)
installed TWRP with adb, reboot into TWRP with VolUp+Power buttons combination
factory reset and clean data partition
reboot
PROBLEM 1: stuck at MI logo... I said "whataver" and reboot into TWRP
plugged into PC, and transferred rom into internal memory manually
PROBLEM 2: I couldn't push with adb because the device is not recognised in fastboot
in TWRP press install, try to install rom zip
PROBLEM 3: get error 7 message "This package is for device gemini.."
I say "whatever" and download global stable rom from MIUI
did another system data cache clean, tried to install rom
PROBLEM 4: "unmount of /firmware failed: no such volume" "mount:failed to mount /dev/block/bootdevice/by-name/sec at /firmware: invalid argument"
It says "scripting succeeded: result was [1.000000] Updating partition details...done", but when I reboot I'm stuck at the MI logo again!
Any help is very appreciated!
Click to expand...
Click to collapse
Well, you need here some corrections to do things in the right way.
In the 3rd step you say that installed twrp through adb but twrp can´t be installed through adb; maybe you wanted to mean fastboot that is other thing.
In the 4th step most important is at first reboot to twrp swipe to allow modifications and then you have to perform "format data" to can reboot normally to system although some times is required no-verity zip for R5P vince (just Google) some users refer that is needed despite I never did.
In the 8th step; fastboot mode can´t work simultaneously meanwhile are you using adb so you don´t need it when you are using adb although this you can´t transfer a file from pc to your device using simply adb; you need to enable first in advanced options from twrp the feature adb sideload then placing the file that you want to transfer from pc to device in the same adb folder you have to type in a terminal with admin rights adb sideload nameoffile.zip but this is not to transfer a file only but to transfer it and flash it onto device.
In the 10th step first open the zip file of the rom with notepad++, go to META-INF/com/google/android/updater-script and check what device is it made for and additional you can browse to system/build.prop and similarly open it and check ro.product/model cause gemini is other variant.
So I think that you flashed firstly a rom for other device and maybe you need to restore some partitions to correct this using MiFlash tool.
But first to this if most of all partitions are working and not damaged you can flash almost any partition through fastboot mode, unzip the rom in the same adb folder and type every file for every partition one by one but maybe you need only system, boot and userdata partitions so try first these three, I hope that you know syntax of fastboot commands.