[Android 10] RevengeOS 3.1 for Lenovo Z6 Pro

[cpc71783]

Hello, I'll be getting the international version of the phone, linked below. Will this ROM work with the phone linked?

https://www.amazon.com/Lenovo-128GB-Factory-Unlocked-Warranty/dp/B082J7QMDK/

 

[kalexel]

I still cant make boot this rom, bootlop... why it cant boot on my phone? i made a full whipe, no more crash dump but cant start the S.O. why? on any possible way

 

[threeeye]

I still cant make boot this rom, bootlop... why it cant boot on my phone? i made a full whipe, no more crash dump but cant start the S.O. why? on any possible way

Can you post your steps of how you are flashing the ROM?

 

[kalexel]

Can you post your steps of how you are flashing the ROM?

Here:

i have unlocked bootloader.
Im on GLOBAL ROM: L78051_11.0.575
1. first i flash the modified vbmeta and the TWRP recovery from mauronofrio
2. the i put the rom on the device
3. full wipe (system, data, cache, vendor)
4. flash the ROM
5. Flash the GAPPS (pico)
6. wipe dalvik
7. Reboot
8. BOOTLOP... :crying::crying::crying:
What is wrong?

 

[threeeye]

Here:

i have unlocked bootloader.
Im on GLOBAL ROM: L78051_11.0.575
1. first i flash the modified vbmeta and the TWRP recovery from mauronofrio
2. the i put the rom on the device
3. full wipe (system, data, cache, vendor)
4. flash the ROM
5. Flash the GAPPS (pico)
6. wipe dalvik
7. Reboot
8. BOOTLOP... :crying::crying::crying:
What is wrong?

As far as I recall, you are doing everything right...
I'm not sure why you are getting a boot loop
Did you try booting after flashing the ROM (without flashing GAPPS)?
Try open_gapps-arm64-nano (not pico)
Sorry for not being more help...

 

[ducatisto]

I still cant make boot this rom, bootlop... why it cant boot on my phone? i made a full whipe, no more crash dump but cant start the S.O. why? on any possible way

I would try a FORMAT data, a wipe often isn't enough. And i don't really see a reason to wipe vendor, to the contrary. Good luck.

 

[wlcbtd]

According to first post, you must only wipe data.
Orher point , your base rom 11.0.575 it is a fake raw rom.
It's a very old cn rom custom for have multilang,
Try with 11.0.405st as a base . It's the last row rom way better than your's.

 

[benjieb]

I think 11.0.575 is not fake global rom but an old CN rom.
If it is stock unaltered it should receive various OTA up to 11.1.105

 

[wlcbtd]

True, but kalexel say 11.0.575 Global rom.
That why i think he was on 11.0.575 zaza rom.
At the launch it was a popular solution to have a "better global rom". But with no Ota possibility.

But my advice is just for help him to move to revenge .
I'm a red global unlock religious, you're a blue lock cn fan. ?

 

[benjieb]

True, but kalexel say 11.0.575 Global rom.
That why i think he was on 11.0.575 zaza rom.
At the launch it was a popular solution to have a "better global rom". But with no Ota possibility.

But my advice is just for help him to move to revenge .
I'm a red global unlock religious, you're a blue lock cn fan.

Ahah, we will all endup Revenge fans anyway
Are you using it yet ?

Have you joined the Telegram group ?

 

[wlcbtd]

Ahah, we will all endup Revenge fans anyway
Are you using it yet ?

Have you joined the Telegram group ?

No revenge for now, bluetooth audio is very important for me !.
And yes i'm on telegram, that's why i have joke ?
You say red is for vampire .

 

[kalexel]

True, but kalexel say 11.0.575 Global rom.
That why i think he was on 11.0.575 zaza rom.
At the launch it was a popular solution to have a "better global rom". But with no Ota possibility.

But my advice is just for help him to move to revenge .
I'm a red global unlock religious, you're a blue lock cn fan.

in fact, my ROM dont have OTA´s maybe youre right. its probably a fake Global ROM, also i just wanna try this custom ROM, the BT audio its also a daily basic use for me, its just very weard that i cant make this ROM start in any way.

my actual rom is (abput phone) 11.0.405 ST

after so many bootlops y may wait some more updates to try again to flash te ROM...

 

[wlcbtd]

If you are on 11.0.405st you have the last global rom.
If english is not a problem for you you can try the 11.1.105 who is the last stable chineese rom, you can change the language at start to english.
And after all this adventure you can give a chance to the 11.5.229 who is the last chineese beta for android Q.

But keep looking for revenge advance the dev is waiting for the deliver of his phone so we hope big improvement soon ?

If you go to the telegram group we have an active community including the revenge dev. So maybe more help.

Look for a group lenovo z6 pro

 

[Lucchetto00]

Hello guys, a new build is here ! A lot of bug fixes, check the first post to download
Very important: You'll need ZUI 11.5.229 firmware to install the new build

 

[threeeye]

Thanks for the hard work, do we need to wipe anything, or just flash it on top the old version?

BTW, did you get your phone yet?

 

[hehk1234]

The new version have problem, I can't make any call.

 

[kanschelskes]

The new version have problem, I can't make any call.

flash q.zip through twrp

 

[threeeye]

Anyone also gets E3004: This package is for device: zippo; This device is Zippo (with a capital Z)?

Edit:
NVM, I edited this line in "RevengeOS-3.1-Q-UNOFFICIAL-zippo-20200216-0918.zip\META-INF\com\google\android"

assert(getprop("ro.product.device") == "Zippo" || getprop("ro.build.product") == "Zippo" || abort("E3004: This package is for device: zippo; this device is " + getprop("ro.product.device") + ".");

Edit 2:
I get Qualcomm CrashDump Mode

 

[descarao81]

I get Qualcomm CrashDump Mode

Do Format Data from TWRP (Format, not Wipe) and install Revenge again.

 

[threeeye]

Do Format Data from TWRP (Format, not Wipe) and install Revenge again.

I did a data format, and it doesn't help, now I get a recovery loop,stuck on Lenovo boot logo or get stuck at the Revenge booting logo animation for more than an hour...
I'm now trying to flash a ROM that I know is supposed to work, if this doesn't work, I'll need to flash a EDL ROM (I think I may have bricked my phone)...