Q&A for [Kernel] [12/1] FIRE-ICE [R14]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Kernel] [12/1] FIRE-ICE [R14]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
flashed ok on new factory image
5.0.1 stock / flashed cf autoroot/flashify/twrp ... flashed your rom/su/gapps/ set up the tablet and then flashed fire/ice. Tablet seems smooth and zippy . also of note previous to flashing your rom I also flashed the new factory image unencrypted if that matters. Thanks for your efforts on the rom.
fazbender said:
5.0.1 stock / flashed cf autoroot/flashify/twrp ... flashed your rom/su/gapps/ set up the tablet and then flashed fire/ice. Tablet seems smooth and zippy . also of note previous to flashing your rom I also flashed the new factory image unencrypted if that matters. Thanks for your efforts on the rom.
Click to expand...
Click to collapse
Cheers
ROM? What ROM
posted in the wrong thread : - / . meant to post in the lollipolosa rom thread. so in my previous post just swap out the word rom and insert kernel ,,,,hmmm still doesn't work .
lol - ty for your efforts with the kernel.
Just a quick heads up for those that don't know.
Since some of the terminal emulators don't seem to work and the one that I was able to get working doesn't allow copy and paste.
ROM toolbox pro, and I'm sure plenty of other apps allow you to make the value changes a lot easier and quicker than typing it all out.
jaben2 said:
Just a quick heads up for those that don't know.
Since some of the terminal emulators don't seem to work and the one that I was able to get working doesn't allow copy and paste.
ROM toolbox pro, and I'm sure plenty of other apps allow you to make the value changes a lot easier and quicker than typing it all out.
Click to expand...
Click to collapse
You need to copy it to clipboard
What is the "lite version of the Nexus 9"?
Sent from my Nexus 9 using Tapatalk
TriadX1 said:
What is the "lite version of the Nexus 9"?
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
The nexus 9 with data
Encryption still enabled
First off, I'd like to say that I love your kernel, as it has solved my main issue of overheating on my tablet.
My problem is that despite my best efforts, it still says that the tablet is encrypted. I'm currently on the latest Lollipopalooza running the latest Fire and Ice Kernel and the your modified TWRP recovery (I've tried both R1 and testR2). Doing a factory reset displays the message that it was successfully decrypted, but it still shows up as encrypted under Security settings. I'm also unable to perform a factory reset from adb because it says that the file system f2fs is not supported, and it shows this message despite the fact that I had formatted it back to ext4 through TWRP in a previous attempt to get things in working order. I've attached some screen shots of my security settings as well as the output from fstab.flounder and fstab.flounder64, both showing that it is encryptable. I apologize if this has been posted before, but for the life of me I was not able to find anything that could help. I appreciate any help
JackTheRipper1891 said:
First off, I'd like to say that I love your kernel, as it has solved my main issue of overheating on my tablet.
My problem is that despite my best efforts, it still says that the tablet is encrypted. I'm currently on the latest Lollipopalooza running the latest Fire and Ice Kernel and the your modified TWRP recovery (I've tried both R1 and testR2). Doing a factory reset displays the message that it was successfully decrypted, but it still shows up as encrypted under Security settings. I'm also unable to perform a factory reset from adb because it says that the file system f2fs is not supported, and it shows this message despite the fact that I had formatted it back to ext4 through TWRP in a previous attempt to get things in working order. I've attached some screen shots of my security settings as well as the output from fstab.flounder and fstab.flounder64, both showing that it is encryptable. I apologize if this has been posted before, but for the life of me I was not able to find anything that could help. I appreciate any help
Click to expand...
Click to collapse
Ok hmm
do this
in Recovery
enter adb
and do
cat /proc/version
Give me the output
You know what
screw it I make a flashable zip I would do the same thing
as a factory reset
USBhost said:
Ok hmm
do this
in Recovery
enter adb
and do
cat /proc/version
Give me the output
You know what
screw it I make a flashable zip I would do the same thing
as a factory reset
Click to expand...
Click to collapse
I appreciate the speedy response . Anyway, here is the output I got from recovery:
Code:
/ # cat /proc/version
I:Actual command is: 'cd "/" && cat /proc/version 2>&1'
Linux version 3.10.40[FIRE-ICE]RECOVERY ([email protected]) (gcc version 4.9.3 20141031 (prerelease) (Linaro GCC 4.9-2014.11) ) #1 SMP PREEMPT Fri Dec 5 20:58:57 PST 2014
JackTheRipper1891 said:
I appreciate the speedy response . Anyway, here is the output I got from recovery:
Code:
/ # cat /proc/version
I:Actual command is: 'cd "/" && cat /proc/version 2>&1'
Linux version 3.10.40[FIRE-ICE]RECOVERY ([email protected]) (gcc version 4.9.3 20141031 (prerelease) (Linaro GCC 4.9-2014.11) ) #1 SMP PREEMPT Fri Dec 5 20:58:57 PST 2014
Click to expand...
Click to collapse
Hmm dont know why it does not work
But any way
In about 5min the flashable zip will be ready
---------- Post added at 04:19 PM ---------- Previous post was at 03:56 PM ----------
ok just boot this recovery
like
fastboot boot test.img
then go to install
and move to /res
then you will see a zip called
factory reset.zip
then flash
note i have not tested it so its up to you
to flash it
https://drive.google.com/file/d/0B1cOHQ70J9vlNEN3bHpyVmkzb3M/view?usp=sharing
USBhost said:
Hmm dont know why it does not work
But any way
In about 5min the flashable zip will be ready
---------- Post added at 04:19 PM ---------- Previous post was at 03:56 PM ----------
ok just boot this recovery
like
fastboot boot test.img
then go to install
and move to /res
then you will see a zip called
factory reset.zip
then flash
note i have not tested it so its up to you
to flash it
Click to expand...
Click to collapse
I get an error
Code:
E:Mount: Unable to find partition for path '/res'
Error flashing zip '/res/factory reset.zip
JackTheRipper1891 said:
I get an error
Code:
E:Mount: Unable to find partition for path '/res'
Error flashing zip '/res/factory reset.zip
Click to expand...
Click to collapse
Hmm ok
1 sek
But in the mean time
manually format data to ext4
then back to f2fs
USBhost said:
Hmm ok
1 sek
But in the mean time
manually format data to ext4
then back to f2fs
Click to expand...
Click to collapse
Alright I'll give it a try when I return home in a few hours. Thank you for the help so far
JackTheRipper1891 said:
Alright I'll give it a try when I return home in a few hours. Thank you for the help so far
Click to expand...
Click to collapse
ok i feel so stupid now lol
just format data to f2fs
and your awesome
USBhost said:
ok i feel so stupid now lol
just format data to f2fs
and your awesome
Click to expand...
Click to collapse
I really don't want to be a bother, but it's still encrypted
I even tried manually changing it to ext4 and back again to f2fs, but no change
JackTheRipper1891 said:
I really don't want to be a bother, but it's still encrypted
I even tried manually changing it to ext4 and back again to f2fs, but no change
Click to expand...
Click to collapse
NP at all
Thats one stubborn nexus 9
You know what
I will edit my kernel to
Not support encrypted data
To see if that does it
Also can you give me the output of
su -c mount
USBhost said:
NP at all
Thats one stubborn nexus 9
You know what
I will edit my kernel to
Not support encrypted data
To see if that does it
Also can you give me the output of
su -c mount
Click to expand...
Click to collapse
Thanks for the help
Ive attached a screenshot of the output.
JackTheRipper1891 said:
Thanks for the help
Ive attached a screenshot of the output.
Click to expand...
Click to collapse
ok lets get this on the shell lol
ok download force format data.zip && boot.img
then move force format data.zip to /cache
then boot to recovery
then flash it
then format cache to f2fs
then boot to bootloader
then do
fastboot flash boot boot.img
then reboot
lets hope this does it lol
Related
Ok guys, im awful at writing tutorials so i spent the past hour or so looking for the best one, as a few of you have pm'd me asking me to tell you guys how to build recoveries:
First, let's check out the CyanogenMod tree. The CyanogenMod repository contains Clockwork Recovery, which is part of a full Android build.
repo init -u git://github.com/CyanogenMod/android.git -b ics-release
repo sync
make -j4 otatools
Now, use dump_image or dd to dump your recovery or boot image from a running phone and copy it to your computer somewhere.
dump_image boot boot.img
To build Android from source for a new device, you need to set up a board config and its makefiles. This is generally a long and tedious process. Luckily, if you are only building recovery, it is a lot easier. From the root of your Android source directory (assuming you've run envsetup.sh), run the following (substituting names appropriately):
build/tools/device/mkvendor.sh device_manufacturer_name device_name /your/path/to/the/boot.img
You will receive the confirmation "Done!" if everything worked. The mkvendor.sh script will also have created the following directory in your Android source tree:
manufacturer_name/device_name
Now, type the following:
lunch full_device_name-eng
This will set the build system up to build for your new device. Open up the directory in a file explorer or IDE. You should have the following files: AndroidBoard.mk, AndroidProducts.mk, BoardConfig.mk, device_.mk, kernel, system.prop, recovery.fstab, and vendorsetup.sh.
The two files you are interested in are recovery.fstab and kernel. The kernel in that directory is the stock one that was extracted from the boot.img that was provided earlier. For the most part, recovery.fstab will work on most devices that have mtd, emmc, or otherwise named partitions. But if not, recovery.fstab will need to be tweaked to support mounts and their mount points. For example, if your /sdcard mount is /dev/block/mmcblk1p1, you would need the following lines in your BoardConfig.mk:
/sdcard vfat /dev/block/mmcblk1p1
Once the recovery.fstab has been properly setup, you can build the recovery using:
make -j4 recoveryimage
Your recovery can then be found at $OUT/recovery.img. If you are in need of building a fakeflash recovery, you will need to run the following to create the update.zip that hot replaces the recovery:
make -j4 recoveryzip
Once this is done, build, and tested, notify me, "koush", on Github and I can build official releases and add ROM Manager support!
Tip: Run "make clobber" between builds if you change the BoardConfig.mk, or the change will not get picked up.
Credits to Koush and his tutorial here
Hey Lloir was just checking your guide (I'm from the X8 scene). The funniest bit was "Notify...me, "koush"". I guess it's a typo. Anyways good guide.
I think you guys should look into getting Lloir a dev Desire X, he could do a lot more for you guys if he actually had the device
He has done some great work on the One V, including porting both CM9 and CM10, and he could do the same over here for you guys. I'm just dropping by to say that I vouch for Lloir He also has his own ROM in the works
Hopefully you can snag one of these devices soon Lloir, its always nice to get a fun device to play around on and to develop CM for
thanks for that endorsement Rohan, didn't expect that at all..
Lloir said:
thanks for that endorsement Rohan, didn't expect that at all..
Click to expand...
Click to collapse
I tried to compile a CWM based on gingerbread to get the earlier version of nandroid backups, but I just can't get it to work. Props and thanks again for making a CWM 6 for us, without it, we'd be nowhere
Thanks
Hi,
I managed to successfully built CWM using your guide.
It kinda works but i did not adjust recovery.fstab so i get errors saying failed to find cache partition to mount at /cache and some related to recovery.log.
Anyways, have you found the reason for the graphical glitch yet??
Thanks for the guide, it helped me to get started.
Got CWM working (still testing) for my rk3066 based tablet.
One thing I could not figure out - what to does one need to put into recovery.fstab to be able to mount a USB stick from CWM?
hi
Jin^eLD said:
Thanks for the guide, it helped me to get started.
Got CWM working (still testing) for my rk3066 based tablet.
One thing I could not figure out - what to does one need to put into recovery.fstab to be able to mount a USB stick from CWM?
Click to expand...
Click to collapse
On github, find a device tree with similar setup (a similar tab with option for mounting sd card) and use its fstab as reference. You'll also need to add BOARD_LUN_PATH or TARGET_LUN_FILE_PATH or something like that in the BoardConfig.mk of your device to make USB mounting work. Hope it helps.
Regards
Yasir
Yasir Javed Ansari said:
On github, find a device tree with similar setup (a similar tab with option for mounting sd card) and use its fstab as reference. You'll also need to add BOARD_LUN_PATH or TARGET_LUN_FILE_PATH or something like that in the BoardConfig.mk of your device to make USB mounting work. Hope it helps.
Regards
Yasir
Click to expand...
Click to collapse
Yasir, that was one of the things I noticed about the CM9 boardconfig : the paths you just mentioned need fixing
yes, i fixed it, then broke it again.... now figuring out what broke it
any ideea how i can build a touch recovery?
---------- Post added at 03:13 PM ---------- Previous post was at 03:11 PM ----------
neXus PRIME said:
Hi,
I managed to successfully built CWM using your guide.
It kinda works but i did not adjust recovery.fstab so i get errors saying failed to find cache partition to mount at /cache and some related to recovery.log.
Anyways, have you found the reason for the graphical glitch yet??
Click to expand...
Click to collapse
it it cannot find cache partition, the fstab is not correct
for the graphics, what are the bugs?
dany547 said:
any ideea how i can build a touch recovery?
---------- Post added at 03:13 PM ---------- Previous post was at 03:11 PM ----------
it it cannot find cache partition, the fstab is not correct
for the graphics, what are the bugs?
Click to expand...
Click to collapse
The method lloir posted is from koush, it needs some tweaking to work properly. Are you interested in building one yourself?
Compile from a new device
Hello,
I have a BLU Dash 3.5 and would like to build recovery.
I followed the steps in the guide and compilation errors did not return put the recovery did not work. The phone connects but gets the BLU logo on the screen.
The ADB recognizes the device.
The / system / data / cache / sdcard and / sd-ext is mounted correctly.
but the phone's screen does not pass soon.
I noticed that the ROM Manager can make and restore backups normally.
What am I doing wrong?
dump_image
i tried dump_image of boot boot terminal emulator says dump_image not found... i m running jelly bean 4.1.2 Samsung gt-s5282
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
To take a screen shot, just slide left
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
HTC Desire X (protou)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Click to expand...
Click to collapse
Another Dev here! Good job!
xpirt
Is this official release? Or chances of getting official support? Will be testing it later on.
prototype-U said:
Is this official release? Or chances of getting official support? Will be testing it later on.
Click to expand...
Click to collapse
Sure, it is official. Just untested for your device, until now
Look in main thread link and supported devices list to get an idea
This thread is meant to give specific support for this device and sort bugs when reported
When reporting bugs, please:
- give a detailed description how to reproduce it
- Advanced / "Report Error" and attach here the log
- eventually, if phone unresponsive: adb pull /tmp/recovery.log
xpirt said:
Another Dev here! Good job!
xpirt
Click to expand...
Click to collapse
:good::good::good:
As soon as someone test it working (at least booting and not bricking your phone ), I will remove the red warning. That's meant to keep noobs away until it is tested
I tihnk as we can't flash a new recovery through recovery (due to S-On), it would be more practical to load up the recovery.img directly, so we can flash it through fastboot
dansou901 said:
I tihnk as we can't flash a new recovery through recovery (due to S-On), it would be more practical to load up the recovery.img directly, so we can flash it through fastboot
Click to expand...
Click to collapse
Good to know
Next updates will be only recovery.img renamed like the zip
For now, just extract the recovery.img from the zip and flash it
First testing report: Recovery is booting, aromafm works. Nothing else tested so far...
---------- Post added at 09:57 PM ---------- Previous post was at 09:47 PM ----------
Further testing: Would be nice to have the opportunity to mount the sdcard so it can be accessed via USB (like UMS in TWRP). Is this possible?
dansou901 said:
First testing report: Recovery is booting, aromafm works. Nothing else tested so far...
---------- Post added at 09:57 PM ---------- Previous post was at 09:47 PM ----------
Further testing: Would be nice to have the opportunity to mount the sdcard so it can be accessed via USB (like UMS in TWRP). Is this possible?
Click to expand...
Click to collapse
As it is based on CWM, I believe you can: mounts and storage>all the way down>mount USB storage.
Sent from my awesome fridge
dansou901 said:
First testing report: Recovery is booting, aromafm works. Nothing else tested so far...
---------- Post added at 09:57 PM ---------- Previous post was at 09:47 PM ----------
Further testing: Would be nice to have the opportunity to mount the sdcard so it can be accessed via USB (like UMS in TWRP). Is this possible?
Click to expand...
Click to collapse
Thanks for the feedback :good:
Did you try the menu: Mounts and Storage / Mount USB Storage?
After boot, you have to wait about 1mn for this to activate and before trying the USB mount storage
Phil3759 said:
Thanks for the feedback :good:
Did you try the menu: Mounts and Storage / Mount USB Storage?
After boot, you have to wait about 1mn for this to activate and before trying the USB mount storage
Click to expand...
Click to collapse
It's working... must have missed that. A second thing: Is it possible to remove the haptic feedback? For me, it's just annoying that the phone is vibrating each time...
dansou901 said:
It's working... must have missed that. A second thing: Is it possible to remove the haptic feedback? For me, it's just annoying that the phone is vibrating each time...
Click to expand...
Click to collapse
Start by browsing a bit the new features please
There is a lot to discover in PhilZ Settings menu
Vibrator and a lot more are there
Read the main thread also (link in op) + features + Guide to set up
Thanks again and report any issue
Will do tomorrow... Thanks for this great recovery!
Saw your recovery for the Nexus 7, but I never tried it... Will try this today, but is it for jb hboot or for ics?
Sent from my HTC Desire X using Tapatalk HD
Hi OP,
Just thinking if i can contribute in some way.
Desire X 1.24 hboot (ics) and 1.25 hboot (jb), has different mount points and sizes. If you need to make a CWM for ICS and JB desire x users, then you can use recovery.fstab and BoardConfig.mk sizes from my github linked below:
https://github.com/ProtoU/device_protou_recovery
Branch: "twrp" for ICS stuff
Branch: "twrp-jb" for JB stuff.
Glad to help.
Regards
Yasir
EDIT: Maybe this commit will clarify everything:
https://github.com/ProtoU/device_protou_recovery/commit/eba386989c92f656c247c4d2942f64cf16e74eb8
neXus PRIME said:
Hi OP,
Just thinking if i can contribute in some way.
Desire X 1.24 hboot (ics) and 1.25 hboot (jb), has different mount points and sizes. If you need to make a CWM for ICS and JB desire x users, then you can use recovery.fstab and BoardConfig.mk sizes from my github linked below:
https://github.com/ProtoU/device_protou_recovery
Branch: "twrp" for ICS stuff
Branch: "twrp-jb" for JB stuff.
Glad to help.
Regards
Yasir
EDIT: Maybe this commit will clarify everything:
https://github.com/ProtoU/device_protou_recovery/commit/eba386989c92f656c247c4d2942f64cf16e74eb8
Click to expand...
Click to collapse
Thank you
HTC is amazing me...
You mean, when updating from ics to jb you have to reformat phone partitions?
Anyway. The current recovery is based on cm-10.1 tree. However, I see that the recovery.fstab is same as the ics one you posted. Can anyone enlighten me for your device?
If i guess right, currently, cm10.1 will not run properly on new hboot?
If that's the case, it is important to let me know. I will rename my release tagged with hboot 1.24 and look to release another for 1.25
Sent from my GT-I9100 using Tapatalk 2
Phil3759 said:
Thank you
HTC is amazing me...
You mean, when updating from ics to jb you have to reformat phone partitions?
Anyway. The current recovery is based on cm-10.1 tree. However, I see that the recovery.fstab is same as the ics one you posted. Can anyone enlighten me for your device?
If i guess right, currently, cm10.1 will not run properly on new hboot?
If that's the case, it is important to let me know. I will rename my release tagged with hboot 1.24 and look to release another for 1.25
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
RECOVERY.FSTAB is DIFFERENT
# mount point fstype device [device2]
/recovery emmc /dev/block/mmcblk0p21
-/boot emmc /dev/block/mmcblk0p22 ICS
-/cache ext4 /dev/block/mmcblk0p27 ICS
-/data ext4 /dev/block/mmcblk0p26 ICS
+/boot emmc /dev/block/mmcblk0p27 JB
+/cache ext4 /dev/block/mmcblk0p26 JB
+/data ext4 /dev/block/mmcblk0p25 JB
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
-/system ext4 /dev/block/mmcblk0p25 ICS
+/system ext4 /dev/block/mmcblk0p24 JB
/misc emmc /dev/block/mmcblk0p17
/devlog ext4 /dev/block/mmcblk0p28
/emmc vfat /dev/block/mmcblk0p31
Well, that i saw...
But my question remains: does official cwm work on you jb 1.25?
If yes, then this one will.
The reason is simple. names can be implemented in kernel too. When we boot into recovery, it is kernel from recovery that will handle it
Maybe that's why recovery partition did not change!
So, can you enlighten me now and be more precise? Have no much time to start searching this from scratch
Sent from my GT-I9100 using Tapatalk 2
Phil3759 said:
Thank you
HTC is amazing me...
You mean, when updating from ics to jb you have to reformat phone partitions?
Anyway. The current recovery is based on cm-10.1 tree. However, I see that the recovery.fstab is same as the ics one you posted. Can anyone enlighten me for your device?
If i guess right, currently, cm10.1 will not run properly on new hboot?
If that's the case, it is important to let me know. I will rename my release tagged with hboot 1.24 and look to release another for 1.25
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Phil3759 said:
Well, that i saw...
But my question remains: does official cwm work on you jb 1.25?
If yes, then this one will.
The reason is simple. names can be implemented in kernel too. When we boot into recovery, it is kernel from recovery that will handle it
Maybe that's why recovery partition did not change!
So, can you enlighten me now and be more precise? Have no much time to start searching this from scratch
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Hy. No, the official recovery isn't working with JB, and yes, 1.25 hboot have new partition table (because JB kernel is bigger than the boot partition in 1.24 hboot.. I don't know that a simple resize why not enough, but we got it so), but you don't need to rebuild the recovery, just change the recovery.fstab to this: http://pastebin.com/t3QNcXh3 I use your recovery with this now. Great work! Thank you very much!
EDIT: I can upload the recovery with the JB recovery.fstab, if you want to save your time.
HTML:
I AM NOT RESPONSIBLE IF YOUR DEVICE GETS BRICKED
Alright, I have been working on porting Ubuntu Touch to our lovely Evo 3D's. I will be posting my work here and will change the thread once I get it out of alpha. As you can see this is only recommended for devs or people that know how to use Linux just now.
FAQ
Plz halp i am stuk!?
Click to expand...
Click to collapse
A: No.
Can I help?
Click to expand...
Click to collapse
A: Sure! I have a github where I upload my source code, feel free to fork and submit pull requests.
Requirements
Ubuntu FS - (raring-preinstalled-phablet-armhf.zip).
Decent knowledge of Linux.
Guide
1. Download the Ubuntu FS & shooteru image
2. Backup your phone.
3. Wipe everything (Wipe data/factory reset + dalvik cache, and your ext4 partition).
4. Format your sdcard to have two partitions - one Fat32 (for android) and one ext4 (for Ubuntu)
4. Turn off your phone, insert the SD-card into your computer.
5. Transfer the shooteru image to your SD-card (Like you would do if you'd flash it normally).
6. Open a terminal, Unzip the Ubuntu FS.
7. Run the following command; sudo tar --numeric-owner -axf blabla.tar.gz
8. Run the following command; sudo mv binary /INSERT-PATH-TO-SDCARD-EXT4-PARTITION/ubuntu/
9. Safely eject the SD-card and insert it into your phone.
10. Boot into recovery.
11. Flash the shooteru image
12. Boot up
13. Change the values in /usr/bin/ubuntu-session (Look for export GRID_UNIT_PX = 18 and change it to 12)
14. Reboot
15. Win.
Download
Shooteru image 0.1 (Dev-Alpha)
Changelog
0.1 - 12/7/13
Initial Release
Bugs
Camera
Wi-Fi
Bluetooth
Data
3D
3G
Touch Buttons
Volume
Audio
Resolution
Thanks
Evervolv team
Ubuntu Touch team
helicopter88
good job! thanks
thanks! i'm trying to develop on Ubuntu Touch!
slinkyregent said:
thanks! i'm trying to develop on Ubuntu Touch!
Click to expand...
Click to collapse
It's awesome isn't it?
I won't be able to update this as much as I would like to for just now due to some important family matters. I am however talking with some Ubuntu Touch developers to help solve some issues
Ubuntuz said:
It's awesome isn't it?
I won't be able to update this as much as I would like to for just now due to some important family matters. I am however talking with some Ubuntu Touch developers to help solve some issues
Click to expand...
Click to collapse
I sow the same thread,the same OP like yours on Chinese forum.
dr_jerremy said:
I sow the same thread,the same OP like yours on Chinese forum.
Click to expand...
Click to collapse
Hm.... Odd. I used the same style as the old Evervolv ubuntu threads.
EDIT: Updated the thread with newer Ubuntu builds... it now boots! A lot doesn't work just now but as always I am working hard on it.
dr_jerremy said:
I sow the same thread,the same OP like yours on Chinese forum.
Click to expand...
Click to collapse
I am very curious about the chinese forum you said. can you tell me the website? thanks in advance
uBuntuz working on uBuntu
epic stuff there
im afraid everytime the chinese forum is mentioned, XDA admin/mods close it
jcsy said:
uBuntuz working on uBuntu
epic stuff there
im afraid everytime the chinese forum is mentioned, XDA admin/mods close it
Click to expand...
Click to collapse
haha yeah I'm working on getting the latest Ubuntu Touch images to work and also make it easier to install
I don't know what all this business is about the chinese forums but I'll just stay out of it
Ubuntuz said:
It's awesome isn't it?
I won't be able to update this as much as I would like to for just now due to some important family matters. I am however talking with some Ubuntu Touch developers to help solve some issues
Click to expand...
Click to collapse
When I have some time, i download and i try this rom... I've got a really slowly connection (150kb/s ****ing italian ISP). Please take that updated! :good:
PS: If anyone want to help me or work with me for create Ubuntu Apps, send me a PM!
it seems like windows cannot read a sd with 2 partitions.. no problem on SuSe, though... here... be wwarned...
e3d said:
it seems like windows cannot read a sd with 2 partitions.. no problem on SuSe, though... here... be wwarned...
Click to expand...
Click to collapse
Having 2 partitions on the SD card shouldn't matter with 0.2.
The file you requested was not found in goo.im,the link is broken.
tzpm said:
The file you requested was not found in goo.im,the link is broken.
Click to expand...
Click to collapse
Oops! Fixed it!
loop logo htc ,
---------- Post added at 11:01 AM ---------- Previous post was at 10:56 AM ----------
boot up ? what is your mind? how to do /
dqhuy1989 said:
loop logo htc ,
---------- Post added at 11:01 AM ---------- Previous post was at 10:56 AM ----------
boot up ? what is your mind? how to do /
Click to expand...
Click to collapse
try 0.1 with the 0.1 guide. I'm kinda putting off supporting this since hardly anyone has a) used it and b) commented their results.
I got evervolv boot screen with the first method and second method gave this messege in terminal
"sudo rsync -aP binary /INSERTPATHTOSDCARD/ubuntu/
sending incremental file list
rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken pipe (32)
rsync: mkdir "/INSERTPATHTOSDCARD/ubuntu" failed: No such file or directory (2)
rsync error: error in file IO (code 11) at main.c(605) [Receiver=3.0.9]
rsync: connection unexpectedly closed (9 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9]"
Ubuntuz said:
try 0.1 with the 0.1 guide. I'm kinda putting off supporting this since hardly anyone has a) used it and b) commented their results.
Click to expand...
Click to collapse
What did you expect when you said this:
Ubuntuz said:
Alright, I have been working on porting Ubuntu Touch to our lovely Evo 3D's. I will be posting my work here and will change the thread once I get it out of alpha. As you can see this is only recommended for devs or people that know how to use Linux just now.
Click to expand...
Click to collapse
I don't think such attitude will get you anywhere as a dev. First you need to feel you want to do something for yourself. Then you can start enjoying it... Just my $0.02
zzrzr said:
I got evervolv boot screen with the first method and second method gave this messege in terminal
"sudo rsync -aP binary /INSERTPATHTOSDCARD/ubuntu/
sending incremental file list
rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken pipe (32)
rsync: mkdir "/INSERTPATHTOSDCARD/ubuntu" failed: No such file or directory (2)
rsync error: error in file IO (code 11) at main.c(605) [Receiver=3.0.9]
rsync: connection unexpectedly closed (9 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9]"
Click to expand...
Click to collapse
See where it says "INSERTPATHTOSDCARD" yeah? Put the path to your SD card there.
decemberhayes said:
What did you expect when you said this:
I don't think such attitude will get you anywhere as a dev. First you need to feel you want to do something for yourself. Then you can start enjoying it... Just my $0.02
Click to expand...
Click to collapse
I figured that there was plenty of people on this board that could figure out how to use Linux.
I think if u don't have anything valuable to help Ubuntu, then we should keep quiet
I don't, so I wouldn't criticise anything
For those who do, please help and assist in any way
Testing, drivers, kernel, etc
I believe Ubuntu meant well when he is asking for any form of help from the community to help develop this
Whether he has passion for himself or the project or not , that's not appropriate to condemn or expect
Let's work together when we can, where we can
-----------------------------------------------------
Tapatalked from my HTC EVO 3D GSM
Johnnyslt CM10.1, 06-July-2013
Stock kernel & SIO
-----------------------------------------------------
So I am stuck in a bootloop and no obvious way out.
US Galaxy Player 4.0
Rooted and been on custom roms for a year now. Problem started after upgraded to latest CM. Tried going back to stock but no luck in resolution. I am able to get into recovery and download mode and flash with odin. I can run adb shell. Just won't boot. The error message I get is as follows:
"E:format_volume: rfs format failed on /dev/block/mmcblk0p2"
In my adb shell I can see that there is no "mmcblk0..." files at all.
I have tried to go through the full stock recovery and used the PIT files and the stock rom through odin. I get the same boot loop and cant get the data to wipe due to the same error. I can flash anything through Odin easily without fail but everything is stuck in boot loop. I just don't seem to have /data to wipe.
There are some other posts around which indicate the Partition may be screwed but I am not sure what it is supposed to look like or the command line syntax to use to correct.
http://forum.xda-developers.com/showthread.php?t=1468213&highlight=wipe+data+shell
I have several nandroid backups on an external location but now I can't get the external card to recognize in CWM so haven't been able to try to revert backwards that way. I have backup of efs and all other stuff just can't seem to get to it.
Anybody with Ideas or direct help are greatly appreciated
map1122 said:
So I am stuck in a bootloop and no obvious way out.
US Galaxy Player 4.0
Rooted and been on custom roms for a year now. Problem started after upgraded to latest CM. Tried going back to stock but no luck in resolution. I am able to get into recovery and download mode and flash with odin. I can run adb shell. Just won't boot. The error message I get is as follows:
"E:format_volume: rfs format failed on /dev/block/mmcblk0p2"
In my adb shell I can see that there is no "mmcblk0..." files at all.
I have tried to go through the full stock recovery and used the PIT files and the stock rom through odin. I get the same boot loop and cant get the data to wipe due to the same error. I can flash anything through Odin easily without fail but everything is stuck in boot loop. I just don't seem to have /data to wipe.
There are some other posts around which indicate the Partition may be screwed but I am not sure what it is supposed to look like or the command line syntax to use to correct.
http://forum.xda-developers.com/showthread.php?t=1468213&highlight=wipe+data+shell
I have several nandroid backups on an external location but now I can't get the external card to recognize in CWM so haven't been able to try to revert backwards that way. I have backup of efs and all other stuff just can't seem to get to it.
Anybody with Ideas or direct help are greatly appreciated
Click to expand...
Click to collapse
This is how we fix that with the Player 5 : http://forum.xda-developers.com/showthread.php?t=2398120&page=4 (read the whole thread from page 4 on)
You'll need to do pretty much the same thing but you need an image from the Player 4.:good:
recrtora above
Thank you Meticulus. I see that you were involved in the thread I referenced too and this is where I figured I needed to go. However this is where I get tripped up. The main issue being that I don't have an image from a 4.0 US player. The thread I linked to had the Intl Player shown... There were even a few requests for the US version later on in the thread.
So- Anyone want to share their US player working partition table?
Is this information contained in the .PIT files somehow?
anyway to retrieve this?
map1122 said:
Thank you Meticulus. I see that you were involved in the thread I referenced too and this is where I figured I needed to go. However this is where I get tripped up. The main issue being that I don't have an image from a 4.0 US player. The thread I linked to had the Intl Player shown... There were even a few requests for the US version later on in the thread.
So- Anyone want to share their US player working partition table?
Is this information contained in the .PIT files somehow?
anyway to retrieve this?
Click to expand...
Click to collapse
As far as I know that's the only way to do it is with the picture.... Be patient, I'm sure someone will post an image...
@zaclimon ???
Needed: out put of fdisk on mmcblk0
Code:
adb root
adb shell
fdisk -l /dev/block/mmcblk0
Then post a screenshot, or just the output.:highfive:
Meticulus said:
As far as I know that's the only way to do it is with the picture.... Be patient, I'm sure someone will post an image...
@zaclimon ???
Needed: out put of fdisk on mmcblk0
Code:
adb root
adb shell
fdisk -l /dev/block/mmcblk0
Then post a screenshot, or just the output.:highfive:
Click to expand...
Click to collapse
Here it is, do note that it's a intl device though too.
zaclimon said:
Here it is, do note that it's a intl device though too.
Click to expand...
Click to collapse
That's definately not what I expected... to see from the 4.0's partition table...
Meticulus said:
That's definately not what I expected... to see from the 4.0's partition table...
Click to expand...
Click to collapse
We only have mmc blocks for the actual storage of the device. The system partition and others are pure raw nand (which is why we use mtd and yaffs2)
Envoyé depuis mon Nexus 7 avec Tapatalk 4
zaclimon said:
We only have mmc blocks for the actual storage of the device. The system partition and others are pure raw nand (which is why we use mtd and yaffs2)
Envoyé depuis mon Nexus 7 avec Tapatalk 4
Click to expand...
Click to collapse
So then, will recreating these partitions solve the OP problem?
Meticulus said:
So then, will recreating these partitions solve the OP problem?
Click to expand...
Click to collapse
Most probably because it will only touch /data and internal storage. Actually this is the first time I see a problem like this for the 4.0.
Envoyé depuis mon Nexus 7 avec Tapatalk 4
So any confidence in the international vs the US version being the same?
Now the next thing is I used the command fdisk to start trying to recreate the partitions using the post instructions you recommended. I did not get an option for "new". I attached the output from the shell command. Tried looking up shell command references on fdisk but is not helping me here. Is it because there is not mmcblk0 at all? I don't seem to be getting into the command mode of the fdisk command.
If I use fdisk -l /dev/block/mmcblk0 I get "no such file or directory"
map1122 said:
So any confidence in the international vs the US version being the same?
Now the next thing is I used the command fdisk to start trying to recreate the partitions using the post instructions you recommended. I did not get an option for "new". I attached the output from the shell command. Tried looking up shell command references on fdisk but is not helping me here. Is it because there is not mmcblk0 at all? I don't seem to be getting into the command mode of the fdisk command.
If I use fdisk -l /dev/block/mmcblk0 I get "no such file or directory"
Click to expand...
Click to collapse
Hmm... Can post a list of /dev/block ?
Code:
adb shell
ls /dev/block
Here you go.
map1122 said:
Here you go.
Click to expand...
Click to collapse
Hmmmmm .... see if you can get here: /sys/bus/platform/devices/s3c-sdhci.0 and post the output
Like so?
map1122 said:
Like so?
Click to expand...
Click to collapse
yes.... I'm not sure what's wrong but id recommend installing a full odin flashable rom...
Not sure what that would be for the 4.0..
Here is another place you can check /sys/bus/platform/devices/s3c-sdhci.0/mmc_host/mmc0/mmc0:0001/block/mmcblk0
Here is the output of that. No further.
I am already on fresh Odin flash. Several attempts actually. I have been able to flash back to Stock (and use PIT) files, access stock recovery. I did this first to think I could restore to OEM. Then flash the Terra-Silent kernel to obtain CWM and the IcyFusion Rom (did this again this morning so I could get adb to link). These are the only Odin flashable that I am aware of for the 4.0. Obviously nothing boots because the issues discussed here.
Thank you.
what does "partition SD Card" in the Advanced and Debugging menu in CWM do?
map1122 said:
Here is the output of that. No further.
I am already on fresh Odin flash. Several attempts actually. I have been able to flash back to Stock (and use PIT) files, access stock recovery. I did this first to think I could restore to OEM. Then flash the Terra-Silent kernel to obtain CWM and the IcyFusion Rom (did this again this morning so I could get adb to link). These are the only Odin flashable that I am aware of for the 4.0. Obviously nothing boots because the issues discussed here.
Thank you.
Click to expand...
Click to collapse
I don't know if those are "full" odin flashable roms.
Try here: http://forum.xda-developers.com/showthread.php?t=1531850
Yes, that is the one I am using to revert to stock and additional PIT. I checked MD5 sums too.
Would this kind of thing be backed up in a nandroid?
map1122 said:
Yes, that is the one I am using to revert to stock and additional PIT. I checked MD5 sums too.
Would this kind of thing be backed up in a nandroid?
Click to expand...
Click to collapse
No, It wouldn't be backed up in android...
I'm betting that the U.S. Odin ROM on that page is not a "full" recovery rom either... I'm downloading right now to check. If it isn't, we need to find out how safe it is to flash an INT version first then flash a USA over it.
On the 5.0, we can do that... and everything is OK but don't know about 4.0...
EDIT: Seem like the only difference is that INT has bootloaders and USA does not. That doesn't help us...
Was this already known ? Thought not, right ?
Anyway look for source : https://dl.twrp.me/ailsa_ii/
raystef66 said:
Was this already know ? Thought not, right ?
Anyway look for source : https://dl.twrp.me/ailsa_ii/
Click to expand...
Click to collapse
Ey buddy I need your help , magisk keep forgetting my rooted apps ... I forgot whats the command I have to run on terminal emulator can you please help me !
luisaet82 said:
Ey buddy I need your help , magisk keep forgetting my rooted apps ... I forgot whats the command I have to run on terminal emulator can you please help me !
Click to expand...
Click to collapse
if it's this what you're referring too...
In terminal :
Code:
su
reboot disemmcwp
or adb :
adb shell reboot disemmcwp
raystef66 said:
if it's this what you're referring too...
In terminal :
or adb :
adb shell reboot disemmcwp
Click to expand...
Click to collapse
The first one ... Thank you so much .. great night
So its about twrp and first reaction is off topic...why you dont pm him?!!
Predatorhaze said:
So its about twrp and first reaction is off topic...why you dont pm him?!!
Click to expand...
Click to collapse
Big deal...that's called helping someone out you know.
You could have pm me or him too you know
And really? All those exclamation marks too? I suggest to ease down (and I know you already a bit longer then yesterday...) your comments are from time to time most inappropriate. I leave it with that
Can i flash the latest version when i have the treble recovery from nfound?
@BaamAlex the version 3.2.3.0 has as far as I could see that on my axon 7 no treble support
Chris axon 7 said:
@BaamAlex the version 3.2.3.0 has as far as I could see that on my axon 7 no treble support
Click to expand...
Click to collapse
Have you installed this here?
Yes
raystef66 said:
Was this already known ? Thought not, right ?
Anyway look for source : https://dl.twrp.me/ailsa_ii/
Click to expand...
Click to collapse
Wow. This completely flew past me (and probably most of the xda community lol). Gonna check it out later. Thanks for telling us
Was this the same release that Nfound said was using older sources than his custom release?
This version boots as it should even with a fully loaded f2fs data partition. Finally the f2fs bug in TWRP has been solved!!!!!
Oki said:
This version boots as it should even with a fully loaded f2fs data partition. Finally the f2fs bug in TWRP has been solved!!!!!
Click to expand...
Click to collapse
Can we use that TWRP on treble? It will be better if we format all partitions to f2fs?
Aviver said:
Can we use that TWRP on treble? It will be better if we format all partitions to f2fs?
Click to expand...
Click to collapse
This TWRP works perfectly with treble roms. The main limitation is the inability to wipe, format, backup and restore the vendor partition using the menu system. You can always use the terminal to manage all that. For integrated vendor management, your only option so far is TWRP 3.2.1-8 Treble.
F2FS is a filesystem aimed to ssd storage devices. It provides an efficient and elaborated write policy that takes advantage of the flash memory. Reads are not specially efficient, this is why ext4 is used for read only partitions and f2fs for read/write partitions. So, system and vendor are ext4 while data and cache should be f2fs.