Related
We now know that the new vibrant phones have the hardware key disabled to enter recovery mode. But these phones are not defective. The hardware key has been purposefully disabled as part of a misplaced strategy to secure a phone that has basically no security built into it.
Therefore it is really easy to gain root access to these phones. However the process requires the use of the adb program that is part of the google android sdk. This program likes to run on a 32-bit linux distribution. Since it will not run on a 64 bit system, here is how I managed to gain root access to my phone:
1. Download the sdk from google.
2. Boot into linux on a 32 bit machine. (I used ubuntu live cd on an old Toshiba laptop with an available linux partition to mount on the hd. Your mileage may vary.)
3. If you are not using ubuntu make sure that your c library is compatible.
4. Install the google android sdk on the hd linux partition, e.g. /home/android.
5. Plug your Samsung vibrant into the usb port on the linux machine.
The following steps are specific to ubuntu. The important thing to remember is that the adb program must run its server as root to gain the access we desire.
6. Start the terminal app: Applications > Accessories > Terminal
7. Mount the partition and change to the sdk directory:
sudo mount /dev/sda2 /media
cd /media/*/home/android/tools
7. Start the adb server:
sudo ./adb start-server
8. Make sure your device is recognized:
./adb devices
If you do not see your device connected you have some troubleshooting to do.
9. Reboot your phone into recovery mode:
./adb reboot recovery
Congratulations! You just gained root access to your hardware locked vibrant.
This message has been posted by my old g4 laptop while tethered through t-mobile 3g using wireless tether on my brand new Samsung vibrant.
M_T_M said:
Hmmmm..good enough to stick!
Click to expand...
Click to collapse
Yeah it's good, but you should move this thread to Samsung Vibrant forum.
This works on any android phone.
Although the method was inspired by the desire to use my vibrant as a g3 modem, the adb program is a general android maintenance tool that runs on linux. So it really doesn't matter what kind of phone you have. Once you have started the adb-server as root the reboot command will boot any android phone plugged into the linux box.
r2d4 said:
Although the method was inspired by the desire to use my vibrant as a g3 modem, the adb program is a general android maintenance tool that runs on linux. So it really doesn't matter what kind of phone you have. Once you have started the adb-server as root the reboot command will boot any android phone plugged into the linux box.
Click to expand...
Click to collapse
Would this also work for the new T-mobile G2 4G ?
I'm sure we will be seeing more locked phones besides the vibrant and g2. This fix should work for them all. The adb-server gives you root access to your phone provided that you have root access to the machine upon which it runs.
r2d4 said:
I'm sure we will be seeing more locked phones besides the vibrant and g2. This fix should work for them all. The adb-server gives you root access to your phone provided that you have root access to the machine upon which it runs.
Click to expand...
Click to collapse
Keep in mind that no matter what you do on the G2, it'll be wiped on reboot. You can gain root temporarily, but when you reboot, it's gone
Installing the root update
tjhart85 said:
Keep in mind that no matter what you do on the G2, it'll be wiped on reboot. You can gain root temporarily, but when you reboot, it's gone
Click to expand...
Click to collapse
If you want to keep root after your next reboot, you need to update your filesystem. The first step is to install the programs busybox and su.
Before you boot into recovery mode, make sure you have the update.zip file downloaded onto your phone's internal memory card. Whatever is on this card will be left alone even upon a factory reset. But the phone's internal memory will be wiped. The update.zip file merely installs those two programs to the internal memory and doesn't wipe anything.
1. Download the root update for your phone. Rename the file update.zip and place it on the root directory of your device's internal flash memory.
2. Once you are in recovery mode, use the volume keys to scroll and the power key to select "reinstall packages". (This works on the vibrant. The g2 may be slightly different.)
3. Your phone will reboot and you will find the Superuser app has been installed. This app lets you grant root access to applications that need it.
Now you can download powerful apps from the market to gain even more control over your phone.
I hope this helps.
Does boot with a live CD of 32 bit ubuntu on my AMD64 work?? or do i need to boot on a computer with a 32bit processor as well?
Running the 32 bit distribution cd on your 64 bit system should be fine.
Need help
Hello I need help to unlock my samsung vibrant
can someone tell me where i can fin the link
thank you
r2d4 said:
If you want to keep root after your next reboot, you need to update your filesystem. The first step is to install the programs busybox and su.
Before you boot into recovery mode, make sure you have the update.zip file downloaded onto your phone's internal memory card. Whatever is on this card will be left alone even upon a factory reset. But the phone's internal memory will be wiped. The update.zip file merely installs those two programs to the internal memory and doesn't wipe anything.
1. Download the root update for your phone. Rename the file update.zip and place it on the root directory of your device's internal flash memory.
2. Once you are in recovery mode, use the volume keys to scroll and the power key to select "reinstall packages". (This works on the vibrant. The g2 may be slightly different.)
3. Your phone will reboot and you will find the Superuser app has been installed. This app lets you grant root access to applications that need it.
Now you can download powerful apps from the market to gain even more control over your phone.
I hope this helps.
Click to expand...
Click to collapse
Does boot with a live CD of 32 bit ubuntu on my AMD64 work?? or do i need to boot on a computer with a 32bit processor as well?
unlocking on root system
I was wondering if it was okay to unlock a Samsung Vibrant when it is already rooted?
the JI6 OTA update fixed this issue.
If you upgraded using Kies or ODIN, you may still be HWL, BUT, there is a fix:
If you can not get into download mode, please try this:
** Please note this is for JI6, if you are running froyo do not do this **
untermensch has a fix for those who are HWL'd that seems VERY effective. I always heard some who updated from JFD to JI6 had the HWL fixed automatically, but that was not the case for everyone. It appears those who updated OTA got the fix, but most who did ODIN or Kies did NOT get the HWL issue fixed.
Please see his excellent thread by clicking here. Hope this helps.
If you are using froyo, I imagine you could revert back to JI6 and flash this to fix the HWL.
HWL but scared to update.zip
Hi all. I am running Ji6 and i am still hardware locked. I just want to root my phone so i can delete some stock bloatware.
Can root my phone without having to "fix" HWL. I am wondering, how Kies successfully upgraded my phone to JI6 with HWL? If I upgrade to froyo (once available) will the upgrade access recovery? WIil the upgrade brick my phone?
I know for Froyo there is z4root which seems to be an easy, safe way to root..
So should i plan on waiting for Froyo??
Just fyi... I just had my vibrant warranty replaced through tmobile, when I registered it with samsung the manufacture date showed november. I had no issues getting to recovery using the keypresses.
The whole warranty swap went alot better than I was expecting, phone looks new not refurbed, it came in like 1 or 2 days from when I called, AND they unlocked it for me even though I was at my unlock limit since it was a warranty replacement, just make sure they specify that in the request.
Sent from my Samsung Galaxy S - powered by Team Whiskey™
Thanks for help, T-mobile's Vibrant is hardware locked.
Of course, you don't need either Linux or 32-bit, it worked just fine from a Windows 64-bit machine (and will from any that has a version of ADK for it). Just Shift+right-click in "android-sdk-windows\platform-tools" and select "Open command window here", enter "adb devices" to launch the daemon and make sure your device is connected properly (it needs to be in "USB debugging mode", which you can select in settings), and then enter "adb reboot recovery". Phone should restart, select "Reinstall Packages" using volume keys and power key to enter.
Bought Samsung Vibrant - SGH T959 - Have questions...
Hi all,
I joined the forums recently to learn about rooting my EVO. With the help of a number of people on the forums I was able to easily root my EVO and install a custom ROM. Still haven't flashed any new Kernels yet but I may do that soon.
Anyway, I bought a Samsung Galaxy S (Vibrant) which of course is T-Mobile phone. I got it from my friend for $50 because I know they sell on eBay for anywhere from $250-$350.
However, I recently upgraded the phone for him before I bought it to 2.2 (Froyo). This seems to be bad for me because now I want to Unlock the phone so that it can be used with any carrier, or a carrier aside from T-Mobile but I've read in the forums here that it's hard to Unlock the device if you've upgraded to Froyo via Kies.
Can anyone help me with Unlocking my device and could someone give me a quick rundown of what the key commands are for this phone too? Such as how to access recovery to flash a ROM. Although I am not going to ROOT this device unless it is required in order to unlock the phone.
Thanks in advance for any help!!!
Oh, and I won't get mad if my post needs to be moved to another thread either so please move it to the right place if it needs to be.
Thanks!
PAinguINx said:
Hi all,
I joined the forums recently to learn about rooting my EVO. With the help of a number of people on the forums I was able to easily root my EVO and install a custom ROM. Still haven't flashed any new Kernels yet but I may do that soon.
Anyway, I bought a Samsung Galaxy S (Vibrant) which of course is T-Mobile phone. I got it from my friend for $50 because I know they sell on eBay for anywhere from $250-$350.
However, I recently upgraded the phone for him before I bought it to 2.2 (Froyo). This seems to be bad for me because now I want to Unlock the phone so that it can be used with any carrier, or a carrier aside from T-Mobile but I've read in the forums here that it's hard to Unlock the device if you've upgraded to Froyo via Kies.
Can anyone help me with Unlocking my device and could someone give me a quick rundown of what the key commands are for this phone too? Such as how to access recovery to flash a ROM. Although I am not going to ROOT this device unless it is required in order to unlock the phone.
Thanks in advance for any help!!!
Oh, and I won't get mad if my post needs to be moved to another thread either so please move it to the right place if it needs to be.
Thanks!
Click to expand...
Click to collapse
Well now, I found this http://forum.xda-developers.com/showthread.php?t=761045 but is it cool to do this while running Froyo? And another question, since I bought this phone from a friend can I still have it replaced/fixed (if needed) if the warranty is still active on it?
Thanks!
Back to original ROM by Odin, T959UVJFD.tar and s1_odin_20100512.pit
in dounload mode (down + power)
I have an LG Enlighten (Verizon Wireless), not an LG Optimus Slider (Virgin Mobile), running Android 2.3.4 (Gingerbread). I am in desperate need of a root solution. I have searched the online forums to no avail. I have put the phone up for sale for fear that this device may never be rooted. I am calling on XDA Developers to produce a working root before I ultimately rid myself of this thing. To add, I tried running Android SDK (adb). No go. The instructions threw me even after trying them repeatedly on several different occasions. It could be that my laptop
has no internet access, but I'm not entirely sure.
I really enjoy this phone and have customized it to the point of
exhaustion. All I'm waiting for now is ROOT! Please help ASAP...
Have you attempted to root it? Have you tried Superoneclick, z4root, and/or Gingerbreak?
Re: Have you tried to root it?
Yes, I have. Unfortunately, with no success. Results are as follows:
Z4Root - The end result is my phone takes me back to the previous screen (internet, home, games, music, etc.). It begins the rooting process... acquiring shell root. Then it just sticks for approximately 30 seconds and then closes. I have repeated the process on several occasions in the event that something unusual happened the first time around. But the result is always the same.
Gingerbreak - This app just ultimately hangs, endlessly. Approximately two hours worth before I just quit in frustration. But all online forums claim it should take no more than 15 minutes tops. I should also note that I read Z4Root and Gingerbreak will not work on rooting Android 2.3.4 due to the patching of an exploit. However, I did not update my phone to this firmware. It came preinstalled. And I have not found a procedure for downgrading (sbf'ing) an LG Enlighten.
SuperOneClick - This is the one I'm currently trying still. I can't recall the website, but in addition to SOC, it also requires the use of adb from Android SDK. The problem I'm coming across is the laptop I'm using to perform this action is without internet access (which I've tried feverishly to restore to no avail). And I'm thinking this is what the issue may be, but I'm not entirely sure. The only access I have to the internet currently is on my phone. However, I make a weekly trip to the college library (no restrictions on installing, downloading, etc.). So maybe I can try something there.
For the past month, I've been doing extensive research online trying to find any and all information in regards to resolving this matter. A few sites have blamed Verizon for crippling their Android devices from performing certain functions. For instance, this particular device has no "boot into recovery mode" (which I confirmed with a Verizon tech support person). Had it, I easily could've updated with the .zip file from my SD card (which I've now deleted since it's rendered useless).
I did read today that the next version of SuperOneClick v2.3 (to come out at a later date) will include the option for the forced inclusion of adb debugging/android files which could be the solution to my problems. Possibly.
I apologize if this reply post seems a little long-winded. But I wanted to provide you with all the information I have available in order to better recieve instruction as how to proceed forward. I will continue to try the SuperOneClick in hopes that I will acquire root. But if not, I will rely on the expertise of those in the XDA community.
Thanks,
Centim6
Rooting LG Enlighten
Ok. I found the solution. There is a video on youtube which shows you how to do it. And it works. I now have a rooted device! Finally. Thank you for your assistance.
centim said:
Ok. I found the solution. There is a video on youtube which shows you how to do it. And it works. I now have a rooted device! Finally. Thank you for your assistance.
Click to expand...
Click to collapse
Hi, I too have an LG Enlighten from Verizon wireless. I was just wondering how your root process went? Did the phone work well afterwards? Also do you by any chance have a link to or at least remember the name of the video you watched which helped you to get your phone rooted.
thanks in advance, Angel
centim said:
Ok. I found the solution. There is a video on youtube which shows you how to do it. And it works. I now have a rooted device! Finally. Thank you for your assistance.
Click to expand...
Click to collapse
Can you link to the video?
Sparky42 said:
Can you link to the video?
Click to expand...
Click to collapse
seeing as there is no link, I would say no.
secondly, the video posted and my own research indicates that root was possible only if it was v. 2.3.3. There isn't anything available for 2.3.4.
I have rooted my LG Enlighten which was on Gingerbread 2.3.4. I made a tutorial over at phandroids forums since xda does not let me post links to outside sources. Just google Lg Enlighten root and you will find it in the first or second link. Enjoy.
PS: If you do not believe me I made a video of my phone rooted on youtube. My user name there is the same as xda and I posted pictures at the end of my tutorial. Gingerbread 2.3.4 is fully exploitable on the LG Enlighten.
fsdfgasgfisd said:
I have rooted my LG Enlighten which was on Gingerbread 2.3.4. I made a tutorial over at phandroids forums since xda does not let me post links to outside sources. Just google Lg Enlighten root and you will find it in the first or second link. Enjoy.
PS: If you do not believe me I made a video of my phone rooted on youtube. My user name there is the same as xda and I posted pictures at the end of my tutorial. Gingerbread 2.3.4 is fully exploitable on the LG Enlighten.
Click to expand...
Click to collapse
I think it would a great idea to include which firmware you used this on. I kbow for a fact that it fails on v4 and v5.
And its not that I don't believe you (I do btw) its just the lack of specifics are going to excite someone and they'll leave you a nasty message cause they thought it would work. So, just a heads up:
Android version:
Firmware version:
Sent from my LG-VS700 using xda premium
I can confirm that the new VS700ZV5 update crippled the ability of this phone to root. I just tried the gingebreak and it didnt work. Any way around this?
Same here, android 2.3.4; firmware VS700ZV5.
I haven't been able to get root to work with SoC....
Any chance someone will figure a way around this update?
please reply to root on you tube PLEASE!
centim said:
Ok. I found the solution. There is a video on youtube which shows you how to do it. And it works. I now have a rooted device! Finally. Thank you for your assistance.
Click to expand...
Click to collapse
Extremely frustrated and hoping you will share this link. I to have tried everything to root my Enlighten to no avail and would appreciate your help more than I can explain! Please! Thank you and congats!
I had my phone rooted, then verizon put out an update, and now I can't root it. I think we're screwed until sombody figures out a new method.
Model: LGVS700
Firmware: VS700ZV5
im not sure if this will help but here, i found this claiming to be able to root the phone.
First, you need the file hboot_2.xx_soff-V8.9.zip, download it.
Unzip it into c:evoroot on your pc.
Second, put your LG Enlighten into development mode by
going to Settings->Applications->Development and turn USB
debugging on.
Third, connect your LG Enlighten to your computer and set
your USB to Just charge.
Fourth, if you get errors with drivers, install their HTC drivers.
(You can also install HTC Sync, but it is bulky!)
Fifth, open up a command prompt by typing cmd.
Sixth, type the following commands: (Or copy and paste,
easier!)
Code:
cd evoroot
adb push root/unrevoked-forever.zip /sdcard/
adb push root/mtd-eng.img /sdcard/
adb push pc36img/PC36IMG-ENG.zip /sdcard/PC36IMG.zip
adb push pc36img/PC36IMG-MR.zip /sdcard/PC36IMG-MR.zip
adb push root/flash_image /data/local/
adb -d install -r root/z4root.apk
Seventh, go to your phone and launch Z4Root app. Then select
temp root and wait until its done.
Eighth,go back to command prompt and type:
Code:
adb shell
su
If you get a pound(#) sign, that means you have temp root,
which just gives you temporary root so we can now install
permanent root.
ninth, go back to command prompt and type the following:
Code:
chmod 0755 /data/local/flash_image
./data/local/flash_image misc /sdcard/mtd-eng.img
sync
And reboot to bootloader mode by typing:
Code:
reboot bootloader
When bootloader mode starts up, it will look for PC36IMG.zip
and after about 3 minutes ask you if you want to install
PC36IMG.zip.
Say Yes by hitting the volume up button, it should now install
the new zip file, should take about 10 minutes. Go grabs some
coffee and come back.
Eleventh, reboot when its done by hitting the volume up
button.
It will reboot into the OS and we dont want that so takes the
battery out and puts it back in it. Then go back to the
bootloader by hitting the power button while holding down
the volume down button.
Choose Bootloader and wait until you get the triangle sign and
type:
Code:
adb push recovery /
adb shell busybox Cinstall /sbin
adb shell nohup /sbin/recovery
&
Go back to your LG Enlighten and you should see green
menus.
Choose install zip from sd card and choose unrevoked-
forever.zip
After that installs, Choose MS-USB
Go to your computer and delete PC36IMG.zip, then rename
PC36IMG-MR.zip to PC36IMG.zip.
Then power off your LG Enlighten, power back on by pressing
Power Button while holding down the Volume Down button,
this should get you back into bootloader mode.
Simply wait and when it asks to install the update, hit the
Volume Up button.
then reboot your LG Enlighten, your device should now be
rooted with Recovery menu then you can flash new ROMs for
LG Enlighten.
LG Enlighten root
I have lg enlighten running 2.3.4 and it is rooted with super user and rom toolbox working. I used POOT.APK which can be found on google. It worked well and everything went smooth. It is a simple and easy to use application. (You can use either SU or SSU)
any way to update it to ics? i have one
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
Hello XDA community, this is my first thread, i had never needed to post anything cause i always find everything im searching for in this awesome community... until now :crying:
Last week I got a new android device which is made by Polaroid, model: PSPR355, its a pretty low class device but I thought it would be enough for me.... then i realize I needed root permissions, for obvious reasons... easy I thought... i had rooted many devices...how hard can it be...right?... WRONG! :crying: . The first problem I encountered were the drivers..couldnt find em anywhere... fortunatelly i found a tutorial were i could install the drivers in a different way...although I took 2 days to do this...Ive been about 5 days trying to root my phone.... Ive tryied about 10 different programs with their different versions... and any of those rooted my phone, nor Oneclikroot, nor Unlockroot, etc, etc..... I really gave up trying to find something on the web cause i didnt even find the phone on its official site, so I came her defeated asking for any solution, idea, or if you want to help me with commands, a programm or anything else to root my phone, Im not even afraid of trying programming (Im trying to learn how to make roms, kernels, etc for this phone cause theres nothing on the web abou it but this is a theme for another time) if you wanted to help me i would really appreciate it, im a little desperate so anything would come useful thanks everyone and I hoppe you can help me!!! :fingers-crossed:
MecaMarck said:
If you wanted to help me i would really appreciate it, im a little desperate so anything would come useful thanks everyone and I hoppe you can help me!!! :fingers-crossed:
Click to expand...
Click to collapse
I would recommend trying the towelroot application. It can be downloaded from here, just click on the orange lambda to download the tr.apk file. Then open towelroot follow the instructions in the application. After the device reboots I would recommend downloading, Root Checker Basic form the Play Store and running that to make sure your device is rooted. Finally install SuperSU, and you should be good to go.
First thanks for answering so fast shimp208! And I guess I forgot to tell that I was in Mexico and Im using Telcel's network, I downloaded and installed the apk file but it doesnt starts I click the button pops up a black screen and then closes to the last app I used...any idea about this error...or if its beacuse of the carrier, by the way the device has Android 2.3.7 I dont know if it has something to do with this error
MecaMarck said:
First thanks for answering so fast shimp208! And I guess I forgot to tell that I was in Mexico and Im using Telcel's network, I downloaded and installed the apk file but it doesnt starts I click the button pops up a black screen and then closes to the last app I used...any idea about this error...or if its beacuse of the carrier, by the way the device has Android 2.3.7 I dont know if it has something to do with this error
Click to expand...
Click to collapse
Does it present an error message of any kind before it force closes? Try uninstalling and then re-installing the application, and if that doesn't work go to application manger under settings, find the towelroot application and select the options to clear it's cache and data. The carrier won't have any effect in this case, and with it being Android 2.3.7 your device most definitely has a kernel build date before June 3rd, 2014.
shimp208 said:
Does it present an error message of any kind before it force closes? Try uninstalling and then re-installing the application, and if that doesn't work go to application manger under settings, find the towelroot application and select the options to clear it's cache and data. The carrier won't have any effect in this case, and with it being Android 2.3.7 your device most definitely has a kernel build date before June 3rd, 2014.
Click to expand...
Click to collapse
No it simply closes without showing anything, and without even giving the "Force Close" message, i thought it was because i first installed it on the sd card, or because of not enough space but no, I moved it to the phone and uninstalled some apps I had, I uninstalled and installed towelroot twice and it didnt work, I installed the v1 of it and i got to the [make it ra1n] screen but when I click the button it closes immediately again without any error message
MecaMarck said:
No it simply closes without showing anything, and without even giving the "Force Close" message, i thought it was because i first installed it on the sd card, or because of not enough space but no, I moved it to the phone and uninstalled some apps I had, I uninstalled and installed towelroot twice and it didnt work, I installed the v1 of it and i got to the [make it ra1n] screen but when I click the button it closes immediately again without any error message
Click to expand...
Click to collapse
Very interesting, while in theory the app should work for any kernel build date earlier then June 3rd, 2014 the app many not be compatible with devices running an Android version less then 4.x.
shimp208 said:
Very interesting, while in theory the app should work for any kernel build date earlier then June 3rd, 2014 the app many not be compatible with devices running an Android version less then 4.x.
Click to expand...
Click to collapse
Yes that´s what i thought, do you think that theres no rooting method for this phone? if so, do yo think there´s a way of doing one?
MecaMarck said:
Yes that´s what i thought, do you think that theres no rooting method for this phone? if so, do yo think there´s a way of doing one?
Click to expand...
Click to collapse
Since you have the usb drivers working on your computer, try booting into the bootloader and using fastboot to see if the command fastboot devices returns anything. If the computer see's the device in fastboot that's a good sign. If your device doesn't have a locked bootloader which it likely doesn't, then I can try and create a rooted system image for you to flash in fastboot. Provided fastboot see's your device if it does, if you can provide me an adb dump of your /system folder then I will see what can be done.
Interesting for me.,.
Sent from my LT26w using xda premium
Same Boat
shimp208 said:
Since you have the usb drivers working on your computer, try booting into the bootloader and using fastboot to see if the command fastboot devices returns anything. If the computer see's the device in fastboot that's a good sign. If your device doesn't have a locked bootloader which it likely doesn't, then I can try and create a rooted system image for you to flash in fastboot. Provided fastboot see's your device if it does, if you can provide me an adb dump of your /system folder then I will see what can be done.
Click to expand...
Click to collapse
I'm in the same boat
I use moto-fastboot (any way it's fastboot)
#:\moto-fastboot devices
? fastboot
don't show any info...
I do a system dump in this way
#:\adb pull / c:\PSPR355
mega,co,nz/#!ThIUQYiS!LLbJ9e1-yVJI4juNlWQuPfa9GFH6HP9lr4X8Gwu1MBY
Change "," please, sorry mod if you want i can delete it! =$
klonic0 said:
I'm in the same boat
I use moto-fastboot (any way it's fastboot)
#:\moto-fastboot devices
? fastboot
don't show any info...
I do a system dump in this way
#:\adb pull / c:\PSPR355
mega,co,nz/#!ThIUQYiS!LLbJ9e1-yVJI4juNlWQuPfa9GFH6HP9lr4X8Gwu1MBY
Change "," please, sorry mod if you want i can delete it! =$
Click to expand...
Click to collapse
Unfortunately if fastboot doesn't show your device without any other flashing utility, even with the system dump there is no way to flash a rooted system image if it was created.
Got to see if this guys do the trick!
http://forum.xda-developers.com/showthread.php?t=2066041
shimp208 said:
Since you have the usb drivers working on your computer, try booting into the bootloader and using fastboot to see if the command fastboot devices returns anything. If the computer see's the device in fastboot that's a good sign. If your device doesn't have a locked bootloader which it likely doesn't, then I can try and create a rooted system image for you to flash in fastboot. Provided fastboot see's your device if it does, if you can provide me an adb dump of your /system folder then I will see what can be done.
Click to expand...
Click to collapse
Hello shimp well I connected my device on FastBoot Mode and my computer recognized it and it installed a driver named: ADB Testing Interface I dont know if thats a good sign or what should I do, I tried entering into recovery mode but it shows only an android little guy and exclamation quote... so I think it doesnt have a recovery boot I dont know if thats relevant, Could you help with the adb dump i dont know how to get it. And.... I dont know if besides you help me with the rooted system image you could teach me how I do this.... anyways thanks a lot for helping me! I'll keep doing everything you need so we can root this device!
MecaMarck said:
Hello shimp well I connected my device on FastBoot Mode and my computer recognized it and it installed a driver named: ADB Testing Interface I dont know if thats a good sign or what should I do, I tried entering into recovery mode but it shows only an android little guy and exclamation quote... so I think it doesnt have a recovery boot I dont know if thats relevant, Could you help with the adb dump i dont know how to get it. And.... I dont know if besides you help me with the rooted system image you could teach me how I do this.... anyways thanks a lot for helping me! I'll keep doing everything you need so we can root this device!
Click to expand...
Click to collapse
Since your computer recognizes the device and installed the driver and shows the device when in fastboot mode that's a good sign. The Android with the exclamation point is part of normal stock Android system recovery, it just means that the recovery menu has been hidden (You should be able to get the menu to appear by pressing the power and both the volume buttons in recovery mode). To dump /system run the following command:
Code:
adb pull /system
Then please send me a link to the /system dump, from there I will make a rooted system image.
Factory Rooted??
Hey guys I'm new to this so I may be wrong but has anybody thought to check if the Polaroid PSPR355 comes Factory Rooted??? I had a Polaroid Tablet, PID something(I forget the name), which I tried for hours to root resulting in: bootloop, hard reset, root, bootloop, hard reset, root, bootloop, hard reset, about to give up. So I Googled how to root Polaroid PID something (again, I forget the name), and I come to a post somewhere(forgot that too) that tells me my Tablet and similar Polaroid electronic devices(as well as most electronic devices coming from China) are factory rooted due to some Chinese law. So after the last hard reset, I downloaded HowToRoot App to check if my Polaroid Tablet is, in fact, rooted. I press the little lock button(root checker) and I find that, to my surprise, my Polaroid Table is in fact rooted. So all I had to do was download SuperSU from Google Play Store and Update Binary when prompted and I was Super User. Don't know if this helps but it worked for me.
Dont use this method ive heard bad experiences
Want Root but Don't want to Ruin my phone
HERPDERP202 said:
Method 1
Install Kingo Root On Your Pc Then Install It, After That Install Terminal Emulator From The Play Store
Then Type adb reboot disemmcwp (This disables write protection or else if you reboot your phone you
wont have a root) Next If That doesnt work type su 1st and if it asks for root say yes
Method 2
Download ADB tools and driver
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Open cmd and go to c:\adb\ then type adb reboot disemmcwp
After That install kingoroot from your pc then your finished
Tell me if this is not explained correctly
Click to expand...
Click to collapse
Hi I am wondering if there is any downside to either of these 2 Methods ? I have this Phone I am pretty familiar with Rooting as I have Rooted many Devices Tablets/Phones Some successful others Semi So my concern is this is my only decent Phone I dont want to Lose any Hardware functions Nor make the phone Slower Simply want to Remove some Apps I don't use That take up the majority of the 8gb of Space Note I have 32gb Sd Installed
I'm getting ready to try this soon. Do you know if root can be removed after it is applied permanently? I'll be giving my kids these phones but need to get past the issue of writing to the SD card as they have already used up all the internal memory, and Googles great idea of preventing write to the SD for apps in 5.x is really a buzz kill so far for them.
Thanks,
Mike
I Need Rom, Try root and bricked. Help Me Please. :crying::crying:
o.angeles said:
I Need Rom, Try root and bricked. Help Me Please. :crying::crying:
Click to expand...
Click to collapse
I just bricked mine to. Remember I told to factory reset it. You said it made it worst.
When I bricked mine I did what I told you them reset the cache and rebooted into bootloader and it fixed mine with no problem
Dark Elf God said:
I just bricked mine to. Remember I told to factory reset it. You said it made it worst.
When I bricked mine I did what I told you them reset the cache and rebooted into bootloader and it fixed mine with no problem
Click to expand...
Click to collapse
Thanks for comment but that did not work
HERPDERP202 said:
Method 1
Install Kingo Root On Your Pc Then Install It, After That Install Terminal Emulator From The Play Store
Then Type adb reboot disemmcwp (This disables write protection or else if you reboot your phone you
wont have a root) Next If That doesnt work type su 1st and if it asks for root say yes
Method 2
Download ADB tools and driver
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Open cmd and go to c:\adb\ then type adb reboot disemmcwp
After That install kingoroot from your pc then your finished
Tell me if this is not explained correctly
Click to expand...
Click to collapse
After doing as described my device is now rooted, I also restarted it to double check. For those of you looking for assurance. I used a pentest app and exploited my device with a tool. With this tool I can run check_root and it will either say "Device is rooted" or "Device is not rooted" after running it several times, and restarting my device several times, my device remained rooted. Thank you!
Bad Tutorial
First: You aren't writing English properly. How does it make sense to install the same thing twice? Word it properly. I attempted both methods to no avail. I believe this is because English is not your first language. Thanks for the tutorial . I wish I could have that time back. Love from the USA <3.