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.
Hi all, I did a fastboot-mac that recognize our folio when in fastboot mode.
Just to recall what fastboot mode is: fastboot is an android state useful to flash and/or wipe images/partitions.
All version I tried didn't worked and then I compiled my own starting from the latest android sources.
This version works! Maybe some mac user like me could find it useful.
fastboot-mac.gz
And this is the linux version:
fastboot-linux.gz
Now why would we want to use Mac.... anything
Thanks
sacrilege!!!!
Lappz said:
Now why would we want to use Mac.... anything
Thanks
Click to expand...
Click to collapse
Btw, there is also the linux version...
roglio said:
Hi all, I did a fastboot-mac that recognize our folio when in fastboot mode.
Just to recall what fastboot mode is: fastboot is an android state useful to flash and/or wipe images/partitions.
All version I tried didn't worked and then I compiled my own starting from the latest android sources.
This version works! Maybe some mac user like me could find it useful.
fastboot-mac.gz
And this is the linux version:
fastboot-linux.gz
Click to expand...
Click to collapse
i have a question. i did not quite understand how fastboot will work on linux. or what would the function be?. can you help me explain a little?
gingerboy92 said:
i have a question. i did not quite understand how fastboot will work on linux. or what would the function be?. can you help me explain a little?
Click to expand...
Click to collapse
for me the same... here what I found :
3) Get the latest version of fastboot from the android sdk
4) Boot folio into fastboot (switch on, after toshiba press 3x power and then volume up) and connect to pc via usb
5) go to the directory where the fastboot executable lives and type your command
I have a lot of problems to access my folio under windows. Because I use both mac and linux, for me is more handy to access the fastboot mode via those OSes.
In my understanding the fastboot ditributed with the android sdk does not include the latest code to handle the tegra2 platform; then this is the reason why I recompiled it for both mac and linux starting from the latest git sources.
There is another reason why is worth to use mac or linux : no drivers are needed to access the fastboot mode!
Btw, if your windows setup works, of course you don't need to use neither mac nor linux version.
Just to recap: the fastboot mode give you the ability to erase and write any partition on an android device. Is really easy to do it:
"fastboot devices" will list all android devices attached via usb in fasboot mode
"fastboot erase recovery" will erase the recovery partition
"fastboot flash recovery recovery.img" will flash a new recovery.img in few seconds
I like fastboot mode because is more effective flashing a new distro and for my setup is useful because I do dual boot with ubuntu, replacing the recovery partition with the linux boot image.
I forgot to mention "fastboot -w" to wipe data partition and restore factory default
Moved to proper forum
I Have a folio which is working on the normal android system, but when I tread to install foliomod a few months ago my folio got ****ed.!
i cannot enter recovery mode. This is the reason why i have to use fastboot right?
I'm on a mac and what are the precise instructions on making fastboot work? and what should i do to get my recovery working again?!
This is a part i do not get
'' go to the directory where the fastboot executable lives and type your command'' Directory??
When i run the mac file you provided i simple says : command not found, (while my folio is connected in fastbood mode!)
Please help me out! Thanks alot!
hi, first of all, you must install the android sdk.
go to: sdk and download android-sdk_r15-macosx.zip
then, decompress the zip file and move the created folder to the root of your boot harddisk.
well, now you have to download the basic tools: navigate to /android-sdk-mac_x86/tools and double click android. this will open the android manager
install at least Android SDK tools and Android SDK platform-tools (remove any other predefined download)
now decompress the fastboot-mac executable (from my first post) and move it to /android-sdk-mac_x86/platform-tools
ok; now open a terminal and type: "cd /android-sdk-mac_x86/platform-tools"
then try to type: "./fastboot-mac devices" it should show the list of currently attached devices in fastboot mode. often the device is displayed as "????????" it is ok.
if the last command doesn't work, maybe you need to give it execution permission with this command: "chmod +x fastboot-mac" and retry
try and let me know
once you get your device in fastboot mode, look for a recovery.img and do as follow:
./fastboot-mac erase recovery
./fastboot-mac flash recovery recovery.img
then reboot in recovery mode and install what you want.
I suggest you to download the cwm betelgeuse recovery (cwm=clockworkmod).
Roglio! Thanks in advance,
I'm going to try it out tonight after I finish work!
A quick question:
I haven't got my folio with me but when i try to do this:
ok; now open a terminal and type: "cd /android-sdk-mac_x86/platform-tools"
I get:
MacBook-Pro-van-Willem-Jan-van-Dun:~ willem-janvandun$ /android-sdk-macosx
-bash: /android-sdk-macosx: is a directory
MacBook-Pro-van-Willem-Jan-van-Dun:~ willem-janvandun$ cd/android-sdk-macosx
-bash: cd/android-sdk-macosx: No such file or directory
MacBook-Pro-van-Willem-Jan-van-Dun:~ willem-janvandun$ cd /android-sdk-macosx
Al different commands as you can see. Which is the good one?
Thanks!
Roglio you are an hero!
You made my day!
Great job and keep up the good work! my little nephew will be so glad his tablet is working again!
Thanks!
You're welcome
Glad of being been helpful!
One more question!
I installed foliomod and everything is working great! But how can i backup this complete rom? do i use Rom Manager? and whch clockworkmod should i install then?
THanks!!
Via fastboot you should already installed cwm. If not i suggest v0.3 based on cw 3028.
This recovery already has a backup functionality to save the whole system (data included) to an sd card.
taxandria said:
One more question!
I installed foliomod and everything is working great! But how can i backup this complete rom? do i use Rom Manager? and whch clockworkmod should i install then?
THanks!!
Click to expand...
Click to collapse
links broken !
roglio said:
Hi all, I did a fastboot-mac that recognize our folio when in fastboot mode.
Just to recall what fastboot mode is: fastboot is an android state useful to flash and/or wipe images/partitions.
All version I tried didn't worked and then I compiled my own starting from the latest android sources.
This version works! Maybe some mac user like me could find it useful.
multiupload-com/5EFKZ8IMT0"]fastboot-mac.gz
And this is the linux version:
multiupload-com/91QOOXZHPY"]fastboot-linux.gz
Click to expand...
Click to collapse
I have the 2 operative systems, and the binaries are very useful on both cases, but the links are broken, can you upload them again ?
thank you
Did you get the message: Magic Value Mismatch:-.-.-.-.-.-?!
After flashing a new recovery it happens sometimes.
GREEN ZONE
Are you able to go to the recocery menu(power + vol up)? If not, go to BLUE ZONE. If yes, follow these steps
1. check whether you have copied your rom as "update.zip" to your SD card's root directory
2. Go to recovery menu and install update.zip
BLUE ZONE
You may did something wrong while flashing a new recovery. Here is the right method:
1. go back to fastboot mode(power+power+power+vol up) and type these commands on your PC
2. fastboot erase userdata
3. fastboot erase system
4. fastboot erase cache
5. fastboot erase linux
6. fastboot erase recovery
7. fastboot flash recovery recovery.img (change path, if recovery.img is not in the same directory as fastboot.exe)
8. fastboot reboot
Are you able now to go to the recovery menu? If yes, go to GREEN ZONE and follow steps. If not, go to ORANGE ZONE.
ORANGE ZONE
Are able to unpack the update.zip and find the system.img and boot.img files? If not, then go to RED ZONE. If yes, copy these 2 files to the directory where the fastboot.exe is, run these commands:
1. fastboot erase recovery
2. fastboot flash recovery recovery.img
3. fastboot -w
4. fastboot erase linux
5. fastboot erase system
6. fastboot flash system system.img
7. fastboot flash linux boot.img
8. fastboot reboot
ROM is installed. Enjoy it!
RED ZONE
Make sure, that you copied the same recovery.img to fastboot folder, that you had flashed before to your tablet.
Type this command in recovery mode:
1. fastboot boot recovery.img
This command will run the recovery from your PC. After the recovery menu is booted, go to GREEN ZONE and enjoy your ROM!
If this was helpful to you, please do not hesitate to click on Thanks!
Lol, nice to see my post copy/pasted without any links indicated. Anyway, I hope It's helpful for ppl.
Tried following these steps, however, I'm still getting this error... followed this thread
http://forum.xda-developers.com/showthread.php?t=1470823
installed recovery successfully (via fastboot), and update seems to install fine, until I reboot and get the "Magic Value Mismatch" again..
Any ideas?
yellowumbrella said:
Tried following these steps, however, I'm still getting this error... followed this thread
http://forum.xda-developers.com/showthread.php?t=1470823
installed recovery successfully (via fastboot), and update seems to install fine, until I reboot and get the "Magic Value Mismatch" again..
Any ideas?
Click to expand...
Click to collapse
So you installed the recovery via fastboot. Did you manage to boot into recovery mode?
I had that issue, that I couldn't boot into recovery mod from my Folio, by pressing power+Up button. Thats why I added the RED ZONE method. Its like booting recovery from your PC. (fastboot boot recovery.img). All the times I wanna upgrade my current ROM, I have to do this step, because the power+up does not work, and the Folio skips booting in recovery and wanna do normal booting. However there is no Rom installed on machine, so I get the magic value mismatch message.
So try to boot recovery from your PC, but be sure you have copied to your fastboot folder the same recovery, that you flashed onto the tablet.
I hope it was helpful. If something is not clear, feel free to ask.
Hi there, thanks for the answer.
I am able to install recovery images via fastboot.
Device is showing up as a question mark with >fastboot devices
but recovery installs fine. CWM gives a series of e: can't opne/mount /cache errors.
Foliomod 1.4 installs no problem, thanks to the method here
http://forum.xda-developers.com/showthread.php?t=1458876
yellowumbrella said:
Hi there, thanks for the answer.
I am able to install recovery images via fastboot.
Device is showing up as a question mark with >fastboot devices
but recovery installs fine. CWM gives a series of e: can't opne/mount /cache errors.
Foliomod 1.4 installs no problem, thanks to the method here
http://forum.xda-developers.com/showthread.php?t=1458876
Click to expand...
Click to collapse
Are you able to wipe cache from recovery? And what else errors are listed?
One more thing, try to flash your boot.img and system.img via fastboot as written above.
If I follow this
http://forum.xda-developers.com/showthread.php?t=1458876
and let it install cwm v 3, I get the cache error and cannot wipe or mount via recovery.
If I follow the ICS thread, and flash the new cwm v5 via fastboot, I don't get the cache error, but the rom simply won't start. If I open the package, there is a boot.img, but not a system.img, just a system folder...
I could try flashing boot.img, but I don't see how that could help
yellowumbrella said:
If I follow this
http://forum.xda-developers.com/showthread.php?t=1458876
and let it install cwm v 3, I get the cache error and cannot wipe or mount via recovery.
If I follow the ICS thread, and flash the new cwm v5 via fastboot, I don't get the cache error, but the rom simply won't start. If I open the package, there is a boot.img, but not a system.img, just a system folder...
I could try flashing boot.img, but I don't see how that could help
Click to expand...
Click to collapse
Well just to see it clear. So you are able to install Foliomod 1.4, so your Internal storage is not broken.
When I get home, I will check the system folder of ICS rom. There are some method to create system.img from an unpacked folder...
So, in CWM 5.5.0.4 you manage to install Zip from SD card, ROM and GAPPS as well, but the Rom does not boot?!
yup, that's exactly it.
Haven't tried installing Gapps since I can't even get the rom to boot.
I have a perfectly working tablet with foliomod 1.4, and I did get honeycomb to run but some apps crashed so I reverted back to foliomod.
with CWM CWM 5.5.0.4 everything seems to work great, except at reboot, nothing happens (somehow, I no longer even get the magic value mismatch)
------------------
PS. not sure if this is at all relevant, but I cannot fastboot from win7, I'm fastbooting in either ubuntu or xp via VirtualBox, and the device, when calling >fastboot devices shows up as ?????????? (ubuntu) and ? (xp)... :\
yellowumbrella said:
yup, that's exactly it.
Haven't tried installing Gapps since I can't even get the rom to boot.
I have a perfectly working tablet with foliomod 1.4, and I did get honeycomb to run but some apps crashed so I reverted back to foliomod.
with CWM CWM 5.5.0.4 everything seems to work great, except at reboot, nothing happens (somehow, I no longer even get the magic value mismatch)
------------------
PS. not sure if this is at all relevant, but I cannot fastboot from win7, I'm fastbooting in either ubuntu or xp via VirtualBox, and the device, when calling >fastboot devices shows up as ?????????? (ubuntu) and ? (xp)... :\
Click to expand...
Click to collapse
Try to install gapps as well. Maybe it helps...
nope, no luck even with gapps installed..
just a blank screen..
sigh
yellowumbrella said:
nope, no luck even with gapps installed..
just a blank screen..
sigh
Click to expand...
Click to collapse
Have you tried all the roms? ICS Alpha 1,2,3 and 4?
Tried 3 and 4, didn't bother trying earlier ones, as it seems the latest ones work for most users
yellowumbrella said:
nope, no luck even with gapps installed..
just a blank screen..
sigh
Click to expand...
Click to collapse
Hmmm strange. I ask it for you on developers forum. What you can still do, is to check the steps, that you did them correctly. In most of the cases users forget something, or do some steps incorrectly.
Try to erase userdata, cache, system, linux and recovery in fastboot. You mentioned you had problem with fastboot under Win7. Problem may occur, in case of not proper erasing.
Thanks, I'll give it another try tonight.
Fastboot in win7 is simply not seeing the device. It shows up in XP and Ubuntu, but as "??????" - not sure if that could be a symptom.
I'll post a reply as soon as I've tried, and let you know how it went.
yellowumbrella said:
Thanks, I'll give it another try tonight.
Fastboot in win7 is simply not seeing the device. It shows up in XP and Ubuntu, but as "??????" - not sure if that could be a symptom.
I'll post a reply as soon as I've tried, and let you know how it went.
Click to expand...
Click to collapse
For me it works perfectly on Win7. After Installing SDK and JDK the in the devicemanager it is shown as an Unknown device. Simply add the driver manually to it.
Download driver from attachment.
Copy it to SDK\USB_driver folder
That works for me. After its done, the Folio is shown as "Fastboot" in device manager. But connect the tablet in fastboot mode to your PC before you add driver manually to it.
Thanks for that.
Tried it, still not working in win7. It shows up correctly in device manager, but fastboot itself just doesn't want to see it...
I've attached a screenshot for you
EDIT: screenshot gets resized, but it shows device manager listing
NVIDIA Android Fastboot Device
and a terminal with fastboot not seeing the device
yellowumbrella said:
Thanks for that.
Tried it, still not working in win7. It shows up correctly in device manager, but fastboot itself just doesn't want to see it...
I've attached a screenshot for you
EDIT: screenshot gets resized, but it shows device manager listing
NVIDIA Android Fastboot Device
and a terminal with fastboot not seeing the device
Click to expand...
Click to collapse
When You have win7, You have run the console as admin!
Or copy the complete Fastboot folder to another Destination like c:\temp...
Thanks stefannsv, tried it, still not showing...
But I can access fastboot on another platform, so I assume it's not an issue, I can just switch over to another OS to flash
no go, followed both this original post (tried all steps except orange, cause the rom I'm trying to install has a system folder, not a system.img)
Last method I tried was:
1) boot into fastboot
2) boot cwm-recovery-5.5.0.4.img directly from PC
3) wipe data/factory reset
4) wipe cache partition
5) install zip from SD card and chose the alpha 4 release
installing update...
then back to recovery, reboot and voilà... magic value mismatch again (it had disappeared for a while... )
Also, when booting into CWM 3.0.0.5, I get a series of "E: Can't mount/cache/recovery" type errors.. could this be related?
booting directly into recovery from PC doesn't alllow me to install any ROMS, not even foliomod 1.4 which works if using puppet13th's method
Hey everyone,
This is my first time posting to the forums. I have been trying to get everything done without having to ask questions since there are so many all over the place and I can see how it can get tiring trying to help everyone when their may be an answer out there already if you look. However, I have ran into an issue that I can't seem to find much information on. I have the HTC Rezound that is S-On (apparently you need a Linux machine to get S-Off which I don't have. Using Windows 7.) and have been using fastboot to get things done. I have unlocked the bootloader and have installed the 'Amon Ra' recovery and setup Superuser and SU. As far as I know, I have to use ROM's that are S-On friendly (right?) and I chose to try out 'EclipticRez' and later 'Talon'.
As I tried to flash the ROM's through fastboot it fails with the following errors every time and I cannot continue:
archive does not contain android-info.txt
archive does not contain android-product.txt
From what I found is that it may be a bad download of the ROM. Maybe.... But it happened consecutively with two different ROM downloads.
I also read that maybe the recovery wasn't setup, which as far as I know it is. Should I use a different recovery? Everyone usually references to using CWM, which I wouldn't mind using but I couldn't figure out how to get SU access.
Can I just create the files myself? They are only txt files after all.
If anyone can help me with this I will be so grateful! I'm pretty new to this and it has definitely been a fun learning experience for me
Much thanks in advance!
Strikerz87 said:
Hey everyone,
This is my first time posting to the forums. I have been trying to get everything done without having to ask questions since there are so many all over the place and I can see how it can get tiring trying to help everyone when their may be an answer out there already if you look. However, I have ran into an issue that I can't seem to find much information on. I have the HTC Rezound that is S-On (apparently you need a Linux machine to get S-Off which I don't have. Using Windows 7.) and have been using fastboot to get things done. I have unlocked the bootloader and have installed the 'Amon Ra' recovery and setup Superuser and SU. As far as I know, I have to use ROM's that are S-On friendly (right?) and I chose to try out 'EclipticRez' and later 'Talon'.
As I tried to flash the ROM's through fastboot it fails with the following errors every time and I cannot continue:
archive does not contain android-info.txt
archive does not contain android-product.txt
From what I found is that it may be a bad download of the ROM. Maybe.... But it happened consecutively with two different ROM downloads.
I also read that maybe the recovery wasn't setup, which as far as I know it is. Should I use a different recovery? Everyone usually references to using CWM, which I wouldn't mind using but I couldn't figure out how to get SU access.
Can I just create the files myself? They are only txt files after all.
If anyone can help me with this I will be so grateful! I'm pretty new to this and it has definitely been a fun learning experience for me
Much thanks in advance!
Click to expand...
Click to collapse
1) Switch to TWRP or CWM for your recovery.
2) You install the rom zip via recovery.
3) You then need to fastboot flash the kernel from the rom zip you downloaded. You don't install the whole rom via fastboot.
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom. Using these steps, you can install any rom you want.
Strikerz87 said:
Hey everyone,
This is my first time posting to the forums. I have been trying to get everything done without having to ask questions since there are so many all over the place and I can see how it can get tiring trying to help everyone when their may be an answer out there already if you look. However, I have ran into an issue that I can't seem to find much information on. I have the HTC Rezound that is S-On (apparently you need a Linux machine to get S-Off which I don't have. Using Windows 7.) and have been using fastboot to get things done. I have unlocked the bootloader and have installed the 'Amon Ra' recovery and setup Superuser and SU. As far as I know, I have to use ROM's that are S-On friendly (right?) and I chose to try out 'EclipticRez' and later 'Talon'.
As I tried to flash the ROM's through fastboot it fails with the following errors every time and I cannot continue:
archive does not contain android-info.txt
archive does not contain android-product.txt
From what I found is that it may be a bad download of the ROM. Maybe.... But it happened consecutively with two different ROM downloads.
I also read that maybe the recovery wasn't setup, which as far as I know it is. Should I use a different recovery? Everyone usually references to using CWM, which I wouldn't mind using but I couldn't figure out how to get SU access.
Can I just create the files myself? They are only txt files after all.
If anyone can help me with this I will be so grateful! I'm pretty new to this and it has definitely been a fun learning experience for me
Much thanks in advance!
Click to expand...
Click to collapse
also to note....you dont have to install linux to get s-off....if you follow my guide you can do it straight from a live disk rather than installing it....so it wont erase or mess up your windows partition at all
Solved!
Thank you, Mjones, I finally got it! I knew it was much easier than I was making it out to be. I was missing the kernel! Yeah, a crucial part in the process, I know
I first ran CWM and flashed the ROM over and ran the .zip through recovery (which I couldn't understand at first as I could never find it in the directory) but the installer would only go 50% and would fail... makes sense why now lol
I later flashed TWRP and backed up again after recovering from the fail. I flashed over the kernel and voila! So simple... Had to slap myself.
Thanks again! Case solved.
REV3NT3CH, that is sweet!! I have been hoping there is a way to gain s-off with Windows. I have 7 at work and 8.1 (which I can't get anything to work on) at home. I actually have to focus on work today haha so I'll look into the method and try it out tomorrow if I can. Thanks for all of the help.
mjones73 said:
1) Switch to TWRP or CWM for your recovery.
2) You install the rom zip via recovery.
3) You then need to fastboot flash the kernel from the rom zip you downloaded. You don't install the whole rom via fastboot.
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom. Using these steps, you can install any rom you want.
Click to expand...
Click to collapse
Thank You So much, Mine case also Resolved. I was too frustated sice last 3 days cause my phone was in dead mode. At the end, fastboot flash boot boot.img Worked. ThankYOu
mjones73 said:
1) Switch to TWRP or CWM for your recovery.
2) You install the rom zip via recovery.
3) You then need to fastboot flash the kernel from the rom zip you downloaded. You don't install the whole rom via fastboot.
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom. Using these steps, you can install any rom you want.
Click to expand...
Click to collapse
I need to be able to do it via fastboot, as my Motorola Electrify M is stuck in a bootloop and there's no way I could find to boot into recovery. I'm using ./fastboot update name_of_update.zip and it is an official OTA .zip but I still get this error. Any suggestions?
ecols33 said:
I need to be able to do it via fastboot, as my Motorola Electrify M is stuck in a bootloop and there's no way I could find to boot into recovery. I'm using ./fastboot update name_of_update.zip and it is an official OTA .zip but I still get this error. Any suggestions?
Click to expand...
Click to collapse
Sorry, don't know anything about that phone.
ecols33 said:
I need to be able to do it via fastboot, as my Motorola Electrify M is stuck in a bootloop and there's no way I could find to boot into recovery. I'm using ./fastboot update name_of_update.zip and it is an official OTA .zip but I still get this error. Any suggestions?
Click to expand...
Click to collapse
Did you try this first? (Right from Moto's site)
Perform a factory reset using external keys
1. Power off the phone, press and hold volume down button, press power button
2. Screen will come up with "Fastboot", press Vol down key to cycle through choices until you get "Android Recovery", then press Vol up key
3. Wait for the "triangle ! / Android" screen then go on to step 4
4. Press both Vol up and Vol down key simultaneously. A menu will come up
5. Tap on Vol down key until "wipe data/factory reset" is highlighted, and tap Power key. Another Confirmation screen will come. Tap on Vol down key until coming to Yes and tap Power key
6. After userdata is cleared, the "reboot system now" option will be highlighted by Default. Tap Power key
7. Phone will reboot to initial setup screen.
PLEASE HELP! I have a Huawei P8 and I tried to update to android 6.0 (GRA-L09xxxxxxxxxxxB317 or something) Went to install it and now im stuck in bootloop (a very annoying one, I can rarely get into eRecovery and eRecovery is not able to fix my problem: "Getting package info failed") so I went into fastboot&rescue mode and I did the flash thing via my PC (that Fastboot flash boot boot.img etc.) but I get this error saying: "FAILED (remote: Command not allowed)" for any image im trying to flash. My fastboot/bootloader or whatever it's called is locked my android is unrooted and stock android. I don't know how to unlock it I can't find anything anywhere.. HELP ME
not working
hariom.gupta11 said:
Thank You So much, Mine case also Resolved. I was too frustated sice last 3 days cause my phone was in dead mode. At the end, fastboot flash boot boot.img Worked. ThankYOu
Click to expand...
Click to collapse
not working on my 4c. write successful but when reboot is completed it goes to previous state.
"the user data partition can no longer be used"
zb602kl_x00tdb
L0RDZ3RO said:
PLEASE HELP! I have a Huawei P8 and I tried to update to android 6.0 (GRA-L09xxxxxxxxxxxB317 or something) Went to install it and now im stuck in bootloop (a very annoying one, I can rarely get into eRecovery and eRecovery is not able to fix my problem: "Getting package info failed") so I went into fastboot&rescue mode and I did the flash thing via my PC (that Fastboot flash boot boot.img etc.) but I get this error saying: "FAILED (remote: Command not allowed)" for any image im trying to flash. My fastboot/bootloader or whatever it's called is locked my android is unrooted and stock android. I don't know how to unlock it I can't find anything anywhere.. HELP ME
Click to expand...
Click to collapse
I have same problem on asus zenfone max pro m1 I bought it online said used and now working
can't boot into recovery.
can't boot into system.
Only EDL Mode and Fastboot Mode, but fastboot is Locked whic I cant unlock because I cannot boot into system to toggle USB Debugging and allow OEM unlocking
Qualcomm is harder to flash than MTK that can use SP FlashTool.
on this I use QFIL but keeps "sahara error". I tried searching and try moving firmware file to bin but no Luck. I'm currently trying different version of QFIL Tool.
If it FAILS my only HOPE is to use MUT-QCfire which will Require a "SmartCardReader" Which is a bit pricey and I don't even know if it will work on my device.
Hi all,
Just followed the instructions below to get a new rom on my TF201.
Now I have Teamwin recovery booting showing V2.6.3.0 and asking for a password.
Teamwin does not show data in external or internal sdcards.
I am unable to get into fastboot mode, using power and vol down.
It has failed since running this line fastboot -i 0x0b05 flash recovery ne0zone75_tf300t.blob
I have all of the nvflash blobs etc.
Any ideas how to recover from this point?
Thanks
RR
This may help
Starting from a stock bootloader V 10.4.2.18
What you will need
Woking fastboot & adb / SDcard optional
TWRP for a 201 = twrp_tf201t.blob
@ne0zone75 TWRP for the 300 = ne0zone75_tf300t.blob
HairyBean BL & TWRP: This is effectively turn your 201 into a 300 <---- which is a flashable zip inside the zip that you downloasd
All 3 of the above file are in a zip in the Download section @ the top of every page of the thread ...... THIS ZIP IS NOT FLASHABLE...Your must unzip it to get to the real files !!! The name of this zip is 'upgrade_tf201_to_tf300t.zip'
CROMBI 201 ROM zip
A fully charged tablet
All the above files in the same directory as your fastboot.exe (if using windows) In your home folder on linux....
The process
Lets start with the TWRP recovery for the 201, let flash it with fastboot...
Power your tablet off and with the [ VOL DOWN & POWER ] buttons boot the tablet into the bootloader
Once there [ VOL DOWN ] untill the green box is on the USB ICON then [ VOL UP ] to select fastboot
Let make sure your PC can see your tablet with this command.
Code:
fastboot devices
Code:
fastboot -i 0x0b05 flash recovery twrp_tf201t.blob
Then
Code:
fastboot -i 0x0b05 reboot-bootloader
[ VOL UP ] ON RCK to enter recovery
Once in TWRP check to see if adb is working...
Code:
adb devices
Ok now that we know that is working let go ahead and push the HairyBean BL onto the tablet
Code:
adb push HairyBean_Bootloader_TWRP2.5.zip /sdcard
Now under the install tab in TWRP fine the folder and flash it....
reboot once it has fishined..If ask to install SuperUser say NO..........
LET THE BLUE BAR FILL !!!!!!!!! Once it has finished it will reboot into Hairybean TWRP....
Once booted into recovery, run this command to boot into fastboot
Code:
adb reboot-bootloader
You will see that the USB icon is missing now, this is good... If you still see the USB icon DON'T go to the next step
Now lets flash @ne0zone75 TWRP recovery
Code:
fastboot -i 0x0b05 flash recovery ne0zone75_tf300t.blob
Once that has finished let reboot into bootloader
Code:
fastboot -i 0x0b05 reboot-bootloader
Now enter recovery....
Make sure its verison 2.7.1.0
Go to Wipe////Format Data////Type yes
This can take up to 90 mins to format
DO NOT INTERRUPT THE FORMAT !!!!!!!
Now lets push CROMBI-KK onto your tab
Code:
adb push cm-11.0-2014xxxx-crombi-kk-tf201t.zip /sdcard
Find it under the install tab and flash it..
REBOOT into android, first boot can take up to 15 minutes
ADB interface working
Ok, lots of playing this morning tells me that the adb interface is working when the teamwin recovery is showing.
adb devices gives <number> recovery
Any ideas how to proceed from here, apart from carefully
RangeyRover1 said:
Ok, lots of playing this morning tells me that the adb interface is working when the teamwin recovery is showing.
adb devices gives <number> recovery
Any ideas how to proceed from here, apart from carefully
Click to expand...
Click to collapse
When on the twrp screen .....
Does the command .....
Code:
adb reboot-bootloader
Do anything ??
Thx Josh
Hello I was having a tough time trying to Flash Crombi KK rom. At 1 point I had to use a recovery blob because I was stuck. I started from there upgraded bootloader and twrp 2.5. Flashed twrp 2.8 and Crombi KK rom kept showing fail. I eventually gave up and tried to go from 2.8 TWRP back to 2.5 with JB Bootloader. Bad move I know. Whenever I pressed up to go to recovery it would get stuck. Then eventually I tried wiping data from Bootloader screen. Now the 3 options, recovery, coldboot and wipe data wont show. Stuck at Asus screen "The Device is Unlocked".
I downloaded naked drivers and android ADB drivers.. however I cannot get them to install on windows 7. I'd appreciate any help to try to this back running again
Lyvewire said:
Hello I was having a tough time trying to Flash Crombi KK rom. At 1 point I had to use a recovery blob because I was stuck. I started from there upgraded bootloader and twrp 2.5. Flashed twrp 2.8 and Crombi KK rom kept showing fail. I eventually gave up and tried to go from 2.8 TWRP back to 2.5 with JB Bootloader. Bad move I know. Whenever I pressed up to go to recovery it would get stuck. Then eventually I tried wiping data from Bootloader screen. Now the 3 options, recovery, coldboot and wipe data wont show. Stuck at Asus screen "The Device is Unlocked".
I downloaded naked drivers and android ADB drivers.. however I cannot get them to install on windows 7. I'd appreciate any help to try to this back running again
Click to expand...
Click to collapse
Do you have your nvflash blobs backed up ?
Thx Josh
lj50036 said:
Do you have your nvflash blobs backed up ?
Thx Josh
Click to expand...
Click to collapse
No blobs. I 've had this device since day one. Rooted it, bricked before but never this. I remember having a hard time making a NVFlashbackup for the same reason of my device showing up and eventually gave up. Any other suggestions?
Lyvewire said:
No blobs. I 've had this device since day one. Rooted it, bricked before but never this. I remember having a hard time making a NVFlashbackup for the same reason of my device showing up and eventually gave up. Any other suggestions?
Click to expand...
Click to collapse
No nvflash blob, no fastboot, no adb ....
There is nothing that can be done if the above statement is true ......
Thx Josh
lj50036 said:
No nvflash blob, no fastboot, no adb ....
There is nothing that can be done if the above statement is true ......
Thx Josh
Click to expand...
Click to collapse
Thanks for replying
I tried using this http://forum.xda-developers.com/showthread.php?t=2588979 to install ADB. It got to waiting for device and of course nothing. Is there something else needed to get the ADB to read the device? I downloaded the naked drivers as well but nothing showed up in device manager. No executable file to run. Am I missing something?
WooHoo
lj50036 said:
When on the twrp screen .....
Does the command .....
Code:
adb reboot-bootloader
Do anything ??
Thx Josh
Click to expand...
Click to collapse
Why, yes. yes it does Thanks.
Ok I have the RCK, Android,wipe data icons.
fastboot devices on this screen now gives <number> fastboot
Woot!
I'm keen to have specific instructions on how to recover from this point back to stock, then take a deep breath and try to get to custom.
My concern is that a lot of the threads with guidance for recovery and flashing are old, and I don't want to brick this thing.
So, is there a thread for recovery to stock from this point?
I have found this thread discussing recovery. http://forum.xda-developers.com/transformer-prime/help/guide-t2864946
am waiting for full charge of tablet at the moment.
Thanks for all the help so far.
RR
RangeyRover1 said:
Why, yes. yes it does Thanks.
Ok I have the RCK, Android,wipe data icons.
fastboot devices on this screen now gives <number> fastboot
Woot!
I'm keen to have specific instructions on how to recover from this point back to stock, then take a deep breath and try to get to custom.
My concern is that a lot of the threads with guidance for recovery and flashing are old, and I don't want to brick this thing.
So, is there a thread for recovery to stock from this point?
Thanks for all the help so far.
RR
Click to expand...
Click to collapse
You need the blob from the stock frimware downloaded from the Asus website ....
It will be in a zip file that needs unzipped twice ...... Make sure you get the correct 'SKU' for your tablet ......
Then follow this guide, skip to the first fastboot command and go from there .....
http://forum.xda-developers.com/showthread.php?t=2538028
Thx Josh
FIXED
lj50036 said:
You need the blob from the stock frimware downloaded from the Asus website ....
It will be in a zip file that needs unzipped twice ...... Make sure you get the correct 'SKU' for your tablet ......
Then follow this guide, skip to the first fastboot command and go from there .....
http://forum.xda-developers.com/showthread.php?t=2538028
Thx Josh
Click to expand...
Click to collapse
Thanks, thats got me back to square one.
Maybe a new thread detailing the pain to get to Custom rom!
Cheers Josh.
RR
tf300 update required?
Ok, i seem to be failing when i apply neowin tf300 update, when following the crombikk instructions on post #4. The system does not now boot into recovery. Is this step absolutely required for the newer roms?
Thanks
RR