Related
I am unable to install Cyanogenmod. I have TWRP that was installed with AutoRec. I tried flashing the Stable 10.2 CM version,and when I flashed it said "Failed", which put me into a security error boot loop. Then I tried a nightly, and it said "Success" and when I tried to start it up, it put me into another boot loop. I have the stock Kernel, and I am rooted. Is something like goo manager or rom manager better to use for this? Or what is the safest way to install a custom ROM
Zach_Deem said:
I am unable to install Cyanogenmod. I have TWRP that was installed with AutoRec. I tried flashing the Stable 10.2 CM version,and when I flashed it said "Failed", which put me into a security error boot loop. Then I tried a nightly, and it said "Success" and when I tried to start it up, it put me into another boot loop. I have the stock Kernel, and I am rooted. Is something like goo manager or rom manager better to use for this? Or what is the safest way to install a custom ROM
Click to expand...
Click to collapse
JackpotClavin's version is the only one that works on the VS980. http://forum.xda-developers.com/showthread.php?t=2702958
Sent from my XDABBEB VS98025A v2.0.0 using XDA free mobile app
What he said, the official nighties only work with the JB baseband.
So is there any other way to do this? I saw that is is extremely risky, and it will permanently brick my phone. Is there any other thing im able to do to flash this?
Zach_Deem said:
So is there any other way to do this? I saw that is is extremely risky, and it will permanently brick my phone. Is there any other thing im able to do to flash this?
Click to expand...
Click to collapse
If you want CM11 with the KK baseband(24A), use the version z3pp3lin pointed you to, otherwise most other AOSP based roms have already been upgraded to work with the KK baseband, use one of those. Just double check the notes on the rom to make sure it's KK/24A based.
Do I have to do all of those steps? You said there is a like for cyanogenmod for 24a. I don't see one though
Zach_Deem said:
Do I have to do all of those steps? You said there is a like for cyanogenmod for 24a. I don't see one though
Click to expand...
Click to collapse
All those steps are required to manually install a recovery on KK, that was pre-autorec, if you've already installed TWRP, you can skip to step 11.
mjones73 said:
All those steps are required to manually install a recovery on KK, that was pre-autorec, if you've already installed TWRP, you can skip to step 11.
Click to expand...
Click to collapse
So I can only use his roms?
Zach_Deem said:
So I can only use his roms?
Click to expand...
Click to collapse
You have the 24A KK baseband on your phone, you can only use roms that work with that baseband. If you specifically want CM11, you need to use the rom linked, otherwise any other 24A KK based rom will work. Check the notes for any rom you want to install to see what baseband it works with.
mjones73 said:
You have the 24A KK baseband on your phone, you can only use roms that work with that baseband. If you specifically want CM11, you need to use the rom linked, otherwise any other 24A KK based rom will work. Check the notes for any rom you want to install to see what baseband it works with.
Click to expand...
Click to collapse
So If I want cm, I have to use his links correct? I just want to be sure so I don't get another bootloop
Why not just use a AOSP or CM based ROM that works with the 24A baseband... CM is good, but hardly the "best" ROM out there, if there is such a thing... Try AICP 6.0, it is extremely stable and the VS980 version is excellent and very feature packed.
Zach_Deem said:
So If I want cm, I have to use his links correct? I just want to be sure so I don't get another bootloop
Click to expand...
Click to collapse
For about the 4th time, yes.
mjones73 said:
For about the 4th time, yes.
Click to expand...
Click to collapse
Im about to flash the cm version and we will see how this goes
I downloaded the rom onto my phone but I'm scared for some reason. Is it guaranteed to not brick if I'm on the right version?
Zach_Deem said:
I downloaded the rom onto my phone but I'm scared for some reason. Is it guaranteed to not brick if I'm on the right version?
Click to expand...
Click to collapse
Not too freak you out more, but no, there is no guarantee. That's why every ROM has the disclaimer in the OP. By flashing you're taking responsibility that you understand the risks involved. If you flash cm and damage your phone somehow, it's on you. So it's either stay with rooted stock where you know nothing will happen, or flashing and taking the risk. Your choice...
njstein said:
Not too freak you out more, but no, there is no guarantee. That's why every ROM has the disclaimer in the OP. By flashing you're taking responsibility that you understand the risks involved. If you flash cm and damage your phone somehow, it's on you. So it's either stay with rooted stock where you know nothing will happen, or flashing and taking the risk. Your choice...
Click to expand...
Click to collapse
Alright, but is there any way to know if a rom is successfully flashed other than it saying successful or restarting?
Zach_Deem said:
Alright, but is there any way to know if a rom is successfully flashed other than it saying successful or restarting?
Click to expand...
Click to collapse
No.
Probably a stupid question, but please remember I came from an HTC.... so be nice....
On a nexus 6 when I flash a rom, beit custom or stock does it flash the firmware as well?
Also, coming from an HTC I had to take the OTA to update the firmware and then flash my favorite rom based on said firmware to fully be updated.
Does this apply to nexus devices, specifically nexus 6?
k.s.deviate said:
Probably a stupid question, but please remember I came from an HTC.... so be nice....
On a nexus 6 when I flash a rom, beit custom or stock does it flash the firmware as well?
Also, coming from an HTC I had to take the OTA to update the firmware and then flash my favorite rom based on said firmware to fully be updated.
Does this apply to nexus devices, specifically nexus 6?
Click to expand...
Click to collapse
no. just flash the rom, it has everything you need, but the gapps(google apps), which is a second flash.
simms22 said:
no. just flash the rom, it has everything you need, but the gapps(google apps), which is a second flash.
Click to expand...
Click to collapse
I rarely use anyting not based on stock... if I flash a stock LRX22C will i get the firmware as well?
Same goes for when the 5.0.* update rolls out and someone makes a flashable stock rom based on that build. Firmware included?
There's no such thing as "firmware" on the nexus in regards to updates. In fact, theres no such thing on any of these phones, just some silly carriers decide to change things on HTC devices to be called "firmware" - incorrectly I might add... Sooooo short answer, forget about "firmware" as its not a thing.
rootSU said:
There's no such thing as "firmware" on the nexus in regards to updates. In fact, theres no such thing on any of these phones, just some silly carriers decide to change things on HTC devices to be called "firmware" - incorrectly I might add... Sooooo short answer, forget about "firmware" as its not a thing.
Click to expand...
Click to collapse
Thats what i wanted to hear, thank you.
k.s.deviate said:
Thats what i wanted to hear, thank you.
Click to expand...
Click to collapse
No probs.. But actually I'll elaborate a little more...
Full ROM flash from fastboot is also referred to as "flashing factory images) is the equivalent of flashing a HTC RUU. It will include a system.img (ROM), radio.img, boot.img (kernel), recovery.img and bootloader.img.
OTA update will include usually full radio.img, patches to multiple apks (and more) in system (ROM), patch to update recovery, boot loader and often a full boot.img or kernel patch.
Custom rom or converted stock ROM zip will usually be a system image and a boot image.
Hope this helps a little.
rootSU said:
No probs.. But actually I'll elaborate a little more...
Full ROM flash from fastboot is also referred to as "flashing factory images) is the equivalent of flashing a HTC RUU. It will include a system.img (ROM), radio.img, boot.img (kernel), recovery.img and bootloader.img.
OTA update will include usually full radio.img, patches to multiple apks (and more) in system (ROM), patch to update recovery, boot loader and often a full boot.img or kernel patch.
Custom rom or converted stock ROM zip will usually be a system image and a boot image.
Hope this helps a little.
Click to expand...
Click to collapse
So when an updated android version is released, in order to get the best possible performance (on whichever ROM i choose to use) I should just flash the factory image in order to get the latest radio, bootloader and kernel?
k.s.deviate said:
So when an updated android version is released, in order to get the best possible performance (on whichever ROM i choose to use) I should just flash the factory image in order to get the latest radio, bootloader and kernel?
Click to expand...
Click to collapse
If you're staying stock unrooted, ota is the easiest. You'll get latest everything. If you're rooted or have any modifications, standard ota will fail, in which case, factory image is best IMHO.
rootSU said:
If you're staying stock unrooted, ota is the easiest. You'll get latest everything. If you're rooted or have any modifications, standard ota will fail, in which case, factory image is best IMHO.
Click to expand...
Click to collapse
Thanks! I'm bouncing between CleanROM and Chroma..(Can't decide which i like better) so OTA is useless for me.
I do appreciate the help, I've been trying to figure it out myself ever since i got my Nexus but I couldnt find any solid info.
k.s.deviate said:
Thanks! I'm bouncing between CleanROM and Chroma..(Can't decide which i like better) so OTA is useless for me.
I do appreciate the help, I've been trying to figure it out myself ever since i got my Nexus but I couldnt find any solid info.
Click to expand...
Click to collapse
No worries. Well which ever you stick with, just flash a ROM.zip as and when updates are released by your dev. Forget about updating radio and bootloader unless you feel you need to.
rootSU said:
No worries. Well which ever you stick with, just flash a ROM.zip as and when updates are released by your dev. Forget about updating radio and bootloader unless you feel you need to.
Click to expand...
Click to collapse
Sounds good, thanks again!
Alright, I'm in need of some help, and I'm not sure if this is the right place to put this thread, so if it';s in the wrong place, I'm sorry for taking up space in the wrong section.
My issue is with my Nexus 6, the Verizon variant; I had a custom kernal, running 6.0, and was rooted. I wanted to upgrade to 6.0.1, and downloaded the newer version of the ElementalX kernal, the one I was using, as well as the necessary SuperSU files. I downloaded the new Android version, installed it, and before it went intoi the OS, I flashed the kernal and SuperSU upgrade, and now my phone either won't boot, or is taking the longest time for a phone to boot on the planet.
I need to download a 6.0.1 ROM that I can flash with TWRP. Any links or advice anyone could offer would be grately appreciated, because right now, I'm drawing a massive blank.
Many thanks!
Do you need to backup any data?
Could you not just flash a stock "like" rom such as this one by Danvdh http://forum.xda-developers.com/nexus-6/development/rom-5-1lightromstock-lmy47e-03-19-2015-t3059493 as it has already been rooted.
I have been running it for a while, very solid and stable rom.
Which SuperSU did you install?
Reflash the rom youre using and then flash Super su (asuming its not a pre-rooted rom) BEFORE flashing elemental x. Other kernels work the other way around
Question?
Are you trying to run systemless root wit EX? If so did you click on yes when TWRP asked you to root your rom?
That would would cause the rom not to boot.
http://forum.xda-developers.com/showthread.php?t=3252922 stock with root latest q
Don't flash anything else till you boot at least once.
Sent from my Nexus 6 using Tapatalk
joncy92 said:
Do you need to backup any data?
Click to expand...
Click to collapse
I decided to download and flash a custom CM13 build, but it's a bit finicky, kinda to be expected with an early release, though. I'm using that ROM, for now. I'd still prefer getting something from the CM team, something that's supported and I can download upgrades to.
joncy92 said:
Do you need to backup any data?
Click to expand...
Click to collapse
holeindalip said:
Which SuperSU did you install?
Click to expand...
Click to collapse
Pretty sure it was 2.61. I have a few versions of it on my phone, ready for flashing, but was careful, making sure I chose the right one.
swazii said:
Question?
Are you trying to run systemless root wit EX? If so did you click on yes when TWRP asked you to root your rom?
That would would cause the rom not to boot.
Click to expand...
Click to collapse
I'm not great with this stuff. Sorry4Noobishness. I'm not sure what systemeless rooting is.. Originally, I just flashed SuperSU and EX onto the stock ROM I was using. Worked fine. When I decided to upgrade, I downloaded the 6.0.1 ROM, installed it, but didn't boot into the OS. I booted into TWRP, and flashed the new EX and SuperSU stuff. The phone didn't boot after that. It was just stuck on the Google boot animation of all the interacting circles.
I decided to use a custom ROM, a CM13 ROM, but it isn't supported, which is why I'm not looking for a CM13 ROM I can use, because, well, I'd kinda like to be able to upgrade when an upgrade comes out.
Flashing a nightly build from their site did the same thing. I flashed the ROM, then gapps, then SuperSU, and it gets stuck on the boot animation. I let it sit for about half an hour, then restored the custom build I was using. I'm not really sure what to do to get a REAL CM13 build on this thing.
DaJesuZ said:
Pretty sure it was 2.61. I have a few versions of it on my phone, ready for flashing, but was careful, making sure I chose the right one.
Click to expand...
Click to collapse
2.61 is old now, 2.65 is the latest.
DaJesuZ said:
I'm not great with this stuff. Sorry4Noobishness. I'm not sure what systemeless rooting is.. Originally, I just flashed SuperSU and EX onto the stock ROM I was using. Worked fine. When I decided to upgrade, I downloaded the 6.0.1 ROM, installed it, but didn't boot into the OS. I booted into TWRP, and flashed the new EX and SuperSU stuff. The phone didn't boot after that. It was just stuck on the Google boot animation of all the interacting circles.
I decided to use a custom ROM, a CM13 ROM, but it isn't supported, which is why I'm not looking for a CM13 ROM I can use, because, well, I'd kinda like to be able to upgrade when an upgrade comes out.
Flashing a nightly build from their site did the same thing. I flashed the ROM, then gapps, then SuperSU, and it gets stuck on the boot animation. I let it sit for about half an hour, then restored the custom build I was using. I'm not really sure what to do to get a REAL CM13 build on this thing.
Click to expand...
Click to collapse
Sounds to me like you dont have the correct bootloader. Which bootloader are you currently using? try flashing the newest bootloader and radio then flash your rom again. It should then boot up fingers crossed.
Jnewell05 said:
http://forum.xda-developers.com/showthread.php?t=3252922 stock with root latest q
Don't flash anything else till you boot at least once.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Alright, I decided to go with this ROM, but now I'm stuck with an issue: It won't let me install any apps. Minimalist gapps was used, so I'm not sure what's wrong. Should I just flash stock gapps and see how it goes?
DaJesuZ said:
Alright, I decided to go with this ROM, but now I'm stuck with an issue: It won't let me install any apps. Minimalist gapps was used, so I'm not sure what's wrong. Should I just flash stock gapps and see how it goes?
Click to expand...
Click to collapse
Why did you flash gapps? It seems that this rom comes with gapps already.
blanco2701 said:
Why did you flash gapps? It seems that this rom comes with gapps already.
Click to expand...
Click to collapse
Wouldn't let me use the Play Store. Nothing would install, and it's kinda pointless to have an internet-capable device if it can't connect to what's supposed to provide me with that internet connectivity (downloading Chrome, for example). Had to flash stock gapps, but it all seems to be working now.
Hey, i want to return my phone to the stock xiaomi android.
anyone knows how to do that?
currently im on latest evolutionX.
thanks
Was about to ask the same... I think you just need to flash the stock rom, if you are on f2fs you will have to format and change partition type, as stock kernel doesn't have the drivers for it
GatorV said:
Was about to ask the same... I think you just need to flash the stock rom, if you are on f2fs you will have to format and change partition type, as stock kernel doesn't have the drivers for it
Click to expand...
Click to collapse
was able to restore stock by flashing latest rom using miflash.
seems to work perfectly fine.
it is annoying that I can't install youtube vanced though
orma1 said:
was able to restore stock by flashing latest rom using miflash.
seems to work perfectly fine.
it is annoying that I can't install youtube vanced though
Click to expand...
Click to collapse
u can install it but u will have to first disable miui optimizations from developer options.
Does anyone know of a stock miui rom for the Spes that has been debloated of ads and other crap and optimised? Don't mind whether it is a recovery rom or needs to be flashed with fastboot (or miflash).
I'm currently on v13 Android 11 the global version, quite happy to remain on that.
Can someone provide a link to the rom?
Thanks.
Look here: https://xiaomi.eu/community/threads/miui-13-stable-release.64441/
I have tested a lot of roms, and in the end I installed the official one and removed software through adb, today I don't have any bugs or strange problems, besides that I can use the camera in its entirety. I got bored with the custom ones, some games don't run, others are terrible and at the moment there is no fix for this.
Microsheepcl said:
I have tested a lot of roms, and in the end I installed the official one and removed software through adb, today I don't have any bugs or strange problems, besides that I can use the camera in its entirety. I got bored with the custom ones, some games don't run, others are terrible and at the moment there is no fix for this.
Click to expand...
Click to collapse
Ditto, I always appreciate the custom roms and appreciate the efforts developers go to because there are a lot on here that do nothing but complain about custom roms, however I think I'd prefer a stable daily driver. There is no sign of the kernel source being released which would be a big help for the devs.
I've just finished flashing the stock rom and will go about debloating. There are a number of "safe to remove" lists for miui roms so I will get to work.
Thanks the replies guys.
maritimesbob said:
Ditto, I always appreciate the custom roms and appreciate the efforts developers go to because there are a lot on here that do nothing but complain about custom roms, however I think I'd prefer a stable daily driver. There is no sign of the kernel source being released which would be a big help for the devs.
I've just finished flashing the stock rom and will go about debloating. There are a number of "safe to remove" lists for miui roms so I will get to work.
Thanks the replies guys.
Click to expand...
Click to collapse
Hi, may I ask how did you flashed stock ROM? I recently tried to flash 13.0.5 A12 on mine through TWRP, it probably refuses to boot because after the ROM has finished flashing I flashed TWRP next. I also know the fastboot + miflash method but everytime I do it, it gives me anti rollback check error
I downloaded the miui.eu rom which is debloated and allegedly more optimised. I went back A11 the same as I had before I unlocked my bootloader. I flashed the fastboot version and used the bat script inside the zip to flash it.
Alex Zander-kun said:
Hi, may I ask how did you flashed stock ROM? I recently tried to flash 13.0.5 A12 on mine through TWRP, it probably refuses to boot because after the ROM has finished flashing I flashed TWRP next. I also know the fastboot + miflash method but everytime I do it, it gives me anti rollback check error
Click to expand...
Click to collapse
Ok, that's strange, it shouldn't give an antirollback error when you have the same version of android and miui.
Try again with myflash
But surely when flashing the official rom by twrp you damaged something, if I remember correctly the twrp of spes does not have support for flashing a stock rom, even less if it goes as an update.
Anyway, if you want to make your rom boot, try taking the boot.img out of the fastboot rom and flashing that boot.img to your phone and see if it boots.
Microsheepcl said:
Ok, that's strange, it shouldn't give an antirollback error when you have the same version of android and miui.
Try again with myflash
But surely when flashing the official rom by twrp you damaged something, if I remember correctly the twrp of spes does not have support for flashing a stock rom, even less if it goes as an update.
Anyway, if you want to make your rom boot, try taking the boot.img out of the fastboot rom and flashing that boot.img to your phone and see if it boots.
Click to expand...
Click to collapse
My first guess was that it was because at that time I was on an Android 13-based custom ROM (Pixel Experience Plus 13 and CrDroid 9.0), but I was proven wrong after I flashed PE+12 shortly before trying MiFlash. Because it gave me the same error (Anti-rollback check)
Oh, I actually tried the flash-stock-ROM-via-TWRP method after I tried MiFlash method, so I doubt that's the issue. But all I can say is a few days ago I flashed 13.0.5 A12 firmware (latest at the time of writing), so could that be that issue?
I might wanna try what you said, thanks for the suggestion. But for now, I'm on EU and may stay for a few months
Alex Zander-kun said:
My first guess was that it was because at that time I was on an Android 13-based custom ROM (Pixel Experience Plus 13 and CrDroid 9.0), but I was proven wrong after I flashed PE+12 shortly before trying MiFlash. Because it gave me the same error (Anti-rollback check)
Oh, I actually tried the flash-stock-ROM-via-TWRP method after I tried MiFlash method, so I doubt that's the issue. But all I can say is a few days ago I flashed 13.0.5 A12 firmware (latest at the time of writing), so could that be that issue?
I might wanna try what you said, thanks for the suggestion. But for now, I'm on EU and may stay for a few months
Click to expand...
Click to collapse
Always that I need as a base a stock ROM flashed, I "simply" use the fastboot commands that are inside the ROM, I open my ADB/fastboot CMD/terminal, and drag and drop the flash_all.bat file while in Windows or the flash_all.sh file while on Linux. This method allows to me, to can follow the process while the scripts are running, and search for issues (if there are some)
As per the TWRP flashing the stock ROM, it worked fine too. You just need to flash the ROM, then boot to recovery once, you'll find the stock one, then format data from it, then you are ready, either to go straight to system, or if you prefer have TWRP (or any custom recovery), go to fastboot and follow the method to boot to, and then flash it permanently to the ramdisk.