[ROM][UNOFFICIAL][10.0][tb8504f/x] Resurrection Remix OS for Lenovo TAB4 8

[Aryan@123]

I've tried it on my TB-8504X and it doesn't happen for me. Audio starts working when I disconnect the headphones. Which firmware are you on? Try S001031.

Please Give Me Your Telegram Username I Want Your Help Urgently

 

[Hausemaster]

Null

 

[Aryan@123]

I only have discord, please contact me there if possible

Give Your Discord ID And You Are Dev Of This Rom??

 

[Hausemaster]

Null

 

[Hausemaster]

Null

 

[adazem009]

Give Your Discord ID And You Are Dev Of This Rom??

I've built this ROM, my ID is adazem009#0422

 

[Aryan@123]

I've built this ROM, my ID is adazem009#0422

Sir Please Give Your Telegram ID If You Can And Accept My Discord Friend Request I Am Unable To Text You.

 

[Aryan@123]

I've built this ROM, my ID is adazem009#0422

Will You Make Havoc Or PE Rom Please
Can You Give Me Havoc OS Build Where Sim Are Not Working I Will Fix It

 

[adazem009]

Sir Please Give Your Telegram ID If You Can And Accept My Discord Friend Request I Am Unable To Text You.

I think I've declined it by accident, could you send another one?

 

[adazem009]

Will You Make Havoc Or PE Rom Please
Can You Give Me Havoc OS Build Where Sim Are Not Working I Will Fix It

How are you going to fix it? You'll have to rebuild anyway.

 

[Aryan@123]

How are you going to fix it? You'll have to rebuild anyway.

I Have Send You Friend Request Again By My Username Anil#0433 Please Accept It And I Can Solve Issue Of Sim Cards If I Got Build.

 

[OvenCrate]

what am i doing wrong here ?

There's a typo in the META-INF/com/google/android/updater-script file. The 5th line is the following:

       getprop("ro.product.device") == "tb_8504" || getprop("ro.build.product") == "tb_8504" || abort("E3004: This package is for device: TB-8504X,TB-8504F,tb-8504x,tb-8504f,tb_8504; this device is " + getprop("ro.product.device") + "."););

Notice that "tb_8504" is listed twice. One of those should be "tb_8504x." I edited mine locally and it installed successfully. @adazem009 you should fix the upload.

 

[Hausemaster]

There's a typo in the META-INF/com/google/android/updater-script file. The 5th line is the following:

       getprop("ro.product.device") == "tb_8504" || getprop("ro.build.product") == "tb_8504" || abort("E3004: This package is for device: TB-8504X,TB-8504F,tb-8504x,tb-8504f,tb_8504; this device is " + getprop("ro.product.device") + "."););

Notice that "tb_8504" is listed twice. One of those should be "tb_8504x." I edited mine locally and it installed successfully. @adazem009 you should fix the upload.

This issue isn't present in the latest firmware for this device, download it from here https://firmwarefile.com/lenovo-tab-4-8-tb-8504x
Download the S001031 version, then start up qfil and put the device in edl mode, hold both volume up and down buttons before connecting to PC or just reboot to edl from twrp, then it'll install the for!ware and you'll be ready to go from that point

 

[Grimripper_07]

It doesn't go any further after this can anyone help me

 

[Hausemaster]

It doesn't go any further after this can anyone help me

How long did you let it run? And also make sure that your recovery is up to date... And also make sure that the installation zip file isn't corrupted, it it's corrupted, it'll get stuck in the same fashion just re-download the rom and try again, and if still it remains the same, start from scratch (flash the stock firmware, then unlock bootloader and try installing this rom...
Edit: Are you using a keyboard and mouse in the recovery or is the cursor persistent at all times...
Edit 2: https://cloud.mail.ru/public/3zrE/32DtrcBpE

twrp-3.3.1-1-TB8504.img

drive.google.com

You can download the latest recovery from these links, and the developer of the recovery is @highwaystar_ru the above links are from the los 17.1 thread for this device...

 

[Grimripper_07]

How long did you let it run? And also make sure that your recovery is up to date... And also make sure that the installation zip file isn't corrupted, it it's corrupted, it'll get stuck in the same fashion just re-download the rom and try again, and if still it remains the same, start from scratch (flash the stock firmware, then unlock bootloader and try installing this rom...
Edit: Are you using a keyboard and mouse in the recovery or is the cursor persistent at all times...
Edit 2: https://cloud.mail.ru/public/3zrE/32DtrcBpE

twrp-3.3.1-1-TB8504.img

drive.google.com

You can download the latest recovery from these links, and the developer of the recovery is @highwaystar_ru the above links are from the los 17.1 thread for this device..

How long did you let it run? And also make sure that your recovery is up to date... And also make sure that the installation zip file isn't corrupted, it it's corrupted, it'll get stuck in the same fashion just re-download the rom and try again, and if still it remains the same, start from scratch (flash the stock firmware, then unlock bootloader and try installing this rom...
Edit: Are you using a keyboard and mouse in the recovery or is the cursor persistent at all times...
Edit 2: https://cloud.mail.ru/public/3zrE/32DtrcBpE

twrp-3.3.1-1-TB8504.img

drive.google.com

You can download the latest recovery from these links, and the developer of the recovery is @highwaystar_ru the above links are from the los 17.1 thread for this device...

Do you use discord or anything. I think I need your guidance

 

[Hausemaster]

Do you use discord or anything. I think I need your guidance

Yes, I do use discord, my username is Hausemaster#7906

 

[adazem009]

There's a typo in the META-INF/com/google/android/updater-script file. The 5th line is the following:

       getprop("ro.product.device") == "tb_8504" || getprop("ro.build.product") == "tb_8504" || abort("E3004: This package is for device: TB-8504X,TB-8504F,tb-8504x,tb-8504f,tb_8504; this device is " + getprop("ro.product.device") + "."););

Notice that "tb_8504" is listed twice. One of those should be "tb_8504x." I edited mine locally and it installed successfully. @adazem009 you should fix the upload.

I think it's correct, the first command checks if ro.product.device is tb_8504. If that fails, it goes to the second command, which compares ro.build.product. If even that fails, it calls the abort command.

 

[adazem009]

Update - 07/26/2021
Download

• Fixed SELinux denials.
• SELinux is enforcing now (WiFi and Bluetooth should work).
• July 2021 security patch.

 

[ImTherious]

Update - 07/26/2021
Download

• Fixed SELinux denials.
• SELinux is enforcing now (WiFi and Bluetooth should work).
• July 2021 security patch.

Flashed and running without issues - thanks (again)!