[Q] [Save my crappy tablet] Encryption unsuccessful & can't access CWM - General Questions and Answers

Hi there folks,
Hope someone can help me with this as I’ve searched high and low for answers on the interweb to no avail.
I tried installing the CyanogenMod 9 for AllWinner A10 tablets onto my cnmlifestyle table (a cheap tab shipped by the retailer argos).
http://forum.xda-developers.com/showthread.php?t=1760929
The installed failed as I’m getting the “encryption unsuccessful” screen after the initial boot.
I wasn’t too concerned though because I had successfully installed CWM recovery and created a back-up.
But now I can’t get back into CWM recovery?
I still have access to the device via adb but for some reason fastboot won’t work.
When I type “adb reboot recovery” the tablet boots quickly and goes straight into the CyanogenMod splash screen.
I can navigate around the device using adb shell so I’m assuming all is not lost?
Some background information:
The tablet is unsupported but I was pretty sure it was a clone of the Mediacom 907c or Gemei G9 so I used the g9_legacy-compatibility_vX.zip comp zip compatibility pack.
So can anyone suggest some means of either:
Triggering recovery from the PC
Flashing an alternative Rom from the PC using adb
Or getting fastboot up and running.
Any input would be appreciated.
Thanks in advance

Related

Storage Options Scroll 7" 51264 bricked Help Please!!

Hi,
A friend gave me a Storage Options Scroll 7" Model 51624 (TCC8902) with 2.1.
I found that cyanogen has a 2.3 Rom for this device so I tried to flash it.
I flashed the clockwork recovery and did my back up. Then I downloaded the rom from cyanogen and installed.
What was my surprise that when I restarted it got stuck on the main screen with the logo "scroll Storage Options"
I tried to enter the recovery but doesn't work!!!
I think my error was the rom I choose for flashing.
I used the Storage Options Scroll 7" resistive 8K, and I know now that mine is the same one but the resistive 4K.
I though I could do something if I could use the Adb commands and some inspiration but the problem is that my computer doesn't recognize the device (Android in yellow on device manager). I installed the Android SDK that has the google usb driver but still not working. I tried the VTC 5.0.0.1 drivers too but no luck either.
I desperately need some help to install the boot recovery and then I'll flash the right rom.
I use windows 7 x64 and a laptop with windows xp 32.
I've been reading the thread http://forum.xda-developers.com/showthread.php?t=1101094 but has 163 posts and I have to say that I didn't read all of them. Anyway I did a search about bricked scroll and didn'f find anything. If someone knows where to point me at I'll be very gratefull. I appologize if my posts is already solved somewhere.
Thanks in advance
there is a guide on getting android adb set up on the pc with modified drivers somewhere...
1st things 1st though, have you tried holding vol up while turning it on to get into recovery?
as long as you installed the custom recovery correctly (which im sure you did if you managed to install another rom), then you should have no problem getting into it.
unless, that is, you dont have any volume buttons to get into recovery / they dont work!
Sent from my MB860 using xda premium
To flash the cyanogen rom I had to enter the clockwork recovery with the power+vol up. So first thing I did after realised it wasn't going to load the rom was to restart the tablet into recovery but it doesn't work.
That's why I was thinking the posibility of flashing clockwork recovery again through the adb commands or maybe the boot.img (I think this img is the one responsible for boot). But as I said my computers don't recognize the device. Both says Android with the yellow warning.
I'm looking for this modified drivers but can't find them. any web site address?
I have downloaded the firmware from Storage options but as I cant enter into the recovery I can flash it.

[Q] Need Help Re-Flashing Device

Hi --
I have a Samsung Nexus S that I bought used for development purposes.
I ended up using it temporarily as my phone so when that was ended I decided to do a factory reset of the device.
However, it did not succeed! I wound up with the green Droid lying down with the red triangle. I've tried various ways to reboot the device but it appears there is no ROM for the device to load up.
I am also unable to get ADB to recognize the device. It certain situations it will appear in my Device Manager (Windows 8.1 64-bit)
I see options to load a ROM via USB or "ADB sideways" from the recovery menu. However, since I can't get ADB to recognize the device and there isn't a micro SD slot, how do I get a new ROM on to this device? Is it even possible?
I only paid $40 for the phone on eBay but would like to return it to a usable development phone if possible.
Thanks
Rich
HI --
Okay I did discover that I can access the device via Fastboot so I guess I just need help on where to download the right ROM(s) to flash to the device?
Rich
instructions and needed files are here
developers.google. com/android/nexus/images
p.s. since I cant post links yet, I had to put an empty space in front of .com
Thanks so much.. I'll give that a shot.
Rich
let us know if you were succesfull or not
It should be quite straightforward. Let us know if assistance is needed.

[Q] How to root a tablet that won't boot

Hello,
I have a tablet that has recently stopped booting. The manufacturer does not provide a firmware rom, nor have I been able to recover it any other way. I feel like I have been running in circles in researching ways to recover it (but I have learned alot). I think that I could recover the tablet if I could install a more flexible recovery manager, such as CWM or TWRP. However, to my knowledge, the tablet must be rooted first in order to install these custom recoveries. So that brings mt to my question: How can I root a tablet that won't boot? I have heard many good (and a few bad) things about Kingosoft Rooter and other root methods. However, even Kingosoft requires the tablet to have USB debugging enabled. Unfortunately, I did not have this enabled before my tablet crashed. So:
1. Is it possible to root my tablet that won't boot?
2. Is it possible to enable USB debugging on my tablet that won't boot?
3. Is there any other way you can think of to get this tablet running?
By the way, the tablet is a RCA RCT6378W2 tablet. I can access the stock recovery (android system recovery <3e>, but I can't seem to make it do anything worthwhile. Any ideas? Thanks!
1. You can't root because the tablet must be on
2. You can't enable adb debugging because the tablet must be on
3. I guess that your tablet is a made in china tablet, so there should be a devices that have same or similar characteristics, and maybe there is a stock rom for those devices
Good luck for your tablet :good:
jeremyb234 said:
Hello,
I have a tablet that has recently stopped booting. The manufacturer does not provide a firmware rom, nor have I been able to recover it any other way. I feel like I have been running in circles in researching ways to recover it (but I have learned alot). I think that I could recover the tablet if I could install a more flexible recovery manager, such as CWM or TWRP. However, to my knowledge, the tablet must be rooted first in order to install these custom recoveries. So that brings mt to my question: How can I root a tablet that won't boot? I have heard many good (and a few bad) things about Kingosoft Rooter and other root methods. However, even Kingosoft requires the tablet to have USB debugging enabled. Unfortunately, I did not have this enabled before my tablet crashed. So:
1. Is it possible to root my tablet that won't boot?
2. Is it possible to enable USB debugging on my tablet that won't boot?
3. Is there any other way you can think of to get this tablet running?
By the way, the tablet is a RCA RCT6378W2 tablet. I can access the stock recovery (android system recovery <3e>, but I can't seem to make it do anything worthwhile. Any ideas? Thanks!
Click to expand...
Click to collapse
Wipe cache and reboot and when it doesn't work do you have to try factory reset.
Bink Feed said:
Wipe cache and reboot and when it doesn't work do you have to try factory reset.
Click to expand...
Click to collapse
Thanks to both of you for your suggestions.
@ bink feed - Thanks for those recommendations. Those are the normal recommendations that should be given to most people. Unfortunately, I have already tried both of those options with no success. It seems that many, many people are running into this problem. It makes me wonder if the recovery partition is corrupt or if some system files were somehow corrupted. The "wipe cache" option and "factory reset" option both perform successfully according to the recovery system, but they do not fix the problem with the tablet not booting. I apologize for failing to mention that I have tried these options. If you have other ideas, please let me know.
@ kfarhan57 - Thanks for the suggestion. This seems like a good idea and it is something I have attempted to do. Problem is, I don't know precisely what similarities must be present for this to work. I have tried using ROMs from other tablets that share the same processor and motherboard, but have not had any success. They seem to always fail the verification process. I have very, very little experience in all of this, so it's always possible that I am not doing it correctly too. Do you know of anyone who has successfully done this? (Someone who has restored on device with a firmware from a similar device). If so, I'd like to ask them how they did it. Here is what I have tried:
1. Boot device into Android Recovery System.
2. Select "Apply update from ADB"
3. Connect the tablet to PC using USB cable
4. Load up Cmd terminal in Windows, navigate to folder containing ADB.exe
5. Type in "ADB sideload filename.zip"​The only thing that I have successfully sideloaded (and passed verification with) has been 3 small firmware updates for my tablet. Unfortunately, they are minor updates and do not restore the Operating System or ability to boot into the OS. Presently, I have been toying with the idea of merging one of these small firmwares that pass verification with the factory OS firmware from a similar device. I don't know if this is even possible, and if it is, I probably lack the knowledge needed to do it. If anybody reading this post has a suggestion, please let me know! BTW, one other thing I forgot to mention is this- I have the files copied from a working tablet of the same model. I have the boot.img, recovery.img, system.img, and virtually everything from his device... I just don't have a clue what to do with it. Thanks again. Hope to hear back from one of you!

[Completed] How do I fix my boot verified failed error on Acer A500?

I was recently trying to update my Acer Iconia A500 and it appears I made a mistake...I had my tablet rooted and I was using the Acer recovery tool to try to use cwm to update. I was running stock OTA ICS. Acer recovery tool warned that my bootloader should be updated to version 1.03 (Acer recovery tool said I had 0.03.12-ICS). I was trying to update the bootloader and initiated a reboot and I haven't been able to boot since. When I try to boot, I see "boot verified failed...". I've tried several fixes from what I've found searching. The hard reset with power/volume/screen lock does not work and I still see the boot verified failed. I tried copying every version of update.zip I could find to a microsd card and booting by holding power+volume down - same result. If I boot by holding power+volume down+screen lock I get a message saying "bootloader: v.03.12-ICS: Starting Fastboot USB download protocol", but nothing happens. If I plug the tablet into my computer in this state, it makes a noise recognizing a connected device, but I cannot view the drives (drivers are current) - also in this same state if I use the list devices command in adb fastboot no device is displayed.
Any feedback or advice would be greatly appreciated. I'm not experienced and I am simply trying to piece together information from various sources. Normal solutions would be hard reset or booting with update.zip, but neither are working.
XDA Visitor said:
I was recently trying to update my Acer Iconia A500 and it appears I made a mistake...I had my tablet rooted and I was using the Acer recovery tool to try to use cwm to update. I was running stock OTA ICS. Acer recovery tool warned that my bootloader should be updated to version 1.03 (Acer recovery tool said I had 0.03.12-ICS). I was trying to update the bootloader and initiated a reboot and I haven't been able to boot since. When I try to boot, I see "boot verified failed...". I've tried several fixes from what I've found searching. The hard reset with power/volume/screen lock does not work and I still see the boot verified failed. I tried copying every version of update.zip I could find to a microsd card and booting by holding power+volume down - same result. If I boot by holding power+volume down+screen lock I get a message saying "bootloader: v.03.12-ICS: Starting Fastboot USB download protocol", but nothing happens. If I plug the tablet into my computer in this state, it makes a noise recognizing a connected device, but I cannot view the drives (drivers are current) - also in this same state if I use the list devices command in adb fastboot no device is displayed.
Any feedback or advice would be greatly appreciated. I'm not experienced and I am simply trying to piece together information from various sources. Normal solutions would be hard reset or booting with update.zip, but neither are working.
Click to expand...
Click to collapse
Hard/factory reset would have been my first answer too.
Is your issue similar to this one: Boot verified failed after update PLEADE HELP?
Maybe you can unbrick it like described here: [GUIDE] How to unbrick Acer Iconia A500.
And if you need further help, please register on xda and ask in the thread directly.
Good luck !
Thread closed. Thank you!

ADB Device Not Showing as Attached - Shield Tablet PLEASE HELP!!!

!!!PLEASE HELP THANK YOU!!!
Hello everyone thank for taking your time to read this and for hopefully helping me out....
It started a week ago when I had notice that when I updated my Tablet (32gb LTE UK) I forgot to redo the Supersu function and TWRP so i went ahead and rebooted my devices and installed TWRP via adb fastboot not a problem there and i got into custom recovery and install Supersu and restarted the tablet like all the other 20+ times But this time around it stayed on the boot logo and thats as far as i get.
Now having done this many time before on this and my two other shield tablets and samsung phones I'm at a loss, as now when i boot into the bootloader with the options for me to use ADB it will not find my device. I've even gone ahead a installed the rather large and normally unnecessary Android Studio with SDK Manager and tried it with the google drivers instead of the shield driver that I've re-download just in case they had been updated.
* Tablet stays on Boot logo
* I can boot into Bootloader
* If i select fastboot screen goes blank but is on
* If I select Recovery tablet boots with Android laying down as if Sick
* I no longer had a Custom recovery (TWRP)
* ADB does NOT list my attach device
Sorry if I've gone one but as you can tell I'm normally good with this kind of stuff and have looked around for a fix but all have failed so far please if someone can help me that would be the Brilliant.
Cheers Chris.
check device manager in windows while tablet is in bootloader and usb connected. look for a device called fastboot and see if it has an exclimation. Download the atteched zip and look at the images for a visual guide on what to install for the drivers.
any solution??

Categories

Resources