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.
Related
I have followed the guide, did the edit to the android_winusb.ini and the 0x54c in the adb_usb.ini but I still can't get it to show up as a device when I type adb devices (did restart ADB via adb kill-server after editing the files)
It took me awhile to change the driver for Win 7 recognise it as "Android Composite ADB Interface". I had to use
Code:
%CompositeAdbInterface% = USB_Install, USB\VID_054C&PID_05B4
otherwise it kept saying it couldn't find a compatible driver
Model is SGPT112GB/S
Any ideas?
try this "Auto-Installer". In most cases it has helped.
http://forum.xda-developers.com/showthread.php?t=1488822
Tried it already, didn't appear to work, plus as I ran ADB with it, it said it was out of date
Go into System Devices whilst the Tab is connected via USB, delete and uninstall the device there and the re-install. Thats what i'd to do because the first time I installed it I missed the ox54c bit and it only half installed.
Tried that, adb still doesn't list any devices :/ ADB definitely works as it picks up my phone (X10 mini pro) when I plug that in
Some pictures can help, adb manager, device manager and probably de ini file.
Is your Tablet showing up in Device Manager and if so what as ?
defsix said:
Is your Tablet showing up in Device Manager and if so what as ?
Click to expand...
Click to collapse
{
"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"
}
Before it was showing up under Portable Devices. So I followed the instructions to Update the driver and point to the inf file, but it kept saying couldn't find a compatible driver, so I went into the properties for it and checked the Hardware ID, and it wasn't the same as it said in the guide so I changed it in the inf file, once that was done, I was able to update the driver.
confuserr said:
Before it was showing up under Portable Devices. So I followed the instructions to Update the driver and point to the inf file, but it kept saying couldn't find a compatible driver, so I went into the properties for it and checked the Hardware ID, and it wasn't the same as it said in the guide so I changed it in the inf file, once that was done, I was able to update the driver.
Click to expand...
Click to collapse
As stated in my automated installer, you need TWO devices to show up:
If you're not getting the portable device, you need the MTP driver.
Uninstall both devices and reinstall the drivers or manually force an update on them.
Which OS are you running?
Win 7 64bit, either it shows up under portable devices or under Android phone. Not both. Ive tried your installer but it still doesn't work :/ This probably sounds stupid but if i uninstall, to install again just replug the tablet back in right and do the driver update thing? If not, then maybe thats where im going wrong :S
Update: Ok uninstalled, tried your installer. Now only shows under portable
http://dl.dropbox.com/u/16892708/CloudShot/shot_12022012_001734.png
CMD prompt that opened afterwards: http://dl.dropbox.com/u/16892708/CloudShot/shot_12022012_001000.png
confuserr said:
Win 7 64bit, either it shows up under portable devices or under Android phone. Not both. Ive tried your installer but it still doesn't work :/ This probably sounds stupid but if i uninstall, to install again just replug the tablet back in right and do the driver update thing? If not, then maybe thats where im going wrong :S
Update: Ok uninstalled, tried your installer. Now only shows under portable
http://dl.dropbox.com/u/16892708/CloudShot/shot_12022012_001734.png
CMD prompt that opened afterwards: http://dl.dropbox.com/u/16892708/CloudShot/shot_12022012_001000.png
Click to expand...
Click to collapse
When you uninstall, did you check the box that says "Delete the driver software..."
Is USB debugging checked on your tablet? You have to have two items in Device Manager. One is to transfer files (MPT/Sony Tablet S under Portable Devices) and the other under an Android heading (ADB).
If you're plugging in the tablet with USB Debugging checked and nothing's showing up, something's wrong with your system. At the very least, you should get an unknown device. Go to "View" and check "Show hidden devices" and check to see if anything's there. Try another USB port.
Bottom line: you need both items.
I followed your video exactly, USB debugging is enabled.
As soon as I plug the tablet in, it looks for new software. It then says successfully installed and pops up with the auto play options. Under devices it shows up under "Portable Devices". If I do the Update Driver, choose the .inf file, it installs but then it no longer shows up under Portable Devices but instead I have the "Android Phone" category with the Composite ADB Interface.
When uninstalling, it only comes up with the checkbox asking delete driver software when I uninstall the ADB Interface one, not the tablet under "Portable Devices"
I have done "Show hidden devices" all that changes is it shows a category called "Non-Plug and Play Drivers"
Confuserr, Im in the exact same position - and on win 7 x64.
Ive done both SDK install and Automated, nothing works.
I never could update the usb drivers though as windows decides the one I have is perfectly good - will try your little trick.
As soon as i get it to work ill post here, just wanted you to know that your not alone in this..
//Cliff
---------- Post added at 04:29 PM ---------- Previous post was at 04:15 PM ----------
And a second later it works atleast in the device manager.
I did the USB driver install according to the guide in the root thread http://forum.xda-developers.com/showthread.php?t=1487020, now unistalled the drivers (2 times) and installed again pointing to the correct location (android/extras/usb_drivers/)
Ran the latest version of the exploit from above thread and done, successfully rooted - now i just need to figure out what to do with my new rights (except taking away social feed reader and speed it up a bit)
//cliff
I can only assume the problem lies in the fact that the ADB guide Sony posted http://www.kb.sony.com/selfservice/documentLink.do?externalId=C1024692
Says
Region
Canada
Latin America
United States
Products
SGPT11 Series
Click to expand...
Click to collapse
Where as my Region is United Kingdom and SGPT112GB/S but im just taking stabs in the dark now
I have reinstalled the entire SDK Manager and still having problems :/
Edit: I've sent an email to Sony, lets see what they reply with
for me it worked after the removal of the old drivers and then using the ones downloaded from google, untuched. My guess is that this will work for you aswell. Good luck /Cliff
confuserr said:
I can only assume the problem lies in the fact that the ADB guide Sony posted
Where as my Region is United Kingdom and SGPT112GB/S but im just taking stabs in the dark now
I have reinstalled the entire SDK Manager and still having problems
Click to expand...
Click to collapse
I don't think it is your region. I cannot get adb to recognize my tab either and I am in the US (not region related). The strange thing is, I was able to ROOT... I also noticed, that while the ROOT tool was running, adb recognized my device. So, when the ROOT tool paused and was awaiting for me to press any key, I decided to mess around with a few codes to see what happened. I input:
Code:
su
mount -o remount rw /system
cp /system/build.prop /sdcard
busybox /sbin/sh
reboot
Everything worked as it should have. While the tab was rebooting, I shout down the ROOT tool, and after the tab rebooted, everything seems to be working as it should.
I have NO CLUE what the hell was going on. But, it works now and that is all that matters to me... Now on to perfect the custom recovery...
UPDATE
I figured it out! It's something with windows. For some reason, it is not starting the adb server... Here is the solution:
In command prompt type (cd to the directory where your adb.exe is):
Code:
adb kill-server
then press enter
Then type:
Code:
adb start-server
then press enter
Then you can go ahead and type:
Code:
adb shell
then press enter
And now you are on your way!
Hi all I'm having problems with getting ADB to see my device and was hoping someone with more brains can help me to solve this problem. I've searched this as much as I can on XDA and Google in general but nothing I find works device specifically.
First setup: I'm running the brilliant ARHD 11.0 JB with build.prop tweaks on top of Siya 1.6.8 and I don't think that Mike and GM need any introduction since they are both household names in our forums.
My machine OS: 7 Ultimate 64
The drivers I've installed: (this might be a factor in the problem)
Latest Kies. I've also installed the s3 drivers when connecting the device in download mode. I have uninstalled Kies because it's unless after the device drivers have been installed IMHO.
The ADB I am trying to use: I downloaded the generic ADB since I think the bridge is generic and mentioning the platform is irrelevant. But it was not the one bundled into the SDK since its not necessary. I have run it as Admin
My problem: I have connected my phone with debug enabled and disabled Auto play but as soon as I "adb shell" in cmd (after cd the adb directory) I still get the "error: device not found" message.
I've tried what I can but can figure it out could someone with the brain. I wish I had please slap me around the room and point out my obvious error and set me on the right path or at least cry with me in my frustration.
If I could get a devs input it would be awesome but if anyone could help me out, I would greatly appreciate it.
Please tell me if I've ommited any important info.
Thanx guys!
CM
christophermaisch said:
Hi all I'm having problems with getting ADB to see my device and was hoping someone with more brains can help me to solve this problem. I've searched this as much as I can on XDA and Google in general but nothing I find works device specifically.
First setup: I'm running the brilliant ARHD 11.0 JB with build.prop tweaks on top of Siya 1.6.8 and I don't think that Mike and GM need any introduction since they are both household names in our forums.
My machine OS: 7 Ultimate 64
The drivers I've installed: (this might be a factor in the problem)
Latest Kies. I've also installed the s3 drivers when connecting the device in download mode. I have uninstalled Kies because it's unless after the device drivers have been installed IMHO.
The ADB I am trying to use: I downloaded the generic ADB since I think the bridge is generic and mentioning the platform is irrelevant. But it was not the one bundled into the SDK since its not necessary. I have run it as Admin
My problem: I have connected my phone with debug enabled and disabled Auto play but as soon as I "adb shell" in cmd (after cd the adb directory) I still get the "error: device not found" message.
I've tried what I can but can figure it out could someone with the brain. I wish I had please slap me around the room and point out my obvious error and set me on the right path or at least cry with me in my frustration.
If I could get a devs input it would be awesome but if anyone could help me out, I would greatly appreciate it.
Please tell me if I've ommited any important info.
Thanx guys!
CM
Click to expand...
Click to collapse
Your problem determinated drivers , install drivers for samsung devices, reboot your pc, connect your device to your pc , expect driver installation , then check if updated , then if the sdk is installed correctly , adb devices.... USB Debugging enabled ......
i had an isssue last night with adb...
unplug phone from pc and turn off and then on usb debuging on the phone...
enter cmd mode on pc, then
adb kill-server
adb start-server
adb devices
then hopefully it will show the device is connected....
p.s. drivers should be installed and checked, this step it is mandatory....
hope it helps ...
Thank you both for you input but nothing works unfortunately. I'll continue the search thanx again though
May this help connect your usb to direct motherboard port. Do not use usb hub if you are
Sent from my GT-I9300 using xda premium
christophermaisch said:
Thank you both for you input but nothing works unfortunately. I'll continue the search thanx again though
Click to expand...
Click to collapse
Debug/test apps on device over the air, no cable. Must-have developer tool. WiFi ADB
You just installed the "adb" driver for your device. You still need to install the "fastboot" driver. It is the same driver, it just needs to be installed twice - once when your device is booted normally, and once when it is booted in fastboot mode. I personally would use the Universal Naked Drivers by 1wayjonny
When you have USB Debugging mode turned on on your phone and you connect to the computer and you look at Device Manager (Win+R, devmgmt.msc) do you see 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"
}
If you get Unknown Devices automatically expanded, then you haven't got the correct drivers installed.
You don't need to install Kies to have the latest drivers installed; you can extract them from the setup itself:
Download KIES and run the setup but don't do anything with it
Open up your Temporary Files folder: Win+R, %TEMP%
Look for the folders that start with a '{' and end with a '}' and have a bunch of letters, numbers and 4 hyphens in them and within this selection of folders find the folder that has its Date Modified timestamp matching the time you opened the KIES installer exe (in my case it was {44A91F3A-3D8C-43DE-A0BC-04E01C756397}). If you're in the right place, you'll find "Samsung Kies.msi".
Grab Less MSIérables, point it to Samsung Kies.msi and extract SAMSUNG_USB_Driver_for_Mobile_Phones.exe somewhere. lessmsi is a little slow...
You'll see a new folder "SourceDir" wherever you chose to extract the file, navigate through it until you find the EXE. Close the KIES installer and run the driver setup
Oh, rather than using some random version of ADB off the Internet, get it from Google themselves. The latest versions can be found in the platform-tools ZIPs for the SDK, but you don't need to install the SDK just for ADB: Open http://dl.google.com/android/repository/platform-tools_r14-windows.zip (14 is the latest version as of this post) and extract the three adb files from the ZIP and place them somewhere. This way you know it's not a problem of using an old ADB version.
You can also check to see if adbd is actually running on the phone when you plug it in by grabbing Terminal Emulator off the market and running: "/system/bin/ps | grep adbd" (note: you only get grep if you have BusyBox instaled)
Finally, if you really can't get USB connections to work, then use https://play.google.com/store/apps/details?id=com.ttxapps.wifiadb&hl=en :\
christophermaisch said:
Thank you both for you input but nothing works unfortunately. I'll continue the search thanx again though
Click to expand...
Click to collapse
Hey,
I had the exact same problem. This Tutorial : http://goo.gl/OS3Vi worked for me.
Hope it helps
I am having some problem remove an Nandroid backup; (it is impossible to remove it either with Root Exporer or in the terminal as root (rm -rf blah)).
However, now I am trying to use ADB to get rid of it I installed adb and some new drivers for my I9300.
Looked through my phone debug-settings, checked if ADB found my phone (adb start-server, adb devices). Then I rebooted my phone into recovery via CWM - however - now my phone does not want to be found.
Windows Device Manager recognize the phone, but the drivers-icon are yellow-ish (not sure if this is how they are supposed to look). adb devices gives me nothing.
I could really use some help over here.
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!!!!!!
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 ?
Hello,
My phone felt down from the 6th floor through the elevator shaft, ending up really damaged: broken screen (fully black, top left corner partly chipped off) !
Yet, the phone is not completly dead:
- The alarm keeps ringing at each time I have scheduled (several each morning )
- I'm able to switch off the alarm by by swiping left through the bottom of the screen, or by pressing the on/off button
- when I plug phone to my PC (win10) I can hear the bip-bip typical of a device connection, but nothing else happens
- On a PC on which the phone had never been connected, Windows recognised the phone and installed the drivers, but again Windows doesn't ask me what to do with the phone
- bluetooth seems to be working as the phone is seen as available by other devices
I'm trying to find a solution to access some of the data in my phone. Primarily the DCIM folder.
I would like to reboot in fastboot mode, as I believe I may have USB debugging on.
However I don't seem to be able to switch off the phone or reboot it.
Any idea how I could switch off the phone? Enter fastboot.
Do you think I could access the phone screen using an OTG device plugged to my computer screen via HDMI. If yes, which OTG device should I purchase?
Any other idea?
As a last resort, do you think it is possible to fully ripp-off the phone, get the flash drive and mount it somewhere in a tool that could be pluggin via USB?
Surfinette said:
Hello,
My phone felt down from the 6th floor through the elevator shaft, ending up really damaged: broken screen (fully black, top left corner partly chipped off) !
Yet, the phone is not completly dead:
- The alarm keeps ringing at each time I have scheduled (several each morning )
- I'm able to switch off the alarm by by swiping left through the bottom of the screen, or by pressing the on/off button
- when I plug phone to my PC (win10) I can hear the bip-bip typical of a device connection, but nothing else happens
- On a PC on which the phone had never been connected, Windows recognised the phone and installed the drivers, but again Windows doesn't ask me what to do with the phone
- bluetooth seems to be working as the phone is seen as available by other devices
I'm trying to find a solution to access some of the data in my phone. Primarily the DCIM folder.
I would like to reboot in fastboot mode, as I believe I may have USB debugging on.
However I don't seem to be able to switch off the phone or reboot it.
Any idea how I could switch off the phone? Enter fastboot.
Do you think I could access the phone screen using an OTG device plugged to my computer screen via HDMI. If yes, which OTG device should I purchase?
Any other idea?
As a last resort, do you think it is possible to fully ripp-off the phone, get the flash drive and mount it somewhere in a tool that could be pluggin via USB?
Click to expand...
Click to collapse
Look for force reboot butto combination for your phone usually vol up/down + power button
The mounting option works but its quite advanced and you mmay need schematics or guess work lmao
You really don't want fastboot, you want ADB. Did you have ADB enabled before?
When it's connected to your Windows machines what is it showing? MTP (in File Explorer) or ADB?
Don't wait for Windows to ask questions!
Thank you for your help
When I connect my phone to the PC, there is just the connecting sound ("bip bip"), no ADB, no MTP
Since the phone screen is stuck to black, I don't know what's going on on the phone.
When first using the phone one year ago, I had activated ADB and used it to debloat the phone. I never removed ADB myself on the phone, but maybe it was deactivated (i don't know) after a system update. I would love to be able to check whether adb is still activated
When I type > adb devices in power shell with my OP plugged in, there is no device found.
So I believe this ADB option is off for me
Somehow USB debbugging must have been deactived
Also
Force-reboot doesn't seem to work
It may be that you don't have a Windows driver loaded.
Get UsbView.exe
The left pane should change as you disconnect/reconnect the USB cable.
Find the device that appears and disappears, select it, copy the contents of the right pane and post it here.
Renate said:
It may be that you don't have a Windows driver loaded.
Get UsbView.exe
The left pane should change as you disconnect/reconnect the USB cable.
Find the device that appears and disappears, select it, copy the contents of the right pane and post it here.
Click to expand...
Click to collapse
Thanks
Here is the screenshot (sorry my Windows OS is in French).
The new item when I plug my phone is :
[Loc23] DeviceConnected : Composite USB Device
{
"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"
}
Ça ne me dit rien. (It doesn't tell me anything.)
I need the information on the right side when you click on Loc23.
Renate said:
Ça ne me dit rien. (It doesn't tell me anything.)
I need the information on the right side when you click on Loc23.
Click to expand...
Click to collapse
Ha so sorry, still mixing up right and left
OMG, your device is showing as a MIDI interface.
Er, that's not good.
Did you root your device with Magisk? Do you have anything useful on your desktop, boot.img or the Magisk'ed version?
Did you have TWRP recovery or some other?
Renate said:
OMG, your device is showing as a MIDI interface.
Er, that's not good.
Did you root your device with Magisk? Do you have anything useful on your desktop, boot.img or the Magisk'ed version?
Did you have TWRP recovery or some other?
Click to expand...
Click to collapse
No, I've never rooted this device. Never even attempted (with this one), so no Magisk, etc. The only "tweak" I did with it was removing some bloatwares using adb (I did this one year ago, right after purchasing it).
A MIDI interface.... I don't know.... But an alarm clock, for sure
If we're talking about the OnePlus Nord 2, that's a MediaTek.
You could go to a cell phone repair place and let them put in a new screen.
You could buy a screen. You don't need to actually install it. You can just connect it to the old cable and leave it flopping.
I don't think that your device has video out (USB Type C alt mode of DP or HDMI or MHL)
You could pull a copy of your boot image using MTK Client.
You could get someone to give you a boot image or a Magisk'ed image.
A small tweak to the boot image would have it come up as ADB or MTP.
Renate said:
If we're talking about the OnePlus Nord 2, that's a MediaTek.
You could go to a cell phone repair place and let them put in a new screen.
You could buy a screen. You don't need to actually install it. You can just connect it to the old cable and leave it flopping.
I don't think that your device has video out (USB Type C alt mode of DP or HDMI or MHL)
You could pull a copy of your boot image using MTK Client.
You could get someone to give you a boot image or a Magisk'ed image.
A small tweak to the boot image would have it come up as ADB or MTP.
Click to expand...
Click to collapse
Thank you so much for your help.
Changing the screen is not an option, given my phone's current state of destruction... it looks like a miracle the alarm clock still works, and the phone is still responsive to wiping the screen to turn it off
I will have a look at MTK Client, but it may be beyond my skill. Would you have a link to a good tutorial? Also, what would be the "small" tweak needed to the boot image?
They call that format of a phone "candy bar", but that doesn't mean that you should nibble on the corner!
This is the open source (Python) MTK client: https://github.com/bkerler/mtkclient
Hey! Any of you OnePlus Nord2 owners have a boot image to share? A Magisk'ed boot image would be even better.