Related
I'd like to start by apologizing for what is probably the 9,000th "help, I've bricked my phone!" thread. I did some searching, and while I found many, I wasn't able to find one that both dealt with my specific issue, and did so assuming a level of newbishness appropriate for me.
Months ago, I rooted my AT&T Galaxy SIII, and installed CM10. It's been all candy and rainbows since. This morning, I somewhat foolishly decided to update from a nightly I installed in October/November, to the January 7 CM 10.1 nightly, using the built-in updater I had previously used to switch to a nightly.
It worked...sort of. I guess I should have cleared my cache or something ahead of time, because almost all of my GAPPS stopped working. Woops! Figuring that I should probably stop dicking around with my phone until I learned a bit more, I just went back and told the phone to switch back to the nightly I from October/November that I was previously using.
It didn't work. My phone now reaches the CM boot animation and just...sits there. And sits there. And sits there. To complicate the issue, I cannot get the phone to boot into recovery mode (although admittedly, I'm too thick to know what I'm meant to do once I'm there anyway). I CAN get the phone into download mode, but not being sure what I should do there, I thought it best to consult you all on what to do next.
I'm happy to give any additional information needed, and I hope it goes without saying that I am extremely thankful for any help you all can offer.
Try to get it back into recovery by taking the battery out, putting it back in and then holding volume up, home, and power. If you are sure you can't get it into Recovery, but know for sure you can get it into Download, go into Download and flash stock and go from there. These aren't bricks. These are just whoops. Lol.
If you can reach download mode, you'll be okay. What you want to do is use Odin to flash a rooted stock image; from there, you should be able to get back to a point where you can re-install a custom recovery of your choice and try flashing your favourite ROM again.
For the record, it's always a good idea to clear data/cache when changing ROMs, or changing between major revisions of a ROM (such as CM10 -> CM10.1) to avoid this sort of problem.
Actually, you should always wipe cache and dalvik when flashing the update. If it is a major update like 4.1.2 to 4.2.1, then you should wipe cache, wipe dalvik, Factory Reset, Format System then flash your ROM.
Move important files to SD using twrp file manager. Put rom on SD with gapps. Format internal, wipe caches, format system, factory reset, load ROM, load gapps. Reboot.
Sent from a Horny Pink Pony
smelenchuk said:
If you can reach download mode, you'll be okay. What you want to do is use Odin to flash a rooted stock image; from there, you should be able to get back to a point where you can re-install a custom recovery of your choice and try flashing your favourite ROM again.
For the record, it's always a good idea to clear data/cache when changing ROMs, or changing between major revisions of a ROM (such as CM10 -> CM10.1) to avoid this sort of problem.
Click to expand...
Click to collapse
I did this, being careful to follow all the instructions provided. Odin seemed to think everything worked, and after about 10 minutes, it rebooted the phone.
However, it still gets stuck. Now, since CM is no longer installed, it just sits at the SAMSUNG logo forever.
It still boots into download mode, and will now boot into recovery as well. Any suggestions?
naporeon said:
It still boots into download mode, and will now boot into recovery as well. Any suggestions?
Click to expand...
Click to collapse
Boot to recovery and clear data and cache.
smelenchuk said:
Boot to recovery and clear data and cache.
Click to expand...
Click to collapse
Worked like a charm, thanks! Can't believe after all that trouble, I didn't think to do that myself. >.<
So basically I did this:
http://forum.xda-developers.com/showthread.php?t=2538991
But unfortunately, I hadn't realized that the mobile hotspot was sealed up in that update. So I looked it up, and saw that someone had recommended this:
http://forum.xda-developers.com/showthread.php?p=48326067
So I went into TWRP and installed it. But that didn't work. When I booted back up EVERY app was crashing immediately except the stock Samsung apps (Messaging, Email, etc.). I tried to reverse it with the original framework-res.apk but when I did, the phone would get stuck at the AT&T logo (which was silent). I went back and forth a few times (when I applied that tethering mod, the phone would boot; when I tried to reverse it, it wouldn't), then did a factory reset in TWRP. After that, the phone booted, but the Setup Wizard would crash. So I did a Nandroid restore in TWRP and now the phone hangs at the AT&T logo no matter what I do.
My question is, what can I do now? I have a replacement device coming through warranty just in case, but it would be much better to just fix this one. However, I want to be certain and not HARD brick the phone...
I have never been able to restore a stock 4.3 nandroid without everything crashing. I have always had to go back into recovery and wipe data/factory reset and wipe cache and dalvik cache then reboot and go through the whole setup process again. If that doesn't work you could try installing the stock debloat ROM from this thread. That's what I am running and it works great. http://forum.xda-developers.com/showthread.php?t=2540998
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Iantuition said:
So basically I did this:
http://forum.xda-developers.com/showthread.php?t=2538991
But unfortunately, I hadn't realized that the mobile hotspot was sealed up in that update. So I looked it up, and saw that someone had recommended this:
http://forum.xda-developers.com/showthread.php?p=48326067
So I went into TWRP and installed it. But that didn't work. When I booted back up EVERY app was crashing immediately except the stock Samsung apps (Messaging, Email, etc.). I tried to reverse it with the original framework-res.apk but when I did, the phone would get stuck at the AT&T logo (which was silent). I went back and forth a few times (when I applied that tethering mod, the phone would boot; when I tried to reverse it, it wouldn't), then did a factory reset in TWRP. After that, the phone booted, but the Setup Wizard would crash. So I did a Nandroid restore in TWRP and now the phone hangs at the AT&T logo no matter what I do.
My question is, what can I do now? I have a replacement device coming through warranty just in case, but it would be much better to just fix this one. However, I want to be certain and not HARD brick the phone...
Click to expand...
Click to collapse
if you can get back to twrp , clear everything then flash the official correct file that yu want then see if that works...restore your apps/data after a clean refresh for your phone
remember panicking and being paranoid with flashing/rooting is not a a good idea, always rethink what you did wrong, let the phone cool down, research know what you re doing then fix it
dont rush, cuz rushing leads to bricks (learned from experience from day 1 with root)
bellifritz said:
I have never been able to restore a stock 4.3 nandroid without everything crashing. I have always had to go back into recovery and wipe data/factory reset and wipe cache and dalvik cache then reboot and go through the whole setup process again. If that doesn't work you could try installing the stock debloat ROM from this thread. That's what I am running and it works great. http://forum.xda-developers.com/showthread.php?t=2540998
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
How'd you do that? Just the regular factory reset? Cause the setup wizard wouldn't even run after that.
winosxbuntu said:
if you can get back to twrp , clear everything then flash the official correct file that yu want then see if that works...restore your apps/data after a clean refresh for your phone
remember panicking and being paranoid with flashing/rooting is not a a good idea, always rethink what you did wrong, let the phone cool down, research know what you re doing then fix it
dont rush, cuz rushing leads to bricks (learned from experience from day 1 with root)
Click to expand...
Click to collapse
Okay. Which official file though? and should I clear the system and boot partitions too?
Iantuition said:
How'd you do that? Just the regular factory reset? Cause the setup wizard wouldn't even run after that.
Okay. Which official file though? and should I clear the system and boot partitions too?
Click to expand...
Click to collapse
try this two links, everything on flashing 4.3 stock/rooting and fix http://forum.xda-developers.com/showthread.php?t=2540998
http://forum.xda-developers.com/showpost.php?p=46804338
either one will work
AND dont clear everything just cache/dalvik/format system/ factory reset BUT follow the instructions given for that rom to avoid any problems
winosxbuntu said:
try this two links, everything on flashing 4.3 stock/rooting and fix http://forum.xda-developers.com/showthread.php?t=2540998
http://forum.xda-developers.com/showpost.php?p=46804338
either one will work
AND dont clear everything just cache/dalvik/format system/ factory reset BUT follow the instructions given for that rom to avoid any problems
Click to expand...
Click to collapse
Okay so I just leave boot alone. Let us pray, LOL. And sorry if I've sounded like a supernoob but I'm trying to be REALLY careful.
Iantuition said:
How'd you do that? Just the regular factory reset? Cause the setup wizard wouldn't even run after that.
Hit the power button to make the screen go to sleep. Hit the power button again to wake it up. Nothing should be crashing while you are on the lock screen so just hold the power button until the power menu appears and select power off. Once it powers off hold the volume up, home button and power button until you see the blue words in the upper left corner of the screen I believe it says loading recovery. Release the power button but continue holding the other 2 buttons until recovery loads. Now wipe data, cache and under advanced wipe dalvik cache. Reboot and everything should quit crashing but you will have to setup your account and apps again. That is the only way that I can get stock touchwiz 4.3 nandroids to work.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Iantuition said:
Okay so I just leave boot alone. Let us pray, LOL. And sorry if I've sounded like a supernoob but I'm trying to be REALLY careful.
Click to expand...
Click to collapse
it will work, i agree with what bell said. unless its hard bricked then no worries just keep calm and fix the damn phone
I have followed the instructions from Max at galaxynote4root http://galaxynote4root.com/galaxy-note-4-root/how-to-root-unlock-bootloader-on-galaxy-note-4/5/. I got all the way through to the final step which is go into TWRP recovery, install the Oscar kernel and SuperSU zip files. I did not extract these files. Once I did that I got into a boot loop. I get by the Verizon logo to the UI and then it starts rebooting. Since there is not much discussion activity at Max's site, I thought if anyone here could help me.
After the UI comes up and before it goes in the boot loop, I get messages saying "Unfortunately xxxx has stopped." It varies about sometimes it is Knox. S Pen, Google Play, etc.
Try a factory reset by going into recovery and wiping delvik, cache, and data
MonstaSaleens said:
Try a factory reset by going into recovery and wiping delvik, cache, and data
Click to expand...
Click to collapse
That improved the situation. It is no longer in a constant boot loop, but it will still reboot when I manually start it or reboot it. When it starts it says "unfortunately KNOX has stopped running." It was doing that before, too.
I have confirmed I have root and and unlocked bootloader.
Redownload the rom.
Wipe data, cache, dalvic cache and system.
Install rom
Then kernel
And supersu.
Reboot and you should be fine
---------- Post added at 06:32 AM ---------- Previous post was at 06:30 AM ----------
If it continues I'd get a Odin flushable and use the pit file for repatriationing of the system. Maybe something went wrong..... Idk
Just a quick question: Did you use a micro SD card as part of the process? Did you remove this card after you were done unlocking the bootloader?
I know the process has you reformat the card, but I am asking if you have tried booting with the card removed.
codydixon said:
Redownload the rom.
Wipe data, cache, dalvic cache and system.
Install rom
Then kernel
And supersu.
Reboot and you should be fine
---------- Post added at 06:32 AM ---------- Previous post was at 06:30 AM ----------
If it continues I'd get a Odin flushable and use the pit file for repatriationing of the system. Maybe something went wrong..... Idk
Click to expand...
Click to collapse
Just followed your instructions. Everything was fine until I installed the kernel and supersu. I hate to be stuck when I'm so close.
ssj4gogeta2003 said:
Just a quick question: Did you use a micro SD card as part of the process? Did you remove this card after you were done unlocking the bootloader?
I know the process has you reformat the card, but I am asking if you have tried booting with the card removed.[/QUOTE
OK, tried that, and it worked--once. When I reboot with the SD card out, it either won't start or goes back into a boot loop.
Click to expand...
Click to collapse
Although it didn't seem very warm to me, I pulled the battery and let it sit for an hour. When I started it back up, everything was fine.
However, how do I re-enable the use of the SD card. I am afraid if I put in back in, I'll go back into the boot loop?
MrNetwork said:
Although it didn't seem very warm to me, I pulled the battery and let it sit for an hour. When I started it back up, everything was fine.
However, how do I re-enable the use of the SD card. I am afraid if I put in back in, I'll go back into the boot loop?
Click to expand...
Click to collapse
You'll need to connect the micro sd card itself to the computer and format it there. I have used Rufus (https://rufus.akeo.ie/) in the past to do this, but you may use any formatting program that you are familiar with. I recommend FAT32 as your format unless you move files over 4 GB to and from the card.
Thanks. I've rebooted it a couple of times after doing this, and it still is working! Now, should I install a 6.0 ROM or leave well enough alone?
MrNetwork said:
Thanks. I've rebooted it a couple of times after doing this, and it still is working! Now, should I install a 6.0 ROM or leave well enough alone?
Click to expand...
Click to collapse
It will depend on what version of firmware you are currently running. Most 6.0 ROMs require that you are using N910VVRU2CPD1 or N910VVRU2CPF3 for proper use. Please go into About Phone in Settings and check the Baseband Version field to make sure that you have one of those two in there. Flashing a 6.0 ROM with 5.1.1 firmware will cause issues with mobile signal and can make it impossible to use wifi.
If you find that you are running 5.1.1 firmware, then you have two choices: Flash a 5.1.1 ROM and call it a day or go through the process of unlocking the bootloader for 6.0.1 firmware. It's important to note that this will be a different process than the one you just went through. Be sure to research it thoroughly before attempting it. Hsbadr is a great developer and I believe he has a process for that, but it's been a while since I did it myself.
Back in a boot loop again. Once I've loaded the system image, I can reboot several times and everything is stable. As soon as I obtain root by installing the Oscar kernel and BetaSU, the phone becomes unstable. It might boot properly at first, but I still get "XXX has failed to start" where XXX can be any of a number of apps. If I let that go on without first shutting it down, it will go into a boot loop. However, if I do shut it down and restart it will also eventually go into a boot loop. Obviously this phone can't be my daily driver until I get it stable.
Before I install the rom each time, I wipe data, cache, dalvic cache and system.
I wonder if the kernel is the issue?
MrNetwork said:
Back in a boot loop again. Once I've loaded the system image, I can reboot several times and everything is stable. As soon as I obtain root by installing the Oscar kernel and BetaSU, the phone becomes unstable. It might boot properly at first, but I still get "XXX has failed to start" where XXX can be any of a number of apps. If I let that go on without first shutting it down, it will go into a boot loop. However, if I do shut it down and restart it will also eventually go into a boot loop. Obviously this phone can't be my daily driver until I get it stable.
Before I install the rom each time, I wipe data, cache, dalvic cache and system.
I wonder if the kernel is the issue?
Click to expand...
Click to collapse
I need more information to help you out. Please answer the following:
What baseband is your phone at right now? (Refer to my post above for where to find it.)
What ROM have you installed? (Be sure to include Android version as well as name)
Oscar Kernel is specifically for use with 6.0.1 Touchwiz ROMs. If you aren't on 6.0.1 and you haven't installed a Touchwiz-based ROM, then there will be issues.
ssj4gogeta2003 said:
I need more information to help you out. Please answer the following:
What baseband is your phone at right now? (Refer to my post above for where to find it.)
What ROM have you installed? (Be sure to include Android version as well as name)
Oscar Kernel is specifically for use with 6.0.1 Touchwiz ROMs. If you aren't on 6.0.1 and you haven't installed a Touchwiz-based ROM, then there will be issues.
Click to expand...
Click to collapse
Thank you. I finally figured it out. The problem was with oscar_kernel_v0.2. Instead I am using Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P. I'm going to stay with 5.1.1. The only trouble I am having now is with My Tracks not showing the map. I know it's been deprecated by Google, but it still is working on my LG G4. However, I'm not trying to hijack this thread. I'll start a new thread for this issue.
This is now the fastest phone I've used after deleting bloatware and running Nova Launcher.
Good to hear. Enjoy the phone.
I'm writing because I found no solution to this or someone to address this. are there not many having this problem?
After 7.0 update my alarm is not ringing and if I go in the settings to change the alarm sound the app fc, also the YouTube app says "something went wrong" when trying to play a video.
After restart the sound is back for some time, then bug repeats.
I activated touch sound so I get a warning when I need to reboot, but the touch sound is not affected, also the music app is working, but no alarm or notification.
Whipped cash, installed Oos 4.0.3 via recovery (stock, locked bl, no root)
Currently on 7.1.1 Oos 4.1.3
Someone please help
Starting to think that I will have to sent the phone back to OnePlus...
get the full 4.1.3 zip, and on stock recovery wipe everything not just cache...
then back to the main menu on recovery and select install via USB (or something liket hat) and sideload the full rom from computer , after sideload boot to system and for good measures do a factory reset.
theduke7 said:
get the full 4.1.3 zip, and on stock recovery wipe everything not just cache...
then back to the main menu on recovery and select install via USB (or something liket hat) and sideload the full rom from computer , after sideload boot to system and for good measures do a factory reset.
Click to expand...
Click to collapse
Thanks for the reply ! - I will try your suggestion tomorrow if I get the time -
Maybe it's a stupid question but: is there ever a need to wipe internal storage? or wipe everything means just system data ?
plus: could the encryption mess things around ?
marius88cc said:
Thanks for the reply ! - I will try your suggestion tomorrow if I get the time -
Maybe it's a stupid question but: is there ever a need to wipe internal storage? or wipe everything means just system data ?
plus: could the encryption mess things around ?
Click to expand...
Click to collapse
Encryption may cause issues, but I don't think your problem is related to that, something in the update process went wrong I think so you got something corrupted on the either the system.or data partition , so Everytime you install a new ROM it does but the issue stays, the only way to know for sure is a clean install, and the easiest way to that is what I told you, it can also be done by fastboot where you wipe everything with fastboot then sideload , but to be safe better stick with the recovery method... I don't thing internal storage could cause an issue, but I personally from 7.0 to 7.1.1 I did wipe it , better safe than sorry, and it elemenates any possibilities so if you can do that it's better
theduke7 said:
Encryption may cause issues, but I don't think your problem is related to that, something in the update process went wrong I think so you got something corrupted on the either the system.or data partition , so Everytime you install a new ROM it does but the issue stays, the only way to know for sure is a clean install, and the easiest way to that is what I told you, it can also be done by fastboot where you wipe everything with fastboot then sideload , but to be safe better stick with the recovery method... I don't thing internal storage could cause an issue, but I personally from 7.0 to 7.1.1 I did wipe it , better safe than sorry, and it elemenates any possibilities so if you can do that it's better
Click to expand...
Click to collapse
Thank you for the reply!
Weirdest thing, I did not get the chance to reinstall the system yet, but since I posted this the bug did not reaper. I suspect an app was misbehaving and it got updated...I will wait and see.
Just sideloaded, will report how it goes if anyone faces the same problem
New OTA Out, should solve this, it seems
I purchased my Pixel 2 XL from the Google store. I had just upgraded to the 8.1 OTA a few days before when i came across this video and used it to root my phone:
https://youtu.be/nFD9sa-WdUM
Here's the basic steps i took:
Unlock dev options and turn on OEM Unlocking
Boot to stock recovery
Go to his highonandroid site and download TWRP 3.1.1 beta2 (img and zip), an outdated fastboot.zip, magisk 14.5, and the USB drivers which i didnt download because my computer is already recognizing my device just fine.
Extract the fastboot files to a new folder and copy the twrp img file to the fastboot folder.
In CMD, unlock the bootloader with fastboot and reboot phone.
Connect phone as storage device, copy over twrp zip file and magisk 14.5 zip files to root folder on the phone, reboot into recovery
Use fastboot to boot the twrp image that we copied to fastboot folder to get into twrp
Unhook the USB cable, set TWRP to read only, install TWRP, hit home button, then install Magisk and reboot
Once booted up, get into Magisk, download proprietary software, run checks and done.
Once this was done, my fingerprint scanner and wifi no longer worked. I could turn wifi on but it would never find anything. I also received the error when rebooting the phone that says "There's an internal problem with your device. Contact your manufacturer for details." When this message is on the screen, if i dont touch the phone and the screen times out, it flickers really bad and never actually shuts off until i unlock it and hit the OK button.
So i decided to give it another go and ran into some big issues. I figured that i used 8.0 instructions on 8.1 and there was enough things different that it caused problems, so i used this link to reroot:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
I went through the first 10-15 pages and the last 10-15 pages and did some searches on the thread and never found any of my issues, but found that a lot of people used different sets of steps and pretty much everything was successful as long as you didnt miss anything and used the most updated stuff. So i did, i went to googles website and downloaded the newest SDK with fastboot, adb, and all that good stuff, as well as the newest 8.1 image (there was a newer version but it had a carrier label on it so i didnt get that one), and the newest magisk and twrp.
I flashed 8.1 and the phone wouldnt boot, nor would it get into TWRP anymore, so i had to use fastboot to boot the twrp image and reinstall the recovery and magisk but it still wouldnt boot. I ran through several different steps and eventually got it to boot up with recovery working. Its the newest 8.1 image, the newest magisk, and the newest twrp, and since then magisk has updated a couple times.
Now on to my issues!
I still get the "Internal problem" popup when booting
I get a lot more random reboots
Sometimes random things just wont work, like streaming plex to my tv or loading an app or something on an app and i have to reboot and it works fine
I've seen numerous times that the "Internal problem" thing is just a mismatch between the system and vendor build.prop files. I dont know what exactly is mismatching between the two but i've tried reflashing them and all sorts of things and nothing ever fixes it.
Does anyone know if there's a fix to any of these three issues, or if maybe looking at my steps i clearly did something wrong? I'm willing to do the whole thing over again if there's a good suggestion, but once i flashed the 8.1 image and went that route, i rerooted successfully 4 times total before i quit doing it again just because of that internal problem popup, i kept figuring something went wrong or i did something wrong. I had no security or anything set before rooting or flashing or anything, and each time i reflashed the operating system, but when i flashed the OS, i had to extract the system file because i would constantly get an error that it was too big and it failed to truncate it, so i've always had to manually install it by first copying it to my phone and installing it through TWRP. Its been an adventure, but these problems suck!
PMad said:
...Its been an adventure, but these problems suck!
Click to expand...
Click to collapse
It's called training. For the error, you just need to fastboot flash the stock dtbo.img. This was fixed on the 15.1 version of Magisk so you shouldn't have that problem anymore. I can tell you that rooted, kernel and a few root apps and I have never had ANY random reboots, so one of your apps is causing it or you didn't start from a completely blank slate. Run your phone in Safe Mode for a while to see if you stop the reboots 100%. If so, one of your apps is the cause. If you still get reboots in Safe Mode, you're gonna need to re-install. I suggest using the instructions on the Google web page where you got the full image. (and try to distill your posts down a little, ffs)
v12xke said:
It's called training.
Click to expand...
Click to collapse
Every new phone is a new adventure, they are all the same but unique at the same time!
v12xke said:
For the error, you just need to fastboot flash the stock dtbo.img.
Click to expand...
Click to collapse
I'll give this a shot! Thank you!
v12xke said:
This was fixed on the 15.1 version of Magisk so you shouldn't have that problem anymore.
Click to expand...
Click to collapse
15.1 is the version i'm on now but nothing has changed. Which issue was this supposed to fix?
v12xke said:
I can tell you that rooted, kernel and a few root apps and I have never had ANY random reboots, so one of your apps is causing it or you didn't start from a completely blank slate.
Click to expand...
Click to collapse
My concern here is that my settings and apps are literally exactly the same as before root, except for magisk, its my only new app, which would lead me to believe that something Magisk is changing is causing the problem, or something else is happening that i'm not realizing yet.
v12xke said:
Run your phone in Safe Mode for a while to see if you stop the reboots 100%. If so, one of your apps is the cause. If you still get reboots in Safe Mode, you're gonna need to re-install. I suggest using the instructions on the Google web page where you got the full image.
Click to expand...
Click to collapse
The reboots are typically 1 reboot every 1 to 3 days, so its not a terrible issue but its happening and it shouldnt. For flashing the OS, after the first failure when trying to install it, those are the only instructions i've used, but i get that error when trying to install the OS that says something about how it failed to truncate the system.img file and so it wasnt installed, so my work around was to copy the file to the phones root folder, install the 8.1 image then immediately go and manually install the system.img file in twrp since its the only thing that fails, but i still have issues. What is this truncate issue?
v12xke said:
(and try to distill your posts down a little, ffs)
Click to expand...
Click to collapse
I agree! hahaha i just wanted to be clear and include all the details, otherwise everyone would have asked me question after question that i could have just included. It ends up being long, a lot happened!
I'll give that dtbo.img a shot and see what that clears up, then if there's issues with rebooting still i'll try safe mode for a few days and see what that does.
Thank you v12xke! (how do you pronounce that? haha)
PMad said:
...I'll give that dtbo.img a shot and see what that clears up, then if there's issues with rebooting still i'll try safe mode for a few days and see what that does.
Thank you v12xke! (how do you pronounce that? haha)
Click to expand...
Click to collapse
Your dtbo.img got patched by Magisk somewhere along the line and that is why the OS is throwing the error. Extract that img file from the full Google image and fastboot flash it, and the error will go away. There is a long thread around HERE on random reboots you should read. The v12xke is a car (Jaguar E-Type) I once owned.
v12xke said:
Your dtbo.img got patched by Magisk somewhere along the line and that is why the OS is throwing the error. Extract that img file from the full Google image and fastboot flash it, and the error will go away. There is a long thread around HERE on random reboots you should read. The v12xke is a car (Jaguar E-Type) I once owned.
Click to expand...
Click to collapse
So i just tried to do this and ran into one of the issues i had when originally trying to root it... I get into TWRP and it will not take any button presses, like the touch screen has become a screen (minus the touch). Is there a fix for this or do i just need to install TWRP before i use it each time it does this?
PMad said:
So i just tried to do this and ran into one of the issues i had when originally trying to root it... I get into TWRP and it will not take any button presses, like the touch screen has become a screen (minus the touch). Is there a fix for this or do i just need to install TWRP before i use it each time it does this?
Click to expand...
Click to collapse
1. You don't use TWRP to flash dtbo.img, you fastboot it while the phone is in bootloader mode.
2. TWRP works just fine if you install it and leave it installed. Make sure you are using 3.2.1-0 (img and zip).
v12xke said:
1. You don't use TWRP to flash dtbo.img, you fastboot it while the phone is in bootloader mode.
2. TWRP works just fine if you install it and leave it installed. Make sure you are using 3.2.1-0 (img and zip).
Click to expand...
Click to collapse
I was getting into TWRP to create a backup of everything and it popped up asking for my password, and i remembered reading that we have to get rid of all of our security before making a backup, so i tried to hit buttons to cancel it and nothing worked, i had to hold the power button. So i eliminated all of my security and went back thinking it was a 1 time issue but it happened again, it took me straight to the main menu but nothing would work. I'm using 3.2.1-0 like you mentioned and i cant press any buttons. I'd like to back everything up before flashing this or anything else.
PMad said:
I was getting into TWRP to create a backup of everything and it popped up asking for my password, and i remembered reading that we have to get rid of all of our security before making a backup, so i tried to hit buttons to cancel it and nothing worked, i had to hold the power button. So i eliminated all of my security and went back thinking it was a 1 time issue but it happened again, it took me straight to the main menu but nothing would work. I'm using 3.2.1-0 like you mentioned and i cant press any buttons. I'd like to back everything up before flashing this or anything else.
Click to expand...
Click to collapse
You don't need a backup before re-flashing the STOCK dtbo (or boot) partitions, haha. READ UP.