Related
first I would like to say all i did is to re-write instructions with help from booker-t for the nexus files and others narrowed down the steps
also cant forget the people who made this possible
Paul O'Brien:
Koushik K. Dutta:
unrevoked.com OTA Spoofing Method
ChiefzReloaded Brain Storming Guru
Prerequisites
- First from what I found is only able to work with frf72 (atleast in my tests may work on others but definatly did not on erd) so if need be first go and get on that version which I will not cover here plenty of steps
- newest sdk from developer.android.com
- class 6 sdcard (what worked for me)
- micro usb cable
1) download the N1_Root.zip attached from below (thanks booker-t for the work on that) and extract all of the files to the sdk/tools folder
2) now we need to make sure all is detecting drivers right go to applications >> development >> usb debugging
this establishes that we have the adb driver necessary in the pc already
also
3) here is a trick you need to see or find a way of inserting the media card while the battery is still in the phone and make sure you can (i trimmed down the little lip on the battery and allowed me to tightly squeeze the card in)
4) remove battery and sd card and plug phone back in
5) open command prompt to tools folder and type loop
6) connect device and power on in bootloader via vol - and power
7) then go to recovery only on triangle screen leave it there - keeping an eye on phone screen when on triangle screen in a few seconds computer will beep and will see in the running loop that is in recovery mode adb
use ctrl + c on pc to stop that loop
(you may need to reboot the phone a few times with the process to have it seen)
8) now with still just on regular triangle screen slip in the media card
9) on device use power and vol + to see options and click apply update (this will fail since not on media card which is good)
10) in the command line run the following commands:
adb push busybox /sdcard
adb push flash_image /sdcard
adb push ota.zip /sdcard/update.zip
11) in command line type but do not run yet this command:
adb push update /sdcard
12) on device click to apply update and as soon as you do and start seeing the line on screen run the above command. May need a few times to take You will know when it does and screen will clear itself
13) once that completes you can try the following command
adb push flash_image /system/bin
(you may get permission denied errors if you do get the root explorer app from market to copy sadly su file manager did't work for it)
- if it didn't work we need that there so you can reboot and copy if command not working
14) when get got that part your phone is rooted then with flash_image where it needs to be
grab your favorite recovery either amons or clockwork and use a terminal editor to apply and make a nandroid backup
15) apply your new rom and have fun
permission denied on frf83 bummer... this method was working on frf72
elite67 said:
permission denied on frf83 bummer... this method was working on frf72
Click to expand...
Click to collapse
permission denied for pushing the files? i get that on frf72 as well.
still unable to mount the card lol. will reformat card and try again
When do you get the error "permission denied" with using the flash_image command? That is what I ran into and root explorer app let me copy the flash_image file from the sdcard to /system/bin/
hit and miss, my card reads pny class 6, 8gb however not all the time just keep rebooting and trying, one thing I did was remove all my android drivers and let windows reinstall them again, seems like it made it read all the time, I was able to push files in frf72
help .. im done with part 13 .. but i dont understand part 14.!!
help plz!! im sooo close!
I am getting permission denied on FRF83 also.
BUT
why isn't flash_image inside the update.zip with su and superuser.apk?
That way we wouldn't have to push it!
That would be the only possibility for us stuck on FRF83?
(Unless there is a way to revert back to FRF72 from FRF83, but I don't think there is.)
Ok, getting ADB to recognize my device in recovery mode but getting "permission denied"
Using an 8gb Nokia (assuming class 2) card on FRF83.
A good question would be, can you do this on a 2.1 device? Or does it require 2.2
torchedlh said:
Ok, getting ADB to recognize my device in recovery mode but getting "permission denied"
Using an 8gb Nokia (assuming class 2) card on FRF83.
Click to expand...
Click to collapse
select apply update.zip one time before pushing
Can anyone CONFIRM being able to do this on FRF83? Dang, I guess I missed my chance while I was still on FRF72...
Nevermind -- looks like this has been addressed on another thread:
http://forum.xda-developers.com/showthread.php?t=710351
M9x3mos said:
3) here is a trick you need to see or find a way of inserting the media card while the battery is still in the phone and make sure you can (i trimmed down the little lip on the battery and allowed me to tightly squeeze the card in)
Click to expand...
Click to collapse
It might be easier to get a few wires and carefully connect the battery to the pins so that the battery is out but powering the device.
I was thinking of the same thing and would have been easy enough on the phone to use stripped ethernet wire wrapped arround but holding the leads on battery itself would be a little harder. Zipping the little lip off of battery and gently forcing the memory card in was easier for the 3 times I needed to do it to get the process right.
M9x3mos said:
I was thinking of the same thing and would have been easy enough on the phone to use stripped ethernet wire wrapped arround but holding the leads on battery itself would be a little harder. Zipping the little lip off of battery and gently forcing the memory card in was easier for the 3 times I needed to do it to get the process right.
Click to expand...
Click to collapse
This. I found that simply blocking the ports on the SDcard doesnt work. It has to click in to mount
shaving that little part off is very simple and the sd goes straight in. after 5-6 hours of trying over 3 days....this worked immediately
Using a small strip of paper to block the microSD card's contacts works very well. just slide it in the slot, slide the card in there, click it in, and you're good to go.Just make sure the peice of paper isn't too wide and that it goes all the way in.
PS - i have been trying to flash update.zip before running the ADB push commands.
torchedlh said:
Using a small strip of paper to block the microSD card's contacts works very well. just slide it in the slot, slide the card in there, click it in, and you're good to go.Just make sure the peice of paper isn't too wide and that it goes all the way in.
PS - i have been trying to flash update.zip before running the ADB push commands.
Click to expand...
Click to collapse
.....it doesnt work lol.....
youll get mount errors in recovery if you simply remove the paper. youll get adb. actually inserting the card will eliminate the error
Now that we have our own forum, time to stake a claim.
Nooter is an image that's loaded to a microSD card that can boot the Nook Color into a basic Linux environment. It automatically enables adb and turns off ro.secure on bootup, so no interaction is necessary to get root. Nooter sets up the USB port as a USB ethernet device (RNDIS) compatible with most modern OSes to allow SSH logins. From there the ROM can be dumped, partitions mounted and edited, and (hopefully someday) bricks debricked.
Get it here: Nooter 0.2.
Up-to-date directions at http://nookdevs.com/NookColor_Rooting
Changes
0.1
first release
0.2
replaced composite CDC USB device with RNDIS. This should "just work" under most XP and later Windows
add ext2tools, dosfstools, util-linux for manual flash disk reformatting
Thanks to [mbm] for the root procedure, kernel config, and not sleeping; KCHASE731 for dissecting his NC for vital clues about the hardware config; and the rest of #nookdevs
If we've already rooted with Nooter v.01, and are using windows, is there any harm in rooting again with Nooter v.02?
Oh, and THANKS!
jasoraso said:
If we've already rooted with Nooter v.01, and are using windows, is there any harm in rooting again with Nooter v.02?
Oh, and THANKS!
Click to expand...
Click to collapse
Both versions will write the file to turn on adb every time they boot, but will only patch the ramdisk if it hasn't been done already. There's no difference in the rooting procedure from 0.1 and 0.2, just the tools for people wanting to get a shell outside of Android.
Not working for me
I must have done something wrong, but my NC just boots like normal, it never boots off the microSD card.
I am using Ubuntu Maverik.
I install the SD card while the nook is powered down and then I plug the USB cable to the computer, which automatically starts the NC, but it just boots in the OS like normal. after the NC boots, it will connect the sd card and flash memory like normal, and show the nooter02 sd contents.
Any suggestions?
EDIT: OK, figured it out, I used mmcblk0p1, instread of mmcblk0
Yesss !delivered
Hi
I receive my NC today !. It's great nooter 0.2 is awesome for two points :
it gives root access and ...
It demonstrates that the overclock is possible, because the uImage/u-boot force the clock to 1Ghz and it's working well
Code:
cat cpuinfo_cur_freq
1000000
About 997 bogomips
Cheers
Occip
Woot! Thanks for the revised tool to root from the Windoze world!
I'll have to give this a try when I get home...
So, if we used Nooter0.2, we are running 1Ghz?
occip said:
It demonstrates that the overclock is possible, because the uImage/u-boot force the clock to 1Ghz and it's working well
Click to expand...
Click to collapse
I imagine that only while running off SDCard
occip said:
Hi
I receive my NC today !. It's great nooter 0.2 is awesome for two points :
it gives root access and ...
It demonstrates that the overclock is possible, because the uImage/u-boot force the clock to 1Ghz and it's working well
Code:
cat cpuinfo_cur_freq
1000000
About 997 bogomips
Cheers
Occip
Click to expand...
Click to collapse
Heh, I never even checked! I used the config for the Zoom3 sdk (OMAP3630 like the DX) for x-loader and u-boot and I guess that's where that gets set.
We should have BN's sources for both soon enough, and it will be a very easy change to the stock bootloader to get 1GHz in Android.
ryoojin83 said:
I must have done something wrong, but my NC just boots like normal, it never boots off the microSD card.
I am using Ubuntu Maverik.
I install the SD card while the nook is powered down and then I plug the USB cable to the computer, which automatically starts the NC, but it just boots in the OS like normal. after the NC boots, it will connect the sd card and flash memory like normal, and show the nooter02 sd contents.
Any suggestions?
EDIT: OK, figured it out, I used mmcblk0p1, instread of mmcblk0
Click to expand...
Click to collapse
Um, help? I'm following the directions and I'm familiar with the mmcblk0 from my multiple phones, but I don't understand how that applies here. I'm using Maverick and get the same thing you do...it just boots normally.
Thanks
weiln12 said:
Um, help? I'm following the directions and I'm familiar with the mmcblk0 from my multiple phones, but I don't understand how that applies here. I'm using Maverick and get the same thing you do...it just boots normally.
Thanks
Click to expand...
Click to collapse
are you using a dedicated microsd reader or your phone or the nook itself to flash the image?
I just confirmed that nooter broke the NC's in-store features, such as read any book for up to 1 hour per day. Any chance of looking into this?
daveknights said:
I just confirmed that nooter broke the NC's in-store features, such as read any book for up to 1 hour per day. Any chance of looking into this?
Click to expand...
Click to collapse
All Nooter does is set a flag to turn on adbd and turn off the root lockdown flag. Either the BN app checks that root or adbd aren't enabled, or the ramdisk is signed and the process of unpacking, changing the security flag, and repacking the ramdisk screws up the signature. You could try copying the ramdisk.img from partition 3 over uRamdisk in partition 1, which would unroot but leave adbd running, and see if that re-enables the store features. Of course, you'd have no root, but if you just want basic apps then that might be enough.
I am using windows vista 32 sp2 and could not get root. help question. In the windows USB ADB instructions with the copy and paste part
;B & N Nook Color ; %SingleAdbInterface% = USB_Install, USB\VID_2080&PID_0002 %CompositeAdbInterface% = USB_Install, USB\VID_2080&PID_0002&MI_01
why do i get
this bottom part stuck to it
Read more: http://nookdevs.com/NookColor_USB_ADB#ixzz17adJ0qwv
Under Creative Commons License: Attribution Non-Commercial Share Alike
along with my copy and paste. anyone know where this last line come from.
Also about this part of the process with rooting
Once the devices show up, wait another 30 seconds while the script makes the changes to enable ADB. (ADB will be available after you reboot into Android)
is it 30 sec or 5 min's I have read hear on the XDA boards it is 5 mins to enable ADB. It is hard to tell cause nothing really happens.
Once rooted is there a firmware (#) difference i can check to see if it worked
This is the 2nd time i am posting this as before i got no answers
I've been trying this for up to 2 mins, both with Windows and Mac and I'm kinda sure the root isn't working for me. I just received the NC, so is it possible B&N updated over the weekend in response to the news?
Is there a way to check version of firmware/bootloader/etc?
EDIT: Ok got it working amazingly. I uninstalled the driver (Android ADB Interface) and checked the delete files option. When I rescanned it found it and installed the correct drivers under W7.
pokey9000, is the uRamdisk.bak file on partition 1 something nooter created or is that a how the stock NC comes? and if nooter creates it, would deleting uRamdisk and renaming uRamdisk.bak to uRamdisk unroot the NC just like copying the ramdisk.img file over from partition 3?
do you have any documentation on what else (specific files) nooter modifies?
would it be possible to unroot a NC without doing a factory reset?
ruze said:
EDIT: Ok got it working amazingly. I uninstalled the driver (Android ADB Interface) and checked the delete files option. When I rescanned it found it and installed the correct drivers under W7.
Click to expand...
Click to collapse
I had to do the same exact procedure to get a Win7 machine to talk with my NC over ADB.
jsmith.nook said:
pokey9000, is the uRamdisk.bak file on partition 1 something nooter created or is that a how the stock NC comes? and if nooter creates it, would deleting uRamdisk and renaming uRamdisk.bak to uRamdisk unroot the NC just like copying the ramdisk.img file over from partition 3?
do you have any documentation on what else (specific files) nooter modifies?
would it be possible to unroot a NC without doing a factory reset?
Click to expand...
Click to collapse
Nooter modifies the default.prop to allow root in uRamdisk after copying the original to uRamdisk.bak. Then it creates /data/property/persist.service.adb.enable to turn on adb. So copying uRamdisk.bak to uRamdisk and deleting /data/property/persist.service.adb.enable will put things back to normal. But you'll still have app specific content in /data/app, /data/dalvik.cache, /data/data, anything you do to /system, etc.
pokey9000 said:
Nooter modifies the default.prop to allow root in uRamdisk after copying the original to uRamdisk.bak. Then it creates /data/property/persist.service.adb.enable to turn on adb.
Click to expand...
Click to collapse
Would modifying default.prop to enable adb there, rather than create the property file, also work? Or does that have no effect?
Thank you for this great tool. Your work is greatly appreciated.
This is a new ipad2 imitation, i'm interested but need community support please:
it is on HSN, these are the specs :
Specs
Model #:
i10-h
Operating System:
Google Android 2.2
Processor:
Samsung A8 Cortex 1GHz
Display:
9.7"; 1024 x 768 resolution; 4:3 aspect ratio
Dynamic RAM:
512MB DDR
Memory Storage:
4GB built-in
Memory Expansion:
microSD card slot
Wireless Networking:
802.11b/g/n
Bluetooth 2.1
Ports:
(1) HDMI output
(2) USB 2.0
(1) 3.5mm earphone jack
Battery:
Lithium-ion 6800 mAh
Measurements:
Approx. 9.64"L x 7.55"W x 0.47"H
Weight:
Approx. 0.8 lb.
Listing:
UL
Country of Origin:
China
I can not vouch for other methods but I have rooted this tablet with SuperOneClick ver. 2.1.1. If you leave "Exploit" on "auto" and click "root" you will be pleasantly surprised. Took me two tries, but if you turn on usb debugging in settings and leave the screen timeout on 30min your golden. Happy rooting.... I'm also uploading a google apps zip file. I unzipped it and installed all the files in the corresponding places to get a working Android Market. I used Android Commander to move the files & install apk's. *NOTE* You need to install the apps in the "/sysem/app" folder in this order...
1. GoogleServicesFramework.apk
2. OneTimeInitializer.apk
3. SetupWizard.apk
4. Talk.apk
5. Vending.apk
6. Gmail.apk
7. Maps.apk
After... Restart, Connect to wifi, and launch Market. You will be prompted to sign in to google. Then you will see Market License blah blah blah...
*Use the attached zip not the one at the following link* But use this link as a guide if you need it... http://forum.xda-developers.com/showthread.php?t=827209
Have fun.
*Zip File Link*
http://www.mediafire.com/download/d85zjeb9b43j9do/gapps-hdpi-20100817-Impression_10.zip
****THIS METHOD WORKED FOR MY IMPRESSION 10 MODEL # i10-50, but UNTESTED by me on other models****
***EDIT*** Sorry guys... you were unlucky because I forgot something crucial.... THE DARN ADB DRIVER.... You will need to go into the device manager and right click the "Android" device with exclamation mark & click update driver. Search for the driver and point the installer to this folder should work on 32 & 64 bit if my edits are correct... Tested on 64 bit Windows 7.
DRIVER
http://www.mediafire.com/?lzrwj65da0c5c63
Also when you install those "/system/app" files above use Android Commanders "Installer" and install them one at a time in the order above. AND AFTER YOU RESTART USE LAUNCHER AND NOT SETUP OR YOU CAN'T ACTIVATE YOUR WIFI.
I tried both methods,
SuperOneClick and Gingerbreak both did not work.
The table is running android 2.3.1.
wonkastocks said:
I tried both methods,
SuperOneClick and Gingerbreak both did not work.
The table is running android 2.3.1.
Click to expand...
Click to collapse
Do you have usb debugging turned on, and did you use the latest version of SuperOneClick. For me it stalled when my screen timeout was to short and locked me out of my tablet when the screen cut off. Second time around it looked like it was going to fail, stalled and then prompted me to ok the install of busybox... etc etc. I am also running android 2.3.1 and it worked for me. Just have to keep trying till you get it.
PIC's...
http://img148.imageshack.us/img148/5624/44983779.jpg
http://img225.imageshack.us/img225/3019/68779107.jpg
http://img32.imageshack.us/img32/7827/42856323.jpg
http://img198.imageshack.us/img198/3149/44013908.jpg
Remember i'm running a i10-50, but the pictures speak for themselves. SU, Market...
Fails
I've also tried this on my husband's Impression 10 - same model i10-50. Can you give some details of how you rooted? What programs did you use besides Android Commander and SuperOneClick 2.2.1? Any help would be appreciated.
i just got an impression 10 as well. i10-50 model with android 2.3.1. im interested in more in depth info on rooting it as well. i tried updating firmware from the page it gives from the box. instructions to download the system.img file from the impression site. but i am not sure how long it takes? when i loaded the file on sd card and restarted (power+vol-) one time it stayed on the blue screen with the white status bar for like over a half hour. i thought it froze and restarted. when i tried it another few times the blue screen disapeared and i got a screen full of multi colored lines all down it. when i reseted.you could still faintly see those lines even when its running normaly. its faintly in background and you can see it more on certain pages or folders u open. my first tablet and i wish there was more info on it. any clue what im doing wrong?
dude i do customer suport forthis tablet, as u may know by now............it sux
leader Impression I10-50 firmware update
In order for the firmware update to be completed successfully, u need to first format your sd card via sd card reader or your tablet as follows:
Plug in the tablet via usb to your PC or load your card reader with sd card
Then select and left click whatever removable disk drive your tablet shows up
Select format and make sure the file system is set at FAT32
Select start, your sd card should begin formating.
Once complete, then u follow the 13 steps, but since you have already started step 1-13, just press your -volume and power buttons at the same time (steps 11 and 12 again) and it should update your tab. Be sure to do it twice as far as the volume and power button go so the update completes successfully.
I cannot seem to get this thing to root....tried the above with the external sd unmounted and then removed. Followed the instruction on the gtab post. All I can see is the external sd card. It did install superuser. Without the sd it gets stuck at Step 6.
It took awhile....but switched to EZ File Explorer. And I was able to see the internal sd and copy the files Then was able to install the market! Life is good!
edit: nevermind
StephenMC said:
It took awhile....but switched to EZ File Explorer. And I was able to see the internal sd and copy the files Then was able to install the market! Life is good!
Click to expand...
Click to collapse
Do you know if the root is reversible in case you need to put it back to the factory default? Would installing the image file on the Impression website reset the tablet back to stock firmware?
TC93 said:
Do you know if the root is reversible in case you need to put it back to the factory default? Would installing the image file on the Impression website reset the tablet back to stock firmware?
Click to expand...
Click to collapse
Yes, SuperOneClick has a unroot option as well.
StephenMC said:
Yes, SuperOneClick has a unroot option as well.
Click to expand...
Click to collapse
Thanks for the reply. About that file program you used, the only one I can find with a similar name is "ES File explorer". Is that the one you used?
I can't get it to copy the files over in the system directory, it acts like its write protected and fails the copy. I must be doing something wrong.
Oops yes ES File Explorer...
Need go to settings.... Open menu, choose Settings Check Root explorer and mount file system...
I'll probably just give up on this. This still isn't wanting to write/copy the files. This is the whole reason I returned my Nook Color before because of the hassle it takes to do this.
edit: it copies a few files, but then some files it says it failed.. like the "maps.apk" file.
Had a few apk's not move as well. I think map was one of them. Just followed the install order and did those from the external sd.....all worked out.
StephenMC said:
Had a few apk's not move as well. I think map was one of them. Just followed the install order and did those from the external sd.....all worked out.
Click to expand...
Click to collapse
Thank you for your help. I finally got it working, I spent hours on this.
But I decided to try that original posts recommendation of using the program "Android Commander". I had to search to find it, but its a Windows program that makes it much easier to copy files over to the root directory. (although I had to change a setting it in so that it auto closes the log window after it copies, otherwise you can't close the log window, or do anything else until its closed).
I wasn't able to copy the maps with that either though, it gave the error that there wasn't enough space. But it seems to be working fine now.
Impression i10-50
I bought the i10-50 and actually love the tablet. With google market installed (update firmware first), I have full access to the market and no problems installing apps. The only con about the tab is no gps. To install the market, I only downloaded the google apps file and installed the apks in the correct order and that was it. No need to root. I am truly enjoying this tab now.
I have a GTab that was running Calkulin + Clemsyn Combo Overclock at 1.5 ghz V8 on the 1.2 branch fine for a couple months now, then something happened today. Woke up to find there was no sound coming from it (I'd left an Anti-mosquito app running all night), so I tried to play a couple music files. Seemed to get frozen instead of playing, so I restarted. That's when it went into a boot loop from 3 birds to the first splash screen of the loaded ROM.
Attempted to do a backup via CWM, and it failed on /data. Tried a data wipe/reset, then reflashing the ROM and finally NVFlash. Still goes into a bootloop. Repartitioning and mounting doesn't do anything; ADB doesn't see the device at all in CWM or APX; /data cannot be mounted and /sdcard mounts only when a card is inserted (doesn't see the internal space) but still doesn't mount USB storage and says: "E:Unable to write to ums lunfile (No such file or directory)"; drive shows in Win7, but is inaccessible;
As mentioned, APX mode and NVFlash along with CWM works fine. And I can mount /cache and /system fine. I've gotten to Code Double Red here and now I'm draining the battery for the next step (really don't want to pull any screws). Also tried the fix here, but it seems that's just for CM7, which I'll probably try flashing some time.
I'm going to return to the 1.1 branch and try a couple ROMs there, but I have a really slow connection and it's taking a while to get nvflash 1.1.
Did a quick search of the forum and didn't find anything quite similar. Obvious question is, has anyone ever experienced this before? What are some other steps I can take to fix this? Is there a way to backup the internal SD before I probably have to wipe it?
Connect the USB cable to the tablet, then boot it into CWM, and run this command on your PC:
Code:
C:\SOME\PATH> [B]adb shell dmesg > dmesg.txt[/B]
Post that dmesg.txt file here. We'll see what's wrong.
Connected the charger long enough to run the command, but all I get is "error: device not found". As I'd said, ADB doesn't detect the tablet, even though Windows knows when it's connected and disconnected. Is there anything that I can flash to get me a terminal? That's the only way I can think of to get that command run and hopefully direct the output to my SD. Thanks.
I now have a completely dead battery. Wondering what to do next since it's supposed to have been hard reset now. Not seeing anything different after booting; same boot loop even though I just flashed a ROM again.
rajeevvp said:
Connect the USB cable to the tablet, then boot it into CWM, and run this command on your PC:
Code:
C:\SOME\PATH> [B]adb shell dmesg > dmesg.txt[/B]
Post that dmesg.txt file here. We'll see what's wrong.
Click to expand...
Click to collapse
I had seen this thread before where you were helping someone last year. Wish I'd read further to see that he eventually got the same problem I now have. I'm currently working my way through everything. First I need to get ADB running though, so I'm working on that now. Think I may be needing that partition swap trick, but we'll see...
Having issues getting the right USB drivers installed for ADB on Windows 7 64 bit. Using instructions here. But each time I uninstall the device, as soon as I plug in the tablet, it installs the default drivers. Using both Device manager and USBDeview. Updating and other options are also disabled when there is nothing installed. Considering to do a direct registry hack of the device info if I can, and hopefully not break anything important.
Try using Linux.
I finally got ADB working on my system and did some experimenting. Seems there's definitely something wrong with my internal SD according to the dmesg output. Luckily I have a SD which I used in my SG3, and it is already properly partitioned, so I'll try using that. Tried making a fstab file in /etc (mtdblock3) but I got "Magic Value Mismatch" error, so I NVFlashed to return it to how it was. I'm currently researching how to create update files, because it seems that's the only way I can get the SDs swapped. Any guidance is still welcomed. Thanks alot.
Skele Drew said:
Seems there's definitely something wrong with my internal SD according to the dmesg output.
Click to expand...
Click to collapse
Yeah. There are clear error messages relating to the internal SD card. You can either return the tablet and get a replacement, or, use my SD card device swapping technique to use the external SD in place of the non-working internal one.
Tried making a fstab file in /etc (mtdblock3) but I got "Magic Value Mismatch" error, so I NVFlashed to return it to how it was. I'm currently researching how to create update files, because it seems that's the only way I can get the SDs swapped.
Click to expand...
Click to collapse
If you use my files, you don't need to modify anything manually. What're you trying to change, BTW?
I can definitely use some help there. Where are the files? I tried modifying the custom ROM I use by adding a custom fstab and vold.fstab to /etc, an init script to init.d and replacing the /data mounting command with:
Code:
ui_print("Copying Data Files");
run_program("/sbin/mount", "-t", "ext3", "/dev/block/mmcblk2p2", "/data");
ui_print("Mount information:");
ui_print(run_program("/sbin/mount"));
Not sure what you're attempting to do here...
If you just want to use an external SD card in place of your non-working internal one, then all you have to do is a) flash either one of the CWM zip files and then b) flash the SD card swapping zip file right after you install the ROM of your choice. And, if you tell me which ROM you plan to install, I can look inside it and tell you if my scripts will work with that ROM.
If you can read shell/awk scripts, you can look inside the zip files to see what they do and how they do it.
rajeevvp said:
Not sure what you're attempting to do here...
If you just want to use an external SD card in place of your non-working internal one, then all you have to do is a) flash either one of the CWM zip files and then b) flash the SD card swapping zip file right after you install the ROM of your choice. And, if you tell me which ROM you plan to install, I can look inside it and tell you if my scripts will work with that ROM.
If you can read shell/awk scripts, you can look inside the zip files to see what they do and how they do it.
Click to expand...
Click to collapse
I was trying to make a swap script myself, but it's not working. /system dir gets corrupted. I'm using Clemsyn_Caulkinver8final2, a Froyo ROM.
Look at my scripts. If you have any questions, just ask.
Where are the scripts? That's what I've been asking...
EDIT: If this is what you use, then all should be ok. Let you know the result when I'm again online. Thanks alot for your help!
That's what I was talking about. I modified the device-swapping script today to fix-up an additional shell script, /system/etc/inandop.sh, on the various Clemsyn/Beasty ROMs (incl. yours), so use the newer zip file.
rajeevvp said:
That's what I was talking about. I modified the device-swapping script today to fix-up an additional shell script, /system/etc/inandop.sh, on the various Clemsyn/Beasty ROMs (incl. yours), so use the newer zip file.
Click to expand...
Click to collapse
Appears it still doesn't work. However, now instead of having a boot loop, it's just stuck at the splash screen after the 3 birds. I'm going to try combining your script and the ROM to see if I can get better results. I'm also going to try inserting some log/debug messages where I can.
Skele Drew said:
Appears it still doesn't work. However, now instead of having a boot loop, it's just stuck at the splash screen after the 3 birds. I'm going to try combining your script and the ROM to see if I can get better results. I'm also going to try inserting some log/debug messages where I can.
Click to expand...
Click to collapse
THANK YOU RAJEEV!!!!!!!
Today I got the time to work on my tablet again, since I just restarted college and it's been a bit hectic. Decided to try CM7 since when I looked into your script I saw direct management for it, so I NV'd back to 1.1 (I didn't know what branch CM7 was on, but flashing CM7 on 1.2 gave an error and aborted). The first time I tried the CM7, it got to the CM7 logo, then was there for a while until I only had a black screen. The only way I knew the tablet was still on was because ADB was still connected. Then I flashed your script and VOILA! everything started great. So now I have my tablet again for my classes .
I am planning to still run a few tests to see if I can somehow recover/fix the internal SD, so I downloaded your set of e2fsprogs. Think I'll make a flashable file for the entire package.
Again, thanks for all your assistance. It's much appreciated. I really didn't have that much time anymore to work on it myself too. I will continue to learn more as time goes on though, and I hope one day I'll become a guru like you .
Skele Drew said:
Decided to try CM7 since when I looked into your script I saw direct management for it, so I NV'd back to 1.1 (I didn't know what branch CM7 was on, but flashing CM7 on 1.2 gave an error and aborted).
Click to expand...
Click to collapse
The official CM7 is, right now, only for 1.1. However, since you can replace just the kernel and instantly make a 1.2 ROM, you'll have to look at the kernel messages to tell which bootloader version you have (Note: this is only for pershoot kernels).
The first time I tried the CM7, it got to the CM7 logo, then was there for a while until I only had a black screen. The only way I knew the tablet was still on was because ADB was still connected.
Click to expand...
Click to collapse
This is to be expected. When a ROM first runs, it writes a whole bunch of stuff into /data; but, your internal SD card is messed up, so every write would've ended up with the kernel retrying for quite a bit and then failing.
You should've flashed the ROM and immediately afterwards my script to fix-up the mount points on the ROM--ie. before the first boot.
I am planning to still run a few tests to see if I can somehow recover/fix the internal SD, so I downloaded your set of e2fsprogs. Think I'll make a flashable file for the entire package.
Click to expand...
Click to collapse
I doubt if you can "fix" your internal SD card error using any of the e2fsprogs--it looks like a card-controller error rather than a media error. You have one of the non-standard internal SD cards which has caused problems for some other users as well.
Ok. I do have a few issues I hope I can get some help on. For one, flash player doesn't work, and that's something very important. All my browsers direct me to get flashplayer. It worked pretty well in my previous ROM, so it may be an issue with CM7, but I haven't seen any similar issues on their site.
Also, the tablet is less responsive now, though I think this has to do with the /data partition being on external SD, though it's a class 6 card.
Sent from my GTablet using Tapatalk
Did you partition the external SD card correctly into 2 partitions (the first as VFAT and the second as ext3) before you installed CM7? I'm not sure what steps from my post you followed and what steps you skipped: you mentioned you were planning to modify the scripts/ROM, right?
It is also possible that my script is not doing the right thing on CM7 since it doesn't touch the vold.fstab on it. Get me the output of a mount command in CM7, and these files:
Code:
/system/etc/vold.fstab
/system/build.prop
Also make sure that you, or the ROM provider, haven't enabled the SD card switching in Settings > Cyanogenmod settings.
The SD I'm using was in a SG3 using this ROM, so I think it's correctly partitioned. I've accessed the partitions before and the correct names are associated with the contents. I only followed steps 1 & 4. The option to use removable for apps and media is disabled.
build.prop
mount.txt
vold.fstab
Hello,
Here is the short story.
I have Samsung Galaxy ACE which is rooted.
Till y'day I was using CM9 Beta 8 ICS 4.0.4 and it was working well.
I installed CM10 JB for Galaxy Ace alpha1 from "hxxp://maclaw.pl/?page_id=180#comment-3642"
Now the problem is, JB doesn't have File Manager installed and I need to install TB to revert my backups.
Due to some unknown reason I am not able to access internet on my device either through GPRS or 3G connection.
I am desperately looking for a way to access my SDCARD wherein I have all my apk's which I can install however, without File Manager I am not sure how to install an apk.
I did some google search and came across topics about installing apk using Android SDK etc.. however I would not want to work on SDK as I feel its bit tedious job for me.
I also tried Android Injector however that didnt work even if I have enabled USB debugging Mode for adb + apps.
Now, I am hoping that, I can use the Terminal Emulator which is preinstalledo n my phone to install apk present on my sdcard.
However, I am not sure how to do that, It would be really appreciated if anyone can suggest the steps to install apk present on my sdcard from Terminal Emulator available on my phone.
Here are some of the screen captures
http://imageshack.us/photo/my-images/855/screenshot2012072418240.png/
http://imageshack.us/photo/my-images/52/screenshot2012072418234.png/
http://imageshack.us/photo/my-images/822/screenshot2012072418230.png/
Thanks
Never mind...
I managed to install Astro File Manager apk from Terminal Emulator.
For those who are interested, here is what I had done.
Previously, I wasn't able to browse sdcard contents from TE,
I rebooted my phone once, fired up TE again
~Android$ su
Allow root access for TE
~Android# cd sdcard
~Android# ls ( Contents of SD card are listed ) I had copied astrofm.apk on root of SDCARD
~Android# pm install astrofm.apk
Success !
Thanks
P.S. This thread can be closed.
@@
hsotnas said:
Never mind...
I managed to install Astro File Manager apk from Terminal Emulator.
For those who are interested, here is what I had done.
Previously, I wasn't able to browse sdcard contents from TE,
I rebooted my phone once, fired up TE again
~Android$ su
Allow root access for TE
~Android# cd sdcard
~Android# ls ( Contents of SD card are listed ) I had copied astrofm.apk on root of SDCARD
~Android# pm install astrofm.apk
Success !
Thanks
P.S. This thread can be closed.
Click to expand...
Click to collapse
Awesome guide !!!! , thanks bro !! :good::fingers-crossed:
Thank you for the guide
it works. thank you
works, thanks
hsotnas said:
Never mind...
I managed to install Astro File Manager apk from Terminal Emulator.
For those who are interested, here is what I had done.
Previously, I wasn't able to browse sdcard contents from TE,
I rebooted my phone once, fired up TE again
~Android$ su
Allow root access for TE
~Android# cd sdcard
~Android# ls ( Contents of SD card are listed ) I had copied astrofm.apk on root of SDCARD
~Android# pm install astrofm.apk
Success !
Thanks
P.S. This thread can be closed.
Click to expand...
Click to collapse
I very much appreciate the quick tutorial!
However, with that being said, I am having an issue trying to install my .apk onto my Motorola Xoom (Rooted running CM10.1) through the use of Terminal Emulator. I first tried installing the .apk from my File Manager and just clicking on the icon, and clicking Install, like one would think one should be able to do. When that method failed, multiple times(kept saying "insufficient storage, please delete files through app manager") which by the way, I know for a fact I have 15.8GB of storage left on my Xoom, so this should not be the issue. I then decided to try and install through Terminal Emulator. Now one would think it would be about the same as using adb commands on a Computer, which it somewhat is I guess you could say. So I go to T.E. and type the commands to get Super User access, then cd sdcard to go into the directory, then cd download because this is where my file is located, then I type pm install ****.apk.
I get a line of command that says: a) pkg: ****.apk and then b) Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE], and then the command line just goes back to my download folder directory.
I've had this issue before on my Galaxy S3, but can't remember how I ended up resolving the issue. Think I did a factory data reset/wipe, which I don't want to have to do to my Xoom. So any assistance would be much appreciated. I do understand that your device was a Galaxy ACE, but I wouldn't think it would matter as to what the device is, since it is the same install method/command for any Android device essentially. Hope someone can help out. If not, I may have to post in another Device Thread (Motorola Stingray Xoom I would assume).
Many thanks in advance, and I will click the Thank You, if any responses come through.
Really appreciate for the guide man
Sent from my LG-P700 using xda app-developers app
Thanks for the reply... short, to the point, and it works.
DannyShane said:
I very much appreciate the quick tutorial!
However, with that being said, I am having an issue trying to install my .apk onto my Motorola Xoom (Rooted running CM10.1) through the use of Terminal Emulator. I first tried installing the .apk from my File Manager and just clicking on the icon, and clicking Install, like one would think one should be able to do. When that method failed, multiple times(kept saying "insufficient storage, please delete files through app manager") which by the way, I know for a fact I have 15.8GB of storage left on my Xoom, so this should not be the issue. I then decided to try and install through Terminal Emulator. Now one would think it would be about the same as using adb commands on a Computer, which it somewhat is I guess you could say. So I go to T.E. and type the commands to get Super User access, then cd sdcard to go into the directory, then cd download because this is where my file is located, then I type pm install ****.apk.
I get a line of command that says: a) pkg: ****.apk and then b) Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE], and then the command line just goes back to my download folder directory.
I've had this issue before on my Galaxy S3, but can't remember how I ended up resolving the issue. Think I did a factory data reset/wipe, which I don't want to have to do to my Xoom. So any assistance would be much appreciated. I do understand that your device was a Galaxy ACE, but I wouldn't think it would matter as to what the device is, since it is the same install method/command for any Android device essentially. Hope someone can help out. If not, I may have to post in another Device Thread (Motorola Stingray Xoom I would assume).
Many thanks in advance, and I will click the Thank You, if any responses come through.
Click to expand...
Click to collapse
Hi DannyShane,
Not sure if this is still relevant and you are around here, since it's been a very long time and I stopped using Android
I am not an Android geek but here are my 2 cents...
You need to keep .apk file on the root of the SD CARD instead of a folder. IIRC, I had the same exact error which you had mentioned, I was trying to install .apk which was placed in a folder and it didnt work., then I had to move the .apk file to root and it worked flawlessly.
Extremely sorry for the very late response though. I use my secondary e-mail for this forum and missed replies on this thread.
@ All others who have replied, I am glad that, my little finding helped you guys.
Cheers :angel:
I have a few things to add to hsotnas answer. The insufficent space error seems to be a very generic error on android that can have various causes. Maybe there is something like this in the android source code:
PHP:
try{
installApk();
} catch (Exception ex){
output("Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE]");
}
If you understand what I mean
I had this error myself a few days ago and for me it was caused by some left over files in the /data/app-lib directory. It was a self-developed application and I added a library to this directory manually. As I uninstalled the application, it wasn't removed and the reinstall failed with the above mentioned error. So make sure the directories /data/data/app.package.name/ and /data/app-lib/app.package.name/ are empty.
I tried this, to install the play store apk. But I get the error INSTALL_FAILED_INVALID_URI. What is this error refering to?
PSV_Supporter said:
I tried this, to install the play store apk. But I get the error INSTALL_FAILED_INVALID_URI. What is this error refering to?
Click to expand...
Click to collapse
Me too same thing happens when I try to install 3.apk
the command used is "pm install apps/*.apk"
Mine are backups of play store
Thankyou for this tutorial... IT WORKS.. Can't believe it.. You made my day. Thankyou :good:
I'm trying to recover an old tablet and need to install a file manager... the touch screen inst working so I thought terminal would do the job... but .APK's dont show when I go to the root of the SD card and type 'ls'
An ideas?
Thanks it works
failed on me ..