Database Info

QMOBILE NOIR A2 ROOT 100% working

aaj aap ko mein qmobile noir a2 ke root karna ka tarqa batao ga.is mein mere kafi mehnat lage ha so plz
first download this archive http://d-h.st/O9z
In order to root you QMobile Noir A2 , follow these steps.
1) Getting things read
a) Copy "CWM-SuperSU-v1.04.zip" to your noir a2 sdcard.
b) Install drivers from "MT65x3 USB VCOM drivers" folder.
2) now we will Install CWM recovery
a) Turn off your mobile (remove battery)
b) Open SP Flash tool, click "Scatter-loading" and select file "MT6573_Android_scatter.txt".
c) Make sure ONLY "RECOVERY" is checked in partition and "recovery.img" file is selected.now disconnect ur phone if it was connected to usb port.
d) Press "Download" button, and quickly reconnect your phone using a usb cable. It will start flashing the recovery.
Once it is done, you will see a notification and a Green Circle.
3) Gain root access
a) Boot into recovery by holding "volume +" and "volume -" and pressing the power key. and press volume up u will se cwm menu.
b) Select "recovery mode" from the options.
Here, it is recommended that you backup your entire system to sdcard. So that you have something to come back to,
incase you mess up.
c) In recovery menu, select "install zip from sdcard" -> "choose zip from sdcard" and select "CWM-SuperSU-
v1.04.zip" file from sdcard, go for YES option. Wait for the flash to complete.
d) Now select "reboot system now" option. Wait for the phone to reboot to normal mode.
YOU SHOULD NOW HAVE A ROOTED PHONE with SuperSU app installed, if you followed the steps correctly.
To backup, go to recovery select "backup and restore" -> "backup".
To restore, go to recovery select "backup and restore" -> "restore".
agar koe problem ho to zaror poche.ye sare procedure windows 7 32 bit par test hoa tha.is mein mere kafi mehnat
lage ha so plz thnx button ko zaror click shukryia.
after rooting ur noir a2 use titanuim backup to delete those useless system apps like tomcat and make space for
important things..
MORE DEVELOPMENT FOR NOIR A2 COMING SOON

Not working!
Bro I get this error after i click Download on Sp tools and attach my cell phone with a USB cable without the battery. I have followed each and every step clearly, I am using Windows 7 32Bit.
Please Help!

bilal bhai pehele apna phone factory settings par restore karo and usb debugging enable karo and phir drivers reinstall karo phir try karo..AND SP FLASH TOOL MEIN ONLY RECOVERY KE BOX KO TICK KARO US KE AGA CLICK KARO GE TO FILE BROWSER OPEN HO JAE GA WAHA SE MERE recovery.img select karo and phir flash karo,AND SP FLASH TOOL MEIN DOWNLOAD KA BUTTON PRESS KARNE SE PEHLE PHONE KO DISCONNECT KARDO USB SE PHIR DOWNLOAD PREES KARO JAB TIMER AYA GA THEN USB CABLE CONNECT KARO

mega_man said:
bilal bhai pehele apna phone factory settings par restore karo and usb debugging enable karo and phir drivers reinstall karo phir try karo..AND SP FLASH TOOL MEIN ONLY RECOVERY KE BOX KO TICK KARO US KE AGA CLICK KARO GE TO FILE BROWSER OPEN HO JAE GA WAHA SE MERE recovery.img select karo and phir flash karo,AND SP FLASH TOOL MEIN DOWNLOAD KA BUTTON PRESS KARNE SE PEHLE PHONE KO DISCONNECT KARDO USB SE PHIR DOWNLOAD PREES KARO JAB TIMER AYA GA THEN USB CABLE CONNECT KARO
Click to expand...
Click to collapse
Please use English on xda forum, not urdu or any other language....
I hope you understand

iamareebjamal said:
Please use English on xda forum, not urdu or any other language....
I hope you understand
Click to expand...
Click to collapse
If urdu is helping out others so this shouldn't matter what language you are using, there are tons of thread where French, German, Russian languages are being using, so he is just helping out some people leave him to help other on his way:angel:

_hito_ said:
If urdu is helping out others so this shouldn't matter what language you are using, there are tons of thread where French, German, Russian languages are being using, so he is just helping out some people leave him to help other on his way:angel:
Click to expand...
Click to collapse
XDA is not a region based community
If you tell something in English, it may help everybody and not only people who know hindi or urdu
Here, we tend to help each and every body.
You would know that it is obligatory to speak English if you have read the forum rules
And about other threads using languages other than English, you should tell them to use English instead of telling that everyone else should also speak in their regional languages.
If someone is having problem in understanding of English, then you may translate it if you want and know the language.
But if a person comes here and finds a problem and the solution is in hinglish, then he would not be able to know it
And also, hinglish can't be translated if you know, so please write in English
I hope you understand

Error while using this method / achive
I am getting error
EBOOT ERROR : (16008)
[Android Partition size changed!
[HINT] Partial images download error
mega_man said:
aaj aap ko mein qmobile noir a2 ke root karna ka tarqa batao ga.is mein mere kafi mehnat lage ha so plz
PLZ HELP ME...HOW I CAN FIX IT ...
THANKS
first download this archive http://d-h.st/O9z
In order to root you QMobile Noir A2 , follow these steps.
1) Getting things read
a) Copy "CWM-SuperSU-v1.04.zip" to your noir a2 sdcard.
b) Install drivers from "MT65x3 USB VCOM drivers" folder.
2) now we will Install CWM recovery
a) Turn off your mobile (remove battery)
b) Open SP Flash tool, click "Scatter-loading" and select file "MT6573_Android_scatter.txt".
c) Make sure ONLY "RECOVERY" is checked in partition and "recovery.img" file is selected.now disconnect ur phone if it was connected to usb port.
d) Press "Download" button, and quickly reconnect your phone using a usb cable. It will start flashing the recovery.
Once it is done, you will see a notification and a Green Circle.
3) Gain root access
a) Boot into recovery by holding "volume +" and "volume -" and pressing the power key. and press volume up u will se cwm menu.
b) Select "recovery mode" from the options.
Here, it is recommended that you backup your entire system to sdcard. So that you have something to come back to,
incase you mess up.
c) In recovery menu, select "install zip from sdcard" -> "choose zip from sdcard" and select "CWM-SuperSU-
v1.04.zip" file from sdcard, go for YES option. Wait for the flash to complete.
d) Now select "reboot system now" option. Wait for the phone to reboot to normal mode.
YOU SHOULD NOW HAVE A ROOTED PHONE with SuperSU app installed, if you followed the steps correctly.
To backup, go to recovery select "backup and restore" -> "backup".
To restore, go to recovery select "backup and restore" -> "restore".
agar koe problem ho to zaror poche.ye sare procedure windows 7 32 bit par test hoa tha.is mein mere kafi mehnat
lage ha so plz thnx button ko zaror click shukryia.
after rooting ur noir a2 use titanuim backup to delete those useless system apps like tomcat and make space for
important things..
MORE DEVELOPMENT FOR NOIR A2 COMING SOON
Click to expand...
Click to collapse

your qmobile noir a2 is giving that errror because it is v3 to check take the back cover of ur phone and if is there writtend V2 OR V3 if its V3 then i cannot help because this method is for V2 noir a2

iamareebjamal said:
XDA is not a region based community
If you tell something in English, it may help everybody and not only people who know hindi or urdu
Here, we tend to help each and every body.
You would know that it is obligatory to speak English if you have read the forum rules
And about other threads using languages other than English, you should tell them to use English instead of telling that everyone else should also speak in their regional languages.
If someone is having problem in understanding of English, then you may translate it if you want and know the language.
But if a person comes here and finds a problem and the solution is in hinglish, then he would not be able to know it
And also, hinglish can't be translated if you know, so please write in English
I hope you understand
Click to expand...
Click to collapse
racism everywhere

Does the said method also work for QMobile Bolt A2 Lite?

Twrp Recovery 3.0.2 and Root Zenfone 3 ZE552KL(Z012D)/ZE520KL(Z017D) nougat 7.0

Hi everybody!
Nougat 7.0 has just released for ZENFONE 3 ZE552KL(Z012D)/ZE520KL(Z017D) by Asus. I tried and installed successfully Twrp recovery and rooted it as well
Today, I would like to guide you how I did it
First of all, your device must be unlocked bootloader. You can find out it with following here : https://forum.xda-developers.com/zenfone-3/help/guide-how-to-root-zenfone-3-ze552kl-t3471524
- Download files and copy them to your phone:
+ Supersu : https://drive.google.com/file/d/0Bxzxv3DgqkRbTktiS3V5bGVNUlE/view?usp=sharing
+ Busy : https://drive.google.com/file/d/0Bxzxv3DgqkRbVWx6LTRPQjk3dk0/view?usp=sharing
+ Root : https://drive.google.com/file/d/0Bxzxv3DgqkRbN2RFSUVIY0kycm8/view?usp=sharing
+ No verity : https://drive.google.com/file/d/0Bxzxv3DgqkRbdW9UR2FnUXB2d0U/view?usp=sharing
1. Install TWRP recovery :
- Go Setting > Developer mode > turn on USB deburg
- Connect phone with PC and select transfer file mode
- Download file adb tool and extract it on PC (pass : tizen) : https://drive.google.com/file/d/0Bxzxv3DgqkRbUENWVzNvNkVwZVU/view?usp=sharing
- Hold Shift and mouse right click on bank in folder adb_tool, then select "Open command window here"
- Enter command : adb devices , then accept connecting on your device
- Enter next command : adb reboot bootloader. Your phone will automatically reboot in fastboot mode
- Do with suitable phone :
+ For ZE552KL(Z012D) : enter command "fastboot flash recovery twrp-3.0.2-Z012D.img"
+ For ZE520KL(Z017D) : enter command "fastboot flash recovery twrp-3.0.2-Z017D.img"
and wait for successfully notification
- Enter command : fastboot reboot reboot
- When your phone boot on screen of unlock bootloader, press volume up or down, then select Recovery
- Now you are in TWRP recovery
2. Root your device
- Swipe modified system
- Install > Select No verity file. Then select tab Reboot > Recovery. DO NOT MISS STEP, YOU PHONE WILL BE BOOTLOOP OR KEEP RED WARNING IN BOOTING
- Install > Select Supersu
- Install > Select Busy
- Install > Select Root
- Reboot your phone and enjoy root performent
Thank :
- @Chainfire for supersu
- @snowwolf725 for guide unlock bootloader
- @SuperR. for super kitchen
I hope You will get successfully
Thanks All
Note : Sorry for my bad English because I am from Vietnam

hey there, i have problem when i sign in to google at the fiirst time after boot up, it say i typed wrong password, but when i reset it, i need to wait 24 hours i cant do anything, anyone have solution here ?

Bác người việt hả

kuranzi said:
hey there, i have problem when i sign in to google at the fiirst time after boot up, it say i typed wrong password, but when i reset it, i need to wait 24 hours i cant do anything, anyone have solution here ?
Click to expand...
Click to collapse
Try this, it's ok for me.
https://www.youtube.com/watch?v=Ott8KCZc9-Y

kisipro9x said:
Bác người việt hả
Click to expand...
Click to collapse
Đúng rồi bác

thank you man. just bought zenfone 3 4gb ram 64gb model today and so far im loving it. and instantly received a 7.0 nougat update right after checking the system update. after playing around with marshmallow i decided to update to nougat (currently updating). i was worried that theres no solution to root the z3 nougat until i found this thread it turns out its possible haha. again thanks.

help???
Hi,
i made a big mistake when i tried to update so i use to wipe all my phone and re-install all: boot image, recovery image then install manualy the Nougat rom on my Z012dc.
it was unlock, root and twrp_ed with Marshmallow.
i guess my bootloader is still unlock, but i cant flash twrp.img like u show above...
do i have to re-unlock my bootloader and then follow ur tutorial
hope i'm clear enough, english is realy not my best langage ^^
edit: find why: i didnt flash the good twrp, now its ok, going to try to root
edit2: root and everything going fine, start twice

now my phone stuck on bootloop because i forgot to put the no verity file to my internal storage and install it. what should i do? how can i transfer the no verity file from my pc to my phone through the twrp????

w1040 said:
now my phone stuck on bootloop because i forgot to put the no verity file to my internal storage and install it. what should i do? how can i transfer the no verity file from my pc to my phone through the twrp????
Click to expand...
Click to collapse
Enter recovery, connect phone with pc, tranfer no verity file in your phone

cdanthien said:
Enter recovery, connect phone with pc, tranfer no verity file in your phone
Click to expand...
Click to collapse
how to transfer through recovery??? im on twrp right now but how?? im panic dude

w1040 said:
how to transfer through recovery??? im on twrp right now but how?? im panic dude
Click to expand...
Click to collapse
if you are in the recovery, go to mount, select microsd or sd then tap on enable/disable and your phone will appear on your pc, i did with a macbook pro and it works.
hope that help!

"it says my device is corrupt. it cant be trusted and may not work properly. your device will shutdown in 10 seconds" message everytime i want to boot my z3. OMG i just bought this phone and now im stuck on bootloop
---------- Post added at 07:33 AM ---------- Previous post was at 07:23 AM ----------
ok so i followed this step
- Swipe modified system
- Install > Select No verity file. Then select tab Reboot > Recovery. DO NOT MISS STEP, YOU PHONE WILL BE BOOTLOOP OR KEEP RED WARNING IN BOOTING
- Install > Select Supersu
- Install > Select Busy
- Install > Select Root
- Reboot your phone and enjoy root performent
but using the adb sideload and adbsideload testing.zip command using cmd. but i still cannot boot my device wtf??? ((

w1040 said:
"it says my device is corrupt. it cant be trusted and may not work properly. your device will shutdown in 10 seconds" message everytime i want to boot my z3. OMG i just bought this phone and now im stuck on bootloop
---------- Post added at 07:33 AM ---------- Previous post was at 07:23 AM ----------
ok so i followed this step
- Swipe modified system
- Install > Select No verity file. Then select tab Reboot > Recovery. DO NOT MISS STEP, YOU PHONE WILL BE BOOTLOOP OR KEEP RED WARNING IN BOOTING
- Install > Select Supersu
- Install > Select Busy
- Install > Select Root
- Reboot your phone and enjoy root performent
but using the adb sideload and adbsideload testing.zip command using cmd. but i still cannot boot my device wtf??? ((
Click to expand...
Click to collapse
When you see ".....may not work properly", press volume up or down, select recovery, you will be in twrp recovery.
Connect phone with pc. Open window, then copy no verity file in micro sd card. Look at recovery on your phone, install tab, select storage, micro sd card, then install no verity

cdanthien said:
When you see ".....may not work properly", press volume up or down, select recovery, you will be in twrp recovery.
Connect phone with pc. Open window, then copy no verity file in micro sd card. Look at recovery on your phone, install tab, select storage, micro sd card, then install no verity
Click to expand...
Click to collapse
ok so finally i can access my phone and copy the 4 files to my sd card and appeared on the install tab. then after that i did flashed 1 by 1 from noverity until rooted.zip then i reboot there still the message "may not work properly..." message therefore i still cannot boot my phone how?
---------- Post added at 08:04 AM ---------- Previous post was at 07:57 AM ----------
help. i lost 7 hours of sleep bcs of this and now it is 8:03 am and i still havent sleep fixing this issue.
mean while can someone link to a flashable zip of z3 firmware so i can just start over just incase theres no way to fix this?

w1040 said:
ok so finally i can access my phone and copy the 4 files to my sd card and appeared on the install tab. then after that i did flashed 1 by 1 from noverity until rooted.zip then i reboot there still the message "may not work properly..." message therefore i still cannot boot my phone how?
---------- Post added at 08:04 AM ---------- Previous post was at 07:57 AM ----------
help. i lost 7 hours of sleep bcs of this and now it is 8:03 am and i still havent sleep fixing this issue.
mean while can someone link to a flashable zip of z3 firmware so i can just start over just incase theres no way to fix this?
Click to expand...
Click to collapse
Enter recovery, select Wipe tab, format data. Reboot system

cdanthien said:
Đúng rồi bác
Click to expand...
Click to collapse
Hi bác cho m hoi là minh unlock bl rồi thì up lên nogat sao bác

kisipro9x said:
Hi bác cho m hoi là minh unlock bl rồi thì up lên nogat sao bác
Click to expand...
Click to collapse
Tải file rom Nougat (N) về chép vào thẻ nhớ
https://asusvn.com/threads/all-rom-...0kl-zu680kl-zc551kl-zc520tl-zc553kl.1108.html
Vào recovery, chọn update from sd card, chọn file rom. Chờ đến khi hoàn tất. Reboot

cdanthien said:
Tải file rom Nougat (N) về chép vào thẻ nhớ
https://asusvn.com/threads/all-rom-...0kl-zu680kl-zc551kl-zc520tl-zc553kl.1108.html
Vào recovery, chọn update from sd card, chọn file rom. Chờ đến khi hoàn tất. Reboot
Click to expand...
Click to collapse
Mà bây giờ m đang dùng twrp thì sao bac

kisipro9x said:
Mà bây giờ m đang dùng twrp thì sao bac
Click to expand...
Click to collapse
Vào đây :
https://forum.xda-developers.com/zenfone-3/help/guide-how-to-root-zenfone-3-ze552kl-t3471524
Đến dòng cuối ***g bài chủ thớt, tải về recovery.img. dùng adb flash lại recovery gốc rồi update như hướng dẫn

can you fix this?

HOMTOM S9 Plus - Development & Support

In order to keep this thread clean, please use this one to discuss about Development, Support or Software Updates.​
LATEST ROM:
To avoid any possible issues, don't forget to backup your NVRAM so that you won't risk losing your IMEI. How-to: http://www.anythingultimate.in/2015/11/how-to-backup-your-nvram-partition.html
V07 Stock (Android 7.0)
V07-20180308: https://drive.google.com/file/d/1kOJNybmTK2Je63eeaRXFeTANeQOZXki5/view
V07 Stock (Android 7.0) With TWRP Recovery & Root (Magisk)
V07-20180308: https://drive.google.com/open?id=1sTicAERau9SqfrYd0T7xduxMu4KwDyTw
PLEASE NOTE:: After Installation, Animation Speeds need to be adjusted as the Rom will appear slow. Click Settings>About Phone> Tap On Build Number 5 Times to Enable Developer Options. Go Back To Settings, Then Developer Options, Find 'Window Animation Scale, 'Transition Animation Scale' and 'Animator Duration Scale' and change the values to .5x
PREVIOUS ROMS:
V06 Stock (Android 7.0)
V06-20180203: https://drive.google.com/file/d/13ssQRzk2xGX0ZJ7xzU3KxoKjfk3q8T-D/view
V06 Stock (Android 7.0) With TWRP Recovery & Root (Magisk) (See Instructions Below)
V06-20180203: https://drive.google.com/open?id=1dmJ1ikZtfX9UF-TWcBugutg0RvvoZJtQ
V05 Stock (Android 7.0)
V05-20180131: http://www.mediafire.com/file/dndq73fpuen9lc4/PZ0162+-S9+PLUS+V801_HOMTOM_S9_V05_20180131-%E5%8D%87%E7%BA%A7%E5%8C%85.rar
V05 Stock (Android 7.0) With TWRP Recovery & Root (Magisk) (See Instructions Below)
V05-20180131: https://drive.google.com/open?id=1L7KMcg0gSBfD55VvtSaGN_fh1uNWq93a
V04 Stock (Android 7.0):
V04-20171201: https://drive.google.com/file/d/1jHnS8mFnFImhlYtHgPu7ZLZt-t6F_-6f/view
V04 Stock (Android 7.0) With TWRP Recovery & Root (Magisk) (See Instructions Below)
V04-20171201: https://drive.google.com/open?id=1cb2lPeBUWbW99kdciE0G6sc0_tXFECW6
DRIVERS, TOOLS & FIXES
Mediatek Drivers:
https://mega.nz/#!YRt1CRzA!wligaKAyJHbMIO3GWXfM9Zhmuh8OXddE6WY0qNeTluc
Latest SP Flash Tool:
https://mega.nz/#F!dYUm0TbB!SWeMLb5Wu1NbRzTPQ8-s_A
Universal Safetynet Fix: (Only For Versions V04-V06)
https://drive.google.com/open?id=1vUJlgZaJlCzHCS2uU6cHW771CiXozxzm
ADB Install:
See Here: https://forum.xda-developers.com/showthread.php?t=2588979
UNLOCKING THE BOOTLOADER
Before proceeding with flashing ANY Rom through SP Tools, You will need to unlock the Bootloader. Make sure you install ADB first and follow these instructions provided by Oxofrmbl, Thank you Oxo
1) On the phone go to developer options and tick oem unlock and USB debugging
2) Connect device (Switched On)
3) Open adb console and Type "adb devices"
4) On the phone it should ask for permission, give permission
5) Then Type "adb reboot bootloader"
6) Wait for fast Boot Mode and then type "fastboot oem unlock"
7) On phone it's Asking if you really want and press the key for yes.
Now it should unlock the bootloader
Click to expand...
Click to collapse
INSTRUCTIONS TO INSTALL ALL MODDED VERSIONS WITH TWRP & ROOT:
Disclaimer:
I am NOT a developer and most likely will never be one. If you decide to follow these instructions, you agree that I will NOT be held responsible for any Bricked/Blown up device resulting from these instructions. I have not done anything to the Stock Rom except adding the Recovery & Magisk (Root) and this worked on my device. This method is the easiest way of having root & Twrp recovery on your phone, it took me over 3-4 hours to do it the hard way through ADB as never used it before. I have done this to save you the trouble....Gstar35
Instructions:
Please Download the following (Links Above):
Mediatek Drivers (Install Them)
SP Tools
Either V04, V05, V06 OR V07 Stock Rom With TWRP & Root (Magisk)
Universal Safetynet Fix (Only For Versions V04-V06)
Before Proceeding, Double check in your Developer Settings that USB debugging is ticked, Switch off phone and don't connect it to the computer yet.
1) Unzip the Modded Stock Rom to your desktop (You should just have a folder with the V04, V05, V06 or V07 Rom inside)
2) Start SP Tools (Run as Administrator)
3) Click Choose on Scatter Loading File, browse to the Modded Rom Folder on desktop and click MT6750_Android_scatter.text and it will load. If Download-Agent is blank, click choose and navigate to the SP Tool Folder and click MTK_AllInOne_DA.bin to load.
4) Make sure it's says 'Download only' in the drop down bar and that all files are checked.
5) Press 'Download' at the top and connect your phone (off) to your computer. Wait while it flashes until a green box comes up with a tick, unplug phone, Reboot. You should have a working stock rom with Magisk core files and Twrp Recovery (Phone off, Press Vol+ and the power button, choose Recovery in options to boot to Twrp recovery if needed.
Now...with phone on, Download & Install Magisk Manager from the following thread...https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Once installed, open and it should say Latest Version V16.0 & Installed Version 16.0 green ticked, on tapping the 'Start Safetynet Check', both will be red and fail, so we need to sort that out.... Click Install at bottom & Install again, Click the option Direct Install and follow the instructions to the phone reboots. If You've flashed V07, You're All Done.....:good:, If not, proceed to the next step below......
PLEASE NOTE: If you've installed Version V04-V06, Follow The Next Step To Pass All Safetynet Checks On Magisk...
After rebooting, put the Safetynet Fix file on the root of the phone by connecting your phone to computer. Once transferred, turn phone off & reboot to recovery (use instructions above to boot to recovery or download a Quick boot app of Playstore). Install the Safetynet Fix.zip through recovery and then 'Wipe Cache/dalvik' then reboot.
All Done, Your phone should be now rooted and pass all the safetynet checks. I did try unpacking the System.img to try include Magisk Manager and maybe some other things like Adaway etc into the Rom but not read up yet on repacking the files, so I got a bit more learning to do yet, but for now, this will do you.
Extras (Root-Only):
Customization
- Xposed Framework: http://forum.xda-developers.com/showthread.php?t=3034811​
Useful Third-Party Apps:
Battery Life
- Amplify: https://play.google.com/store/apps/details?id=com.ryansteckler.nlpunbounce&hl=en
- Greenify: https://play.google.com/store/apps/details?id=com.oasisfeng.greenify&hl=en​
XDA:DevDB Information
HOMTOM S9 Plus - Development & Support, ROM for the Android General
Contributors
Alberto96, Gstar35
ROM OS Version: 7.x Nougat
Version Information
Status: Testing
Created 2018-03-06
Last Updated 2018-03-22

Aggressiv Doze and partially the WakeUp Tracking and Cut-Off of Greenify can also get to work by giving some rights from PC with adb.
https://greenify.uservoice.com/know...o-grant-permissions-required-by-some-features
(because Greenify is listed under Root-Only, I thought I Could mention this)

Custom ROM is needed, with attention to poor wi-fi and improved fingerprint recognition. Any idea when twrp will be available?

Rooting the S9
hello,
i Rooted my s9 plus,, but i did it with some support of XN logo developers.. and their you can find ther TWRP what you need..
Their is no other one trust me.. i searched and tried alot for 3,5 weeks and finally their it was.. XN logo.. my hero's
I have a question.. who can tell me if their is a custom rom from a other developer, because i missing some feartures and that's pretty anoying..

AngelOffDarkness said:
hello,
i tooted my s9 plus,, but i did it with some support of XN logo developers.. and their you can find ther TWRP what you need..
Their is no other one trust me.. i searched and tried alot for 3,5 weeks and finally their it was.. XN logo.. my hero's
I have a question.. who can tell me if their is a custom rom from a other developer, because i missing some feartures and that's pretty anoying..
Click to expand...
Click to collapse
Could you give me link?

Oxofrmbl said:
Could you give me link?
Click to expand...
Click to collapse
Hi Oxofrmbl, I think he means member XN logo on this other thread..
https://forum.xda-developers.com/android/software/twrp-porter-maker-mediatek-mt67xx-32-t3681861
I desperately want to root this device but I'm still reading up on the various tools etc before diving in to do it as never done mtk devices before, just Samsung phones. Has anyone else tried the above method and it worked?

Gstar35 said:
Hi Oxofrmbl, I think he means member XN logo on this other thread..
https://forum.xda-developers.com/android/software/twrp-porter-maker-mediatek-mt67xx-32-t3681861
I desperately want to root this device but I'm still reading up on the various tools etc before diving in to do it as never done mtk devices before, just Samsung phones. Has anyone else tried the above method and it worked?
Click to expand...
Click to collapse
Thanks. I already, found this thread, but had no time to try porting it myself. I have no experience in porting or developing something.
I want root too and hope someone is working on twrp, because I dont know if I will be successfully and first I have to find time to try
Is adaptive brightness working for anyone?

Gstar35 said:
Hi Oxofrmbl, I think he means member XN logo on this other thread..
https://forum.xda-developers.com/android/software/twrp-porter-maker-mediatek-mt67xx-32-t3681861
I desperately want to root this device but I'm still reading up on the various tools etc before diving in to do it as never done mtk devices before, just Samsung phones. Has anyone else tried the above method and it worked?
Click to expand...
Click to collapse
i used the XN because thats the only one that will work fine.. Take this link
https://androidfilehost.com/?fid=889964283620754855 or this one https://androidfilehost.com/?w=files&flid=220042
their is a file called TWRP porter from mediatek .. that is the one you need
well i can tell you all its not easy but i will tell ya.. you need to unlock the oem first.. their are alot of tutotorials of how to do this..
PUT THE SUPERSU ON YOUR SD CARD BEFORE ROOTING
than get the imagekitchen of this link.. and watch the video too... very important..( its a you tube video and the link is with the video)
https://www.youtube.com/watch?v=rFnG7fso9HE
and than you need the flashtool from above..... take the last version of the three..
their are alot of video's on you tube and i watched a alot of them.. and this was the biggest puzzle but it works like this
( if Xda allows me to make a tutorial i would make one but i am still a noobie.. they say )
if you need an answer on something dn't mind to ask i will try too help ya out..

AngelOffDarkness said:
i used the XN because thats the only one that will work fine.. Take this link
https://androidfilehost.com/?w=profile&uid=817550096634800749
their is a file called TWRP porter from mediatek .. that is the one you need
well i can tell you all its not easy but i will tell ya.. you need to unlock the oem first.. their are alot of tutotorials of how to do this..
PUT THE SUPERSU ON YOUR SD CARD BEFORE ROOTING
than get the imagekitchen of this link.. and watch the video too... very important..( its a you tube video and the link is with the video)
and than you need the flashtool from above..... take the last version of the three..
their are alot of video's on you tube and i watched a alot of them.. and this was the biggest puzzle but it works like this
( if Xda allows me to make a tutorial i would make one but i am still a noobie.. they say )
if you need an answer on something dn't mind to ask i will try too help ya out..
Click to expand...
Click to collapse
If you already did a Port that's working, Could you upload twrp.img (or the file we need to Flash) so we can use this?

On 4pda.ru there is twrp

Amazing, i can install super user and TWRP on my homtom S9, xposed can be runing, lol
Gửi từ S9 Plus của tôi bằng cách sử dụng Tapatalk

Gstar35 said:
Hi Oxofrmbl, I think he means member XN logo on this other thread..
https://forum.xda-developers.com/android/software/twrp-porter-maker-mediatek-mt67xx-32-t3681861
I desperately want to root this device but I'm still reading up on the various tools etc before diving in to do it as never done mtk devices before, just Samsung phones. Has anyone else tried the above method and it worked?
Click to expand...
Click to collapse
After some tries I was not able to get a working twrp but you can root with magisk. You just have to:
Install magisk Manager
Get the stock Boot IMG and copy to phone storage
Open Magisk Manager and click on install and then Patch Boot img
Choose the copied Boot IMG and some Text pops up
When it finished then you have a patched Image inside Magisk Manager folder on internal storage
Now copy patched IMG to Computer, unlock Bootloader and Flash Boot.img with adb and fastboot (maybe Flash Tool but I diddnt use it so I dont know)
Then restart and you will have Magisk Working (maybe install AGAIN but directly from app after all. I had to Do so to get it working properly with modules)

Oxofrmbl said:
After some tries I was not able to get a working twrp but you can root with magisk. You just have to:
Install magisk Manager
Get the stock Boot IMG and copy to phone storage
Open Magisk Manager and click on install and then Patch Boot img
Choose the copied Boot IMG and some Text pops up
War Teil finished then you have a patched Image inside Magisk Manager folder on internal storage
Now copy back to Computer, unlock Bootloader and Flash Boot.img with adb and fastboot (maybe Flash Tool but I diddnt use it so I dont know)
Then restart and you will have Magisk Working (maybe install AGAIN but directly from app after all. I had to Do so to get it working properly with modules)
Click to expand...
Click to collapse
Many Thanks, I'll give it a try later on. I can live with Magisk. I'll let you know later how I get on

Oxofrmbl said:
After some tries I was not able to get a working twrp but you can root with magisk. You just have to:
Install magisk Manager
Get the stock Boot IMG and copy to phone storage
Open Magisk Manager and click on install and then Patch Boot img
Choose the copied Boot IMG and some Text pops up
When it finished then you have a patched Image inside Magisk Manager folder on internal storage
Now copy patched IMG to Computer, unlock Bootloader and Flash Boot.img with adb and fastboot (maybe Flash Tool but I diddnt use it so I dont know)
Then restart and you will have Magisk Working (maybe install AGAIN but directly from app after all. I had to Do so to get it working properly with modules)
Click to expand...
Click to collapse
You're a legend..after trying for 3 hours & a lot of reading how to use/set up adb, I've managed to install Magisk. Only thing is, CTS profile failed in safetynet check. Does this matter?
I pulled the boot.img from the stock ROM and patched that & flashed, but I think it locked the bootloader again as the option to unlock has come back up in developer options. Will having a locked bootloader matter with Magisk?

Gstar35 said:
You're a legend..after trying for 3 hours & a lot of reading how to use/set up adb, I've managed to install Magisk. Only thing is, CTS profile failed in safetynet check. Does this matter?
I pulled the boot.img from the stock ROM and patched that & flashed, but I think it locked the bootloader again as the option to unlock has come back up in developer options. Will having a locked bootloader matter with Magisk?
Click to expand...
Click to collapse
I dont know if the locked bootloader matters. My bootloader stayed unlocked. I also have the failed cts Profile but diddnt find a Solution yet. But i diddnt have Problems with some apps not showing in play store so I dont care about this at the moment.

Hi all
I rooted my device, and I want to share my way as my rooted my device, maybe someone want its
1. Unlock the phone, tap in developers OEM, you can fine the homtom s8 toolkit for root this device.
2. Fine the TWRP 3.0.0 for mt6750t flash using flashify on GG play
Gửi từ Redmi Note 4 của tôi bằng cách sử dụng Tapatalk

duc501613 said:
Hi all
I rooted my device, and I want to share my way as my rooted my device, maybe someone want its
1. Unlock the phone, tap in developers OEM, you can fine the homtom s8 toolkit for root this device.
2. Fine the TWRP 3.0.0 for mt6750t flash using flashify on GG play
Gửi từ Redmi Note 4 của tôi bằng cách sử dụng Tapatalk
Click to expand...
Click to collapse
Some pics
{
"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"
}
Gửi từ Redmi Note 4 của tôi bằng cách sử dụng Tapatalk

So after getting root access through the patched Boot.img I was able to Flash this twrp successfully with flashify
https://drive.google.com/file/d/188XNAXMgKogGSfqbf_SOBDzk8drSCQO2/view?usp=drivesdk

Oxofrmbl said:
So after fettig root access through the patched Boot.img I was able to Flash this twrp successfully with flashify
https://drive.google.com/file/d/188XNAXMgKogGSfqbf_SOBDzk8drSCQO2/view?usp=drivesdk
Click to expand...
Click to collapse
Thanks Oxofrmbl, thanks to everyone for getting us this far.
Does anyone know, what partitions need to be checked for a full backup that can be flashed back in case of boot loop etc? System, data & boot are already checked but there is many partitions listed. Does any of the others need to be checked?

Hello again, I Flashed the safety net fix for magisk and no I have full safety net
https://forum.xda-developers.com/showpost.php?p=73432221&postcount=1075
If you want, you can try, I'm not sure if it Was the only Thing I needed, because I did some other Changes, but I think it should work

[FORMAT ALL + DOWNLOAD] [NOKIA 3] [Auth file need in Sp flash tool] -How to unbrick N

Here we are discussing about Nokia 3 [TA-1020, TA-1028, TA-1032, TA-1038] vibrate only problem after flashing Stock ROM through Sp flash tool with [Format all + Download] mode & the tool need Auth file to reflash the firmware.
I found a condition of Format all + Download in Nokia 3 [NE1]
1st If you "Downgrading" your device with Format all + Download [Ex: Android 9.0 to Android 7.1 or 8.0, 8.1] = May be bricked & needed "Auth file for Unbrick"
2nd If you "Upgrade" your device with Format all + Download [Ex: Android 7.0,7.1,8.0,8.1 to Android 9.0] = Device will successfully flash with IMEI, bt address,WiFi address & SN losses
In my case I "Downgraded" my device with Download only mode in Miracle Thunder with "Android 8.0" version device got bricked [Vibrate only] then I upgrade my device with 5120 build & "Format all + Download" mode = Device flashed successfully with losses of IMEI, bt address, WiFi address i.e Nvram
So if someone unfortunately flash their device with [Format all + Download] & they now need help to unbrick.
Maybe I can help to unbrick by flashing through Official flashing tool & m not sure that this will workout or not.
But theoretically it works out, So I need to check practically ask me for help in telegram.
NOTE: Flashing will be done remotely.
{Mod edit}
Thanks ? || Hit the Like button if it's helps to you.

.

Good job

CRUECY said:
Here we are discussing about Nokia 3 [TA-1020, TA-1028, TA-1032, TA-1038] vibrate only problem after flashing Stock ROM through Sp flash tool with [Format all + Download] mode & the tool need Auth file to reflash the firmware.
I found a condition of Format all + Download in Nokia 3 [NE1]
1st If you "Downgrading" your device with Format all + Download [Ex: Android 9.0 to Android 7.1 or 8.0, 8.1] = May be bricked & needed "Auth file for Unbrick"
2nd If you "Upgrade" your device with Format all + Download [Ex: Android 7.0,7.1,8.0,8.1 to Android 9.0] = Device will successfully flash with IMEI, bt address,WiFi address & SN losses
In my case I "Downgraded" my device with Download only mode in Miracle Thunder with "Android 8.0" version device got bricked [Vibrate only] then I upgrade my device with 5120 build & "Format all + Download" mode = Device flashed successfully with losses of IMEI, bt address, WiFi address i.e Nvram
So if someone unfortunately flash their device with [Format all + Download] & they now need help to unbrick.
Maybe I can help to unbrick by flashing through Official flashing tool & m not sure that this will workout or not.
But theoretically it works out, So I need to check practically ask me for help in telegram.
NOTE: Flashing will be done remotely.
{Mod edit}
Thanks ? || Hit the Like button if it's helps to you.
Click to expand...
Click to collapse
Help me the authentication file nokia 3 ta-1032 my phone is now dead after formart.

cjoybin said:
Help me the authentication file nokia 3 ta-1032 my phone is now dead after formart
Click to expand...
Click to collapse
Start a conversation in Xda

Giúp mình file xác thực nokia 3 ta-1032 với, máy mình hiện đã chết sau khi formart. hiện cổng com nhưng flash rom cần file safe
Translation by Moderation
Help me with nokia 3 authentication file ta-1032, my computer is now dead after formart. shows com port but flash rom needs safe file
Click to expand...
Click to collapse

[Guide - HOW TO] Recover LG G7 (or other newer LG phones) from EDL or 9008 mode.

****** Unbrick all LG G7 models ******
********** This guide has updated into two methods ********** ​
(i). Recover from any boot problem to system or download mode.(which is defined below)
This technique have been very useful to me for fixing my device and there is no any particular guide to fix brick device easily. That's why it is a must to share.
* As long as you can access EDL(9008) mode in your device you can fix your bricked device *
There are so many developers online if you can find who claim to fix or unbrick your bricked device by charging a hefty amount even after that you can not trust them.
****** I am here just to help you so if you want you can donate to me on paypal ******​
This guide has been compiled to fix all the phones which are in bricked state and completely dead state as long as you can access EDL mode(which is a Qualcomm's hidden flashing mode bult into hardware) you are able to fix your phones.
This guide applies to all the following problems :
Boot loop.
Fastboot boot loop(looping in fastboot).
Stuck at LG logo.
No recovery mode.
No fastboot mode.
Red triangle(security error).
"Press key to shut" message displays.
Seems like No sign of life.
And when connects to PC :
QHSUSB BULK or QLOADER or something like that when connects to PC or red LED.
Why are you facing this problem??
Downgrading android version of your phone.
Flashing wrong recovery image.
Flashing wrong firmware/ROM.
Flashing wrong bootloader/fastboot image.
While playing with your phone just for fun.
And many more....
Tools required :
- Qualcomm USB drivers. https://mega.nz/file/YAVhFIiC#nF-cChZklhcsxMHk24GhsB6rlE119erQqmXuBu21c6c
- LG mobile drivers. https://mega.nz/file/4UU3RSJb#iJu32uFbPsSrhIPoVr-BS1f2RqHnqL95lePDhDnK7NY
- LGUP tool lab version and LGUP common dll. https://mega.nz/file/MJdjxCqb#THo7EpmCqFUNa5VHMQcWI5D6M4QcR5p2vhQ77le0Gzo
- LG V35 abl image. https://mega.nz/file/wBV3UaQK#G0bF9gYz9Jb8FjdJsCAP0wmIOSqHrOFUjvUiPOsj91Q
- LG firmware extractor. https://mega.nz/file/oZMzGS6Q#JmYlsH9YgU_CmR5Ra0gjIOg_4S6fNVFPgl3UV0BRz0s
- KDZ tools. https://mega.nz/file/hJNVWAyY#KL8dypxmDXOJ3I9njzQW2TYE-ZgrHaiwnmenNbBcGRs
- QFIL tool. https://mega.nz/file/4AdjXCAS#tWf6XUYO3OxHjZ_XDJZopOtQpVkggW2170QIKDW0JK8
- Snapdragon 845 UFS firehose. https://mega.nz/file/8Zk0AAJQ#-WBO38OBXo6TnykCoOaoXeV2zBxHaUyoq3sR6lmFTtQ
- ADB tool. https://mega.nz/file/URtWmAxZ#TRNwkp9ZQw4BG1we2cxu623fT-6O6XJsBcylNevSF0g
- Stock f/w KDZ for your particuar device no less than last working andriod and build version.
- Knowledge how to boot into EDL (without shorting test pin it can fuse device board).
* Steps :
Step 1 : uninstall all the phone related drivers and restart PC.
Step 2 : to successfully install drivers and software follow below guide -
a. open commant prompt with admin rights run these commands so windows can allow to install driver properly.
- bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
- bcdedit.exe -set TESTSIGNING ON
(these will disable driver signature enforcement and put windows into test mode)
and restart
c. install Qualcomm drivers
d. install LG mobile drivers
e. install QPST
f. install LGUP lab version and place LGUP_Common.dll in C:\Program Files (x86)\LG Electronics\LGUP\model\common\LGUP_Common.dll and restart PC
*** When you boot your phone in download mode and instead it goes into fastboot then you should first open LGUP and then connect phone in download mode because I as experienced this time somehow LGUP forces the phone to stay in download mode rather than switching to fastboot ***
(if thuis works proceed to step 9 else not then step 3)
Step 3 : open LG firmware extract and click open in KDZ row and select downloaded firmware kdz and let it load then check G710xx something from list and click extract if there is any error in log then your kdz file is corrupted, if success then it will produce a DZ file and now in DZ row click open and select DZ file now tool will show you a long list, now select all the items and extract. This will produce so many files in LG firmware extractor folder.
Step 4 : place your kdz file in KDZ tools folder and select OneKeyExtraction.bat type Y, it will produce a dz file and several img files in a folder named as your firmware KDZ's name. copy boot_a.img , abl_a.img , laf_a.img to adb folder for fastboot flashing.
Step 5 : open QFIL from it's installation location and check build type to flat build and in programm file select prog_ufs_firehose_Sdm845_lge.elf file and in lower right corner select storage type to UFS.
Step 6 : connect your device to PC and boot into EDL mode by
a. if it is in any ON condition : POWER button + VOLUME DOWN and prepare to press VOLUME UP repeatedly as soon as phone switches off
b. if it is in dead condition : connecting to PC automatically boot into EDL mode.
if phone is connected in EDL mode now Device manager must show a device under ports tree somehting named as Qualcom HS-USB QLOADER 9008(Com_X)
* if you have bricked your device then I assume you already know how to boot into EDL mode.
Step 7 : now in QFIL select port and select your device, select Tools from QFIL toolbar and select Partition Manger, in warning window ckick OK if you've selected right 845's firehose elf file and after success it must show a list of many partions of your phone.
flashing : it's time for flashing.
*Note: select all the image files one by one in Lg firmware extract folder by typing name in file name control like as showed in screenshot Files_location.jpg.
{
"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"
}
it will take patience because it's a manual one, order must be followed coz tha's the thing that matters...
- find select and right click on "xbl_a" then manage partition data and select load then select "xbl.elf_6"
- find select and right click on "xbl_config_a" then manage partition data and select load then select "xbl_config.ebl_902"
- find select and right click on "xbl_b" then manage partition data and select load then select "xbl.elf_6"
- find select and right click on "xbl_config_b" then manage partition data and select load then select "xbl_config.ebl_902"
- find select and right click on "tz_a" then manage partition data and select load then select "tz.mbn_134"
- find select and right click on "hyp_a" then manage partition data and select load then select "hyp.mbn_646"
- find select and right click on "boot_a" then manage partition data and select load then select "boot.img_163830"
- find select and right click on "cmnlib_a" then manage partition data and select load then select "cmnlib.mbn_81670"
- find select and right click on "cmnlib64_a" then manage partition data and select load then select "cmnlib64.mbn_81798"
- find select and right click on "boot_b" then manage partition data and select load then select "boot.img_163830"
- find select and right click on "cmnlib_b" then manage partition data and select load then select "cmnlib.mbn_81670"
- find select and right click on "cmnlib64_b" then manage partition data and select load then select "cmnlib64.mbn_81798"
- find select and right click on "abl_a" then manage partition data and select load then select "V35abl.img"
- find select and right click on "abl_b" then manage partition data and select load then select "V35abl.img"
- find select and right click on "raw_Resources_a" then manage partition data and select load then select "raw_resources.img_194918"
- find select and right click on "tz_b" then manage partition data and select load then select "tz.mbn_134"
- find select and right click on "hyp_b" then manage partition data and select load then select "hyp.mbn_646"
- find select and right click on "laf_a" then manage partition data and select load then select "laf.img_81990"
- find select and right click on "laf_b" then manage partition data and select load then select "laf.img_81990"
close partition manager and let it restart device into EDL again.
Step 8 : boot your device in fasboot which is currently in EDL mode, to do so press Power + Volume down button and ready to leave Power as soon as phone restart while keep pressing Volume down
a. open command prompt in adb folder and verify device connectivity by
fastboot devices
* it must show a device something like LMV35EAWx.
b. perform these commands, order must be followed coz tha's the thing that matters:
fastboot erase boot
fastboot erase boot_a
fastboot erase boot_b
fastboot erase abl
fastboot erase abl_a
fastboot erase abl_b
fastboot erase laf
fastboot erase laf_a
fastboot erase laf_b
fastboot flash boot boot_a.img
fastboot flash boot_b boot_a.img
fastboot flash boot_a boot_a.img
fastboot flash abl abl_a.img
fastboot flash abl_b abl_a.img
fastboot flash abl_a abl_a.img
fastboot flash laf laf_a.img
fastboot flash laf_b laf_a.img
fastboot flash laf_a laf_a.img
and let your device as it is in fastboot.
we already flashed these partions in EDL mode and flashing in fastboot confirms that partitions do not get overwritten.
Step 9 : open LGUP and somehow proceed to flashing window, where you'll find device list option and many flashing options and a firmware list below, in flashing options select Refurbish and drop your KDZ file in firmware list and follow
a. now from phone's fastboot menu select restart and hold Volume Up now phone will show download mode bar and in few seconds LGUP will recognise your device in list same as above screenshot.
b. flash you KDZ and let your device boot into system.
Now you have a fully working device.
(ii). Recover from dead boot or no partitions list in QFIL partition manager.(hard brick)
I worked around G7's stock kdz and fortunately end up generating flashing file for a single partition but there are so many(100+) partitions and this single one took 1+ hour, which was hardly to arrange. You can imagine how much time 100+ partitions would take to be prepared.
Problem is I have a time consuming job so I can not waste my time on this unless you donate some money and get your device guaranteed recovered ASAP.
** UPDATE **
The guide I was working on, was more complex for noob to understand.
be patience I am slowly working with python scripts and a easy guide which will help you to flash empty device.
***use rawprogram and patch at your risk because it will result in 0 IMEI problem that causes no network signal but your device will be fixed***
And if anyone want to flash firmware through QFIL in that case I am also attaching G710EAW partition.xml , rawprograms.xml, patch.xml and flashable gpt_main & gpt_backup bin.
24.9 KB file on MEGA
mega.nz
Thanks for your support.
Questions are welcome.
Pay Sourabh Kumar using PayPal.Me
Go to paypal.me/SKumar7625 and type in the amount. Since it’s PayPal, it's easy and secure. Don’t have a PayPal account? No worries.
paypal.me
THANKS SO MUCH

Really good guide indeed, saved me from a hard brick a couple of months ago trying to unlock the bootloader.
Thanks for sharing!

isaac.caudillo said:
Really good guide indeed, saved me from a hard brick a couple of months ago trying to unlock the bootloader.
Thanks for sharing!
Click to expand...
Click to collapse
I am glad it worked for you.

Please, help me. My LG got Red Case, can not enter edl mode or download mode. What shouold i do?

yasir.asf said:
Please, help me. My LG got Red Case, can not enter edl mode or download mode. What shouold i do?
Click to expand...
Click to collapse
As far as I know Red Case is mostly a result of messing with your phone through EDL.
I have already explained how to boot in EDL :
(i). POWER button + VOLUME DOWN and prepare to press VOLUME UP repeatedly as soon as phone switches off
once your device connected in EDL mode Device manager must show a device under ports tree something named as Qualcom HS-USB QLOADER 9008(Com_X)

Hi! I'm from Cost Rica (G710EM20a)
Can you help me? I did all the steps and my phone stays on the logo and erasing ring.
I don't know what else to do...

sourabh7625 said:
As far as I know Red Case is mostly a result of messing with your phone through EDL.
I have already explained how to boot in EDL :
(i). POWER button + VOLUME DOWN and prepare to press repeatedly VOLUME UP as soon as phone switches off
once your device connected in EDL mode Device manager must show a device under ports tree something named as Qualcom HS-USB QLOADER 9008(Com_X)
Click to expand...
Click to collapse
Yeah I know, i read full the guide.
I can't enter EDL mode, but finally my phone turns on by flashing stock boot.img in fastboot mode.

Is there any possibility that you can restore partitions? As my device has nothing to select in Edl mode so I cannot restore it, meaning nothing is in the partition data but I do have full access to edl..

Xellas17 said:
Hi! I'm from Cost Rica (G710EM20a)
Can you help me? I did all the steps and my phone stays on the logo and erasing ring.
I don't know what else to do...
Click to expand...
Click to collapse
I am aware about this kinda bootloop, probably it's a result of flashing either different firmware or an older firmware and perhaps disconnecting or exit LGUP before letting the phone goes into system completely.
I suggest you to try flashing latest firmware available for your device through LGUP(select refurbish) and let it boot into system successfully and wait about 3-5 minutes to let LGUP finalizing flashing before disconnecting phone or exit LGUP.

yasir.asf said:
Yeah I know, i read full the guide.
I can't enter EDL mode, but finally my phone turns on by flashing stock boot.img in fastboot mode.
Click to expand...
Click to collapse
As I said if you bricked your phone you must have known how to connect in EDL mode(apart from EDL mode it's really hard to brick 845 phone).
well if you can flash through fastboot then flash fastboot section from step8 and then open LGUP first only after that connect phone in download mode, now it should be in list.
* When you boot your phone in download mode and instead it goes into fastboot then you should first open LGUP and then connect phone in download mode because I as experienced this time somehow LGUP forces the phone to stay in download mode rather than switching to fastboot.

Mr.Conkel said:
Is there any possibility that you can restore partitions? As my device has nothing to select in Edl mode so I cannot restore it, meaning nothing is in the partition data but I do have full access to edl..
Click to expand...
Click to collapse
Perhaps your device have a corrupt PrimaryGPT(which is a some kind of partitions table list container and it is absent in LG G7 firmware kdz)
Qfil rely on data read from device in partition manager but "flat and meta build" option is still there which forces the device to flash partitions regarding the information in rawprogram.xml and patch.xml files.
Unfortunately I don't have these files but I'll update you for an alternative solution.

sourabh7625 said:
Perhaps your device have a corrupt PrimaryGPT(which is a some kind of partitions table list container and it is absent in LG G7 firmware kdz)
Qfil rely on data read from device in partition manager but "flat and meta build" option is still there which forces the device to flash partitions regarding the information in rawprogram.xml and patch.xml files.
Unfortunately I don't have these files but I'll update you for an alternative solution.
Click to expand...
Click to collapse
Well I seen this forum looking for answer but this is not my particular device however I will explain . I have an Lg G8x ThinQ and when we got root I was naive and had accidentally clicked erase entire flash thinking it would just erase the partition data of the one I had selected. This was not the case and it completely erased it leaving me with a blank slate with no download or even a charge screen it is basically dead unless plugged into a pc in which it will boot straight into Edl. I am not expecting your full support but I do have a device backup that I know will work with the device problem being I can't restore it because there's nothing to select! Normally I would restore the partitions one by one as you do but this is not possible since they seem to have been erased in this state. If you have any information on QFIL that would be greatly appreciated I know we're not working on the exact same device but the process is much of the same.
Cheers!

Mr.Conkel said:
Well I seen this forum looking for answer but this is not my particular device however I will explain . I have an Lg G8x ThinQ and when we got root I was naive and had accidentally clicked erase entire flash thinking it would just erase the partition data of the one I had selected. This was not the case and it completely erased it leaving me with a blank slate with no download or even a charge screen it is basically dead unless plugged into a pc in which it will boot straight into Edl. I am not expecting your full support but I do have a device backup that I know will work with the device problem being I can't restore it because there's nothing to select! Normally I would restore the partitions one by one as you do but this is not possible since they seem to have been erased in this state. If you have any information on QFIL that would be greatly appreciated I know we're not working on the exact same device but the process is much of the same.
Cheers!
Click to expand...
Click to collapse
Alright now we know what's the problem. Best I am suggesting you to search for how to generate partition xml rawprogram xml and patch xml (or you can easily generate latter two from former one) for any newer lg device i.e. G7,V35,V40,G8s,G8X,V50 method for using any of these will work.
I am working on finding universal solution to problem.

[QUOTE = "sourabh7625, bài: 84338561, thành viên: 5955016"]
Được rồi, bây giờ chúng tôi biết vấn đề là gì. Tốt nhất tôi khuyên bạn nên tìm kiếm cách tạo phân vùng xml rawprogram xml và patch xml (hoặc bạn có thể dễ dàng tạo hai thứ sau từ cái cũ) cho bất kỳ thiết bị lg nào mới hơn, tức là phương pháp G7, V35, V40, G8s, G8X, V50 để sử dụng bất kỳ cái nào trong số này sẽ hoạt động.
Tôi đang nghiên cứu để tìm ra giải pháp chung cho vấn đề.
[/TRÍCH DẪN]
Tôi cũng đã gặp phải vấn đề tương tự và đang hy vọng có cách giải quyết. Tôi sử dụng g7

[QUOTE = "kyon007, bài đăng: 84341753, thành viên: 11250663"]
[QUOTE = "sourabh7625, bài: 84338561, thành viên: 5955016"]
Được rồi, bây giờ chúng tôi biết vấn đề là gì. Tốt nhất tôi đề nghị bạn nên tìm kiếm cách tạo phân vùng xml rawprogram xml và patch xml (hoặc bạn có thể dễ dàng tạo thứ hai sau cái cũ) cho bất kỳ lg thiết bị nào mới hơn, tức là G7, V35 phương pháp , V40, G8s, G8X, V50 để sử dụng bất kỳ cái nào trong số này sẽ hoạt động.
Tôi đang nghiên cứu để tìm ra giải pháp chung cho các vấn đề.
[/ TRÍCH DẪN]
Tôi cũng gặp phải vấn đề tương tự và tôi hy vọng có cách giải quyết. Tôi sử dụng g7
[/TRÍCH DẪN]

kyon007 said:
[QUOTE = "kyon007, bài đăng: 84341753, thành viên: 11250663"]
[QUOTE = "sourabh7625, bài: 84338561, thành viên: 5955016"]
Được rồi, bây giờ chúng tôi biết vấn đề là gì. Tốt nhất tôi đề nghị bạn nên tìm kiếm cách tạo phân vùng xml rawprogram xml và patch xml (hoặc bạn có thể dễ dàng tạo thứ hai sau cái cũ) cho bất kỳ lg thiết bị nào mới hơn, tức là G7, V35 phương pháp , V40, G8s, G8X, V50 để sử dụng bất kỳ cái nào trong số này sẽ hoạt động.
Tôi đang nghiên cứu để tìm ra giải pháp chung cho các vấn đề.
[/ TRÍCH DẪN]
Tôi cũng gặp phải vấn đề tương tự và tôi hy vọng có cách giải quyết. Tôi sử dụng g7
[/TRÍCH DẪN]
Click to expand...
Click to collapse
from the first image, click save partition file and share here that generated xml.
also share rawprogram xml you are using.

[QUOTE = "sourabh7625, bài đăng: 84344379, thành viên: 5955016"]
từ hình ảnh đầu tiên, nhấp vào lưu tệp phân vùng và chia sẻ tại đây xml đã tạo.
cũng chia sẻ rawprogram xml mà bạn đang sử dụng.
[/TRÍCH DẪN]
Tôi sử dụng file from dzextracted
[URL opensurl = "true"] https://forum.xda-developers.com/t/...rdbrick-or-red-case-in-9008-mode-without-any- hộp.4052841 / [/ URL]

kyon007 said:
[QUOTE = "sourabh7625, bài đăng: 84344379, thành viên: 5955016"]
từ hình ảnh đầu tiên, nhấp vào lưu tệp phân vùng và chia sẻ tại đây xml đã tạo.
cũng chia sẻ rawprogram xml mà bạn đang sử dụng.
[/TRÍCH DẪN]
Tôi sử dụng file from dzextracted
[URL opensurl = "true"] https://forum.xda-developers.com/t/...rdbrick-or-red-case-in-9008-mode-without-any- hộp.4052841 / [/ URL]
Click to expand...
Click to collapse
As I thought your phone have a blank storage ufs like a new HDD which does not have any physical partitions. physical partitions must be made first before anything.
Currently I can offer only stock original partition0.xml for LG G7, which is a physical partitions table. if you can use any other tool to make partitions through it, let me know..
If you can use english that will be time saving for other members and might also help you.

sourabh7625 said:
As I thought your phone have a blank storage ufs like a new HDD which does not have any physical partitions. physical partitions must be made first before anything.
Currently I can offer only stock original partition0.xml for LG G7, which is a physical partitions table. if you can use any other tool to make partitions through it, let me know..
If you can use english that will be time saving for other members and might also help you.
Click to expand...
Click to collapse
can you give me your misc partition file
I want to try some things

kyon007 said:
can you give me your misc partition file
I want to try some things
Click to expand...
Click to collapse
you can get misc image file from stock kdz of your device model using lg firmware extractor.