I am unable to make any ROM, TWRP stick. - Google Pixel XL Questions & Answers

I have FB factory, flashed ROM's and nothing is sticking. Might be corrupt storage. I was wondering if there is a more thorough way to wipe/flash the phone so I can make a ROM/OS stick?

Have you tried a factory image with the -w as in wipe everything?
Sent from my Pixel XL using Tapatalk

Soooperstar said:
Have you tried a factory image with the -w as in wipe everything?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Yes, I have done all of the typical things and I am having very, very bad luck. Out of the box, thinking is critical.

Fixed!

Scottay5150 said:
I have FB factory, flashed ROM's and nothing is sticking. Might be corrupt storage. I was wondering if there is a more thorough way to wipe/flash the phone so I can make a ROM/OS stick?
Click to expand...
Click to collapse
Fastboot format system, fastboot erase userdata, fastboot format cache. There was a guide somewhere someone had about clean flashing. I had an issue once but after totally wiping and a clean install of stock, I haven't had any issues since. Use the flash-all.exe to flash, idk if you flash your images separately, but flashing the zip as a whole through fastboot yielded better results for me. Also being sure that my adb.exe files were up to par. Also be sure to wipe both slots, as it might be slot b giving you problems. Google search should find you the right fastboot commands, I've forgot them off the top of my head. Of course if you're going to wipe you would need to back everything you need up.

Bryanx86 said:
Fastboot format system, fastboot erase userdata, fastboot format cache. There was a guide somewhere someone had about clean flashing. I had an issue once but after totally wiping and a clean install of stock, I haven't had any issues since. Use the flash-all.exe to flash, idk if you flash your images separately, but flashing the zip as a whole through fastboot yielded better results for me. Also being sure that my adb.exe files were up to par. Also be sure to wipe both slots, as it might be slot b giving you problems. Google search should find you the right fastboot commands, I've forgot them off the top of my head. Of course if you're going to wipe you would need to back everything you need up.
Click to expand...
Click to collapse
Yes, my SDK is up to date, from Google site. Interesting about flash-all.exe.
Fastboot format system
fastboot erase userdata
fastboot format cache
These were the commands you have used?
Anyone have beta how to wipe both a and b??
Does anyone want to link me to clean flashing?

Scottay5150 said:
Yes, my SDK is up to date, from Google site. Interesting about flash-all.exe.
Fastboot format system
fastboot erase userdata
fastboot format cache
These were the commands you have used?
Anyone have beta how to wipe both a and b??
Does anyone want to link me to clean flashing?
Click to expand...
Click to collapse
You need to go back to square one.. Asking questions like this lead me to believe you have absolutely no idea what you are doing and you need to leave things alone before further damaging your device...

stebomurkn420 said:
You need to go back to square one.. Asking questions like this lead me to believe you have absolutely no idea what you are doing and you need to leave things alone before further damaging your device...
Click to expand...
Click to collapse
OK folks. I want to apologize for my flooding of the forums attempting to repair my situation last week. Yes, I have been flashing for a long time without real complications. I haven't been on my ADHD meds for a while and that did not help me with the drama last week. Unfortunately my world like most of you is in my phone, I was panicked. Sorry about that.
Needless to say I needed other eyes on what I was doing for perspective sake. I went to my PC tech, luckily had personal flashing experiences with Android, Pixel even. We worked on it for about 6 hours in total. He couldn't get RR to work.
The issue was this after following the OP instructions. Once in the system I couldn't get the WiFi to connect with the phone, not being able to download whatever the phone was looking for. Google play services kept FC'ing. Google TTS kept FC'ing as well. I don't know if there is a fix or a forthcoming fix for this abnormal issue. I deleted data from the apps that were FC'ing and other Google that might be related. PS: not a RR issue I had this same issue with Benzo)
Unfortunately, we didn't save anything from the old RR setup because I couldn't be without a phone for another day. Any constructive thoughts would be welcomed.
I shall attempt to reinstall RR at some point to see if it works, or to get data to help the devs understand what might have happened or might had happened.
I am back on stock, not loving it that is for sure.

Scottay5150 said:
OK folks. I want to apologize for my flooding of the forums attempting to repair my situation last week. Yes, I have been flashing for a long time without real complications. I haven't been on my ADHD meds for a while and that did not help me with the drama last week. Unfortunately my world like most of you is in my phone, I was panicked. Sorry about that.
Needless to say I needed other eyes on what I was doing for perspective sake. I went to my PC tech, luckily had personal flashing experiences with Android, Pixel even. We worked on it for about 6 hours in total. He couldn't get RR to work.
The issue was this after following the OP instructions. Once in the system I couldn't get the WiFi to connect with the phone, not being able to download whatever the phone was looking for. Google play services kept FC'ing. Google TTS kept FC'ing as well. I don't know if there is a fix or a forthcoming fix for this abnormal issue. I deleted data from the apps that were FC'ing and other Google that might be related. PS: not a RR issue I had this same issue with Benzo)
Unfortunately, we didn't save anything from the old RR setup because I couldn't be without a phone for another day. Any constructive thoughts would be welcomed.
I shall attempt to reinstall RR at some point to see if it works, or to get data to help the devs understand what might have happened or might had happened.
I am back on stock, not loving it that is for sure.
Click to expand...
Click to collapse
Sounds to me like you used the wrong GApps. Or maybe used the wrong TWRP, or tried installing TWRP when you should have just booted it. Something like that.

borxnx said:
Sounds to me like you used the wrong GApps. Or maybe used the wrong TWRP, or tried installing TWRP when you should have just booted it. Something like that.
Click to expand...
Click to collapse
I wish I could say the wrong GAPPS, the version from the OP was used (others had issues as well), TWRP 3.2.0 again from the OP was installed per instructions. They were not. Not letting system boot up might have been the bigger issue. I shall never know.

Related

20gb System storage alotment and unable to flash anything

Hello all! I've got a puzzling issue (for me, at least) that I'd like to see if anyone else has encountered and what their possible fix might be.
So I've been alternating between running Resurrection Remix and Pure Nexus the past few months and have had no issues flashing new builds or kernels. Last night when I went to switch back from RR to Pure Nexus I encountered and error I haven't seen before and some weird results from it.
When I went to flash the Pure Nexus it kept failing stating TWRP was unable to find the meta/inf/com/Google (I think) data in the zip. I tried flashing RR again with the same issue. I then tried to wipe and restore a TWRP backup that didn't end up working even though it said it did. I then decided screw it and flashed the factory image for the Pixel XL and was able to at least get booted and running on stock. However, my storage is pretty much gone and now only have like 6gb out of 8gb total. Upon I spection System is currently taking up 20gb worth of storage and even after flashing the factory image again it is still not resolved.
Can anyone tell me what I managed to do here and if there is a fix? Realistically I'd love to figure out how to actually repartition everything in the phone and start from scratch again.
Any advice or insight would be greatly appreciated as I'm not new to rooting and rom'ing but am getting uinely confused as to what has happened here.
PS: I attached a picture of my storage breakdown but can't inspect further due to not having root and being on stock. Viewing storage in TWRP didn't yield much more I formation either.
MR H3LLMAN said:
Hello all! I've got a puzzling issue (for me, at least) that I'd like to see if anyone else has encountered and what their possible fix might be.
So I've been alternating between running Resurrection Remix and Pure Nexus the past few months and have had no issues flashing new builds or kernels. Last night when I went to switch back from RR to Pure Nexus I encountered and error I haven't seen before and some weird results from it.
When I went to flash the Pure Nexus it kept failing stating TWRP was unable to find the meta/inf/com/Google (I think) data in the zip. I tried flashing RR again with the same issue. I then tried to wipe and restore a TWRP backup that didn't end up working even though it said it did. I then decided screw it and flashed the factory image for the Pixel XL and was able to at least get booted and running on stock. However, my storage is pretty much gone and now only have like 6gb out of 8gb total. Upon I spection System is currently taking up 20gb worth of storage and even after flashing the factory image again it is still not resolved.
Can anyone tell me what I managed to do here and if there is a fix? Realistically I'd love to figure out how to actually repartition everything in the phone and start from scratch again.
Any advice or insight would be greatly appreciated as I'm not new to rooting and rom'ing but am getting uinely confused as to what has happened here.
PS: I attached a picture of my storage breakdown but can't inspect further due to not having root and being on stock. Viewing storage in TWRP didn't yield much more I formation either.
Click to expand...
Click to collapse
Format userdata should fix it.
toknitup420 said:
Format userdata should fix it.
Click to expand...
Click to collapse
I believe I tried that at one point last night but will try it again here shortly. Any thoughts on what it could be if this does not fix it? And what method would you recommend to format userdata? Do I do it through TWRP?
fastboot format userdata
swapavi said:
fastboot format userdata
Click to expand...
Click to collapse
So this did indeed fix my storage partition issues but now I am unable to flash TWRP to my device. It is stating my recovery partition doesn't exist. What the hell is happening? haha
MR H3LLMAN said:
So this did indeed fix my storage partition issues but now I am unable to flash TWRP to my device. It is stating my recovery partition doesn't exist. What the hell is happening? haha
Click to expand...
Click to collapse
You may need to fast boot new boot images to slot a and b. You just have to unzip factory image and you will see them in there. Or just flash the factory image all over. Start fresh.
MR H3LLMAN said:
So this did indeed fix my storage partition issues but now I am unable to flash TWRP to my device. It is stating my recovery partition doesn't exist. What the hell is happening? haha
Click to expand...
Click to collapse
Don't flash recovery, you're pixel will get all screwed up lol. You temp boot it and install via the twrp installer zip.

Use TWRP to flash 8.1 update

I feel like I should know how to do this and I just can't think right now...
I have 8.0 and the latest TWRP installed. Root with Magisk as well. I want to update to 8.1 but I don't want to have to factory reset the phone by flashing 8.1 to it and then reflashing root & TWRP. There's a way to do this that I'm not thinking of, right?
I read another post about using FlashFire but regardless of where I put the factory image, the app doesn't see it. So I feel like I'm at a loss right now.
Am I missing something? Thanks in advance!
WyldOne91 said:
I feel like I should know how to do this and I just can't think right now...
I have 8.0 and the latest TWRP installed. Root with Magisk as well. I want to update to 8.1 but I don't want to have to factory reset the phone by flashing 8.1 to it and then reflashing root & TWRP. There's a way to do this that I'm not thinking of, right?
I read another post about using FlashFire but regardless of where I put the factory image, the app doesn't see it. So I feel like I'm at a loss right now.
Am I missing something? Thanks in advance!
Click to expand...
Click to collapse
This is how I upgraded to 8.1, my setup before I upgraded was the same as yours.
1. Bootloader and unlock_critical both unlocked?
2. Download and extract the factory image, and place all contents in your SDK platform tools folder.
3. Edit the flash-all.bat file and remove the -w in the last line of code. (This prevents your data from being wiped)
4. Double click the flash-all.bat file to start the process. It'll take a little while, so be patient.
5. Once it's done, get back to bootloader mode.
6. Flash the twrp.img file. This will take you to temporary twrp.
7. Once in twrp, flash the twrp.zip, then flash custom kernel.zip(optional) then flash your magisk.zip.
8. Reboot and done.
Couple of caveats, make sure your using a good USB transfer cable, and it's recommended to remove your finger print and/or password/pin, and uninstall any themes you have installed. Hope all goes well for you :good:
Badger50 said:
This is how I upgraded to 8.1, my setup before I upgraded was the same as yours.
1. Bootloader and unlock_critical both unlocked?
2. Download and extract the factory image, and place all contents in your SDK platform tools folder.
3. Edit the flash-all.bat file and remove the -w in the last line of code. (This prevents your data from being wiped)
4. Double click the flash-all.bat file to start the process. It'll take a little while, so be patient.
5. Once it's done, get back to bootloader mode.
6. Flash the twrp.img file. This will take you to temporary twrp.
7. Once in twrp, flash the twrp.zip, then flash custom kernel.zip(optional) then flash your magisk.zip.
8. Reboot and done.
Couple of caveats, make sure your using a good USB transfer cable, and it's recommended to remove your finger print and/or password/pin, and uninstall any themes you have installed. Hope all goes well for you :good:
Click to expand...
Click to collapse
Cool thank you I will give this a shot later tonight! One question, what is "unlock_critical?" I haven't seen that mentioned anywhere else before.
WyldOne91 said:
Cool thank you I will give this a shot later tonight! One question, what is "unlock_critical?" I haven't seen that mentioned anywhere else before.
Click to expand...
Click to collapse
The pic is from the Google factory image page. Unlock_critical must be performed on the P2XL to allow the bootloader to be updated with future monthly security or software updates. This does not apply to the standard P2. Be advised, this WILL wipe your phone. However, you really don't have much choice if you want to flash monthly factory images.
Badger50 said:
The pic is from the Google factory image page. Unlock_critical must be performed on the P2XL to allow the bootloader to be updated with future monthly security or software updates. This does not apply to the standard P2. Be advised, this WILL wipe your phone. However, you really don't have much choice if you want to flash monthly factory images.
Click to expand...
Click to collapse
Oh crap... I only ran the OEM unlock. Welp, looks like I'm going to end up wiping anyways. Thanks for the info though. This is definitely one of those situations where I assumed I knew what I was doing and ran with it without actually reading the process.
WyldOne91 said:
Oh crap... I only ran the OEM unlock. Welp, looks like I'm going to end up wiping anyways. Thanks for the info though. This is definitely one of those situations where I assumed I knew what I was doing and ran with it without actually reading the process.
Click to expand...
Click to collapse
No problem my friend. There's a lot to learn on these new pixel devices. There are plenty threads on these forum with tons of info on whatever topic you may have questions about. Just takes time, patience, lots of reading, and a willingness to learn :good:
WyldOne91 said:
Oh crap... I only ran the OEM unlock. Welp, looks like I'm going to end up wiping anyways. Thanks for the info though. This is definitely one of those situations where I assumed I knew what I was doing and ran with it without actually reading the process.
Click to expand...
Click to collapse
Since you are rooted, and already have the mindset that all is or will be lost you have the opportunity to try a couple options that if fail nothing lost...
After doing away with screen security and any themes, do Full backup in TWRP and also use TiBu to back up all your apps and then move them off the phone until after you do your thing.
After you do the critical unlock and get 8.1 installed and rooted you could try restoring the TWRP data partition and see what happens. Worst case it's either not booting or just acting funky. Do a factory wipe and not much lost.
Or... Use TiBu to save some time restoring all your apps. While I have had pretty good luck with restoring data on most apps, a few either won't restore or are boned in some way. Some other folks had a really hard time with restoring data so maybe just restore the apps without data. I run over 100 apps and have been through some version of this many times while playing around. With my crappy internet out here in the boonies it took 4 hours for google to restore all my apps and that's with hardly no data. It took about 20 minutes to restore most everything through TiBu. I would not restore data in the big initial bulk restore but instead go back and cherry pick the data restore on the things you need.
Again worst case all lost but you assumed that anyway and maybe you can save some time and effort if either option works.
Badger50 said:
No problem my friend. There's a lot to learn on these new pixel devices. There are plenty threads on these forum with tons of info on whatever topic you may have questions about. Just takes time, patience, lots of reading, and a willingness to learn :good:
Click to expand...
Click to collapse
Yeah for sure. I'm always willing to learn!
CyberpodS2 said:
Since you are rooted, and already have the mindset that all is or will be lost you have the opportunity to try a couple options that if fail nothing lost...
After doing away with screen security and any themes, do Full backup in TWRP and also use TiBu to back up all your apps and then move them off the phone until after you do your thing.
After you do the critical unlock and get 8.1 installed and rooted you could try restoring the TWRP data partition and see what happens. Worst case it's either not booting or just acting funky. Do a factory wipe and not much lost.
Or... Use TiBu to save some time restoring all your apps. While I have had pretty good luck with restoring data on most apps, a few either won't restore or are boned in some way. Some other folks had a really hard time with restoring data so maybe just restore the apps without data. I run over 100 apps and have been through some version of this many times while playing around. With my crappy internet out here in the boonies it took 4 hours for google to restore all my apps and that's with hardly no data. It took about 20 minutes to restore most everything through TiBu. I would not restore data in the big initial bulk restore but instead go back and cherry pick the data restore on the things you need.
Again worst case all lost but you assumed that anyway and maybe you can save some time and effort if either option works.
Click to expand...
Click to collapse
Yeah I actually already ran a backup with Titanium Backup and moved it to my PC last night just in case I did something stupid haha but I appreciate the tips!

Crosshatch Issue With ROMs & TWRP. Strange Occurrences

Ok, So Here's The Deal.. The Thing.. The WTF
So I had an older version of the Scorpion ROM installed and working fine for a while and wanted to change it up. I downloaded the newest TWRP. Both image and installer.zip, newest Magisk and RR 7.
I flashed the latest stock and you know, followed all the proper steps and after I flashed RR 7, it wouldn't boot up. (Not the issue) as others have had the same issue with RR 7. I left a post about that on the RR 7 thread and went about reflashing stock and proceeded to find a different ROM to check out.
No matter what I try to flash: Lineage, Scorpion, RR 7, dotOS the same thing happens... Everything flashes like it should, but then it won't boot, AND THEN every time I boot back to TWRP to try something else the haptic feedback vibration thing on the pixel 3 xl goes banana sandwich crazy and won't shut off until I reboot to fastboot to flashall to start over. LOL
And not only that but when I jump back to TWRP to try to flash something else stored on the phone, it says the storage is empty and there are nothing available in the menu. And I couldn't get a screenshot but there were some errors that have popped up in twrp as well...
Could This Be An Issue WITH TWRP itself? Because it does it with every single ROM I have flashed today. It's very strange. I have never ran into any issues like this when flashing ROMs, Kernals, etc.
I'm lost. Any help would be awesomely appreciated.
UPDATE: It now vibrates constantly in TWRP and when I reflashed to factory it did the corrupt software screen so I gave it a good ole' factory rest and then it was is stuck in a loop at the G while conecting and disconnecting to the USB over and over and over... now back to corrupt software screen.
I guess I'm just going to have to reflash Stock and just leave it.
Update 2: Still Give The Corrupt Software Thing After Performing FlashAll - soooooooooooooooo
Slo-mo Designs said:
Ok, So Here's The Deal.. The Thing.. The WTF
Could This Be An Issue WITH TWRP itself? Because it does it with every single ROM I have flashed today. It's very strange. I have never ran into any issues like this when flashing ROMs, Kernals, etc. I'm lost. Any help would be awesomely appreciated.
UPDATE: It now vibrates constantly in TWRP and when I reflashed to factory it did the corrupt software screen so I gave it a good ole' factory rest and then it was is stuck in a loop at the G while conecting and disconnecting to the USB over and over and over... now back to corrupt software screen.
I guess I'm just going to have to reflash Stock and just leave it.
Update 2: Still Give The Corrupt Software Thing After Performing FlashAll - soooooooooooooooo
Click to expand...
Click to collapse
Couple of things. Yes there was an issue with v3.2.3-4 TWRP and the vibrator, but that is separate from your boot issues. Go to the dedicated TWRP thread. As for your updates, 1) an FDR just deletes your data and so would not solve your issue. and 2) Guessing you removed the -w switch from the flash-all script or you would not be getting the corrupt software screen. Run the script again with the wipe switch in place, allowing it to wipe your partitions and start over. You've already deleted all your data with the FDR so it won't matter. Best of luck!
Always late to the party.
v12xke said:
Couple of things. Yes there was an issue with v3.2.3-4 TWRP and the vibrator, but that is separate from your boot issues. Go to the dedicated TWRP thread. As for your updates, 1) an FDR just deletes your data and so would not solve your issue. and 2) Guessing you removed the -w switch from the flash-all script or you would not be getting the corrupt software screen. Run the script again with the wipe switch in place, allowing it to wipe your partitions and start over. You've already deleted all your data with the FDR so it won't matter. Best of luck!
Click to expand...
Click to collapse
So yeah... I just now logged back on and saw your response [I have had notification issues on everything from Reddit to FB since I have had the 3XL]
About the response, I have had the issue with it showing the corrupt software screen a bunch when flashing new stuff. The reason I perform the Factory Slap is because it allows me to enter the menu where I have the option to "Boot from ADB" or whatever it says, sideloading seems to be the only way I can make progress when it starts giving the corrupt error.. The reason I didn't perform the full wipe but I can't remember exactly why now since that was over a month ago.
But I finally got it fixed, and I was going to repost because I had found a way to prevent the vibration thing from happening in TWRP but by the time I got around to posting, the new update had fixed it. Lol

Tried to encrypt, now stuck on boot screen!

Ok, so... This is a Galaxy S, 10.5". The T800. I'm running Resurrection OS: the Luis build or whatever. The one with the dog. I attempted to encrypt this thing with the built-in tool. From Settings. I tried and probably failed. I checked on my tablet a few hours later and found it stuck on the boot screen: spinny colors, all that. It never reached the end.
I rebooted into TWRP, and that worked fine. I checked to see if I could access the file manager, and I could. I could peer into various directories on the Data partition and see the files there. So I figure that's a good sign. I figured, I'll wipe the cache and the dalvik cache. That's good for what ails ya. No help. I found some recommendation about using TWRP to repair the data partition, so I tried that. No difference. I tried to boot into Safe Mood, but the key code didn't seem to make any difference either. No good.
So, any suggestions? There wasn't anything essential on there that couldn't reasonably be gotten back. I know I could just wipe... everything and start anew, but it would be a pain in the neck, pardon my French. I'd have to download and reinstall everything. If there's a quick way to get this thing back to normal without that hassle, I'd appreciate it.
If it failed,i fear your app data,information,etc might not work normal y any more?Just get to twrp,plug your usb and get your file,etc back.
Would it help if I provided a logcat?
https://filebin.net/zx61szgrgur7l7n3
Even if I have to just wipe and start over, I want to know what the heck was going on!
FailSafeNow said:
Would it help if I provided a logcat?
https://filebin.net/zx61szgrgur7l7n3
Even if I have to just wipe and start over, I want to know what the heck was going on!
Click to expand...
Click to collapse
Sorry i'm not a developer,just ask the rom builder himself https://forum.xda-developers.com/ga...om-resurrection-remix-n-sm-t800-wifi-t3606243 if i correct?

Question Help! Hanging in FastBoot Mode

Hello,
I clicked wrongly in Titanium Backup.
I clicked Freeze All.
Now I'm in Bootloop. I can start Fastboot mode, but not Recovery or Rescue.
Pixel was rooted with the November update.
With "Fastboot Devices" I see the phone on the PC.
How do I get the apps working again?
Or how do I start a complete new installation?
Translated with the Google Translator ...
Help...
Chris
Try "fastboot erase userdata" or "fastboot format userdata". Yes, its going to wipe the phone. Sorry, no alternative I'm aware of.
F***!
Thank you...
V-Ripper said:
F***!
Thank you...
Click to expand...
Click to collapse
Did you get yourself out of the boot loop?
Sounds to me like OP had something go wrong either with ramdisk or /boot. In the future I would recommend reflashing /boot to see if you're at least able to get back into system.
V0latyle said:
Sounds to me like OP had something go wrong either with ramdisk or /boot. In the future I would recommend reflashing /boot to see if you're at least able to get back into system.
Click to expand...
Click to collapse
I didn't know that Titanium Backup can do this, break a device almost completely by pressing the wrong button.
So the question is: Did the OP do something wrong before, or can this be replicated without issue?
I mean, it's a risky endeavor anyway. To use a root level backup app that wasn't optimized/made for Android 12. There's a reason why people have been recommending Swift for years now.
Morgrain said:
I didn't know that Titanium Backup can do this, break a device almost completely by pressing the wrong button.
So the question is: Did the OP do something wrong before, or can this be replicated without issue?
I mean, it's a risky endeavor anyway. Do use a root level backup app that wasn't optimized/made for Titanium. There's a reason why people have been recommending Swift for years now.
Click to expand...
Click to collapse
I used to use TB wayyyyy back when. I think I still have a paid license for it somewhere.
I'm not totally sure how this could happen; an educated guess is that OP froze a bunch of system apps, causing a kernel panic. No idea why it would mess up /boot though, screwing up /system to the point of a kernel panic would generally result in a bootloop where the kernel starts to load, but hits the same panic and restarts the device.
It's certainly risky using root backup apps that aren't updated for use on modern Android systems...
V0latyle said:
causing a kernel panic
Click to expand...
Click to collapse
Nobody said kernel panic. OP said *bootloop*, which will happen if certain expected services fail to start as expected, which can happen if you disable the wrong package. If he disabled *everything* (as he suggests), then this is logically what will happen.
I would definitely suggest NOT using "titanium backup" -- its closed source (and unmaintained, no update in 2 years!!!), so there's no way to know what its doing. Use oandbackupx (find on f-droid), which is open source and maintained (most recent update a few hours ago).
96carboard said:
Nobody said kernel panic. OP said *bootloop*, which will happen if certain expected services fail to start as expected, which can happen if you disable the wrong package. If he disabled *everything* (as he suggests), then this is logically what will happen.
Click to expand...
Click to collapse
Bootloop on Android can either be a kernel panic or other fatal stop error, such as dependent services failing to start as you described. Either way, it's transparent to the user, who simply sees the device restart. Android is built in such a way that a failure in the boot or runtime process will generally not result in a freeze requiring a hard reset, but will rather restart the device.
@V-Ripper I would have recommended you try reflashing /boot and /system before wiping. Were you able to resolve the issue?
I wonder if op could have booted to safe mode. That should have disabled all the apps. Including TB I think.
Sorry for the OP's problem, but I thought Titanium Backup stopped working a year or so ago. Does it work on the P6 and P6 Pro now?
Az Biker said:
Did you get yourself out of the boot loop?
Click to expand...
Click to collapse
Hello...
I tried "fastboot erase userdata" and then came back to a clean Android.
V0latyle said:
Sounds to me like OP had something go wrong either with ramdisk or /boot. In the future I would recommend reflashing /boot to see if you're at least able to get back into system.
Click to expand...
Click to collapse
I tried to re-flash. Did nothing.
96carboard said:
Nobody said kernel panic. OP said *bootloop*, which will happen if certain expected services fail to start as expected, which can happen if you disable the wrong package. If he disabled *everything* (as he suggests), then this is logically what will happen.
I would definitely suggest NOT using "titanium backup" -- its closed source (and unmaintained, no update in 2 years!!!), so there's no way to know what its doing. Use oandbackupx (find on f-droid), which is open source and maintained (most recent update a few hours ago).
Click to expand...
Click to collapse
Oh cool, I will try it...
Have everything set up again. Thanks to the backup of the various apps.
Thank you all...
V-Ripper said:
Hello...
I tried "fastboot erase userdata" and then came back to a clean Android.
I tried to re-flash. Did nothing.
Oh cool, I will try it...
Have everything set up again. Thanks to the backup of the various apps.
Thank you all...
Click to expand...
Click to collapse
It's nice to hear that your device is working again!
V0latyle said:
Bootloop on Android can either be a kernel panic or other fatal stop error, such as dependent services failing to start as you described. Either way, it's transparent to the user, who simply sees the device restart. Android is built in such a way that a failure in the boot or runtime process will generally not result in a freeze requiring a hard reset, but will rather restart the device.
@V-Ripper I would have recommended you try reflashing /boot and /system before wiping. Were you able to resolve the issue?
Click to expand...
Click to collapse
Yes, but based on what he said, its not a kernel panic.

Categories

Resources