Tablet hangs in Bootloop after installed cm9_nightly_20120721 + protab2xxl_compatibility_1.2.0 startet from cwm 188.8.131.52. Noticed that the "/data" partition only has 15MB of Space with 0B Byte free. I wiped the cache after installation with cwm, i am not able to boot to cwm again because key combinations not work on this device.
Got a T15A Generic tablet which has the same Hardware than protab 2 xxl, Goclever A103, Coby 1042 etc..how to get CM9 or CM10 running?
- bought a Thomson QM734-8G tablet (Allwinner A13b clone), running Jellybean 4.2.2; - PC interface worked fine in MTP and large storage modes; - setup Android SDK & Java JDK on PC and communicate with tablet via ADB;
All OK so far..After a couple of days, I decided to replace stock recovery with ClockworkMod Recovery, so I could start messing about with the tablet.
I found the CWM 184.108.40.206 mod supposed to work with these tablets and, following instructions, determined it was indeed running on sun5i hardware and had 10 partitions (nandj) and downloaded the appropriate version.
I used ADB sideload to install CWM and everything appeared to work OK ... until I rebooted and found myself stuck in a never-ending cycle of CWM-based recovery bootloop.All I get is the CWM recovery console, with a few lines of error & the tablet will go no further.
E:can't mount /cache/recovery/command E:cant mount /cache/recovery/log E:cant open /cache/recovery/log E:cant mount /cache/recovery/last_log E:cant open /cache/recovery/last_log
CWM functions work properly and nothing will mount through the 'Mounts and Storage' section, although sideload mode still seems to work.Attempts to use ADB sideload to install a different CWM or other recovery image have all failed, and LiveSuit and PhoenixSuit both have issues detecting the tablet (despite trying various versions of each & following instructions precisely), so I can't flash a replacement ROM to fix things.
At the moment, I just want to rip CWM out and go back to factory recovery mode and have a working tablet again! I think the Bootloader is locked and the tablet is unrooted. Superuser or SuperSU don't want to install properly. However, using ADB, it looks like I can get root access in shell (#).
I have an Allwinner A10 clone (Kurio 7), it is designed for kids but otherwise a standard android tablet. After hours of googling I rooted and installed CWM & Gapps (not included in the stock ROM). So far so good. The stock ROM was causing issues with some apps, it needed to go.
I flashed CM10 and it worked but no touch screen. It needed a compatibility flash to make it work. You can guess what's coming. I picked the wrong one and now the device does the following:
Reboot loop Black screen (backlight though) PWR+Vol up no longer gets to recovery Vibrates constantly between reboots (due to wrong patch I'm guessing)
ADB picks up the device for a split second between reboots but "adb reboot recovery" does nothing. Even when using wait command. Tried "fastboot flash recovery cwm.img" after wait command, no luck. Is there anything else I can try?
I am trying to use my cheap virtually unbrickable tablet to learn more about kernel development and eventually ROM building.
I have extracted the manufacturers (WoPad) LiveSuit image and used split_bootimg.pl to break up the boot image.
I extracted the config file from the kernel image using extract-ikconfig and it created a config file. I didn't see the config in /proc.
So, I have the factory ramdisk and the factory kernel config.
I have downloaded several kernel sources (lichee-3.0.8, ChritianTroy's 3.0.36, and another one from linux-sunxi 3.0.72). I can successfully compile all of them without errors and they all generate zImages, uImages, etc using the factory config as well as the sun4i_crane configs they come with.
When I repack the boot.img with the newly created kernel and install it on nandc it wont' boot past the android icon (u-boot). When I compare my boot.img to the factory one, they both have the same offset where the kernel starts (0x00000800). I have also ensured I'm replacing the kernel modules when I'm changing kernel versions.
I own a Allwinner A13 7 inch tablet, on which I installed the Cyanogen 10 mod (Due to restrictions I cannot place the link to the mod)
The problem is I probably installed the wrong touchscreen driver, so the tablet boots perfectly into the Mod but I can't do anything. Normally it would be no problem to just put back my backup, but I can't get it to boot into CWM.
In the first place I rebooted into CWM to instal the mod by adding the following command through the "terminal app" before rebooting,
I received a generic Chinese table. it worked well for about two-and-a-half months. Then, just recently, I discovered rooting and the wonderful things it allowed you to do. I decided to download a system-tweak app, which included a CPU control. I was a little wary of overclocking my CPU, having heard it may decrease its life expectancy, but finally I thought "What the heck?" and in a brilliant stroke of genius cranked my 1Ghz processor up to 1.5Ghz, and it promptly froze, forcing me to power it down. When I turned it back on, I discovered that it had been factory reset. I re-installed my apps, including the system-tweak app, and decided not to touch the CPU controls for a while. Soon after, while at my sister's talent show, I discovered I had about 30% battery life, and I was still supposed to record her. So I figured I'd underclock it to save the battery.
Unfortunately, as my finger touched the slider, my brother bumped my arm and caused me to lower the CPU frequency to its lowest setting. It became extremely sluggish, almost to the point of being unresponsive, and finally I had to shut it down. When I restarted it, it started to boot but then got stuck on the shimmering Android logo, and now that's all it does. I can't even boot into recovery mode, and unfortunately I had just turned off USB debugging that same day.
I recently just rooted my evo 3d sprint with the the boot 1.5 and everything went well. I decided i wanted to overclock my phone so i followed zeemaxs way. Before going into the overclock procedure i decided to do the the RCMIX Evo 3d kernel v. 2.2.3 first so i would have better results when done with the overclock procedure.I boot-up the kernel through the recovery mode on the phone butit failed to load so i just rebooted. After that my wifi and 4g stopped working. So i downloaded an app on the market called "flash image GUI" which lets me flash the kernels through the app. I flashed the RCMIX kernel and rebooted and now im stuck ima boot loop. I COULD just go back and back up to my old rom and settings etc but the problem is i dintmake any kind of back up or recovery i think.
I was running Team Jellybeans V5 No Problem for the last little while (on my T959d)Everything worked great (minus a few glitches here and there of course)Saw the update for V6, downloaded, and flashed with CWM.
Did the wipes, (cache, dalvik and factory) did the wipes again after reboot,Now Im stuck in an infinite bootloop, (goes to samsung splash, then Devilkernel Splash, then CWM where it shows cannot mount e:/ (cycles too quick I can't see it..) then it just reboots and continues, I can't boot the phone into CWM recovery, can't boot into download mode, tried USB JIG, doesnt do anything,I can't adb my phone, can't ODIN..
I spoofed my device S6312 to galaxy nexus using network spoofer to download an incompatible game from google play store.According to network spoofer everything worked great but nothing actually happened and that game was still incompatible on play store.So I launched network spoofer and told it to recover my device again to S6102.It said that the device will reboot so I gave it permissions and my device started rebooting but it stop at the Samsung logo and was doing the same thing again and again so s actually boot looping. How to recover my device and any way to do it without a computer.
My galaxy s3 is rooted and cwm installed.I have changed a default dpi and rebooted to find my self in constant boot loop.I'm at the brink of flashing my rom to a custom one to see if it works but very scared to do so especially not knowing much about it.I have performed hard reset by going into recovery mode but it didn't work.
I have an Android tablet (Diablotek D2-721, very cheap I know, but it serves its purpose) that is stuck in a boot loop. The real problem here is that this device apparently does not have any sort of recovery mode and being in a boot loop means it does not get recognized by ADB or any firmware flashing software.
I researched all day yesterday perusing forum after forum but almost every single solution requires booting into recovery.
I had been flashing roms with 4ext recovery since you can just use smartflash but after the last time I flashed a rom the rom wouldn't load and just kept rebooting the phone the the htc screen over and over again
i m using sony ericsson xperia arc s i have rooted my phone few days ago everything was ok i have root through flashtool method and i think 587 kenel was used. i dont know about roms kernel n etc etc i have read the thread and root my phone last night i tried to install font changer i granted superuser request and phone is restarting and then stuck on bootloop first it shows sony screen and then xperia screen and again restart and this process go on what should i do
I have a bricked Samsung Galaxy S2 and have been doing some research on how to fix this. There is a lot of info online, but I don't understand most of it as it is too technical and I need having it translated into layman's terms!
- Galaxy S2 (GT-I9100) - Unlocked - Purchased from Kogan 2 years ago (no longer under warranty) - Appears to be Polish stock based on the packaging and manual - I am in Australia
- Phone is stuck in boot loop, unable to get past the intro flash screen that says Samsung Galaxy S2 GT-I19100.
- It keeps resetting itself and going back to flash screen infinitely. I need to remove the battery in order for it to stop doing that.
- I'm unable to get into the mode that would allow me to do a factory reset, however I am able to get into download mode.
What I think I need to do, but need verifying:
- Download Odin onto my PC. (I think Odin is software that allows me to access the core of the phone via my PC, is this correct?)
- Download the correct version of the operating system. From what I can gather, there are different versions depending upon which network you are with. Because my phone is unlocked, I need to get an unlocked version but I'm not sure whether I should get one designed for Australia or for Poland (or whether it matters)?
- Connect PC and phone via USB cable
- Turn on Odin
- Somehow use Odin to reinstall O/S on my phone
- Are the steps above correct or am I missing something?
- Does it matter which version of Odin I install or can I just do a google search for Odin downloads?
- Where do I find the file I need to reinstall the O/S?
- Where can I find instructions on how to use Odin once I have the correct file to install?
i had a custom rom gingerbread and then i wanted to do a factory reset to go back to the stock room , instead this give me big problems. it is stuck on the lg screen and i try to go into recovery and alit says is do not pull out battery Formatting data , Formatting cache and Factory reset and this it goes right back into the lg screen where it gets stuck . My computer recongizes my phone but i dont know how to use adb commands thing like a pro . i have everything i need in the folder "backup" in the clockwordmod folder .
I installed the stock firmware on my Galaxy Pocket(i.e., XXLF5 Version). Then this morning i downloaded the MakDroid ROM. and installed it through CWM recovery. But after that my phone just keep restarting to the SAMSUNG Logo and freezes there after vibrating several times..
my nexus 5 is stuck in boot loop ( turning on and off by itself and can't get past the Google icon) and i can't access the boot loader for a reset. all system reset/ factory image guides require me to access the boot loader but the problem is that the phone won't stay in the boot loader because of the boot loop, it turns off as soon as i get into the boot loader.
I have a Lenovo P780 (chinese base rom) 4gb version. Rooted it and installed with CWM recovery for P780. Installed Muse UI 3.0 custom rom from custom recovery via sd card. Swapped the internal SD with External SD card by editing the vold.fstab and vold.fstab.nand also.
However, I realised that there are a lot of bloatwares that took up the RAM and started uninstalling chinese apps that seems to come with the custom rom from system. However, when I restarted the phone, its now unable to boot beyond the 1st boot screen. (Boot loop)
Current state of the phone now:
1. Able to enter custom recovery mode, but menu is blank except for the navigation commands. (return, up, down, confirm) 2. Able to enter adb only when the phone is in custom recovery mode. 3. Able to connect to PC (Windows 7 64bit). Mediatek MT6589 usb drivers installed. Many versions of sp flash tools installed and tried. 4. Can't seem to enter fastboot for this phone. (Tried many key combinations. Only Meta mode, recovery mode and factory mode are found)
Things I had tried:
1. Flashing stock rom. I had downloaded the stock roms and tried flashing with sp flash tools, but I always encounter the following errors. Had also tried switching to another windows XP based pc and still encounter these errors. (a) Firmware -> upgrade. Tried Auto Format Flash also and it returns with the same errors. - BROM ERROR: S_FT_FORMAT_FAILED (4010) Format flash error. Possibly given wrong format range. Please check your format settings.
(c) Download (only one img checkbox ticked, tried system.img and recovery.img) - - BROM ERROR: S_FT_DOWNLOAD_FAIL (4008) Download to flash fail!
2. Flashing recovery from adb terminal via windows and usb connection When I put the phone to the custom recovery (with missing menu options), the adb terminal is able to recognise the phone and returns the following after the command 'adb devices': 0123456789ABCDEF recovery
Upon entering the shell via 'adb shell', I am given the # sign. (already in SU mode?)Tried to flash a recovery image from this mode via terminal command flash_image, but encounters the following problems:
(a) unable to mount/remount - mount -o remount rw /system mount: mounting rw on /system failed: Invalid argument
I recently picked up a C800g to tinker with, and was able to install CM9 on it. Everything was working fine until I rebooted: It appears to re-flash the OS every time I restart, wiping all settings/apps, etc. None of the key combinations seem to yield 'recovery' mode any more, and though adb works, it just runs through the same start process (shows the 'LG' logo twice, then the cardboard box + arrow + robot + progress bar, and boot to "factory" state.)
Even after I removed the 'update.zip' file on the SD (this seemed the obvious culprit), it continues to re-flash on every boot. I can't seem to get to fastboot, as it goes through the same startup every time ('adb reboot bootloader', while 'fastboot devices' never picks up anything.)
Outside of keeping the phone powered up, I seem to be in a weird state -- but I can't seem to get out of this cycle (I'm thinking I should be able to 'dd' cwm to one of the partitions, but I haven't seen reference as to which it should be.)
i bought a white Samsung galaxy tab 4 7.0 8gb white from Canada and i decided to turn ART on so i did and the tab was stuck on the boot animation for over 30 minutes. So i went into recovery and deleted cache and data. It booted up fine and i was relieved. Before i did anything on it i turned on ART again and it boot looped again, stuck at the boot animation. This happens every time i turn ART on this tablet. No i am not rooted and i don't have any custom ROM, kernels, or recoveries on this tablet. try turning on ART on their galaxy tab 4 7.0 and see if ART works?
My Samsung Galaxy S3 (GT-I9300) was rebooting itself for the past few days, randomly. Last night, it did it again, but didn't boot back up. Instead, it is now stuck on an infinite boot loop - it gets as far as the splash screen (Galaxy SIII logo), then reboots, on a loop.
I've never tried to flash or root the device, I only used the official OTA updates from Samsung.
The first thing I tried was to remove the battery, SIM card and MicroSD card for 5 minutes. I then wiped the Cache Partition through the Android Recovery Mode. I then flashed using the Samsung Kies recovery procedure. This didn't work. I then tried a Factory Reset through the Android Recovery Mode, multiple times. This also didn't work. The last thing I tried was to flash the ROM using Odin3. I used the firmware version appropriate for my region and carrier. Everything was successful, but I'm still having the same problem.
I tried to view the boot logs with adb, but of course, the phone won't stay on for long enough to establish a USB connection. I'm not sure what else to try.