So i may have hosed my P2 (or at least the data i was trying to keep lol) but i was trying to update to the May update and i meant to remove the -w in the bat file but accidently double clicked. It opened and was probably only open for about a second or two before i closed it and now its stuck in the bootloader. all the options just restart the bootloader. Powering off actually powers off but turning it back on just goes straight to bootloader.
I finally was able to get the monthly to run through and finish flashing and i thought that would finally fix it but it no luck, still goes to bootloader.
Also, not sure but it looks like the device serial is different in the text on the bootloader screen.
pics for help: https://imgur.com/a/vChW2pM
EDIT and now i think i killed it for good. Read you could try to switch boot slots so i did fastboot --set-active=a and restarted and now it wont even power on.
EDIT2 so i got the battery icon to turn on when plugged in and if i hold the power button for 30 seconds it will vibrate then vibrate every 5 seconds or so if i keep holding. Already started the RMA process but just curious if theres anything else i could do. anyway to "force" it to load slot B again?
I have the same problem, tried Deuce's script but when it boot to G logo, it turned out error: "Load ImgAndAuthFailed". I can not switch boot slot (fastboot unknow option in Deuce's script)
fastboot: unknown option -- set-active=_a
fastboot: unknown option -- set-active=a
Click to expand...
Click to collapse
I even can not switch to slot a by fastboot --set-active=a
NaChal said:
I have the same problem, tried Deuce's script but when it boot to G logo, it turned out error: "Load ImgAndAuthFailed". I can not switch boot slot (fastboot unknow option in Deuce's script)
I even can not switch to slot a by fastboot --set-active=a
Click to expand...
Click to collapse
Keep running the commands, I've been there.
NaChal said:
I have the same problem, tried Deuce's script but when it boot to G logo, it turned out error: "Load ImgAndAuthFailed". I can not switch boot slot (fastboot unknow option in Deuce's script)
I even can not switch to slot a by fastboot --set-active=a
Click to expand...
Click to collapse
I was there too, just now. Fastboot wouldn't detect my phone. I was going to factory reset but no stock recovery. I had the factory image installation window open (waiting on device) and was just holding the power button and up volume button and it was going through all the different options. It landed on reboot recovery and I let go. It actually saw my device and started and finished installing the factory image in reboot recovery option instead of start.
Related
The other day my WiFi Xoom stopped getting past the "Motorola Dual Core" screen.
I have removed the SD card.
Android recovery mode gives me the error android with the "!"
It does this plugged in or on battery.
Not rooted.
What else should I try?
neoka said:
The other day my WiFi Xoom stopped getting past the "Motorola Dual Core" screen.
I have removed the SD card.
Android recovery mode gives me the error android with the "!"
It does this plugged in or on battery.
Not rooted.
What else should I try?
Click to expand...
Click to collapse
What were you trying to do before this hapened? Need more info to be able to help.
24348542 26
DavilaDarkness said:
What were you trying to do before this hapened? Need more info to be able to help.
Click to expand...
Click to collapse
Hadn't really done anything. Just normal use. No out of the ordinary installs. Turned it off. Next day I tried turning it on and it won't boot.
Did you ever resolve this ?? I was give one to repair for a child and it too is stuck on the red boot screen. The good thing is the person who sold it to them was a hacker and put TWRP on it of all things. I was floored when I tried to enter recovery and found teamwin.
but the problem is its still stuck on the boot screen, i did flash it 3-4 times with M604 M602 flashes and some other customs but nothing works, it completes flashing and wiping caches but always goes back to stuck on boot screen..
perhaps I have to unclock the bootloader or something for the flash to be succesfull ?
Just wanted to say I fixed it with these commands and firmware if anyone is interested. I tried everything else including flashing with twrp and wiping all caches and it didn't work, getting the stock firmware and doing it like this worked to clear boot screen endless stuck
download fastboot and adb and xoom drivers 6.4 (about 5mb) and the appropriate stock firmware. for me it was ZM604
at the command type
adb reboot bootloader
you may need to unplug and replug cable after it goes in fastboot mode.
fastboot devices
.. should return something "02a439cj0skjdke fastboot" to proceed.
fastboot oem unlock
.. look at your tablet and follow the instructions, for me it was down twice and up once to accept unlock conditions, then it reboots
on reboot press vol down 2 seconds after you see moto logo, it will enter fastboot
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot erase userdata
fastboot reboot
no need to relock after, you will see android logo and first boot pop up after 2-3 mins
So my OnePlus One started dying when I would still have about 10% left. I thought it might be a bug or something with he CM12 nightlies so I wanted to revert back to stock. I transferred all of my media to my comp, got the 64gb zip from the "Revert back to 100% stock" thread, plugged my OnePlus One in, went into fastboot mode, made sure my comp recognized my phone ("fastboot devices") and clicked the "flash-all.bat" or whatever (not on MY comp right now, don't know the exact name) aaaaand some crazy stuff happened.
My phone started rebooting constantly, back into fastboot mode. This isn't how it worked with my Nexus 5 but the command window looked like it was doing what it was supposed to do. Then it got to sending the "system" and FAILED saying the file was too large. My phone rebooted and now it doesn't get past the first splash screen with the 1+ logo and "powered by android"
When I try to get into the bootloader nothing happens, but sometimes I get into the "Cyanogen Recovery" which I've never seen before. I wish I could take a screenshot and post it. It's options are:
Reboot system now
Apply Update
Wipe data/factory reset
wipe cache partition
wipe media
If I could get into fastboot mode I think I would be fine, but I can't.
When I go to "Apply update" I have the option to "apply from adb" and do the adb sideload thing, which I'm not very familiar with.
I think I might be in trouble, could anybody help me?
Is adb working while in recovery? It should. Try using the adb reboot bootloader command.
Transmitted via Bacon
Try pressing Power + Volume Up until your phone boots into fastboot mode and then run flash-all.bat again. If it is not working again, boot to fastboot mode and do all the steps by hand.
Purchased an Lg Gpad 7 Wifi tablet (v400) 2 weeks ago. Came with preinstalled Lollipop android so i couldnt install a recovery rom to flash any other custom roms. Downgraded to Kitkat version following the instructions on Xda forums and succesfully installed Twrp. When i installed Cyanogenmod 12.1 through Twrp i got stuck in fastboot screen.
Any suggestions and / or solutions would be greatly appreciated.
I had a similar problem.. Only mine was stuck at the bootloader. Go in TWRP and repair /data and other partitions. My data partition gave me an error since F2FS is a little flaky and some ROMs corrupted it (claimed they supported it). I would recommend erasing the system, cache and data partition if you can't get into TWRP.
The problem is i cant get out of fastboot whatever i try. It says start on bootloader but the tablet just restarts on an empty screen doing nothing.
Hakalai said:
The problem is i cant get out of fastboot whatever i try. It says start on bootloader but the tablet just restarts on an empty screen doing nothing.
Click to expand...
Click to collapse
if you have an sd card, try removing that, then reboot.
if that doesnt work, try entering fastboot command, fastboot continue
Tried without sdcard and i get the same fastboot screen.
How can i give any commands? The only options i have are Restart Bootloader / Restart / Power off. Tried restarting bootloader but i get nothing in return tablet just stays on with nothing on screen.
Hakalai said:
Tried without sdcard and i get the same fastboot screen.
How can i give any commands? The only options i have are Restart Bootloader / Restart / Power off. Tried restarting bootloader but i get nothing in return tablet just stays on with nothing on screen.
Click to expand...
Click to collapse
you said it was stuck on fastboot, if thats the case, install any needed drivers on your pc, connect device to it, open a terminal in the fastboot dir (after you go get fastboot), then try those commands i gave. you could also try, fastboot reboot dont think i mentioned that before.
bweN diorD said:
you said it was stuck on fastboot, if thats the case, install any needed drivers on your pc, connect device to it, open a terminal in the fastboot dir (after you go get fastboot), then try those commands i gave. you could also try, fastboot reboot dont think i mentioned that before.
Click to expand...
Click to collapse
Did as you said but every command i gave gives me an error message in adb terminal. There are new lines in fastboot menu in tablet now. Bottom two are SECURE BOOT - enabled & LOCK STATE - locked.
Hakalai said:
Did as you said but every command i gave gives me an error message in adb terminal. There are new lines in fastboot menu in tablet now. Bottom two are SECURE BOOT - enabled & LOCK STATE - locked.
Click to expand...
Click to collapse
hmm, ok, im guessing it would have said that normally, when not broken. all the command does is try to release it past where its stuck. it doesnt actually flash, lock, unlock, or change anything.
imo, this seems good, because now we know fastboot is working.
i own lg devices, but not your specific device. i would hate to give you some bad advice and make your tablet broken more, but if it were me in this situation, i would try to flash the factory KK firmware you used to downgrade with odin or however you did it. hopefully, that will clean everything up and let it boot properly.
if for whatever reason you cant do that, we could try extracting the factory file, and just flashing recovery and system, those should be the only things that got changed putting on twrp and cm normally.
Sorry, I have the serious proplem wtih my LG pad V400, I rooted it and using <LG Flash Tool 2014> with <V40010c_00.kdz> to downgrate the firmware but their is error then my LG pad stuck in fastboot menu as with just turn off, restart and restart bootloader. if i seclect one one them the tablet just logged again the fastboot menu
it stuck on the fastboot menu and i cannot do nay think with it. I can restart with factory restore mode but when select yes to restore, it will restart and log in fastboot menu again.
I downloaded adb and fastboot program and put in one folder <Minimal ADB and Fastboot> in C:\Program Files (x86)\Minimal ADB and Fastboot
I dont have recovery image so i download file <cm-13.0-20160421-NIGHTLY-v400-recovery.img> form your link to download TWRP file
move it to folder of fastboot programe and changed its name to <recovery.img>
I turn on the tablet and it waited at fastboot menu
when i run the command <fasboot flash recovery recovery.img> and they said some thing wrong like in picture
please help me
Okay, so I had been out of the flashing game for a while now, and recently got a Pixel 128Gb after using my trusty Nexus 6P, and I attempted to do Fastboot boot-to-root.img, which now has me stuck in a weird bootloop issue.
It boots, gives me the stupid can't be checked for corruption ****, gets to the white Google Screen, then there is a weird visual glitch, a blue line appears near the bottom of the screen, then the phone immediately reboots and does it all over again after doing a ramdump.
I can't even get into recovery to manually flash the stock image, as soon as I try to select RECOVERY it jumps to the boot screen where it tells me again that it cant be checked for corruption, and then starts the bootloop all over again.
ADB cant recognize it for whatever reason either. So now I'm probably not your average ****ed, I'm advanced ****ed.
Any body have any ideas?
boot-to-root is for Android O, you have to follow this guide
I had this same exact problem and I was able to fix it by reflashing the factory image. You said adb cannot recognize your device. But what about fastboot? If you reboot into the bootloader, connect to your PC, and execute "fastboot devices", does your device show? Download the latest factory image here. Extract it and execute flash-all.bat. Let me know if this helps.
You don't understand. When you attempt to reboot and go into recovery the manual way, the moment you select Recovery, the phone reboots and attempts to boot up, fails, performs write to ext4 ramdump, then loops over and over. ADB won't work because it wiped with the fastboot oem unlock which wiped the device, meaning no developer mode, which means no usb debugging.
Doesn't matter. Google is sending me a new one.
:/
jdkzombie said:
You don't understand. When you attempt to reboot and go into recovery the manual way, the moment you select Recovery, the phone reboots and attempts to boot up, fails, performs write to ext4 ramdump, then loops over and over. ADB won't work because it wiped with the fastboot oem unlock which wiped the device, meaning no developer mode, which means no usb debugging.
Doesn't matter. Google is sending me a new one.
:/
Click to expand...
Click to collapse
Fastboot and recovery are two different things. If you hold volume down + power it'll show you the bootloader screen (fastboot), this is where you'd usually select recovery. But if you stay on that screen, you can flash images to your phone. To fix your bootloop, download the boot.img from the stock ROM and use these commands in fastboot:
fastboot flash --slot _a boot boot.img
fastboot flash --slot _b boot boot.img
Then reboot normally.
falsh factory image inside the bootloader, don't need to go to recovery.
Step by Step
Thanks to previous experience with hacking devices (Android, Sony, etc.), patience and only allowing myself to freak out for a few seconds. A couple Google searches lead me to reflashing my Google Pixel 128GB and not sending it back to OEM.
So for the less patient I will break down the steps to do stop the bootlooping.
DON'T PANIC
Either hold down power until your phone turns completely off or wait for the bootlooping to do it for you. It usually only loops a few times before powering down.
Hold Power + Volume Down until it boots into the Fastboot mode.
[This is the screen that says you Phone Stats (serial #, cpu, ram, etc.) and has an Android picture on it laying down.]
Connect your Phone to your computer using a USB 3.0 port.
[My PC wouldn't recognize my phone at all when connected to USB 2.0]
Download from Full Factory Image from Google. { https://developers.google.com/android/images }
[Mine was "7.1.2 (N2G47O, May 2017)" for my Project Fi 128GB Pixel, but make sure you get the one for your phone]
Navigate to where your SDK/Fastboot folder is on your PC
[Unless you moved it, it is usually "C:\Users\USERNAME\AppData\Local\Android\Sdk" by default.]
Unzip the Contents of your Full Factory Image zip file to this location in it's own directory (for cleanliness).
Open a Command Prompt with a Right-Click "Run as Administrator" and navigate you your new zip file's directory.
["\platform-tools\sailfish-n2g47o" or whatever version of the Full Factory Image you used was.]
Type in "flash-all.bat" and wait for your phone to finish its installation. Your phone will restart itself into Fastboot Mode many times during this process.
Once it is finished, you phone should boot into its normal "First Boot Sequence" like you just started it up for the very first time.
At this point you can try flashing something else or use a different technique to update your recovery mode or ROM.
Good Luck.
Newbie here. Tried to download TWRP onto unrooted device (Galaxy Note10 Exynos d1) with Odin and now my phone is stuck on "downloading" screen. When I try to cancel (restart phone) it goes to the startup/booting screen for less than a second and then jumps back to "downloading". It says this at the top left corner of the screen:
recovery: Error validating footer (6) CUSTOM RECOVERY VBMETA N970F XXU1 ASG0. 24967245R
I am able to get into the custom OS installation screen (don't know what it's actually called but second picture) by letting the battery drain so that the phone turns off and then holding volume up + volume down key and plugging the phone into my laptop with USB.
The bootloader is unlocked. I went to https://twrp.me/samsung/samsunggalaxynote10.html and even there it says "Flashing TWRP without first flashing a vbmeta image with verity disabled will render your device unable to boot." Does anyone know how to fix this? Thanks in advance.
TheAckermans said:
Newbie here. Tried to download TWRP onto unrooted device (Galaxy Note10 Exynos d1) with Odin and now my phone is stuck on "downloading" screen. When I try to cancel (restart phone) it goes to the startup/booting screen for less than a second and then jumps back to "downloading". It says this at the top left corner of the screen:
recovery: Error validating footer (6) CUSTOM RECOVERY VBMETA N970F XXU1 ASG0. 24967245R
I am able to get into the custom OS installation screen (don't know what it's actually called but second picture) by letting the battery drain so that the phone turns off and then holding volume up + volume down key and plugging the phone into my laptop with USB.
The bootloader is unlocked. I went to https://twrp.me/samsung/samsunggalaxynote10.html and even there it says "Flashing TWRP without first flashing a vbmeta image with verity disabled will render your device unable to boot." Does anyone know how to fix this? Thanks in advance.
Click to expand...
Click to collapse
Go first to the unlocking menu to check if your device is really unlocked, long press volume up, and see which the menu says.
If it is unlocked, then flash the vbmeta file provided, then try to boot to recovery and perform a factory reset.
SubwayChamp said:
Go first to the unlocking menu to check if your device is really unlocked, long press volume up, and see which the menu says.
If it is unlocked, then flash the vbmeta file provided, then try to boot to recovery and perform a factory reset.
Click to expand...
Click to collapse
Bootloader is unlocked and I've flashed the vbmeta file but now my phone is stuck on the startup screen and I can't seem to boot into recovery. Why?
TheAckermans said:
Bootloader is unlocked and I've flashed the vbmeta file but now my phone is stuck on the startup screen and I can't seem to boot into recovery. Why?
Click to expand...
Click to collapse
Maybe you missed some essential part of the process, by unlocking your device through the Download menu option your data has to be erased, it's recommendable after to unlock the bootloader, to reboot again to system and check once the UBS debugging and OEM unlock options if they remain fine, from there you should reboot to download mode again, uncheck the Auto-reboot option within Odin, flash the vbmeta.tar and then flash the TWRP, if all till here goes well you should reboot manually to TWRP by powering off completely, pressing the three buttons, and just now, pressing the volume up + PWR key buttons till your device boots to TWRP.
SubwayChamp said:
Maybe you missed some essential part of the process, by unlocking your device through the Download menu option your data has to be erased, it's recommendable after to unlock the bootloader, to reboot again to system and check once the UBS debugging and OEM unlock options if they remain fine, from there you should reboot to download mode again, uncheck the Auto-reboot option within Odin, flash the vbmeta.tar and then flash the TWRP, if all till here goes well you should reboot manually to TWRP by powering off completely, pressing the three buttons, and just now, pressing the volume up + PWR key buttons till your device boots to TWRP.
Click to expand...
Click to collapse
Thanks for the help, tough i am struggling to get acces to the download menu option. Could you give me a example to acess the menu?
TheAckermans said:
Thanks for the help, tough i am struggling to get acces to the download menu option. Could you give me a example to acess the menu?
Click to expand...
Click to collapse
The screenshots you uploaded some months ago, are the download screen, you, successfully did boot to, download mode doesn't have a useful menu, it's just a mode, so you can flash some things, using Odin. To boot to, use the same way you did it previously, usually, doing it manually, or if you are rooted, you can use other ways too.