Database Develop

[HELP] Installing Custom Recovery Doesn't Work

Hello all.
Yesterday I received my G1 in the mail, and I have rooted it, and installed HardSPL. The only problem is that whenever I try to flash a custom recovery, it stays the same. I boot into Boot Loader mode, type fastboot flash recovery /path/to/recovery.img, and it says that it flashes successfully, but when I then boot into recovery mode, it is the stock with custom keys recovery. Please help.
NOTE: I am a Samsung person, so I assume I am bad with fastboot, and that is the cause of the errors. Thanks for not calling me a noob in advance!

Nevermind. I have figured it out. I used Ubuntu and all my problems were solved. Suggestion to those who have my problem, don't use Macintosh, as it doesn't flash well. Use Ubuntu Linux, or Windows.

GBGamer said:
don't use Macintosh
Click to expand...
Click to collapse
great advice

Can't help to say that as Steve said; "You must be using it wrong."

Steve wasn't always right...
Sent from my HTC Vision using xda premium

I am definitely making sure my next computer has completely open source (or at least Linux) drivers!
Tick, tock, goes the clock
Even for the Doctor

[Q] Cant browse root

My current situation.
Streak 7 boots after factory reset, asks for a password. there never was one. after numerous attempts i just decided to install another rom.
i have all the files etc and know how to flash it with clockwork, but i cant get it onto the internal sd. only the external. meaning clockwork cant detect it. im kinda stuck here....

I had this issue once, I wiped again from recovery, cache and dalvic as well and it cleared up. Also I use fastboot to install everything for roms.
Sent from a Hacked, Modded and customized Streak 7

sadly ive tried that repeatedly :L

Did you use fastboot to reinstall the system, boot, and recovery files? This or Nvflash will be your only way to get out of it then.
Sent from a Hacked, Modded and customized Streak 7

i could, if you have a solution to why it hangs at "starting fastboot usb download protocall"
and thanks for the help by the way. this has caused me too much stress lol
EDIT: And if you could help me with the fastboot commands afterwards that would be great. i know how to flash recovery and thats about it.

Its suppose to say that on your device.
Now plug it into the computer, install the fastboot drivers, grab a copy of fastboot.exe, and flash the images.

giveen said:
Its suppose to say that on your device.
Now plug it into the computer, install the fastboot drivers, grab a copy of fastboot.exe, and flash the images.
Click to expand...
Click to collapse
Giveen, I am trying to help fill in for those that have been around longer than those of us that are new. I have to agree with the new people that it is difficult to find the knowledge on this site sometimes and the list of commands that are needed to get going. I know I have spent many hours on google, XDA, TabletRoms and WIKI looking for answers. I do get that it is frustrating for you as a developer as well. Sit back and relax and some of us newer noobs will try to assist.
Sent from a Hacked, Modded and customized Streak 7
---------- Post added at 11:14 AM ---------- Previous post was at 11:09 AM ----------
Meanc20 said:
i could, if you have a solution to why it hangs at "starting fastboot usb download protocall"
and thanks for the help by the way. this has caused me too much stress lol
EDIT: And if you could help me with the fastboot commands afterwards that would be great. i know how to flash recovery and thats about it.
Click to expand...
Click to collapse
You need to do more reading here, yea I know it's hard to find info sometimes. Google every way you can think of for your problem and an answer will be found. You don't have a brick yet but you need to know what your doing before diving into this stuff. I spent a week researching before I dived into this just to make sure I knew what I was doing. YouTube video search, flashing Dell streak 7, at least I think that is close enough. It is a for part series on how to flash a custom ROM from Nvflash but you need to read and find the fastboot commands and drivers. They are here.
Sent from a Hacked, Modded and customized Streak 7

i have everything ready but fastboot commands dont work because the device is still stuck "starting the protocall"
i have the correct drivers etc installed but still nothing

Meanc20 said:
i have everything ready but fastboot commands dont work because the device is still stuck "starting the protocall"
i have the correct drivers etc installed but still nothing
Click to expand...
Click to collapse
That's what it's supposed to show till commands are sent from your PC. Do you have "still" have a yellow "?" mark in your device manager?
A quick function test is to type: fastboot reboot and your S7 should reboot.

And this is why I plan on making a fastboot video.

Bricked Nexus 6 please help ASAP!

I just bought a Nexus 6... Unlocked the bootloader and rooted the phone.... after realizing there were some issues with the phone I decided I would try and download the PURE rom for the phone... I installed TWRP recovery and tried to flash the image. When the phone booted back up it said that the data was corrupt, and to enter a password. Entering anything seemed to work and I would then reset the phone... but the same thing would come back up.
So I decided to try and wipe the phone again and re-install the ROM... after that it wouldn't load at all, came back with some kind of error.
Then I decided to do a full wipe of the phone and try and re-install the factory image... Problem is... I haven't tried to do anything with a phone in like 2 years and well... i'm having trouble on trying to figure out how I can restore the factory image. I have the SDK tools installed, the phone drivers are also obviously installed, but can someone help me try to reset to the factory image.
I only have like 3 hours to try and accomplish this from now because after this I have to get on a plane and won't be around and will also leave me without a phone... Can someone please help me as soon as possible? Thank you so much!! I could use somewhat detailed instructions but not crazy

http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008

Try nexus toolkit by wugfresh can't go wrong. If you get error missing system.img while flashing go to options then flash then click force flash. The toolkit will download all needed steps and flash without a problem

dont use a toolkit. you are guaranteed to learn nothing, and doing it the right way is just as fast(and easy). plus, root toolkits mess up often. dong it right never messes anything up.

Nexus device can almost never be bricked, I say almost never because of the people variable, but if you can get it into bootloader mode it is easy to bring back. just follow the instructions above.
I agree that even though wugfresh tools is the best out there. I have used it before. You learn nothing about what needs to be completed.
I could never get the drivers to work for me in most cases. I use ubuntu and it always works running the manual commands.

Ok so I have tried to run the flash-all.bat file and it says in the command prompt it is an unrecognized command...
I'm assuming I must be missing part of the ADB tools? Ugh help!

jwleonhart said:
Ok so I have tried to run the flash-all.bat file and it says in the command prompt it is an unrecognized command...
I'm assuming I must be missing part of the ADB tools? Ugh help!
Click to expand...
Click to collapse
first thing to do in adb is run the command "adb devices" to make sure that adb sees your device, does adb see your device?

It says list of devices attached and then nothing....
Can someone give me a short step by step on what I need to do here? I'm really running low on time, this is really bad....

jwleonhart said:
It says list of devices attached and then nothing....
Can someone give me a short step by step on what I need to do here? I'm really running low on time, this is really bad....
Click to expand...
Click to collapse
wait.. you are flashing the factory img, you do not use adb for that. you boot into the bootloader then use fastboot for that. adb doesnt work in the bootloader anyways, use fastboot while youre in the bootloader, and type fastboot devices to make sure fastboot sees your device.

@simms22 is correct, tool kits make you learn nothing, and you get posts like this.
However if you are time contained. As much as it pains me to say this. Use the tool kit. And learn on a time when you can.
Download Wugs toolskit and flash back to stock images. And you'll be fine.

Update your SDK if u haven't already.
Unzip factory images and place in platform tools folder of SDK. (Unless you have environmental variables set correctly)
Open a command prompt from that directory (place cursor in empty space, hold shift and right click on mouse)
Boot into bootloader
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot
Sent from my Nexus 6

simms22 said:
dont use a toolkit. you are guaranteed to learn nothing, and doing it the right way is just as fast(and easy). plus, root toolkits mess up often. dong it right never messes anything up.
Click to expand...
Click to collapse
Different strokes for different folks!!!!
Sent from my SM-T310 using XDA Premium 4 mobile app

doing the following command in command prompt:
fastboot devices
it shows the following device:
ZX1G2224G5
I'm assuming that is the nexus 6...
So whats next on the list then?
I unzipped the factory image and using the flash-all.bat script it says fastboot is not a recognied command.

dparrothead1 said:
Different strokes for different folks!!!!
Sent from my SM-T310 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
not really.
if you know anything about what you are doing, its one thing, use a toolkit, enjoy yourself. if you have no idea what you are doing, the root toolkit is by far the wrong way to go. as you will still know absolutely nothing, and will learn nothing. and pretty soon, when you have some simple maintenance to do, and you have no idea how, you start thread about having your device bricked. and im sure that you personally have not helped out hundreds that have started threads about having their device "bricked" after using a root toolkit. i have.
---------- Post added at 02:06 PM ---------- Previous post was at 02:05 PM ----------
jwleonhart said:
doing the following command in command prompt:
fastboot devices
it shows the following device:
ZX1G2224G5
I'm assuming that is the nexus 6...
So whats next on the list then?
I unzipped the factory image and using the flash-all.bat script it says fastboot is not a recognied command.
Click to expand...
Click to collapse
you probably have to unzip it twice, if there is another zip within that one zip. and you can try not using the word fastboot, as i also have ran into fastboot programs where it wasnt needed.

simms22 said:
not really.
if you know anything about what you are doing, its one thing, use a toolkit, enjoy yourself. if you have no idea what you are doing, the root toolkit is by far the wrong way to go. as you will still know absolutely nothing, and will learn nothing. and pretty soon, when you have some simple maintenance to do, and you have no idea how, you start thread about having your device bricked. and im sure that you personally have not helped out hundreds that have started threads about having their device "bricked" after using a root toolkit. i have.
---------- Post added at 02:06 PM ---------- Previous post was at 02:05 PM ----------
you probably have to unzip it twice, if there is another zip within that one zip. and you can try not using the word fastboot, as i also have ran into fastboot programs where it wasnt needed.
Click to expand...
Click to collapse
Friend, I'm way too old to get into an internet pissing contest!!! I realize I don't have 27,000+ post, but if you look at my thanks total, you will see that I've helped my share of members!!!! So don't tell me that I dont try to share my knowledge......have a good day and please don't respond to any more of my post!!!! Peace out!!
Sent from my SM-T310 using XDA Premium 4 mobile app

dparrothead1 said:
Friend, I'm way too old to get into an internet pissing contest!!! I realize I don't have 27,000+ post, but if you look at my thanks total, you will see that I've helped my share of members!!!! So don't tell me that I dont try to share my knowledge......have a good day and please don't respond to any more of my post!!!! Peace out!!
Sent from my SM-T310 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
with a silly post like "Different strokes for different folks!!!!" you definitely arent posting like someone your age, as thats what a child would say. im not young myself. anywho, you can not tell me not to respond, lol. ill respond to anyone who posts as silly as you. i have nothing against you, nor are trying to get at you, im simply responding to your silliness.

OP... The password was a numerical representation of your pattern unlock since you were still encrypted. The key is in the first post of the TWRP thread.
Now...extract the factory image until you have boot.img radio.img system.img and recovery.img if there is a bootloader img flash that first.
Flash bootloader with fastboot flash bootloader bootloader.img
Reboot with fastboot reboot-bootloader
Flash boot system and radio respectively with fastboot flash boot/radio/system boot.img/radio.img/system.img one at a time.
Finish with fastboot reboot and you sgould be all set.

op got it flashed, and ended up flashing his rom as well. so, he was successful

I hope saying use a toolkit didn't start an argument, only said to use it because he had a time restraint..

jiv101 said:
I hope saying use a toolkit didn't start an argument, only said to use it because he had a time restraint..
Click to expand...
Click to collapse
no, it didnt start an argument. but he ended up doing it the right way, then flashed his rom. then flashed a different rom because his rom was so so. but really, even if theres a time restraint, if your driver is installed properly, it takes about 3-4 minutes to flash the boot.img

Help with Nexus 6 possible Brick

Alright I am looking for some help here. I was attempting to unroot to update my Nexus 6 to Android M. Not sure how this happened but here it goes. I can boot the phone into recovery TWRP and into boot loader but the OEM is locked....In recovery I have no backups or ROMs o flash and my mac is not connecting with the Nexus 6. It seems like there is no ROM on the phone at all and I cant use Terminal commands I keep getting Failures. I have run the 1 click root and unroots for mac and still nothing. I also have no access to Developer options since I cant load into a ROM...So I cant select allow OEM unlock... Please let me know if there is anything I can do to fix this. Thanks for your help everyone!

Try to uninstall all drivers then re install to see if mac recognizes your phone then sideload a rom to recovery or adb

Had this before. I believe when connecting to your computer, you have to delete every nexus 6 previous connections so it would be as if your phone never connected to your computer before. Then after you do that, it should install drivers and recognize your phone. I'm not sure if I remember correctly but I believe its from your toolbar on your computer where it normally pops up "eject USB " warnings. Sorry if I couldn't help

Delete all drivers relating to Android. Download and install the Android SDK Tools from Google. Update the SDK and install the Google USB driver. Boot into TWRP, connect the N6, then use adb push rom.zip /sdcard.
I think that should work.

or fastboot wipe user data and cache.

nhizzat said:
Delete all drivers relating to Android. Download and install the Android SDK Tools from Google. Update the SDK and install the Google USB driver. Boot into TWRP, connect the N6, then use adb push rom.zip /sdcard.
I think that should work.
Click to expand...
Click to collapse
I have been working on this since last night 7pm... I tried adb push and it just sits there and says starting adb sideload for about 10 min then vibrates with a cancellation. I tried removing Android File Transfer and reinstalling it and I still get the can not find device error. Im thinking this might be a loosing battle.

simms22 said:
or fastboot wipe user data and cache.
Click to expand...
Click to collapse
I did both of these to get past the TWRP boot loop. I can get into TWRP but its empty like everything has been wiped I have no backups or ROMs to flash to. Since the OEM is locked and I cant launch into a ROM to select allow OEM unlock it seems like im going to inevitably lose this battle. Last resort I have a friend coming over with Windows (hoping) WUGfresh can solve the issues....

ibaldwin85 said:
I did both of these to get past the TWRP boot loop. I can get into TWRP but its empty like everything has been wiped I have no backups or ROMs to flash to. Since the OEM is locked and I cant launch into a ROM to select allow OEM unlock it seems like im going to inevitably lose this battle. Last resort I have a friend coming over with Windows (hoping) WUGfresh can solve the issues....
Click to expand...
Click to collapse
did you have any roms on your phone before all this? if you did, did you try to search if they are in a different location in your storage now?

Do you have access a a Windows machine? NRT has an option to reflash a bricked phone. Never bricked mine but that tool has been awesome otherwise.

snatale1 said:
Do you have access a a Windows machine? NRT has an option to reflash a bricked phone. Never bricked mine but that tool has been awesome otherwise.
Click to expand...
Click to collapse
he has no rom and bootloader locked. nrt cant do anything.

simms22 said:
he has no rom and bootloader locked. nrt cant do anything.
Click to expand...
Click to collapse
But if he has TWRP......he can transfer a ROM from the PC and flash it......

paclaco said:
But if he has TWRP......he can transfer a ROM from the PC and flash it......
Click to expand...
Click to collapse
absolutely! and he knows he can do that, but he had no access to a computer(he wrote that his friend is gonna come over with one though).

snatale1 said:
Do you have access a a Windows machine? NRT has an option to reflash a bricked phone. Never bricked mine but that tool has been awesome otherwise.
Click to expand...
Click to collapse
All due respect to the developer, but all WUg's NRT does is automate the downloading and the commands you use to flash manually. It doesn't do anything "special"

simms22 said:
absolutely! and he knows he can do that, but he had no access to a computer(he wrote that his friend is gonna come over with one though).
Click to expand...
Click to collapse
True, but have a Mac, and it is rare that being in recovery and connected to the Mac, do not recognize ....
then wait a Windows computer then ....

FIX! we got it!
Thanks for all the responses guys! We spend another 4 hours on this Sunday and finally got it! We ended up using this forum step by step. http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539
While my friend was installing all of the ADB drivers on his PC I attempted the steps on my mac. It made it through the first to lines of code but when rebooting into Boot loader it came back with a fail notice to unlock the OEM.
When he got all drivers installed we used the same lines of code (modifying C: for the location he had the ADB drivers) and it accepted all codes. Seeing that screen change into the OEM unlock select yes screen was a GREAT moment lol. After that we used NRT to flash Marshmallow...
All in all it was fun trying to figure this out! Not so much fun thinking I had to drop another $300 to get a new phone! Again thanks everyone for the help!

BladeRunner said:
All due respect to the developer, but all WUg's NRT does is automate the downloading and the commands you use to flash manually. It doesn't do anything "special"
Click to expand...
Click to collapse
Agreed, but its convenient as all hell.
Sent from my Nexus 6 using Tapatalk

Root Problems

Just got my unlocked Nexus 6 and am so looking forward to getting root back. My Samsung note 3 bricked and was a normal user and missed my apps. So I read up and downloaded Nexus tool kit and was able to unlock without issue. I can not unencrypt or root. Tried most of the day to no avail. It looks like it just hangs waiting to reboot but never does. I tried command line and get error on trying to write using the cf-root method. In user mode, I could not copy files from the pc. Is this cause of the encryption? I am using a windows 10 laptop, will try win 7 once I get it built. Any advice??

radavi98 said:
Just got my unlocked Nexus 6 and am so looking forward to getting root back. My Samsung note 3 bricked and was a normal user and missed my apps. So I read up and downloaded Nexus tool kit and was able to unlock without issue. I can not unencrypt or root. Tried most of the day to no avail. It looks like it just hangs waiting to reboot but never does. I tried command line and get error on trying to write using the cf-root method. In user mode, I could not copy files from the pc. Is this cause of the encryption? I am using a windows 10 laptop, will try win 7 once I get it built. Any advice??
Click to expand...
Click to collapse
I use this
http://forum.xda-developers.com/showthread.php?t=2947452
Sent from my Nexus 6 using Tapatalk

http://forum.xda-developers.com/nexus-6/general/attention-questions-t3228454

PaulPizz said:
I use this
http://forum.xda-developers.com/showthread.php?t=2947452
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
That is the toolkit I am using. It seems like it does not want to reboot on its own during the process and at the end wont boot on its own. I did poke around using explorer and did find busybox in a directory that had an !flash directory.<sp> I dont have the phone to look at currently. I tried root and root with custom recovery but the phone only boots to the OS. At some point am I supposed to boot into recovery? Is the boot/reboot process supposed to be automatic? Ive waited 20 minutes and the prompt/window would say booting to recovery.....but it would hang. I would manually boot to recovery and I would get the dead droid

i know you said you unlocked. is adb enabled in the rom. dev options? if not enable that and wait for the prompt to allow adb to your pc. win 10 is finicky with adb too i have noticed. use 7 and that may be it too. oh and when it prompts click the always allow checkbox before okaying it.