Database Info

How To Partition SD Card With Ubuntu For Dummies

How To Partition SD Card With Ubuntu For Dummies.
This guide will help people with partitioning their sd card using Ubuntu (Linux Live CD). You can make your Fat32, ext2/3, and linux_swap partitions. The software is free and you do not need to install anything. These instructions should be easy to understand but if anyone still has any questions feel free to ask.
What is needed:
* A computer
* Ubuntu
* Blank CD-R
* Software to burn a .iso image
* G1 or a card reader
1. Go to www.ubuntu.com and download Ubuntu 9.04.
2. Once downloaded you will have a .iso file so you will need a burning software capable of burning .iso files. I use nero but you can use whatever you like. There is other free software you can download to burn the file like www.freeisoburner.com.
3. Now that ubuntu is burned to a disc we can boot it up. Place the disc into the cd tray and turn off the computer.
4. Turn on the computer. When the computer starts up the very first loading screen where you see Dell/Compaq/HP/etc. (the same screen where you would hit f8 to go into safe mode) hit f12 to go into boot mode. Once your boot menu appears select your cd drive. Some computers will boot the cd right away when hitting f12.
5. When the cd boots up it will ask you to select your language. After that it will ask you if you want to try Ubuntu without installing. Hit enter on that option so you won't install anything. Ubuntu will then load.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
6. Put your sd card in the reader or connect your G1 to the computer and mount it.
7. At the top of the screen click System > Administrator > Partitioner Editor. And then Gparted will open up.
8. Click the drop down box to select your sd card. (NOTE - make sure to select your card and not your computer hard drive. Easy way to tell is if you have a 8 gig card choose the one that is 8 gigs. Common Sense)
9. Your sd card will now be displayed. If you already had it partitioned you will see the partitions. Or if it is a brand new card it will say unallocated.
10. If you already have a partition or partitions on it right click each partition and choose unmount. Do that for every partition until you see the keys gone beside the partitions.
11. Right click every partition and choose delete until all partitions are gone and it says unallocated.
12. Right click unallocated and choose new.
13. A box will appear to create your first partition. Create your Fat32 partition first. Click the drop down box and click Fat32. Choose the size you want to make it (I just subtract 1000 from the number to save for my ext partition). And leave it as primary. Now click apply.
14. You will now see your Fat32 partition and unallocated.
14. Right click unallocated again and choose new.
15. This time we will set up our ext partition. Click the drop down box and choose ext2 or ext3. You can leave the size alone and make sure it is also on primary. Click apply.
16. If you are wanting to you can create the linux_swap partition to but it is not necessary.
17. You are now back at the box with Fat32, ext2/3, linux_swap and unallocated. Now click apply. A confirmation box will appear and click apply again.
18. It will format your card and then you are done.
19. You can now click the power icon in the upper right hand corner to turn off Ubuntu and restart into windows.

Great guide.
This works great off the liveCD but when I install Ubuntu, Gparted doesn't install with it. How come?

Pinesal said:
Great guide.
This works great off the liveCD but when I install Ubuntu, Gparted doesn't install with it. How come?
Click to expand...
Click to collapse
I don't know why, does it give you the partiton editor under administrator or does it not show up at all.

supremeteam256 said:
I don't know why, does it give you the partiton editor under administrator or does it not show up at all.
Click to expand...
Click to collapse
It doesn't show up at all.

Pinesal said:
It doesn't show up at all.
Click to expand...
Click to collapse
What version of ubuntu are you using?

I made a guide just like this a few hours ago but decided not to post it as someone had probably already made one Oh well, yours is a little more detailed.
Just remember, there's no need for a wasted CD. You can make a live usb with unetbootin
Btw, I'm really curious why everyone is making massive ext partitions! I would have thought 2/300mb would be enough for most people. I don't know nay apps bigger than 6mb, and most are < 1mb...

supremeteam256 said:
What version of ubuntu are you using?
Click to expand...
Click to collapse
version 8.10...

Pinesal said:
version 8.10...
Click to expand...
Click to collapse
Try 9.04 and see if that makes a difference.

everytime i try and boot from cd(second one made) it loads up fine but then it goes to a screen with a bunch of flashing colors. I am booting without installing. Any suggestions

not to sure why its doing this

c_low29 said:
everytime i try and boot from cd(second one made) it loads up fine but then it goes to a screen with a bunch of flashing colors. I am booting without installing. Any suggestions
Click to expand...
Click to collapse
It did that to me one time when I burned it to a dvd instead of a cd. Does the desktop load up or how far does it get into loading.

nice thread: this would have been really useful yesterday.. i spent hours trying to figure it... and finally got it then found this....never the less thank you

ok here is a question I have Ubuntu on a VMWare virtual computer and also a Ubuntu 9 x64 (newest version as of yesterday) Live CD.
Now when I plug my phone or sdcard with reader it WILL show both the Fat32 AND the ext2 partions while running it on the virtual machine thru VMWare.
BUT
When I use that Live CD it will NOT mount/show the Ext2 partiton only the Fat32. Even though it doesnt show the ext2 mounted I can STILL edit it thru the gparted program. Which is nice to be able to modify the partitions BUT I cant access any files on the ext2 partition
sooo why is it that I cannot access my ext2 partition from the live CD regardless of if its thru the phone USB or through the card reader, but can from the virtual machine?

@pinesal et al
In 8.10 Appilications > Add/Remove > Search: gparted > install Gnome Partition Editor
Ubuntu for some reason doesnt install GParted when istalling the os(maybe they think you won't need it after the initial partitioning to install ubuntu)
Good Luck.
Another Good choice for Live CD or USB is Crunchbang, it's fast, really small OS and it has live stats for your pc integrated into the desktop.

supremeteam256 said:
It did that to me one time when I burned it to a dvd instead of a cd. Does the desktop load up or how far does it get into loading.
Click to expand...
Click to collapse
i made sure to install it to a cd not dvd and it does this to me.

c_low29 said:
i made sure to install it to a cd not dvd and it does this to me.
Click to expand...
Click to collapse
How far does it load and what do you see? What are the specs on your computer? I seen some people had your problem due to there graphics card. When you run the lived cd you can hit f4 and try to run it in a lower resolution. What kind of graphics card you have?

Really great Post haha
could have been doing with this post a week ago haha
never the less
well done poster and thank you

Pinesal said:
It doesn't show up at all.
Click to expand...
Click to collapse
type this in terminal
$ sudo apt-get install gparted
This will download and install the gparted program for you

You should use aptitude instead of apt-get open a command prompt and type :
sudo aptitude install gparted

supremeteam256 said:
How far does it load and what do you see? What are the specs on your computer? I seen some people had your problem due to there graphics card. When you run the lived cd you can hit f4 and try to run it in a lower resolution. What kind of graphics card you have?
Click to expand...
Click to collapse
yah my graphics card can defeinetly handle it( NeVidia GForce 7300 LE)
it shows me a bunch of tiny little green and blue squares

SoupKit (again)...When you're fed up with trying to get ADB to connect in Windows

The SoupKit
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is SoupKit? At it's heart, SoupKit is for those who are tired of messing around with Windows and are ready to do try something that works. It was created to be "sort of" modular in that after the ADB installer has been installed, other Linux scripts can be installed and run from the command line by just typing the name of the script and without worrying about changing directories or dealing with permissions. It's intended to make the transition from Windows to Linux for Android a little bit easier.
How does it work?
The SoupKit ADB Installer --- FOR ALL KINDLE FIRES
This puts everything where it needs to be, installs any necessary dependencies, installs drivers, configures Linux to run adb and fastboot commands, puts the SoupKit in your $PATH and cleans up after itself, all while taking a fraction of the space needed for the Android SDK. What this means for you is, you will be able open any terminal window and start entering adb or fastboot commands immediately. There's no need to change directories, add sudo commands or certain operators that are confusing to command line newbies ( ./ ). You can enter commands just as you see them in tutorials. No more worrying about “ADB Offline”, “Status Unknown” or “List of devices attached ????????????????”. This alone can make a huge difference for anyone having Kindle Fire problems that can't be fixed in Windows or those who are overwhelmed by the technicalities of configuring Linux for Android.
What you need:
First, you need Linux. Don't worry, it's not as bad as you may think.
Luckily, all Linux distros are free to download and install on your computer. It can also be booted from a USB flash drive so you don't have to wipe out your current OS (although you probably should anyway). You can use a VM, but the only VM that I've found that can detect the Kindle Fire in fastboot mode is Parallels. Vmware won't cut it, and VirtualBox sure as hell won't cut it so don't waste your time with them if you ever need to do anything in fastboot (if you're bricked, you need fastboot).
Probably the best method to get Linux running for a new user is by setting up a Linux LiveUSB.
I'm not going to teach you how to set up a Linux LiveUSB, but there are plenty of FREE programs out there that will not only create a Linux LiveUSB for you, but will download your choice of distro as well, and all you need is a USB flash drive (preferably 8GB or larger). A Google search of “Linux LiveUSB” will offer plenty of choices, although, PendriveLinux seems to be a favorite among most. Just be sure to add plenty of “persistence” (1 or more gigabytes) or you will lose everything every time you reboot. And the better quality of flash drive you can use, the better it will be in the long run. Some flash drives just don't do well and can cause some file system corruption over time (not something you want to be dealing with while you're having Kindle Fire problems).
You'll also have to figure out how to boot your computer from a USB. Check your computer's BIOS manufacturer website for instructions on how to do this.
If you're using a LiveUSB, there is no root/sudo password, just hit enter.
Do not use a USB 3.0 port
Once you have Linux installed and booted, you need to make sure your Internet is working. It may take some configuration on your part but it is necessary for the SoupKit to install properly. Luckily, once you have an Internet connection in Linux, the hard part is over.
Don't put the SoupKit.zip on the USB drive before creating the LiveUSB. Instead, use the web browser to navigate to this page and download it once you have Linux running and your Internet connected. Once it's downloaded, you'll likely find it in your Downloads folder.
SoupKit has been tested extensively on all the latest versions of Ubuntu and Mint, but it hasn't really been tested on anything outside of that. Try other distros if you will, but be warned.
To install:
Right-click the “SoupKit.zip”, select “Extract here” open the SoupKit folder and follow the instructions in the README.
Credits:
Don't worry. I didn't forget about you guys. I'll finish this when I have time. In the meantime, you know who you are, and thank you.
Is that all?
NOPE. What SoupKit would be complete without a little something to go with it? SEE POST #2

Due to recent updates, I've decided to remove the option to install Hashcode's 2nd bootloader. There are too many areas where things can go wrong so I think it would be best to let the user follow the small handful of instructions in the 2nd bootloader thread to get it done. IMO, it is not worth the risk to rely on the user to make sure a downgraded stock bootloader is installed before running the script. Plus I think using a script toinstall the downgraded bootloader gives users a false sense of safety in what is potentially very dangerous to do.​ ​
ROOT PLUS for 2nd Generation Kindle Fires
That's right. This works for ALL 2nd generation Kindle Fires
What does it do?
The screenshot above should answer that question pretty quickly.
What do you need to know?
Since Hashcode's bootloader hack is device specific, you must download the version for your device. Each one has the exact same script but the stack, boot and recovery images are different for each particular device. You must have the SoupKit installed for this to work properly. It installs in the same way as the SoupKit; unzip, double click, run in terminal, blah blah.
Make sure you have ADB enabled under “Security” in the settings.
Anything else?
At any point after installation, if you need to run the utility again, just type "rootplus" in the terminal.
What's next?
I have a few more things in store for you guys and they will all be made for the SoupKit. As packages are installed, just type the name of the package in any terminal to launch them at any point (hence "modular"). Everything will be easy to install, easy to launch, and new user friendly.
Don't be skerrd. Move out of your comfort zone a little and give Linux and SoupKit a try. I'm sure you won't be disappointed.
Credits:
* Bin4ry - of course, for providing the root exploit
* prokennexusa and his team - for testing this out on all of the second generation devices
* Thepooch - for extensive testing and always being there to lend a hand
Downloads:
SoupKit - http://d-h.st/PbX
RootPlus for all Kindle Fires - http://d-h.st/jOe

Changelog:
04-23-2013 - Update (RootPlus)
* Removed option to install Hashcode's 2nd bootloader, for safety reasons. There is absolutely nothing wrong with Hashcode's 2nd bootloader. The risk lies in recent updates from Amazon.
03-19-2013 - Update + bugfix (RootPlus)
* Fixed issue with 2nd bootloader install - everything works as it should now
* Added timestamp to saved partitions. Gives users the ability to save more than one set of partition images
03-18-2013 - Update: (RootPlus)
* Changed how 2nd bootloader is installed for compatibility with the KF2
* Added ability to update custom recovery. No need to update the script every time a new recovery is released.
* Added ability to choose partition images to be installed if more than one set exist in the BACKUP folder
* More intuitive restore of saved partition images - will hopefully prevent any chance of user error
03-16-2013 - Bugfix: (RootPlus)
* Fixed issue with permissions on the rootplus script
03-10-2013 - Update: (RootPlus)
* Added extra safety measures, including MD5 check on 2nd bootloader install
02-23-2013 - Initial release

Will try thanks
Sent from my KFTT using xda premium

You, sir, are a wizard... Thanks for putting this together!
Sent from Hell™

Sorry, but I don't see a link for KFHD 7" package. Did I miss somthing?
Rootplus KF 7 is for Kindle Fire HD 7"?
Droid DNA

I'm stuck on installing the bootloader option 6. It back up the kfhd7 then go to installing stacks. There I get a line that is "/system/etc/install-recovery.sh' - No such file or directory" the kindle reboots. And that's were it stuck saying...< waiting for device >

zuke66 said:
I'm stuck on installing the bootloader option 6. It back up the kfhd7 then go to installing stacks. There I get a line that is "/system/etc/install-recovery.sh' - No such file or directory" the kindle reboots. And that's were it stuck saying...< waiting for device >
Click to expand...
Click to collapse
For now, use the restore option to restore the partitions that were saved when you chose the option to install the bootloader hack and TWRP.
In the meantime, I need to know what software version you're using, and whether or not you have edited your build.prop. Also, after you restore your system, use adb to access the shell and list the contents of your /system/etc directory and post it here.
Code:
adb shell su -c "ls /system/etc"

When I do a restore it reboots then stop at "waiting for device"
Sent from my SPH-L710 using xda app-developers app

zuke66 said:
When I do a restore it reboots then stop at "waiting for device"
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Okay, a few questions...
Do you have normal use of the device? Does it boot normally? Have you rebooted yet (if not, don't)
You still haven't told me what software version you are running or whether or not you've edited your build.prop...
What Linux distro/version are you using?
Is your Linux install a full install, LiveUSB, or VM?
Is it 32 or 64 bit?
Are you using a USB 3.0 port?
Do you have a factory cable?
What is the output of the following command?:
Code:
sudo cat /etc/udev/rules.d/51-android.rules

Thanks dude I got adb working plus with the old soupkit revived my kindle fire 1st gen
Sent from my KFTT using xda premium

Update 3-10-2013: Added extra safety measures, including MD5 check on 2nd bootloader install

3-16-2013: Fixed issue with permissions on the rootplus script

03-18-2013 - Update: (RootPlus)
* Changed how 2nd bootloader is installed for compatibility with the KF2
* Added ability to update custom recovery. No need to update the script every time a new recovery is released.
* Added ability to choose partition images to be installed if more than one set exist in the BACKUP folder
* More intuitive restore of saved partition images - will hopefully prevent any chance of user error

03-19-2013 - Update + bugfix (RootPlus)
* Fixed issue with 2nd bootloader install - everything works as it should now
* Added timestamp to saved partitions. Gives users the ability to save more than one set of partition images
If you downloaded yesterday's update, please install this one. There was a bug preventing the 2nd bootloader install. It is fixed now.
Sorry for the inconvenience.

Hello, I'm stuck at step 6. Until "installing stack" it works fine, but than came some "not a directory" Alerts. See here:
http://pastebin.com/3rk4Vksh
Even setting it manualy with a rebooter-app in fastboot mode dosn't works, because it was not listed.
My System: Linux Mint 14 Cinnamon 64 bit (regular install). I dosn't have a fastboot cable yet, but the rebooter app. I think this is the point. The tool want to reboot it into fastboot, but it wants to boot normally.
Edit: I testet my fastboot with the instructons fron the 2nd bootloader tread and it works. But I have to boot normally and than rebooting it from the app into fastboot mode.

When did you download this? The most recent version installs the 2nd bootloader through the shell, not fastboot. And was your device rooted before trying to install the 2nd bootloader?
[Edit:] I think I see what the problem might be. Download this copy of the RootPlus script, place it in your ~/bin/SoupKit/files folder and replace the one that's already there. Let me know if that makes a difference and I'll upload an updated version.

It was the same, but I found the error. The directory tmp and the file install-recovery.sh were withe a .bak below. Just renamed and it should work.
Edit: it was succsessfull ^^

Panixy said:
It was the same, but I found the error. The directory tmp and the file install-recovery.sh were withe a .bak below. Just renamed and it should work.
Click to expand...
Click to collapse
Renaming install-recovery.sh to install-recovery.sh.bak is a necessary part of the recovery install. Why your tmp directory was renamed, I couldn't say. I'm looking at the script now and I don't see anything of the sort. I'll keep looking at it to see if anything stands out at me.

Thanks for this. I have a friend is no friend to linux, but I am. I read some other posts about rooting a kindle on software 7.30. Is this possible, or no? It's weird because people are successful to obtain root, but in post #2, it says that it will not work. just need to know so i can tell him.
either way, thank you for all the work that you do

[Q] Can someone explain QHUSB_DLOAD to me??

From researching around XDA, it looks like a "mode" either the PC or the phone enters into.... but what does it mean or do?
My problem is that when I plug my device into the laptop, it tries to install the necessary drivers, but states that it "Cannot install QHUSB_DLOAD"...
Any knee-jerk ideas as to why this would be? Is this one the drivers I install with the HTC drivers? I installed the drivers that are in the hasoon2000 post which contains the AIO toolkit. The driver file is called: HTC 3.0.0.007. I was thinking I could install it manually if it was a driver from this file....but I also tried to extract it (thinking I would get the necessary inf or .dll files), but it wouldn't let me extract it.
Any help is appreciated...!

http://www.google.nl/search?hl=en&s...s;..0.0...1ac.1j2.6.mobile-gws-hp.I6MZc5Yffqg
Or
http://www.google.nl/search?q=brick...ZSN0wXvoYHQAw&ved=0CAgQ_AUoAQ&biw=360&bih=567
Verstuurd van mijn HTC One S met Tapatalk

It seems you are in a brick! Do not use unlimited.io's tool, just not yet. That will hamper your efforts to rescue your phone.
Use the unbrickig thread in development. You need an Ubuntu LiveCD / Wubi
Sent from my One S using Tapatalk 2

Well that would make sense. The phone is an old 1S which I took for a swim (inadvertently) and it is damaged (it works, but the display is barely operable). Thankfully, I have a brand new replacement from TMO, but the problem is that I <b>really, really need the contents of my SD card</b> from the damaged phone. Before I go through the unbricking procedure, let me ask... Do you know of any simpler way to recover the contents of the SD?? That's all I need. Them I'm shipping it back to TMO.
Regarding a live Ubuntu CD...I have a dual boot setup but it's a debian distro...but I cannot imagine that would be an issue...but I guess I will find out.
Sent from my HTC VLE_U using xda premium

syntropic said:
Well that would make sense. The phone is an old 1S which I took for a swim (inadvertently) and it is damaged (it works, but the display is barely operable). Thankfully, I have a brand new replacement from TMO, but the problem is that I <b>really, really need the contents of my SD card</b> from the damaged phone. Before I go through the unbricking procedure, let me ask... Do you know of any simpler way to recover the contents of the SD?? That's all I need. Them I'm shipping it back to TMO.
Regarding a live Ubuntu CD...I have a dual boot setup but it's a debian distro...but I cannot imagine that would be an issue...but I guess I will find out.
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
Debian shouldn't really be an issue but I would work with Ubuntu just to be on the safe side. Not sure of a quicker way to rescue the contents of the SD card. Maybe if you enumerate the partitions you can save a copy of the SD card? Not sure though, touch of jobo would be a better person to ask since I am not too experienced with Linux.
I would unbrick it the normal way, unless someone knows otherwise.
Sent from my One S using Tapatalk 2

I wanted to do some testing, but I seem unable to boot into QHSUSB mode. On my other OneS I could do it by holding vol-up while rebooting bootloader, but not anymore.
Look at the downgrade thread. You can skip the step where you have to brick the device.
If you can see your partitions in your devices, you can try and mount the partition directly.
mkdir mydeadsdcard
mount -r -t vfat /dev/hdx36 mydeadsdcard
Chances are you can not see your partitions tho. I think the reason you boot into QHSUSB is that your emmc is defective.
-Jobo

touch of jobo said:
I wanted to do some testing, but I seem unable to boot into QHSUSB mode. On my other OneS I could do it by holding vol-up while rebooting bootloader, but not anymore.
Look at the downgrade thread. You can skip the step where you have to brick the device.
If you can see your partitions in your devices, you can try and mount the partition directly.
mkdir mydeadsdcard
mount -r -t vfat /dev/hdx36 mydeadsdcard
Chances are you can not see your partitions tho. I think the reason you boot into QHSUSB is that your emmc is defective.
Click to expand...
Click to collapse
I actually got it to connect (or I no longer so the QHUSB error). However, when I type adb devices, this is displayed.
C:\HTCOne>adb devices
List of devices attached
HT244W403652 recovery
So.. Is this phone in recovery right now??? (remember my screen is non-functional). And I was running Jellybean 4.2.2 on that phone....I tried "adb pull /mnt/sdcard" "adb pull /storage/sdcard" "adb pull /mnt/sdcard0" and "adb pull /storage/sdcard0"
And in all cases, it reported that the remote object "does not exist". Am I referring to the SDcard correctly??? Or is this an issue with the fact that it seems to be in recovery??
Thanks!!!

syntropic said:
I actually got it to connect (or I no longer so the QHUSB error). However, when I type adb devices, this is displayed.
C:\HTCOne>adb devices
List of devices attached
HT244W403652 recovery
So.. Is this phone in recovery right now??? (remember my screen is non-functional). And I was running Jellybean 4.2.2 on that phone....I tried "adb pull /mnt/sdcard" "adb pull /storage/sdcard" "adb pull /mnt/sdcard0" and "adb pull /storage/sdcard0"
And in all cases, it reported that the remote object "does not exist". Am I referring to the SDcard correctly??? Or is this an issue with the fact that it seems to be in recovery??
Thanks!!!
Click to expand...
Click to collapse
You can try referring to the internal storage using the mmcblk number (mmcblk0p12 is HBOOT for example)
Sent from my One S using Tapatalk 2

usaff22 said:
You can try referring to the internal storage using the mmcblk number (mmcblk0p12 is HBOOT for example)
Sent from my One S using Tapatalk 2
Click to expand...
Click to collapse
What is the block number for the SD card? I apologize for my ignorance....

syntropic said:
What is the block number for the SD card? I apologize for my ignorance....
Click to expand...
Click to collapse
/dev/block/mmcblk0p36

You're aces...
Sent from my HTC VLE_U using xda premium

Also see here: http://forum.xda-developers.com/showthread.php?t=2091801

touch of jobo said:
Also see here: http://forum.xda-developers.com/showthread.php?t=2091801
Click to expand...
Click to collapse
That's awesome! I had no idea someone had figured that many of them out...
I think i will thumbtack that to my wall.

OK... well here is what happened so far...
I tried using the block number but that wasn't recognized either... apparently the phone was off or actually in recovery (as it says "recovery" after I run "adb devices".
Then I decided to hit the power button. To my surprise, the screen flashed on. It made it all the way through to the home screen and then snapped off.... but I hear text message notifications so I know it is on. When I do "adb devices" now, I get "XXXXXXX offline" (see below for a cut/paste of my shell (I am in dos unfortunately).
C:\Windows\system32>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT244W403652 recovery
C:\Windows\system32>cd\
C:\>adb pull /dev/block/mmcblk0p36 c:\sdcardbak\
remote object '/dev/block/mmcblk0p36' not a file or directory
<<<At this point I powered up the phone... the screen went dead, but the phone is still running. Windows informed me that Linux Gadjet drivers were installed... However, I have no access to a pass-through storage device, and as you can see below, adb states that it is offline.>>>
C:\>adb devices
List of devices attached
HT244W403652 offline
I ran "adb pull /dev/block/mmcblk0p36/ ..." again and I recieved an error: device offline. I don't even know what offline means in this context. I always have USB debugging on this phone and I would be surprised if it wasn't still turned on. So what does offline mean??? Any ideas??
I have to copy this SD card in the next 24 hours and send this non-functioning 1S back to TMO, or they are going to screw me out of $850.....any help is sincerely appreciated!!!!!
EDIT: From a glance around the web and XDA... this seems like a driver issue... however, I just finished rooting my new 1S and everything worked fine. I tried switching USB jacks. As far as rebooting.... I can try, but I doubt the screen will turn on during the boot animation.... from experience it takes about 3 days for the screen to work... then it dies upon hitting the desktop (just like the scenario above). The only thing I can think of doing is installing HTC Sync... it is a longshot, but I cannot think of another solution.

Well HTC Sync didn't make a difference. I still get Error: device Offline when I try to do any action.
Is there any adb expert here who knows something??? I am trying to go through the adb commands (the few listed in windows), and hoping that something can be done.
As mentioned earlier.... I have some very important files on this SD card, and because I have been sent a replacement, I need to return this phone to TMO by thursday morning, or they will debit my card $850. Beyond important files, I also just have several GB of pictures and things that I really hate to lose.
So if there are any talents here who could think out of a box I would really really appreciate it.

syntropic said:
Well HTC Sync didn't make a difference. I still get Error: device Offline when I try to do any action.
Is there any adb expert here who knows something??? I am trying to go through the adb commands (the few listed in windows), and hoping that something can be done.
As mentioned earlier.... I have some very important files on this SD card, and because I have been sent a replacement, I need to return this phone to TMO by thursday morning, or they will debit my card $850. Beyond important files, I also just have several GB of pictures and things that I really hate to lose.
So if there are any talents here who could think out of a box I would really really appreciate it.
Click to expand...
Click to collapse
Are you running a CM10.1 or Android 4.2.2 ROM?
Device offline is usually when you haven't allowed adb to perform operations on your phone.
If yes, once you do adb devices and if USB debugging is enabled, you need to press "always allow from this computer" and "OK" (obviously you have to simulate where the buttons are since your touchscreen doesn't work)
Here's a screenshot from a different device to help you.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my One S using Tapatalk 2

usaff22 said:
Are you running a CM10.1 or Android 4.2.2 ROM?
Device offline is usually when you haven't allowed adb to perform operations on your phone.
If yes, once you do adb devices and if USB debugging is enabled, you need to press "always allow from this computer" and "OK" (obviously you have to simulate where the buttons are since your touchscreen doesn't work)
Here's a screenshot from a different device to help you.
Sent from my One S using Tapatalk 2
Click to expand...
Click to collapse
Thank you... that's very helpful... I was running a baked bean version I built and that was based on cm10.1/ 4.2.2.
But the only puzzling thing is: (i) I have never seen that message before and yet (ii) was—before the phone was damaged—in ADB all of the time...
So I will trying poking around the screen. I only hope that when the screen goes out it doesn't also render touchscreen non-functional. Since we cannot "wake-up" our phones if they are in sleep mode, right?? We always need to use a hardware button like Power or the volume rocker. But I will give it a shot...
THANKS!

Well, know the screen is on all the time, but there is nothing to see... it is all distorted video... like chomatic noise basically. And I tried several times to run "adb devices" and when I would get
error: device offline
I would try to press the part of the screen I surmised would be correct.
Eventually I launched some app I have on my desktop...so the touchscreen is working.
But I don't think that message is the problem (or rather, I don't think it is coming up).
I know this is not an easy nut to crack, but if you have any other ideas, please let me know. I am going to scour the web for any other posts about offline devices. I just cannot imagine that, since ADB was built for a developer to use from a special shell on the computer that there isn't some way to hack through this....

syntropic said:
Well, know the screen is on all the time, but there is nothing to see... it is all distorted video... like chomatic noise basically. And I tried several times to run "adb devices" and when I would get
error: device offline
I would try to press the part of the screen I surmised would be correct.
Eventually I launched some app I have on my desktop...so the touchscreen is working.
But I don't think that message is the problem (or rather, I don't think it is coming up).
I know this is not an easy nut to crack, but if you have any other ideas, please let me know. I am going to scour the web for any other posts about offline devices. I just cannot imagine that, since ADB was built for a developer to use from a special shell on the computer that there isn't some way to hack through this....
Click to expand...
Click to collapse
So the screen half-works now? Does it show part of the screen?
I would keep trying to get the device online using the accept RSA fingerprint method. You can connect the phone via USB to a different computer with adb. Type adb devices on the cmd/terminal and then the "Accept RSA fingerprint" dialog should come up.

syntropic said:
Am I referring to the SDcard correctly??? Or is this an issue with the fact that it seems to be in recovery??
Click to expand...
Click to collapse
When you boot into recovery, your sdcard is not yet mounted.
Boot your device into recovery.
Get into an adb shell and type 'mount /sdcard'.
In you adb shell, type 'df' (or 'mount') before and after you mount the sdcard partition to make sure it got mounted. Type 'ls /sdcard/' to check whether you can see your files on your sdcard. If your sdcard partition is now properly mounted in recovery, then from your PC you can adb pull /sdcard/
-Jobo

[Q] Rooting NEC Terrain

Hello! I've read the one thread I can find on this, but doesn't seem to be a lot of activity there lately.
I wonder whether anyone's still working on this and whether there's been any progress!
Anyone know?
Thanks much
WP

Wombat Pete said:
Hello! I've read the one thread I can find on this, but doesn't seem to be a lot of activity there lately.
I wonder whether anyone's still working on this and whether there's been any progress!
Anyone know?
Thanks much
WP
Click to expand...
Click to collapse
Root it with Framaroot App...
Press thanks if it worked

Worth trying, but - alas
N'ayam Amarsh'e said:
Root it with Framaroot App...
Press thanks if it worked
Click to expand...
Click to collapse
Thanks for the idea; unfortunately, neither exploit worked. Any other ideas?

Wombat Pete said:
Thanks for the idea; unfortunately, neither exploit worked. Any other ideas?
Click to expand...
Click to collapse
I have a universal Guide To root phones I am now goin' to post it... You can read it and root your phone
---------- Post added at 01:22 PM ---------- Previous post was at 12:34 PM ----------
Wombat Pete said:
Thanks for the idea; unfortunately, neither exploit worked. Any other ideas?
Click to expand...
Click to collapse
Read My Universal GUIDE To root Any Android Device : http://forum.xda-developers.com/showthread.php?t=2684210
Don't Forget To press Thanks Whenever I help You...

Problem with Explorer
N'ayam Amarsh'e, I'm trying your system. So far, so good - up until the Droid Explorer step.
But Droid Explorer installs, with the SDK tools, ... and then crashes upon running it (can't find the SDK stuff).
I looked at the Droid Explorer site under issues - EVERYONE is now having this problem.
I tried various locations for SDK, ...uninstalling and reinstalling DE, and and even earlier releases of Droid Explorer (from before the problem seemed to have cropped up) - nothing works.
Is there any alternative that will work? Or do you happen to know how to fix this problem (no one on their forums seems to know!)?
Thanks again
PS - I got release 8.7.2.x64 to install AND start, but now it doesn't find the android device. Made sure USB debugging is still connected, and that it's "connected as a media device".
PPS - Droid Explorer's site says everywhere that it's supposed to work for already-rooted devices...
N'ayam Amarsh'e said:
I have a universal Guide To root phones I am now goin' to post it... You can read it and root your phone
---------- Post added at 01:22 PM ---------- Previous post was at 12:34 PM ----------
Read My Universal GUIDE To root Any Android Device : http://forum.xda-developers.com/showthread.php?t=2684210
Don't Forget To press Thanks Whenever I help You...
Click to expand...
Click to collapse

Wombat Pete said:
N'ayam Amarsh'e, I'm trying your system. So far, so good - up until the Droid Explorer step.
But Droid Explorer installs, with the SDK tools, ... and then crashes upon running it (can't find the SDK stuff).
I looked at the Droid Explorer site under issues - EVERYONE is now having this problem.
I tried various locations for SDK, ...uninstalling and reinstalling DE, and and even earlier releases of Droid Explorer (from before the problem seemed to have cropped up) - nothing works.
Is there any alternative that will work? Or do you happen to know how to fix this problem (no one on their forums seems to know!)?
Thanks again
PS - I got release 8.7.2.x64 to install AND start, but now it doesn't find the android device. Made sure USB debugging is still connected, and that it's "connected as a media device".
PPS - Droid Explorer's site says everywhere that it's supposed to work for already-rooted devices...
Click to expand...
Click to collapse
Hi this shouldn't be a problem but I think linux would be the best.... in linux you can use nautilus for exploring files of your device with root privileges... try it... i m going to edit the guide now...

Linux
N'ayam Amarsh'e said:
Hi this shouldn't be a problem but I think linux would be the best.... in linux you can use nautilus for exploring files of your device with root privileges... try it... i m going to edit the guide now...
Click to expand...
Click to collapse
So I have to find someone with a linux box? I don't have one at the moment... hmmm...

Wombat Pete said:
So I have to find someone with a linux box? I don't have one at the moment... hmmm...
Click to expand...
Click to collapse
See my guide again it's updated... it also have links

Nautilus does not detect NEC Terrain in Recovery mode
N'ayam Amarsh'e said:
See my guide again it's updated... it also have links
Click to expand...
Click to collapse
Tried Ubuntu 11.04 as well as a couple of other versions. None of them detect anything with the NEC Terrain in recovery mode.
Other hints are welcome, I too would like to have this phone rooted.

timekiller_9 said:
Tried Ubuntu 11.04 as well as a couple of other versions. None of them detect anything with the NEC Terrain in recovery mode.
Other hints are welcome, I too would like to have this phone rooted.
Click to expand...
Click to collapse
You surely don't have drivers.... Download them again and give it a try...

N'ayam Amarsh'e said:
You surely don't have drivers.... Download them again and give it a try...
Click to expand...
Click to collapse
What drivers are you talking about? There are no "drivers" for Ubuntu per say. The only thing that needs to be done is in /etc/udev/rules.d you have to have the appropriate vendor in there, which I do. With the NEC Terrain booted normally:
$ ./adb devices
List of devices attached
30c17c2 device
then I do
$ ./adb reboot recovery
and wait for the NEC Terrain to get in to recovery mode
$ ./adb devices
List of devices attached
And that's it, no devices listed. The NEC Terrain does not respond in recovery mode. Please don't say I don't have drivers, drivers are for Windows. You said this should be done in Ubuntu via Nautilus. I'm not seeing how that could be the case. Please enlighten.

Waiting and Watching
Just Gonna throw out that i have two of these phones. If anyone can tell me what to do to help things along I will. I have tried several different universal root methods to no avail. Watching intently. Interested enough that i made an xda account after lurking for the last few years.

Any luck rooting the NEC Terrain?

No Luck
Haven't had any luck rooting it yet. But I'm quite impressed with the durability of these phones. Ive had mine covered in paint, washed it with gas, and sent it to the bottom of the swimming pool. It just keeps going strong.

Official NEC Terrain site has changed..
Before I bought my NEC Terrain the page necterrain(dot)com was an info site about the phone.
It has since changed to a strange log-in page. I know this is off toppic, but maybe there is some magical nugget of root-getting unlocking code in there.
..not that I'm advocating breaking into such a page.. I'm just postulating. :laugh:

found this today...
I'm not too savvy with this tech stuff but i figured if anyone could do it it would be you guy's here... i did not create this nor write it and since i am new i cannot post a link but its from our friends over at yumapk... so w/o further a due:
"Here is the tutorial of getting root access on NEC Terrain.
Before getting access on NEC Terrain, you need to prepare 4 tools:
Ⅰ：Android SDK
Ⅱ: The related drive of NEC Terrain
Ⅲ: cm-hero-recovery.img
Ⅳ: superuser.zi
The first step is to install USB drive:
Firstly, let’s come into this step. Find Setting-Application program-USB debugger button, then check the first option. Next, connect your USB line with PC, it will prompt you to install driver. If it is the 32 bit system, then you are supposed to choose “x86” document to install the drive. Whereas, if it is 64 bit system, choose “amd64” document to install the drive.
The second step is to prepare the software for NEC Terrain:
In detail, remove the “TMG” document in your software kit to the root directory in C disk, in order to give us the convenience of finding C:\TMG\
The third step is to examine adb.exe and fastboot.exe:
To begin with the third procedure, all we need to do is to ensure that we have the document of adb.exe and fastboot.exe in TMG. So we need to accomplish those procedures one by one.
The fourth step is to check the condition of drive installation:
Unplug your USB line, then shut down NEC Terrain, next press the backspace key. Go on pressing the power key to enter bootloader. Then connect NEC Terrain with PC, and fastbootusb will come out in NEC Terrain. Pay more attention that never press mount at this time.
Open Start-Run-CMD, then enter the order: cdC:\TMG
C:\TMG>_ will come out when the order runs successfully.
Then input the order: fastboot devices.
The fifth step is to start rooting:
Enter: fastboot boot cm-hero-recovery.img after C:\TMG>. Then NEC Terrain will enter the mode of recovery.
We will see seven options in this mode, they are the following ones:
[Home+Back]reboot system now\\restart
　[Alt+S]apply sdcard:update.zip\\install update.zip in SD
　[Alt+A]apply any zip fromsd\\install any zip file in SD
　[Alt+W]wipe data /factoryreset\\delete all datas
　[Alt+B]nandroid v2.2 backup\\back up
　[Alt+R]restore late stbackup\\recover the final back-ups
[Alt+F]repair ext filesystems\\suggest backing up ROM in NEC Terrain, use the trackball to move the cursor to [Alt+B]nandroidv2.2backup, check it. If there is something wrong with your NEC Terrain, it can also recover.
　　
　
　　
　　Now start entering the order, an order is in a line. Pay attention to the small letters and the big letters and also the blank.
　　adb shell mount /system
　　adb push su /system/bin/
　　adb shell chmod 4755 /system/bin/su
　　adb push Superuser.apk /system/app/
　　adb shell reboot
　　After rebooting, you will finally get root access on NEC Terrain."
if this works hopefully someone can make a script to make this more convenient for the others like me

[permanently]temp rooting tools
it suport xposed framework , wifi tethering shoud work(byebye ATT.
this tool came from twitter/uniQta.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://twitter.com/uniQta/status/515004550520918017/photo/1
https://twitter.com/uniQta/status/514104619396378624/photo/1
----
03/26 file was removed.

Hi.. I'm a completly new android guy and started with NEC terrain this week.. And after one weekend with it I managed to skrew it up allready.. I have an unlocked phone, but played with some 2G/3G/LTE apps, so I could switch between those signals, since I could do that on my old BB pearl, and on the pearl it worked like a charm.. Well I press the wrong button, and now my radio is turned onto USA BAND, and can't be changed unless I flash the stock firmware.. I have no idea how to do that so I need help.. But at the same time I've looked up all this ROOT, cuz' this awesome phone does not have my good old features from nokia feature phones nor the blackberry.. the abillity turn power off AND ON on schedule.
And thru my frustrations I fell over a guy who put android 4.4 on his device, since I'm new I read somewhere I can't post links.. But if you google: "How to update NEC Terrain to Android 4.4-Kitkat" then you find the post right away.. does this help you guys? and in the end me?
Greatings from Daniel from Denmark

Lets continue discussion in one thread!
http://forum.xda-developers.com/showpost.php?p=59514154&postcount=77
I created a GitHub repo to collect information, also on how to disable apps (since thats as good as it gets for now).

recover/repair a file ( not deleted)

Hi,
i tried to cut and paste the files from my android to the pc, all went through, but one of them didn't seem to start, so i tried copying somewhere else, it wouldn't work either, is there a way to recover it from the phone itself or make it work/repair it in the pc?
Thank you

what is the file format of the one file that didn't moved?

aiSanaul said:
what is the file format of the one file that didn't moved?
Click to expand...
Click to collapse
it is Mp4, and was a video taken by me with the camera app

METAL66 said:
it is Mp4, and was a video taken by me with the camera app
Click to expand...
Click to collapse
did you tried send it separately?
also is video size larder like 3-5gb ?
try creating an archive of it in phone and then try sending.

METAL66 said:
Hi,
i tried to cut and paste the files from my android to the pc, all went through, but one of them didn't seem to start, so i tried copying somewhere else, it wouldn't work either, is there a way to recover it from the phone itself or make it work/repair it in the pc?
Thank you
Click to expand...
Click to collapse
what tool used to tranfer?

the Microsoft MTP protocol is not implemented well. in case you faced the famous data loss on copy with Windows Explorer, the files are gone and can't be recovered.
you can copy existing files from adb. first, enable developer options by tapping the build number on the - about phone - screen (7x) seven times. in settings - developer options - enable usb-debugging. on PC download platform-tools and install the google usb driver. add the platform-tools path to environment variables.
open cmd.exe and navigate to the platform-tools directory. type adb devices and confirm the connection on phone screen. you are now ready to copy directories.
Code:
adb devices
adb pull -a /sdcard/DCIM/Camera

aiSanaul said:
did you tried send it separately?
also is video size larder like 3-5gb ?
try creating an archive of it in phone and then try sending.
Click to expand...
Click to collapse
the file is 1GB, i will try to zip and extract, but would it help? because i need to repair it not just send it.
EDIT: i get this message when trying to zip/rar it:
Read error in the file.
Data error (cyclic redundancy check).

jwoegerbauer said:
what tool used to tranfer?
Click to expand...
Click to collapse
a normal copy paste from the phone "folder" on pc windows

alecxs said:
...
you can copy existing files from adb. first, enable developer options by tapping the build number on the - about phone - screen (7x) seven times. in settings - developer options - enable usb-debugging. on PC download platform-tools and install the google usb driver. add the platform-tools path to environment variables.
....
Click to expand...
Click to collapse
IMO a bad general recommendation, if phone isn't a Google device like Pixel or Nexus. One have always to use the ADB provided by device's OEM.

Right, Windows might complain "We couldn't find driver software for your device" even though you pointed it to the correct driver. But the driver is pretty generic and works for all devices, if you force install it.
Update Driver -> Browse my computer for driver software -> Let me pick from the list of device drivers on my computer -> Show all devices -> Have Disk -> android_winusb.inf -> Android ADB Interface
It may not work for every device (I remember once a Sony Xperia didn't work) but I can confirm for Huawei, Samsung, Xiaomi, Cubot and Blackview devices. For which phone/ tablet the Google USB driver did not work for you?
But right, you can always use the OEM usb drivers for adb. There the PID/VID is added in the android_winusb.inf and driver is properly signed, so these drivers can installed automatically when device is connected. But I am not that Windows expert.
METAL66 said:
the file is 1GB, i will try to zip and extract, but would it help? because i need to repair it not just send it.
EDIT: i get this message when trying to zip/rar it:
Read error in the file.
Data error (cyclic redundancy check).
Click to expand...
Click to collapse
Note that the MTP protocol is only a transfer protocol for copying files to/off the phone, it's not really a "drive" you can use like other disk drives from Explorer (for example editing files). It has issues with large files, I do not recommend that method. People have lost data trying to move directories from phone to PC due a serious bug.
adb is much more stable and faster, although it also cannot handle read errors in case of file system corruption on the phone itself. for this I recently wrote a shell script to pull files in smaller parts. But it requires Linux.

alecxs said:
Code:
adb devices
adb pull -a /sdcard/DCIM/Camera
Click to expand...
Click to collapse
Huh? Why the -a?
-a listen on all network interfaces, not just localhost
MTP is bogus, ADB is much better.
I have a Windows utility adbsync (in the sig) that's nice for syncing directories between device and desktop.
I set it up to sync reading materials to devices and photos/movies back to desktop.

the -a flag for adb pull preserves mtime of pictures.

alecxs said:
the -a flag for adb pull preserves mtime of pictures.
Click to expand...
Click to collapse
Oh! I learn something every day.
Still, that's wacky that there is the global -a and the pull-specific -a.
(adbsync preserves the modified times too!)

METAL66 said:
a normal copy paste from the phone "folder" on pc windows
Click to expand...
Click to collapse
If MTP doesn't work as expected, then instead of using ADB try FTP: Windows OS has it - you simply have to activate the FTP client, Android file explorers as https://apkpure.com/file-manager-file-explorer/com.alc.filemanager have it - the FTP server.

METAL66 said:
the file is 1GB, i will try to zip and extract, but would it help? because i need to repair it not just send it.
EDIT: i get this message when trying to zip/rar it:
Read error in the file.
Data error (cyclic redundancy check).
Click to expand...
Click to collapse
there is the problem system is unable to read the file... is that file in your phone's internal storage or in sd card, cuz maybe the card is read write protected and causing problems.
try providing read and write permissions for the file and then continue sending it to pc...

METAL66 said:
Hi,
i tried to cut and paste the files from my android to the pc, all went through, but one of them didn't seem to start, so i tried copying somewhere else, it wouldn't work either, is there a way to recover it from the phone itself or make it work/repair it in the pc?
Thank you
Click to expand...
Click to collapse
A file only can be read by system if both its start address and its end address ( there may be a chain of several start and end addresses if file is stored in chunks ) on the storage medium is known. The file's content hereby is irrelevant, it's not interesting the system what is to be read: that's only of interest when file's content should get viewed.
This should be clear to anybody. @alecxs has already pointed out that.
If a copy operation fails it should be obvious that the 1 file you mentioned couldn't get read by system, then it's corrupted for whatever reason.
You have no chance to get this fixed.
From the point of view of the computer reading and viewing a file are totally different things.

aiSanaul said:
there is the problem system is unable to read the file... is that file in your phone's internal storage or in sd card, cuz maybe the card is read write protected and causing problems.
try providing read and write permissions for the file and then continue sending it to pc...
Click to expand...
Click to collapse
If a SD-card is locked
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
then you will not be able to modify or delete the contents on the memory card: READING a locked SD-card can't get prevented, never. If a SD-card isn't readable then it's corrupted. Point.