Related
Hi all,
Since Sunday I try to solve the hard brick of my Moto G XT1032. I was on a rom GPE in 4.4.4 (EU) and by making the MAJ Lollipop during the sunday, the tel reboot on the logo Motorola and nothing more.
I tested severals tutos on XDA and many french websites, as:
Http: // forum.xda-developers.com / showthread.php? T=2633272
http: // forum.xda-developers.com/moto-g/help/mo to-g-hard-brick-lollipop-t2998124
And a lot of the others...but nothing!
Well, I said myself it doesn't matter because mototool repair the tel with no problems, as usual. But not, many errors when I try of downgrade in 4.4.2 or in 4.4.4 with it. I tried to flash (cache/ system / data / Dalvik) with CWM and TWRP with one tens of versions all in all and impossible to make no anything to put back. I tried to install many rom's, always the same.
I have errors as " remote failure ", impossible of mount the partitions system/cache, hab check failed and more more more, i don't remember the other's errors...
I cannot copy files (like a rom) via ADB to the tel in mode bootloader and I don't know what to do anymore of the whole...
If you have an idea, I am interested because there I think that except the SAV ... i'am in bull***t. :silly:
Thanks to all of your help and good week!
(sorry for my poor english)
Try manually flashing a stock 4.4.4 ROM , not a 4.4.2 ROM, for your phone. You may not be able to flash motoboot if the bootloader on your phone is newer than the bootloader you are trying to flash.
audit13 said:
Try manually flashing a stock 4.4.4 ROM , not a 4.4.2 ROM, for your phone. You may not be able to flash motoboot if the bootloader on your phone is newer than the bootloader you are trying to flash.
Click to expand...
Click to collapse
I try but the problem it's adb, because it's impossible to synchronize my phone with it.
When i try "adb reboot-bootloader" in a shell, i have the error "device not found".
And it's impossible to continue the tutorial :
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
What is the solution for this?
adb reboot bootloader works if your phone is booted and you have debugging enabled.
ADB commands don't work when the phone is in fastboot mode.
Put your phone into fastboot mode, connect it to your computer, type in "fastboot devices" and your's phone serial # should appear on screen.
audit13 said:
adb reboot bootloader works if your phone is booted and you have debugging enabled.
ADB commands don't work when the phone is in fastboot mode.
Put your phone into fastboot mode, connect it to your computer, type in "fastboot devices" and your's phone serial # should appear on screen.
Click to expand...
Click to collapse
OK. I have a phone serial who appear on screen (with the command "fastboot devices"), but with the command "adb devices", i have no serial, so no devices attached...
EDIT : Into TWRP Recovery, i have the adb serial too
ok, now it's good I the phone turn on a retail rom 4.4.4.
For all those who have experienced the problem (a GPE 4.4.2 update to 4.4.4 and 5.0.1), the procedure is "simple".
Install adb+fastboot and copy the rom into the folder.
Fisrt, put your phone into bootloader mode and check the command 'fastboot devices"; you must have a serial into the shell. Boot on the TWRP recovery (2.7.1.1) and type the command into the shell "adb devices"; again, you must have a serial. If it's OK, format cache/system/data/dalvik and reboot the phone into the bootloader.
In my case, i use the rom RETAIL-FR_4.4.4 OTA.
Code:
fastboot flash partition gpt.bin
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot erase cache
fastboot erase userdata
fastboot reboot
IF this does not work , it is still possible to achieve a different manipulation .
Take CWM recovery (Philz Touch for example) and try to push a rom with adb.
@+
You can't use adb commands when the phone is in fastboot mode. THis is why adb devices returns nothing.
Glad you got it working.
Recently I rooted my phone and flash the resurrection remix naught in moto g3 xt1550....
For some reason I start to flash firmware ROM .....but it is not flashing.... Shows " preflash validation failed " and on system image " invalid image" .......... I tried many times but it didn't flash......when I skip the partition gpt file then every image file start flashing and phone start..,..
But their is no network......
After that whenever I switch off or reboot or go to recovery rather than that it start boot loader....
Then I flashed the resurrection remix again..... When I press reboot after flashing then it goes to boot loader......
At boot loader I press power on then it start booting and there is no network in this ROM too......
What can I do now ...... Please help.........
To clear the Fastboot mode, in fastboot enter "fastboot oem fb_mode_clear" and after that it should start the OS without going into fastboot each time.
The fact this is happening leads me to believe your other problem is related... meaning you didn't flash the stock images properly. If you have no network then you need to reflash the radio stack and boot.img file, they must match and you have to erase the modemstX partitions for the radios to work properly.
yes U will get the error of "preflash validation failed" cause of the security update which motorola released for the month of October, January and recent April.... Do one thing again flash the appropriate stock rom according to ur mobile But skip these two steps/Files >>> 1) fastboot flash partition gpt.bin and 2) fastboot flash bootloader bootloader.img and enter the remaining command/or follow the whole procedure but skip these two file mentioned above U will succed:fingers-crossed::good:
For ur simplicity im providing u commands and plz CHECK UR SPARSECHUNK Files it varies according to mobile I have 7 thats y 7 sparsechunk files DO CHECK URs ok>>>>
fastboot oem fb_mode_set
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Do it ur own risk Im not responsible for any damage :laugh:
everything went well except my network .........i checked in about phone < status < imei no is " 0 ".......how to restore that...........i think thats why the network isn't showing.......................
acejavelin said:
To clear the Fastboot mode, in fastboot enter "fastboot oem fb_mode_clear" and after that it should start the OS without going into fastboot each time.
The fact this is happening leads me to believe your other problem is related... meaning you didn't flash the stock images properly. If you have no network then you need to reflash the radio stack and boot.img file, they must match and you have to erase the modemstX partitions for the radios to work properly.
Click to expand...
Click to collapse
where I find radio stack...... I don't know........and I didn't flash the stock images correctly because I have to skip the partition gpt and bootloader......
give me something else to solve it......
btw thanks sir......:good:
heisenberg1546 said:
where I find radio stack...... I don't know........and I didn't flash the stock images correctly because I have to skip the partition gpt and bootloader......
give me something else to solve it......
btw thanks sir......:good:
Click to expand...
Click to collapse
The "radio stack" is the relevant radio portions of the firmware image...
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
It is not uncommon that they don't take the first time, repeat it and the boot.img command. Verify EVERY command returns an OKAY response, if not, repeat it.
And do not copy and paste the commands all at once, type them out and look at the response, or at least copy and paste each command individually.
acejavelin said:
The "radio stack" is the relevant radio portions of the firmware image...
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
It is not uncommon that they don't take the first time, repeat it and the boot.img command. Verify EVERY command returns an OKAY response, if not, repeat it.
And do not copy and paste the commands all at once, type them out and look at the response, or at least copy and paste each command individually.
Click to expand...
Click to collapse
isn't working sir........
I did without copy paste.........
boot img command gives preflash validation failed....
heisenberg1546 said:
It is not uncommon that they don't take the first time, repeat it and the boot.img command. Verify EVERY command returns an OKAY response, if not, repeat it.
And do not copy and paste the commands all at once, type them out and look at the response, or at least copy and paste each command individually.
isn't working sir........
I did without copy paste.........
boot img command gives preflash validation failed....
Click to expand...
Click to collapse
You didn't do the boot.img... but Might want to look at the IMEI 0 recovery thread... I don't have any more ideas.
acejavelin said:
You didn't do the boot.img... but Might want to look at the IMEI 0 recovery thread... I don't have any more ideas.
Click to expand...
Click to collapse
After those commands ...... I flash again all img's including the boot.img......
How to restore the imei file ..... Like in mediatek device ,,, we can write by sn tools .....
heisenberg1546 said:
After those commands ...... I flash again all img's including the boot.img......
How to restore the imei file ..... Like in mediatek device ,,, we can write by sn tools .....
Click to expand...
Click to collapse
I don't know... There is a thread here specifically about it, you will have to look there.
I want to keep the custom rom (RR-O-v6.0.0-20180511-ospreyl) with all networks
acejavelin said:
To clear the Fastboot mode, in fastboot enter "fastboot oem fb_mode_clear" and after that it should start the OS without going into fastboot each time.
The fact this is happening leads me to believe your other problem is related... meaning you didn't flash the stock images properly. If you have no network then you need to reflash the radio stack and boot.img file, they must match and you have to erase the modemstX partitions for the radios to work properly.
Click to expand...
Click to collapse
Hey, I have installed RR-O-v6.0.0-20180511-osprey on Moto G(3rd Generation), and now the error is: "No sim Detected ", IMEI number is fine. I want to flash radio firmware in this custom Rom. Will flashing radio stack of stock rom 6.0.1 (Moto G3 x1550) work?
adb reboot bootloader
fastboot flash modem NON-HLOS.bin (That must of Moto G3?)
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash boot boot.img (Is it to be of RR or of Moto?)
fastboot reboot
Is there any other option or solution then please mention.
You need to flash stock firmware first then your network problem solved then you can install custom roms?
Good Luck!
Hello everyone, i have big problem with my new motorola x force, i bought it with dead software. And i tried install new, (I'm doing it isnt first time). I get key for unlock from motorola service but is imposible. I get an error. This device can not be unlocked.
I guess first owner, forgot turn on develop mode.
Any idea? I'm tried flashing it with instructions from other thread https://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515.
I download soft from motorola, I'm tried first ver. android and new one. Everything without result.
Rasah97 said:
Hello everyone, i have big problem with my new motorola x force, i bought it with dead software. And i tried install new, (I'm doing it isnt first time). I get key for unlock from motorola service but is imposible. I get an error. This device can not be unlocked.
I guess first owner, forgot turn on develop mode.
Any idea? I'm tried flashing it with instructions from other thread https://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515.
I download soft from motorola, I'm tried first ver. android and new one. Everything without result.
Click to expand...
Click to collapse
You do not need to unlock the bootloader to flash original moto firmware
Just put it in bootloader mode and on your pc where you have fastboot and all the firmware files open a command/terminal prompt and type the following
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img (not all devices have this)
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk0 (flash all sparsechunks in number order - for example)
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
TheFixItMan said:
You do not need to unlock the bootloader to flash original moto firmware
Just put it in bootloader mode and on your pc where you have fastboot and all the firmware files open a command/terminal prompt and type the following
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img (not all devices have this)
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk0 (flash all sparsechunks in number order - for example)
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Click to expand...
Click to collapse
Sure, but When i done it phone starting with Motorola logo and restarting, I didn't have this file img with nr 1/4 I mean this fastboot flash system system.img_sparsechunk4
I download soft from Motorola, I don't remember version but it like 5.1? Middle one from list and in another one first vet same
Rasah97 said:
Sure, but When i done it phone starting with Motorola logo and restarting, I didn't have this file img with nr 1/4 I mean this fastboot flash system system.img_sparsechunk4
I download soft from Motorola, I don't remember version but it like 5.1? Middle one from list and in another one first vet same
Click to expand...
Click to collapse
Some phones may not have sparsechunks 0 & 4 - as long as you flash all the ones in the firmware in number order
I don't have your phone so I couldn't tell you what firmware to use
I have Motorola g5 so I can just tell you the process
And looking on that firmware thread it says you need to use mfastboot for system images - so see that thread for details
Long as everything is flashed successfully in the order I have written above including erasing user data
Sooo.... Could you tell me which comand i have to use ?
Related to no sim card issue?
I'm wondering if this is related to a problem I am having with mine phone. I flashed the official firmware (6.0) on my moto x force and everything works but the simcard. It says it's not loaded so I have no phone or cell data. My sim card works in other moto phones so its not that.
Story: I bought US version Z3 Play open market model from B&H. I could unlock the bootloader according to Motorola Developer site, but I encountered problem to root and I have struggled half day to make root done from booting TWRP to patching boot.img.
Eventually, I bit the bullet and make a step up to update to Pie bu downloading RETAIL ROM instead of RETUS. This time I patched the updated boot.img and I got success.
Prerequisite:
Full RETAIL Pie ROM
https://mirrors.lolinet.com/firmware/moto/beckham/official/RETAIL/
Bootloader unlocked
It's recommended to flash in Linux (I used Ubuntu) as I didn't have luck with Windows
Main battery should be full and supplied battery module should be at least 50% (you can charge battery module with 9V PD charger)
Some typing (all fastboot commands typed as ./fastboot)
Be aware some components will be flashed in b partition. Failure to do it will cause bootloop
./fastboot erase userdata is optional, but it is recommended to avoid unexpected trouble
Steps:
1. Download the Pie ROM and extract to somewhere you know (you can drag and drop the file into terminal window).
2. Copy the boot.img to the phone and let Magisk Manager to patch it, and copy the patched_boot.img to where you can locate.
3. Backup your personal data just in case
4. Prepare USB C cable
5. Enter bootloader. Turn the phone off, press and hold both volume down and power button together, and connect you phone to host computer. (You phone should show USB conmected)
6. Enter the following commands
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot reboot
Click to expand...
Click to collapse
7. After the phone has booted up, wait until it completed the update process. Now you have to go back to bootloader for rooting.
fastboot flash boot patched_boot.img
Click to expand...
Click to collapse
Booting process takes much longer, but it's one process until you update ROM and regain root again.
8. Run Magisk Manager to check root status
This is what I did to manually update to Pie and root it. Your milage may vary.
Good luck
Will this work on the amazon version?
CrimsonSaber5G said:
Will this work on the amazon version?
Click to expand...
Click to collapse
If the bootloader can be unlocked, it's likely
Will this still allow you to get OTAs or will it break it?
crazyjimbo said:
Will this still allow you to get OTAs or will it break it?
Click to expand...
Click to collapse
I used to flash stock on my rooted z3play, then take the OTA . For some reason that's not possible anymore. I really need the latest OTA to sideload it. I tried many different roms 8.1 and 9.0
Hey everyone. So recently I tried rooting my motorola g7 play. I followed this guide on youtube
and everything was going fine until one point I received something like "bad error" (or something like that) when I tried installing magisk patched boot.img file on my phone. It then asked if I would try installing again or do a factory reset. I tried again and it didn't work so thought I had no choice besides to do a factory reset. When I booted it back up, it put this code on the top left of the screen: 80012A99-86FDA48-4E357816-0E549F1B-B067FD5 and then everything was working fine until it asked to do the language selection. The problem was that the touch screen wouldn't work anymore, but the side buttons still work. So I tried restarting my phone, safe mode and using things in bootload mode (factory mode, recovery mode, etc.) and the screen still didn't work. I think the problem may be where I got the boot.img from, which is here: https://forum.xda-developers.com/t/magisk-on-g7-play-xt1952-4-installed-succesfully.3975477/ and I feel like this problem is still able to be fixed. I was considering buying an otg adapter to try connecting my mouse to the phone, but I'm not sure since it might be considered a waste of money. any help would be appreciated. Thanks in advance!
nimbussecond said:
Hey everyone. So recently I tried rooting my motorola g7 play. I followed this guide on youtube
and everything was going fine until one point I received something like "bad error" (or something like that) when I tried installing magisk patched boot.img file on my phone. It then asked if I would try installing again or do a factory reset. I tried again and it didn't work so thought I had no choice besides to do a factory reset. When I booted it back up, it put this code on the top left of the screen: 80012A99-86FDA48-4E357816-0E549F1B-B067FD5 and then everything was working fine until it asked to do the language selection. The problem was that the touch screen wouldn't work anymore, but the side buttons still work. So I tried restarting my phone, safe mode and using things in bootload mode (factory mode, recovery mode, etc.) and the screen still didn't work. I think the problem may be where I got the boot.img from, which is here: https://forum.xda-developers.com/t/magisk-on-g7-play-xt1952-4-installed-succesfully.3975477/ and I feel like this problem is still able to be fixed. I was considering buying an otg adapter to try connecting my mouse to the phone, but I'm not sure since it might be considered a waste of money. any help would be appreciated. Thanks in advance!
Click to expand...
Click to collapse
I started flashing TWRP a month or so ago on my g9 Power with the wrong version and the touchscreen did the same thing, I attached an OTG and hooked the mouse and it worked great... As for your failed flash, is your firmware xt1952-4? I suspect that boot.img is from a phone with a different touchscreen. I would find the correct firmware from lollinet and reflash a stock boot.img and you should be fine. Install Magisk as an app then modify your own boot.img and install root that way. ALSO if you can still use side buttons you should still be able to flash a new stock boot.img from inside fastboot without digitizer support...
Dauksza72 said:
Accident... Don't know how to delete it now...
Click to expand...
Click to collapse
Dauksza72 said:
I started flashing TWRP a month or so ago on my g9 Power with the wrong version and the touchscreen did the same thing, I attached an OTG and hooked the mouse and it worked great... As for your failed flash, is your firmware xt1952-4? I suspect that boot.img is from a phone with a different touchscreen. I would find the correct firmware from lollinet and reflash a stock boot.img and you should be fine. Install Magisk as an app then modify your own boot.img and install root that way. ALSO if you can still use side buttons you should still be able to flash a new stock boot.img from inside fastboot without digitizer support...
Click to expand...
Click to collapse
OK, thank you so much. In fastboot mode it says Product/Variant: channel XT1952-4 32GB PVT, so I assume that the firmware is indeed xt1952-4. Also could you clarify how to flash a new stock boot.img from inside fastboot because I'm not sure how to modify anything on my phone without allowing usb debugging (which I can't do since the phone factory resetted). If there are no other options I plan on trying the OTG adapter then.
nimbussecond said:
OK, thank you so much. In fastboot mode it says Product/Variant: channel XT1952-4 32GB PVT, so I assume that the firmware is indeed xt1952-4. Also could you clarify how to flash a new stock boot.img from inside fastboot because I'm not sure how to modify anything on my phone without allowing usb debugging (which I can't do since the phone factory resetted). If there are no other options I plan on trying the OTG adapter then.
Click to expand...
Click to collapse
I've not had issues with using fastboot after a stock flash even without going in and enabling adb thru developer mode. When you hold volume - while powering up and plug in the usb cord from the PC you should go into the bootloader and can flash the new boot image from there with fastboot commands. You may already know but open cmd prompt on pc, type cd then drag your fastboot directory folder over to cmd prompt and drop it, click anywhere in cmd prompt and hit enter. Put your system boot image inside the folder with you fastboot files and type "./fastboot flash boot boot.img" and hit enter and you should be flashing.
Dauksza72 said:
I've not had issues with using fastboot after a stock flash even without going in and enabling adb thru developer mode. When you hold volume - while powering up and plug in the usb cord from the PC you should go into the bootloader and can flash the new boot image from there with fastboot commands. You may already know but open cmd prompt on pc, type cd then drag your fastboot directory folder over to cmd prompt and drop it, click anywhere in cmd prompt and hit enter. Put your system boot image inside the folder with you fastboot files and type "./fastboot flash boot boot.img" and hit enter and you should be flashing.
Click to expand...
Click to collapse
Thanks so much, my phone seems to work fine now. I ended up finding the right boot.img file and wanted to try following the video again, but at the last step where I have to flash the magisk patched img file, command prompt gives me the error (bootloader) is-logical:boot_b: not found. Do you know what I can do to so that it can flash properly?
nimbussecond said:
Thanks so much, my phone seems to work fine now. I ended up finding the right boot.img file and wanted to try following the video again, but at the last step where I have to flash the magisk patched img file, command prompt gives me the error (bootloader) is-logical:boot_b: not found. Do you know what I can do to so that it can flash properly?
Click to expand...
Click to collapse
In fastbootD, (go to bootloader and type
./fastboot reboot fastboot)
./fastboot erase-logical-partition product_a
./fastboot erase-logical-partition product_b
then flash the Magisk_modified.img to boot_a and boot_b from fastboot.
./fastboot flash boot_a Magisk(whatever Magisk named it)
./fastboot flash boot_b Magisk(whatever Magisk named it)
./fastboot -w
./fastboot reboot
Now that you know how to recover from a soft brick don't be afraid to play around with it. Eventually you'll make a text document and have all your commands on it so all you have to do is copy the whole page and paste it in fastboot and pretty much automate the whole process... Let me know if that helps.
Realized I typed flash product_a/b instead of boot_a and boot_b... SORRY. Total oversize. Delete product , flash boot
Dauksza72 said:
In fastbootD, (go to bootloader and type
./fastboot reboot fastboot)
./fastboot erase-logical-partition product_a
./fastboot erase-logical-partition product_b
then flash the Magisk_modified.img to boot_a and boot_b from fastboot.
./fastboot flash boot_a Magisk(whatever Magisk named it)
./fastboot flash boot_b Magisk(whatever Magisk named it)
./fastboot -w
./fastboot reboot
Now that you know how to recover from a soft brick don't be afraid to play around with it. Eventually you'll make a text document and have all your commands on it so all you have to do is copy the whole page and paste it in fastboot and pretty much automate the whole process... Let me know if that helps.
Click to expand...
Click to collapse
For some reason I can't get into FastbootD, it gives the error FAILED (remote: 'Unknown command') fastboot: error: Command failed. I tried searching up stuff, removing the passcode, switching USB ports and more but I couldn't get the screen to pop up. What can I do about this?
Have you tried reflashing stock recovery? You also may be able to delete partition and flash through regular fastboot. If you still haven't got it by this evening then I'll brick my wife's g7 and figure out a work around for you.
Dauksza72 said:
Have you tried reflashing stock recovery? You also may be able to delete partition and flash through regular fastboot. If you still haven't got it by this evening then I'll brick my wife's g7 and figure out a work around for you.
Click to expand...
Click to collapse
So I tried flashing stock recovery and I seem to get a similar error to when I flash the magisk patched file and I've tried deleting partition and flash through regular fastboot, but it didn't work either (error in the image). I might be doing something wrong since I'm still very new to this, but I also tried downloading TWRP since I know that's another way to root and it lead to the same problems as well (bootloader) is-logical whatever I'm trying to do not found. I also tried LMSA (Lenovo Rescue and Smart Assistant) to see if there was something wrong with my phone, but it made no difference. I might consider an alternative rooting method, let me know what's the best option. You don't have to brick your wife's g7, but either way I appreciate it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ok, do this and post a screenshot again and we'll get it pinpointed. I think your tools are out of date but it could still be a firmware issue.
Make sure you're using latest platform tools, https://developer.android.com/studio/releases/platform-tools.
./fastboot --version
./fastboot -w
./fastboot getvar current-slot
./fastboot oem device-info
Are you sure the g7 Play has a separate recovery partition? It may be part of the boot partition... Instead of flashing the modified image to a/b just try
./fastboot flash boot "modimg".img
Dauksza72 said:
Ok, do this and post a screenshot again and we'll get it pinpointed. I think your tools are out of date but it could still be a firmware issue.
Make sure you're using latest platform tools, https://developer.android.com/studio/releases/platform-tools.
./fastboot --version
./fastboot -w
./fastboot getvar current-slot
./fastboot oem device-info
Click to expand...
Click to collapse
Ok I updated it to the most recent version and also fastboot flash boot "modimg".img says boot_a not found as well. Here are the results of the commands you told me to run.
Are these the files you have?
Post a screenshot of the flashfile.xml or servicefile.xml
nimbussecond said:
Ok I updated it to the most recent version and also fastboot flash boot "modimg".img says boot_a not found as well. Here are the results of the commands you told me to run. View attachment 5295077
Click to expand...
Click to collapse
The G7 Play doesn't have fastbootd and recovery/boot are merged. You can't have twrp and magisk at the same time. Magisk must patch the boot.img as recovery. (Check all 3 boxes) When you boot up, you must hold Vol↓+power, and select recovery from the fastboot menu to have root.
Inside your firmware zip, there's a flashfile.xml, open it and flash everything as directed, and in order. It'll start with gpt.bin. That's the only tricky one, it repartitions the phone so it flashes to "partition" like so...
fastboot flash partition gpt.bin
Spaceminer said:
The G7 Play doesn't have fastbootd and recovery/boot are merged. You can't have twrp and magisk at the same time. Magisk must patch the boot.img as recovery. (Check all 3 boxes) When you boot up, you must hold Vol↓+power, and select recovery from the fastboot menu to have root.
Inside your firmware zip, there's a flashfile.xml, open it and flash everything as directed, and in order. It'll start with gpt.bin. That's the only tricky one, it repartitions the phone so it flashes to "partition" like so...
fastboot flash partition gpt.bin
Click to expand...
Click to collapse
Thanks, that's where I was headed with this.
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash vendor vendor.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot oem fb_mode_clear
fastboot erase userdata
fastboot erase DDR
Dauksza72 said:
Thanks, that's where I was headed with this.
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash vendor vendor.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot oem fb_mode_clear
fastboot erase userdata
fastboot erase DDR
Click to expand...
Click to collapse
I did a lot of dev work for this phone. I had to help.
Alright so I did what you guys told me to with the flashfile.xml, the zip I used is XT1952-4_CHANNEL_RETCA_10_QPYS30.52-22-11-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml. I tried doing recovery mode after this and after flashing the magisk boot.img, but it had the same result. I'm not sure what to do after this step. (These are the screenshots after I did the commands).
nimbussecond said:
Alright so I did what you guys told me to with the flashfile.xml, the zip I used is XT1952-4_CHANNEL_RETCA_10_QPYS30.52-22-11-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml. I tried doing recovery mode after this and after flashing the magisk boot.img, but it had the same result. I'm not sure what to do after this step. (These are the screenshots after I did the commands).View attachment 5295529View attachment 5295531View attachment 5295533
Click to expand...
Click to collapse
Install magisk manager, patch your boot.img as "recovery". Flash the patched boot.img. Use the volume buttons while in the bootloader menu to select recovery, and hit the power button. Open magisk and it should be rooted. If it needs additional setup allow it.