Yesterday unlocked via HTC dev. The through fast boot flashed twrp. That didn't work so well I couldn't actually flash any ROMs I could make a backup and I could restore. OK so I flashed cwm through Fast boot success however I flashed 2 ROMs one experia all seemed to work but WiFi was of no use I don't pay for service so that was obviously a no go. I flashed the ROM 3 times even re downloading it again. Ok so on to aokp flashed via cwm flashed jb gapps flashed boot.IMG via fast boot. Would boot up to start up then FC and reboot and boot loop at the aokp screen. Repeated numerous times getting various results.
Now I relocked boot loader and ran the ruu.exe and had to leave in the process it looked like it was booting hopefully when I come home it will be back to stock. Far from a dev so I am confused. I just want to try out some roms? Could this but a kernel issue? Recovery or something else?
Sent from my SGH-T999 using xda premium
md1008 said:
Yesterday unlocked via HTC dev. The through fast boot flashed twrp. That didn't work so well I couldn't actually flash any ROMs I could make a backup and I could restore. OK so I flashed cwm through Fast boot success however I flashed 2 ROMs one experia all seemed to work but WiFi was of no use I don't pay for service so that was obviously a no go. I flashed the ROM 3 times even re downloading it again. Ok so on to aokp flashed via cwm flashed jb gapps flashed boot.IMG via fast boot. Would boot up to start up then FC and reboot and boot loop at the aokp screen. Repeated numerous times getting various results.
Now I relocked boot loader and ran the ruu.exe and had to leave in the process it looked like it was booting hopefully when I come home it will be back to stock. Far from a dev so I am confused. I just want to try out some roms? Could this but a kernel issue? Recovery or something else?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
first more info will get u more accurate advice ie.... build date of aokp.... last nightly is messed up use stable for best results. also the method of which u applyed these roms would be nice htc s-on is a pain so it requires a little diffrent prosses thin on other phones and diffrent strokes for diffrent roms
for wifi u have to reflash boot.img....
for FC and bootloops factory reset, wipe cache partition, wipe dalvik cache....
download latest nightly and follow this------>
1. download rom and gapps,transfer them to root of SD card
2. extract boot.img(the kernel) from ROM zip,or whichever is compatible and place it in fastboot folder
3. go into bootloader, FIRST flash the boot.img in fastboot.
4. go into recovery, then FULL WIPE-factory reset, erase cache and dalvik cache.
5. then flash the ROM.
6. boot into the rom.then again enter into recovery and then flash gapps.
do the above steps in the same order all over again....it should work...:fingers-crossed:
If I am not mistaking I used the latest stable build of aokp, and I flashed both roms through recovery using both CWM and TWRP and also flashed kernel using fastboot. Although I reflashed TWRP and flashed AOKP and all seems to be right in the world. right now in at the set up screen so far no freeze or boot loop and wifi is working. Consider this problem solved
And yeah S-on sucks!
Hi,
I am on CM 10.2 nightly. Everytime I try to install an different ROM on CWM 6.0.27, eg. Android Revolution 22.0, the installation procedure goes fine. During Aroma installer I choose to wipe user data partition and so on. Then after reboot my phone stucks on "samsung galaxy note gt-n7100" screen. Afterwards I have to go back into recovery and have to recover my rom so the phone will boot again. Really strange. Any suggestions why my phone is behaving this way?
Regards, heinzelrumpel
heinzelrumpel said:
Hi,
I am on CM 10.2 nightly. Everytime I try to install an different ROM on CWM 6.0.27, eg. Android Revolution 22.0, the installation procedure goes fine. During Aroma installaer I choose to wipe user data partition and so on. Then after reboot my phone stucks on "samsung galaxy note gt-n7100" screen. Afterwards I have to go back into recovrey and have to recover my rom so the phone will boot again. Really strange. Any suggestions why my phone is beahving this way?
Regards, heinzelrumpel
Click to expand...
Click to collapse
Change the recovery, often Philz 5.15 works best with Aroma installer.
Androidwizzard said:
Change the recovery, often Philz 5.15 works best with Aroma installer.
Click to expand...
Click to collapse
Unfortunately this does not do the trick Still stuck after reboot.
I can't tell you why its happening, but what I've done in the past to get around the issue is to flash a stock rom with Odin, then flash a new recovery before going to another custom rom. If you worry about the Knox warranty bit being set you'll have to find an old 4.1 image somewhere to flash. Since I'm past warranty I don't care anymore.
Good luck!
Wipe data cache dalvik format system etc nstall the new rom reboot and after go again to recovery and factory reset it.
Sent from my GT-N7100 using Tapatalk
I have been trying everything to successfully install CM 11.0 Kit Kat 4.4 on my Captivate Glide, to no avail.
I have followed these instructions numerous times:
http://forum.xda-developers.com/showthread.php?p=49743700
I have even used Superuser 3.2 RC2 arm signed and the RC3 versions for root.
Everytime I get my device rooted (which I have checked after the fact), I reboot into TWPR, factory reset and wipe the dalvik cache and then try to install the ROM. Everytime I try it has failed and I have to reflash a stock rom.
What in the sam hell am I doing wrong?
taydayrey said:
I have been trying everything to successfully install CM 11.0 Kit Kat 4.4 on my Captivate Glide, to no avail.
I have followed these instructions numerous times:
http://forum.xda-developers.com/showthread.php?p=49743700
I have even used Superuser 3.2 RC2 arm signed and the RC3 versions for root.
Everytime I get my device rooted (which I have checked after the fact), I reboot into TWPR, factory reset and wipe the dalvik cache and then try to install the ROM. Everytime I try it has failed and I have to reflash a stock rom.
What in the sam hell am I doing wrong?
Click to expand...
Click to collapse
are you on 4.0.4?
What version of TWRP are you using (you need to use Bubor's latest TWRP, Fetch it here)
taydayrey said:
I have been trying everything to successfully install CM 11.0 Kit Kat 4.4 on my Captivate Glide, to no avail.
I have followed these instructions numerous times:
http://forum.xda-developers.com/showthread.php?p=49743700
I have even used Superuser 3.2 RC2 arm signed and the RC3 versions for root.
Everytime I get my device rooted (which I have checked after the fact), I reboot into TWPR, factory reset and wipe the dalvik cache and then try to install the ROM. Everytime I try it has failed and I have to reflash a stock rom.
What in the sam hell am I doing wrong?
Click to expand...
Click to collapse
what he said, use the latest TWRP.
Yes, I am running 4.0.4
And I have only been able to use TWRP 2.6.3 (2.6.3.1)...using odin to flash it.
I wanted to use 2.6.3.4 but it was just a zipped recovery image. I thought you couldn't use a zip when installing a recovery? I just wasn't clear on which would actually work.
taydayrey said:
Yes, I am running 4.0.4
And I have only been able to use TWRP 2.6.3 (2.6.3.1)...using odin to flash it.
I wanted to use 2.6.3.4 but it was just a zipped recovery image. I thought you couldn't use a zip when installing a recovery? I just wasn't clear on which would actually work.
Click to expand...
Click to collapse
there is NO 2.6.3.4.
Actually you need 2.7, but version string is 2.6.3.
Recovery without selinux would fail, I dont know other reason to fail. Try to install 2.6.3.1.zip from recovery, reboot to recovery, and install cm again.
stormdude124 said:
are you on 4.0.4?
What version of TWRP are you using (you need to use Bubor's latest TWRP, Fetch it here)
Click to expand...
Click to collapse
2.6.3.4 at http://dualhoki.vim.hu/bubor/dev/twrp-i927/twrp-2.6.3-4.zip
Check for latest by browsing http://dualhoki.vim.hu/bubor/dev/twrp-i927/
---------- Post added at 11:56 AM ---------- Previous post was at 11:50 AM ----------
xqme said:
2.6.3.4 at http://dualhoki.vim.hu/bubor/dev/twrp-i927/twrp-2.6.3-4.zip
Check for latest by browsing http://dualhoki.vim.hu/bubor/dev/twrp-i927/
Click to expand...
Click to collapse
2.6.3-4 not 2.6.3.4 sorry
I recently flashed TWRP on my ZE551ML Marshmallow and tried to flash a ROM. But after I reboot, the device goes into recovery no matter what I do. I tried 3 different ROMS but none work. I also to flash other recoveries like CWM but they don't work either, only the first TWRP seems to load.
Steps followed:
1. Wipe Data
2. Flash ROM
3. Wipe Cache
4. Install gapps
5. Reboot.
Please help. Thanks in advance.
shubham21197 said:
I recently flashed TWRP on my ZE551ML Marshmallow and tried to flash a ROM. But after I reboot, the device goes into recovery no matter what I do. I tried 3 different ROMS but none work. I also to flash other recoveries like CWM but they don't work either, only the first TWRP seems to load.
Steps followed:
1. Wipe Data
2. Flash ROM
3. Wipe Cache
4. Install gapps
5. Reboot.
Please help. Thanks in advance.
Click to expand...
Click to collapse
check this here
http://forum.xda-developers.com/zenfone2/help/stuck-recovery-flashing-rom-boot-t3499441
Where it says > `restore old mm blob back up`, you install CM14.1 and pico gapps
timbernot said:
check this here
http://forum.xda-developers.com/zenfone2/help/stuck-recovery-flashing-rom-boot-t3499441
Click to expand...
Click to collapse
See the thing is nothing works. No matter what I flash, it keeps booting into the bootloader or recovery
Yes it will use the modder tool by giovix you unlocked bootloader ? if not , do it in modder too then follow those steps in link
I have now tried to install the latest RR and Omnirom builds and the problem remains the same.
I've been very particular about wiping data before the installs.
Here is what I have done,
Performed data wipe by typing "yes" when requested. Used advance wipe to wipe everything.
Installed Rom, Stock Gapps and Magisk zip files.
Wiped Cache.
Reboot
The phone will not boot and only returns to recovery.
Can anyone help?
Here is my TWRP log if this helps - https://pastebin.com/ghpXkt3t
Not sure if this is relevant, but every time I try to flash a ROM it always fails on the first attempts and needs a second try to succeed.
TylerDurdenK said:
I have now tried to install the latest RR and Omnirom builds and the problem remains the same.
I've been very particular about wiping data before the installs.
Here is what I have done,
Performed data wipe by typing "yes" when requested. Used advance wipe to wipe everything.
Installed Rom, Stock Gapps and Magisk zip files.
Wiped Cache.
Reboot
The phone will not boot and only returns to recovery.
Can anyone help?
Click to expand...
Click to collapse
If you only get to the mi logo and not the ROM boot screen then format data "yes 3-4 times in a row.
If that doesn't work then wipe the system and data and retry
I was only getting the Mi logo, so I did the format data 4 times in a row and rebooted.
I then saw the Omnirom logo for the first time!
unfortunately 2 seconds later I'm back in TWRP.
I have now tried for the 5th time to perform a fresh install.
Formatting data multiple times, wiping system and data multiple times.
The result is the same.
I see a flicker of the Omnirom logo and I get booted back into recovery.
TylerDurdenK said:
I see a flicker of the Omnirom logo and I get booted back into recovery.
Click to expand...
Click to collapse
Please try this:
1. Wipe: Dalvik / Art Cache; System; Data; Cache;
2. Go back to main TWRP screen and install the rom, install Google Apps, install "addonsu-15.1-arm64-signed.zip" (in case of Lineage) or the latest Magisk (in case of other rom)
3. Wipe Cache
4. Reboot
If this doesn't work and the device restarts in twrp, then pls download the twrp flashable Xiaomi rom from here: http://en.miui.com/download-334.html
1. Wipe: Dalvik / Art Cache; System; Data; Cache
2. Go back to main twrp screen and install the Xiaomi rom. Do not reboot.
3. Go back to main twrp screen and Wipe: Dalvik / Art Cache; System; Data; Cache
4. Go back to main twrp screen and install the rom (Lineage or OMNI or RR), install Google Apps, install "addonsu-15.1-arm64-signed.zip" (in case of Lineage) or the latest Magisk (in case of other rom)
5. Wipe Cache
6. Reboot
I had the same problem and this method worked for me, maybe it will work for you too. :fingers-crossed:
If it doesn't then maybe you have to start from zero and flash the original Xiaomi rom in fastboot mode (rom here: http://en.miui.com/a-234.html) via MIUI ROM Flashing Tool, unlock bootloader (bootloader might relock), flash twrp and then flash new custom rom.
No idea what happened but I have the same issue atm.
I was running a recent Omnirom for a few weeks. System got unstable, so decided to flash the newest version. Got me stuck in a bootloop. I tried everything, short of relocking and unlocking the bootloader.
- Full wipe, including storage
- Reflash Global Dev through TWRP.
- Flash stock Global Dev over flashboot
- Flash Omni, wipe, flash omni again.
All the same. Global Dev runs, all AOSP roms just go into bootloop. No idea what went wrong, I've flashed tens of custom roms over the past months without issues.
Firipu said:
No idea what happened but I have the same issue
All the same. Global Dev runs, all AOSP roms just go into bootloop. No idea what went wrong, I've flashed tens of custom roms over the past months without issues.
Click to expand...
Click to collapse
Then maybe the right solution to get out of bootloops would be to start from zero and flash the original Xiaomi rom in fastboot mode (rom here: http://en.miui.com/a-234.html) via MIUI ROM Flashing Tool, unlock bootloader (as bootloader will relock), flash twrp, do a full wipe and then flash new custom rom.
senerex said:
Then maybe the right solution to get out of bootloops would be to start from zero and flash the original Xiaomi rom in fastboot mode (rom here: http://en.miui.com/a-234.html) via MIUI ROM Flashing Tool, unlock bootloader (as bootloader will relock), flash twrp, do a full wipe and then flash new custom rom.
Click to expand...
Click to collapse
I have reflashed the original Xiaomi ROM (running it atm ) using the official Xiaomi Flash Tool.
I just did not relock my bootloader doing that (there's an option to leave it unlocked). Will relocking and then unlocking the bootloader really make a difference?
Firipu said:
I have reflashed the original Xiaomi ROM (running it atm ) using the official Xiaomi Flash Tool.
I just did not relock my bootloader doing that (there's an option to leave it unlocked). Will relocking and then unlocking the bootloader really make a difference?
Click to expand...
Click to collapse
Not really. You ev. save yourself a waiting time of 72h....
Not sure what happened. I set up MIUI completely. Then, getting frustrated after using it for 10 minutes, decided to try one more time. Same thing.
1) Fastboot flash TWRP.
2) Wipe
3) Flash Rom
4) Flash GAPPS
Worked this time. No idea what went wrong the first 4 times. Only difference is that I went through the trouble to set up the entire phone this last time before trying again.
Anyhoo, so if anyone has the same issue. Set up phone in MIUI, only then wipe/flash
I got mine working by not installing Magisk. I just flashed Omnirom and GApps and it worked.
After setting up my phone I have since rebooted into recovery and installed Magisk and it works.
Can't system boot after install TWRP, Lazy Magisk on MIX M2S
Hello,
I have this problem, the phone does not boot after TWRP, Lazyflasher and Magisk being installed all fine.
I have re-installed the official ROM on my Xiaomi MI MIX 2S, then TWRP is fine too, then Lazy and Magisk fine.
When I reboot, it is stocked on MI logo whatever I do.
I have tried most of the advise posted but still stocked.
I restarted from scratch, installing again the official ROM, then fastboot flash recovery twrp, then lazy and Magisk, but still stocked on MI.
Thanks a lot in advance
Did you wipe system by any chance.. If you did you need to flash miui again with fastboot.. Or boot into fastboot and type this command 'fastboot format userdata' and press enter. You are facing this issue because of encryption
goxthak0 said:
Did you wipe system by any chance.. If you did you need to flash miui again with fastboot.. Or boot into fastboot and type this command 'fastboot format userdata' and press enter. You are facing this issue because of encryption
Click to expand...
Click to collapse
Gratitude for your reply. What do you mean by "wipe system". I installed the rom and then TWRP etc...
I flashed the ROM again and went into bootloader
I typed "fastboot format userdata" and the system replied:
"/usr/local/bin/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
Can you advise.
Thanks a LOT
Did you use the correct rom ? Mi mix 2 or mi mix 2s?
fotocreaman said:
Did you use the correct rom ? Mi mix 2 or mi mix 2s?
Click to expand...
Click to collapse
I used MI MIX 2D:
As in en.miui web site
https://en.miui.com/download-343.html
Author: MIUI Official TeamVersion: V10.0.9.0.PDGMIFH (MIUI10) Size: 1.7G
My mobile is:
MI MIX 2S, Android 9PKQ1
MIUI Global 10.0
Thanks a lot for your advise as always stock, despite different attempts
Did you try to flash using mi tools?
fotocreaman said:
Did you try to flash using mi tools?
Click to expand...
Click to collapse
NO, I followed the usual process with ADB tools.
However, I have no boot "stuck at MI logo (bootloop)" problem when I flash the ROM.
It happens only when use TWRP and flash Magisk and Lazy.
Then, when I restart it got stuck at MI Logo.
Do you suggest I try to flash with MI logo (I don't have a PC though).
If so, should I just flash the ROM and then, what about TWRP, should I use MI flash or ADB?
I just want to make sure that the problem is with the ROM instal?
Thanks a LOT