Related
This tool is was designed in order to easily patch the registry to force Kies to update your Galaxy S.
This latest version of patcher works even with latest Kies (2.0.0.11014_49_2), all you have to do is to spoof your firmware version to and older one, you can even spoof the product code in order to change it.
The new spoof system works differently from the older patching system, it allow you to use the original dll of kies and works on latest Kies; It should even be future-proof.
IMPORTANT NOTE:
Patcher Version 1.8 doesn't fully work yet.
When I built it i only partially tested. I stopped where it notified me the update were available (because i didn't need an update and i was sure it were like Kies 1.x
After my release i noticed the complaint and i tested it fully, sadly something is missing so the patcher can't be used to fully work with Kies 2.0 yet. Sorry, i'll try to sort it out...
VERSIONS:
Patcher Version 1.7 works with Kies 1.x, while Version 1.8 works from 2.0
PRELIMINARY NOTE:
[WARNING!] Do Not flash Any ROM (firmware) until you can get the 3 buttons DOWNLOAD MODE working, even with this Kies trick.
If you want to test the 3 buttons download mode then notice that you can switch back to normal mode by pulling the battery out and then back in. At the next boot the phone will be back in normal mode.
LAGFIX USERS:
[WARNING!] Remember to disable lagfix before to update.
This will avoid filesystem errors that may occurs at the boot of the new flashed firmware.
INSTRUCTIONS:
1) Download latest Kies Registry Patcher, tool is attachment. Note: It require Microsoft .NET Framework 3.5 or later version.
2) Update Kies to 2.0.0.11014_49_2.
3) Launch Kies Registry Patcher; If you patched the dll in the past with an older version of the patcher then be sure to launch new release as administrator since it have to revert the dll to the original version as the patch isn't needed anymore (Right click on application > Run as Administrator).
4) Launch Kies and connect your phone; Wait for Kies to recognize it properly.
5) You have 2 possibilities now:
5a) Drop down the combo-box "Spoof Product Code as" and select the wanted one. It should automatically fill the "Spoof Software Revision as" textbox with the needed data necessary to find your update.
This feature was added in order to give all the opportunity to use the needed product code. (Special thanks to MCOGW that shared with me his database of product codes/sw revisions).
The label above will be completed with the country related to the chosen product code.
5b) From patcher select:
File > Load Backup
Open the backup that you want to use (e.g. kies-backup-XEU.xml if you want to spoof your phone as XEU, or if your phone is XEU yet and you want to flash it again).
6) From patcher answer "YES" in order to apply the registry update.
7) From Kies you can now update as normal.
====================================================================================================
Note #1:
Remeber that this patch will remain ACTIVE until you set "Enable Spoof" field to False!
It's not a problem but ater you update the phone it's suggested to put that value to false so the patch become inactive.
====================================================================================================
Note #2:
You can play with Advanced settings but those are experimental/untested, so make sure you know what you're doing.
====================================================================================================
1.3.1.0 Update:
- Window 64bit compatibility added.
- You can now update disabling Battery Charge check: Beware, do not update with a very low battery charge level.
- Sha1 evaluation of dll to patch in order to be sure of the version.
====================================================================================================
1.4.0.0 Update:
- Fix in case more than 1 phone is found in registry.
- Removed Framework check cause it had a bug with framework4
- Ability to save Kies ROM when you update your phone (in order to use with Odin or in local mode). [See Note#1]
- Added Local folder textbox in order to specify your saved ROM
- Added management of FotaTest.
====================================================================================================
1.5.0.0 Update:
A new registry patching system has been introduced.
It doesn't need to patch Kies dll anymore and it should be future proof.
Note:
Product Code Spoof have to be last 3 letters only of product code (e.g. ITV for italian product code, XEU for European, etc...).
====================================================================================================
1.6.0.0 Update:
I added to the tool a database of product codes/sw revisions (credits goes to MCOGW that shared with me his db).
====================================================================================================
1.7.0.0 Update:
Added Registry Menu.
Registry > Erase Registry option give you the opportunity to erase DeviceDB registry Key to delete bad settings and so avoiding patcher to work in a possible wrong folder.
Use it only in case of problems (when you follow the guide but you still receive the message that no update is still available for your phone).
Added a component to browse for folders where needed.
====================================================================================================
SPECIAL FUNCTIONS:
1) SAVE A KIES ROM:
You can save a Kies ROM only during a flash update. So, wait for the download from server to be complete (follow the progress in Kies) once the download is complete the rom will be decompressed. After that your phone will be send in download mode and the flash process begin. You have like 2,5 minutes in order to click on: "ROM > Save Rom", don't worry, saving will take like 5 seconds so don't rush, you have a lot of time ;-)
====================================================================================================
2) UPDATE FROM A LOCAL KIES ROM:
You can update your phone using your local files:
You can use the files you saved during your previous update sessions (see point (1)) or download any Kies Rom on XDA.
You have to put these 4 files in a folder (you can use any name for the folder):
0_XXXXXXXXXX.tar
1_csc_dummy.tar
2_phone_dummy.tar
3_contents_dummy.tar
XXXXXXXXXX is your Kies Rom, rename it putting a "0_" in front of the name.
download the dummy files from the attachment or create your own ones (those a just 0' bytes files).
SS_DL.dll isn't used by Galaxy S so you can delete it.
Open the patcher and select:
Enable Local Test > True
Local Binary ZipFolder Path > Put the folder where you keep your local Rom (e.g. c:\MyLocalKiesRom ), the path must NOT end with "\".
Write registry to save the configuration.
Disconnect the ethernet cable (you have to avoid samsung server to answer).
Open Kies and Update as normal.
====================================================================================================
3) DISABLE BATTERY CHARGE CHECK:
You can update even if your battery isn't fully charged.
Actually Kies check that your battery charge is at least 50% before to continue, but if you don't want to wait and you have enough charge (like 20%) you can disable the battery check and update as normal.
Open the patcher and select:
ADVANCED 1 > Enable Battery Charge Check > False
Write registry to save the configuration.
====================================================================================================
You Legend. Thanks. Will save loads of messing about. Good job.
Sent from my GT-I9000 using Tapatalk
This works amazingly. I got my SGS updated to froyo
Sent from my GT-I9000 using XDA App
No Luck In Canada
I tried the fix with no luck... I currently have JH2 and kies 1.5.3.10103.100.
- Without the fix I get a message saying "latest version already installed"
- With the fix I get a message saying "version JF3 cannot be updated"
It was worth a shot though...
@seagryphon:
what backup did u selected?
You have to use the right combinations of informations or you won't find any firmware in samsung server!
Hey Nodial,
I tried "kies-backup-XEU" without modifying what you had in there.
i just done
GREAT JOB...
okay, I figured out the problem... In Canada the the version I got from Bell is I9000M. If I change the registry setting to remove the "M" in the Model name I get the option to upgrade to JPO.
My question is has anyone from Canada tried this? Will the JPO version be compatable with I9000M?
Nice, i didn't even knew bout that difference!
A new version is coming, it will allow you to flash without battery charge check.
1.3.1.0 update. See first post for change log.
Hello, thanks for the app.
But i have some trouble launching it, I tried on 3 different computers (1 win7 and 2 winXP) all with the latest net framework installed but the prog keeps telling me it needs version 3.5 or higher to work.
It sounds really strange to me. Hope you can help
I'm releasing a new version today cause i've added some new tricks.
Ok, i'll disable the framework check as it seems it's bugged for .net 4
Thanks
Nice works
Just waiting for the new version to give it a try. Thanks
Sent from my GT-I9000M using XDA App
1.4.0.0 update. See first post for change log.
doesn't seem to work for me.
Loaded the XEU file, patched the reg and DLL but when i connect the phone it still says its up to date.
god damned vodafone sent an update to my phone last night to add in vodafone crap. phone is even slower now and dying to get standard froyo on it
It could happen on 1.3 if more than 1 phone folder is found and the wrong one is used.
This is fixed on 1.4, have u tested it?
It was 1.4 I tried.
So I tried with 1.3.1. Same result.
Any idea's? I could be missing a step
Did it work for you in canada with a gt-i9000m?
Sent from my GT-I9000M using XDA App
@-l-Z3K3-l-
- Open the patcher, patch the dll if you haven't done it yet (Use last Kies version).
- Open Kies, let it recognize the phone.
- Load a backup! You have to use the XEU one or your own data for your phone model! You need to seek the info in internet, i jusy know the lower version of ITV and XEU.
- Write the registry
- Update using Kies.
@mayo1973
Yes, it works will all Phones, the only problem is the settings are different for each region. You have to seek the right one for your model.
Would be nice to collect them here if someone have some other region settings to share.
Hi everyone,
Many people have complained about the Wave bootloader being closed and that being major problem for the development of alternative OS.
I had a closer look at the booting process and would like to contribute my observations to the community. I shall have little time (next to none) to work on it further, so I'd like someone to take it from this point.
OK, that said I can introduce you to what I found:
The booting process starts with initialization of the hardware, interrupts, etc. and gets to the selection of the booting mode. This is the place that checks the key combination, JIG and possible problems. Basing on this the bootloader will run the phone in either normal boot mode, go to dowload or upload mode.
Normal boot shall start with checking the FOTA module. If you already tried flashing your phone you probably noticed that some versions of the FW include a file with *.fota extension. The file is unencrypted and not signed. It's about 2MB, but the bootloader reserves exactly 3MB for it. FOTA is intended to be used for firmware update over the air, but I know nothing about it being used for Wave. You may read something about the design and get a concept of that process here:
http://www.freepatentsonline.com/pdfb/documents/usapp/patent_pdf/2010/017/US20100175062/pdf/US20100175062.pdf
Basically, it is possible that boot would need to perform some actions that are a result of FOTA. Therefore, during the normal boot it reads the FOTA module from the NAND (0xC600000) and checks whether the module exists and is in the right version. That is done by checking a magic (text "FOTA_ENGINE_VER_INFO_2.0") under the 0xC600100. If it is found missing or incorrect you will end up with the message "FOTA Engine is not intalled" or "FOTA Engine version mismatch" on the screen and you will need to restart your phone in the download mode to load it.
After that, the code checks for additional magic values at 0xC880000. In case it is "BPDZ" it jumps to the code in the FOTA file. The contents of the file is loaded to RAM location 0x43800000 and executed from there.
I've made an experiment as a proof-of-concept and have a confirmed that the above is true and valid information. I crafted a FOTA file longer that the usual attached (to be bigger than 2,5 MB). In case you want to repeat that, remember that last 1024 bytes are not loaded and insert additional data before that. My file had two magic values:
"FOTA_ENGINE_VER_INFO_2.0" at 0x100 offset and "BPDZ" at 0x280000. At offset 0 I've placed my code that started with several NOPs (just in case) and code that called original bootloader functions to display text on the screen.
After loading the file with Multiloader, the message appeared on the screen as expected. Reloading of the original FOTA file made the phone boot normally.
The discovery opens wide area of possibilities starting with replacing bootloader without signing it or using JTAG, multiboot, etc.
As the original bootloader is in the memory as well, we can use it, but I would not recommend that approach as we would need additional version control and changing original routines and data addresses for each version.
OK. I hope I made it clear enough to understand, but I can clarify what I might have omitted in the description. The idea is that someone here would pick that up from where I finished and develop a decent loader leaving the original files (apart from FOTA) untouched.
Best Regards,
mijoma
-----------------------------------
Edit: Added proof-of-concept FOTA file (based on XXJL2 FOTA). Use wisely - remember you take full responsibility for what you load on your phone. Works ONLY with XXJL2 bootloader.
Very interesting ... great job
My little knowledge/experiments...
1.
Before I NEVER updated manually FOTA. I never seen any Errors like other user... with FOTA not installed or something similar.
Maybe reason is, because my testdevice has NO active SIM card, so no network...
2.
I've tested examples from mijoma. On XXJL2 Boot...
Simple only flash FOTA with Multiloader.
At your own risk. Not all sideeffects known.
I had NO problems.
3.
Results... I can't see any special after Flashing. But I can go through internal menu, see Pictures.
http://forum.xda-developers.com/showthread.php?t=906966
Normally I have more messages... but with modified FOTA Wave restarts. So the way is correct.
4.
Delta files are sometimes in Firmware also with Boot... I will add next Link to what I found about Delta files...
Delta Files are part of FOTA concept...
5.
Depend on Firmware... Software update... but sometimes is this point removed and I can't login, because no network...
In other words, I have to start FOTA over this internal menu to see that it is doing something.
Best Regards
@adfree
I think you are testing the previous version. Could you confirm you are using mod version 2?
Best Regards,
mijoma
bplib_S8500OpEuro_XXJL2_mijoma_mod2.zip
You are right, not tested yet. Only prior Version.
I will test today mod2 and report later.
I have to flash back to XXJL2... as I play actual on Orange JE7.
Thank you.
Best Regards
YT: watch?v=A35k3E1F1O4
It's working....
Best regards.
Amazing job dude. It seems like this could help us to change booting stuff
Nice work mijoma !!!
I can confirm it works.
Now I see the same like on this Video:
http://www.youtube.com/watch?v=A35k3E1F1O4
Thanx jedil1 for Link.
Sorry mijoma.
I have no idea where I made mistake...
This time my first Test was Full Flash (without Boot)...
Second only FOTA and it works too... Original, then yours...
If you flash "Full", then you interrupt the Index process at Start, where Blue Screen shows...
Best Regards
Great job!!!
And my opinion,this is a single way to starting full working android on s8500,
because we need to initialize the modem at bootloader stage for fuel gauge.
i temporary use modem from m130k without fuel gauge.
Few Firmware packages have Delta files:
Code:
delta.bin
delta_AP.bin
delta_CFS.bin
delta_CP.bin
delta_CRSRC.bin
delta_FS.bin
delta_LFS_01.bin
delta_LFS_02.bin
delta_RSRC2.bin
Around 16 MB...
If I use Google for "Delta Files FOTA"... then I can also find this:
http://www.faqs.org/patents/app/20100175062
Theory/ideas
What we also can do with this Security hole:
- maybe "move" folder System to SD or internal Memory, to have no more problems with RC1
- maybe someone is smart enough, to integrate Dump Function for Dump whole RAM or moviNAND... like JTAG
See Upload function...
Best Regards
adfree said:
- maybe someone is smart enough, to integrate Dump Function for Dump whole RAM or moviNAND... like JTAG
See Upload function...
Best Regards
Click to expand...
Click to collapse
I think that Samsung have thought of that already. I had not analysed that as so far, but there's UPLOAD option in the bootloader (handled by a bit separate code from DLOAD). I haven't got the wave, so I never tested it.
You can make a patch on my mod and place a direct jump to that code. I've made a quick patch so you can try it out. I don't know whether there's any software that can handle that mode. I've made a look and there are several funny commands that can be used:
"PrEaMbLe"
"AcKnOwLeDgMeNt"
"PoStAmBlE"
"PoWeRdOwN"
"DaTaXfEr"
Remember that this time we're dealing with some real functionality of the bootloader and that may have some consequences so use on your own risk.
Best Regards,
mijoma
----------------------
Edit: Sorry if anyone tried loading it. By mistake I've used addressing from XXJEE. I've changed the name to represent what it was and added a correct file for XXJL2 bootloader
Upload to PC is in combination with Debug Mode higher then Low...
After you see Bluescreen with very interesting infos you can press Button, then Upload to PC on Screen. But I don't know how to catch Data, as no COM Port is visible.
Btw...
Now I know where I made big mistake.
First tests I used XEKC2 Firmware with XXJL2 Bootloader, as I thought its only Bootloader related. Sorry.
My fault.
So there must be more then Bootloader from XXJL2 in handset, to run successfully FOTA Mod2.
About new Mod with Upload, I will investigate this time better, before I'll report.
Thank you.
Best Regards
We need to get this guy a wave to test stuff on! Who wants to donate theirs ha
sabianadmin said:
We need to get this guy a wave to test stuff on! Who wants to donate theirs ha
Click to expand...
Click to collapse
It may have sounded like a joke, but I second that....
He's seems trustworthy and very capable of being sucessful Just like adfree, oleg_k and other guys over there.
I have my paypal account limited but in 1 month I'll b able to donate maybe 20€
Thanks guys, but I don't think it's necessary.
I do it for fun - don't need any other gratification. Wave got me interested with the effort the manufacturer put trying to keep it closed. I don't need a handset to disassemble the bootloader.
The question is more would you like a wave for you're efforts as otherwise you really won't be able to benefit from you're own work when we have meego, android, webOS etc booting on the Wave. Theres no extra pressure, sure you have already done the trickiest part of the work.
No, I'm being completely honest here. I find this rather a weird form of relax than work.
Wave is a nice phone and I think I'm going to get myself one, but I don't expect a gift.
mijoma said:
Wave is a nice phone and I think I'm going to get myself one, but I don't expect a gift.
Click to expand...
Click to collapse
You are a champ, buddy
Good luck !
Sent from my GT-I9003 using XDA App
Hello,
i have made a Firmware Downloader that had the availability to download all Samsung Mobile Fimrwares, but since march this year samsung changed the server, and is using a new system for getting the data. However this tool could help someone who maybe find the new way to download firmwares, it has already access to the old server, only the firmwares are all transfered to the neofus server.
It could help someone, maybe, because i am not allowed to do anything here, cause i am new, i will try to support the new developers.
It is developed in C# .net 4 and you will need kies installed, or the fuscryptlib registered, found in the kies folder or in the app folder.
regsvr32 %Path%/fuscrypt.dll
Should i explain that this downloader had the availability to download also android fw and so on? maybe there is someone who can made it.
It was before march the ultimate tool to get every fw from the server. I tried at my own to make a new one, the my developer mentor tried it, we failed due to lack of time.
Just downloaded the "Slyfer300" app. The UI is superb. Just a pity Samsung has changed the server to their firmwares and we cannot use this tool for now. Let's hope and pray someone comes up and lend a hand to complete this wonderful app. So that we can easily download and flash firmwares manually without the need for kies.
I included a screenshot of this superb app below for the eyes only (until it becomes a fully functional app)
The App worked a half year, samsung changed the servers since March 2011, i was before here @badanation.de and developed it in the past. The app was secret and we offered for everyone free Firmwares of their desire, the only rule was only for badanation members.
I puplished it, cause maybe someone here @xda could make it work with the new server that was a cool time when you start the app and you can download any firmware you want.
The old system was based on a PL/SQL query over PHP, i have found a bug in the system and could request the whole Database from the Firmwares, you can see in advanced mode what was possible.
Also user names and their ... was visible, but i newer wonted to damage samsung i always wanted to help other users with the firmware problems we all have.
The new System is a little bit tricky signatures and so on no more php
As i know here was some nice developers @xda that could maybe improve it. Let us see what the feature brings to us.
Hi, nice tool. Unfortunately it's not working with the new servers. I have made a tool that can download the latest firmware from samsungs new servers, but it still requires an old firmware as input. I have not found any way to browse all firmwares like you could on the old server. A lot have chenged in the way you request firmwares and it unfortunately no possible to reuse this tool on the new server.
Yes, it was not simple to find out the right PL/SQL commands for oracle, it was more a doing by trying thing. But as i saw it on keys the listening method still exists on new server, it is the same database, only with a new system. I have done some Kies 2 researches but than give up, cause of lack of time. I had a tool that can download with the new request system.
Only what you need is to pass through the right PL/SQL command, in Kies you find an CarrierTestMode and ServiceCenterMode, one of this two can listen the whole Phonebinary databases, the code is to huge, i havent done a lot since the half year slyfer worked.
Its in a case simply only need to find out the right command, also what is neccessary to find a security whole on new server, on the old server, it was prohibited to execute SQL statements except of predefined calls, but i found a way as you see, it was more an oracle bug, how you can get anyway in and become the whole database information with dictionary commands out, it was at least so easy to get everything out of there. Then i have done some facelifting and made for me an advanced mode to be prepared of changes, but at the near end it doesnt worked any more.
I think you can get in like kies withouth authentification, as before, cause there is no username or password needet if the table is accessable by everyone, its like free to air.
If you need some tips, how i have found out the way in, i can help you. i dont know how to encrypt the new way, but i know that the answer is in the FusCipherUtil.dll it hink it is named so, dont know it exactle, kies is like an open book as you also seems to know.
Forgotten one thing, if you try to send SQL command that listen whole database, then you will get in timeout, cause oracle needs time to collect all the data, i had problems to recieve simple sized calls from it, so you must limit them that you can recieve the data in time everything over an minuete dont works as i remember.
1250 rows around was for my requests the maximum, everything above, througn a server timeout.
larioteo said:
Forgotten one thing, if you try to send SQL command that listen whole database, then you will get in timeout, cause oracle needs time to collect all the data, i had problems to recieve simple sized calls from it, so you must limit them that you can recieve the data in time everything over an minuete dont works as i remember.
1250 rows around was for my requests the maximum, everything above, througn a server timeout.
Click to expand...
Click to collapse
Your program its more power full then CheckFus.
Advanced mode verry great. Verry frustrated, cant use it for now.
hello larioteo are u still working on the new Kies app ?
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
I use Motorola Edge S, with LOS 19.1. From v20220709 and after, bluetooth cannot be connected any more.
I want to flash back to v20220618, but Motorola system disallow downgrading, even its rom is LOS.
Can anyone tell me how to modify the LOS.zip (e.g. the date in the files of metadata & metadata.pb, checksum, ......), so that I can cheat the system to allow flashing the earlier version, without causing damaging problem ?