I'm posting this just because it might be helpful for others, as well as providing some warning for anyone else who might one day get into the same situation.
I was rooted and had installed TWRP on my new Gpad 7.0 V410 and everything was running just fine. I've been modding Android devices for years and thought I knew what I was doing. I didn't like the AT&T boot animation and thought I'd replace it. I found the stock animation in system/media, and replaced it (with a Nexus 7 ani) just like I'd done on previous devices.
When I rebooted, the animation started and ran. But then it hung, and rebooted. It was now stuck in a bootloop. Well, no problem, I thought, I'll just get back into recovery and restore the stock ani.
That was when I discovered how locked down the firmware is on this device. No fastboot. No standard Android bootloader. Not even, as far as I could tell, anyway of rebooting into recovery using the hardware buttons.
I could get to the factory reset screen and download mode, but neither have any way to get to recovery. ADB could not connect. The LG support tool found it, but did nothing but tell me the firmware was up to date. Lots of searching and reading turned up similar tales of woe. I began to worry that there was no way out.
Having no other ideas, I tried doing a factory reset. It ran, and lo and behold, kicked me into TWRP. From here, I confirmed that the device was wiped.
However! I had had the foresight to create a TWRP backup on my external sdcard, and that was still there. Restoring it got everything back in working order.
The moral: If you're up and running now, make an external backup. It could save your butt just as it did mine.
Amen
I'd just like to add that you can enable fastboot on this tablet for anyone who might read this thread. If you follow the method described here you'll lose download mode, but the tablet will fall back to fastboot when download mode fails. :good:
Without a kdz file released for the V410 the download mode isn't really good for anything, but fastboot gives you a fighting chance of being able to flash your way out of trouble if you brick your V410. Probably advisable to keep a backup of the laf partition just in case you need it someday.
Aha, thanks, I had seen that referenced several times, but wasn't sure where to go with it, and wanted to try less extreme methods before attempting something like that.
I've been spoiled by modding HTC and Nexus devices up to now, so this is a bit of a culture shock over here.
Edit: Decided to bite the bullet in case of future problems and nuked laf. Ah, sweet fastboot. :highfive:
Hello, does anybody know when a recovery for the moto G7 play XT1952-4 might be released? I am eager to root my new phone.
I am also looking for the recovery of Moto G7 Play, I unlocked my BootlLoader to make Root and I do not think any Recovery
You don't need TWRP to root the phone. As long as the bootloader is unlocked, you can root with Magisk. Select the Link To Installation Instructions and follow the Boot Image Patching section. It requires using ABD commands, and although it looks/seems complicated, it is actually very easy. Plus, you will have learned something as well as root your phone.
If the G7 Play is actually code-named "Channel", then this link will give you stock firmware for you to download and extract the stock boot image.
Magisk boot.img
Ok I got the retail Canada ROM. Now I am going to extract boot img and patch it with Magisk manager. Once patched I am going to flash it to my phone using abd fastboot? At this point it will be rooted or do I use SuperSU to root? Under software channel on my phone it says "Bell" but the build number and model number matched up. XT1952-4 PPY29. 105-57 so it should be good hopefully.
Thanks
Error: cannot open 'magisk_patched.img'
Must be wrong Rom. Everything worked fine until I had to flash it. I put patched IMG right in adb directory and opened a command window from there but when I tried to flash it I got the error cannot open file. Oh well I think I will wait for a recovery it's the easy way for me.
Thanks
Code named 'channel'
There are 2 more versions of it in the list you provided. Not sure what the abbreviations are before CA for Canada but I will try them too. If I get the same error when flashing these patched boot.imgs I will have to wait for a recovery. Hopefully it won't by be too much longer. I just hope there will be a recovery.
Thanks
Continued error when flashing patched files.
I have tried 3 boot images from 3 different retail Canada firmwares. All 3 patched alright by magisk manager but when I try to fastboot flash boot magisk_patched.img I get the same error cannot open file. I must be doing something wrong. My phone's bootloader is unlocked so unless someone has a solution. I will definitely have to wait for a recovery. Hopefully soon!.
Thanks
Dumb question...when you are attempting to flash your patched boot image, is your phone in fastboot mode? Also, you may be able to extract your boot image via ADB. It's been a while since I've done it and am having trouble finding the proper commands, but you can try this:
adb pull /dev/block/bootdevice/by-name/boot stockboot.img
Click to expand...
Click to collapse
It may or may not work. I hope it does but apologize if it does not.
Furthermore, you will likely have to wait quite a while for a custom recovery (TWRP). The G7 play has A/B partitions, which makes ROM building and recoveries very difficult. There is no separate "recovery" partition with A/B...the recovery is combined within the boot image. FYI - I have a Xiaomi A2 Lite that has A/B partitions. We still don't have a 100% working TWRP after 9 months. Custom ROMs have just been coming out slowly. I was able to root with Magisk using ABD commands though.
This link might provide clearer steps for installing Magisk.
Best of luck!
Yes, it was in fastboot mode. I will keep trying with your new intructions. Thanks for your help.
My mistake
I did not even have adb fastboot installed I was opening a command window out of the folder that was left over from uninstallation. I am about to try it again. It should work now. Stay tuned.
So far
Okay, so I installed adb fastboot and flashed the patched boot file from the RETCA firmware. I got this message " failed (boot a)" . So I tried the flashing the 2nd patched boot file that was from I think BWACA firmware. With this flash I got " not signed or corrupt" then the phone failed to start with bootloader log to confirm.
So I took the original unpatched boot.img from RETCA and flashed it. This fixed the phone so it would start fine making me believe that it's the right boot image but maybe the other firmware boot.img would have fixed the failing to start issue as well. So I think I need to pull the boot.img from the phone itself like you suggested. I am going to read some more and continue. I will figure it out. Any suggestions would be of great value.
Thanks.
Getting Closer
I realized that the magisk zip file that magisk manager downloaded did not get unzipped so that it could patch the boot.img properly. Fixed that. Flashed the boot.img and it said "okay" but said "(bootloader) image signed with key bad key" so I think I will have to pull the boot.img from the phone itself. So I am about to read up on that then I should be able to flash successfully for root access.
Thanks
jwreidmoto said:
I realized that the magisk zip file that magisk manager downloaded did not get unzipped so that it could patch the boot.img properly. Fixed that. Flashed the boot.img and it said "okay" but said "(bootloader) image signed with key bad key" so I think I will have to pull the boot.img from the phone itself. So I am about to read up on that then I should be able to flash successfully for root access.
Thanks
Click to expand...
Click to collapse
A few posts back you said you flashed the stock RETCA boot image. If that's the case, then if you successfully pull the boot image from the phone, you are simply pulling the RETCA boot image you already flashed. It seems that the RETCA boot image is the correct one for you phone. I would start completely from scratch with that. To verify which build number you have, go to Settings>About Phone or ( Settings > About Phone > Software channel) and scroll down to Build Number. Match it up to one from link with all the firmware images.
The only other thing I can say is that you should read and completely understand what to do prior to doing it. I am sorry you are having difficulties with this. It really should not be so hard. As I don't have the phone I cannot be of much more assistance. However, once you figure it out, perhaps you can write a quick guide to help others.
EDIT: You should be rooted. SEE POSTS 10-13. Did you check for root?
EDIT 2: I'm assuming that since you unlocked the bootloader, when you reboot the phone the screen goes black and says "Bad Key", correct? That is normal for Moto phones.
2nd, after you root, when you reboot the phone, the screen should go black and say "N/A". Again that is normal for Moto phones.
I understand what you are saying I would also expect the N/A on the black screen that's when I knew I successfully rooted my old phone. I must have the right boot image if flashing it fixed the startup failure. I am going to start all over again and see.
Have to give up.
Tried and tried it's just not going to work. I think it's the patching because the boot file starts out as 32mb and only 18mb after being patched. Flashing has no effect on my phone even though it says 'okay' when I flash. I never get the N/A on boot unless there is a startup failure. Oh well have to live with ads among other anoyyances. My Moto g4 play is rooted I can use than in case a solution comes up. Thanks for all your help.
jwreidmoto said:
Oh well have to live with ads among other anoyyances.
Click to expand...
Click to collapse
DNS66 is your friend! I have used it on other unrooted phones. It was decent from what I remember. Good luck!
Sorry that root wasn't working.
EDIT - If you are up for a little more testing...I just found this. I don't remember if it's what I had to do for my Xiaomi or not, but it makes sense. (Further research - No I did not have to do this). Scroll down to method #2 and look for the part about A/B partitions:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
Click to expand...
Click to collapse
Edit #2 - I don't give up easily LOL
After any of your attempts to flash the patched_boot image, did you ever boot the phone and open the Magisk Manager app? Doing so should ask to install Magisk, if not you must tap on the "Install" button. Then choose "Install" > "Direct Install (Recommended)" to install Magisk on the phone, and reboot when finished.
Neither do I
I have been trying everything since we last talked. Just so you know the link labelled as "this" in your last response is not working. I always opened the magisk app after flashing to see if it was either installed or gave me the option to do a direct install unfortunately, it did not. I have magisk manager installed on my rooted Moto G4 plus and it gives me that option to do a direct install. Will definitely try your new info. Thanks so much for more help. I will let you know.
Still no luck
Without the link I got the jist of what you were saying by the quote boot_a boot_b I tried both consequtively and then tried it for ever possible retail Canada image still no luck. Thanks for your help. I don't know why it's so hard for this phone. I will keep researching.
I'm at about the same place where jwreidmoto is. I purchased my unlocked g7play from Best Buy. First I tried the files in the channel/RETUS folder, these all caused a bootloop. I then tried in the RETAIL folder... still no joy. None of the version numbers quite matched up, and none worked to restore the phone. I finally found a matching file in the AMZ folder, which I was able to use to get the phone to boot up again. So I used that boot.img file with magisk and when I flashed, it gave no errors, no indication anything failed. Unfortunately though, I do not have root access. I started over from scratch and did the process over with the AMZ boot img again, and again no errors, but no root. I've never rooted before, so I don't know if there's another part somewhere I missed, but I do feel like I was able to follow the directions on the g7 thread by mingkee, and performed the steps accurately. I supposed it's just the wrong boot img. The about phone says the software channel is US Retail, and the build number is PPY29.105-36. The RETUS folder only has PPY29.105-43 and RETAIL folder has five different zip files, but none were PPY29.105-36.
You are doing it right
You have not missed any steps. If the boot.img fixed the boot loop then it should be the right one. I had the same issue with a startup failure and fixed it with the RETCA boot.img so I am also using the right one also. I think it's an issue with the model of phone, this method just does not work. We might have to wait a while until someone comes up with a solutuon. I know it sucks.
So, straight to the point--anybody here have an idea about how to relock the bootloader on an H811 when ONLY download mode is available?
Over the last few days, this H811 has progressively succumbed to the dreaded G4 bootloop plague, and it is now purely bootlooping (doesn't even get to T-Mobile logo). Before it got so bad, I was able to flash it back to factory state (minus the unlocked bootloader) with the 20x KDZ using LGUP (reason why I did this will be explained below...). But this means that recovery is not available to get get into bootloader mode that way. And I have not yet had a complete successful boot after the KDZ flash to enable USB debugging, which would allow me to get into bootloader mode with the adb reboot bootloader command. So essentially, only download mode is available at this point, uggh...
The back story is that I just bought this used H811 to try out steadfasterX's LOS16, which, by the way, is fantastic! And almost immediately, the phone started displaying bootloop-ish symptoms. For example, like after the initial bootloader unlock, which I did immediately on receiving the device just a few days ago, the phone crashed during the optimizing apps step of the subsequent reboot (it probably overheated). I should have just relocked the bootloader at that point, and sent it back to the vendor for replacement. But I was anxious to try LOS16, and between occasional crashes, I eventually got it installed. But over the next few days, the crashing and occasional bootlooping became so progressively worse that I decided I really did need to send it back for replacement. So today I reflashed the 20x KDZ with LGUP, and that worked fine. But I'd like to relock the bootloader, too, so the vendor doesn't claim I screwed with it, and thus, that they are not responsible for replacing it. But as I mentioned, the only mode available at this point is download mode because it is purely bootlooping on the initial text screen without even getting to the TMo logo.
If I could get into bootloader mode, I could try to do either a a.) fastboot oem lock (given it is fully stock with the recent 20x KDZ flash, there should be no chance of bricking...), or b.) I could also flash just the misc partition extracted from the 20x KDZ. But again, without recovery, nor the possibility to enable USB debugging, I cannot get into bootloader mode. So that's why download mode is my only option.
steadfasterX's SALT works with download mode, but it cannot flash single partitions yet to follow the misc partition flashing strategy I mentioned above.
So what options does this leave me?
Option 1.) phone is in the freezer right now to see if I can get just one more good boot in order to get enable USB debugging, and thus, get to bootloader mode via adb; and from there, then relock the bootloader so the vendor doesn't see the bootloader unlocked message, and claim that I am responsible for the problems...; yeah, the freezer method is a long shot, but in the past with a VS986 that was bootlooping, I did get one final boot out of it for data rescue using this freezer method...
Option 2.) in download mode and via SALT, I can get a shell into the phone; maybe there is a way to flash just the misc partition (extracted from the 20x KDZ) via a command line in that shell, and thus, get the system back to a locked state?
Option 3.) well, send it back to the vendor as is, and hope that they do not try to claim it is my fault because the see the unlocked bootloader message...
Option 4.) if options 1-3 do not work, well, perhaps give LG a call to see if they will fix the circuit board; by the way, they did it for the VS986 I mentioned above without any questions whatsoever; but the difference is that I was the original purchaser of that VS986 whereas this H811 is a secondhand purchase, and LG might use that as a reason for not fixing it.
Any other options that I might be missing? Thanks for any wisdom or suggestions you might be able to provide!
Anyway, my learning lesson from all of this is patience--like I said, I should have returned the device immediately on seeing the first signs of bootlooping because in my experience with both the VS986, and this newly received H811, well, once bootlooping symptoms start, they progress very quickly...
verbage said:
So, straight to the point--anybody here have an idea about how to relock the bootloader on an H811 when ONLY download mode is available?
Over the last few days, this H811 has progressively succumbed to the dreaded G4 bootloop plague, and it is now purely bootlooping (doesn't even get to T-Mobile logo). Before it got so bad, I was able to flash it back to factory state (minus the unlocked bootloader) with the 20x KDZ using LGUP (reason why I did this will be explained below...). But this means that recovery is not available to get get into bootloader mode that way. And I have not yet had a complete successful boot after the KDZ flash to enable USB debugging, which would allow me to get into bootloader mode with the adb reboot bootloader command. So essentially, only download mode is available at this point, uggh...
The back story is that I just bought this used H811 to try out steadfasterX's LOS16, which, by the way, is fantastic! And almost immediately, the phone started displaying bootloop-ish symptoms. For example, like after the initial bootloader unlock, which I did immediately on receiving the device just a few days ago, the phone crashed during the optimizing apps step of the subsequent reboot (it probably overheated). I should have just relocked the bootloader at that point, and sent it back to the vendor for replacement. But I was anxious to try LOS16, and between occasional crashes, I eventually got it installed. But over the next few days, the crashing and occasional bootlooping became so progressively worse that I decided I really did need to send it back for replacement. So today I reflashed the 20x KDZ with LGUP, and that worked fine. But I'd like to relock the bootloader, too, so the vendor doesn't claim I screwed with it, and thus, that they are not responsible for replacing it. But as I mentioned, the only mode available at this point is download mode because it is purely bootlooping on the initial text screen without even getting to the TMo logo.
If I could get into bootloader mode, I could try to do either a a.) fastboot oem lock (given it is fully stock with the recent 20x KDZ flash, there should be no chance of bricking...), or b.) I could also flash just the misc partition extracted from the 20x KDZ. But again, without recovery, nor the possibility to enable USB debugging, I cannot get into bootloader mode. So that's why download mode is my only option.
steadfasterX's SALT works with download mode, but it cannot flash single partitions yet to follow the misc partition flashing strategy I mentioned above.
So what options does this leave me?
Option 1.) phone is in the freezer right now to see if I can get just one more good boot in order to get enable USB debugging, and thus, get to bootloader mode via adb; and from there, then relock the bootloader so the vendor doesn't see the bootloader unlocked message, and claim that I am responsible for the problems...; yeah, the freezer method is a long shot, but in the past with a VS986 that was bootlooping, I did get one final boot out of it for data rescue using this freezer method...
Option 2.) in download mode and via SALT, I can get a shell into the phone; maybe there is a way to flash just the misc partition (extracted from the 20x KDZ) via a command line in that shell, and thus, get the system back to a locked state?
Option 3.) well, send it back to the vendor as is, and hope that they do not try to claim it is my fault because the see the unlocked bootloader message...
Option 4.) if options 1-3 do not work, well, perhaps give LG a call to see if they will fix the circuit board; by the way, they did it for the VS986 I mentioned above without any questions whatsoever; but the difference is that I was the original purchaser of that VS986 whereas this H811 is a secondhand purchase, and LG might use that as a reason for not fixing it.
Any other options that I might be missing? Thanks for any wisdom or suggestions you might be able to provide!
Anyway, my learning lesson from all of this is patience--like I said, I should have returned the device immediately on seeing the first signs of bootlooping because in my experience with both the VS986, and this newly received H811, well, once bootlooping symptoms start, they progress very quickly...
Click to expand...
Click to collapse
For boot looping tricks see my signature while I think freezer is your best bet here .
In SALT -> advanced menu -> wipe partitions
Choose misc and wipe only that.
Locked again .
Sent from my OnePlus 6T using XDA Labs
steadfasterX said:
For boot looping tricks see my signature while I think freezer is your best bet here .
In SALT -> advanced menu -> wipe partitions
Choose misc and wipe only that.
Locked again .
Click to expand...
Click to collapse
Ah, wonderful! I was thinking that there were some special bits in the misc partition, and thus, it had to be flashed. But if I can simply wipe it, perfect! Thanks so much, steadfasterX, for your unending generosity with helping the community here!
No luck with the freezer technique after several attempts. I did get as far as the T-Mobile logo on one try, but it went back to bootlooping immediately. So I proceeded with the misc partition wipe via SALT, and the operation appeared go fine with a success message. But then on rebooting, the bootloader unlocked message still appeared. Not that it should make a difference, but I repeated the operation several times and used several different reboot mechanisms--via that SALT reboot button, pulling the battery, etc., but the bootloader unlocked message still sticks. So it looks like I might have to send it back as is.
verbage said:
No luck with the freezer technique after several attempts. I did get as far as the T-Mobile logo on one try, but it went back to bootlooping immediately. So I proceeded with the misc partition wipe via SALT, and the operation appeared go fine with a success message. But then on rebooting, the bootloader unlocked message still appeared. Not that it should make a difference, but I repeated the operation several times and used several different reboot mechanisms--via that SALT reboot button, pulling the battery, etc., but the bootloader unlocked message still sticks. So it looks like I might have to send it back as is.
Click to expand...
Click to collapse
Ah yea the h811 is different then the others .. I rem again.. There are also persist and others involved for the h811 . You could flash the ilapo TWRP from my leech server and flash the following partitions with dd:
devinfo, misc, persist, persistent, drm, sns
Ensure you use the exact same firmware as your current bootloader stack
Sent from my OnePlus 6T using XDA Labs
steadfasterX said:
Ah yea the h811 is different then the others .. I rem again.. There are also persist and others involved for the h811 . You could flash the ilapo TWRP from my leech server and flash the following partitions with dd: devinfo, misc, persist, persistent, drm, sns
Click to expand...
Click to collapse
Hmmm, I wish I could flash the ilapo TWRP, but after recently flashing the official 20x KDZ using LGUP, I have not been able to get even one successful, complete boot to enable USB debugging. And of course, the TWRP recovery partition was vaped by flashing the KDZ, too. So the only functionality available at this point is download mode. But I have not yet found a way to flash only select partitions (like the six you mentioned) in download mode. For sure, it must be possible (maybe like by using dd for manual, command line flashing using the limited shell provided by SALT). But I am not at that level of expertise yet
This said, I have been doing some exploring regarding the six partitions you mentioned. I used SALT to unpack the original H811 20x KDZ image, and it seems that five of the six partitions (devinfo, misc, persistent, drm, sns) are just filled with zeros. So I suspect there is no real need to actually flash those directly--I think I can just wipe them with SALT for the same effect, right? This leaves just the sixth partition--persist--which is almost all zeros itself, too, with the exception of about 3,500 non-zero bytes spread throughout the file. So maybe in the long run this might boil down to simply having to flash one partition (i.e. persist) as the rest can be wiped since they are all zeros anyway? Whatever the case, whether I have to flash just one partition or all six, the problem remains--there is no straightforward path available to me for flashing a single selected partition via download mode.
-------------------------------
Okay, I have been sitting on the above paragraphs for a couple of days, which gave me some more time to ponder the situation, and make some useful observations. In particular, I have closely watched the dim screen on the H811 while using LGUP to flash the official 20x KDZ image. At one point about halfway through the process, it starts quickly flashing up the names of partitions as it presumably flashes them by name. It appears that the persist partition is one of those which is flashed... And so (maybe?) eureka--could this solve my dilemma of having to flash just a single, selected partition via download mode???
More specifically, if I just load the full KDZ image via LGUP, which takes care of the persist partition, and then if I just wipe the other five partitions (devinfo, misc, persistent, drm, sns) under SALT, well, will this effectively relock the bootloader???
Happy to hear any comments about this before I attempt it!
verbage said:
Hmmm, I wish I could flash the ilapo TWRP, but after recently flashing the official 20x KDZ using LGUP, I have not been able to get even one successful, complete boot to enable USB debugging. And of course, the TWRP recovery partition was vaped by flashing the KDZ, too. So the only functionality available at this point is download mode. But I have not yet found a way to flash only select partitions (like the six you mentioned) in download mode. For sure, it must be possible (maybe like by using dd for manual, command line flashing using the limited shell provided by SALT). But I am not at that level of expertise yet
This said, I have been doing some exploring regarding the six partitions you mentioned. I used SALT to unpack the original H811 20x KDZ image, and it seems that five of the six partitions (devinfo, misc, persistent, drm, sns) are just filled with zeros. So I suspect there is no real need to actually flash those directly--I think I can just wipe them with SALT for the same effect, right? This leaves just the sixth partition--persist--which is almost all zeros itself, too, with the exception of about 3,500 non-zero bytes spread throughout the file. So maybe in the long run this might boil down to simply having to flash one partition (i.e. persist) as the rest can be wiped since they are all zeros anyway? Whatever the case, whether I have to flash just one partition or all six, the problem remains--there is no straightforward path available to me for flashing a single selected partition via download mode.
-------------------------------
Okay, I have been sitting on the above paragraphs for a couple of days, which gave me some more time to ponder the situation, and make some useful observations. In particular, I have closely watched the dim screen on the H811 while using LGUP to flash the official 20x KDZ image. At one point about halfway through the process, it starts quickly flashing up the names of partitions as it presumably flashes them by name. It appears that the persist partition is one of those which is flashed... And so (maybe?) eureka--could this solve my dilemma of having to flash just a single, selected partition via download mode???
More specifically, if I just load the full KDZ image via LGUP, which takes care of the persist partition, and then if I just wipe the other five partitions (devinfo, misc, persistent, drm, sns) under SALT, well, will this effectively relock the bootloader???
Happy to hear any comments about this before I attempt it!
Click to expand...
Click to collapse
I just know that the mentioned partitions are involved in unlocking the bootloader on a h811 - so they are involved in locking it down as well.
while doing my PoC for unlocking all g4's we found that if you backup ALL these partitions when your device is unlocked and re-flash them on the same device (h811 only) while it is locked it will be unlocked again.
the thing is lgup will never flash ALL partitions on a regular flash and thats why you keep your unlocked state (usually) after flashing a new kdz.
For sure thats the case for misc and very likely for the above mentioned.
afaik selecting the refurbish mode will flash any of them.
so TLDR; you COULD wipe the above partitions in SALT, one by one and boot after each to see if its enough.
the second option is to use the lgup developer version. it might be able to flash single partitions (havent used that for long time). would give it a try but you have to google for it.
the third option is opening a shell with SALT while in download mode (advanced menu) and see if you can do this:
https://forum.xda-developers.com/showpost.php?p=74433698&postcount=149
btw: what is the LAF protocol version shown in the SALT main window? could you pls share the debug log (advanced menu -> debug log -> upload button)
yea and the last resort would be to bring the device down to 9008 mode and using QFIL to re-flash all partitions involved (requires a lot of knowledge and preparation though)
.-
steadfasterX said:
I just know that the mentioned partitions are involved in unlocking the bootloader on a h811 - so they are involved in locking it down as well.
Click to expand...
Click to collapse
Thanks for all the pointers and great guidance! I will see where it takes me this weekend.
For the moment, the LAF protocol version is listed as 1000001, and I posted the SALT debug log at https://bpaste.net/show/eqxU.
verbage said:
Thanks for all the pointers and great guidance! I will see where it takes me this weekend.
For the moment, the LAF protocol version is listed as 1000001, and I posted the SALT debug log at https://bpaste.net/show/eqxU.
Click to expand...
Click to collapse
thats great. this version is fully supported in SALT for flashing!
start SALT in a terminal with
Code:
sudo ~/programs/SALT/salt --experimental
and you get new buttons in the main window.
That makes things a lot easier I guess
-.
steadfasterX said:
thats great. this version is fully supported in SALT for flashing!
start SALT in a terminal with
Code:
sudo ~/programs/SALT/salt --experimental
and you get new buttons in the main window.
That makes things a lot easier I guess
-.
Click to expand...
Click to collapse
Yes, I saw the flashing temporarily not auto-enabled comment in the log, and was about to hunt down how to do it, but now that I know the needed switch, perfect. In fact, I just did it, and I see the new buttons with extended functionality--great! I can't play any more now, but for sure, this weekend!
Thank you so much, steadfasterX, for your generous and unending support for the user community here!
verbage said:
I can't play any more now, but for sure, this weekend!
Click to expand...
Click to collapse
Okay, okay, okay--I had time to play...
I first backed up the six H811 partitions in question (i.e. devinfo, misc, persist, persistent, drm, sns) just in case... And then wiped all six of them in SALT.
Now the phone reboots with no unlocked bootloader message on startup--great. Still crazy bootlooping, though, but now without the unlocked bootloader warning so I feel much more confident in exchanging it for a replacement.
In sum, wiping those six partitions does the trick--no need to flash just the persist partition as was discussed in previous postings. For sure, that might wreak havoc with the MAC addresses or similar, but in this case, it doesn't really matter because the phone is already completely disfunctional because of the bootlooping.
Thanks again, steadfasterX!
verbage said:
Okay, okay, okay--I had time to play...
I first backed up the six H811 partitions in question (i.e. devinfo, misc, persist, persistent, drm, sns) just in case... And then wiped all six of them in SALT.
Now the phone reboots with no unlocked bootloader message on startup--great. Still crazy bootlooping, though, but now without the unlocked bootloader warning so I feel much more confident in exchanging it for a replacement.
In sum, wiping those six partitions does the trick--no need to flash just the persist partition as was discussed in previous postings. For sure, that might wreak havoc with the MAC addresses or similar, but in this case, it doesn't really matter because the phone is already completely disfunctional because of the bootlooping.
Thanks again, steadfasterX!
Click to expand...
Click to collapse
Haha great ! Glad it worked for you ! Hope the replacement goes fine now
Sent from my OnePlus 6T using XDA Labs
Hi all!
Long story short, I beefed it...
I tried flashing the unofficial twrp and accidentally did format all on spflashtool.
I'm two months in and for the life of me I can't fix my phone... I've even tried to learn how to write a custom OS myself to fix it but I'm definitely not smart enough.
So, here's where I'm at right now:
When I flash the engineering ROM, the phone boots normally and all that seems to work, but flashing the official MIUI causes a bootloop to the stock recovery.
In there, there's the message "NV data is corrupted".
I'm 2 months in now, so I've seen almost all google pages, so yes, I've tried flashing using the official tool, flashed vbmeta with --disable-verity and --disable-verification.
It's my phone and I have the box here, so I have both IMEI numbers which I managed to flash in the engineering ROM, but flashing the normal MIUI somehow deletes the IMEI numbers again.
I can get into fastboot so the bootloader is unlocked, but I can't boot into the system so I can't enable dev options.
please, if you can help I'm more than happy to answer any other questions and being called an idiot :')
help me, XDA, you're my only hope
check the link
BootLoop not letting me access fastboot
Okay so when I flashed Magisk boot image my device activated boot problems. And when I tried to access recovery mode via adb (from Android Studio), my phone entered a bootloop from which I cannot exit. Vol down + power buttons does not work...
forum.xda-developers.com
I'm in the same exact boat as you...That guide was absolute trash and I can't find anything.
historypm said:
I'm in the same exact boat as you...That guide was absolute trash and I can't find anything.
Click to expand...
Click to collapse
Hold tight, I'm very close to fixing it!
Got everything working except mobile network. As soon as I figure that out, I'll post a fix here
RadixMalum said:
Hi all!
Long story short, I beefed it...
I tried flashing the unofficial twrp and accidentally did format all on spflashtool.
I'm two months in and for the life of me I can't fix my phone... I've even tried to learn how to write a custom OS myself to fix it but I'm definitely not smart enough.
So, here's where I'm at right now:
When I flash the engineering ROM, the phone boots normally and all that seems to work, but flashing the official MIUI causes a bootloop to the stock recovery.
In there, there's the message "NV data is corrupted".
I'm 2 months in now, so I've seen almost all google pages, so yes, I've tried flashing using the official tool, flashed vbmeta with --disable-verity and --disable-verification.
It's my phone and I have the box here, so I have both IMEI numbers which I managed to flash in the engineering ROM, but flashing the normal MIUI somehow deletes the IMEI numbers again.
I can get into fastboot so the bootloader is unlocked, but I can't boot into the system so I can't enable dev options.
please, if you can help I'm more than happy to answer any other questions and being called an idiot :')
help me, XDA, you're my only hope
Click to expand...
Click to collapse
Good evening, sorry for my bad English, but I have the same problem when this happened, I had miui V13.0.7.0 there, I got bootlop, I loaded V12.5.2.0 there and the phone worked everything except the network, try and let me know
You have to download the firmware and paste it into the platform tools folder and click flash all.bat
I had lineage19.1 working and a respective custom recovery with it. That was cool. Then I got dumb...
I proceeded to flash the new custom recovery for lineage-20.0-20230103-recovery-lemonadep.img. I am still not sure if the recovery needs updates or how to do so anyway. Can I still upgrade to version 20.0 with a recovery from 19.1? Regardless I am stuck in fastboot loop.
I am lost. I can't get to recovery mode anymore. How do I check things and see what to do next?
Hi.
I have been looking into lemonadep a bit lately.
I found a (renewed) 9 Pro a few days ago.
Should be here by the end of the week and I test more then.
Might want to ask your question in the LOS 20 thread.
Development [ROM][OFFICIAL][lemonadep][13] LineageOS 20 - Link
Cheers.
MintyFreshSocks said:
I had lineage19.1 working and a respective custom recovery with it. That was cool. Then I got dumb...
I proceeded to flash the new custom recovery for lineage-20.0-20230103-recovery-lemonadep.img. I am still not sure if the recovery needs updates or how to do so anyway. Can I still upgrade to version 20.0 with a recovery from 19.1? Regardless I am stuck in fastboot loop.
I am lost. I can't get to recovery mode anymore. How do I check things and see what to do next?
Click to expand...
Click to collapse
I suppose you are about to flash lineage20,
if so, search "payload-dumper" tool
from the rom's payload.bin extract dtbo, vendor_boot and boot img files, flash them to the related partitions, and your phone should be ready to load the new rom via sideloading it
Thank you for your time and consideration.
I have lost track of my own efforts here. Basically I'm right where I left off, with a little less battery. I am now onto the process of using MSM tool from this place. I get things started and then I reach "param preload failed" under the status, in the MSM tool. Is there any hope? I get scared when reading this disclaimer...
"If you modified any partition not touched by MSM, namely param and persist but there are others, you face a possibility of a hard brick. MSM will reset your "Enable OEM Unlocking" in dev settings and you might get a corrupt boot. Restore your backups before attempting. That said, If all you just tried to convert a ROM using OTA payload.bin, you should be fine."
...because yea I'm a curious kitty. I think I was messing in just about everything dangerous that I could... I still have a bootloader screen, thats fun to play with... I've got the right driver from qualcomm and it says the proper "QDloader 9008." But still no dice with MSM.
Is MSM the only option? I found this other OEM reFlash tutorial. I have questions tho...
Step 4: Gives me a prompt that says "Server Busy" "This action cannot be completed because the other program is busy. Choose 'Switch To' to activate the busy program and correct the problem."
I'm gonna stop running through the dark and hope someone can be my savior. A wing and a prayer.
What phone you got tmo,global EU?
I always assumed it was the global version. Bought it in the USA. Model LE2125
Host Machine is a Legion 7 16ACHg6.
Perhaps "New generation USB 3.0/3.1 ports may not allow the QPST tool to recognize your phone and could also cause problems during the flashing process."
Q1. Would there be a way to test and verify this possibility with my current machine? I am using the factory "red" usb-c cable.
Q2. How to verify no other drivers are causing issues simultaneously. (I went through quite a number of drivers before this)
Alas, my previous question regarding this "alternative MSM tutorial" and what the Server Busy means, should take precedence I think.
I am new to XDA and the android community and I truly love and thank you all. There is so much here and so much more opportunity. Thanks again.