I'm on Android 10 april update and want to reinstall stock android 10 rom. My phone is not rooted, Bootloader locked and no custom recovery install.
The closest thing to reinstall for you is to perform a factory reset. If you want to reflash whole rom, unlock the bootloader and flash stock rom via fastboot. Not sure why would you want to do that though.
_mysiak_ said:
The closest thing to reinstall for you is to perform a factory reset. If you want to reflash whole rom, unlock the bootloader and flash stock rom via fastboot. Not sure why would you want to do that though.
Click to expand...
Click to collapse
After installing April update (perviously on Android 10 march update) and using it for few hours, my phone got stuck so I rebooted by holding power down button. Error appeared " Can't load Andoid system. Your data might be corrupted". I was forced to factory reset and lost my data. Installed my apps again and reboot for some reason only to be presented by same error again. So I thought reinstalling rom might fix this error.
mrhamza15 said:
After installing April update (perviously on Android 10 march update) and using it for few hours, my phone got stuck so I rebooted by holding power down button. Error appeared " Can't load Andoid system. Your data might be corrupted". I was forced to factory reset and lost my data. Installed my apps again and reboot for some reason only to be presented by same error again. So I thought reinstalling rom might fix this error.
Click to expand...
Click to collapse
It would be useful to troubleshoot why the phone doesn't boot (with "adb shell logcat") - on fully stock phone it might be caused by some app or HW defect. Logcat should reveal the reason for crash. What's the status of your phone now?
_mysiak_ said:
It would be useful to troubleshoot why the phone doesn't boot (with "adb shell logcat") - on fully stock phone it might be caused by some app or HW defect. Logcat should reveal the reason for crash. What's the status of your phone now?
Click to expand...
Click to collapse
Factory reset again, installed apps and rebooted it twice. Fortunately, it didn't happen again but I'm still worried. I didn't flash stock rom. Just factory reseted.
mrhamza15 said:
Factory reset again, installed apps and rebooted it twice. Fortunately, it didn't happen again but I'm still worried. I didn't flash stock rom. Just factory reseted.
Click to expand...
Click to collapse
Enable ADB in developer settings so you can troubleshoot it if your phone crashes again.
Related
Was just curious, was hopin to send my phone back in to att today (due to a power button that no longer works) since i got a replacement. Unrooted back to stock and deleted all of my photos and everything and then got stuck on a bootloop so im unable to do a hard reset. Unfortunately I can't even get into 3e recovery since my power button is broken, so is it possible to do a hard/factory reset to wipe the internal SD from odin or any other program? much appreciated
If the phone is on and booted up, you can do a wipe data/factory reset from the settings menu within the phone:
Menu > Settings > Privacy > Factory Data Reset in Gingerbread
Menu > Settings > Back up and reset > Factory data reset in ICS
If your phone is not on, there are several ways to boot it:
adb reboot
flash stock firmware in Odin with reboot checked
etc.
You can also get into recovery with:
adb reboot recovery
creepyncrawly said:
If the phone is on and booted up, you can do a wipe data/factory reset from the settings menu within the phone:
Menu > Settings > Privacy > Factory Data Reset in Gingerbread
Menu > Settings > Back up and reset > Factory data reset in ICS
If your phone is not on, there are several ways to boot it:
adb reboot
flash stock firmware in Odin with reboot checked
etc.
You can also get into recovery with:
adb reboot recovery
Click to expand...
Click to collapse
I'll look into adb recovery. The phone is not on for clarification. It's stuck in a permanent bootloop.
Sent from my SAMSUNG-SGH-I777 using XDA
ChocolateSnow said:
I'll look into adb recovery. The phone is not on for clarification. It's stuck in a permanent bootloop.
Sent from my SAMSUNG-SGH-I777 using XDA
Click to expand...
Click to collapse
If it were my phone, I would flash the stock firmware package in Odin, with reboot checked. Once the flash completes, the phone should boot normally. Then you should be able to wipe data/factory reset from the phone.
or try the adb reboot recovery to see if that will work.
If you still have a bootloop after flashing stock again, then you may need to flash the full stock distribution. You don't say in the OP how the phone got into a bootloop, or what you flashed to stock from.
creepyncrawly said:
If it were my phone, I would flash the stock firmware package in Odin, with reboot checked. Once the flash completes, the phone should boot normally. Then you should be able to wipe data/factory reset from the phone.
or try the adb reboot recovery to see if that will work.
If you still have a bootloop after flashing stock again, then you may need to flash the full stock distribution. You don't say in the OP how the phone got into a bootloop, or what you flashed to stock from.
Click to expand...
Click to collapse
Apologies again for not being specific and I appreciate your efforts in going back and forth with me.
The reason my phone is currently in a bootloop was when I followed the process on your thread for preparing my phone to be sent back for warranty replacement. Using odin I flashed the stock image (UCKH7, and my flash counter reads NO which is good) and after the phone extracted the files and Odin said I was bone stock, my phone just continuously reboots on the att startup animation (which you predicted and outlined could be fixed by going into 3e recovery and doing a factory reset but since my power buttons rubbish, I can't select any options even if I do get into 3e recovery)
Edit: I also flashed to stock from AOKP and I even followed through your process a second time thinking that re-flashing the stock firmware would remove the bootloop, however no luck
Sent from my SAMSUNG-SGH-I777 using XDA
You probably don't need the bootloaders. I think adb reboot recovery is your best option. Let me know if it works.
creepyncrawly said:
You probably don't need the bootloaders. I think adb reboot recovery is your best option. Let me know if it works.
Click to expand...
Click to collapse
Even if he gets into recovery, how will he select any of the menu options with a broken power button?
mattdm said:
Even if he gets into recovery, how will he select any of the menu options with a broken power button?
Click to expand...
Click to collapse
Damn you're right. What was I thinking?
I guess the only option is just take the phone back as is.
creepyncrawly said:
Damn you're right. What was I thinking?
I guess the only option is just take the phone back as is.
Click to expand...
Click to collapse
Yeah that's what I figured as well since I can't select any options. It's Alright, luckily I deleted anything personal before even doing the unroot. And the Odin flash definitely unlinked all of my account info from the phone so I was just asking for my own peace of mind and curiosity. Just dropped the phone off in the mail this morning, thank you both for your help. You guys rule.
Sent from my SAMSUNG-SGH-I777 using XDA
creepyncrawly said:
Damn you're right. What was I thinking?
I guess the only option is just take the phone back as is.
Click to expand...
Click to collapse
Yeah I can't see any other option. Should be fine though...it has stock firmware and kernel on it now, even with the bootloop. He can just say, my phone went crazy and I don't know why!
mattdm said:
Yeah I can't see any other option. Should be fine though...it has stock firmware and kernel on it now, even with the bootloop. He can just say, my phone went crazy and I don't know why!
Click to expand...
Click to collapse
That's the plan! Thanks again
Sent from my SAMSUNG-SGH-I777 using XDA
Hi.
Met a problem with my GT-I9300. When I shut the phone off it just reboots. The phone was rooted and running a custom rom when this started. Now I have unrooted with mobile Odin and flashed a official firmware but the problem persists.
I have even tried a battery pull. When battery is inserted again the phone remains off til I push the powerbutton. But when I try to turn it off after this it just reboots again.
Anyone else had this? Tips on what to do?
I've never had any luck fixing this problem. I always had to wipe and flash. However, as a temporary fix, you can power off from recovery.
Sent from my GT-I9300 using Tapatalk
can I ask what you are doing when you turn it off?
Sent from the asylum
Just to clarify, even wipe the phone and restore it to stock completely by flashing official firmware doesnt solve it.
When I turn it off I hold powerbutton til i get the powermenu. From there I choose "turn off". Phone does what it should, screen goes off and everything, only a few seconds later the phone boots again.
basse10000 said:
Just to clarify, even wipe the phone and restore it to stock completely by flashing official firmware doesnt solve it.
When I turn it off I hold powerbutton til i get the powermenu. From there I choose "turn off". Phone does what it should, screen goes off and everything, only a few seconds later the phone boots again.
Click to expand...
Click to collapse
If the phone was totally cleaned formatted sd card and stock firmware installed then its a hardware problem .
But my guess is it as not totally clean .
....................................
Clean Slate for those that balls up the firmware .Or need to return to service or decide if its hardware/firmware problem .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card .
Remove battery
Boot to download mode
Open Odin
Install correct stock firmware .
jje
I have now tried to wipe and format sys/data/cach/sd in cwm. Flashed stock firmware via odin. Still same issue. Guess its hardware.
Thanks anyway.
This may sound strange, but is this the clock problem the Desire HD had.
In time settings, uncheck the auto update.
Change time & date to something random.
Power off and pull the battery before it reboots.
Give it a min, power up, reselect auto update and reboot.
Should be good to go. If its the same problem that is.
Sent from the App that Time Forgot.
It also happens to me yesterday, I wipe cache, system, data, reinstall roms (CM and AOKP) and is still happening
r0uzic said:
It also happens to me yesterday, I wipe cache, system, data, reinstall roms (CM and AOKP) and is still happening
Click to expand...
Click to collapse
It happened also to me once. I flashed my rom in the same order as you did. But what my problem solved was, I made a wipe AFTER I installed the ROM. After that, I didn't had this issue anymore.
These are the steps I did...
- Get into the CWM recovery
- Wipe Data/factory reset
- Wipe Cache
- Wipe Dalvik-Cache
Hope it works also to you...
Solved
I solved it by flashing a later official firmware - XXALF6.
Darkrider82 said:
It happened also to me once. I flashed my rom in the same order as you did. But what my problem solved was, I made a wipe AFTER I installed the ROM. After that, I didn't had this issue anymore.
These are the steps I did...
- Get into the CWM recovery
- Wipe Data/factory reset
- Wipe Cache
- Wipe Dalvik-Cache
Hope it works also to you...
Click to expand...
Click to collapse
basse10000 said:
I solved it by flashing a later official firmware - XXALF6.
Click to expand...
Click to collapse
Thanks, I'll try twice methods
Update: It's rare, but has returned to work normal and I doing nothing
Hello,
i found a solution for that problem. You will lose some sd card files.
go to settings-storage-others (or other) and mark all files. Then delete them an go to downloadmode to reflash you firmware. Reboot and the problem is missing.
i recently rooted my phone and flashed clockwork and was running beastmode kernal on stock rom.everything was working ok i used to get little glitches here and there so i tried to restore my phone back to factory.i entered the recovery mode and wipe date/factory reset and then went on to restore the backup.everything went smooth until i reboot the phone and now the phone is stuck in the droid(eye logo) and wont past that at all and just glitches and freezes on that screen.my friend has tried to fix it but there is no communication between the phone and the computer(usb debugging must have been disabled when i wipe data/factory reset and i basically cant do anything to fix it.is there a way around this to where i can just reset the phone to factory or install a rom or something
nathan101 said:
i recently rooted my phone and flashed clockwork and was running beastmode kernal on stock rom.everything was working ok i used to get little glitches here and there so i tried to restore my phone back to factory.i entered the recovery mode and wipe date/factory reset and then went on to restore the backup.everything went smooth until i reboot the phone and now the phone is stuck in the droid(eye logo) and wont past that at all and just glitches and freezes on that screen.my friend has tried to fix it but there is no communication between the phone and the computer(usb debugging must have been disabled when i wipe data/factory reset and i basically cant do anything to fix it.is there a way around this to where i can just reset the phone to factory or install a rom or something
Click to expand...
Click to collapse
Your phone is not bricked. When the phone is stuck on the droid eye, hold the power button and the volume down key at the same time until it reboots. This will get you into bootloader mode. Press the volume down key to highlight recovery and press the power button to enter it. Once you're in recovery go ahead and restore a backup or reflash something new. Either way make sure to do a full wipe.
Sent from my HTC6435LVW using xda app-developers app
klarson said:
Your phone is not bricked. When the phone is stuck on the droid eye, hold the power button and the volume down key at the same time until it reboots. This will get you into bootloader mode. Press the volume down key to highlight recovery and press the power button to enter it. Once you're in recovery go ahead and restore a backup or reflash something new. Either way make sure to do a full wipe.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
thats what i did i restored my backup and this is what happens. and i cannot push any files over to the phone because usb debugging is not enabled so there is no communication between the phone and computer at all
boot into recovery then use "adb push <path to rom> /mnt/sdcard/" to put a rom on the sd then install. Make sure you use a boot.img that came with the rom if it has one as it may cause problems if you don't.
Edit: you will need another rom for this and I would recommend reflashing a boot.img
Jmlannan said:
boot into recovery then use "adb push <path to rom> /mnt/sdcard/" to put a rom on the sd then install. Make sure you use a boot.img that came with the rom if it has one as it may cause problems if you don't.
Edit: you will need another rom for this and I would recommend reflashing a boot.img
Click to expand...
Click to collapse
the problem im having is the phone is not being recongnized by the adb so there for i can not push anything to the phone.i have no communication with the phone at all so i cant push any files at all.im looking for a way around this
nathan101 said:
i recently rooted my phone and flashed clockwork and was running beastmode kernal on stock rom.everything was working ok i used to get little glitches here and there so i tried to restore my phone back to factory.i entered the recovery mode and wipe date/factory reset and then went on to restore the backup.everything went smooth until i reboot the phone and now the phone is stuck in the droid(eye logo) and wont past that at all and just glitches and freezes on that screen.my friend has tried to fix it but there is no communication between the phone and the computer(usb debugging must have been disabled when i wipe data/factory reset and i basically cant do anything to fix it.is there a way around this to where i can just reset the phone to factory or install a rom or something
Click to expand...
Click to collapse
USB debugging has nothing to do with ADB in recovery, recovery basically has its own kernel and ADB is always enabled. Are you saying ADB doesn't work in recovery? If so, it is probably a driver problem with your computer. Also, some phones randomly get corrupt /data/ partitions (mine used to get them until I started using DSB's stock kernel with system write) and the only way to fix it is to do a factory reset or restore a backup. This might be what happened to you. If so just do a factory restore and see if it will boot.
Perhaps reflashing recovery? Worth a try if ur still having problems, also try installing then uninstalling htcs sync app.
nathan101 said:
i recently rooted my phone and flashed clockwork and was running beastmode kernal on stock rom.everything was working ok i used to get little glitches here and there so i tried to restore my phone back to factory.i entered the recovery mode and wipe date/factory reset and then went on to restore the backup.everything went smooth until i reboot the phone and now the phone is stuck in the droid(eye logo) and wont past that at all and just glitches and freezes on that screen.my friend has tried to fix it but there is no communication between the phone and the computer(usb debugging must have been disabled when i wipe data/factory reset and i basically cant do anything to fix it.is there a way around this to where i can just reset the phone to factory or install a rom or something
Click to expand...
Click to collapse
Try restoring back to stock with the Droid DNA RUU, i had issues with it locking up and freezing and i couldnt do a thing with it. i stumbled on the RUU and followed the instructions and re-stocked it. then just root and flash again. worked for me and im now running the Battery Plus ROM and have no issues yet. good luck
Just be sure to re lock before you flash the ruu
Sent from my HTC6435LVW using xda premium
Hey,
So I updated my Nexus 9 with today's OTA, after which I'm greeted with the dead android 'No command.'.
I've attempted to wipe the cache data and factory reset from the recovery menu, and factory reset from the power + volume down menu.
My boot-loader is locked as I've never felt the need of rooting or running custom roms - so the tablet is entirely stock.
I also attempted to run fastboot which is throwing errors due to the boot-loader being locked.
I tried to re-apply the patch using adb from the recovery menu, however after the patch is verified I'm receiving this error: system partition has unexpected contents
Is there anything I can do to fix this myself at this point?
I've contacted Google but haven't heard back from them yet.
Any help is greatly appreciated or guidance!
Kind Regards,
Cellzor said:
Hey,
So I updated my Nexus 9 with today's OTA, after which I'm greeted with the dead android 'No command.'.
I've attempted to wipe the cache data and factory reset from the recovery menu, and factory reset from the power + volume down menu.
My boot-loader is locked as I've never felt the need of rooting or running custom roms - so the tablet is entirely stock.
I also attempted to run fastboot which is throwing errors due to the boot-loader being locked.
I tried to re-apply the patch using adb from the recovery menu, however after the patch is verified I'm receiving this error: system partition has unexpected contents
Is there anything I can do to fix this myself at this point?
I've contacted Google but haven't heard back from them yet.
Any help is greatly appreciated or guidance!
Kind Regards,
Click to expand...
Click to collapse
You can try:
fastboot format cache
fastboot format userdata
(note that IF this is successful, it will wipe your SDcard)
If this doesn't work, you are out of options. The only thing you can do is return it for repair/replacement.
Thanks for the reply, those commands worked fine but I'm still stuck in the boot loop
I had the exact same issue, I just logged a ticket online at HTC and they sent me a free returns label. (This is the second time it's been in, first time was for dodgy power/volume buttons)
Hi there
I'm totally happy with this device but had an issue today for no apparent reason.
I was using it normally, I put it in my pocket (80% battery) and when I took it out, it was stuck on MI logo screen. Maybe screen wasn't properly blocked or something. But I find all the situation quite shocking since I normally set manual updates for system, and apps, playstore, etc.
I haven't done any flashing opperation recently since I'm not much into this kind of things nor installed any new app recenlty. However the phone was rooted (previos bootloader unlocking) quite a while ago by using "magisk method keeping stock recovery for OTA".
The phone is permanently on with MI logo on screen. I tried using power off button for a long time to see if I could turn it off but it didn't work.
I have access to Fast Boot and to Stock Recovery (3.0).
Is there any way to enter the system again without losing all data? If not, can I recover data before "flashing" anything or before using "wipe all data" option in recovery mode?
Thank you for any possible answer.
Reinstall twrp and boot into twrp from Command Window and Flash Lazy flasher you'll be booted into Your phone
notoriouslion said:
Reinstall twrp and boot into twrp from Command Window and Flash Lazy flasher you'll be booted into Your phone
Click to expand...
Click to collapse
Thanks a lot mate, with this small guidance and not much idea about this things I flashed lazyflasher, wiped cache and dalvik (couldn't with stock recovery) and reboot into system.
Just out of curiosity, by flashing this lazyflasher have I done permanent changes on the system, or just through the first immediate boot they disappear?
What do you think could cause a bootlop if not an update? May an app installed a while ago causing something like this?
xdaforo said:
Thanks a lot mate, with this small guidance and not much idea about this things I flashed lazyflasher, wiped cache and dalvik (couldn't with stock recovery) and reboot into system.
Just out of curiosity, by flashing this lazyflasher have I done permanent changes on the system, or just through the first immediate boot they disappear?
What do you think could cause a bootlop if not an update? May an app installed a while ago causing something like this?
Click to expand...
Click to collapse
It happens sometimes for Unknown reasons and Lazyflasher will not harm your device and I would suggest you to flash Another Rom
xdaforo said:
Thanks a lot mate, with this small guidance and not much idea about this things I flashed lazyflasher, wiped cache and dalvik (couldn't with stock recovery) and reboot into system.
Just out of curiosity, by flashing this lazyflasher have I done permanent changes on the system, or just through the first immediate boot they disappear?
What do you think could cause a bootlop if not an update? May an app installed a while ago causing something like this?
Click to expand...
Click to collapse
Did you run any root apps ? If /system changes you need Lazyflasher I think. You could alternatively reflash the ROM (without wiping data)