Database Info

[Q] Stuck in Recovery

A buddy of mine has a Nexus S. He's been having issues with his phone. He was having issues with screen locking, none responsive, etc. Now his phone won't boot. It stays stuck in recovery. Anything can be done? Phone is not rooted.

For sure. Is it a custom recovery or stock?
Sent from my Nexus S using XDA Premium App

For sure. Is he running a custom recovery or stock?
Sent from my Nexus S using XDA Premium App

He's running stock.
It's weird that it's degraded like this. I've only had a Captivate and now I have the Atrix and I've never seen this happen unless trying to flash a custom rom. But I know he doesn't know how to do that.
To get specific he's got:
OS: 2.3.3
Baseband: I9020XXKb1
Kernel: 2.6.35.7-g1d030a7
Build Number: GRI40.

My friend, you must do the following:
1- flash cwm recovery via sdk on bootloader mode.
2- download any rom from the development forum (stock, cm7, and so on)
3- mount USB storage via cwm recovery
4- put the mod zip file on the root of the sdcard via usb
5- flash the rom(install zip)
6- reboot your device
Sent from my Nexus S using XDA Premium App

thanks! it's gonna be a bit of a task since i have to walk him through it all remotely.

razorbladex401 said:
thanks! it's gonna be a bit of a task since i have to walk him through it all remotely.
Click to expand...
Click to collapse
NP
If you have any issues please post here so that i can help you

Having an issue installing the drivers. When we connect the phone it shows up as an unknown device. I try to use the google drivers and it doesn't install them. I install kies and it was able to install some drivers but i need to get adb access which I can't. The phone is in the bootloader but nothing i can do to it. Any ideas?

razorbladex401 said:
Having an issue installing the drivers. When we connect the phone it shows up as an unknown device. I try to use the google drivers and it doesn't install them. I install kies and it was able to install some drivers but i need to get adb access which I can't. The phone is in the bootloader but nothing i can do to it. Any ideas?
Click to expand...
Click to collapse
Try pdanet. It installs the drivers for any phone. Install it on his computer and his phone.
Sent from my Nexus S using XDA App

Rafael Cadina said:
My friend, you must do the following:
1- flash cwm recovery via sdk on bootloader mode.
2- download any rom from the development forum (stock, cm7, and so on)
3- mount USB storage via cwm recovery
4- put the mod zip file on the root of the sdcard via usb
5- flash the rom(install zip)
6- reboot your device
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
He's gonna need to root before being able to flash a custom recovery.
Sent from my Nexus S using XDA App

I spent 6 hours fixing this guys problem because he was a amateur.
Read this http://forum.xda-developers.com/showthread.php?t=1000722 It'll go through the process. It's pretty much the same as your problem.
tl;dr.
1. Get USB Drivers
2. Setup SDK tools
(Links for these are in my thread).
3. Unlock the phone if it isn't already (fastboot oem unlock)
4. Download CWR IMG (its in my thread)
5. fastboot flash recovery recovery.img (rename crespo-clockwork..... to recovery.img; it has to be in /sdk/tools/ .. show extensions).
6. boot into CWR
7. mount USB
8. download a ROM (or do this before you start -- or nandroid backup)
9. wipe dalvik,cache,factory (if you're flashing a ROM)
10. flash or nandroid restore
11. phones back to normal

zephiK said:
I spent 6 hours fixing this guys problem because he was a amateur.
Read this http://forum.xda-developers.com/showthread.php?t=1000722 It'll go through the process. It's pretty much the same as your problem.
tl;dr.
1. Get USB Drivers
2. Setup SDK tools
(Links for these are in my thread).
3. Unlock the phone if it isn't already (fastboot oem unlock)
4. Download CWR IMG (its in my thread)
5. fastboot flash recovery recovery.img (rename crespo-clockwork..... to recovery.img; it has to be in /sdk/tools/ .. show extensions).
6. boot into CWR
7. mount USB
8. download a ROM (or do this before you start -- or nandroid backup)
9. wipe dalvik,cache,factory (if you're flashing a ROM)
10. flash or nandroid restore
11. phones back to normal
Click to expand...
Click to collapse
Zephiks got you covered. I was gonna walk you throught it but had to go to class. Hope you get it working.
Sent from my Nexus S using XDA App

I can't get the phone to show up as an adb device. I had installed the drivers using PDAnet which worked for a few minutes. I went to unlock the bootloader but it just froze. It didn't do anything after about an hour we powered the phone off. now after you start it up it doesn't show up as an adb device.......

razorbladex401 said:
I can't get the phone to show up as an adb device. I had installed the drivers using PDAnet which worked for a few minutes. I went to unlock the bootloader but it just froze. It didn't do anything after about an hour we powered the phone off. now after you start it up it doesn't show up as an adb device.......
Click to expand...
Click to collapse
What OS do you run in your PC?
You must first download de sdk .zip, extract it into a folder.
Then, install USB package from the SDK.
Then, enter devmgmt.msc on Run... (Windows). Select the driver that is missing (Android 1.0) > Left click > Update driver > Browse my computer > Let me pick from a list > have disk > choose the folder you installed google usb drivers (inside C:\ SDK folder\extra).

Rafael Cadina said:
What OS do you run in your PC?
You must first download de sdk .zip, extract it into a folder.
Then, install USB package from the SDK.
Then, enter devmgmt.msc on Run... (Windows). Select the driver that is missing (Android 1.0) > Left click > Update driver > Browse my computer > Let me pick from a list > have disk > choose the folder you installed google usb drivers (inside C:\ SDK folder\extra).
Click to expand...
Click to collapse
Yea i've tried that to load the driver. It's running Windows 7 Home Premium 64bit. The only drivers that seem to work are from PDAnet. I finally got it to show up again so i've issued the fastboot oem unlock, my buddy confirms it but the phone does nothing.....

[Q] Need URGENT help............? Nexus S. Problem with Android Bootloader Interface.

Need URGENT help............? Nexus S. Problem with Android Bootloader Interface or perhaps i don't have any idea what the problem is.
I am using nexus s 19020T, rooted, clockworkmod . My problem starts with ICS update. I got update and tried to install it. I got bellow error
"Opening update package...
Installing update...
Verifying current system...
failed to stat "/system/app/Gmail.apk": No such file or directory
file "/system/app/Gmail.apk" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/app/Gmail.apk", "94d64de3d567cb9205f52a734e95f9053e6e6e99", "e2a3cf5648dbfa057787610d3f35f557297ea6bb")
assert failed: apply_patch_check("/system/app/Gmail.apk", "94d64de3d567cb9205f52a734e95f9053e6e6e99", "e2a3cf5648dbfa057787610d3f35f557297ea6bb")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/update.zip")
"
Then i reverted every thing back to 2.3.1 (nandroid backup). Now I am not able to become superuser. But I got 2.3.6 OTA. Again tried to update super user binaries. I am getting error "signature verification failed. Installation aborted."
I able to access the adb via command prompt whenever my mobile is power on but when I am in fastboot I am not able to access adb and fastboot commands. I can clearly see whenever device reboots under "devmgmt.msc" Android Phone - Android Bootloader Interface is disappearing.
It seems same problem faced here http://forum.xda-developers.com/archive/index.php/t-1304158.html. But in my case I don't have clockworkrecovery access also, My mobile is just unlocked without root access. I don't have any idea how to install image. At least I want to install clockwork recovery. Is there any other way around to do that?
Please let me know if you need further information.
Thanks in advance. Really not being a superuser sucks..........!

Earlier few days i tried [ROM][AOSP] ICS build for Nexus S - kwiboo for few days and back to 2.3.6 using rommanager. Is it got to do any thing with " ICS build for Nexus S"?

Try format /system, becareful not to format the wrong partition. Then flash a full ROM, eg. 4.0.3 full ROM (about 160MB). Apply root afterwards.

Si_NZ said:
Try format /system, becareful not to format the wrong partition. Then flash a full ROM, eg. 4.0.3 full ROM (about 160MB). Apply root afterwards.
Click to expand...
Click to collapse
May I know the procedure? Because I am not able to install any rooted application and I am not able to use adb/fastboot commands while I am in Fastboot mode.

My problem seems to be faced by one person http://forum.xda-developers.com/archive/index.php/t-1304158.html. But in my case I don't have clockworkrecovery access also, My mobile is just unlocked without root access.

229 views no reply...!

When in bootloader mode, does fastboot devices display the device ID correctly?

sorry i don't know how to solve it

suksit said:
When in bootloader mode, does fastboot devices display the device ID correctly?
Click to expand...
Click to collapse
yup we can see device serial number in fastboot mode.

sriharshavr.y said:
May I know the procedure? Because I am not able to install any rooted application and I am not able to use adb/fastboot commands while I am in Fastboot mode.
Click to expand...
Click to collapse
Try read the stickied thread for rooting carefully. You need to get at least fastboot working, so that you can flash CWM. I suspect you have a driver issue. Believe it or not, doing it in Linux is probably easier than you think... Most modern Linux distributions have drivers for these phones out of the box. When I was trying to resurrect my bricked phone, I used the Ubuntu live CD. It detected the phone on the live CD without me doing anything! If you want, you can read the stickied root guide for Ubuntu. Do it in a VM or install it on a spare computer, whatever you prefer.

You need to install stock rom from rom manager ver 2.3.3 then update to 2.3.6 then apply the update.zip from the stock recovery =] that worked for me

irizwan said:
You need to install stock rom from rom manager ver 2.3.3 then update to 2.3.6 then apply the update.zip from the stock recovery =] that worked for me
Click to expand...
Click to collapse
Hey irizwan thaks for giving reply. But here my problem is, I lost super user binaries and I am not able to install anything which requires root access.

sriharshavr.y said:
Hey irizwan thaks for giving reply. But here my problem is, I lost super user binaries and I am not able to install anything which requires root access.
Click to expand...
Click to collapse
Opps sorry ... i don't know how to help you here ... right now i'm on ICS completely stock waiting for a stable root =]

sriharshavr.y said:
yup we can see device serial number in fastboot mode.
Click to expand...
Click to collapse
If fastboot devices command works, then you shouldn't have any problem installing CWM recovery.
Put the downloaded recovery image in the same directory as fastboot.exe then use the command fastboot flash recovery your-downloaded-recovery.img to flash it.

Si_NZ said:
Try read the stickied thread for rooting carefully. You need to get at least fastboot working, so that you can flash CWM. I suspect you have a driver issue. Believe it or not, doing it in Linux is probably easier than you think... Most modern Linux distributions have drivers for these phones out of the box. When I was trying to resurrect my bricked phone, I used the Ubuntu live CD. It detected the phone on the live CD without me doing anything! If you want, you can read the stickied root guide for Ubuntu. Do it in a VM or install it on a spare computer, whatever you prefer.
Click to expand...
Click to collapse
Can I have link or some resource for more information to follow the above mentioned procedure because I am quiet new to linux.

I actually formatted my 'nexus s' with windows 7 operating system, because win 7 is prompting when ever I plugged in my mobile to access sdcard. My question is
"Is there any relation between formatting sdcard and corrupting bootloader"?

You can ROOT your device very easy...
first download : http://www.4shared.com/zip/2L09-JyW/Root_Nexus_S.html
Just unpack , connect your device and click run.bat
After that you need : remove install-recovery.sh just in .....
run in windows-> Start->at the search bar write cmd and navigate into your android sdk is installed
For me :
C:/"Programs and Files (x86)"/Android/android-sdk/tools/>adb shell
# rm /system/etc/install-recovery.sh
#exit
or with Root Explorer into system/etc/install-recovery.sh just renam it (ex. : .sh.old)

sriharshavr.y said:
Can I have link or some resource for more information to follow the above mentioned procedure because I am quiet new to linux.
Click to expand...
Click to collapse
If you have a 9020T, follow this guide http://forum.xda-developers.com/showthread.php?t=895545
If you have a i9023 or i9020A, follow this guide http://forum.xda-developers.com/showthread.php?t=1007782
Try that first, hopefully you can get fastboot working in Windows. Otherwise, I have to walk you through the steps to do it in Ubuntu.

Pantech Element TWRP Recovery and Stock Rooted Roms

This is TWRP recovery and Stock rooted roms for the ICS firmware on the tablet.
These will only work if you currently have ICS running on your tablet. If you still have honeycomb then do the upgrade first.
Nothing was added or removed from the stock roms besides root and busybox.
Only bug with TWRP is that you can't mount sdcard in recovery. Just use adb push.
Instructions for installing TWRP Recovery:
1. Ensure you have Android SDK installed with adb and fastboot working
2. Download both the twrprecovery.img and twrprecovery.zip from here
3. Copy twrprecovery.zip to external sdcard
4. Reboot tablet to bootloader by issuing the command "adb reboot bootloader"
5. Then "fastboot boot twrprecovery.img"
6. When in recovery choose install then browse to /sdcard and choose twrprecovery.zip and flash that zip
7. Now TWRP is installed permanently.
Thanks:
attn1 - gave me some help since I am new to pantech devices
Dees_troy - for TWRP code obviously
Tassadar - for his rotation code for twrp. Without this it wouldn't have been possible

Disclaimer: Flash this ROM at your own risk. I am not responsible for what you do on your device. I left this stock to provide a base for anybody that wants to use it. Mod this rom how you want. Just please remember to give credit where credit is due.
This is a pure stock rooted rom. It has items like busybox, init.d support and so forth. No apps were added or removed. Both Odexed and Deodexed versions below.
Downloads

just in case i need another

Once I reboot into fastboot, I am getting 'cannot load twrprecovery.img': no error
Any ideas? I even created a directory named tools in the adb directory on my computer and moved twrprecovery.img into it.
(Thought that might help).
Where is the twrprecovery.img file supposed to reside? (On the computer, or on the phone?)

mavblues said:
Once I reboot into fastboot, I am getting 'cannot load twrprecovery.img': no error
Any ideas? I even created a directory named tools in the adb directory on my computer and moved twrprecovery.img into it.
(Thought that might help).
Where is the twrprecovery.img file supposed to reside? (On the computer, or on the phone?)
Click to expand...
Click to collapse
On the computer. your command prompt should be at wherever you put twrprecovery.img file is. So for example you put twrprecovery.img at the root of c:, your command prompt should read c:/ .....
Sent from my M7 using xda premium

Tada!!!
Thanks, you rock!
---------- Post added at 01:39 PM ---------- Previous post was at 01:10 PM ----------
OK, stupid question:
How do you reboot to TWRP? It loaded the first time, and I did a backup.
After reboot, I can only seem to get into the standard recovery.
What is the button combination to get to TWRP?
Also, will we be able to use goo manager to update TWRP as new versions come out, or is this a custom version?
TIA

mavblues said:
Tada!!!
Thanks, you rock!
---------- Post added at 01:39 PM ---------- Previous post was at 01:10 PM ----------
OK, stupid question:
How do you reboot to TWRP? It loaded the first time, and I did a backup.
After reboot, I can only seem to get into the standard recovery.
What is the button combination to get to TWRP?
Also, will we be able to use goo manager to update TWRP as new versions come out, or is this a custom version?
TIA
Click to expand...
Click to collapse
Read the instructions. You HAVE to flash the zip I provided for recovery to be installed permanently.
This recovery required some special code for screen rotation. Dees_troy is working on getting it added to mainline. So right now you can't get it through goo manager. But I work closely with Dees to make sure all my builds are officially supported. I will post here when it becomes available through there
Sent from my M7 using xda premium

jmztaylor said:
Read the instructions. You HAVE to flash the zip I provided for recovery to be installed permanently.
This recovery required some special code for screen rotation. Dees_troy is working on getting it added to mainline. So right now you can't get it through goo manager. But I work closely with Dees to make sure all my builds are officially supported. I will post here when it becomes available through there
Sent from my M7 using xda premium
Click to expand...
Click to collapse
Got it - working great!

I'm stuck on fastboot mode. <waiting on device>
I tried unplug/replug USB to different connector, and it's still on <waiting for device>
I even tried to install driver manually from each files pantech folder and still no response
TWRP is on same folder and also set on environment variable
I have done adb devices and it detects as PORORO03111xxxxxxxxxxx
Any suggestion guys?

dagadu said:
I'm stuck on fastboot mode. <waiting on device>
I tried unplug/replug USB to different connector, and it's still on <waiting for device>
I even tried to install driver manually from each files pantech folder and still no response
TWRP is on same folder and also set on environment variable
I have done adb devices and it detects as PORORO03111xxxxxxxxxxx
Any suggestion guys?
Click to expand...
Click to collapse
Waiting on device in fastboot means drivers aren't installed or the wrong ones are. Download the software upgrade app from pantech site then install. Browse to the install directory and run the installer for the drivers. But before that uninstall whatever drivers you have installed currently. I'm mobile or else I would link you directly
Sent from my M7 using xda premium

dagadu said:
I'm stuck on fastboot mode. <waiting on device>
I tried unplug/replug USB to different connector, and it's still on <waiting for device>
I even tried to install driver manually from each files pantech folder and still no response
TWRP is on same folder and also set on environment variable
I have done adb devices and it detects as PORORO03111xxxxxxxxxxx
Any suggestion guys?
Click to expand...
Click to collapse
Did you check "USB debugging" on the tablet?
Also, I had to set USB connection on the tablet to the last choice "PC Data Mode".
Hope it helps.

jmztaylor said:
Waiting on device in fastboot means drivers aren't installed or the wrong ones are. Download the software upgrade app from pantech site then install. Browse to the install directory and run the installer for the drivers. But before that uninstall whatever drivers you have installed currently. I'm mobile or else I would link you directly
Sent from my M7 using xda premium
Click to expand...
Click to collapse
Is this what you're referring to? I download it from Pantech website.
htt p://c7240 62.r62 .cf2.rackcdn. com/PantechPCSuite_1.1.1.3437. exe
When do I need to install the driver? During fastboot mode, or normal mode?
I also notice that when I change the usb mode to MTP, it detects missing driver as well.
During normal mode it detects 2 pantech drivers in order to connect to pc suite.
Oya, when you guys do adb devices, does your device detect POROROxxxxxxx as well or only numbers?
I wonder this has anything to do with it, because I was trying to root with honeycomb version earlier and my pantech is ICS 4.0.4

dagadu said:
Is this what you're referring to? I download it from Pantech website.
htt p://c7240 62.r62 .cf2.rackcdn. com/PantechPCSuite_1.1.1.3437. exe
When do I need to install the driver? During fastboot mode, or normal mode?
I also notice that when I change the usb mode to MTP, it detects missing driver as well.
During normal mode it detects 2 pantech drivers in order to connect to pc suite.
Oya, when you guys do adb devices, does your device detect POROROxxxxxxx as well or only numbers?
I wonder this has anything to do with it, because I was trying to root with honeycomb version earlier and my pantech is ICS 4.0.4
Click to expand...
Click to collapse
Anytime when the tablet is not plugged in. This will make the computer automatically install anything needed for the tablet and you won't have issues with fastboot or adb anymore
Sent from my M7 using xda premium

jmztaylor said:
Instructions for installing TWRP Recovery:
1. Ensure you have Android SDK installed with adb and fastboot working
2. Download both the twrprecovery.img and twrprecovery.zip from here
3. Copy twrprecovery.zip to external sdcard
4. Reboot tablet to bootloader by issuing the command "adb reboot bootloader"
5. Then "fastboot boot twrprecovery.img"
6. When in recovery choose install then browse to /sdcard and choose twrprecovery.zip and flash that zip
7. Now TWRP is installed permanently.
Click to expand...
Click to collapse
I did not understand anything of this manual...
I took the CWM file for Pantech A810S and replaced it recovery to ours, flashed(connect working Element to PC and start cwm.but), everything works.

1806 said:
I did not understand anything of this manual...
I took the CWM file for Pantech A810S and replaced it recovery to ours, flashed(connect working Element to PC and start cwm.but), everything works.
Click to expand...
Click to collapse
Actually it's similar steps; however, yours is more like 1-click root
Anyway, I tried everything all above, but it didn't solve my problem, then I found the solution from other website
I just want to share in case others are stuck in fastboot mode like me:
1. When your tablet screen is on fastboot mode (white), go to device manager on your pc
2. Right click on Android > Update driver
3. Click on Browse driver
4. Choose Let me pick manually from my pc list
5. Choose Android phone and pick the first list there. It should be "Android ADB..."
6. Install and fastboot continued
if you can't find Android ADB from your pc list, then you should unplug device then install PC Suite.
here's the old tuts: youtube com/watch?v=UHRonVzBMsI
Hopefully it helps others and thank you very much for all your help!

Delete!

Finally! and a question
Finally a recovery for the element! Rhanks to the OP. Now I am less afraid to tinker with my tablet.
Question: The most important thing right now that I'd like to do is move the folder /data/data from the internal storage, to the internal SD card. This is stopping me from using Google Magazines and Google music, since their data is being stored there, and it shares space with actual applications. 1GB is not that much space for APPS, Dalvik Cache and APPs' data when you add magazines, and when google starts caching Music and Chrome data there. I currently only have 300MB left before I install Music and magazines. And that is AFTER I've used app2sd on all apps that can be moved. How do I do this?
I have tried simply creating a Link using "ln - s /mnt/sdcard/data /data/data" once I copied/moved the contents of the directory, which sort of works initially, but it will not work after a reboot. It actually stops my tablet from booting. (again, thanks to the OP for the recovery).
right now, I am just doing an "ln" on the specific folder inside the /data/data folder, but it acts weird when I use Titanium Backup to restore data
-> Android noob <-

Installing TWRP went smooth as silk. With twrprecovery.zip on you micro sdcard and Element connected with usb cable and USB debuuging checked 1.Just copy twrprecovery.img into your sdk folder/ platform-tools and also have a copy of cmd.exe from windows in the platform-tools folder. 2. Start cmd.exe and type or copy & paste command reboot bootloader 3. Then on white screen(fastboot) type or paste command fastboot boot twrprecovery.img 4. When you boot into TWRP install twrprecovery.zip.....As you rebbot system TWRP should ask if you want Supersu installed and swipe to install. Once rebooted install supersu from the Play store and open Supersu to update SU file all should be good
Thanks for the info and files. I know I'm a little late on this Tablet but picked it up cheap and with ATT 4G it goes along with my devices. The orginial owner hadn't even installed ICS and she wasn't even aware of an update. She now owns an Apple :laugh::laugh:device LOL

I just picked one up for $90 bucks off ebay. It was on slickdeals .net
Figured i'd use it around the pool and save my phone!
No one has deved a JB rom though Could KK even be possible?

marcustaz said:
I just picked one up for $90 bucks off ebay. It was on slickdeals .net
Figured i'd use it around the pool and save my phone!
No one has deved a JB rom though Could KK even be possible?
Click to expand...
Click to collapse
Yes good deal, got mine last month on Craigslist for $70.00 and works really well. The owner hadn't even updated to 4.0 or even knew how. It is a good tablet and have rooted it. I think its development is pretty well dead as not many sold. Only thing bad about it is the Element reads 2nd partition instead of 1st as most android devices do, so harder to use link2sd or folder mount as they both use 2nd partition.
Sent from my PantechP4100 using XDA Premium 4 mobile app

ADB won't recognize phone/bootloader/Can't replace recovery HELP!

So basically I found out just today we have Cyanogenmod 10.2 >.<
I downloaded the Joilaroi version, flashed it in TWRP 2.6xx and then suddenly "E: Error in updating binary script" did a bit of googling and found out that it's a common problem with TWRP > 2.3.3.0
So I was about to downgrade it to 2.3.3.0 or temp boot into CWM. Connected my phone to my laptop and went to bootloader, then did Adb devices....the list was empty.
Reinstalled HTC drivers, used different USB port...nothing.
TL;DR : Phone doesn't get recognized in Bootloader mode, Can't flash ROM, Can't replace recovery. Help!

AIndoria said:
So basically I found out just today we have Cyanogenmod 10.2 >.<
I downloaded the Joilaroi version, flashed it in TWRP 2.6xx and then suddenly "E: Error in updating binary script" did a bit of googling and found out that it's a common problem with TWRP > 2.3.3.0
So I was about to downgrade it to 2.3.3.0 or temp boot into CWM. Connected my phone to my laptop and went to bootloader, then did Adb devices....the list was empty.
Reinstalled HTC drivers, used different USB port...nothing.
TL;DR : Phone doesn't get recognized in Bootloader mode, Can't flash ROM, Can't replace recovery. Help!
Click to expand...
Click to collapse
Why don't you flash with terminal emulator?
Just put recovery.img in the root of your sdcard
Open terminal type
su
cd sdcard
flash_image recovery recovery.img
That's it
Sent from my gt-1900 using xda premium

Taha Haq said:
Why don't you flash with terminal emulator?
Just put recovery.img in the root of your sdcard
Open terminal type
su
cd sdcard
flash_image recovery recovery.img
That's it
Sent from my gt-1900 using xda premium
Click to expand...
Click to collapse
That's what I'm doing now but I need a proper solution :/ Basically Windows won't recognize my phone through fastboot. I'd rather not keep installing CM9 again and again after a failed flash, you know?

AIndoria said:
That's what I'm doing now but I need a proper solution :/ Basically Windows won't recognize my phone through fastboot. I'd rather not keep installing CM9 again and again after a failed flash, you know?
Click to expand...
Click to collapse
install htc drivers and make dure you cleared the all registry and files from your previous installation and connect your device
open cmd and go to the folder where you placed adb and type command
adb kill-server =>it will close all adb processes running at that time
adb start-server => it will start new adb process
adb devices=> to reconize your device
if it shows your device then through fastboot command flash the recovery
but make sure you have all neccessary binary files in that folder for adb and fastboot
hit thanks if helped

AIndoria said:
That's what I'm doing now but I need a proper solution :/ Basically Windows won't recognize my phone through fastboot. I'd rather not keep installing CM9 again and again after a failed flash, you know?
Click to expand...
Click to collapse
You can try installing the newer Drivers.
Else your usb port may be broken. that is also a possiblity

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.