[Q] OTA Update caused phone to not boot - Desire Q&A, Help & Troubleshooting

Hi,
I know next to nothing about phones (although am OK when it comes to computers). I've an HTC Desire which I've had a couple of months which I've not touched the operating system on. I received an OTA update yesterday which I duely installed. The phone has been unable to boot since.
From reading around I've discovered that there's a recovery mode which installs a file update.zip from the SD card. I'm assuming this is what's corrupted on the phone (as it won't boot by installing this file either).
HTC have been no help, neither have O2 in the UK. They all seem to think wiping the data is the only solution and if I try anything on my own I'm going to invalidate the warranty. I can't see how installed a working official update file will invalidate anything, but I'd just like a copy of the file to try.
Does anyone have any ideas on how to fix the phone without having to do a hard reset?
Thanks.

Before the update were you getting an o2 logo when booting up the phone? If so, download the file at the bottom of this post and then:
1. Turn the phone on holding the back button to get into FASTBOOT
2. Connect phone to the PC
3. Once drivers are installed run the file
It should get you back to stock BUT it will mean losing all data on the phone
File to download:
http://ship.ibeta.org/shipped/Bravo...00.32U_5.09.05.30_2_release_144166_signed.exe

Yes, I still get the O2 logo when I try to boot (it just gets stuck at the logo). The phone is still stock, I've never tried to mess with it before, it's just had an automatic update installed which corrupted it.
Is there any way to get the phone to work WITHOUT losing the data on the phone?
Otherwise I'll try that file (or follow the hard reset instructions).
I'm currently becoming a quick study of all things phone operating systems.

Unfortunately not

EddyOS said:
Unfortunately not
Click to expand...
Click to collapse
Would not an update.zip from another phone be able to fix the problem?
Or is there a way of getting the data off a phone stuck at the boot screen?
I'm beginning to feel that the old expression about microsoft building bridges might be better applied to phones. I can normally fix my computer when things go wrong and not lose the data if I do need to rebuild.

The ONLY way you can get it working is to wipe the cache - which you can't do with a stock ROM. All you can do is either wipe the data as it is or install the RUU

Surely there must be a way to wipe the cache without wiping the data?
Is there a way of getting a working recovery file onto the SD card and getting the phone to boot off that? I'm assuming that won't mean I lose all the data.

As I've already said, there's no way of doing it. You're going to have to lose your data unless you root first, back it up then wipe but to restore you'd have to root again
If there was a way of doing it I think I'd have posted it by now

Related

In need of depsperate help!!!

Try to flash to JH2 (and repartition 512) - the stock B model firmware.
If it fails - try to push one of complete roms (doc_kalpik) and install it using clockwork.
Otherwise have no idea what is wrong.
.....
I will download the firmware files now,
any instructions on how to use clockwork? and install the complete rom?
Did you perform a repartition when you reflashed ?
ignore me wrong thread!
inshadesofgrey said:
I will download the firmware files now,
any instructions on how to use clockwork? and install the complete rom?
Click to expand...
Click to collapse
isnt there a install guide in doc-kaplik topic? In clockwork (might need to push update.zip and rom manually - dont remember how) choose install zip from sdcard and navigate to file you need.
i did......still didnt work
Sounds like what mine was doing when the internal SD died.
dupel said:
isnt there a install guide in doc-kaplik topic? In clockwork (might need to push update.zip and rom manually - dont remember how) choose install zip from sdcard and navigate to file you need.
Click to expand...
Click to collapse
will this work even if i didnt have clockwork on my phone?
I flashed the stock JH2 with 512.pit and reparition checked, but the phone goes to the samsung logo, and flash animation and to a blank screen with only the buttons lit up........ah, am losing all hopes really fast.
Now that you are on jh2 take out sim leave external sd inside charge it til full, turn on while and it will boot, saying no memory going internal or external.
So far that would be doa, unless someone found a way to fix or reformat external card but most people that sent it for repair with these symptoms had done doa exchange like me twice or samsung replaced external module meaning it was hardware issue. Sorry.
Sent from my i9000M
it's a long shot, but can I buy an external SD card and run android from there?
I am guessing the only hope is to buy a new phone then?
inshadesofgrey said:
Hi guys, I have been a silent observer of XDA for a while now and you guys have helped through the past 4-5 phones that I've had - but now, I am stuck, so I thought I'll ask for help.
I have a galaxy S (i90000-GT) - originally from Bell, Canada but unlocked. I was running the XJPH with lag-fix and two days ago, when the phone rebooted, it got stuck in a boot loop, samsung logo with black screen comes on, and it starts all over again. Now, I can get into download mode and I followed the process to install JM8, and the stock file (the US Vibrant stock file) and I tried this as well:howto-froyo-fw-i9000xxjpm-upgrade-via-odin-root-recovery-2e-lagfix/[
But to no avail. The boot loop is still there. With JM8, the phone boots up and the goes beyond the flash samsung logo (with the music) but loads to a black screen, with the lights on.
Am really frustrated as this is my only work phone (and I go back to work tomorrow). Without the phone, I am pretty much screwed. I dont care about the Data on the phone (have performed 3-4 data wipes during installing the above mentioned roms) . So anything you can advise, will help!
any ideas?
Click to expand...
Click to collapse
Have you wiped your data/factory reset & wiped your cache? Many phones get stuck at startup because of them.

[Q] Please help - Desire very poorly.

Hi. I hope someone can help.
I've been using my desire rooted and S-OFFed running Defrost for sometime, all has been fine. Was playing Angry birds yesterday and the phone froze.
Pulled the battery and rebooted, carried on playing. Froze again.
Pull the battery again but phone stuck on the first splash screen. Fiddled a bit, couldn't get into recovery. So I left the phone on charge until the light went green, then removed the battery and left it overnight.
This morning I put the battery in and switched it on. It booted fine, but froze when I tried to unlock it.
I've tried pulling the battery again and again. I can get into HBOOT, but the phone isn't recognised for ADB or fastboot commands via USB. It often freezes even in fastboot mode.
I tried to do a clear storage, but that froze as well. Although a subsequent attempt appeared to work but the phone still won't boot normally.
So I can't reflash or do anything else. HAs anyone actually sent a phone back for repair with custom firmware/splash screen installed, as I don't think I'm going to be able to revert it to stock.
I've tried numerous restarts with and without a sim and an sd card inserted. Not sure what else to try.
Any help greatly appreciated.
did you wipe the dalvik cache through recovery?
try this if you can.
No I haven't wiped the dalvik cache. I have managed to get in to recovery on a couple of occasions. But the phone has frozen again navigating the menu.
I will try that if I get into recovery again though.
Thanks
Quick update.
After leaving the battery out for a couple of hours. I tried again and the phone started to boot. It got to the splash animation and the wipe had obviously worked because it was the DeFrost default of the X. This then looped a few times then froze.
I pulled the battery and managed to get in to Clockwork Mod recovery and did a wipe from there, which appeared to work, but then it rebooted by itself and I still didn't manage to do a dalvik wipe.
Now I'm back to the same point again. I can't get into recovery.
I guess I'll try again after leaving the battery out for a while.
One thing I did notice when in recovery was that the trackpad didn't work. I had to use vol and power keys. If I get into recovery again, I'll try a keytest if I get into recovery again.
And another update.
I got into recovery again and did a wipe dalvik cache.
I got the following error.
E:Can't mount /dev/block/mmcblk0p2
(No such file or directory)
Dalvik cache wiped.
So I'm not sure if it actually did it or not.
I then tried to do a nandroid restore and got a similar error.
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E:Can't mount /sdcard
Then the phone froze again.
So I'm guessing something is corrupted here.
Should I try formatting the SD card. (I have backed up all the data I could using my PC).
i think your dalvik will have been wiped. i always get the same message.
have you tried it again but without trying to restore a nand?
Yes, I tried it again. I only seem to be able to get in to recovery after leaving the battery out for a while.
This time I did a dalvik wipe then rebooted, but it's just stuck on the initial splash screen again.
I'm pulling my hair out here (what little I have)
have you considered going back to a stock rom using an RUU or PB99IMG?
then you'd have to root again and restore your nand if possible/needed.
I'd be happy to try reverting to stock, but don't you need to get the phone to boot before you can do that?
I have sent this phone back for repair previously and done just that (it suffered from the overheating problem and had a whole new motherboard less than months ago).
After leaving the battery out again for a while, a normal switch on got to the animation splash then rebooted twice before freezing again.
Is this likely to be a corruption in the flash memory, or a hardware problem?
Hello,
I've got exactly the same problem! The phone freezes on the first splash-screen (not the Rom's bootanimation) and I can't get into recovery.
I'm running Oxygen Rom (2.0-RC6) and using Apps2SD in combination with an 8GB Transcend microSD card. I've only "rooted" it once using Unrevoked (long time ago), so I assume it is still S-On. I'm using clockwork's recovery, too.
At the moment I really don't know what to do.
What could I try?
pc99mk:
At the moment I'm leaving the battery out the phone until afternoon, hoping to get into recovery
Thank you in advance for every bit of an answer
Read up on the PB99IMG process if you can get into recovery (power & vol down).
Otherwise, the RUU will work if you can boot into fastboot (power & back key).
Sent from my HTC Desire using Tapatalk
Hi spadoleo.
Sorry to hear you're having similar troubles.
I'm sure mine must have some sort of hardware problem now.
After leaving the battery out for a while again last night, I managed to get into fastboot and flash the latest alpharev hboot, and clockworkmod 3.0.0.5 in the hope that my freezing problems there were due to a slight corruption.
Clockworkmod has definitely updated as the colour of the menu has changed, but it still freezes soon after entering.
I just want to try and get the phone looking as much like a stock phone prior to sending it back now.
Does anyone have a fasstboot flashable image of the following:
UK TMobile 'Pink Circle' splash1 image
Standard HBOOT
Standard recovery
Otherwise I'm just going to have to send it back to HTC as is, and hope they still fix it under warranty.
Or is there any way of getting a RUU to start doing anything with the phone in fastboot?
Or indeed anything else I can try?
See my post above.
You can run an RUU in fastboot.
Sent from my HTC Desire using Tapatalk
Hi mikep99.
Ok thanks for the advice. I'll have a read of the pb99img stuff.
I tried the RUU this morning in fastboot mode, but every time it justs sits at the 'Verifying information on your Android phone' for a while, then times out with a USB connection error.
I seem to have best results after leaving the battery out for a while (no idea why that should make any difference but it does), so I'll try it again in an hour or so.
Cheers
Install htc sync if you haven't already.
And try turning off antivirus and firewall on your PC
HTH
Sent from my HTC Desire using Tapatalk
Ok. I read up on the PB99IMG process.
I found a PB99IMG.zip file posted by Teppic74 which is a stock Froyo.
I copied it to the root of my goldcard and booted the phone.
It loaded the file and came up with
Incorrect CID error
update fail
I then kicked myself. I created the gold card to revert the phone to stock before sending it to HTC previously.
They replaced the motherboard. Would this have changed my CID?
I then thought 'no problem I'll just go through the gold card creation process again'
But although I can do stuff on the phone in fastboot mode, adb doesn't work in that mode. So trying adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid
just gives an error.
So if my CID has changed, any idea how I can create a gold card with the phone in this state. Should adb only work when the phone is booted, or should it work in hboot or fastboot?
i'm not sure which PB99IMG you're trying to flash but i'd use this (if its not the same):
http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_159811_signed.zip
with regards to the goldcard, have you mounted the sdcard when in recovery? and then running
cat /sys/class/mmc_host/mmc1/mmc1:*/cid
again?
if that doesn't work, you can use another TMobile Desire to create it.
therefore, i don't think the mbo change should affect your goldcard????
EDIT - when you got your phone back from repair, was it completely wiped? Tmobile may have wiped/swapped etc.. the goldcard you previously made.
I think it was that image that I used. But I'll download it again just to be sure.
When the phone was repaired before, I sent to HTC directly and I didn't send any sd card or battery. So it should still be as it was.
So if the CID isn't motherboard specific it should still work.
Is there any way to check whether it is still a goldcard? I may have formatted it again (don't recall).
Although thinking about it, I still have the image file emailed to me when I created the gold card originally, so I could just reapply it and try again.
I'm out tonight, but will try a few things and post back with my results.
Thanks for your help so far.
Another update and things have moved forward.
It turned out I'd trashed my gold card, but I did still have the image file so I recreated it.
I then booted the phone again and it loaded the PB99IMP.zip file.
It then asked me if I wanted to perform the update. I said yes, and it updated the bootloader and rebooted. Then it froze on Checking PB99IMP.zip....
After leaving it 10-15 minutes I pulled the battery again and left it for a while.
I tried again just now.
I can see that it has updated the HBOOT, so I'm no longer S-OFF.
Just now I thought it was going to work it got about halfway through updating the system partition before freezing.
If only it had updated the splash1 image before the system, I might've had the phone in a suitable state to return. But it still shows my custom splash1 screen when powering on normally - then it changes to the piccy with the green arrows.
I'll try it again later after leaving the battery out for a while.
But the fact it freezes in the middle of such an update suggests it's definitely a hardware problem of some sort.
If anyone has any other ideas I could try, please let me know. But once again thanks for all the help so far.
Sounds like you're getting somewhere
Just keep on trying every now and again.
Hopefully it'll go through...
Sent from my HTC Desire using Tapatalk

[Q] CM10 m2 Encryption Issue

Ok. I foolishly enabled encryption on my i711 and after putting in the password, the volumes unlock and the system starts. The problem is that if the screen goes off for any reason, the phone reboots. Tried all sorts of things to correct and decided I no longer wanted the phone encrypted. There is no way back. Ok, so I thought I could do a factory reset... No dice. The phone reboots and all is still encrypted and there.
Next I tried clockworkmod but couldn't do ANYTHING there because the encrypted volumes aren't mountable. I couldn't factory reset, install a new rom, etc.
Next I went to ODIN and tried to repartition. No luck there either. I flashed clockworkmod again for good measure and even tried Nand Erase All.
After this I booted into the phone and tried to repartition... Now I have a phone that displays the lovely CM10 boot screen but never gets passed that. I can still get into recovery.
Any thoughts on how to undo the encryption and reflash a rom?
fza99 said:
Ok. I foolishly enabled encryption on my i711 and after putting in the password, the volumes unlock and the system starts. The problem is that if the screen goes off for any reason, the phone reboots. Tried all sorts of things to correct and decided I no longer wanted the phone encrypted. There is no way back. Ok, so I thought I could do a factory reset... No dice. The phone reboots and all is still encrypted and there.
Next I tried clockworkmod but couldn't do ANYTHING there because the encrypted volumes aren't mountable. I couldn't factory reset, install a new rom, etc.
Next I went to ODIN and tried to repartition. No luck there either. I flashed clockworkmod again for good measure and even tried Nand Erase All.
After this I booted into the phone and tried to repartition... Now I have a phone that displays the lovely CM10 boot screen but never gets passed that. I can still get into recovery.
Any thoughts on how to undo the encryption and reflash a rom?
Click to expand...
Click to collapse
I have some very bad news for you.... Encryption is a one way street. Once encrypted the only way back is to flash stock via fastboot.
I can't even start to explain how to use fastboot as I have never been in a situation where I have needed it.
recoveries lose all access on encrypted devices so this is the only way.
Here is some links to get you started... Please do research before you begin the process and make sure you've obtained the appropriate files. I will take no responsibility for bricking your device.
Flashing via Fastboot:
http://forum.xda-developers.com/wik...id#Android_Flashing_Guide_.28with_fastboot.29
Installing Fastboot on Windows:
http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
Sent from my SGH-I747 using xda app-developers app

[help] [oneplus3] [stuck in boot logo] [softbricked] cannot boot into system [solved]

Hey boss., after flashing open beta 12, the phone started hanging now and then. I tried to contact oneplus forums and they asked me to send the log files. Since they took too long to respond, I went to oneplus service centre. They flashed my phone with old oxygen os and the phone didn't start. It went into bootloop
Then I asked them, they said motherboard is corrupted. I left the place and I requested online customer support from oneplus. They too flshed and concluded the same. Can I know whether flashing/sideloading openbeta created this issue? If so, can you provide me support to avail the warranty on the phone? or recover it via any other method or process?
Please respond as soon as possible. My communication with the world has become limited after this issue. I hope there is some sort of support.
Also note that, the phone can boot into fastboot mode, but bootloader is locked. It can boot into recovery. I tried wiping everything, but the phone is not rebooting.
When I start the phone, it stucks in the boot logo and after a while, the screen becomes blank and a white color notification LED is glowing.
Kindly help me.
i had the same issue last week after updating to 13..and i tried to flash the black theme..it went black..i had nothing....it was like it was bricked... here's how after many failed attempt's..i had to clean out all files including backups.wipe data i had to wipe system i had to clean out all previous files.from TWRP recovery.then i had to download the latest software release then put the zip file in my phone storage not in the download file ..then i had to flash stock recovery.then install the new system..and i made the mistake of trying to use some of my app backups like for one estrong file ..all of them were corrupt.so start fresh.
You might try this unbricking method:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Though your device isn't hard-bricked, this would reset your device to the absolute factory settings (watch out, your data will be erased) on an older OxygenOS version.
I would recommend the 2nd Method, as it restores all partitions to factory settings.
I might also know where your issue came from:
Though you can flash the Open Beta (or any other ZIP from OnePlus) through the Stock Recovery, OnePlus states that you need to be on an unlocked bootloader for not bricking your device.
TimSchumi said:
You might try this unbricking method:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Though your device isn't hard-bricked, this would reset your device to the absolute factory settings (watch out, your data will be erased) on an older OxygenOS version.
I would recommend the 2nd Method, as it restores all partitions to factory settings.
I might also know where your issue came from:
Though you can flash the Open Beta (or any other ZIP from OnePlus) through the Stock Recovery, OnePlus states that you need to be on an unlocked bootloader for not bricking your device.
Click to expand...
Click to collapse
It worked, but no network connection or wifi connection!
Is there a way to bring them back?
SivaMaxwell said:
It worked, but no network connection or wifi connection!
Is there a way to bring them back?
Click to expand...
Click to collapse
You might try to unlock your bootloader (There are giudes to do this) and flash a OxygenOS package from oneplus.net through the stock recovery, to ensure the firmware is OK (Do a factory reset from recovery!). I don't know if the Unbrick Tool only restores corrupted partitions or all. It might have installed the wrong system over your previously installed firmware if only corrupted partitions are restored. Keep the bootloader unlocked to be on the safe side (After some time you will be able to just ignore the boot message and you have better access to fastboot and recovery)!
Also, GG to OnePlus for (fake) Motherboard corruption!
About warranty:
Warranty should be ok as long as you won't do hardware modifications (I think).
Bootloader unlocking is definitely safe
TimSchumi said:
You might try to unlock your bootloader (There are giudes to do this) and flash a OxygenOS package from oneplus.net through the stock recovery, to ensure the firmware is OK (Do a factory reset from recovery!). I don't know if the Unbrick Tool only restores corrupted partitions or all. It might have installed the wrong system over your previously installed firmware if only corrupted partitions are restored. Keep the bootloader unlocked to be on the safe side (After some time you will be able to just ignore the boot message and you have better access to fastboot and recovery)!
Also, GG to OnePlus for (fake) Motherboard corruption!
About warranty:
Warranty should be ok as long as you won't do hardware modifications (I think).
Bootloader unlocking is definitely safe
Click to expand...
Click to collapse
I tried to update to recent oxygen os. Then the original proble started again.
It is not booting up, again..
SivaMaxwell said:
I tried to update to recent oxygen os. Then the original proble started again.
It is not booting up, again..
Click to expand...
Click to collapse
No, reflash the OxygenOS package of the same Version that is installed by the Unbrick Tool (If you can still get itfrom oneplus.net) and then check if Network does work. Also, check your IMEI.
I think you might have a corrupted EFS partition. That's y you don't have a working network. Check whether your device show a IMEI under about phone.
m4manusraj said:
I think you might have a corrupted EFS partition. That's y you don't have a working network. Check whether your device show a IMEI under about phone.
Click to expand...
Click to collapse
EFS doesn't have an effect on WiFi.
That's why I think that it is a firmware issue
I think, I have solved it guys. I'll let you know once completely under control
So, Thank you very much for your support. With this little support from you and my previous Foresightedness helped me restore the phone.
So just in case if any one else faces the same or similar problem, this is the process:
STEP0: If there is any partition corrupted, the device don't boot properly. And, The customer care/ sevice centre guys state it as motherboard problem. Donot Panic. Always take TWRP backup whenever you change your ROM. This Backup helps you to restore whenever you're in trouble. In this particular case, ESF backup is required. So, take a complete backup (everything) in TWRP, it saves your ass.. keep the backup in your PC or any safe Storage (the complete TWRP Folder which is in Internal Memory) before flashing any custom ROM.
Step1: Follow method2 in this guide: https://forums.oneplus.net/threads/g...plus-3.452634/
Step2: if everything is alright, its done. Otherwise, The device boots up with some missing features and details. At this time, you have to unlock the bootloader. See The forum to know how to do it. Basic searching can give you the method.
If you can transfer the TWRP folder from PC to Phone, it's good. But the phone boots itself because of missing firmware. Even Bluetooth couldn;'t be used.
In my particular case, I couldnot copy from PC to mobile or viceversa. So, you cannot copy back your TWRP folder in this situation.
So, Unlock bootloader. Then reboot to system (without doing anything)
Step3: Reboot to bootloader and flash TWRP 3-0.2 version only. otherwise device will be encrypted.
Step4: download Ressurection Remix ROM version : ResurrectionRemix-M-v5.7.4-20161113-PUBLIC-ex-oneplus3 or you can experiment with any other custom ROM but only android 6 (*Marshmallow). Also make sure that you have universal adb drivers. install them if not (search in the forums.)
Step5: goto TWRP recovery, in this, goto wipe option. Drag the swipe to wipe button here. (normal wipe).
Step6: Now, in advanced options, select adb sideload option and select the two wipes in the next menu. Start ADB sideload in the TWRP.
Step7: Now, Start the adb sideloading the custom ROM from your PC. You donot Require Gapps for transferring a file. So donot flash Gapps.
Step8: After the sideload is complete, reboot into system. Now you can transfer files between phone and PC. Now, Copy the Complete TWRP folder into the internal memory. A pop-up asks for merging the folders. Allow the merging, even if you have another TWRP backup there. They don't overlap.
Step9: Now, Boot into TWRP and restore completely. The phone boots up properly, this time. Everything works as expected. every mysterious problem is solved. Now you will get update request if you are on previous version of OOS.
Last but not Least: Please do not use any app recovery tools. they may cause issues while following the above steps
Thank to every XDA member, helping us save the time and money we spend at service center.
m4manusraj said:
I think you might have a corrupted EFS partition. That's y you don't have a working network. Check whether your device show a IMEI under about phone.
Click to expand...
Click to collapse
TimSchumi said:
EFS doesn't have an effect on WiFi.
That's why I think that it is a firmware issue
Click to expand...
Click to collapse
Yes, boss. The EFS is corrupted. But, thanks to TWRP, it also has the option to backup EFS, modem. SO, I used my old backup from Jan2017 to restore it back.
But, TO place TWRP back in phone, the original OOS3.1.2, even after reflashing didn't support. I thought for a while and flashed the All loved RR (MM) . THen, it gave me the scope to t/f the folder to internal memory.
Now, I restored the EFS , Modem, sytem with data. and hell yea!! the phone is back to life.
Complete Backup, Atleast once for 3 months saves your ass..
I am glad it helped. That's the power of Xda.
My OP3 is stuck on the boot animation only while booting up Oxygen OS. At first I thought it was bricked but as I proceeded I found out that it isn't and i'm able to boot other OS on it. I've had Resurrection Remix which I had no problems flashing whatsoever. But I'm having this problem with Oxygen OS. Has anyone experienced this? What do I do? Please help.

S20 Ultra exynos stock OS stuck in boot loop. Data recovery?

Hi Guys,
As the title says my S20 Ultra has managed to get itself stuck in a boot loop as of last night. I can boot into recovery mode, download mode and safe mode. When booted into safe mode it will stay on the home screen fine. However if i try to unlock the phone to use it, it crashes and reboots into a bootloop.
If I just plug in a usb to access the files via usb in safe mode before the phone is unlocked the phone is not detected (device manager detects a samsung device but nothing in file explorer most likely because the usb services haven't started up yet and won't until the phone is unlocked).
Im sure a factory reset will solve the bootloop issue but I don't want to lose the date on the phone until it's backed up (recently renovated our house and I have pictures on there of before and afters I would like to keep).
Is there a method I could use to get the data back other then sending the phone off to a recovery service? Maybe something that doesn't void the warranty of the phone but if there is no other choice I would consider voiding the warranty. I used to install custom roms on all my old android phones but never felt the need to on this one. I'm fairly tech savvy so am Just looking for ideas.
Cheers
Coddeh said:
Hi Guys,
As the title says my S20 Ultra has managed to get itself stuck in a boot loop as of last night. I can boot into recovery mode, download mode and safe mode. When booted into safe mode it will stay on the home screen fine. However if i try to unlock the phone to use it, it crashes and reboots into a bootloop.
If I just plug in a usb to access the files via usb in safe mode before the phone is unlocked the phone is not detected (device manager detects a samsung device but nothing in file explorer most likely because the usb services haven't started up yet and won't until the phone is unlocked).
Im sure a factory reset will solve the bootloop issue but I don't want to lose the date on the phone until it's backed up (recently renovated our house and I have pictures on there of before and afters I would like to keep).
Is there a method I could use to get the data back other then sending the phone off to a recovery service? Maybe something that doesn't void the warranty of the phone but if there is no other choice I would consider voiding the warranty. I used to install custom roms on all my old android phones but never felt the need to on this one. I'm fairly tech savvy so am Just looking for ideas.
Cheers
Click to expand...
Click to collapse
Try flashing the same firmware you're currently running using Odin and HOME_CSC to keep your data, possible it will replace and fix the corrupted files causing the bootloop
So last night I tried what you have mentioned. It didn't change anything unfortunately.
I then thought it might be worth trying an older firmware. I tried rolling back to the previous firmware and then to android 10. Both of these ended up making things worse and it would boot loop at the android startup screen.
Luckily I managed to get back into Odin mode and put the current firmware back on and I'm now back to square one.
OK so I have had a thought. I've seen that some people have managed to establish a USB connection to thier device through TWRP and managed to backup their data through that. I've also seen that on older phones you can use odin to only flash TWRP and then boot into it. I'm not sure if things have changed drastically and you are unable to do that on the S20 ultra now. After my data (pictures and videos) was backed up I could then reflash the recovery back to stock and do a factory reset to fix the bootloop.
Does this seem plausible?

Categories

Resources