Hi
I've looked around the XDA Forums, and on various other forums. I have a Hipstreet Titan, I tried to root using the Tasselhof's Root package, and it went reasonably well until I selected the option (#3) to copy over the build.prop file. After that I get the Android logo every boot-up. Factory wipe I guess wiped - I don't really have any way to verify. I pushed a different build.prop on, but that didn't seem to take (or make any difference). For some reason my adb shell (whateverother parms) doesn't work. It returns "- exec '/system/bin/sh' failed: No such file or directory (2) -". So I figure the OS has been toasted. (I didn't have this much trouble rooting my LG Eclypse. )
Now, I just need to find an original ROM, or some other slightly modded (rooted would be nice) ROM to get on to my device before I find out how far out my back door I can throw this thing. As this Hipstreet tablet is an off brand (really far off, but hey, I got it free), I haven't been able to find a ROM posted anywhere. Likely I just haven't looked in the right spot yet. Yes, I know, I should have backed up first - but I didn't. As soon as I get an OS working on this, I'll back it up - promise.
I've also tried "adb sideload system.img" using a system image file that comes with the Android ADT kit and the factory recovery mode. That appears to upload the file, reboot the device then report (on the windows terminal) "* failed to write data 'protocol fault (no status)' *". The device reboots into the recovery system screen.
So, if someone would be so kind as to point me to a rom file that will work on this device, it would be most appreciated.
PS this is the Titan rev A, when I got the device (second hand) the Google Play store functioned just fine. The person I got it from is not a techy, so I doubt they applied any root or update to it, so I'm guessing it came already set up.
Ok, let me rephrase simply.
Can someone with a working Hipstreet Titan, rooted or not, please send me, or post a link to their ROM?
Click to expand...
Click to collapse
I know people have this device, and it's quite reasonable to assume that not all of them are bricked, therefore this request is technically feasible. Further, with a number of people posting about this device in technical forums, I know people with technical knowledge own this device.
I would really hate to throw out an otherwise perfectly good tablet.
Jarod997 said:
I would really hate to throw out an otherwise perfectly good tablet.
Click to expand...
Click to collapse
Hi - did you ever resolve this issue?
beach9000 said:
Hi - did you ever resolve this issue?
Click to expand...
Click to collapse
Not yet. I had given up for a while. Most of my internet searches kept coming back to the same few articles on this website.
I have a lead on someone who has another Titan, but they live seven hours away - it's been difficult coordinating a meeting.
Jarod997 said:
Hi
I've looked around the XDA Forums, and on various other forums. I have a Hipstreet Titan, I tried to root using the Tasselhof's Root package, and it went reasonably well until I selected the option (#3) to copy over the build.prop file. After that I get the Android logo every boot-up. Factory wipe I guess wiped - I don't really have any way to verify. I pushed a different build.prop on, but that didn't seem to take (or make any difference). For some reason my adb shell (whateverother parms) doesn't work. It returns "- exec '/system/bin/sh' failed: No such file or directory (2) -". So I figure the OS has been toasted. (I didn't have this much trouble rooting my LG Eclypse. )
Now, I just need to find an original ROM, or some other slightly modded (rooted would be nice) ROM to get on to my device before I find out how far out my back door I can throw this thing. As this Hipstreet tablet is an off brand (really far off, but hey, I got it free), I haven't been able to find a ROM posted anywhere. Likely I just haven't looked in the right spot yet. Yes, I know, I should have backed up first - but I didn't. As soon as I get an OS working on this, I'll back it up - promise.
I've also tried "adb sideload system.img" using a system image file that comes with the Android ADT kit and the factory recovery mode. That appears to upload the file, reboot the device then report (on the windows terminal) "* failed to write data 'protocol fault (no status)' *". The device reboots into the recovery system screen.
So, if someone would be so kind as to point me to a rom file that will work on this device, it would be most appreciated.
PS this is the Titan rev A, when I got the device (second hand) the Google Play store functioned just fine. The person I got it from is not a techy, so I doubt they applied any root or update to it, so I'm guessing it came already set up.
Click to expand...
Click to collapse
It looks like they made a few different versions of the tablet and it matters also about how much storage as to which firmware you should try. The person here: http://www.androidtablets.net/forum...eet-titan-a13-7-inch-tab-firmware-needed.html was able to load the firmware from another device that was similar. There were some major issues, but better to get it running first and sort that out later I guess. But his link has a bunch of other a13 tablet firmwares. If that is the same as yours, possibly one of them will be enough to boot up.
es0tericcha0s said:
It looks like they made a few different versions of the tablet and it matters also about how much storage as to which firmware you should try. The person here: (link manually removed) was able to load the firmware from another device that was similar. There were some major issues, but better to get it running first and sort that out later I guess. But his link has a bunch of other a13 tablet firmwares. If that is the same as yours, possibly one of them will be enough to boot up.
Click to expand...
Click to collapse
Thanks for the help! I'll have a look at some of those. I'd really like to have a tablet back that doesn't have a 3.5" screen.
So I managed to get LiveSuit 1.11 installed on Win 8-64, yes it IS doable. But, my problem is I can't get the tablet recognized. The Power+Vol boot takes it in to "recovery" mode, (so reports "adb devices") - does this keep it from being able to be used by LiveSuit?
"adb wait-for-device" hangs
In my Device Manager I have Android Device->Android ADB Interface, and Universal Serial Bus controllers->USB Device(VID_1f3a_PID_efe8) with a yellow exclamation.
I know I had "adb wait-for-device" passing fine at one point, but I don't remember what I had to do to get there. So much trouble for a free tablet.
I have a Titan that I unfortunately tried to root using what would only work on the ICS model and it's the JB model. It bootloops on the Android boot sequence. I can adb into the tablet and browse it, and I can see in the logcat where it gives up and restarts.
I saw the post on that other forum about using the Tragidy firmware but that file at Dorkfiles now appears to be paywalled. If anyone has that or another compatible firmware already downloaded and would be able to share, that would be wonderful.
At this point the Titan in front of me may as well be a mini cutting board or a large coaster. Not that it matters much, as some store gave it out to my parents for free and we all own better devices. It's just that they don't own any Androids and I thought I could configure this one as an easy remote for them to push content from their media server to their Smart TV instead of using the TV's complicated interface.
cmstlist said:
I have a Titan that I unfortunately tried to root using what would only work on the ICS model and it's the JB model. It bootloops on the Android boot sequence. I can adb into the tablet and browse it, and I can see in the logcat where it gives up and restarts.
I saw the post on that other forum about using the Tragidy firmware but that file at Dorkfiles now appears to be paywalled. If anyone has that or another compatible firmware already downloaded and would be able to share, that would be wonderful.
At this point the Titan in front of me may as well be a mini cutting board or a large coaster. Not that it matters much, as some store gave it out to my parents for free and we all own better devices. It's just that they don't own any Androids and I thought I could configure this one as an easy remote for them to push content from their media server to their Smart TV instead of using the TV's complicated interface.
Click to expand...
Click to collapse
So I managed to get a system backup off of my father-in-law's Titan - just have to figure out how to get it on my brick. I'm having great difficulty trying to do a restore while in recovery mode.
What means did you use to back it up?
Sent from my Nexus 5 using Tapatalk
cmstlist said:
What means did you use to back it up?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
adb backup
Jarod997 said:
adb backup
Click to expand...
Click to collapse
The adb backup command doesn't back up the system files. Unless there's some other way to use it that I'm not aware of?
Sent from my Nexus 7 using Tapatalk
cmstlist said:
The adb backup command doesn't back up the system files. Unless there's some other way to use it that I'm not aware of?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Aw crap, really? The cutting board a-la-iPad commercial is sounding like such a good idea at the moment.
On the good tablet I could get in the shell - "adb shell", and then "su", but then what? How do you copy all the files off the system through the USB onto the computer from the shell? For whatever reason (and I dislike ADB for this) I could not do "adb pull /* /destination-folder/*" - it kept saying that it was skipping a lot of files. Or otherwise if I was trying other variations on commands and parameters, adb would just spew its help page - never mind telling me what's wrong with the command I just entered.
Why, oh why, is it so hard to take a copy of a good working OS and put it on to another tablet?
But, make you a deal - help me get a good system image off this working tablet and I'll toss it to ya.
If you can find the right mount points on the partition table got may be able to make a system dump using dd. But restoring it I have no idea since there's no custom recovery available for this tablet.
Sent from my Nexus 7 using Tapatalk
Hi guys,
Wondering if anyone here has the know how to help.
Im fiddling with some new Kobo arcs, the 7HD and the 10HD and im having some bother with installing a custom recovery img.
For simplicity sake im going to refer to them as the same device as they are both behaving the same way
The device is rooted, and I am able to flash a custom recovery made by Jenkins builder but its not functional, when you boot to the recovery OS it just goes black and the back light flashes on an off (screen remains black it just lightens up)
At this point I can reboot as normal and adb to it and flash the original recovery img and all is well.
As far as I can tell its bootloader is unlocked but there might be a second bootloader im not able to interact with yet, possible called uboot?
From adb I am able to reboot the device in to bootloader and fastboot and both function as id expect, but the problem im having is booting directly to fastboot in case I bugger something up which would allow me to fix it.
I can boot the device in to a "mode" that tries to install an APX device, ive tried using various adb, fastboot, and composite drivers and nothing seems to work, ive downloaded some old NVidia APX tegra 2 drivers ive found but these fail to work with the NVFlash utility that comes with it, it says unknown device found, which would make sense given the utility is at least 3 years old
So firstly,
Does anyone know what might course the customer recovery rom to fail and yet flash like it is doing, if so any suggestions where to start to look for a solution?
Secondly,
Does anyone know much about this APX mode and how to actually put it to good use the driver appears to work and communicate but im needing something desktop wise to talk to it...?
hope you guys can help
edit
ive answered some of question 2 myself, it appears its a pain in the arse by all accounts and not as user friendly as I was hoping, I can send commands to it but it appears that commands may need to be "signed" of sorts as I don't get any response other than acknowledgment of the command sent, ill monitor the USB traffic and see if that sheds some light, it also appears that NVflash (not to be confused with its cousin in the GPU arena) is also hopelessly out of date and once again Linux is needed to get something more updated, if there is ANY help at all id appreciate some input
D
dazza9075 said:
Hi guys,
Wondering if anyone here has the know how to help.
Im fiddling with some new Kobo arcs, the 7HD and the 10HD and im having some bother with installing a custom recovery img.
For simplicity sake im going to refer to them as the same device as they are both behaving the same way
The device is rooted, and I am able to flash a custom recovery made by Jenkins builder but its not functional, when you boot to the recovery OS it just goes black and the back light flashes on an off (screen remains black it just lightens up)
At this point I can reboot as normal and adb to it and flash the original recovery img and all is well.
As far as I can tell its bootloader is unlocked but there might be a second bootloader im not able to interact with yet, possible called uboot?
From adb I am able to reboot the device in to bootloader and fastboot and both function as id expect, but the problem im having is booting directly to fastboot in case I bugger something up which would allow me to fix it.
I can boot the device in to a "mode" that tries to install an APX device, ive tried using various adb, fastboot, and composite drivers and nothing seems to work, ive downloaded some old NVidia APX tegra 2 drivers ive found but these fail to work with the NVFlash utility that comes with it, it says unknown device found, which would make sense given the utility is at least 3 years old
So firstly,
Does anyone know what might course the customer recovery rom to fail and yet flash like it is doing, if so any suggestions where to start to look for a solution?
Secondly,
Does anyone know much about this APX mode and how to actually put it to good use the driver appears to work and communicate but im needing something desktop wise to talk to it...?
hope you guys can help
edit
ive answered some of question 2 myself, it appears its a pain in the arse by all accounts and not as user friendly as I was hoping, I can send commands to it but it appears that commands may need to be "signed" of sorts as I don't get any response other than acknowledgment of the command sent, ill monitor the USB traffic and see if that sheds some light, it also appears that NVflash (not to be confused with its cousin in the GPU arena) is also hopelessly out of date and once again Linux is needed to get something more updated, if there is ANY help at all id appreciate some input
D
Click to expand...
Click to collapse
I know this is old, but how did you flash the original recovery? I think I need to do this so that I can install the update ZIP for the Kobo 10. CWM is failing to install the file.
Reposted from the bottom of another sad-hearted thread. BTW Screenshot is just some graphic relief from happier daze with a Kindle that would do its half of the work to make the relationship function without so much damn grief.
----
Although I had Safe Strap, SU and etc. installed on my rooted HDX 7", I panicked when my firewall failed to block the 13.3.2.1 update and cut the power off in mid update. Unfortunate reflex that led to a soft brick. Although I now can get into Fastboot no problem (I can't access the ADB commands though), I have tried to flash recoveries, boot images and so on. I can erase data (I'd call myself an expert at this part of the rooting process) and arrange file system layouts but then can't get past this error:
FAIL: flashing not allowed for locked hw.
Anyone know how to, maybe change permissions on the hardware or whatnot to get the device to let me write to the system partition? I'm flashing from a iMac btw.
I mean the Christmas colors of the text as far as what worked and what didn't are fun to look at, but the actual loading of the Kindle OS might provide more long term visual excitement. Thanks and love all y'all's insights into navigating the treacherous waters of root access and tweaking the twerkinator in these here twandroids.
----
EDIT: I can use the ./adb commands but I was having trouble before with the period-less version. Was still getting no device to show up when I query adb but got this through fastboot:
fastboot -i 0x1949 devices -l
(serial number) fast boot usb:FA130000
Redaction is mine ...
noobkidsontheblock said:
Reposted from the bottom of another sad-hearted thread. BTW Screenshot is just some graphic relief from happier daze with a Kindle that would do its half of the work to make the relationship function without so much damn grief.
----
Although I had Safe Strap, SU and etc. installed on my rooted HDX 7", I panicked when my firewall failed to block the 13.3.2.1 update and cut the power off in mid update. Unfortunate reflex that led to a soft brick. Although I now can get into Fastboot no problem (I can't access the ADB commands though), I have tried to flash recoveries, boot images and so on. I can erase data (I'd call myself an expert at this part of the rooting process) and arrange file system layouts but then can't get past this error:
FAIL: flashing not allowed for locked hw.
Anyone know how to, maybe change permissions on the hardware or whatnot to get the device to let me write to the system partition? I'm flashing from a iMac btw.
I mean the Christmas colors of the text as far as what worked and what didn't are fun to look at, but the actual loading of the Kindle OS might provide more long term visual excitement. Thanks and love all y'all's insights into navigating the treacherous waters of root access and tweaking the twerkinator in these here twandroids.
----
EDIT: I can use the ./adb commands but I was having trouble before with the period-less version. Was still getting no device to show up when I query adb but got this through fastboot:
fastboot -i 0x1949 devices -l
(serial number) fast boot usb:FA130000
Redaction is mine ...
Click to expand...
Click to collapse
can you get to safe strap at all???
Hello,
I was asked to forward my problem here so here it goes:
Not a long time ago I bought Asus ME302C FHD 10 and tried to root it. I followed a guide but I can't paste link just now.
Anyhow, the guide told me to flash rooted system image. I did every step correctly except that after i rebooted it, my device got stuck on logo screen, sometimes saying "no command".
I would like to undo that by getting unrooted system image for my device or rather get a working rooted system image. I am not sure about other possibilities as I am not experienced in android rooting or anything related. I do have fastboot up and working.
Thank you a lot in advance.
Edit: I figured out that Asus website has factory system images, however I don't really know which one to use because they all are for different countries and I am not sure what device is mine. Is there a way to check parameters of your device without booting it?
Edit2: I messed with the device more and found out that adb doesn't recognize device, as in, running 'adb devices' nothing gets listed. However, 'fastboot devices' does output my device, not sure where the problem is. Also, firmwares listed on asus website are zipped files and I don't know how to flash them. I tried 'fastboot flash system zippedfile.zip' but it would give me an error.
Solved
After few sleepless nights and loads of browser tabs opened I finally managed to fix my device.
All I needed was to use a different SKU firmware from Asus website. Now I can finally boot it thanks to XDA developers team and their useful information on the forums.
Hello guys, first i hope it's in the right place to post this and second sorry for my english.
And also thx for many tips i got from here on my road to get this working. But now i don't know what to do.
(Win 7 Starter 32bit, Android Debug Bridge version 1.0.31)
My situation: had a S3 (I9300) with Android 4.3 and a broken screen. Touch is still working. The broken screen wasn't a problem at first, because as it fell down, the screen was all right. After about 15 min it started to get black at the top. But most of the screen was ok. After the night everything was black.
So i read about droidatscreen and started to root and play with the device. First i put CF-Root-SGS3-v6.4 with Odin on the phone and then started to try to make adb work under Android.
I was in recovery and add this line to the build.prop "persist.service.adb.enable=1" .
I'm not sure, but i think after a reboot of the phone i had adb running under Android. At this time adb said not authorized and the window with the confirmation for usb debugging wasn't popping out (because i tried and tried to touch at the place where it shold be).
Than i read about "persist.service.adb.enable=1 persist.service.debuggable=1 persist.sys.usb.config=mtp,adb" adding to default and build.prop , also didn't work.
Than i added "ro.adb.secure=0" and changed "ro.adb.qemud=1" to 0 in both files, and after rebooting the phone i hit the place on the screen and adb devices went from unauthorized to device. I finally made it and could use droidatscreen. (i don't think that ro.adb.secure=0 deactivated the rsa fingerprint, but i think it got it to pop up the confirmation window).
Now i was able to see the menue, i changed some things in options, like touch sound and screen unlock sound to be able to hear the things i couldn't see, i also changed the setting for showing touches in the dev menue.
And now the bad thing happened, i touched the option usb debugging (not on the check, but on the word itself (i could see it because of the latency of droidatscreen and the phone rebooted and wasn't able to connect to adb).
Now i only get the mtp device and adb devices shows nothing but a blank line.
I'm still able to change build.prop and other data in recovery but even load the original files to the phone and going step by step further didn't bring me the unauthorized message in adb devices.
I hope someone could help me. Maybe someone knows the files which are changed during changing the options in Android menue.
Btw. i already wiped cache, but do not want to do more than this (i mean wiping ).
Thx
Edit:
Solved the problem.
Found out about the getprop and setprop commands and used getprop in adb shell. Didn't found anything like "persist.service.adb.enable" ... , only something like
[service.adb.root]: [1] [ro.adb.qemud]: [1] and [persist.sys.usb.config]: [mtp] .
Searched in /data/property for adb things, and saw "persist.service.adb.enable" "persist.sys.usb.config" .
"getprop persist.service.adb.enable" showed a blank line, so i "setprop persist.service.adb.enable 1",
now "getprop persist.service.adb.enable" showed a 1 and after rebooting phone, i was able to get a unauthorized message from adb devices, and reconneting the usb let the confirmation popup.
Thx anyways.