yashsingh1/xdaforums huggingface dataset:
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] sybob:
Hi all,

this is a bit of a mess. I am desperately trying to get root, flash TWRP or at least flash an official firmware: nothing works! I have the AT&T model with build 35.

1) Flashing trwp with modified xml, recovery and firehose tells me it flashed successfully, no errors. I reboot and get...stock recovery! :(

2) Trying to flash official firmware with official firehose gives me "ERROR: function: rx_data:247 Error occurred while reading from COM port", "ERROR: function: sahara_main:924 Sahara protocol error" and then "ERROR: function: main:303 Uploading Image using Sahara protocol failed".

3) Using Uni-Android tool, as described working by another user, always errors or dies when trying to run flasher (firehose), official, the one that came with twrp and internal ones

Can it really be this hard? Any hints what else to try? I find the first problem the most annoying and confusing, how can it tell all worked when it in fact does nothing?? Pleas help.

Cheers,

bob

---------- Post added at 10:45 PM ---------- Previous post was at 10:36 PM ----------

Hi again,

just read about the typo and successfully flashed TWRP. I'll report back with probably more problems :)

cheers

bob

---------- Post added at 10:57 PM ---------- Previous post was at 10:45 PM ----------

Wonderful... I used the start address for the recovery that was provided with twrp. Now the devices is bricked, it's stuck in ZTE boot screen. I have no clue how to continue from here as I cannot put it back into EDL :(

What to do now? Do I need to buy an EDL cable from China and wait 4 weeks for it to arrive? :(
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
You can get in edl via the button combo volume up down and power if it puts you in dfu mode you mentioned you have uniandroid. Under reboots do dfu to edl
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] sybob:
Thanks, sounds good, but in UAT 5.02 I only find "fastboot to edl mode" under Anrdroid/Reboots. Do I need a newer version?

cheers

bob
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
5? I hope you mean 25
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] sybob:
Now 9.01. Reboot options haven't changed. Are you sure there is a DFU to EDL option in Version 25?

---------- Post added at 11:39 PM ---------- Previous post was at 11:36 PM ----------

Is there another way to go from DFU to EDL? Or get ADB working without being able to boot into system? Thanks for your patience ;)

---------- Post added at 11:43 PM ---------- Previous post was at 11:39 PM ----------

This is a really wacky tool. It's fully of typos and the GUI is evil. Before I spend 49,99 to unbrick this 80$ device, I really need to be sure. Hope you understand.
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
I'm going to admit I don't feel like putting in my windows drive lol. But search for ZTE axon 7 dfu tool that will work to get your from dfu to 9008
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] ZeroTheSavior:
You do not. If you haven't nuked your system partition you can boot into FTM and then reboot into EDL using adb.

To restore your system, use Mi Flash tool + EDL firmware files from that other thread I linked.

If you nuked your system partition then yes you need an EDL cable. I didn't have any luck with using ZTE DFU to EDL tool, but if you want to try anyway then it's in the Axon 7 forums.
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] sybob:
I am in FTM mode. However, I don't see the device in ADB. Will try more/again. Any tips? Thank you :)
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] ZeroTheSavior:
Go to device manager, find device named "Android" with yellow icon, right click, update driver, pick from list, android device, android adb interface
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] sybob:
Thanks! This is a hell of a ride! I managed to get into edl mode but QFIL won't flash the stock files. And miflash is as crappy as the other stuff, throwing exceptions and asking for drivers. Will try more ... :P
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Qfil won't work you have to use miflash use the version from axon 7 threads.
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] ZeroTheSavior:
Don't use QFIL, it WILL hang on flashing system.img and brick it. Or you can remove userdata.bin and system.img lines from rawprogram0.xml first and it will work.

If you need to flash system.img, You need the exact Mi Flash from this post

https://xdaforums.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] sybob:
Very very exciting and great help guys. It's flashing in MiFlash! Will try to exchange recovery without bricking this time and report back! Thanks again!!
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] sybob:
Hi, status update. In my understanding twrp recovery must be located at the same sector/hex start as the original recovery in my firmware (which is b37 now). But:

- I exchanged the recovery.img for twrp.img and flashed the whole firmware using MiFlash: device gets stuck at boot. Can boot into twrp tho.

- I flashed the original recovery.img together with the whole firmware. Then flashed twrp.img using QFIL: device gets stuck at boot. Can boot into twrp tho.

I cannot flash twrp.img without losing access to system / normal boot. Any ideas? Thanks in advance :)

cheers

bob
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] sybob:
Please enlighten me how to flash twrp without bricking normal boot :) I'd specifically love to decrypt and format my data partition and install supsersu :)

In twrp i have the problem that i cannot access sd card nor usb stick. they always show 0mb. I guess i can copy no_verity_encrypt.zip and supseru_201710..something to internal memory and flash from there once i can have both twrp and system.

cheers

bob
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] sybob:
Just an idea: What about flashing full firmware with MiFlash, then copy files needed to internal memory, then flash twrp, then (from twrp) flash no_verity_encrypt.zip ... will that remove boot checks and make system work again?

cheers

bob
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] Corekai:
Unjustified Dev - Read this

Hey Unjustified Dev. Your guide works. But you need to add this additionally, these steps.

It bootlooped for me until I flashed the B37 Rom with the Recovery Image & a Boot.img I found in a thread involving you. As soon as I reinstalled firmware + your recovery + your edited boot image, It worked just fine. I used the TWRP to delete thermal Throttling & to make the CPU pegged at 2150 MHZ Constantly. It can get pretty hot, like 70 degrees on the CPU.

Anyways, I really need your help. I have two of this phone - One has a totally broken second screen. I would love to be able to flash LineageOS on my broken Axon M, since it only has one functional screen (I will remove the second screen physically soon, detaching from the motherboard)

Please provide to me your LineageOS, I would love to be able to root it and just have a cool rooted single screen Axon M haha.

I have been lurking this thread for a while now.
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] sybob:
Oh, I obviously need that boot.img too to prevent bootloop! Can you please tell me where to find it?

cheers

bob
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] Corekai:
​

Here it is. I have to change the url because new user. (Https) ://drive.google.com/file/d/1xBH_BHFyQGtKOt7FekuPtTCa9-E27xAF/view?usp=sharing[/url]

I reuploaded it to my Google Drive.
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] sybob:
thank you, will try right away!!

cheers

bob

---------- Post added at 08:53 PM ---------- Previous post was at 08:04 PM ----------

Sorry to say that, but after finally being able to have both twrp AND working system I now get:

SuperSU installer

- Mounting /system, /vendor, /data and rootfs

- BAD RECOVERY DETECTED, NO UNZIP, ABORTING

Updater process ended with ERROR: 1

:(

Any chance to fix this or to get root otherwise? Magisk?

cheers

bob

---------- Post added at 09:18 PM ---------- Previous post was at 08:53 PM ----------

So, flashing Magisk 20 with trwp and your boot.img results in black screen half a second after power up. Again softbricked. I am pretty used in unbricking right now but totally out of ideas how to obtain root. Did you manage to get root on AT&T model?

cheers

bob

---------- Post added at 09:58 PM ---------- Previous post was at 09:18 PM ----------

I am seriously lost. No SuperSU.zip is flashable from this TWRP (BAD RECOVERY DETECTED, NO UNZIP, ABORTING) while Magisk is flashable but results in instant-EDL mode after boot. What can I do? Please help!
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] ZeroTheSavior:
Root is not possible at this time. Unjustified dev said in the research thread that installing magisk or custom kernel causes bootloop.

Installing Magisk on the stock kernel on the Axon 7 also causes a bootloop, so perhaps a custom kernel is required first.
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] sybob:
Thank you. I made my peace with it and learned that I don't need to have root to unbloat/uninstall system apps. It's my first Android without root and I have to admit it has advantages like being able to play Nintendo games out of the box ;)
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] :
Hi I have written a new boot.img for the AXON M AT&T with full Magisk support.

But I need someone to test, I don't have the phone. Just commend and I will send you the link.
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] Drakosha:
Ready to test!

Hi! I'm ready to test :) Z999 AT&T. (If boot is signed with "Magisk Test Keys" if WILL fail, the only way to get over the locked bootloader is to somehow keep original AT&T boot.img signature.)
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Not sure how magisk signs the newer images but it will not work. My twrp is signed but not with ZTE keys but my own generated ones.
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] Drakosha:
Idea!!!

Hi!

Wait a second. TWRP is, basically, a stock kernel that boots recovery instead of Android. And AT&T bootloader does not block recovery kernels, signed with non-stock keys. SO, if we flash the rooted kernel instead of TWRP and start the phone with the key combination to boot into recovery, it will boot the rooted kernel!

This is something I can test by myself, I'll report here soon...
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
The kernel is not stock. It's my source built kernel based on my Axon 7 work. Also the kernel doesn't tell the device to go into recovery the bootloader does via the button combo or via the reboot magic sent from the kernel. I've tried many things I couldn't get the device rooted on stock without bricking it
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] Drakosha:
Well, my idea didn't work. :( I patched stock kernel with Magisk and flashed it using TWRP in recovery slot, but the phone has still refused to boot, both with "Vol UP" pressed or not...

P.S. Now my phone says "Device is corrupt" and requires pressing power at every boot, but after that is starts as normal. I reflashed B37 (with TWRP & patched boot) using MiFlash, but the message is still there. I guess, I need to factory reset...

P.P.S. Factory reset didn't work :(

P.P.P.S adb reboot "dm-verity enforcing" worked. This is something that should be included in FAQ.
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] :
My Internet is not so good. I will send the link tomorrow

---------- Post added at 10:12 PM ---------- Previous post was at 10:10 PM ----------

If it does not work, I'll geht an Axon M in the nect few Werks and then complete Magisk for it
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] Corekai:
Hey I will test as I have two AXON M with Twrp already
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] :
Here is the link:

Removed
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] sybob:
Why? Why did you remove it?? :(
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] :
It hasn't work
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] ZeroTheSavior:
no unzip binary in TWRP?

Is there some way to compile it? Or link busybox unzip to unzip?
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] shawn5569:
Sorry, I'm new here.

Can somebody guide me how do I exactly do "flash system.img using Mi flash"? Does this mean, I can flash ONLY the system.img? I don't see any option in Mi flash tool.

BTW, I'm using the the EDL NTT Docomo firmware from Deadman because mine is the Docomo version. (https://xdaforums.com/axon-m/how-to/rom-zte-axon-m-stock-firmware-firehose-t3909847)
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] FF7CloudsNobody:
Wow I'm dumb, back before my life went crazy (divorce, new job, more work from said job, etc.) I was trying to work on this. Idk why I missed the dm verity. I had ended up soft bricking it testing builds and forgot how I got past the boot loop the first time. I'll have to test it this weekend when my daughters aren't home.

---------- Post added at 03:35 PM ---------- Previous post was at 03:32 PM ----------

No, this means if it must be flashed, you must use that version. Otherwise other versions will work. I'll look at my recovery from my computer pre-wipe to see if I have my program files that I used a few months back
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] benzersizadam:
am i dumb or there is no patch0.xml file ?
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] none24:
Hi, im getting a message in MiFlash saying "The String was not recognized as a valid Uri. Parameter name: input Url"

Can you please help? Thank you
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] shawn5569:
I don't mean to be rude but errr...I can't make any sense of what you have just said...:crying:
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] 3dcantaloupe:
Flashing TWRP using QFIL

Hello! it seems QFIL is not able to flash the TWRP image even though I fixed the typo (Or I think I did). Thank you for any help you can provide me. I did not use any patch0.xml

Here is a log when I was flashing:

Start Download

COM Port number:3

Switch To EDL

Switch To EDL FailFailed to Switch to Emergency Download mode

Download Fail:Fail to find QDLoader port after switch

Finish Download

Here is my edited Rawprogram.xml:

<?xml version="1.0" ?>

<data>

<!--NOTE: This is an ** Autogenerated file **-->

<!--NOTE: Sector size is 512bytes-->

<program start_sector="1181696" start_byte_hex="0x24100000" sparse="false" size_in_KB="65536.0" readbackverify="false" physical_partition_number="0" partofsingleimage="false" num_partition_sectors="131072" label="recovery" filename="recovery.img" file_sector_offset="0" SECTOR_SIZE_IN_BYTES="512"/>

</data>
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] FF7CloudsNobody:
Basically my life went off the rails on top of my laptop dying on me. It has gotten alot better recently though so...

Good news: I built a computer since then and I'm about to install Linux on a secondary hard drive for development of a Lineage ROM

Bad news: I have to start over from scratch

I know this is an old post but I just saw this mention ?

If I remember right, there was a certain way to go about it and I think I mentioned that previously in this thread. I'll get it working and let you know the steps, if you still want the help.
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] 3dcantaloupe:
Yes, I will look for it, but may I please know the steps? Thank you so much! :)
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] FF7CloudsNobody:
If flashing without the patch0.xml file doesn't work, use the one found in the full firmware zip

I got the flashing working, ill update this post with what I have when i get back to my computer later today.
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] 3dcantaloupe:
Thank you! I'm looking forward to it!

edit: any more updates?
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] 3dcantaloupe:
NVM, I managed to figure it out, and I even made a guide for those that want a detailed illustration of the process! Here it is: https://youtu.be/EDvRqkKjpbw :)
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] dimex:
Are you able to get root with this method?
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] 3dcantaloupe:
Nope, I was just able to get twrp on the phone. Do you have any suggestions for me to try to get root? That would be amazing!
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] dimex:
I don't. But you mentioned flashing Magisk so I thought you'd have more info.
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] 3dcantaloupe:
Yep, I said that it may be possible in the future and that I was exited. I am trying out various ways to get magisk onto the Axon M without bricking it, so lets see where it takes us!

Hello man, how are you? are you ok? It has been more than a day (months actually), so I am wondering if you are fine both physically and mentally.
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] FF7CloudsNobody:
Yeah I'm doing fine. Sorry about not responding all this time, the xda labs app I used to use didn't ever tell me I had a reply.

I know that I still have the flashing tool setup on my computer but I did give up on making a fully functional lineage os rom for this phone and converted my Linux drive for more storage on the windows side of my computer. When I did this, I transferred all my work over to a Google cloud server to try to continue it but then I messed up somewhere while working on it and stopped working on it so I could focus on my family and work. I was taking on too much and had to cut back on certain things including this. I may pick it back up at some point but due to me messing up the rom development the way I did, I'd have to start from scratch for the 4th or 5th time.
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] 3dcantaloupe:
Sorry for the super late reply, just saw this. You are a really dedicated man and I commend you for that! Yep, I was also thinking about creating my own Lineage for this phone. Unfortunately, I was not able to get any sort of root in the stock rom, so I was thinking maybe I could incorporate it in this new Lineage I was gonna make. But I still have to get started on this rom, so I was wondering if you could provide me tips for this large endeavor. Any sort of help is appreciated! Anyway, take care of your personal life,

nothing is more important than family,

even work or this phone. Good luck! (y)
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] Attila's:
can you show me how to build it. on this year zte axon m come with only android 7.1 and it so old for much app now.
[OnePlus 6T  Questions & Answers] roblpetty:
I tried unrooting my 6T and something went wrong. Now when it boots it shows the bootloader unlocked warning then goes to black screen and stops. It will randomly vibrate when I press the screen or the power button. My computer doesn't recognize it and I can't even seem to be able to turn it off completely. The only thing I can get it to do is reboot by pressing and holding the power and volume up buttons.

Any advice on how I can force it into fastboot or get my computer to recognize it so I can working on it?
[OnePlus 6T  Questions & Answers] cultofluna:
Keep pressing simultaneously volume up , volume down and power button all three of them until you get the fastboot screen.

It maybe takes a while...
[OnePlus 6T  Questions & Answers] lladwein:
like the first answer:

hold vol up, vol down and power butten as long as the phone boots into fastboot mode and flash fastboot Rom OR

hold vol up and vol down for about 5-6 seconds, and plug your phone to your computer. if it gets recognized (with typical sound of windows) try msm tool. And be sure you have the qualcomm driver installed.
[Realme X Questions & Answers] cocoon_zz:
Official A16 ozip was released yesterday:

realme.com/support/software-update

My working flow is as follows:

1. Extract boot.img and vbmeta.img from the converted zip

2. Use Magisk to patch the boot.img , we got magisk_patched.img

3. fastboot flash boot magisk_patched.img and reboot. However, in this method it says

the current image (boot/recovery) have benn destroyed and can not boot

4. I asked others, they said I have to flash vbmeta.img too. So I used ./fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img. This time, when booting, it just turns black (Under normal circantance, it will show a yellow REALME logo, however not appearing in this method)

_____________________________________

What should I do? Does this vbmeta.img in the official zip work? Thanks for your help!
[Realme X Questions & Answers] HelloKaran:
Upload a video
[Realme X Questions & Answers] LovemyRealme:
Hi, I have twrp on the rmx1901cn (Chinese version), can I use the converted zip to image my phone back to its original state using twrp? I don't mind getting back to Chinese stock ROM anymore.

Also, I only have access to TWRP and boot loader now.
[Realme X Questions & Answers] LovemyRealme:
Please provide some more hints. I'm stuck at the same spot.

I've got a little further. I converted the ozip to zip. Extracted the boot.img from the converted file. Flashed boot.img to the phone. and flashed vbmeta.img using the same commands as cocoon_zz.

I'm getting the same black screen as cocoon_zz. I haven't use Magisk but the stock rom is okay by me. Can you guys please give some hints on how to get pass the black screen after the realme logo?
[Xiaomi Mi 9 SE Questions & Answers] o5cargallo:
could you help me know how to flash a rom like havocOS
[Samsung Galaxy Tab S4 Questions & Answers] minion_8686:
I was able to fix this issue, thanks to anyone that viewed this thread with intents to help.

So... I followed this guide (https://xdaforums.com/galaxy-tab-s4/how-to/guide-rooting-wifi-version-galaxy-tab-t3841763) and it bricked my Tab S4 version T830XXU3BSF3 (Wifi). I get to the Samsung screen with a custom powered by logo and Set Warranty Bit : Kernal at the top but it wont load any further. I downloaded the latest firmware from sammobile and attempted to flash from Odin. Odin reports all threads completed, but still unable to get past the Samsung screen. Also attempted cache clear and factory reset, nothing worked, can anyone give me some info on how I might be able to resolve this? Or do I just have a fancy paper weight now? Thanks.

(I'm fairly new to this whole process so if I have dump follow up questions, I apologize in advance)
[Samsung Galaxy Tab S4 Questions & Answers] daitalos:
Try again,you make a mistake somewhere ....Take the correct firmware (for your country) and follow the instructions .Needs patience!

Read carefully for :

BL (Bootloader)

CP (Modem / Radio)

CSC_*** (Country / Region / Operator)

HOME_CSC_*** (Country / Region / Operator)

Use the odin v3.13.3 & after the installation is complete,go to recovery mode > wipe data/factory reset > wipe cache & reboot (it takes some time for boot be patient)

_ https://www.sammobile.com/samsung/galaxy-tab-s4-105-wi-fi/firmware/SM-T830/

_samsung drivers : https://samsungusbdriver.com/download/samsung-driver-v1-7-11-0

[_*(If the situation persists,you can first flash TWRP for your model, from TWRP > wipe data / factory reset > advanced wipe > system/cache/data/internal/dalvik > format data > Reboot on download mode ! > Flash stock firmware via Odin following the instructions correctly etc) ....

_ https://xdaforums.com/galaxy-tab-s4/development/recovery-twrp-3-3-0-sm-t83x-t3928278

All this with twrp,ONLY if failure continues ! ]

sry for english
[Samsung Galaxy Note 10+ Accessories] BigMosley:
Anyone use the Ghostek Atomic Slim in the past? Considering getting the clear back/black version to show off the Aura Glow but some reviewers of previous devices say the Aluminum bumper affected cell reception? My favorite case is the OtterBox Pursuit Series but OtterBox only makes them for the S line and not the Note line, so I'm looking for the next best thing.