Welcome, visitor! [ Register | Loginrss

  • Title: Stock R-16 for TWRP (Xposed fixed)
  • Listed: 07/14/2017 9:28 pm
  • ROM Version: R-16 Android 6.0
  • You must be logged for ROM download.


Overall Rating : 2


1084 total views, 4 today

3 Total favorites

  

Stock R-16 for TWRP (Xposed fixed)
Stock R-16 for TWRP (Xposed fixed) - Image 1Stock R-16 for TWRP (Xposed fixed) - Image 2Stock R-16 for TWRP (Xposed fixed) - Image 3Stock R-16 for TWRP (Xposed fixed) - Image 4Stock R-16 for TWRP (Xposed fixed) - Image 5Stock R-16 for TWRP (Xposed fixed) - Image 6

Author adMember Info

matroskin444


DESCRIPTION


Stock firmware R-16 for TWRP.
Xposed works fine.
After installing xposed, download 5-7 minutes.

init.d – yes

busybox – yes

root – no

Install via TWRP. Wipe dalvick, cashe, system and data partition before install the rom.

Before installing it is recommended to make a backup!!!



※Please make a backup of your device before installing or updating ROM


Donate with PayPal to matroskin444

Donate with YANDEX to matroskin444


7 Responses to“Stock R-16 for TWRP (Xposed fixed)”







  1. 03/10/2017

    Peru

    Excellent work, could you develop a rom miui for this model please? You are a big thank you very much





  2. 09/07/2016

    Dominican Republic

    when trying to install I get the file is corrupt





  3. 08/10/2016

    Germany

    Good work friend 8/10, however after installing I am unable to connect with ADB from win7 or linux. The device ID comes up bogus as 123456ABCDEF, no confirmation dialog, no revoke permissions option. Also unable to flash other Roms with spflashtools, (using win7) getting unrecognised device. Not a huge problem because this is my Rom of choice. But I made a backup of data with ADB and can't restore now. Please help, I could do it manually if I knew it would work, but really dont want to have to dissect my adb backup and attempt to sideload the data back on. Any advice?

    • matroskin444




      05/12/2017

       

      Serial number 123456ABCDEF is listed on all official firmware.

      Try to reinstall the adb drivers, because you are the first with such a problem, others all get connected and are properly stitched.


Leave a Reply

You must be logged in to post a comment.