Related
I've searched and can't seem to find a way to solve the issue.
I'm trying to install a metamorph to make the engadget widget transparent and I need to movie the apk from /data/app to /system/app (according to this post: http://forum.xda-developers.com/showpost.php?p=6319426&postcount=102)
In doing so I've received the cross-device link error.
I've tried these sets of commands:
(note: I am typing the below commands from memory, I got them by searching and I typed them word for word even if the commands below may be incorrect)
Code:
mount -o rw,remount /dev/block/mtdblock5 /data
mount -o rw,remount /dev/block/mtdblock3 /system
mv /data/app/name.of.apk /system/app
HTML:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mv /data/app/name.of.apk /system/app
I've even tried using root explorer and while it shows a progress bar and says it's moving the apk, nothing happens.
I've tried rebooting the phone and the issue still persists.
Can anyone help? Thanks!
Go into /data/data and /data/dalvik-cache and delete all files affiliated with that apk and reboot, the move a copy of the apk file to /system/app, fix permissions and reboot.
let me know if this works.. i'm curious. i had to resort to
Code:
cat /data/app/name.of.app.apk > /system/app
to get it to work. i read somewhere that mv doesn't sit well on android 2.1. cat worked fine, but maybe i didn't realize if mv required the data & dalvik-cache to be wiped.
snandlal said:
Go into /data/data and /data/dalvik-cache and delete all files affiliated with that apk and reboot, the move a copy of the apk file to /system/app, fix permissions and reboot.
Click to expand...
Click to collapse
I tried, but that didn't resolve the issue.
shift_ said:
let me know if this works.. i'm curious. i had to resort to
Code:
cat /data/app/name.of.app.apk > /system/app
to get it to work. i read somewhere that mv doesn't sit well on android 2.1. cat worked fine, but maybe i didn't realize if mv required the data & dalvik-cache to be wiped.
Click to expand...
Click to collapse
That didnt' work either.
To the both of you, thanks for the help so far. I appreciate it.
:-/
Try putting the apk file directly on the c: drive, go into adb shell, do command: mount /system, then command: exit, the command: adb push c:\name of app.apk /system/app
That works for sure, but I'm still left wondering why I can't move a file from one directory to another on the device.
lolz mclollerson said:
That works for sure, but I'm still left wondering why I can't move a file from one directory to another on the device.
Click to expand...
Click to collapse
hmm.. that worked, but mv and cat didn't? that's really weird.
I am also receiving this message. I am trying to:
mount -o remount,rw /dev1/block1/mtdblock4 /system
# mv /sdcard/bootanimation.zip /system/customize/resource
failed on 'bootanimation.zip' - Cross-device link
any ideas??
Evening all,
I am getting very frustrated with my DroidX, since I cannot seem to get it rooted. I believe the crux of my problem lies in that I cannot seem to keep USB Debugging active, even though its enabled. It seems to show up once in awhile, and then just disappears. This does not allow rooters like Z4 to do its job.
I was running the Moto version 5 USB drivers, but backed down to the 4.9 USB drivers and still no luck. Has anyone run into this and can you guide me in rectifying this?
Thanks,
Steve
stevefxp said:
Evening all,
I am getting very frustrated with my DroidX, since I cannot seem to get it rooted. I believe the crux of my problem lies in that I cannot seem to keep USB Debugging active, even though its enabled. It seems to show up once in awhile, and then just disappears. This does not allow rooters like Z4 to do its job.
I was running the Moto version 5 USB drivers, but backed down to the 4.9 USB drivers and still no luck. Has anyone run into this and can you guide me in rectifying this?
Thanks,
Steve
Click to expand...
Click to collapse
what version of Android you have?
I am running VZW stock 2.2.1 but the problem seems to lie in the fact I cannot keep USB debugging on, even though it is enabled on the phone.
Has anyone seen this?
Root your phone without your computer - This would be the path someone on a Mac could take or someone without access to a computer.
This works for the DX and D2 phone, won't work for the D1
Visit the market and get the free Android Terminal Emulator installed.
Visit the market and make sure you have Astro installed.
Grab rageagainsthecage.zip with your phone http://www.droidforums.net/forum/at...s-root-them-unroot-them-rageagainsthecage.zip
Use Astro to navigate to the /sdcard/download folder
Long press on the rageagainstthecage.zip file and "extract to this directory"
The 4 files, from the zip file should now be in the /sdcard/download folder (rageagainstthecage-arm5.bin, su, superuser.apk and busybox.
What are we going to do?
Steps 1- 5: Change to the /tmp folder on your phone, copy the file to the tmp directory, change its permissions. run it, and wait.
Step 6: make sure we can proceed
Steps 7 - 14: make system read-writable, copy the superuser. su and busybox files to where they need to go, use chmode to change their permissions, then make the system folder read-only, and exit Terminal Emulator.
If you want to know more about the commands being used here: cd, cp, chmod, mount, and exit are all Linux commands you can look up on your favorite search engine.
Okay, let's do it - type the blue parts in Terminal Emulator
cd /tmp
cp /sdcard/download/rage*.bin /tmp/
chmod 777 rage*.bin
./rage*.bin
This will take some time, just wait for the $ to show up so you know it is done.
Go to Settings > Applications > Manage Applications > Terminal Emulator > and Force Stop the application
Sanity check - Go into Terminal Emulator again and make sure you have a # symbol as a prompt. If so you are ready to proceed.
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/download/Superuser.apk /system/app/Superuser.apk
cp /sdcard/download/su /system/bin/su
cp /sdcard/download/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
For USB debugging, it might be your usb connection type. Try changing it to computer, mass storage, etc, until you find what's stable. I used Z4root when I did mine. Took like 2 minutes, and no computer, no terminal commands, true one-click root. Don't have the APK anymore, since I've moved on to the Bolt, sorry. But a google search should pull it up.
Thanks to all. I am now rooted. Woo hoo!
Hi Guys,
I have just gotten Wifi Ad Hoc connection working in the Samsung 10.1v (don't see why it won't work on the 10.1 either)
You need to have adb installed and your Tablet needs to be rooted.
I used 2 threads as reference for making this work:
http://forum.xda-developers.com/showthread.php?t=1069569
and
http://forum.xda-developers.com/showthread.php?t=1033314
As a newbie to this i will show you what i did, maybe someone can clean up the process with a simple approach:
You need to turn on Airplane mode to disable wifi, or you will get an error when trying to copy the wpa_supplicant file later on in the instructions...
I had trouble with the adb push command (shown in the above threads) so I did this instead.
Unzip and copy wpa_supplicant file (attached) to Tablet (I used downloads directory)
Get ES File Explorer from Market
Open ES File Explorer and in settings menu select Root options.
Set Root Explorer and use HiAPK
Then Tick Mount File System, then exit menu and navigate to /system/bin and copy wpa_supplicant to somewhere safe (I made backup directory in storage/ sd memory)
Now copy new wpa_supplicant file from where you saved it (downloads directory) to /system/bin
Now in windows command box type:
adb shell
# su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# chmod 755 /system/bin/wpa_supplicant
# chown system.wifi /data/misc/wifi/wpa_supplicant.conf
# exit
Now reboot and turn off airplane mode and enjoy.
Usual conditions if you follow this and something bad happens please don't blame me i used the above method (with trial and error) which worked for me (but maybe i just got lucky)
Also I want to acknowledge the hard working devs that pioneered the process and created the file - great work!!
Good luck...
drnackers said:
Hi Guys,
I have just gotten Wifi Ad Hoc connection working in the Samsung 10.1v (don't see why it won't work on the 10.1 either)
You need to have adb installed and your Tablet needs to be rooted.
I used 2 threads as reference for making this work:
http://forum.xda-developers.com/showthread.php?t=1069569
and
http://forum.xda-developers.com/showthread.php?t=1033314
As a newbie to this i will show you what i did, maybe someone can clean up the process with a simple approach:
You need to turn on Airplane mode to disable wifi, or you will get an error when trying to copy the wpa_supplicant file later on in the instructions...
I had trouble with the adb push command (shown in the above threads) so I did this instead.
Unzip and copy wpa_supplicant file (attached) to Tablet (I used downloads directory)
Get ES File Explorer from Market
Open ES File Explorer and in settings menu select Root options.
Set Root Explorer and use HiAPK
Then Tick Mount File System, then exit menu and navigate to /system/bin and copy wpa_supplicant to somewhere safe (I made backup directory in storage/ sd memory)
Now copy new wpa_supplicant file from where you saved it (downloads directory) to /system/bin
Now in windows command box type:
adb shell
# su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# chmod 755 /system/bin/wpa_supplicant
# chown system.wifi /data/misc/wifi/wpa_supplicant.conf
# exit
Now reboot and turn off airplane mode and enjoy.
Usual conditions if you follow this and something bad happens please don't blame me i used the above method (with trial and error) which worked for me (but maybe i just got lucky)
Also I want to acknowledge the hard working devs that pioneered the process and created the file - great work!!
Good luck...
Click to expand...
Click to collapse
what about the usage of battery after install that wpa_supplicant.conf
Because i used to transfer a similar file like wpa_supplicant.conf to help my samsung Galaxy S i9000 to connect the adhoc WIFI. The usage of battery is horrible, I charged my phone whole night and there is no more battery remaining next morning
I will keep you posted, but been using it on ad hoc for a couple of hours now and nothing out of the usual. Battery seems just same as on wifi.
I will leave it on overnight and report back tomorrow
Sent from my GT-P7100 using XDA App
OK well it has been connected all night to Xperia x10 running barnacle no issues downloading through swarm bittorrent client.
Battery was 78% now at 58% so I would see this as acceptable.
Only 1 issue I have noticed, every time you connect to ad hoc it asks for password and adds it as new connection, so you end up with a few in the list but hold on old connections and 'forget' works fine
Sent from my GT-P7100 using XDA App
drnackers said:
OK well it has been connected all night to Xperia x10 running barnacle no issues downloading through swarm bittorrent client.
Battery was 78% now at 58% so I would see this as acceptable.
Only 1 issue I have noticed, every time you connect to ad hoc it asks for password and adds it as new connection, so you end up with a few in the list but hold on old connections and 'forget' works fine
Sent from my GT-P7100 using XDA App
Click to expand...
Click to collapse
woooo! Wonderful!
I had used the ad hoc wifi and knew that issue already. Anyway, thank you for remining!!
Maybe something should do with the usage of battery, because there is 20% drop during the whole night.........
well, in that case, my cellphone cannot tolerate it
just installed the JuiceDefender app on my 10.1v.
before that, the wifi/3G standby overnight will consume about 10% of battery.
after installing it, and the night more, it went down by 4%.
2nd day of using it and battery life SEEMS better.
I created a zip flashabile on recovery, we'll post it and put it in the first thread?
Anyone try this on 10.1?
DroidHam said:
Anyone try this on 10.1?
Click to expand...
Click to collapse
I haven't tried but it works
I cant seem to get it working right...
After following these steps my wifi drops every 10 seconds... It will see the adhoc though ;-D
I have to disable wifi and re-enable then it will auto join a network for another 10sec before it drops. any advice?
I used adb and it worked "MAKE SURE THAT YOU LOCK THE PERMISSION with CHMOD 755 or it will not work"
put the tablet in airplane mode
I download the file put into C:\ of desk top
I had backup my original by using adb pull /system/bin/wpa_supplicant
these are commands and responses
>adb shell
[email protected]:/ # su
su
[email protected]:/ # mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
[email protected]:/ # chmod 777 /system
chmod 777 /system
[email protected]:/ # chmod 777 /system/bin
chmod 777 /system/bin
[email protected]:/ # chmod 777 /system/bin/wpa_supplicant
chmod 777 /system/bin/wpa_supplicant
[email protected]:/ # exit
exit
[email protected]:/ # exit
exit
>adb push c:\wpa_supplicant /system/bin/wpa_supplicant
1267 KB/s (295964 bytes in 0.228s)
>adb shell
[email protected]:/ # su
su
[email protected]:/ # mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
[email protected]:/ # chmod 755 /system/bin/wpa_supplicant
chmod 755 /system/bin/wpa_supplicant
[email protected]:/ # chmod 755 /system/bin
chmod 755 /system/bin
[email protected]:/ # chmod 755 /system
chmod 755 /system
[email protected]:/ # exit
exit
[email protected]:/ # exit
exit
Tried the flashable zip using cwm 4.0.0.4 but I keep getting installation not successful message. The installation starts, file is opened but the result is unsuccessful. Any suggestions?
10.1v /unlocked / rooted / cwm 4.0.0.4
Edit: Just saw the manual push method above. It will just be so much easier if the flashable version would work.
pushed to system/bin w/ root explorer and edited permissions with RE too.
works so far on my 10.1 retail rooted
nick7920 said:
1267 KB/s (295964 bytes in 0.228s)
Click to expand...
Click to collapse
Works perfectly. The only thing different is the file size reported. Typo?
1762 KB/s (295964 bytes in 0.164s)
baggenismo said:
I cant seem to get it working right...
After following these steps my wifi drops every 10 seconds... It will see the adhoc though ;-D
I have to disable wifi and re-enable then it will auto join a network for another 10sec before it drops. any advice?
Click to expand...
Click to collapse
I have exactly the same issue. I did this same procedure on my galaxy tab (the original 7" one) and it worked great. Replacing the wpa_supplicant file on my galaxy tab 10.1 has the connections work for 10 seconds and then drop. Incidently, I find this is true for all connections (ad-hoc and regular). Switching back to the original file fixes this. I've played around with the config file in /data/mis/wifi/wpa_supplicant.conf and added ap_scan=1, but I've had no luck. I have the 16 GB retail version. My version also had a locked bootloader. Any suggestions would be most appreciated.
Thanks,
Ben
I don't seem to have this problem of wi-fi disconnecting on my 10.1v. So far working perfectly with Connectify, even when the device has screen off, connection seems to persist - I did select never switch to mobile data from settings. I don't know how long it will stay connected though, haven't done a time test yet.
makbil said:
I don't seem to have this problem of wi-fi disconnecting on my 10.1v. So far working perfectly with Connectify, even when the device has screen off, connection seems to persist - I did select never switch to mobile data from settings. I don't know how long it will stay connected though, haven't done a time test yet.
Click to expand...
Click to collapse
My tablet is wifi only. Perhaps this is the issue. Has anyone gotten this to work who has a wifi only tablet (retail edition)?
does not work...
Left the tablet aside for an hour. I unlocked the screen, and instantly opened the web browser. The connection was working. So maybe it does have something to do with 3G connection even though it is turned off. I am using Connectify (free version) on my notebook.
Just thought of something. I have juicedefender set to turn off 3g when my phones screen turns off. This could cut connectivity without dropping wifi signal. Will test theory tomorrow...
Sent from my Galaxy Tab 10.1 using Tapatalk.
After i succesfull deodex my stock rom i've decided to share my experience with ya'll people ...
Here we go :
1. You must be rooted !!!
2. Download -> xUltimate
3. Unzip xUltimate v2.2, and launch "Main.exe"
4. Now xUltimate should recognize the phone and make a connection. You now should see a list of options.
5. Run option 1. After option 1 is done, run option 2.
6. Now these well take a while. Run option 3
7. IMPORTANT: After you have run option 3, you MUST navigate to the xUltimate folder and find "origi_frame" folder, and delete "guava.odex". It's a bad file, and interferes with deodexing process.
8. Now run option 4, and wait.
9. Exit xUltimate, and put the phone in USB mass storage then copy "done_frame", and "done_app" to the root of the sdcard then put the phone in PC mode.
10. Open a command prompt, and do the following:
Code:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
busybox cp /sdcard/done_app/* /system/app/
busybox cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
After phone is boot, reboot again in CWM and Wipe Dalvin Cache, reboot and ENJOY !!!
Notice : The boot will take a little bit longer than normal (2-4 seconds +)
P.S. For step 7 ... there is no guava.odex, don't worry about, continue to next step !
Credits :
Rainabba, Mike919, toxman, teenfaces, Xeudoxus !
Fisrt post ! Good work dude!!
You must have adb (by installing android sdk, platform-tools, install usb driver too) and jdk to do this if anyone is wondering.
kevinlekiller said:
You must have adb (by installing android sdk, platform-tools, install usb driver too) and jdk to do this if anyone is wondering.
Click to expand...
Click to collapse
I assumed that those who want to deodex their rom already knew that, anyway, thanx for reply
Nice tutorial!
Sent from my GT-S5830 using xda premium
Thanks y'all, I will also post other tutorials if i discover something interesting !
I know this question is stupid, but what's the difference between odexed and deodexed rom?
Yesterday I was trying to figure out how to deodex and today you make a tutorial, lol
Thanks.
excellent!! could create one of how to add cf-root and menu extended to create custom roms, is the last thing I need to learn to develop roms
tazlooney89 said:
excellent!! could create one of how to add cf-root and menu extended to create custom roms, is the last thing I need to learn to develop roms
Click to expand...
Click to collapse
Cf root xd to easy
Its in th .zip self
Just extract look in folder and place them where they belong
Sent from my GT-S5830 using xda premium
thanks dude!
now i can get pdroid running on stock rom *_*
Great tutorial thanks!
It would be great if you show how to enable CRT animation in any stock rom ang make grouping widgets in menu.
P4qui7o said:
After i succesfull deodex my stock rom i've decided to share my experience with ya'll people ...
Here we go :
1. You must be rooted !!!
2. Download -> xUltimate
3. Unzip xUltimate v2.2, and launch "Main.exe"
4. Now xUltimate should recognize the phone and make a connection. You now should see a list of options.
5. Run option 1. After option 1 is done, run option 2.
6. Now these well take a while. Run option 3
7. IMPORTANT: After you have run option 3, you MUST navigate to the xUltimate folder and find "origi_frame" folder, and delete "guava.odex". It's a bad file, and interferes with deodexing process.
8. Now run option 4, and wait.
9. Exit xUltimate, and put the phone in USB mass storage then copy "done_frame", and "done_app" to the root of the sdcard then put the phone in PC mode.
10. Open a command prompt, and do the following:
Code:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
busybox cp /sdcard/done_app/* /system/app/
busybox cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
After phone is boot, reboot again in CWM and Wipe Dalvin Cache, reboot and ENJOY !!!
Notice : The boot will take a little bit longer than normal (2-4 seconds +)
P.S. For step 7 ... there is no guava.odex, don't worry about, continue to next step !
Credits :
Rainabba, Mike919, toxman, teenfaces, Xeudoxus !
Click to expand...
Click to collapse
Superb Tutorial Dude...
I am currently testing @Jusadas latest "Carbon Sunday Beta1" rom... It is fully odexed & so far is bug free (Totally)...... I would like to try & DeOdex the rom so that PDroid & Patch can be implemented...
I Know that PDroid framework has now been ported for Odexed roms, but when I flash the Odexed version I get stuck at Android txt during boot...
Will report back if your technique works...
Stay Breezy n Be Lucky...
Pe"ACE"...
Thanx man what a great work , i actually look for deodexing method coz i want to translate an odexed rom but i has to be deodexed first
I'll give it a shot !
Excellent guide!!!
Will try it tmw
Thanks =)
Sent from my GT-P6800 using xda premium
Well the title says manually deodex. But this uses the tool. To manually do it you need to decompile each app individually and then edit it.
Btw, nice giude..
TeamCooper Developer
TheMyth Developer
www.teamcooper.net
ERROR!
Tried this on my stock ddkq8 gingerbread 2.3.6 rom. But whenever I run this line: busybox cp /sdcard/done_app/* /system/app/
it says cp: No space left on device.
and my phone bricks.
It seems that the command does not overwrite the files in /system/app and thus the error.
BTW what do you mean by pc mode?
PLS reply!
galaxyace152 said:
Tried this on my stock ddkq8 gingerbread 2.3.6 rom. But whenever I run this line: busybox cp /sdcard/done_app/* /system/app/
it says cp: No space left on device.
and my phone bricks.
It seems that the command does not overwrite the files in /system/app and thus the error.
BTW what do you mean by pc mode?
PLS reply!
Click to expand...
Click to collapse
Before "10. Open a command prompt, and do the following:"
Just delete some apps to make 40 mb free in system !
That's how i did and work's
Use Root Explorer or something
shaaan said:
Well the title says manually deodex. But this uses the tool. To manually do it you need to decompile each app individually and then edit it.
Btw, nice giude..
TeamCooper Developer
TheMyth Developer
www.teamcooper.net
Click to expand...
Click to collapse
Developer Talking
---------- Post added at 08:57 PM ---------- Previous post was at 08:56 PM ----------
Stuck on boot loop! :| And yes, I wiped everything. Nice tutorial BTW, appreciate it.
EDIT: Never mind. Sorted it.
C:\android-sdk-windows\platform-tools>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
$ su
su
# stop
stop
# mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
# busybox cp /sdcard/done_app/* /system/app/
busybox cp /sdcard/done_app/* /system/app/
cp: can't stat '/sdcard/done_app/*': No such file or directory
# busybox cp /sdcard/done_frame/* /system/framework/
busybox cp /sdcard/done_frame/* /system/framework/
cp: can't stat '/sdcard/done_frame/*': No such file or directory
# rm /system/app/*.odex
rm /system/app/*.odex
# rm /system/framework/*.odex
rm /system/framework/*.odex
# mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
# reboot
reboot
C:\android-sdk-windows\platform-tools>
how come mine is like this...? anyone can help me...? plz
after that my phone cant start...it stuck on the galaxy ace screen...???
It took some doing, but after following the instructions in this link:
http://forum.xda-developers.com/showthread.php?t=2559915
I was finally able to root my Nook Glowlight. The instructions are kind of sprawled out and extremely unclear so I will sum up.
As always, you will need the ADB. In order to install the ADB, you need the Java Development Kit and the Android Studio (formerly known as the Android SDK)
http://www.oracle.com/technetwork/java/javase/downloads/index.html
http://developer.android.com/sdk/installing/studio.html
How to obtain root via ADB: The ONLY way you can root is using Windows. I was successful on Windows 7 32 bit, but it may be possible on other versions.
step 1) install bootloader driver.
You need to grab the drivers from here (bnusbdrivers.zip):
http://forum.xda-developers.com/showpost.php?p=49665945&postcount=279&nocache=1&z=184593200683593
then, open the Device Manager (on Windows). Be ready to right click on the new device 'omap3660' that shows.
With the nook turned completely off, plug in a USB cable. you will have less than 3 seconds to right click the new omap3660 device that shows up in the system profiler.
If you were successful and you right clicked on it in time, manually install the Barnes & Noble USB driver (there are entries added to the generic Google drivers for both the TI Omap 3660 bootloader and the ADB device after you modify the uRamdisk later on)
***NOTE***
If you WEREN'T successful on your first try (took me THREE times to get to it in time), you aren't going to get another chance to install the drivers. At least not easily anyway, because after Windows tries to automatically install the drivers for the bootloader and fails, it will disregard the device any time it shows up after that. So, you are going to need to delete the registry entries that it created, which in my experience was easier said than done. Even admin access was not sufficient to make the necessary changes to the registry.
You will need to launch regedit.exe using another tool called psexec which is available here:
http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx
after you download the pstools package, copy those .exe files to C:\Windows\System32\ (in order to add them to $PATH in cmd.exe)
Then, once you've installed the pstools commands to C:\Windows\System32\, run cmd.exe as admin (right click it and select 'run as administrator') and then open regedit.exe with the following command
Code:
psexec -s -i -d regedit.exe
Then, once regedit is open you need to find the keys created by the Nook bootloader and delete them. The Nook bootloader's device ID is 0451:d00e
You are going to be looking in HKEY_LOCAL_MACHINE\Current Control Set\enum\usb\ for the keys with the bootloader's device IDs. There may also be keys generated in control set 001 and 002 as well. Delete all of those keys and then reboot your computer. Then with the nook power off completely, repeat the process from the first step. eventually you will be successful installing the bootloader driver.
Step 2) temporarily boot with uRamdisk-noogie
you need to download omaplink.exe from here:
http://www.temblast.com/android.htm
and you also need to download the four files which allow you to temporarily mount the boot partition; omap3_aboot.bin, u-boot-ng2-exp-v03.bin, uImage-ng2-130-stk and uRamdisk-noogie.
They are available here:
http://forum.xda-developers.com/showpost.php?p=49779966&postcount=285
download usbboot-ng2-images-noogie-v1.zip
The next part is easy.
Extract the .zip file and then fire up cmd.exe. cd into the directory of the newly extracted .zip
in the new working directory, enter the command
Code:
omaplink omap3_aboot.bin u-boot-ng2-exp-v03.bin uImage-ng2-130-stk uRamdisk-noogie
Then, with the Nook powered all the way off and omaplink running, plug it in and a few seconds later, after the device boots up all the way, you will be looking at the contents of the boot partition instead of the internal storage like normal.
Step 3) Edit uRamdisk
you will need to download bootutil.exe from here
http://www.temblast.com/android.htm
copy bootutil.exe to C:\Windows\System32
with the boot partition mounted, copy uRamdisk to your computer and extract the files init.rc and default.prop, eg;
Code:
bootutil /x /v uRamdisk init.rc default.prop
then using notepad++ (available here: http://notepad-plus-plus.org/) edit the files as follows
default.prop
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
and
init.rc
comment out lines 375 and 392-399
(do this by adding a # to the beginning of the line)
uncomment line 215
(do this by deleting the # at the beginning of the line)
save both files and then repack them into uRamdisk
Code:
bootutil /r /v uRamdisk init.rc default.prop
copy uRamdisk back onto the Nook, eject the disk and power off the device. Reboot and you should be able to connect to ADB via WiFi
eg;
Code:
adb connect 192.168.0.10
replacing '10' with whatever IP your Nook is grabbing from your router.
Step 4) Full Root
at this point, you have root access via ADB only. You will not have root access in any apps like Root Explorer, Terminal, TiBackup, etc.
In order to finish PROPERLY rooting your Nook, you need to install 'su' to /system/bin/ and install the superuser.apk
Code:
adb connect 192.168.0.10
adb shell mount -o remount, rw /system
adb push su /system/bin/
adb shell chmod 6755 /system/bin/su
adb install superuser.apk
reboot your device one more time and then you will be fully rooted.
*** Note ***
this devices firmware seems to be a strange hybrid between donut and eclair, although it purports itself to be Android 2.1. The Superuser.apk and su binary came from an old Cyanogenmod 4.6 build in case anyone was wondering (Android Donut). The ones from Cyanogenmod 5 (Android Eclair) do not work. you will get the 'install failed older sdk' error.
installing busybox
I tired installing busybox by using the stericson busybox pro.apk. It would always freeze at 6.47%.
I figured out that if I grabbed an older version of the busybox binary and pushed it to /system/xbin manually and then chmodded it to the proper permissions, auto updates and proper symlinking work using the busybox app
Code:
adb shell mount -o remount, rw /system
adb shell mkdir -p /system/xbin
adb push busybox /system/xbin
adb shell chmod 6755 /system/xbin/busybox
adb install busybox.apk
Then reboot, and run the busybox app to update and create symlinks.
enjoy!
installing nano and bash
Code:
adb connect 192.168.0.10
adb shell
mount -o remount, rw /system
adb push nano /system/xbin/
chmod 6755 /system/xbin/nano
adb push bash /system/xbin/
chmod 6755 /system/xbin/bash
bash
mv /system/bin/sh /system/bin/sh.bak
ln -s /system/xbin/bash /system/bin/sh
chmod 6755 /system/bin/sh
adb push profile /system/etc/
adb push terminfo /system/etc/
and then in terminal emulator under 'Preferences' change the initial command to
Code:
export TERMINFO=/system/etc/terminfo;export TERM=linux;export HOME=/sdcard;
and finally
Code:
adb push bashrc /sdcard
adb shell
mv /sdcard/bashrc /sdcard/.bashrc
exit
nano works just fine via ADB, but because of lack of 'ctrl' key (and physical buttons to assign it to) you won't be able to write files (ctrl+o) using the terminal on your nook. But between having full proper root access, busybox, a proper bash terminal emulator and nano for editing config files, this should REALLY extend the usefulness of your Nook Glowlight. It should work just fine on other versions of Nook too.
Hi N00b-un-2,
Many thanks for your summary!
There is one important edit that I think you missed,
in init.rc you also need to:
Line #375, comment out "disabled" with a # at the start of the line.
(see http://forum.xda-developers.com/showthread.php?p=49070213#post49070213)
without this I couldn't get adb to connect.
And since you already made it very noob friendly, might I suggested you clarify:
Line #215 remove # to enable adb over wifi
(rather than search for 5555)
Also, I'm not expert, but I believe the commands to get superuser on the device are (at least it worked for me):
adb connect 192.168.x.x
adb shell mount -o remount, rw /system
adb push su /system/bin/
adb shell chmod 6755 /system/bin/su
adb install superuser.apk
Finally, I'm not sure if this is important, but maybe remount system as read only again:
adb shell mount -o remount, ro /system
Thanks again, nice work!
---------- Post added at 01:48 PM ---------- Previous post was at 01:10 PM ----------
Hi again,
had similar issues with installing busybox, here's what worked for me (note needed to run su to create dir):
adb shell mount -o remount, rw /system
adb shell /system/bin/su
adb shell mkdir -p /system/xbin
adb push busybox /system/xbin
adb shell chmod 6755 /system/xbin/busybox
adb install busybox.apk
cheers.
As far as remounting /system as ro, I would HIGHLY recommend just rebooting at this point, otherwise your nook might be stuck in a weird pseudo-rooted state. Probably won't cause any problems, but why risk it?
Thanks for clarifying the line number. I will make the appropriate edits to my instructions. I was working off the top of my head and couldn't remember what exact line the ADB over TCP config was, as I just used ctrl+w '5555' to find it myself.
There are several pre-edited uRamdisk images floating around the forum with various features enabled which would be easier for noobs than extracting the config files and manually editing and then repacking them. In the future I'll probably throw those on here as well.
darz said:
Hi N00b-un-2,
Many thanks for your summary!
There is one important edit that I think you missed,
in init.rc you also need to:
Line #375, comment out "disabled" with a # at the start of the line.
(see http://forum.xda-developers.com/showthread.php?p=49070213#post49070213)
without this I couldn't get adb to connect.
And since you already made it very noob friendly, might I suggested you clarify:
Line #215 remove # to enable adb over wifi
(rather than search for 5555)
Also, I'm not expert, but I believe the commands to get superuser on the device are (at least it worked for me):
adb connect 192.168.x.x
adb shell mount -o remount, rw /system
adb push su /system/bin/
adb shell chmod 6755 /system/bin/su
adb install superuser.apk
Finally, I'm not sure if this is important, but maybe remount system as read only again:
adb shell mount -o remount, ro /system
Thanks again, nice work!
---------- Post added at 01:48 PM ---------- Previous post was at 01:10 PM ----------
Hi again,
had similar issues with installing busybox, here's what worked for me (note needed to run su to create dir):
adb shell mount -o remount, rw /system
adb shell /system/bin/su
adb shell mkdir -p /system/xbin
adb push busybox /system/xbin
adb shell chmod 6755 /system/xbin/busybox
adb install busybox.apk
cheers.
Click to expand...
Click to collapse
N00b-un-2 said:
There are several pre-edited uRamdisk images floating around the forum with various features enabled which would be easier for noobs than extracting the config files and manually editing and then repacking them. In the future I'll probably throw those on here as well.
Click to expand...
Click to collapse
Would have been good if I could have easily found a pre-edited image, but your instructions were a great alternative, thanks again
darz said:
Would have been good if I could have easily found a pre-edited image, but your instructions were a great alternative, thanks again
Click to expand...
Click to collapse
Sorry for the really noob question, I have rooted, wifi adb running and installed apps as per your instructions, but I can't seem to access any of it on the nook. How can I get access to the launcher I installed?
You mentioned pre-edited images, do any of those come with the apps I need to get access to a custom launcher?
Cheers,
Dariusz
==============
Updated: All sorted
==============
For some reason had some issues with ADW launcher, Launcher pro worked fine.
ps I think I made a mistake with the su step I suggested, if you run a one line shell command I don't think it keeps su privileges, so I believe you need to run commands within the shell as per below:
adb shell
mount -o remount, rw /system
/system/bin/su
mkdir -p /system/xbin
exit
adb push busybox /system/xbin
adb shell chmod 6755 /system/xbin/busybox
adb install busybox.apk
Noob
Hey guys any instructions noob friendly or a video in youtube,i stick up at dab connect 192.168.0.10.I dos't have a Windows PC and using Mac whit Parallels Desktop.Is it possible instructions for Mac?
The above instructions from N00b-un-2 should work fine running a vm with parallels on your Mac.
OB
Sent from my SPH-D710VMUB using Tapatalk 2
valentin1985 said:
Hey guys any instructions noob friendly or a video in youtube,i stick up at dab connect 192.168.0.10.I dos't have a Windows PC and using Mac whit Parallels Desktop.Is it possible instructions for Mac?
Click to expand...
Click to collapse
Before you perform the adb connect step you need to find out what your IP address is:
On your nook, click on the settings icon in the top right corner and then select "Change"
Under Wireless Networks, select the wifi name that you are already connected to (where it says "Connected to the internet")
This will display your connection details, remember that IP address
Now go back to your pc and type:
adb connect [IP address]
darz said:
Before you perform the adb connect step you need to find out what your IP address is:
On your nook, click on the settings icon in the top right corner and then select "Change"
Under Wireless Networks, select the wifi name that you are already connected to (where it says "Connected to the internet")
This will display your connection details, remember that IP address
Now go back to your pc and type:
adb connect [IP address]
Click to expand...
Click to collapse
BIG HINT! If you're using Powershell ISE, you have to type .\adb.exe connect [IP address] or else it won't recognize "adb" as an executable!
Don't ask why, because I don't know. :?
thenookieforlife3 said:
BIG HINT! If you're using Powershell ISE, you have to type .\adb.exe connect [IP address] or else it won't recognize "adb" as an executable!
Don't ask why, because I don't know. :?
Click to expand...
Click to collapse
So far so good,but now what?
valentin1985 said:
So far so good,but now what?
Click to expand...
Click to collapse
I just gave a little tip on Powershell ISE. I do not know much about the Nook GlowLight rooting process, as I have a NSTG, not a NG. Ask someone else.
thenookieforlife3 said:
I just gave a little tip on Powershell ISE. I do not know much about the Nook GlowLight rooting process, as I have a NSTG, not a NG. Ask someone else.
Click to expand...
Click to collapse
Yes,i try whit dis command .\adb.exe connect 192.168.0.9 but result is the same.
valentin1985 said:
Yes,i try whit dis command .\adb.exe connect 192.168.0.9 but result is the same.
Click to expand...
Click to collapse
But that's okay! What I said was, if you are using the command program Powershell ISE, do it that way instead. But you are just using cmd.exe, not Powershell ISE!
In cmd.exe, which is what you are using, it is not neccessary to type .\adb.exe. Just type adb.
From there, ask someone else in this thread.
thenookieforlife3 said:
But that's okay! What I said was, if you are using the command program Powershell ISE, do it that way instead. But you are just using cmd.exe, not Powershell ISE!
In cmd.exe, which is what you are using, it is not neccessary to type .\adb.exe. Just type adb.
From there, ask someone else in this thread.
Click to expand...
Click to collapse
I prefer to use ConEmu or Console2 when I am forced to use Windows. Not a big fan of CMD.EXE or Powershell/PowershellISE. there are plenty of other CLI alternatives out there
N00b-un-2 said:
I prefer to use ConEmu or Console2 when I am forced to use Windows. Not a big fan of CMD.EXE or Powershell/PowershellISE. there are plenty of other CLI alternatives out there
Click to expand...
Click to collapse
Well, as I ONLY use Windows and Powershell ISE has a nice-enough layout for my purposes, I use it. That's why I gave a tip on it.
Actually on a lot of installs just typing adb in the command console won't work either unless it's got the path variable set up correctly, I find it easiest to just right click and choose run as administrator, no need for the path to be setup.
OB
Sent from my SPH-D710VMUB using Tapatalk 2
FW 1.2.1
Hi guys,
thanks for creating this thread. I was wondering if this rooting procedure was tested with the firmware 1.2.1 ?
real-6 said:
Hi guys,
thanks for creating this thread. I was wondering if this rooting procedure was tested with the firmware 1.2.1 ?
Click to expand...
Click to collapse
This rooting procedure is for the new Nook GlowLight with firmware 1.3.1. Your device is a Nook Simple Touch with GlowLight, which can be rooted very easily using the rooting package here.