Hi i have a problem, when i install custom rom for example. rr 5.8.3 on 7.1.2 when i boot phone and i have screen welcome and i start configuration and this configuration crashed, i install with wipe, and i install new nitrogenos and i have the same situation. When i install rom on 7.1.1 all its ok, what can i do to fix it? Please help me its screen from phone http://imgur.com/a/uUPls
You might be using an outdated GApps package, as it is known to cause this issue. Try with the latest opengapps.
jayaram95 said:
You might be using an outdated GApps package, as it is known to cause this issue. Try with the latest opengapps.
Click to expand...
Click to collapse
Yea i install old version gapps and i dont have any problems on 7.1.1, hmm then i must install new gapps if i check i will write
;P
You can flash newer gapps from here.
OR
You can follow this guide on older gapps.
Very thanks, i have one question, i must install firmware to install rom for example rr or nitrogen? i never install and everything is right
Okay i install beansgapps and its works Thanks for help
badamczuk1 said:
Very thanks, i have one question, i must install firmware to install rom for example rr or nitrogen? i never install and everything is right
Click to expand...
Click to collapse
no need to flash it if there's nothing wrong
if there's something wrong, try to flash latest MIUI Beta firmware, you can find it in ROM section, and no need to flash it everytime you flash a new ROM, just flash it once and you're good to go
Related
Hello guys, I am a newbie to this forum(been following it for a long time and finaaly decided to join)
Anyways,
I am using a rooted moto e with twrp 2.7.2.0.
My problem is that when I flash this stock rom flashable zip(optimised version)
http://forum.xda-developers.com/moto-e/development/flashable-zip-stock-deodexed-rom-moto-e-t2823368
it flashes fine.But after clean flashing this rom, when I try to flash PA Gapps it throws an error which says
"INSTALLATION FAILURE: PA GApps can only be installed on top of an existing
PA GApps installation. Since you are currently using another GApps package, you
will need to wipe (format) your system partition before installing PA GApps"
This is happening for this file pa_gapps-modular-mini-4.4.4-20141121-signed.
It worked fine with previous versions of PA Gapps.I have attached the log file below.
Please help.
Why are you flashing gapps on a ROM that already has the playstore?
Sent from my XT1023
it will not work...as stock rom already have a gapp package
alex_is_the_1 said:
Why are you flashing gapps on a ROM that already has the playstore?
Sent from my XT1023
Click to expand...
Click to collapse
Just to update all Google applications to the latest version.
dchatterjee172 said:
it will not work...as stock rom already have a gapp package
Click to expand...
Click to collapse
Let me see flashing older gaaps versions. Yup i tried with an older version which is not gaaps 2.0
pa_gapps-modular-mini-4.4.4-20141110 and this worked. Maybe its a problem with latest gaaps package.
I was wondering if someone could clarify if dirty flashing a cm13 upgrade (nightly) you can also flash new gapps, or if based on the recommendation below that can only be done on first cm flash from stock.
Anyone ever done this or it just is not useful /should not /cannot be done?
"Note: In case you want to use any gapps, YOU MUST install the right gapps the first time that you flash a marshmallow ROM. Do not boot with an older gapps or without one and then try to install it later."
Thanks!
Yes you can flash new gapps after dirty flashing CM13. But I don't know why anyone would do that since CM13 has gapps persistence between dirty flash.
Pixel launcher as system app got me wondering about this!
Thanks!
xskull03 said:
Yes you can flash new gapps after dirty flashing CM13. But I don't know why anyone would do that since CM13 has gapps persistence between dirty flash.
Click to expand...
Click to collapse
AGREE !~:good:
do whatever , but remember,
DO NOT TURN ON THAT "UPDATE CYANOGEN RECOVERY" OPTION, which erases twrp ,
and too many ppl complain about stuck in cm recovery after ota,, remember that..
Thanks for that!
Don't even know where that is.
Will look for it!
jvc73 said:
Thanks for that!
Don't even know where that is.
Will look for it!
Click to expand...
Click to collapse
It's in Developer Options.
Sent from my Galaxy Tab 3 using XDA Labs
Been using the Xiaomi Redmi Note 3 (Kenzo) for a long time now and since the ROM was outdated, I decided to update it this past weekend. However for whatever reason, something broke and I've been getting bootloops. Since then, this is what I did and it still doesn't work.
Used MiFlash to fastboot flash MIUI v8.5.1.0 Global Stable, and then OTA updated to v8.5.2.0.
Test the phone to make sure all functions work properly.
Immediately officially unlocked the bootloader using Mi Unlock.
Fastboot flashed TWRP 3.1.1.0.
Made EFS and ROM backups as usual.
Clean flashed Resurrection Remix 5.7.4 (Radon kernel) with /data and /cache as F2FS.
Flashed Open Gapps 6.0 ARM64 Mini.
Right now, I'm back to running stock MIUI v8.5.1.0, which was flashed using MiFlash. Then I did the OTA update to MIUI v8.5.2.0. May someone please guide me or correct the above steps in order to install the linked Resurrection Remix ROM? Or maybe a Nougat ROM?
geokilla said:
Been using the Xiaomi Redmi Note 3 (Kenzo) for a long time now and since the ROM was outdated, I decided to update it this past weekend. However for whatever reason, something broke and I've been getting bootloops. Since then, this is what I did and it still doesn't work.
Used MiFlash to fastboot flash MIUI v8.5.1.0 Global Stable, and then OTA updated to v8.5.2.0.
Test the phone to make sure all functions work properly.
Immediately officially unlocked the bootloader using Mi Unlock.
Fastboot flashed TWRP 3.1.1.0.
Made EFS and ROM backups as usual.
Flashed Resurrection Remix 5.7.4 (Radon kernel) with /data and /cache as F2FS.
Flashed Open Gapps 6.0 ARM64 Mini.
Right now, I'm back to running stock MIUI v8.5.1.0, which was flashed using MiFlash. Then I did the OTA update to MIUI v8.5.2.0. May someone please guide me or correct the above steps in order to install the linked Resurrection Remix ROM? Or maybe a Nougat ROM?
Click to expand...
Click to collapse
Try without f2fs. Use ext4
geokilla said:
Been using the Xiaomi Redmi Note 3 (Kenzo) for a long time now and since the ROM was outdated, I decided to update it this past weekend. However for whatever reason, something broke and I've been getting bootloops. Since then, this is what I did and it still doesn't work.
Used MiFlash to fastboot flash MIUI v8.5.1.0 Global Stable, and then OTA updated to v8.5.2.0.
Test the phone to make sure all functions work properly.
Immediately officially unlocked the bootloader using Mi Unlock.
Fastboot flashed TWRP 3.1.1.0.
Made EFS and ROM backups as usual.
Flashed Resurrection Remix 5.7.4 (Radon kernel) with /data and /cache as F2FS.
Flashed Open Gapps 6.0 ARM64 Mini.
Right now, I'm back to running stock MIUI v8.5.1.0, which was flashed using MiFlash. Then I did the OTA update to MIUI v8.5.2.0. May someone please guide me or correct the above steps in order to install the linked Resurrection Remix ROM? Or maybe a Nougat ROM?
Click to expand...
Click to collapse
Flash LOS 13 which is far stable than the RR 5.7.4. You should've flashed another rom before moving back to MIUI. The process you followed is correct but you also need to flash the compatible firmware like for RR you need CM13 firmare and for LOS you'll the recommended firmware posted in the thread itself.
I went through some ROM threads and one recommended flashing MIUI8 Global DEVELOPER and not Global STABLE. Am I supposed to be using MIUI 8 Global DEVELOPER as the starting point?
vistaabalaji said:
Try without f2fs. Use ext4
Click to expand...
Click to collapse
EXT4 had the same issue. Just bootloops forever.
naturist said:
Flash LOS 13 which is far stable than the RR 5.7.4. You should've flashed another rom before moving back to MIUI. The process you followed is correct but you also need to flash the compatible firmware like for RR you need CM13 firmare and for LOS you'll the recommended firmware posted in the thread itself.
Click to expand...
Click to collapse
The Resurrection Remix build I linked is based off of LineageOS 13 so it should be stable.
So you're saying I missed flashing a firmware? I see some ROMs recommend flashing the firmware, while others don't. Which is the proper firmware to flash if the ROM thread doesn't state which firmware to use?
geokilla said:
I went through some ROM threads and one recommended flashing MIUI8 Global DEVELOPER and not Global STABLE. Am I supposed to be using MIUI 8 Global DEVELOPER as the starting point?
EXT4 had the same issue. Just bootloops forever.
The Resurrection Remix build I linked is based off of LineageOS 13 so it should be stable.
So you're saying I missed flashing a firmware? I see some ROMs recommend flashing the firmware, while others don't. Which is the proper firmware to flash if the ROM thread doesn't state which firmware to use?
Click to expand...
Click to collapse
The one on this thread. Second post.
well seems to be a new problem...
so what must be done... i will suggest to get latest miui fastboot rom from here
https://forum.xda-developers.com/redmi-note-3/how-to/links-direct-official-download-links-t3449488
flash it via mi flash tool (im running 64 bit os ,so using mi flash beta ) in edl mode by wiping full things including storage..
if your boot loader is unlocked official way it must be unlocked now also if not i guess you know how to unlock it officially.
then use official twrp from
www.twrp.me
i faced this issue once and did the exact steps above and now no problem..
by the way i tried things like unplugging battery from the board... lol... read in miui forum...
I've been having very similar issues (updated official firmware in a non officially unlocked bootloader).
It's been hell but I've managed to get los14.1 installed. Now my issue lies with constant gapps crashes. I'm thinking of just giving up and getting miui.
Felheipe said:
I've been having very similar issues (updated official firmware in a non officially unlocked bootloader).
It's been hell but I've managed to get los14.1 installed. Now my issue lies with constant gapps crashes. I'm thinking of just giving up and getting miui.
Click to expand...
Click to collapse
use latest gapps.outdated or older one causes crashes...
adithyan25 said:
use latest gapps.outdated or older one causes crashes...
Click to expand...
Click to collapse
One would think so but in reality is the other way around. I'm using a 20170303 and it has been the most stable version across all my devices and so on.
Felheipe said:
One would think so but in reality is the other way around. I'm using a 20170303 and it has been the most stable version across all my devices and so on.
Click to expand...
Click to collapse
seriously the one from march??
dude just download older gapps wont work on latest updates. ot will force close for sure...
at least try before telling ..use latest one from opengapps... there is a reason they are updating tje sote everyday...ftom the may builds you need latest gapps as petr release dates... just give a try ..its only 150 mb or so.... i can vonform its duw to outdated gapps
adithyan25 said:
well seems to be a new problem...
so what must be done... i will suggest to get latest miui fastboot rom from here
https://forum.xda-developers.com/redmi-note-3/how-to/links-direct-official-download-links-t3449488
flash it via mi flash tool (im running 64 bit os ,so using mi flash beta ) in edl mode by wiping full things including storage..
if your boot loader is unlocked official way it must be unlocked now also if not i guess you know how to unlock it officially.
then use official twrp from
www.twrp.me
i faced this issue once and did the exact steps above and now no problem..
by the way i tried things like unplugging battery from the board... lol... read in miui forum...
Click to expand...
Click to collapse
That's exactly what I did, as I mentioned in OP lol. Except I wasn't flashing MIUI 8 in EDL mode.
adithyan25 said:
seriously the one from march??
dude just download older gapps wont work on latest updates. ot will force close for sure...
at least try before telling ..use latest one from opengapps... there is a reason they are updating tje sote everyday...ftom the may builds you need latest gapps as petr release dates... just give a try ..its only 150 mb or so.... i can vonform its duw to outdated gapps
Click to expand...
Click to collapse
I tried 0625 and the newest one. 0303 is the latest stable Google play services (as far as i am aware).
Felheipe said:
I tried 0625 and the newest one. 0303 is the latest stable Google play services (as far as i am aware).
Click to expand...
Click to collapse
no idont guess so...
pls try after downloading latest one from here
www.opengapps.org
arm64-7.1- pico(if you want Google assistant you must use nano or above)
iam using yesterday build of opengapps and not facing any issues...and do a clean flash if possible...
or else you can tru beansgapps....
edit:- playservices had updated many times after 0303.. so i can say its outdated
adithyan25 said:
no idont guess so...
pls try after downloading latest one from here
www.opengapps.org
arm64-7.1- pico(if you want Google assistant you must use nano or above)
iam using yesterday build of opengapps and not facing any issues...and do a clean flash if possible...
or else you can tru beansgapps....
Click to expand...
Click to collapse
I've tried yesterdays version. Play store wouldn't even open. Dirty flashed 0625 play store opens but a lot of apps crash, everything works fine with 0303.
I'm flashing miui and I'm going to try the official bootloader unlock, but this have been a couple of strange days.
Felheipe said:
I've tried yesterdays version. Play store wouldn't even open. Dirty flashed 0625 play store opens but a lot of apps crash, everything works fine with 0303.
I'm flashing miui and I'm going to try the official bootloader unlock, but this have been a couple of strange days.
Click to expand...
Click to collapse
dirty flashing isn't a solution ... theres changes in trees of the rom and kernel..
anyway head back to miui unlocl officially and when coming back to custom rom do wipe everything and give it a shot..probably the crash may be due to over written or exiating files...
happy flashing
~peace
I should mention I clean flashed the ROMs. Updated OP.
Ok trying it again right now and so far, this is what I did:
Used MiFlash to fastboot flash MIUI v7.7.6 Global DEV.
Test the phone to make sure all functions work properly.
Tried to unlock bootloader using Mi Unlock but it said bootloader is already unlocked.
Boot into MIUI again.
Fastboot flashed TWRP 3.1.1.0.
No boot into MIUI.
Flash Kenzo firmware 8.2.4.0 in TWRP
Clean flash LineageOS 13 and Open Gapps 6.0 ARM64 Mini with /data and /cache in EXT4
IT WORKS!
I guess now I'll try Resurrection Remix.
Hi, currently i just flash crdroid into my old i9300, but after flash i cant flash gaaps using twrp.
Whenever i try to open gaaps zip file from twrp, it return to main twrp menu. Anyone can help me?
And after i flash crdroid 7.1.2 without gaaps, my phone lock on (D carrier). But my sim are (A carrier). Why?
Sorry if i created double post but i try search Google fews hours still cant find any solution.
Please help.
Have you done clean install of both? are your gapps compatible? (it should be ARM 7.1) About the network lock try different modem. And what about other roms like ressurection remix?
McXred said:
Have you done clean install of both? are your gapps compatible? (it should be ARM 7.1) About the network lock try different modem. And what about other roms like ressurection remix?
Click to expand...
Click to collapse
I downloaded crdroid 7.1.2, but gaaps until 7.1 only.
Can you please guide me to do a clean install?
I havent try other rom bcz i try download ressurectio. Remix but the link was down.
Hello everyone I'm new to all this so please go easy on me.
The problem I am having is I want to install lineage os on my HTC one max but every time I do so after I hit reboot system the HTC logo comes up and then my phone will constantly restart it self. i wipe dalvik cache, Cache, data and system before I flash the Rom and gapps, any help would be appreciated thanks
The rom that you are trying to install is official lineage, is not where you get the rom i ned more info,
mtkmanjaro said:
The rom that you are trying to install is official lineage, is not where you get the rom i ned more info,
Click to expand...
Click to collapse
i would send a link to it but as i am new i am not allowed if you search "Htc One Max LineageOS" it's the first link by Cyanogenmods.org there is a download link in there.
it is supposed to be an unofficial version by tarkzim
EJ251 said:
i would send a link to it but as i am new i am not allowed if you search "Htc One Max LineageOS" it's the first link by Cyanogenmods.org there is a download link in there.
it is supposed to be an unofficial version by tarkzim
Click to expand...
Click to collapse
Well there's two possible causes for bootlop, this build is not support your variant , or you downloaded the wrong architecture of gapps for Htc one Max you need to get the Arm 32 gapps, if you flashed the Arm 64 then there's the problem.
I suppose you do all wipes before flashing the rom.
mtkmanjaro said:
Well there's two possible causes for bootlop, this build is not support your variant , or you downloaded the wrong architecture of gapps for Htc one Max you need to get the Arm 32 gapps, if you flashed the Arm 64 then there's the problem.
I suppose you do all wipes before flashing the rom.
Click to expand...
Click to collapse
according to my phone the model number is just HTC One Max, i am using the 32bit gapps and have done all wipes before hand.
EJ251 said:
according to my phone the model number is just HTC One Max, i am using the 32bit gapps and have done all wipes before hand.
Click to expand...
Click to collapse
Maybe you need to update to a lastest firmware before installing lineage, ¿Are you trying a custom kernel or something? If you do all wipes and your variant is supported i don't see the reason, why you can't boot, you can try another rom to see if the problem is in the lineage rom itself
mtkmanjaro said:
Maybe you need to update to a lastest firmware before installing lineage, ¿Are you trying a custom kernel or something? If you do all wipes and your variant is supported i don't see the reason, why you can't boot, you can try another rom to see if the problem is in the lineage rom itself
Click to expand...
Click to collapse
yeah ill give another rom a try, i got onto cyanogen's website and looked through the device support list and my phone isn't listed on either the official or unofficial list so i dunno maybe it doesn't support it not sure why there is a download available though