Related
Hi iv got a HTC ONE S, it is stuck on boot loop is there any way i can get my pictures and data off my phone? thanks
Can you get into the recovery? And are you running a custom recovery?
If you can get into your recovery(cwm or twrp) you can plug it into usb and mount it as usb storage.
If I helped in any way please hit thanks
Just fix the bootloop. Sounds like you gave up on it. Can you get into the bootloader? Hold volume down and power. Till the device shuts off. Then redo that method and poof. Hboot. If you can. What hboot version are you on?
Sent from my HTC One S using xda app-developers app
I have the same problem, phone keep reboot and will not turn on, i can get into recovery, but can not get contact via USB, what am i doing wrong?
Any step by step how to get out pictures before setting it back to factory settings
recovery loop
Just rooted HTC One S TMOUS using Hasoon 2000's tool. tried CWM backup of rooted stock, then followed instructions for PA 2.52 + gapps. Got stuck on PA boot screen. Won't boot all way up.
Phone will only boot into recovery. adb reboot bootloader goes into recovery. can't get into hboot to restore stock using RUU.
Advice?
Thanks kindly.
Same Problem here.
I wanted to join a wifi-network, then the htc freezed and now it's in bootloop.
I still read some oder threads in the internet but not realy good ideas I like.
Does anyone know whats happening in HBoot when I use "Clear Storage"? Does he clear the phone-memory or the SD-Memory? Or anything else?
Bond246 said:
Same Problem here.
I wanted to join a wifi-network, then the htc freezed and now it's in bootloop.
I still read some oder threads in the internet but not realy good ideas I like.
Does anyone know whats happening in HBoot when I use "Clear Storage"? Does he clear the phone-memory or the SD-Memory? Or anything else?
Click to expand...
Click to collapse
did anyone solve this? I have an unbranded unrooted HTC One S that is also stuck in a bootloop. I was just scanning the WIFI networks from settings and then the phone started looping by itself and only stopped after the battery was empty.
The phone is not modified in any way. I can get into hboot with power-volume down but then what? I don't really feel like doing a factory reset. Is there any other way out? Does the factory reset help?
Hi
I had the same problem and fixed it.
I made factory reset, then when i configured my Google account i disables the "sync Internet" Option.
Sent from my HTC One S using xda app-developers app
gingi007 said:
Hi
I had the same problem and fixed it.
I made factory reset, then when i configured my Google account i disables the "sync Internet" Option.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Ya seen someone say that not sure if it was you but also some people have found having to many saved hotspots can also send you into a bootloop.
in my case for sure it was the google account cause i did factory reset, and had no saved hotspots and still it happened when i switched the wifi on\off after the factory reset(i mead got into boot-loop and needed a factory reset).
it is a serious bug\problem - i can't believe this can happen because of such a silly configuration.
the OS of HTC is not stabled at all!
If your bootloader is locked, then you dont have too many options re getting information off of your phone. Someone else may be able to post ideas. A factory reset may be your only option..
If you have already unlocked your bootloader, my suggestion would be to flash the latest TWRP Custom Recovery (google it). You can connect to your computer via usb through TWRP and access your sd card to get pictures, videos etc off of it.
Through TWRP you can also have access to adb.exe (ie using adb.exe commands and not just fastboot.exe commands, and thereby access all sorts of adb related commands (backups, linux shell, etc).
In order to actually fix the bootloop, well, usualy I find this is due to issues with the Kernel and custom ROM you are flashing (either one or the other), and so would reflash whatever worked before (ie a previous ROM or previous kernel).
But if this is all happening on a device you have not rooted nor flashed anything custom... Well, then that is a good question!
AKToronto
gingi007 said:
in my case for sure it was the google account cause i did factory reset, and had no saved hotspots and still it happened when i switched the wifi on\off after the factory reset(i mead got into boot-loop and needed a factory reset).
it is a serious bug\problem - i can't believe this can happen because of such a silly configuration.
the OS of HTC is not stabled at all!
Click to expand...
Click to collapse
Ya I'm not saying what you said is wrong or didn't work for you but I do think I could be right about kongo09 and Bond246 issue since it did happen when dealing with wifi and seen a few people say the same thing.
I am in a bootloop. What i did to get the phone start is just press first down volume button then power button (keep holding them until the phone goes oof). Inmediatily when the phone go off, stop pressing anything. ANYTHING, BE FAST, and it will boot normally. I am now tryying to get the stock recovery to avoid this sht.
gingi007 said:
Hi
I had the same problem and fixed it.
I made factory reset, then when i configured my Google account i disables the "sync Internet" Option.
Click to expand...
Click to collapse
Did the factory reset make you lose all your data? As in: pictures etc? I have read varying stories regarding this, some say you lose it all, some say you don't.
I have some recordings of interviews on there that I really(!!!) cannot lose. Does anyone know if HTC has the possibility to recover files from a phone in this condition?
jazzmijnhv said:
Did the factory reset make you lose all your data? As in: pictures etc? I have read varying stories regarding this, some say you lose it all, some say you don't.
I have some recordings of interviews on there that I really(!!!) cannot lose. Does anyone know if HTC has the possibility to recover files from a phone in this condition?
Click to expand...
Click to collapse
If you unlocked the bootloader then you could flash TWRP which will let you mount SD for the PC.
Darknites said:
If you unlocked the bootloader then you could flash TWRP which will let you mount SD for the PC.
Click to expand...
Click to collapse
Unfortunately not... Unrooted, stock bootloader and all... I spent all day reading threads on different forums, but so far it seems that there is no other solution to this bootloop problem than just doing a factory reset. But like I said, I have some very important recordings on my phone and before I give up on them I want to make sure I tried everything.
If anyone knows of a way to root and flash a new bootloader without wiping all my data in the process, that would be highly appreciated.
Or if anyone knows whether it is possible to somehow approach the storage (maybe through Linux) while the phone is bootlooping (not normally recognized by computer).
But also: I would very much like to hear from people who have done a factory reset from the stock boot loader: has it wiped just your apps and app data? Or has it wiped your files as well (photos, music, recordings etc)?
Like I said: any info would be much appreciated...
jazzmijnhv said:
Unfortunately not... Unrooted, stock bootloader and all... I spent all day reading threads on different forums, but so far it seems that there is no other solution to this bootloop problem than just doing a factory reset. But like I said, I have some very important recordings on my phone and before I give up on them I want to make sure I tried everything.
If anyone knows of a way to root and flash a new bootloader without wiping all my data in the process, that would be highly appreciated.
Or if anyone knows whether it is possible to somehow approach the storage (maybe through Linux) while the phone is bootlooping (not normally recognized by computer).
But also: I would very much like to hear from people who have done a factory reset from the stock boot loader: has it wiped just your apps and app data? Or has it wiped your files as well (photos, music, recordings etc)?
Like I said: any info would be much appreciated...
Click to expand...
Click to collapse
Not much you can do then because even unlocking could wipe SD.
Not sure if its possible with a locked bootloader but you may want to try getting into your bootloader then try typing fastboot boot <working kernel file>
Replace the phrase "<working kernel file>" with a stock boot.img that you know works.
As you can see this command is different from fastboot flash boot <working kernel file>.
This may get you out of the bootloop if you had kernel issues, and may allow you to load a kernel temporarily. Not sure if it works on locked bootloaders but it might.
If all you can access is the bootloader and fastboot, then you really have to play around with fastboot commands. See http://android-dls.com/wiki/index.php?title=Fastboot for the list.
Good luck!
jazzmijnhv said:
Unfortunately not... Unrooted, stock bootloader and all... I spent all day reading threads on different forums, but so far it seems that there is no other solution to this bootloop problem than just doing a factory reset. But like I said, I have some very important recordings on my phone and before I give up on them I want to make sure I tried everything.
If anyone knows of a way to root and flash a new bootloader without wiping all my data in the process, that would be highly appreciated.
Or if anyone knows whether it is possible to somehow approach the storage (maybe through Linux) while the phone is bootlooping (not normally recognized by computer).
But also: I would very much like to hear from people who have done a factory reset from the stock boot loader: has it wiped just your apps and app data? Or has it wiped your files as well (photos, music, recordings etc)?
Like I said: any info would be much appreciated...
Click to expand...
Click to collapse
Stock bootloader, same bootloop scenario - factory reset wiped everything including photos, music, other files. Clear storage seems to keep everything except the installed apps and configuration. It's the 4th time I'm doing it unfortunately :
Recently I unlocked bootloader, installed twrp and succesfully rooted my device, but while I was tinkering with my device I accidentally wipe all data, partition, etc in TWRP now I guess I wiped out everything including OS !!!
How can I restore ? Do I need to flash new hammerhead image ?
Right now I'm following this tutorial
http://forum.xda-developers.com/showthread.php?t=2513701
It'll be great if anyone of you can point me right way.
You can just flash any custom rom using this
http://forum.xda-developers.com/showthread.php?t=2575150
Or
Follow the thread you posted to restore a factory image..
But restoring a factory image will unroot your device..
You have twrp so the first thing you did was make a nandroid, right? Live and learn.
Thanks for the help, I just flashed new image. Everything works good except wifi, random drops + slow speed.
I contacted google for replacement and they send me RMA form. Unrooted the phone, bootlocker locked + flag reset.
Thanks for the help, I just flashed new image. Everything works good except wifi, random drops + slow speed.
I contacted google for replacement and they send me RMA form. Unrooted the phone, bootlocker locked + flag reset.
Huh? You're doing an RMA why?
sent from my hammerhead
albertpaulp said:
Thanks for the help, I just flashed new image. Everything works good except wifi, random drops + slow speed.
I contacted google for replacement and they send me RMA form. Unrooted the phone, bootlocker locked + flag reset.
Click to expand...
Click to collapse
Why are you rma'ing it. Was wifi messed up before you erased everything?
jd1639 said:
Why are you rma'ing it. Was wifi messed up before you erased everything?
Click to expand...
Click to collapse
Before rooting wifi problem was rarely occur now after rooting problem arise more frequently, now even after unrooting wifi is super slow sometimes not even connecting. I hate RMAing but seems like no other way.
http://forum.xda-developers.com/showthread.php?t=2586410
jd1639 said:
You have twrp so the first thing you did was make a nandroid, right? Live and learn.
Click to expand...
Click to collapse
Awesome advice. I made a nandroid of my N5 first thing after getting all my apps straight. Playing with flashing a rom in TWRP I did a manual "wipe data" which proceded to wipe out the entire SDCARD in the process including my nandroid. Sooooo.... Yes, make a nandroid but also back it up to your computer or dropbox right away.
albertpaulp said:
Before rooting wifi problem was rarely occur now after rooting problem arise more frequently, now even after unrooting wifi is super slow sometimes not even connecting. I hate RMAing but seems like no other way.
http://forum.xda-developers.com/showthread.php?t=2586410
Click to expand...
Click to collapse
Don't RMA it, there's nothing wrong with the hardware. All you have to do is reflash the factory image. If you didn't know what you were doing, you shouldn't have been messing around with your phone in the first place. Reflash your phone back to its factory state and next time do your homework before you start tinkering. People like you are going to cause Google to change their return policy so that returns are much more heavily scrutinized.
BirchBarlow said:
Don't RMA it, there's nothing wrong with the hardware. All you have to do is reflash the factory image. If you didn't know what you were doing, you shouldn't have been messing around with your phone in the first place. Reflash your phone back to its factory state and next time do your homework before you start tinkering. People like you are going to cause Google to change their return policy so that returns are much more heavily scrutinized.
Click to expand...
Click to collapse
Before rooting wifi problem was rarely occur now after rooting problem arise more frequently, now even after unrooting wifi is super slow sometimes not even connecting. I hate RMAing but seems like no other way.
Click to expand...
Click to collapse
You know how to read right ? also I did reflashed to stock image and unrooted + locked bootloader but problem persists, what do you propose I do now ? I started loving my phone now I'm getting new one, it's hard for me too, it's like adopting a son.
Hey there team. I've been a long time lurker here and might not have made many posts. Getting this phone and given my time flashing, rooting, and following guides here, I really want to start getting in on the conversations and discussions. Let me go through with what happened to my last LG Volt...
I had successfully rooted the device using towelroot and been playing around with the usual root access apps. I had superuser, busybox, etc. What I came across as a problem with the device was it's RAM usage on a lot of apps and the problem was largely just OS (after purging a lot of apps off the device). The biggest problem I was having was with Skype crashing and ending calls anytime you switched out of the Skype app itself.
Being the idiot I am, I began looking into possibly using SWAP memory to try to extend my RAM a little to see if I could correct what Skype was doing (assuming it was a RAM issue, which, now thinking about it, I don't think it was because my EVO V worked fine [On custom roms granted]). So I tried doing some swap stuff and it overall just would not go. I figured it was a KitKat issue involving the SD Card and how the file structure on the LG Volt seemed to handle SD related stuff, all going to emulated memory. So. I decided it wasn't worth the trouble and research anymore, and considering not too much work had been done on the Volt yet, I decided to give up that campaign and wait for more research to get done.
In the mean time, I told the phone to do a factory reset so I can start back fresh and go about using the device normally. This might have been where I made a mistake. I told the device to factory reset and format everything through the Android OS instead of booting into the stock recovery and telling it to do a factory reset. The phone shut off and never came back. I was not able to get it to charge, I could not enter LG Download Mode, I couldn't get into the recovery, absolutely nothing. Tried seeing if I could use the LG Mobile support tool to push anything to the phone since my computer could still see the phone connected... No luck.
So, my questions to the team here on XDA is:
1. What exactly happened to cause the phone to start the factory reset, but, lose everything? I could only assume that the phone kicked the system, data, boot, recovery, and... well.. everything off and fried it's memory. I assume it had to do with what I was trying to do with swap memory and something getting seriously messed up.
2. More specific on what the phone did after, it would not turn on, charge, go to recovery, or download mode. It was completely unresponsive. Would there have been a way to resurrect this phone back from the dead that I wasn't able to find after all the looking and research I had done?
3. With the new LG Volt I recieved from Virgin, how safe would you say things would be to go about rooting again and being more careful with my apps while I wait or get involved with some of the future ROM development for the device?
4. Is there something with how LGs recovery and download partitions are set up that would cause these to be unable to function? Or something that is particular to the LG Volt?
Finally, 5. I noticed that the work done and the team researching the Volt right now have managed to get an unlocked bootloader and a custom recovery that works. Would it be safe with the research done now to go about unlocking and flashing the custom recovery on?
These questions all take into account common knowledge stuff such as, the potentially to brick a phone again is always there and to continue doing as much research and reading as I can to know what I'm doing with the device accurately. Hope my questions can be answered here, until then, cheers gentlemen.
marth141 said:
Hey there team. I've been a long time lurker here and might not have made many posts. Getting this phone and given my time flashing, rooting, and following guides here, I really want to start getting in on the conversations and discussions. Let me go through with what happened to my last LG Volt...
I had successfully rooted the device using towelroot and been playing around with the usual root access apps. I had superuser, busybox, etc. What I came across as a problem with the device was it's RAM usage on a lot of apps and the problem was largely just OS (after purging a lot of apps off the device). The biggest problem I was having was with Skype crashing and ending calls anytime you switched out of the Skype app itself.
Being the idiot I am, I began looking into possibly using SWAP memory to try to extend my RAM a little to see if I could correct what Skype was doing (assuming it was a RAM issue, which, now thinking about it, I don't think it was because my EVO V worked fine [On custom roms granted]). So I tried doing some swap stuff and it overall just would not go. I figured it was a KitKat issue involving the SD Card and how the file structure on the LG Volt seemed to handle SD related stuff, all going to emulated memory. So. I decided it wasn't worth the trouble and research anymore, and considering not too much work had been done on the Volt yet, I decided to give up that campaign and wait for more research to get done.
In the mean time, I told the phone to do a factory reset so I can start back fresh and go about using the device normally. This might have been where I made a mistake. I told the device to factory reset and format everything through the Android OS instead of booting into the stock recovery and telling it to do a factory reset. The phone shut off and never came back. I was not able to get it to charge, I could not enter LG Download Mode, I couldn't get into the recovery, absolutely nothing. Tried seeing if I could use the LG Mobile support tool to push anything to the phone since my computer could still see the phone connected... No luck.
So, my questions to the team here on XDA is:
1. What exactly happened to cause the phone to start the factory reset, but, lose everything? I could only assume that the phone kicked the system, data, boot, recovery, and... well.. everything off and fried it's memory. I assume it had to do with what I was trying to do with swap memory and something getting seriously messed up.
2. More specific on what the phone did after, it would not turn on, charge, go to recovery, or download mode. It was completely unresponsive. Would there have been a way to resurrect this phone back from the dead that I wasn't able to find after all the looking and research I had done?
3. With the new LG Volt I recieved from Virgin, how safe would you say things would be to go about rooting again and being more careful with my apps while I wait or get involved with some of the future ROM development for the device?
4. Is there something with how LGs recovery and download partitions are set up that would cause these to be unable to function? Or something that is particular to the LG Volt?
Finally, 5. I noticed that the work done and the team researching the Volt right now have managed to get an unlocked bootloader and a custom recovery that works. Would it be safe with the research done now to go about unlocking and flashing the custom recovery on?
These questions all take into account common knowledge stuff such as, the potentially to brick a phone again is always there and to continue doing as much research and reading as I can to know what I'm doing with the device accurately. Hope my questions can be answered here, until then, cheers gentlemen.
Click to expand...
Click to collapse
1. im not sure what is going on lately, but there seems to be an influx of jacked phones lately from botched modding and attempting to fdr to fix it.
a note for future reference, a fdr will fix nothing you did that required root. so if you mess something up, just go right for the stock flash to try and fix it, if it can be fixed.
2. i doubt it.
3. i would go for it.
4. cant answer that, sorry.
5. absolutely, as long as it is stable.
any body knows how te get correct spc or msl..i try with meid converter but wrong msl..please.
Hey all, before I start I'd like to apologise for making the post here but I don't know what you guys would classify the state of my phone as, "bricked, soft-bricked, hard-bricked", I have no clue! As a result I have no idea what threads to start looking in so I've come here to make this, sorry again!
I'm here looking for help because I think I've completely destroyed my Moto G and really really would like to fix it.
Basically, I had been running an old version of CyanogenMod for months and was not able to update due to the fact my bootloader was not updated. After finally updating it through a tool on XDA, I installed the newest version of CyanogenMod onto the phone and it was all going well, except for the fact all of my Google apps were crashing and making it impossible to use.
Now, I'm not sure why, but without taking any precautionary measures or looking into it at all or what I needed to do, I then decided to try and flash a Paranoid Android rom onto the phone, which installed fine. I load the phone up and something comes up with a passcode saying I need to unlock it to use the phone. I put in some random things and eventually get it, but it says my data is corrupted and therefore I need to reset to factory settings and there's a button there to do it. I think "why not" and click.
So now, the phone did something weird and basically went into a bootloop of the PA logo, so I restarted the phone and went to the bootloader thing. When doing "Normal Startup" it loads the phone with the PA logo like before, comes up with a brief "Android is Upgrading" screen before showing me the passcode screen for half a second, before repeating this, thus having a bootloop. Every so often, I can put my code in and press the reset button again, but it does the same thing.
On the other hand, if I try to access my ClockworkMod recovery system, the screen repeatedly flashes with the CWM background of the Android Alien guy, as if to say it keeps trying to start but it cannot.
TLDR: I cannot access my phone through a normal powerup or through my recovery, have I screwed it completely?
I'd hugely appreciate any help here guys because I'm stressing like I never have before here, thanks!
EDIT: it is the X0123 version!
Spaciouz said:
TLDR: I cannot access my phone through a normal powerup or through my recovery, have I screwed it completely?
I'd hugely appreciate any help here guys because I'm stressing like I never have before here, thanks!
EDIT: it is the X0123 version!
Click to expand...
Click to collapse
Just a few questions before I start suggesting a full flash to stock.
Did you have any SIM passwords, boot passwords, CWM passwords before flashing?
Also In CWM does it flash before any options are selected and did you dirty flash the new ROM over the old ROM?
Anyway, your phone is not hardbricked as it can get to recovery so thats good news.
I would suggest flashing your phone back to factory stock using the tools here on XDA (http://forum.xda-developers.com/showthread.php?t=2542219). That should hopefully resolve most of the issues and then if you feel like it you can start flashing custom ROMs again.
Hi ~
- Be kind with me, it's my first post! -
I'm facing a very bad problem with my Galaxy S6. A week ago I received an OTA from Samsung and I installed it. My phone rebooted and showed the bugdroid, meaning that the update was progressing. After that, the device keep rebooting over and over just after I entered my encryption password. I said to myself that I can try to wipe the cache because maybe an application was causing this problem. But now, the device is only showing the Samsung logo then just shut himself off.
Now I need your help to get my data. The hard part is that my device is encrypted. After many hour of search I see two solutions:
Flash the rom via ODIN
Install TWRP which can read encrypted volumes
The first solution seems easy and I keep the warranty. The problem is that I'm not 100% sure that flashing the rom again will not touch the /data and /sdext partitions (and the header/footer where master key are to decrypt the volume).
The second solution seems safer and should not touch any other partitions. But knox counter will be incremented and I will loose my warranty.
So, does anyone could test if flashing the rom via ODIN do not absolutely touch encrypted volumes and certificate that I will be able to get my data again?
Thank you a lot
Have a leap of faith. Go ahead and flash. Otherwise bring it to Samsung for warranty repair. They may be able to recover your data for you.
roydok said:
Have a leap of faith. Go ahead and flash. Otherwise bring it to Samsung for warranty repair. They may be able to recover your data for you.
Click to expand...
Click to collapse
I want to be sure and I don't want to loose any photos if possible, so no
I already tried to go in a Samsung repair store (Allo PSM), but they just don't care about my data, their job is just to make the phone working again.
So Anyone is able to confirm to me that flashing stock Galaxy S6 ROM (AP Via Odin) doesn't touch the /data and /sdext partition that are encrypted?
After many hours of search, I was able to make my phone working again!
For anyone concerned by the problem in the future, here's some informations:
You can flash a stock rom, your encrypted /data will not be erased and you will be prompt to enter your password on the next boot
In my case flashing a newer rom didn't solve my problem (bootloop after entering the password of the encrypted partition). I had to flash the rom that was in the phone before the OTA.
Now everything seems to working again. No data were lost, all my configuration was saved. Android showed a message that a problem occurred during the upgrade process and I sent logs to Samsung, hoping that it will help them!