Related
Sorry got another question is there another all in one tool that will unlock bootloader and work on software versions that are not EURxxx because im worried that ill brick my phone imputing commands manually
afrolong said:
Sorry got another question is there another all in one tool that will unlock bootloader and work on software versions that are not EURxxx because im worried that ill brick my phone imputing commands manually
Click to expand...
Click to collapse
When @Omario-242 helped you before you didn't press the 'Thanks' button - which is common courtesy when someone helps you.
You really need to learn to search and read before asking basic questions as anything you ask is likely to have been asked at least 10 times before.
I'll start by putting your mind at rest on one thing - you cannot brick this phone. So, if you don't read properly and understand what you are doing, the worst you will have to do is flash a .kdz file to recover (as a hint, look this stuff up so you know what to do if you do screw-up).
Disclaimer: I try my best to produce valid answers, but if you have no idea what you're doing, don't do it.
Terms and Definitions
NVflash / APX mode
This is the lowest level of software that can talk to an Nvidia Tegra device. Basically this is the Holy Grail of memory modification, which can even fix a damaged bootloader.
To use it, one boots the tablet with [Vol +] + [Power]. This will lead to the PC detecting an "APX" device. The screen stays blank.
This is no working solution for anything yet, as not only there is no leaked NVflash binary yet, but also the communication is encrypted via an unique 128bit AES key. This key is at no stage accessible, but can be used to encrypt data during boot. This is where the wheelie tool for previous transformers was of help. The Communication itself happens via a protocol called nv3p, which actually is open source, but as long as the key is unreachable, that's not a lot of use. NOTE: I will create an extra post with a lot more details about this.
Fastboot
The Android Bootloader.
This is the essential part of software which loads Android/a Recovery image/rooting ramfs/etc.
This is the most delicate part in the Android boot process, as fastboot is the lowest level of communication we have so far. In other words: The only way to fix a damaged bootloader would be NVflash, which is not yet available for this device.
Generally the Bootloader is locked as a method to prevent unauthorized access to data stored on the device. A locked Bootloader means no Fastboot.
Bootloader unlocking
To gain access to fastboot devices, the Bootloader needs to be unlocked. This can be as simple as installing an APK provided by the manufacturer or running "fastboot unlock".
Unlocking the Bootloader always leads to three resulting actions: Fastboot now works, all data on the device is wiped, the device's warranty is now void.
Unlocking the bootloader via unlock app can require you to have internet access and a valid google account. This can be problematic in the case of one-time-passwords, as the normal password will possibly not work (and you'll wonder why the heck it doesn't run).
Bootloader locking
This is (at least currently) not possible. Warranty void remains permanent.
RamFS
Simple file system in a file, which gets loaded into RAM. We use this for rooting.
Boot image
A file generally called "boot.img". This contains the kernel.
Recovery image
A partition image that contains a bootable linux kernel and file system, which server the purpose of creating and restoring nandroid backups and perform related tasks.
Brick - general
A device with messed up software, not being able to boot let alone perform any higher task other than being a brick.
Soft brick
A device not booting, which still responds to fastboot queries.
Hard brick / Brick
Fastboot doesn't work anymore. Maybe a visible boot loop, maybe nothing. The only point in which this differs from scrap is the ability to get into APX mode.
Chances are, there will be a way to use NVflash to fix this sometime.
Unbrick
Fixing a bricked device. Currently only soft bricked devices can be unbricked.
Root
General term for having super user abilities on a linux powered device. This can be used for reading/writing/executing restricted files, modifying things, loading custom ROMs etc.
Also having Root can mean "running with scissors", as there's not much left to prevent you from deleting important files and bricking your device.
Remember: Having Root is a very useful device, but with power comes responsibility. Also there is Android malware, which specifically targets rooted devices.
Rooting
The process of gaining Root. In early methods this generally starts with unlocking the device's Bootloader, then booting a Kernel with a purposely prepared ramfs to install and modify certain files.
As always, unlocking the Bootloader means all data will be wiped. By chance at some point someone will figure out a way to do this without unlocking.
ROM
A stock or custom Android ROM image. This contains everything needed for a running system. Custom ROMs contain tweaks, themes, improvements, styles, preloaded apps etc. Also more often than not, a load of bloat ware will be removed.
Bloat ware
Apps nobody needs/many fail to understand what they actually do/bring new ways to crash your device/sniff your precious data/revive long fixed and forgotten security leaks/the manufacturer adds to promote sales ("hey look, we've got an app for that pre installed").
Most importantly, cannot be removed from your device without Root.
Stock
A mint Android ROM, just like what the device gets shipped with.
Guides
Rooting
Requirements: Currently none
Compatible versions: anything > 10.14.1.47
Method: Booting custom Kernel and ramfs
Status: Proven
Link: http://forum.xda-developers.com/showthread.php?t=2516215
Recovery
Creator: Drgravy
Version: 6.0.3.7
Status: Abandoned but functional
Requirements: Bootloader <= 10.14.1.47 (this will not work with 10.26.1.7. Trying to do so will not work, but still boot Android as usual.)
Link: http://forum.xda-developers.com/showthread.php?t=2524401
Recovery
Creator: lpdunwell
Version: 6.0.4.5
Status: Experimental, WIP
Requirements: Bootloader >= 10.26.1.7
Link: http://forum.xda-developers.com/showthread.php?t=2556944
Various information
Hardware assembly date
On the box, rear side label.
Partition information / Unbricking
Link: http://forum.xda-developers.com/showthread.php?t=2546941
Keyboard key remapping
The physical keyboard has custom keys, with functions of debatable value. Here's how to remap them to suit your needs.
Note: This also works for other ASUS Transformers.
Warning: Backup any file you attempt to edit!
Method: The keyboard mapping is described in /system/usr/keylayout/asuspec.kl. The structure is pretty straight forward.
After saving the file, reboot the device.
Code:
Key: Function: Key number: Text:
lock Delete 142 "key 142 FORWARD_DEL WAKE UNLOCK"
search ALT 217 "key 217 ALT_LEFT WAKE UNLOCK"
HDMI configuration
The HDMI resolution can be adjusted. This can be handy under certain circumstances, although results may vary.
Method: Via terminal; disable frame buffer 1, change resolution, enable frame buffer 1
Info: To get a list of valid settings, run "cat /sys/class/graphics/fb0/modes".
This will reset at reboot.
This example enforces 1920x1200 @ 59Hz, in my case to force a HP Compaq monitor to keep running (without this it'll go to sleep for whatever reason).
Code:
echo 0 > /sys/class/graphics/fb1/device/enable
echo "D:1920x1200p-59" > /sys/class/graphics/fb1/mode
echo 1 > /sys/class/graphics/fb1/device/enable
Teardown
Teardown with two images and a brief description of the process: http://forum.xda-developers.com/showthread.php?t=2564143
Q&A
Q: "I have never rooted anything before. Can you send me some fairy dust to fix my bricked tablet if anything goes wrong?"
A: No. And if you are not absolutely sure of what you're doing, there's a fair chance you'll mess it up. Been there, done that.
Q: "What are known causes of bricked TF701?"
A:
Failed upgrade
Flashing incompatible boot.img and blob
Flashing something other than blob to staging
Removal of important files after rooting
Q: "I had a quick look at your instructions for xxx and I don't understand..."
A: Tough luck.
Q: "I re-read your instructions for xxx, searched the forum and I still cannot understand..."
A: Check if there's a matching thread. If there isn't create one with a diagnostically conclusive title. Use as much detail as possible.
Final notes
I hope this helps. As always, updates will follow.
Want to see your tutorial/guide/etc. here? Send me a detailed PM with the subject "TF701 Q&A extension".
You can help making this even better!
Found a mistake or believe I'm wrong about something? Let's discuss it.
Has this helped you? Consider clicking thanks.
THANK YOU for the hack to get a forward delete on the keyboard! That has been bugging me for a year!
Works just the same on the TF700 keyboard, btw.
Ask the mod to make it sticky, then it will always be at the top of the main thread.
Sent from my superfast Asus Infinity TF701with Dock
Snah001 said:
Ask the mod to make it sticky, then it will always be at the top of the main thread.
Sent from my superfast Asus Infinity TF701with Dock
Click to expand...
Click to collapse
he is retired .... Doesnt reply to any request ...
berndblb said:
THANK YOU for the hack to get a forward delete on the keyboard! That has been bugging me for a year!
Works just the same on the TF700 keyboard, btw.
Click to expand...
Click to collapse
yeah, the keymapping crap...
I found tons of "unpack this apk, edit soandso..." but I wanted to have it changed on a lower level. the remapping should work on most if not all transformers, and be easily portable to anything that has a hardware keyboard...
Rikodu said:
he is retired .... Doesnt reply to any request ...
Click to expand...
Click to collapse
Huh? Wut?????
Considering this is the first "Q & A" post, I will sticky it.
Provided the OP updates and maintains it.
MD
I'm pretty sure the resolution hack can be improved, but it's all I needed for now...
anybody write an app for that?
Moscow Desire said:
Huh? Wut?????
Considering this is the first "Q & A" post, I will sticky it.
Provided the OP updates and maintains it.
MD
Click to expand...
Click to collapse
go for it, it's sinking...
cheers
lpdunwell said:
go for it, it's sinking...
cheers
Click to expand...
Click to collapse
Seeing if you were paying attention..... :good:
lol
Maybe you could explain where to see the build date.
As far as I know its in the serial number after the characters. But in my case (and maybe others) I can´t see a date in 160074 .
done
hard bricked tf701t
Dear lpdunwell,
I have a bricked tf701, only asus logo available and loopboot, fastboot menu is broken as well. Only APX mode working, but I could not find appropriate nvflash for my pad (s I see there is no nvflash currently available for my tab)
In your explanation about bricked device, you wrote that there is possibility to recover tf701?
Please describe what nvflash version should I use to succeed?
Thanks in advance,
stream1313
stream1313 said:
Dear lpdunwell,
I have a bricked tf701, only asus logo available and loopboot, fastboot menu is broken as well. Only APX mode working, but I could not find appropriate nvflash for my pad (s I see there is no nvflash currently available for my tab)
In your explanation about bricked device, you wrote that there is possibility to recover tf701?
Please describe what nvflash version should I use to succeed?
Thanks in advance,
stream1313
Click to expand...
Click to collapse
Sorry mate we don't have nvflash and it is too late for you now anyway If you only have access to APX you are hard bricked. Best to sell it for parts and move on.... Or if you want to revive it send it to Asus to fix at a cost or source a replacement mainboard and do it yourself.
sbdags said:
Sorry mate we don't have nvflash and it is too late for you now anyway If you only have access to APX you are hard bricked. Best to sell it for parts and move on.... Or if you want to revive it send it to Asus to fix at a cost or source a replacement mainboard and do it yourself.
Click to expand...
Click to collapse
Hi man.. Why do you think I have to forget about my toy.. It was my Christmas (New Year in Tbilisi, Georgia, opposite planet side) present to myself But it is all the lyric only
Pls explain - do you really think that for ex., several weeks / months later, smb will create the nvflash or any similar SW which will be able to fix my problem? Actually I believe that until all electronic components are ok, device is not "dead" forever... Why you so pessimistic exactly for 701 transformer tab? Pls if you have time reply me
Kind regards,
Stan
stream1313 said:
Hi man.. Why do you think I have to forget about my toy.. It was my Christmas (New Year in Tbilisi, Georgia, opposite planet side) present to myself But it is all the lyric only
Pls explain - do you really think that for ex., several weeks / months later, smb will create the nvflash or any similar SW which will be able to fix my problem? Actually I believe that until all electronic components are ok, device is not "dead" forever... Why you so pessimistic exactly for 701 transformer tab? Pls if you have time reply me
Kind regards,
Stan
Click to expand...
Click to collapse
the way nv flash works is you need to flash the special bootloader to extract your device blobs and device specific keys. As you haven't been able to do it and you CANNOT do it once you have bricked you will have no chance. How are you going to flash a bootloader that you need fastboot for?
Sorry to bring bad news but if you only have APX with no saved nv flash files (which is not yet avail for our device) then you currently have 0% chance of recovering.
sbdags said:
the way nv flash works is you need to flash the special bootloader to extract your device blobs and device specific keys. As you haven't been able to do it and you CANNOT do it once you have bricked you will have no chance. How are you going to flash a bootloader that you need fastboot for?
Sorry to bring bad news but if you only have APX with no saved nv flash files (which is not yet avail for or device) then you currently have 0% chance of recovering.
Click to expand...
Click to collapse
Thanks a lot for reply (as well as for my another, initial thread reply) I have only CWM backup of my tab, on the MD card. But I do not know, does this backup contain all needed stuff? At list, I did not found there saved nv flash or blob files. Just "blobgenerator" (462Kb) and "blobtester" (370Kb), also some system files with "nv" in the name. But I do not have Idea, does CWM saving the low level loader files, at list I was not able to recognize them there...
my apologize for too many questions as well as for my poor English - it is not my native lang
Kind regards,
Stan
stream1313 said:
Thanks a lot for reply (as well as for my another, initial thread reply) I have only CWM backup of my tab, on the MD card. But I do not know, does this backup contain all needed stuff? At list, I did not found there saved nv flash or blob files. Just "blobgenerator" (462Kb) and "blobtester" (370Kb), also some system files with "nv" in the name. But I do not have Idea, does CWM saving the low level loader files, at list I was not able to recognize them there...
my apologize for too many questions as well as for my poor English - it is not my native lang
Kind regards,
Stan
Click to expand...
Click to collapse
No having CWM backups saved won't help you as you have no way of getting to the bootloader which would then be used to open the recovery so you could restore. WIthout a working bootloader you can't proceed. NV Flash uses APX mode to restore the blobs via the wheelie binary. You haven't captured the blobs to restore and as they are encrypted to your device you can't use anyone elses.
It's a new main board or nothing I'm afraid.
sbdags said:
No having CWM backups saved won't help you as you have no way of getting to the bootloader which would then be used to open the recovery so you could restore. WIthout a working bootloader you can't proceed. NV Flash uses APX mode to restore the blobs via the wheelie binary. You haven't captured the blobs to restore and as they are encrypted to your device you can't use anyone elses.
It's a new main board or nothing I'm afraid.
Click to expand...
Click to collapse
I see, everything is clear. Thanks for your time man. But I beleive that Asus has some kind of "backdoor" for such cases, for internal usage, of course. Asus manifest about "mainboard replacement" probably just for business, normally must be some way to crack this protection. I hope somebody from Asus will share some useful info or even software for public usage... Maybe it's my dreams only, I'm realistic (I'm working as IT/IS/GSM/WCDMA, but I'm so far from programming..)
Again, thank you. Pls notify me in case of any news about K00C hack
Problems flashing CWM recovery
stream1313 said:
I see, everything is clear. Thanks for your time man. But I beleive that Asus has some kind of "backdoor" for such cases, for internal usage, of course. Asus manifest about "mainboard replacement" probably just for business, normally must be some way to crack this protection. I hope somebody from Asus will share some useful info or even software for public usage... Maybe it's my dreams only, I'm realistic (I'm working as IT/IS/GSM/WCDMA, but I'm so far from programming..)
Again, thank you. Pls notify me in case of any news about K00C hack
Click to expand...
Click to collapse
----------------------------------------------------------------------------------------
Sorry I am not yet familiar with how to ask questions.
I recently bought a TF701T having used a TF700T now for two years and before that the TF101, TF201 and TF300T.
All these tabs I installed a recovery: CWM or TWRP and flashed the best ROM I could find. Usually Cyanomod or CROMi-X.
Everything worked fine so I was very excited when I got hold of the TF701T with its incredible Q-ratings and smoothness.
Unlocking worked just fine but installing CWM just does not work: flashing with Fastboot works OK but when I boot into recovery the little green man falls down and stays there
FYI: I am on the latest BL: 10.26.1.28, so newer than the mentioned 10.26.1.18 !
Please could anyone respond ?
Regards, JOTX10 from the Netherlands.
Ok, Ladies and Gentleman I need some deep thought processing here for some help with a Motorola Nexus 6. In brief here is what the problem is, a while back when flashing Pure Nexus rom, I experienced a loss of my IMEI. I can restore my IMEI but if and when I do, I lose any 4g and LTE connectivity. The phone functions in 3g with data and phone etc... just slow as molasses but if I restore my IMEI to the one that doesn't show up my IMEI correctly I get back LTE/4g and all works fine also. I've tried going all the way back to the original firmware which was saved to computer and restoring it. Same thing, I have IMEI but no LTE/4g. restore bad efs and get LTE/4g back. I've tried going through all the factory firmware's and flashing by ADB and or TWRP and nothing firmware wise will allow me to restore the IMEI and have LTE/4g signal. If I restore the bad efs and get OOOOOOOO for IMEI when using the *#06# on any firmware version, I regain LTE/4g functioning! I am using Pure Nexus 7.1 now and can still see the 00000000 as a IMEI, if I restore my efs and get IMEI back showing correctly, no LTE/4g signal! My phone can only function as it should as long as the IMEI doesn't show correctly! I have tried just flashing base bands and other segments of any rom and still the problem persist! I have even tried restoring an EFS from another nexus 6 and still no help. It's not the sims because I've tried AT&T sims and Verizon sims from other phones and it does the same thing! I've tried flashing with a sims in the phone and without. Any ideas??? It's like somehow a correlating segment of a file is not being recognized when the correct IMEI is present, like some thing some where in the efs, IMEI, and radio are not taking to each other so to speak, unless it shows the zero's! Brain waves come on and help me out here!!
Have you tried doing a fresh install of a complete factory nexus image? (i.e. entirely wiping the device)
jbaumert said:
Have you tried doing a fresh install of a complete factory nexus image? (i.e. entirely wiping the device)
Click to expand...
Click to collapse
Thanks, and Yes, about 30 different times, using Google developer site original factory firmware, using ADB and or TWRP all the way back to original image, which I have saved as I said in the original post! I don't have a problem restoring IMEI it's just if I do, the phone will not connect to LTE/4g no way no how. I have to have a "0" IMEI for the phone to function as it should actually function and the LTE/4g radio to work, something strange is a miss!
TheWacoKid said:
Thanks, and Yes, about 30 different times, using Google developer site original factory firmware, using ADB and or TWRP all the way back to original image, which I have saved as I said in the original post! I don't have a problem restoring IMEI it's just if I do, the phone will not connect to LTE/4g no way no how. I have to have a "0" IMEI for the phone to function as it should actually function and the LTE/4g radio to work, something strange is a miss!
Click to expand...
Click to collapse
Alrighty, no need to yell.... The factory image is flashed with "fastboot" NOT adb or TWRP. Just wanted to clarify how you were returning the phone to stock.
jbaumert said:
Alrighty, no need to yell.... The factory image is flashed with "fastboot" NOT adb or TWRP. Just wanted to clarify how you were returning the phone to stock.
Click to expand...
Click to collapse
Yes I said thanks because I was yelling! Jezz, get a grip THIS IS YELLING! ADB/Fastboot both tools are used to flash, extract etc.. with your computer, so obviously one cannot flash/restore etc... without using the proper tools via computer!
Try this:
1) Install "Change APN" app from Google store
2) Open ChangeAPN and click the "option" ( the 3 vertical dots) in the upper right-hand corners.
3) click "reset to default"
4) exit the app
5) perform carrier reset ##3282#
6)If needed: after the phone reboots, perform PRL/Device config update. That's it and you should have LTE data.
Dixon Butz said:
Try this:
1) Install "Change APN" app from Google store
2) Open ChangeAPN and click the "option" ( the 3 vertical dots) in the upper right-hand corners.
3) click "reset to default"
4) exit the app
5) perform carrier reset ##3282#
6)If needed: after the phone reboots, perform PRL/Device config update. That's it and you should have LTE data.
Click to expand...
Click to collapse
Thanks! Ok, Itried that, restored my IMEI, "reset APN to default" Tried Carrier reset ##3282# and it says "NO Cellular Network" even though I am showing my network and 3G. So, I rebooted and same thing, went to PRL and tried to update and it says "update error" but it will refresh!
TheWacoKid said:
Yes I said thanks because I was yelling! Jezz, get a grip THIS IS YELLING! ADB/Fastboot both tools are used to flash, extract etc.. with your computer, so obviously one cannot flash/restore etc... without using the proper tools via computer!
Click to expand...
Click to collapse
You clearly don't know the difference between a recovery, the bootloader and the operating system.
ADB is used when the phone is on and is not how you flash a factory image. Fastboot is used in the bootloader and is the proper method of restoring to factory.
admiralspeedy said:
You clearly don't know the difference between a recovery, the bootloader and the operating system.
ADB is used when the phone is on and is not how you flash a factory image. Fastboot is used in the bootloader and is the proper method of restoring to factory.
Click to expand...
Click to collapse
No, I guess not, that's how I've been flashing, restoring and unbricking cells for years, I just don't understand anything!
TheWacoKid said:
No, I guess not, that's how I've been flashing, restoring and unbricking cells for years, I just don't understand anything!
Click to expand...
Click to collapse
You know some magic we don't? There is no way you've flashed a ROM with ADB...
@admiralspeedy
I was very gratified when I noticed that I'd overnight become a Senior Member - until I realised that it had nothing to do with the wisdom I'd imparted in my posts, but only that I'd posted 100. So seniority doesn't imply knowledge, which I think you're beginning to demonstrate in this thread as well as in another where I've seen this same strange unnecessarily belligerent attitude.
TheWacoKid is asking for help, which I'd be happy to offer if I had any ideas. I feel absolutely no desire to tell him that he has no idea what he's doing. And nor should you.
Stop trolling and become a properly-active member of the community.
dahawthorne said:
@admiralspeedy
I was very gratified when I noticed that I'd overnight become a Senior Member - until I realised that it had nothing to do with the wisdom I'd imparted in my posts, but only that I'd posted 100. So seniority doesn't imply knowledge, which I think you're beginning to demonstrate in this thread as well as in another where I've seen this same strange unnecessarily belligerent attitude.
TheWacoKid is asking for help, which I'd be happy to offer if I had any ideas. I feel absolutely no desire to tell him that he has no idea what he's doing. And nor should you.
Stop trolling and become a properly-active member of the community.
Click to expand...
Click to collapse
Actually, I wouldn't have jumped on him like that if he hadn't come out swinging with snarky comments when people tried to help him.
admiralspeedy said:
You know some magic we don't? There is no way you've flashed a ROM with ADB...
Click to expand...
Click to collapse
Look, I came on here to discuss a situation and or problem, which is what I thought this web site was known for, which I havent run into before, in that way not only do I get some help and or suggestions which might help me but help others at the same time who might have the same problem and or will have in the future and find possible solutions! If you don't have anything positive to add to the conversation/situation/problem at hand you are wasting my time, others time and most of all just making a fool out of yourself being childish and immature. Most on here come for solutions not looking to nitpick and try and belittle others like they know everything, which you don't, otherwise you would have given a solution! So you can continue to act like a troll or just leave the situation be and by the way, you ever hear of ADB Sideload??
Use method 2 , you will get everything definitely
https://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
TheWacoKid said:
Look, I came on here to discuss a situation and or problem, which is what I thought this web site was known for, which I havent run into before, in that way not only do I get some help and or suggestions which might help me but help others at the same time who might have the same problem and or will have in the future and find possible solutions! If you don't have anything positive to add to the conversation/situation/problem at hand you are wasting my time, others time and most of all just making a fool out of yourself being childish and immature. Most on here come for solutions not looking to nitpick and try and belittle others like they know everything, which you don't, otherwise you would have given a solution! So you can continue to act like a troll or just leave the situation be and by the way, you ever hear of ADB Sideload??
Click to expand...
Click to collapse
I'm "belittling" you because your first two replies to someone who tried to help you were snarky and rude. In your own words, get a grip.
admiralspeedy said:
Actually, I wouldn't have jumped on him like that if he hadn't come out swinging with snarky comments when people tried to help him.
Click to expand...
Click to collapse
Time for you to go back and read some more...
You can flash a ROM with adb... Now unless you can help him... Shaddyup
rignfool said:
Time for you to go back and read some more...
You can flash a ROM with adb... Now unless you can help him... Shaddyup
Click to expand...
Click to collapse
No, you can use ADB sideload to flash a ROM which requires you to be in the recovery. Standard ADB cannot be used to flash a ROM.
admiralspeedy said:
I'm "belittling" you because your first two replies to someone who tried to help you were snarky and rude. In your own words, get a grip.
Click to expand...
Click to collapse
Amazing to any one with half a brain how you a Troll can think from typed response that someone is yelling, swinging, snarky and rude but your the one with an attitude that is all the above because like I said your a childish troll! I can't believe this site would even allow someone like you to be a member paid or otherwise! Your attitude is all your own and based on your own weak assumptions! Now go back to playing with your legos!
drmuruga said:
Use method 2 , you will get everything definitely
https://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Click to expand...
Click to collapse
Thanks, I've used both of those methods, I have even tried just flashing individual parts all by themselves to see if just one part would give an error of some kind while flashing, no errors on any flash of any kind, the only difference being that if I read them correctly that on those methods it said to wipe data factory reset in recovery, before reboot, the Flashall bat file reboots automatically into image just flashed, I usually reboot as last command, if that makes any difference, I've even tried wiping then just flashing the new bootloader after a wipe, because it basically acts like a security checkpoint and partition manager, then rebooting and flashing the rest of one of the google firmware versions for the nexus 6.
TheWacoKid said:
Thanks, I've used both of those methods, I have even tried just flashing individual parts all by themselves to see if just one part would give an error of some kind while flashing, no errors on any flash of any kind, the only difference being that if I read them correctly that on those methods it said to wipe data factory reset in recovery, before reboot, the Flashall bat file reboots automatically into image just flashed, I usually reboot as last command, if that makes any difference, I've even tried wiping then just flashing the new bootloader after a wipe, because it basically acts like a security checkpoint and partition manager, then rebooting and flashing the rest of one of the google firmware versions for the nexus 6.
Click to expand...
Click to collapse
So was there a solution? The thread just ended. I also have this problem but I'm no where as technical as thewacokid.
But I do know how to follow steps
Additional facts - I don't know how to root a phone, therefore this is all factory settings, purchased phone new via Amazon, on t-mobile network... pretty downtrodden about my current situation... really would appreciate any guidance.
Llebowski
If you have access to a laptop or PC, download Wug Fresh's Nexus Root Toolkit. After installing go through the steps to setup your version of operating system. Go to restore from boot loop and follow the instructions.
@Rondeau79: Except he isn't in a bootloop, thus the toolkit won't do him any good.
@Llebowski: The solution to your erase problem is to do nothing. The Nexus 6 internal storage is encrypted by default, and erasing an encrypted volume takes a lot of time, especially if it has a lot of data in it. Three hours isn't uncommon. If it still is trying to erase as of the time I write this, then we'll have to dig deeper, but for now, be patient.
Strephon Alkhalikoi said:
@Rondeau79: Except he isn't in a bootloop, thus the toolkit won't do him any good.
@Llebowski: The solution to your erase problem is to do nothing. The Nexus 6 internal storage is encrypted by default, and erasing an encrypted volume takes a lot of time, especially if it has a lot of data in it. Three hours isn't uncommon. If it still is trying to erase as of the time I write this, then we'll have to dig deeper, but for now, be patient.
Click to expand...
Click to collapse
As long as a computer recognizes the device and fastboot works, he can get himself out of that mess.
@Rondeau79: Your previous comment assumed the OP's device was in a bootloop. It's not, and therefore the instructions you gave him were incorrect and would not have fixed the problem. The OP should not be using a toolkit in any event, but should learn how to use ADB and Fastboot by themselves.
Your current comment also will not help, because by the time the OP's device has notified the OP of the erasure occurring, it's too late for fastboot commands to do anything. In fact, once the erase has begun, it must complete or else the internal storage may become corrupted.
The only effective solution to the OP's problem is to do nothing and let the erasure finish.
Strephon Alkhalikoi said:
@Rondeau79: Your previous comment assumed the OP's device was in a bootloop. It's not, and therefore the instructions you gave him were incorrect and would not have fixed the problem. The OP should not be using a toolkit in any event, but should learn how to use ADB and Fastboot by themselves.
Your current comment also will not help, because by the time the OP's device has notified the OP of the erasure occurring, it's too late for fastboot commands to do anything. In fact, once the erase has begun, it must complete or else the internal storage may become corrupted.
The only effective solution to the OP's problem is to do nothing and let the erasure finish.
Click to expand...
Click to collapse
There are many different ways to skin a cat! Meaning there a multiple ways to fix a problem. One way might not be the same as another, but the ends will justify the means. This guy is looking for help, the OP has nothing to do with the way the problem can be solved. I could easily have that phone fixed in about 15 minutes. Chill out dude!
@Rondeau79: Reading comprehension failure on your part? OP's thread title is "Nexus 6 on Erasing Screen for 3+ hours after attempted factory reset - Help please??" The additional information provided by the OP is that this phone is bone stock and not rooted. The guy is looking for help. He is trying to understand why his phone is still doing the erase step after initiating the factory reset three hours previous.
The only reason you're getting so defensive in your most recent post is because you have absolutely no clue what you're talking about, and know it. The specious claim that you could have the OP's phone fixed in fifteen minutes proves it. So, instead of telling me to chill out - something I don't need to do because I'm perfectly fine - you need to own up to your mistakes and do some research before tossing out random snippets of "help" that have nothing to do with the OP's problem.
*hands you an ID-10-T form*...fill that out, mail it in, and you'll get your card in a few weeks.
Rondeau79 said:
There are many different ways to skin a cat! Meaning there a multiple ways to fix a problem. One way might not be the same as another, but the ends will justify the means. This guy is looking for help, the OP has nothing to do with the way the problem can be solved. I could easily have that phone fixed in about 15 minutes. Chill out dude!
Click to expand...
Click to collapse
Hi sir
Please help me how to fix this
I foolishly upgraded to 9.0.5 with the OEM method instead of flashing as in times past. Sure enough it gave me some nonsense that my phone was corrupt and that a factory reset was necessary. Sadly lots of valuable pictures were on my phone and I'm scrambling to root my phone again to try DiskDigger since that appears to be the best app from searches.
Unfortunately the tutorial I used in the past doesn't seem to work or apply very well now. ADB Fastboot doesn't seem to recognize my device for some reason. Any tips would be appreciated.
According to https://forum.xda-developers.com/htc-10/how-to/thread-t3333345 requests for help should go to the help forum. Requests for help must not go to the how-to forum. You should ask the moderators to move this thread to the correct forum.
Nicky Carts said:
I foolishly upgraded to 9.0.5 with the OEM method instead of flashing as in times past. Sure enough it gave me some nonsense that my phone was corrupt and that a factory reset was necessary. Sadly lots of valuable pictures were on my phone and I'm scrambling to root my phone again to try DiskDigger since that appears to be the best app from searches.
Unfortunately the tutorial I used in the past doesn't seem to work or apply very well now. ADB Fastboot doesn't seem to recognize my device for some reason. Any tips would be appreciated.
Click to expand...
Click to collapse
First of all: your data is lost - unrevertable. Diskdigger is for restoring accidentally deleted media files. If you format and reencrypt the data partition all data is lost from the partition. The only way to restore your data is a backup of media files (not in nandroids).
What do you mean by "ADB Fastboot"? For adb you need to enable adb in dev opts, for fastboot you need to boot in fastboot mode (aka bootloader mode: hold "vol up" and "power" to power on). These two are different animals.
If the devices doesn't show up in fastboot mode, you need to debug the pc host first. A starting point for win would be the device manager and the event log. If the drivers are installed correctly, you need to walk through the physical conmection: ports, cable, dirt in the usb-c jack etc.
nvertigo67 said:
First of all: your data is lost - unrevertable. Diskdigger is for restoring accidentally deleted media files. If you format and reencrypt the data partition all data is lost from the partition. The only way to restore your data is a backup of media files (not in nandroids).
What do you mean by "ADB Fastboot"? For adb you need to enable adb in dev opts, for fastboot you need to boot in fastboot mode (aka bootloader mode: hold "vol up" and "power" to power on). These two are different animals.
If the devices doesn't show up in fastboot mode, you need to debug the pc host first. A starting point for win would be the device manager and the event log. If the drivers are installed correctly, you need to walk through the physical conmection: ports, cable, dirt in the usb-c jack etc.
Click to expand...
Click to collapse
I too struck in same state, But I've a different situation.. OEM Unlocked Successfully but cant flash twrp getting an error of DATA TRANSFER Failure , Too Many Links.. Tried diff USB Ports and Diff PC running Diff OS too..Still cant enable to flash TWRP ..Hope someone threw some light into this!
nvertigo67 said:
First of all: your data is lost - unrevertable. Diskdigger is for restoring accidentally deleted media files. If you format and reencrypt the data partition all data is lost from the partition. The only way to restore your data is a backup of media files (not in nandroids).
What do you mean by "ADB Fastboot"? For adb you need to enable adb in dev opts, for fastboot you need to boot in fastboot mode (aka bootloader mode: hold "vol up" and "power" to power on). These two are different animals.
If the devices doesn't show up in fastboot mode, you need to debug the pc host first. A starting point for win would be the device manager and the event log. If the drivers are installed correctly, you need to walk through the physical conmection: ports, cable, dirt in the usb-c jack etc.
Click to expand...
Click to collapse
Guess I'm SOL with my pics of my son. It's ok. I only have myself to blame. I started enabling backups to Google Photos. Something I was never a fan of. Thanks though. I'll still be interested in rooting my 3T with 9.0.5 since this phone still has plenty of life and takes great pics.
Nicky Carts said:
I started enabling backups to Google Photos. Something I was never a fan of.
Click to expand...
Click to collapse
I'm completely with you on g's backup service! Nowadays you get a high quality usb-c 128Gb stick for around 25 € or $, for 40 bucks a 256 Gb one (i.e. sandisk Ultra Dual USB-Stick, Typ-C (SDDDC2-016G-G46)). I strongly recommend getting one for every user of a non-sdcard device - it saves my arse more then once! nandroids, titanium backups, media, etc all go there.
Hope someone threw some light on this to give some tips to root OP 3T running 9.0.5 !
vettayyan said:
I too struck in same state, But I've a different situation.. OEM Unlocked Successfully but cant flash twrp getting an error of DATA TRANSFER Failure , Too Many Links.. Tried diff USB Ports and Diff PC running Diff OS too..Still cant enable to flash TWRP ..Hope someone threw some light into this!
Click to expand...
Click to collapse
I don't know, what you mean by "I too struck in same state". The issue with not being able to flash a custom recovery ("DATA TRANSFER Failure") is completely different from not being able to connect to the device in fastboot mode at all ("Fastboot doesn't seem to recognize my device") and loosing the content of userdata if blindly updating the fw.
Hijacking a thread with a completely different issue is considered bad manners.
vettayyan said:
Hope someone threw some light on this to give some tips to root OP 3T running 9.0.5 !
Click to expand...
Click to collapse
If you hijack a thtead with a completely different issue, the probability is high, that you don't get answered. Impatiently insisting on getting an answer in the hijacked thread doesn't increase the probability of getting an answer... Showing bad manners twice, doesn't make good manners.
nvertigo67 said:
I don't know, what you mean by "I too struck in same state". The issue with not being able to flash a custom recovery ("DATA TRANSFER Failure") is completely different from not being able to connect to the device in fastboot mode at all ("Fastboot doesn't seem to recognize my device") and loosing the content of userdata if blindly updating the fw.
Hijacking a thread with a completely different issue is considered bad manners.
If you hijack a thtead with a completely different issue, the probability is high, that you don't get answered. Impatiently insisting on getting an answer in the hijacked thread doesn't increase the probability of getting an answer... Showing bad manners twice, doesn't make good manners.
Click to expand...
Click to collapse
You're right ,friend..But the Title of discussion is " Best TUtorial to Root OP 3T ,OOS 9.0.5.And I'm too asking the same..
Or the Topic Starter might have given some different topic..
I think you might too see the title of the discussion first, it is about what ? I'm too struck in Rooting OOS 9.0.5.and I too said the same. and Thought somehow to root it by all means..
If the topic starter diverted means What I can do about that!
vettayyan said:
You're right ,friend..But the Title of discussion is " Best TUtorial to Root OP 3T ,OOS 9.0.5.And I'm too asking the same..
Or the Topic Starter might have given some different topic..
I think you might too see the title of the discussion first, it is about what ? I'm too struck in Rooting OOS 9.0.5.and I too said the same. and Thought somehow to root it by all means..
If the topic starter diverted means What I can do about that!
Click to expand...
Click to collapse
You aren't stuck with rooting - you're stuck trying to flash in fastboot. While rooting may depend on being able to flash in fastboot, you're not actually having issues with acquiring root yet.
And, as I mentioned before, don't post the same question in different threads.
Sent from my OnePlus 3T using XDA Labs