Related
YES PLEASE POST QUESTIONS IN THIS THREAD RATHER THAN CREATING YOUR OWN "PLEASE HELP MY BRICK" THREAD
PLEASE READ AND RESEARCH FIRST AND THEN IF YOU MUST POST GIVE AS MUCH INFO AS POSSIBLE!Why am i making this thread? Aren't there already tons of them?
Exactly!
There are a couple a week and many times the old threads have already answered
all the questions needed to recover the brick, or explain why it cant be. So I'm here
to alleviate the clutter and hopefully help people more quickly.
Let's try to define a "brick"
People seem to say there is a "hard brick" and a "soft brick," to me that's just nonsense.
A brick is a brick. when you have no access to your recovery or your bootloader
then you have a brick. This is your phone wont turn on and it cant be recovered without j-tag equipment. (not for a novice)
Now you have no more than a brick on hand, or a pretty paperweight. What most
people have is a "soft brick" which really isn't a brick rather a phone that isn't
working as it should, but still a completely recoverable phone. A phone that doesn't
boot is just that, not a soft brick as it should be easy to fix and not to be used
as a paperweight. But i'll stop quibbling about the terms now as at least we
have an understanding.
A couple things first:
I implore you to read through a few threads on this as oh so many answers are there.
These are just a few from the last month or so!
HERE HERE HERE HERE HERE HERE HERE HERE HERE HERE HERE HERE HERE HERE
As apparent as it may seem to those who frequent this forum, clutter only lessens
the experience here. Many never read the forum rules or listen to the mods. I'm
not trying to be a **** here, but we do need to at least attempt to keep the threads
clean. I understand that there is a lot to sift through but i can assure everyone
that questions will be answered faster and more clear to those who at least attempt
to do a little homework... rant over, let's fix those bricks!
So your phone wont boot...
you will need to know a few things about your phone as will the people helping you.
Let's make a list of needed information...
1) Are you rooted? Which method did you use to obtain root?
Click to expand...
Click to collapse
Different methods of rooting can give a different outcome. Importantly having true
radio s-off or not, and with some methods (visionary) that could cause a brick in itself.
If you cant remember how you rooted thats fine, information given here will help.
2) Can you access either bootloader mode or recovery on your phone?
Click to expand...
Click to collapse
If you can, then chances are your phone can be fixed. If you don't know how to
get into these modes - simple way is to power on while holding volume down.
This is the bootloader (also known as Hboot or SPL - secondary program loader)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is an example of the screen
The important information to take out of here is the engineering DZ Hboot, radio
secure flags removed (s-off) and the 26.13.04.19_M radio (commonly .19 radio)
You can see it is in fastboot mode (in red) and to scroll up and down through the
options you use the volume rocker, selecting an option with the power button.
if you choose bootloader the screen will look like this:
Obviously some bootloaders will read different depending on radio, Hboot version,
including shipped verse engineering, s-on/off, etc. And I believe without an ENG
Hboot you don't get the system info option.
3) Write down everything you can on this screen, including *SYSTEM INFO*
if you have it and the output from *IMAGE CRC*
Click to expand...
Click to collapse
Please realize the more information the better, give everything but personal info,
really just the IMEI in the *SYSTEM INFO* option. (which really isn't all that personal) This leads to:
4) Which recovery do you have? Stock? Clockwork? 4EXT? Version #...
Click to expand...
Click to collapse
If you don't know, check!
5) What happened recently or just prior that may have cause this?
Click to expand...
Click to collapse
This may be anything to i was updating angry birds to i tried turning it on and it
wouldn't. If your answer is i dropped it in the toilet and just plugged it into an outlet
to dry, i cant help you to much...
6) Pull a logcat of the bootloop
Click to expand...
Click to collapse
If you're not sure how to pull a logcat HEREare some quick pointers. You will need the Android
SDK, and ADB.exe download in platform tools. THIS GUIDE will help setting up
fastboot and ADB, both are very helpful and needed tools for Android users
Pulling a logcat
Once you have ADB up and running open a command prompt (Linux and OSX users
will have different steps) where ADB.exe is located on PC by holding shift and right-
clicking in the folder > choose open command here. In CMD type:
Code:
adb devices
if you see your serial number then proceed, if not we need to troubleshoot.
Code:
adb logcat > logcat.txt
this will create a text file in the directory CMD is in named logcat.txt, you can name
the .txt what you'd like by changing the logcat.txt to whatever, maybe output.txt
now to stop it just hit (Ctrl + c) the control key and c key at the same time. Now
upload it to XDA, or put in code wraps, or post the link to the pastebin.
Code:
This is written in code wraps and [URL="http://pastebin.com/"]HERE YOU WILL FIND PASTEBIN[/URL]
***Please provide as much of this information as you can in your first post!***
What can i do to recover my phone already!
You are probably very frustrated right now, very understandable... please don't yell
at, or complain about, or blame your situation on those trying to help. No one is forcing
you to take the help given here and the last thing i want to hear is your complaints
about me/XDA/the world because your phone is toast and you need j-tag equipment.
Just wanted to get this out there, although its rare, don't blame others for your mistakes
or your misfortunes, thanks
Everyone has a unique situation! This is not a solve all for everyone!
Click to expand...
Click to collapse
Getting down to business...
Slowly lets work through the more obvious steps first, as simple as they seem to some,
it will fix most peoples problems. I will start by assuming you are rooted, those that
aren't i will add some more info....
First thing to do is to take out the battery.
Click to expand...
Click to collapse
What... well i said I'm starting slow. This is more for when a phone wont boot into
anything, no operating system, no recovery, no Hboot. If it does not, the first thing
to check is the battery. When you plug it in does the LED charge indicator come
on? Does the LED ever change to green? Have you tried different chargers? USBs?
Different batteries? It may be a hardware fault such as a bad USB port or charger.
I'm not going to spend more time on this case, but if you are finding yourself in this
situation, try a few things out first, if nothing works then feel free to post here and
I or some other helpful XDA member will attempt to troubleshoot more.
So your in a bootloop - rooted phones -
This is your phone gets past HTC/T-Mobile splash screen and gets stuck in the ROM's
boot animation. This tends to be most common issue for people new to android and
is very easily fixed. This may be caused by various things such as bad flash of the
ROM if its the first time booting into it. Maybe you adjusted DPI or overclocked too
much. Well, many possibilities, so first boot to recovery and wipe all (you will loose
personal info here) No matter the recovery you have (except stock) there are options
to wipe system, cache, dalvik, data. Do this, and while you are at it why not format
partitions, easy if in 4ext recovery. And for safe measure USE THIS SUPERWIPE
Or the AIO TOOL is proving to be great as well.
*If you would like you can always first try flashing the ROM or kernel first without
a wipe, or only wiping cache and dalvik, this may be a cure without loosing data*
After all this wiping and formatting we need to flash the ROM again. If you continually
have problems try a different ROM (something known stable) or a new download.
Every good ROM developer should have a MD5sum posted with their download. A
matching MD5sum will make sure what you flash will be what the developer uploaded
and didn't get corrupt when you downloaded it. GREAT MD5 TOOL FOR WINDOWS
And THIS ONE WILL ALSO CHECK SHA-1
If you are still getting a bootloop after all this then more info will be needed, post
here with your problem and all information you can give about your phone. Also if
you have ADB access then please post a logcat as well (pastebin or code wraps!)
Code:
This is written in code wraps, and [URL="http://pastebin.com/"]HERE YOU WILL FIND PASTEBIN[/URL]
If you don't know how to post a logcat then you didn't read the first post!
If your not sure you are doing any of the above correctly feel free to ask for more
details otherwise see THIS GUIDE for a better understanding
Stuck in a bootloop - not rooted-
You will have far less opportunities to fix this with an non-rooted phone. The first
thing you may want to try is boot into safe mode (hold 's' button on keyboard while
powering on. If this works then you more than likely have a malicious app, try and
remove the most recently installed or most recently updated.
If this wont work then we'll need to boot into Hboot (volume down while powering
on) Then choose factory reset. You will loose all data (except whats on SD card,
or whats stored in the cloud) This will be like the day you first got your phone.
If that doesn't help the last thing you can try is to flash the latest RUU (ROM Utility
Update) from HTC.COM or other options HERE as well.
Not all phones are made equal...
If you have ADB access through recovery it may be helpful to know what eMMC
you have. There were two different chips made for the vision; SEM04G and M4G2DE,
the latter being a chip prone to failure by no fault of the user.
open a command prompt anywhere on computer and type
Code:
adb devices
if you see your serial # then you have access to ADB, if not more troubleshooting needed
now continue on
Code:
adb shell
dmesg | grep mmc0
if the output is something similar to this:
mmc0: failed to get card ready
mmc0: reinit card
mmc0: Starting deferred resume
mmc0: Deferred resume failed
Click to expand...
Click to collapse
Then chances are your eMMC is fried, dead, and unrecoverable. :crying: sorry
To test which chip you have, again in CMD type
Code:
adb shell
cat /proc/kmsg | grep 'mmc0:0001'
you should see an output ending in something like
mmcblk0: mmc0:0001 SEM04G 2.17 GiB
or
mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
Other methods
This may work better for those with a working phone wanting to check theirs:
Code:
adb shell
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
-this can be done via ADB or terminal with a working phone without booting to recovery-
I am under the impression, but haven't yet confirmed that the M4G2E (bad) chip is
made by Samsung while the SEM04G (good) chip is made by Sandisk. No guarantee
but you may be able to check this via fastboot:
Code:
fastboot oem check_emmc_mid
this should display either Samsung or Sandisk - if anyone can confirm this i would
be very appreciative!
*pulling a logcat or checking what eMMC you have will not recover any part of
your phone, just give more info about your phone and potentially help with the
troubleshooting process
*lots more to come, hopefully today or tomorrow!
More advanced measures
The previous post only suggests basic technology "fixes." While i don't consider factory
reset a fix, the outcome may be you have a working phone. These few things mentioned
above are just the first steps in recovering your brick, ALWAYS start with the basics
before moving on to more drastic measures as you can cause further damage. Of course
you may have to do this to recover your phone, my warning is to read up and ask questions!
Phone wont boot - no recovery
This is a bad sign, but in many cases flashing a new recovery via fastboot is all you need
to do. If you have an engineering SPL than proceed:
First do a test boot: boot phone into bootloader>fastboot mode>usb>open CMD
Code:
fastboot devices
See if your serial # comes up, if so proceed if not READ THIS (POST #3)
Code:
fastboot oem jump
Copy and paste the output, give it 5-10 minutes, if your phone sits at HTC splash then:
DOWNLOAD THIS RECOVERY to computer, extract the image noting the folder its in
Boot phone into bootloader>fastboot mode>usb>open CMD where recovery.img is
Code:
fastboot erase recovery
Note if there is an error or not
Code:
fastboot flash recovery recovery.img
If everything worked then:
Code:
fastboot reboot-bootloader
From here choose recovery, once rebooted go ahead and format all
*If you still cant boot into recovery post here!
Still i cant restore my phone!
Things are looking grim, but there still may be hope. If you have a working Hboot there
will always still be a chance. I always recommend ROOTING A PHONE RIGHT WHEN YOU GET IT
Even if your only reason is to recovery when things go bad, having an engineering
bootloader is just the cats meow. So unless your eMMC is fried, we should be able
to get you up and running again!
So fresh and so clean!
Wiping clean is great and formatting is even better. If you loose recovery access
it may be hard. Thankfully fastboot can help!
Code:
fastboot erase system -w
*I'm having trouble getting fastboot format and oem format commands to work,
I'll update this post when i see what the issue is.*
If you still have a working recovery do all wipes and formatting through it. Also try
and flash THIS SUPERWIPE SCRIPT and or THE AIO WIPE TOOL
When all is failing...
It is looking like you may have a fried chip, or at the very least some severely corrupt partitions.
An eMMC that has lost read/write capabilities we cant fix, not even with j-tag :crying:
But corrupt partitions can be fixed, usually by simply reformatting. I'm working on the
fastboot commands, but you can always reflash other partitions (like you did the recovery)
-----------------Always be careful flashing firmware!!---------------------
Click to expand...
Click to collapse
Check md5sums, and know what and why you are flashing, don't jump to this step
when you're in a bootloop!
HERE ARE SOME PC10IMG.ZIPS The post explains how to flash them trough your SPL
but you can open and extract the content and then flash through fastboot. Commands:
Code:
fastboot flash radio radio.img
This will give you the .19 radio only
Code:
fastboot flash hboot hboot_7230_0.82.0000_100902.nb0
This will give you the Desire Z engineering Hboot. *if you use the G2 one change the command
Code:
fastboot flash update PC10IMG.zip
This will the whole package (preferred over SPL flashing as any error will show in CMD)
*need to change command or change name of .zip
I'm not making this thread for :good: Thanks or 5star rating, I'm doing this to help out
others. XDA members have helped me so many times in the past that this is just one
of my small contributions. All i ask of you to be respectful and share what you learn
*Hope your up and running again soon!
i would define a brick as something used to build a house..... i would describe my phone that wasn't working as a broken phone
thanks for the information that's really help full..:angel:
Everyone has a unique situation! This is not a solve all for everyone!
Click to expand...
Click to collapse
So is this a good place for solving unique situations? .. or should I start a new thread somewhere else?
I've tried to bric this thing a thousand times by all the various good posts in the forums. cant seem to get into recovery or flash new one, maybe hardware is bad?
have access through fastboot & PC10IMG, but not adb. comes back to reboot-loop, maybe recovery partition is bad?
eng hboot s-off ... kinda noob, but.
and dont want to interupt the flow of your page here, either. thanks
Not at all a disruption, this is why I'm making the thread. I want everyone who has a nonworking phone to have an easy place to share their problems and hopefully find a fix.
Haven't finished all the info in the first few posts but I hope to have many solutions covered there and if not people can dig through this one thread, instead of dozens, to find the answers they need
So on to you situation
Can you get into bootloader? I assume so being you said you have fastboot but no adb. (By the way you should have adb access in recovery) can you write down all the info I'm requesting in the op about your phone please, this will help expdiate your fix if there is one
Sent from my HTC Vision using xda premium
I can get into bootloader, but not recovery. I was able to access the stock recovery once. i'll work on the rest of the info ..
meantime, anyway to confirm good/bad hardware, eMMC? i would hate for the past week to have all been on a fried chip.
If you had adb working then you can check which emmc you have, there is one prone to failing. Also you can check system info in hboot. For now your best bet is to flash a new recovery via fastboot. I will be adding this in the first few posts when I get a moment
http://forum.xda-developers.com/showthread.php?p=27796375
See post 3
I would appreciate if you can post the information in the op as it will determine if you can even flash a recovery via fastboot or if other steps need to be taken rather then just me guessing on what to do next, the more info you can give in your first post the less questions I will have to ask making less clutter in this thread
Sent from my Nexus 7 using xda premium
yeah great. thanks
i have tried to flash new recovery multiple times .. it seems to take, but then i can never get into it, just back to reboot-loop. i have also seemingly been able to flash radio, hboot, partitions .. all via fastboot - cant get adb.
vision pvt eng s-off
hboot 0.84.2000
microp 0425
radio 26.03.02.26_m
eMMC boot
sys info:
sn 123456789
lcd so
touchpanel atmelc12_20aat
commit adbd7a75
os ver. 1.19.531.1
imei 123456789
cid 11111111
eMMc sandisk 2152 mb 4407295 sectors
image crc:
hboot 0x2a125cf4
boot 0x1b87420d
recovery 0xd4af6ad9
system 0x749ce305
#some of this has changed periodically as i've flashed this and that and back again multiple times
i have tried flashing two different CWM recoveries and the EXT_4 as well, no luck.
i seems to be able to flash different hboots at will.
at one point after other things didn't work, i ignored the 'Warning' and flashed a PC10IMG stock, which gave me the ship hboot, still s-off ..
i have tried flashing ROM.zip's directly, including CM7 and stock gingerbread - no luck. done lots of wipes.
"word is .." (not my phone) this trouble came after trying to update CM? maybe something about firmware??
not sure about root - i assume i have it, but no idea what method was used originally to root, etc
at this point i've tried what i know and it seems beyond me <am a hobbyist>, so i'm looking for some insight as to what might be going on - if it's worth still trying to fiddle with it or if it's for target practice ..
thanks for the thread.
When you say your trying to flash cm7 directly are you flashing it as an update via fastboot? Do you have any old nandroid backups made in yaffs2? If you do you can flash the images in fastboot and see what happens
It sounds as if the recovery partition is severely corrupt, but it is strange that flashing through fastboot doesn't give an error. Without adb it makes it hard to test a few things but I have a couple more ideas you can try, I need to check a couple things out and when I get home ill post back
Sent from my HTC Vision using xda premium
i have tried flashing various ROMs, cm7 included, various ways -- as update, as zip, as pc10img.
no backups for this devices. maybe i can steal files from another device?
i have got various fastboot errors, though usually seems to flash mostly.
when i erase cache, for example, i get .. erase complete, but no auto format
i tried flashing a recovery again and get no error msg.
well you cant flash backups made from a different model but another dz\g2 will work fine,
if i get a second ill tray and dig a few up for you.
try to record any error you get through fastboot though
looking at your system info you show:
eMMc sandisk 2152 mb 4407295 sectors
i believe the "bad" emmc shows a
emmc samsung - for the bad chip and
emmc uknown - if its completely fried
there may be a fastboot oem command to confirm what chip you have, ill test on this
being you have already flashed a pc10img.zip why dont you go ahead and flash ONE OF THESE
only difference is one has g2 engineering hboot and the other dz, both come with a 4ext touch recovery rc
try flashing through fastboot not hboot though, this way we can get the errors if any
demkantor said:
why dont you go ahead and flash ONE OF THESE
Click to expand...
Click to collapse
Code:
[email protected]:~$ fastboot flash zip /home/simon/Downloads/PC10IMG/DZ_PC10IMG.zip
sending 'zip' (17811 KB)...
OKAY [ 3.074s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) start image[radio] unzipping for pre-update...
(bootloader) start image[radio] flushing...
FAILED (remote: hboot pre-update! please flush image again immediately)
finished. total time: 34.219s
[email protected]:~$ fastboot flash zip /home/simon/Downloads/PC10IMG/DZ_PC10IMG.zip
sending 'zip' (17811 KB)...
OKAY [ 3.070s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) start image[sp1] unzipping & flushing...
(bootloader) start image[tp] unzipping & flushing...
(bootloader) start image[tp] unzipping & flushing...
(bootloader) start image[rcdata] unzipping & flushing...
OKAY [ 26.993s]
finished. total time: 30.063s
[email protected]:~$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.159s]
finished. total time: 0.159s
[email protected]:~$ fastboot reboot
rebooting...
comes up to white HTC screen, buzzes once, flashes off, back to reboot-loop. something is not right :cyclops:
what does it say on hboot screen now? anything change?
also just a thought, have you tried hitting factory reset from booloader, this also should boot you into recovery, if choosing recovery wont get you there i doubt this will but just a thought.
if you want you can always try the latest ruu through fastboot, may risk loosing fastboot commands afterwords though
the radio changed - back to the .19 radio
tried reset from bootloader - same business
i did try a newer ruu (not sure about newest?) - got the new stock bootloader, radio. i would like to try the ruu.exe from htc, but i am not on a windows machine and wine is out of date for debian stable ..
i wonder about some things:
is it possible to rewrite the misc.img from fastboot?
a way to have boot ignore the recovery partition?
abandon android all together and install a native linux?
well im thinking the issue maybe deeper as technically you could erase the recovery and still boot into an os so there is something even worse going on here. there is some sort of read/write issues with the emmc but what im not exactly sure
as for removing android and booting a linux distro... yes and no. you can do it if you had a working os being that you can run debian or ubuntu under chroot, like a virtualbox
there maybe a way and im sure there are some threads hear on xda, but if you cant get android running i dont think you will get anything else running.
you can always try logging onto #G2ROOT @ FREENODE and see if someone has any ideas in real time
edit:
another thought, when you flash a new recovery via fastboot does it give a message like "okay.... finished... total time..."
or does it just flicker?
if you get the message likes its complete maybe there is a chance it is being flashed to the nand but something else is keeping you from rebooting to it.
the earlier clockwork recoveries used to have a bug, when you plug your phone in
with the phone powered off, it would auto boot to recovery. just looked at another thread
and someone there had this happen with a cw touch recovery, (only ever heard of it happening with older recoveries before)
but maybe try flashing an one like THIS ONE and see what happens
thanks for the help and ideas ..
i have tried flashing the older recoveries, but may try again. and when i do, i get all the good messages - "okay.... finished... total time..." etc.
some sort of read/write issues
Click to expand...
Click to collapse
I remember reading in the 'Warning' post that if the stock image gets flashed on top of root/s-off that there is a conflict of version number or something to do with misc_img or wpthis.ko business. i think i will try back to that thread and the downgrade firmware thread to see what of that i can do from fastboot.
at this point i dont have much to lose, so i'm open to experimenting some. like i said in OP - i've tried to bric this thing a thousand ways :fingers-crossed:
edit.
i've just tried a buunch of different thing with no change. am having to assume it's hardware, maybe not worth much xtra time now - but for with the screwdrivers ..
try and see if you can get into fastboot RUU mode?
Code:
fastboot oem rebootRUU
from here you can try to do a complete install of original ROM, radio, recovery etc.
i don't know how much help you will have with this but before you use your phone to build a wall...
BE CAREFUL WITH THESE
if it doesn't work you may end up with nothing... not much different then you have now
if it does seem to finish
Code:
fastboot reboot-bootloader
see if you can access recovery now?
demkantor said:
try and see if you can get into fastboot RUU mode?
Code:
fastboot oem rebootRUU
from here you can try to do a complete install of original ROM, radio, recovery etc.
i don't know how much help you will have with this but before you use your phone to build a wall...
Click to expand...
Click to collapse
this is what i was doing yesterday - no luck
BE CAREFUL WITH THESE
if it doesn't work you may end up with nothing... not much different then you have now
if it does seem to finish
Code:
fastboot reboot-bootloader
see if you can access recovery now?
Click to expand...
Click to collapse
these are all windows.exe - i dont have access to a machine to extract the rom.zip ..
i did do this all once a week ago and i think i remember being able to get to the stock recovery at one point, but was not able to repeat that yesterday.
edit
i will try this again - these RUUs are newer than the one i had - at this point i would be happy with stock because this is a nice device otherwise. think i'll open up the back too and see what kind of squirrel is living on the board.
any chance it's possible to boot directly from SD?
I was thinking to make a clean post about unrooting and here it is
How to Unroot the HTC Desire 816
In case you aren’t excited to have root-access on your HTC Desire 816 and you want to get your device back to stock, our guide below should help you do exactly that. It’ll help you unroot your device and get it back to the stock firmware. It also opens up an opportunity for you to customize your device from the scratch.

Unrooting is the process of removing root access, a custom recovery (if you have one), and just trying to get the device back to as close to stock as possible.
Some of the reasons for unrooting your HTC Desire 816 are:
Sending in the device for warranty (most, but not all unrooting procedures reinstate the manufacturer warranty if you had one before rooting).
Starting over (simply undoing everything you did while rooted so you can have a clean slate to start over).
Fix any issues (Maybe rooting messed something up? No problem, unrooting will take care of it for you).
Ready to get started? Here’s how to unroot the HTC Desire 816:
I. Before You Begin
1. You should’ve rooted your device using the procedure given here.
2. This flashes the stock firmware on your device.
3. This should only work on Windows based PCs.

4. You should’ve appropriate drivers installed on your PC. If you haven’t, you can download the latest drivers from here.
5. This procedure only works for the International version of the device.
II. Downloading Required Files
1. Download Fastboot and save it to your desktop.
Fastboot
2. Download Stock RUU .zip and save it to your desktop.
Stock RUU
III. Relocking the Bootloader on the HTC Desire 816
1. Extract files from Fastboot to your desktop by right-clicking on it and selecting Extract here.

2. Enable USB debugging on your device by heading to Menu > Settings > Developer options > USB debugging.
3. Plug in your device to your PC via USB cable.
4. Launch a Command Prompt Window on your desktop. To do that, simply hold down Shift and right-click on any blank area on your screen and select Open command window here.
5. Type in following command into the Command Prompt Window:
adb reboot fastboot
6. Your device should reboot into fastboot mode.
7. Next, issue the following command:

fastboot oem lock
8. It should relock the bootloader on your device.
9. You’re done!
Great! Your first step towards unrooting your device is now complete. Your HTC Desire 816’s bootloader is now relocked and you can flash the stock firmware on it.
IV. Unrooting the HTC Desire 816
1. Connect your device to your PC using the USB cable.
2. Enable USB debugging on your device by going to Menu > Settings > Developer options > USB debugging.
3. Open a Command Prompt Window on your desktop. To do so, simply hold down Shift and right-click on any blank area on your screen and select Open command window here.
4. Type in following command into the Command Prompt Window:
adb reboot fastboot
5. Your device should reboot into fastboot mode.
6. Now issue the following command. Make sure to replace filename.zip with the actual name of the Stock RUU .zip file you downloaded earlier.
fastboot flash zip filename.zip
7. It should start flashing the stock firmware on your device.
8. When it’s done, reboot your device.
9. You’re all done!
Brilliant! Your HTC Desire 816 is now unrooted and is running the fully functional stock firmware that the company has officially released for your device.
NO THANKS , I LOVE TO SOLVE PROBLEMS!!

i really need help over her :
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAIL99 unknown fail
FAILED (remote: 99 unknown fail)
what should i do now !!!
Which rom did you used i mean which stock rom and from where downloaded
And have u checkd that that stock rom is supported in ur mobile
I have HTC Desire 816 A5_UL android 5.0.2 ,I used this ROM from here : https://www.androidfilehost.com/?fid=23991606952595166
it's an exe RUU but i extracted the rom from it , and the android-info file contains this :
modelid: 0P9C20000
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__102
cidnum: HTC__203
cidnum: HTC__Y13
cidnum: HTC__032
cidnum: HTC__M27
cidnum: HTC__A07
cidnum: HTC__J15
cidnum: HTC__016
cidnum: HTC__002
mainver: 2.34.401.1
btype:1
aareport:1
hbootpreupdate:13
DelCache:1
and my CID : HTC__E11
Pm me on facebook i will help you
Id from my profile . .
MihirSheth said:
Pm me on facebook i will help you
Id from my profile . .
Click to expand...
Click to collapse
I appreciate the fact that you took the time to make this forum post to help people but you should really be helping them here in these forums so that others can come later if your not available and use the same information to help themselves. Now, whatever you did to help this person is now on Mark Zuckerberg's personal servers and not where it belongs. Here on XDA.
Every once in a while you might need to P.M. with someone for a specific reason or if something is off topic for a particular forum or personal in nature but you(in my opinion) should also do that here on XDA as the moderators provide us with personal mail accounts here. Which I make use of. If your worried about not knowing something or making an error let me put you at ease as today I made a huge error while helping the same person who you just offered to help at the Zuckerberg's .
I admitted my error then apologized and did everything I could to resolve the issue even asking for help from another XDA member by XDA's mail service . This member, Nukaro, graciously offered to help and was able to get the person's device back working again no thanks to my mistake (albeit an honest one). The point is that this was all documented and saved here for others to learn by and use in the future. Do I like a mistake I made being left in a forum for all to see. Hell no, because I take a lot of personal pride in helping people here . But I'm happy to leave it as a learning tool for others as well as myself to not make the same mistake again and if your not able or not willing to do the same you have no business posting here in my humble opinion because that's not really helping anyone. I've gotten more knowledge from reading the back and forth interactions with people here on XDA's forums than I ever learned from any tutorial. Food for thought and good luck to you.
thoctor said:
I appreciate the fact that you took the time to make this forum post to help people but you should really be helping them here in these forums so that others can come later if your not available and use the same information to help themselves. Now, whatever you did to help this person is now on Mark Zuckerberg's personal servers and not where it belongs. Here on XDA.
Every once in a while you might need to P.M. with someone for a specific reason or if something is off topic for a particular forum or personal in nature but you(in my opinion) should also do that here on XDA as the moderators provide us with personal mail accounts here. Which I make use of. If your worried about not knowing something or making an error let me put you at ease as today I made a huge error while helping the same person who you just offered to help at the Zuckerberg's .
I admitted my error then apologized and did everything I could to resolve the issue even asking for help from another XDA member by XDA's mail service . This member, Nukaro, graciously offered to help and was able to get the person's device back working again no thanks to my mistake (albeit an honest one). The point is that this was all documented and saved here for others to learn by and use in the future. Do I like a mistake I made being left in a forum for all to see. Hell no, because I take a lot of personal pride in helping people here . But I'm happy to leave it as a learning tool for others as well as myself to not make the same mistake again and if your not able or not willing to do the same you have no business posting here in my humble opinion because that's not really helping anyone. I've gotten more knowledge from reading the back and forth interactions with people here on XDA's forums than I ever learned from any tutorial. Food for thought and good luck to you.
Click to expand...
Click to collapse
100% True, instructions should be available for anyone to see maybe someone has the same problem if mine was solved on facebook no one else will be able to benefit from it. we all learn from our mistakes and the thing that happened with me gave me a better understand to how things work with rooting, flashing updating.... by the way this post was before this little problem that happened with me as i was also trying to unroot beside fixing the binary issue. Anyway thanks to your effort i got what i wanted and people who may have the same issue will also benefit from it in the future.
Hi
Thanks for this thread. I followed all the instructions and my 816 A5_UL Single sim is now relocked but I have no OS.
Phone details follow:-
A5_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.101.1102.17.0506
OPenDSP-v28.2.2.00546.0331
OS-
eMMC-boot 1536MB
Nov 20 2014,21:05:17.0
I have tried the Eur RUU on this thread but it stops with error NOT Correct img.
How can I find the correct RUU for this phone.
TIA
Stransky
Stransky said:
Hi
Thanks for this thread. I followed all the instructions and my 816 A5_UL Single sim is now relocked but I have no OS.
Phone details follow:-
A5_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.101.1102.17.0506
OPenDSP-v28.2.2.00546.0331
OS-
eMMC-boot 1536MB
Nov 20 2014,21:05:17.0
I have tried the Eur RUU on this thread but it stops with error NOT Correct img.
How can I find the correct RUU for this phone.
TIA
Stransky
Click to expand...
Click to collapse
If you have the a5_ul here is a link to a newer member who has this same device and wrote a great tutorial for flashing back the stock OS and recovery. I have a different version of this device but have had someone follow her forum instructions and links and got back to stock after wiping their O.S. . This person here "not so much" and I'll leave it at that. Link below and good luck.
EDIT: want to mention the members name is Nukaru as it's this members hard work not mine that made this great tutorial.
http://forum.xda-developers.com/showpost.php?p=64953243&postcount=13
Where is the links ???
All links are disabled...
iamramprabu said:
Where is the links ???
All links are disabled...
Click to expand...
Click to collapse
I've read all of this posters forums he has started and to say his suggestions and info. are not very credible would be an understatement. What version of the 816 do you have? (a5_ ul/chl/dug) and what region are you in?
I have also got a rooted HTC d816 but I guess I'm bored with it coz all the ROMs are single sim and at the same time my my model a5 DWG 's official marshmallow is also realised officially I want to unroot but my phone is not being detected in fastboot mode in my PC so I badely need help what can be dome about that..
I could really use some help. I'm at the edge of my patience and have tried pretty much everything I can think of. I say near brick cause a phone without WiFi and BT is kinda useless.
Here's the back story. I had my previous xt1575 stolen. I purchased a used one off ebay. I received it, only to find it was bootloader unlocked, rooted. Not an issue in theory but I wasn't told that. Ok, upon trying the phone it worked but the battery would last 3 hours, it would have random reboots and would run so hot i could hardly hold the phone. I figured it was a faulty kernel. I flashed a new kernel and stock rom. Battery life went back to almost perfect but was off by about 20%. The random reboots were still an issue, but everything else seemed to work. A randomly rebooting phone is far from ideal. I figured I'd keep trying. Maybe it was a software issue. I would get random results with different roms. And the rebooting really seemed to occur when I had all my apps downloaded. So, I decided to run to flash again and run lean and see if with just the default apps whether it would reboot. After the flash, I waited a few hours, then BT and WiFi just stopped working. No go. The actual toggles revert to off position essentially immediately and neither turn on. I've since tried FDRs, different roms, different kernels, no luck. No idea what to do at this point. It could be hardware, obviously. It could be that the wifi chip was faulty and causing the overheating/battery drain from before, and finally after running so hot that one day before I flashed, it just did final damage to the chip that came to pass 3 days later. I don't know. It's possible but i somehow feel like it's a SW issue. I could send it back but it's complicated and i would really prefer to see if I can get this resolved. I've reflashed the modem bin files of stock roms, etc. Another issue i get often is when i try flashing, I get the writing 'boot'... (bootloader) Preflash validation failed FAILED (remote failure) and other such failures. Additionally, TWRP often just disappears. Aside from that, the OS, usually runs fine. I can't download apps obviously due to no WiFi, but everything else seems fine and I haven't had any reboots since the wifi/bt stopped working. I don't know if it's a partition issue, or hardware or what. I could use some advice. I'm at the limit of my patience and my knowledge here.
Let me know what you guys need and thanks ahead of time for your help.
vijn said:
I could really use some help. I'm at the edge of my patience and have tried pretty much everything I can think of. I say near brick cause a phone without WiFi and BT is kinda useless.
Here's the back story. I had my previous xt1575 stolen. I purchased a used one off ebay. I received it, only to find it was bootloader unlocked, rooted. Not an issue in theory but I wasn't told that. Ok, upon trying the phone it worked but the battery would last 3 hours, it would have random reboots and would run so hot i could hardly hold the phone. I figured it was a faulty kernel. I flashed a new kernel and stock rom. Battery life went back to almost perfect but was off by about 20%. The random reboots were still an issue, but everything else seemed to work. A randomly rebooting phone is far from ideal. I figured I'd keep trying. Maybe it was a software issue. I would get random results with different roms. And the rebooting really seemed to occur when I had all my apps downloaded. So, I decided to run to flash again and run lean and see if with just the default apps whether it would reboot. After the flash, I waited a few hours, then BT and WiFi just stopped working. No go. The actual toggles revert to off position essentially immediately and neither turn on. I've since tried FDRs, different roms, different kernels, no luck. No idea what to do at this point. It could be hardware, obviously. It could be that the wifi chip was faulty and causing the overheating/battery drain from before, and finally after running so hot that one day before I flashed, it just did final damage to the chip that came to pass 3 days later. I don't know. It's possible but i somehow feel like it's a SW issue. I could send it back but it's complicated and i would really prefer to see if I can get this resolved. I've reflashed the modem bin files of stock roms, etc. Another issue i get often is when i try flashing, I get the writing 'boot'... (bootloader) Preflash validation failed FAILED (remote failure) and other such failures. Additionally, TWRP often just disappears. Aside from that, the OS, usually runs fine. I can't download apps obviously due to no WiFi, but everything else seems fine and I haven't had any reboots since the wifi/bt stopped working. I don't know if it's a partition issue, or hardware or what. I could use some advice. I'm at the limit of my patience and my knowledge here.
Let me know what you guys need and thanks ahead of time for your help.
Click to expand...
Click to collapse
What image are you using? Make sure you are using MPH24.49-18-4 (the -4 is important and newer than the one that ends in 18-18 on Moto's site) with the May 1, 2016, security update from here and flashing each step manually using this post's instructions.
I could explain most of the issues individually you are seeing, unless you are already using the specific version I referenced, since they all seem to relate to improper or old version flashing, but it doesn't really matter because the answer to all of them is the same... Reflash the proper version making sure each steps results in an OKAY.
If I am way off base, then it is likely a hardware problem.
acejavelin said:
What image are you using? Make sure you are using MPH24.49-18-4 (the -4 is important and newer than the one that ends in 18-18 on Moto's site) with the May 1, 2016, security update from here and flashing each step manually using this post's instructions.
I could explain most of the issues individually you are seeing, unless you are already using the specific version I referenced, since they all seem to relate to improper or old version flashing, but it doesn't really matter because the answer to all of them is the same... Reflash the proper version making sure each steps results in an OKAY.
If I am way off base, then it is likely a hardware problem.
Click to expand...
Click to collapse
Well, first off thanks a lot for your help. I had installed that particular version, though it wasn't the one currently installed. But I followed all the instructions and steps and got success writes for all and it booted up but didn't recognize any wifi networks and i tried to toggle on the wifi and same as before. Nothing happens. Wifi simply won't turn on. Same for bluetooth. Looking more like a HW problem isn't it?
vijn said:
Well, first off thanks a lot for your help. I had installed that particular version, though it wasn't the one currently installed. But I followed all the instructions and steps and got success writes for all and it booted up but didn't recognize any wifi networks and i tried to toggle on the wifi and same as before. Nothing happens. Wifi simply won't turn on. Same for bluetooth. Looking more like a HW problem isn't it?
Click to expand...
Click to collapse
I mean I know HW can die at any time, and maybe it was already dying from before which caused the initial issues when I got the phone, but I just have this sneaking suspicion that it's not HW related. I can't shake that feeling. But every SW based solution I try doesn't seem to do the trick.
acejavelin said:
I could explain most of the issues individually you are seeing, unless you are already using the specific version I referenced, since they all seem to relate to improper or old version flashing, but it doesn't really matter because the answer to all of them is the same... Reflash the proper version making sure each steps results in an OKAY.
Click to expand...
Click to collapse
Actually when u have a chance, I'd love this. Been rooting, modding my phones for years but I've never gone past a certain level of understanding. I'm not by nature a code guy though I have enjoyed playing around with custom roms and stuff. Anyway, ya, no pressure and my priority is to see if I can get this fixed or should just send it back, but if you do have time afterwards, would love to know what the deal is.
Still hoping someone can help me out with this. Any ideas? I'd really appreciate it.
vijn said:
Still hoping someone can help me out with this. Any ideas? I'd really appreciate it.
Click to expand...
Click to collapse
us the restore to stock tool, then install twrp and flash trupure and without booting flash the updated modem
unitz0mbie said:
us the restore to stock tool, then install twrp and flash trupure and without booting flash the updated modem
Click to expand...
Click to collapse
Hmm. Definitely willing to try that. You wouldn't happen to have links to Trupure and the updated modem would you? And the Restore to stock tool is this I assume: CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162. Not sure what Trupure is. It's a custom ROM?
vijn said:
Hmm. Definitely willing to try that. You wouldn't happen to have links to Trupure and the updated modem would you? And the Restore to stock tool is this I assume: CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162. Not sure what Trupure is. It's a custom ROM?
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-x-style/development/rom-trupurex-fast-smooth-t3237155
scroll down u will find a link for a modem, and u just flash it aswell
trick is to to flash the rom and modem without booting. if u only boot rom u will no wifi/bt etc
unitz0mbie said:
https://forum.xda-developers.com/moto-x-style/development/rom-trupurex-fast-smooth-t3237155
scroll down u will find a link for a modem, and u just flash it aswell
trick is to to flash the rom and modem without booting. if u only boot rom u will no wifi/bt etc
Click to expand...
Click to collapse
That's so weird. Never heard of that before but will definitely try it. Thanks a lot.
unitz0mbie said:
https://forum.xda-developers.com/moto-x-style/development/rom-trupurex-fast-smooth-t3237155
scroll down u will find a link for a modem, and u just flash it aswell
trick is to to flash the rom and modem without booting. if u only boot rom u will no wifi/bt etc
Click to expand...
Click to collapse
And Trupure? That's a ROM I assume. Know where I can find that? I could research it obviously, but figured there's likely a couple different versions of it. Would rather get the one you recommend. - nevermind. I see that the link you provided was for trupure. Thanks a lot. Will let you know how it goes.
unitz0mbie said:
https://forum.xda-developers.com/moto-x-style/development/rom-trupurex-fast-smooth-t3237155
scroll down u will find a link for a modem, and u just flash it aswell
trick is to to flash the rom and modem without booting. if u only boot rom u will no wifi/bt etc
Click to expand...
Click to collapse
The thing is, I'm on 6.0. Secondly my TWRP keeps getting deleted. And I just tried flashing twrp again and now I'm getting this: sending 'recovery' (34434 KB)...
OKAY [ 0.753s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.773s
Not sure how to proceed. Not much I can do without a working recovery. Any ideas?
vijn said:
That's so weird. Never heard of that before but will definitely try it. Thanks a lot.
Click to expand...
Click to collapse
no problem, if u still have no bt u can find the specific files u need to flash
---------- Post added at 11:41 PM ---------- Previous post was at 11:39 PM ----------
vijn said:
The thing is, I'm on 6.0. Secondly my TWRP keeps getting deleted. And I just tried flashing twrp again and now I'm getting this: sending 'recovery' (34434 KB)...
OKAY [ 0.753s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.773s
Not sure how to proceed. Not much I can do without a working recovery. Any ideas?
Click to expand...
Click to collapse
what version of twrp are u using
---------- Post added at 11:43 PM ---------- Previous post was at 11:41 PM ----------
vijn said:
The thing is, I'm on 6.0. Secondly my TWRP keeps getting deleted. And I just tried flashing twrp again and now I'm getting this: sending 'recovery' (34434 KB)...
OKAY [ 0.753s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.773s
Not sure how to proceed. Not much I can do without a working recovery. Any ideas?
Click to expand...
Click to collapse
try using the restore to stock tool, it will remove twrp
and then u can reflash twrp
unitz0mbie said:
no problem, if u still have no bt u can find the specific files u need to flash
---------- Post added at 11:41 PM ---------- Previous post was at 11:39 PM ----------
what version of twrp are u using
Click to expand...
Click to collapse
3.0.2 i think. can't really check but i think that's what i remember from the last time i loaded it
Here's the thing, there seems to be a consistent issue writing to the boot partition and TWRP never lasts. I don't know all that much about this but I feel as though there's a part of the software that is constantly being deleted/overwritten and that may explain why the modem never stays and twrp never stays. Does that make any sense?
The return to stock tool gives the following 2 errors:
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.378s
and
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 149.569s
Obviously the second error is the end of the process. Can't go any further if it can't write the system. Super confused. Every time I install a new ROM another issue pops up.
unitz0mbie said:
no problem, if u still have no bt u can find the specific files u need to flash
---------- Post added at 11:41 PM ---------- Previous post was at 11:39 PM ----------
what version of twrp are u using
---------- Post added at 11:43 PM ---------- Previous post was at 11:41 PM ----------
try using the restore to stock tool, it will remove twrp
and then u can reflash twrp
Click to expand...
Click to collapse
Managed to get the restore to stock working. Restarted bootloader. Tried to flash twrp, and same error: writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.779s
vijn said:
Managed to get the restore to stock working. Restarted bootloader. Tried to flash twrp, and same error: writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.779s
Click to expand...
Click to collapse
is your bootloader locked?
unitz0mbie said:
is your bootloader locked?
Click to expand...
Click to collapse
to be honest, I don't even know any more. I've locked and unlocked it a bunch of times. Some tools I've used automatically lock or unlock it. At this point i just tried to unlock is using my key and got the following error: error: Command length (142) exceeds maximum size (64). So, ya, i have no idea what's going on. The bootloader page says device:locked, but the prebootloader page says bootloader unlocked.
unitz0mbie said:
is your bootloader locked?
Click to expand...
Click to collapse
I have to step away for a couple hours. I will be back. But regardless of how this goes, I just wanted to say thanks for trying to help with this stuff. I've never had so many issues with a phone before. My previous ones would occasionally give me some headaches, but not to this extent. Anyway, hopefully you'll still be around when i get back or will have some other recommendations.
sounds like your BL is locked man.
I play pogo mock gps a lot, but recent installed the update. I don't care that much about root. I would be happy just to have original stock.
I can't get fastboot to connect. I have opened developer menu and turned on fastboot and debug. Fastboot and adb never connect from cmd. The only time I could get it to see my phone was some windows program that looked like it installed apk files. And I had to set photo xfer mode. I have Moto drivers 6.4.0. I didn't install the 2gb developer pack. Is that my problem.
Any help would be great. Kind of ****ty life circumstances right now and pogo is my escape. Don't have data ATM and not all gyms have a public WiFi.
Edit: tried again with a different computer. I can only see a connection using Windows adb installer 2.0. I had to disable driver signing. it lists my Motorola phone when in mpt mode. Cmd adb doesn't see anything. Just says waiting for device. Also installed developer tools on first computer and it didn't help. I see pages saying the Verizon model is rootable, are the real or fake?
Okay. I got my phone to connect to fastboot. Using the files from this made it work.
My phone was not eligible for unlock from the moto website. I should be able to restore stock without unlock? I did typed "fastboot oem unlock"
downloaded XT1609_HARPIA_VZW_MPI24.241-2.35-1_cid2_subsidy-VZW_regulatory-DEFAULT_CFC.xml
and I ran the commands from this
Which returned:
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
So I need the right .img but where can I get that? downloaded it or buy a new phone from Walmart and backup that image? But if I did buy a new phone, would it be pre march and may security updates? or how would I know?
Eppich8479 said:
Okay. I got my phone to connect to fastboot. Using the files from this made it work.
My phone was not eligible for unlock from the moto website. I should be able to restore stock without unlock? I did typed "fastboot oem unlock"
downloaded XT1609_HARPIA_VZW_MPI24.241-2.35-1_cid2_subsidy-VZW_regulatory-DEFAULT_CFC.xml
and I ran the commands from this
Which returned:
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
So I need the right .img but where can I get that? downloaded it or buy a new phone from Walmart and backup that image? But if I did buy a new phone, would it be pre march and may security updates? or how would I know?
Click to expand...
Click to collapse
yea we're all getting the same issues. I believe its because downgrading in Xt1609 is disabled and it doesnt even let u downgrade to lower security versions either, we're probably going to be waiting for a newer rom , perhaps Motorola wont be a **** and will release the stock rom for android 7 once it comes out
Walmart had a new one for 54$+tax, price matched Walmart online. It came with the Feb security. I can play my game again, but it still wants to upgrade. I can force stop it, but it downloads a little each time. I think I'll have to do a factory restore once it hits 90%. Then rinse and repeat. How do I kill moto system update permanently?
Hello,
My wife's moto g5 plus today just showed up with "startup failed" and it's booting in Fastboot Flash Mode (Secure).
This phone was stock international version, nothing was touched.
My thought is that probably the storage device is dead (or close to), because any operation I tried ends with FAILED (remote failure), even flashing a new partition.
If I try to use "factory" (within fastboot flash mode), it fails booting, same goes for any other option beside "bootloader logs" and BarCodes.
Interesting, I discovered that the IMEI and SKU for this phone are all zeros, even though nothing was ever flashed on this phone beside standard OTA updates, so maybe the storage device has been failing for a while. I remember at some point asking my wife why her phone was always running on 3G. (This was a new phone, not a used one).
Unfortunately OEM is locked, but when I try to unlock it with fastboot oem get_unlock_data, I get:
Code:
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.037s]
finished. total time: 0.038s
At this point I'm considering purchasing a new phone, but I'd be happy to perform some other test (at this point I don't care of anything that's on the phone, it's going in the garbage anyway) that someone might suggest.
Finally, a way to cleanup the storage device would be ideal, I want to clear the phone before throwing it in the garbage (well, recycling really)
Thanks for any help!
Yup. No hope. Probably the storage is done. Get a new device.
Fire-Dragon-DoL said:
Hello,
My wife's moto g5 plus today just showed up with "startup failed" and it's booting in Fastboot Flash Mode (Secure).
This phone was stock international version, nothing was touched.
My thought is that probably the storage device is dead (or close to), because any operation I tried ends with FAILED (remote failure), even flashing a new partition.
If I try to use "factory" (within fastboot flash mode), it fails booting, same goes for any other option beside "bootloader logs" and BarCodes.
Interesting, I discovered that the IMEI and SKU for this phone are all zeros, even though nothing was ever flashed on this phone beside standard OTA updates, so maybe the storage device has been failing for a while. I remember at some point asking my wife why her phone was always running on 3G. (This was a new phone, not a used one).
Unfortunately OEM is locked, but when I try to unlock it with fastboot oem get_unlock_data, I get:
At this point I'm considering purchasing a new phone, but I'd be happy to perform some other test (at this point I don't care of anything that's on the phone, it's going in the garbage anyway) that someone might suggest.
Finally, a way to cleanup the storage device would be ideal, I want to clear the phone before throwing it in the garbage (well, recycling really)
Thanks for any help!
Click to expand...
Click to collapse
Sounds like the eMMC is broken.
Just to have made the attempt you could try to flash the latest signed Motorola firmware:
https://mirrors.lolinet.com/firmware/moto/potter/official/
Choose the 8.1.0_OPS28.85-17-6-2 build for your region and flash it by fastboot.
You should have Motorola drivers and ADB/Fastboot installed, everything downloadable here:
https://forum.xda-developers.com/g5...solve-imei0-explanation-t3825147/post80478329
But as said above, there's not much hope.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
Sounds like the eMMC is broken.
Just to have made the attempt you could try to flash the latest signed Motorola firmware:
https://mirrors.lolinet.com/firmware/moto/potter/official/
Choose the 8.1.0_OPS28.85-17-6-2 build for your region and flash it by fastboot.
You should have Motorola drivers and ADB/Fastboot installed, everything downloadable here:
https://forum.xda-developers.com/g5...solve-imei0-explanation-t3825147/post80478329
But as said above, there's not much hope.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Thanks, tested all that.
If fails at the first command, but I tried running the others just to see if it would "do anything". It fails on every command with a "remote" error.
I guess it IS dead. Time to look for a new cheap phone :silly:
Perhaps one last ditch try, use Lenovo Smart Assistant -
https://support.lenovo.com/us/en/downloads/ds101291
goodjuju said:
Perhaps one last ditch try, use Lenovo Smart Assistant -
https://support.lenovo.com/us/en/downloads/ds101291
Click to expand...
Click to collapse
Tested that too, it's a brick
Thanks for the suggestion though, I appreciated the good will!
fwiw....Due to the recent launch of the G8, brand new 64GB/4GB Moto G7s, not the janky Power or Play models, are going for $150-$160 'Buy it Now' on ebay and new 64gb/3gb G6's for $99! I luv it when a new G launches...prices come a tumblin down.
Also...the nearly new 'Open Box' & A+ grade G7s will start going waay down as folks start trading in their G7s for a G8, or other, to upgrade. I've had fantastic luck with open boxers...like the G5+ I have now.