Related
ph84 said that dual boot is possible and he will write how to.
When???(don't hurry, I only ask)
Maybe your question can be answered if you look for the Topogigi's post in this thread [HOW TO] Linux on Folio.
I've not try this, because i don't understand some things... if someone makes a how to step by step, would be amazing !!
Here is how to get it without steps:
Topogigi said:
[ONLY FOR DEVELOPERS AND SKILLED PEOPLE: NOT FOR NEWBIES!!!]
My 2 cents:
I installed ubuntu and it works quite well. I'd like to point out that it you can boot android or ubuntu flashing the boot.img containing the linux kernel in place of recovery kernel (fastboot flash recovery boot.img). You can even try a kernel before flashing it to the device (fastboot boot boot.img). To enter fastboot mode in your device, simply press the power button three times when the Toshiba logo appears on the screen at powerup, then press volume up one time. Voila, you are in fastboot mode...
To boot linux, you have to press "power+volume up", then follow the instruction on screen to wipe the device (don't worry, it will boot linux and it will not wipe anything). You'll miss the recovery partition that way, but you'll gain a dual-boot tablet with android and ubuntu in change. Not a bad trade.
If you really need recovery, you can always reflash it with fastboot, so the process is perfectly reversible.
Now, back to business:
1) Touchscreen works (sort of). If you apt-get evtest, you'll notice that /dev/input/event3 is bound to the touchscreen and it reports to be alive and kicking. The test reports the coordinate changing and the pressure on the screen (multitouch works too). But......in Xorg, the device only reports the pressure and coordinates are not changing. You can test with xinput as I did. It seems a software-related issue: the drivers does not report correctly what the hardware is telling him. I'll investigate and report back if news will come out.
2) Wifi could eventually work. The card is bound via SDIO bus, and a ar6000 driver supporting SDIO is available. I'll try to compile the driver ASAP.
3) Suspend, cpufreq do not work and I doubt they will work without driver sources
4) Battery is working, framebuffer is working good and the system seems quite snappy also with an EXT4 partition on a MMC. Openoffice works great, quicker than expected.
5) If you compile the kernel with nilfs2 support, you can easily mount all the android partitions within ubuntu with ease. Not bad...
That's all for the moment: I hope that someone will help me to make this little devil fly.
Click to expand...
Click to collapse
sergi711 said:
Maybe your question can be answered if you look for the Topogigi's post in this thread [HOW TO] Linux on Folio.
I've not try this, because i don't understand some things... if someone makes a how to step by step, would be amazing !!
Here is how to get it without steps:
Click to expand...
Click to collapse
That's quite easy in fact :
In fastboot, just flash the boot.img instead of recovery :
fastboot flash recovery boot.img
That's it... you will loose "auto" recovery, but you will gain Linux Ubuntu
Akta
Akta77 said:
That's quite easy in fact :
In fastboot, just flash the boot.img instead of recovery :
fastboot flash recovery boot.img
That's it... you will loose "auto" recovery, but you will gain Linux Ubuntu
Akta
Click to expand...
Click to collapse
It sounds easy... but i have never enter in fastboot mode... I don't know what commands use...
Another question, I have flashed the update.zip from ph84 to boot only ubuntu, when i flash this boot.img on fastboot mode how I flash the foliomod ???
fastboot, SDK, UPDATE.ZIP, DRIVERS etc.
Sergi711
1.I know for that(try), but I can't use fastboot. I installed all drivers, but I can't send commands to Folio 100. I made thread for help, but no one help me. If you can help, please, help me!!!!!!
Can we make update.zip with that kernel and don't use fastboot?
2.a)First, download and install SDK.
http://developer.android.com/sdk/index.html
Second, go here http://www.addictivetips.com/mobile/enable-adb-usb-drivers-for-nvidia-tegra-based-android-tablets and install drivers.
Third, enter fastboot mode(3X Power UP+Volume UP) IF YOU PRESS POWER UP 4X, YOU'LL BRICK TABLET AND FOR THAT YOU CAN'T FIND HELP!!!!!
Moreover, connect Folio with PC,Laptop, NetBook, Tablet PC or NoteBook via USB and open terminal(Start>Run>cmd) and go to C:/android-sdk/platform-tools (in my
case)
Terminal: cd C:/android-sdk/platform-tools
Fifth, now run fastboot.exe and type anything you want
Terminal: fastboot _______________( fastboot flash recovery boot.img)
b) If you flash boot.img from ph84 to boot Ubuntu ARM on Folio 100, in future, you'll can only boot from SD Card or USB(sdmmc-update.zip or usb-update.zip). You'll not use Folio's internal storage and you'll can't boot to FolioMod, but from recovery you can easily reflash FolioMod or another rom or custom kernel(you need to reflash kernel and you can made your own update.zip with your custom kernel and don't touch FolioMod )
Akta77
Can we we copy recovery to /date or /date/date folder and boot it like MCLP said for installing FolioMod or another rom?
Step 1. Install Root Explorer on Folio 100(can't post app, because rules, but with googling find it easily or download it from android market)
Step 2. Copy the recovery image from FolioMod(if you want original recovery) or from CyanogenMod7.0.0(if you want unofficial ClockworkMod recovery) to SD Card or Internal storage
Step 3.With Root Explorer copy recovery.img to /date or if you find another date directory inside copy there(copy recovery.img to both directory just in case)
Step 4. Exit from Root Explorer, got to Settings>Applications>Development and enable USB Debugging
Step 5. Connect Folio 100 to PC or etc. via USB and open Terminal(cmd) and go to SDK directory C:/android-sdk/platform-tools(in my case)
Terminal: cd C:/android-sdk/platform-tools
adb shell (use this if you have installed SDK drivers for Tegra devices)
cat /data/recovery.img >/dev/block/mmcblk0p7
or
Install any Terminal app on Folio 100 and type
Android Terminal: cat /data/recovery.img >/dev/block/mmcblk0p7
After this, you should have recovery
Jon2555 said:
Sergi711
1.I know for that(try), but I can't use fastboot. I installed all drivers, but I can't send commands to Folio 100. I made thread for help, but no one help me. If you can help, please, help me!!!!!!
Click to expand...
Click to collapse
Maybe this helps: http://forum.xda-developers.com/showthread.php?t=1055754
Most other fastboot binaries out there don't recognize tegra devices.
I just use the SDK's Fastboot under Linux (built from Cyanogen's 7 repo) without any problem.
If you are using Windows, have you modified the inf has stated by google?
Entering fastboot is simple : just press x3 power and then volume up at boot screen.
You will be in fastboot mode.
I am not sure we can boot the kernel from somewhere else than boot partition or recovery partition. But we could maybe build a relocable kernel and load Linux or Android using kexec from boot partition like "petiboot" on PS3
Akta
Thank's guys!!! I'm going to try it whan I back from France.
Sent from my folio 100 using Tapatalk
could someone that have a dual boot ubutntu/android make a how to for us... ??? because i read the lastest post that you reply i don't know how to have a dual boot yet.. i can't understand... please a how to is needed, step by step...
thanks in advance !!!
Hi,
Just wrote you how to do it
Boot the tab in fastboot (3xPower + 1 Vol Up)
Then connect your tablet on your PC and do :
fastboot flash recovery boot.img (boot.img is extracted from update.zip according to your wish (SDCARD or USB PENDRIVE)).
Akta
ok i flash the boot.img on fastboot, and then ??? i only have now ubuntu, how i install android after fastboot flash boot boot.img ????
I know, i must enter fastboot mode, and flash boot.img instead of recovery.
After that, i will only be able to boot from sdcard... isn't it ?
Ok, i must have 2 sdcards to boot android, and the other sdcard to boot ubuntu ???
if this is right... how the sdcard must be ??? update.zip on the root ???, the update zip extracted on the root of sdcard ??
i have lot of doubts after the fastboot flash recovery boot.img step, sorry.... can anyone help me ??
I think when you flash boot.img(sd or usb) for dualboot, when sd card with Ubuntu is in Folio you'll boot ubuntu(sd or usb) and if you haven't got Ubuntu sdcard or you have it (but not Ubuntu sd) or if you haven't any you will boot to android.
What's up with my question?
Sent from my folio 100 using Tapatalk
Ok i understand that after flash boot.img instead of recovery on fastboot mode... folio will boot from sdcard, in that case, if you push a sdcard with an ubuntu filesystem, folio will boot ubuntu, and if you remove sd after boot moment, folio will recognise internal sd and boot android ??? thats it ???
edit: but what boot.img must i flash ???
When i will have some time, i will rebuild a boot.img able too boot linux from a second partition on the sdcard. You will have fat32 on first partition and ext3 or ext4 on second. For now, you can live your sdcard in the folio but android is not able to access it (lack of ext3 / ext4 support, but easy to install ).
Akta
Thank's Akta for your help!!! Can you sometime post your progress? I want to help, but I don't have dev skills. Can you post some good link(searched, but no luck) or your howto about making kernels? I found for themes and I'll try to make some in my free time.
Sent from my folio 100 using Tapatalk
Quite interested by the dual boot on Folio 100.
I will keep an eye on this thread.
Akta77 said:
That's quite easy in fact :
In fastboot, just flash the boot.img instead of recovery :
fastboot flash recovery boot.img
That's it... you will loose "auto" recovery, but you will gain Linux Ubuntu
Akta
Click to expand...
Click to collapse
I there, I have few questions:
First, why are you flashing boot into recovery? Is not supposed that boot is the image that cares about booting procedure?
Second, once first question is solved, which boot image are we supposed to flash? I mean, we will need one that searches into sd for a boot/grub, isnt it?
Third, what about the procedure, I explain myself, the logical order of doing all this is: flash an android rom, CM for example, then do the procedure to install ubuntu into the sd and finally flash the boot img so system looks for sd-ubuntu and if it's not found, then boot internal android rom, am i right?
Thanks!
1. Yes.
2. Yes.
3. Yes.
Sent from my GT-I5700 using Tapatalk
Well, then:
Which image should we flash? Where can I can get it?
And finally, this image where must be flashed to dualboot?
Thanks!
Look in the second post on first page. You will see someone talking about dual boot. Find that post in first threde of Ubuntu for Folio 100 that wrote DerArtem(I think)
I don't have time to post link, but if you don't find it tell me and I'll post link.
I have a UK-bought SGT10.1, which I rooted shortly after purchase and installed CWM Recovery using Odin. I've been running In Paris for a while, and was about to update to v5. Last time I downloaded pershoot's kernel from droidbasement, I saw an updated version of CWM Recovery here: http://droidbasement.com/db-blog/?p=2370.
Being a security-type, running the latest versions is always the best option to me - and seeing I know my way around the console I figured I'll install adb/fastboot and use that this time instead of Odin. So I downloaded the SDK, installed the Tab 10.1 drivers (I've reinstalled Windows since I rooted), and grabbed the fastboot .exe from the previous revision and placed it inside android-sdk\platform-tools next to adb.
Now I'm trying to follow the instructions to install the extracted .img - but having some issues getting into fastboot mode in order to execute the commands. Running adb devices results in expected output, as does adb reboot recovery. However running adb reboot bootloader causes the device to reboot all the way back through to the lockscreen. I see some advice stating that to manually enter fastboot you reboot the device holding power+vol down, then pressing down to switch to the second option that isn't download mode. However that to me is the option to manually enter CWM Recovery, so now I'm confused. Running fastbooot reboot-bootloader cause
I don't want to brick my device, so I figured I'd ask for some advice here for getting into fastboot mode, and ask whether I can just flash the .zip inside CWM Recovery or if that is a very risky move?
Thanks in advance
Hi,
I do have a Ace 2 (I8160) but I can't get the mobile on the Wifi and he keeps saying: trying to get the IP-adress
Does somebody know how to solve this problem?
Try to connect to another wifi. If the wifi you're trying is yours, go to the router's settings & remove wireless security, then try again.
For the moment \I'm in another house and again I can't get acces to the Wifi and there is also a Wifi signal that isn't protected and there I have the same problem .......... trying to get the IP-adress
You running stock or custom ROM? Have you flashed anything recently? Did the wifi ever work before?
I do have stock and yesterday I rooted the phone and I "think: it has something to do with that ?!
Is it an option to install the stock back there this is a new phone so I do have another phone for the moment.
Simply having root permissions shouldn't affect your ability to connect to wifi. Have you installed a custom recovery? If yes, try clearing cache & dalvik cache.
No I didn't.
Is it possible to install now or doesn't it make that any sence ..... I don't think so
Pfffff, how can we solve this ??
Some ideas:
Unroot, see if it reverts your problem
Flash a custom recovery, if one is available (I suggest Android Flash Recovery to flash it)
If you have a data connection, install ROM Manager & flash custom recovery that way
post-mortem said:
Some ideas:
Unroot, see if it reverts your problem
Flash a custom recovery, if one is available (I suggest Android Flash Recovery to flash it)
If you have a data connection, install ROM Manager & flash custom recovery that way
Click to expand...
Click to collapse
I'm from Holland and my English is not soooooo good
Do you mean that I can install the original software from this phone with the ROM Manager ( http://www.samfirmware.com/ ) ?
And as far I know it's not possible to unroot this phone ??!!
The ROM Manager app has an option to download & install CWM recovery, if your phone is in their database. sammobile/samfirmware will let you download the stock software for your phone, and you need to plug your phone to a computer to flash it. It will return your phone to stock, and you will lose all data.
I thought it was easyer with the second option:
Flash a custom recovery, if one is available (I suggest Android Flash Recovery to flash it) but I thin it works the same?
If ROM Manager has a custom recovery in their database, then that's easier & less steps, but I avoid ROM Manager because it bricked my phone. If you download a custom recovery .img file which you know is compatible with your exact model #, then Android Flash Recovery is probably safer. Android Flash Recovery requires the use of a computer, and a Windows one, at that. However, you can flash any custom recovery (i.e., AmonRa, TWRM), and not just CWM.
What is the bootloader / fastboot mode ??
Is that the CWM .... but I'm wondering if this is available for my GSM
No, CWM is recovery. When you see that, it means you have done something to force your phone to boot off of the recovery partition, instead of the normal boot procedure. Fastboot is different; it's like an alternative to adb. You can put your phone into fastboot mode (I don't have your device, so I don't know how you would do it), but you can also communicate through fastboot when you're not in fastboot mode.
To test if you're able to communicate with the device properly, connect your phone via USB, then type adb devices to see which devices are visible to your system; same with fastboot devices .
post-mortem said:
No, CWM is recovery. When you see that, it means you have done something to force your phone to boot off of the recovery partition, instead of the normal boot procedure. Fastboot is different; it's like an alternative to adb. You can put your phone into fastboot mode (I don't have your device, so I don't know how you would do it), but you can also communicate through fastboot when you're not in fastboot mode.
To test if you're able to communicate with the device properly, connect your phone via USB, then type adb devices to see which devices are visible to your system; same with fastboot devices .
Click to expand...
Click to collapse
Now I'm lost ...........
I connect my phone to the laptop and it's recognized but where do I have to type this ???
Those commands you type on the laptop, in a cmd window. Remember step 2? You need to be in that folder (which you said was c:\ ).
post-mortem said:
Those commands you type on the laptop, in a cmd window. Remember step 2? You need to be in that folder (which you said was c:\ ).
Click to expand...
Click to collapse
SORRY I don't really know what you are talking about
I know the old ms-dos command prompt ...... do you mean that and where did we talk about it ??
bruce the boss said:
SORRY I don't really know what you are talking about
I know the old ms-dos command prompt ...... do you mean that and where did we talk about it ??
Click to expand...
Click to collapse
LOL, sorry! I got this thread confused with another one! Never mind about the step 2 thing.
Uh, yeah, so those commands are typed into a DOS prompt. You need to be in the same folder as where your adb and fastboot binaries are located (unless you added them to the PATH, of course).
go to samsung service center. claim warranty.
it's easier to fix it
So I need to appeal to the android gurus of the world. I have an issue that I am having a difficult time sussing out and I am hoping someone else can help me figure it out.
My device is an HTC One M7, rooted, running Insert Coin 3.0.2 (Android 4.4.2), S-On., Hboot 1.44, TWRP Recovery
My problem is I can not access my Recovery and Fastboot isn't seeing my device, so I can not flash a new one. I can get to my phone in adb, just fine, but using flash_image to flash a recovery threw up a -1 error, so flashing recovery through adb appears to be out, as well. If I go to my Bootloader, selecting Recovery simply dumps me back to Fastboot.
I haven't booted into recovery since I installed this Rom, months ago, so I don't know exactly when my Recovery broke. I do know that today, I tried updating TWRP through Flashify and I suspect that may be part of the issue, since Flashify insisted on pulling down the TWRP for the M8 instead of the M7. I didn't catch that little nugget till after I flashed it.
I am pretty well open to anything that might work, but I am not sure what my options are when I can't even get into recovery. A pre-emptive thank you to anyone attempting to help. It should be said that apart from this, the phone works fine. I simply can't get into recovery to update my ROM, anymore.
Ok, I am an idgit. Could a mod move this to the Q&A forum? Apologies.
EqualOpportunityDork said:
So I need to appeal to the android gurus of the world. I have an issue that I am having a difficult time sussing out and I am hoping someone else can help me figure it out.
My device is an HTC One M7, rooted, running Insert Coin 3.0.2 (Android 4.4.2), S-On., Hboot 1.44, TWRP Recovery
My problem is I can not access my Recovery and Fastboot isn't seeing my device, so I can not flash a new one. I can get to my phone in adb, just fine, but using flash_image to flash a recovery threw up a -1 error, so flashing recovery through adb appears to be out, as well. If I go to my Bootloader, selecting Recovery simply dumps me back to Fastboot.
I haven't booted into recovery since I installed this Rom, months ago, so I don't know exactly when my Recovery broke. I do know that today, I tried updating TWRP through Flashify and I suspect that may be part of the issue, since Flashify insisted on pulling down the TWRP for the M8 instead of the M7. I didn't catch that little nugget till after I flashed it.
I am pretty well open to anything that might work, but I am not sure what my options are when I can't even get into recovery. A pre-emptive thank you to anyone attempting to help. It should be said that apart from this, the phone works fine. I simply can't get into recovery to update my ROM, anymore.
Click to expand...
Click to collapse
ADB works in an OS or in custom recovery and fastboot works in the bootloader. ADB doesn't work if the phone is in bootloader. I think you will have to run a RUU then go into stock recovery and do a factory reset. Let the phone boot normally then you can start the custom routine. You might also check to see if your ADB & fastboot are up to date. To run the RUU you will have to relock your bootloader since you are S-ON.
Thanks. Yea, I've managed to figure out the difference between adb and fastboot through all this. so plus for learning! However, the only method I have found for relocking my bootloader is through fastboot, which I can't seem to be able to use.
I will see if there's a newer version of fastboot out there, though. hadn't thought of that.
EqualOpportunityDork said:
Thanks. Yea, I've managed to figure out the difference between adb and fastboot through all this. so plus for learning! However, the only method I have found for relocking my bootloader is through fastboot, which I can't seem to be able to use.
I will see if there's a newer version of fastboot out there, though. hadn't thought of that.
Click to expand...
Click to collapse
Another quick thought, you wouldn't happen to be using Win 8 are you? If so, Win 8 doesn't see hboot 1.44 you are going to have to use a Win 7, Mac or Linux machine. Sorry, I didn't catch it earlier. Here is a how to for Linux and you don't have to install it permanently on your computer:
HOW TO USE LINUX FOR FASTBOOT & ADB VIA USB
This guide originally posted by @Danny201281
http://forum.xda-developers.com/showpost.php?p=54272479&postcount=219Linux is your friend; if your drivers are not working the chances of getting them working again without the phone booting are slim. But Linux doesn't need drivers to talk to your device.
Go here: http://www.pendrivelinux.com/ and download Universal USB Installer – Easy as 1 2 3
Then go here: http://releases.ubuntu.com/12.04/ and download Ubuntu from the first link at the top that says PC (Intel x86) desktop CD
Then use these files to create a bootable Linux USB drive with at least a 2 GB persistent file for storing files. You'll also probably need to change your boot settings in the computers bios to boot from USB.
MOVING YOUR FILES TO UBUNTU
Once booted you should be at a screen with options to "Try Ubuntu” or "Install Ubuntu". We don’t need to Install anything so just choose "Try Ubuntu" and the computer will boot to the Ubuntu Desktop (If you get a popup saying "system has encountered an error" or something similar just cancel and ignore it, it should have no effect on what we need to do as it is due to missing Linux OS updates we don’t need). On the left of the screen you'll see the Dock. Open the orange folder icon near the top this is the Home folder. It’s where we need to put any files we need to work with such as a rom.zip you want to push to the device or recovery.img files for flashing.
To get your files here is a simple drag and drop process. In the top left of the Home folder you'll see the drive structure of you pc under devices. Choose your PCs hard drive and Right-Click then" Open in a new window". Locate your .zip or .img files and drag them into the home folder. Now wait for the copy process to complete and rename them for easier typing later, e.g., rom.zip, firmware.zip or recovery.img etc.
USING ADB AND FASTBOOT
First you need to install adb fastboot; this is easy just 3 commands in the terminal. Thanks to Webupd8 team.
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
Code:
sudo apt-get update
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
Make sure your connected to the internet and press Ctrl+Alt+T to open the terminal then type or copy and paste the above commands one at a time waiting for each to complete their output. It may seem to have stopped at times but be patient when the prompt returns to normal enter the next command and when there all done you’re ready to use adb and fastboot.
Once you've moved all the files you need to the home folder that’s it you’re ready to go. Close everything down on the desktop (optional) and press Ctrl+Alt+T this will open the terminal now connect your phone with the USB cable. All fastboot commands need to have the "sudo" prefix added at the start, e.g.
fastboot flash recovery recovery.img becomes sudo fastboot flash recovery recovery.img
fastboot devices becomes sudo fastboot devices
However, adb should work basically the same as on windows. If you do have problems with normal adb commands adding “sudo” can help here as well.
Click to expand...
Click to collapse
Dude, you are my hero. I couldn't get fastboot to work, because I had missed the part where I needed to preface it with sudo. I had adb and fastboot running a couple of days ago on my Mint install, but I didn't realize I was missing 4 freaking letters to get it right. Just flashed latest twrp and booted into recovery, no problem.
Thanks again, for the help, even if I should have found that on my own, sooner. I thought I had really hosed something on my phone. Now I can move on to hopefully not screwing something else up.
You could have used flashify to flash a recovery.IMG. free app from app store
I mentioned trying Flashify in the OP.
Hi there,
i am newbie at xda-developers and posting this thread to get you android engineere help to unbrick my cdma android phone.
last yesterday, i've tried to to install custom rom in my phone by using adb sdk.
my hardware is QRD
brand model is MTS MTAG353 Coolpad 5210
Android version 2.3.5
Iast week i planed to change its rom and download a cwm7.1 Custom rom compatible with android 2.3.5.
i'd took backup of my original rom before flashing files of cwm custom rom. and start flashing files of cwm.
i'd first flash recovery by adb command "flastboot flash recovery recovery.img" and then flash "fastboot flash boot boot.img"
And after that use command "fastboot reboot" (mistake i did).
then my phone reboot, mts logo image appear and then black screen. My phone connected with pc but no usb port show that my android device is connected.
now i am confuse what to do. As adb don't show my device connected with pc. I've backup of my last used boot and recovery file. But i don't know, how to re-flash them.
so guys, if there is any solution reply me as-soon-as possible.