Roms wont boot. - Xiaomi Mi Mix 2 Questions & Answers

I just got a Mi Mix 2 today, and have it fully unlocked. The stock rom runs fine, but when I install the latest TWRP and then flash any rom, I get constant crashes. Launchers, google apps, everything. Following instructions from each thread specifically and have been rom flashing for years, so it's something specific to this phone. On the recommended firmware, and stock rom runs great. Suggestions?
EDIT: It may have been a dongle/cable issue. I have switched cables, and gotten the rom to match MD5 FINALLY and it seemed to boot one. Just wanted to put this here for anyone else that was having similar issues.

Have you signout on your Mi account?

Related

[Q] AOSP keyboard failed to launch?

So I've decided to start playing around with custom ROMs. I'm still pretty new to Android so maybe this is going to be stupidly simple.
Earlier today I flashed PACman Rom. Downloaded directly from the thread. I wasn't super happy with how slow it ran and a friend suggested it might be a nightly. I noticed in settings it said the release was from 09/09 so I thought he might be right. I decided to wipe it and install the most recent stable version of PAC man.
Seemed to flash just fine, but the startup was a bit odd. It didn't go through the standard stuff like syncing your google account, setting up wifi, etc. Jumped right to the home screen. At first that didn't seem like an issue. I can do that all manually. But then it flashed on screen saying AOSP keyboard couldn't launch. Obviously without being able to type at all or even open the keyboard, I can't do a whole lot to get it set up.
Tried a couple times to flash that ROM and same thing every time. Restored from my nandroid and everything worked perfectly. Decided to try CyanogenMod and got 10.2 stable release with gapps. Wiped and flashed. Same thing. Straight to the home screen, no keyboard. Every other gapp is there.
Any ideas on what I can do differently? Or what I might be doing wrong, or some way I can get this to work?
Did you flash gapps with pacman ROM?
Sent from my Galaxy Nexus
Yes I did. And I actually just figured out what it was. I was using 4.3 gapps with 4.2.2 ROMS

[Q] Stock ROM over Stock flashing issue

Good day,
I'm wondering if anyone has gone through this; it goes like this, last night I flashed my n7100 Note 2 with a stock rom 4.1.2 XEF (France)(the same exact rom I used to flash my phone with for 10ths of times) nothing went wrong as Odin completed the processes successfully (apparently) rebooting the phone to finalize the installation, however it booted into the previously installed system, including all of the apps I installed earlier, in other words nothing's changed at all, I hope I'm making sense, I tried two different computers ending with the same result, how come it worked like charm before and now it does not? Thanks again for any advice.

Custom roms and freezing help

hello my wife has a tmobile galaxy s4, as do i, but her wifi stopped working one day, i tried everything to fix it and nothing worked, so i rooted the phone and and flashed twpr, and tried some custom roms, but they all end up freezing on the lock screen or out of nowhere and ive tried various roms, all stable as they say on the post, but they freeze on me, im on the nh7 baseband and bootloader i used a phone info app to check. what could be causing this with every rom i tried? ive tried the pac-man rom, slimkat, google play edition, dan&ktoonz rom. ive rooted and used roms on my old galaxy s3 no problem.
Try flashing a stock rom, just for giggles & grins. See if that works before you go off the deep end.
Pp.
Where can i get the stock roms
http://galaxys4root.com/galaxy-s4-stock-firmware/ Choose your stock Rom here
now are these flashable via twpr.
Tell me if they helped in anyway
Try working with this as the Web site mentioned before by Pablo has the not so latest firmware, and this is trustworthy from our own forum, just follow the instructions, read through the thread for answers in case you have any questions.
http://forum.xda-developers.com/showthread.php?p=55374113
Pp.

[Q] Help! What have I done to my Pro 10.1

Here's the story. I purchased a factory refurb'd Tab Pro 10.1 (SM-T520NZKAXAR) on Woot a few weeks back. I live in Canada, but it is a USA tablet, if that matters. It came with a 90-day Samsung warranty. As soon as I got it, I started looking at custom ROMs. I have experience with custom ROMs on my HTC One m8 (and old m7), but not with any Samsung devices. I wish I had kept it stock for a few weeks first to check it out, but here we are.
I created a nandroid backup of the stock firmware, however I quickly deleted it during a wipe when flashing my first custom ROM, which was GraveD's v3.0. It seemed to go OK, but then it would start to freeze up and reboot on it's own. This seemed to happen mostly under load, and especially when trying to install apps from the Play store. I tried going back to the stock kernel, thinking that could be the problem. It stopped the crashing, but then wifi wouldn't work. So I could choose between having a tablet that crashes all the time, and has difficulty installing apps, or one without wifi. Both were basically useless.
I tried installing another custom ROM, GigaWatts Pro. Again, flashing seemed to go well, and the ROM also seemed to work very nicely for a couple of days. No random reboots, and wifi worked great. I spent a few days downloading all of my apps and getting things set up the way I like, when yesterday something went wrong. Perhaps the tablet lost its root (is that possible?). All of a sudden, apps are crashing all over the place (Unfortunately, [insert app name] has stopped). Titanium backup hangs at "Asking for root...". Installing apps is also difficult again. The tab doesn't reboot on it's own, but Play Services crashes constantly. Whenever I try to get into developer options, the Settings app crashes. I'm not even 100% sure USB debugging is enabled right now, although I'm still able to flash using ODIN.
I tried doing a factory reset and re-installing GigaWatts. Same problems. Tried making sure the root was OK. Same problems. I've tried using twrp 2.8.0.0 as well as 2.7.1.0 with no luck.
Right now, I've downloaded the stock firmware for Canada T520UEUANI1 4.4.2 (although the tab was bought from a USA site). I assume this also installs it's own Kernel. It shows Kernel version:
3.4.39-2776001
[email protected] #1
Mon Sep 15 17:44:40 KST 2014
I'm experiencing the same problems. Google Play Newsstand crashes every 10 minutes or so. Settings is almost useless. Installing apps is problematic.
Can anybody tell me if there's something I'm missing? Anything left to try? Does it sound like a hardware/ROM/kernel problem? If it's hardware, can I still utilize the Samsung warranty after trying to flash custom ROMs? I'm going to try to download another Cellular South stock ROM, but it seems like the problems are persisting regardless of which ROM i have installed, so I think it's something else (kernel or hardware-related).
Any help is GREATLY appreciated. My new tablet is basically useless, and I've run out of ideas.
Try this latest firmware since you mentioned your tablet is the XAR model the firmware should be cellular south (wifi)
http://www.sammobile.com/firmwares/download/39630/T520UEUANK1_T520XARANK1_XAR.zip/
If that doesn't help then it could just be a bad tablet .
(btw when you flashed a custom rom you probably tripped the hardware knox flag and voided any warranty it had, I guess you could play dumb if they ask and say it came like that since it was refurbished, and hope they still repair/replace it)
I just tried the USA cellular south firmware. Still experiencing the exact same issues. I'm completely out of ideas. Does anyone else have any ideas? Otherwise I'm going to have to try warranty service and hope for the best. Is there anything I can do to restore the Knox flag before I send it in?
Also, in download mode the tab is recognizing the system as custom. Is this normal after flashing a stock image?
So do a factory reset in recovery, and clear the cache also. Then load the cellular South file thru Odin. Then factory reset again. See if this clears your problems.
k8108 said:
So do a factory reset in recovery, and clear the cache also. Then load the cellular South file thru Odin. Then factory reset again. See if this clears your problems.
Click to expand...
Click to collapse
I've tried the Cellular South firmware to no avail. I'll be trying to warranty the tablet now. Fingers crossed!

Experimenting with ROMs

I'm looking for an S7E/N5 hybrid with mostly everything working. Coming from a N3, this would be a Dark Lord ROM with fingerprint and NFC.
I started with a stock BPA1 phone which I unlocked/rooted. I wanted to upgrade to a true 6.0.1 ROM which meant upgrading firmware. I started with Odin flashing a tar.md5 of the CPD1 firmware - bad idea. It failed and messed up the bootloader. So broke phone.
I was able to Odin the stock BPA1_BPA1 and the BPA1_CPD1 firmwares. In each case though, it was very hard to obtain root. If it rebooted or locked up for any reason, I had to go back and reflash the stock firmware, wipe and reinstall kingoroot. Otherwise I was stuck in a bootloop with DL Mode saying I was locked. This is what lead me to fix it. I noticed after the first flash of samsung_unlock_n4-fix (root took that time and no crashes) it would bootloop. I went into DL Mode to reflash firmware but it finally showed Developer Mode. I gave it a shot and flashed twrp without issue. Instead of having to install the n4-fix twice or go through multiple roots, turns out that it took just took once to reclaim Dev Mode.
(I had been thinking that Dev Mode was wiped out with aboot when flashing the stock BPA1. Guess not)
So the bootloop I figured was due to a kernel issue. With Dev Mode, I Odin flashed TWRP. I formatted my sdcard and put a kernel on it, using twrp to flash it. And tada, working phone. This worked on both the BPA1_BPA1 and the BPA1_CPD1. So I was able to load the 6.0.1 firmware. It took so long to do this though that I didn't get a chance to try more than a few roms.
From a brief visit to these ROMs, I am still looking for something that has everything:
From T-Mobile:
Maximum OvrDrive 6.0.1 MM v.8 - Great ROM but I didn't have wifi afterloading it. I'm sure I was missing something to get it to work but I realized this was not an S7E port either.
Maximum OvrDrive S7 v3.7 - It's a 5.1.1. ROM and works well but is missing AOD, fingerprint and most importantly hotspot.
General forum:
Dr.Ketan 6.1.1 - could not get this to load. It bootlooped after flashing the M5 rom (910g?), kernel, datafix and supersu as per instructon. Will revisit.
Verizon forum:
Kyubi Note 5 Port - One of the first ROM I tried and it is amazing. This is a very stable ROM with almost all the bells and whistles. I wouldn't even look at another ROM except it doesn't offer AOD and a few minor tweaks (haven't figured out how to skin my status bar clock for example). I posted in the thread a fix for MMS btw. It's a 5.1.1 ROM of course and lacks in a few ways.
I'm still looking for a perfect ROM for me. Will update the list as I try them.
I flashed the Noble ROM yesterday. So far, so good.
If you get time this rom by @aukhan and the Emotriod team is great. It's a pure note 4 with edge features, but I can't remember if mobile hotspot works or not. I'm using the Nameless Rom at the moment and really enjoying it as well. On the Nameless Rom mobile hot spot works, I'll check to see if fingerprint works, everything else as far know works well. One more option is Kurama Rom, I got it to boot with data/mobile/wifi, but to be honest I didn't stick with it too long because as soon as I got it set up, the Emotriod Rom caught my eye and I just had to have it.
douger1957 said:
I flashed the Noble ROM yesterday. So far, so good.
Click to expand...
Click to collapse
Hahaha....I've been on Noble for a few weeks now, and just flashed hsbadrs cm13 7.17. release for a change. Noble is a beautiful rom, and I themed it with Marshmallow dark theme from the Samsung theme store. CM13 is just slightly more fluid, and used to be my favorite, Noble is by far the most stable s7 port on my phone.
Sent from my SM-N910V using XDA-Developers mobile app
Dr Ketan rom you need to flash rom then m5 fix right away let it boot (can take up to 11 minutes no longer average 5-6) dont sign into anything ( google, samsung, etc.) then go back into recovery and flash louforgiveno's data fix for your bootloader and ketan rom. then reboot. It has to be a clean flash in my experience. It will take about 5 minutes to get data signal but it comes. The roaming indicator off text stays on lock screen it does not mean you are roaming though (check in about device), there is a way to get rid of it but i didn't doesnt bother me.
Does anyone know if there is a way to add Wifi calling to any of the N910F roms?
UPDATE: I went back to Ketans Rom but on the BPA1 bl and it works very nicely. I had to utilize my MMS fix to get the native app to send mms. I'm currently working on finding an Xposed framework that boots. Neither Wanam mod's or the stock seem to fit. Ketens is so far the most kitted out N5/S7E rom I've seen, with even a cobbled together version of AOD. Anyone have any luck with Xposed running the H Vitamin kernel? I'm thinking of switching to some other kernel to see how it works.
kevintm78 said:
If you get time this rom by @aukhan and the Emotriod team is great. It's a pure note 4 with edge features, but I can't remember if mobile hotspot works or not. I'm using the Nameless Rom at the moment and really enjoying it as well. On the Nameless Rom mobile hot spot works, I'll check to see if fingerprint works, everything else as far know works well. One more option is Kurama Rom, I got it to boot with data/mobile/wifi, but to be honest I didn't stick with it too long because as soon as I got it set up, the Emotriod Rom caught my eye and I just had to have it.
Click to expand...
Click to collapse
Just curious what kernel and data fix are you using with the emotroid rom. I have tried Lous MMs fix v4 and also the 3b version but MMS is all not working properly.
Is there anything wrong with the mm bootloader? Seems like a lot of ppl Including me is having trouble flashing roms on it. So we Convert back to the lollipop bootloader... How can we get roms to work on the mm bootloader. I can't find any reason to this.

Categories

Resources