Related
Hello, so...where to start. Phone was original stock. It randomly froze and started boot looping. I had installed the Sprint update 6.23.651. 6 about a month prior to this. (the update made it sluggish)
So I did research, I went to Hboot, but recovery and factory reset didnt do anything. After selecting either one, it just started looping immediately. So tried fastboot commands, nothing work really except erase cache. ADB did not show anywhere even though my drivers were up to date. Contaced HTC and dowloaded the update application. Put the phone on fastboot, ran the wizard. when it was all done, it said it was finish updating. But was still looping. HTC told me i had to send it in and pay a fee. BS! i did nothing to my phone, they broke it with the updates.
Long story short, i figure how to unlock it. Great, so i started trying to flash updates that had the same CID and Model. To list last few:
1) Guru_Reset_M7_Sprint_1.31.651.2
2)Guru_Reset_M7_Sprint_3.04.651.2
3)RUU_M7_WLS_JB_50_Sprint_1.29.651.7
But none of them worked. Just gave me some error that i cant recal. tried other comands that further bricked my phone, like (fastboot flash boot boot_signed.img) (fastboot flash recovery recover.img). I have been working on this for 3 days, today is the 4th. After this, it would loop once and turn off. So i tried multiple recovery images out of the zips listed above. Those made it so that it finally say entering recovery, but then it would loop and turn off.
Then i kept reading that people are being told to relock the hboot (fastboot oem relock) and then flash the zip. Tried it with those 3 listed above again. the 12 signature error showed up of course.
Tried running the update 6.23....from spring, the wizard gave me some error, basically, my phone is way off to even set back to where it was at first.
After some research, I tried tried cwm 6.0.4.8-m7 to have a standard known recovery image flashed. I had actually tried it before but it didnt work. and for whatever reason, it lunched clockworkrecovery.
Here i erased data/factory reset. Also wiped the calvik data (something like that) since that what it says everywhere to do for first step. (kept a mental note that wouldn't fix my phone since it was further bricked than before i began). But before exiting the recovery mode, i noticed that adb commands were finally working! so i tried the two methods if found to install a rom. Sideload and push. Through side load, it takes forever to reach 100% but once it gets there it says
* failed to write data 'protocol fault (no status)' * {in cmd}
So i tried to push. after pushing it to the sdcard (internal btw) i got to the sdcard and run it. End result. *(bad) installation aborted * {on the phone}
so then im like whatever, lets reboot and see if anything changes. Bootlooping still. Recovery and factory/reset send me to bootloader now (it used to just loopboot). so i flash recovery again. Doesnt work. fastboot erase cache, then flash image, still not working. So i managed to remember some steps i followed that might of been the reason recovery worked. so I flash boot_signed.img, then flash recovery. doesnt work. so fastboot boot boot.img cmd responds but phone freezes, then manually turn it off. then get back into fastboot, flash recovery, erase cache, flash recovery(x3 times). and recovery works.
This is the 3rd time i got into recovery, but it takes me about 10 mins of doing the different combinations of the what i just mentioned before it goes through.
So im at the point where i could possibly get it fixed. But nothing seems to work
I would really appreciate it if someone could help me. I know that the rom has to match my hboot version? but im at hboot 1.6 and the only thing i found was here
http://forum.xda-developers.com/showthread.php?t=2795856
but that only gives me the firmware and the exe that doesnt work for me. I also tried to run the exe and during it, seach my C-drive for rom.zip. Apparently it creates a temporary rom. I pulled it out, it doesnt contain everything
Last thing i was going to do, was put relock it and run recovery. but because im not sure how to make recovery work every time from the get-go. when relocked, recovery didnt work, so i had to flash, thus i had to unlock, spent 10 minutes making it work and forgot that it was unlocked. I could try and see if i could relock and get recovery to run. But it could take forever to get it to work, thus is why im looking to see if there is anything i can do from recovery. (also, both time i was in recovery, i did erase wipe everything, so maybe thats why it wont work after reboot and have to reflash it)
This is where im on.
clockwork recovery window in phone.
phone stuff:
hboot-1.6 something
s-on
os 6.23.651...etc
cid SPCS_001
modelid: PN0720000
the guru zip mention above have the same cid and modelid as my phone according to
http://www.htc1guru.com/downloads/ruu-file-downloads/
Thank You, I hope i am as close to fixing it as i think i am.
madeofscars117 said:
Hello, so...where to start. Phone was original stock. It randomly froze and started boot looping. I had installed the Sprint update 6.23.651. 6 about a month prior to this. (the update made it sluggish)
So I did research, I went to Hboot, but recovery and factory reset didnt do anything. After selecting either one, it just started looping immediately. So tried fastboot commands, nothing work really except erase cache. ADB did not show anywhere even though my drivers were up to date. Contaced HTC and dowloaded the update application. Put the phone on fastboot, ran the wizard. when it was all done, it said it was finish updating. But was still looping. HTC told me i had to send it in and pay a fee. BS! i did nothing to my phone, they broke it with the updates.
Long story short, i figure how to unlock it. Great, so i started trying to flash updates that had the same CID and Model. To list last few:
1) Guru_Reset_M7_Sprint_1.31.651.2
2)Guru_Reset_M7_Sprint_3.04.651.2
3)RUU_M7_WLS_JB_50_Sprint_1.29.651.7
But none of them worked. Just gave me some error that i cant recal. tried other comands that further bricked my phone, like (fastboot flash boot boot_signed.img) (fastboot flash recovery recover.img). I have been working on this for 3 days, today is the 4th. After this, it would loop once and turn off. So i tried multiple recovery images out of the zips listed above. Those made it so that it finally say entering recovery, but then it would loop and turn off.
Then i kept reading that people are being told to relock the hboot (fastboot oem relock) and then flash the zip. Tried it with those 3 listed above again. the 12 signature error showed up of course.
Tried running the update 6.23....from spring, the wizard gave me some error, basically, my phone is way off to even set back to where it was at first.
After some research, I tried tried cwm 6.0.4.8-m7 to have a standard known recovery image flashed. I had actually tried it before but it didnt work. and for whatever reason, it lunched clockworkrecovery.
Here i erased data/factory reset. Also wiped the calvik data (something like that) since that what it says everywhere to do for first step. (kept a mental note that wouldn't fix my phone since it was further bricked than before i began). But before exiting the recovery mode, i noticed that adb commands were finally working! so i tried the two methods if found to install a rom. Sideload and push. Through side load, it takes forever to reach 100% but once it gets there it says
* failed to write data 'protocol fault (no status)' * {in cmd}
So i tried to push. after pushing it to the sdcard (internal btw) i got to the sdcard and run it. End result. *(bad) installation aborted * {on the phone}
so then im like whatever, lets reboot and see if anything changes. Bootlooping still. Recovery and factory/reset send me to bootloader now (it used to just loopboot). so i flash recovery again. Doesnt work. fastboot erase cache, then flash image, still not working. So i managed to remember some steps i followed that might of been the reason recovery worked. so I flash boot_signed.img, then flash recovery. doesnt work. so fastboot boot boot.img cmd responds but phone freezes, then manually turn it off. then get back into fastboot, flash recovery, erase cache, flash recovery(x3 times). and recovery works.
This is the 3rd time i got into recovery, but it takes me about 10 mins of doing the different combinations of the what i just mentioned before it goes through.
So im at the point where i could possibly get it fixed. But nothing seems to work
I would really appreciate it if someone could help me. I know that the rom has to match my hboot version? but im at hboot 1.6 and the only thing i found was here
http://forum.xda-developers.com/showthread.php?t=2795856
but that only gives me the firmware and the exe that doesnt work for me. I also tried to run the exe and during it, seach my C-drive for rom.zip. Apparently it creates a temporary rom. I pulled it out, it doesnt contain everything
Last thing i was going to do, was put relock it and run recovery. but because im not sure how to make recovery work every time from the get-go. when relocked, recovery didnt work, so i had to flash, thus i had to unlock, spent 10 minutes making it work and forgot that it was unlocked. I could try and see if i could relock and get recovery to run. But it could take forever to get it to work, thus is why im looking to see if there is anything i can do from recovery. (also, both time i was in recovery, i did erase wipe everything, so maybe thats why it wont work after reboot and have to reflash it)
This is where im on.
clockwork recovery window in phone.
phone stuff:
hboot-1.6 something
s-on
os 6.23.651...etc
cid SPCS_001
modelid: PN0720000
the guru zip mention above have the same cid and modelid as my phone according to
http://www.htc1guru.com/downloads/ruu-file-downloads/
Thank You, I hope i am as close to fixing it as i think i am.
Click to expand...
Click to collapse
Make sure you have latest HTC drivers installed on your computer, relock your bootloader and then launch the 6.23.651.6 RUU
Wow, I dont know why I didnt think of that. Everything must be running together.
Alright, so it updated. My phone is back to how it used to be looping like when it first broke. So, from here. Should I unlock it, flash the recovery to cwm, relock bootloader and see if it enters cwm recovery and try to push or sideload a rom?
when relock, i beleive it restarts, so i dont know if it that would stop the cwm recovery from working. Also, if i manage to get all of what i mentioned working. Wouldnt I get the 12 signature error?
Im sorry, its been days and nothing seems clear anymore since I havent been able to fix it
Hi everyone, I'm having a lot of problems with my phone: last night, after it dropped to 0% battery life, it wouldn't charge. So i waited a while and ifinally managed to turn it on, but It wouldn't go past the Cyanogenmod logo. So i tried few things,first wiping cache, then factory reset from TWRP and I even tried the "Factory" option in the fastboot screen. Nothing worked, and it even got worse I think, TWRP says it's unable to mount /data partition and /storage partition. I don't know what caused it, and i don't remember the precise moment it became "unmountable" for the first time (since I've been trying to fix this thing for like 24 hours now).
Since i couldn't fix it via recovery, I tried looking for people who had the same problem on the internet, and I tried everything i could find. (like this: http://forum.xda-developers.com/showthread.php?t=2683787).
I then tried to go back to stock rom via adb and fastboot, but without success.
The main problem with fastboot is the fact that it doesn't change anything in my phone, it gives no errors when i try to flash the stock rom, but when i reboot my phone, nothing changes, or at least this is my opinion, since I still get the cyanogenmod logo, and TWRP doesn't get replaced (while it should go away, since when in the whole process of flashing the rom, i also flash recovery.img, which shouldn't be TWRP).
I tried a whole lot of other commands too, like "fastboot erase recovery", but TWRP is still there, and so is the cyanogenmod logo.
This is why i think fastboot is unable to write in my phone, but if that's the case, it should at least give errors.
So, wrapping up, my data partition seems to be corrupted, and flashing the stock rom still gets my into a bootloop (with the logo from the previous rom and TWRP still there).
Do you have any advice?
P.S: my phone is a xt1068
Are you able to pull logcat?
Logcat command works, i don't get errors in the terminal, but in the text file there's only this line : "/sbin/sh: exec: line 1: logcat: not found"
Dmesg works though, I don't know if it's helpful
"
dagrot said:
I then tried to go back to stock rom via adb and fastboot, but without success.
The main problem with fastboot is the fact that it doesn't change anything in my phone, it gives no errors when i try to flash the stock rom, but when i reboot my phone, nothing changes, or at least this is my opinion, since I still get the cyanogenmod logo, and TWRP doesn't get replaced (while it should go away, since when in the whole process of flashing the rom, i also flash recovery.img, which shouldn't be TWRP).
I tried a whole lot of other commands too, like "fastboot erase recovery", but TWRP is still there, and so is the cyanogenmod logo.
This is why i think fastboot is unable to write in my phone, but if that's the case, it should at least give errors.
So, wrapping up, my data partition seems to be corrupted, and flashing the stock rom still gets my into a bootloop (with the logo from the previous rom and TWRP still there).
Do you have any advice?
P.S: my phone is a xt1068
Click to expand...
Click to collapse
I have same phone, you mentioned you also tried to flash stock rom without success, did you flash the partition file aswell before flashing system and the rest of files ? Check the flashfile.xml file into the stock firmware folder to make sure you not missing anything.
Code:
fastboot flash partition gpt.bin
Good luck.
i'm on the same boat. It seems it's a NAND issue, but how come it happens randomly?
It seems to happen (its a bit rare, so don't get worried) when you let your battery drop to 0% and the phone suddently turn off, like what happened to the OP.
Sent from my XT1063 using XDA Free mobile app
Lynse said:
It seems to happen (its a bit rare, so don't get worried) when you let your battery drop to 0% and the phone suddently turn off, like what happened to the OP.
Sent from my XT1063 using XDA Free mobile app
Click to expand...
Click to collapse
If it's a bit rare, how come there are a rather interesting quantity of posts regarding that matter? I'd like to know WHY I can't write even with fastboot. There should be a way of unlocking the NAND / partitions. Even if I try to hard brick it, it's impossible.
PS: can we someone a look at this? http://forum.xda-developers.com/showpost.php?p=56608822&postcount=2
Possibly if we can force the way to QHSUSB mode, phone can be saved.
jhonnyx said:
PS: can we someone a look at this? http://forum.xda-developers.com/showpost.php?p=56608822&postcount=2
Possibly if we can force the way to QHSUSB mode, phone can be saved.
Click to expand...
Click to collapse
Unfortunately I didn't quite understand what that is about, if you happen to try it out let us know.
Anyway, if we don't manage to fix it, I guess I'm going to try and take it back to the store, since it is a common problem. Only problem is I'm on a custom rom and I can't even go back to stock and relock the bootloader, so I don't think they are going to replace it, but it's worth a try.
You can try by helping me to look for a circuit PDF from the board or trying it yourself.
I could try and disassemble it, but you're gonna have to wait a few days, I'm not at home and I'm gonna be back on the weekend.
As for the circuit pdf, I was only able to find videos and guides on how to disassemble it, unfortunately
Dude, no worries. Ive took the back out with all the screws, but I have nothng to make shorts with.... I'll come up with something. Take your time and keep me posted.
any news concerning this problem? i have tried searching for a manual but I did not succeed.
Anyways after finding the manual, we can short circuit the 2 capacitors there and the phone will be in qhsusb mode.
And after that ?
gbb14 said:
any news concerning this problem? i have tried searching for a manual but I did not succeed.
Anyways after finding the manual, we can short circuit the 2 capacitors there and the phone will be in qhsusb mode.
And after that ?
Click to expand...
Click to collapse
After that.... well.... after some research, we'll be needing singleimage.bin to use the blankflash utility for lollipop phones (mbm-ci 5.0 lollipop) so somebody can generate the singleimage.bin for us.
Once we have that, we can try to flash the phone at lowlevel to see what happens.
I will search the internets in hoping to find the schematics of this phone.
Keep me informed if you find it faster .
Cheers mate
we can connect through hangouts / etc.
look up for my user at gmail
So I recently tried updating MIUI v5 to MIUI v6. However, I stupidly opted for the FOTA update, rather than updating using recovery.
After running the update, my phone rebooted and it worked fine, MIUI v6 running great. However, because I'd updated using the in-built updater, my data and apps were still there from before. This was causing no-end of 'process stopped running' alerts, which drove me crazy after around 10 minutes.
Therefore, I decided to try and wipe my data. I went to the recovery menu and found that MIUI had installed its own Chinese recovery, my previous TeamWin one was gone. So I fumbled around and managed to find the 'Wipe data' etc. option, and chose it. I was presented with a couple more options which I didn't understand, and (stupidly) accepted both. This left me with a phone that would no longer boot past the 'Sony' logo. I was also unable to access the Chinese recovery menu.
Feeling a little worried at this point, I started to Google around for guides on how to flash a recovery back onto a phone stuck in a boot loop. After hours of searching, I decided it wasn't possible and instead follow a guide for fixing 'boot loops' through flashing an original Sony 'ftf' firmware using flashtool.
Now, the guide I was following was quite old, and provided a link to 'C6903_14.2.A.0.290_Global LTE' - so this is what I used to flash (which I'm now regretting). Before flashing, I was presented with some options, for which the guide I was following recommended I deselect the 'kernel' option. So I did this too.
After around 10-15 minutes and what seemed like a successful flash, I tried turning the phone on. This time, the Sony logo appears, then disappears to a black screen, and then the backlight turns off, followed by the Sony logo, then a black screen, then backlight turning off, etc. So slightly different behaviour to before, but still boot looping.
I think what may have happened is that MIUI includes an updated kernel, and through flashing the 14.2.A.0.290 firmware without a kernel, I've introduced some sort of incompatibility.
The problem I'm having now is getting another firmware onto the phone in order to resolve this. For some reason, despite flashtool recognising the phone being plugged in with flash mode, it refuses to load the firmware - I'm instead presented with the message:
"You must have the according fsc script to flash this device."
Does anyone know how I might be able to get around this? I admit to being a bit of a noob when it comes to flashing so have probably dug my own hole here, and seem to have left myself completely unable to work out what I need to do in order to get back out! Any help would be hugely appreciated.
Please see the attached screenshot of what I see when I try flashing with flashtool. The whole flash takes around 2 seconds, so it appears as though nothing's actually happening. However, it did flash successfully before, only without the kernel (which I think is what's causing my problems).
Please help!
langauld said:
Please see the attached screenshot of what I see when I try flashing with flashtool. The whole flash takes around 2 seconds, so it appears as though nothing's actually happening. However, it did flash successfully before, only without the kernel (which I think is what's causing my problems).
Please help!
Click to expand...
Click to collapse
This version of Flashtool you're using is known to require some files for your device to be able to work.
Try using the version before it.
Oh and NEVER:
- Wipe /system and /data using recovery with unlocked bootloader (it will remove everything and the phone will not be able to boot).
- Flash an ftf of a older android version (like flashing kitkat on top of lollipop) without including kernel because that will cause a bootloop. (not sure about flashing lollipop on top of kitkat but I think it's the same)
Just2Cause said:
This version of Flashtool you're using is known to require some files for your device to be able to work.
Try using the version before it.
Oh and NEVER:
- Wipe /system and /data using recovery with unlocked bootloader (it will remove everything and the phone will not be able to boot).
- Flash an ftf of a older android version (like flashing kitkat on top of lollipop) without including kernel because that will cause a bootloop. (not sure about flashing lollipop on top of kitkat but I think it's the same)
Click to expand...
Click to collapse
You sir, are a god amongst men. I'd never have thought to try the previous version of FlashTool. From reading around, I knew some devices had issues with it, but because it lists the Z1 as being 'supported', I didn't think that would apply to me.
I flashed again without deselecting the kernel and it booted first time. Thank you again.
langauld said:
You sir, are a god amongst men. I'd never have thought to try the previous version of FlashTool. From reading around, I knew some devices had issues with it, but because it lists the Z1 as being 'supported', I didn't think that would apply to me.
I flashed again without deselecting the kernel and it booted first time. Thank you again.
Click to expand...
Click to collapse
Glad I could help.
I'm fairly sure I've managed to brick my phone, but I wanted to check before I accept defeat.
In short, I tried to follow this guide, huawei-p9-nougat-emui5-0-full-firmware-b339-europe-vodafone flashed the second file first, and couldn't get the phone to boot.
Attempted to use the recovery tool built in, but it couldn't recover the phone.
Eventually, under the assumption I had entirely ruined my phone, and some searching came across this tool DC-Phoenix-flash-repair-tutorial
Attempted to use it to flash the initial image as mentioned in the first link, which didn't work.
After multiple attempts at various peoples suggestion, I tried to go back to basics, so used the DC Pheonix tool to flash the TWRP image to the device, which appears to have worked, I can boot into TWRP.
I then booted into TWRP and tried to install the stock ROM from this forum, which fails because it cannot mount /data /cust etc
I've gotten to the point of giving up after spending hours doing what I thought were fixes to realise I've probably destroyed my phone, any help would be greatly appreciated
I thought I had finally reached nirvana with this device thanks to the help of so many here. I had TWRP, root, defeated encryption, and a nicely running Android. I was even able to make TWRP backups of /data and /boot (to be precise, at one point - not sure when it was but I think after initial Android setup - I was able to make a much more complete TWRP backup with many partitions never shown again but that disappeared at some point).
So I went on with my transition from my old Note3 phone to this device. I spent all day yesterday moving TiBackups of user apps, copying across data, making more limited TWRP backups (of data and boot the only options - except if I mounted system_root, which allowed me to include /system but that did not actually work either), polishing settings, and thinking I had it made! Throughout all of this I had no problems or signs of problems other than some apps not working on the new device and having to be replaced with alternatives which I completely expected.
At cocktail hour I decided to do a reboot to see the "finished product" of all this effort. When I did, the device tried to boot into Android: I saw the thinq logo but no boot animation, just the thinq logo for a very long time - followed by a screen blank and bootloop. I was able to enter TWRP and things looked "normal" from there. I kept trying to boot into system with no progress. I tried wiping /data, I tried restoring the backups I had made. Nothing changed - still bootlooping.
From within TWRP I can use adb shell to look around. I can see familiar stuff from my installed apps in /data/data and /data/app - including from one of the very last apps I installed (from Play not via TiBackup). I know this was not in any TWRP backup I had taken or restored. So this makes me think that my attempts to restore /data from backups or even wiping /data from TWRP have had no effect despite no errors showing. I wanted to see what was in /system so I mounted system and now in adb shell I can see familiar stuff in there too - including busybox installed into xbin. I can also mount vendor and in /vendor/etc I can see the fstab.judypn with encryptable for /data.
One thing I do NOT see is the result of one of the last things I did/tested. I installed Termux, installed the dropbear package, and copied the resulting dbclient binary to /data/local. After doing this I actually invoked /data/local/dbclient with success. Now, I do not see anything in /data/data/com.termux/files/usr related to dropbear nor do I see the dbclient in /data/local.
When I tried to power off from TWRP, the device never fully turned off. The animation showing the power level remained showing all the time but it was just a circle with lightening bolt but no actual power level showing. Removing power cable made no difference. Finally, I left the device in TWRP and powered on. At least I could blank the screen and prevent the battery from running dry.
All of this is with slot A current as reported by TWRP. I cannot seem to enter fastboot mode (I was previously able to do this from a power off condition by holding volume up and inserting USB). Of course, I am not able to achieve a real powered-off condition. Thankfully, I am still able to enter engineering mode and see the device in QFIL. But I have not tried anything here as of now. I can switch to slot b and get into download mode by holding power up and inserting USB. All attempts to use other TWRP boot options (save recovery and "power off") just put me into bootloop again.
I am stumped as to what is happening, how to "fix" this, or what to do.
Thanks for any suggestions.
Same thing happened to me. Yesterday.
I was going through my system programs, and nuked several of the extra Google Play items (Movies, Music, etc.). Same thing. Boot to V40 ThinkQ screen. Sat there for a while. Then reboot.
Nothing I did brought the old girl back to life. So I started over with kdz and redid everything again. Pain in the ass, but it's working again. Interestingly enough, loading the full kdz didn't relock the bootloader. I used both Refurbish and Partition DL on two separate attempts. Bootloader stayed unlocked throughout, and is still unlocked.
Had a devil of a time getting system to mount. Tried over and over again to get Magisk installed.
What finally worked was rebooting into recovery after pushing the .magisk file, and only then installing Magisk.
[NG]Owner
NGOwner said:
Same thing happened to me. Yesterday.
I was going through my system programs, and nuked several of the extra Google Play items (Movies, Music, etc.). Same thing. Boot to V40 ThinkQ screen. Sat there for a while. Then reboot.
Nothing I did brought the old girl back to life. So I started over with kdz and redid everything again. Pain in the ass, but it's working again. Interestingly enough, loading the full kdz didn't relock the bootloader. I used both Refurbish and Partition DL on two separate attempts. Bootloader stayed unlocked throughout, and is still unlocked.
Had a devil of a time getting system to mount. Tried over and over again to get Magisk installed.
What finally worked was rebooting into recovery after pushing the .magisk file, and only then installing Magisk.
[NG]Owner
Click to expand...
Click to collapse
Well, they say misery loves company and I do feel a bit better just knowing I am not alone here.
Since I could enter download mode, I too decided to try re-flashing the .kdz using LGUP's partition dl and specifically NOT checking boot_a, laf_a or boot_b as described here <https://forum.xda-developers.com/showpost.php?p=82206107&postcount=115>. I was not fast enough to get into TWRP on the automatic reboot and saw that I was brought to a bootable system and an Android start page with the boot loader still locked and TWRP still there.
So did the partition dl again and managed to catch TWRP. I mounted vendor but when I tried to push the fstab I got something I have not seen before "remote could not create file: Read-only file system" and 0 files pushed. To be sure, I used adb shell and cat'ed /vendor/etc/fstab.judypn and it contains force encrypt. So I know things are not quite right.
Trying again from the partition dl. And this time I managed the push. I think I missed re-doing the ramdisk and rebooting into recovery. I made sure to do that this time and now I can proceed. I seem to have managed to get back to a bootable Android with TWRP, Magisk, and defeated encryption once again.
So I wonder if I should try to restore anything from a backup or just redo all of yesterday's efforts (like the movie Groundhog Day)?
Can I ask which device and firmware you are using? Thanks
I would not use any backups aside from the backups in your google account. Redo all of yesterday's efforts (except the one thing that caused the reboot loop ... whatever that was!).
You said your bootloader was relocked after LGUP? Or did you mistype there?
Odd. Mine wasn't, not once. Despite multiple LGUP loads.
I've got a crossflashed Sprint LM-V405UA to US specs 20E.
And yes, misery does love company!
[NG]Owner
NGOwner said:
I would not use any backups aside from the backups in your google account. Redo all of yesterday's efforts (except the one thing that caused the reboot loop ... whatever that was!).
You said your bootloader was relocked after LGUP? Or did you mistype there?
Odd. Mine wasn't, not once. Despite multiple LGUP loads.
I've got a crossflashed Sprint LM-V405UA to US specs 20E.
And yes, misery does love company!
[NG]Owner
Click to expand...
Click to collapse
No, you are correct - I mistyped. My bootloader has remained unlocked (this time I got it right)
Nor sure it matters any, but mine if a 405QA with 20E.
I have read some recently (while searching for this bootloop problem) that LG seems to have long had a problem with bootloops on their devices. Not sure I saw anything specifically about the V40 though. Seems that in the past they were "fixed" with software updates. I do not expect any updates beyond 20E and wonder if 20a (which I think I had earlier) would be any different/better.
I have had great luck with Nandroid and TWRP backups in the past. They have really saved me (most often from myself but also from apps/mods gone wild). Indeed, I used TWRP restore yesterday with the previous night's auto-made backup on my Note 3. It seems that in doing something - maybe the TiBackup of all user apps/data - the phone got messed up and even reboots would not fix it. The TWRP restore certainly did!
I am new to the whole Magisk "systemless" root as I have always used SuperSu before. As I understand it (which is limited for sure) the idea here is to NOT modify system in any way. But I also note that this does not seem to preclude me from modifying things in system using my file manager, for example. And I did some of this sort of thing. If you are nuking pre-installed apps, that would be changing system as well, no? I wonder if that is the activity that caused this?
I am a bit hesitant to re-live yesterday. At least not until I have some idea of what I did that caused this. Not sure what I will do.
Thanks for all the help.
PS - given that I had TWRP backup (of at least /data) and how often I rely upon these in everyday life, I decided to at least try restoring and see what happened. Hard to imagine ending up worse that I was earlier this morning. I did the restore and rebooted to system. I was shocked, quite frankly, to see the system come right up and have many of my previously installed apps visible and working. I did find that I had to re-enable the modules in EdXposed (even though they showed as enabled already) since they were not working) and that brought them back to life.
So I guess I can move forward from here being careful, taking TWRP backups even more often, and rebooting more often to see what, if anything, kills this again.
NGOwner said:
Same thing happened to me. Yesterday.
I was going through my system programs, and nuked several of the extra Google Play items (Movies, Music, etc.). Same thing. Boot to V40 ThinkQ screen. Sat there for a while. Then reboot.
Nothing I did brought the old girl back to life. So I started over with kdz and redid everything again. Pain in the ass, but it's working again. Interestingly enough, loading the full kdz didn't relock the bootloader. I used both Refurbish and Partition DL on two separate attempts. Bootloader stayed unlocked throughout, and is still unlocked.
Had a devil of a time getting system to mount. Tried over and over again to get Magisk installed.
What finally worked was rebooting into recovery after pushing the .magisk file, and only then installing Magisk.
[NG]Owner
Click to expand...
Click to collapse
Well, this happened to me once again. I saw no reason why it should not do so. So I have been re-introducing apps from my TiBackup slowly and in under a strict protocol in an effort to (a) limit the damage done to my work and (b) try to isolate the culprit(s). I decided, since I found that I could restore TWRP backups of /data after re-doing the most of the TWRP install and defeat encryption process, that I would install apps slowly and execute them and in small groups. After each group I would do a reboot to see if that worked. If that worked, I would go into TWRP, run a backup, and name the backup of /data with something to id the app group that was added and seemed fine.
I started working backwards by the first letter of the app name. I first did U-Z and found that worked fine. Took a backup and went on to S-T. After this group it was bootloop time! So I put humpty-dumpty back together, restored the /data backup from U-Z, and this time installed only those apps starting with T. After this a no-problem reboot and a backup of /data and I will continue to plod on with those apps starting with S (and so on).
Horribly tedious. I can see no other way to proceed unless someone has a better idea.
PS - So I re-installed apps starting with S and basically had no problems. Hmmm. But I do recall that when testing execution of some of these apps the first time around, I decided to install busybox (Stericson), AdAway, and Afwall+ out of sequence. Before I did this I decided to check a bit more. I found that there is a Magisk busybox module and even though I have always used Stericson without troubles, I thought it best to use the Magisk module for this. I also found that Magisk has a setting for systemless hosts which could be affected by AdAway. So I enabled that before doing anything with AdAway. I also checked to see if AfWall+ might have any issues and found none. So I guess it is possible that using Stericson busybox or failing to use systemless hosts could have been an issue. I may never know for sure but at least so far I am fine after installing apps that I previously installed and had a bootloop. So FYI.
Alright, I'm a total idiot. I went and did this again, following the mantra: If it aint broke, you're not trying hard enough.
Setting all that aside, I went and tried to do some more debloating of my v40 (used this guide, that I was linked to from here), and wound up in "this fresh hell" again. Dammit! Crap.
So apparently there is a system application that is crucial to the boot of the phone that I uninstalled.
There is a fix to this, but it comes at a cost. Get into TWRP. Navigate to advanced, select Fix Recovery Reboot. Your phone will boot normally now. But you will lose root. And (so far) any attempt to reinstall Magisk to re-obtain root will result in the same bootloop again.
So here's where I need some help:
1) So if I wanted to reinstall my system partition to get back to stock from a KDZ, but still keep my installed apps, etc., how do I do that?
2) How do I get my Slot B to work correctly? It has only bootlooped there. Since I got my phone. Once I get my phone back to operational state with root, how do I make sure that Slot B works (so I have a backup I can fall back on if (when) I bork something else?
[NG]Owner