I am not responsible for any damage that may occur, you assume all responsibility for what you install on your phone.
This is a custom rom for R1HD, (Zen UI).
This is a rom I ported to my R1HD, I like the rom, thought I would share with community.
Rom is rooted, but doesn't prop per app, if you want prop per app after install go to playstore and install SuperSu https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
The rom works well for me, it's intended for people who want something other than stock rom.
The rom includes gapps, so playstore works correctly. The rom is fast and smooth, nice to look at as well.
You need to have bootloader unlocked, and have twrp recovery.
e1a3216d83e18f99c5f2f5c1b8e415b4 /home/vampirefo/Desktop/R1HD_Roms/zen/R1HD_ZenUi.zip
To install download
https://www.androidfilehost.com/?fid=385035244224382387
place R1HD_ZenUi.zip and sdcard reboot to twrp
factory reset
install R1HD_ZenUi.zip
reboot to system.
this rom will take a while on first boot.
Kernel Source
https://github.com/vampirefo/android_kernel_mediatek_mt6735
Only tested via my twrp.
https://www.androidfilehost.com/?fid=24713784966774807
credits
Lexan
Vampirefo
XDA Developers.
Looks gorgeous vamp. Glad you got all the blob stuff sorted out.
"Updater process ended with ERROR: 7"
Does not flash.
bullet25 said:
"Updater process ended with ERROR: 7"
Does not flash.
Click to expand...
Click to collapse
What recovery you using? I only tested on my twrp recovery.
Sent from my R1 HD using Tapatalk
vampirefo said:
What recovery you using? I only tested on my twrp recovery.
Sent from my R1 HD using Tapatalk
Click to expand...
Click to collapse
TWRP.
bullet25 said:
TWRP.
Click to expand...
Click to collapse
You using my twrp?
Sent from my R1 HD using Tapatalk
vampirefo said:
You using my twrp?
Sent from my R1 HD using Tapatalk
Click to expand...
Click to collapse
No, lopestone's. You don't have a TWRP linked in the OP. Why should there be a difference?
bullet25 said:
No, lopestone's. You don't have a TWRP linked in the OP. Why should there be a difference?
Click to expand...
Click to collapse
I don't use his twrp only tested on my twrp.
Sent from my R1 HD using Tapatalk
vampirefo said:
I don't use his twrp only tested on my twrp.
Sent from my R1 HD using Tapatalk
Click to expand...
Click to collapse
Okay, can you please link to your TWRP?
bullet25 said:
Okay, can you please link to your TWRP?
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=24713784966774807
Sent from my R1 HD using Tapatalk
Can this port be used as base for others?
Same error even with your TWRP.
bullet25 said:
Same error even with your TWRP.
Click to expand...
Click to collapse
Works perfectly for me.
Sent from my BLU ENERGY X PLUS using Tapatalk
got it to install with lopestorms recovery. needed to mount the /system as writeable first
but it still had an error message during the flash. I t didnt stop the install. It said failed to mount /system (resource busy) then it continued anyway.
mrmazak said:
got it to install with lopestorms recovery. needed to mount the /system as writeable first
but it still had an error message during the flash. I t didnt stop the install. It said failed to mount /system (resource busy) then it continued anyway.
Click to expand...
Click to collapse
Well yes, cause you shouldn't be mounting system at all, mounting system causes the busy error.
You should just wipe data and cache, not mess with system.
That explains why you all have problems, system should never be touched.
All you should be doing is click wipe, slide one time this is factory reset. Do nothing else then click back and install ROM.
Sent from my BLU ENERGY X PLUS using Tapatalk
vampirefo said:
Well yes, cause you shouldn't be mounting system at all, mounting system causes the busy error.
You should just wipe data and cache, not mess with system.
That explains why you all have problems, system should never be touched.
All you should be doing is click wipe, slide one time this is factory reset. Do nothing else then click back and install ROM.
Sent from my BLU ENERGY X PLUS using Tapatalk
Click to expand...
Click to collapse
iknow system being mounted cause the busy message, but recovery was set with system not writeable before and that caused error 7
to get past error 7 needed to take check mark off "mount system read-only"
mrmazak said:
iknow system being mounted cause the busy message, but recovery was set with system not writeable before and that caused error 7
to get past error 7 needed to take check mark off "mount system read-only"
Click to expand...
Click to collapse
Recovery should never be set ro on system.
Anyway you have it figured out.
Sent from my BLU ENERGY X PLUS using Tapatalk
Flashed it and it works sdly oukitel 10000 does not have a Nougat or a cm13 from what i can see or even an MIUI 8(that would of been a sweet rom to this devices)
PS Also avoid using xposed , some xposed modules will crash the system.ui thus forces you to have to boot back to rec. to start over with the rom. Just a heads-up.(specially for Android N-Ify xposed module lovers like me)....but version 615 worked without crashing the systemUI but bugs in icons(quicksettings) some work some crashes the system but it bring you back to the lockscreen without crashing the hole thing. In other words best to avoid xposed with this rom.
Even though we can't get source compiling to work, it's good to see some sort of ROM for this thing anyway. Good job vamp! Downloading now, can't wait to flash it.
EDIT: Hey would you look at that, FM works!!!
EDIT 2: After fairly extensive use, I've found that both LTE and video recording (with the built in app anyway) don't work. I had an issue with Assistive Touch (I think it was called that) repeatedly crashing, but that can be solved by getting a root uninstaller and outright uninstalling it.
jasonmerc said:
EDIT: Hey would you look at that, FM works!!!
Click to expand...
Click to collapse
You mean like FM radio? If so, then I will have to switch: ).
Related
Suddenly I cannot flash ROMs. I've downloaded, and have tried to flash, 2 ROMs. They are downloaded correctly, too. I've downloaded them multiple times as well.
When I try to flash, it gives me a bunch of prop errors and then gives me an error that the ROM cannot be flashed. I am able to restore backups, though.
I'm not sure what's causing this, as it happened out of the blue. A few days ago I flashed a ROM fine but reverted back to my original ROM because I did not like the other ROM.
I always wipe data and wipe system, and have even wiped cache. Really I'm at a loss her so any help would be greatly appreciated.
what two roms are you trying to flash and on what recovery/version?
B_I_N_G_E said:
what two roms are you trying to flash and on what recovery/version?
Click to expand...
Click to collapse
Tried the Pac-Man ROM and another ROM that I forgot the name of. Recovery is TWRP but I'm not sure what version. It's the version that installed a long time ago when I first rooted and unlocked the device, so it's definitely not the newest version.
BoostinBen said:
Tried the Pac-Man ROM and another ROM that I forgot the name of. Recovery is TWRP but I'm not sure what version. It's the version that installed a long time ago when I first rooted and unlocked the device, so it's definitely not the newest version.
Click to expand...
Click to collapse
Download goo manager from play store. Open, menu button, install OpenRecoveryScript. That will update TWRP. Then try again.
Sent From My Sticky Note, Too?
B_I_N_G_E said:
what two roms are you trying to flash and on what recovery/version?
Click to expand...
Click to collapse
BoostedB18C said:
Download goo manager from play store. Open, menu button, install OpenRecoveryScript. That will update TWRP. Then try again.
Sent From My Sticky Note, Too?
Click to expand...
Click to collapse
Unfortunately I got the same error, albeit it seemed to move along a little more than before. The exact error is as follows:
"file_getprop: failed to stat /sdcard/kernal.pro. Error flashing zip (and a few other irrelevant things)"
BoostinBen said:
Tried the Pac-Man ROM and another ROM that I forgot the name of. Recovery is TWRP but I'm not sure what version. It's the version that installed a long time ago when I first rooted and unlocked the device, so it's definitely not the newest version.
Click to expand...
Click to collapse
In the older Casual root methods the installed recovery was for the international Note 2. and caused some issues on our VZW version.
As was mentioned, install the newest TWRP or CWM and you should be fine.
Also.... remember flashing between a 4.3 ROM and 4.2 and earlier have some differences. Make sure to really read and reread the OP to any ROM you are flashing as most have subtle differences in the recommended method to flash and recovery suggested.
Milimbar said:
In the older Casual root methods the installed recovery was for the international Note 2. and caused some issues on our VZW version.
As was mentioned, install the newest TWRP or CWM and you should be fine.
Also.... remember flashing between a 4.3 ROM and 4.2 and earlier have some differences. Make sure to really read and reread the OP to any ROM you are flashing as most have subtle differences in the recommended method to flash and recovery suggested.
Click to expand...
Click to collapse
Right now I'm on JellyBeans, which is a great ROM. I just wanted to try something different. That ROM is 4.1.2, IIRC.
CWM works? Hrm...gotta give that a try considering I bought it a while ago.
BoostinBen said:
Right now I'm on JellyBeans, which is a great ROM. I just wanted to try something different. That ROM is 4.1.2, IIRC.
CWM works? Hrm...gotta give that a try considering I bought it a while ago.
Click to expand...
Click to collapse
Tried CMW and I get the same error about the kernal.prop
I'm running Saber's kernal. Could it be something with that?
BoostinBen said:
Tried CMW and I get the same error about the kernal.prop
I'm running Saber's kernal. Could it be something with that?
Click to expand...
Click to collapse
I'm going to say the quote.
"Its time for a date with Odin." - @droidstyle
http://forum.xda-developers.com/showthread.php?p=34891181
Just start from scratch and you will be good.
Sent from my Nook Tablet
BoostedB18C said:
I'm going to say the quote.
"Its time for a date with Odin." - @droidstyle
http://forum.xda-developers.com/showthread.php?p=34891181
Just start from scratch and you will be good.
Sent from my Nook Tablet
Click to expand...
Click to collapse
Thanks. I'll give this a try and report back.
Sent from my SCH-I605 using Tapatalk 2
Interesting. I am able to load ROMs with the Aroma installer just fine, just not any that are regular ZIP files.
BoostinBen said:
Interesting. I am able to load ROMs with the Aroma installer just fine, just not any that are regular ZIP files.
Click to expand...
Click to collapse
Any ideas why zip installs give me a kernal.prop error?
BoostinBen said:
Any ideas why zip installs give me a kernal.prop error?
Click to expand...
Click to collapse
Have you tried just flashing a new kernel? there was some issues with a few versions of sabre kernel.... get the newest one or Perseus or something else.
Install the newest version of your recovery (CWM or TWRP)
Boot into recovery.
Clear dalvik/cache
Flash your kernel
Clear dalvik and cache again (just because thats what i do, no idea if its needed)
Test your installed ROM or just install a new ROM following the instructions in the OP of the ROM thread...
If there is no install instructions, I always:
Make a nandroid backup!
Clear dalvik/cache
Factory reset (wipe all but SD card, depending on your recovery)
Install ROM
Clear dalvik and cache again
Install GAPPS (Google Apps package) if not included in ROM
Reboot system
Profit?
Good Luck, report success/failure
BoostinBen said:
Any ideas why zip installs give me a kernal.prop error?
Click to expand...
Click to collapse
What kernel are you using?
Sent from my SCH-I605 using Tapatalk 2
michigan66 said:
What kernel are you using?
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
I'm using Saber's overclocked one. I will grab another kernal and give it a shot and report back.
Got this fixed by switching to another kernel.
I recently installed TWRP 2.6.3.1 on my tablet and installed cm11 along with the gapps through it. It will install it successfully but when I attempt to boot the os it just goes straight back to TWRP. It gets to cyanoboot and says at the bottom booting emmc recovery or something like that. Has anyone else had this problem and if so how did you solve it? Thank you
Sent from my XT907 using xda app-developers app
Me too... Help me
You should take a look at this thread http://forum.xda-developers.com/showthread.php?p=44807398#post44807398 (including in particular my post on the thread http://forum.xda-developers.com/showpost.php?p=44807398&postcount=9).
digixmax said:
You should take a look at this thread http://forum.xda-developers.com/showthread.php?p=44807398#post44807398 (including in particular my post on the thread http://forum.xda-developers.com/showpost.php?p=44807398&postcount=9).
Click to expand...
Click to collapse
without result
I believe it may be a bootloader error
Sent from my XT907 using xda app-developers app
johnny567 said:
I believe it may be a bootloader error
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Did you fix it?
trongdu82 said:
Did you fix it?
Click to expand...
Click to collapse
No I have not been able to I believe I wiped my bootloader partition so I may have just caused more problems for myself
johnny567 said:
No I have not been able to I believe I wiped my bootloader partition so I may have just caused more problems for myself
Click to expand...
Click to collapse
Even if you do, there is no way you can actually brick your NT. You will have to use something like gptfdisk to remake partitions.
(I wiped my entire partition table on my NT by accident and recovered it after 4 or 5 hours of tinkering).
I used this guide: http://forum.xda-developers.com/showthread.php?t=1605664
johnny567 said:
No I have not been able to I believe I wiped my bootloader partition so I may have just caused more problems for myself
Click to expand...
Click to collapse
You should never wipe any partition other than /system, /data, and /cache -- see http://forum.xda-developers.com/showpost.php?p=48612997&postcount=1 for info on the NT partitions and their function.
You might want to consider the recovery method described at http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/.
long complicated solution
trongdu82 said:
Me too... Help me
Click to expand...
Click to collapse
so just in case you have not solved this i have found a solution though it may be more complicated than it needs to be.
1.i used this recovery and completely reset my tablet. http://forum.xda-developers.com/showthread.php?t=2179403&highlight=unbrick
2. i rooted
3. i flashed cwm through the bootable sd card
4. installed cm10.2 along with the gapps for it.
5. i went through the whole set up of cm10.2 (this may not matter)
6. went into fastboot and flashed twrp 2.6.3.1 (just to make sure there were no errors i booted all the way into cm.)
7. flashed cm11 along with gapps.
I hope this helps! if you have any problems or need any of the files i used i will post them asap.
johnny567 said:
so just in case you have not solved this i have found a solution though it may be more complicated than it needs to be.
1.i used this recovery and completely reset my tablet. http://forum.xda-developers.com/showthread.php?t=2179403&highlight=unbrick
2. i rooted
3. i flashed cwm through the bootable sd card
4. installed cm10.2 along with the gapps for it.
5. i went through the whole set up of cm10.2 (this may not matter)
6. went into fastboot and flashed twrp 2.6.3.1 (just to make sure there were no errors i booted all the way into cm.)
7. flashed cm11 along with gapps.
I hope this helps! if you have any problems or need any of the files i used i will post them asap.
Click to expand...
Click to collapse
My Nook is 8 Gb...
I have a mtk6572 will installing modules brick my device
Sent from my GT-S5830L using xda app-developers app
no it will not brick your phone but it will do hang or force stop your system ui sometimes
divyamg28 said:
no it will not brick your phone but it will do hang or force stop your system ui sometimes
Click to expand...
Click to collapse
Never had that problem
BenDroid1 said:
I have a mtk6572 will installing modules brick my device
Sent from my GT-S5830L using xda app-developers app
Click to expand...
Click to collapse
keep this on the root of your sd card...
https://www.dropbox.com/s/h0u496vl6vwp79x/Xposed-Disabler-Recovery.zip
havent ran into brick yet but definitely an endless bootloop...flash this zip and it doesnt delete your xposed modules, just switched it off so you can boot
spiral777 said:
keep this on the root of your sd card...
https://www.dropbox.com/s/h0u496vl6vwp79x/Xposed-Disabler-Recovery.zip
havent ran into brick yet but definitely an endless bootloop...flash this zip and it doesnt delete your xposed modules, just switched it off so you can boot
Click to expand...
Click to collapse
The Xposed installer creates that zip on install. So no need to share it. Isn't it device/rom specific too? (it flashes back some original files from before install)
GriffinSauce said:
The Xposed installer creates that zip on install. So no need to share it. Isn't it device/rom specific too? (it flashes back some original files from before install)
Click to expand...
Click to collapse
Never realized that... Thnx
For anyone that thinks it can't brick your phone it can. I had a Note 4 t;mobile, had a custom recovery twrp 2.8.7, had a backup to. I somehow messed it up so bad I couldn't even get to recovery, Odin original rom, recovery, everything even tried baseband/bootloader. Flashed 4 different original roms, tried flashing philz recovery also. Even restored it via Kies3 said it completed but on boot my phone says recovery...booting and then shuts off. It was worth the risk imo.
Please help me ... After I flash the framework from xposed installer i had the problem of the system force stopping how can I fix it without losing my data
How can I flash the uninstaller , I tried by entering the recovery and apply update from my sd card but it does not work can you tell me if there is another way and thanks
I earlier rooted my cell and it was working fine till yesterday. I reinstalled the DogeMod Rom but now my Xposed Module is not working. I installed root checker from the playstore but it's showing that I am not rooted. I can go into the recovery and have tried flashing supersu files, xposed modules, twrp recovery but still I am unable get it rooted again. I believe that this is a rooting issue only.
Kindly troubleshoot my problem.
Thanking in anticipation.
Manipal said:
I earlier rooted my cell and it was working fine till yesterday. I reinstalled the DogeMod Rom but now my Xposed Module is not working. I installed root checker from the playstore but it's showing that I am not rooted. I can go into the recovery and have tried flashing supersu files, xposed modules, twrp recovery but still I am unable get it rooted again. I believe that this is a rooting issue only.
Kindly troubleshoot my problem.
Thanking in anticipation.
Click to expand...
Click to collapse
Do you have a custom recovery?
christi9503 said:
Do you have a custom recovery?
Click to expand...
Click to collapse
Yes Sir, I can go in the recovery, I tried flashing SuperSu files and other files to get my device rooted but to no effect.
I also tried to root it via SP Flash but still it is showing not rooted
Manipal said:
Yes Sir, I can go in the recovery, I tried flashing SuperSu files and other files to get my device rooted but to no effect.
I also tried to root it via SP Flash but still it is showing not rooted
Click to expand...
Click to collapse
@Manipal
Try flashing this guy.
Also format cache partition and dalvik cache.
christi9503 said:
@Manipal
Try flashing this guy.
Also format cache partition and dalvik cache.
Click to expand...
Click to collapse
Encryption Unsuccessful
Encryption was interrupted and the data on your phone is no longer accessible. Reset your phone now. -_-
Manipal said:
Encryption Unsuccessful
Encryption was interrupted and the data on your phone is no longer accessible. Reset your phone now. -_-
Click to expand...
Click to collapse
When did you get this after clearing cache or after flashing the su update?
christi9503 said:
When did you get this after clearing cache or after flashing the su update?
Click to expand...
Click to collapse
When I rebooted my device after the given instructions were completed.
Manipal said:
When I rebooted my device after the given instructions were completed.
Click to expand...
Click to collapse
Well I have never seen that error before. It is strange because it is just Su binary and SuperSu in the zip i gave you. Did you manage to boot it?
Yes, I have to reinstall all my software's afresh.
Sent from my Nexus 4 using XDA Free mobile app
Manipal said:
Yes, I have to reinstall all my software's afresh.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
Is root working now at least?
christi9503 said:
Is root working now at least?
Click to expand...
Click to collapse
Yes, thanks god, it's working now.
Between thanks for the assistance.
Sent from my Nexus 4 using XDA Free mobile app
Manipal said:
Yes, thanks god, it's working now.
Between thanks for the assistance.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
Sorry for the inconvenience with that error. I don't know what caused it never seen that ever before hope all your data is ok.
christi9503 said:
Sorry for the inconvenience with that error. I don't know what caused it never seen that ever before hope all your data is ok.
Click to expand...
Click to collapse
I reinstalled my rom last night and when I was to reboot again it remained struck there. So first thing in the morning I formatted and installed the rom fresh. It took me about 3 hours to get everything installed and now I am facing the same trouble again.
I am struck at my bootscreen. I rebooted the device when I tried to install a font of Chocooky from Fonter Xposed Module. I am in a big fix now. Please help me now as it is not bypassing the bootscreen :crying:
I am not home and i don t have your device. I just gave a universal root solution. I will try to help when i get home to make some research for your device.
Sent from my LG-P710 using XDA Free mobile app
I'm regular user of Magisk on my Mi5. But it was plagued with the famous issue of losing root after a while.
But while playing around beta ROM, I found that it comes preinstalled with busybox. Somehow felt that's breaking it, so used osmosis's busybox cleaner script from recovery and removed it.
Gave the phone couple of reboots, now Magisk doesn't lose root.
May be you guys can try, make sure you have full flashable ROM zip available in case of any issue or bootloops.
Yup it has, I didn't want to resort to that because I want to keep system unmodified... I'm thinking if it's possible to make use of the magisk busybox to systemlessly replace the inbuilt one...
Sent from my MI 5 using Tapatalk
I haven't seen any issue with removing busybox and i can pass safetynet with Magisk module.
Where you able to take an ota?... With my current setup, I can take ota anytime... V13 is just around the corner now...
Sent from my MI 5 using Tapatalk
I always go for full ROM, handy in case of issues.
chhapil said:
I always go for full ROM, handy in case of issues.
Click to expand...
Click to collapse
Full Rom, Recovery Rom or Fastboot Rom?
Edit: Does it flash via updater app even if the system is modified?
Sent from my MI 5 using Tapatalk
I mean recovery flashable ROM. Yeah the updater app uses recovery flashable.
Full ROM don't check for system modifications
chhapil said:
I mean recovery flashable ROM. Yeah the updater app uses recovery flashable.
Full ROM don't check for system modifications
Click to expand...
Click to collapse
Oh... Okay, thanks for the info... Didn't test that myself because full roms are just too big...
Sent from my MI 5 using Tapatalk
I just tried removing system busybox, the issue still persist after installing modules such as appsystemizer...
Sent from my MI 5 using Tapatalk
teddy0209 said:
I just tried removing system busybox, the issue still persist after installing modules such as appsystemizer...
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
thats issue with the module, for me as well AppSystemizer is breaking the root.
Give it a couple of reboots