Related
Hi all!
i wrote reviews for two devices that are very interesting on checking together.
iPega 9023 rev2 -> Telescopic bluetooth controller for smartphones/phablets/tablets and standalone usage.
Teclast X89
There is a summary of the Teclast X89 Device. (sorry, but i can´t post complete article here, due the limitations of the characters by message on this forum)
_______________________________________________________________________________
[REVIEW] Teclast X89 Baytrail Tablet Dual OS (Windows & Android)
Acknowledgments
To Geekbuyingstore for send me a sample of their product Teclast X89 to test it and write this review.
Note about this review
This article is the first part of the main review of the device. Currently i get bricked the device when trying to update/install a clean windows version, and i can´t keep testing for now, until i found the way to recover it
When i get the device unbricked (if i get this), i will post a second part with steps for recovery, firmware update, tips and tricks for this device.
This article is based on general usage of the device, and for windows get many videos of games running directly on the device itself, for showing what you can expect of this.
For technical info and benchmarking on windows, when i get this device operative again, i will update this article with these sections.
Apologize if the article is not enough informative as you can expect. I'll do my best to bring a second part with more info about this device.
Product showcase(Checking of the external view of the package)
First of all, i never mention about packaging of the store that sent to me their articles, because usually i don´t consider interesting to mention, but this time i will do an exception because i get so pleased about this point.
For this review, Geekbuying sent to me two devices (but i wrote in different articles) that correspond to a suggested (by me) combo for use together:
Tablet Teclast X89
iPega 9023 controller
Both of them come in the same package, but fully protected, first with the typical plastic with bubbles, covering all the content:
Then, there is a bag with protective system for avoiding shocking of the devices.
The package arrives without any kind of problems, with the original packaging of the devices in perfect condition.
I wanted to remark this because is not usual that stores give this attention on the devices they send.
Now, back to the device itself. the packaging of it is simple, but all main texts are in chinese.
In the front we found the name of the product (Teclast tPad), and the Intel logo, that give to us a main clue about what is inside.
Back part is the description of the product in chinese
Note that there is no info about the specific model of the tablet (Teclast X89)
Inside we found the basic distribution of the package
Product information
According with the manufacturer, or searching info on web pages, we can found many sources of information about the device and sometimes these information may be not consistent (may be different from one web page to other), and this may cause some confusion for anybody that wants to get info about this product.
On this section i will post the info i get from the manufacturer (or is not possible, the web page that i consider more reliable), listing only the relevant points for a tech analysis of the product, and omit these points that don´t get any relevant info about the device (as many time we found on many pages, things such video capabilities, mail capabilities, etc, that really are software based features that we can install on the device, and not a real feature of the device itself)
I did not found the official specs on Teclast webpage. There is the specs of the previous version (X89HD), but not for this specific device (Teclast X89, or Teclast X89 Retina Display)
Operating System: Android 4.4 & Windows 8.1 OS (Dual Boot)
Model: Teclast X89 Dual OS
Announced: 2014-07
Color: White
Shell Material: Plastic
Display
Size: 7.9 Inch
Resolution: 2048*1536
Display Technology: IPS Retina capacitive touch screen
CPU&GPU
CPU Manufacturer: Intel
CPU Model: Bay Trail-T Z3735F
CPU Core: Quad Core
CPU Speed: 1.83GHz
RAM&ROM
RAM Type: DDR3L
RAM: 2GB
Hard Drive Type: eMMC
Hard Drive Capacity: 32GB
Extend Card: T-FLASH(Support 32G MAX)
Other Functions
Camera
Front: 2.0MP
Back: 5.0MP (Autofocus)
HDMI: Up to 1080p
3G: Supporting external 3G modem
Bluetooth: 4.0
GPS: NO
G-Sensor: Four way
Power
Battery Type: Li-ion battery, 5000mAh
Battery / Run Time(up to)
Wifi On: 4 hours
Wifi Off: 8 hours
Power Device Type: AC Adapter, AC 100-240V
Charging Voltage: DC 5V, 2A
Communications
Wireless ConnectionWIFI
Wireless Protocol802.11 b/g/n
Dimensions200 ×138 ×7.4mm
Net Weight512g
Connectors Ports
1 x Micro USB Port
1 x Earphone jack
1 x Micro HDMI port
1 x Micro SD Card slot
Hope you found interesting and useful.
_______________________________________________________________________________
Zalu2!
Not booting to windows after root
Hi,
I was reading your review about teclast x89, it is awesome.
I was following your instruction for rooting my dual boot teclast x89 (E7ED), and everything went great, i was rooted.
But then my problem apear, i can't boot into windows. Menu for selecting which OS to boot, dissapear. I try every single combination of key, but everytime it boots to Android. CAN YOU PLEASE HEEEEELP ME?
Thanks
djshorty said:
Hi,
I was reading your review about teclast x89, it is awesome.
I was following your instruction for rooting my dual boot teclast x89 (E7ED), and everything went great, i was rooted.
But then my problem apear, i can't boot into windows. Menu for selecting which OS to boot, dissapear. I try every single combination of key, but everytime it boots to Android. CAN YOU PLEASE HEEEEELP ME?
Thanks
Click to expand...
Click to collapse
Hi.
The rooting method will not affect to booting selectiong of OS.
of select, power on the device, and after release the power button, press VOL- & VOL+ at the same time.
the device will ask you to select an Operating System.
another way is connect any USB keyboard (via USB OTG cable), and when turning on the device hit quickly and repeat the "supr" key, for entering to BIOS.
once you get on BIOS interface, go to second screen and select "OS Selection" (or something this way, sorry i can´t check now) as first booting method.
This will enable the OS selection screen
check my review (on my blog) and follow the instructions for configuring the bios for select OS, and add more time for pressing Supr (by default is 1 or 2 seconds, i don´t remember. i suggest 4 or 6 seconds)
Greetings!
Deen0X said:
Hi.
The rooting method will not affect to booting selectiong of OS.
of select, power on the device, and after release the power button, press VOL- & VOL+ at the same time.
the device will ask you to select an Operating System.
another way is connect any USB keyboard (via USB OTG cable), and when turning on the device hit quickly and repeat the "supr" key, for entering to BIOS.
once you get on BIOS interface, go to second screen and select "OS Selection" (or something this way, sorry i can´t check now) as first booting method.
This will enable the OS selection screen
check my review (on my blog) and follow the instructions for configuring the bios for select OS, and add more time for pressing Supr (by default is 1 or 2 seconds, i don´t remember. i suggest 4 or 6 seconds)
Greetings!
Click to expand...
Click to collapse
thanks for the reply,
i try both of your method but no luck,
First, i select power on the device, and after release the power button, press VOL- & VOL+ at the same time. It goes in "dmx" fastboot mode,
Second,
When i enter in bios (supr-del key), in boot manu i have 3 options:
1. UEFI OS (it boots directly to android)
2. Windows boot manager (it boots directly to win)
3. UEFI: built in EFI shell( it opens shell)
can you please check in your tablet what option you have at boot manu?, are they same with mine, what did you select?
What ever i try, i can only boot to android or windows, i cant get screen where i can choose what os to start. Before it was screen this screen
with Operating System selection, but now is gone..
please help!!
p.s in windows now, touch is not working, android is ok.
Thanks
djshorty said:
thanks for the reply,
i try both of your method but no luck,
First, i select power on the device, and after release the power button, press VOL- & VOL+ at the same time. It goes in "dmx" fastboot mode,
Second,
When i enter in bios (supr-del key), in boot manu i have 3 options:
1. UEFI OS (it boots directly to android)
2. Windows boot manager (it boots directly to win)
3. UEFI: built in EFI shell( it opens shell)
can you please check in your tablet what option you have at boot manu?, are they same with mine, what did you select?
What ever i try, i can only boot to android or windows, i cant get screen where i can choose what os to start. Before it was screen this screen
with Operating System selection, but now is gone..
please help!!
p.s in windows now, touch is not working, android is ok.
Thanks
Click to expand...
Click to collapse
If you has been removed this View attachment 3193425
TRY IT →bbs.teclast.com/forum.php?mod=viewthread&tid=389148
mooncake5874 said:
If you has been removed this View attachment 3193425
TRY IT →bbs.teclast.com/forum.php?mod=viewthread&tid=389148
Click to expand...
Click to collapse
Yes, i removed that Stupid of me
Thanks, i will try this, but i dont know chinese, i try to download and tell you results.Is this apk?or all firmware?
Thanks
djshorty said:
Yes, i removed that Stupid of me
Thanks, i will try this, but i dont know chinese, i try to download and tell you results.Is this apk?or all firmware?
Thanks
Click to expand...
Click to collapse
I made the same mistake:crying:,but I can't find download for this apk at that time. so I reinstall all firmware.
this APK backup. file path“/system/app/”
↓
View attachment VManager.apk
GOOD LUCK!
mooncake5874 said:
I made the same mistake:crying:,but I can't find download for this apk at that time. so I reinstall all firmware.
this APK backup. file path“/system/app/”
↓
View attachment 3193597
GOOD LUCK!
Click to expand...
Click to collapse
Thanks,
i install it but no luck.
Should i open this program and select something, or is it enough thaat i installed it?
ANd it will be very good if someone who knows to make a tutorial in english to flash new firmware from scratch (instaling dual boot, android, windows) like x98, that is good tutorial.
Thanks
djshorty said:
Thanks,
i install it but no luck.
Should i open this program and select something, or is it enough thaat i installed it?
ANd it will be very good if someone who knows to make a tutorial in english to flash new firmware from scratch (instaling dual boot, android, windows) like x98, that is good tutorial.
Thanks
Click to expand...
Click to collapse
Maybe you can use google translation
mooncake5874 said:
Maybe you can use google translation
Click to expand...
Click to collapse
I use google translate, but it is awful, i downlod tutorial pdf file, and translated, but i am afraid that i can make mistake because translation is awful.
If someone who knows chinese and english can translate it right it will be good.
Or someone can confirm that tutorial for x98 3g is the same as this only the files are different, that is also good think to do.
currently, i'm writting a second part of the review, with instructions for flashing the device, installing android and windows (both)
for now, i'm a little bit busy and i can´t give so much time, but let me some days and i will publish this part of the review, for helping flashing the device.
Deen0X said:
currently, i'm writting a second part of the review, with instructions for flashing the device, installing android and windows (both)
for now, i'm a little bit busy and i can´t give so much time, but let me some days and i will publish this part of the review, for helping flashing the device.
Click to expand...
Click to collapse
Thanks for everything i manage to repair my tablet by installing dual boot.
If you need help about your review, i can help just tell me. And as suggestions to your review, you can write what apps are safe to remove, so people cant get into trouble like me. Also you can write how can we install only android or only windows, for big storage 32gb to be used only for 1 system
Thanks everybody.
Hibernat does not work
Hello X89 owners,
i also have the newest dual boot retina display version and i am really impressed by the tablet. All works fine and great performance. Only one thing does not work that worked fine for all my other windows tablets i use before. I am not a big fan of connected standby because it still drains battery, so i use "%windir%\System32\rundll32.exe powrprof.dll,SetSuspendState" command to hibernate the devices (because default button is not visible).
Unfortunately it does not work with the teclast x89. If i run "%windir%\System32\rundll32.exe powrprof.dll,SetSuspendState" hibernate command it shuts down the tablet but after reboot it does not restore the hibernate state, it simply boots up normally. I also checked event log having error:
error: Windows failed to resume from hibernate with error status 0xC000000D.
I also tried recreating hiberfil.sys and checking disc consistence. But nothing helped. So can you try this on your devices? I simply want to know if its a general Teclast X89 problem...
Thx and br
Arangato
Hi Arangato.
I'm doing some testings with MeegoPad T01 (similar baytrail than Teclast), and as you i can´t get this thing to hibernate by command line
messing with the device, in some moment i get an effective hibernate state, but i'm not sure how i get.
in some testings, after unplug the power and connect again, the device boot windows (quick than normal) from scratch, and show me the application i get running previous the sleep (burnout paradise)
i will keep doing tests, but i really don´t know how to replicate for now. This messages really is for confirme that there is some way to do a sleep on this device, but of course, is not the standard way.
i'm thinking now... may be when i sleep the device, i think i keep the power button pressed to shutdown... for long time, after this unplug power source, wait few seconds and plug again. (something like this i did, i think)
keep testing...
"powercfg -h on" should enable hibernate mode
But the difference between a cold boot and hibernate resume is not that long
aitnog said:
"powercfg -h on" should enable hibernate mode
But the difference between a cold boot and hibernate resume is not that long
Click to expand...
Click to collapse
i tried but did not enabled.
yeah, may be on timing is the same, but there is a good difference. With Hibernating, when you get back, get all the tasks you're doing in the same status (games, work, etc). i really prefer hibernate than complete turn off for this reason.
but thanks anyway.
i recovered the tablet and doing some testings (but for now i´m centered on other devices i must release reviews).
meanwhile, i published the guide for flashing and recover the device, translating the original in chinese, and adding some other stuff that may be useful.
http://manguiro.blogspot.com/2015/03/guide-teclast-x89-installation-guide.html
Note: if your device cannot recover (like mine) with normal steps, or there is some message about corrupt partition table, invalid disk, etc, you must do some manual steps (the flashing tool can´t handle this)
i will put my steps on other article (really, i need to publish another reviews first), but basically i opened the flashing xml file, and check that there are some commented lines that, if you uncomment, the flashing tool will omit anyway, then you must do these steps manually, from fastboot command.
with this, i be able to 100% recover the device. Now i get android and windows working without problems.
hope you found useful.
Touch has stopped working! In windows.
djshorty said:
Thanks for everything i manage to repair my tablet by installing dual boot.
If you need help about your review, i can help just tell me. And as suggestions to your review, you can write what apps are safe to remove, so people cant get into trouble like me. Also you can write how can we install only android or only windows, for big storage 32gb to be used only for 1 system
Thanks everybody.
Click to expand...
Click to collapse
Hey my touch stopped working in windows too.
Anyone have any idea how to fix it? I have only had this for 1 hour and now it is useless for what I got it for...
I need to find out how to restore the touch capabilities to windows. I tried refreshing, it happened after I went to android for the first time.
I've got the Atom Z3736 Win 8.1 version of this but does anyone know if it's possible to install dual boot because this version uses the Z3735?
Because just about all the forums for this device are in Chinese and using Google translate is a nightmare to even find the right people to ask.
com.android.systemui keeps crashing when charging level at 100%
Hello,
recently I get my Teclast X89 tablet, but unfortunately it appeares to have a problem. When the battery charging level comes to 100% (at 99% everything is OK) tablet becomes totally unusable. When the screen is switched off it cannot be waken up and when I use the tablet a window pops up telling that "Process com.android.systemui has stopped", like here:
imgur.com/hjWI1lP
After restart everything is OK, but it really grinds my gears. Maybe someone know how to fix this problem?
Please halp!
Bogusz
Hello Deen0X, thanks for your reply and explanation. Now i know it seems to be a general problem. If you have a tablet like this connected standby is activated and with this hibernate is also enabled by default (you should find a hiberfil.sys file in C root, its used for fast boot option) so you normally can hibernate with the command i mentioned before: "%windir%\System32\rundll32.exe powrprof.dll,SetSuspendState" this works fine for my other acer win 8.1 tablet (OOTB system) directly after install. But not for the Teclast x89. Of course having a normal boot and restore from hibernate is pretty same time, also fast boot does not have that big impact. I like hibernate because it "freezes" actual system status without draining battery after that.. i often have several browser windows opened, some other metro apps and i like to resume to that state and not to have a clean boot.
@Deen0X: could you check your event log? Is there also the message that device could not restore from hibernation?
So keep me updated, or maybe anybody else can try the "%windir%\System32\rundll32.exe powrprof.dll,SetSuspendState" command to hibernate the teclast x89 dual boot. It will not harm the device. I have the experience if hibernation is disabled and you run this command it simply locks the screen..
Thx and br
Arangato
Hi,
So I came across an Elite Tablet with below Spec, looking for root/twrp/cwm:
Baylake
anzhen4mrd7_w
iNtel Atom Z3735F
Kitkat
Came across a similar device, ANZHEN4_M BAYTRAIL1418C453
c1nd3r said:
Hi,
So I came across an Elite Tablet with below Spec, looking for root/twrp/cwm:
Baylake
anzhen4mrd7_w
iNtel Atom Z3735F
Kitkat
Click to expand...
Click to collapse
I can get to fastboot, but can't find any twrp to flash. Recovery is locked with a pin. It's one of those hotel tablets that lets you control the lights and order room service etc. Thought it could be fun to take it to the next step, but need some guidance.
Sorry to bring up a very old thread. I was just given one of these for free from a family member. This was a promotional device given away at a seminar. I would like to hack this to learn a bit but need a place to start.
Details from the tablet:
- IFWI VERSION: 1G-141024
- SERIAL_NUM: Baytrail 160ADA152
- DROIDBOOT VERSION: 2.0
- PRODUCT: ANZHEN4_N
It will boot into fastboot and recovery/droidboot but seems to be very restricted. I have options to upgrade via ADB, as well as loading a file from the SD card in the main settings however I assume these both need a signed file to succeed.
Google has led to some dead ends. Did find a listing of specifications from a shady looking russian site, linked here.
I would love to find the base firmware to have something to fall back on if I mess up, or even some help on how to go about pulling this myself from the device. From there I can work on root and loading custom roms. Crawl first.
Very appreciated for any future help!
have the same product and not find how root the device. Please helpme.
I have an AT&T Galaxy S7 Active - US Model - SM-G891A
I haven't seen any credible sources with a root for this device. From what I can tell, it is identical to the Qualcomm version of the Galaxy S7(non-edge) with one exception; The S7 Active has the "Active button".
Since almost every Qualcomm variant of the Galaxy S7 has been rooted, is there a chance that the S7 active is rootable? or is there already a root?
Let me know if you need any other information or if you would like a test dummy.
UPDATE: Successful Root Of the Galaxy S7 Active (Qualcomm)
PLEASE USE THE POLL TO LET US KNOW WHAT VERSION OF FIRMWARE YOU END UP ROOTING. IF YOU FAIL, PLEASE PROVIDE US WITH AS MUCH INFORMATION, ABOUT YOUR EXPERIENCE, THAT YOU CAN. THIS WAY WE CAN DO OUR BEST TO HELP YOU AND CONTINUE IMPROVING THIS ROOT.
ROOT - CLICK BELOW
Original Tutorial Credit(HERE)
Updated for Galaxy S7 Active (by NotSoMiniGun)
Make sure you have downloaded these files:
• SuperSU v2.74 (updated) SuperSU v2.76
• Modified ODIN
• Unlock boot.tar
• Fastboot
• Samsung Official USB Drivers v1.5.40
Make sure you meet these requirements:
• Firmware PG7, PH2, PI2, PK2, PL1(6.x.x only)
• NO NOUGAT SUPPORT YET (1/30/2017)
• >60% Battery charge
Additional suggestions and warnings:
• Make sure you know both your Samsung account info and your Google account info. You will need these, for Factory Reset Protection, if something goes wrong and you need to wipe your phone.
• I, also, recommend rooting a clean/wiped/reset phone. This rules out quite a few things that could cause failures or strange behavior during or after the rooting process.
• You WILL lose some speed and battery life. This is not an optimized root. If you are comfortable with that fact, then go ahead. You’ve been warned. Do not complain about it on this thread.
• Install the Samsung drivers even if your computer already seems to have them. Right click and run the .exe as administrator. REBOOT after install. This rules out another potential point of failure.
• MAKE SURE YOU ONLY HAVE YOUR PHONE PLUGGED IN. Make sure there are as few USB devices, as possible, plugged into your computer during the rooting process.
• DISABLE YOUR ANTI-VIRUS
Step 1:
Read EVERYTHING above. Twice.
Step 2:
Open Settings->About Device and scroll down to “Build Number”. Tap it repeatedly until it says you have activated “Developer Mode”.
Step 3:
Open Settings->Developer Options and turn ON both “USB Debugging” and “OEM Unlock”.
Step 4:
Turn phone OFF. Once off, hold (Volume Down, Center Home, and Power) until you see a blue warning screen.
Step 5:
Press Volume Up and plug your phone into your computer. You should have blue screen that says “Downloading”.
Step 6:
All of the files should be downloaded to your computer and be sitting in your “Downloads” folder. Un-zip the ODIN-modified.zip, right click the ODIN .exe, and run as administrator.
IF YOU DON’T SEE A BLUE BOX AT THE TOP LEFT OF ODIN THEN DO THESE STEPS AGAIN:
1. Run the Samsung USB Drivers .exe again.
2. Reboot your computer.
3. Make sure your data cable isn’t damaged and is plugged in all the way.
Step 7.
Select AP and choose the ENG Boot file ending in .tar. Then click “Start”. The blue box should eventually turn green and say “PASS”.
IF YOU GET STUCK IN A BOOT LOOP:
“If your phone ends up in a bootloop (which most likely will), you will need to do a factory reset. To do this, hold down Volume Down, Center Home, and Power buttons together until your phone resets then quickly switch the Volume Down to Up key while holding the rest of the buttons down until you see “Recovery booting” at the top-left of the screen. If you mess up, don’t worry you can keep trying until you get it right. Once in stock recovery, choose “Wipe data/factory reset” then “yes” to do a factory reset. THIS WILL ERASE EVERYTHING ON YOUR PHONE! Reboot and after 5-10 minutes, you should be welcomed by a welcome screen, go ahead and login.”
Step 8:
Go through the set-up screens until you can repeat Steps 2 & 3.
Step 9:
Unzip fastboot.zip to its own directory. Unzip the contents of SuperSU and copy them to the fastboot folder.
Step 10:
Shift-RightClick in the white space below the files in the fastboot folder. Click “Open Command Window Here”.
Step 11:
Type the following in the Command Prompt:
Code:
adb devices
Code:
root.bat
Watch your phone for any messages and make sure to tap OK. If it freezes, unplug your phone, plug it back in, and restart from Step 10.
Step 12:
Install BusyBox from the app store. Open the app and make sure it installs to “/system/xbin”. DO NOT INSTALL IT ANYWHERE ELSE. THIS WILL CAUSE PROBLEMS AND REQUIRE A FLASH AND RE-ROOT.
Step 13:
You are now successfully rooted. Read the rest of this post carefully to fix the following items:
WiFi password reset
SecurityLogAgent
General Lag and other issues.
TO UNROOT - CLICK BELOW
Link to Instructions Provided By (jembot)
WARNING:
DO NOT uninstall "SecurityLogAgent", DO freeze it using Titanium Backup. Uninstalling it seems to cause instability and random system crashes.
DO NOT attempt to update SuperSU BINARY UPDATE:You can update to v2.76 from v2.74 with the provided file (updating the app is also ok) after root. Other attempts to update will break WiFi, Cellular Data, Access to the Play Store, and will require a reflash in ODIN to regain functionality.
If you do accidentally do this, just reflash to PI2 firmware and check for OTA updates, or use the update packages, to bring your device back to PL1 Firmware. It will lag a lot, so be patient.
FIRMARE AND PACKAGE DOWNLOAD LINKS
PI2 Firmware Download Password: G891AUCS2API2_FULL_FSFD (Cost me $10 lol)
PG7 Firmware Download
PG7 to PH1 Update
PH1 to PI2 Update
PI2 to PK2 Update
PK2 to PL1 Update
PI2 to PL4 Update
PK2 to PL4 Update
PL1 to PL4 Update
SuperSU v2.74
SuperSU v2.76
Modified ODIN
Unlock boot.tar for PL1 or earlier (credit activefan01)
Original boot.tar for PL4 (use if updating to nougat)
imsservice.apk (use to remove VoLTE and RCS icons)
Fastboot (bundle used in the rooting tutorial)
Samsung Official USB Drivers v1.5.40
Other Issues and Solutions:
If you get and MD5 error:
Your download for the tar file was probably incomplete or corrupt. To fix, re-download and make sure it downloads completely before trying again.
If ODIN does not recognize the file or doesn't display it in the browser:
The file should end in a .tar extension, not a .MD5 extension. Use THIS tutorial to show file extensions in windows(if you can't see them), and make sure the file ends in .tar
If you still experience significant lag or battery usage:
1. Try any of the suggested CPU governor apps on this thread.
2. I, personally, noticed the biggest improvement with Device Control [root] from the play store
3. Enable - Power Efficient Workqueue
Enable - LCD power reduce
Core Limits - 1593 MAX - 307 MIN and Lock Frequencies
Governor - Interactive and Lock Governor UPDATE: "PERFORMANCE" seems to work significantly better at removing lag and, surprisingly, saving battery
Enable - Automatic FStrimming
Enable - Core Control and MSM-Thermal
Enable - Reapply on boot with a 15 second delay
4. Under developer options, consider setting all of the animation speeds to 0
5. As always, you are responsible for any damage to your device or data
For those of you who want Xposed:
1. Install Flashfire from the Play Store
2. Put these 2 files on your phone FRAMEWORK and APK
3. Use Flashfire to flash the zip to your phone.
4. Install the APK and Reboot.
5. Enjoy
6. Avoid these modules or risk bricking your phone:
- Gravitybox - Confirmed
- Xblasttools - Confirmed
For those of you who want to Tether/Hotspot:
1. Install XTether in Xposed
2. Activate and Reboot
3. The native hotspot/tether options will now work in settings
4. Enjoy more.
If you have issues with AT&T keeping you from setting up your phone:
1. Make sure you connect to WiFi on first step of the Samsung setup
2. Do the normal setup until you get to the AT&T Setup portion
3. Let the setup "scan" for connections on WiFi
4. Dismiss the warning about limited WiFi and turn the WiFi OFF
5. Proceed with the rest of the setup by hitting NEXT or SKIP when available
6. You should now be able to use your phone and should be able to setup all AT&T related software separately.
To fix WiFi password reset issue:
1. Install BuildProp from the Play Store
2. Change the value of ro.securestorage.support=false
3. Save, reboot, enter WIFI password for the last time!
How to remove the VoLTE and RCS(hurricane looking thing) icons: (tested by FtaWolf)
1. Install a file explorer like FX
2. Set Read/Write access to System Partition, use the 3 dot menu in the top right
3. (be careful not to touch anything else, I soft-bricked my phone twice on accident)
3. Navigate to /system/priv-app/imsservice
4. Rename file imsservice.apk to imsservice.apk.bak, tap and hold to rename
5. Copy THIS file into the same folder
6. Then set permission to 644, again, tap and hold to change permissions
7. Reboot and you should be good to go.
How to add HotSpot and MobileData toggles or remove unwanted toggles (credit slimshouki)
1. Install CSC Feature Expert from the PlayStore
2. Scroll down until you find "Config Def Quick Setting Item" (Do not search for it, you wont find it)
3. Add " ,WiFiHotspot,MobileData"
4. (OPTIONAL) Delete any toggles you don't want. Make you there is a single comma between all values
5. Open Settings->Personal->Backup and Reset->Reset Settings
6. After it reboots you should see the toggles.
COMPATIBILITY STATUS:
Galaxy S7 & S7 Edge Qualcomm Variant Root: Confirmed Successful On: PG7, PH2, PI2, PK2, PL1 || Fails On: PL4, Android 7.0 Update
Poot Debug APK Qualcomm Root: Incompatible
Dirty Cow Exploit: Temp/Partial Root
TO DO:
Determine Root Method/Source (activefan01, perhaps you can weigh in)
Custom Recovery (if possible)
Optimize Current Root Method (currently takes a decent toll on battery life)
7.0.0+ Root (currenty only works on pre-nougat systems)
If no one has any answers on the availability of a functioning root for the Samsung Galaxy S7 Active, can some one tell me why the Active series of phones seem to be actively ignored? Is there an extreme difference in hardware? Is it difficult for devs to get their hands on the device? Is there not enough interest?
The basic gist with the Active line is: nobody really cares in terms of development because they're just not popular devices in terms of sales. They're better devices, in my opinion, but that doesn't mean much to anyone else obviously.
Root would be nice to muck around with I suppose, be able to do some more things, run some root-required apps and so on but, I can live without it so far.
The fact that there is no working firmware available from AT&T or Samsung anywhere could have something to do with it as well perhaps. I've been looking for a pure stock image just in case I have issues but so far it's just non-existent and probably always will be unavailable.
The Active models are great devices, just not popular to the majority of buyers unfortunately and that immediately translates into not being popular with developers or the community in general. I'm getting 2.5 days of battery life per charge with at least 7 hours of SOT with this one I have now so I'm a happy camper without any complaints.
br0adband said:
The basic gist with the Active line is: nobody really cares in terms of development because they're just not popular devices in terms of sales. They're better devices, in my opinion, but that doesn't mean much to anyone else obviously.
Root would be nice to muck around with I suppose, be able to do some more things, run some root-required apps and so on but, I can live without it so far.
The fact that there is no working firmware available from AT&T or Samsung anywhere could have something to do with it as well perhaps. I've been looking for a pure stock image just in case I have issues but so far it's just non-existent and probably always will be unavailable.
The Active models are great devices, just not popular to the majority of buyers unfortunately and that immediately translates into not being popular with developers or the community in general. I'm getting 2.5 days of battery life per charge with at least 7 hours of SOT with this one I have now so I'm a happy camper without any complaints.
Click to expand...
Click to collapse
I'm only getting 4hrs of sot..... Hmm
I don't use cellular except when I'm out and about, I use about 40-45% brightness or less (auto brightness when out and about), I have roughly 155 packages disabled with Package Disabler Pro, that's about it.
With a 4000 mAh battery, the GS7A better last as long as mine is lasting or something is absolutely wrong I'd say - it's not that hard to get this kind of battery life and usage but as always YMMV.
I am also searching for root. I got some link in google search, but they are not working. I bought this unlocked device in India. While it works fine with old network, but it does not work with new network which are purely 4g and use voice over LTE for calls.
Sent from my SAMSUNG-SM-G891A using Tapatalk
---------- Post added at 02:13 PM ---------- Previous post was at 02:12 PM ----------
I need to put Indian CSC on this phone.
Sent from my SAMSUNG-SM-G891A using Tapatalk
br0adband said:
I don't use cellular except when I'm out and about, I use about 40-45% brightness or less (auto brightness when out and about), I have roughly 155 packages disabled with Package Disabler Pro, that's about it.
With a 4000 mAh battery, the GS7A better last as long as mine is lasting or something is absolutely wrong I'd say - it's not that hard to get this kind of battery life and usage but as always YMMV.
Click to expand...
Click to collapse
Would you be willing to compile a list of all the packages you disabled? Maybe then I can get better battery life.
Sent from my SAMSUNG-SM-G891A using Tapatalk
Here's the list as XML and it's attached as well for import to Package Disabler Pro:
Code:
<importExportSetting>
<disabledPackages class="java.util.ArrayList">
<string>com.mobeam.barcodeService</string>
<string>com.monotype.android.font.rosemary</string>
<string>com.matchboxmobile.wisp</string>
<string>com.sec.android.widgetapp.samsungapps</string>
<string>com.samsung.android.app.galaxyfinder</string>
<string>com.sec.android.app.chromecustomizations</string>
<string>com.samsung.android.app.aodservice</string>
<string>com.samsung.svoice.sync</string>
<string>com.drivemode</string>
<string>com.sec.android.app.clipvideo</string>
<string>com.sec.android.devicehelp</string>
<string>com.android.wallpapercropper</string>
<string>com.sec.android.app.wfdbroker</string>
<string>com.att.android.digitallocker</string>
<string>com.samsung.android.app.withtv</string>
<string>com.sec.android.app.safetyassurance</string>
<string>org.simalliance.openmobileapi.service</string>
<string>com.samsung.android.easysetup</string>
<string>com.android.externalstorage</string>
<string>com.sec.android.easyonehand</string>
<string>com.sec.factory</string>
<string>com.cequint.ecid</string>
<string>com.directv.dvrscheduler</string>
<string>com.samsung.android.qconnect</string>
<string>com.amazon.mShop.android.install</string>
<string>com.sec.android.app.tourviewer</string>
<string>com.sec.android.Kies</string>
<string>com.samsung.faceservice</string>
<string>com.monotype.android.font.foundation</string>
<string>com.sec.android.widgetapp.easymodecontactswidget</string>
<string>com.samsung.android.email.provider</string>
<string>com.samsung.android.firmware.tsp</string>
<string>com.google.android.configupdater</string>
<string>com.sec.android.app.billing</string>
<string>com.sec.android.app.minimode.res</string>
<string>com.samsung.android.game.gamehome</string>
<string>com.samsung.android.slinkcloud</string>
<string>com.dti.att</string>
<string>com.dsi.ant.service.socket</string>
<string>com.sec.android.AutoPreconfig</string>
<string>com.sec.android.app.soundalive</string>
<string>com.samsung.android.securitylogagent</string>
<string>com.android.carrierconfig</string>
<string>com.samsung.android.app.watchmanager</string>
<string>com.samsung.android.app.assistantmenu</string>
<string>com.locationlabs.cni.att</string>
<string>com.samsung.SMT</string>
<string>com.samsung.aab</string>
<string>com.samsung.vvm</string>
<string>com.sec.android.ofviewer</string>
<string>com.samsung.hs20provider</string>
<string>net.aetherpal.device</string>
<string>com.sec.att.usagemanager3</string>
<string>com.dsi.ant.sample.acquirechannels</string>
<string>com.samsung.android.smartface</string>
<string>com.android.mms</string>
<string>com.android.backupconfirm</string>
<string>com.sec.android.app.SecSetupWizard</string>
<string>com.hancom.office.editor.hidden</string>
<string>com.sec.bcservice</string>
<string>com.android.calendar</string>
<string>com.samsung.android.providers.context</string>
<string>com.sec.android.preloadinstaller</string>
<string>com.sec.android.uibcvirtualsoftkey</string>
<string>com.samsung.android.sdk.professionalaudio.utility.jammonitor</string>
<string>com.android.sharedstoragebackup</string>
<string>com.yellowpages.android.ypmobile</string>
<string>com.samsung.android.app.colorblind</string>
<string>com.android.printspooler</string>
<string>com.android.dreams.basic</string>
<string>com.att.myWireless</string>
<string>com.sec.android.app.dictionary</string>
<string>com.samsung.android.app.talkback</string>
<string>com.samsung.android.game.gametools</string>
<string>com.asurion.android.mobilerecovery.att</string>
<string>com.sec.smartcard.manager</string>
<string>com.sec.allsharecastplayer</string>
<string>com.samsung.app.slowmotion</string>
<string>com.samsung.android.smartcallprovider</string>
<string>com.directv.promo.shade</string>
<string>com.dsi.ant.plugins.antplus</string>
<string>com.samsung.android.personalpage.service</string>
<string>com.samsung.advp.imssettings</string>
<string>com.samsung.android.app.advsounddetector</string>
<string>com.sec.android.app.clockpackage</string>
<string>com.samsung.android.app.mirrorlink</string>
<string>com.samsung.android.sm</string>
<string>com.sec.android.widgetapp.locationwidget</string>
<string>com.google.android.apps.walletnfcrel</string>
<string>com.samsung.android.controltv</string>
<string>com.samsung.mdl.radio</string>
<string>com.sec.spp.push</string>
<string>com.dsi.ant.server</string>
<string>com.samsung.android.gamepad.service</string>
<string>com.samsung.android.allshare.service.fileshare</string>
<string>com.synchronoss.dcs.att.r2g</string>
<string>com.sec.android.mimage.photoretouching</string>
<string>com.samsung.android.universalswitch</string>
<string>com.samsung.helphub</string>
<string>com.sec.android.app.sns3</string>
<string>flipboard.boxer.app</string>
<string>com.google.android.feedback</string>
<string>com.google.android.apps.photos</string>
<string>com.android.managedprovisioning</string>
<string>com.sec.android.providers.tasks</string>
<string>com.ubercab</string>
<string>com.monotype.android.font.chococooky</string>
<string>com.android.dreams.phototable</string>
<string>com.samsung.safetyinformation</string>
<string>com.facebook.katana</string>
<string>com.samsung.app.highlightplayer</string>
<string>com.sec.android.app.vepreload</string>
<string>com.android.providers.partnerbookmarks</string>
<string>com.cleanmaster.sdk</string>
<string>com.samsung.android.keyguardwallpaperupdator</string>
<string>com.android.wallpaper.livepicker</string>
<string>com.samsung.android.beaconmanager</string>
<string>com.amazon.mShop.android</string>
<string>com.samsung.android.app.FileShareClient</string>
<string>com.facebook.system</string>
<string>com.sec.android.soagent</string>
<string>com.samsung.android.fmm</string>
<string>com.samsung.android.mdm</string>
<string>com.smlds</string>
<string>com.ws.dm</string>
<string>com.samsung.knox.appsupdateagent</string>
<string>com.samsung.android.spayfw</string>
<string>com.samsung.app.newtrim</string>
<string>com.samsung.android.spay</string>
<string>com.sec.hearingadjust</string>
<string>com.samsung.android.dlp.service</string>
<string>com.samsung.android.bbc.bbcagent</string>
<string>com.samsung.android.voicewakeup</string>
<string>com.sec.android.splitsound</string>
<string>com.wssnps</string>
<string>com.samsung.android.app.watchmanagerstub</string>
<string>com.policydm</string>
<string>com.samsung.android.app.FileShareServer</string>
<string>com.enhance.gameservice</string>
<string>com.americanexpress.plenti</string>
<string>com.sec.svoice.lang.es_US</string>
<string>com.lookout</string>
<string>com.samsung.android.sm.provider</string>
<string>com.monotype.android.font.cooljazz</string>
<string>com.android.bluetoothmidiservice</string>
<string>com.facebook.appmanager</string>
<string>com.samsung.voiceserviceplatform</string>
<string>com.samsung.aasaservice</string>
<string>com.samsung.android.allshare.service.mediashare</string>
<string>com.sec.android.app.mt</string>
<string>com.sec.knox.switcher</string>
<string>com.qualcomm.atfwd</string>
<string>com.sec.android.app.magnifier</string>
<string>com.samsung.android.video</string>
<string>com.amazon.kindle</string>
</disabledPackages>
</importExportSetting>
Thank you. I'm going to mess around with it later.
Sent from my SAMSUNG-SM-G891A using Tapatalk
Here first run with sot with S7 Active.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SAMSUNG-SM-G891A using Tapatalk
FtaWolf said:
Here first run with sot with S7 Active.
Click to expand...
Click to collapse
That's awesome, really it is, but what does that have to do with this thread and rooting it?
br0adband said:
That's awesome, really it is, but what does that have to do with this thread and rooting it?
Click to expand...
Click to collapse
Not thing. What did disabled package pro have do with thread. You didn't ? It.
Sent from my SAMSUNG-SM-G891A using Tapatalk
Back On Track
While I agree the S7 Active is a fantastic phone with fairly substantial battery life, those merits should be discussed in another thread such as HERE. The main goals of this thread are:
1. Determine if there is an available Root for the Samsung Galaxy S7 Active
2. Determine if any current exploits, for other models, could be modified to Root the S7 Active
- The Galaxy S7 (snapdragon model) Root
- Dirty Cow
- etc.
3. To offer help or a reward to anyone willing to make progress on this topic.
I personally am wiling to donate $50+ to anyone able to provide a legitimate root (or to a charity of their choice).
Please let me know if there is an official way of presenting a bounty or if there is any other way I can help progress this project.
I fully agree with "Notsominigun". This phone is fantastic in all aspects, but root is very essential in some scenario to utilize its potential, especially those who are using unlocked phone in other network and country. Some features are not working which can be enabled easily by rooting and taking full control of the phone.
I have searched for "Dirty Cow" and found it can be used to root any android device with following steps:
http://androiding.how/dirty-cow-root-android/ ; I will try it once get a Linux system
-snip-
Poot
Is there any evidence that the POOT generic Qualcomm root would work on the Galaxy S7 active?
NotSoMiniGun said:
Is there any evidence that the POOT generic Qualcomm root would work on the Galaxy S7 active?
Click to expand...
Click to collapse
Most likely not as that is an old method. You could try the method mentioned a few posts up.
Sent from my SAMSUNG-SM-G891A using Tapatalk
first of all, I apologize for my "English", I had to use google translator.
I am edu present, I'm from Argentina, and was looking for information on how to root the s7 active, no luck, but I found information that perhaps more experienced people can help them find a solution ....
Qualcomm Quadrooter Exploit
QuadRooter Android sounds like another serious security exploit. Which one can allow a malicious app Apparently to gain root access based on Qualcomm Android phones and tablets, enabling the app to do pretty much what Then it pleases. , According to Check Point, the research group discovered That QuadRooter, up to 900 million Android devices Qualcomm Could be AFFECTED. This exploit targets the drivers Qualcomm Which is why it is specific to this hardware. As of the 1st Augusts security update Google has patched 3 of the 4 will patch vulnerabilities and the last one in the September 1st update. To keep your device safe from bugs it is always in Original bests to stay on top of your security updates. One of the best ways to protect your phone from malicious software is to download apps only from trusted sources or google play.
If you want to check and see if your device can possible be vulnerable to this threat Then you can download and run QuadRooter Scanner by check point. Personally I am hoping That a developer can figure out this exploit and use it to get many android users root access. I am sure someone can create a app gets root then a INJECTS That SuperSU and their binary into the device. If you are hoping for the same I recommend not updating to new security patches and give the developers some time to get root access devices.
I would not be surprise to see this QuadRooter vulnerability Implemented into Kingroot app some time soon, as it would make there app on Android devices unstoppable. What do you think about this bug please comment below and let me know.
This information I found in rootjunky.
I hope you can serve something
---------- Post added at 01:58 AM ---------- Previous post was at 01:45 AM ----------
rahuldixit2010 said:
I fully agree with "Notsominigun". This phone is fantastic in all aspects, but root is very essential in some scenario to utilize its potential, especially those who are using unlocked phone in other network and country. Some features are not working which can be enabled easily by rooting and taking full control of the phone.
I have searched for "Dirty Cow" and found it can be used to root any android device with following steps:
http://androiding.how/dirty-cow-root-android/ ; I will try it once get a Linux system
Click to expand...
Click to collapse
how did it go?
I tried it but not got success.
rahuldixit2010 said:
I fully agree with "Notsominigun". This phone is fantastic in all aspects, but root is very essential in some scenario to utilize its potential, especially those who are using unlocked phone in other network and country. Some features are not working which can be enabled easily by rooting and taking full control of the phone.
I have searched for "Dirty Cow" and found it can be used to root any android device with following steps:
http://androiding.how/dirty-cow-root-android/ ; I will try it once get a Linux system
Click to expand...
Click to collapse
That's awesome! Now, who is familiar with Linux... can dump boot.img and kernel.img from the phone...
I found that it's here:
cd dev/block/platform/soc/624000.usfshc/by-name/
dd if=/dev/block/sda6 of=/sdcard/efs.img
dd if=/dev/block/sdd10 of=/sdcard/aboot.img
dd if=/dev/block/sda13 of=/sdcard/fota.img
dd if=/dev/block/sda16 of=/sdcard/modem.img
dd if=/dev/block/sda17 of=/sdcard/boot.img
dd if=/dev/block/sda18 of=/sdcard/recovery.img
I don't know, will these comands work in linux?
Short version of question: How can I unbrick my ONEPLUS 3 (A3000) if I cannot boot to Android and OEM Unlock AND USB Debugging both have not been enabled?
Long version: Phone was recently purchased second hand from a third-party market (Kijiji, kind of like craigslist for Canadians). Person I bought it from claimed in the ad that the device was in a bootloop and couldn't access the OS. I had in the past successfully saved a ONEPLUS 1 from bricked status, so I didn't feel a simple bootloop would pose much of an issue. That, and at the price he was selling I really couldn't turn it down.
I tried various different methods of restoring the phone's partitions, OS, and firmware to stock/custom, but had no real luck with any (I will list below what I have attempted). If there was a root cause of this, I believe it's due to the fact that some part of the phone's storage partition (boot or system if I had to guess) had become corrupted at some point. Given the volume of threads I've seen here and elsewhere online, I wouldn't rule out a bad OTA flash, but doesn't really matter. What does matter, however, is that the Android OS is inaccessible despite my best efforts, and the bootloader is set to locked and ADB Debugging remains off.
Generally speaking, is there a way to access Developer Options to correct both these issues through terminal or a tool? I'm confident that I can get my device working again if I could access this menu, but as of yet I have had no luck.
Methods used to restore/info worth mentioning
While I don't doubt their effectiveness at large, for whatever reason I have yet to find a tool/guide that yields the anticipated results upon completion. MSM Download Tool (V3 and V4) have both been downloaded, executed, and completed numerous times, but will still not boot past the loading screen upon completion.
According to Unified Android Toolkit, my device build is being detected as "OnePlus3 7.0 NRD90M" and All-in-One Toolkit is showing that Android 6.0.1 is installed.
Drivers are all installed correctly, as proven both via tools downloaded and through Windows CMD terminal (adb devices, fastboot devices, adb get-state, etc)
Stock recovery and bootloader modes can both be reached through both hardware keys and software commands. I will note that it seems to take longer than I'd expect to boot to either of these modes using hardware keys.
I have utilized multiple USB ports, Type-C cables, different OS' on two laptops (MS Windows 10 and 7, FWUL Linux). I usually have no problem with the device being detected by the system. When I have, it usually involved one pesky USB cord.
common commands used and their effects:
fastboot OEM unlock: fails, cannot be done remotely
fastboot flash x: fails, remote: flashing partitions not allowed
ADB push: fails. cannot access partition
ADB devices: device is seen by system with serial and state
fastboot devices: device is seen by system with serial
ADB sideload: varying results. Some will fail at 0% citing "total xfer: 0.00x", some will reach 47% and fail (always exactly 47% oddly). Generally if the sideload operation passes 47% it will complete.
fastboot format/erase x: fails, partition formatting/erasing not allowed
fastboot continue: executes, but does not help with android bootloop issue as I had hoped
While I searched for an answer online, I did come across an infosec whitepaper regarding ONEPLUS 3 vulnerabilities, though it was over a year old. To my surprise, the command they had been entering works on my device, but I'm not sure how to properly use it effectively. The command used was fastboot OEM boot_mode [rf/wlan/ftm/normal]. Now, I was unable to determine what each of the triggers does, but what I did discover is that with boot_mode set to rf, my device would display chinese/korean lettering in lieu of the usual ONEPLUS logo with "powered by Android" below. This is also how I managed to have my device show up in CMD terminal for ADB commands to be issued. To the best of my knowledge though, there doesn't seem to be much point to it as I couldn't push/pull any files. Does anybody know where I could find more info on this command, as I'd like to know what the other triggers accomplish.
I've just about exhausted every available resource looking for an answer, but im still coming up short. I've gone as far as contacting ONEPLUS directly, but without proof of purchase they can't (more accurately won't) help me. And while it's not a business practice I would personally support, I can understand why they have it implemented. I've contacted a few phone shops in the area, but none have been able to assist me further than I've already gotten in this process.
I apologize again for creating a new thread about this, but I felt my circumstances warranted a new thread due to the bulk of the others having either an unlocked bootloader or TWRP installed, neither of which I do.
So, can anybody offer their help or suggest something I haven't already tried? Or should I be on EBAY looking for motherboards? Thanks in advance.
Calgary84 said:
Short version of question: How can I unbrick my ONEPLUS 3 (A3000) if I cannot boot to Android and OEM Unlock AND USB Debugging both have not been enabled?
Long version: Phone was recently purchased second hand from a third-party market (Kijiji, kind of like craigslist for Canadians). Person I bought it from claimed in the ad that the device was in a bootloop and couldn't access the OS. I had in the past successfully saved a ONEPLUS 1 from bricked status, so I didn't feel a simple bootloop would pose much of an issue. That, and at the price he was selling I really couldn't turn it down.
I tried various different methods of restoring the phone's partitions, OS, and firmware to stock/custom, but had no real luck with any (I will list below what I have attempted). If there was a root cause of this, I believe it's due to the fact that some part of the phone's storage partition (boot or system if I had to guess) had become corrupted at some point. Given the volume of threads I've seen here and elsewhere online, I wouldn't rule out a bad OTA flash, but doesn't really matter. What does matter, however, is that the Android OS is inaccessible despite my best efforts, and the bootloader is set to locked and ADB Debugging remains off.
Generally speaking, is there a way to access Developer Options to correct both these issues through terminal or a tool? I'm confident that I can get my device working again if I could access this menu, but as of yet I have had no luck.
Methods used to restore/info worth mentioning
While I don't doubt their effectiveness at large, for whatever reason I have yet to find a tool/guide that yields the anticipated results upon completion. MSM Download Tool (V3 and V4) have both been downloaded, executed, and completed numerous times, but will still not boot past the loading screen upon completion.
According to Unified Android Toolkit, my device build is being detected as "OnePlus3 7.0 NRD90M" and All-in-One Toolkit is showing that Android 6.0.1 is installed.
Drivers are all installed correctly, as proven both via tools downloaded and through Windows CMD terminal (adb devices, fastboot devices, adb get-state, etc)
Stock recovery and bootloader modes can both be reached through both hardware keys and software commands. I will note that it seems to take longer than I'd expect to boot to either of these modes using hardware keys.
I have utilized multiple USB ports, Type-C cables, different OS' on two laptops (MS Windows 10 and 7, FWUL Linux). I usually have no problem with the device being detected by the system. When I have, it usually involved one pesky USB cord.
common commands used and their effects:
fastboot OEM unlock: fails, cannot be done remotely
fastboot flash x: fails, remote: flashing partitions not allowed
ADB push: fails. cannot access partition
ADB devices: device is seen by system with serial and state
fastboot devices: device is seen by system with serial
ADB sideload: varying results. Some will fail at 0% citing "total xfer: 0.00x", some will reach 47% and fail (always exactly 47% oddly). Generally if the sideload operation passes 47% it will complete.
fastboot format/erase x: fails, partition formatting/erasing not allowed
fastboot continue: executes, but does not help with android bootloop issue as I had hoped
While I searched for an answer online, I did come across an infosec whitepaper regarding ONEPLUS 3 vulnerabilities, though it was over a year old. To my surprise, the command they had been entering works on my device, but I'm not sure how to properly use it effectively. The command used was fastboot OEM boot_mode [rf/wlan/ftm/normal]. Now, I was unable to determine what each of the triggers does, but what I did discover is that with boot_mode set to rf, my device would display chinese/korean lettering in lieu of the usual ONEPLUS logo with "powered by Android" below. This is also how I managed to have my device show up in CMD terminal for ADB commands to be issued. To the best of my knowledge though, there doesn't seem to be much point to it as I couldn't push/pull any files. Does anybody know where I could find more info on this command, as I'd like to know what the other triggers accomplish.
I've just about exhausted every available resource looking for an answer, but im still coming up short. I've gone as far as contacting ONEPLUS directly, but without proof of purchase they can't (more accurately won't) help me. And while it's not a business practice I would personally support, I can understand why they have it implemented. I've contacted a few phone shops in the area, but none have been able to assist me further than I've already gotten in this process.
I apologize again for creating a new thread about this, but I felt my circumstances warranted a new thread due to the bulk of the others having either an unlocked bootloader or TWRP installed, neither of which I do.
So, can anybody offer their help or suggest something I haven't already tried? Or should I be on EBAY looking for motherboards? Thanks in advance.
Click to expand...
Click to collapse
Thanks for the exhaustive description. You seem to have covered every known method. If the MSM Tool also fails, I think that it is a hardware issue and you are better off searching for a new motherboard instead of wasting further time on trouble-shooting.
Best of luck!
tnsmani said:
Thanks for the exhaustive description. You seem to have covered every known method. If the MSM Tool also fails, I think that it is a hardware issue and you are better off searching for a new motherboard instead of wasting further time on trouble-shooting.
Best of luck!
Click to expand...
Click to collapse
I was afraid of that..... is there a way to test a given hardware component?
Have you tried the unbrick tool FULL updated: https://mega.nz/#!NmhhgZyB!CM7Fw8VjECiMIhh4gRXUx24QVCiE599_ZFAPDf08AiM
acetone802000 said:
Have you tried the unbrick tool FULL updated: https://mega.nz/#!NmhhgZyB!CM7Fw8VjECiMIhh4gRXUx24QVCiE599_ZFAPDf08AiM
Click to expand...
Click to collapse
Indeed I have, dozens of times between the full and mini versions. I've even gone as far as running the toolkits featuring MSMDownloadTool v4.0 to see if it achieved different results (it did not). The mini tool would finish doing its thing (turned the text green upon completion),but I would face varying partitions not being flashed correctly. The full version completes and does not have these varying partitions missing, but the device would then be either stuck in a bootloop where it will eventually reboot itself, or would hang indefinitely on the "swirling dots" loading screen. I tried the remedy of deleting cache in recovery, but this did not help.
deleted
***UPDATE*** - As I mentioned in this thread earlier, I noticed a discrepancy between the variant type listed on my actual device and the variant type returned when queried via fastboot. This got me thinking, and to make a long story somewhat shorter, I found that while most stock Oxygen images I attempt to sideload onto the device fail (at precisely 47%, oddly), I was able to sideload two different Hydrogen images without any resistance at all. I'm guessing something to do with the eMMC vs UFS file storage systems and how each OS uses them.
So I got Hydrogen flashed onto my my device. Smooth sailing, right? Afraid not. Despite fastboot's output clearly stating it was a successful transfer, and the stock recovery on the device echoing this, I still cannot get the OS to load. Now i' stuck with the loading screen hanging indefinitely prior to animation occurring, so basically the static ONEPLUS logo. Factory resets and cache wipes have done nothing to help the situation along. Conventional wisdom from the threads here seem to say using the MSMTool is the right answer..... and thus the circle of frustration is complete with me arriving back where I started. Does anybody have another suggestion I can try out? Still can't flash/boot to TWRP, unlock bootloader, or access Android to activate USB Debug/OEM Unlock either btw.
Have you tried flashing just the firmware, i havent flashed in years but i would assume you could sideload the firmware as well?
voodooline said:
Have you tried flashing just the firmware, i havent flashed in years but i would assume you could sideload the firmware as well?
Click to expand...
Click to collapse
Guess who didn't read? And after a year without flashing + a lack of reading skills, you still think you could solve this case? That's a spirit.
===
You better do pm some devs in dev section and point them to this thread and see if they can help, if you are still curious.
My guess is dead emmc, it can be replaced without buying the whole board.
150208 said:
Guess who didn't read? And after a year without flashing + a lack of reading skills, you still think you could solve this case? That's a spirit.
===
You better do pm some devs in dev section and point them to this thread and see if they can help, if you are still curious.
My guess is dead emmc, it can be replaced without buying the whole board.
Click to expand...
Click to collapse
I did read it, its funny always someone who has to be a **** about things. I should have been more specific. He was able to flash h2os. So he could try to flash the firmware for h2os to see if that gets it to boot.
voodooline said:
I did read it, its funny always someone who has to be a **** about things. I should have been more specific. He was able to flash h2os. So he could try to flash the firmware for h2os to see if that gets it to boot.
Click to expand...
Click to collapse
Magnificent, bro.
You're a truly genius.
* Prelude
What started this journey was noticing that Tasker had restricted call screening
to android versions 10+. I would be delighted to hear what techniques fellow
forum members use to fight spam calls. I am a complete beginner, and so I
thought I would detail my journey in case it proves useful for others. There is
some outdated information and plenty of online tutorials, it just takes some
time to sort it out.
I have a Huawei P20 lite ANE LX3.
* Unlocking the Bootloader
I believe this is by far the most tedious step. Now that I am free from carrier
contracts, I know that my next phone will not be from a manufacturer with a
locked bootloader. In any case you may have some luck emailing Huawei directly
or through paid third-party services. What worked for me was potatoNV
GitHub - mashed-potatoes/PotatoNV: Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620
Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620 - GitHub - mashed-potatoes/PotatoNV: Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620
github.com
The documentation on the repository is perfectly fine. Specifically in my case,
the device first showed under device manager as 'USP SER' and I had to reinstall
the test point drivers (found in the above README) for it to turn into 'Huawei
USB COM 1.0.' PotatoNV did its job and I managed to get my unlock code.
* Project Treble/GSI? Fastboot? ADB?
Again, being new to all of this, I did notice a lot of noise when searching
online for information. The most informative links I found useful:
- https://github.com/phhusson/treble_experimentations/wiki/Frequently-Asked-Questions-(FAQ)
- https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
- https://developer.android.com/studio/releases/platform-tools
What is worth repeating is to USE THE GOOGLE PLAY APP 'TREBLE INFO' over the
more popular 'Treble Check', which falsely informed my that I needed an A image
rather than being fine with an A/B image. This wasted a lot of my time.
Initially I went down the route of using TWRP to flash the image, but this led
me to a soft brick (could very well be my own fault). The phone was frozen to
the TWRP splash screen, 'adb reboot bootloader' would not work. Power plus
volume down or volume up also had no effect. With no access to e-recovery or the
bootloader, I had really dug myself into a hole.
* Unscrewing a bricked phone
My last chance at fixing this consisted of getting the stock service firmware.
[NO ROOT] [BOOTLOADER LOCK] How to install an update [DLOAD Method]
I'm very happy :D:D After spending a lot of time trying to figure out how to install an original firmware using the dload method, I managed to find a guide that explains how to do it and today I will report the main steps: First of all, we need...
forum.xda-developers.com
This forum thread was useful and on unscrewing the situation. The real useful
part of the above link was the 'Software Upgrade Guidelines' documentation.
So ultimately what unbricked my phone was following the direction to press all
three buttons (power, volume up, volume down) at once to enter "automatic
upgrade mode." I gather this was supposed to utilize the 'dload' folder I copied
over earlier. As an aside, it was a lifesaver that 'adb shell' gave me access to
some unix commands to make poking around easier. The automatic upgrade using the
'dload' folder failed.
BUT RESTARTING FROM THIS "AUTOMATIC UPGRADE MODE" GRANTED ME ACCESS TO RECOVERY
MODE VIA THE POWER BUTTON + VOLUME UP whereas before this was not the case. By
the grace of God this allowed me to download a recovery image from Huawei
servers. How much longer will their servers retain this image? I don't know, but
I'm grateful either way.
* Lineage OS successfully flashed
What instead worked for me was flashing the "GSI image without TWRP" - from the
2nd of the 3 links above. This is the image that I used:
lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img.xz
For sake of completeness M Rahman's 2018 article was still mostly accurate, the
'-u' flag may be omitted from 'fastboot -u flash system name_of_system.img'. The
only other thing I would append to his instructions is -AIF-'s recommendation to
4. Run command fastboot reboot, unplug your phone, when appears on screen yellow
warning, press and hold for 3 sec Volume Up . In eRecovery select 'Wipe
data/factory reset'.Reboot . - From:
https://forum.xda-developers.com/t/losq-lir-lineageos-17-1-18-1-unofficial-gsi.4219291/
I say this because I had seen the power button + down volume/up volume technique
yield different results depending on whether the phone was connected to the
computer. I suspect this is the fault of HiSuite, but who is going to track down
a bug like this?
* Evaluation
Pros:
- I had solved my initial problem.
- The new phone feeling!
Cons:
The most noticeable deficiency was that adding an external SD card AS SYSTEM
STORAGE would never finish; I gave it about a day before giving up.
I will add further reports as they come up.
In conclusion I give props to Huawei for keeping that server image alive, but
last I heard they were pivoting away from smartphones into clean energy
altogether. If I were to do it all over again, I'm not sure it would be worth
it. This took a good day's worth of time.
Big thanks to the AOSP developers and the XDA community for buying
my old P20 lite a bit more time. I'm also interested in which companies the
community considers friendly to "popping the hood"/tweaker mentality.
Hope this was helpful for someone,