NOTE-1:
I'm not a developer or something even near to that. All information provided here is copied from different internet sources and according to best of my knowledge.
I have tried this on QMobile Z8 only. It's similar to Wiko Ridge 4G and Blu Life One (2015) in hardware specifications.
I'll not be responsible for any harm to you or your device. It works perfectly for me. You may try it on your own risk.
Save / backup your data before continuing. Whole device will be wiped.
NOTE-2:
If you have a custom recovery, install Stock ROM instead.
If you don't have a custom recovery, get here.
If your device is bricked and can't boot into recovery or bootloader mode(read here what it is), proceed.
REQUIREMENTS:
A PC with Windows and uninterrupted power supply. (I used Dell Inspiron 15R with Windows 8.1 and 10). Microsoft Visual C++ 2010 x86 Redistributable must also be installed.
A USB data cable.
Fully charged phone, soft-bricked at maximum i.e. no recovery, no boot accessible
STEPS:
Download QMobile Z8 Factory Firmware KitKat 4.4.4 (QMobile Z8_MP_KK_QMB_PK_07) or Lollipop 5.0.2 (QMobileZ8_MP_5.0_QMB_PK_06). Extract files to some easily accessible folder, say Stock Firmware.
Download and Install Qualcomm USB Drivers to your PC
Download and Install QPST (QFIL Flasher) to your PC. Official flasher from Wiko also works fine with all firmware. Just need to replace firmware folder.
Run QFIL. No Port Available should be displayed on UI top.
Select Build Type: Flat Build
Click on Load XML. Navigate to Stock Firmware folder and select rawprogram xml (1 or 2) file/s.
On next window, select patch xml file from Stock Firmware folder.
On Select Programmer, click on Browse and select prog_emmc_firehouse mbn file from Stock Firmware folder.
Power off your phone. (Re-insert battery being on safe side)
Press Upper and Lower Volume buttons and hold (key combinations for Download mode / Emergency mode on QMobile Z8; may differ for other devices)
Connect phone to PC through USB cable. Hold volume keys. Driver installation may take some time on first connect. No Port Available will be replaced by Qualcomm HS-USB QDLoader 9008 (COM XX). Now phone is connected to PC in Download Mode.
You may also check device connectivity in Device Manager. Qualcomm HS-USB QDLoader 9008 (COM4) will appear under COM PORTS section. If it doesn't, try reinstalling drivers or uninstall any drivers installed for other devices. Reinstall given drivers and then reboot PC.
Keep HOLDing keys.
Click on Download and wait for download progress to start. Then release keys and wait for installation to complete. DO NOT INTERRUPT FLASHING PROCESS OR IT MAY HARD BRICK YOUR PHONE LEAVING IT USELESS.
Once Download is finished, Exit QFIL, disconnect phone from PC and press power button to reboot if it doesn't reboot on its own.
Done. You have a newly purchased phone in your hands if all goes well.
i have an issue when i am flashing it
11:56:58: INFO: =======================================================
11:56:58: INFO: TARGET SAID: '[email protected] [email protected]'
11:56:58: INFO: TARGET SAID: 'start 131072, num 97347'
11:57:00: INFO: Overall to target 2.016 seconds (12.32 MBps)
11:57:00: INFO: {percent files transferred 1.32%}
11:57:02: INFO: Overall to target 4.000 seconds (11.88 MBps)
11:57:02: INFO: {percent files transferred 2.54%}
11:57:02: INFO: TARGET SAID: 'Read back verify failed at sector 1036513896,num sectors 131072'
11:57:02: INFO: TARGET SAID: 'Finished sector address 131072'
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
11:57:02: {ERROR: Please see log}
Writing log to 'C:\Users\umair\AppData\Roaming\Qualcomm\QFIL\COMPORT_4\port_trace.txt', might take a minute
Log is 'C:\Users\umair\AppData\Roaming\Qualcomm\QFIL\COMPORT_4\port_trace.txt'
Download Fail:FireHose Fail:FHLoader Failrocess fail
Finish Download
here is the log of the error
ayyaroayyas said:
11:56:58: INFO: =======================================================
11:56:58: INFO: TARGET SAID: '[email protected] [email protected]'
11:56:58: INFO: TARGET SAID: 'start 131072, num 97347'
11:57:00: INFO: Overall to target 2.016 seconds (12.32 MBps)
11:57:00: INFO: {percent files transferred 1.32%}
11:57:02: INFO: Overall to target 4.000 seconds (11.88 MBps)
11:57:02: INFO: {percent files transferred 2.54%}
11:57:02: INFO: TARGET SAID: 'Read back verify failed at sector 1036513896,num sectors 131072'
11:57:02: INFO: TARGET SAID: 'Finished sector address 131072'
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
11:57:02: {ERROR: Please see log}
Writing log to 'C:\Users\umair\AppData\Roaming\Qualcomm\QFIL\COMPORT_4\port_trace.txt', might take a minute
Log is 'C:\Users\umair\AppData\Roaming\Qualcomm\QFIL\COMPORT_4\port_trace.txt'
Download Fail:FireHose Fail:FHLoader Failrocess fail
Finish Download
here is the log of the error
Click to expand...
Click to collapse
any solutions for this???
Antarez96 said:
any solutions for this???
Click to expand...
Click to collapse
Most probably eMMC is dead. See this.
Related
Another (official) way to flash OS.nb (part04.bin) .
Hi All!
To flash image we use nspl (part03.bin) with some modification.
How to use:
1. Download nspl.zip with part03.bin and part04.bin (0 byte) in it.
2. Replace in data.zip with orinal one and flash with DWI.exe .
3. Convert OS.nb (part.04.bin) to NBH with any tools.
You can use nbhgen by bot. Copy part04.bin in botNbhgen folder and run botNbhgen.bat .
4. During boot, when Splash appears on screen, press and hold VolDown, until the nspl boot.
Code:
screen: device:
Splash SPL ____
|
aMAGLDR V1.13 WM5 |
Booting WPH |
WPH LOAD |___ Press
123456 | &
GO GO GO | Hold
|
LOGO NSPL____|
________ Till
WP7
4. Run ROMUpdateUtility.exe by HTC to flash RUU_signed.nbh.
This method may be useful if errors occur when using magldr to flash part04.bin:
Code:
An error has occurred
Read below for more information
Error Description: send d000ff partition data failed
Info: .\RSPL\RSPL.cpp (1279)
Error Description:
Info: .\RSPL\RSPL.cpp (956)
AnDim
Reserved for future ..
thnks bro
Thanks bro,
it really helped me a lot...
I managed to get back the WP7 after 2 mnths from partition 4 failed issue
Will try when going back to WP7 after some Android refreshments
Thanks and Keep it up Andim.
Is this really interesting for dev to have another way to create rom, without proper DFT tools ?
I have an Alcatel Pixi3 4.5 4G model 5017O and I'm working on development for this phone.
I did a hexdump on the stock boot.img and was quite surprised to see this:
00004b80 |.......... -- Sy|
00004b90 |stem halted.Atte|
00004ba0 |mpting division |
00004bb0 |by 0!...Uncompre|
00004bc0 |ssing Linux.....|
00004bd0 |decompressor ret|
00004be0 |urned an error..|
00004bf0 | done, booting t|
00004c00 |he kernel...inva|
00004c10 |lid distance too|
00004c20 | far back...inva|
00004c30 |lid distance cod|
00004c40 |e...invalid lite|
00004c50 |ral/length code.|
00004c60 |incorrect header|
00004c70 | check..unknown |
00004c80 |compression meth|
00004c90 |od..invalid wind|
00004ca0 |ow size.invalid |
00004cb0 |block type..inva|
00004cc0 |lid stored block|
00004cd0 | lengths....too |
00004ce0 |many length or d|
00004cf0 |istance symbols.|
00004d00 |invalid code len|
00004d10 |gths set....inva|
00004d20 |lid bit length r|
00004d30 |epeat...invalid |
00004d40 |literal/lengths |
00004d50 |set.invalid dist|
00004d60 |ances set...inco|
00004d70 |rrect data check|
00004d80 |....Out of memor|
00004d90 |y while allocati|
00004da0 |ng output buffer|
00004db0 |....Out of memor|
00004dc0 |y while allocati|
00004dd0 |ng input buffer.|
00004de0 |Out of memory wh|
00004df0 |ile allocating z|
00004e00 |_stream.Out of m|
00004e10 |emory while allo|
00004e20 |cating workspace|
00004e30 |....Not a gzip f|
00004e40 |ile.header error|
00004e50 |....read error..|
00004e60 |uncompression er|
00004e70 |ror.............|
Does anyone else have an Alcatel, or any MediaTek based phone with a stock boot.img, that they can check to see if all of the phones they release are like this?
You can run a hexdump and check for yourself in Linux and let me know, or post your phone specs (MediaTek based only) here as well as a link to download your stock unmodified boot.img.
To do the hexdump cd into the dir with your stock boot.img and run the following command (in Linux):
hexdump -C "boot image name" | tee boot_dump.txt
where "boot image name" is the name of your boot image (without the quotes) that you made during a readback in SP Flash tools when you did your backup of you stock rom. The hexdump will be saved to a file named boot_dump.txt.
(You may have to run "sudo apt-get install hexdump" (without the quotes) in Ubuntu if you don't already have hexdump installed.)
If this is in the wrong section, please let me know.
Hey, i have a little problem and i would be grateful if someone would help me, my LeEco Le Max2 Bricked, the screen went blue , i turned it off and now it doesn't want to start at all or charge ( even the led is not functional)
I explored the forum and passed a few errors but i'm stuck at :
Total to be tansferd with <program> or <read> is 3.17 GB
22:18:04: INFO: Sending <configure>
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
22:18:04: {ERROR: XML not formed correctly. Expected a < character at loc 0}
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
22:18:04: {ERROR: 3. TAG not found or recognized}
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
22:18:04: {ERROR:
There is a chance your target is in SAHARA mode!!
There is a chance your target is in SAHARA mode!!
There is a chance your target is in SAHARA mode!!
This can mean
1. You forgot to send DeviceProgrammer first (i.e. QSaharaServer.exe -s 13rog_emmc_firehose_8994_lite.mbn)
2. OR, you did send DeviceProgrammer, but it has crashed and/or is not correct for this target
Regardless this program speaks FIREHOSE protocol and your target is speaking SAHARA protcol, so this will not work
}
Writing log to 'C:\Users\Aex\AppData\Roaming\Qualcomm\QFIL\port_trace.txt', might take a minute
Log is 'C:\Users\Aex\AppData\Roaming\Qualcomm\QFIL\port_trace.txt'
Download Fail:FireHose Fail FHLoader Failrocess fail
Finish Download
Thanks
do this steps :
https://www.gizmochina.com/2016/11/20/leeco-x820-max-2-super-unbrick-guide/
---------- Post added at 12:11 AM ---------- Previous post was at 12:11 AM ----------
do this steps :
https://www.gizmochina.com/2016/11/20/leeco-x820-max-2-super-unbrick-guide/
HTC-TYTN2 said:
do this steps :
https://www.gizmochina.com/2016/11/20/leeco-x820-max-2-super-unbrick-guide/
---------- Post added at 12:11 AM ---------- Previous post was at 12:11 AM ----------
do this steps :
https://www.gizmochina.com/2016/11/20/leeco-x820-max-2-super-unbrick-guide/
Click to expand...
Click to collapse
Why not this https://forum.xda-developers.com/le-max-2/how-to/guide-hard-brick-fix-qualcomm-hs-usb-t3492949 ?
valy_cta said:
Why not this https://forum.xda-developers.com/le-max-2/how-to/guide-hard-brick-fix-qualcomm-hs-usb-t3492949 ?
Click to expand...
Click to collapse
I didn't have any experience with flashing devices , when i said i didn't managed to make it work i was talking about your tutorial, i followed all your steps and i'm getting blocked by that error .
From the log I thought it was a corrupted file or something . Do you have any other idea why i'm getting that Firehose Error? I searched google and found 0 results in how i'm supposed to fix it
fratziweru said:
I didn't have any experience with flashing devices , when i said i didn't managed to make it work i was talking about your tutorial, i followed all your steps and i'm getting blocked by that error .
From the log I thought it was a corrupted file or something . Do you have any other idea why i'm getting that Firehose Error? I searched google and found 0 results in how i'm supposed to fix it
Click to expand...
Click to collapse
if the method can not unbrick your phone, you can try the firmware , hope help you .
https://www.needrom.com/download/le...ultilanguage-rom-unbrick-phone-qfil-fastboot/
Anybody know how to solve this problem?
/*invalid image type recieved*/
is_ack_succesfull : 1031 SAHARA_NAK_INVALID_IMAGE_TYPE
sahara protocol error
uploading image using sahara protocol failed
fish555 said:
Anybody know how to solve this problem?
/*invalid image type recieved*/
is_ack_succesfull : 1031 SAHARA_NAK_INVALID_IMAGE_TYPE
sahara protocol error
uploading image using sahara protocol failed
Click to expand...
Click to collapse
Its very possible that Windows security corrupted the Qfil and damaged this file, turn off antivirus, re-download Qfil and try again.
tsongming said:
Its very possible that Windows security corrupted the Qfil and damaged this file, turn off antivirus, re-download Qfil and try again.
Click to expand...
Click to collapse
Thanks for your answer
I turene off antivirus and brandmauer.
I think the problem must be in wrong image (i used kdz, img for d325 and my phone is 325f)
Also i red on forums that d325 may have two kind of processors.It's the reason why BoardDiag showed error
Anyone has 810 qfil ?
---------- Post added at 05:23 PM ---------- Previous post was at 05:19 PM ----------
Qualcomm 810 qfil which match with this methode?
leeco max x900
Hi,
I have bought a brand new LeTV (Leeco) Max 1 (x900). I installed twrp and tried to install custom rom. Unfortunately I didnt succeed and my phone is now only going into qualcomm 9008 mode. I have tried QFIL with the previous x800 service rom which supposedly puts it into a bootloop but you can still get it into fastboot mode. I have tried and tried but I constantly get the same sahara errors over and over. From what I have been reading, Qualcomms are unbrickable. So my question is where am I going wrong? The phone has a Qualcomm 810 in it. Do I need a specific file from LeEco that is currently unattainable? Please help. This is the flashest looking brick that I have ever owned...
fratziweru said:
Hey, i have a little problem and i would be grateful if someone would help me, my LeEco Le Max2 Bricked, the screen went blue , i turned it off and now it doesn't want to start at all or charge ( even the led is not functional)
I explored the forum and passed a few errors but i'm stuck at :
Total to be tansferd with <program> or <read> is 3.17 GB
22:18:04: INFO: Sending <configure>
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
22:18:04: {ERROR: XML not formed correctly. Expected a < character at loc 0}
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
22:18:04: {ERROR: 3. TAG not found or recognized}
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
22:18:04: {ERROR:
There is a chance your target is in SAHARA mode!!
There is a chance your target is in SAHARA mode!!
There is a chance your target is in SAHARA mode!!
This can mean
1. You forgot to send DeviceProgrammer first (i.e. QSaharaServer.exe -s 13rog_emmc_firehose_8994_lite.mbn)
2. OR, you did send DeviceProgrammer, but it has crashed and/or is not correct for this target
Regardless this program speaks FIREHOSE protocol and your target is speaking SAHARA protcol, so this will not work
}
Writing log to 'C:\Users\Aex\AppData\Roaming\Qualcomm\QFIL\port_trace.txt', might take a minute
Log is 'C:\Users\Aex\AppData\Roaming\Qualcomm\QFIL\port_trace.txt'
Download Fail:FireHose Fail FHLoader Failrocess fail
Finish Download
Thanks
Click to expand...
Click to collapse
fratziweru said:
Hey, i have a little problem and i would be grateful if someone would help me, my LeEco Le Max2 Bricked, the screen went blue , i turned it off and now it doesn't want to start at all or charge ( even the led is not functional)
I explored the forum and passed a few errors but i'm stuck at :
Total to be tansferd with <program> or <read> is 3.17 GB
22:18:04: INFO: Sending <configure>
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
22:18:04: {ERROR: XML not formed correctly. Expected a < character at loc 0}
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
22:18:04: {ERROR: 3. TAG not found or recognized}
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
22:18:04: {ERROR:
There is a chance your target is in SAHARA mode!!
There is a chance your target is in SAHARA mode!!
There is a chance your target is in SAHARA mode!!
This can mean
1. You forgot to send DeviceProgrammer first (i.e. QSaharaServer.exe -s 13rog_emmc_firehose_8994_lite.mbn)
2. OR, you did send DeviceProgrammer, but it has crashed and/or is not correct for this target
Regardless this program speaks FIREHOSE protocol and your target is speaking SAHARA protcol, so this will not work
}
Writing log to 'C:\Users\Aex\AppData\Roaming\Qualcomm\QFIL\port_trace.txt', might take a minute
Log is 'C:\Users\Aex\AppData\Roaming\Qualcomm\QFIL\port_trace.txt'
Download Fail:FireHose Fail FHLoader Failrocess fail
Finish Download
Thanks
Click to expand...
Click to collapse
This my be too late for you, but it can help people in the future with this same issue.
When using the QFIL program, you need to use the "prog_emmc_firehose_8994_lite.mbn" rather than the other .mbn (or elf) file as the program path, on my phone, I had 2 .elf files and use the wrong one, which caused me to have the same fault as you did. You must also use all program and patch files or you will get it to be in a state that it only gets to the point of the splash screen. The recovery/ bootloader is not available using the phones buttons and the device does not appear on the PC at all.
If somehow you got to that point. Leave your phone connected to the computer when it is stuck on the splash screen. In about 20 minutes ( yes, I know it is a long time.) the phone will reset with two options in recovery mode. The phone will also be picked up by the PC at this time.
Just enter cmd prompt in the adb file and enter "adb reboot edl" to bring your phone into edl mode. This will allow you to reinstall firmware using the QFIL program.
{
"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"
}
Evolution X 4.4 for the Galaxy Tab S3 LTE and Wifi [gts3lltexx, gts3lwifixx]
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, thermonuclear war, or
* you getting fired because the alarm app failed following these directions.
* YOU are choosing to make these modifications, and if
* you point your finger at me for messing up your device, I will laugh at you.
*/
Living, Breaking, Keep Evolving.
Evolution X is a flashable custom ROM to bring a true Pixel-feel to your Android Device at first glance, with many additional configurations at your disposal. We aim to provide frequent builds with monthly security patches from the latest AOSP sources!
- Team Evolution X -@joeyhuab (Founder & Lead Developer)
@peaktogoo (Project Manager)
@AnierinB (Project Specialist)
- Design -@ecnivtwelve (Lead Designer)
@MartonDev (Website Designer)
- Credits -@rorymc928
@Dobsgw
Evolution X Team
https://evolution-x.org/
Reach us on Twitter! @evolutionxROM
Themes
- 4 Statusbar Icon Styles
- 5 Lock Screen Clock Styles
- 6 System Icon Shapes
- 17 System Fonts
- Color Bucket
- Custom QS Header Images
- Pixel 2019 Wallpapers
- QS Opacity & Color Configs
- QS Backround Image Blur
- RGB Accent Picker
Statusbar
- 4G/LTE Icon Toggle
- 7 Battery Icon Styles
- 7 Custom VoLTE Icons
- Battery Percent Show/Hide Config
- Brightness Control
- Carrier Label Settings
- Clock Options
- Network Traffic Activity
- Rounded Corners Config
Notifications
- Blink Flashlight On Call
- Edge Lighting
- Force Close Notifications
- In Call Vibrations
- Kill App Button
- Notification light Config
Quick Settings
- Battery Percentage Configs
- Bottom Brightness Slider Toggle
- Custom QS Footer Text
- Custom QS Header Images
- Gaming Mode Quick Settings Tile
- QS Background Image Blur
- QS Opacity & Color Configs
- Quick Pulldown (Left/Right)
- Quick Settings Rows & Columns Customization
- Tile Titles Toggle
- Toggles To Hide Misc Icons
Power Menu
- Advanced Restart
- Airplane
- Flashlight
- Lock Down
- Logout
- Restart
- Screenshot
- Settings
- Users
- Visibility On Lockscreen Configs
Gestures
- AOSP Gestures
- Back Gesture Height Config
- Back Gesture Vibration Toggle
- Double Tap to Sleep Lockscreen
- Double Tap To Sleep Status Bar
- Screen Off Gestures
- Screen Off Power Button Torch
- Status Bar Brightness Control
- Swipe To Screenshot
- Toggle To Hide Back Gesture Icon
- Toggle To Hide Navbar Pill
Lockscreen
- Custom Clock & Date Fonts
- Fingerprint Authentication Vibration Toggle
- FOD Icon Picker
- FOD Pressed State Icons
- FOD Recognizing Animations
- Lock Icon Toggle
- Lock Screen Music Visualizer
- Lock Screen Media Artwork Configs
- Lock Screen Shortcuts
- Pocket Detection
- Pressed FOD Icon Picker
- Status bar visibility toggle
Navigation
- Invert Layout
- Navigation Bar Hide/Show Toggle
- Navigation Bar Tuner
Hardware Buttons
- Power Menu Customization
- Volume Rocker Cursor Control
- Volume Rocker Playback Control
- Volume Rocker Wake
Animations
- Disable Transition Animations
- ListView Animations
- QS Tile Animation Duration & Interpolator configs
- QS Tile Animations (Flip/Rotate)
- Screen Off Animations
- Scrolling Cache Configs
- System Animation Configs
Miscellaneous
- Accidental Wake Up Prevention
- Alarm Blocker
- Charging Animation
- Dashboard Condition/Suggestion Toggle
- Default USB Config
- Disable Device Identifier Restrictions
- Doze Settings
- Gaming Mode
- Legacy App Scaling
- Launch Music App On Headset Connection
- Screenshot Type (Full/Drag)
- Sensor Block Per Package
- Signature Spoofing Support
- Smart Charging
- Time In State Monitor
- Wakelock Blocker
- Wake On Charge
You tell me.
DO NOT FLASH GAPPS, ALREADY INCLUDED
First Time Install / Clean Flash1. Download the proper flashable ZIP for your device
2. Reboot to Recovery
3. Wipe Data/Cache/System
4. Format Data (Optional)
5. Flash the ROM
6. Reboot to System
7. Reboot to Recovery (Optional)
8. Flash Magisk (Optional)
9. Reboot to System and #KeepEvolving
Update / Dirty Flash
1. Reboot to Recovery
2. Download the proper flashable ZIP for your device
3. Reboot to Recovery (Optional)
4. Flash Magisk (Optional)
5. Flash the ROM
6. Reboot to System and #KeepEvolving
MEGA:
SM-T825: Download link is removed temporarily.
SM-T820: Download link is removed temporarily.
Android version: 10
Evolution version: 4.4 Undergrounds
Security patch level: June 5, 2020
I actually thought this Tab was dead. Thank you SO much. I'm currently downloading this ROM. Thanks!
666anoymous666 said:
I actually thought this Tab was dead. Thank you SO much. I'm currently downloading this ROM. Thanks!
Click to expand...
Click to collapse
Hello! Have you installed the firmware, because on my t-825 ERROR 7?
---------- Post added at 02:03 PM ---------- Previous post was at 02:02 PM ----------
Here is the error log
Iperation_start: 'Flashing'
Installing zip file '/external_sd/EvolutionX_4.4_gts3lltexx-10.0-20200602-1436-UNOFFICIAL.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
I:Update binary zip
Verifying package compatibility...
Package doesn't contain compatibility.zip entry
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment not used in updater.
SELinux: Loaded file_contexts
Target: Xiaomi/sagit/sagit:8.0.0/OPR1.170623.027/V9.2.3.0.OCAMIEK:user/release-keysTarget: Xiaomi/sagit/sagit:8.0.0/OPR1.170623.027/V9.2.3.0.OCAMIEK:user/release-keys
--------------------------------------------------------------------------------------------------------
______ __ __ _ _ __ ______ __ __ _ _ __
/ ____/ ______ / /_ __/ /_(_)___ ____ | |/ / / ____/ ______ / /_ __/ /_(_)___ ____ | |/ /
/ __/ | | / / __ \/ / / / / __/ / __ \/ __ \| / / __/ | | / / __ \/ / / / / __/ / __ \/ __ \| /
/ /___ | |/ / /_/ / / /_/ / /_/ / /_/ / / / / | / /___ | |/ / /_/ / / /_/ / /_/ / /_/ / / / / |
/_____/ |___/\____/_/\__,_/\__/_/\____/_/ /_/_/|_| /_____/ |___/\____/_/\__,_/\__/_/\____/_/ /_/_/|_|
by Team Evolution X by Team Evolution X
--------------------------------------------------------------------------------------------------------
Android version: 10 Android version: 10
Build id: QQ3A.200605.001 Build id: QQ3A.200605.001
Build date: 20200602-1436 Build date: 20200602-1436
Security patch: 2020-06-05 Security patch: 2020-06-05
Device: gts3lltexx Device: gts3lltexx
--------------------------------------------------------------------------------------------
Extracted file "/tmp/install/bin/backuptool.sh"
Extracted file "/tmp/install/bin/backuptool.functions"
Extracted 2 file(s)
Patching system image unconditionally...Patching system image unconditionally...
performing update
script aborted: package_extract_file(): no system.transfer.list in package
package_extract_file(): no system.transfer.list in package
error: 25
cause: 114
Updater process ended with ERROR: 7
I:Install took 0 second(s).
Error installing zip file '/external_sd/EvolutionX_4.4_gts3lltexx-10.0-20200602-1436-UNOFFICIAL.zip'
Updating partition details...
Iata backup size is 0MB, free: 24684MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
...done
vegych said:
Hello! Have you installed the firmware, because on my t-825 ERROR 7?
---------- Post added at 02:03 PM ---------- Previous post was at 02:02 PM ----------
Here is the error log
Iperation_start: 'Flashing'
Installing zip file '/external_sd/EvolutionX_4.4_gts3lltexx-10.0-20200602-1436-UNOFFICIAL.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
I:Update binary zip
Verifying package compatibility...
Package doesn't contain compatibility.zip entry
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment not used in updater.
SELinux: Loaded file_contexts
Target: Xiaomi/sagit/sagit:8.0.0/OPR1.170623.027/V9.2.3.0.OCAMIEK:user/release-keysTarget: Xiaomi/sagit/sagit:8.0.0/OPR1.170623.027/V9.2.3.0.OCAMIEK:user/release-keys
--------------------------------------------------------------------------------------------------------
______ __ __ _ _ __ ______ __ __ _ _ __
/ ____/ ______ / /_ __/ /_(_)___ ____ | |/ / / ____/ ______ / /_ __/ /_(_)___ ____ | |/ /
/ __/ | | / / __ \/ / / / / __/ / __ \/ __ \| / / __/ | | / / __ \/ / / / / __/ / __ \/ __ \| /
/ /___ | |/ / /_/ / / /_/ / /_/ / /_/ / / / / | / /___ | |/ / /_/ / / /_/ / /_/ / /_/ / / / / |
/_____/ |___/\____/_/\__,_/\__/_/\____/_/ /_/_/|_| /_____/ |___/\____/_/\__,_/\__/_/\____/_/ /_/_/|_|
by Team Evolution X by Team Evolution X
--------------------------------------------------------------------------------------------------------
Android version: 10 Android version: 10
Build id: QQ3A.200605.001 Build id: QQ3A.200605.001
Build date: 20200602-1436 Build date: 20200602-1436
Security patch: 2020-06-05 Security patch: 2020-06-05
Device: gts3lltexx Device: gts3lltexx
--------------------------------------------------------------------------------------------
Extracted file "/tmp/install/bin/backuptool.sh"
Extracted file "/tmp/install/bin/backuptool.functions"
Extracted 2 file(s)
Patching system image unconditionally...Patching system image unconditionally...
performing update
script aborted: package_extract_file(): no system.transfer.list in package
package_extract_file(): no system.transfer.list in package
error: 25
cause: 114
Updater process ended with ERROR: 7
I:Install took 0 second(s).
Error installing zip file '/external_sd/EvolutionX_4.4_gts3lltexx-10.0-20200602-1436-UNOFFICIAL.zip'
Updating partition details...
Iata backup size is 0MB, free: 24684MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
...done
Click to expand...
Click to collapse
Hello! No I still couldn't finish downloading cuz Mega is blocked in my area and the VPN I'm using is SLOW. And I have a couple of questions for you:
1) Which TWRP are you using? Ashyx's one or the one posted by the Evolution dev?
2) Is the current version of your ROM 9.0 or 8.0?
Edit: While looking at the log file I noticed it said that the target device was a Xiaomi. What on earth?
666anoymous666 said:
I have a couple of questions for you:
1) Which TWRP are you using? Ashyx's one or the one posted by the Evolution dev?
2) Is the current version of your ROM 9.0 or 8.0?
Click to expand...
Click to collapse
1)I tried to use different versions of twrp 3.2.1-1, 3.2.3-0 and version from Valera for treble firmware. Version from dev It is not installed on my T-825, it is not installed either through recovery or through odin
2)9.0
Hi guys!. I will try to see what I can do to fix this error during the installation, since I didn't have problems during the installation on my T825.
And I want to be clear before all: if you see like in the other post "Xiaomi Sagit" during the installation or in the settings app It's because this is a port from the latest Evolution X 4.4 made for Sagit (Xiaomi Mi 6) by the Evolution X team.
So this isn't alll my own work, and that's why I put people in the credits section.
I will appreciate more feedbacks to see if I am the only one with which this ROM works.
Thanks!.
PD: I realized the ROM I tested was a previous port that I abandoned few days ago, but don't worry; if I can I'll test the actual build today, hoping I will not be not busy.
666anoymous666 said:
Hello! No I still couldn't finish downloading cuz Mega is blocked in my area and the VPN I'm using is SLOW. And I have a couple of questions for you:
1) Which TWRP are you using? Ashyx's one or the one posted by the Evolution dev?
2) Is the current version of your ROM 9.0 or 8.0?
Edit: While looking at the log file I noticed it said that the target device was a Xiaomi. What on earth?
Click to expand...
Click to collapse
If you want I can upload my builds also on Google Drive .
First of all, I'm NOT an Evolution dev, I'm just a guy who had enough there were not a lot of ROMs for this tablet, since I have a T825 and I really wanted to have Evolution X, so I ported it from Sagit (the Xiaomi).
I'm a beginner so maybe I did something wrong, but in all cases I apologize all people if something is not working.
As I said I will test this build by myself today, so I will know what's not working.
vegych said:
Hello! Have you installed the firmware, because on my t-825 ERROR 7?
---------- Post added at 02:03 PM ---------- Previous post was at 02:02 PM ----------
Here is the error log
Iperation_start: 'Flashing'
Installing zip file '/external_sd/EvolutionX_4.4_gts3lltexx-10.0-20200602-1436-UNOFFICIAL.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
I:Update binary zip
Verifying package compatibility...
Package doesn't contain compatibility.zip entry
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment not used in updater.
SELinux: Loaded file_contexts
Target: Xiaomi/sagit/sagit:8.0.0/OPR1.170623.027/V9.2.3.0.OCAMIEK:user/release-keysTarget: Xiaomi/sagit/sagit:8.0.0/OPR1.170623.027/V9.2.3.0.OCAMIEK:user/release-keys
--------------------------------------------------------------------------------------------------------
______ __ __ _ _ __ ______ __ __ _ _ __
/ ____/ ______ / /_ __/ /_(_)___ ____ | |/ / / ____/ ______ / /_ __/ /_(_)___ ____ | |/ /
/ __/ | | / / __ \/ / / / / __/ / __ \/ __ \| / / __/ | | / / __ \/ / / / / __/ / __ \/ __ \| /
/ /___ | |/ / /_/ / / /_/ / /_/ / /_/ / / / / | / /___ | |/ / /_/ / / /_/ / /_/ / /_/ / / / / |
/_____/ |___/\____/_/\__,_/\__/_/\____/_/ /_/_/|_| /_____/ |___/\____/_/\__,_/\__/_/\____/_/ /_/_/|_|
by Team Evolution X by Team Evolution X
--------------------------------------------------------------------------------------------------------
Android version: 10 Android version: 10
Build id: QQ3A.200605.001 Build id: QQ3A.200605.001
Build date: 20200602-1436 Build date: 20200602-1436
Security patch: 2020-06-05 Security patch: 2020-06-05
Device: gts3lltexx Device: gts3lltexx
--------------------------------------------------------------------------------------------
Extracted file "/tmp/install/bin/backuptool.sh"
Extracted file "/tmp/install/bin/backuptool.functions"
Extracted 2 file(s)
Patching system image unconditionally...Patching system image unconditionally...
performing update
script aborted: package_extract_file(): no system.transfer.list in package
package_extract_file(): no system.transfer.list in package
error: 25
cause: 114
Updater process ended with ERROR: 7
I:Install took 0 second(s).
Error installing zip file '/external_sd/EvolutionX_4.4_gts3lltexx-10.0-20200602-1436-UNOFFICIAL.zip'
Updating partition details...
Iata backup size is 0MB, free: 24684MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
...done
Click to expand...
Click to collapse
JordanBleu said:
If you want I can upload my builds also on Google Drive .
First of all, I'm NOT an Evolution dev, I'm just a guy who had enough there were not a lot of ROMs for this tablet, since I have a T825 and I really wanted to have Evolution X, so I ported it from Sagit (the Xiaomi).
I'm a beginner so maybe I did something wrong, but in all cases I apologize all people if something is not working.
As I said I will test this build by myself today, so I will know what's not working.
Click to expand...
Click to collapse
Hello! First up I want to thank you for suggesting to host the ROM in Google Drive. But I have downloaded it already, so I have no need. Then I apologise for not understanding the post clearly. Also I know this is not the right post, but I installed your TWRP 3.3.1-1 or something like that and now i can't boot to recovery at ALL. Could you help a bit?
666anoymous666 said:
Hello! First up I want to thank you for suggesting to host the ROM in Google Drive. But I have downloaded it already, so I have no need. Then I apologise for not understanding the post clearly. Also I know this is not the right post, but I installed your TWRP 3.3.1-1 or something like that and now i can't boot to recovery at ALL. Could you help a bit?
Click to expand...
Click to collapse
Sure, what variant of this tablet do you have?.
I think for the moment until I discover the bug and upload another build, try flashing the ROM with the older TWRP from ashyx.
Sorry for all that problems, I'll try all my build today and see what happens.
Thank you for testing!
JordanBleu said:
Sure, what variant of this tablet do you have?.
I think for the moment until I discover the bug and upload another build, try flashing the ROM with the older TWRP from ashyx.
Sorry for all that problems, I'll try all my build today and see what happens.
Thank you for testing!
Click to expand...
Click to collapse
Hello once again! Yes my device is SM-T820. Your TWRP didn't install no matter what I tried, so that skipped. But now there is another problem. Like that other person mentioned, I also got the ERROR 7 message while flashing the ROM. Now the problem is I wiped everything and can't do anymore testing because my tab has no OS. So I'd suggest you find out what on earth went wrong. Thnx, Ishaq
666anoymous666 said:
Hello once again! Yes my device is SM-T820. Your TWRP didn't install no matter what I tried, so that skipped. But now there is another problem. Like that other person mentioned, I also got the ERROR 7 message while flashing the ROM. Now the problem is I wiped everything and can't do anymore testing because my tab has no OS. So I'd suggest you find out what on earth went wrong. Thnx, Ishaq
Click to expand...
Click to collapse
Sounds like he's working on the error 7 and fixing TWRP 3.3.1.
If you need your tablet to operate in the meantime, you should use ODIN to flash the most recent firmware for your region (can find on SAMMOBILE). This will give you the stock operating system and recovery. If you want to flash something stable (like tweaked ROM by rorymc28), you will need to reinstall the most recent TWRP from ODIN found here: https://forum.xda-developers.com/ga...recovery-twrp-3-1-0-1-samsung-galaxy-t3581359
My apologies for the problems that happened with this ROM.
I think it was too early and I should have tested it several times before posting it.
Now let me test my builds one by one, and until I find the problem with the famous "Error 7", download links are removed, sorry.
I will keep you informed when I will post a new build with this error fixed.
Alright, I'm uploading to my Google Drive the new build.
The problem was that some files were missing, but I fixed that.
Right now I didn't test the new build because my Tab S3 is charging (I am not lying, it is charging for real), when it will be charged, I will backup my important files and test by myself.
Here's the folder with both new builds, T825 and T820 (the last one is still uploading, it will take 7 more minutes).
https://drive.google.com/drive/folders/1O1zJvwCZR60suTAQ903v0EMnV3fEpuvW?usp=sharing
I hope this time it will work for you guys.
Edit: the new build for T820 is now uploaded!.
Please tell me if this time works.
Thanks!.
phone calls can be made in this rom ..?
bozkurtum said:
phone calls can be made in this rom ..?
Click to expand...
Click to collapse
I think it should work, I still didn't test it on my Tab S3 LTE.
Can you give us your feedback if you test the new build? Thank you!.
JordanBleu said:
I think it should work, I still didn't test it on my Tab S3 LTE.
Can you give us your feedback if you test the new build? Thank you!.
Click to expand...
Click to collapse
i want to install this rum on my samsung t827 tablet i asked for it
bozkurtum said:
i want to install this rum on my samsung t827 tablet i asked for it
Click to expand...
Click to collapse
Hello and yes you can, i can't guarantee the phone will work, but NORMALLY it should work.
You can test it.
For you, since there's no a specific build for your device, you have to choose the build called "gts3lltexx" in the SM-T825 folder in my Google Drive I posted before.
hello, I tried to install it on my device (t825), but it still shows the error:
"E1001: Failed to update system image.
Updater process ended with ERROR: 7"
Bakarios said:
hello, I tried to install it on my device (t825), but it still shows the error:
"E1001: Failed to update system image.
Updater process ended with ERROR: 7"
Click to expand...
Click to collapse
Can you send me the entire log please? Thanks.
rom not loading gives this error samsung s3 tab t827
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.