EDIT: title is incorrect, model is actually S2109A-F
Hi, I'm pretty novice but have searched a solid 2 days about this topic on this device.
The lenovo a2109a-f I recently got (I know, its like 4-5 years old, but for 40$, not a bad 9+" tablet) was in fine working order, but did have some bloatware. Feeling ballsy, I attempted a root, and now it boot loops, meaning it will constantly reboot and show the animated splash screen, and play the synthetic chime sound. Each loop lasts about 1-2 minutes.
Since I can still access the fastboot and the boot recovery I've tried the following:
1) attempt the install of a new rom (original ICS or JB for this device) from a micro SD card inserted into the slot
- no go, it says it mounts the sd card, but wont read from it
2) attempt factor reset (cache, factory reset etc)
- no change and same root file still shows up in the tablet "/sdcard/"
3) Rerun the flash recovery process
- Tablet seems to accept linux (from windows) commands via cmd (fastboot -i <address/commands go here>), but no change for the boot loop
4) attempted other recovery images in fastboot mode
- thought I actually damaged it more. Since it stopped boot looping but wouldn't even boot to recovery at all. I then flashed the original recovery ("CWM_S2109.img") and was able to get the bootloader back and the bootlooping behavior again.
My question for you all, is there something I need to do via the fastboot method to clear the cache of the bootloader, or the memory of the device and install the bootloader that way and hope it accepts a basic OEM rom? Again, I'm no programmer, but am able to follow instructions and would love to be able to fix my 40$ mistake here sometime. Thanks in advance for all your help. I've used a lot of your tips and resources here over the years and have learned a lot from your skills and experience.
Related
First, sorry if this does not belong here. I did search here and Google and there were a few posts touching on this, but for the most part they were old and the issues were unresolved.
PLEASE Skip The Following (between ** and **) at first unless you really want to read it. My questions are at the end.
**
1. I say this a lot. Though I have abstained for the past week, since I first received my GTab, I have bricked it in various ways and always recovered (thanks to all the G Masters here and elsewhere).
2. This time I really do not know what happened. I added a new program and next time i rebooted ended up in a loop. No problem: I have been very cautious about making backups in CWMod regularly (and using NVFlash ever week or so).
a. Followed acceptable procedures to restore via CWMod. Nothing. Stuck in bootloop again.
b. Turned to ADB and NvFlash. Batch restored BL and the 11 partitions. Wasn't really paying attention to the screen at the time. No errors, all success. Boot loop again.
c. Went back and tried again, this time paying attention. Though the utility enumerates and formats all 11 partitions, it does not appear to upload the part-2.img and part3.img (Boot Config Table and Partition Table).
d. Those sound important so I tried to use the rawdevicewrite command (NOTE: beokit's NVFlash version does not include this command). It would not let me proceed without installing the bootloader again along with Part-2.img. That worked ... insofar as it did write the img to the partition.
e. Move on to Part-3.img. Tried to use --resume and it told me that the bootloader was bad. Tried to reinstall bootloader with it and it failed also indicating that the bootloader was bad.
f. Reboot--nothing but black. Fortunately I knew that ADB was still there.
g. Tried to use the NVFlash Format utility followed by Stock 3558 recovery followed by NVFlash - CWMod. Best I got was back to boot loop. Various other permutations including replacing Part-9.img with the boot image from CWMod backup.
h. Finally, I broke down and repartitioned the internal SD ... which, for some reason TBD, only took about 2 seconds. Reboot Recovery --> forgot about wiping the SD and decided to flash Vegan 7 right away. Install from SD-->choose file-->flash. Reboot ---> No loop, 30 seconds later fully booted. Second recommended reboot.
i. Wait a minute --- I installed from the SD Card that I just partitioned???? Annoyed that I wasted a good 10 minutes backing up the SDcard to my computer before partitioning, rebooted into CWMod and tried to repartition again. Success in 2 seconds. So Repartitioned again with different values (not 2048/0). Success in 2 seconds. And again back to 2048/0. Reboot recovery.
j. Navigate to SD card in CWMod. Still untouched. Installed Pershoot's kernel and booted in 30 seconds again. Currently in Titanium Back up restoring my 198 items...
**
I have the correct versions of NVFlash and CWmod.
Questions:
I . Why does NVFlash format Partitions 2 and 3 if it doesn't NVFlash then Restore partitions 2 and 3?
II. The only thing that got me out of the boot loop was to repartition my SDCard. Any thoughts on how this fixed the problem even though it did not actually repartition? And maybe why it didn't repartition (or why all my files were intact)?
At this point I would just really like to understand what went on? I am currently attributing success to the supernatural.
Also: This has been said many times before on here: BACKUP and REPARTITION your SD Card when nothing else seems to be working (especially when you are stuck in boot loop or frozen boot and cannot mount DATA partition in CWMod). Maybe it will help even if it doesn't actually repartition it at all...
Thanks!
Hi,
This is my first post on this website. I have owned a RCA Tablet (RCT6378W2 purchased on Black Friday from Walmart) for about 9 months now. Last night, while using it, it sort of stopped for about a minute. Then the screen had some lines on it, and the unit restarted itself. However, after this, it could not get past the RCA Boot Screen with the dogs on it. I tried leaving on this screen overnight with no success. Because the unit turns on and hangs on the boot screen, I figured it was likely a software or operating system corruption issue. Since then, I have figured out how to enter the recovery system v4.2.01 (holding volume + and Power). I have tried:
1. Wipe Cache Partition --- did not resolve problem
2. Wipe Data/factory reset --- seems to have been successful, but still not boot.
3. Apply update from cache -- there are no choices available to choose from.
It seems that unless I can find a way to make a self-booting SD card (is that possible?), then I am stuck with only 3 options (apply update from ADB, Update RKimage from external storage, and apply update from external storage). I have read many threads and websites, but have had no success. It seems that these are some of my obstacles:
1. I cannot seem to find a stock RCA rom image for this device. It appears that RCA has not made these available as other manufacturers have done. If you are able to find this, please send me a link!
2. I have tried to make a self-booting SD card using Phoenix Card, but can't find an .img that works with it. I have also tried using a generic sd card image and custom rom to install, but have failed at that. I have never rooted a device before or installed a custom rom.
3. I have tried looking for custom roms, but can't find one that is compatable with this tablet (seems they are mostly for the big name tablets). I have tried downloading Cyanogenmod for Nook Color (I heard this would work), but the recovery system does not seem to allow for any other firmwares to be installed (unless I am doing something wrong)
4. This tablet is not rooted, nor has the developer tool options been enabled (which I cannot do now that it doesn't boot)
Do you have any ideas? As stated, I am new to all of this, so please answer in detail if you can. Please help!
I purchased an HP Slate Pro 21 off of ebay that was freezing on boot, and it definitely is. My thought was if I could unlock it and load a different ROM, etc. that the problem may go away. Here is what I have done/figured out so far.
First power on, the device freezes at the first HP logo.
wiping the data (factory reset) allowed me to get into the O/S after several reboots
I was able to enable developer mode and USB debugging, at which point the device forces a reboot.
From this point, no matter what I do I cannot get the device to boot up all the way without freezing.
I can however, reload the factory image from HP's site (tried via SD card, and ADB just in case) and eventually through a multitude of reboots and freezes in different places (i.e. Boot Logo, Animated Boot Logo, Optimizing Apps) it will boot into the setup menus.
Problem is, at this point USB debugging has been factory reset to disabled. If I enable it, I'm back at square one and can't get the device to fully boot up.
There is a menu option to deploy image via ADB, and I can connect to it from my PC but it's (I believe, since I'm a noob) that it's a restricted mode for sideloading only.. Since I can see the device in the device list but it says (sideload) next it and the only adb command that I can run is to transfer an image. Problem is, I only have the HP image.
Are there any other steps to determine if this is a hardware problem? Further things I can do to try and get the device to boot? Other images I can try from ADB or SD Restore that will pass the signature check? (Since I can't load TWRP yet, because it's still locked).
Thanks for any help you can offer!
Good day.
I got a Nexus 5 D820 from my mom who dropped it in the river about a year ago at which time the phone was dead. It had indication of power but would not turn on. It was in a drawer powered off until yesterday.
I was able to power the phone on although it would not boot. The Google logo appeared and the android loading animation, but it would always reboot or freeze at different points. From the bootloader the phone seemed stable and I never had an issue pushing/flashing files. At this point I flashed a few different recovery images for the device, but only Philz would work, while TWRP and CWM would only freeze or bootloop.
From Philz I was able to flash a few different ROMS including the latest official one from google and also a few custom roms with/out gapps. None of these would boot and had the same freeze/bootloop at the google logo or android animation with no consistency.
I figured at this point possibly the sdcard had become corrupted/damaged by the water since I was able to flash pretty much anything I wanted. This is where things went downhill.
I followed a guide to use the partition editor from within an ADB shell. The guide assumed I was formatting an external SD card and suggested deleting all partitions. I did make a backup of the configuration of the partitions just in case but followed the instructions and removed everything. I was concerned what would happen once I rebooted the device at this point so I looked around a bit and it was suggested that flashing a google factory image would recreate the missing partitions so I didn't have to do it manually, so I rebooted thinking I could just flash the google package from the bootloader. This was the last time the phone ever showed any indication of working.
Now I have no indication of even power, no LED's, no bootloader.
Please let me know what you think... Thanks.
Before deleting the partitions, did you perform a full factory wipe before or after flashing different ROMs?
Does the phone appear as a device in Windows Device Manager when connected via USB?
If you deleted all of the partitions you deleted the bootloader partition.
I got my Nokia 3.1 in a bit of a weird situation trying to flash the stock ROM. I feel like it's a lost cause, but since I can still boot in recovery mode, there may still be a solution, I will explain in case someone can help.
It started when I tried to update from Android 8.0 to 10.0 (none of the previous OTA updates had worked and would always reboot in Oreo 8.0). This time, it didn't work and got the phone stuck in a boot loop.
The phone is still under warranty, but because I bought it overseas and there's no Nokia care centre here is New Zealand, I had no option but trying to repair it myself.
A wipe/factory reset didn't help, but after changing the active slot from B to A (using fastboot), it booted again in Oreo 8.0. Only problem is that I could no longer start a fresh Oreo 8.0 install without updating first and since all updates failed, I was stuck.
I suspect slot B is damaged or corrupt, hence the impossibility to update. To check it, I switched back the active slot to B after a factory reset, and that was not a great idea, the phone wouldn't even boot and looked hard-bricked.
But I still managed to use SP tool to download firmware, so I did that with the original Nokia 3.1 stock ROM (ES2).
However, I could not flash all files, I'm not too sure why.
I had the error message:
ERROR: STATUS_SEC_INSUFFICIENT_BUFFER
Verified boot is enabled
Please download signed image (sutinfo-verified.img) or disable verified boot
I didn't know how to do either of these, so I skipped the three problematic files: sutinfo.img, systeminfo_a.img, and cda_a.img (not sure what they do?).
It worked and un-bricked the phone, but it now boots to recovery mode only. What puzzles me is that I also no longer have access to fastboot, even when I reboot to bootloader (as if it skipped bootloader and went straight to recovery). I suspect it is because it still boots on slot B but I don't know how I can check that or change it back to slot A without fastboot access.
I tried using adb: adb shell getprop ro.boot_suffix but although it can see the device, it failed because it says device is unauthorized. I've tried all the fixes for this I found, to no avail.
So that's where I am, able to boot to recovery (but with adb unauthorized), able to flash firmware (except those files that must be signed), and unable to access fastboot.
I'm giving up hope that it's repairable, but I'd love to at least understand what happened, if someone has any idea...
Sorry for the long story...