Help me please - OnePlus 3 Questions & Answers

Read from here please!!!!!!
http://forum.xda-developers.com/oneplus-3/development/rom-tipsyos-t3399355/page17
POST #165
Phone is encrypted!!!!

Wrong pin after restore?
Sent from my OnePlus3 using XDA Labs

Wrong section, the Q&A is made for that.
Into recovery > advanced > Terminal or with adb shell":
Code:
rm /data/system/locksettings.*
Reboot.

Related

[RECOVERY][ClockWorkMod 3.0.2.8][BETA]

Disclaimer:
Proceed at your own risk. I am not responsible if your device gets bricked or damaged during the process.
recovery-CW3028-OP-thunderc_002.zip
Port to Optimus V
This version is using a beta kernel I am working on. (driver updates from new Optimus-S source, NOOP set default)
Backup and restore tested.
Camera button == Action
Code:
In an ADB shell:
> mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
> cat /sdcard/flash_image > /system/bin/flash_image
> chmod 755 /system/bin/flash_image
> mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
> mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
> flash_image recovery /sdcard/recovery.img
> exit
reboot into recovery (I use QuickBoot, but "adb reboot" works fine as well)
Enjoy!
I'll update more after work.
[hold]
Badass, thank you!
Sent from my VM670 using XDA App
What's the difference between this and the one posted on romrepo?
Sent from my LG-VM670 using Tapatalk
vegetajin8 said:
What's the difference between this and the one posted on romrepo?
Sent from my LG-VM670 using Tapatalk
Click to expand...
Click to collapse
Cant say 100% as I only used the recovery-thunderc-v-1.2.0-GNM.img recovery (Amon_RA based) once since I've had the OptV.
This is based on CWM source and the stock recovery kernel (for now)
which allows advanced restores etc.
The only other Recovery I see is CWMA which looks like a Xionia kernel and a Amon_Ra/ClockWorkMod hybrid recovery. I know nothing about that recovery, so be sure to try it out and see which you like best.
opcode1300 said:
Cant say 100% as I only used the recovery-thunderc-v-1.2.0-GNM.img recovery (Amon_RA based) once since I've had the OptV.
This is based on CWM source and the stock recovery kernel (for now)
which allows advanced restores etc.
The only other Recovery I see is CWMA which looks like a Xionia kernel and a Amon_Ra/ClockWorkMod hybrid recovery. I know nothing about that recovery, so be sure to try it out and see which you like best.
Click to expand...
Click to collapse
I've tried xionia I like it to a point that almost all roms will only work with it. I'm currently using 3.0.2.8 from rom repo for the v and like it better. Just wish everyone would use one recovery to develop their roms with.
Sent from my LG-VM670 using Tapatalk
I'm sorry, but I am having some trouble using the ADB. Where does the .zip file need to be when I type in all of these commands?
Whenever I try to type in the first command (mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system) in the ADB shell it says Operation not permitted. Anyone know how to get around it?
When in adb type su then the command see if that works.
Sent from my LG-VM670 using XDA Premium App
Why not just add terminal directions? much simpler
$ su
# cat /proc/mtd
identify recovery -mines mtd2 - & backup...
# cat /dev/mtd/mtd2 > /sdcard/recovery.img
place the recovery to be flashed on sdcard root (example.img)
# flash_image recovery /sdcard/example.img
I saw a clockwork recovery avalibale threw rom manager for the optimus v and would like to know if that's a stable recovery ?
Sent from my T-Mobile G2 using XDA App
arsonist63086 said:
I saw a clockwork recovery avalibale threw rom manager for the optimus v and would like to know if that's a stable recovery ?
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Depending on how new the OV is.
The newer OVs have a different screen and that recovery is not compatible
Sent via LG VM670 IHO
Someone explain recovery for me, is it basically a rom?
BOB DOLE
Recovery
omgpk said:
Someone explain recovery for me, is it basically a rom?
BOB DOLE
Click to expand...
Click to collapse
No its not a rom but what can be used to flash roms
Sent from my LG-P500 using XDA
Here is a dictionary link
omgpk said:
Someone explain recovery for me, is it basically a rom?
BOB DOLE
Click to expand...
Click to collapse
Here is some info on it.
http://forum.xda-developers.com/showthread.php?p=10377391#post10377391
Once you are on the page you can scroll up to the top to see the other information that is there.

[GUIDE]How to provide a logcat ![ATUALIZED]

Helping developers!
Learn how to provide a logcat the devs .....
By phone ...
Open the terminal emulator
type
Code:
su
# logcat > /sdcard/logcat.txt
The log will be on your sdcard.
By the computer (Windows) ....
Download the Qtabd
Link: http://motyczko.pl/qtadb/QtADB_0.8.1_windows.zip
Open qtabd, select where you extracted the package adb.
Connect the phone to the pc.
In qtabd select logcat.
Select all (ctrl + a)
Save to PC
continues
Provide logcat on Ubuntu
Qtabd 32 bits :http://motyczko.pl/qtadb/QtADB_0.8.1_linux32.tar.gz
Qtabd 64bits :http://motyczko.pl/qtadb/QtADB_0.8.1_linux64.tar.gz
Binaries ADB : http://motyczko.pl/qtadb/linux_binaries.tar.gz
Open terminal:
Code:
sudo apt-get install libqtgui4 libqt4-network libqt4-declarative
32 bits :
Code:
$ cd Downloads/linux_binaries/
$ sudo cp adb aapt /usr/bin/
$ cd /usr/bin/
$ sudo chmod +x adb aapt
New terminal
Code:
$ cd Downloads/QtADB_0.8.1_linux32
$ sudo cp QtADB /usr/bin/
$ cd /usr/bin/
$ sudo chmod +x QtADB
Now
Code:
$ sudo QTABD
Tell where are the binaries and enjoy!
Thnx sir
Very useful
sent using repencis 3.5 wid a2sd
press thnxxx
very nice guide......... also post about how to provide logcat using Android SDK ...........its good to know all new user how to use SDK
Sent from my GT-S6102 using Tapatalk 2
Sir i hope u upload the Terminal Emulator too....
Sent from my GT-S5360 using xda premium
it works well in my device.
Sent from my GT-S5360 using xda app-developers app
How do you provide logcat if phone dont boot??? For example you just flashed a fresh custom rom and it wont boot, how do you get logcat cause you cant even open terminal in phone to input those commands
Sent from my GT-S5360 using xda premium
thirdzcee said:
How do you provide logcat if phone dont boot??? For example you just flashed a fresh custom rom and it wont boot, how do you get logcat cause you cant even open terminal in phone to input those commands
Sent from my GT-S5360 using xda premium
Click to expand...
Click to collapse
using part Windows
using qtabd !!
Nice work, this should be good for the community. Sticked so that everyone will see it and learn how to do it.
whitexp said:
using part Windows
using qtabd !!
Click to expand...
Click to collapse
How about ubuntu? Cause im on ubuntu although i do have windows running from virtualbox but thats only for the rest of my family here cause they prefer windows and i prefer ubuntu ... its 64 bit ubuntu by the way.,. How to get logcat then?
Sent from my GT-S5360 using xda premium
atualized
whitexp said:
atualized
Click to expand...
Click to collapse
nice
its helpfull!
thirdzcee said:
How do you provide logcat if phone dont boot??? For example you just flashed a fresh custom rom and it wont boot, how do you get logcat cause you cant even open terminal in phone to input those commands
Click to expand...
Click to collapse
here is a method that worked for me.
1. Turn off your phone (if stuck, just remove the battery).
2. At your command prompt, do "adb logcat > logresult.txt".
3. Plug your phone to your usb and power it.
4. After at least 1-2 minutes or until the phone has fully booted up, terminate your logcat session (ctrl+c)
Click to expand...
Click to collapse
Can op or anyone add info how to read and analyst error from logcat??
Love You man...
whitexp said:
Helping developers!
Learn how to provide a logcat the devs .....
By phone ...
Open the terminal emulator
type
Code:
su
# logcat > /sdcard/logcat.txt
The log will be on your sdcard.
By the computer (Windows) ....
Download the Qtabd
Link: http://motyczko.pl/qtadb/QtADB_0.8.1_windows.zip
Open qtabd, select where you extracted the package adb.
Connect the phone to the pc.
In qtabd select logcat.
Select all (ctrl + a)
Save to PC
continues
Click to expand...
Click to collapse
Hey... Nice job... thanked already...
---------- Post added at 12:14 AM ---------- Previous post was at 12:03 AM ----------
Just wondering, can you also upload some tutorials on identifying common issues through logcat?
that would be great for me as i am not of comp sc background, yet want to positively help the devs and possibly someday dev some... B)
[I think some others are also thinking just what i am thinking... LOL]
hey man working great! thanks :good:
very useful thread, thank you
I might be wrong but cwm can generate logcat.....
Sent from my GT-S5360 using xda premium
alkesh95 said:
I might be wrong but cwm can generate logcat.....
Sent from my GT-S5360 using xda premium
Click to expand...
Click to collapse
Yes I think you are wrong.. It can show log generated during installation.. That too if the dev has written any "echo" commands.. It also generates some info like about any problem occurred while installation.. In advanced section has show log option..
hit thanks button! if above post helps u..
Sent from my GT-S6102
nitubhaskar said:
Yes I think you are wrong.. It can show log generated during installation.. That too if the dev has written any "echo" commands.. It also generates some info like about any problem occurred while installation.. In advanced section has show log option..
hit thanks button! if above post helps u..
Sent from my GT-S6102
Click to expand...
Click to collapse
Thanks buddy....
Sent from my GT-S5360 using xda premium

[Q] like someone seen this ever eror

Basic data of the machine are:
GT-N7100
AV: 4.1.2,
BB: N7100UBALJ1,
CWMRecovery-V6.0.1.9
I thought radio was the problem and the update from the menu and have given CWMRecovery dalvik ect format and it does not work if anyone knows please explain how to do it I will be very grateful
try to use another launcher.
btw i am not sure its the right place to ask...
Please follow the rules, don't post questions in the development section. Ask or report to forum moderator to move this post to the Q&A section.
one more thing I noticed, the product code was reset (000000)
boldman78 said:
try to use another launcher.
btw i am not sure its the right place to ask...
Click to expand...
Click to collapse
friend I've updated I've done everything and this error appearing sige
ediltoyo said:
friend I've updated I've done everything and this error appearing sige
Click to expand...
Click to collapse
0. Download a ROM and put it on external SD or computer.
1.Backup things you need to a computer
2. Flash TWRP recovery (Idk how to do it on CWM)
2.1 take off external SD (if u have one)
3. Go to wipe and format data and wipe everything. Everything..
4. Now you are left with a phone that has nothing at all..
4.1 return SD, restart TWRP
4.2 put the file from the computer to the device.
5. Flash a fresh ROM
6. now you gotta be fine.
Sent from my GT-N7100
ediltoyo said:
Basic data of the machine are:
GT-N7100
AV: 4.1.2,
BB: N7100UBALJ1,
CWMRecovery-V6.0.1.9
I thought radio was the problem and the update from the menu and have given CWMRecovery dalvik ect format and it does not work if anyone knows please explain how to do it I will be very grateful
Click to expand...
Click to collapse
It's related to a corrupt efs partition. Reflashing a rom or factory reset would not solve it.
Google for 'factory mode' to get the solution.
Sent from my GT-N7100 using xda premium
ediltoyo said:
Basic data of the machine are:
GT-N7100
AV: 4.1.2,
BB: N7100UBALJ1,
CWMRecovery-V6.0.1.9
I thought radio was the problem and the update from the menu and have given CWMRecovery dalvik ect format and it does not work if anyone knows please explain how to do it I will be very grateful
Click to expand...
Click to collapse
Your EFS is corrupted and your phone is now in Factory Mode. Use Terminal Emulator, which can be downloaded from the Google Play Store, and enter the following commands.
Open terminal emulator and type;
su
rm /efs/FactoryApp/keystr
rm /efs/FactoryApp/factorymode
echo -n ON >> /efs/FactoryApp/keystr
echo -n ON >> /efs/FactoryApp/factorymode
chown 1000.1000 /efs/FactoryApp/keystr
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/keystr
chmod 0744 /efs/FactoryApp/factorymode
reboot
I hope you have a backed up EFS image because you will need it.to replace the corrupted one. Find Dr.Ketan's posts for that.
Thread moved to Q&A, where it should be

Fix for note 2 if stuck in factory mode

1. I ODIN BACK TO STOCK WITH ROOT
2. DOWNLOADED TERMINAL EMULATOR
FOLLOW DIRECTIONS IN LINK WORKED GREAT
I THOUGHT I F***ED MY DEVICE TIL I FOUND THIS
http://www.444android.com/samsung-g...xy-note-ii-factory-mode-sorunu.html#post86539
Excellent...
Thank you, this is sure to help other users...g
taylormade772 said:
1. I ODIN BACK TO STOCK WITH ROOT
2. DOWNLOADED TERMINAL EMULATOR
FOLLOW DIRECTIONS IN LINK WORKED GREAT
I THOUGHT I F***ED MY DEVICE TIL I FOUND THIS
http://www.444android.com/samsung-g...xy-note-ii-factory-mode-sorunu.html#post86539
Click to expand...
Click to collapse
I tried all the other methods and suggestions. Finally I tried this one and it worked. The post is in another language, but the code works. Don't worry if terminal tells you bla bla bla not found, just keep typing in the next code. When you reboot, factory mode will be a thing of the past.
how this gonna work ? mind helping me out ?
Did you try pulling the battery? How do you know if you're stuck in factory mode?
You want have lock screen and a small box with system info will be on display
sent from Notetorious B.I.G.
Holy crap finally I'm out of this DAMN factory mode.. Nothing else worked!
I got in there initially by trying to repair my EFS partition.
Thank you thank you thank you.
I really appreciate the help here. I had a i605 that had that annoying Factory Mode box because I messed up my EFS folder with Root Explorer. Now at least I have a baseband and 000000000's for my ESN. Much appreciative to the developers who share their knowledge with us.
FIX for getting out out of Factory Mode-Must be rooted
Might as well post the fix since it does work.
From terminal emulator or adb shell
su
rm /efs/FactoryApp/keystr
rm /efs/FactoryApp/factorymode
echo -n ON >> /efs/FactoryApp/keystr
echo -n ON >> /efs/FactoryApp/factorymode
chown 1000.1000 /efs/FactoryApp/keystr
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/keystr
chmod 0744 /efs/FactoryApp/factorymode
reboot
Also located here, on XDA. What a coincidence
http://forum.xda-developers.com/showpost.php?p=42794146&postcount=1
To cut down on errors you can copy-paste these commands into the terminal emulator.
rangercaptain said:
To cut down on errors you can copy-paste these commands into the terminal emulator.
Click to expand...
Click to collapse
Excellent suggestion. Factory mode is an inconvenience, but repairable. Hosing up your /efs,4 and without a backup. Painful.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
"Permission denied"
rangercaptain said:
To cut down on errors you can copy-paste these commands into the terminal emulator.
Click to expand...
Click to collapse
But how can i change permissions in the terminal. On every command is answering with "Permission denied"?
Tnx in advance for your answer.
zupanoski said:
But how can i change permissions in the terminal. On every command is answering with "Permission denied"?
Tnx in advance for your answer.
Click to expand...
Click to collapse
You need to be root. Type su, approve the root request when the message pops up.
If you phone is not rooted, then you need to root it.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

[Q&A] How to Root KVT49L.D85110r and Install TWRP. My experience

Q&A for How to Root KVT49L.D85110r and Install TWRP. My experience
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for How to Root KVT49L.D85110r and Install TWRP. My experience. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
This worked fantastic for me!
Perfect guide to fix the root problem on the 10r! Great work on the guide!
thanks
really didn't want to downgrade to previous version. this worked great. awesome detailed instructions. thank you so much for this thread.
With this do you lose all your data?
not working
ALL IS FINE UNTIL I GET TO THIS STEP IN THE LINK:
- Type "ls /temp" to make sure that recovery.img and fakesu are in /temp folder . If it is not, then you did not complete correctly the above instructions..repeat it
AT THIS POINT I AM GETTING "NOT FOUND". DID THE STEPS ABOVE SEVERAL TIMES.
================================================== ========================================
C:\Users\nick\Downloads\ADB LOCAL READY>c:\windows\system32\cmd.exe
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\nick\Downloads\ADB LOCAL READY>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
LGD851xxxxxxxx recovery
C:\Users\nick\Downloads\ADB LOCAL READY>adb push recovery.img /temp
9716 KB/s (11245568 bytes in 1.130s)
C:\Users\nick\Downloads\ADB LOCAL READY>adb shell
[email protected]:/ $ /temp/fakesu
/temp/fakesu
# Is /temp
Is /temp
/temp/fakesu: Is: not found
#
================================================== =======================================
christian2399 said:
With this do you lose all your data?
Click to expand...
Click to collapse
no, you will not
---------- Post added at 07:37 PM ---------- Previous post was at 07:31 PM ----------
sharkoparko said:
ALL IS FINE UNTIL I GET TO THIS STEP IN THE LINK:
- Type "ls /temp" to make sure that recovery.img and fakesu are in /temp folder . If it is not, then you did not complete correctly the above instructions..repeat it
Click to expand...
Click to collapse
I responded in the main thread
ls /temp on su command # , it is just to confirm that recovery.img image and fakesu files were pushed to the temp folder
. You should check that both are there and continue to step 13
can you tell me what you mean by push through recovery im a nube and i dont know how to do that causethat same command isnt working for me
The TWRP recovery is pushed into your device /temp folder on step 9 and it is installed in your device with the comands in step 13.
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
hey Im having that same problem
dd if=/temp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery that command isnt working and i wanted to know if anyone can help me get around this??
Not working for me - see output
PurpleDrake doesn't appear to be able to get temp root. Any ideas on where to go from here?
Launching PurpleDrake for OSX
Welcome to PurpleDrake!
Please ensure your phone is connected, powered on, and USB debugging is properly enabled.
Your phone should be showing your homescreen with no other apps open. This is to ensure a clean state.
When you're ready, press [enter]...
Press [enter] to continue...
Waiting for device... ....
.... Found device!
Your phone is a [ LG-D851 ] on [ TMO ] running SW version [ V10r ] ...
Alright. We're ready to go. We're going to temproot your phone first. Press enter when you're ready!
Press [enter] to continue...
Rebooting phone...
Waiting for device... .. Found device!
Found device, checking if vulnerable...
Yep, performing temproot...
Waiting for system to settle...
ERROR: Something went wrong. FakeSU didn't work, rebooting phone.
Debug information - 'ls -l /temp/fakesu':
/temp/fakesu: No such file or directory
------------------------
We tried to temproot you, and it didn't work. This phone isn't vulnerable, it would appear.
Please post on XDA with your phone model, carrier, and SW version in the PurpleDrake thread and someone will take a look.
Your phone has been rebooted back to normal system mode, no changes have been made. Thanks for trying!
logout
---------- Post added at 01:09 AM ---------- Previous post was at 12:56 AM ----------
phpthug said:
PurpleDrake doesn't appear to be able to get temp root. Any ideas on where to go from here?
Launching PurpleDrake for OSX
Welcome to PurpleDrake!
Please ensure your phone is connected, powered on, and USB debugging is properly enabled.
Your phone should be showing your homescreen with no other apps open. This is to ensure a clean state.
When you're ready, press [enter]...
Press [enter] to continue...
Waiting for device... ....
.... Found device!
Your phone is a [ LG-D851 ] on [ TMO ] running SW version [ V10r ] ...
Alright. We're ready to go. We're going to temproot your phone first. Press enter when you're ready!
Press [enter] to continue...
Rebooting phone...
Waiting for device... .. Found device!
Found device, checking if vulnerable...
Yep, performing temproot...
Waiting for system to settle...
ERROR: Something went wrong. FakeSU didn't work, rebooting phone.
Debug information - 'ls -l /temp/fakesu':
/temp/fakesu: No such file or directory
------------------------
We tried to temproot you, and it didn't work. This phone isn't vulnerable, it would appear.
Please post on XDA with your phone model, carrier, and SW version in the PurpleDrake thread and someone will take a look.
Your phone has been rebooted back to normal system mode, no changes have been made. Thanks for trying!
logout
Click to expand...
Click to collapse
So, I apparently already had TWRP installed as the recovery somehow of this device, so I just had to flash the SU zip from it and all is good. Thanks!
christian2399 said:
hey Im having that same problem
dd if=/temp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery that command isnt working and i wanted to know if anyone can help me get around this??
Click to expand...
Click to collapse
1- make sure that device is recognized , if not unplug it and plug it back on
2- make sure that you apply this dd command when you are on # su command
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
vcurbel said:
1- make sure that device is recognized , if not unplug it and plug it back on
2- make sure that you apply this dd command when you are on # su command
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
Click to expand...
Click to collapse
I did do all that correctly but still for some reason it says file cannot be found everything works until that step please help me i want my root back!
christian2399 said:
I did do all that correctly but still for some reason it says file cannot be found everything works until that step please help me i want my root back!
Click to expand...
Click to collapse
Did you do the ls/temp on su # command? It will give you all files on the /temp folder. If you do not see the twrp recovery.img there.. it means that the recovery.img was not pushed into the /temp folder on step 8.
Another question? What do you mean about that you want you root back? Do you have root before? Do you a custom recovery before?IS IT TWRP? If so ...it is easy...just move the updatesupersu2.40.zip file to you sdcard and install it in your custom recovery
Sent from my LG-D851 using XDA Free mobile app
vcurbel said:
Did you do the ls/temp on su # command? It will give you all files on the /temp folder. If you do not see the twrp recovery.img there.. it means that the recovery.img was not pushed into the /temp folder on step 8.
Sent from my LG-D851 using XDA Free mobile app
Click to expand...
Click to collapse
look this iswhat im getting
christian2399 said:
look this iswhat im getting
Click to expand...
Click to collapse
Yea...as you can see recovery file is not in you temp folder.....you need to go back to step 8 and push it
Sent from my LG-D851 using XDA Free mobile app
Worked for me!!
Glad I stumbled on this thread. It worked for me. I did have to move the recovery.img twice (it didn't move the first time). But I was able to check that it was not there with the ls. Thanks for this tutorial! Appreciated.
You all did it the hard and complicated way. You should have just followed the instructions in this thread
http://forum.xda-developers.com/showthread.php?t=2961261
It how I updated both my phone and my wife's phone when the update came out last month and it took less than a minute
Thanks
I'm glad I found a way for this to work
truckerdewd said:
You all did it the hard and complicated way. You should have just followed the instructions in this thread
http://forum.xda-developers.com/showthread.php?t=2961261
It how I updated both my phone and my wife's phone when the update came out last month and it took less than a minute
Click to expand...
Click to collapse
This thread is not about to install the R update. It is to root it and to install twrp custom recovery
Sent from my LG-D851 using XDA Free mobile app
vcurbel said:
This thread is not about to install the R update. It is to root it and to install twrp custom recovery
Sent from my LG-D851 using XDA Free mobile app
Click to expand...
Click to collapse
Wrong. If you read, it has everything needed to update to to the R update and root it. This is the exact sane thread I used to update both my phone and my wife's phone.

Categories

Resources