Database Info

[Q] What do I need to get Heimdall to work? (Mac)

I have tried numerous times to get it to flash to my phone. Thankfully I don't need it yet but as of now I have no backup plan if I ever had to return to stock. The best I have got is "Failed to detect compatible device."
If someone would be kind enough to, at the least, give me a checklist or links to what all I need to get this thing running I'd really appreciate it.
Running Mac OS X Lion if it helps.

i dont know about the mac version but there should be a readme in there for installation. also i think the mac needs codeless kext installed. should be outlined in the readme but couldnt tell you for sure.

I followed the instructions as best as I could understand. The UI pops up but refuses to flash or even recognize my phone.

re: flashing rom
tight686 said:
I have tried numerous times to get it to flash to my phone. Thankfully I don't need it yet but as of now I have no backup plan if I ever had to return to stock. The best I have got is "Failed to detect compatible device."
If someone would be kind enough to, at the least, give me a checklist or links to what all I need to get this thing running I'd really appreciate it.
Running Mac OS X Lion if it helps.
Click to expand...
Click to collapse
Since you have a mac it would be a lot easier for you to flash a
clockworkmod type custom rom.
You must have clockworkmod recovery to be able to do this.
If you are running stock rom and already have clockworkmod
recovery in your phone then then you can BACKUP your stock
rom with clockworkmod and then flash a new custom rom
as long as its a clockworkmod rom zipfile.
Most all of these custom roms you see here on xda are all
clockworkmod types (zipfiles) which do NOT need ODIN
or Heimdall at all.
But you do need to have a usb card reader if your your
computer is not reconizing your samsung phone as an external
USB drive.
If your Mac computer does reconize your phone as a external
USB device then you do not need to remove the microSD card
and you do not need a card reader.
I am sure you know how to use a usb card reader so I will not
go into that now.
Here is the link to the most popular custom rom for Infuse
which is the type you need. (clockworkmod flash)
http://forum.xda-developers.com/showthread.php?t=1195571
Follow the easy step by step instructions to a "T" if you
don't want to start all over and have to do it again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Good Luck,
Enjoy!
Please don't forget to give me a big THANKS if this post was worthwhile reading!

----------

Thanks everyone.
My main concern is that I'm running Gingerbread v2 b2. When we get the official bootloaders will I need to flash through Odin/Heimdall? Otherwise I'm fine.

tight686 said:
Thanks everyone.
My main concern is that I'm running Gingerbread v2 b2. When we get the official bootloaders will I need to flash through Odin/Heimdall? Otherwise I'm fine.
Click to expand...
Click to collapse
You are already on a rooted rom. Just get sgs lernel flasher and flash a "rainbow fix kernel." But id try to get heimdall working. it is super easy on linux. I love the debian package system.
If it doesnt see the device it sounds like an issue with that "codeless kext" which is described as being like a driver. that is unless samsung dropped the ball on the boot loaders again. the bootloaders in the odin oneclick packages for the galaxy s would prevent the device from being visable on a mac in download mode. later versions had this fixed. if i had a mac id help. i think the mac is a great system but i just dont know enough about your problem.
there is always the bootcamp or virtual machine options. if you need windows maybe i can help out if you pm me. or yu can do a quick install of mint or ubuntu which is not only more similar to mac than windows but with no need for drivers and the debian packages is easier to install heimdall on than odin is in windows.
or maybe you can contact the developers of heimdall.

tight686 said:
I have tried numerous times to get it to flash to my phone. Thankfully I don't need it yet but as of now I have no backup plan if I ever had to return to stock. The best I have got is "Failed to detect compatible device."
If someone would be kind enough to, at the least, give me a checklist or links to what all I need to get this thing running I'd really appreciate it.
Running Mac OS X Lion if it helps.
Click to expand...
Click to collapse
what version of heimdall did you download? i ask because it seems 1.3 wants a firmware.xml file that specifies compatible devices, could be an issue of it looking for that file. i still use v1.1.1, i just updated to 1.3 but dislike it and am going back, will see if 1.2 is compatable with the 1.1.1 frontend because it doesnt appear to have a frontend package.
edit:
yes v1.2.0 comandline seems to work with 1.1.1 frontend, install 1.1.1 and then you may upgrade to 1.2 (atleast that's how it works under linux)

Ok so I can use VMWare to load another OS on my Mac.
Any recommended distros to use this Debian package? So many flavors of Linux.
Lastly, can you please link me to past versions of Heimdall? I can only find the most recent.

tight686 said:
Ok so I can use VMWare to load another OS on my Mac.
Any recommended distros to use this Debian package? So many flavors of Linux.
Lastly, can you please link me to past versions of Heimdall? I can only find the most recent.
Click to expand...
Click to collapse
most use ubuntu. debian packages but there own repositories that are less likely to provide unstable updates to break your system.

[Q] ADB not recognizing phone on USB when its booted android, fine in recovery

Hey everyone, basically just what the title says. I plug it into the computer via USB, and ADB will not see the device when it's booted into Android. However when I boot it into recovery, it sees it fine.
I'm running Cyanogen 9 for a rom and TWRP for recovery.
Booted into android:
C:\Users\Michael>adb devices
List of devices attached
Booted into recovery:
C:\Users\Michael>adb devices
List of devices attached
b3fe68e1 recovery
I've tried installing drivers, deleting drivers, reinstalling drivers, rebooting, countless times now. Samsung's own software Kies won't even recognize the phone.
I am able to use ADB over wifi with ADB Wireless.
C:\Users\Michael>adb devices
List of devices attached
10.0.0.99:5555 device
Oh, and I can turn on USB Storage and access the filesystem with no problems.. so that works fine.
Am I going crazy or has someone else had this same problem? Thanks everyone.

Sorry for the silly question but have you enabled it in settings? That may or may not help you:thumbup:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

I should have posted that in my original thread.. but yes I have it enabled. I tried having ADB over network enabled just to see if it would help.. but it did't.

Is "USB Debugging" in the phone (inside Android) checked ? check this option and see..
PS:sorry if it is enabled ... ROM problem ? did adb work on stock ROM ?

Yep it is enabled. It did not work with the stock rom either and the only reason I know that is because my wife just got the same phone yesterday and I noticed it wasn't working while trying to root it.

Start all over again ...
Uninstall all drivers for the device and kies..
Install adb and USB driver for the phone and try again ...
You seem to have a software problem (a driver issue) somewhere around your PC (are you on Mac or Windows ?)

mahanddeem said:
Start all over again ...
Uninstall all drivers for the device and kies..
Install adb and USB driver for the phone and try again ...
You seem to have a software problem (a driver issue) somewhere around your PC (are you on Mac or Windows ?)
Click to expand...
Click to collapse
+1
try on another comp and c what happens, 2 phones cant be both screwed up so it must b comp

Yeah I agree it must be something to do with Windows. I will try installing the drivers and such on a computer at work on Monday and see what gives.
In the mean time I uninstalled everything and rebooted. Then I downloaded the drivers from Samsung's website, from here:
http://downloadcenter.samsung.com/c...27_GS_II_Skyrocket_USB_Driver_v1_3_2200_0.exe
I also read this post:
http://forum.xda-developers.com/showthread.php?t=1415051
and the #2 article points to: ATT_i777_GS2_USB_Drivers.zip
So I tried installing that too. Still nothing.
I took a couple screenshots during the process, maybe it will raise a red flag to one of you guys because I certainly can't figure this out.
When I plug in my phone, the "Android" device is what comes and goes. I've tried updating the drivers for that and pointing them to the Samsung drivers directory, just says it can't find them.
I admit to still being new around the whole android development thing, but with Windows I'm pretty proficient, I just can't figure out what I'm missing.

Just out of curiosity, why do you need to access adb with the phone not in recovery? You can do push pull commands through adb even if phone is in recovery

yoft1 said:
Just out of curiosity, why do you need to access adb with the phone not in recovery? You can do push pull commands through adb even if phone is in recovery
Click to expand...
Click to collapse
If super user is installed yes you can pull or push even in Android...But if not rooted it's only done while in recovery...

y do u need to use adb, i have returned to stock many times, so i installed cwm many times, all the roms r rooted, so w/cwm and root explorer i have not needed to use adb myself

vincom said:
y do u need to use adb, i have returned to stock many times, so i installed cwm many times, all the roms r rooted, so w/cwm and root explorer i have not needed to use adb myself
Click to expand...
Click to collapse
Well if you ask me I wouldn't trust root and i would modify things using recovery and adb..but that's just me..

mahanddeem said:
Well if you ask me I wouldn't trust root and i would modify things using recovery and adb..but that's just me..
Click to expand...
Click to collapse
k, but r u not installing any custom roms, as far as i know they are all prerooted, or u just need root todo ur own stuff

Personally I just like being able to have access to use adb. I can still use it over wifi using "adb wireless" so it's not a complete loss -- but for some reason the fact that the usb isn't working is just bothering me.
I'm not going to spend much more time fighting with it.. I'm sure it has something to do with the windows and the drivers.

mmerlina said:
Personally I just like being able to have access to use adb. I can still use it over wifi using "adb wireless" so it's not a complete loss -- but for some reason the fact that the usb isn't working is just bothering me.
I'm not going to spend much more time fighting with it.. I'm sure it has something to do with the windows and the drivers.
Click to expand...
Click to collapse
i agree its win7 and drivers

Hey I know this thread is a week old or so, but I just wanted to let you know I found the problem. The problem was actually the Cyanogenmod ROM I had installed.
I was having a few other unrelated problems with that rom so I decided to try SkyICS, and low and behold.. I can now access adb via usb.
Just wanted to put the solution forward and maybe it will shine light on someone else's problem.
Thanks again to everyone for all their help.

mmerlina said:
Hey I know this thread is a week old or so, but I just wanted to let you know I found the problem. The problem was actually the Cyanogenmod ROM I had installed.
I was having a few other unrelated problems with that rom so I decided to try SkyICS, and low and behold.. I can now access adb via usb.
Just wanted to put the solution forward and maybe it will shine light on someone else's problem.
Thanks again to everyone for all their help.
Click to expand...
Click to collapse
Not exactly a solution though, in that Sky ICS is still a TW-based ROM (as in, based off the stock ROM) and not an AOSP-based ROM like CM9 or AOKP.
I also had this issue. The problem was in fact a Windows driver issue though, even though I had installed them already. When I went to Device Manager it would always show up as generic "Android" device with no driver under "other devices". I right-clicked it, Selected "Update device drivers" and then I believe there was an option to select drive from existing installed drivers. I'm on my linux partition right now so I forget what the precise option dialogue was, but it was a separate option from the "Browse my computer" option. From there it opened up a long list and I scrolled down and found one of the Samsung entries listed. I believe it was Samsung Electronics Co. Ltd. (there were others like SAMSUNG in all caps, etc.). I then selected the driver from the list within that Samsung group and ADB worked again.

[TOOL] schlexedeeler Tool V2 [ONLY ICS!] * ROOT Acer Iconia A210 [NOT USE ON JB!!]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
lieckedeeler & schlex2010
aka SCHLEXEDEELER
ONLY USE THIS TOOL IF YOU HAVE AN ICS VERSION (4.0.4)
WE ARE NOT RESPONSIBLE FOR BRICK OR ANY OTHER ERRORS ON YOUR TABLET
WE ARE NOT RESPONSIBLE FOR BRICK OR ANY OTHER ERRORS ON YOUR TABLET
ONLY USE THIS TOOL IF YOU HAVE AN ICS VERSION (4.0.4)
- Root incl. su & busybox binary (install Superuser from Play Store)
- permanent RW on system folder
- adb root shell
- DVB-T USB support (schlexedeeler Kernel 1.1+)
- CWM Recovery with touch
Click to expand...
Click to collapse
DOWNLOAD SCHLEXEDEELER TOOL V2
=============================================================================================================================
If you want flash back stock kernel or/and stock recovery and stock bootanimation.zip
First step: Copy stcok bootanimation.zip to /system/media
Second step: Flash stock kernel & recovery
It is stock recovery and kernel out of ICS 4.0.4​​​
Download stock bootanimation.zip
Click to expand...
Click to collapse
Download Tool to flash stock kernel & stock recovery
Click to expand...
Click to collapse
Password for the 7zip files:
iknowtherisk!​
Click to expand...
Click to collapse

Thank you! Going to try this as soon as i get to my a210.

.... Placeholder ....

And you can just press the 3 point?, Only root, the kernel does not need to unlock me ....

Probably not. It dumps a CWR image to /dev (overwriting the factory recovery?), which is boot, so you have to be unlocked.
CWR is used to mount /system (rw) so that adb can push Superuser and some other binaries.
I got stuck, after loading up CWR. My Windows 7 (x64) couldn't recognize my A210 while CWR was running. Downloaded USB drivers through the Android SDK, and the Acer USB drivers, but neither of them did any good i continued with the rooting process (so that it could clean up after itself) but nothing got pushed to /system (which is no surprise, seeing my tablet was unrecognized). So, now i have an unlocked bootloader, no root, and i'm unable to get into recovery... nothing happens, if i hold volume down, while powering on. I have to press the reset button, to restart it properly.
Could it be that there are no drivers for Windows 7 x64?
Edit: ok, i've read through the topic at android-hilfe.de, and got it working (had to manually install the driver). Now i have root! Thank you!

help for dummies
deleted

deleted

does it give a instruction for this tool, it would be great
Greets

Is anyone working on a ROM or MOD for the Iconia A210 ?
Sent from my A210 using xda app-developers app

Hey 4.1.1 To have?

Alexey71 said:
Hey 4.1.1 To have?
Click to expand...
Click to collapse
What exactly is your question?
I don't know if it will work with 4.1.1, because I do not have 4,1.1 on my tablet! You have?

I get everything back to its factory state, or even be the standard kernel?

Alexey71 said:
I get everything back to its factory state, or even be the standard kernel?
Click to expand...
Click to collapse
Sorry for OT:
Please learn english, or use a better translater tool for your questions!
You use this tool at your own risk, so please stop bugging me with private messages AND forum posts!

Hy everybody
I tried to root my A210 yesterday using your program. But I point out some difference between what happen and the "how to".
First, I didn't have 4 option when I start the tool. I just have the bootloader option and a root option.
Following the "how to", I first activated the open mode to boot.Then, I choose the second choice (root) and that's when it didn't follow the "how to" document. My A210 did restart and boot to a*SCHLEXEDEELER edition but it never ask me to restore my data. And when it get restarted, everything was as it were.I also didn't have all the part about installing the driver because my PC still detect the tab as "adb interface".
I aldo never had the section about mount and unmount system.
Then the*SCHLEXEDEELER tool ask me if I wanted to install the custom recovery. As I was pretty scared of what might happened, I answered "no". So the tool ended.
I cheched on my tab but I was still not root so I did all that stuff again but choose "yes" instead of "no" for the custom recovery.The*SCHLEXEDEELER tool printed out many lines but one caught my attention.
It was something like :"data\tmp\cwm[...].img : no such file or dir".there is a file called "cwm[...].img" (the [...] is because I don't recall the exact name) in the folder in wich there is the*SCHLEXEDEELER tool.
But I didn't suceed in making it finding this file.
And when I checked whether I'm root or not, it turns out that I wasn't.
Any ideas or suggestion?
Still, thanks a lot for your job.

Tab acer A210 user said:
Hy everybody
I tried to root my A210 yesterday using your program. But I point out some difference between what happen and the "how to".
First, I didn't have 4 option when I start the tool. I just have the bootloader option and a root option.
Following the "how to", I first activated the open mode to boot.Then, I choose the second choice (root) and that's when it didn't follow the "how to" document. My A210 did restart and boot to a*SCHLEXEDEELER edition but it never ask me to restore my data. And when it get restarted, everything was as it were.I also didn't have all the part about installing the driver because my PC still detect the tab as "adb interface".
I aldo never had the section about mount and unmount system.
Then the*SCHLEXEDEELER tool ask me if I wanted to install the custom recovery. As I was pretty scared of what might happened, I answered "no". So the tool ended.
I cheched on my tab but I was still not root so I did all that stuff again but choose "yes" instead of "no" for the custom recovery.The*SCHLEXEDEELER tool printed out many lines but one caught my attention.
It was something like :"data\tmp\cwm[...].img : no such file or dir".there is a file called "cwm[...].img" (the [...] is because I don't recall the exact name) in the folder in wich there is the*SCHLEXEDEELER tool.
But I didn't suceed in making it finding this file.
Click to expand...
Click to collapse
FIRST OF ALL you don't read the thread correctly:​
The "How to" of Heroturtle is NOT for V2.0 Final Edition!! Do not use that "how to" !!​
So here is what the tool do if you select root:
Start your device into bootloader (fastboot mode)
Flash boot.img to your device via fastboot
Pushing binary files like su and busybox to your tablet
READY!
It's important that you have install all drivers correctly!
The 4 points are from the Versions before and are not necessary anymore now.
If you have done the root process, you must install SuperUser from the PlayStore! After that you have root!
Use only schlexedeeler Tool V2... You are confusing something and write about things that no longer exist in the new version!!! No restore my data. etc...

Sorry for my bad English
schlexedeeler Kernel 1.1, Not mount USB - NTFS format....

ok, got it.
I will try to install super user tonight and see if it's good.
I'll write a message to keep you inform about that.
thank you for your quick and pertinent reply

Tab acer A210 user said:
ok, got it.
I will try to install super user tonight and see if it's good.
I'll write a message to keep you inform about that.
thank you for your quick and pertinent reply
Click to expand...
Click to collapse
If not, please let me know, then we will find a solution for you, but I think if you do only that, what the tool tell you, you're on the right way :good:

Alexey71 said:
Sorry for my bad English
schlexedeeler Kernel 1.1, Not mount USB - NTFS format....
Click to expand...
Click to collapse
I will talk to lieckedeeler... Maybe he have a solution for that.

Minor Update 2.01:
* correct some missspellings
* correct adb command for flashing CWM recovery

Cloudfone Excite 350g

This is a rebranded phone in the Philippines running ICS 4.0.4, has 512mb RAM, 1GHZ core. Does anyone know what the original phone is? I've had a hard time looking for pc drivers, but was able to root it with bin4ry.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
sent from my rooted Cloudfone Excite 350g

I just found out that the phone is a rebranded Mobistar Touch Cream 350.

Rooted the Cloudfone Excite 350g?
Hi mrichiem! I have the same phone but was unable to root it with Bin4ry v17, though I have installed the drivers using Moborobo and also tried with Super OneClick. What process have you made to root it? O_O I tried taking it to safe mode, but still the permission is still denied. I am searching ways to root it but since it was just released last December, I guess the company is suppressing the growth of tutorials of rooting their models. But I guess the company is expecting users to root it because of it's low internal memory. O_O Thanks.

::ROOT:: Cloudfone Excite 350g
Let me set down here exactly what I did to root my excite 350g. The files you will need are attached, but you will have to search and download Moborobo. I had to research the proper way to install the drivers as my first attempt ended up soft-bricking my phone. I had to bring it to the service center to have it repaired. Funny thing was my warranty still covered it, even though it was already rooted and I had changed the boring yellow bootanimation.
So, be warned and root at your own risk!!
Extract the files to a folder or your desktop. Turn off your 350g and remove the battery. The next step will take a bit of dexterity and timing. Plug the USB cable to your PC. Press and hold the Volume up button on the phone and quickly insert the battery. The pc will prompt you to install drivers for the device. Just direct the wizard to the MTK65xx Driver folder. Once drivers are installed release the volume up button. Open the MTK Android PC Sync Tool and select Cloudfone Excite 350g in the popup. This will install the MTK Suite Daemon on the phone. Once done, you can close the tool. Next open Moborobo which will automatically install additional drivers for the phone. Once you have done all of this, you may now proceed with rooting. I have included two versions of bin4ry in the file. Try using Root Mtk Android 4.0.4 v15 first. If this does not work, use Root MTK ICS. The phone should now be rooted.
Download: http://www.4shared.com/rar/kOhRfezo/DEV.html

Great!
Haha. As they were saying that the warranty will be void if you have rooted the phone. Great! Thanks! I'll try it. I hope i won't end up bricking my phone. Thanks mrichiem! :good: I will reply as soon as I have tried the method. :highfive:

Haist... after following all the instruction still after rebooting my phone dont show a super user icon. Even the computer says im already rooted
Sent from my Flare (S100)/A9 using Tapatalk 2

Please try this to know if you are really rooted...
werdna99 said:
Haist... after following all the instruction still after rebooting my phone dont show a super user icon. Even the computer says im already rooted
Sent from my Flare (S100)/A9 using Tapatalk 2
Click to expand...
Click to collapse
Please install this app from the Google PlayStore:
Android Terminal Emulator by Jack Palevich
It is mainly a Linux Command Prompt Emulator that is used to do some functions such as cp (Copy), ifconfig (Get the IP address of your phone), etc.
After you installed it, please follow the instructions below:
Open the Android Terminal Emulator App.
Type: cd root
If you see something like /system/bin/sh: cd: /root - Permission denied, you are not yet rooted. And maybe that is the reason why the SuperUser app was not installed.
Are you rooting the your CM Flare? I guess this trick works only for Cloudfone350g.

Sir, exactly how many seconds does it take for you to plug the phone via usb then hold the volume up and insert the battery?? i cannot seem to get it right. i've tried a dozen times already and i still can't get it.

No sir. Im rooting the cloudfone of my friend. I already root several android phone this unit give me head ache my cm flare ia already rooted
Sent from my Flare (S100)/A9 using Tapatalk 2

Replying to all
HI ALL!
At first I was having difficulty with this method trying this on Windows 7. But I switched to Windows XP in order to see if there would be difference. Use Windows XP instead because I have successfully rooted my phone with that.
I just rooted my phone now, so it took me a long time to reply. It is because I tried to see if someone would verify the trick and to give further instructions to it. But then, it seems no one is willing to share. XD
So here is the reason for each step of the trick.
1. Insert the USB Cable (take note, the USB cable to the PC not to the Phone), insert the battery, then hold Volume UP. This would only take less than 10 seconds. It's aim is to force the PC to detect the MTK Preloader so that you can install it the drivers for it.
2. Run MTK Android PC Sync Tool and let it install the MTK driver for your phone. The aim is to install the "debug mode MTK driver" into your Phone so that the Root by Bin4ry would be able to copy files into your Phone's internal memory and run commands.
3. Lastly, Open moborobo and let it install the Moborobo Suite Daemon into your device. The aim is just like the #2. To add drivers that will support the rooting.
Root it with Root Mtk Android 4.0.4 v15.
I have added some screenshots as a proof Hit thanks for me and mrichiem if you have succeed!

BlueFireSiege said:
HI ALL!
At first I was having difficulty with this method trying this on Windows 7. But I switched to Windows XP in order to see if there would be difference. Use Windows XP instead because I have successfully rooted my phone with that.
I just rooted my phone now, so it took me a long time to reply. It is because I tried to see if someone would verify the trick and to give further instructions to it. But then, it seems no one is willing to share. XD
So here is the reason for each step of the trick.
1. Insert the USB Cable (take note, the USB cable to the PC not to the Phone), insert the battery, then hold Volume UP. This would only take less than 10 seconds. It's aim is to force the PC to detect the MTK Preloader so that you can install it the drivers for it.
2. Run MTK Android PC Sync Tool and let it install the MTK driver for your phone. The aim is to install the "debug mode MTK driver" into your Phone so that the Root by Bin4ry would be able to copy files into your Phone's internal memory and run commands.
3. Lastly, Open moborobo and let it install the Moborobo Suite Daemon into your device. The aim is just like the #2. To add drivers that will support the rooting.
Root it with Root Mtk Android 4.0.4 v15.
I have added some screenshots as a proof Hit thanks for me and mrichiem if you have succeed!
Click to expand...
Click to collapse
Last time i used a windows 7 pc ill try your advice
Sent from my Flare (S100)/A9 using Tapatalk 2

Backup rom
Please backup rom for me, i need rom!!

I also had the same problem as I has already rooted my Excite 350g before backing up the ROM. So I had to search the net to look for a way to restore my phone in case something went wrong. And indeed, something went wrong. I ended up flashing the original Mobiistar firmware and discovered something interesting. The original camera resolution of the device is 3MP, which is what I have now. And after uninstalling the stock Vietnamese files, I ended up with 160MB of free internal memory. The site is in Tieng Viet, so use Chrome to translate the page as it loads and depend more on the screenshots than the actual instructions. As usual, flashing MTK ROMs work best on PCs running Windows XP.
Click Here to Open Link

Posting benchmark results before and after flashing the stock Mobiistar ROM.
sent from my Excite 350g

[root] chuwi v10hd 3g

Hello ,
I find a way to root this very good tablet , the "CHUWI V10HD 3G 64GO" dual boot windows 8.1/android 4.4.2 and 4.4.4.
I have followed this website : http://tablette-chinoise.net/rooter-toutes-les-tablette-intel-x86-avec-supersu-t7014
Frist you need to download the rooting kit : http://ul.to/71jrzvgy
and the intel adb driver : IntelAndroidDrvSetup1.9.0.zip
On your computer ,unzip the "IntelAndroidDrvSetup1.9.0.zip" and run the .exe to install the driver
connect your tablet to your computer , and boot the tablet on android
On android ,activate the "Usb debug mode" from the developper menu
On your computer unzip the "Root-tablette-chinoise.net.rar" and launch the "3 Root-tablette-chinoise.net.bat"
follow the instrunction on your screen , and yeah it's done !!:highfive:
hope it helps.
mirrors:
Root-tablette-chinoise.net.rar
http://uptobox.com/egez2zpy2lls
IntelAndroidDrvSetup1.9.0.zip
http://uptobox.com/d3mmycfutzzt

funregis said:
Hello ,
I find a way to root this very good tablet , the "CHUWI V10HD 3G 64GO" dual boot windows 8.1/android 4.4.2 and 4.4.4.
I have followed this website : http://tablette-chinoise.net/rooter-toutes-les-tablette-intel-x86-avec-supersu-t7014
Frist you need to download the rooting kit : Root-tablette-chinoise.net.rar
and the intel adb driver : IntelAndroidDrvSetup1.9.0.zip
On your computer ,unzip the "IntelAndroidDrvSetup1.9.0.zip" and run the .exe to install the driver
connect your tablet to your computer , and boot the tablet on android
On your computer unzip the "Root-tablette-chinoise.net.rar" and launch the "3 Root-tablette-chinoise.net.bat"
follow the instrunction on your screen , and yeah it's done !!:highfive:
hope it helps.
Click to expand...
Click to collapse
can you please upload the rooting kit and adb drivers to xda servers or mediafire or mega. uploaded.to is not the most convienient. have to wait 3 hours to get the next filr

suspect008 said:
can you please upload the rooting kit and adb drivers to xda servers or mediafire or mega. uploaded.to is not the most convienient. have to wait 3 hours to get the next filr
Click to expand...
Click to collapse
I have added uptobox

funregis said:
I have added uptobox
Click to expand...
Click to collapse
thak you very much for fast action. hope to be in touch. any issues so far with the device? I only had it for 2 days but could not try it.

It's working fine. The battery is the only weak point.

funregis said:
It's working fine. The battery is the only weak point.
Click to expand...
Click to collapse
Yep noticed that, but its expected running a x86 processor and powerful hardware. Idle drain in android is higher than windows.
anyways, funregis, I cant get root with your script. I got drivers installed and adb works fine. it gets detected and device responds to adb commands. but root script is not working as intended.
I get lot of missing files messages in the script window. here I attach screen shot as I cant copy it.
can you recheck the script in bat file. I see that you are trying to copy the files to temp folder in devices data partition but I think im not seeing the source is declared correctly. so no file is being copied. im not much of a script guy so I dont know for sure exactly. can you help me.
Edit : checked, script seems to be correct.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

suspect008 said:
Yep noticed that, but its expected running a x86 processor and powerful hardware. Idle drain in android is higher than windows.
anyways, funregis, I cant get root with your script. I got drivers installed and adb works fine. it gets detected and device responds to adb commands. but root script is not working as intended.
I get lot of missing files messages in the script window. here I attach screen shot as I cant copy it.
can you recheck the script in bat file. I see that you are trying to copy the files to temp folder in devices data partition but I think im not seeing the source is declared correctly. so no file is being copied. im not much of a script guy so I dont know for sure exactly. can you help me.
Edit : checked, script seems to be correct.
View attachment 3349402
Click to expand...
Click to collapse
Have you set your tablet in "debug USB mode" from the developper menu on android ? I forgot to write this on the guide

funregis said:
Have you set your tablet in "debug USB mode" from the developper menu on android ? I forgot to write this on the guide
Click to expand...
Click to collapse
yep thats the basics right.
Your script works. I executed commands manually. all work fine. all the files get pushed and every command is in right way when executed manually. but just after the tab restart, all things get reset. im not sure about a workaround on this situation. do you have any idea?
I ve set usb debugging and drivers installed correctly and adb works fine.

suspect008 said:
yep thats the basics right.
Your script works. I executed commands manually. all work fine. all the files get pushed and every command is in right way when executed manually. but just after the tab restart, all things get reset. im not sure about a workaround on this situation. do you have any idea?
I ve set usb debugging and drivers installed correctly and adb works fine.
Click to expand...
Click to collapse
Strange it worked for me on android 4.4.2 and 4.4.4 , no idea of the problem if all command worked
When you launch the .bat have you "0/root" as id in the first prompt ?
I've uploaded the rooting kit with english translation (it can helps or not...)

funregis said:
Strange it worked for me on android 4.4.2 and 4.4.4 , no idea of the problem if all command worked
When you launch the .bat have you "0/root" as id in the first prompt ?
I've uploaded the rooting kit with english translation (it can helps or not...)
Click to expand...
Click to collapse
Yes ID is "0/root". its still the same as screen shot when ran the script bat file. im gonna try manual method again and without rebooting I will update the su binaries

Got the root
I achieved the root. just I had to manually push the files and everything. and without reboot I updated the binaries and now it sticks. so thank you for help and files.

Nice

OK, dudes. CONFIRMED ROOT android 4.4.4 with MOTOCHOPPER thanks to morlock8k's link: http://www.mediafire.com/?f4lipgd1hh3jug2