Database Info

[Q] i9023 bricked. Secure: on (S-ON), radio XXXXX

The last week I have been struggling to unbrick my i9023 Nexus S. Without any luck... Let's start at the beginning, how I bricked my Nexus S. If you don't think this is relevant you can skip it.
Stay with me because it's going to be a long thread...
How I bricked my Nexus S
I was running a CM9 Nightly (from around 10 March) until a week ago, together with the matrix CFS 18.0 kernel. I had a problem with rebooting. Every time I rebooted, it would take 2 or 3 tries before it actually started. First it would just reboot again, or even freeze. So after almost a month I was kinda tired of that problem, so I decided to flash a new CM9 Nightly, the one from 7 April. I flashed the Nightly like I always do, wipe cache/dalvik, and I also flashed the new matrix CFS 18.5 kernel, + the latest gapps and the reloadedICS mod. It was working fine. I rebooted a couple of times more into recovery because I wasn't happy with the reloadedICS mod. Everything was still working fine.
The battery was draining very quickly though. I was watching TV for an hour and when I decided to go to bed the battery was already dead. So I put it in the charger because I wanted to check my facebook before I went to bed. It booted fine, but when I started loading facebook in the browser, my phone freezed. I wasn't really alarmed because, well, let's face it, that's the risk with nightlies. So I pulled out the battery, something I have done a lot of times since I started rooting/flashing. After that: dead. No reaction. No charging icon when it was plugged in the charger. No vibration when I pressed the power button, nothing. A brick...
What I've tried
Although it is uncommon, I wasn't the first to brick a Nexus S. Apparently it had something to do with updating to ICS 4.0.4, on which the april 7 nightly was based on I guess.
Luckily there was AdamOutler's Unbrickable Resurrector. After some setbacks I managed to get the Resurrector working. And against all odds I "unbricked" my Nexus S on the first try! Well, I got it into download mode (home and search button). The only problem was that I still didn't have a screen. The home and search button were lit up, but the screen was still black... And according to most people, it isn't supposed to be black...
Ignoring that fact, I downloaded fastboot and tried to flash bootloader.img, as instructed. It didn't work because my bootloader wasn't unlocked, something that struck me as very weird because it definitely was unlocked before the brick. So I tried to unlock the bootloader. But for that, you need a screen... With a lot of luck I managed to unlock the bootloader. Don't ask me how, but after a few tries I succeeded.
I was making progress. And I was happy about that . So I tried to flash the bootloader again. But it still didn't work. "Write failed". After some internet research I found out wat the problem was. It had something to do with the bootloader and radio being a different version. I used the command "fastboot getvar all" and it told me the following:
- Bootloader version: i9020XXKA3
- Radio version: i9020XXXXX
Apparently the radio version isn't supposed to be XXXXX, and that's why I couldn't flash bootloader.img or radio.img. Also, this is the reason that I couldn't boot my device in the first place.
Obviously I wasn't the only person with this problem. I found a guy that had the same problem as me. He used the command "fastboot boot recovery3101.img", using an older version of CWM recovery. If you used that command, your phone would always boot into recovery, so that you can flash a new OTA.
So I downloaded that older version of CWM, and I tried the same command. And it worked! The home and search button were off and the menu and back button were on! But, still no screen. And the guy that used the same command did have a screen...
I had no clue on what to do next, so I pressed the power button, in the hope that I could boot my device directly into recovery after that. I pressed the power button, the backlight of the soft keys went out... and that was my poor Nexus S' last breath of life...
I tried the resurrector tool after that... "failed to write"...
So, am I really f***ed?
I just can't comprehend that my Nexus S could be dead forever... The hardware is fine, it's just the software that keeps it from booting up! The idea of that is crazy... Certainly with a Nexus S for christ's sake!
So, what am I to do? I kinda gave up hope...
UPDATE: SITUATION ATM
1) With AdamOutler's Unbrickable Resurrector I can get into download mode. Sometimes it doesn't work but when I pull out the battery it works again.
Now I can flash every partition with fastboot, except for;
- the bootloader (which is XXKA3)
- the radio (which is XXXXX)
The probable cause for this is the fact that "secure: on", according to "fastboot getvar all". This is very weird because no one on the internet has a Nexus S with "secure: on". It is some security for i.a. HTC devices.
When flashing the bootloader or radio, I get the following error:
sending 'bootloader/radio' <file size>...
OKAY [time]
writing 'bootloader/radio'...
FAILED <remote: Write Fail>
finished. total time: time
Click to expand...
Click to collapse
Using "fastboot -w update image-******.zip":
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
After that the flash goes fine. When it reboots, my phone is dead again. This is because the radio didn't change with this zip. If there would be a radio in that zip, it would not have worked anyway.
The radio is booted first in android, and because of this I can't do anything (the XXXXX version is wrong). This is probably also why the recovery doesn't work properly (see below). And the "secure: on" prevents me from flashing another radio.
2) With "fastboot boot recovery.img" I can get in the recovery mode. ADB "shell" works, and so does "push" and "pull". The screen is black, though. Even with a very strong flashlight I still can't see anything. I can only see 2 or 3 lines (it is different with each recovery). When I press the volume buttons to scroll, I see no changes at all on my screen.
What I have tried in recovery:
- Installing an OTA zip. I can ADB "push" an OTA zip. I have checked that with ADB "shell". Since I can't see anything I have to guide myself using pictures from CWM menus. But nothing happens. There is no sign that the install worked. The only sign that I'm actually in recovery is that the menu and back softkey are lit up, and that when I press the power button without pressing the volume buttons first, my phone powers off (this is because "reboot system now" is on top of the list in recovery, I guess).
- ADB pushing anything on /sdcard. When I turn off my phone after that and resurrect it again, the file is gone. This could be because my memory is dead. But isn't this because the resurrector removes it? Anyway, when I push a file with ADB, it definitely is on my sdcard. Only after rebooting and resurrecting it isn't...
NOTE: Rebooting/booting in whatever mode doesn't work. The only two things I can do are listed above. The moment I plug out my device, I have to use the resurrector again. Because of this there it makes no sense to flash a recovery, since I can't boot anyway. The only way I can get into recovery is by using "fastboot boot recovery.img".
NOTE 2: Recovery.log shows some errors. I will post the whole log soon...
Possible solutions?
A) How can I flash a different radio, despite of "secure: on"?
B) Can we change "secure: on" to "secure: off"? For HTC users this is as normal as "fastboot oem unlock", but there is no one on the internet that has a Nexus S with "secure: on".

I've never really saw a Nexus S totally bricked by software. It's often a combo of small user errors and small software bugs.
There is a bug with the SLCD version of the Nexus S where the backlight doesn't come on and thus it looks like it doesn't work but the softkeys light up. However, if you take a flashlight to the screen and look at an angle, you will see what's being displayed.
Also, you do not need to use an old version of CWM specifically.
Are you able to hold vol + and power to get into bootloader? If not, pull the battery out for at least 10 minutes, then put it back in and try again.

polobunny said:
I've never really saw a Nexus S totally bricked by software. It's often a combo of small user errors and small software bugs.
There is a bug with the SLCD version of the Nexus S where the backlight doesn't come on and thus it looks like it doesn't work but the softkeys light up. However, if you take a flashlight to the screen and look at an angle, you will see what's being displayed.
Also, you do not need to use an old version of CWM specifically.
Are you able to hold vol + and power to get into bootloader? If not, pull the battery out for at least 10 minutes, then put it back in and try again.
Click to expand...
Click to collapse
I know about that bug where the backlight doesn't work, and that's how I managed to unlock the bootloader eventually.
My phone is as dead as a brick. The resurrector doesn't work anymore, so I can't get into bootloader. I can't get into download mode, I can't get into anything.
I know you don't really need to use an old version of CWM, but it got me into recovery. Unfortunately, after I shut down my device, I can't do anything anymore... I guess the resurrector doesn't work because recovery is now on the boot partition?

Androyed said:
I know about that bug where the backlight doesn't work, and that's how I managed to unlock the bootloader eventually.
My phone is as dead as a brick. The resurrector doesn't work anymore, so I can't get into bootloader. I can't get into download mode, I can't get into anything.
I know you don't really need to use an old version of CWM, but it got me into recovery. Unfortunately, after I shut down my device, I can't do anything anymore... I guess the resurrector doesn't work because recovery is now on the boot partition?
Click to expand...
Click to collapse
If the phone doesn't even power on AT ALL (not even a split second) when you press the power button i'd look into a hardware problem more than a software problem. You can get into the bootload using VOL+ and power usually, not only using the ressurector.

polobunny said:
If the phone doesn't even power on AT ALL (not even a split second) when you press the power button i'd look into a hardware problem more than a software problem. You can get into the bootload using VOL+ and power usually, not only using the ressurector.
Click to expand...
Click to collapse
Well, than that hardware problem occured when I pulled out the battery after my screen freezed...
But if it really is a hardware problem, isn't it strange that I was able to get it into download mode, and that I got it to communicate with my computer using fastboot? I even got it into recovery mode for a brief moment!

Androyed said:
Well, than that hardware problem occured when I pulled out the battery after my screen freezed...
But if it really is a hardware problem, isn't it strange that I was able to get it into download mode, and that I got it to communicate with my computer using fastboot? I even got it into recovery mode for a brief moment!
Click to expand...
Click to collapse
It is very weird indeed. If I had to pick something hardware related, I'd say your battery died. Just a guts feeling, and it goes with the quick discharge scenario...

polobunny said:
It is very weird indeed. If I had to pick something hardware related, I'd say your battery died. Just a guts feeling, and it goes with the quick discharge scenario...
Click to expand...
Click to collapse
I have used other batteries (luckily I have friends with a Nexus S), but that doesn't change anything.
The big question is, how can I get into download mode again? The resurrector worked at first, but when I flashed CWM to the boot partition and rebooted after that, I can't get any signs of life out of my Nexus S. Resurrector doesn't work anymore, nothing...
The weird thing is, the moment I used the "fastboot boot recovery.img" command, windows stopped recognising the device. But according to the soft keys, it did go from download mode into recovery mode. I still didn't see anything, but I guess that's because the SLCD bug.
I guess I should not have had rebooted when I was finally in recovery...

Hmmm... someone might have an idea. I still find it extremely strange it doesn't power on at all. Were you aware of any power button problem with your Nexus? Had to double click the power button to wake it?

polobunny said:
Hmmm... someone might have an idea. I still find it extremely strange it doesn't power on at all. Were you aware of any power button problem with your Nexus? Had to double click the power button to wake it?
Click to expand...
Click to collapse
Nope, no problem at all.
The only way I could get some life out of it, was by using the resurrector tool. But now even that isn't possible anymore...
Is it actually possible to really perma-brick a Nexus S? Or are people just saying that because they lack the knowledge to unbrick it. I'm pretty sure it can't be a hardware problem. It is the software that is preventing it to boot up. That's what a brick is, right?

WOW, GOOD NEWS!
After a few (totally random) tries, I managed to resurrect my phone again! I am now in the download mode. From here I can use fastboot boot recovery.img. I still don't have a screen though...
When I get into recovery (without screen), what should I do then? Because previous time, windows stopped recognizing my phone... Should I push an OTA to my Nexus S BEFORE I use fastboot boot recovery.img? And if so, how? And if I do so, how on earth am I going to manage to install that zip without a screen? There are a lot of files on my sd card... An option would be to wipe them all, if that's possible. Another option would be to give it something starting with a 1 or an A so that it comes up on top of the list.

The problem is that I can't flash anything because of that i9020XXXXX radio version.... Is there any way I can flash another radio? Just flashing with fastboot doesn't work because of that XXXXX version...

Got it into recovery again! Windows recognized USB mass storage for a second, but not anymore.
Using a flashlight I can see that there is SOMETHING on the screen, but when I press the volume buttons to scroll nothing changes...

Another breakthrough! I installed ADB drivers, and now I got ADB working!
Can you control CWM recovery from the computer, using ADB? Because now all I have to do is flash an OTA, but I can't see anything, not even with a flashlight...

I'm not real good at the technical stuff, but it seems like you should be able to put one of the ota's on your computer and when you connect the phone, it should take you through a flash sequence. Hopefully someone above my pay grade will jump in here and help.
Hang in there, we're all pulling for you.

wmdunn said:
I'm not real good at the technical stuff, but it seems like you should be able to put one of the ota's on your computer and when you connect the phone, it should take you through a flash sequence. Hopefully someone above my pay grade will jump in here and help.
Hang in there, we're all pulling for you.
Click to expand...
Click to collapse
I'm not really good at the technical stuff either. I'm like this dog:
{
"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"
}
But I can learn quickly. I know how to push a file to the SD Card using ADB. I also now how to wipe all user data using fastboot. Combining that, I have a SD Card with only 1 file: the OTA I want to flash. That should make thinks a lot easier since I can't see a damn on my screen.
My problem wouldn't even that bad, if it weren't three problems combined. Normally when people unbrick their phone with the resurrector, they can flash a bootloader.img. But I can't, because of that i9020XXXXX baseband version. I tried to flash another radio.img but that doesn't work either. To top this off, my screen doesn't work. Even with a flashlight I only see that there's SOMETHING on the screen, but I don't see any changes when I press the volume buttons for example.
The problem with not seeing anything is that I don't know if what I did, worked. I can't confirm anything. Maybe when I flash the OTA it says: update failed. But I can't see that so how would I know?
That's why I was hoping for a way to not only push files to the SD Card using ADB and wipe all user data using fastboot, but also for a way to install zip from SD Card using ADB/fastboot.

Could this be a corrupt radio? There was a thread about the 4g radio that delves a little into what the radio actually does. I'll find it when I'm back home. Try flashing a radio through cwm if you can manage.

Harbb said:
Could this be a corrupt radio? There was a thread about the 4g radio that delves a little into what the radio actually does. I'll find it when I'm back home. Try flashing a radio through cwm if you can manage.
Click to expand...
Click to collapse
You think that would work? Because I can't flash via fastboot...
Anyway, it is worth a shot. I've tried flashing several OTAs through several recoveries without much luck, but at least now I have the knowledge to go back to where I was (download mode/recovery).
I don't know anything about radios, but the XXXXX baseband version isn't good, at least that's what people say. It prevents you from flashing a bootloader.img, and also from flashing another radio.img. And maybe it was the reason that my Nexus S bricked in the first place.
By the way, thank you all for your help!

[Q] i9023 very freaking bricked, lost all hope...
Pls help i am also facing same problem i have given NS to service center they said they will be changing its mother board is there any thing can b done.

Androyed said:
You think that would work? Because I can't flash via fastboot...
Anyway, it is worth a shot. I've tried flashing several OTAs through several recoveries without much luck, but at least now I have the knowledge to go back to where I was (download mode/recovery).
I don't know anything about radios, but the XXXXX baseband version isn't good, at least that's what people say. It prevents you from flashing a bootloader.img, and also from flashing another radio.img. And maybe it was the reason that my Nexus S bricked in the first place.
By the way, thank you all for your help!
Click to expand...
Click to collapse
Try installing factory images from fastboot, You dont need the screen for that just get it to download mode.
http://forum.xda-developers.com/showthread.php?t=1572307

in cmd it says waiting for device and nothing happened its blank

Worst case scenario ****up, need help badly :(

After 8 years of tinkering with Android phones I have no clue how this happened.
PIXEL 2 (Walleye, non-xl)
Tried getting TWRP and ElementalX working but either one or both weren't doing there thing, though I could at least boot and use my phone normally. Finally ended in a situation where I couldn't boot passed fastboot with an error at the bottom "ERROR: LoadImageAndAuth Failed: Load Error". Found a fix that said to change the active partition. Set it to b and that worked and surprise it loads TWRP...so somehow TWRP was installed, but I can't actually load Android.
Grabbed the latest factory image and manually flashed all the files in the zip-within-the-zip. Everything flashed with no hiccups so I rebooted to bootloader with the intention to then reboot the system, and now this is happening:
TLDR Phone won't turn on. Holding PWR+VolDown SEEMS to do nothing, but it actually flashes a line on the screen like it's trying to load something for a milisecond, then does nothing. Holding PWR+VolUp does nothing. Holding PWR+VolUp+VolDown does the same screen flash followed by the notification LED blinking red 2 or 3 times. Please help!
EDIT: if it matters, the phone is about 50% battery and currently still on judging purely by the fact that it's been warm for about an hour.

sorry for your troubles, i have yet to see this with our phones. Just to get some more information, what happens when you try and charge it? If you plug your phone in to a computer via USB, does it show up in devices? If it shows in devices, can you run platform-tools and see if it shows up via fastboot devices with an ID? If you can connect to fastboot, you could attempt to flash images that way.

djer34 said:
sorry for your troubles, i have yet to see this with our phones. Just to get some more information, what happens when you try and charge it? If you plug your phone in to a computer via USB, does it show up in devices?
Click to expand...
Click to collapse
Nothing happens if I plug into the computer, no sound and not listed in devices. Plugging it in to the charger does nothing except possibly charges it, but I wouldn't know because the screen doesn't seem to be able to turn on for more than a milisecond of a flash.

I had this same problem when I flashed Elemental X kernel over top of the flash kernel and all I did was use the flash-all script that is included with the system image from google. This got me back to my OS where I flashed elemental and magisk. Do you have insurance through your provider?

Battery Charging problem when OFF...

Help here:
OP6 + unlocked+TWRP+Magisk+ Pie9.0.9 xXx Rom.
Yesterday i replace the battery, and it was after one year, wish was without energy. Before assemble rear, i charge a little and test everything.
However i have a strange problem:
When charging OFF, the phone boots and appears the information of telephone unlocked, and stays there.
It should appear the symbol of a central battery + percentage and then go black.
Apart that, everything seems ok with the phone, i can turn OFF, reboot normally, enter TWRP and then system...
Is this normal? Or maybe is something wrong with battery?

Someone?

Can your phone charge in unlock interface? Maybe your phone's boot partition is broken, and it can't show charging interface. Try to use mem tools to flash a full package.

Hi.
It charges normally. On or OFF. Last time i erase and flash ROM 9.0.9, i did have some problems in fact....
And i did flash 9.0.9 Autoinstall from Maurofrio, full package. Everthing seems normal and ok....TWRP, Magisk, etc,etc....
Edit:
Turn off, conect cable, vibrate, and get unlock message.
Press power button + 6 seconds, gets black.......vibrate and again message.....something is weird....
Does not show red light of charging, but i think its hardware here, not software.

Mord0rr said:
Hi.
It charges normally. On or OFF. Last time i erase and flash ROM 9.0.9, i did have some problems in fact....
And i did flash 9.0.9 Autoinstall from Maurofrio, full package. Everthing seems normal and ok....TWRP, Magisk, etc,etc....
Click to expand...
Click to collapse
Try to use MSM Download Tool to restore phone, it will fix everything except the hardware problem.

j3 2017 dont boot after flash

hi i flashed j3 2017 with odin.the final result was passed but the phone dont boot.it goes only to odin download mode. any solution

ntamvakeras said:
hi i flashed j3 2017 with odin.the final result was passed but the phone dont boot.it goes only to odin download mode. any solution
Click to expand...
Click to collapse
Well, I'm no expert on booting, but I would try this. First, pull the battery to shut off the phone. Second, reinstall the battery and Press and hold "Volume Up+Home+Power" buttons at the same time till your phone is on,then your Samsung will enter Recovery Mode. It takes a while to get to the recovery screen so be patient. You may see the dead android for a while, but after a few minutes you will get the recovery menu. From there you can try reboot system and see if it will boot for you.
Good Luck!

BigZ1 said:
Well, I'm no expert on booting, but I would try this. First, pull the battery to shut off the phone. Second, reinstall the battery and Press and hold "Volume Up+Home+Power" buttons at the same time till your phone is on,then your Samsung will enter Recovery Mode. It takes a while to get to the recovery screen so be patient. You may see the dead android for a while, but after a few minutes you will get the recovery menu. From there you can try reboot system and see if it will boot for you.
Good Luck!
Click to expand...
Click to collapse
Forgot to ask you a question. I have a J3 that I'm trying to unlock the boot loader. If you get yours working, would you mind checking your developer options to see if you have the button for OEM unlocking? I would appreciate it. Thanks

BigZ1 said:
Forgot to ask you a question. I have a J3 that I'm trying to unlock the boot loader. If you get yours working, would you mind checking your developer options to see if you have the button for OEM unlocking? I would appreciate it. Thanks
Click to expand...
Click to collapse
I did that but nothing is happening. Only volume down home end power combination works

{
"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"
}

Did you hold the keys down continuously? That is to say, until you either get recovery mode (or in your case bootloader mode)? If you let go of the key combo after seeing the Samsung J3 screen, you let go too soon. I've always had success with getting into recovery that way. Try it again.
If you truly can't start up in recovery mode, I think you may have wiped out your recovery partition. I'd suggest you use Odin to flash it again.

I just tried booting into recovery mode and then reboot to system. If you can get to that point, you are home free. If you can't get to recovery mode, I think your best bet is to try to reflash with Odin. Maybe you got a bad download. Consider getting a fresh download and reflashing with Odin.

One more thing you might be able to do. IF you had usb debugging enabled, you could connect the phone to your pc, and issue a fastboot command "fastboot reboot" which would reboot you into the system.
This reqires some level of technical skill and some setup work to get fastboot installed (on windows) or if you have a Linux computer, fastboot is probably already installed.
The above is only going to work if you had the developers option for usb debugging turned on before you flashed the phone, and even then it may or may not work, depending on how far the phone gets while booting.
I think at this point, your best option is downloading a fresh copy of your system image from Samsung, and reflashing it with Odin. Hoperfully it will still connect to Odin, since it's already in bootloader mode.

This phone was fully functional but had broken screen as you see. I left it and I ordered a new from aliexpress. After one month the new screen came. I took the phone for charging but it gave a signal that battery not charged. And the phone not opened. I placed a new battery for charging but still couldn't get to menu and I did a wipe data factory reset but nothing happened so I decided to flash it with odin but while the flash is OK the phone don't boot. When I try to charge it is gives a green screen

ntamvakeras said:
This phone was fully functional but had broken screen as you see. I left it and I ordered a new from aliexpress. After one month the new screen came. I took the phone for charging but it gave a signal that battery not charged. And the phone not opened. I placed a new battery for charging but still couldn't get to menu and I did a wipe data factory reset but nothing happened so I decided to flash it with odin but while the flash is OK the phone don't boot. When I try to charge it is gives a green scree
Click to expand...
Click to collapse

After you flashed it, and rebooted the phone, how long did you wait for the phone to boot into system? It takes a long time (like maybe 15 minutes) for it to get to the point where you do the initial configuration. If you can try flashing with Odin again, give it at least 15 minutes to get through it's initialization process. That might be what went wrong. Just a guess on my part, but that's what I think. Let me know if it works.

VID_20220727_202947.mp4
drive.google.com

ntamvakeras said:
VID_20220727_202947.mp4
drive.google.com
Click to expand...
Click to collapse
I did all this but nothing happens I don't see the Samsung logo only a green screen. I upload a video to see what I doing

I wish I could help you. I think you are doing everything right. This problem exceeds my knowledge. Maybe someone else smarter can help you.

OK thanks a lot for your assistance

ntamvakeras said:
OK thanks a lot for your assistance
Click to expand...
Click to collapse
I don't know if you are still trying to fix your phone. If so, you might try experimenting with the ODIN option for reboot after flash. Try turning it off, flash with ODIN, unplug cable, pull battery and re-insert, see if it will boot (be patient, it will be slow). If that doesnt work, pull and reinsert battery, then try to boot into recovery with keys.
Just an idea... might get lucky.

BigZ1 said:
I don't know if you are still trying to fix your phone. If so, you might try experimenting with the ODIN option for reboot after flash. Try turning it off, flash with ODIN, unplug cable, pull battery and re-insert, see if it will boot (be patient, it will be slow). If that doesnt work, pull and reinsert battery, then try to boot into recovery with keys.
Just an idea... might get lucky.
Click to expand...
Click to collapse
I did it but nothing happened. The matter is that the phone don't power on after flash. I don't know what else to do

Hello ntamvakeras, on the first video I tell you that in option you manipulate in pit. I have an old j3 2017 I managed to install official Firmware and then install TRWP, the J3 cable is the good one I didn't have the good is we change it worked.
When you use in option pit these why you do this, I flash I don't touch pit.

ntamvakeras said:
View attachment 5669359
Click to expand...
Click to collapse
Will never boot FRP lock and OEm are On i think a account is hanging to the phone , boot in recovery samsung mode and wipe data factory reset from there , reboot

meric57 said:
Hello ntamvakeras, on the first video I tell you that in option you manipulate in pit. I have an old j3 2017 I managed to install official Firmware and then install TRWP, the J3 cable is the good one I didn't have the good is we change it worked.
When you use in option pit these why you do this, I flash I don't touch pit.
Click to expand...
Click to collapse
HI I did that because I have done a lot of experiments in this phone. I know that is wrong but I did that as last way to recover the phone

Xiaomi Mi 4 (Cancro) 16GB/3GB Global Model Stuck in EDL mode

From last 2 weeks I have been struggling with getting my mi4 to work again. Earlier, I was running AOSP Extended Custom Rom based on ANDROID 10 without root but bootloader unlocked since last 3+ years and It was running well. Following complication happened suddenly without installing any new app on my phone:
My payment app shown that my phone is rooted and did not let me do any payments
Unable to connect to WIFI showing password cannot be saved
After that, I tried cleaning apps cache while system was on and through TWRP recovery cleaned Dalvik cache and cache but that did not change any behavior.
Instead of factory resetting and reinstalling same rom, I was looking for new rom and found Xtended XR Vanilla ANDROID 11 rom unofficially released in following thread:
Xtended XR Vanilla ANDROID 11 For Mi4 (Cancro)
I downloaded this rom and Gapps from BitGapps as somehow LiteGapps was not installing playstore even it stated in the information. I tried installing Xtended XR and Gapps but TWRP stated Storage is insufficient. So, I decided to see if only Xtended XR rom works or not? It worked after reinstalling. Everything was working fine but battery was draining fast that was unusual because earlier it was giving me around 1.5-2 hours of Screen on Time and now it was down to around 40-50 mins! In order to get Google Playstore, I had to resize system partition.
After reading few articles, threads and watching YouTube videos, I deleted cache, system, data and vender partitions and resized and recreated them. But after doing that still twrp was showing the same message of storage but I found that it is a problem with many custom roms but can be solved by unmounting system, resize system and mounting system again from twrp after flashing rom. It worked and I was able to install BitGapps and except battery draining everything worked. Therefore I was thinking of flashing some custom kernel for battery draining as I was using CraneWing kernel with AOSP Extended it was working fine. Before that I started setting up my phone settings and installed apps from playstore.
Everything was fine till now but on next day after finishing all basic settings and installing apps, I encountered new problem. It happened twice whenever I try to change brightness manually phone restarts automatically. From second time onward phone stopped booting to system.
I tried following things that did not work:
Re-flashing Xtended XR Rom and BitGapps (installed successfully every time but didn't boot)
Wiping and Formatting cache, data, and system partitions
Changing TWRP version
Installing Stock Fastboot MIUI Global Rom for Mi4 Cancro (installed 4-5 times successfully via PC on fastboot, MI recovery opened twice but system did not boot)
Re-flashing TWRP again (Because battery was not charging, so whenever I keep phone as it is for like 1-2 days for draining battery I can open TWRP with 1-3% battery and can charge till 16-20% then it goes to boot loop with Mi Logo)
By this time I was only able to access Fastboot, so tried installing stock rom but it did not boot. Recovery is also not accessible. I found that I can flash stock rom in EDL mode. My phone does not support EDL from fastboot. Then I found following thread for reboot to edl via fastboot:
Reboot to EDL Via Modified Fastboot For Redmi Note 3
I used that but because it was for Redmi Note 3 and I think I made a mistake by using that. I tried button combinations of Power and Volume buttons and also tried battery draining but that did not work. Now at this moment I am stuck with following problems in given order to make my phone work again:
Battery not charging
Stuck in EDL Mode. Restarting frequently (in 2-3 seconds) in EDL continuously without system recognizing it as Qualcomm Device
Able to turn on Fastboot when Connect with Wall Charger but cannot with USB connected with PC. Though I can turn on Fastboot with wall charger connected and then connect to PC to perform any fastboot commands.
Custom Recovery not accessible (Can flash recovery but not opening)
I am not sure it is entirely battery problem or something wrong with custom rom, gapps or fastboot miui stock rom. I am not sure how can I solve this problem now. Battery replacement seems one thing that I can do but the company stopped manufacturing batteries but I found someone who has 3 years old battery stock and says it works very well for this and many other devices batteries that he sells even if manufactured batteries kept unused for long.
What should I do? I would appreciate if someone help me on this.
Thanks.

I think your brightness problem reason was that you flash cuatom kernel. I think that kernel not supported android 11. You should just tried other custom roms like havoc lineage for android 11 or etc.
Does it have blink red LED When you plug your device to charger?
It should turn to fastboot when you plug via USB to PC and hold vol up + power... Anyway, use another cable (original is better) to do that.
If u can't do that :
So about battery, for your problem i think you have 2 ways:
1. Buy and Change battery and flash fastboot rom and...
2. Charge your battery and flash fastboot and...
Just plug your device for 6-8 hours to the charger and after that, flash fastboot...
Be careful that you should use original cable.

moj.enjoy said:
I think your brightness problem reason was that you flash cuatom kernel. I think that kernel not supported android 11. You should just tried other custom roms like havoc lineage for android 11 or etc.
Does it have blink red LED When you plug your device to charger?
It should turn to fastboot when you plug via USB to PC and hold vol up + power... Anyway, use another cable (original is better) to do that.
If u can't do that :
So about battery, for your problem i think you have 2 ways:
1. Buy and Change battery and flash fastboot rom and...
2. Charge your battery and flash fastboot and...
Just plug your device for 6-8 hours to the charger and after that, flash fastboot...
Be careful that you should use original cable.
Click to expand...
Click to collapse
Actually, I did not flash any custom kernel with Xtended XR rom I was just thinking about finding compatible kernel later and then flash it.
Yes, I do get red LED but phone is continuously in EDL bootloop either I put on charge or connect with PC. With charger I can turn on fastboot but with PC it remain stuck in EDL. So I can perform some fastboot commands via getting fastboot by connecting charger -> turn on fastboot -> plug into PC. But after restart it remain in EDL bootloop. So exiting EDL is first major problem that I need to solve.
Your other two suggestions would not work if I cannot get out of EDL bootloop. Though I do think changing battery after resolving EDL bootloop can work but as of now I have no luck. I hope you get my point.
is there a way to manually stopping EDL via opening phone and do something with the motherboard or battery?
btw you have made a great rom @moj.enjoy thank you. I only got to use it for sometime but I liked it. I am planning to install the same rom if my phone starts.
Click to expand...
Click to collapse

maxrajgor said:
Actually, I did not flash any custom kernel with Xtended XR rom I was just thinking about finding compatible kernel later and then flash it.
Yes, I do get red LED but phone is continuously in EDL bootloop either I put on charge or connect with PC. With charger I can turn on fastboot but with PC it remain stuck in EDL. So I can perform some fastboot commands via getting fastboot by connecting charger -> turn on fastboot -> plug into PC. But after restart it remain in EDL bootloop. So exiting EDL is first major problem that I need to solve.
Your other two suggestions would not work if I cannot get out of EDL bootloop. Though I do think changing battery after resolving EDL bootloop can work but as of now I have no luck. I hope you get my point.
is there a way to manually stopping EDL via opening phone and do something with the motherboard or battery?
Click to expand...
Click to collapse
I know what you are say. But are u sure that you are in EDL mode?
I think when you charge battery, it can automatically bypass EDL! In my opinion charge your battery 8 hours and don't touch that. After that

moj.enjoy said:
I know what you are say. But are u sure that you are in EDL mode?
I think when you charge battery, it can automatically bypass EDL! In my opinion charge your battery 8 hours and don't touch that. After that
Click to expand...
Click to collapse
Alright, let me charge battery for 8 hours and then I will post here whatever happens.

maxrajgor said:
Alright, let me charge battery for 8 hours and then I will post here whatever happens.
Click to expand...
Click to collapse
I tried charging battery for 8 hours, but phone remain uncharged. Sadly, nothing changed.
While charging with charger, the red LED blinks variably between 3-12 times before showing MI logo in bootloop.
Blinking of red LED is the same when connected with PC, but in PC it remains in blinking and neither show MI logo nor allow me to fastboot. Also I hear connect and disconnect Windows OS sounds for devices frequently.

Its
maxrajgor said:
I tried charging battery for 8 hours, but phone remain uncharged. Sadly, nothing changed.
While charging with charger, the red LED blinks variably between 3-12 times before showing MI logo in bootloop.
Blinking of red LED is the same when connected with PC, but in PC it remains in blinking and neither show MI logo nor allow me to fastboot. Also I hear connect and disconnect Windows OS sounds for devices frequently.
Click to expand...
Click to collapse
I think It's battery issue...

CONCLUSION​I changed battery then able to flash custom rom, gapps and installed apps. It was working fine.
But again after few hours it suddenly went to bootloop and never booted again. Technician said there is some problem with PCB and phone is considered dead now.
Thank you @moj.enjoy for giving your time here.