Hi Guys,
I had CM 10 on my phone and I was able to use CWM successfully. But, then I flashed Pandroid 4+ (CM 11 based) Kitkat 4.4 ROm on my phone.
Now, I am not able to boot into recovery mode. As i try to enter into recovery mode, My phone gets stuck in the boot screen and does not boot up. After so many attempts of pressing power button, it starts. It's so painful.
I want to revert back to CM 10 stable rom, but I can't boot in to recovery mode.
I did some research and found a CWMFixed.zip as a solution. It contains a boot.img file. Please let me know how can i flash this file without entering into CWM.
Or if there is any other solution for this problem then please let me know.
It urgent.
@tysonraylee I hope you can help me in this as you had posted a similar query in other thread.
Thanks in advance.
My friend, If you would have only read the PA thread properly you would know that beta 5 has the bug where it breaks the recovery you would have avoided the problem altogether but anyways i would suggest that you flash an odin format (.tar) kernel using PC Odin which will get you a working recovery and from there it should be pretty easy, if you took a nandroid backup before you will be able to restore your previous rom and if you didnt you have to flash a different rom of your choice
flash this TW PC odin format (.tar) kernel by bauner https://www.androidfilehost.com/?fid=95784891001607164
make sure once you flash this to not let the phone boot into ROM, after flashing successful take off the battery and then insert back and boot into recovery.
Once you have a recovery then you need a SE Linux compatible recovery so for that connect the device to PC and mount the usb storage through recovery then transfer
This Bauner's KK kernel if you require CWM https://www.androidfilehost.com/?fid=95784891001608504
and this GeeckoDev Raw kernel if you require TWRP recovery http://forum.xda-developers.com/showpost.php?p=53978758&postcount=583 (download raw_kernel_r6_k44.zip)
once transfered to your device flash the one you require and remember we are flashing these kernel just for temporary use and once a rom is flashed they will get overwritten with the recovery that comes with the rom kernel so you dont have to worry about these kernels
Once flashed remember to reboot to recovery and not system, once the device boots into your desired recovery then either restore your previous rom from backup or falsh a new one
hope this helps and remember next time before flashing a rom read the OP and atleast 4-5 last pages. Believe me this will save you a lot of trouble in your future flashing endeavours
Related
Hi guys!
Yesterday I successfully rooted my NS (it is a European SLCD model with stock 2.3.6 on it) following the newest guide on nexusshacks.com. So I ended up with TWRP recovery.
Then I thought the easiest to install CM is via Rom Manager. Therefore I had to change recovery for CWM. (I flashed the latest one.)
And here comes my question: why am I unable to flash CM?
First I tried it in Rom Manager, after wiping everything and rebooting system nothing happens, except for a big yellow exclamation mark.
Then I downloaded the proper CM myself and I tried to do the whole process manually in recovery menu. After wiping and choosing update from SD card I get a message like the process is aborted.
I also tried with an older CWM and with other ROM.
Any suggestions?
Thanks a lot
Sent from my Nexus S using XDA App
Boot into bootloader, then flash recovery via fastboot.
fastboot flash recovery recovery.img
stock firmware will rewrite your recovery after each boot. flash recovery then flash this right after.
Follow what SEAN SAys..............He is a Master in all these , and he helped me with details to root, flash cwm, make it sticky and flash custom ROMS.
It took me 5 minutes to do all those , and Now I am switching Roms like I switch my underwears every day twice.
I must say, Sean has the best possible way which is like a finger click.
Hey All,
I just got my One XL and I was so excited by the root on 2.20 that I decided to try and flash the custom rom of AOKP on onto it.
After rooting the phone, I did the following:
Flashed TWRP 2.3.1.0 - success
Then I went and saw the thread about the AOKP rom and followed instructions. On that thread, it states that you must flash the boot.img before doing this through fastboot if you are coming forom 2.20 firmware, so I did that. Then I saw that it said on the thread "do not complain about bootlooping if you flashed a custom KERNEL or did not manually flash the stock KERNEL via fastboot" As this was the first custom rom I had attemped with this phone I assumed that I had the stock KERNEL already installed, so I did not flash any kind of kernel.
As soon as I flashed the boot.img from AOKP, I saw that there was red writing on the bootloader about this being for development use only and I noticed that the phone would get past the bootloader to a black screen and then would reboot (boot loop).
I thought that the issue here was that I did not flash the kernel so I went and downloaded the rohan.kernel and flashed that. HOWEVER, I did not realize that I was meant to use recovery to do that and I pushed the boot.img from within the kernel via fastboot instead of using recovery to flash the new kernel (not sure if that matters all that much, but I think that from now on all rom work will be done in the day time after sleeping a little more).
After doing that I see no change in the performance of the phone (it is still boot looping). I am unsure of what to do now. I managed to push the KERNEL zip file and the ROM zip file to the phone via adb but when I try and install them via TWRP I am getting an error because the phone reports that it is unable to mount /sdcard/.
Can one of the far more knowlegable gurus here point me in the right direction? I have wiped the cache and davlik cache numerous times but that has not helped. Should I use TWRP to wipe the system? How can I get the phone back to a place where I can install the new rom?
Thanks!!
ackerchez said:
Hey All,
I just got my One XL and I was so excited by the root on 2.20 that I decided to try and flash the custom rom of AOKP on onto it.
After rooting the phone, I did the following:
Flashed TWRP 2.3.1.0 - success
Then I went and saw the thread about the AOKP rom and followed instructions. On that thread, it states that you must flash the boot.img before doing this through fastboot if you are coming forom 2.20 firmware, so I did that. Then I saw that it said on the thread "do not complain about bootlooping if you flashed a custom KERNEL or did not manually flash the stock KERNEL via fastboot" As this was the first custom rom I had attemped with this phone I assumed that I had the stock KERNEL already installed, so I did not flash any kind of kernel.
As soon as I flashed the boot.img from AOKP, I saw that there was red writing on the bootloader about this being for development use only and I noticed that the phone would get past the bootloader to a black screen and then would reboot (boot loop).
I thought that the issue here was that I did not flash the kernel so I went and downloaded the rohan.kernel and flashed that. HOWEVER, I did not realize that I was meant to use recovery to do that and I pushed the boot.img from within the kernel via fastboot instead of using recovery to flash the new kernel (not sure if that matters all that much, but I think that from now on all rom work will be done in the day time after sleeping a little more).
After doing that I see no change in the performance of the phone (it is still boot looping). I am unsure of what to do now. I managed to push the KERNEL zip file and the ROM zip file to the phone via adb but when I try and install them via TWRP I am getting an error because the phone reports that it is unable to mount /sdcard/.
Can one of the far more knowlegable gurus here point me in the right direction? I have wiped the cache and davlik cache numerous times but that has not helped. Should I use TWRP to wipe the system? How can I get the phone back to a place where I can install the new rom?
Thanks!!
Click to expand...
Click to collapse
First of all I think if you're on 2.2 fw I don't think you can flash kernels through TWRP - I think it has to be through fastboot, I don't know first hand as I'm still on an earlier fw version.
Secondly if you can get into recovery you can flash another rom.
Go to Mount > Mount USB Storage with your phone connected via USB, it should mount as a drive otherwise windows asks you to format format the drive if this happens chances are may have wiped it in bootloader with factory reset or clear storage in either case just format the drive.
You can then drag and drop another rom onto the phone and flash that - remember to extract the boot.img from the rom and flash via fastboot so it will boot.
Goodluck
thejosh86 said:
First of all I think if you're on 2.2 fw I don't think you can flash kernels through TWRP - I think it has to be through fastboot, I don't know first hand as I'm still on an earlier fw version.
Secondly if you can get into recovery you can flash another rom.
Go to Mount > Mount USB Storage with your phone connected via USB, it should mount as a drive otherwise windows asks you to format format the drive if this happens chances are may have wiped it in bootloader with factory reset or clear storage in either case just format the drive.
You can then drag and drop another rom onto the phone and flash that - remember to extract the boot.img from the rom and flash via fastboot so it will boot.
Goodluck
Click to expand...
Click to collapse
Hey!
Thanks a ton for your reply! I managed to get the phone to install a new ROM (AOKP V5) and it seems to boot up. Now when I get into that rom, I see all kinds of things crashing on me. The "Settings" app crashes, the keyboard crashes..any idea?
Did you wipe system, factory reset, davlik and cache from within TWRP before flashing?
Try that otherwise if you're still running into issues post in the thread.
You flashed the 11/10 JB gapps?
Sent from my Nexus 7 using xda premium
ok, i got the phone back up now and have been able to flash stuff properly.
I am working on an issue where after flashing a new rom (AOKP v4) and then a new kernel right after (rohan.kernel V2) the rom seems to hang on the loading splash screen. Has anyone else had this happen? Know how to solve it?
ackerchez said:
ok, i got the phone back up now and have been able to flash stuff properly.
I am working on an issue where after flashing a new rom (AOKP v4) and then a new kernel right after (rohan.kernel V2) the rom seems to hang on the loading splash screen. Has anyone else had this happen? Know how to solve it?
Click to expand...
Click to collapse
Did u wipe everything? (davlik, cache)
Sent from my HTC One XL using xda premium
Hello,
1st.: while starting this new thread, I looked through the automaticly generated similar threads and found non that was suiting my problem.
Last night I unlocked the bootloader of my wifes Xperia L (C2105) and got stuck into an boot loop. After this I had the need to flash an original rom (4.1.2). This results in an total wipe of the phone :crying:
Now the phone has an unlocked bootloader and an old Android Version. I want to install the pacman rom 4.4.4. I know i have to use cwm or twrp to do this, but do I need to root the device?
I'm a little bit confused. I thought installing the *.img-File from TWRP, with the folloing command, will get me the recovery option an with this option
Code:
c:\fastboot\Fastboot.exe flash boot C:\fastboot\openrecovery-twrp-2.8.4.0-taoshan.img
Can anyone help me out?
My wife is not upset, but with the boot loop from last night in my mind, I'm quit unsure what to do next.
many thanks in advanced
Felix
you need to root the device and use flashtool by androxyde(Easier and user friendly), first download the rom and put it in internal/external memory and then install thunderzap 4.12 by select bootkk.img and install it in fastboot mode in flashtool, now enter the recovery go into wipe and format options and choose clean to install a new ROM and then flash the pac rom and reboot
Root isn't necessary.
Download PAC ROM, Take boot.img inside the zip.
Flash boot.img via fastboot.
Boot into recovery, wipe data / factory reset.
Flash ROM and GApps.
That's it
NOP, you dont need to root to install a custom rom
felix leiter said:
Hello,
1st.: while starting this new thread, I looked through the automaticly generated similar threads and found non that was suiting my problem.
Last night I unlocked the bootloader of my wifes Xperia L (C2105) and got stuck into an boot loop. After this I had the need to flash an original rom (4.1.2). This results in an total wipe of the phone :crying:
Now the phone has an unlocked bootloader and an old Android Version. I want to install the pacman rom 4.4.4. I know i have to use cwm or twrp to do this, but do I need to root the device?
I'm a little bit confused. I thought installing the *.img-File from TWRP, with the folloing command, will get me the recovery option an with this option
Code:
c:\fastboot\Fastboot.exe flash boot C:\fastboot\openrecovery-twrp-2.8.4.0-taoshan.img
Can anyone help me out?
My wife is not upset, but with the boot loop from last night in my mind, I'm quit unsure what to do next.
many thanks in advanced
Felix
Click to expand...
Click to collapse
you can download the rom, extract it and keep, boot.img file, in fastboot folder, and also keep the downloaded rom zip file in sd card for later use.
than you can use use fastboot commands to flash those boot.img which will install the recovery into your phone, than .
use reboot command in fastboot, it will reboot your phone, take out your cable, using volume up key go to recovery,
there clear all the cache and delvik cache file, then, install your custom rom by selecting from your sd card, it will take a bit of time for first time, so don't worry,
than you are done,
Hey guys
so after ive rooted my MI4i, i installed a custom ROM called Infinitive OS, which is quite good then i stupidly flashed Sensei Kernel to My MI4i, and now, my phone is bricked. I tried to turn it on, after the Mi logo, it shuts off. I am still able to get to my TWRP Recovery, tried to delete cache/dalvik/factory reset, but no use. Still can't boot to system. PLEASE HELP GUYS
Thanks..
jonathanfilbert said:
Hey guys
so after ive rooted my MI4i, i installed a custom ROM called Infinitive OS, which is quite good then i stupidly flashed Sensei Kernel to My MI4i, and now, my phone is bricked. I tried to turn it on, after the Mi logo, it shuts off. I am still able to get to my TWRP Recovery, tried to delete cache/dalvik/factory reset, but no use. Still can't boot to system. PLEASE HELP GUYS
Thanks..
Click to expand...
Click to collapse
Tried flashing back the rom? and did you get to boot into the rom before flashing the kernel?
Yes, b4 I flashed the kernel everything works fine.
jonathanfilbert said:
Yes, b4 I flashed the kernel everything works fine.
Click to expand...
Click to collapse
If i understand well, if you can get to twrp there is no reason to worry...
You just download an official / developer rom or any custom rom, reflash and you are done.
Yeah I know, thing is, mi4i doesn't have an external memory slot..
jonathanfilbert said:
Yeah I know, thing is, mi4i doesn't have an external memory slot..
Click to expand...
Click to collapse
go to recovery and connect your phone in mtp mode from recovery , take backup from internal memory and flash official stable rom
You may flash the device recovery/kernel/firmware via FastBoot
Flash TWRP Recovery via Fastboot, then adb sideload a ROM on the Device. Or Download Official Fastboot firmware for the device and flash it.
Don't forget to say thanks
flash the device with fastboot rom via FastBoot using mi flash
I have the same problem. Just Go into TWRP and wipe Dalvik/Cache/Data/System, after that just flash ROM again and everything works fine
The problem is with firmware and kernel. The firmware isn't compatible with kernel. If u flash the whole rom with firmware it will be fine, if U know witch FW have u used flash it flash it back or flash back original kernel.
check http://forum.xda-developers.com/mi-4i/development/miui-firmware-flash-t3367968
Regards
Whatever You Do, first take a backup of your EFS Partition with TWRP or MI Toolkit. My device crashed and corrupted all partitions suddenly and my IMEI is lost now and I didn't have any backup of EFS to restore my IMEI.
And for restoring your device back to normal you will have to follow this..
1. Take backup of EFS and store it somewhere safe in you pc.
2. Download and extract the Fastboot ROM for Mi4i from here : http://update.miui.com/updates/v1/fullromdownload.php?d=ferrari_global&b=X&r=global&n=
3. As you have already rooted, I suppose that you already have adb drivers installed. If not then install
4. Open Recovery and press and hole POWER and VOLUME DOWN button after recovery boots up completely and do not release the keys until fastboot opens.
5. open Terminal(Linux)/CMD(Windows) and navigate into the directory you just downloaded and extracted.
5. Run "flash_all.bat"(Windows)/"flash_all.sh"(Linux).
6. Give it some time and you will get a brand new MIUI 7. After flashing miui 7 you can install any rom you wish.
Let me know if your device gets fixed or if you need any help..
Thanks.
not able boot to twrp recovery and even not in system
not able start twrp in my mi4i as system get crashed and now my phone is not booting up just suck in mi logo. plz help not able to start my device and not able flash my device. I think I lose my imei no. because i was trying to change my imei. I have a backup of miui8 by twrp will it help me to start my device. plz help !!!
My mi4i couldn't complete booting,when i try to switch on it will show mi logo and goes to black and again mi logo(mi logo is blinking in a regular interval) the red notification light is also blinking,i tried the mi flash tool ,but the problem is still alive....i was using cm 13 ....somebody please help me
Hello everyone, I'll tell you what happened
First I was in CM13.1, then I flashed to oxygen OS 3.1.4 custom
(When I flash the ROM, without warning me the recovery was updated to the version TWRP 3.0.3-2TugaPower, previously being in a version inferior to 2.8)
After logging in to the new recovery, I noticed that the recovery version was not on the TWRP page, so I decided to flash the most recent version of TWRP (twrp-3.1.1-0-bacon.img), flashe it through Android sdk (Fastboot), everything went well the pc recognized me the OPO in fastboot Mode and flashe the recovery without problems, the problem came when I try to enter the new recovery the OPO does not enter the recovery stays in the OnePlus Logo.
(Before updating the recovery I tried to restate the backup of my previous rom CM13.1 but when I was going to restart it it stays in the OnePlus logo, and when I go to recovery I fixed that in the section of "Mount" system is not checked , Active but still the same, and when I return to recovery is removed.)
I ask you if you can give me ideas to be able to have recovery again and revive my OPO plz.
Molex69 said:
Hello everyone, I'll tell you what happened
First I was in CM13.1, then I flashed to oxygen OS 3.1.4 custom
(When I flash the ROM, without warning me the recovery was updated to the version TWRP 3.0.3-2TugaPower, previously being in a version inferior to 2.8)
After logging in to the new recovery, I noticed that the recovery version was not on the TWRP page, so I decided to flash the most recent version of TWRP (twrp-3.1.1-0-bacon.img), flashe it through Android sdk (Fastboot), everything went well the pc recognized me the OPO in fastboot Mode and flashe the recovery without problems, the problem came when I try to enter the new recovery the OPO does not enter the recovery stays in the OnePlus Logo.
(Before updating the recovery I tried to restate the backup of my previous rom CM13.1 but when I was going to restart it it stays in the OnePlus logo, and when I go to recovery I fixed that in the section of "Mount" system is not checked , Active but still the same, and when I return to recovery is removed.)
I ask you if you can give me ideas to be able to have recovery again and revive my OPO plz.
Click to expand...
Click to collapse
I guess you didn't read the OP of Oxygen Os correctly,he clearly mentioned that this 'Tuga Power Recovery' is patched to work with Oxygen Os's firmware and one should not flash any other recovery.Now,what you can do is this,
https://drive.google.com/file/d/0B-ikULjZZlloNHpOdVBrTzQxZzQ/view?usp=drive_web
> Download This file, install it somewhere and run Revert-2-CM.exe. Make sure you have fastboot drivers installed or it wont work.Avoid using any Antivirus program while doing this as they might give false alarms.After this you'll be restored to TWRP then you can flash any rom you want.The reason due to which you weren't able to find 'TugaPower Recovery' on TWRP page is because this is an Unofficial Recovery.
Question
What does the program do with the OPO?
If you are familiar with fastboot commands, this method should work. Had my OnePlus in the same situation last night messing around with Efidroid. Phone was bootlooping. Efidroid boot menu as well as recovery mode were both inaccessible. I had tried several other things but none worked for me. *CAUTION: this method did ERASE my userdata.* I downloaded a fastboot-able stock full firmware zip, then manually reflashed device. My beloved OnePlus is no longer my daily driver but still my fave device to experiment with so I just used COS 13.1 file. After full reboot, I downloaded and flashed official TWRP. Device is fully functional again, but without OOS installed.
Molex69 said:
What does the program do with the OPO?
Click to expand...
Click to collapse
It'll change your firmware and alter your recovery to a functional TWRP.You'll lose Oxygen Os after doing this.Though you can use this anytime when not being able to flash TWRP.
What should i do
Thanks a lot thanks to the method you told me my OPO has recovery again really thanks, but I have a question, I still in the TugaPower recovery, should I flash the stock recovery or the newest version of TWRP?
Because I do not know if flashing again the TWRP will happen the same