Database Info

100$ to whoever can help me solve this (NO JOKE)

i have already checked xda for a solution but couldnt find one i even checked google and youtube and still found nothing i am in need help bad. i will even pay someone paypal if they can help me with my phone
i downloaded the matrix rom and i liked it but i wanted to go back to ice cream sandwhich for the day so when i tried to go to recovery it froze on the google screen while trying to get to recovery i kept trying and trying but my recovery wasnt working i couldnt get to it. so i went to titanium back up and clicked un-install all system and data because i thought it was when i restored all system and data from ICS but after i did the uninstall i kept getting a force close alot of things and i got all the way down to one and it was process.android i think and everytime i clicked force close it popped right bacj up instently. so i took out the battery and put it back in and now i cant power on my phone it gets stuck on the matrix screen. can you please help me i can only acces the volume up power button menu.
*solved*

Fastboot OEM lock. Fastboot OEM unlock and start the process all over again. Also wipe everything 3 times.
Including system and boot.
Also double check you're installing all the compatible zips.
Sent from my Nexus S using xda premium

it wont let me do any of that it keeps saying waiting for device then gets stuck on that ive installed pdanet but it keeps giving me a htc sync error =1 and my bootloader and everything was already unlocked i dont know what to do i cant turn my phone on or get to recovery. thats why im paying 100 dollars to anyone who can help me restore my phone and make sure its up and running ive been trying for 2 days now and thats my work phone and everything im stressed

Serious_Beans said:
Fastboot OEM lock. Fastboot OEM unlock and start the process all over again. Also wipe everything 3 times.
Including system and boot.
Also double check you're installing all the compatible zips.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
when i turn on the phone and it keeps trying to load the matrix animation the phone still connects with my computer and says removable disk f but when i try and click on it. it says please insert a disk into removable disk f

Hmm uninstall all the USB drivers and reinstall them
Sent from my Nexus S using xda premium

Serious_Beans said:
Hmm uninstall all the USB drivers and reinstall them
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
at the bottom of my phone screen it says fastboot statud - FAILInvalid command

If you have the SDK installed on your computer. Here is what you need to do in order to get back into recovery.
#1 Boot your phone into bootloader, Vol up and power
-Plug into computer using usb while in fastboot(bootloader) and see if it recognizes it. Type adb devices it should list a serial number for your device.
( My SDK is installed in c:\android\) so you would type something like cd c:\android\tools and hit enter and then type adb devices )
#2 If you have installed sdk and pdanet drivers and your computer still does not see your phone in fastboot is this. Go to the folder where sdk is installed and copy everything excluding the folders that is in the Platform-tools folder into the tools folder. After that download Stock Phone files unzip it into a folder on desktop.
Dont run the script yet, what you have to do is after you unzip the stock look in the folder you just unzipped them in and you should see a file called fastboot, adb, and some other .dll's AdbWinApi.dll and etc move only these 4 files to your sdk tools folder.
#3 Now re open a cmd prompt and go back to c:\android\tools (enter) then type in adb devices and your computer should recognize it this time around.
Then all there is left to do is download the recovery of your choice here's mine Recovery and after you download it rename it recovery. After you rename it move it to sdk tools folder and while still in fastboot(bootloader) type in fastboot flash recovery recovery.img
You should now be able to enter recovery and flash roms again
EDIT #1
If you havent setup SDK here is a wiki guide on how to do so http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK

Make sure you are using the most up to date drivers and then use ADB to install recovery again. If I'm understanding it right I think that's what you need to try.
Sent from my Supercharged MikG'd up EVO 4g while eatin some Chop Suey.
Hit that thanks button if I managed to help.

Envynet said:
If you have the SDK installed on your computer. Here is what you need to do in order to get back into recovery.
#1 Boot your phone into bootloader, Vol up and power
-Plug into computer using usb while in fastboot(bootloader) and see if it recognizes it. Type adb devices it should list a serial number for your device.
( My SDK is installed in c:\android\) so you would type something like cd c:\android\tools and hit enter and then type adb devices )
#2 If you have installed sdk and pdanet drivers and your computer still does not see your phone in fastboot is this. Go to the folder where sdk is installed and copy everything excluding the folders that is in the Platform-tools folder into the tools folder. After that download Stock Phone files unzip it into a folder on desktop.
Dont run the script yet, what you have to do is after you unzip the stock look in the folder you just unzipped them in and you should see a file called fastboot, adb, and some other .dll's AdbWinApi.dll and etc move only these 4 files to your sdk tools folder.
#3 Now re open a cmd prompt and go back to c:\android\tools (enter) then type in adb devices and your computer should recognize it this time around.
Then all there is left to do is download the recovery of your choice here's mine Recovery and after you download it rename it recovery. After you rename it move it to sdk tools folder and while still in fastboot(bootloader) type in fastboot flash recovery recovery.img
You should now be able to enter recovery and flash roms again
EDIT #1
If you havent setup SDK here is a wiki guide on how to do so http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
Click to expand...
Click to collapse
can someone help me threw team viewer and just access my computer threw that and help me that way

Envynet said:
If you have the SDK installed on your computer. Here is what you need to do in order to get back into recovery.
#1 Boot your phone into bootloader, Vol up and power
-Plug into computer using usb while in fastboot(bootloader) and see if it recognizes it. Type adb devices it should list a serial number for your device.
( My SDK is installed in c:\android\) so you would type something like cd c:\android\tools and hit enter and then type adb devices )
#2 If you have installed sdk and pdanet drivers and your computer still does not see your phone in fastboot is this. Go to the folder where sdk is installed and copy everything excluding the folders that is in the Platform-tools folder into the tools folder. After that download Stock Phone files unzip it into a folder on desktop.
Dont run the script yet, what you have to do is after you unzip the stock look in the folder you just unzipped them in and you should see a file called fastboot, adb, and some other .dll's AdbWinApi.dll and etc move only these 4 files to your sdk tools folder.
#3 Now re open a cmd prompt and go back to c:\android\tools (enter) then type in adb devices and your computer should recognize it this time around.
Then all there is left to do is download the recovery of your choice here's mine Recovery and after you download it rename it recovery. After you rename it move it to sdk tools folder and while still in fastboot(bootloader) type in fastboot flash recovery recovery.img
You should now be able to enter recovery and flash roms again
EDIT #1
If you havent setup SDK here is a wiki guide on how to do so http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
Click to expand...
Click to collapse
Dang you must have put this up like 2 second before I posted mine lol
Sent from my Supercharged MikG'd up EVO 4g while eatin some Chop Suey.
Hit that thanks button if I managed to help.

Maybe you should just try Odin.
http://forum.xda-developers.com/showthread.php?t=1022481
DL: http://droidangel.blogspot.com/2011/05/odin-multi-downloader-flasher-program.html
Greetz

OP... check your PM inbox.

Why on earth have you posted this thread 6 times? Lol
Sent from my Nexus S using XDA App

scottypeterson said:
Dang you must have put this up like 2 second before I posted mine lol
Sent from my Supercharged MikG'd up EVO 4g while eatin some Chop Suey.
Hit that thanks button if I managed to help.
Click to expand...
Click to collapse
after i type adb it says adb isnt recognized as a internel or external cammand operable program or batch file

Ok I don't know if you tried this already but do this:
1. download the recovery img from here:
http://wiki.cyanogenmod.com/wiki/Ne...de#Installing_the_ClockworkMod_Recovery_Image
and put it somewhere on ur computer
2. plug phone into comp
3. boot the phone into the fastboot mode with the android guy
4. fastboot erase recovery
5. fastboot flash recovery ____.img
and if you can boot into recovery now, just wipe data, cache, and dalvik cache and flash the ics rom
see if that helps

mathkid95 said:
Ok I don't know if you tried this already but do this:
1. download the recovery img from here:
http://wiki.cyanogenmod.com/wiki/Ne...de#Installing_the_ClockworkMod_Recovery_Image
and put it somewhere on ur computer
2. plug phone into comp
3. boot the phone into the fastboot mode with the android guy
4. fastboot erase recovery
5. fastboot flash recovery ____.img
and if you can boot into recovery now, just wipe data, cache, and dalvik cache and flash the ics rom
see if that helps
Click to expand...
Click to collapse
I suggested this about 7 hours and 3 threads ago.. I think the problem is either he doesn't have the proper drivers or SDK setup properly.
Da_Reaper said:
after i type adb it says adb isnt recognized as a internel or external cammand operable program or batch file
Click to expand...
Click to collapse
This leads me to believe that SDK isn't set up properly. If it's set up correct you should be able to access adb without the phone even connected.

Yes thank you guys i love u all

check your mp , excepted if you found the solution.

$100? Lol
Sent from my Nexus S using XDA App

crump84 said:
I suggested this about 7 hours and 3 threads ago.. I think the problem is either he doesn't have the proper drivers or SDK setup properly.
This leads me to believe that SDK isn't set up properly. If it's set up correct you should be able to access adb without the phone even connected.
Click to expand...
Click to collapse
Yeah excuse me for not reading all 6 threads
Sent from my Nexus S using XDA App

[SD CARD][HOW TO] Cant Mount SD Card or SD Card Corrupted

For those who may be flashing ROMs, cannot mount the SD Card any more, and may have accidentally corrupted their SD Card, here are some helpful steps.
Preliminary Review - Check to see if you can mount in recovery or bootloader
First, go back to your bootloader screen and click on fastboot (reset your phone and hold the power and vol down button). Once in bootloader check your computer drives to see if the sd card is recognized
Your computer may be able to recognize the drive even if it cant open it. If thats the case, you may be able to format it from your computer (use FAT32 formatting).
Second, If you cannot see your SD Card in your ROM or from the PC, and you are using Clockwork Recovery (CW), try flashing TWRP recovery first. Do this by going through the following steps:
Step #1
Download TWRP recovery from http://teamw.in/project/twrp2/100 Make sure to download the correct version for your device
Step #2
Place the recovery file into a folder with fastboot.exe
Step #3
Reboot your phone and hold down the Vol Down Button and Power Button until your bootloader screen appears, then enter fastboot. Then connect to your computer. I find this method works best by holding down the buttons right away. If your phone is off, press the power button then immediately press and hold the power and vol off buttons again until bootloader screen shows up. Dont let go until the screen shows.
Step #4
Type
Code:
fastboot flash recovery twrp.img
but replace the twrp.img wording with the exact name of your downloaded TWRP recovery
Step #5
Enter TWRP recovery by selecting it from your bootloader screen. Then ensure the device is connected to your computer and select the Mount option and then mount your sd card.
IF you still cant see your SD Card from TWRP recovery or you get an error, proceed to the next steps. Your computer may be able to recognize the drive, even if it cant open it (if your lucky).
If your computer recognizes the drive but cant open it, you can try formatting it from your computer (make sure to format as FAT32)
If you really cant see your SD Card, and your fairly sure its corrupted, and you have no way formatting it from your computer, continue on below:
Basic Solution
Reflashing Stock Recovery to your device using fasboot, then doing a full factory reset. This would be using the method in post http://forum.xda-developers.com/showthread.php?t=1630459
PLEASE NOTE THIS METHOD WILL WIPE THE DATA FROM YOUR DEVICE AS WELL AS FROM YOUR SD CARD
This method works because custom recoveries cannot re format SD Cards on the HTC One S, only wipe data from them. However, the stock recovery does have a proprietary feature that will reformat the internal sd card if it has been corrupted.
Inotherwords:
Step #1
Download the stock recovery from: http://loadbalancing.modaco.com/download.php?file=ville_recovery_signed.img
*******Note that this file is a stock recovery for S4 devices, not S3.
Place the file into the same folder as your fastboot.exe
Step #2
On your device, go into bootloader and fastboot mode, connect your computer to the device, and type
Code:
fastboot flash recovery ville_recovery_signed.img
Step #3
Reboot into the bootloader and then choose to "clear storage" from the main screen and afterwards reset to factory defaults.
Step #4
Go back into the bootloader once step #3 is done and enter fastboot, connect your device and reflash your original custom recovery again. Your SD Card should be visible
Advanced Solution - If you do not want to wipe the data from your device
This method does not require reflashing the original recovery and factory reseting the whole phone. However, it still means that the info on your sd card will be lost. It also needs a rooted device.
This method does not require you to access your bootloader or use fastboot. You can do this while having your phone in custom recovery.
DO NOT ATTEMPT UNLESS YOU FEEL COMFORTABLE WITH THE INSTRUCTIONS. THERE ARE ALWAYS RISKS WITH FORMATTING. DO NOT HOLD ME RESPONSIBLE FOR BRICKED DEVICES. YOUR DEVICE IS LIKELY OUTSIDE OF WARRANTY ALREADY SINCE YOU WOULD HAVE UNLOCKED THE BOOTLOADER.
I have taken this solution from HTC One X forums namely from post 17 at http://forum.xda-developers.com/showthread.php?t=1647806&page=2
However, I have also confirmed (SneakyGhost's partition list for HTC One S) that the correct mmcblk0p for the HTC One S sd card is mmcblk0p36.
Step #1: Download the version of busybox listed below, unzip it and also put this in the folder with ADB before you get started. You only need to do this if you dont already have busybox installed on your HTC One S. Sometimes this busybox file can be found under /system/bin or /system/xbin if youve previously installed it. If so, replace the paths in the instructions below for that of your busybox. If you have busy box already installed in /system/bin , then you do not need to type in the paths since the adb shell automatically picks up programs in that folder
Step #2: Go to your command prompt in the folder with adb.exe . Connect your HTC One S to your computer and type
Code:
adb devices
and ensure your computer sees your HTC One S. This command should work even if you are in a custom recovery like TWRP or CW (but for gods sake, if your on CW, the first thing you should do is flash TWRP, but thats just an editorial opinion, lol).
Step #3: Type
Code:
adb push busybox /data/local/tmp
This pushes busybox to a temp folder on your HTC One S. Make sure you are pushing the busybox file and not the zip file. If you already have busy box installed you do not need to do this step. (you can delete it from this folder later if you like)
Step #4: Type
Code:
adb shell
to get into your linux shell. Then type
Code:
su
to get root access. Your command prompt should now be a # and not $.
Step #5: Type
Code:
chmod 755 /data/local/tmp/busybox
to fix permissions for busybox. You may not need to do this if you already have busy box installed with the correct permissions. If these instructions dont work with your version of busy box, try setting the permissions with this code but replace the path with the location of your busybox.
Step #6: Type
Code:
cat /proc/partitions
and just ensure you see mmcblk0p36. This is the sdcard partition for HTC One S
Step #7:Type
Code:
/data/local/tmp/busybox mkfs.vfat /dev/block/mmcblk0p36
Make sure you type this correctly. You dont want to format the wrong partition accidentally.
That should work. Pls let me know if it doesnt. If it doesnt work with your version of busybox just try using the one in the zip file below. Also remember, dont just push the zip file. Extract the busybox file from the zip and push that to your device instead.
Also, it may help to use adb through a custom recovery instead of being in your ROM (ie if it doesnt work when your phone is booted normally, try doing the steps with recovery loaded).
There are other methods to try too They would be:
Other Solutions
Other Method #1: Relocking your bootloader and using a compatible RUU with your phone. This will fully wipe your device
Other Method #2: If your computer sees your sdcard even if it cant open it when your device is connected, you can try formatting it that way (ie the way you would format any other drive on your computer)
Only use the busybox method if you are comfortable with it and if other methods have failed. You can learn more about the formatting command (ie mkfs.vfat) by googling it.

So if I got this right if I have busybox already I only have to do is step 7.

Almost, but yes, that is the key step. Although you would still want to open a terminal Window, either an adb shell or from the phone, and type su to get root, and double check to ensure the shell sees the partition. Also, I did hear in the one X forums that not every version of busy box worked. I would imagine an updated version would likely work though.
Sent from my HTC One S using xda premium

Step 4, a quicker way: adb shell su , get you into shell as root right away

AKToronto said:
Almost, but yes, that is the key step. Although you would still want to open a terminal Window, either an adb shell or from the phone, and type su to get root, and double check to ensure the shell sees the partition. Also, I did hear in the one X forums that not every version of busy box worked. I would imagine an updated version would likely work though.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Oh right hope I don't need it lol.
I think this should be moved to Q&A and replace the other sticky that's there.

Darknites said:
Oh right hope I don't need it lol.
I think this should be moved to Q&A and replace the other sticky that's there.
Click to expand...
Click to collapse
Im thinking it would be helpful to have this post there. Im not sure how I request to do that though. Should I PM a moderator?

AKToronto said:
Im thinking it would be helpful to have this post there. Im not sure how I request to do that though. Should I PM a moderator?
Click to expand...
Click to collapse
No idea but does sounds like a good start lol.

Darknites said:
No idea but does sounds like a good start lol.
Click to expand...
Click to collapse
I asked a moderater to review by clicking on the ! in the post, but I havent heard back yet. I also updated the post to be more n00b friendly too, and tried to cover off all sd card related issues.

AKToronto said:
I asked a moderater to review by clicking on the ! in the post, but I havent heard back yet. I also updated the post to be more n00b friendly too, and tried to cover off all sd card related issues.
Click to expand...
Click to collapse
Nice update. Ya I wish they hurry up with sorting it, the other one is a load of crap and this really should replace it.

Updated with a link to another good tutorial about pushing ROMs to the phone

Its like they don't care about stickys any more, come mods its about time this replaced the crappy one.

Cant get past the
'fastboot flash recovery ville_recovery_signed.img'
step at the moment, just keep getting 'waiting for device'.

Steveh8204 said:
Cant get past the
'fastboot flash recovery ville_recovery_signed.img'
step at the moment, just keep getting 'waiting for device'.
Click to expand...
Click to collapse
Does your bootloaderscreen say "fastboot usb" anywhere? There is an option that you have to select in your bootloader called fastboot... If it says fastboot usb then you are connected, and you shouldnt get a waiting for device error.

AKToronto said:
Does your bootloaderscreen say "fastboot usb" anywhere? There is an option that you have to select in your bootloader called fastboot... If it says fastboot usb then you are connected, and you shouldnt get a waiting for device error.
Click to expand...
Click to collapse
yea I got into the bootloader and then fast boot. ive managed to sort it now, for some reason my pc was the problem, I had to reboot my computer after a command window prompt otherwise I just got the waiting for device screen.
typical really, my laptop and phone both conspiring against me.
eventually managed to flash another recovery which did see my sdcard so all is good now.
thanks for your reply though!

AKToronto said:
For those who may be flashing ROMs, cannot mount the SD Card any more, and may have accidentally corrupted their SD Card, here are some helpful steps.
Click to expand...
Click to collapse
Dude, this works flawless!
Thought I had a soft-brick, but your instructions bring back my sd-card!
I choose the "advanced Option", it works fine....
Typing su-command generated an error message, but the other steps still functioned....
I will place link in section "helpfull links" in my signatur
Big THX to you good sir, ...

Steveh8204 said:
Cant get past the
'fastboot flash recovery ville_recovery_signed.img'
step at the moment, just keep getting 'waiting for device'.
Click to expand...
Click to collapse
Just format your phone using your PC... That's all you need to do...all those steps are overkill... Bootloader on phone... Connect to pc .. Navigate to devices on PC and format your phone...then flash recovery like stated above..
Sent from my One S using xda premium

$droyd$ said:
Just format your phone using your PC... That's all you need to do...all those steps are overkill... Bootloader on phone... Connect to pc .. Navigate to devices on PC and format your phone...then flash recovery like stated above..
Sent from my One S using xda premium
Click to expand...
Click to collapse
Some people had reported not being able to see their phone from their PC no matter what they tried... Hence the advanced steps

Dude add S3 stock recovery please.

Darknites said:
Dude add S3 stock recovery please.
Click to expand...
Click to collapse
Good point Darknites. Thank you. Do you have a link to S3 stock recovery? I dont seem to have one handy... But I did edit the OP to make that point a bit clearer (that the link is for S4 devices). Thanks again bud. Good catch.

AKToronto said:
Good point Darknites. Thank you. Do you have a link to S3 stock recovery? I dont seem to have one handy... But I did edit the OP to make that point a bit clearer (that the link is for S4 devices). Thanks again bud. Good catch.
Click to expand...
Click to collapse
Nope but a RUU will have it.

[Q] I've really messed up my phone, can't seem to install stock ROM now

How can I flash a stock ROM considering I cannot boot the phone up normally in order to put the file onto the phone? The Moto G has no external storage so I can't use an SD card.
I get get into the bootloader, and I have managed to install Team Win Recovery Project but don't know what else to do!

Euskadi said:
How can I flash a stock ROM considering I cannot boot the phone up normally in order to put the file onto the phone? The Moto G has no external storage so I can't use an SD card.
I get get into the bootloader, and I have managed to install Team Win Recovery Project but don't know what else to do!
Click to expand...
Click to collapse
Disclaimer : I have not used TWRP recovery on Moto G. So may have errors in my post
You have 2 options.
1. On some versions of TWRP, under advanced you have an option to mount USB. You can the access the phone as a drive from a computer.
2. Use ADB to push file to the phone. Install drivers and ADB works in recovery,

Thanks I actually found out about the adb push thing just after making this thread. I was able to push Beanstalk onto the device and install it through TWRP, however it's just stuck on the Beanstalk bootscreen forever. I tried installing it again and the same thing is happening. This also happened earlier when I tried to install Cyanogenmod

Once when i wanted to flash Stock 4.3 i got also stuck in bootanimation.
To restore Stock i had to execute flashall.bat /eu. The option /eu erases userdata. Once i did this my phone booted without any issues.
So what you can try is to erase userdata via fastboot or cwm
fastboot erase userdata
Click to expand...
Click to collapse

onyinly made
I tried one final Hail Mary before going to be last night, erased all data and installed Cyanogenmod again and I'm pleased to say it worked!
Only downside is I've lost all my apps & data. Now I did back these up using Titanium, and stored them on Google Drive, however the reason I got into this mess in the first place is because I manually flashed the 4.4.2 update, which worked ok, but then when I restored my apps/data with Titanium my soft buttons (back button etc) disappeared!
I guess I'll just play it safe and not try to restore the back up this time.

M8 u couldn't give a walk through guide how u pushed ROM to phone pls
Sent from my HTC Desire C using XDA Premium 4 mobile app

the sarge said:
M8 u couldn't give a walk through guide how u pushed ROM to phone pls
Click to expand...
Click to collapse
Not exactly an expert myself but look for a download of 'Fastboot', it should have a program called adb.exe or abd-windows.exe. Turn on your phone while holding the Volume Down button and it should start into the bootloader screen, plug in the USB and it will say it's connected.
Then you go to the folder (on your PC) that has adb.exe - put your ROM .zip into this folder - then hold shift and right-click somewhere inside the folder (not on a file) and choose "Open command window here".
Then you just type "adb push ROM.zip /sdcard" where ROM.zip is the name of the zip file. note: you might have to type adb-windows instead, depends what .exe you have
Then just wait until it finishes transferring. Will take 30 secs or so for a 200mb ROM.
I'm sure if you google "adb push" you'll get some better instructions, with downloads etc

While reverting to stock it's important to use mfastboot(moto-fastboot) instead of normal fastboot. Download mfastboot.exe and place in adb folder, and replace 'fastboot' commands with 'mfastboot'
Sent from my XT1032 using XDA Premium 4 mobile app

Or try supertool on root junkies download site worked for me to get o t a kit kat
Sent from my Moto G using XDA Premium 4 mobile app

[Q] I need help with my Nexus 5 with no OS on it.

I screwed up trying to restore and now it says the phone is not rooted and has no OS installed on it. I still have access to the custom recovery if that helps. I have tried using ADB and Fastboot but it does not seem to be working. I need to know asap because it is for my dad and he travels a lot. He needs a phone. Please any help is appreciated.

1.Flash twrp
2. Go to adb sideload
3. In the terminal type adb sideload filename.zip
The ROM will flash and that's it.
If you need it back to stock just google "nexus 5 factory image" then download the latest one and follow the instructions given by google.
Also are you running linux (which distro) or windows just so I know what to tell you if that doesn't work

First of al: It's best to not use Windows 8 since there have been some driver incompatibilities and I'm not sure if they have been completely fixed yet.
Install 'Universal Naked Driver' and 'Minimal ADB and fastboot'. Both can be found here on xda.
Download the latest factory image for hammerhead from Google website. Extract the downloaded file twice and copy over everything to your 'Minimal ADB and fastboot' install dir.
Double click the flash-all.bat while your phone is in bootloader mode.
This will COMPLETELY reset your phone (all personalbdata will be wiped). Only the bootloader will stay unlocked.

awsumatt said:
1.Flash twrp
2. Go to adb sideload
3. In the terminal type adb sideload filename.zip
The ROM will flash and that's it.
If you need it back to stock just google "nexus 5 factory image" then download the latest one and follow the instructions given by google.
Also are you running linux (which distro) or windows just so I know what to tell you if that doesn't work
Click to expand...
Click to collapse
When trying step 3, it says cannot read sideload.

The command is not "sideload filename.zip" but
"adb sideload filename.zip"
Did you enter it correctly?

What does the terminal say as an error? And are you running Linux, Mac, or windows?

experience7 said:
The command is not "sideload filename.zip" but
"adb sideload filename.zip"
Did you enter it correctly?
Click to expand...
Click to collapse
Yes that is exactly how i entered it but with the file name of course. Although I did try your method but i don't see any file called flash-all.bat.

So just gonna ask again, what message did you get in the terminal?

Did you extract it twice? There should be a tgz file at some point... this one can be extracted as well (using 7-zip for example)

experience7 said:
The command is not "sideload filename.zip" but
"adb sideload filename.zip"
Did you enter it correctly?
Click to expand...
Click to collapse
okay nevermind my last comment. Now it says fastboot is not recognizable internal or external command. Press any key to exit

After you copied all the files into the Minimal ADB and fastboot folder the flash-all.bat should be in the same directory as fastboot.exe. Is this the case?

Try adb kill-server then (I'm a little rusty with windows) su adb start-server

experience7 said:
Did you extract it twice? There should be a tgz file at some point... this one can be extracted as well (using 7-zip for example)
Click to expand...
Click to collapse
Okay after I run the flash-all.bat, it just hangs at waiting for device

Install the 'Universal Naked Driver', reboot your computer and try again.
Again: The phone has to be in bootloader mode (you have to see the green android)

experience7 said:
Install the 'Universal Naked Driver', reboot your computer and try again.
Again: The phone has to be in bootloader mode (you have to see the green android)
Click to expand...
Click to collapse
I've decided to take the loss on this one. I just do not have time for this. I'll just go get it replaced. Thank you so much for the help. I'll definitely use XDA for more of my android problems in the future. Thank you again and to everyone who replied to this thread.

sbecerra407 said:
I've decided to take the loss on this one. I just do not have time for this. I'll just go get it replaced. Thank you so much for the help. I'll definitely use XDA for more of my android problems in the future. Thank you again and to everyone who replied to this thread.
Click to expand...
Click to collapse
Install this(fastboot + adb): http://forum.xda-developers.com/showthread.php?t=2588979
Download the file for Nexus 5: https://developers.google.com/android/nexus/images
Extract the file
Connect phone to pc in bootloader mode
Double click in flash all script
Wait for it to finish

sbecerra407 said:
When trying step 3, it says cannot read sideload.
Click to expand...
Click to collapse
ofc... you need to ENABLE sideload on twrp itself..

Thread cleaned.
Let's keep it on topic guys,

Very poor call quality

Hi i'm new here and i'm really hoping someone can help me
I am using a one plus one. Running: Cyanogen OS Version 13.1.2-ZNH2KAS3P0-bacon
When I make phone calls the other person on the other end can only here static or can't even hear me at all!!! It's so frustrating not being able to talk to people. I looked on google and people are saying to disable google voice assistant which I did but I still have the same issue.
I am VERY NEW to all this rooting and stuff. I went google and youtube and people are suggesting to root the phone. I spent 5 hours watching youtube videos trying to figure out how to root my phone and put a OS on it. Every video I watch results in errors on my computer or phone.
I don't know what to do...is there a noob friendly guide? I read online that the Lineage OS is the best OS for oneplus one?

root with kingroot and done
go here for solution
https://forum.xda-developers.com/oneplus-one/development/fix-low-mic-call-t3055661
hit thumbs up for say thanks
go here for everything
https://forum.xda-developers.com/on...ex-oneplus-one-resources-compilation-t2843675
:good:

rony raj said:
root with kingroot and done
go here for solution
https://forum.xda-developers.com/oneplus-one/development/fix-low-mic-call-t3055661
hit thumbs up for say thanks
go here for everything
https://forum.xda-developers.com/on...ex-oneplus-one-resources-compilation-t2843675
:good:
Click to expand...
Click to collapse
I wouldn't share that fix too much the script is faulty and soft bricked some phones in the past.
I would rather do the fix manually.
There isn't much to do you have to change just 2 values in 2 different files.
/system/build.prop
Find
Code:
ro.qc.sdk.audio.fluencetype
Change "fluence" to "none"
/system/etc/audio_platform_info.XML
Find
Code:
SND_DEVICE_IN_HANDSET_MIC
And change the value from 40 to 4
I do this every time I flash a CM based ROM

rony raj said:
root with kingroot and done
go here for solution
https://forum.xda-developers.com/oneplus-one/development/fix-low-mic-call-t3055661
hit thumbs up for say thanks
go here for everything
https://forum.xda-developers.com/on...ex-oneplus-one-resources-compilation-t2843675
:good:
Click to expand...
Click to collapse
I did try Kingroot before and it was not even compatible with my device!
seanwlk said:
I wouldn't share that fix too much the script is faulty and soft bricked some phones in the past.
I would rather do the fix manually.
There isn't much to do you have to change just 2 values in 2 different files.
/system/build.prop
Find
Code:
ro.qc.sdk.audio.fluencetype
Change "fluence" to "none"
/system/etc/audio_platform_info.XML
Find
Code:
SND_DEVICE_IN_HANDSET_MIC
And change the value from 40 to 4
I do this every time I flash a CM based ROM
Click to expand...
Click to collapse
Am I able to make these changes without a rooted phone?

theaccountant87 said:
I did try Kingroot before and it was not even compatible with my device!
Am I able to make these changes without a rooted phone?
Click to expand...
Click to collapse
No, the directories are reachable only with root.
If your bootloader is unlocked you can just flash twrp as custom recovery through fastboot and then flash the superSU zip from the twrp recovery.
The OPO is one of the easiest phones to root ?

Haha not for me. Picture your grandma calling you to help her turn on the computer. I'm one step above that LOL.
I'm reading through the forums and there are all these confusing terms
seanwlk said:
No, the directories are reachable only with root.
If your bootloader is unlocked you can just flash twrp as custom recovery through fastboot and then flash the superSU zip from the twrp recovery.
The OPO is one of the easiest phones to root
Click to expand...
Click to collapse

theaccountant87 said:
Haha not for me. Picture your grandma calling you to help her turn on the computer. I'm one step above that LOL.
I'm reading through the forums and there are all these confusing terms
Click to expand...
Click to collapse
Here's a small guide that recaps the method I've used over the years.
*Warning* You will need to unlock your bootloader, which will factory reset your phone
1- Download and install fastboot and USB drivers https://drive.google.com/file/d/0B9fZIF6vzIBzT2ZtZkNSVFI5ZHc/view?usp=drivesdk
This is a all-in-one installer I found a long while ago and I keep it in my drive to have it always available wherever I go. Say yes to all the prompts. And reboot the PC just in case.
2- Download Twrp and SuperSU
https://eu.dl.twrp.me/bacon/twrp-3.1.0-0-bacon.img.html
https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
3- Backup all your data
4- Reboot your phone into bootloader and connect it to the PC.
5- Open a command prompt where you downloaded the twrp img file and type:
Code:
fastboot oem unlock
6- Now:
Code:
fastboot flash recovery twrp-3.1.0-0-bacon.img
(same name as the downloaded file)
7- Let the phone do the first boot.
8- Reboot into recovery flash the superSU zip you previously downloaded.
9- Boot the device.
PS
Always avoid minitools such as kingroot and stuff like that ? trust your terminal ?

seanwlk said:
Here's a small guide that recaps the method I've used over the years.
*Warning* You will need to unlock your bootloader, which will factory reset your phone
1- Download and install fastboot and USB drivers https://drive.google.com/file/d/0B9fZIF6vzIBzT2ZtZkNSVFI5ZHc/view?usp=drivesdk
This is a all-in-one installer I found a long while ago and I keep it in my drive to have it always available wherever I go. Say yes to all the prompts. And reboot the PC just in case.
2- Download Twrp and SuperSU
https://eu.dl.twrp.me/bacon/twrp-3.1.0-0-bacon.img.html
https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
3- Backup all your data
4- Reboot your phone into bootloader and connect it to the PC.
5- Open a command prompt where you downloaded the twrp img file and type:
Code:
fastboot oem unlock
6- Now:
Code:
fastboot flash recovery twrp-3.1.0-0-bacon.img
(same name as the downloaded file)
7- Let the phone do the first boot.
8- Reboot into recovery flash the superSU zip you previously downloaded.
9- Boot the device.
PS
Always avoid minitools such as kingroot and stuff like that trust your terminal
Click to expand...
Click to collapse
Thanks so much for your help ! In step 3 when you say backup all your data, rather than copying all my pictures and contacts is there a quicker way? Do you use a program to backup an image of your phone that saves everything including text messages, contacts and pictures?

theaccountant87 said:
Thanks so much for your help ! In step 3 when you say backup all your data, rather than copying all my pictures and contacts is there a quicker way? Do you use a program to backup an image of your phone that saves everything including text messages, contacts and pictures?
Click to expand...
Click to collapse
I don't use any kind of software, I'm just organised, since I factory reset very often I keep stuff in the Download/Video/Image/Music folders and I copy them every time.
For the contacts I use google contacts which let's me sync across all the devices and save stuff without losing it in case of reset. Never saved a contact in my SIM.
I use only whatsapp and other IM apps that have their own backup online systems so I never lose anything but applications which I later downalod and install again.

seanwlk said:
I don't use any kind of software, I'm just organised, since I factory reset very often I keep stuff in the Download/Video/Image/Music folders and I copy them every time.
For the contacts I use google contacts which let's me sync across all the devices and save stuff without losing it in case of reset. Never saved a contact in my SIM.
I use only whatsapp and other IM apps that have their own backup online systems so I never lose anything but applications which I later downalod and install again.
Click to expand...
Click to collapse
Got it . Thanks again Sean. I'll give it a shot later on tonight!

theaccountant87 said:
Got it . Thanks again Sean. I'll give it a shot later on tonight!
Click to expand...
Click to collapse
Good luck ? it's not hard as it seems

Hi Sean,
i'm stuck on: 8- Reboot into recovery flash the superSU zip you previously downloaded.
I have the zip file in my sdk platform tools folder and in CMD prompt I put:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
adb push UPDATE-SR3-SuperSU-v2.79-SR3-20170114223742.zip /sdcard/
I get
adb: error: failed to get feature set: no devices/emulators found
I tried to manually copy the SuperSu zip file into my device but when I connect my OnePlus I can't see it being connected to my computer?!
I'm a little worried because my phone is unusable as of now and just in recovery mode

theaccountant87 said:
Hi Sean,
i'm stuck on: 8- Reboot into recovery flash the superSU zip you previously downloaded.
I have the zip file in my sdk platform tools folder and in CMD prompt I put:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
adb push UPDATE-SR3-SuperSU-v2.79-SR3-20170114223742.zip /sdcard/
I get
adb: error: failed to get feature set: no devices/emulators found
I tried to manually copy the SuperSu zip file into my device but when I connect my OnePlus I can't see it being connected to my computer?!
I'm a little worried because my phone is unusable as of now and just in recovery mode
Click to expand...
Click to collapse
You can mount the phone as MTP from the twrp recovery in the advanced settings, and then you'll be able to copy the files inside.
What do you mean with unusable? If you did as I wrote everything should be fine.
Just in case if the phone bootloops or it's stuck in the bootlogo, from the recovery wipe cache dalvik and data.
NOTE.
First boot can take a while, mine once lasted 30min after I clean fresh installed a ROM
EDIT
You don't need to move to the SDK folder on the cmd, the tool I made you Install works system wide from every folder, that's why I love it.