Hi, I have a very strange problem on my DHD. I started to have a lot of FC, making the phone unusable. I tried to make a factory reset from settings but the phone got stucked at HTC logo, and nothing was wiped. I made a factory reset from bootloader, but the phone vibrated three times and also got stucked at logo. I made a factory reset from recovery and the process was completed, but with some errors. Then I rebooted and nothing was wipe, and the FC's were still there.
So I decided to flash an RUU, the process was completed and now I have exactly the same! Same ROM, same data, nothing wiped, nothing flashed.
So it seems like the memory is corrupted and not writable at all or something like that?
The phone is completely stock, never rooted or debranded (it's from Vodafone Spain)
Yes, it's problem with eMMC.
http://forum.xda-developers.com/showthread.php?t=2602786&page=18
This is not my thread but I have lot of post in it.
Explaining about exactly the same problem.
In link is final page in which you can see what i have done for now.
I'm trying to repair it without changeing eMMC.
I recomend reading the whole thread.
Woah, seems complicated... Thank you very much, I'll try and report!
Related
Does someone know what this mean? Every time i boot my device i`ve got this screen. If i push power button all my data will be lost, but if i push the round circle or do nothing devise boots normally.
I had this earlier and i did mtty and i assumed that this problem was gone, but no. I have my own rom (23053) and after flash ewerything was fine. This thing come up later when i had to do soft reset.
Nobody?? What is this?
something went worng in the flashing process of your own rom.
there are 2 ways of fixing this.... MTTY or flashing an original rom, an then reflash your own rom.
I recommend you the second one heheh
From MRM2007's signature you can find an original rom
http://ifile.it/_hq1nlzf/Diamond_ROM-Radio-SPL
Also the most safe way to do this is from your internal storage, puting diamimg file in your internal storage, go into bootloader ( press <-- + VolDown while softresetting) and follow instructions.
Flash that one, hard reset, flash your rom, hard reset and test it again...
Credit goes to mrm2007 that help me with this also.
Mariano.
I did earlier MTTY and i tought that everythin vas fine. But no. Earlier when i had some boot broblem, my device just did hard reset, no that kind of screen.
That`s not a broblem for me. I`m just courious what that might be.
By the way. I allways flash roms in internal storage.
I was updating some apps in the market, as suddenly the phone reboots without any warnings.
OK, **** happens i thought and let it boot. But now the phone starts the ROMs boot animation for about 4-5 seconds and then reboots over and over again.
I pulled the battery and started into recovery. I made a nandroid and wiped cache and dalvik. Reboot with same behavior.
Recovery again: wiped everything and flashed a new AOKP M3 - result: reboot and loop again
Back to recovery: tried to flash the before made nandroid - MD5 checksum error
Flashed an older nandroid and got boot loops again.
So, i think this piece is for the service now...
What is the best way to reset this GN? Using ToolKit to put back stock recovery and lock the bootloader? Or should i try something else?
Update:
Flashed Stock Google Image via ToolKit 5.4 and after that the phone is booting normal?!?
I reflashed the touch recovery and pushed the AOKP build 27 back to the phone and flashed it.
So far so good - I have to start from the bottom now, because flashing the stock rom wiped the whole phone and EVERYTHING on sdcard is gone
Do you think there is a hardware failure? Perhaps some sort of memory malfunktion or something like that?
Same thing just happened to me, thi is the second time
lighthammerhh said:
I was updating some apps in the market, as suddenly the phone reboots without any warnings.
OK, **** happens i thought and let it boot. But now the phone starts the ROMs boot animation for about 4-5 seconds and then reboots over and over again.
I pulled the battery and started into recovery. I made a nandroid and wiped cache and dalvik. Reboot with same behavior.
Recovery again: wiped everything and flashed a new AOKP M3 - result: reboot and loop again
Back to recovery: tried to flash the before made nandroid - MD5 checksum error
Flashed an older nandroid and got boot loops again.
So, i think this piece is for the service now...
What is the best way to reset this GN? Using ToolKit to put back stock recovery and lock the bootloader? Or should i try something else?
Update:
Flashed Stock Google Image via ToolKit 5.4 and after that the phone is booting normal?!?
I reflashed the touch recovery and pushed the AOKP build 27 back to the phone and flashed it.
So far so good - I have to start from the bottom now, because flashing the stock rom wiped the whole phone and EVERYTHING on sdcard is gone
Do you think there is a hardware failure? Perhaps some sort of memory malfunktion or something like that?
Click to expand...
Click to collapse
Firstly when you get bootloops or any other problem do NOT do a nandroid as it backs up EVERYTHING, including the problem.
When you "wiped everything" did you go to mounts and storage and format system, cache and data?
If not then you didn't do a proper full wipe.
This is my own experience, but I want to warn you guys. I had a similar problem with my GNex. The first time it happened, my phone rebooted itself every 5 seconds. I completely restored it using factory image and it ran fine for 3 weeks, then one day, the phone just rebooted itself and got stuck at the boot image. I had to factory reset it again to make it work.
After the second time, I called Samsung and sent it in for repair last week. They are shipping me a replacement unit. It seems the problem was hardware related.
econometrician said:
This is my own experience, but I want to warn you guys. I had a similar problem with my GNex. The first time it happened, my phone rebooted itself every 5 seconds. I completely restored it using factory image and it ran fine for 3 weeks, then one day, the phone just rebooted itself and got stuck at the boot image. I had to factory reset it again to make it work.
After the second time, I called Samsung and sent it in for repair last week. They are shipping me a replacement unit. It seems the problem was hardware related.
Click to expand...
Click to collapse
For 3 weeks... exactly 3 weeks, 21 days?
I can tell you that my first boot loop brick was 20 days after I bought the phone. The second was later that day. But the third one was... again, 20 days after the last successful restore. Is there something magical about the 3-week mark???
I am currently taking nightly nandroid backups, so when I had my third boot loop brick my backup was just under a day old. If this is ultimately a hardware problem that can be warrantied, I guess I'll have to try that next time. I would have to make sure I return it with the bootloader locked, stock recovery, but without the wipe because it has to still be boot looping to prove there's an issue!
Anyway, things I will point out:
- It's the complete wipe in bootloader that blanks the internal storage.
- If you have CWM installed, you can back up the internal storage over USB via adb pull /sdcard/ ./sdcard/ (correct me if I got the syntax wrong)
- When the boot loop brick has happened, CWM is not capable of properly reformatting or restoring to the data partition. I have not found a way to repair it without blanking /sdcard (which on the GN is actually in /data/media), so if you don't want to lose those files the only way to keep them is to pipe them out, blank the phone, and then pipe them back in afterwards.
- After a complete wipe in bootloader (either by flashing userdata.img or by relocking/unlocking bootloader), you must boot the phone once into the OS in order to complete the reformatting of /data. If you try booting straight into recovery after a wipe in the bootloader, CWM cannot read or write from that partition.
Can't say for sure whether it's exactly 21 days but it's definitely around 3 weeks. Why don't u give Samsung a call? The phone is not supposed to behave this way. Plenty of people don't have this problem. My wild guess is that the internal flash memory is faulty.
econometrician said:
Can't say for sure whether it's exactly 21 days but it's definitely around 3 weeks. Why don't u give Samsung a call? The phone is not supposed to behave this way. Plenty of people don't have this problem. My wild guess is that the internal flash memory is faulty.
Click to expand...
Click to collapse
I'll warranty it through my carrier next time as they do exchanges on site. The trouble is, once I've recovered the phone, there's no evidence of the problem anymore. The best way to prove it is to show it fritzing out.
Sent from my Galaxy Nexus using Tapatalk
I think this is a known problem. You shouldn't have to prove it to them. They should be aware of it.
It bricked again today so I warrantied it in-store at my carrier. They gave me a brand new one after being unable to find a solution when fiddling with it. As a bonus, all the little hairline scratches on my screen are gone too
The store guy said he's never seen this issue, and it's one of only two warranty locations for my carrier in the Vancouver area. So I can only hope this was a rare hardware problem and not something that pervades every GN they're going to sell.
I can tell this one is from a different batch because it came preloaded with 4.0.2.
Good for you. hopefully my new phone will behave
Hello, all. I've had this problem for about a year, but I just kind of put the KF away once I got it replaced instead of fixing it.
Last year, I put my KF into a softbrick, factory reset bootloop. On boot, the KF warns:
Your Kindle has detected a problem and must clear App storage. The recovery process will erase some apps and data from your device.
Click to expand...
Click to collapse
The rest is the generic factory reset info. Press power to proceed. This looks like it goes through the process, restarts, and just boots back up into this message. Thus, bootloop. I've tried looking up others with the same problem, but no one has had the same one I mention. I don't have a custom bootloader or TWRP.
As for what caused this, if i can remember correctly I was having trouble with google apps permissions and changed a folder in /system/ to something else. The fire freaked out and I rebooted it. The above has happened ever since. So the only modification is being rooted. I've tried getting access to adb, but it hasn't listed the device. Maybe I installed the drivers wrong or something, but I didn't mess with it for long because I don't like being in Windows if I can help it.
Any help would be greatly appreciated. Not in too big of a hurry, though, as I have a Nexus 7 currently. ^.^
Get a factory cable to force it into fastboot so you can flash a new bootloader and twrp , then flash a new rom. You can also attempt to race it to factory reset and reset it some have success.
Thepooch said:
Get a factory cable to force it into fastboot so you can flash a new bootloader and twrp , then flash a new rom. You can also attempt to race it to factory reset and reset it some have success.
Click to expand...
Click to collapse
I knew about fastboot, I should have mentioned. I just don't have the money to spend on one currently. What do you mean by attempt to race it to factory reset and reset it?
Just what I said you have just a little time to race to settings and factory reset it before it fc`s and shuts down some people manage to pull it off.
Hello,
today I accidentally tapped on "Update" (to 7.1.1) on my rooted Nexus 5X... Something you usually shouldn't do, but it was 2am and I was tired and.... Doesn't matter. After this my phone rebooted and almost instantly showed the dead android with the message "No command". And now I'm stuck there. After rebooting I still land there.
Since the error message almost instantly appeared and since I still can boot into TWRP (3.0.2-2), I think the update wasn't installed and I hope to find a way to avoid the factory reset of my phone. Do you have some tips or possible solutions what I should do in this case?
Thank you for your help.
Its odd this happened, when rooted and twrp installed. in my experience, the update will just simply fail and it will boot back up.... in your case, it sounds like something flashed but the phone didnt like it.... All I can think of is if you cant get into twrp, boot into fastboot and flash the factory image from google, you will loose all data though.....
EDIT, RE-READ you post, if you CAN get into TWRP, try flashing a backup... you should have a backup I hope, lol... First rule of root and flashing is make a backup asap....LOL
When I rooted my phone I did a backup. But the problem is, it was several months ago. So I tried the only method I could save all my data. It wasn't safe, I knew this, but no risk no fun.
My solution was: Download the ota update from Google and flash it with TWRP... Voila! My phone boots properly with the new update... But this method is like I mentioned before not safe and can probably cause a boot-loop with an overwritten recovery. I had to flash my recovery again, but everything works fine now.
Hi all,
Maybe you've read my previous post, but I encountered the next problem
My phone was running HDMaximus 7.1.0, no problems. Just reinstalled it last week since I got some Google Play Services errors. Now, my phone rebooted suddenly, and after that it stated: Your phone has been encrypted. Well, I entered my PIN, which was correct, but my data is corrupt.
Tried some things, also with TWRP, and now I'm stuck with the M9, with TWRP, without OS and my internal storage is saying 0mb. Repairing that partition didn't help.
I've tried to sideload it, to push it, nothing helps, because of the internal storage. But the connection with the device is there, so that's not the problem.
Is there a way to recover from this? Maybe with a stock RUU from the SD card, or to rewrite the partitions?
Help is appreciated!
Regards,
Jacco
Fryslanboy said:
Hi all,
Maybe you've read my previous post, but I encountered the next problem
My phone was running HDMaximus 7.1.0, no problems. Just reinstalled it last week since I got some Google Play Services errors. Now, my phone rebooted suddenly, and after that it stated: Your phone has been encrypted. Well, I entered my PIN, which was correct, but my data is corrupt.
Tried some things, also with TWRP, and now I'm stuck with the M9, with TWRP, without OS and my internal storage is saying 0mb. Repairing that partition didn't help.
I've tried to sideload it, to push it, nothing helps, because of the internal storage. But the connection with the device is there, so that's not the problem.
Is there a way to recover from this? Maybe with a stock RUU from the SD card, or to rewrite the partitions?
Help is appreciated!
Regards,
Jacco
Click to expand...
Click to collapse
https://forum.xda-developers.com/verizon-one-m9/help/bricked-issues-return-to-100-stock-t3547433
Read my thread hope this helps.
Thats helping me a lot. I tried it with a stock RUU, 3.35.401.12, but when I start the download mode to flash it, it reboots just as soon when I push the Vol Up button. Weird.
(Phone is doing the whole sequence in about a second, then reboots and nothing happens)
Fryslanboy said:
Thats helping me a lot. I tried it with a stock RUU, 3.35.401.12, but when I start the download mode to flash it, it reboots just as soon when I push the Vol Up button. Weird.
(Phone is doing the whole sequence in about a second, then reboots and nothing happens)
Click to expand...
Click to collapse
That is weird. Did u format data in TWRP by typing Yes, not just factory reset?
Well, I can't get into TWRP anymore. When I select Recovery in the fastboot menu, it goes to the black HTC screen, after that quick flash of the TWRP screen (it worked before) and then it goes to it's white HTC screen.
I'll try to install TWRP via fastboot, maybe that'll help
Just tried to flash TWRP through fastboot, which was finished, but I still can't access Recovery. Weird..
You haven't stated if you are s-off. Have you made sure the stock rom matches your sku?.
Beamed in by telepathy.
Yes,
I am S-OFF. I tried several rom's, but I'll double check that. Good point!