I want to see the early boot messages after power on my Photon, it will be very useful for new kernel port testing. I've found that Atrix 4G can have UART cable to access the early boot messages in this thread:
http://forum.xda-developers.com/showthread.php?t=1081743&highlight=uart
My question is, can Photon also use the same cable to access UART? I've tried to make such cable, but there is nothing send to PC. I can't figure out what is going on. Is there any other way to see the early boot messages?
Set debugging to 7 and enable uart in menuconfig when compiling your kernel
skytsai said:
I want to see the early boot messages after power on my Photon, it will be very useful for new kernel port testing. I've found that Atrix 4G can have UART cable to access the early boot messages in this thread:
http://forum.xda-developers.com/showthread.php?t=1081743&highlight=uart
My question is, can Photon also use the same cable to access UART? I've tried to make such cable, but there is nothing send to PC. I can't figure out what is going on. Is there any other way to see the early boot messages?
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
Sorry, could you give me more detail? What's the meaning of "Set debugging to 7"? And for "enable uart in menuconfig", is it in Low-level debug console UART as below? Which one should I select? Thank you so much in advanced!!
───────────────── Low-level debug console UART
│ Use the arrow keys to navigate this window or press the hotkey of │
│ the item you wish to select followed by the <SPACE BAR>. Press │
│ <?> for additional information about this option. │
│
│ │ (X) None │ │
│ │ ( ) UART-A │ │
│ │ ( ) UART-B │ │
│ │ ( ) UART-C │ │
│ │ ( ) UART-D │ │
│ │ ( ) UART-E
jokersax11 said:
Set debugging to 7 and enable uart in menuconfig when compiling your kernel
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
myself and mrinehart93 tested with a bunch of kernels and the cables
http://forum.xda-developers.com/showpost.php?p=17245085&postcount=49
atrix doesnt support it. this is the first ive heard of anyone having it work on this phone either
I've been talking with some nvidia guys and uart kinda works on .32. Its mostly getting the right setup. It does have to be enabled by kernel. I'll post more as I find out
Sent from my MB855 using XDA App
Thanks, I'm looking forward to it.
jokersax11 said:
I've been talking with some nvidia guys and uart kinda works on .32. Its mostly getting the right setup. It does have to be enabled by kernel. I'll post more as I find out
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
Related
Hello, readers.
I am about to receive a MT6577-based phone. My religion prohibits me from using windows :silly: and I am using Linux since good old 1993,
I have done a lot of reading during the past months. I have installed the Android SDK, and thus I have adb up and running and I believe
I won't have problem in rooting the phone (which I must do as first thing). I have found a terminal application. I believe it will be
reasonably easy for me to find myself at home.
The only big gap I still have is on how to proceed about flashing updated/modified roms to the phone. There is a very informative thread
on china-iphone.ru about the specific phone I will get. It is in Russian, but thanks to Babelfish I was able to understand a lot. Most
important, I got hold of the latest official rom for the phone I will receive.
But then, how to proceed with flashing? all tutorials I found describe the windows way of transferring this file's
contents to the phone. Use is made of one of two tools that Mediatek apparently released. This is a no-no for me. I mean: Android is
Linux. I should not have to downgrade to windows to deal with my Linux phone! And then, I simply have no windows whatsoever here.
I see three possible ways for me to proceed:
Find an equivalent software that runs under Linux
Try to run one of Mediatek's softwares under Wine
Obtain from Mediatek, or elsewhere, the precise specs about the USB protocol being used, and implement my tool
Reverse-engineer the protocol
The first item is, I believe, a dead end. I think my search has been exhaustive enough.
The second one is a path I'd rather not tread.
The third one would be a nice project, but I perceive that Mediatek is a bit opaque when it comes to providing technical specifications.
The fourth one would very quickly come to a dead end, I believe, with a bricked device.
Any suggestion on the above, or on other possible ways?
Also: I have come across some very vague mentions about flashing this sort of devices from recovery mode.
From what I have gathered, you put the rom file on a SD card, and then enter recovery mode and let the phone do its own flashing.
This would be ideal for me, but I came across no mention about this mechanism on threads that are specific to this class of phone.
Do MT6577-based phones come with recovery mode? How is it used?
I would be thankful to anyone who could provide details on this aspect.
So far I have only flashed a custom recovery into my MTK6577 phone and I did it with dd.
The full ROM is exposed on /dev/block/mmcblk0.
Once you have rooted your phone you can use dd along with the info in the scater file (from windows tool) or from Memory/eMMC in the EngineerMode (at least in my phone).
Good Luck
P.S.: In my phone the recovery can be booted into from the phone info in Settings.
Or pressing volume up when turning on the phone and releasing volume up once it vibrates (if not it goes to factory mode that has a bunch of tests in it).
Or using adb reboot revovery
FrankVM said:
The full ROM is exposed on /dev/block/mmcblk0.
Once you have rooted your phone you can use dd along with the info in the scater file (from windows tool) or from Memory/eMMC in the EngineerMode (at least in my phone).
Click to expand...
Click to collapse
Thanks a lot.
Indeed, I had found out about using dd plus the info in the scatter file. At first I completed the task of loading a different recovery image, and that was sufficient at the moment. Later on, I spent another weekend on this: I started working on a Ruby script that, by interfacing with the phone via ADB, would dump and upload any partition, and possibly do the reverse, too. The upload part sort-of worked, and I was able to get hold of the current booting partition. What I wanted to do was to modify the boot script to let me run at boot a script resident on one of the sdcards.
I got to the point of unpacking the data in the gzipped/cpio-ed root fs archive, and certainly I would not have had problems modifying the script. But I was blocked when I tried to find the data about the format of ROOTFS. I mean: I could find the start of the compressed material, but I could not find exact reference about those few bytes that preceed it. Must those bytes change if the actual content changes?
I only have one phone, and I certainly do not want to brick it (or have to pour half-days of work into blind-man debugging mode...)
The block is 512 bytes long, filled with 0xff's except for (in my case)
00000000 88 16 88 58 │ 9F 94 08 00 │ 52 4F 4F 54 │ 46 53 00 00 │ 00 00 00 00 . X ..ROOTFS......
00000014 00 00 00 00 │ 00 00 00 00 │ 00 00 00 00 │ 00 00 00 00 │ 00 00 00 00 ....................
and it seems quite clear that the only data that may change are the first 8 bytes - presumably 4 shorts, which in my case would have the values:
5768
22664
38047
8
When I find out what these numbers are, and when I have another free weekend, I may go on in my exploring path.
I looked into modifying boot/recovery images a few weeks back but haven’t gotten around to fiddling with mine.
The initial data is the uboot header, if I remember correctly. It does need to change.
There is a tool out there in perl that does all the required to unpack and repack the boot images for MTK65xx phones.
Here is forum page with the tool info: http://forum.xda-developers.com/showthread.php?t=1587411
my way to do it on ubuntu
well I basically did it on ubuntu, but it was actually virtual box windows under ubuntu so...whatever
This thread is from 2012... 3 years later in 2015 and not a single mtk flash tool was developed for linux... i bet using a windows based phone it will be easyer to find that kinda tool
Now there is a flash tool for Linux available, (look for needrom.com -> sp-flash-tool-v5-1424-00),but I can't get it to work. I suppose there is a vcom driver missing. Unfortunately my phone (UMI Hammer) does not support adb flash, otherwise I would be very happy to do it that way.
I think it took so long that a linux flash tool became available because MediaTek didn't share their code with developers. They changed their policy about a year ago, though.
I wrote a tutorial for setting up the SP_Flash_Tool_Linux
It works
Wait a minute! I'm not writing about Overclock, I simply compiled "Galaxy Star Kernel" from Source...
...for fun...
...with CPU frequency scaling...
Prerequisites:
a 64bit Linux Machine with a working build environment
a local copy of a Jellybean arm cross toolchain
tools to unpack and repack a boot image from a Stock firmware
Kernel source downloaded from Samsung Open Source Release Center
How I did it:
First of all I unzip the kernel source into a linux folder and modify one line from
Code:
CROSS_COMPILE ?= /opt/toolchains/arm-eabi-4.4.3/bin/arm-eabi-
to
Code:
CROSS_COMPILE ?= /home/doc/builds/CYANOGENMOD_10.0__4.1.2_JELLYBEAN/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-
which is the full local path to my cross prebuilt toolchain previously downloaded from Cyanogenmod repositories...
Then I follow the kernel readme to prepare it for my Galaxy Star:
Code:
[email protected]:~/tmp/kernel-gt5280$ [b]make mint-vlx-rev03_defconfig[/b]
...
[email protected]:~/tmp/kernel-gt5280$
And finally I simply issue the master command:
Code:
[email protected]:~/tmp/kernel-gt5280$ [b]make zImage[/b]
...
...
...
LD vmlinux
SYSMAP System.map
SYSMAP .tmp_System.map
OBJCOPY arch/arm/boot/Image
Kernel: arch/arm/boot/Image is ready
AS arch/arm/boot/compressed/head.o
GZIP arch/arm/boot/compressed/piggy.gzip
AS arch/arm/boot/compressed/piggy.gzip.o
CC arch/arm/boot/compressed/misc.o
CC arch/arm/boot/compressed/decompress.o
SHIPPED arch/arm/boot/compressed/lib1funcs.S
AS arch/arm/boot/compressed/lib1funcs.o
LD arch/arm/boot/compressed/vmlinux
OBJCOPY arch/arm/boot/zImage
Kernel: arch/arm/boot/zImage is ready
[email protected]:~/tmp/kernel-gt5280$
Unfortunately, repacking the Compressed Kernel (zImage 3,5Mb) with the ramdisk into an Odin boot.img leads to a "not booting" system stuck at samsung logo...
Repacking instead the Uncompressed Kernel (Image 7,1 Mb) leads to normal boot with the system up and running (victory ):
{
"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"
}
Now looking for frequency scaling:
...searching inside Kernel configuration with the command
Code:
[email protected]:~/tmp/kernel-gt5280$ [b]make menuconfig[/b]
I find this menu:
Code:
.config - Linux/arm 3.0.8 Kernel Configuration
──────────────────────────────────────────────────────────────────────────────
┌───────────────────────── CPU Power Management ──────────────────────────┐
│ Arrow keys navigate the menu. <Enter> selects submenus --->. │
│ Highlighted letters are hotkeys. Pressing <Y> includes, <N> excludes, │
│ <M> modularizes features. Press <Esc><Esc> to exit, <?> for Help, </> │
│ for Search. Legend: [*] built-in [ ] excluded <M> module < > │
│ ┌─────────────────────────────────────────────────────────────────────┐ │
│ │ CPU Frequency scaling ---> │ │
│ │ [color=red][ ] CPUfreq support for Spreadtrum SC8810 CPUs[/color] │ │
│ │ [ ] CPU idle PM support │ │
│ │ │ │
│ └─────────────────────────────────────────────────────────────────────┘ │
├─────────────────────────────────────────────────────────────────────────┤
│ <Select> < Exit > < Help > │
└─────────────────────────────────────────────────────────────────────────┘
where I simply switch on the frequency scaling for the Galaxy CPU:
Code:
.config - Linux/arm 3.0.8 Kernel Configuration
──────────────────────────────────────────────────────────────────────────────
┌───────────────────────── CPU Power Management ──────────────────────────┐
│ Arrow keys navigate the menu. <Enter> selects submenus --->. │
│ Highlighted letters are hotkeys. Pressing <Y> includes, <N> excludes, │
│ <M> modularizes features. Press <Esc><Esc> to exit, <?> for Help, </> │
│ for Search. Legend: [*] built-in [ ] excluded <M> module < > │
│ ┌─────────────────────────────────────────────────────────────────────┐ │
│ │ CPU Frequency scaling ---> │ │
│ │ [color=green][[b]*[/b]] CPUfreq support for Spreadtrum SC8810 CPUs[/color] │ │
│ │ [ ] CPU idle PM support │ │
│ │ │ │
│ └─────────────────────────────────────────────────────────────────────┘ │
├─────────────────────────────────────────────────────────────────────────┤
│ <Select> < Exit > < Help > │
└─────────────────────────────────────────────────────────────────────────┘
After another Odin boot.img...
here we are:
Easy Play
Everything shared starting from here: My Google Drive
WARNING: I started from a GT-S5280XXAMF1 Stock Firmware, knowing exactly wat I was doing...
Beware, use my work as you wish but "at your own risk"!
And now what's Next?
...who knows...
...surely I'm not skilled enough to overclock this Kernel source or add governors...
I just made a "one shot compilation" and I was lucky !
Can u make another one for gt s5282
Sent from my GT-S5282 using Tapatalk
Steps required!
Sure i can!
But, if I can easy handle the Linux side of the job on my PC, I need a step from your phone just before my build action...
...this is true, anyway, only once for a given Kernel Source!
First of All, looking inside Samsung Open Source Release Center I see three Kernel Sources:
I need to choose the right one for the Region of your Phone (or current firmware):
- MEA (Middle East and Africa);
- SEA (South East Asia);
- SWA (South West Asia).
After that, when I prepare the Kernel tree for build (as I briefly described in the first post) with the following command:
Code:
[email protected]:~/tmp/S5282$ [b]make mint-vlx-rev03_defconfig[/b]
...
[email protected]:~/tmp/S5282$
I have to check (once for all) the resulting configuration file with the one extracted from your running kernel!
You must issue one console command from PC with "adb shell" (difficult to setup) or from a Terminal emulator from the Phone (easy to go) installing, for example, the free App "Terminal Emulator" from Palevich (thanks forever ).
The phone, of course, must be rooted and busyboxed;
Here what to type:
Code:
[email protected]:/ $ [b]su[/b]
[email protected]:/ # [b]zcat /proc/config.gz > /data/local/config.txt[/b]
[email protected]:/ #
This command simply creates a text file in the /data/local folder with listed all the configuration options!
I need it to check for differences, just to modify the build tree accordingly.
Ah... of course I need a boot.img file to mod and, maybe, the right PDA code for it... just to prepare an Odin archive with the right naming convention...
After All I'll build the Kernel and prepare two images in my google drive:
- the original boot.img ready for Odin,
- the cpufreq modded boot.img ready for Odin.
What else?
You have to test it!
If it doesn't boot, simply flash back the original image in place.
That's All!
No need to wipe anything before, during and after...
Doc_cheilvenerdi.org said:
Sure i can!
But, if I can easy handle the Linux side of the job on my PC, I need a step from your phone just before my build action...
...this is true, anyway, only once for a given Kernel Source!
First of All, looking inside Samsung Open Source Release Center I see three Kernel Sources:
I need to choose the right one for the Region of your Phone (or current firmware):
- MEA (Middle East and Africa);
- SEA (South East Asia);
- SWA (South West Asia).
After that, when I prepare the Kernel tree for build (as I briefly described in the first post) with the following command:
Code:
[email protected]:~/tmp/S5282$ [b]make mint-vlx-rev03_defconfig[/b]
...
[email protected]:~/tmp/S5282$
I have to check (once for all) the resulting configuration file with the one extracted from your running kernel!
You must issue one console command from PC with "adb shell" (difficult to setup) or from a Terminal emulator from the Phone (easy to go) installing, for example, the free App "Terminal Emulator" from Palevich (thanks forever ).
The phone, of course, must be rooted and busyboxed;
Here what to type:
Code:
[email protected]:/ $ [b]su[/b]
[email protected]:/ # [b]zcat /proc/config.gz > /data/local/config.txt[/b]
[email protected]:/ #
This command simply creates a text file in the /data/local folder with listed all the configuration options!
I need it to check for differences, just to modify the build tree accordingly.
Ah... of course I need a boot.img file to mod and, maybe, the right PDA code for it... just to prepare an Odin archive with the right naming convention...
After All I'll build the Kernel and prepare two images in my google drive:
- the original boot.img ready for Odin,
- the cpufreq modded boot.img ready for Odin.
What else?
You have to test it!
If it doesn't boot, simply flash back the original image in place.
That's All!
No need to wipe anything before, during and after...
Click to expand...
Click to collapse
ok no problem.. plz tell if u can make cwm 6.4.4 for galaxy star bcoz we need ot for our CM 11 project
---------- Post added at 01:29 PM ---------- Previous post was at 01:27 PM ----------
rahulsinghal said:
ok no problem.. plz tell if u can make cwm 6.4.4 for galaxy star bcoz we need ot for our CM 11 project
Click to expand...
Click to collapse
bcoz our current focus is on cm and cwm 6.4.4
Doc_cheilvenerdi.org said:
Sure i can!
But, if I can easy handle the Linux side of the job on my PC, I need a step from your phone just before my build action...
...this is true, anyway, only once for a given Kernel Source!
First of All, looking inside Samsung Open Source Release Center I see three Kernel Sources:
I need to choose the right one for the Region of your Phone (or current firmware):
- MEA (Middle East and Africa);
- SEA (South East Asia);
- SWA (South West Asia).
After that, when I prepare the Kernel tree for build (as I briefly described in the first post) with the following command:
Code:
[email protected]:~/tmp/S5282$ [b]make mint-vlx-rev03_defconfig[/b]
...
[email protected]:~/tmp/S5282$
I have to check (once for all) the resulting configuration file with the one extracted from your running kernel!
You must issue one console command from PC with "adb shell" (difficult to setup) or from a Terminal emulator from the Phone (easy to go) installing, for example, the free App "Terminal Emulator" from Palevich (thanks forever ).
The phone, of course, must be rooted and busyboxed;
Here what to type:
Code:
[email protected]:/ $ [b]su[/b]
[email protected]:/ # [b]zcat /proc/config.gz > /data/local/config.txt[/b]
[email protected]:/ #
This command simply creates a text file in the /data/local folder with listed all the configuration options!
I need it to check for differences, just to modify the build tree accordingly.
Ah... of course I need a boot.img file to mod and, maybe, the right PDA code for it... just to prepare an Odin archive with the right naming convention...
After All I'll build the Kernel and prepare two images in my google drive:
- the original boot.img ready for Odin,
- the cpufreq modded boot.img ready for Odin.
What else?
You have to test it!
If it doesn't boot, simply flash back the original image in place.
That's All!
No need to wipe anything before, during and after...
Click to expand...
Click to collapse
Bro i will provide that file to you soon bcoz currently I am owning this phone. Plz qait 2-3 dys
what block partition that can use to flash kernel with cwm ?
Hello Everyone,
A lot of you may not be familiar with IUNI U3, a not famous Chinese android phone brand?
My question is How to enlarge system partition of my IUNI U3?
Information that i have collected about and endeavor on my device is as follows:
Following [HOWTO][GUIDE][Mi3][Mi4]Resize/extend system partition capacity, I have checked the partition on my IUNI U3.
the initial partition design is
{
"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"
}
After a series of remove, new, name and convert handling from no. 20 up to no. 12, the final design is as follows
As I guess, I erased some important file in partitions like fsg, fsc, ssd and splash which are not contained in SD card flash package.
-------Explanation Start------
Sorry, i do not know the exact name for SD card flash package and line flash package.
Simple illustration is as follows.
1. SD card flash package is the zip file that we put into SD card (or Internal Storage, treated as SD card ) and then use recovery install zip from SD card to re-install android system, during which partition design will not be modified.
The tree of SD card flash package are
tree
IUNI-U3-BetaV3.0.04-201503300001
├─firmware-update
├─META-INF
│ └─com
│ ├─android
│ └─google
│ └─android
├─recovery
│ └─etc
└─system
├─app
├─bin
├─etc
│ ├─acdbdata
│ │ ├─Fluid
│ │ ├─Liquid
│ │ └─MTP
│ ├─bluetooth
│ ├─cne
│ ├─dhcpcd
│ │ └─dhcpcd-hooks
│ ├─firmware
│ │ ├─ar3k
│ │ │ └─1020201
│ │ ├─ath6k
│ │ │ └─AR6004
│ │ │ ├─hw1.2
│ │ │ ├─hw1.3
│ │ │ └─hw3.0
│ │ └─wlan
│ │ └─prima
│ ├─gn_camera_feature
│ │ ├─arcsoft
│ │ │ └─maskfile
│ │ ├─res
│ │ │ └─picture_frame
│ │ └─scalado
│ │ └─warp
│ ├─hostapd
│ ├─logmask
│ ├─permissions
│ ├─ppp
│ ├─security
│ │ └─cacerts
│ ├─srs
│ ├─surround_sound
│ └─wifi
├─fonts
├─framework
│ └─webview
│ └─paks
├─iuni
│ └─aurora
│ ├─change
│ │ ├─desktop
│ │ └─lockscreen
│ │ ├─City
│ │ ├─Color
│ │ ├─Dream
│ │ ├─Green
│ │ └─Timely
│ ├─gallery
│ │ └─maskfile
│ └─launcher
│ └─config
├─lib
│ ├─crda
│ ├─drm
│ ├─egl
│ ├─hw
│ ├─modules
│ │ ├─ath6kl-3.5
│ │ └─pronto
│ ├─soundfx
│ └─ssl
│ └─engines
├─media
│ └─audio
│ ├─alarms
│ ├─notifications
│ ├─ringtones
│ └─ui
├─priv-app
├─sdcard
│ ├─DCIM
│ ├─lyric
│ └─music
├─tts
│ └─lang_pico
├─usr
│ ├─icu
│ ├─idc
│ ├─keychars
│ ├─keylayout
│ └─share
│ ├─bmd
│ └─zoneinfo
├─vendor
│ ├─etc
│ └─lib
│ ├─drm
│ ├─egl
│ ├─hw
│ ├─rfsa
│ │ └─adsp
│ └─soundfx
└─xbin
Click to expand...
Click to collapse
2. Line flash package is the set of files (usually in zip files, namely under a root directory) that we use special computer software to re-install android phone system when our phone is connected to computer via USB cable.
The tree of Line flash package(which contains many .img files) is
tree /F
NBL8910A01_A_platform_T0401
│ boot.img
│ cache.img
│ cache_1.img
│ cache_2.img
│ cache_3.img
│ cache_4.img
│ emmc_appsboot.mbn
│ Gionee_info.ini
│ NBL8910A01_A_platform.log-2015-02-05-01-41-40
│ NBL8910A01_A_platform.qcn
│ persist.img
│ persist_1.img
│ ramdisk-recovery.img
│ ramdisk.img
│ rawprogram_unsparse.xml
│ rawprogram_unsparse_for_factory.xml
│ recovery.img
│ system.img
│ system_1.img
│ system_2.img
│ ...
│ tree_nbl.txt
│ userdata.img
│ userdata_1.img
│ ...
│ vmlinux
│
└─bp_image
8974_msimage.mbn
adsp.b00
...
adsp.mdt
checksparse.py
cmnlib.b00
...
cmnlib.mbn
cmnlib.mdt
contents.xml
createAllZeroFile.py
dd.py
dsp2.mbn
dummy_bin.bin
fs_image.tar.gz.mbn.img
gpt_backup0.bin
gpt_both0.bin
gpt_main0.bin
hwio.cmm
isdbtmm.b00
...
isdbtmm.mbn
isdbtmm.mdt
keymaster.b00
...
keymaster.mdt
load_coredump.cmm
lsusb.py
mba.b00
mba.mbn
mba.mdt
mc_v2.b00
...
mc_v2.mbn
mc_v2.mdt
mjsdload.cmm
modem.b00
...
modem.mdt
MPRG8974.mbn
msg_hash.txt
msp.py
NBL8910A_Release_Note.txt
NON-HLOS.bin
NPADump.cmm
partition.xml
patch0.xml
playready.b00
...
playready.mbn
playready.mdt
prog_emmc_firehose_8974.mbn
ptool.py
qdsp6sw.mbn
rawprogram0.xml
recover_f3.cmm
rpm.mbn
rpm_log_bfam.py
rpm_npadump.cmm
rpm_ulogdump.cmm
sampleapp.mbn
sbl1.mbn
sdi.mbn
singleimage.py
singleimage_partition_8064.xml
singleimage_partition_8930.xml
singleimage_partition_8960.xml
singleimage_partition_8974.xml
splash.img
testsparse.py
tqs.b00
...
tqs.mdt
tz.mbn
tzbsp_no_xpu.mbn
ULogDump.cmm
wcnss.b00
...
wcnss.mbn
wcnss.mdt
widevine.b00
...
widevine.mbn
widevine.mdt
Click to expand...
Click to collapse
-------Explanation End------
So the good news now is, I can redesign IUNI U3 partition design via adb shell. the problem is i destroyed my original system and when i re-install the system using SD card flash package. The WiFi cannot work!!! And when i re-install the system using Line flash package, the partition design will be come back to initial design.
So now, I want to know how to modify Line flash package so that I can have a larger system partition initialized during my re-install process?
Hope to get help from you.
Johann,
GMT +8, 13:26 2015/4/25
Any Android Geek Here?
happyjohann said:
Click to expand...
Click to collapse
I will get a iuni u3 maybe next week then I will try to resize my system partition but in the other way I will srink it a little, maybe 500MB is enougth.
In otherside is possible to make for example a 4GB usrdata partition and the the left space for special "sdcard" vfat partition?, because I would like to mount it as massive storage for my car mp3 , because the stock mtp is not recognised.
Hey! I just got a solution, well is a workarround.
As you want to increase system partition moving others partitions the solution is "quite" easy.
First of all install your firmware from flash tool.
Then copy all the intermediate partitions to a file, using the dd command to a partition with space then copy to your computer with adb pull:
dd if=/dev/block/mmcblk0p19 of=/cache/p19tmp.part
This will copy as binary whole the partition, problem is that you can't resize it as is a unknown filesystem. but you will be able to repartitioning the others files and move the intermediate partitions to get the necessary free space.
I found a limitation about number or partition you can't partition more than 20 partitions, WTF!! is gpt it has more than 64 primary partitions on a limited kernels, and more than 128 on "uncapped kernels".
So In my case I'm trying to make a userdata of type ext4 of about 2GB and the left space to vfat simulated sdcard that I will be able to mount as massive storage.
I'm considering delete the cache partition and map as /system/cache folder but I don't have any tool to unpack the kernel image. (maybe mtk boot tools?)
Can you tell me all the available tools for this and the msm87xx platform to manipulate the kernel and other things?
Thank you!
Hi Team,
Recently I was asking you for help (successfully) regardingmissing adb in my android photo-frame
(https://forum.xda-developers.com/t/goclever-zoom-me-adb-connection.4210165/)
But I still didn't manage to edit build.prop file with success... I mean - I can edit it but it reverts to previous state after reboot.
I actually want to add only one line:
qemu.hw.mainkeys=0
I managed to unpack img with software
(http://downloadfiles.goclever.com/Tablet/Zoom_me/ZM7WIFI_20150717.img)
And in the simplest situation I get below filelist:
aultls32.fex
aultools.fex
BasePath.txt
boot.fex
boot0_nand.fex
boot0_sdcard.fex
bootloader.fex
cardscript.fex
cardtool.fex
config.fex
diskfs.fex
dlinfo.fex
env.fex
fes1.fex
image.cfg
recovery.fex
split_xxxx.fex
sunxi_mbr.fex
system.fex
sys_config.fex
sys_partition.fex
u-boot.fex
usbtool.fex
Vboot.fex
Vbootloader.fex
Venv.fex
Vrecovery.fex
Vsystem.fex
Following a lot of guides I managed to get some additional files, and folders, among others: system.fex.iso.
But when I try to edit and save this iso I get some read/write errors related to filenames...
I can also use some switches and unpack img with below additionally:
├───boot.fex.dump
│ └───ramdisk.dump
│ ├───data
│ ├───dev
│ ├───proc
│ ├───res
│ │ └───images
│ │ └───charger
│ ├───sbin
│ ├───sys
│ └───system
├───recovery.fex.dump
│ └───ramdisk.dump
│ ├───data
│ ├───dev
│ ├───etc
│ ├───proc
│ ├───res
│ │ └───images
│ │ └───charger
│ ├───sbin
│ ├───sys
│ ├───system
│ └───tmp
└───_iso
But I don't know how it can help...
All in all I'm unable to edit it fex/img/iso file to be able to save it back...
I tried that in Windows and Ubuntu.
Can you help me anyhow?
It's a jellybean - it should not be that hard.
Did you chmod it 644?
Try putting it to /data/local.prop
That's what I also expected, but it actually doesn't work as described in many manuals... I face a lot of problems with accessing the data in img, and it actually seems like non-compatible with available tools.
What do you mean by putting it to /data/local.propp? There is no /data directory in root of extracted rom. Can you please provide more precise directions?
Not extracted one but live using adb for example...
adb shell
su
echo qemu.hw.mainkeys=0 >> /data/local.prop
chmod 644 /data/local.prop
Geez... how could I miss this way...
Thanks it worked - however it behaves strange, because main app overrides the settings and once started - bar disappeared. Navigation Bar 3rd party application turned out to be a solution.
Let me ask one more question - during one of reflashes, due to problems with rom upload I selected "Format upgrade mode" instead of recommended "Normal upgrade mode".
After that I lost an unique device number (it got renewed to another one). It's not a big issue, however I wonder where should I look for to rewrite it back (I have the number written down) if possible?
EDIT:
I mean if you know what areas are formatted that I can scan for missing/changed number?
Unique device number meaning what?
Device ID Changer [ADIC] - Apps on Google Play
Change device ID or ANDROID ID and restore to original, view device and sim info
play.google.com
It's kind of decimal 7 digits ID used internally by ZoomMe application (default launcher).
The app you recommended recognizes different number, so it's not the one I look for.
I checked the files of this launcher, but no luck so far. Previously when I reflashed device without formatting it, this number was persistent.
well, pull all partitions (under /dev/block/) and do search for the new string. Try utf-8 or what ever also... maybe you can hexedit it and push it back.
OK, will try that. Thank you for your support.
I've found in nandk (UDISK) that the number which is currently used as new mentioned device ID is stored as IMEI (tablet does not have GSM modem): IMEI=(8 initial digits)(7 digits of Device ID).I can edit it in HxD, but I can't push it back to device, because it reports lack of free space...
Any ideas?
Maybe some other idea to change IMEI? I tried already AT command and Xposed IMEI Changer, but no real luck.
Well, on that nandk can have some file that you can edit. What sort is it. It's just zeros in firmware file. Maybe you can just cut it after that value and push or dd it back. A dirty hack but might work. IDK.
edit:
Or is this a rights problem? If you pulled from it, it must fit into it.
Or so one could assume...
I couldn't make it working anyhow... and gave up. But thanks for your engagement.
Hey guys,
I am pretty new to this, let me explain my problem.
Few days ago I got the Xiaomi DuoQin F22 pro but did not have the google services and playstore (I have the chinese version with chinese apps). I wanted to install a rom version with playstore and where I can use google services. I followed this thread to try to install a version with playstore : https://forum.xda-developers.com/t/...th-google-play-with-and-without-root.4509111/
Considering this is a first time for me i did not put the oem unlock on "ON" and tried anyways to put a rom using the flashtool. It started but I got a message that says that my phone is locked and it can't flash with the new ROM. But when i restarted my phone to set oem unlock on "ON" i got this message popping up and i can't get in the phone.
"red state
your device has failed verification may not work properly
please download boot image with correct signature or disable verfied boot."
After this it waits 5sec and restart the phone and i get this message again and it keeps looping.
I cant disable verified boot.
this is what i tried :
with adb => I tried "fastboot flashing unlock" and I get this message "unlock operation is not allowed"
I am stucked I don't find a lot of resources for this phone on the internet.
Thanks in advance,
tsoundi
you can unlock bootloader or flash partitions with mtkclient.
tsoundi said:
Hey guys,
I am pretty new to this, let me explain my problem.
Few days ago I got the Xiaomi DuoQin F22 pro but did not have the google services and playstore (I have the chinese version with chinese apps). I wanted to install a rom version with playstore and where I can use google services. I followed this thread to try to install a version with playstore : https://forum.xda-developers.com/t/...th-google-play-with-and-without-root.4509111/
Considering this is a first time for me i did not put the oem unlock on "ON" and tried anyways to put a rom using the flashtool. It started but I got a message that says that my phone is locked and it can't flash with the new ROM. But when i restarted my phone to set oem unlock on "ON" i got this message popping up and i can't get in the phone.
"red state
your device has failed verification may not work properly
please download boot image with correct signature or disable verfied boot."
After this it waits 5sec and restart the phone and i get this message again and it keeps looping.
I cant disable verified boot.
this is what i tried :
with adb => I tried "fastboot flashing unlock" and I get this message "unlock operation is not allowed"
I am stucked I don't find a lot of resources for this phone on the internet.
Thanks in advance,
tsoundi
Click to expand...
Click to collapse
The same happened to me. have you got any solution?
todaysdeallist said:
The same happened to me. have you got any solution?
Click to expand...
Click to collapse
Hey man sorry I answer months later was busy with things and did not find any solutions. Did you find something ?
Isn't that similar to F21 so just use mtkclient??
[TOOLS][MOD][SCRIPTS] MlgmXyysd's Qin F21 Pro Unlock Tool
Welcome to MlgmXyysd's Qin F21 Pro Unlock Tool Powered by MTK Client @ Bjoern Kerler. A tool to crack Qin F21 Pro BootLoader without erasing userdata. Screenshots Usage View README in the ZIP ! Remember to keep the backup properly, they are...
forum.xda-developers.com
alecxs said:
Isn't that similar to F21 so just use mtkclient??
[TOOLS][MOD][SCRIPTS] MlgmXyysd's Qin F21 Pro Unlock Tool
Welcome to MlgmXyysd's Qin F21 Pro Unlock Tool Powered by MTK Client @ Bjoern Kerler. A tool to crack Qin F21 Pro BootLoader without erasing userdata. Screenshots Usage View README in the ZIP ! Remember to keep the backup properly, they are...
forum.xda-developers.com
Click to expand...
Click to collapse
the thing is I have to press buttons on the phone when on the mtkclient but it does not seems to work...
edit: also the phone keeps rebooting constantly so don't have much time to perfomr manipulations
from readme.txt
Code:
------------------------------
About top-left and top-right key
------------------------------
╭───────────────╮
│ ┌───────────┐ │
│ │ │ │
│ │ │ │
│ │ │ │
│ │ duo qin │ │
│ │ │ │
│ │ │ │
│ │ │ │
│ └───────────┘ │
│ Qin AI Life │
│ ■■■ ○○○ ■■■ │ <- Boot ROM keys
│ □□□ ○○○ □□□ │
│ 1 2 3 │
│ 4 5 6 │
│ 7 8 9 │
│ * 0 # ● │
╰───────────────╯
------------------------------