Develop Bugs

Phone won't boot

I turned off my phone (vzw galaxy nexus) today to replace the battery and it wouldn't boot back up. It was stuck on the Google screen. I've tried almost everything i could think of. I was running AOKP jb build 4 at the time with imo's lean kernel. I've tried doing restores and installing fresh aokp b4 and ics milestone 6 ROMs. The ics rom/restore goes into boot loop and any jb rom/restore gets stuck at Google.
A few odd things i did notice was that the first time i tried to wipe dalvik cache, cwm recovery was frozen for a few minutes and i had to battery pull but after that it was able to wipe it quickly. Another thing is when i restore my backups, there is a error in restoring /data.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Anyone know any fixes? I haven't tried installing a stock image yet since I'm not home but the situation doesn't look good.
Sent from my SCH-I535 using Tapatalk 2

How long did you let it sit at the Google screen? If an 'improper shutdown' is detected (no idea what constitutes improper), the JB boot loader does a full scan of the file structure to make sure everything is intact. I've had it take several minutes now and then, and others have reported longer before the Nexus animation begins.
Sent from my Galaxy Nexus using xda premium

I let it sit for a couple of minutes, but oh well i fixed it by flashing a stock Google image. Thanks for the suggestion though.
Sent from my SCH-I535 using Tapatalk 2

Impossible to brick Nexus,always there is a way to revive your phone .

youll have to flash factory image via fastboot to get it to work again
you can pull your sdcard data in recovery to your pc because after flashing via fastboot youll lose all your data even the sdcard data

ZenFone 2 - Flash memory failing?

Hi everyone,
This is regarding my ASUS ZenFone 2 ZE551ML (1.8 GHz CPU, 4 GB RAM, 16 GB ROM). A few days ago, after 1 year and 11 months of excellent service, suddenly I saw that some of the apps (Play Music, ASUS MiniMovie) were corrupted. But a simple uninstall and reinstall fixed them. Later that day, I was about to open settings when a message popped up "Unfortunately, settings has stopped". Rebooting the phone did not fix it and I was totally stuck as I was unable to clear the data also for the settings app which also requires "Settings" to function. I managed to do a factory reset after which, I could not even get to the home screen because that involves the Settings app as well.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I went on to proceed with factory reset from the recovery mode and to my shock, the recovery mode was also corrupted. Screen just froze with a USB logo. I tried to flash the recovery with xFSTK but got write error.
Then I took apart the device and cooled the flash memory (SK hynix manufactured) with some IPA.
The device booted up and was able to get to the home screen. Then I followed the ASUS standard downgrade procedure to downgrade the device from Marshmallow to Lollipop (which should force flashing of the recovery as well and everything). Phone was stable then. Then following ASUS standard upgrade procedure, I upgraded to Marshmallow and did a factory reset again. Set up everything and phone is rock stable now, performs good as new with no slow downs or anything.
My question is "What exactly happened?" It was never rooted and very well taken care of (even looks like new). Is the flash memory failing? Can the firmware get corrupted on its own?
Any answers would be appreciated. Thanks.

Hello I am also having the same issue? Can you please explain more about the way you have recovered. I love my Asus Zenfone2. I am trying to do Factory RESET which causes this issue. Do you mean, use IPA to clean the Memory side? Please help me. My email ID is [email protected]

Firstly, try to flash it with xFSTK using the tutorial here on XDA. If it fails, then you need to take the phone apart.

Unable to boot error but still have access to twrp and rom

Hello,
I've been at war with my phone trying to figure out hot to fix this bootloader problem but no good answers. If I turn on my phone I get the wait 5 seconds message and if I hit the power/lock button before waiting I get this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If I leave it alone and don't hit the power/lock button it will boot normally to my rom. I also have access to twrp. Any help to fixing this is greatly appreciated
I am on Dirty unicorn 11.6
Jaguar rom also come buggy for my phone some reason? And briefly can some tell me why my phone doesn't charge while it off? It turns on as soon as I put in the charger?
Update: I got bored so I flashed my ROM again and it went away. But as soon as I rebooted and flashed gapps it broke it again. But I'm still able to access the ROM. It also breaks when installing magisk. I'm guessing it breaks the boot image
Solved: I flashed a stock rom using qilf. It fixed the problem but twrp got removed and bootloader remained UNLOCKED so i just flash twrp via adb fastboot and got my root back

yes i got the same problem im waiting for any solution

Nitro1010 said:
Hello,
I've been at war with my phone trying to figure out hot to fix this bootloader problem but no good answers. If I turn on my phone I get the wait 5 seconds message and if I hit the power/lock button before waiting I get this
If I leave it alone and don't hit the power/lock button it will boot normally to my rom. I also have access to twrp. Any help to fixing this is greatly appreciated
I am on Dirty unicorn 11.6
Jaguar rom also come buggy for my phone some reason? And briefly can some tell me why my phone doesn't charge while it off? It turns on as soon as I put in the charger?
Update: I got bored so I flashed my ROM again and it went away. But as soon as I rebooted and flashed gapps it broke it again. But I'm still able to access the ROM. It also breaks when installing magisk. I'm guessing it breaks the boot image
Click to expand...
Click to collapse
I got this problem too....then i flashed stock rom via qfil and then unlocked bootloader and flashed twrp.....now its working fine

unable to install or launch TWRP

Hey,
I've unlocked my Mi 6 today (i'm using the global developer ROM 8.9.13 (MIUI10)) and wanted to root it, as many guides said I have to replace the default recovery with something like TWRP
result was:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
after leaving it like that for 30 minutes nothing has changed, the screen on my mobile was the the default fastboot screen nothing ever changed
so i tried to just launch TWRP without installing it:
nothing changed like before and i've stopped after 5minutes
i also have the same result with RedWolf Recovery Project:
I also tried using XiaoMiTool but all i got was the message that my phone is not connected to my MiAccount and still locked and did nothing
Does anyone have any idea whats going?
Edit:
seems like flashboot commands dont work? tried flashboot continue to reboot the device after checking with fastboot devices to see if it was recognized by the system and it was indeed.
and the result were the same as above cmd was stuck mobile didnt react....
Thanks
Dugma

Dugma said:
Hey,
I've unlocked my Mi 6 today (i'm using the global developer ROM 8.9.13 (MIUI10)) and wanted to root it, as many guides said I have to replace the default recovery with something like TWRP
[...]
Click to expand...
Click to collapse
I'd rather flash the recovery than just booting to it. You can flash it with fastboot flash recovery recovery.img
You should be able to boot to recovery afterwards. Or at least that's what I did when I bought my phone. I updated to the latest version of MIUI (android 8.0), then I enabled "oem unlock") and I was able to flash twrp with no problems. Keep in mind that the stock rom erases any custom recovery with the default one on boot.

Facing the same issue. Tried everything but no success.

Question Rooted Pixel 6 Pro - no longer receiving updates

Hi all, I have rooted my pixel 6 pro since day 1 and always used the magisk way of patching and restoring images for updates, since the February update Google tells me updates are no longer supported on my device per screenshots, anyone else had this issue and know how to resolve it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

You might want to backup, uninstall magisk in the app, reboot. Then full reset/wipe and reboot. Then manually update to the latest May 2022 version using adb or the android flash tool. Something has gone awry with your software. Better to be safe than sorry.

Just used the android flash tool and flash the latest image without the wipes, then reroot, should fix it all.

Gytole said:
Just used the android flash tool and flash the latest image without the wipes, then reroot, should fix it all.
Click to expand...
Click to collapse
But with my device rooted and my bootloader unlocked won't that throw me into a boot loop? Then I'll have to completely wipe and restore no?

zamarax said:
But with my device rooted and my bootloader unlocked won't that throw me into a boot loop? Then I'll have to completely wipe and restore no?
Click to expand...
Click to collapse
Nope! Quite the opposite if I get stuck in a bootloop I just use the flash tool to fix it. No loss of data, but you need to re-boot the magisk boot image then reflash in magisk afterwards as it will completely remove magisk

So I did what you suggested and now my device is stuck in a boot loop with corrupt data, I did however patch the boot.img previously when I tried to send it to the device via ADB so I'm going to try to push that now and see what happens. Here are the options I selected for Android Flash Tool.

Second attempt with not selecting 'Disable Verity' and 'Disable Verification' worked successfully.
Thank you, I really appreciate it!

zamarax said:
Second attempt with not selecting 'Disable Verity' and 'Disable Verification' worked successfully.
Thank you, I really appreciate it!
View attachment 5608917
Click to expand...
Click to collapse