I'm trying to resurrect alternative ROM development, CM9 with the target.
For analysis I want to ask advanced users to export images of their devices.
I am interested in ICS upgraded devices.
How to:
You have to be rooted.
Connect you device to ADB.
Export copy of your partitions by executing in adb terminal
Code:
su
dd if=/dev/block/mmcblk0p1 of=/mnt/sdcard/ROW-32-3G-Recovery-mmcblk0p1.img
dd if=/dev/block/mmcblk0p2 of=/mnt/sdcard/ROW-32-3G-Boot-mmcblk0p2.img
dd if=/dev/block/mmcblk0p3 of=/mnt/sdcard/ROW-32-3G-System-mmcblk0p3.img
You should name images with REGION-CAPACITY-NETWORK-xxxxxx, see my example in code.
After having images, post location, where devs can download it or PM me to find a way to transfer it.
I will make repository of all gathered versions and make it available to other developers.
Reserved for repository links
I'm assuming your looking for dumps of someone who isn't already on the 0.0.7.3 CM9 Alpha? I'm willing to help push development of an alternate roms as I just hate the lenovo changes to just stock android. Let me know if I can be of service
Of course dumps of Lenovo Roms. My target is CM9, but analysis of Lenovo way and ripping some binary blobs (like libs) will be helpfull.
We have to start from somewhere
jaba_cz said:
Of course dumps of Lenovo Roms. My target is CM9, but analysis of Lenovo way and ripping some binary blobs (like libs) will be helpfull.
We have to start from somewhere
Click to expand...
Click to collapse
US tablets welcomed?
Sent from my Galaxy Nexus using Tapatalk 2
Of course. US, WE, ROW and any other. This can help us deduce differences and make custom builds compatible with different devices.
jaba_cz said:
Of course. US, WE, ROW and any other. This can help us deduce differences and make custom builds compatible with different devices.
Click to expand...
Click to collapse
If you can send me the commands to do this I'm not sure if its same for row that you have on your op or I'm also going to give the nvflash a try
Sent from my Galaxy Nexus using Tapatalk 2
I also have working adb I was able to reboot using adb to confirm that's my extent on knowledge in adb lol
Sent from my Galaxy Nexus using Tapatalk 2
ker2gsr said:
If you can send me the commands
Click to expand...
Click to collapse
For command look into first post
In section "code"
Wouldn't this part of the code /ROW-32-3G-Recovery-mmcblk0p1.img different being that I got a US tablet
I only have a WiFi version
Sent from my Galaxy Nexus using Tapatalk 2
ker2gsr said:
Wouldn't this part of the code /ROW-32-3G-Recovery-mmcblk0p1.img different being that I got a US tablet
I only have a WiFi version
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Than name it US-32-WIFI......
Or anything you like, just keep information, what device it was.
Sent from my ThinkPad Tablet using XDA Premium HD app
jaba_cz said:
Than name it US-32-WIFI......
Or anything you like, just keep information, what device it was.
Sent from my ThinkPad Tablet using XDA Premium HD app
Click to expand...
Click to collapse
Oh OK will try when I get home
Sent from my Galaxy Nexus using Tapatalk 2
may I ask? Isn't it a problem our device have ext4 FS instead of kind a imgfs(yaffs for example). Is it possible to disassemble system image then?
TPT_OTA3_US_ICS_rooted.zip is a Nandroid I made AFTER a factory reset and the OTA3 update but BEFORE I rebooted into ICS for the first time. CWR was lost after reboot. Root was preserved.
I'm not sure what use it will be... I don't have any tests to report. I was hoping that it might allow someone to get the official ICS update without losing CWR but I would feel terrible if someone bricked their TPT with this backup. If someone confirms it's usefulness I would be pleased.
Located at: http://everyrandom.com/files/download.php?file=216TPT_OTA3_US_ICS_rooted.zip
were do you want it sent?
jaba_cz said:
I'm trying to resurrect alternative ROM development, CM9 with the target.
For analysis I want to ask advanced users to export images of their devices.
I am interested in ICS upgraded devices.
How to:
You have to be rooted.
Connect you device to ADB.
Export copy of your partitions by executing in adb terminal
Code:
su
dd if=/dev/block/mmcblk0p1 of=/mnt/sdcard/ROW-32-3G-Recovery-mmcblk0p1.img
dd if=/dev/block/mmcblk0p2 of=/mnt/sdcard/ROW-32-3G-Boot-mmcblk0p2.img
dd if=/dev/block/mmcblk0p3 of=/mnt/sdcard/ROW-32-3G-System-mmcblk0p3.img
You should name images with REGION-CAPACITY-NETWORK-xxxxxx, see my example in code.
After having images, post location, where devs can download it or PM me to find a way to transfer it.
I will make repository of all gathered versions and make it available to other developers.
Click to expand...
Click to collapse
Ok, I guess I'll be the first So no matter how much you look via a file browser after mounting your TPT within your OS you will not find the dump files (at least on Windows, I didn't try my Linux box). Lenovo somehow filters out .img files or something. I tried renaming the file extension but I still wasn't able to see them.
So, I had to use adb to grab them. Simply:
Code:
adb pull /sdcard/US-16-WIFI-Recovery-mmcblk0p1.img
Anyways, here are my dumps for my tablet. The system dump is almost ~800MB so I'm gonna have to see where I can upload it. I might try Drive in a bit and I'll update the list.
US-16-WIFI-Recovery-mmcblk0p1.img
US-16-WIFI-Boot-mmcblk0p2.img
US-16-WIFI-System-mmcblk0p3.img
here is mine http://db.tt/VL2VLPzz boot. img_32_us
http://db.tt/FYFEILyf recovery. im_32_us
http://db.tt/jCn1WXaY system. img_32_us
rocking rooted ics ThinkPadTablet..... *****es
Happy to see that people are still working on cm9 for the tpt.
Unfortunately I don't have root. As there is currently bio iron to get root when running Lenovo ota3, is there a way to downgrade to 3.1 hc to use the old root method?
Sent from my GT-I9300 using xda premium
Related
NOTE: If you do not know how to SBF or have problems SBFing please do not post about it here. This is a research thread
A while ago TreyM started development on MIUI4DX. Unfortunately he does not own a Droid X. And due to personal reasons he may not be returning to the scene for some time. If he was here I would ask to take over development, but because of the circumstances I've decided to head development. (If anyone has an issue with this please contact me.)
I'd use the other thread created by TreyM for this, but I feel due to this being very unstable and being in a place where there are other device developers, I may be able to get some more input. Also this is an older build of MIUI,
Here comes the hot stuff!
Instructions:
These are in update.zip form. Just install as a zip through ClockworkMod
To grab a logcat you must have the ADB. Open a terminal (Command Prompt) and input the following:
Code:
adb devices
adb -d logcat > MIUI4DX-logcat.txt
I also need dmesg output.
Code:
adb devices
adb shell
dmesg
Go to pastebin.com and post a link to logcats and dmesg output here.
Test builds, and changelogs.
Here is test #9. It is basically the Defy MIUI ported to the Droid X
http://tetradsoftware.com/android/i...ile=miuiandroid_DroidX-1.7.10_pre-alpha-9.zip
Does not get to the bootanimation
LOGCAT: http://pastebin.com/SLy6TSqh
DMESG: http://pastebin.com/kc4N34cy
This is test #10. It's basicly the Defy apps, and framework-res.apk forted to CM7:
http://tetradsoftware.com/android/index.php?dir=DroidX/MIUI4DX/&file=MIUI-Alpha-10.zip
This actually gets to the bootanimation
LOGCAT: http://logcat.miui.us/285002
DMESG: http://pastebin.com/0wAFVXKs
Please, please, please look over the logcats, and dmesg for both of them. I can't decided which to go from.
Follow me on Twitter @ghostlypickel
are we suppose to just install one of the given zip's or do we have to use the commands first. Some detailed instructions would be extremely helpful
reannimated said:
are we suppose to just install one of the given zip's or do we have to use the commands first. Some detailed instructions would be extremely helpful
Click to expand...
Click to collapse
Install then run the commands. The test logs and changelogs are at the bottom for organizational reasons, since it's being constantly updated.
Downloading now flashing and logging when I arrive home in about an hour or so.
Just flashed the new miui port for the nook color. Wip but great Tom nonetheless.
Sent from my DROIDX using XDA Premium App
Edit: took a bit longer getting home then expected. Redownloading now previous went south.
OP updated with important info. Please look at BOTH builds logcats/dmesg. I cannot decide which to go from.
Still looking for testers?
cyberhern said:
Still looking for testers?
Click to expand...
Click to collapse
I dont think he is since the real release is coming out tonight for the DX and D2.
bigshotrob22 said:
i dont think he is since the real release is coming out tonight for the dx and d2.
Click to expand...
Click to collapse
i hope that's true
cyberhern said:
i hope that's true
Click to expand...
Click to collapse
It is. It's supposed to be released on miui, xda, and on rootzwiki.
Sent from my DROIDX using XDA App
bigshotrob22 said:
It is. It's supposed to be released on miui, xda, and on rootzwiki.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
THANKS for the heads up...
Guess I know what I'll be doing this weekend.
!-)
sweet! i will have to try this tomorrow but definitely keeping an eye out on this thread
Hello everybody!
Yesterday I was thinking about a new app for Android, and this app would be able to comunicate with the recovery to schedule things like backup and restore. In 2011 I released "ROM Updater" (not that big success though) which used extendedcommands, an extension to the recoveries made by the team of CyanogenMod (it was indeed created to let the CM updater work).
ClockworkMod Recovery adopted this system, but the author probably didn't want the competition, so started to release the ClockworkMod recovery with encrypted extendedcommands. You can still recompile CWM and redistribute with the unencrypted commands, though I decided to opt for something less rouge-ish (why the hell should I recompile something that already "works"?).
Team Win Recovery Project is a 100% open-source recovery with a new scripting language, called "OpenRecoveryScript". It's just like extendedcommands, but without all the implications of "Premium"* or in any case limited API.
Well, TWRP is not only that, it's a full-multitouch recovery, easy to use. It's being built for a list of devices, and this list will be updated every time someone will compile the recovery for his own device. I decided to compile it for the P7500, hoping it will be added soon to the official list. In the mean while, I'll release the builds right here.
I've built and tested the recovery image for the P7500 (WiFi+GSM) and it's been confirmed that it works on the P7510 device too (WiFi only).
Goo.im GT-P7500 TWRP repository
TechErrata GT-P7500 TWRP repository
TWRP 2.2.1.5 - GT-P7500
openrecovery-twrp-2.2.1.5-gt-p7500.img (on Goo.im)
openrecovery-twrp-2.2.1.5-gt-p7500.img (on TechErrata.com)
TWRP 2.2.2.0 - GT-P7510 (thanks to MapleSyrup)
openrecovery-twrp-2.2.2.0-gt-p7510.img
How to flash:
- Copy the recovery into the storage partition (alias /sdcard)
- In adb, as root, execute dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p2
Cheers
*I personally think that Koushik Dutta (the ClockworkMod guy), encrypting the commands with his distributions, played hard: ROM Manager is the "official" CyanogenMod updater (it's distributed along with any CM release even if it's not opensource (and the CM guys worked hard to take the closed-source apps out of their release)), de-facto everybody install the CWM recovery just 'cause it's already there (déjà vu Internet Explorer?). I think this is called "monopoly" and should be fought in any possible way.
I'm all for true open source development, and will be watching your progress on this. Kudos and a thanks to you!
Sent from my GT-P7510 using XDA Premium HD app
I'd be willing to test for the p4vzw. If you build an image for it.
Sent from my Galaxy Nexus using Tapatalk 2
This appears to work on my Wifi Galaxy Tab 10.1 (p7510). Although the log says "E: Unable to mount /sdcard" I can access the sdcard just fine. I tried updating to the latest droidbasement.com kernel and it flashed perfectly.
Oh, and thanks for the quick and easy non-odin way of flashing recoveries.
The recovery is already in the goo.im repository
http://goo.im/devs/OpenRecovery/gt-p7500
The dropbox image is already update to fix the /sdcard "problem" ^^
Would this work on a Galaxy Tab 10.1 wifi (p4wifi)?
Sent from my Nexus One
According to AAccount yes. Please confirm this, so that I'll tell the TWRP guys to add the repo for that device too and I'll update the title of the conversation here.
I can say without a doubt that this is the best recovery I have used on any device in my 3 years with android phones. Wow! Graphics a bit grainy on the p7500, but functionality is fantastic! Thanks!
Very nice recovery system, good to see other options. HTC users had several choices such as AmonRa and 4ext.
Can confirm that it works on the WiFi only version. Thanks for the options , friend. Been running TWRP on my One X since the boot loader was unlocked, and I was missing it.
Sent from my GT-P7510 using Tapatalk 2
At the risk of sounding like a noob.....what is adb, and can someone provide a link so I can school myself on it?
Sent from my GT-P7510 using XDA Premium HD app
Swammy1979 said:
At the risk of sounding like a noob.....what is adb, and can someone provide a link so I can school myself on it?
Sent from my GT-P7510 using XDA Premium HD app
Click to expand...
Click to collapse
You don't actually need to use adb. Any terminal app should do it. Just tyope "su" before issuing the dd command. I used this app https://play.google.com/store/apps/details?id=jackpal.androidterm&feature=nav_result. I suppose a word of caution would be to make sure you have the command correctly. Don't make a typo like mmcblk0p3 or you could be in a nasty situation.
Adb can be found in the android sdk. Google "android sdk" and download the appropriate one. After that have the sdk download platform tools.
Swammy1979 said:
At the risk of sounding like a noob.....what is adb, and can someone provide a link so I can school myself on it?
Sent from my GT-P7510 using XDA Premium HD app
Click to expand...
Click to collapse
An easy and safe way if you have the SDK installed is to run adb shell
Then type su
paste in the dd command posted earlier
Thanks....I went on google and am now learning about Android SDK. Interesting stuff. I know how I will be spending my weekend!
EDIT: In the meantime, I went ahead and used terminal emulator for the commands. I definitely like the touch interface...and it looks nicer than cwm for sure! It is a little slow graphically, but I think that can be forgiven based on the look of the interface.
Confirmed working on the p7510 wifi
Sent from my GT-P7510 using XDA Premium HD app
Hi
It works like a charm on my 7500.
Thanks for that. Maybe some one could make the install more user friendly, a recovery zip?
Sent from my GT-P7500 using XDA Premium HD app
I could create an update zip... if only I could remember where I left the signing tool...
This is a really nice recovery, thanks for posting it. And I think that with this recovery I can flash a zip from the command line, this will be really useful for my scripts.
elegos said:
The dropbox image is already update to fix the /sdcard "problem" ^^
Click to expand...
Click to collapse
BTW, I'm compiling it for the GT-P7510 (p4wifi), everything works fine, but I don't know how to fix the /sdcard error message, could you please tell me how to do it?
That is a nice one, thank you very much for this project.
MapleSyrup said:
This is a really nice recovery, thanks for posting it. And I think that with this recovery I can flash a zip from the command line, this will be really useful for my scripts.
BTW, I'm compiling it for the GT-P7510 (p4wifi), everything works fine, but I don't know how to fix the /sdcard error message, could you please tell me how to do it?
Click to expand...
Click to collapse
http://goo.im/devs/OpenRecovery/gt-p7500/openrecovery-twrp-gt-p7500-2.1.8.img
^-- this works for the 7510 too
BTW it's just a line in recovery.fstab in the device sources: comment the /sdcard one.
Works great for me although it's a bit slow to boot into compared to CWM or even to TWRP on my brother's HP Touchpad. Also text is a bit pixelated. Other than that though it seems to work well. I use 4ext on my Nexus One so it's really nice to finally get a touch recovery on my tab too
Sent from my GT-P7510 using Tapatalk
Before everyone starts flaming me and trying to kill me for being such a noob, i would like to say that i'm a teen and a noob.
ANYWAYS, i got bored and decided to have a go at porting Firefox OS to the Optimus 2X. After figuring out how to make a flashable zip out of .img's, I tested a bit. Unfortunately ADB doesnt work and I don't know how to do live kernel debugging.
What works: Kernel
What doesn't work: everything else
Source code: http://github.com/JordanRulz
Download:
First Semi-working attempt: http://d-h.st/juX (not a flashable zip)
2nd attempt: link on http://jordanrulz.tk/ (flashable)
3rd attempt (current): http://d-h.st/0We(flashable)
Turn signature verification off before flashing
BUILD INSTRUCTIONS (still doesn't work, but for anyone who thinks they might have the answer, go right ahead)
1.
Code:
git clone http://github.com/JordanRulz/B2G.git
2.extract a cm9 rom to B2G/my_device_backup
3.cd to the B2G directory and
Code:
ANDROIDFS_DIR=my_device_backup ./config.sh p990
and wait for the code to download. This has a good chance of failing because repo and git are stupid.
4.
Code:
./build.sh
5.edit core/sysroot/init.rc so that it imports init.p990.rc
6.go to line 98 of build/core/Makefile and change the build fingerprint to something acceptable by the build system
7.go online and find a wpa_ctrl.h and put it in hardware/libhardware_legacy/wifi/libwpa_client/wpa_ctrl.h
8.copy libcamera.so and libwpa_client.so from a cm9-based rom to out/target/product/p990/obj/lib/
9.it should turn out boot,img, system.img, a system folder, userdata.img, a userdata folder, etc. with adaptations, you should be able to craft a flashable zip out of the folders.
Please hit donate if you feel my work is worth donating to.
Good effort bro!
Way to go buddy.... Expecting this Rom for our beloved Optimus 2x. (me too a noob cant help much)..
Thanks and wish u best of luck..
ahahaha, great work! bring to the old O2X a new system!
Interesting tread, I'll look at the files. Let's hope this will be a cooperative tread to make this
Ok. What i did similarly to my phone to get this up. First, use PowerISO and extract userdata.img and system.img. Once done, its just like system folder of android while userdata is just data folder for user's data. Obviously. And then, the boot.img goes to the same as a flashable rom zip root folder. So basically, they are the same as flashing cm. Just need to add another few commands for recovery.img so that the whole thing is flashed like cm10
nicholaschw said:
Ok. What i did similarly to my phone to get this up. First, use PowerISO and extract userdata.img and system.img. Once done, its just like system folder of android while userdata is just data folder for user's data. Obviously. And then, the boot.img goes to the same as a flashable rom zip root folder. So basically, they are the same as flashing cm. Just need to add another few commands for recovery.img so that the whole thing is flashed like cm10
Click to expand...
Click to collapse
doesn't work. "invalid image file"
i think probably you can pm any recognised dev's for help....if you post a thread here i dont think anybody will try to help....you can pm the dev's like tonyp, harsh, carburano or anyone and you can ask for help in packaging and later on continue with your development....just an idea....:good:
good stuff man., were not the flaming community of yester year
This is getting really frustrating, after restarting multiple times and over 10 failed attempts. I have forked all the repos to my github so that all that want to help are able to do so. http://github.com/JordanRulz
Hello everyone. It's for new bl or old bl? Thanks
Sent from my LG-P990 using xda app-developers app
I say it´s for the old BL, if i don´t read the updater-script inside completly wrong.
It's for old bl
Sent from my LG-P990 using xda app-developers app
build instructions (for a non-working build, but still useful for f*cking around) were added.
JordanRulz said:
build instructions (for a non-working build, but still useful for f*cking around) were added.
Click to expand...
Click to collapse
:good::good:
Don't know if you're going at it the right way but good luck, and you should contact another dev just to make sure at least that you're on the right path.
I'm trying to get help from several devs.
Sent from my LG Optimus 2x using xda app-developers app
JordanRulz said:
I'm trying to get help from several devs.
Sent from my LG Optimus 2x using xda app-developers app
Click to expand...
Click to collapse
I hope if you develop successful, it will have 1 for SU660 :victory:
http://jordanrulz.tk/ not open the sites, is a virus java drive, jordan you really noob report on f.b.i
alexcyb said:
http://jordanrulz.tk/ not open the sites, is a virus java drive, jordan you really noob
Click to expand...
Click to collapse
Its not a "virus java drive", its a hidden bitcoin miner. If u use a secure browser like Firefox, it will prompt you before running it.
Sent from my LG Optimus 2x using xda app-developers app
Hi to all, this time I'm trying to port Ubuntu Touch, I have built device-specific zip file for Ubuntu Touch but after installing it and daily preinstalled Ubuntu armhf image from http://cdimage.ubuntu.com/ doesn't boot, no black screen, only Galaxy bootscreen, in kernel's defconfig I've done all modifications listed on https://wiki.ubuntu.com/Touch/Porting and compiled with brunch janice
Hi guys any one working on this?
Sent from my GT-I9070 using xda app-developers app
No logs?
Sent from my GT-I9070 using Tapatalk 4
Shaaan said:
No logs?
Sent from my GT-I9070 using Tapatalk 4
Click to expand...
Click to collapse
ADB not working in bootscreen, last_kmsg is useless because to enable ADB I have to enter in recovery so the file is overwritten. With device-specific package the recovery's graphic changes according to Ubuntu, and flashing a CM kernel boots the Android part (I can see CM bootanimation, but OS obviously doesn't load). Maybe the problem is in the kernel's ramdisk, I have to add something to init.rc or change BOOTCLASSPATH to boot Ubuntu?
Any updates?
Sent from my GT-I9070 using xda app-developers app
I don't think the project will be succesful.As you know we even can't get a proper AOSP ROM and Cyanogens are unofficial and we should hope another OS ?
But of course I'm not hate just saying; maybe my knowledge would be false, thanks for work.
Darkness and Hope said:
I don't think the project will be succesful.As you know we even can't get a proper AOSP ROM and Cyanogens are unofficial and we should hope another OS ?
But of course I'm not hate just saying; maybe my knowledge would be false, thanks for work.
Click to expand...
Click to collapse
This project is just for test, the OS is based on CM kernel, so it should be boot if all is done correctly, I think that the error is in the kernel's ramdisk
Inviato dal mio GT-I9070
Are there any realistic chances that there will ever be a Ubuntu Touch OS for this phone? I mean i certainly do not ask for a ETA. But i would love to have a Ubuntu Touch on my phone. If this is not possible then Ohhhkehhh no problem. So will there any further progress on this or not?
Finally something moves! I recompiled again with other changes, now after installing device-specific zip file and preinstalled image I get a bootloop with a black screen for 5 seconds, so kernel tries to boot OS but unfortunately I can't use ADB shell because is not working...
If any dev can/wants to help me is welcome! Two brains are better than one...
Uart. You need uart to debug it if the kernel cannot reach the point of loading adb!
Sent from my GT-I9070 using Tapatalk 4
Tesla-MADAL93 said:
Finally something moves! I recompiled again with other changes, now after installing device-specific zip file and preinstalled image I get a bootloop with a black screen for 5 seconds, so kernel tries to boot OS but unfortunately I can't use ADB shell because is not working...
If any dev can/wants to help me is welcome! Two brains are better than one...
Click to expand...
Click to collapse
Try starting adb service on early-init and start services using logwrapper binary to debug
Sent from my GT-S5367 using xda app-developers app
Shaaan said:
Uart. You need uart to debug it if the kernel cannot reach the point of loading adb!
Sent from my GT-I9070 using Tapatalk 4
Click to expand...
Click to collapse
I was thinking about uart but I don't have an interface...
frapeti said:
Try starting adb service on early-init and start services using logwrapper binary to debug
Sent from my GT-S5367 using xda app-developers app
Click to expand...
Click to collapse
Okay, I will try this
I upload device-specific zip on my dev-host as soon as I can, so if a dev wants to take a look into it he can
Inviato dal mio GT-I9070
EDIT: Device-specific zip available here
Code:
[CODE][CODE]
[/CODE][/CODE]
Tesla-MADAL93 said:
I was thinking about uart but I don't have an interface...
Okay, I will try this
I upload device-specific zip on my dev-host as soon as I can, so if a dev wants to take a look into it he can
Inviato dal mio GT-I9070
EDIT: Device-specific zip available here
Click to expand...
Click to collapse
Part of TeamCanjica is interested in getting ubuntu touch running . I have already made all modifications needed if you want to join this project please pm me. I am running a test build now on my ste device.
Edit: understand it's not Janice. Diego or Frapeti are doing it. I have another ste device similar to s3 mini.
---------- Post added 26th January 2014 at 12:06 AM ---------- Previous post was 25th January 2014 at 11:20 PM ----------
Tesla-MADAL93 said:
Finally something moves! I recompiled again with other changes, now after installing device-specific zip file and preinstalled image I get a bootloop with a black screen for 5 seconds, so kernel tries to boot OS but unfortunately I can't use ADB shell because is not working...
If any dev can/wants to help me is welcome! Two brains are better than one...
Click to expand...
Click to collapse
I get the same issue as well interesting I have a different ste device so hey it's a common issue
https://github.com/Novathor-Touch
A little info on the real issue with ubuntu touch bootloop
That's my data partition pretty sure you have the same issue. Now if I can change the features I should be ok
Code:
sec-battery sec-battery: sec_bat_monitor_work: Status(Discharging), Health(Good), Cable(1)
[ 2.924194] initrd: mounting /dev/mmcblk0p25
[ 2.927978] EXT2-fs (mmcblk0p25): error: couldn't mount because of unsupported optional features (44)
[ 2.951538] EXT4-fs (mmcblk0p25): couldn't mount as ext3 due to feature incompatibilities
[ 3.029205] EXT4-fs (mmcblk0p25): recovery complete
[ 3.029235] EXT4-fs (mmcblk0p25): mounted filesystem with ordered data mode. Opts: (null)
[ 3.587127] Kernel panic - not syncing: Attempted to kill init!
dead or undead?
So is this it now for our Ubuntu Touch hopes?
Will there be anything done?
Or is this here just a relict of a dead end road?
I would love to see Ubuntu on my phone and certainly i am not the only one - but if it will not be possible then please just tell me and i will check for compatibility on a future phone i will buy just to be sure.
dawnofkardath said:
So is this it now for our Ubuntu Touch hopes?
Will there be anything done?
Or is this here just a relict of a dead end road?
I would love to see Ubuntu on my phone and certainly i am not the only one - but if it will not be possible then please just tell me and i will check for compatibility on a future phone i will buy just to be sure.
Click to expand...
Click to collapse
I can see the desperation in you for Ubuntu touch, good. Then why don't you try yourself and contribute to others instead of cribbing here. Your post sounded very rude, sorry to say this.
Sent from my GT-I9070 using Tapatalk
No ETAs please. I am still working on it. Btw, Nexus devices have the maximum compatibility by Canonical, but issues too.
Annasarp said:
I can see the desperation in you for Ubuntu touch, good. Then why don't you try yourself and contribute to others instead of cribbing here. Your post sounded very rude, sorry to say this.
Sent from my GT-I9070 using Tapatalk
Click to expand...
Click to collapse
Sorry.
I did not want to:
- offend anybody or anything
- ask for ETA
- sound rude in any way
I was asking if there is still work in progress or if this is totally abandoned.
This was answered by Tesla and i am grateful to hear that he is still working on it.
So please excuse me for writing words that can be misunderstood.
For participating:
I have some minor Linux skills and compiled some kernels due to real time audio applications within linuxmint and opensuse.
I work as a 3d design egineer for special machines.
I never had the time to get into compiling ubuntu touch (married and 2 kids and a - but if you think my skills would be of help please feel free to contact me via pm and i will do what i can to help you or anybody who needs help with the issue.
any updates
londheaakash said:
any updates
Click to expand...
Click to collapse
Tesla-Madal is working on it. Be patient. And pls. Stop asking questions like when next update.
Sent from my GT-I9070P using xda app-developers app
Anyone trying on this can share their progress here so we can help
Enviado desde mi GT-I9505 mediante Tapatalk
!!!!!! NOT FULLY TESTED !!!!!!!
This patch is based on Tasssadar's hardboot patch for mako. And I borrowed some code (hardboot page address usage) from alvinhochun's Xperia M port. The kernel source is 9.2.A.0.295 from Sony. Thanks all of above!
Here is Tassadar's original thread which explains what is kexec hardboot and what it does. Apply this patch to your kernel source and it will be capable of booting another kernel/system without reflashing.
Note: KEXEC_HB_PAGE_ADDR doesn't need to be a certain value. In my tests, 0x88000000 and 0x88A00000 both work. However, I don't know if there are significant side effects... There is no ram_console entry in /proc/iomem... The default address calcuated by original patch is 0x88CE0000,which doesn't work, so I removed the calculation code and hardcoded the address (thanks alvinhochun)
Click to expand...
Click to collapse
Usage can be seen in the sh file attached. Sh file is modded on Tasssadar's. Kexec binary is also taken from his github. Thanks again!
Parameters:
--load-hardboot : load the kernel with hardboot request
--initrd : ramdisk path (For 2012 line, that's the ".cpio.gz" file)
--mem-min : where the kernel should be loaded to (lowest address). This is not certain,either. 0x82000000, 0x85000000 both work. You can try different values. (Is there any limitation to this? Plz tell me...) Normally 0x82000000 will be okay.
--command-line : command line for the guest kernel. Note that the arguments appended by bootloader (semcandroidboot.babe1324 etc)need to be added here manually.
Click to expand...
Click to collapse
Now I have successfully dual-booted stock 4.3(205) and OmniROM 4.4 (homemade):
1. re-partition external sdcard to 4 parts. 1 for regular data storage(mmcblk1p1), 1 for /system (mmcblk1p4), 1 for /data (p2) and 1 for /cache (p3).
2. mount /dev/block/mmcblk1p4 to USB storage in TWRP and "dd if=(9.2.A.1.205 system.ext4 extracted from FTF) of=(USB storage)" on computer. You can use a card reader also.
3. modify the fstab files in stock 205 ramdisk to change the devices for /system, /data and /cache. If you want to add recovery, edit their fstabs also. (PERMISSIONS FOR THESE FILES ARE REALLY IMPORTANT! All .rc and fstab should be 644, root:root. Otherwise it won't boot)
4. repack the ramdisk. Push the zImage and ramdisk to the phone and execute the sh file. The phone reboots and stock 4.3 loads.
5. rebooting the phone will go back to host ROM.
Click to expand...
Click to collapse
But there is one problem: in stock 4.3, Baseband is shown as "Unknown" and the phone gets no signal. On the host ROM, it works properly. It seems to be related to TA reading, but I can't think of anything wrong with this...Logcat shows three TA units were missing. But in host ROM, they are shown as missing too. Full logcat attached in zip. I didn't touch any file other than fstab, fstab.qcom and init.target.rc in 205 ramdisk. Stock 4.1 works like a charm though.
Anyone knows? Thanks in advance~
You said you had a Omnirom for tx (homebuild)... Could you share it... If it's stable?
Sent from my LT29i using XDA Premium 4 mobile app
alanc.1996 said:
You said you had a Omnirom for tx (homebuild)... Could you share it... If it's stable?
Sent from my LT29i using XDA Premium 4 mobile app
Click to expand...
Click to collapse
New build arrived (2014/05/21). See the separate thread. Following is the old message.
==================
At least it won't reboot ramdomly..but there may be some minor bugs.
Link: http://pan.baidu.com/s/1i3Hq4ip (Password: kpnn)
Internet connection is not very good here so uploading to devhost/mediafire is nearly impossible...
You need to flash the kernel first, then use the recovery to flash the ROM, then flash the kernel again. After system boots, push the modules file to /system/lib/modules
This is based on tital's port. Thanks a lot~
Later I will open a thread to introduce this ROM...
Cool! Will try it out!
Sent from my LT29i using XDA Premium 4 mobile app
Months ago, when I restored an Nandroid backup of 9.2.A.0.295, the same problem appeared. But at that time only mobile service was dead, while WiFi worked. Now mobile service and WiFi are all dead. The screen stops at "Turning on Wi-Fi". However, in dmesg & lsmod, I can see that WLAN driver module has been loaded, with MAC address changed correctly...And in Service Menu(*#*#SERVICE#*#*), Configuration in Service info is dead. Tapping on it will cause the app to stop responding. What is the point?
OK I tried 9.1.B.1.67 firmware. Everything works, including baseband, Wi-Fi and *#*#SERVICE#*#*... However, it's not so attractive as stock 4.3...
Possible to run this way Doomlord custom kernel (based on stock 205) from stock ROM (PureXT etc)?
RpRAUC said:
Possible to run this way Doomlord custom kernel (based on stock 205) from stock ROM (PureXT etc)?
Click to expand...
Click to collapse
As long as the kernel matches the ROM (phone operates normally when you install the custom kernel as usual), it should be okay...
Is it your plan to keep this TX exclusive, or would you be willing to port this to T?
Great work!
Sent from my LT30p using XDA Free mobile app
Galcactus said:
Is it your plan to keep this TX exclusive, or would you be willing to port this to T?
Great work!
Sent from my LT30p using XDA Free mobile app
Click to expand...
Click to collapse
This patch may work on T without any modification, except for the macro name in memory.h
Has there been any further development on this?
Sent from my LT30p using XDA Free mobile app
Galcactus said:
Has there been any further development on this?
Sent from my LT30p using XDA Free mobile app
Click to expand...
Click to collapse
It's already perfectly working...
In which case, is there any chance of having a guide on how to use this? A few brief steps outlining which files need to be used where, would be greatly appreciated.
(On a side note is there any chance of a version built especially for the Xperia T? I know that there aren't many differences, but it's better to be safe than sorry).
Much obliged
Sent from my LT30p using XDA Free mobile app
Galcactus said:
In which case, is there any chance of having a guide on how to use this? A few brief steps outlining which files need to be used where, would be greatly appreciated.
(On a side note is there any chance of a version built especially for the Xperia T? I know that there aren't many differences, but it's better to be safe than sorry).
Much obliged
Sent from my LT30p using XDA Free mobile app
Click to expand...
Click to collapse
This is a little bit complicated... but I'll try to make a post about this in a few days.
The kernel commits should be the same for TX and T :
https://github.com/updateing/androi...mmit/3d4950e7d3a0cc1549e82fda6c1d961f83e04f4a
https://github.com/updateing/androi...mmit/8843e01fb1b6752768056589a510a2f8985c0884