Related
Hi guys, its been a few days since I joined here. [Read : I am a noob/newbie in Android related things, and I desperately need help.]
In July (maybe, I forgot), I rooted my ZE550KL, using exactly this method from the website of www-asus-zenfone-com. :cyclops:
Now that, my android seems aged, I wanna shift/upgrade to Marshmallow/Nougat, be it Stock or Custom ROM.
Few days earlier, I unlocked my Bootloader using the Unofficial Bootloader Unlocking Method, as found on this Forum.
I also installed TWRP Recovery, and I tried to flash CM-14.1 [7.1] Nougat-Nightly through TWRP, but, unfortunately, resulted in Status 7 Error. I tried to solve the problem by removing "asserts" section in Update-Binary text file, in the build. But, again, I seemingly worsened the problem; as I got Status 6 error thereby. So, I did factory reset, and I still retain root.
Now, today as I am going through the Official thread of CM 14.1 Nougat, I saw numerous users reporting Bugs of connection issues (something like Wifi to Mobile Data switch problem), which I would like to OBVIOUSLY AVOID, as I want a stable, bug-less build. So, I am thinking to go with the last snapshot build of CM 13.0 Marshmallow.
Here comes the my question : " SHOULD I FLASH CM 13.0 MM -- OR -- STOCK ROM OF MM -- OR -- RESURRECTION REMIX MM ROM?? "
In any of the case, please guide me through the process of doing so.
And, if I have to flash CM 13.0 MM, what would I do if I encounter Status Error 7 again ? :crying:
first you have to upgrade it to marshmallow using stock rom. Then you can flash cm13 or cm14.1
Devc100 said:
first you have to upgrade it to marshmallow using stock rom. Then you can flash cm13 or cm14.1
Click to expand...
Click to collapse
Please, like I said, guide me through how to do it. Thanks in advance, in case you help. :good:
Ph4nToM_Z3rO said:
Hi guys, its been a few days since I joined here. [Read : I am a noob/newbie in Android related things, and I desperately need help.]
In July (maybe, I forgot), I rooted my ZE550KL, using exactly this method from the website of www-asus-zenfone-com. :cyclops:
Now that, my android seems aged, I wanna shift/upgrade to Marshmallow/Nougat, be it Stock or Custom ROM.
Few days earlier, I unlocked my Bootloader using the Unofficial Bootloader Unlocking Method, as found on this Forum.
I also installed TWRP Recovery, and I tried to flash CM-14.1 [7.1] Nougat-Nightly through TWRP, but, unfortunately, resulted in Status 7 Error. I tried to solve the problem by removing "asserts" section in Update-Binary text file, in the build. But, again, I seemingly worsened the problem; as I got Status 6 error thereby. So, I did factory reset, and I still retain root.
Now, today as I am going through the Official thread of CM 14.1 Nougat, I saw numerous users reporting Bugs of connection issues (something like Wifi to Mobile Data switch problem), which I would like to OBVIOUSLY AVOID, as I want a stable, bug-less build. So, I am thinking to go with the last snapshot build of CM 13.0 Marshmallow.
Here comes the my question : " SHOULD I FLASH CM 13.0 MM -- OR -- STOCK ROM OF MM -- OR -- RESURRECTION REMIX MM ROM?? "
In any of the case, please guide me through the process of doing so.
And, if I have to flash CM 13.0 MM, what would I do if I encounter Status Error 7 again ? :crying:
Click to expand...
Click to collapse
While flashing CM13 if that error 7 includes "asus.verify trustzone failed..." Then its bcoz of need to update modem files (LP to MM)....
Easy way to overcome it is..... download MM modem ZIP from second post of OFFICIAL CM13 thread (120MB) and flash it using TWRP (If you are using twrp).... THEN you can flash cm13 hopefully without error 7....
If you are using stock recovery then Either u can flash twrp and use above method... OR... Download ASUS ZE550KL firmware zip file from ASUS site (1.6GB) .... Put it in SDCARD... Then boot to stock recovery and use "apply update from sdcard" option... select ZIP... Alongwith firmware Ur Modem files will also update to MM... and now u can flash twrp and then cm13...
sorry.. I know if i am lazy to post direct links...
Try it.. I will help if i can
aadi50 said:
While flashing CM13 if that error 7 includes "asus.verify trustzone failed..." Then its bcoz of need to update modem files (LP to MM)....
Easy way to overcome it is..... download MM modem ZIP from second post of OFFICIAL CM13 thread (120MB) and flash it using TWRP (If you are using twrp).... THEN you can flash cm13 hopefully without error 7....
If you are using stock recovery then Either u can flash twrp and use above method... OR... Download ASUS ZE550KL firmware zip file from ASUS site (1.6GB) .... Put it in SDCARD... Then boot to stock recovery and use "apply update from sdcard" option... select ZIP... Alongwith firmware Ur Modem files will also update to MM... and now u can flash twrp and then cm13...
sorry.. I know if i am lazy to post direct links...
Try it.. I will help if i can
Click to expand...
Click to collapse
Thanks, dude. One question, should I get CM 13.0 or Resurrection Remix ?
Ph4nToM_Z3rO said:
Thanks, dude. One question, should I get CM 13.0 or Resurrection Remix ?
Click to expand...
Click to collapse
We have both stable RR and CM13.
CM is simple and clean and less loaded.... RR is most feature rich Custom rom we have alongwith stability...
Rest depends on what type of user, u are... If u like trying differnt ROMs... Start with CM13...
If u just want to have a feature rich longtime setup, U can use RR directly without wasting time... It is based on CM, So it obviously have everything CM has.... :good:
Ph4nToM_Z3rO said:
Please, like I said, guide me through how to do it. Thanks in advance, in case you help. :good:
Click to expand...
Click to collapse
Latest Stock Marshmallow:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550KL/UL-Z00L-WW-21.40.1220.1877-user.zip
Stock RecoveryRestore it using TWRP)
https://drive.google.com/open?id=0B2BGto29cXq1NjYySjRES21yOTg
Last Lollipop Software:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550KL/UL-Z00L-WW-1.17.40.1531-user.zip
First Lollipop Software:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550KL/UL-Z00L-WW-1.11.40.299-user.zip
First Do A nandroid backup of your phone. So that if any thing goes wrong, U can recover it.
Then Download both the Stock MM and Recovery file named TWRP.zip.
Extract TWRP.zip.
Then take both the MM software and Xtracted TWRP folder in a memory card.
Then Open TWRP recovery in ur phone and restore the stock recovery.
Then Erase Every Thing including System.
Then Restart The recovery. Now you will see that the recovery has gone back to the stock recovery.
Now flash the stock marshmallow from your memory card.
Then flash TWRP from fastboot and thn u can flash any supported custom Android MM or Android N.
N.B. If it dosent work. Then you have to first install the last lollipop Zenfone 2 Laser(Z00LD) software then install the marshmallow.
Hey friends i am seeing green screen after flashing custom ROM and i am not able to boot into custom rom.
Phone model Samsung j500F 2015.
aytida4 said:
Hey friends i am seeing green screen after flashing custom ROM and i am not able to boot into custom rom.
Phone model Samsung j500F 2015.
Click to expand...
Click to collapse
It's because you are flashing MM rom (except cm13) and you are on Lollipop or vice versa.
#Henkate said:
It's because you are flashing MM rom (except cm13) and you are on Lollipop or vice versa.
Click to expand...
Click to collapse
No friend actually I m using marshmallomarshmallow stock
Rom and I'm installing ressurction Rom 6.0 but still it is showing green screen. Is it the problem of BOOTLOADER?
aytida4 said:
No friend actually I m using marshmallomarshmallow stock
Rom and I'm installing ressurction Rom 6.0 but still it is showing green screen. Is it the problem of BOOTLOADER?
Click to expand...
Click to collapse
I have the same problem …
aytida4 said:
No friend actually I m using marshmallomarshmallow stock
Rom and I'm installing ressurction Rom 6.0 but still it is showing green screen. Is it the problem of BOOTLOADER?
Click to expand...
Click to collapse
SiiXFX said:
I have the same problem …
Click to expand...
Click to collapse
You must be on Lollipop to flash RR 6.0.1, just like CM13.
#Henkate said:
You must be on Lollipop to flash RR 6.0.1, just like CM13.
Click to expand...
Click to collapse
Thanks friend I will try.
Same Green Screen
I have a same problem and i try the first 5.1.1 rom and after it i install the cyanogenmod 13 which i found in the rom article anybody can help me ? skype or somthing call service ?
Vityy said:
I have a same problem and i try the first 5.1.1 rom and after it i install the cyanogenmod 13 which i found in the rom article anybody can help me ? skype or somthing call service ?
Click to expand...
Click to collapse
Friend i had that problem then i installed stock 5.1.1 rom and
Then tried this and then it is working good. U can also
Try this.
aytida4 said:
Friend i had that problem then i installed stock 5.1.1 rom and
Then tried this and then it is working good. U can also
Try this.
Click to expand...
Click to collapse
I flashed the 5.1.1 rom but still i get the green screen/lines at the boot. I always get bootloops when i flash any zip. Plz help
aytida4 said:
Hey friends i am seeing green screen after flashing custom ROM and i am not able to boot into custom rom.
Phone model Samsung j500F 2015.
Click to expand...
Click to collapse
Possible problems,
- the rom is not for your device or variant
- The bootloader is for another version of Android
- Twrp was compiled with a different version of Android so are you going to get an error.
- Your bad luck exceeds an acceptable level ... ???
I have the same problem on my j500h too its turn to yellow color until the logo cant see because of that color i flashed custom kernel properly step by step 2 custom kernel i flashed they have already problem with that im running on 5.1.1 lollipop and my build number is LMY48B.J500HXXU1APA5
Keancarl said:
I have the same problem on my j500h too its turn to yellow color until the logo cant see because of that color i flashed custom kernel properly step by step 2 custom kernel i flashed they have already problem with that im running on 5.1.1 lollipop and my build number is LMY48B.J500HXXU1APA5
Click to expand...
Click to collapse
Which Custom Rom did you flash?
Keancarl said:
I have the same problem on my j500h too its turn to yellow color until the logo cant see because of that color i flashed custom kernel properly step by step 2 custom kernel i flashed they have already problem with that im running on 5.1.1 lollipop and my build number is LMY48B.J500HXXU1APA5
Click to expand...
Click to collapse
You get green screen when:
1) You flash MM ROMs (based on stock Touchwiz MM) over Lollipop and vice versa.
2) You flash MM/N ROMs (based on AOSP/CM such as LOS13, AOSIP, Mokee etc.) over Lollipop and vice versa.
3) I can't confirm this, but based on your comment, you get green screen when you flash a MM kernel over Lollipop and of course, vice versa too.
AndroiDTechi said:
Which Custom Rom did you flash?
Click to expand...
Click to collapse
not custom rom but kernel idk what the problem is so now i decided to have android backup in order to back again to my current system
---------- Post added at 06:46 AM ---------- Previous post was at 06:31 AM ----------
#Henkate said:
You get green screen when:
1) You flash MM ROMs (based on stock Touchwiz MM) over Lollipop and vice versa.
2) You flash MM/N ROMs (based on AOSP/CM such as LOS13, AOSIP, Mokee etc.) over Lollipop and vice versa.
3) I can't confirm this, but based on your comment, you get green screen when you flash a MM kernel over Lollipop and of course, vice versa too.
Click to expand...
Click to collapse
:good: i back to its current system now what i want is stock rom with customize and rooted system
aytida4 said:
Hey friends i am seeing green screen after flashing custom ROM and i am not able to boot into custom rom.
Phone model Samsung j500F 2015.
Click to expand...
Click to collapse
Flash 5.1.1 cynogenmod rom then install RR remix
Demicro said:
Possible problems,
- the rom is not for your device or variant
- The bootloader is for another version of Android
- Twrp was compiled with a different version of Android so are you going to get an error.
- Your bad luck exceeds an acceptable level ...
Click to expand...
Click to collapse
For those, who -as I did - don't really understand this (see the quote)...
I had the same issue when I wanted to install a custom Marshmallow ROM (6.0.1) over my stock Lollipop (5.1.1). The solution was to download and flash a new Bootloader and Modem with Odin. See tis:
https://forum.xda-developers.com/galaxy-j5/how-to/6-0-1-5-1-1-bootloader-modem-j500xx-t3566801
I just ran into this error while trying to install a custom ROM for my J500H.
My phone was running latest 6.0.1. I installed TWRP from This thread, then installed followed the instructions to install Resurrection Remix (7.1.2), but on first boot i got the green screen with the error (set warranty bit: kernel). Also tried Lineage 14.0 but doesn't work. I can still enter TWRP and download mode after getting this error.
This is my first time flashing a Samsung device. Could someone tell me what i did wrong?
https://forum.xda-developers.com/galaxy-j5/development/rom-resurrectionremix-v5-8-1-t3566035
iH8Ecchi said:
I just ran into this error while trying to install a custom ROM for my J500H.
My phone was running latest 6.0.1. I installed TWRP from This thread, then installed followed the instructions to install Resurrection Remix (7.1.2), but on first boot i got the green screen with the error (set warranty bit: kernel). Also tried Lineage 14.0 but doesn't work. I can still enter TWRP and download mode after getting this error.
This is my first time flashing a Samsung device. Could someone tell me what i did wrong?
Click to expand...
Click to collapse
Sorry, first time i didn't your post till the end.
First of all.
Restore firmware with "Samsung smart switch".
You can downgrade to 5.1.1 by this instruction.
1.Flash this firmware by Odin
https://drive.google.com/file/d/0B-pt1IG7T4hmVzhuMnRyeTBjTGM/view?usp=drivesdk
(Before flashing, wipe all storages(all except internal, external in advanced wipe. If you have stock recovery, you must do both wipes)
2. After first boot flash recovery from Vince
(for both bootloaders)
3. Before flashing RR5.8.4 wipe all storages too( all, except extrnl and intrlnl)
4. Flash RR and gapps.
5. Wipe data and cache.
wrongwriter3 said:
Sorry, first time i didn't your post till the end.
First of all.
Restore firmware with "Samsung smart switch".
You can downgrade to 5.1.1 by this instruction.
1.Flash this firmware by Odin
https://drive.google.com/file/d/0B-pt1IG7T4hmVzhuMnRyeTBjTGM/view?usp=drivesdk
(Before flashing, wipe all storages(all except internal, external in advanced wipe. If you have stock recovery, you must do both wipes)
2. After first boot flash recovery from Vince
(for both bootloaders)
3. Before flashing RR5.8.4 wipe all storages too( all, except extrnl and intrlnl)
4. Flash RR and gapps.
5. Wipe data and cache.
Click to expand...
Click to collapse
Did you mean i have to flash RR over 5.1.1? Last time i ran into this error i was flashing it over 6.0.1, and I did full wipes within TWRP.
iH8Ecchi said:
Did you mean i have to flash RR over 5.1.1? Last time i ran into this error i was flashing it over 6.0.1, and I did full wipes within TWRP.
Click to expand...
Click to collapse
Yes.
Because it work only with 5.1.1 bootloader.
HEY THERE THIA S IS SHANTANU MISHRA ..
I NEED AN URGENT HELP REGARDING VOLTE ISSUE
FROM LAST 3-4 MONTH I AM USING ROM AND MIUI DEV ROMS VOLTE WORKS GREAT BUT AFTER FKNG LAG I MAKE A DECISION TO INSTALL A NEW ROM THT IS CM13 . I DOWNLOAD THE ROM AND GOING FOR ISNTALL IT I DO WIPE SYSTEM ,ARCHE ,DATA ,INTERNAL FULL WIPE AND THEN INSTALL A ROM ITS GIVING ME AN ERROR NO SYSTEM IMAGE .. THN I FLASH FASTBOOT 4.4 KITKAT MIUI OFFICIAL AND THEN INSTALL 3.0.2.0 RECOVERY AND FLASH CM13 MOKEE 7.1.1 MOKEE 6.0 AND MANY ROM THERE IS NO VOLTE ENABLED NOW I TRY AVERY POSSIBLE METHOD BUT FAILED ... I TRY FASTBOOT FLASH 5.1 MIUI OFFICIAL AND DEV ROM STILL THERE IS NO VOLTE SIGN ON STATUS BAR.......SETTINGS SHOW VOLTE ENABLE BUT WHEN I MAKE A CALL its ended please need
an urgents help i also try lollipop firmware no still no volte with with roms and with miui 5.1 also
please help devs in big trouble
thank you ....
shantanu mishra said:
HEY THERE THIA S IS SHANTANU MISHRA ..
I NEED AN URGENT HELP REGARDING VOLTE ISSUE
FROM LAST 3-4 MONTH I AM USING ROM AND MIUI DEV ROMS VOLTE WORKS GREAT BUT AFTER FKNG LAG I MAKE A DECISION TO INSTALL A NEW ROM THT IS CM13 . I DOWNLOAD THE ROM AND GOING FOR ISNTALL IT I DO WIPE SYSTEM ,ARCHE ,DATA ,INTERNAL FULL WIPE AND THEN INSTALL A ROM ITS GIVING ME AN ERROR NO SYSTEM IMAGE .. THN I FLASH FASTBOOT 4.4 KITKAT MIUI OFFICIAL AND THEN INSTALL 3.0.2.0 RECOVERY AND FLASH CM13 MOKEE 7.1.1 MOKEE 6.0 AND MANY ROM THERE IS NO VOLTE ENABLED NOW I TRY AVERY POSSIBLE METHOD BUT FAILED ... I TRY FASTBOOT FLASH 5.1 MIUI OFFICIAL AND DEV ROM STILL THERE IS NO VOLTE SIGN ON STATUS BAR.......SETTINGS SHOW VOLTE ENABLE BUT WHEN I MAKE A CALL its ended please need
an urgents help i also try lollipop firmware no still no volte with with roms and with miui 5.1 also
please help devs in big trouble
thank you ....
Click to expand...
Click to collapse
to enable volte you need to flash miui8 redmi2 prime rom on your device...then flash latest twrp and try any custom roms
flash this rom https://forum.xda-developers.com/redmi-2/development/rom-aospextended-rom-v1-1-t3486744
AKHILR4J said:
to enable volte you need to flash miui8 redmi2 prime rom on your device...then flash latest twrp and try any custom roms
Click to expand...
Click to collapse
YES BROTHER I already flash 2 miui 8 lollipop boatloader rom still no volte please suggset something different thank you
abhishek227 said:
flash this rom https://.xda-.com/redmi-2/development/rom-aospextended-rom-v1-1-t3486744
Click to expand...
Click to collapse
i flash cm14 mokee 7.1.1 volte is not working and this rom is also based on 7.1.1 means same problem m gonna face dam sure
anyways thank your for the reply
did you try flashing firmware(28mb) in lineage os thread via twrp ? everything else working fine ?
after flashing miui8 lolipop rom did you get volte there ?
try this rom
hey buddy flash miui custom rom. miui hellas it has volte inbuilt nice rom no bug& issue try it buddy...wipe all and flash through twrp.
link= https://www.androidfilehost.com/?fid=529152257862716724 forredmi2/prime
AKHILR4J said:
did you try flashing firmware(28mb) in lineage os thread via twrp ? everything else working fine ?
after flashing miui8 lolipop rom did you get volte there ?
Click to expand...
Click to collapse
no volte after flashing and no i didnt flash any 28mb firmware in lineage os thread........ everything work fine only volte sucks thank for the reply brother
saifuk said:
hey buddy flash miui custom rom. miui hellas it has volte inbuilt nice rom no bug& issue try it buddy...wipe all and flash through twrp.
link= https://www.filehost.com/?fid=529152257862716724 forredmi2/prime
Click to expand...
Click to collapse
yes before this volte issue i flash this n volte works but after full wiping and flashing this rom the givme the error no system image then i flash miui 5.1 lp rom via fastboot and thn flash this hellus via twrp still no volte
thank you for the reply
there is firmware in lineage os thread...flash it via twrp(latest) it's just 28mb file that include modem etc..flash that and flash any custom rom after that...then check for volte
may be it will help you
AKHILR4J said:
there is firmware in lineage os thread...flash it via twrp(latest) it's just 28mb file that include modem etc..flash that and flash any custom rom after that...then check for volte
may be it will help you
Click to expand...
Click to collapse
can u please LINK ME this zip for download
flash this.... https://goo.gl/FNbbMP
AKHILR4J said:
flash this.... https://goo.gl/FNbbMP
Click to expand...
Click to collapse
what to wipe before flashing the zip ??? a full wipe
or leave wipe with leaving system
The best solution is here☺☺☺
I face this problem more then 100 time
Step 1~ go to twrp.
Step 2~Advance wipe wipe all except sd card
Step 3~Boot into fastboot
Step 4~flash miui 7 via mi flash tool
Step 5~after the device reboot to system choose updater and choose update file of miui 8
AFTER ALL THIS VOLTE WORKS 100% :good::good:
sagar515 said:
I face this problem more then 100 time
Step 1~ go to twrp.
Step 2~Advance wipe wipe all except sd card
Step 3~Boot into fastboot
Step 4~flash miui 7 via mi flash tool
Step 5~after the device reboot to system choose updater and choose update file of miui 8
AFTER ALL THIS VOLTE WORKS 100% :good::good:
Click to expand...
Click to collapse
thanks for the reply which miui 7 version ? u r telling about and will fastboot miui 7 method not working here?
shantanu mishra said:
thanks for the reply which miui 7 version ? u r telling about and will fastboot miui 7 method not working here?
Click to expand...
Click to collapse
Bro flash miui7.5 via mi flash tool
And checked out my method........
if u dont get volte still try to create a apn and its name as ims,u can see hd sign in custom rom or volte symbol in miui rom
Ok , so here is the solution working 100% guarranted.
1) install fastboot rom via mi flash of redmi 2 .
2) after installing this download recovery rom (not fastboot rom) of redmi 2 prime (miui8 / latest) and place it inside internal/ external memory.
3) go to updater app and choose update pack (recovery rom of redmi 2 prime).
4)after installing it, install twrp and then clean flash any rom.
and Boooooommmmm u get VOLTE , no need to install any jio calling app.
just me i am using it and working for me , every time i try it.
shantanu mishra said:
HEY THERE THIA S IS SHANTANU MISHRA ..
I NEED AN URGENT HELP REGARDING VOLTE ISSUE
FROM LAST 3-4 MONTH I AM USING ROM AND MIUI DEV ROMS VOLTE WORKS GREAT BUT AFTER FKNG LAG I MAKE A DECISION TO INSTALL A NEW ROM THT IS CM13 . I DOWNLOAD THE ROM AND GOING FOR ISNTALL IT I DO WIPE SYSTEM ,ARCHE ,DATA ,INTERNAL FULL WIPE AND THEN INSTALL A ROM ITS GIVING ME AN ERROR NO SYSTEM IMAGE .. THN I FLASH FASTBOOT 4.4 KITKAT MIUI OFFICIAL AND THEN INSTALL 3.0.2.0 RECOVERY AND FLASH CM13 MOKEE 7.1.1 MOKEE 6.0 AND MANY ROM THERE IS NO VOLTE ENABLED NOW I TRY AVERY POSSIBLE METHOD BUT FAILED ... I TRY FASTBOOT FLASH 5.1 MIUI OFFICIAL AND DEV ROM STILL THERE IS NO VOLTE SIGN ON STATUS BAR.......SETTINGS SHOW VOLTE ENABLE BUT WHEN I MAKE A CALL its ended please need
an urgents help i also try lollipop firmware no still no volte with with roms and with miui 5.1 also
please help devs in big trouble
thank you ....
Click to expand...
Click to collapse
which rom you are on now?
adithbalan said:
which rom you are on now?
Click to expand...
Click to collapse
If you want volte then again fastboot the ROM, after that download recovery ROM of redmi 2 prime and then open updater app and choose above file and update. Now again install twrp and custom ROM, I will suggest aosp extended, RR os or validus in performance. You will get volte.
hey there,
I m using RR(resurrection remix) from years and i know much about flashing and stuff but today i got to know that there was RR OS android 9 available in moto g5 plus so i flashed the rom by wiping dalvik cache,cache,system,data and storage as well and then i flashed gapps and i got an error code 64 which said that i have to use ARM64 not ARM for my device so i again did everything and then flashed gapps 9.0 ARM64 and it was complete and my device booted successfully but when i was setting up password/pattern i came to know that there was no option of setting up fingerprint but it did have fingerprint gesture options in settings -> resurrection tools. please help me for solving this problem.
THANK YOU!!!
vritansh said:
hey there,
I m using RR(resurrection remix) from years and i know much about flashing and stuff but today i got to know that there was RR OS android 9 available in moto g5 plus so i flashed the rom by wiping dalvik cache,cache,system,data and storage as well and then i flashed gapps and i got an error code 64 which said that i have to use ARM64 not ARM for my device so i again did everything and then flashed gapps 9.0 ARM64 and it was complete and my device booted successfully but when i was setting up password/pattern i came to know that there was no option of setting up fingerprint but it did have fingerprint gesture options in settings -> resurrection tools. please help me for solving this problem.
THANK YOU!!!
Click to expand...
Click to collapse
Flash firmware update zip from the arrowos forum that should do it.
debdeep98 said:
Flash firmware update zip from the arrowos forum that should do it.
Click to expand...
Click to collapse
you are telling me to flash arrow OS?
vritansh said:
you are telling me to flash arrow OS?
Click to expand...
Click to collapse
Nope. There is a file. Firmware-upgrade.zip. something like that. Flashing that would work if you had nougat as base instead of oreo.
debdeep98 said:
Nope. There is a file. Firmware-upgrade.zip. something like that. Flashing that would work if you had nougat as base instead of oreo.
Click to expand...
Click to collapse
i am on android pie so i have to downgrade and flash it and upgrade back?.....or shall i try flashing directly?.... and i cannot find that zip file if you have the link than send it
vritansh said:
i am on android pie so i have to downgrade and flash it and upgrade back?.....or shall i try flashing directly?.... and i cannot find that zip file if you have the link than send it
Click to expand...
Click to collapse
Flash directly. IF it doesn't work then go back to nougat then flash stock twrp oreo and then RR7.0
https://androidfilehost.com/?fid=1322778262904029635
debdeep98 said:
Flash directly. IF it doesn't work then go back to nougat then flash stock twrp oreo and then RR7.0
https://androidfilehost.com/?fid=1322778262904029635
Click to expand...
Click to collapse
thank you very much its fixed by flashing that zip on RR7.....thanks man
works on xt1680
works on xt1680
Flash the 8.1 firmware. (recommended) Check XDA, you'll get it.
otherwise you can flash a zip which will enable the fingerprint sensor but you won't get nfc.
Best option is to flash the 8.1 firmware update, make sure to uncheck erase EFS.
After sucessfully flashing it, flash any custom rom of your choice.
I've been using for a couple of months a M12 A11 Rom from a Greek forum. Last time I tried (2 months ago), I couldn't get my phone to boot when I flashed an AOSP rom like Lineage. I tried 2 different roms with the same results. What can I do to fix that? I used Orange Recovery R11.0.
Download firmware Miui 11 for fastboot flash via Miflash tool
jastonas said:
I've been using for a couple of months a M12 A11 Rom from a Greek forum. Last time I tried (2 months ago), I couldn't get my phone to boot when I flashed an AOSP rom like Lineage. I tried 2 different roms with the same results. What can I do to fix that? I used Orange Recovery R11.0.
Click to expand...
Click to collapse
After clean fleash without block
Clean all
Flesh mitools
Flesh orange fox r11 stable recovery
1. Update latest firmware Q via recovery global version
After instal aosp ROMs
jastonas said:
I've been using for a couple of months a M12 A11 Rom from a Greek forum. Last time I tried (2 months ago), I couldn't get my phone to boot when I flashed an AOSP rom like Lineage. I tried 2 different roms with the same results. What can I do to fix that? I used Orange Recovery R11.0.
Click to expand...
Click to collapse
flash last fw in rom chanel after reset recovery and flash rom
denis0690 said:
After clean fleash without block
Clean all
Flesh mitools
Flesh orange fox r11 stable recovery
1. Update latest firmware Q via recovery global version
After instal aosp ROMs
Click to expand...
Click to collapse
okankayci said:
flash last fw in rom chanel after reset recovery and flash rom
Click to expand...
Click to collapse
Is this the right one? https://xiaomifirmwareupdater.com/miui/lavender/stable/V11.0.1.0.QFGMIXM/
First download global miui 11 for fastboot.
Flash via miflashtol with clean all.
After install twrp Orange fox r11stable
Wipe all
Format data
Reboot recovery
Install rom aosp
Instal magisk
Reboot
After all this time, still can't get it to work. I've flashed MIUI 11.0.1 Stable, but amy aosp rom I tried installing, even after 20 or more wouldn't boot.