I was wondering if anyone tried installing a GSI Rom on this phone since the phone can have an unlocked bootloader and meets the minimum requirements. There is an android 10 GSI available.
https://www.xda-developers.com/android-10-custom-gsi-project-treble/
I tried a few ROMs, all of them went into "Qualcomm Crashdump Mode"
Maybe I'm not flashing it right, but the post says to just flash it into system...
I've tried:
Flashing GSI system alone
Flashing GSI then flash boot and vendor
Replacing a system img from a fastboot ROM with GSI
All of the flashes ended up with "Qualcomm Crashdump Mode"
maybe I'm doing it wrong...
yeah you missed to format data at 1st through twrp... it's a MUST before GSI flash ! but i can tell you that it's just time wasting... i tried almost all of them.... too many thing don't work really satisfying and/or messed up everything
kanschelskes said:
yeah you missed to format data at 1st through twrp... it's a MUST before GSI flash ! but i can tell you that it's just time wasting... i tried almost all of them.... too many thing don't work really satisfying and/or messed up everything
Click to expand...
Click to collapse
I did wipe data, in fact, I wiped data, cache, system, delvik, boot and storage, everything except my sd card...
threeeye said:
I did wipe data, in fact, I wiped data, cache, system, delvik, boot and storage, everything except my sd card...
Click to expand...
Click to collapse
you wipe or format data? It's not equal!
i told him already in pm
alexeei said:
you wipe or format data? It's not equal!
Click to expand...
Click to collapse
I honestly don't remember, I tried a few times, with a few different ways
So I can't tell for sure if I just wiped, formatted or factory reset... (I had a few beers in me...)
After failing with the GSI, I wanted to go back to the ROM that I was before (a fastboot_11.0.350)
But for some reason it didn't work, so I tried a few more options
After everything failed, I started to think that my phone it bricked, and I'll need to get a new phone...
But I managed to flash a 11.0.350_ST with QPST (first time that I managed to do it successfully)
So now I'm with this ROM, I don't like it so much, but it works...
I hope now you know why I can't remember if I did a wipe or a format...
kanschelskes said:
i told him already in pm
Click to expand...
Click to collapse
I checked my PM, I didn't see any messages...
I'm looking to consider buying this phone, I was surprised about it's price, can someone of you inform about how is GSI working in Z6 Pro? From my point of view no one stated that they're using GSI, after Qualcomm Bootscreen error. Thank you
Enviado desde mi Redmi Note 4 mediante Tapatalk
Marioh2451 said:
I'm looking to consider buying this phone, I was surprised about it's price, can someone of you inform about how is GSI working in Z6 Pro? From my point of view no one stated that they're using GSI, after Qualcomm Bootscreen error. Thank you
Enviado desde mi Redmi Note 4 mediante Tapatalk
Click to expand...
Click to collapse
You can use GSIs as long as your data is unencrypted. I've used many of them. The main issues are fingerprint, media over Bluetooth and DT2W not working so far.
descarao81 said:
You can use GSIs as long as your data is unencrypted. I've used many of them. The main issues are fingerprint, media over Bluetooth and DT2W not working so far.
Click to expand...
Click to collapse
Have these issues been resolved for GSI roms at this time? I'm asking because I'd love to replace the ROM on my K10 note/Z6 youth!
Related
Hello xda community!
I received the nexus 6p christmas and after a few hours playing with it, I unlocked, installed twrp and installed cm13. I then installed ak kernal. My phone installs both fine and runs as normal without any FC. Then this is where it gets weird. When I had my new rom and kernal all set up. I go into TWRP and create a backup. I restart and I'm bootlooping. It tells me my device is corrupt. It did this with the original backup of stock rom, cm13, with and without ak kernal installed... and then sometimes my phone will soft-brick (gets stuxk on google logo) I really love cm engine as I habe a theme. But I'm unsure what is happening to my phone.
Any help is appreciated! - thanks.
Info
Xtra-arrow said:
Hello xda community!
I received the nexus 6p christmas and after a few hours playing with it, I unlocked, installed twrp and installed cm13. I then installed ak kernal. My phone installs both fine and runs as normal without any FC. Then this is where it gets weird. When I had my new rom and kernal all set up. I go into TWRP and create a backup. I restart and I'm bootlooping. It tells me my device is corrupt. It did this with the original backup of stock rom, cm13, with and without ak kernal installed... and then sometimes my phone will soft-brick (gets stuxk on google logo) I really love cm engine as I habe a theme. But I'm unsure what is happening to my phone.
Any help is appreciated! - thanks.
Click to expand...
Click to collapse
Wipe everything > Advance Wipe Phone in recovery
Reinstall CM13 through Recovery and don't flash another kernel
:good:
Geeks Empire said:
Wipe everything > Advance Wipe Phone in recovery
Reinstall CM13 through Recovery and don't flash another kernel
:good:
Click to expand...
Click to collapse
Whoa! Don't tell him to wipe everything in the advanced wipe menu, that'll wipe the internal storage too which is completely unnecessary.
Xtra-arrow said:
Hello xda community!
I received the nexus 6p christmas and after a few hours playing with it, I unlocked, installed twrp and installed cm13. I then installed ak kernal. My phone installs both fine and runs as normal without any FC. Then this is where it gets weird. When I had my new rom and kernal all set up. I go into TWRP and create a backup. I restart and I'm bootlooping. It tells me my device is corrupt. It did this with the original backup of stock rom, cm13, with and without ak kernal installed... and then sometimes my phone will soft-brick (gets stuxk on google logo) I really love cm engine as I habe a theme. But I'm unsure what is happening to my phone.
Any help is appreciated! - thanks.
Click to expand...
Click to collapse
Which partitions are you backing up when creating the nandroid with TWRP?
Heisenberg said:
Which partitions are you backing up when creating the nandroid with TWRP?
Click to expand...
Click to collapse
System, data, boot - Installing the kernel made no difference, the device still corrupted on reboot. and then sometimes at least twice it has soft-bricked
Geeks Empire said:
Wipe everything > Advance Wipe Phone in recovery
Reinstall CM13 through Recovery and don't flash another kernel
:good:
Click to expand...
Click to collapse
Already tried it mate, a number of times. no joy.
Xtra-arrow said:
Hello xda community!
I received the nexus 6p christmas and after a few hours playing with it, I unlocked, installed twrp and installed cm13. I then installed ak kernal. My phone installs both fine and runs as normal without any FC. Then this is where it gets weird. When I had my new rom and kernal all set up. I go into TWRP and create a backup. I restart and I'm bootlooping. It tells me my device is corrupt. It did this with the original backup of stock rom, cm13, with and without ak kernal installed... and then sometimes my phone will soft-brick (gets stuxk on google logo) I really love cm engine as I habe a theme. But I'm unsure what is happening to my phone.
Any help is appreciated! - thanks.
Click to expand...
Click to collapse
The bootloader message won't go away until you lock the bootloader. Its just there as a warning to you in case you did not unlock your phone. As for CM I'm sure there are still many bugs to be worked out. I know I'm going to wait before Flashing it until I see people enjoying it as a daily driver. There are some great devs here in the n6p forums though so I recommend checking out some other ROMs too.
XxMORPHEOUSxX said:
The bootloader message won't go away until you lock the bootloader. Its just there as a warning to you in case you did not unlock your phone. As for CM I'm sure there are still many bugs to be worked out. I know I'm going to wait before Flashing it until I see people enjoying it as a daily driver. There are some great devs here in the n6p forums though so I recommend checking out some other ROMs too.
Click to expand...
Click to collapse
i understand the boot message and CM - i have tried other roms too. i'm not the only one who is getting bootloops on every rom. not sure what to do mate. it says corrupted then boot loops upon restart
Xtra-arrow said:
i understand the boot message and CM - i have tried other roms too. i'm not the only one who is getting bootloops on every rom. not sure what to do mate. it says corrupted then boot loops upon restart
Click to expand...
Click to collapse
Maybe this will be helpful. I think you have the red level warning like this user. Seems like the exact same situation.
http://forum.xda-developers.com/showthread.php?p=64403982
Turns out it isn't bootlooping. Its taking at least 3 minutes to turn on. It looks like bootlooping. BUt if finally loaded. After doing my uninstalling of aomw system apps. Its rebooted and keeps optimising apps. 2-4 then restarts and does same
Info
Heisenberg said:
Whoa! Don't tell him to wipe everything in the advanced wipe menu, that'll wipe the internal storage too which is completely unnecessary.
Click to expand...
Click to collapse
It s necessary to Wipe everything when don't know which modification cause the problem.
+ Recovering the backup also not working for this situation.
@Xtra-arrow
Can u explain step-by-step what u did so far
more detail = better help
:good:
Geeks Empire said:
It s necessary to Wipe everything when don't know which modification cause the problem.
+ Recovering the backup also not working for this situation.
@Xtra-arrow
Can u explain step-by-step what u did so far
more detail = better help
:good:
Click to expand...
Click to collapse
No it isn't necessary to wipe the userdata partition. No modifications are stored in the userdata partition. It would only be necessary to wipe system, data, cache, and dalvik cache. And probably flash the vendor partition too. Not userdata though.
I had a similar problem when I botched a SU flash, same warning then it would take forever to boot, then the rom would degrade over the next several minutes. I know its not fun to start over, but it was the only thing that cleared all the problems. I didn't want to take more time finding another solution when going back to stock is so simple with this device. Follow the instructions in step #11 of Heisenberg's guide (great guide, I link it to friends a lot). Then start again, I know, not what you wanted to hear. Hope this helps!
I am also in agreement with Heisenberg in regards to the userdata partition.
Geeks Empire said:
It s necessary to Wipe everything when don't know which modification cause the problem.
+ Recovering the backup also not working for this situation.
@Xtra-arrow
Can u explain step-by-step what u did so far
more detail = better help
:good:
Click to expand...
Click to collapse
Thank you very much for replying. I have found the root of the cause but no solution. Uninstalling or disabling system apps will cause my phone to go into a "optimising apps" boot loop on the next restart. What do you think? ++ every restore I make on twrp either soft bricks or bootloops. Crazy!
Info
Xtra-arrow said:
Thank you very much for replying. I have found the root of the cause but no solution. Uninstalling or disabling system apps will cause my phone to go into a "optimising apps" boot loop on the next restart. What do you think? ++ every restore I make on twrp either soft bricks or bootloops. Crazy!
Click to expand...
Click to collapse
If you are sure about reason Forget ur Backups.
you should completely install Stock Kernel, Rom, Boot.img >> Back to Stock
But If I remember correctly u did this before...
I just have to say Retry Also Install and use Nexus Root Toolkit
:good:
I have reinstalled original stock files from google. I've wiped everything numerous times. Installed ROMs just after. It took me a while but I think it comes down to the system apps. I'm running a custom ROM, cm13 and my phone is running fine. I know if I was to delete all the unwanted apps off my phone, on next reboot it will try and optimise apps, finish. Says starting apps... Then reboots. Follows the same process.
Xtra-arrow said:
I have reinstalled original stock files from google. I've wiped everything numerous times. Installed ROMs just after. It took me a while but I think it comes down to the system apps. I'm running a custom ROM, cm13 and my phone is running fine. I know if I was to delete all the unwanted apps off my phone, on next reboot it will try and optimise apps, finish. Says starting apps... Then reboots. Follows the same process.
Click to expand...
Click to collapse
Can I ask what gapps are you using? Are you using your google account to recover your apps, or are starting fresh each time?
Sent from my Nexus 6P using Tapatalk
Thanks for your reply. I've actually now narrowed itnright down to a few apps, maybe gapps. Sound recorder, voice recorder app and the google app. Either one or more of these cause my optimising apps bootloop.
Hi folks, first off English is not my main modus operandi so bear with me thx.
I tried out every room there is for the VNS-L31, CM13 from here, Revolution RC3 from a Spanish forum, Beanstalk and a few others what where more glorified reskins ... anyway before installing CM13 I made a full dump on TWRP but wile forgetting I wasn't on stock but on Revolution RC3, so I ended up with the wrong encryption key for the DATA folder, pardon me internal memory SD ... RRC3 is based on the European Stock B150 with a lot of tweaks, also a not perfect encryption of the internal SD similarly to CM13 problem with the SD.
Here is the main beef I am having, after getting of CM I tried to restore my dump and ended up ****ing up the encryption of the internal memory card. Now I can't got back to say the 161 internalional version and I am kinda bound to the European L31900B versions of the stock rom if I install anything else the accounts like Google or Facebook are not working and anything not installed already on the phone is FC.
I can't format data because of the encryption. Not under fastboot or any of the trwps, tried 3 different ones, I checkted the phone is not frp. I did lock frp and bootloader again and unlocked them so to double make sure I was right on that one. I tried going back to stock with the dload method but no dice data still locked. Delete accounts with root explorer and went back to vnsl31900b130 what seams to be the firmware that I am stuck on now with the ****ed up encryption ....
I am used to flashing stuff left and right but this is new land for me any help would be greatly appreciate ... And my warning DONT SCREW WITH TGE ENCRYPTION ON YOUR PHONE ... ITS A *****!!!!
Cant you just delete the system in TWRP?
Thijs van Hal said:
Cant you just delete the system in TWRP?
Click to expand...
Click to collapse
Nope I deleted everything in TWRP, System, Cust, that is not a problem, the data partition on the other hand I can't format not I twrp, or by fastboot erase/format/-w commands ... Really annoying, never had an issue like this ... Funny that I can delete things with an root explorer under Android and that saving data works fine but the moment I leave the os it just closes up. Even the dump I made can't replace the data partition outside of the os
markus2811 said:
Nope I deleted everything in TWRP, System, Cust, that is not a problem, the data partition on the other hand I can't format not I twrp, or by fastboot erase/format/-w commands ... Really annoying, never had an issue like this ... Funny that I can delete things with an root explorer under Android and that saving data works fine but the moment I leave the os it just closes up. Even the dump I made can't replace the data partition outside of the os
Click to expand...
Click to collapse
Ive never seen that before to, weird man...
I have the same issue. Any fix?
Nemeroz said:
I have the same issue. Any fix?
Click to expand...
Click to collapse
No, but I am starting from scratch, also I am trying to manually corrupt the data partition so to be able to format it ... Just a pain, at the moment I am stuck, maybe if I can get someone else's firmware dump for my phone might do the trick its big so I am not sure anyone would upload something that big ... We see
markus2811 said:
No, but I am starting from scratch, also I am trying to manually corrupt the data partition so to be able to format it ... Just a pain, at the moment I am stuck, maybe if I can get someone else's firmware dump for my phone might do the trick its big so I am not sure anyone would upload something that big ... We see
Click to expand...
Click to collapse
Did you try to Flash stock recovery and do a factory reset?
Or via fastboot do this command :
fastboot format userdata
Sent from my HUAWEI VNS-L31 using XDA Labs
simo255 said:
Did you try to Flash stock recovery and do a factory reset?
Or via fastboot do this command :
fastboot format userdata
Sent from my HUAWEI VNS-L31 using XDA Labs
Click to expand...
Click to collapse
I tried all of them. Nothing worked :crying:
Nemeroz said:
I tried all of them. Nothing worked :crying:
Click to expand...
Click to collapse
So I fixed my problems with BadWolfs help he got me back to stock by flashing a special zip that allowed me to install the firmware from dload on the external sdcard
Thx again for your help
markus2811 said:
So I fixed my problems with BadWolfs help he got me back to stock by flashing a special zip that allowed me to install the firmware from dload on the external sdcard
Thx again for your help
Click to expand...
Click to collapse
Forgot here us the link http://www.htcmania.com/showthread.php?t=1261335
Everything you need to go back to stock from cm13 (if you screw up like me) or nougat beta is in here. Is in spanish but google translate is doing a pretty good job all bloody credit is going to badwolf and his friends
Thx and good night
markus2811 said:
Forgot here us the link http://www.htcmania.com/showthread.php?t=1261335
Everything you need to go back to stock from cm13 (if you screw up like me) or nougat beta is in here. Is in spanish but google translate is doing a pretty good job all bloody credit is going to badwolf and his friends
Thx and good night
Click to expand...
Click to collapse
when you flash the oem info didnt it say unable to mount data? like before?
I found that my phone, a Chinese model, is crypted maybe flashing a rom, how do I encrypt it?
venezolano69 said:
I found that my phone, a Chinese model, is crypted maybe flashing a rom, how do I encrypt it?
Click to expand...
Click to collapse
Screenshot?
Here you have it
Maybe this will help you?
http://www.htcmania.com/showthread.php?t=1291480
rubiohiguey said:
Maybe this will help you?
http://www.htcmania.com/showthread.php?t=1291480
Click to expand...
Click to collapse
But I can do everything right now and never my phone ask me for a password, I flashed a lot of rom and always my phone works in the same way, it seems no crypted.
venezolano69 said:
But I can do everything right now and never my phone ask me for a password, I flashed a lot of rom and always my phone works in the same way, it seems no crypted.
Click to expand...
Click to collapse
go into twrp > wipe > format data
you'll lose everything, but that has worked for me in the past
robertzas said:
go into twrp > wipe > format data
you'll lose everything, but that has worked for me in the past
Click to expand...
Click to collapse
OK thanx
I formatted data and now phone is no encrypted but it is complicated flash a Rom, always it says cannot mount cache and sometimes I cannot flash the rom
Now I'm on lineageos last nightly and I wanted to flash pacrom and no way
It's officially available the Flyme for our OnePlus 3/3T
The version is 6.7.5.8R so it's in the beta stage.
Anyone interested? I tried to flash on my 3T model A3003. The rom boots but after the initial wizard i got black screen where only the notification worked.
The thread on flyme forum said:
PS: If you have 3 / 3T users from the official 7.1.1 directly downgrade to Flyme6, card boot LOGO (more than ten minutes) or boot boot after the black screen, please enter the Recovery format data partition, restart the boot!
Click to expand...
Click to collapse
I tried to format many times, but i got always black screen.
Can someone report other experience?
Link for download:
http://www.flyme.cn/firmwarelist-107.html#8
Link to forum:
http://bbs.flyme.cn/forum.php?mod=viewthread&tid=1790328&page=1&extra=#pid25461286
Any fix for the black screen?
Does this rom support f2fs partition ?
Edit : so this is xs build ? Like the miui 8 xs build I think we need to convert system, data partition to ext4 to make this rom boot...
twentyfourinc said:
Does this rom support f2fs partition ?
Edit : so this is xs build ? Like the miui 8 xs build I think we need to convert system, data partition to ext4 to make this rom boot...
Click to expand...
Click to collapse
The rom boot, i go through the initial wizard and then i got black screen only notification.
Btw, yes is XS build
Sent with OnePlus 3T ?
is that good ? i've never tried flyme before..
error in dnd mode.
dnd mode is always on, cannot turn not this.
hope who can fix.
sossio18 said:
The rom boot, i go through the initial wizard and then i got black screen only notification.
Btw, yes is XS build
Sent with OnePlus 3T
Click to expand...
Click to collapse
So we dont need to convert to ext4 ?
emouse112 said:
error in dnd mode.
dnd mode is always on, cannot turn not this.
hope who can fix.
Click to expand...
Click to collapse
You have other than black screen?
Sent with OnePlus 3T ?
twentyfourinc said:
So we dont need to convert to ext4 ?
Click to expand...
Click to collapse
I don't know, dude. You could give a try maybe.
Sent with OnePlus 3T ?
It works on oneplus 3 a3003?
RealRudyz said:
It works on oneplus 3 a3003?
Click to expand...
Click to collapse
Just read the thread and you got the answer
Sent with OnePlus 3T ?
sossio18 said:
Just read the thread and you got the answer
Sent with OnePlus 3T
Click to expand...
Click to collapse
Yes , but I tried a flash and the device went brick
Is it working for anyone?
It's not even booting for me, I get the oneplus logo followed by a black screen with a white led. Am I missing something here? (I did use the latest twrp and I wiped everything).
EDIT: Formatting data worked
noahvt said:
It's not even booting for me, I get the oneplus logo followed by a black screen with a white led. Am I missing something here? (I did use the latest twrp and I wiped everything).
EDIT: Formatting data worked
Click to expand...
Click to collapse
What was you rom before flyme?
Can you explain step by step the procedure you did?
sossio18 said:
What was you rom before flyme?
Can you explain step by step the procedure you did?
Click to expand...
Click to collapse
I fixed the previous problem but now it's just stuck on the flyme logo with the spinning circle. I was running resurrection remix before I flashed this rom. I formatted everything and then flashed the rom. (even fully formatting the internal storage) and I also tried formatting the data partition as ext4 but it's still stuck
Installed without GPlay, everything was fine. Ater installing GApps Micro ROM asking for previous account, but just restarts setup wizard. Maybe, installing via Google Installer will be fine.
OP3T, Data - EXT4, now - second ROM.
New beta 6.7.5.10R
Downloading right now, maybe they fixed the black screen...we'll see
sossio18 said:
You have other than black screen?
Sent with OnePlus 3T
Click to expand...
Click to collapse
boot to twrp, sellect wipe, sellect format data, type yes to wipe.
reboot, and it boot to os done.
Is this global or Chinese version
Hey guys, not exactly sure where to post this since this has happened to me both with AICP and now once with Dark Rom. So simply put I am just using my phone and then randomly it soft reboots. I hurry and take some logs before the next. Then the next. Then it keeps doing this with each time between getting shorter until it just won't fully boot up without wiping dalvik and cache.
I am using Dark Rom at the moment with A2017U version and the stock kernel that comes with Darkrom. However I believe I did have it with LlamaSweet as well. The only modifications I have done are magisk and trying out jococ v2 tweak which I doubt either is the cause.
Has anyone had ant issues like this or does anyone know how to fix it? I hate knowing it's random and it may make my alarm clock not go off if it is in a bootloop.
Hope to get some help with this! Thanks!
JTruj1ll0923 said:
Hope to get some help with this! Thanks!
Click to expand...
Click to collapse
Just realized the zip posted has only files that are blank.... So here is a log I grabbed from TWRP. Hopefully this will help instead!
JTruj1ll0923 said:
Just realized the zip posted has only files that are blank.... So here is a log I grabbed from TWRP. Hopefully this will help instead!
Click to expand...
Click to collapse
No idea, not a dev. But I've read somewhere that Magisk 14.5 might be the culprit. I had this exact same problem on LineageOS. I made a backup of the system that was doing this, then wiped system and data, flashed LOS, booted it, then went to TWRP, wiped system and data, and restored the backup (only system, boot and data backed up). That solved it until you rebooted or the phone just decided to reboot itself...
Choose an username... said:
No idea, not a dev. But I've read somewhere that Magisk 14.5 might be the culprit. I had this exact same problem on LineageOS. I made a backup of the system that was doing this, then wiped system and data, flashed LOS, booted it, then went to TWRP, wiped system and data, and restored the backup (only system, boot and data backed up). That solved it until you rebooted or the phone just decided to reboot itself...
Click to expand...
Click to collapse
By doing this what would be the benefit? From what I can see you are basically back at point A by restoring the files. But yeah I do have magisk 14.5 installed... I had some problems with 14 but I'll see if I can get it to work this time. Thanks!
JTruj1ll0923 said:
By doing this what would be the benefit? From what I can see you are basically back at point A by restoring the files. But yeah I do have magisk 14.5 installed... I had some problems with 14 but I'll see if I can get it to work this time. Thanks!
Click to expand...
Click to collapse
Yes, it seems like it would do nothing, but it actually fixed my phone every time.
Maybe you can try the magisk uninstaller zip, dunno
Choose an username... said:
Yes, it seems like it would do nothing, but it actually fixed my phone every time.
Maybe you can try the magisk uninstaller zip, dunno
Click to expand...
Click to collapse
Thats Interesting. Well it happened again and logs were empty again... So I moved back to magisk 14.0 if that doesn't work I'll try restoring system and data.
@JTruj1ll0923,,
Hi,
you can try to backup before hard reset your phone. Usually, the LlamaSweet and DARK ROM are not compatibile with A2017G, so ZTE stock ROM would be a better choice.
William Guo said:
@JTruj1ll0923,,
Hi,
you can try to backup before hard reset your phone. Usually, the LlamaSweet and DARK ROM are not compatibile with A2017G, so ZTE stock ROM would be a better choice.
Click to expand...
Click to collapse
Thanks but I have a a2017u. Don't know if that makes much a difference though.