Basically i had already made all the """dangerous""" things and managed to not brick the phone, i had twrp, magisk and a miui 10 Rom
but for some reason i still can't figure out the phone just decided on itself to shutdown and get the red notification led (when i plug it to anything)
at first i thought it was something related to the battery but after letting it charge and still having nothing to happen i decided to search and found out that this red led means its bricked.
and i was actually fine with that since i have another phone (xiaomi redmi note 4x) that i could use, but i really just prefer this one.
I already tried to unbrick it with the method that has already been posted here (link) but after the thing with "Write memory" it just keeps not turning on with the red led.
What should i do?
Is there any other method that i can try? if so, can someone please give me a link?
I've already tried following 3 videos of the unbrick (2 were the same and the other just changed the order of changing the "Download-agent" to DA_BR after or before the "Write Memory" step) and doesn't seem to work
i thought it may be something to do with the fact that i had this custom rom? (Miui 10 01.09.2018 from tickernel)
Please help me, this is my daily driver and i just love this phone.
Related
Hi all,
This is my first post on XDA, but have found it useful in the past when needing info for my original G1 and later my HTC Desire, both of which I rooted and added custom roms on via the threads here.
Now though I am really stuck having cocked up an attempt to install Cyanogenmod 10.2 on my 4X HD.
I have a black screen with red text saying "Stuck on Critical Failure:Unable to start Kernel." and a few more lines.
I initially followed a guide at AndroidLegend but because the links in this guide went to Nightly's for 10.2 I decided to download a stable 10.1 instead. I can't post the link but the comments show the problems I was having.
The end result was that I never managed to install 10.1 and had just gone back to the original factory settings, but along the way on another forum I saw someone mention that the ROM may have the original phone name wrong and to take out the assert name in a config file, which I did (now knowing that that was the last thing I should have done). So upon rebooting I ended up where I am now.
I have searched thoroughly on these forums and have tried numerous fixes none of which none have been successful.
The one that I feel comes closest is this one by RuedasLocas (post number 7) on "Rollback Optimus 4X HD from 4.1.2 JellyBean to 4.0.3 Stock ICS"
I've followed it exactly and tried 3 or 4 times on different PC's and although I can see the phone in Device Manager and change port settings (LGE CDMA USB Serial Port to 41) etc, I never get beyond LGFlash Tool changing from "waiting" to anything downloading in Blue or failing in Red, nothing happens and my phone will just sit there in SafeMode whilst plugged in.
Can anyone suggest anything else that I need to do?
Many thanks if you got this far!
Snookered said:
Hi all,
This is my first post on XDA, but have found it useful in the past when needing info for my original G1 and later my HTC Desire, both of which I rooted and added custom roms on via the threads here.
Now though I am really stuck having cocked up an attempt to install Cyanogenmod 10.2 on my 4X HD.
I have a black screen with red text saying "Stuck on Critical Failure:Unable to start Kernel." and a few more lines.
I initially followed a guide at AndroidLegend but because the links in this guide went to Nightly's for 10.2 I decided to download a stable 10.1 instead. I can't post the link but the comments show the problems I was having.
The end result was that I never managed to install 10.1 and had just gone back to the original factory settings, but along the way on another forum I saw someone mention that the ROM may have the original phone name wrong and to take out the assert name in a config file, which I did (now knowing that that was the last thing I should have done). So upon rebooting I ended up where I am now.
I have searched thoroughly on these forums and have tried numerous fixes none of which none have been successful.
The one that I feel comes closest is this one by RuedasLocas (post number 7) on "Rollback Optimus 4X HD from 4.1.2 JellyBean to 4.0.3 Stock ICS"
I've followed it exactly and tried 3 or 4 times on different PC's and although I can see the phone in Device Manager and change port settings (LGE CDMA USB Serial Port to 41) etc, I never get beyond LGFlash Tool changing from "waiting" to anything downloading in Blue or failing in Red, nothing happens and my phone will just sit there in SafeMode whilst plugged in.
Can anyone suggest anything else that I need to do?
Many thanks if you got this far!
Click to expand...
Click to collapse
when you get to "waiting", plug out your cell phone, eject battery, put the battery back in and hold vol - while plugging it back into comp. lgflashtool should then recognise the device and start flashing.
another thing you can do is use kdz flasher, which has a bit easier interface when compared to lgflashtool.
Many thanks for the speedy reply Flying_Bear, possibly seeing some success, did as you said and a file downloaded to the device, however I am now seeing the image that I have attached.
It looks like it's saying don't remove cable and don't switch off and refresh?
Can you confirm what I should do next?
Thanks again
Snookered said:
Many thanks for the speedy reply Flying_Bear, possibly seeing some success, did as you said and a file downloaded to the device, however I am now seeing the image that I have attached.
It looks like it's saying don't remove cable and don't switch off and refresh?
Can you confirm what I should do next?
Thanks again
Click to expand...
Click to collapse
hmmm, truth to be told, i dont remember seeing that image appear when using lgflashtool. also, i've never seen anyone with similar problem to yours (unable to start kernel)
did you give it some time? if it didnt work, try http://forum.xda-developers.com/showthread.php?t=2069723; it's similar to lgflashtool, but no need to set up ports, and you can track the progress while it's flashing (lParam=x on pictures). try 20a kdz file, if that fails, report here with some more info on what the problem was. hope we can fix things for you
also, can you post the link on tutorial you followed to flash cm, just so i can check what steps you have done? just remove http from the link if you cant post it
Flying_Bear said:
hmmm, truth to be told, i dont remember seeing that image appear when using lgflashtool. also, i've never seen anyone with similar problem to yours (unable to start kernel)
did you give it some time? if it didnt work, try http://forum.xda-developers.com/showthread.php?t=2069723; it's similar to lgflashtool, but no need to set up ports, and you can track the progress while it's flashing (lParam=x on pictures). try 20a kdz file, if that fails, report here with some more info on what the problem was. hope we can fix things for you
also, can you post the link on tutorial you followed to flash cm, just so i can check what steps you have done? just remove http from the link if you cant post it
Click to expand...
Click to collapse
It's working!
Just read your reply and as I wanted to wait to see what you might say I left the phone alone, so it was still attached to the pc showing that image.
I then unplugged it, held the power button down to power it down and then back on again, image of the android came up for a second showing as though it was updating, then the LG logo and then Setup started.
5 minutes later wifi and 3G were working and I was logged into Google.
So problem solved!
I'll hang back from updating further until I've read up more on XDA....thanks so much for your help though!
Hello! Hope you guys can help me out sorting my problem with Mi5 Pro.
A friend of mine hard bricked the phone during flashing. No response whatsoever, phone totally dead. I managed to recognize it by PC via test points (showed Qualcomm QD-Loader 9008).
- installed succesfully fastboot rom Latest Global Stable via newest version of MiFlash (i was unsuccessfull with old version).
- it was a clean installation, wiped everything and everything went smooth,
but for some reason my screen is totally black. When i plug it into a wall charger it lights up first red light, then after a while green. I was thinkig it shows signs of life, but the screen no matter what i do is still black.
I can enter into fastboot (pwr + Vol-) but screen is always black.
I tried flashing via EDL mode, fastboot mode and non-work (always succesfull, but screen is always OFF).
I tried latest global and latest developer china version.
It seems that it has a bootloader unlocked because i tried flashing twrp via adb and it was ok, but i can't do anything because i cant see what i am doing on screen which is always black.
Is there anyway to revive this phone. HELP!!!!!!!!!!!!!!!
Bad stuff.
My only idea at the moment is to try to plug the phone to a TV via HDMI cable using an adapter like this.
you may Have Touched the screen cable creating few microfracture, i think. you can open the phone and try to un-plug and plug screen flat. you've already opened the phone, so it can not hurt.
Tried it already, doesn't work.
Fortinho. Ordered the cable today.
I have another Mi5 new one. Do you think guys would it harm if i swithced the motherboard to a new one, which i am sure screen and battery are fine?
I am kinda bit afraid not to burn anything on the new when i plugg the mbo from faulty one.
I had this problem,
I flash the latest MIUI ROM CHINA with Miflash, after the global, and i reflash the China and working for me
mrsachou said:
I had this problem,
I flash the latest MIUI ROM CHINA with Miflash, after the global, and i reflash the China and working for me
Click to expand...
Click to collapse
So. tell me exactly. Didn't quite understand.
China rom - global rom - china rom
or
just china over global?
i got the same problem can someone help me please
Tenta usar a ROM da europa, talvez ajude
same problem..black screen of death !!! duh !!
Hey stomas30,
I know it might be too late, but someone might have this problem, so here is the possible solution.
The first time I flashed my Mi5 (quiet long time ago), I flashed the wrong TWRP by accident from MIUI mi5/Pro forum. I assume that I flashed mi5Pro TWRP by accident, so my screen went completely black (dark), while phone was functioning well (could charge, hear the sounds, launch recovery/fastboot). I couldn't find any possible solutions, and I gave up.
After that I decided to flash another Recovery (latest TWRP) for Mi5, and I was still unable to launch the screen.
So the solution is to flash the first ever released TWRP for Mi5, and then update to the latest TWRP.
Do it on your own risk, yeah...
Hope it helps,
Max.
P.S. sorry for too much background information.
Max was right!
Hey!
I know too that maybe is too late, but I had the same problem and Maxim Zaika is ****ing damn right!!
I have downloaded the first TWRP+ROM from XIAOMI.EU (MiFlash_xiaomi.eu_gemini_6.4.21_6.0), flash it via MiFlash tool and now my Xiaomi has come back to life!!
After that I will reflash with the latest MIUI 9 and I hope it will be work right again!
Thank you very much Max!
PS1: All the process are explained in spanish in a YouTube video (Instalar TWRP+ROM Xiaomi.eu en Xiaomi MI5 bootloader desbloqueado)
PS2: Google the words in brackets to find de ROM and the YouTube video, this is my first post and I can't post outside links)
All credits for de youtuber Alberto Moyano aka moyano92.
Did you end up figuring out a fix for this? Just took the back off, replugged the battery into the motherboard and I can see a red LED, which is an improvement from no LED. Going to charge it all night and hope for the best
So I did a big mistake,I tried too many custom roms and I think I messed up my phone. My current custom rom is Resurrection Remix.
Few days ago my phone was having a weird problem,my recovery was gone,and the phone's screen turned black after 2 mins of booting up.However this issue solved automatically,I reinstalled recovery. ( I should have reflashed the custom rom,but I didn't:crying The settings was still missing,but I ignored it as there was not much use of settings.
Fast forward to today's morning , the phone was at 7% I don't know what I thought but I decided to give it a reboot.AND now my phone is not starting(It's not bootloop ,the phone is not even starting up).The battery is not charging up(It's very difficult to get new battery for Nokia X2,that would be the last thing I'd want to do,that or either buying a new phone)
.There is no light,no vibration whenever I connect my charger.I got my charging socket changed but nothing is working.I think it's a software issue.
Please is there anything I can do to recover my phone? Anything?:crying:
make sure your battery is ok and charged.
then try to flash the phone using pc with "nokia x2 tools" and a custom ROM and recovery
Hello everyone. I updated my rooted OP3T (with TWRP installed for recovery) to OOS 4.0.1(I think? I know for sure it was 4.0.x) a week or so ago using a VPN as I live in the US and today I got the new update for whatever version that was about 30 mb, and after I rebooted I got stuck booting into TWRP so I followed the guide linked underneath here and got up to step 12 (flashing beta 9) and after swiping to restart my phone will not turn on in any way, shape, or form. Whenever I plug it in/unplug it from my computer I'll still get the Win10 device connected/disconnected sound and if I hold the power button for long enough while it's plugged in I'll get another device connected sound or disconnected, usually followed by the opposite sound. There doesn't seem to be a pattern to the sounds, but if anyone knows what's happening I really need help with this as it's the only phone I was able to afford and if it's bricked I don't know if I have the money for another one. Thanks
https://forum.xda-developers.com/showpost.php?p=70102813&postcount=5
Lol no wonder your phone doesn't work anymore. You flashed the beta to the OP 3 onto your 3T. Use this to fix your phone.
Edit: Sorry if this was of use to some people when it was deleted.
Just Passing By said:
Lol no wonder your phone doesn't work anymore. You flashed the beta to the OP 3 onto your 3T. Use this to fix your phone.
Click to expand...
Click to collapse
I tried to use that thread, but my phone wouldn't show up underneath Unknown Devices, in fact unknown devices would never come up at all. my pc is still in test mode from this :/
Don't worry if it doesn't appear under unknown devices. Just use the tool. A lot of what the instructions say is unnecessary. Just make sure that when you plug in your phone that one of the ports becomes "active" (I haven't had to use this tool in months, so I'm not sure exactly what it's supposed to say exactly) and press the start button.
Edit: Sorry if this was of use to some people when it was deleted.
ok. I 'll download the tool and get back to you after trying it.
edit:that worked! you are my new favorite person.
thank you so much )))))))))
Deleted
WAIT
Just Passing By said:
Deleted
Click to expand...
Click to collapse
WHY IS THIS DELETED? IM having the same problem what did you do please save me as well
Sounds like you flashed the wrong version of Oneplus 3 firmware to your phone. Do you have a 3 or a 3t? If you flash the incorrect one you will get exactly the unbootable state you describe. In that case you will have to use Qualcomm MSM Downloader tool to flash back the correct ROM and firmware partitions to get it running again. Just download the correct MSM recovery package for your phone and follow the instructions in the thread.
due to constant flashing my k3 note has been bricked at least 2 times, ive recovered it through preloader etc.
im also quite known to spflashtools and metatool etc.
some time ago my phone had water damage however i cleaned it thorough with alcohol and didnt use it for a month it worked after.
i also during dissasembly stripped torn the power volume button cable which i resoldered a replacement which is working.
my phone was working perfect although as some might know through experience some TWRP versions dont flash certain roms and others do
so i was on 3.1.0.0 twrp and any rom got me in a bootloop. i flashed through recovery itsself 3.0.3.0 and all was fine.
(btw prior to this i restored an original rom with scatter file through spflashtools to be sure and after straight ahead to the correct TWRP working version and just one stable rom which in my case was lineage 14.1 of this month 16 june if im not mistaking)
so all working better than ever as development progressed etc. suddenly i flash twrp 3.1.1.1 by daniel_hk and twrp booted without the logo i had to press the power button for it to show up in twrp as if it were in standby.
i wipe dalvik and cache i boot up normally. i shut down the phone i turn it on later and nothing blackscreen.
what is frightening is this time with or without battery no matter what settings or drivers no preloader detection on the computer.
i have had bricks due to flashing in the past which had exactly same result no screen no charging light completely dead BUT there was preloader detection on the computer.
the thing is i didnt mess with the preloader now lately it was just regular flashing. as in the past for the same reason my phone got bricked twice i wasnt flashing anything special just through recovery. the brick due to this was also not just a bootloop but as i explained above...
any thoughts?
i hesitate it is water damage since i took all measures and it was just working perfect. also prior to this it had bricked due to same reasons just recovery flashing etc.
id appreciate tremendous if anyone has something to share
https://www.youtube.com/watch?v=A3TmXtOA0IA the second half of this video shows a hardware method for gaining preloader access when all else fails. anyone can help me with figuring this out?
its about shorting a certain pin to ground of which i have no clue of on the k3 note
https://www.youtube.com/watch?v=jPn4FBAHib0
heres another example claiming of shorting the mountpoints ground and kcolo. the problem is on the lenovo k3 note the mountpoints which there are plenty of have no label and it might be a bad idea to try shorting the whole board.
ive been reading this shorting method can be effective on mediatek devices
heres a detailed thread of the process of fixing phones which might even have a corrupted preloader
https://forum.hovatek.com/thread-11802.html
http://apkdevelop.blogspot.gr/2015/0...broken-of.html
________________
as i continued researching today to put it in a nutshell there are solder mountpoints on mediatek phones of which 2 points of one which is ground and the other goes by many names also known as colo etc are short circuited which results in a forced preloader state. if someone does have this information on which is which i would tremendously appreciate it since this way i can access the preloader and fix this phone.
i cannot just try blindly because some contain voltage and that might make the phone completely unusable
...
...
i did various things and got it working again, still the information about the colo and gnd points would be valueable
Could you please explain what exact you did, because I got EXACT the same problem !!! @thanas
My phone is dead since Q3 2016 and since then I didn't thought anymore of it as maybe repairable. Already buyed a Multimeter and an external Battery charger (still waiting for arrival), but I got absolute NO idea what to do exactly, because as you already said, the points aren't labeled.
see attachment for Mainboard pic.
im really sorry as i havent logged in at all all this time just seen your message. how did the problem appear? i tried everything including replacing the power/volume button strip.
i assume u have also disabled driver verification in windows installing preloader drivers/vcom etc etc.. tinkering with spflash tools and holding the volume button as you connect to flash it? in some cases also different usb port different cable or computer/os ? these are the first steps