Develop Bugs

[Q] What exactly is on the emmc and what should not work when it is fried ?

After self rebooting while trying out vlc beta et freezing:
My DZ refuses to (symptom is I end stuck on green HTC logo on white screen for each of these possibilities):
* boot to OS
* boot to recovery (through bootloader) (So no adb possible)
* factory reset from bootloader
It will however:
* boot to bootloader (Vol-+Power) and go to fastboot
* accept flashing via fastboot (Ive flashed various recoveries and finally even reflashed stock RUU hoping it could help)
I've notice that when I tuen it on normally, I vibrates then I get HTC logo than after a few seconds it vibrates once and stays on HTC logo
For the record this has allready happend once in the past... and I eventually got it to reboot by leaving the DZ batteryless for a hole weak (I tried 24h, 48h and eventually a weak) before putting the battery back in and seeing it let me boot it to recovery... My reasonning behind this wait was that there might be accumulated static somewhere and that leaving it out batteryless would drain all juice out and the static with it (based on computer motherbaord issues allready encountered)... Since then I have been on Virtuous Unity, Affinity, Quatro and lately Andromadus Audacity Beta1-4 and lastly mimicry whithout any problems.
So right now It is again sitting out battery less for several days as 24h has not sufficed...
As I wait (I'm suffering o an old iPhone 2g...) I have been going through all the forums looking for information... And have found tons of issues concerning the emmc and its "fryability". However everytime people talk about fried emmcs they seeem to be booting to recovery without an issue...
If the phone never boots, I'm guessing there are 3 possible explanations:
* emmc
* motherboard
* cpu
Now I've found that all can be repurchased (yeah warranty gone for me as I'm S-Off and unless I can boot one last time permroot and revert gfree I will stay S-Off) at http://www.parts4repair.com/htc-desire-z/
But the real question is: Is there a way to determine if emmc is fried (I'm booting to bootlader which seems to be on emmc from my understanding)
Finally I've allways assumed that it is useless to leave the phone at HTC logo more than 30 seconds... is this a mistake ?
Thanks in advance for any help/answers
P.S. Does the battery charge when in bootloader or fastboot ? If not I might not be able to reccharge it once it is drained...

http://forum.xda-developers.com/showthread.php?t=1039504
http://forum.xda-developers.com/archive/index.php/t-1456036.html
http://forum.xda-developers.com/showthread.php?t=1051995
http://forum.xda-developers.com/showthread.php?t=1456036
first see what chip you have, you can use adb commands within your bootloader
have you been able to get fastboot to work at all?

Thanks for all the links, I had allready read those threads and those are what generated my questions.
Yes fastboot seems to work (flashing ends with OK every time)
I have tried to adb to the phone when in bootloader but that is a no go (From my research I thought the phone had to be either booted normally or in recovery to be able to adb to it and since I can do none of those two...)

When I reflashed stock 1.34 ROM from fastboot it overwrote the bootloader and replaced the engineering one with the stock one (I can see that when in bootlader)... So am I correct in assuming that the emmc is not fried and that all flashboot flashes are therefor working ?

to my understanding some blocks in the emmc get corrupt and others don't, just being able to rewrite hboot or recovery doesn't mean everything is fine it may just mean this block is ok. where you able to write a new recovery and boot into it?
Sent from my HTC Vision using xda premium

Flashing a recovery seems OK (i.e. according to command line it worked) but booting to it does not work...
I've tried cwm and 4ext (used to be on 4Ext).
I'll wait out my week with the battery pulled out and see what happens when I put it back in... But if it does boot I'm S-Oning it and send it in for warranty because this behavior isn't normal...

dwardo said:
Flashing a recovery seems OK (i.e. according to command line it worked) but booting to it does not work...
I've tried cwm and 4ext (used to be on 4Ext).
I'll wait out my week with the battery pulled out and see what happens when I put it back in... But if it does boot I'm S-Oning it and send it in for warranty because this behavior isn't normal...
Click to expand...
Click to collapse
Well no luck...
I've reflashed it with HTC 1.34.405*RUU.exe --> Seemd to go fine but didn't reboot after
I've reflashed using the corresponding PC10IMP.zip on /sdcard and booting into bootloader:
where I got
BOOTLOADER ok
BOOT ok
RECOVERY ok
SYSTEM ok
etc...
Everything said OK... but still won't boot to OS or to recovery stays on green HTC logo on white background.
I've noticed 2 things:
* that on booting it vibrates once then a few seconds (~5) it vibrates once again while on HTC green on white logo and just stays there after...
* that when it is off and I plug the usb, the led does not turn on... (indicator of mobo problem ?)

Well tonight I tried reviving the phone again... 10 days without touching the phone...
Lets' back up here... 10 days ago I flashed a modified Stock PC10IMG of 1.34.405.5 RUU - modified because I repalced bootloader with DZ engineering one and recovery with 4ext-touch-recovery-1.0.0.3-RC3. But the phone would not:
* boot to recovery
* fastboot boot 4ext-touch-recovery-1.0.0.5-RC3.img
* fastboot boot boottosd.img
So back to tonight... I tried
fastboot boot 4ext-touch-recovery-1.0.0.5-RC3.img
and it booted to recovery right away (less than 10 seconds... in the past I have left it for more than 10 minutes without succes...) and complained that cache partition needed wiping... (This is odd to me I thought the PC10IMG flashing would do that...)
So anyways I did just that and then went for the emmc version and got:
#cat /sys/class/block/mmcblk0/device/name
SEM04G
So normally the good emmcs...
Then I rebooted to recovery from Nand flash (not fastboot) worked and finaly rebooted to stock 1.34.405.5 (i.e. rooted for now)
So now I'm just wondering WHAT HAPPENED ?
I did nothing in between 2 series of similar boot tests... except wait 10 days.
I'm leaning more and more towards static electricity problems...
So now I'm wondering... Get back to S-on ? but I'ts working so servicing will not be accepted... Or going back to Andromadus mimicry (I have a backup I can apply )
Well going for andromadus as I allready bought a phone with broken lcd for parts !
If anyone has commands he would like me to run I'm more than willing to do it...

How to fix blocked boot recovery samsung?

Hello guys,
A few months ago, I rooted my phone using kingroot. After a few weeks, i tried to install TWRP custom recover to unlock bootloader. I accidently downloaded a wrong version of it and flashed it using flashify app, after which i booted into recovery to check the new recover mode. But, something awkward happened. THE BOOT MODE DIDN'T OPEN AND THE SCREEN GOT STUCK AT "Booting into recovery". I read on the internet and realised that my device has got soft-bricked. Also, phone wasn't rebooting. So, i found a solution atleast start my phone. I took out my battery, pressed the buttons for download mode and then placed the battery back in and pressed the buttons for download mode and somewhow rebooted my phone (i read about this technique in xda forums). Now, although my phone works but i cannot access the recovery mode as it has got soft-bricked. Thus, i cannot perform a hard reset as it gets caught in that "recovery booting stuck cycle". So, can anyone tell me how to fix this? PLS QUICKLY. aLSO, i don't know much about ADB, so pls explain that too as my friend suggested me to use ADB to fix softbrick but im not sure!!
:crying:

random infinite bootloop.

Hello there
After my phone randomly rebooted while watching a video it ran into a bootloop.
I had been running LineageOS for the past couple of months and everything was fine up until yesterday.
I have tried restarting, and everything and only managed to reflash twrp via adb and force it to boot into twrp, but now it's stuck booting into that.
when I try to boot into lineage I only see the boot animation of lineage that never stops, and when I boot into twrp I see the boot screen of that, which never stops.
I've let the phone do its thing for so long that it has run out of power, so it's not something that just takes a long time. I feel like this thing is completely bricked now.
Anyone maybe got a solution? Any help would be appreciated.

Hi,
Think I might have the same issue, except I didn't flash or modify anything on the phone. I'm running all stock ROM and all the rest.
Stuck in a bootloop in recovery mode. Mini partition does not recognise the phone. Same with QPST. QComDloader does, but only for a few seconds, so whatever I try it's not fast enough before the next reboot...
Whats are the options? I don't want to have to send it back to China

Stuck in boot loop even after factory reset. Able to get into bootloader and recovery

Hoping for some help or alternatives to fix my fiancee's Pixel XL. Last night the phone just kept flashing the 'G' logo on for 10 seconds, off for 10 seconds. She said the phone was close to dying before it happened, and I imagine it probably ended up draining the battery afterwards with the constant bootloop. Plugged it in all night but the charging screen didn't come up and would just stay in the bootloop. I could get it into the boot loader (power button and volume down), but it wouldn't go into recovery mode and instead would go right back to the boot loop.
So I tried a battery pack to charge it and it still didn't show charging, but I was able to get it into recovery mode eventually, but still boot loop afterwards. At one point, after leaving it on boot loader menu while attempting to charge, it eventually just tried to start itself and made its way to the second Google splash screen after the main G logo. Looked like it froze there though and I couldn't get it to that point again.
On my way to work this morning I tried plugging it into my car's USB port after powering off from the boot loader, and this time I kept flashing that it was charging (looked like it was 3/4 charged but not sure how accurate that is). So I got into recovery again and tried 3 factory resets consecutively. Still bootloop after attempting a startup afterwards. There was a similar issue a couple weeks ago where it looked like it was stuck in a bootloop, but it turned out the phone actually was dead that time and the charger wasn't working. Once we switched chargers it booted right up.
Any other suggestions or possibilities? I don't have much troubleshooting experience otherwise. Phone is fully stock, Google Fi. Any other info I can provide please let me know!

well, i'm not sure if it makes a difference, but now for some reason i can't get into recovery mode again. just goes into the boot loop. It also goes into the boot loop as soon as I plug the phone in to charge.

cgibsong002 said:
well, i'm not sure if it makes a difference, but now for some reason i can't get into recovery mode again. just goes into the boot loop. It also goes into the boot loop as soon as I plug the phone in to charge.
Click to expand...
Click to collapse
I assume you can't get into the bootloader using power and volume down buttons?

I have always been about to get into the boot loader. Actually i can get into recovery again as well. Seems if i let it sit for a while it'll go to recovery again. Maybe heat related.

My OG Pixel did the same thing to me one morning. I tried everything to revive my pixel but nothing worked. I did some digging and it turns out there is an issue with the storage on the phone. It's just a old fancy paper weight.

cgibsong002 said:
I have always been about to get into the boot loader. Actually i can get into recovery again as well. Seems if i let it sit for a while it'll go to recovery again. Maybe heat related.
Click to expand...
Click to collapse
If you can get into recovery, have you tried to sideload a full ota.zip (not an update)?

mozhno said:
If you can get into recovery, have you tried to sideload a full ota.zip (not an update)?
Click to expand...
Click to collapse
I haven't. I see that Google has all the ota's on their site. Is there a specific one that i might want to try? The same one? Go back a few? Will i even be able to sideload if my phone is fully stock?
Edit: sideload adb successfully but no change. I loaded the 6-5 ota which was what i already had.

cgibsong002 said:
I haven't. I see that Google has all the ota's on their site. Is there a specific one that i might want to try? The same one? Go back a few? Will i even be able to sideload if my phone is fully stock?
Edit: sideload adb successfully but no change. I loaded the 6-5 ota which was what i already had.
Click to expand...
Click to collapse
Sounds as if it's time to just try stuff and see what sticks. Regarding using an ota, it works if you are stock, and I sideload it even if I have installed majisk or installed another kernel. It typically works for me with fewer chances of blowing things up than flashing a stock image. Regarding what to try next, you may have already gone into recovery to check the install function to see if your storage still appears and try to flash anything that worked in the past; if you have a backup in twrp you could try to restore it; you could wipe cache and dahlvik; or even sideload an earlier ota version that worked. Since the 6-5 ota did not work nothing really jumps out to me as obvious. One final caveat, I once had to reboot a sideloaded ota a second time before my pixel booted properly. If I think of something else I'll post again.

I took it to ubreakifix and they told me that this is indeed a known issue with pixel xl's that they all suffered from a faulty motherboard and that is indeed the cause here. Said he thought there was actually a class action about it so I'll have to look into it. Really pisses me off that Google repeatedly told me it's not a known issue when their authorized repair center says it is.
Anyway i have a warranty with Upsie that I'm hoping to get this replaced with. We'll see.

cgibsong002 said:
I took it to ubreakifix and they told me that this is indeed a known issue with pixel xl's that they all suffered from a faulty motherboard and that is indeed the cause here. Said he thought there was actually a class action about it so I'll have to look into it. Really pisses me off that Google repeatedly told me it's not a known issue when their authorized repair center says it is.
Anyway i have a warranty with Upsie that I'm hoping to get this replaced with. We'll see.
Click to expand...
Click to collapse
Good luck

I'm assuming you tried booting into twrp recovery, going to reboot, and picked slot A ( or B if already in A) to reboot to and then rebooted system? A lot of the times simply switching slots from recovery and then rebooting is the fix. At least for me.

手机早期经历的情况得说明一下。root没有？Twrp是谁的？

Also, for anyone else having this issue, try rebooting into the bootloader. Connect to PC, and try fastboot --set-active=a
If this doesn't work, try booting back into your recovery image using fastboot boot *whatever you named your TWRP recovery image* and then flashing your twrp.zip again in recovery, and when rebooting if you're in slot B choose slot A in recovery to boot into.
Also keep in mind in Windows 10, it uses Powershell, so commands have to be typed in .\fastboot not just fastboot or it won't take it.

Stuck in bootloop, fastboot works, TWRP wont load, can't side load

Hey guys, been a hot minute since I've been around these parts but I've got a weird one for you.
I'm stuck in a boot loop. I can get into the bootloader using pwr+vol up, but thats it. If I try to enter recovery it boot loops.
Using fastboot commands and I can get things to flash (so it says), but am still stuck in this bootloop.
Tried loading TWRP using fastboot boot twrp.img and it says it succeeded but then loops without ever getting the TWRP splash
Tried extracting the img files from the most recent OTA downloaded from google from the payload.bin and flashing those with no success.
Tried flashing the boot.img out of LineageOS and it still loops afterwards... I'll admit that this was a last ditch effort and I hope I didn't screw myself, but I figure I can just reflash if needed since I can still access fastboot.
I feel like since I can get into the bootloader that there's got to be SOMETHING I can do, but nothing seems to be working. Is this old phone truly bricked? Any ideas??

A little extra info. I was on a stock rom, it was rooted for a while and eventually after some of the ota's I lost it and didn't bother getting it back. the bootloader unlocked, though, so there's that.

ridethisbike said:
Hey guys, been a hot minute since I've been around these parts but I've got a weird one for you.
I'm stuck in a boot loop. I can get into the bootloader using pwr+vol up, but thats it. If I try to enter recovery it boot loops.
Using fastboot commands and I can get things to flash (so it says), but am still stuck in this bootloop.
Tried loading TWRP using fastboot boot twrp.img and it says it succeeded but then loops without ever getting the TWRP splash
Tried extracting the img files from the most recent OTA downloaded from google from the payload.bin and flashing those with no success.
Tried flashing the boot.img out of LineageOS and it still loops afterwards... I'll admit that this was a last ditch effort and I hope I didn't screw myself, but I figure I can just reflash if needed since I can still access fastboot.
I feel like since I can get into the bootloader that there's got to be SOMETHING I can do, but nothing seems to be working. Is this old phone truly bricked? Any ideas??
Click to expand...
Click to collapse
As a rule of thumb
-- A 'bricked phone' is usually unresponsive, won't power on, and doesn't function normally.