I'm might be in wrong place but im Looking for any info on g8 power lite variant of g8 power. UK unlocked regards retail. Looking like It is a oddball as I cannot find anything. I don't think there will be much support but if anybody knows if this similar enough to any other variant ?? Android pie out the box no update. Not even Moto app to enable one button navbar. Any help thanks
Hello
I just got the LATAM version of that same phone, and i can tell you that it's gonna take some time to get information, but it will appear in some time.
Indeed, this is the right place, but it seems to be that similar models have variants around the globe, and the Moto G8 Power Lite it's not a priority right now.
I'm waiting the same for my version (XT2055-2), but it's just a matter of patience.
Keep looking on the forum and eventually it will appear some information
Kiffo said:
Hello
I just got the LATAM version of that same phone, and i can tell you that it's gonna take some time to get information, but it will appear in some time.
Indeed, this is the right place, but it seems to be that similar models have variants around the globe, and the Moto G8 Power Lite it's not a priority right now.
I'm waiting the same for my version (XT2055-2), but it's just a matter of patience.
Keep looking on the forum and eventually it will appear some information
Click to expand...
Click to collapse
Yea I thought as much, motorola seems to be putting out lots of versions of every device. This is by far the worst device I have had in recent memory, seems be missing quite a bit of the usual options available on other recent moto devices. I would have a go at bits myself but it also seems my version of this device has a Chinese bootloader installed, I don't think I will still have this device by the time any work is done I need to change phones quite often for work. Good luck.
bukata said:
Yea I thought as much, motorola seems to be putting out lots of versions of every device. This is by far the worst device I have had in recent memory, seems be missing quite a bit of the usual options available on other recent moto devices. I would have a go at bits myself but it also seems my version of this device has a Chinese bootloader installed, I don't think I will still have this device by the time any work is done I need to change phones quite often for work. Good luck.
Click to expand...
Click to collapse
The chinese bootloader is something common on Motorola, even i have the same thing. But i guess they gonna come up with something. As per today, the Brazil version of this smartphone started getting Android 10 (with some bugs tho) so i guess Motorola gonna start moving things in the coming weeks
Hi, I've got g8 power lite and would like some modding but how can I recon which version have I got?
islandman75 said:
Hi, I've got g8 power lite and would like some modding but how can I recon which version have I got?
Click to expand...
Click to collapse
Go to Settings > About Phone > Model & hardware
and it will show you the Model, Serial number and Model(SKU) of the device. Ithing what you are after is the SKU.
Tip: Under the title "Model & Hardware" you should see "Model: moto g8 power lite" in a gray(er) font.
{This may vary between models and versions}
Hope this helps.
lennonhorrocks said:
Go to Settings > About Phone > Model & hardware
and it will show you the Model, Serial number and Model(SKU) of the device. Ithing what you are after is the SKU.
Tip: Under the title "Model & Hardware" you should see "Model: moto g8 power lite" in a gray(er) font.
{This may vary between models and versions}
Hope this helps.
Click to expand...
Click to collapse
found it, thank you. I've got XT2055-1
It's not possible to unlock the bootloader on the G8 power lite, only the G8/G8 power.
It cannot be done using fastboot but it is certainly possible using the Realtek VCOM USB protocol
Rooting Moto G8 Power Lite
Does anyone know where I can find a decent guide to rooting the G8 Power Lite (if one exists - I know it's only been out a few months)? I've had a Google around and looked on this forum and on reddit but I can't find anything. I haven't done...
forum.xda-developers.com
This video sums it up well
Essentially you need to:
1. download MTKCLIENT from github, works best on Linux IMHO but Windows works too - on Windows you need additional USB drivers and MTK Drivers, which i attached. Use PIP to install the requirements by going into the MTKCLIENT directory and typing into CMD/Terminal: python3 pip install -r requirements.txt
2. Copy the G8 power Lite specific script to the root folder of the MTKCLIENT
3. Open up the phone, remove the plastic covering the cameras and motherboard. Unplug the battery. Short these two pins either by soldering them together or just using something metal - this is only necessary during the flash and then should be removed.
View attachment 5889467
4. Plug in usb cable to the phone but dont connect it to the pc yet. Start the program either by CD-ing to the MTKCLIENT directory and running it via CLI (on Linux: python3 mtk w proinfo,seccfg proinfo.bin,seccfg.bin, If it wont unlock using the custom G8 script, just run this generic command: python mtk da seccfg unlock) or doubleclicking the desbloq_bootloader.bat on Windows. Then short the two pins, keep them shorted and connect the USB cable to the PC. You should see a bunch of code scroling, it will automatically close/end.
5. Unplug USB, remove short circuit from two pins, plug in battery, turn on phone, you should see lines of text during the boot like this:
View attachment 5889471
Bootloader unlocked. Now the only use is ROOT, no custom ROMs or Recoveries available as its vastly different from normal G8 power, which has a Snapdragon CPU and totally different screen. You'll also get a big "CARRIER INVALID" message on the home screen, so after you ROOT make sure to relock the bootloader using the same method but the command is python3 mtk da seccfg lock
I'm almost sure that what I got it's a - Moto g8 Power lite - XT2055-1
So I got the phone long ago and it's been mostly at home and used as a backup by some of my friends.. I can't even remember which person had it last time.
Thing is that I completely forgot about the Motorola protection and after factory reset it keeps on asking for the last used google account which I got no clue which one would be. To make things worst I have no way to find out the IMEI's so that I can use Motorola RSA.
It looks like to me that I can't enter BootRom mode and I can only access preloader mode even tho, I got access to recovery mode and meta mode. I have tried all the key combos I can imagine by now.
I have also tried sp flash tools but I'm getting an error when the process is starting.
I'll drop some more details soon.. thank you.
BadChoices said:
I'm almost sure that what I got it's a - Moto g8 Power lite - XT2055-2
So I got the phone long ago and it's been mostly at home and used as a backup by some of my friends.. I can't even remember which person had it last time.
Thing is that I completely forgot about the Motorola protection and after factory reset it keeps on asking for the last used google account which I got no clue which one would be. To make things worst I have no way to find out the IMEI's so that I can use Motorola RSA.
It looks like to me that I can't enter Boot mode and I can only access Preload mode even tho, I got access to recovery mode. I have tried all the key combos I can imagine.
I have also tried sp flash tools but I'm getting an error when the process is starting.
I'll drop some more details soon.. thank you.
Click to expand...
Click to collapse
have you tried using mtkclient? unlock the bootloader and then remove frp
aryanhington said:
have you tried using mtkclient? unlock the bootloader and then remove frp
Click to expand...
Click to collapse
I did before as far as I recall but I gave up on it I think 'cus I ran into some issues as well.. I'm a bit rusty when it comes to this kind of stuff.. now that I'm reading all again about the tools etc I'm gonna give mtkclient a go and keep you all posted. Thank you again.
First off some questions please.. and I'm running win 11 pro.
What am I suppose to see on the screen when on Brom mode ? or how do I know that I'm on that mode.. obviously that if I'm not the operations just fail.
cant run mtk_gui atm for some reason trying to clear that out.. 'C:\Users\Q\AppData\Local\Programs\Python\Python311\Lib\site-packages\shiboken6\libshiboken does not exist'
Also tried bypass_utility_v1.4.2 using dif. key combos always returns 'device in preloader mode, trying to crash..'
mtkclient handshake returns failed 'Preloader - [LIB]: status: handshake failed, retrying..'
I'll keep on trying to understand all this just need my time.. all help appreciated.
BadChoices said:
First off some questions please.. and I'm running win 11 pro.
What am I suppose to see on the screen when on Brom mode ? or how do I know that I'm on that mode.. obviously that if I'm not the operations just fail.
cant run mtk_gui atm for some reason trying to clear that out.. 'C:\Users\Q\AppData\Local\Programs\Python\Python311\Lib\site-packages\shiboken6\libshiboken does not exist'
Also tried bypass_utility_v1.4.2 using dif. key combos always returns 'device in preloader mode, trying to crash..'
mtkclient handshake returns failed 'Preloader - [LIB]: status: handshake failed, retrying..'
I'll keep on trying to understand all this just need my time.. all help appreciated.
Click to expand...
Click to collapse
for brom/preloader mode you will need to use the shorting method shown in the previously mentioned youtube video, not sure why you're trying mtk_gui and bypass_utility_v1.4.2 , what are you trying to achieve by using them?
Well reading from github where you get the mtkclient I thought that I could unlock the bootloader using the bypass_utility_v1.4.2 just like that.. guess ain't that easy and tbh after reading your previous words also thought that I could try using the mtkclient regardless being via the gui or the terminal.
I have seen some posts about the Brasilian fella and more shorting method but thought that by now wouldn't be needed anymore.. I did have my phone open before 'cause of that.. guess I'll have to have a look again.. my bad.
Thanks again.
BadChoices said:
Well reading from github where you get the mtkclient I thought that I could unlock the bootloader using the bypass_utility_v1.4.2 just like that.. guess ain't that easy and tbh after reading your previous words also thought that I could try using the mtkclient regardless being via the gui or the terminal.
I have seen some posts about the Brasilian fella and more shorting method but thought that by now wouldn't be needed anymore.. I did have my phone open before 'cause of that.. guess I'll have to have a look again.. my bad.
Thanks again.
Click to expand...
Click to collapse
you might be able to get into brom/preloader mode by holding volume down button while it is booting but shorting also brings the same result
aryanhington said:
you might be able to get into brom/preloader mode by holding volume down button while it is booting but shorting also brings the same result
Click to expand...
Click to collapse
I still can't believe what is that I ran into.. so was about to disassemble the motherboard/cameras cover that doesn't look that straight forward but went on checking again some bits on the vid.. meanwhile made a search for moto g8 power lite disassembling when got the suggestion moto g8 power lite frp bypass.. the first vid solved my issue.. I just died 'cus I have been wondering about an hack like this for ages now.
I'll come back for some further assistance on some other devices when I get the... brains.
Thanks for the support @aryanhington
BadChoices said:
I still can't believe what is that I ran into.. so was about to disassemble the motherboard/cameras cover that doesn't look that straight forward but went on checking again some bits on the vid.. meanwhile made a search for moto g8 power lite disassembling when got the suggestion moto g8 power lite frp bypass.. the first vid solved my issue.. I just died 'cus I have been wondering about an hack like this for ages now.
I'll come back for some further assistance on some other devices when I get the... brains.
Thanks for the support @aryanhington
Click to expand...
Click to collapse
care to share what you did so we can know?
I do care.. I also care the way some people talk to others behind screens.
Now if you read what I have just said on my previous post and the first post so to get what you/I'm dealing with you will realize that I was stuck on welcome screen, after soft reset, 'cus of FRP, once the last google account used was still active and I had no clue. Just use the search string on youtube that I have mentioned and on the first vid follow the 20k steps to be able to bypass google/android FRP.
Farewell.
Would someone please point me out their fav XT2055-1 roms ?
Thank you.
Related
Hello everyone! I am in dire need of help.
So I recently decided to acquire a regular Motorola G7 because I had heard its battery is fantastic. This far, I have been loving it.
But silly me decided I wanted to explore OEM boot unlocking to eventually root the device. After successfully completing theses tasks, I installed the TWRP recovery. Sadly, something (must have) went wrong because when I tried to reboot, the phone went into hard brick. Completely unresponsive, holding both power and vol. down button for 2+ minutes did nothing. I basically have exhausted every Internet recommendations thus far and nothing has been fruitful.
I have been able to get the Qualcomm Port 9008 (COM3) to show up in device manager when I hold power and vol. down. Also, the program QPST also recognizes a phone in Sahara download mode (although I have no idea what it means nor what to do with that, if anything).
So here I am, asking for your help. I have read somewhere that a blankflash zip file could allow me to restore my phone but alas, I wasn't able to find any nor would I know what to do with it.
I would greatly appreciate any help.
Regards,
Afireblood.
Edit: I have managed to find a way to potentially salvage my bricked phone, using QIFL tool to flash a stock rom. However, to do so I need some files (which are proper to the Moto G7 - any other would not do). They are:
programmer (firehose?).mbn
rawprogram.xml
patch.xml
If anyone has any clue where I could find that (except everywhere on Google - it hasn't been helpful), I would very much appreciate it!
afireblood said:
Hello everyone! I am in dire need of help.
So I recently decided to acquire a regular Motorola G7 because I had heard its battery is fantastic. This far, I have been loving it.
But silly me decided I wanted to explore OEM boot unlocking to eventually root the device. After successfully completing theses tasks, I installed the TWRP recovery. Sadly, something (must have) went wrong because when I tried to reboot, the phone went into hard brick. Completely unresponsive, holding both power and vol. down button for 2+ minutes did nothing. I basically have exhausted every Internet recommendations thus far and nothing has been fruitful.
I have been able to get the Qualcomm Port 9008 (COM3) to show up in device manager when I hold power and vol. down. Also, the program QPST also recognizes a phone in Sahara download mode (although I have no idea what it means nor what to do with that, if anything).
So here I am, asking for your help. I have read somewhere that a blankflash zip file could allow me to restore my phone but alas, I wasn't able to find any nor would I know what to do with it.
I would greatly appreciate any help.
Regards,
Afireblood.
Edit: I have managed to find a way to potentially salvage my bricked phone, using QIFL tool to flash a stock rom. However, to do so I need some files (which are proper to the Moto G7 - any other would not do). They are:
programmer (firehose?).mbn
rawprogram.xml
patch.xml
If anyone has any clue where I could find that (except everywhere on Google - it hasn't been helpful), I would very much appreciate it!
Click to expand...
Click to collapse
Update: Now in search of the Moto G7 specific blankflash.zip
If anyone knows where I can find that I would really appreciate it!!
I am not familiar with the g7. (I own a G5+). I believe the G7 code name is "river". You can look at https://mirrors.lolinet.com/firmware/moto/river/ and they show a blank flash - but let me say something - a blank flash must be exact for your phone. Its basically the main disk partition with other partitions inside. My phone has 64GB/4GB, and 32GB/3GB-2GB models - so you see a problem. But if all the G7s are the same, then this blank flash should be OK.
Also you can download the phones original firmware at https://mirrors.lolinet.com/firmware/moto/river/official/RETUS/ , if its a US model. If its not, back up 1 directory and you can find it by either carrier or country. You can fastboot the firmware - which I would do before a blankflash,
Hope that helps.
Requesting someone's backup of emmc so I can unbrick my XT2117-4 Retail(Retus) Moto G power 2021. Stuck in Qusb-HS Dloader 9008 mode after setting active slot to b with nothing on slot b in fastboot. If I could atleast somehow swap back to slot_a I feel like that would work but I don't think that's really a possibility in edl. Mainly the GPT also would be helpful. Motorola/borneo_retail/borneo:10/QZBS30.Q4-43-35-2/f8e93:user/test-keys is the build I was on at the time. My phone is hard bricked not soft bricked. There is no fastboot mode only edl mode with Qcom HS-USB 9008. I believe It got bricked by me switching to slot_b in fastboot mode with nothing on slot_b not even bootloader. Also my bootloader is unlocked and it was rooted with magisk at the Time of hard brick. I believe fastboot set_active_slot b was the command that bricked it or what ever the correct usage of the set active command was if that's not exactly it. I just need the emmc_prog_firehose for SM_KAMORTA_H or SDM662 or SM6115. Whatever the proper name out of those it would be I guess for this phones type.
Can't use LSMA since it's hard bricked it doesn't even recognize anything is plugged in. I need a blankflash file to use with qboot or the emmc_programmer and then use QFIL or QPST possibly. I use Linux and Windows both if that helps at all somehow.
More info from a reply of mine.
REPLY:
"No it specifically warned that there was nothing on b and it was dangerous but I wasn't paying much attention to it because I was watching family guy so I told it to go ahead and switch. Insta brick after that decision. It does warn you though or it did with me on my phone. Whenever you've done it your slot probably wasn't really "empty" in the sense it didn't have a bootloader on it. You can't boot up a phone that's on a slot without even a bootloader on it otherwise you'll literally have nothing to load your boot image in the first place which means no recovery or fastboot either for A/B devices hence you then have a hard bricked phone in emergency download mode afterwards that either needs reprogrammed or deep flashed (If there's really a difference I don't know). I think you still need a firehose_emmc_programmer or Blank-flash file which has a programmer in it to do that though which is what I need. Some phones might have different emergency protocols for that situation or maybe it's been updated since to where it prevents A/B phones from getting stuck in limbo on an empty slot but the XT2117-4 Moto G Power 2021 doesn't it just warns or atleast when I bricked mine. It's nice to have the option for developer and testing purposes probably or just as a way to get into EDL Mode. I just wasn't paying as much attention as I should have been while tweaking my phone. I'm not a developer or expert though so someone correct me if I'm mistaken somewhere but I have atleast an alright understanding of what's going on I hope from my experience with rooting/rooted phones. A/B partitioning is still kind of a weird newer thing to me since I haven't done much after bricking my G Power and I was used to System As Root before that."
snuffinaround said:
Requesting someone's backup of emmc so I can unbrick my XT2117-4 Retail(Retus) Moto G power 2021. Stuck in Qusb-HS Dloader 9008 mode after setting active slot to b with nothing on slot b in fastboot. If I could atleast somehow swap back to slot_a I feel like that would work but I don't think that's really a possibility in edl. Mainly the GPT also would be helpful. Motorola/borneo_retail/borneo:10/QZBS30.Q4-43-35-2/f8e93:user/test-keys is the build I was on at the time.
Click to expand...
Click to collapse
Did you by any chance track down anything or solve this? Mine is currently soft bricked also.,,bootloader locked and will only boot to fastboot. any help would be great!
HazyBoneX said:
Did you by any chance track down anything or solve this? Mine is currently soft bricked also.,,bootloader locked and will only boot to fastboot. any help would be great!
Click to expand...
Click to collapse
You already tried LMSA?
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
sd_shadow said:
You already tried LMSA?
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
Click to expand...
Click to collapse
Yes every time it says fastboot flash single partition failed
Hello guys. I have this device and I'll help you. Mine's not rooted yet which is why I came to ask a question and accidentally clicked this thread. Tell me what I need to do to get what you need and I'll do it. i don't know how to use a mouse in TWRP and it sounds like that's what you need. I have a wireless mouse with a usb dongle but no type-c otg at the moment. I just found out from another post in here about using twrp from a terminal. I need to learn more about that too. Dude made a kernel backup with an adb twrp command. I asked him about it but have gotten no response.I also only run linux, but may install a windows 11 virtual machine to use LMSA since every lolinet kernel I've rooted so far results in no touch response.
Have you guys tried fastboot flashing the entire lolinet firmware? I just made a tutorial on it. I've never had a problem that wouldn't fix and I have quite a bit of experience....
Fastboot Flash Firmware Commands (borneo)
I made this list because I needed it and didn't see one around here. If anyone can use it, here it is with a link to the firmware. Taylor made for the XT2117 Moto G Power 2021 (borneo). https://mirrors.lolinet.com/firmware/moto/borneo/...
forum.xda-developers.com
I'd bet that would fix it. It re-writes all partitions.
arkansawdave74 said:
Hello guys. I have this device and I'll help you. Mine's not rooted yet which is why I came to ask a question and accidentally clicked this thread. Tell me what I need to do to get what you need and I'll do it. i don't know how to use a mouse in TWRP and it sounds like that's what you need. I have a wireless mouse with a usb dongle but no type-c otg at the moment. I just found out from another post in here about using twrp from a terminal. I need to learn more about that too. Dude made a kernel backup with an adb twrp command. I asked him about it but have gotten no response.I also only run linux, but may install a windows 11 virtual machine to use LMSA since every lolinet kernel I've rooted so far results in no touch response.
Have you guys tried fastboot flashing the entire lolinet firmware? I just made a tutorial on it. I've never had a problem that wouldn't fix and I have quite a bit of experience....
Fastboot Flash Firmware Commands (borneo)
I made this list because I needed it and didn't see one around here. If anyone can use it, here it is with a link to the firmware. Taylor made for the XT2117 Moto G Power 2021 (borneo). https://mirrors.lolinet.com/firmware/moto/borneo/...
forum.xda-developers.com
Click to expand...
Click to collapse
If you If you could pull a total nandroid backup i think that should be what i need to restore my phone if any one could chime in it would be greatly qpp
Yes I have tried that. Check out command line android backup twrp.
HazyBoneX said:
If you If you could pull a total nandroid backup i think that should be what i need to restore my phone if any one could chime in it would be greatly qpp
Click to expand...
Click to collapse
Ok. I have a question as I've never used a mouse with my phone before. Are you guys using a mouse through OTG to use im TWRP? To help you any time soon I'll have to find info for using TWRP with ADB commands as I don't think I have the hardware to use my mouse.
Edit: I found information faster than I thought I would. I looked it up in the past and could find nothing but it's a new feature.
HazyBoneX said:
If you If you could pull a total nandroid backup i think that should be what i need to restore my phone if any one could chime in it would be greatly qpp
Click to expand...
Click to collapse
Okay, that would require me to factory reset because I won't send a backup of my logged in system. I would do that if I thought it would help, but it won't. I don't thiink amyone has beennable to restore a stock nandroid on these auto-encrypting motos. If I''m wrong, and I may be, show me. I've tried many times and many ways. I have been able to restore custom backups, but never stock.
arkansawdave74 said:
Okay, that would require me to factory reset because I won't send a backup of my logged in system. I would do that if I thought it would help, but it won't. I don't thiink amyone has been able to restore a stock nandroid on these auto-encrypting motos. If I''m wrong, and I may be, show me. I've tried many times and many ways.
Click to expand...
Click to collapse
I I'm not really sure I can't get any files to flash on it I can get TWRP to load I can't get the Motorola restore program to flash anything so I'm literally just stuck in fast food with a locked bootloader and non-rooted and no developer options turned on any help would be appreciated
HazyBoneX said:
I I'm not really sure I can't get any files to flash on it I can get TWRP to load I can't get the Motorola restore program to flash anything so I'm literally just stuck in fast food with a locked bootloader and non-rooted and no developer options turned on any help would be appreciated
Click to expand...
Click to collapse
I feel your pain. You have tried the obvious
fastboot set_active a
of course? I'm not trying to be a smartass. You just may have switched slots with twrp and don't know the fastboot command.
arkansawdave74 said:
I feel your pain. You have tried the obvious
fastboot set_active a
of course? I'm not trying to be a smartass. You just may have switched slots with twrp and don't know the fastboot command.
Click to expand...
Click to collapse
Fastboot set_active a retutns....
Setting current slot to 'a'...
FAILED REMOTE FAILURR
HazyBoneX said:
Fastboot set_active a retutns....
Setting current slot to 'a'...
FAILED REMOTE FAILURR
Click to expand...
Click to collapse
Ok. How was it that you switched slots and got stuck? I want to experiment but I don't want to make the same mistake.
Also, if your bootloader is locked, aren't you still under warranty? Can you make a warranty claim?
If not, you may be able to unlock it in your current state which might make fixing it easier. You could try
fastboot oem get_unlock_data
and if it returns some lines of code you can likely unlock it now.
With a locked bootloader you are very limited and my twrp backup of a RETUS would have had no chance at all of helping you unless you happen to have a factory unlocked US variant.
I had it rooted and the bootloader unlocked...then i tried to follow a flash back to stock and re lock boot loader guide....but now when it boots it says no valid os or i can go into fastboot and thats about it....
HazyBoneX said:
I had it rooted and the bootloader unlocked...then i tried to follow a flash back to stock and re lock boot loader guide....but now when it boots it says no valid os or i can go into fastboot and thats about it....
Click to expand...
Click to collapse
Have you tried to unlock it again with the same code? I have never even tried to relock a bootloader. I may have nightmares. If you still have the unlock email I would try that.
arkansawdave74 said:
Have you tried to unlock it again with the same code? I have never even tried to relock a bootloader. I may have nightmares. If you still have the unlock email I would try that.
Click to expand...
Click to collapse
I have tried that also and developer options are not on so i cant
So sorry. If i think of anything else I'll let you know. I think relocking your bootloader with an altered kernel was a bad idea, but I think relocking your bootloader is a bad idea anytime.
My phone is hard bricked not soft bricked. There is no fastboot mode only edl mode with Qcom HS-USB 9008. honestly a mmcblk0 backup would definitely help if anyone would want to backup and then pm me a link or something. I believe It got bricked by me switching to slot_b in fastboot mode with nothing on slot_b not even bootloader. Also my bootloader is unlocked and it was rooted with magisk at the Time of hard brick
snuffinaround said:
Requesting someone's backup of emmc so I can unbrick my XT2117-4 Retail(Retus) Moto G power 2021. Stuck in Qusb-HS Dloader 9008 mode after setting active slot to b with nothing on slot b in fastboot. If I could atleast somehow swap back to slot_a I feel like that would work but I don't think that's really a possibility in edl. Mainly the GPT also would be helpful. Motorola/borneo_retail/borneo:10/QZBS30.Q4-43-35-2/f8e93:user/test-keys is the build I was on at the time.
Click to expand...
Click to collapse
My phone is hard bricked not soft bricked. There is no fastboot mode only edl mode with Qcom HS-USB 9008. honestly a mmcblk0 backup would definitely help if anyone would want to backup and then pm me a link or something. I believe It got bricked by me switching to slot_b in fastboot mode with nothing on slot_b not even bootloader. Also my bootloader is unlocked and it was rooted with magisk at the Time of hard brick
sd_shadow said:
You already tried LMSA?
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
Click to expand...
Click to collapse
LSMA won't work because my phone won't turn on its stuck in emergency download mode and so LSMA doesn't even detect device
Hey guys I’ve been here once or twice before but it’s been a while. I have some in the ass and I need your help please. I’ve been working at unlocking the boot loader on my Motorola Moto G power 2021 for two months now. The reasoning is for that I have no PC nor desktop rather one of my old android phones (Motorola Moto G7 Optimo) That I have had, Trying to figure out how to unlock my boot loader on my Motorola Moto G power 2021. I managed to unlock the boot loader finally but now I’m having issues with trying to install TWRP. My question is is that is there another custom room that I can install with two androids connected to USB – C double cable? I’ve been waiting for a long time to get my phone routed, please help and thanks
If you have one android rooted with magisk, there is an ADB/Fastboot Magisk module that might work for that, but I've never actually tried it. But I'm pretty sure one would have to be rooted. Another option might be to install linux on your phone. I have manjaro linux installed on mine but, again, it is limited without root because of selinux policy. With root, that can be disabled.
I also just noticed adb and fastboot can be installed in termux without root with
pkg install android-tools
You might try that.
If it workS, then YES, you can root without pc. Just 2 Android phones and a doubLe type c cable.
bryzone25 said:
but now I’m having issues with trying to install TWRP.
Click to expand...
Click to collapse
Don't install the TWRP we have now. Just boot it to use it with adb shell commands or a mouse. If you install it you'll get a bootloop, Dude says. I had to use it to extract my kernel for rooting.
Aaaannd the story thickens…. I ended up unlocking the boot loader with the two android phones and a USB – C type. However when I tried to flash Magisk, it flip my phone into a boot loop. Now, Me being the rookie that I am and trying to progress far too quickly, I Have relocked my boot loader and now I have a message which says no valid operating system can be found, will not boot.
Can someone please put me out of my misery and just go ahead and say that I am screwed?
Try to unlock your bootlloader againDamn I can't even type in here. Fgn xda is throwing up an ad over the typing area every time I make a cursor. Ok it finally stopped as I took a screenshot.
Now why on earth are you people trying to relock your bootloaders? I've rarely heard of such a thing and only to try to claim warranty, but I've been here for 2 days and already found 2 people with relocked (possible) bricks on this phone. And there aren't even many people here yet. What gives?
Don't worry yet. I think you're in better shape than the other guy.
If you still have your unlock email try to unlock it again with the same code. If you don't, or that doesn't work run get_unlock_data again and request another code.
BTW, I've never done this twice. So it might not work. If it doesn't, there is another option. Just come back and tell us how it went.
What carrier is your phone?
arkansawdave74 said:
Try to unlock your bootlloader againDamn I can't even type in here. Fgn xda is throwing up an ad over the typing area every time I make a cursor. Ok it finally stopped as I took a screenshot.
Now why on earth are you people trying to relock your bootloaders? I've rarely heard of such a thing and only to try to claim warranty, but I've been here for 2 days and already found 2 people with relocked (possible) bricks on this phone. And there aren't even many people here yet. What gives?
Don't worry yet. I think you're in better shape than the other guy.
If you still have your unlock email try to unlock it again with the same code. If you don't, or that doesn't work run get_unlock_data again and request another code.
BTW, I've never done this twice. So it might not work. If it doesn't, there is another option. Just come back and tell us how it went.
What carrier is your phone?
Click to expand...
Click to collapse
arkansawdave74 said:
so yeah I tried it again but the boot loader is still locked however I think the partitions are messed up after I was trying to flash magic and it fell right into a boot loop. Somehow it has actually gotten better and not continuously boot looping I can stay in fast boot but it won’t burn into anything else or power off unless it runs out of battery. But I do have the same code but it’s not taking hit it because OEM unlocking on developer mode is still locked.
Click to expand...
Click to collapse
So what other plans do you have I’m very curious to know? Also I am through straight talk on a TracFone. I’m also trying to unlock the boot loader on my Moto G7 optimo and I’ve tried the unlock data through Motorola and it says it can’t be unlocked but I think that’s b******t
Bry2025 said:
I’ve tried the unlock data through Motorola and it says it can’t be unlocked but I think that’s b******t
Click to expand...
Click to collapse
That used to happen to me a lot in the olden days when I used Windows and would manually type the code. I never know if they are Os or zeros. Now that I use linux I just copy/paste the code quick and easy. If you know that phone with that carrier can be unlocked, keep trying. In Android I know you can copy/paste from the terminal. I hear some carriers make you wait so long before unlocking too, although I've never had a phone with that problem. A good friend told me just the other day he had a Boost phone that they made him wait 6 months to unlock.
As far as plans, I got this phone by accident and dropped and broke the screen the 1st day I had it, before the case arrived. When the case arrived, it was a case for the G9 Power, which I thought this phone was when I ordered it. So, next month I will order the G9 Power since I already have a case and screen protector for it. My last phone was the G8 Stylus (sofiap) and this "Power" just doesn't have the same great battery life. I also had the G7 Power (ocean) and it had excellent battery life. I meant to get the G9 Power for the 6000 mAh battery, but with it's higher resolution screen it's probably no better than this Power. I think all "Power"s should have a 720P screen for the better battery life. or at least a switch to select the resolution you want like on my Galaxy S7.
This phone needs some ROMs though, so if I can find the time, I will do my best to give it a couple, if luck is on my side. Maybe a Resurrection Remix and a crDroid or Bliss. But really, it's whatever I can get to build, so maybe none. Lol.
Bry2025 said:
So what other plans do you have I’m very curious to know? Also I am through straight talk on a TracFone. I’m also trying to unlock the boot loader on my Moto G7 optimo and I’ve tried the unlock data through Motorola and it says it can’t be unlocked but I think that’s b******t
Click to expand...
Click to collapse
I think there's still hope for you. I'm trying to figure out which stock firmware version your phone came with. If we can figure that out, I think you can flash and boot it even with a locked bootloader. What splash screen and boot animation does it have? Is it tracphone? I see a US Cellular version. When you boot to the bootloader what does the 1st white line say on the lower left? The BL line?
Also, I assume you got fastboot working phone to phone. I've tried 3 different adb/fastboot installations and can't get it to work (Magisk module, the one from termux pkg install android-tools, and one from github.). Can you tell me how you did it?
arkansawdave74 said:
That used to happen to me a lot in the olden days when I used Windows and would manually type the code. I never know if they are Os or zeros. Now that I use linux I just copy/paste the code quick and easy.
Click to expand...
Click to collapse
I've used copy and paste on windows to unlock several moto devices.
It's the only sane way to do it.
sd_shadow said:
I've used copy and paste on windows to unlock several moto devices.
It's the only sane way to do it.
Click to expand...
Click to collapse
Yeah, I hear there is some trick to do it. Maybe in the new powershell (I've never tried it), but highlighting some text and right clicking to copy doesn't work in a command prompt, or it didn't 6 years ago. Did they add that functionality?
arkansawdave74 said:
Yeah, I hear there is some trick to do it. Maybe in the new powershell (I've never tried it), but highlighting some text and right clicking to copy doesn't work in a command prompt, or it didn't 6 years ago. Did they add that functionality?
Click to expand...
Click to collapse
I think I used copy/paste in cmd.exe since windows 7, but I don't know when it started working.
Well Damn....now I have one less way to insult Windows. Hey @sd_shadow , you would sure know...can you flash and boot the original firmware that came on your phone (same software channel) with a locked bootloader? Seems like you could but I've never tried it.
And @Bry2025 do you have USB Debugging enabled in Developer Options?
arkansawdave74 said:
Well Damn....now I have one less way to insult Windows. Hey @sd_shadow , you would sure know...can you flash and boot the original firmware that came on your phone (same software channel) with a locked bootloader? Seems like you could but I've never tried it.
And @Bry2025 do you have USB Debugging enabled in Developer Options?
Click to expand...
Click to collapse
Moto devices can be finicky.
You should be able to flash stock firmware with fastboot, but on windows rsd lite or the newer lsma work more reliably.
On windows mfastboot sometime works when standard fastboot.exe doesn't.
Linux may work better.
USB debugging doesn't effect fastboot mode, it's an adb function.
Edit:for locked bootloader
Booting stock .img may work for some devices
sd_shadow said:
USB debugging doesn't effect fastboot mode, it's an adb function.
Click to expand...
Click to collapse
Yes, but I was going to have him run
adb shell getprop | grep build.version.base
to figure out the software channel he needs. With the output I could find the exact build he is/was running on lolinet. That's hoping his bootloop is booting far enough for adb to enable though. adb shell wont work from stock recovery and adb shell from the quamp twrp we're using returns guamp device info. Wtf?
sd_shadow said:
On windows mfastboot sometime works when standard fastboot.exe doesn't.
Linux may work better.
Click to expand...
Click to collapse
On Linux fastboot seems to be flawless. I'm surprised to hear that it has trouble on Windows. But I think he's running fastboot from another android., which is so cool. Opens a door for root with no pc.
arkansawdave74 said:
I think there's still hope for you. I'm trying to figure out which stock firmware version your phone came with. If we can figure that out, I think you can flash and boot it even with a locked bootloader. What splash screen and boot animation does it have? Is it tracphone? I see a US Cellular version. When you boot to the bootloader what does the 1st white line say on the lower left? The BL line?
Also, I assume you got fastboot working phone to phone. I've tried 3 different adb/fastboot installations and can't get it to work (Magisk module, the one from termux pkg install android-tools, and one from github.). Can you tell me how you did it?
Click to expand...
Click to collapse
arkansawdave74 said:
I think there's still hope for you. I'm trying to figure out which stock firmware version your phone came with. If we can figure that out, I think you can flash and boot it even with a locked bootloader. What splash screen and boot animation does it have? Is it tracphone? I see a US Cellular version. When you boot to the bootloader what does the 1st white line say on the lower left? The BL line?
Also, I assume you got fastboot working phone to phone. I've tried 3 different adb/fastboot installations and can't get it to work (Magisk module, the one from termux pkg install android-tools, and one from github.). Can you tell me how you did it?
Click to expand...
Click to collapse
My Moto G power of 2021 is the one that I unlocked the boot loader with the code off of the Motorola site and then I tried to mess with Magis and it ended up boot looping so I tried to lock it again thinking that would help somehow and that’s where I’m at on that one. On the Moto G7 optimo I haven’t gotten anywhere with that one yet however I did get I haven't gotten anywhere with that one yet however I did get the Unlock data and put it on Motorola site and it said it can’t be unlocked. Also sorry but I’m new to this so I don’t understand about the splash screen and boot animation so please let me know what I need to do to give you that information.
Now with the phone to phone android to android, are used the Google app BUGJAEGER 3.0-full (164). Are used the command: fastboot oem unlock <unlock code> . And it unlocked right away.
arkansawdave74 said:
Well Damn....now I have one less way to insult Windows. Hey @sd_shadow , you would sure know...can you flash and boot the original firmware that came on your phone (same software channel) with a locked bootloader? Seems like you could but I've never tried it.
And @Bry2025 do you have USB Debugging enabled in Developer Options?
Click to expand...
Click to collapse
I just got a laptop and I’m going to attempt to use the command prompt and copy and paste to see if I can get the unlock code for my G7 optimo but on the Moto G power of 2021, I did have all of it unlocked but now since my dumbass locked the boot loader again I can’t get back on the initial platform and get developer tools. If I can get the OEM unlocking toggled back on I probably can unlock it reflash the firmware and boot my phone again
<EVERYONE>
Just to recap, my Motorola Moto G power 2021 is Bootloader locked after Magisk Installation failure. I have messed around with it and have it stuck in Fastboot Mode after it was stuck in bootloop. Some progress but the boot loader is locked again because of a error of mine and now it will not take my unlock code that I used before. Mind you, I did all of this between two android phones and an app called BUGAEGER That is available on Google play
Hisense just released a new device called the A9. Since this phone has Snapdragon 662 I was wondering how easy it would be to root this device. I know there is an EDL for this CPU. The Hisense A5 series was also rootable. Not sure what method was used.
The Onyx Boox Note Air 2 (a 10.3" tablet), which I have, also runs on the same Snapdragon 662 and can be rooted via Magisk. I used the EDL to dump the boot.img on the Note Air 2 to root it via Magisk.
Disclaimer: I'm not a developer or super technical guy, but have rooted a few devices by following guides.
Does anyone know how easy or fast a root would be available? I'm assuming they didn't lock the bootloader on this device as most Chinese devices.
Hello, could you share with us how to root boox device please?
It would be great if GAPPS could be used.
Replying to bump this thread. I have the Hisense A9 and would love to be able to root. It has an option to unlock the bootloader in the developer options if that is helpful.
formeriphoneuser said:
Does anyone know how easy or fast a root would be available? I'm assuming they didn't lock the bootloader on this device as most Chinese devices.
Click to expand...
Click to collapse
Hello and good morning, @formeriphoneuser
I hope you'll always find and get the support you require.
However, prior to your next posting please read the guidances that are stuck on top of every forum like
[Read Before Posting]QUESTIONS DO NOT BELONG IN GENERAL
Hello Everybody, In order to attempt to keep this forum neat and tidy the moderation team is asking you to post your questions into the Questions and Answers (Q&A) forum and not into the General section. You can find the Q&A forum by clicking...
forum.xda-developers.com
and the others. I've moved the thread to Android Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
I recently good a Hisense A9, and I've been trying to extract the boot.img and / or recovery.img from it (since I can't find either of those online yet). So far I've been trying to get boot.img from EDL mode using this EDL tool. I can boot into EDL mode fine, but when I try to run an EDL command there are lots of errors. It's possible I'm using the wrong Firehose file, but I think it's right. (I'll post a link to the logs below). I've been following this guide mainly. Is anyone else working on this?
*Edit* the firehose file I'm using is 0014d0e100000000_d40eee56f3194665_FHPRG.bin.
Anyway, OP - hopefully I, or someone, can get the boot image or recovery image soon, then we should be able to patch it with Magisk fairly easily and install Google Services etc.
A word of warning to anyone who wants to try working on this - every time I restart after being in EDL mode, the phone goes into a boot loop of sorts. I enter the 6-digit pin at boot-up, and the phone says something in Chinese (which Google translates as something like "optimising the system, please wait", from memory), and then keeps showing the desktop screen for a second, then looping back to the pin code input, then showing the message, and then repeat. If you hold down volume down, it'll go into safe mode, but then the same thing happens when you restart. I've always managed to get out of it, but I'm not 100% sure how! Something like holding the power key down for about 10 seconds while it's looping... The phone vibrates, but doesn't turn off, and then the loop stops and you can enter your 6-digit pin again and it's back to normal. If that doesn't work, then try turning the phone off, then back on again, but holding the power key down so it keeps restarting without fully booting. Last time I made it restart ~5 times, and then it was back to normal. Maybe it cleared some kind of system cache...?
These are the errors I get from the EDL tool when I try to extract the boot image.
https://pastebin.com/ejXfCJs9
https://pastebin.com/5CqUPB0a
https://pastebin.com/LMmEmm6v
RunnyYolk said:
I recently good a Hisense A9, and I've been trying to extract the boot.img and / or recovery.img from it (since I can't find either of those online yet). So far I've been trying to get boot.img from EDL mode using this EDL tool. I can boot into EDL mode fine, but when I try to run an EDL command there are lots of errors. It's possible I'm using the wrong Firehose file, but I think it's right. (I'll post a link to the logs below). I've been following this guide mainly. Is anyone else working on this?
Anyway, OP - hopefully I, or someone, can get the boot image or recovery image soon, then we should be able to patch it with Magisk fairly easily and install Google Services etc.
A word of warning to anyone who wants to try working on this - every time I restart after being in EDL mode, the phone goes into a boot loop of sorts. I enter the 6-digit pin at boot-up, and the phone says something in Chinese (which Google translates as something like "optimising the system, please wait", from memory), and then keeps showing the desktop screen for a second, then looping back to the pin code input, then showing the message, and then repeat. If you hold down volume down, it'll go into safe mode, but then the same thing happens when you restart. I've always managed to get out of it, but I'm not 100% sure how! Something like holding the power key down for about 10 seconds while it's looping... The phone vibrates, but doesn't turn off, and then the loop stops and you can enter your 6-digit pin again and it's back to normal. If that doesn't work, then try turning the phone off, then back on again, but holding the power key down so it keeps restarting without fully booting. Last time I made it restart ~5 times, and then it was back to normal. Maybe it cleared some kind of system cache...?
These are the errors I get from the EDL tool when I try to extract the boot image.
https://pastebin.com/ejXfCJs9
https://pastebin.com/5CqUPB0a
https://pastebin.com/LMmEmm6v
Click to expand...
Click to collapse
Maybe try this loader. This is for sure the one I used for my NA2. Otherwise, you have quite some errors that relate to python. Not sure what the issue is there.
formeriphoneuser said:
Maybe try this loader. This is for sure the one I used for my NA2. Otherwise, you have quite some errors that relate to python. Not sure what the issue is there.
Click to expand...
Click to collapse
Awesome, thanks! I should have mentioned which loader I was using (different to the one you linked). I'll edit my post to say what I used before.
I tried the loader that @formeriphoneuser suggested, but with a similar result. (https://pastebin.com/ucMkEkeW). I also tried with the flag --memory="ufs" in case the device has UFS memory, but similar result.
But the good new is, I've just discovered a reliable way to avoid the boot loop after leaving EDL mode. So to leave EDL mode, make sure any running commands have ended, unplug the device from the computer, and press and hold the eink button (on the left of the phone), volume-up, and power button. Keep them all pressed until the first vibration (after about 15 seconds or so, then release the power button only). Keep the other two pressed while the phone boots, and even while you're entering your 6 digit pin code. When you see the main screen you can release the buttons and your phone shouldn't enter the boot loop. I have no idea how much of that is necessary, but something in there works for me.
I've added an Issue to the github repo for the EDL tool I'm using. Other than that, I think I've hit a brick wall and won't be able to do any more for now. Unless anyone knows how to check that the firehose file is correct for my device, and update it if it's not. Hopefully Hisense will release the stock firmware, or send us an OTA update or something.
Does this work? if the Bootloader could be unlocked.
Arthurliao said:
Does this work? if the Bootloader could be unlocked.
Click to expand...
Click to collapse
The problem with a GSI is that Android doesn't have partial refresh support for the eInk display, which means a driver has to be written from scratch, otherwise the display will be verrrrrry slow.
RunnyYolk said:
I tried the loader that @formeriphoneuser suggested, but with a similar result. (https://pastebin.com/ucMkEkeW). I also tried with the flag --memory="ufs" in case the device has UFS memory, but similar result.
But the good new is, I've just discovered a reliable way to avoid the boot loop after leaving EDL mode. So to leave EDL mode, make sure any running commands have ended, unplug the device from the computer, and press and hold the eink button (on the left of the phone), volume-up, and power button. Keep them all pressed until the first vibration (after about 15 seconds or so, then release the power button only). Keep the other two pressed while the phone boots, and even while you're entering your 6 digit pin code. When you see the main screen you can release the buttons and your phone shouldn't enter the boot loop. I have no idea how much of that is necessary, but something in there works for me.
I've added an Issue to the github repo for the EDL tool I'm using. Other than that, I think I've hit a brick wall and won't be able to do any more for now. Unless anyone knows how to check that the firehose file is correct for my device, and update it if it's not. Hopefully Hisense will release the stock firmware, or send us an OTA update or something.
Click to expand...
Click to collapse
Bit of a long shot here, but I vaguely remember having trouble with EDL on my Oneplus 6T and I think the solution was to use a USB2 port instead of USB3.
RunnyYolk said:
I tried the loader that @formeriphoneuser suggested, but with a similar result. (https://pastebin.com/ucMkEkeW). I also tried with the flag --memory="ufs" in case the device has UFS memory, but similar result.
But the good new is, I've just discovered a reliable way to avoid the boot loop after leaving EDL mode. So to leave EDL mode, make sure any running commands have ended, unplug the device from the computer, and press and hold the eink button (on the left of the phone), volume-up, and power button. Keep them all pressed until the first vibration (after about 15 seconds or so, then release the power button only). Keep the other two pressed while the phone boots, and even while you're entering your 6 digit pin code. When you see the main screen you can release the buttons and your phone shouldn't enter the boot loop. I have no idea how much of that is necessary, but something in there works for me.
I've added an Issue to the github repo for the EDL tool I'm using. Other than that, I think I've hit a brick wall and won't be able to do any more for now. Unless anyone knows how to check that the firehose file is correct for my device, and update it if it's not. Hopefully Hisense will release the stock firmware, or send us an OTA update or something.
Click to expand...
Click to collapse
Also, looking at your pastebins, It seems you are running Ubuntu via a Parallels Virtual Machine. I would suggest using the LiveDVD from the EDL github repo and running it on bare metal to rule out any system related issues. Given that the pastebins show errors relating to libusb1.py, there is a good chance your issues are due to the emulated USB controller provided by Parallels.
matteqa said:
Also, looking at your pastebins, It seems you are running Ubuntu via a Parallels Virtual Machine. I would suggest using the LiveDVD from the EDL github repo and running it on bare metal to rule out any system related issues. Given that the pastebins show errors relating to libusb1.py, there is a good chance your issues are due to the emulated USB controller provided by Parallels.
Click to expand...
Click to collapse
I tried booting the liveDVD from the repo in Parallels, but it wouldn't boot, saying something like Ubuntu was missing. But I'll try it as a bootable USD drive. I won't be able to do it until next weekend at the earliest, but I'll report back when I've tried that method. Thanks for your suggestions!
So I bought a USB drive and flashed the liveDVD from the repo to it, but my only computers are Macs and will recognise the USB drive as bootable - I've tried Fat32 / HFS+ file systems, made sure it's a GUID partition table, and used both Etcher GUI and terminal's `dd` to burn the image to the drive, but still the USB never shows up in the startup utility. Anyway, I've hit a roadblock on this for now - I think my next options are to either pick up a cheap Windows laptop, or put a bounty out for boot.img (or preferably full root! )
RunnyYolk said:
So I bought a USB drive and flashed the liveDVD from the repo to it, but my only computers are Macs and will recognise the USB drive as bootable - I've tried Fat32 / HFS+ file systems, made sure it's a GUID partition table, and used both Etcher GUI and terminal's `dd` to burn the image to the drive, but still the USB never shows up in the startup utility. Anyway, I've hit a roadblock on this for now - I think my next options are to either pick up a cheap Windows laptop, or put a bounty out for boot.img (or preferably full root! )
Click to expand...
Click to collapse
Just checking, have you tried the macOS version of the EDL tool? All of your pastebins are from ubuntu parallels, however there is also a native macOS version in the github repo.
matteqa said:
Just checking, have you tried the macOS version of the EDL tool? All of your pastebins are from ubuntu parallels, however there is also a native macOS version in the github repo.
Click to expand...
Click to collapse
Ah, that's a good call! I did try the native Mac version on one machine, but it wasn't able to find libusb library, so I started using parallels / ubuntu, and then basically forgot that the native mac version existed! So thanks for the reminder - I tried it yesterday on an older Mac, and the native EDL client seems to be working properly. Unfortunately I think the firehose / loader files I have aren't correct. When I ran it with a loader I get sahara - [LIB]: Unexpected error on uploading, maybe signature of loader wasn't accepted ?
type object 'req' has no attribute 'image_id', and then I tried running it without any loader and got sahara - [LIB]: Couldn't find a loader for given hwid and pkhash (0014d0e100430000_56d3f3c74a52172b_[FHPRG/ENPRG].bin) :(.
So I guess we need the correct loader for the A9. I'm pretty clueless about how these files come to exist in the first place (do they have to come from the manufacturer, or can we build them ourselves?), but anyway I'll open a new issue on Github and see if the developer of the client can help.
For completeness' sake, here are logs from each attempt at reading boot_a (I tried three different loaders, each one with and without --skipresponse, and then once with no loader).
https://pastebin.com/AA9d5Tdh
https://pastebin.com/gXHS9pYN
https://pastebin.com/6e5FeWDc
https://pastebin.com/8dGWFNau
https://pastebin.com/iTd8ZsVH
https://pastebin.com/2esPvxyX
https://pastebin.com/Pvz9YxfE
https://pastebin.com/D47mPKt6
*edit* This is the issue on Github: https://github.com/bkerler/edl/issues/303
RunnyYolk said:
Ah, that's a good call! I did try the native Mac version on one machine, but it wasn't able to find libusb library, so I started using parallels / ubuntu, and then basically forgot that the native mac version existed! So thanks for the reminder - I tried it yesterday on an older Mac, and the native EDL client seems to be working properly. Unfortunately I think the firehose / loader files I have aren't correct. When I ran it with a loader I get sahara - [LIB]: Unexpected error on uploading, maybe signature of loader wasn't accepted ?
type object 'req' has no attribute 'image_id', and then I tried running it without any loader and got sahara - [LIB]: Couldn't find a loader for given hwid and pkhash (0014d0e100430000_56d3f3c74a52172b_[FHPRG/ENPRG].bin) :(.
So I guess we need the correct loader for the A9. I'm pretty clueless about how these files come to exist in the first place (do they have to come from the manufacturer, or can we build them ourselves?), but anyway I'll open a new issue on Github and see if the developer of the client can help.
For completeness' sake, here are logs from each attempt at reading boot_a (I tried three different loaders, each one with and without --skipresponse, and then once with no loader).
https://pastebin.com/AA9d5Tdh
https://pastebin.com/gXHS9pYN
https://pastebin.com/6e5FeWDc
https://pastebin.com/8dGWFNau
https://pastebin.com/iTd8ZsVH
https://pastebin.com/2esPvxyX
https://pastebin.com/Pvz9YxfE
https://pastebin.com/D47mPKt6
*edit* This is the issue on Github: https://github.com/bkerler/edl/issues/303
Click to expand...
Click to collapse
Have you tried to read from "boot" instead of "boot_a". Maybe hisense isn't using A/B partitions since they don't care about google play certification. Also, have you tried using --memory=ufs.
Otherwise, it may be that the loader has a custom signature. As far as I know, the loader is proprietary and you have to get it from the manufacturer.
@RunnyYolk
I've also just found a patched version of a SDM662 loader on another forum that might work.
I've reuploaded it here: https://cloud.matteqa.com/index.php/s/M6MxgPFDsYwaKP6
matteqa said:
@RunnyYolk
I've also just found a patched version of a SDM662 loader on another forum that might work.
I've reuploaded it here: https://cloud.matteqa.com/index.php/s/M6MxgPFDsYwaKP6
Click to expand...
Click to collapse
Thanks! I tried this loader, and also the --memory=ufs flag / "boot" alternatives as you suggested, but had the same errors as before. I'm pretty sure I saw boot_a and boot_b directories somewhere when I was exploring the filesystem in adb shell, but I'll double check again when I have time.
Are there any other avenues I could try to root this device? I wonder if there's any point trying to boot TWRP from an A7? Am I right in thinking I can `fastboot boot recover.img` without risk of bricking the phone? (Ie just booting rather than flashing.)... Maybe I'm clutching at straws...
The Issue:
The phone is constantly booting looping (flashes the Oneplus logo).I am unable to go to fastboot through either adb or through the on-phone buttons.
When plugged into a charger, it immediately begins to bootloop once enough power is supplied.
The only way to turn it off is by letting it get to 0%.
What caused the issue:
My phone got soft bricked all of a sudden, so I followed some tutorials that I found online showing me how to flash firmware using adb in fastboot and by unlocking my bootloader. This temporarily fixed the issue, but it told me that after doing everything I should relock it through ADB. Foolishly, I did so and am now stuck in this situation.
What I've tried:
I am able to get into EDL mode by holding both volume buttons, even while in the boot loop state.
I have downloaded the latest version of QPST and this firmware file (https://firmwarefile.com/oneplus-10t-5g-cph2415).
Quick note: I'm not sure if that's how it's meant to be, but QPST always detects my phone as "Download" (ESN: Download, Phone Number: Download, Banner: Download).
I am not quite sure how to use QPST and have tried following the guide, which told me to select some.hex files from the firmware I downloaded, but I was unable to find any.hex files at all and therefore could not proceed.
I also tried QFIL by selecting prog_firehose_ddr.elf from the IMAGES folder and tried multiple times in both UFS and emmc mode, selecting all of the rawprogram 1-5.xml files with their corresponding patch1-5.xml files from the IMAGES folder, but I always got the same error:
ERROR: function: sahara_rx_data:276 Unable to read packet header. Only read 0 bytes
ERROR: function: sahara_main:982 Sahara protocol error
ERROR: function: main:320 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Fail process fail
Finish Download
I have tried the leaked EDL flasher from here: https://forum.xda-developers.com/t/edl-flash-tool-leak.4494211/. However, I have been unsuccessful in doing so, though I may have been doing it wrong, and it would be greatly appreciated if someone could explain or tell me how to do it. As you can see in the attached image, I tried to flash it by using the images folder located in the firmware that I have downloaded. But it just gets stuck at 3%
indefinitely as the time goes up forever.
Thanks for reading looking forward to any replies/info
uh do not flash it by qfil it will just not work because oneplus actually blocked qfil and qpst so the only way is their edl tool and you cannot flash it on the edl tool unless you have an (actual) account and (not) bypassed
oneplus is really starting to nerve me really their merge with oppo is like a mistake
oneplushypergaming said:
oneplus is really starting to nerve me really their merge with oppo is like a mistake
Click to expand...
Click to collapse
the Merge was a mistake, its laughable that OnePlus went from being with the opensource community to being completely against it.. What annoys me the most is, instead of just locking their bootloader, they post the source code for their phone, probably as they have to, yet they give no way to utilize that code without developers running the risk of bricking their device.. Developers are willing to dedicate their time and money, to build for a device, all they ask, is for the ability to be able to unbrick, that is humble, Devs ask for donations, they do not force it.. Oppo do not even allow their bootloader to be unlocked, which prevents users from bricking their device.. OnePlus allow users to unlock their bootloader, knowing full well that Developers will understandably not be willing to develop for a device without a potential 60-80% brick chance.. The code could very well build for said rom, but once flashed it has the potential to turn the dev's device into a paper weight, meaning something they do to provide, turns into something that ultimately takes..
hosthere247 said:
the Merge was a mistake, its laughable that OnePlus went from being with the opensource community to being completely against it.. What annoys me the most is, instead of just locking their bootloader, they post the source code for their phone, probably as they have to, yet they give no way to utilize that code without developers running the risk of bricking their device.. Developers are willing to dedicate their time and money, to build for a device, all they ask, is for the ability to be able to unbrick, that is humble, Devs ask for donations, they do not force it.. Oppo do not even allow their bootloader to be unlocked, which prevents users from bricking their device.. OnePlus allow users to unlock their bootloader, knowing full well that Developers will understandably not be willing to develop for a device without a potential 60-80% brick chance.. The code could very well build for said rom, but once flashed it has the potential to turn the dev's device into a paper weight, meaning something they do to provide, turns into something that ultimately takes..
Click to expand...
Click to collapse
Well said to be honest that clears my suspicion about oppo they are greedy and dirty and maybe it is oppo who is making oneplus act like this in the first place oneplus should really consider all of this and give the people what they want instead of being a monopoly like oppo i never even liked oppo from the beginning actually i trusted oneplus with my 7t because i knew if i were to brick it the msm tool will always be there it has been months since the release of the 10t and ace pro and yet still no msm tool for it or a way to even get it back yet but there are many msm tools for the rest of the oneplus devices so maybe i am wrong they can tell us but i still think it is wrong that th 10 pro has to have an actual account.
I'm stuck with a Hard Brick and my device screen is black, only entering EDL for a few seconds.
Qmiclient it's the new MSM
AkayamiShurui said:
Qmiclient it's the new MSM
Click to expand...
Click to collapse
Hello , I found this topic because i'm facing the same problem as OP after relocking bootloader .... As anyone found solution to flash on edl mode ? Thanks
mybrickplus said:
Hello , I found this topic because i'm facing the same problem as OP after relocking bootloader .... As anyone found solution to flash on edl mode ? Thanks
Click to expand...
Click to collapse
the only thing i can think of is a slot switch
Yes Probably what happened but now i'm totally stuck on the bootloop until no baterry left.
Cant access fastboot because the phone boot and 2 seconds later reboot ... I can only access edl mode with Oneplus Flasher (bypassed by Hexa change) but after that, like op described the time keep increasing ,and circle progress stays at 3%, nothing seems change on phone
You have no option but to use the official flashing revovery via Oneplus / oppo whoever does it which means paying them to reflash the phone correctly
Ok thank you, so ive to send back the phone or i can do it on my own ?
mybrickplus said:
Ok thank you, so ive to send back the phone or i can do it on my own ?
Click to expand...
Click to collapse
no need to send the phone to oneplus just contact them directly and arrange for one of their techs to reflash your phone over the internet
leezaal said:
no need to send the phone to oneplus just contact them directly and arrange for one of their techs to reflash your phone over the internet
Click to expand...
Click to collapse
He could try but I'm not that sure that they are continuing to offer this service.
Thank you for your help and answers
So anyone who still watching this thread I made progress on this whole problem I took the 11r firmware file and it has script.sh commands in there and I ran them and it extracted all of the firmware files and made a bin folder that has only two folders inside of it and it took all the files to make it it puts it in your recovery section of your computer but it compiled all the empty files so they actually have things on them if you want to know how I did it and what I used just private message me cuz I will not be posting public because Oppo