SOLVED:
The reason Device was not detected in Fastbootmode was due to my new ryzen 3000 system, I tried it on my much older quad core 46XXk(?) Intel system and it gave me no problems whatsoever finding the device in fastboot mode in my first try! wtf amd!
The second Set of problems came with flashing 16.0631.1910.64. It gave me a ton of errors and it was on an infinite boot loop, nothing I tried fixed it, my device was a worthless brick in that state, but fastboot Power+Volume up > 16.0631.1910.64 worked perfectly.
I decided to instead try 16.0631.1910.35, but once I flashed it everything worked perfectly! I am in the latest version of android 10 atm and can acess banks, play nintendo games, etc with the rooted device.
Hi, I bought this phone (Rog 2) mostly Intended as a donation for a friend that was complaining on facebook that he's probably going to be homeless due to covid and didnt even have his phone since he cracked the screen. While I cant help with housing I can help with a measly phone and I heard for gaming this is one of the best.
I got the tencent version not knowing what the heck I was getting myself into ( I thought all ROG 2 were the same and didn't even think to look it up). Been googling for days, I am trying to make this a full WW variant and basically as hassle free as possible for him, it seems that it has an obscure version of "pkq1.190414.001.ww_phone-16.0622.1906.19-0 " Rom, but according to HWInfo the fingerprint is CN.
Problem is I tried following this guide, I unlocked the bootloader with the ROG phone unlock tool, but on step 2 I load into fastboot, click flashall_AFT but all I see is a cmd with the message [command] : fastboot.exe flash all WW_ZS660KL_16.0631.1910.35_M3.13.33.30-ASUS_1.1.207_Phone-user.raw and nothing happens.
I noticed that on the cmd of the minimal adb devices and fastboot folder, the "adb devices" gives my device , the "adb reboot bootloader" works by taking me to the bootloader, but the "fastboot devices" does not give me anything at all once im in bootloader. In fact when using adb reboot bootloader I hear the windows beep as if the cellphone is disconecting. Any ideas what is going on?
TeknoViking- said:
Hi, I bought this phone (Rog 2) mostly Intended as a donation for a friend that was complaining on facebook that he's probably going to be homeless due to covid and didnt even have his phone since he cracked the screen. While I cant help with housing I can help with a measly phone and I heard for gaming this is one of the best.
I got the tencent version not knowing what the heck I was getting myself into ( I thought all ROG 2 were the same and didn't even think to look it up). Been googling for days, I am trying to make this a full WW variant and basically as hassle free as possible for him, it seems that it has an obscure version of "pkq1.190414.001.ww_phone-16.0622.1906.19-0 " Rom, but according to HWInfo the fingerprint is CN.
Problem is I tried following this guide, I unlocked the bootloader with the ROG phone unlock tool, but on step 2 I load into fastboot, click flashall_AFT but all I see is a cmd with the message [command] : fastboot.exe flash all WW_ZS660KL_16.0631.1910.35_M3.13.33.30-ASUS_1.1.207_Phone-user.raw and nothing happens.
I noticed that on the cmd of the minimal adb devices and fastboot folder, the "adb devices" gives my device , the "adb reboot bootloader" works by taking me to the bootloader, but the "fastboot devices" does not give me anything at all once im in bootloader. In fact when using adb reboot bootloader I hear the windows beep as if the cellphone is disconecting. Any ideas what is going on?
Click to expand...
Click to collapse
Have you installed adb drivers https://github.com/koush/UniversalAdbDriver
Also, just checking the obvious, you are using the side port of the phone, not the bottom, right?
reg66 said:
Have you installed adb drivers https://github.com/koush/UniversalAdbDriver
Also, just checking the obvious, you are using the side port of the phone, not the bottom, right?
Click to expand...
Click to collapse
Hi! Yeah, I have the exact same driver you mentioned as well as Minimal ADB and Fastboot and using the black sideport.
It seems when I connect it during the fastboot(Green arrow menu) I do hear the "USB Device plugged" sound so there's that.
flashall_AFT still just gives me a black page with: [command] : fastboot.exe flash all WW_ZS660KL_16.0631.1910.35_M3.13.33.30-ASUS_1.1.207_Phone-user.raw
TeknoViking- said:
Hi! Yeah, I have the exact same driver you mentioned as well as Minimal ADB and Fastboot and using the black sideport.
It seems when I connect it during the fastboot(Green arrow menu) I do hear the "USB Device plugged" sound so there's that.
flashall_AFT still just gives me a black page with: [command] : fastboot.exe flash all WW_ZS660KL_16.0631.1910.35_M3.13.33.30-ASUS_1.1.207_Phone-user.raw
Click to expand...
Click to collapse
Before running flashall_AFT.cmd, when you hear the device connect, have you tried entering 'fastboot devices' before doing anything else? See if it gives you a serial. If it does.
Then have you removed the original zip file from the extracted folder that contains the raw img? Once you click flashall_AFT.cmd, the cmd window should stay open for around 5 minutes while the flash takes place, then the phone will reboot once done
reg66 said:
Before running flashall_AFT.cmd, when you hear the device connect, have you tried entering 'fastboot devices' before doing anything else? See if it gives you a serial. If it does.
Then have you removed the original zip file from the extracted folder that contains the raw img? Once you click flashall_AFT.cmd, the cmd window should stay open for around 5 minutes while the flash takes place, then the phone will reboot once done
Click to expand...
Click to collapse
Top left image is from using the "fastboot devices" command, as you can see I type it it doesn't show or seem to do anything really. The right image is from clicking flashall_AFT, both inside bootloader on my rog 2 and outside give the same result.
The Zip file? As in the 2.7 one I downloaded? Yeah that content of that is in a folder in root of C drive, the zip is in a completely different drive so they are not sharing a directory . I did not modify anything inside the extracted file though.
For reference I am following the steps here: https://forum.xda-developers.com/t/...rom-cn-to-ww-with-latest-1910-35-raw.4002279/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TeknoViking- said:
Top left image is from using the "fastboot devices" command, as you can see I type it it doesn't show or seem to do anything really. The right image is from clicking flashall_AFT, both inside bootloader on my rog 2 and outside give the same result.
The Zip file? As in the 2.7 one I downloaded? Yeah that content of that is in a folder in root of C drive, the zip is in a completely different drive so they are not sharing a directory . I did not modify anything inside the extracted file though.
For reference I am following the steps here: https://forum.xda-developers.com/t/...rom-cn-to-ww-with-latest-1910-35-raw.4002279/
View attachment 5173971
Click to expand...
Click to collapse
Ok, try unpacking the attached zip to root of C, like the other adb folder. Then click on 'cmd-here.exe' to launch cmd window and then try 'fastboot devices'. (that's assuming the drivers of the original install are working). Let me know if you get a serial response.
reg66 said:
Ok, try unpacking the attached zip to root of C, like the other adb folder. Then click on 'cmd-here.exe' to launch cmd window and then try 'fastboot devices'. (that's assuming the drivers of the original install are working). Let me know if you get a serial response.
Click to expand...
Click to collapse
Done, nothing happens, did it multiple times here's what I get:
TeknoViking- said:
Done, nothing happens, did it multiple times here's what I get:
Click to expand...
Click to collapse
Ok, what a pain! Try uninstall minimal adb drivers and I'll see if I can find ano version for you....
reg66 said:
Ok, what a pain! Try uninstall minimal adb drivers and I'll see if I can find ano version for you....
Click to expand...
Click to collapse
Will do! ty
TeknoViking- said:
Will do! ty
Click to expand...
Click to collapse
try this version, after installing the drivers you could also try that folder with the cmd-here file in combination. Also, try booting into android os and enable developer options (click on 'build' 7 or so times in settings/system/about phone/software information/build number), then go to developer options and enable USB debugging - might make a difference...
Also, check your pm, I sent you modified instructions for using the other guide that'll take you straight to last Android 9 version before you can update to Android 10 (1910.64). You could always be downloading that newer RAW + root img while tinkering with getting the damn thing recognised by your pc!!
Tried the 1910.64 you sent me and its the same problem unfortunately, still stuck on step 2. I already had USB debugging with the "USB debugging" option ticked on when I created the topic.
I take it doing number 4 Is a bad idea if can't get past 2? "4) Download the root&bootstockww191035.zip "rootww191064" and extract it to the Minimal ADB and Fastboot Folder (C:\Program Files (x86)\Minimal ADB and Fastboot) from here "
TeknoViking- said:
Tried the 1910.64 you sent me and its the same problem unfortunately, still stuck on step 2. I already had USB debugging with the "USB debugging" option ticked on when I created the topic.
I take it doing number 4 Is a bad idea if can't get past 2? "4) Download the root&bootstockww191035.zip "rootww191064" and extract it to the Minimal ADB and Fastboot Folder (C:\Program Files (x86)\Minimal ADB and Fastboot) from here "
Click to expand...
Click to collapse
Yeah, there's no point continuing until you can get fastboot devices to at least show your device. Do you have another pc/laptop you could try on? Are you using an AMD based system, pretty sure I read somewhere that can give issues, along with the system used! Sorry that's a bit vague...
TeknoViking- said:
Tried the 1910.64 you sent me and its the same problem unfortunately, still stuck on step 2. I already had USB debugging with the "USB debugging" option ticked on when I created the topic.
I take it doing number 4 Is a bad idea if can't get past 2? "4) Download the root&bootstockww191035.zip "rootww191064" and extract it to the Minimal ADB and Fastboot Folder (C:\Program Files (x86)\Minimal ADB and Fastboot) from here "
Click to expand...
Click to collapse
Oh sorry, you meant try flashing the root img, NO, definitely not. The root img MUST only flashed after successful flashing of RAW - both rom and boot/root boot img's must match. (But either way, if your device isn't recognised by fastboot it just won't flash, just an FYI)
See this thread for info on Ryzen issues, if that is what you're running. The OP says he used an external USB hub as a solution
reg66 said:
Yeah, there's no point continuing until you can get fastboot devices to at least show your device. Do you have another pc/laptop you could try on? Are you using an AMD based system, pretty sure I read somewhere that can give issues, along with the system used! Sorry that's a bit vague...
Click to expand...
Click to collapse
Ok I tried this on my intel system and it detected it!! "fastboot devices" gave me the serial. So when I tried to do step 2 and I used ADB_FASTBOOT to run flashall_AFT from the 1910.64 it failed and it it seems to be on a loop in bootloader "The boot loader is unlocked and software integrity cannot be guaranteed..) etc screen.
I attached the image. This is with the 1910.64 on step two.
Also I got this from continually trying to boot:
TeknoViking- said:
Ok I tried this on my intel system and it detected it!! "fastboot devices" gave me the serial. So when I tried to do step 2 and I used ADB_FASTBOOT to run flashall_AFT from the 1910.64 it failed and it it seems to be on a loop in bootloader "The boot loader is unlocked and software integrity cannot be guaranteed..) etc screen.
I attached the image. This is with the 1910.64 on step two.
Click to expand...
Click to collapse
Hmm, this phone is troublesome. Sorry dude, I've not seen that before. The bootloader unlock tool definitely worked, right? What about if you try using the original 1910.35 RAW - same error?
TeknoViking- said:
Also I got this from continually trying to boot:
Click to expand...
Click to collapse
Do you have above 50% charge? If not, definitely make sure to have enough charge for the whole process. I was always of the understanding, as a rule of thumb, to have devices above 50% before performing flashing of custom roms etc
reg66 said:
Do you have above 50% charge? If not, definitely make sure to have enough charge for the whole process. I was always of the understanding, as a rule of thumb, to have devices above 50% before performing flashing of custom roms etc
Click to expand...
Click to collapse
Yeah the charge is over 90 percent, anything I can do for that error? when I connect to the intel pc it doesn't even beep any more. I still can access the boot screen though.
EDIT: OOPS, noticed I had it plugged on the bottom, nvm intel system still detects the device. I did perform everything on the side port usb but I took it out to try and check back on the ryzen system.
Related
Hey,
So I unlocked the boot-loader and installed CWM Recovery and flashed to- http://forum.xda-developers.com/showthread.php?t=2026675 but it doesn't go any where from the loading screen then I tried installing Pac-Man ROm same thing keeps loading in the boot screen doesn't go further my device is S-on and I don't know if it is rooted ? I'm sort of a noob at rooting any ways can some one tell me why this is ?
Cheers
For a start you need to get rid of CWM. It does weird and wonderful (not in a good way) things to this phone. Try TWRP or the one from Wild Child (sorry cant remember the name of it). Second, being S-on requires you to manually flash the boot.img using fastboot or you just get bootloops. Best thing you could do is read thoroughly through the pinned post as they contain all the info you need.
Spectrejester said:
For a start you need to get rid of CWM. It does weird and wonderful (not in a good way) things to this phone. Try TWRP or the one from Wild Child (sorry cant remember the name of it). Second, being S-on requires you to manually flash the boot.img using fastboot or you just get bootloops. Best thing you could do is read thoroughly through the pinned post as they contain all the info you need.
Click to expand...
Click to collapse
WHat does this mean" manually flash the boot.img using fastboot "
Thanks
it means flashing the boot.img or boot image to the phone while in bootloaders fastboot option using fastboot in a command prompt. I suggest taking time to read all pinned post in development area several times till you understand it before doing anything more, lest you end up with a bricked phone.
Here is a link to a good start http://forum.xda-developers.com/showthread.php?t=1416836
As i said read it several times to make sure you know what you are doing is right.
Here is a relatively easy to follow guide. Wherever you see "something in quotes" only look at whats INSIDE the quotes. Ignore the quotes themselves.
Okay, what you need to do is this:
Replace CWM with TWRP or WCX Recovery
on your phone go to setting>developer options and click USDB Debugging to enable it
now, on your computer, set up adb
To get the HTC USB Drivers download and install HTC Sync (If you do not need the Sync application itself you can uninstall it but the drivers will remain on your system). * in some cases may be necessary to temporary disable your antivirus software during the installation of HTC Sync.
Download the attached file below
Extract the archive on your C: drive. You will have C:\android-tools folder
assuming you have flashed the PAC rom, download the EXACT SAME ROM to your computer, open the zip file, copy the "boot.img" or "boot" file. Paste it into the C:/android-tools folder
in that same folder, control+shift+right click. Select open command prompt here
now, in the window that pops up, type in "adb devices" - you should now see a code starting with HT(this is your device)
next, type in "adb reboot bootloader"
wait a few seconds. your phone will turn off, and reboot in bootloader. go into fastboot mode using volume rockers and power button
in the command prompt window, type in "fastboot devices" You should see that same HT... code from before
type "fastboot flash boot boot.img" into the command window.
on your phone, using the volume rockers and power button to select reboot. Your Rom should now boot nicely.
Hope this helps you get a ROM on your Vivid. If it does, please thank me using the Thanks button
Mihir1997 said:
Here is a relatively easy to follow guide. Wherever you see "something in quotes" only look at whats INSIDE the quotes. Ignore the quotes themselves.
Okay, what you need to do is this:
Replace CWM with TWRP or WCX Recovery
on your phone go to setting>developer options and click USDB Debugging to enable it
now, on your computer, set up adb
To get the HTC USB Drivers download and install HTC Sync (If you do not need the Sync application itself you can uninstall it but the drivers will remain on your system). * in some cases may be necessary to temporary disable your antivirus software during the installation of HTC Sync.
Download the attached file below
Extract the archive on your C: drive. You will have C:\android-tools folder
assuming you have flashed the PAC rom, download the EXACT SAME ROM to your computer, open the zip file, copy the "boot.img" or "boot" file. Paste it into the C:/android-tools folder
in that same folder, control+shift+right click. Select open command prompt here
now, in the window that pops up, type in "adb devices" - you should now see a code starting with HT(this is your device)
next, type in "adb reboot bootloader"
wait a few seconds. your phone will turn off, and reboot in bootloader. go into fastboot mode using volume rockers and power button
in the command prompt window, type in "fastboot devices" You should see that same HT... code from before
type "fastboot flash boot boot.img" into the command window.
on your phone, using the volume rockers and power button to select reboot. Your Rom should now boot nicely.
Hope this helps you get a ROM on your Vivid. If it does, please thank me using the Thanks button
Click to expand...
Click to collapse
Where are the attached files mate ?
Oh LOL...
http://forum.xda-developers.com/attachment.php?attachmentid=1764898&d=1361948659
Mihir1997 said:
Oh LOL...
http://forum.xda-developers.com/attachment.php?attachmentid=1764898&d=1361948659
Click to expand...
Click to collapse
C:\android-tools\android-tools>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
C:\android-tools\android-tools>
Why is this ?
dinukap4 said:
C:\android-tools\android-tools>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
C:\android-tools\android-tools>
Why is this ?
Click to expand...
Click to collapse
Is ur phone plugged in? is USB debugging on in the dev options menu?
Mihir1997 said:
Is ur phone plugged in? is USB debugging on in the dev options menu?
Click to expand...
Click to collapse
ok did that now waiting to load fingers crossed
About 5 min passed still loading :/ Should I wipe anything ?
Edit- Tried with both CM and pac same :/ did everything correctly btw what does "now, on your computer, set up adb" Mean ?
C:\android-tools\android-tools>adb devices
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
C:\android-tools\android-tools>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT1AXVJ00209 recovery
C:\android-tools\android-tools>adb reboot bootloader
C:\android-tools\android-tools>fastboot devices
HT1AXVJ00209 fastboot
C:\android-tools\android-tools>fastboot flash boot boot.img
sending 'boot' (3570 KB)...
OKAY [ 0.796s]
writing 'boot'...
OKAY [ 1.549s]
finished. total time: 2.350s
C:\android-tools\android-tools>
that is like the thing that the next steps explain.
so, did you fastboot flash the boot img?
it has to be the boot from the rom you want.
Mihir1997 said:
that is like the thing that the next steps explain.
so, did you fastboot flash the boot img?
it has to be the boot from the rom you want.
Click to expand...
Click to collapse
When I try to do the CMD stuff on this screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It tells me -
C:\android-tools\android-tools>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
C:\android-tools\android-tools>
Click to expand...
Click to collapse
And if I give this command -adb reboot bootloader
C:\android-tools\android-tools>adb reboot bootloader
error: device not found
Click to expand...
Click to collapse
But if i go to recovery and enable Debugging it passes, But I cant enable it and come back to the Fast boot screen because debugging will be disabled and I get the same thing-
If done with recovery debugging-
C:\android-tools\android-tools>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT1AXVJ00209 recovery
Click to expand...
Click to collapse
Bump!!
BUMP! Please help me out
Is this an HTC vivid ? screenshot doesn't look like one...
Lol, wrong forum. This is NOT an HTC Vivid. You have to atleast know what phone you have. Go to the forum for your device. but either way. This image suggest you have not plugged a UDB into the phone. If you had, it would say "fastboot USB"
esloan said:
Is this an HTC vivid ? screenshot doesn't look like one...
Click to expand...
Click to collapse
Mihir1997 said:
Lol, wrong forum. This is NOT an HTC Vivid. You have to atleast know what phone you have. Go to the forum for your device. but either way. This image suggest you have not plugged a UDB into the phone. If you had, it would say "fastboot USB"
Click to expand...
Click to collapse
I got that off google images lol not my phone anyways I got it to work, but it doesnt have play store and my memory car isn't accessible ? I tried with 2 mem cards both the same cant download anything
dinukap4 said:
I got that off google images lol not my phone anyways I got it to work, but it doesnt have play store and my memory car isn't accessible ? I tried with 2 mem cards both the same cant download anything
Click to expand...
Click to collapse
Play store Fix: flash Gapps (google apps) - you can do a search on google. Download the correct one. if you have a rom with Android 4.2.2, use a Gapps for 4.2.2
Memory card: What rom are you using? go into the Rom forum and post there for help.
Mihir1997 said:
Here is a relatively easy to follow guide. Wherever you see "something in quotes" only look at whats INSIDE the quotes. Ignore the quotes themselves.
Okay, what you need to do is this:
Replace CWM with TWRP or WCX Recovery
on your phone go to setting>developer options and click USDB Debugging to enable it
now, on your computer, set up adb
To get the HTC USB Drivers download and install HTC Sync (If you do not need the Sync application itself you can uninstall it but the drivers will remain on your system). * in some cases may be necessary to temporary disable your antivirus software during the installation of HTC Sync.
Download the attached file below
Extract the archive on your C: drive. You will have C:\android-tools folder
assuming you have flashed the PAC rom, download the EXACT SAME ROM to your computer, open the zip file, copy the "boot.img" or "boot" file. Paste it into the C:/android-tools folder
in that same folder, control+shift+right click. Select open command prompt here
now, in the window that pops up, type in "adb devices" - you should now see a code starting with HT(this is your device)
next, type in "adb reboot bootloader"
wait a few seconds. your phone will turn off, and reboot in bootloader. go into fastboot mode using volume rockers and power button
in the command prompt window, type in "fastboot devices" You should see that same HT... code from before
type "fastboot flash boot boot.img" into the command window.
on your phone, using the volume rockers and power button to select reboot. Your Rom should now boot nicely.
Hope this helps you get a ROM on your Vivid. If it does, please thank me using the Thanks button
Click to expand...
Click to collapse
$$$ post right here -- Thanks for putting this up -- Huzzah Huzzah
Super noob here. I was trying to update my android revolution hd rom and somehow I screwed everything.
Do I have a chance to fix my phone or should I purchase a new one?
My unit is a HTC One m7 (sprint).
I understand that in order to fix this I need to install a new recovery (I have a CWM old version). The phone reboots in regular mode but as ROM is not working it reboots to recovery, but this doesn't work either I just see a 0,5s splash screen and the loop goes on.
I have read the "disaster recovery" thread but they assume Fastboot USB works. My problem is I dont even know how to connect my phone to my computer in order to work from there.
My bootloader is still unlocked (fortunately).
I have Hboot 1.44 should I update it?
A step-by-step dumb proof will be appreciated!
First download a toolkit for the HTC one m7. You can find it in the android development section. With that you can install a new recovery. I recommend twrp. After that push a ROM via adb to the device and flash that Rom. There are hundreds of sprint ROMs and even more threads "how to adb push"
http://forum.xda-developers.com/showthread.php?t=2265618
[GUIDE] Complete Flashing Guide | Rooting | Going Back To Stock | 05.05.2013
Philipp_94 said:
First download a toolkit for the HTC one m7. You can find it in the android development section. With that you can install a new recovery. I recommend twrp. After that push a ROM via adb to the device and flash that Rom. There are hundreds of sprint ROMs and even more threads "how to adb push"
http://forum.xda-developers.com/showthread.php?t=2265618
[GUIDE] Complete Flashing Guide | Rooting | Going Back To Stock | 05.05.2013
Click to expand...
Click to collapse
Thanks, downloaded this tool seems great, but my phone is not getting recognized by the system. Im using Windows 8.1
http://forum.xda-developers.com/showthread.php?t=2727913
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My drivers are installed, I have "HTC Sync Manager" installed. This is desperating.
Blocked ONE said:
Thanks, downloaded this tool seems great, but my phone is not getting recognized by the system. Im using Windows 8.1
http://forum.xda-developers.com/showthread.php?t=2727913
My drivers are installed, I have "HTC Sync Manager" installed. This is desperating.
Click to expand...
Click to collapse
First off if your running CWM and tried to install ARHD then your gonna have issues as ARHD is only compatible with TWRP recovery 2.6.3.3 or 2.7.1.1
If Windows 8 has stopped recognizing your phone and you can't boot to a Rom unfortunately there's little chance of you getting it working again.
So you have 2 good options. Get/make an otg cable and use it to install a Rom compatible with CWM.
Or create a Linux boot disk to use adb/fastboot. Linux doesn't need drivers for your phone so no detection problems then you can flash recovery or push a Rom whatever you want.
---------- Post added at 03:50 PM ---------- Previous post was at 03:27 PM ----------
Blocked ONE said:
I have read the "disaster recovery" thread but they assume Fastboot USB works. My problem is I dont even know how to connect my phone to my computer in order to work from there.
Click to expand...
Click to collapse
To use Fastboot :- boot the phone to the boot loader and select Fastboot from the menu. Then connect you phone via usb cable and Fastboot should change to fastbootusb.
Open the folder that contains adb and fast boot on your pc then hold Shift and right click on the empty white background space, from the menu that appears select "open command window here"
In the command window type
fastboot devices
If you get an output of your phone's serial no. Fastboot is working.
Danny201281 said:
First off if your running CWM and tried to install ARHD then your gonna have issues as ARHD is only compatible with TWRP recovery 2.6.3.3 or 2.7.1.1
If Windows 8 has stopped recognizing your phone and you can't boot to a Rom unfortunately there's little chance of you getting it working again.
So you have 2 good options. Get/make an otg cable and use it to install a Rom compatible with CWM.
Or create a Linux boot disk to use adb/fastboot. Linux doesn't need drivers for your phone so no detection problems then you can flash recovery or push a Rom whatever you want
To use Fastboot :- boot the phone to the boot loader and select Fastboot from the menu. Then connect you phone via usb cable and Fastboot should change to fastbootusb.
Open the folder that contains adb and fast boot on your pc then hold Shift and right click on the empty white background space, from the menu that appears select "open command window here"
In the command window type
fastboot devices
If you get an output of your phone's serial no. Fastboot is working.
Click to expand...
Click to collapse
I write fastboot devices and nothing happens.
I think I'm trying on a friends computer he has Linux. Hope this is not bricked lol. At least the phone turns ON, it can be charged as well, and bootloader works. But can't fastboot!
Blocked ONE said:
I write fastboot devices and nothing happens.
I think I'm trying on a friends computer he has Linux. Hope this is not bricked lol. At least the phone turns ON, it can be charged as well, and bootloader works. But can't fastboot!
Click to expand...
Click to collapse
Your not even close to being bricked
On Linux you will still need to install adb/fastboot but no drivers for your phone needed. As long as adb is working your on a winner
Also you will need to add sudo at the beginning of each command
E.g "adb devices" becomes " sudo adb devices" or "fastboot flash recovery" becomes " sudo fastboot flash recovery"
Blocked ONE said:
I write fastboot devices and nothing happens.
I think I'm trying on a friends computer he has Linux. Hope this is not bricked lol. At least the phone turns ON, it can be charged as well, and bootloader works. But can't fastboot!
Click to expand...
Click to collapse
Danny201281 said:
Your not even close to being bricked
On Linux you will still need to install adb/fastboot but no drivers for your phone needed. As long as adb is working your on a winner
Also you will need to add sudo at the beginning of each command
E.g "adb devices" becomes " sudo adb devices" or "fastboot flash recovery" becomes " sudo fastboot flash recovery"
Click to expand...
Click to collapse
also Sprint has a different partition structure you CANNOT use files for a GSM phone on yours ...please go to the sprint forums for the files and help you need
Sirs, ubuntu doesnt recognize it either!
While on the bootloop it says system can't mount the Android unit. This means the USB is working.
But on the bootloader/fastboot it doesn't even pop up this message, its like nothing is plugged. WTF I think it is bricked, can't connect anywhere. I feel stupid just trashed my phone for a non important ROM update.
Blocked ONE said:
Sirs, ubuntu doesnt recognize it either!
While on the bootloop it says system can't mount the Android unit. This means the USB is working.
But on the bootloader/fastboot it doesn't even pop up this message, its like nothing is plugged. WTF I think it is bricked, can't connect anywhere. I feel stupid just trashed my phone for a non important ROM update.
Click to expand...
Click to collapse
you need to calm down
first turn the phone off
hold power plus volume down
when the phone goes off keep holding volume down and let go of power
now your in the bootloader
use the volume key to select bootloader then power off
now wait
now hook the phone to the usb and hit power plus volume down
let go of both when you see the bootloader again
now your in fastboot USB
now you can flash the correct recovery to your phone.
next you need this >> http://forum.xda-developers.com/showthread.php?t=2658910
clsA said:
you need to calm down
first turn the phone off
hold power plus volume down
when the phone goes off keep holding volume down and let go of power
now your in the bootloader
use the volume key to select bootloader then power off
now wait
now hook the phone to the usb and hit power plus volume down
let go of both when you see the bootloader again
now your in fastboot USB
now you can flash the correct recovery to your phone.
next you need this >> http://forum.xda-developers.com/showthread.php?t=2658910
Click to expand...
Click to collapse
I followed your instructions but the device doesn't show up in Ubuntu.
But if I try to boot in regular mode, it shows! "Android Phone". The problem is I can't access this, since it just appears for some seconds because this is during the bootloop. Anyway during these seconds, if I click on "Android Phone" it says it cant access it... This is confusing.
I tried both USB 3.0 and 2.0 since I have read 3.0 has problems sometimes.
Should I install any kind of drivers on Ubuntu?
Blocked ONE said:
I followed your instructions but the device doesn't show up in Ubuntu.
But if I try to boot in regular mode, it shows! "Android Phone". The problem is I can't access this, since it just appears for some seconds because this is during the bootloop. Anyway during these seconds, if I click on "Android Phone" it says it cant access it... This is confusing.
I tried both USB 3.0 and 2.0 since I have read 3.0 has problems sometimes.
Should I install any kind of drivers on Ubuntu?
Click to expand...
Click to collapse
From @nkk71 Superguide
5) Q: How do I create a Linux Live USB
Windows users: http://click.xda-developers.com/api...ww.ubuntu.com/download/deskt...ick-on-windows
Mac users: http://www.ubuntu.com/download/deskt...ick-on-mac-osx
Ubuntu 12.04 LTS 32bit ISO from here: http://www.ubuntu.com/download/desktop
Once the Ubuntu Live USB is ready, shutdown your computer and restart from the USB
No need to install, just use the "Try Ubuntu" option
open a terminal
and install adb & fastboot using (copy/paste 1 line at a time into terminal):
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
you can then check version, by typing "adb version"
and check connection using "adb devices" in custom recovery or booted phone
and "sudo fastboot devices" in bootloader
you can also check @tobesedated guide for more info: [Guide]Suggestion For S-off On 1.55 HBoot Using Ubuntu---Step by step with pictures
Click to expand...
Click to collapse
OK i think im making some progress!!
I am running this ubuntu from USB, installed adb and fastboot, and I think its connected now. At console I type "fastboot devices" and it says: "HT359W90.... fastboot"
Then I downloaded the TWRP 2.7.1.1 and flashed it. Finally I rebooted the phone and now it enters recovery!!!!!! :good: Im now sure the one is not dead!! Thank you so much guys.
Now what? Should I make a factory reset or just go ahead and flash the ROM I intended to get? Don't want to screw it again...
p.s. Apparently I can't push the ROM from ubuntu to sdcard. It says "no such file or directory". And from phone, the ADB Sideload feature doesnt work either, it gest stuck at "starting ADB sideload feature" even after 15 minutes...
Blocked ONE said:
OK i think im making some progress!!
I am running this ubuntu from USB, installed adb and fastboot, and I think its connected now. At console I type "fastboot devices" and it says: "HT359W90.... fastboot"
Then I downloaded the TWRP 2.7.1.1 and flashed it. Finally I rebooted the phone and now it enters recovery!!!!!! :good: Im now sure the one is not dead!! Thank you so much guys.
Now what? Should I make a factory reset or just go ahead and flash the ROM I intended to get? Don't want to screw it again...
p.s. Apparently I can't push the ROM from ubuntu to sdcard. It says "no such file or directory". And from phone, the ADB Sideload feature doesnt work either, it gest stuck at "starting ADB sideload feature" even after 15 minutes...
Click to expand...
Click to collapse
Ok so you have usb Linux working that's great.
What method did you use to install adb/fastboot? Hopefully it was the Webupd8 repository install as this makes life easy.
Danny201281 said:
Ok so you have usb Linux working that's great.
What method did you use to install adb/fastboot? Hopefully it was the Webupd8 repository install as this makes life easy.
Click to expand...
Click to collapse
Yes I followed the method quoted by clsA
Make sure your Rom is compatible with Sprint then to push it to the phone do this.
Boot your Linux usb stick and select the try ubuntu option. Wait for the desktop to load. Open the Home folder. In the top left you should see other drives connected to your pc. Go into your hdd and copy the Rom to the Home folder of the Linux usb and rename it rom.zip.
Now reboot computer, and Wait for it to return to the try/install ubuntu screen. And press
Control + alt + F1 (this will take you to main Linux terminal)
Boot your phone into recovery and connect with usb and type
adb devices (to check phone is detected if phone is not detected see below)
Then
adb push rom.zip /sdcard
If phone is not detected type the following 3 commands waiting for each to complete there out put. Be patient it may seem stuck at some points and you may see some errors but just wait for the terminal to return to normal after each command I.E ready to accept another command. Once all 3 commands have completed try adb devices again.
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
Danny201281 said:
Make sure your Rom is compatible with Sprint then to push it to the phone do this.
Boot your Linux usb stick and select the try ubuntu option. Wait for the desktop to load. Open the Home folder. In the top left you should see other drives connected to your pc. Go into your hdd and copy the Rom to the Home folder of the Linux usb and rename it rom.zip.
Now reboot computer, and Wait for it to return to the try/install ubuntu screen. And press
Control + alt + F1 (this will take you to main Linux terminal)
Boot your phone into recovery and connect with usb and type
adb devices (to check phone is detected if phone is not detected see below)
Then
adb push rom.zip /sdcard
If phone is not detected type the following 3 commands waiting for each to complete there out put. Be patient it may seem stuck at some points and you may see some errors but just wait for the terminal to return to normal after each command I.E ready to accept another command. Once all 3 commands have completed try adb devices again.
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
Click to expand...
Click to collapse
Ubuntu crashes whenever I press Ctrl+Alt+F1, tried twice and had to reboot.
I was using Ctrl+Alt+T for opening a console. Already did all those 3 commands but not working. This seems challenging! I have read something about 32-bits instructions needed for this? Im running under a 64bit computer and 64 bit linux distribution.
By the way a friend has got an OTG cable, would this work to get a ROM inside the SD-Card?
Blocked ONE said:
Ubuntu crashes whenever I press Ctrl+Alt+F1, tried twice and had to reboot.
I was using Ctrl+Alt+T for opening a console. Already did all those 3 commands but not working. This seems challenging! I have read something about 32-bits instructions needed for this? Im running under a 64bit computer and 64 bit linux distribution.
By the way a friend has got an OTG cable, would this work to get a ROM inside the SD-Card?
Click to expand...
Click to collapse
You should be using 32bit Linux it will run ok on a 64bit machine. But with 64bit Linux you will need to install 32bit libs I think.
Yes an otg cable can be used to copy the Rom to the phone
It's weird that you had Fastboot working but adb won't though. Try using adb without the sudo prefix. It should be working if Fastboot is. But remember you must be in recovery to use adb. Not the bootloader.
Fastboot = bootloader
Adb = recovery
Blocked ONE said:
p.s. Apparently I can't push the ROM from ubuntu to sdcard. It says "no such file or directory".
Click to expand...
Click to collapse
Ok slight brain fart on my part lol. The error you got implies that adb is working but your Rom is not in the right place.
You can put the Rom in the home folder and use the adb push command from the terminal as it is when opened.
Or if the Rom is for instance in the downloads folder you must first use
cd Downloads (to take the terminal to the downloads folder)
Then adb push
More problems lol
Apparently I can't flash any ROM because it says I cant mount cache, data nor internal storage.
Im on TWRP 2.7.1.1
Blocked ONE said:
More problems lol
Apparently I can't flash any ROM because it says I cant mount cache, data nor internal storage.
Im on TWRP 2.7.1.1
Click to expand...
Click to collapse
So you've got the Rom on the phone but when go To recovery you can't see the rom because of this error?
It's normal to see these type of errors after using fastboot erase cache. But not normally with internal storage.
If you can see the Rom just flash it it should work.
Guys I have TWRP V2.8.10...I was trying to install ViperOne Rom. I had in installed but I foolishly did a FULL ADVANCED Whipe...Idk why I did that I wasn't thinking about it...well naturally it wiped the ROM clean off the device as well as EVERYTHING else. I don't even have my backup to restore to. UGH I'm so frustrated with myself. Well anyways I try to enable MTP while in TWRP and its shows the HTC One as a portable device as well as havin 24.9 of 25.0 GB of FREE Space however it will NOT let me copy the ViperOne ROM over....it keeps saying the file size is too large. IT most certainly is NOT too large. There has to be someway around this to FORCE this file onto to the device for a reflash. Any help would be appreciated here. Idk if this is a windows thing but I was thinking I could maybe even attach a micro to full size usb plug to the htc and put the rom on a flash drive and flash it onto the device but idk if this would work. I should also note that when I open internal storage on the device it only shows the TWRP folder. I'm half wondering if the device has lost its root as well...will a reflash over the terminal maybe help?
gravatrax1 said:
Guys I have TWRP V2.8.10...I was trying to install ViperOne Rom. I had in installed but I foolishly did a FULL ADVANCED Whipe...Idk why I did that I wasn't thinking about it...well naturally it wiped the ROM clean off the device as well as EVERYTHING else. I don't even have my backup to restore to. UGH I'm so frustrated with myself. Well anyways I try to enable MTP while in TWRP and its shows the HTC One as a portable device as well as havin 24.9 of 25.0 GB of FREE Space however it will NOT let me copy the ViperOne ROM over....it keeps saying the file size is too large. IT most certainly is NOT too large. There has to be someway around this to FORCE this file onto to the device for a reflash. Any help would be appreciated here. Idk if this is a windows thing but I was thinking I could maybe even attach a micro to full size usb plug to the htc and put the rom on a flash drive and flash it onto the device but idk if this would work.
Click to expand...
Click to collapse
If you have a USB-OTG adapter it will certainly work.
your other options are adb push rom.zip /sdcard
and adb sideload rom.zip
just be sure the rom.zip is in the same folder as adb
I have a fastboot folder on my desktop the directory is
C:\Users\GRAVATRAX\Desktop\fastboot
VIPER adb and fastboot are all in the same folder, how would enter this into the command terminal? I'm following instructions that I found but it cames throwing me errors
Attached a pic, what am i doing wrong here lol
gravatrax1 said:
I have a fastboot folder on my desktop the directory is
C:\Users\GRAVATRAX\Desktop\fastboot
VIPER adb and fastboot are all in the same folder, how would enter this into the command terminal? I'm following instructions that I found but it cames throwing me errors
Attached a pic, what am i doing wrong here lol
Click to expand...
Click to collapse
What does your storage show as in recovery? 0mb?
Since you wiped it all anyway you may as well try Wipe>Format Data, from within twrp. You will be prompted to type yes to confirm. When its done reboot recovery and try MTP again.
As for using adb and fastboot. Do this, Hold Shift and Right Click on your fastboot folder. From the drop down menu that appears select "Open a command window here" this should open a cmd prompt with your fastboot folder as it's working directory.
Now use the push command
Code:
adb push viper.zip /sdcard
The command window will appear unresponsive until the push completes. When it's done install the Rom with your recovery.
Danny201281 said:
What does your storage show as in recovery? 0mb?
Since you wiped it all anyway you may as well try Wipe>Format Data, from within twrp. You will be prompted to type yes to confirm. When its done reboot recovery and try MTP again.
As for using adb and fastboot. Do this, Hold Shift and Right Click on your fastboot folder. From the drop down menu that appears select "Open a command window here" this should open a cmd prompt with your fastboot folder as it's working directory.
Now use the push command
Code:
adb push viper.zip /sdcard
The command window will appear unresponsive until the push completes. When it's done install the Rom with your recovery.
Click to expand...
Click to collapse
How long does it usually take to transfer files via this method? It shows the file onthe device but in the amount of like 128kb, will it give some sort of confirmation when its done?
Also in recovery it would show the device as having an internal storage os 26034.
If this doesn't work where I can find an otg cable? Would it be possible to use lets say a male to female usb adapter with a standard micro usb cable to achieve this effect
gravatrax1 said:
How long does it usually take to transfer files via this method? It shows the file onthe device but in the amount of like 128kb, will it give some sort of confirmation when its done?
Click to expand...
Click to collapse
While the Rom is being pushed you will see only a blinking cursor in the command window. When it's complete you should get a confirmation and the prompt will return to normal
It can take several minutes.
A basic OTG cable looks like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But they com in all sorts of shapes and sizes I use one like this
Picked up in my local tesco for a few quid
Danny201281 said:
While the Rom is being pushed you will see only a blinking cursor in the command window. When it's complete you should get a confirmation and the prompt will return to normal
It can take several minutes.
Click to expand...
Click to collapse
Alright Ill just be patient and let it do its thing....I tried to push the file via adb sideload however it kept saying device not found And yes i would enable ADB sideload via TWR
I might have to take a trip down to best buy and staples nad see if I can find one...I would call and see if they have what Im looking for...but LOL.
SO while we are waiting for this file to be pushed I am curious as to why this is happening. what exactly did I do for it cause to bring me this issue in Windows?
gravatrax1 said:
Alright Ill just be patient and let it do its thing....I tried to push the file via adb sideload however it kept saying device not found And yes i would enable ADB sideload via TWR
I might have to take a trip down to best buy and staples nad see if I can find one...I would call and see if they have what Im looking for...but LOL.
Click to expand...
Click to collapse
you need to fix your pc drivers while the phone is in recovery
look for the one in device manager with an exclamation mark and update the driver manually
clsA said:
you need to fix your pc drivers while the phone is in recovery
look for the one in device manager with an exclamation mark and update the driver manually
Click to expand...
Click to collapse
The deivce manager shows no issues with the drivers :/
Still trying to push the file...something gotta be wrong here.
gravatrax1 said:
Alright Ill just be patient and let it do its thing....I tried to push the file via adb sideload however it kept saying device not found And yes i would enable ADB sideload via TWR
I might have to take a trip down to best buy and staples nad see if I can find one...I would call and see if they have what Im looking for...but LOL.
SO while we are waiting for this file to be pushed I am curious as to why this is happening. what exactly did I do for it cause to bring me this issue in Windows?
Click to expand...
Click to collapse
Check your SDK is upto date by typing this into the fastboot command window
Code:
adb version
The latest is 1.0.32.
Also you may try TWRP 2.6.3.3 some other versions of TWRP have issues with adb. :good:
EDIT:- Infact reading back to your first post i see your using TWRP 2.8.1.0. It's been a while since i first tested that version but i'm sure I ditched it because of problems with adb
Hi. Tried to install lineage yesterday (didn't go well at all). After that car crash I did a factory reset to get back to scratch. However, I cannot reinstsll Netflix now. Google play protect seems to be fine so I'm not sure what is wrong now.
Edit: Google pointed me in the wrong direction. I seen to have lost the certification when I tried to install lineage. What do I need to do to fix this?
Is the problem due to me unlocking the bootloader or would cleaning the cache/data on Google play fix this?
Eggstones said:
Is the problem due to me unlocking the bootloader or would cleaning the cache/data on Google play fix this?
Click to expand...
Click to collapse
Play Protect has nothing to do with it. Your Bootloader in unlocked so you are failing Safetynet. Are you on OOS now or LOS? It's not clear in your post because you said you installed LOS and then did a Factory Reset. That would leave you still on LOS. But you also said back to scratch. So are you on OOS or LOS?
Relocking your Bootloader is possible on both OOS or LOS. That fixes the Safetynet issue either way. Or you can use Magisk on either to fix the Safetynet issue too.
Dirk said:
Play Protect has nothing to do with it. Your Bootloader in unlocked so you are failing Safetynet. Are you on OOS now or LOS? It's not clear in your post because you said you installed LOS and then did a Factory Reset. That would leave you still on LOS. But you also said back to scratch. So are you on OOS or LOS?
Relocking your Bootloader is possible on both OOS or LOS. That fixes the Safetynet issue either way. Or you can use Magisk on either to fix the Safetynet issue too.
Click to expand...
Click to collapse
I couldn't install twrp as it didn't recognise the image file so couldn't proceed with lineage. (Have to say the install guide expect the user to really know a heck of a lot of stuff that should be in the guides). Ended up doing a factory reset back to OOS 9.0.5 (I think that is the latest stock version).
So locking the bootloader would fix this issue? It only seems like Netflix is being cranky.
Not rooted so I don't I can use magisk.
Eggstones said:
I couldn't install twrp as it didn't recognise the image file so couldn't proceed with lineage. (Have to say the install guide expect the user to really know a heck of a lot of stuff that should be in the guides). Ended up doing a factory reset back to OOS 9.0.5 (I think that is the latest stock version).
So locking the bootloader would fix this issue? It only seems like Netflix is being cranky.
Not rooted so I don't I can use magisk.
Click to expand...
Click to collapse
Magisk is the root method, and also used to fix Safetynet issues. You would need TWRP installed though.
Locking the Bootloader right now will fix the issue you are having. It will also factory reset your phone again, so be prepared for that.
That said, installing TWRP is easy if you follow the guides carefully and avoid the obvious pifalls, or simply trying to use the wrong TWRP is a common issue.
In case you still want to try LOS:
This TWRP:
Download twrp-3.3.1-0-oneplus3.img
Follow this guide from funkwizard:
Flashing TWRP Recovery
Adjust the following settings on the phone:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
USB Debugging:
On your phone go to Settings > About phone > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > Developer options > Enable USB debugging
Enable OEM Unlocking:
On your phone go to Settings > Developer options. Then enable the 'OEM Unlocking' option and make sure that from now on, OEM unlocking option is enabled before you reboot. Sometimes, it might get disabled itself.
Enable Advanced Reboot:
On your phone go to Settings > Developer options. Then enable the 'Advanced Reboot' option.
Place TWRP image in the Platform Tools folder in C:\adb
Then boot into fastboot/bootloader mode on your phone by holding volume up + power or selecting the reboot to bootloader via advanced reboot options.
Open a new command prompt in the platform tools folder and run the following command:
Code:
fastboot flash recovery (file name).img
Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead unplug your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed, or you can also use the command:
Code:
fastboot boot recovery.img
/Guide.
Just to be clear, when you fastboot flash the TWRP image i linked you to, the command will be:
Code:
fastboot flash recovery twrp-3.3.1-0-oneplus3.img
Make sure your phone is actually in fastboot mode when you do this. Just follow the guide. (On Windows 10 a command prompt window can be opened in the platform tools folder by typing 'cmd' in the Address Bar in that folder, using Windows Explorer).
Once you have flashed TWRP, you do need to boot straight into that Recovery. If you boot into the OS, the stock Recovery will overwrite TWRP again. (follow the guide).
Once you are in TWRP, swipe to 'allow modifications'. (If you decide to go down the custom ROM path you will need to Format /Data and Wipe Partitions, then connect to your PC and transfer any zips you need to install to Internal Storage).
You will have to decide for yourself whether you want to be rooted with Magisk. While it can be used to fix Safetynet issues, it's not needed for that. If you want root access, flash Magisk. If you don't want root, don't. Simple.
Let's say for arguments sake you don't want to be rooted and have sucessfully installed TWRP. Next step would be to install LOS. Assuming you want a stable ROM, it would be LOS 16 you install. So you would flash the latest build of that along with Gapps and the second Zip in this post:
https://forum.xda-developers.com/showpost.php?p=78433987&postcount=3 which is:
https://drive.google.com/open?id=1Yy...2YSyxEXNXWolH5 (sec-patch-2019-08-01.zip)
That zip takes care of one Safetynet problem. (CTS Profile).
Once you have LOS setup you can relock your Bootloader. That then takes care of the remaining Safetynet issue.
Clear Cache/Data on the Play Store App and reboot. Use the 'Root and Safetynet Checker' App to test Safetynet status. Once it shows 'Passed', Netflix and Banking Apps (Including Google Pay) that rely on Safetynet will all work.
Or stay on OOS and relock your Bootloader. Only you know what you want, although it seems that after our previous discussions you are ready to dip your toes into the custom ROM scene. Don't let some early setbacks deter you. You're almost there.
At the moment I'm just trying to get back to where I started. Funk wizards guide is slightly different from the one on the lineage wiki page. I got as far as installing twrp but got only an error message (something on the lines can't load image). Not sure if that's due to adb being wrongly installed or the image being in the wrong folder. Don't think the wiki page mentioned advanced boot mentioned above. Slightly surprised that my banking apps work fine but not Netflix. You would have thought they would be more 'cranky'.
Been trying again today to do this and am failing massively. Everything seemed fine till I tried to do a backup with helium. Helium is not recognising my OnePlus 3t. Tried to install the drivers that comes with the phone but stopped it after the instal had gone on for about 30 minutes.
Tried the ADB route but the command line doesn't recognise the command. Not sure how to check if it is installed prooerly. Can't remember how I did on my old laptop but on my new hp it doesn't seem to have worked. Remember it being very straightforward so don't understand why it has failed this time
ADB was installed using the lineage page's instructions.
Eggstones said:
Been trying again today to do this and am failing massively. Everything seemed fine till I tried to do a backup with helium. Helium is not recognising my OnePlus 3t. Tried to install the drivers that comes with the phone but stopped it after the instal had gone on for about 30 minutes.
Tried the ADB route but the command line doesn't recognise the command. Not sure how to check if it is installed prooerly. Can't remember how I did on my old laptop but on my new hp it doesn't seem to have worked. Remember it being very straightforward so don't understand why it has failed this time
ADB was installed using the lineage page's instructions.
Click to expand...
Click to collapse
Here's a way to test that ADB can connect to your phone:
- open a PowerShell (a more modern version of CMD) session by right-clicking on the folder where you extracted the ADB files (the folder that contains adb.exe).
- type (without the quotes) ".\adb version". That will tell you the version of ADB your running and that you can execute the command.
- connect your phone to your PC then type ".\adb devices" on your PC. You should get a prompt on your phone asking if you want to trust your PC - say yes. Then you'll get the ID of your phone listed on your PC if everything works ok.
If that all works but just typing "adb devices" doesn't, then that means you haven't set up the of environment settings properly on your PC.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
Here's a way to test that ADB can connect to your phone:
- open a PowerShell (a more modern version of CMD) session by right-clicking on the folder where you extracted the ADB files (the folder that contains adb.exe).
- type (without the quotes) ".\adb version". That will tell you the version of ADB your running and that you can execute the command.
- connect your phone to your PC then type ".\adb devices" on your PC. You should get a prompt on your phone asking if you want to trust your PC - say yes. Then you'll get the ID of your phone listed on your PC if everything works ok.
If that all works but just typing "adb devices" doesn't, then that means you haven't set up the of environment settings properly on your PC.
Click to expand...
Click to collapse
Sorry but I do not follow. Type where? If I right click on the folder there is nothing opening up where I can write the command in. Only the normal file options show up.
If I search for it using the windows 10 search function I can start it but it doesn't recognise ./adb as a command. So where have I gone wrong?
@Eggstones
Sorry, I meant to say shift-right-click on the folder and then select "Open PowerShell window here" from the menu.
Sent from my OnePlus 3T using XDA Labs
Thanks. That worked. I have version 1.0.41.
So now the question is why isn't it recognising my phone. I can see it when I go into the file explorer and open all subfolders.
Eggstones said:
Thanks. That worked. I have version 1.0.41.
So now the question is why isn't it recognising my phone. I can see it when I go into the file explorer and open all subfolders.
Click to expand...
Click to collapse
What worked?
1. typing "./adb version"
2. typing "adb version"
3. typing "./adb devices"
And please quote my post otherwise I can't tell that you've replied.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
What worked?
1. typing "./adb version"
2. typing "adb version"
3. typing "./adb devices"
And please quote my post otherwise I can't tell that you've replied.
Click to expand...
Click to collapse
Sorry. Yes all of the above. Have now managed to back up the phone (ok didn't get a promt to confirm backup but it seems to have worked). Not sure why I need to write "./adb" to make the commands work but is seems to have done the trick.
Let's see if I can get lineage on the phone now.
And thanks again for your help and patience
Eggstones said:
Sorry. Yes all of the above. Have now managed to back up the phone (ok didn't get a promt to confirm backup but it seems to have worked). Not sure why I need to write "./adb" to make the commands work but is seems to have done the trick.
Let's see if I can get lineage on the phone now.
And thanks again for your help and patience
Click to expand...
Click to collapse
Glad you got it working. But you said that all three commands worked, the second of which had just "adb version", then said you had to use ./adb. If the second one worked then just plain adb should work all the time.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
Glad you got it working. But you said that all three commands worked, the second of which had just "adb version", then said you had to use ./adb. If the second one worked then just plain adb should work all the time.
Click to expand...
Click to collapse
For some reason ADB is only recognised as a command if I use ./ In front of it . No idea why but at least it is working. Will try to do the ROM tomorrow.
There might be crying
Eggstones said:
For some reason ADB is only recognised as a command if I use ./ In front of it . No idea why but at least it is working. Will try to do the ROM tomorrow.
There might be crying
Click to expand...
Click to collapse
That means you haven't set up the Windows environment properly.
The setup instructions in https://wiki.lineageos.org/adb_fastboot_guide.html say:
Code:
On Windows 10:
Open the Start menu, and type “advanced system settings”
Select “View advanced system settings”
Click on the Advanced tab
Open the “Environment Variables” window
Select the Path variable under “System Variables” and click the “Edit” button
Click the “Edit Text” button
Append ;%USERPROFILE%\adb-fastboot\platform-tools to the end of the existing Path definition (the semi-colon separates each path entry)
Can you share:
1. What your Windows Path looks like (screenshot?) and
2. The full path of the folder where you installed ADB
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
That means you haven't set up the Windows environment properly.
The setup instructions in https://wiki.lineageos.org/adb_fastboot_guide.html say:
Can you share:
1. What your Windows Path looks like (screenshot?) and
2. The full path of the folder where you installed ADB
Click to expand...
Click to collapse
Will post that later. When I set it up I followed that guide, but wouldn't be surprised if the pathway thing is wrong as it is a bit opaque in my view.
BillGoss said:
That means you haven't set up the Windows environment properly.
The setup instructions in https://wiki.lineageos.org/adb_fastboot_guide.html say:
Can you share:
1. What your Windows Path looks like (screenshot?) and
2. The full path of the folder where you installed ADB
Click to expand...
Click to collapse
I think I know what's gone wrong.
Pathway: C:\platform-tools
I'm guessing that is the line that should be in the environmental variables...
Eggstones said:
I think I know what's gone wrong.
Pathway: C:\platform-tools
I'm guessing that is the line that should be in the environmental variables...
Click to expand...
Click to collapse
I'd be very surprised if C:\platform-tools is the correct path unless that's actually where you put the unzipped folder.
And kjien\adb... is definitely not right (doesn't include a drive name).
If you use Windows Explorer and select the folder that contains the ADB files and then click on the "Copy path" icon in the menu ribbon (next to the Copy and Paste buttons), then the clipboard will have the correct path.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
I'd be very surprised if C:\platform-tools is the correct path unless that's actually where you put the unzipped folder.
And kjien\adb... is definitely not right (doesn't include a drive name).
If you use Windows Explorer and select the folder that contains the ADB files and then click on the "Copy path" icon in the menu ribbon (next to the Copy and Paste buttons), then the clipboard will have the correct path.
Click to expand...
Click to collapse
That is what I did to get the path. So should C:\platform-tools replace kjien\adb to make it work?
TL;DR- I'm trying to get back to Android 11 but I only have access to the fastboot menu since my phone is bootlooping. I'm fairly certain I hadn't enabled USB debugging when the phone was fully functional so I'm not sure if I can use ADB to do so. I also don't have the bootloader unlocked
I downloaded the 12 beta preview last week to try the new features, some UI bugs understandably but was mostly fine. A couple days ago while the screen was off and I just had the phone in my hand it randomly activated SOS mode so after a brief panic and cancelation of the 911 call I opted out of the beta immediately. The next morning after using my phone a bit I picked it up and noticed it was rebooting and was a little warm, and it's been bootlooping since then. I still remember the Andoid 12 UI being active so I'm pretty sure it hadn't reverted to the "new" 11 firmware yet.
I'm trying to revert back to 11 using the ADB on my PC, but I realized that I'm pretty sure I hadn't enabled USB debugging when my phone was still functional, so I'm not sure how to bypass that if I can at all. The web firmware flasher tool does detect my phone, but can't properly connect and I assume it's because the USB debugging isn't enabled.
Before I tried using the ADB I had attempted to perform a factory reset to fix the bootloop and the log messages said it was successfully done, but that didn't get it out of the loop.
@jet flyer
I didn't see the word "locked" or "recovery" anywhere in your post. If you are bootloader unlocked, you use fastboot to flash a full image. If you are BL locked, that should have been in your TL;DR. If you are BL locked, you can still flash a full OTA without having usb debug enabled. You just need to have the latest fastboot/adb binaries installed. Download the rescue OTA, put it in your adb folder and then from recovery mode, use the update via adb option. You do NOT need usb debug enabled to do this. You do however need a working Recovery mode. If you are BL locked and cannot access recovery that is the end of the road.
Sorry for the delayed response wanted a day off so I had enough time to properly deal with this. No it's not unlocked, edited OP to indicate that.
I only downloaded adb last week so that should be the most recent, are the fastboot binaries included in that install or is that something separate?
Using this video for help on how to run adb
I get the device connected sound on my PC when I select install from ADB on the recovery menu and I have ADB running at the C:\adb folder location. when I do the adb devices command I get this
'adb' is not recognized as an internal or external command,
operable program or batch file.
using the powershell I got the long list of text that's mentioned in the video after typing \adb but I still get a similar, but different, error when doing the devices command trying to confirm it's connected
Since this is probably just an error on my part not doing the right commands or something I'm hopping on the xda discord, I'll post here if I get it figured out
Download platform tools from here https://developer.android.com/studio/releases/platform-tools. Unzip it and then put the file that you want to side load in the same folder. I prefer PowerShell. Type adb sideload "file name.zip. That might not work if USB debugging isn't checked. If it doesn't try this.
Transfer the download OTA file to your device’s internal or external storage. Don’t put it inside any folder as the system won’t be able to find it.
Next up, boot your device to recovery.
From recovery, navigate to the Apply Update from SD Card option using Volume Keys. Press the Power key to confirm your selection.
Similarly, use the Volume keys to highlight the OTA.zip file and the Power key to install it. Once the process finishes, you could then use the Reboot system now option to boot your device back to OS
ok finally got something to run on my phone but got an error, here's the file paths and what I typed just in case
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And here's what the phone says, sorry about the marginal focus my backup pixel 2XL is doing it's best with the reflective screen. The relevant messages start right after the purple of the IR focusing laser reflection
one of the first errors is E: footer is wrong
and Error 21: signature verification failed
I recall hearing on one of those videos or guides I read that something has to be digitally signed, but this is a direct download from the Android website, wouldn't be already be signed?
jet flyer said:
ok finally got something to run on my phone but got an error, here's the file paths and what I typed just in case
View attachment 5333167
And here's what the phone says, sorry about the marginal focus my backup pixel 2XL is doing it's best with the reflective screen. The relevant messages start right after the purple of the IR focusing laser reflection
View attachment 5333175
one of the first errors is E: footer is wrong
and Error 21: signature verification failed
I recall hearing on one of those videos or guides I read that something has to be digitally signed, but this is a direct download from the Android website, wouldn't be already be signed?
Click to expand...
Click to collapse
Sorry for the delayed response, but If you use "reply" to a post the user will get an email notification and so respond more quickly. I normally check this board once a week. Yes, there is one zip file from Google that contains all the binaries you need for adb/fastboot. Yes the image coming from Google is signed. They even include the file hash so you can verify the file is a mirror image and un-corrupted. I'm going to continue down the adb method because it is fool proof and you may not be able to "push" the file to your device and use the sdcard method.
I'm not sure you have added your adb folder to your PC's path statement and this could be causing an issue. If you add this folder to the path, you can call up adb from any folder. However if you have the ota image in the same adb folder, and you navigate to that same folder before typing commands it will still work. I'm not seeing any of your inputs on your photo, so I can't check that. You can easily copy/paste text from the command window so we can clearly see what you are typing and the response back. What response are you getting to "adb devices" and "adb version" ? Until you get back your phone's serial number as a response, you are not connected properly. You can PM me for more assistance or use the reply button on this note. Best of luck.
v12xke said:
Sorry for the delayed response, but If you use "reply" to a post the user will get an email notification and so respond more quickly. I normally check this board once a week. Yes, there is one zip file from Google that contains all the binaries you need for adb/fastboot. Yes the image coming from Google is signed. They even include the file hash so you can verify the file is a mirror image and un-corrupted. I'm going to continue down the adb method because it is fool proof and you may not be able to "push" the file to your device and use the sdcard method.
I'm not sure you have added your adb folder to your PC's path statement and this could be causing an issue. If you add this folder to the path, you can call up adb from any folder. However if you have the ota image in the same adb folder, and you navigate to that same folder before typing commands it will still work. I'm not seeing any of your inputs on your photo, so I can't check that. You can easily copy/paste text from the command window so we can clearly see what you are typing and the response back. What response are you getting to "adb devices" and "adb version" ? Until you get back your phone's serial number as a response, you are not connected properly. You can PM me for more assistance or use the reply button on this note. Best of luck.
Click to expand...
Click to collapse
Ah sorry, still getting used to the specifics of this forum. Thanks for checking though.
I do get the serial number back as a response to verify I'm properly connected, I just didn't do it in that specific instance to avoid posting that online. And yes I did add it to the path(as far as I understand, that's just a convenience thing though?) but I'm still running it from the ADB folder just to be sure.
I'll go ahead and type here what commands I did and what the phone log says, since it's not in focus in the picture.
on adb I typed .\adb sideload coral-[specific file version].zip
adb response: Total xfer: 0.00x
on my phone which was on the load from adb screen it said this:
Now send the package you wan to apply
to the device with "adb sideload <filename> . . .
Supported API: 3
Finding update package. . .
Verifying update package. . .
E:footer is wrong
Update package verification took 0.5 s (result 1).
E:Signiture verification failed
Error: 21
Install from ADB completed with status 2.
Installation aborted.
Then it tried one more time automatically with the exact same text except taking 0.6 seconds but still failing and the same error messages. Should I just download the latest package (now the June update) and try again, or did I do something wrong? The file explorer window is where I opened the powershell from and where the file was extracted to. What does error 21 mean?
jet flyer said:
Ah sorry, still getting used to the specifics of this forum. Thanks for checking though.
I do get the serial number back as a response to verify I'm properly connected, I just didn't do it in that specific instance to avoid posting that online. And yes I did add it to the path(as far as I understand, that's just a convenience thing though?) but I'm still running it from the ADB folder just to be sure.
I'll go ahead and type here what commands I did and what the phone log says, since it's not in focus in the picture.
on adb I typed .\adb sideload coral-[specific file version].zip
adb response: Total xfer: 0.00x
on my phone which was on the load from adb screen it said this:
Now send the package you wan to apply
to the device with "adb sideload <filename> . . .
Supported API: 3
Finding update package. . .
Verifying update package. . .
E:footer is wrong
Update package verification took 0.5 s (result 1).
E:Signiture verification failed
Error: 21
Install from ADB completed with status 2.
Installation aborted.
Then it tried one more time automatically with the exact same text except taking 0.6 seconds but still failing and the same error messages. Should I just download the latest package (now the June update) and try again, or did I do something wrong? The file explorer window is where I opened the powershell from and where the file was extracted to. What does error 21 mean?
Click to expand...
Click to collapse
Sorry, I don't know what error 21 means. Trying the latest image is not going to hurt at this point. Make sure you post the complete file name of the image you are trying to flash. I think there may be bootloader version mismatch that is causing the errors. Verify and post your bootloader version (fastboot menu) and OS version (recovery menu). Have you tried doing a factory reset from recovery and retrying? At this point I would keep searching "rescue ota" for tips and hints. Pasting your screen would be best, rather than retyping. Best of luck!
v12xke said:
@jet flyer
I didn't see the word "locked" or "recovery" anywhere in your post. If you are bootloader unlocked, you use fastboot to flash a full image. If you are BL locked, that should have been in your TL;DR. If you are BL locked, you can still flash a full OTA without having usb debug enabled. You just need to have the latest fastboot/adb binaries installed. Download the rescue OTA, put it in your adb folder and then from recovery mode, use the update via adb option. You do NOT need usb debug enabled to do this. You do however need a working Recovery mode. If you are BL locked and cannot access recovery that is the end of the road.
Click to expand...
Click to collapse
So I read up and Error 21 is because the bootloader is locked. I have the latest bianaries installed like you mentioned, is there something else I was missing in my process?
jet flyer said:
So I read up and Error 21 is because the bootloader is locked. I have the latest bianaries installed like you mentioned, is there something else I was missing in my process?
Click to expand...
Click to collapse
Because your bootloader is locked, you cannot flash a full image . You have to flash an OTA instead.
Secondly, the OTA you choose has to match your current bootloader version or it won't work.
Read the instructions again for flashing a rescue OTA via recovery.
1. Have you accessed the phone's recovery menu and used the update via adb option?
2. What is your current bootloader version? (recovery menu)
3. What is the full name of the file you are attempting to flash? (OTA)
https://developers.google.com/android/ota
v12xke said:
Because your bootloader is locked, you cannot flash a full image . You have to flash an OTA instead.
Secondly, the OTA you choose has to match your current bootloader version or it won't work.
Read the instructions again for flashing a rescue OTA via recovery.
1. Have you accessed the phone's recovery menu and used the update via adb option?
2. What is your current bootloader version? (recovery menu)
3. What is the full name of the file you are attempting to flash? (OTA)
https://developers.google.com/android/ota
Click to expand...
Click to collapse
ohh, I never noticed that tab at the top that says OTA, I get it now that those are needed for non-unlocked bootloaders. I see all the different versions, what does my bootloader version have to do with one of those? I only see the dates pertaining to the monthly updates, how do I know which one is for my bootloader version? I found the section specific to the Pixel 4XL
That worked!!! Thanks for the help, kinda annoyed it was as simple as that tab at the top left of the page saying OTA updated, but glad to have my phone back after 6 weeks. My Pixel 2XL did it's best but a lot of the apps I use for my action camera or drone stuff didn't even work with it haha
jet flyer said:
That worked!!! Thanks for the help, kinda annoyed it was as simple as that tab at the top left of the page saying OTA updated, but glad to have my phone back after 6 weeks. My Pixel 2XL did it's best but a lot of the apps I use for my action camera or drone stuff didn't even work with it haha
Click to expand...
Click to collapse
Happy to hear you are back up and running! Cheers.