!!!!!! 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
Related
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
It's important for everyone to know that since this is a development thread, most, if not all conversation should be dedicated to helping us boot the ROM. All questions related to and including "will our device be able to handle Jellybean?" should be moved to the following thread: http://forum.xda-developers.com/showthread.php?t=1736089
Our biggest problem so far: There are incompatibilities with Jellybean and the Adreno drivers, which our phone needs to function. We can't just remove the Adreno drivers and boot the ROM (I tested this, by removing them from our latest CM9 nightly, which wouldn't boot as a result. I also removed the Adreno drivers and used the Jellybean ramdisk, framework, libs, and bin files but still no boot.).
PureMotive's port
I booted my source-built Jellybean.
Status: ALPHA
Working
Root
ADB
3G
WiFi
Calls (outgoing and incoming)
Signal
UI
Soft keys + lights
RIL
GPS
Brightness settings
Sync
SMS
MMS
Gmail
Gtalk
Twitter
Facebook
Audio
Downloads
Native screenshot (should work now)
Google Now
Untested
Video
Bluetooth
Camera
Broken
Butter
Browser (default)
HWA
Click to expand...
Click to collapse
Albinoman's port
Check his thread located here
Click to expand...
Click to collapse
PORTING FILES:
Code:
Jellybean SDK: [URL]http://d-h.st/EUH[/URL]
Jellybean Ramdisk: [URL]http://d-h.st/XhF[/URL]
Boot.img used in Tiny's port: [URL]http://d-h.st/a0C[/URL]
Vicious Jellybean (VZW GNex port): [URL="http://rootzwiki.com/topic/28486-rom-vicious-toro-jellybean-v3-100-functional-franco-kernel-beats-audio-mods-optimized-link-in-op-for-stock-kernel-added-112am-06302012/"]Vicious Jellybean[/URL]
On vacation. When I get back next week I'll check it out
Sent from my unrootable DROID2
where the hell is the ramdisk
Just wanted to mention my scan of the ramdisk the other night didn't lead to anything conclusive. I checked real quick yesterday I think but didn't really have time to look in depth. I didn't see a problem with the way the system mounted so something else is causing it. I'm trying to port it right now. We'll see what happens.
Maybe I should give it a try.
How about paste bin a logcat?
Here is my current logcat
http://paste.ubuntu.com/1074131/
Sent from my Droid Incredible using xda premium
Shano56 said:
where the hell is the ramdisk
Click to expand...
Click to collapse
Posted in the OP.
PonsAsinorem said:
How about paste bin a logcat?
Click to expand...
Click to collapse
We cannot get a logcat with the Jellybean ramdisk, even with these edits to default.prop:
Code:
persist.sys.usb.config=mass_storage,adb
persist.service.adb.enable=1
persist.sys.strictmode.disable=true
persist.service.adb.root=1
ro.secure=0
ro.allow.mock_location=1
ro.debuggable=1
service.adb.root=1
The error that follows is this:
Code:
'system/bin/sh' failed no such file or directory
Adding a "sh" file to /bin results in other errors (don't have them right now)
The only way a logcat will work is if we use the ramdisk from a CM9 ROM in addition to the CM9 libs.
PureMotive said:
Posted in the OP.
Click to expand...
Click to collapse
hehe now u post it. ty
edit: i thought you needed it extracted
PureMotive said:
Posted in the OP.
We cannot get a logcat with the Jellybean ramdisk, even with these edits to default.prop:
Code:
persist.sys.usb.config=mass_storage,adb
persist.service.adb.enable=1
persist.sys.strictmode.disable=true
persist.service.adb.root=1
ro.secure=0
ro.allow.mock_location=1
ro.debuggable=1
service.adb.root=1
The error that follows is this:
Code:
'system/bin/sh' failed no such file or directory
Adding a "sh" file to /bin results in other errors (don't have them right now)
The only way a logcat will work is if we use the ramdisk from a CM9 ROM in addition to the CM9 libs.
Click to expand...
Click to collapse
I got a port booting with your jellybean ramdisk. It won't go far but I'm about to provide a logcat after testing some changes. Toolbox and busybox work. I ported from the gnex. No boot screen but it does start to load files. Maybe you guys can figure it out from here. I'll upload it and my logcat after I test my zip.
Logcat linked below:
http://paste.ubuntu.com/1075642/
Initial Port Below:
http://d-h.st/shx
Upload!!!! Lol
Sent from my Droid Incredible using xda premium
tiny4579 said:
I got a port booting with your jellybean ramdisk. It won't go far but I'm about to provide a logcat after testing some changes. Toolbox and busybox work. I ported from the gnex. No boot screen but it does start to load files. Maybe you guys can figure it out from here. I'll upload it and my logcat after I test my zip.
Logcat linked below:
http://paste.ubuntu.com/1075642/
zip file coming next.
Click to expand...
Click to collapse
Did you use the ramdisk from the OP or the boot.img I sent you? I got it to the point where it would load the framework .jar files, but haven't encountered what you did in your logcat so I'd consider it progress lol. Seems to be an issue with EGL...
EDIT: Nevermind lol
The error that follows is this:
Code:
'system/bin/sh' failed no such file or directory
Adding a "sh" file to /bin results in other errors (don't have them right now)
Sounds to me like you are missing /bin/mksh either in ROM or in symlink in updater
Sent from my PG06100 using xda premium
Just wanted to first of all say thanks for this - it's awesome that this is even being worked on. We have such an awesome dev community. Secondly, just wanted to offer my support in any way possible. I don't have a lot of experience with porting Android, but I do have pretty good Linux system knowledge and a willingness to experiment. Downloading tiny's build now, going to mess around with some system files and see what happens. Thanks again guys!
Cm is going to working on cm10.
http://briefmobile.com/cyanogenmod-cm10-coming-with-jelly-bean-source-code-release
Sent from my ADR6300 using xda app-developers app
tiny4579 said:
I got a port booting with your jellybean ramdisk. It won't go far but I'm about to provide a logcat after testing some changes. Toolbox and busybox work. I ported from the gnex. No boot screen but it does start to load files. Maybe you guys can figure it out from here. I'll upload it and my logcat after I test my zip.
Logcat linked below:
http://paste.ubuntu.com/1075642/
Initial Port Below:
http://d-h.st/shx
Click to expand...
Click to collapse
Hey tiny4579 could you post what you changed/added in your build?
Albinoman said:
Hey tiny4579 could you post what you changed/added in your build?
Click to expand...
Click to collapse
I don't remember quite what I did and I'm not in a position to test but what if you take evervolv as a base and replace the app and framework folders with the ones from my port and the boot.img with the one from the port. It probably won't work by a long shot but at least it's worth a try.
Sent from my Galaxy Nexus using Tapatalk 2
I see progress! I will download your port right now and see what I can help you with.
tiny4579 said:
I don't remember quite what I did and I'm not in a position to test but what if you take evervolv as a base and replace the app and framework folders with the ones from my port and the boot.img with the one from the port. It probably won't work by a long shot but at least it's worth a try.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'll try that later today. What version of evervolv are you using?
Sent from my Droid Incredible using xda premium
Albinoman said:
I'll try that later today. What version of evervolv are you using?
Sent from my Droid Incredible using xda premium
Click to expand...
Click to collapse
I was testing with 2.2.0a1.
Sent from my Galaxy Nexus using Tapatalk 2
This will only modify what needs to be tweak in the build.prop.
It will not modify anybody else's build.prop work.
This means it can be used after you install a custom ROM and
keep any changes your dev has made to their own build.prop.
I have screen shots of my 3 Mps DSL Line and my LTE.
If it gives any indication about how much more performance gain there is
WiFi gives me up to 2.9 Mbps normally.
LTE gives me close to 30 Mbps normally.
Revision 2:
little less aggressive on the phone itself
little bit better WiFi and LTE speeds
cleaned up TONS of code and named everything!
Also the 2nd version will save a backup so you
can restore your old build.prop if you do not like
the changes that were made from from the tweaks.
AND it should keep the original build.prop.
Mind you, the undoer will only work with version 2.
you can also make a swap file (paging file like windows)
command will be
# busybox mkswap /dev/block/zram0
# chmod 077 /dev/block/zram0
# reboot
how did you install an ULV kernel on your droid 4?
dewhashish said:
how did you install an ULV kernel on your droid 4?
Click to expand...
Click to collapse
through an inti.d script
Won't install
I can't get these to install, using safestrap 3.0. Any ideas what I am doing wrong?
zeroktal said:
I can't get these to install, using safestrap 3.0. Any ideas what I am doing wrong?
Click to expand...
Click to collapse
it has only been tested on SS211.
I believe there are differences in the way it reads
and mounts the partitions...
what does the error say?
Not to sound stupid, but will this work on Eclipse 1.3.4 for D4?
Sent from my DROID4 using xda app-developers app
panamakevin said:
Not to sound stupid, but will this work on Eclipse 1.3.4 for D4?
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
the way It is set it up -should- in theory work with any ROM made for the D4.
Can we get this written for ss305?
jkieffer46 said:
Can we get this written for ss305?
Click to expand...
Click to collapse
yes give me a little while to install and reconfigure for ss3
jkieffer46 said:
Can we get this written for ss305?
Click to expand...
Click to collapse
I have tried and failed miserably! I am no means a "true" programmer BUT
I have a work around for the people with SS3. Although it does involve a
terminal emulator which is free and the Google Play Store link is BAM!
I will make a flashable fix in the morning with instructions on how to do it.
I will also have a screenshot of what to type as well. The script will still do
the same thing as the flashable BUT in the terminal (manual way)
Just ran the .sh
I just modified and ran the SH from the command line. Only had to remove one > per file. Thanks, my speed increase isn't amazing, but its solid. You are Awesome.
Is there a way to flash this in ss305 yet or what
No, I'm sorry, haven't time to work on it. right now the work around is through a shell and reboot
Sent from my DROID4 using xda premium
Ok ill wait. I dont know how to do anything other than flash zips
Does it have any tweaks for GSM/HSDPA? The 3G is really poor on Droid 4.
I am not responsible for any possible bad effects which may result from using included software! You flash it on your own risk!
Probably it will work in the P905 version, because I flashed the a P905 kernel in my P905M without problems. But, as usual, it is your risk.
User esgie confirmed that it works on SM-P905 too!
STOCK compiled with SELinux setenforce enabled
Kernel base: compiled from Samsung sources without modifications (opensource.samsung.com)
Kernel ramdisk: extracted from stock image
Features: setenforce command working
WARNING!
FLASHING THIS WILL TRIP KNOX AVOIDING YOUR WARRANTY!
Known issues
WiFi gets a little screwy. To fix it edit /system/build.prop, change the parameter ro.securestore.support from true to false and reboot.
Installation
flash using ODIN (AP/PDA)
Image sha1sum
b85360a80f6205269b75d9dfabccac211a224d46
CREDITS
- Graeme Hill`s Dev Blog (http://graemehill.ca/compiling-permissive-android-kernel)
- osm0sis user Android Image Kitchen tool (http://forum.xda-developers.com/showthread.php?t=2073775)
- Samsung (opensource.samsung.com)
- esgie Kernel STOCK RELOADED (http://forum.xda-developers.com/showthread.php?t=2771469)
No one interested?
Thanks a lot. Will try it.
Sent from my GT-N7100 using XDA Premium 4 mobile app
rodpp said:
I am not responsible for any possible bad effects which may result from using included software! You flash it on your own risk!
Probably it will work in the P905 version, because I flashed the a P905 kernel in my P905M without problems. But, as usual, it is your risk.
STOCK compiled with SELinux setenforce enabled
Kernel base: compiled from Samsung sources without modifications (opensource.samsung.com)
Kernel ramdisk: extracted from stock image
Features: setenforce command working
WARNING!
FLASHING THIS WILL TRIP KNOX AVOIDING YOUR WARRANTY!
Known issues
WiFi gets a little screwy. To fix it edit /system/build.prop, change the parameter ro.securestore.support from true to false and reboot.
Installation
flash using ODIN (AP/PDA)
CREDITS
- Graeme Hill`s Dev Blog (http://graemehill.ca/compiling-permissive-android-kernel)
- osm0sis user Android Image Kitchen tool (http://forum.xda-developers.com/showthread.php?t=2073775)
- Samsung (opensource.samsung.com)
- esgie Kernel STOCK RELOADED (http://forum.xda-developers.com/showthread.php?t=2771469)
Click to expand...
Click to collapse
Hangs on boot before the Samsung logo.
Sent from my SM-P905M using XDA Premium HD app
gorcutt said:
Hangs on boot before the Samsung logo.
Sent from my SM-P905M using XDA Premium HD app
Click to expand...
Click to collapse
Hi,
I just downloaded the file from this post and checked the sha1sum against the original file that I uploaded and it´s ok. The sha1sum value is b85360a80f6205269b75d9dfabccac211a224d46. So there is no file corruption problem.
Please check if your file has the same sha1sum.
Tonight I´ll flash this file again in my tablet and verify if it works. It´s highly improbable that I uploaded the wrong file, but I´ll check flashing it.
As soon as possible I´ll update here the result of this test.
Regards,
Rodrigo.
Awesome!
Flashed, seems to boot ok on SM-P905
Great job.
Seems to be working fine! Boots as permissive and setenforce 0/1 working fine.
Great job. Now we are waiting for at least some basic overclocking and governors implementation
esgie said:
Awesome!
Flashed, seems to boot ok on SM-P905
Great job.
Seems to be working fine! Boots as permissive and setenforce 0/1 working fine.
Great job. Now we are waiting for at least some basic overclocking and governors implementation
Click to expand...
Click to collapse
Thank you very much for confirm that it works on SM-P905, I'll include this information on the first post.
If you find some WiFi issues don't forget to edit /system/build.prop, change the parameter ro.securestore.support from true to false and reboot.
Regards,
Rodrigo.
Already had the property changed in my build.prop, so i'm not exactly sure if the wifi works out of the box or not. Although I confirm that it DOES work with the build.prop modification
And by "does work" I meant both wifi and mobile radio working flawlessly.
gorcutt said:
Hangs on boot before the Samsung logo.
Sent from my SM-P905M using XDA Premium HD app
Click to expand...
Click to collapse
rodpp said:
Hi,
I just downloaded the file from this post and checked the sha1sum against the original file that I uploaded and it´s ok. The sha1sum value is b85360a80f6205269b75d9dfabccac211a224d46. So there is no file corruption problem.
Please check if your file has the same sha1sum.
Tonight I´ll flash this file again in my tablet and verify if it works. It´s highly improbable that I uploaded the wrong file, but I´ll check flashing it.
As soon as possible I´ll update here the result of this test.
Regards,
Rodrigo.
Click to expand...
Click to collapse
Hi there, I tested here and the image is working fine here. The user esgie just confirmed that too, in a P905. Please check the sha1sum of your downloaded image file.
Regards,
Rodrigo.
rodpp said:
Hi,
I just downloaded the file from this post and checked the sha1sum against the original file that I uploaded and it´s ok. The sha1sum value is b85360a80f6205269b75d9dfabccac211a224d46. So there is no file corruption problem.
Please check if your file has the same sha1sum.
Tonight I´ll flash this file again in my tablet and verify if it works. It´s highly improbable that I uploaded the wrong file, but I´ll check flashing it.
As soon as possible I´ll update here the result of this test.
Regards,
Rodrigo.
Click to expand...
Click to collapse
I probably did something wrong.
I've downloaded again and wiill try once more.
MD5 f39207bd4c45b1854372cd519942a6c2
SHA1 b85360a80f6205269b75d9dfabccac211a224d46
Thanks.
Sent from my GT-N7100 using XDA Premium 4 mobile app
As we all can see, our devices lacks of community support.
I wonder if you are the first person on the planet who managed to prepare an environment and compile P905(x) kernel succesfuly
May I ask you if have any plans to proceed with the kernel developement?
Please integrate fauxsound
esgie said:
As we all can see, our devices lacks of community support.
I wonder if you are the first person on the planet who managed to prepare an environment and compile P905(x) kernel succesfuly
May I ask you if have any plans to proceed with the kernel developement?
Click to expand...
Click to collapse
Unfortunately I don't have enough free time, so I don't have plans to work in kernel development. I did this because I was needing it to install some stuffs in my tablet and decided to share it here o XDA where I always found useful things.
If someone wants simple modifications and points some links explaining that I can try without problems.
And if someone have problems preparing an environment to compile the kernel, let me know, I'll be very happy to help.
Regards,
Rodrigo.
koko115 said:
Please integrate fauxsound
Click to expand...
Click to collapse
Do you have a link?
Honestly, I don't know what fauxsound is!
rodpp said:
Do you have a link?
Honestly, I don't know what fauxsound is!
Click to expand...
Click to collapse
Well, i'm not the one who asked this nor I have ever heard about it, but by curiousity I googled this. Got link for this app at Google Play. There are github links in app description to patches that needs to be added to kernel to make this work.
Just can't see Note Pro in officially supported devices -list and don't know can this device even be supported. There reads "Unofficially Supporting: Any Phones using Qualcomm Audio Chip WCD93xx chipsets." But I don't know which chipset NP12.2 got.
Spere said:
Well, i'm not the one who asked this nor I have ever heard about it, but by curiousity I googled this. Got link for this app at Google Play. There are github links in app description to patches that needs to be added to kernel to make this work.
Just can't see Note Pro in officially supported devices -list and don't know can this device even be supported. There reads "Unofficially Supporting: Any Phones using Qualcomm Audio Chip WCD93xx chipsets." But I don't know which chipset NP12.2 got.
Click to expand...
Click to collapse
Thanks, it seems simple if the audio chip is compatible. I'll try to include this in the kernel.
Thanks, Rodrigo for the great work!
Finally i was able to get Ubuntu running using linux complete installer.
Its a shame there's so little development for this great device.
I wish i had skills to do some.
Thanks, from Piracicaba-SP
js345 said:
Thanks, Rodrigo for the great work!
Finally i was able to get Ubuntu running using linux complete installer.
Its a shame there's so little development for this great device.
I wish i had skills to do some.
Thanks, from Piracicaba-SP
Click to expand...
Click to collapse
Yes, one of my motivations to compile this kernel was to boot Linux images too.
Regards,
Rodrigo.
Enviado de meu SM-P905M usando Tapatalk
rodpp said:
Thanks, it seems simple if the audio chip is compatible. I'll try to include this in the kernel.
Click to expand...
Click to collapse
I tried to compile the kernel with the patches sugested by the Fauxsound developer but, unfortunately, I have no success.
Probably it will be necessary more kernel modifications to compile it with the Fauxsound patches.
Enviado de meu SM-P905M usando Tapatalk
Hi,
I have a question about your kernel.
does it contains a root feature ?
I am running XXUANI1 firmware on P900 (wifi version), and have tried the auto root from Chainfire.
it does not work well (I think it was release for a previous firmware), and give a lot of random reboot.
I was thinking that may be I could flash a kernel accepting to work with su.bin
thanks for any information.
Olivier
orobin said:
Hi,
I have a question about your kernel.
does it contains a root feature ?
I am running XXUANI1 firmware on P900 (wifi version), and have tried the auto root from Chainfire.
it does not work well (I think it was release for a previous firmware), and give a lot of random reboot.
I was thinking that may be I could flash a kernel accepting to work with su.bin
thanks for any information.
Olivier
Click to expand...
Click to collapse
The kernel is for P905M/P905...
Well I got permission from zarboz to use this kernel, but having problems with WiFi. Tried with sun_dream sense 5. Tried wiping cache and factory reset still same problem going to try on stock. Well tried on medusa Rom same problem. Must be in kernel. Any help would be appreciated and welcomed.
https://www.dropbox.com/s/rzsbypd1ft758ir/Myst_4.2.zip?dl=0
Sent from my HTC first using XDA Free mobile app
The more info we can gather the easier it will be to find a fix for this. So if someone can test this out and give us some feedback, thank you very much .
Is there any other kernel for this phone that has WiFi working? Maybe I could try to get the WiFi piece from the good one and put it into this one.
The medusa and sense 5 would I just replace all WiFi references.
Sent from my HTC first using XDA Free mobile app
blafree64 said:
The medusa and sense 5 would I just replace all WiFi references.
Sent from my HTC first using XDA Free mobile app
Click to expand...
Click to collapse
after flashing this kernel, could you do this for me:
1. Flash UKM http://forum.xda-developers.com/android/software/zip-synapse-script-universal-kernel-t2736986
2. Install "synapse" (its an app), reboot
3. Go into synapse, you should now be able to configure the kernel (if you still cant, refer to the link above).
4. Post screenshots of EVERYTHING
5. Upload your build.prop (/system/)
i wish i had a first i could go through the file system myself.
Edit:
Hopefully stock android filesystems stay the same from version to version. im on 5.0 at the moment on my nexus but try some of these things too:
1: delete this folder /data/misc/wifi/ And /data/misc/dhcp and system/etc/wifi reboot. (try deleting 1, then reboot, then if it doesnt work, delete the first 2 folders, reboot, if that doesnt work, delete all 3. try different combos).
(and/or)
2: force stop Bluetooth Share (i think you can go to apps>all> and find it there. reboot
3: drain the battery to 0. like make sure the thing is DEAD and wont boot even into recovery. let it sit for some time. plug in your charger and turn it on at the same time.
here is some additional info. if you want to try this. go right a head!
jpsflores said:
Hello all!
I registered here so that i could share a possible solution to the stuck wifi problem. On my nexus the BT was also stuck most of the time.
Been having the problem for about two weeks and was about to do a clean install and, if the problem persisted, call Google support. Thing is, I had the feelling it was software related and that the hardware was ok.
I´m not sure if BT, Wifi and NFC use the same hardware but the fact was that wifi worked for a few days, BT for a few more and NFC was always functional.
I did some extensive research thru the web and it seemed that this problem was not nexus unique and seemed to be related with wpa_supplicant.conf or wpa_supplicant in the bin file.
On this page, mind you the text is pretty old and not entirely android related:
http:_//_blog.linuxconsulting.ro_/2010/04/porting-wifi-drivers-to-android._html (I can't post links yet so just copy past and remove spacing)
I found this little snippet that caught my attention:
Seems that you can add ap_scan=1 to your wpa_supplicant.conf depending on the drivers you have.
After some more research on the subject of ap_scan i found that:
It seems that addind ap_scan=1 imposes that wpa_supplicant.conf handles the scanning and AP selection. IF there's something wrong with the driver, and not with wpa_supplicant as i originaly thought, this could bypass the problem.
So I added ap_scan=1 just before the device identification lines in wpa_supplicant.conf, reeboted, and now the wifi and bluetooth toggle normaly. I've tried ap_scan=0 (the driver handles the scanning) and the problem returns, so ap_scan=1 does allow you to toggle the wifi and BT on.
I can't yet verify that the phone actually connects to a wireless network and has the same stability and range as before as I'm at work and there's no wireless here.
Therefore I ask for your help to verify this "fix" and thoughts on this.
Sorry if the post is a mess. Both english and programming aren´t my native languages...
My device is a Nexus 5 with stock 4.4.4 KitKat and root.
Greets.
---------- Post added at 10:29 AM ---------- Previous post was at 09:46 AM ----------
So, quick update:
Managed to find an wireless network around and connected to it. Some time later, no sure how much, the phone rebooted.
Some time after that the wifi and Bt were stuck again. Accessed wpa_supplicant.conf and deleted the new wireless network information. Rebooted and all was functional again.
Seems the fix is incomplete as any rewrite of the wpa_supplicant.conf reinduces the initial problematic behaviour...
____________________ Extra Update_______________________
Ok, so it seems that the wpa_supplicant.conf is suposed to have ap_scan=1 by default.
After boot and when I connect to a wifi network my file resets and shows without ap_scan=1 and instead of:
ctrl_interface=wlan0
its
ctrl_interface=data/misc/wifi/sockets
Wifi with a conf. like this never works. If I manualy "correct" the file and reboot, the wifi toogles on, but after a wifi connect gets busted up again.
by now I've done:
- copy wpa_supplicant (the bin file) from a stock 4.4.4
- Check file permissions for all wpa_supplicant files
- dirty flash the stock build (it's my original build so less harm done i guess)
- 2 Clean installs
- 6 factory resets
And the problem persists.
I've called google support and they are sending a new phone as we speak. Now I'm not sure if it's a software or hardware problem (maybe a combination of the two?) but I figured it would be better to reroll a device instead of trying to fix this one as this problem is cleary out of my league.
Thank you all!
Click to expand...
Click to collapse
Cannot download synapse playstore is incompatible ugh..
Sent from my HTC first using XDA Free mobile app
This is my kernel that I'm running right now that I maded awhile back is the info right?
Sent from my HTC first using XDA Free mobile app
blafree64 said:
This is my kernel that I'm running right now that I maded awhile back is the info right?
Sent from my HTC first using XDA Free mobile app
Click to expand...
Click to collapse
Yeah all end correct. Try the steps I posted to fixing Wi-Fi hopefully it will work
BTW. Are you running android 4.4? I thought HTC first is only 4.1
I built this kernel awhile back use GCC 4.6 so is it 4.4 cause all works on this kernel
Sent from my HTC first using XDA Free mobile app
blafree64 said:
I built this kernel awhile back use GCC 4.6 so is it 4.4 cause all works on this kernel
Sent from my HTC first using XDA Free mobile app
Click to expand...
Click to collapse
Is everything working?
All things work but I think its a typo because its api level 16 I don't no how to read kernel info like which toolchain is for what android version.
Sent from my HTC first using XDA Free mobile app
blafree64 said:
All things work but I think its a typo because its api level 16 I don't no how to read kernel info like which toolchain is for what android version.
Sent from my HTC first using XDA Free mobile app
Click to expand...
Click to collapse
Alright.
If you need any more help let me know
I'll do my best