Full Tutorial and clean Rom by @demenicis http://www.needrom.com/download/zte-axon-mini-model-b2016-only/
You can search on this thread to find the files for Android 6.0.1
You need to root and install TWRP for flashin Android Marshmallow
I recently bought a ZTE Axon Mini here in Europe. It is a pretty good phone, the only problem is the software part which has some lag and UI problems.
They certainly can be fixed with a custom rom or rooting and doing changes or by ZTE themselves.
Here I will write the problems
1) The touch responsiveness could be more fast and snappy, when scrolling etc.
2) random lag occurs from time to time, Some other lag issues with the background apps closing etc.
3) Notifications sometimes do not show at all even when keeping aps on whitelist (deactivate mi assistant to solve this)
4) Dolby Audio gets deactivated almost every time you use headhones .
5) Marshmallow release anytime soon?
6) the UI is too heavy for the phone, most stock apps have issues
7) You cannot adjust brightness inside camera app on auto mode, the HDR mode is really not good ( too blurry)
Click to expand...
Click to collapse
Most of these issues have been fixed on 6.0.1 Rom (search thread)
Summary and further tweaks by @demenicis http://www.needrom.com/download/zte-axon-mini-model-b2016-only/
Edit 1--------------------------------------------------
Root method has been found and works on all axon mini models Android 5.1.1
Credit for finding @orbitz52 and @Heze85
http://www.mgyun.com:81/thread-48100-1-1.html
Just translate the page on Chrome and follow the instructions
For 6.0.1 Marshmallow Root you need to have custom recovery and flash supersu via recovery
Edit 2--------------------------------------------------------
Notification issue has been solved (read pages 1-3)
!!IMPORTANT NEWS!!
Custom recovery for axon mini by @Bormental
TWRP 3.0.2 for ZTE Axon mini unofficial.
It works in all Axon mini mods (B2015 and B2016 with or without "Force Touch".
Installation manual:
1. ROOT device (see the manual in this thread).
2. Download the archive with TWRP.
3. Unzip twrp.img to phone's internal storage.
4. Install any terminal emulator from Google Play and open it.
5. Paste these lines one by one to terminal:
Code:
su
dd if=/dev/block/bootdevice/by-name/recovery of=/sdcard/stock_recovery.img
dd of=/dev/block/bootdevice/by-name/recovery if=/sdcard/twrp.img
6. Keep the file stock_recovery.img in safe place. It is your stock recovery image.
7. Now TWRP is installed. You can run it by holding vol+ and power button when phone is off or just reboot your phone while holding the vol+ button.
HOW TO ENTER RECOVERY WHEN ON BOOTLOOP WITHOUT EMPTYING THE BATTERY by @Crisvendetta
1. Hold volume up and power button the whole time of this procedure until the moment said below
2. Keep holding, the first time the device will be stuck on boot logo for 10 seconds and restart
3.Keep holding until the device is stuck on boot loop for 5-6 seconds before powering down.
4. RELEASE BUTTONS AS SOON AS SCREEN SHUTS DOWN ON THE 5 SECOND BOOT
5.Now Device is shut down
6. You can enter recovery normally by holding power plus volume+
What to do if the phone with android 6.0.1 is suddenly switching off during backup, restore, copying heavy files or installing ROM:
CLICK TO HIDE CONTENT
Install aboot image from 5.1.1
Reboot recovery
Make all needed operations
Return back aboot image from 6.0.1 before rebooting to system
Attention! Android will boot only with proper aboot image installed!
WARNING! Your warranty is now void! Any operation with firmware can break your phone!
Special thanks
1) @Bormental
2) @orbitz52
3) @demenicis
Hi,
I can't confirm 1), actually my device runs smooth. I have the Build Version ZTE B2016 FTV1.0.0B01.0
2) random lags occurs, but rare.
3) it seems that this is an issue by the power saving management, I also have some issues with it. I'm actually testing autostart and whitelisting for background the important apps like messengers.
4) I didn't tested this yet
5) I read something arround February this year.
If you google for root, you can find some work instructions, but OTA will be deactivated. I have not tested it yet, will give the phone a few months and ZTE for the update
Issues
I have a lot of problems with this phone. Sometimes apps doesn't work. Most of the times I can't recive notifications, sometimes is laggy, some options doesn't work or change to it's inicial configuration, force touch is not accurate.... A lot! Please ZTE do something!. BTW, how can I solve the notification problem?!
Thank you so much
Korgan1983 said:
Hi,
I can't confirm 1), actually my device runs smooth. I have the Build Version ZTE B2016 FTV1.0.0B01.0
2) random lags occurs, but rare.
3) it seems that this is an issue by the power saving management, I also have some issues with it. I'm actually testing autostart and whitelisting for background the important apps like messengers.
4) I didn't tested this yet
5) I read something arround February this year.
If you google for root, you can find some work instructions, but OTA will be deactivated. I have not tested it yet, will give the phone a few months and ZTE for the update
Click to expand...
Click to collapse
The notification part is the worst until now.
What I would add is that the camera app is unstable. It gets randomly on night mode and could be improved, on the focus and autoexposure part .
Overall the phone is great, it needs to be improved on the software part and I believe it could succeed and give ZTE a even better reputation
Now on the updates, does anyone know when marshmallow will be released for the Axon mini?
Notification
Crisvendetta said:
The notification part is the worst until now.
What I would add is that the camera app is unstable. It gets randomly on night mode and could be improved, on the focus and autoexposure part .
Overall the phone is great, it needs to be improved on the software part and I believe it could succeed and give ZTE a even better reputation
Now on the updates, does anyone know when marshmallow will be released for the Axon mini?
Click to expand...
Click to collapse
Yes, the notification part is the worse. It should be solved in the coming days...
ZTE AXON notifications FIX !
Aitex10 said:
Yes, the notification part is the worse. It should be solved in the coming days...
Click to expand...
Click to collapse
Ok guys, I have solved the notification issue, it seems ZTE had optimized the system for app cleaning, it even cleaned out some resources whatsapp and other apps such as this need to send notifications. Here is the solution for the ZTE AXON (all series)
1. Go inside settings /Power manager /manage background . Here deselect all the apps that you want to send notifications.
2. settings/power manager/auto start manager . Here select all the apps that you want to send notifications.
3. go inside Mi-assistant /Acceleration/ Whitelist . Here select all the apps that you want to send notifications. Otherwise, disable Mi-Assistant from the settings/apps.
It seems the tap to accelerate would remove all resources from these apps, With these changes, every notification will come as usual. CHEERS!!
Crisvendetta said:
Ok guys, I have solved the notification issue, it seems ZTE had optimized the system for app cleaning, it even cleaned out some resources whatsapp and other apps such as this need to send notifications. Here is the solution for the ZTE AXON (all series)
1. Go inside settings /Power manager /manage background . Here deselect all the apps that you want to send notifications.
2. settings/power manager/auto start manager . Here select all the apps that you want to send notifications.
3. go inside Mi-assistant /Acceleration/ Whitelist . Here select all the apps that you want to send notifications.
It seems the tap to accelerate would remove all resources from these apps, With these changes, every notification will come as usual. CHEERS!!
Click to expand...
Click to collapse
How come Axon on 5.1.1 doesn't have Power manager or Mi-assisant?
Crisvendetta said:
Ok guys, I have solved the notification issue, it seems ZTE had optimized the system for app cleaning, it even cleaned out some resources whatsapp and other apps such as this need to send notifications. Here is the solution for the ZTE AXON (all series)
1. Go inside settings /Power manager /manage background . Here deselect all the apps that you want to send notifications.
2. settings/power manager/auto start manager . Here select all the apps that you want to send notifications.
3. go inside Mi-assistant /Acceleration/ Whitelist . Here select all the apps that you want to send notifications.
It seems the tap to accelerate would remove all resources from these apps, With these changes, every notification will come as usual. CHEERS!!
Click to expand...
Click to collapse
Also remove the accelerator settings inside the mi assistant / software settings
Dooosu said:
How come Axon on 5.1.1 doesn't have Power manager or Mi-assisant?
Click to expand...
Click to collapse
I am also on 5.1.1.
Notification works better with enabling autostart and enabling background settings. I have disabled the Accelerator / Mi-Assistant, Android has its own power management.
Hello,
i did not find MI-Assistant, where exctely?
Crisvendetta said:
Also remove the accelerator settings inside the mi assistant / software settings
Click to expand...
Click to collapse
Hi,
where can i finf mi Assistant??????
ridowski said:
Hi,
where can i finf mi Assistant??????
Click to expand...
Click to collapse
Which version of Axon do you have ?
It seems the ZTE Axon A1R doesn't have mi-assitant or even power manger/ background manager, and it's on 5.1.1
Guess no way to get that without unlocking the bootloader?
Crisvendetta said:
Ok guys, I have solved the notification issue, it seems ZTE had optimized the system for app cleaning, it even cleaned out some resources whatsapp and other apps such as this need to send notifications. Here is the solution for the ZTE AXON (all series)
1. Go inside settings /Power manager /manage background . Here deselect all the apps that you want to send notifications.
2. settings/power manager/auto start manager . Here select all the apps that you want to send notifications.
3. go inside Mi-assistant /Acceleration/ Whitelist . Here select all the apps that you want to send notifications.
It seems the tap to accelerate would remove all resources from these apps, With these changes, every notification will come as usual. CHEERS!!
Click to expand...
Click to collapse
Tried this on mine and this made no difference in fact in an attempt to combat the delayed notifications I had done the above and unfortunately in my case made no difference? If anyone has any other suggestions please let me know.
hoppi05 said:
Tried this on mine and this made no difference in fact in an attempt to combat the delayed notifications I had done the above and unfortunately in my case made no difference? If anyone has any other suggestions please let me know.
Click to expand...
Click to collapse
Inside mi assistant remove the auto run on startup and then press exit the mi assistant.
This last few days every notification has shown on time, I did a fresh factory reset and the applied all the settings. Don't know if that would help everyone but I am satisfied until now
I didn't do a factory reset and stopped the Mi-Assistant. Notifications work well after that. But don't forget to do Step 1 and 2, that is still neccessary beside of stopping the Assistant.
I was wondering what is the difference between zte b2015 and b2016 models. I have the b2016 but it seems nothing changes with b2015.
My geekbench 3 scores single core 712 multicore 3107
Antutu 38051 .
Korgan1983 said:
I didn't do a factory reset and stopped the Mi-Assistant. Notifications work well after that. But don't forget to do Step 1 and 2, that is still neccessary beside of stopping the Assistant.
Click to expand...
Click to collapse
Indeed, disabling Mi-assistant together with the steps mentioned, solves all notification issues
Dooosu said:
How come Axon on 5.1.1 doesn't have Power manager or Mi-assisant?
Click to expand...
Click to collapse
What model is that? Sounds like the US version?
Related
This is place where you can come and ask questions regarding support as well as any other general discussion for the Null rom. Please keep the development thread to just that DEVELOPMENT. The developer of this rom is here to develop and not here to answer your questions because you can't take the time to figure out the answer yourself. This will be a community driven thread. Therefore, if you feel something needs to be added to the OP please mention me in a post and I'll take a look
If you need to download the rom free to stop by the dev thread to download. However, if I see you ask a question in here and then go to that thread to ask the same question I will be handing out infractions. Please consider this your only warning.
On a side note, I'll be transferring the OP of this thread to a person with this device in due time. However, for the moment this needed to be created. If you are willing to take the OP from me please feel free to send me a PM. The only requirement that I would have is that you keep it updated properly.
FAQ / IT DOESNT WORK ! WAH
INTERNET ACCESS
GO INTO "FULL SETTINGS -> BLUETOOTH -> SELECT YOUR PHONE SETTING ICON (ON THE RIGHT OF PHONE NAME) -> TICK INTERNET ACCESS".
ENSURE BLUETOOTH TETHERING IS ENABLED ON YOUR PHONE BEFORE HAND OBVIOUSLY.
*NOTE* ENSURE YOUR MOBILE DEVICE SUPPORTS TETHERING, US VARIANT PHONES HAVE RESTRICTIONS INPLACE. REFER TO THE US INTERNET TETHERING THREAD.
*NOTE 2* BLUETOOTH TETHERING DOES NOT AUTO RECONNECT, INSTALL THIS THIRDPARTY SOLUTION ON YOUR GEAR TO ENABLE AUTO RECONNECT.
PLAYSTORE / GOOGLE ACCOUNT MANAGER HAS STOPPED..
VERIFY YOU HAVE A BLUETOOTH INTERNET TETHERING CONNECTION ESTABLISHED BEFORE ATTEMPTING TO ADD A GOOGLE ACCOUNT.
MUST NOT BE USING THIRD PARTY TETHERING, EG. PDANET.
HOW DO I FULL WIPE?
BOOT INTO RECOVERY MODE AND SELECT THE "RECOVERY" OPTION. DO THIS AFTER FLASHING THE ROM
UNABLE TO WAKE GEAR WHILE IN PHONE CALL
THIS IS CAUSED BY THE HOME BUTTON REMAP MOD, THE HOME BUTTON MUST BE PRESSED IN ORDER TO WAKE THE GEAR UP IN THIS STATE.
ONLY WORK AROUND IS TO EITHER USE THE WRIST WAKEUP GESTURE OR DISABLE THE HOME BUTTON REMAP MOD.
*NOTE* BY DISABLING THE HOME BUTTON REMAP MOD, THIS WILL DISABLE THE ABILITY TO MANUALLY LOCK THE SCREEN WHILE USING A CUSTOM LAUNCHER.
DOUBLE TAP BRIGHTNESS/SOUND TOGGLE HAS DISAPPEARED
THIS IS CAUSED BY USING THE FULL SYSTEM UI, SIMPLY PUT IT REPLACES THE DOUBLE TAP WINDOW WITH THE NOTIFICATION SHADE. BY USING GRAVITYBOX YOU CAN ADD ADDITIONAL TOGGLES LIKE BRIGHTNESS & SOUND TILES TO THE FULL NOTIFICATION SHADE.
OTHERWISE SIMPLY REFLASH THE ROM WITH THE FULL SYSTEMUI OPTION UNTICKED.
SCREEN FLICKERING/GITTERING
THIS IS CAUSED BY THE INITIAL BOOTUP, REBUILDING THE CACHE AND INITIALIZING ALL THE APPS. GIVE YOUR GEAR A FEW MINUTES TO SETUP AND RESTART.
SCREEN UNLOCKS TO NOVALAUNCHER PAGE PREVIEW?
GO INTO "NOVA SETTINGS -> GESTURES -> HOME BUTTON -> NONE".
ENABLE DEVELOPER SETTINGS / USB DEBUGGING
GO INTO "SETTINGS -> GEAR INFO -> ABOUT GEAR", TAP SOFTWARE VERSION 10 TIMES.
ENABLE UNKNOWN SOURCE APK INSTALLATION
GO INTO "FULL SETTINGS -> SECURITY -> TICK UNKNOWN SOURCES".
ENABLE MTP
GO INTO "FULL SETTINGS -> STORAGE -> MENU BUTTON (TOP RIGHT OF SCREEN) -> USB COMPUTER CONNECTION -> MEDIA DEVICE (MTP)".
WATCH STYLER NOT WORKING
ENSURE ITS SELECTED AS THE DEFAULT WATCHFACE IN GEAR MANAGER.
IF CLOCK FACE DOES NOT UPDATE UPON CHANGING, RESTART GEAR.
DOUBLE CLICK HOME BUTTON DOESNT WORK ON TOUCHWIZ LAUNCHER !
*NOTE* DO NOT DO THE FOLLOWING IF YOU ARE USING NOVALAUNCHER, YOU WILL NOT BE ABLE TO MANUALLY LOCK YOUR GEAR.
*NOTE 2* YOU CAN SIMPLY REFLASH THE ROM WITHOUT WIPING AND DISABLE THE HOME BUTTON REMAP MOD.
NAVIGATE/PULL THE FOLLOWING FILE FROM YOUR GEAR: /SYSTEM/USR/KEYLAYOUT/GPIO-KEYS.XML
EDIT IN A TEXT EDITOR SO IT LOOKS LIKE THE BELOW:
Code:
key 115 VOLUME_UP WAKE
key 114 VOLUME_DOWN WAKE
key 116 POWER WAKE
[B]key 172 HOME WAKE[/B]
edit
Amazing. This thread is very much needed song as how the dev thread keeps getting cluttered with posts that wouldn't be there if some one would have read
sent from my Note 3 or Galaxy Gear
Yeah this thread is an awesome idea to leave the general discussion and support issues out of the other thread.
Whenever I select "recovery" it doesn't give me an option to install the rom?
I followed the steps for the root and the add the .zip to my SD card on the phone. When I select the option for recovery it just does a system restore on it. Any help?
You need to flash twrp first
sent from my Note 3 or Galaxy Gear
feature request
[what about to include support fpr AquaMail client?
I'm using it and I think it is the better at the moment
The developer could be interesting....
Just a quick (somewhat noob) enquiry about the Gear and what this ROM can do for it, as I'm thinking of picking up a Note3 + Gear from work (Vodafone), as the watch is free.
Firstly, I hate Touchwiz with a passion! I don't wish for anyone to read that in an angry way, but I'm really not fond of the colours, themeing, etc. of that particular UI. I much prefer vanilla Android and, as such, would look to root the Note3 and install CM or an equivalent on it.
Would I then lose any functionality of the Gear? Can the GearManager APK be installed on a non-TW ROM?
I'll need a bit of an idiot's guide for the whole thing, but it's nothing I can't research.
Pepski said:
Just a quick (somewhat noob) enquiry about the Gear and what this ROM can do for it, as I'm thinking of picking up a Note3 + Gear from work (Vodafone), as the watch is free.
Firstly, I hate Touchwiz with a passion! I don't wish for anyone to read that in an angry way, but I'm really not fond of the colours, themeing, etc. of that particular UI. I much prefer vanilla Android and, as such, would look to root the Note3 and install CM or an equivalent on it.
Would I then lose any functionality of the Gear? Can the GearManager APK be installed on a non-TW ROM?
I'll need a bit of an idiot's guide for the whole thing, but it's nothing I can't research.
Click to expand...
Click to collapse
No. Sadly not.
Or at least not with all the bells and whistles working.
I actually am testing CM11 on my note 3 as I type. I was wondering if someone could link me to the latest gear manager so I could test how it works.
Sent from my Note 3 w/ CM11
ktetreault14 said:
I actually am testing CM11 on my note 3 as I type. I was wondering if someone could link me to the latest gear manager so I could test how it works.
Sent from my Note 3 w/ CM11
Click to expand...
Click to collapse
Here's 2 versions. The latest and the previous one, a lot of people are having problems with the latest, and even Samsung supposedly admitted it was bugged and they were going to release a new one. The previous version seems to work fine for people, and there's no real functional updates on the latest one anyway, so you might prefer it.
Latest version - 1.5.121601
Previous version - 1.5.120903
I couldn't get cm11 to download the necessary apks for gear manager so I restored a tw backup and backed up the apks themselves. When I went to restore them the only ones that would not restore were the weather and svoice. It is paired now with gear manager running in the notifications. Still testing out what works and what doesn't
Sent from my Note 3 w/ CM11
Running 16, removed Ms. Pac-Man for running too slow on the Gear, everything's running smooth.
Sent from Spaceball One.
I have nexus 5 rooted and running null16, could anyone please point me out how to make gear manager to work?has anyone made notifications work? so far i can just make calls from it and syncs the time.I have read everywhere but nothing works so far and i can't seem to find a reliable sorce of information. If we could make something like an app and null to be modified to work with that so we lose gear manager dependency i belive that would be a game changer . Fomey i will donate something pretty soon as i allways apreciate work from people creative like yourself .
EDIT: 15 AUD for you Fomey, thank you for your work !
reboot after install of null_16
i have attempted several times now to install the null_16 on my galaxy gear. after each time i attempt to go into the recovery mode to actually install it, it reboots and resets the device. i have read numerous times to flash the null_03_TWRP2.7.tar.md5 file and i have done this with odin and received a pass at the top left of the odin program and then it reboots the galaxy gear. i then install the null_16 file on the root of the sd card directory with wondershare mobilego (left zipped as noted in several videos i have watched) after this i remove device from charging device and this is when i try to go to recovery modeto install. after getting to recovery and holding power button for approximately 3 seconds and release this is when it reboots and has reset itself. any help would greatly be appreciated and yes it is rooted with supersu. I am sure i am doing something wrong but not sure what.
ernie36564 said:
i have attempted several times now to install the null_16 on my galaxy gear. after each time i attempt to go into the recovery mode to actually install it, it reboots and resets the device. i have read numerous times to flash the null_03_TWRP2.7.tar.md5 file and i have done this with odin and received a pass at the top left of the odin program and then it reboots the galaxy gear. i then install the null_16 file on the root of the sd card directory with wondershare mobilego (left zipped as noted in several videos i have watched) after this i remove device from charging device and this is when i try to go to recovery modeto install. after getting to recovery and holding power button for approximately 3 seconds and release this is when it reboots and has reset itself. any help would greatly be appreciated and yes it is rooted with supersu. I am sure i am doing something wrong but not sure what.
Click to expand...
Click to collapse
Read.
ernie36564 said:
i have attempted several times now to install the null_16 on my galaxy gear. after each time i attempt to go into the recovery mode to actually install it, it reboots and resets the device. i have read numerous times to flash the null_03_TWRP2.7.tar.md5 file and i have done this with odin and received a pass at the top left of the odin program and then it reboots the galaxy gear. i then install the null_16 file on the root of the sd card directory with wondershare mobilego (left zipped as noted in several videos i have watched) after this i remove device from charging device and this is when i try to go to recovery modeto install. after getting to recovery and holding power button for approximately 3 seconds and release this is when it reboots and has reset itself. any help would greatly be appreciated and yes it is rooted with supersu. I am sure i am doing something wrong but not sure what.
Click to expand...
Click to collapse
Download mk7 for your country.... I don't care if you are already on it just do it! Flash with Odin then flash twrp recovery..... Use adb to boot to recovery....... Trust me it works!
Sent from my Note 3 SM-N900A rooted by Designgears
OMG i got it running!
thanks so much for all the work done with this rom... Everything seems to be running perfect...
At first i couldn't get it to flash properly... I was trying everything. Took hours to initially get the recovery going. It ended up being a driver issue and after a lot of reading and troubleshooting i was finally able to get it up and running.
One question that i have that i couldn't find the answer too... Is there any way to have the watch widget (either the stock clocks or watch styler) appear as a full screen widget without the launcher or the status bar at the top... yet keep the status bar and launcher on the other pages? I am assuming that i can't do it after reading countless of pages... Because i do like the full screen watch face.
Thanks again for all the hard work!
---------- Post added at 09:05 PM ---------- Previous post was at 09:00 PM ----------
eroracing said:
Download mk7 for your country.... I don't care if you are already on it just do it! Flash with Odin then flash twrp recovery..... Use adb to boot to recovery....... Trust me it works!
Sent from my Note 3 SM-N900A rooted by Designgears
Click to expand...
Click to collapse
I had to follow this step in order to get the recovery to stick. No matter what i did including flashing the stock recovery then flashing twrp i couldnt get it going until i did this:
almulder1092 said:
Installing Null_ TWRP: (Version as of this tutorial is Null_ 03 TWRP)
Thanks to fOmey for this Null_ TWRP
Installing Null_ TWRP:
Preparation:
Download Null_ TWRP - fOmey
READ THE NULL_ TWRP Original Post
Installation:
Put your Gear into Download Mode
Connect your Gear to you PC.
Open Odin
Click on the PDA Button
Locate the Null_ TWRP file and select it. (It should be a .md5 file, if it is zipped, then unzip it)
Press Start
Once it is completed it will reboot the gear.
Null Quote:
If you find the recovery is not sticking & your Gear wipes when attempting to access recovery after flashing, you must root your Gear prior to installing TWRP again & Run the following commands in ADB:
*NOTE* You will gave to accept a supersuser request popup when executing "SU" command
*NOTE 2* Probably a good idea to run this prior to first installation (To save time)
Code:
$ adb shell
$ su
# mount -o rw,remount /dev/block/mmcblk0p20 /system
# rm /system/recovery-from-boot.p
ADB stands for Android Debug Bridge
If needed "ADB" can be found here on xda - Thanks to shimp208
.[/CENTER]
Click to expand...
Click to collapse
gypsydigi said:
OMG i got it running!
thanks so much for all the work done with this rom... Everything seems to be running perfect...
At first i couldn't get it to flash properly... I was trying everything. Took hours to initially get the recovery going. It ended up being a driver issue and after a lot of reading and troubleshooting i was finally able to get it up and running.
One question that i have that i couldn't find the answer too... Is there any way to have the watch widget (either the stock clocks or watch styler) appear as a full screen widget without the launcher or the status bar at the top... yet keep the status bar and launcher on the other pages? I am assuming that i can't do it after reading countless of pages... Because i do like the full screen watch face.
Thanks again for all the hard work!
---------- Post added at 09:05 PM ---------- Previous post was at 09:00 PM ----------
I had to follow this step in order to get the recovery to stick. No matter what i did including flashing the stock recovery then flashing twrp i couldnt get it going until i did this:
Click to expand...
Click to collapse
You cannot do what you are asking.... But you can set clock widget. Use Nova settings to hide notification bar, dock and scroll indicators then use gesture and button settings to create gesture to accommodate just about anything! I have swype down to open notification bar..... Swipe up open notification app.... Double tap opens app drawer and 2 finger Swipe up opens my dialer! Just set widget long press and resize to full screen. You may have to adjust colums and rows in Nova settings to accommodate whatever widget you are using in order to center properly. Hope this helps!
Sent from my Note 3 SM-N900A rooted by Designgears
On the newest release (16) there is support for custom boot animation and includes the null boot animation. Is that a part of the aroma installer or is the custom null boot animation a part of the rom that you cannot remove? I'd rather stick with the stock if you don't mind.
I am using MIUI Global 7.5| Stable (7.5.1.0 MXDMIDE) ROM & suddenly the notification area and lock screen is not working. The recent button and home button on the device is also not working. I was researching the web regarding the bug is android which might be causing this issue?
See this link here >> Android Police link >>
How To Fix Missing Home And Recents Buttons, And Notification Shade That Refuses To Pull Down After Android Update
Second Link >> Google Plus Link of PaulOBrien >>See this also
Now both the above try to resolve by connecting the mobile to you desktop/lappy in order to execute the command. There is an alternate option available here which might also work >> S7 Edge not showing notifications in tray and "recent apps" button and settings button dnt work
It talk about doing it by following this steps
"And I followed what the user Mike Tompkins said: "Did this using nova launcher. Long press home screen choose shortcut, activities, setup wizard, setup wizard test activity. Creates shortcut, open follow directions. Not sure if it really helps. Didn't have issue."
Here's the fix, being broken down dummy style:
1) Download Nova Launcher & set it as default to replace TouchWiz.
2) Long press on the home screen.
3) Choose Widgets.
4) At the top, under Nova Launcher, scroll to the right & press & hold on Activities and place it somewhere empty on the home screen.
5) Scroll down to Setup Wizard. I saw 2 Setup Wizard options.
6) Under the first Setup Wizard option, I opened it & scrolled down to the 3rd choice which said ".SetupWizardTestActivity". It might be in a different spot for you, but look at the small writing, that's how I saw this one.
7) Select that to create the widget shortcut.
8) Open it. Apparently you're supposed to have a menu to go through and just click through "Next", but there wasn't one for me.
The screen just flashed and then next thing you know, everything works!
But I am unable to find the .".SetupWizardTestActivity"
Any suggestion?
Moreover whenever I am going to developer option I see this message "Developer option is not available for this user"
I am sure I don't have any other user added to this handset.
Help & suggestions?
I have been able to access the device using abd, after adding permission, and have downloaded the logcat files of the device which is attached herewith >> Unable to attach logcat as am a new user, let me know how I can add them.
Now when I am connecting the devices via adb, the devices are showing in adb devices.
When i am executing this command >> adb shell am start -n com.google.android.setupwizard/.SetupWizardTestActivity
I am getting this following message:
Starting: Intent { cmp=com.google.android.setupwizard/.SetupWizardTestActivity }
Error type 3
Error: Activity class {com.google.android.setupwizard/com.google.android.setupwizard.SetupWizardTestActivity} does not exist.
I am not sure why this problem is appearing? any help to fix this issue of home button, recent button, notification issues fixed?
thing happened to you,seems like a system ui absence .. just reflash the rom ot try any other custom roms available.. or just a factory reset might help,,if not hepfull, i would insist you to try a custom rom..
btw are you rooted??
thilak devraj said:
thing happened to you,seems like a system ui absence .. just reflash the rom ot try any other custom roms available.. or just a factory reset might help,,if not hepfull, i would insist you to try a custom rom..
btw are you rooted??
Click to expand...
Click to collapse
Yes the problem seems to be System UI or something, I am not sure. I had rooted the device after the problem appeared, but it didn't able to resolve the issue. Today I had installed MIUI 8.0 on the device and all the problem disappeared, so it seemed like the problem, was with the bug in MIUI 7, or inherent bug when upgrading from KitKat to MM.
Updated version of this ROM: [ROM][TMOBILE][S7_SM-G930T][Oreo 8.0 Rooted][WifiCalling]G930TUVU4CRI2
ROM last updated: 10/30/2018
Introduction:
HUGE thanks to the guys that got this going like root & figuring out hybrid stocks! This ROM is a complete rewrite of my ROM [ROM][TMOBILE][S7_SM-G930T][Oreo Rooted] That ROM doesnt have WifiCalling & I couldn't get it to work for the life of me, so I rewrote it. I started with stock, and slowly stepped back making changes, reinstalling each time, confirming it still worked. About 200 installs later & 1000s of changes, this is the result. Yes, it took a LONG time. Hope you enjoy it! Don't forget to say Thanks so I know it is actually helpful to others, and continue doing this!
Description:
Stock Tmobile Oreo 8.0 modified (G930TUVU4CRF1)
EXTREMELY debloated! Nearly bare minimum, while still retaining hardware functionality. Eg, Samsung Gallery & Camera exist so we get 4k recording, and there aren't errors when we pull up the Gallery to edit, etc. Yes, this means NO Samsung or Android Pay. There could be more apps to debloat but Im out of time for now! (Please provide suggestions if interested)
Everything possible I replace Samsung with Google
Solid ROM. It was actually kind of slow for me, but I'm curious how this works for others.
Xposed is part of the guide, which will give you infinite customization & tweak-ability
If you hate Samsung SW and just want a solid working ROM with very few install options to get you up and running this is for you.
This will delete all of your data on the phone! (Not external SD card) This is the only way so don't ask. Backup your data!
Features:
Tmobile Wifi Calling works, along with Visual Voicemail & Mobile Hotspot
Many Aroma Installer app options
(Optional) KevinsFavorites option in Aroma. I'm not sure I'd recommend it due to my tastes. If you're looking for some good common apps tho, it includes: Amazon, AmazonMusic, AquaMail, Gmail, GoogleDrive, GoogleKeep, GooglePhoto, Hangouts, IFTTT, Pandora, RootBrowserClassic, TitaniumBackup, Uber, & Wink (If you install these and want to remove them later, use TitaniumBackup (or similiar) to uninstall
Root Features: See Downloads->Recommended Root Zip & say Thanks!
Debloated
De-Knoxed
Decrypted /data/ partition
OTAs disabled
Speed & Build Prop Tweaks
Dual speaker
Ruthless Launcher
Apps
AdAway
AOD Clock Face Themes
CPUSpy
DisableService
Kernel Adiutor
Samsung Video Editor and Trimmer
Xposed
Many more...
Download Links:
Base.7z & Oreo_Kevin71246Modded_v3.#.#.zip
Installation:
This will delete all of your data! If you continue, you acknowledge that the Author is NOT responsible for anything that happens to your phone!
Summary (for Pros)
Flash Oreo stock
Root
Flashfire
Oreo_Kevin71246Modded_v3.1.##, Auto-mount, Mount /system read/write Option
Go through Aroma setup. When finished, it should boot to Recovery (if not do this). Do a "Wipe data/factory reset"->Reboot
Detailed Steps
Install Stock Oreo:
Download mode & Setup
Make sure you have latest device drivers setup on your PC
Enable USB Debugging on phone in Developer Settings
Boot phone into Download Mode:
Turn off your device
Press and hold Volume Down + Home + Power button
When you see the warning screen, release buttons & press Vol UP. Phone should say "Downloading..."
Download and unzip Base.7z to PC (This contains stock Oreo, ODIN, & root)
ODIN
Open ODIN on PC (\Base\Odin_313.exe)
Connect USB from PC to phone. ID:COM in Odin should turn Blue with a COM port
Select AP, BL, CP and CSC files from the \Oreo_Stock\Base\ folder for corresponding files
Select HERO2QLTE_USA_VZW.pit
Select Start
Finished: Phone will reboot & show Carrier screen for 3-5mins. Wait until Setup screen & go through quickly (bare minimum) since you'll wipe it again. Once in Android, go to Settings->Display->Screen resolution->WQHD->Apply
Root Instructions: (+Flashfire, SuperSU)
Reboot phone into Download mode
Odin
AP: Select \Base\Root\AP_SM_G930_OREO_ENG_BOOT.tar
Start-> Wait for phone to boot to Android OS
Root
Double-click \Base\Root\cmd-here.exe & Type: root.bat [enter]
Option: 1 (Install Root No tweaks) (Or pick whatever you want)
*Note: With this system root, do not update su binary. Disable notifications for SuperSU app. Don't flash any superuser zips in recovery that are not made by jrkruse
Install Custom Hybrid ROM & Xposed
Download & copy Oreo_Kevin71246Modded_v##.zip to phone
Flashfire
Open Flashfire on phone
Red + symbol->Flash Zip or OTA->Oreo_Kevin71246Modded_v#, Auto-mount, Mount /system read/write Option->Check mark
Click Lighting bolt at bottom-> OK
Phone will reboot to Aroma. Go through setup. (See above for what's in KevinsFavorites)
When finished, allow Aroma to exit.
It should reboot into Recovery (If not, do this: immediately hold Vol-Up btn+Home btn until you see recovery on screen. If you missed it, try again: hold Vol-Down+Pwr btn ~10sec until phone restarts & immediately hold Vol-Up btn+Home btn until you see recovery on screen.)
In recovery: Factory Reset->Yes->Restart phone
*Wait 5-10min on loading screens
Go thru Android setup. Ignore "Xposed Installer has stopped" error
Followup-Steps:
Set Dialer: Phone Settings->Apps->Menu->Default Apps->Calling App->Select Phone
Recommendations:
Xposed
Setup Xposed: Xposed Installer app:Install framework option & restart phone
Xposed Installer app: Settings button (3 lines)->Download->Search "GravityBox [O]"->Click it->Versions tab->Download->Install->Back arrow (upper left)->Settings->Modules->Check box next to GravityBox [O]->Restart phone
GravityBox [O] Tweaks: (Open GravityBox app)
Battery indicator: Statusbar tweaks->Battery settings->Turn on Master switch->Battery indicatory style: None->Battery percent text...->Back
Clock: Statusbar tweaks->Clock settings->Turn on Master switch->Center clock...
Firefds Kit [O] Tweaks: (Install same way as Gravity box)
This is a supplement to Gravitybox. Things of note: Advanced power menu, call recording, & disable bluetooth toggle popup, etc
Known Issues:
Visual Voicemail may fail to register, but restart phone and give it a few hours. It works eventually.
RCS (Rich Communication Services/AdvancedMessages/Chat) texts don't show up in Android Messages & Textra, etc apps (This is an issue on stock as well!!)
Fix: (Use Samsung Messages)
How to Install Samsung Messages via ADB (Easiest way though is just reinstall!):
Download Messaging_SEP81.zip, unzip, & manually copy apk to phone via usb/Windows My Computer
adb shell (Get into shell to run beow commands)
su (Run as root)
mount -o rw,remount /system (Mount system read/write since default it read-only)
chmod 755 /system/priv-app/Messaging_SEP81 (Set permissions on folder)
chmod -R 644 /system/priv-app/Messaging_SEP81 (Set permissions on apk file)
ls -l /system/priv-app/Messaging_SEP81 (Check permissions - Should be: -rw-r--r-- 1 root root - not sure what 1 & 2 is)
ls -l /system/priv-app | grep "Messaging" (Check permissions - Should be: drwxr-xr-x 2 root root)
reboot (Reboot device)
Changelog:
Version 3.1.32: First stable build
Ver 3.1.36:
-Disabled encryption on /data/ partition to resolve "Bluetooth paired devices deleted after reboot" issue & so mods play nicer with ROM
-Fixed "Device not supported" error on Google Phone app
Ver 3.1.37:
-Added most of the apps I replaced or added as options in Aroma Installer now
Credits:
- @jrkruse & @klabit87 for Root
- @partcyborg for helping jrkruse
- @jrkruse for his similar ROMs as guides & help
- @Lanc-City for assistance in ROM modding
- @gustco for eng boot.img
- @Raymonf for modified odin
- @amarullz for Aroma Installer
- @Chainfire for FlashFire & SuperSU
- @rovo89 for Xposed
- @JaeKar99 for the cool & colorful boot animation
- @mrRobinson for AdAway ADAway.org
- Brandon Valosek for CPUSpy
- WangQi for DisableService
- Willi Ye for Kernel Adiutor
- @shubby for Ruthless Launcher
- @Craz Basics for Dual Speaker Mod
...
- Please PM me if you were forgotten!
Some screenies:
Saved2
Saved3
Well nice job!
jrkruse said:
Well nice job!
Click to expand...
Click to collapse
...but your'e the best! (You & I both know I couldnt have done it without all your other work!)
Once I FINALLY got WifiCalling to work, I thought... Imagine ALL the S7 XDA members out there with crappy Tmobile signal across Rural America that could TOTALLY use Wifi Calling!!! Haha, but seriously!! & that thought was the birth of this thread
kevin71246 said:
...but your'e the best! (You & I both know I couldnt have done it without all your other work!)
Once I FINALLY got WifiCalling to work, I thought... Imagine ALL the S7 XDA members out there with crappy Tmobile signal across Rural America that could TOTALLY use Wifi Calling!!! Haha, but seriously!! & that thought was the birth of this thread
Click to expand...
Click to collapse
Is this Ufirm firmware?
jrkruse said:
Is this Ufirm firmware?
Click to expand...
Click to collapse
I have so many FW packages on my PC at this point, from so many places that I used while trying to get this to work, but I think it might be a package from one of your threads(?) Since I'm not exactly sure what you're asking regarding "Ufirm FW", I'll elaborate hoping that answers your question. (Tho I'm thinking you mean the U variation/unlocked. So based on these stock files below I guess the answer is no.) If you're question is really, "is it possible to get tmobile wifi calling to work on a U model #", then I'd have to really think about that. But at this point I don't have an answer. I can tell you a million dependencies about it tho! (I seriously have hundreds of revisions I made while testing, & notes. The symbolic & meta links in Aroma initially broke it, as I found out after a week or so of testing - wish I knew a bit more about them, and why they're all there, then I'd know what was wrong about them...)
High-level process:
1)Flash Base/Stock/Oreo Rom:
- AP_G930TUVU4CRF1.tar
- BL_G930TUVU4CRF1.tar
- CP_G930TUVU4CRF1.tar
- CSC_TMB_G930TTMB4CRF1.tar
- HEROQLTE_USA_VZW.pit
2)Root with your method
3)Flash Xposed framework & my ROM (it's a "start with stock then remove what we don't want" type of Aroma/Edify script)
jrkruse said:
Is this Ufirm firmware?
Click to expand...
Click to collapse
BTW, any idea how to prevent the "verification failed" error I mention in the OP steps, after flashing Xposed framework? I tried flashing dm-noverity but no luck. At least my guide covers it at this point tho... Thanks again
kevin71246 said:
BTW, any idea how to prevent the "verification failed" error I mention in the OP steps, after flashing Xposed framework? I tried flashing dm-noverity but no luck. At least my guide covers it at this point tho... Thanks again
Click to expand...
Click to collapse
If you choose the keep safestrap option during root the it will flash the system/vendor/etc/ fstab.qcom that totally removes data encryption but when that fstab.qcom is flashed it also requires a data wipe for phone to boot then when you install xposed you won’t see that error but either way you end up wiping data so your choice
Sent using some kind of device I modified
It works perfectly!!
I have not had any problems so far, here I leave you for the link to download and try those who are interested in VIPER4ANDROID: https://drive.google.com/file/d/1572ORe6TOrsRBuxWWBChH-WMnxkvcUjH/view?usp=drivesdk
You just have to flash it with Flashfire, but if you do not pull them, let me know Thank you very much !!! Kevin for the effort!
---------- Post added at 10:17 PM ---------- Previous post was at 10:15 PM ----------
I have not had any problems so far, here I leave you for the link to download and try those who are interested in VIPER4ANDROID: https://drive.google.com/file/d/1572ORe6TOrsRBuxWWBChH-WMnxkvcUjH/view?usp=drivesdk
You just have to flash it with Flashfire, but if you do not pull them, let me know Thank you very much !!! Kevin for the effort!
First, I want to thank you so much kevin71246. I tried your previous version as I was sick and tired of how sluggish my phone felt after the last two T-Mobile OTA updates. So far the experience on the phone has been great but I wanted to post about an issue I had with that version to see if anyone else has come across it or can figure out what is going on. The reason I am making this a reply in this thread instead of your other is because I will be flashing this update shortly but I want to get the ball rolling on the issue first.
I went through the whole process, installing the minimum with Google Apps, though I did restore everything previously installed once I log in with my Goggle Account. I am unsure if this contributed to the problem but I will not be restoring apps on the next try. It seems no matter what process I attempt to connect my Ticwatch E to my S7 the Wear OS app will not recognize it which causes the watch to get stuck in the setup phase, making it useless. This was after multiple and different connection attempts, resets, reboots and factory (watch only) restores. The watch will show up under bluetooth and create the initial connection but it will not stay connected. Anyone have any idea? Is this ROM missing something?
Edit: Mid way through the install, I wanted to note that I checked for the issue after doing the "Install Stock Oreo" but before Root and everything worked as it should. Wear OS sees the watch instantly and Bluetooth connects fine.
Edit: So I am a day into using the ROM and I am still having issues. While it will connect and work perfectly fine now, when ever I do a reboot of the phone the watch no longer connects. I will just get constant Bluetooth Connection Requests, every single time the watch tries to get data, and it never actually connects. To fix this I need to do a complete reset of the watch and do the whole setup process again. As you can imagine this is no good, expecting to wipe my watch every time my phone reboots makes it still almost useless.
charredchar said:
First, I want to thank you so much kevin71246. I tried your previous version as I was sick and tired of how sluggish my phone felt after the last two T-Mobile OTA updates. So far the experience on the phone has been great but I wanted to post about an issue I had with that version to see if anyone else has come across it or can figure out what is going on. The reason I am making this a reply in this thread instead of your other is because I will be flashing this update shortly but I want to get the ball rolling on the issue first.
I went through the whole process, installing the minimum with Google Apps, though I did restore everything previously installed once I log in with my Goggle Account. I am unsure if this contributed to the problem but I will not be restoring apps on the next try. It seems no matter what process I attempt to connect my Ticwatch E to my S7 the Wear OS app will not recognize it which causes the watch to get stuck in the setup phase, making it useless. This was after multiple and different connection attempts, resets, reboots and factory (watch only) restores. The watch will show up under bluetooth and create the initial connection but it will not stay connected. Anyone have any idea? Is this ROM missing something?
Edit: Mid way through the install, I wanted to note that I checked for the issue after doing the "Install Stock Oreo" but before Root and everything worked as it should. Wear OS sees the watch instantly and Bluetooth connects fine.
Edit: So I am a day into using the ROM and I am still having issues. While it will connect and work perfectly fine now, when ever I do a reboot of the phone the watch no longer connects. I will just get constant Bluetooth Connection Requests, every single time the watch tries to get data, and it never actually connects. To fix this I need to do a complete reset of the watch and do the whole setup process again. As you can imagine this is no good, expecting to wipe my watch every time my phone reboots makes it still almost useless.
Click to expand...
Click to collapse
I believe I know what the issue is, I'm testing a fix (for THIS ROM) as we speak. Stay tuned. Maybe tomorrow if I have time and it works I'll update the OP. BTW, this ROM and my other ROM are TOTALLY different. Thanks for the feedback!
FranMLG said:
I have not had any problems so far, here I leave you for the link to download and try those who are interested in VIPER4ANDROID: https://drive.google.com/file/d/1572ORe6TOrsRBuxWWBChH-WMnxkvcUjH/view?usp=drivesdk
You just have to flash it with Flashfire, but if you do not pull them, let me know Thank you very much !!! Kevin for the effort!
Click to expand...
Click to collapse
What do you mean by this? "but if you do not pull them, let me know"
And tell me more about Viper4Android, and if it works solid for you on this ROM...then I'll consider adding it. Thanks!
New version, see change log in OP for details.
Yeah i.a give this a shot in a little. Do I need to root phone or can I just flash through Odin. Sorry not used to this locked bootloader crap..... s8crj1 are the last 6 digits of the software I'm on. I did receive the latest update will this effect me installing this. Sorry as I said not used to this locked bootloader crap.
jrkruse said:
If you choose the keep safestrap option during root the it will flash the system/vendor/etc/ fstab.qcom that totally removes data encryption but when that fstab.qcom is flashed it also requires a data wipe for phone to boot then when you install xposed you won’t see that error but either way you end up wiping data so your choice
Sent using some kind of device I modified
Click to expand...
Click to collapse
Hi, why you have to flash this - HEROQLTE_USA_VZW.pit on 930t, is it ROM specified? if I do and don't then what are pro and cons?
---------- Post added at 01:36 PM ---------- Previous post was at 01:26 PM ----------
josh2020glacier said:
Yeah i.a give this a shot in a little. Do I need to root phone or can I just flash through Odin. Sorry not used to this locked bootloader crap..... s8crj1 are the last 6 digits of the software I'm on. I did receive the latest update will this effect me installing this. Sorry as I said not used to this locked bootloader crap.
Click to expand...
Click to collapse
since bootloader is locked you can't use TWRP so you have to use Flashfire to install this ROM, as you know flashfire required root so you have to setup the base per OP and then root the base then install the ROM and then root it again, read the first page I don't think you will get a instructions more detailed then his
Okay so I just realised I was posting comments on the old thread, my bad. Coming back to the question, can the boot animation be changed? I've messed with the qmg files in an attempt to replace the weird, nauseating rainbow animation but even after overwriting the latter, it persists. Looking forward to a reply kek
Alkan3 said:
Okay so I just realised I was posting comments on the old thread, my bad. Coming back to the question, can the boot animation be changed? I've messed with the qmg files in an attempt to replace the weird, nauseating rainbow animation but even after overwriting the latter, it persists. Looking forward to a reply kek
Click to expand...
Click to collapse
Nauseating rainbow? LOL. Sorry. This is much more of a general question though, that wouldn't exactly pertain to this ROM specifically. And given I don't have an answer, I'd try searching BootAnimation How-Tos to get this customized. The ONLY thing I did regarding this was replaced the existing files with the rainbow ones. That's it. Apologies in advance.
Just discovered an issue: RCS (Rich Communication Services / Chat) texts don't show up in Android Messages app. See "Known Issues" in OP for a solution. BTW I posted a new ROM version a few days back that allows many choices in Aroma Installer. Make sure to pick Samsung Messages (instead of Google), so you get RCS chat text messages!
Warning: Don't install an older OS on top of a newer one, you may have a very high chance of bricking your phone. If you are ready to take risk of bricking for the sake downgrading / requirement or already bricked, then only attempt the following . you need an autoloader & build version exactly matching to your phone.
I have downgraded successfully from Build ABP244 (Android 8.1.0) to AAX862 ( Android 7.1.1)
Caution: Blackberry/Google may introduce any constraints against downgrade through future OTA updates to strengthen the security etc.
My Phone Details:
BlackBerry, Keyone, Special Edition, Dual Sim, India.
PRD: PRD-63764-001 (Group: KEYone BBB100-7)
OS Build: ABP244 (Android 8.1.0)
[Upgrade history from ABB216 (android 7.1.1) to ABG076 (Android 8.1.0 ) ….to…to ABP244(Android 8.1.0 )]
1. I have checked phone PRD, by typing the following code into the phone dialer:
*#2886#
Clicked on "MANU"
Clicked on "Traceability"
There you can see phone's manufacturer no: Mine is PRD-63764-007 (for example) (photo#1 in attachment)
Exited from the menu click "PASS"
Then again clicked "PASS"
At the end of the menu clicked "exit"
2. compared with PRDs master at https://tclota.birth-online.de/ and download suitable Autoloader (ROM and its flasher)
3. AAX862 (it is written as AAX863 but actually AAX862) which is suitable to above PRD No is downloaded from
https://androidfilehost.com/?fid=890129502657599708
Topic: https://forums.crackberry.com/blackberry-keyone-f445/blackberry-keyone-autoloaders-1108372/
4. Removed passwords /patterns / finger prints from screen lock (settings>security>screen lock>select none), Removed google account [ settings>Users & Accounts (or Accounts in case of android 7.1.1 ) >googel>options>Remove, remove google]
[removed find my device at device administrator , find from Google Account (settings> google> google account >options (3 horizontal line at rhs bottom)>manage devices>black berry keyone>remove>remove- i have done but this may not be needed]
Theory: On BlackBerry devices powered by Android, Factory Reset Protection (FRP) is enabled by default to reduce the value of a stolen device. This feature prevents the use of a BlackBerry device powered by Android unless authorized by the known user.
Once you sign in with a Google account, FRP is enabled. Once enabled, only users who have reset their device via Settings > Backup & reset > Factory data reset may proceed through the setup wizard without being prompted to enter the Google login information that was previously used on the device before resetting. This form of reset is the only reset flow that is considered trusted.)
[I have reset the device from Android (I have done, but this may not be needed]
[Enabled Developer options and usb debugging was made on (I have done, but this may not be needed)]
5. Rebooted to fastboot mode by switching off >pressed and held volume down button and simultaneously , pressed power button till the phone restarts , then released volume down, once fastboot loads
[>select fastboot by pressing volume button , I have done, but this may not be needed (no further power button press)]
(photo#2 in attachment)
6. Installed BlackBerry-USBDrivers-5.0.0.2 downloaded from the link below for windows and restarted the windows.
Downloaded from https://swdownloads.blackberry.com/Downloads/entry.do?code=4EE0932F46276313B51570F46266A608
7. Connected it to Windows PC through USB port (Windows device manager photo#3 in attachment)
8. Extracted AAX862Universal.7z with 7z
9. Browsed to the above extracted folder, double clicked on file flashall.bat to run batch file (other option available is flashallnowipe.bat ).
10. Entered y in response to question …….. to continue (y/n), (photo#4 in attachment)
it immediately rebooted to fastboot again (photo#5 in attachment) but the process was going smooth.
Process successfully completed (photo#6 in attachment) and phone is rebooted to OS in Auto
Sometimes, the phone can get stuck when booting for the first time. If this happens to you, make sure you've waited long enough, and then just hold the power button down to force a reboot.
It needs simcard or internet to reach user interface.
Caution:
When Autoloader build no AAY819 (common/universal to many PRDs but not all) downloaded from https://mega.nz/#!wVxBxYZA!BahovAZA_...M5Ic_QkJigS3LI and flashed, flashing is successful but when is updated from App Drawer >updates…22 mb downloaded , install started , rebooted and installed to 100% but message appeared that “ This is embarrassing, the update failed, try to install again later, your phone will reboot after 120 sec…. Error code 3305” , It reboots and build no shows as ABB216 but 2nd Sim is not working.
Reflashed with Build No AAX862, both sims and other hardware are working normal , Further when update option is used it is getting updated to ABB216 without any error again both sims and other hardware are working normal .
Stop updates
(this facility not available in Oreo)
Pre requisite : disconnect phone from Internet (Put off Wifi and mobile data)
1). App drawer>Updates>Options(3 vertical dots)>settings>system> check for updates –Off (=never), Automatically download – off (=ask to download)
2). App drawer>Updates>Options(3 vertical dots)>settings>System applications > Automatically update –off (=never), new app notifications –off
If system update already started or pre -requisite is forgot: Go to Settings>Apps>Updates>Storage>clear data , now repeat step 1 & 2
Advantages:
1) The feel, the look , the smoothness , the speed , low in bugs of the build ABB216. It is excellent
2) “True phone dialer & contacts” app has all most all the features, you ask it has already has, like blue mark for outgoing calls, green for incoming, saffron for canceled, red for missed call as history (it cannot work properly with Oreo latest due to restriction on call log, restrictions increased in ascending order from Build ABG076 to ABJ879 to ABM376 to ABP244 ). Never hangs while calling (OS).It has contact share through SMS with pleasant interface, excellent dual sim management etc.
3) SMS Organizer by Microsoft also appears to be facing restrictions with Android 8.1.1 , hence it will be working excellently.
4) Rear camera (of Build ABB216)a lot nearer to true to actual ( than Oreo Build ABG076)
5) Light Manager works flawless with very low power consumption for customization of notification LED as keyone has no built in facility to customize.
Disadvantages:
1) less secured than Oreo,
2) 7.1.1 Camera not far better than improved camera by build ABP244.
3) Oreo has configurable alarms but same is achieved in Nougat with updating of Time App
4) Oreo has PIP useful e.g. for maps
5) Google playstore installs regular patches without our control making older android slow
6) call history symbols are rarely used and minor , further they can be seen at stock phone (the issue still exist with Oreo compatible TruePhone v1.78) advantage 2 may be considered almost nullified
7) file Explorer scrolling goes back if some shaking taking place.
8) Download is interrupted few times from playstore even when Download from mobile data
9) usb data transfer is slow
10) all features of Silence premium do not disturb app are not working ( my favourite profiles app ) like whitelist and repeat calls will enable ring, interruptions to silence mode (app is defective up to v 2.15f ) but they have created v2.17 which works as designed but does not install on nougat.
11) Light flow can be installed in place of Light Manager on Oreo , hence advantage 5 nullified
However I am happy with downgrade and will maintain as long as possible or till I get apps to get the nougat like flexibility and user experience as per above mentioned facts at advantages.
Thanks to the respective contributors& community. This is only experience sharing , no credit or responsibility.
As the time progressed, disadvantages increased and advantages reduced . I have re-upgraded please on 22.12.19 especially due to functional requirement of Silence Premium as mentioned above and no equivalent is available.
@knreddy, good work, please do you know if this exact firmware will work on the sprint variant of the keyone?
updated 8 times
One ui gsi to all samsung
no boot loops all features are working now i'm using one ui 5 it's pretty fast
For those who want, the best 3 game acceleration magisk modules are below, I've been using them for a long time, it's fine
magisk should be delta beta and always update (optional download below)
download the photos from below I couldn't get it because there is a photo limit
problems
samsung camera not working use other camera apps
flash the 2 magisk modules below to repair developer options
big icon and big keyboard (only tablet like this)
no smartview
No charging animation when device is off (like lineageos gsi)
freezes in games (turn off cpu limitation in power saving mode and limit app and home screen open it will reduce freezing and fps problem)
samsung tablet search not working
sometimes boot problem when installing magisk module flash the magisk module below
Note:
workaround: if a screen says the device is locked, turn off the screen a few times and turn it on again if it doesn't work, restart it
permanent solution : delete system priv-app knoxguard folder with es file manager
One ui 5 S21FE debload port gsi (4.26gb) link : https://sourceforge.net/projects/ni...neUI-AB-13-20230120-NipponGSI.img.gz/download
stable One ui 5 gsi link : https://sourceforge.net/projects/ni...-5.0-AB-13-20230102-NipponGSI.img.gz/download
One ui 4 tab s6 lite gsi link : https://sourceforge.net/projects/nippongsi/files/Generic - OneUI-tabs6-4.1 - NMOZP5BUQX/OneUI-tabs6-4.1-AB-12-20220807-NipponGSI.img.gz/download
One ui 5 tab s8 lite gsi link : https://mega.nz/file/CSxWRK5Q#tcS-DIJfldf_HqsX9tdUkBRSu5p6qjmVsllIcJS0vJo
optional nokia ui link : https://sourceforge.net/projects/nippongsi/files/Generic - NokiaUI-13.0 - LBOWIGZLFM/NokiaUI-13.0-AB-13-20230127-NipponGSI.img.gz/download
Telegram : {Mod edit. Oswald Boelcke}
If you want, I can add apps that need crb android kitchen and one ui (currently I'm planning to add tab s6 and s21fe galaxy store eye relief shield and opencamera)
Thanks nippon gsi and Hausemaster
some google translation errors
Is there any way that we can get the tablet UI, I don't know if there is any way to do it.
WigettaGaming said:
Is there any way that we can get the tablet UI, I don't know if there is any way to do it.
Click to expand...
Click to collapse
Even if you do it gives an error
I can't boot this error on the device as a Lock Screen prevents it from starting and it ends up restarting endless times.
my device is T500 A7 Wifi, GSI not start, bootloop in screenlocked "phone is unathorized".
make sure magisk delta beta version and update magisk (latest version below)
ismail demirbaş said:
make sure magisk delta beta version and update magisk (latest version below)
Click to expand...
Click to collapse
Even after following all the steps, the device does not start the GSI, they just reach the start screen and soon after informing that it is blocked and restarts several times in an infinite loop and does not start the system in a way, it is regrettable I would very much like to try the One UI 5.
After doing the step by step of turning off the device if it displayed the lock screen and turning it off and if it didn't work I could restart, that's where the error is, after restarting it doesn't initialize in any way, it goes into an infinite loop.
When you installed the software, did you remove anything or install a difficult magisk module, format the device and reinstall the rom
It has to be magisk delta beta, it doesn't support this rom because its stable version is old
infinite boot happens when root captures or an important file is deleted
try flashing the empty product file
please report the results
I'm coming back to report the results, and yes for me it worked fine, the blocking solution was to eliminate the "knox guard" of the applications, I was using the Tab S6 Lite's GSI and that worked very well for me, even Dex was working , but I believe they did a very big debloat on the rom, maybe I can try to port the GSI Nippon S6 Lite one day,
Thanks! Worked on my Tab A7 Lite!
mendesvictor said:
I'm coming back to report the results, and yes for me it worked fine, the blocking solution was to eliminate the "knox guard" of the applications, I was using the Tab S6 Lite's GSI and that worked very well for me, even Dex was working , but I believe they did a very big debloat on the rom, maybe I can try to port the GSI Nippon S6 Lite one day,
Click to expand...
Click to collapse
system knox guard i couldn't find it
how did you find
I still couldn't solve the phone locked problem. The problem is that the device detects the bootloader as closed even though it is open (guess this problem will be solved if we remove the root)
Phone locked is not displayed as long as root is up to date and rebooting the device
ismail demirbaş said:
Phone locked is not displayed as long as root is up to date and rebooting the device
Click to expand...
Click to collapse
You can find knox guard in system /priv-app to remove knox guard , remember to only remove it from system /priv-app, I did this and it was working normally with no blocking interferences on my One UI 5 and 4.1
mendesvictor said:
You can find knox guard in system /priv-app to remove knox guard , remember to only remove it from system /priv-app, I did this and it was working normally with no blocking interferences on my One UI 5 and 4.1
Click to expand...
Click to collapse
thanks, I had looked at priv-app before, but I had not seen it, I just found it, the system did not reduce the slowness, but the lock solved it.
mendesvictor said:
I'm coming back to report the results, and yes for me it worked fine, the blocking solution was to eliminate the "knox guard" of the applications, I was using the Tab S6 Lite's GSI and that worked very well for me, even Dex was working , but I believe they did a very big debloat on the rom, maybe I can try to port the GSI Nippon S6 Lite one day,
Click to expand...
Click to collapse
tab s6 gsi goes to boot for me, it doesn't allow me to uninstall, it would be good if twrp could be removed, the easiest way is to remove crb (without editing system.img)
Link: https://forum.xda-developers.com/t/tool-windows-kitchen-crb-v3-1-6.3947779/
one ui 4 tab s6 do not select wifi during installation and install without sim card if possible
thanks, I searched for priv-app before but I didn't see it (maybe because I was using a device in low light) I used tab s6 before, knoxguard is harder to remove then because the phone is locked, then it goes to boot immediately. and the power button did not work, it did not compile well and there is no big difference compared to the original one ui 4, so I do not use it, I am waiting for the one ui 5 tab s6 version
My suggestion to you is to use crb, but only for file removal, otherwise you may experience a boot error (if you know about crb, there is an update, I thought I'd let you know again)
ismail demirbaş said:
thanks, I searched for priv-app before but I didn't see it (maybe because I was using a device in low light) I used tab s6 before, knoxguard is harder to remove then because the phone is locked, then it goes to boot immediately. and the power button did not work, it did not compile well and there is no big difference compared to the original one ui 4, so I do not use it, I am waiting for the one ui 5 tab s6 version
Click to expand...
Click to collapse
Hi, there won't be one ui5 from the tab s6, but there'll soon be a one UI 5 from tab s8, as I opened a request to Nippon to make an s8 tab gsi...
ismail demirbaş said:
one ui 4 tab s6 do not select wifi during installation and install without sim card if possible
Click to expand...
Click to collapse
Also, just to let you know, the Power and volume buttons don't work on the tab s6 gsi...
Hausemaster said:
Hi, there won't be one ui5 from the tab s6, but there'll soon be a one UI 5 from tab s8, as I opened a request to Nippon to make an s8 tab gsi...
Click to expand...
Click to collapse
well thanks
Hausemaster said:
Also, just to let you know, the Power and volume buttons don't work on the tab s6 gsi...
Click to expand...
Click to collapse
I knew but thanks
ismail demirbaş said:
I knew but thanks
Click to expand...
Click to collapse
Sorry, I didn't read the above posts, my bad..
ismail demirbaş said:
well thanks
Click to expand...
Click to collapse
I'll post the link once it's available...
hello, i solved the samsung tab s8 lite boot problem, i'm using it now, they removed a lot of things, i added it to a few programs
Added programs
galaxy store
game launcher (including game booster)
samsung gallery
smart view and related services
I have added the necessary applications for the smart switch.
color panel added
wallpaper editing added
emergency section added
health section added (maybe needed)
Removed apps:
removed samsung dex because it doesn't work
knoxguard removed
settings - battery and device maintenance - security section removed
group sharing removed
problems
screen rotation not working
settings - battery and device care - battery - background apps - sleep mode, deep sleep mode not working
link : https://mega.nz/file/CSxWRK5Q#tcS-DIJfldf_HqsX9tdUkBRSu5p6qjmVsllIcJS0vJo
ismail demirbaş said:
hello, i solved the samsung tab s8 lite boot problem, i'm using it now, they removed a lot of things, i added it to a few programs
Added programs
galaxy store
game launcher (including game booster)
samsung gallery
smart view and related services
I have added the necessary applications for the smart switch.
color panel added
wallpaper editing added
emergency section added
health section added (maybe needed)
Removed apps:
removed samsung dex because it doesn't work
knoxguard removed
settings - battery and device maintenance - security section removed
group sharing removed
problems
screen rotation not working
settings - battery and device care - battery - background apps - sleep mode, deep sleep mode not working
link : https://mega.nz/file/CSxWRK5Q#tcS-DIJfldf_HqsX9tdUkBRSu5p6qjmVsllIcJS0vJo
Click to expand...
Click to collapse
a) download the product.img from above link
b)Reboot to recovery from magisk app, then, in twrp, click on 'Reboot' button
c) click 'fastboot'
d) the device will now reboot and then after a few seconds, a twrp ui will appear with the text 'fastboot'
e) connect your device to a pc with the latest version of platform tools and drivers installed
f) run these commands in order
fastboot flash product product.img
fastboot erase system
fastboot resize-logical-partition system 4700000000
fastboot reboot recovery
maybe multidisabler to disable knox
ismail demirbaş said:
a) download the product.img from above link
b)Reboot to recovery from magisk app, then, in twrp, click on 'Reboot' button
c) click 'fastboot'
d) the device will now reboot and then after a few seconds, a twrp ui will appear with the text 'fastboot'
e) connect your device to a pc with the latest version of platform tools and drivers installed
f) run these commands in order
fastboot flash product product.img
fastboot erase system
fastboot resize-logical-partition system 4700000000
fastboot reboot recovery
Click to expand...
Click to collapse
samsung doesn't have fastboot it can only flash tar or md5 files
Stephanizgo said:
maybe multidisabler to disable knox
Click to expand...
Click to collapse
not deleted with knox multi disable
Stephanizgo said:
samsung doesn't have fastboot it can only flash tar or md5 files
Click to expand...
Click to collapse
you misunderstood open twrp if it is not up to date update twrp twrp reboot click there is a fastboot button press it it will open twrp again but in a different way like twrp fastboot mode
How can I fix the brightness issue
I have a brightness issue on all Samsung GSIs