Related
I can say that my Diamond jailbreak the PS3 at first boot "everytime".
I use HERMES V4 and OPEN MANAGER 2.1
The solution that I found is simple (with XDAndroid 2.2 RC 2.1 + System RC 2.2).
The first time:
-check to have replace zImage
-check to have put modules-2.6.27.46-01162-g741ab49-dirty.tar.gz in the directory of xdandroid (delete the old modules)
-put psfreedom.ko in the root of memory
-download payload from attachment
-put payload_hermesV4.bin in the root of memory
-overclock the phone (in startup.txt add inside "set cmdline": acpuclock.oc_freq_khz=680000) or download my STARTUP.TXT from attachment (only DIAM100)
-edit "froyo.user.conf" in the conf directory and replace the section "# custom shell commands, these commands run last" with this:
# custom shell commands, these commands run last
custom_shells{
rm -f /sdcard/fsck*.rec
echo ""
echo ""
echo "*************************************"
echo "*************************************"
echo "******D i s c o n n e c t ****** U S B ******"
echo "*************************************"
echo "*************************************"
echo ""
echo ""
sleep 3
insmod /sdcard/psfreedom.ko
sleep 2
echo "**********************************"
echo "**********************************"
echo "********P a y l o a d ****************"
echo "**********************************"
echo "**********************************"
cat /sdcard/payload_hermesV4.bin > /proc/psfreedom/payload
}
or download my conf file from attachment and put the file in the conf directory (only DIAM100)
-launch haret with USB connected to PC
-disconnect cable when the message "Disconnect USB from PC" is display
-put the phone to airplane mode
-install Advanced Task Killer Free (ATK)
-launch ATK
-change setting and set security to LOW (kill more application)
-kill all application (after I have 50Mb free)
-connect to PS3
jailbreak in normal way
The next time you just:
-launch haret with USB connected to PC
-disconnect cable when the message "Disconnect USB from PC" is display
-launch ATK and kill all application
-connect PS3
jailbreak in normal way
I hope this can help everyone who jailbreak with Diamond
UPDATE(only for DIAM100):
The STARTUP.TXT attached contains my path.
Change the name of the directory: "rel_path=your directory"
EXAMPLE: "rel_path=andboot"
HELP1:
If you don't have 50 Mb of free memory from ATK try:
-remove all widget from all the android desktop
-set as background of the desktop a simple color (not an image)
-disable the animation of the video (in the configuration of android you can find video option)
-etc... (all other simple procedure to free more memory)
HELP2:
If you don't find where to set security level LOW:
-open ATK
-press HOME button
-press Setting
-press Security Level
-select Low
-press BACK button (turn back)
-press BACK button (turn back)
-KILL selected apps
I have more than 50Mb free after this operation.
ALL-IN ONE solution: (thanks to Gonsi)
HTC_Diamond_PSFreedom_Hermes_V4b.rar
All-In-One Solution: PSFreedom 3.41 v1.3.1 PL3 Hermes v4b with PSN Patch
HTC_Diamond_PSFreedom_3.41_v1.3.1_Hermes_V4b_PSN_Patch.rar
Download this file and decompress it on your root.This file contains already ALL that you need.(include HermesV4)
It is ready for Diam100.
Change the startup.txt file if you have other phone.
NB: If you change the startup.txt file remember to edit it to set rel_path=xdandroid
Last payload:
For the last payload visit the HTC HERO psfreedom wiki page
Download the payload that you want and then change the conf file to load it (replace payload_hermesV4.bin with the name of the new payload)
Good day.
Works great!
Great solution, i tried a similar procedure (by me) but yours is great!
Now I've only the same problem as described in other post.
When i try to load backup of my game (original) from an external disk (2,5"), it returns always on xmb and not load nothing.
Any idea?
worked first time for me too, i've got psfreedom auto loading in the init file, so all you have todo is kill apps and jail break.
[one thing left to try is set ATK to autoload and set it to aggressive autokill and hopefully all you'll need todo is boot into andriod and jailbreak.] - scratch this bit as auto kill smallest interval is 30 mins
edit: tried a second time and the jailbreak didn't work first time... actually tried several times and then eventually rebooted phone and tried again, worked on second attempt (got unknown usb device on first try)
Ok, now works perfect.
It was an hard disk problem (external 2.5" samsung model 0804h hd 80gb), it is not fully supported.
Now i use another hard disk and it works
zulm said:
worked first time for me too, i've got psfreedom auto loading in the init file, so all you have todo is kill apps and jail break.
[one thing left to try is set ATK to autoload and set it to aggressive autokill and hopefully all you'll need todo is boot into andriod and jailbreak.] - scratch this bit as auto kill smallest interval is 30 mins
edit: tried a second time and the jailbreak didn't work first time... actually tried several times and then eventually rebooted phone and tried again, worked on second attempt (got unknown usb device on first try)
Click to expand...
Click to collapse
control the memory free (on ATK)
I have 50Mb and I jailbreak everytime at first boot
I did also:
-in settings/display disable all effect
-in desktop load like background a single color (and not a picture)
-remove ALL the gadget from all the desktop
...
it works great
ATTENTION: Autoload psfreedom.ko
I think that initrd.gz is not the right place where insert the insmod command.
Try to edit "froyo.user.conf" in the conf directory and insert in the section # custom shell commands, these commands run last
insmod /sdcard/psfreedom.ko
obviously before the } that end the list of commands...
You must have something like
# custom shell commands, these commands run last
custom_shells{
rm -f /sdcard/fsck*.rec
insmod /sdcard/psfreedom.ko
}
This for two reasons:
1.is more simple to modify (is a plain text file in XDAndroid directories, so you don't need Linux)
2.you load the module "after" the other modules that psfreedom.ko need
Now I am at work, I will try this solution this afternoon... but if someone can test... is simple to modify the conf file.
EDIT:
Ok, it works
You can edit the conf file and then when xdandroid boot you have only to launch ATK and kill all application
@bastard: You're spreading FUD. PSF module does not depend on any module which is loaded in conjunction with XDandroid. Why are you claiming this?
And you consider booting a full blown OS (which IS Linux by the way), installing apps and configuring a lot of other stuff more simple than booting another Linux (or just using your main OS if it's Linux compatible) and modify initrd once?
Anyway, have a good day!
Chatty said:
@bastard: You're spreading FUD. PSF module does not depend on any module which is loaded in conjunction with XDandroid. Why are you claiming this?
Click to expand...
Click to collapse
PSfreedom depend on the modules that you load on boot.
In particolary g_android.ko that enable debugging via USB
This is why on the psfreedom procedure you find to "copy" the modules in xdandroid directory
Now, i don't know if you have to load before or after...
But the psfreedom procedure say to load psfreedom.ko in terminal so I think this is the right order:
1.modules
2.psfreedom.ko
in this way it work... in the other... i don't know
Chatty said:
And you consider booting a full blown OS (which IS Linux by the way), installing apps and configuring a lot of other stuff more simple than booting another Linux (or just using your main OS if it's Linux compatible) and modify initrd once?
Anyway, have a good day!
Click to expand...
Click to collapse
I didn't say this...
I think (and wrote) that is "more simple" to modify a text file (the conf file) directly on phone rather than copy initrd.gz, boot to Linux, expand initrd.gz, edit init file, recompile to initrd.gz and then put it again on phone ONLY to autoload psfreedom on startup... (and allways do the rest of stuff)
Then I think (and wrote) that to have the order 1.modules 2.psfreedom.ko
modify the conf is better than modify initrd.gz
I don't understand why you have to enter into a debate...
if you don't like my procedure... use another.
Anyway, have a good day!
2 issues.
-overclock the phone (in startup.txt put the line acpuclock.oc_freq_khz=700000)
I can't put 700000, the phone crash when I start Android, I can put 680000, but no more.
-change setting and set security to LOW (kill more application)
I don't understand this, how can I change this setting?
I've tried the trick and it works like before for me, not better...
sexto said:
2 issues.
-overclock the phone (in startup.txt put the line acpuclock.oc_freq_khz=700000)
I can't put 700000, the phone crash when I start Android, I can put 680000, but no more.
Click to expand...
Click to collapse
I use 700000 and works fine for me, but I think it's normal... on the xdandroid you can find:
Overclocking
acpuclock.oc_freq_khz=XXXXXX ( i personally use 600000-640000 )
but it very unstable if you try to get higher than 650000-700000
Use the value that works for you.
sexto said:
2 issues.
-change setting and set security to LOW (kill more application)
I don't understand this, how can I change this setting?
I've tried the trick and it works like before for me, not better...
Click to expand...
Click to collapse
-open ATK
-press HOME button
-press Setting
-press Security Level
-select Low
-press BACK button (turn back)
-press BACK button (turn back)
-KILL selected apps
I have more than 50Mb free
With this I jailbreak every time at first time.
Have you change the phone to airplane mode? It use less cpu...
Yeah.
I have done the security think and now yes, it always works, at the moment, I've tried twice, but works both.
Thanks for the trick, you are my hero!!
By the way, I am spanish, it's possible that I wrote some word or sentence incorrectly, but I try do it well ^^
could someone upload these modified files? i can't find in my phone,thanks
I did everything you said but still it doesnt run every time on first boot it takes like 5 to 10 times to boot
any new version psfreedom for openmanager v1.13？
That would be awesome
agreed, I really want no bluray disc needed.
Also with the hermes payload, they will eventually create some custom firmware, no more psfreedom!
Thank you for opening this thread! But...
I did everything u recommended but still receiving the "unknown USB device connected". So, the same problem persists: It only works after the first boot!
Any other suggestions so we can solve the diamond problem once for all?
PS: PS3 jailbreak USBs are not available in my country so i have to count on the diamond jailbreak
UPDATE 1: After switching to Windows mobile--->Reconnect to PC in active sync mode--->Disconnect when the message appears--->Connect to PS3 and apply Jailbreak! It REALLY WORKS!
Do Note that using HTC Diamond is tricky when it comes to Jailbreaking the PS3 since it's not 100% compatible So take real care of the time between the power and eject buttons: YOU SHOULD WAIT LIKE 1/2 A SECOND TO PRESS THE EJECT AFTER THE POWER & IT WILL WORK WITH A RATE OF 1 OVER 2
UPDATE 2 : After Rebooting the phone from Win Mobile to Android (While connected to PC) if the JB doesn't work with the error "Unknown USB device connected", Just shut down the phone, reboot in win mobile reconnect to PC and boot back to Android then try again it should work!
Hope this helps!
Recheck procedure
codvisp said:
I did everything u recommended but still receiving the "unknown USB device connected". So, the same problem persists: It only works after the first boot!
Any other suggestions so we can solve the diamond problem once for all?
PS: PS3 jailbreak USBs are not available in my country so i have to count on the diamond jailbreak
UPDATE 1: After switching to Windows mobile--->Reconnect to PC in active sync mode--->Disconnect when the message appears--->Connect to PS3 and apply Jailbreak! It REALLY WORKS!
Do Note that using HTC Diamond is tricky when it comes to Jailbreaking the PS3 since it's not 100% compatible So take real care of the time between the power and eject buttons: YOU SHOULD WAIT LIKE 1/2 A SECOND TO PRESS THE EJECT AFTER THE POWER & IT WILL WORK WITH A RATE OF 1 OVER 2
UPDATE 2 : After Rebooting the phone from Win Mobile to Android (While connected to PC) if the JB doesn't work with the error "Unknown USB device connected", Just shut down the phone, reboot in win mobile reconnect to PC and boot back to Android then try again it should work!
Hope this helps!
Click to expand...
Click to collapse
I reply to you, but it's ok for everyone who have some troubles:
-you don't need to reboot to windows mobile
-you don't need to reboot the phone
If you have "unknown USB device connected" simply retry the jailbreak (leave the phone connect to PS3).
NOW
For my procedure...
It works ALLWAYS at first boot (not AFTER first boot)
If you have some problem check all the step, particolary:
-overclock (700000 or 680000 works fine, try which one works for you)
-phone in airplane mode
-security level LOW in ATK
-memory after kill all the application MUST be more than 50Mb
If you don't have this value of free memory try:
-remove all widget from all the android desktop
-set as background of the desktop a simple color (not an image)
-disable the animation of the video (in the configuration of android you can find video option)
-etc... (all other simple procedure to free more memory)
I wrote this guide becouse I NEVER try two time to jailbreak my PS3 after this trick... NEVER
So, eventually you can try different timing from press Power button and Eject button, but the REAL problem is the free memory and the speed of Diamond.
So I suggest:
- re-check the speed of overclock (try 680000 maybe is more stable)
- re-check alll the step of my guide
- re-check this list of trick to free more memory
I hope to help everyone with DIAMOND (DIAM100)
bastardociccio said:
I reply to you, but it's ok for everyone who have some troubles:
-you don't need to reboot to windows mobile
-you don't need to reboot the phone
If you have "unknown USB device connected" simply retry the jailbreak (leave the phone connect to PS3).
NOW
For my procedure...
It works ALLWAYS at first boot (not AFTER first boot)
If you have some problem check all the step, particolary:
-overclock (700000 or 680000 works fine, try which one works for you)
-phone in airplane mode
-security level LOW in ATK
-memory after kill all the application MUST be more than 50Mb
If you don't have this value of free memory try:
-remove all widget from all the android desktop
-set as background of the desktop a simple color (not an image)
-disable the animation of the video (in the configuration of android you can find video option)
-etc... (all other simple procedure to free more memory)
I wrote this guide becouse I NEVER try two time to jailbreak my PS3 after this trick... NEVER
So, eventually you can try different timing from press Power button and Eject button, but the REAL problem is the free memory and the speed of Diamond.
So I suggest:
- re-check the speed of overclock (try 680000 maybe is more stable)
- re-check alll the step of my guide
- re-check this list of trick to free more memory
I hope to help everyone with DIAMOND (DIAM100)
Click to expand...
Click to collapse
It is WORKING with a 99% rate!
1. The Overclocking to 7,000 is working at its best.
2. I am not using ATK.
3. Phone in airplane mode is a must, i agree.
4. Disabling the animation is a must also.
5. I need to boot in WinMobile so i can use my phone normally...
6. I really noticed that one of the most important points is: the lapse of time between the Power & Eject buttons. It has to be larger than other devices at 1/2 sec. aprox. (as compared to HTC HD2 or others...)
Regards
codvisp said:
It is WORKING with a 99% rate!
1. The Overclocking to 7,000 is working at its best.
2. I am not using ATK.
3. Phone in airplane mode is a must, i agree.
4. Disabling the animation is a must also.
5. I need to boot in WinMobile so i can use my phone normally...
6. I really noticed that one of the most important points is: the lapse of time between the Power & Eject buttons. It has to be larger than other devices at 1/2 sec. aprox. (as compared to HTC HD2 or others...)
Regards
Click to expand...
Click to collapse
if you don't use ATK, you don't use my procedure!
Try to use ATK and it will work with 100% rate!
I repeat that timing between power and eject is less important...
Try ATK and then you never try two time!!!
(ATK free that you can download free on the internet. You can put the apk directly on xdandroid directory and it autoinstall )
htcinho said:
Works great!
Great solution, i tried a similar procedure (by me) but yours is great!
Now I've only the same problem as described in other post.
When i try to load backup of my game (original) from an external disk (2,5"), it returns always on xmb and not load nothing.
Any idea?
Click to expand...
Click to collapse
Try deleting Backup Manager and reinstalling. I had the same problem and that worked for me. Good luck.
FRX07.1 is here!!
This is a maintenance release - basically taking the newest components to make a completely up-to-date (as of Sept. 1).
Quite a lot has changed since FRX06 - the install process hasn't really, but be sure to read the changelog in the next post and the caveats in post #3!
<<<This is a link to the... FAQ Click it!!>>>
I have created a complete bundle of FroYo with a stable kernel from GIT (August 19 / 1348), and rootfs from GIT (Sept. 2).
Please, feel free to DONATE to the XDAndroid project!
Every little bit helps!
Directions:
1. Download the full bundle (zip). (Updated September 1 2011)
If instead you just want the system.ext2 (zip) (Updated July 15 2011) file by itself... Don't download this if you're not sure! Grab the full bundle!
2. Extract it. You’ll see a folder, FRX07.1, copy its contents to the root of your SD card. If you want to run Android from a folder instead of all the files on the root of the card, follow the steps below.
3. Go into the STARTUPS folder. Grab the appropriate startup.txt for your device (if you don't know what device you have, you should read the FAQ), and move it to the root of the card (or where you run haret.exe from. If you want to change the location of the build, put a rel_path= statement in the cmdline section of the startup.txt. Mine is located two folders deep on the SD, so my rel_path=Androids/TP2Ref)
4. Screen calibration - you have three choices:
Re-use an old ts-calibration file if you have it and you know it's good.
Download the ts-calibration.zip file and extract it to where you put the rest of the files (root of SD or in a folder - make sure it all stays together!)
Manually calibrate - boot with no ts-calibration file and watch the boot process - you'll be asked to hit 5 points to calibrate the screen. If you have issues calibrating, try an older kernel (1225 works well) Once you have the calibration file hold on to it (make 15 copies if it's a good one ), reboot & go back to the newest kernel!
6. Run haret.exe.. Profit!
Let it settle out on the first boot. Many have reported they had to reboot basically because it was so slow - if you let it sit for about 10 mins so the media scanner can go thru everything, etc. it will be much more pleasurable experience. If you want adb in and watch the processes via top, you'll see why the phone seems so slow - there's lots of background processes cranking because this is the first boot .
Troubleshooting:
Please read the... FAQ
If you have any issues with the kernel, feel free to change it:
There are some devices that are having issues with the newest kernels. Please see the kernel autobuild service to get archived kernels. Once you download a replacement kernel, go to where you run haret.exe from - remove your old zImage/modules-xxxxx.tar.gz. Take the new zImage/modules-xxxxx.tar.gz and replace the old ones, same folder - where you run haret.exe from. Make sure the ‘zImage’ is named just that. Do not rename the modules file, do not extract it - should be in .tar.gz format.
See Incremental Updates for more information on updating the kernel and other components.
Random issues can often be solved by forcing the system to create a new data.img. If you're worried about losing data (all user data is stored in the data.img!!), Titanium Backup works quite well. If you wish, you can rename the data.img to something else, and let the system create a new one - just to see if it resolves your problem.
Similarly, if you wish try formatting your SD card - I prefer to use the HP Tool - do a full format, FAT32.
Even though this build is considered fairly stable, you are more than likely going to run into issues. The next post will address issues particular to this build - PLEASE READ THESE before asking questions! Feel free to post questions in this thread, I will do my best to address them. Big thanks to stinebd for releasing the system image, and of course the other developers for their hard work on making these kernels available.
Caveats:
BT - works! But audio doesn't route. See this thread if you're feeling adventurous and want to play with/don't mind using some unstable/incomplete code...
Audio stutters every 10sec. The only fix I've heard is using a kernel from G3rmo (unfortunately it is old), or
Code:
su
kill -9 28
Which kills the [battery] process. I'm sure this will have negative effects on the battery meter/battery life...
SD Card not working...? "Waiting for SD Card" appearing on boot...? Try putting this command in your startup.txt
Code:
msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave
See gummbah30's post reminding us of these commands.
SD Card has partitions? (If you used a non-XDAndroid build the answer is YES) Then you need to add "no_partitions" to your startup.txt. Between the quotes on the set cmdline line. Do not put it on its own line, it goes in between the quotes! Make sure there is one space between each item.
Front buttons messed up/wrong? You can use my rootfs which incorporates g3rm0's layout. This custom rootfs is no longer necessary, I have committed the changes so you can use the autobuild rootfs (in conjunction with physkeyboard=blac in your startup.txt)!
Keyboard tiny/unusable? Either change the IME (long press on the input box) Get rid of it! I've heard "Hackers Keyboard" is a good alternative - many options. There's also "Better Keyboard", Swype, etc... Side load the APK using AndroidApps, adb install, etc.
stinebd's Changelog:
stinebd said:
Here’s a new release for you, folks. This is a major release with a ton of changes, new features, and fixes. Our friend hyc/highlandsun did most of the heavy lifting for this release. Highlights include a rewritten RIL with support for world phones and greatly improved CDMA support; fixes for the media codecs; fixes for MMS on Sprint; increased security with the Superuser app.
A list of changes is included below. The FRX07 system image is available for download now, and will require the use of a new rootfs image, also available now. Additionally, we have a new bundle containing everything needed to enjoy a full FRX07 system.
Note: Due to the incredibly long list of changes, this is a somewhat condensed, terse changelog describing only the overall scope of the changes.
FRX07:
frameworks/base:
Major frameworks changes for CDMA/GSM dual-mode worldphone support. (hyc)
Fixes for data connection handling to improve startup time. (hyc)
Fixes for wifi handling to avoid issues on hanged drivers. (hyc)
Stagefreight (media codecs) fixes. (hyc/viruscrazy)
Fixes for Sprint’s wonky MMS markup structure. (hyc)
Fix MediaScanner not finding audio files (including ringtones) in system.ext2
hardware/libhardware_legacy:
Minor GPS driver fixes. (Alex[sp3dev])
Rename wifi interfaces to wlan0 on all devices (hyc)
hardware/xdandroid-ril: Major RIL refactoring for improved performance on all devices, and added CDMA/GSM dual-mode worldphone support. (hyc)
packages/apps/Gallery3D: Switched back to Gallery3D as the gallery app (closes bug #111)
packages/apps/Mms: Fixes for Sprint’s wonky MMS markup structure. (hyc)
packages/apps/Phone: Fixes for CDMA/GSM dual-mode worldphone support. (hyc)
packages/apps/Superuser: Added the Superuser package for authorizing su privileges. This, along with our signed builds, provides greatly increased security for the end user (mostly against malicious apps from the Market).
system/extras/su: Added as a dependency for the Superuser package
vendor/qcom/android-open: Include missing stagefright codec symbols. (hyc/viruscrazy)
To coincide with the FRX07 system image, the following rootfs changes have been made:
init.froyo.rc modifications...
Adjust wpa_supplicant service for the new abstraction provided by libhardware_legacy, as well as interface rename
Abstract the hciattach service to provide bluetooth support on both chipsets
Rename wifi interface to wlan0 on all devices
apns-conf.xml updated
keymaps completely reorganized, and RHOD end-call keya has been remapped to be the Home key in Android.
default.prop: set ro.secure=1 to lock down the adb shell - su can be used with the Superuser app to authorize root access in adb if needed.
Click to expand...
Click to collapse
Layman's Changelog
(As in, the changelog I wrote )
FRX07.1 Changelog:
RHOD - all buttons on the front no longer wake the device. Only the power button wakes the device now.
Updated to the newest RIL
hyc's modified libs for video now baked in - *most* HQ YouTube videos (and other HQ videos) should finally work!
RHOD & TOPA - Userland (Android) now controls the LED by default now. If you need to debug sleep, you will have to change the behavior manually.
Facebook sync should now work, out-of-box.
FRX07 Changelog:
Updated RIL (thanks hyc!) - this covers many different bugs that were in the old RIL - I'm only going to cover the major ones...
CDMA now works correctly (for the most part). force_cdma (and north_am_dialing) is now deprecated (not needed/ignored!)
You can boot with a SIM in on a CDMA device and choose your GSM or CDMA on the fly under Settings.
Location based on towers now works on CDMA.
1xRTT now displays correctly, but I never seem to get EVDO Rev.a... I always get 0. This is represented by a 3g icon, as this is what the Android framework provides.
Full MMS support! Please see this page for configuration instructions. Will need help fleshing out the list of carriers folks!
Spotty service, switching towers, etc should no longer cause the dreaded SoD (Sleep of Death) condition!
(Basic audio) 3.5mm support for RHOD400/500
Droidwall works out of the box now
Keyboard backlight now fades in/out
Gallery3D back in! Picasa Web Sync comes with it
A couple new apps added to AndroidApps folder:
rpierce99's app GetLogs
Titanium Backup
Cool man! Thanks for your work.
Thanks!
Well, in fact WEP works perfectly for me. The only thing that wifi fails is at turning it on after turning it off 2 times...
Also, with latest updates I can pair BT, haven't tried to transfer anything.
Eodun said:
Thanks!
Well, in fact WEP works perfectly for me. The only thing that wifi fails is at turning it on after turning it off 2 times...
Also, with latest updates I can pair BT, haven't tried to transfer anything.
Click to expand...
Click to collapse
Ah, I forget how different the bugs are for the TI chipsets. I'll change it, thanks!
Updated to FRX07! Enjoy!
woo FRX07 - I should really update my blackstone as its running 05 still
It seems that the 20110716 Kernel is giving problem to the Blackstone/Topaz.
you may use the previous kernel, or wait until is fixed.
Brgds
mass storage not connecting......anyone else facing this problem?
welard said:
mass storage not connecting......anyone else facing this problem?
Click to expand...
Click to collapse
USB mass storage has never worked (on looped mounts).
You can kinda fake it with Droid Explorer, it uses ADB to 'fake' USB mass storage.
arrrghhh said:
USB mass storage has never worked (on looped mounts).
You can kinda fake it with Droid Explorer, it uses ADB to 'fake' USB mass storage.
Click to expand...
Click to collapse
ok thanks alot....
Had to use a different kernel as yours wouldnt let it boot up
Working:
installing apps, no fc, its connecting to wifi nicely, only dropped once so far, connected to google account fine, coping nicely with downloading and installing multiple apps!!! i like that the others i have tried freeze up
Defect list:
Power control wigit loads frame but not icons on first load
froze when opening camera the second time had to battery pull! on first load
On restart attempt seemed to load haret ok, boot speed and time impoved compaired to first load, still lightly juddering boot animation
On second boot reloaded power control wigit, now displays correctly
Downloading and installing two apps at once navigating home screens caused 20second freeze up.
As someone said the motions but not the workings for usb connection, i cant get droid explorer to see my device so :-(
BT is reallly messed up using app "bluetooth file transfer", just loops itself to death, killings wi-fi as well, not kwl
Using phones bluetooth in settings, my computer says unable to send blah blah then when i turn off bluetooth the wifi is dropped might be connected
Can i overclock stably with this mod?
How do i get the front facing camera working?
FRX07 with CWM
I just succeeded in starting FRX07 as a CWM build.
But the startup wizard seems to be a little bit crazy. It's my first try to make a CWM build, so no wonder there are problems.
If I really can make a stable build I will post the results here.
alphecca911 said:
Can i overclock stabley with this mod?
How do i get the front facing camera working?
Click to expand...
Click to collapse
I couldn't really follow you post, these were the only questions I could find..
You can overclock - stably, dunno. I don't, so you tell me if you can OC.
Front-facing cam doesn't work, kernel issue not build.
ThaiDai said:
I just succeeded in starting FRX07 as a CWM build.
But the startup wizard seems to be a little bit crazy. It's my first try to make a CWM build, so no wonder there are problems.
If I really can make a stable build I will post the results here.
Click to expand...
Click to collapse
Startup wizard...? There isn't a startup wizard on XDAndroid builds...
yes i am sorry for that, i have just been note taking as i have been instaling and testing in the event that someone came, they could assist. I have it up and running now but it didnt work using ur kernel. (wouldnt boot) i have listed defects so far.
Thankyou for your answers to my questions.
Great rom, best i have tried
alphecca911 said:
yes i am sorry for that, i have just been note taking as i have been instaling and testing in the event that someone came, they could assist. I have it up and running now but it didnt work using ur kernel. (wouldnt boot) i have listed defects so far.
Thankyou for your answers to my questions.
Great rom, best i have tried
Click to expand...
Click to collapse
Hrm. I've heard BLAC doesn't work on the newest kernel... I'll have to ask emwe, he had a list of changes for FRX07 release, but I assumed they were RHOD-only... Perhaps something is effecting BLAC that isn't supposed to be .
I don't have a BLAC, so you'll have to help me - what is the newest kernel that does work? 20110711_082424? Also, how far does it get in the process? If adb is up, logs would be appreciated. Thanks.
Allright I'm running into problems! Haret starts and I get as far as the linux boot animation, but then the phone crashes and reboots... anyone else experiencing this?
bdacier said:
Allright I'm running into problems! Haret starts and I get as far as the linux boot animation, but then the phone crashes and reboots... anyone else experiencing this?
Click to expand...
Click to collapse
Sorry mate, seems the newest kernel isn't BLAC friendly! Please tell me which kernel does work... Use the autobuild service and try older kernels. First post has details on how to change your kernel, plus links to autobuild service...
To alphecca911 - most of your issues seem to be first boot related. Remember, you should let it sit on first boot so all the processes that run on first boot have plenty of time to work! I usually let it sit until it sleeps. I've had a lot of weird issues trying to do too many things on first boot on the device... I am impatient just like you probably . Just fight it .
Startup wizard...? There isn't a startup wizard on XDAndroid builds...
Click to expand...
Click to collapse
That might explain a lot
I just checked the system/app folder in the frx07 package. Of course you're right. I copied apps into this without looking. And there was an old SetupWizard.apk.
But just in the moment I started frx07 without any error.
Now I can start to make a real nice package for CWM. And "most" important: try a different boot animation.
I have to thank all XDAndroid developers for this and arrrghhh here for pointing me to it with his posts.
Really great job you are doing here at XDA developers
Thanks
Wow, this is a weird one.
I've been having real trouble debugging a native app on my current stock, rooted Android 4.2.2 on the Galaxy Nexus.
I think I've traced the problem to the fact that /data/system/packages.list is not updating correctly, and according to the timestamp, it stopped doing so the day I installed Android 4.2.
In order to debug without root, you need to use the run-as command. That command requires the correct entry in packages.list. If it's not there, it fails the security check and refuses to run gdbserver.
Wading through the AOSP code led me to com.android.server.pm.Settings.writeLPr() that is supposed to create this file. That function is only referenced by com.android.server.pm.PackageManagerService.
So, a two-part question. Would anyone mind checking to see if their /data/system/packages.list has updated (Only stock, rooted 4.2.x people, please!) after the 4.2 update.
My packages.xml seems to be fine (but obviously run-as doesn't use that).
Secondly, does anyone know how to trigger a manual rebuild?
Thanks in advance!
Update (The very next day!)
Would you believe I found the problem using a tmp-file race?!?
Some package seems to have been badly installed. The packagemanager started writing the .tmp file and threw an exception when it came to that entry, silently rolling back, therefore never updating packages.list.
I saw something like this in the log:
I/PackageManager( 391): Failed to install pkg from /mnt/asec/com.yoyogames.droidtntbf-2/pkg.apk from sdcard
Which was the entry in packages.xml just after the entries stopped in packages.list.tmp!
Deleting the package and re-adding it, made the exception go away, and packages.list gets recreated every time the package db changes!
Whoohoo!
Jan Gutter
This is a development thread at the moment. I'm going to start working on porting the kexec-hardboot patches to the N900T (actually CyanogenMod hlte) kernel. With the kexec-hardboot patch applied, the kernel will be able to act as a second stage bootloader and boot other kernels. Combined with the kexecboot program, it can act as a second stage bootloader, allowing you to boot kernels from any storage device without flashing them. Ultimately the goal here is to dual-boot Android and non-Android Linux without having to re-flash kernels constantly. Like with my Note i717 port I will be focusing on kexec first, then getting Debian to boot on the device with the Freedreno graphics driver. The Note 3 is a very powerful ARM device and with Freedreno working it could play many of the 3D FOSS games.
Here is my modified kexecboot that I will be using:
https://github.com/CalcProgrammer1/kexecboot
Here is a video showing how it works on the Note i717 (it will work the same way on the Note 3):
https://www.youtube.com/watch?v=qtb-TSGumNo
My Note i717 thread:
http://forum.xda-developers.com/showthread.php?t=1787856
Here is the kexec-hardboot porting guide I will be using:
https://github.com/Tasssadar/multirom/wiki/Porting-kexec-hardboot
For anyone inclined you could also get MultiROM working with this. I am not familiar with that framework but have used kexecboot many times on many devices in the past, so I am going with that.
EDIT 1: I've got the main patch applied and I've found some numbers for the addresses that I think might work. Everything compiles and I'm able to build a boot.img and flashable zip, but I'm sure it won't work in its current state. The Note 3 uses a DSI command-mode panel which is different than the Note 1's video-mode panel in that it doesn't continuously refresh (i.e. at 60Hz). Instead, screen updates must be forced manually by using an ioctl for the framebuffer device. There are several ways to handle this - I could add this ioctl into kexecboot any time it draws to the screen but this would only work for kexecboot. Alternatively I could write a background program that sits in a 60Hz waiting loop and calls the ioctl repeatedly, simulating a video-mode panel. I've talked to some other people on the #freedreno Freenode IRC channel and the refreshing background program has been done with some success on other devices (2013 Nexus 7) so I think I'll take this route first as it will hopefully let me get a framebuffer console up for debugging with.
EDIT 2: I found a way to make kexecboot refresh the screen. I call the FBIOPAN_DISPLAY ioctl in kexecboot's framebuffer refresh function and that makes the kexecboot GUI appear on screen. Now to figure out how to build a kernel and pack a boot.img.
EDIT 3: I figured out how to make boot images, it requires a device-tree supporting mkimage tool such as this: https://bitbucket.org/itsmikeramsay/mkbootimg/src I was able to build a boot.img with a precompiled kernel and my new ramdisk with kexecboot, it worked enough to show the kexecboot GUI. Now to build my modified kernel into the mix and create a kexec-bootable kernel for CM11.
EDIT 4: I might put the Note 3 kexec on hold for a bit as I clean up the Note 1 and TouchPad port of Debian. I ran into an issue on the Note 1 with Kexec where CM wouldn't mount the internal storage when booted via kexec-hardboot. I still need the Note 3 as my primary phone so I can't hack on it without a backup plan.
EDIT 5: The issue with storage not mounting appears to be related to having an ext-formatted SD card inserted (which is where I keep Debian). Booting without the card inserted works fine. Hopefully the same applies to the Note 3.
EDIT 6: I got the kexecboot kernel builder scripts for the Note 1 up on github now and released the first version of it, so I'm going to look into the Note 3 some more. I didn't realize that the Note 3 uses device tree until I messed with it earlier. I'm not sure if kexec needs to reserve a dtb image for the kernel or not, that could be a major roadblock if so as the patch I ported didn't take device tree into account. I'm not entirely sure how device tree and atags work but somehow they're related apparently, at least in terms of kexec.
EDIT 7: I think I have my build root mostly set up for Note 3. Initial test was a failure, though it did at least attempt to boot my new kernel rather than drop into download mode like my earlier attempts. I need to figure out what device tree stuff is required in order to boot a compiled kernel with the new mkboot tool and then enable fbconsole so I can see when the display changes.
EDIT 8: I think I figured out how to make a dt.img file now for the device tree stuff, but I've found that my ramdisk doesn't work on the stock CM11 kernel binary nor my custom compiled one. It did, however, work when patched into LeanKernel's boot.img (replacing the default ramdisk). This was the result of that: http://i.imgur.com/c2racE1.jpg I may try using the leankernel defconfig as a base instead of the CM11 defconfigs.
EDIT 9: Derp herp derp herp didn't look at the boot partition size...it's 11.0MB. My cm-based boot.img was 12.3MB. Of course that ain't gonna work.
EDIT 10: WOOT! Kernel has booted, xz compression is some wizard level magic, it shaved off like 3MB without changing anything else. Now to reapply the kexec-hardboot stuff and see how it fares.
EDIT 11: I spent some more time looking into kexec-hardboot on the Note 1 (as it's a ton easier to debug since it has a video-mode panel) and figured out how to properly reset it. The important code is in relocate_kernel.S, an assembly function that does the very last wrap-up stuff before rebooting. On the Note I was letting the watchdog timer kick the reset after hanging on an infinite loop, but the Note 3 doesn't seem to have this watchdog in place and will loop endlessly. The important thing to note from this is that relocate_kernel.S uses physical addressing. The Note had a pretty in-depth reboot procedure and it looks like the Note 3 may be a bit simpler. I'll be looking into this soon to see if I can get it rebooting correctly.
EDIT 12: I'm going to use USB serial for debugging instead of messing with the stupid fbconsole. To initialize the USB you need to set up the ID fields in /sys/class/android_usb/android0 and set functions to acm. Then use getty (part of busybox) to open a bash shell on the port with "getty -n -l bash 115200 ttyGS0 linux". Then use minicom or other terminal on PC to connect to the ttyACMx interface.
EDIT 13: I was able to get a working shell through USB and play around with kexec tools directly. It would not boot when I did kexec -e, whether or not I used hardboot or not. I may need to apply a patch to load dtb images for the kexec'd kernel.
EDIT 14: Looks like I'll need to build my own kexec-tools based off the newest release (v2.0.7) which has device tree image support. I'm still looking for a hardboot implementation that uses dtb images.
EDIT 15: I dug through the stack of calls up from machine_kexec to figure out why machine_kexec was never called. It appears that kernel_restart_prepare (kernel/kexec.c, line 1595) might be hanging and keeping the system awake instead of dropping through to machine_kexec() like it should. Since we're rebooting with hardboot anyways it should be reasonably safe to just forget a clean shutdown and cut straight to the machine_kexec() function. The bootloader will reinitialize the hardware anyways. This is hopefully almost the end, as I'm sure my reboot code is being called and it is successfully rebooting. It hasn't booted the new kernel yet but it could be an address issue.
EDIT 16: Something's happening...I think I may be right on the edge of getting it working but not quite there yet. I got it to lock up after rebooting which means that the redirection was successful (redirecting to the kexec kernel instead of the kexec-boot kernel) but the kexec kernel is crashed or something. Probably something to do with device tree. It might require a dt.img passed in or it might require the command line being set.
EDIT 17: I managed to get Tasssadar's MultiROM kexec-tools to build. I talked to XDA user flar2 who had done some work on the HTC One M8 and ran into a similar issue with device tree kernels not booting. He mentioned that there may be some custom device tree entries that aren't being picked up by kexec-tools and gave me a link to a repository to look at. For now, here's my kexec-tools branch based on Tasssadar's work with the fixed-up Makefiles that compile correctly: https://github.com/CalcProgrammer1/kexec-tools/tree/kexec-tools-2.0.2 I will look into this more this weekend or so.
EDIT 18: So the Note 3 kernel doesn't have last_kmsg (RAM console) enabled for some reason, or at least it isn't appearing despite being enabled in config. RAM console shows the dmesg (kernel log) of the previous kernel run so long as the reserved RAM area isn't erased. This is important as it allows viewing any logs left behind by failed-to-boot kexec'd kernels. I'm guessing both the host (kexecboot) and guest kernel will need RAM console to be working for any meaningful debugging. Samsung has all sorts of goofy debug stuff (SEC_DEBUG_) but the RAM console doesn't appear to be part of that.
EDIT 19: After a lot of printk's and a lot of failures I got last_kmsg support working! This means booting a last_kmsg supporting kernel and then rebooting into another last_kmsg supporting kernel will grant you a /proc/last_kmsg file that contains the previous boot's dmesg log. This will be incredibly helpful for kexec testing. For any other kernel devs who want this capability, you need to register a platform_device for ram_console using the start and end addresses already included for the persistent_ram ram_console registration. For some idiot reason it reserves the persistent RAM but it doesn't set up a ram_console device to use said RAM.
EDIT 20: New Tools! With the help of some users in the S4 forum, I have some new debugging tools available to better see what's going on with reboots. First is viewmem (http://blog.maurus.be/2011/01/23/samsung-i9000-irom-dump/) which dumps memory to stdout. The Note 3 kernel has sec_debug which logs boot messages from the bootloader and optionally kernel to address 0x10000008 in memory. Viewmem is able to read this log as well as inspect other memory locations to see if things are where they should be. The other debugging tool is a physical serial port, hidden on the USB data pins. Putting a 615K resistor between GND and the ID pin of the USB connector as well as shorting the VCC and GND pins causes the port to go into serial debug mode on reboot. The D+ and D- pins become TX and RX, and hooking up a 3.3V serial interface (PL2303 USB serial breakout in my case) you can dump bootloader and kernel messages to a PC running a serial console.
cant wait to give it a shot
this sounds amazing for the note 3
sounds like Ubuntu will be coming soon
Cant wait to dual boot AOSP and TW
I'm so proud to be the same t mobile person as you
I take off my hat and bow!
only if I had a bank account I would so donate to you
Just keep doing what your doing
And you will become famous a xda
I will so make this Thread a Newsworthy Thread!
Update 4
Im crying
Well best of luck
Definitely worth waiting for, we'll be here
Robbdreality said:
Definitely worth waiting for, we'll be here
Click to expand...
Click to collapse
+1
I got framebuffer console working on the Note 1 a bit better last night, though it's still not great. I really need to get framebuffer console working on the Note 3 before anything because it makes debugging a whole lot easier. The super-high DPI might become a problem though, the text was already hard to read on the Note 1's 800p screen. This is what I'm looking forward to seeing on the Note 3: http://i.imgur.com/1kmKDOw.jpg
CalcProgrammer1 said:
I got framebuffer console working on the Note 1 a bit better last night, though it's still not great. I really need to get framebuffer console working on the Note 3 before anything because it makes debugging a whole lot easier. The super-high DPI might become a problem though, the text was already hard to read on the Note 1's 800p screen. This is what I'm looking forward to seeing on the Note 3: http://i.imgur.com/1kmKDOw.jpg
Click to expand...
Click to collapse
Same there But ubuntu
What linux is that one
Debian (testing). I chose it over Ubuntu because it works better in a chroot from within Android. Upstart (Ubuntu's init system) doesn't like chroot or running services from in a chroot as well. Ultimately the idea is to be able to use it both as a chroot within Android (to host ssh and samba and such while still being an Android phone) as well as a full blown reboot into Debian system for playing with the GPU and using hardware that Android normally locks. My TouchPad setup is exactly this, where the Debian rootfs is located within Android's data partition as /data/debian and the initramfs init script on my kernel bind-mounts that directory as the root directory before passing over to the Debian init. You could do the same with Ubuntu as well. The biggest issue is the kernel which you can put whatever distro you want on top of.
i wish you all the luck in the world hmm!?! No, ?!? I wish you all the luck in the whole cosmos! @CalcProgrammer1
update 10
im so happy
Agreed, love the progress
Update 11
Keep up the good work
USBhost said:
Update 11
Keep up the good work
Click to expand...
Click to collapse
+1
This is really cool
Sent from my SM-N900T using XDA Free mobile app
iakeco said:
This is really cool
Sent from my SM-N900T using XDA Free mobile app
Click to expand...
Click to collapse
ii there
Update 14, rootin for you
Robbdreality said:
Update 14, rootin for you
Click to expand...
Click to collapse
+1
Robbdreality said:
Update 14, rootin for you
Click to expand...
Click to collapse
Just now root'in? You should've rooted a long time ago! Using Android without root is a nightmare!
CalcProgrammer1 said:
Just now root'in? You should've rooted a long time ago! Using Android without root is a nightmare!
Click to expand...
Click to collapse
I will never get a device without root
The vary day that i got ny N7 i unlocked the bootloader and rooted it lol
But i think he meant something like im cheering for you
Hi all,
Since I haven't seen a kernel tree on XDA that had the mediatek drivers (the ones xiaomi has put in a separate git repo), I thought I'll put them back into the tree.
The drivers have been taken out of the tree from drivers/misc/mediatek. To make them work at all, the makefiles need some changes.
1) In the connectivity folder, to build more than just the wifi drivers, the others folders must be added back into the build (at least, obj-y += {folders}/).
2) The include directives must be changed to include from $(srctree)/drivers/misc/mediatek/... instead of $(TOP)/vendor/.../kernel_modules/...
Besides that, there are some minor changes here and there to get them working properly.
I've managed to get it to boot correctly after disabling stock modules (by moving the folder, otherwise they seem to get inserted even if the drivers are already in the kernel). However, even if the connac device appears in the /sys/devices/platform, wifi still fails to turn on. GNSS turns on, but it is very slow. Only some gps and glonass sats show up, much fewer than normally should, and I could not get a fix (this might be either because there's some firmware problem preventing beidou and galileo from showing up, or the system is too slow and hasn't yet loaded beidou and galileo data - can't tell because I've been indoors and even on stock kernel, cold TTFF is quite long).
Care to share some thoughts? Some resources, maybe?
P.S.: I've not published the merged tree because I've poked it a lot and it's a mess.
I've dug more into this. It's quite likely that the drivers released by Xiaomi don't match the shipped kernel (or the hardware on the device).
It looks like the released wifi driver has trouble accessing the hardware registers and ports on the wifi block. Also, the firmware binary specified in the driver source doesn't match those on vendor (it's searching for WIFI_RAM_CODE_soc1_0_1_1, while stock uses WIFI_RAM_CODE_soc1_0_2a_1; these are hardcoded in the driver). I've searched through the sources for the file loaded by the stock kernel and it's not mentioned anywhere in the source.
Edit: Actually it does match, it's the flavoured firmware branch. I was confused by the comments above the code.
Edit2: Everything boils down to a missing definition in the Makefiles/build options. See below.
Ok, finally found the problem. The modules need to be built with WIFI_IP_SET=2. This flag changes both the name of the firmware and some padding in the structures. That's why it failed so hard.
AAAArgh...
If this works ok, I'll try to post a working tree next couple of days.
I've put the sources on github. Wifi, GPS, NFC, Bluetooth work built-in.
That said, there still seems to be some problems (I'm seeing reboots every 15 mins or so).
I know for a thing that there's a problem with the embedded secure element (somewhere along the TEE/NFC stack), and I think that's what causes the reboots.
Couldn't get the eSE to work; if anyone's interested, the error looks like this:
Code:
[ 197.239862] -(0)[240:teei_switch_thr][TZ_LOG] ESE-S | [phNxpEsePal_spi.cc:171/spiread_dma] <err> dma read nad over time.\x0d
[ 197.241310] -(0)[240:teei_switch_thr][TZ_LOG] ESE-S | \x0d
Which sounds like the eSE server in the TEE can't talk properly to the eSE chip over the spi bus.
However, I've disabled the secure element in Android, and it seems like the problems are gone (though secure card wallets, like Google Pay will have to use a software implementation).
I've disabled the secure element in Android by (replace removal by moving to a backup location at your discretion)
Code:
rm /vendor/etc/init/[email protected]
rm /vendor/etc/init/[email protected]
rm /bin/hw/[email protected]
rm /bin/hw/[email protected]
pm hide com.android.se
It might be that only the last command is necessary though (if you do test this, please reply - I only went up on the chain of dependencies).