Related
EDIT :Successfully rooted my phone via changing the microSD card, did the downgrading process, Goldcarding and rooting process from scratch and it worked!
Hi , i have just created an account after failed rooting on countless tries , i tried all the methods the forum gave me ... so i just opted to create an account to post about this problem im having ...
ok , i downgraded successfully , running ROM ver 1.31.405.5 , my HBOOT is 0.43.00001 , MICROP-0816 ,RADIO-7.05.35.26L, LEGEND UNKNOWN SHIP S-ON so i should be fine to start rooting right?
i followed MaDaCo's Steps and failed numerous times at step 2 , the green recovery window wont show itself! then i found other guides where it says do not remove the goldcard after step 1 as shown here
youtube.com/watch?v=SQzo6qahctk
this is my step 1 proceedure in the CMD :
Legend Root Step 1
Erasing cache and rebooting in RUU mode...
erasing 'cache'... OKAY
... OKAY
About to start flash...
sending 'zip' (121756 KB)... FAILED (command write failed (Too many links))
< waiting for device >
sending 'zip' (121756 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOstart image[hboot] unzipping for pre-update check...
INFOstart image[hboot] unzipping & flushing...
INFO[RUU]UZ,hboot,0
INFO[RUU]UZ,hboot,100
INFO[RUU]WP,hboot,0
....
then it continues to all the way ...
INFO[RUU]WP,system,100
INFOstart image[userdata] unzipping & flushing...
INFO[RUU]UZ,userdata,0
INFO[RUU]UZ,userdata,100
INFO[RUU]WP,userdata,0
INFO[RUU]WP,userdata,100
INFOstart image[sp1] unzipping & flushing...
INFO[RUU]UZ,sp1,0
INFO[RUU]UZ,sp1,100
INFO[RUU]WP,sp1,0
INFO[RUU]WP,sp1,100
OKAY
Rebooting to bootloader...
rebooting into bootloader... OKAY
Step 1 complete - now use the bootloader menu to enter recovery mode.
To do this, press the power button, wait a few seconds, then use the volume keys
and power button to select the RECOVERY option.
so i followed the Unlockers way now ... not removing the goldcard and going straight into Recovery mode ( the triangle with the ! sign ) and started Step 2 in CMD :
C:\r4-legend-root>C:\r4-legend-root\step2-windows.bat
Legend Root Step 2
Pushing required files to device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
push: files/etc/mtab -> /etc/mtab
push: files/etc/fstab -> /etc/fstab
push: files/sbin/wipe -> /sbin/wipe
push: files/sbin/unyaffs -> /sbin/unyaffs
push: files/sbin/ums_toggle -> /sbin/ums_toggle
push: files/sbin/um -> /sbin/um
push: files/sbin/tune2fs -> /sbin/tune2fs
push: files/sbin/toolbox -> /sbin/toolbox
push: files/sbin/sdparted -> /sbin/sdparted
push: files/sbin/recovery -> /sbin/recovery
push: files/sbin/reboot -> /sbin/reboot
push: files/sbin/parted -> /sbin/parted
push: files/sbin/nandroid-mobile.sh -> /sbin/nandroid-mobile.sh
push: files/sbin/mkyaffs2image -> /sbin/mkyaffs2image
push: files/sbin/mke2fs -> /sbin/mke2fs
push: files/sbin/log2sd -> /sbin/log2sd
push: files/sbin/fs -> /sbin/fs
push: files/sbin/flash_image -> /sbin/flash_image
push: files/sbin/fix_permissions -> /sbin/fix_permissions
push: files/sbin/e2fsck -> /sbin/e2fsck
push: files/sbin/dump_image -> /sbin/dump_image
push: files/sbin/busybox -> /sbin/busybox
push: files/sbin/backuptool.sh -> /sbin/backuptool.sh
push: files/sbin/adbd -> /sbin/adbd
push: files/system/bin/sh -> /system/bin/sh
push: files/system/bin/linker -> /system/bin/linker
push: files/system/lib/libstdc++.so -> /system/lib/libstdc++.so
push: files/system/lib/libm.so -> /system/lib/libm.so
push: files/system/lib/liblog.so -> /system/lib/liblog.so
push: files/system/lib/libcutils.so -> /system/lib/libcutils.so
push: files/system/lib/libc.so -> /system/lib/libc.so
31 files pushed. 0 files skipped.
1577 KB/s (3734509 bytes in 2.312s)
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
Pushing update file to device sdcard - this may take a few minutes...
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
Now wipe and apply rootedupdate.zip from the recovery image menu.
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
and then im STILL at the bloody triangle box with no green recovery window anywhere in sight.
EDIT: about the ADB Server didn't ACK , i tried numerous times after rebooting and spammed step 2 bat file , i would get this :
push: files/system/lib/libm.so -> /system/lib/libm.so
push: files/system/lib/liblog.so -> /system/lib/liblog.so
push: files/system/lib/libcutils.so -> /system/lib/libcutils.so
push: files/system/lib/libc.so -> /system/lib/libc.so
31 files pushed. 0 files skipped.
1577 KB/s (3734509 bytes in 2.286s)
adb server is out of date. killing...
*daemon started successfully*
Pushing update file to device sdcard - this may take a few minutes...
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
Now wipe and apply rootedupdate.zip from the recovery image menu.
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
Everything else is the same , whether ADB Server didn't ACK or not
While in Recovery Mode , i pressed volume up + power i would get a small blue recovery window , at the bottom it says "E:Can't open/cache/recovery/command"
it will be there no matter what, even before doing step 1 or 2 , i went to recovery mode afew times to check what is wrong and would always see THAT message ...
so can anyone point out what is wrong ? Q.Q
THANK YOU SO MUCH IF YOU HELPED ME !! , im currently stuck on ROM 1.31 , i cant upgrade to later versions of rom for some reason. so its me rooting this legend or nothing
Edit again : about this error :
sending 'zip' (121756 KB)... FAILED (command write failed (Too many links))
i re-downgraded , tried the rooting process again , and this error did not show up, the process itself was identical to what i posted above. Main problem lies in step 2 where the green recovery windows dont pop up ... i suspect that after "pushing" the 31 files , there needs to be more "pushing" of files to SD card but failed to do so? :/
have exactly the same problem like you.dont know what to do.
its been a full 20hours i posted this , still no help ;(?
Looks like the connecting is gone to your phone, try DroidExplorer
http://de.codeplex.com/
It will install also the drivers for Windows what is needed to connect to your phone. The phone is changed for Legend Htc to normal Droid, so Windows is also needed other drivers.
This is not executed yet:
adb-windows.exe shell busybox --install /sbin
echo.
echo Pushing update file to device sdcard - this may take a few minutes...
echo.
adb-windows.exe shell mount /sdcard
adb-windows.exe push rootedupdate.zip /sdcard
echo.
echo Now wipe and apply rootedupdate.zip from the recovery image menu.
echo.
adb-windows.exe shell nohup /sbin/recovery &
nope, doesnt work for me , can connect to my device but cant do anything else , cant copy over root files / music , whatever ;/
what os do you have?
i have win 7 64 bit. could this be the problem?
Edit :
have a question...
can i just install this version here without a root? so that im back to normal? I know that i cant get the root after this.
[ROM]RUU_Legend_Vodafone_AU_2.10.178.1_Radio_47.39.35.0 9_7.08.35.21
im using windows 7 X64 also ...
about that rom , i dont know. im very new to android , why does other people root to easily and we rot with problems T^T
i think read on other threads that it is a 30 % chance that it wont work with win 7 64 bit. maybe we have to try for example on xp Mode.
i wanted to try azure but i think now that im also happy if i can get it back to normal
Same here. Sometimes another error! I'm using windows 7 x86
Quick update ;
I successfully rooted my phone by changing SDcards , i did the downgrading , goldcarding and rooting process from scratch !
make sure you do the goldcard again as the same image wont work for the changed gold-card.
and a tip : if you see errors in step 1 ( 2 sending errors ) , be persistant and keep trying! for me i kept getting an error but after 5~6 tries of constantly starting step1 , it worked!
for step 2 , make sure u can push the 31 files and it should give you a message "pushing files to SDcard , it may take afew minutes" it should take about 30~50seconds ( or more ;/ ) it should not be instantanous! with things like could not connect to daemon or whatnot .
Congratz
I'm trying with another sdcard right now...
When pushing the files in step 2 i now have a new error.
after a few files it says, protocol failure
it gives me the error on windows 7 x86 and windows xp x86
any idea?
i also had that error , again , try to be persistant! keep launching it until you get the results wanted , u may want to try rebooting ur phone if it doesnt work after 10~15 tries
One of my standard threads with codes and info. I will add onto this as I find more.
Dialer Codes
Code:
##25327# - nothing?
##2539# - nothing?
##3282# - DATA
##33284# - DEBUG (Password: 777468 / SPRINT)
##3424# - DIAG
##367738# - DNSSET
##4772579# - GPSCLRX
##72786# - SCRTN
##786# - RTN
##889# - TTY
*#0011# - Service Mode
*#7284#
**7838 - nothing?
**583 - nothing?
Stole some codes from [B][URL="http://forum.xda-developers.com/member.php?u=2698939"]thekingofmean[/URL][/B]'s thread [URL="http://forum.xda-developers.com/showthread.php?t=2261538"]here[/URL]. Thank you!
*#0*# General Test Mode
*#0228# Battery status
*#06# IMEI
*#1234# Check HW/SW Info, PDA, CSC, MODEM (F/W Ver)
*#12580*369# SW & HW Info
*#2663# TSP / TSK firmware update
*#34971539# Camera Firmware Update
*#7353# Quick Test Menu
*#9900# Sys Dump Menu
*#9090# Diag Config
AT Commands
See here for AT command info from E:V:A
Code:
AT+SYSSLEEP
AT+VERSNAME
AT+MAXPOWER
AT+TEMPTEST
AT+SIMDETEC
AT+PRODCODE
AT+CALIDATE
AT+BANSELCT
AT+SECNRSSI
AT+READRSSI
AT+CALLCONN
AT+SCMMONIT
AT+TESTMODE
AT+GPSSTEST
AT+MSLSECUR
AT+IMEITEST
AT+AKSEEDNO
AT+LIFETIME
AT+IMEICERT
AT+LVOFLOCK
AT+DETALOCK
AT+LOCKREAD
AT+CFUN
AT+MEIDAUTH
AT+CHNSELCT
AT+AOTKEYWR
AT+FACTORST
AT+BAKUPCHK
AT+FAILDUMP
AT+NAMCHECK
AT+PRLVERIF
AT+RECONDIT
AT+KSTRINGB
AT+SVCBANDB
AT+LOCKINFO
AT+EFSSYNCC
AT+$QCSIMSTAT
AT+$QCPBMPREF
AT+$CREG
AT+$CCLK
AT+$QCCNMI
AT+*CNTI
AT+$QCCLR
AT+$QCDMR
AT+$QCDNSP
AT+$QCDNSS
AT+$QCTER
AT+$QCSLOT
AT+$QCSIMAPP
AT+$QCPINSTAT
AT+$QCPDPP
AT+$QCPDPLT
AT+$QCPWRDN
AT+$QCDGEN
AT+$QCPDPCFGE
AT+$BREW
AT+$QCANTE
AT+$QCRPW
AT+$QCSQ
AT+$CSQ
AT+$QCSYSMODE
AT+$QCCTM
AT+$QCBANDPREF
AT+^PREFMODE
AT+^SYSINFO
AT+^SYSCONFIG
AT+^CARDMODE
AT+^DSCI
AT+$QCVOLT
AT+$QCHWREV
AT+$QCBOOTVER
AT+$ECALL
AT+$QCDEFPROF
AT+$QCMRUE
AT+$QCMRUC
AT+$QCAPNE
AT+$QCPDPIMSCFGE
AT+$QCCLAC
AT+^SPN
AT+$QCRMCALL
AT+$QCDRX
AT+$MDN
AT+$MSID
AT+$MIPERR
AT+$1XRXPWR
AT+$1XECIO
AT+$DORXPWR
AT+$DOSINR
AT+$DEBUG
AT+$ERI
AT+FCLASS
AT+ICF
AT+IFC
AT+IPR
AT+GMI
AT+GMM
AT+GMR
AT+GCAP
AT+GSN
AT+CMEE
AT+WS46
AT+PACSP
AT+CLCC
Partition List
Thanks to balistic2 for providing this.
Code:
[email protected]:/ # ls -al /dev/block/platform/msm_sdcc.1/by-name/
lrwxrwxrwx root aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root backup -> /dev/block/mmcblk0p23
lrwxrwxrwx root boot -> /dev/block/mmcblk0p20
lrwxrwxrwx root cache -> /dev/block/mmcblk0p18
lrwxrwxrwx root carrier -> /dev/block/mmcblk0p28
lrwxrwxrwx root efs -> /dev/block/mmcblk0p10
lrwxrwxrwx root fota -> /dev/block/mmcblk0p22
lrwxrwxrwx root fsg -> /dev/block/mmcblk0p24
lrwxrwxrwx root hidden -> /dev/block/mmcblk0p27
lrwxrwxrwx root m9kefs1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root m9kefs2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root m9kefs3 -> /dev/block/mmcblk0p15
lrwxrwxrwx root mdm -> /dev/block/mmcblk0p2
lrwxrwxrwx root modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root param -> /dev/block/mmcblk0p19
lrwxrwxrwx root persdata -> /dev/block/mmcblk0p26
lrwxrwxrwx root persist -> /dev/block/mmcblk0p17
lrwxrwxrwx root recovery -> /dev/block/mmcblk0p21
lrwxrwxrwx root rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root sbl2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root sbl3 -> /dev/block/mmcblk0p5
lrwxrwxrwx root ssd -> /dev/block/mmcblk0p25
lrwxrwxrwx root system -> /dev/block/mmcblk0p16
lrwxrwxrwx root tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root userdata -> /dev/block/mmcblk0p29
AOSP Diag Mode
Make script or run in Script Manager. See here for more diag mode info.
Code:
#/system/bin/sh
#reboot phone to disable
#enables diag mode
echo "0" /sys/class/android_usb/android0/enable
echo "04E8" /sys/class/android_usb/android0/idVendor
echo "685D" /sys/class/android_usb/android0/idProduct
echo "diag,diag_mdm" /sys/class/android_usb/android0/f_diag/clients
echo "hsic" /sys/class/android_usb/android0/f_acm/acm_transports
echo "diag,acm,adb" /sys/class/android_usb/android0/functions
echo "1" /sys/module/ci13xxx_msm/parameters/streaming
echo "1" /sys/class/android_usb/android0/enable
autoprime said:
*#0011# - Service Mode
Click to expand...
Click to collapse
Mine says No Service. I hit Menu button. Wifi is the only thing that really gives me any options. There is a Wifi Power Save toggle switch for On or Off. What does this do?
jpkelly05 said:
Mine says No Service. I hit Menu button. Wifi is the only thing that really gives me any options. There is a Wifi Power Save toggle switch for On or Off. What does this do?
Click to expand...
Click to collapse
unfortunately i dont have this device yet so I can't say exactly what everything does. I'm just sifting thru dumps and roms to find fun stuff.
on a different note... I've updated the OP to include a script to enable diag mode on the GS4. Diag mode can be used to write new PRLs to your device while on an AOSP rom(using DFS or QPST etc)... or diag mode can be used for other fun things... but if you don't know what it does then you probably don't need it
whats the test screen? ##0#?? does anyone kno it? NEVERMIND!! i found it.. *#0*#
what are all the commands aosp roms will take?
Been trying to work on learning AT commands and found some in the modem.bin of the NAE tarball like AT+MSLSECUR and AT+SIMDETEC however NONE of the commands in this list do anything. I've tried a ? after the command and a =? after the command, still errors out. I'm connected to the modem port (not the port used for flashing phones but for sending AT commands). I think this port is labeled /dev/ttyUSB0. I've tried downgrading to MDC baseband. Still nothing. How the heck am I supposed to send these other AT commands to the phone?
@ecs87 The AT commands shown on top of this thread are not correct, because:
1) they are device dependent
2) they are service provider dependent
3) they are mixed "fake" AT commands, as interpreted by RIL daemon, and "real" Modem AT commands, as we like.
I have several posts and threads on this subject, please search. In addition, AT port may not be accessible if
already used by RIL daemon in some cases.
I figured it out EVA. Apparently you MUST be using a UART cable. I think it's just the regular USB cable with a resistor on a line. I didn't do too much research on it because I was able to simulate the same thing using a GSM service box and a c3300k cable then accessing the box port using a terminal type application. I was then able to use the "exteneded" set of AT commands I found in modem.bin. The AT+AKSEEDNO does have me stumped though. Well...I guess the AT+MSLSECUR does as well. I'm able to get an output, but it must be calculated and returned. I was able to logcat the default MSLSECUR password for the G900P but I wasn't sure how it was calculated. Same goes for the AKSEEDNO. And considering how the AKSEEDNO changes every time you call for it, logging does nothing to help.
Sent from my SPH-L720 using XDA Free mobile app
My original thread for this is http://forum.gsmhosting.com/vbb/f83/note-3-imei-writing-questions-1828950/ Keep in mind I'm not trying to CHANGE the IMEI, but rather write the original one WITHOUT a box or EFS backup (I like to tinker...what can I say?). I got all the way down to the AKSEEDNO...then I hit a brick wall lol. Makes sense considering that's the absolute last step before I get to send the AT command to write the IMEI and sign the IMEI with a certificate.
Unable to access diag mode in AOSP
I've got a Galaxy S4 on SlimKat 4.4.4.
I've saved the script for AOSP diag mode in Script Manager, and ran it. I also tried running it over an ADB shell. Neither reports errors, but nothing ever changes. The phone remains the same. I've tried unplugging/replugging USB cable to no avail. The phone never shows as a different device in device manager. Are there any known reasons for this not working?
Hello all
I'm the proud owner of a stock HTC One and iPhone to Android convert...
My phone got water damaged then repaired by a water damaged specialist (new screen and ribbon) said company were quite rude with me and on digging deeper got slated on a 6 page forum thread...sigh
So I got the phone back and after two days I get a multi coloured screen and an exclamation mark in the battery..read about this as a connection fault or possibly a dead battery. The phoned stayed alive and switched on by leaving it plugged into a mains charger and I thought I'd leave it like this until I could think of the next move
The next move happened for me as the charge level, 0~5% dropped and bootloop started. Eventually the phone ran out of juice and switched off (I have no option to switch it off with the power button) and then started to accept a charge with USB cable from a macbook.
So now I have a fully charged phone showing a green led that is switched off. My Mum passed away a couple of months back and I'd like to retrieve the photos of her before attempting a factory reset - Ive read that re flashing the ROM might help but I'm a newb to this, prob could do it with instruction but ideally would just like the data taken off the phone and would then give the insurance company a ring
Any advice or guidance very much appreciated
Anyone?
Considering what you guys on the forum know what to do with a phone this must be pretty vanilla but some help would be really apprecisted , cheers
diytothestars said:
Anyone?
Considering what you guys on the forum know what to do with a phone this must be pretty vanilla but some help would be really apprecisted , cheers
Click to expand...
Click to collapse
your phone has hardware problems from getting Wet and being opened by technicians. I'm sorry but theirs nothing we can do for you
clsA said:
your phone has hardware problems from getting Wet and being opened by technicians. I'm sorry but theirs nothing we can do for you
Click to expand...
Click to collapse
Thanks for your reply cisA
Does a hard reset wipe all images from the phone
Is there a way to get the images from the phone with phone boot looping - IE from recovery mode which I can get to
The boot looping started when I was downloading an update last week, could it have been corrupted due to low battery? Can this be remedied from Recovery mode?
diytothestars said:
Thanks for your reply cisA
Does a hard reset wipe all images from the phone
Is there a way to get the images from the phone with phone boot looping - IE from recovery mode which I can get to
The boot looping started when I was downloading an update last week, could it have been corrupted due to low battery? Can this be remedied from Recovery mode?
Click to expand...
Click to collapse
Twrp does have a file manager in it but your going to need an USB OTG flash drive to move the stuff too
you could put the phone in recovery and try to use adb pull /sdcard/DCIM/100MEDIA and see if you get anything
It worked for me
C:\fastboot>adb pull /sdcard/DCIM/100MEDIA
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
pull: building file list...
pull: /sdcard/DCIM/100MEDIA/IMAG0045.jpg -> ./IMAG0045.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0044.jpg -> ./IMAG0044.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0042.jpg -> ./IMAG0042.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0041.jpg -> ./IMAG0041.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0038_1.jpg -> ./IMAG0038_1.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0040.jpg -> ./IMAG0040.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0043.jpg -> ./IMAG0043.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0038.jpg -> ./IMAG0038.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0039.jpg -> ./IMAG0039.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0037.jpg -> ./IMAG0037.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0036.jpg -> ./IMAG0036.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0035.jpg -> ./IMAG0035.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0034.jpg -> ./IMAG0034.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0033.jpg -> ./IMAG0033.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0032.jpg -> ./IMAG0032.jpg
pull: /sdcard/DCIM/100MEDIA/ZOE_0009.jpg -> ./ZOE_0009.jpg
pull: /sdcard/DCIM/100MEDIA/ZOE_0009.mp4 -> ./ZOE_0009.mp4
pull: /sdcard/DCIM/100MEDIA/IMAG0031.jpg -> ./IMAG0031.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0030.jpg -> ./IMAG0030.jpg
pull: /sdcard/DCIM/100MEDIA/ZOE_0008.jpg -> ./ZOE_0008.jpg
pull: /sdcard/DCIM/100MEDIA/ZOE_0008.mp4 -> ./ZOE_0008.mp4
pull: /sdcard/DCIM/100MEDIA/ZOE_0007.jpg -> ./ZOE_0007.jpg
pull: /sdcard/DCIM/100MEDIA/ZOE_0007.mp4 -> ./ZOE_0007.mp4
pull: /sdcard/DCIM/100MEDIA/ZOE_0006.jpg -> ./ZOE_0006.jpg
pull: /sdcard/DCIM/100MEDIA/ZOE_0006.mp4 -> ./ZOE_0006.mp4
pull: /sdcard/DCIM/100MEDIA/ZOE_0005.jpg -> ./ZOE_0005.jpg
pull: /sdcard/DCIM/100MEDIA/ZOE_0005.mp4 -> ./ZOE_0005.mp4
pull: /sdcard/DCIM/100MEDIA/ZOE_0004.jpg -> ./ZOE_0004.jpg
pull: /sdcard/DCIM/100MEDIA/ZOE_0004.mp4 -> ./ZOE_0004.mp4
pull: /sdcard/DCIM/100MEDIA/ZOE_0003.jpg -> ./ZOE_0003.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0029.jpg -> ./IMAG0029.jpg
pull: /sdcard/DCIM/100MEDIA/ZOE_0003.mp4 -> ./ZOE_0003.mp4
pull: /sdcard/DCIM/100MEDIA/ZOE_0002.jpg -> ./ZOE_0002.jpg
pull: /sdcard/DCIM/100MEDIA/ZOE_0002.mp4 -> ./ZOE_0002.mp4
pull: /sdcard/DCIM/100MEDIA/IMAG0028.jpg -> ./IMAG0028.jpg
pull: /sdcard/DCIM/100MEDIA/ZOE_0001.jpg -> ./ZOE_0001.jpg
pull: /sdcard/DCIM/100MEDIA/ZOE_0001.mp4 -> ./ZOE_0001.mp4
pull: /sdcard/DCIM/100MEDIA/IMAG0027.jpg -> ./IMAG0027.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0026.jpg -> ./IMAG0026.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0025.jpg -> ./IMAG0025.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0024.jpg -> ./IMAG0024.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0023.jpg -> ./IMAG0023.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0022.jpg -> ./IMAG0022.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0021.jpg -> ./IMAG0021.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0020.jpg -> ./IMAG0020.jpg
pull: /sdcard/DCIM/100MEDIA/2014-06-18 10.41.42.jpg -> ./2014-06-18 10.41.42.jpg
pull: /sdcard/DCIM/100MEDIA/2014-06-18 10.42.13.jpg -> ./2014-06-18 10.42.13.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0019.jpg -> ./IMAG0019.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0018.jpg -> ./IMAG0018.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0017.jpg -> ./IMAG0017.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0012.jpg -> ./IMAG0012.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0016.jpg -> ./IMAG0016.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0015.jpg -> ./IMAG0015.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0014.jpg -> ./IMAG0014.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0013.jpg -> ./IMAG0013.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0011.jpg -> ./IMAG0011.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0010.jpg -> ./IMAG0010.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0009.jpg -> ./IMAG0009.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0008.jpg -> ./IMAG0008.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0007.jpg -> ./IMAG0007.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0006.jpg -> ./IMAG0006.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0005.jpg -> ./IMAG0005.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0004.jpg -> ./IMAG0004.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0003.jpg -> ./IMAG0003.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0002.jpg -> ./IMAG0002.jpg
pull: /sdcard/DCIM/100MEDIA/IMAG0001.jpg -> ./IMAG0001.jpg
66 files pulled. 0 files skipped.
3666 KB/s (491428713 bytes in 130.886s)
C:\fastboot>
Click to expand...
Click to collapse
Just an update on this, I switched the phone on last night after a 4 day rest and it didn't bootloop
I suspect a very low battery was the issue and getting a charge in via the laptop did it a favour
I've transferred my data via AFT which WAS recognised by the Mac this time
Many thanks for your advice
diytothestars said:
Just an update on this, I switched the phone on last night after a 4 day rest and it didn't bootloop
I suspect a very low battery was the issue and getting a charge in via the laptop did it a favour
I've transferred my data via AFT which WAS recognised by the Mac this time
Many thanks for your advice
Click to expand...
Click to collapse
Glad to hear it started working. Just a note though, if the battery dies and you charge it off a laptop, there is a lower current from the usb and thus, a slower charge. You might have been bootlooping because the couple mins on laptop charge wasn't enough to keep it on. Charge from the wall next time and make sure you give it 5-10 mins before booting up again.
Always better to charge from the wall. ?
this is a official Chinese version ,and not use /CUST to /VENDOR,so most of recovery not support it(but still can use it)I will upload to mega soon,and here is something i can show you
the first step is something you are ready,backup you file(whole data will be format) and unlock BL
the second step is flash the MIUI10 with p and pt
if you want go back to miui10 with o and non Treble,there is the third step
issues:
none，it is good for daily using
Attention:
don't flash any boot or boot fix, because this one is different with others, if you flashed any kernel or boot fix, it would NOT boot, but we can still flash MAGISK, just don't flash kernel or boot fix.zip
DOWNLOAD
MIUI10 WITH PIE AND PROJECT TREBLE
https://mega.nz/#!KFAQjabB!0peaRtW89NVJSqRCI0olqLO3-DI9Bvora5jwQhBe9iA
here is the rom you must flash by miflash if you want go back to non treble
https://mega.nz/#!Wc5AjK4a!LLGfxp5Fky_mABBwlh8gSFg8Iyihyst3YkHQxhxBXmE
abl -> /dev/block/sde23
ablbak -> /dev/block/sde24
apdp -> /dev/block/sde5
bk1 -> /dev/block/sda3
bk2 -> /dev/block/sda4
bk3 -> /dev/block/sda5
bk31 -> /dev/block/sdd2
bk32 -> /dev/block/sdd5
bk4 -> /dev/block/sda8
bk41 -> /dev/block/sde4
bk42 -> /dev/block/sde30
bk43 -> /dev/block/sde45
bk5 -> /dev/block/sda12
bk51 -> /dev/block/sdf2
bk52 -> /dev/block/sdf3
bk53 -> /dev/block/sdf6
bk6 -> /dev/block/sda13
bluetooth -> /dev/block/sde32
boot -> /dev/block/sde40
cache -> /dev/block/sda16
cdt -> /dev/block/sdd3
cmnlib -> /dev/block/sde19
cmnlib64 -> /dev/block/sde21
cmnlib64bak -> /dev/block/sde22
cmnlibbak -> /dev/block/sde20
cust -> /dev/block/sde42
ddr -> /dev/block/sdd4
devcfg -> /dev/block/sde7
devcfgbak -> /dev/block/sde8
devinfo -> /dev/block/sde35
dip -> /dev/block/sde31
dpo -> /dev/block/sde1
dsp -> /dev/block/sde37
frp -> /dev/block/sda7
fsc -> /dev/block/sdf1
fsg -> /dev/block/sde34
hyp -> /dev/block/sde13
hypbak -> /dev/block/sde14
keymaster -> /dev/block/sde17
keymasterbak -> /dev/block/sde18
keystore -> /dev/block/sda6
limits -> /dev/block/sde3
logfs -> /dev/block/sda10
logo -> /dev/block/sde36
mdtp -> /dev/block/sde39
mdtpsecapp -> /dev/block/sde25
mdtpsecappbak -> /dev/block/sde26
misc -> /dev/block/sda9
modem -> /dev/block/sde41
modemst1 -> /dev/block/sdf4
modemst2 -> /dev/block/sdf5
msadp -> /dev/block/sde6
oops -> /dev/block/sda11
persist -> /dev/block/sda14
pmic -> /dev/block/sde9
pmicbak -> /dev/block/sde10
recovery -> /dev/block/sda15
reserve -> /dev/block/sdd1
rpm -> /dev/block/sde11
rpmbak -> /dev/block/sde12
sec -> /dev/block/sde2
splash -> /dev/block/sde38
ssd -> /dev/block/sda2
sti -> /dev/block/sde33
storsec -> /dev/block/sde28
storsecbak -> /dev/block/sde29
switch -> /dev/block/sda1
system -> /dev/block/sde44
toolsfv -> /dev/block/sde27
tz -> /dev/block/sde15
tzbak -> /dev/block/sde16
userdata -> /dev/block/sda17
vendor -> /dev/block/sde43
xbl -> /dev/block/sdb1
xblbak -> /dev/block/sdc1
my english is poor,but i will try my best to help you
here is the line
https://pan.baidu.com/s/1RwPOoavi2YNwcrTNgPV8UQ，and put '8xtv' to web to get MIUI10 with p and pt
https://pan.baidu.com/s/1bG9W13mWuWWZyN2PpcyqVg，and put 'kfp0' to web to get MIUI10 with o and non Treble
I will upgrade it to mega
now it's 5 o'clock in the morning,so tired
Good job
artful said:
Good job
Click to expand...
Click to collapse
added MEGA download
Could you get the global version?
Thanks for the chinese version.
Greetings
Thank you for the post.
I am on the xiaomi.eu ROM. I got the android pie, but I don't have Treble enabled.
Why is this?
Sent from my MI 6 using Tapatalk
It is said that flashing this firmware will fix the fingerprint sensor , you can have a try.
https://pan.baidu.com/s/1Y2NQnEBYVQeRcTDHRrI7DA
code: dzb8
Interesting! But I have already back to lineage,MIUI made me lost my patience.
LKc丶 said:
It is said that flashing this firmware will fix the fingerprint sensor , you can have a try.
https://pan.baidu.com/s/1Y2NQnEBYVQeRcTDHRrI7DA
code: dzb8
Click to expand...
Click to collapse
Please, can you upload it to mega? I can't download from baidu because I don't have chinese number phone.
juanyllo87 said:
Please, can you upload it to mega? I can't download from baidu because I don't have chinese number phone.
Click to expand...
Click to collapse
In China we can only use free Baidu netdisk :crying:,but I think he will upload it to mega soon.
juanyllo87 said:
Please, can you upload it to mega? I can't download from baidu because I don't have chinese number phone.
Click to expand...
Click to collapse
have a try
https://mega.nz/#!7oZjQIiI!3ZVx_DmC2wAnUtNoTLsDgTKR2QTdAqFDQ7OmITaQs3Q
LKc丶 said:
have a try
https://mega.nz/#!7oZjQIiI!3ZVx_DmC2wAnUtNoTLsDgTKR2QTdAqFDQ7OmITaQs3Q
Click to expand...
Click to collapse
still can't add fingerprint
akd1 said:
still can't add fingerprint
Click to expand...
Click to collapse
That's too bad .
As I Know,PT is not officially released by Xiaomi, but there may be a officially stable PT version after the vacation. (Labour Day)
Let's wait.
If someone wants to install another rom you must first install this, to remove treble.
Install with Xiaomi MiFlash Tool
https://mega.nz/#!cxRh2YjR!eZKkhIIlUiUvCCdcFONuZXTMhQqnpx4DpXLnTrhTYQk
juanyllo87 said:
Could you get the global version?
Thanks for the chinese version.
Greetings
Click to expand...
Click to collapse
don't have global vesion,but it's easy to add gapps
LKc丶 said:
That's too bad .
As I Know,PT is not officially released by Xiaomi, but there may be a officially stable PT version after the vacation. (Labour Day)
Let's wait.
Click to expand...
Click to collapse
this is a offical vesion,developed by XIAOMI,but not released and will never released,this is let you easy to flash another rom,as the XIAOMI framework developers said,this is the final version with project treble,so if you had flashed the PT from others,better to change to this office version(by the way,as i test,this pt could flash color os )
juanyllo87 said:
If someone wants to install another rom you must first install this, to remove treble.
Install with Xiaomi MiFlash Tool
https://mega.nz/#!cxRh2YjR!eZKkhIIlUiUvCCdcFONuZXTMhQqnpx4DpXLnTrhTYQk
Click to expand...
Click to collapse
still could install other PT rom,as for me,i won't go back
Works with:
- Xiaomi Redmi 9 Power
- Xiaomi Redmi 9T
Build Date:
2021/06/13
Android Version:
QKQ1.200730.002
Display ID:
QL2880-lime-V065-Q-0613
Build Fingerprint:
Redmi/lime/lime:10/QKQ1.200730.002/1648:userdebug/test-keys
Security Patch:
2020-10-01
Radio/Modem/Baseband Version:
A.1.0-00505.1-KAMORTA_GEN_PACK-3
Download:
https://www.mediafire.com/file/y25b...ing_QL2880-lime-V065-Q-0613_by-VD171.zip/file
Password:
Pass is in the attached file: PASSWORD_by_VD171.txt
Prop.default:
Code:
ro.build.version.incremental=1648
ro.odm.build.version.incremental=1648
ro.vendor.build.version.incremental=1648
ro.product.board=lime
ro.product.odm.device=lime
ro.product.odm.model=lime
ro.product.odm.name=lime
ro.product.system.device=lime
ro.product.system.model=lime
ro.product.system.name=lime
ro.product.vendor.device=lime
ro.product.vendor.model=lime
ro.product.vendor.name=lime
ro.build.flavor=lime-userdebug
ro.build.display.id=QL2880-lime-V065-Q-0613
ro.board.platform=bengal
ro.build.id=QKQ1.200730.002
ro.odm.build.id=QKQ1.200730.002
ro.system.build.id=QKQ1.200730.002
ro.vendor.build.id=QKQ1.200730.002
ro.bootimage.build.fingerprint=Redmi/lime/lime:10/QKQ1.200730.002/1648:userdebug/test-keys
ro.odm.build.fingerprint=Redmi/lime/lime:10/QKQ1.200730.002/1648:userdebug/test-keys
ro.system.build.fingerprint=Redmi/lime/lime:10/QKQ1.200730.002/1648:userdebug/test-keys
ro.vendor.build.fingerprint=Redmi/lime/lime:10/QKQ1.200730.002/1648:userdebug/test-keys
ro.build.tags=test-keys
ro.odm.build.tags=test-keys
ro.system.build.tags=test-keys
ro.vendor.build.tags=test-keys
ro.build.type=userdebug
ro.odm.build.type=userdebug
ro.system.build.type=userdebug
ro.vendor.build.type=userdebug
ro.build.version.security_patch=2020-10-01
ro.vendor.build.security_patch=2020-10-01
ro.bootimage.build.date=Sun Jun 13 11:26:22 CST 2021
ro.build.date=Sun Jun 13 11:26:22 CST 2021
ro.odm.build.date=Sun Jun 13 11:26:22 CST 2021
ro.system.build.date=Sun Jun 13 11:26:22 CST 2021
ro.vendor.build.date=Sun Jun 13 11:26:22 CST 2021
MD5 hashes:
Code:
abl.elf -> 307b569127da67ebdeb370565583de1a
adsp.mbn -> ffa7d3bc5ef6f891ab5125d48234b89b
Android.mk -> 9974f4247eb0ae79e4b255bc9f00fcbb
AndroidBoard.mk -> a6b120e6be701425f0173dd692da4251
AndroidProducts.mk -> 02ceda404d626107e7120c75b69f78e0
apdp.mbn -> f07702b513692fcc0527f7b110352349
BoardConfig.mk -> 9faf9a77e686cdf7c376b597187f9ac3
boot-debug.img -> 6a4e7d179387eb2e2bf34289c7b0c5a8
boot.img -> 1657f03a47b851e8a4bb8c17c8ccb86a
BTFM.bin -> 60bafd6a584fb0a7400cf2165ca88e43
cache.img -> b8153431cc4d6ea191b645e0a128bdc0
cdsp.mbn -> 011980a2a26de149c948c1231d53cf22
cmnlib.mbn -> 77fa0376beb60fb0bd012a6494df9a6a
cmnlib64.mbn -> f355ecc5aa729b2d2b1c368b78251538
crclist.txt -> e02e29f4e54bd8296d21e58e631e9d2d
devcfg.mbn -> f1a7eeb49175d09288c17617f518646f
dspso.bin -> 05ac90f5b8ed3081953bfc6fa6892723
dtb.img -> 39e42397b1a22d76cd719541c5352098
dtbo.img -> ee0390d2139b9ee762e78284856c4621
featenabler.mbn -> 72cee21b29be1d40fc1c67ba7f77b2b3
ffu_list.txt -> de14db3496000a21b5dfab4aebbdd65b
fpctzappfingerprint.mbn -> 74fa2cff302eba319ceab45fe6800584
framework_manifest.xml -> 27356acf4cc0f74dcc57a6d15feacf4d
fsgall.img -> f41be81fc7bc6399253ff709f7505b6f
fstab_AB_dynamic_partition.qti -> 7c3d314e66a594d3eb4e33595ffc38be
fstab_AB_variant.qti -> 119a06c449fd04b505197683f0efcd09
fstab_non_AB_dynamic_partition.qti -> 6f4d0e4bae0bae60b6d71fac323dc472
fstab_non_AB_variant.qti -> 6dec0d19154c8281a42442fcb86bbb83
goodixfp.mbn -> c2ef5ece85b46b8da46e22e7a5c76524
gpio-keys.kl -> fab01e275a873c98eb02d028914d106e
gpt_backup0.bin -> a36dcedb727673b91a2e7b8b22a1aa75
gpt_backup1.bin -> f0de661557245fd66019c67609c947da
gpt_backup2.bin -> c06bcb8b4e61886020a05a285acd741c
gpt_backup3.bin -> befa5fc7e32238c271d301809de66e02
gpt_backup4.bin -> 2b488b4ca19529696da66503c31fec99
gpt_backup5.bin -> 5297cf70c8bea38c889f4a7f7cb34aed
gpt_both0.bin -> 5cad138c5ee02829f9c93b05b204f95e
gpt_both1.bin -> bd2495d9ab349f50b79b1ff725dbe685
gpt_both2.bin -> 70eb31cdc704c1069733716a954c4f56
gpt_both3.bin -> 4089e123aa5efeef27e243ff672971f4
gpt_both4.bin -> 6e7eeea89b88461b4ab002c01be3ea5a
gpt_both5.bin -> 9f4fea4d36ccd14d4e2520d5dc63374d
gpt_empty0.bin -> 7b062e4b9562bb74ea8fe445676b3a92
gpt_empty1.bin -> 7b062e4b9562bb74ea8fe445676b3a92
gpt_empty2.bin -> 7b062e4b9562bb74ea8fe445676b3a92
gpt_empty3.bin -> 7b062e4b9562bb74ea8fe445676b3a92
gpt_empty4.bin -> 7b062e4b9562bb74ea8fe445676b3a92
gpt_empty5.bin -> 7b062e4b9562bb74ea8fe445676b3a92
gpt_main0.bin -> 02a364a649d8ceacfb1d4ef999c69a32
gpt_main1.bin -> 89cd12e778b682e1bbef3c39d4c04b47
gpt_main2.bin -> 0126324ac62639234b97c15b24a3fb6a
gpt_main3.bin -> 79d7af8800e97a51b6a3777275f4c8dc
gpt_main4.bin -> f81792b8fce6267a71cb2f1ef1ce3666
gpt_main5.bin -> 41043df5c47c07d3204f8ccecb4e7978
gptest.mbn -> c566897e78ab5c509715fa45dcf4a5f0
haventkn.mbn -> f2aebab2e886c94644eeda2f27d5addf
hyp.mbn -> 42208206997cfade7c3e48b356eab71a
imagefv.elf -> 6aa23453aa999dc35eba9923f1441609
init.target.rc -> aeb427a1c3333b6d9dc77f3f776eb506
km4.mbn -> 9a438dc22df7c80178cacfd62ef60184
lime.mk -> 1dfbe34c27e319b90441c9a89af1d39d
logfs_ufs_8mb.bin -> c040a889d66a4f120f502f89b551f42b
manifest.xml -> caf0e96e0c0bf30f991f165030fa3cc4
manifest_ab.xml -> b623b992da295acd8310f43e8f4ebe85
metadata.img -> ac7abb42ba4dd0f75335153549f41f84
MICRON_LYRA2_64GB_0605.bin -> e35b487e8c63d492aac16db97cbd77ef
multi_image.mbn -> 434a8847eb2848e3ed6f25713aadad53
NON-HLOS.bin -> 875cb19f6013dfe44f1d15fc7b5159e2
NOTICE -> 98017cf03a7e1b612bcf232f9b44aa2e
odm_manifest_lemon.xml -> 9b290f8f379c3e8a6f8f79822acac677
odm_manifest_lime.xml -> 2384e886ad7573acb92604d4103c1c87
odm_manifest_pomelo.xml -> 2384e886ad7573acb92604d4103c1c87
partition.xml -> e3b3e37247680b45408fd3d1982eca09
patch0.xml -> 15694a6e6716908db07b048d915ab37f
patch1.xml -> 0780990ee59934bdcaffc918cac99aed
patch2.xml -> 81036277fd056a16c0e418a756a5a835
patch3.xml -> f1e955eeee449ed57767ac0b87552cf1
patch4.xml -> 82a65c3c86ad47ffa1aaa21417598c32
patch5.xml -> 90ed396b2667209688b315f4dcc37104
persist.img -> 9c8f964fb03faa6a79d6e4ab2dd1957d
prebuilt_dtbo.img -> 5a310187621d72f82d672daf91231463
product.img -> 3edbde6439c089e66368cd370c6cd903
prog_firehose_ddr.elf -> 13dd339bd2db3a8c9bdfa6357d41ca12
ProjectConfig.mk -> 8f9e31321f8452a1e690f2e426ad8a22
provision_hynix.xml -> c7fecbec91b6aa5449bbe7ff5c2ca51d
PT_3Dv5_TLC_Voyager_UFS2.2_A251_USER.bin -> ca3088a07474377f54429f7cb1d9d7a2
public.libraries-qti.txt -> d599da22e6c4b8467ce28e1e562250eb
qupv3fw.elf -> dde60357158c8f7275aa153d8e221bba
ramdisk-debug.img -> e931fe2a009dbaab4f60775f83f0e772
ramdisk-recovery.img -> 8e579f57d0695d925b08a63b57c809f1
ramdisk.img -> 19e3f68d17f4d8f5a8b47d24a4d3e72b
rawprogram0.xml -> 98c3a8110edccdf01c57bfa5f0dd97a3
rawprogram0_BLANK_GPT.xml -> b3200cadf9be377d4f950cc03f4490a6
rawprogram0_WIPE_PARTITIONS.xml -> a08020b62484e1bfa7dbc6a7a76ac8fb
rawprogram1.xml -> 1df8d77508440b40cce09e94d5904af9
rawprogram1_BLANK_GPT.xml -> 30c9b7228531bbc0a0bfc5421105c196
rawprogram1_WIPE_PARTITIONS.xml -> 2c9dd8708195e23f910c0728873662c6
rawprogram2.xml -> 5b75a6083172cce4147d4a8769d81a55
rawprogram2_BLANK_GPT.xml -> 3198bf3e352b48600e63b90979e71a08
rawprogram2_WIPE_PARTITIONS.xml -> db15a8c1ac994e50be924e32ed9f03f4
rawprogram3.xml -> e03411d04b290ffe1ea9b993d1f23074
rawprogram3_BLANK_GPT.xml -> 439d4e875584101690085e1c95833e24
rawprogram3_WIPE_PARTITIONS.xml -> 3322789cb2c9e42bebd04f364e7a7aed
rawprogram4.xml -> fbaa3ea21bca23aa413bb9167773c7c7
rawprogram4_BLANK_GPT.xml -> 4d34e3bb4a83abdbe5f1fbf972d31918
rawprogram4_WIPE_PARTITIONS.xml -> 1dae44f86205d39ac83a6f83ee8911ad
rawprogram5.xml -> ebc54f7ab9d20e97b7601fb71bab4d6f
rawprogram5_BLANK_GPT.xml -> 93e0a3b178a136cda2cbab8de547f645
rawprogram5_WIPE_PARTITIONS.xml -> 9abf9d0a5859d4394a159ea29b499d9a
recovery-two-step.img -> a5a6f212c93886ff8515c2479ef4bfb2
recovery.img -> 251497aba4fed6188919606dda5cd715
recovery_AB_dynamic_partition.fstab -> a1734c76b6cf3c7cceb6384f2b167bf9
recovery_AB_variant.fstab -> 131037786ef6b9a8c56a1e34cb03ecc5
recovery_non-AB_dynamic_partition.fstab -> e4e761473a7a0e190c3e0ed5d5438600
recovery_non-AB_variant.fstab -> 379263def26dcaf344aa027980f4b731
rpm.mbn -> 05c3096461be56f1d94200be9124c547
S101_64G_430bda1ae4_MICRON.bin -> 2644fac2ba2516c40aee7cc543544a29
S201_64G_dd6e035122_MICRON.bin -> ea229b469d8e39e2d411cdac0fc467fa
SANTOS_UFS_2_2_V5_TLC_256Gb_128GB_P17.bin -> 1238740ee9d31d3f5b560c61f94f7845
Santos_V5_TLC_128GB_P15_General.bin -> f02b19fc3bcb8f2a9f1c8bdb919a86ac
sec.dat -> 21775907582b06389a656ab56011c160
sec.elf -> db0ff694b116843bef34a1b8fc1fbd5b
smplap64.mbn -> 6ef1323ee8a74727359ca510719fea36
soter64.mbn -> 9ecc10629adb114076489cd12540d94c
sparsecrclist.txt -> a6b02a3d5d0819ae7a994decbb456db9
storsec.mbn -> cbcaa3cd55ef02eb318066eaa800cf90
super.img -> ec54cd76fc3d8300a37222bc9ad9b31a
super_empty.img -> 1f8c5307a34885c9577d875d5c366d93
system.img -> 2e1cd737578b8c94dd0ead1c9ddeb97f
system.prop -> dcf0fa9fc04edeaed8ef6a9d0d224276
tz.mbn -> 21c38fd53a3c46e1ebdb2efc59bacba7
uefi_sec.mbn -> 4a28fa0f72ecc18a173d8035098e36c5
userdata.img -> e952e2c175d99f35d20acdd31d90e8f2
vbmeta.img -> 1cbd4a76cf8bc05d1dc3f84fb2dacf02
vbmeta_system.img -> 74a918bbd11203de6d001c2ebade8f08
vendor.img -> 3dd4303c5c516e33f374a6419e0656b6
vold.fstab -> a1e06a3daf0404cb89944e95dfdd8fec
widevine.mbn -> f07842bfedbf439111d9be6a6a35eb81
xbl.elf -> 14cda50cabdaaae74a0a204a39b68b32
xbl_config.elf -> 7975e2560048f7c4a543045d399091ee
Xiaomi_Columbus_S76_PRV_0005_Official_FW_bitflip_count.bin -> fc9018659527ad3add419eff38a75753
Xiaomi_Columbus_S76_T005_Test _FW_bitflip_count.bin -> 7f6647928bb0eb78b2c583603fffd460
zeros_1sector.bin -> 620f0b67a91f7f74151bc5be745b7110
zeros_5sectors.bin -> daa100df6e6711906b61c9ab5aa16032
Woah, nice!
Done.
Uploaded.
Enjoy !
Hey,
I noticed that the EDL Loader included in the Engineering Firmware does not require an authentication, meaning that the Redmi 9T can now be unbricked without having to contact a Service Center, etc.
Thank you
TheRedHugo said:
Hey,
I noticed that the EDL Loader included in the Engineering Firmware does not require an authentication, meaning that the Redmi 9T can now be unbricked without having to contact a Service Center, etc.
Thank you
Click to expand...
Click to collapse
Very good work, my friend.
You are welcome
Hello, phone come with problem:
Not power on, when connect to PC - hs-usb qdloader 9008
Try flash it. Flash Ok, but problem same
Not power on, when connect to PC - hs-usb qdloader 9008
What may be? Memory die?
Abzal said:
Hello, phone come with problem:
Not power on, when connect to PC - hs-usb qdloader 9008
Try flash it. Flash Ok, but problem same
Not power on, when connect to PC - hs-usb qdloader 9008
What may be? Memory die?
Click to expand...
Click to collapse
If you can flash to the device, it is not dead.
So what problem may be?
VD171 said:
Works withass
- Xiaomi Redmi 9 Power
- Xiaomi Redmi 9T
Build Date:
2021/06/13
Android Version:
QKQ1.200730.002
Display ID:
QL2880-lime-V065-Q-0613
Build Fingerprint:
Redmi/lime/lime:10/QKQ1.200730.002/1648:userdebug/test-keys
Security Patch:
2020-10-01
Radio/Modem/Baseband Version:
A.1.0-00505.1-KAMORTA_GEN_PACK-3
Download:
https://www.mediafire.com/file/y25b...ing_QL2880-lime-V065-Q-0613_by-VD171.zip/file
Password:
Pass is in the attached file: PASSWORD_by_VD171.txt
Prop.default:
Code:
ro.build.version.incremental=1648
ro.odm.build.version.incremental=1648
ro.vendor.build.version.incremental=1648
ro.product.board=lime
ro.product.odm.device=lime
ro.product.odm.model=lime
ro.product.odm.name=lime
ro.product.system.device=lime
ro.product.system.model=lime
ro.product.system.name=lime
ro.product.vendor.device=lime
ro.product.vendor.model=lime
ro.product.vendor.name=lime
ro.build.flavor=lime-userdebug
ro.build.display.id=QL2880-lime-V065-Q-0613
ro.board.platform=bengal
ro.build.id=QKQ1.200730.002
ro.odm.build.id=QKQ1.200730.002
ro.system.build.id=QKQ1.200730.002
ro.vendor.build.id=QKQ1.200730.002
ro.bootimage.build.fingerprint=Redmi/lime/lime:10/QKQ1.200730.002/1648:userdebug/test-keys
ro.odm.build.fingerprint=Redmi/lime/lime:10/QKQ1.200730.002/1648:userdebug/test-keys
ro.system.build.fingerprint=Redmi/lime/lime:10/QKQ1.200730.002/1648:userdebug/test-keys
ro.vendor.build.fingerprint=Redmi/lime/lime:10/QKQ1.200730.002/1648:userdebug/test-keys
ro.build.tags=test-keys
ro.odm.build.tags=test-keys
ro.system.build.tags=test-keys
ro.vendor.build.tags=test-keys
ro.build.type=userdebug
ro.odm.build.type=userdebug
ro.system.build.type=userdebug
ro.vendor.build.type=userdebug
ro.build.version.security_patch=2020-10-01
ro.vendor.build.security_patch=2020-10-01
ro.bootimage.build.date=Sun Jun 13 11:26:22 CST 2021
ro.build.date=Sun Jun 13 11:26:22 CST 2021
ro.odm.build.date=Sun Jun 13 11:26:22 CST 2021
ro.system.build.date=Sun Jun 13 11:26:22 CST 2021
ro.vendor.build.date=Sun Jun 13 11:26:22 CST 2021
MD5 hashes:
Code:
abl.elf -> 307b569127da67ebdeb370565583de1a
adsp.mbn -> ffa7d3bc5ef6f891ab5125d48234b89b
Android.mk -> 9974f4247eb0ae79e4b255bc9f00fcbb
AndroidBoard.mk -> a6b120e6be701425f0173dd692da4251
AndroidProducts.mk -> 02ceda404d626107e7120c75b69f78e0
apdp.mbn -> f07702b513692fcc0527f7b110352349
BoardConfig.mk -> 9faf9a77e686cdf7c376b597187f9ac3
boot-debug.img -> 6a4e7d179387eb2e2bf34289c7b0c5a8
boot.img -> 1657f03a47b851e8a4bb8c17c8ccb86a
BTFM.bin -> 60bafd6a584fb0a7400cf2165ca88e43
cache.img -> b8153431cc4d6ea191b645e0a128bdc0
cdsp.mbn -> 011980a2a26de149c948c1231d53cf22
cmnlib.mbn -> 77fa0376beb60fb0bd012a6494df9a6a
cmnlib64.mbn -> f355ecc5aa729b2d2b1c368b78251538
crclist.txt -> e02e29f4e54bd8296d21e58e631e9d2d
devcfg.mbn -> f1a7eeb49175d09288c17617f518646f
dspso.bin -> 05ac90f5b8ed3081953bfc6fa6892723
dtb.img -> 39e42397b1a22d76cd719541c5352098
dtbo.img -> ee0390d2139b9ee762e78284856c4621
featenabler.mbn -> 72cee21b29be1d40fc1c67ba7f77b2b3
ffu_list.txt -> de14db3496000a21b5dfab4aebbdd65b
fpctzappfingerprint.mbn -> 74fa2cff302eba319ceab45fe6800584
framework_manifest.xml -> 27356acf4cc0f74dcc57a6d15feacf4d
fsgall.img -> f41be81fc7bc6399253ff709f7505b6f
fstab_AB_dynamic_partition.qti -> 7c3d314e66a594d3eb4e33595ffc38be
fstab_AB_variant.qti -> 119a06c449fd04b505197683f0efcd09
fstab_non_AB_dynamic_partition.qti -> 6f4d0e4bae0bae60b6d71fac323dc472
fstab_non_AB_variant.qti -> 6dec0d19154c8281a42442fcb86bbb83
goodixfp.mbn -> c2ef5ece85b46b8da46e22e7a5c76524
gpio-keys.kl -> fab01e275a873c98eb02d028914d106e
gpt_backup0.bin -> a36dcedb727673b91a2e7b8b22a1aa75
gpt_backup1.bin -> f0de661557245fd66019c67609c947da
gpt_backup2.bin -> c06bcb8b4e61886020a05a285acd741c
gpt_backup3.bin -> befa5fc7e32238c271d301809de66e02
gpt_backup4.bin -> 2b488b4ca19529696da66503c31fec99
gpt_backup5.bin -> 5297cf70c8bea38c889f4a7f7cb34aed
gpt_both0.bin -> 5cad138c5ee02829f9c93b05b204f95e
gpt_both1.bin -> bd2495d9ab349f50b79b1ff725dbe685
gpt_both2.bin -> 70eb31cdc704c1069733716a954c4f56
gpt_both3.bin -> 4089e123aa5efeef27e243ff672971f4
gpt_both4.bin -> 6e7eeea89b88461b4ab002c01be3ea5a
gpt_both5.bin -> 9f4fea4d36ccd14d4e2520d5dc63374d
gpt_empty0.bin -> 7b062e4b9562bb74ea8fe445676b3a92
gpt_empty1.bin -> 7b062e4b9562bb74ea8fe445676b3a92
gpt_empty2.bin -> 7b062e4b9562bb74ea8fe445676b3a92
gpt_empty3.bin -> 7b062e4b9562bb74ea8fe445676b3a92
gpt_empty4.bin -> 7b062e4b9562bb74ea8fe445676b3a92
gpt_empty5.bin -> 7b062e4b9562bb74ea8fe445676b3a92
gpt_main0.bin -> 02a364a649d8ceacfb1d4ef999c69a32
gpt_main1.bin -> 89cd12e778b682e1bbef3c39d4c04b47
gpt_main2.bin -> 0126324ac62639234b97c15b24a3fb6a
gpt_main3.bin -> 79d7af8800e97a51b6a3777275f4c8dc
gpt_main4.bin -> f81792b8fce6267a71cb2f1ef1ce3666
gpt_main5.bin -> 41043df5c47c07d3204f8ccecb4e7978
gptest.mbn -> c566897e78ab5c509715fa45dcf4a5f0
haventkn.mbn -> f2aebab2e886c94644eeda2f27d5addf
hyp.mbn -> 42208206997cfade7c3e48b356eab71a
imagefv.elf -> 6aa23453aa999dc35eba9923f1441609
init.target.rc -> aeb427a1c3333b6d9dc77f3f776eb506
km4.mbn -> 9a438dc22df7c80178cacfd62ef60184
lime.mk -> 1dfbe34c27e319b90441c9a89af1d39d
logfs_ufs_8mb.bin -> c040a889d66a4f120f502f89b551f42b
manifest.xml -> caf0e96e0c0bf30f991f165030fa3cc4
manifest_ab.xml -> b623b992da295acd8310f43e8f4ebe85
metadata.img -> ac7abb42ba4dd0f75335153549f41f84
MICRON_LYRA2_64GB_0605.bin -> e35b487e8c63d492aac16db97cbd77ef
multi_image.mbn -> 434a8847eb2848e3ed6f25713aadad53
NON-HLOS.bin -> 875cb19f6013dfe44f1d15fc7b5159e2
NOTICE -> 98017cf03a7e1b612bcf232f9b44aa2e
odm_manifest_lemon.xml -> 9b290f8f379c3e8a6f8f79822acac677
odm_manifest_lime.xml -> 2384e886ad7573acb92604d4103c1c87
odm_manifest_pomelo.xml -> 2384e886ad7573acb92604d4103c1c87
partition.xml -> e3b3e37247680b45408fd3d1982eca09
patch0.xml -> 15694a6e6716908db07b048d915ab37f
patch1.xml -> 0780990ee59934bdcaffc918cac99aed
patch2.xml -> 81036277fd056a16c0e418a756a5a835
patch3.xml -> f1e955eeee449ed57767ac0b87552cf1
patch4.xml -> 82a65c3c86ad47ffa1aaa21417598c32
patch5.xml -> 90ed396b2667209688b315f4dcc37104
persist.img -> 9c8f964fb03faa6a79d6e4ab2dd1957d
prebuilt_dtbo.img -> 5a310187621d72f82d672daf91231463
product.img -> 3edbde6439c089e66368cd370c6cd903
prog_firehose_ddr.elf -> 13dd339bd2db3a8c9bdfa6357d41ca12
ProjectConfig.mk -> 8f9e31321f8452a1e690f2e426ad8a22
provision_hynix.xml -> c7fecbec91b6aa5449bbe7ff5c2ca51d
PT_3Dv5_TLC_Voyager_UFS2.2_A251_USER.bin -> ca3088a07474377f54429f7cb1d9d7a2
public.libraries-qti.txt -> d599da22e6c4b8467ce28e1e562250eb
qupv3fw.elf -> dde60357158c8f7275aa153d8e221bba
ramdisk-debug.img -> e931fe2a009dbaab4f60775f83f0e772
ramdisk-recovery.img -> 8e579f57d0695d925b08a63b57c809f1
ramdisk.img -> 19e3f68d17f4d8f5a8b47d24a4d3e72b
rawprogram0.xml -> 98c3a8110edccdf01c57bfa5f0dd97a3
rawprogram0_BLANK_GPT.xml -> b3200cadf9be377d4f950cc03f4490a6
rawprogram0_WIPE_PARTITIONS.xml -> a08020b62484e1bfa7dbc6a7a76ac8fb
rawprogram1.xml -> 1df8d77508440b40cce09e94d5904af9
rawprogram1_BLANK_GPT.xml -> 30c9b7228531bbc0a0bfc5421105c196
rawprogram1_WIPE_PARTITIONS.xml -> 2c9dd8708195e23f910c0728873662c6
rawprogram2.xml -> 5b75a6083172cce4147d4a8769d81a55
rawprogram2_BLANK_GPT.xml -> 3198bf3e352b48600e63b90979e71a08
rawprogram2_WIPE_PARTITIONS.xml -> db15a8c1ac994e50be924e32ed9f03f4
rawprogram3.xml -> e03411d04b290ffe1ea9b993d1f23074
rawprogram3_BLANK_GPT.xml -> 439d4e875584101690085e1c95833e24
rawprogram3_WIPE_PARTITIONS.xml -> 3322789cb2c9e42bebd04f364e7a7aed
rawprogram4.xml -> fbaa3ea21bca23aa413bb9167773c7c7
rawprogram4_BLANK_GPT.xml -> 4d34e3bb4a83abdbe5f1fbf972d31918
rawprogram4_WIPE_PARTITIONS.xml -> 1dae44f86205d39ac83a6f83ee8911ad
rawprogram5.xml -> ebc54f7ab9d20e97b7601fb71bab4d6f
rawprogram5_BLANK_GPT.xml -> 93e0a3b178a136cda2cbab8de547f645
rawprogram5_WIPE_PARTITIONS.xml -> 9abf9d0a5859d4394a159ea29b499d9a
recovery-two-step.img -> a5a6f212c93886ff8515c2479ef4bfb2
recovery.img -> 251497aba4fed6188919606dda5cd715
recovery_AB_dynamic_partition.fstab -> a1734c76b6cf3c7cceb6384f2b167bf9
recovery_AB_variant.fstab -> 131037786ef6b9a8c56a1e34cb03ecc5
recovery_non-AB_dynamic_partition.fstab -> e4e761473a7a0e190c3e0ed5d5438600
recovery_non-AB_variant.fstab -> 379263def26dcaf344aa027980f4b731
rpm.mbn -> 05c3096461be56f1d94200be9124c547
S101_64G_430bda1ae4_MICRON.bin -> 2644fac2ba2516c40aee7cc543544a29
S201_64G_dd6e035122_MICRON.bin -> ea229b469d8e39e2d411cdac0fc467fa
SANTOS_UFS_2_2_V5_TLC_256Gb_128GB_P17.bin -> 1238740ee9d31d3f5b560c61f94f7845
Santos_V5_TLC_128GB_P15_General.bin -> f02b19fc3bcb8f2a9f1c8bdb919a86ac
sec.dat -> 21775907582b06389a656ab56011c160
sec.elf -> db0ff694b116843bef34a1b8fc1fbd5b
smplap64.mbn -> 6ef1323ee8a74727359ca510719fea36
soter64.mbn -> 9ecc10629adb114076489cd12540d94c
sparsecrclist.txt -> a6b02a3d5d0819ae7a994decbb456db9
storsec.mbn -> cbcaa3cd55ef02eb318066eaa800cf90
super.img -> ec54cd76fc3d8300a37222bc9ad9b31a
super_empty.img -> 1f8c5307a34885c9577d875d5c366d93
system.img -> 2e1cd737578b8c94dd0ead1c9ddeb97f
system.prop -> dcf0fa9fc04edeaed8ef6a9d0d224276
tz.mbn -> 21c38fd53a3c46e1ebdb2efc59bacba7
uefi_sec.mbn -> 4a28fa0f72ecc18a173d8035098e36c5
userdata.img -> e952e2c175d99f35d20acdd31d90e8f2
vbmeta.img -> 1cbd4a76cf8bc05d1dc3f84fb2dacf02
vbmeta_system.img -> 74a918bbd11203de6d001c2ebade8f08
vendor.img -> 3dd4303c5c516e33f374a6419e0656b6
vold.fstab -> a1e06a3daf0404cb89944e95dfdd8fec
widevine.mbn -> f07842bfedbf439111d9be6a6a35eb81
xbl.elf -> 14cda50cabdaaae74a0a204a39b68b32
xbl_config.elf -> 7975e2560048f7c4a543045d399091ee
Xiaomi_Columbus_S76_PRV_0005_Official_FW_bitflip_count.bin -> fc9018659527ad3add419eff38a75753
Xiaomi_Columbus_S76_T005_Test _FW_bitflip_count.bin -> 7f6647928bb0eb78b2c583603fffd460
zeros_1sector.bin -> 620f0b67a91f7f74151bc5be745b7110
zeros_5sectors.bin -> daa100df6e6711906b61c9ab5aa16032
Click to expand...
Click to collapse
Abzal said:
So what problem may be?
Click to expand...
Click to collapse
Allright, sorry. My mistake.
VD171 said:
Qdloader is for QUALCOMM devices.
LIME is mediatek.
Apparentely you doing something wrong.
Click to expand...
Click to collapse
Lime has Qualcomm Snapdragon 662 processor.
Show me Redmi 9T on mediatek, this phone go on Snapdragon 662
Allright, sorry. My mistake.
I'm not so familiarized with qualcomm devices.
How to flash normal firmware if bootloader locked. cant find unlock bootloader option
almat_moto said:
How to flash normal firmware if bootloader locked. cant find unlock bootloader option
Click to expand...
Click to collapse
Apply for unlocking Mi devices
en.miui.com
Thanks for providing this. Managed to unbrick my Redmi 9T that has been sitting in a drawer for months.
SZander93 said:
Thanks for providing this. Managed to unbrick my Redmi 9T that has been sitting in a drawer for months.
Click to expand...
Click to collapse
Good work, my friend.
You are welcome
Abzal said:
Hello, phone come with problem:
Not power on, when connect to PC - hs-usb qdloader 9008
Try flash it. Flash Ok, but problem same
Not power on, when connect to PC - hs-usb qdloader 9008
What may be? Memory die?
Click to expand...
Click to collapse
Hello, it is working way, maybe it can help you:
password not work
wil232 said:
password not work
Click to expand...
Click to collapse
Password is inside the attached file PASSWORD_by_VD171.txt.
Enjoy