Database Users

Is Your G2 or Desire Z a Brick? Lets Find Out!

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 want to throw my n7 across the room. (4.2.2 install problems)

First of all I have a 16gb n7 currently on 4.2.1 JOP40D. It's unlock/rooted on STOCK rom.
First off I have tried installing the OTA update and would get an error everytime.
Then I tried installing CWM and manually pushing the update nakasi update and it still threw an error:
Verifying current system..
assert failed: apply_patch_check ("/system/build.prop", 38f7593c2ff2fa85a147 etc...)
E: Error in /sdcard/0/6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip
(status 7)
Installation abborted.
So from googling/searching that I have figured that there is something not "stock" about my build.prop. I had edited it to get rid of the NAV bar but after re-editing it back to stock, it would still throw the same error.
So first I tried reflashing 4.2.1 ... threw the same error
Now I'm trying to get the build prop out of the JOP40D update but when I look in the files it is called "build.prop.p" ... I'm not sure what that last .p is about? Also when opening it there are just about 2 lines of chinese characters... Soooo this is where I'm stuck... I need to know how to extract a proper build prop from 4.2.1 or I need someone to post a stock 4.2.1 build prop.. thanks..
edit: before people suggest I have tried redownloading both the JOP40D and JPQ39 files
edit2: I am on a mac so flashing to stock from fastboot / abd isn't really an option

The checksum performed requires the file to be exactly identical to the original.
No extra spaces, identical line termination schemes et cetera - identical byte-for-byte. That means including characters you can not see in an editor.
You can certainly copy the original to a folder side-by with your hand-edited version and run any checksum on the both of them to see if you got it right, but it is probably easier to just copy the original into place.
Simply put, the only reason that check continues to fail is because the file you have there is NOT identical to the original.
good luck

canadianrider said:
edit2: I am on a mac so flashing to stock from fastboot / abd isn't really an option
Click to expand...
Click to collapse
since when does fastboot or adb not work on a mac????
http://developer.android.com/sdk/index.html
hint: they have the package for mac...download it and follow the directions to run fastboot/adb commands...its easier than you think

canadianrider said:
Now I'm trying to get the build prop out of the JOP40D update but when I look in the files it is called "build.prop.p" ... I'm not sure what that last .p is about?
Click to expand...
Click to collapse
That is a *patch* file. It is used to perform binary patching of the original file - it is neither the original nor the replacement for the original.
You need to dig the original build.prop out of the 4.2.1 factory distro, or your own nandroid backups ( you do make backups, right?) The 4.2.1 distros are no longer online from Google, but oldblue910 has your butt covered with his randomphantasmagoria (sp?) site. Check for the link in the OTA post by oldblue910 over in the dev forum.
http://www.randomphantasmagoria.com <--- choose nakasi or nakasig links on rhs of page as appropriate

the easiest option would be to fastboot
system.img
and
boot.img
from the 4.2.2 images google provides...

bftb0 said:
That is a *patch* file. It is used to perform binary patching of the original file - it is neither the original nor the replacement for the original.
You need to dig the original build.prop out of the 4.2.1 factory distro, or your own nandroid backups ( you do make backups, right?) The 4.2.1 distros are no longer online from Google, but oldblue910 has your butt covered with his randomphantasmagoria (sp?) site. Check for the link in the OTA post by oldblue910 over in the dev forum.
http://www.randomphantasmagoria.com <--- choose nakasi or nakasig links on rhs of page as appropriate
Click to expand...
Click to collapse
Thank you! That's what I was looking for.
I did make a backup .... many moons ago.. then the hard drive on my windows pc died. And there went my backups..
Pirateghost said:
since when does fastboot or adb not work on a mac????
http://developer.android.com/sdk/index.html
hint: they have the package for mac...download it and follow the directions to run fastboot/adb commands...its easier than you think
Click to expand...
Click to collapse
Yeah I looked that up after I posted this.. Now to figure out how to use ADB and Fastboot.
Pirateghost said:
the easiest option would be to fastboot
system.img
and
boot.img
from the 4.2.2 images google provides...
Click to expand...
Click to collapse
Not sure how to do that... I've been looking at the thread for putting the n7 back to stock with adb/fastboot .. haven't looked too closely yet (just sat down) but I don't want to relock the bootloader so im not sure if that applies to me. Is there a thread on how to flash firmware with ADB?
Cheers

canadianrider said:
Thank you! That's what I was looking for.
I did make a backup .... many moons ago.. then the hard drive on my windows pc died. And there went my backups..
Yeah I looked that up after I posted this.. Now to figure out how to use ADB and Fastboot.
Not sure how to do that... I've been looking at the thread for putting the n7 back to stock with adb/fastboot .. haven't looked too closely yet (just sat down) but I don't want to relock the bootloader so im not sure if that applies to me. Is there a thread on how to flash firmware with ADB?
Cheers
Click to expand...
Click to collapse
running adb and fastboot commands DO NOT require you to relock the bootloader
its simple. once you have your fastboot executables set up on your computer its literally as simple as putting the device in fastboot mode, and running:
fastboot flash system nameofsystem.img
fastboot flash boot nameofboot.img

Pirateghost said:
running adb and fastboot commands DO NOT require you to relock the bootloader
its simple. once you have your fastboot executables set up on your computer its literally as simple as putting the device in fastboot mode, and running:
fastboot flash system nameofsystem.img
fastboot flash boot nameofboot.img
Click to expand...
Click to collapse
No no I know it does not require you to relock the bootloader.. I just assumed the method used in the one thread I was talking about would relock the bootloader.. I'm just talking out of my ass here though.. I'll start reading on how to use fastboot soon.
If anyone has any good idiot proof guides I'd appreciate it.

follow GOOGLE's directions for setting up fastboot and adb.
it is literally 2 commands
fastboot flash system nameofsystemimgfile.img
fastboot flash boot nameofbootimgfile.img
while the device is in fastboot mode....its not complicated. download the files you need and get started. in the amount of time you have waited on a reply, you could have already had it done. you dont have to learn every command, you just need to 'install' fastboot and adb and put the files in the proper place.
https://developers.google.com/android/nexus/images
http://bit.ly/158k5Wr

ah hah! after a bit of reading and fumbling around with fastboot I did it! thanks for all the help guys. my blood pressure can go down now..

canadianrider said:
ah hah! after a bit of reading and fumbling around with fastboot I did it! thanks for all the help guys. my blood pressure can go down now..
Click to expand...
Click to collapse
see? it wasnt really that complicated.

Pirateghost said:
see? it wasnt really that complicated.
Click to expand...
Click to collapse
no it wasn't... but it was a little more complicated because there's no "this is how you flash on a mac" thread ... I just had to compile different parts from different threads.

canadianrider said:
no it wasn't... but it was a little more complicated because there's no "this is how you flash on a mac" thread ... I just had to compile different parts from different threads.
Click to expand...
Click to collapse
i provided a lmgtfy link, that had many threads listed on setting it up on a mac.
all nexus devices are the same in respect to fastboot/adb
any thread you find for n7, galaxy nexus, nexus4....pretty much universal

Ok, now just came across another issue.. I'm on 4.2.2 and all is well, but now I want to root.
And now adb is saying that my device is offline? I've tried restarting the device. Checking and unchecking USB debugging. Unplugging and plugging it back in but nothing? ... I've read on windows machines it might be a driver issue but with mac's we don't have to install drivers.
ADB worked perfectly fine before the update...

Has anyone made a version of the 4.2.2 update that can be installed even for those of us with modified system/app files? The only way I could get the last two updates was to hunt down this specific version of the update files.

canadianrider said:
Ok, now just came across another issue.. I'm on 4.2.2 and all is well, but now I want to root.
And now adb is saying that my device is offline? I've tried restarting the device. Checking and unchecking USB debugging. Unplugging and plugging it back in but nothing? ... I've read on windows machines it might be a driver issue but with mac's we don't have to install drivers.
ADB worked perfectly fine before the update...
Click to expand...
Click to collapse
What version of adb are you using? (command: "adb version")
With 4.2.2 you should see a pop-up on the tablet asking you to accept the device (PC/Mac) with the RSA fingerprint yadda-yadda-yadda... If you don't hit the accept/OK button within 2-3 seconds, adb will report the device offline ... even if you eventually press the OK/accept message in the popup on the tablet.
Try restarting the adb server on the Mac and be ready to press the button on the popup (make sure screen on tab is unlocked)
Code:
adb kill-server
adb devices

gavingt said:
Has anyone made a version of the 4.2.2 update that can be installed even for those of us with modified system/app files? The only way I could get the last two updates was to hunt down this specific version of the update files.
Click to expand...
Click to collapse
Pirate posted a link of the full 4.2.2 ROM that can be installed with fastboot.
bftb0 said:
What version of adb are you using? (command: "adb version")
With 4.2.2 you should see a pop-up on the tablet asking you to accept the device (PC/Mac) with the RSA fingerprint yadda-yadda-yadda... If you don't hit the accept/OK button within 2-3 seconds, adb will report the device offline ... even if you eventually press the OK/accept message in the popup on the tablet.
Try restarting the adb server on the Mac and be ready to press the button on the popup (make sure screen on tab is unlocked)
Code:
adb kill-server
adb devices
Click to expand...
Click to collapse
Android Debug Bridge version 1.0.29
No pop up on the tablet

Ah nevermind.. I'm just reading on the ADB website that you need version 1.0.31 or higher with 4.2.2 .... thanks for the heads up!

[Q][Noobs] I typed command "fastboot erase bootloader"

I very noobs when type command "fastboot erase bootloader". My Nexus 7 is brick.
Can you help me fix this problem?

KingMGT said:
I very noobs when type command "fastboot erase bootloader". My Nexus 7 is brick.
Can you help me fix this problem?
Click to expand...
Click to collapse
Hi, KingMGT...
You typed the command that should never be typed!
Unless you have previously created 'blobs' specific to your Nexus 7 (using the flatline procedure), your device is unrecoverably bricked.
Rgrds,
Ged.

Can you help me fix this problem? :( :([/QUOTE said:
Strip it and sell the parts on eBay apart from the motherboard im afraid its unrecoverable without blob backups
Sent from one of my 47 iPads running android C3P0
Click to expand...
Click to collapse

Captain Sweatpants said:
Strip it and sell the parts on eBay apart from the motherboard im afraid its unrecoverable without blob backups
Sent from one of my 47 iPads running android C3P0
Click to expand...
Click to collapse
Is RMA out of discussion here ?

Wild78 said:
Is RMA out of discussion here ?
Click to expand...
Click to collapse
Yes. Because he erased his bootloader.

You could buy a new motherboard and fit it you self its pretty easy and you can get them for about £40/50 but warranty is out the question.
Sent from one of my 47 iPads running android C3P0

Read read read, learn, learn more, understand, understand fully......then and only then start messing with your devices.
Sorry for your loss.
Sent from my N5 cell phone telephone....

KingMGT said:
I very noobs when type command "fastboot erase bootloader". My Nexus 7 is brick.
Can you help me fix this problem?
Click to expand...
Click to collapse
Well bro, you have my sympathy.
This command results in hard bricks.....
Now the only way is to restore a .blob backup which you should have taken through flatlines nvflash before doing the biggest mistake of your life.
You may reclaim your warranty, I think.....but your n7 is dead.
Sent from my Nexus 7 using Tapatalk

Thanks all.
I sold it and bought a new Google nexus 7 16GB Wifi.
After bought, i instant backup blob.bin hehe.

We live and learn. The first time I started messing with android I hard bricked a Samsung galaxy spica. Got really nervous about messing with my next phone
Sent from one of my 47 iPads running android C3P0

KingMGT said:
I very noobs when type command "fastboot erase bootloader". My Nexus 7 is brick.
Can you help me fix this problem?
Click to expand...
Click to collapse
I am pretty sure your nexus is a paperweight, but can I ask....what possessed you to type that?...

KingMGT said:
I very noobs when type command "fastboot erase bootloader". My Nexus 7 is brick.
Can you help me fix this problem?
Click to expand...
Click to collapse
Curious if you know which bootloader version you have? I'm on 4.23 and I have, out of morbid curiousity, typed that which should never be type... fastboot erase bootloader and it doesn't erase. Says erase failed. Bootloader and Nexus unharmed. That being said, please DO NOT try this at home! But I'm wondering under what circumstances a bootloader would allow itself to be erased? I've flashed bootloaders, which makes total sense, but erasing should never be an option.

adomol said:
Curious if you know which bootloader version you have? I'm on 4.23 and I have, out of morbid curiousity, typed that which should never be type... fastboot erase bootloader and it doesn't erase. Says erase failed. Bootloader and Nexus unharmed. That being said, please DO NOT try this at home! But I'm wondering under what circumstances a bootloader would allow itself to be erased? I've flashed bootloaders, which makes total sense, but erasing should never be an option.
Click to expand...
Click to collapse
You sir, are brave.
Sent from my N5 cell phone telephone....

adomol said:
Curious if you know which bootloader version you have? I'm on 4.23 and I have, out of morbid curiousity, typed that which should never be type... fastboot erase bootloader and it doesn't erase. Says erase failed. Bootloader and Nexus unharmed. That being said, please DO NOT try this at home! But I'm wondering under what circumstances a bootloader would allow itself to be erased? I've flashed bootloaders, which makes total sense, but erasing should never be an option.
Click to expand...
Click to collapse
Hi, adomol...
As politely as I can put this, but "Why?"... did you try this...
Generally, the command...
Code:
fastboot erase <partition_name>
...will delete/erase whatever the named partition occupies. Often, this will be for something relatively innocuous, (eg., fastboot erase boot, fastboot erase userdata, etc.) but it also WILL ERASE THE UNIQUE DEVICE SPECIFIC, CRYPTOSIGNED BOOTLOADER for your unique Nexus 7 if your attempt to erase the bootloader succeeds. And your device is then HARDBRICKED.
---------------------------------------------
I suspect the reason why your quasi-suicidal attempt to brick your Nexus 7 failed, is because your bootloader is probably locked... and fastboot commands fail if the bootloader is locked.
I strongly recommend you desist from further experimentation along these lines.
Rgrds,
Ged.

GedBlake said:
Hi, adomol...
As politely as I can put this, but "Why?"... did you try this...
Generally, the command...
Code:
fastboot erase <partition_name>
...will delete/erase whatever the named partition occupies. Often, this will be for something relatively innocuous, (eg., fastboot erase boot, fastboot erase userdata, etc.) but it also WILL ERASE THE UNIQUE DEVICE SPECIFIC, CRYPTOSIGNED BOOTLOADER for your unique Nexus 7 if your attempt to erase the bootloader succeeds. And your device is then HARDBRICKED.
---------------------------------------------
I suspect the reason why your quasi-suicidal attempt to brick your Nexus 7 failed, is because your bootloader is probably locked... and fastboot commands fail if the bootloader is locked.
I strongly recommend you desist from further experimentation along these lines.
Rgrds,
Ged.
Click to expand...
Click to collapse
I know it was reckless and could have hardbricked my device, but the thrill overtook me. I have a history of this kind of behavior. But that is beside the point.
I've used fastboot many times and executed most of the usual commands... format, erase, flash, devices, oem unlock, oem lock. All on this very device. The same one I almost euthanized. It is a Nexus 7 2012, unlocked running all-f2fs SlimKat, bootloader version 4.23 (which is the current version.) I flashed that bootloader myself a couple months back when I did a nexus factory image install through fastboot. I also used the erase command on all the usual partitions before flashing them, as I took care of each one seperately.
That being said, I executed the dreaded command on this N7. Result... erase failed
Now that result just brings up more questions, although it would make sense to have fastboot not be able to erase that part or somehow build into the bootloader somekind of failsafe. Could be that 4.23 can't be erased and older versions can?

adomol said:
I know it was reckless and could have hardbricked my device, but the thrill overtook me. I have a history of this kind of behavior. But that is beside the point.
I've used fastboot many times and executed most of the usual commands... format, erase, flash, devices, oem unlock, oem lock. All on this very device. The same one I almost euthanized. It is a Nexus 7 2012, unlocked running all-f2fs SlimKat, bootloader version 4.23 (which is the current version.) I flashed that bootloader myself a couple months back when I did a nexus factory image install through fastboot. I also used the erase command on all the usual partitions before flashing them, as I took care of each one seperately.
That being said, I executed the dreaded command on this N7. Result... erase failed
Now that result just brings up more questions, although it would make sense to have fastboot not be able to erase that part or somehow build into the bootloader somekind of failsafe. Could be that 4.23 can't be erased and older versions can?
Click to expand...
Click to collapse
Hi, adomol...
You're definitely onto something here... I must be mad, but I've just attempted to erase my bootloader. And encountered a similar error to yours.
So, with every precaution available to hand, here's what I did...
------------------------------------
...made available a known working copy of the v4.23 bootloader.img on my laptop, with the intention of immediately fastboot flashing it, in the event the bootloader erase SUCCEEDED. (Providing you DON'T reboot the device immediately after a bootloader flash failure (or erasure), there is a small window of opportunity to fastboot flash a known working bootloader... before you reboot the device.)
...made available my 'flatline' created 'blob.bin' file, and nvFlash tools...
My device...
Nexus 7 (2012), 16Gb,'grouper' model, WiFi only.
Bootloader v4.23, unlocked.
Custom recovery is TWRP 2.7.0.0
Running rooted KitKat 4.4.2, with modifications (see my sig. for details).
--------------------------------------------------------------------------
With all tools, files and everything I could think of readily available (and my heart in my stomach!!)... I ran the potential Nexus 7 command line killer...
WARNING TO ALL READERS: The following command is potentially VERY dangerous, and may BRICK your device. Do NOT use casually. The previous poster raised an interesting issue regarding the v4.23 bootloader, and what follows is my own risky experiment... which happily, did not brick MY Nexus 7. I can make no such guarantees about YOUR Nexus 7.
Code:
fastboot erase bootloader
It failed... with this error message...
Code:
erasing 'bootloader'...
FAILED <remote: Unsupport Erase bootloader Partition.>
finished. total time: 0.016s
See my attached thumbnail.
So, it DOES appear that, at least as far as the v4.23 bootloader is concerned... it's impossible to deliberately erase it... although accidentally overwriting it, I suspect might be a different matter - eg., inadvertently fastboot flashing a boot.img to the bootloader partition, for example.
Anyway... very nice find, @adomol... you've discovered something interesting as a result of your bravery or foolhardiness... and I can't decide which! Whichever quality it is, I think I share it.
--------------------------------------------------------------------------
Right... I'm off for a cigar, and a drop of whisky to calm my nerves.
Rgrds,
Ged.

GedBlake said:
Anyway... very nice find, @adomol... you've discovered something interesting as a result of your bravery or foolhardiness... and I can't decide which! Whichever quality it is, I think I share it.
--------------------------------------------------------------------------
Right... I'm off for a cigar, and a drop of whisky to calm my nerves.
Rgrds,
Ged.
Click to expand...
Click to collapse
I'm breeding an XDA loony bin in here! It's like Jackass Nexus 7 edition. :laugh:
Thanks for posting the screenshot, though. I wish I would have been resourceful enough to do that, considering how unlikey these results were thought to have been. Good job @GedBlake!

@adomol That being the one command that will irrevocably brick a nexus you at either very brave or stupid to type that please tell me you had a blob.bin backup before trying that. Anyway that's an interesting find nonetheless.
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.

stuck in bootloader, no recovery.

hi, i have a problem with my N6P. it was unlocked, twrp flashed and running newest version of this ROM http://forum.xda-developers.com/nexus-6p/development/rom-debloated-prerooted-deoxeded-t3372600.
then, out of the blue, phone refused to work. when i'm trying to restart it, only option is boot to bootloader. i was trying to flash newest radio, bootloader, vendor and recovery - all failed with message "(remote: flash write failure)"
when i'm in bootloader mode, Andy Android is lying on his back, with no red exclamation point.
also there is written below Andy:
BL: K
Baseband: (empty)
Product/Variant: Angler-VN2
Serialn Number: (is present, but i think there is no need to write it)
CPU: MSM8994 0x20001
eMMC: 32GB Samsung
DRAM: 3072MB HYNIX LPDDR4
Console: NULL
Battery OK
Device is LOCKED
Qfuse Status: ENABLED
Off-Mode-charge: ENABLED
Download Mode: DISABLED
Connect USB Data Cable
strange thing is, that there is written "Device is LOCKED", because when wrote command "fastboot flashing unlock", there was a message:
...
(bootloader) Device already unlocked!
FAILED (remote failure)
I was able to fastboot boot boot.img, but it hanged on "Google" screen.
device is not visible after writing "adb devices", but is visible after writing "fastboot devices".
any ideas?

Might be a dumb question, but have you tried going back to stock Android N using Googles Factory Image in fastboot just to determine if your phone will still boot into os?

i'm downloading GFI, but 3 more hours left to finish download (unless there is a mirror server to download them). i'll probably try to do it, but i would like to avoid it because my backup is 2 months old :/

Fe Mike said:
Might be a dumb question, but have you tried going back to stock Android N using Googles Factory Image in fastboot just to determine if your phone will still boot into os?
Click to expand...
Click to collapse
tried this, no luck - still "remote flash write failure" message.
strange thing is, that i'm able to relock the bootloader (at least command "fastboot flashing lock" gave me possibility to do this {(YES/NO) message}, i didn't relocked it.
i've read, that this is probably fried emmc, but would it be possible to relock bootloader though?

miguelm75 said:
tried this, no luck - still "remote flash write failure" message.
strange thing is, that i'm able to relock the bootloader (at least command "fastboot flashing lock" gave me possibility to do this {(YES/NO) message}, i didn't relocked it.
i've read, that this is probably fried emmc, but would it be possible to relock bootloader though?
Click to expand...
Click to collapse
You might be right about fried emmc, have you tried placing a twrp.img in fastboot folder and run command fastboot boot twrp-x-x-x.img (not flash)? If it is fried can you rma?
Edit: I found this thread, second post has a link that may help. It is kinda advanced. The process can at least tell you if in fact emmc is bad and if it's not bad there may be a way of fixing it.

Fe Mike said:
You might be right about fried emmc, have you tried placing a twrp.img in fastboot folder and run command fastboot boot twrp-x-x-x.img (not flash)? If it is fried can you rma?
Edit: I found this thread, second post has a link that may help. It is kinda advanced. The process can at least tell you if in fact emmc is bad and if it's not bad there may be a way of fixing it.
Click to expand...
Click to collapse
1. i tried to flash recovery - no luck.
2. there will be problem with RMA, because i won this phone in a giveaway at AndroidAuthority.com and it has US warranty, so it would be rather expensive to send it to USA from Poland. but i will try to contact Huawei support in my country.
3. did you forgot to insert link to this thread?

miguelm75 said:
1. i tried to flash recovery - no luck.
2. there will be problem with RMA, because i won this phone in a giveaway at AndroidAuthority.com and it has US warranty, so it would be rather expensive to send it to USA from Poland. but i will try to contact Huawei support in my country.
3. did you forgot to insert link to this thread?
Click to expand...
Click to collapse
Yes I did, my bad.
https://www.google.com/amp/s/amp.re...here_a_way_to_check/?client=ms-android-google

Fe Mike said:
Yes I did, my bad.
https://www.google.com/amp/s/amp.re...here_a_way_to_check/?client=ms-android-google
Click to expand...
Click to collapse
thank you. unfortunatelly this is for LG devices. i can't find anything similiar for Huawei devices. i did tried Nexzus Root Toolki by Wug Fresh and i got the same error - "remote flash write failure"
so i think i will try to contact Huawei and local phone service to see, if they are able to fix it. thank you for your help.

Did you try to format data partition then flash the google image?

Iceburn1 said:
Did you try to format data partition then flash the google image?
Click to expand...
Click to collapse
i just did and received (remote: failed to erase partition) error.

miguelm75 said:
thank you. unfortunatelly this is for LG devices. i can't find anything similiar for Huawei devices. i did tried Nexzus Root Toolki by Wug Fresh and i got the same error - "remote flash write failure"
so i think i will try to contact Huawei and local phone service to see, if they are able to fix it. thank you for your help.
Click to expand...
Click to collapse
The op has an LG device but in second post there is a link (the one I'm posting now) for Qualcomm chipsets.
http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301

miguelm75 said:
tried this, no luck - still "remote flash write failure" message.
strange thing is, that i'm able to relock the bootloader (at least command "fastboot flashing lock" gave me possibility to do this {(YES/NO) message}, i didn't relocked it.
i've read, that this is probably fried emmc, but would it be possible to relock bootloader though?
Click to expand...
Click to collapse
Same thing just happened to me except I was just using my phone then it crashed and never came back tried for days to recover was able to re-lock bootloader but no other commands took. Had to RMA it back to Huawei took 3 weeks but it was covered by 12 month warranty so that's a plus

did you switch on find my phone in administer options before unlocking and flashing errors ?

rowihel2012 said:
did you switch on find my phone in administer options before unlocking and flashing errors ?
Click to expand...
Click to collapse
no, i didn't touch it.

Happened to me too while using it. I am still trying to save my data, but no luck for now.

(ROOTED) MOTO X Pure (Style) XT1575 Cannot recieve calls

Make: Motorola
Model: Moto X Pure Edition (Style) XT1575
OS: 6.0 Marshmallow
Rooted: yes
Bootloader: you'd better believe it
Hello,
I am having a little trouble with the calling function on my moto x pure edition XT1575.
Problem:
The first time i loaded the os, my phone couldnt boot. it was stuck on the bootloader screen for days until i found a file that i ran in my recovery called SR3 SuperSU v2.78 it helped my phone get out of the bootloader page and i was finally able to use my phone and everything was great! until somebody called.
The phone is connected to my cell network and the phone will ring and i can call out. But, when i hit the phone but it does not display the call window. sometimes i dont realize i am calling somebody until i hear a small "Hello?". while i am on the call with the other person I am on the home screen and can not hang up the call. When others call me my phone rings but it only displays the home screen and it will not allow me to answer the call. All i can do is wait for the phone to stop ringing and hit the call button to call them back. I cannot call my voicemail as there is no keypad. only the home screen and yes i tend to pull up apps with my face.
The only solution i have to this problem is to connect a bluetooth device to it. I have been wearing my Gear S2 3G around so i could make and answer calls minus the use of the voice functionality. Voice commands do not work on my smartwatch anymore for some reason. I have to manually turn the dial to select the contact i would like to call. I can still add phone numbers on the phone (this function didnt work before until i installed another os then reinstalled it). but quite frankly, there is a time i would like to be able to pick up my phone and just answer an incoming call rather then fiddling around with this watch all the time. trying to keep it charged.
What I have tried:
I have tried a number of things. installing a new boot img, new recovery, downloading a new kernel. loading all new img folders into the command prompt. Then my laptop was acting up and i had to reinstall windows to fix it. A friend of mine suggested I should work on getting back my original os and reload some working folders . Ok, so i followed the steps and noticed my command prompt now will not read my phone to load the new img's and i noticed the drivers are not installed. ok, im working with a new computer basically and it doesnt quite recognize my phone. so i installed motorola device manager. adb, usb and the other driver has installed correctly, cool. I tried the casual test on the command prompt "adb devices" it didnt recognize it...ok? so i tried to type in the recovery img like before. nothing. tried to boot up the bootloader. nothing. what is going on here? i have all the drivers and the files waiting to go into the phone. I even restarted the computer to finalize the changes i made to the computer. nothing i have tried works.
what am i going to try next?
clockworkmod... if this doesnt work then i dont know what will.
If there are any suggestions out there any anyone that can help me with the problems that i am having with my phone please reply to this post. Thank you for any help that is posted up here. I will try to comment on what method has worked for me so that whoever has this problem will be able to fix this very simple functionality for a phone. I mean what is the point of carrying around a phone that cannot make or receive phone calls? sure its rooted and thats all cool and fancy. but its laughable that my phone cannot handle what a phone is supposed to do. At this point i might be carrying around 2 phones with me. its ridiculous lol. A phone that cannot call people. I have a small tablet. its not even a phone anymore lol. its a fancy tablet. please comment below, thank you guys!

(update)
I just followed the instructions on this link (http://forum.xda-developers.com/moto-x-style/general/xt1572-mm-twrp-root-xposed-t3276792) from another member of this site. I restored my phone to the way it was when i bought it. but i dont have any connection through my data nor can i connect to wifi. will update again when i find a fix.

Tacoman64 said:
Make: Motorola
Model: Moto X Pure Edition (Style) XT1575
OS: 6.0 Marshmallow
Rooted: yes
Bootloader: you'd better believe it
Hello,
I am having a little trouble with the calling function on my moto x pure edition XT1575.
Problem:
The first time i loaded the os, my phone couldnt boot. it was stuck on the bootloader screen for days until i found a file that i ran in my recovery called SR3 SuperSU v2.78 it helped my phone get out of the bootloader page and i was finally able to use my phone and everything was great! until somebody called.
The phone is connected to my cell network and the phone will ring and i can call out. But, when i hit the phone but it does not display the call window. sometimes i dont realize i am calling somebody until i hear a small "Hello?". while i am on the call with the other person I am on the home screen and can not hang up the call. When others call me my phone rings but it only displays the home screen and it will not allow me to answer the call. All i can do is wait for the phone to stop ringing and hit the call button to call them back. I cannot call my voicemail as there is no keypad. only the home screen and yes i tend to pull up apps with my face.
The only solution i have to this problem is to connect a bluetooth device to it. I have been wearing my Gear S2 3G around so i could make and answer calls minus the use of the voice functionality. Voice commands do not work on my smartwatch anymore for some reason. I have to manually turn the dial to select the contact i would like to call. I can still add phone numbers on the phone (this function didnt work before until i installed another os then reinstalled it). but quite frankly, there is a time i would like to be able to pick up my phone and just answer an incoming call rather then fiddling around with this watch all the time. trying to keep it charged.
What I have tried:
I have tried a number of things. installing a new boot img, new recovery, downloading a new kernel. loading all new img folders into the command prompt. Then my laptop was acting up and i had to reinstall windows to fix it. A friend of mine suggested I should work on getting back my original os and reload some working folders . Ok, so i followed the steps and noticed my command prompt now will not read my phone to load the new img's and i noticed the drivers are not installed. ok, im working with a new computer basically and it doesnt quite recognize my phone. so i installed motorola device manager. adb, usb and the other driver has installed correctly, cool. I tried the casual test on the command prompt "adb devices" it didnt recognize it...ok? so i tried to type in the recovery img like before. nothing. tried to boot up the bootloader. nothing. what is going on here? i have all the drivers and the files waiting to go into the phone. I even restarted the computer to finalize the changes i made to the computer. nothing i have tried works.
what am i going to try next?
clockworkmod... if this doesnt work then i dont know what will.
If there are any suggestions out there any anyone that can help me with the problems that i am having with my phone please reply to this post. Thank you for any help that is posted up here. I will try to comment on what method has worked for me so that whoever has this problem will be able to fix this very simple functionality for a phone. I mean what is the point of carrying around a phone that cannot make or receive phone calls? sure its rooted and thats all cool and fancy. but its laughable that my phone cannot handle what a phone is supposed to do. At this point i might be carrying around 2 phones with me. its ridiculous lol. A phone that cannot call people. I have a small tablet. its not even a phone anymore lol. its a fancy tablet. please comment below, thank you guys!
Click to expand...
Click to collapse
The problem here is we don't know your phones state and what files you have used and what you have done...
To be honest, at this point I would do a full reflash back to pure stock. The instruction link is in my signature (you don't have to lock, that is optional). Once you are in a known good state, then maybe you can root the right way.

Found the problem (no solution yet)
it seems all of my files are running fine when i enter them into the command prompt but the only one that is not working is the gpt.bin.
(fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.369s)
I didnt just copy and paste the name. i manually typed it but it just doesnt work for some reason. hope this information helps.

Tacoman64 said:
it seems all of my files are running fine when i enter them into the command prompt but the only one that is not working is the gpt.bin.
(fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.369s)
I didnt just copy and paste the name. i manually typed it but it just doesnt work for some reason. hope this information helps.
Click to expand...
Click to collapse
Yup... As I suspected... "Preflash validation failed" means you are attempting to flash an older Android version than you have already installed. You need to use a newer/newest firmware version.

(update)
I have successfully unrooted my device. I have typed all the file commands in the command prompt and the only error i got was a preflash validation failed error. I read a few forums to make sure that this was not going to brick my device and found out. Because i am not upgrading my os. the gpt.bin file really isnt necessary. I suppose it would be good to try to code it in anyways but if it fails then it should be fine.
THE PROBLEM:
Was another file wasnt installing correctly. I think the first time i typed in Flash modem NON-HLOS.bin It must have failed before but i didnt see it. It failed again on me but i sent the command again and it successfully installed (huh... weird).
In Conclusion:
So it goes to show you.
Rule 1: OPEN command prompt in the same folder you have your files extracted on by holding shift+right click. It should have an option to open command prompt. (if you've tried it multiple times then put the files in a new folder)
Rule 2: CHECK YOUR COMMANDS! see if they have installed correctly. gpt.bin file doesnt mean anything if you're not upgrading your original os.
Rule 3reverts to rule 2) CHECK your NON-HLOS.bin file in your commands list to see if it downloads correctly to you command prompt.
Rule 4:NO FAILURES. NONE of these other files should say failed and if they do. RE-TYPE them in. If that doesnt work. then download another file. you might just either have a broken file, it didnt download correctly or it might just be the wrong one. find the right file for your model number of phone!
This is to all those who dont know much about computers.
Rule 5: MISSING FILES. If there are any missing files then check your files. the failures could be due to not extracting your files, not downloading the proper files, and simply typing them incorrectly. ex. fastboot flash logo "logo.bin". if your logo name is not "logo.bin" and you just copy pasted it. the file will fail. your file could say something different like "XT1575-logo-new-9-14-15.bin". So instead, type in "fastboot flash logo XT1575-logo-new-9-14-15.bin" it should successfully download. If it doesnt. revert back to the previous rules.
NOW: On to Re-Rooting my device.

Tacoman64 said:
I have successfully unrooted my device. I have typed all the file commands in the command prompt and the only error i got was a preflash validation failed error. I read a few forums to make sure that this was not going to brick my device and found out. Because i am not upgrading my os. the gpt.bin file really isnt necessary. I suppose it would be good to try to code it in anyways but if it fails then it should be fine.
THE PROBLEM:
Was another file wasnt installing correctly. I think the first time i typed in Flash modem NON-HLOS.bin It must have failed before but i didnt see it. It failed again on me but i sent the command again and it successfully installed (huh... weird).
In Conclusion:
So it goes to show you.
Rule 1: OPEN command prompt in the same folder you have your files extracted on by holding shift+right click. It should have an option to open command prompt. (if you've tried it multiple times then put the files in a new folder)
Rule 2: CHECK YOUR COMMANDS! see if they have installed correctly. gpt.bin file doesnt mean anything if you're not upgrading your original os.
Rule 3reverts to rule 2) CHECK your NON-HLOS.bin file in your commands list to see if it downloads correctly to you command prompt.
Rule 4:NO FAILURES. NONE of these other files should say failed and if they do. RE-TYPE them in. If that doesnt work. then download another file. you might just either have a broken file, it didnt download correctly or it might just be the wrong one. find the right file for your model number of phone!
This is to all those who dont know much about computers.
Rule 5: MISSING FILES. If there are any missing files then check your files. the failures could be due to not extracting your files, not downloading the proper files, and simply typing them incorrectly. ex. fastboot flash logo "logo.bin". if your logo name is not "logo.bin" and you just copy pasted it. the file will fail. your file could say something different like "XT1575-logo-new-9-14-15.bin". So instead, type in "fastboot flash logo XT1575-logo-new-9-14-15.bin" it should successfully download. If it doesnt. revert back to the previous rules.
NOW: On to Re-Rooting my device.
Click to expand...
Click to collapse
Actually, your experience is not weird... it is not uncommon for NON-HLOS to fail the first time, subsequent attempts usually work... no idea why, some people say to use the erase modemst# commends first, others don't...
You are still in a mixed environment, the fact your are getting a preflash validation error means your partition table is newer than the one you are attempting to flash, this your device is out of sync (all your partitions don't match version wise). Although this condition itself will not result in bricking, taking an OTA later could cause that (we don't know, it could potentially). Something is definitely amiss, otherwise the gpt.bin would flash and go fine, but the phone KNOWS the partition table you are attempting to flash is older than the one on the device, that should tell you something. If you are going to flash a custom ROM, oh well, but if you are going to stay stock you should flash the latest 18-4 firmware image completely.

my intentions are to root my phone. I was just repairing my call functionality so i could receive phone calls. my phone works now. i can call people and i think receive calls because the call page pulls up when i call out. i dont know if i could receive calls because my phone is currently not activated. (not a phone issue, just didnt pay the bill) when my phone was activated with the root. the phone would ring but no call came up and when i called out the phone page would not be there. so i couldnt hang up a call or access the number pad while in a call for automated systems. now i can so i think that part of it is fixed. I am currently following one of your how to pages but it doesnt explain how to install twrp on the phone. it only says to go to advanced mode of what i believe to be the advanced mode on the recovery menu and put in that command before installing supersu. im still looking for command prompts on how to reinstall my recovery and trying to better understand what advanced setting you are trying to point out.

ITS ALIVE!!!
My phone is now FIXED and ROOTED! thanks to all of you wonderful people out there who helped me! posting up the wonderful posts that include all of the files, data and commands i needed to make this possible. Thank you all again! You guys are the best. now all there is to do is to put some mods on here and have fun with my new toy

acejavelin said:
Actually, your experience is not weird... it is not uncommon for NON-HLOS to fail the first time, subsequent attempts usually work... no idea why, some people say to use the erase modemst# commends first, others don't...
You are still in a mixed environment, the fact your are getting a preflash validation error means your partition table is newer than the one you are attempting to flash, this your device is out of sync (all your partitions don't match version wise). Although this condition itself will not result in bricking, taking an OTA later could cause that (we don't know, it could potentially). Something is definitely amiss, otherwise the gpt.bin would flash and go fine, but the phone KNOWS the partition table you are attempting to flash is older than the one on the device, that should tell you something. If you are going to flash a custom ROM, oh well, but if you are going to stay stock you should flash the latest 18-4 firmware image completely.
Click to expand...
Click to collapse
I made a how to explaining step by step. how to properly root the moto x pure and or all 6.0 motorola's If you would like to check out, make corrections to my post feel free, and or if you have any suggestions on how to make it better please let me know. http://forum.xda-developers.com/moto-x-style/general/how-to-unlock-root-moto-x-pure-style-t3504263

Tacoman64 said:
I made a how to explaining step by step. how to properly root the moto x pure and or all 6.0 motorola's If you would like to check out, make corrections to my post feel free, and or if you have any suggestions on how to make it better please let me know. http://forum.xda-developers.com/moto-x-style/general/how-to-unlock-root-moto-x-pure-style-t3504263
Click to expand...
Click to collapse
It's funny because my guide went live the other day, just haven't added it to my sig yet... http://forum.xda-developers.com/moto-x-style/general/guide-how-to-root-pure-style-t3503958

acejavelin said:
It's funny because my guide went live the other day, just haven't added it to my sig yet... http://forum.xda-developers.com/moto-x-style/general/guide-how-to-root-pure-style-t3503958
Click to expand...
Click to collapse
I seen that that's where I got the code I was missing the first time around. I am about to create another post and attach that link to it on here too. So if someone were to mess up their phone by skipping or not checking the command prompt then they have a plan B. I'll be the simple 1 stop post for every issue on Motorola like Walmart lol. I think it will get cluttered though.