Database Develop

[Q] HELP! ZR C5503 freezing at boot then looping!

Hi All,
I desperately need help with my C5503. I've been trying to update from 4.3 to 4.4 (?) via OTA (.230 firmware) but have been unsuccessful. No problems though, my unit was fine and working without issues anyway. Before I begin, let me enumerate some points for clarity and completeness:
- phone has stock 4.3
- phone is rooted via towelroot with SuperSU installed
- phone has stock recovery
- phone has locked bootloader
- phone is out of warranty
- phone's USB debugging is OFF
- when plugged into a power outlet with the charger, the phone would charge normally (red led would light up, and if you clicked on the power button it would show the charging indicator)
- holding volume down and power does not do anything (phone continues to power on then freezes then reboots)
- holding volume up and power does not do anything (phone continues to power on then freezes then reboots)
- holding volume up then plugging in the usb cable while flashtool is on makes the phone connect in fastboot mode (blue LED light turns on)
- holding volume down then plugging in the usb cable while flashtool is on makes the phone connect in flash mode (no LED light)
Okay, let's continue to what happened. I have widgetsoid installed, and I chose a widget for reboot. Last night, when I pressed on the widget to reboot, as usual choices came up for normal, recovery, hotboot, bootloader, etc. For some reason, and maybe because I was getting frustrated at my phone not updating via OTA, I chose the "bootloader" option when I should have chosen "normal." My phone turned off, then after a few seconds the "SONY" logo came up followed by "XPERIA." After that, the colorful ribbons, then BAM it just froze. Then after a few seconds or so, it looped back to the "SONY" logo again and repeated the cycle until I pulled out the battery.
It's worth noting that I never got past the colorful ribbons until it would freeze and would reboot, but it doesn't freeze at the same place every time. Sometimes the colorful ribbons would just start to come out when it would freeze, or it would freeze in the middle, or it would freeze towards the end. But I never got past the first animation of the colorful ribbons before it would freeze and reboot.
Next steps: I researched like crazy about what to do and the advice was to flash the firmware. So...
- I downloaded and installed the latest flashtool by androxyde. Got it working as it should.
- I also downloaded the kernel only ftf files for .230, .283, and .292 for flashing in case I had to do it that way.
- I even downloaded the stock firmware (via xperifirm with flashtool) and created the ftf for my region (custom PH), carefully excluding TA files.
- I carefully followed the instructions to flash the phone but encountered an error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- I also tried fastboot but it kept asking for a kernel (.sin) file that I don't have and I have no idea where to find. I don't have any idea what to use either.
I'm seriously out of options at this point, as nothing I do seems to work. Maybe it's because USB Debugging is OFF that's why I'm unable to make any headway? But maybe somebody out there has found a way? Is it time to bring this to the service center?
Please help, I'm willing to lose all my contacts and apps and start over if I have to, as long as my phone works again. I'm desperate! :crying:
TIA!

update: fastboot mode
Using flashtool's fastboot mode (blue LED lit up), this is what shows up in the main window:
My bootloader is locked and the USB debugging is off, is there anything I can do at this point? I hope someone can help, please!

what is error in processHeader: 1 : incorrect function?
I've tried looking for more information about this error but it doesn't look like flashtool has an extensive documentation on error codes. Google hasn't really given me a lot of leads either. Does anybody know? Any advice? Please?

Update: TA backup, ADB installation, CWM installation
I've downloaded and installed TA backup so I can back up the DRM keys before attempting to unlock the bootloader. But since the phone won't turn on, I can't turn on the usb debugging either, so no joy there.
I've downloaded the minimal adb and fastboot files from here: http://forum.xda-developers.com/showthread.php?t=2317790 so I can try to go into recovery and maybe install CWM, but since the phone won't boot properly and usb debugging is off, the phone isn't detected by adb either.
Seems like it's a hopeless case. I hope somebody can give me some more ideas to try.

manilenio said:
I've downloaded and installed TA backup so I can back up the DRM keys before attempting to unlock the bootloader. But since the phone won't turn on, I can't turn on the usb debugging either, so no joy there.
I've downloaded the minimal adb and fastboot files from here: http://forum.xda-developers.com/showthread.php?t=2317790 so I can try to go into recovery and maybe install CWM, but since the phone won't boot properly and usb debugging is off, the phone isn't detected by adb either.
Seems like it's a hopeless case. I hope somebody can give me some more ideas to try.
Click to expand...
Click to collapse
Try the ftf from this thread http://forum.xda-developers.com/showthread.php?p=50195441
Tapped from my furious Dogo

Hi! Thank you for your advice. Can you be more specific about which ftf file to use? Thanks.

manilenio said:
Hi! Thank you for your advice. Can you be more specific about which ftf file to use? Thanks.
Click to expand...
Click to collapse
https://mega.co.nz/#!ipIk3LTD!DXLtfhcUREHjUKTDqsW_GrTgyH4iUrlVRBR__V3M93Y
Tapped from my furious Dogo

vaisakh7 said:
https://mega.co.nz/#!ipIk3LTD!DXLtfhcUREHjUKTDqsW_GrTgyH4iUrlVRBR__V3M93Y
Tapped from my furious Dogo
Click to expand...
Click to collapse
your link points to a c5502 firmware, my phone is a c5503. thank you, i'll look around for another ftf file and i'll try again.

Resolved, but all apps and data gone...
In the end, because I had no other recourse, I repaired using Sony's PC Companion. It did not require the bootloader to be unlocked (like the Sony flashtool) and did not require the USB debugging to be on, either. All it needed was internet connection to download the newest firmware available, and it flashed my phone in less than 10 minutes. I'm happy to say it worked, but sad that all my apps and data are gone. At least it's now working, and I don't have to go to the service center anymore or buy a new phone.
Next step: flash to .230 and install towelroot, then back to .283.
Thanks, this thread may now be closed.

Same sort of problem here.
I have same sort of problem.
Phone boots and when booted it shows black screen with Arrow back.
Once turned off it wont turn on any more and reboots after while.
I tried to fix same way but after restoring the problem was still the same.
So i unlocked the Phone (no backup from the key's oops...)
After that i installed a 4.4 rom but i think it is for a 5502 Phone. (mine is a 5503)
Everything works fine until i decided to try make a Phone call with it.
Phone part is not working now.
The i tried a 5503 rom and came back with the black screen problem again.
Any idea's how to fix the Phone part of this Phone so it works with a 5503 rom again?
Greetings from rijswijk - holland
manilenio said:
In the end, because I had no other recourse, I repaired using Sony's PC Companion. It did not require the bootloader to be unlocked (like the Sony flashtool) and did not require the USB debugging to be on, either. All it needed was internet connection to download the newest firmware available, and it flashed my phone in less than 10 minutes. I'm happy to say it worked, but sad that all my apps and data are gone. At least it's now working, and I don't have to go to the service center anymore or buy a new phone.
Next step: flash to .230 and install towelroot, then back to .283.
Thanks, this thread may now be closed.
Click to expand...
Click to collapse

vastloper said:
I have same sort of problem.
Phone boots and when booted it shows black screen with Arrow back.
Once turned off it wont turn on any more and reboots after while.
I tried to fix same way but after restoring the problem was still the same.
So i unlocked the Phone (no backup from the key's oops...)
After that i installed a 4.4 rom but i think it is for a 5502 Phone. (mine is a 5503)
Everything works fine until i decided to try make a Phone call with it.
Phone part is not working now.
The i tried a 5503 rom and came back with the black screen problem again.
Any idea's how to fix the Phone part of this Phone so it works with a 5503 rom again?
Greetings from rijswijk - holland
Click to expand...
Click to collapse
Hey, I think you should find a complete 5503 ftf file to use, then flash everything, don't exclude anything except the TA files. I'm not knowledgeable enough to really give you any other advice. I'm going back to 4.3, because 4.4.4 isn't worth the irritation (some of my apps don't work with kitkat, and kitkat prevents saving to the external sdcard too). I'll just wait for lollipop. Goodbye 4.4, hello again 4.3!

Stuck on bootloop - unrooted, S-ON, Unlocked, Tampered

Hi all... My device just went on bootloop. Last evening battery was drowned so I reached home and plugged it to charger and its on bootloop since then.. now fastboot screen is coming automatically on power on.
Screen is showing this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Don't know what to do as this device is not rooted or unlocked.

sumit77seo said:
Hi all... My device just went on bootloop. Last evening battery was drowned so I reached home and plugged it to charger and its on bootloop since then.. now fastboot screen is coming automatically on power on.
Screen is showing this:
Don't know what to do as this device is not rooted or unlocked.
Click to expand...
Click to collapse
You can try
Code:
fastboot erase cache
then a factory reset
otherwise you'll have to flash the 7.21.707.21 RUU to reset your phone back to stock. The ruu will wipe everything from your phone.
File and instructions here: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944

alray said:
You can try
Code:
fastboot erase cache
then a factory reset
otherwise you'll have to flash the 7.21.707.21 RUU to reset your phone back to stock. The ruu will wipe everything from your phone.
File and instructions here: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
Click to expand...
Click to collapse
Thanks I did all that... and I recovered successfully.. but after setting up... I just ran the older backup of my phone... and now its completely dead... No charging... no flashboot screen... nothing... completely dead.... But when plugged into system... After pressing power+vol down for 10 sec will make ding sound like its booting.... but nothing on phone... not even LED... Is my phone completely dead...

sumit77seo said:
Thanks I did all that... and I recovered successfully.. but after setting up... I just ran the older backup of my phone... and now its completely dead... No charging... no flashboot screen... nothing... completely dead.... But when plugged into system... After pressing power+vol down for 10 sec will make ding sound like its booting.... but nothing on phone... not even LED... Is my phone completely dead...
Click to expand...
Click to collapse
Sounds like your backup was corrupted or a mod inside the backup was no good for the device. Leave phone on the charger for a while and hopefully the juice will awaken it from it's sleep. Otherwise consider it bricked.
Sent from my C525c using Tapatalk

SHM said:
Sounds like your backup was corrupted or a mod inside the backup was no good for the device. Leave phone on the charger for a while and hopefully the juice will awaken it from it's sleep. Otherwise consider it bricked.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Ok I will plug into the wall charger for 2-3 hours. What do you mean by bricked. So can't we unbrick it?? As I have heard somewhere no device can be bricked fully. As my device is not in warranty, the HTC guys will charge me much more... Can't we do anything?

sumit77seo said:
Ok I will plug into the wall charger for 2-3 hours. What do you mean by bricked. So can't we unbrick it?? As I have heard somewhere no device can be bricked fully. As my device is not in warranty, the HTC guys will charge me much more... Can't we do anything?
Click to expand...
Click to collapse
There are two types of bricks. Soft and Hard. Soft brick typically means you have access to your device in some way to some degree that which would allow you to recover the device promptly. An example of a soft brick would be to corrupt your partitions and neither the recovery or system works. Even if by installing a custom recovery. But access to rebootRUU still makes it plausible to restore everything assuming one has access to that RUU (this example is HTC specific).
A hard brick would be a scenario where nothing is accessible. System, recovery, bootloader, etc. Meaning there is no feasible way to gain the needed access to restore your device in some fashion so that it will work again.
Both types of bricks exist and both types of bricks are easily possible. Although, a hard brick is very unlikely to be seen by most since most typically have some sort of knowledge as to what they are doing prior to doing it. An example for a Hard Brick would be to attempt to reverse engineer the bootloader, make an error that goes unnoticed, and apply the mod with this fatal error to the device thus resulting in the device failing to boot at all.
Sent from my C525c using Tapatalk

SHM said:
There are two types of bricks. Soft and Hard.
Click to expand...
Click to collapse
though i tend to agree with you, but there are more than two types... i can think of at least four (not sure atm if i can think of more),
from mild, soft, hard, or just not-bricked-but-not-bootable either bricks
but when it goes from "Last evening battery was drowned so I reached home and plugged it to charger and its on bootloop since then" ... i wasnt flashing my phone or anything else, it just happened, then 99% of the time it's a hardware problem, and wont be fixed without changing the motherboard.

nkk71 said:
though i tend to agree with you, but there are more than two types... i can think of at least four (not sure atm if i can think of more),
from mild, soft, hard, or just not-bricked-but-not-bootable either bricks
but when it goes from "Last evening battery was drowned so I reached home and plugged it to charger and its on bootloop since then" ... i wasnt flashing my phone or anything else, it just happened, then 99% of the time it's a hardware problem, and wont be fixed without changing the motherboard.
Click to expand...
Click to collapse
A hardware issue could definitely be the cause. Thanks for bringing that up. As of there being four types... I believe there is really only two. Soft (still have access to some degree whether it be the recovery or just fastboot for example), hard (absolutely no access), and boot loops (Everything is operable but something as small as a file not having proper permissions), but could honestly be debatable so lets just agree just to agree lol.
With that said, I experienced a soft brick last weekend. I was converting my device to f2fs and borked my partitions after twrp abruptly crashed on me. Had no access to the recovery, system, and so on - it all failed to boot or respond in any way. I did however still have access to fastboot which allowed me to use my decrypted RUU. If not for that, my phone would be nothing more than a paperweight.
Sent from my C525c using Tapatalk

I believe I have bricked my HTC One Mini 2?

Was at work using both my company phone (iPhone 5) and my personal phone (HTC One Mini 2) just fine. Put my personal phone away to get on with actual work and came home at around 5:30'ish. Played a bit ("a bit") until about 9/10pm (I think?) whereby I looked for my phone to just check things like WhatsApp and Snapchat and the phone wasn't turning on when I was holding the power button. I just thought to myself "huh, the battery must be dead" and put it to charge and the charging LED (as well as the charging screen with the "do not distribute outside htc blabla" dev screen) displayed so I just assume it's charging as per usual. Fast forward to about 1am, I have finished using my computer and decide to hop into bed. I go to turn on my phone by first powering down with power, vol up and vol down (as usual) and then try to boot the phone up. It boots as normal up until the O/S loading screen with a pac-man boot animation (I have PAC ROM installed) whereby it will freeze on the "game over" image of the boot animation and then proceed to go to a black screen. I thought to myself "hm, must be a mistake or something" and try it again to no avail. So I then go into recovery to do a fresh install and I try to wipe the phone and I do a factory reset in twrp, but upon trying to format data, the progress bar doesn't move (and so I left it overnight as I couldn't be bothered to wait). Upon leaving it overnight (1am to 7am) to format the data, I wake up to see that the progress bar hadn't moved at all from 0%. I then just thought "maybe the phone has actually formatted it but hasn't updated the image on screen so me being the dumbo I am, decided to force shut down the phone (with power, volup and voldown) and upon trying to boot the phone up again, it displays the HTC logo with the red writing, tries to boot into the O/S, fails, and then tries to boot into recovery and gets stuck in a boot loop (it will show the twrp logo and then a black screen, twrp logo and then black screen etc.). I have tried to flash twrp again (without first removing the twrp currently on it) but I was wondering what I could do in this situation. I am able to access the bootmenu (for hboot and fastboot) but nothing else.
TL;DR: I think I bricked my HTC One Mini 2. Came home, charged phone and phone got stuck at boot animation. Wiped phone in recovery, it got stuck on formatting data and now It can't boot into the O/S since it's wiped and it can't boot into Recovery for whatever reason.

DistincTHD said:
blah blah
Click to expand...
Click to collapse
This is not Facebook, go straight to the point.
Did you install a different kernel?

kativiti said:
This is not Facebook, go straight to the point.
Did you install a different kernel?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry for the confusion, I wasn't doing that because I couldn't/didn't want to explain, it's just a common message people get after dev unlocking their HTC phones. And no, It was working up until when I tried to use it last night randomly. I flashed PAC-ROM ages ago (like maybe 2-3 weeks ago or maybe even a month) with the HTC One M9 Camera Kernel and that's it. I then tried to use it last night and what I explained in the original post occurred.

DistincTHD said:
[IMG="HTC Dev Message"]
Sorry for the confusion, I wasn't doing that because I couldn't/didn't want to explain, it's just a common message people get after dev unlocking their HTC phones. And no, It was working up until when I tried to use it last night randomly. I flashed PAC-ROM ages ago (like maybe 2-3 weeks ago or maybe even a month) with the HTC One M9 Camera Kernel and that's it. I then tried to use it last night and what I explained in the original post occurred.
Click to expand...
Click to collapse
Oops, Just realised you meant the whole post, not just the blah blah bit within the post. But yeah what I did, I explained above and in the original post. I basically just told a story to give a better idea of what generally happened before the phone just pooped out on me.

DistincTHD said:
Sorry for the confusion, I wasn't doing that because I couldn't/didn't want to explain, it's just a common message people get after dev unlocking their HTC phones. And no, It was working up until when I tried to use it last night randomly. I flashed PAC-ROM ages ago (like maybe 2-3 weeks ago or maybe even a month) with the HTC One M9 Camera Kernel and that's it. I then tried to use it last night and what I explained in the original post occurred.
Click to expand...
Click to collapse
Something its corrupted so try to reinstall everything using the files from this post plus your choosen ROM.
When rebooting phone unplug USB cable.

kativiti said:
Something its corrupted so try to reinstall everything using the files from this post plus your choosen ROM.
When rebooting phone unplug USB cable.
Click to expand...
Click to collapse
I can't access twrp recovery but I do have fastboot enabled and working and I can access the boot menu so how would I go about wiping everything before re-flashing the recovery and then re-installing the o/s and everything else?

Just tried to first erase everything before installing and it's locking me out of the phone? It's telling me that an administrator console is unable to erase the system or its data so I'm quite stumped at the moment

DistincTHD said:
Just tried to first erase everything before installing and it's locking me out of the phone? It's telling me that an administrator console is unable to erase the system or its data so I'm quite stumped at the moment
Click to expand...
Click to collapse
you don't need to do all that.
try to flash twrp. (if OK use it to wipe everything)
If NOT ok flash stock recovery and unlock bootloader( yes again, this will wipe your phone and fix permissions)
Then you can do all you want.
Good luck.
let me know...

kativiti said:
you don't need to do all that.
try to flash twrp. (if OK use it to wipe everything)
If NOT ok flash stock recovery and unlock bootloader( yes again, this will wipe your phone and fix permissions)
Then you can do all you want.
Good luck.
let me know...
Click to expand...
Click to collapse
Right, so before I read that message, I flashed stock recovery and tried to reformat data and now It won't let be get into the boot menu and the HTC dev writing is gone (so I think it's locked again). On top of this, it just keeps booting into the reformatting data screen and just ends up hanging so I think I will let the battery drain or something (no idea how long it would take, probably days) and then try again from there. Pretty sure it is bricked now though lol welp. Is there any way to cancel a format?

Nexus 6 not turning on

Hello i bought a replacement screen for my phone about a month ago because everything was still working except the screen was broken from cracks. As i was about to replace the screen i noticed my phone is now not turning on at all even on charge. No red light, nothing. Is it possible the battery just needs to be replaced or is the phone completely dead?

Try charging it for a few hours on a low power charger like a computer USB port.
When the battery gets very depleted, it can have trouble taking a charge from a faster charger.

ktmom said:
Try charging it for a few hours on a low power charger like a computer USB port.
When the battery gets very depleted, it can have trouble taking a charge from a faster charger.
Click to expand...
Click to collapse
Hi, i tried to charge it using the PC but it didn't change anything. Would it be worth it getting a new battery to test if it still works?

I guess that's a decision you have to make. Is the expenses of the battery worth the risk that something else is wrong. It's possible the power button assembly has a problem. It's possible the USB port is worn, damaged or dirty.

Paperweight now? Having a different issue but potentially fatal??
My nexus 6 has been my faithful companion for many years, and now, though it is not my main phone, is used as my bedside companion for many uses. I boot it up one day and it gives some sort of "file encryption error" and then would not boot. I downloaded a fresh rom and adp to try to wipe it and just get it back to any working state, but nothing seems to work. What am I doing wrong?? (see photos attached)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

archos5005 said:
My nexus 6 has been my faithful companion for many years, and now, though it is not my main phone, is used as my bedside companion for many uses. I boot it up one day and it gives some sort of "file encryption error" and then would not boot. I downloaded a fresh rom and adp to try to wipe it and just get it back to any working state, but nothing seems to work. What am I doing wrong?? (see photos attached)
Click to expand...
Click to collapse
Let's start with some basics. It looks like the phone is stock (not bootloader unlocked).
What version was on the device before the problem?
Can you boot to recovery? (With the phone powered off, press and hold Volume Down, then press and hold Power)
Try sideloading an OTA the same as your current version. They are available on the Full OTA Images for Nexus and Pixel Devices page. The instructions there are solid.
If your not sure what was on the device, use the newest release.
Based on your photo, the device is not unlocked. You won't be able to Fastboot flash anything if you can't unlock it which requires the OEM unlocking to be enabled in developers options. Since you can't boot, you are stuck there.
It's quite possible the eemc has failed and the device is damaged.
BTW; your images are not showing up because the use of the IMG tag is wrong. There should not be anything inside the brackets with the tag (e.g. ="error"). The link does go between the opening and closing tags as you have it.
In the future, it also is a good idea to start your own thread, instead of burying a question inside a unrelated thread.

ktmom said:
What version was on the device before the problem?
pretty sure it is the latest (for that model) Android 7.1.1
Can you boot to recovery? (With the phone powered off, press and hold Volume Down, then press and hold Power)
I can get to the screen that shows the green android man lying with his compartment open. Is that recovery? It seems that everytime I try an option, it does not "do" anything. E.g., factory reset just won't let me do it. It just doesn't work [is this a symptom of emmc memory just being damaged? I know on PC's, a total reformat can isolate bad sectors...]
Try sideloading an OTA the same as your current version. They are available on the Full OTA Images for Nexus and Pixel Devices[/URL] page. The instructions there are solid.
I think I've followed that, (see the second picture) but again those commands don't seem to "do" what the commands usually should do. Like I need a tougher solution--willing to totally wipe everything and reformat and start anew, like a low level format.
Based on your photo, the device is not unlocked. You won't be able to Fastboot flash anything if you can't unlock it which requires the OEM unlocking to be enabled in developers options. Since you can't boot, you are stuck there.
It's quite possible the eemc has failed and the device is damaged.
I think I tried unlocking it, but same thing it didn't "work" either that, or I'm just doing it totally wrong [is it not the command "fastboot flashing unlock"??].
Click to expand...
Click to collapse
Thanks in advance. I just don't want to accept that it was working great one day and then turning it on the next day the flash memory is just TOTALLY bad, you know?

When a you boot to recovery, then get the "no command screen" press and hold Power then press and release Volume Up. If you can get to recovery, do a factory reset.
Unlocking the bootloader won't work unless you have already enabled OEM unlock in the developer options when booted to system. I said this earlier.
ADB won't work unless the kernel is booted. ADB only works when booted to recovery or fully booted to system.
Unless the bootloader is unlocked, Fastboot doesn't get you anything.
If you get to recovery and a factory reset doesn't solve your problems, do an OTA sideload using the link I gave you before.
Please Do Not bury your comments within the wipe of someone else's post. It makes it impossible to follow the conversation. Just respond below the quoted post.

Stuck on BOOTLOOP without RECOVERY and can't access FASTBOOT

I am having Nokia 8 TA-1004. I had the same issue as many of them. The phone restarts often whenever I open an app or start interacting with UI. It was so frustrating. But it was find when I am using it while charging. And there is absolutely no problem in it. Many of them were confused whether it is motherboard issues or update issue becuz the problem started only after Feb security update that came last year. Since then I was struggling and I gave up.
Today I had an idea of using custom rom to see whether the problem can be fixed. I searched for custom roms officially there I none. But I got a Pixel Experience Rom, unofficial ofcourse. So I went on with unlocking the bootloader so I followed the official steps and unlocked it. While installing TWRP I was but confused with it becuz it needs to be booted with recovery.img temporarily and flashed with recovery.zip in TWRP.
I wrote the command :
fastboot flash recovery recovery.img it just failed.
I wrote : fastboot boot recovery.img but nothing turned up when I went to recovery mode.
But in one article I found a command :
fastboot flash boot recovery.img
It booted to twrp but I was unaware that I flashed it instead of boot.img and I can't acces MTP to tranfer file to my phone. So I try to boot into os and copy the recovery.zip so that I could install it. But that's it. It went into BOOTLOOP. I can't access the fastboot nor recovery. It just vibrates startes shows powered by Android and loops this. I tried everything to enter fastboot or recovery, if I get atleast one shot of recovery or fastboot I could bring it back.
It loops again and again switches on shows "powered by Android" switches off that's it. I will be so pleased if some have some sort of solution. It will be great to hear suggestions about it.
Thanks in advance.....

You have fallen victim to the A/B partition scheme. It is correct that the TWRP image needs to be first booted with fastboot and from there the .zip file must be flashed. This is because in A/B devices there is no recovery partition (that is why the command "fastboot flash recovery recovery.img" failed). The recovery instead lives in the boot partition together with the kernel. By typing "fastboot flash boot recovery.img" you essentially have deleted the kernel of the device which causes the bootloop. I would suggest you to read this xda article which will help you understand the details: https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/ .
Now the only way to fix this is to repair the boot partition of the phone. This can be done with a tool known as NOST: https://github.com/StollD/NOST . (Note that you will lost all of your data with this method so keep this in mind). Once you have downloaded the tool you need to get a complete Nokia 8 firmware image. The one that worked for me was this: https://github.com/resident-nokia/t-virus/releases/tag/5150-revert . Once you have both installed, launch NOST, follow the instructions and select the firmware file. On the screen after that, click the arrow down button next to "Normal Download" and tick the box labeled as "Erase User Data". Now to proceed you must enter download mode. This is a bit tricky in your current situation but it can be done in 2 ways:
1. Wait until your battery dies down. Then hold down the volume down button and connect the phone to a computer.
2. (Bit tricky to pull off and I managed to do it) Hold down the power button until the screen goes black. Then immediately hold down the volume down and connect to a computer.
Once you are in Download Mode disconnect and reconnect the phone to the computer and click the Next button in NOST. If all goes well this will repair your partitions and boot you back to the stock rom.
Hope this helps.

emufan4568 said:
You have fallen victim to the A/B partition scheme. It is correct that the TWRP image needs to be first booted with fastboot and from there the .zip file must be flashed. This is because in A/B devices there is no recovery partition (that is why the command "fastboot flash recovery recovery.img" failed). The recovery instead lives in the boot partition together with the kernel. By typing "fastboot flash boot recovery.img" you essentially have deleted the kernel of the device which causes the bootloop. I would suggest you to read this xda article which will help you understand the details: https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/ .
Now the only way to fix this is to repair the boot partition of the phone. This can be done with a tool known as NOST: https://github.com/StollD/NOST . (Note that you will lost all of your data with this method so keep this in mind). Once you have downloaded the tool you need to get a complete Nokia 8 firmware image. The one that worked for me was this: https://github.com/resident-nokia/t-virus/releases/tag/5150-revert . Once you have both installed, launch NOST, follow the instructions and select the firmware file. On the screen after that, click the arrow down button next to "Normal Download" and tick the box labeled as "Erase User Data". Now to proceed you must enter download mode. This is a bit tricky in your current situation but it can be done in 2 ways:
1. Wait until your battery dies down. Then hold down the volume down button and connect the phone to a computer.
2. (Bit tricky to pull off and I managed to do it) Hold down the power button until the screen goes black. Then immediately hold down the volume down and connect to a computer.
Once you are in Download Mode disconnect and reconnect the phone to the computer and click the Next button in NOST. If all goes well this will repair your partitions and boot you back to the stock rom.
Hope this helps.
Click to expand...
Click to collapse
hey, the same thing has happened with my realme c2. I tried to install gsi in it but ended but making it go into boot loop into recovery mode and there is no recovery in it so it keeps on turning off and then restarts and goes into recovery mode again. I can't even access fastboot mode. how to solve this?

Sathvk KVS said:
hey, the same thing has happened with my realme c2. I tried to install gsi in it but ended but making it go into boot loop into recovery mode and there is no recovery in it so it keeps on turning off and then restarts and goes into recovery mode again. I can't even access fastboot mode. how to solve this?
Click to expand...
Click to collapse
Unless you erased the recovery partition yourself, the recovery still exists. Try completely shutting off your phone (waiting for the battery to drain, or pressing the power button for an extended period of time, I don't know the key combinations for your Reame C2) and then enter fastboot mode to fix up the partition that were messed up

emufan4568 said:
Unless you erased the recovery partition yourself, the recovery still exists. Try completely shutting off your phone (waiting for the battery to drain, or pressing the power button for an extended period of time, I don't know the key combinations for your Reame C2) and then enter fastboot mode to fix up the partition that were messed up
Click to expand...
Click to collapse
I have the same problem on a redmi 9 after flashing twrp BUT only partition A

emufan4568 said:
Unless you erased the recovery partition yourself, the recovery still exists. Try completely shutting off your phone (waiting for the battery to drain, or pressing the power button for an extended period of time, I don't know the key combinations for your Reame C2) and then enter fastboot mode to fix up the partition that were messed up
Click to expand...
Click to collapse
cant enter fastboot with key combinations or any other? if i plug in usb it just starts the bootloop again?

smiley.raver said:
cant enter fastboot with key combinations or any other? if i plug in usb it just starts the bootloop again?
Click to expand...
Click to collapse
yep, the guy from service tries to rewrite the motherboard now

Officer X said:
yep, the guy from service tries to rewrite the motherboard now
Click to expand...
Click to collapse
Wat happened actually. I wanted to get my phone serviced, but im scared of the price to repair. They said if the chip still can receive data they will try repair it. But if the it broken, they have to repair the motherboard. IM SCARED THO.

LeBronLaS said:
Wat happened actually. I wanted to get my phone serviced, but im scared of the price to repair. They said if the chip still can receive data they will try repair it. But if the it broken, they have to repair the motherboard. IM SCARED THO.
Click to expand...
Click to collapse
LeBronLaS said:
You might as well tinker around with it my phone did that same thing it didn't have fastboot and computer couldn't see it through ADB drivers but I kept messing with it and kept flashing it and I got it back
Click to expand...
Click to collapse

Oppo Stock ROM
Find Oppo and Realme Stock ROM (Firmware) for various Oppo/Realme Devices. All the Oppo/Realme Firmwares listed are available for free.
oppostockrom.com
This website has real me and Oppo 0FP files

hi evreyone
i have same problem with my galaxt tab s6, Do You have any solution ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

emufan4568 said:
You have fallen victim to the A/B partition scheme. It is correct that the TWRP image needs to be first booted with fastboot and from there the .zip file must be flashed. This is because in A/B devices there is no recovery partition (that is why the command "fastboot flash recovery recovery.img" failed). The recovery instead lives in the boot partition together with the kernel. By typing "fastboot flash boot recovery.img" you essentially have deleted the kernel of the device which causes the bootloop. I would suggest you to read this xda article which will help you understand the details: https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/ .
Now the only way to fix this is to repair the boot partition of the phone. This can be done with a tool known as NOST: https://github.com/StollD/NOST . (Note that you will lost all of your data with this method so keep this in mind). Once you have downloaded the tool you need to get a complete Nokia 8 firmware image. The one that worked for me was this: https://github.com/resident-nokia/t-virus/releases/tag/5150-revert . Once you have both installed, launch NOST, follow the instructions and select the firmware file. On the screen after that, click the arrow down button next to "Normal Download" and tick the box labeled as "Erase User Data". Now to proceed you must enter download mode. This is a bit tricky in your current situation but it can be done in 2 ways:
1. Wait until your battery dies down. Then hold down the volume down button and connect the phone to a computer.
2. (Bit tricky to pull off and I managed to do it) Hold down the power button until the screen goes black. Then immediately hold down the volume down and connect to a computer.
Once you are in Download Mode disconnect and reconnect the phone to the computer and click the Next button in NOST. If all goes well this will repair your partitions and boot you back to the stock rom.
Hope this helps.
Click to expand...
Click to collapse
Thanks, I´ts served for me the second option.

So I made the fatal mistake of trying to flash the cfdroid rom for android 12. I failed to realise that I needed T-Virus 2.0 for it to work. I already had T-Virus 1.0, but using TWRP, I wiped out the current Android 9 custom Rom I was running. The flashing of the new one obviously failed, but now im stuck in a bootloop and can no longer boot into recovery at all. I tried letting the phone die but as soon as it gets power again it enters the boot loop and wont eve boot into download mode no matter the key-combination. I am trying to flash T-Virus 2.0 on my linux machine but it if it cant even boot into download mode then it seems I am doomed. The phone has been sitting and practically dead for 2 weeks now. Anyone got any suggestions? I'm running out of options to try.
EDIT: Okay, I managed to get to download mode after posting this. But I am getting a `<Waiting for any device>` message using the `flash_T-Virus_Linux.sh` script. Seems like the phone is not picked up.
EDIT2: I decided to run the script as root and it is now stuck at
Code:
Flashing T-VIRUS partition-table
Sending 'partition:0' (44 KB)
EDIT3: It finally worked. I basically had to unplug the phone, turn it off again and make sure I run the `flash_T-Virus_Linux.sh` script using root privileges. Now I can boot into the phone with a Pixel Experience rom.
I am so rusty, the last time I modded this phone was when Android 9 was a thing.

Thanks so much, Amazing, It work!!! cororectly explained, thanks!!
You know a twrp for Redmi Note 9? I need to unloock again, but i want to set custom rom, because the stock room have problems. If you know letne know please, thanks again

Have the Sam for my older Tab A 10.1 (T510). Flashed an updated TWRP, rebooted, now it keeps rebooting. Powerbutton nor volumes up and down don't work. Just rebooting rebooting...hioefukky when battery goes empty, I can try stuff.

My infinix note 12 g96 is stuck in boot loop saying damage state your device has been locked and can’t be trusted and Just keeps restarting
I recently unlocked the boot loader and immediately rooted using a flashed boot image of the phone I flashed with magisk
I didn’t restart after unlocking and now it’s stuck in boot loop and I can’t enter recovery mode with the hardware keys please I need help

Rayde101 said:
My infinix note 12 g96 is stuck in boot loop saying damage state your device has been locked and can’t be trusted and Just keeps restarting
I recently unlocked the boot loader and immediately rooted using a flashed boot image of the phone I flashed with magisk
I didn’t restart after unlocking and now it’s stuck in boot loop and I can’t enter recovery mode with the hardware keys please I need help
Click to expand...
Click to collapse
me too i have the same problem with my infinix note 12 g96
Please let me know if you've fixed yours i need help

Sounds like u need to flash stock rom, or somhow update with earlier firmware