Ok so, I flashed a CM13 rom on a K4 Note (16GB internal and 3GB ram version). I pretty much followed all the steps required for flashing - unlocked bootloader - installed TWRP - wiped (factory reset) - flashed the Rom. Now, the phone booted up alright and worked for a day. The phone doesn't belong to me, and the owner decided that he wanted to factory reset it one more time. Since I also wamted to show him how TWRP functions, I booted into recovery via the advanced boot option in Cyanogen (Did not use the key combination). So this phone turns off and decides not to start. I waited for some time and decided to manually power it up. It won't. I held down the key for about 5 minutes and yet, to no avail. Not even a vibration. No response at all.
So, I would like to understand what happened with the phone, since as far as I can tell, TWRP was working fine. I used the key combo method to boot into TWRP thrice the night before - to flash CM, to flash gapps and to flash thr xposed installer. I can say CM was working fine since I used it for a night to get a hold of any bugs. Nothing went wrong at that time.
So, what can I do now? Since the phone is completely unresponsive and is not being detected upon being connected to the PC, I suppose it's hard bricked. But what cause the brick in the first place? Any possibe way to recover the phone? Is it even hard bricked though?
What about battery charging % frist chik battery I think battery fult
Sent from my GT-I9505 using Tapatalk
Nah, it doesn't charge either. I tried plugging it in and turning it on. It still won't.
It's just sitting there. Doing nothing.
Related
Hi all,
well, to be honnest I already posted my story in the help thread but no answer came so I try with a new thread
We'll see if I'm luckier this way !
a few weeks ago I broke my screen and decided to change it myself.
Everything went fine (even restarted successfully my phone before applying the tape to fix the screen) until I finally tried to restart my phone after the repair is done.
Since then I'm not able to turn on my phone
Holding the power button starts fastboot mode, UP + power doesn't do anything and DOWN + power enters recovery. Weird !
Another weird thing: it only works if I'm not plugged. When I'm plugged nothing ever happens.
I suspected I could have damaged buttons or cables. I have looked carefully but nothing appears to be broken.
Here is what I already did without any result:
- I had access to the original recovery so wiped the cache
- I tried to recover the phone but that did not work so
- I installed twrk using adb (like here)
- and then installed the rom as explained here (I used the last release here, so it should be cm-13.0-20160819-SNAPSHOT-ZNH5YAO0IN-bacon.zip). It seemed to work but finally no, same situtation
- I tried this but so far not able to get the qualcomm port listed once the phone is on. It may be related to the fact that I have to unplug to boot it but I always got a Android bootloader interface listed.
Any idea someone ?
Thank you very much for your help !
Did you try to "fastboot reboot" while in fastboot mode?
Try flashing a CM14 rom. Mine came with CM12 so I tried flashing back to CM11 and I did flash it successfully through Fastboot but alas it won't boot. The boot logo loads but then I'm introduced to a black screen.. So I flashed back to a (at that time the latest stable) CM12.1 but same result. And I got worried. Then I decided to flash a CM13 rom which was a beta build (at that time newly released Android 6) and it booted into it alright! So I suggest flashing a CM14 and let me know how it does.
The problem seems be much deeper than just a broken screen. It may sometime affect the chipset of the cellphone.
For that we can't do anything.
For now you can try the following things :
1 . Flash the latest Cyanogen Firmware from the same place you have downloaded the snapshot cm13.
2. Flash recovery (TWRP) using adb.
3. Wipe
-System
-Data
-Cache and Dalvik Cache
4. Flash the latest Cyanogen Rom .
5. Boot into recovery.
6. Flash some gapps as per the Android version.( Open Gapps I recommend)
7. Boot back to recovery .
8. Boot into System.
This is the max you can do for now.
You can also check device forums for recovering from a bricked device post.
Go through the post and check if any symptoms matches yours. You'll find the answer right away.
And the last option you can do is going to service center, they will charge you mostly (even if in warranty as you have yourself tampered hardware of the phone.)
Hope it will help. Thanks
When I got my replacement tablet for the recall, I followed the instructions to kill the kill switch on my old tablet (a 16gb Wifi only version). I deleted the TegraOTA folder, and used the zip file as well. I then installed BlissPop and have left it that way since.
A few days ago, I decided to switch from the now-defunct BlissPop over to LineageOS. For some reason, I couldn't get the tablet to boot into recovery (I installed the TWRP app, wouldn't boot into TWRP; I flashed TWRP using fastboot, wouldn't boot into TWRP; I flashed Nvidia's stock recovery, still wouldn't boot into recovery).
So I decided to flash stock, but new everything (I think the 5.2 or 5.3 version). Booted into OS setup (without connecting to network) so I could enable debugging/connect with ADB. This worked, so I rebooted into bootloader and finally got into TWRP. But, because of shared storage, I couldn't get into system folder to see if TegraOTA was back. So I decided to go back to original stock so I could access internal storage. Performed a factory reset, flashed the very original stock system/recovery/boot from these forums.
Restarted tablet and... nothing. Black screen. When its plugged in, the light shows it has charging, but no amount of time or effort pressing the power button will get it to do anything.
Did I brick it somehow? I've flashed various upgrades, OTAs, custom ROMs on both Shield Tablets I've had and am 99.99% sure that I didn't do anything wrong this time. Did I unknowingly flash something that would allow the kill switch to be thrown even if the tablet was never connected to my network? Is there any way to test? Basically I want to be certain its 100% done for before I toss it and buy a new tablet (I sold my replacement earlier this week, which is why I decided to upgrade the old one in the first place). Thanks in advance for any help!
If you installed latest stock and system detected tablet with bad battery it probably killed itself even if you did not connected it to internet
Hi, it is an older device so you might have experienced everything possible.. so,
After a long time of trying to fix that phones mind, I wiped everything avaible in TWRP
multiple times(got mad). Last thing was data.
That way I went from a bootloop to an active nothing.
Phone does not react to any command, it does not react to USB charging or on PC.
That's the case a few months back, the phone halfway in the trash and I bought
myself a iphone (hate it).
I put the Galaxy S7 on a charger today and it starts immediatly in to TWRP.
From there I tried to install a ROM that's left on the SD card, which forced
a restart into TWRP. Into download mode I managed to install the stock Oreo ROM via Odin.
It went through like a charme, all green. PASS!
The phones screen is black and does not react to any command, nothing.
I had "auto-reboot" activated.
The phone is active it's warm and I'm waiting for the battery to die again, to restart.
..meanwhile,
Can you give some advice please?
Why would the phone have struggle with the boot with stock rom installed.(which has worked before,no updates installed)
When should I install TWRP?
When do I install what kernel?
Last thing running was the LightROM with moro kernel with nothing tweaked.
Also. The issue why i deaded the phone was a camera/flash thing, where I could only take pictures with flash activated.
Front and back camera. On all camera apps, I couldnt scan my ID for banking due to that.
Also on different kernels and different ROMs including the Samsung stock.
Why would that be
Could not accept...
Jvers said:
Hi, it is an older device so you might have experienced everything possible.. so,
After a long time of trying to fix that phones mind, I wiped everything avaible in TWRP
multiple times(got mad). Last thing was data.
That way I went from a bootloop to an active nothing.
Phone does not react to any command, it does not react to USB charging or on PC.
That's the case a few months back, the phone halfway in the trash and I bought
myself a iphone (hate it).
I put the Galaxy S7 on a charger today and it starts immediatly in to TWRP.
From there I tried to install a ROM that's left on the SD card, which forced
a restart into TWRP. Into download mode I managed to install the stock Oreo ROM via Odin.
It went through like a charme, all green. PASS!
The phones screen is black and does not react to any command, nothing.
I had "auto-reboot" activated.
The phone is active it's warm and I'm waiting for the battery to die again, to restart.
..meanwhile,
Can you give some advice please?
Why would the phone have struggle with the boot with stock rom installed.(which has worked before,no updates installed)
When should I install TWRP?
When do I install what kernel?
Last thing running was the LightROM with moro kernel with nothing tweaked.
Also. The issue why i deaded the phone was a camera/flash thing, where I could only take pictures with flash activated.
Front and back camera. On all camera apps, I couldnt scan my ID for banking due to that.
Also on different kernels and different ROMs including the Samsung stock.
Why would that be
Could not accept...
Click to expand...
Click to collapse
OK so what you've done is correct flashing stock (which includes stock kernal). You have to make sure the stock ROM is correct for your device and region or it will not start.
It's not unusual to have to flash it twice with Odin.
Next up you don't need to wait for batt to die to restart. Press volume down+home+power and keep them pressed until phone restarts. Should now be in download mode, reflash correct ROM with Odin. TWRP is wiped off the phone when you flash a stock ROM.
If it doesn't go through the boot up/freezes/ does nothing etc. You need to "wipe cache" then reboot from the recovery menu.
Press and hold volume down+home+power. As soon as the screen goes black move your finger to volume up (it may take more than one attempt). Once your in recovery menu use volume up and down to move through options and power to execute. Wipe cache then reboot and allow the phone to go through all the reboot stuff. It can take a few minutes just leave it alone. It will also reboot a couple of times.
If it does nothing after 15 minutes then start again and repeat the process.
Thanks for reply.
The Phone was off for a day and after charging for 1h it still does not react to any command. Vol down + home + power does nothing. Same with vol up.
Is there a way to force a boot? Even if the PC does not recognize a device on usb?
I Tried the commands 30 secs each, plugged in and off. Also usb port is not broke since the phone is getting temperature after a while charging..
Hi everyone.
Last night my phone ran out of power and when I charged it back up it wouldn't boot at all, so this morning I decided to try and fix it but I think I have just screwed it up even more to the point that its completely bricked.
I could still access TWRP and tried to reinstall the firmware and flash TWRP through the checkbox execpt about 1 minute in the screen went off due to the time out, but the screen wouldn't come back on at all so I left it for an hour just in case if it was still running in the background, after this time I hard restarted the phone and entered TWRP again and but it didn't install the firmware properly and my computer wasn't reading the phone properly so as a test I tried to swap bootloader from A to B stupidly and now I can't seem to access anything, only thing I can do is the menu where it says start, power off, recovery mode and restart bootloader. Pressing any of these settings seems to just put me back in to this menu again.
When plugging in the phone in to the PC it make's no noise at all as well.
Have I completely hard bricked my phone? Or is there a way to fix it?
Thanks Ben
All fixed I flashed the RAW firmware
Hey,
I have got Xiaomi POCO X3 PRO NFC 8/256GB, most probably have android 11 MIUI 12.5.5 global, in EU. Been using automatic updatese. Please note, that I haven't flashed any custom software. Have been using vanilla OS since release and been updating it with automatic updates.
Suddenly my phone has entered bootloop state and I am not able to take it out of it since.
Latest action I have taken just before the problem started is that I connected my phone to charger during the game ( PGR) , while it was at around 40% charge. After short moment it has frozen and restarted the phone. Since then it has been constantly bootlooping with POCO icon and resetting again, turning off the screen and back to POCO icon - it has been for over 2 hours already. It doesn't feel that my power button is stuck.
Still can operate power + vol buttons reliably. I can access Fastboot and MIUI Recovery Menu 5.0, where I have 4 options:
1. Reboot - back to bootloop
2. Wipe data - haven't tried it yet
3. Connect to MIAssistant - TIL it is supposedly dead service?
4. Safemode - it brings me back to bootloop again
Tried to take out SIM and microsd, to no avail. Haven't tried to wipe out data until I try other solutions, to restore it, as I have some 2FA on it, which would be a pain to recover.
I haven't learned before around flashing and recovery for the last few years (only I have done it around android 4, 5 and 6). I would like request assistance - how to approach resolving this problem?
Currently I am reading on fastboot, which I believe might help me here, by connecting it to PC.
EDIT: Got around this https://xiaomiflashtool.com/tutorial/use-xiaomi-flash-tool and stock rom https://xiaomistockrom.com/xiaomi-poco-x3-pro , I believe it might work
EDIT #2: At 20.11.2022. At around end of october this issue started repeating out of nowhere. And then suddenly stop,
Then the phone bricked. Sent for warranty and just got it back.
Turns out that motherboard died and was the cause.
gol_galad said:
Hey,
I have got Xiaomi POCO X3 PRO NFC 8/256GB, most probably have android 11 MIUI 12.5.5 global, in EU. Been using automatic updatese. Please note, that I haven't flashed any custom software. Have been using vanilla OS since release and been updating it with automatic updates.
Suddenly my phone has entered bootloop state and I am not able to take it out of it since.
Latest action I have taken just before the problem started is that I connected my phone to charger during the game ( PGR) , while it was at around 40% charge. After short moment it has frozen and restarted the phone. Since then it has been constantly bootlooping with POCO icon and resetting again, turning off the screen and back to POCO icon - it has been for over 2 hours already. It doesn't feel that my power button is stuck.
Still can operate power + vol buttons reliably. I can access Fastboot and MIUI Recovery Menu 5.0, where I have 4 options:
1. Reboot - back to bootloop
2. Wipe data - haven't tried it yet
3. Connect to MIAssistant - TIL it is supposedly dead service?
4. Safemode - it brings me back to bootloop again
Tried to take out SIM and microsd, to no avail. Haven't tried to wipe out data until I try other solutions, to restore it, as I have some 2FA on it, which would be a pain to recover.
I haven't learned before around flashing and recovery for the last few years (only I have done it around android 4, 5 and 6). I would like request assistance - how to approach resolving this problem?
Currently I am reading on fastboot, which I believe might help me here, by connecting it to PC.
EDIT: Got around this https://xiaomiflashtool.com/tutorial/use-xiaomi-flash-tool and stock rom https://xiaomistockrom.com/xiaomi-poco-x3-pro , I believe it might work
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
NOSS8 said:
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Click to expand...
Click to collapse
Thanks, will follow this to make back up and in case it occurs again.
Managed to resolve this problem by draining up my battery due to constant restarts(obviously can't pull out battery). After that happened, connected my phone to normal charger, juiced it up to 10% and phone started just fine.
I have tried to recreate this problem, however it didn't occur again.