I rooted my AT&T HTC One and when i was going to flash a rom I accidentally wiped the phone completely. I can go into TWRP but cant move files into the phone. When i try plugging it into my computer all i hear is the little ring that windows does when you plug in something into the usb but i cant access the phones storage. I also tried buying a USB otg cable but the phone didnt seem to recognize it. please help. I've been stuck without a phone for about a week now.
Please help please help!!!!!!
coachpete said:
i rooted my at&t htc one and when i was going to flash a rom i accidentally wiped the phone completely. I can go into twrp but cant move files into the phone. When i try plugging it into my computer all i hear is the little ring that windows does when you plug in something into the usb but i cant access the phones storage. I also tried buying a usb otg cable but the phone didnt seem to recognize it. Please help. I've been stuck without a phone for about a week now.
Click to expand...
Click to collapse
can someone please help me!!!!!!
HTC One not recognized by Windows 7 or Windows 8
coachpete said:
I rooted my AT&T HTC One and when i was going to flash a rom I accidentally wiped the phone completely. I can go into TWRP but cant move files into the phone. When i try plugging it into my computer all i hear is the little ring that windows does when you plug in something into the usb but i cant access the phones storage. I also tried buying a USB otg cable but the phone didnt seem to recognize it. please help. I've been stuck without a phone for about a week now.
Click to expand...
Click to collapse
I am baby stepping through the trouble shooting process to try to get an image over to the phone so I can reimage through TWRP v2.7.0.0 but neither my Windows 7 machine nor my Windows 8 machine are recognizing the HTC One as a media device. I have tried the updated drivers with no luck. PLEASE HELP!!
coachpete said:
I am baby stepping through the trouble shooting process to try to get an image over to the phone so I can reimage through TWRP v2.7.0.0 but neither my Windows 7 machine nor my Windows 8 machine are recognizing the HTC One as a media device. I have tried the updated drivers with no luck. PLEASE HELP!!
Click to expand...
Click to collapse
you can use ADB from twrp recovery to push a rom to your /sdcard
follow this guide step by step and quote me here if you have question.
HTC ONE M7_U/M7_UL - ADB PUSH & FLASH A ROM - DETAILED INSTRUCTIONS
Prerequisites:
You need ADB and FASTBOOT on your computer, either by installing the Android SDK or Minimal ADB and FASTBOOT
You need to know how to start a fastboot/adb command prompt:
To open a command window prompt, in Windows go to Start Menu --> ''Run'' then type cmd. Change the directory to the ADB folder on your machine:
If using the default install location for the SDK:
Code:
cd C:\android-sdk-windows\tools
If using the default install location of Minimal ADB and FASTBOOT:
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
Or hold left shift + right click a blank space inside the folder where adb and fastboot are located and select ''Open command window here'' from the contextual menu.
{
"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"
}
You need TWRP recovery (2.6.3.3 or higher) on your device.
Unlock bootloader if not already unlocked:
Thanks to Electroz for the video tutorial
Flash TWRP Recovery:
Make sure the recovery.img file is in the same folder where adb and fastboot are located
reboot phone in bootloader mode
Flash the recovery:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
You need your HTC drivers correctly installed on your PC:
If not, follow this guide (thanks to nkk71):
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Procedure:
Make sure the ROM you want to flash is in the same folder where ADB and FASTBOOT are.
Here is a list of the HTC M7 roms
Connect your phone to computer using usb cable
Reboot phone in recovery mode (TWRP):
If phone is booted in OS:
Code:
adb reboot recovery
if not booted or bootlooping, hold power button + volume down until phone boot in bootloader mode
then select BOOTLOADER then RECOVERY using volume up/down to navigate and power button to select.
Make sure your phone is booted in TWRP main menu:
transfer the rom to your /sdcard folder:
Code:
adb push name_of_rom.zip /sdcard/
Wait for the zip file to transfer, this can take several minutes and there is no progress bar. When the command prompt give you back the hand and display how much bytes transferred in X seconds, the transfer is completed:
In TWRP main menu, select ''INSTALL''
Browse the installation menu and select your rom zip file inside /sdcard folder:
Swipe to confirm you want to flash the rom
Reboot phone
Click to expand...
Click to collapse
Computer doesn't recognize my HTC ONE
alray said:
you can use ADB from twrp recovery to push a rom to your /sdcard
follow this guide step by step and quote me here if you have question.
HTC ONE M7_U/M7_UL - ADB PUSH & FLASH A ROM - DETAILED INSTRUCTIONS
Click to expand...
Click to collapse
Thank you but my computer does not recognize my HTC one. I have tried installing the drivers from various sources but still no go! please help @alray
coachpete said:
Thank you but my computer does not recognize my HTC one. I have tried installing the drivers from various sources but still no go! please help @alray
Click to expand...
Click to collapse
check step 4 of the above prerequisites, click on ''show content'' then you'll find the instruction how to correctly install drivers.
Still no luck with the drivers
alray said:
check step 4 of the above prerequisites, click on ''show content'' then you'll find the instruction how to correctly install drivers.
Click to expand...
Click to collapse
Followed the detailed instructions for downloading and installing the correct drivers and my Windows 7 machine still does not recognize the HTC One correctly.
coachpete said:
Followed the detailed instructions for downloading and installing the correct drivers and my Windows 7 machine still does not recognize the HTC One correctly.
Click to expand...
Click to collapse
boot your phone in twrp, go in windows device manager and take a screenshot and post it here
when your phone is in twrp main menu, open a cmd prompt and do this command:
Code:
adb devices
what is the output?
FINALLY
alray said:
boot your phone in twrp, go in windows device manager and take a screenshot and post it here
when your phone is in twrp main menu, open a cmd prompt and do this command:
Code:
adb devices
what is the output?
Click to expand...
Click to collapse
Thanks for all your help I am now up and running!!!!!!
Related
The MoDaCo Mod for MOJO, which adds root and increased Play Store app availability to the MadCatz MOJO, is now available!
The mod takes the form of a Superboot image (as used on many devices previously), with additional features to resolve the Play Store lack-of-apps issue.
What is this?
Superboot is a boot.img that when booted, will root your device the first time you boot (installing su and the superuser APK). No need to flash any partitions, no messing with the contents of your data partition, no overwriting the shipped ROM on your device, just boot the boot image using the instructions below and you're done!
What are the pre-requisites?
You need a MOJO (duh) and a USB Male A-A cable to carry out this process. And a computer I suppose (Windows, Mac or Linux).
Any caveats?
You should note that while rooting may affect your ability to receive future OTAs, reverting back to stock is easy enough. We'll cross that bridge when we come to it.
Download
APPLY THIS AT YOUR OWN RISK!
Superboot MMM³ - DOWNLOAD - MD5: 835de32dd795d2825ade1ed1be422abf
How to use Superboot - Windows, Linux and OSX
Download the Superboot zip file above and extract to a directory
Put your device in bootloader mode - Unplug the power cable and any USB cables (the dongle can stay in), insert the USB Male A-A cable in the port labelled '2.0', then insert the power cable. 'Key driver not found.. Booting OS' will appear on screen.
WINDOWS - install the device drivers from the directory you extracted above if required, then run 'superboot-windows.bat' as Administrator
MAC - Open a terminal window to the directory containing the files, and type 'chmod +x superboot-mac.sh' followed by 'sudo ./superboot-mac.sh'
LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x superboot-linux.sh' followed by 'sudo ./superboot-linux.sh'
You will see 'Booting downloaded image' and a black screen, then the screen will return to 'Key driver not found.. Booting OS'. At this point, unplug the USB cable and the power cable, wait a few moments, then reconnect the power cable to boot as normal.
For all the missing apps to show up on the Play Store, you may need to clear data on the Play Store in 'Settings -> Applications' and reboot, then run the Play Store again.
Enjoy!
P
{
"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"
}
Thank you!
Thank you for kicking off true development for the Mojo to move forward. I'll try this as soon as I can and respond.
you rock!
Now I'm off to get dog food! Oh...I mean I'm using that as an excuse to run and get myself a USB cable. You're awesome, paulobrien. I'll root this evening!
There we go!!! What we've all been waiting for!!!
BTW, what are the changes to the Play Store that enable all the apps?
Thanks for this! Now I need an A-A cable...
Ok it's finaly come so happy thanks Paul O'Brien
I don't understand why my pc won't see my mojo there is no sound when i plug into it i try usb 2 and 3 with a usb 3 male male cable
So after i type reboot bootloader the mojo reboot normaly even if i unplug the power etc... and the pc do nothing
Thanks for what you did this is awesome
Mojo goes into fastboot mode and installed drivers fine. However currently running into issue where when I run the superboot-windows.bat file in admin mode it opens cmd for a second then immediately closes. The mojo doesn't seem to respond whatsoever. Any thoughts?
Ya same here mojo say key driver not found... Booting OS but when I run the .bat file doesnt close just sitting waiting for device
buggin0915 said:
Ya same here mojo say key driver not found... Booting OS but when I run the .bat file doesnt close just sitting waiting for device
Click to expand...
Click to collapse
Are running the bat file as an admin? right click>run as admin
ya ran in admin also tried to run adb just to see if i can connect device but nothing. computer is connecting just not the device with adb/fastboot
2 things to try:
1) Run the bat file in an actual command window to see the output, or edit it and add pause at the end (likely device not found or fastboot isn't in the path)
2) Manually force a driver (I believe the fastboot driver from the Android SDK should be able to be forced, since this is just a Tegra 4 chipset)
To ensure its ready to go, you should be able to write:
"fastboot devices"
And see that there is a device there. I will try when I get my cable
Thanks I'll try out more tomorrow.
For me i have to add absolute filepath to script if i run it as admin
if the folder is under C:\ it is: C:\r1-mojo-superboot-mmm\fastboot-windows.exe boot boot.superboot.img
But just telling me "waiting for device". driver is installed properly and device is recognized as usb device.
saenta said:
For me i have to add absolute filepath to script if i run it as admin
if the folder is under C:\ it is: C:\r1-mojo-superboot-mmm\fastboot-windows.exe boot boot.superboot.img
But just telling me "waiting for device". driver is installed properly and device is recognized as usb device.
Click to expand...
Click to collapse
Could you try editing the batch file, replacing 'fastboot boot' with 'fastboot -i 0x0738 boot'? I don't think that should be necessary on Windows (I use a Mac) but it's worth a try!
P
paulobrien said:
Could you try editing the batch file, replacing 'fastboot boot' with 'fastboot -i 0x0738 boot'? I don't think that should be necessary on Windows (I use a Mac) but it's worth a try!
P
Click to expand...
Click to collapse
Perfect thanks that worked!
saenta said:
Perfect thanks that worked!
Click to expand...
Click to collapse
Ah, awesome, i'll update the script in the zip.
P
Hi i'm facing a problem and i see i'm the only one for the moment
i use a usb 3 male male cable but when i plug into the mojo and pc nothing hapens no sound of windows who say there is an usb plug so maybe it's because i use a usb 3 cable ( the cable is pluged into the usb 2 port )
and the other thing it's when i reboot into bootloader the device reboot normaly i don't see "Key driver not found.. Booting OS"
Download updated to r2 (Windows fix).
P
Dead-neM said:
Hi i'm facing a problem and i see i'm the only one for the moment
i use a usb 3 male male cable but when i plug into the mojo and pc nothing hapens no sound of windows who say there is an usb plug so maybe it's because i use a usb 3 cable ( the cable is pluged into the usb 2 port )
and the other thing it's when i reboot into bootloader the device reboot normaly i don't see "Key driver not found.. Booting OS"
Click to expand...
Click to collapse
Have you followed the instructions precisely or are you trying to do it a different way?
P
paulobrien said:
Have you followed the instructions precisely or are you trying to do it a different way?
P
Click to expand...
Click to collapse
Thanks for reply
Yes i think i'm doing it exactly like it's described
I have no problem with my phone and driver but the mojo looks dead with usb slave
Dead-neM said:
Thanks for reply
Yes i think i'm doing it exactly like it's described
I have no problem with my phone and driver but the mojo looks dead with usb slave
Click to expand...
Click to collapse
You won't see it when you plug it in, open device manager you will see fastboot device without driver.
To install the Mojo driver on Windows 8 you need to disable driver signature checking, else install will fail.
Your USB3 cable is backward compatible to USB2.
Have you taken mojo from power? if you only reboot bootloader you won't see anything.
Hello,
I need the help of the XDA community. I'm very new to Android and Ive gotten myself in quite a bit of trouble.
I rooted my phone recently and decided to unroot the phone in order to trade with another user. In the process, my phone is wiped clean, and attempting to use RUU has left me relocked with S-On. I currently have no OS on the device. Attempting to run RUU gets no results, as I am met with Error 155 before I get any progress when the phone starts the "Sending" process. My phone will go into bootloader and it is recognized as a fastboot device by my PC, but not as an ADB device. I have the info from my bootloader menu below.
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
OS-5.12.502.2
My phone is an AT&T HTC ONE M7, 32 GB. I am at a loss and I've tried researching. Any help would be greatly appreciated.
Thanks
Juice Jones said:
Hello,
I need the help of the XDA community. I'm very new to Android and Ive gotten myself in quite a bit of trouble.
I rooted my phone recently and decided to unroot the phone in order to trade with another user. In the process, my phone is wiped clean, and attempting to use RUU has left me relocked with S-On. I currently have no OS on the device. Attempting to run RUU gets no results, as I am met with Error 155 before I get any progress when the phone starts the "Sending" process. My phone will go into bootloader and it is recognized as a fastboot device by my PC, but not as an ADB device. I have the info from my bootloader menu below.
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
OS-5.12.502.2
My phone is an AT&T HTC ONE M7, 32 GB. I am at a loss and I've tried researching. Any help would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
My guess you tried to run a RUU of a lower version than what is on your phone that is why you got the error 155. ADB does not work if there is no OS because it needs USB Debugging enabled in the OS but it works with a custom recovery like TWRP. Download the Guru Reset 5.12.502.2 and push it to your phone with the following procedure:
Originally posted by @alrayHTC ONE M7_U/M7_UL - ADB PUSH & FLASH A ROM - DETAILED INSTRUCTIONS
Prerequisites:
You need ADB and FASTBOOT on your computer,
either by installing the Android SDK or Minimal ADB and FASTBOOT
You need to know how to start a fastboot/adb command prompt:
To open a command window prompt, in Windows go to Start Menu --> ''Run'' then type cmd. Change the directory to the ADB folder on your machine:
If using the default install location for the SDK:
Code:
cd C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools
If using the default install location of Minimal ADB and FASTBOOT:
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
Or hold left shift + right click a blank space inside the folder where adb and fastboot are located and select ''Open command window here'' from the contextual menu.
{
"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"
}
You need TWRP recovery on your device.
We still recommend to use version 2.6.3.3 for all roms
except if another version is specified in the rom OP.
Use 2.7.1.1+ for roms that require "block:by-name" support (CM11)
Unlock bootloader if not already unlocked:
Thanks to Electroz for the video tutorial
Flash TWRP Recovery:
Make sure the recovery.img file is in the same folder where adb and fastboot are located
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
reboot phone in bootloader mode
Flash the recovery:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
You need your HTC drivers correctly installed on your PC:
If not, follow this guide (thanks to nkk71):
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Procedure:
Make sure the ROM you want to flash is in the same folder where ADB and FASTBOOT are.
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
Here is a list of the HTC M7 roms. Some other roms can be found here.
Connect your phone to computer using usb cable
(if not using the official HTC USB calble, make sure
you are using a USB data cable and not only a charging
cable. Data cables have 4 contacts: 5V, GND, DATA+, DATA-.
Charging cable only have 5V and GND contact and will not work)
Reboot phone in recovery mode (TWRP):
If phone is booted in OS:
Code:
adb reboot recovery
if not booted or bootlooping, hold power button + volume down until phone boot in bootloader mode
then select BOOTLOADER then RECOVERY using volume up/down to navigate and power button to select.
Make sure your phone is booted in TWRP main menu:
transfer the rom to your /sdcard folder:
Code:
adb push name_of_rom.zip /sdcard/
Wait for the zip file to transfer, this can take several minutes (5-15) and there is no progress bar, the command prompt will be unresponsive for that duration. When the command prompt is responsive again and display how much bytes transferred in X seconds, the transfer is completed:
In TWRP main menu, select ''INSTALL''
Browse the installation menu and select your rom zip file inside /sdcard folder:
Swipe to confirm you want to flash the rom
Reboot phone
Click to expand...
Click to collapse
Click to expand...
Click to collapse
majmoz said:
My guess you tried to run a RUU of a lower version than what is on your phone that is why you got the error 155. ADB does not work if there is no OS because it needs USB Debugging enabled in the OS but it works with a custom recovery like TWRP. Download the Guru Reset 5.12.502.2 and push it to your phone with the following procedure:
Click to expand...
Click to collapse
So I attempted to follow your instructions, got my bootloader unlocked and TWRP installed. Got the Guru Reset pushed onto my phone storage. Now I'm getting an error when trying to install. "Error Flashing zip" "E: Unable to mount '/cache' " "E: Unable to mount '/data/ " "E:Unable to mount storage. "
Not sure where to go from here.
Juice Jones said:
So I attempted to follow your instructions, got my bootloader unlocked and TWRP installed. Got the Guru Reset pushed onto my phone storage. Now I'm getting an error when trying to install. "Error Flashing zip" "E: Unable to mount '/cache' " "E: Unable to mount '/data/ " "E:Unable to mount storage. "
Not sure where to go from here.
Click to expand...
Click to collapse
Are you using TWRP 2.6.3.3? If not, flash it first.
In TWRP under Wipe, there’s an Advanced Wipe menu. Go there and select Data, format the partition. Downside you will have to push the Guru Reset back to the phone.
TWRP 3.1.1-0 for Samsung Galaxy J5 2016
with Aroma support
by Lemlis
{
"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"
}
-------------------------------------------------
J510FN--OK!
J510GN--OK!
J510MN--OK!
J510H--OK!
J510F--OK!
-------------------------------------------------
Description:
TWRP3.1.1-0 :
Based on Official TWRP-3.1.1-0 seed
Boot.img base J510FN
What's new in 3.1.1-0
Code:
Update changues twrp 3.1.1-0
[COLOR="DarkGreen"][B]Removed warning[/B][/COLOR] [COLOR="Red"]Recovery is not seandroid enforced[/COLOR]
Support Aroma installer
MTP--ok!
ADB Backup Support
Backup EFS
Wipe Persist
Wipe Preload
Mount Efs/Preload/Firmware-modem/firmware/Persist
and more features
-------------------------------------------------
Bugs:
------
ADB works great!
You can copy Copy TWRP Backups to Your PC or Copy TWRP Backups Back to Your Phone using ADB
How to Copy check post #2
-------------------------------------------------
How to install .tar:
Code:
1. Install device usb drivers and Odin
In Phone Developer options - On OEM unlock
2. Power off the device.
3. Boot to download mode (VOLUME DOWN/HOME/POWER).
4. Volume UP once.
5. Open Odin as an administrator, connect the device to a usb port,
and make sure a blue button appears and says "Added" in description on the left.
6. Select AP or PDA for older Odin and search for the downloaded tar file.
7. Uncheck auto reboot from the second tab.
8. Start flash and you should see the succeeded command.
9. Unplug the device and remove the battery.
10. Reboot to TWRP and enjoy! (VOLUME UP/HOME/POWER).
How to install .img:
Code:
1.Download the latest TWRP image file (.img)
2.Boot into the TWRP recovery.(VOLUME UP/HOME/POWER)
3.Go to install and find and select the Images button.(At right-bottom)
4.Browse to the image that you downloaded and select it.
5.Choose recovery and swipe to flash.
You are done!
-------------------------------------------------
Download for install with Odin .tar:
TWRP_3.1.1-0.tar
Download for Install Image from TWRP .img:
TWRP_3.1.1-0.img
-----------------------------------------------------------------------------------------------------Credits:
@By Zonik Aroma support
@GeneticEnginer--MTP fix
@SpamMachine --Removed warning
TWRP v3.1.0 will Bring Support for Backing up Directly to your PC
--------------------------------
What should I back up in TWRP?
--------------------------------
TWRP Backup & Restore Tool
How to Copy TWRP Backups to Your PC1.First, ensure that you have the latest version of ADB installed . If you do, head to your ADB folder on your PC and Shift+Right Click on an empty space in the window. Choose “Open a Command Prompt Here”.
2.Boot your phone into TWRP’s recovery (VOLUME UP/HOME/POWER)
3.Plug your phone into your PC with a USB cable. In your command prompt, run the following command to ensure your device is connected and recognized by ADB:
Code:
adb devices
You should see the serial number of your device pop up, which indicates it is connected
4.Now, just run this command to copy your TWRP folder to your computer:
If your backup is placed in internall storage this comand:
Code:
adb pull /sdcard/TWRP TWRP
If your backup is placed in externall SD storage this comand:
Code:
adb pull /external_sd/TWRP TWRP
This will “pull” your TWRP folder into your ADB folder on your PC. This will take a while, so be patient and wait until you see the command prompt re-appear.
When it’s done, you can close the Command Prompt window, disconnect your device, and reboot into Android. You should now feel safe wiping your phone, because all your TWRP backups are stored safely on your computer.
--------------------------------
How to Copy TWRP Backups Back to Your Phone
Boot back into TWRP’s recovery environment on your phone and connect it to your PC with a USB cable. On your PC, head to your ADB folder and Shift+Right Click on an empty space in the window to “Open a Command Prompt Here”.
In the command prompt, run:
If you want put backup in internall storage this comand:
Code:
adb push TWRP /sdcard/TWRP
If you want put backup in externall SD storage this comand:
Code:
adb push TWRP /external_sd/TWRP
This will copy the TWRP folder in your ADB folder–the backups we copied in the first section of this guide–back to your phone. Again, this will take a while, so give it time and wait for the command prompt to re-appear before continuing.
lemlis said:
Again, this will take a while, so give it time and wait for the command prompt to re-appear before continuing.
Click to expand...
Click to collapse
Thanks a lot!
I will test it on J510H.
It's perfectly work on J510H :good:
I post it on 4PDA.
Good luck
lemlis said:
TWRP v3.1.0 will Bring Support for Backing up Directly to your PC
--------------------------------
What should I back up in TWRP?
--------------------------------
How to Copy TWRP Backups to Your PC
1.First, ensure that you have the latest version of ADB installed . If you do, head to your ADB folder on your PC and Shift+Right Click on an empty space in the window. Choose “Open a Command Prompt Here”.
2.Boot your phone into TWRP’s recovery (VOLUME UP/HOME/POWER)
3.Plug your phone into your PC with a USB cable. In your command prompt, run the following command to ensure your device is connected and recognized by ADB:
You should see the serial number of your device pop up, which indicates it is connected
4.Now, just run this command to copy your TWRP folder to your computer:
If your backup is placed in internall storage this comand:
If your backup is placed in externall SD storage this comand:
This will “pull” your TWRP folder into your ADB folder on your PC. This will take a while, so be patient and wait until you see the command prompt re-appear.
When it’s done, you can close the Command Prompt window, disconnect your device, and reboot into Android. You should now feel safe wiping your phone, because all your TWRP backups are stored safely on your computer.
--------------------------------
How to Copy TWRP Backups Back to Your Phone
Boot back into TWRP’s recovery environment on your phone and connect it to your PC with a USB cable. On your PC, head to your ADB folder and Shift+Right Click on an empty space in the window to “Open a Command Prompt Here”.
In the command prompt, run:
If you want put backup in internall storage this comand:
If you want put backup in externall SD storage this comand:
This will copy the TWRP folder in your ADB folder–the backups we copied in the first section of this guide–back to your phone. Again, this will take a while, so give it time and wait for the command prompt to re-appear before continuing.
Click to expand...
Click to collapse
Any new roms coming soon? I want something with aosp look
J510F Working Fine !!
So fast! Lithuania = gods
Telepracity said:
So fast! Lithuania = gods
Click to expand...
Click to collapse
He is an Awesome man!
MN maybe work ?
lemlis, maybe you should base it on harpia (moto g4 play) instead of athene (moto g4) as the g4 play as got exactly same specs.
Good job @lemlis
Edit : Working fine in J5 2015 . I try add mode download in recovery
By Zonik said:
Good job @lemlis
Edit : Working fine in J5 2015 . I try add mode download in recovery
Click to expand...
Click to collapse
mtp and download mode
No F2FS button
umm where can i get the stock recovery? i really need it bcoz i really dont want to root i thought twrp can fix my 32 gb sd card but it did not fix it so i want to return to stock recovery.
888_icon said:
umm where can i get the stock recovery? i really need it bcoz i really dont want to root i thought twrp can fix my 32 gb sd card but it did not fix it so i want to return to stock recovery.
Click to expand...
Click to collapse
In my thread there is a link to all twrp
TheWalkingSans said:
In my thread there is a link to all twrp
Click to expand...
Click to collapse
No i just need the stock recovery.img not twrp of j5 2016 i dont want to download the stock rom bcoz the file is too large
888_icon said:
where can i get the stock recovery?
Click to expand...
Click to collapse
If you want get somthing you must specify your model Phone and firmware version.
There is no extrasensory individuals,who can see at a distance
lemlis said:
If you want get somthing you must specify your model Phone and firmware version.
There is no extrasensory individuals,who can see at a distance
Click to expand...
Click to collapse
ohhh i see its SM-J510GN i just really need the stock recovery.img thats all
888_icon said:
ohhh i see its SM-J510GN i just really need the stock recovery.img thats all
Click to expand...
Click to collapse
bootloader and firmware version wich you use???
lemlis said:
bootloader and firmware version wich you use???
Click to expand...
Click to collapse
umm i dunno whats a bootloader and the firmware is J510GNDXU2APK2
Hello,
I want to root and install recovery to my device. Does my device J510L (6.0.1) use this recovery?
Please guide me the way to do it on J510L. Thx.
Hi guys, I'm here to learn something about Android Security System.
I have this Sapphire TV BOX
model: DWI259S / UIW4020ETI / UIW4020ETI2 (Sapphire)
SoC: Broadcom BCM7271
The goal of this post is to understand how I can gain root access on this device
I know how to turn it in recovery mode .
if you are interested you can read this Reddit post from ams_sharif
"You can boot to recovery by switching the unit off ( the black button in the back), then while holding the power button (the one on the side, next to the pair button) turn the set top box on until the recovery shows up."
This is what I see.
{
"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"
}
I tried to flash an update.zip in order to see if I can execute command through any script, but the verification of the signature fails.
I tried to click on "Apply update from USB" (that is adb sideload) , but connecting the tv box on the pc nothing happen, no device found neither with "adb devices"
I tried also to click on "Reboot to bootloader" but "fastboot devices" command return nod devices connected.
My idea was to read the recovery image from fastboot extract it and try to compile my own TWRP
Do you have any suggestions to guide me in the right way?
@element14
When you enter
Code:
adb devices
and don't see an entry listed under the “List of devices” section, then your device isn't connected to PC.
Same is case when you enter
Code:
fastboot devices
Recovery option "Apply update from USB" isn't equal to "adb sideload". This option assumes the Update.Zip you want to flash is located on USB-device connected with your TV box.
With regards to rooting your TV box you can try to flash Chainfire's SuperSu Pro.
BTW: TWRP isn't a recovery image you compile in order to flash, it's merely a touch-enabled replacement for device's Stock Recovery menu as shown by you
Example screenshot:
jwoegerbauer said:
@element14
When you enter
Code:
adb devices
and don't see an entry listed under the “List of devices” section, then your device isn't connected to PC.
Same is case when you enter
Code:
fastboot devices
Recovery option "Apply update from USB" isn't equal to "adb sideload". This option assumes the Update.Zip you want to flash is located on USB-device connected with your TV box.
Click to expand...
Click to collapse
I tried to flash a custom script that use the
Code:
u_print()
function , but the signature verification fails i get an
Code:
errorr:21
jwoegerbauer said:
With regards to rooting your TV box you can try to flash Chainfire's SuperSu Pro[/url].
Click to expand...
Click to collapse
Are you sure that I can flash an unsigned zip like superSu , with a stock recovery and locked bootloader ?
jwoegerbauer said:
BTW: TWRP isn't a recovery image you compile in order to flash, it's merely a touch-enabled replacement for device's Stock Recovery menu as shown by you
Click to expand...
Click to collapse
The TWRP is an open source project , all the source code is avaiable. But to have it works , you need the original kernel .
I tought , If I can unlock the bootloader I can read the image of the recvoery.img and from it extarct the kernel
Thanks for your answer.
@ element14
did you manage to make the device usebale?
Hello, i am also interested to reset\flash this device but I couldn't find any useful guide, did you manage to root it or flash it, I want to use it as android STB.
As long as you can establish an USB-connection ( read: ADB connection ) then you can root any device's Android OS, otherwise NOT.
Any updates on this topic? It would be great to know if someone was able to root it.
If this is the etisalat version of this box I have gotten APKs to work on it.
xilogofficial said:
If this is the etisalat version of this box I have gotten APKs to work on it.
Click to expand...
Click to collapse
What apk exactly?what you can do with this apk? And how you installed?
element14 said:
What apk exactly?what you can do with this apk? And how you installed?
Click to expand...
Click to collapse
I think it lets you install any APK on the device. Check https://emiratestel.github.io/website
There is only one port. Is there any other way? And how can i play videos from usb
xilogofficial said:
I think it lets you install any APK on the device. My method:
Going to apps list:
- insert usb
- click browse
- go up to internal storage, press ok, click Apps
part 1
- go to apps list, keep usb inserted
- scroll to Files, click it, click open
- if it opens skip to part 2
- else it will crash and show the first time boot
- go to apps list again while keeping usb inserted
- open files again
part 2
- connect a mouse to other USB port, navigate into the USB and into where you placed your APKs
- double click the apk to install it
- on first time install, it will show an error about unknown sources
- click settings on the prompt
- enable all sources shown
- continue installing the app
Click to expand...
Click to collapse
There is only one usb port. Is there any other way? And how can i play videos from usb
there's another on the bottom, or use a USB hub.
you can't play videos from USB without installing third party apps.
xilogofficial said:
If this is the etisalat version of this box I have gotten APKs to work on it.
Click to expand...
Click to collapse
Good Day! Appreciate your support . Dear Exactly Etisalat TV box model: DWI259S, but it is locked on Etisalat home page with their logo as I don't have Etisalat subscription any more, in that situation how possible to browse an APK file as you said in below steps? 2nd thing there is no standard Firmware available by Manufacturer (Technicolor), Please make a video or at least solve with help of photos and help us close this topic. Till date solution is not yet provided, Please help, Thanks and appreciate your support
.
element14 said:
Hi guys, I'm here to learn something about Android Security System.
I have this Sapphire TV BOX
model: DWI259S / UIW4020ETI / UIW4020ETI2 (Sapphire)
SoC: Broadcom BCM7271
The goal of this post is to understand how I can gain root access on this device
I know how to turn it in recovery mode .
if you are interested you can read this Reddit post from ams_sharif
"You can boot to recovery by switching the unit off ( the black button in the back), then while holding the power button (the one on the side, next to the pair button) turn the set top box on until the recovery shows up."
This is what I see.
I tried to flash an update.zip in order to see if I can execute command through any script, but the verification of the signature fails.
I tried to click on "Apply update from USB" (that is adb sideload) , but connecting the tv box on the pc nothing happen, no device found neither with "adb devices"
I tried also to click on "Reboot to bootloader" but "fastboot devices" command return nod devices connected.
My idea was to read the recovery image from fastboot extract it and try to compile my own TWRP
Do you have any suggestions to guide me in the right way?
Click to expand...
Click to collapse
Any Luck dear, Please advise as I want the same solution and receive same error 21.
engr.sys said:
Any Luck dear, Please advise as I want the same solution and receive same error 21.
Click to expand...
Click to collapse
Kindly Join our Discord Server Link :https://discord.gg/sbFnauNTWy
I can help u there
Hi
Can you please share the APK please ?
any update on this? did anyone managed to finally root this device or least sideload and apk?
b1acktiger said:
Hi
Can you please share the APK please ?
Click to expand...
Click to collapse
PM Me
Can you please share the APK please ?
Since there is no proper information about unlocking the bootloader for the newer versions of Oneplus Nord 2, this is how I got it to unlock and actually work.
For my system it did reset the device, clearing all the files and factory restoring the device, just make sure to make a backup before you do anything.
Just like any other post, no warranties or anything, this is all at your own risk.
1: Make sure to enable OEM unlocking and ADB Debugging in the developer options
1.1: To have these options, first go to About phone > Version
1.2: Keep tapping the "Build number" to unlock the developer options
1.3: Navigate back to settings and open Additional Settings. There you will find the Developer Options.
2: Install: Platform tools: https://androidfilehost.com/?fid=17248734326145690420
3: Install: MediaTek Preloader USB VCOM drivers: https://drive.google.com/file/d/1TPbW-v9-yOrzH15OaHmsPQad420mULeF/view
4: CMD to the root of the platform tools and use the command "adb reboot bootloader"
5: While in the weird tiny screen, validate that your device is there by typing "fastboot devices"
6: If so, type fastboot flashing unlock
7: Profit.
Hope this helps any other people searching for a proper way to do this.
OMG I spent hours searching for a working fastboot driver. Unlocked successfully! I owe you a beer man drop me your paypal
meterpreter said:
OMG I spent hours searching for a working fastboot driver. Unlocked successfully! I owe you a beer man drop me your paypal
Click to expand...
Click to collapse
The cheers is already great, hope they release a working stock rom soon so we can finally have some custom roms going!
Eastw1ng said:
The cheers is already great, hope they release a working stock rom soon so we can finally have some custom roms going!
Click to expand...
Click to collapse
I hope so too. I would really like to put lineage on this thing, probably the only os that can make a usable device out of this actually very good phone
Unlocking the bootloader requires two settings to be made in Android's Developer Options:
ADB Debugging
Allow OEM Unlock
@Eastw1ng, as obvious as this may be once you remember, unlocking the bootloader is something most people don't do very often - it might make sense to include that in the OP
@NetSoerfer, you're not wrong, quickly added it to the start.
I have a issue, Fastboot cant't find mobiledevice in win10. Adb commands working great. Debugging and oem unlock options enabled.
Tried:
1. different usb ports, cables and PC
2. Oneplus, Google and Mediatek USB drivers. With ADB or Bootloader interface.
3. Reinstalling PC USB drivers.
Am i missing out something?
CapnRene said:
I have a issue, Fastboot cant't find mobiledevice in win10. Adb commands working great. Debugging and oem unlock options enabled.
Tried:
1. different usb ports, cables and PC
2. Oneplus, Google and Mediatek USB drivers. With ADB or Bootloader interface.
3. Reinstalling PC USB drivers.
Am i missing out something?
Click to expand...
Click to collapse
use latest platform tools
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
HofaTheRipper said:
use latest platform tools
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Click to expand...
Click to collapse
Hmmm, it worked, I think last one was ver. 30. Last year I downloaded "15 second ADB". It seems it made a mess in my ADB directories. Had to delete few folders and path from win10 Environment Variables. Made new folder and added new path.
I think it is last time when I use some kind "ADB installer".
I wonder if Android Studios didn't come with it automatically? Because I reinstalled that and it didn't work?(it might be that 15 sec installer messed up paths)
CapnRene said:
Hmmm, it worked, I think last one was ver. 30. Last year I downloaded "15 second ADB". It seems it made a mess in my ADB directories. Had to delete few folders and path from win10 Environment Variables. Made new folder and added new path.
I think it is last time when I use some kind "ADB installer".
I wonder if Android Studios didn't come with it automatically? Because I reinstalled that and it didn't work?(it might be that 15 sec installer messed up paths)
Click to expand...
Click to collapse
Can you tell me how to install these drivers I tried but still not detecting
You have same issue that adb is detecting phones but fastboot not?
There is no installer by google. You just replace files for updating.
For first make sure CMD doesn't find multiple locations for ADB. Type in CMD where adb. Be sure that it finds correct folder where is platform tools ver 31.0.3!
If it's wrong then you need insert new Path in system variables or changes whole folder where 'where adb' indcates. Also double check that oem unlocking is enabled in developer options on phone.
This is my CMD exaple:
X:\Users\XXX>where adb
X:\platform-tools\adb.exe
And system variables
{
"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"
}
CapnRene said:
You have same issue that adb is detecting phones but fastboot not?
There is no installer by google. You just replace files for updating.
For first make sure CMD doesn't find multiple locations for ADB. Type in CMD where adb. Be sure that it finds correct folder where is platform tools ver 31.0.3!
If it's wrong then you need insert new Path in system variables or changes whole folder where 'where adb' indcates. Also double check that oem unlocking is enabled in developer options on phone.
This is my CMD exaple:
C:\Users\Rene>where adb
C:\platform-tools\adb.exe
And system variables
View attachment 5420349
Click to expand...
Click to collapse
I have done all the things still it's not detecting but surprisingly it's detecting my old one plus 6 easily.
On another lappy where I . using zorin os ubuntu based os simple terminal commands installed android platform tool on Linux and I got easily detected Nord with same commands.
But anyway thanks
CapnRene said:
You have same issue that adb is detecting phones but fastboot not?
There is no installer by google. You just replace files for updating.
For first make sure CMD doesn't find multiple locations for ADB. Type in CMD where adb. Be sure that it finds correct folder where is platform tools ver 31.0.3!
If it's wrong then you need insert new Path in system variables or changes whole folder where 'where adb' indcates. Also double check that oem unlocking is enabled in developer options on phone.
This is my CMD exaple:
C:\Users\Rene>where adb
C:\platform-tools\adb.exe
And system variables
View attachment 5420349
Click to expand...
Click to collapse
Can you tell me twrp given in another thread is working on oos11.3 v10 ?
pankspoo said:
I have done all the things still it's not detecting but surprisingly it's detecting my old one plus 6 easily.
On another lappy where I . using zorin os ubuntu based os simple terminal commands installed android platform tool on Linux and I got easily detected Nord with same commands.
But anyway thanks
Click to expand...
Click to collapse
Have you tried installing these "MediaTek Preloader USB VCOM drivers"? Quite often it's a driver issue and you'll be able to see in the device manager if something's not properly loading the drivers.
pankspoo said:
Can you tell me twrp given in another thread is working on oos11.3 v10 ?
Click to expand...
Click to collapse
It is working for me on v10, just make sure to have the v10 bootloader on hand, it might require a reflash of that after the recovery patch
Eastw1ng said:
Have you tried installing these "MediaTek Preloader USB VCOM drivers"? Quite often it's a driver issue and you'll be able to see in the device manager if something's not properly loading the drivers.
Click to expand...
Click to collapse
Yes installed
Eastw1ng said:
It is working for me on v10, just make sure to have the v10 bootloader on hand, it might require a reflash of that after the recovery patch
Click to expand...
Click to collapse
V10 bootloader means boot.img? If you have that please send me
pankspoo said:
V10 bootloader means boot.img? If you have that please send me
Click to expand...
Click to collapse
You can find the images sakarya posted before: https://forum.xda-developers.com/t/root-tool-oneplus-nord-2-oxygen-11-3-dn2103_11_a-xx-eea.4332959/
pankspoo said:
Yes installed
Click to expand...
Click to collapse
Alright, well just put it into fastboot mode and check your device manager, does it show any devices that are not properly installed? If so, try to resolve it from there
Eastw1ng said:
You can find the images sakarya posted before: https://forum.xda-developers.com/t/root-tool-oneplus-nord-2-oxygen-11-3-dn2103_11_a-xx-eea.4332959/
Click to expand...
Click to collapse
Thanks