Related
Hi,
My phone started to fail and give me a lot of errors that it was stopping initiator, android.process.acore, etc... and got stuck in this errors, having to accept the error dialogs all the time and being impossible to make anything with it.
I tried to reset my moto G and wipe all user data. I entered fastboot mode (couldn't do it form phone normal menu) and made a factory reset. No changes after reboot.
Then I tried to reinstall firmware. I've made all the steps in several tutorials found here. The bootloader is unlocked, I put the last firmware , entered recovery mode and ask for wipe/reset user data, but when the phone reboots, there are no changes: I have again the personalized screen image and the gesture blocking, as if the user data remains there, and all the errors.
Is there any way to erase all user data and leave the phone as the first day? Am I making something wrong or need to make something more?
Thanks in advance
Sounds like you might have encrypted it?
BobbaLouie said:
Sounds like you might have encrypted it?
Click to expand...
Click to collapse
Not consciously, the phone had normal use....
If it was encrypted you'd have to enter a password before it even got to the boot logo, so it would be very obvious.
BobbaLouie said:
If it was encrypted you'd have to enter a password before it even got to the boot logo, so it would be very obvious.
Click to expand...
Click to collapse
Then, it is not encrypted.
thanks
Jorge BCN said:
Hi,
My phone started to fail and give me a lot of errors that it was stopping initiator, android.process.acore, etc... and got stuck in this errors, having to accept the error dialogs all the time and being impossible to make anything with it.
I tried to reset my moto G and wipe all user data. I entered fastboot mode (couldn't do it form phone normal menu) and made a factory reset. No changes after reboot.
Then I tried to reinstall firmware. I've made all the steps in several tutorials found here. The bootloader is unlocked, I put the last firmware , entered recovery mode and ask for wipe/reset user data, but when the phone reboots, there are no changes: I have again the personalized screen image and the gesture blocking, as if the user data remains there, and all the errors.
Is there any way to erase all user data and leave the phone as the first day? Am I making something wrong or need to make something more?
Thanks in advance
Click to expand...
Click to collapse
Are you rooted? If so, you might have to FORMAT your phone, which will erase even your storage. I used TWRP and my phone just factory reset after I formatted. I think there must've been some sort of corruption.
Jorge BCN said:
Hi,
My phone started to fail and give me a lot of errors that it was stopping initiator, android.process.acore, etc... and got stuck in this errors, having to accept the error dialogs all the time and being impossible to make anything with it.
I tried to reset my moto G and wipe all user data. I entered fastboot mode (couldn't do it form phone normal menu) and made a factory reset. No changes after reboot.
Then I tried to reinstall firmware. I've made all the steps in several tutorials found here. The bootloader is unlocked, I put the last firmware , entered recovery mode and ask for wipe/reset user data, but when the phone reboots, there are no changes: I have again the personalized screen image and the gesture blocking, as if the user data remains there, and all the errors.
Is there any way to erase all user data and leave the phone as the first day? Am I making something wrong or need to make something more?
Thanks in advance
Click to expand...
Click to collapse
Try clearing data,cache,dalvik cache and reflashing the ROM..if all fails try to clear data and flash the stock ROM through fastboot mode.
KVCmoto said:
Try clearing data,cache,dalvik cache and reflashing the ROM..if all fails try to clear data and flash the stock ROM through fastboot mode.
Click to expand...
Click to collapse
I've made it all, but when reboot, there is the same data there....
Neither can't root the phone, when I make adb sideload supersu.zip, I receive a installation aborted error after verification of the file....
Any Ideas?
Thanks in advance
Jorge BCN said:
I've made it all, but when reboot, there is the same data there....
Neither can't root the phone, when I make adb sideload supersu.zip, I receive a installation aborted error after verification of the file....
Any Ideas?
Thanks in advance
Click to expand...
Click to collapse
Flash the stock ROM once more through boot loader http://forum.xda-developers.com/showthread.php?t=2542219
If you have TWRP installed and your data backed up, I would highly suggest formatting your phone. My phone was having heaps of trouble, including random reboots, the inability for factory data reset, it was slow, having wake time issues, all sorts of shiz. One reformat and it was all better.
MoseIlla said:
If you have TWRP installed and your data backed up, I would highly suggest formatting your phone. My phone was having heaps of trouble, including random reboots, the inability for factory data reset, it was slow, having wake time issues, all sorts of shiz. One reformat and it was all better.
Click to expand...
Click to collapse
What do you mean with reformat? I can't boot into other recovery than stock, and it doesn't allow me erase user data, thats the problem.
When I try to flash other recovery (TWRP, Philz,..) it seems that has been flashed ok but when go to recovery from bootloader menu I have the old stock recovery menu...
Thanks in advance
Jorge BCN said:
What do you mean with reformat? I can't boot into other recovery than stock, and it doesn't allow me erase user data, thats the problem.
When I try to flash other recovery (TWRP, Philz,..) it seems that has been flashed ok but when go to recovery from bootloader menu I have the old stock recovery menu...
Thanks in advance
Click to expand...
Click to collapse
You unlocked the bootloader then, yes? How's your ROM behaving?
MoseIlla said:
You unlocked the bootloader then, yes? How's your ROM behaving?
Click to expand...
Click to collapse
Can you be more explicit?
Are you using the special mfastboot or the generic fastboot executable from the Android SDK?
Execute these commands with the phone in fastboot (bootloader menu):
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
liveroy said:
Are you using the special mfastboot or the generic fastboot executable from the Android SDK?
Execute these commands with the phone in fastboot (bootloader menu):
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Click to expand...
Click to collapse
Hi, the same after rebooting, I have all my user data... (I'm using mfastboot for OSX, but the same result with fastboot under Darwin subfolder of stock firmware)
no errors executing it, no errors in the phone, but no effect in phone user data
$ ./mfastboot erase cache
erasing 'cache'...
OKAY [ 0.017s]
finished. total time: 0.017s
$ ./mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.018s]
finished. total time: 0.019s
$ ./mfastboot reboot
Jorge BCN said:
Can you be more explicit?
Click to expand...
Click to collapse
I just reread your first post. When did your phone start giving you errors? Did you install any new apps, did you let it die completely? The errors had to have started somewhere. Perhaps we can undo a bit of the damage that lead to this and get you back to a somewhat usable state if we have that information.
MoseIlla said:
I just reread your first post. When did your phone start giving you errors? Did you install any new apps, did you let it die completely? The errors had to have started somewhere.
Click to expand...
Click to collapse
No idea. There was not anything special or new app. A month ago it started to give errors. Sometimes I can get 1 or 2 minutes working without errors, but can't delete user data or reset from phone menu (no result when touch the button).
Thanks
Jorge BCN said:
No idea. There was not anything special or new app. A month ago it started to give errors. Sometimes I can get 1 or 2 minutes working without errors, but can't delete user data or reset from phone menu (no result when touch the button).
Thanks
Click to expand...
Click to collapse
Does this coincide with a firmware update (Like Android 4.4.2 to 4.4.3)?
MoseIlla said:
Does this coincide with a firmware update (Like Android 4.4.2 to 4.4.3)?
Click to expand...
Click to collapse
Nopes, as far as I know
Here's what I know about the issue, perhaps it will give someone else an idea:
1. The issue is either caused by or is unaffected by previous factory resets.
2. The issue is either caused by or is unaffected by the installation of new and/or updated ROMs.
3. If it's the same issue I was having, and I believe that it least shares the same root cause, then it is something that gets worse over time; it causes system instability (system UI crashes in increasing number, random reboots, etc...), slowness, and refuses to allow you to hard reset after a while.
4. In the case that it is the same issue, it has different effects on different methods of factory resets. In TWRP the factory reset process just continues on forever, until you hard reboot the device or until the battery drains out. If you press the factory reset button in fastboot it just resets to system, making no changes.
5. In TWRP I used the reformat option and have since had no issues, including better than new performance with crDroid.
Based on my understanding of the Moto G partition tables, I believe that the issue may have to do with gradual data corruption, possibly on the storage partition. This may be because of a software bug in the firmware or maybe a hardware issue. Due to the ubiquity of the lock up/reboot issue, which is well documented and has several guides indicating that a factory reset is in order when this occurs, I'm thinking that it is safe to assume that some resource shared both with the system and storage partitions is to blame.
If that is the case, then I would think it's the cache or a bug with an updated system app that leaves traces in the device storage.
This is all assuming the issues are interrelated, so I may be way off base, but if my assumptions are correct, then the only suggestion I can think of is to completely clear the device storage and cache and then try to factory reset again, as it may be hanging up on removing something there and aborting when it runs into trouble.
Maybe someone has a better idea. Your device may be bricked and since you unlocked the boot loader AFTER the issues started, you voided your warranty with none of the advanced recovery tools that you'd have with a custom recovery.
In other words: You might have to get a new phone.
I'm really at a loss for what to do here... I'll give as much backstory as I can.
I had installed WETA v4.1 while also running Renovate ICE, which was not causing any issues until I toggled the "Google Photos workaround" option which set my phone as a Pixel 3 XL. This caused a conflict and made Renovate ICE think I was an unsupported device, thus causing my RiCE tweaks to cease working.
Being a good boy I decided to do a nandroid backup before I installed WETA v4.1 so I was going to just restore from that and re-install WETA without toggling the Google Photos workaround. After restoring in TWRP and hitting reboot system I ran into a bootloop in Fastboot. I cannot boot into recovery even. It is detected in fastboot but using .\fastboot reboot didn't work and I tried to use the all-in-one tool and none of those reboot options worked either.
How can I get out of this fastboot situation? Please help!!
I tried flashing recovery from fastboot:
FAILED (remote: (recovery_a) No such partition')
Well... google helped out finally after reading 100 posts... it was as simple as flashing my recovery using the following command:
fastboot flash boot recoveryname.img
I thoroughly enjoyed this roller coaster of a one way conversation.
Thank you.
Hunter3U said:
I thoroughly enjoyed this roller coaster of a one way conversation.
Thank you.
Click to expand...
Click to collapse
You're welcome. I was freaking out for a little bit thinking I lost everything. I rooted my Galaxy S3 years ago but haven't done much in terms of rooting etc since 2012 or so... needless to say I am making some rookie mistakes. I'm still stumped as to what happened with the TWRP restore that caused this to happen in the first place. Any ideas?
i.Design said:
You're welcome. I was freaking out for a little bit thinking I lost everything. I rooted my Galaxy S3 years ago but haven't done much in terms of rooting etc since 2012 or so... needless to say I am making some rookie mistakes. I'm still stumped as to what happened with the TWRP restore that caused this to happen in the first place. Any ideas?
Click to expand...
Click to collapse
I've never had great luck with twrp restores. I have made a few on this phone but never got them to go through properly. My phone stays set up in a way where i don't ever need backups to get up and running. I know i restore too much to have to worry about backing up everything on a regular basis.
i.Design said:
I tried flashing recovery from fastboot:
FAILED (remote: (recovery_a) No such partition')
Click to expand...
Click to collapse
what command did you use.
download and choose your model and OS
try
Code:
fastboot flash boot boot_patched.img
if it still does not boot then try TWRP
Code:
fastboot flash boot twrpname.img
when recovering from TWRP just recover data only. Not Boot and System/Vendor.
Bradl79 said:
what command did you use.
download and choose your model and OS
try
Code:
fastboot flash boot boot_patched.img
if it still does not boot then try TWRP
Code:
fastboot flash boot twrpname.img
when recovering from TWRP just recover data only. Not Boot and System/Vendor.
Click to expand...
Click to collapse
Ah sorry I didn't mention the command - it was:
.\fastboot flash TWRP.img
I didn't use the correct command, after doing fastboot flash boot twrpname.img it worked.
Thanks for the note on restoring only data, that must be where things went south.
I have the T-Mobile OnePlus 8. SIM/BL unlocked, converted to international firmware. FP worked the whole time during the conversion. Had issues with the modem, but that's a given an was sorted out.
I heavily rely on Google Pay because I'm lazy and rarely carry my wallet with me. I ended up installing EdXposed to see what has changed since the last time I used it years ago. There was a XStadia module that came in handy so that I could use Stadia on my data connection instead of WiFi. After using it for some time, I decided that having Xposed wasn't worth breaking SafetyNet over, so I uninstalled. Well for some reason, it didn't uninstall probably or something happened along the way that SN was still broken. So I figured the only way to fix is to factory data reset. Bad idea. These devices nowadays aren't like what they used to be. Ended up with multiple CrashDump screens. Ran into a crap ton of issues so I ended up used my the MSM tool to go back to the stock T-Mobile firmware, using the 10.5.7 fastboot ROM to go back to international, etc.
When I went back to international again, I noticed that my fingerprint sensor wasn't working so I followed the guide found here: https://forum.xda-developers.com/oneplus-8/how-to/guide-fix-persist-img-loss-finger-print-t4126455 The only thing I wasn't able to do was downgrade to an earlier OOS like 10.5.4 mentioned in the guides OP due to the phone not letting me. I tried the MSM 10.5.4 tool, and the 10.5.4 fastboot ROM. Both didn't work and gave me errors (I'm guessing because it's a branded device and certain critical partitions can't be overwritten). So I ended up pulling my broken persist from the T-Mobile stock rooted firmware, fastboot flashed 10.5.7, and went from there.
After some time, I finally had a working FP. Thanks again @antnyhills. When it was working, I thought that every time I used the FP, it gave me more errors than it actually unlocked the phone. So, I thought I'd be a little curious and see if doing the FP tests again would fix it. IT DID NOT. I ended up breaking it so bad, that now I get an error saying "fingerprint hardware not present". When I go to setup a new fingerprint, it says "enrollment was not completed. Fingerprint sensor error, please try again". If I go back to dismiss the error, the FP is still present, and when I press on it, the circle lights up, it just doesn't vibrate or register anything.
So, I followed the guide again. Again, nothing. Now I'm sitting here and nothing works. Camera doesn't work (black screen when opening), flashlight doesn't work, and I'm sure there's a few other things, just didn't mention. What do I do now? Get a hold of OnePlus and see if they'll replace my device? Is there a way to erase the Persist.img from the device and reflash it again somehow?
TL;DR: FP sensor broken, camera broken, after following broken persist.img guide.
antnyhills said:
Make sure you are using your original persist.img from your backup the first time you did this guide to transfer the two folders. If that fails. Flash your the same original back up persist.img and start the guide again.
Click to expand...
Click to collapse
Make sure you are using your original persist.img from your backup the first time you did this guide to transfer the two folders. If that fails. Flash your the same original back up persist.img and start the guide again.
If you get it working again, the FP sensor just as accurate as it was out of the box because you are using the factory calibrations.
When you set up your fingerprint it is not accurate at first but over time in learns you fingerprint even more and becomes more accurate and fast.
antnyhills said:
Make sure you are using your original persist.img from your backup the first time you did this guide to transfer the two folders. If that fails. Flash your the same original back up persist.img and start the guide again.
Click to expand...
Click to collapse
I did, multiple times to no avail. How do I go about flashing the persist.img? There are only a few options in TWRP. Two super, recovery, and boot.
I know, I remember reading somewhere that it learns every time. I should've just left it alone and let it do its thing, but of course I had to go and mess things up.
Is my flashlight and camera not working because of persist files?
When I got it working again using your guide, when I started tinkering around, even though my FP was working, when I rebooted, it said"fingerprint hardware not present". Now all of the apps that use FP don't even ask me if I want to use FP like it's not even there .
TheKnux said:
I did, multiple times to no avail. How do I go about flashing the persist.img?
Click to expand...
Click to collapse
Go to the bootloader.
Code:
fastboot reboot fastboot
This will take you to fastbootd. It will look like your recovery. You must have stock original recovery installed. TWRP will not work.
Code:
fastboot flash persist [INSERT YOUR PERSIST.IMG HERE]
Example:
Code:
fastboot flash persist C:\user\example\desktop\persist.img
Make sure you are flashing the persist.img from your original time you performed this guide. This will take you back to were you where before you ever performed the guide.
Then follow the guide one more time, follow it VERY CAREFULLY as there is a lot to go wrong.
Best of luck!
Edit: Also, I would assume your camera/flashlight broke because of your persist partition. Hence Why we are going to start from scratch with your original broken persist.img
antnyhills said:
Go to the bootloader.
This will take you to fastbootd. It will look like your recovery. You must have stock original recovery installed. TWRP will not work.
Example:
Make sure you are flashing the persist.img from your original time you performed this guide. This will take you back to were you where before you ever performed the guide.
Then follow the guide one more time, follow it VERY CAREFULLY as there is a lot to go wrong.
Best of luck!
Edit: Also, I would assume your camera/flashlight broke because of your persist partition. Hence Why we are going to start from scratch with your original broken persist.img
Click to expand...
Click to collapse
I'm not a noob at rooting/ROMing. I'm just new at doing this kind of stuff. Messing with critical files in the root directory. I appreciate you chiming in and helping me with this. I'll do what you said and report back. Appreciate everything you've done, including you helping me with this.
TheKnux said:
I'm not a noob at rooting/ROMing. I'm just new at doing this kind of stuff. Messing with critical files in the root directory. I appreciate you chiming in and helping me with this. I'll do what you said and report back. Appreciate everything you've done, including you helping me with this.
Click to expand...
Click to collapse
No worries. Eager to hear your update.
antnyhills said:
No worries. Eager to hear your update.
Click to expand...
Click to collapse
target reported max download size of 805306368 bytes
sending 'persist' (32768 KB)...
OKAY [ 0.703s]
writing 'persist'...
FAILED (remote: Flashing is not allowed for Critical Partitions
)
finished. total time: 0.718s
That is my error I get when following your instructions.
TheKnux said:
target reported max download size of 805306368 bytes
sending 'persist' (32768 KB)...
OKAY [ 0.703s]
writing 'persist'...
FAILED (remote: Flashing is not allowed for Critical Partitions
)
finished. total time: 0.718s
That is my error I get when following your instructions.
Click to expand...
Click to collapse
Make sure you do
Code:
fastboot reboot fastboot
Like I mentioned it should look like the stock recovery. When you do that does it take you to your stock recovery?
If you have discord, I'll PM you a link, might be easier to communicate.
antnyhills said:
Make sure you do
Code:
fastboot reboot fastboot
Like I mentioned it should look like the stock recovery. When you do that does it take you to your stock recovery?
If you have discord, I'll PM you a link, might be easier to communicate.
Click to expand...
Click to collapse
So to my knowledge, stock recovery is the screen with the OnePlus logo, some chinese words, and English and Fastboot is the screen that says the SoC name, device state, etc.
I even tried "fastboot flash persist_critical persist.img" and it didn't work. Also, fastboot reboot fastboot doesn't do anything. Fastboot reboot bootloader sends me to fastboot. Using Windows 10/PowerShell.
I do have Discord but it runs like crap on my PC (old laptop) and since my phone is down currently, this is the only way to talk.
TheKnux said:
So to my knowledge, stock recovery is the screen with the OnePlus logo, some chinese words, and English and Fastboot is the screen that says the SoC name, device state, etc.
I even tried "fastboot flash persist_critical persist.img" and it didn't work.
I do have Discord but it runs like crap on my PC (old laptop) and since my phone is down currently, this is the only way to talk.
Click to expand...
Click to collapse
Boot phone
Put persist.img on the root of your 'sdcard'
Code:
adb shell
Code:
su
Code:
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
reboot
antnyhills said:
Boot phone
Put persist.img on the root of your 'sdcard'
Code:
adb shell
Code:
su
Code:
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
reboot
Click to expand...
Click to collapse
Okay, that seems to have worked. I did that while on T-Mobile firmware. I just fastboot flashed the 10.5.7 international firmware, updating to 10.5.9 via OTA now, when it reboots, I'm going to install TWRP and Magisk, and push the persist.img again using the command you gave me once more for good measure then fix FP using your guide. On the flip side, once I pushed the persist.img using your command, my flashlight and camera works again, just not FP, yet. I'll report back after following your guide. Thank you again.
TheKnux said:
So to my knowledge, stock recovery is the screen with the OnePlus logo, some chinese words, and English and Fastboot is the screen that says the SoC name, device state, etc.
I even tried "fastboot flash persist_critical persist.img" and it didn't work. Also, fastboot reboot fastboot doesn't do anything. Fastboot reboot bootloader sends me to fastboot. Using Windows 10/PowerShell.
I do have Discord but it runs like crap on my PC (old laptop) and since my phone is down currently, this is the only way to talk.
Click to expand...
Click to collapse
You need to have the latest version of adb and fastboot from Google on your PC for "fastboot reboot fastboot" to work and be able to access fastbootd.
https://developer.android.com/studio/releases/platform-tools
Fastbootd is something new and different from bootloader. It allows flashing to all partitions (required due to dynamic partitioning in Android 10). However, it looks very similar to stock recovery (it actually uses stock recovery which is why it won't work with TWRP flashed). "fastboot reboot bootloader" sends you to bootloader, which is no longer the same as fastboot.
However, the instructions posted by @antnyhills will also work perfectly fine for restoring persist. That's the method I use (personally I try to avoid fastboot flash at all on this phone)
Your problem is you completely corrupted your persist.img. That's why you have a backup . Or now you'd be without sensors, camera, flashlight, etc until someone posted theirs but then you would never be able to fix fingerprint.
Once you have fingerprint working again, take a new backup of persist. Then no need to fix it again in the future if it gets messed up. Simply restore it.
starcms said:
You need to have the latest version of adb and fastboot from Google on your PC for "fastboot reboot fastboot" to work and be able to access fastbootd.
https://developer.android.com/studio/releases/platform-tools
Fastbootd is something new and different from bootloader. It allows flashing to all partitions (required due to dynamic partitioning in Android 10). However, it looks very similar to stock recovery (it actually uses stock recovery which is why it won't work with TWRP flashed). "fastboot reboot bootloader" sends you to bootloader, which is no longer the same as fastboot.
However, the instructions posted by @antnyhills will also work perfectly fine for restoring persist. That's the method I use (personally I try to avoid fastboot flash at all on this phone)
Your problem is you completely corrupted your persist.img. That's why you have a backup . Or now you'd be without sensors, camera, flashlight, etc until someone posted theirs but then you would never be able to fix fingerprint.
Once you have fingerprint working again, take a new backup of persist. Then no need to fix it again in the future if it gets messed up. Simply restore it.
Click to expand...
Click to collapse
I tried Googling for the latest adb/fastboot drivers but I already spent half the day restoring my persist and fixing my FP. I thought there would be a flasher like the 1.4.2 drivers but it wants me to install the sdk and install it through there. Not my top priority right now, next time I'm on my pc though I will for sure. The method @antnyhills told me to do to push the persist worked great, followed his guide again, fixed FP, and backed up persist with FP and all sensors working. Stored it in two places so I don't accidentally delete them lol. The updated drivers you're mentioning, that'll allow me to flash critical partitions in case I mess something up again next time?
Huge thanks to @antnyhills for coming in here and helping me out, and to you for giving me your two cents as well. I was so tempted to be a Karen and get T-Mobile and OnePlus on the phone to RMA my device. ?
TheKnux said:
I tried Googling for the latest adb/fastboot drivers but I already spent half the day restoring my persist and fixing my FP. I thought there would be a flasher like the 1.4.2 drivers but it wants me to install the sdk and install it through there. Not my top priority right now, next time I'm on my pc though I will for sure. The method @antnyhills told me to do to push the persist worked great, followed his guide again, fixed FP, and backed up persist with FP and all sensors working. Stored it in two places so I don't accidentally delete them lol. The updated drivers you're mentioning, that'll allow me to flash critical partitions in case I mess something up again next time?
Huge thanks to @antnyhills for coming in here and helping me out, and to you for giving me your two cents as well. I was so tempted to be a Karen and get T-Mobile and OnePlus on the phone to RMA my device.
Click to expand...
Click to collapse
It's not updated drivers. It's an updated version of adb and fastboot that fully supports all the new commands needed (such as "fastboot reboot fastboot"). I had provided a link. Just download and unzip to your adb directory on your PC and select replace all files when copying.
https://developer.android.com/studio/releases/platform-tools
starcms said:
It's not updated drivers. It's an updated version of adb and fastboot that fully supports all the new commands needed (such as "fastboot reboot fastboot"). I had provided a link. Just download and unzip to your adb directory on your PC and select replace all files when copying.
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Where would the adb directory be if I used the "adb and fastboot installer for windows" (or whatever it's called) found here on XDA? I'm guessing it's years old. I think it said version 1.4.2 or something.
Also, are you or @antnyhills on Telegram at all?
what was the final of this, i have the oneplus8 tmobile, and i want to convert to globla, but this issue scared me
Greetings,
Recently picked up this Pixel 3 and I like it hardware-wise but want to degoogle as much as I can (only want the bare minimum Play store to ensure I can use all my usual apps [nothing from Google - let me know if you need a list]).
Think that means I'll want to end up with Lineage OS 18.1 (Android 11?) + OpenGApps (Pico) + Magisk (for root?) does this seem correct?
Been reading a mishmash of this: https://forum.xda-developers.com/t/the-complete-pixel-3-how-to-guide-newbie-friendly.3922269/page-2 and other guides and I'm a bit confused.
I've rooted and imaged my previous Moto phone but it's been a while. From what I gather so far, the general plan for this Pixel is: oem unlock, usb debugging, unlock bootloader, boot recovery, install recovery, install lineage, install opengapps, install magisk, ????, profit.
However in the guide I linked, I see that the TWRP section is all red and strikethrough. And have read (perhaps old info?) that Android 10 and up TWRP doesn't work/support?
Yet every guide I've seen says to install TWRP and also the date on this OP is updated November 2020...? Plus, there are notes on the twrp page that just say mtp isn't working but otherwise that means it should work, right?: (https://twrp.me/google/googlepixel3.html)
I've unlocked the bootloader oem unlock, got the USB drivers and platform-tools installed (via most up-to-date Android Studio), see my device (Google Pixel 3) with adb devices, and can issue commands like adb reboot fastboot... I have everything this guide mentions ready to go, but I am stuck at temporarily booting recovery image:
Error output:
C:\Users\Nate\AppData\Local\Android\Sdk\platform-tools>fastboot boot twrp-3.3.0-0-blueline.img
Sending 'boot.img' (65536 KB) OKAY [ 0.232s]
Booting FAILED (remote: 'Unrecognized command boot')
fastboot: error: Command failed
C:\Users\Nate\AppData\Local\Android\Sdk\platform-tools>fastboot boot twrp-3.3.0-0-blueline.img
Sending 'boot.img' (65536 KB) OKAY [ 0.263s]
Booting FAILED (remote: 'Error verifying the received boot.img: Invalid Parameter')
fastboot: error: Command failed
The first command I realized failed because it was in 'fastbootd'... so I made sure to have it on the 'regular' fastboot, and get the second error. Invalid parameter... what's invalid?
This is what my screen looks like which makes me believe I've done right so far (attachments).
Feel incredibly humbled to be stuck at the first stage
Can anyone please tell me what I'm doing wrong or what I missed? Your assistance is much appreciated.
Thank you in advance.
TWRP has not worked on the Pixel 3 for a couple of years. I have not tried installing Lineage on my Pixel 3, but the process described at https://wiki.lineageos.org/devices/blueline/install should work. Basically use Lineage Recovery instead of TWRP.
dcarvil said:
TWRP has not worked on the Pixel 3 for a couple of years. I have not tried installing Lineage on my Pixel 3, but the process described at https://wiki.lineageos.org/devices/blueline/install should work. Basically use Lineage Recovery instead of TWRP.
Click to expand...
Click to collapse
Ok, thank you for the reply. I will go ahead and use the Lineage Built in recovery.
I wanted to use TWRP since before I actually start changing things, wanted to do a full and complete backup, basically a complete image of all files and partitions as is before I start changing things. I'll check the lineage wiki, but to your knowledge can you do a complete backup from lineage recovery?
nasch007 said:
Ok, thank you for the reply. I will go ahead and use the Lineage Built in recovery.
I wanted to use TWRP since before I actually start changing things, wanted to do a full and complete backup, basically a complete image of all files and partitions as is before I start changing things. I'll check the lineage wiki, but to your knowledge can you do a complete backup from lineage recovery?
Click to expand...
Click to collapse
Sorry, I have not used Lineage Recovery, so I don't know what backup capability it has.
Lineage recovery is just a modified stock recovery, it has no backup ability, only what is in stock.
wangdaning said:
Lineage recovery is just a modified stock recovery, it has no backup ability, only what is in stock.
Click to expand...
Click to collapse
Roger that. Thanks to dcarvil's guidance (pointing me to the correct instructions) I was able to successfully install and root.
I have some follow up questions, probably best suited for another thread. But while I have your attention, could you tell me where to report bugs or get general usage support? There's a few things that I don't think are working the way they're supposed to or features that seem missing. If you don't know, I respect that and a mod can close this thread.
Thanks again!
I have a new Pixel 4a, Android 12. I want to use lineage 19.1. I try already several days to flash TWRP, sunfish_twrp3.6.1-11 or sunfish_twrp11-test3. No success. Finally I write fastboot flash boot_a_twrp.img instead of fastboot boot twrp.img. It ended up with the screen of teamwin, hanging there. Now the pixel is not booting to android any more but each time to the incomplete teamwin screen. So I tried to flash the newest factory image. No success : "writing 'boot' failed (remote: Failed to write to partition Not Found)
I need help urgently. Thanks!
Henneranek said:
I have a new Pixel 4a, Android 12. I want to use lineage 19.1. I try already several days to flash TWRP, sunfish_twrp3.6.1-11 or sunfish_twrp11-test3. No success. Finally I write fastboot flash boot_a_twrp.img instead of fastboot boot twrp.img. It ended up with the screen of teamwin, hanging there. Now the pixel is not booting to android any more but each time to the incomplete teamwin screen. So I tried to flash the newest factory image. No success : "writing 'boot' failed (remote: Failed to write to partition Not Found)
I need help urgently. Thanks!
Click to expand...
Click to collapse
I don't think you're providing enough info. "I tried to flash the newest factory image" doesn't tell useful people what you did. I'm not useful, anyway.
I wouldn't use TWRP on the 4a. I'm using LOS recovery. You can follow the instructions (read the whole thing first) here: https://wiki.lineageos.org/devices/sunfish/install
That should allow you to do a clean install of LOS19.
Thank you for giving advice. I followed exactly your recommended web-site (Install LineageOS on sunfish, Temporarily booting a custom recovery using fastboot). From what I understand the first step is to install a recovery which in my case was sunfish_twrp3.6.1-11.img . I did not work. I also tried an older twrp.img. "fastboot flash boot twrp.img" did not work. I read and read, learned about 2 slots, without a deep understanding. Then I tried " fastboot flash boot_a_twrp.img". It seemed to work. But when I reboot into recovery it is stuck at the screen of teamwin (see attachment).
I thought to give up and do a factory reset. But there I got this: Failed to write to partition Not Found. What can I do now? Is there a way to do a factory reset to slot_b ?
If you try to help me please remember that I don't have enough knowledge to understand abbreviations.
Henneranek said:
Thank you for giving advice. I followed exactly your recommended web-site (Install LineageOS on sunfish, Temporarily booting a custom recovery using fastboot). From what I understand the first step is to install a recovery which in my case was sunfish_twrp3.6.1-11.img . I did not work. I also tried an older twrp.img. "fastboot flash boot twrp.img" did not work. I read and read, learned about 2 slots, without a deep understanding. Then I tried " fastboot flash boot_a_twrp.img". It seemed to work. But when I reboot into recovery it is stuck at the screen of teamwin (see attachment).
I thought to give up and do a factory reset. But there I got this: Failed to write to partition Not Found. What can I do now? Is there a way to do a factory reset to slot_b ?
If you try to help me please remember that I don't have enough knowledge to understand abbreviations.
Click to expand...
Click to collapse
if it goes into bootloader head over to the android flash tool and give that a try,,https://source.android.com/setup/contribute/flash
To hammered58 Thank you for this suggestion reg. android flash tool. This seems very complicated and I don' t understand some terms. I am a NOOB.
In my Pixel 4a the slot a is somehow obstructed. Can't I use slot b to do a factory reset?
Henneranek said:
To hammered58 Thank you for this suggestion reg. android flash tool. This seems very complicated and I don' t understand some terms. I am a NOOB.
In my Pixel 4a the slot a is somehow obstructed. Can't I use slot b to do a factory reset?
Click to expand...
Click to collapse
Its not complicated at all,, just put you phone in fastboot, which I know you have done before , go here (https://flash.android.com) and follow the on screen prompts, select any factory image and start.
Dear hammered58, I am so thankful to you! Thank you for encouraging me to use the Android Flash Tool. I was skeptical. To undo the pop-up blocker in Chrome was complicated for me. After some failures because I was not patient enough I finally succeeded.
Henneranek said:
Dear hammered58, I am so thankful to you! Thank you for encouraging me to use the Android Flash Tool. I was skeptical. To undo the pop-up blocker in Chrome was complicated for me. After some failures because I was not patient enough I finally succeeded.
Click to expand...
Click to collapse
Good to know it worked for you