Recovery - AT&T LG V10

Hey, with the new MM update I thought, well I might as well try to see if commands work for it via ADB... and sure enough [ADB Reboot Recovery] works, where in 5.1.1 it didnt for me. It rebooted into this dark screen, with a little scared lookin android bot with a red traingle above his chest. D: poor droid. Well, I wondering what this means. Anyone?

It means you got the phone to boot to recovery. Not much you can do in the stock recovery
Sent from my LG-H900 using XDA-Developers mobile app

Related

Cant boot up To clockword recovory?

Im kinda new to this guy so plz bare with me:/. Ive rooted my phone before by super one click, and also installed a app called "Absolute System Root Tools" and couple rooted apps, n from absolute app i would click "Reboot into recovery" and of course would take me to that orang android. But now that i try doing it by holding down volume and power. Nothing happens :/, all its been doing its factoring reset. Even if i do it from the absolute app, nothing happens just restarts normal. Can some one help me out here what i need to reboot to recovory, would appreciate it and plz bare with me bearly getting into this.
No worries. I was there last week
If you have CWM already installed, you should be able to just HOLD power + volume down at the same time until the boot screen changes from LG > ANDROID and some icons (then you can let go of both buttons. Try that.
Did you flash CWM properly through the NVFLASH tools? http://forum.xda-developers.com/showthread.php?t=1056847
Or did you just install CWM the soft way through an app in the OS while it was running like you would through Rom Manager? For Tegra devices this isn't a proper recovery flash and will not work correctly. Recovery flash needs to be done through NVFLASH.
Yeah I got ityalready guys, took me all night till 8am to figuered it out and finally installed my first rom thanks for the help by the way.
Sent from my LG-P999 using XDA Premium App

Not able to boot in recovery menu

Hey guys,
I hope I'm not missing something obvious because I spent the last 2 hours searching for a solution.
Today I decided to unlock and root my Motorola Xoom 3G (EU-version, stock-android 4.x).
I unlocked it using fastboot and flashed the CWM recovery. But when I try to enter the recovery menu by pressing volume down when the Motorola logo apperas, it just says "Reading ODM fuse: 1". After that, it shows me a picture with an red exclamation mark.
I have no idea what to do now. Since I have no ADB access, I'm not able to do a "adb reboot bootloader" to flash CWM again.
Do you guys have any clue what's the matter? Thanks in advance
prisoner627
im assuming your xoom still boots up? if so youll still be able to get adb to work, just try flashing cwm again , you can also get fastboot working by turning the xoom on once you see the motorola logo count to 3 then press volume up and itll start fastboot protocol support
Sent from my Xoom using XDA Premium App
Right, I forgot. It still boots up but I can't get through the lockscreen. There's a message saying "device not ready. please enter a valid sim card".
right unfortunately i cant help with regards to sim card error as i own the wifi only model but someone a bit more knowledge able will see this and may have the answer
have you tried putting a sim card in? what does it say if you put one in?
Sent from my Xoom using XDA Premium App
Alright, I didn't mind the branding. With a T-Mobile card, I am able to enter the PIN and use the Xoom as usual.
Before I really mess up, can you tell me what to do next? Unfortunately, I don't have a micro sd card here so I am not able to do the "Universal Xoom Root" ( http://forum.xda-developers.com/showthread.php?t=1242241 ).
ok so youve unlocked the bootloader using fastboot oem unlock?
Sent from my Xoom using XDA Premium App
Yup, unlocked it is.
ok next step is to push recovery via adb have you tried doing that again?
Sent from my Xoom using XDA Premium App
recovery via ADB? I tried the CWM recovery image via fastboot last time ( http://forum.xda-developers.com/showthread.php?t=1074979 ).
yea you connect your xoom to pc let it connect etc etc, then open a command prompt in same folder where your adb files are located then type
adb reboot bootloader
once rebooted into bootloader
fastboot flash recovery recovery ( name of recovery here)
make sure youve downloaded the recovery image and not the zip file
Sent from my Xoom using XDA Premium App
Alright I did everything, no errors. But when I boot into the recovery, I still get "Reading ODM fuse: 1" and the exclamation mark...
try a different recovery perhaps? theres a few on here ill see if i can find one i used and post link
Sent from my Xoom using XDA Premium App
Yes I already thought of using the recovery of Team Rogue but it comes as a zip file, so I can't flash it, right?
cant flash it without entering recovery, im not sure what cauaing the problem , when you hold the power button and you get shutdown reboot etc if you press reboot do you get a second set of option ?? reboot,recovery bootloader etc?
Sent from my Xoom using XDA Premium App
You mean pressing the power button in normal usage, on the homescreen? I only get to decide whether I want to shut down the device or not. But this wasn't different before I started "flashing".
aah ok must be the rom im on thats got it , im not really sure where to go from here maybe do a factory reset and try again youve unlocked your bootloader though so dnt need to do that again
Sent from my Xoom using XDA Premium App
Same error with a factory reset... damn whats going on?
i honestly domt know i never had any probs doing mine and i asked my friendmwho has same xoom as you and he never had any trouble so kinda got me stumped lol
Sent from my Xoom using XDA Premium App
Guess I'll have to wait until someones bringing the big hint But I really thank you for your time. Since I know now that my device isn't completely bricked, you helped me a lot.
not a problem glad i could help even if a little lol
Sent from my Xoom using XDA Premium App

Mightve bricked my P5113

Hi, i tried updating my tab to the leaked 4.1 OTA and after following the instructions my tab wont boot. It will only play the boot animation then hang at the samsung logo for about ten minutes then go black. I cant get it into download or recovery mode, but when i plug it into the wall it shows the battery icon. Also odin recognises the tab while its hanging at the samsung logo.. i have heard talk of a usb jig but not for this tablet.. Can anyone offer any advice? thanks in advance
If Odin sees it a USB jig isn't needed.. Just flash the stock f/w tar and you're good
EDIT: fail... No download mode... Umm... Sounds like you're in a bootloop... No idea why recovery and download wouldnt work tho...
Sent from my XT907 using Tapatalk 2
HulianMango said:
Hi, i tried updating my tab to the leaked 4.1 OTA and after following the instructions my tab wont boot. It will only play the boot animation then hang at the samsung logo for about ten minutes then go black. I cant get it into download or recovery mode, but when i plug it into the wall it shows the battery icon. Also odin recognises the tab while its hanging at the samsung logo.. i have heard talk of a usb jig but not for this tablet.. Can anyone offer any advice? thanks in advance
Click to expand...
Click to collapse
The good news is that the device probably isn't bricked. If it was unfixably bricked you shouldn't even see the boot animation.
It's figuring out how to fix it that's the hard part.
What you've clearly done as far as the ROM though is installed the rom improperly somehow. Might have missed as step in the process, or the ROM could have just been a bad download and no fault of your own. These things happen to the best of us.
Assuming that clockworkmod recovery is still installed, and you just can't get into it, you might try to see if you can access it using adb from your computer.
If you have abd installed boot the device as far as it'll go then see if you can connect to it with adb and run this command...
abd reboot recovery
Also try
adb reboot boot loader
If you don't have adb installed read this...
http://forum.xda-developers.com/showthread.php?t=1853159
If that doesn't work (and I only give it a 50-50 shot at best as adb isn't always useful during the boot process, which is where you are stuck....then we'll think of something else.
Also please describe the steps you are using to try and get into recovery just to make sure you're trying it the right way.
And after it gets stuck at the Samsung screen are you turning it off completely by holding the power, volume up, and volume down all at once? That should shut the device off completely, which is where you need to be before trying to boot into recovery.
Thank you both! ! I managed to get it going
Sent from my GT-P5113 using xda app-developers app
HulianMango said:
Thank you both! ! I managed to get it going
Sent from my GT-P5113 using xda app-developers app
Click to expand...
Click to collapse
Please share how you got it fixed and what ended up working.
That way when someone else Google's the same probelm a year from now and finds this thread, he'll have the answer waiting for him. (See my signature cartoon from XKDC.com for a comical represensation of why not explaining what the outcome was is annoying)
Glad it got working!
Well i asked in the thread for that rom and it was suggested that the battery needed charging, I didnt think this was the case cuz my tab had been plugged in to the wall for about an hour already but I let it sit for a couple hours and it finally booted although it said there was 15% power left... its still charging really slow but it boots now!
Sent from my GT-P5113 using xda app-developers app

HTC One Mini (No OS/Data wiped) HELP!

I need some help, I'm a total noob at all this stuff. So basically, all what I wanted to do is root my phone. So I unlocked bootloader, installed twrp, had super user and everything but while I was on the twrp menu rather than hitting the install button I hit the wipe button then accidentally (really) confirmed wiping. Now my phone is completely wiped no OS nor data, at least it boots up but the booting up loading screen stays there forever. I can also get into the bootloader screen but for some reason when I try to install twrp again it doesn't install, there's like that small green bar at the top right of the bootloader screen it only does half way 50% and never increases. I'm really hopeless, lol. Please help, what should I do? How to install HTC's One mini OS from scratch without having any problems?
l3raveHeart said:
I need some help, I'm a total noob at all this stuff. So basically, all what I wanted to do is root my phone. So I unlocked bootloader, installed twrp, had super user and everything but while I was on the twrp menu rather than hitting the install button I hit the wipe button then accidentally (really) confirmed wiping. Now my phone is completely wiped no OS nor data, at least it boots up but the booting up loading screen stays there forever. I can also get into the bootloader screen but for some reason when I try to install twrp again it doesn't install, there's like that small green bar at the top right of the bootloader screen it only does half way 50% and never increases. I'm really hopeless, lol. Please help, what should I do? How to install HTC's One mini OS from scratch without having any problems?
Click to expand...
Click to collapse
Did that too with my HTC One M7UL once upon a time. You can push files to your device, when it's in fastboot, via adb fastboot. So push a system/zip to your device and flash it in TWRP, when you get there. As long as you can do adb in fastboot, there's hope for you!
Good luck
Thanks for your reply.
Do you by any chance know where to get HTC One Mini's system zip?
Hello, put your phone out by holding the powerbutton till it is really out.
Then hold volume up and the powerbutton, this will get you to TWRP.
Now you can use ADB sideload to push a rom to your phone by using adb.
Sent from my HTC One mini using XDA Free mobile app
Zoeriva said:
Hello, put your phone out by holding the powerbutton till it is really out.
Then hold volume up and the powerbutton, this will get you to TWRP.
Now you can use ADB sideload to push a rom to your phone by using adb.
Sent from my HTC One mini using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the reply really appreciate your help, but when I try to push a file using cmd it says ''error device not found'' What could be causing this error to happen and how to fix? Thanks again.
It's a good idea to update the drivers for the phone, if you don't already have that. Btw, that's the HTC syncing program. Try the command: adb devices. That will show connected devices.
Sent from my One using XDA Free mobile app

Blue light Brick [XPosed]

Aloha guys,
I was trying to install Xposed and, regrettably, I didn't look into it as much as I should've before trying to install it; I'm inexperienced with all this.
Long story short, I installed the apk, went to install the framework through TWRP and then when I tried to restart the phone afterwards, it will show the Samsung screen and then a pulsating Blue LED light with a pitch black screen. From there, I am able to get it back into Odin mode and TWRP but I havent been able to get the phone to actually restart. I have no clue, but maybe I didnt install the correct framework? I just chose the most recent version in Arm64 v. 86. Super worried here that I ruined my phone and would appreciate any suggestions!
Mahalo
Model: SMG92P
Build: F2
Firmware: 6.0.1
APK from here: http://forum.xda-developers.com/showthread.php?t=3034811
http://forum.xda-developers.com/showthread.php?t=3180960
Sent from my SM-G920W8 using Tapatalk
DarryDoo said:
http://forum.xda-developers.com/showthread.php?t=3180960
Sent from my SM-G920W8 using Tapatalk
Click to expand...
Click to collapse
Okay, I appreciate the link. Are you saying my solution is the "adb logcat" ? Is my issue considered a bootloop?
Really appreciate it.
I'm saying you installed the wrong version of Xposed.
There's a flashable zip to uninstall Xposed in the link I provided. Flash it, then flash the correct Xposed zip, and hope for the best.
Sent from my SM-G920W8 using Tapatalk
---------- Post added at 06:53 ---------- Previous post was at 06:52 ----------
Actually, use the uninstaller from your original link.
Sent from my SM-G920W8 using Tapatalk
black screen
Managed to do the same thing to my S6 trying to install Xposed for the first time, phone was rooting using Odin3
CF-Auto-Root-zeroflte-zerofltexx-smg920f.tar
Installed XposedInstaller_3.0_alpha4.apk & TWRP via Flashy, restarted and used xposed-v86-sdk23-arm64.zip but black screen with bluelight on reset, managed to enter recovery mode after learning how to do it but it's the default samsung one it seems, no idea where TWRP went?
Any idea what to do?
Tried clearing the cache and formatting with the default recovery thing still won't load please don't tell me i bricked this thing
Edit* Managed to fix it by using Odin3 to restore original firmware but i'm not sure what i did wrong in the first place to cause it to hang if anyone can glance at the filenames above it's all correct right? perhaps it's because i didnt uhh, deodox or whatever it's called? seems so hard just to get this framework running ugh!
And how do i make it so TWRP stays, seems i had to keep flashing it to use it? seems i triggred my KNOX void status to 1 also messing with Odin3 ah well!
you need to use ODIN to restore the phone, after that it should boot. As for twrp, install via ODIN and boot into recovery immediately. if you install twrp then boot to android it will automatically replace it with the stock recovery. On first boot TWRP patches the phone so it doesn't get replaced.
And use the S6 version of Xposed that Wanam created. See my link above.
Sent from my SM-G920W8 using Tapatalk
Thanks guys, ended up going with "XtreStoLite-ROM-3.3.1-DPDP.zip" because i didn't know if "CF-Auto-Root-zeroflte-zerofltexx-smg920f.tar.md5" was deodoxd or whatever
was able to boot with this, but "xposed-v86-sdk23-arm64.zip" created a bootloop, uninstalling with TWRP and running "xposed-uninstaller-20150831-arm64.zip" solved it
"xposed-v86.0-sdk23-arm64-custom-build-by-wanam-20160709.zip" didn't cause a bootloop and i finally managed to get onto the phone!
Sorry for the long file names just hoping it helps someone else it appears i voided my KNOX warranty thing by using Odin, oops it's not even a very old phone either i'm just hoping now the above stuff doesn't comprimise my phone and contain anything like keyloggers ect!
Hi gents.
Few minutes ago I managed to perform same mistake here.
Now,my phone displays only SAMSUNG label and blue LED is on.
Both of those are slowly "breathing" repeatedly.
I am not able to switch the phone off,in order to enter recovery or download.
How did you managed to get into download mode?
Very long power hold doesn't work.
Thank you,Tomas.
Edit>
Nevermind,I managed to power it off.
Here are some tips:
1. Simulated battery removal:Hold Vol.Down+Power
2. Entering download mode: Hold Vol.Down+Home+Power,confirm by Vol.Up
3. Recovery: Hold Vol.Down+Home+Power to get into download mode,don't confirm download by Vol.Up button. Then hit the Vol.Down button(Cancel) and immediately hold Vol.Up+Home+Power
In recovery,there is an option to turn off the device,what stops to drain the battery.
Hey there,
i managed to get the same error on my phone
Yesterday i installed xposed, now its stuck with a blackscreen and the blue LED, or sometimes with the Samsung Sign and blue LED.
I tried to flash the stock firmware with Odin 3.12 but it fails with a write error after a few seconds. I already tried to wipe and clear cache in recovery.
So can you guys give me any idea how i can get my phone to boot again? :/
Thanks:fingers-crossed:

Categories

Resources