How to root Nook HD+ (and Nook HD too, I guess).
(Thanks for some useful ideas to sparkym3: http://forum.xda-developers.com/member.php?u=4411543 )
(tested only on 2.0.0 version (as comes out of the box), also works on 2.0.2
Get one of the attached files: root_win.zip if you are on windows, or root_unix.tgz if you are on Linux or Mac.
unpack the file to some dir and run "makeroot" on Windows or "sh makeroot.sh" on Mac/Linux
After a couple of reboots you should be able to do
adb shell and issue a "su" command in the shell and get the root prompt (#).
Thanks to someone0 for his prior investigations here.
Known bugs:
Superuser.apk does not really install because package manager could not be contacted.
Oh, and I think you'll find this interesting too:
Hai.
Kind of a two-fer, eh?
I noticed that people see their Nook HDs restoring to factory settings after 8 unsuccessful reboots next time you boot after rooting, so possibly there's some extra check somewhere.
Very sneaky on the B&N side, I'd say.
Hm, the 8 failed boot = wipe and restore has been true since the NC, and is valuable because it helps keep the device from getting bricked, also triggerable if the registration token doesn't match BN's reg token. I learned this early on by restoring a backup made before I'd erased and deregistered. I forget where the token lives, in /data/ somewhere.
I'll take a look at this on 2.0.2 this weekend - mine updated before I got ADB working so it restores to 2.0.2 now...
OK, so this approach does work with the 2.0.2 OS, and restarting the device does put it into a boot cycle. Very nasty.
Before I rebooted, I removed the post_boot_hook file and also got rid of the symlink; I'd say BN is doing some kind of inventory of what's in system and driving a reflash based on that.
My guess is it's not a very careful inventory, but it'll certainly be amenable to study now that we can get, at least temporarily, root.
Hm. Interesting -- my ability to mkdir /data/su is now gone after the restore. I wasn't able to do it the first time I tried, either - I suspect that there's something keeping some level of eye on that.
Oh, very uncool - in addition to resetting the system, they wipe personal data in the process. Losing the apps doesn't surprise me much. Losing the books I'd sideloaded surprises me.
roustabout said:
Hm, the 8 failed boot = wipe and restore has been true since the NC, and is valuable because it helps keep the device from getting bricked, also triggerable if the registration token doesn't match BN's reg token. I learned this early on by restoring a backup made before I'd erased and deregistered. I forget where the token lives, in /data/ somewhere.
I'll take a look at this on 2.0.2 this weekend - mine updated before I got ADB working so it restores to 2.0.2 now...
OK, so this approach does work with the 2.0.2 OS, and restarting the device does put it into a boot cycle. Very nasty.
Before I rebooted, I removed the post_boot_hook file and also got rid of the symlink; I'd say BN is doing some kind of inventory of what's in system and driving a reflash based on that.
My guess is it's not a very careful inventory, but it'll certainly be amenable to study now that we can get, at least temporarily, root.
Hm. Interesting -- my ability to mkdir /data/su is now gone after the restore. I wasn't able to do it the first time I tried, either - I suspect that there's something keeping some level of eye on that.
Oh, very uncool - in addition to resetting the system, they wipe personal data in the process. Losing the apps doesn't surprise me much. Losing the books I'd sideloaded surprises me.
Click to expand...
Click to collapse
Do the new HD & HD+ still allow you boot from the external sd card ?
roustabout said:
Hm, the 8 failed boot = wipe and restore has been true since the NC, and is valuable because it helps keep the device from getting bricked, also triggerable if the registration token doesn't match BN's reg token. I learned this early on by restoring a backup made before I'd erased and deregistered. I forget where the token lives, in /data/ somewhere.
I'll take a look at this on 2.0.2 this weekend - mine updated before I got ADB working so it restores to 2.0.2 now...
OK, so this approach does work with the 2.0.2 OS, and restarting the device does put it into a boot cycle. Very nasty.
Before I rebooted, I removed the post_boot_hook file and also got rid of the symlink; I'd say BN is doing some kind of inventory of what's in system and driving a reflash based on that.
My guess is it's not a very careful inventory, but it'll certainly be amenable to study now that we can get, at least temporarily, root.
Hm. Interesting -- my ability to mkdir /data/su is now gone after the restore. I wasn't able to do it the first time I tried, either - I suspect that there's something keeping some level of eye on that.
Oh, very uncool - in addition to resetting the system, they wipe personal data in the process. Losing the apps doesn't surprise me much. Losing the books I'd sideloaded surprises me.
Click to expand...
Click to collapse
if you put your books into /system/media, it will back them up to the cloud
Is it possible to push a new recovery with adb after rooting? The 8 failed boot repair is only possible with the stock recovery. But then again you may end up in an endless bootloop without it there to finish it's task. But maybe you can find and delete the trigger flag that starts the process.
leapinlar said:
Is it possible to push a new recovery with adb after rooting? The 8 failed boot repair is only possible with the stock recovery. But then again you may end up in an endless bootloop without it there to finish it's task. But maybe you can find and delete the trigger flag that starts the process.
Click to expand...
Click to collapse
stuff is best to be not mentioned. /sarcasm.....
recovery is signed, so it's not super easy to replace it with anything that would run.
The unsigned bootloader trick at the moment requires a boot from sdcard.
shouldn't step 8 & 9 be outside the code block?
verygreen:
I just want to thank you for your all your work on the Nook series. I've been using your "size-agnostic method ..." tools and process to run from the SD card on my Nook Color since you created the method, and now I'm excited to use your work on my new Nook HD+ (just received yesterday) !
just got mine and got an update notification. turned off wifi so it didnt complete.any word if it breaks root ir bootloader?
CWM is now possible too.
Something is interesting, eventhough mine originally got automatically updated to 2.0.2, but after the factory reset, it went back to 2.0.0. But for some weird reason I can't get root.
Maybe this will help, the build number is 2.0.0.1031.lithium01.ovation.rldp.s68403 with the manufactured date 10/22/2012
please compare mine to your.
I also rewrote your code into a batch file. You can double check it I guess.
Code:
@echo off
cls
@echo .
@echo wait for it
@echo .
adb devices
@echo .
@echo if you do not see you device listed above hit ctrl+c and exit the script
@echo then check adb on your PC and device then try again.
@echo .
@echo reroute /data/local/tmp
adb wait-for-devices shell rm -r /data/local/tmp
adb shell ln -s /data/ /data/local/tmp
@echo .
@echo Now rebooting
@echo .
adb reboot
@echo .
@echo waiting for reboot to finish and making directory /data/su
adb wait-for-devices shell mkdir /data/su
@echo uploading su
adb push su /data/su/
@echo uploading busybox
adb push busybox /data/su/
@echo uploading boot_complete_hoot
adb push boot_complete_hook.txt /data/boot_complete_hook.sh
adb shell chmod 755 /data/boot_complete_hook.sh /data/su/*
@echo .
@echo Now rebooting again
@echo .
adb reboot
@echo .
@echo waiting for reboot to finish and getting shell
adb wait-for-devices shell
someone0 said:
Something is interesting, eventhough mine originally got automatically updated to 2.0.2, but after the factory reset, it went back to 2.0.0. But for some weird reason I can't get root.
Maybe this will help, the build number is 2.0.0.1031.lithium01.ovation.rldp.s68403 with the manufactured date 10/22/2012
please compare mine to your.
I also rewrote your code into a batch file. You can double check it I guess.
Click to expand...
Click to collapse
so, when you run this, after the final adb shell, what are the permissions on /system/xbin/su?
run su and you should get the root prompt.
I don't get root prompt, su never get copied to /system/xbin/su
here is the list of my finding.
Code:
/data/
-rwxr-xr-x shell shell 167 2012-11-10 05:52 boot_complete_hook.sh
/data/su
-rwxr-xr-x shell shell 586212 2012-11-10 06:07 busybox
-rwxr-xr-x shell shell 22364 2012-11-10 06:07 su
/data/local
lrwxrwxrwx shell shell 2012-11-10 06:20 tmp -> /data/
cat boot_complete_hook.sh
#!/system/bin/sh
/data/su/busybox mount /system -o remount,rw
/data/su/busybox cp /data/su/su /system/xbin/su
chown 0.0 /system/xbin/su
everything is in place and correct, but no dice. either boot_complete_hook.sh didn't get executed or it did but never get launched with root permission.
someone0 said:
I don't get root prompt, su never get copied to /system/xbin/su
here is the list of my finding.
Code:
/data/
-rwxr-xr-x shell shell 167 2012-11-10 05:52 boot_complete_hook.sh
/data/su
-rwxr-xr-x shell shell 586212 2012-11-10 06:07 busybox
-rwxr-xr-x shell shell 22364 2012-11-10 06:07 su
/data/local
lrwxrwxrwx shell shell 2012-11-10 06:20 tmp -> /data/
cat boot_complete_hook.sh
#!/system/bin/sh
/data/su/busybox mount /system -o remount,rw
/data/su/busybox cp /data/su/su /system/xbin/su
chown 0.0 /system/xbin/su
everything is in place and correct, but no dice.
Click to expand...
Click to collapse
well, there should be more stuff in the shell file, you miss the final chown line: chmod 06755 /system/xbin/su
It did, I just didn't copy and paste the output correctly. But regardless, since the foulder /system/xbin don't have the su file, this mean as I suspected earlier, either it wasn't executed or lauched w/ root permission.
someone0 said:
It did, I just didn't copy and paste the output correctly. But regardless, since the foulder /system/xbin don't have the su file, this mean as I suspected earlier, either it wasn't executed or lauched w/ root permission.
Click to expand...
Click to collapse
check if your /system/bin/clrbootcount.sh calls /data/boot_complete_hook.sh
verygreen said:
check if your /system/bin/clrbootcount.sh calls /data/boot_complete_hook.sh
Click to expand...
Click to collapse
This is interesting, it look as if it won't launch the /data/boot_complete_hook.sh
Code:
cat /data/boot_complete_hook.sh
#!/system/bin/sh
/data/su/busybox mount /system -o remount,rw
/data/su/busybox cp /data/su/su /system/xbin/su
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
[B][email protected]:/data $ /data/boot_complete_hook.sh
/data/boot_complete_hook.sh
/system/bin/sh: /data/boot_complete_hook.sh: No such file or directory
1|[email protected]:/data $
[/B]
Yub it does
Code:
cat clrbootcount.sh
#!/system/bin/sh
################################################################################
##
#
# File clrbootcount.sh
# Description Clear the bootcount variable to 0 on successful boot
#
##
# Run potential hook first.
[B]/data/boot_complete_hook.sh[/B]
# Zero the boot count
cat /system/etc/zerobootcnt > /bootdata/BootCnt
Related
All credit for the binary goes to Sebastian Krahmer at http://c-skills.blogspot.com/. Please see fit to donate via Paypal to [email protected]
If you want a simpler 'one-click' process, go to this thread: Easier 1-2-3 Droid 2 Root for Windows / Linux / Mac
***NOTE: Proceed at your own risk. I and the providers of this code are not responsible for anything you do to your phone!***
Setup:
- Install adb (here) and Motorola drivers for windows(32-bit or 64-bit)
- Download attached archive
- Extract to a directory, I used c:\Droid2Root
- Make sure you have USB degugging enabled
- Change connection to PC Mode
Process:
- Open command prompt
- cd c:/wherever-your-sdk-tools-folder-is
- adb devices (to verify the connection)
- cd c:/Droid2Root
- adb push Superuser.apk /sdcard/Superuser.apk
- adb push su /sdcard/su
- adb push busybox /sdcard/busybox
- adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
- adb shell
- cd data/local/tmp
- chmod 0755 rageagainstthecage-arm5.bin
- ./rageagainstthecage-arm5.bin
- let the process run until it 'kicks' you out (may take a minute or two) to c:/Droid2Root
- cd c:/wherever-your-sdk-tools-folder-is
- adb kill-server
- adb devices (to verify the connection)
- adb shell (you should now have a # prompt, if not return to ./rage step above)
- mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
- cp /sdcard/Superuser.apk /system/app/Superuser.apk
- cp /sdcard/su /system/bin/su
- cp /sdcard/busybox /system/bin/busybox
- chmod 4755 /system/bin/su
- chmod 4755 /system/bin/busybox
- mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
- exit
- exit
I'm sure there are certain steps that could be streamlined or eliminated, so please feel free to make a suggestion and I'll edit the post.
Additional thanks to @rainabba and AllDroid.org for their excellent Droid X rooting tutorial, which assisted me greatly in this process.
waiting for a recovery, glad to see its rooted
Android n00b here, I can remove the Verizon crapware with this right? And tether?
thelolotov said:
Android n00b here, I can remove the Verizon crapware with this right? And tether?
Click to expand...
Click to collapse
yes and yes
thelolotov said:
Android n00b here, I can remove the Verizon crapware with this right? And tether?
Click to expand...
Click to collapse
I wouldn't remove anything yet since we don't have a sbf file to recover from partial bricks. However, tethering and any other apps that require root can be used now.
I'm new to doing this all the adb way.
When you say extract to a directory what do you mean to extract. After it downloads the achive files its done.....
i understand the rest of the commands but im lost there
Hmm, alright, that's still worth it, will I lose my data/have to hard reset to root?
Right click the downloaded archive and "extract files". You need to do this so adb can push them to the phone.
thelolotov said:
Hmm, alright, that's still worth it, will I lose my data/have to hard reset to root?
Click to expand...
Click to collapse
Nope, it just gives you access. Nothing deleted.
I'm retarded i didnt realize it was attached to the post, i thought it was what adb downloaded when i first opened it cause it called them archives.
cannot access
I got as far as pushing super user su and busy box onto my phone but it says that system in read only.. how do i fix this?
Anybody actually try this?
Hello,
I am following your directions and when I get to the "adb push Superuser.apk" step I receive the following error:
"failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file system"
I get this same error for the other adb push steps that follow.
Edit: To verify, I get a # shell.
Edit 2: I tried pushing the Superuser.apk to /data/local/tmp then cp to /system/app/, this also popped up a read-only file system error.
I'm currently trying it.
I have a 64 bit driver on my computer that i used to use for my D1 but it doesn't recognize my D2 when doing adb devices and i cant install the 32 bit driver
GSletta said:
I got as far as pushing super user su and busy box onto my phone but it says that system in read only.. how do i fix this?
Click to expand...
Click to collapse
Did you verify you have the # prompt three steps before that?
Yeah i get the # but it wont let me push superuser su and busybox
GSletta said:
Yeah i get the # but it wont let me push superuser su and busybox
Click to expand...
Click to collapse
Weird.. I didn't need to mount the system manually, but let me if there's a step I left out.
and some more screens (feel free to use in first post):
http://i.imgur.com/nPllt.jpg
http://i.imgur.com/COTEA.jpg
http://i.imgur.com/open3.jpg
djh816 said:
and some more screens (feel free to use in first post):
http://i.imgur.com/nPllt.jpg
http://i.imgur.com/COTEA.jpg
http://i.imgur.com/open3.jpg
Click to expand...
Click to collapse
Did you add any steps to mount the system? I don't believe I did, but it seems others are finding it to be read-only.
jerseyh22accord said:
I'm currently trying it.
I have a 64 bit driver on my computer that i used to use for my D1 but it doesn't recognize my D2 when doing adb devices and i cant install the 32 bit driver
Click to expand...
Click to collapse
Don't know if it will help you, but if it's anything like the DInc, you could just use the SDK's drivers and add a few device identifier lines to the INF file before installing them.
Has anyone begun working on rooting and customizing roms yet? I know the device isn't out for a week or so but I would figure I would ask. My vibrant I so much better rooted and I wanted the same experience on this sidekick.
Sent from my SGH-T839 using XDA App
Wreximus said:
Has anyone begun working on rooting and customizing roms yet? I know the device isn't out for a week or so but I would figure I would ask. My vibrant I so much better rooted and I wanted the same experience on this sidekick.
Sent from my SGH-T839 using XDA App
Click to expand...
Click to collapse
i wish i knew how to do this, but if i can't figure it out, i'm sure others will soon.
Just got mine last night. The usual Samsung trick with rageagainstthecage-arm5.bin works great.
abliss said:
Just got mine last night. The usual Samsung trick with rageagainstthecage-arm5.bin works great.
Click to expand...
Click to collapse
Oh really? Cool. So far all I've used is one-click root for the Samsung Epic.... is this similar? I'll check it out, thanks!
Has anyone tried using SuperOneClick yet?? I will probably try in a bit and post back with my results..
Ok... well I didn't try SuperOneClick, but I did root it via the rageagainstthecage exploit...
Want to help me do the exploit on my SK4G to root it man ?
Give me instructions ?!
I got it working on mine too. The basic steps were
1) enable debug USB mode on your phone
2) install Samsung drivers for the phone - right now Samsung's site seems to not have a choice for the Sidekick 4G's model (SGH-T839), but I grabbed the drivers for the Vibrant (at www .samsung.com/us/support/downloads/SGH-T959ZKDTMB) and they worked.
3) get adb shell working on your PC (Google it)
4) download the rageagainstthecage-arm5.bin and Superuser packages from the links in this page: wiki.cyanogenmod.com/index.php?title=HTC_Hero_%28CDMA%29:_Full_Update_Guide (be sure to unzip the files into the directory where your adb.exe program is unless you've put it in your path)
5) reboot your phone and plug it in
6) adb push rageagainstthecage-arm5.bin /data/local/tmp
7) adb shell
8) cd /data/local/tmp
9) chmod 755 rageagainstthecage-arm5.bin
10) ./rageagainstthecage-arm5.bin
11) wait until you get booted back out to your DOS command prompt
12) adb kill-server
13) adb start-server
14) adb shell
15) you should now be at a # prompt. The first few times I tried, I wasn't - I was at $. Doing this from a fresh boot seemed to be the trick. Reboot your phone and try again if you're getting a $.
16) mount -o remount,rw /dev/block/stl9 /system
17) exit
18) adb push su /system/xbin
19) adb shell chmod 4755 /system/xbin/su
20) adb push Superuser.apk /system/app
21) adb shell mount -o remount,ro /dev/block/stl9 /system
22) exit
23) reboot the phone then run an app that requests root, such as Root Explorer, to verify
(p.s. sorry for having to mangle the URL's above, XDA won't let me include links since I haven't posted 8 times yet)
josby said:
16) mount -o remount,rw /dev/block/st19 /system
18) adb push su /system/xbin
19) adb shell chmod 4755 /system/xbin/su
20) adb push Superuser.apk /system/app
21) adb shell mount -o remount,ro /dev/block/st19 /system
Click to expand...
Click to collapse
Just to note, on step 16 and 21... it is /dev/block/stl9 rather than st19
Also, after step 20, I had to run the following commands for the superuser application to grant root privledges to applications..
adb shell echo "root::0:0:root:/data/local:/system/bin/sh" > /etc/passwd
adb shell echo "root::0:" > /etc/group
Awesome to see it being rooted so fast.
I'm really interesting in getting this phone but I'm not in the US. Does anyone know if the phone will work outside US?
brenix said:
Just to note, on step 16 and 21... it is /dev/block/stl9 rather than st19
Click to expand...
Click to collapse
Dang, good catch, thanks. That's what I get for not copying and pasting from my terminal window...stupid, since I was just chastising two people at work for making the same mistake yesterday. I've edited the original post to prevent problems for people who might start before reading the entire thread.
Interesting about having to create a passwd and group file...I've only run a few root apps so far, but they've worked without me doing this. I wonder if it's app-specific.
Now to start removing some of the damn bloatware this thing comes with!
19) adb shell chmod 4755 /system/xbin/su
i get stuck on there it says unable to chmod no such file or directory . there's SU in my android-sdk/tools
i'm so glad this thing got rooted. i used to be a scene kid with a kick. i dont have this phone, i doubt i'm going to get this phone considering the sensation is droppin soon.... but for nostalgia purposes, i'm glad it got rooted. now you can really hack it!!!
not like the old ones!!
Good looking out...I rooted mine earlier today. What version of Clockworkmod Recovery are you all using?
fawkReviewz said:
19) adb shell chmod 4755 /system/xbin/su
i get stuck on there it says unable to chmod no such file or directory . there's SU in my android-sdk/tools
Click to expand...
Click to collapse
Double-check your step 18...that's the step that copies the su file from your computer onto the phone. I forget the exact output format, but it shows you a Kb/second number of how fast the file transfer went when it finishes successfully.
droctii said:
Good looking out...I rooted mine earlier today. What version of Clockworkmod Recovery are you all using?
Click to expand...
Click to collapse
I'm not brave enough to try putting the ClockworkMod for one of the Samsung devices on the list onto mine, for fear of bricking it. Don't know enough about that works as far as hardware differences go.
I have removed the APK's listed below from /system/app with no apparent ill-effects. Not that YOU should remove them necessarily - just that they're things I don't have a need for:
AccountAndSync.apk
AmazonMp3.apk
AppPack.apk
DriveSmart.apk
DriveSmartHelper.apk
install_flash_player.apk
LiveWallpapers.apk
LiveWallpapersPicker.apk
Memo.apk
MiniDiary.apk
MobileBackup.apk
MyFiles.apk
PhoneSetupWizard.apk
Twitter-2.0.1-121.apk
vvm-signed.apk
Though there must be something I don't fully understand, because even after a reboot, Amazon MP3 and AppPack are still on my phone, and they still work.
FYI, don't remove Settings.apk - I got stuck in a loop where the launcher kept crashing then reloading itself (thank goodness I was able to put it back in place with adb).
Can anyone tell me if Setcpu works for them?
Ace42 said:
Can anyone tell me if Setcpu works for them?
Click to expand...
Click to collapse
Appears to work fine.. no crashes although the Max Hz is 1000. U can still raise the Min Hz.
Sent from my Nexus S using XDA App
Can someone post a full:
ls of / and /dev/block and /efs
Thanks
Will this phone get a proper sub-forum on xda?
I been looking for an ATT Avail root guide since january, I found this page today and I am wondering if anyone has done this successfully?
if you google "root att avail" it is the top search result link right now and it is at a site called android police.
here is a copy/paste of the article:
New root methods show up all the time, so it's not a huge deal that a rather unknown phone on AT&T is now rooted. So why are we posting about it? Because the root method used is, well... interesting.
It was uncovered by our own Justin Case from TeamAndIRC, and while a big part of the process will look very familiar to some of you, there is one step that induces a wait, what? moment.
Before you get started throwing commands at the little guy, though, you need to grab this file. After that, commence command throwing.
adb shell rm -r /data/local/logs (if this command gives you an error, do not worry, it is precautionary)
adb shell mkdir /data/local/logs
adb shell ln -s /data/local.prop /data/local/logs/loglast1.tar.gz
Dial *983*7668# on your phone. This does a few things, it mounts /system as writable on boot, and creates the loglast1.tar.gz.
Wait about 10 seconds, then continue.
adb shell echo 'ro.kernel.qemu=1' > /data/local.prop (Nod to Rosenberg here)
adb reboot
Once the phone reboots, continue
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb shell rm -r /data/local/logs
adb shell rm /data/local.prop
adb shell rm /data/property/persist.sys.ztelog.enable
adb shell rm -r /data/local/rwsystag
Head into the Market and grab the Superuser app.
Done.
Catch that bold part? Looks like someone at ZTE dropped the ball and left seventy-nine developer codes in the retail version of the device. Oops.
Of course, their mistake is your gain. Hell, there's even a code to disable Carrier IQ: *983*24737#. Enter the code, ???, profit.
While this is definitely an unusual and unique find, it's also quite dangerous. This means that any app can mount the system as writable and, from there, basically control everything. As a result, JCase contacted ZTE to let them know of their oversight.
Click to expand...
Click to collapse
if someone could let me know if this is legit, that would be a fantasticism.
yes that is legit.
see my thread:
http://forum.xda-developers.com/showthread.php?t=1437032
Jcase broke it, the loon created a batch file to make it easier
http://forum.xda-developers.com/showpost.php?p=21627136&postcount=37
thats the last version of the batch file
Cool, thanks, for some reason I cannot connect to my avail via usb, I have it in developer mode and unknown sources checked, I ran adb devices command and it does not find my phone and when I try to run or debug in eclipse it does not find my phone there either.
I used it, and now have root. I wish all phones were this easy to root.
Update: Friday November 2nd 2012
Fixed a bad upload of the su file, must of become corrupt sorry.
Silly permission bug again, but w/e. LG should know better, from what I am told this is a recently released device. This is a long standing known issue. Lg get your sh*t together.
Directions:
unzip su.zip into the current path (directory) you are in.
adb shell
(while in adb shell)
rm /data/local/tmp/profile_calib_m
ln -s /data/local.prop /data/local/tmp/profile_calib_m
exit
adb reboot
adb wait-for-device shell
(once in the adb shell again)
echo 'ro.kernel.qemu=1' > /data/local.prop
rm /data/local/tmp/profile_calib_m
exit
adb reboot
adb wait-for-device remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 6755 /system/xbin/su
adb shell rm /data/local.prop
adb reboot
Once rebooted install superuser from the market:
https://play.google.com/store/apps/details?id=com.noshufou.android.su
As usual thanks for all your work for this GREAT community!!! :good:
Thanks for letting me watch you work & getting root for my wife's phone.
Edit: DroidHost of Androidarea51.com has made a OneClick for this phone using Jcase's root. it also installs a recovery & Superuser all at the same time.
androidarea51.com/***-all-things-
root-***-174/
Help Me Please
what do you do when it says permission denied or not permitted when waiting for device, remounting, or pushing su?
lol now all we need is someone to write different roms :>
cyanogen would be nice :> lol
thank you for rooting this phone :>
jcase, i pmd you i need help please
TechManPro said:
what do you do when it says permission denied or not permitted when waiting for device, remounting, or pushing su?
Click to expand...
Click to collapse
run adb shell
make sure your prompt is a # not a $. If it is a $ start over, if it is a # make sure you run adb remount.
jbach44 said:
lol now all we need is someone to write different roms :>
cyanogen would be nice :> lol
thank you for rooting this phone :>
Click to expand...
Click to collapse
No problem.
You actually left out a step. In order to push su to the phone you have to adb remount -o rw. Otherwise it is a read-only filesystem and it cannot be pushed to the phone. Most people would probably get this, but the novices who end up with bricked phones will be angry.
Great work!
iliekandroid said:
You actually left out a step. In order to push su to the phone you have to adb remount -o rw. Otherwise it is a read-only filesystem and it cannot be pushed to the phone. Most people would probably get this, but the novices who end up with bricked phones will be angry.
Great work!
Click to expand...
Click to collapse
Actually no, you are incorrect.
adb remount without the additional parameters is correct, and not possible of bricking a phone with adb remount. No novice would be angry, because there is not possible brick from this guide, as long as it is followed.
I got the LG for my daughter (13 going on 30), and now it works fine. Thanks jcase.
Did not unlock my lgl35g
Yes I am a Noob... nobody likes me
I have exhausted every resource that I could find on this phone. I thought that this post was the answer to my problem, however it did not seem to help at all. Everything seemed as if it was working fine as I went step by step through the process. However, I rebooted my phone and there is no difference then when I started. The "su.zip" file enclosed in this post was not able to extract into the directory of my ADB client. It kept saying root already existed, but I was unable to see it in windows explorer? Is this "su.zip" a modified version of a pre-existing file in the SDK kit? I really need to unlock this phone so that I can clean up the junk. Any help would be greatly appreciated.
jcase said:
Update: Friday November 2nd 2012
Fixed a bad upload of the su file, must of become corrupt sorry.
Silly permission bug again, but w/e. LG should know better, from what I am told this is a recently released device. This is a long standing known issue. Lg get your sh*t together.
Directions:
unzip su.zip into the current path (directory) you are in.
adb shell
(while in adb shell)
rm /data/local/tmp/profile_calib_m
ln -s /data/local.prop /data/local/tmp/profile_calib_m
exit
adb reboot
adb wait-for-device shell
(once in the adb shell again)
echo 'ro.kernel.qemu=1' > /data/local.prop
rm /data/local/tmp/profile_calib_m
exit
adb reboot
adb wait-for-device remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 6755 /system/xbin/su
adb shell rm /data/local.prop
adb reboot
Once rebooted install superuser from the market:
Click to expand...
Click to collapse
anyone know of a way to SIM unlock this device? I have AT&T and would like to use it om there, i bought it for $30 on clist thinking net 10 would work with an AT&T SIM but was wrong, any help would be appreciated...
anyone know of a way to SIM unlock this device? I have AT&T and would like to use it om there, i bought it for $30 on clist thinking net 10 would work with an AT&T SIM but was wrong, any help would be appreciated...
Click to expand...
Click to collapse
What is weird about that is i put the sim in a iphone and it worked just fine!!! Best bet would be ebay for unlock...
I have the Net10 one that I put a Straight Talk SIM in with no problems if I can get my hands on a AT&T SIM today I'll check it out.
---------- Post added at 07:39 AM ---------- Previous post was at 07:34 AM ----------
NateDoggTN said:
Yes I am a Noob... nobody likes me
I have exhausted every resource that I could find on this phone. I thought that this post was the answer to my problem, however it did not seem to help at all. Everything seemed as if it was working fine as I went step by step through the process. However, I rebooted my phone and there is no difference then when I started. The "su.zip" file enclosed in this post was not able to extract into the directory of my ADB client. It kept saying root already existed, but I was unable to see it in windows explorer? Is this "su.zip" a modified version of a pre-existing file in the SDK kit? I really need to unlock this phone so that I can clean up the junk. Any help would be greatly appreciated.
:
Click to expand...
Click to collapse
Did you push the su binary file or the whole folder? If you pushed the whole folder you will have to remove the directory & start over.
how to run root
Sorry for sounding like a noob, but I am...when it comes to LG. im trying to root my homies LG optimus logic but im not sure where to run the command from. if some one could help me out on to where the zip should actullay be placed and unziped to that would be a big help, thanks. and if there is a thread already for this please hook up a link.
thanks
thanks mate for this
i appreciate your time.
Anyone know of a rooted ROM
I have looked all over, but it doesn't look like a dev has created a ROM for this device. Has anyone come across one? If I knew programming I would give it a shot, but it's a mystery to me. I know that CyanogenMod 9 for the L3 (e400) works, but there is a problem with the radios, hence no cellular, wifi, or bluetooth.
Source code......
http://www.lg.com/global/support/opensource/opensource-detail.jsp
http://forum.xda-developers.com/showthread.php?p=34104009
This guy had some success with CM9, but no radio. Anyone know how to extract the radio? I've never built a rom, but this is tempting.
Ok, so a friend of mine bought 3 of these things from Kohls on Black Friday as Christmas presents for her kids and has asked me to help set them up as kid friendly devices. Unfortunately they don't come with any Gapps installed and I'm having difficulty installing any of them including the Play Store. I'm also running into problems installing simple games like Angry Birds. In fact very few of the APK's that I have backed up from my other Android devices seem to want to install on these tablets. I also can't find any forums on here or anywhere else evening addressing these devices yet. I'm wondering if there's some kind of generic udate.zip I can use for these things that isn't device specific? A little while back I was able to install an update.zip on a Zeki tablet that enabled me to finally install all the Gapps and maximize it's potential. But then again those things come rooted out of the box and the update was Zeki specific, so...
Anyways, please if anyone can help? This could be your chance to be the first to help unlock the potential of these devices.
Rooting PTAB8000
This is NOT my work, it is from mbellot at FreakTab, but it worked great for me.
Rooting is easy, market is nearly as easy. Here is the original thought process.
Here it is, modified the way I have done it (a couple times), broken into logical chunks.
1. C:\ADB> adb shell
2. [email protected]:/ $ mv /data/local/tmp /data/local/tmp.bak
3. [email protected]:/ $ ln -s /data /data/local/tmp
4. [email protected]:/ $ exit
5. C:\ADB> adb reboot
This gives you write access to /data for the next set of steps.
6. C:\ADB> adb wait-for-device
7. C:\ADB> adb shell
8. [email protected]:/ $ echo ro.kernel.qemu=1 >/data/local.prop
9. [email protected]:/ $ exit
10. C:\ADB> adb reboot
This puts you into a "debug" mode of sorts, the LCD will be black after the boot logo comes and goes.
11. C:\ADB> adb wait-for-device
12. C:\ADB> adb remount
remount succeeded
13. C:\ADB> adb push su /system/bin/su
518 KB/s (22364 bytes in 0.042s)
14. C:\ADB> adb shell
15. [email protected]:/ # chown root.shell /system/bin/su
16. [email protected]:/ # chmod 06755 /system/bin/su
17. [email protected]:/ # rm /system/xbin/su
rm failed for /system/xbin/su, No such file or directory
18. 255|[email protected]:/ # ln -s /system/bin/su /system/xbin/su
19. [email protected]:/ # exit
The chown and chmod in steps 15 and 16 are critical to su working properly.
20. C:\ADB> adb push Superuser.apk /system/app/.
3923 KB/s (843503 bytes in 0.209s)
At this point you can install market files. You need to do it before you remove the local.prop file since the PTAB8000 refuses to run adb in root mode or allow remounting. You can use this as a starting point for installing market, but I would suggest you grab the latest ICS gapps and replace the files. Also, market/play is not vending.apk in ICS, its phonesky.apk.
Once you're done with su and market you need to make your tablet boot normal again.
21. C:\ADB> adb shell
22. [email protected]:/ # rm /data/local.prop
23. [email protected]:/ # rm /data/local/tmp
24. [email protected]:/ # mv /data/local/tmp.bak /data/local/tmp
25. [email protected]:/ # exit
26. C:\ADB> adb reboot
Finished.
Thanks.
HD Brian said:
This is NOT my work, it is from mbellot at FreakTab, but it worked great for me.
Rooting is easy, market is nearly as easy. Here is the original thought process.
Here it is, modified the way I have done it (a couple times), broken into logical chunks.
1. C:\ADB> adb shell
2. [email protected]:/ $ mv /data/local/tmp /data/local/tmp.bak
3. [email protected]:/ $ ln -s /data /data/local/tmp
4. [email protected]:/ $ exit
5. C:\ADB> adb reboot
This gives you write access to /data for the next set of steps.
6. C:\ADB> adb wait-for-device
7. C:\ADB> adb shell
8. [email protected]:/ $ echo ro.kernel.qemu=1 >/data/local.prop
9. [email protected]:/ $ exit
10. C:\ADB> adb reboot
This puts you into a "debug" mode of sorts, the LCD will be black after the boot logo comes and goes.
11. C:\ADB> adb wait-for-device
12. C:\ADB> adb remount
remount succeeded
13. C:\ADB> adb push su /system/bin/su
518 KB/s (22364 bytes in 0.042s)
14. C:\ADB> adb shell
15. [email protected]:/ # chown root.shell /system/bin/su
16. [email protected]:/ # chmod 06755 /system/bin/su
17. [email protected]:/ # rm /system/xbin/su
rm failed for /system/xbin/su, No such file or directory
18. 255|[email protected]:/ # ln -s /system/bin/su /system/xbin/su
19. [email protected]:/ # exit
The chown and chmod in steps 15 and 16 are critical to su working properly.
20. C:\ADB> adb push Superuser.apk /system/app/.
3923 KB/s (843503 bytes in 0.209s)
At this point you can install market files. You need to do it before you remove the local.prop file since the PTAB8000 refuses to run adb in root mode or allow remounting. You can use this as a starting point for installing market, but I would suggest you grab the latest ICS gapps and replace the files. Also, market/play is not vending.apk in ICS, its phonesky.apk.
Once you're done with su and market you need to make your tablet boot normal again.
21. C:\ADB> adb shell
22. [email protected]:/ # rm /data/local.prop
23. [email protected]:/ # rm /data/local/tmp
24. [email protected]:/ # mv /data/local/tmp.bak /data/local/tmp
25. [email protected]:/ # exit
26. C:\ADB> adb reboot
Finished.
Click to expand...
Click to collapse
HD Brian,
I'm going to say thanks because I'm sure everything you just posted is probably going to be very clear to quite a few people that understand all of that. So thank you for helping out. Unfortunately though for me, I got lost. Though I've been tinkering with android and windows mobile devices for about 3 years now, I've actually never done any ADB editing and not sure I fully understand how to do it.
Personally I'm not too concerned about modifying these things too much because they are for someone else's kids, and I've found a way to work around rooting and using Gapps to be able to install the apps they're needing. And before I hand these things back over to be wrapped for Christmas I'm going to make a video showing what I've done to maximize the out of box potential of these things.
But on that note, I'm going to make a request of you if you don't mind. Considering you seem to know how to easily achieve the task, I was wondering if you'd be willing to make and post a Youtube video that takes people through the steps. I know it might be time consuming, but after all we are all here to help each other out. And I'm sure that the people who actually own these devices would really appreciate it. At this point I haven't been able to find any videos on how to mod this tablet yet and the only forums that I've found discussing these things are the one you mentioned and this one here.
So I hope you'll be willing to help other owners out, and I appreciate you taking the time to respond.
Thanks
I had been thinking about reloading the stock rom and doing the root all again as a refresher for myself, but I have never done a YouTube video before. I will try to find the time to do it and them I will post the link here.
For anyone still having issues with rooting and getting the play store on this device I have just made a script to automate the whole process.
filedropper [dot] com / polaroidaio
Note ADB drivers are required.
TeODH4 said:
For anyone still having issues with rooting and getting the play store on this device I have just made a script to automate the whole process.
filedropper [dot] com / polaroidaio
Note ADB drivers are required.
Click to expand...
Click to collapse
Thanks! I was able to run this script, it read the tablet, I asked it to root and install gapps, it said it completed but when the device restarts, I see the polaroid logo twice, then the screen goes black and just sits there forever. I was able to re-install factory and boot it back up so that was good. But didn't know if you had any ideas on what was wrong with my device. I'm using a brand new stock Polaroid PTAB8000 ICS 4.0.3. Windows 7, freshly installed Android Development Kit from today to get my ADB.
smokethrower2 said:
Thanks! I was able to run this script, it read the tablet, I asked it to root and install gapps, it said it completed but when the device restarts, I see the polaroid logo twice, then the screen goes black and just sits there forever. I was able to re-install factory and boot it back up so that was good. But didn't know if you had any ideas on what was wrong with my device. I'm using a brand new stock Polaroid PTAB8000 ICS 4.0.3. Windows 7, freshly installed Android Development Kit from today to get my ADB.
Click to expand...
Click to collapse
Any luck with this script yet? Also, how were you able to flash back to factory?
Wanted to add, got the same black screen so I booted to recovery and did factory reset which got me back to square 1. I install the getjar app store and did a search for gmail. when it came up i downloaded it, and during the installation it also installed the "Google Play" store. I was getting a few errors but after turning sync on and using the store for a bit they all cleared up so far. Now I have google play and gmail apps on the tab.
BigT504 said:
Wanted to add, got the same black screen so I booted to recovery and did factory reset which got me back to square 1. I install the getjar app store and did a search for gmail. when it came up i downloaded it, and during the installation it also installed the "Google Play" store. I was getting a few errors but after turning sync on and using the store for a bit they all cleared up so far. Now I have google play and gmail apps on the tab.
Click to expand...
Click to collapse
Sorry about the black screen issue guys there was an issue with the code. I've also completely rewritten the application in c++. All features should work without issues now.
You can download the software here: mediafire [dot] com/?o2864kb92hcc0hb (sorry i can't post links yet, I'll work on getting some posts done...)
1) Download RAR file
2) Extract RAR file
3) Run PolaroidAIO.exe
4) Enable USB debugging and Stay awake
5) Drivers are included in this release if needed
6) Enjoy your fully rooted tablet with the Play Store and Google Services Framework.
If anyone is intrested in the source code let me know and I will post it as well...
Have fun guys!
---------- Post added at 09:58 AM ---------- Previous post was at 09:26 AM ----------
smokethrower2 said:
Thanks! I was able to run this script, it read the tablet, I asked it to root and install gapps, it said it completed but when the device restarts, I see the polaroid logo twice, then the screen goes black and just sits there forever. I was able to re-install factory and boot it back up so that was good. But didn't know if you had any ideas on what was wrong with my device. I'm using a brand new stock Polaroid PTAB8000 ICS 4.0.3. Windows 7, freshly installed Android Development Kit from today to get my ADB.
Click to expand...
Click to collapse
There was a bug in the old code, same thing happend to mine after i did a factory reset to try and replicate your situation. Try the updated version 1.2 and let me know if u face any simular issues.
---------- Post added at 10:14 AM ---------- Previous post was at 09:58 AM ----------
Dossey said:
HD Brian,
I'm going to say thanks because I'm sure everything you just posted is probably going to be very clear to quite a few people that understand all of that. So thank you for helping out. Unfortunately though for me, I got lost. Though I've been tinkering with android and windows mobile devices for about 3 years now, I've actually never done any ADB editing and not sure I fully understand how to do it.
Personally I'm not too concerned about modifying these things too much because they are for someone else's kids, and I've found a way to work around rooting and using Gapps to be able to install the apps they're needing. And before I hand these things back over to be wrapped for Christmas I'm going to make a video showing what I've done to maximize the out of box potential of these things.
But on that note, I'm going to make a request of you if you don't mind. Considering you seem to know how to easily achieve the task, I was wondering if you'd be willing to make and post a Youtube video that takes people through the steps. I know it might be time consuming, but after all we are all here to help each other out. And I'm sure that the people who actually own these devices would really appreciate it. At this point I haven't been able to find any videos on how to mod this tablet yet and the only forums that I've found discussing these things are the one you mentioned and this one here.
So I hope you'll be willing to help other owners out, and I appreciate you taking the time to respond.
Thanks
Click to expand...
Click to collapse
Hey I just wanted to point out that you can indeed use root and remount /system. if you have proper root. which my AIO application will test for you as well. Here's what you do to remount /system as r/w:
Code:
C:\dev\adb>adb shell
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount,rw /system
mount -o remount,rw /system
[email protected]:/ # chmod 777 /system
chmod 777 /system
[email protected]:/ # chmod 777 /system/app
chmod 777 /system/app
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
C:\dev\adb>adb push sample.apk /system
/app/sample.apk
12 KB/s (187 bytes in 0.015s)
C:\dev\adb>adb shell
[email protected]:/ $ su
su
[email protected]:/ # chmod 755 /system/app
chmod 755 /system/app
[email protected]:/ # chmod 755 /system
chmod 755 /system
[email protected]:/ # mount -o remount,ro /system
mount -o remount,ro /system
[email protected]:/ #
I was able to get the play store on with the first upload and then by following a couple of steps from aother tutorial, but I can't seem to get any apps in the Play Store to open or download. I keep getting a "device is not compatible" message. I've tried the DPI play store and also messed around with LCD Density Monitor but haven't had any luck. If someone could help tackle this problem as well as get netflix up and running, I would be extremely grateful. This seems like a pretty awesome tablet, it just needs to be let free.
I feel I should also add, for anyone considering doing this, that once you have the Play Store installed, at least in my experience; if you have it hooked up to a PC via the USB and try to install anything, it goes ape sh** and starts trying to force close and kicks a whole bunch of errors. It doesn't seen to do anything, but it's annoying as hell. I haven't tried it yet with it plugged into the charger, and it doesn't do it nearly as much when you have it unplugged, but it's just another one of those quirks that I'm sure will be fixed in due time.
TeODH4 said:
Sorry about the black screen issue guys there was an issue with the code. I've also completely rewritten the application in c++. All features should work without issues now.
You can download the software here: mediafire [dot] com/?o2864kb92hcc0hb (sorry i can't post links yet, I'll work on getting some posts done...)
1) Download RAR file
2) Extract RAR file
3) Run PolaroidAIO.exe
4) Enable USB debugging and Stay awake
5) Drivers are included in this release if needed
6) Enjoy your fully rooted tablet with the Play Store and Google Services Framework.
If anyone is intrested in the source code let me know and I will post it as well...
Have fun guys!
---------- Post added at 09:58 AM ---------- Previous post was at 09:26 AM ----------
There was a bug in the old code, same thing happend to mine after i did a factory reset to try and replicate your situation. Try the updated version 1.2 and let me know if u face any simular issues.
---------- Post added at 10:14 AM ---------- Previous post was at 09:58 AM ----------
Hey I just wanted to point out that you can indeed use root and remount /system. if you have proper root. which my AIO application will test for you as well. Here's what you do to remount /system as r/w:
Code:
C:\dev\adb>adb shell
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount,rw /system
mount -o remount,rw /system
[email protected]:/ # chmod 777 /system
chmod 777 /system
[email protected]:/ # chmod 777 /system/app
chmod 777 /system/app
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
C:\dev\adb>adb push sample.apk /system
/app/sample.apk
12 KB/s (187 bytes in 0.015s)
C:\dev\adb>adb shell
[email protected]:/ $ su
su
[email protected]:/ # chmod 755 /system/app
chmod 755 /system/app
[email protected]:/ # chmod 755 /system
chmod 755 /system
[email protected]:/ # mount -o remount,ro /system
mount -o remount,ro /system
[email protected]:/ #
Click to expand...
Click to collapse
Just to be sure you may want to run the updated script because there was alot of garbage left behind by 1.0. which 1.2 will clean up.
1) Select "Remove Google Applications and Framework"
2) When done, select "Un-Root Device"
3) Finally select "Root Device and Install Google Applications, and Framework"
This will clean up the garbage left behind by 1.0 and might help with some of your issues.
I am aware that some apps are showing up as un-supported, I'm pretty sure its an issue with build.prop. I'm looking into it right now. Are you having issues with all the apps on the play store? or just some of them like netflix, angry birds, etc? Also can you elaborate on what errors you are getting? I think i need to find an updated version of google services framework, I've noticed when the market upgrades to the play store it will crash quite a few times during the updates, and then gets better but does crash from time to time. Don't hurt functionality but it is very annoying.
If you find any info on any of this please be sure to share. I'll try and get an updated release out tonight that takes care of at least some of these issues... At least we are making progress...
I downloaded the files from location listed above but it my anti virus primped me for a Trojan virus... Is this not a secure release?
psctornado said:
I downloaded the files from location listed above but it my anti virus primped me for a Trojan virus... Is this not a secure release?
Click to expand...
Click to collapse
This is a secure release, it probably doesn't like all the files embedded into the exe... I can re-upload it un-packed if you like.
No it's ok I thought I would ask. So the big issue is the play store?
psctornado said:
No it's ok I thought I would ask. So the big issue is the play store?
Click to expand...
Click to collapse
Yes, the protected applications do not show up, or if you try to use the web site, and send an app to your device it will say unsupported, I'm going to take a look at my build.prop in a little bit and see if i cant get the full market working. From what I can tell its google blocking the apps because this is a non google supported device. which is why we needed to load the play store in the first place, if you run AIO 1.2 you will at least get all Googles app's working... Gmail, etc. I will have an update out soon to fix the play store issues, and hopefully fix the crashing gapps service...
Okay. I don't have the tablet with me right now, but when I do, I'll redo everything. Also, I was able to get Netflix to work by downloading it from Amazon's App store and everything "seemed" to work. I'll have to try more testing when I get the tablet back. As far as the Play store goes, it just says that it has stopped working and has to close, and when I hit okay, the error goes away but it stays open. I'll get the exact verbatim when it pops up again. Other than that, nice work and hopefully we can work out the kinks.
TeODH4 said:
Just to be sure you may want to run the updated script because there was alot of garbage left behind by 1.0. which 1.2 will clean up.
1) Select "Remove Google Applications and Framework"
2) When done, select "Un-Root Device"
3) Finally select "Root Device and Install Google Applications, and Framework"
This will clean up the garbage left behind by 1.0 and might help with some of your issues.
I am aware that some apps are showing up as un-supported, I'm pretty sure its an issue with build.prop. I'm looking into it right now. Are you having issues with all the apps on the play store? or just some of them like netflix, angry birds, etc? Also can you elaborate on what errors you are getting? I think i need to find an updated version of google services framework, I've noticed when the market upgrades to the play store it will crash quite a few times during the updates, and then gets better but does crash from time to time. Don't hurt functionality but it is very annoying.
If you find any info on any of this please be sure to share. I'll try and get an updated release out tonight that takes care of at least some of these issues... At least we are making progress...
Click to expand...
Click to collapse
rysimpson318 said:
Okay. I don't have the tablet with me right now, but when I do, I'll redo everything. Also, I was able to get Netflix to work by downloading it from Amazon's App store and everything "seemed" to work. I'll have to try more testing when I get the tablet back. As far as the Play store goes, it just says that it has stopped working and has to close, and when I hit okay, the error goes away but it stays open. I'll get the exact verbatim when it pops up again. Other than that, nice work and hopefully we can work out the kinks.
Click to expand...
Click to collapse
If the play store is just crashing then i would most definitely recommend using 1.2 to clean things up and reload the playstore, you may even want to go as far as to do a factory reset after you un-install and un-root... Well for some reason build.prop doesn't seem to change anything on the market, I'm downloading an updated gapp for 4.0.3 maybe that will take care of some issues under the hood.
TeODH4 said:
If the play store is just crashing then i would most definitely recommend using 1.2 to clean things up and reload the playstore, you may even want to go as far as to do a factory reset after you un-install and un-root... Well for some reason build.prop doesn't seem to change anything on the market, I'm downloading an updated gapp for 4.0.3 maybe that will take care of some issues under the hood.
Click to expand...
Click to collapse
So are you saying a clean install will remedy the issue?what is the 1.2 download link?
psctornado said:
So are you saying a clean install will remedy the issue?what is the 1.2 download link?
Click to expand...
Click to collapse
Sorry for the late response, but it should fix some of the issues. See the thread below for more info on current bugs...
I will now be posting all project updates and downloads here: http://forum.xda-developers.com/showthread.php?t=2066041
BigT504 said:
Any luck with this script yet? Also, how were you able to flash back to factory?
Click to expand...
Click to collapse
I haven't tried the new version yet since I don't have my laptop with me right now but I'll try it later. To reset back to factory after getting stuck on the black screen follow this sites direction. You will need a micro SD card. southerntelecom dot com / polaroidsupport / firmware /firmware_guide_ptab8000 dot html then download the files for your model and then put them on the SD card and insert the SD card in the tablet. Then to start the factory reset hold down volume down and power at the same time until you see the update screen come up. I believe that is what it said. It should explain it all in the link. If my link won't post since I'm new just Google ptab8000 firmware and click on the link for a southerntelecom firmware site.