Hello everytone, I'm afraid I'm in the boot loop.
I have tried rooting my Pixel 7 running android 13. I have downloaded my current build number. Unlocked the boot loaded, got the init_boot.img file and ran it through magisk. After that I loaded that file onto with fastboot, and got the boot failure. Then I tried loding with fastboot flash boot back the init_boot.img file, does't work. I also tried the boot.img file too, but this doesn't also work... Any ideas how I can fix this? Have I bricked it or is there a way to get out of this boot loop. I read somewhere that there are slot's for the boot's and init_boot, but I don't know how to manually put them there...
emali said:
Press and hold the Power button for 30 seconds. Some Pixels require you to tap Restart after holding the Power button.
best waterproof work boots,
Click to expand...
Click to collapse
I tried it, and the phone shut off. After I released the power button, it went into fastboot again, with reason boot failure...
I think I know what I did wrong. I was watching a pixel 6 rooting video, but I knew and did the init_boot.img file. The problem I have done is at the end, i have placed this command. fastboot flash boot magisk.img, I have placed the magisk init file on the boot.img on the file, I should have done fastboot flash init_boot magisk.img to my udnerstanding....So Now I tried to flash back the stock boot.img to the boot_b, as this was used, and not I get NO COMMENT android logo with red exclemation mark...
I was able to get into recovery mode, somehow wow....after trying to flash the original boot and init_boot, got into fastboot mode, then it tried to boot, held the volume down button and somehow it worked!!! What didn't work was choosing "Recovery Mode" from the fastboot, never worked, wow what a loooooop
teddysx3 said:
I was able to get into recovery mode, somehow wow....after trying to flash the original boot and init_boot, got into fastboot mode, then it tried to boot, held the volume down button and somehow it worked!!! What didn't work was choosing "Recovery Mode" from the fastboot, never worked, wow what a loooooop
Click to expand...
Click to collapse
Just flash stock again from pixels homepage, use Flash instead of download.
teddysx3 said:
I think I know what I did wrong. I was watching a pixel 6 rooting video, but I knew and did the init_boot.img file. The problem I have done is at the end, i have placed this command. fastboot flash boot magisk.img, I have placed the magisk init file on the boot.img on the file, I should have done fastboot flash init_boot magisk.img to my udnerstanding....So Now I tried to flash back the stock boot.img to the boot_b, as this was used, and not I get NO COMMENT android logo with red exclemation mark...
Click to expand...
Click to collapse
You could've used Pixel Flasher which is the easiest tool to flash/update/root your Pixel. Check its forum here
dexlemaffo said:
You could've used Pixel Flasher which is the easiest tool to flash/update/root your Pixel. Check its forum here
Click to expand...
Click to collapse
Thanks, sorry I'm getting back into android from a long pause...thanks for that!
Related
Hello,
I have a Droid 4 that recently black-screened and wouldn't respond to any input, and upon rebooting won't get past the Motorola Logo boot screen.
It was previously rooted, but I had not flashed anything onto it, and I believe it was on Android 2.3.6 still.
The current state of affairs:
A normal boot shows the Motorola Dual Core Technology screen, as well as a thin multi-colored line along the bottom of the screen.
Boot Mode Selection Menu works fine, but booting into Recovery shows the Motorola screen indefinitely (without the thin line at the bottom)
AP Fastboot and BP SBF flash modes appear to work normally, and I am able to see the device in RSD Lite 6.0.
Steps I have taken:
I tried to fix the problem by flashing 9.8.2O-72_VZW-18 Blur_Version.98.72.18.XT894.Verizon.en.US from sbf.droid-developers.org/cdma_maserati/list.php The flash was successful, apart from not rebooting successfully. When I manually restarted into AP Fastboot, RSD said the flash passed successfully.
There has been no change in startup behavior since I flashed the new version. I still can't boot into normal phone operation or recovery.
Please help!
Regards,
RS
RestroomSounds said:
Hello,
I have a Droid 4 that recently black-screened and wouldn't respond to any input, and upon rebooting won't get past the Motorola Logo boot screen.
It was previously rooted, but I had not flashed anything onto it, and I believe it was on Android 2.3.6 still.
The current state of affairs:
A normal boot shows the Motorola Dual Core Technology screen, as well as a thin multi-colored line along the bottom of the screen.
Boot Mode Selection Menu works fine, but booting into Recovery shows the Motorola screen indefinitely (without the thin line at the bottom)
AP Fastboot and BP SBF flash modes appear to work normally, and I am able to see the device in RSD Lite 6.0.
Steps I have taken:
I tried to fix the problem by flashing 9.8.2O-72_VZW-18 Blur_Version.98.72.18.XT894.Verizon.en.US from sbf.droid-developers.org/cdma_maserati/list.php The flash was successful, apart from not rebooting successfully. When I manually restarted into AP Fastboot, RSD said the flash passed successfully.
There has been no change in startup behavior since I flashed the new version. I still can't boot into normal phone operation or recovery.
Please help!
Regards,
RS
Click to expand...
Click to collapse
It looks like you tried to flash the JB fastboot files. If you were on GB that may be your problem. I'm not for sure on this but I think the fastboot files will only flash over itself or the previous software version. Maybe try flashing the GB or ICS fastboot files and see what happens. Doesn't sound like it could make it worse.
kwyrt said:
It looks like you tried to flash the JB fastboot files. If you were on GB that may be your problem. I'm not for sure on this but I think the fastboot files will only flash over itself or the previous software version. Maybe try flashing the GB or ICS fastboot files and see what happens. Doesn't sound like it could make it worse.
Click to expand...
Click to collapse
Thanks for the suggestion. I tried the 6.5.1_167_DR4-1_M1-219, which didn't have any effect. I'll try the 6.5.1_167_DR4-1_M1-215 and see what happens.
You can flash same or higher than what your phone/device was....ie....if you were on GB you can flash the GB, ICS or JB fastboot files to stay at GB, update to ICS or update to JB. If you were on ICS you can fastboot the ICS or JB fastboot files to stay the same at ICS or update to JB.
If you are on JB or have flashed the JB fastboot files....you can only RSDlite the JB fastboot files.
I would reflash the JB fastboot files and then attempt to let the phone boot normally. If it boots normally, then reboot and try to enter Recovery.
Try booting into a Linux OS and connect the phone. Then use the Droid 4 ICS or JB utility. Boot the phone into fastboot ap mode,connect the phone to linux, and run ICS or JB Utility. It should work right away, I was getting the same thing a few days ago and the JB utility worked for me with Linux and not Windows.
Sent from my DROID4 using xda premium
can somebody please help me? my screen just went black at work today and it does nothing at all now. if I hold the power button it vibrates once. if I hold power+volume down I get to recovery. I tried to reboot from there and I get the unlocked bootloader warning screen and from there it just goes to a black screen. so I get back to recovery and installed my back up and that didn't help at all. somebody please help me.
So the bootloader is unlocked, what else have you done to the phone?
You may need to reflash it with rsdlite.
OP you need to provide more details. are you getting the M logo? is it bootlooping? is the phone doing ANYTHING but getting in to recovery?
load the fastboot menu and use mfastboot to flash the system, boot and recovery images. you should be able to bring the phone back to life without losing data.
640k said:
OP you need to provide more details. are you getting the M logo? is it bootlooping? is the phone doing ANYTHING but getting in to recovery?
load the fastboot menu and use mfastboot to flash the system, boot and recovery images. you should be able to bring the phone back to life without losing data.
Click to expand...
Click to collapse
Im not getting the M logo. Not bootlooping. just get the warning bootloader unlocked screen. sits there for 10 seconds or so and then screen goes black. that's it.
to flash the system, boot, and recovery images. am I getting those form here:http://forum.xda-developers.com/showthread.php?t=2452246
jeb192004 said:
Im not getting the M logo. Not bootlooping. just get the warning bootloader unlocked screen. sits there for 10 seconds or so and then screen goes black. that's it.
to flash the system, boot, and recovery images. am I getting those form here:http://forum.xda-developers.com/showthread.php?t=2452246
Click to expand...
Click to collapse
just downloaded and opened that up. I don't think that's it....
Steve-x said:
So the bootloader is unlocked, what else have you done to the phone?
You may need to reflash it with rsdlite.
Click to expand...
Click to collapse
the only thing ive done to the phone is put xposed framework on it and gravity box. that was prob a month ago tho. this is the first prob ive had with the phone.
You may want to follow this guide to return the phone to stock firmware:
http://forum.xda-developers.com/showthread.php?t=2446515
You could also try commenting out the line that overwrites user data so you don't lose your data.
Try plugging your phone into the original charger and then boot to recovery, from their try rebooting while still plugged in. If that doesn't work try this again but wipe just the caches and reboot while plugged in. I have had a screen go black before on other devices and plugging the original charger(car and most others didn't work) in and booting to recovery then rebooting would get it working again.
PS When you boot to recovery check your battery level.
well...I used the moto x toolkit and returned to stock using that. everything booted up. so far everything is looking good. lost all my data but that's not that big of a deal.
640k said:
OP you need to provide more details. are you getting the M logo? is it bootlooping? is the phone doing ANYTHING but getting in to recovery?
load the fastboot menu and use mfastboot to flash the system, boot and recovery images. you should be able to bring the phone back to life without losing data.
Click to expand...
Click to collapse
Well im with the same problem but i got the M logo and is not stuck in bootlooping.... right after the boot it goes black...
I had my LG G2 VS980 (Verizon) on stock 26a KitKat with root and TWRP 2.7.0.0 recovery and I flashed CWM 12.1 using TWRP which worked great. I still had the TWRP recovery, which I believe uses an exploit on a 24a KitKat. Then, I decided to try CWM Touch recovery and used Flashify to download and flash, which, by all outward appearances seemed to work. (It gave success notification.) Then, after rebooting into recovery, it showed the LG boot logo, then black screen with tiny white writing that scrolled down about 4-6 lines, and then disappeared into a black screen that can only be escaped by holding the power down for about 10 secs. It boots into phone just fine (thank God), and if I hold the up + power at boot, it still shows download firmware mode, and if I hold the down + power and release and repress again at LG logo, I still get the Restore Factory screen, which is promising, but I am extremely reluctant to try that since I have no idea what would happen after upgrading to CWM 12.1 and my recovery is in the shape that its in. One thing that's interesting that no matter which app I use to try to flash a TWRP or CWM recovery, it always seems to flash too fast to be really doing anything at all, and it always goes back to that same tiny white writing then black screen. Also, another weird thing is that if I try to use Autorec which I downloaded to try to flash TWRP that way, it says Invalid Model, VS980 4G required, but that is what I have. Anyone who can figure this out and I will rename my firstborn after them! Thank you.
what happened is that you flashed a non bumped-loki'd recovery that by itself doesn't work. The screen you saw was probably LG secure boot error. The exploit bypasses this very screen that appears because our bootloader is locked.
To fix this, get this recovery here, extract the recovery.img from the dowloaded zip and use the flash tool to flash it. Your device should boot into twrp normally.
theobserver76 said:
what happened is that you flashed a non bumped-loki'd recovery that by itself doesn't work. The screen you saw was probably LG secure boot error. The exploit bypasses this very screen that appears because our bootloader is locked.
To fix this, get this recovery here, extract the recovery.img from the dowloaded zip and use the flash tool to flash it. Your device should boot into twrp normally.
Click to expand...
Click to collapse
OK, I'm going to try that right now. Thank you for your time and help.
It worked! Thank you so much! And I really like the recovery I now have as an added bonus. What a relief.
[SOLVED: Just downloaded latest version of Odin from Sammobile. What a relief!]
Hey guys, this is my first post so please forgive me for any mistakes.
My Note, unlocked SM-960U1, was stuck on June 1 security patch so I decided to flash to this month's firmware:
N960U1UEU2CSH2 for XAR
This got me stuck in a boot loop, which is now causing me to panic. I tried going to download mode and flashing it again but then another issued appeared:
it got stuck on a blue screen with the android and "erasing" I used HOME_CSC This isn't even supposed to erase anything!!!
I tried going on recovery mode but It didn't show up. I went to download mode then, and chose restart. That led me to the recovery mode and I chose restart again, and it showed me this:
#Reboot Recovery Cause is [[odin]RebootRecoveryAfterOdinDL]#
Support SINGLE-SKU
Block-Based OTA
Supported API: 3
# MANUAL MODE v1.0.0#
Rebooting...
That just froze and never rebooted! NO other commands work now. I am freaking out. The phone is hot also. Please someone help out!
Update
I can go on download mode now, but if I choose reset it sends me to the boot screen and then I see a dead android for a split second, then I'm in recovery mode. I can do nothing useful in there and restarting just freezes again
AppleToaster said:
I can go on download mode now, but if I choose reset it sends me to the boot screen and then I see a dead android for a split second, then I'm in recovery mode. I can do nothing useful in there and restarting just freezes again
Click to expand...
Click to collapse
you might have your terminology backwards. There isnt a button in download mode to reset the phone, there is one in recovery tho.
Anyways, if you can get to download mode, youre likely gonna be just fine. Just download a fresh copy of your firmware and flash it with Odin with your phone in download mode
Battery Drained
AppleToaster said:
I can go on download mode now, but if I choose reset it sends me to the boot screen and then I see a dead android for a split second, then I'm in recovery mode. I can do nothing useful in there and restarting just freezes again
Click to expand...
Click to collapse
I know it's been a year, but I recently experienced the issue. So this is for...someone else? lol
If you had a PASS on Odin and yet you stuck on boot loop, chances are your battery is drained, and it might not successfully boot to run configuration and deletion. Connect it to a power source, it might prompt it to the boot loop but do it regardless. After like 15-30 mins, you should see the battery charging indicator. You should be good!
Hey all
I'm updating to May Updates using This Guide and then plan to update to June.
Problem is that I send 'adb reboot recovery' and the phone restarts, shows the start up screen, then the Google logo, then restarts without ever showing the android logo.
I can get into Fastboot mode and try to select recovery with the volume and power, but again, it boots to the google logo, then back to the unlock warning and boots to my lock screen, never going to the android logo.
Ideas?
ibphantom said:
Hey all
I'm updating to May Updates using This Guide and then plan to update to June.
Problem is that I send 'adb reboot recovery' and the phone restarts, shows the start up screen, then the Google logo, then restarts without ever showing the android logo.
I can get into Fastboot mode and try to select recovery with the volume and power, but again, it boots to the google logo, then back to the unlock warning and boots to my lock screen, never going to the android logo.
Ideas?
Click to expand...
Click to collapse
Make sure you are using the latest adb/fastboot binaries (April, 2020). Flash the stock boot.img from the same guide. You will be unrooted but will be able to boot into System. Now read up on how to patch your own boot.img, it really is very simple. Personally I do not depend on, wait on, or use OTA's. The full image is available the first Monday of every month, and I extract/patch the boot.img from it. The whole operation including rooting takes just a few minutes. It's just one extra step. Once you get the pattern down it can be done very quickly, consistently and you're not depending on someone else's files. If you are bound and determined to use this method, you should seek out more guidance in the tutorial thread itself. Good luck. :good: