Database Users

[Q] Help! Possibly Bricked or bad internal memory

I am looking for guidance this time.....I have a Nexus s I9020 (t mobile version) and a couple weeks ago I don't know what happened really but i may have been messing around with a newer version of clockwork recovery late one night .... then the phone wouldn't boot past the google screen and I couldn't do anything to fix it... I tried to figure things out the next day and this is a list of things i have figured out...
1. in clockwork it can't mount anything....like anything at all pertaining to the internal memory/storage
2. I was tired and irresponsible
3. I tried fastboot just about everything
4. I tried flashing newer/older versions of clock work......nothing worked
5. I have tried downloading and installing roms via adb and fastboot but an error message comes up...
6. now this I know is retarded but make fun of me as you will... I fastboot locked the device......i know stupid because now when I type in fastboot oem unlock it hangs and does nothing after I check unlock on the phone...
I can get into fastboot mode and it says no boot or recovery img?
now if I had access to the internal memory I would def. be able to go back to stock but there in lies the problem what on earth can i do to make this thing a paper weight?

this is what i'm talking about, the bootloader doesn't unlock it just hangs .... any thoughts?
"w w w.youtube.com/watch?v=C4cS0kMj4AI"

[Q] Acer Iconia A200 not working.

Sorry for the incorrect forum, but it appears there is no such forum for my specific device.
So story goes, I rooted it about 6 months back, lost the charger and stopped using it for maybe 2 months, found the charger yesterday, turned it on, was prompted with a System Update upon connecting to the internet, update failed, tried to do a hard reset (pwr, vol +, lock button) - it returned the message "Unrecoverable Bootloader Error (0x19000008)"
After receiving this message, I am unable to boot the device, it hangs at the "Iconia Tab" splash screen.
I tried various methods found online, including one where I put the device in the "fastboot mode" with the series of buttons previously mentioned, went as far as trying to execute the command "fastboot oem unlock" and other variants of the same command or related commands, and all of them lead me to "< waiting for device >".
This puts me in an uncomfortable position, as I am fairly tech-savvy, and normally capable of knocking out minor inconveniences such as this one.
I am fairly familiar in the android/rooting/rom'ing world with phones, and the methods used for this device were very unfamiliar, and confusing. Normally I'd just use the fastboot files to restore it to stock, and be done with it, the methods with this tablet are confusing and most solutions people have posted have been unsuccessful in my aid to fixing this.
So I ask you ladies and gentlemen, what can I do?
Any and all help is greatly appreciated, and thank you in advance.

PwnFx said:
Sorry for the incorrect forum, but it appears there is no such forum for my specific device.
So story goes, I rooted it about 6 months back, lost the charger and stopped using it for maybe 2 months, found the charger yesterday, turned it on, was prompted with a System Update upon connecting to the internet, update failed, tried to do a hard reset (pwr, vol +, lock button) - it returned the message "Unrecoverable Bootloader Error (0x19000008)"
After receiving this message, I am unable to boot the device, it hangs at the "Iconia Tab" splash screen.
I tried various methods found online, including one where I put the device in the "fastboot mode" with the series of buttons previously mentioned, went as far as trying to execute the command "fastboot oem unlock" and other variants of the same command or related commands, and all of them lead me to "< waiting for device >".
This puts me in an uncomfortable position, as I am fairly tech-savvy, and normally capable of knocking out minor inconveniences such as this one.
I am fairly familiar in the android/rooting/rom'ing world with phones, and the methods used for this device were very unfamiliar, and confusing. Normally I'd just use the fastboot files to restore it to stock, and be done with it, the methods with this tablet are confusing and most solutions people have posted have been unsuccessful in my aid to fixing this.
So I ask you ladies and gentlemen, what can I do?
Any and all help is greatly appreciated, and thank you in advance.
Click to expand...
Click to collapse
Will it boot to the stock recovery? If so, do some searching for a a200 rom or update. If it's an update, then you'll need to decrypt it (look in the Themes and Apps forum for the decrypting tool. It should be one of the first threads). After decrypting, open the zip, and pull the "update.zip" (do not extract), and copy that update.zip to your Ext SD card. Reboot to the stock recovery and see if it installs it. Might have to try several a200 update.zips before one works.

Moscow Desire said:
Will it boot to the stock recovery? If so, do some searching for a a200 rom or update. If it's an update, then you'll need to decrypt it (look in the Themes and Apps forum for the decrypting tool. It should be one of the first threads). After decrypting, open the zip, and pull the "update.zip" (do not extract), and copy that update.zip to your Ext SD card. Reboot to the stock recovery and see if it installs it. Might have to try several a200 update.zips before one works.
Click to expand...
Click to collapse
Please correct me if I am wrong, but the power + volume + lock toggle is the method used to get to the recovery?
When I try that it gives me that bootloader error and will not proceed any further.

PwnFx said:
Sorry for the incorrect forum, but it appears there is no such forum for my specific device.
So story goes, I rooted it about 6 months back, lost the charger and stopped using it for maybe 2 months, found the charger yesterday, turned it on, was prompted with a System Update upon connecting to the internet, update failed, tried to do a hard reset (pwr, vol +, lock button) - it returned the message "Unrecoverable Bootloader Error (0x19000008)"
After receiving this message, I am unable to boot the device, it hangs at the "Iconia Tab" splash screen.
I tried various methods found online, including one where I put the device in the "fastboot mode" with the series of buttons previously mentioned, went as far as trying to execute the command "fastboot oem unlock" and other variants of the same command or related commands, and all of them lead me to "< waiting for device >".
This puts me in an uncomfortable position, as I am fairly tech-savvy, and normally capable of knocking out minor inconveniences such as this one.
I am fairly familiar in the android/rooting/rom'ing world with phones, and the methods used for this device were very unfamiliar, and confusing. Normally I'd just use the fastboot files to restore it to stock, and be done with it, the methods with this tablet are confusing and most solutions people have posted have been unsuccessful in my aid to fixing this.
So I ask you ladies and gentlemen, what can I do?
Any and all help is greatly appreciated, and thank you in advance.
Click to expand...
Click to collapse
I recommend trying in the Acer A200 forum here: http://www.acertabletforum.com/forum/forum.php Does your PC recognize the table when it's plugged in? YOu could try to reflash the bootloader. Just throwing out a couple of ideas.

[Q] htc panache fastboot helpc

Hello everyone
I have an htc Panache which is stuck on the boot screen. So I downloaded sdk and everything. The only thing that detects my phone is in the fastboot. so running fastboot devices >> shows my device model #. But after that I don't know if there is a way to root from the fastboot. After almost 3 weeks of research I am unable to find the stock rom. So I was thinking about rooting it, but adb commands don't seem to work even after numerous driver updates. If anyone can tell me some commands to turn S-ON to off from fastboot, that will be great. otherwise I don't think the device is still bricked. Thanks

Probable brickage of TN7

Hi folks,
So, after little usage due to instability caused by the Lollipop upgrade I hadn't used the TN7 in a while. Yesterday I thought I'd have a go at reconditioning it.
Background: The bootloader has been unlocked, recovery was TWRP, I'd flashed and reflashed stock ROMs of KitKat and Lollipop several times previously. The main problem in Lollipop was that whilst the SD card files were showing up fine in FS Explorer, I couldn't see any of my files or folders when looking at local storage. Also, Google Play Services refused to update (or install using an APK).
Yesterday I grabbed the factory ROM from the nVidia site to do a full factory install and reset. I followed the instructions, flashing the recovery, boot, system, userdata, staging blob and dtb in that order. I then rebooted and...nothing. No power (or so it appears), no boot screen, no ability to get back into the bootloader, nada, zilch. When I read back through the flash commands I noticed that the final part of flashing the system image failed, which could well be the cause - I should have paid more attention.
I've searched all over and tried multiple options to get the TN7 to boot or show some signs of life. I don't even get an LED showing when plugged into a wall socket to charge.
The device doesn't show in fastboot or adb on the Mac. I did however get a small sign of life from Windows. If I hold down the power button for around 10 secs and let go, I can hear the Windows chime of a device connecting, immediately followed by a disconnect sound, the Device Manager updates but shows nothing new.
So my question is: have I completely screwed the pooch, or is there something that can be done to resurrect it?
Cheers for reading,
Gray

Evil Penguin said:
Hi folks,
So, after little usage due to instability caused by the Lollipop upgrade I hadn't used the TN7 in a while. Yesterday I thought I'd have a go at reconditioning it.
Background: The bootloader has been unlocked, recovery was TWRP, I'd flashed and reflashed stock ROMs of KitKat and Lollipop several times previously. The main problem in Lollipop was that whilst the SD card files were showing up fine in FS Explorer, I couldn't see any of my files or folders when looking at local storage. Also, Google Play Services refused to update (or install using an APK).
Yesterday I grabbed the factory ROM from the nVidia site to do a full factory install and reset. I followed the instructions, flashing the recovery, boot, system, userdata, staging blob and dtb in that order. I then rebooted and...nothing. No power (or so it appears), no boot screen, no ability to get back into the bootloader, nada, zilch. When I read back through the flash commands I noticed that the final part of flashing the system image failed, which could well be the cause - I should have paid more attention.
I've searched all over and tried multiple options to get the TN7 to boot or show some signs of life. I don't even get an LED showing when plugged into a wall socket to charge.
The device doesn't show in fastboot or adb on the Mac. I did however get a small sign of life from Windows. If I hold down the power button for around 10 secs and let go, I can hear the Windows chime of a device connecting, immediately followed by a disconnect sound, the Device Manager updates but shows nothing new.
So my question is: have I completely screwed the pooch, or is there something that can be done to resurrect it?
Cheers for reading,
Gray
Click to expand...
Click to collapse
Hi,
It can be fixed via apx mode.
Download drivers and switch to apx mode.
Follow instructions http://mobileviandroid.blogspot.in/2015/07/nvidia-tegra-note-7-apx-images.html?m=1
Remember to change your device serial number as mentioned in instructions.
I also faced the same problem as you are facing now. It fixed. If you need any help further just post. God bless. Hope it helps

DJDON1302 said:
Hi,
It can be fixed via apx mode.
Download drivers and switch to apx mode.
Follow instructions http://mobileviandroid.blogspot.in/2015/07/nvidia-tegra-note-7-apx-images.html?m=1
Remember to change your device serial number as mentioned in instructions.
I also faced the same problem as you are facing now. It fixed. If you need any help further just post. God bless. Hope it helps
Click to expand...
Click to collapse
Lol that site ripped my Tutorial! how nice of them, You should of linked the person to https://forum.xda-developers.com/nvidia-tegra-note-7/general/nvidia-tegra-note-7-apx-images-t3149839

Essential Phone Half-Bricked?

Hello everyone,
I have a very peculiar problem with getting my Essential Phone to work again. It was lying around for roughly two years as I switched to another phone. Seeing as one of my relatives needs a new phone and has really low requirements I thought I could try to set it up again. I downloaded the official drivers again (Version 1.0.0 I think) as well as the last official release of fastboot images (February 2020).
Before I switched to a new Phone I had the Essential running with Lineage OS and remember wiping it with fastboot -w after I got the new device.
Now when I try to flash anything the device won't respond. It shows up when fastboot devices is used in the bootloader, but all fastboot commands get no answer whatsoever. I then switched from the official fastboot drivers to the latest android drivers which then gave me the sending x to y message when I try to flash anything, but nothing actually happens.
Interestingly enough, I can reboot to bootloader just fine and the Lineage Recovery is still accessible eventhough it shows an:
E: Failed to bind mount /mnt/staging/emulated/media/0 on storage/emulated: No such file or directory
on the bottom which leads me to believe that my device partitions may be corrupted outside of the recovery partition and the phone is bricked. In recovery adb commands can be used and I can reboot to bootloader for example.
When trying to sideload via the "Appy Update" function of the Lineage Recovery, I get an:
Error applying update: 26 (ErrorCode::kDownloadMetadataSignatureMismatch))
everytime. I tried different methods and Roms but nothing worked so far.
Can anyone help me with regards to bypassing signature verification entirely or point me in the direction of another solution?
Thanks for reading, I hope you have a nice day!

McMeth said:
Hello everyone,
I have a very peculiar problem with getting my Essential Phone to work again. It was lying around for roughly two years as I switched to another phone. Seeing as one of my relatives needs a new phone and has really low requirements I thought I could try to set it up again. I downloaded the official drivers again (Version 1.0.0 I think) as well as the last official release of fastboot images (February 2020).
Before I switched to a new Phone I had the Essential running with Lineage OS and remember wiping it with fastboot -w after I got the new device.
Now when I try to flash anything the device won't respond. It shows up when fastboot devices is used in the bootloader, but all fastboot commands get no answer whatsoever. I then switched from the official fastboot drivers to the latest android drivers which then gave me the sending x to y message when I try to flash anything, but nothing actually happens.
Interestingly enough, I can reboot to bootloader just fine and the Lineage Recovery is still accessible eventhough it shows an:
E: Failed to bind mount /mnt/staging/emulated/media/0 on storage/emulated: No such file or directory
on the bottom which leads me to believe that my device partitions may be corrupted outside of the recovery partition and the phone is bricked. In recovery adb commands can be used and I can reboot to bootloader for example.
When trying to sideload via the "Appy Update" function of the Lineage Recovery, I get an:
Error applying update: 26 (ErrorCode::kDownloadMetadataSignatureMismatch))
everytime. I tried different methods and Roms but nothing worked so far.
Can anyone help me with regards to bypassing signature verification entirely or point me in the direction of another solution?
Thanks for reading, I hope you have a nice day!
Click to expand...
Click to collapse
I've been reading around a little, it seems like it could be a recovery issue? try the official lineage recovery if you're not already. If you can get fastboot working at all try to reflash the stock rom and go from there.

I had a similar problem. Use a windows computer with the essential drivers (you can download from reddit) and use the official cable

DO NOT use the cable supplied with the Essential phone for data transfer, it is likely to brick your phone. Use a high quality one from a reputable manufacturer!