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,
After spending many time trying to root my storex tab 901 I bought in france (Already installed on 4.1.1 with google play), Iwas finnaly able to root it using adb and command line.
to do so:
- Download attached file
- Download from google SDK usb_adb_driver
- Go to your device parameters-> USB -> enable debbuging mode
- create a c:\root folder on your windows XP computer then Extract the zip file attached into it.
- Plugin your device to the computer, when prompted for driver, use google sdk USB_ADB_Driver
- When done, open a windows terminal command line
- type: c:
- type: cd \
- type: cd root
- type: cd rootkit
- type: go.cmd
If everything goes well, your tablet should reboot. you can try installing the free app from google store called "Root checker" to confirm your device is properly rooted.
Also, if you lost the original rom and live suite, here is the link to download the latest build from storex web site:
(I will post the link later when I find it)
JB 4.2.2
CAUTION: USE THIS ROM AS YOUR OWN RISK.......Be sure you have the official rom in case it is not working for you. It appears that even though you have the same tablet Reference, depending on when you buy it, hardware might be a bit different and most likely you will take the risk of having a unusable Touch screen or wifi...
I found out you can fully use your Ezee Tab 901 4.2.2
you can install rom from Manta MID 13.
You will be able to install the rom using Livesuite.
Gain:
- Android 4.2.2
- Root Access out of the box
- Play store installed.
Everything will be working
For the link type in google:
MID13 Android 4.2.2 Jelly Bean - Manta Multimedia Info
select google link called: manta.info.pl
select the link catshare or 4shared.
Start live suite 1.7, select the download img file, do a format when prompted. You done.
When the tablet restart, go to the parameter icon, and change language to French or english
Procedure on the Ezee tab 901 with livesuit:
- completly turn off the tablet, unplug cable
- start livesuite and select the downloaded image file
- keep the VOL- button pressed and plug the usb cable
- without releasing the VOL- button press the Power button 6 times.
- You should hear windows sound saying a USB device has been plugged
- if windows request it, install the driver from Livesuitefolder\usbdriver
- Livesuite should automatically start the flashing process.
- when prompted, "Format device" press YEs.
- When it s 100% you tablet should reboot.
Done.
Note: I did not invent anything, thanks to the good work of MANTA team members. I just found out this rom works on my tablet out of the box.
Hi,
Thanks for sharing these tips. I'm gonna try to update to 4.2.2, hoping this is going to fix some problems with this tablet.
I've been looking a lot for information about how to update ezee tab 901, so you did definitely a great work !
edit : iflash went well, but touch screen is not responding anymore. Any idea of how to solve it ?
Thanks.
samus64 said:
Hi,
Thanks for sharing these tips. I'm gonna try to update to 4.2.2, hoping this is going to fix some problems with this tablet.
I've been looking a lot for information about how to update ezee tab 901, so you did definitely a great work !
edit : iflash went well, but touch screen is not responding anymore. Any idea of how to solve it ?
Thanks.
Click to expand...
Click to collapse
Hi,
did you try going into recovery mode and factory reset? (shutdown tabel completely and keep press on volume+key then press power button)
in the menu, using vol+/- scroll down to wipe factory reset and validate by pressing the power key.
Let me know how it goes.
btw, are you sure your tablet is a Ezee tab 901 and not 971?
Cheers
Hi,
Yes I've got 901 and not 971 (written on the back of the device). I tried factory reset , but still the same problem. However, I flashed again with the original rom, and then touch screen went functional again but the wifi switch is kinda "broken" : it's impossible to turn on wifi from the Settings menu.
I returned the tablet where I bought it, seems there's a sort of material problem with it :/
samus64 said:
Hi,
Yes I've got 901 and not 971 (written on the back of the device). I tried factory reset , but still the same problem. However, I flashed again with the original rom, and then touch screen went functional again but the wifi switch is kinda "broken" : it's impossible to turn on wifi from the Settings menu.
I returned the tablet where I bought it, seems there's a sort of material problem with it :/
Click to expand...
Click to collapse
Im sorry to hear that, i dont think something is broken, i had the same issue with a memup tablet, even though it was a same reference, some model had different hardware, sonlike you after testing multiple rom i had only touch s creen and no wifi ( wifi switch went back to off when i tried to turn it on) or on other rom, i had working wifi but no touch screen.
I hope they will replace your device...
Cheers
pierrottls31 said:
Im sorry to hear that, i dont think something is broken, i had the same issue with a memup tablet, even though it was a same reference, some model had different hardware, sonlike you after testing multiple rom i had only touch s creen and no wifi ( wifi switch went back to off when i tried to turn it on) or on other rom, i had working wifi but no touch screen.
I hope they will replace your device...
Cheers
Click to expand...
Click to collapse
Yep the wifi switch is exactly what i've got on this storex. Thanks for your help anyway. Ho and by the way, I properly rooted it with you first tuto
Cheers.
Fast custom ROM 4.2.2 by TOxico for Ezee tab 901
Guys,
I manage to find a very fast and usable rom for our tablet: (THanks to Toxico.) this rom will change your life.
All information and download are in the thread here:
http://forum.xda-developers.com/show...php?p=42274265
It should basically work on any A13 device with livesuit (tested on my Ezee tab 901 and on my 704CET mem up)
This rom comes with no TS driver, but there is all explanation and download to install the needed driver.
note: you might loose the camera though. I encourage you to read the full thread before going further and flash your tablet.
If you want to know the driver used on your tablet, run a adb shell and type lsmod (You will have a list of loaded/used driver.)
Dont be scared, everything is written in the toxico's thread
My only advice, if you dont know how to use adb, do not try it, this is not that easy.
I hope this will help.
Best regards.
As usual do it at your own risk and even more: make sure you have the original rom... just in case
Tutorial for 971.
Hi there,
Does anyone know a tutorial like this one but for the 971??
My brother-in-law wasn't using is so I'm thinking in tweaking it to see how it gets.
MaedaKeiji said:
Hi there,
Does anyone know a tutorial like this one but for the 971??
My brother-in-law wasn't using is so I'm thinking in tweaking it to see how it gets.
Click to expand...
Click to collapse
Hi, sorry i cant help you, it looks like the 971 is using a10 cpu, sôit can be different.
If you know what you are doing, u can try to backup your original firmware and test the solution i have provided from toxico in py post above. But there is no warranty it s going to work.
Any case, donnot forget google is your friend
Good luck
Unfornetly it seems google doens't like this tablet...
I'll see what I can do with some backups and all.
Thanks anyway!
hi all can someone please help after ouya send out new firmware 2 weeks ago it messed up my box big time cant even do anything with it
1 ouya is not rooted
2 ouya was working 100% before new firmware
3 tried the usb keyboard reset trick (did not work) all I am getting is what is in video ???
thanks
bigyellowfish said:
hi all can someone please help after ouya send out new firmware 2 weeks ago it messed up my box big time cant even do anything with it
1 ouya is not rooted
2 ouya was working 100% before new firmware
3 tried the usb keyboard reset trick (did not work) all I am getting is what is in video ???
thanks
Click to expand...
Click to collapse
anyone please :crying:
I tried watching video but could not. Does your system boot
mcord11758 said:
I tried watching video but could not. Does your system boot
Click to expand...
Click to collapse
thanks for your time mcord
sorry don't know what's happing there it you can look at this line and post number 19 is all I can get on my ouya , have nothing but problems after last update
http://ouyaforum.com/showthread.php?14831-cant-get-to-ouya-store/page2
4366
bigyellowfish said:
thanks for your time mcord
sorry don't know what's happing there it you can look at this line and post number 19 is all I can get on my ouya , have nothing but problems after last update
http://ouyaforum.com/showthread.php?14831-cant-get-to-ouya-store/page2
Click to expand...
Click to collapse
also can anyone please tell me what is put in box at point 1.23 of this video ???
thanks
https://www.youtube.com/watch?v=-03E5mMQtO4
bigyellowfish said:
also can anyone please tell me what is put in box at point 1.23 of this video ???
thanks chamber
https://www.youtube.com/watch?v=-03E5mMQtO4
Click to expand...
Click to collapse
You do not hands to do that step if you do not want to. It makes life a little easier but is not necessary
Say you save platform tools on your c drive
You can go to the folder then hold shift and right click and select open command
Or you can just go to start and in search enter cmd then select it to open command window. Once open you can change directories. On my pc I named platform tools adb instead. So I type in command
cd /adb
Then hit enter. You should now be in the correct directory
Make sure Firmware zip is saved in the same folder. Skip the part in the video where he cd desktop. Just type in the adb sideload command.
anyone please help with Port Forwarding on a DD-WRT for ouya ??? port from ?? and port to ???
thanks
After 3 months of searching, I'm presenting you the method to Root your ASUS Fonepad 7 FE375CG (FE375CXG)
Introduction:
Originally this Rooting method appeared on 4pda, a Russian android forum meant for Russian community.
I translated the content of the Rooting in English below.
I hope the people, who have long waited for a working Lolipop Root, will find this guide useful.
Disclaimer:
* Warranty is void.
* I don’t guarantee that this will work.
* It maybe cause bad effects to your tablet.
* You are responsible for any damages or other issues that may arise directly or indirectly because of this.
* Very important: All your data and programs will be lost!
Before starting:
This root is specifically for WW_fonepad-12.14.3.18 (that's World wide version - lolipop).
This root will work both for FE375CG and FE375CXG.
To this date, 12-March-2016, WW_fonepad-12.14.3.18 is the latest update for this tablet.
Using this method will require to download 4 objects, in total of 900 MB.
Using this method will require a PC and a SDcard.
As for SDcards, I recommend Class 10 SDcard for android.
Step1: Pre-rooting - Check your software model.
1. Make sure that you are fully updated to WW_fonepad-12.14.3.18 (Lolipop) via OTA update.
2. You can check your firmware version here. ::: Settings --> About --> Software information --> Build number
Step2: Preparing firmware
1. Go ahead and download firmware ==> UL-K019-WW-12.14.3.18-user.zip (Lolipop) (800mb) ::: (Look at this picture)
2. Rename the zip file to MOFD_SDUPDATE.zip
3. Place MOFD_SDUPDATE.zip in your SDcard. (Don't put it inside another folder. ) (Look at this picture)
Step3: Preparing USB connection
1. Download USB-drivers for ASUS connectivity ===> Download ASUS_Android_USB_drivers_for_Windows.zip, then unpack it, then install Install_Driver.bat
2. Download USB-drivers for ASUS connectivity ==> Download and install IntelDnXUSBDriverSetup.zip.
Step4: Rooting
1. Turn off your Asus fonepad 7 FE375CG (FE375CXG)
2. At the same time, Press and hold Vol+, Vol- and Power for 4 seconds. ::: Screen on your Fonepad will remain turned off
3. Connect Fonepad to computer
Initializing rooting/using downgrade.cmd:
4. Download rooting tool ===> Download Downgrade_K019_NEW.zip, unpack it and start Downgrade.cmd. ::: Blue window will appear on your monitor and start working
5. Wait till you see logo Intel appear on your tablet. Disconnect from PC then turn off your tablet by holding power-button.
6. On tablet, again press and hold Vol+, Vol- and Power for 4 seconds.
7. Connect Fonepad to computer
8. On computer, hit Enter. ::: Rooting will continue
9. Later, you'll get a notice "ERASE USER DATA (FACTORY RESET)?". When you see that you should Only press ENTER.
10. Wait at least 10 mins for the rooting process to finish. When everything is done, the blue window (Downgrade.cmd) will close by itself.
Finalizing rooting/using DROIDBOOT:
11. Once Downgrade.cmd closes, your tablet will be in DROIDBOOT screen.
12. On tablet, Insert your SDcard into Fonepad. (MAKE SURE THAT YOUR HAVE PLACED MOFD_SDUPDATE.zip INSIDE YOUR SDCARD (Like in Step2).
13. With Vol+ or Vol- navigate to “Recovery” then click Power to select ::: Your tablet will proceed to root. Wait 5~10 minutes. When everything is done, your tablet will be turned-on and ready.
Congratulations. You've done it!
14. Go ahead and update SuperSu in Play Store.
It worked for me so it should work for you.
Thank yous:
Thank you 4pda for providing this method of rooting, source.
I copy pasted disclaimer from this guy's post, someone else's thread, as this sums everything well.
To Suzukube, for providing feedback to this guide.
Cheers,
Mello
Thank you I bought one yesterday, I'm really lucky ! I can't found the Downgrade_K019_NEW.rar file ? I try this one but no downgrade.cmd inside https://yadi.sk/d/EjGOWsFuicPJE
suzukube said:
Thank you I bought one yesterday, I'm really lucky ! I can't found the Downgrade_K019_NEW.rar file ? I try this one but no downgrade.cmd inside https://yadi.sk/d/EjGOWsFuicPJE
Click to expand...
Click to collapse
Download link has been applied. You can find it in Step4. :good:
Thank you ! I'm trying again !
---------- Post added at 06:23 PM ---------- Previous post was at 05:28 PM ----------
Hello ! I successfully rooted my phone, your tuto is perfect
Just : 5. Wait till you see logo Asus/Intel appear on your tablet. Disconnect from PC then turn off your tablet by holding power-button.
Click to expand...
Click to collapse
>>> Only an Intel logo appeared for me. I waiting a little longer expecting seeing another Asus/Intel logo But it was fine ^^ ! And it's easy to do, we have almost nothing to do ! I rooted because 8gb of memory is not enough, so I want to incorporate Sys App Update in the System partition
Oh Also, after step 13, your tablet will take a lot of time to boot, like 5 minutes ^^ !
To save your device, there is an amazing Asus application. It is called "Sauvegarde" in french. YOu can use it to restore your apps settings
suzukube said:
Thank you ! I'm trying again !
---------- Post added at 06:23 PM ---------- Previous post was at 05:28 PM ----------
Hello ! I successfully rooted my phone, your tuto is perfect
>>> Only an Intel logo appeared for me. I waiting a little longer expecting seeing another Asus/Intel logo But it was fine ^^ ! And it's easy to do, we have almost nothing to do ! I rooted because 8gb of memory is not enough, so I want to incorporate Sys App Update in the System partition
Oh Also, after step 13, your tablet will take a lot of time to boot, like 5 minutes ^^ !
To save your device, there is an amazing Asus application. It is called "Sauvegarde" in french. YOu can use it to restore your apps settings
Click to expand...
Click to collapse
Haha, Keep your smile up!
I'm always happy to share a working solution with good people like you!
I will incorporate your feedback into the guide, thanks for your feedback!
Perfect I linked your tuto on my (frecnh) reviews of that Phablet ^^ ! Rooted, it's just perfect ! You can do so much things with it !
Thank you
it worked with my device fe375cg
Hi , is there any way not losing user data ?
m.tarhsaz said:
Hi , is there any way not losing user data ?
Click to expand...
Click to collapse
Hi Tarhsaz,
In short, there isn't
So for example, you should redownload your calculator........ O_O
Ahaha I'm kidding xD
But really, you should redownload whatever you want to have after Rooting.
And backup your important data on computer or somewhere else, before rooting.
i have message intel soc device detection failed
i need help
I followed all the instructions, and this was the result, I need help to get my phablet
finding update package...
E:failed to mount /sdcard (invalid argument)
E:Can´t mount /sdcard/MOFD_SDUPDATE.zip
SD Instalacion aborted.
E:Installation failed with status 1
Thanks
Carlbornoz said:
i need help
I followed all the instructions, and this was the result, I need help to get my phablet
finding update package...
E:failed to mount /sdcard (invalid argument)
E:Can´t mount /sdcard/MOFD_SDUPDATE.zip
SD Instalacion aborted.
E:Installation failed with status 1
Thanks
Click to expand...
Click to collapse
Did you stop at Step 13?
Did you make sure that you have put MOFD_SDUPDATE.zip in SD card before step 13?
Remember to place MOFD_SDUPDATE.zip in SD cards but not inside a folder
mellomilky said:
Did you stop at Step 13?
Did you make sure that you have put MOFD_SDUPDATE.zip in SD card before step 13?
Remember to place MOFD_SDUPDATE.zip in SD cards but not inside a folder
Click to expand...
Click to collapse
As it is in the instructions at the root of the sd card
Carlbornoz said:
As it is in the instructions at the root of the sd card
Click to expand...
Click to collapse
Try with a new sd card, it will work
hi, i need help. my fe375cxg got rooted according to step 10 without much problem. then i went to step 11 & inserted SD card keeping the file MOFD_SDUPDATE.zip in root folder but recovery at step 13 failed to find the file, so i mistakenly rebooted. now it does not go to recovery state. if i push vol up & power switch at the same time it vibrates & shows "ASUS IN SEARCH OF INCREDIBLE powered by android" but does not go to recovery. i assume if i can go to recovery then i can flash MOFD_SDUPDATE.zip file. can anybody suggest how to go to recovery OR any other idea how to proceed. Thanks a lot in advance for your feedback.
Edit: At last by pushing vol up & power switch at the same time for a short time i was able to go to recovery mode. However, it looks like the file name should be MOFD_SDUPDATE (not MOFD_SDUPDATE.zip, since it is already a zip file) in the root folder of SD card, and it worked smoothly for me.
At the same time, Press and hold Vol+, Vol- and Power for 4 seconds.
Doesnt work with my device Asus Fonepad FE375CXG-1A006A. Whats that for a mode? Is that recovery mode or bootloader? Should I feel a vibration when pushing these 3 buttons? Does this work with win10x64?
I tried now Recovery mode (like smith74 is suggesting in his edit), but now --> Intel SoC Device Detection Failed in the BlueWindow appears
I also tried it again starting the .cmd as administrator --> !!! ERROR !!! FWR_DnX NOT EXIST, EXIT!
Edit: Ok now I got it. (It works with Win10x64 too, you don't have to use Win7 or sth like that). The trick is that you don't get any haptic feedback from the FE375CXG and you also don't (nearly) see anything on screen of the fonepad. You really have to push all 3 buttons (+) (-) and (Power). You can count to 4 or (better) take a deep look on the fonepad-screen, it flickers! Then release the buttons. After when you plugin your device (and everything is ok) Windows shows a screen, installation of "moorefield" or "adb-drivers.." something like that. Then you can go on with 4) Downgrade.cmd
Great Job .. many thanxx
How to downgrade from Lollipop to kitkat on Asus fonepad fe375cg? please, help!
So I'm facing some problems after upgrading to Lollipop via OTA. The device became very slow, I can hardly use it. Can I use this method to downgrade to KitKat? In other words, Can I use Kitkat firmware instead of the lollipop and continue with the same steps?!
Confirmed work for K019 Asus Fonepad 7 FE375CXG, indonesia,
with latest firmware WW_fonepad-12.14.3.18 official ota.
never tampered with, locked bootloader, not rooted.
i only used this tablet for my porn device.
Thank you op,, you have no idea how i bricked 2 different asus devices with different methods,,, and this is the only method that works....
As for problems, i have a few:
1. Step 4-4, like zardoz77 said,, there's no feedback whether i successfully pressed the vol+,- and power button,,, for me,, there's no flickering screen either,,, but what works for me is,, you have to press that 3 button for EXACTLY 4 SECONDS, and then release it,,, more or less than 4 seconds,, then it's gonna be "intel soc detection failed".
2. Step 4-8, when i see intel logo on tablet, then disconnect -> press3 button -> reconnect -> hit enter,,, the blue window unable to recognize the tablet!! and there are dozens of "attempt to reconnect" text,,, then i yanked the usb cable,, and it continues to root,, turns out the problems is my usb cable,, just one of the few solutions of that particular step.
3. Step 4-13, for me, the first time boot after recovery is 15-20 minutes,, at first, i thought it failed,, but then gave it a time,, it will show you the welcome screen.
Thanks a lot OP,,
Now, time to strap those sweet dualshock3 controllers.
tyring to delete my posting ... but don't know how
Most old methods of changing the region on the samsung watches don't work anymore. Given their return policy I thought I bought expensive junk.
*#272*719434266344#
Click to expand...
Click to collapse
starts the csc selection but doesn't actually change the region.
TL;DR you need to install the combination firmware and edit two files
INFO: Netodin works fine in linux as well with wine since it works over the wifi
1. Start NetOdin3 click options and disable auto reboot
2. Click AP and select the combination firmware
3. Hold reboot button on the Samsung watch, when the reboot screen shows up press home multiple times to get into the boot menu
4. Jump to the Download (Wireless) and hold the boot button again to get into the Firmware download menu
5. Press the same button to more times to switch the watch to AP mode
6. Connect your wifi to the watch SM-R830-someid
7. In NetOdin3 press Start to flash the combination firmware
8. Click reset and now press CSC button
9. Select the CSC md5 and press start
10. When you reboot the device hold the boot button again until you enter the boot menu again
11. Select recovery and let the device restart
12. Enter settings -> About watch -> Software -> Tap software version until debug mode starts (you may need to restart your watch)
13. Connect watch to wifi
14. sdb connect <watchip>
15. sdb root on
16. sdb shell
17. backup active-customer.info: sdb pull /csa/csc/csc-active-customer.inf
18. backup prodcode.dat: sdb pull /csa/imei/prodcode.dat
19. edit /csa/csc/csc-active-customer.inf and replace csc code (I used vim and the XAR for the US version, https://www.geeksforgeeks.org/vi-editor-unix/ )
20. edit /csa/imei/prodcode.dat and replace last three characters to csc code you want (don't enter the csc selection after this it will reset it to the factory region)
21. reboot the device into recovery (i used /usr/bin/csc-util --reboot customer_change but i'm not sure it's necessary)
22. run netodin again and select AP, BL and CSC to flash stock
23. enjoy samsung pay if you have a US credit card (seems like you no longer need to install samsung pay apks on non samsung phone it's part of the wearables app)
R830 combination firmware
https://www.file-upload.net/download-13751174/combination-R830XXU1ASI2.7z.html
R830 3 file firmware
https://www.file-upload.net/download-13751206/multi-3file-R830XXU1BSI9.7z.html
sha256 checksums:
e719a024540706c07ae956c2a737b43dcaefa2b3335b1118121b6ca8168089ab AP_R830XXU1BSI9_usr.tar.md5
d0be4fdd7f5abaa6a4520f487b85dec14f94dd9d14a239fde69f5281817f7d99 BL_R830XXU1BSI9_usr.tar.md5
8f28bee9aa56b5c8d2fb8fa7bf16ab5cf0c3bff5fc547e2ada18a90c161f61e5 COMBINATION-FT40_R830XXU1ASI2.tar.md5
efe5e799c95c70aa1de8cced5a544bc471b2b74f61a3babffa72a7e295804225 CSC_OXA_R830OXA1BSI9_usr.tar.md5
Click to expand...
Click to collapse
Thanks to @adfree for the links and purcival for the order of how to flash the combination firmware and stock after
[0] Netodin
[1] how to change region on samsung gear s3
[2] combination firmware for sm-r820 by @adfree
[3] sdb in tizen studio CLI tools section
Hi,
Can l use this method just for updating the firmware of my watch?l'm still on R830XXU1ASHF.. if yes should l follow all these steps??
Thanks
What csc your watch?
tb_ said:
What csc your watch?
Click to expand...
Click to collapse
Thank you for your reply,l bought my watch in UK.
According to the list the csc is BTU-UNITED KINGDOM.
A Beginner
Hi,
First of all I want to thank you guys for the grat work.
I want to say that I am actually a beginner or amature when it comes to what you are doing
The instructions are very clea. But I would really appreciate it if anybody describes what to do with more details, especially the codes of sdb. Just some more details
It would be great if you can upload a video "If possible"
1. What is the worst thing that might happen if I do something wrong? Can the watch be ruind? Can I fix it if it happens?
2. Where can I find the csc of my country "Sweden" I googled it and found like 5 or 6 different csc !! Is there any trusted source?
3. Is it appliable to R820??? the 44mm model? or do I need to do something different in my case??
Thanks in advance
Coming from the other thread to confirm this worked for me, thanks a ton! Didn't think it would be that simple with just editing two text files.. lol
For those who missed it(I did), some steps are missing where one has to repeatedly connect back to AP every time something has to be done in NetOdin.
Also if anyone is confused about the steps, it's pretty much the same process for all samsung watches so just search for it on youtube, it's there.
Out of curiosity, where did you get the firmware from?? @tb_
2avrmillion said:
Coming from the other thread to confirm this worked for me, thanks a ton! Didn't think it would be that simple with just editing two text files.. lol
For those who missed it(I did), some steps are missing where one has to repeatedly connect back to AP every time something has to be done in NetOdin.
Also if anyone is confused about the steps, it's pretty much the same process for all samsung watches so just search for it on youtube, it's there.
Out of curiosity, where did you get the firmware from?? @tb_
Click to expand...
Click to collapse
Hi ,
Thanks for your feedback,are the sdb thing code mandatory?on youtube they only add the 3 or 4 files on odin and just flash it...
Hey guys, firstly thankyou! This worked perfectly and now I'm able to use Samsung pay down in Australia! Only thing that I would add from the perspective of being a complete beginner to Odin, is how to save the files when you edit the CSC (press escape then type ":wq") it took me an extra 20 minutes to figure it out and I thought someone might find it useful
2avrmillion said:
Out of curiosity, where did you get the firmware from?? @tb_
Click to expand...
Click to collapse
Got it from a third party. I was worried that it was counterfeit so before installing it I went through the system files to see if it's really the right model. But I can of course not guarantee that it wasn't modified by a third party. But I kinda assume that samsung won't boot from any random image given that you can't downgrade Samsung and even their tizen to any version you want apparently.
dodo1515 said:
Thank you for your reply,l bought my watch in UK.
According to the list the csc is BTU-UNITED KINGDOM.
Click to expand...
Click to collapse
{tizen} % cat preconfig/BTU/preset/csc-preset.ini
[default]
keyboard_lang="en_GB"
keyboard_preinstalled_lang="1^en_GB#en_US#de_DE#fr_FR#it_IT#pl_PL^en_GB
Click to expand...
Click to collapse
The csc.img has BTU inside. But I can't guarantee you anything when I ran this with my zone set to XTC it was booting fine but I couldn't get my phone to connect / initialize the watch after the factory reset. But not sure if it was the app or because i didn't properly reset or if I maybe shouldn't have reset.
So I can tell you that it will boot without issues but whether it works no idea. Maybe someone else can comment on that.
Highpryority said:
Hey guys, firstly thankyou! This worked perfectly and now I'm able to use Samsung pay down in Australia! Only thing that I would add from the perspective of being a complete beginner to Odin, is how to save the files when you edit the CSC (press escape then type ":wq") it took me an extra 20 minutes to figure it out and I thought someone might find it useful
Click to expand...
Click to collapse
I think you are talking about steps 17 and 18. If so can you please till me a bit more detailed how to do these steps ! I mean Do we edit manually in the sdb?? or how are we editing? Why do we need to save the files after editing? there is nothing about saving files in the steps above!
Sorry if my questions are silly but I am a real beginner here!
tareqsy91 said:
1. What is the worst thing that might happen if I do something wrong? Can the watch be ruind? Can I fix it if it happens?
Click to expand...
Click to collapse
No one will give you guarantees on this because no one wants to blame if something goes wrong. But if you try absolutely under no circumstances interrupt the flashing process and absolutely don't use the wrong model ROM. Also to be safe don't try to flash a firmware that has a lower version than your current one.
tareqsy91 said:
2. Where can I find the csc of my country "Sweden" I googled it and found like 5 or 6 different csc !! Is there any trusted source?
Click to expand...
Click to collapse
csc usually depends on the vendor. So there are a bunch of sweden csc's . But you should be able to find your current csc in /cas/imei/prodcode.dat
a list is on droid views
tareqsy91 said:
3. Is it appliable to R820??? the 44mm model? or do I need to do something different in my case??
Click to expand...
Click to collapse
r820 is the 44mm bluetooth model.
825 and 835 are lte with one version being US and the other being global I believe.
tb_ said:
No one will give you guarantees on this because no one wants to blame if something goes wrong. But if you try absolutely under no circumstances interrupt the flashing process and absolutely don't use the wrong model ROM. Also to be safe don't try to flash a firmware that has a lower version than your current one.
r820 is the 44mm bluetooth model.
825 and 835 are lte with one version being US and the other being global I believe.
Click to expand...
Click to collapse
Lower frimware? I have Tizen version 4.0.0.7
1. Do you know if the availabe combination frimware for R820 is of a lower frimware??
2. Yes My R820 is the 44mm bluetooth. thats correct. I guess I should use R820 which you linked in your original post!
3. Can you please describe more about steps 17-18 I didn't really understand how to edit! It's my first time using this sdb thing
Thanks for your patience everybody answering or even reading my questions
I think I am the most commenting member on this topic.
I have read a lot and almost all the details in each shared link in this thread.
I am trying hard I swear. Lately after downloading the shared files in the links in the original post. I can't start the file "web-cli_Tizen_Studio_3.3_windows-64"
It is just flashing a cmd window and nothing happens after that!
What should I do in this case??
The other file in the link "web-ide_Tizen_Studio_3.3_windows-64" is telling I should have JDK software which I installed but It didn't help anyway!
tareqsy91 said:
I think I am the most commenting member on this topic.
I have read a lot and almost all the details in each shared link in this thread.
I am trying hard I swear. Lately after downloading the shared files in the links in the original post. I can't start the file "web-cli_Tizen_Studio_3.3_windows-64"
It is just flashing a cmd window and nothing happens after that!
What should I do in this case??
The other file in the link "web-ide_Tizen_Studio_3.3_windows-64" is telling I should have JDK software which I installed but It didn't help anyway!
Click to expand...
Click to collapse
Don't use that because I had the same issue in Windows 10. Go to https://forum.xda-developers.com/showpost.php?p=74585286&postcount=330 and download SDBstarterKidv1.zip. Extract it and run ansicon.exe under data/tools folder. It will open a command prompt.
shinzomask said:
Don't use that because I had the same issue in Windows 10. Go to https://forum.xda-developers.com/showpost.php?p=74585286&postcount=330 and download SDBstarterKidv1.zip. Extract it and run ansicon.exe under data/tools folder. It will open a command prompt.
Click to expand...
Click to collapse
Thanks for the advice
I haven't done Netodin steps yet.
I am trying now to just connect the watch to the computer through the wifi network.
I have debugging mode on in the watch but I still can not connect to the watch
It keeps telling me failed to connect
connecting to 192.168.0.16:26101 ...
failed to connect to 192.168.0.16:26101
Is it normal I can't connect before doing the netodin steps??
tareqsy91 said:
Thanks for the advice
I haven't done Netodin steps yet.
I am trying now to just connect the watch to the computer through the wifi network.
I have debugging mode on in the watch but I still can not connect to the watch
It keeps telling me failed to connect
connecting to 192.168.0.16:26101 ...
failed to connect to 192.168.0.16:26101
Is it normal I can't connect before doing the netodin steps??
Click to expand...
Click to collapse
Normally the watch comes up with a prompt to allow your pc to connect to your watch. Maybe you might have to restart your watch. I would try the netodin step first because it might be more straightforward to connect the combination firmware to the computer because I didn't get any prompt on that.
Also maybe check that your virus scanner/firewall isn't blocking access.
shinzomask said:
Normally the watch comes up with a prompt to allow your pc to connect to your watch. Maybe you might have to restart your watch. I would try the netodin step first because it might be more straightforward to connect the combination firmware to the computer because I didn't get any prompt on that.
Also maybe check that your virus scanner/firewall isn't blocking access.
Click to expand...
Click to collapse
I've tried to turn off my antivirus and firewall but still no connection.
The newer versions of sdb 4.1.8 is showing the following:
The version of SDB client (4.1.8) and server (2.2.60) are different.
This may cause version compatibility problems.
It is recommended to use SDB server 4.1.8. *
I've tried to turn off my antivirus and firewall but still no connection.
The newer versions of sdb 4.1.8 is showing the following:
The version of SDB client (4.1.8) and server (2.2.60) are different.
This may cause version compatibility problems.
It is recommended to use SDB server 4.1.8. *
Click to expand...
Click to collapse
1.
sdb.exe once started is Background process...
To close active sdb you can do this:
Code:
sdb kill-server
2.
https://forum.xda-developers.com/showpost.php?p=74585286&postcount=330
Look into this old post...
Try to read:
Code:
Guidelines_on_Connecting_GearS2_device_using_WiFi.pdf
Guidelines_on_Connecting_GearS2_device_using_WiFi_151222.pdf
Ignore Gear S2 text... because this is same shhh... since years...
Mandatory is to find your correct IP.
Hint...
Maybe it helps to try different PCs or Notebooks... sometimes more luck on other device... but only with correct IP in Command...
connecting to 192.168.0.16:26101 ...
failed to connect to 192.168.0.16:26101
Click to expand...
Click to collapse
If these digits are correct...
Command Line looks like this:
Code:
sdb connect 192.168.0.16
Not more not less... NO need to add something behind...
Best Regards
This is driving me crazy guys
Still cannot connect to the watch through wifi yet
I am getting this answer now
* server not running. starting it now on port 26099 *
* server started successfully *
connecting to 192.168.0.16:26101 ...
failed to connect to 192.168.0.16:26101
I am trying on both the older and the newer versions of sdb
Debugging mode is on in my watch
When writing same command again "sdb connect 192.168.0.16" I get weird figures or "error: target offline" in the newest version of sdb
I have even tried to create a private wifi from the computer I use and connect the watch to the same network but it didn't help either.
I am still only trying to connect the watch to the computer through sdb. I haven't done the odin steps yet. I am afraid doing odin steps and not being able to complete the sdb connecty steps !!
I have another question:
Where I live in Sweden. Samsung didn't release a bluetooth version at all. That's why I bought mine from Germany.
If I change my csc to Sweden. Will it work as there is actually no swedish bluetooth SM-R820 !! I mean that mine watch will be probably the only bluetooth r820 with swedish csc !!!! will I get updates as usual? will the watch even work?
@tareqsy91
1.
You have nobody who can help you?
No family... no friends nor neighbar with second/other PC... Notebook?
I am using different PCs with:
Win XP
Win 7
Win 8
Win 8.1
Never tried with sh .tty Win 10...
1.1
Maybe give infos what you use... Windows Version AND 32 bit or 64 bit
2.
Sweden or Germany...
No matter...
F. device work with byteexact Values... Sales Code aka CSC...
2.
Their are few other methods to READ EXACT infos from device... instead talking about blabla Sweden or Germany...
Look at this post... with screenshots...
App which can read these 2 files from Watch:
https://forum.xda-developers.com/showpost.php?p=80072694&postcount=786
Code:
com.somyac.gear.transfer.lite
Best Regards