hi, i am on rooted lineage os Nogut theme on my k5, few hours ago I installed substratum engine and tested a light blue and white theme, but after i removed the theme phone goes into reboot and stuck on lienage boot logo, i can access recovery via volume and power key but i dont want to lose my data, but deleting all system/app/data, is there any way around to solve it, i tried a dirty flash of lineage but problem is still the same. its my main phone so i am kind of hopeless without it
Also deleted substratum files via file manager in twrp, but still no luck.
neteater said:
hi, i am on rooted lineage os Nogut theme on my k5, few hours ago I installed substratum engine and tested a light blue and white theme, but after i removed the theme phone goes into reboot and stuck on lienage boot logo, i can access recovery via volume and power key but i dont want to lose my data, but deleting all system/app/data, is there any way around to solve it, i tried a dirty flash of lineage but problem is still the same. its my main phone so i am kind of hopeless without it
Also deleted substratum files via file manager in twrp, but still no luck.
Click to expand...
Click to collapse
You had to flash substratum rescue.zip, but now I'm not sure you can repair it like. Just try it, it don't cost a dime.
nlooooo said:
You had to flash substratum rescue.zip, but now I'm not sure you can repair it like. Just try it, it don't cost a dime.
Click to expand...
Click to collapse
I didnt know about that, have flashed my phone, but to my surprise all the data was saved.
neteater said:
I didnt know about that, have flashed my phone, but to my surprise all the data was saved.
Click to expand...
Click to collapse
Next time try to read more about the stuff that you use.
Related
Hello everyone, so the other day i went out to sell my Xperia S and when i went to seal the deal i literally could not do the factory reset. I went into the menu, started it, it rebooted and it ended up on a black screen after "rebooting" with the blue light on indefinitely. If i hard reseted it, my google account and settings were still in it. Tried to log into recovery, and the effect is the same, blue led on black screen but nothing else, and same effect from the Android device manager.
Since Sony update service is not supported it exits(it always worked with that before) and the PC companion tells me im running custom rom, and exiting instead of flashing the factory image...
I tried to reflash the recovery through adb but no success.
I'm running the unofficial PA 4.6 beta from this forum, and had the TWRP-CWM dual recovery(which looked like has been rewrote to be CWM purely by the PA OTAs)
So any ideas what i can do? In this form, whit all the data on it, I can't even give it away for free, not to mention asking money for it...
TheGregButcher said:
Hello everyone, so the other day i went out to sell my Xperia S and when i went to seal the deal i literally could not do the factory reset. I went into the menu, started it, it rebooted and it ended up on a black screen after "rebooting" with the blue light on indefinitely. If i hard reseted it, my google account and settings were still in it. Tried to log into recovery, and the effect is the same, blue led on black screen but nothing else, and same effect from the Android device manager.
Since Sony update service is not supported it exits(it always worked with that before) and the PC companion tells me im running custom rom, and exiting instead of flashing the factory image...
I tried to reflash the recovery through adb but no success.
I'm running the unofficial PA 4.6 beta from this forum, and had the TWRP-CWM dual recovery(which looked like has been rewrote to be CWM purely by the PA OTAs)
So any ideas what i can do? In this form, whit all the data on it, I can't even give it away for free, not to mention asking money for it...
Click to expand...
Click to collapse
Did You try flashing a stock ftf using flashtool?
The problem is that it doesn't even get into recovery, like I said I reboot into recovery and it drops me on a black screen (lit) with the blue led on, but neither cwm not twrp comes in and it just idles there indefinitely.
Mirhawk said:
Did You try flashing a stock ftf using flashtool?
Click to expand...
Click to collapse
Disregard my first reply, I totally missed your point on it... Will try flash tool tomorrow!
I got my ZUK Z2 Plus For like 3 days and I unlocked the boot loader and flashed twrp, Now as soon as I install any custom ROM it and boots into it I dont know wtf is going on my phone heats up so much and then in the middle of the setup it goes off with the led light powered on I tried installing stock rom and this things didn't happens on it.
I flashed RR, Bootleggers, AEX and others and after all this madness the phone doesn't stay cool it heats up so much that its screen goes off and led is on
Hep me guys
mdzaibsk said:
I got my ZUK Z2 Plus For like 3 days and I unlocked the boot loader and flashed twrp, Now as soon as I install any custom ROM it and boots into it I dont know wtf is going on my phone heats up so much and then in the middle of the setup it goes off with the led light powered on I tried installing stock rom and this things didn't happens on it.
I flashed RR, Bootleggers, AEX and others and after all this madness the phone doesn't stay cool it heats up so much that its screen goes off and led is on
Hep me guys
Click to expand...
Click to collapse
First
Flash zui 3.5.337 ig its latest and u can get that flashing method in guid section
After that again unlock bootloader and try
This time take backup of ur current rom so u need not to have flash stcok again
...
I am getting an error while flashing bootleggers rom sometimes it says error 7 and sometimes zip file is corrupt. I have tried using the unzipping zip file and deleting the assert section from the update script it but it doesnt work out. Need serious help
Vento001 said:
I am getting an error while flashing bootleggers rom sometimes it says error 7 and sometimes zip file is corrupt. I have tried using the unzipping zip file and deleting the assert section from the update script it but it doesnt work out. Need serious help
Click to expand...
Click to collapse
Not sure, but have you checked this thread?
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/z2plus-treble-roms-flashing-reverting-t3778287
Make sure to flash right files based on which type of ROM you are selecting to install.
Different setup required for treble and non treble ROM
mdzaibsk said:
I got my ZUK Z2 Plus For like 3 days and I unlocked the boot loader and flashed twrp, Now as soon as I install any custom ROM it and boots into it I dont know wtf is going on my phone heats up so much and then in the middle of the setup it goes off with the led light powered on I tried installing stock rom and this things didn't happens on it.
I flashed RR, Bootleggers, AEX and others and after all this madness the phone doesn't stay cool it heats up so much that its screen goes off and led is on
Hep me guys
Click to expand...
Click to collapse
Is there any case that you are not doing a clean flash? (While in twrp, "wipe"-> "advanced wipe"-> check system-davlik-cache-data-> swipe) ??
Bro,
Flash zui 1.9 (Chinese version) using mi flash tool or qpst.
The problem will probably be solved.
Then again try unlocking bootloader and flash twrp.
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.
A couple of days ago my phone started crashing randomly, so I decided to deactivate all my Magisk packages which seemed to fix the issue, but the next day it crashed again and it wouldn't go past the boot screen anymore. It crashes the moment the three little white boot up dots appear on the screen, so I decided to clear all the data through TWRP and flash a stock rom all over again. All seemed fine until I tried to install TWRP and root the rom. My phone is now stuck constantly crashing on the boot up screen no matter what I do. Does anyone have any advice? Thanks.
JimmyWhiskers said:
A couple of days ago my phone started crashing randomly, so I decided to deactivate all my Magisk packages which seemed to fix the issue, but the next day it crashed again and it wouldn't go past the boot screen anymore. It crashes the moment the three little white boot up dots appear on the screen, so I decided to clear all the data through TWRP and flash a stock rom all over again. All seemed fine until I tried to install TWRP and root the rom. My phone is now stuck constantly crashing on the boot up screen no matter what I do. Does anyone have any advice? Thanks.
Click to expand...
Click to collapse
Try FORMAT data option under twrp and go to advance and repair all the partition. Restart recovery then flash custom rom. Xiaomi eu. Let see if it got stuck again or not..
kraken77 said:
Try FORMAT data option under twrp and go to advance and repair all the partition. Restart recovery then flash custom rom. Xiaomi eu. Let see if it got stuck again or not..
Click to expand...
Click to collapse
I've tried that and it doesn't seem to do anything. I've formatted all data and even repaired the partitions. Nothing seems to work.
JimmyWhiskers said:
I've tried that and it doesn't seem to do anything. I've formatted all data and even repaired the partitions. Nothing seems to work.
Click to expand...
Click to collapse
Did you format and type yes before formatting?
any success??
kraken77 said:
Try FORMAT data option under twrp and go to advance and repair all the partition. Restart recovery then flash custom rom. Xiaomi eu. Let see if it got stuck again or not..
Click to expand...
Click to collapse
What is with flashing xiaomi eu specifically? Shouldn't any custom rom work?
rtm2000 said:
What is with flashing xiaomi eu specifically? Shouldn't any custom rom work?
Click to expand...
Click to collapse
Nothing serious actually but to troubleshoot and to see if 'stock rom' causes that problem rather than 'custom rom'.. but its okay if you want to use custom rom.
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.