I upgraded to 6.0 a day or two ago and had quite a few booting problems trying to get it going, something I have not had upgrading on a Nexus ever before. Anyway, after reinstalling TWRP just to make sure, re-downloading a couple ROMs and kernels again to my phone (even though MD5 checked out) and reinstalling everything about 3 times I finally got the phone to boot. So at least my phone works again, but my problem I am wondering about now is that my phone will not boot and gets stuck on the ROM splash screen every time I turn the phone on. IN order to fix it I have to go into recovery and wipe dalvik and cache to get the phone to boot. Is this normal behavior for Android 6.0 right now? I dont feel like it is... Does anyone know what could be wrong?
Did you wipe data or did a factory reset? Unless it's a minor change, you always need to wipe data too. In TWRP factory reset does that without deleting your photos and such, but always do a full backup nevertheless.
Another question, did you upgrade the bootloader and the radio from the official factory image? (MRA68K or MRA58N)
Yep I did a 100% wipe like I always do when installing any new ROM.
Bootloader is on the M preview version 2. Didnt see any download links for a newer bootloader version. Radio is the M radio as well. MRA68K I believe.
I went and downloaded the official OTA and extracted the bootloader and radio from that. I think they are the same versions, at least for the bootloader. I will install them when I get home tonight anyway and see if it fixes the issue.
Related
Okay...so I had the Cyan ROM and I went into Recovery and wiped everything. Does that mean that I don't have a ROM installed? Or is it just like a factory reset...but instead it resets it back to the original Cyan ROM?
I did do a full wipe and then flashed what I thought was a ROM but I guess it turned out to just be an add-on.
So, I guess my other question is...when I flash an addon/theme to a ROM...it becomes a part of that rom...even after a complete wipe?
Factory reset/wipe wipes everything. You don't have a ROM to boot up with anymore.
Add-ons go on top of ROMs. Add-ons alone = nothing to boot with, either.
You can still boot after doing a factory reset, to my knowlege it just wipes all your settings and internal data.
It does? Admittedly I haven't tried that for a while, but the last time I wiped in recovery and rebooted, it didn't really boot up.
I understand the factory reset under Settings -> Privacy is different, though.
When I woke up this morning...I tried the wipes under Recovery just for the heck of it...and it booted up. Now I'm just what exactly is on the ROM? All the addons and themes? It looks that way.
I guess since the only real danger of Bricking the phone would be to interrupt the flashing of the radio...so I guess I'll go into trial and error mode for the next couple of days.
Yeah, during my "let's try everything and flash different ROMs twice a day" phase, I kept expecting the phone to die and never wake again. Looks like the only real ways to brick it are flashing radio and SPL.
Okay...so if you use the Factory Reset under settings...it seems to do nothing but reboot the phone.
If you wipe through Recovery...it just resets your settings and apps. All addons are still intact. So I'm assuming that when you flash an Addon...it becomes fused with the main ROM?
I don't understand why the ringtones that I pushed to the system/media folder are still there after a wipe and reflash of the same rom? Shouldn't reflashing overwrite everything?
I downloaded and installed Rodriguezstyle MiUi rom yesterday, following all the install procedures(the double wipes and what not). But when I go to use it, it sometimes worked and it sometimes would crash and reboot. It was very weird because instead of just rebooting to the os, it would give the Nexus X then, after going no further, reboot again giving the Nexus X and reboot again and so on. This happened with every MiUi rom I installed, but not with the Evil Desire rom I have now. I really like MiUi, do you guys have any fix?
Specs - Nexus One w/ 5.12 Korean Radio
Trying Rods 1.6.6
Have you overclocked it with setcpu? You might want to turn that off and see what happens. I assume you did a complete wipe first btw?
I did wipe and my rom crashes before I can install setcpu
MIUI 0.11.5 + English Pack
I am using MIUI 0.11.5 Deodexed + English Pack. No issues so far. Its perfect.
Why are you making multiple useless threads about this?
@ inferus
could you post the site you got it from. And I have also tired the bundle, which did not work either
MIUI stock
Here you go
http://forum.xda-developers.com/showthread.php?t=789566
I tried all three of those and on every one my phone gets stuck in the boot loop. I have tried everything, factory wiping, cache wiping, dalvik wiping, battery wiping, and clear storage. is there any way I can completely delete the operating system off my phone so I can freshly install the new rom of MiUi. This is bootloop also happens to me when I flash micromod and cyanogen. THIS IS SO FRUSTRATING! does anyone have the same problem too
this static X bootloop also happened a lot on KoR. its based on CM6.0 but maybe this solution will also fix your problem:
http://forum.xda-developers.com/showpost.php?p=8023620&postcount=4383
@pseudoheld
You are the freaken man, however, is this a permanent fix or only temporary?
I spoke too soon, when I do HBoot in the boot loader, sometimes it skips going to the recovery and goes into the boot loop. Is there any way to update the bootloader
paintmandoo3993 said:
I tried all three of those and on every one my phone gets stuck in the boot loop. I have tried everything, factory wiping, cache wiping, dalvik wiping, battery wiping, and clear storage. is there any way I can completely delete the operating system off my phone so I can freshly install the new rom of MiUi. This is bootloop also happens to me when I flash micromod and cyanogen. THIS IS SO FRUSTRATING! does anyone have the same problem too
Click to expand...
Click to collapse
I was not referring to the other links on that post. I installed the stock hosted directly on that post. Also provided a link below for your convenience
http://djmcnz.batteryboss.org/MIUI/deodexed/miui-n1-0.11.5-deodexed-signed-PROPER.zip
And the English pack.
http://forums.miui-dev.com/viewtopic.php?f=5&t=39
i will keep you posted, again
and same problem. Bootloop and whenever I go to the HBoot and try to boot into recovery I get the boot loop again and it wont even enter recovery, I gotta pop the battery
what recovery did you use
So this morning I decided to get myself a new ROM on my optimus 2x. After 2years with CyanogenMod7, I was starting to get more and more problems, so I went for it... my 2nd lifetime rom installation.
I thought I understood it all good.. decided to go with ParanoidAndroid CM10 (http://forum.xda-developers.com/showthread.php?t=2097807). I followed pengus's instructions thoughtfully.
1. Copied the ROM .zip, the gapps .zip, and the kernel .zip.,
2. Factory reset, clear cache, dalvik, etc..
3. Booted the phone in recovery, and installed the 3 .zip package in the order I just mentioned (at step1)
After rebooting my phone would keep booting with a new and fresh version of Cyanogenmod 7.. for some reason. I remade the operation a couple times and it would always get my in cyanogenmod (wtf?). Now, after a couple hours of messing around, I installed back nvflash and tried other loaders : cwm 5.0, cwm 6.0, twrp 2.5.0..
Eventually after the usual clear cache / factory reset, unpacking zip files, my phone stoped rebooting in cyanogenmod7, but then it would just get stuck with the "LG" logo forever....
Now, I've taken my ENTIRE day off trying to figure this one now. I've been at it since 8hours more or less, and now I'm expecting calls and I'm out of phone. The whole experience has been very frustrating.... and I'm out of solutions here..
Hopefully this is just a newbie mistake (cuz I'm still kinda newbie in the whole rooting experience). Plz help...
something I don't understand :
when using twrp 2.5.0 as recovery, after I did a full wipe, and fresh installation, just after I click reboot now. it says that it appears my phone is not rooted, and that I can click yes to install SuperSU.. sometimes I click YES, sometimes I don't ... both action don't change the fact that my phone gets stuck at the LG logo.
So turns out I had a gingerbread partition and was trying to install an IceCreamSandwitch version of android.
With All-In-One-Toolkit, I was able to fix the partition and all.... wow all my day because of this ;(
Ok so i had 5.02 rooted kitkat. Obviously unlocked bootloader. It says 3. And twrp 2.8something...
For the previous months every time i rebooted the phone it took like 10 minutes to boot for some reason. But it worked. It was laggy these days so i thought i will wipe everything and install CM12.1.
So i downloaded the rom and gapps. Then i wiped delvik, cache, system, internal memory and data. I also did format data.
I dont really understand, obviously, how android works. So i had the zips on external card and pressed install on from twrp menu. Then wiped cache and delvik cache. Tried to reboot and says 'Warning no OS found'. I say okay and then it says that it wants to root. I say ok again.
Now the PROBLEM is that it does nothing. It justs stucks on motorola boot logo for too much time. I am not sure if this is because i already had a problem with booting taking too much time or because of what i have wiped. I also tried updating bootloader again. Not sure if this changed anything
Long story short, how do i continue now? Is there a way to really delete everything i have done on the phone, then install fresh twrp and then CM12.1? And how do i fix the booting taking too much time problem...
Any help will be valueable. I just dont get how things work because nowadays there are too many things, kernels, roms, bootloaders, recoveries etc... Can i just flash the CM rom from my computer via usb? I tried something like that by ?sideload? only to get a problem about requiring 1.0.32 version. I tried to download new SDK but again i have 1.0.31 version of adb...
Thanks!
P.S. Yes, i am totally lost. But i have desire to understand...
NUKE1989 said:
Ok so i had 5.02 rooted kitkat. Obviously unlocked bootloader. It says 3. And twrp 2.8something...
For the previous months every time i rebooted the phone it took like 10 minutes to boot for some reason. But it worked. It was laggy these days so i thought i will wipe everything and install CM12.1.
So i downloaded the rom and gapps. Then i wiped delvik, cache, system, internal memory and data. I also did format data.
I dont really understand, obviously, how android works. So i had the zips on external card and pressed install on from twrp menu. Then wiped cache and delvik cache. Tried to reboot and says 'Warning no OS found'. I say okay and then it says that it wants to root. I say ok again.
Now the PROBLEM is that it does nothing. It justs stucks on motorola boot logo for too much time. I am not sure if this is because i already had a problem with booting taking too much time or because of what i have wiped. I also tried updating bootloader again. Not sure if this changed anything
Long story short, how do i continue now? Is there a way to really delete everything i have done on the phone, then install fresh twrp and then CM12.1? And how do i fix the booting taking too much time problem...
Any help will be valueable. I just dont get how things work because nowadays there are too many things, kernels, roms, bootloaders, recoveries etc... Can i just flash the CM rom from my computer via usb? I tried something like that by ?sideload? only to get a problem about requiring 1.0.32 version. I tried to download new SDK but again i have 1.0.31 version of adb...
Thanks!
P.S. Yes, i am totally lost. But i have desire to understand...
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657 try to restore to stock
I am trying to do this but i dont have some files like boot.img or logo.bin etc.... Where can i download those? There is a link about mfastboot is not working. I am using linux btw so i guess the fastboot i already have is okay
EDIT: Ok i am obviously stupid. The files are on the zip ROM. Okay i am doing this. Now the question i have is, cant i install CM12.1 using fastboot like this ROM?
Okay and it worked. It booted stock rom and this time it booted in a minute or two (considering it was the first time booting i think its awesome).
Now i have to try CM rom. At least i know how to return the phone back if anything happens. Thank you very very much!
NUKE1989 said:
Okay and it worked. It booted stock rom and this time it booted in a minute or two (considering it was the first time booting i think its awesome).
Now i have to try CM rom. At least i know how to return the phone back if anything happens. Thank you very very much!
Click to expand...
Click to collapse
Glad to help
now just copy the rom you want to install and the gapps, install the latest TWRP, wipe: Cache, Dalvik Cache, Data and System and just flash the zips
Many thanks I managed to install CM12.1. Thought i think i failed to flash most of gapps for some reason i dont really care.
I only have one severe bug. 3G is not working for some reason. So i dont have gsm internet except the slow one...
Before MM I was already having issues with my LP install. Lockups, crashes, etc.. I had planned on performing a fresh install of my LP ROM yesterday but was excited to see that MM was released. I was hoping that installing MM over LP would fix the issue that I was experiencing. No dice.
So, is it possible to go into TWRP, perform a factory reset (including erasing Internal Storage) and then booting into Download Mode so I can install MM fresh using Odin? Is there anything that I need to know of or missing before performing this procedure? I can then reinstall TWRP and root afterwards. I just want a fresh install and can't wait two or three days for a Flashable Zip. My system is just too unstable in its current form.
Thanks.
JC
For The Record
This is exactly what I just did. It works perfectly and now my phone is back to operating normally. And with a clean install of 6.0.1 to boot!
Now....time for TWRP and Root........
What is safe to wipe in TWRP? I did an install of MM for the 910T stock rom and unfortunately tried the encryption. I thought it would give me the option to decrypt, but that is not the case.
Wipe
Mister_E105 said:
What is safe to wipe in TWRP? I did an install of MM for the 910T stock rom and unfortunately tried the encryption. I thought it would give me the option to decrypt, but that is not the case.
Click to expand...
Click to collapse
I wiped EVERYTHING in TWRP. Powered off the phone and then booted to Download Mode. From there I pushed out a fresh copy of MM using Odin. It flashes a new stock recovery. After the phone boots up go back into Download Mode and flash TWRP using Odin. Then you can flash Beta SuperSU in TWRP for root.
But.....I wanted to follow up on this post. My Note 4 started experiencing issues last week. I was hoping a fresh OS install would fix things. Unfortunately for me during a power off to go into recovery to flash SuperSU I received the dreaded mmc_read failed error. The phone is nearly two years old and I have never seen the bug on my device. I had thought that I was one of the lucky early purchasers. I was wrong.
The device got worse and worse. To the point that now it rarely boots at all. It just sits at the "Samsung Note 4" screen. I can't even get into TWRP reliably. And the mmc screen is popping up more frequently now as well.
I had no choice but to stop by T-Mobile yesterday and (reluctantly) buy a S7 Edge. I say reluctantly for two reasons. 1. The Note 7 comes out in barely over a month 2. There is no known root for S7 (and Note 7 will probably be the same)
I have 30 days to decide if this phone is for me or not. Not having root is something that I never thought I'd have to live with. Barring some unforeseen circumstance I thought I'd have the Note 4 for a couple more years. And I didn't have the time to look for a used one as I needed a phone immediately.
Fingers crossed they get this thing roooted because it really is a pretty sexy device!
I found that the only way to clear the encryption was to load the stock recovery, it had the power to wipe the partitions and allow a clean install.