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 # ● │
╰───────────────╯
------------------------------
Related
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
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.
I'm looking to pinout both test pins. I bought this phone a few days ago. I unlocked it with TWRP, I looked at the possibilities. I made a mistake with TWRP by switching the system to sideload B (I chose between A and B) and the system refused to start. I do not have access to the bootloader with the buttons. I only enter QDLoader HS-USB Driver mode working. I read the instructions on how to make a blank flash. I took the 18 files out of the phone and made a new blank flash for this model - moto g9 power / but in the end it gives me an error. Now I'm looking for a solution. - "C: \ Documents and Settings \ Administrator \ Desktop \ MOTO G9 POWER blankflash \ Blankflash for G9 POWER>. \ Qboot.exe blank-flash Motorola qboot utility version 3.86 [0.000] Opening device: \\. \ COM4 [0.000] Detecting device [0.000] ... cpu.id = 333 (0x14d) [0.000] ... cpu.sn = 2936128399 (0xaf01c38f) [0.000] Opening singleimage [0.000] Loading package [0.000] ... filename = pkg.xml [0.000] Loading programmer [0.000] ... filename = programmer.elf [0.000] Sending programmer [0.156] Handling things over to programmer [0.156] Identifying CPU version [0.156] Waiting for firehose to get ready [3.297] ... SM_KAMORTA_H 1.0 [3.297] Determining target secure state [3.297] ... secure = yes [3.375] Configuring device ... [3.391] Flashing GPT ... [3.391] Flashing partition with gpt.bin [3.406] Initializing storage [3,484] ... blksz = 512 [37.016] Re-initializing storage ... [37.016] Initializing storage [37328] Flashing bootloader ... [37.344] Flashing abl_a with abl.elf [37.344] partition abl_a not found! [37.359] ERROR: do_package () -> do_recipe () -> do_flash () -> pt_find () -> not found [37.375] Check qboot_log.txt for more details [37.375] Total time: 37.375s FAILED: qb_flash_singleimage () -> do_package () -> do_recipe () -> do_flash () -> pt_find () -> not found "the last message puzzles me. I want to transfer the system to sideload A again, so I have to reset the device firmly. Are there people familiar with the possibilities?
2 I built a blankflash for the Moto G8
1 How To Blank Flash & Fix/Repair Hard Bricked Motorola Devices/Moto G8+|Tutorial Get It Working Again - YouTube
Version Bootloader MBM-3.O-cebu retail 232f3ba894-201209
motostockrom.com/motorola-moto-g9-power-xt2091-3
I'm looking to pinout both test pins.
Have you tried using LMSA?
It recovered a dead phone for me once.
Rescue and Smart Assistant (LMSA)
Also, I too once accidentally switched slot to B, and system didn't boot. However, I was able to get into fastboot mode and switch by entering the command to switch slots.
https://support.lenovo.com/bg/en/downloads/ds101291 i saw this but my computer is 32 bit / i am looking for the program qualcomm edl mode flash tool or something like Axon10Pro_ (More) _EDL_Tools_v1.1d because i want to make active a siteloader because i saw that this can be done not so difficult otherwise for edl pinout I saw how it works and no problem
man88nam said:
https://support.lenovo.com/bg/en/downloads/ds101291 i saw this but my computer is 32 bit / i am looking for the program qualcomm edl mode flash tool or something like Axon10Pro_ (More) _EDL_Tools_v1.1d because i want to make active a siteloader because i saw that this can be done not so difficult otherwise for edl pinout I saw how it works and no problem
Click to expand...
Click to collapse
qualcomm edl mode flash tool / Axon10Pro_ (More) _EDL_Tools_v1.1d
In those .XML files, can you delete the line that says "abl" and try again?
I will do, but these files can be downloaded according to the instructions on how to make closed files extracted from the phone itself
https://www.reddit.com/r/MotoG/comments/k73n66
I downloaded from the bootloader 18 files that are original, this is in connection with blank flash, where in the end there is an error, because eight made active "B" sector instead of A
I removed the ABL file from the XML, but the error remains, plus the message for a missing ABL file ELF
[ 37.297] file abl.elf not found in singleimage.bin!
[ 37.297] ERROR: do_package()->do_recipe()->do_flash()->not found
[ 37.297] Check qboot_log.txt for more details
[ 37.297] Total time: 37.297s
I'm just looking for an EDL program that works similar to this command line Set Bootable Partition- Slot A / run_AB-partition-swap - but here it wants some text file for the presence of a port, port_trace.txt
I'm sorry, I can't help further here. Even though the active slot is B, the partition abl_a should exist and should be flashable regardless. It looks as though there isn't such a partition at all, which I don't even know how that happened.
The tool which you are using is correct, it's doing its job properly. Are you sure you have the right firmware version and software channel? Because bootloader.img differ depending on the firmware version and the carrier. I'd also suggest downloading from https://mirrors.lolinet.com/firmware/moto/cebu/official/, instead of the link you mentioned, motostockroms.
Also, try asking in this Telegram group: https://t.me/lolinet. There are people on there who are more knowledgeable, maybe they can help.
After trying the firmware image from lolinet and trying the process again with that firmware, I'd try to get into bootloader mode once again through power buttons, and if that doesn't work, send the phone into the service center.
Motorola_Moto_G9_Power_XT2091-3_RETUK_CEBU_RETAIL_QZC30.Q4-22-57_10_by_(motostockrom.com) With the TWRP program I chose with active slot B / I don't know if it deleted the content from slot A of the bootloader. By the way, I downloaded the original product firmware XT2091-3 according to the instructions for this, which I get when I try blank flash / I have no idea what to do, so I'm looking for a program "qualcomm edl mode flash tool" and I constantly get Indian sites with dangerous behavior.
I thank you for your time
Hey,
Today I found EDL points for Moto G9 power. Infact im also facing firmware issue.
I accidentally locked bootloader with stockrom again trying to unlock but not working.
Causing No valid OS to boot.
if i try unlock again showing message like " enable OEM unlocking in developer options"
unfortunately not podsible. But still waiting for proper EDL flash tool.
feel free to guide if any one got resolution.