Hi, I am new to this, but I am learning fast. I have a RCA tablet (rct6378w2) that will not boot. It powers on, but hangs on the RCA splashscreen. I am able to access the recovery system. Wiping the cache and factory reset doesnt seem to fix the problem. Because the tablet powers on and the screen works okay, I feel like there is still hope for the device. I was wondering if someone could list all of the common reasons why a tablet will power on, but not boot into android. Extra credit if you can tell me which possible problems are fixable and which ones are not. Thanks!
jeremyb234 said:
Hi, I am new to this, but I am learning fast. I have a RCA tablet (rct6378w2) that will not boot. It powers on, but hangs on the RCA splashscreen. I am able to access the recovery system. Wiping the cache and factory reset doesnt seem to fix the problem. Because the tablet powers on and the screen works okay, I feel like there is still hope for the device. I was wondering if someone could list all of the common reasons why a tablet will power on, but not boot into android. Extra credit if you can tell me which possible problems are fixable and which ones are not. Thanks!
Click to expand...
Click to collapse
1. ROM is wrong for the tablet
2. Tablet has no ROM installed
These are the issues possible for you as you say you wiped and factory reset the tablet but did you re-install the ROM afterwards ?
TechMinerUK said:
1. ROM is wrong for the tablet
2. Tablet has no ROM installed
These are the issues possible for you as you say you wiped and factory reset the tablet but did you re-install the ROM afterwards ?
Click to expand...
Click to collapse
Thanks for the response. Well, to give clarity as to when the problem began, this is what happened. I was doing normal things on my tablet, and it seemed to lag really bad. As I tried to press the home button once or twice, I saw some strange lines on the screen as it faded (kind of like when a battery dies). Then the device restarted and hung on boot. After rebooting a few times, I then tried to wipe the cache with no success. After this, I did the factory reset. I know that it cannot be the wrong ROM, but I wonder if somehow the files were corrupted or if the storage unit could have failed. Anyways, according to various instructions I have seen online, I thought that doing the factory reset would restore the original factory rom image? Am I incorrect?
jeremyb234 said:
Thanks for the response. Well, to give clarity as to when the problem began, this is what happened. I was doing normal things on my tablet, and it seemed to lag really bad. As I tried to press the home button once or twice, I saw some strange lines on the screen as it faded (kind of like when a battery dies). Then the device restarted and hung on boot. After rebooting a few times, I then tried to wipe the cache with no success. After this, I did the factory reset. I know that it cannot be the wrong ROM, but I wonder if somehow the files were corrupted or if the storage unit could have failed. Anyways, according to various instructions I have seen online, I thought that doing the factory reset would restore the original factory rom image? Am I incorrect?
Click to expand...
Click to collapse
Depends, if it's a custom recovery it could wipe everything
TechMinerUK said:
Depends, if it's a custom recovery it could wipe everything
Click to expand...
Click to collapse
Thanks for the response. I have only used the regular stock recovery that is preloaded on the device (I think it's called Android System Recovery 3e. To my knowledge, I don't believe there are any working custom recoveries for this device. It seems that doing the factory reset is normally the way to go to fix OS issues on this device. However, when the factory reset process is successful (as far as going through the process is concerned), but it does not fix the issue, it makes me wonder if the factory recovery image is corrupt or something. Any ideas? Also, if the device turns on and I can navigate through the recovery options and even use ADB, do you think the hardware is still good? If so, then it would be a software/firmware problem... right?
I would simply like to get the device working. I don't care whether its a stock recovery or custom recovery, stock rom or custom Rom. I just want to use the device again and not have to throw it in the garbage. Do you have any ideas how I can get it going?
One other thing, I just don't understand why it's so difficult to restore a tablet. A PC is ultra easy to fix by using a self-booting recovery disk or a live linux iso. Perhaps someone can explain to me why it seems to be impossible to find a working rom anywhere for this device.
jeremyb234 said:
Thanks for the response. I have only used the regular stock recovery that is preloaded on the device (I think it's called Android System Recovery 3e. To my knowledge, I don't believe there are any working custom recoveries for this device. It seems that doing the factory reset is normally the way to go to fix OS issues on this device. However, when the factory reset process is successful (as far as going through the process is concerned), but it does not fix the issue, it makes me wonder if the factory recovery image is corrupt or something. Any ideas? Also, if the device turns on and I can navigate through the recovery options and even use ADB, do you think the hardware is still good? If so, then it would be a software/firmware problem... right?
I would simply like to get the device working. I don't care whether its a stock recovery or custom recovery, stock rom or custom Rom. I just want to use the device again and not have to throw it in the garbage. Do you have any ideas how I can get it going?
One other thing, I just don't understand why it's so difficult to restore a tablet. A PC is ultra easy to fix by using a self-booting recovery disk or a live linux iso. Perhaps someone can explain to me why it seems to be impossible to find a working rom anywhere for this device.
Click to expand...
Click to collapse
Unfortunatley because it's not a common brand of tablet not many developers are working on creating ROMs for it
Related
Whenever I try to boot into recovery (vol up and power), I get a blue screen with no text or options. It's supposed to give me an option so that I can mod my phone. I have CWM recovery, and I followed the instructions right. I'm not sure why I continue to see a screen with no options. Any help would be appreciated.
Can anyone help me with this? I know the Impulse isn't a very popular phone, but someone has to know something that relates to this (it's pretty much the same as the Ideos X5, I believe). I could really use some help.
I changed the OP to hopefully narrow the problem down for anyone reading. Maybe it'll be easier to read and help with that way.
Are you sure that you flashed the right recovery for your phone?
MissionImprobable said:
Are you sure that you flashed the right recovery for your phone?
Click to expand...
Click to collapse
Yeah, that was the problem. I was able to load the rom, which led to another problem: can't get pass the at&t screen. Doing a factory reset doesn't do anything either. I had my apps and my system data backed up on titanium, so will that help me at all to restore my phone (I can only boot recovery)? Is there anything I can do, or did I brick my phone trying to load this rom?
jlm990 said:
Yeah, that was the problem. I was able to load the rom, which led to another problem: can't get pass the at&t screen. Doing a factory reset doesn't do anything either. I had my apps and my system data backed up on titanium, so will that help me at all to restore my phone (I can only boot recovery)? Is there anything I can do, or did I brick my phone trying to load this rom?
Click to expand...
Click to collapse
In your case i would go back to stock firmware and you will be good to go
And then do it all again and maybe some went wrong during installation on your phone
Cheers
Hi there,
I need some help here. My wife's Sprint Nexus S is acting up - keep popping messages such as "Unfortunately XXX has stopped." So I decided to do a hard reset. I followed the instructions but weirdly the phone did not do it. It acted like doing the hard resetting but then rebooted with nothing changed. I tried both the software way - Settings, factory reset, and the hardware way - Vol up button + Power, then recovery, then Vol up + Power again at the Android with exclamation image, chose "Wipe all data and factory reset." However, the phone boots with nothing changed.
Can anyone help me with this? What else can I try?
Thanks much in advance.
<DELETED>
You could try fixing the permissions on the files through Rom Manager; it fixes a lot of Force Close generally.
kwudude said:
Have you tried installing a custom recovery and doing a hard reset through that route yet? E.G. ClockworkMod or TWRP
Click to expand...
Click to collapse
Thanks. I will give it a try. Can you point me to some instructions / files for downloading, etc.?
Cpu.gastronomy said:
You could try fixing the permissions on the files through Rom Manager; it fixes a lot of Force Close generally.
Click to expand...
Click to collapse
This one is actually the Sprint stock rom untouched. So... no Rom Manager on it. Thanks anyway. I guess a custom recovery is the only way to go now...
<DELETED>
I wouldn't install a custom recovery, and ultimately technically void your warranty, for the sole purpose of resetting it though...
Just use a one click root tool, it flashes superuser, cmw, but keeps the rest of the (stock) rom you're on!
---===:::Greetzz, jojoost:::===---
Sent from my iPad using Tapatalk HD
Thanks to you all for all the good suggestions. I have tried several things but did not succeed.
1. Flashed a clockworkmod recovery. That was successful. So I went ahead to use its factory reset function. The process completed without error but once rebooted, the phone remains the same as before.
2. Connected the phone to a PC, turned on USB storage, copied a ROM image zip file to a folder. Then tried to install it through Recovery. But the file I copied was nowhere to be found.
3. Put then phone into the bootloader mode, connected to PC, use fastboot to flash boot, system, recovery, userdata, radio image files. All went through with any issue. Rebooted, phone is the same.
In short, whatever I do, the phone remains the same. No changes can be made.
I also tried the one-click tool but could not proceed ahead. It required USB debugging turned on. I turned it on, the check mark was there, but it was really NOT turned on because on the PC, the message is that it is not on. On the phone, if I switch to a different application, or simply go back one step, and then go to developer option, the checkmark was not turned on.
It feels like the internal memory/storage becomes read-only. No changes can be made. I am not sure if the hardware is bad, or some permission issue.
Any ideas that I should try next?
From what I read and understand, I think I had a bad nand problem. Guess time to let the phone go RIP.
I've been scouring the Googlenets for days now trying to figure out how to fix this, and nobody has either had the exact same problem I have (doubtful), or no one has posted it.
I'm currently running CM10 and Android 4.1.2. I was planning on upgrading to lollipop via http://forum.xda-developers.com/eee-pad-transformer/development/rom-t2942560, but somehow my recovery stopped working. I had TWRP 2.3 and was going to upgrade to 2.8 (as recommended), and that's where something went wrong. I'm not exactly sure what I did, or what step I was on when it happened, but I rebooted the tablet and ended up with a never ending Asus splash screen. POWER + VOLUME DOWN to access recovery didn't get me anywhere but the same splash screen with some white text promising a recovery that would never come.
I tried APX flashing with Easy Flasher to no avail. I tried POWER + VOLUME DOWN, wait, then select wipe. Nothing. When I POWER + VOLUME DOWN, and wait, I can boot into CM10 just fine and everything appears dandy. That's when I tried Factory Reset in the settings. Still nothing!
Am I being dumb? Any help or even just some empathy would be great about now. What should I do?
Thanks in advance.
bump for luck...
I'm guessing this is a new problem and the device is too old to tinker.
I would suggest returning to stock and starting over again.
barkeater said:
I would suggest returning to stock and starting over again.
Click to expand...
Click to collapse
By returning to stock do you mean factory reset? My problem is I am unable to factory reset. Do you know another way to factory reset that I didn't try? Thanks.
I had a little time to mess around with this again, but unfortunately I didn't succeed. I tried using EasyFlasher from this post: http://forum.xda-developers.com/showthread.php?t=1688012. It taught me that the difficulties continue. It would appear tat I am not able to turn on APX mode, as I get no connection after holding power and volume up for what seems like an eternity.
I also started to wonder if something is wrong with my partitions. When I look at storage in settings, it says I have 13 GB total space, but when I add up the apps, pictures, audio, downloads, and available, it only ends up at 4 GB. That's weird.
Anyone out there have any ideas? Thanks.
ZachTMartin said:
I had a little time to mess around with this again, but unfortunately I didn't succeed. I tried using EasyFlasher from this post: http://forum.xda-developers.com/showthread.php?t=1688012. It taught me that the difficulties continue. It would appear tat I am not able to turn on APX mode, as I get no connection after holding power and volume up for what seems like an eternity.
I also started to wonder if something is wrong with my partitions. When I look at storage in settings, it says I have 13 GB total space, but when I add up the apps, pictures, audio, downloads, and available, it only ends up at 4 GB. That's weird.
Anyone out there have any ideas? Thanks.
Click to expand...
Click to collapse
Sounds like your OS is still loading? If so you might try this apk. "Reboot2Recovery" if that gets you into recovery you can flash the new twrp from there.
No luck. It boots to the never ending Eee Pad splash screen, which is the same screen it hangs on if I reboot normally.
ZachTMartin said:
No luck. It boots to the never ending Eee Pad splash screen, which is the same screen it hangs on if I reboot normally.
Click to expand...
Click to collapse
Anything here help you?
http://www.transformerforums.com/fo...-recovery-kernel-need-help-desperately-2.html
or here
http://www.transformerforums.com/fo...ogo-screen-keeps-restarting-eternal-loop.html
Stock firmware is still avaialble
http://www.asus.com/ca-en/support/Download/28/1/0/1/32/
None of them had an answer to my problem. When I do the volume down + power I get the two icons, wipe and cold boot. Wipe doesn't do anything and the other option puts me back in my OS.
I really think it's something to do with my partitions, but I haven't been able to find anything to fix it. Is there a way to reset my partitions without APX? I can't seem to APX either.
ZachTMartin said:
None of them had an answer to my problem. When I do the volume down + power I get the two icons, wipe and cold boot. Wipe doesn't do anything and the other option puts me back in my OS.
I really think it's something to do with my partitions, but I haven't been able to find anything to fix it. Is there a way to reset my partitions without APX? I can't seem to APX either.
Click to expand...
Click to collapse
When I read your problem again t seems that you have CM10 installed with stock recovery? Must be due to failed install in your first post.
Did you try the firmware download from the asus link above? Wonder what happens if you copy to system and if cm10 would recognize it as a system update ans install.
http://www.asus.com/support/FAQ/1011948/
Watch out for asus's zip in a zip.
I dusted this off with the long break. Tried to install the Asus firmware and ended up hanging on the load screen again. I'm starting to think it must be something with my bootloader, but I can't seem to figure out how to get in there.
This is probably a lost cause at this point. Thanks for the help.
Happy new year!
Edit:
I decided not to give up and ended up getting recovery back! Woohoo! I'm not really sure exactly what the problem was, but I was looking here (http://blog.chazomatic.us/2013/10/27/updating-and-rooting-an-asus-transformer-tablet/) and it looks like the following fixed it:
Code:
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /dev/block/mmcblk0p4 /data/local/tmp
I'm still not sure why, but now it boots normally and goes into recovery just fine. :good:
First of all, I'm pretty noob this days on Android so I'm very sorry guys, also english is not my first language.
My nexus was working great until today. I ended a Whatsapp Call and get a black screen, phone looks frozen (happened before). Reboot it and works fine for 5-10 minutes, after that it started to reboot itself the whole time in bootlop, stuck in the rom intro, after the Google text. My rom is one of the very first roms from Slim Roms, I'm sorry I don't remember the Android Version, but is "old".
I can access to the recovery mode tho. I tried to wipe dalvik cache and the TWRP failed, wipe and factory reset, fail as well... I don't know what else to do. I don't have any image to install in the sd, or any backup. Windows 10 recognize an "android" but can't access to it so I can't copy any file to it.
Is my phone dead or can I do something? I love this phone :crying:
Any help please? I tried using ADB and get to copy some files into the phone but still every time I try to do a wipe cache, factory reset or what ever I get a Unable to mount Data / Cache / Storage... every time the same error.
I google it and found that some people could fix that error by repairing the file system and select ext4. But I can't do that, my TWRP build is quite old (v2.6.3.4) and doesn't have that option here. Any suggestions?
Thanks btw
Me again
I've been reading forums for more than 7 hours today and trying different solutions, and nothing. But found this guy here https://androidforums.com/threads/is-my-nexus-5-dead.1099076/
He basically had the same issue as me few years ago, exactly the same, He didn't find any luck apparently.
How is it possible that a phone that can get access to TWRP or copy/flash files via ADB/Fastboot can't be saved? Theoretically in this case this is not a hard bricked, right? So? This is so so weird
It's possible that portions of the internal memory are damaged.
The only thing left to try is flash a stock ROM using ADB commands. I recommend trying a KK ROM.
No OS but twrp working
Hello friend.
If I have understood your problem correctly then you have twrp working but no os.
I found that there is an option in twrp to enable MTP. once you do that you will be able to access it. While the phone is in recovery mode connect it to the computer and it will get recognized and you can transfer zip file to it and then flash a new os.
Cheers!
audit13 said:
It's possible that portions of the internal memory are damaged.
The only thing left to try is flash a stock ROM using ADB commands. I recommend trying a KK ROM.
Click to expand...
Click to collapse
I tried that already, it does the installation thing but always fail in the end
mevrik_007 said:
Hello friend.
If I have understood your problem correctly then you have twrp working but no os.
I found that there is an option in twrp to enable MTP. once you do that you will be able to access it. While the phone is in recovery mode connect it to the computer and it will get recognized and you can transfer zip file to it and then flash a new os.
Cheers!
Click to expand...
Click to collapse
Also tried that: new rom+ gapps via usb adb and the TWRP says Failed...
I mean I still have OS because every single time I try to turn on my phone the animation screen of the Slim Rom goes in. The problem is I can't install anything new, no new rom, no factory image, no new version of TWRP, I can't wipe data or cache or do a factory reset because I get a big red Failed always. Feelsbad
ekeixdurden said:
I tried that already, it does the installation thing but always fail in the end
Also tried that: new rom+ gapps via usb adb and the TWRP says Failed...
I mean I still have OS because every single time I try to turn on my phone the animation screen of the Slim Rom goes in. The problem is I can't install anything new, no new rom, no factory image, no new version of TWRP, I can't wipe data or cache or do a factory reset because I get a big red Failed always. Feelsbad
Click to expand...
Click to collapse
Try this: lock the bootloader and reboot back into the bootloader. If the bootloader remains locked, that's a good sign. If the bootloader is unlocked, that is a bad sign.
audit13 said:
Try this: lock the bootloader and reboot back into the bootloader. If the bootloader remains locked, that's a good sign. If the bootloader is unlocked, that is a bad sign.
Click to expand...
Click to collapse
I tried that with the Nexus root tool kit and the bootloader still is unlocked
ekeixdurden said:
I tried that with the Nexus root tool kit and the bootloader still is unlocked
Click to expand...
Click to collapse
Tells me that the memory chip is defective and needs to be replaced.
Indicates to me that the chip had lost its write capability.
audit13 said:
Tells me that the memory chip is defective and needs to be replaced.
Indicates to me that the chip had lost its write capability.
Click to expand...
Click to collapse
Shieeeet... So nothing to do I guess? I already ordered a new phone but if I can save this beauty would be great
It would be great to fix it but the simplest solution may be to buy a nexus 5 with a smashed screen and working motherboard. I've done this before and it's worked out well because the nexus 5 is pretty old by today's phone standards so I got it cheap.
hmm not a bad idea at all. Thank you!
Hello
my sister's phone somehow broke down. It's not rooted or anything, was use for mainly day to day use. She called me yesterday that her phone randomly resets (like 1x per hour).
I plugged phone to computer, wanted to transfer pictures and "important" data to pc and during the transformation phone closed and I am unable to open it again. I managed to transfer around 60% of pictures but mostly important ones so the loss is not that big.
-phone started "looping" at start screen logo to samsung for like 30minutes. After a while it somehow booted into the system and I tried to do software update. Downloaded the update and then installed it but at some point phone closed down and started looping loading screen again. Since then im unable to boot it into the system....
-I entered recovery mode and did Factory reset. Doesnt help. Wiped cache, doesnt help.
-i know little to nothing about android but my guess is that i somehow bricked the system when i did factory reset just when the phone was updating?
is there any solution to somehow "install" fresh android on the phone via PC? Phone is not rooted but it has activated USB debugging options.
****EDIT***
I was thinking that it could be hardware issue but phone can stay open in recovery mode for hours so I suppose it is software problem?
Phone is still under warranty but i cba dealing with services and would rather fix it myself.
Thank you for any help
You should simply done a factory reset.
It will need reflashed. In the long run it may be best to let Samsung hash it out.
Yeah i should've done factory reset while phone was still usable. But I wanted to recover all of the photoa, thats why i tried to do system update first....
dehumless said:
Yeah i should've done factory reset while phone was still usable. But I wanted to recover all of the photoa, thats why i tried to do system update first....
Click to expand...
Click to collapse
Updates don't help especially in this case where the OS was teeter toddling on the abyss. Safe mode. The first mistake was not having the critical data redundantly backed up. All you can do is learn from the mistakes.
blackhawk said:
Updates don't help especially in this case where the OS was teeter toddling on the abyss. Safe mode. The first mistake was not having the critical data redundantly backed up. All you can do is learn from the mistakes.
Click to expand...
Click to collapse
well, right now im trying to find android firmware images and will try to flash them on with Odin later.
But I am sure that i will face several problems on the way
dehumless said:
well, right now im trying to find android firmware images and will try to flash them on with Odin later.
But I am sure that i will face several problems on the way
Click to expand...
Click to collapse
You can use SmartSwitch to do that, but I'm a total novice at flashing Androids and the best method. Pick and use the safest method...
A Samsung Experience center at Best Buy can also do it. They might be able to give you more insight as to why it failed.