Develop Bugs

[Q] Nexus stuck in reboot loop (what to do?)

I felt my nexus reboot during class today(it was in my pocket) and then it got stuck in a reboot loop, it freezes during boot animation and starts over.
I have tried to pull out the battery, to do a cold boot as well.
It is rooted, and i followed one of the early tutorials to do so (i don't remember exactly which).
Is there anything i can do without loosing my data(no backup, i know,stupid me).
Can i try to reset the bootloader for example?
I have also received 3 system updates the last week, assumable from samsung, (yakjuxw). But it hasn't increased my android version. I don't know if this has anything to do with my problem, but i feel like i should mention it.

+1 on this too...i was checking my messages this morning and it just rebooted. havent had this ever happen to me, no matter wiping, reflashing, restore....nothing works...just keeps rebooting at google screen 4 or 5 times...then it just stays on the screen, phone starts to heat up too.

Same here, I installed Chrome bate last night. Did you guys do the same? I wonder if it is the cause of the problem.

i did try out chrome beta yesterday, but ended up uninstalling it. im on a ir10 modaco kitchen rom with a 1.35ghz oc custom kernal.

I am on stock rom without root.
I found the below and it scares me. Looks like there isn't any fix...
http://androidforums.com/samsung-galaxy-nexus/493450-dreaded-bootloop.html

Snobjorn said:
I felt my nexus reboot during class today(it was in my pocket) and then it got stuck in a reboot loop, it freezes during boot animation and starts over.
I have tried to pull out the battery, to do a cold boot as well.
It is rooted, and i followed one of the early tutorials to do so (i don't remember exactly which).
Is there anything i can do without loosing my data(no backup, i know,stupid me).
Can i try to reset the bootloader for example?
I have also received 3 system updates the last week, assumable from samsung, (yakjuxw). But it hasn't increased my android version. I don't know if this has anything to do with my problem, but i feel like i should mention it.
Click to expand...
Click to collapse
Can you access the bootloader?

Snobjorn said:
I felt my nexus reboot during class today(it was in my pocket) and then it got stuck in a reboot loop, it freezes during boot animation and starts over.
I have tried to pull out the battery, to do a cold boot as well.
It is rooted, and i followed one of the early tutorials to do so (i don't remember exactly which).
Is there anything i can do without loosing my data(no backup, i know,stupid me).
Can i try to reset the bootloader for example?
I have also received 3 system updates the last week, assumable from samsung, (yakjuxw). But it hasn't increased my android version. I don't know if this has anything to do with my problem, but i feel like i should mention it.
Click to expand...
Click to collapse
i am pretty sure if you reset the bootloader it will wipe everything. just go into recovery and do a factory reset (last option of course).

I installed google chrome earlier today aswell.
I have now tried to restore from an earlier nandroid backup, but it fail at the \data stage.
Factory reset didnt help either.
edit:
However, i was able to pull data using adb. Saved my images atleast.
also: i have clockworkmod v5.5.0.2

Do you have the SDK installed on your pc? If so, you should connect it and run ddms. You can then watch the log and see where your phone is crashing. Maybe that would give a starting point to what is wrong.

I start ddms, and my phone pops up under devices witha nomber as name, ther after '??' and 'unknown' nothing else. This is when my phone is in clockworkmod recovery . it disappears when i try reboot.

Hmmm that's weird. You might have to try flashing the stock images in fastboot.

El Daddy said:
Hmmm that's weird. You might have to try flashing the stock images in fastboot.
Click to expand...
Click to collapse
Hell yeah! This worked for me.
Sent from my Galaxy Nexus using xda premium

[Q] Rooted 4.3 OTA soft-bricked, wouldn't load any apps

So basically I did this:
http://forum.xda-developers.com/showthread.php?t=2538991
But unfortunately, I hadn't realized that the mobile hotspot was sealed up in that update. So I looked it up, and saw that someone had recommended this:
http://forum.xda-developers.com/showthread.php?p=48326067
So I went into TWRP and installed it. But that didn't work. When I booted back up EVERY app was crashing immediately except the stock Samsung apps (Messaging, Email, etc.). I tried to reverse it with the original framework-res.apk but when I did, the phone would get stuck at the AT&T logo (which was silent). I went back and forth a few times (when I applied that tethering mod, the phone would boot; when I tried to reverse it, it wouldn't), then did a factory reset in TWRP. After that, the phone booted, but the Setup Wizard would crash. So I did a Nandroid restore in TWRP and now the phone hangs at the AT&T logo no matter what I do.
My question is, what can I do now? I have a replacement device coming through warranty just in case, but it would be much better to just fix this one. However, I want to be certain and not HARD brick the phone...

I have never been able to restore a stock 4.3 nandroid without everything crashing. I have always had to go back into recovery and wipe data/factory reset and wipe cache and dalvik cache then reboot and go through the whole setup process again. If that doesn't work you could try installing the stock debloat ROM from this thread. That's what I am running and it works great. http://forum.xda-developers.com/showthread.php?t=2540998
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Iantuition said:
So basically I did this:
http://forum.xda-developers.com/showthread.php?t=2538991
But unfortunately, I hadn't realized that the mobile hotspot was sealed up in that update. So I looked it up, and saw that someone had recommended this:
http://forum.xda-developers.com/showthread.php?p=48326067
So I went into TWRP and installed it. But that didn't work. When I booted back up EVERY app was crashing immediately except the stock Samsung apps (Messaging, Email, etc.). I tried to reverse it with the original framework-res.apk but when I did, the phone would get stuck at the AT&T logo (which was silent). I went back and forth a few times (when I applied that tethering mod, the phone would boot; when I tried to reverse it, it wouldn't), then did a factory reset in TWRP. After that, the phone booted, but the Setup Wizard would crash. So I did a Nandroid restore in TWRP and now the phone hangs at the AT&T logo no matter what I do.
My question is, what can I do now? I have a replacement device coming through warranty just in case, but it would be much better to just fix this one. However, I want to be certain and not HARD brick the phone...
Click to expand...
Click to collapse
if you can get back to twrp , clear everything then flash the official correct file that yu want then see if that works...restore your apps/data after a clean refresh for your phone
remember panicking and being paranoid with flashing/rooting is not a a good idea, always rethink what you did wrong, let the phone cool down, research know what you re doing then fix it
dont rush, cuz rushing leads to bricks (learned from experience from day 1 with root)

bellifritz said:
I have never been able to restore a stock 4.3 nandroid without everything crashing. I have always had to go back into recovery and wipe data/factory reset and wipe cache and dalvik cache then reboot and go through the whole setup process again. If that doesn't work you could try installing the stock debloat ROM from this thread. That's what I am running and it works great. http://forum.xda-developers.com/showthread.php?t=2540998
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
How'd you do that? Just the regular factory reset? Cause the setup wizard wouldn't even run after that.
winosxbuntu said:
if you can get back to twrp , clear everything then flash the official correct file that yu want then see if that works...restore your apps/data after a clean refresh for your phone
remember panicking and being paranoid with flashing/rooting is not a a good idea, always rethink what you did wrong, let the phone cool down, research know what you re doing then fix it
dont rush, cuz rushing leads to bricks (learned from experience from day 1 with root)
Click to expand...
Click to collapse
Okay. Which official file though? and should I clear the system and boot partitions too?

Iantuition said:
How'd you do that? Just the regular factory reset? Cause the setup wizard wouldn't even run after that.
Okay. Which official file though? and should I clear the system and boot partitions too?
Click to expand...
Click to collapse
try this two links, everything on flashing 4.3 stock/rooting and fix http://forum.xda-developers.com/showthread.php?t=2540998
http://forum.xda-developers.com/showpost.php?p=46804338
either one will work
AND dont clear everything just cache/dalvik/format system/ factory reset BUT follow the instructions given for that rom to avoid any problems

winosxbuntu said:
try this two links, everything on flashing 4.3 stock/rooting and fix http://forum.xda-developers.com/showthread.php?t=2540998
http://forum.xda-developers.com/showpost.php?p=46804338
either one will work
AND dont clear everything just cache/dalvik/format system/ factory reset BUT follow the instructions given for that rom to avoid any problems
Click to expand...
Click to collapse
Okay so I just leave boot alone. Let us pray, LOL. And sorry if I've sounded like a supernoob but I'm trying to be REALLY careful.

Iantuition said:
How'd you do that? Just the regular factory reset? Cause the setup wizard wouldn't even run after that.
Hit the power button to make the screen go to sleep. Hit the power button again to wake it up. Nothing should be crashing while you are on the lock screen so just hold the power button until the power menu appears and select power off. Once it powers off hold the volume up, home button and power button until you see the blue words in the upper left corner of the screen I believe it says loading recovery. Release the power button but continue holding the other 2 buttons until recovery loads. Now wipe data, cache and under advanced wipe dalvik cache. Reboot and everything should quit crashing but you will have to setup your account and apps again. That is the only way that I can get stock touchwiz 4.3 nandroids to work.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse

Iantuition said:
Okay so I just leave boot alone. Let us pray, LOL. And sorry if I've sounded like a supernoob but I'm trying to be REALLY careful.
Click to expand...
Click to collapse
it will work, i agree with what bell said. unless its hard bricked then no worries just keep calm and fix the damn phone

Crosshatch Issue With ROMs & TWRP. Strange Occurrences

Ok, So Here's The Deal.. The Thing.. The WTF
So I had an older version of the Scorpion ROM installed and working fine for a while and wanted to change it up. I downloaded the newest TWRP. Both image and installer.zip, newest Magisk and RR 7.
I flashed the latest stock and you know, followed all the proper steps and after I flashed RR 7, it wouldn't boot up. (Not the issue) as others have had the same issue with RR 7. I left a post about that on the RR 7 thread and went about reflashing stock and proceeded to find a different ROM to check out.
No matter what I try to flash: Lineage, Scorpion, RR 7, dotOS the same thing happens... Everything flashes like it should, but then it won't boot, AND THEN every time I boot back to TWRP to try something else the haptic feedback vibration thing on the pixel 3 xl goes banana sandwich crazy and won't shut off until I reboot to fastboot to flashall to start over. LOL
And not only that but when I jump back to TWRP to try to flash something else stored on the phone, it says the storage is empty and there are nothing available in the menu. And I couldn't get a screenshot but there were some errors that have popped up in twrp as well...
Could This Be An Issue WITH TWRP itself? Because it does it with every single ROM I have flashed today. It's very strange. I have never ran into any issues like this when flashing ROMs, Kernals, etc.
I'm lost. Any help would be awesomely appreciated.
UPDATE: It now vibrates constantly in TWRP and when I reflashed to factory it did the corrupt software screen so I gave it a good ole' factory rest and then it was is stuck in a loop at the G while conecting and disconnecting to the USB over and over and over... now back to corrupt software screen.
I guess I'm just going to have to reflash Stock and just leave it.
Update 2: Still Give The Corrupt Software Thing After Performing FlashAll - soooooooooooooooo

Slo-mo Designs said:
Ok, So Here's The Deal.. The Thing.. The WTF
Could This Be An Issue WITH TWRP itself? Because it does it with every single ROM I have flashed today. It's very strange. I have never ran into any issues like this when flashing ROMs, Kernals, etc. I'm lost. Any help would be awesomely appreciated.
UPDATE: It now vibrates constantly in TWRP and when I reflashed to factory it did the corrupt software screen so I gave it a good ole' factory rest and then it was is stuck in a loop at the G while conecting and disconnecting to the USB over and over and over... now back to corrupt software screen.
I guess I'm just going to have to reflash Stock and just leave it.
Update 2: Still Give The Corrupt Software Thing After Performing FlashAll - soooooooooooooooo
Click to expand...
Click to collapse
Couple of things. Yes there was an issue with v3.2.3-4 TWRP and the vibrator, but that is separate from your boot issues. Go to the dedicated TWRP thread. As for your updates, 1) an FDR just deletes your data and so would not solve your issue. and 2) Guessing you removed the -w switch from the flash-all script or you would not be getting the corrupt software screen. Run the script again with the wipe switch in place, allowing it to wipe your partitions and start over. You've already deleted all your data with the FDR so it won't matter. Best of luck!

Always late to the party.
v12xke said:
Couple of things. Yes there was an issue with v3.2.3-4 TWRP and the vibrator, but that is separate from your boot issues. Go to the dedicated TWRP thread. As for your updates, 1) an FDR just deletes your data and so would not solve your issue. and 2) Guessing you removed the -w switch from the flash-all script or you would not be getting the corrupt software screen. Run the script again with the wipe switch in place, allowing it to wipe your partitions and start over. You've already deleted all your data with the FDR so it won't matter. Best of luck!
Click to expand...
Click to collapse
So yeah... I just now logged back on and saw your response [I have had notification issues on everything from Reddit to FB since I have had the 3XL]
About the response, I have had the issue with it showing the corrupt software screen a bunch when flashing new stuff. The reason I perform the Factory Slap is because it allows me to enter the menu where I have the option to "Boot from ADB" or whatever it says, sideloading seems to be the only way I can make progress when it starts giving the corrupt error.. The reason I didn't perform the full wipe but I can't remember exactly why now since that was over a month ago.
But I finally got it fixed, and I was going to repost because I had found a way to prevent the vibration thing from happening in TWRP but by the time I got around to posting, the new update had fixed it. Lol

Failed to clear BCB message - A520F

Hello.
I was fiddling around with my phone today and wanted to clear the cache from the Recovery.
After rebooting tho it showed me a message (note that I never toggled OEM unlock or even accessed recovery/download mode or anything before today):
fail to open recovery_cause(No such file or directory)#
Reboot Recovery Cause is [UNKNOWN]# No Support SINGLE-SKU
File Based OTA
Supported API: 3
MANUAL MODE v1.0.0#
Sucessfully verified dmverity hash tree
E:Failed to clear BCB message:failed to find /misc partition
Click to expand...
Click to collapse
And after a minute or so the Recovery showed up. I went to delete the cache, all went well until I was met with the same message at the end:
E:Failed to clear BCB message:failed to find /misc partition
Click to expand...
Click to collapse
Should I worry about anything ? The phone booted normally but I'm a bit skeptical about that error (maybe the cause of my as of late noticeable battery drain ?) and any help is appreciated!
EDIT: Another thing to notice is that when booting into recovery, it seems the phone is trying to install an update which isn't there, and only then takes me to the recovery menu.

Hir0xM said:
Hello.
I was fiddling around with my phone today and wanted to clear the cache from the Recovery.
After rebooting tho it showed me a message (note that I never toggled OEM unlock or even accessed recovery/download mode or anything before today):
And after a minute or so the Recovery showed up. I went to delete the cache, all went well until I was met with the same message at the end:
Should I worry about anything ? The phone booted normally but I'm a bit skeptical about that error (maybe the cause of my as of late noticeable battery drain ?) and any help is appreciated!
EDIT: Another thing to notice is that when booting into recovery, it seems the phone is trying to install an update which isn't there, and only then takes me to the recovery menu.
Click to expand...
Click to collapse
Everything you said I think is normal. So don't worry about it. It still clears cache or whatever you do.

SnowFuhrer said:
Everything you said I think is normal. So don't worry about it. It still clears cache or whatever you do.
Click to expand...
Click to collapse
I see, thank you
It's a weird bug so that's why I was worried. I did read some reports that some users couldn't wipe data due to this in the Recovery and it got me a bit worried.
Let's hope it's just a stupid bug and nothing more. Thanks again!

Hir0xM said:
I see, thank you
It's a weird bug so that's why I was worried. I did read some reports that some users couldn't wipe data due to this in the Recovery and it got me a bit worried.
Let's hope it's just a stupid bug and nothing more. Thanks again!
Click to expand...
Click to collapse
No problem. Report if it doesn't work.

SnowFuhrer said:
No problem. Report if it doesn't work.
Click to expand...
Click to collapse
Hi there
I have this issue. I cant factory reset the phone as it says MDM does not allow this.
so I used odion to reload the Stock Firmware on these but now I have FRP on this.
as it's a work device & dont know the user that last used this phone.
even after the flash I still have bcb message
Is there any other way of sorting this out.

UmangA said:
Hi there
I have this issue. I cant factory reset the phone as it says MDM does not allow this.
so I used odion to reload the Stock Firmware on these but now I have FRP on this.
as it's a work device & dont know the user that last used this phone.
even after the flash I still have bcb message
Is there any other way of sorting this out.
Click to expand...
Click to collapse
When you get into work phones, things get really ugly. Can you wipe data by flashing just csc in Odin?

Similar problem with S7, it just keeps rebooting
I have an S7, I have the same problem, the phone started freezing and rebooting every minute. So decided to Wipe out the cache and do factory reset, saw this message "E:Failed to clear BCB message:failed to find /misc partition"
The phone never goes past the Galaxy S7 Android logo screen most of the time, if it did manage to go pass, it freezes after 2 to 3 mins and reboots.
So I tried and successfully rooted, installed TWRP, took a backup and tried to wipe cache, it failed.
formatted the and tried to restore from backup and it failed, as it never went pass the S7 logo screen.
so I tried Lineage OS 17 and it worked like a charm
then tried back to Android 9 ROM from Samsung, it too started to hang and freeze - If it was an Hardware issue, I would expect Lineage OS to freeze too.
I think and it looks like Samsung is forcing its customers to buy new phones .....
Please help
thanks
Z

How to fix Galaxy J7 prime texting or calling issues: not receiving text or call aler
How to fix Galaxy J7 prime texting or calling issues: not receiving text or call alerts?
My phone is Samsung galaxy j7 prime
when I factory reset it show me this error E:Failed to clear BCB message: failed to open /dev/block/platform/13540000.dwmmc0/by-name/MISC: No such file or directory

Galaxy tab A 8
Even without appearing to have any hardware problems, my galaxy tab shows exactly the same messages described above and the same situations. I suspect it is even programmed obsolescence. Would anyone have any reliable tutorial on how to reset it completely and install a rom that was stable and compatible? Thank you :fingers-crossed::fingers-crossed:

Exactly the same problem
Hi guys,
I exactly do have the same problem. I upgraded from LineageOS 16 (which was working smooth.y ) to LineageOS 17.1 and faces a problem wit IMEI, So I tried to revert back to Stock ROM, flashed via ODIN latest version.
I could flash the stock ROM (doing NAND Eras and Re-Partition due to Vendor partition). But after reboot, the ROM won't boot and stuck with SAMSUNG screen blinking.. I managed to access the Stock Bootloader and could do a full factory reset, but I still get the error message like above.
If anyone has an idea how to solve...

My sister had many randomly chrashing apps and ask me how to fix it.
In recovery the same message was printed. BCB and /misc ...
Well I tried to clean install stock rom (A5 2017) with odin, but the user data was never deleted ... Don't know how to use odin ...
I have then flashed lineageos and now there are random reboots and apps are only crashing sometimes once opened.
I attached a crash log. The app crashin is called antennapod (https://play.google.com/store/apps/details?id=de.danoeh.antennapod&hl=de&gl=US)
Anyone knows what causing these? And if they are still related to BCB and/or /misc?

houston_ said:
I attached a crash log. The app crashin is called antennapod (https://play.google.com/store/apps/details?id=de.danoeh.antennapod&hl=de&gl=US)
Click to expand...
Click to collapse
Somehow tha attachment was delincined.
Log_2020-12-01_21-40-15.txt
drive.google.com

Camera won't open; YouTube doesn't load

My Pixel 2XL is acting up starting this morning
- The camera app won't open, it crashes instantly. Other apps can't access the camera. I tried clearing the data, cache and restarting. Nothing has worked so far.
- YouTube is stuck in a load loop, all is see is the loading circle to infinity. I attempted to clear cache and data and install an older version. Again, nothing works.
- Restarting didn't solve anything.
- Both issues linger in safe mode.
Any ideas on wtf could be going on?

boeder9 said:
My Pixel 2XL is acting up starting this morning
- The camera app won't open, it crashes instantly. Other apps can't access the camera. I tried clearing the data, cache and restarting. Nothing has worked so far.
- YouTube is stuck in a load loop, all is see is the loading circle to infinity. I attempted to clear cache and data and install an older version. Again, nothing works.
- Restarting didn't solve anything.
Any ideas on wtf could be going on?
Click to expand...
Click to collapse
Sounds like you've got an unexplained, interesting and unwanted glitch! Are you full stock, or rooted?
Your only solution will likely be a factory reset, or possibly a dirty fastboot flash of the factory image so as not to wipe your data. You might even get by with just fastbooting the vendor image as well.

Badger50 said:
Sounds like you've got an unexplained, interesting and unwanted glitch! Are you full stock, or rooted?
Your only solution will likely be a factory reset, or possibly a dirty fastboot flash of the factory image so as not to wipe your data. You might even get by with just fastbooting the vendor image as well.
Click to expand...
Click to collapse
Full stock.
I want to avoid any resets tbh.
Could the OTA Monthly Update solve anything?

boeder9 said:
Full stock.
I want to avoid any resets tbh.
Could the OTA Monthly Update solve anything?
Click to expand...
Click to collapse
It's definitely worth a try. Just like fastbooting the factory image without the -w :good:

Badger50 said:
It's definitely worth a try. Just like fastbooting the factory image without the -w :good:
Click to expand...
Click to collapse
I guess I'll wait for the Sept update, if that doesn't work, I'll try the manual flashing
Sent from my Pixel 2 XL using Tapatalk

boeder9 said:
I guess I'll wait for the Sept update, if that doesn't work, I'll try the manual flashing
Click to expand...
Click to collapse
The job of flashing the factory image while saving data is super easy. If you have a pc and a half hour your golden. If you wanna give it a go, let us know and one of us can walk you through it if you have any concerns...
Sent from my Pixel 2 XL using XDA Labs

Even i have the same camera issue. It suddenly stopped working. Some times it does start after a few tries if i hold it in landscape mode. But mostly it keeps crashing and doesn't even allow other apps to access camera.

So a quick follow-up. Here is what i've done so far:
- Cleared storage/cache and uninstalled the camera updates
- Installed Android 10
- Updated to Camera 7.0 Beta
- Booted into safe mode.
None of these actions solved the issue.
I then resetted my phone (2 days ago) and that seemed to have solved the problem. However, starting a few minutes ago and while I was taking photos, I again lost focus in the lens and the app crashed.
What could be the issue? It seems its the focus is problematic though it worked for a good while. Surely it isn't hardware as the camera worked for ~40 hours after resetting.

boeder9 said:
What could be the issue? It seems its the focus is problematic though it worked for a good while. Surely it isn't hardware as the camera worked for ~40 hours after resetting.
Click to expand...
Click to collapse
Just because it worked correctly for around 40 hours after a reset doesn't mean that you can rule out hardware issues as a culprit. Especially since you have done everything you possibly could on the software end and it hasn't helped.

Strephon Alkhalikoi said:
Just because it worked correctly for around 40 hours after a reset doesn't mean that you can rule out hardware issues as a culprit. Especially since you have done everything you possibly could on the software end and it hasn't helped.
Click to expand...
Click to collapse
You're absolutely right. I did another reset (this time without restoring from backup) and the camera doesn't open at all. I'm hoping its a OS bug.
Thank god the Pixel 4 will be released in 4 weeks.

CyberpodS2 said:
The job of flashing the factory image while saving data is super easy. If you have a pc and a half hour your golden. If you wanna give it a go, let us know and one of us can walk you through it if you have any concerns...
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
I have exactly the same problem that they report, it does not open cameras or YouTube.
Can you give me the steps to upload a factory image?
Regards