Related
Hi,
Finally got my galaxy tab to work after 6 hours. Now it is running well.
As it is 4 am here, i will post a guide for Singapore users once i wake up as i have meet with problems during the whole process.
Luckily, all information can be found on this forum but just that you will have to read through 20 plus pages from different topic in order to get the answer.
Super happy with my phone now!
*just another newbie* =)
Sent from my GT-P1000 using XDA App
Sorry to steal your thread. Singaporean tab user here as well. I think we should constantly update this thread for singapore users. I was running dxjm4 up til this morning when i decided to flash to roto-jme. spent the last few days reading the thread and considering whether to upgrade or not because of the lack of information for singapore users. so i decided to take the plunge and just go for the upgrade no risk no gain. my tab got stucked at the samsung logo after it auto rebooted but it was fine after i manually rebooted it
what i did was to upgrade from jm4 instead full flashing my tab. it turned out fine so far but there's one thing that puzzles me. the apps that roto mentioned were removed are still in my tab such as daily briefing etc.. do u have this problem as well?
Not Too Sure... I am new to Galaxy Tab or rather Android =P
But i suggest you do a full flash again.
i wasn't ready to even root my device initially as i only gotten my Tab on Saturday 7th Jan 2011.
One thing that actually forced me to root and flash the rom is the stock version whether bug or not i just couldn't sync with my company exchange 2010, which is critical for me.
Nonetheless, i haven't tried the jme v4 as yet (I suppose) as i did not know how to get it to work.
All i did was follow:
http://forum.xda-developers.com/showthread.php?t=895827
And all went well, except that Data doesn't work.
Thoughout the whole process i did not use the file name "Roto-JME-Full-v4"
which set me thinking whether did i actually do the right thing.
One thing is most of the stock app was gone, baseband was change to I9000UGJK3, Kernel Version 2.6.32.9 [email protected] #1 and Build number is Froyo.XXJME.
HCgoh said:
Not Too Sure... I am new to Galaxy Tab or rather Android =P
But i suggest you do a full flash again.
i wasn't ready to even root my device initially as i only gotten my Tab on Saturday 7th Jan 2011.
One thing that actually forced me to root and flash the rom is the stock version whether bug or not i just couldn't sync with my company exchange 2010, which is critical for me.
Nonetheless, i haven't tried the jme v4 as yet (I suppose) as i did not know how to get it to work.
All i did was follow:
http://forum.xda-developers.com/showthread.php?t=895827
And all went well, except that Data doesn't work.
Thoughout the whole process i did not use the file name "Roto-JME-Full-v4"
which set me thinking whether did i actually do the right thing.
One thing is most of the stock app was gone, baseband was change to I9000UGJK3, Kernel Version 2.6.32.9 [email protected] #1 and Build number is Froyo.XXJME.
Click to expand...
Click to collapse
i am new to android too and this is my first android device. your baseband is weird? I9000? which firmware did u flash???
Root devices *Important Points
And Yes i woke up...
Anyway i do not gain credit from the guide itself as everything can be found in this forum. If you want to thank people, please thank the people that writes the program and the trial & error people if you find my thread useful. I am just consolidating all the steps that i used to flash my Tab, important things to take note of and etc...
Step by step guide to Rooting:
Please read
http://forum.xda-developers.com/showthread.php?t=812367
*Important points to Note when Rooting"
Process:
1) Connect your galaxy tab with debugging mode disabled and sync with Kies even once - You must be damn sure Kies can connect to your phone
2) Disconnect it and enable debugging mode from Settings>Applications>Development>USB Debugging
3) Connect the tab again to PC and click on home button so that Tab comes out of Kies connection - I found that after USB Debugging is turn off, Kies can still find your phone but it will just appear as Connecting... on the top left hand side of Kies. (I left my Kies on throughout the process)
4) Launch SuperOneClick.exe
5) Click on root and wait for 5-10 Mins - it stated 5 - 10 min but it took like 5 - 10 sec for SuperOneClick to prompt me saying that device is rooted.
And that all for Rooting whole process took me about 5 min Including all the reading. (Simple Great Job by SuperOneClick!)
Now comes the slightly complicated part: Flashing New Roms
Below is the thread that is used
1) http://forum.xda-developers.com/showthread.php?t=894763
2) http://forum.xda-developers.com/showthread.php?t=895827
What i did was:
1) Download OdinV3 1.7 (Provided in the thread 895827)
2) Download Addon-JME-Modem.zip (http://files.deodexed.com/ModADroid-Galaxy-Tablet/Rotohammer/JME/)
3) Download P1_add_hidden.pit (http://files.deodexed.com/ModADroid-Galaxy-Tablet/Rotohammer/JME/)
4) Download Roto-JME-FmtIntSD.zip (http://files.deodexed.com/ModADroid-Galaxy-Tablet/Rotohammer/JME/archive/)
Additional:
I also downloaded (But till now i have not use any of the file below)
1) Roto-JME-FmtIntSD-v2.zip ( http://files.deodexed.com/ModADroid-Galaxy-Tablet/Rotohammer/JME/archive/)
2) Roto-JME-Upgrade-v4.zip ( http://files.deodexed.com/ModADroid-Galaxy-Tablet/Rotohammer/JME/)
Why is it not used, i myself is not too sure. For FmtIntSD alot of people is asking which is it to use as there are 2 different version 1 & 2 (i Suppose).
I have used the Version 1, as the time posted in the FTP link seem to be later than Version 2.
Also as thread http://forum.xda-developers.com/showthread.php?t=895827 shows in the screenshot, under tab CSC: Addon-JME-Hidden.Tar, this file is missing plus confirmation from the thread saying that it will fine without it.
Once downloaded, it is time to get to business =)
Steps i took:
1) Startup Odin
2) Connect Galaxy Tab to Kies make sure Kies is able to connect to the device and is able to Sync with device (Toggle with the USB Debugging option Either On or OFF) *My kies is never turn off from the start Rooting to Flashing* i think in order for Odin to work properly, Kies must be able to detect the device is been plugged in. (Just my Thought)
3) At this point of time Odin will also detect the device been plugged in as show in the screenshot provided in thread 895827. The yellow box will appear stating COM10 or 11 or 12 (DOesn't matter what com Number)..... Left hand bottom of ordin will also show Added!
Checked Make sure and double checked.... Yeah the next part!!!
4) Unplugged my phone from the USB
5) Off my phone
5) On my phone to get to the downloading mode (Hold Power Button and Volume Down Button)
6) Checked my Odin, Bottom left log shows REMOVED!
Hell Ya exactly the same as the sceenshot.....
7) Plugged in my phone with the Downloading screen....
8) Waited.... Waited..... 5 min pass..... Windows 7 is still searching for "Gadget Serial Port" Odin didn't detect the device connected.... don't have to worry Windows 7 will eventually find the driver, just got to give it sometime (Just in case you meet with the same problem like i did, Windows 7 took almost 10 min for the device to be ready)
9) Check Odin, Bottom left hand log.... ADDED!
Almost there.....
10) Plant in all the .Tar file as show in screenshot (Thread 895827)
*Please make sure you unzip the .rar file the logo is similar to winrar icon once you unzip. Can get a little messy, what i did was unzip and delete the original zip file that i downloaded. Remember JME-Hidden.Tar is not needed, just leave it blank*
11) Tick the "Re-partition" in Odin
Now you are all ready to start, double check all the setting and click the "Start" in Odin... =)
12) Pray.... Pray... Pray....
Whole process took me about 5 min, Odin will show you the details as it is flashing, Installing and Bla Bla Bla.... Once it is ready, Odin will prompt you either Successful or Failed...
Phone will automatically restart. Just leave it till you see the main screen comes out.
* I Succeed on my first try, so if you fail i guess you got more reading to do than me, but i am sorry that i am unable to help if you fail at this point*
Now then all good, checked my phone all seem well... did a call to my house number, Working....
Now the complication that i faced: My 3G (data Services) is NOT RUNNING!!!!
Did a search on the forum and found a few threads that is helpful:
1) http://forum.xda-developers.com/showthread.php?t=901021
2) http://forum.xda-developers.com/showthread.php?t=845263&highlight=modem.bin&page=3
3) http://forum.xda-developers.com/showthread.php?t=847273&highlight=modem_bell_i9000
* I Have attached the modem.bin that i use to get my 3G working, but before you download the attachment please do a few check as stated below.Things to check if your 3G (Data Service) is not working:
1) APNs setting
Setting>Wireless and Network>Mobile Networks>Access Point Names
2) Select the Access Point Names and see if there is any setting inside.
3) If it shows "No Setting"
4) Tab on the bottom left hand corner of your galaxy tab, "MENU" button beside the "Home" buttom
5) select "Add APN"
6) Use the information below, key in whatever is there. Those that you don't know just leave it blank. (As long as your are in Singapore i believe you know which telco you are with)
StarHub (Singapore)
APN: shwap or shwapint
Leave user/pass blank.
M1 (Singapore)
APN: sunsurf
user: 65 pass:
user123
swirlyMMS :
MMSC and Proxy server settings MMSC : http://mmsgw:8002/
Proxy : 172.16.14.10:8080
MMS-specific APN Settings
APN: miworld
username:65
password:user123
SingTel (Singapore)
APN: internet
Username: 65IDEAS (or blank)
Password: IDEAS (or blank)
Once Key-in "MENU" button again and safe the setting, now go back to your APNs and check to see if you have selected the setting you key-in (Button on the right hand side will be "GREEN"
Now Wait & Pray that the logo "3G" or "H" appear on the top beside your signal strenght bar.
if no launch your dialer (Press Phone) and Dial *#2263# select "automatic" 1st option. (Select it once and exit by pressing "HOME" or "BACK")
Wait & Pray....
I believe this should get it going as under JME-Modem.zip, the modem should already be in.
__________________ I sincerely hope that you do not have to do the step below________________________________________________
If the 3G or H is still not showing after you tried the above step. Download the modem.bin (Attachment in this thread modem_bell_i9000.zip)
Then follow the step below:
1) Unzip the file
2) startup Odin
3) Browse for the Modem.bin, using Odin "Phone" Tab (File you unzip from the attachment downloaded from here)
4) off your phone and boot it up to the "DOWNLOADING SCREEN"
Checklist:
5) Re-partition is NOT tick
6) Odin detect your device
Hit "Start" and wait for your phone to reboot.
*I succeed with this flashing of modem, if you fail all i can say is good luck*
Once your phone is up, check on the APNs setting again (Key-in the details is there is nothing in the list) Check on *#2263# and set it as automatic.
Then End.....
Conclusion:
I use the exact same step for my phone, and get it going. I hope it helps you.
Again i would want to highlight that none of the above is by me, all information can be found in thread posted by other users. Please give thanks to them as they are the one doing the job, taking risk to try ROMs, Root and etc...
=) i hope my thread helps anyone with the same problem as me...
PS: DO NOT HOLD ME RESPONSIBLE IF THE ABOVE GUIDE DOESN"T WORK FOR YOU.
Hi Kay Kiat,
I Seriously don't know. See the steps i posted, i believe it is because i flash a i9000 modem in that is why my baseband is weird. =p
i believe all i need to do is to re-flash the Jme modem in, and it should be right.
But currently at work no time to try. haha
Best Regards
Hi guys, Singapore GT user here also. Looking forward to try out your guide.
EDIT: Just flashed Roto's JME-Full-v4 with repartition. All works fine. No modem flash required.
HCgoh said:
Hi Kay Kiat,
I Seriously don't know. See the steps i posted, i believe it is because i flash a i9000 modem in that is why my baseband is weird. =p
i believe all i need to do is to re-flash the Jme modem in, and it should be right.
But currently at work no time to try. haha
Best Regards
Click to expand...
Click to collapse
hmmm. my 3g/gprs seems okay.. i went from jj1->jm4 via kies then jm4->rotojme via flash.. my baseband is p1000dxjm2 (i believe this is from jm4 as i did not flash modem when i upgraded to rotojme). hmmm.. did u set your apn correctly?
Sg user here as well
Anyone managed to get chinese input up?
Sent from my GT-P1000 using XDA App
junchen said:
Sg user here as well
Anyone managed to get chinese input up?
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
are you talking about the keyboard?
Hi,
wanted to share my experience from flashing this Rom.
The way I've done it is download the latest full version find in the ftp site (not the archive) directory and using Odin to fladh my tab. I also downloaded all the other files but did not use them.
Overall, this rom is good. It solved my exchange problem but i've lost a few things as well. There's no more chinese input and i'm no longer able to zoom and pinch on dolphin browser. Does anubody has any solutions to these problems?
Thx.
Sent from my GT-P1000 using XDA App
中文鍵盤及手寫
This is what I've been using in a US T-mobile Tab with Roto-JME & it's working fine! Enjoy
junchen said:
Sg user here as well
Anyone managed to get chinese input up?
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
xenomage said:
i'm no longer able to zoom and pinch on dolphin browser.
Click to expand...
Click to collapse
This was solved in another thread, maybe the Roto-JME one itself. Theres a new version from Dolphin with the fix. You'll find it
xenomage said:
The way I've done it is download the latest full version find in the ftp site (not the archive) directory and using Odin to fladh my tab.
Click to expand...
Click to collapse
The Roto-JME-Full-v4 will format the internal sdcard only if it is corrupted. So you can shorten the steps to just flashing that one firmware. The ones in the archive are there just in case we needed to test something.
APN settings
Hi
Did you guys copy down the APN settings and did you manage to get your MMS working? I only have my 3G working. Was trying out the different settings to get MMS working too.
ps: for chinese input, can just install google pinyin. been using it since Im only android. swype does have chinese input but the one on the tab doesnt have it. I was testing the beta using my hero and i can do chinese input using the swype keyboard. i wonder if there is anyway to update the swype version to the latest one released by them.
Chinese input
xpgroup said:
This is what I've been using in a US T-mobile Tab with Roto-JME & it's working fine! Enjoy
Click to expand...
Click to collapse
Hi,
this may sound kinda dumb but after i download and install the attached APK, nothing happens on the keyboard.
How is it supposed to work?
Thanks.
go to settings > locale and text > enable whatever keyboard you want. then rmb to change your input method whenever u wanna use the new keyboard
xenomage said:
Hi,
this may sound kinda dumb but after i download and install the attached APK, nothing happens on the keyboard.
How is it supposed to work?
Thanks.
Click to expand...
Click to collapse
You'll need to goto Setting-Locale and text, check the Penpower Input Method. After that, at any input screen, press & hold - then select the input method.
xpgroup said:
This is what I've been using in a US T-mobile Tab with Roto-JME & it's working fine! Enjoy
Click to expand...
Click to collapse
Thanks for the file, it works fine. Just the right hand side part of the keyboard is emtpy. I wonder if there is anything to adjust the scale.
Thanks.
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!
I need some assistance trying to find a method to root my Dash M (which appears to be extremely rare to find a rooting method for).
I already tried framaroot (tool I used to root my tablet before) and Kingroot and such, but none were able to do it (and all google searches led to videos on rooting a BLU Dash 5.0 or another device from the Dash range, which isn't what I needed).
The Dash M is running Android 5.1 and custom build BLU_D030U_V16_GENERIC 28-01-2016 15:41
If anyone could help it'd be very much appreciated c:
Unlock OEM in developer mode and try it whit Kingroot
AnarchyPhoenix746 said:
I need some assistance trying to find a method to root my Dash M (which appears to be extremely rare to find a rooting method for).
I already tried framaroot (tool I used to root my tablet before) and Kingroot and such, but none were able to do it (and all google searches led to videos on rooting a BLU Dash 5.0 or another device from the Dash range, which isn't what I needed).
The Dash M is running Android 5.1 and custom build BLU_D030U_V16_GENERIC 28-01-2016 15:41
If anyone could help it'd be very much appreciated c:
Click to expand...
Click to collapse
I have a Blu Advance 5.0, from the same exact family. In May, they had an OTA sent out to it to update the security. And little did I know, that meant no more root. Before the OTA to V06, I was on V04, and was able to root with Kingroot in less than a minute, perfectly. After the update, nothing good came of it.
For the past months I've tried hundreds of things to flash custom roms and recoveries (which I figured it out eventually) and then it crashed, due to a "damaged OTA". This meant that it couldn't update because I was rooted.
So here's the solution... If there's any older versions of your model or chipset (AKA Mediatek D030UX, D030U {MT6580}), download that firmware to your computer desktop as a (.zip) file. Then download the SP Flash Tool (Smart phone flash tool) from their website, and plug your phone into your computer via Media Transfer (MTK).
If you already have developer's options enabled, skip this.
- Go into your settings, go all the way down to "About Device", and find where it says "Build Number" (which will most likely have the phone brand in the file name). Tap on that about 8 times until it give a toast notification saying "Developer's Mode Enabled".
After you get that done, go back into your regular setting and now there should be a box above your "About Device" button that says "Developer Options". Tap that, then turn them on (press OK/YES if a prompt pops up) and then select the following options ,if available.
-OEM Unlock
-USB Debugging
Now plug your phone into a computer and install the drivers for your phone (it should do it automatically) and launch the SP Flash Tool that you had downloaded (extract to desktop before you launch, or it will show "error"). Now open the SP Flash tool and click on the "Scatter Loading" button. Navigate to your desktop, and find the firmware folder you downloaded. Click on that, then click on "Firmware", and it should bring up a .TXT file (Scatter file) with the desired firmware version you want. Click on it and press open.
A chart will appear in the space below with all the things the firmware has built in. All of them should be checked. Take out your battery now (from your phone) and plug the phone in without the battery. Wait for the model on the left to name your device, and click on the drop down list above the chart, it should give 3 options. Firmware Upgrade, Download only, and Format All + Download. Press Format All + Download. The bar at the bottom will turn a few colors, depending on what it's doing.
Now you're done! It's flashed. From that version, try to figure out a way of rooting it.
WARNING: Flashing erases all data on device, please backup to an external storage (SD CARD), before attempting this, in case you brick your device.
Sent from my RCT6873W42M using XDA Labs
---------- Post added at 03:04 AM ---------- Previous post was at 02:56 AM ----------
TechTeen17 said:
I have a Blu Advance 5.0, from the same exact family. In May, they had an OTA sent out to it to update the security. And little did I know, that meant no more root. Before the OTA to V06, I was on V04, and was able to root with Kingroot in less than a minute, perfectly. After the update, nothing good came of it.
For the past months I've tried hundreds of things to flash custom roms and recoveries (which I figured it out eventually) and then it crashed, due to a "damaged OTA". This meant that it couldn't update because I was rooted.
So here's the solution... If there's any older versions of your model or chipset (AKA Mediatek D030UX, D030U {MT6580}), download that firmware to your computer desktop as a (.zip) file. Then download the SP Flash Tool (Smart phone flash tool) from their website, and plug your phone into your computer via Media Transfer (MTK).
If you already have developer's options enabled, skip this.
- Go into your settings, go all the way down to "About Device", and find where it says "Build Number" (which will most likely have the phone brand in the file name). Tap on that about 8 times until it give a toast notification saying "Developer's Mode Enabled".
After you get that done, go back into your regular setting and now there should be a box above your "About Device" button that says "Developer Options". Tap that, then turn them on (press OK/YES if a prompt pops up) and then select the following options ,if available.
-OEM Unlock
-USB Debugging
Now plug your phone into a computer and install the drivers for your phone (it should do it automatically) and launch the SP Flash Tool that you had downloaded (extract to desktop before you launch, or it will show "error"). Now open the SP Flash tool and click on the "Scatter Loading" button. Navigate to your desktop, and find the firmware folder you downloaded. Click on that, then click on "Firmware", and it should bring up a .TXT file (Scatter file) with the desired firmware version you want. Click on it and press open.
A chart will appear in the space below with all the things the firmware has built in. All of them should be checked. Take out your battery now (from your phone) and plug the phone in without the battery. Wait for the model on the left to name your device, and click on the drop down list above the chart, it should give 3 options. Firmware Upgrade, Download only, and Format All + Download. Press Format All + Download. The bar at the bottom will turn a few colors, depending on what it's doing.
Now you're done! It's flashed. From that version, try to figure out a way of rooting it.
WARNING: Flashing erases all data on device, please backup to an external storage (SD CARD), before attempting this, in case you brick your device.
Click to expand...
Click to collapse
You can download the tool at the bottom of this thread.
Sent from my RCT6873W42M using XDA Labs
Root BLU Dash M
AnarchyPhoenix746 said:
I need some assistance trying to find a method to root my Dash M (which appears to be extremely rare to find a rooting method for).
I already tried framaroot (tool I used to root my tablet before) and Kingroot and such, but none were able to do it (and all google searches led to videos on rooting a BLU Dash 5.0 or another device from the Dash range, which isn't what I needed).
The Dash M is running Android 5.1 and custom build BLU_D030U_V16_GENERIC 28-01-2016 15:41
If anyone could help it'd be very much appreciated c:
Click to expand...
Click to collapse
i know this is an old thread but.... i rooted mine (Dash M) with KingoRoot (look it up on Google)... i tried lots of stuff with no results, everything failed (i've already tried to root with KR in windows) but the only thing that worked was rooting with the android app in KR page... i felt really stupid after trying everything with no results when i've been using KR for other "hard phones".... either way, the only downside is that their SU manager displays all the time ads no matter where in the phone you are... but you can freeze the app to fix this and unfreeze it when you need to assign permissions....
BTW: its KingoRoot not kingroot (just in case)
I have a Galaxy Tab S4 device
I installed the following file on it
COMBINATION_FAC_FA81_T835XXU2ARI2_FACFAC_CL14168542_QB19864423_REV00_user_mid_noship_MULTI_CERT.tar.md5
Now the device has reached an interesting and strange situation that I do not know
I want to go back to the previous situation.
I can not get back to download mode.
I want to install back the real firmware.
How do I get out of this situation or I can switch back to download mode.
משה בניית אתרים said:
I have a Galaxy Tab S4 device
I installed the following file on it
COMBINATION_FAC_FA81_T835XXU2ARI2_FACFAC_CL14168542_QB19864423_REV00_user_mid_noship_MULTI_CERT.tar.md5
Now the device has reached an interesting and strange situation that I do not know
I want to go back to the previous situation.
I can not get back to download mode.
I want to install back the real firmware.
How do I get out of this situation or I can switch back to download mode.
Click to expand...
Click to collapse
Suddenly I found the place he could lead me away to the download page.
But he wants a password.
What can I do to find the password.
Misha knew?
Suddenly I found the place he could lead me away to the download page.
But he wants a password.
What can I do to find the password.
Misha knew?
Connect your device to a PC.
Then using adb type the following into a command prompt:
adb reboot download
Then I tried to re-install, and installed something wrong, and it wrote me this:
SCURIYY EROR: THIS DEVICE HAS DEEN FLASHED WITH HNANAHORIZED SOFTWARE & IS LOCKED. CALL YUR MOBILE OPERATOR FPR ADDITIONAL SUPPORT. PLEASE NOTE THAT REPAIR / RETURN FOR THIS ISSUE MAY HAVE ADDITIONAL COST.
I gave it to the repair shop, I hope they will succeed and that it's cheap ...
ashyx said:
Connect your device to a PC.
Then using adb type the following into a command prompt:
adb reboot download
Click to expand...
Click to collapse
Thanks for that tip, Ashyx. That saved my day. BTW, what is that password that the Factory Binary SW asks for? What's the reason for a password there?
I was trying this "Factory Binary" (combination) firmware because as soon as Pie came out for my SM-T835 (Galaxy Tab S4), it was available only for France (CSC = XEF) and I wanted to preview Pie/One UI in my device. Then my region's firmware (Brazil Open, CSC= ZTO) came out and I flashed it on the tablet. For some reason, my CSC became CHO (Chile Open), and I wasn't able to revert it back to ZTO (although it's a Multi-CSC and contain both regions) . Then I flashed
COMBINATION_FAC_FA81_T835XXU2ARI2_FACFAC_CL14168542_QB19864423_REV00_user_mid_noship_MULTI_CERT.tar.md5
(AP only) after having flashed official
T835UBU2ARL1_CL14803871_QB20870118_REV00_user_low_ship_MULTI_CERT_meta.tar.md5
but after entering code *#243203855#, as described in
https://www.sammobile.com/forum/threads/39155-How-to-change-CSC-with-a-combination-file
the code was recognized (cleared from the dialer) but no CSC selection appeared.
Do you have an idea where it went wrong?
Thanks in advance.