Code:
Deleting Cryption Meta Data
-- Copying media files...
Successfully copied meida files. [COLOR="Lime"]//"meida" is not a typo. By that I mean it's ACTUALLY spelled like that. :P[/COLOR]
# MANUAL MODE #
-- Updating application...
[COLOR="Red"]E:install_application_for_customer:Can't unmount
/preload
copy application failed[/COLOR]
-- Applying Multi-CSC...
Successfully applied multi-CSC.
[code]
I'm trying to unbrick my phone. Right now I'm stock recovery, download mode, and phone won't connect to PC. Notice I said "My phone" won't connect and not my PC won't recognize. I have the drivers, re-installed them countless times.
Is there some insta-flash zip file that I can put on my SD Card? I mean, when I had the G2, I was able to put some file called a PC10IMG.zip file on my SD card and that started as soon as I went to the bootloader. Does the Epic 4G Touch even have a bootloader?
Does anyone know where I might be able to get a JTag service online, because Mobile Tech Videos isn't responding to me. -_-
yes can someone please reply cause i think im in the same sitiation
I know this is late but did you get your issue resolved?
Wanting to root my new Telstra T-Hub 2, made by Technicolor.
There appears to be no USB drivers available (nothing via Google)
There also appears to be no way to get into the Download Mode for connection to Odin. (again nothing on Google)
So these two points have left me a bit lost.
It is running Android (GB) 2.3.7
Any one have any ideas????
Rabs_1976 said:
Wanting to root my new Telstra T-Hub 2, made by Technicolor.
There appears to be no USB drivers available (nothing via Google)
There also appears to be no way to get into the Download Mode for connection to Odin. (again nothing on Google)
So these two points have left me a bit lost.
It is running Android (GB) 2.3.7
Any one have any ideas????
Click to expand...
Click to collapse
I got ADB working on my T-Hub 2 by using the generic Google drivers, and edited the adb_usb.ini to just say 0x069B
So far I have problems rooting it.
wocko1 said:
I got ADB working on my T-Hub 2 by using the generic Google drivers, and edited the adb_usb.ini to just say 0x069B
So far I have problems rooting it.
Click to expand...
Click to collapse
BUMP
I have this Tablet as-well and having the same problem.
any ideas on the best way to root this thing?
wocko1 do you have any more details on how to got that far?
Thanks guys.
Rabs_1976 said:
Wanting to root my new Telstra T-Hub 2, made by Technicolor.
There appears to be no USB drivers available (nothing via Google)
There also appears to be no way to get into the Download Mode for connection to Odin. (again nothing on Google)
So these two points have left me a bit lost.
It is running Android (GB) 2.3.7
Any one have any ideas????
Click to expand...
Click to collapse
was it released in any other countries as another device?
even if we got root on it what can we do for a custom ROM if noone can dev for it
Madaz2 said:
was it released in any other countries as another device?
even if we got root on it what can we do for a custom ROM if noone can dev for it
Click to expand...
Click to collapse
We as owners/users of T-Hub 2 devices require sensible answers to important questions.
We need usb drivers for the T-Hub 2, either from Telstra or from Technicolor the manufacturer of the device so that we can attain " ROOT ACCESS" via a usb cable connection to a computer.
Unless we can get "ROOT ACCESS" we cannot move applications to an external SD card (32 GB in my case) or use Titanium Backup or certain Antivirus programs that require "ROOT ACCESS".
Please accept the undeniable fact that 1 Gigabyte of storage on the internal SD card is totally insufficient and pathetic, almost as pathetic as the fact that we are still stuck with "Gingerbread" which puts us three versions behind on Android which is now up to "JellyBean" v2.
The fact is, I believe the Android operating system running on the T-Hub 2 is, like all other versions of Android, based on the Linux kernel which is software using the GNU General Public License, which allows people to see, copy, use, and modify for their own needs.
If indeed I am correct in my assumption then Telstra/Technicolor could be in breach of a world standard which would mean that the proprietary blocks and gates that they have built to prevent access to the kernel on the T-Hub 2 are illegal.
Download Mode discovered...and more...
I thought this:
Hold "Volume-" and "Volume+" and "Power Button" boots into download mode. This is incorrect.
This gets you to recovery mode (which shows the Android robot fallen over).
Help!
wocko1 said:
I got ADB working on my T-Hub 2 by using the generic Google drivers, and edited the adb_usb.ini to just say 0x069B
So far I have problems rooting it.
Click to expand...
Click to collapse
Have been looking for the drivers everywhere, and so far none of them have worked. Even tried wireless adb to no avail. Also tried gingerbreak but still nothing. Sick of looking at the bloatware. Someone please help!
anyone had more success now that it has ICS 4.0.4
Yes, it can be rooted, but...
Hi,
Yes, much more progress. I've gained ADB root access using the restore method (i.e., restoring a backup which has been modified to install a file to a strange path, e.g,: ../../../system/bin/su), I recommend creating your own restore file rather than using one of the many out there and using it to install the necessary SU software to the appropriate locations.
If your device isn't detected by ADB, check that the device ID has been added to the ADB config file. The Thub2 ID is not recognised automatically. Also, when using fastboot remember to specify this ID or it won't find your THub.
The biggest issue with the THub2 is that Telstra have (in an oddly intelligent move) adopted SquashFS for the root file system; this is the FS used on things like linux liveCD's, and it's 100% RO (well, 99% RO . I have gotten around this in a number of ways. 1: I copied the SquashFS partition using DD to an Ext4 partition, then forced a dirty unmount of the SquashFS partiition chained to a mount of the new Ext4 partition to /system. RW access no problems, SU installs OK, but no persistence without forcing the dirty unmount each boot. 2: I copied the SquashFS partition to my ~ using DD, mounted and edited the partition, then re-flashed to the thub. worked much better, persistence across reboots, but dangerous and dodgy method that could risk many NANDs. 3: I cross-compiled a busybox containing UnionFS to Android.
Option 3 is by far the best option. UnionFS provides a transperent RW layer for SquashFS filesystems, writing the updates that couldn't be written to a RO system like squash to another partition (e.g., Ext4 on SD card). Mount a UnionFS system over /system to enable write access to the system. Maybe a better idea to mount it at /, but that raises other problems I couldn't be bothered dealing with.
I mentioned above that SquashFS is on 99% RO (in all my other experiences, it has been well and truly 100% RO, so this indicates something else a-going on that we should be able to use; I haven't looked into it yet.). For some reason, files installed to the Thub2 using the Restore method are persistent. Very useful, and should lead to a cleaner method.
So rooting so far:
Root with Restore method to install (1 & 2., SU bins, or 3., UnionFS Busybox)
Remount / as RW
-->Path 1 & 2
Dirty unmount /system && dirty unmount /system2 && mount /dev/block/etc.. NOTE: Once you dirty unmount /system, you will need to reference the location of the Ext4 partiition using the absolute (real) name of the device. You will also need to invoke busybox from a fully qualified path, eg. /data/local/tmp/busybox, as the internal /bin applications are no longer available (eg., mount).
-->Path 3
No need to umount /system, just mount the UnionFS system over the top.
Finally, for Paths 1 & 3...
Install Superuser application and be free!
So to sum up; I have easily rooted the Thub2 to root over ADB using a number of methods, however the Restore method works 100% of the time. I have mounted an Ext4 system to /system in order to have RW, but this isn't persistent. I have re-flashed the SquashFS with modified content, and this works a treat, but is RO and dangerous to NAND. I have mounted a UnionFS system over the SquashFS system, and this seems to provide the best all round performance.
I also wrote a short and nasty .apk to mount the UFS system without terminal, so that's a go as well.
Have fun pulling it all apart; I don't read these message boards, so I probably won't se any questions. More than enough to get rooted though.
THub Drivers and ADB Access
THUB 2 DRIVER INSTALLATION AND ADB ACCESS
This method sets out how to install drivers for the THub 2 and access ADB (Android Debug Bridge).
Access to ADB is the usual way that you use to Root an Android device.
Please note that not all ADB versions work. If you download and try a root method, you may have to copy the ADB.exe and support files across so that the root method can at least have a chance of working.
INSTALLING GOOGLE UNIVERSAL ANDROID DRIVERS
1. Ensure that Debugging has been enabled – Settings Developer options USB debugging and make sure the box is checked
2. The following is for Windows 7, other versions will be similar
3. Unzip the file and copy contents to a folder on the C: drive. I copied it to a folder I named THub
4. Plug the THub into your PC and it will try to find suitable drivers – some drivers may load and install but at least one will come up with “No driver found”
5. Open “Computer”
6. Click on “System properties”
7. Click on “Device Manager”
8. Under “Other devices” you will see T-Hub2 with an icon with a yellow exclamation mark.
9. Right-click the device and select "Update Driver"
10. Select "Browse my computer for driver software"
11. Select "Let me pick from a list of device drivers"
12. Click “Show All Devices”
13. Click “Have disk …”
14. Browse to where you put the extracted files
15. Select and open “Android_winusb.inf”
16. Select “Android Composite ADB Interface”
17. Click “Next” and then Click “Yes” (Ignore warning)
18. Wait until the software installs
19. You should now have Android Composite Interface” under the “Android Phone” listing
If you have problems, ensure Debugging is selected and try unplugging the THub and reconnecting it
ACCESSING ADB
1. Ensure that Debugging has been enabled – Settings Developer options USB debugging and make sure the box is checked
2. The following is for Windows 7, other versions will be similar, It also assumes that the file has been down loaded, unzipped and installed in a folder called THub on you C: drive
3. Connect the THub to your PC
4. Click in the “Start” icon, lower left icon on your PC Desktop
5. In the entry box type in “CMD” and push “Enter”
6. You will be at the “Command Prompt”
7. You need to navigate to the “THub” folder, the following are my entries, and yours should be similar.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Terry>cd .. and “Enter”
C:\Users>cd .. and “Enter”
C:\>
C:\>cd THub and “Enter”
C:\THub>
8. At the THub folder type in “ADB devices” and “Enter”
9. You should get an output similar to this:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
01545CAB0B015004 device
C:\THub>
10. You now have ADB access
11. Try “adb shell” and “Enter” to enter ADB and then “ls” and “Enter” to get the THub Root folder listing
What next, I don’t know but at least we have ADB access?
I have been trying to copy system files to my SD card to have a look at them but have no success.
Does anyone know how?
Here is the site I uploaded the files to:
"You can fill in the missing bits"
xxx.mediafire.com/download/voku3wnuff5s2ef/THub.zip
NOTE: There is also a file called “UniversalAdbDriverSetup6.msi”.
I don’t know what it is for, but I installed it anyway. It MAY be necessary for the above method.
Firstly, I understand this is an old thread but quite a lot of us Australians have this THub 2 now because Telstra seem to basically be handing them out like shots at a party.
As far as I know this thing still has no root access. You can get into ADB with it without too much trouble.
But what I really want to know is how I can get root access with SuperSU so I can install something like AdAway to remove the seemingly ridiculous amount of advertisements that apps and etc. come with.
In addition to that, after installing just TWO small apps. It seems the device's internal memory is already full and it cannot install any more apps.. I need root access in order to run Apps2SD so I can move some apps to the SD card that I have purchased for it.
Does anyone, and I mean anyone have any ideas about how to root this thing? There has to be some Australian who has a rooted version with SuperSU running.
I tried 'towelroot' but the device just rebooted (meaning it failed) and then when I ran the .apk again it said that the device was unsupported.
It's one thing to be able to get access to the root partition (which is possible over ADB) but it's another to be able to run apps with root privileges.
For any information.
The specs are:
Manufacturer - Technicolor
Operating System - Ice Cream Sandwich 4.0.4
Processor - 1 GHz dual core
Screen - 7″ (1024 x 600 pixels)
Camera - 1.9 MP rear camera, 1.2 MP HD front camera
RAM - 1GB
Storage - 2 GB Internal with an expandable Micro SD card slot (1GB internal usable)
Battery - 6000 mAh (non-removable)
I know it's nothing amazing, but if I could root the device and change the DPI, remove advertisements and install a few hacks. I'd get so much more out of the device.
I picked it up in almost perfect condition second-hand off eBay for only $15. They're worth $360 AU brand-new.
If anyone has any information at all, please do post something. My apologies again for bumping a super old thread but otherwise I was going to just start my own.
Possible to restore system partition
Hi Guys,
I done goofed.
I killed my T-Hub by flashing a corrupted system partition and now the device wont boot and only displays the Telstra logo at the boot loader. I do have a backup of my system partition however I cant work out how I would perform the restore. The boot loader will not allow an ADB connection so no luck there.
Im thinking JTAG may be my only option. I have experience with this on other devices but i cant find the JTAG terminals on this thing? I must have tapped about 60 different combinations of testpoints now and have only been able to get console out of the radio module which is obviously no good for talking to the kernel.
Any help would be greatly appreciated.
Cheers,
Swamp
SwampCrack1210 said:
Hi Guys,
I done goofed.
I killed my T-Hub by flashing a corrupted system partition and now the device wont boot and only displays the Telstra logo at the boot loader. I do have a backup of my system partition however I cant work out how I would perform the restore. The boot loader will not allow an ADB connection so no luck there.
Im thinking JTAG may be my only option. I have experience with this on other devices but i cant find the JTAG terminals on this thing? I must have tapped about 60 different combinations of testpoints now and have only been able to get console out of the radio module which is obviously no good for talking to the kernel.
Any help would be greatly appreciated.
Cheers,
Swamp
Click to expand...
Click to collapse
I'm completely new to this. What ROM would i look for to install on the THUB if any? And if i could install it?
clearburn said:
I'm completely new to this. What ROM would i look for to install on the THUB if any? And if i could install it?
Click to expand...
Click to collapse
sorry but no one has developed a ROM for this device, there is no demand
Madaz2 said:
sorry but no one has developed a ROM for this device, there is no demand
Click to expand...
Click to collapse
Thanks. I thought there might have been a rom from the basic device that didn't have all of the Telstra stuff on it.
It is currently a brick
if you can root it then you could install Titanium backup and uninstall the bloatware off of it
Some moderate success
I have had some moderate advancements of late.
I can get temporary ADB root using the directory traversal exploit
.
While the above method gets you a root terminal session, as it screws with some settings the device is nearly unusable due to screen flicker and general lag. I guess the exploit breaks some settings. Does anyone know how to leave the exploit in place and restore the settings file to eliminate the flickering and lag?
I have been able to export the system partition, edit it (add su.bin and SuperUser.apk) then swap the system mount so the device uses my edited system partition as described by malleus. When I try to flash my partition the device reboots and is in a semi brick state (reboot loop, stuck on boot loader Telstra logo).
I was able to obtain the OTA update files by getting an old 2.3.7 device, rooting it then grabbing the OTA files using ADB once it had downloaded them. These OTA's can be flashed from an SD card (ext4 format) in 3e recovery. This was a good bit of progress as it means I can restore from a bricked state. If anyone needs them, the files I have are:
Product_4.0.4_3.38-FOTA
Product_4.0.4_3.48-FOTA
This is all new territory for me but i think I am getting close to achieving full, persistent root in 4.0.4.
Any help would be appreciated.
I would be very interested in your progress as I have one of these but in default state it is only usable as a phone on the DECT base.....
Having some useful apps running off an SD card would help no end (like multimedia remote for my home theatre system)
Cheers,
Alex B
SwampCrack1210 said:
I have had some moderate advancements of late.
I can get temporary ADB root using the directory traversal exploit
.
While the above method gets you a root terminal session, as it screws with some settings the device is nearly unusable due to screen flicker and general lag. I guess the exploit breaks some settings. Does anyone know how to leave the exploit in place and restore the settings file to eliminate the flickering and lag?
I have been able to export the system partition, edit it (add su.bin and SuperUser.apk) then swap the system mount so the device uses my edited system partition as described by malleus. When I try to flash my partition the device reboots and is in a semi brick state (reboot loop, stuck on boot loader Telstra logo).
I was able to obtain the OTA update files by getting an old 2.3.7 device, rooting it then grabbing the OTA files using ADB once it had downloaded them. These OTA's can be flashed from an SD card (ext4 format) in 3e recovery. This was a good bit of progress as it means I can restore from a bricked state. If anyone needs them, the files I have are:
Product_4.0.4_3.38-FOTA
Product_4.0.4_3.48-FOTA
This is all new territory for me but i think I am getting close to achieving full, persistent root in 4.0.4.
Any help would be appreciated.
Click to expand...
Click to collapse
Has anyone made any progress on this?
I have two of these tablets that have sat unused since I got them from Telstra. I really just want to update it to at least 4.1, but there's no official release from Telstra for the T-Hub, and I don't think there will be. Are ports entirely unfeasible?
Do you think I could contact Technicolor? What should I say?
P.S. there is a recovery mode, because I've booted into it.
hxxp://imgur.com/O0uq4Uk
Hello,
In the process of rooting and trying to install CWM Recovery in preparation to flash Cyanogenmod, I seem to have denied myself access to the phone's internal storage. In the "File Manager" app, I get the following screen:
Local: /storage
No files
No search results
In addition, any app that requires access to internal memory will not work, instead showing messages such as "Try again after scanning media files" or "Not enough storage". If I plug in the USB cable and set it to "Media sync (MTP)" mode, Windows Explorer will show the device but list the internal storage as having "0 bytes" and no files.
I already tried the following:
- Factory reset
- Flashing the official ROM through the Windows Enabler / UpTestEX tools
In both tries the phone was "reset", as in it returned to the initial Android welcome screen where you set up your Google account, but in each case I still didn't have access to internal storage.
This is what I have in the "About phone -> Software information" option:
Android version: 4.1.2
Baseband version: APQ8064T/MDM9x15M
Kernel version: 3.4.0
Build number: JZO54K
Software version: E98810b
The phone does not have Wi-Fi access either, which is why I was tinkering around with custom ROMs in the first place, so I won't be able to download anything to it as part of the solution.
Is there anything else I can try?
I'm guessing you used FreeGee to install CWM? Perhaps try restoring?
If that didn't work... Id move the EFS backups to my computer. I'd make a NAND backup in CWM. Then I'd get CM and gapps on a micro SD. I'd do a format of system, data, and cache. Then I'd install CM and gapps. Then I'd cross my fingers.
Sent from my LG-E980 using Tapatalk
ackliph,
Since I didn't have Wi-Fi access on the phone, and at the time I didn't know how to reverse tether it to the computer, I was looking for a procedure to install CWM Recovery that didn't involve downloading files directly within the phone (only transfering via USB). Right now I can't find the exact instructions I used, but it was similar to what is described by hkfriends in this thread: http://forum.xda-developers.com/showthread.php?t=2361941, the only difference being that the image I downloaded was not that one.
I rooted the phone with Universal Root, then followed those instructions to install CWM Recovery. It seemed to have worked, but when I rebooted... nothing happened! The phone booted normally, and if I tried entering recovery mode all I got was the stock LG recovery.
I continued looking for another way to install a custom recovery, but instead came upon instructions to flash KDZ files with UpTestEx. Since the immediate problem I was trying to solve was the lack of Wi-Fi access (and not really the custom ROM), I thought it couldn't hurt to try updating the stock ROM. The procedure did update my ROM, but I ended up in my current predicament: no access to internal storage, and still no Wi-Fi access! It even managed to unroot the phone.
So your suggestion would be to try installing CM via a microSD card. OK, I can get a microSD and try that. However, I do believe I will need root access to do anything of the sort. I tried Universal Root again, and got the following messages:
Beginning Root Process
/system/bin/sh: can't create /sdcard/G_security: Permission denied
Now change from Charge Only to MTP
No need to disconnect USB
Press Enter after making the change.
adbd cannot run as root in production builds
error: device not found
If uid=0(root), gid=0(root) is displayed
Press Enter to Continue
1955 KB/s (1085140 bytes in 0.542s)
mount: permission denied (are you root?)
cp: can't create '/system/xbin/busybox': Read-only file system
failed to copy 'su' to '/system/xbin/su': Read-only file system
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file system
Unable to chown /system/xbin/su: No such file or directory
You are now properly Rooted.
Click to expand...
Click to collapse
Evidently, that didn't work.
I guess I will need some other method of rooting it.
Hello
I just upgraded my TabS 10.5 on Lollipop 5.0.2 and had problem to access SD card...
I performed a full clean & wipe then install stock 5.0.2 rom and setup the tab.
I installed TWRP then Cf-Auto-Root and used NextApp SD Fix to patch sd card access...
Most of things are ok but I have some strange issues:
QuickPick say: "unknown error (code 14) could not open database"
Dodonpachi say: "SD card is in use. Select "Turn off USB storage" to launch application."
And the Amazon App store say it can't download...
If I try to download F-droid from Chrome I get a "No SD card" error message...
I don't understand what's the problem so I need your help to find it out
You installed twrp THEN cf-autroot? So that was sorta pointless because you just wiped twrp off with flashing cf-autoroot.
Lollipop works different now for sd card access. Apps can be given write access to the sd card as long as the app requests it and the user agrees.
i messed up
root then twrp... so I'm rooted and have twrp ^^
I just need to wait for these app updates ?
kraoc said:
i messed up
root then twrp... so I'm rooted and have twrp ^^
I just need to wait for these app updates ?
Click to expand...
Click to collapse
I grab a logcat for QuickPic and I read this:
Code:
2015-04-21 08:22:59,ERROR,SQLiteDatabase,Failed to open database '/storage/emulated/0/Android/data/com.alensw.PicFolder/cache/thumb_96100.db'.
android.database.sqlite.SQLiteCantOpenDatabaseException: unknown error (code 14): Could not open database
at android.database.sqlite.SQLiteConnection.nativeOpen(Native Method)
at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:318)
at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:228)
at android.database.sqlite.SQLiteConnectionPool.openConnectionLocked(SQLiteConnectionPool.java:512)
at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:206)
at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:178)
at android.database.sqlite.SQLiteDatabase.openInner(SQLiteDatabase.java:894)
at android.database.sqlite.SQLiteDatabase.open(SQLiteDatabase.java:864)
at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:699)
at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:674)
at com.alensw.a.bb.a(Unknown Source)
at com.alensw.a.bb.a(Unknown Source)
at com.alensw.a.bb.a(Unknown Source)
at com.alensw.a.bf.run(Unknown Source)
and
Code:
2015-04-21 08:22:59,WARNING,System.err,remove failed: ENOENT (No such file or directory) : /storage/emulated/0/Android/data/com.alensw.PicFolder/cache/others_3
2015-04-21 08:22:59,WARNING,System.err,android.database.sqlite.SQLiteCantOpenDatabaseException: unknown error (code 14): Could not open database
2015-04-21 08:22:59,WARNING,System.err,android.database.sqlite.SQLiteCantOpenDatabaseException: unknown error (code 14): Could not open database
2015-04-21 08:22:59,ERROR,SQLiteLog,(28) failed to open "/storage/emulated/0/Android/data/com.alensw.PicFolder/cache/thumb_96100.db" with flag (131072) and mode_t (0) due to error (2)
2015-04-21 08:22:59,ERROR,SQLiteLog,(28) failed to open "/storage/emulated/0/Android/data/com.alensw.PicFolder/cache/thumb_96100.db" with flag (131072) and mode_t (0) due to error (2)
2015-04-21 08:22:59,WARNING,System.err,android.database.sqlite.SQLiteCantOpenDatabaseException: unknown error (code 14): Could not open database
I'm not sure about the problem but I'll check for path and permissions soon.
I think this is strange because I reinstalled my tablet from scratch and reinstalled the app too...
So everything should bo ok...
PS: I google a bit about permissions and found some links:
http://stackoverflow.com/questions/...storage-permission-with-getexternalcachedir-o
http://possiblemobile.com/2014/03/android-external-storage/