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.
Related
Well I think I'm gonna be sick....
Help me please. I killed my baby!!!!!
ohhh maybe not ok I won't freak. I took the risk.
Sorry bout that just whinning out loud. Here is my sotuation. I wanted to upgrade my rom to mario's 9.6 over at ppcgeeks. I thought I followed all the rules but I got stuck in the bootloader mode I think. All I get is a dark screen that says serial when not connected to cable or usb when it is. (oooooooooh its bad it hurts) Ok, I disconnected it from comp tried to launch the rom exe after I sft reset. It went to bootload and nothing works now no sft or hrd reset. Did I kill her? ( It really hurts. Please say it aint so. Ill tack it all back) I'll stay away from rom updates forever !!! Just give her back to me un harmed)
There's a tutorial for Stuck In bootloader somewhere... please search...
For thoose who stuck in bootloader this is how to unstuck:
1. Get Mtty here:
http://rapidshare.com/files/28321691/mtty1.42.zip.html
2. Right Click Activesync icon in tray, and select connection setting, then un-mark Allow USB connections at Activesync Connection settings.
{
"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"
}
3. Extract the zip file and Run mtty.exe and select USB from the Port dropdows list and then click OK button.
4. press Enter two times for showin USB>
5. Type:
set 14 0
[ENTER]
task 8
[ENTER]
(for soft-reset).
6. Ur device should reset and u might close mtty utility.
7. Done.
ur device should be just fine... if not try to re-flash the OS again while in Bootloader (press and hold POWER+RECORD button then press RESET)
re-enable/re-mark Activesync after this proccess might necesarry, to allow USB Connection again for enablin Activesync ur pda with ur PC.
u r the best man..
hugi
Praise you Helmi!!!
You are AWWWWsome. I followed your instructions and my baby lives.
I am stuck with mario 9.6 rom but that ain't bad compared to a bricked phone.
I am interested in how to cook my own rom. I'm gonna keep readin though cause I apparently have a lot to learn.
our hero
Helmi_c is my hero.
Damn Helmi_c you saved my phone
Seriously Stuck
Helmi...
I'm in the same boat except I cannot use mtty because I do not have an option for USB, only COM1 and 2......I also tried another utility I found on ppcgeeks called uni_exitbootloader without success. The details can be found here:
http://www.ppcgeeks.com/cant-update-rom-now-stuck-in-bootloader-t7982.htmlhttp://www.ppcgeeks.com/cant-update-rom-now-stuck-in-bootloader-t7982.html
My question is What can I do now???
Any thoughts....Anyone?????
GOD BLESS YoURE HART OMGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGG URRRRRRRRRRRA GENIOSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
tip for Mac OS X
I tried several times to run the mtty.exe program without success. I was running WinXP inside Parallels and each time I connected the PPC6700 to the Mac, Parallels told me that another program was using the PPC6700. After acknowledging that message mtty would not show me a USB connection.
Finally I hit on the idea of rebooting my Mac and booting directly into Windows (I used BootCamp to create a separate Windows partition). Obviously this way, Parallels was not involved. mtty immediately showed me a USB option, and 10 seconds later my unit was rebooting successfully.
Many, many thanks! Un abrazo muy fuerte!
S
same thing
im not seeing usb what should i do im using windows xp
Stuck too
I don't know if this is related but a I had no response from my xv6700 so I hooked it up and it would reboot over and over to the white Verizon screen. Later it gave just a white screen with an off-white "skunk line" down the screen. Now It doesn't reboot and I have just a red blinking light. I tried popping the battery when this first started with no luck as well as a hard reset using option 3 (2 function keys and pin-hole reset).
I turned USB connections off in my Vista Mobile Device center but I still don't get a USB option in mtty.
Is there anything I can do or is it bricked?
Thanks for the great forum!
I have since moved on to the titan, but it is very difficult to brick these phones. Can you get into bootloader? if i remember its camera + power + soft reset button (i think), once in that you can flash a new rom like the verizon stock to get back to basics. you should be doing this all in XP, not vista. I think some people could, but i never flashed in vista, xp was tried and true and never failed me (only reason i still have my crappy laptop with XP!)
Thanks
Thanks for the reply Friguy33. Somehow, a miracle I think, it started to come back with the initial setup but it still reboots itself throughout the process and after. The battery is drained and it reports that once the today screen comes up but instead of just starting to charge it, something else I think causes it to reboot.
Prior to reboot the screen dims about 40%. I tried those three buttons but nothing new has happened and no boot loader screen. I don't understand why it keeps rebooting.
helmi_c said:
There's a tutorial for Stuck In bootloader somewhere... please search...
For thoose who stuck in bootloader this is how to unstuck:
1. Get Mtty here:
http://rapidshare.com/files/28321691/mtty1.42.zip.html
2. Right Click Activesync icon in tray, and select connection setting, then un-mark Allow USB connections at Activesync Connection settings.
3. Extract the zip file and Run mtty.exe and select USB from the Port dropdows list and then click OK button.
4. press Enter two times for showin USB>
5. Type:
set 14 0
[ENTER]
task 8
[ENTER]
(for soft-reset).
6. Ur device should reset and u might close mtty utility.
7. Done.
ur device should be just fine... if not try to re-flash the OS again while in Bootloader (press and hold POWER+RECORD button then press RESET)
re-enable/re-mark Activesync after this proccess might necesarry, to allow USB Connection again for enablin Activesync ur pda with ur PC.
Click to expand...
Click to collapse
OMG!! it worked. Thank you so much. You are the best!!
Maddddd LOVE!!!
I Love Helmi_C
forgetting
you are forgetting to go into activesync and shut off the usb connections, then unplug your apache, then reboot the apache, plug it in, then rerun mtty. you dont have to reboot the apache, but i have always found it to be best.
This still isnt working for me. I tried the way on ppcgeeks too. =/
I, I can´t too.
I connect, usb are there, but when i go for 4 step, on program show "Cmd>" not "USB>"... USB show only title of window... i put step 14 0 fornt Cmd, shoe again Cmd and after put Task 8 and show invalid command!
Someone can help me?
I, I can´t too.
I connect, usb are there, but when i go for 4 step, on program show "Cmd>" not "USB>"... USB show only title of window... i put step 14 0 fornt Cmd, shoe again Cmd and after put Task 8 and show invalid command!
Someone can help me?
The easiest way to get outa bootloader is to hard reset a few times (it's gonna go back into to bootloader each time) then disable your ActiveSync/Windows Mobile Device Center USB connections and re-flash. Works for a wuite a few people I know. Give it a try.
Hello guys,
I've bought myself a secondhand I-mate Jam with a French Rom on it which I offcourse want to change.
After trying many many I just don't seem to work. I think I never got in the Bootloader mode (hold Camera button + power button and then press the reset button) but when I do this my screen just turns black and nothing happens.
If I try to start up everytime I get the startup wizard with pen calibration. Then he goes to windows and starts with the customization untill the screen goes black again and I can't do anything. If I want to powerup again I need to slide the battery cover back and forth and then I can powerup again. Only just to get the startup wizard again.
Please help me with this. I'm going crazy with trying and trying.
Cheers,
Veek
After more searching and trying I finally got the HTCMAG_ROM_WWE_O3 from Cotulla installed. Only my radio isn't the good version.
So trying to go back to older rom with good radio and then install HTCMAG_ROM_WWE_O3 again.
And I think with I-mate the bootloader is just a black screen. I still keep getting a black screen when I try to acces bootloader mode.
Cheers,
Veek
bootloader mode on htc magician marked with a black screen and there are writings SERIAL or USB (if connected with USBSync) at the top center of the screen, while the bottom of the screen are made V1.xx (bootloader version)...
I think i have your same problem! it keeps rebooting and everytime i try to install a new radio version it turns to boot mode (or almost that should be usb + 1.0 ) and nothin happens... i want to give him life back! =(
Geko90 said:
I think i have your same problem! it keeps rebooting and everytime i try to install a new radio version it turns to boot mode (or almost that should be usb + 1.0 ) and nothin happens... i want to give him life back! =(
Click to expand...
Click to collapse
try reflash Radio Rom again ! for smooth and successful flashing process should remove the SIM card from your device
Installation:
- Extract files Radio Rom
- Enter bootloader mode on device (Press POWER + CAMERA + RESET, you will see Serial/USB at top and 1.0X at bottom)
- Connect via USB to PC
- Run MaUpgradeUt_noID.exe
- Follow instructions in Update program.
- At the end you should see at device screen: "100% Upgrade Radio Image Complete".
- After flashing press reset.
Hakim Rahman said:
try reflash Radio Rom again ! for smooth and successful flashing process should remove the SIM card from your device
Installation:
- Extract files Radio Rom
- Enter bootloader mode on device (Press POWER + CAMERA + RESET, you will see Serial/USB at top and 1.0X at bottom)
- Connect via USB to PC
- Run MaUpgradeUt_noID.exe
- Follow instructions in Update program.
- At the end you should see at device screen: "100% Upgrade Radio Image Complete".
- After flashing press reset.
Click to expand...
Click to collapse
I'm trying to do this, but something's wrong... when I run maupgradeut_noID.exe the window says the ppc has to be connected via usb and synced with active sync... issues start after clicking on "Upgrade", because the phone goes in boot mode and nothing more happens... only that less than a minute later the pc loses connection of the phone =(
Geko90 said:
I'm trying to do this, but something's wrong... when I run maupgradeut_noID.exe the window says the ppc has to be connected via usb and synced with active sync... issues start after clicking on "Upgrade", because the phone goes in boot mode and nothing more happens... only that less than a minute later the pc loses connection of the phone =(
Click to expand...
Click to collapse
if so, then try to disable connections Ms. ActiveSync on your PC
open Ms ActiveSync --> File --> Connection Settings --> do not check column Allow USB connections
Hakim Rahman said:
if so, then try to disable connections Ms. ActiveSync on your PC
open Ms ActiveSync --> File --> Connection Settings --> do not check column Allow USB connections
Click to expand...
Click to collapse
I'm going to try it! Finger crossed for me xD
tryed... if I uncheck "usb connection", the pc doesn't recognize the ppc at all =(
that's what I get when trying to upgrade radio or rom
{
"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 sync it it shows me the pocketpc disk in "computer" and I can explore it... is it someway useful? also, when synced, I get this window (trying to update):
now... do you think there is still some possibility for my magician to wake up from this long sleep?
THANKS
Geko90 said:
I'm going to try it! Finger crossed for me xD
tryed... if I uncheck "usb connection", the pc doesn't recognize the ppc at all =(
that's what I get when trying to upgrade radio or rom
If I sync it it shows me the pocketpc disk in "computer" and I can explore it... is it someway useful? also, when synced, I get this window (trying to update):
now... do you think there is still some possibility for my magician to wake up from this long sleep?
THANKS
Click to expand...
Click to collapse
even if you uncheck the " usb connection " and the pc does not recognize the device, however the upgrade process is still running
Hakim Rahman said:
even if you uncheck the " usb connection " and the pc does not recognize the device, however the upgrade process is still running
Click to expand...
Click to collapse
Hi,
i'm experiencing the same problem. I have never been able to access the bootloader by pressing those 3 buttons. The device just freezes and i need to remove the battery in order to reset it. Others also have experienced the same problem. Why won't the bootloader show up?
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.
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"
}