Hi,
I tried to flash CM10.2 (stable) by first flashing boot.img with fastboot and then flashing the zip from the recovery. When that didn't work I tried to flash different versions of CM10/11, both from get.cm and from FXP. I have an unlocked bootloader and ran stock Android 4.2 before. Is there any known issues that I might've missed?
Related
Hey guys. I have unlocked my bootloader, TWRP 3.0.2.1 is installed. I was able to install aosp-5.1.1-prerooted-v4 and MIUI7 5.1 RN3Pro 6.4.21 greatslon.
However, I have issues flashing official ROMs, e.g. 6.4.14 (MIUI7) (http://en.miui.com/download-301.html) is getting stuck on Miui logo.
Am I missing something?
You need to flash patched boot.IMG file for respective ROM you are flashing Using TWRP..
you can find them here..
http://miuidroid.com/rn3/boot_images/
Try using the newest TWRP that auto-patches the boot.img for you
I flashed Oxygen Recovery and then installed the latest build of H2OS. After the ROM booted up, I flashed TWRP 3.0.2, 3.0.1 and 3.0.0 but none of these boot, i.e., my phone doesn't boot to recovery. What can I do now?
P.S.: Bootloader is unlocked
Found a remedy, flashing the BluSpark's modded version worked. Someone please tell me how to delete this thread :3
I am using TWRP 3.0.2.0 It is giving me problems as shown in images below.
I tried flashing new recovery but it also couldn't get flashed. While flashing new CM 13/CM14.1 ROMs it is giving errors, but it flashes older CM 13 ROMs fine.
dvaibhavd said:
I am using TWRP 3.0.2.0 It is giving me problems as shown in images below.
I tried flashing new recovery but it also couldn't get flashed. While flashing new CM 13/CM14.1 ROMs it is giving errors, but it flashes older CM 13 ROMs fine.
Click to expand...
Click to collapse
Bro wait....!!!
Is this real?
You are using too old recovery(as your ss says 2.8.7)+old boot loader..you need some work on your phone to be able to flash new cm 13/14.1.
Just head over to general thread and find how to upgrade boot loader and install latest twrp.
After that you can flash all latest available ROM.
Boot logo Problem
Hey I have used this method http://forum.xda-developers.com/one...update-bootloader-firmware-to-t3478917/page20 and updated the BL.However after flashing CM14 I am stuck on 1+ logo.
I was able to flash stock Oxygen Rom .I want to flash CM 14 please help
Same
utkhirodka said:
Hey I have used this method http://forum.xda-developers.com/one...update-bootloader-firmware-to-t3478917/page20 and updated the BL.However after flashing CM14 I am stuck on 1+ logo.
I was able to flash stock Oxygen Rom .I want to flash CM 14 please help
Click to expand...
Click to collapse
Same here with the TZ issues. As for the recovery, the TWRP version 3.0.2-0 is the most latest one that I can flash & boot into successfully. If I flash anything newer than 3.0.0-1 my OPX is stuck on OP logo as well.
My phone is stuck at one plus boot logo when i tried to go into recovery mode or tried to start it the oneplus logo popped and goes out again and again and when i tried to flash twrp through fastboot mode it say the device is locked cant change or erase the recovery what should i do please guide me
The only recovery that will flash on mine is 3.0.2-0. I've tried flashing through Fastboot. I've even tried to use the dd command for both 3.0.3-0 official and blu sparkz v41 and it gets stuck at the OnePlus logo.
Phone still boots into OOS just fine and 3.0.2-0 flashes through the old JMZ TWRP app just fine. It's just any other method that doesn't work.
The latest recoverys for new bootloader is 3.0.3, bluesparks 3.0.2-1 V41 or Sultans updated TWRP. 3.0.2 and under us for old bootloader.
Exodusche said:
The latest recoverys for new bootloader is 3.0.3, bluesparks 3.0.2-1 V41 or Sultans updated TWRP. 3.0.2 and under us for old bootloader.
Click to expand...
Click to collapse
Again, I tried flashing 3.0.3 and it wouldn't stick.
blackknightavalon said:
Again, I tried flashing 3.0.3 and it wouldn't stick.
Click to expand...
Click to collapse
After flashing recovery you have to boot right into it with fastboot command then swipe to allow modifications?
Exodusche said:
After flashing recovery you have to boot right into it with fastboot command then swipe to allow modifications?
Click to expand...
Click to collapse
As stated above, all it does is hang at the OnePlus logo.
Also...
fastboot boot drive:\path\to\twrp-3.0.3-0-onyx.img
downloading 'boot.img'...
OKAY [ 0.507s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.540s
Click to expand...
Click to collapse
blackknightavalon said:
As stated above, all it does is hang at the OnePlus logo.
Click to expand...
Click to collapse
Ok sorry what I did was keep it simple. Reflash original stock recovery, flash 2.2.3 then flash 3.1.4 and boot. Just skip everything and reboot back to bootloader mode. Now you can flash latest TWRP and should boot latest ROMs without any issues.
Exodusche said:
Ok sorry what I did was keep it simple. Reflash original stock recovery, flash 2.2.3 then flash 3.1.4 and boot. Just skip everything and reboot back to bootloader mode. Now you can flash latest TWRP and should boot latest ROMs without any issues.
Click to expand...
Click to collapse
2.2.3 flashed successfully. I already know 3.1.4 will work. I'll post again if your plan completely works.
...and I'm still getting the same errors after flashing 3.1.4 through stock recovery. o.0
I'm going to start from the earliest firmware available and flash progressively from there and see if that works.
Hey guys.
I'm using a 32/3GB kenzo with an unlocked bootloader running official rr mm.
I formatted the phone, flashed CM14 firmware, flashed the official RR nougat and GAPPS, then rebooted to system.
At this point, it started bootlooping, booting to the MI splashscreen, staying there for about half the time it usually does, before rebooting and repeating the process.
At this point, I was unable to access recovery, but was able to access fastboot and edl.
Flashing a recovery using the "fastboot flash recovery" command failed, so I assume that the partitions were corrupted.
I had to revert to MIUI by flashing through edl using MI flash, which fixed all the issues.
Can someone tell me what I did wrong?
Or should I follow the newbie guide 2.0 from the forums?
Thanks in advance to anyone who replies.
Ivanlai said:
Hey guys.
I'm using a 32/3GB kenzo with an unlocked bootloader running official rr mm.
I formatted the phone, flashed CM14 firmware, flashed the official RR nougat and GAPPS, then rebooted to system.
At this point, it started bootlooping, booting to the MI splashscreen, staying there for about half the time it usually does, before rebooting and repeating the process.
At this point, I was unable to access recovery, but was able to access fastboot and edl.
Flashing a recovery using the "fastboot flash recovery" command failed, so I assume that the partitions were corrupted.
I had to revert to MIUI by flashing through edl using MI flash, which fixed all the issues.
Can someone tell me what I did wrong?
Or should I follow the newbie guide 2.0 from the forums?
Thanks in advance to anyone who replies.
Click to expand...
Click to collapse
Which recovery you uaed for flashing rr n. Because you went bootloop and recovery was not able to access that means may be some problems in recovery or either in rom/gapps zip. Make sure you are flashing gapps for NOUGAT only. And use latest stable miui firmware (not cm14 zip one although may be both are same)
Try this
1. Flash zcx recovery (I recommend this, never disappointed)
2. Flash latest miui stable firmware
3. Flash rom zip
4. Flash gapps n
Boot to system
5. Then flash kernel or anything.
Apcoolboy said:
Which recovery you uaed for flashing rr n. Because you went bootloop and recovery was not able to access that means may be some problems in recovery or either in rom/gapps zip. Make sure you are flashing gapps for NOUGAT only. And use latest stable miui firmware (not cm14 zip one although may be both are same)
Try this
1. Flash zcx recovery (I recommend this, never disappointed)
2. Flash latest miui stable firmware
3. Flash rom zip
4. Flash gapps n
Boot to system
5. Then flash kernel or anything.
Click to expand...
Click to collapse
Thanks for the reply, I'll try it soon. Can you tell me how to get the miui stable firmware?
Should I fastboot flash latest MIUI stable before flashing the ROM or is there a MIUI firmware zip file to flash?
Ivanlai said:
Thanks for the reply, I'll try it soon. Can you tell me how to get the miui stable firmware?
Should I fastboot flash latest MIUI stable before flashing the ROM or is there a MIUI firmware zip file to flash?
Click to expand...
Click to collapse
There is flashable zip file which is extracted from miui rom only. So both way will be good as flash latest stable miui rom and then twrp > rom zip > gapps. Or twr0 > firmware zip (search in any custom rom thread you will get one) > custom rom zip > gapps.
Only benefit of flashing firmware zip is less time consuming and less file size (around 50mb) compare to full miui rom.
Ivanlai said:
Thanks for the reply, I'll try it soon. Can you tell me how to get the miui stable firmware?
Should I fastboot flash latest MIUI stable before flashing the ROM or is there a MIUI firmware zip file to flash?
Click to expand...
Click to collapse
https://forum.xda-developers.com/redmi-note-3/development/firmware-hmnote3proglobal-t3574361
Ivanlai said:
Hey guys.
I'm using a 32/3GB kenzo with an unlocked bootloader running official rr mm.
I formatted the phone, flashed CM14 firmware, flashed the official RR nougat and GAPPS, then rebooted to system.
At this point, it started bootlooping, booting to the MI splashscreen, staying there for about half the time it usually does, before rebooting and repeating the process.
At this point, I was unable to access recovery, but was able to access fastboot and edl.
Flashing a recovery using the "fastboot flash recovery" command failed, so I assume that the partitions were corrupted.
I had to revert to MIUI by flashing through edl using MI flash, which fixed all the issues.
Can someone tell me what I did wrong?
Or should I follow the newbie guide 2.0 from the forums?
Thanks in advance to anyone who replies.
Click to expand...
Click to collapse
unlock your bootloader again it will run without problem..
Hi! I have a weird issue. Any new roms like 7.1.2, 8.0etc are just not booting up in my redmi note 3. I always get stuck at the boot logo. The phone vibrates and hints as if it is going to boot up boot its not. The process continues and the phone doesn't boot up. It works all fine with the older roms. But with newer version the roms dont boot up. I tried several roms like Nitrogen,RR,Linege OS etc. But newer versions of both Nougat and Oreo roms don't boot up. I don't have any clue of what to do now. I have zcx twrp installed and have officially unlocked the bootloder. Please if anyone have any insight regarding the issue it will be helpful.
Thank You.
Check whether the bootloader is still unlocked by commands. Twrp in this case, is useless so flash MIUI official rom & again unlock officially.
Make sure you wipe everything in Twrp if the command says bootloader is unlocked.
Try flashing LazyFlasher after the ROM. Also, are you flashing the recommended firmwares before flashing the ROM?
Update modem (firmware). Either by: flashing latest MIUI Beta fastboot rom or from here