Hello,
I accidentally flashed a Rom CM 10.1 after a CM 10.2 Rom.
Unfortunately, the tablet does not boot now.
I can get the tab only by fastboot, ADB impossible.
I've already flashed CWM via fastboot several times, unfortunately without success.
Is it possible via fastboot commands to set up the tab completely new?
Related
Yesterday I attempted to update my Xoom to the newest EOS nightly. After installing/wiping/rebooting I found myself with the RSD mode 3 problem. Having encountered this before I used ADB to flash a stock boot & CWM recovery. After this I have tried to flash several different roms (EOS 3/ EOS 4 nightly/CyanogenMod nightly) but each time the device gets stuck at the boot logo, not the motorola dual core screen but the actual ROM boot logo. Any ideas what I should do/try next? I'm sure there must be a simple solution to this, I just don't know/can't find it
Hello all.
I installed succesfully CM10.1 on a Galaxy Tab 2 7.0 P3110 of my friend then, when i rebooted in recovery using the power off menu in CM10.1 it bootlooped.
Now i can't go in recovery or download mode.
Just the pc when i connect it with usb cable reveal OMAP4430.
This is similar to my LG P920, usually in this way i was able to flash fastboot u-boot and then flash again the system.
Is there a fastboot for P3110?
Have you any solution?
----------
Edit, solved, was just the battery low.... sorry for the inconvenience
Hi everybody,
I "had" a rooted Moto G, with the stock factory rom (updated to 4.4.3) and the FAUX kernel,... :good:
Yesterday I tried to flash cyanogenmod 11 (the last nightly), with the correct gapps and an Xperience Kernel. But I had a bootloop (endless rotating arrow of CM11). In fact, my recovery had not correctly wipe data/factory reset,....
So I used fastboot to wipe all what i had done and to start all over again (fastboot -w)...
After other mistakes, I can't access adb (the device isn't recognized), and even fastboot is not reachable (i've got an error in my device manager: "Fastboot Falcon S unknown").
So here is the situation: No ROM, No adb, No fastboot, the only thing i've got is the bootloader screen!:crying::crying::crying:
Help me plz I trust!
Hi, My moto g (XT1032) was previously running Lollipop 5.02 with a custom kernel. Also using TWRP.
I was trying out a new kernel and rom, I backed up my phone before I did all this so I went ahead and tried to install CM12 this failed so I recovered from the back up and now I am stuck in a bootloop and can not access recovery.
As soon as I try to access recovery the TWRP splash screen appears but then boots normally!!
ADB is not recognising the device whether I use Moto adb drivers or universal ones!
Really need help, would greatly be appreciated!
(Just trying fast boot, will update if no success)
Liam
Amateur developer (tinkering with kernels )
I think you ****ed up
ADB commands only work in recovery or when the phone has fully booted the OS.
Have you tried to flash your phone's stock 4.4.4 ROM? Do not flash anything older.
Hey guys, I'm trying to port CWM to galaxy A5. I tested it by flashing the recovery with odin about 5 times, but odin flashed it to bootloader (download mode). The problem is that when I rebooted my phone (my ROM is CM13), it stucked on bootanimation. I've tried flashing stock ROM and it booted fine, I've tried flashing CM12 and it booted fine, but when i re-flashed CM13 it stucked on bootanimation. I think that it isn't a ROM problem, because before testing the CWM recovery it worked well. I've also typed adb reboot bootloader (I know that samsung devices doen't have bootloader, but I was curious to try it ). So, I think that I've damaged some partition but I need help.
Sorry for my english, too
DeadSquirrel01 said:
Hey guys, I'm trying to port CWM to galaxy A5. I tested it by flashing the recovery with odin about 5 times, but odin flashed it to bootloader (download mode). The problem is that when I rebooted my phone (my ROM is CM13), it stucked on bootanimation. I've tried flashing stock ROM and it booted fine, I've tried flashing CM12 and it booted fine, but when i re-flashed CM13 it stucked on bootanimation. I think that it isn't a ROM problem, because before testing the CWM recovery it worked well. I've also typed adb reboot bootloader (I know that samsung devices doen't have bootloader, but I was curious to try it ). So, I think that I've damaged some partition but I need help.
Sorry for my english, too
Click to expand...
Click to collapse
Anyone?