Related
I've just upgraded to 4.4 here on my Nexus 7 which has broken Kingsoft office which I require for my work.
Whilst I wait for a fix from Kingsoft, is there any way to roll back to 4.3 without voiding my warranty?
Thanks in advance.
Try quick office. It's free and works fine.
If you still want to roll back, you can do without voiding warranty
Download the one click factory restore from here
http://liciousroms.com/nexus7Gen2_restore.html
and some instructions and info here
http://forum.xda-developers.com/showthread.php?t=2381582
also your bootloader needs to unlocked for it to work and you will lose your data if you unlock the bootloader now.
There might be better options though. Wait for someone more knowledgeable to reply.
littleromeo said:
Try quick office. It's free and works fine.
If you still want to roll back, you can do without voiding warranty
Download the one click factory restore from here
http://liciousroms.com/nexus7Gen2_restore.html
and some instructions and info here
http://forum.xda-developers.com/showthread.php?t=2381582
also your bootloader needs to unlocked for it to work and you will lose your data if you unlock the bootloader now.
There might be better options though. Wait for someone more knowledgeable to reply.
Click to expand...
Click to collapse
Thanks for that. The reason I need to use Kingsoft is because I need the data validation function on the spreadsheets with drop down boxes for what's allowed.
Cheers
mattburley said:
I've just upgraded to 4.4 here on my Nexus 7 which has broken Kingsoft office which I require for my work.
Whilst I wait for a fix from Kingsoft, is there any way to roll back to 4.3 without voiding my warranty?
Click to expand...
Click to collapse
You can rollback to 4.3 system software however if you try to keep your user data your system will hang at boot. If you have a backup of your 4.3 user data then that is not a big deal. Alternatively if you wipe data factory reset from recovery that will get things working again.
You do need to unlock your bootloader and flash the factory images though.
sfhub said:
You can rollback to 4.3 system software however if you try to keep your user data your system will hang at boot. If you have a backup of your 4.3 user data then that is not a big deal. Alternatively if you wipe data factory reset from recovery that will get things working again.
You do need to unlock your bootloader and flash the factory images though.
Click to expand...
Click to collapse
Thanks both.
So if I follow the instructions on http://forum.xda-developers.com/showthread.php?t=2381582 I should be OK? Or do I need to unlock the bootloader? If so how do I do that?
Cheers
mattburley said:
Thanks both.
So if I follow the instructions on http://forum.xda-developers.com/showthread.php?t=2381582 I should be OK? Or do I need to unlock the bootloader? If so how do I do that?
Cheers
Click to expand...
Click to collapse
You need to have the bootloader unlocked to flash anything unsigned. Currently the only thing Google sends out that is signed are the OTAs. There is no OTA from KRT16S/O back to JSS15*, so your only option is to use a factory restore. Since the factory restores shipped so far are not signed, you need to unlock bootloader.
You can unlock the bootloader here:
http://forum.xda-developers.com/showthread.php?t=2379618
During the process of unlocking bootloader, the system will wipe your userdata and sdcard for security reasons.
The post you reference assumes your bootloader is already unlocked.
So, you got two options left.
You need to unlock the bootloader under both methods. Remember it wipes user data completely.
After unlocking you can either flash the factory image for 4.3 or use the one click factory restore.
Personally I feel one click factory restore is easier
littleromeo said:
So, you got two options left.
You need to unlock the bootloader under both methods. Remember it wipes user data completely.
After unlocking you can either flash the factory image for 4.3 or use the one click factory restore.
Personally I feel one click factory restore is easier
Click to expand...
Click to collapse
If the bootloader is already unlocked, could I revert to 4.3 without losing data ?
lapocompris said:
If the bootloader is already unlocked, could I revert to 4.3 without losing data ?
Click to expand...
Click to collapse
Yes, but I may be mistaken but unlocking the boot loader may constitute as voiding the warranty as well.
You would have to unlock it, which will wipe, downgrade to 4.3, then relock it to make it look stock.
Thanks guys I'm back on 4.3. How do I re-lock the boot loader?
Matt
lapocompris said:
If the bootloader is already unlocked, could I revert to 4.3 without losing data ?
Click to expand...
Click to collapse
You can get back to the 4.3 ROM w/o wiping user data (as a result of the unlock)
However the 4.3 ROM will not boot (will hang at X animation) with your user data once the 4.4 upgrade process has completed on your user data, so you will probably end up wiping user data anyway to get the boot to complete.
---------- Post added at 12:26 PM ---------- Previous post was at 12:25 PM ----------
mattburley said:
Thanks guys I'm back on 4.3. How do I re-lock the boot loader?
Matt
Click to expand...
Click to collapse
Boot to bootloader (Power+VolDown)
in command prompt in your SDKs platform-tools directory
fastboot oem lock
Unlike unlocking, you will NOT have to wipe user data when locking.
Locking just sets a flag so it is very fast.
However, I would leave it unlocked if I were you and you are not selling it or getting warranty work done. If you ever need to unlock again you are going to be in the same boat of losing all of your data.
Rick
mattburley said:
I've just upgraded to 4.4 here on my Nexus 7 which has broken Kingsoft office which I require for my work.
Whilst I wait for a fix from Kingsoft, is there any way to roll back to 4.3 without voiding my warranty?
Thanks in advance.
Click to expand...
Click to collapse
latest version is compatible with kitkat
Let me ask a question. I've got my bootloader unlocked and I've downloaded the stock 4.3.2 from the Google Developer's site. If I don't want to do the one click restore can someone point me in the right direction for a good step by step? I've looked at a couple of different ones but none looked right or I'm not reading things correctly. To be honest I can't find the one I read from a couple of days ago. It addresses dealing with the tarball you get when you download the image from Google, but I'm really really bad about not using bookmarks. So I'm kinda stuck at this point now. Thanks in advanced.
Found it
I can get the bootloader menu to come up but it says its locked and its a Verizon version. I've done a bunch of reading. My last resort is to file for lost but if there is a way to get it working again. I will donate to Chainfire or whoever.
Why would you u unlock then lock,??? If your phone is still operational just relock your bootloader.
just use depixel8 to unlock again and then use the firmware from googles website to flash everything back which will fix whatever else you messed up
---------- Post added at 12:52 AM ---------- Previous post was at 12:51 AM ----------
use the version for Marlin that ends in P... and unlocking isn't necessary to do flash this but I figured you want unlock which is the only reason why I said to do depixel8 again
I used Chainfires method of Unlocking and then I unrooted the phone. I was tyring to play pokemon lol with my girl so I just locked the bootloader thinking it would factory reset my root automatically now it boots straight to charging weird. But aslong as I can still see the settings screen where you can START , Recovery and all that their is still a way right? I do half understand what you guys say because I used to write software in Visual Basic. Its just I haven't really dabbled into the Android / Linux stuff much.
In the bootloader(fastboot mode), while being connected to your PC, try typing fastboot format userdata and then fastboot format cache. This will wipe your device and maybe boot up. You can't flash anything now with a locked bootloader.
Sent from my Pixel XL using XDA-Developers mobile app
KrazyBrandon said:
I can get the bootloader menu to come up but it says its locked and its a Verizon version. I've done a bunch of reading. My last resort is to file for lost but if there is a way to get it working again. I will donate to Chainfire or whoever.
Click to expand...
Click to collapse
What do you mean "My last resort is to file for lost"?
I'm hoping you're not intending to commit fraud because you screwed up you're phone. Apologies if I'm misreading your statement.
@KrazyBrandon, Benjamin150 may be able to help you. I sent him a pm so be on the lookout for his advice.
Sent from my Pixel XL using XDA-Developers mobile app
Roger that I look forward to trying. I really enjoy the phone.
none of these advices are correct... unlock using depixel8 again which might fix the issue on its own if not just go to https://developers.google.com/android/images click accept and download the image for Marlin that ends in a P and extract it place your adb and fastboot binaries inside the folder that was made by extracting.... then go to the android bootloader mode hook up to computer and do fastboot flash-all.bat this will factory reset your device but you will be completely back to stock
Mike02z said:
What do you mean "My last resort is to file for lost"?
I'm hoping you're not intending to commit fraud because you screwed up you're phone. Apologies if I'm misreading your statement.
Click to expand...
Click to collapse
this is exactly what I was thinking and a reason why we pay so much for insurance and coverages. just a disgrace to read that comment. I've reported this post.
diabl0w said:
none of these advices are correct... unlock using depixel8 again which might fix the issue on its own if not just go to https://developers.google.com/android/images click accept and download the image for Marlin that ends in a P and extract it place your adb and fastboot binaries inside the folder that was made by extracting.... then go to the android bootloader mode hook up to computer and do fastboot flash-all.bat this will factory reset your device but you will be completely back to stock
Click to expand...
Click to collapse
He locked his bootloader. You can't flash IMG files with a locked bootloader.
Sent from my Pixel XL using XDA-Developers mobile app
ko0ky said:
this is exactly what I was thinking and a reason why we pay so much for insurance and coverages. just a disgrace to read that comment. I've reported this post.
Click to expand...
Click to collapse
No need for all that. I'm sure you've done some questionable things in your life. Seriously?
Moderator Warning,
I am closing this thread down, as we do not discuss insurance fraud on this site.
Hi guys,
I was using Pure Nexus for a long time and didn't have an issue with this, but now I'm on stock and my Verizon plan is a legacy plan that doesn't allow me to have WIFI tethering.
What is the best way to do this on Oreo 8.1?
I assume it's using ElementalX Kernel and changing the code to say true, I don't remember the command line
Should I be doing it this way? If so what recovery should I be using with Oreo 8.1?
Do I flash it differently than 7.1 Nuget? (boot to bootloader, boot to RC1 TWRP image, install TWRP zip)
Thanks ahead of time
I'm with him. Coming from a nexus 6 to a pixel 2XL and need pointed in the direction to a ROM or whatever the solution is now to unlock the hotspot on big red. Still on a grandfathered plan. Thanks in advance.
Add net.tethering.noprovisioning=true to your build prop (I use JRummy's Build.prop editor, just add the line to the bottom of the file). I also believe there is a Magisk module for this.
funkybrunk said:
Add net.tethering.noprovisioning=true to your build prop (I use JRummy's Build.prop editor, just add the line to the bottom of the file). I also believe there is a Magisk module for this.
Click to expand...
Click to collapse
This means I need to be rooted... I assumed the same.
What are you running to be rooted on Oreo 8.1? My assumption is it's different than Nuget 7.1 since I had issues doing it the same way.
fsuagentsmith said:
This means I need to be rooted... I assumed the same.
What are you running to be rooted on Oreo 8.1? My assumption is it's different than Nuget 7.1 since I had issues doing it the same way.
Click to expand...
Click to collapse
I haven't had to reroot in a while, Last time was when 8.0 was released. I used the guide here:
https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-systemlessly-root-pixel-xl-t3660324
All subsequent monthly updates and update to 8.1 were applied using flashfire, and root was maintained via everroot (function in flashfire). I honestly don't understand why more people don't use FF to update, it definitely is the easiest. Just make sure to clean themes before updating.
funkybrunk said:
I haven't had to reroot in a while, Last time was when 8.0 was released. I used the guide here:
https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-systemlessly-root-pixel-xl-t3660324
All subsequent monthly updates and update to 8.1 were applied using flashfire, and root was maintained via everroot (function in flashfire). I honestly don't understand why more people don't use FF to update, it definitely is the easiest. Just make sure to clean themes before updating.
Click to expand...
Click to collapse
Thank you, I'm following this post and have now a stupid problem.... my encryption password is incorrect, not sure why. Any idea on where to find out what I used (even though I know what I used when setting up the phone from scratch)
I just did a factory reset and started over to make sure I wasn't going crazy.... still no dice. TWRP is not accepting my encryption password.
Update:
I was told in another thread that this is a known issue with TWRP and Oreo 8.1. The only fix was to remove the PIN after boot and work from there. I have done this and your directions worked. Thanks
Hey, fsuagentsmith
Did you enable hotspot on 8.0/8.1?
Let me know, cause I'm ready to jump off the pure Nexus too!
fsuagentsmith said:
Thank you, I'm following this post and have now a stupid problem.... my encryption password is incorrect, not sure why. Any idea on where to find out what I used (even though I know what I used when setting up the phone from scratch)
I just did a factory reset and started over to make sure I wasn't going crazy.... still no dice. TWRP is not accepting my encryption password.
Update:
I was told in another thread that this is a known issue with TWRP and Oreo 8.1. The only fix was to remove the PIN after boot and work from there. I have done this and your directions worked. Thanks
Click to expand...
Click to collapse
.me said:
Hey, fsuagentsmith
Did you enable hotspot on 8.0/8.1?
Let me know, cause I'm ready to jump off the pure Nexus too!
Click to expand...
Click to collapse
Yes I did.
Sorry I didn't see your post till just now as I don't contribute much on this site. I kind of know what I'm doing but I'm too busy to be a big contributor.
Thanks for asking.
If you mess up your device I'm not responsible, it works for me, and for others. I will help as much as i can, but it is on YOU, the user to follow the prerequisites and read carefully. This zip was created in collaboration with @TxanMoe and myself
This zip can be used to return to the stock rom(for the most part, you'll still have fastboot,root,twrp) as long as you can get into TWRP recovery on the device. It also flashes the modem bands needed for working Sprint LTE(bands 25,26,41, ect.."all the Sprint bands")
Prerequisites:
1. Activate with Sprint first if you intend to use the converted US998 on Sprint!
2. You already crossflashed to US998 if not follow the guide here "Frankenstein method" [https://forum.xda-developers.com/lg...sflashing-t3780969/post76510671#post76510671]
3. You followed the bootloader unlock, root, TWRP "WTF" thread here https://forum.xda-developers.com/lg-v30/how-to/wtf-lg-v30-t3790500
(US998 to LS998) Downloads: (Sprint LS998 system,boot,modem)* MAKE SURE TO FLASH MAGISK, NO-VERITY OPT ENCRYPT, AND RCD DISABLER BEFORE LEAVING RECOVERY!!*
Sprint 20b
https://drive.google.com/file/d/1aQojUcchnEruHwnecfaVGToxZbmj-UX3/view?usp=drivesdk
Sprint 21a(may security patch)
https://drive.google.com/file/d/1JCalyu7mt8DW6wMWbgGViqj0oi9eUSr7/view?usp=drivesdk
*Instructions*:
a. Make a backup in TWRP of system,boot,and data before proceeding!
b. Reboot to TWRP and wipe data (factory data reset)
c. Install the SPRINTLS998.zip (20b or 21a)from TWRP (Do NOT leave recovery yet)
d. Flash Magisk, no verity encrypt, and RCD disabler(you should already have these files if you followed the WTF thread)
e. Reboot
d. Once booted up you need to connect to WiFi. go to settings, update profile and prl. Reboot
quantemplation said:
For anyone who flashes back to Sprint but needs to edit the APNs still, you can type this in command prompt(from PC)
Code:
adb shell
su
am start -n com.lge.hiddenmenu/com.lge.hiddenmenu.ModemProtocol.ModemProtocolMain
Then go to PDP Setting
Then go to APN setting
Click to expand...
Click to collapse
be sure to thank his post here
https://forum.xda-developers.com/showpost.php?p=76633700&postcount=45
JonnyTrulove said:
@JWnSC thanks to the help of some of you great people in this thread I have had the chance to do this conversion twice now. Both times it worked great but I did have to update the APN settings before getting mobile data to work for me. I know you were kind enough to include screenshots of the right APN settings but I just wanted to share that both times I used the ##SCRTN## dialer code to force OTA provisioning and it worked, so I thought you may want to add that option to your first post. Might be a good option for someone that's in hurry to get connected.
Only negative I can think of is that you would not have tethering unless you were subscribed or you manually added the "Dun" provision to the APN later.
Just wanted to share in case you thought it was worth adding to your original post. If not, no biggie. Thanks
Click to expand...
Click to collapse
Special thanks:
@TxanMoe for finding the bootloader exploit and helping me along the way
@ChazzMatt for his in depth Guides and help in this forum
@SGCMarkus for TWRP recovery for this device and all the roms he provides
@quantemplation
@JonnyTrulove
and to any others I may have missed..
Here is a zip for warranty exchange ect...*NOT Recommended* (you will lose root, TWRP)
https://drive.google.com/file/d/19FHVNn6TS5ybdNIziL1nyKPWcIc_RN0t/view?usp=drivesdk
From TWRP(wipe data) install the FACTORYSPRINT.zip reboot device, update prl and profile, reboot, do a system update
It works. I tested it
I'll give this a real-world run-through tomorrow when my new LS998 arrives.
SilverZero said:
I'll give this a real-world run-through tomorrow when my new LS998 arrives.
Click to expand...
Click to collapse
I tested it myself to make sure it works. Working on creating a full back to stock zip for warranty exchange ect.. Will post that after I test and know all is well.
JWnSC said:
I tested it myself to make sure it works. Working on creating a full back to stock zip for warranty exchange ect.. Will post that after I test and know all is well.
Click to expand...
Click to collapse
Yeah...it sucks we need this...sprint not allowing access to kdz is a load of bs...it is much appreciated that we have you helping to support us sprint users...i am looking back at my past lg phones now to see if i can find the process of creating a working kdz...one of the people i think in the g2 or g3 forums actually created a kdz using the untouched signed lg files and it was fully flashable to get back to 100% stock...i don't know if too much has changed since then to do this again...but it would be nice to have for some...me...i won't be doing anything that removes my bootloader unlock and root...but those with warranty may want to have that ability...thanks to all that have contributed to making this a great device...i missed root on a level people outside these forums may never understand
Could you tell me if i could switch out your LS998 bins for h933 ones? also on my dump from lgup can i just change _com6 to .bin ?
cre4per said:
Could you tell me if i could switch out your LS998 bins for h933 ones? also on my dump from lgup can i just change _com6 to .bin ?
Click to expand...
Click to collapse
Right. change "_COM#" to ".bin" should be fine as long as the rsa keys match for the devices you are flashing. Don't flash nougat to Oreo or vice versa
JWnSC said:
Right. change "_ whatever com #" to ".bin" should be fine as long as the rsa keys match for the devices you are flashing. Don't flash nougat to Oreo or vice versa
Click to expand...
Click to collapse
perfect will give it a try, hoping this will let me get volte back on mydevice
JWnSC said:
Here is a zip for warranty exchange ect...*NOT Recommended* (you will lose root, TWRP)
https://drive.google.com/file/d/19FHVNn6TS5ybdNIziL1nyKPWcIc_RN0t/view?usp=drivesdk
From TWRP install the FACTORYSPRINT.zip reboot device, update prl and profile, reboot, do a system update
It works. I tested it
Click to expand...
Click to collapse
Could you lock the bootloader after this? Or will it show an error?
guapinoy said:
Could you lock the bootloader after this? Or will it show an error?
Click to expand...
Click to collapse
Bootloader would still be unlocked but the message after every boot would disappear and you won't be able to enter fastboot. (After you do the system update)
I thought after installing the latest update it would lock the bootloader...it didn't, but it did remove the text after every boot saying to lock bootloader and you won't be able to enter fastboot after. Activating developer options will show the boot is still unlocked. It does change the software info to LS99821a instead of US99820a
To lock the bootloader, you could probably flash the other Sprint zip(without flashing magisk ect..) and just sprint recovery or the factory zip. Reboot to bootloader from twrp and lock it that way. Then do the Sprint system update *I have to do more testing tho I don't recommend doing this until it's tested*
I have followed WTF thread for my Spring LS998. I have also flashed the modem.bin. I have working LTE on US99820a. I went to try and update PRL and Profile but clicking the buttons does nothing at all. Is this common? Also, i noticed that text messaging are received intermittently. They come in, in bunches, but only immediately after I send out a text. has this happened to anyone else?
I'm assuming if i flash the SPRINTLS998.zip, it will correct this issue, but I don't want to if there is no need and there is a fix. I want to try out DotOS, but don't want to carry my texting and MMS issues over from my current U99820a setup.
Omatter4 said:
I have followed WTF thread for my Spring LS998. I have also flashed the modem.bin. I have working LTE on US99820a. I went to try and update PRL and Profile but clicking the buttons does nothing at all. Is this common? Also, i noticed that text messaging are received intermittently. They come in, in bunches, but only immediately after I send out a text. has this happened to anyone else?
I'm assuming if i flash the SPRINTLS998.zip, it will correct this issue, but I don't want to if there is no need and there is a fix. I want to try out DotOS, but don't want to carry my texting and MMS issues over from my current U99820a setup.
Click to expand...
Click to collapse
You can't update profile/ prl on US998 firmware(or at least I couldn't). Backup your setup and try DotOS if you already have working lte. This thread is mainly for users to get lte back. I'm not running the stock Sprint firmware. I switched to stock firmware first to get lte working and switched back to us998 rom.
If you wipe data and flash the SprintLS998.zip you won't have any issues. It already contains the Sprint modem, system, and boot. No need to flash the modem from the other thread.
Will flashing the sprint zip only have bands 25,26 &41?? I'm in an area with band 13 also.. Thanks.
Lurien said:
Will flashing the sprint zip only have bands 25,26 &41?? I'm in an area with band 13 also.. Thanks.
Click to expand...
Click to collapse
???
If you flash the Sprint modem you'll have all the Sprint bands.
It's just the US998 does not have LTE bands 26 & 41. So you have to flash the Sprint modem to get them. If the LS998 normally has LTE band 13, then you'll have that.
Have any of our few sprint users taken latest update and tried to bootloader unlock and root their devices?...just wondering if they actually managed to patch it yet...
jamesd1085 said:
Have any of our few sprint users taken latest update and tried to bootloader unlock and root their devices?...just wondering if they actually managed to patch it yet...
Click to expand...
Click to collapse
I tested the latest update, it installed. I dumped the modem, system and boot from it. I can make a zip from it later. My bootloader was still unlocked tho. I plan to lock it and test..been putting it off, don't want to get stuck on stock haha. I need my phone this week. I'll test this weekend. After the latest update it removed the bootloader warning and I couldn't enter fastboot but the bootloader still showed unlocked under developer options.
JWnSC said:
I tested the latest update, it installed. I dumped the modem, system and boot from it. I can make a zip from it later. My bootloader was still unlocked tho. I plan to lock it and test..been putting it off, don't want to get stuck on stock haha. I need my phone this week. I'll test this weekend. After the latest update it removed the bootloader warning and I couldn't enter fastboot but the bootloader still showed unlocked under developer options.
Click to expand...
Click to collapse
How did you install? Because twrp is there it failed on mine
jamesd1085 said:
How did you install? Because twrp is there it failed on mine
Click to expand...
Click to collapse
I flashed the factory back to stock.zip and went to settings, system update.
Not worth it imo...I was testing the factorysprint.zip to make sure it worked. I can make a flashable zip later(to only include system, modem,boot)..I don't think much changed. Looks like it was just an update to disable fastboot and access to recovery
Omatter4 said:
I have followed WTF thread for my Spring LS998. I have also flashed the modem.bin. I have working LTE on US99820a. I went to try and update PRL and Profile but clicking the buttons does nothing at all. Is this common? Also, i noticed that text messaging are received intermittently. They come in, in bunches, but only immediately after I send out a text. has this happened to anyone else?
I'm assuming if i flash the SPRINTLS998.zip, it will correct this issue, but I don't want to if there is no need and there is a fix. I want to try out DotOS, but don't want to carry my texting and MMS issues over from my current U99820a setup.
Click to expand...
Click to collapse
The first time I tried the profile and PRL updates they took a while to actually launch. Not sure if yours would if you just waited a bit longer (like a minute). I would try that and then the Sprint zip (that's actually more likely to fix your issue).
SilverZero said:
The first time I tried the profile and PRL updates they took a while to actually launch. Not sure if yours would if you just waited a bit longer (like a minute). I would try that and then the Sprint zip (that's actually more likely to fix your issue).
Click to expand...
Click to collapse
I had to connect to wifi when i updated profile...it kept telling me to contact carrier when i tried to update through data connection
Hi there!
I've installed the full OTA SQ1D.211205.016.A4 using Adb sideload but I had have installed another OTA version, specifically SQ1D.211205.016.A1.
I've tried to install the correct version over using adb sideload but it fails because it says is an older version.
How can I install the correct OTA for my Pixel 6 Pro?
Cheers.
sgbmad said:
Hi there!
I've installed the full OTA SQ1D.211205.016.A4 using Adb sideload but I had have installed another OTA version, specifically SQ1D.211205.016.A1.
I've tried to install the correct version over using adb sideload but it fails because it says is an older version.
How can I install the correct OTA for my Pixel 6 Pro?
Cheers.
Click to expand...
Click to collapse
Hmm strange, as I'd done similarly in that I'd installed A1 and needed A4. However I didn't experience an issue with side loading...
Perhaps you could try flashing the full factory image but with the -w removal (research this fully) to avoid data loss, so essentially dirty flashing the full image should help?
cd993 said:
Hmm strange, as I'd done similarly in that I'd installed A1 and needed A4. However I didn't experience an issue with side loading...
Perhaps you could try flashing the full factory image but with the -w removal (research this fully) to avoid data loss, so essentially dirty flashing the full image should help?
Click to expand...
Click to collapse
Thank you for your response cd993. Then, a full factory image flash with full wipe also works, it's true?
sgbmad said:
Thank you for your response cd993. Then, a full factory image flash with full wipe also works, it's true?
Click to expand...
Click to collapse
Sure, a full wipe will indeed clear all data of yours and install the factory image. But I'd try first to remove the line of code in the flash-all.bat file that prevents a data wipe. Plus also there's the factor of keeping root, if you are actually rooted. Let me know if you need any guidance on this though there are lots of info around on these forums
cd993 said:
Sure, a full wipe will indeed clear all data of yours and install the factory image. But I'd try first to remove the line of code in the flash-all.bat file that prevents a data wipe. Plus also there's the factor of keeping root, if you are actually rooted. Let me know if you need any guidance on this though there are lots of info around on these forums
Click to expand...
Click to collapse
Thank you so much,
Well, first of all I would need to know where download the factory image and how can I remove the code in the flash-all.bat. If you show me where can I found that info your help will be very apreciate.
On the other hand, I still have no clear what would be the version I need. I bought the phone at the Google Store in Germany. Also, I do not really do not know what the difference between one version is and if it really is important to put the one that corresponds to you.
sgbmad said:
Thank you so much,
Well, first of all I would need to know where download the factory image and how can I remove the code in the flash-all.bat. If you show me where can I found that info your help will be very apreciate.
Click to expand...
Click to collapse
No problem. The factory image can be found here:
https://developers.google.com/android/images
Are you wanting to root? Forgive me I'm mistaken, though I sense that you are relatively new to this and so I'd suggest following the guide found here:
https://forum.xda-developers.com/t/pixel-6-pro-easy-step-by-step-unlock-root.4361847/
cd993 said:
No problem. The factory image can be found here:
https://developers.google.com/android/images
Are you wanting to root? Forgive me I'm mistaken, though I sense that you are relatively new to this and so I'd suggest following the guide found here:
https://forum.xda-developers.com/t/pixel-6-pro-easy-step-by-step-unlock-root.4361847/
Click to expand...
Click to collapse
Well, I'm not new to this really, but it is my first Pixel. Long time ago I was addicted to flash ROMs
Currently I prefer to use the phone without root.
sgbmad said:
Well, I'm not new to this really, but it is my first Pixel. Long time ago I was addicted to flash ROMs
Currently I prefer to use the phone without root.
Click to expand...
Click to collapse
Great, you'll enjoy this phone!
There's lots of how-to guides on this forum so give them all a good read to benefit your understanding on how the Pixel works and let us know if any questions
cd993 said:
Great, you'll enjoy this phone!
There's lots of how-to guides on this forum so give them all a good read to benefit your understanding on how the Pixel works and let us know if any questions
Click to expand...
Click to collapse
Thank you cd993
I didn't know the Android Flashing Tool for Chrome. There is an option to flash without wipe the device. I'll probably use this tool for flash an image.
sgbmad said:
Thank you cd993
I didn't know the Android Flashing Tool for Chrome. There is an option to flash without wipe the device. I'll probably use this tool for flash an image.
Click to expand...
Click to collapse
Yeah that's a very handy one, especially when not wanting to root.
Have fun!
cd993 said:
Yeah that's a very handy one, especially when not wanting to root.
Have fun!
Click to expand...
Click to collapse
Sure! I think I'll wait for Google says something about this:
[U: Not the wrong build] Latest Google Pixel 6 update is causing network issues in Europe
Some Pixel 6 and Pixel 6 Pro owners in Europe have found that the December update is causing various network issues on their phones.
9to5google.com
Thanks!