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.
I'm not sure where to post this, sorry for that.
I haven't found any help or so in any threads about my phone on this forum or on others...
I own a Vodafone Smart 2 (Alcatel V860) mobile phone that I rooted, had the original ROM (got rid of the Vodafone mess ) for a while and then flashed Roeddie's v 0.9.9 (OTA 4) ROM and it was all going well...
Until a couple of days ago when I saw a thread on HtcMania.com claiming a clockworkmod recovery for this phone, so I said why not... (not allowed to post the url...)
I've put the .zip on my SDcard and flashed it via the original recovery. The cwm loaded, but at reboot it was stuck in the original recovery. Sort of Boot Loop.
Happened this before (when flashing some idiot cm7), so I wiped data/factory reset, dalvik, cache partition and I restored a previous backup, supposed to solve that Boot Loop. But, this time, it didn't... The phone was still booting directly into the original recovery.
So I tried another thing. I've started the phone in fastboot mode and used the fastboot method to write that backup. That meant "fastboot erase bootloader, boot, system, userdata, custpack, recovery, cache" and then "fastboot flash the images from the backup", method that I used before and worked without any problem.
But, this time, after I erased everything, when I started to flash the images from the backup... the phone, somehow, POWERED OFF, I still don't have the slightest idea why... :crying:
When i powered it on, the bootloader was missing so it just froze with the Android logo on the screen and after a few seconds it shut down.
I tried starting it in fastboot mode, but no luck. It starts just like that every time, but if I plug the USB cable in it, it doesn't shut down anymore, freezing with the logo on screen.
Windows won't recognize it under any circumstances, no matter what drivers I have. no adb, fastboot. So it's pretty much useless.
If i restart it like 5 times, Windows eventually recognizes it as a Modem. Useless.
I think it's a Soft Brick, because it starts but it has no idea what to do without the bootloader. It would generally be recoverable, but, as you can see, I don't have any method to communicate with this phone...
I would consider the jtag, with a RIFF Box. Taking the motherboard out of it and "writing the dead body", but I don't think the Riff Manager supports this sh**ty phone and I wouldn't like to pay for it.
The phone is still covered by warranty, but I'm not sure if they are going to do it for free, because I messed with it.
I can try that story: "I was taking an OTA Update and the phone never powered on." maybe they are going to buy it.
So is it any other method to write at least the bootloader on it, any other that the ones mentioned before, methods that I have no access to ?
RO.maniac said:
I'm not sure where to post this, sorry for that.
I haven't found any help or so in any threads about my phone on this forum or on others...
I own a Vodafone Smart 2 (Alcatel V860) mobile phone that I rooted, had the original ROM (got rid of the Vodafone mess ) for a while and then flashed Roeddie's v 0.9.9 (OTA 4) ROM and it was all going well...
Until a couple of days ago when I saw a thread on HtcMania.com claiming a clockworkmod recovery for this phone, so I said why not... (not allowed to post the url...)
I've put the .zip on my SDcard and flashed it via the original recovery. The cwm loaded, but at reboot it was stuck in the original recovery. Sort of Boot Loop.
Happened this before (when flashing some idiot cm7), so I wiped data/factory reset, dalvik, cache partition and I restored a previous backup, supposed to solve that Boot Loop. But, this time, it didn't... The phone was still booting directly into the original recovery.
So I tried another thing. I've started the phone in fastboot mode and used the fastboot method to write that backup. That meant "fastboot erase bootloader, boot, system, userdata, custpack, recovery, cache" and then "fastboot flash the images from the backup", method that I used before and worked without any problem.
But, this time, after I erased everything, when I started to flash the images from the backup... the phone, somehow, POWERED OFF, I still don't have the slightest idea why... :crying:
Logically, when i powered it on, the bootloader was missing (I've erased it earlier and the phone Powered Off just before writing the bootloader from backup) it just freoze with the Android logo on the screen and after a few seconds it shut down. Because it has no bootloader and it doesn't know how and what to boot...
I tried starting it in fastboot mode, but no luck. It starts just like that every time, but if I plug the USB cable in it, it doesn't shut down anymore, freezing with the logo on screen.
Windows won't recognize it under any circumstances, no matter what drivers I have... no adb, fastboot, odin. So it's pretty much useless...
If i restart it like 5 times, Windows eventually recognizes it as a Modem. Useless...
I have no fastboot, adb, odin (that I'm not sure if works on this phone) access... :crying:
I think it's a Soft Brick, because it starts but it has no idea what to do without the bootloader. It would generally be recoverable, but, as you can see, I don't have any method to communicate with this phone...
I would consider the jtag, with a RIFF Box. Taking the motherboard out of it and "writing the dead body", but I don't think the Riff Manager supports this sh**ty phone and I wouldn't like to pay for it...
The phone is still covered by the warranty, but I'm not sure if they are going to do it for free, because I messed with it. Basically, I can try that story: "I was doing an On The Air Update and the phone never powered on..." maybe they are going to take it... anyways...
So, I'm asking you, is it any other method to write at least the bootloader on it, any other that the ones mentioned before, methods that I have no access to ???
Click to expand...
Click to collapse
Don't know anything about your phone but all I can sare is that using flashtool, flash the stock kernel(find for your device using search box) and reinstall stock firmware or if your bootloader is unlocked, flash a different kernel with working recovery. I have xperia x10 so not even close to your phone
Bigkiler5 said:
Don't know anything about your phone but all I can sare is that using flashtool, flash the stock kernel(find for your device using search box) and reinstall stock firmware or if your bootloader is unlocked, flash a different kernel with working recovery. I have xperia x10 so not even close to your phone
Click to expand...
Click to collapse
My bootloader isn't unlocked. No one actually did that until now for this "space craft"...
I don't think that "flashtool" will be able to connect to my phone as Windows doesn't recognize it at all... And, as far as I know, flashtool is only for SONY's Xperia...
Thanks, anyway...
RO.maniac said:
My bootloader isn't unlocked. No one actually did that until now for this "space craft"...
I don't think that "flashtool" will be able to connect to my phone as Windows doesn't recognize it at all... And, as far as I know, flashtool is only for SONY's Xperia...
Thanks, anyway...
Click to expand...
Click to collapse
Like i said i have xperia x10 so i have knowledge about my device. You should ask this question in your mobile's forum. That will really help..... I think the solution they will give may be similar but in a different way.
Greets
i cant power on phone vodafone smart 2
my Vodafone won't turned on after trying to make recovery from alberto. and even did not vibrate after pressing power button to turn it on.
also it does not work at all like there are no battery attached to it. almost dead phone. and my computer not detect it anymore. and can't access fastboot or recovery screen.
do anyone fix this problem??
same problem bricked Vodafone smart ii
Yes, mine too has the same problem, pc won't see it else than Broadcom usb to com device, using a COM port and I don't know what to do as it won't start at all...
Nobody has any ideea, like on Alcatel OT908 which can be unbricked?
Many thanks
mixeristu said:
Yes, mine too has the same problem, pc won't see it else than Broadcom usb to com device, using a COM port and I don't know what to do as it won't start at all...
Nobody has any ideea, like on Alcatel OT908 which can be unbricked?
Many thanks
Click to expand...
Click to collapse
Post on your phone's forum and try to reinstall official software using pc suite(or whatever you call it)
vodacrap II bricked
Bigkiler5 said:
Post on your phone's forum and try to reinstall official software using pc suite(or whatever you call it)
Click to expand...
Click to collapse
My phone IS Vodafone Smart II that' why I did write here. Have the same problem like the others, pressing power button does nothing, phone is recognized only as Broadcom USB to Serial so I can't do anything and have no ideea what to do
mixeristu said:
My phone IS Vodafone Smart II that' why I did write here. Have the same problem like the others, pressing power button does nothing, phone is recognized only as Broadcom USB to Serial so I can't do anything and have no ideea what to do
Click to expand...
Click to collapse
It could be a hard brick and your info seems to confirm this but don't take my word for it. Search on google for issues with your device I seem to remember reply to a thread similar to this a while back.
Sent from my HTC One using Tapatalk 4 beta
**Press the thanks button if I have helped you.
---------- Post added at 09:39 PM ---------- Previous post was at 09:33 PM ----------
The I think.this is because when some phones are bricked they show the manufactures name such as on a hard bricked htc device it sometimes shows qhsusb_dload (don't quote me on that if my spelling is wrong) and it connects under a Qualcomm USB device driver. That is because sometimes on devices the chipset is made by Qualcomm but on your device the chipset is made by Broadcom and that why it shows a Broadcom named device driver.
Sent from my HTC One using Tapatalk 4 beta
**Press the thanks button if I have helped you.
Hi!
Someone has news about this topic?
bad news
cfjrocha said:
Hi!
Someone has news about this topic?
Click to expand...
Click to collapse
Yes, the bad news is that even JTAG could not repair my hard-bricked vodacrap II. My advice is to be really carefull when installing the custom android version, especially when using another sim than vodafone, some of the mods won't let you insert the network cod (eight of 1), mine didn't work with any version of the mods, sometimes I wasn't able to receive calls, sometimes to make calls, depending. Take it and keep it using vodafone or in any other case don't buy is not worthy.
i accidentally erased boot and bootloader.nor download mode nor recovery work and my pc recognize it like Broadcom USB wireless modem.Any solution?
Hello to you all, I am new to XDA and it is because of this problem I am having.
The other day, my N5 shut down unexpectedly and kept that virtual power button pressed (I've seen this happen to a lot of people). The next day, it stopped doing that, but the next big issue started: The phone was stuck on boot animation. Since then, I am not able to boot the phone, so I entered the bootloader (which is still functional) and tried to unlock the bootloader (I blame myself for not doing this since the beginning) from my PC but every time it reboots the phone to keep the changes, the bootloader locks itself again, preventing me to fastboot an image to my device
This is the main issue here, I can't start up my phone, the bootloader won't unlock and somehow, I can't ADB because my PC won't recognize the device. In other words, it seems my Nexus is bricked (may be the first Nexus in the history to be bricked).
I believe there must be a solution for this problem, can anyone help me please!?!?!
Thank you all!
this is how I fix mine.
Can you boot into recovery?
hongkongking said:
this is how I fix mine.
Can you boot into recovery?
Click to expand...
Click to collapse
Hey, thanks for this help, I'll let you know how that goes. And yes, I can boot into recovery.
My device isnt recognized on ADB, and everytime I try to unlock the bootloader, when the device restarts, immeditaly locks the bootloader again.
did u factory reset and wipe dalvik / cache? did u install a correct PC driver? did you ever using adb to connect to your phone?
I remember someone said sometimes you need to unlock the bootloader several times to get it unlocked.
from this and this, your nand flash seems has problem.
Try using LG Flash Tool to flash facory image, it doesn't need to unlock bootloader, but i think it's better not to write anything to nand flash as you don't know if it has problem or not, do so might make your phone completely bricked.
A mistery with my nexus
Hello! First sorry for my bad english.
I'm running stock android 6.0 (developer preview 3) by stephanmc.
I installed months ago the twrp recovery wich I currently hace.
Since a few days ago , my phone began to charge the battery very slowly and stop being recognized by the PC.
I discovered that is charging in USB mode when it is actually connected to the wall. I'm using the original cable and charger of the nexus. I have already used other cables and its the same results.
The curious thing is that when this happens ( because if I restart the phone many times eventually works well for a while) is when my phone doesnt boot in bootloader. I discovered that a black screen appears when I reset the phone in bootloader mode. And if I restart the phone many times until the bootloader is visible , the phone charge and is recognized by the PC.
Anyone know what might be happening ? I'm from Uruguay and I have no guarantee!
Thanks and regards!
Something similar happened to me once because I changed something in the kernel I should have not. Don't remember what but update the kernel and I was fine after that.
RSax said:
A mistery with my nexus
Hello! First sorry for my bad english.
I'm running stock android 6.0 (developer preview 3) by stephanmc.
I installed months ago the twrp recovery wich I currently hace.
Since a few days ago , my phone began to charge the battery very slowly and stop being recognized by the PC.
I discovered that is charging in USB mode when it is actually connected to the wall. I'm using the original cable and charger of the nexus. I have already used other cables and its the same results.
The curious thing is that when this happens ( because if I restart the phone many times eventually works well for a while) is when my phone doesnt boot in bootloader. I discovered that a black screen appears when I reset the phone in bootloader mode. And if I restart the phone many times until the bootloader is visible , the phone charge and is recognized by the PC.
Anyone know what might be happening ? I'm from Uruguay and I have no guarantee!
Thanks and regards!
Click to expand...
Click to collapse
USB recognizability in M Preview is a bit buggy for now, you have to switch your mode to MTP when you connect the device to the PC.
About bootloader, what do you mean by "reset the phone in bootloader" ?
make sure you have at least Lollipop bootloader installed, then let me know.
Thanks
stephanmc said:
USB recognizability in M Preview is a bit buggy for now, you have to switch your mode to MTP when you connect the device to the PC.
About bootloader, what do you mean by "reset the phone in bootloader" ?
make sure you have at least Lollipop bootloader installed, then let me know.
Thanks
Click to expand...
Click to collapse
Hi! Thank you both for your answers. My english is bad and even more when talking about phone's components and stuff.
I meant to say that when I hold the power button and vol down with my phone off, or power button + vol down + vol up, most of the times I recieve a black screen on my dipslay.
I'm pretty sure I have the lollipop bootloader because I installed your 6.0 ROM from twrp on 5.1.1 stock, having already this issue.
I'm afraid to try installing the factory image because when I get to the bootloader the good news don't last too long and suddenly the bootloader isn't working again
Another data is that when I try to change the USB connection mode from the developer menu on settings I recieve this message: "Unfortunately, settings has stopped".
Do you think I may have a deffective usb port or/and flex cable?
RSax said:
Hi! Thank you both for your answers. My english is bad and even more when talking about phone's components and stuff.
I meant to say that when I hold the power button and vol down with my phone off, or power button + vol down + vol up, most of the times I recieve a black screen on my dipslay.
I'm pretty sure I have the lollipop bootloader because I installed your 6.0 ROM from twrp on 5.1.1 stock, having already this issue.
I'm afraid to try installing the factory image because when I get to the bootloader the good news don't last too long and suddenly the bootloader isn't working again
Another data is that when I try to change the USB connection mode from the developer menu on settings I recieve this message: "Unfortunately, settings has stopped".
Do you think I may have a deffective usb port or/and flex cable?
Click to expand...
Click to collapse
Do not worry about your English I'm not a native speaker too, so I can understand this .
The best way to know if bootloader haven't an issue, is to try to boot in that mode from command line: adb reboot bootloader
Some more questions:
You state that you already had this issue on Lollipop stock?
What do you mean by " don't last too long and suddenly isn't working again" ? You mean the phone reboots itself without doing anything ? Or the screen of green Android in bootloader becomes black and you still are in bootloader mode?
Have you then installed my rom in the clean way i described ?
I would like to have the exact steps by steps of what you have
Thanks
stephanmc said:
Do not worry about your English I'm not a native speaker too, so I can understand this .
The best way to know if bootloader haven't an issue, is to try to boot in that mode from command line: adb reboot bootloader
Some more questions:
You state that you already had this issue on Lollipop stock?
What do you mean by " don't last too long and suddenly isn't working again" ? You mean the phone reboots itself without doing anything ? Or the screen of green Android in bootloader becomes black and you still are in bootloader mode?
Have you then installed my rom in the clean way i described ?
I would like to have the exact steps by steps of what you have
Thanks
Click to expand...
Click to collapse
Hi! Sorry for not responding before! I've been very busy with the university.
If I can acces to the bootloader (MOST of the times I can't, It's really a pain in the *#@) my pc does recognize the phone in that mode, and I can even go to the recovery and mount the data. Sometimes if I reboot the phone after that it works well for a little while.
The other times the pc doesnt recognize the phone at all, if I connect the phone it only starts charging, not leting me to change the connection mode (settings has stopped).
What do you mean by " don't last too long and suddenly isn't working again" ? You mean the phone reboots itself without doing anything ? Or the screen of green Android in bootloader becomes black and you still are in bootloader mode?
No, I've never been too long in bootloader to check that, but I dont think so. I meaned that if I start the phone in that moment (when the phone boots into bootloader mode) it works well but only for a little while.
Most of the times that I try to boot into bootloader the phone vibrates once and then a black screen appears. I tried rebooting the phone into bootloader mode from an app, but its the same result that pressing the buttons of the phone.
Yeah I had this problem on stock 5.1.1 too.
I installed your rom in the way that you described!
Thanks!!
Bump
Someone knows a possible solution? It is possible that I have the data pins of the port broken? Or the USB flex board half broken? Idk.
Good day ,
I've been looking around for solution in this forum for two days now and none has helped me solving the problem I'm having. Hopefully by posting more specific details on this thread, you guys could help me pinpoint what to do. My main goal is to backup all data from the internal storage if possible (the data in the SD cards are backed up fine) then proceed to possibly make the phone usable again.
The phone was initially somehow soft-brick (loop on bootloader - tampered, locked, security warning and S-ON). Tried all possible actions/options on the bootloader but none has worked out, it would just prompt me back to bootloader. I am really not sure, as to how it ended up soft-brick. The phone was bought through Vodafone Australia carrier and has never been rooted etc.
So following guide on from (forums.androidcentral.com/htc-one-m8/398427-htc-one-tampered-locked-security-warning-2.html), So from the guide I've done as followed:
- I understand I have to firstly unlocked the bootloader, which was done just fine. So after Unlocked, I could still boot to hboot and getting tampered, unlocked and S-ON (no security warning).
- Then I connect my phone to fastboot, flash twrp-2.8.5.0-k2_ul.img and clear the cache
- I then tried to access the recover mode
- The phone restarted and stuck on the HTC logo with "Starting recovery..." message at the top but nothing really loaded for a long while
- So then I tried to restart it but it just won't work, I then pulled out the battery and re-inserted it
- After that, the phone was just stuck on the battery symbol with solid orange light on (this occurs if the USB cable is connected to power or computer), I tried all button, buttons up/down power hold etc (I even tried that covering middle battery part and let the outer ones connected) but none helped
-- If I unplugged the USB cable, the battery symbol and the solid orange light would still persist until it runs out of battery
-- If I removed the battery then re-insert the battery without connecting to USB cable, it's not displaying anything regardless how long I pressed the buttons (I tried holding them for more than 3 minutes which I assumed enough?)
That's pretty much everything, I really hope someone could shed some light for me - the thing is the data is fairly crucial that it may even help me prove a legal case, where some physical threats were sent out to me. :crying:
Thanks for the assistance in advance!
Help anyone?
i guess that if you didn't break your phone as i did the datas are still there and so, have you a recovery installed like twrp ? if not do it with bootloader, all you have to do is access fastboot and recovery to use adb commands and copy datas, if you can't do that i'm afraid there is no much to do without erasing all..
colton49 said:
i guess that if you didn't break your phone as i did the datas are still there and so, have you a recovery installed like twrp ? if not do it with bootloader, all you have to do is access fastboot and recovery to use adb commands and copy datas, if you can't do that i'm afraid there is no much to do without erasing all..
Click to expand...
Click to collapse
Hi there,
Thanks for your response, so I could access fastboot before and installed TWRP, the phone became 'totally' unresponsive after I installed TWRP and restart the phone.
At first it's stuck on recovery screen loading screen, then it just won't show anything. At the moment, I am wondering if there is any way to recover the internal storage data. I have contacted local HTC service center about the issue and they recommended me to go back to Australia (where I bought the phone) since they don't sell this model here in Indonesia (nearest country selling this model would be Singapore or Malaysia) - so yeah not much help from them as well.
Any other thought?
One SV does not respond
sorry wrong topic...