Database Users

Q&A for Linux/Android

Ok thought might as well start this off myself seen as people keep talking about it, lets have a Q&A thread instead of bashing up the original thread so it can be used just for news and updates.
Does Android work on my HD2?
yes and no, at the moment it boots, no touch-screen driver so that's it so if you try this is what you get
microang has made up some pretty nice versions that dont blue screen check them out here
http://forum.xda-developers.com/showthread.php?p=7032400#post7032400
Can I flash Android?
NO NO NO, it will run from Haret, it will not be a ROM, (yet maybe one day)
Can I boot Ubuntu?
yes you can, but touch-screen issues again,
UPDATE there now is a TS image to use
you would be better off using a mouse and keyboard via a powered usb hub.
Startup txt
Who can I donate to?
Dcordes' PayPal
Cotulla's PayPal
Netripper's PayPal
Links for fatsal-ubuntuX1-20100225 running on you're HD2, there is 3 but i cant find them all post if you have a working link.
http://hotfile.com/dl/51297725/02a8295/fatsal-ubuntuX1-20100225.7z.
thanks to yumm_007 for packaging this up
This Blog site & this Video is as FAKE as it get don't bother with it.
http://alltechdownloads.blogspot.com/
http://www.youtube.com/watch?v=BujRY_q53JI
http://androidforhd2.tk/
This is the IRC channel please dont go and post loads of crap there either
http://webchat.freenode.net/
use channel #htc-linux
Netrippers channel log
http://irclog.netripper.com/?chan=htc-linux&msgonly=0
__________________
Ok I have to go out i will add more and see about a ubuntu Tut to get it running when i get back, please post in here from now so we don't block up the original thread so we can leave that for news and development,
the 2 images are of how i have my folders set up and the other pic of proof it boots
I take no credit for the hard work gone in to this development just tried top clear the thread a bit but that didnt work did it lol, ALL CREDIT GOES TO
Dcordes'
Cotulla's
Netripper's

What I found was that the ubuntu folder must be inside another folder which is on sd root. So tree wise its setup as...
1) SD root
2) Folder (containing the ext2 and the ubuntu folder which contains the haret files)
If you do it like you did, it hangs, I had the same problem. If you do it the way I explained, it gets to the actual linux kernel (tux) but kp's when the modules are to be loaded.
Click to expand...
Click to collapse
Ok, this solves the cpu coherency freeze, what next? what is that we're doing wrong and can't boot the image?
thanks in advance.

artn3r said:
Yes, but i downloaded it over the rapidshare mirror.
what i did:
-copied everything to the sd root
-replaced zimage with the kernel that boots on hd2 (from irc log)
-merged the default.txt and startup.txt of the ubuntu build with the irc-log-build
start haret.exe
Click to expand...
Click to collapse
have you tried this yet???

hi guys,
i currently don`t understand what exactly i have to do to run the HaRET. i`ve downloaded the "fatsal-ubuntuX1-20100225". there are haret and so on and a folder named ubuntu. when i extract it to my sdcard an boot haret i got a stop error "can not access SDroot".
what is wrong? maybe i am stupid?

braumeister said:
hi guys,
i currently don`t understand what exactly i have to do to run the HaRET. i`ve downloaded the "fatsal-ubuntuX1-20100225". there are haret and so on and a folder named ubuntu. when i extract it to my sdcard an boot haret i got a stop error "can not access SDroot".
what is wrong? maybe i am stupid?
Click to expand...
Click to collapse
I got it working on touch diamond start of the year, just downloading for leo now
this was posted
ayilm1 said:
What I found was that the ubuntu folder must be inside another folder which is on sd root. So tree wise its setup as...
1) SD root
2) Folder (containing the ext2 and the ubuntu folder which contains the haret files)
Click to expand...
Click to collapse

Demon_man said:
have you tried this yet???
Click to expand...
Click to collapse
That's the first of it, but go grab artn3r's pre packed ubuntu from the official Android/Linux thread a few posts after the one you quoted I think, and set it up folder wise as...
1) SD root
2) "fatsal-ubuntuX1-20100225" (containing the ext2 and THEN the ubuntu folder which contains the haret files)
That's what I did to make it work but as stated in the official thread, it hangs at the module loader

the name doesn`t matter?

well I'm downloading now, i have to pop out but i will be be back in 45 mins, and ill play try n get it running, if you get it going in the meantime let us no

braumeister said:
the name doesn`t matter?
Click to expand...
Click to collapse
Not sure TBH. Something interesting happens if renamed to something other than the original name though. The coherency test hangs but if reverted, it runs up to the tux.

Just upload ur files if you got it runing

Great idea man!
Demon_man said:
Ok thought might as well start this off myself seen as people keep talking about it, lets have a Q&A thread instead of bashing up the original thread so it can be used just for news and updates.
Click to expand...
Click to collapse
Nice idea man! Glad to see that lot of people is running in the correct way to help this development!
Cheers from Portugal

Ok, SOME progress. Mine HALF succeeded in rebooting after deleting then recopying the files over (making changes of course). It got past the rebooting in 5 seconds hang and now has actually made an attempt to restart. (yay!) But all I got was it declaring it was about to reboot and the Kernel version number. i.e. 2.6.32.9

ayilm1 said:
Not sure TBH. Something interesting happens if renamed to something other than the original name though. The coherency test hangs but if reverted, it runs up to the tux.
Click to expand...
Click to collapse
no it doesn`t matter where the files are or in which folder or how it is called.
tried this:
1) haret, ubuntu folder and co in the root of the sd card
2) new folder called "fatsal-ubuntuX1-20100225" with alle the files and ubuntu folder in there
3) renamed the folder "fatsal-ubuntuX1-20100225" to anything else
does not matter...the result is all the same.
haret booting, init the panel and stops after a line "welcome to kovsky aka xperia - ubuntu" with an error
mount: mounting /dev/block/mmcblk0p1 on /sdcard failed - invalid argument
failed to mount the sd card. cannot continue
/bin/sh: can`t access tty: job control turned off
/ # _ (blinking cursor)
BUT...hardware controls response

braumeister said:
no it doesn`t matter where the files are or in which folder or how it is called.
tried this:
1) haret, ubuntu folder and co in the root of the sd card
2) new folder called "fatsal-ubuntuX1-20100225" with alle the files and ubuntu folder in there
3) renamed the folder "fatsal-ubuntuX1-20100225" to anything else
does not matter...the result is all the same.
haret booting, init the panel and stops after a line "welcome to kovsky aka xperia - ubuntu" with an error
mount: mounting /dev/block/mmcblk0p1 on /sdcard failed - invalid argument
failed to mount the sd card. cannot continue
/bin/sh: can`t access tty: job control turned off
/ # _ (blinking cursor)
BUT...hardware controls response
Click to expand...
Click to collapse
Ok maybe it was just mine acting up then.

have you any partitions on sd card? one or more? if so on which parti do you have the files?

@braumeister
mount: mounting /dev/block/mmcblk0p1 on /sdcard failed - invalid argument
failed to mount the sd card. cannot continue
/bin/sh: can`t access tty: job control turned off
/ # _ (blinking cursor)
Interesting, mine gets none of that. In fact, the loadmodule shell extension is the only think stopping mine from progressing. Oh and umm. It also attempts to switch to rootfs.

braumeister said:
have you any partitions on sd card? one or more? if so on which parti do you have the files?
Click to expand...
Click to collapse
No other partitions, hmmm. But in case this helps, its still got winmo stuff on it, so not formatted to ext2. Doubt that'd make a difference though as the SD's format shouldn't effect the format of the ubuntu image.

transferring files now to my sd card
BOOTED

Hi,
Touchscreen working fine for me.. thanks to cotulla
At bootup it will stuck shortly and show your TS type.. the ones with 2A are the lucky
Image here:
http://cotulla.pp.ru/leo/ImageTS.rar
Do you mind uploading ur setup for unbuntu image?
Thanks you

chris5932 said:
Hi,
Touchscreen working fine for me.. thanks to cotulla
At bootup it will stuck shortly and show your TS type.. the ones with 2A are the lucky
Image here:
http://cotulla.pp.ru/leo/ImageTS.rar
Do you mind uploading ur setup for unbuntu image?
Thanks you
Click to expand...
Click to collapse
do you mean me?? and how you got touchscreen working lol

The Viewsonic G Tablet Super Thread (w/Market, Gmail, and Maps!)

I've tried this twice already with a factory reset in between each try, and it's worked both times!
Attached is a bunch of files you will need to make this work.
Download the attached Zip file and extrat the contents to your desktop
Mount your G and upload the "G Tablet" folder to your G's internal SD card
Using AndRootFile or any other file manager that supports root access, mount as R/W, and copy the contents of G Tablet\permissions to System\etc\permissions.
Copy the contents of G Tablet\framework to System\Framework
Copy the contents of G Tablet\lib to System\lib
Copy all the APK's found inside G Tablet\APK into your system\app folder.
Install them in this order:
GoogleServicesFramework.apk
OneTimeInitializer.apk
SetupWizard.apk
Talk.apk
Vending.apk
Gmail.apk
Maps.apk
Make sure you remount it as R/O when you're done!
Restart your G, Connect to Wifi, then launch Market.
Follow the standard Google Account setup procedure and enjoy your newly installed Market.
PROOF THAT IT WORKS (the guide might be broken at some point though, see explanation below): http://www.youtube.com/watch?v=3dm2Kax8RQM
Someone please test this and let me know if you have any problems. Factory resetting doesn't delete any files I might have moved into the system folder so I might be missing something in this guide.
Feel free to donate to my beer fund if this helped you
Copying the following over from my thread over at Overclock.net (best computer enthusiast community, ever!)
Guides:
Setting Up ADB:
The ADB drivers do not recognize the Tegra hardware by default. You need to modify the USB inf file in order for it to recognize it and install the proper hardware.
Go to the usb_driver folder inside your Android SDK folder
Open up android_winusb.inf
Add the following under [Google.NTx86] and save (or if you prefer, download my pre-modified android_winusb.inf attached to the bottom of this post, and replace your existing android_winusb.inf with mine).
Code:
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
If you are running a 64 bit version of Windows, you need to add that code to the [Google.NTamd64] section as well.
Next, open a command prompt and type
Code:
echo 0x955 >> "%USERPROFILE%\.android\adb_usb.ini"
On your G, go to Settings -> Applications -> Development, and check "USB Debugging"
Plug in your USB cable, it will tell you that some drivers were not installed. That's okay! Point it to your usb_driver folder and it'll install the proper drivers.
Make sure ADB is working by opening a command prompt, navigating to your android sdk "tools" folder, and typing
Code:
adb devices
You should see a bunch of numbers if everything is set up correctly.
Click to expand...
Click to collapse
Rooting:
You need to have ADB fully working before proceeding. The easiest way to root is by using CLShortFuse's SuperOneClick. If you can spare the money, consider donating a buck or two to his beer fund
Connect your G and make sure USB debugging is enabled/ADB is working.
Extract the contents of SuperOneClickv1.5.2-ShortFuse.zip to a folder of your choice.
Run SuperOneClick.exe and click on Root. Wait for the process to finish, and you're rooted! Easy as pie.
Click to expand...
Click to collapse
Installing Launcher Pro/ADW:
It's actually really easy.
Download the Launcher Pro APK from here: http://www.launcherpro.com/apk/LauncherPro-0.8.1.1.apk
Connect your G and move the Launcher APK over to your Tablet's internal/external SD card.
Using whatever file manager you prefer (on your G), execute the Launcher Pro APK and install it.
Upon completion, hit the Home button and choose LauncherPro as your default launcher.
Reboot and feel the speed!
Click to expand...
Click to collapse
Fixes:
Wifi Fix:
If your Wifi "errors" upon enabling, try one of the following methods
Method 1:
Reboot. Seriously, it fixes the problem a large portion of the time.
Click to expand...
Click to collapse
Method 2:
Download Wefi from here: http://www.wefi.com/download/android/
Install the APK on your G.
Run WeFi, hit the menu button (button between back and home), and hit Settings
Make sure Automatic Startup is checked. Click on "Wi-Fi on WeFi start" and choose "Always Turn On"
Restart your G and pray.
Click to expand...
Click to collapse
Method 3: Master Reset (you will lose all your apps)
Go to settings -> Security and do a Factory Wipe.
This works only SOMETIMES, but is not a guaranteed fix, so only use this as a last ditch resort
Click to expand...
Click to collapse

nicely done, sir

Awesome job. OCN FTW

Fantastic.. worked like a champ!
Thanks!

Where did you find the USB drivers to mount the device?

Can i also include the contacts, mail, and calendar gapps?

mattmanion said:
Where did you find the USB drivers to mount the device?
Click to expand...
Click to collapse
By mounting I mean connect the USB cable, then under the Notification Icon, Tap "USB Connected, Select to copy files to/from your computer"

insight3fl said:
Can i also include the contacts, mail, and calendar gapps?
Click to expand...
Click to collapse
Go for it, let us know what you find

r34p3rex said:
By mounting I mean connect the USB cable, then under the Notification Icon, Tap "USB Connected, Select to copy files to/from your computer"
Click to expand...
Click to collapse
Do you know if there is a tutorial out there for installing the Root Explorer or Astro file manager on this thing? Sorry, I'm a newbie.

VERY NICE WORK!
FYI I reposted this on the slatedroid.com forum gave you credit and linked back to this thread. If you don't want it on there let me know and I will take it down.

by the way.. All I did to get this working was install the apk's in order and reboot. I do have a problem .. I can't find some apps on the market.. for example winamp doesnt show up..just the winamp 3rd party app.
Anyone else?

Does anyone know why live wallpapers aren't available?

tri0xinn said:
by the way.. All I did to get this working was install the apk's in order and reboot. I do have a problem .. I can't find some apps on the market.. for example winamp doesnt show up..just the winamp 3rd party app.
Anyone else?
Click to expand...
Click to collapse
I will look into that. The most likely reason is the lack of a unique Android ID.

does the regular nullsoft winamp show up for you?

great work man. Just saw the video.
I'm still trying to get adb access. First thing I did was modded the usb files but not the 64bit cuz I didn't see it. Guess I didn't look hard enough. Modded the 32bit one and added the Nvidia tegra info. Then tried adb and the oneclickroot and it didn't work. I then went in and found the amd64 area and added the lines to that portion of the usb.ini file also.
I don't have adb working to root. I'm on Win 7 64bit. any idea's. Then I'll try your guide.

xguntherc said:
great work man. Just saw the video.
I'm still trying to get adb access. First thing I did was modded the usb files but not the 64bit cuz I didn't see it. Guess I didn't look hard enough. Modded the 32bit one and added the Nvidia tegra info. Then tried adb and the oneclickroot and it didn't work. I then went in and found the amd64 area and added the lines to that portion of the usb.ini file also.
I don't have adb working to root. I'm on Win 7 64bit. any idea's. Then I'll try your guide.
Click to expand...
Click to collapse
Gunth you want me to help over Teamviewer?

My files are in place, but the APK files are not "installing" on boot and the tablet sets up normaly and gmail app is not there. I have tried going back in and changing R/O in root explorer, but still not go.. what am I missing? Can these files be pushed to the tablet via adb or do you have to use root explorer? Seems I had the same problem when I did this with my Odroid T.. I tried root explorer but ended up pushing with adb.
Thanks for your work on this
hmmm... it says "install"... I need to launch them from explorer and actualy "install" them? then reboot?

insight3fl said:
My files are in place, but the APK files are not "installing" on boot and the tablet sets up normaly and gmail app is not there. I have tried going back in and changing R/O in root explorer, but still not go.. what am I missing? Can these files be pushed to the tablet via adb or do you have to use root explorer? Seems I had the same problem when I did this with my Odroid T.. I tried root explorer but ended up pushing with adb.
Thanks for your work on this
hmmm... it says "install"... I need to launch them from explorer and actualy "install" them? then reboot?
Click to expand...
Click to collapse
You need to run each APK manually through Root Explorer (or any package installer of your choice). Placing them there does not do anything

xguntherc said:
great work man. Just saw the video.
I'm still trying to get adb access. First thing I did was modded the usb files but not the 64bit cuz I didn't see it. Guess I didn't look hard enough. Modded the 32bit one and added the Nvidia tegra info. Then tried adb and the oneclickroot and it didn't work. I then went in and found the amd64 area and added the lines to that portion of the usb.ini file also.
I don't have adb working to root. I'm on Win 7 64bit. any idea's. Then I'll try your guide.
Click to expand...
Click to collapse
I'm having the same issue Gunth so when you get it working let me know

Just finished up installing the apks. Got a problem though. Now my home and search buttons don't work. Also lost Airplane mode when powering off.
*EDIT* Just watched your video. I don't think that's a finicky button. I think this hack causes the problem.
*EDIT 2* Just did a reset. Home button and search work again. So, it's got to be the hack.
Doc

[SCRIPT] Windows One Click Root Method [3/26/11]

HTC Thunderbolt Windows One Click Root
This is a simple batch file that will guide you in rooting your device.
It is pretty easy to follow along but please take your time and read everything. It has only been tested a few times so please report any errors or issues you find.
Huge thanks to NetForce-TX on IRC for testing along with helping, I owe you!
Also thanks to Jcase for guidance
TeamAndIRC and Captainkrtek (Me) are NOT responsible for any bricks, fires, or damaged/broken hardware due to this process
If you wish to read the batch files contents either open it with notepad or check the pastebin
Instructions are included in the file when running it along with where to get the necessary files.
Prerequisites:
Drivers Installed & Working
SDK Installed with ADB
Exploits.zip with contents extracted to your ADB dir
PG05IMG.zip
Downgrade RUU
A Thunderbolt running 605.6 or 605.9 Firmware
You can download the OneClickRoot here
I will update this from time to time if needed, If you have issues with the batch file please PM me on XDA or find me on irc.andirc.net #Thunderbolt.
I will not reply to your PM if you want me to help you root your phone!
UPDATE: If SU acts up (IE: Force closes) flash this via CWM

Reserved for Linux version

Wow, looks easy! But I'm glad I did it through ADB. Nice job!

pinhead875 said:
Wow, looks easy! But I'm glad I did it through ADB. Nice job!
Click to expand...
Click to collapse
Thanks! It is pretty simple, only a few things you have to do manually (no possible workaround) such as flashing from the bootloader.

Anyone try this yet?
sent using Tapatalk on the TB.

egeorgia said:
Anyone try this yet?
sent using Tapatalk on the TB.
Click to expand...
Click to collapse
Already a few people have tested it, all successes

so we set the phone to debug mode and the usb mode to just charging?
i was going to to the other root ;set up my ADB earlier but chickened out... i already have the files downloaded

Cg006 said:
so we set the phone to debug mode and the usb mode to just charging?
i was going to to the ot her root and set up my abd earlier but chickened out... i already have the files downloaded
Click to expand...
Click to collapse
Yeah exactly, just debug and charging, until you have to copy over the roms then you will set the USB mode to mount SD

I did the long method but I missed the step to get s-off. Can I still use the one click root method sk I can obtain s-off?

alphatectz said:
I did the long method but I missed the step to get s-off. Can I still use the one click root method sk I can obtain s-off?
Click to expand...
Click to collapse
Yes you can, but I reccomend unrooting whatever you have done so far using this http://forum.xda-developers.com/showthread.php?t=1009423

Captainkrtek said:
Yes you can, but I reccomend unrooting whatever you have done so far using this http://forum.xda-developers.com/showthread.php?t=1009423
Click to expand...
Click to collapse
Ok, I'll unroot and use the one click method. Thx

can we get a poll maybe to see success rate

Can we get a Step by Step Instruction Guide? it would be nice for us beginners

ok so after i choose my path where my android sdk platform tools folder is i get
Pushing files via ADB...
This process may take some time, if it takes longer than 30 seconds
Make sure the drivers are install and USB debugging is on.
cannot stat 'psneuter': No such file or directory
cannot stat 'busybox': No such file or directory
cannot stat 'misc.img': No such file or directory
Unable to chmod /data/local/psneuter: No such file or directory
Unable to chmod /data/local/busybox: No such file or directory
so what did i do wrong? i get my serial number when i get type adb devices....

b33zy682 said:
ok so after i choose my path where my android sdk platform tools folder is i get
Pushing files via ADB...
This process may take some time, if it takes longer than 30 seconds
Make sure the drivers are install and USB debugging is on.
cannot stat 'psneuter': No such file or directory
cannot stat 'busybox': No such file or directory
cannot stat 'misc.img': No such file or directory
Unable to chmod /data/local/psneuter: No such file or directory
Unable to chmod /data/local/busybox: No such file or directory
so what did i do wrong? i get my serial number when i get type adb devices....
Click to expand...
Click to collapse
You need to put the contents of exploits.zip in the same directory ADB is in

ok what in that zip needs to go where?

Phone Has been Succesfully Rooted.
Did most of the steps while doing some WoW Raiding. lol
Thank you so much.... now.. should i flash a new rom on this baby?

b33zy682 said:
ok what in that zip needs to go where?
Click to expand...
Click to collapse
take everything that is in exploits.zip and move it to your android sdk directory specifically the location of adb.exe (will either be in platform-tools or tools) as for the two RUUs, they can be anywhere but you will have to move them at one point to your SD card. That is about it

Cg006 said:
Phone Has been Succesfully Rooted.
Did most of the steps while doing some WoW Raiding. lol
Thank you so much.... now.. should i flash a new rom on this baby?
Click to expand...
Click to collapse
Yes you should

Cg006 said:
Phone Has been Succesfully Rooted.
Did most of the steps while doing some WoW Raiding. lol
Thank you so much.... now.. should i flash a new rom on this baby?
Click to expand...
Click to collapse
damn right! lol

[Q] Inconsistancies accessing Device Storage from windows

I've just noticed this today and wondered if anyone else has see this?
There seems to be an inconsistancy between the tablet and the view of the Device Storage when connected to windows via micro usb port.
For instance. I connect the tablet to windows with micro usb cable and I view files under "Device Storage" which is the contents of the internal sdcard from /mnt/sdcard.
I also start up an adb shell and cd to the /mnt/sdcard directory. As expected, both show the same files. And if I create a file or folder in the windows exporer view, the file or folder shows up in the adb shell view as well.. great..
However, If I create a file or folder using the adb shell, it does not get reflected to the windows explorer view (until the tablet is rebooted). Likewise, if I create file in the explorer view and then delete it in adb shell, it stays around in the explorer view. Also, if I delete a file in the explorer view, it stays around in the adb shell view.
Anyone know what's going on here and why it doesn't stay in sync? Is the windows explorer view using some kind of cache view?
Thanks

Euclid's Brother said:
I've just noticed this today and wondered if anyone else has see this?
There seems to be an inconsistancy between the tablet and the view of the Device Storage when connected to windows via micro usb port.
For instance. I connect the tablet to windows with micro usb cable and I view files under "Device Storage" which is the contents of the internal sdcard from /mnt/sdcard.
I also start up an adb shell and cd to the /mnt/sdcard directory. As expected, both show the same files. And if I create a file or folder in the windows exporer view, the file or folder shows up in the adb shell view as well.. great..
However, If I create a file or folder using the adb shell, it does not get reflected to the windows explorer view (until the tablet is rebooted). Likewise, if I create file in the explorer view and then delete it in adb shell, it stays around in the explorer view. Also, if I delete a file in the explorer view, it stays around in the adb shell view.
Anyone know what's going on here and why it doesn't stay in sync? Is the windows explorer view using some kind of cache view?
Thanks
Click to expand...
Click to collapse
I have had 100% of the same thing happen on my A500. I often find that my files are in the wrong location and I still cannot get the external SD to read from the computer.
I have another problem concerning these issues maybe you could help with. I may have either flashed an update without the proper files to go before it; or I have have forgotton to wipe something. Nonetheless, my A500 wouldn't boot. When I did some research, I went to this site {http://forum.ppcgeeks.com/showthread.php?p=2127076#post2127076} because it seemed in my eyes to have pertinent information. I got the update.zip to install and my A500 booted again! However, I could not get to stop two because my insternal SD card was wiped somehow and when I get to the main screen, do the circular unlock, the launcer, and many other programs repeatedly force close, so much so that I cannot do ANYTHING. How would you approach this, and is there a way for me to get into CWM. I have a recent nandroid backup that what 100% functional, and I would hope the MD5 sums would still match....
Any help/advice is greatly appreciated!

ibrooks.. try the instruction in post#1 of thread http://forum.xda-developers.com/showthread.php?t=1132760
That will wipe the data, which I believe is causing all your force closes.
Once that is done, then you can root with gingerbreak.
After that, you can continue the instructions from that thread you referenced. But instead, I would suggest flashing the official 3.1 from http://forum.xda-developers.com/showthread.php?t=1159443
Edit: The official 3.1 is not pre-rooted, you'll need to do the 3.1 root app if you want root access back.

Euclid's Brother said:
ibrooks.. try the instruction in post#1 of thread http://forum.xda-developers.com/showthread.php?t=1132760
That will wipe the data, which I believe is causing all your force closes.
Once that is done, then you can root with gingerbreak.
After that, you can continue the instructions from that thread you referenced. But instead, I would suggest flashing the official 3.1 that's pre-rooted from http://forum.xda-developers.com/showthread.php?t=1159443
Click to expand...
Click to collapse
uh... it's not pre-root...it's stock and will need "iconiaroot" to root
http://forum.xda-developers.com/showpost.php?p=15456928&postcount=5

UnicornKaz said:
uh... it's not pre-root...it's stock and will need "iconiaroot" to root
http://forum.xda-developers.com/showpost.php?p=15456928&postcount=5
Click to expand...
Click to collapse
Thanks.. I guess I was thinking about the leaked version that was released with pre-root. i've updated my post.

I've had that problem happen when I was trying to downgrade from the leaked 3.1. I was getting frustrating trying to flash different ROMs and the about kept showing the same version over and over again. Finally I realised that the files were just being copied to the device storage instead of the SD card. Taking the card out and copying the files directly did the trick.
Sent from my A500 using XDA Premium App

Great! Nice to know that I'm not cRaZy! I was having quite a time last night trying to copy files back and forth from the tablet, only to have them not show up where I knew they were in Windows explorer when connected via usb,.

Free 50 GB Box Account HELP

I followed the instructions according to mdalacu
Working great, and all i had to do was to change only 2 lines in buid.prop using ES File explorer with 2 options activated: Root Explorer and Mount File System.
1. Be sure that you have root
2. Install ES File explorer and Options and check this: Root Explorer and Mount File System
3. Navigate to /system. Long press on buid.prop , open as text.
4. Edit the file by modifying this lines:
ro.product.model=GT-N7000
ro.product.brand=samsung
into
ro.product.manufacturer=LGE
ro.product.model=VS910 4G
5. reboot
6. install from market box (box.net)
7. Create the account. A confirmation message will appear that you have 50 GB capacity.
8. Again from EFS File Explorer navigate to /system. Check that you have a file named build.prop.bak and if so, delete buid.prop. Rename build.prop.bak into build.prop. Now you can disable from options : "Root Explorer" and "Mount File System"
9. Reboot
10. Enjoy your amizing phone
Note: I had done this on KL7 with stock kernel.
Was able to create a bunch of accounts, then deleted the build.prop file and renamed the build.prop.bak back to build.prop, rebooted the phone, and I get to the Samsung Galaxy Note N7000 screen, then it goes black. I cannot boot up the device now.
Any suggestions?

yeahmon said:
4. Edit the file by modifying this lines:
ro.product.model=GT-N7000
ro.product.brand=samsung
into
ro.product.manufacturer=LGE
ro.product.model=VS910 4G
Click to expand...
Click to collapse
I don't think you are supposed to change "brand" to "manufacturer". For me, there was already a "ro.product.manufacturer" value (edit: of course, I also changed the "model" value) and I just changed that.
However, I don't see how this could have caused your problem. Are you sure you renamed the backup file "build.prop" correctly? Maybe accidentally left a symbol there, or deleted one too many?

bnapalm said:
However, I don't see how this could have caused your problem. Are you sure you renamed the backup file "build.prop" correctly? Maybe accidentally left a symbol there, or deleted one too many?
Click to expand...
Click to collapse
Sounds like OP deleted the build.prop and perhaps the rename failed and didn't notice, so now they have no build.prop file whatsoever.
--
Are you able to access the device using a cable via adb (is USB debugging enabled on your phone)?
I know nothing about rooting the Note just yet, though if it's the same setup as G1/Nexus/Desire (I guess it would be) you should be able to get into recovery then use adb at a command line to push a new build.prop file to /system which should allow your device to boot.

bnapalm said:
I don't think you are supposed to change "brand" to "manufacturer". For me, there was already a "ro.product.manufacturer" value (edit: of course, I also changed the "model" value) and I just changed that.
However, I don't see how this could have caused your problem. Are you sure you renamed the backup file "build.prop" correctly? Maybe accidentally left a symbol there, or deleted one too many?
Click to expand...
Click to collapse
It worked, and I was able to reboot back into the Note with these settings.
jayshah said:
Sounds like OP deleted the build.prop and perhaps the rename failed and didn't notice, so now they have no build.prop file whatsoever.
--
Are you able to access the device using a cable via adb (is USB debugging enabled on your phone)?
I know nothing about rooting the Note just yet, though if it's the same setup as G1/Nexus/Desire (I guess it would be) you should be able to get into recovery then use adb at a command line to push a new build.prop file to /system which should allow your device to boot.
Click to expand...
Click to collapse
I think you're right about losing the build.prop file. Fortunately, I backed it up. I am trying to access the device now. I have no GUI on the Note. I am hoping it is just a blank screen and the device is still functioning in the background. I'll be back momentarily with an answer to accessing it.

ok...I can access the Note's file system. However, when I try to copy the backup build.prop file into the system directory via Android Commander, it says I need root access to do this permission.
The Note IS rooted. I don't get it.

This appears to be a problem with Android Commander. There are threads about this same problem, but rather than the software creator place a link to his FAQ that he ridicules everyone for not reading, he lambasts them instead. Thats a real good way to get a donation.
Anybody got any other suggestions for a root file explorer, preferably for Mac, but PC will work too.

be careful, backup buid.prop and restore it after creating Box account.

amincom said:
be careful, backup buid.prop and restore it after creating Box account.
Click to expand...
Click to collapse

I am having no luck finding a way to get root access from a computer.

deleted post
user error

The tumbleweeds are big around here

There's an app for that
Without having to edit files and without root.
http://www.androidguys.com/2011/12/28/get-50gb-of-free-box-cloud-storage-without-rooting/

But is there an app to copy my file over from my computer?

amincom said:
be careful, backup buid.prop and restore it after creating Box account.
Click to expand...
Click to collapse
vcespon said:
Without having to edit files and without root.
http://www.androidguys.com/2011/12/28/get-50gb-of-free-box-cloud-storage-without-rooting/
Click to expand...
Click to collapse
Please read the OP before posting.
--
The fact that you are using Android Commander implies you have adb access, this is good.
Here's what I would do to fix your problem, it definitely isn't the only way, but it will work.
#1: Get ADB installed on your PC/Mac/Linux
#2: Open a command line and run
Code:
adb devices
as a test, you should get output that one device is connected via cable, if you don't abort here, nothing else will work
#3: run
Code:
adb remount
This will make your /system writeable
#3: I'll put this as a windows instruction because I don't know the Mac filesystem, but it's almost identical
Code:
adb push C:\build.prop /system/
This will push C:\build.prop (please put your backup copy here) into /system/ of your Note. If you're on a mac, you will need to find another place to put it, e.g. if it's /users/bob/build.prop the command just becomes
Code:
adb push /users/bob/build.prop /system/
I hope this helps
Edit: Paste a copy of output here if it doesn't work so I can help debug

I was onto this earlier but a Command line gets me this:
'adb' is not recognized as an internal or external command, operable program or batch file.

yeahmon said:
I was onto this earlier but a Command line gets me this:
'adb' is not recognized as an internal or external command, operable program or batch file.
Click to expand...
Click to collapse
You'll need to download/install adb first.

jayshah said:
You'll need to download/install adb first.
Click to expand...
Click to collapse
standby...

its taking forever to install SDK

This is a lost cause.
No matter what I do, I get the same errors. Anything I try to do to remedy the issue only opens another door to hell.
I should have stuck with Dropbox.

yeahmon said:
This is a lost cause.
No matter what I do, I get the same errors. Anything I try to do to remedy the issue only opens another door to hell.
Click to expand...
Click to collapse
You're really going to have to paste the error messages here for any of us to help you further
Alternatively, can't you just reflash your current ROM on top?