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.
Related
I've got a dead bootloader. My device doesn't upgrade thru SD and not with USB. can somebody please help me because i realy don't know what to do. My device is dead for almost 3 weeks now
[edit]
Even my backup on SD doesn't load. And this happend after i downgrade the radio version of the well know greek rom
[/edit]
nobody?
Is there a solution to flash only the bootloader?
I think you need to add some more info, if anyone should have a chance to help. For example what happened when it died - how and why? What happens if you remove the battery cover, replaces it and turns on the device? Text on screen, like USB or Serial? Have you tried uploading ROM from different PCs?
The more info you provide, the more likely it is that someone recognizes your situation from own experience and can provide some help.
HBK said:
I think you need to add some more info, if anyone should have a chance to help. For example what happened when it died - how and why? What happens if you remove the battery cover, replaces it and turns on the device? Text on screen, like USB or Serial? Have you tried uploading ROM from different PCs?
The more info you provide, the more likely it is that someone recognizes your situation from own experience and can provide some help.
Click to expand...
Click to collapse
You are totaly right.
I have update my frvice with the wrong greek rom and now i have the 15 sec reboot thing.
When I startup my device he ends up the bootloader and the only way to get the device booting to windows is remove the battery cover. But the her reboots again after the 15 seconds.
In the bootloader i tried to load my backup with the SD card but nothing happens. I also tried to load a ROM with MaUpgradeUt_NoID but nothing happens. I only get empty version thing.
{
"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"
}
If i use the regular MaUpgradeUt and change the file change.bat for the xda3nbftool I get a error "error 201: get device data error".
I also tried to backup my device with the wrong ROM on it, to look at the header but nothing happens (romupdate.exe).
So my conclusion is that my bootloader is dead. Please correct me when i'm wrong but if this is the case how can i correct my bootloader.
When you unplug your Magician from the USB cable, what do you see?
If you see (with the backlight OFF) "Serial v1.00" or similar, thats a WORKING bootloader.
Make sure you have Active Sync DISABLED (right click the taskbar icon, click "Connection Settings..." the uncheck "Available by USB".
You should then plug in the USB cable and it should change to "USB v1.00" or similar.
Your PC may detect the connection as new hardware - that is a good sign that you have Active Sync disabled.
Let the New Hardware Wizard do it's thing, then re-run the upgrade setup and it should work.
If not, you've got BIG problems.
guess I'm in big trouble
The only thing i can do, is trying a different pc without ASync. On the current pc i'm working on, USB in activesync is disabled.
Are there any posibilties to reload (rebuilt, update) Bootloader.
Can somebody please help me.
The bootloader is built in as it's own ROM, and I've never seen a utility that can make it writeable. I doubt you've destroyed your bootloader, but that doesn't help you - sounds like you'll have to bite the bullet, act dumber than you are, and return it to the manufacturer for a repair - and probably pay for the privilege.
KevinL said:
The bootloader is built in as it's own ROM, and I've never seen a utility that can make it writeable. I doubt you've destroyed your bootloader, but that doesn't help you - sounds like you'll have to bite the bullet, act dumber than you are, and return it to the manufacturer for a repair - and probably pay for the privilege.
Click to expand...
Click to collapse
:shock:
But isn't it strange that if you can't destroy it, it doesn't work anymore? And isn't there somebody who had the same problem?
Before you give up, try this:
Try using another USB cable.
I have experimented many times to realise that the upgrading process does require matching with the right cable.
I noticed that in the screenshot you posted, there is no info on what the device will be upgrade to! I could be wrong, but this may well mean that your device is incompatible with the ROM you are trying to upload.
Try downloading another ROM and give it a go. The best thing would be, if you can find one made specifically for your brand, ie Qtek, I-mate or whatever, and DON'T patch it. Just let the original installer do the job...
Talents said:
Before you give up, try this:
Try using another USB cable.
I have experimented many times to realise that the upgrading process does require matching with the right cable.
Click to expand...
Click to collapse
I'm using the cable that came with my device so that can't be wrong. But i could give it a try.
HBK said:
I noticed that in the screenshot you posted, there is no info on what the device will be upgrade to! I could be wrong, but this may well mean that your device is incompatible with the ROM you are trying to upload.
Try downloading another ROM and give it a go. The best thing would be, if you can find one made specifically for your brand, ie Qtek, I-mate or whatever, and DON'T patch it. Just let the original installer do the job...
Click to expand...
Click to collapse
There isn't a orignal rom fot the dutch T-mobile MDA. And if you use a original installer, it uses ActiveSync. And i can't boot windows because it restarts after 15 seconds so I can't use ActiveSync.
Why can't you use an original ROM updater, if you have the Greek resetting ROM installed? I believe a lot of us has done so without any problems, including me. I don't remember precisely what I did, but it was no problem whatsoever. Most likely I just entered bootloader mode first, to keep the Magician from resetting...
HBK said:
Why can't you use an original ROM updater, if you have the Greek resetting ROM installed? I believe a lot of us has done so without any problems, including me. I don't remember precisely what I did, but it was no problem whatsoever. Most likely I just entered bootloader mode first, to keep the Magician from resetting...
Click to expand...
Click to collapse
I really tried everything but without any results. I realy don't know why i can't use the original ROM updater.
I have the similar problem, but mine one doesnt even start windows. It always go into the bootloader mode and stays there. I try upgrading it, but it gives me communication errors.
Do this
This is what you do.
Disconnect your JAm from USB
Go from your PC , ACTIVESYNC > FILE > CONNECTION SETTINGS > remove the check mark for ALLOW USB CONNECTION TO THIS DESKTOP COMPUTER
Now connect your JAM to your PC again via USB, this time active sync should not start since you have disabled USB
Now double click on the installer file of the original ROM and you should be good to go
After Reset , enable USB ,
Go from your PC , ACTIVESYNC > FILE > CONNECTION SETTINGS > Put a check mark for ALLOW USB CONNECTION TO THIS DESKTOP COMPUTER
MDA dead
I have tried.... it's not responsing as it should be.
I'll gladly donate to the person(s) who resolves, or helps me to resolve this problem. History: The title says it all... 2 weeks ago I rooted my Galaxy S2 Epic 4G TouchEL29 710 Gingerbread from Sprint. This is the second rooted phone I've owned, however the first phone in which I've rooted myself. It took many frusturating hrs to get it right. People don't understand that just because THEY know what they're talking about, I certainly had NO idea as I've never done it before and don't know terms and where to get downloads without correct links. Before I screwed up today I actually rooted a friend's Galaxy S Nexus! Weehoo for me I'm so smart I'll just go an extra step with my own phone today which brings me to...
Problem now: Today I decided to flash a custom ROM. MIUI I believe. I downloaded ROM Manager (I had it on my EVO 4G and it worked well) and as soon as it booted back up it LOCKED. I think I did what ALL first timers are terrified of doing. I bricked my phone. It's STUCK on the Android System Recovery <3e> screen. It has a white triangle in a black background with a yellow ! inside. Under it in red letters it says E: update file is backed up: Reportedted (spelled just like that) under that in yellow it says # MANUAL MODE# --Updating application...
Installing Apks.
Successfully updated application
On the top where it says Enter OK for reboot system now, apply update from sdcared, wipe data/fac reset and wipe cache partition I can scroll through those, but when I choose an option and click the "enter" key, nothing happens, it just stays frozen as though I've done nothing. I took my battery out several times and it goes directly back to this screen upon putting the battery back.
I've spent hours pouring over these (and other) forums and find questions similar to mine, but not exactly. I can get into downloading mode by holding the volume and the on button together. A lot of good it does when I don't know what to download.
I didn't mean to overfill everyone with so much information, but I think in order to get the answers I need, I need everyone to know what I have here. Again, my phone is bricked up. I can't do anything on it. My phone is very important to my job and daily life as I'm certain it is to many people. I shouldn't have been messing with stuff when I don't know what I'm doing, but now I'm relying on other people's kindness and knowledge to get me out of the mess I made. Thank you to everyone who tries helping and as I said before, I will gladly donate a bit of money for your time and wisdom if you're able to help me.
Sarah MN
Hey Sarah, I see you're a new member. In the top right corner of the site, there's a search box that says "Find your device". Type in "Epic 4G Touch" and you'll be able to see all of the sub-forums for your device. Normally, you're supposed to post a question like this in the "Questions & Answers" section, but I'll answer it for you anyways:
Here's what you'll need to flash your phone back to stock:
1. Relax, breathe. All is not lost, I promise you!
2. Download this. It will literally put your phone back to stock EL29 with root (latest Sprint OTA) with one click. Here's a video on how to do it if you're nervous: http://www.youtube.com/watch?v=v7pWjmKCsoc
3. Put your phone in download mode by holding Volume Up and Power when turning on your phone. Hit "Yes" (Volume Up) when you get the warning.
4. Plug your phone into your computer. Your phone should show up in ODIN and the program should look like this after you hit start:
{
"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"
}
As long as u can get into download mode, all is well.
-download Odin on ur computer
-find a stock rom for the epic touch
( hotfile.com/dl/138745617/0615e1c/SPH-D710_SPR_1_20111228163442.zip.html )
-unzip the rom.
-open Odin and fill the fields with the unzipped files. See the file names, and then select appropriately
Phone = xxxx_phone.tar or
Xxxxx_modem.tar
csc = xxxxxxxx_csc.tar
I'm not sure which tar files are present in the above link. If u download and unzip them, you'll be able to figure it out, just as how phone field is xxxxx_phone.tar. if not, just pm me or post it here
Once u fill the fields, put ur phone in download mode and connect it to the computer. Odin will detect ur phone and show a yellow box. Start the process and wait 5-6 minutes till u see a green box saying pass.
This will give u a stock rom, causing u to lose root access. you will have to reroot
All u had to do was go to the reboot option press the volume up then volume down then volume up and volume down and it should start working
Sent from my SPH-D710 using xda app-developers app
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.
I've troubleshooted a lot of things on my Vibrant since 2010, but for some reason I couldn't get it right on the GS4G (and it's embarrassing). I'm not new to Odin, but I get the phone ---- ! ---- pc screen whenever I try to connect to my computer. Yes, I understand that it's another way of the phone being in download mode, but the other variables involved make it difficult to start from scratch again. Here's a list of what I've checked so far:
- 64-bit drivers from http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_4G#FAQ_.28with_answers.29 have been installed/reinstalled multiple times, and the computer (64-bit Windows 7) has been rebooted to make sure
- the computer will not recognize the device no matter what I do; all Odin attempts using files from http://forum.xda-developers.com/showthread.php?t=1480418 have had no effect
- attempts to connect to Odin and have it recognize the phone by showing the yellow COM have ended in vain
- yes, the phone in question is a Samsung Galaxy S 4G and the previous ROM on it was Black Valhalla
Another checklist I constantly read: http://forum.xda-developers.com/showpost.php?p=22234345&postcount=63 . It's basically a repeat of what I've done above. I'm just showing what I've read on how to fix this problem.
I can't even get the one-click program to recognize the phone because of some USB issue. The USB ports are seen fine by the Vibrant in download mode, so it shouldn't be any different for the GS4G. I've used all of the USB ports on this laptop and nothing works.
Any help would be greatly appreciated.
Have you tried thoroughly uninstalling all drivers including for the vibrant and restarting your laptop?
lumin30 said:
Have you tried thoroughly uninstalling all drivers including for the vibrant and restarting your laptop?
Click to expand...
Click to collapse
Yup, that's what I meant by installing/reinstalling. Sorry for being a bit vague.
I was really thorough with the USB drivers.
joe98200 said:
Yup, that's what I meant by installing/reinstalling. Sorry for being a bit vague.
I was really thorough with the USB drivers.
Click to expand...
Click to collapse
Remove them all again. Try the Heimdall One-Click guide in the second link of my signature.
In the notes I link a utility called USBDeview. Use it to double check you have all android and samsung related drivers removed. Make sure you also go into your traditional uninstall programs on your laptop and uninstall samsung drivers from there. Heimdall One-Click has drivers and everything else you need within the program.
lumin30 said:
Remove them all again. Try the Heimdall One-Click guide in the second link of my signature.
In the notes I link a utility called USBDeview. Use it to double check you have all android and samsung related drivers removed. Make sure you also go into your traditional uninstall programs on your laptop and uninstall samsung drivers from there. Heimdall One-Click has drivers and everything else you need within the program.
Click to expand...
Click to collapse
I'm getting this whenever I try to connect. All Android and Samsung-related drivers are removed already, even more thoroughly with the utility program.
{
"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"
}
Edit: I don't see USB Receiver (Interface 0). http://i50.tinypic.com/34ioirr.jpg
Is there something else I should do with these available options? The computer seems to recognize the phone now.
Edit 2: For some odd reason, Odin recognizes the phone before the drivers from the One-Click were installed. I just finished using Odin to go back to stock since the One-Click program wasn't showing the USB Receiver (Interface 0) I was looking for. Before I decided to close everything, I wanted to see what Odin thought. I assume the root of this whole problem was really the USB drivers that I couldn't get rid of without the utility program. Thanks for your help!
I never thought that annoying T-Mobile startup sound would sound so glorious.
Glad you got it.
If you do flash to the "homebrew" ICS ROMs, you'll need the Google USB drivers from the SDK; the Samsung ones won't recognize the phone.
(This applies to Windows only)
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"
}