UPDATE(02/24/17): Added another new animation by request! It's a modified version of the AOSP Marshmallow boot animation that I customized for the Honor 8.
-------
UPDATE(02/15/17): Added another new animation called "digital 2"! Hope you like it.
-------
UPDATE(02/04/17): Added another new animation called "digital" and added boot animation files with Nougat support!
-------
UPDATE(01/23/17): Added a new animation called "hologram" and a restore file in case anyone wants to revert back to the stock one.
-------
I hope you guys enjoy the animations I made. A lot of work went into making them and figuring out how to get them to work properly on all the different versions of the Honor 8, so if you like them please be sure to press the "THANKS" button on this post, rate this thread 5 stars or if you feel like buying me a coffee even to show your appreciation and support for all the effort, then even better. Thanks!
-------
If you want more information on how to make your own animation for the Honor 8 btw, then here is a tutorial:
https://forum.xda-developers.com/showthread.php?p=70667090
RED ORB
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
HOLOGRAM
DIGITAL
DIGITAL 2
MODIFIED MARSHMALLOW(MM)
(Made this one by request.)
RESTORE
(This file restores the stock boot animation.)
REQUIREMENTS:
An Honor 8 or other 1080x1920 Display Size Device
ROOT ACCESS
CUSTOM RECOVERY OR AN APP THAT FLASHES ZIP FILES
A FULL SYSTEM BACKUP(Highly Recommended.)
TO INSTALL:
1) Download the animation file you want below and put it on the root of your sdcard.
(If the files marked "_nougat" don't change the animation on your Nougat device, then just try one of the regular ones. Also, if you are on US variant L04, build B162, Marshmallow, it is also confirmed that you need to download the Nougat ones. That's all I know so far though until I hear more from you guys, so PLEASE leave a comment with your region/variant/build if the regular files don't work on your MM device or the Nougat files don't work on your Nougat device. Either way though, one of the two versions should work for most Honor 8 variants.)
If you have any issues with the animation not working btw, then know it's just a matter of where the bootanimation.zip needs to be placed on your device. For more info read this post here:
https://forum.xda-developers.com/showthread.php?p=71546460
2) Boot into recovery.
3) DO A FULL SYSTEM BACKUP BEFORE FLASHING ANYTHING(You have been warned!).
4) Select "Install"(to install the zip in recovery), then select the zip file and install it.
That's it. Easy!
-------
*Special thanks to my tester @faizalotai for helping me with testing all of these animations to make sure they're functioning properly.
-------
(PLEASE DO NOT MIRROR THESE FILES!)
HAPPY FLASHING GUYS! ENJOY!!!
If you enjoyed these animations, then please be sure to hit the "Thanks" or Donate button below. Thanks!
Nice job!
I enjoy the stock boot animation, would you be able to figure how it works in order to "restore" it even when we unlock the device?
You know, if we unlock, we've got a ****ing "phone unlocked warning blablablablabla...", would it be possible to have the usual boot animation instead of that?
Tapsibaba said:
Nice job! I enjoy the stock boot animation, would you be able to figure how it works in order to "restore" it even when we unlock the device?
You know, if we unlock, we've got a ****ing "phone unlocked warning blablablablabla...", would it be possible to have the usual boot animation instead of that?
Click to expand...
Click to collapse
I think the phone unlocked warning might be a deeper system thing, but restoring the old animation afterwards shouldn't be that hard. You can always do it from a backup or just save the bootanimation.zip and drop it back in later manually with the correct permissions. I suppose I could make a restore file for you guys too, but it would have to be tested by someone before I uploaded it.
bogarty said:
HAPPY FLASHING GUYS! ENJOY!!!
Click to expand...
Click to collapse
Ahhh, finally...its released.
Op's doing really hard work for this bootani like he doesn't sleep night and day..
Btw, Op's doesn't have the device so thats why it took long enough to released, if he had one, i believed all the problem will be solved in no time.
Anyway thanks to OP and his awesome work ??
Tapsibaba said:
Nice job!
I enjoy the stock boot animation, would you be able to figure how it works in order to "restore" it even when we unlock the device?
You know, if we unlock, we've got a ****ing "phone unlocked warning blablablablabla...", would it be possible to have the usual boot animation instead of that?
Click to expand...
Click to collapse
The untrustworthy phone screen is apart of the bootloader. It isn't tied even remotely to the boot animation.
Any tips on how it was done, maybe with a guide on how it can be repeated?
Thanx for your work!
Saythis said:
The untrustworthy phone screen is apart of the bootloader. It isn't tied even remotely to the boot animation.
Click to expand...
Click to collapse
Daaaamn it, Huawei. It was much better on my good old Moto G, just had to edit the bootlogo. So, I guess no way to make it disappear? (Not even relocking the bootloader because it would wipe the phone and remove root access I guess?)
Too bad
Tapsibaba said:
Daaaamn it, Huawei. It was much better on my good old Moto G, just had to edit the bootlogo. So, I guess no way to make it disappear? (Not even relocking the bootloader because it would wipe the phone and remove root access I guess?)
Too bad
Click to expand...
Click to collapse
Without proper source we won't be able to do anything about it sadly. And yes, relocking would result in losing TWRP and root because as far as I know the only way to relock is to flash a full firmware package (which there are only ones for MM/EMUI 4.1).
Bisclavret said:
Any tips on how it was done, maybe with a guide on how it can be repeated?
Click to expand...
Click to collapse
I made this Honor 8 boot animation tutorial today just for you!
https://forum.xda-developers.com/showthread.php?p=70667090
Hey guys! I just released A BRAND NEW BOOT ANIMATION today that I think you guys might really like. I also released A RESTORE FILE that returns your device to the stock animation too, in case anyone wants to ever go back. @Tapsibaba Thought you might like that, since you asked.
Both files are in the OP!
bogarty said:
Hey guys! I just released A BRAND NEW BOOT ANIMATION today that I think you guys might really like. I also released A RESTORE FILE that returns your device to the stock animation too, in case anyone wants to ever go back. @Tapsibaba Thought you might like that, since you asked.
Both files are in the OP!
Click to expand...
Click to collapse
Hey, I just tried to flash your boot animations, but after what looks like a successful flash in TWRP
nothing changed. I tried to reflash them,.. still nothing changed.
FRD-L04 B162
Update : Your package flashes,.. Its in my system/media folder (Bootanimation.zip) but the original for my variant must be located somewhere else Im guessing.
JF-GINO said:
Hey, I just tried to flash your boot animations, but after what looks like a successful flash in TWRP
nothing changed. I tried to reflash them,.. still nothing changed.
FRD-L04 B162
Update : Your package flashes,.. Its in my system/media folder (Bootanimation.zip) but the original for my variant must be located somewhere else Im guessing.
Click to expand...
Click to collapse
Hmm...strange. You might be the only one this has happened to so far. Worked great for my tester and haven't heard anything about it not working from the 40 other people who downloaded so far. Frankly, I spent so much time doing maybe 100+ tests for weeks to get these to work already too, not sure I'll really be able to be doing too much more tweaking on these unfortunately, as I'm going to be flying out somewhere today. Obviously you have OEM Unlock switched on, your bootloader's unlocked, you're rooted, etc. probably right to have gotten that far? And you're using either the red orb or holo files right and not restore because that's what the restore file does. Not sure what else it could be really. If you want to do some tests for me dropping my bootanimation.zip into the other locations where it's stored on your device, changing the permissions to whatever the file is already in there before rebooting(generally rw-r--r--), then I'd really appreciate it. Thank you and good luck!
bogarty said:
Hmm...strange. You might be the only one this has happened to so far. Worked great for my tester and haven't heard anything about it not working from the 40 other people who downloaded so far. Frankly, I spent so much time doing maybe 100+ tests for weeks to get these to work already too, not sure I'll really be able to be doing too much more tweaking on these unfortunately, as I'm going to be flying out somewhere today. Obviously you have OEM Unlock switched on, your bootloader's unlocked, you're rooted, etc. probably right to have gotten that far? And you're using either the red orb or holo files right and not restore because that's what the restore file does. Not sure what else it could be really. If you want to do some tests for me dropping my bootanimation.zip into the other locations where it's stored on your device, changing the permissions to whatever the file is already in there before rebooting(generally rw-r--r--), then I'd really appreciate it. Thank you and good luck!
Click to expand...
Click to collapse
I think I found where my boot animation is and Its not in the location your zip places it.
On US variant L04, the boot animation is located in one of these locations :
/cust/special_cust/FRD-L04/hardware/usa/media
and /cust/hw/usa/media
I will test this location further. If itis the case, L04 users might need a different zip to flash. Ill let you know.
UPDATE: I have found the location and confirm working.
Location for my L04 is : /cust_spec/media/bootanimation.zip
JF-GINO said:
I think I found where my boot animation is and Its not in the location your zip places it.
On US variant L04, the boot animation is located in one of these locations :
/cust/special_cust/FRD-L04/hardware/usa/media
and /cust/hw/usa/media
I will test this location further. If itis the case, L04 users might need a different zip to flash. Ill let you know.
UPDATE: I have found the location and confirm working.
Location for my L04 is : /cust_spec/media/bootanimation.zip
Click to expand...
Click to collapse
Awesome thanks! Yeah this is the trickiest device ever for animations. I'll try and upload some special files for the L04 later today. If anyone else has any problems too, then just let me know and I'll make one for your device too. Most should work with the standard ones though I think.
bogarty said:
I made this Honor 8 boot animation tutorial today just for you!
https://forum.xda-developers.com/showthread.php?p=70667090
Click to expand...
Click to collapse
Thank you a lot for this! Cheers.
Special files for some L04 devices have been uploaded to the OP. @JF-GINO
Just wanted to say thank you to those who hit the "Thanks" button on the OP or left a comment. Especially in the case of the Honor 8, it may be the only way that I know these animations worked for your specific variant and, of course, that you liked them. Thank you! I'm hoping to possibly make more at some point in the future.
Hey guys! I just made another new boot animation and added it to the OP!!! Hope you like it. I also added animation files for those who've upgraded to Nougat, as it seems that they may have moved the boot animations in Nougat, at least for sure for the L04 variant anyhow. I'd love to hear feedback about the other Honor 8's though as well.
As usual too, I can't thank @faizalotai enough for all the tests and information about the Honor 8. I couldn't do it without you!
May I request for the AOSP Nougat bootanimation to be ported for our Honor 8?
Sent from my Honor 8 using XDA Labs
Related
mods please relocate this post if in wrong area; could not find SGS2 4G forum. If not, please delete this comment!
Hey guys,
I'm hoping we can try keeping this thread for those who have the I9210 SGS2 phone, which is really only going to be the I9210T (Telstra) model which is 4G compatable; has a bigger screen; a better processor and NFC chip. I'm excited getting stuck into this device; have not had much of a play with it yet.
GSMarena Specs, user comments and pics here:
http://www.gsmarena.com/samsung_galaxy_s_ii_lte_i9210-4124.php
For the latest FIRMWARES or info on UNLOCKING device:
Sign up/sign in and search on www.samfirmware.com
Causing a fuss helps; I managed to get this phone today on $59 CAP without paying the MRO $5 per mth and also had over $250 of previous contract termination fees fully waived; so think i have done well there.
Right now I just want to root this phone safely and where possible, get unbranded firmware (i hate all of telstra's locked apps) whilst maintaining all of Tesltra's functionalities with this phone and modem, so that i don't notice any difference in 4G access speeds...
If you have any useful tips, tricks, videos, manuals (etc), link or post them and I'll see if i can add them to this post. If you respond to this thread confirming you have the same phone in Australia and on the Telstra network, i'll add your details here:
SGS2 4G LTE I9210T owners:
roosta
lunchbox201
xrobau
bwp85
ecips
Nutterpc
Joel006
AcidDrops
Click to expand...
Click to collapse
This device has a Snapdragon and the GT-I9100 has an Exynos, so they are 2 completely different devices.
I don't believe XDA has a forum for this device, so I moved it to Android General.
Thanks
Hey Roosta,
There is a few of us out here now who have this phone. Myself, i got mine the first day it was released.
Rooting instructions can be found here:
http://forums.overclockers.com.au/showthread.php?t=1022750
A few people have complained about the bottom buttons not working after rooting. I did not have this issue. The instructions i followed (which was prior to the release of the OCAU instructions above) were for the ATT Skyrocket. Link here:
http://forum.xda-developers.com/showthread.php?t=1340526
lunchbox201 said:
Hey Roosta,
There is a few of us out here now who have this phone. Myself, i got mine the first day it was released.
Rooting instructions can be found here:
http://forums.overclockers.com.au/showthread.php?t=1022750
A few people have complained about the bottom buttons not working after rooting. I did not have this issue. The instructions i followed (which was prior to the release of the OCAU instructions above) were for the ATT Skyrocket. Link here:
http://forum.xda-developers.com/showthread.php?t=1340526
Click to expand...
Click to collapse
Thanks lunchbox, but with the success rate very low from those users who have tried ROOT, i am a bit hesitant trying out the method; especially with MULTIPLE people losing 2 of the 3 front phone buttons.
So you have used the American version and instructons STEP FOR STEP to root the I9210T Aussie stock phone with their files, and it worked no problems?
Anyone else tried and can they share their choice of guide and/or files where the result was a SUCCESS for the aussie stocked version of this phone?
Hey guys,
Thought you'd wanna know i have been playing with the T989 ROMS.
Just installed the SlickMOD supreme 3.5 and it worked.
Link here to ROM: http://forum.xda-developers.com/showthread.php?t=1596790
Take note of instructions. Also the bottom buttons didn't work until after a reboot or two.
DO A NANDROID BACKUP. SAVED MY BUTT MANY TIMES!!!!!!!!!
---------- Post added at 04:40 PM ---------- Previous post was at 04:36 PM ----------
roosta said:
Thanks lunchbox, but with the success rate very low from those users who have tried ROOT, i am a bit hesitant trying out the method; especially with MULTIPLE people losing 2 of the 3 front phone buttons.
So you have used the American version and instructons STEP FOR STEP to root the I9210T Aussie stock phone with their files, and it worked no problems?
Anyone else tried and can they share their choice of guide and/or files where the result was a SUCCESS for the aussie stocked version of this phone?
Click to expand...
Click to collapse
My steps were to install the CWM recovery file supplied from the AT&T thread through Odin. Once phone restarted i went to the market and downloaded the SU file and busybox from there. Thats all i did and it worked without any problems.
Hey guys. quick update. I managed to get my phone replaced by Telstra putting the "buttons not working" issue described and linked-to above, as i bit the bullet, had a go and couldn't get the same outcome as xrobau or lunchbox. I recommend anyone with SGS2 4G does not attempt root until we have a 100% fullproof method working for all who follow a tutorial step for step, OR until ICS is released.
Hey guys, we have been having some luck with installing roms here:
http://forum.xda-developers.com/showthread.php?t=1593061
hey guys, i also have just got one of these phones, coming from HTC were the support for roms and stuff is massive, im looking to support how ever i can get things rolling here.
Theme for Stock Telstra ROM
Hi Guys,
I have knocked up a theme for the stock Telstra ROM.
It includes the lidroid 14 button mod, a modified Google Play and some general ICSifying of the ROM.
Still very much a work in progress (eg, fix colour of clock in status bar), however I though I would get it out there!
Cheers,
Gary
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You can grab the CWM flashable zip file here:
http://www.spice.net.au/GT-I9210T/Telstra_GT-I9210I_Ecips_Theme.zip
ecips said:
Hi Guys,
I have knocked up a theme for the stock Telstra ROM.
It includes the lidroid 14 button mod, a modified Google Play and some general ICSifying of the ROM.
Still very much a work in progress (eg, fix colour of clock in status bar), however I though I would get it out there!
Cheers,
Gary
You can grab the CWM flashable zip file here:
http://www.spice.net.au/GT-I9210T/Telstra_GT-I9210I_Ecips_Theme.zip
Click to expand...
Click to collapse
Hey Gary,
Tried this last night on my phone and got multiple FC's to the point where i had to do a complete restore.
Custom ROM looks nice Gary.
Still waiting for a fullproof stock root. Keep up the efforts Devs!
RoOSTA
I too have had different outcomes in the attempt to root the i9210T.
My first attempt I followed the skyrocket method and worked flawlessly. Buttons working.
While I had CWM installed it wasn't seen from within Rom manager. Not a big thing.
Was able to backup etc through recovery. Then I thought I have a go at a different ROM.
This is where it all went wrong. I bricked the phone. Thats right dead. no signs of life. I was able to get it replaced under warranty.
My new phone I tried again. rooted fine. buttons working. I was trying to get into recovery using the Volume UP+down and Power method so I could do a backup when I accidentally went into a ram dump mode screen. Couldn't get out of this screen so I took out the battery. When it rebooted I had no bottom buttons.
I have read that those who were able to do a backup were able to retrieve their buttons by restoring their boot.img file.
I have tried that. But my buttons were dead before the backup. I used a working boot.img from another phone hoping that would fix it. But that also did not work.
Currently have no buttons and am using the app 'button savior' for the time being.
Would be very interested in any suggestions or fixes for this issue.
I have tried different Roms mainly written for the SGH-989 phone which seem to work. haven't fully tested them, but no buttons.
So I don't think a new ROM will fix this issue. It seems to be deeper that that.
Even re flashing the stock Telstra ROM onto the phone does not fix the button issue.
What I stress is if you do attempt to root your phone, don't power down your phone before getting into recovery and doing a backup of your phone.
Those out there that are trying different things have their working boot.img file to restore to get their buttons again. No sure why it works on their phones and not on others. Must be more that just the boot.img file.
Any suggestion appreciated.
robpi said:
I too have had different outcomes in the attempt to root the i9210T.
My first attempt I followed the skyrocket method and worked flawlessly. Buttons working.
While I had CWM installed it wasn't seen from within Rom manager. Not a big thing.
Was able to backup etc through recovery. Then I thought I have a go at a different ROM.
This is where it all went wrong. I bricked the phone. Thats right dead. no signs of life. I was able to get it replaced under warranty.
My new phone I tried again. rooted fine. buttons working. I was trying to get into recovery using the Volume UP+down and Power method so I could do a backup when I accidentally went into a ram dump mode screen. Couldn't get out of this screen so I took out the battery. When it rebooted I had no bottom buttons.
I have read that those who were able to do a backup were able to retrieve their buttons by restoring their boot.img file.
I have tried that. But my buttons were dead before the backup. I used a working boot.img from another phone hoping that would fix it. But that also did not work.
Currently have no buttons and am using the app 'button savior' for the time being.
Would be very interested in any suggestions or fixes for this issue.
I have tried different Roms mainly written for the SGH-989 phone which seem to work. haven't fully tested them, but no buttons.
So I don't think a new ROM will fix this issue. It seems to be deeper that that.
Even re flashing the stock Telstra ROM onto the phone does not fix the button issue.
What I stress is if you do attempt to root your phone, don't power down your phone before getting into recovery and doing a backup of your phone.
Those out there that are trying different things have their working boot.img file to restore to get their buttons again. No sure why it works on their phones and not on others. Must be more that just the boot.img file.
Any suggestion appreciated.
Click to expand...
Click to collapse
I have been pulling apart the kernel source related to the touch key driver.
It seems that the firmware update is embedded in the kernel driver.
If you take a look in:
/usr/src/Android/drivers/input/touchscreen/melfas_download.c
You will find at line 480:
// Include MELFAS Binary source code File ( ex> MELFAS_FIRM_bin.c)
I suspect that the issue is that the non-I9210T kernels contain different firmware which bricks the controller.
-----------------
I still need to get my hands on the "virgin" sbl1 partition so I can return my phone.
Must be someone out there that can help me?
Just wanted to add I have a GT-I9210T as well, and like many others, already had the first RA for it, lol
Just wanted to add, should have my dev box running tomorrow, picking up the cables for it after work
What OS u think I should run on it, lol
Not windows was my idea
But I'm aiming to get my dev environment running so I can start to mess round with the source
Sent from my GT-P7500 using xda premium
So I download the right source this week, its the 9210T_SEA source code correct?
Sent from my GT-P7500 using xda premium
Nutterpc said:
So I download the right source this week, its the 9210T_SEA source code correct?
Sent from my GT-P7500 using xda premium
Click to expand...
Click to collapse
I believe so. Especially if you're looking at something with the letter 'T' in it.
Additional information of the firmware used for this phone is in my sig. Samfirmware also released another version of the firmware, but i believe its practivcally identical in most areas (code wise) as the stock tesltra F/W.
Any updates?
Woooooooooooooooooo
Phone arrived back from repair today.....
Gunna wait till a bulletproof solution is in place to root this and install custom firmware before i mess with it again
Got my phone now, telstra shop didn't want to give me the phone till they got the charger that they gave me with the loaner phone was returned as well
Going to finish setting up the servers at home, and then start looking at the source for the phone
Do you think its worth trying to aim for a stock pre rooted ROM?
Might look at making that one of my projects this weekend
Sent from my GT-I9210T using xda premium
Just wanted to add my experience with the SGSII 4G...
I got the phone on the 2nd day after it's initial release, attempted a root and lost the soft-touch buttons with no way of going back. I went back to the Telstra store (1hr after getting the phone), and had to wait 4 days for it to be sent off as an ELF and then got a replacement unit.
The replacement unit was a part of a newer batch, but also at this point I did not want it to look suspicious and therefore did not try the root again.
A lot more development and modifications have happened, special mentions to Qasha who actually found a way to resolve the soft-touch buttons. Given that I now had some sort of a safety net, with other repeating it, I tried the root method (as posted by Rob on the OCAU forums), and to my surprise it all worked first go - No need to try and recover from the soft-keys disappearing at all.
With that being said, there may have been a bad batch deployed out - with some users getting the root straight away, and others not so lucky.
Bring on the custom roms ;-)
My wife had apparantly rooted the device without me knowing, went to update it for my daughter for christmas, and now all I can get is a booting icon, and into the recovery menu. I'm sorry if someone has already received help for this, but i need to know how to get it back to stock. it has stock recovery menu, and i can't seem to find which recovery menu is compatible with this device, as well as an OTA file for it, or even a stock file
any help is very much appreciated.
k35513r said:
My wife had apparantly rooted the device without me knowing, went to update it for my daughter for christmas, and now all I can get is a booting icon, and into the recovery menu. I'm sorry if someone has already received help for this, but i need to know how to get it back to stock. it has stock recovery menu, and i can't seem to find which recovery menu is compatible with this device, as well as an OTA file for it, or even a stock file
any help is very much appreciated.
Click to expand...
Click to collapse
. Oh no.
I'm afraid we don't have a recovery or stock image for the new Nabi JR. If you can't get back in to Android there isnt much we can do. Even if we could there is no custom recovery yet. We could make one if we could boot in to Android possibly. You could try booting stock recovery and pressing vol + and vol - at the same time. That will bring up a menu where you could try a factory reset. I don't think that will help but it's worth a shot.
aicjofs said:
. Oh no.
I'm afraid we don't have a recovery or stock image for the new Nabi JR. If you can't get back in to Android there isnt much we can do. Even if we could there is no custom recovery yet. We could make one if we could boot in to Android possibly. You could try booting stock recovery and pressing vol + and vol - at the same time. That will bring up a menu where you could try a factory reset. I don't think that will help but it's worth a shot.
Click to expand...
Click to collapse
unfortunately a factory reset didn't do the trick. would it be worth contacting customer support? purchase date was 11/30, receiving date was the 22nd
k35513r said:
unfortunately a factory reset didn't do the trick. would it be worth contacting customer support? purchase date was 11/30, receiving date was the 22nd
Click to expand...
Click to collapse
Its always worth a shot to see what they say. For someone to help you here there will need to be someone with a Nabi JR S model that is willing to root it, and grab the boot.img, then we need to build recovery and get a good image from a working device. It could take hours or it could take a month, or maybe never(although I know at least 2 people are interested in a recovery).
It's also possible someone could build the kernel from source if the Fuhu source is good and make a recovery(but you still need a 2nd tablet from someone to get a working system image). Either way it can't hurt to see what Nabi support will do.
I'll be calling them next week, if they don't fix it, I'll just buy another, and then I can assist you with getting a recovery image and whatnot. If they do fix it, then I can still assist, lol. Either way Id be happy to help when possible.
No response from customer support after a total hold time of 5 hours on 3 attempts. Corporate offers no response either. Probably short staffed after the bankruptcy filing
Sent from my SM-N910T using Tapatalk
k35513r said:
No response from customer support after a total hold time of 5 hours on 3 attempts. Corporate offers no response either. Probably short staffed after the bankruptcy filing
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
I read the public record bankruptcy filing. They owe a lot of back pay to workers. I am sure the customer service could use a morale boost.
aicjofs said:
I read the public record bankruptcy filing. They owe a lot of back pay to workers. I am sure the customer service could use a morale boost.
Click to expand...
Click to collapse
i'll be watching if we get a system dump.
if it ends up being a total loss (as in fuhu doesn't come through), could always pull/tap the nand chip and dump it old school.
jr S seems to be out of stock everywhere now :-\
edit: also watching for any jr S ota url
PS what method did your wife use to Root it?
saw my first jr S in the wild today.
store only had a display model, or i might've picked one up to get at the special bits.
by chance anyone know the nabi default temp parent passwd (to get back to full android)?
default pass is usually zxcv6789
I have the SNBJR-MT5C, and I have been able to get root using the Kingo method through sideloading. It's a persistent even through factory reset with busybox installed. If someone could help I'd be happy to provide whatever is needed to get TWRP and Gapps on it.
Backups
I have a backup of everything off of this device. It is a mediatek 8127, and it is a PAIN. I have twrp installed on one, but the other one I have, installing the SAME ONE, bootloops. Is there somewhere I could upload that stuff to, so you guys can help?
peppy6582 said:
I have a backup of everything off of this device. It is a mediatek 8127, and it is a PAIN. I have twrp installed on one, but the other one I have, installing the SAME ONE, bootloops. Is there somewhere I could upload that stuff to, so you guys can help?
Click to expand...
Click to collapse
So you made TWRP for the new JR? Just zip it up and use google drive or something?
aicjofs said:
So you made TWRP for the new JR? Just zip it up and use google drive or something?
Click to expand...
Click to collapse
Not really a twrp backup. I got the files backed up with MTK Droid Tools. https://drive.google.com/file/d/0B9xUxjr7RhzYb19iekMydVZUS00/view?usp=sharing
Corbow6 said:
default pass is usually zxcv6789
I have the SNBJR-MT5C, and I have been able to get root using the Kingo method through sideloading. It's a persistent even through factory reset with busybox installed. If someone could help I'd be happy to provide whatever is needed to get TWRP and Gapps on it.
Click to expand...
Click to collapse
awesome, i'm not in here all the time and somehow missed the notification. if someone doesn't beat me to it, i'll try to write something up. in the meantime, don't brick it!
Install Google Play Store
Corbow6 said:
default pass is usually zxcv6789
I have the SNBJR-MT5C, and I have been able to get root using the Kingo method through sideloading. It's a persistent even through factory reset with busybox installed. If someone could help I'd be happy to provide whatever is needed to get TWRP and Gapps on it.
Click to expand...
Click to collapse
I just figure it out an way to install GAPPS on this model of Nabi Jr.
See my guide at : http://forum.xda-developers.com/android/development/guide-manually-install-play-store-fuhu-t3435200
peppy6582 said:
I have a backup of everything off of this device. It is a mediatek 8127, and it is a PAIN. I have twrp installed on one, but the other one I have, installing the SAME ONE, bootloops. Is there somewhere I could upload that stuff to, so you guys can help?
Click to expand...
Click to collapse
How are you able to get the firmware dump off the Junior? My friend and I are struggling to get SP Flash Tool to work properly on a Nabi SE unit we're attempting to dump the ROM from. With the driver Windows 10 automatically downloads upon detecting an MTK device, I get a COM port error, but when I used the one downloaded off Miracle Box's support page, all I get is this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
We tried practically everything to no avail (and nearly soft-bricked one of the SEs my friend has, only for it to somehow pull off a Lazarus lol), and I am at a loss at this. Care to help? More so if you by any chance have an SE at hand.
It's not on the net anywhere either, google is not working for the OT Elevate. There are no custom ROMs for the OT Elevate either.
I know that someone has one of these OT Elevate 5017B phones lying around somewhere. Post a stock ROM for download. People are suffering from bricks and soft-bricks. HELP more, we need to start a project making an attempt to catalog stock ROMs for every android device on earth.
There needs to be a larger archive of these ROMS. iOS developers are killing you. They have a database of all of the iOS firmwares, and there is a database of custom firmwares even for the iPhone 6S.
I know that the iPhone's situation is different, that one company designs the hardware and the software, and that everything is proprietary. I also feel there are too many companies making android phones. competition is one thing, but security of an OS is another. different phones from the same year with older versions of the OS on them, not good.
Marshmellow has been released and there are still 2016 phone releases with 4.5 OS on them. That's not secure. Why can't we make Android more secure by building better custom ROMs for more devices? I know there is a big shortage of developers, but you can recruit. Maybe even get funded by an organization, research grant?
Everyone needs more ROMs. Especially for Alcatel OT Elevate. Let's do something about this.
On 3. 1-2-3, Go Team!!!! :highfive: Let's Get It!
I have one of those Alcatel OneTouch phones right now, and I agree completely upon the notion for a catalog of all android devices that can be flashed.
@mU$!c @tyrex420
These Alcatel devices can only get attention if developers have them in their hands to work with. These devices are running a MediaTek SoC and not many developers like to work with those phones because of a lack of source code to work with or incomplete source in some cases. Yes you are correct in saying that Apple is different as it's one software, one hardware but you have to understand Google only set the stage and the companies do the rest. Not every company is Samsung or Sony. Alcatel has a tool which is really good called Mobile Upgrade Tool which has the factory ROM for their devices (which imho they need work on getting those newer devices supported). It works well if you haven't done much modification to your phone. Now the thing is that when those companies take the phones and modify them in some way like in locking the bootloader or hiding fastboot mode (Tracfone,MetroPCS), there's not much that a developer can do about that. Also those companies do not have that same support tool that Alcatel has which re-downloads the factory ROM because they are modified in some way.
Here's the good part about the phone running a MTK SoC. There are third-party tools such as MTK Droid Tools or SmartPhoneFlashTool (SPFT) which enables the users to make factory backups of their ROMs in the event that their devices suffers from a bootloop. What you can now do is become that developer that you are asking for to work on your phone and make something out of it. Be the first to upload a flashable factory ROM for your phone. Create a thread where users can come and post their issues and assist each other positively. It's nothing hard to do unless as I said before the company locks some part of the phone and makes these tools useless. By the way, MTK Droid Tools developer dropped support at Jelly Bean so KitKat and up won't work with the tool as it should.
Again, yes I agree with you in saying it would be nice for a users to find a compilation of ROMs that they can just follow instructions and flash but the thing is source code and users themselves not knowing how to use the tools mentioned above. If you want you can ask me for help in guiding you on how to use the tools. I've been doing this for 3 years now working with MTK and I'm learning something new everyday.
Sorry for my long reply, I hope to see a reply from you concerning getting a factory ROM for this device maybe a thread similar to mine .
@kirito9
Thank you. I learned more in 2 minutes from your reply than in two hours searching the internet. XDA needs more people like you!
-Cheers
bg260 said:
@kirito9
Thank you. I learned more in 2 minutes from your reply than in two hours searching the internet. XDA needs more people like you!
-Cheers
Click to expand...
Click to collapse
You're welcome .
kirito9 said:
You're welcome .
Click to expand...
Click to collapse
I had one of these fall in my lap. Charging port is shot. At least I can remove the battery and charge. I'm trying to see if it's worth fixing. All signs are pointing to no, unfortunately. OEM Bootloader unlock is available but without Fastboot.......
bg260 said:
I had one of these fall in my lap. Charging port is shot. At least I can remove the battery and charge. I'm trying to see if it's worth fixing. All signs are pointing to no, unfortunately. OEM Bootloader unlock is available but without Fastboot.......
Click to expand...
Click to collapse
Hmm so you don't have a working charging/usb port. I doubt you'll be able to do much with this phone in terms of development. Not sure if there is a way to unlock the bootloader from the device itself, doubt it.
kirito9 said:
Hmm so you don't have a working charging/usb port. I doubt you'll be able to do much with this phone in terms of development. Not sure if there is a way to unlock the bootloader from the device itself, doubt it.
Click to expand...
Click to collapse
I'll see if I can get something useful out of it. Maybe a recovery.img, boot.img, system.img. I'll have to use one of those dreadful one-click apps though.
As for the OP I think this is as close as it gets.
http://forum.xda-developers.com/wiki/
Being a public wiki everyone is welcome to add to or amend it.
bg260 said:
I'll see if I can get something useful out of it. Maybe a recovery.img, boot.img, system.img. I'll have to use one of those dreadful one-click apps though.
As for the OP I think this is as close as it gets.
http://forum.xda-developers.com/wiki/
Being a public wiki everyone is welcome to add to or amend it.
Click to expand...
Click to collapse
Yeah although the information is quite old still useful.
Root with Kingroot and backup with flashify haha. But won't you need the unlocked bootloader to root?
Got side tracked. Device currently disassembled, trying to replace usb but it is hard soldered to the Motherboard. Cheap phones....
bg260 said:
Got side tracked. Device currently disassembled, trying to replace usb but it is hard soldered to the Motherboard. Cheap phones....
Click to expand...
Click to collapse
Ahh cheap phone problems. Let me know if you get through.
Successfully rooted with Kingroot v4.92 . I have included others JIC.
I used The paid SuperSUme Pro to eradicate Kinguser from the device. Here are some other options.
http://forum.xda-developers.com/gal...ve-kinguser-replace-supersu-sch-i545-t3334533
After updating SuperSu via the playstore I installed Busybox Pro, but the unpaid version is fine. At which point I updated the SU binaries the "Normal Way" without a hitch.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
@kirito9
I'll start with a system.img What else do you need?
Thanks
-Bg260
bg260 said:
Successfully rooted with Kingroot v4.92 . I have included others JIC.
I used The paid SuperSUme Pro to eradicate Kinguser from the device. Here are some other options.
http://forum.xda-developers.com/gal...ve-kinguser-replace-supersu-sch-i545-t3334533
After updating SuperSu via the playstore I installed Busybox Pro, but the unpaid version is fine. At which point I updated the SU binaries the "Normal Way" without a hitch.
View attachment 3906591
@kirito9
I'll start with a system.img What else do you need?
Thanks
-Bg260
Click to expand...
Click to collapse
Did you get the the USB removed? Hmm what are we trying to achieve? A full backup or a ROM?
kirito9 said:
Did you get the the USB removed? Hmm what are we trying to achieve? A full backup or a ROM?
Click to expand...
Click to collapse
I wasn't able to replace the USB. Without an unlocked bootloader there is not much I can do. Thought maybe I would help the cause is all. I personally will probably screw with it till it bricks. IDK. Thought someone could at least get a recovery going. I'm not a developer in that sense. I usually just crack open the system.img and add/remove a few thing to my liking. I'll go ahead and dump a system/boot/recovery.img package on AFH if anyone has interest.
bg260 said:
I wasn't able to replace the USB. Without an unlocked bootloader there is not much I can do. Thought maybe I would help the cause is all. I personally will probably screw with it till it bricks. IDK. Thought someone could at least get a recovery going. I'm not a developer in that sense. I usually just crack open the system.img and add/remove a few thing to my liking. I'll go ahead and dump a system/boot/recovery.img package on AFH if anyone has interest.
Click to expand...
Click to collapse
Ahh, that'd be nice. Someone might mess up their stock recovery/boot/system. Please upload and maybe I can try to get a custom recovery for this device. Then make a full backup using the custom recovery.
kirito9 said:
Ahh, that'd be nice. Someone might mess up their stock recovery/boot/system. Please upload and maybe I can try to get a custom recovery for this device. Then make a full backup using the custom recovery.
Click to expand...
Click to collapse
Found something different, the system partition on mmcblk0p33 is 800mb 535 used.
There is also something called custpack on mmcblk0p32 at 1gb total 663mb used. I made an img of both. I'll upload it in a little bit.
Quick question, I have been using furiusisomount with Linux mint cinnamon to rummage around system images. Lately it throws an error and won't mount. Is this familiar to you? I'm not as proficient with the CLI as I'd like to be so I often rely on GUI.
bg260 said:
Found something different, the system partition on mmcblk0p33 is 800mb 535 used.
There is also something called custpack on mmcblk0p32 at 1gb total 663mb used. I made an img of both. I'll upload it in a little bit.
Quick question, I have been using furiusisomount with Linux mint cinnamon to rummage around system images. Lately it throws an error and won't mount. Is this familiar to you? I'm not as proficient with the CLI as I'd like to be so I often rely on GUI.
Click to expand...
Click to collapse
Ok, both images are critical for Alcatel devices running MTK SoC to get it booting. The furiusisomount I'm not familiar with but maybe I can help. What error are you getting?
kirito9 said:
Ok, both images are critical for Alcatel devices running MTK SoC to get it booting. The furiusisomount I'm not familiar with but maybe I can help. What error are you getting?
Click to expand...
Click to collapse
Ok, Here you go. It has boot, aboot, recovery, system and custpack. Are you going to need patitioning info? Be easy if I had adb. But I don't
I'll get back to you on that error. I'm having some other issues and I think it might be systemic. I may have to do a fresh install of Mint.
Let me know what else you need. Happy to help.
https://www.androidfilehost.com/?fid=385035244224385460
bg260 said:
Ok, Here you go. It has boot, aboot, recovery, system and custpack. Are you going to need patitioning info? Be easy if I had adb. But I don't
I'll get back to you on that error. I'm having some other issues and I think it might be systemic. I may have to do a fresh install of Mint.
Let me know what else you need. Happy to help.
https://www.androidfilehost.com/?fid=385035244224385460
Click to expand...
Click to collapse
I think there may be another way to get the partitioning info but let me look into it. Thanks for the files and will let you know if I need anything else .
kirito9 said:
I think there may be another way to get the partitioning info but let me look into it. Thanks for the files and will let you know if I need anything else .
Click to expand...
Click to collapse
See if this is what you need. Created it with DiskInfo Pro. I used a different machine and mounted the system image fine. I thought it was a bad copy because the Build.prop displayed as broken. Then I realized it was just a symlink to the actual build.prop in custpack. At any rate, there's a copy of the build.prop in there as well.
View attachment build.prop-partitions-5017b.zip
UPDATE: Axon 7 A2017U Build 29 (MR3)
New OTA update is arriving and looking forward for what bring to the table.
aerospaceman Employee Oct 30, 2016 6:01 PM
Over the next 24 to 72 hours, you can expect our 3rd software update (MR3) to the Axon 7 (A2017U). This update will bring your device to the latest build, B29. This update comes less than one and a half months from the previous one, but the more exciting news is that we're in parallel paths to deploy Nougat as quickly as possible.
Here are the latest updates you will see on B29 (coming from the previous build, B27):
Notification bell is now optional (hooray!)
New application management policy to enhance battery life
Optimized video camera focus on moving objects
Resolved .FLAC file playback issue
Visual Voicemail optimized for dual SIM
Updated fix for Mute Call issue
Other general enhancements
Note: This is an over-the-air (OTA) update. To check availability of an update, click on "Settings -> Updates."
Aside from this update, you can bet on our R&D team being hard at work on Android N. Early tests from your Mod Squad have been very positive and we trust that many of you will also not sleep for the first several days after upgrading. Setting Nougat aside, we remain heads down prioritizing fixes and enhancements for our community. Your constant feedback, both positive and negative, continue to motivate our R&D team. So please don't let up on your interactions with us and each other about the Axon 7. Until the next update, please drop a comment below to add further motivation for your R&D team!
Click to expand...
Click to collapse
-------------------------------------------------------------------------
UPDATE: Axon 7 A2017U Build 29 (MR3) Announcement Link
-------------------------------------------------------------------------
TWRP Flashable Files can be found here : TWRP_A2017U.B29_Bootstack_StockSystem_Files
What's does the " Parallel paths" mean....
S8ntsHaz3 said:
What's does the " Parallel paths" mean....
Click to expand...
Click to collapse
Ha! I was thinking the same thing. It sounds like more vague crap from ZTE like normal.
jonathan3579 said:
Ha! I was thinking the same thing. It sounds like more vague crap from ZTE like normal.
Click to expand...
Click to collapse
I'm wondering if it means that it's at a parallel in development as far as time between updates... Like b27>b29 was 1 and 1/2 months and that's what they're lookin at for a time frame?
S8ntsHaz3 said:
What's does the " Parallel paths" mean....
Click to expand...
Click to collapse
jonathan3579 said:
Ha! I was thinking the same thing. It sounds like more vague crap from ZTE like normal.
Click to expand...
Click to collapse
S8ntsHaz3 said:
I'm wondering if it means that it's at a parallel in development as far as time between updates... Like b27>b29 was 1 and 1/2 months and that's what they're lookin at for a time frame?
Click to expand...
Click to collapse
my guess is " performing of multiple operations simultaneously " meaning getting MR's OTA and working Naugat (Android 7) at the same time???
well i'm just assuming so , and i assume next Update will be N release., you know B3x
DrakenFX said:
my guess is " performing of multiple operations simultaneously " meaning getting MR's OTA and working Naugat (Android 7) at the same time???
well i'm just assuming so , and i assume next Update will be N release., you know B3x
Click to expand...
Click to collapse
Oh how I hope your right!!!!
Now to wait for the download link
xtermmin said:
Now to wait for the download link
Click to expand...
Click to collapse
It's here!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my ZTE A2017U using Tapatalk
toyanucci said:
It's here!
Click to expand...
Click to collapse
How'd you get the embedded battery percentage?! I sorely miss that from my Nexus 6P.
jonathan3579 said:
How'd you get the embedded battery percentage?! I sorely miss that from my Nexus 6P.
Click to expand...
Click to collapse
There's an app in play store to enable it in any device!
Sent from my ZTE A2017U using Tapatalk
toyanucci said:
There's an app in play store to enable it in any device!
Click to expand...
Click to collapse
Oh sweet, thanks. I think I tried it before but it didn't stick after rebooting. Has it changed since then? If so, I'm definitely gonna have to search for it again.
I have the option for the update as well. Waiting as I'm rooted.
Here is the download link if anyone wants to play with it.
update_P996A01_B27_to_B29.up
I'll be looking into it and try to create a flashable zip for us TWRP users
DrakenFX said:
Here is the download link if anyone wants to play with it.
update_P996A01_B27_to_B29.up
I'll be looking into it and try to create a flashable zip for us TWRP users
Click to expand...
Click to collapse
Thanks for looking into a twrp version!
Sent from my ZTE A2017U using Tapatalk
Parallel paths does indeed mean they are simultaneously working on updates and the long awaited Nougaaaattttt update. ZTE has done a good job updating and listening to their customers in the z-forum. Lets hope this plus Official CM and unlock bootloader without breaking warranty will help ZTE be known as a developer friendly Own.
How do we install if we are unlocked bootloader and rooted??
Do we have any idea if flashing U roms on G device works? Would love to get rid of the bell
Here over in europe, i just received for my A2017G an 703mb big B05 Update.(previous B03)
Strange that ours is 703mb big (hope they fix the youtube freeze Problem) and also supports optional notification bell (no info for that in the change log)
Take a look:
DrakenFX said:
Here is the download link if anyone wants to play with it.
update_P996A01_B27_to_B29.up
I'll be looking into it and try to create a flashable zip for us TWRP users
Click to expand...
Click to collapse
Here is an Mega Mirror for the B29 update. Just in case.
I have simply copied it from its location "data/data/com.zte.zdm/files" where the updater places its OTA files.
https://mega.nz/#!K050XAqT!6EBTgtX13VTdAOiUjiYqeE6jemeOJ2mN8smrrreai6o
MD5: 9a7f45caf459a21a905de0c543748309
If you place the file into that directory. You should be good to go using the inbuild updater.
Dewaynelives said:
How do we install if we are unlocked bootloader and rooted??
Click to expand...
Click to collapse
I was on B27, unlocked bootloader, TWRP recovery, rooted, with changes to /system, and have successfully upgraded to B29 (w/ same modifications). Since I made changes to /system (AdAway, Titanium Backup, AFWall) and wanted a clean slate for everything, I wiped my A7.
If you don't want to factory reset your device and didn't make any changes to /system, you might only have to unroot, restore stock boot.img and stock recovery.img via TWRP (from rczrider's topic linked below), install B29.zip in stock recovery, flash TWRP, then flash root, but I didn't do it personally, so no guarantees.
Anyway, this is what I did. Some of these steps might not have been needed, and probably could have been done differently, but it's what worked for me, and yes I like rebooting:
1. Download the B29 update, DrakenFX's B27 StockSystem zip for TWRP (which also flashes stock boot.img), stock B27 recovery.img from rczrider, and SuperSU 2.65. Put all on microSD.
2. Booted into TWRP and did a factory reset, rebooted back into TWRP and flashed DrakenFX's B27 StockSystem ZIP, rebooted back into TWRP and flashed stock B27 recovery.img, rebooted device.
3. Powered on the device and made sure it booted into OS fine and was still reporting the correct amount of internal storage space. Rebooted into stock recovery and flashed the B29 update.zip from my microSD card. Installed fine, rebooted into OS to made sure it still worked.
4. Rebooted into fastboot, connected to my computer and flashed Unjustified Dev's TWRP via Minimal ADB & Fastboot, booted into TWRP and flashed SuperSU 2.65 from my microSD, let the device reboot itself a couple of times.
I now have B29 with unlocked bootloader, TWRP, and root.
NOTE: Something I noticed when I was going through and disabling system apps: WeShare can't be disabled from the Settings > Apps menu, but can be disabled by opening the app drawer, pressing and holding on it, and dragging it up to "Disable" at the top of the screen.
However, it would probably be easier to just wait for DrakenFX to create custom TWRP install zips for B29.
ROM Pyrana 0.9 HTC U12+ 1.53.401.5 DUGL
. Base: 1.53.401.5 DUGL (dual sim)
. Decembrer 2018 Security Patches
. Deodex
. Busybox, zip aligne
. Disable error reporting
. Root with last Magisk! v19.1 (Default) Credit to @topjohnwu
. Optimized and stable
. Renew HTC Wallpaper
. Pyrana Wallpaper
. All apk up to date
. Slver clock
. Weather custom color
Screen:
For the best experience, please make sure you have the latest HTC U12+ firmware installed prior to installing this ROM (Only for Android 8.0. .The part 'vendor will not be flashed, only system. No need for root, it is in Rom directly
From a base 1.53.401.5 imperatively to have the party 'vendor.
At boot time, leave plenty of time to put everything in place and have a good WIFI connection.
Once everything stabilized update Magisk.
Install:
Backup your ful system and data
Copy Pyrana-U12 to external SD
Reboot to recovery TWRP 3.2.3-3 and format partition, data and cach.
And start Install the zip
Filehost https://www.androidfilehost.com/?fid=1395089523397959188
md5: c120131bd005deba27d8ca4e97f0aba6
****************************************
Download Pyrana-U12-0.6-1.34.401.2 stable:
Update 2019/01/13
FILEHOST https://www.androidfilehost.com/?fid=11410963190603905105
MD5: 1bb28a84eb361542f50ca902d5b2561d
Compatible:
DUGL Dual SIM
Install:
It is imperative to start from a 1.30.401.2 base to get the 'vendor' version!
Unlock your device bootloader via > HTC Dev
Backup your ful system and data
Copy Pyrana-U12-0.6 to external or internal SD
Reboot to recovery TWRP and format partition, System, data and cach.
And start Install the zip
When finished restart and wait for initialization (First boot will take approximately 2 or 3 minutes to optimization)
All flash rom is under your responsibility
Accepts no responsibility for:
Any damage to your device
Any loss of data
All my rom are tested several times in complete wipe system and data
BUGS:
Face unlock not work
********* Tuto HtcDev for unlock bootloader *******
https://mega.nz/#!g8pGiIqB!4F1izBcb_d0ohTHQqWYhjimTCM9ievZBaveIvD_GkoU
Nice, I see you was able to make it, like I told you, without vendor partition, congrats!!!!!!!!
JEANRIVERA said:
Nice, I see you was able to make it, like I told you, without vendor partition, congrats!!!!!!!!
Click to expand...
Click to collapse
Hi,
With patience and trick it is possible
nice, hope you will add more features and fix known bugs in near future! thanks
Nice to see you here @Alan-B
Hi,
Unlocking the face is a root problem, for the moment there is no definitive solution!
The Power apk is not mine so I can not change it, it's not legal. In any case the reboot in recovery is problematic! we may not have installed TWRP fixed! and if there is it can be on partition A or B !!
I do not know if it works on Viper? but it is not certain!
Sorry for the bad English ..
Alan-B said:
Hi,
Unlocking the face is a root problem, for the moment there is no definitive solution!
The Power apk is not mine so I can not change it, it's not legal. In any case the reboot in recovery is problematic! we may not have installed TWRP fixed! and if there is it can be on partition A or B !!
I do not know if it works on Viper? but it is not certain!
Sorry for the bad English ..
Click to expand...
Click to collapse
reboot recovery and faceunlock both work on magisk version of the Viper ROM, the faceunlock doesn't work on full ROM but reboot recovery does work on full ROM but is a dirty & complicated hack
JEANRIVERA said:
reboot recovery and faceunlock both work on magisk version of the Viper ROM, the faceunlock doesn't work on full ROM but reboot recovery does work on full ROM but is a dirty & complicated hack
Click to expand...
Click to collapse
Hi,
I just checked ... my TWRP is in patition B and power reboot works in recovery. If in patition A I do not know !!
To unlock the face, I never had it on my U12..
PS: If we have a backup of the data, it can be restored after the flash of my rom (as long as there are no updates to Android system file in this data or there is a risk of conflict!)
Alan-B said:
Hi,
I just checked ... my TWRP is in patition B and power reboot works in recovery. If in patition A I do not know !!
To unlock the face, I never had it on my U12..
PS: If we have a backup of the data, it can be restored after the flash of my rom (as long as there are no updates to Android system file in this data or there is a risk of conflict!)
Click to expand...
Click to collapse
Yep data backup works for the same version of the HTC rom.before flashing new update/rom, it is recommended to restore data first, then update rom then backup data again, in case you play with stuff and you have to restore data again
Sent from my HTC U12+ using XDA Labs
DeeZZ_NuuZZ said:
Yep data backup works for the same version of the HTC rom.before flashing new update/rom, it is recommended to restore data first, then update rom then backup data again, in case you play with stuff and you have to restore data again
Sent from my HTC U12+ using XDA Labs
Click to expand...
Click to collapse
Hi,
Warning ! if we do not format the data, there may be a problem that the device no longer sees the card sd External after installation of the system! but we can restore data after, there are no problems!
PS: I uninstall all the updates just system in settings / applications, I make a backup of the data, I install my zip and once configured I restore my data.
@Alan-B, any plans to have this work for US Unlocked variant as well? If I am not mistaken we worked together briefly on a device. I want to say it was the U11...
mammothjojo88 said:
@Alan-B, any plans to have this work for US Unlocked variant as well? If I am not mistaken we worked together briefly on a device. I want to say it was the U11...
Click to expand...
Click to collapse
Hi,
The problem with the U12, no way to put AROMA to choose a version! Because of the various partitions on the U12 +. It would be necessary to make an entire rom for each version.
The only solution is to make small changes like Viper but via MAGISK! what I do not do!
I could make a version for US Unlocked, but no way to test it!
Alan-B said:
Hi,
The problem with the U12, no way to put AROMA to choose a version! Because of the various partitions on the U12 +. It would be necessary to make an entire rom for each version.
The only solution is to make small changes like Viper but via MAGISK! what I do not do!
I could make a version for US Unlocked, but no way to test it!
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I wouldn't be so sure of that..... coming soon from a dev near you.....
JEANRIVERA said:
I wouldn't be so sure of that..... coming soon from a dev near you.....
Click to expand...
Click to collapse
Hi,
Yes maybe soon but super-R will not do it, you have to do everything in manual.
I have to test and for that it takes time!
I have no one who helps me for my rom! and that for more than 10 years!
Hard to know everything .... so it takes time. Other cooks are many, each has its specialty!
PS: I saw your discussions but there is no final solution yet!
Alan-B said:
Hi,
Yes maybe soon but super-R will not do it, you have to do everything in manual.
I have to test and for that it takes time!
I have no one who helps me for my rom! and that for more than 10 years!
Hard to know everything .... so it takes time. Other cooks are many, each has its specialty!
PS: I saw your discussions but there is no final solution yet!
Click to expand...
Click to collapse
If you are looking for help I'll be more than happy to help, I am willing to learn or at least try to provide any help I can. I don't want to pressure you but I don't mind getting my hands dirty. Let me know
Alan-B said:
Hi,
Yes maybe soon but super-R will not do it, you have to do everything in manual.
I have to test and for that it takes time!
I have no one who helps me for my rom! and that for more than 10 years!
Hard to know everything .... so it takes time. Other cooks are many, each has its specialty!
PS: I saw your discussions but there is no final solution yet!
Click to expand...
Click to collapse
I think you misunderstood my intention with this post, AROMA is going to be openly available once it is ready for release, we are still having some issues, but not with AROMA any more, AROMA does run perfectly fine now after some tweaks, the problem is the method of installation, right now it can only be triggered manually from a command line while in recovery, we are looking for a solution for it to be able to flash AROMA zip files just like before.
I did not meant to mock you or make fun of you at all, this is a sharing community and once it is available and working, it will be shared for all of us to use it, we just don't think it is ready for public release yet
I am sorry if my comment make you feel any other way than what was my intention. have a nice day!!!!!!!! :fingers-crossed:
hi,
Hello,
No problems, I just wait if it is posible to have the opportunity to adapt Aroma to have choices for installation. Which served more convenient than an .img file. This will allow to have a zip compatible with the various versions, as I did for the U11 (which unfortunately is broken)
Thanks to you for bringing an interest to my work and thanks to 'mammothjojo88' for your proposal, doing the work is not a problem for me, just having some solutions to make the work easier and make it more efficient and practical.
PS: What I find a little sad is the return can or thank you for my work to which I never had donations! for the HTC10 + of 1200 download for the U11 300 and for the U12 +, 25 on 3 days. On the French Forums where it's very different! and I have many thanks for my rom
Alan-B said:
hi,
Hello,
No problems, I just wait if it is posible to have the opportunity to adapt Aroma to have choices for installation. Which served more convenient than an .img file. This will allow to have a zip compatible with the various versions, as I did for the U11 (which unfortunately is broken)
Thanks to you for bringing an interest to my work and thanks to 'mammothjojo88' for your proposal, doing the work is not a problem for me, just having some solutions to make the work easier and make it more efficient and practical.
Click to expand...
Click to collapse
Aroma will be fully customizable just like before once it is ready, we are still working on the last steps of making aroma work, but once it is done it will be just like on previous devices
Great to hear! I will be more than happy to help with any testing you require. Just let me know
mammothjojo88 said:
Great to hear! I will be more than happy to help with any testing you require. Just let me know
Click to expand...
Click to collapse
Hi,
I'm busy compiling a US Unlock version. I'll post it for testing
Test version for Unlock UHL:
https://www.androidfilehost.com/?fid=1322778262904022930
md5: 9fcc1798f2bed7425b5f79f393f687f1