Related
Alright, so following some prodding, searching, and questioning, I flashed MIUI V6 to my BLU Vivo Air alongside TWRP.
I will update this post with a detailed, step-by-step guide including my own personal mirrors for your convenience and those of you without 4PDA accounts, which is the Russian equivalent of XDA.
Upon booting, I noticed apps force closing without being launched. Namely Hangouts and Newsstand. I'm sure reinstalling them will resolve the issue rather quickly.
Stay tuned for updates.
Update 1:
TWRP had difficulty mounting data and cache for me, and was unable to format them. This led to applications force closing, window mishaps, and accounts glitching out. I just flashed Carliv recovery, and flashed MIUI with it. Flashing gapps at the moment, and will update you on my progress.
Update 2:
Currently attempting to format data (success), cache (success), and dalvik (success).
Update 3:
Rebooting into MIUI V6, checking if I've entered a bootloop.
5 seconds - Boot animation reached, "MIUI Pro."
165 seconds - Still booting.
180 seconds - Setup screen reached, MIUI V6 flashed successfully.
Update 4:
Google apps flashed successfully, no redraws or force closes this time. Had an issue with the keyboard not registering as being selected, Google voice typing appeared as the default. Pull down notification shader and "choose input method" to select MIUI Smart Keyboard. Signed into Google successfully. Will run preliminary tests on video playback, camera, and multitasking.
Guide:
If you mess up your phone, it is on you, and I am not to be held liable for your actions. This is your responsibility. A lack of planning on your part does not constitute an emergency on mine. With that out of the way, if you encounter troubles, I am more than happy to help you.
Step 1:
Root your phone using one of the links provided. Click HERE for method 1, or HERE for method 2. I personally used method 1 because it was the first I saw. They both get the job done.
Step 2:
Install THIS application (Settings -> Security -> Unknown Sources), and install a recovery. I installed Carliv recovery, and had no problems with it. You can also install TWRP, however, it had issues mounting data and cache. This left it unable to factory reset when I flashed MIUI, which subsequently led to problems. I do not recommend flashing TWRP - You have been warned. Carliv recovery says it can't "mount" cache, although when formatting it does so without a problem. I believe Carliv is supposed to be touch-based, although the touches weren't responding for me. The controls are as follows: Volume +/- for navigating, Power for selecting, and the Back key for, you guessed it, going back.
Step 3:
Install MIUI V6, located HERE, and then install Google Apps, located HERE. After installing, factory reset the device from recovery and reboot into the system. I posted my timestamps at the top of the post, so you can get an idea of how long your flash/boot process should take.
Step 4:
Basic setup. Be ready to fix your keyboard if you had the same issue I did, which isn't even necessarily a problem. Choose WLAN network and sign into your accounts, then you're good to go.
To root the ROM, I recommend finding "iRoot" for your computer. Then boot to recovery and install the SuperSU zip, as it's better than the root app which comes with the iRoot method.
Enjoy your ROM, and be sure to thank our Ruski comrades over at 4PDA!
Special thanks to @DvDwx. (research), @itsJohnuno (answers), and @Milly7 (testing).
All download links are being hosted by me, and I recommend creating mirrors of your own as safety precautions in the event that the files are removed or become unavailable.
Have a phenomenal day or night, possibly even both. If you have any questions, I'll do my best to answer them.
Nice Guide ;D
DvDwx. said:
Nice Guide ;D
Click to expand...
Click to collapse
Push that Guide to Android Development thread, that is a ROM ;D
We need talk with our Forum Administrator to Manage some Topics and Fuse KAZAM Tornado 348 with BLU Vivo Air menu... and try explain to this administrator about the re-branding process to he can add the other phones like AllView, Fly and Gionee to this Phone Menu Threads topics ;D
:highfive:
DvDwx. said:
Push that Guide to Android Development thread, that is a ROM ;D
We need talk with our Forum Administrator to Manage some Topics and Fuse KAZAM Tornado 348 with BLU Vivo Air menu... and try explain to this administrator about the re-branding process to he can add the other phones like AllView, Fly and Gionee to this Phone Menu Threads topics ;D
:highfive:
Click to expand...
Click to collapse
I didn't create the resources in the ROM, I just made a guide to flashing ROMs using a specific ROM as an example. I would feel bad posting it in the developer section because I don't wish to be given credit for the ROM. I didn't make it.
Ilxaot said:
I didn't create the resources in the ROM, I just made a guide to flashing ROMs using a specific ROM as an example. I would feel bad posting it in the developer section because I don't wish to be given credit for the ROM. I didn't make it.
Click to expand...
Click to collapse
i understand that ;D
on my WonderMedia WM8880 Tablet project i share the projects from other developers... but i asked they to have permission to share that, and leave on post the credits with their names... maybe if you talk with developer on 4PDA for permission to do it or ask him if it is possible he share he ROM Project here is will be perfect... anyway Good Guide to Flash this ROM :highfive:
Could you please describe how to flash the carliv recovery. I downloaded the app in step 2 but I can't even seem to install the twrp recovery because phone reboots into stock recovery and I don't even see an option for the carliv one.
dimasp6 said:
Could you please describe how to flash the carliv recovery. I downloaded the app in step 2 but I can't even seem to install the twrp recovery because phone reboots into stock recovery and I don't even see an option for the carliv one.
Click to expand...
Click to collapse
You need have root to do this... And sometimes the root dont work correctly and dont stay giving the rights to aplicantion can work...
DvDwx. said:
You need have root to do this... And sometimes the root dont work correctly and dont stay giving the rights to aplicantion can work...
Click to expand...
Click to collapse
I do have root with Kingroot. So I just need to keep trying until it successfully flashes?
Edit: The app mlp RIO recovery installer constantly freezes on me not allowing me to flash any of the recoveries.
dimasp6 said:
I do have root with Kingroot. So I just need to keep trying until it successfully flashes?
Edit: The app mlp RIO recovery installer constantly freezes on me not allowing me to flash any of the recoveries.
Click to expand...
Click to collapse
You can also try iRoot. Install SuperSU and try using it as the root granter for the recoveries.
Does the magnetometer (compass) work for you guys on the miui rom? It doesn't work for me.
ron580 said:
Does the magnetometer (compass) work for you guys on the miui rom? It doesn't work for me.
Click to expand...
Click to collapse
The app itself hadn't worked for me, I tried it earlier. Have you tested another app? It may be the stock app. I haven't messed with it much, not a huge navigator myself. [emoji14]
Ilxaot said:
The app itself hadn't worked for me, I tried it earlier. Have you tested another app? It may be the stock app. I haven't messed with it much, not a huge navigator myself. [emoji14]
Click to expand...
Click to collapse
The senor doesn't work at all using this rom & google maps wont work properly without it. Also the time on the lock screen and the home screen show different times about an hour apart Other than that everything else works fine.
ron580 said:
The senor doesn't work at all using this rom & google maps wont work properly without it. Also the time on the lock screen and the home screen show different times about an hour apart Other than that everything else works fine.
Click to expand...
Click to collapse
Yeah. I've also noticed that downloading updates is botched, because it downloads an update for a different phone model. If you try to install it the installation will fail, but it won't hurt your phone.
All in all it's a pretty solid ROM for me.
Ilxaot said:
Yeah. I've also noticed that downloading updates is botched, because it downloads an update for a different phone model. If you try to install it the installation will fail, but it won't hurt your phone.
All in all it's a pretty solid ROM for me.
Click to expand...
Click to collapse
Yes its a great rom maybe we can ask the developer if he can fix the issues for us on 4pda. I would do it but i couldn't register on 4pda i kept on receiving an error.
request
Ilxaot said:
All in all it's a pretty solid ROM for me.
Click to expand...
Click to collapse
Known bugs? any screenshot running this ROM please? I'd like to see some, I'm not updated on what's going on with MIUI and btw, great work! thanks in advance!
JesusEMC said:
Known bugs? any screenshot running this ROM please? I'd like to see some, I'm not updated on what's going on with MIUI and btw, great work! thanks in advance!
Click to expand...
Click to collapse
I'll post some tomorrow. Re-read the past 5-6 posts and you'll see the bugs. I think you'll like it. MIUI is certainly different (settings default apps) and such, but it's a formidable ROM and performs relatively well.
ron580 said:
Yes its a great rom maybe we can ask the developer if he can fix the issues for us on 4pda. I would do it but i couldn't register on 4pda i kept on receiving an error.
Click to expand...
Click to collapse
on Captcha you need count the numbers and ignore the russian Letters Like for exemple -> ##22###16## -> 22+16= 38
to can finish the registration... and no, you don't need use VPN or Proxy to create the account :highfive:
ron580 said:
Yes its a great rom maybe we can ask the developer if he can fix the issues for us on 4pda. I would do it but i couldn't register on 4pda i kept on receiving an error.
Click to expand...
Click to collapse
I'm sure he knows about it...and the guy is activity working on the ROM...except the latest update seems to just boot loop from what I've read, rather just wait and see.
itsJohnuno said:
I'm sure he knows about it...and the guy is activity working on the ROM...except the latest update seems to just boot loop from what I've read, rather just wait and see.
Click to expand...
Click to collapse
Our Buddy @SSJGohon found the kernel source code and already shared on some topic(i Already re-shared that on Cyanogen Mod to Mediatek SoC's Development thread... but anyone there say nothing about it... and already shared on 4PDA to maybe the MiUi developer can Bring something to All...). i already downloaded and already start my research about what can be maked with that and for sure have a possibility to we have a custom Kernel and maybe Custom ROM like PURE AOSP, AOSPA... but Cyanogen Mod is more difficult because we don't have a updated Repo Source from MediaTek to work like Driver Blobs to GPU, Bluetooth, Wifi Drivers... etc
My real problem is i don't have all skills to make a custom kernel to Mediatek SoC because a lot of things change from Qualcomm to Mediatek.. but if anyone here want to try development that just search the topics with @SSJGohon comments replays :highfive:
Ilxaot said:
I'll post some tomorrow. Re-read the past 5-6 posts and you'll see the bugs. I think you'll like it. MIUI is certainly different (settings default apps) and such, but it's a formidable ROM and performs relatively well.
Click to expand...
Click to collapse
I've already installed the ROM, it runs smoothly! You were right, I really like it! I had an issue trying to format /data, it took like 15 minutes, and did a hard reset (pressed power button for a few seconds) and tried to format again and it worked. Im a little bit worry cause I've had 2 radom reboots so far.. Any idea of what has happened to me?
CAUTION TO NOT LOOSE TWRP
I read two posts that say v21, now again on V8.5, put the stock recovery back instead of twrp. This is probably a side effect of a fresh stock /system and wipe of /data.
As a preventive step, when done flashing and wiping reboot to recovery FIRST, before booting the system It will allow recovery to handle removing the recovery-from-boot.p that flashes stock recovery.
I just patched the modified V7.4.2 up to the newly released 8.3 now 8.4. 8.5, 8.7,9.0 -V9.2 Patch
New update has been made from V17 to V21 of the non prime version of R1-HD, Non prime is behind on security patch (2017-05-05)
Copied ROM from phone and made twrp install ROM from it.
* No preloader change (official updates change the preloader to block your ability to use sp flash tools for rom flashing)
* No lk.bin change __ this part is what allows you to choose boot options(boot menu when power and volume pressed together)
* No "FOTA" app Fota has now been left in to make it easier to get next update, if that ever happens.
* No opera browser
* No adds (removed in the modified 7.4.2)
* Custom boot logo (only done on v8.3, there was no interest in this so abandoned)
--Newer versions of rom left stock, Leaving mods up to user.
** while it is not necessary to do a wipe with this ROM, I still recommend it.
**Thanks:
** @vampirefo needed his patched v7.4.2 in order to apply this new 8.3 patch and again for 8.4
** @ColtonDRG OR @jasonmerc I do not remember which one made it: For the image used in the custom logo
and the modified zip is here .
Roms are rootable with SuperSU, flashed in twrp after install. Must be done in systemless mode. In order to patch system veridy in boot.img
Logo update did not work on original rom changing link to updated version
BLU rolled v8.3 back to v7.4.2 because of app compatability issues. V8.4 is there fixed release. Both 8.3 and 8.4 are modified prime roms with ads stripped
V21 is the non prime update.
Unmodified V6.1
==>NON-ROOTED-logo-not-replaced-modified-V8.3
==>Fixed Logo modified NON_ROOTED V8.3
==>>modified V8.4
==>>modified V8.5
==>>Full with Ads V8.7
==>>Full with Ads V9.0
==>>Patch For V9.2 must be flashed on top of fresh V9.0
****Run debloat ==>script to remove ads if you need/ want to, or remove from zip before flashing ****
alt. manual example: before reboot, while still in twrp. Select mount and put checkmark next to system. Then run these two commands in adb terminal
Code:
adb shell rm /system/priv-app/com.amazon.*/com.amazon.*.apk
adb shell rm /system/app/Adups*/*.apk
==>>Modified V21
** stand alone logo installs
I flashed this but I didn't get the custom boot logo.
mendelgordon said:
I flashed this but I didn't get the custom boot logo.
Click to expand...
Click to collapse
I had that happen to my second phone too.
I don't have an explanation yet.
I even made a separate update.zip , that one didn't make the logo change either. I did eventually change it with sp flash tool.
I tried with both recoveries.
and multiple /dev location formats. and for whatever reason my one phone did not accept the logo change from recovery.
And the other test phone it worked.
mendelgordon said:
I flashed this but I didn't get the custom boot logo.
Click to expand...
Click to collapse
Neither did I but it all seems to be working fine
Been using this for about a day now, likewise no custom boot logo, but that's fine. Otherwise, it's been running super well. A lot better than the previous mostly stock version did for me with the bloatware APKs removed after the install. A lot of the general idiosyncrasies of the previous version of the stock rom seem to have gone away for me. It seemed to have weird storage management issues, errors moving to SD, broken symlinks that prevent apps from moving or being reinstalled, and a lot of other little non-storage issues, but so far, none off that here.
Long story short, good work! I hope we eventually see proper 7.x roms through some of the efforts going on, but in the meanwhile, your work here has made life a little bit better on 6.
It seems that I was able to get the logo.bin to update when I applied the original update patch, but not when I used the same line in the rom install.
It is no big deal that it did not work, I was just trying to make it look different at boot time.
edit:
I think i found the problem with the logo not updating.
i used the update-binary from the official patch update. (the one that allowed the logo to change the first time)
and it changes . so since the ROM seems to install the way it is , only the logo didn't flash I put it in a separate update.zip if anyone is interested in it.
EDIT 2:
clarification.
It was not so much the binary allowing the logo to change but the format of the partition location I had been using that needed that binary.
Further test had shown me that I could have used the binary I was using but just change the partition naming line
Code:
package_extract_file("logo.bin", "/dev/block/mmcblk0p9")
the above code works with the same update-binary as rom install
But I was using
Code:
package_extract_file("logo.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo")
Taken straight from the official patch, and thats why it needed the update-binary also.
I dont know what is different in the binary other than , major size difference.
The powered by me logo was just a test file to see changes in the logo.
**logo-update is same as composite but with alt updater-binary
**composite-logo screenshot is in op
**stock logo will return to original BLU logo
mrmazak said:
It seems that I was able to get the logo.bin to update when I applied the original update patch, but not when I used the same line in the rom install.
It is no big deal that it did not work, I was just trying to make it look different at boot time.
edit:
I think i found the problem with the logo not updating.
i used the update-binary from the official patch update. (the one that allowed the logo to change the first time)
and it changes . so since the ROM seems to install the way it is , only the logo didn't flash I put it in a separate update.zip if anyone is interested in it.
EDIT 2:
clarification.
It was not so much the binary allowing the logo to change but the format of the partition location I had been using that needed that binary.
Further test had shown me that I could have used the binary I was using but just change the partition naming line
Code:
package_extract_file("logo.bin", "/dev/block/mmcblk0p9")
the above code works with the same update-binary as rom install
But I was using
Code:
package_extract_file("logo.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo")
Taken straight from the official patch, and thats why it needed the update-binary also.
I dont know what is different in the binary other than , major size difference.
The powered by me logo was just a test file to see changes in the logo.
Click to expand...
Click to collapse
Hahaha the scribbled "ME" is hilarious. Your work is awesome, I don't think anyone using this rom will have an issue with the boot image but thanks for being so helpful and explaining.
P. S. Do you have any plans with the Nougat update?
Serenitybs said:
Hahaha the scribbled "ME" is hilarious. Your work is awesome, I don't think anyone using this rom will have an issue with the boot image but thanks for being so helpful and explaining.
P. S. Do you have any plans with the Nougat update?
Click to expand...
Click to collapse
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
linuxsociety said:
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
Click to expand...
Click to collapse
Somebody already tried this out
linuxsociety said:
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
Click to expand...
Click to collapse
It was just wishful thinking. I have no idea how all of this is done. All I know is @mrmazak has helped me to fall in love with my phone again with this V8.3. The 7.4.2 did seem a bit buggy for my phone but this update works beautifully and I didn't even root it. If this remains true I will be happy with this phone for awhile even on 6.0
Really confused right now.
I was browsing through the settings menus. And found in the Settings-security- menu a toggle labeled "quick boot" ( not to be confused with "fastboot") . I enabled it then rebooted to see if it booted quicker. Didn't seem to make much if any difference. So I went back to turn it back off. And it wasn't there. I checked in my other phone , it wasn't there on that one either.
Did any body see this menu item, and if so where is is it?
Edit 1:
Few more power off , power on cycles to compare times. With other phone and defiantly seems to have turned on some faster boot option.
This phone goes from off to on in 5-6 seconds other phone takes about 20.
Edit 2:
OK , I panicked for a minute.
Couldn't find the setting and thought that it was another way to block sp flash tool by preventing you from ever being fully powered off.
But the setting was in accessibility not security.
Mrmazak, first of all, thanks for the ROM, installed it yesterday. But I have a problem with SELinuxModeChanger app. First, I'm getting a security warning when installing it, then - when running it. And another message, with this app running - "can't obtain root", although SuperSU shows its status with green #, like every other app it gives root privileges to. On my other Prime phone, running 6.1 out of the box stock ROM, FM radio works just fine with SELinuxModeChanger app behaving flawlessly (no security warnings whatsoever). Any ideas?
detroitredwings said:
Mrmazak, first of all, thanks for the ROM, installed it yesterday. But I have a problem with SELinuxModeChanger app. First, I'm getting a security warning when installing it, then - when running it. And another message, with this app running - "can't obtain root", although SuperSU shows its status with green #, like every other app it gives root privileges to. On my other Prime phone, running 6.1 out of the box stock ROM, FM radio works just fine with SELinuxModeChanger app behaving flawlessly (no security warnings whatsoever). Any ideas?
Click to expand...
Click to collapse
The mode changer app is technically a security issue. I did have that warning a few times when using mode changer app from the XDA thread of the developer, then when I used the app downloaded from f-droid it worked with systemless root and didn't give the security warning.
The app downloaded from f-droid worked for me as well, many thanks!
Big thanks for getting this out, updated from previous debloated, rooted version to this modified 8.3 stock rom, rooted with SU v2.79 SR3, all is good - only App that won't show up nor install, even tried the ones off APK Mirror site - is my Dunkin Donuts App, LOL. Play Store now said it's not compatible and the APK started to install then failed - any ideas or suggestions on what to do ??
Otherwise, it's all good - I will survive without DD App, just run that from another device when I need my caffeine fix.
Letitride said:
Big thanks for getting this out, updated from previous debloated, rooted version to this modified 8.3 stock rom, rooted with SU v2.79 SR3, all is good - only App that won't show up nor install, even tried the ones off APK Mirror site - is my Dunkin Donuts App, LOL. Play Store now said it's not compatible and the APK started to install then failed - any ideas or suggestions on what to do ??
Otherwise, it's all good - I will survive without DD App, just run that from another device when I need my caffeine fix.
Click to expand...
Click to collapse
I also had an app that previously work, say is not compatible now.
Maybe has to do with apps that have links to pay accounts. And that has something to do with trustzone. (Tee1 & tee2)
Those sections I left out of the update. I will add it back in and test. Update when I do. It is also possible this problem is why Blu rolled back there update.
**EDIT**
well that didn't go well at all.
I flashed the new trustzone.bin files from the official update. Now phone no longer turns on and no longer connects to flash tool
**EDIT 2**
After much persistence and many failed attempts to get phone recognized in pc again. Finnaly got to a point that phone was cycling between "preloader" driver and "usb serial device", and with careful timing was able to start sp flash tool at just right time and the flashing back to original trustzone files seems to have recovered phone.
for the record i am not sure what steps made it work. But I was shifting back and forth between leaving phone sit on charge, then on charge with rubber band wrapped around power button, then not plugged in , and not plugged in with rubber band on power button.
Okay... persistence is key in customization, i guess! I am getting somewhere here!
mrmazak said:
The first link is needed to get phone unlocked so you can install twrp.
Click to expand...
Click to collapse
Finally got thru the steps in order (1-2-3-4) then Step (5) and sub-step 1. I can also boot to TWRP.
Now this brings me to this thread, 8.3 Stock ROM. The thread assumes one knows how to install it and I suspect this could be as easy as uploading it to a folder in the phone then booting to TWRP and INSTALLING the ZIP file? Could someone clarify the steps to install this 8.3 ROM?
Thanks!
OldSkewler said:
Okay... persistence is key in customization, i guess! I am getting somewhere here!
Finally got thru the steps in order (1-2-3-4) then Step (5) and sub-step 1. I can also boot to TWRP.
Now this brings me to this thread, 8.3 Stock ROM. The thread assumes one knows how to install it and I suspect this could be as easy as uploading it to a folder in the phone then booting to TWRP and INSTALLING the ZIP file? Could someone clarify the steps to install this 8.3 ROM?
Thanks!
Click to expand...
Click to collapse
Yes. You are correct
Either put the zip file on external sd card , put card into phone boot into recovery mode and install , or put file directly onto phone .
Many ways to do that.
Easiest is to copy to phone while phone is connected to PC.
Cam also download file from internet with your phone.
Bottom line is get zip file to the phone boot to recovery and install
Anyone else having wifi issues after upgrading? While watching videos it seems the internet cuts out. The phone says it's still connected but I have to turn wifi off and back on for anything to work. Could be my router also but it didn't seem to be doing this until I installed 8.3
mrmazak said:
Yes. You are correct
Either put the zip file on external sd card , put card into phone boot into recovery mode and install , or put file directly onto phone .
Easiest is to copy to phone while phone is connected to PC.
Bottom line is get zip file to the phone boot to recovery and install
Click to expand...
Click to collapse
Right on man! I am officially running 8.3 ROM with April 5th 2017 Security Patch Level! Geez.. it was not easy but I got this working!
MrMazak, I followed all your instructions on both links, so could you tell me what exactly I have on my phone? Is it rooted? Bootloader Unlocked? The phone seems to be working fine but I don't know what level of access I have. Honestly I don't even know exactly what the differences between all these terms are.
Also, do I have or not SU? One of the steps under the .bat I believe install it. How do I access it?
Thanks again!
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
Weasel0 said:
Anyone else having wifi issues after upgrading? While watching videos it seems the internet cuts out. The phone says it's still connected but I have to turn wifi off and back on for anything to work. Could be my router also but it didn't seem to be doing this until I installed 8.3
Click to expand...
Click to collapse
My install is pretty fresh, couple of hours, but as far as I can tell all is working fine with Wifi, As a matter of fact this is a new device only connected with Wifi and no SIM Card.... internet works fine.
Hello to all,
first of all sorry for my English, i'm using google translate, I do not know if you can help me here.
I bought this jewel from Gearbest and arrived yesterday.
I would like to unlock the bootloader and root it following this wonderful guide , but I can not get into developer options, I get the error "the settings application crashed abnormally"
I wanted to do this via the toolkit, but in EDL mode the phone is not recognized, maybe because in developer options I have to select the OEM UNLOCK.
The only good thing is that it recognizes usb debugging mode (at least I think) because I see the debug notification icon.
I can not understand where it came from, I went into bootloader mode but did not release me information.
From the onscreen screen I can only provide these info:
model number zte a2017g
version android 6.0.1
kernel version 3.18.20
build number zte a2017gv1.0.0b11
baseband version th.2.0.c1.9-00050-m8996faaaanazm
The MiFlavor version is 4.0
The smartphone does not receive OTA updates. I downloaded the global version (b05) of Nougat, the update with Android started I did not find it (I renamed the rom file in update.zip and put in the root of the SD CARD). I tried through recovery mode but it does not do anything to me, it's as if the smartphone was locked in everything and for everything.
I'm doing well ? How do I update when I download the rom? Can you please help me? Is there any system to interact with this smartphone and unlock it? I do not want to keep a phone that I can not update and root it.
Thanks in advance to who will help.
UPDATE:
I tried to manually install the downloaded ROM, but in recovery mode it does not flash the new rom ... the phone does not even try it !!!
It's as if the phone was locked in everything and I only have to keep the installed rom.
Some idea ?
SuDGLaD said:
UPDATE:
I tried to manually install the downloaded ROM, but in recovery mode it does not flash the new rom ... the phone does not even try it !!!
It's as if the phone was locked in everything and I only have to keep the installed rom.
Some idea ?
Click to expand...
Click to collapse
Hey I would recommend clearing the data for settings if you can. To do this go to your launcher, find the settings icon and either drag or hold down or do whatever it takes to get to the app info. I haven't used stock in a long time so idk. But then go into storage and clear data. Then go and try again.
I do have one question though. How did you get usb adb debugging enabled if you didn't get into developer options at all?
For the second half of your question you won't be able to flash anything without first unlocking the bootloader and flashing TWRP onto the device. For the devices recovery idk which one you meant, but it needs to be TWRP. Good luck!
JTruj1ll0923 said:
Hey I would recommend clearing the data for settings if you can. To do this go to your launcher, find the settings icon and either drag or hold down or do whatever it takes to get to the app info. I haven't used stock in a long time so idk. But then go into storage and clear data. Then go and try again.
I do have one question though. How did you get usb adb debugging enabled if you didn't get into developer options at all?
For the second half of your question you won't be able to flash anything without first unlocking the bootloader and flashing TWRP onto the device. For the devices recovery idk which one you meant, but it needs to be TWRP. Good luck!
Click to expand...
Click to collapse
Thanks to my friend, without doing anything, suddenly, he made me enter the developer options menu.
I've been able to do the rest.
Now I have the phone with unlocked bootloader, root and TWRP installed.
Do not ask me how I got the debug without going into the menu, I could not answer you ... it will remain a mystery !!!
I take advantage of your availability: can I flash the zip of the official ROM through TWRP? Or is there a risk that the phone goes into brick mode?
SuDGLaD said:
Thanks to my friend, without doing anything, suddenly, he made me enter the developer options menu.
I've been able to do the rest.
Now I have the phone with unlocked bootloader, root and TWRP installed.
Do not ask me how I got the debug without going into the menu, I could not answer you ... it will remain a mystery !!!
I take advantage of your availability: can I flash the zip of the official ROM through TWRP? Or is there a risk that the phone goes into brick mode?
Click to expand...
Click to collapse
What rom are you trying to install? Usually you will be absolutely fine.
SuDGLaD said:
Thanks to my friend, without doing anything, suddenly, he made me enter the developer options menu.
I've been able to do the rest.
Now I have the phone with unlocked bootloader, root and TWRP installed.
Do not ask me how I got the debug without going into the menu, I could not answer you ... it will remain a mystery !!!
I take advantage of your availability: can I flash the zip of the official ROM through TWRP? Or is there a risk that the phone goes into brick mode?
Click to expand...
Click to collapse
JTruj1ll0923 said:
What rom are you trying to install? Usually you will be absolutely fine.
Click to expand...
Click to collapse
You can't flash an official zip through TWRP, it will just fail. No brick.
Edit: didn't read OP lol. If you want to update, you have to flash the stock recovery (there are stock recovery flashable zips on the Download Center) then install the update, then get TWRP again. Or you can install a custom ROM (I recommend one based on stock MiFavor 5.0, I think that the best one is ADM Team V3 (the one that's not based on B13), this way you can simply download, flash in TWRP, and you'll be done
JTruj1ll0923 said:
What rom are you trying to install? Usually you will be absolutely fine.
Click to expand...
Click to collapse
Thanks :good:
Choose an username... said:
You can't flash an official zip through TWRP, it will just fail. No brick.
Edit: didn't read OP lol. If you want to update, you have to flash the stock recovery (there are stock recovery flashable zips on the Download Center) then install the update, then get TWRP again. Or you can install a custom ROM (I recommend one based on stock MiFavor 5.0, I think that the best one is ADM Team V3 (the one that's not based on B13), this way you can simply download, flash in TWRP, and you'll be done
Click to expand...
Click to collapse
Thanks mate !!
I installed the rom that you suggested to me, I find it very good, but this phone has very poor support (MiFavor).
SuDGLaD said:
Thanks :good:
Thanks mate !!
I installed the rom that you suggested to me, I find it very good, but this phone has very poor support (MiFavor).
Click to expand...
Click to collapse
Very poor support? It's going to get Android O, and it's got at least 1 update per month (officially). It's unclear whether that ROM you installed will be updated since it's based on an older version, but the latest (B13) breaks a bunch of stuff like Google Play Games, Maps, the GPS works awfully...
Choose an username... said:
Very poor support? It's going to get Android O, and it's got at least 1 update per month (officially). It's unclear whether that ROM you installed will be updated since it's based on an older version, but the latest (B13) breaks a bunch of stuff like Google Play Games, Maps, the GPS works awfully...
Click to expand...
Click to collapse
No no ... do not get me wrong.
My reference is to rom, MiFlavor is really bad. I come from 3 Xiaomi smartphones and I can assure you is another world.
The smartphone is really nice and well balanced (apart from the just enough battery) and I would replenish it a thousand times. :fingers-crossed::good:
I hate asking this as each has his own preference, however, I have only just ordered my ZTE Axon device as it was such a good offer, being even cheaper than brand new 2018 mid rangers! I purchased the device brand new and sealed for just £193 ($274) so you cannot go wrong.
My current phone was the Sony Xperia XZ Premium but I am giving it away to my wife and need another to replace it.
After some reading it seems the first thing I need to do is install all drivers and run the Axon 7 Tool kit. This will unlock bootloader, root and flash recovery from my understanding.
Then I can proceed to installing a custom rom of my choice followed by immediately flashing a modem otherwise I will not have any signal. Would this be everything needed to successfully running a custom rom trouble free?
Lastly, I would like a simple rom, preferably based on stock/vanilla Android, slim and bloat free. Something very basic, bug free and made for pure speed and decent battery. What are the top recommended roms with this regard? I did look into these, anything better? What are the differences? Thank you so much for your advise.
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3716825
https://forum.xda-developers.com/axon-7/development/rom-slm-version-t3704143
https://forum.xda-developers.com/axon-7/development/rom-dark-rom-t3654264
kanej2006 said:
I hate asking this as each has his own preference, however, I have only just ordered my ZTE Axon device as it was such a good offer, being even cheaper than brand new 2018 mid rangers! I purchased the device brand new and sealed for just £193 ($274) so you cannot go wrong.
My current phone was the Sony Xperia XZ Premium but I am giving it away to my wife and need another to replace it.
After some reading it seems the first thing I need to do is install all drivers and run the Axon 7 Tool kit. This will unlock bootloader, root and flash recovery from my understanding.
Then I can proceed to installing a custom rom of my choice followed by immediately flashing a modem otherwise I will not have any signal. Would this be everything needed to successfully running a custom rom trouble free?
Lastly, I would like a simple rom, preferably based on stock/vanilla Android, slim and bloat free. Something very basic, bug free and made for pure speed and decent battery. What are the top recommended roms with this regard? I did look into these, anything better? What are the differences? Thank you so much for your advise.
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3716825
https://forum.xda-developers.com/axon-7/development/rom-slm-version-t3704143
https://forum.xda-developers.com/axon-7/development/rom-dark-rom-t3654264
Click to expand...
Click to collapse
As for the SL!M roms i made ( making some advertisement here ) i only can advise looking at these ones as they are aroma roms and can be debloated further. Battery tweak is included and choice between SuperSU and Magisk is possible. These roms are stock-based as to preserve, imo, the sound quality of the phone as it came out of the box. No bug issues imo and fully up to date :
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3716825
Based on MiFavor5.0 (CN) but fully applyable on all versions
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3735003
Based on stock G version but fully applyable on all versions and with the latest security patches of the A2017G-N(ougat)-B09
But then again others can comment on my slim roms better then i can perhap :cyclops:
Futhermore i do not advice https://forum.xda-developers.com/axon-7/development/rom-slm-version-t3704143 as it is was my first version of MiFavor 5.0. Instead use the first link.
Didn't used the last one you mentioned based on LOS but others can advice more into this.
Good Luck and ENJOY !
raystef66 said:
As for the SL!M roms i made ( making some advertisement here ) i only can advise looking at these ones as they are aroma roms and can be debloated further. Battery tweak is included and choice between SuperSU and Magisk is possible. These roms are stock-based as to preserve, imo, the sound quality of the phone as it came out of the box. No bug issues imo and fully up to date :
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3716825
Based on MiFavor5.0 (CN) but fully applyable on all versions
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3735003
Based on stock G version but fully applyable on all versions and with the latest security patches of the A2017G-N(ougat)-B09
But then again others can comment on my slim roms better then i can perhap :cyclops:
Futhermore i do not advice https://forum.xda-developers.com/axon-7/development/rom-slm-version-t3704143 as it is was my first version of MiFavor 5.0. Instead use the first link.
Didn't used the last one you mentioned based on LOS but others can advice more into this.
Good Luck and ENJOY !
Click to expand...
Click to collapse
^ Thank you very much raystef66 for your speedy response! I will go for this version - https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3735003
Fingers crossed I should receive my Axon 7 Sunday or Monday at the very latest. First Thing I'll run the Axon 7 Toolkit so that I can unlock the bootloader, have recovery and root then I'll be able to flash your rom, looking forward into doing so!
I'll keep you informed in the coming days when complete. :good:
kanej2006 said:
^ Thank you very much raystef66 for your speedy response! I will go for this version - https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3735003
Fingers crossed I should receive my Axon 7 Sunday or Monday at the very latest. First Thing I'll run the Axon 7 Toolkit so that I can unlock the bootloader, have recovery and root then I'll be able to flash your rom, looking forward into doing so!
I'll keep you informed in the coming days when complete. :good:
Click to expand...
Click to collapse
Yeah, very exciting isn't it :good: It's a damn good phone, quick, nice quality screen and an amazing sound... !
I assume you'll get the G version ? The SL!M➃ is based on this G-version (btw, take a look at the DownloadCenter to have all necessary files) and keeps all things to stock. Just some minor mods and improvements, nothing fancy as to stay stock. With the battery tweak included i always get >7h SOT. But that depends of course on usage. But then again i do alot in a day . Some others have no benefit on the battery tweak but i'll hope you end up with a descent SOT.
Keep us posted :good:
raystef66 said:
Yeah, very exciting isn't it :good: It's a damn good phone, quick, nice quality screen and an amazing sound... !
I assume you'll get the G version ? The SL!M➃ is based on this G-version (btw, take a look at the DownloadCenter to have all necessary files) and keeps all things to stock. Just some minor mods and improvements, nothing fancy as to stay stock. With the battery tweak included i always get >7h SOT. But that depends of course on usage. But then again i do alot in a day . Some others have no benefit on the battery tweak but i'll hope you end up with a descent SOT.
Keep us posted :good:
Click to expand...
Click to collapse
Sounds good! I would be happy with around 7 hours SOT. Once received I'll let you know what version I receive, however, I'm guessing I'll get the Chinese version as it's coming from Dubai, UAE (Middle East) and most likely it'll come from China and not EU as it's much closer.
I have everything ready accept for a flashable TWRP. The link appears down for me and I was not able to find a flashable version, could you please give me a link of a working one? I was only able to find a non flashable version which is run via CMD/fastboot commands.
I would much rather a flashable recovery in which I can flash once installing your rom along with SuperSU or Magisk. Regards!
kanej2006 said:
Sounds good! I would be happy with around 7 hours SOT. Once received I'll let you know what version I receive, however, I'm guessing I'll get the Chinese version as it's coming from Dubai, UAE (Middle East) and most likely it'll come from China and not EU as it's much closer.
I have everything ready accept for a flashable TWRP. The link appears down for me and I was not able to find a flashable version, could you please give me a link of a working one? I was only able to find a non flashable version which is run via CMD/fastboot commands.
I would much rather a flashable recovery in which I can flash once installing your rom along with SuperSU or Magisk. Regards!
Click to expand...
Click to collapse
The TWRP is inside the toolkit, so you can flash it downthere imo. Never done this that way though as in those early days i used this one to do everything. But use the toolkit and you're good to go.
raystef66 said:
The TWRP is inside the toolkit, so you can flash it downthere imo. Never done this that way though as in those early days i used this one to do everything. But use the toolkit and you're good to go.
Click to expand...
Click to collapse
Ah good to hear, glad it's included in the kit. So I can simply use the one from the kit to flash recovery after flashing your rom? Because in the instructions it mentions we have to manually flash recovery after the rom.
kanej2006 said:
Ah good to hear, glad it's included in the kit. So I can simply use the one from the kit to flash recovery after flashing your rom? Because in the instructions it mentions we have to manually flash recovery after the rom.
Click to expand...
Click to collapse
That depends. I dont know what version of twrp is installed via the toolkit. Perhaps it checkes for the latest when it updates but not sure. But if a certain version is installed which is not the latest, put the latest twrp.img onto your int or extSD and flash via your twrp you've installed.
Second, if your phone would be an CN version and not a G, you'll have to install the Universal BL and your specific modem as described in the rom thread. You can find them in the link of the rom thread. So, after installing the Universal BL (which has an older version of twrp !) , you'd have to install the latest via twrp too. So just flash the twrp image and you're good to go.
Btw, i made a flashable zip before of that Universal BL which replaces the old twrp with the 3.1.1.0 version, which will do fine too.
Here's the link : https://androidfilehost.com/?fid=673791459329066038 (it also works on the SLIM4 as it just replaces twrp)
So after installing this version, you dont need to flash another twrp (as it brings you to the 3.1.1.0 as said)
kanej2006 said:
Ah good to hear, glad it's included in the kit. So I can simply use the one from the kit to flash recovery after flashing your rom? Because in the instructions it mentions we have to manually flash recovery after the rom.
Click to expand...
Click to collapse
Uuhh. I think you'll get the G version. Anything else than China and US gets G. With that said, I recommend you two things:
- (If you get a G) Use Controllerboy's guide instead of the toolkit. Lately a lot of stuff is going wrong with the toolkit
-Whatever happens, DO NOT ATTEMPT TO RELOCK THE BOOTLOADER.
-Once you have TWRP, just follow the instructions on each ROM. Never flash stuff from other models.
-Take the TWRP img either from raystef66's download center or from twrp.me
raystef66 said:
I dont know what version of twrp is installed via the toolkit. Perhaps it checkes for the latest when it updates but not sure. But if a certain version is installed which is not the latest, put the latest twrp.img onto your int or extSD and flash via your twrp you've installed.
Second, if your phone would be an CN version and not a G, you'll have to install the Universal BL and your specific modem as described in the rom thread. You can find them in the link of the rom thread. So, after installing the Universal BL (which has an older version of twrp !) , you'd have to install the latest via twrp too. So just flash the twrp image and you're good to go.
Btw, i made a flashable zip before of that Universal BL which replaces the old twrp with the 3.1.1.0 version, which will do fine too.
Here's the link : https://androidfilehost.com/?fid=673791459329066038 (it also works on the SLIM4 as it just replaces twrp)
So after installing this version, you dont need to flash another twrp (as it brings you to the 3.1.1.0 as said)
Click to expand...
Click to collapse
Will do. You are right, the toolkit automatically checks for the latest update and it finds version 3.1.1.0.
Choose an username... said:
Uuhh. I think you'll get the G version. Anything else than China and US gets G. With that said, I recommend you two things:
- (If you get a G) Use Controllerboy's guide instead of the toolkit. Lately a lot of stuff is going wrong with the toolkit
-Whatever happens, DO NOT ATTEMPT TO RELOCK THE BOOTLOADER.
-Once you have TWRP, just follow the instructions on each ROM. Never flash stuff from other models.
-Take the TWRP img either from raystef66's download center or from twrp.me
Click to expand...
Click to collapse
I did see on the forum users attempting to relock the bootloader and it worsened things, I will not attempt this.
Should be able to let you know tomorrow or the day after what version I get and hopefully when I successfully gain recovery and root access!
I just hope I don't get the dead microSD bug that many people have mentioned. Top of the range 64Gb/128Gb MicroSD cards can be costly so I would not like to have them corrupted!
@raystef66, Do you have any other download links for your rom aside from androidfilehost? I tried several different servers but all keep randomly freezing otherwise saying 5 hours, 6 hours, 11 hours and 15 hours. Extremely slow download.
If you want to try a more Android vanilla ROM, then I suggest AICP. Be sure to use the unofficial builds by genesixxbf3. They are very stable and have good features.
https://forum.xda-developers.com/axon-7/development/rom-aicp-12-1-t3611013
kanej2006 said:
@raystef66, Do you have any other download links for your rom aside from androidfilehost? I tried several different servers but all keep randomly freezing otherwise saying 5 hours, 6 hours, 11 hours and 15 hours. Extremely slow download.
Click to expand...
Click to collapse
Yeah, sometime AFH can be cruel. Just depends. I tried the Washington DC just a moment and no problems there. I just advice, take one and let it take it's time. Some way or another the download speed gets stable enough And then again, you still have a bit of time don't you or has it dropped of yet with the postman :cyclops: Do I Hear a heartbeat there ? :good:
raystef66 said:
Yeah, sometime AFH can be cruel. Just depends. I tried the Washington DC just a moment and no problems there. I just advice, take one and let it take it's time. Some way or another the download speed gets stable enough And then again, you still have a bit of time don't you or has it dropped of yet with the postman :cyclops: Do I Hear a heartbeat there ? :good:
Click to expand...
Click to collapse
Haha, no, not yet received! Where I am living at the moment, the weekend is Friday and Saturday, Sunday to Thursday work, strange but that's the way it is.
The seller estimates the item to arrive on Sunday or Monday, hopefully Sunday.
In the end the Netherland's sever finally managed to get me the 2.1Gb download complete. I did try others but were slower. Good thing in your rom you included the 3 different models for the Axon 7. I'm yet to see which one I receive!
Confirmed G version received.
kanej2006 said:
Confirmed G version received.
Click to expand...
Click to collapse
The AcTiOn can begin :good:
Use this guide like said above and you'll be ok.
raystef66 said:
The AcTiOn can begin :good:
Use this guide like said above and you'll be ok.
Click to expand...
Click to collapse
Not working, been trying for hours.
Not connecting despite all drivers installed, including Qualcom driver. Followed all instructions as stated. Stuck from number 20. When entering this command I get ''failed to connect''
When typing in adb devices it finds my device.
1) Backup all the data of your phone's internal memory that you don't want to lose. Copy it to your PC
2) Download the axon7tool from here: http://www.filedropper.com/axon7tool-15-win64
3) Download minimal adb and fastboot from here: https://www.androidfilehost.com/?fid=457095661767103465
4) Unzip the minimal adb and fastboot file, place the folder with the files in it somewhere you can easily find it
5) Place the axon7tool exe in the same folder as adb.exe and rename it to "axon7tool.exe" (it's easier to work with that way)
6) Download the TWRP .img and .bin files from here: https://drive.google.com/open?id=0B4...nlaZU1NRldoRjA
7) Place the TWRP .img file in the same folder as "adb.exe" and "axon7tool.exe", rename it to "recovery.img"
8) Make a copy of the "recovery.img" file and name it "recovery.bin". Leave it in the same folder
9) Go to settings in your phone and go to "About Phone". Tap "Build Number" 7 times to make the Developer Options available
10) Go to "Developers options" and tick "Allow OEM unlock" and "Android Debugging"
11) Connect your Axon 7 to your PC
12) Open a command window by holding shift and right-clicking in a blank space in the folder where the "adb.exe", " axon7tool.exe", "recovery.img" and "recovery.bin" files are located. Click "Open command window here"
13) Type "adb devices" and hit enter. You should see one device with some code listed
14) Type "adb reboot edl" and hit enter. Your device will reboot to EDL mode. It appears to be off, but it is in fact in EDL mode.
15) Go to Device Manager on your pc and verify your Axon 7 is listed as "QUSB_BULK"
16) In command, type "axon7tool -r gpt boot recovery" and hit enter
17) After it is executed, your phone will reboot. Wait until it has fully booted.
18) In command, type "adb reboot edl"
19) Verify you now have 3 backup files in your ADB folder for gpt, recovery and boot. These are backup files in case something goes wrong
20) In command, type "axon7tool -w recovery" - STUCK HERE - FAILED
kanej2006 said:
Not working, been trying for hours.
20) In command, type "axon7tool -w recovery" - STUCK HERE - FAILED
Click to expand...
Click to collapse
You're on nougat ? Look into about phone for that.
Afaik, you'll have to be on MM. So downgrade/rollback if on Nougat (look into DownloadCenter for B10 or B11) and do the procedure all over again.
Imo it's due to that.
edit: sure you have the recovery.img and bin in your adb folder ?
raystef66 said:
You're on nougat ? Afaik, you'll have to be on MM. So downgrade/rollback if on Nougat (look into DownloadCenter for B10 or B11) and do the procedure all over again.
Imo it's due to that.
edit: sure you have the recovery.img and bin in your adb folder ?
Click to expand...
Click to collapse
No, I am on stock MM.
kanej2006 said:
No, I am on stock MM.
Click to expand...
Click to collapse
Should work then.
Can you download recovery again. Check all characters if they're all written ok.
Sure the toolkit cannot bring enlightment too ?
Disclaimer
**** All flashing is done at your own risk! ****
**** While this recovery should not break your device, don't come back here blaming anyone if it does! ****
This is a TWRP 3.2.3 build based on Android 7.1.2 source kernel for the Galaxy Tab Active 2 (codename: gtactive2lte) - Exynos. The "tar" file should be installed using Odin (tested on Odin 3.12.3).
Special Notes:
1. DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options, if its not there, you may have to wait for a few days to access that option, some users claim that its within 10 days before this option appears).
2. KNOX will be tripped once you flashed custom binaries to your phone.
3. Samsung Firmware OTA (aka System Updates) will no longer work once you flashed custom binaries.
(You can flash custom ROMs if you want to keep the OS up-to-date.)
4. It is HIGHLY UNRECOMMENDED to purchase any access to any kind of private forums, ROMs or Kernels.(DO NOT GET FOOLED.)
Installation process:
1. Flash Stock ROM.
2. Flash recovery using Odin (AP = recovery.tar).
3. Load recovery immediately after flashing.
4. Format data (Will erase /data partition).
5. Reboot to recovery.
6. ADB push SuperSU to internal storage / insert SD-Card with SuperSU.zip.
7. Flash SuperSU using TWRP install option.
8. Reboot to system (May bootloop several times. Wait untill system loads).
Bugs:
1. ADB sometimes doesn't work in MTP mode. Need to manually change to PTP in order to get adb usage.
2. Bad label in ADB shell + bad characters appearing while writing through AD. Works well out of recovery and on recovery's terminal.
Sources:
Device tree - Device tree
Kernel - Kernel
TWRP sources - platform_manifest_twrp_omni
SuperSU - SuperSU-2.82-SR5
Recovery download:
Recovery
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 08/19/2018 (DD/MM/YYYY)
Contributors:
Many thanks to TWRP's developers for the support on building this recovery.
Special thanks to CaptainThrowback, Bigbiff and Dees_Troy on TWRP-freenode and Ashyx on xda-developers.
Please post any bugs you encounter. I will try to fix any issues that come up.
Thanks for the work and sharing. I'm excited to try. Having root would be great, but I'd also like to be able to make voice calls ( using bluetooth as the built-in speaker & microphone aren't adequate ). Do you think this is possible. What changes, if any, are required to have work with T397 Tab Active 2 ( US variant ) ? I'm sure that it's mobile frequencies are different than what the euro-spec'd T395, but otherwise I think identical.
Slomo
slomo2 said:
Thanks for the work and sharing. I'm excited to try. Having root would be great, but I'd also like to be able to make voice calls ( using bluetooth as the built-in speaker & microphone aren't adequate ). Do you think this is possible. What changes, if any, are required to have work with T397 Tab Active 2 ( US variant ) ? I'm sure that it's mobile frequencies are different than what the euro-spec'd T395, but otherwise I think identical.
Slomo
Click to expand...
Click to collapse
Well, Samsung has a nice repo of their source kernels for every phone Samsung sources
I guess we just have to validate some data taken from boot.img from the stock rom and then build the same with the appropriate source kernel.
Shedaim said:
Well, Samsung has a nice repo of their source kernels for every phone Samsung sources
I guess we just have to validate some data taken from boot.img from the stock rom and then build the same with the appropriate source kernel.
Click to expand...
Click to collapse
Had no idea the source was available for these devices, thanks for sharing. T397 source is in the repository. Let me know if there is something that I can do to assist. I've not compiled these sources although I've compiled other things. Possible to use this tablet as a phone with this ROM as stock T397 ( even after installing several different dialers does not dial ) ?
slomo2 said:
Had no idea the source was available for these devices, thanks for sharing. T397 source is in the repository. Let me know if there is something that I can do to assist. I've not compiled these sources although I've compiled other things. Possible to use this tablet as a phone with this ROM as stock T397 ( even after installing several different dialers does not dial ) ?
Click to expand...
Click to collapse
I can't check the dialer thing, as I don't even have cellular network on my Tablet.
I'll try to build the recovery for the T397 later today, but you will have to check it I guess, as I have no access to that one.
Shedaim said:
I can't check the dialer thing, as I don't even have cellular network on my Tablet.
I'll try to build the recovery for the T397 later today, but you will have to check it I guess, as I have no access to that one.
Click to expand...
Click to collapse
This will be great, let me know if I can help, perhaps document.
slomo2 said:
This will be great, let me know if I can help, perhaps document.
Click to expand...
Click to collapse
Ok, so this is a first try, so I believe it's not going to work, but who knows? we may get lucky.
Recovery for SM-T397 - Android 7.1.2
If it doesn't get installed or leads to a bootloop, I'm gonna need you to pull the boot.img from your device, or send me a link of the stock ROM if it's available.
Please follow the intsallation process described on the README file on the github repository
Shedaim said:
Ok, so this is a first try, so I believe it's not going to work, but who knows? we may get lucky.
Recovery for SM-T397 - Android 7.1.2
If it doesn't get installed or leads to a bootloop, I'm gonna need you to pull the boot.img from your device, or send me a link of the stock ROM if it's available.
Please follow the intsallation process described on the README file on the github repository
Click to expand...
Click to collapse
Thank you! Successfully installed. I found this video helpful for this generation of Samsung device and learning how to navigate recovery and download modes. I disabled auto-reboot in ODIN per your instructions, but it wasn't clear to me how to power-off after download so as to be able to go into recovery without booting so after adequate time I just pulled the battery. I'll spend the evening playing with things and report back, but so far everything seems to be working
---------- Post added at 11:27 PM ---------- Previous post was at 11:15 PM ----------
slomo2 said:
Thank you! Successfully installed. I found this video helpful for this generation of Samsung device and learning how to navigate recovery and download modes. I disabled auto-reboot in ODIN per your instructions, but it wasn't clear to me how to power-off after download so as to be able to go into recovery without booting so after adequate time I just pulled the battery. I'll spend the evening playing with things and report back, but so far everything seems to be working
Click to expand...
Click to collapse
One thing I notice, 7.1.1 is what was/is installed on my tablet now. Not sure what version of Android available on Samsung Opensource or how to check it, but I suspect it is the same since nothing has been pushed OTA.
7.1.1 is what The T397U should have already been on before you started. Mine is and I have not installed this recovery as of yet. Just wanted to let you know it's where it should be.
slomo2 said:
Thank you! Successfully installed. I found this video helpful for this generation of Samsung device and learning how to navigate recovery and download modes. I disabled auto-reboot in ODIN per your instructions, but it wasn't clear to me how to power-off after download so as to be able to go into recovery without booting so after adequate time I just pulled the battery. I'll spend the evening playing with things and report back, but so far everything seems to be working
---------- Post added at 11:27 PM ---------- Previous post was at 11:15 PM ----------
One thing I notice, 7.1.1 is what was/is installed on my tablet now. Not sure what version of Android available on Samsung Opensource or how to check it, but I suspect it is the same since nothing has been pushed OTA.
Click to expand...
Click to collapse
Awesome. I really had my doubts being it the first build and all. I guess, there aren't really any major differences.
If it's possible, can you go through the TWRP checklist here
Some of the tests aren't really necessary, but it's a good checklist to go by anyway.
That way, I can officially add it to the OP.
Shedaim said:
Awesome. I really had my doubts being it the first build and all. I guess, there aren't really any major differences.
If it's possible, can you go through the TWRP checklist here
Some of the tests aren't really necessary, but it's a good checklist to go by anyway.
That way, I can officially add it to the OP.
Click to expand...
Click to collapse
Sorry for delay. I've done the following tests all with the expected results. The only thing I noticed compared to previous installations of TWRP that I've performed ( some years ago ) is that the load time of recovery seems long at 1:15. Also a message about "RECOVERY NOT SEANDROID ENFORCING" which I suspect is normal. Tablet has been working without incident. Thanks again.
Blocking checks
- Correct screen/recovery size
- Working Touch, screen
- Backup to internal/microSD
- Restore from internal/microSD
- reboot to system
-ADB ( yes, if this means being able to access from ADB while in recovery )
Medium checks
- Screen goes off (and on )
- F2FS/EXT4 Support, exFAT/NTFS where supported
- all important partitions listed in mount/backup lists
===> define important ? - depends on the device, i guess
= Assume we can still boot a recovery (aboot/lk is still there for fastboot), can restore everything left ?
- backup/restore to/from external (USB-OTG) storage
- Correct date
Minor checks
- MTP export
- reboot to bootloader
- reboot to recovery
- poweroff
- battery level
- USB mass storage export
- set brightness
- vibrate
Security Policy Updates should not be applied to this system ?
Since this is stock Samsung OS that is rooted I'm guessing this system is still SELinux "enforcing" so does this mean that I can/should say yes to Security Enhancements automatic updates from Samsung ? Any explanation or link on this matter appreciated.
Hey @Shedaim, thanks a lot for this recovery, would it be possible to release an update for oreo?
maddada said:
Hey @Shedaim, thanks a lot for this recovery, would it be possible to release an update for oreo?
Click to expand...
Click to collapse
Hey, sorry for the very late answer.
I'm currently not working on Android and I've never tried on OREO, so my politically correct answer would be: "Right now there is no plan to work the same magic on OREO, but whoever wants, can try to use the device tree I created with a new official OREO kernel (didn't know they have one already)".
Anyway, keep checking the forum from time to time, I may have found the time to work on it
Links to the device tree and other tools used are in the main page of this thread.
Thank you,
Shedaim
I Pay 100$ for making my Galaxy Tab Active 2 booting when its charging
Hey guys,
i hope somebody can help me.
Im trying since 2 Weeks to make my Galaxy Tab Active 2 booting when its charging.
I try all the ways i found (fastboot, LPM change and Autoboot App) and nothing was successful.
So i hope to find with this way somebody who would help me to get the feature.
I need it because i installed the Active 2 on my Harley Davidson as my navigation.
And the problem is that i make a Novalauncher thats looking like the original Harley Davidson one and starts without a code.
So when i put the Tablet in the Mask i dont get a method to press to power button and when i make a method (hole trough the mask or something) then everybody can start up my tablet and use it.
So if somebody can help me with that i will pay them 100$ for helping!
you can contact me at [email protected].
thanks alot
Excuse me for a moment, but i have a Galaxy Tab Active 2 WIFI (sm-t390) and im looking for a custom recovery for it. All i can find for this model is the SM-T395 variant of TWRP,root, etc. Absolutelly nothing for the SM-T390? Does any one have any ideas???? Thank you in advance either way.
sCOTTN916 said:
Excuse me for a moment, but i have a Galaxy Tab Active 2 WIFI (sm-t390) and im looking for a custom recovery for it. All i can find for this model is the SM-T395 variant of TWRP,root, etc. Absolutelly nothing for the SM-T390? Does any one have any ideas???? Thank you in advance either way.
Click to expand...
Click to collapse
I used the methods and recovery here for my tablet which is a T397U...works flawlessly. The same should work for the wifi T390 you have aswell.
Flash process
I am new to the rooting process. This will be my first time. What is the actual flash process? How do I flash the rom on my tablet?
All the links are dead can anyone please post this recovery
i can Flash this twrp-3.2.3-0-gtactive2lte-7.1.2.tar, Odin says pass, but there is no TWRP. it boots into System. when i stop and boot to recovery, there is stll custom recovery from T395XXU5CSH2.
Any hints?