My brother attempted to root my Galaxy Tab P6200 (and succeeded), and then tried to run an app which increased pixel density which is when everything went downhill.
Thereafter, I constantly get this message "Sorry! The application Tw Launcher (process com.android.launcher) has stopped unexpectedly." and my tab has been rendered useless for the time being.
I have been desperately trying to flash various packages, right from the Official firmware from here to Clockwork Mod from here.
All to no avail, as I am constantly getting the error as shown below.
{
"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"
}
I am using a Macbook Pro running OSX Lion 10.7.4, Heimdall-Frontend v 1.3.1
I do have access to a Windows machine (running Vista) as well, but there my problem is that the tab is not getting recognised (inspite of installing KIES and Samsung drivers).
Any ideas on how to resolve this? Thank you for your time.
Jambavan said:
My brother attempted to root my Galaxy Tab P6200 (and succeeded), and then tried to run an app which increased pixel density which is when everything went downhill.
Thereafter, I constantly get this message "Sorry! The application Tw Launcher (process com.android.launcher) has stopped unexpectedly." and my tab has been rendered useless for the time being.
I have been desperately trying to flash various packages, right from the Official firmware from here to Clockwork Mod from here.
All to no avail, as I am constantly getting the error as shown below.
View attachment 1227962
View attachment 1227963
I am using a Macbook Pro running OSX Lion 10.7.4, Heimdall-Frontend v 1.3.1
I do have access to a Windows machine (running Vista) as well, but there my problem is that the tab is not getting recognised (inspite of installing KIES and Samsung drivers).
Any ideas on how to resolve this? Thank you for your time.
Click to expand...
Click to collapse
I remember I messed up my tablet using the DPI Changer app when I first got it (I think I tried setting DPI to 170 or 180, I don't remember), but I had already made a backup in CWM which I restored and that fixed the problem.
I don't know whether the following will help or not. Have you used the Play Store on your device to download apps? You could try installing a different launcher (that works at the DPI you set) directly to your device using the Play Store from a web browser on your PC ( https://play.google.com/store?hl=en ). You may need to tap the home button on your tablet to select it/set it as default after it has been installed.
BTW, that CM 9 ZIP you tried to flash should be installed using ClockworkMod (CWM).
It might be worth a try. I hope this helps.
Hi k_t_b, thanks for your reply.
Unfortunately, I am no longer signed in to my account on the tab, and can't seem to sign in either because of the TW launcher problem.
Jambavan said:
Hi k_t_b, thanks for your reply.
Unfortunately, I am no longer signed in to my account on the tab, and can't seem to sign in either because of the TW launcher problem.
Click to expand...
Click to collapse
So, when you visit the play store using a web browser on your computer, signed-in to your account, you aren't able to click "INSTALL" and select your device from the list "SEND TO ANOTHER DEVICE..."? Even if you can't tap the home button on your status bar to select an alternate launcher after installing a different launcher, you should be able to select the other launcher upon rebooting your tablet.
But, If I am understanding you correctly, you signed-out of your google account on the tablet (removed your account or turned off syncing) before you changed the DPI? If that's the case, I suppose my suggestion isn't an option.
If you can get ADB working (you have the Android SDK installed and the USB drivers from Samsung KIES) then you might want to try to pull the build.prop file, edit the DPI value and push build.prop back to your tablet.
Are you able to boot into recovery mode? (With your tablet off, Hold the Volume Up and Power buttons at the same time)
k_t_b said:
So, when you visit the play store using a web browser on your computer, signed-in to your account, you aren't able to click "INSTALL" and select your device from the list "SEND TO ANOTHER DEVICE..."? Even if you can't tap the home button on your status bar to select an alternate launcher after installing a different launcher, you should be able to select the other launcher upon rebooting your tablet.
But, If I am understanding you correctly, you signed-out of your google account on the tablet (removed your account or turned off syncing) before you changed the DPI? If that's the case, I suppose my suggestion isn't an option.
If you can get ADB working (you have the Android SDK installed and the USB drivers from Samsung KIES) then you might want to try to pull the build.prop file, edit the DPI value and push build.prop back to your tablet.
Are you able to boot into recovery mode? (With your tablet off, Hold the Volume Up and Power buttons at the same time)
Click to expand...
Click to collapse
Hi again,
Yes you are right, I am no longer signed in. When I found the tab in its current state, I got into recovery mode and selected 'factory rest'. On rebooting, I found out that I was no longer signed in to my google account, nor could I try to sign back in since at every stage the TW Launcher fails.
Also, as of now, the tab is in Download mode (since I was trying to flash the firmware), and it says something on the lines of "Do not switch off target device". So not sure if I should turn off the tab or not.
Jambavan said:
Hi again,
Yes you are right, I am no longer signed in. When I found the tab in its current state, I got into recovery mode and selected 'factory rest'. On rebooting, I found out that I was no longer signed in to my google account, nor could I try to sign back in since at every stage the TW Launcher fails.
Also, as of now, the tab is in Download mode (since I was trying to flash the firmware), and it says something on the lines of "Do not switch off target device". So not sure if I should turn off the tab or not.
Click to expand...
Click to collapse
Don't worry about that. If this was a phone with a removable battery, then you might remove the battery to get it out of download mode. You should be able to power off this tablet without a problem as long as you aren't in the middle of flashing it.
If you can't use ADB successfully while booted normally or in recovery, then I believe your only option will be to flash a stock firmware with Odin, Heimdall or flash CM 9. If you want to go the CM 9 route, then make sure you flash CWM first ( garyd9's CWM http://forum.xda-developers.com/showthread.php?t=1392348 - you can find instructions in his CWM for the 6210 thread and I think you'll need to have a microSD card to perform this operation ) , then install that CM 9 zip (which you attempted to flash using Heimdall) using CWM.
Thanks once again for your reply, I really appreciate the help. :good:
I will try and use the adb route and reply if I have any luck. Just one thing though, will it make a difference if I am using Linux as a virtual machine? (Ubuntu run via Parallels on a Macbook).
Also, while I agree with each of the three modes suggested by you, as of now I am stuck with both Mac and Windows (running Windows Vista) telling me while using Heimdall that it has "failed to detect compatible download-mode device". Odin on the other hand, doesn't show any signs of the port turning yellow.
I have installed KIES on both the machines, so not sure what the issue is. Also tried the usual restarting and changing USB ports procedures.
I think that with the cmw is possible to install unsigned packages. So is just a question of making a package with a corrected build.prop. the structure of a update package is real simple, look the one on the thread about root.
Just an idea.
Sent from my GT-P6210 using Tapatalk 2
leodfs said:
I think that with the cmw is possible to install unsigned packages. So is just a question of making a package with a corrected build.prop. the structure of a update package is real simple, look the one on the thread about root.
Just an idea.
Sent from my GT-P6210 using Tapatalk 2
Click to expand...
Click to collapse
As of now, my problem is that neither my Mac nor my PC is recognising the P6200 when in "Download" mode. I have installed Kies (on both Windows and Mac), and also the drivers that come with Heimdall (For Windows).
Literally all you have to do is just reflash the Rom in recovery without wiping. Factory reset won't do it. Done it myself a time or 2
Sent from my myTouch 4g via Tapatalk
I finally flashed the stock rom using Odin. Also, I had to install certain drivers for the USB, details of which I will post later.
Sent from my GT-P6200 using xda app-developers app
Related
here is proof. (sorry normal cam is broke so u gotta deal with webcam)
{
"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"
}
Should work for:
Gogear Connect 3 8gb SA3CNT08
Gogear Connect 3 16gb SA3CNT16 (not tested. may need to edit drivers with proper device ids)
Now there are Pre-Rooted custom roms. look at the bottom of the post for a link to the guide.
this is 32 bit only at the moment
on the official Phillips support forum they stated that the developers wouldn't give out the adb drivers, so i used the method found on hikboys thread to make my own.
Now its an actual guide!
1. Put your Connect 3 into "Debug Mode"
a. From the home screen, press the Menu button below the screen.
b. Tap the Settings option.
c. Choose Applications.
d. Select Development.
e. Check the box for USB Debugging to turn it on.
2. Plug in The USB cable
3. After the drivers install, uninstall them in the device manager
4. refresh the drivers and you will see device that says go gear connect
5. install the ADB driver, linked at the bottom of the page, for the go gear connect in the device manager
6. download the newest copy of super one-click from here
7. open super one-click and change the exploit drop down menu to "zergRush"
8. click on the root button and let it do its thing.
9. click OK on the popup to install busybox.
10. after that it may ask you to verify root, allow it to
11. you are now rooted. do a happy dance.
I Have Figured out how to unbrick and flash this device if you have Messed it up while having root privileges. this method can also be used to install custom roms once some are made. if people need the repair/flash method or wanna work on roms let me know in the comments and i will post the files and guides needed for it.
this guide is by mateo1212
Now there are pre-rooted custom roms check out the guide Here
just figured out updating definantly removes the root but you can use the same method to re root.
processor information for the curious=
800mhz arm v7 Cortex A8
Freescale i.MX51 EVK board
very awesome! i just got this for my son for xmas, root will be awesome. so much bloat on this thing.
going to try rooting now. Thanks again.
**edit** i gave this a try and it worked flawlessly. Very happy to be able to remove all of the bloat that comes with this device.
How do I upgrade driver to adb interface? I've rooted other devices and never saw this instruction before. Thanks
I got it rooted. Thanks so much
What I did is uninstall the original driver that installs when you connect the device. After you uninstall, reconnect it to your pc, use the drivers here to allow for adb.
Sent from my LG-P999 using XDA App
hey. im glad my post is helping you guys. i have some thing i would like input on.
1. im in the process of working on a custom rom for this device, should i continue?
let me know. thanks
also if people with the 16gb version can give me there device ids i can make custom adb drivers for your devices also, because this method will work for your devices
Im actually thinking about purchasing this for myself and was a little skeptical until i saw it can be rooted..whats ur opinions on this device? is it worth it? im one click away from ordering. And id definately be interested in custom roms for this.
this is a pretty cool little device. the only thing i have a problem with is the screen size. its a little small for my fat fingers but in the end you get used to it pretty quick. there is a lot of bloatware on it also but after you root you can get titanium backup and remove alot of it. i personally love the songbird music program they have installed. it is soooo much better than the stock music player. some apps dont show up in market but you can always sideload them(downloading the apks to the pc and copying them over to the sdcard then using a file explorer to install them). in all i think if you dont mind the smaller screen it will be a good buy after you root it.
Yea the screen size is what I'm really worried about I've gotten used to the 4inch screen on my phone...I'm torn between this and the galaxy 4.0
Sent from my LG-P999 using XDA App
yea my gf is going to be getting the galaxy player 4.0 around income tax time. she does not like the fact that my mp3 player does not have a camera..lol from what i have seen the galaxy player 4.0 is pretty easily rooted but there isn't any custom firmware for the us version i have only found custom roms for the uk and korean versions.
right now im working on making a rom thats as close to stock AOSP as i can get that includes root and some other helpful software.
im also going to make a custom themed rom with the Espier Launcher as the default launcher and im going to make it clone ipod as much as possible.
the processor is the freescale imx515 so im going to work on compiling my own custom rom from scratch as the hardware is similar to the evaluation board kit. but thats down the road. the first few roms will be based off of the stock rom
i expect my first rom to be out tonight or tomorow during the day
Drivers
When i uninstall drivers, I'm not able to install the new ABD drivers yet, when i uninstall the drivers, the device goes away. When i scan for changes, it installs the stock one, when ii try to update drivers, it says drivers up to date.... any help please.... Thanks
Windows 7 x64 OS
well first off. according to your post you are running windows 7 x64 and this is only for windows 7 x86. to get it working in x64 i need to finish the drivers and then i dont know if you will need to deal with driver signing issues.
if you are doing it in windows x86 make sure to delete the driver that shows up under "universal serial bus controllers" section it will show up as "USB Mass Storage Device" all you have to do is un plug it and plug it back in to figure out whitch one it is. but i repeat if you are running x64 THIS WILL NOT WORK
Fear not though i will soon be posting a few custom roms that are already rooted.
i have 5 in progress now
1 thru 3 are done i just need to gather up the files and write up the guide
1.the stock rom that comes with the device except its rooted and has a few extra utilitys
2.the stock rom that comes with the device except it is stripped of the bloatware and it is rooted and has a few extra utilitys
3.A close to AOSP rom, or atleast the best i can get, with root and a file browser and only the radio app from the normal rom (even has stock android boot screen)
4. A ROM that makes this device loosely imitate the iPod touch
5. totally themed ROM using launcher pro as the default launcher and it will keep the songbird app for music like the two stock ROMs. it will also have root
Ordered one last night now waiting for it to get here...
Sent from my LG-P999 using XDA App
i am uploading the files for the custom roms now
mateo1212 said:
i am uploading the files for the custom roms now
Click to expand...
Click to collapse
did you upload the roms? i need to root my device and flash a new rom, there is so much bloat ont his thing it's crazy
yea i put a link in the bottom of the original post. you do not have to be rooted to flash the custom firmware.
I got it rooted but For some reason no facebook app on it?
Says not supported once i try to update it after i dl'ed it from Snappz, it does not show up on Android Market? I got the SA3CNT08K/37 *gb Model.
yea there is an issue with the market and such for some apps. i have attached the new facebook apk. copy the facebook apk to you sd card and use root explorer to install the apk.
16 gb
I have a 16GB Let me know how I can help..device id's and such.
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.
[Q] Connecting to PC via USB After JB Update gives "Connected As An Installer"
I did the OTA Jellybean update the day it came out and all was well. But now I have an issue when I connect the phone to my computer via USB.
When I first plug it in it says "Connected as an installer" and creates a CD Drive on my computer with the volume name being "Verizon Mobile". An autoplay prompt dialogue appears showing that I can run some executable called ToolLauncher-Bootstrap.exe.
Inside the folder is the Samsung USB Driver installer and some other weird files. In USB mode settings neither mode is checked and if I try to select MTP manually it switches right back to installer. Then after about 10-15 seconds the phone switches over to MTP mode like usual.
So it only works if I let it connect as an installer and wait the 10 seconds for it to switch on it's own. So it still works but is incredibly annoying. Does anyone have any clue what this is? I'm pretty saavy but this has me stumped.
Pictures below:
{
"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"
}
I had this question myself. I wondered why that installer comes up before the media device.
Sent from my SCH-I535 using xda app-developers app
Maybe the Mayan Calendar ending has something to do with it....
I get the same thing, did you run the installer? Maybe its a file manager utility that samsung added to their JB release for better file transfer between phone and pc. Wonder if it will auto MTP once you let the installer finish. It might be a one time deal.
VittoCornelius said:
I get the same thing, did you run the installer? Maybe its a file manager utility that samsung added to their JB release for better file transfer between phone and pc. Wonder if it will auto MTP once you let the installer finish. It might be a one time deal.
Click to expand...
Click to collapse
You should read the original thread. I mentioned that it only connects as installer for about 10 seconds and then switches over to MTP. So it works still it just is incredibly annoying and inconvenient to have to keep waiting every time. Especially since it didn't do this before the JB update.
I've tried running one of the programs and some weird thing pops up from Verizon to install something. But it cuts over to MTP mode before you ever get a chance to do anything.
It's very strange and I think this might have to do with using EZ-Unlock and messing with the bootloader on 4.1.1. I mean I find it odd that it's connecting as an installer for the bootstrap and that's basically what the bootloader is. I bet we'll hear that EZ Unlock needs to be fixed soon.
Doesn't have anything to do with EZ-Unlock or being rooted.
My 535 did the same thing stock.
The same thing happened to me just click the notification then check the mount as media device option and that should get you back to normal.
zaccat4 said:
The same thing happened to me just click the notification then check the mount as media device option and that should get you back to normal.
Click to expand...
Click to collapse
Again I mentioned this already as well in the OP. I really ask that you guys read the entire post. When I go to USB settings and set it manually it switches over to MTP but then quickly goes back to installer. Then it will start the process over again and automatically switch to MTP 10 seconds later on it's own.
Basically I have to let it connect as installer and let it switch to MTP on it's own otherwise it won't stay on MTP mode. Surely someone must have a clue why this is happening? I never had this issue on stock nor rooted ICS regardless of what others have said. It was only when I upgraded to JB. It happened BEFORE I applied EZ Unlock or root now that I think about it.
wushdishmeen said:
Again I mentioned this already as well in the OP. I really ask that you guys read the entire post. When I go to USB settings and set it manually it switches over to MTP but then quickly goes back to installer. Then it will start the process over again and automatically switch to MTP 10 seconds later on it's own.
Basically I have to let it connect as installer and let it switch to MTP on it's own otherwise it won't stay on MTP mode. Surely someone must have a clue why this is happening? I never had this issue on stock nor rooted ICS regardless of what others have said. It was only when I upgraded to JB. It happened BEFORE I applied EZ Unlock or root now that I think about it.
Click to expand...
Click to collapse
Here's the fix. Not sure what all the side effects are, but it definitely kills that stupid installer mode auto mount thing.
(Part of this is from user triggerm8)
1) You'll probably have to unlock the hidden menus by entering *#22745927 in the dialer.
2) Go into the USB I2C Mode Control menu by entering *#7284#.
3) Select Qualcomm USB Options
4) Choose MTP + ADB and save.
Next time you plug in your phone, it will go right to MTP mode bypassing that irritating Verizon install disc mount!
Averix said:
Here's the fix. Not sure what all the side effects are, but it definitely kills that stupid installer mode auto mount thing.
(Part of this is from user triggerm8)
1) You'll probably have to unlock the hidden menus by entering *#22745927 in the dialer.
2) Go into the USB I2C Mode Control menu by entering *#7284#.
3) Select Qualcomm USB Options
4) Choose MTP + ADB and save.
Next time you plug in your phone, it will go right to MTP mode bypassing that irritating Verizon install disc mount!
Click to expand...
Click to collapse
Thanks! :good:
Averix said:
Here's the fix. Not sure what all the side effects are, but it definitely kills that stupid installer mode auto mount thing.
(Part of this is from user triggerm8)
1) You'll probably have to unlock the hidden menus by entering *#22745927 in the dialer.
2) Go into the USB I2C Mode Control menu by entering *#7284#.
3) Select Qualcomm USB Options
4) Choose MTP + ADB and save.
Next time you plug in your phone, it will go right to MTP mode bypassing that irritating Verizon install disc mount!
Click to expand...
Click to collapse
Thanks this worked perfectly. So glad someone figured it out because it was driving me nuts. :laugh:
Averix said:
1) You'll probably have to unlock the hidden menus by entering *#22745927 in the dialer.
2) Go into the USB I2C Mode Control menu by entering *#7284#.
3) Select Qualcomm USB Options
4) Choose MTP + ADB and save.
Click to expand...
Click to collapse
Thanks. I've tried this solution before, but it sort of meets my needs: I select
PTP + ADB
and it connects (directly, bypassing the Installer mode) as MTP.
So, I still need to manually change the connection mode. FYI.
- ooofest
First of all, thank you for reading my post.
I'll try to point out what is going on right now iwith the phone (never saw it happen, ever).
Phone boots but shows a blank (black screen with faded light in the corners) after booting.
After several tries, found out that the 4G is on and receiving notifications (LED is blinking waiting for my response ) and I'm receiving calls nonetheless, so it is working but I can't use the screen.
The screen IS FINE, the boot shows up properly, the fastboot menu shows up properly, sometimes the icons and widgets shows up where they should be, the "Shut down" button shows up properly.
What seems to be the issue is that the upper tray with the time, data, and other things, and the down one with the "◁ ⭘ ▢" menu doesn't shows up AT ALL, so I just receive a blank screen.
Also, the computer isn't finding the phone even if it is connected through the USB cable.
I'm acessing the "Whatsapp" app in the computer right now, which requires the phone to be online and with a internet connection, meaning that the apps are functional and something really weird is happening.
The phone was working fine until last afternoon, just blanked moments after I got out of my house (when I first noticed the issue).
So... anyone willing to crack heads with me trying to figure out what the hell is happening here?
I'll provide pictures soon.
Thanks in advance!
:highfive:
EDIT1: seems to show this "Unfortunately System UI has Stopped" from time to time.
EDIT2: https://youtu.be/AS-wv0NB-g4 (recorded the issue) the 58s shows what i'm talking about.
{
"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"
}
Most likely a firmware issue
xtragen said:
First of all, thank you for reading my post.
I'll try to point out what is going on right now iwith the phone (never saw it happen, ever).
Phone boots but shows a blank (black screen with faded light in the corners) after booting.
After several tries, found out that the 4G is on and receiving notifications (LED is blinking waiting for my response ) and I'm receiving calls nonetheless, so it is working but I can't use the screen.
The screen IS FINE, the boot shows up properly, the fastboot menu shows up properly, sometimes the icons and widgets shows up where they should be, the "Shut down" button shows up properly.
...
Also, the computer isn't finding the phone even if it is connected through the USB cable.
...
EDIT1: seems to show this "Unfortunately System UI has Stopped" from time to time.
EDIT2: https://youtu.be/AS-wv0NB-g4 (recorded the issue) the 58s shows what i'm talking about.
Click to expand...
Click to collapse
Most likely a firmware issue - may be a corruption has developed or could be an incompatible app update (Google Play Services or your launcher?) . Are you rooted? You haven't indicated what ROM you have installed (Stock, custom ...?). Is the recovery stock or custom? Can you enter recovery? Does everything look as it should in recovery? If custom, do you have a recent backup and have you tried running it? The 1045 is the US version I believe - are you sure it's not a 1040 (Canada/Brazil)?
Your best bet may be to install/flash another ROM, either stock or custom. Check out lost101's or vpnair's threads for stock firmware for your phone - they've done an excellent service by providing these ROMS and they are great. I've used both at different times to overcome some issues - may be the best way to go at this stage.
Good luck --- S.
Something caused and error in your firmware, you have to do the following:
1.- Try to backup your files. See if you can connect it to the PC and explore the files from there.
2.- Once backup is done, you have 2 ways:
A) Unlock bootloader, then flashing TWRP recovery, then installing a custom ROM like CyanogenMOD or AOSP.
B) Search and download the stock firmware file, extract the files, and then flashing it to your phone using mfastboot excecutable.
You can find the files and the info here in XDA thread, just do it carefully and read instructions.
If you can't find something say it and I can help, but won't spoonfeed you.
Good luck.
sdembiske said:
Most likely a firmware issue - may be a corruption has developed or could be an incompatible app update (Google Play Services or your launcher?) . Are you rooted? You haven't indicated what ROM you have installed (Stock, custom ...?). Is the recovery stock or custom? Can you enter recovery? Does everything look as it should in recovery? If custom, do you have a recent backup and have you tried running it? The 1045 is the US version I believe - are you sure it's not a 1040 (Canada/Brazil)?
Your best bet may be to install/flash another ROM, either stock or custom. Check out lost101's or vpnair's threads for stock firmware for your phone - they've done an excellent service by providing these ROMS and they are great. I've used both at different times to overcome some issues - may be the best way to go at this stage.
Good luck --- S.
Click to expand...
Click to collapse
Stock and yes, 1045.
I've fixed the issue by restoring the phone through the fast boot (but lost all my data because I couldn't create a backup at all).
Case closed, thanks.
moralesnery said:
Something caused and error in your firmware, you have to do the following:
1.- Try to backup your files. See if you can connect it to the PC and explore the files from there.
2.- Once backup is done, you have 2 ways:
A) Unlock bootloader, then flashing TWRP recovery, then installing a custom ROM like CyanogenMOD or AOSP.
B) Search and download the stock firmware file, extract the files, and then flashing it to your phone using mfastboot excecutable.
You can find the files and the info here in XDA thread, just do it carefully and read instructions.
If you can't find something say it and I can help, but won't spoonfeed you.
Good luck.
Click to expand...
Click to collapse
I'll migrate to the Oneplus 3 soon, but just so you know, I'll root the phone later on, couldn't find the cause of the problem and had to wipe the phone in order for it to work, so that's it, case closes. Thanks.
Good to know ...
xtragen said:
Stock and yes, 1045.
I've fixed the issue by restoring the phone through the fast boot (but lost all my data because I couldn't create a backup at all).
Case closed, thanks.
Click to expand...
Click to collapse
If you run into the issue again at any point, your apps and some data can be backed up to your Google account. Additionally, it is worth rooting your phone and installing Titanium Backup (free) available on Play Store to back up all your data. Once rooted, make sure you backup your phone through recovery and copy the contents on your phone over to your computer from time to time, particularly the recovery backups and the Titanium backups. If you haven't created backups on your computer of all your phones folders in the internal and external divisions on your phone through a USB connection, another solution, in the event you lose USB, is to take out your SD card, insert it in a card reader and create matching folders for both internal and external (SD Card) on you computer and copy all the contents over directly from the card.
Takes a little time but backups can save your ass when needed.
S.
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"
}