[Alcatel V860] Bricked, no access to recovery - General Questions and Answers

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?

Related

Did I hard brick?

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.

[Q] TF700 Unrecoverable bootloader error 0x00000008

signature Mismatch Unrecoverable bootloader error 0x00000008
unlocked & rooted.
had TWRP TeamWin installed
tried to install a new Rom & got the above error
wiped data & now only the following shows.
signature Mismatch
Unrecoverable bootloader error 0x00000008
is this unit dead & not fixable?
I bought from Amazon so maybe returnable? if not fixable, had for a week now.
If you can't get into fastboot or recovery then it is hardbricked.
le rustle face
Keion said:
If you can't get into fastboot or recovery then it is hardbricked.
le rustle face
Click to expand...
Click to collapse
have never used fastboot icon but it dont boot that far for the icons to show anymore.
but no recovery as it can't continue far enough for TWRP TeamWin splash screen to show up
as i guess the bootloader needs to work to get past this stage.
as far as I read there are no fixes for bad bootloader. but this was posted in feb & march of 2012 so I was hoping for new info & maybe a fix.
this is most probably the reason why asus voids your warranty when you unlock. I dont trust any other recovery than ClockWorkMod.
Maybe toggle signature verification to disabled? Or if your able to still go into recovery, sideload the latest firmware from asus site and flash it from recovery?
..........
Sorry just read the above comment... Hopefully someone here can help you out. Good luck to you!
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
atc3030 said:
Gtalk Me before you send it. I think I had the same problem and if so i can fix it for you. Gtalk: [email protected]
Click to expand...
Click to collapse
try contacting this guy and see if he can help.
for what its worth I flashed with twrp and had no issues.
lafester said:
try contacting this guy and see if he can help.
for what its worth I flashed with twrp and had no issues.
Click to expand...
Click to collapse
Would have been nice to have a backup bootloader, holding down buttons to switch to & repair
if asus can repair im sure there is a way.
I am not able to get into recovery any longer.
seems like the clockworkmod has an option to disable signature option, but I can't even get to twrp
I made a big mistake & did this flashing AOKP 4.1.1 with twrp I think it wiped the twrp recovery app & messed up the bootloader now.
im sure there is a repair for fixing the bootloader as if it is sent to asus they can repair it for like $50 ;(
Any steps to take to help repair this would be great
NeoGodSpeed said:
Would have been nice to have a backup bootloader, holding down buttons to switch to & repair
if asus can repair im sure there is a way.
I am not able to get into recovery any longer.
seems like the clockworkmod has an option to disable signature option, but I can't even get to twrp
I made a big mistake & did this flashing AOKP 4.1.1 with twrp I think it wiped the twrp recovery app & messed up the bootloader now.
im sure there is a repair for fixing the bootloader as if it is sent to asus they can repair it for like $50 ;(
Any steps to take to help repair this would be great
Click to expand...
Click to collapse
your issue was with the pre alpha AOSP rom, not with the TWRP recovery. TWRP recovery also allows no signature checking.
okantomi said:
your issue was with the pre alpha AOSP rom, not with the TWRP recovery. TWRP recovery also allows no signature checking.
Click to expand...
Click to collapse
cool, nice to know.
seems there must be a way to do something as if you hold the right vol button + power it connects to PC & shows in windows 7 Device Manager
but not the same as if the system was booted in to android as it shows the internal & sdcard. this dont show the interal or sdcard but shows it's connected. wonder if asus connects to the port where the charging cable or dock go's to repair bad bootloaders.
tried adb.exe devices but it dont show anything connected still. even tried the asus android bootloader interface 4.0.0.5 driver.
NeoGodSpeed said:
cool, nice to know.
seems there must be a way to do something as if you hold the right vol button + power it connects to PC & shows in windows 7 Device Manager
but not the same as if the system was booted in to android as it shows the internal & sdcard. this dont show the interal or sdcard but shows it's connected. wonder if asus connects to the port where the charging cable or dock go's to repair bad bootloaders.
tried adb.exe devices but it dont show anything connected still. even tried the asus android bootloader interface 4.0.0.5 driver.
Click to expand...
Click to collapse
I'm really sorry this happened to you, but you probably knew you were venturing into very untested ground.
Are you posting in the Pre alpha AOSP thread? That might be more productive for you. It seems there have been at least 3 hardbricks from flashing that rom.
polish_pat said:
this is most probably the reason why asus voids your warranty when you unlock. I dont trust any other recovery than ClockWorkMod.
Click to expand...
Click to collapse
This does not sound like a recovery issue, but rather a bootloader checksum failure. I know you are probably not bashing TWRP, but it should be noted that this NOT a borked recovery
NeoGodSpeed said:
Would have been nice to have a backup bootloader, holding down buttons to switch to & repair
if asus can repair im sure there is a way.
I am not able to get into recovery any longer.
seems like the clockworkmod has an option to disable signature option, but I can't even get to twrp
I made a big mistake & did this flashing AOKP 4.1.1 with twrp I think it wiped the twrp recovery app & messed up the bootloader now.
im sure there is a repair for fixing the bootloader as if it is sent to asus they can repair it for like $50 ;(
Any steps to take to help repair this would be great
Click to expand...
Click to collapse
Accessing the bootloader on phones is done at a much lower level, not sure about tablets. JTAGing is usually the way bootloader is restored when hard bricked (a serial connection). I have been googling just to see what is out there... but pretty limited info on bootloader recovery/overwrite for any of the asus tablets.
NeoGodSpeed said:
cool, nice to know.
seems there must be a way to do something as if you hold the right vol button + power it connects to PC & shows in windows 7 Device Manager
but not the same as if the system was booted in to android as it shows the internal & sdcard. this dont show the interal or sdcard but shows it's connected. wonder if asus connects to the port where the charging cable or dock go's to repair bad bootloaders.
tried adb.exe devices but it dont show anything connected still. even tried the asus android bootloader interface 4.0.0.5 driver.
Click to expand...
Click to collapse
Keep digging. The fact that your PC can see the device is a start. Does win7 load the device drivers?
Poser said:
This does not sound like a recovery issue, but rather a bootloader checksum failure. I know you are probably not bashing TWRP, but it should be noted that this NOT a borked recovery
Accessing the bootloader on phones is done at a much lower level, not sure about tablets. JTAGing is usually the way bootloader is restored when hard bricked (a serial connection). I have been googling just to see what is out there... but pretty limited info on bootloader recovery/overwrite for any of the asus tablets.
Keep digging. The fact that your PC can see the device is a start. Does win7 load the device drivers?
Click to expand...
Click to collapse
Im not bashing anyone or any product, was my fault, no one elses. I have been modding for 20 years & should have known better & done more research into what I was doing here. We are warned all over these forums that everything we do is a risk. you dont blame anyone but your self.
JTAGing would be the way to repair, I agree, I just haven't found anything for the transformers yet. been looking, but nothing out there that someone has connected & got to work. just talk about jtag & transformer. there are some arm7 jtag programmers im sure some software could be made, but I think we are far from knowing how to talk to the bootloader in a low level, im sure some are trying to reverse engineer to get to the boot loader.
yes, windows loads the drivers when you hold the right vol button + power. you hear it connecting if windows 7 has speakers on. the drivers do have to be installed for this to work, I think the device is called APX in device manager.
I have posted in the other forum about this, but like I said above, not a products fault.
I would like to thank everyone for there input.
Poser said:
This does not sound like a recovery issue, but rather a bootloader checksum failure. I know you are probably not bashing TWRP, but it should be noted that this NOT a borked recovery
Accessing the bootloader on phones is done at a much lower level, not sure about tablets. JTAGing is usually the way bootloader is restored when hard bricked (a serial connection). I have been googling just to see what is out there... but pretty limited info on bootloader recovery/overwrite for any of the asus tablets.
Keep digging. The fact that your PC can see the device is a start. Does win7 load the device drivers?
Click to expand...
Click to collapse
The Volume Up + Power button combination allows you to put the device in APX mode but it's still useless without a working NVflash solution.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
thanks for the info Pretoriano80
I will keep researching for Jtag & bootloader recovery & waiting for nvflash to be ported to the transformer series Doesn't even seem JTAG would even be needed just a port of nvflash, jtag would be a marketing thing most likely after reseaching other tablets that have unlocked bootloader, they just use nvflash if im correct in my finding here. as if it can be fixed down the road then no worries anyone would have as it could be fixed if a JTAG or nvflash portedwas made, bought & was plug & play install not taking apart tablet, just plug into docking station port & plug usb cable to computer install drivers & JTAG software GUI interface software made for windows 32bit & 64bit plus Linux support also or just nvflash ported. im sure there are people already looking into this.
I sent back the unit to Amazon will get another unit late thursday.
I think I will only root this unit, until I understand & research more on Android devices like I should have from the start my mistake, No one else, as this was my fault & no one else.
everyone should know everything is at risk, if the bootloader is unlocked. my new replacement will only be rooted, till I see a must have for a unlocked bootloader. rooted seems to be a must have. but not a unlocked bootloader at this stage of the transformer. maybe at some point down the road, it would be a must have, but time will tell.
:fingers-crossed: Let me know if any of you are looking into JTAG & or nvflash for the tranformer, im sure nvflash is the way to go & not jtag
Poser said:
This does not sound like a recovery issue, but rather a bootloader checksum failure. I know you are probably not bashing TWRP, but it should be noted that this NOT a borked recovery
Click to expand...
Click to collapse
Is there a version of cwm yet? Although it has some really great features, I still don't quite trust twrp after causing all of those soft bricks after recovering by not properly restoring /boot
Sent from my Nexus 7 using xda premium
Thread cleaned. Take the fighting out to the parking lot boys....

No os and no recovery!

I would gladly appreciate and donate to anyone who can step-by-step guide Me to reviving My Shield Tablet 32GB LTE US! I had TWRP but somehow cannot make it back into it, all i get is the bootloop or the Fastboot screen. My laptop runs on Win8 and most of the time can't or won't recognize the tablet and when it does, it can never seem to find the files I'm trying to push to it. Someone told Me it can never be truly or permanently bricked and for about 6 months I gave up but I miss having a bigger screen, games, all the storage, etc. I need My tablet back and NOBODY is giving Me a clear way to do it as I AM pretty much a noob at all this. This is the absolute most stressful/tedious root I had ever had to do and shortly after getting TWRP and achieving root access through KingRoot, I accidentally wiped My partition and then locked Myself out of recovery... If ANYONE can help, I would ULTIMATELY appreciate it. Thank You.
Mmmmmmmh your tablet have unlocked bootloader?
If yes probably you can do something with ADB....
if not...i think you can trash your tablet ;_; at least if you don't solder an eprom flasher, but it's out of my possibility and need sort of reverse engeneering
If you can actually get to the fastboot menu, you should be good to go. You'll have to unlock your bootloader, but once you do that you can flash the recovery partition or flash an entire recovery image. Do respond if you're looking to do so.
I unlocking the bootloader was the very first thing I did. Yes, i need to know exactly where to get the image, where to save it, and how to push it thru adb please.
I do have accidental insurance... But i don't want to do that.
If you go to the link in my signature, you will find guides for flashing the recovery partition (among other things) as well as download links for the recovery images.
If you lack installations for adb/fastboot, there's a tool on XDA called Minimal ADB and Fastboot. I'd recommend using it.
can you help me? I have same issue.
My tablet only shows up as APX in device manager.
Cant boot up to NVIDIA logo, Cant boot up to fastboot nothing.
It was unlocked before now.
No bootloader, no luck. Only NVIDIA can help you now.
http://forum.xda-developers.com/shield-tablet/help/help-help-bricked-shield-tablet-original-t3313428
I believe I can get it working again somehow by puting the recovery on the SD card seeing how mine came with a usb adapter
Reflash twrp via fastboot

Leagoo T565 (Mediatek?) bricked

Hi,
while trying to root my Leagoo T565 phone I must have mixed up something and/or gotten the wrong file to flash - in any case, the phone is now as bricked as I ever made it happen to any device: When turned on, it gets into a boot loop (before starting the OS, probably because there isn't any left), but I can't get into fastboot or recovery either (none of the keys have any effect.)
I came as far as "fastboot oem unlock", which completed fine. But as one of the next steps I must have flashed a wrong bootloader by mistake.
Can anyone think of a way I could possibly recover the phone? I'm at a loss here since I can't even get into fastboot any more.
Is there still a way or might I as well toss the device?
Any help would be much appreciated!
Regards

Question Recover bricked moto stylus 5g after flashing TWRP

Hey guys, I recently rooted my stylus 5g and went to install TWRP. I was able to get it to boot to TWRP, but I believe within TWRP I did the flash wrong as now my device is hard bricked. I cannot get it to show the initial logo, get to the bootloader or I think even EDL. I've tried the Lenovo recovery tool and the Moto all-in-one tool, but essentially all I get now is a black screen.
Any input on what I can do to either diagnose and possibly recover my device? I have the original firmware downloaded, but without being able to get to the bootloader, recovery, or even EDL, I'm at a loss as to how to proceed. I did grab a blankflash for the device, but I'm not clear on how to begin to use that to move forward.
Thanks for any advice you can provide.
-Ryan
Hello friend, honestly I am new to this. In fact I'm looking for how to unlock my moto g stylus 5g xt2131-1 from metropcs to use it with a mobile operator in Colombia. But given your problem, and everything I've researched recently, I would say you could check this video:
in which revive a moto g8+, although it is a different version, it should work if you do the steps as indicated.
Did you ever figure this out? Mine is also hard bricked at the moment. I've been trying to get it to the 9008 mode so I can blankflash but I've had no luck. I see on some phones there is a pair of pins on the board that need to be shorted but I'm not sure which ones. I just bought an edl cable on amazon which should be here tomorrow, hopefully that will get it in the correct mode.
duffman452001 said:
Did you ever figure this out? Mine is also hard bricked at the moment. I've been trying to get it to the 9008 mode so I can blankflash but I've had no luck. I see on some phones there is a pair of pins on the board that need to be shorted but I'm not sure which ones. I just bought an edl cable on amazon which should be here tomorrow, hopefully that will get it in the correct mode.
Click to expand...
Click to collapse
could you let me know if that works. im struggling with this as well
Absolut_Malarkey said:
could you let me know if that works. im struggling with this as well
Click to expand...
Click to collapse
No luck. Only change with the EDL cable is that if I plug the phone in via the cable with the battery unplugged it was a pretty rapid blink vs before it would blink every 10 seconds or so if I held the power button while plugged in to power. The button on the EDL cable had no effect. I then tried to short out every combination of pads on the board similar to the video above. No luck, it just seems to be completely toast. All I did from TWRP is format data and reboot to fastboot. Dead since then.
Is there any more information on this subject?
View attachment IMG_20220717_121138987~2_66348_SP-8988.jpg
Here is the pcb picture. Not sure if the number 2 has any significant meaning but someone told me it was one of those points with one by the battery connector. Anyone have any info on this it would be greatly appreciated.
EDL test points and blank-flash boost mobile
Here are the edl (emergency download mode) test points for Motorola Moto G Stylus 5G XT2131.
forum.xda-developers.com
duffman452001 said:
No luck. Only change with the EDL cable is that if I plug the phone in via the cable with the battery unplugged it was a pretty rapid blink vs before it would blink every 10 seconds or so if I held the power button while plugged in to power. The button on the EDL cable had no effect. I then tried to short out every combination of pads on the board similar to the video above. No luck, it just seems to be completely toast. All I did from TWRP is format data and reboot to fastboot. Dead since then.
Click to expand...
Click to collapse
thank god i saw this, i was getting ready to flash TWRP even just unlocked my bootloader and everything, not taking this chance! i honestly got so many phones to root, unlock the bootloader, flash new roms, but litterly all of them have at least one problem.. (my devices range from lg to motorola, zte, htc, samsung...) i had a moto g play, but i tried to flash TWRP from magisk, and looked like it was stuck in boot loop, then used motorola tool, and fried it.. litterly didnt show any sign of life after, (I dont thing it was motorlas tool, i think it had something to do with me trying to flash TWRP, anyway, the screen looks like an explosion! had more fun hitting it with a rubber mallet than getting frusterated, and maybe fixing it...
liammmmnnnn said:
thank god i saw this, i was getting ready to flash TWRP even just unlocked my bootloader and everything, not taking this chance! i honestly got so many phones to root, unlock the bootloader, flash new roms, but litterly all of them have at least one problem.. (my devices range from lg to motorola, zte, htc, samsung...) i had a moto g play, but i tried to flash TWRP from magisk, and looked like it was stuck in boot loop, then used motorola tool, and fried it.. litterly didnt show any sign of life after, (I dont thing it was motorlas tool, i think it had something to do with me trying to flash TWRP, anyway, the screen looks like an explosion! had more fun hitting it with a rubber mallet than getting frusterated, and maybe fixing it...
Click to expand...
Click to collapse
I did end up recovering mine via the test points https://forum.xda-developers.com/t/...ank-flash-boost-mobile.4469613/#post-87181339
duffman452001 said:
I did end up recovering mine via the test points https://forum.xda-developers.com/t/...ank-flash-boost-mobile.4469613/#post-87181339
Click to expand...
Click to collapse
my moto g stylus is thru T-Mobile, i heard that its different, lol i just honestly dont want to brick mine, im also kinda new to this stuff, so if something is gonna go wrong even with steps its me LOLL, also im not meaning to be mean if you take it that way
deleted.
liammmmnnnn said:
my moto g stylus is thru T-Mobile, i heard that its different, lol i just honestly dont want to brick mine, im also kinda new to this stuff, so if something is gonna go wrong even with steps its me LOLL, also im not meaning to be mean if you take it that way
Click to expand...
Click to collapse
That thread for the 2131 EDL is correct, ive used it.
wickedxjay said:
That thread for the 2131 EDL is correct, ive used it.
Click to expand...
Click to collapse
You used it it on the xt2215-4?

Categories

Resources