[Q] LG E400 stuck in CWM boot loop - Android Q&A, Help & Troubleshooting

Hello friends
I am not very well versed with Android platform and OS. I had CWM ver 5.8 installed on my phone but I never used it. The ROM is Stock ROM. Today, I got a notification for update and I did the same. As after downloading the phone rebooted, it got stuck in CWM Boot loop.
I have searched Google and tried to use "adb" and "fastboot" a number of times. As I input the command "fastboot flash recovery recovery.img" I am getting a "<waiting for device>" and then nothing is happening. I have the USB driver for the phone insatalled and I am using a PC with Windows XP SP3.
Please help me friends, I am in real trouble.

Related

[Q] HELP!!!!

I flashed froyo safe will not brick rom by Eugene and now im stuck on "recovery mode, but cant do anything really . need help here at first i still had adb shell access but seem to be having a driver issue now when i try 2 boot i get Vibrant boot logo then i9000 boot logo then stock recovery mode, im running win 7 32 never flashed froyo prior and was running kernel-vibrant-stock.tar, withe stock some one please help.... even if its just getting back to dl mode so i can use odinat first adb was fine now im having a driver issue please help........
When you are in the recovery, unplug the USB from your computer for a few seconds, then plug back it, then in your terminal window type: "adb reboot"
Please go easy with the font, its abrasive.

[Q] Help Phone stuck in bootloader screen ZTE

I was upgrading the current Stock rom on my ZTE Nubia Z5s Mini, I went through the recovery mode to load the new rom and got a message saying that the rom installed correctly, I rebooted the device and now its stuck at the MIUI logo or if I try to load the recovery mode I get the Nubia logo just to load back to the miui logo again. I got the rom from the MIUI site its v5.
I've left the phone for over an hour hoping it was just loading up but no change, the phone heats up and even has a charger screen when plugged in.
Anyway to get back into the recovery mode to load the original rom again or any other way of fixing this? help :crying:
I've no idea how to help you with this but I'm bumping the thread because I know how you feel.
Sent from my HUAWEI Y536A1
I'm trying to flush the rom by using adb but with an issue, even thou my device is recognized as Nubia Z5s Mini in device manager it still gives a driver error "these have been installed" and in cmd adb it does not see the device.
Update : Got drivers for install from Clockwordmod website but it will only accept the drivers if I set the phone as a modem in device manager when installing them, still not recognized by adb using CMD.
Solved driver issue and qusb_download issue, ADB drivers are done through all drives in device manager pointing to the Google USB drivers and select adb interface then run CMD from within the Google SDK program folder in platform-tools to read the device.
Now using emmc but need to generate EMMCBLD.HEX & 7x30_msimage.mbn if anyone can help, I can enter adb using recovery mode but blocked from making changes in fastboot mode, currently in download mode which can see a drive H but need the two files to proceed any further.

Vodafone Smart II aka. Alcatel v860 stuck on bootloop

Hello, yesterday i tried to install a custom rom on my smart II through recovery -> update.zip (i changed the rom.zip to update.zip, bc i can't access bootloader/fastboot) but i think i messed up , because after rom being succesful installed I factory resetd it :/ , after that i rebooted and got stuck in bootloop, i've tried some stuff, but i don't want to mess it up even more, I've tried using cmd with adb commands, trying to get some response from the device to the pc, but when my smart II is on loop if i do ("fastboot devices") it shows the id of my device, but when i tried to used toolkit to flash recovery it's stuck on this message (<waiting for device..>) something like that, and never recognizes it. i'm able to provide more information if needed,
thank you!

Unable to access bootloader

Yesterday I tried to flash a a new rom on my Xperia Z2 (unlocked bootloader).
From TWRP I did an advanced wipe and selected basically everything except my mircoSD (because it has the new files).
After a long time of waiting I tried to flash the ZIP file and it gave me an error. I thought this had to do with the wipe so I decided to reboot my phone.
As you can imagine, it got stuck on the Sony logo (because system would be empty).
From this moment I couldn't do anything with my phone, except from the tool Emma.
I now have some clean installation of Sony their Android 6.0.1 for the Z2 (23.5.A.0.570) but Im unable to flash TWRP through fastboot.
The command adb devices shows my phone, fastboot devices gives an empty response.
When I restart to the bootloader from adb and try to flash TWRP I get the message "< waiting for device >".
I tried on three different PCs including a clean install of Windows with all kind of different drivers, yet I cant get fastboot to work.
Am I stuck with this unrooted version of Android now or do you guys have any suggestions for me?
Thanks in advance!
Install drivers correctly
EugenStanis said:
Install drivers correctly
Click to expand...
Click to collapse
As I said I've tried all kind of different drivers (Android tools, Sony drivers and flahstool drivers). So for me it's hard to tell what I'm doing wrong.
My computer notices the phone (if I hold volume up and attach the charger), it just doesn't show up under fastboot devices.
EugenStanis said:
Install drivers correctly
Click to expand...
Click to collapse
Okay, apparently it was because of the driver signature stuff in Windows 10.. The fastboot command now works fine!
Next problem occurred though, flashed the newest TWRP recovery but as soon as I enter "adb reboot recovery" my phone just normally boots again..
Why do things never work out the right way for me as they are intended..
PaulusE said:
Okay, apparently it was because of the driver signature stuff in Windows 10.. The fastboot command now works fine!
Next problem occurred though, flashed the newest TWRP recovery but as soon as I enter "adb reboot recovery" my phone just normally boots again..
Why do things never work out the right way for me as they are intended..
Click to expand...
Click to collapse
Manually boot into recovery by booting up your device normally and when you see a violet LED, press vol+.

LG G Vista VS880PP Phone Security Error 1003

I Flashed TWRP Recovery onto my Rooted VS880PP Phone, but when I try to boot into it I get Security Error 1003 error message on my screen, and the phone freezes on that screen. If I remove the battery and restart my phone I can boot normally into my rooted Android Lollipop system, but I have no access to Recovery. Also I do have a computer running Windows 10, and ADB Fastboot Installed.. When I connect my phone to the computer ADB recognises the VS880PP Device. I need help getting my phone to boot into recovery. Thanks in advance for any assistance you can provide.

Categories

Resources