{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4.2 - SD
Due to numerous requests, I ported my NAND build to be used also with SD, booting it via MAGDLR or WindowsMobile (Haret)
...: FEATURES :...
1.84 base Deodexed and Zipaligned
RMNET/PPP Selectable via config.txt (boot via WMO only PPP)
Multilanguage and full chinese handwriting support.
Rooted (SU app + SU binaries)
AdFree
AutoAPNs
5mpx camera with face recognition + 800*400 camcorder
HSDPA, GPS, Bluethoot, WiFi all working
% battery icon and status bar icons changed (use original framework-res.apk to go back to stock attached in 2nd post)
fonts changed (use original fonts to go back to stock attached in 2nd post)
[*]Enhanced Shutdown Menu
[*]WiFi MAC Fixed
Working HTC-SENSE.COM, HTC-HUB, HTC-LIKES
Working HTC Headsets using my kernel
Working notification LEDs
[*]Working Streaming Video
[*]Working Flash Player, No more browser crash
Support config.txt to tweak boot options
Modified shutdown android process to cleanly unmount data partition and avoid data corruption.
EXT3 Filesystems to improve data safety and speed.
Personal tweaks to I/O to have the most fast full hd build you ever seen
Fast, Fast, FAST!....... FAST!
Tweaked to be stable, battery efficient and good for daily use.
.
REMOVED APPS (you can install them from market or use the package in second post):
AdobeReader.apk
Facebook.apk
GoogleMaps.apk
Quickoffice.apk
SoundHound_freemium.apk
Street.apk
Talk.apk
Twitter.apk
VoiceCommander.apk
YouTube.apk
Click to expand...
Click to collapse
...: WHAT IS NOT WORKING :...
HTC E-Reader (removed)
Weather could be buggy for someone. If its so for you, try the fix in second post
Click to expand...
Click to collapse
...: CHANGELOG :...
Code:
4.2 - 21 MAR 11
- Fixed Flash player in websites via modified app to not let the market to update it (credits: cmyxlgo)
- Fixed Camera, now no more FC in sharing (credit: aread22, pyrorob)
- Updated ad-free
- Improved data stability
- Improved ppp
- Cleaned system from unuseful stuff
- Optimized and zipaligned again
- Updated to Rafpigna 1.9 OC Kernel, with EB support
4.1 - 12 MAR 11
New base TELUS 1.84.661.1
new kernel rafpigna 1.8 OC
updated gmail
updated market
updated flash player so you will have no more erros (dont let the market to update it!)
updated busybox to 1.18 stable
modified init and init.log to have better debug informations
zip align of all apps on boot to improve speed, ram, and battery drain
updated some driver and libs for better stability
updated all languages including Serbian and handwriting languages
MMS sizes 300kb, 600kb, 1024kb (default 300kb, choose size in the sms settings)
reduced freeze a bit when installing apps from the market
some other small fixes and tweaks I forgot
Reverted to radio drivers from 3.2 for better data stability
Fixed a typo in init causing some issues with data and booting
Fixed some drivers dependencies
Some fixes on some parts of the system to improve stability and speed.
Some other small fixes
3.2.2 - 02 MAR 11
Fixed path issues
3.2.1 - 02 MAR 11
Tweaked booting process to be more compatible
added possibility to change wifi mac address
added another method to boot from a different folder
fixed update installations
3.2 -> first release
Click to expand...
Click to collapse
...: REQUIREMENTS :...
MAGDLR 1.13 or WINDOWS MOBILE
FAT partition as first partition and PRIMARY on sd card, otherwise will not boot
A little bit of brain to read the instructions and dont post questions until you did at least a search in the thread
Click to expand...
Click to collapse
Quadrant @ stock speed ---- Quadrant @ 1,5ghz
(click on the images for bigger size)
...: INSTRUCTIONS :...
Apart from the below instruction you can see also the COLOSSUS_R tutorial HERE
Download the build 7z file
Extract the whole "Android" folder in the root of your sd card. This means you have to extract not only the files inside the folder, but the folder itself!
If you are coming from a previous version and you want to keep your data and settings, dont overwrite the userdata.img file and keep your old one.
Create, inside the folder, a config.txt file based on your needs (see below for instructions). If you dont create one, the default values will be used. Anyway you can create it also on second or any next boot. Some users experienced boot issues with config.txt created with windows notepad. Try to use Notepad++ and select "Conver end line character" to UNIX in the "Edit" menu, before save.
When creating txt files, make sure your Windows is setted up to show extensions also for known files. Otherwise will happen that you will create files like "something.txt.txt" because you dont see the last .txt
If it will not boot after you follow the instructions, read post 3
FOR WINDOWS MOBILE BOOT:
First of all modify the config.txt file in your build folder, with wince=1 or you will be stuck at bootscreen.
Boot Windows Mobile, open file exploer, browse to your sd card and the android folder, tap on CLRCAD.exe (nothing will happen) then on HARET.EXE and wait the boot
First boot will take about 5-10 minutes depending on your sd card speed.
If you hear the bootsound more than one time, you have boot-loop.. something has gone wrong. Read again the instructions, check the md5/sha1 of downloaded file, start all again from scratch.
Once you see the unlock screen, dont touch your phone for 5 minutes.
After the 5 minutes, unlock the screen, do your setup.
When on the sense home screen, wait again 5 minutes without touching anything.
long press on the power button and shutdown the phone
Boot again
Again wait 5 minutes on the lock screen, then unlock it.
Go in settings -> audio -> and disable audible touch tones to avoid robo voice or phone freezes.
Enjoy.
If you want to change the build folder from "Android" to "Anythingelse" just open the startup.txt and add this line: set cmdline "rel_path=YourFolderName"
Folder name must not contains special charactes like . , ! | and so on...
FOR MAGDLR BOOT
Please note: If you want to change the build folder from "Android" to anything else just create a "rafdroid.txt" file on your sd root with the following text inside it: rel_path=YourFolderName
Folder name must not contains special charactes like . , ! | and so on...
Boot in MAGDLR powering on your phone while you press the power button until MAGDLR appears.
Select "SERVICES"
Select "BOOT SETTINGS"
Select "AD SD Dir"
Select the "ANDROID" folder or the folder where you dropped the rom.
Now select "BOOT AD SD" and wait boot
If you hear the bootsound more than one time, you have boot-loop.. something has gone wrong. Read again the instructions, check the md5/sha1 of downloaded file, start all again from scratch.
Once you see the unlock screen, dont touch your phone for 5 minutes.
After the 5 minutes, unlock the screen, do your setup.
When on the sense home screen, wait again 5 minutes without touching anything.
long press on the power button and shutdown the phone
Boot again
Again wait 5 minutes on the lock screen, then unlock it.
Go in settings -> audio -> and disable audible touch tones to avoid robo voice or phone freezes.
Enjoy.
Click to expand...
Click to collapse
...: CONFIG.TXT :...
A config.txt is included in the build folder. It has currently only the "wince=0" option, so you have to change it according to your needs.
Some users experienced boot issues if they create/modify the config.txt file using Windows Notepad. If you have the build not booting, try to use Notepad++ (google for it) and, before saving the file, goes in "Edit" menu, then select "Convert end-line carachter" and select "UNIX"
Also check the you are displaying file extensions. This because if you file extensions are hidden, you will create a config.txt.txt file that will not be read by the system and you will be stuck at boot.
Those are the options you can specify in the file:
gps_zone=[your country]
check http://www.pool.ntp.org/zone/@ for country codes (example: it for italy, us for usa.. and so on...)
wince=[1 or 0]
1 to boot the build via windows mobile
0 to boot the build via magdlr
default is 0
if you try to boot via winmo or magdlr without setting properly this parameter, the build will not boot.
ppp_mode=[1 or 0]
1 to enable PPP
0 to enable RMNET.
Default is 0
If wince=1 default ppp_mode will be 1
old_light_driver=[1 or 0]
0 to use the new light driver (working notification leds, button backlight control)
1 to use the old light driver (no notifications leds, buttons will go off after 10 seconds)
default is 0
auto_btn_backlight=[1 or 0]
1 to have the buttons backlight going off/on with the screen
0 to have the buttons backlight going off after 10 seconds from when the last button is pressed
default is 1
this work only if old_light_driver=0
wifi_mac_change=[1 or 0]
1 tells the system that you will need to change the wifi mac address to a custom one
0 tells the system that you will use the wifi mac address based on device hardware
custom_wifi_mac=yy:yy:yy:yy:yy:yy
here you have to write the wifi mac address you want.
This is needed, and will work, only if you specify wifi_mac_change=1
If you not write any mac address here, the default 00:11:22:33:44:55 will be used
Just an example on how a file could look:
Code:
gps_zone=it
ppp_mode=0
wince=0
old_light_driver=0
auto_btn_backlight=1
Click to expand...
Click to collapse
...: TIPS :...
Robot voice - known issue - disable audible touch tones and no more robot voice.
On every boot an "init.log" is created under your Android folder. Post this file if you have boot loops or booting issues, this will help debug and to solve the issue.
I modified the whole android shutdown process to avoid any data corruption. Please always choose SHUTDOWN instead of REBOOT!!! In this way you wil never have data loss or corruption!!!! Also if in my instructions or somewhere you read "reboot your phone" always SHUTDOWN then power it up again!
Click to expand...
Click to collapse
...: DOWNLOADS :...
Please, if you respect my work, dont upload this file on any other mirror or host, always put the original link in any forum or web page where you are going to post it.
Since the new base, a fresh install is suggested (means dont use the old userdata.img)
You can try to install on old userdata.img just copying all files from the zip except the userdata.img but you can have bugs, issues and loose some functionalities of the new update.
To keep al the bugfixing a FRESH installation is suggested. If you experience any bug not reported in the first post, try a fresh install (new userdata.img) and see if it happens again.
RAFDROID HD 4.2 SD -> DOWNLOAD HERE
MD5: D55FB4F671A79842B9D2618462526BE9
SHA1: 2F38F6F44F91AB54B9F6CA61A2987DF6405AE256
CRC32: 33021A3E
Old versions:
RAFDROID HD 4.1 SD -> DOWNLOAD HERE
MD5: CBDF69DF2382401E0EFFD6031B00D563
SHA1: B879A08475A32CAFB4C392E4B9EEE676FCC93E17
CRC32: 414635DA
RAFDROID HD 3r2f2 SD -> http://www.multiupload.com/HA3TRFQD9S
MD5: BE39664A7F6B4FD40DD614F0EA4FD2B3
SHA1: F508BB2D72ECDDFAF94A379601D964E62917DFFF
CRC32: FF766DAA
Click to expand...
Click to collapse
...: CREDITS THANKS :...
Cotulla and DFT for making all this possible
Darkstone - Special thanks to him for his big help
Rajko,atoore,ocm,Cass,Markinus, LeTama, cedesmith, domineus, imilka, crawlingcity, Sergio76, cmylxgo, dandiest, tytung
rmk40 for the modded su app/bin
All the testers of my NAND build and the themers kurniawan77 and dandsta34
Everyone else I forgot and a lot of other people on #htc-linux-chat
Click to expand...
Click to collapse
...: DONATIONS :...
I'm putting a lot of time in this, nights without sleeping, downloading, flashing, reflashing..So, if you like my work and appreciate it, and you want to buy me a coffe or a beer for chilling out, I will appreciate it you can do this here DONATE otherwise a click on the "thanks" button is still a good idea
Click to expand...
Click to collapse
...: KERNEL :...
My kernel is capable of Overclock up to 1.5Ghz. Anyway overlcock at you risk. I'm not responsible if you will blow your phone
You are free to use any kernel you want. Just make sure to put all the relevant system files (like modules) in the "root" folder structure under Android folder (look following post for instructions)
This build is tested to work properly with my kernel. I will not reply to any issue using other kernels.
You can find my kernel thread here: http://forum.xda-developers.com/showthread.php?t=940823
Click to expand...
Click to collapse
...: AndroidApps installation instruction and filesystem installation instructions :...
If you want to automatically install any app during boot, you can create a folder "AndroidApps" under the Android folder and put the apk there. The apps will be installed during next boot. Please dont do this on first boot because some times can give issues. The folder will be automatically deleted after the apps are installed
If you want to change any system files, you can create a "root" folder under your Android folder. In this "root" folder you have to replicate the structure of the system folders. Example: you want to change the gps.conf file that is in the following path: /system/etc/gps.conf you have to create this folder structure: "root -> system -> etc" and in the last folder (etc) you have to put your modified gps.conf file.Durin boot it will be copied and the folder deleted. Use this method if you want to change kernel and you need to push the new modules.. in that case the folder structure will be "root -> system -> lib -> modules" and here all the modules files.
Click to expand...
Click to collapse
...: Updates :...
Download the zip update that you want to apply
extract the whole "update" and "root" folders in the "Android" folder. This means looking in the Android folder you will have two subfolders "root" and "update" (in some cases the "update" folder is not present in the zip... no needed)
boot the build
FOR 4.X Version ONLY!
Standard Font: -> http://www.multiupload.com/A2V1QT48DI
RafDroid Font -> http://www.multiupload.com/VWNIIH9P2X
Standard Framework (taskbar icons) -> http://www.multiupload.com/YZALGSEPS6http://hotfile.com/dl/109974758/9fa3c11/SD_update_stock_4rX_framework.7z.html
Rafdroid Framwork (taskbar icons) -> http://www.multiupload.com/OOYO7UZKXE
Removed Apps: extract the whole folder in your Android folder and boot-> http://www.multiupload.com/GUS146P63W
Weather fix (if your weather doesn't update or it's buggy) -> http://www.multiupload.com/IF5FD2784R
FOR 3.X Version ONLY!
Standard Font: -> http://www.multiupload.com/A2V1QT48DI
RafDroid Font -> http://www.multiupload.com/VWNIIH9P2X
Standard Framework (taskbar icons) -> http://www.multiupload.com/JAA3K6VLJM
Rafdroid Framwork (taskbar icons) -> http://www.multiupload.com/77TLLYZEHD
Removed Apps: extract the whole folder in your Android folder and boot http://www.multiupload.com/LWIZC71LPJ
Click to expand...
Click to collapse
To do list (all those things will be uploaded on sunday night CET )
Provide zips for stock font and stock framework/status bar
Provide zips for themes like in the screenshots
Provide zip of removed apps
Check if this works with WP7 partitioned sd card
Do you have problems in booting?
check that your first partition is fat32
check that your fat partition and all other partitions (example the ones created by wp7) are primary partitions.
follow this tips, thanks to zarathustrax -> http://forum.xda-developers.com/showpost.php?p=11688635&postcount=52
if nothing above works, consider to format your sd card with panasonic sd formatter, using "full erase" method. You can find the tool as attachment in the bottom of this post.
check that you have config.txt inside your build folder
check that you are editing/creating the config.txt with a unix compatible text editor like notepad++ (read the config.txt instruction in post 1 to understand how to use)
if you changed the build folder name (example: from Android to RafdroidSomething) make sure you have a "rafdroid.txt" file in your sd card root and in it you have a line rel_path="RafdroidSomething"
if still no luck, try to post your problem but dont forget to post:
- are you using wmo or magldr?
- how is your config.txt?
- did you keep the enclosed userdata.img or changed with your own?
- are you using the included kernel (zimage)?
- a "init.log" file inside the android folder is created? If yes, post it!
- did you copy the "whole" android folder, including the folder itself, on the root of sd card?
- did you changed the folder name?
More info you will provide, more possibility you have that i or someone else can give you the solution to your issues.
Click to expand...
Click to collapse
...: FAQ :...
q) Can you provide a mirror for the downloads
a) I'm sorry but the answer is "no". I pay hotfile every month and the downloads give me the possibility to pay it. I dont do this for money, but I also dont want to waste my money
q) My phone sometimes freeze and I have to reboot.
a) Go in Settings -> Audio -> disable audible touch tones. this will solve the issue in most of the cases.
q) During/after boot a window appears with "System process not respoding". What I have to do?
a) This is caused from the new audio driver I used. The new audio driver has better phone stability and no robo voice. You have two choices: 1) Click on "wait" and all will be fine OR 2) download the "old_acdb_file.zip" and flash it via recovery. In this way you will not have the error anymore but you will start having robo voice on first call (you can avoid this disabling audible touch tones) and could happen that your phone freezes when receiving a call. It's your choiche. I preferred the "window error" one because for me is more important to have a working phone than an error window appearing at boot.
q) I have robo voice when I make a call
a) To avoid this, disable "audible touch tones" from the "settings -> audio" menu. You will have no-more robo voice also if you reboot.
a) During the robo-voice call, enable the speaker, then disable it. You will have no more robo-voice until next reboot.
q) I have very low audio during calls
a) During the call, enable the speaker, then disable it. You will have loud volume until next reboot.
q) after boot I see only a white screen with a green htc logo
a) just wait. It can take fro 5 up to 20 minutes depending on your sd card. There are no issue. The build booted fine, it's just copying all the files to SD. This will happen only on first installation.
q) I'm having high battery drain
a) Try reboot. Try disabling gps in location. As you can see from the screenshot I have 4mA with WIFI active! Also be careful. If during google account setup you choose to backup/restore all your data, the sync process will be dramatic heavy because it has to reinstall all your apps. It could need a couple of hours to settle. Also high battery drain could be caused by SD. try another one.
q) It's really laggy!!!!
a) as all Desire HD builds this is BIG! This needs at least 10-15 minutes after boot to be usable. Then try to use it for 5-6 hours.. and do a couple of reboots.. you will see that the speed will improve. After 24 hours of use and 4-5 rebots this will be really fast.
q) It lags when I'll install apps?
a) yes a little. Just to say: I have a desire hd... it lags also in the same case.. very few.. but the lag is there.. so it's an issue form desire hd base.
q) I have no GPS or the fix is really slow
a) Firs fixt can take up to 5 minutes. just wait.You can edit the config.txt gps_zone= to your country. See here for the right strings http://www.pool.ntp.org/zone/@ if this not solves, try use QuickGps from the market to download a-gps data.
q) Can I unmount the SD while in use or connect the phone as mass storage to my pc while in use?
a) No. Is dangerous for your files
q) It not boots
a) partition again and format again your sd card. follow the guide linked in the first post. post your init.log file for help
q) I have no data/3G/HSDPA
a) probably you have to set your apn manually. google it for tips on how to do and what settings are need for your carrier
q) How do I remove BOOTSOUND / How do I change bootanim
a) bootsound and bootanim are located in /system/customize/resource
Just delete android_audio.mp3 if you dont want sound
q) I have wake up lag
a) It's an issue that devs are trying to solve. It's not related to the build itself. In the Q&A Forum there is a thread about this problem. HERE, HERE,....
q) I have issues in flash during web brosing, the browser force closes
a) If you have issues with flash videos on website, you need an older flash version. Check this post. Thanks to Jayedamina http://forum.xda-developers.com/show...&postcount=280
Click to expand...
Click to collapse
...............
--- last one for me... just in case... ---
Wow, this is awesome.. thanks for showing the SD crowd a little love! downloading now
Really nice to see your HD build on SD.
Thanks!
rafpigna, your hd builds are maybe the best desire hd based builds for hd2
i'm very glad that you've ported it for running from magldr, thanks
Thank's !
Downloaded it,setting up right now
booted just fine .
Data working fine,arows are not working. EDIT:fine after restart !)
Thank's for the SD build !
finally see you here in SD builds, one of my favorite chief. Thank Raf.
Oh my God if i can only send a beer through package! You rock my HD2
Thanks Raf, how to restore stock font?
Master chief ! many thanks from sd lovers !
Thanks for the ROM mate..
I have read alot about its NAND version and about its wonderful performance..
Just tried it now ( SD/WinMo/No MAGLDR ), it ran well on me test card ( 8GB ), but when I tried it on me main 16 GB card, it just stucks on the first boot screen.. looks like it has something to do with SD partitionning..
P.S. both cards were unpartitionned...
Cheers...
jaguaralani said:
Thanks for the ROM mate..
I have read alot about its NAND version and about its wonderful performance..
Just tried it now ( SD/WinMo/No MAGLDR ), it ran well on me test card ( 8GB ), but when I tried it on me main 16 GB card, it just stucks on the first boot screen.. looks like it has something to do with SD partitionning..
P.S. both cards were unpartitionned...
Cheers...
Click to expand...
Click to collapse
Your init.log of unsuccessful boot would help me to find if there is an issue
Sent from my Desire HD using XDA App
Unfortunately,on WinMo boot, no fires hangs on the screenshot RAFDROID and nothing else for over 20 minutes.
What can I do?
init.log:
Code:
e2fsck on loop0
/dev/block/loop0: clean, 1492/25600 files, 95127/102400 blocks
e2fsck on loop1
/dev/block/loop1: clean, 11/65536 files, 12644/262144 blocks
Available space on partitions:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mmcblk0p1 7774208 3071040 4703168 40% /bootsdcard
/dev/block/loop0 403144 374052 8612 98% /system
/dev/block/loop1 1032088 34088 945572 3% /data
Mounted partitions:
rootfs on / type rootfs (rw)
proc on /proc type proc (rw,relatime)
none on /dbgfs type debugfs (rw,relatime)
/dev/block/mmcblk0p1 on /bootsdcard type vfat (rw,noatime,nodiratime,fmask=0111,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/loop0 on /system type ext3 (rw,noatime,nodiratime,errors=continue,data=writeback)
/dev/block/loop1 on /data type ext4 (rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered,noauto_da_alloc)
checking loop0
tune2fs 1.41.3 (12-Oct-2008)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: 4e17b557-ed30-42e8-9160-b39a0a76896e
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file
Filesystem flags: signed_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 25600
Block count: 102400
Reserved block count: 5120
Free blocks: 7273
Free inodes: 24108
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 24
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 6400
Inode blocks per group: 400
Filesystem created: Sat Feb 26 07:02:59 2011
Last mount time: Sat Feb 26 17:51:04 2011
Last write time: Sat Feb 26 17:51:04 2011
Mount count: 2
Maximum mount count: 21
Last checked: Sat Feb 26 07:02:59 2011
Check interval: 15552000 (6 months)
Next check after: Thu Aug 25 07:02:59 2011
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
Default directory hash: half_md4
Directory Hash Seed: d4b9346e-8363-420c-ab55-c2296936941e
Journal backup: inode blocks
checking loop1
tune2fs 1.41.3 (12-Oct-2008)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: deefdaf7-4c6e-4e21-bc36-a6b0e4c4300f
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file
Filesystem flags: signed_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 65536
Block count: 262144
Reserved block count: 13107
Free blocks: 249500
Free inodes: 65525
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 63
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
Filesystem created: Sat Feb 26 02:55:15 2011
Last mount time: Sat Feb 26 17:51:06 2011
Last write time: Sat Feb 26 17:51:06 2011
Mount count: 1
Maximum mount count: 34
Last checked: Sat Feb 26 02:55:15 2011
Check interval: 15552000 (6 months)
Next check after: Thu Aug 25 02:55:15 2011
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
Default directory hash: half_md4
Directory Hash Seed: 5b971090-c3f1-4206-8a0d-392e2f5fe4c1
Journal backup: inode blocks
gps_zone
pl
ppp_mode
0
sd_boost
wince
0
old_light_driver
0
auto_btn_backlight
0
+++++++ GPS ZONE CHANGED +++++++
+++++++ MAGLDR MODE ACTIVATED +++++++
+++++++ RMNET MODE ACTIVATED +++++++
+++++++ BTN BACKLIGHT AUTO-OFF ACTIVATED (echo 1) +++++++
rafpigna said:
Your init.log of unsuccessful boot would help me to find if there is an issue
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
My Pleasure !
Thanks....
but it did not initiate any init.log !!!
and this was me config.txt
gps_zone=uk
ppp_mode=1
wince=1
old_light_driver=0
auto_btn_backl
Have realy been waiting for this - so thanks rafpigna.
Just wating for "Provide zips for stock font" ;-)
jaguaralani said:
My Pleasure !
Thanks....
but it did not initiate any init.log !!!
and this was me config.txt
gps_zone=uk
ppp_mode=1
wince=1
old_light_driver=0
auto_btn_backl
Click to expand...
Click to collapse
If there is no log means SD card is not mounted. Are you using wp7 or wm?
Sent from my Desire HD using XDA App
rafpigna said:
If there is no log means SD card is not mounted. Are you using wp7 or wm?
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
WM 6.5>>>>>>>>>>>
This is my partition table as generated by gdisk
Logical sector size: 512 bytes
Disk identifier (GUID): 98101B32-BBE2-4BF2-A06E-2BB33D000C20
Partition table holds up to 32 entries
First usable sector is 34, last usable sector is 15269854
Partitions will be aligned on 2-sector boundaries
Total free space is 313196 sectors (152.9 MiB)
Code:
# Name Start (sector) End (sector) Size Size (Sectors) Partition GUID Code
1 modem 131072 262143 64 MB 131072 EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
2 sbl1 262144 263167 512KiB 1024 DEA0BA2C-CBDD-4805-B4F9-F428251C3E98
3 sbl1bak 263168 264191 512KiB 1024 DEA0BA2C-CBDD-4805-B4F9-F428251C3E98
4 aboot 264192 266239 1024KiB 2048 400FFDCD-22E0-47E7-9A23-F16ED9382388
5 abootbak 266240 268287 1024KiB 2048 400FFDCD-22E0-47E7-9A23-F16ED9382388
6 rpm 268288 269311 512KiB 1024 098DF793-D712-413D-9D4E-89D711772228
7 rpmbak 269312 270335 512KiB 1024 098DF793-D712-413D-9D4E-89D711772228
8 tz 270336 271871 768KiB 1536 A053AA7F-40B8-4B1C-BA08-2F68AC71A4F4
9 tzbak 271872 273407 768KiB 1536 A053AA7F-40B8-4B1C-BA08-2F68AC71A4F4
10 pad 273408 275455 1024KiB 2048 EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
11 modemst1 275456 278527 1.5MiB 3072 EBBEADAF-22C9-E33B-8F5D-0E81686A68CB
12 modemst2 278528 281599 1.5MiB 3072 0A288B1F-22C9-E33B-8F5D-0E81686A68CB
13 misc 281600 283647 1024KiB 2048 82ACC91F-357C-4A68-9C8F-689E1B1A23A1
14 fsc 283648 283649 1024Bytes 2 57B90A16-22C9-E33B-8F5D-0E81686A68CB
15 ssd 283650 283665 8KiB 16 2C86E742-745E-4FDD-BFD8-B6A7AC638772
16 splash 283666 304145 10MiB 20480 20117F86-E985-4357-B9EE-374BC1D8487D
17 DDR 393216 393279 32KiB 64 20A0C19C-286A-42FA-9CE7-F64C3226A794
18 fsg 393280 396351 1.5MiB 3072 638FF8E2-22C9-E33B-8F5D-0E81686A68CB
19 sec 396352 396383 16KiB 32 303E6AC3-AF15-4C54-9E9B-D9A8FBECF401
20 boot 396384 461919 32MiB 65536 20117F86-E985-4357-B9EE-374BC1D8487D
21 system 461920 4557919 2GB 4096000 97D7B011-54DA-4835-B3C4-917AD6E73D74
22 persist 4557920 4623455 32MiB 65536 6C95E238-E343-4BA8-B489-8681ED22AD0B
23 apedata 4623456 4688991 32MiB 65536 6C95E238-E343-4BA8-B489-8681ED22AD0B
24 cache 4688992 5213279 256MiB 524288 5594C694-C871-4B5F-90B1-690A6F68E0F7
25 recovery 5213280 5278815 32MiB 65536 9D72D4E4-9958-42DA-AC26-BEA7A90B0434
26 devinfo 5278816 5280863 1024KiB 2048 1B81E7E6-F50D-419B-A739-2AEEF8DA3335
27 keystore 5373952 5374975 512KiB 1024 DE7D4029-0F5B-41C8-AE7E-F6C023A02B33
28 oem 5374976 5506047 64MiB 131072 7DB6AC55-ECB5-4E02-80DA-4D335B973332
29 config 5506048 5507071 512KiB 1024 91B72D4D-71E0-4CBF-9B8E-236381CFF17A
30 userdata 5507072 15269854 4.7GiB 9762783 1B81E7E6-F50D-419B-A739-2AEEF8DA3335
My version of the tool is this
Code:
!/usr/bin/python
#===========================================================================
# This script parses "partition.xml" and creates numerous output files
# specifically, partition.bin, rawprogram.xml
# REFERENCES
# $Header: //source/qcom/qct/core/pkg/bootloaders/rel/1.2/boot_images/core/storage/tools/jsdcc/partition_load_pt/PartitioningTool.py#2 $
# $DateTime: 2012/01/12 16:00:13 $
# $Author: coresvc $
# when who what, where, why
# -------- --- -------------------------------------------------------
# 2011-03-22 ah rawprogram for GPT for 'grow' partition, since mjsdload.cmm couldn't handle big number
# 2011-03-22 ah Corrected final disk size patch (off by 1 sector), corrected GPT labels (uni-code)
# 2011-03-18 ah Fixed default bug for DISK_SIGNATURE, align_wpb -> align
# 2011-03-16 ah New DISK_SIGNATURE tag added for MBR partitions, Split partition0.bin into
# MBR0.bin and EBR0.bin, Corrected bug in backup GPT DISK patching
# 2011-03-10 ah Removes loadpt.cmm, splits partition0.bin to MBR0.bin, EBR0.bin
# 2011-03-09 ah Much more error checking, cleaner, adds "align_wpb" tag
# 2011-02-14 ah Added patching of DISK for GPT
# 2011-02-02 ah Allow MBR Type to be specified as "4C" or "0x4C"
# 2011-25-01 ah Outputs "patch.xml" as well, allows more optimal partition alignment
# 2010-12-01 ah Matching QPST, all EXT partitions 64MB aligned (configurable actually)
# More error checking, Removed CHS option, GPT output is 2 files (primary and backup)
# 2010-10-26 ah better error checking, corrected typo on physical_partition for > 0
# 2010-10-25 ah adds GPT, CFILE output, various other features
# 2010-10-08 ah released to remove compile errors of missing PERL script modules
I am purposely trying to keep my fsc partition to 1kb. I can make the change in my xml file to 2kb and the tool will continue. If I leave it at 1kb it will error out. Anyone else have this issue?
Should have held off asking. Once I found a newer version of the tool that issue is solved. Case closed.
follows the link of Stock Moto X4 ROM with Android 7.1.1 and September patch.
Model: X4 (Payton)
Version: NPW26.83-34-0-1
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
The linked page shows a error, will be better if you can upload the file.
Yeah, link is borked. But I may pull it anyway... will post here if I do.
Had my XT1900-1 (Project Fi) for about an hour before I got bored and the bootloader was unlocked.
Thinking of rooting just to debloat (don't get me started on how bloated the Android One build is)... seems like root will be pretty straightforward given that unlock is painless and partition access seems unrestricted. Haven't tried yet, but thinking that just perms and pushing su might do the trick. Would like to have the device for a couple days before I go that far. [edit: Actually, Magisk looks like a pretty good bet w/o custom recovery... may try that]
Then maybe, if I have time start gathering vendor stuff/blobs/etc and build... something.
Anyone else out there tinkering yet?
mightysween said:
Yeah, link is borked. But I may pull it anyway... will post here if I do.
Had my XT1900-1 (Project Fi) for about an hour before I got bored and the bootloader was unlocked.
Thinking of rooting just to debloat (don't get me started on how bloated the Android One build is)... seems like root will be pretty straightforward given that unlock is painless and partition access seems unrestricted. Haven't tried yet, but thinking that just perms and pushing su might do the trick. Would like to have the device for a couple days before I go that far. [edit: Actually, Magisk looks like a pretty good bet w/o custom recovery... may try that]
Then maybe, if I have time start gathering vendor stuff/blobs/etc and build... something.
Anyone else out there tinkering yet?
Click to expand...
Click to collapse
I heard that the reason for the bloat is due to a huge number of partitions that consume space. As such, debloating may not be as easy as you hoped...
ebrandsberg said:
I heard that the reason for the bloat is due to a huge number of partitions that consume space. As such, debloating may not be as easy as you hoped...
Click to expand...
Click to collapse
Just ran cat /proc/partitions.... dang, you are right
|payton_sprout:/ $ cat /proc/partitions
major minor #blocks name
1 0 8192 ram0
1 1 8192 ram1
1 2 8192 ram2
1 3 8192 ram3
1 4 8192 ram4
1 5 8192 ram5
1 6 8192 ram6
1 7 8192 ram7
1 8 8192 ram8
1 9 8192 ram9
1 10 8192 ram10
1 11 8192 ram11
1 12 8192 ram12
1 13 8192 ram13
1 14 8192 ram14
1 15 8192 ram15
253 0 1048576 zram0
179 0 30535680 mmcblk0
179 1 3584 mmcblk0p1
179 2 3584 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 2048 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 128 mmcblk0p9
179 10 128 mmcblk0p10
179 11 512 mmcblk0p11
179 12 512 mmcblk0p12
179 13 1024 mmcblk0p13
179 14 1024 mmcblk0p14
179 15 512 mmcblk0p15
179 16 512 mmcblk0p16
179 17 512 mmcblk0p17
179 18 512 mmcblk0p18
179 19 512 mmcblk0p19
179 20 512 mmcblk0p20
179 21 128 mmcblk0p21
179 22 128 mmcblk0p22
179 23 256 mmcblk0p23
179 24 256 mmcblk0p24
179 25 112640 mmcblk0p25
179 26 112640 mmcblk0p26
179 27 1 mmcblk0p27
179 28 8 mmcblk0p28
179 29 16384 mmcblk0p29
179 30 16384 mmcblk0p30
179 31 1024 mmcblk0p31
259 0 512 mmcblk0p32
259 1 512 mmcblk0p33
259 2 2048 mmcblk0p34
259 3 2048 mmcblk0p35
259 4 6144 mmcblk0p36
259 5 6144 mmcblk0p37
259 6 32768 mmcblk0p38
259 7 512 mmcblk0p39
259 8 128 mmcblk0p40
259 9 16384 mmcblk0p41
259 10 512 mmcblk0p42
259 11 8192 mmcblk0p43
259 12 65536 mmcblk0p44
259 13 65536 mmcblk0p45
259 14 16384 mmcblk0p46
259 15 16384 mmcblk0p47
259 16 1024 mmcblk0p48
259 17 8192 mmcblk0p49
259 18 256 mmcblk0p50
259 19 256 mmcblk0p51
259 20 1 mmcblk0p52
259 21 1 mmcblk0p53
259 22 4608 mmcblk0p54
259 23 4608 mmcblk0p55
259 24 33424 mmcblk0p56
259 25 33424 mmcblk0p57
259 26 64 mmcblk0p58
259 27 64 mmcblk0p59
259 28 8192 mmcblk0p61
259 29 8192 mmcblk0p62
259 30 589824 mmcblk0p63
259 31 589824 mmcblk0p64
259 32 4227072 mmcblk0p65
259 33 4227072 mmcblk0p66
259 34 20262895 mmcblk0p67
179 32 4096 mmcblk0rpmb
252 0 4161104 dm-0
252 1 580580 dm-1
Click to expand...
Click to collapse
---------- Post added at 02:09 PM ---------- Previous post was at 01:56 PM ----------
Looks like the OP file was a leaked Brazilian version of the firmware... wonder if the boot.img is the same as US ?
And also looks like Motorola may be giving each variant of the device its own device name... not sure if this will be good down the line, development-wise, or not:
ro.product.name=payton_fi
ro.product.device=payton_sprout
Click to expand...
Click to collapse
So is it because of project Treble that we have such large system partition. Using 13 GB is too much.
saketkutta said:
So is it because of project Treble that we have such large system partition. Using 13 GB is too much.
Click to expand...
Click to collapse
Is this the partition scheme for Treble? If so, I'm fine with this personally, as it means they have thought ahead to help future-proof the phone (if there is such a thing).
I was seeing users in other threads saying it takes 16-18GB. That's just ridiculous. It should be half that, at most. My brand new install of OS X 10.13 High Sierra doesn't even take up that much space.
crazyates said:
I was seeing users in other threads saying it takes 16-18GB. That's just ridiculous. It should be half that, at most. My brand new install of OS X 10.13 High Sierra doesn't even take up that much space.
Click to expand...
Click to collapse
My custom OS on Nexus 5X took little more than 4 GB. Even if it was project treble (which is not confirmed yet BTW) it should not take more than 9 GB or 10 GB max. Mine out of the box it was 13 GB and something which is ridiculous)
Where did you get the ROM from? Link above is dead?
Iansip said:
Where did you get the ROM from? Link above is dead?
Click to expand...
Click to collapse
I don't think anyone got it here... I saw it bouncing around a couple Brazilian servers, but not open to download. Now that I look, it is the same Build # as the Project Fi version. So, hopefully it will turn up somewhere.
Seems the link in the OP is not dead, just goes to a secure server. It was originally posted on some G+ feeds, but no one has mirrored it yet, apparently
Actually, looks like that whole server is down right now. Every URL returns the same XML error. So maybe it will come back to life soon...
Oh, look at that... Moto has either geo or ISP restrictions on their download! VPN Proxy through server in Los Angeles, and download is running (sloooooowwwly).
Will update tomorrow morning.
UPDATE: Download died at 1.1 GB and the VPN workaround is no longer working. Grrrrr. Could probably extract boot.img anyway, but with no way to check the hash and no images to fall back on, too risky to actually patch/flash it
Got it... well, I have a completed download -- Obviously there is no way to verify the file since I have no MD5/SHA to check against. That said, the archive opens without errors, so I have boot.img now, just not enough stupidity to modify it and flash an unverified firmware back onto a brand new device.
Have a mirror uploading, will share when complete and maybe can get added to the OP.
WARNING: This is unverified fimware for testing/research only. Please don't flash it and then complain when you paperweight your new X4.
UPDATED 10-27-2017: This ZIP has several corrupt files... verify anything against the MD5 in the "flashfile.xml" file before using!
FILE: PAYTON_NPW26.83-34-0-1_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
SIZE: 2702597112 bytes
SHA256 (unverified on the Motorola end!!!): 124f53fef572850532d029d00166829e200b777491502504c9de215fe7dd1046
DOWNLOAD: https://drive.google.com/open?id=0ByZWXbOZqmVqQ09FUXliN3hYMGs
@Anderson_ARS , can you add this to the OP to save people asking the same question over and over and over? Thanks
mightysween said:
Yeah, link is borked. But I may pull it anyway... will post here if I do.
Had my XT1900-1 (Project Fi) for about an hour before I got bored and the bootloader was unlocked.
Thinking of rooting just to debloat (don't get me started on how bloated the Android One build is)... seems like root will be pretty straightforward given that unlock is painless and partition access seems unrestricted. Haven't tried yet, but thinking that just perms and pushing su might do the trick. Would like to have the device for a couple days before I go that far. [edit: Actually, Magisk looks like a pretty good bet w/o custom recovery... may try that]
Then maybe, if I have time start gathering vendor stuff/blobs/etc and build... something.
Anyone else out there tinkering yet?
Click to expand...
Click to collapse
I'd love to see a unlock/root method. Hope to see TWRP asap!
Slickademo said:
How do you unlock and root? I just got mine today
Click to expand...
Click to collapse
Unlock is just a regular Motorola unlock... lot of threads on how that is done.
Root is a little more risky and complicated to explain here. The first thing we all need is a trusted factory image -- hopefully the one above is just that. I would suspect that once we confirm a factory image, root methods will be plentiful.
mightysween said:
Got it... well, I have a completed download -- Obviously there is no way to verify the file since I have no MD5/SHA to check against. That said, the archive opens without errors, so I have boot.img now, just not enough stupidity to modify it and flash an unverified firmware back onto a brand new device.
Have a mirror uploading, will share when complete and maybe can get added to the OP.
Click to expand...
Click to collapse
I have tried downloading the file several times and always get to the very end and then it fails. I'm using idm and multiple threads and maybe I should try just a single thread..
once I get it downloaded I will validate the checksum with yours.
edit: I should add that I am in Vegas and have been able to access the link directly from the day it was posted.
Jayman007 said:
I have tried downloading the file several times and always get to the very end and then it fails. I'm using idm and multiple threads and maybe I should try just a single thread..
once I get it downloaded I will validate the checksum with yours.
edit: I should add that I am in Vegas and have been able to access the link directly from the day it was posted.
Click to expand...
Click to collapse
Oh, neat...definitely IP restricted then as I tried a VPN in LV and was still blocked. Wonder what the story is there!
Yes, if you end up with the same SHA256 let me know, we can at least be sure the file is intact.
---------- Post added at 10:37 PM ---------- Previous post was at 10:35 PM ----------
Jayman007 said:
I have tried downloading the file several times and always get to the very end and then it fails. I'm using idm and multiple threads and maybe I should try just a single thread..
once I get it downloaded I will validate the checksum with yours.
edit: I should add that I am in Vegas and have been able to access the link directly from the day it was posted.
Click to expand...
Click to collapse
Also FWIW, using that proxy link I posted gave me dl speeds of 2.5-3 Mbps, and plowed straight through to 100%.
mightysween said:
FILE: PAYTON_NPW26.83-34-0-1_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
SIZE: ~2.0 GB
CHECKSUM: UNVERIFIED! (my local SHA256: f8efa78d21f0fd4b968e860ec06b85442caaf7a93c325fbe7c5c0913306af86e)
DOWNLOAD: https://mega.nz/#!RkM2nSpL!4kHuZQfyHoSfeD-bfCcRxOi3A3rO7hz37RGcxRCglic
@Anderson_ARS , can you add this to the OP to save people asking the same question over and over and over? Thanks
Also, if you wish to try a direct download from Motorola, this link may work... it is a proxy download through NordVPN. Again, no guarantees and no way to verify (though if you end up with the same SHA256 as above, there is good chance the file is intact).
DIRECT DOWNLOAD (via anon proxy): http://proxy-it.nordvpn.com/browse....cbNvGOLw5iqOebtX0lAb+hCJw==&b=1&f=norefer&pr=
Click to expand...
Click to collapse
I downloaded it via the proxy and have the same checksum as you, so at least this means that your download is *probably* not corrupt. I don't have the device, so I'm certainly not going to flash it.
Code:
f8efa78d21f0fd4b968e860ec06b85442caaf7a93c325fbe7c5c0913306af86e PAYTON_NPW26.83-34-0-1_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
gee one said:
I downloaded it via the proxy and have the same checksum as you, so at least this means that your download is *probably* not corrupt. I don't have the device, so I'm certainly not going to flash it.
Click to expand...
Click to collapse
Thank you kindly! I downloaded again as well with same checksum, so I think we can assume the file is intact.