After an unsuccessful descent from v20 to v10 is currently in CWM Recovery. Trying different combinations of keys but the phone still turns on only CWM .... (Do not have an android, EMERGENCY) Previously I had cwm 6.0.3.0, now when I try to install AVATAR'a 4.3 i have CWM 6.0.3.2 but Android still does not get up ....
I also tried many many other ROMs upload from CWM but on the same (still enter to CWM).
Laptop detects the phone as the Google Galaxy Nexus ADB Interface (driver is properly uploaded), when you try to install ROM through KDZ unfortunately the phone is undetectable. I tried to install on CS_EMERGENCY, DIAG, EMERGENCY - no response from the phone.
Any ideas ?
Related
[Q] I cannot boot EURO Tab anymore. Always landed into Android system recovery <3e>
Hallo all. I've been searching this forum for solution and I've not found any. My GTab cannot boot normal any more. Every time it lands into Android system recovery <3e>. Please help me. I'm really frustrated.
How it started:
I ran ROM Manager to check whether there is support for EURO Tab (no supprot yet). Then from inside ROM Manager I booted into recovery to do a nandroid backup. Unfortunately no nandroid is there. When I did reboot GTab cannot start anymore. Everytime I boot I land into Android system recovery <3e>. Booting into downloading mode is also not possible. I've tried many times. GTab only boot into recovery <3e>.
I have Galaxy Tab EURO, rooted, updated to JM6.
hello!
have you flashed the international kernel before? if u did so and u want to revert all, u can flash with heimdall a stock kernel and a stock secondary bootloader (boot.bin and sbl.bin) from JM6! maybe u need to reflash the whole firmware with heimdall or Odin, whatever u like better!
Thanks for reply. Actually I did flash the EURO ROM three weeks ago. I did nothing recently. I only booted into recovery via ROM Manager and since then GTab cannot boot normally.
I tried Odin already, but no success, because I cannot switch into downloading mode, but recovery. I tried with adb shell, and cannot find the directory /data.
I have rooted and flashed the EURO ROM on my Gtab as well; and I am having the same problem finding a ClockworkMod version compatible with this ROM. I've tried AT&T, TMobile, and Verizon versions of ClockworkMod. I preordered from UK, so I didn't expect any to work, but it doesn't hurt to try.
Anyway, I run into a similar problem as you on reboot. I get to system recovery and it "sticks". However, if I press the HOME key a few times, it will reboot normally.
Still no recovery, still no nand, but at least the Gtab is functioning. I guess I just wait on a EURO version of recovery.
Ever since my installation of a wrong firmware on my F320L (Korean variant) a few months ago, I can´t get into stock-recovery any more. At that time I didn´t install CWM or TWRP, nor did I flash any custom ROMs, but something must have broken the recovery along the line. Since then I could never get into recovery mode or use the hard factory reset function, even though after installation of the right firmware for my device, everything else worked fine again. Download mode too is OK.
Now I have recently flashed stock-firmware (F320L 11c), rooted and installed CWM 6.0.4.4.
Interestingly I can´t access CWM via the hardware-keys either, just as the problem before with the stock recovery, but I can get into CWM if I use the adb command to boot into recovery.
But in order to do that the device must be fully functional and bootable, otherwise adb won´t work. I am a bit concerned that if anything happens and I were to soft-brick my device, I wouldn´t get into CWM-recovery any more, since it is not accessible via hardware key-combination, but only over the adb-command.
Anybody got an idea how to solve this issue?
Hello.
I write to you because I have a big problem with mi LG G2 D802.
Yesterday I tried to install a CRM apk to use in a signature of the University. I was using CM11, but the apk had failed. So, I restored my ROM STOCK backup and when the phone start, a new update was downloaded and installed. Then, the phone only enter in recovery mode. I tried the different wipes, restore again ROM Stock, install again CM11 ROM but the problem was not solved.
I tried to enter in bootleader (pushing vol+ and insert the usb cable), but the phone reboot in recovery.
Now, I don´t know why, the phone is empty. I tried to restore ROM Stock backup from USB OTG but the recovery don´t recognizes the folders.
Please, can anybody help me? I need the pone!
Thanks.
Regards,
Nicolas.
Hmm try to install a clean ROM using adb sideload... If that doesn't work then you might have to use kdz to flash to stock
have you tried this if it doesn't work you will need to go back to stock using kdz/tot method
TWRP 2.7.0.0 Loop
Thanks for your answers. Luckily I solved the problem with .zip archive downloaded on the web.
Now, you can close the thread.
Thanks!
lg g2 att rooted with stock ROM
i actually already found a fix here
http://forum.xda-developers.com/showthread.php?t=2451696
but i tried it and it didn't work.
the phone connects fine to my computer and ADB works even though it's in recovery, but after copy/pasting the code i'm still getting the same problem.
i've tried a full wipe, and trying to install an old backup. i've tried installing the stock rooted rom again, still ending up at CWM recovery.
any other options?
Hello,
I am having some problems since today i flashed the su binaries over my completely new lineageos install. (a14.4, fully wiped before).
it was stuck during boot at the android logo(let it boot for half an hour, multiple times, no progress). so naturally i wanted to boot to recovery, though it would not boot into recovery with any imaginable key combo.
so i went into bootloader mode (which, in my case, is jsut download mode, no fastboot whatsoever, and yes, i checked fastboot devices, (also adb), nothing to be found there)
next, knowing i had no other choide at that moment, i flashed a stock rom, via download mode. worked so far.
stock rom was running (ics), bootloader was still download mode only, and recovery was now stock android rec.
my next step was flashing a custom rom, since this was the most important thing to get to working then.
via adb sideload i fashed lineageos, once again. was working fine, so recovery next. but nothing worked.
included with lineageos is root access, so i enabled all the stuff, incl. adb, on my phone. but adb sideload always spit out errors (code 7 or 255) on rec install (twrp 2.8.something touch.zip) [some error about /tmp/update.zip] trying cwm resulted in the same thing, like did flashing gapps.
pushing the files to the internal memory (/sdcard) did not help, since 'flash from sdcard' resulted in an empty sdcard folder with no files to install (in recovery. in the file explorer while running the os, the files where there)
then i tried rashr (not sure exactly which app it was) to install rec. it said everything worked fine, trying to install cwm. so i rebooted
and nothing worked. the rom would not boot anymore (again, stuck at android logo) since the stock recovery only allows for adb access in form of sideload, no push whatsoever, and sideload did not let me install the os via zip, it was back to flashing a stock rom once again.
so i did that again (this time lolipop)
this is where i am now:
the rom boots perfectly, like does the kinda stock recovery, but again: no files in the sdcard path within the rec menu, though i pushed them there, and they appear there in the file manager.
i installed root, for those neat apps, that maybe one would work, but they need root and the stock rom does not know how to give those rights to apps, no option found for this whatsoever.
also, download mode is gone. (still no fastboot)
when i try to boot the bootloader, i just goes on to usual os boot (key combo and adb reboot bootloader result in the same thing)
recovery is still working, but pretty useless still. when i try to sideload a file, it quits with failed verification of the file. which is no surprise to me, since it shows the message halfway through the send process (observed from the adb terminal on my pc, never gets even close to 100% before the message appears on the phone which also cuts the connection therefore the file send process.)
i have absolutely no idea what the hell will get this working again. i dont really care about the download mode, but what i really need is a custom recovery to finally work, so i can install all of my stuff again.
does anyone have any idea on what i could try next?
hopefully yours,
azyrael
SOLVED
so i noticed for root apps i need to install supersu (or something like this) to give root access to apps if there is no native way within the rom to do this stuff.
install supersu and found out i somehow had no root access at all. tried ioroot etc, did not work
so i installed a stock jb android rom, rooted the device via ioroot, install recovery via autorec, and it finally worked!
this took me only two days.
thx xda for providing all of the tools i needed for this <3
kinda unsolved
so, it got recovery to work. installation of lineageos also worked perfectly., though this bricks my device.
no matter what i wipe, installing a custom rom will stop it from booting. this could only be fixed by installing a stock rom again, which also reverses root and install a stock recovery. since i only need root and the rec for installing a custom rom, which does not work anymore, i wont bother with this anymore. i have abosutely no idea whatsoever, and tried everything even barely coming to my mind.
still open for suggestions, but the stock rom will have to suffice for now.