Related
I read in the bootloader development thread that it'd reached a level where it could almost boot into a custom system image stored on the SD card. Some questions about that:
1. The creation of that image, is it similar to how it's done for use with the XDAndroid project? (The porting of Android to HTC WinMo devices)
2. Is there a way to avoid having to reflash the device after every attempt? It looks like the boot-scripts take control pretty early in the process so having a choice if you want to proceed would be awesome, especially since I can't figure out how to get hold of a bootlog.
Thanks
ddewbofh said:
1. The creation of that image, is it similar to how it's done for use with the XDAndroid project? (The porting of Android to HTC WinMo devices)
Click to expand...
Click to collapse
I have no clue how they do it for XDAndroid, but here's how I created mine:
dd if=/dev/zero of=rootfs.ext2 bs=1M count=512 (for 512Mb fixed size)
mkfs.ext2 rootfs.ext2 (press y to accept)
mount somewhere
copy your stuff into
umount
ddewbofh said:
2. Is there a way to avoid having to reflash the device after every attempt? It looks like the boot-scripts take control pretty early in the process so having a choice if you want to proceed would be awesome, especially since I can't figure out how to get hold of a bootlog.
Click to expand...
Click to collapse
You don't need to re/flash at all. Pressing any key during the bootup will cancel the script and get you back into old good SE's 1.6
zdzihu said:
You don't need to re/flash at all. Pressing any key during the bootup will cancel the script and get you back into old good SE's 1.6
Click to expand...
Click to collapse
I've tried hammering all the keys without any success, since it works for you maybe I'm doing it at the wrong time. Where in the boot process do you do it?
And thanks for the tip about the image, didn't want to risk messing something up since I had to reflash after every try.
ddewbofh said:
I've tried hammering all the keys without any success, since it works for you maybe I'm doing it at the wrong time. Where in the boot process do you do it?
Click to expand...
Click to collapse
Bash them for a while as soon as you see SE logo appearing
ddewbofh said:
And thanks for the tip about the image, didn't want to risk messing something up since I had to reflash after every try.
Click to expand...
Click to collapse
Make sure you either name your image rootfs.img (not .ext2) or edit the init in the ramdisk accordingly.
Cheers
Thanks, that should make things much, much easier.
zdzihu said:
I have no clue how they do it for XDAndroid, but here's how I created mine:
dd if=/dev/zero of=rootfs.ext2 bs=1M count=512 (for 512Mb fixed size)
mkfs.ext2 rootfs.ext2 (press y to accept)
mount somewhere
copy your stuff into
umount
You don't need to re/flash at all. Pressing any key during the bootup will cancel the script and get you back into old good SE's 1.6
Click to expand...
Click to collapse
is there different form flash?
I've figured out why my phone refuses to go back to normal after testing the chroot. It needs grep and the standard sh doesn't provide it nor is there a grep symlink/binary in /system/bin so I'll add those manually.
Anyways, if anyone has a script or something to do all this it would be very helpful. I'm not looking forward to going over tons of symlinks manually.
ddewbofh said:
I've figured out why my phone refuses to go back to normal after testing the chroot. It needs grep and the standard sh doesn't provide it nor is there a grep symlink/binary in /system/bin so I'll add those manually.
Anyways, if anyone has a script or something to do all this it would be very helpful. I'm not looking forward to going over tons of symlinks manually.
Click to expand...
Click to collapse
How about busybox --install -s /your_destination_dir ?
zdzihu said:
How about busybox --install -s /your_destination_dir ?
Click to expand...
Click to collapse
Awesome, thanks. My knowledge about busybox is limited at best so when I saw install listed as a busybox function I assumed it was the "normal" install command.
In the quest for finding a way to use custom kernels I'm playing around with the splboot module but I need to find a way to get hold of dmesg or kmsg from failed attempts. Is there a reliable way to get any of these logs?
I've tried adding a line in the mount_iso script which cats kmsg to a file right before executing the splboot but I'm seeing nothing that would indicate that I'm running anything but the stock kernel.
Any ideas?
Hi there, i was trying to run Debian on my pro, but i cant install it! i try two methods, the Linux installer Beta 1.7 (say kernel dosnt have ext and loop support) and the SU terminal emulator way (cant chmod to 4755 any file, even using the su command - from here: http://www.talkandroid.com/android-forums/android-development/1091-install-debian-android.html )...
My pro is ROOTED with latest z4root, i even do a factory repair with pc companion...
Any advice???
Regards!
I tried this as well... no loop is no loop ( required for chroot type runs )
works on a Samsung i5700 I have at work tho...
thnx for the reply, so i can add loop and the ext thing? or we need a custom kernel? , what rom have the samsung?, in other hand i dont know why i cant chmod the files, even using root explorer! regards...
needs a new kernel yes.
i5700 is running samdroid cooked ( forget which version, but added multitouch )
damn :/
now why i cant chmod the files using su terminal emulator or root explorer? maybe is because my sdcard is formated in fat32, regards!
fat32 knows nothing about *nix style permissions, in a way though... all files on a fat32 are set 0777, but not really... heh
For what it's worth, I've just had Debian running in a chroot on my X10 Mini Pro, using the instructions at talkandroid.com, as mentioned by the original poster. Sorry, but as a new poster, I'm not allowed to link directly to those directions. This is with stock ROM, upgraded to Android 2.1, rooted with SuperOneClick.
A few modifications are necessary to make it work. I'm going to try to describe what I've done, but I am working backwards, so it's entirely possible that I'll leave something out and you could suffer disastrous consequences. So please be sure you back up all crucial data before proceeding, and be prepared to accept the possibility that your phone could be destroyed in the process.
First of all, the instructions tell you to run scripts from your SD card, which isn't going to work unless the card has a partition with a Linux-compatible file system. I suggest following the directions as far as step 4. Then replace the "bootdeb" file in the "debian" directory with the modified version attached to this post. Rename it "bootdeb". Then you will have to run the following commands manually, preferably using adb shell, but it can be done in a terminal on the phone. Either way, using the ash shell helps by providing command completion and history.
As root (su):
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock0 /system
mkdir /data/local/mnt
cd /sdcard/debian
cp bootdeb /data/local/bin #note: you may need to mkdir /data/local/bin first
cd /data/local/bin/
chmod 4777 bootdeb
You should now be able to run the bootdeb script to start up Debian.
The installation file says, "Be sure to run /scripts/onetime.sh as root from the shell after your FIRST 'boot'." This will prompt you to set a root password.
At this point, the Debian installation is command line only and root only. The image file needs to be resized before much can be added.
The other files in the Debian directory may be useful, but they all need to be modified before they can be used.
This is only a beginning. I don't know that I'm likely to get very far with it, so anyone else who's inclined to jump in and make this work better is welcome to do so!
edit: correcting grammatical error
Just in case anyone else shares my obsession -- I mean interest in getting Debian to run on an X10 Mini Pro, I thought I should report my progress. Or lack thereof.
Actually, as I said in the previous post, command line Debian works, and that's a lot of power to have available. But it would be nice to get X working, despite the lack of video drivers.
There's a lot of information out there about setting up X with a VNC server on an Android phone, then running a VNC client to access the graphic environment. The source of most accounts seems to be a thread at the androidfanatic forums, with the title "Gnome, KDE, IceWM or LXDE Desktop on your Android!"
(Sorry, I'm still too new at this to be allowed to post links, so this is the only way I can indicate where to find the information.)
I've tried lots of variations on those directions, trying to adapt them to the X10 Mini Pro. And I've had a little success. I can get to the Icewm or LXDE desktop and run the terminal program, but I can't start any programs that use X. Invariably, I get this error:
Error: Can't open display: :1.0
I've run out of ideas, so I'm taking a break from the project. If anyone else is interested enough to try, good luck to you!
For what it's worth, the most recent and comprehensive account of running Debian with X on Android phones appears to be at lanrat.com, in the "android" directory, filename "debian".
@RobbH
Very interesting! I'm waiting a new 8gb card so that I try it! Should you come up with any new progress please report here
Original message> Hi guys,
does anybody knows how to restore folio and take it back to life?
My son played with my tablet and he messed something.
Now I have bricked tablet, black screen, no toshiba logo after turn on, nothing just green led :/
Only thing working is when I connect usb cable to pc, It connect as ATX.
I found some threads but they are so complicated
Can somebody help me and write for me restoration guide for dummies?
Edit: Does anybody have full dumps? I need bootloader, bct for start.
EDIT> I will pay 30 EUR to Who will help me to restore my dead tablet.
I need all dumps, bootloader, bct and short batch file for nvflash.
On what partition is bootloader? I can dump it but I don't know on what partition it is and I know a very little about nvflash.
Jon2555 said:
On what partition is bootloader? I can dump it but I don't know on what partition it is and I know a very little about nvflash.
Click to expand...
Click to collapse
I think bootloader is in ../prebuilt/bootloader.bin
I found good restore guide:
Backing Up
Download the latest Linux For Tegra (L4T) package from here and unzip it
Open a terminal and change to the following directory: linux4tegra/nvflash
the following command sends the vanilla bootloader into your device RAM (it will not overwrite anything)
# LD_LIBRARY_PATH=. ./nvflash --bl ../prebuilt/fastboot.stock.bin --go
the following command saves your disk partitioning (very important!)
# LD_LIBRARY_PATH=. ./nvflash -r --getpartitiontable partitiontable.txt
use the following command with to save the partitions one by one to your harddisk (see Partition Layout for details)
# for i in $(seq 2 14); do LD_LIBRARY_PATH=. ./nvflash -r --read $i part-$i.img; done
You should endup with part-2.img, part-3.img [...] up to part-14.img, and partitiontable.txt.
Keep them in a safe place if you intend to play a bit with your AC100.
Restoring
In the partitiontable.txt, you should see following pattern (you need the highlighted values for each partition you want to restore):
PartitionId=[PartitionId]
Name=...
DeviceId=18
StartSector=[StartSector]
NumSectors=[NumSectors]
BytesPerSector=2048
Open a terminal and change to the following directory: linux4tegra/nvflash
Reload the vanilla bootloader using the following command:
# LD_LIBRARY_PATH=. ./nvflash --bl fastboot.bin --go
For earch part-[PartitionId].img you want to restore, execute the following command:
# LD_LIBRARY_PATH=. ./nvflash -r --rawdevicewrite [StartSector] [NumSectors] part-[PartitionId].img
Reboot your device.
Do you manage to get folio to life?
cmjm said:
Do you manage to get folio to life?
Click to expand...
Click to collapse
not yet because I don`t have correct dumps and bootloader :/ so I am waiting for someone who dump me this and prepare script for nvflash.
I heared that bootloader.bin is in .../prebuilt but where is it???
Sent from my IDEOS S7 Slim using XDA App
ok, thank you.
Let's see if someone can do that for us.
you have installed the drivers apx.
Someone to help us.
I want and I asked where is the bootloder???
Sent from my Xoom using Tapatalk
In my I can no longer view, I'll try to search the web.
I can not find it. funny find several people who says that had solved the problem but no one is able to help.
yeah, I am also curious where is bootloader. There are two ways where can it be:
in partition 0 or 1 or somewhere in file tree. I don`t know :/
btw I have RMA this tablet and will get new from them. After that I could try to dump it.
this is good news.
I've tried everything and still nothing.
Gives news when you can.
I searched a bit in android git and find that prebuilt is in source code that Toshiba didn't release, only kernel... Only hope is dumping.
Sent from my IDEOS S7 Slim using XDA App
Any news??
cmjm said:
Any news??
Click to expand...
Click to collapse
finally I`ve give up. After RMA I received for small repay toshiba thrive so I don`t need dump anymore.
Thank you guys for all.
Is there a Solution?
How much do you have to pay?
I sent it to Toshiba and they have repair it for free.
Sent from my Desire HD using XDA App
Hello guys, i have a question here, i bought this tablet from Focalprice:
http://www.focalprice.com/CE0427B/Y...PX820_Dualcore_12GHz_Tablet_PC_with_WiFi.html
This tablet have the same specs of the Ippo Y88, BUT Y88 have 1.5ghz and mine have 1.2ghz, they use the SAME dualcore A5 processor, IMAPX820.
Well, i search on google, and use the tool here on XDA to find some information, but its impossible to find anything about this processor, and those tablets... I know they are simple tablets, but someone know if i can ROOT this thing using CWM and put some light ROM, or Cymod?
Thnaks for help, this forum is the best, and i love the Galaxy S3 forum!
This proc is new, or have some other name?
up
up.
too cheap to be rooted? xD
p_morales said:
up.
too cheap to be rooted? xD
Click to expand...
Click to collapse
Hehe, idk maybe this tablet is not so good, so none develop for it. ;x
p_morales said:
up.
too cheap to be rooted? xD
Click to expand...
Click to collapse
How is your answer supposed to help anybody? People buy cheap tablets for a lot of reasons, I bought this to use it for a home automation system and it's perfectly fit for this purpose.
I'm also interested in rooting it, so any information ( ROMs , ideas on how to root it or how to make a ROM dump without root, etc) would be much appreciated.
crwro said:
How is your answer supposed to help anybody? People buy cheap tablets for a lot of reasons, I bought this to use it for a home automation system and it's perfectly fit for this purpose.
I'm also interested in rooting it, so any information ( ROMs , ideas on how to root it or how to make a ROM dump without root, etc) would be much appreciated.
Click to expand...
Click to collapse
My answer helps as yours. I only wanted to say that Aldighieri is not the only person looking for a way to root it.
Maybe nobody will develop a rooting method for this kind of tablets, but there could be an existing method that works ¿isnt it? hope so.
Thanks all of u!
Calm down boys, hehe!
So, none know a way? Is impossible to root this thing? =/
Aldighieri said:
Calm down boys, hehe!
So, none know a way? Is impossible to root this thing? =/
Click to expand...
Click to collapse
If you or somebody else can provide/find the original ROM I might be able to root it. I'm not an expert but I've managed to root an "unrootable" android tv box once. I've asked the guys at focalprice for the ROM but they didn't answer my email and I don't have too much hope given their awful customer service.
Oh thanks! Ill try to find it with someone on ebay, or google, if i find it i tell you! Thanks! )
Same problem for me. Excelent tablet, bu timpossible to root. When I try (with different methods: unlockroot,z4root, superoneclick, root bin4ay, rootx...) a massage say that is rooted, but when I try to install Superuser don't work for me. Please, help!
I asked for sellers on ebay to try to find the rom with the providers, but have no awnser yet, if u can, try it too! ^^
Me too on focal price. If i know something, I will post about it. Is very a rare case...
Thanks.
Aldighieri said:
I asked for sellers on ebay to try to find the rom with the providers, but have no awnser yet, if u can, try it too! ^^
Click to expand...
Click to collapse
elefantino9 said:
Me too on focal price. If i know something, I will post about it. Is very a rare case...
Thanks.
Click to expand...
Click to collapse
Nice! Thanks!
Still no answer from focalprice on my side and I think the best chance to find the ROM is via ebay sellers. I've tried a few methods of rooting the tablet without any luck and I came to the conclusion (with my limited knowledge) that the problem is related to the file system the ROM is packed, which doesn't allow changing file permissions. I can't go further without risking bricking my tablet, but if we find the original ROM I may be able to unpack /repack it, changing the permissions in the process. It may be a long shot but it's worth a try.
Thanks everybody for your efforts!
Fast response from focalprice: a word file with how to use this tablet: on, off, mute, how listen to the music...wow!
IF you find the rom ok, but you can't use it because the recovery is not present on this tablet. If you can do somethins, please, post it.
Thanks :good:
crwro said:
Still no answer from focalprice on my side and I think the best chance to find the ROM is via ebay sellers. I've tried a few methods of rooting the tablet without any luck and I came to the conclusion (with my limited knowledge) that the problem is related to the file system the ROM is packed, which doesn't allow changing file permissions. I can't go further without risking bricking my tablet, but if we find the original ROM I may be able to unpack /repack it, changing the permissions in the process. It may be a long shot but it's worth a try.
Thanks everybody for your efforts!
Click to expand...
Click to collapse
Hello friends!
I'm completly frustated. Google is burned with my researches. I have found this video and I think that is our tablet, but this combination don't work for me. Any idea?
Thank you for the info. I've tried the method in the video and it doesn't work on my tablet either, so probably we have a different model. Even if there is no recovery mode as the guys from focalprice say, I am sure that the ROM can be updated/reinstalled somehow, via usb maybe?
I'll keep trying to make a ROM dump from my tablet and I'll post here if I succeed.
Aldighieri said:
Hello guys, i have a question here, i bought this tablet from Focalprice:
http://www.focalprice.com/CE0427B/Y...PX820_Dualcore_12GHz_Tablet_PC_with_WiFi.html
This tablet have the same specs of the Ippo Y88, BUT Y88 have 1.5ghz and mine have 1.2ghz, they use the SAME dualcore A5 processor, IMAPX820.
Well, i search on google, and use the tool here on XDA to find some information, but its impossible to find anything about this processor, and those tablets... I know they are simple tablets, but someone know if i can ROOT this thing using CWM and put some light ROM, or Cymod?
Thnaks for help, this forum is the best, and i love the Galaxy S3 forum!
Click to expand...
Click to collapse
Okay, I found a way to root it, but its on different device (Infotmic GF20). Firstly you have to enter recovery mode with adb (adb reboot recovery), then disconnect and reconnect usb cable, enter adb shell. If you have # as prompt, you can continue - it will work on your device too - if not, you have to obtain firmware from seller to root it. If you have #, type
Code:
ubiattach -m 1
busybox mount -tubifs /dev/ubi0_0 /system
Then exit adb shell, get su binaries and supersu app, and pull them to the device:
Code:
adb push su /system/xbin/
adb shell chown 0.0 /system/xbin/su
adb shell chmod 6755 /system/xbin/su
adb shell ln /system/xbin/su /system/bin/su
adb shell chown 0.0 /system/bin/su
adb shell chmod 6755 /system/bin/su
adb shell push supersu.apk /system/app/
Reboot device and it should work
OMG! Incredible!
My problem is the seller: they don't have the firmware, but I will try to understand all the process and I will try.
Thanks, thanks and thanks
lolet said:
Okay, I found a way to root it, but its on different device (Infotmic GF20). Firstly you have to enter recovery mode with adb (adb reboot recovery), then disconnect and reconnect usb cable, enter adb shell. If you have # as prompt, you can continue - it will work on your device too - if not, you have to obtain firmware from seller to root it. If you have #, type
Code:
ubiattach -m 1
busybox mount -tubifs /dev/ubi0_0 /system
Then exit adb shell, get su binaries and supersu app, and pull them to the device:
Code:
adb push su /system/xbin/
adb shell chown 0.0 /system/xbin/su
adb shell chmod 6755 /system/xbin/su
adb shell ln /system/xbin/su /system/bin/su
adb shell chown 0.0 /system/bin/su
adb shell chmod 6755 /system/bin/su
adb shell push supersu.apk /system/app/
Reboot device and it should work
Click to expand...
Click to collapse
Don't works for me. I can see the recovery (thanks), but when I unplug and plug the device, windows (xp) don't recognize the tablet. I use the Universal ADB drivers https://github.com/koush/UniversalAdbDriver, but I think that are the correct drivers. Any idea? Thanks! :good:
Here we have the solition, but I don't understand the recovery mode driver installation...
Hello,
I've just received new phone, Alcatel One Touch Fire E (6015X).
This phone has got installed FirefoxOS,
my question is can I install android somehow?
I was looking for that information however not found anything what would help me.
kmlnvm said:
Hello,
I've just received new phone, Alcatel One Touch Fire E (6015X).
This phone has got installed FirefoxOS,
my question is can I install android somehow?
I was looking for that information however not found anything what would help me.
Click to expand...
Click to collapse
Hello,
I'm looking for a recovery image of this phone, do you know of any location to find one? Or could you possibly make one very please to help such people out? Hamachi (Flame) builds dont work.
uxuxux said:
Hello,
I'm looking for a recovery image of this phone, do you know of any location to find one? Or could you possibly make one very please to help such people out? Hamachi (Flame) builds dont work.
Click to expand...
Click to collapse
if you could tell me how to extract it from my phone, i can make it for you
jecustoms said:
if you could tell me how to extract it from my phone, i can make it for you
Click to expand...
Click to collapse
Hey, thanks for your offer. I found a guide for the Alcatel Flame, but I think we are interested in Step 5 only.
Code:
Step 5: Create backup images
Now start shell on the phone using adb shell command and dump backup images to SD card:
$ cat /dev/mtd/mtd0 >/mnt/sdcard/boot.img
$ cat /dev/mtd/mtd1 >/mnt/sdcard/system.img
$ cat /dev/mtd/mtd5 >/mnt/sdcard/userdata.img
$ cat /dev/mtd/mtd7 >/mnt/sdcard/recovery.img
When finished (you may also dump some more MTD partitions if you like), transfer those files to your computer. You may again use ADB for that:
$ mkdir hamachi-backup
$ I="boot.img system.img userdata.img recovery.img"
$ for i in $I; do adb pull /mnt/sdcard/$i hamachi-backup/; done
I can't link yet but it's from Krzysztof Adamski's blog, the full post is titled Alcatel One Touch Fire Hacking (Mini)Guide.
Maybe it would be enough, as the alcatel source for this device is not available yet on their sourceforge page, I'm not sure if it's possible to make a full recovery image without that.
I found another mention of such thing on the b2g-dev mail list
Code:
> You can backup the partitions from a working phone using 'dd' to dump
> them (you can find the relevant devices under /dev/block) and then use
> fastboot to flash them on the bricked phone (provided that fastboot
> still works).
first of all, i am a total noob..
"Now start shell on the phone using adb shell command"
what does it mean? how can start it?