Develop Bugs

No reaction after flashing CustomROM and Rebooting

Hello,
I flashed a CustomROM and gapps, tried to reboot into system, but my phone does not react anymore since that attempt. The screen is black.
ROM: http://forum.xda-developers.com/mi-max/development/rom-cm13-unoficial-2016-06-14-universal-t3473016
Gapps: core package from 07-16-16 (arm)
Is there a way to recover it?

Tsd560ti said:
Hello,
I flashed a CustomROM and gapps, tried to reboot into system, but my phone does not react anymore since that attempt. The screen is black.
ROM: http://forum.xda-developers.com/mi-max/development/rom-cm13-unoficial-2016-06-14-universal-t3473016
Gapps: core package from 07-16-16 (arm)
Is there a way to recover it?
Click to expand...
Click to collapse
You have hydrogen or helium?
Which TWRP image did you install exactly?

My device is a Helium 64-3GB bought in China (June/16)
Recovery was flashed using Flasher Toolkit from "en.miui.com" -> /thread-301971-1-1.html
(Link not allowed)
file name: "twrp-3.0.2-2-hydrogen"
I remember that I might have seen Hydrogen in the text box during installation, if you aim on the detection during the installation.

Tsd560ti said:
My device is a Helium 64-3GB bought in China (June/16)
Recovery was flashed using Flasher Toolkit from "en.miui.com" -> /thread-301971-1-1.html
(Link not allowed)
file name: "twrp-3.0.2-2-hydrogen"
I remember that I might have seen Hydrogen in the text box during installation, if you aim on the detection during the installation.
Click to expand...
Click to collapse
Yeah... Wrong recovery and the install detected your helium as hydrogen leaving you a brick.
My bad... I just added the warning about that in the thread after seeing your question... Should of thought about this scenario but since we have helium twrp for a long time now I I assumed nobody is isuing hidrogen... I knew what you did just wanted to make sure.
Never been in a brick myself but read this thread and you should be back booting in no time
http://forum.xda-developers.com/mi-max/how-to/guide-install-global-miui8-root-t3435594
And install proper twrp, please... or you won't be able to install any helium rom.

The device gets recognized in MiFlash, but after flashing the twrp and the stock rom, the device still does not boot.
Any proposes on my mistake?
EDIT: I just started the procedure again, unplugged the battery, connected the "jumper" and the phone booted properly.
After some failed reboots, it randomly booted into TWRP (now the right one, at least i hope so. gonna check this later) and I installed the latest RR (love the design).
So now, its just the ugly 3G-bug left and a little OC would be nice

Tsd560ti said:
The device gets recognized in MiFlash, but after flashing the twrp and the stock rom, the device still does not boot.
Any proposes on my mistake?
EDIT: I just started the procedure again, unplugged the battery, connected the "jumper" and the phone booted properly.
After some failed reboots, it randomly booted into TWRP (now the right one, at least i hope so. gonna check this later) and I installed the latest RR (love the design).
So now, its just the ugly 3G-bug left and a little OC would be nice
Click to expand...
Click to collapse
Great job:good:

Android A1(AQ4501) Dead :(

I own a canvas A1 4GB variant, I had rooted my phone and flashed custom recovery(everything was finee), After a while my phone's battery started giving me problems(lasted only few hours), I considered flashing Stock ROM or any other trusted ROM, I had flashed RR M[07/07] based on android MM, The battery was still giving problem, A week later, My mom's phone broke and she had to use this(A1) temporarily, I formatted everything and thought of flashing stock ROM and handing over the phone to her, I tried flashing the official zip via TWRP, It gave me some error regarding unable to mount system, System partions or something(I don't remember). And after that, I could't flash any ROM, I tweaked some settings in TWRP and now my phone is totally dead, It does not boot up at all, No recovery mode turns on, Nothing except a black dead screen, I tried flashing stock firmware via SP flash tool, It completes and says successful but still nothing happens, Just wanna know if something can happen to this one? I really loved that device and would be great to have it back working.

Flash correct stock firmware in sptools

arunassain said:
Flash correct stock firmware in sptools
Click to expand...
Click to collapse
doesn't work. I have tried various STOCK Roms on mine but didnt work. Please post a link if possible which u think works.

Cannot root my S9

Hi everyone,
this is crazy. I followed different guides on how to root my phone but I get the idea I really have to wait for 7 days to have another chance at rooting, or is this just a myth?
I installed twrp, flashed resurrection remix. I had problems with my camera when trying to record video. I always got green flickering on screen. also not able to record more than 60fps (why? isn't s9 supposed to?).
But what struck me most was the fact that my phone wasn't rooted. When installing supersu in the recovery I get the message "sepolicy failed" or something. I guess this is why I cannot root my phone? Installing superuser from the playstore shows me also that I am indeed not rooted.
What can I do? I am all out of ideas and websites...
Should I reflash stock and do the OEM and odin procedure again, and wait 7 days?

Nairozed said:
Hi everyone,
this is crazy. I followed different guides on how to root my phone but I get the idea I really have to wait for 7 days to have another chance at rooting, or is this just a myth?
I installed twrp, flashed resurrection remix. I had problems with my camera when trying to record video. I always got green flickering on screen. also not able to record more than 60fps (why? isn't s9 supposed to?).
But what struck me most was the fact that my phone wasn't rooted. When installing supersu in the recovery I get the message "sepolicy failed" or something. I guess this is why I cannot root my phone? Installing superuser from the playstore shows me also that I am indeed not rooted.
What can I do? I am all out of ideas and websites...
Should I reflash stock and do the OEM and odin procedure again, and wait 7 days?
Click to expand...
Click to collapse
Try use magisk 16.6 for root issues, ofc when you use custom rom you dont get full camera potential and these green flickers are just minor cosmic bugs.

"Myth" might want to read up more.
You need to flash twrp and flash the no verity file then flash the custom rom
Or even better, flash soldiers rom instead of the resurrection remix. Didnt you read that theres a camera problem?
Better use magisk for rooting btw, use the 16.6

Now I am in a never ending boot sequence loading resurrection remix. I can only hard reset and enter twrp.
I don't know if the installation or magisk did it, because I cannot boot to the system.
anyideas?

Nairozed said:
Now I am in a never ending boot sequence loading resurrection remix. I can only hard reset and enter twrp.
I don't know if the installation or magisk did it, because I cannot boot to the system.
anyideas?
Click to expand...
Click to collapse
try flash rom + gapps and boot system after that boot recovery and flash magisk 16.6 and boot system

Thanks for the advice. I flashed back to stock firmware to have the zerocam mod working perfectly. But now my lockscreen freezes after a few minutes. So I tried to deactivate my phone going into lockscreen. I get the Black screen of Death now instead when the display turns off into sleep mode. Only way out is rebootingby hard reset, power button+volume down.
What can I do?.... Thanks for Any further advice.

Error 7 vendor clash when flashing custom rom

Hi guys. Just looking for a bit of assistance. I unlocked the bootloader and installed twrp. Booted into twrp and tried to flash the rom. While it was flashing, the screen was showing an error 7 showing the vendor as my old phone, a Zuk 2 plus. Flashed Miui 10 back on for the time being. Do I have to install or flash a specific image to the phone to install the custom rom?

In the past I also got same error, just try Orange fox recovery

I'll have a look at that when I get a chance. Also been told I might have to update the firmware. Thanks for the reply! ?

Oops, I also forgot I used this firmware https://github.com/XiaomiFirmwareUp...n_miui_MIMIX2Global_9.1.24_33b7dc74ff_8.0.zip
With this one error 7 also seems to disappear

Thanks for the link, I will give it a go tomorrow. I'll see how it goes! ?

UNABLE TO BOOT ANY ROM AFTER LATEST GApps INSTALLATION

Hi people,
Today I unlocked my Lenovo ZUK Z2 Plus and installed latest twrp recovery 3.3.1 successfully(no errors until now, butter smooth). After that I flashed "CARBON-CR-7.0-OPAL-RELEASE-z2_plus-20200122-0608" without installing GApps. This time the ROM booted successfully. I was able to use the phone and make calls.
Then I installed the GApps " open_gapps-arm64-9.0-stock-20200131.zip" downloaded from OpenGApps.org. This time around, when I booted after installing GApps, the phone showed the welcome screen, but got suddenly turned off. After that the phone just shows ZUK logo and keeps rebooting.
To fix this, I went to recovery again, wiped clean DATA & DALVIK CACHE & CACHE & SYSTEM & VENDOR partitions, hoping I would start from the beginning and again install only ROM and not GApps and hoping I would be able to use the phone.
Now this time around, even though I wiped every partition that TWRP shows, the phone just kept rebooting without starting Android OS. So I cleaned again everything using TWRP(cleaning DATA procedure) and then transferred ROM zip files to phone and again flashed only ROM. Still the phone kept rebooting.
Now I got pissed off. I flashed factory ROM using QFIL method. This time after the boot animation it went straight to "Shutting Down" dialogue and again the phone restarted.
CAN SOMEBODY TELL ME WHAT THE HELL IS EXACTLY WRONG WITH MY PHONE?
WHAT COULD HAVE GONE WRONG THAT EVEN AFTER CLEANING ALL THE PARTITIONS AND FLASHING USING THE FACTORY PROCEDURE, THE PHONE STILL KEEPS REBOOTING?
Is there any other partition that needs to be cleared(which the TWRP does not list)?
Can somebody just tell me how to get out of this?
(Please explain the steps and the reason for each, as I am a noob in this matter).
WAITING FOR ANYBODY'S PROMPT RESPONSE AS MY PHONE IS COMPLETELY UNUSABLE. THANKS IN ADVANCE.

what ZUI version you flashed with QFIL ?

AndroidUser5 said:
Hi people,
Today I unlocked my Lenovo ZUK Z2 Plus and installed latest twrp recovery 3.3.1 successfully(no errors until now, butter smooth). After that I flashed "CARBON-CR-7.0-OPAL-RELEASE-z2_plus-20200122-0608" without installing GApps. This time the ROM booted successfully. I was able to use the phone and make calls.
Then I installed the GApps " open_gapps-arm64-9.0-stock-20200131.zip" downloaded from OpenGApps.org. This time around, when I booted after installing GApps, the phone showed the welcome screen, but got suddenly turned off. After that the phone just shows ZUK logo and keeps rebooting.
To fix this, I went to recovery again, wiped clean DATA & DALVIK CACHE & CACHE & SYSTEM & VENDOR partitions, hoping I would start from the beginning and again install only ROM and not GApps and hoping I would be able to use the phone.
Now this time around, even though I wiped every partition that TWRP shows, the phone just kept rebooting without starting Android OS. So I cleaned again everything using TWRP(cleaning DATA procedure) and then transferred ROM zip files to phone and again flashed only ROM. Still the phone kept rebooting.
Now I got pissed off. I flashed factory ROM using QFIL method. This time after the boot animation it went straight to "Shutting Down" dialogue and again the phone restarted.
CAN SOMEBODY TELL ME WHAT THE HELL IS EXACTLY WRONG WITH MY PHONE?
WHAT COULD HAVE GONE WRONG THAT EVEN AFTER CLEANING ALL THE PARTITIONS AND FLASHING USING THE FACTORY PROCEDURE, THE PHONE STILL KEEPS REBOOTING?
Is there any other partition that needs to be cleared(which the TWRP does not list)?
Can somebody just tell me how to get out of this?
(Please explain the steps and the reason for each, as I am a noob in this matter).
WAITING FOR ANYBODY'S PROMPT RESPONSE AS MY PHONE IS COMPLETELY UNUSABLE. THANKS IN ADVANCE.
Click to expand...
Click to collapse
Greetings buddy,
For my interest, i would like to know that the carbon rom u flashed was based on Android 9 or Android 10????

arielcasari said:
what ZUI version you flashed with QFIL ?
Click to expand...
Click to collapse
zui 2.5 st which is meant for indian users.

Naresh Rawat said:
Greetings buddy,
For my interest, i would like to know that the carbon rom u flashed was based on Android 9 or Android 10????
Click to expand...
Click to collapse
android 9.0.
what could be the problem... what do you think?

AndroidUser5 said:
android 9.0.
what could be the problem... what do you think?
Click to expand...
Click to collapse
I m at job so i reply late. No offense please ???
Ok plz let me know that if ur device boots up to fastboot mode. If yes then repeat the whole process but this time try installing different twrp. U can also use (https://www.androidfilehost.com/?a=show&w=files&flid=38683) tool kit for flashing. (DO NOT TRY TO RELOCK BOOTLOADER USING THIS TOOL) Also use flame gapps.
Will catch u soon regarding ur issue.
Peace out n TY???

Naresh Rawat said:
I m at job so i reply late. No offense please
Ok plz let me know that if ur device boots up to fastboot mode. If yes then repeat the whole process but this time try installing different twrp. U can also use (https://www.androidfilehost.com/?a=show&w=files&flid=38683) tool kit for flashing. (DO NOT TRY TO RELOCK BOOTLOADER USING THIS TOOL) Also use flame gapps.
Will catch u soon regarding ur issue.
Peace out n TY
Click to expand...
Click to collapse
i have already tried using twrp 3.2, but no luck. I will try flame gapps and will let you know. i will try this coming saturday.
Dhanyavad.

Naresh Rawat said:
I m at job so i reply late. No offense please
Ok plz let me know that if ur device boots up to fastboot mode. If yes then repeat the whole process but this time try installing different twrp. U can also use (https://www.androidfilehost.com/?a=show&w=files&flid=38683) tool kit for flashing. (DO NOT TRY TO RELOCK BOOTLOADER USING THIS TOOL) Also use flame gapps.
Will catch u soon regarding ur issue.
Peace out n TY
Click to expand...
Click to collapse
I again flashed the Stock ZUI 2.5. ST ROM using QFIL. But before doing this I had moved the SIM Card to another fone, so this fone was without any connection. This time the fone booted up successfully. Then I reflashed the Carbon ROM mentioned before and flashed Flame GApps Basic edition as suggested by you. This time the fone booted up successfully. But as soon as I connected the fone to internet, it downloaded something from Google Play Services in the background and again it started the same problem.
SO BASICALLY WHEN IT DOWNLOADS SOMETHING FROM GOOGLE IN BACKGROUND, IT STARTS THE REBOOTING NONSENSE.
I searched the internet for this and some articles on the internet suggested that "Google Dialer" component is causing reboot. Those articles suggested that if the "Google Dialer" is not set as the default dialer, it reboots. BUT HOW TO SET IT AS DEFAULT, WHEN IT STARTS REBOOTING IMMEDIATELY AND IT DOES NOT GIVE ENOUGH TIME?
EVEN THE EARLIER GApps 9.0 stock package that I flashed had warned to set the "Google Dialer" as default, but upon boot up it kept rebooting.
Even initially I started this UNLOCKING AND CUSTOM ROM FLASHING exercise after the factory ROM started rebooting after updating "Google play services".
So this seems to me an issue from Google.
Has Google done this on purpose to make people switch older phones to new ones?(Because I own a total of 3 android devices and only this device is rebooting not the other ones).
Looking forward to your reply.

Greetings Buddy..how's life going??
Ok once again I hv read ur op regarding ur problems. Let's start from the beginning. Boot up to twrp and format the data first before wiping everything. Try flashing lineageOS 16 using official gapps. (Flash gapps along with the flashing ROM, same time. Because flashing gapps after ROM's 1st reboot may result synchronise error or sometime bootloop). If successful, then flash ur carbon ROM and see whether it boots up to normal or still gives such error.
BTW sorry for my late replies. Till then peace out

Naresh Rawat said:
Greetings Buddy..how's life going??
Ok once again I hv read ur op regarding ur problems. Let's start from the beginning. Boot up to twrp and format the data first before wiping everything. Try flashing lineageOS 16 using official gapps. (Flash gapps along with the flashing ROM, same time. Because flashing gapps after ROM's 1st reboot may result synchronise error or sometime bootloop). If successful, then flash ur carbon ROM and see whether it boots up to normal or still gives such error.
BTW sorry for my late replies. Till then peace out
Click to expand...
Click to collapse
I am now not able to boot any ROM. Just keeps rebooting after the ZUK splashscreen. Hence, I again reflashed the Recovery properly, using the procedure as before. Now I am not able to boot into the recivery, too.