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.
Related
Okay so i had my phone rooted for fun and had no original purpose of installing CM7 on it before i read about a thread that displayed that it was a safe method to do according to what was wroten.
The phone (Galaxy S i9000) 2.2.1 Android was however, what i think is "bricked".
The phone starts with a simple picture showing me a phone with a dot-frame going to a triangle (warning sign) and further to a computer screen. Does this mean that the phone is bricked or is this something else?
The phone does not respond to:
Adb (android-sdk) throught CMD (windows 7 32 bit)
Kies
Odin
Droid Explorer
Android Control 1.3
The phone was originally modified with Odin 1.7 and failed after pushing the ROM into the phone. According to what i did, i did everything correct according to what was written in the explenation.
Please answer as quick as possible, otherwise i will try to get out the warranty which i doesn't even have anymore.
This screen means in fact that you are "nearly bricked" but some kind of emergency system is running what should act like the download mode (as I know it from my SGT). I had similar problem and after a bunch of work I found out that it was the USB driver from Samsung. A simple click in the Samsung Kies Software to re-install drivers helped me and I was able to normally flash a new Kernel, Rom, whatever. I guess you have a sync software as well (as well Kies?!), or try uninstalling drivers manually. Might work. May be worth a try.
Edit: Even with broken drivers it seemed that it was working with Kies... sync (with comlications, broke my calendar app after restarting tab after sync), storage mode, everything but no adb and such.
Sent from my GT-P1000 using XDA App
I know tried to:
Re-install Kies completelly
Removed drivers (manually)
Turned of the phone: ripped the battery out
Put it back in
Re-installed Kies (no phone connected)
Kies 2.0 Successfully installed
Re-install drivers throught kies
Checked that the phone was off and repeated step: 3
Put the usb cable in and begged to the god of nerds
Profit? No...
Kies didn't even find any device that it could try to connect to. Neither did any of above written softwares. The pc cant communicate with the phone.
Tried: 3-button-combo: lots of times!!
Adb prints: No device found
Odin: No device
Kies: No device
DroidExplorer: No device
Note that i live in Europe.
Guess you have a nice 450€ brick then... but as I am more a semi-noob than a semi-pro I am not qualified to tell you this as a shure fact... just an opinion...
send from my SGT with Overcome...
I contacted the company that sold my phone, got the number for Samsung Support, they redirected me to the company "Mobilbyrån" which will re-install and make sure my phone starts working as usual for 45 £. All thought i could done it with a jig on my own, but i rather trust a professional company to do this for me in exchange for my warranty (billing only guilty if warranty denied).
According to "Mobilbyrån" or translated "Phone Agency" this is a ordinary errand and that it's highly possible that this will go on my warranty that is still guilty for atleast 8 more months.
Solution for my problem would be to:
1. Build a Jig to hardware boot the phone into download mode
2. Enter Odin and push a new rom inside (preferebly a stock (android))
3. flash kernel (could be done before 2?)
4. Profit
I guess there is no way, even for Samsung, to find out if there was a third party Rom etc is installed as device refuses to do anything. You are only f*** up if they are still able to read out current data somehow... but 45£ is really a fair deal...
send from my SGT with Overcome...
Sucks to hear that about your phone. I have a similar model and I managed to CM7 working. I followed a tutorial on this website and I semi-bricked it too at first although I've never had the same problem as you regarding Odin not being able to locate the phone.
Can you tell me the steps you took in trying to flash CM7 on it?
Also, refer to this topic to see if it can be of any help: clicky
It was when i were to use Odin the second time.
I managed to flash the speedmod kernel into the original Android ROM (stock). I also managed to install one of the zips that were to be installed throught recovery. But after this (when connecting to Odin) and this was the step where only one of the checkboxes (F.Reset Time i think).
So i made this and the Odin 1.7 told me: "Failed" or such. And i then got paniced, i disconnected the phone since i was so frightened something had gone bad, the phone was turned of and i reset the battery (in and out) and started the phone to notice that image (as told above).
Now i thought: Yeah, lets just reset the phone throught recovery and were kind of happy by the thought of it. So i tried to access it with the 3-btn-combo but as i just remembered is that in Europe this is patched to be removed.
So i thought, lets send a adb shell to the phone throught Android-spk and i connected the phone and sent the command: Adb wait-for-device, nothing happened and the phone couldn't be found by above said softwares.
So i thought: "Hmm... this isn't good"... So i started googling for what reason this could be and i believe it's called "Semi-bricked", that is "Almost" bricked phone.
So i were sad, called Samsung Tech support and they told me to contact "Mobilbyrån Stockholm" who were a tech repair support, they wanted either 45 £ or my warranty insurance if i wanted the phone fixed. I thought... yeah right, so i sent my phone to the company and i am now waiting for what they are about to do with it.
I suppose a jig would work, thought no one i know got one and i have poor skills at constructing electrical or related components so i put up a thread (like this one) at Sweclockers.com and found a guy that had one which he could lend for me, super, just have to wait and see what happens.
I suppose this "Jig" method could work, but will the computer really notice my phone as a device? It doesn't do that now, thats why i am asking.
At all moments i used Terminal for Android phones (throught market: Android Terminal) by sending commands (since 3-btn-combo didnt work):
> "Su" <- needed for Superuser allowance for controlling the phone
> "Adb reboot recovery"
> "Adb reboot download"
And the phone starts with this picture:
{
"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"
}
Also, in that correct order.
Hey guys, I know I'm a noob and I apologize in advance if this question has been answered.
I'm trying to root my G2x with SuperOneClick. I have a Mac and I'm running VMware with Windows 7. I'm following the directions on this page (starting in debug mode, drivers installed):
http://forum.xda-developers.com/showthread.php?t=803682
and it gets hung up on step 6. I read a little more and turned my debug mode off and on, and then the process completes. It looks like it completes step 7, but then when it is "Remounting /system with read/write access"...it says "/mount: operation not permitted. FAILED"
Also----I have tried the other method with CWM but windows 7 does not give me the option to install the drivers for the APX mode (when I go to the device properties, install driver is disabled)
I really just want to root my phone the easiest way possible. Any advice would be GREATLY appreciated!! (especially if it can get me rooted with SOC). Thanks!
fsustrength said:
Hey guys, I know I'm a noob and I apologize in advance if this question has been answered.
I'm trying to root my G2x with SuperOneClick. I have a Mac and I'm running VMware with Windows 7. I'm following the directions on this page (starting in debug mode, drivers installed):
http://forum.xda-developers.com/showthread.php?t=803682
and it gets hung up on step 6. I read a little more and turned my debug mode off and on, and then the process completes. It looks like it completes step 7, but then when it is "Remounting /system with read/write access"...it says "/mount: operation not permitted. FAILED"
Also----I have tried the other method with CWM but windows 7 does not give me the option to install the drivers for the APX mode (when I go to the device properties, install driver is disabled)
I really just want to root my phone the easiest way possible. Any advice would be GREATLY appreciated!! (especially if it can get me rooted with SOC). Thanks!
Click to expand...
Click to collapse
Which stock ROM, froyo or gingerbread?
tahahawa said:
Which stock ROM, froyo or gingerbread?
Click to expand...
Click to collapse
Sorry, I should have stated that - Gingerbread.
fsustrength said:
Sorry, I should have stated that - Gingerbread.
Click to expand...
Click to collapse
Then don't mess with super one click. Just flash clockwork mod recovery and then flash the root.zip.
"If you run Mac or another Linux flavor, make sure you install Mono:
http://www.go-mono.com/mono-downloads/download.html"
from
http://forum.xda-developers.com/showthread.php?t=803682
Here you go, simple instructions for rooting 2.3.3 GB G2x.
http://forum.xda-developers.com/showthread.php?t=1255214
Thanks guys...I'm still having some issues though.
As far as running SuperOneClick on my Mac. I installed Mono and figured out how to open it with Terminal. However, when I click Root, it says:
"Automatic version check failed. Is your OS version 2.0 or higher?"
{
"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"
}
Then when I click Yes, it gives me this result and fails:
I tried to follow all the instructions, but I'm not very knowledgable when it comes to Terminal. I'm not so sure how to do these steps (in particular, installing the libraries to get ADB working and installing WinForms...were these done automatically by running the Mono installer?
http://forum.xda-developers.com/showpost.php?p=8699742&postcount=537
________________________________________
That's my issue with SuperOneClick.
With ClockWorkMod, I have a different problem. First, can it be done on a Mac without running Windows? If not, I have tried running it on my Windows 7 VMware build, and it will not allow me to install the drivers. When I boot my phone in APX mode, I right click on the device and get to device properties, it has install driver disabled (greyed-out) and I don't know what to do.
Again, thanks for the advice. I know I'm a noob but I really appreciate your help guys!!!
fsustrength said:
Thanks guys...I'm still having some issues though.
As far as running SuperOneClick on my Mac. I installed Mono and figured out how to open it with Terminal. However, when I click Root, it says:
"Automatic version check failed. Is your OS version 2.0 or higher?"
Then when I click Yes, it gives me this result and fails:
I tried to follow all the instructions, but I'm not very knowledgable when it comes to Terminal. I'm not so sure how to do these steps (in particular, installing the libraries to get ADB working and installing WinForms...were these done automatically by running the Mono installer?
http://forum.xda-developers.com/showpost.php?p=8699742&postcount=537
________________________________________
That's my issue with SuperOneClick.
With ClockWorkMod, I have a different problem. First, can it be done on a Mac without running Windows? If not, I have tried running it on my Windows 7 VMware build, and it will not allow me to install the drivers. When I boot my phone in APX mode, I right click on the device and get to device properties, it has install driver disabled (greyed-out) and I don't know what to do.
Again, thanks for the advice. I know I'm a noob but I really appreciate your help guys!!!
Click to expand...
Click to collapse
Don't use a windows vm. use Linux instead. Find the script and you should be fine. find the thread for Mac and it details everything.
tahahawa said:
Don't use a windows vm. use Linux instead. Find the script and you should be fine. find the thread for Mac and it details everything.
Click to expand...
Click to collapse
Thanks. I found this as the "Mac thread"...is it what I should be looking at?
http://forum.xda-developers.com/showpost.php?p=8699742&postcount=537
I'm having a little trouble with the instructions. Namely, when I'm entering
apt-get install lib32ncurses5
apt-get install lib32stdc++
apt-get install libmono-winforms2.0-cil
Terminal says they can't be found, and I can't find these in the downloaded SOC directory either. I'm thinking this is the problem because it keeps asking me if I'm using version 2.0. Am I doing something wrong?
______
Also, I know you said not to use VM, but I don't have a PC so I'm trying everything I can think of. Here is the result when I'm running SOC on my VM.
To get to this point, it actually stops on Step 5/6 and goes unresponsive. At that point, the only thing I have done to make it move was to toggle USB debugging off and on (I've left it on that step for 20-30 minutes and nothing happens if I don't toggle it).
Then it says failed. I'm hoping by reading the results you might be able to figure out what's going on?
______
One more question---is there anyway to do CWM on the Mac? I have only found instructions for the PC on the forums. Maybe I'm missing it. I have noticed on the CWM instructions it says:
"Install APX Windows driver from APX folder.
(Windows x86 and x64 O/S Drivers):
****If you are running VmWare kill it.****"
I don't understand what it is asking me to kill.
Again, thanks a lot for your time and consideration. I really appreciate it, and if I didn't have a dropbox account I would definitely sign up with your referral. Hope you're having a nice weekend.
Food you check the sticky in the dev section? http://forum.xda-developers.com/showthread.php?t=1099281
Thanks everyone!!!! What ended up working was this:
Flashing CWM with a Linux Virtualbox (after updating the CWM files that were existing already in the Virtualbox).
Then I downloaded the root and put it on my SD card, and rooted via CWM on my G2X. Finally after too many hours for something so "simple" I am finished. Thank you everyone who gave their input!! It was very helpful. I hope that someday I can return the favor!
Ive had this phone for a week or so and have since rooted it. But I am now having trouble connecting using USB. I can connect it to my PC and it will show 2 removable drives in my list of drives in explorer but I cannot access them. I also cannot mount my SD card in CWM. It doesnt show any removable drives when I try in explorer.
This all worked fine until I tried installing Samsung Kies which seems to be a POS and somehow screwed my drivers up. Ive removed them, got Kies off my system even went so far as to remove the Samsung drivers off my system and use Revo Uninstaller Pro to get any remnants off only to reinstall and have the same issue.
Any help would be appreciated.
Im using Win 7 64bit. With this ROM http://forum.xda-developers.com/showthread.php?t=1918608
I also tried this to no avail.
First uninstall Kies from your PC and make sure you doesn't leave behind any files.
Uninstallation of the software and the drivers installed by Kies I suggest using Revo uninstaller to do that.
Uninstall it from your PC then make a fresh installation.
Open Kies but do not connect your phone, if it wants to update Kies, go ahead and do it.
Close Kies, connect your phone and open Kies.
Smerks said:
I also tried this to no avail.
First uninstall Kies from your PC and make sure you doesn't leave behind any files.
Uninstallation of the software and the drivers installed by Kies I suggest using Revo uninstaller to do that.
Uninstall it from your PC then make a fresh installation.
Open Kies but do not connect your phone, if it wants to update Kies, go ahead and do it.
Close Kies, connect your phone and open Kies.
Click to expand...
Click to collapse
Uninstall all divers than install this one. Driver Link
I'd also switch ROMS and see if that helps.
chjema said:
Uninstall all divers than install this one. Driver Link
I'd also switch ROMS and see if that helps.
Click to expand...
Click to collapse
Thats the driver I had installed, but I think KIES somehow screwed everything up. Im going to try to reinstall KIES then remove it with Revo and install the exact driver from your link and report back.
chjema said:
Uninstall all divers than install this one. Driver Link
I'd also switch ROMS and see if that helps.
Click to expand...
Click to collapse
Well I did try what you linked and no good. I still get the 2 removable drives showing up in windows but it tells me to insert a disk when I try to access them.
I dont quite know how Im going to change ROMS if I cant mount USB storage in CWM to get the ROM on there for flashing.
Smerks said:
Well I did try what you linked and no good. I still get the 2 removable drives showing up in windows but it tells me to insert a disk when I try to access them.
I dont quite know how Im going to change ROMS if I cant mount USB storage in CWM to get the ROM on there for flashing.
Click to expand...
Click to collapse
Are you mounting them from your phone? You need to mount them pnce you connect it to the pc.
Seen here http://www.gadgetvenue.com/wp-content/uploads/2010/05/Dream-Android-2-2-usb.png
That is not our phone but it looks the same
Smerks said:
I dont quite know how Im going to change ROMS if I cant mount USB storage in CWM to get the ROM on there for flashing.
Click to expand...
Click to collapse
Haha yeah..true. You can Odin back to stock, or Insert the SDcard into your PC (no cable) and put a Rom there, or can also "I THINK" use adb to push a rom.
chjema said:
Are you mounting them from your phone? You need to mount them pnce you connect it to the pc.
Seen here http://www.gadgetvenue.com/wp-content/uploads/2010/05/Dream-Android-2-2-usb.png
That is not our phone but it looks the same
Click to expand...
Click to collapse
1st let me say Im an idiot on forgetting to mount the USB that way but it wasnt asking me I had to look on the notifications and tap from there.
But that still leaves me unable to mount from within CWM. I attempt to mount my SD card and it doesnt show anything, now I also installed ROM Manager and flashed CWM Touch in between my rooting and now, could this somehow have screwed things up?
Something else I just noticed since the 2 removable drives are now accessible, thanks to you helping me realize I was forgetting something important, both of these drives seem to have what may be important stuff on them but also seem like it may be duplicated or being a bit new to this it could just be the way its supposed to be.
{
"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"
}
Smerks said:
1st let me say Im an idiot on forgetting to mount the USB that way but it wasnt asking me I had to look on the notifications and tap from there.
But that still leaves me unable to mount from within CWM. I attempt to mount my SD card and it doesnt show anything, now I also installed ROM Manager and flashed CWM Touch in between my rooting and now, could this somehow have screwed things up?
Something else I just noticed since the 2 removable drives are now accessible, thanks to you helping me realize I was forgetting something important, both of these drives seem to have what may be important stuff on them but also seem like it may be duplicated or being a bit new to this it could just be the way its supposed to be.
Click to expand...
Click to collapse
cant mount in CWM I think, At least I never got it to work.
DCIM is your camera pics, the others I wouldn't worry...Looking at your files it seems just fine. Fine just fine.
http://www.youtube.com/watch?v=9aA-1rqtQWs
chjema said:
cant mount in CWM I think, At least I never got it to work.
DCIM is your camera pics, the others I wouldn't worry...Looking at your files it seems just fine. Fine just fine.
http://www.youtube.com/watch?v=9aA-1rqtQWs
Click to expand...
Click to collapse
You are a gentleman and a scholar, thank you very much.
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
BRING BACK A DEAD RCA TAB
Time to set the scene. I had a stock rca tab laying around so I found the thread to a discontinued project on here. I flashed the files and could not get it to boot again. Stuck in an awesome two dog logo. Yay. So after searching a couple days for the stock files I ran across someone comparing this tab to the Cube u25gt-c4y. What do I have to lose. I searched and found the stock files and bam! I had a chinese tablet. Surprisingly it works with just a few flaws. After flashing you will see a nvram error in the wifi. Easy fix. Adb seemed finicky at first but straightened itself out. Screen rotation is also 180 degrees out. You have to tilt it down and lock the rotation. Lastly you have to change the language to english because the default is chinese. Will be trying to get the gps and fm radio working soon.
Step 1.
Install Sp Flash Tool if you have not already. There are many posts on this so I wont repost them.
Step 2.
I used the "Format and Download All" option. I have read dont do it on some threads but I have seen others that said to.
If you want TWRP then rename the file to recovery.img and replace the one in the roms file.
Step 3.
Use Kingroot 4.96.apk and then grab the Super sume to replace the kingroot with SuperSu.
Installing SU from twrp when it asks works fine.
That should be it and now you have a working tab again.
As always USE AT YOUR OWN RISK!!! Nothing to risk though if your tab is already a brick.
Thank you to all the posts I searched to get my tab back working.
https://mega.nz/#F!PY1ExBLB!fns00mTE-hvXsz6sdXdVaA
For the Wifi Nvram WARNING: ERR 0x10 https://forum.xda-developers.com/showthread.php?t=2730486
ADB FIX
So after installing this rom you may have a problem with the adb working. Originally I had this problem and I'm not exactly sure how I repaired it. I believe I had installed multiple "MTP Enabler" programs. After reinstalling I had the problem again and this time found the fix.
Code:
1. Open /data/property/persist.sys.usb.config and change to mtp,adb
2. Open /system/build.prop and add/edit these lines.
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
3. Reboot your phone and wait for the drivers to install. Enjoy.
Installed Wrong Preloader?
Luckily for us we can just open Sp Flash Tool with the correct files then push and hold the Power + Vol Up with the usb connected. After approximately 30seconds it should allow flashing.
jeffmoss1999 said:
So after installing this rom you may have a problem with the adb working. Originally I had this problem and I'm not exactly sure how I repaired it. I believe I had installed multiple "MTP Enabler" programs. After reinstalling I had the problem again and this time found the fix.
Code:
1. Open /data/property/persist.sys.usb.config and change to mtp,adb
2. Open /system/build.prop and add/edit these lines.
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
3. Reboot your phone and wait for the drivers to install. Enjoy.
Click to expand...
Click to collapse
Is your device still working?
leetree2001 said:
Is your device still working?
Click to expand...
Click to collapse
Yes. So far I have found it's hard to kill this unit. I don't have the original firmware but have it working with this firmware where it is usable. Like I stated the worst thing is the screen rotation but all u have to do is lock rotation and it's fine.
Thanks for your response. I have two of the rca6773w22B I will give a try later And post later
leetree2001 said:
Thanks for your response. I have two of the rca6773w22B I will give a try later And post later
Click to expand...
Click to collapse
This is not for the w22B just the w22.
Understand your warning. But had these under the coach
For about a year. And nothing else has poped up on the
Old inter web. Soooo,either this or the trash they go.
I have the 22B version also
leetree2001 said:
understand your warning. But had these under the coach
for about a year. And nothing else has poped up on the
old inter web. Soooo,either this or the trash they go.
Click to expand...
Click to collapse
did this work????
Did it work?
leetree2001 said:
Understand your warning. But had these under the coach
For about a year. And nothing else has poped up on the
Old inter web. Soooo,either this or the trash they go.
Click to expand...
Click to collapse
Im having the same issue looking for a rom for my Voyager 2
Did that sulution work for the w22b version?
Yay my tablet is bricked. Thanks SP flash. frickin crashed
My tablet no longer turns on after I tried SPFlashTools, it started DL process and then timed out. If I connect to windows computer, it makes a connect sound but does not do anything, neither responds to SPFlashTools anymore. Any Idea ?
jeffmoss1999 said:
BRING BACK A DEAD RCA TAB
Time to set the scene. I had a stock rca tab laying around so I found the thread to a discontinued project on here. I flashed the files and could not get it to boot again. Stuck in an awesome two dog logo. Yay. So after searching a couple days for the stock files I ran across someone comparing this tab to the Cube u25gt-c4y. What do I have to lose. I searched and found the stock files and bam! I had a chinese tablet. Surprisingly it works with just a few flaws. After flashing you will see a nvram error in the wifi. Easy fix. Adb seemed finicky at first but straightened itself out. Screen rotation is also 180 degrees out. You have to tilt it down and lock the rotation. Lastly you have to change the language to english because the default is chinese. Will be trying to get the gps and fm radio working soon.
Step 1.
Install Sp Flash Tool if you have not already. There are many posts on this so I wont repost them.
Step 2.
I used the "Format and Download All" option. I have read dont do it on some threads but I have seen others that said to.
If you want TWRP then rename the file to recovery.img and replace the one in the roms file.
Step 3.
Use Kingroot 4.96.apk and then grab the Super sume to replace the kingroot with SuperSu.
Installing SU from twrp when it asks works fine.
That should be it and now you have a working tab again.
As always USE AT YOUR OWN RISK!!! Nothing to risk though if your tab is already a brick.
Thank you to all the posts I searched to get my tab back working.
https://mega.nz/#F!PY1ExBLB!fns00mTE-hvXsz6sdXdVaA
For the Wifi Nvram WARNING: ERR 0x10 https://forum.xda-developers.com/showthread.php?t=2730486
Click to expand...
Click to collapse
What version is this Android OS?
Also: I can't have access to wifi.rar fix file. Where is it?
I am also looking around for stock rom RCT6773W22 (no additional letters or numbers)
I've installed all possible drivers for this tablet.
I physically inspected the USB charging port was not bent and (internally at circuit level) everything is connected, nothing is loose.
When the tablet is off, the device is not seen. But the screen of the tablet shows it is charging from the PC normally.
Windows 10, then proceeds to chime "device disconnected" sound.
If I turn on the tablet, I ask for ADB DEVICES and the tablet is not recognized at all. The tablet stays at logo boot loop.
Maybe I need to install something so the hardware of the tablet grants access to adb commands?
{
"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"
}