Hi guys,
I'm facing the following issue:
I took my pixel 4a, unlocked the bootloader, later worked on the boot.img to with magisk to root the device... prepared the modified img file and launched the command fastboot and it went successfully. Later sent the fastboot reboot comand, and the device booted up, it is stuck with the google logo and from there, trying to get back into fastboot mode but whenever I do the procedure (presso volume down + power up) , I first get a screen telling that the device is corrupted and it might be not safe... later starting to bootup but straight away stuck at google logo ... the device is not seen from adb commands or fastboot commands... how can i recover the device according to you guys ?
thanks,
giuseppe
letsrock666 said:
Hi guys,
I'm facing the following issue:
I took my pixel 4a, unlocked the bootloader, later worked on the boot.img to with magisk to root the device... prepared the modified img file and launched the command fastboot and it went successfully. Later sent the fastboot reboot comand, and the device booted up, it is stuck with the google logo and from there, trying to get back into fastboot mode but whenever I do the procedure (presso volume down + power up) , I first get a screen telling that the device is corrupted and it might be not safe... later starting to bootup but straight away stuck at google logo ... the device is not seen from adb commands or fastboot commands... how can i recover the device according to you guys ?
thanks,
giuseppe
Click to expand...
Click to collapse
If you are getting the unlocked bootloader message of "being corrupted", that is normal. You'll see it every time you reboot now that your bootloader is unlocked. Sounds like you are having trouble getting back into fastboot. I find it easier if I unhook my phone from the pc while holding the power and volume down (not up) buttons. You should be able to fastboot flash your stock boot.img to get your phone back. Make sure you have the correct boot.img for your firmware.
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
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
I was messing around with my settings last night and quickly enabled the pattern lock without paying much attention to the lock I entered (careless, I know) and now I'm locked out of my OPO on CM13 6.0.1 Marshmallow. I'm not sure if it's just Marshmallow or not but I can't even boot into TWRP.. when I hold the custom recovery buttons with phone both on and off it wont boot into recovery. When this happened, I didn't have USB debugging enabled so I can't use ADB. The only screens that I can look at are the locked lockscreen (spent all night and day guessing patterns) and I AM able to boot into Fastboot mode via powering off the phone and holding the power + up volume button which gives me a SLIVER of hope that I may not have to lose everything due to such a stupid and careless mistake.
Making matters worse, my phone is my only internet source so I'm at the library posting this hoping I'll get the response I need (or any response) sooner rather than later. I'll do ANYTHING I possibly can to not lose my files.. please help! (I even went and bought a brand new laptop with Windows 10 on it since my XP home computer doesn't like my OPO.)
If you can get to fastboot, then you could try flashing the system.img only and see if it boots. If not, the you may have to flash the entire package, excluding userdata and recovery.
Fastboot flashing guide:
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Fastboot image:
http://builds.cyngn.com/factory/bacon/cm-13.0-ZNH0EAS2JK-bacon-signed-fastboot-2d1a3b8dca.zip
If you are able to boot into fastboot mode,then first flash a custom recovery(eg.twrp) using the command
Code:
fastboot flash recovery recovery.img
Then boot into recovery from fastboot mode using this command
Code:
fastboot boot recovery.img
If you did everything right you might boot into your recovery. And from there I'm sure you can resolve your issue.
If you want any further help please contact me at [email protected]
Hit Thanks If You Find My Solution Valid
Hi There!
I'm exeriencing a wierd problem:
On my rooted Doogee S60, i was able to enter the built in recovery mode (and from there the fastboot mode) with Vol+ and Power.
Since i've installed a twrp recovery.img, pressing Vol+ and Power will launch the TWRP UI (wich i cant use, because my touchscreen is disabled).
Normal boot won't work eighter - i flashed a corrupted system.img file as it looks like (ooops). There is also the message at the Boot Screen saying:
"Orange State - Your device has been unlocked and can't be trusted. Your device will boot in 5 seconds"
... although these 5 seconds won't countdown and the device won't boot.
If i enter the TWRP, i can still access the ADB mode. So i can sideload stuff on the device, even the sd card is shown on pc. But the command
adb reboot fastloader
will reboot the phone, but not load the fastloader/fastboot - as it stucks at boot screen (orange state).
Any other ideas to access fastboot, due to flash the recovery.img again with the original to fix?
... or simple question: did i brick it?
thx in advance
Command
Code:
adb reboot fastloader
doesn't exist.
Look inside here:
How to Reboot Android Device into Fastboot or Recovery Mode via ADB « My Digital Life
If you’re using Android phones, tablets or devices, which is proliferating across all markets, prices and channels nowadays, then you may want to familiar yourself with fastboot or recovery mode, which is useful when you need to troubleshoot your beloved phone from the like of Samsung, HTC...
www.mydigitallife.net
introjoe said:
Hi There!
I'm exeriencing a wierd problem:
On my rooted Doogee S60, i was able to enter the built in recovery mode (and from there the fastboot mode) with Vol+ and Power.
Since i've installed a twrp recovery.img, pressing Vol+ and Power will launch the TWRP UI (wich i cant use, because my touchscreen is disabled).
Normal boot won't work eighter - i flashed a corrupted system.img file as it looks like (ooops). There is also the message at the Boot Screen saying:
"Orange State - Your device has been unlocked and can't be trusted. Your device will boot in 5 seconds"
... although these 5 seconds won't countdown and the device won't boot.
If i enter the TWRP, i can still access the ADB mode. So i can sideload stuff on the device, even the sd card is shown on pc. But the command
adb reboot fastloader
will reboot the phone, but not load the fastloader/fastboot - as it stucks at boot screen (orange state).
Any other ideas to access fastboot, due to flash the recovery.img again with the original to fix?
... or simple question: did i brick it?
thx in advance
Click to expand...
Click to collapse
Hi introjoe,
Are you doing? i have the doogee s60 but i just cant root it :'( can you tell me please how did you do it, or the files you use for it? i allready tried but, when i reset and enter fastboot mode, my pc simply dont recognize it.
I want to upgrade the android system to 9 or 10, thats why im doing all o this.
Thanks in advance.
@doryan666
i wasnt able to root the device in the end unfortunately.
i tried using an unofficial twrp, but i was stuck at the main boot screen
i t seems to need some bootloader-activation-code to enter the bootloader to install a new os.
the command line would look like
adb reboot bootloader "CODE"
the activation code has not been released yet by doogee ... and most probably never will be.
sorry to say but i dont think android upgrad will be possible with this device
Tried to follow this guide to root my pixel 4a and completed all steps up to 3.4. My phone is now stuck in fastboot mode and I can't get into recovery mode to do a factory reset. Not sure what to do, I'm a little lost. I accidentally used this or this image for Android 10 when I think I should have used this image for Android 11.
Any help would be very appreciated.
Maybe you can use this guide:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com
And start on this line in "First Step" section:
Plug the phone into a usb port of your pc.
Then complete all the tasks in "Second Step" section to get your phone at least booting in android 10.
ifixibrick said:
Tried to follow this guide to root my pixel 4a and completed all steps up to 3.4. My phone is now stuck in fastboot mode and I can't get into recovery mode to do a factory reset. Not sure what to do, I'm a little lost. I accidentally used this or this image for Android 10 when I think I should have used this image for Android 11.
Any help would be very appreciated.
Click to expand...
Click to collapse
Run the online flash tool from bootloader screen bro. Make sure you install adb and fastboot tools.
Raj Pandiyan said:
Run the online flash tool from bootloader screen bro. Make sure you install adb and fastboot tools.
Click to expand...
Click to collapse
How do I do that? I seem to be stuck in fastboot mode.
ifixibrick said:
How do I do that? I seem to be stuck in fastboot mode.
Click to expand...
Click to collapse
Is it bricked? Cannot flash stock Android to remove ArcaneOS
I recently purchased a used Pixel 4a, and I now understand why the seller was offering such good price for it and why he refused to respond to me now I have it. This phone has ArcanseOS 10 installed, which has only 3 apps installed... Setting...
forum.xda-developers.com
reboot to recovery, press volume up + power to bring up the recovery settings, turn on sideloading
then adb sideload the factory image.
jawz101 said:
reboot to recovery, press volume up + power to bring up the recovery settings, turn on sideloading
then adb sideload the factory image.
Click to expand...
Click to collapse
Hello. Currently stuck in fastboot mode. Using the volume buttons to select recovery mode and pressing the power button to go into it doesn't take me to recovery mode. The screen briefly goes dark before entering fastboot again. I think the phone is trying to restart but not getting past fastboot mode.
ifixibrick said:
Hello. Currently stuck in fastboot mode. Using the volume buttons to select recovery mode and pressing the power button to go into it doesn't take me to recovery mode. The screen briefly goes dark before entering fastboot again. I think the phone is trying to restart but not getting past fastboot mode.
Click to expand...
Click to collapse
Can you type fastboot reboot recovery and get into recovery mode? You'll see a little Android guy with a red thing if you're in there.
If that doesn't work- it almost sounds as though your recovery partition is deleted or something. You can reflash the recovery from fastboot.
Hey, I had the same problem. I've got it resolved now and wasn't able to find any help on how to resolve it, but this thread is as close as it came, so in the off chance that somebody else comes along, I thought I'd write up the steps I took.
Because it was in fastboot mode, I was able to easily restore my phone to factory settings by running flash factory image script I downloaded here.
My original image was sunfish-rq3a.210605.005-factory-be541467 which I followed the steps with but couldn't get it to work. I got to the Google logo with a status bar that just ran forever. But the flash-all.sh script worked to get the phone booting again.
So what I did to get Magisk to work was to use that same factory image site to download an older version. I used a version that was listed in a different root guide with the idea that maybe the version I tried before wasn't compatible with magisk, but presumably the one from the guide was. So I tried sunfish-rq1a.210105.002, ran the flash-all in fastboot, and confirmed that it booted--it did.
Next I redid 2.2 through 3 and it worked, and the boot completed with Magisk installed. Everything seems to be working fine now.