Hi all,
I'm in a tricky position which is completely my fault, but cannot for the life of me get the phone to boot. In short -
1. updated to October security patch no problem, everything booted up fine
2. in an attempt to get rooted with Magisk again, I installed TRWP and *think* i installed to the wrong partition.
3. I can boot into fastboot, and can load TWRP, but as the touch screen isn't working I can't do anything in there.
4. For some reason adb doesn't seem to be detected, that may have been turned off during the update?
So, anybody got any solutions to me installing the OS again with Fastboot and a TWRP that can't be interacted with?
UPDATE - through some combination of luck and sheer determination, I've managed to get the phone to book again. I flashed the Sept boot file which seemed to kick it into gear, then re-flashed the October boot. All seems ok and I can breathe again. As you were.
Best,
Related
Got myself in a right mess here -
I'm on the 2nd to latest version of N (NPD56N) and cannot for the life of me get any recovery to work. I've just messed about with the decryption problem, and have flashed a no-force encryption boot.img. The phone boots and works fine, but I can't get any recovery to flash, despite fastboot saying it's worked fine. I did have TWRP installed for a bit, but it only worked once and then I got the red explanation mark of death and depression again. Note, the power+vol up does nothing as it usually does - This is the main issue!
I understand i'll need a new boot.img once upgarded to NPD90G, but that's not the issue right now.
I'm trying to go back to stock everything (I mean, I only rooted to get the damn new Nexus launcher to work properly, which I can't even install)
Basically, i'm trying to get on the latest version of N with root access and a stock recovery if possible.
SOMEONE SAVE ME PLS
Thanks
Edit - Finally fixed. Wiped everything I could and used Skipsofts tool to install 6.0.1 and success. No idea what caused it.
Resolved.
I originally had OOS3.0.2, and I tried to get Beanstalk rom installed. Beanstalk didn't load correctly, and I softbricked my phone. I managed to go through the recovery of downloading the qualcomm drivers and that weird updating program and then sideload an older version of OOS (2.2). I went to this link and did method 1 https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/. But when I get things fixed up, I can't seem to update to CM13, or even to do a normal update with root, without root, with twrp, without twrp. Nothing. Strangely enough, no matter what I've been doing, the data I had from the very original pre-screw-up time is still all there. Every time I try an update it hangs on the 1+ screen and stays there. How can I get past this? I can't seem to upgrade, and I'm stuck in lollipop.
Well I was still able to get into my phone and do a stock recovery from the Update and Restore option from the phones settings menu, so that fixed it.
Same thing as the OP of this thread: https://forum.xda-developers.com/moto-g4-plus/help/bootloop-to-twrp-ota-update-t3667456
Late last night I saw that there was an update available and, given that I've only rooted my phone, security updates are important, and it's a mere ~15 minutes download + install time tops I went for it.
I absolutely cannot seem to get the update to install via the OTA channel - it downloads just fine but when I attempt to install it it boots into TWRP and once there the only way to leave is via Bootloader > Start (System just reboots into TWRP) and upon reaching Android I'm told that the update was unsuccessful.
I now have two problems:
1. I don't like having notifications that I can't do anything about. Assuming that this OTA is going to nag me for eternity that's definitely going to become an annoyance - but I'd prefer the update vs blocking the notification (again, IF it nags)
2. Every time I restart my phone (or it crashes) I now have to deal with TWRP. It's not a major annoyance. It's at most 8 extra seconds added to my boot time and I don't restart my phone more than 3 times a week. But it IS butt-ache inducing.
Edit: Forgot to add that I came across this and downloaded it https://forum.xda-developers.com/moto-e4/how-to/boost-mobile-ota-t3763851 My E4 is a 1766 and is also from Boost Mobile (Sprint) so I imagine they're the same update. Point is, can I install this with TWRP successfully or would that do nothing / make things worse?
travistyse said:
Same thing as the OP of this thread: https://forum.xda-developers.com/moto-g4-plus/help/bootloop-to-twrp-ota-update-t3667456
Late last night I saw that there was an update available and, given that I've only rooted my phone, security updates are important, and it's a mere ~15 minutes download + install time tops I went for it.
I absolutely cannot seem to get the update to install via the OTA channel - it downloads just fine but when I attempt to install it it boots into TWRP and once there the only way to leave is via Bootloader > Start (System just reboots into TWRP) and upon reaching Android I'm told that the update was unsuccessful.
I now have two problems:
1. I don't like having notifications that I can't do anything about. Assuming that this OTA is going to nag me for eternity that's definitely going to become an annoyance - but I'd prefer the update vs blocking the notification (again, IF it nags)
2. Every time I restart my phone (or it crashes) I now have to deal with TWRP. It's not a major annoyance. It's at most 8 extra seconds added to my boot time and I don't restart my phone more than 3 times a week. But it IS butt-ache inducing.
Edit: Forgot to add that I came across this and downloaded it https://forum.xda-developers.com/moto-e4/how-to/boost-mobile-ota-t3763851 My E4 is a 1766 and is also from Boost Mobile (Sprint) so I imagine they're the same update. Point is, can I install this with TWRP successfully or would that do nothing / make things worse?
Click to expand...
Click to collapse
You cannot install it with twrp on a rooted device. You would have to modify the updater script in it for that. And remove a bunch of assert props. And hope your system isn't modified too much.
So no, you can't. You have to flash back to stock, (the version you're on now) then install it. Or just sit tight, there is someone working on a partition updater, and a twrp flashable rom with the update included.
Once you root and install twrp, ota updates ain't gonna happen. How do you not know this
If you need a solution for the recovery Loop issue you're going to have to give me a minute to find the link it can be fixed.
It's a problem if TWRP when you format data not wiping something properly
this should help a recovery loop. Only if your issue is, every reboot it goes right to twrp. Then you have to reboot bootloader and select start. Easy fix.
madbat99 said:
You cannot install it with twrp on a rooted device. You would have to modify the updater script in it for that. And remove a bunch of assert props. And hope your system isn't modified too much.
So no, you can't. You have to flash back to stock, (the version you're on now) then install it. Or just sit tight, there is someone working on a partition updater, and a twrp flashable rom with the update included.
Once you root and install twrp, ota updates ain't gonna happen. How do you not know this
If you need a solution for the recovery Loop issue you're going to have to give me a minute to find the link it can be fixed.
It's a problem if TWRP when you format data not wiping something properly
this should help a recovery loop. Only if your issue is, every reboot it goes right to twrp. Then you have to reboot bootloader and select start. Easy fix.
Click to expand...
Click to collapse
Thank you! And, frankly, because I never stick to stock. I always flash Cyanogenmod or LineageOS pretty much first thing when I get a phone. This time there wasn't a build available that seemed stable enough (Late November) but I still needed Root. I'm used to getting updates from both LOS and CM OTA so I figured the only thing preventing official OTA updates from working was that the build was entirely different. My assumption in this case was that I was still running the stock ROM that came with the device AND they were offering an OTA via notification so the phone must be eligible to receive it. >-> My bad.
travistyse said:
Thank you! And, frankly, because I never stick to stock. I always flash Cyanogenmod or LineageOS pretty much first thing when I get a phone. This time there wasn't a build available that seemed stable enough (Late November) but I still needed Root. I'm used to getting updates from both LOS and CM OTA so I figured the only thing preventing official OTA updates from working was that the build was entirely different. My assumption in this case was that I was still running the stock ROM that came with the device AND they were offering an OTA via notification so the phone must be eligible to receive it. >-> My bad.
Click to expand...
Click to collapse
The ota has a bunch of checks in it. If anything fails the checks, ota fails. When you root, there are system changes, boot.img changes, etc. All of which cause the ota to fail. Of course lineage and cm didn't have such strict checks in their update zips because they expect us to root and modify system. Manufacturers do not.
So tl;dr version - i was using my tablet, saw an update to magisk, installed it, now it boots to black screen while running sambones rom
[SM-P580] [BQK1] SaMBoNeS
TWRP 3.2.3.0 --> 3.3.1.0
longer story:
i was trying to get a game to run, it wasnt...and realized it has been a while for a restart, so i checked to see if anything needs to be updated and saw magisk needed an update. i didnt note what version it was before but it was a version or two earlier than what it was trying to install.
rebooted to blackscreen no samsung logo
have tried restarting a dozen times, booted to TWRP, tried to force normal system boot through the UI, nothing.
I tried installing a new kernal [SiriKernel], it made it to the samsung logo, waited 15 - 20 minutes and it never made it past. restored a backup using TWRP
updated TWRP to 3.3.1.0, still no luck.
i had this problem a long time ago, and cannot figure out how i fixed it....it may have fixed itself but it isnt this time. any advice would be appreciated. I am trying to avoid wiping and starting again if at all possible because the problem seems familiar. also trying to stick to a rom for use with adaptive storage. if i do have to wipe if that can be done on a newer stock OS that's fine as well but last time i messed with this tablet it wasnt
Sorry in advance for my English. As the name makes clear, my SMT280 doesn't turn on. The thing is, after I reflashed it and installed TWRP, I needed to do a full data reset. I went to TWRP, and apparently accidentally put a check mark on the system item. After that, the system stopped loading and the tablet freezes on the logo screen. Also, the PC stopped recognizing it, so I can't flash it through Odin. In an attempt to fix something, I took boot.img, and recovery.img from stock firmware and installed them via TWRP. Now, of course, I lost TWRP, and with IT the last hope, because now I only have a default recovery, and all the above problems remain. As I said, I don't think the tablet is still recoverable, but still, if anyone knows of any way, I would be extremely grateful. Thanks.