MOTO E xt1022 Hard bricked - Moto E Q&A, Help & Troubleshooting

I had rooted my phone which is MOTO E (first generation)XT 1022. After rooting my phone i degraded my phone from lollipop to kitkat 4.4.2. Then I updated my phone to kitkat 4.4.2 to kitkat 4.4.4. After doing that process my phone hard bricked. I tried to recover my phone from hard brick situation but i could not but after running blankflash.bat file "failed <blank-flash:greet device:error reading packets> "is shown. please help me !
I have followed given approach:
What is A Brick?
A Brick Usually Occurs when you Flash a Wrong Firmware on your device or you try to downgrade your bootloader. In both the cases if you see nothing but a blank screen and "qhsusb_bulk" when connecting to the computer (Check Devices and Printers on your PC) .
Prerequisites
Stock Moto E Firmware of your Choice
Motorola USB Drivers
MFastbootv2
Blanflash
RiffBox JTAG Drivers
INSTRUCTIONS
If you have A 64-Bit Processor you'll need to disable driver signature Enforcement. Press F8 while the computer is booting and then choose the option.
Go To Start and search for Device Manager
Plug in your Moto e
You'll See qhsusb_bulk
Now select update driver Software
Choose from the Riffbox Jtag Drivers.
Now you'll see Qualcomm HS-USB QLoader 9008
Unzip the motorola qboot utility and run blankflash.bat
Now Enter into fastboot from your Moto e
You can now flash the firmwares compatible with your bootloader version

kaushalg16 said:
I had rooted my phone which is MOTO E (first generation)XT 1022. After rooting my phone i degraded my phone from lollipop to kitkat 4.4.2. Then I updated my phone to kitkat 4.4.2 to kitkat 4.4.4. After doing that process my phone hard bricked. I tried to recover my phone from hard brick situation but i could not but after running blankflash.bat file "failed "is shown. please help me !
I have followed given approach:
What is A Brick?
A Brick Usually Occurs when you Flash a Wrong Firmware on your device or you try to downgrade your bootloader. In both the cases if you see nothing but a blank screen and "qhsusb_bulk" when connecting to the computer (Check Devices and Printers on your PC) .
Prerequisites
Stock Moto E Firmware of your Choice
Motorola USB Drivers
MFastbootv2
Blanflash
RiffBox JTAG Drivers
INSTRUCTIONS
If you have A 64-Bit Processor you'll need to disable driver signature Enforcement. Press F8 while the computer is booting and then choose the option.
Go To Start and search for Device Manager
Plug in your Moto e
You'll See qhsusb_bulk
Now select update driver Software
Choose from the Riffbox Jtag Drivers.
Now you'll see Qualcomm HS-USB QLoader 9008
Unzip the motorola qboot utility and run blankflash.bat
Now Enter into fastboot from your Moto e
You can now flash the firmwares compatible with your bootloader version
Click to expand...
Click to collapse
You're device is hard bricked (as you know ) & can only be recovered by changing the motherboard by Motorola which will cost you about 2/3 of original price. So your right choice would be to buy a new phone.
WORD OF CAUTION- Never accept any ota updates after you mess up with your bootloader, recovery, root etc. Wait for an official firmware release.
You should've searched a little bit before clicking on that tempting "yes, I'm in" button. There are so many of users just like u who bricked the device in the same way.
I know it feels bad to hear but there's nothing you can do abt it so, chill.✌

You should've researched more :
http://forum.xda-developers.com/moto-e/general/warning-downgrading-information-moto-e-t3062859

it's right there in the general section as a sticky post... that degrading to 4.4.2 and OTAing to 4.4.4 will surely brick the phone..... still I don't know why people make this mistake....

MOTO E Xt1022
booo159159 said:
it's right there in the general section as a sticky post... that degrading to 4.4.2 and OTAing to 4.4.4 will surely brick the phone..... still I don't know why people make this mistake....
Click to expand...
Click to collapse
hi...please tell me another way by which i could save my phone. Is there another way to recover the phone or change the mother board.. Please help me..

There's no other way except changing the motherboard.

kaushalg16 said:
hi...please tell me another way by which i could save my phone. Is there another way to recover the phone or change the mother board.. Please help me..
Click to expand...
Click to collapse
where are YOU gonna find another motherboard? moreover HOW are you gonna change the motherboard?
only service centre have the ability and prerequisites to do that..
there is no method to unbrick our hardbricked condor (xt1022) motorola moto e.
i hate to break this to you but you phone is screwed (you're not alone, though).
there's this one guy who claims that he succesfully unbricked his phone but he is LAZY AF to make a post
http://forum.xda-developers.com/moto-e/general/guide-moto-e-hardbrick-fixing-guide-t3350387
i am talking about you @Harsh_1998 help the guys out here, will ya?

even i bricked my device...i think blank flash will solve it..can someone help me out?
QUOTE=ALPHAWolf96;66412566]You're device is hard bricked (as you know ) & can only be recovered by changing the motherboard by Motorola which will cost you about 2/3 of original price. So your right choice would be to buy a new phone.
WORD OF CAUTION- Never accept any ota updates after you mess up with your bootloader, recovery, root etc. Wait for an official firmware release.
You should've searched a little bit before clicking on that tempting "yes, I'm in" button. There are so many of users just like u who bricked the device in the same way.
I know it feels bad to hear but there's nothing you can do abt it so, chill.[/QUOTE]

hi..,
i rooted my device moto xt1022 and flashed cm13. my phone got soft bricked when i was updating to other update of cm13. then i downgraded my device to kitkat. after few days my sim was not being detected and also battery started to drain fast so i turned off my phone and didn't use my phone for two weeks. now when my device charged with difficulty and when it's turned on it displayed the message "unfortunately android.phone stopped" also similar messages appeared from keyboard app...they were appearing for every second hence i thought of changing the software and i powered off my device. when i tried to go to recovery mode it didn't respond NOT EVEN TURNING ON,, i think my device is hard bricked can anyone help me......??

Related

Flashed a corrupt preloader on MediaTek device. Should I say RIP or not?

Apparently sometimes it's not the best idea to use the flashing software that the manufacturer of your phone released.
I have a Wiko Lenny(technically a MediaTek MT6572) that has(or had - now it's dead) the habit of simply rebooting into a bootloop every few months. Fixing that was simple; just start SP Flash Tool, format everything then flash the stock ROM back. Last time I did that was around 4 months ago, and since then I have upgraded to Windows 10, and as such, lost the tools I had installed.
Yesterday it went into a bootloop again. I didn't remember exactly what tools I used, so I assumed they were the tools that Wiko supplied a while back with the V10 ROM. Well, they weren't. I still thought I'd give them a try. I mean, it's from the manufacturer's site, so they must work even better that the ones I was using.
I was wrong. The tool flashed the ROM "successfully", but the only thing it actually succeeded to do is corrupt the preloader. For those who don't know, corrupting the preloader basically means the phone won't even power on(not boot, actually power on), won't charge, and the PC won't detect anything if you connect the phone. Practically, it's the hardest brick a phone can get.
The fastest way to fix that is by either using a JTAG connection to flash everything manually, or by entering something called the Mediatek META mode(don't quote me on this one, though - I never heard of it before). JTAG - well I don't have the tools or expertise necessary to do that(although I'd love to learn how to do it - if anyone can point me to a well-written guide or two about that, please do!), and I simply can't get the phone to enter the META mode.
Is JTAG the only way to do it? Is META mode just a myth? Is there a way to save my phone, or should I just say "RIP" and buy a new one(I have the money for a Samsung Galaxy A3, the new one, but I was planning to buy a new computer with that money - is it worth it?)?
TL;DR (It's not that long but anyway...):
I have a Wiko Lenny(Mediatek MT6572) with a corrupted preloader after I flashed it with Wiko's tool. Can I repair it or should I just buy a new phone?
Link to the culprit that killed my phone(AKA Wiko V10 ROM): https://docs.google.com/uc?id=0BzeAvoIC2yhHMTZESUU1Y3hUM0E
Come on people, let's fix this little guy.
EDIT: Please, just tell me what your ideas are... A tip, a crazy idea, some details about MTK devices that could help, anything is appreciated.
Please...
Looks like I'm getting the 10 posts just by begging people to say something... :crying:
I have an MTK phone and its always going wrong and not booting/turning on because I mess with it and break it
I'm sure I flash the backup I made in mtktools with spflash, and plug the phone in with no battery attached, I also have to use windows 7 on a dual boot as windows 10 never played ball properly. You also need the mtk VCOM driver installed, not just adb and normal drivers. If you have all these, and have tried them, then that is the end of my knowledge sadly. Only other thing is going to needrom and seeing if they have a full rom/backup with partition tables/preloader etc.
Also, had to try a few versions of sptools as certain versions didnt work, forget which one I have and which didnt work. And also had to use a samsung USB lead as the stock one didnt work, or the other way round. I just remember it was a ball-ache but did eventually work. Am not on that pc so cant be more helpful, sorry....
robneymcplum said:
I have an MTK phone and its always going wrong and not booting/turning on because I mess with it and break it
I'm sure I flash the backup I made in mtktools with spflash, and plug the phone in with no battery attached, I also have to use windows 7 on a dual boot as windows 10 never played ball properly. You also need the mtk VCOM driver installed, not just adb and normal drivers. If you have all these, and have tried them, then that is the end of my knowledge sadly. Only other thing is going to needrom and seeing if they have a full rom/backup with partition tables/preloader etc.
Also, had to try a few versions of sptools as certain versions didnt work, forget which one I have and which didnt work. And also had to use a samsung USB lead as the stock one didnt work, or the other way round. I just remember it was a ball-ache but did eventually work. Am not on that pc so cant be more helpful, sorry....
Click to expand...
Click to collapse
Thanks for replying. I'm not sure if I have the VCOM drivers, but I'll check. Luckily I also have a Win7 PC besides this one, so I'll try it there too.
You need to repair preloader. Contact me !
gsm-decode said:
You need to repair preloader. Contact me !
Click to expand...
Click to collapse
Please do a nice thing, and tell me how to repair it here. Maybe there will be people in the exact same situation...
Can't fix MIne too !
DragonSky87 said:
Please do a nice thing, and tell me how to repair it here. Maybe there will be people in the exact same situation...
Click to expand...
Click to collapse
I also got an android phone that is INTEX AQUA I5 hd , i was flashing my phone and unfortunatly my pc got off while flashing . And my preloader got currepted .
When i tries to flash my phone it connects to pc as Mediatek Viacom port , but after 3-4 sec it connects as a usb port .
I continuously gots connceted and dissconnected .
and my Sp flash tool shoes error " S_DA_SDMMC_READ_FAILED(3153) "
Can anybody help me with it ? please help me as soon as possible.
You need to flash preloader by Testpoint,after that flash rom.
Dont remember exactly the testpoint but you can try
DragonSky87 said:
Apparently sometimes it's not the best idea to use the flashing software that the manufacturer of your phone released.
I have a Wiko Lenny(technically a MediaTek MT6572) that has(or had - now it's dead) the habit of simply rebooting into a bootloop every few months. Fixing that was simple; just start SP Flash Tool, format everything then flash the stock ROM back. Last time I did that was around 4 months ago, and since then I have upgraded to Windows 10, and as such, lost the tools I had installed.
Yesterday it went into a bootloop again. I didn't remember exactly what tools I used, so I assumed they were the tools that Wiko supplied a while back with the V10 ROM. Well, they weren't. I still thought I'd give them a try. I mean, it's from the manufacturer's site, so they must work even better that the ones I was using.
I was wrong. The tool flashed the ROM "successfully", but the only thing it actually succeeded to do is corrupt the preloader. For those who don't know, corrupting the preloader basically means the phone won't even power on(not boot, actually power on), won't charge, and the PC won't detect anything if you connect the phone. Practically, it's the hardest brick a phone can get.
The fastest way to fix that is by either using a JTAG connection to flash everything manually, or by entering something called the Mediatek META mode(don't quote me on this one, though - I never heard of it before). JTAG - well I don't have the tools or expertise necessary to do that(although I'd love to learn how to do it - if anyone can point me to a well-written guide or two about that, please do!), and I simply can't get the phone to enter the META mode.
Is JTAG the only way to do it? Is META mode just a myth? Is there a way to save my phone, or should I just say "RIP" and buy a new one(I have the money for a Samsung Galaxy A3, the new one, but I was planning to buy a new computer with that money - is it worth it?)?
TL;DR (It's not that long but anyway...):
I have a Wiko Lenny(Mediatek MT6572) with a corrupted preloader after I flashed it with Wiko's tool. Can I repair it or should I just buy a new phone?
Link to the culprit that killed my phone(AKA Wiko V10 ROM): https://docs.google.com/uc?id=0BzeAvoIC2yhHMTZESUU1Y3hUM0E
Click to expand...
Click to collapse
Repair your own device
Soft Brick: Soft brick is the state of android device which occur due to some software problems like boot loops or phone freezing at some point during boot. This only occurs if some software problem occurred in the device mainly during OS upgrade or ROM flashing. If your device is in such state then you are luck there are 99% chances that you can recover your beloved device without needing any professional help or spending hundred of dollars.
Hard Brick Hard brick is the state of android device that occurs when your device won’t boot at all i.e. no boot loop,no recovery and also not charging. This occurs due to trying to flashed firmwere not made for your device or flashed incorrectly. This is more difficult to resolve and often require professional help
in MTK Android there is many Partitions in your phone. like Preloader, Recovery, Bootimg etc….. if somehow Preloader get Corrupted then you phone will not able to DETECT WITH PC !!! in other words you will have phone with BOOT DEAD.
How Preloader get corrupted ?
There could be few reasons but main reason could be that someone or you Flash your complete phone (include Preloader) with wrong files or with wrong ver. Also there could be reason someone Delete Preloader or you Deleted.
How could i know my phone have preloader dead ?
Preloader can be dead if some one Flash it wrong and after flash your mobile will not detect with pc any more. for confirm
1.sp flash tools does not detect your phone anymore and also the computer does not as there is a pop sound when usb is connected to device
2.open device manager
take battery out from phone
insert usb
insert battery
and check is computer detecting any device
If it’s not detect then you have phone which Preloader is dead AKA Boot Dead
How can i repair it ?
requirement
1.screwdriver (by which you can open the screw from handset)
2.bricked device
3.a usb cable
4.a copper wire( for sold test points)
5.a pc with sp flash tool,mtk drivers and stock firmwere for your mobile
now you have to disassemble your phone and take pcb out. check there should be some Golden points. check these points there should be written on them Rx,Tx,GND,Vcc,Vcharge etc… check there should be written “COLO” or “KOLO” or“KCOLO” you have to Sold that point with GND After Sold Attach usb now your phone will detect with USB !! and now ready to Flash.
In some phones “COLO” or “KOLO” or “KCOLO” not written for those type of phones you have to test all points one by one Short Golden point with GND and attach usb cable which point short with gnd can able to detect your phone by pc isForce Preloader Mode Test Point !! Keep in mind Don’t Short Vcc,Vcharge or any other pin which have 4.x Volts also i had tested “Colo” or “Kolo” or “KCOLO” don’t have any kind of volts.
need help
gsm-decode said:
You need to repair preloader. Contact me ![/QUOTE
i have samsung clone A9 MT6580 After reflash phon,e is dead by sptool..i thinkl preloader is damaged..i dont have back up..but ditecting VCOM BUT Always "Sft Enable Dram_Fail (4032)" in format or fullfash in all tools
Click to expand...
Click to collapse
help me i corrupted my pre loader
gsm-decode said:
You need to repair preloader. Contact me !
Click to expand...
Click to collapse
hi sir I try to flash a stock rom downloaded from internet
its a vivo v5 android mobile phone
I tried to flash but I got a few alerts
the selected model does not support model verification
and
if I tried it gives me a brom error
now my phone condition is hard bricked and responding to flash tool
gsm-decode said:
You need to repair preloader. Contact me !
Click to expand...
Click to collapse
HI sir how can I contact you
Hi I also have the same problem - when I flashed the stock rom of my LG K7 X-210 (MT6580__lge__LG-X210__m13g__5.1__ALPS.L1.MP6.V2.19_ARIMA6580.WE.L_P42) with the SP Flash tool when I was in a bootloop, I accidentally forgot to uncheck the preloader option. I flashed it to my phone and from that point onwards it didn't want to start up any more, nor would it react if I tried charging it. So conclusion: the preloader is corrupt...
However, I read online that MTK devices (mine is MT6580) have a 'meta' mode which allows your device to still connect to SP Flash tool even if it is hardbricked (in my case by pressing the volume up button, and then simultaneously plugging it in the computer). It is then recognized as MTK Com port something in device manager.
Luckily I have the same phone (but it's not mine) and I was wondering if it was possible to make a full rom dump from that device and restore it on mine? (a method that is safe for the other device as well)
i have a proble on my new phone since i flash preloader my touch is not working anymore, any solutions ?
gsm-decode said:
You need to repair preloader. Contact me !
Click to expand...
Click to collapse
I need to repair preloader of My Nokia G20.
hello this is very simple.
i solved this problem.
i wrte english very small.
flash atarken yanlış attığın preloader dosyası ile başlat.cihazı bilgisayara bağla.format bittikten hemen sonra doğru preloader dosyasını klasörün içine yapıştır.ama çok hızlı olmalısın.yani uyumsuz preloader dosyası ile cihaza yükleme yaparken tam format esnasında uyumlu olan preloader dosyasını hızlıca yapıştır.
gsm-decode said:
You need to repair preloader. Contact me !
Click to expand...
Click to collapse
Hello, is it too late to write?

[Q] what is qhsusb_bulk ?

i bricked my android and when i connect it to the laptop its shows "qhsusb_bulk" after some research on google i came to know that it is some kind of download mode for qualcomm devices like mine and i am stuck here cause i messed up my bootloader (cause i flashed different device's rom)
i tried every method available (there weren't much BTW) but no use
please can anyone help me with this i want my phone back....
bonny1256 said:
i bricked my android and when i connect it to the laptop its shows "qhsusb_bulk" after some research on google i came to know that it is some kind of download mode for qualcomm devices like mine and i am stuck here cause i messed up my bootloader (cause i flashed different device's rom)
i tried every method available (there weren't much BTW) but no use
please can anyone help me with this i want my phone back....
Click to expand...
Click to collapse
Please tell more about your device mate . And go search on your phone forum instead here, I'm sure there is a guide for hard brick device in your phone's forum.
For example, I've a LG G2, and well, when in qhsusb_bulk mode, it can't be recover, so don't worry now.
bonny1256 said:
i bricked my android and when i connect it to the laptop its shows "qhsusb_bulk" after some research on google i came to know that it is some kind of download mode for qualcomm devices like mine and i am stuck here cause i messed up my bootloader (cause i flashed different device's rom)
i tried every method available (there weren't much BTW) but no use
please can anyone help me with this i want my phone back....
Click to expand...
Click to collapse
Send your phone's model number and version so anyone help you
Br
Shahzaib Jahangir
As with most qualcomm devices, a bricked bootloader needs uart access to restore it (if a image is even available)
Guys im having the same issue but with a CATS50, what can i do, i have tried almost all

Question HARD Bricked Moto G power (2021) XT2117-4 / Blankflash, Flash file, or emmc_prog_firehose request.

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

HELP, LG G2 HARD BRICK

I wanted to install the lineage firmware on my lg g2 phone, the instructions said to downgrade the bootloader version after I encountered a problem that the phone does not turn on; boot certification verify. What to do as quickly as possible I want to solve the problem, in other guides on xda the pictures or links are not working, the specific id of my phone LG G2 D802, sorry for my bad English. and i have black screen boot. help plz. thank you
I want to add that when connected to a PC, it is defined as Qualcomm hs-usb Diagnostics 9006
and create more disk about 10-13 and 1 disk have files
adb dont work . fastboot too . help plz

Question Moto g power 2021 9008 ports is not showing hard brick

so I been trying to install GSI and I erase all the partitioning and forgot to create them again and now my phone is hard brick when I connect my deep flash cord to my Moto g power 2021 and hold the button it's show no ports and I have the driver install when I connect only thing that happen is that the led blink over and over again. What type of brick is this and is there a fix or i have to buy a new phone please help
Are you using LMSA tool to flash? Because that's what I recommend you use. Also make sure you have the Motorola drivers installed on your computer
That is not the correct software to use while restoring this phone use Fastboot and grab the stock firmware here and match the model https://mirrors.lolinet.com/firmware/motorola/borneo/official/ Flashing instructions are literally a Google search away.
iTrySmoke said:
That is not the correct software to use while restoring this phone use Fastboot and grab the stock firmware here and match the model https://mirrors.lolinet.com/firmware/motorola/borneo/official/ Flashing instructions are literally a Google search away.
Click to expand...
Click to collapse
LMSA is the official tool to use for Lenovo and Motorola devices. Although lolinet is unofficial, both are equally good tools to use to unbrick a device
Fazwalrus said:
LMSA is the official tool to use for Lenovo and Motorola devices. Although lolinet is unofficial, both are equally good tools to use to unbrick a device
Click to expand...
Click to collapse
I've been told by the phone it's self to use that software for Verizon devices only but Aye does the same thing I guess
KILLFIREY1389 said:
so I been trying to install GSI and I erase all the partitioning and forgot to create them again and now my phone is hard brick when I connect my deep flash cord to my Moto g power 2021 and hold the button it's show no ports and I have the driver install when I connect only thing that happen is that the led blink over and over again. What type of brick is this and is there a fix or i have to buy a new phone please help
Click to expand...
Click to collapse
Suggest you go onto the Motorola Blankflash channel on Telegram to get some help: https://t.me/motoblankflash
The admin guys there know their stuff and can give you some specific help/recommendations and the correct method and blankflash files to use.

Categories

Resources