Related
Hi guys!
Just recently I bought the "HDC Galaxy Note 2" off of fastcardtech. I got it a few days ago, am fairly pleased with it except for the slight miscalibrated touch screen. There are some apps on various markets aiming to fix this by re-applying new calibrations. The problem is that you'll have to be rooted in order to run them.
The phone comes with a built-in calibration setting, called "Als_ps calibration", which you can utizile to correct the sensor. Alas, it only corrects the phone's recognition of obstacles placed above it, so that you accidentaly wouldn't press any undesired button during a call.
Phone: http://www.fastcardtech.com/Galaxy-Note-2-Mega
Here's what I've done so far!
Enabled USB-debugging and installed USB-drivers. [MT65xx_USB_Driver.zip]
Tried the bin4ry root method, normal mode. [Root_with_Restore_by_Bin4ry_v18.zip]
This method:
http://forum.xda-developers.com/showthread.php?t=1886460
Everything works just fine until the phone reboots. Bin4ry is then unable to mount or copy the last files needed to apply root permission, see attached picture.
I have attached my specs in a screenshot, nevermind the quality, t'was done by another crap-camera! Sorry ;]
Any kind soul who can help me root this thing?
Edit:
Rooting this device has been made possible by GT35pro. See posts below.
same problem
KristN91 said:
Hi guys!
Just recently I bought the "HDC Galaxy Note 2" off of fastcardtech. I got it a few days ago, am fairly pleased with it except for the slight miscalibrated touch screen. There are some apps on various markets aiming to fix this by re-applying new calibrations. The problem is that you'll have to be rooted in order to run them.
The phone comes with a built-in calibration setting, called "Als_ps calibration", which you can utizile to correct the sensor. Alas, it only corrects the phone's recognition of obstacles placed above it, so that you accidentaly wouldn't press any undesired button during a call.
Phone: http://www.fastcardtech.com/Galaxy-Note-2-Mega
Here's what I've done so far!
Enabled USB-debugging and installed USB-drivers. [MT65xx_USB_Driver.zip]
Tried the bin4ry root method, normal mode. [Root_with_Restore_by_Bin4ry_v18.zip]
This method:
http://forum.xda-developers.com/showthread.php?t=1886460
Everything works just fine until the phone reboots. Bin4ry is then unable to mount or copy the last files needed to apply root permission, see attached picture.
I have attached my specs in a screenshot, nevermind the quality, t'was done by another crap-camera! Sorry ;]
Any kind soul who can help me root this thing?
Click to expand...
Click to collapse
omg i have the exact same problem, did you get a solution? PLEASE i need to root it so bad
CWM installed and rooted the HDC galaxy note 2 MAGE / MEGA
rebmoe said:
omg i have the exact same problem, did you get a solution? PLEASE i need to root it so bad
Click to expand...
Click to collapse
I just created the cwm recovery and root. The link is on my blog. The zip file is password protected so be sure to get it from my blog page.
http://gt35pro-mobile-gadgets.blogspot.sg/2013/02/cmw-recovery-english-and-root-for-hdc.html
After you have clockwork mod recovery, use it to flash the root access into the phone.
Have fun!
KristN91 said:
Hi guys!
Just recently I bought the "HDC Galaxy Note 2" off of fastcardtech. I got it a few days ago, am fairly pleased with it except for the slight miscalibrated touch screen. There are some apps on various markets aiming to fix this by re-applying new calibrations. The problem is that you'll have to be rooted in order to run them.
The phone comes with a built-in calibration setting, called "Als_ps calibration", which you can utizile to correct the sensor. Alas, it only corrects the phone's recognition of obstacles placed above it, so that you accidentaly wouldn't press any undesired button during a call.
Phone: http://www.fastcardtech.com/Galaxy-Note-2-Mega
Here's what I've done so far!
Enabled USB-debugging and installed USB-drivers. [MT65xx_USB_Driver.zip]
Tried the bin4ry root method, normal mode. [Root_with_Restore_by_Bin4ry_v18.zip]
This method:
http://forum.xda-developers.com/showthread.php?t=1886460
Everything works just fine until the phone reboots. Bin4ry is then unable to mount or copy the last files needed to apply root permission, see attached picture.
I have attached my specs in a screenshot, nevermind the quality, t'was done by another crap-camera! Sorry ;]
Any kind soul who can help me root this thing?
Click to expand...
Click to collapse
Kristen, where you able to re-calibrate after rooting; I just ordered this phone last week so I want to be prepared if need be.
londonflu said:
Kristen, where you able to re-calibrate after rooting; I just ordered this phone last week so I want to be prepared if need be.
Click to expand...
Click to collapse
The one I got did not have that screen calibration problem. Everything works good. Anyway, root is available now.
Superb!
Thank you for sorting this out!
-KristN91
Extra Guide
Follow the link provided by GT35pro in his first post.
To everyone attempting this flash;
!! First of all, copy the Superuser.zip to the root of your internal phone memory or external SD Card.!!
* Use a high-quality mini-USB cable (The one that comes with your phone should work just fine)
* Connect your MEGA to your pc, without the battery inserted.
(This device will connect and disconnect, when it's visible, be sure to grab it and follow the next step)
* Make sure that you have the right drivers for MTK65xx preloader "mtk65xx Vcom driver" and install them through the Device Manager.
* Insert your battery again, with the cable still connected, and install the second MTK65xx preloader.
* Disconnect phone from pc and remove the battery
* Start up Smart flash Tool and select the scatter file included in the package.
* Now, select and tick the checkbox for Recovery only. Smart Flash Tool will complain about the flash, due to it not containing all the appropriate files needed for a "secure boot". Nevermind that pop-up and proceed with downloading.
* Start Download
* Insert the battery and connect your phone to your pc, with that, the flashing should start.
* Boot Phone into recovery mode (pwr button and vol - or vol +) and install superuser from ZIP-file.
* After reboot you should be rooted.
///////////////
Fun Fact!
I actually managed to install a pre-rooted HDC S7100 rom on my MEGA.
The port isn't 100% accurate
-Invalid IMEI, this was fixed by Talkingmobile's guide; " how to write imei number for MTK 65XX " -Just google it!
-Auto-rotation is unavailable, no fix yet.
-Als_pl calibration is unavailable (resulting in active screen during call)
Besides that, the rom is arguably better than the MEGA's original N7100 rom, in terms of visual presentation.
Smooth transitions, vivid and vibrant colors would be a good example of aspects that would come out as improved over the original rom.
Interested in the S7100 rom? Just PM me and I'll provide the link.
Cheers!
S_ft_need_download_all_fail (4050)
I'm trying for several days, but always get this error in the flash tool: S_FT_NEED_DOWNLOAD_ALL_FAIL (4050)
Tried on Windows 7 x64, Windows 7 x32 and Windows XP SP3 (x32). Only on the Windows XP computer I was able to make a backup with Flash Tool using the Read Back option.
When I try to flash the red bar goes to 100% then the error message shows...
Does anyone get this error aswell, and did someone manage to solve this?
Please help, I'm in desperate need for root because I need touch screen calibration.
Thnx!!
YES! SUCCES!! I managed to root my HDC Mage :laugh: Did use another method though, check http://forum.xda-developers.com/showthread.php?t=2160490 if you are interested.
Anyway, now back to calibrating the touchscreen. What tools are good do fix touchscreen issues? I already tried http://forum.xda-developers.com/showthread.php?t=934500, but I still am not satisfied.
Thnx :good:
Just curious, if anyone that owns an HDC, is actually located in the USA?
londonflu said:
Just curious, if anyone that owns an HDC, is actually located in the USA?
Click to expand...
Click to collapse
Nope, the Netherlands. Why do you ask?
Sent from my GT-I9000 using xda app-developers app
jg77 said:
Nope, the Netherlands. Why do you ask?
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
Because I tried to order 5 different phones from China including Fastcardtech; they couldn't ship for some reason; even got an empty box from ZOPO mobile. I ended up buying the BLU here in the US, I'm kind of glad it happened, since now I have an N'vidia Tegra 4 CPU, that runs circles around the dual-core phones.
I did order one more phone on ebay from China, been waiting for 2 weeks now. MAKES ME WONDER IF THEY EVEN ACTUALLY SHIP TO THE US AT ALL?
Thank to Paypal I was able to get refunded everytime.
KristN91 said:
Follow the link provided by GT35pro in his first post.
To everyone attempting this flash;
!! First of all, copy the Superuser.zip to the root of your internal phone memory or external SD Card.!!
* Use a high-quality mini-USB cable (The one that comes with your phone should work just fine)
* Connect your MEGA to your pc, without the battery inserted.
(This device will connect and disconnect, when it's visible, be sure to grab it and follow the next step)
* Make sure that you have the right drivers for MTK65xx preloader "mtk65xx Vcom driver" and install them through the Device Manager.
* Insert your battery again, with the cable still connected, and install the second MTK65xx preloader.
* Disconnect phone from pc and remove the battery
* Start up Smart flash Tool and select the scatter file included in the package.
* Now, select and tick the checkbox for Recovery only. Smart Flash Tool will complain about the flash, due to it not containing all the appropriate files needed for a "secure boot". Nevermind that pop-up and proceed with downloading.
* Start Download
* Insert the battery and connect your phone to your pc, with that, the flashing should start.
* Boot Phone into recovery mode (pwr button and vol - or vol +) and install superuser from ZIP-file.
* After reboot you should be rooted.
///////////////
Fun Fact!
I actually managed to install a pre-rooted HDC S7100 rom on my MEGA.
The port isn't 100% accurate
-Invalid IMEI, this was fixed by Talkingmobile's guide; " how to write imei number for MTK 65XX " -Just google it!
-Auto-rotation is unavailable, no fix yet.
-Als_pl calibration is unavailable (resulting in active screen during call)
Besides that, the rom is arguably better than the MEGA's original N7100 rom, in terms of visual presentation.
Smooth transitions, vivid and vibrant colors would be a good example of aspects that would come out as improved over the original rom.
Interested in the S7100 rom? Just PM me and I'll provide the link.
Cheers!
Click to expand...
Click to collapse
I took out the battery then connect it to the pc and open device manager, it show mtk65xx preloader then the phone disconnect its self and connect back every two seconds is there a way to fix this pls
thank you
I took out the battery then connect it to the pc and open device manager, it show mtk65xx preloader then the phone disconnect its self and connect back every two seconds is there a way to fix this pls
farazafs said:
I took out the battery then connect it to the pc and open device manager, it show mtk65xx preloader then the phone disconnect its self and connect back every two seconds is there a way to fix this pls
Click to expand...
Click to collapse
Did you install all necessary drivers?
Sent from my GT-I9000 using xda app-developers app
---------- Post added at 08:21 AM ---------- Previous post was at 08:17 AM ----------
farazafs said:
I took out the battery then connect it to the pc and open device manager, it show mtk65xx preloader then the phone disconnect its self and connect back every two seconds is there a way to fix this pls
Click to expand...
Click to collapse
Did you install all necessary drivers? How does sp flash tool respond when you download the recovery?
Sent from my GT-I9000 using xda app-developers app
jg77 said:
Did you install all necessary drivers?
Sent from my GT-I9000 using xda app-developers app
---------- Post added at 08:21 AM ---------- Previous post was at 08:17 AM ----------
Did you install all necessary drivers? How does sp flash tool respond when you download the recovery?
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
I can Install all necessary drivers, when I Power OFF phone and connect it to my PC, in device manager it can show MT65xx Preloader (Com 9) connected n within 3 sec it can be disconnected.... in SP Flash Tool i can select recovery then press download button... then again i can connect phone, it's give me some 80xx error. it's mean that device not connect.
farazafs said:
I can Install all necessary drivers, when I Power OFF phone and connect it to my PC, in device manager it can show MT65xx Preloader (Com 9) connected n within 3 sec it can be disconnected.... in SP Flash Tool i can select recovery then press download button... then again i can connect phone, it's give me some 80xx error. it's mean that device not connect.
Click to expand...
Click to collapse
An 80Xx error does not always mean device not connected. It can also mean there is something not right in the scatterfile (error 8038). You should take a look at the sp flash tool logfiles. You can post them here so I can have a look.
jg77 said:
An 80Xx error does not always mean device not connected. It can also mean there is something not right in the scatterfile (error 8038). You should take a look at the sp flash tool logfiles. You can post them here so I can have a look.
Click to expand...
Click to collapse
Attached snapshot given below... always when I tried to flash Recovery from SP Flash Tool it's only give me this error.
farazafs said:
Attached snapshot given below... always when I tried to flash Recovery from SP Flash Tool it's only give me this error.
Click to expand...
Click to collapse
There is something wrong in the layout of the scatterfile. Can you post the logiles of sp flash tool? Just zip them all together.
I have had the exactly the same error with my HDC Mage. I just had to rename a small section of the scatterfile and then it was all good.
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
First Look Video
Full Review
Welcome to another "First Look" on a china phone. In this video we will have a look at the 5.5" Cubot X15. A very stylish chinaphone in good quality. In the video I also compare the Design with the LeTV S1, so check it out
Cubot X15 MTK6735, 5.5 FHD, 2.5D Glass, 4G LTE, OTG, SmartWake
The manufacturer Cubot are not exactly known for visually beautiful smartphones. But the new model called Cubot X15 is a whole new story. It is built very sturdy and has a very solid aluminium frame, so there is no way to bend it. The backcover is made of plastic, but this can not be opened, so you can not remove the battery. This is a dual sim dual standby smart phone. In general, the smartphone looks very nice and cool and almost like something from LeTV. Nevertheless, it is quite heavy in the hand, because it also include a large battery.
{
"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"
}
Specifications:
- 5.5 inch 2.5D FullHD Screen, 1920x1080 pixels
- MTK6735 64bit Quad Core, 1.3GHz
- Mali-T720 GPU
- Android 5.1 OS
- 2GB RAM + 16GB ROM
- Camera: Rear 16.0MP, Front 8.0MP
- OTG, HotKnot, Bluetooth 4.0, GPS/AGPS
- Smart Wake, Air Gestures
- MicroSD card support
- Dual SIM dual standby, Micro SIM, Nano SIM
- Network 2G/3G/4G:
- 2G: GSM 850/900/1800/1900MHz
- 3G: WCDMA 900/1900/2100MHz
- 4G: LTE 800/1800/2100/2600MHz
Source: http://notebookitalia.it
Great device, How about battery life and screen on time?
I am really looking forward to it. I am about to order a unit for myself. http://www.cubotmall.com/cubot-x15-4g-lte-mobile-phone.html , It is the official website? Anyone have any experience with CubotMall?
I'm looking to purchase that device, any owners out there.
How's the batter life?
Is it rootable?
randomjoe13 said:
I'm looking to purchase that device, any owners out there.
How's the batter life?
Is it rootable?
Click to expand...
Click to collapse
I'm still waiting for mine, it is not released yet.
s7yler said:
I'm still waiting for mine, it is not released yet.
Click to expand...
Click to collapse
According to that site it is available:
http://www.gearbest.com/cell-phones/pp_218613.html?wid=4 and this coupon gives you $26 off: X15GB
randomjoe13 said:
According to that site it is available:
http://www.gearbest.com/cell-phones/pp_218613.html?wid=4 and this coupon gives you $26 off: X15GB
Click to expand...
Click to collapse
Not available yet, also not at Gearbest, but I believe it will be in a few days. The shops say stock even days before they actually have real stock, experienced that many times.
UPDATE: I just got my X15 and so far I really like it! I have now added my "First Look" video to post #1
Anyone got this yet? Any root access? I hear I can't install nova on it? What's that about?!
Phone amazing. No root though. Someone help?
Snapchat lenses were working and stopped suddenly too.
Any at all got root access?
The Cubot X15 looks so beautiful! But it does not support waterproof?
Zunera M said:
The Cubot X15 looks so beautiful! But it does not support waterproof?
Click to expand...
Click to collapse
It is not waterproof
I have had this phone for a week now and its actually really good. The screen is quite responsive there seems to be no lag on even when there is a load on it, the brightness control and auto brightness is quit reasonable and in my opinion better than my previous phone the s4. The shut down and reboot times are very fast even when booting for the first time. Battery life is really good, when just normally using it no games just the occasional looking stuff up on google, using facebook all day and texting and calling it last be 61 hours. Gaming on it and heavy used produced an up time of 37 hours. The speaker shocked me since there is a grill for a second speaker but there is only one on the bottom, but sound quality is great. Call quality is pretty good people who normally used sound mumbled come in more clearly and i can actually make out what they are saying. Gaming performance is very good, hardly any lag from actual graphics or processing only lag for me came when my wifi was being bogged by my roommate. The screen itself is fairly water resistant but not water proof and i dont plan on testing that any further. The only con i really have found so far is that i cant root it whether it is my own ignorance on this type of phone or there isnt a reliable method out yet it still upsets me. My personal overall rating would have to be 8.5/10 I would definitely recommend this phone to people whom are on a budget and want a nice phone
Still no root access anyone? Or even a Snapchat fix? That's the only reason I want root, sad I know. No lenses on Snapchat is doing my head in
McMCC in the russian forum 4pda rooted his Cubot X15.
He used Pack-Flashtool-v5.1528.00.000.rar what seems to be the flash-tool of mediatek.
Maybe someone can try if he reaches to root his phone with these tools.
Sorry I can not post links yet.
That's good to know. I literally have no idea how to do that but thanks for giving me hope.
A Full Review video has now also been added to post #1
Finally got a Successful ROOT!
So after rooting I installed Nova and deleted the stock launcher and it improved responsiveness tenfold. I also started ripping out other apps that I know I'll never use like hotknot, Launcher, and have installed 3C Toolbox which after setting up TRIM and turning on all maintenance on boot has really helped. Droidoptimizer is awesome as well.
Everything you need to RooT
Alright, So this is everything that I managed to find,compile,tweak, and finally get to work on my Cubot x15 which should work for every other cubot x15. I'll tell you exactly how I managed to get root working and provide a link with the working cwm and drivers and the stock rom and a way to flash back to it. I used the stock 5.1 x15 scatter file to map out CWM and it works for me so far. Sorry I'm not too much of a writer but I'll try my best.
1. Every thing you need plus probably some you dont, https:// www.dropbox.com /sh/4iskxmmzxvj48z9/AACIs5Vm3Q_2yxGMIqktKadGa?dl=0
2. Now this is going to be how I did it step by step, if you know a better way or can see how i'm setting it up then help us if you know a faster way. I installed ADB-setup-1.4.2.exe first, hit yes on the 3 things that it asks. now these drivers won't detect the x15 but it installs all the ADB where it needs to go, mainly in C:\ADB and users\.android so if you know how to do it you can skip this part but if not I would install it.
3.Okay, so on your cubot go to settings, about phone, and tap on build 7 times to enable developer options. In developer options turn on USB debugging and OEM unlocking. Now OEM unlocking is going to wipe your phone back to stock, backup what ever you can like pictures, music, and so fourth, if you have a microSD card in your phone it won't wipe that so migrate what you can to your SD. Now this is the part that I got stuck on for a while trying every MTK tool and adb command so I'll save you some time. After you turn OEM unlocking on, power off your phone and then turn it back on while holding VOL + or up and power together, this should bring you into to a black screen with the choice to boot into Recovery/FastBoot//Normal, volume + changes choices and Vol - selects. Well need to manually put it into fastboot mode after the next step. so go to normal for now and reboot.
4. So download Nicks Cubot x15 root TooLs, there are the cubot drivers that we need in adb_fastboot_utils, what i did was unrar'd that folder into C:\ADB and replaced that adb drivers that we installed in the last step with the new ones we need for the cubot, it works pretty well. Install them by replacing the other ADB drivers but if it doesn't take then you can right click on your computer, go to manage, device manager, click in the window where you don't select anything , like under Universal Serial Bus controller when it's closed, you do this so that the action tab will then let you select add legacy hardware. Go to Action, Add Legacy Hardware, click on next, select install the hardware that I manually select from a list, Next, show all devices highlighted, Next, Have Disk, then browse to C:\ADB and find the folder, I'm using windows 8 so I ended up in C:\adb\usb_driver_mtk_win8 and click the .inf file. If windows gives you **** about not being signed and fails then you have to reboot while holding shift, go to advanced options and reboot without driver enforcement, i think it's number 7. if you do have to do that just repeat the device driver install steps and it should work. Now, after you get all this installed you can test it by opening CMD and typing adb devices. Your phone should show up but it will say unauthorized, if not make sure USB debugging is turned on in developer options and that your phone is plugged in via USB cable. if you get the unauthorized message open your lock screen and your phone should be asking you to authorize your computer, check always remember computer and authorize.
4. So now for the fun part. If you did it correctly you can now see your phone by typing adb devices in CMD prompt. If you can then make sure you saved what you wanted onto your sdcard and go to developer options and tick OEM unlocking again. now you should still have your ADB CMD prompt window open with your device being seen, if thats the case type, cd C:\adb, which should change your command directory to C:\ADB, after you switch directories type, adb reboot bootloader, your phone should reset to a black screen with some options, VOL + changes options and VOL - selects, if you have the option, select fastboot, if not then type fastboot devices. If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine but if you do see your device type, fastboot oem unlock. Now go to your phone and it will prompt you to make sure you want to unlock your bootloader, VOL + to accept or VOL - to reboot. hit VOL + and CMD prompt will let you know when it's finished. After it's finished. Leave the CMD prompt open and your phone in Fastboot mode. and read the next step.
5. Alright so your phone should be in fastboot mode, now in my included root tool kit I have included recovery images, recovery.img is the stock one and Cwm_recovery.img is the one we want to flash. So copy cwm_recovery.img into C:\ADB if you installed the adb drivers in step 2 or the cwm recovery to where ever your sdk tools are. RENAME cwm_recovery.img to just recovery.img, if you're lazy just select rename and delete cwm_. So it should be sitting in C:\ADB\Recovery.img along with fastboot and adb that you copied.
6. So after moving the new cwm_recovery.img that you renamed to recovery.img into your c:\adb folder you're almost done, type fastboot flash recovery recovery.img and after a couple of seconds Fastboot will flash the image and give you a success/failure notification. If successful, you're all set. To check out the new recovery image you have to reboot by typing fastboot reboot or just holding the power button down. Now hold VOL + and power to reboot to the options screen with Recovery, Fastboot, Normal. VOL + until you highlight Recovery and then press VOL -. You should boot into your new CWM recovery. I have included SuperSu.Zip, BusyBox.Zip, and Xposed Framework.Zip. I flashed all of these but not at the same time. I did SuperSu first and rebooted to see if it would boot and it did. SuperSu rooted the phone enough to where I installed busybox.apk but you can restart and flash busybox.zip. Now with Xposed after I flashed it, it took a minute to boot and it started optimizing android apps, it restarted 4 times or so before completing optimization so don't freak out, it will optimize them all and then boot. You should now have a fully rooted Cubot x15 complete with xposed framework.
If you have any questions or if I wasn't clear enough on a certain part please feel free to ask and I'll try my best to help. I'll even reflash my phone if you get stuck and need help, we'll figure it out. Any ways, I hope this helps you guys and it has been working stable for me so far.
Hello, thank you for your detailled instructions, but i can not open the dropbox link. so i could not get the cwm_recovery.img. Please shre it once more. Thanks
Chris
I need to come up with the best way to control recovery for the FireTV Stick. Right now, I'm leaning towards requiring USB ADB and having people use the mouse emulator. And then the bootmenu would not auto boot and you would need to manually select what to boot every time. Unless someone else has any better ideas?
rbox said:
I need to come up with the best way to control recovery for the FireTV Stick. Right now, I'm leaning towards requiring USB ADB and having people use the mouse emulator. And then the bootmenu would not auto boot and you would need to manually select what to boot every time. Unless someone else has any better ideas?
Click to expand...
Click to collapse
Would you not be able to make it boot normally like it auto loads on the aftv2 but instead of saying select left to boot normal or right for recovery you could say you have 6 seconds to use a certain adb command to enter recovery? (But not in those words HAHA) maybe auto display the ip address of the stick on-screen at the same time at the top of the screen?) I don't know if this is possible or not but just helping with sum ideas? Good luck mate
deanr1977 said:
Would you not be able to make it boot normally like it auto loads on the aftv2 but instead of saying select left to boot normal or right for recovery you could say you have 6 seconds to use a certain adb command to enter recovery? (But not in those words HAHA) maybe auto display the ip address of the stick on-screen at the same time at the top of the screen?) I don't know if this is possible or not but just helping with sum ideas? Good luck mate
Click to expand...
Click to collapse
I guess I could autoboot after some long delay, I don't think 6 seconds is enough, something like 10 or 15 would probably work. It would have to be USB ADB, and not network ADB, because getting wifi to work is a little tricky. I looked into it when I was working on the FireTV2 stuff, and wound up shelving the idea.
So I found some information for setting up an ad-hoc wifi network, so I'll look into if that can be used for easier wifi...
rbox said:
I guess I could autoboot after some long delay, I don't think 6 seconds is enough, something like 10 or 15 would probably work. It would have to be USB ADB, and not network ADB, because getting wifi to work is a little tricky. I looked into it when I was working on the FireTV2 stuff, and wound up shelving the idea.
Click to expand...
Click to collapse
Sounds ok though, for a working recovery I'm sure most users wouldnt mind waiting a few more seconds so if something goes wrong It can be undone/saved via a backup
---------- Post added at 01:36 AM ---------- Previous post was at 01:31 AM ----------
rbox said:
So I found some information for setting up an ad-hoc wifi network, so I'll look into if that can be used for easier wifi...
Click to expand...
Click to collapse
You know best mate
Is there any way to see if it got stuck or didn't boot last time, and then boot to recovery once after that? like a file that gets touched early in boot and then deleted later? not sure if that really would make sense, but an auto recovery on failed boot would be pretty awesome. maybe ANY adb input on boot at all, counts as boot recovery so it can be faster? 1,
enter or something?
Any way to just detect if a pc is connected via adb and if so, then boot recovery?
Not sure if these will be useful, but wanted to share the ideas that came to my mind. I definitely would like it to standard boot to OS if possible though.
edit: actually if a-a cable was used on original fire tv didn't it auto go to fastboot?
ImCoKeMaN said:
Is there any way to see if it got stuck or didn't boot last time, and then boot to recovery once after that? like a file that gets touched early in boot and then deleted later? not sure if that really would make sense, but an auto recovery on failed boot would be pretty awesome. maybe ANY adb input on boot at all, counts as boot recovery so it can be faster? 1,
enter or something?
Any way to just detect if a pc is connected via adb and if so, then boot recovery?
Not sure if these will be useful, but wanted to share the ideas that came to my mind. I definitely would like it to standard boot to OS if possible though.
edit: actually if a-a cable was used on original fire tv didn't it auto go to fastboot?
Click to expand...
Click to collapse
So I can't figure out what happened the previous boot. Would need to modify the kernel for that. So I can detect if you're plugged in to the wall versus plugged in to a computer. But I think some people plug theirs into the tv usb port, and it would probably detect that the same as the computer. So maybe if it's wall, always boot straight, and if it's not plugged in to the wall, it's either plugged in to a tv or a computer, then it will show the bootmenu. You'll have I don't know, 10 or 20 seconds to adb shell in and run a command that will boot to recovery, otherwise it'll boot normally.
I was playing around with adhoc wifi, and I coudln't seem to get anything to work. Once I get recovery starting I may play around with it some more. The good news is I'm like 95% done for FireTV1... I think I figured out all the way I can possibly brick the stick, so I can avoid doing it. Haha. That was one of the reasons I wanted to get the FireTV1 working first. Because FireTV1 and FireTV2 I have ways to recover, the stick if anything goes wrong it's pretty much a lost cause.
Unfortunately, I'm not going to be able to work on much in a few days, for a while, so it'll probably be 2 weeks before I can release something for FireTV1 and really get stuff going for the Stick.
If I remember correctly one or more android devices I have seen would auto boot recovery if device failed to boot a certain number of times. A delay at boot could be as long as you wanted since its not like people reboot the device often. Another though is if the stick can detect the difference between a reboot and a power-on, maybe the delay could be different between them. If I wanted to reboot to recovery there are apps that can do that, so delay for a reboot could be shorter than one for power-on.
highspeedfelon said:
If I remember correctly one or more android devices I have seen would auto boot recovery if device failed to boot a certain number of times. A delay at boot could be as long as you wanted since its not like people reboot the device often. Another though is if the stick can detect the difference between a reboot and a power-on, maybe the delay could be different between them. If I wanted to reboot to recovery there are apps that can do that, so delay for a reboot could be shorter than one for power-on.
Click to expand...
Click to collapse
Thanks. I'll play around with some of these ideas too.
The PC with dual operating systems come to mind. Where 1 OS is set as default and you have 30 seconds (default time, but adjustable) to choose the 2nd OS. If no choice is made it boots to the default.
2WhlWzrd said:
The PC with dual operating systems come to mind. Where 1 OS is set as default and you have 30 seconds (default time, but adjustable) to choose the 2nd OS. If no choice is made it boots to the default.
Click to expand...
Click to collapse
That's how it works, the problem is how to make the selection. On FireTV1 and 2 it's with a keyboard. But you can't do that for the stick.
Use the power cycle as the trigger. The bootloader should have a time window (6 seconds) where a file (/cache/boot_recovery) is written to flash and removed after the time window has closed. If someone power cycles the device during this window, the file remains and can be checked during start up and evaluated.
For example.
0s Booting up.
0.1s checking file which indicates recovery in (/cache/boot_recovery) -> none found
1s Show begin of recovery time window -> touch /cache/boot_recovery -> countdown 6 seconds
2s user power cycle
0s Booting up.
0.1s checking file which indicates recovery in (/cache/boot_recovery) -> found
0.2s booting recovery
0s Booting up.
0.1s checking file which indicates recovery in (/cache/boot_recovery) -> none found
1s Show begin of recovery time window -> touch /cache/boot_recovery -> countdown 6 seconds
7s rm /cache/boot_recovery
7.2 booting normal image
malfino said:
Use the power cycle as the trigger. The bootloader should have a time window (6 seconds) where a file (/cache/boot_recovery) is written to flash and removed after the time window has closed. If someone power cycles the device during this window, the file remains and can be checked during start up and evaluated.
For example.
0s Booting up.
0.1s checking file which indicates recovery in (/cache/boot_recovery) -> none found
1s Show begin of recovery time window -> touch /cache/boot_recovery -> countdown 6 seconds
2s user power cycle
0s Booting up.
0.1s checking file which indicates recovery in (/cache/boot_recovery) -> found
0.2s booting recovery
0s Booting up.
0.1s checking file which indicates recovery in (/cache/boot_recovery) -> none found
1s Show begin of recovery time window -> touch /cache/boot_recovery -> countdown 6 seconds
7s rm /cache/boot_recovery
7.2 booting normal image
Click to expand...
Click to collapse
Interesting... very brute forcy, but it could work.
...in Addition, one could think of a small little app called reboot to recovery, that does nothing more than writing that little file to cache and reboot?
Edit: and thank you so much rbox for your efforts! Im on aftv1 and completely rely on your magic thanks mate!
dafunkydan said:
...in Addition, one could think of a small little app called reboot to recovery, that does nothing more than writing that little file to cache and reboot?
Edit: and thank you so much rbox for your efforts! Im on aftv1 and completely rely on your magic thanks mate!
Click to expand...
Click to collapse
That would be a great idea, maybe put the apk as a systems app so it can't be deleted by mistake would also be a good move
Sent from my SM-G900F using Tapatalk
OK. So time for some good news. I figured out how to get wifi going on the FireTV2. So using the same method, I'm pretty sure I'll be able to get it going on the Fire Stick. If it all works out, you won't need USB to control it. In other news, I think I've figured out how the wifi remote works, and I think I may be able to make it work in recovery too. I won't hold up the FireTV 1 recovery for it, so I'll release that as is without wifi and without the remote working, and then as I'm working on recovery for the Stick, I'll get wifi and remote working for everything. I had some issues with the FireTV1, so I don't know if I'll be able to get wifi working for it.
Hmm will the new WiFi remote be a requirement? I have the original with the bt remote. I did like that timing method as an option though as I plan to have stick to travel and not have otg most of the time so slightly faster default boot would be nice.
ImCoKeMaN said:
Hmm will the new WiFi remote be a requirement? I have the original with the bt remote. I did like that timing method as an option though as I plan to have stick to travel and not have otg most of the time so slightly faster default boot would be nice.
Click to expand...
Click to collapse
No. There will be a few options.
ImCoKeMaN said:
Hmm will the new WiFi remote be a requirement? I have the original with the bt remote. I did like that timing method as an option though as I plan to have stick to travel and not have otg most of the time so slightly faster default boot would be nice.
Click to expand...
Click to collapse
I think by wifi remote he means the app for android not another device. If you havent tried the app its pretty handy.
highspeedfelon said:
I think by wifi remote he means the app for android not another device. If you havent tried the app its pretty handy.
Click to expand...
Click to collapse
No, I mean the physical "Voice Remote" that uses Wifi Direct. I think the android app probably uses a complicated Amazon protocol that requires more than I can throw at it in recovery.
Note this is NOT the Blu R1 HD that Amazon sold with advertising built in; it is a separate more expensive model named BLU R1 PLUS. I have searched online for several weeks and not a peek how to Root BLU R1 Plus except the standard promises of paid root services and of course Kingroot. I've used Kingroot before on other phones in desperation but it seems you never get all of their app off your phone even if they are able to root it.
Has anyone any idea how to root this phone? Thank you!
If you have rooted your BLU R1 PLUS (not the Amazon Prime model) if you would share how, I will be more than grateful. Thank you.
Seriously? Still not a single method to root this device?
I think it's a great fone (with a few issues like multi-touch), but still... Wanted to mess with some root tweaks since several months ago.
Any news on this thread?
I have the same problem, i had it since a year ago i dont get how there is not a single root method yet.
I don't know either. The boot loader is locked on this one. I believe all the effort went into cracking the Amazon commercial one. I am guessing there are only a couple of people who can crack them and they either stay busy with more exciting models (the cheapest ones are not always the most popular for some reason, it's the opposite with me). Yes I made the mistake of purchasing the BLU R1 Plus without researching that all the love was being spent on the other models, otherwise this appears to be a really nice phone. I've had it for nearly 6 months and it's still in the box because I am using my old cracked face BLU until I hear how to root this one. I don't use them unless I can root and add secure Xposed environment. Too much, too exposed to the laughable "free" world of apps. I like the BLU phones. This one even has an extra long battery life and doesn't require a bank loan to purchase as most of the popular ones do
Also I tried Kingroot on this one in desperation .... massive list of failures and not sure what condition it left the phone in.
Root TWRP Blu R1 Plus
Unlock Bootloader & Root
BLU R1 Plus
Yes it has been done
Thanks to Antonio Lopes for his help with this and porting TWRP
Thanks to RootJunky for his FRP Unlock img
Thanks to Larry Miller for additional device testing
This method uses adb and fastboot commands and has only been tested on v13
It will wipe your device during install
ADB and Fastboot Minimal is included in zip file
Before any actions: copy all that you need from SDcard internal to PC!
If you want backup calls, messages, contacts (different by goggle contacts or if you can record all the contacts in your google contacts account directly through the contacts application).
For backup, use any application from google play!
Save in your PC! After all the processes you can restore them using the same application that you used.
- Instructions to PROCESS:
1. On phone
Enable Developer Options
Enable USB Debugging too
2. On PC search the folder of adb
fastboot minimal C drive
Unzip TWRPRootR1Plus.zip and Place unlock.img , recoveryTWRP.img and SR3-SuperSU-v2.79SR3-20170114223742.zip in adb folder
Start adb
adb devices ( Ensure connection)
adb reboot bootloader
fastboot flash frp unlock.img
fastboot oem unlock
( Confirm with volume up select )
fastboot flash recovery recoveryTWRP.img
Fastboot will show image flashed but due to BLUs locking of device fastboot reboot will not function
So ….
Unplug device , Hold power off until device turns off
Hold Volume up and Plug device back into PC ,
Continue to hold volume up until TWRP boots fully
Select Wipe , Select Format Data ( don’t worry if any errors show )
Reboot recovery
Select Mount , Select Mount USB Storage
Open Device on PC , Move SR3-SuperSU zip to device external_sd
Unmount
Select Install
Select external_sd
Select SU zip and install
Reboot System
Phone May reboot several time do not interrupt boot
https://www.mediafire.com/download/hjmjpgepfbnjy7h