[ROM] 2.3.1 boot.img with ro.secure=0 and ext4 hack. adb remount with CM7 boot.img - Nexus S Android Development

this is the 2.3.1 kernel off my nexus s modded with ro.secure=0. adb remount works again! apparently people really like this option? lots of complaints it didnt work since upgrading to 2.3.1.
edit: added @supercurio's ext4 file system hack. all credits to him for providing the how-to.
edit2: added the boot.img from CM7 with @supercurio's ext4 file system hack.
test:
Code:
fastboot boot roext4.img
install:
Code:
fastboot flash boot roext4.img

Thank you sir, trying this now.
Yes I love my adb remount, makes things a ton easier for upgrading the market manually with adb push for example.

Michael.B. said:
Thank you sir, trying this now.
Yes I love my adb remount, makes things a ton easier for upgrading the market manually with adb push for example.
Click to expand...
Click to collapse
Worked great. Wifi and adb remount again on 2.3.1

Michael.B. said:
Worked great. Wifi and adb remount again on 2.3.1
Click to expand...
Click to collapse
glad someone got some use out of it.

Any chance you can make a version that works on CM7? I just tried this and wifi doesn't work w/ CM7.
Sent from my Nexus S using XDA App

added cm7 boot.img with ext4 hack.

My bluetooth stopped working after flashing roext4.img. it tries to activivate but fails......

Thanks for the CM7 version! Works great.
Sent from my Nexus S using XDA App

unremarked said:
Thanks for the CM7 version! Works great.
Click to expand...
Click to collapse
glad i could give something back. even if its minor.

teckhwee said:
My bluetooth stopped working after flashing roext4.img. it tries to activivate but fails......
Click to expand...
Click to collapse
I just test my bluetooth w/ the CM7 version. It doesn't work as well. I guess the ext4 hack breaks it in general. I went back to my original boot.img, and bluetooth works again.

Luxferro said:
I just test my bluetooth w/ the CM7 version. It doesn't work as well. I guess the ext4 hack breaks it in general. I went back to my original boot.img, and bluetooth works again.
Click to expand...
Click to collapse
yep. bluetooth seems to be an issue with it. i dont use bt at all so its not really an issue for me.

I confirm that there is a problem with Bluetooth

k0mpresd said:
yep. bluetooth seems to be an issue with it. i dont use bt at all so its not really an issue for me.
Click to expand...
Click to collapse
^
I'm okay with giving up Bluetooth for the performance enhance.
Sent from my Nexus S using XDA App

MMM, wifi is working but i can't complete quadrant benchmark!

MrNameless said:
MMM, wifi is working but i can't complete quadrant benchmark!
Click to expand...
Click to collapse
Quadrant doesn't work correctly on gingerbread. It happens on stock roms as well. it's just random, and sometimes it will complete.

this is voodoo kernel? do you need special recovery?

k0mpresd said:
Code:
fastboot flash boot cm7.img
Click to expand...
Click to collapse
It looks like the noauto_da_alloc flag has to be applied to the /data mount after bluetooth services are started. Where in the img did you have it specify that flag was it in the initial mount or did you remount with it at the end of init?

Zenoran said:
It looks like the noauto_da_alloc flag has to be applied to the /data mount after bluetooth services are started. Where in the img did you have it specify that flag was it in the initial mount or did you remount with it at the end of init?
Click to expand...
Click to collapse
here is the modded file. if you have a better solution, let me know and ill post an img.

Related

Patch for cm-issue 2236, accessing /emmc on Windows

Hi folks... I submitted a patch for CyanogenMod issue 2236, and was suggested to mention it here on xda to get testing/feedback.
code.google.com/p/cyanogenmod/issues/detail?id=2236
review.cyanogenmod.com/2442
(sorry, apparently as a new forum user, I can't linkify those...)
Thanks!
Someone needs to make this an update.zip
Seems to have done the trick. I built the patch and now I can see both volumes in Windows. Linux only sees the SD card though, but I might be doing something wrong.
Care to upload your vold file?
kall00, I can now see both the sdcard and emmc on Fedora 13 x86_64 and on Windows 7 x64.
Note that before this patch, there were also two ext3 partitions shared, which are the internal /data and /cache. I think this was actually very bad, as those are still mounted on the device, so you could easily corrupt the filesystem that way.
Anyway, here's my build of vold for easier testing.
CUViper, works for me on nightly build 119 under Win7 x64 -- thanks!
not sure if it's necessary, but I did chmod it to 755 to match the existing file before rebooting
Here's a update.zip for it. Install via RM or recovery.
Thanks goes to the OP.
Works great.
the posted vold works flawlessly when pushed into the 117 nightly.
and yeah, make sure to chmod to 755 after pushing or you'll get system force closes
works very well!!!
anywayz, is there any way that i can save the pictures and videos to internal memory with camera app?
Applied the voldupdate.zip and worked great. Good job!
Would this work with Shadow ROM?
Sent from my Incredible using Tapatalk.
Should work on any vanilla rom I'd imagine
whewstoosae said:
Would this work with Shadow ROM?
Click to expand...
Click to collapse
AFAIK, Shadow ROM's vold is identical, so it'll probably work.
CUViper said:
AFAIK, Shadow ROM's vold is identical, so it'll probably work.
Click to expand...
Click to collapse
Thanks man, I'll try it.
Sent from my Incredible using Tapatalk.
Tested on Ruby 1.1.4 and it works perfectly. Thanks for the patch.
CM 6.1 rc1 seems to auto mount as if this patch was used, but I still cant read emmc in win7.
Can I apply this to the rc1 or do we need to compile a new one based off of the newer code?
The change was merged last night, so hopefully we should be good for the next RC/final. But anyway, vold hasn't seen any other commits for a while, so the voldupdate.zip is still current.

[ROOT]boot.img of HKTW 2.3.4 with ADB REMOUNT support

Hi, all, after test for a many times, I finally made the boot.img of HKTW 2.3.4 with
Code:
adb remount
command support. So excited ha?
I think most of you know that the advantage of this command support.
You can push any files to system partition with adb remount first.
The result:
Code:
$adb devices
List of devices attached
TA207034Z2 device
$ adb remount
remount succeeded
That's it, click me:
PLEASE download from the attachment, I'm really sorry that my site was down.
Original Post @: http://ligux.com/t-71-1-1.html
HOW-TO:
1. You should have an unlocked atrix 4g and flash HKTW 2.3.4.
2. You should have CWM recovery, search forum to flash one by Tenfar.
3. Goto fastboot to flash this img. This forum has the way to flash the img
No one interested in this?So disappointed
Actually; I would be really interested; it's just GREAT you can push files to /system/ through adb and makes things easier. Sadly, I'm still on 1.8.3. since I can't stand using HKTW rom on my atrix (I need the phone at my work and can't rely on a debug build)... Do you think I can use this on AT&T stock 1.8.3.??? (after bootloader unlock, obviously)
Adb remount is supported on 2.3.4 boot already.
Adb root
Adb remount
Sent from my MB860 using Tapatalk
_Dennis_ said:
Adb remount is supported on 2.3.4 boot already.
Adb root
Adb remount
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
There is "adb root" command exist. I didn't know that before. My experience is outdated. I'm sorry. But if flash this boot.img, it's not necessary to run "adb root" command first
fernandodistinto said:
Actually; I would be really interested; it's just GREAT you can push files to /system/ through adb and makes things easier. Sadly, I'm still on 1.8.3. since I can't stand using HKTW rom on my atrix (I need the phone at my work and can't rely on a debug build)... Do you think I can use this on AT&T stock 1.8.3.??? (after bootloader unlock, obviously)
Click to expand...
Click to collapse
I don't think this will work on 1.8.3. Because this is based on android 2.3.4. BTW, after I test for about some days, I think this build is stable and the battery go better than 2.2.2. I did run a livewallpaper on my device and leave there for a ninght, the battery was still 100%
flzyup said:
I don't think this will work on 1.8.3. Because this is based on android 2.3.4. BTW, after I test for about some days, I think this build is stable and the battery go better than 2.2.2. I did run a livewallpaper on my device and leave there for a ninght, the battery was still 100%
Click to expand...
Click to collapse
did u reset your battery stats when flashing 2.3.4
firefox3 said:
did u reset your battery stats when flashing 2.3.4
Click to expand...
Click to collapse
No, I didn't do that
link is down
joeryu said:
link is down
Click to expand...
Click to collapse
Sorry, my host was down for some reason, I'm trying to fix it ASAP
joeryu said:
link is down
Click to expand...
Click to collapse
I uploaded the zip file to the attachment, please check.

[MOD] Webtop over HDMI Hack for Atrix GB 2.3.4 (HKTW, AT&T 4.5.91, ORFR 4.5.2A)

I am pleased to announce that I've patched the Atrix webtop files, allowing us to run webtop over HDMI on HKTW, AT&T 4.5.91 and ORFR 4.5.2A based system images (yes this will work on custom ROMs too), without the requirements of an official dock!
The goal is to enable the Webtop function over HDMI on any display, not just official Motorola Docks. There seem to be more HDMI display options that are disabled, for example: Clock Widget, Gallery, Music, Home. Sadly, none of these options actually do anything on the big screen, they just display the interface on the phone
However, Webtop works great! Just use the instructions below to replace the original DockService and PortalApp apk's.
Included are two versions of the DockService in the zip attached to this thread, one will enable only the additional Webtop mode for HDMI. The second one will be a "dev" version that enables every option, for those of you that are curious and/or want to try to get some of them to work over HDMI! Only one version of PortalApp is included, which is required for webtop to work, with both versions of the DockService.
One particularly interesting option that many of you are interested in is included in the dev build too: Mirror phone on display . Sadly, as stated above, it does not work (yet?). Will you get it to work?
Requirements:
Have one of the supported build and functional webtop flashed
Be rooted
Be able to work with adb
First, unpack the attached zip-file.
Go into the correct directory for your version.
Now run (in a terminal)
Code:
adb push DockService.apk /sdcard/
adb push PortalApp.apk /sdcard/
adb shell
# you are now in the phone shell
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
mv /system/app/DockService.apk /system/app/DockService.apk.bak
mv /system/app/PortalApp.apk /system/app/PortalApp.apk.bak
mv /system/app/DockService.odex /system/app/DockService.odex.bak
mv /system/app/PortalApp.odex /system/app/PortalApp.odex.bak
rm /data/dalvik-cache/*DockService* /data/dalvik-cache/*PortalApp*
cd /system/app
cp /sdcard/DockService.apk ./
cp /sdcard/PortalApp.apk ./
chown 0:0 ./DockService.apk
chown 0:0 ./PortalApp.apk
chmod 644 ./DockService.apk
chmod 644 ./PortalApp.apk
reboot
NOTE: if these instructions dazzle you, try Ronaldo's CWM package (for AT&T only!): http://forum.xda-developers.com/showpost.php?p=15871616&postcount=53
NOTE2: ignore errors concerning odex files if you are deodexed.
NOTE3: If you have issues with the Touchscreen Input not working, try a reboot first. If the problem doesn't go away: fastboot flash a (stock) webtop image for your base ROM. It is currently unclear what causes this problem, but my guess is a bad flash of the webtop partition, possibly CWM related. Reboot/reflash has solved the problem for a few people encountering this issue.
Thanks to Gizmo, eval & romracer!
More information on dev version
Some extra information on the different modes that are available (but currently non-functional):
Clock: Transform your phone screen into a big clock with perks. See the time from afar, set alarms, play music, view photos and get live weather information. This mode was designed for your bedside but is useful in the kitchen and as a desk clock too.
WidgetDock: Get access to the same Android widgets, apps and shortcuts as on your phone home screen. Arrange them and change the wallpaper to your liking. All of which will be saved and applied the next time your dock your phone.
Mirror: Access and display all of the phone applications on a larger display
Other: Displays non-smart mode dock apps
Gallery: View photos and videos
Music: Access, listen, and share music
There is also mention of an "easport" option, with the following description: "Entertainment detailed description goes here. To be added later."
Although not working currently, they give a good insight in what is to come
IMO, one of the best features of the Atrix right here. You're the man!
Great, I was looking forward to this. Thanks again.
Sent from rooted Atrix on 2.3.4 with unlocked bootloader using xda premium app.
_unknown said:
Today, I am pleased to announce to you a modified DockService.apk which allows us to run webtop over HDMI on HKTW, without the requirements of an official dock!
...
Major thanks go to a friend who prefers to stay anonymous, but was key in solving this problem! And as always thanks to the ever-helpful eval- for his assistance
Click to expand...
Click to collapse
Bull****, this was all you!! Awesome work, BTW =) Excited to go back to 2.3.4!
Touch pad controls dont work for me
Everything works fine
Holy **** ! That is all.
So, frist, thanx for this excelent work! Now my webtop works.
I just have one problem, my mousepad on lapdock doesnt work!
works great! thanks!
Awesome work! I only used my atrix for a few minutes before flashing 2.3.4 so I have no idea how well this worked before, but I'm pleased. All I know is when I plug in the HDMI, it restarts into the webtop mode and it works well from there. The entertainment center app crashes but that isn't as a result of this, it definitely did that when I tried to run it before.
mouse not working
loads fine but no mouse control for me either..
Same for me. The webtop loads up fine, but no mouse control on the touchpad.
_kansei_ said:
Awesome work! I only used my atrix for a few minutes before flashing 2.3.4 so I have no idea how well this worked before, but I'm pleased. All I know is when I plug in the HDMI, it restarts into the webtop mode and it works well from there. The entertainment center app crashes but that isn't as a result of this, it definitely did that when I tried to run it before.
Click to expand...
Click to collapse
Does your mouse work ? A majority, myself included, it does not ....
For the ones whose touchpad does not work.
Did you install the CG61.img or do the Update's for HKTW 2.3.4 - Roll-up of Fixes and Mods (Navalynt's Mod) that included the Webtop Fix?
I'm using Rollup tried version 1.4 and 1.5. Touchpad is broke ****.
dicksteele said:
Does your mouse work ? A majority, myself included, it does not ....
Click to expand...
Click to collapse
I was having the same problem with the mouse I fixed it by reflashing webtop from fastboot.
Sent from my MB860 using XDA App
NYG-SBXLII said:
I was having the same problem with the mouse I fixed it by reflashing webtop from fastboot.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Before I read your reply I said wtf and tried that before I gave up for the night and that was my fix also.
Now to start hacking it and get lxterminal going.
Thanks !!!
dicksteele said:
Does your mouse work ? A majority, myself included, it does not ....
For the ones whose touchpad does not work.
Did you install the CG61.img or do the Update's for HKTW 2.3.4 - Roll-up of Fixes and Mods (Navalynt's Mod) that included the Webtop Fix?
I'm using Rollup tried version 1.4 and 1.5. Touchpad is broke ****.
Click to expand...
Click to collapse
if by touchpad you mean using the screen of the phone as a touchpad, it's working fine. I don't have a lapdock to test, but I could walk over to the AT&T store in the AM to check it out.
Edit: if that is the case, and something is working on my Atrix but not on many others, I assure you it was just a lucky accident. I may be a systems engineer by date but by night I'm little more than an Android n00b. I'll gladly poke around on my device to collect info that might help others get their webtops sorted.
I successfully flashed the webtop and the touchpad is working fine. But I did notice at times, GUI became unresponsive to the touchpad (touchscreen). It it not perfect, but it works
See now this almost makes me wish I still had my Atrix...
I would love to tinker around with these APKs some more. Especially with the new options cropping up.
But, as it is I am doing it all blind... doing DEV for a phone you don't have is tricky business.
Awesome!! Worked perfect!
Installed using ADB via OP commands. Never flashed the CG61.img or the Update's for HKTW 2.3.4 - Roll-up of Fixes and Mods (Navalynt's Mod) that included the Webtop Fix and I am having absolutely NO problems using the screen as the mouse pad.
Make sure you followed all commands and set the permissions correctly with the chmod command.
No problems at all here, but I did flash the non-dev apk.... if you flashed the dev apk then that may be where the mouse pad issue is, I can not confirm.

[HOW TO] G.B on International Builds using 2ndinit (minor update 04/07/11)

Before anything............. This may Brick your phone, follow instructions and it wont
Big shoutouts to:
2nd-init------
skrilax_cz for writing this awesome trick!
edgan for getting it working on atrix with taskset
this hack:
eval for crazy loopback mount idea and all scripts
unknown for lots of helpful testing and debug
XLR88 for the system.img of GB 2.3.4
This is an example of the sort of thing that 2ndinit makes possible
but it is a quick hack and running with the wrong kernel - so still buggy
Bugs
1) The screen flips out when locked, so basically you swipe left and screen goes right.
2) No wifi
3) Camera dont work
4) Moto sign in not working
5) fingerprint
Working
1) Mobile data
2) network
3) Google sign in
4) Market
5) Calls
Will update when fixes are found and bugs are ironed out.
How to get GingerBread via 2ndinit on a locked bootloader for motorola atrix
Tools you need
Adb or Rootexplorer, 2ndinit.apk, terminal
Fastboot
Install 2ndinit.apk
Reboot
in terminal type
ls -a /sys/kernel/debug
Click to expand...
Click to collapse
should get output not
...
Click to expand...
Click to collapse
Download this ...........http://download839.mediafire.com/gv6kzdu34z3g/lcldnltaqj8xd9x/2ndGB.tgz
extract this to sdcard
Download this ...........http://hotfile.com/dl/122055970/0a6dfce/moto-fastboot.zip.html
Extract to sdcard
Delete everything in /preinstall
adb shell
su
cd /preinstall
rm -rf
Click to expand...
Click to collapse
copy 2nd-init, taskset, busybox to /preinstall
In ternimal
chmod 755 2nd-int
chmod 755 taskset
chmod 755 busybox
Click to expand...
Click to collapse
Rename hk. Img to system.img to and then copy to /preinstall folder
copy files from /ETC/rootfs/ to /system/etc/rootfs/ and set permissions
chmod 644 /system/etc/rootfs/*
Click to expand...
Click to collapse
copy this to /system/bin/ download and add gb directory to /data/ so it becomes /data/gb/
In terminal type
ls -a /sys/kernel/debug
Click to expand...
Click to collapse
you should get nothing at all
reboot.....
Backup your data this is a recommendation just in case
reboot again...........
when rebooting hold volume down then scroll down to EARLY USB ENUMERATION then volume up (do this everytime you want gingerbread)
wait.............
You should successfully boot into GingerBread... Congradulations
getting back to froyo
reboot
If all this fails, install 2ndinit.apk from here
Then repeat this tutorial...
Sorry about the crap video
WATCH HERE
If anyone can help to solve the flip of screen here is some clues that may help
1) screen is working prefectly until screen turns off, then it flips
Glad my work could be of use =)
And thanks for taking this off my hands while I'm away... hope you can fix the touch screen left-right input flip ... if anyone has any ideas, PM me, _unknown and stevendeb25. Here's to hoping all international users can enjoy 2.3.4 soon!
PS. haha thanks for quoting all my cursing in IRC about my /data failures
How my hack works
For international devs who want an idea of how I did it (before stevendeb25's tutorial & release) the following details my mount_ext3.sh:
Loopback hack only loads if you fastboot menu to early USB enum, so, run if ro.usb_mode==debug (plus helps us debug to adb early... why /system/etc/rootfs/default.prop we copy to / has ro.secure=0 & persist.service.adb.enable=1) In addition to default.prop we copy, extracted files from GB's ramdisk:, /init, /init.rc (modified, comment out mounting /system) and ueventd.rc from etc/rootfs, plus symlink /sbin/ueventd->/init.
Next, mknod and mount /preinstall rw, where we keep taskset, 2nd-init and busybox binaries, as well as system.img (CG60 from hktw 2.3.4 sbf.) It's probably already in /dev/block/ but this varied across froyo builds so mknod and mount rw to be safe. Good idea to use /preinstall/busybox from now on as /system mount dis/appears.
e2fsck -y the system.img and then losetup the loopback mount, umount -f -l /system, and mount -t ext3 <loopbackdevice> /system. For debug cat out /proc/mounts to a file in /preinstall or /data, actually I also append ">>/preinstall/debug 2>&1" to every command. Finally, now you can (taskset) 2nd-init your new system!
Unfortunately, seems necessary to fastboot -w or just rm -r /data/* between boots of froyo and GB. Annoying, but I couldn't easily get a GB-only /data mounted.
Now, can you fix the input flip left-right after lock screen? Clues are: it doesn't happen if this trick is tried on GB kernel (with Froyo ramdisk, system, and same 2nd-init trick.) Also, it persists after warm reboot, GB->GB. Pulling in /system/lib/hw from Froyo didn't help. Tho you'll want to bring back (and insmod) aev.ko, evfwd.ko, plus revert dhd.ko to Froyo version, as the first two are in-kernel on GB, and the latter seems to differ. I am fairly confident most bugs can be fixed by replacing (lock screen? nvrm_daemon?) pieces of GB userspace with Froyo versions in system.img. I just lost a bit of ambition after finding the fastboot oem unlock in the BL plus I will be away for a bit.
So, good luck to stevendeb25 and all you non-ATT Atrix hackers!
At least International users get some Gingerbread love! Good job guys!
i can't believe!!!
what a great new!!!
thanks guys!
the video seems to be really amazing!
wanna try it!!!!
that bootscreen looks awesome at first part in the video, is that stock?? oo
Excellent work brothers, you guys are really making us proud as well as you should be!
Very good job!
Now I can start dreaming about GB in my non-att atrix
You sexy, sexy man! Rawr!!
Great news
Sent from my MB860 using XDA Premium App
stratax said:
that bootscreen looks awesome at first part in the video, is that stock?? oo
Click to expand...
Click to collapse
Yeah stock orange uk bootscreen
Sent from my MB860 using XDA Premium App
Lol..
Awesome Steven, lookin' forward
bongd said:
You sexy, sexy man! Rawr!!
Click to expand...
Click to collapse
Stock Bell Atrix on Rogers with updated radio, Rooted, deodexed, Honeycomb theme, and frozen!
Released ............ enjoy guys, if dont want flip screen, dont lock the phone
This remember me when we try to put android on Windows Mobile Phones!haha
Anyway, nice work man, Let's play a lil
Wow, good work guys. I am sure this has been torture for international users. For the past couple of weeks, we in the states (or anyone on at&t) have been like kids on Christmas, while everyone else sits on the sidelines It's a good thing the 2nd init port got put to good use.
HolySorento said:
This remember me when we try to put android on Windows Mobile Phones!haha
Anyway, nice work man, Let's play a lil
Click to expand...
Click to collapse
Android has been ported to the Iphone, but as far as I know only to the older generations.
c'mon guys, are you trying that??
post your opinions!!
stevendeb25 said:
Released ............ enjoy guys, if dont want flip screen, dont lock the phone
Click to expand...
Click to collapse
Great work steve
Steven, is there no way for you to use drivers from the hktw build to fix wifi and camera?
Or do those require kernel level access or something?
Sent from my MB860 using XDA Premium App
stevendeb25 said:
Yeah stock orange uk bootscreen
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Think anyone could post this? It looks much better than the ATT one.
tasty_boy said:
c'mon guys, are you trying that??
post your opinions!!
Click to expand...
Click to collapse
I'd love to try but without wifi and that flip issue I think I'll pass this version.
Sinful Animosity said:
Steven, is there no way for you to use drivers from the hktw build to fix wifi and camera?
Or do those require kernel level access or something?
Click to expand...
Click to collapse
Other way around... if you pull in dhd.ko from the latest Froyo build you flashed on your system, as well as aev.ko and evfwd.ko (and /system/etc/firmware or wifi/ ?) into loopback mounted /system you will have more chance of working wifi in HKTW2.3.4. (HINT HINT you could do this directly in the mount_ext3.sh script... copy useful 2.2 stuff to /preinstall, copy back into new /system after unmount,remount, even insmod if you have to...)
Remember, this trick produces a mismatch between /system version (GB,2.3.4) and kernel version in boot.img which is actually running. We can take care of ramdisk post-hoc before 2nd-init but older kernel and its API is still in place so pieces of HKTW userspace will have to be replaced/modded to fix bugs. This version of mount_ext3 is an early release for the hackers who want to tinker until it works... good luck! I will have only web and ssh access off and on for 10 days but can answer any questions by PM, on IRC or here..

New Ubuntu port!

I want to run this on Samsung galaxy s4 i9505 jfltexx.
Anyone want to work on this?
Im willing to help in anyway i can
Sent from my GT-I9505 using xda app-developers app
Update: port is almost ready
Trying to sort a few compile errors
I would like to see this happen.
Relys said:
I would like to see this happen.
Click to expand...
Click to collapse
Me too
Sent from my GT-I9505G using Tapatalk
Awesome, can you dualboot it? And how big is the port rom?
Sent from my GT-I9505 using Tapatalk
JustSueMe said:
Update: port is almost ready
Trying to sort a few compile errors
Click to expand...
Click to collapse
Need any help?
Sent from my GT-I9505 using Tapatalk
Download link ! Alpha !
http://www.datafilehost.com/d/44a25a60
link is to download phablet
instructions:
reboot to recovery
wipe all partitions
flash phablet in above link
flash trusty-preinstalled-touch-armhf.zip [u can find on cdimages.ubuntu.com]
reboot phone to system
--
at this point youll have a black screen and no activity
plug phone into pc
grab this file : (70-jfltexx.rules) http://www.datafilehost.com/d/17d6dd77
now open terminal
$ su
$ adb push 70-jfltexx.rules /usr/lib/lxc-android-config/
$ reboot
phone will look like its doing nothing for a bit, but wait.
now it will boot back up like normal but you will have a ubuntu touch gui
BUGS:
no conectivity
no sound
edge swipe is small but works without case
camera
frame jumps to the right for some apps occasionally (unsure if thats on purpose of buggy... i vote buggy)
app crashing (maybe reason for camera crash?)
doesnt show imei
no sdcard mounted
terminal app doesnt even work so need to use adb to run commands
enjoy lol ... note alpha in title if anyone wants to complain ... also note only you are responsible for what happens to your device.
now have connectivity via reverse tether
adb root
adb shell setprop sys.usb.config rndis,adb
if you get permission error use adb server as root
ubuntu network manager will show that samsung android is connecting.
open network settings edit that connection and change auto DHCP to shared
adb shell
run this command (logged into phone)
dhclient usb0 -v
now on phone open webbrowser and you should be able to connect
just got WIFI !
haha progress
adb shell
insmod /system/lib/modules/dhd.ko firmware_path=/system/etc/wifi/bcmdhd_sta.bin nvram_path=/system/etc/wifi/nvram_net.txt
now wifi will turn on
make it auto load at boot
touch /data/local/userinit.sh
add to the file :
#!/bin/bash
insmod /system/lib/modules/dhd.ko firmware_path=/system/etc/wifi/bcmdhd_sta.bin nvram_path=/system/etc/wifi/nvram_net.txt
make it run
chmod +x /data/local/userinit.sh
help !
im trying to fix the gsm
here is my output
[email protected]:/# nmcli dev
DEVICE TYPE STATE
/ril_0 gsm disconnected
wlan0 802-11-wireless connected
[email protected]:/etc/NetworkManager/system-connections# ls
TALKTALK-FCF354 Three
TalkTalk--* is my WIFI
Three is my mobile 3g data
so ill try to load Three
[email protected]:/etc/NetworkManager/system-connections# nmcli con up id Three
Error: Connection activation failed: The connection was not supported by oFono.
here is the contents of Three :
[connection]
id=Three
uuid=39a02ed3-d946-45f8-9abb-81ef997add03
type=gsm
autoconnect=false
[ppp]
refuse-eap=true
refuse-chap=true
refuse-mschap=true
refuse-mschapv2=true
nobsdcomp=true
nodeflate=true
no-vj-comp=true
[ipv4]
method=auto
[serial]
baud=115200
[gsm]
number=*99#
username=three
apn=3internet
contents of TalkTalk
[connection]
id=TALKTALK-FCF354
uuid=1bcf8cdf-9152-49de-b279-7770e94e5006
type=802-11-wireless
[802-11-wireless]
ssid=TALKTALK-FCF354
mode=infrastructure
mac-address=5C:F8:A1:90:2F:FB
security=802-11-wireless-security
[802-11-wireless-security]
key-mgmt=wpa-psk
auth-alg=open
psk=Password1
[ipv4]
method=auto
[ipv6]
method=auto
Why is TalkTalk supported and Three is not ?
as i understand it it uses https://github.com/rilmodem/ofono
AND if fixed this configuration may only give 3g data connection on the THREE 3 UK newtork not calls or sms but one step at a time/
JustSueMe said:
http://www.datafilehost.com/d/44a25a60
link is to download phablet
instructions:
reboot to recovery
wipe all partitions
flash phablet in above link
flash trusty-preinstalled-touch-armhf.zip [u can find on cdimages.ubuntu.com]
reboot phone to system
--
at this point youll have a black screen and no activity
plug phone into pc
grab this file : (70-jfltexx.rules) http://www.datafilehost.com/d/17d6dd77
now open terminal
$ su
$ adb push 70-jfltexx.rules /usr/lib/lxc-android-config/
$ reboot
phone will look like its doing nothing for a bit, but wait.
now it will boot back up like normal but you will have a ubuntu touch gui
BUGS:
no conectivity
no sound
edge swipe is small but works without case
camera
frame jumps to the right for some apps occasionally (unsure if thats on purpose of buggy... i vote buggy)
app crashing (maybe reason for camera crash?)
doesnt show imei
no sdcard mounted
terminal app doesnt even work so need to use adb to run commands
enjoy lol ... note alpha in title if anyone wants to complain ... also note only you are responsible for what happens to your device.
Click to expand...
Click to collapse
Will this work with an ATT that has a locked bootloader that needs loki file for the kernel?
toxicpaulution said:
Will this work with an ATT that has a locked bootloader that needs loki file for the kernel?
Click to expand...
Click to collapse
well for one this is for jfltexx, and secondly if the boot loader is locked i doubt that could flash it as u need a new the boot.img.
if you want it on att model you ill prob need to buid depreciated ubuntu touch.
depreciaed UT boots android then ubuntu in a container
this boots ubuntu then andriod in container.
JustSueMe said:
well for one this is for jfltexx, and secondly if the boot loader is locked i doubt that could flash it as u need a new the boot.img.
if you want it on att model you ill prob need to buid depreciated ubuntu touch.
depreciaed UT boots android then ubuntu in a container
this boots ubuntu then andriod in container.
Click to expand...
Click to collapse
Well see with ATT we can boot custom roms(MDL users) as long as the kernel is already lokidokied, or you can flash the loki zip and it will bypass the ATT check and allow you to boot a custom rom, Now seeing how this is based of CM10.2(thats what the file is saying so i am just taking a guess) if I flashed the Loki zip after flashing the rom would it work? But I am doing a backup as of now and I am going to test and see if it works :3 I will report back lol
---------- Post added at 01:49 PM ---------- Previous post was at 01:03 PM ----------
toxicpaulution said:
Well see with ATT we can boot custom roms(MDL users) as long as the kernel is already lokidokied, or you can flash the loki zip and it will bypass the ATT check and allow you to boot a custom rom, Now seeing how this is based of CM10.2(thats what the file is saying so i am just taking a guess) if I flashed the Loki zip after flashing the rom would it work? But I am doing a backup as of now and I am going to test and see if it works :3 I will report back lol
Click to expand...
Click to collapse
Didn't work, Getting status 7 which would mean I would have to edit the update script so it doesn't just look for the inital phone. I will do that now and try again.
toxicpaulution said:
Well see with ATT we can boot custom roms(MDL users) as long as the kernel is already lokidokied, or you can flash the loki zip and it will bypass the ATT check and allow you to boot a custom rom, Now seeing how this is based of CM10.2(thats what the file is saying so i am just taking a guess) if I flashed the Loki zip after flashing the rom would it work? But I am doing a backup as of now and I am going to test and see if it works :3 I will report back lol
---------- Post added at 01:49 PM ---------- Previous post was at 01:03 PM ----------
Didn't work, Getting status 7 which would mean I would have to edit the update script so it doesn't just look for the inital phone. I will do that now and try again.
Click to expand...
Click to collapse
the base may be cm10 but it doesnt boot cm10. the boot.img gets flashed and it boots ubuntu , the cm part is in a container within ubuntu
i dont think att will be able to use this is the bootloader cant be flashed
JustSueMe said:
the base may be cm10 but it doesnt boot cm10. the boot.img gets flashed and it boots ubuntu , the cm part is in a container within ubuntu
i dont think att will be able to use this is the bootloader cant be flashed
Click to expand...
Click to collapse
Yeah changing the updater script didnt do the job :/ lame lol well it was work the try, I will follow this htread though seems promising.
toxicpaulution said:
Yeah changing the updater script didnt do the job :/ lame lol well it was work the try, I will follow this htread though seems promising.
Click to expand...
Click to collapse
okay it wont let me adb push the file says bash: adb: command not found
edit: im running now but the connectivity through reverse thether isnt working. btw im on the att s4
JustSueMe said:
haha progress
adb shell
insmod /system/lib/modules/dhd.ko firmware_path=/system/etc/wifi/bcmdhd_sta.bin nvram_path=/system/etc/wifi/nvram_net.txt
now wifi will turn on
make it auto load at boot
touch /data/local/userinit.sh
add to the file :
#!/bin/bash
insmod /system/lib/modules/dhd.ko firmware_path=/system/etc/wifi/bcmdhd_sta.bin nvram_path=/system/etc/wifi/nvram_net.txt
make it run
chmod +x /data/local/userinit.sh
Click to expand...
Click to collapse
I have successfully ported the zip to the SGH-I337 AT&T model same as yours wifi no data after fixes. Are you having trouble with the roms sliding from the lockscreen to home trouble?
---------- Post added at 02:34 AM ---------- Previous post was at 01:59 AM ----------
Joeyxc said:
I have successfully ported the zip to the SGH-I337 AT&T model same as yours wifi no data after fixes. Are you having trouble with the roms sliding from the lockscreen to home trouble?
Click to expand...
Click to collapse
link for att or tmobile http://www.androidfilehost.com/?fid=23252070760974893
Enjoy
This is just the cm, still follow the other instructions for everything else
http://www.youtube.com/watch?v=mJLKX_QWSpc&feature=youtu.be
Joeyxc said:
I have successfully ported the zip to the SGH-I337 AT&T model same as yours wifi no data after fixes. Are you having trouble with the roms sliding from the lockscreen to home trouble?
---------- Post added at 02:34 AM ---------- Previous post was at 01:59 AM ----------
link for att or tmobile http://www.androidfilehost.com/?fid=23252070760974893
Enjoy
This is just the cm, still follow the other instructions for everything else
http://www.youtube.com/watch?v=mJLKX_QWSpc&feature=youtu.be
Click to expand...
Click to collapse
So I should flash that first and then the others as stated?
toxicpaulution said:
So I should flash that first and then the others as stated?
Click to expand...
Click to collapse
Yup! Let me know if you run into any issues don't forget to thank if it worked!
Sent from my SGH-I337 using Tapatalk
Joeyxc said:
Yup! Let me know if you run into any issues don't forget to thank if it worked!
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
Forgot you need to use the Loki file for att, I'm doing adb on my other lappy haha xD then I'll boot it
Sent from my SGH-I337 using Tapatalk

Categories

Resources