Today I flashed blisspop rom v2.2 + Gapps in my Mi3 using TWRP v2.8.6.0. But after the reboot, the phone boots into Stock MIUI 6. It looks like stock MIUI is installed. How to boot into newly installed custom rom.Is it anything related to dual boot or something went wrong during flash.
Probably you flashed the custom rom in system 2. Boot in system 1 via cwm and then flash the custom rom.
use CWM
Mi3 uses two system. system 1 and system 2.
TWRP always flashes in one system alone...
Use CWM recovery instead of TWRP. Even I faced same issues when i started flashing, etc )
check miui forums for CWM zip files.
http://forum.xda-developers.com/xiaomi-mi-3/development/recovery-clockworkmod-mi3w-6-0-5-0-t2847367
Flash it on both systems otherwise it won't work
If you wanna you dual boot (i don't recommend) then install miui on both systems, wipe data, just boot to sys 1 and reboot to recovery, take the system 1 backup with data, wipe data, enable tdb(true dual boot), again wipe to be sure, install custom rom on both systems, boot it and rebbot to recovery, restore system backup to system 2 n data 2, done
This method is faily old so i don't know if that works or not as i don't use tdb
Hey ,
I am also Facing the same issue as above, installed a cfw but still get MIUI to load.
How can i install the CWM over a TWRP and where can i get the CWM for MI 3W?
praty22 said:
Hey ,
I am also Facing the same issue as above, installed a cfw but still get MIUI to load.
How can i install the CWM over a TWRP and where can i get the CWM for MI 3W?
Click to expand...
Click to collapse
http://en.miui.com/thread-58602-1-1.html
Sent from my MI 3W using Tapatalk
Related
I have CWM 4.00.15 installed and I tried to install Ryyu's Rom (Wipe) by putting it on the SD card and rebooting into recovery, then selecting the zip file and hitting apply. When the installation tried to update my kernel, it just froze and rebooted. I was then stuck on a boot loop between the Galaxy S screen and the CyanogenMod boot screen. I know that Ryyu's did not install correctly because the CyanogenMod boot screen was still there. I had to use 3 button recovery and erase cache, davlik cache and user data before trying to install AOSP Essence, but same problem happened. Installation dies and phone keeps rebooting in loops. Finally, gave up and went back to CyanogenMod Nightly and it worked.
Why can't I seem to install any other ROMs besides Cyanogen? I know I am doing something wrong, but not sure what. Any advice/help appreciated. Thanks.
Have you tried starting from a clean install?
Try starting with a stock rom and then to activate Cwm flash a modded Kernel.
Br1g0 said:
Have you tried starting from a clean install?
Try starting with a stock rom and then to activate Cwm flash a modded Kernel.
Click to expand...
Click to collapse
Hi,
this is what I initially did to get Cyanogen on:
1. Used Superoneclick root to root phone
2. Check that 3 button recovery and download mode works. Recovery version was 3e, so installed superlagfix from android market. This automatically installed ClockworkMod Recovery as well.
3. Use CWM and flashed recovery for Samsung Galaxy S i9000
4. Reboot into recovery and select the CyanogenMod zip file and click apply to install.
To install subsequent ROMs, I just put the zip file on my SD card, reboot into recovery and repeat step 4 above, after clearing cache and user data. It is after that I get stuck on boot loops.
I did do a Nandroid backup before my initial Cyanogen install so I can go back and restore it, but it would be Froyo.
when coming from CM / MIUI - Samsung based ROM
you MUST flash a 3 file firmware with pit and re-partition.
Cyanogen and MIUI use different partitions than samsung ROMs so this is why you are having issues.
Ok, just managed to flash Darky's EE 10.2 using Odin. Not sure if Odin is the ideal way, but it worked. Really enjoying Darky's. Thanks folks!
Hey Guys,
I have this problem where i cant seem to flash to any new roms in CWM with the new roms in zip files on my SD card.
I have tried flashing to new kernels but it doesn't seem to change anything.
The last rom i flashed was Criskelo v7 and i haven't changed because i cant every time i try to flash something new in CWM it seems like it only just starts to do it then freezes and i leave it because it might be working and it always end up rebooting and then i find I'm back on Criskelo v7 as if its a fresh install and it need my google account / full setup as if its new but no new rom.
I have also tried updating CWM with odin it works to update odin but it still cant flash any new roms.
Am i doing something wrong? please if anyone has any idea let me know.
Sorry if this has been covered but i really did try and find similar problems.
Thanks
What does the screen read? Error 7?
Sent from my GT-N7000 using xda app-developers app
Flash ANy ROMS
Dr_Rag
if you want to flash any roms using cwm,
1. Flash Safe kernels like Hydracore (http://forum.xda-developers.com/showthread.php?t=1749863) or Philz Kernel (http://forum.xda-developers.com/showthread.php?t=1877270).
2. Reboot in recovery
3. Do all 3 wipes (wipe data, wipe cache partition & wipe dalvik cache)
4. Flash romzip
5. Reboot
If you want to flash XXLS7 TW JB Dump Based Roms , then
1. Flash Safe kernels like Hydracore (http://forum.xda-developers.com/showthread.php?t=1749863) or Philz Kernel (http://forum.xda-developers.com/showthread.php?t=1877270).
2. Reboot in recovery
3. Do all 3 wipes (wipe data, wipe cache partition & wipe dalvik cache)
4. Format /system & /preload in mount and storage
5. Flash romzip
6. Reboot
BTW what rom you are going to install
I had a similar issue and it was a root issue.
To see if it is the same for you, if you have SuperSU, open it, and press 'Continue' if prompted to update binary. If this fails, your problem is root related, the solution of which is below. Unfortunately I don't know how else to test if you don't have SuperSU or if the update prompt doesn't appear.
Below is how I fixed the problem. It may not work for you, and if it doesn't, it's not my fault.
Also note this method will fix the issue no matter what caused it, and wipes data, so backup what you need. It also assumes your ROM is flashable.
1 Put your ROM anywhere in /storage/sdcard0 on your phone.
2 Go to hotfile.com/dl/155490069/c7932d4/N7000XXLPY_N7000OXALPY_DBT.zip.html on your computer to download N7000XXLPY_N7000OXALPY_DBT.
4 Extract this to produce N7000XXLPY_N7000OXALPY_N7000XXLPT_HOME.tar.md5.
5 Flash this through Odin.
6 After your phone reboots (you can't get into the actual OS so you must do this in the Samsung boot animation), enter recovery.
7 Wipe data and cache.
8 Enter download mode.
9 Go to puu.sh/1q5mJ to download GL_NOTECORE_HYDRACORE_v4-3b_STD.tar.
10 Flash this through Odin.
11 After your phone reboots (you don't need to wait to get into the actual OS - you can do it in the Samsung boot animation), enter recovery.
12 Flash your ROM.
Hi there! I want to test the official CM12.1 rom so I decided to format the phone and flash a custom kernel and then the rom.
First I flashed TWRP (2.8.7.0) using fastboot and enter it. I made a complete wipe using the advanced wipe and marking all options (except usb-otg).
Once the partitions are clean I flashed the kernel using the install option and selecting the zip file, finally the same for the CM12.1 rom (nightly). Wiped cache and dalvik and restart, but somehow miui reinstalled.... (it is possible to completely delete miui?). The kernel seems to be the stock (3.4.0-g7f72d41-01413-g70bd50e).
I read in the official CM12.1 post that the rom automatically extends the system partition (merging the two system partitions to have a partition with 1.28GB), is this true or do I have to do it manually (flashing something?).
Thanks.
Flash this once and your partition will be 1.2 GB.
Thanks! Is it normal that it still shows just 629MB? (I can see it in the repair/resize/change-file-system section).
Now, every rom that I flash it stucks at the "mi boot logo"... Maybe I'm doing something wrong; I wipe/factory reset (including cache/dalvik) and then flash the zip, and (wipe again, the option at the left to reboot) and reboot to system.... It's stuck, I tried with other custom roms and it happens the same. What am I doing wrong??
Did you switched the partition (system 1 for non - miui and system 2 for miui)? It's located in advanced options in cwm.
pratyush997 said:
Did you switched the partition (system 1 for non - miui and system 2 for miui)? It's located in advanced options in cwm.
Click to expand...
Click to collapse
I'm using TWRP. So I have to flash CWM to extend the partition?
ChazyTheBest said:
I'm using TWRP. So I have to flash CWM to extend the partition?
Click to expand...
Click to collapse
I do not use TWRP, can't help you.
ChazyTheBest said:
I'm using TWRP. So I have to flash CWM to extend the partition?
Click to expand...
Click to collapse
Yes, the repartition zip only works on CWM. People said that they have problem while repartitioning with TWRP.
zzvilzz said:
Yes, the repartition zip only works on CWM. People said that they have problem while repartitioning with TWRP.
Click to expand...
Click to collapse
did you solve your problem?...im having that same problem of you :crying:
Hi there,
my plan was to install CM 12.1 with the help of this site:
http://forum.xda-developers.com/galaxy-s3/development-i9305/rom-t3066156
At first, I used Odin to get TWRP on my phone. With TWRP I did a complete backup (EFS, Boot, Cach, System, Data).
Actually, I thought I have done everything like it is instructed on this page.
->
"First time installing CyanogenMod 12.1 to your Galaxy S3 I9305, or coming from another ROM:
- Read known issues ans FAQs
- Flash one of the recovery images (CWM or TWRP)
- Copy GApps and CM12.1 ZIPs to your SDCard
- Boot into Recovery
- Flash CM12.1 zip from SDCard
- Flash GApps zip from SDCard
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
- Reboot
- Don't restore system data using Titanium Backup!
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!"
<-
After installing GApps, I wiped all data on the internal storage, did a factory reset and rebooted.
Unfortunately, I have been stucking at boot. There has been only the CM symbol on the display.
With TWRP I restored my backup. After that, my phone has been booting normally, but it could not find any mobile service.
According to the settings, my phone didn't recognise my sim card anymore.
(After using Odin, I did a reboot and noticed already that my phone hasn't got any mobile service anymore. Can this be?)
Moreover, I discovered that I my phone has got difficulties to copy things from the computer to the SD-card or to the internal storage.
Even copying things from the SD-card to the internal storage, or the other way round, using a file manager app like "Astro" is not working.
I tried to do a factory reset, but then again, the phone stucks at boot. On the display just appears "SAMSUNG".
Can you guys please help me to get back to a working phone?
With best regards,
New.Android.User
which version of TWRP did you flash?
I used twrp-2.8.7.0-i9305.img.tar
although pm'ed you the solution I'll post a big warning again:
DO NOT USE TWRP 2.8.7.0 from twrp.me. This build is faulty and causes a soft brick. To fix that you need to flash stock rom again and stay on TWRP 2.8.5.0 or any other recent recovery of Philz Touch or CWM.
alright! Thank you so much!
So, I will continue like that:
1. With the help of Odin i will install a new bootloader. I recommended twrp-2.8.5.0-i9305.tar
2. Then again with Odin, I will install the stock rom using -> sammobile.com/firmwares/download/45775/I9305XXUFOB2_I9305DTMFOB2_DTM/
3. Then I will go to the TWRP-recovery and install CM12.1 with GApps.
Is this the right order?
first stock, then custom recovery and then you can flash rom and gapps
Comming from stock ROM every new ROM I'm trying to flash just hangs on a boot logo (animation) of CM for example. Phone was wiped fully several times using TWRP and Cyanogenmod Recovery (/system, /data, /cache, /dalvik-cache).
Any help, please?
what version of twrp are you using? i've had the same issue with twrp 2.8.7.0. It seems to be buggy.
Try another version. 2.8.5.0 works fine for me.
// you might need to / want to / have to restore your phone to stock rom AND recovery first.
Agree with the possibility of TWRP problem.There is a version 3 out now which might work but 2.8.5 is definitely OK. Philz recovery should also work.Make sure these are the correct versions for phone.HTH.
Flash recovery via Odin. Firstly make sure you are using recovery made for our phone. To be honest, I prefer TWRP, and I am using 2.8.5 as I remember. Also, which roms you tried ? I had CM 12.1 and CM 13, and they worked totally fine, but I just loved more stock 4.4.4 so I downgraded.