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!

How do I flash back stock? v.SignatureMismatch,BootLoop,etc

We have a handfull of TF300T's and I am sure the answer is on here somewhere but I keep searching and can't find exactly what I am looking for.
I have some tablets that boot loop, some that turn on and say signature mismatch, and some that just stick on ASUS and one that says unlocked at the top in small text but that's it. What's the one thing I can do to all of them to just reflash them back to factory state? Everything I search involves getting back to rooted and unlocked.
Thanks guys.

New motherboard
Or
Sell it for parts
Or
Test to get rma with asus
Sent from my TF300T using xda app-developers app

okrasitna said:
New motherboard
Or
Sell it for parts
Or
Test to get rma with asus
Sent from my TF300T using xda app-developers app
Click to expand...
Click to collapse
Really? There's no way around that? They really reach a point where they're not flashable?

kmad86 said:
Really? There's no way around that? They really reach a point where they're not flashable?
Click to expand...
Click to collapse
You would need to take each as an individual and find what access you have (bootloader, recovery(stock, cwm, or twrp), adb, fastboot. At this time the only way to treat them as a group would be rma to Asus.
Yes they reach a point where we don't have methods to recover them and there are many hoping that will change in the future.
Take a unit, verify the conditions and I am sure you will find many threads for each case. Some meet with success and others don't. If time is a controlling factor you could try ebay for motherboards as mentioned in the post above. My understanding the cost of a motherboard on ebay is much less then an rma to Asus.
Good Luck!

tobdaryl said:
You would need to take each as an individual and find what access you have (bootloader, recovery(stock, cwm, or twrp), adb, fastboot. At this time the only way to treat them as a group would be rma to Asus.
Yes they reach a point where we don't have methods to recover them and there are many hoping that will change in the future.
Take a unit, verify the conditions and I am sure you will find many threads for each case. Some meet with success and others don't. If time is a controlling factor you could try ebay for motherboards as mentioned in the post above. My understanding the cost of a motherboard on ebay is much less then an rma to Asus.
Good Luck!
Click to expand...
Click to collapse
I appreciate it. I'll see what I can figure out. Right now my first obstacle to tackle is the "signature not matched" on boot.
While I am thinking about it, what's the actual proper way to get a firmware update? It prompted me on the 4017, but I've been told there's a 4020 but my tab won't find it if I just search for update.

kmad86 said:
I appreciate it. I'll see what I can figure out. Right now my first obstacle to tackle is the "signature not matched" on boot.
While I am thinking about it, what's the actual proper way to get a firmware update? It prompted me on the 4017, but I've been told there's a 4020 but my tab won't find it if I just search for update.
Click to expand...
Click to collapse
Signature mismatch occurs when the bootloader in the tablet and the one being flashed don't match or the one most recently flashed. There are three bootloaders for this unit. ICS (4.0), JB (4.1), and JB 4.2 (4.2) each of these have associated firmware. Not like 4017 or 4020. Instead: ICS = 9.4.3.29 or 9.4.3.30 - JB 10.4.2.9 or 10.4.2.13 or 10.4.2.17 or 10.4.2.18 or 10.4.2.20 - JB 4.2 10.6.1.8. I don't know what the numbers you listed represent.
Some units never seem to get updated ota(over the air). Assuming the unit boots into the os look in Settings/About Tablet/Build number. I don't suggest updating to 4.2 at this time -if you should the tablet should be on 10.4.2.20 beforehand.
Download firmware one numeric higher than the one listed in settings. Unzip once and place the resulting zip on your internal sdcard or place on your micro sdcard and copy to the internal sdcard. Sometimes the file will be accepted on the external sdcard. Watch notifications in lower right -you are looking for a triangle to appear. If it doesn't appear in a minute or two reboot the tablet and wait again. If it appears accept the update and wait about ten minutes for completion.
If the above fails download the firmware and unzip once as above. Name the resulting zip EP201_768_SDUPDATE.zip and place on internal sdcard and follow the above directions. If that fails power tablet off, power on while holding power and volume down -when the icons appear press volume up while on the RCK icon - stock recovery should take over and accept the update.

tobdaryl said:
Signature mismatch occurs when the bootloader in the tablet and the one being flashed don't match or the one most recently flashed. There are three bootloaders for this unit. ICS (4.0), JB (4.1), and JB 4.2 (4.2) each of these have associated firmware. Not like 4017 or 4020. Instead: ICS = 9.4.3.29 or 9.4.3.30 - JB 10.4.2.9 or 10.4.2.13 or 10.4.2.17 or 10.4.2.18 or 10.4.2.20 - JB 4.2 10.6.1.8. I don't know what the numbers you listed represent.
Some units never seem to get updated ota(over the air). Assuming the unit boots into the os look in Settings/About Tablet/Build number. I don't suggest updating to 4.2 at this time -if you should the tablet should be on 10.4.2.20 beforehand.
Download firmware one numeric higher than the one listed in settings. Unzip once and place the resulting zip on your internal sdcard or place on your micro sdcard and copy to the internal sdcard. Sometimes the file will be accepted on the external sdcard. Watch notifications in lower right -you are looking for a triangle to appear. If it doesn't appear in a minute or two reboot the tablet and wait again. If it appears accept the update and wait about ten minutes for completion.
If the above fails download the firmware and unzip once as above. Name the resulting zip EP201_768_SDUPDATE.zip and place on internal sdcard and follow the above directions. If that fails power tablet off, power on while holding power and volume down -when the icons appear press volume up while on the RCK icon - stock recovery should take over and accept the update.
Click to expand...
Click to collapse
Thanks for the great info! However, I can't get into it to verify what software it has at all. In that case what would I do?
Also, where do I download the firmware? Sorry for all the questions, trying to wrap my head around all this and a the stuff I've been reading in search is all about modified software/roms. Not a lot of information on stock stuff that I could find.

kmad86 said:
Thanks for the great info! However, I can't get into it to verify what software it has at all. In that case what would I do?
Also, where do I download the firmware? Sorry for all the questions, trying to wrap my head around all this and a the stuff I've been reading in search is all about modified software/roms. Not a lot of information on stock stuff that I could find.
Click to expand...
Click to collapse
Here is a link for downloading the firmware and most other things you may need to download or references to things you might need to know. Look through at least the first three posts.
[INDEX]13 Mar 2013 - TF300T/TG WITH ALL ASUS ORIGINAL TOOLS-Firmwares-Kernels-Guides
Not knowing what firmware is in each unit I believe I'd try 10.4.2.20 as my base line. That is the newest JB (4.1) firmware.
Note: The firmware numbers I have used relate to TF300T units and US skus.
The methods I gave for updating firmware all assume stock recovery is installed which is the best place to start.
mismatch in general section - http://forum.xda-developers.com/search.php?searchid=163947942
mismatch in Q&A - http://forum.xda-developers.com/search.php?searchid=163948372
bootloop in general - http://forum.xda-developers.com/search.php?searchid=163948615
bootloop in Q&A - http://forum.xda-developers.com/search.php?searchid=163948785
Note 2: If you are unable to get into the os the only method above that is useful is the last.
If the above fails download the firmware and unzip once as above. Name the resulting zip EP201_768_SDUPDATE.zip and place on internal sdcard and follow the above directions. If that fails power tablet off, power on while holding power and volume down -when the icons appear press volume up while on the RCK icon - stock recovery should take over and accept the update.
Holding power and volume down is a attempt to get into the bootloader (apx is useless). See my signature for a link about getting into the bootloader.
If you don't have drivers properly loaded for this tablet and you are on windows see my signature for a link to get them properly loaded.

tobdaryl said:
Here is a link for downloading the firmware and most other things you may need to download or references to things you might need to know. Look through at least the first three posts.
[INDEX]13 Mar 2013 - TF300T/TG WITH ALL ASUS ORIGINAL TOOLS-Firmwares-Kernels-Guides
Not knowing what firmware is in each unit I believe I'd try 10.4.2.20 as my base line. That is the newest JB (4.1) firmware.
Note: The firmware numbers I have used relate to TF300T units and US skus.
The methods I gave for updating firmware all assume stock recovery is installed which is the best place to start.
mismatch in general section - http://forum.xda-developers.com/search.php?searchid=163947942
mismatch in Q&A - http://forum.xda-developers.com/search.php?searchid=163948372
bootloop in general - http://forum.xda-developers.com/search.php?searchid=163948615
bootloop in Q&A - http://forum.xda-developers.com/search.php?searchid=163948785
Click to expand...
Click to collapse
Wow, I really appreciate this! I'm going to check it over.

kmad86 said:
Wow, I really appreciate this! I'm going to check it over.
Click to expand...
Click to collapse
Reread my last post as I added some useful info.
We were overlapping posts and I see I had not finished typing when you responded.
I'll be offline for an hour or two but I'll check later.

tobdaryl said:
Reread my last post as I added some useful info.
We were overlapping posts and I see I had not finished typing when you responded.
I'll be offline for an hour or two but I'll check later.
Click to expand...
Click to collapse
none of the links work for me. they bring me back to the main forum.
mismatch in general section - http://forum.xda-developers.com/sear...chid=163947942
mismatch in Q&A - http://forum.xda-developers.com/sear...chid=163948372
bootloop in general - http://forum.xda-developers.com/sear...chid=163948615
bootloop in Q&A - http://forum.xda-developers.com/sear...chid=163948785
Click to expand...
Click to collapse

tobdaryl said:
Reread my last post as I added some useful info.
We were overlapping posts and I see I had not finished typing when you responded.
I'll be offline for an hour or two but I'll check later.
Click to expand...
Click to collapse
Ok, so I tried the Power+down with the SD card and the zip file on one that had no touch at all. IT WORKED!
At first I thought it was messed up and it froze on the android on it's back with the red triangle. I reset it after 5 minutes and it went to ASUS with a blue progress bar and then worked.
One problem fixed!

kmad86 said:
Also, I tried the Power+Down and booted with the SD card in it and the .zip. It seems like it started to work and about two minutes in with the android and the red triangle, everything seemed to freeze and never unfroze.
Click to expand...
Click to collapse
Note 2: You need to think about getting adb and fastboot working properly.
adb can be accessed when powered on and just sitting there
and when booted into cwm or twrp
fastboot get into the bootloader (power and volume down) press volume down to choose the usb icon then volume up to select - this would be on the 4.0 and 4.1 bootloader - if you have the 4.2 bootloader there is no usb icon and the tablet if left will auto turn on fastboot (look in upper left for the message) (DO NOT USE WIPE DATA IN THE BOOTLOADER)
test if adb is working by typing
adb devices
test if fastboot is working by typing
fastboot devices
each will return the unit serial number or all zeros when working
I'm sorry to do a piece at a time but there are so many options etc
Searching
go to general (example) without choosing a thread look in the upper right for search to the right of this there is a gear select that (advanced search) - in search by keyword type mismatch (example) - scroll to the bottom and click search.
This example searches all general threads and all posts within these threads.

tobdaryl said:
Note 2: You need to think about getting adb and fastboot working properly.
adb can be accessed when powered on and just sitting there
and when booted into cwm or twrp
fastboot get into the bootloader (power and volume down) press volume down to choose the usb icon then volume up to select - this would be on the 4.0 and 4.1 bootloader - if you have the 4.2 bootloader there is no usb icon and the tablet if left will auto turn on fastboot (look in upper left for the message) (DO NOT USE WIPE DATA IN THE BOOTLOADER)
test if adb is working by typing
adb devices
test if fastboot is working by typing
fastboot devices
each will return the unit serial number or all zeros when working
I'm sorry to do a piece at a time but there are so many options etc
Searching
go to general (example) without choosing a thread look in the upper right for search to the right of this there is a gear select that (advanced search) - in search by keyword type mismatch (example) - scroll to the bottom and click search.
This example searches all general threads and all posts within these threads.
Click to expand...
Click to collapse
a piece at a time is fine for me. I'm learning! I really do appreciate the help.
I don't have any software downloaded but the ASUS sync program. I need to download cwp and twrp as now I am realizing those are programs.
I tried the same MicroSD trick on another tablet with touch problems, and it went through the process but booted back to a really weird screen and I still have no touch.
Picture of Screen
{
"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"
}

kmad86 said:
a piece at a time is fine for me. I'm learning! I really do appreciate the help.
I don't have any software downloaded but the ASUS sync program. I need to download cwp and twrp as now I am realizing those are programs.
I tried the same MicroSD trick on another tablet with touch problems, and it went through the process but booted back to a really weird screen and I still have no touch.
Picture of Screen
Click to expand...
Click to collapse
That's an interesting screen I have never seen. I don't know what it is but may be useful.
I forgot to cover something in my last post.
The android lying on his back is stock recovery with no file to process. We need to get adb and fastboot working properly. We can use adb to push our file to the internal sdcard and let stock recovery process it for us.
Tell me about your pc! Windows 7, 8, linux, mac?

tobdaryl said:
That's an interesting screen I have never seen. I don't know what it is but may be useful.
I forgot to cover something in my last post.
The android lying on his back is stock recovery with no file to process. We need to get adb and fastboot working properly. We can use adb to push our file to the internal sdcard and let stock recovery process it for us.
Tell me about your pc! Windows 7, 8, linux, mac?
Click to expand...
Click to collapse
I have a windows 7 laptop that I can use. I am primarily mac but I know Windows is best for these.
I just tried another, and got the same screen as above with no touch.

kmad86 said:
I have a windows 7 laptop that I can use. I am primarily mac but I know Windows is best for these.
I just tried another, and got the same screen as above with no touch.
Click to expand...
Click to collapse
Good choice!
Read your pm and let me know what I have forgotten or anything you don't understand.
For the moment let's use the tablet you began with and finish the thread for any who are watching or come later. We'll need to consider another communication vehicle for the remainder.

tobdaryl said:
Note 2: You need to think about getting adb and fastboot working properly.
adb can be accessed when powered on and just sitting there
and when booted into cwm or twrp
fastboot get into the bootloader (power and volume down) press volume down to choose the usb icon then volume up to select - this would be on the 4.0 and 4.1 bootloader - if you have the 4.2 bootloader there is no usb icon and the tablet if left will auto turn on fastboot (look in upper left for the message) (DO NOT USE WIPE DATA IN THE BOOTLOADER)
test if adb is working by typing
adb devices
test if fastboot is working by typing
fastboot devices
each will return the unit serial number or all zeros when working
I'm sorry to do a piece at a time but there are so many options etc
Searching
go to general (example) without choosing a thread look in the upper right for search to the right of this there is a gear select that (advanced search) - in search by keyword type mismatch (example) - scroll to the bottom and click search.
This example searches all general threads and all posts within these threads.
Click to expand...
Click to collapse
In my years of computer experiences, usually my friends come to me to help them out. With this, I am so lost and feel so hopeless as I am starting to understand how they feel most of the time.
Anyhow. I am really lost with the CWM and TWRP thing. CWM seems to need to be installed through the tablet in the android store and runs on it? TWRP also seems to need installed on the tablet and used on it. I was assuming I would install something on the windows computer that communicates with the tablet to get it going. I think that's why I am so off track here.
When you say type "adb devices" to verify it's working. Where am I typing that? In the SDK kit somewhere?

kmad86 said:
In my years of computer experiences, usually my friends come to me to help them out. With this, I am so lost and feel so hopeless as I am starting to understand how they feel most of the time.
Anyhow. I am really lost with the CWM and TWRP thing. CWM seems to need to be installed through the tablet in the android store and runs on it? TWRP also seems to need installed on the tablet and used on it. I was assuming I would install something on the windows computer that communicates with the tablet to get it going. I think that's why I am so off track here.
When you say type "adb devices" to verify it's working. Where am I typing that? In the SDK kit somewhere?
Click to expand...
Click to collapse
Sorry that is one I missed. Forget CWM. Both CWM and Twrp are custom recoveries used to replace stock recovery. They can be used to flash stock rom or custom rom, root, and etc.
Let's stick with the this thread for now as we are overlapping. Go to android-sdk/tools and run android.bat. Install Android SDK Platform-tools. This will add the android-sdk/platform-tools directory and inside you will find adb and fastboot. They should be run as administrator with cmd (terminal - cmd - command prompt).

tobdaryl said:
Sorry that is one I missed. Forget CWM. Both CWM and Twrp are custom recoveries used to replace stock recovery. They can be used to flash stock rom or custom rom, root, and etc.
Let's stick with the this thread for now as we are overlapping. Go to android-sdk/tools and run android.bat. Install Android SDK Platform-tools. This will add the android-sdk/platform-tools directory and inside you will find adb and fastboot. They should be run as administrator with cmd (terminal - cmd - command prompt).
Click to expand...
Click to collapse
One more thing, is all of this for signature mismatch, or the no touch ones?
I'm slowly grasping this!

Help an idiot flash a factory image

So i decided a few days ago to try and flash a factory image for kitkat on my N7. But i downloaded the image for the wrong device. the script has wiped recovery and system etc. The N7 now just boots to bootloader.
i got the proper factory image to flash, but i cannot get the device recognized on the pc running Windows 7 now. its showing as Other Devices / Android. I did install the drivers from the SDK and it now appears as Android ADB Interface. However ADB is still not recognizing it. I have done adb devices but nothing is found.
Any help, it is fixable isnt it??

You can't use adb commands in fastboot. You should use fastboot commands and flash the factory image
Sent from my Nexus 5

Tones1971 said:
So i decided a few days ago to try and flash a factory image for kitkat on my N7. But i downloaded the image for the wrong device. the script has wiped recovery and system etc. The N7 now just boots to bootloader.
i got the proper factory image to flash, but i cannot get the device recognized on the pc running Windows 7 now. its showing as Other Devices / Android. I did install the drivers from the SDK and it now appears as Android ADB Interface. However ADB is still not recognizing it. I have done adb devices but nothing is found.
Any help, it is fixable isnt it??
Click to expand...
Click to collapse
Well, I had a serious issue with something similar, after trying to update (not flash the factory image) to KitKat it produced an error and now it's bootlooping and, worse, my computer won't recognize the device, so I can't flash the factory image whatsoever. Your problem is much more light, as your computer is actually recognizing the device. What I'd suggest is using the Nexus Root Toolkit by WugFresh. Yes, I know, a lot of people here don't like using it but it's extremely useful when you have drivers issues.
It's actually a pretty straight forward procedure, you install the toolkit and it will ask you for your device model, android version, etc., then take you through the process of updates and stuff. Then, on the main window, you have this wizard "Full Driver Installation Guide" that will give you 4 ways to get your device working. You can find the Toolkit here: http://www.wugfresh.com/nrt/. Good luck!

I vote we ban all talk of toolkits. 99.9% of the help threads around here start with, "I was using/used x toolkit and now my device won't boot."
What happened to people learning about their devices?
How about learning how to fix your problems, rather than compound them by not understanding what you are doing? How about if you don't have the capacity to learn it, you leave it the F alone?
Sent from my Nexus 5

Pirateghost said:
I vote we ban all talk of toolkits. 99.9% of the help threads around here start with, "I was using/used x toolkit and now my device won't boot."
What happened to people learning about their devices?
How about learning how to fix your problems, rather than compound them by not understanding what you are doing? How about if you don't have the capacity to learn it, you leave it the F alone?
Sent from my Nexus 5
Click to expand...
Click to collapse
It's also difficult when trying to assist somebody... they're using the vocabulary of toolkits (which I'm not familiar with)... and I'm going on about fastboot... which they don't understand. It's like there are now two different languages... TOOLKIT and FASTBOOT.
Makes it very difficult to assist people.
Maybe I should have a tinker with Wugfresh... if for no other reason than to at least get an insight into how these things work.
Rgrds,
Ged.

The concept of the toolkit is great. It's the implementation and use of it that is horrible.
I think a toolkit should walk you through the actual steps and force you to type in the commands. You select an option of what you want it to do, it tells you what to type step by step to achieve said goal, and checks that you don't type in the wrong thing for the option you selected.
Unfortunately I don't think there is a market for that when you can get everything 'one clicked' for you.
Sent from my Nexus 5

Pirateghost said:
The concept of the toolkit is great. It's the implementation and use of it that is horrible.
I think a toolkit should walk you through the actual steps and force you to type in the commands. You select an option of what you want it to do, it tells you what to type step by step to achieve said goal, and checks that you don't type in the wrong thing for the option you selected.
Unfortunately I don't think there is a market for that when you can get everything 'one clicked' for you.
Sent from my Nexus 5
Click to expand...
Click to collapse
So an edit box where you could be prompted to type in things like fastboot flash recovery recovery.img... interesting idea... sort of walks you through the process, but doesn't obsessively hold your hand, where you don't learn anything.
I suspect most people just have problems with drivers, because, let's face it, fastboot and ADB aren't exactly difficult to use... unless people have difficulty understanding command lines in these GUI driven days, where everything is a simple menu or button click away... kind of sad really.
Rgrds,
Ged.

GedBlake said:
So an edit box where you could be prompted to type in things like fastboot flash recovery recovery.img... interesting idea... sort of walks you through the process, but doesn't obsessively hold your hand, where you don't learn anything.
I suspect most people just have problems with drivers, because, let's face it, fastboot and ADB aren't exactly difficult to use... unless people have difficulty understanding command lines in these GUI driven days, where everything is a simple menu or button click away... kind of sad really.
Rgrds,
Ged.
Click to expand...
Click to collapse
Basically yeah.
I have a feeling a good portion of the hesitation comes from the command line being scary to most people.
Sent from my Nexus 5

In the tgz file you download there is a 'flash-all.bat' file that does everything for you. If you open it in notepad, you see exactly what it does and in what order.
Yes, drivers are probably the issue, they were for me at least. I ended up using NRT (wugs toolkit) to install drivers (and root later, but that's a new topic)
Code:
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
ping -n 10 127.0.0.1 >nul
fastboot -w update image-nakasi-jwr66y.zip
echo Press any key to exit...
pause >nul
exit
This is a Google way to flash the factory image.
---------- Post added at 10:02 PM ---------- Previous post was at 09:59 PM ----------
Pirateghost said:
The concept of the toolkit is great. It's the implementation and use of it that is horrible.
I think a toolkit should walk you through the actual steps and force you to type in the commands. You select an option of what you want it to do, it tells you what to type step by step to achieve said goal, and checks that you don't type in the wrong thing for the option you selected.
Unfortunately I don't think there is a market for that when you can get everything 'one clicked' for you.
Sent from my Nexus 5
Click to expand...
Click to collapse
The idea is great, try writing it
I'm sure it'll be greeted with appreciation.

Tones1971 said:
So i decided a few days ago to try and flash a factory image for kitkat on my N7. But i downloaded the image for the wrong device. the script has wiped recovery and system etc. The N7 now just boots to bootloader.
i got the proper factory image to flash, but i cannot get the device recognized on the pc running Windows 7 now. its showing as Other Devices / Android. I did install the drivers from the SDK and it now appears as Android ADB Interface. However ADB is still not recognizing it. I have done adb devices but nothing is found.
Any help, it is fixable isnt it??
Click to expand...
Click to collapse
As long as you can still boot into bootloader mode, it is still fixable. Try reinstalling fastboot drivers.

Pirateghost said:
I vote we ban all talk of toolkits. 99.9% of the help threads around here start with, "I was using/used x toolkit and now my device won't boot."
What happened to people learning about their devices?
How about learning how to fix your problems, rather than compound them by not understanding what you are doing? How about if you don't have the capacity to learn it, you leave it the F alone?
Sent from my Nexus 5
Click to expand...
Click to collapse
Yeah, because that was really helpful to him. I didn't tell him to use the toolkit to flash, root, unlock, or anything of the sort. For drivers issues, I do recommend (and will continue to do so) using the toolkit when official drivers don't work, because it has helped me a lot in the past, but I haven't used it to flash anything.

Download the image for your device and extract it into a folder
Download the zip below and move the files into the folder you created above
http://forum.xda-developers.com/showthread.php?t=1484407
Switch device off. Hold volume down and turn it back on, so it's in fastboot mode
Plug device into computer
Run "flash-all.bat" in the system image folder you extracted first

Want to thank everybody for their replies. Have had a family emergency so havent had a chance to try any suggestions, but didnt want to just ignore the thread i started.

ROOT with PIE Guide

Hi All,
In the best interest to provide clarity I'm creating this quick and easy tutorial on how to root your Razer Phone 2 after the Pie Upgrade. Please send me any feedback to improve this post, we need to build up a strong community.
*As usual, I'm not responsible of any damage or brick to your phone, do it at your own risk.
Pre-Requirements:
-Be sure to have at least 70% of charges... or plug your phone to power
-Backup anything you consider important
-Already installed Pie Upgrade via OTA or Side Loaded​
-Enable Developer Options
• Open Phone "Settings" and scroll down.
• You will see an option "Build Number".
• Simply tap on it 7 times to enable it on your Android Oreo based device.
• Your device immediately display a message on screen that will say "You are now a developer".
• The Developer Option is now available in the Settings>System>Developer Options. Enjoy!​
- Install Android Drivers (https://developer.android.com/studio/run/win-usb) and ADB, I personally recommend -[TOOL]Minimal ADB and Fastboot [2-9-18] - https://forum.xda-developers.com/showthread.php?t=2317790
-Unlock Bootloader
• To enable OEM unlock, go to Settings > Developer options and check Enable OEM unlock
• Using ADB commands reboot on bootloader​
adb reboot bootloader​
• After reboot completes follow phone menus and select "UNLOCK BOOTLOADER"; accept all warnings, after restart you have completed the unlock.​
Root and Installing Magisk
Since our phone doesn't have a proven customer recovery fully working (Ex TWRP) Magisk needs to be installed by manually patching the device boot image.
Making leverage of Warrior1988 post [Root Magisk Pie Update For Unlocked Devices] all credits to him. Download the image from his post
• Boot in fastboot mode To boot into fastboot, press and hold the Power button + Volume Down Keys for few seconds; Copy the image on the same folder as your ADB and Run the following commands:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot​
Install Magisk Download the apk and install it as usual on your RP2, that should be all.
DONE!!!! You now have a unleashed the beast! Please send me any recommendations to improved this guide.

chpimentelpr said:
Install Android Drivers and ADB
Click to expand...
Click to collapse
Your link has everything necessary for this step, right? Direct link to version 1.4.3 is here: https://androidfilehost.com/?fid=746010030569952951
Or are drivers and ADB two separate downloads?
chpimentelpr said:
• To enable OEM unlock, go to Settings > Developer options and check Enable OEM unlock
Click to expand...
Click to collapse
I assume this is where we plug our phone into our computer?
chpimentelpr said:
• Using ADB commands reboot on bootloader
Click to expand...
Click to collapse
For anyone dumb and new like me, I think this is with cmd.exe in Windows. Win+S -> type "cmd" (without quotation marks) and hit enter. Once open, you want to navigate to ADB, which you've already installed via the above instructions.
So your cmd will say:
C:\Users\YourName>
And you want to get to ADB, so you'll type "cd" (without quotation marks) which means you want to change directories, and then "cd adb" (if its in C:\ directory) or "cd [whatever the path is to the ADB folder]\adb"
Assuming it was directly in C:, you should see something like:
C:\adb>
Now you want to type "adb devices" to make sure it sees your phone is plugged in. You should see: "list of devices attached - [model] device" or something.
Now you're ready to go with the instructions starting at "adb reboot bootloader." If I'm wrong about this, someone less new and dumb than I am please correct me.
chpimentelpr said:
• Copy the image on the same folder as your ADB and Run the following commands:
fastboot flash*boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
Click to expand...
Click to collapse
I'm confused on this one. The first one has "flash*boot_a," but the second one has "flash boot_b" without the * symbol. What does the * do, and what happens if we mess it up? Sorry if that's a dumb question.

AbsoluteContingency said:
Your link has everything necessary for this step, right? Direct link to version 1.4.3 is here: https://androidfilehost.com/?fid=746010030569952951
Or are drivers and ADB two separate downloads?
I assume this is where we plug our phone into our computer?
For anyone dumb and new like me, I think this is with cmd.exe in Windows. Win+S -> type "cmd" (without quotation marks) and hit enter. Once open, you want to navigate to ADB, which you've already installed via the above instructions.
So your cmd will say:
C:\Users\YourName>
And you want to get to ADB, so you'll type "cd" (without quotation marks) which means you want to change directories, and then "cd adb" (if its in C:\ directory) or "cd [whatever the path is to the ADB folder]\adb"
Assuming it was directly in C:, you should see something like:
C:\adb>
Now you want to type "adb devices" to make sure it sees your phone is plugged in. You should see: "list of devices attached - [model] device" or something.
Now you're ready to go with the instructions starting at "adb reboot bootloader." If I'm wrong about this, someone less new and dumb than I am please correct me.
I'm confused on this one. The first one has "flash*boot_a," but the second one has "flash boot_b" without the * symbol. What does the * do, and what happens if we mess it up? Sorry if that's a dumb question.
Click to expand...
Click to collapse
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot

Warrior1988 said:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
Click to expand...
Click to collapse
No asterisk. Cool. Got it. Thank you, dude.

The drivers are the regular ones for android nothing specific, they can be downloaded from their SDK https://developer.android.com/studio/run/win-usb

App root detection?
If I root my Razer phone 2 using this guide, will certain apps like banking apps, and rideshare apps be able to detect root?

Bounty33 said:
If I root my Razer phone 2 using this guide, will certain apps like banking apps, and rideshare apps be able to detect root?
Click to expand...
Click to collapse
You can use magisk to hide the root from those apps. In general banking app are not affected by root. Google pay could be affected, but I don't use it so can't be sure. And you can always unroot.

AbsoluteContingency said:
No asterisk. Cool. Got it. Thank you, dude.
Click to expand...
Click to collapse
Did you rooted? Anything missing on the guide? I want make it as useful as possible so feedback is welcome.

chpimentelpr said:
Did you rooted? Anything missing on the guide? I want make it as useful as possible so feedback is welcome.
Click to expand...
Click to collapse
I have not, but I've been really sick and useless. I think I'll try tonight and let you know how it goes. Thanks for the guide, dude.
---------- Post added at 02:50 PM ---------- Previous post was at 02:45 PM ----------
Wait, yes, I do have a question. I download the drivers, and I download the Fastboot ADB thing. What do I do with the drivers? Do they just install in Windows like anything else, and that allows me to connect to the phone?

AbsoluteContingency said:
I have not, but I've been really sick and useless. I think I'll try tonight and let you know how it goes. Thanks for the guide, dude.
---------- Post added at 02:50 PM ---------- Previous post was at 02:45 PM ----------
Wait, yes, I do have a question. I download the drivers, and I download the Fastboot ADB thing. What do I do with the drivers? Do they just install in Windows like anything else, and that allows me to connect to the phone?
Click to expand...
Click to collapse
Yes, install them as any other driver.

After rooting can you relock the boot loader or will that brick the phone?

ndragon798 said:
After rooting can you relock the boot loader or will that brick the phone?
Click to expand...
Click to collapse
Not sure, but why you want to relock the boot.

chpimentelpr said:
Not sure, but why you want to relock the boot.
Click to expand...
Click to collapse
Mostly to get rid of the startup message

Very nice. I've rooted a ton of phones over the years, but they had more established communities and had well-explained (and tested) methods of rooting. The previous guide posted (that you referenced) was fine enough, but it was very much lacking a couple prerequisites that I was wondering/concerned about. This guide has cleared all of that up for me, and I now feel confident about rooting this phone.
Just as soon as I charge up the phone and install the OTA I've been avoiding until now... lol. Hoping somebody will make a Magisk module to move the clock back to where it belongs (if they haven't already).
EDIT: Just wanted to add my success story to this. Only thing I had to do that wasn't listed in the instructions (but makes sense) is that fastboot didn't work until I enabled USB Debugging (again, after the wipe and reboot), and I had to very manually tell the computer which driver to use (ADB) after that. Didn't have that issue for the bootloader instructions beforehand (that time, the driver worked automatically), so I figured I'd mention it.

chpimentelpr said:
Not sure, but why you want to relock the boot.
Click to expand...
Click to collapse
Also is there a way to turn back on the preboot authentication. Pretty much I just want to maintain full encryption and the built in security while having root.

ndragon798 said:
Also is there a way to turn back on the preboot authentication. Pretty much I just want to maintain full encryption and the built in security while having root.
Click to expand...
Click to collapse
I don't believe encryption is supported at the moment, and I don't encourage you to try it until TWRP is fully supported since you may end up in a boot loop. I'm eagerly waiting for the full encryption capability, so I will let you know as soon as something come up.

This has to be......one of the most usefull and noob friendly guides i have ever seen.....
You sir....are a God
Thank You.

ChronosTrigger said:
This has to be......one of the most usefull and noob friendly guides i have ever seen.....
You sir....are a God
Thank You.
Click to expand...
Click to collapse
i'm glad it helps.

Alright so after fighting with windows for a few hours, I discovered that my ADB was severely outdated.... Lesson learned there.
After getting the new boot image installed, though, I hit another problem... WiFi refuses to work. The toggle switch in the statusbar, nor the toggle in the system settings, will bring my wifi to life. Which is weird! Because I got through setup just fine, connected to wifi and signed into google... Yet now all wifi functionality has vanished. I tried a factory reset, to no avail. I'm gonna have to restore the factory boot image and start all over... But for now, figured I'd ask if anyone else has run into this weird bug?
***update***
I've now gone and flashed the global image for 8.1.0 to the phone... and it's telling me the OS is up to date???? How do I get back to pie?? It's late here and I've got wifi back now... but I'm stumped. Any help would be so greatly appreciated!

xttweaponttx said:
Alright so after fighting with windows for a few hours, I discovered that my ADB was severely outdated.... Lesson learned there.
After getting the new boot image installed, though, I hit another problem... WiFi refuses to work. The toggle switch in the statusbar, nor the toggle in the system settings, will bring my wifi to life. Which is weird! Because I got through setup just fine, connected to wifi and signed into google... Yet now all wifi functionality has vanished. I tried a factory reset, to no avail. I'm gonna have to restore the factory boot image and start all over... But for now, figured I'd ask if anyone else has run into this weird bug?
***update***
I've now gone and flashed the global image for 8.1.0 to the phone... and it's telling me the OS is up to date???? How do I get back to pie?? It's late here and I've got wifi back now... but I'm stumped. Any help would be so greatly appreciated!
Click to expand...
Click to collapse
I doubt the issue with the wifi is related with the image, since it doesn't have anything to do with it. If your phone doesn't detect the update you will need to sideload it. Then try the root guide again. Let us know how it goes, it the first time I hear something wrong with WIFI after rooting.