Related
So starting from beginning, while playing some music, my A700 reboot and hang up in infinite loop of Acer and Iconia Tab logos. As Vol+Power was not responding, I sent it back to Acer for repair and received it back yesterday after they replaced motherboard (and microphone!?).
Cool.
But no, because after a couple of hours of re-installing, it reboot and finished in the same Logos loop, just after selecting Airplane mode.
So my question, can I re-flash this A700 with a complete clean stock ROM, as I have only access to Fastboot mod?
To reflash with fastboot, you'd need an unlocked bootloader. I wouldn't risk that if I were you.
It looks likes a hardware issue. A ROM contains drivers. Drivers control the hardware. When going into airplane mode, the drivers shut down some of the hardware components, like WIFI and Bluetooth. If you'd have a modded ROM, I'd say there's some driver issue which causes the tablet to crash (weird that it's stuck on bootloop, though). Since that's not the case, I'd say there's something wrong with your hardware.
To apply factory settings, did you do the right moves?:
http://forum.xda-developers.com/showthread.php?t=1861092
How did you enter fastboot mode?
Note that there's only a slight difference in going into fastboot or the factory reset mode. It's only a Vol + and -.
I was asking because I already flashed (in November) my 'previous' A700 with a stock ROM (because JB OTA update failed) without unlocking anything (but using Recovery).
You are probably right, it may be an hardware fault as it does exactly the same as first time and that Acer Support replaced complete motherboard. However it was looking at me very strange that I could get two hardware fault in the row.
I will give a try to the factory reset (I did not knew the move), thanks for the tips.
As far as I know it's not possible to flash a stock ROM with fastboot without unlocking the bootloader. Instead, you have to rename the stock ROM to update.zip and put it on your internal storage and then flash it by using recovery (also a button trick).
It could be that it's still the same hardware problem. Maybe Acer didn't know what was wrong and just replaced the motherboard. It's a massive repairing service center, so they're not going to search for everything.
Oh, an important question:
Did Acer, or did they not reinstall your tablet after they "repaired" it?
If not, then it might just be that. It's like your home pc. When you change your motherboard, you might need to reinstall the thing (or re-activate Windows, but that's not relevant ) to prevent errors.
Good luck and I hope you succeed
Ps. For what it's worth, you can also try to reflash your device with a beta ROM (it's beta because there isn't a stock ROM available which you can flash without having the bootloader unlocked). You can download it here. Now I'm not quite sure if you can update your tablet then, so it's coming out of beta. To flash it, do whatever I said with the renaming to update.zip (to transfer the ROM, you can use an sd card. It might just look for update.zip on the sdcard too). Please keep in mind that I'm not sure if you can update your tablet so it'll come out of beta. If you are going to try this, please post your results here
troun2000 said:
So starting from beginning, while playing some music, my A700 reboot and hang up in infinite loop of Acer and Iconia Tab logos. As Vol+Power was not responding, I sent it back to Acer for repair and received it back yesterday after they replaced motherboard (and microphone!?).
Cool.
But no, because after a couple of hours of re-installing, it reboot and finished in the same Logos loop, just after selecting Airplane mode.
So my question, can I re-flash this A700 with a complete clean stock ROM, as I have only access to Fastboot mod?
Click to expand...
Click to collapse
Considering the same issue happened under the same circumstances, we can pretty much rule out hardware failure. (they claim to have changed the mainboard.
If you look at the Acer 700 troubleshooting tree, they followed procedures. Or perhaps they "claimed" to have changed the system board, when in reality they just re-flashed the rom over the top so they can make more money by the hour. A common practice.
So the issue to me, seems to be either a faulty rom, or, faulty player. Were you using a player from the Play Store?
Also, would help to know which OS you were on. ICS or JB?
As with re-installing a rom, you should be able to get to the stock recovery. In which case, you could try
a. Re-installing the stock version rom again (renamed as update.zip)
b. Install an update.zip compatible with your region.
There are 2 types of boot loop.
1. Iconia.... this is a boot animation loop (stuck at boot animation)
2. Tab continually re-boots over and over. This is a boot-loop
3. Although not considered a boot-loop, stuck at the Acer logo.
So which do you have?
More than likely you have animation loop. Which means the OS is corrupted somehow.If I understand you correctly.
As with fastboot OEM unlock, you can do the following;
Flash a custom recovery
Flash a kernel (boot.img)
Flash a complete system image. This is not like flashing a Rom. It's an image file generated from another user who has a working 700.
As with unlocking your bootloader, well, it depends on if you wish to get things fixed. Or to return it yet again to Acer Repair. Can't tell you what to do Mate. But if it were me, I would take matters into my own hands after previous attempts.
MD
So I tried the following (yes, it is inverted relative to theory);
- Press [vol +] + [power]
- As soon as the tablet vibrates, let go of power and play several times [lock]
=> Fastboot mod, displaying "Bootloader vJB-653b3d3: Starting Fasboot USB download protocol"
- Press [vol-] + [power]
- As soon as the tablet vibrates, let go [power] and play [lock]
=> no effect
And as reminder, Recovery is not reachable.
TomONeill said:
As far as I know it's not possible to flash a stock ROM with fastboot without unlocking the bootloader. Instead, you have to rename the stock ROM to update.zip and put it on your internal storage and then flash it by using recovery (also a button trick).
It could be that it's still the same hardware problem. Maybe Acer didn't know what was wrong and just replaced the motherboard. It's a massive repairing service center, so they're not going to search for everything.
(...)
Ps. For what it's worth, you can also try to reflash your device with a beta ROM (it's beta because there isn't a stock ROM available which you can flash without having the bootloader unlocked). You can download it here. Now I'm not quite sure if you can update your tablet then, so it's coming out of beta. To flash it, do whatever I said with the renaming to update.zip (to transfer the ROM, you can use an sd card. It might just look for update.zip on the sdcard too). Please keep in mind that I'm not sure if you can update your tablet so it'll come out of beta. If you are going to try this, please post your results here
Click to expand...
Click to collapse
So I guess I can not flash, because I do not have access to recovery, only to fastboot.
TomONeill said:
Oh, an important question:
Did Acer, or did they not reinstall your tablet after they "repaired" it?
If not, then it might just be that. It's like your home pc. When you change your motherboard, you might need to reinstall the thing (or re-activate Windows, but that's not relevant ) to prevent errors.
Good luck and I hope you succeed
Click to expand...
Click to collapse
Yes they re-install OS as the A700 came back with a German Rom where I sent it with a French Rom.
Thanks a lot for your help :good:
Moscow Desire said:
Also, would help to know which OS you were on. ICS or JB?
[...]
There are 2 types of boot loop.
1. Iconia.... this is a boot animation loop (stuck at boot animation)
2. Tab continually re-boots over and over. This is a boot-loop
3. Although not considered a boot-loop, stuck at the Acer logo.
So which do you have?
Click to expand...
Click to collapse
Can you answer both questions MD asked you?
If you're running Jelly Bean, the bootloader has changed. This requires a different way of going in the recovery mode:
DЯΦ[email protected]П said:
With JB there is a change on the A700 (can't test on A701):
Boot into recovery:
- Press [vol-] + [power]
- Once the tablet vibrated, let go [power] and keep [vol-].
- Now the tablet vibrates a second time, let go [vol-] and press [vol+] quick
- Once the text that appears on the screen ("loading recovery kernel image"), let go [vol+].
Click to expand...
Click to collapse
Moscow Desire said:
Considering the same issue happened under the same circumstances, we can pretty much rule out hardware failure.
Click to expand...
Click to collapse
Not really, first time it happened while playing music with google music player (reboot then loop).
Second time it was after setting the Airplane mode for night (reboot then loop).
Moscow Desire said:
(they claim to have changed the mainboard).
If you look at the Acer 700 troubleshooting tree, they followed procedures. Or perhaps they "claimed" to have changed the system board, when in reality they just re-flashed the rom over the top so they can make more money by the hour. A common practice.
Click to expand...
Click to collapse
I though the same but I found a 'technical paper' saying that board and microphone were changed, and both Wifi and Bluetooth Mac adresses have changed. So it seems they really changed motherboard.
Moscow Desire said:
So the issue to me, seems to be either a faulty rom, or, faulty player. Were you using a player from the Play Store?
Also, would help to know which OS you were on. ICS or JB?
Click to expand...
Click to collapse
Rom were 'different' when it happened; first was an FR and second was a DE. It was google stock player (only first time).
JB both times.
Moscow Desire said:
As with re-installing a rom, you should be able to get to the stock recovery. In which case, you could try
a. Re-installing the stock version rom again (renamed as update.zip)
b. Install an update.zip compatible with your region.
Click to expand...
Click to collapse
I do not have access to stock recovery, only fastboot mode
Moscow Desire said:
There are 2 types of boot loop.
1. Iconia.... this is a boot animation loop (stuck at boot animation)
2. Tab continually re-boots over and over. This is a boot-loop
3. Although not considered a boot-loop, stuck at the Acer logo.
So which do you have?
More than likely you have animation loop. Which means the OS is corrupted somehow.If I understand you correctly.
Click to expand...
Click to collapse
I have;
Acer Logo/animation -> Inconia Tab Logo/animation -> reboot -> Acer Logo/animation -> and so on...
Moscow Desire said:
As with fastboot OEM unlock, you can do the following;
Flash a custom recovery
Flash a kernel (boot.img)
Flash a complete system image. This is not like flashing a Rom. It's an image file generated from another user who has a working 700.
As with unlocking your bootloader, well, it depends on if you wish to get things fixed. Or to return it yet again to Acer Repair. Can't tell you what to do Mate. But if it were me, I would take matters into my own hands after previous attempts.
MD
Click to expand...
Click to collapse
OK, that helps a lot, thanks. I guess what I would like to do is to flash a system Image. Where can I get one?
So far, I have Android SDK installed and Acer drivers installed (which bring me a "ADB interface"-"Acer fastboot interface" device in Windows Device manager)
Whats up guys? I did a factrory reset/wipe data on my tf300 tab and now its stuck at the asus screen I cant even get it to turn off till the batteryruns down Power and volume down just turn the screen off for a second then back to asus screen. Any tips? Should i just replace the motherboard? What all will that involve other than the hardware swap?
jerimynal wiley said:
Whats up guys? I did a factrory reset/wipe data on my tf300 tab and now its stuck at the asus screen I cant even get it to turn off till the batteryruns down Power and volume down just turn the screen off for a second then back to asus screen. Any tips? Should i just replace the motherboard? What all will that involve other than the hardware swap?
Click to expand...
Click to collapse
what boot loader> also you did wipe from recovery not the first menu right?
jerimynal wiley said:
Whats up guys? I did a factrory reset/wipe data on my tf300 tab and now its stuck at the asus screen I cant even get it to turn off till the batteryruns down Power and volume down just turn the screen off for a second then back to asus screen. Any tips? Should i just replace the motherboard? What all will that involve other than the hardware swap?
Click to expand...
Click to collapse
Is your device unlocked? What version android were you running? And does nothing show up if you continue to hold the volume down and power button after it resets? Hopefully you'll be able to fastboot TWRP recovery. I encountered a similar problem when I tried to install a custom 4.1 ROM from stock Android 4.0.3, but my device was unlocked and I was able to successfully get things going after carefully searching these forums.
bricked tf300
MaMMiTs said:
Is your device unlocked? What version android were you running? And does nothing show up if you continue to hold the volume down and power button after it resets? Hopefully you'll be able to fastboot TWRP recovery. I encountered a similar problem when I tried to install a custom 4.1 ROM from stock Android 4.0.3, but my device was unlocked and I was able to successfully get things going after carefully searching these forums.
Click to expand...
Click to collapse
Yes it is unlocked Jellybean nothing happens if i keep holding the volume down and power except the screen goes off for a second the right back to the asus screen Fastboot won't work, it just says waiting for device My pc won't see it at all, not in device manager or anyuthing No apx either. If i could get fastboot to work i think i could fix it
I face a similar problem, but my fastboot is working. However, when I try to flash something through fastboot, the screen hangs until I reboot it. Also, if I choose one of the three options, it gives the message "Unrecoverable Bootloader Error."
I almost for got the details:
Bootloader - 10.6.1.18....I think...(it's JB 4.2.1, I'm sure)
Recovery - formerly twrp-2.4.4-jb.blob ( not 2.4.4-jb-42.blob)
Android - not booting
Device unlocked
Error (in red letters) - Unrecoverable bootloader error)
And no, I do not have NVFlash.
Any thing that I might've missed? Please let me know. ASUS wants $99 just to troubleshoot over the phone. I don't think so.
Also same problem. Fastboot 'sees' the TF300 device but does not flash.
I have the same problem. Fastboot 'sees' the TF300 device but does not flash. If somone has come up with a solution for this, could you please share, it would be greatly appreciated. Did Asus finally release NVflash for JB 4.2? It seems it is the only possible way of solving this, or isn't it?
Thanks for your help
aarsyl said:
I face a similar problem, but my fastboot is working. However, when I try to flash something through fastboot, the screen hangs until I reboot it. Also, if I choose one of the three options, it gives the message "Unrecoverable Bootloader Error."
I almost for got the details:
Bootloader - 10.6.1.18....I think...(it's JB 4.2.1, I'm sure)
Recovery - formerly twrp-2.4.4-jb.blob ( not 2.4.4-jb-42.blob)
Android - not booting
Device unlocked
Error (in red letters) - Unrecoverable bootloader error)
And no, I do not have NVFlash.
Any thing that I might've missed? Please let me know. ASUS wants $99 just to troubleshoot over the phone. I don't think so.
Click to expand...
Click to collapse
---------- Post added at 08:44 PM ---------- Previous post was at 08:31 PM ----------
It seems there is no solution yet. See this post:
http://forum.xda-developers.com/showthread.php?t=2179874&page=17
jerimynal wiley said:
Whats up guys? I did a factrory reset/wipe data on my tf300 tab and now its stuck at the asus screen I cant even get it to turn off till the batteryruns down Power and volume down just turn the screen off for a second then back to asus screen. Any tips? Should i just replace the motherboard? What all will that involve other than the hardware swap?
Click to expand...
Click to collapse
What happened in the end? Did you go to ASUS and get it repaired? How much did it cost?
Hi guys,
I solved the problem with the bootloader error (0x0000000) assistance in sending the TF300T. I told him that during the upgrade something must have gone wrong and the OS did not boot anymore. They repaired free of charge. My dealer to whom I entrusted the tablet is Mediaworld (a chain of electronic products Italian). I hope you can serve
Hi.
I own a TF700T and seems to have bricked it. Last status was: I had the latest stock ROM with root running and wanted to get a CM11 based 4.4.2 image from here. I downloaded it and used rom manager to get it installed. But the install script failed at some point and I thought the recovery might be outdated. So I used ROM Manager to update recovery... I tried CWM and TWRP option. Finally I booted up into recovery trying again to install those damn rom - I used the option to wipe all data / settings from the main menu and tried again to install the ROM which again failed (I do not remember the error message clearly). I gave up. I used the "reboot" option.
Now:
- Powering up gets me into the screen with the ASUS logo (left upper corner says "the device is unlocked"). Here it is stuck forever.
- Power + Vol-Down is same as just Power - I do not get into flashboot with those 3 small icons... I just get the ASUS logo and nothing else happens. Reset hole does not change situation. The device is pretty much "always on" now (till battery is exhausted) as long-press Power turns off and immediately on again
- Only thing that seems to work: Power + Vol-Up ends up in APX mode - my computer recognizes the device via USB at this point
Unfortunately I never did any set up to nvflash.
Do I have any chance to get this thing alive again?
Thanks a lot in advance,
q2.
Quentin2 said:
Hi.
I own a TF700T and seems to have bricked it. Last status was: I had the latest stock ROM with root running and wanted to get a CM11 based 4.4.2 image from here. I downloaded it and used rom manager to get it installed. But the install script failed at some point and I thought the recovery might be outdated. So I used ROM Manager to update recovery... I tried CWM and TWRP option. Finally I booted up into recovery trying again to install those damn rom - I used the option to wipe all data / settings from the main menu and tried again to install the ROM which again failed (I do not remember the error message clearly). I gave up. I used the "reboot" option.
Now:
- Powering up gets me into the screen with the ASUS logo (left upper corner says "the device is unlocked"). Here it is stuck forever.
- Power + Vol-Down is same as just Power - I do not get into flashboot with those 3 small icons... I just get the ASUS logo and nothing else happens. Reset hole does not change situation. The device is pretty much "always on" now (till battery is exhausted) as long-press Power turns off and immediately on again
- Only thing that seems to work: Power + Vol-Up ends up in APX mode - my computer recognizes the device via USB at this point
Unfortunately I never did any set up to nvflash.
Do I have any chance to get this thing alive again?
Thanks a lot in advance,
q2.
Click to expand...
Click to collapse
Unfortunately ROM Manager does not work with the TF700 and you are not the first one to find out the hard way...
If you cannot find a way to boot into the bootloader to have fastboot, there's nothing you can do anymore without the NVflash blobs.
Did you try holding Vol - and then pressing the reset button in that little pinhole on the side of the tablet?
If you have ADB drivers installed on your PC you could try if you can establish an ADB connection at any point. If you did, you could issue the command: "adb reboot bootloader", which would enable you to flash a recovery and/or bootloader. This probably won't work since you need to be in the recovery or have Android booted for ADB to work, but worth a try anyway...
Admittedly these are very thin straws - but what have you got to loose?
Also: Just a few days ago a user here was stuck on a bootloop to recovery and couldn't get out of it. He left it alone overnight and all the sudden the bootloop sorted itself out... I have no explanation for it and it is unlikely to happen in your case, but you never know...
Good luck!
Thanks for replying.
Yes, I did keep Vol-Down (means Vol-Left) pressed while pinching the reset button. It did not help.
I will experiment a bit more. It's not really a boot "loop" - it gets stuck at the ASUS logo and this does not change anymore. Not overnight.
So far I could only see it being recognized as USB device in APX mode. Can you give me a bit background here? I have nvflash here. The blobs are not available anywhere on the net? Or why is that all a big fuzz? I used to have a Notion Ink Adam and APX saved my life several times, but the blobs were available to everybody. Nobody has the blobs here? Or are they device-specific?
I cannot believe that a today's device with a non-bricked bootloader and working APX is totally lost and even the manufacturer will only offer a costly RMA to replace the whole mainboard!?
Best regards,
q2.
Quentin2 said:
Thanks for replying.
Yes, I did keep Vol-Down (means Vol-Left) pressed while pinching the reset button. It did not help.
I will experiment a bit more. It's not really a boot "loop" - it gets stuck at the ASUS logo and this does not change anymore. Not overnight.
So far I could only see it being recognized as USB device in APX mode. Can you give me a bit background here? I have nvflash here. The blobs are not available anywhere on the net? Or why is that all a big fuzz? I used to have a Notion Ink Adam and APX saved my life several times, but the blobs were available to everybody. Nobody has the blobs here? Or are they device-specific?
I cannot believe that a today's device with a non-bricked bootloader and working APX is totally lost and even the manufacturer will only offer a costly RMA to replace the whole mainboard!?
Best regards,
q2.
Click to expand...
Click to collapse
For the TF700 the nvflash blobs are device specific - sorry.
Damn. That was the only answer I didn't want to read
Thanks a lot. So chances are gone, only RMA could help... I will ask friendly at Asus what costs they will charge...
q2.
Update:
Reply is here.
They only want to exchange mainboard. They of course know (and it seems that this is the only thing they know) that my bootloader was unlocked, therefore this is no case of guarantee for them. I know, I wrote to them that I just want to know how much they wanna charge me to fix this issue.
But: they don't want to tell me how much. They say they do not even know which revision and what hardware is inside my tablet, not even from my serial number. And I must first send them my tablet and they will charge me 95 Euro to check what's going on. And then they will tell me how much it will cost (and according to other threads I saw prices of over 400 Euro for a mainboard change - the TF701 successor model cost 450 Euro new in store)...
I somehow feel the need to reply that if they would've put only half the energy the put into logging who has unlocked the bootloader into the fact of making APX usable as a emergency recovery (as obviously not even Asus is able to generate a working blob for my device), they would have higher customer satisfactory statistics. I still just cannot believe a today's device lacks of all recovery options after a bootloader fails for some reason - as well as I cannot understand why Koush did not display a warning in ROM manager if problems are known to the community with this specific device (I mean the problem did not arise last week and ROM manager had tenths of updates since then).
I know that in the end all was my fault. And all flashing is done on our own risk. I will have to deal with it.
Phew...
Unlucky. It should be be stickied here somewhere that ROM Manager bricks the TF700 but then there is no guarantee it would be read. It is well known on this forum but that doesn't help people that don't visit frequently.
You can replace the mainboard yourself fairly easily. Watch the you tube vids on how to do it,. That is what I would do if I was in your position.
berndblb said:
For the TF700 the nvflash blobs are device specific - sorry.
Click to expand...
Click to collapse
Is there a way to backup my blobs before I leave all stock then?
Thanx! Zeddock
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
zeddock said:
Is there a way to backup my blobs before I leave all stock then?
Thanx! Zeddock
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2455925&highlight=nvflash
Any Solution?
Quentin2 said:
Hi.
I own a TF700T and seems to have bricked it. Last status was: I had the latest stock ROM with root running and wanted to get a CM11 based 4.4.2 image from here. I downloaded it and used rom manager to get it installed. But the install script failed at some point and I thought the recovery might be outdated. So I used ROM Manager to update recovery... I tried CWM and TWRP option. Finally I booted up into recovery trying again to install those damn rom - I used the option to wipe all data / settings from the main menu and tried again to install the ROM which again failed (I do not remember the error message clearly). I gave up. I used the "reboot" option.
Now:
- Powering up gets me into the screen with the ASUS logo (left upper corner says "the device is unlocked"). Here it is stuck forever.
- Power + Vol-Down is same as just Power - I do not get into flashboot with those 3 small icons... I just get the ASUS logo and nothing else happens. Reset hole does not change situation. The device is pretty much "always on" now (till battery is exhausted) as long-press Power turns off and immediately on again
- Only thing that seems to work: Power + Vol-Up ends up in APX mode - my computer recognizes the device via USB at this point
Unfortunately I never did any set up to nvflash.
Do I have any chance to get this thing alive again?
Thanks a lot in advance,
q2.
Click to expand...
Click to collapse
Unfortunately I'm stuck in same boat I tried to wipe out settings completely and clockwork mode was stuck and I was able to wipe recovery with TWRP or so I thought tried to reboot into recovery got stalled and now stuck on asus screen. I'm not opposed to buying a new motherboard but I find it very hard to believe that no one has come up with a solution to flashing the mainboard with the original firmware. I'm tempted to ask asus but I know the bill will be more then the tablet. Did you find an easier solution or do I just have to swap out the mainboard?
sbdags said:
http://forum.xda-developers.com/showthread.php?t=2455925&highlight=nvflash
Click to expand...
Click to collapse
Thanx, but it seems like to backup blobs I have to do the very thing that will risk me needing backup of my blobs? ... install a custom bootloader before I have a backup?
Is this right?
Is this a safer method?
zeddock
zeddock said:
Thanx, but it seems like to backup blobs I have to do the very thing that will risk me needing backup of my blobs? ... install a custom bootloader before I have a backup?
Is this right?
Is this a safer method?
zeddock
Click to expand...
Click to collapse
That's correct. You have to flash a modified bootloader and recovery. Done correctly this is not risky at all. But if there is a single line in the instructions you are not sure you understand, you are not quite ready.
There are quite a few tutorials on flashing in fastboot on this forum. Read them.
But generating your nvflash blobs you have to do without a safety net. It's worth it though! I have become much more adventurous with my tablet since I have the blobs squared away...
berndblb said:
Done correctly this is not risky at all.
Click to expand...
Click to collapse
How do you define risk?
Flashing a bootloader (without having nvflash access) is always risky by my definition, it *can* permabrick your tablet if something goes wrong at the wrong moment. But it's the best we have.
Just for reference I have a p5113 model.
A while back I put Cyanogen on my tablet. A few months ago I cracked the screen, only a bit on the corner, of course I can't stand cracked screens so I ordered a replacement. When I installed the screen everything connected fine and dandy so I tried to start it up, but when I did the touch function didn't work. I thought maybe it was just a bad screen that I had ordered, so I got another. When I got the second screen in I replaced it, but this time it was doing the same thing as before where the touch wasn't working! I made sure everything was connected okay and also checked for anything damaged, but everything seemed fine. For some reason I thought maybe hard resetting it would help, but it didn't. At this point I was just trying to get the stock 4.2.2 firmware back on it. I downloaded the firmware, used ODIN to get it onto the tablet. When it restarted after the firmware was loaded on, it was stuck in a bootloop. I heard that it may just need to be factory reset again so I tried to get into recovery mode, but only goes into ODIN/Download mode, which is what my final problem is here.
TL;DR Tablet will not go into recovery mode. Only ODIN/download mode.
I haven't been able to find ANYONE else that has had this problem before. So if anyone knows the source of my problem, I would be very appreciative of your help.
Well you could have fried the capacitive touch circuit with a static charge I have no idea what your skill level is also you could have a bad image or you could have bonked the hardware and it doesn't detect critical boot hardware I'm not that well versed in firmware related boot issues but hopefully some helpful nerd can give you a hand you could also just try again aster you download a new IMG
Sent from my toaster
Samwise13 said:
Just for reference I have a p5113 model.
A while back I put Cyanogen on my tablet. A few months ago I cracked the screen, only a bit on the corner, of course I can't stand cracked screens so I ordered a replacement. When I installed the screen everything connected fine and dandy so I tried to start it up, but when I did the touch function didn't work. I thought maybe it was just a bad screen that I had ordered, so I got another. When I got the second screen in I replaced it, but this time it was doing the same thing as before where the touch wasn't working! I made sure everything was connected okay and also checked for anything damaged, but everything seemed fine. For some reason I thought maybe hard resetting it would help, but it didn't. At this point I was just trying to get the stock 4.2.2 firmware back on it. I downloaded the firmware, used ODIN to get it onto the tablet. When it restarted after the firmware was loaded on, it was stuck in a bootloop. I heard that it may just need to be factory reset again so I tried to get into recovery mode, but only goes into ODIN/Download mode, which is what my final problem is here.
TL;DR Tablet will not go into recovery mode. Only ODIN/download mode.
I haven't been able to find ANYONE else that has had this problem before. So if anyone knows the source of my problem, I would be very appreciative of your help.
Click to expand...
Click to collapse
sounds like a damaged digitizer to me.
may as well get a new tablet as digitizers tend to cost almost the same as a new device...
now... recovery...
this may sound redundant but try flashing the firmware again. when it flashes make sure it says "recovery.img" or similar at some point in the Odin log.
be sure to use the correct pit file and the repartition check box when flashing.
there are usually two or more firmwares per tablet so if one fails to boot recovery try the other.
the site I find that has reliable files is samsung-updates.com but be prepared for slow downloads averaging am hour and a half.
Sent from my SGH-T999 using Tapatalk
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