Related
this from rad131304 not me, thank you
Windows 7 Sideload Instructions
Hope this helps some people - I tried to be very step-by-step about it.
Again, thank you Pokey9000, the guys and gals from the IRC channel, and everybody else for all of your hard work! 99.9% of this is an aggregation of what is already in this thread; some of it comes from nookdevs also.
You will need the following applications on your Windows 7 computer:
- cygwin (www dot cygwin dot com)
- Android Debug Bridge (ADB) - this comes with the android SDK
- Android USB Drivers - this comes with the android SDK
-- (WOQ) stands for without quotes, it means that I am giving you something between quotes to copy and paste.
-- if you see <some_odd_name> inside quotes, it means you MUST replace this with something from your specific OS instance (e.g. a drive letter, or something)
1. make sure your NC is disconnected from you computer
2. make sure your SD card is mounted on your computer (readable/browsable in explorer)
3. Install cygwin - you only need the base install AFAICT (YMMV), don't worry about the options for now.
4. download nooter at http //www dot mediafire dot com/?hugt8uxcfffpdvg
5. extract the contents to a folder in your cygwin install (standard install path is c:\cygwin)
6. Go to: Start, type in (WOQ) "compmgmt.msc" - this may require UAC elevation
7. Select "Disk Management" under storage
8. note the drive letter of the SD card and the disk number
9. Go To: Start > All Programs > Cygwin > Cygwin Bash Shell
10. At the prompt, type (WOQ): "mount //./<f>: /dev/sd<c>"
Where <f> is your drive letter, and
<c> is the letter you would get if you zero-indexed the disk number into the alphabet (i.e. 0 = a, 1 = b) **
11. press enter - there should be no output
12. at the prompt, type (WOQ): "dd if=<path_to_nooter_from_cygwin_install_folder>/nooter_sdcard_40MB.img of=/dev/sd<c>"
It will sit at this for a few minutes seeming to do nothing, be patient; you should get a response eventually that looks like:
80326+0 records in
80326+0 records out
41126912 bytes (41 MB) copied, 174.525 s, 236 kB/s
13. remove the sd card from the computer and plug it into the NC
14. power down the NC (hold power button for 15 seconds)
15. connect the NC to the computer
16. Wait for a "Composite Device" to be recognized by Windows and fail to install drivers
17. Wait for 15 seconds after the recognition
18. power down the NC
19. remove SD card ***
20. Find your android_winusb.inf file - this is located in your android-sdk install directory in the usb_driver folder. (NOTE: if you installed this in the program files folder, you will need to UAC elevate your editor to edit this file)
21. Paste the following lines into the file below both occurrences of the line ";Moto Sholes" after the ADBInterface definitions:
;B & N Nook Color
%SingleAdbInterface% = USB_Install, USB\VID_2080&PID_0002
%CompositeAdbInterface% = USB_Install, USB\VID_2080&PID_0002&MI_01
22. save the file and close
23. find your adb_usb.ini file - it is usually located in c:\users\<username>\.android\
24. add (WOQ) "0x2080" on its own line
25. power on NC - at this point, the NC should boot normally, but ADB won't be able to recognize it
26. Go To: Start > Devices and Printers
27. Right-click on Nook and select properties
28. Select the hardware tab
29. If you have something that says "Nook" and has a yellow yield sign with a "!", then continue, if not skip to 38
30. Click on "Nook"
31. Select Properties
32. Click Change Settings (may require UAC elevation)
33. Click update driver
34. Select "browse for driver software on your computer"
35. Browse to the android-sdk/usb_driver folder
36. click next
37. You should be done; skip to 47 (I have no idea if this is correct - i pieced it together from somewhere in this as I did not get Nook to appear in the Device Functions List)
38. If you don't have a "Nook" Device Function, click on "USB Mass Storage Device"
39. Select Properties
40. Click Change Settings (may require UAC elevation)
41. Select the Driver Tab
42. Click Uninstall
43. Click OK
44. Disconnect NC
45. Reconnect NC
46. You should be done (this is different from my previous instructions on how to uninstall the NC USB drivers, I have not tested it so YMMV)
47. Go To: start > run > cmd
48. type (WOQ): "cd <path_to_android_sdk>\tools"
49. type (WOQ): "adb.exe kill-server"
You should get something like:
* server not running *
50. type (WOQ): "adb.exe remount"
You should get something like:
* daemon not running. starting it now *
* daemon started successfully *
remount failed: No such file or directory
51. You are done configuring to sideload
From here you should be able to sideload from ADB.
by rad131304
Just to throw it out there...
Does this cause a PERMANENT change to the Color Nook?
Edit: thank you for posting this
I believe it was mentioned in a previous post that if you did a factory reset (power off completely, then hold power, nook button and vol up) that it would reset the Nook back to non rooted factory defaults. Can anyone else confirm this?
HeroHTC said:
Just to throw it out there...
Does this cause a PERMANENT change to the Color Nook?
Edit: thank you for posting this
Click to expand...
Click to collapse
Are these instructions for Win 7 64 or 32 bit?
BTW, how does one go back or to menu without those buttons?
RichTJ99 said:
Are these instructions for Win 7 64 or 32 bit?
BTW, how does one go back or to menu without those buttons?
Click to expand...
Click to collapse
believe this was done on win 64, some buttons are located in or below menu bar, some will depend on launcher.
I also wanted to mention this
http://forum.xda-developers.com/showpost.php?p=9517050&postcount=863
NOTE: I have not even opened my nook box yet, its still sealed but I am getting ready. Just waiting on an email solution.
Do you think a partitioned SD card woul dprevent this from working?
I'm pretty sure my card is partitioned....I read something in the BIG THREAD about departitioning a card.....
I can't get this to work for me and I just thought my card might be the culprit.
Thanks
I cannot find the file listed in step 23. This is the only thing keeping me from root. Also when I plug my nc in, the light on the cord is amber instead of green. It tells me that adb drivers are installed. But it won't show up as a folder in my computer any more. How do I add files without removing the SD card and plugging it into my computer.
Sent from my HERO200 using XDA App
RichTJ99 said:
Are these instructions for Win 7 64 or 32 bit?
BTW, how does one go back or to menu without those buttons?
Click to expand...
Click to collapse
I did this on 32 bit - AFAIK, they don't support cygwin on 64 bit yet (it might run though, but YMMV).
The back and menu buttons are soft-buttons. The nook for some reason hides them by default in a bunch of apps.
sudermatt said:
Do you think a partitioned SD card woul dprevent this from working?
I'm pretty sure my card is partitioned....I read something in the BIG THREAD about departitioning a card.....
I can't get this to work for me and I just thought my card might be the culprit.
Thanks
Click to expand...
Click to collapse
IIRC, somebody said that in the big thread, too.
oakleyrdc said:
I cannot find the file listed in step 23. This is the only thing keeping me from root. Also when I plug my nc in, the light on the cord is amber instead of green. It tells me that adb drivers are installed. But it won't show up as a folder in my computer any more. How do I add files without removing the SD card and plugging it into my computer.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
It could be hidden (so you'll have to change the hidden files and folders setting), or installed in another user directory (like Admin).
If I run Windows XP, how many of these steps would change? I'm thinking it might need its own thread.
I did mine on Win 64bit using winimage. Everything is working fine.
rad131304 said:
I did this on 32 bit - AFAIK, they don't support cygwin on 64 bit yet (it might run though, but YMMV).
Click to expand...
Click to collapse
XP
cabbieBot said:
If I run Windows XP, how many of these steps would change? I'm thinking it might need its own thread.
Click to expand...
Click to collapse
plus 1 for XP
So once your rooted, do you need to do anything special to install apk files that you download from dropbox? Is superuser ready?
i cant find the android_winusb file in the windows XP version of the android SDK. is there a different one that does the same?
EDIT: it appears the sdk is not split between versions of windows
im going to reinstall the sdk and see maybe if i accidently deleted it at some point
cabbieBot said:
If I run Windows XP, how many of these steps would change? I'm thinking it might need its own thread.
Click to expand...
Click to collapse
Very little changes; the only thing I can tell you off the top of my head is that
C:\users\<username>\.android\
Becomes
C:\documents and settings\<username>\.android\
Also, I don't know where, besides device manager, that you could locate the nook like you do in devices and printers - it may show up in my computer, also in scanners and cameras in the control panel - you can always right click a drive, select properties, select the hardware tab, select the b&n storage device, click properties, select the driver tab and uninstall from there....
HTH
EDIT: To delete the NC through device manager:
start > run > compmgmt.msc
browse to Device Manager
Expand Universal Serial Bus Controllers
Select USB Mass Storage Device (there may be multiple)
Right-Click and select "properties"
select the details tab
in the dropdown, select "Hardware Ids" - if this says "USB\VID_2080&...." then this is the NC
click ok
right Click again and select uninstall
disconnect NC from computer
reconnect NC to computer
NC re-finds all drivers, including ADB
start > run > cmd
cd <android-sdk-dir>\tools
adb.exe remount
Fixed instructions!
that's what I get for writing this crap at 1 in the AM ... I left out two INSANELY important steps at step 11.
SORRY!!!!
Windows 7 Sideload Instructions
Hope this helps some people - I tried to be very step-by-step about it.
Again, thank you Pokey9000, the guys and gals from the IRC channel, and everybody else for all of your hard work! 99.9% of this is an aggregation of what is already in this thread; some of it comes from nookdevs also.
You will need the following applications on your Windows 7 computer:
- cygwin (http://www.cygwin.com)
- Android Debug Bridge (ADB) - this comes with the android SDK
- Android USB Drivers - this comes with the android SDK
-- (WOQ) stands for without quotes, it means that I am giving you something between quotes to copy and paste.
-- if you see <some_odd_name> inside quotes or a code block, it means you MUST replace this with something from your specific OS instance (e.g. a drive letter, or something)
make sure your NC is disconnected from you computer
make sure your SD card is mounted on your computer (readable/browsable in explorer)
Install cygwin - you only need the base install AFAICT (YMMV), don't worry about the options for now.
download nooter at http://www.mediafire.com/?hugt8uxcfffpdvg
extract the contents to a folder in your cygwin install (standard install path is c:\cygwin)
Go to: Start, type in (WOQ) "compmgmt.msc" - this may require UAC elevation
Select "Disk Management" under storage
note the drive letter of the SD card and the disk number
Go To: Start > All Programs > Cygwin > Cygwin Bash Shell
At the prompt, type:
Code:
mount //./<f>: /dev/sd<c>
Where <f> is your drive letter, and
<c> is the letter you would get if you zero-indexed the disk number into the alphabet (i.e. 0 = a, 1 = b) **
press enter - there should be no output
REMOVE SD CARD FROM PC
INSERT SD CARD INTO PC
at the prompt, type:
Code:
dd if=<path_to_nooter_from_cygwin_install_folder>/nooter_sdcard_40MB.img of=/dev/sd<c>
It will sit at this for a few minutes seeming to do nothing, be patient; you should get a response eventually that looks like:
80326+0 records in
80326+0 records out
41126912 bytes (41 MB) copied, 174.525 s, 236 kB/s
Click to expand...
Click to collapse
IF THIS COMPLETES ALMOST IMMEDIATELY, YOU PROBABLY HAVE AN ERROR
remove the sd card from the computer and plug it into the NC
power down the NC (hold power button for 15 seconds)
connect the NC to the computer
Wait for a "Composite Device" to be recognized by Windows and fail to install drivers
Wait for 15 seconds after the recognition
power down the NC
remove SD card ***
Find your android_winusb.inf file - this is located in your android-sdk install directory in the usb_driver folder. (NOTE: if you installed this in the program files folder, you will need to UAC elevate your editor to edit this file)
Paste the following lines into the file below both occurrences of the line ";Moto Sholes" after the ADBInterface definitions:
Code:
;B & N Nook Color
%SingleAdbInterface% = USB_Install, USB\VID_2080&PID_0002
%CompositeAdbInterface% = USB_Install, USB\VID_2080&PID_0002&MI_01
save the file and close
find your adb_usb.ini file - it is usually located in c:\users\<username>\.android\
add (WOQ) "0x2080" on its own line
power on NC - at this point, the NC should boot normally, but ADB won't be able to recognize it
Go To: Start > Devices and Printers
Right-click on Nook and select properties
Select the hardware tab
If you have something that says "Nook" and has a yellow yield sign with a "!", then continue, if not skip to 40
Click on "Nook"
Select Properties
Click Change Settings (may require UAC elevation)
Click update driver
Select "browse for driver software on your computer"
Browse to the android-sdk/usb_driver folder
click next
You should be done; skip to 49 (I have no idea if this is correct - i pieced it together from somewhere in this as I did not get Nook to appear in the Device Functions List)
If you don't have a "Nook" Device Function, click on "USB Mass Storage Device"
Select Properties
Click Change Settings (may require UAC elevation)
Select the Driver Tab
Click Uninstall
Click OK
Disconnect NC
Reconnect NC
You should be done (this is different from my previous instructions on how to uninstall the NC USB drivers, I have not tested it so YMMV)
Go To: start > run > cmd
type:
Code:
cd <path_to_android_sdk>\tools
./adb.exe kill-server
You should get something like:
* server not running *
Click to expand...
Click to collapse
if adb.exe is not in tools (or tools does not exist), try:
Code:
cd <path_to_android_sdk>\platform-tools
./adb.exe kill-server
type:
Code:
./adb.exe remount
You should get something like:
* daemon not running. starting it now *
* daemon started successfully *
remount failed: No such file or directory
Click to expand...
Click to collapse
You are done configuring to sideload
From here you should be able to sideload from ADB.
To sideload an app, simply do the following:
Code:
./adb.exe install <app_name>
Thanks Rad!
im going insane, ive completely updated the SDK but i cant find this damn android_winusb file
When you updated the SDK, did you install the USB drivers also? If you did, that file should be in whatever directory you installed the SDK in under the usb_driver subdirectory.
cabbieBot said:
im going insane, ive completely updated the SDK but i cant find this damn android_winusb file
Click to expand...
Click to collapse
I'm an idiot, I was certain the USB Drivers were installed. Done and done now, sheesh what a waste of time!
now to hunt for adb_usb which is being a pain to find too. Has anyone found adb_usb on XP?
I can see the folder C:\documents and settings\<username>\.android\ but theres two folders in there for AVD and AndroidDesktopNotifier. Maybe if someone can upload the adb_usb file I can just throw it in the folder and cross my fingers?
TUTORIAL ON ADB AND LOGCAT : JDMC : Just doing my contribution.
This is part of TeamAscend, so if you are going to post this Tutorial on other forums please credit me, visit our website : I AM AWESOME!
Hello this is just to teach newbie users on how to install adb and get it working, I will also teach you how to use logcat to help devs with particular issues, okay lets get into it, I will try to be as formal and understandable is I can, I'm still a 15 year old so bare with my written language, not that its bad but we Kiwi's use weird slangs...
Setting up ADB
1. Okay first of all we need to enable Android debugging.
1a. To do so, head into Settings > development and check android debugging, If you're on CM10 + you will need to set Developer Options to "ON" then select Android Debugging.
2. Get a usb adapter and connect it to your pc and connect your device. Let it install drivers "If it's the first time.
3. Download "SDK Tools". and install it to your desktop for now, you can move it later when you want.
4. Now create a new folder on the desktop and copy all SDK contents into it so its neat and tidy.
5. Open "SDK Manager" and un-check everything except "Android SDK Platform-Tools" and click install packages, wait till it's done then close the window, now you should be in the folder that contains the SDK Tools etc... if you see the "platform-tools" folder you're good to go.
6. Now open the "platform-tools" folder and copy the destination output at the top.
7. Now we need to set the new destination to CMD, click the start button type "cmd".
8. When it opens type "cd" obviously without the ", now hit space and click paste now your command should look something like this...
"cd C:\Users\Your PC name\Desktop\the folder that contains the sdk tools name\platform-tools" here's mine : "cd C:\Users\Lenovo\Desktop\ADB\platform-tools". Now hit enter, your target folder will change.
9. Once its done type " adb devices", make sure your phone is connected! now hit enter and it'll show your device, now you know ADB Is up and running! If doesn't show your device continue to the next step, if it does continue from step "11".
10. Download the HTC drivers and install it, plug your phone again and wait for it to install all components, if MTP fails to install just ignore it. (If your storage is on MTP), now repeat the procedure from "7" again.
11. Now lets Logcat, Now there are 2 different approaches to the logcat, I will be showing you how to do both in this tutorial. Neither one is more correct than the other, it is 100% personal preference. Feel free to try both and see where you get.
LOGCAT PROCEDURE
Doing logcat from inside the CMD window.
1. Make sure your phone is plugged in and debugging is on, now repeat procedure "7" to set target folder if it isn't already done. ie : cd _____________________________ <-- your folder destination.
2. Type "adb logcat" without the " and hit enter. It will then print a list of random writing, whether you understand or not, it doesn't matter, it's not for your use .
3. To save the logcat for devs to use, once the logcat is running, please RECREATE the bug/issue you are having. so that it logs the error into it, now to stop the logcat hit "ctrl" + "C".
4. Once this is done please RIGHT CLICK choose "Select All" then press "Enter" on your keyboard this will copy the entire log to the clipboard. You can then paste it into a .txt file to upload and show to devs.
Doing logcat to text file.
1. Now repeat procedure "7" to set target folder if it isn't already done, make sure your phone is plugged in and usb debugging mode is enabled. Once this is done we are going to type the following command "adb logcat > logcat.txt" without the ", this should initiate the logcat, it will appear as though nothing is happening, this is correct!!! So don't worry.
2. Once the logcat is running, please RECREATE the bug/issue you are having. To stop the logcat on your keyboard press "ctrl" + "C".
3. Now you've done logging, note the logcat.txt file will be located in the platform-tools folder, just open it and you will see logcat.txt, upload it for the dev and he/she will investigate.
More ADB Commands for various logcats Thanks to "Tcpaulh" from Modaco.
External adb folder, just needed thanks man : Download
1. radio logcat for Wifi issues.
adb logcat -b radio > radiolog.txt
2. kernel logs.
adb shell
su
cat /proc/kmsg > /sdcard/kmsg.txt
exit
adb pull /sdcard/kmsg.txt
3. kernel message buffer (on request).
adb shell
dmesg > /sdcard/dmesg.txt
exit
adb pull /sdcard/dmesg.txt
This was a tutorial I wrote up for my old device, users found it easier to understand then most, I cleaned this one up a bit which should be suitable for the Desire X, note, I may ask allot of question like a noob on the Q & A but HTC is so confusing.
Hopefully, users start using this so we can help out our devs, our sweet sweet devs, so they can whip u some magic.
If this helped, hit the thanks meter, no need for donations.
Model Number Moto E (2nd Generation) with 4G LTE
Hardware SKU
XT1527
Android version 5.1
Andriod security patch level
2016-04-01
Build Number
LPIS23 29-18.9-2
by pass google and now in setting but build number no work by pressing can't open developer plz help someone
No One Knows !
I have solution
Mod Edit
My services are not required here
help plzzz
please help me, I have no way to pay you, I have no credi card, but I really need to have this phone ...
wrong place
This section is for Moto E first gen (condor) not for Moto e second gen (surnia).
iazmatkhan said:
Model Number Moto E (2nd Generation) with 4G LTE
Hardware SKU
XT1527
Android version 5.1
Andriod security patch level
2016-04-01
Build Number
LPIS23 29-18.9-2
by pass google and now in setting but build number no work by pressing can't open developer plz help someone
Click to expand...
Click to collapse
Take my skype i give you solution
Arsalan.shahab1
desirlowens said:
please help me, I have no way to pay you, I have no credi card, but I really need to have this phone ...
Click to expand...
Click to collapse
add me on skype:
arsalan.shahab1
This model of AT & T version 5.1 does not allow unlock bootloader
It not allowed to also upload version 6.0 for retail and still has not left the AT & T version.
Test dpc does not work for this security because itis not gives the option of encryption as Owner.
ByPass:
1. Playing in email and keep pressed the @ until a menu of options.
2. keyboard settings Google
3. orthographic / staff / Dictionary correction for all languages
4. On the next screen tap the magnifying glass and press the letter "c". Several options were deployed and there
Google Pinyin Input to choose. On the next screen we chose the same option.
5. Then choose "about" Open Source Licenses"
6. On the next screen may maintain finger pressing and the option will appear
"Share" to choose "messages" typing 112 and send. At that time the call keyboard appears
delete 112 and type * # * # 4636 # * # *
7. On the next screen you can choose info or battery usage statistics.
8. Then go to back with the arrow on the top left
9. ByPass done.
10. Here you can not enable the developer and we can not restore option. It's just bypass
---------- Post added at 01:34 AM ---------- Previous post was at 01:24 AM ----------
Process FRP
Download four app
Aptoide
Es fileExplorer
Kingo Root
Terminal Emulator
The accecibilidad this phone is very poor so that the process is as follows:
1. In the menu go to Use data / You Tube / Application Settings / About
2. chose Google Privacy Policy
3. Open Google Chrome and from there download each of the applications but do not open.
4. Then return to the phone menu with the option "back"
5. We will install fromStorage File Explorer and open it
6. From the File Explorer install the other three applications
7. Open Aptoide and install the Nova Launcher, open and see the phone menu
8. Execute Kingo Root and Root and wait to tell you Done
9. Let back and look for the Terminal Emulator, enter and type "SU" to give us the option
root access #
10. Write in the amulador the following command:
content insert --uri content://settings / secure --bind name: s: user_setup_complete --bind value: s: 1
11. After that go back out from terminal emulator. Enable developer and OEM Unlockif not does not imortant.
12. Go to account and fill your own google account. The phone let you fil up.
13 Very importante do no delete the phone
14. Restart the phone and when start again you can enter your own google account. Then delete the phone.
15. Done. Credits: arsalrock55
---------- Post added at 01:38 AM ---------- Previous post was at 01:34 AM ----------
Note:
You can add the app Multi Windows that offers a fast accessibility when the process fails and you have not to do all the ByPass again butI had problems with this app.
He also clarified that does not always go in the first time is because the root with Kingo Root maybe you have to do many times.
I hope you serve the process.
Tested 100%
Hallo....
arsalrock55 said:
Mod Edit
My services are not required here
Click to expand...
Click to collapse
Cual es la solucion?
Cannot Open File
At number 5 of the process, I get a (Cannot open file message) on any apk. do you know why?
ByPass:
1. Playing in email and keep pressed the @ until a menu of options.
2. keyboard settings Google
3. orthographic / staff / Dictionary correction for all languages
4. On the next screen tap the magnifying glass and press the letter "c". Several options were deployed and there
Google Pinyin Input to choose. On the next screen we chose the same option.
5. Then choose "about" Open Source Licenses"
6. On the next screen may maintain finger pressing and the option will appear
"Share" to choose "messages" typing 112 and send. At that time the call keyboard appears
delete 112 and type * # * # 4636 # * # *
7. On the next screen you can choose info or battery usage statistics.
8. Then go to back with the arrow on the top left
9. ByPass done.
10. Here you can not enable the developer and we can not restore option. It's just bypass
---------- Post added at 01:34 AM ---------- Previous post was at 01:24 AM ----------
Process FRP
Download four app
Aptoide
Es fileExplorer
Kingo Root
Terminal Emulator
The accecibilidad this phone is very poor so that the process is as follows:
1. In the menu go to Use data / You Tube / Application Settings / About
2. chose Google Privacy Policy
3. Open Google Chrome and from there download each of the applications but do not open.
4. Then return to the phone menu with the option "back"
5. We will install fromStorage File Explorer and open it
6. From the File Explorer install the other three applications
7. Open Aptoide and install the Nova Launcher, open and see the phone menu
8. Execute Kingo Root and Root and wait to tell you Done
9. Let back and look for the Terminal Emulator, enter and type "SU" to give us the option
root access #
10. Write in the amulador the following command:
content insert --uri content://settings / secure --bind name: s: user_setup_complete --bind value: s: 1
11. After that go back out from terminal emulator. Enable developer and OEM Unlockif not does not imortant.
12. Go to account and fill your own google account. The phone let you fil up.
13 Very importante do no delete the phone
14. Restart the phone and when start again you can enter your own google account. Then delete the phone.
15. Done. Credits: arsalrock55
---------- Post added at 01:38 AM ---------- Previous post was at 01:34 AM ----------
Note:
You can add the app Multi Windows that offers a fast accessibility when the process fails and you have not to do all the ByPass again butI had problems with this app.
He also clarified that does not always go in the first time is because the root with Kingo Root maybe you have to do many times.
I hope you serve the process.
Tested 100%[/QUOTE]
root moto e
Greetings you can become root to motorola e second generation of at & t.
I'd appreciate your help
iazmatkhan said:
Model Number Moto E (2nd Generation) with 4G LTE
Hardware SKU
XT1527
Android version 5.1
Andriod security patch level
2016-04-01
Build Number
LPIS23 29-18.9-2
by pass google and now in setting but build number no work by pressing can't open developer plz help someone
Click to expand...
Click to collapse
1. Charge phone up to 100%, keep charger connected.and make sure you insert a correct working sim card.
2. Start the phone, connect to WiFi, get to the last screen (input Google email) and press on text input and
open Google keyboard settings (long press @ on bottom left).
3. press Google keyboard settings, and select Languages, Deselect `use system language` and scroll down to activate
Vietnamese.
4. Go back to the screen whereby the phone is asking for your email address, pop up the keyboard and
press and hold the Globe symbol near the `@` a tab will pop out showing `Change keyboard` ,select `Google voice typing`
5. you will see a keyboard emoji at your down right, click on it and select choose keyboards,after that activate
`Google pinyin input and iwnn IME` go back and press and hold `@` key and select google keyboard settings and choose Text
correction
6. choose personal dictionary and tap on `for all languge` click on the magnifier glass,type `C` scroll down and select
Google pinyin input and select the same option,select about and click open source licenses,select a text and click on
the share option and choose messaging
Send the composed message to emergency number 112
7. Press the phone icon that just appeared on the top right part of the screen
8. Delete 112 from number selection and input *#*#4636#*#*
9. In the opened window chose 'Usage statistics' and press back arrow on the TOP of the screen, not bottom!
10. You are now in the phone's settings
11. Go to About in settings
12. enable debugging mode
12. Use miracle box to remove frp using adb Tab
It works 100% search in youtube: Bypass Google account moto E 2nd gen Android 5 1
Link
Video solution here https://www.youtube.com/watch?v=UUnOiJolKHI
NB: I edited some of the instruction above as some sections were wrong or hard to understand. You still have to muddle through to get a proper understanding. My model was AT&T version 5.1
This model of AT & T version 5.1 does not allow unlock bootloader
It not allowed to also upload version 6.0 for retail and still has not left the AT & T version.
Test dpc does not work for this security because it does not give the option of encryption as Owner.
ByPass:
1. Playing in email and keep pressed the @ until a menu of options.
2. keyboard settings Google
3. orthographic (text correction / staff(personal dictionary) / Dictionary correction for all languages
4. On the next screen tap the magnifying glass and press the letter "c". Several options were deployed and there
Google Pinyin Input to choose. On the next screen, we chose "google hindu input".
5. Then choose "about" Open Source Licenses"
6. On the next screen may maintain finger pressing and the option will appear
"Share" to choose "messages" typing 112 and send. At that time the telephone icon appears
select telephone icon
delete 112 and type * # * # 4636 # * # *
7. On the next screen you can choose info or battery usage statistics.
8. Then go to back with the arrow on the top left
9. ByPass done.
10. Here you can not enable the developer and we can not restore option. It's just bypass
---------- Post added at 01:34 AM ---------- Previous post was at 01:24 AM ----------
Process FRP
Download four app
Aptoide
Es fileExplorer
Kingo Root
(Instead of Kingo Root use Croowt for rooting.)
Terminal Emulator
The accessibility of this phone is very poor so that the process is as follows:
1. In the menu go to Use data (Data Usage)/ You Tube / Application Settings / About
2. chose Google Privacy Policy
3. Open Google Chrome and from there download each of the applications but do not open.
4. Then return to the phone menu with the option "back"
5. We will install fromStorage File Explorer and open it
6. From the File Explorer install the other three applications
7. Open Aptoide and install the Nova Launcher, open and see the phone menu
(sometimes the phone will send you back to the beginning,. If this happens use some of the previous instructions to help you get back to this point. Use your common sense or ingenuity to decide what instructions get you back)
8. Execute Kingo Root and Root and wait to tell you Done
(sometimes the phone will send you back to the beginning,. If this happens use some of the previous instructions to help you get back to this point. Use your common sense or ingenuity to decide what instructions get you back)
9. Let back and look for the Terminal Emulator, enter and type "SU" to give us the option root access #
10. Write in the amulador the following command:
content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
11. After that go back out from terminal emulator. Enable developer and OEM Unlockif not does not imortant.
12. Go to account and fill your own google account. The phone let you fil up.
13 Very important: do no delete (reset) the phone as yet
14. Restart the phone and when start again you can enter your own google account. Then delete (reset) the phone.
15. Done. Credits: arsalrock55
HELP
arsalrock55 said:
mod edit
my services are not required here
Click to expand...
Click to collapse
i would like ur help
Additional help
madrick73 said:
at number 5 of the process, i get a (cannot open file message) on any apk. Do you know why?
bypass:
1. Playing in email and keep pressed the @ until a menu of options.
2. Keyboard settings google
3. Orthographic / staff / dictionary correction for all languages
4. On the next screen tap the magnifying glass and press the letter "c". Several options were deployed and there
google pinyin input to choose. On the next screen we chose the same option.
5. Then choose "about" open source licenses"
6. On the next screen may maintain finger pressing and the option will appear
"share" to choose "messages" typing 112 and send. At that time the call keyboard appears
delete 112 and type * # * # 4636 # * # *
7. On the next screen you can choose info or battery usage statistics.
8. Then go to back with the arrow on the top left
9. Bypass done.
10. Here you can not enable the developer and we can not restore option. It's just bypass
---------- post added at 01:34 am ---------- previous post was at 01:24 am ----------
process frp
download four app
aptoide
es fileexplorer
kingo root
terminal emulator
the accecibilidad this phone is very poor so that the process is as follows:
1. In the menu go to use data / you tube / application settings / about
2. Chose google privacy policy
3. Open google chrome and from there download each of the applications but do not open.
4. Then return to the phone menu with the option "back"
5. We will install fromstorage file explorer and open it
6. From the file explorer install the other three applications
7. Open aptoide and install the nova launcher, open and see the phone menu
8. Execute kingo root and root and wait to tell you done
9. Let back and look for the terminal emulator, enter and type "su" to give us the option
root access #
10. Write in the amulador the following command:
Content insert --uri content://settings / secure --bind name: S: User_setup_complete --bind value: S: 1
11. After that go back out from terminal emulator. Enable developer and oem unlockif not does not imortant.
12. Go to account and fill your own google account. The phone let you fil up.
13 very importante do no delete the phone
14. Restart the phone and when start again you can enter your own google account. Then delete the phone.
15. Done. Credits: Arsalrock55
---------- post added at 01:38 am ---------- previous post was at 01:34 am ----------
note:
You can add the app multi windows that offers a fast accessibility when the process fails and you have not to do all the bypass again buti had problems with this app.
He also clarified that does not always go in the first time is because the root with kingo root maybe you have to do many times.
I hope you serve the process.
Tested 100%
Click to expand...
Click to collapse
[/quote]
how to open aptoide
kingo root fail
how to open aptoide[/QUOTE]
it keeps telling me root failed
---------- Post added at 10:48 AM ---------- Previous post was at 10:08 AM ----------
bromass said:
NB: I edited some of the instruction above as some sections were wrong or hard to understand. You still have to muddle through to get a proper understanding. My model was AT&T version 5.1
This model of AT & T version 5.1 does not allow unlock bootloader
It not allowed to also upload version 6.0 for retail and still has not left the AT & T version.
Test dpc does not work for this security because it does not give the option of encryption as Owner.
ByPass:
1. Playing in email and keep pressed the @ until a menu of options.
2. keyboard settings Google
3. orthographic (text correction / staff(personal dictionary) / Dictionary correction for all languages
4. On the next screen tap the magnifying glass and press the letter "c". Several options were deployed and there
Google Pinyin Input to choose. On the next screen, we chose "google hindu input".
5. Then choose "about" Open Source Licenses"
6. On the next screen may maintain finger pressing and the option will appear
"Share" to choose "messages" typing 112 and send. At that time the telephone icon appears
select telephone icon
delete 112 and type * # * # 4636 # * # *
7. On the next screen you can choose info or battery usage statistics.
8. Then go to back with the arrow on the top left
9. ByPass done.
10. Here you can not enable the developer and we can not restore option. It's just bypass
---------- Post added at 01:34 AM ---------- Previous post was at 01:24 AM ----------
Process FRP
Download four app
Aptoide
Es fileExplorer
Kingo Root
(Instead of Kingo Root use Croowt for rooting.)
Terminal Emulator
The accessibility of this phone is very poor so that the process is as follows:
1. In the menu go to Use data (Data Usage)/ You Tube / Application Settings / About
2. chose Google Privacy Policy
3. Open Google Chrome and from there download each of the applications but do not open.
4. Then return to the phone menu with the option "back"
5. We will install fromStorage File Explorer and open it
6. From the File Explorer install the other three applications
7. Open Aptoide and install the Nova Launcher, open and see the phone menu
(sometimes the phone will send you back to the beginning,. If this happens use some of the previous instructions to help you get back to this point. Use your common sense or ingenuity to decide what instructions get you back)
8. Execute Kingo Root and Root and wait to tell you Done
(sometimes the phone will send you back to the beginning,. If this happens use some of the previous instructions to help you get back to this point. Use your common sense or ingenuity to decide what instructions get you back)
9. Let back and look for the Terminal Emulator, enter and type "SU" to give us the option root access #
10. Write in the amulador the following command:
content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
11. After that go back out from terminal emulator. Enable developer and OEM Unlockif not does not imortant.
12. Go to account and fill your own google account. The phone let you fil up.
13 Very important: do no delete (reset) the phone as yet
14. Restart the phone and when start again you can enter your own google account. Then delete (reset) the phone.
15. Done. Credits: arsalrock55
Click to expand...
Click to collapse
i got the kingo root to work but i cant get te emulator to work
arsalrock55 said:
Take my skype i give you solution
Arsalan.shahab1
Click to expand...
Click to collapse
Same problem over here, the one issue is no one wants to even help Android 5.1 or older users seems everyone has gotten spolied
First thing to do is to unlock bootloader and then root your device. Then go to terminal on pc and enable usb debugging. type:
adb shell
su
then copy and paste all this into the terminal window : https://del.dog/asovalisad.pl then type enter.
if you go to aida 64 it will tell you that all your sensors are working again. DO NOT REBOOT, FIX DOESN'T STICK AFTER REBOOT Tested on Pixel 3 (blueline) but it should work on every pixel. full credit to @ab123321 and @_LLJY
Add "sync"
Hey if you're touching the persist partition, you'll want to add a "sync" command to flush content out to the disk / UFS.
zaacc said:
First thing to do is to unlock bootloader and then root your device. Then go to terminal on pc and enable usb debugging. type:
adb shell
su
then copy and paste all this into the terminal window : https://del.dog/asovalisad.pl then type enter.
if you go to aida 64 it will tell you that all your sensors are working again. DO NOT REBOOT, FIX DOESN'T STICK AFTER REBOOT Tested on Pixel 3 (blueline) but it should work on every pixel. full credit to @ab123321 and @_LLJY
Click to expand...
Click to collapse
Thank you for sharing the script.
A suggestion to try out: put this script in init so it is initialised at each reboot.
Let us know if it works!
THIS IS ONLY TESTED IN WEAR OS 3 ON A GALAXY WATCH 4
THOUGH THIS SHOULD WORK ON ALL WATCHES AND OLDER VERSIONS OF WEAR OS
Requirements:
ADB installed on your computer
Have your wear OS device connected to the same network as you computer
A bit of patience, this works in a very weird way!
Downloading apks and installing them
Firstly enable adb and adb debugging over WiFi on your wear OS device
Then download the latest apks:
Termux
MultiVnc If you want a graphical environment on Linux
When you have the apks run these commands:
Code:
adb connect IP_OF_YOUR_WEAR_OS_DEVICE
You might be able to see your ip under the button for enabling adb debugging over wifi
Then run these commands in the downloads folder
Code:
adb -s " IP_OF_YOUR_WEAR_OS_DEVICE" install NAME_OF_THE_DOWNLOADED_TERMUX_APK_FILE
and
Code:
adb -s " IP_OF_YOUR_WEAR_OS_DEVICE" install NAME_OF_THE_DOWNLOADED_MULTI-VNC_APK_FILE
BE AWARE THAT YOU MIGHT HAVE TO RESTART THE ADB CONNECTION, SOMETIMES IT MAY FREEZE.
to do that run
Code:
adb disconnect
then
Code:
adb connect IP_OF_YOUR_WEAR_OS_DEVICE
Installing Linux in Termux
Stay awake sleepyhead!
To make everything easier enable the option in Termux to keep your watch awake, this will save you from so much trouble.
First open up Termux, then long press the black background.
Then press the three dots and choose the option "More...".
Scroll down until you see the option "Keep screen on", turn on that.
Keyboard?
I've discovered that there's a problem with Wear OS keyboards, for some reason they might not interact properly with certain android applications.
So open up Termux in your Wear OS device and see if you can write anything in Termux.
If that works, see if there's any enter button on your keyboard and see if it works.
If Termux gave any response to what you entered then skip this part and head straight for "The Linux multiverse!"
If the enter button doesn't work then you gotta install an android keyboard.
The best keyboard I've found that also works on round Wear OS devices is "Unexpected keyboard"
Download the keyboard and run:
Code:
adb -s " IP_OF_YOUR_WEAR_OS_DEVICE" install NAME_OF_THE_DOWNLOADED_KEYBOARD_APK_FILE
When the keyboard is installed change you default keyboard into the previously installed keyboard.
The Linux multiverse!
On your ANDROID PHONE install Andronix.
In there you will have a lot of options for installing Linux on Termux. You can choose whatever you want!
When you've chosen what you want, then Andronix will copy a command to your phones clipboard.
Oh no!
This is where you might only have a few options!
The problems is that you have to get the command from your phone to your Wear OS device, though your Wear OS device might not even let you copy and paste!
Though there is a way to bypass this, ANDROID APPS! The easiest way is to install messenger lite(not messenger for Wear OS).
First download Messenger lite. (source for the messenger download link)
Then In the downloads folder run:
Code:
adb -s " IP_OF_YOUR_WEAR_OS_DEVICE" install NAME_OF_THE_DOWNLOADED_MESSENGER_APK_FILE
Log into messenger on your phone and your Wear OS device.
On your phone send the command Andronix gave you, to yourself in messenger.
Then open up messenger on your Wear OS device and long press the command and select copy!
Now the biggest hassle is gone!
The long, really long awakening
Now that you've copied the command, enter Termux. Then long press the black background and press paste.
NOW DON'T TOUCH ANYTHING, so that you don't accidentally change anything in the command.
From your computer run:
Code:
adb shell input keyevent 66
Try to remember this command, or put it somewhere easy to copy. You'll need it pretty often. (this command serves as an enter button)
The installation of Linux will now begin, there will be some Y/N questions, just choose the default options by running:
Code:
adb shell input keyevent 66
After a while you might get questions about region, keyboard and such.
use
Code:
adb shell input keyevent 66
to scroll down when it says [MORE]
then use
Code:
adb shell input text "NUMBER/WORD"
(don't remove the parentheses)
then again use
Code:
adb shell input keyevent 66
as an enter button
It might also ask you for a vnc password, choose a small and easy password.
FINALLY LINUX!
You should now have Linux installed on your Wear Os device. Go do whatever you want with it.
Just remember that your Wear OS device uses arm, so if you wanna use x86 applications, then you gotta use Box64 if you have a 64-bit processor and Box86 if you have a 32-bit processor
Start Linux(Linux might automatically start after installation)
First run:
Code:
adb shell input text "ls"
Code:
adb shell input keyevent 66
This will run the ls command.
Look for a file closely name to start-SOME_LINUX_DISTRO.sh or start-andronix.sh
then run:
Code:
adb shell input text "./start-SOME_LINUX_DISTRO"
then
Code:
adb shell input keyevent 66
BOOM Linux is now running :3
What about GUI?
If you installed a Linux version with a graphical interface then you either gotta use a VNC to display anything on your watch
run
Code:
adb shell input text "vncserver-start"
then
Code:
adb shell input keyevent 66
then
Code:
adb shell input keyevent 66
The terminal will say " New 'remote-desktop' at :NUMBER on machine localhost "
remember that number
now exit Termux and start Mutli-Vnc
Scroll down to "New Connection"
in Address enter localhost
in port enter 590 and then the number. (If the number as is higher than 9, enter 59 and then the number)
Scroll down password and enter in the vnc password you chose earlier.
Then the scroll all the way down and press the big green "Connect" button!
You should now some something, maybe not a lot, but something"
You can manually set the resolution if you want, so that you're able to utilize the screen better, go here for a guide on that.
External GUI
If you actually wanna use the Linux installation, then you'll have to use an external device to view the desktop.
You can follow this guide here, as it's better at explaining then me.
You can also use this guide if you wanna use XSDL.
A tip for entering &, use the keyboard on the watch! Also the read the explanation of commands before you continue, you'll need it!
Command explanation!!
adb shell input text " " will enter any text into the connected adb device, %s is used for spaces
adb shell input keyevents will do any key event, like pressing enter, 66 is for enter
If something doesn't work, let me know. I might've missed something!