Hello all, i have a redmi 2 pro 2014819
i cant install marshmallow roms, as soon the boot logo comes up, the phone restarts and stay in loop.
am i doing something wrong?
i'm cleaning every partition, then doing a clean flash with rom + Gapps, but no sucess.
so far i've tried ressurection, nexus experience and getting bootloop.
any advice on what to do?
if ur flashing from beta lp miui it will not work u have to flash kk stable and then u have to try it will work fine with twrp
HUNTER_SG said:
if ur flashing from beta lp miui it will not work u have to flash kk stable and then u have to try it will work fine with twrp
Click to expand...
Click to collapse
hmm, let me try. i'm using a brazilian rom, 5.1 . will update later if worked
ty very much! worked like a charm, i didn't read anywhere as far i remember that you have to flash from 4.4.
Related
Hello Guys!!!
I have a Samsung i9505 and I'm trying to use a custom rom. I've been using Google Play Edition 4.4.2 and sometime ago it started to notify the 4.4.3 update. I've tried to install it, but nothing happened. I've installed the Jamal GPE 4.4.3 and it works. The problem is that I can't reboot the device. If I do it, the device does not start again... have to install everything again... I've also tried to install Miui Rom, Mahdi Rom and the problem persists. All these Roms works, but I can't reboot... I'm using Team Win v2.5.0.
Am I doing anything wrong?
Thank You!
thiagob737 said:
Hello Guys!!!
I have a Samsung i9505 and I'm trying to use a custom rom. I've been using Google Play Edition 4.4.2 and sometime ago it started to notify the 4.4.3 update. I've tried to install it, but nothing happened. I've installed the Jamal GPE 4.4.3 and it works. The problem is that I can't reboot the device. If I do it, the device does not start again... have to install everything again... I've also tried to install Miui Rom, Mahdi Rom and the problem persists. All these Roms works, but I can't reboot... I'm using Team Win v2.5.0.
Am I doing anything wrong?
Thank You!
Click to expand...
Click to collapse
reflash your device with original firmware and root again and intsall new roms.
uohvid sunday
fleming.patel said:
reflash your device with original firmware and root again and intsall new roms.
Click to expand...
Click to collapse
Thanks Fleming. I'm gonna try this steps!
Regards,
Thiago C
thiagob737 said:
Thanks Fleming. I'm gonna try this steps!
Regards,
Thiago C
Click to expand...
Click to collapse
Reflashing a stock rom shouldn't be needed.
You are using an old version of the recovery. Upgrade the recovery and everything should probably be solved. Make sure to always fully wipe before flashing roms.
Lennyz1988 said:
Reflashing a stock rom shouldn't be needed.
You are using an old version of the recovery. Upgrade the recovery and everything should probably be solved. Make sure to always fully wipe before flashing roms.
Click to expand...
Click to collapse
Thank you!!!!
I flashed the stock rom and the stock recovery yesterday. After that, I flashed CWM (last version non-touch), mahdi rom 4.4.4 and gapps.
Everything is working now.
Thank You guys!
Regards,
Thiago.
My smg900f goes into bootlop with cm12 alpha http://forum.xda-developers.com/gal...ent/rom-cyanogenmod-12-0-android-5-0-t2945538
I tried with the latest versione of philz touch, with all of build and tried also another 5.0 rom http://forum.xda-developers.com/galaxy-s5/unified-development/nexus-experience-rom-t2944276
if you don't trust me see this https://www.youtube.com/watch?v=mXZ82O-A36Q.. i waited for an hour and i don't know what i wrong
Just don't use cm12. I tried it a couple days ago and didn't think much of it and thought the ui was incredibly ugly. If I were you I'd just wait until more features have been implemented
benderboe said:
My smg900f goes into bootlop with cm12 alpha http://forum.xda-developers.com/gal...ent/rom-cyanogenmod-12-0-android-5-0-t2945538
I tried with the latest versione of philz touch, with all of build and tried also another 5.0 rom http://forum.xda-developers.com/galaxy-s5/unified-development/nexus-experience-rom-t2944276
if you don't trust me see this https://www.youtube.com/watch?v=mXZ82O-A36Q.. i waited for an hour and i don't know what i wrong
Click to expand...
Click to collapse
Have you tried with other recoveries? Like TWRP or CWM? I've used Philz in the past and had nothing but bad experiences. TWRP hasn't ever let me down.
Theshawty said:
Have you tried with other recoveries? Like TWRP or CWM? I've used Philz in the past and had nothing but bad experiences. TWRP hasn't ever let me down.
Click to expand...
Click to collapse
I tried with philz touch and twrp. Same result
benderboe said:
I tried with philz touch and twrp. Same result
Click to expand...
Click to collapse
Well man I'd say your just SOL on this ROM. Your either doing something wrong or it's just not compatible for some reason. Sorry dude but it's time to let it go
I have the same result. However, it is with every Android 5.0 Rom out right now. To me it appears that the recovery (and I have tried them all) is just not fully flashing the rom. Whenever flashing a ROM that is 4.4.2 or 4.4.4 the progress bar goes up as its flashing the rom, then when it finishes the rom is installed. However with the 5.0 Android ROMs or cm12 the progress bar does nothing for about 2 minutes, then when it does start going up it only does part and the finishes really quick and seems like half flash.
I've been using CM12 for basically since the day it came out, I've had no problems yet...It is not as fluid as Touchwiz, but it works for now. I flashed it with Philz. Philz has never let me down until now...
My friend's got a s3 neo and all he wants is cm 12 on his phone. I rooted using towelroot but I can't get into recovery and even if I install any custom recovery the phone boots into download mode saying "Could not do normal boot" bla bla and Qualcomm secure boot enabled and write secured something like that. I think that some qualcomm security is not letting the recovery written in system. AND then when I boot the phone back on and start flashify it says the current installed recovery: Stock recovery.
Help me here guys. I just wanna get into recovery somehow and wipe and get on with lollipop
Was it on 4.4 before updating to cm 12 ?
Rox said:
Was it on 4.4 before updating to cm 12 ?
Click to expand...
Click to collapse
Nope. It's never updated to 4.4 it's on 4.3
Are you sure you have installed the 4.3 custom recovery? The 4.4.4 version cannot work on 4.3. Make sure you followed this guide not the 4.4.4.
Barbarian-King said:
Are you sure you have installed the 4.3 custom recovery? The 4.4.4 version cannot work on 4.3. Make sure you followed this guide not the 4.4.4.
Click to expand...
Click to collapse
Thanks man, was flashing 4.4 recoveries all along...
Are there any other lollipop rom than CM12 ?
@Rox @Barbarian-King Guys I DM'ed you both the same thing. Sorry if I'm annoying you but it's kinda urgent and I'm a nexus 5 user. So I installed the cm12 with TWRP for 4.3. and then after installing it boots into the same "could not do normal boot" download mode screen. Thing is He's kinda jerk and wants it back quicly and I know I can flash stock 4.4.4 but my internet is kinda slow. I have Cm11 and CM12 downloaded but no luck with both
Really need help from both of you
Read requirements before installing ROM. You must be on stock 4.4 firmware
Rox said:
Read requirements before installing ROM. You must be on stock 4.4 firmware
Click to expand...
Click to collapse
Oh! I'm really soryy, so there is no workaraound now ?
I must be on 4.4 ? is there any other rom that doesn't require that
No. Flash stock 4.4 ROM firmware with Odin
Rox said:
No. Flash stock 4.4 ROM firmware with Odin
Click to expand...
Click to collapse
Well, Thanks and :'(
Thanks for the time man, So I install 4.4 and then lollipop
Rox said:
Read requirements before installing ROM. You must be on stock 4.4 firmware
Click to expand...
Click to collapse
I searched but it doesn't say anywhere that you should be on 4.4 either on cm11 or 12 thread...
Anyway you're the developer you obviously know more Mention it I think you should
I've been a mod head for many years and just got my Storm after many happy HTC years. I was just wondering is worth rooting the Storm as it is already running a customised OS. Any thoughts please?
I recomend you rooting . It is simple. Now we have TWRP so i believe custom roms like DU and others will be availble soon AS for now you can choose between COS 12.1.1 (Lollipop) and CM13(marshmallow) and i believe cm12.1 (lollipop). Shotly i recomend rooting.
aciupapa said:
I recomend you rooting . It is simple. Now we have TWRP so i believe custom roms like DU and others will be availble soon AS for now you can choose between COS 12.1.1 (Lollipop) and CM13(marshmallow) and i believe cm12.1 (lollipop). Shotly i recomend rooting.
Click to expand...
Click to collapse
Do you have to increase the size of the system partition to install CM13 (marshmallow) or simply flash the latest CM13 recovery and nightly for the storm(kipper) device.
You dont need to repartition. I recomend flash TWRP and then cm13, because i've had some problems with Cyanogen recovery
Sent from my Wileyfox Storm using XDA Labs
aciupapa said:
You dont need to repartition. I recomend flash TWRP and then cm13, because i've had some problems with Cyanogen recovery
Click to expand...
Click to collapse
OK thanks, I already have TWRP installed, so you can easily install the latest cm13 nightly using TWRP recovery, then an applicable gaps package.
Do you have drivers for the storm. If so post a link
Hey guys, I'll keep it short. I was rooted, installed TWRP, running Simple Rom and was just feeling to flash erobot. Flashed it doing full wipes and then rebooted, cool. Got to the samsung logo and within a second back to the note 4 screen. Okay I said, maybe the file I downloaded was corrupted or I installed it wrong. Did it over again, this time trying a few variations in the aroma installer (not installing xposed) thought maybe that was the problem. Bam same issue.
No worries I still had the old simple rom on the sd card. Went back with the same install and what do you know, that rom is now in a bootloop as well. Tried flashing through odin but I always get a nand write failed to start or something like that. Tried 3 different usb ports and same issue.
Am I missing something? Any advice would be greatly appreciated.
So you are using the Exynos model? Last I checked there is this OJ5 bootloader which can't be downgraded from!
ithehappy said:
So you are using the Exynos model? Last I checked there is this OJ5 bootloader which can't be downgraded from!
Click to expand...
Click to collapse
Yes I'm on the exynos model. So what did I do wrong, I went from lollipop to a lollipop rom. I didn't go back to KK or anything. What do I have to do?
guys help me im having bootloop because i was trying to install the su suser .in my note 4 Note 4 N910C lolipop in tw recovery still boot loop? because i want to root it .send me a maasage thank you
Anyone?
Did you flash a kernel for your variant after flashing the ROM?
No but that is my next move today, had a feeling it might be the problem, I'll try it and report back.
Oj5 bl doesn't let the flash of older rom even lp 5.1.1 older then oj5 but erobot 12 and 13.4 are newest then oj5 so it must be something else like the supersu v2.65 have issues with some costum kernels try to flash v 2.45
radium56ad said:
Oj5 bl doesn't let the flash of older rom even lp 5.1.1 older then oj5 but erobot 12 and 13.4 are newest then oj5 so it must be something else like the supersu v2.65 have issues with some costum kernels try to flash v 2.45
Click to expand...
Click to collapse
Will try that, thanks. On a side note, flashed custom kernel after flashing the ROM and nothing same bootloop.
try this! http://forum.xda-developers.com/note-4/help/n910c-to-stock-rom-cm13-t3321132
migsguerra said:
guys help me im having bootloop because i was trying to install the su suser .in my note 4 Note 4 N910C lolipop in tw recovery still boot loop? because i want to root it .send me a maasage thank you
Click to expand...
Click to collapse
Had the same problem, solved it by flashing cf auto root using ODIN.
can't you just flash the previous rom again??
Enter your recovery and flash your "old" rom