Related
Okay so I tried searching everywhere for a solution and I didn't find anything.
So this is what happened, I was on ICS leak 4.0.4 ICS.672.1.13.en.03 then I tried to Fxz to AT&T 2.3.5 InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID28 5.zip and it got stuck at 5/20 saying "Rebooting bootloader" the screen stayed black for a long time, so I clicked close and this is where all this happened. My phone doesn't turn on, not even Fastboot, when I plug it into the charger it doesn't do anything, but when I plug it into my laptop without battery the white led turns on but still it doesn't do anything, the laptop doesn't detect anything and when I press the buttons it doesn't react nor do anything. I don't know anymore what to do, I bought this overseas so I have no warranty and it's not an AT&T phone. If anyone went through this, I really don't know what to do.. I know it's not softbrick as I can see it. I'll be very thankful if there is a solution, but my hopes are really down..
I know I read all the guides, it said "Don't pull battery or unplug. So I didn't unplug or remove battery, I just clicked close. I really didn't know this could happend. Didn't see it in any thread or post that you can't Fxz from 4.0.4 to AT&T 2.3.5, I only followed the steps from this thread: http://forum.xda-developers.com/showthread.php?t=1779968
I don't want this to happen to anyone.
Wrong thread! sorry... check your PMs darkmixta!
I made the same mistake
darkmixta said:
Okay so I tried searching everywhere for a solution and I didn't find anything.
So this is what happened, I was on ICS leak 4.0.4 ICS.672.1.13.en.03 then I tried to Fxz to AT&T 2.3.5 InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID28 5.zip and it got stuck at 5/20 saying "Rebooting bootloader" the screen stayed black for a long time, so I clicked close and this is where all this happened. My phone doesn't turn on, not even Fastboot, when I plug it into the charger it doesn't do anything, but when I plug it into my laptop without battery the white led turns on but still it doesn't do anything, the laptop doesn't detect anything and when I press the buttons it doesn't react nor do anything. I don't know anymore what to do, I bought this overseas so I have no warranty and it's not an AT&T phone. If anyone went through this, I really don't know what to do.. I know it's not softbrick as I can see it. I'll be very thankful if there is a solution, but my hopes are really down..
I know I read all the guides, it said "Don't pull battery or unplug. So I didn't unplug or remove battery, I just clicked close. I really didn't know this could happend. Didn't see it in any thread or post that you can't Fxz from 4.0.4 to AT&T 2.3.5, I only followed the steps from this thread: http://forum.xda-developers.com/showthread.php?t=1779968
I don't want this to happen to anyone.
Click to expand...
Click to collapse
I made the same mistake, any way to repair my phone? Thanks a lot...
maqndon said:
I made the same mistake, any way to repair my phone? Thanks a lot...
Click to expand...
Click to collapse
THIS IS THE CORRECT WAY TO FXZ BACK FROM ICS:
http://forum.xda-developers.com/showthread.php?t=1805975
You are totally bricked, no way out, sorry, you need a new phone.
jimbridgman said:
THIS IS THE CORRECT WAY TO FXZ BACK FROM ICS:
http://forum.xda-developers.com/showthread.php?t=1805975
You are totally bricked, no way out, sorry, you need a new phone.
Click to expand...
Click to collapse
I was thinking about Motorola factory cable, if it would do something?
I read in some thread that it forces Motorola to go in fastboot mode http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
What's very interesting is that the phone definitely knows that it is not in the presence of mere mortals when you use a Factory Cable. The phone knows it is in the presence of Moto gods as it boot differently than normal. Some phones like the Motorola Napoleon actually come right out and say "Factory Cable Connected". Other phones will boot straight to the bootloader for flashing. The various Droids appear to boot normally until you notice that there is no USB connected indicator at the top (once the OS is up) and that the host computer doesn't register all the usual devices. Instead the host computer only registers the bare minimum interfaces needed for RadioComm, RSD Lite, etc. to be able to talk to the phone. This in and of itself simplifies things as you don't have to monkey with setting the phone to the right mode (e.g. "PC Mode") -- it is automatically in the right mode for flashing.
Another interesting thing that is allegedly possible with the Factory Cable is that with the battery removed, it is possible to access some diagnostic pads on the main board of the phone, that when shorted (before connecting the Factory Cable) will boot the phone in a special recovery mode to help recover bricked phones. I say "allegedly" because thus far we've not had much luck with this, and our information is that it may only apply to unsecured phones anyway -- not secured consumer phones. Running around shorting things randomly inside your phone is a very bad idea unless you are willing to risk the phone, your computer, or both -- but sometimes things must die in the name of science -- but again I digress.
Click to expand...
Click to collapse
Factory Cable
I made this cable yesterday and nothing... when i connect the phone into PC the white light turn on for less than a second then turn off. The PC don't recognize the phone in Linux neither Windows.
I believe that i made the cable right but i'm not a 100% sure.
white led is also an indication battery out of power. Do try connecting wall charger for a while and see if that brings up the power.
The bootloader is what controls the phone at this level. If the bootloader is corrupted the phone is hard bricked and the only way to fix it would be to jtag flash a working bootloader.
jboxer said:
The bootloader is what controls the phone at this level. If the bootloader is corrupted the phone is hard bricked and the only way to fix it would be to jtag flash a working bootloader.
Click to expand...
Click to collapse
But how is the bootloader corrupted if it was stuck at rebooting bootloader? Motorola got a very strange flashing thing...
darkmixta said:
But how is the bootloader corrupted if it was stuck at rebooting bootloader? Motorola got a very strange flashing thing...
Click to expand...
Click to collapse
Your bootloader is not corrupted, you hard bricked because you tried to flash a bootloader that is a lower version. There is code in the BL to not allow that, that is one of a few things that will actually brick this phone.
jimbridgman said:
Your bootloader is not corrupted, you hard bricked because you tried to flash a bootloader that is a lower version. There is code in the BL to not allow that, that is one of a few things that will actually brick this phone.
Click to expand...
Click to collapse
If the phone still has the new bootloader and it is not corrupted then why are these phones hard bricked? The Android boot sequence starts with the bootloader when the power key is pressed. During the bootloader process it initilaizes the hardware using init.rc and init.<machine_name>.rc and then it looks for keys being pressed to run fastboot, recovery, etc and in the absence of that will attempt to boot up the Android system. So did RSD wipe the kernel and then when it got stuck on the flashing the downgraded bootloader (many phones don't allow this) was the kernel not reflashed yet? Or is there no init.rc and init.<machine_name>.rc for the bootloader to initiize the hardware? If the phone still has a valid bootloader, kernel and init files it should boot so that fastboot can be run. What got wiped that is preventing the phone from booting? When hard bricked phones are resurrected with a jtag flash often it is just a valid bootloader or bootloader and kernel that are flashed that allow the phone to be booted into fastboot or recovery so a valid rom can be flashed.The bootloader is also what handles charging the phone when you charge a phone that has been turned off, so if a valid bootloader and kernel are present when you plug in the charger you should see the charging sequence. Just curious what got so messed up that the bootloader is not even booting to a point where fastboot can be run and the phone doesn't respond to a charger.
jboxer said:
If the phone still has the new bootloader and it is not corrupted then why are these phones hard bricked? The Android boot sequence starts with the bootloader when the power key is pressed. During the bootloader process it initilaizes the hardware using init.rc and init.<machine_name>.rc and then it looks for keys being pressed to run fastboot, recovery, etc and in the absence of that will attempt to boot up the Android system. So did RSD wipe the kernel and then when it got stuck on the flashing the downgraded bootloader (many phones don't allow this) was the kernel not reflashed yet? Or is there no init.rc and init.<machine_name>.rc for the bootloader to initiize the hardware? If the phone still has a valid bootloader, kernel and init files it should boot so that fastboot can be run. What got wiped that is preventing the phone from booting? When hard bricked phones are resurrected with a jtag flash often it is just a valid bootloader or bootloader and kernel that are flashed that allow the phone to be booted into fastboot or recovery so a valid rom can be flashed.The bootloader is also what handles charging the phone when you charge a phone that has been turned off, so if a valid bootloader and kernel are present when you plug in the charger you should see the charging sequence. Just curious what got so messed up that the bootloader is not even booting to a point where fastboot can be run and the phone doesn't respond to a charger.
Click to expand...
Click to collapse
This is similar to what has been done here with our phone:
http://www.xda-developers.com/android/motorola-at-it-again-locks-down-atrix-4g-even-more/
It is just like the atrix 4G situation.
What Moto has done with the A0.72 bootloader is that it will not allow you to flash back to the A0.65 bootloader once the A0.72 has been flashed to the device. What it does is blows one of the 3 efuses that allows the phone to boot to the mbmloader (moto's bootloader loader).
That is why we now have a modified fxz that will flash all of the fxz minus the bootloder. So you will be on GB, but still have the latest BL A0.72.
Moto has 3 layers of the bootloader itself and all 3 are signed with the same root CA, the very last one is the one that actually loads the kernel, and the issue with these bricks is that the 2nd layer of the bootloader mbmloader that is what these people that have bricked after flashing, was the mbmloader that allowed you to "load"/flash the mbm.bin for A0.65 and that tripped the efuse that turns the 1st layer BL off, so no charging either.
Moto seems to have gotten real nasty to to us Devs as of late, and why most of us in here are saying this will be our last MOTO phone.
P.S. so far even JTAG has not been ale to resurrect some of these bricks. I was at an AT&T repair facility the other day (yes I have full access to the back area) and we played with one of the reported ICS leak bricked phones and it would not even see that the phone was connected to the JTAG box. There was another phone that was also a "hard brick" that was not from the same leak that was a GB phone and it connected right up to the JTAG box without issue.
jimbridgman said:
This is similar to what has been done here with our phone:
http://www.xda-developers.com/android/motorola-at-it-again-locks-down-atrix-4g-even-more/
It is just like the atrix 4G situation.
What Moto has done with the A0.72 bootloader is that it will not allow you to flash back to the A0.65 bootloader once the A0.72 has been flashed to the device. What it does is blows one of the 3 efuses that allows the phone to boot to the mbmloader (moto's bootloader loader).
That is why we now have a modified fxz that will flash all of the fxz minus the bootloder. So you will be on GB, but still have the latest BL A0.72.
Moto has 3 layers of the bootloader itself and all 3 are signed with the same root CA, the very last one is the one that actually loads the kernel, and the issue with these bricks is that the 2nd layer of the bootloader mbmloader that was these people that have bricked with was the mbmloader that allowed you to "load"/flash the mbm.bin for A0.65 and that tripped the efuse that turns the 1st layer BL off, so no charging either.
Moto seems to have gotten real nasty to to us Devs as of late, and why most of us in here are saying this will be our last MOTO phone.
P.S. so far even JTAG has not been ale to resurrect some of these bricks. I was at an AT&T repair facility the other day (yes I have full access to the back area) and we played with one of the reported ICS leak bricked phones and it would not even see that the phone was connected to the JTAG box. There was another phone that was also a "hard brick" that was not from the same leak that was a GB phone and it connected right up to the JTAG box without issue.
Click to expand...
Click to collapse
That's definitely a strange situation. Jtag talks directly to the cpu and the nand flash so no matter how hard the phone is bricked it should be able to be accessed via jtag. I guess the moto efuses are operating at a very low level? Kind of crappy to put that in there that renders a device unusable. People are going to run out of phones to buy. On the LG-P999 forum many people swore off LG due to lack of updates and not being able to get hardware drivers from LG or Nvidia. At least with the Nvidia chip the P999 is virtually unbrickable as recovery and bootloader can be flashed at a very low level using Nvidia tools (bootloader is not even run to flash at this level). Phones that get the most updates are Nexus branded phones but I personally will never buy a Samsung device again. They have bad hardware code in their EMMC chips and there is a rash of Nexus S devices bricking themselves during an OTA flash or factory reset when the EMMC is issued an erase command. The bad code corrupts the EMMC during the erase and renders the device bricked beyond any repair. It only happens sometimes and when it does Samsung cannot even flash them again. So I guess that just leaves HTC. Now that Google owns Motorola future Moto models may become Nexus devices. I personally prefer Moto phones but I have not hard bricked mine yet. Since I bought it second hand and am in Thailand I have been very cautious and have done very little modding to it and decided to wait (thankfully) for the official OTA release. I almost flashed the leak and glad I waited. Thanks for the explanation as to why they are perma-bricked.
This is exactly happened to my phone.
I was up on the first ICS leak, rooted and everything working great! I tried installer a font and it rebooted as normal but then stalled at the "Rethink Possible" screen. After pulling the battery and starting all over, I attempted to start the ICS process again, starting with going back to 2.3.5 (Yes, this is where I went wrong!)
The darn thing is literally a brick right now.
I wish I would have left it alone....
MACKSnare519 said:
This is exactly happened to my phone.
I was up on the first ICS leak, rooted and everything working great! I tried installer a font and it rebooted as normal but then stalled at the "Rethink Possible" screen. After pulling the battery and starting all over, I attempted to start the ICS process again, starting with going back to 2.3.5 (Yes, this is where I went wrong!)
The darn thing is literally a brick right now.
I wish I would have left it alone....
Click to expand...
Click to collapse
Yes, you hard bricked it and there is nothing you can do to fix it. There were many warning about this posted with the leak and in other threads. Sorry to hear that you killed your phone. :crying:
Technically, if you were on the FIRST leak, you should be able to fxz back.
Sent from my SAMSUNG-SGH-I727 using xda premium
Fall of Enosis said:
Technically, if you were on the FIRST leak, you should be able to fxz back.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Yea, but he would have had to read the forums and fxz back using the custom script to prevent downgrading the baseband and bricking.
How do I unbrick a Samsung Conquer? Model SPH-D600, FE16 stock firmware, unmodified. I was unsuccessful obtaining root with Super One Click or the root exploit for Evo 4G which purportedly works (SPH-D710.FE16_CL579416_ROOTED-oc-sfx.exe). My phone worked fine after trying these 2 methods, but the root would never take.
Next I tried the Odin method from the files upped to this thread: [ROM] Custom Stock Samsung Conquer 4G FC17 Rooted With Tweaks
I downloaded both .rar archives to extract valid files. I followed the instructions in the included text file, puting my phone in download mode, loading the 2 files in Odin, and pressing the start button (easy, right?). After letting Odin run for several minutes, it hung on step 5/8, and the Odin program closed, but my phone remained in download mode. I couldn't get my phone to respond to any keys, so my only choice was to remove the battery. Now the phone will not power on. No bootloader, no response at all. Please help!
Hey bro what's the screen look like at the moment cause I done a very similar thing and I soft bricked my phone when I used ordinary the first time because odin closed so I pulled the USB cord out and then I softball bricked it. If its a computer then,? Triangle then Android guy on your screen then you have soft bricked it and I'll be able to have lip you fix it.
And remember do not panic as that's when you really screw stuff up.
Sent from my YP-G70 on ics using xda premium
Evoium said:
Hey bro what's the screen look like at the moment cause I done a very similar thing and I soft bricked my phone when I used ordinary the first time because odin closed so I pulled the USB cord out and then I softball bricked it. If its a computer then,? Triangle then Android guy on your screen then you have soft bricked it and I'll be able to have lip you fix it.
And remember do not panic as that's when you really screw stuff up.
Click to expand...
Click to collapse
I can't get anything to show on the screen at all. No lights come on or anything.
Can you get into clockworkmod?
By holding up volume key + menu key + power key.
If yes, when you get into clockworkmod wipe data cache and do a factory reset.
Then power down or switch your mobile and then enter into download mode and use odin to flash your desired GB Rom.
Hope this solves your problem.
Once I realized it was't even responding to the charger, I knew it must be dead. I tried several button combos, and I spoke with my carrier's tech support who suggested other methods. This phone is hard-bricked with a capital B. I'm just have to deal with getting a new phone. At least the Credo people are pretty nice about discounts.
hollacoast said:
Once I realized it was't even responding to the charger, I knew it must be dead. I tried several button combos, and I spoke with my carrier's tech support who suggested other methods. This phone is hard-bricked with a capital B. I'm just have to deal with getting a new phone. At least the Credo people are pretty nice about discounts.
Click to expand...
Click to collapse
My samsung screen loads then the warning a custom os can cause critical problems in phone are. is it bricked oh no!
Some general rules:
It is not recommended to flash bootloaders on your device unless necessary. When flashing bootloaders, make sure the model number matches the device you are flashing. Also, always use a new cable without any wiggle room or cable damage.
To get into download mode to use Odin or Heimdall:
Remove and replace battery.
hold Volume Down & Home then press power while continuing to hold power.
You can now use Odin or Heimdall to flash a stock ROM package.
The Fix for Hard Bricks:
In the event that you cannot get to download mode, please contact me. I am developing a boot-from-sdcard fix for bricked Galaxy Cameras based on the methods used in i9300 here: http://forum.xda-developers.com/showthread.php?p=34139922. The hardware mod must be located to boot Odin Mode (Loke Daemon) the SDCard. JTAG will not work on Exynos 4412 devices.
I am subscribed to this thread.
AdamOutler said:
Some general rules:
It is not recommended to flash bootloaders on your device unless necessary. When flashing bootloaders, make sure the model number matches the device you are flashing. Also, always use a new cable without any wiggle room or cable damage.
To get into download mode to use Odin or Heimdall:
Remove and replace battery.
hold Volume Down & Home then press power while continuing to hold power.
You can now use Odin or Heimdall to flash a stock ROM package.
The Fix for Hard Bricks:
In the event that you cannot get to download mode, please contact me. I am developing a boot-from-sdcard fix for bricked Galaxy Cameras based on the methods used in i9300 here: http://forum.xda-developers.com/showthread.php?p=34139922. The hardware mod must be located to boot Odin Mode (Loke Daemon) the SDCard. JTAG will not work on Exynos 4412 devices.
I am subscribed to this thread.
Click to expand...
Click to collapse
Why will JTAG not work on Exynos 4412? Also, if i wanted to view UART output from the GT-I9300, is all i need a linux box with a cable like this?
--UPDATE: looks like you did a video for the Captivate on your UART jig. Taking a look now for resistor values regarding the GS3, perhaps an oscilloscope would help here?
There is no UART output on USB on this device. Also Exynos4412 JTAG is usually disabled except for the Nexus10.
AdamOutler said:
There is no UART output on USB on this device. Also Exynos4412 JTAG is usually disabled except for the Nexus10.
Click to expand...
Click to collapse
Bummer, I just saw that it looks like you had to interface directly to 2 board pins on the Galaxy Camera to get UART i imagine it will be similar on the GS3.
Touch screen not responding
hi, i am not sure if its the right place to post or not. i tried to root my camera with galaxy s3's kernel(using sgs3 toolkit) and after flashing the kernel nothing happen but my cameras screen stop responding. i tried to flash default frimware via odin but touch screen isnt working.
any advice please
regards
umfaruki said:
hi, i am not sure if its the right place to post or not. i tried to root my camera with galaxy s3's kernel(using sgs3 toolkit) and after flashing the kernel nothing happen but my cameras screen stop responding. i tried to flash default frimware via odin but touch screen isnt working.
any advice please
regards
Click to expand...
Click to collapse
Why would you do that when Adam gave us a specific root method for our GCams? You should probably post this in general section. I sure hope someone can help you out. It would be a bummer if you lost your camera
Good Luck.
I have a bricked GC100. efs screwed up. boot loops. boots in recover, boots in download mode flashes all available stock firmware, doesn't boot normally. tried booting up after flashing, factory settings after flashing. Any hope for this device?
rudie_techie said:
I have a bricked GC100. efs screwed up. boot loops. boots in recover, boots in download mode flashes all available stock firmware, doesn't boot normally. tried booting up after flashing, factory settings after flashing. Any hope for this device?
Click to expand...
Click to collapse
. Did you do a factory reset/wipe data?
Yeah... installed stock recover, didn't work, tried with CWR, didn't work... went through all available post, nothing helped... boot animation shows, samsung logo shows then again boot animation...
Finally got it fixed. As GC100 is similar to S3, downloaded efs file for S3 flashed it via odin through bootloader and voila... attaching the file for reference if anyone else gets into trouble!
Shouldn't I be awarded king of all screw ups!? Tried to flash a Rom for S3. No problem with few tweaks, didn't work however, flashed stock gc100 now touch screen not working. factory reset with stock recovery, cwm recovery still touch not responding... flashed 3 parts stock rom + efs, flashed 3 part stock without efs, flashed 4 stock roms 1 package, still touch not working...
rudie_techie said:
Shouldn't I be awarded king of all screw ups!? Tried to flash a Rom for S3. No problem with few tweaks, didn't work however, flashed stock gc100 now touch screen not working. factory reset with stock recovery, cwm recovery still touch not responding... flashed 3 parts stock rom + efs, flashed 3 part stock without efs, flashed 4 stock roms 1 package, still touch not working...
Click to expand...
Click to collapse
It's closer to an s4 than s3 but if you wanted a galaxy cam phone, they already make the s4 zoom.
http://www.samsung.com/global/microsite/galaxycamera/mobile/galaxys4/index.html
I don't want a phone and I'm aware of S4 zoom. Its just that I can't sit and do "nothing". Well that's why i keep playing around (and always get into trouble ) Well getting the touch replaced as that's the only way. logcat says -1v for touch which means I've fried the touch digitizer. hahah (Still in warranty, unrooted and resetted the counter with triangle away)
twistedumbrella said:
It's closer to an s4 than s3 but if you wanted a galaxy cam phone, they already make the s4 zoom.
http://www.samsung.com/global/microsite/galaxycamera/mobile/galaxys4/index.html
Click to expand...
Click to collapse
Its the same specs as an international S3, but it's got lower screen resolution. Its definately not like an S4 at all.
AdamOutler said:
Its the same specs as an international S3, but it's got lower screen resolution. Its definately not like an S4 at all.
Click to expand...
Click to collapse
Definitely wasn't talking about hardware specs just the software.
Either way, it would be better to compile a build using the phone as a base and making the necessary changes than attempting a direct port.
ow about porting CM to this camera...!? I'm not an expert just a desire!
rudie_techie said:
ow about porting CM to this camera...!? I'm not an expert just a desire!
Click to expand...
Click to collapse
AOSP is what Samsung starts with, so it is always possible to do the basics. CM would probably break it, though. That seems to happen a lot
Looked around a lot and found no solution so here it goes.
I was trying to update to KitKat and at the Pwr Volume- screen I mistakingly hit the wipe data. I wasn't on a custom ROM before, I used the clockwork mod app to install TWRP. Now I'm stuck on the screen where it says This Device is Unlocked and won't do anything else. I've tried every restart button combo but it always goes back to that screen. Can anyone help me out please or is this a lost cause.
Also the computer does not recognize it since it won't get past the opening screen and fastboot/adb wont do anything either
Wipe data in bootloader mode when unlocked = bricked for good unless you have nvflash backups
Or, if you can get back into bootloader mode, follow busters method to unbrick
Sent from my GS3 on AOSB 4.4.2 using Tapatalk 4
Don't have NVFlash backups and I cant get to the boot loader so I guess I'm boned. Was good while it lasted, was running slow towards the end so I guess it was about that time lol
Hello, dear XDA community!
I'm writing here to ask you for help. My cousin gave me his Vodafone Smart 2 (aka Alcatel V860), which got fatally bricked while flashing an official OTA (!!!).
For crazy it may seem, the situation is pretty serious, as the phone doesn't get pas the Android robot logo. I cannot access to recovery nor to fastboot nor to the bootloader (power + vol up, power + vol down do not respond).
I have had a little practice with flashing, but I knew that the minimum prerequisite for flashing or recovering anything is having a working bootloader. And here, the bootloader seems corrupted.
Is there anything I can do to revive the phone?
Might be wrong since i've not much exp with bricked androids, and im new to them my self.
But having seen others with truely borked boot loaders I don't think you would even get a screen if it was corrupt would you?
I do not know if it will work on your device but i've seen those with corrupted boot loaders be able to unbrick them by shorting pins on the flash.
This might be flash chip dependent and not a working solution on all devices, it also means taking the phone apart..
You'll have to research from there, I know it's not that helpful but IF you get desperate it might be something to look into.
That's if it ends up being the bootloader at all.
Raztan said:
Might be wrong since i've not much exp with bricked androids, and im new to them my self.
But having seen others with truely borked boot loaders I don't think you would even get a screen if it was corrupt would you?
I do not know if it will work on your device but i've seen those with corrupted boot loaders be able to unbrick them by shorting pins on the flash.
This might be flash chip dependent and not a working solution on all devices, it also means taking the phone apart..
You'll have to research from there, I know it's not that helpful but IF you get desperate it might be something to look into.
That's if it ends up being the bootloader at all.
Click to expand...
Click to collapse
Thanks for your help Raztan! I think that first of all it's a software failure.
What I'm wondering is: is there a way to push the bootloader to the phone, some way or another, even if the phone doesn't even reach fastboot or recovery?