Dumping stock ROM?? - Moto G5 Questions & Answers

I am going to get the Moto G5 in a few days, but I want to dump the stock ROM before doing anything in case the custom ROMS don't work the way I want them to or if I mess something up I have something to go back to, and to save myself the trouble of downloading a factory image and the bandwidth it has to use.

There is a video on YouTube won't let me share well there a collection from unlock boot and install twrp and root to unbrick restore factory if you type android doctor on ytube and he has 3 videos for g5 with simply to follow instructions.:good:

stevegtrlmk said:
There is a video on YouTube won't let me share well there a collection from unlock boot and install twrp and root to unbrick restore factory if you type android doctor on ytube and he has 3 videos for g5 with simply to follow instructions.:good:
Click to expand...
Click to collapse
I want a dump:a factory image, except taken straight from my phone and not Lenovo's servers

Related

VS986 13B >>ROOTED<< >>DEBLOATED<< System Image & KDZ DOWNLOAD

VS986 13B >>ROOTED<< >>DEBLOATED<< System Image & KDZ DOWNLOAD
EDIT:Thank you everyone for your support in this thread and to those that donated. This thread actually got me the first donations I've ever received just for tinkering around with phone operating systems; super cool. However, I will no longer be actively taking feature requests or looking for/fixing bugs as I have succumbed to the allure of the V10 and have retired my beloved G4 in less than a year of ownership. I must say the V10 is a gorgeous phone and I absolutely love it. I will continue to frequent this thread and answer any questions and offer any help that I can give to help anyone who may need it. My G4 is now on eBay (until Sunday) so if anyone is interested in a MINT condition Verizon G4 with a LOT of extras, PM me and I will give you the link listing as I believe posting it on here violates xda policy. Now time to explore the V10 forums. Cheers all!
_______________________________________________________________
Fellow Big Red G4 owners,
I am providing for everyone a ROOTED BEBLOATED 13B system image for the Verizon G4. I was on 12A rooted and the OTA to 13B failed so I flashed the stock 12A image that I had laying around, took the OTA successfully, pulled a stock 13B image, used the root injection method found in these forums and flashed back. I can confirm this works!! I'm running it on my phone right now. This system image is also slightly debloated. No, I don't have some fancy program that can open the system image files and pick and choose what I want to delete. All I did was boot my phone on the rooted 13B system and use root explorer and root uninstaller to remove a bunch of stuff that wasn't needed. I made a few other changes as well. Once I was satisfied with my debloating I extracted the system image again and am sharing it with you all! Below is a list of the changes I made as well as the download link. WARNING!!!!!!!! I AM NOT RESPONSIBLE FOR ANYTHING YOU DO WITH YOUR PHONE!! I ASSUME YOU KNOW WHAT YOU'RE DOING IF YOU PROCEED!!!!!!
EDIT 1: I put the img file in a highly compressed rar and 7z archive so the you now only have to download a 1.74 GB file instead of a 4GB+ file.
EDIT 2!! It looks like the official 13B KDZ is FINALLY here thanks to @autoprime !!! Get it HERE.
----------------------------------------------------------------------------
The super user binaries are updated. (meaning you wont get prompted to update them on first boot.)
BusyBox has been pre-installed.
AdAway Host file baked in.
Google Chrome browser has been removed and has been replaced with the stock LG Browser!!
The following system apps have been replaced with those from the new LG V10:
SmartNotice (The best difference is that it's somewhat transparent so it looks WAY cooler.)
Calendar
File Manager
Gallery
Music
^^I was able to get odex files for the above V10 system apps so they don't have to be "optimized" on first boot.^^ Even though the Contacts and Home Launcher app are available from the V10, the Contacts app always force closed no matter what I did and the Home Launcher app would randomly pop up with a "Loading Apps..." pop-up box for about a second when you hit the Home button, so I left both those apps out.
All the VZW bloatware apps have been removed, save for visual voicemail, which I like and actually use. In response to a question I received as to why I removed the CallerNameID app, I use Advanced Calling and CallerNameID, as well as a few other Verizon apps, are not compatible with Advanced Calling according to Verizon's web-site. (See attached screenshot.)
The stock, very annoyingly bright red, could-have-been-a-flashlight-app (lol) Verizon boot animation has been deleted and was replaced with a nice, simple and unobtrusive stock android boot animation. White text on black background. Much better.
The DPI has been set to 560 compared to the stock 640. It will go as low as 540 with no FCs but 560 is just about perfect for me. If you don't like this size, use Textdroider app to change the dpi. NOTE: The only stock app I have found that doesn't work with this lower DPI setting is the LG Voice Recorder. It doesn't work on any DPI setting other than 640 (not even 639). However this app is still included in case you wish to revert back to stock 640 DPI and use it.
-----------------------------------------------------------------------
First boot after a factory reset using this image will be really quick as it will only have to optimize 2 or 3 apps instead of 20+. If you don't like anything, such as the DPI, or visual voicemail, etc, you can change whatever you want since you'll be rooted. This is just how I like my phone.
YOU MUST have already taken the 13B OTA and you will need to be un-rooted to take the OTA. If you are on 11A or 12A rooted, the easiest way to un-root is to use the 13B KDZ to reset your phone to factory un-rooted stock. If you use the KDZ method be sure to backup your personal data as flashing a KDZ will wipe all your data.
You can follow the instructions on how to flash the system image HERE. You will more than likely run into problems if you are on 11A or 12A and try to flash this image without having first updated to 13B using one of the methods listed above (OTA or KDZ), so don't even try. I will not be able to help you get out of that predicament.
You can download the image file HERE!! (RAR Archive format)
Same image in 7z archive format HERE due to several users have MD5 mismatches with the RAR archive. (Needs free 7-Zip archiver program to unpack.)
The MD5 of this file (the IMG file; not the archive files) as it sits on my desktop is 1eca2a177f50f4a092bc5ef0939a99a7
Another thing to remember. Once you flash this image, there is no going back to the state your phone was in before (stock, un-rooted) unless you have a backup of your current system image. Meaning, even if you do a reset to factory defaults from the stock G4 recovery after you've flashed this system image, the defaults it will go back to are those of this system image.
IMPORTANT!! Resetting to factory defaults using the stock G4 recovery after you have flashed this image will NOT un-root your phone. You will have to flash a KDZ file to get back to stock un-rooted. There are instructions on how to extract your current system image HERE before you flash my image.
CREDITS
HUGE thanks, kudos and all credit for the LG Browser goes to @xdabbeb. I was never able to find a new version of the LG Browser that would work on the G4. I asked xdabbeb to see if he could get it working for me and he was gracious enough to do so; thank you!! I became hooked on the LG Browser being a long time fan and user of his ROMs for the Verizon G2.
Thanks to @BySezerSimsek for the V10 system apps. His thread with all the apps is HERE.
I do not take credit for any of the methods used in achieving this. All credits for superuser scripts, injection methods, ported V10 apps, etc goes to the appropriate people. You know who you are. I'm not a developer by any means. I'm just a power user who's not afraid to take the plunge and follow instructions from other very respected users who give all of us the tools we need to make our phones what we want them to be. Without these people, we would have very boring phones. lol. This is the least I can do to contribute back to the community who has helped me out in so many ways.
ENJOY!!!!!!!!!!!!
will give it a try in a few. I dont see clear instructions on how to pull my own system .img for back up purposes
Edit: I guess if i look i would find it. HaHA, to early in the morning to be reading XDA!
Anyone tried this yet?
Sent from my VS986 using Tapatalk
I cant get a good download of this? Is anyone else having success?
madmaverickmatt said:
I cant get a good download of this? Is anyone else having success?
Click to expand...
Click to collapse
Nope, keeps failing. No worries. It's fairly new. Give it some time to work the kinks out.
Sent from my VS986 using Tapatalk
13B? When did that come out? I never even got 12A. Stuck on 11A with screen touch problems.
dvgb173 said:
13B? When did that come out? I never even got 12A. Stuck on 11A with screen touch problems.
Click to expand...
Click to collapse
Within the last 24 hours I believe. I just checked for an update this morning via WiFi and got/installed it.
https://www.reddit.com/r/lgg4/comments/3u3nfo/verizon_update_1124_wifi_fix/
I was on 11A and the 422.1MB download took me straight to 13B .
Any pointers for this VS986 + forum newbie on how to root 13B greatly appreciated .....
divineBliss said:
Within the last 24 hours I believe. I just checked for an update this morning via WiFi and got/installed it.
https://www.reddit.com/r/lgg4/comments/3u3nfo/verizon_update_1124_wifi_fix/
I was on 11A and the 422.1MB download took me straight to 13B .
Any pointers for this VS986 + forum newbie on how to root 13B greatly appreciated .....
Click to expand...
Click to collapse
Again, like the 12a rooted image, there is no coming back from this if something goes wrong. Maybe someone could write a short step-by-step for those of us who want to make a personal backup of our system.img, and I really need to go find the instructions to flash the pre-rooted image since that was so long ago now. Really happy to see this though.
ps.- the download worked fine for me.
I second his advice to create a backup of your current system.img. If you don't you will need to factory reset again when you want to install another OTA, that's what happened to me. No matter what I tried, the OTA would not install on my system.img, even after I unrooted etc. I think I also went too far with moving system apps to the SD card and freezing some apps which prevented it from installing.
To install the OTA on a rooted VS986, is it necessary to flash a stock image (kdz), or can we simply unroot via SuperSU?
dvgb173 said:
To install the OTA on a rooted VS986, is it necessary to flash a stock image (kdz), or can we simply unroot via SuperSU?
Click to expand...
Click to collapse
I'm on 11A and I am wondering this as well. Not sure where to go from here....
rfarrah said:
I'm on 11A and I am wondering this as well. Not sure where to go from here....
Click to expand...
Click to collapse
On 11A as well.
I'm pretty fed up with this phone, so when I get home I'm going to kdz 11a stock with LGUP tool, factory reset, take the 13B OTA, back up the stock system image, then inject root and see how that runs.
Then I'll probably flash the debloated image later this weekend.
dvgb173 said:
To install the OTA on a rooted VS986, is it necessary to flash a stock image (kdz), or can we simply unroot via SuperSU?
Click to expand...
Click to collapse
The update will not install if you are rooted. You can try, it will go through the motions and throw an error.
If you KDZ, make sure you use the KDZ of the version you are on. If you are on 12A and flash the 11A KDZ, you will brick your phone.
The proper way to do this is to BACKUP YOUR SYSTEM.IMG BEFORE YOU DO ANY ROOTING so you can just restore your original system image and restore back to out of the box experience.
If you did NOT backup the system image, then I would recommend looking for a STOCK UNROOTED system image of the same level you are currently running. Push the system.img back onto your phone, take the OTA, BACKUP, and push a rooted system image.
dvgb173 said:
On 11A as well.
I'm pretty fed up with this phone, so when I get home I'm going to kdz 11a stock with LGUP tool, factory reset, take the 13B OTA, back up the stock system image, then inject root and see how that runs.
Then I'll probably flash the debloated image later this weekend.
Click to expand...
Click to collapse
My plan, too, but without the debloated image. Backing everything up now....
I don't have the original stock image. Can anyone provide a link to an 11A stock image?
Sys img Bkup command?
Is this the correct code to run a backup on my 12a unrooted stock, using the LG Root.zip?
dd if=/dev/block/mmcblk0 bs=8192 skip=65536 count=548352 of=/data/media/0/system.img
sefirosu0522 said:
I don't have the original stock image. Can anyone provide a link to an 11A stock image?
Click to expand...
Click to collapse
Here is a link to a kdz:
http://storagecow.eu/index.php?dir=Xda/LG+G4/Verizon+VS986/
rfarrah said:
Here is a link to a kdz:
http://storagecow.eu/index.php?dir=Xda/LG+G4/Verizon+VS986/
Click to expand...
Click to collapse
Thanks. Maybe I mistyped. What I meant is, the stock image we pull off when we first root. I deleted mine. Is KDZ the only way to go or are the two essentially the same?
usr folder
Hello Everyone,
I was wondering if anyone could pull there /system/usr folder from 13 and upload it?
I'd like to tryout the new idc to see if that resolves the last of my touch issues on 11A
Thanks in advance,
~Eugene
player911 said:
<snip>...If you did NOT backup the system image, then I would recommend looking for a STOCK UNROOTED system image of the same level you are currently running. Push the system.img back onto your phone, take the OTA, BACKUP, and push a rooted system image.
Click to expand...
Click to collapse
I don't remember backing up system image as part of the Low Effort Root procedure. I will go check, but if it wasn't in the steps, I didnt do it.
If it was, I should have it somewhere.
I do have the original 11a stock rooted image saved. But that won't do me any good.
How is the system image backup accomplished without root? It is probably in the Inject Root thread.

Le S3 factory image 5.8.020S directly from LeEco!

Here it is as promised. This is only for the x522 Le S3 (Le 2 variants for US Market)! Download here: http://www.mediafire.com/file/55m4m5of3uvmef5/S2_X522-NA-OP-IFXNAOP5802012141S-5.8.020S.zip
I couldn't figure how to install this aside from using TWRP so this is what I did from stock unrooted 5.8.019S (which I had root prior, then restored via a back up from someone but could not take OTA):
1. adb reboot bootloader
2. fastboot oem unlock-go
3. fastboot boot twrp.img (has to be the chinese ydss twrp, the official twrp will not let you flash the stock image). Chose read-only instead of swipe to allow modification.
4. wipe factory reset, and format data.
5. go to mount, and enable mtp, and drag the stock image into the root directory of the phone.
6. go to install, and flash the stock rom. This will take a bit of time 5-10 minute or so, the progress bar doesn't move properly so don't panic if you see it "freezing" up.
7. once it is completed, it will tell you it's done. Before reboot, wipe dalvik and cache only, then reboot system.
You should be on stock recovery from this image, and unrooted. In theory, this should still allow you to take OTA. I might be wrong though, I don't know how LeEco does their firmwares and checks. I hope a mod on here make a forum for the Le S3 so we don't keep posting in Le 2 forum. Hopefully someone can cook this factory image to a nice working rom that we can flash, and hopefully figure a way so that we can use flashfire app to update ota even when rooted.
Enjoy It took me a pretty long time to drag this out of LeEco. Please rep if I helped ya'll.
xterminater07 said:
Here it is as promised. This is only for the x522 Le S3 (Le 2 variants for US Market)! Download here: http://www.mediafire.com/file/55m4m5of3uvmef5/S2_X522-NA-OP-IFXNAOP5802012141S-5.8.020S.zip
I couldn't figure how to install this aside from using TWRP so this is what I did from stock unrooted 5.8.019S (which I had root prior, then restored via a back up from someone but could not take OTA):
1. adb reboot bootloader
2. fastboot oem unlock-go
3. fastboot boot twrp.img (has to be the chinese ydss twrp, the official twrp will not let you flash the stock image). Chose read-only instead of swipe to allow modification.
4. wipe factory reset, and format data.
5. go to mount, and enable mtp, and drag the stock image into the root directory of the phone.
6. go to install, and flash the stock rom. This will take a bit of time 5-10 minute or so, the progress bar doesn't move properly so don't panic if you see it "freezing" up.
7. once it is completed, it will tell you it's done. Before reboot, wipe dalvik and cache only, then reboot system.
You should be on stock recovery from this image, and unrooted. In theory, this should still allow you to take OTA. I might be wrong though, I don't know how LeEco does their firmwares and checks. I hope a mod on here make a forum for the Le S3 so we don't keep posting in Le 2 forum. Hopefully someone can cook this factory image to a nice working rom that we can flash, and hopefully figure a way so that we can use flashfire app to update ota even when rooted.
Enjoy It took me a pretty long time to drag this out of LeEco. Please rep if I helped ya'll.
Click to expand...
Click to collapse
I use this with a Thumb Drive, makes life easier
https://www.amazon.com/dp/B017XARUKC/ref=cfb_at_prodpg
How will that help in my post? Which part can it cut down?
Thanks a lot. Worked like a charm and I'm now on 5.8.020s. How did you obtain the file?
xterminater07 said:
How will that help in my post? Which part can it cut down?
Click to expand...
Click to collapse
just for people who are not sure of the mtp part in step 5..
its not a necessary item, i just find it quicker to write files to thumb drive while i am setting up into TWRP,
might not need to format data then either,as only doing that to write file to phone
Its just my personal preference , not a must have item
But thankyou again for your persistence with LeEco and getting this file..
For whats its worth, i restrored 19s , let it run a few mins, then went back to TWRP and without wiping data or anything else and leaving it read only i let the 20s file install, and all is running well..
As of yet i have not tried to load TWRP on the 20s system, but having the full backup will give us OTA's hopefully
Y even use 19s when the image is 20s. The problem with restoring is the backup was done by read and write twrp. This kills ota righ?
They also gave me 19s image but I'm like why use it. Oh by the way guys, LeEco's camera app sucks balls. I ended up using "A better camera unlocked" app and it's ten times better! HDR is amazing but it takes about 1-2 second so hold your hands still! Hehe... If anyone got better camera reccommendation let us know. I tried open camera as well, not good.
I don't know if you can find it and if you do, I have always liked the snapdragon camera.
I am lost, can someone point me were the Chinese TWRP is located, I currently have the official version on the phone.
Charles Broccoli said:
I don't know if you can find it and if you do, I have always liked the snapdragon camera.
I am lost, can someone point me were the Chinese TWRP is located, I currently have the official version on the phone.
Click to expand...
Click to collapse
Snapdragon camera 2.2 was ported for all marshmallow but it requires flashing via twrp. I will try that later in read only mode. The chinese twrp is here https://mega.nz/#!XhYznTzA!z-XfbrIaVrKWAC-OaW86NFj1EAvZs68GmSchedQ-vhI.
Also, after reading around I found out the Le S3 has the exact camera as the Le 2 instead of the Le pro 3 . It uses the omnivision ov 16880, which is decent but nowhere near the sony imx298 which is seen on the one plus 3. LeEco has confirmed to enable camera2api in their EUI 6.0 coming in 2017. However, can any developer tell us how is this any difference from us rooting the device ourselves and enabling camera2api via build.prop? Or does enabling it, just basically turns it on but if LeEco has not build it to their rom, it won't work right?
Will this work on le 2 X526?
Sent from my SM-G935F using Tapatalk
xterminater07 said:
Snapdragon camera 2.2 was ported for all marshmallow but it requires flashing via twrp. I will try that later in read only mode. The chinese twrp is here https://mega.nz/#!XhYznTzA!z-XfbrIaVrKWAC-OaW86NFj1EAvZs68GmSchedQ-vhI.
Also, after reading around I found out the Le S3 has the exact camera as the Le 2 instead of the Le pro 3 . It uses the omnivision ov 16880, which is decent but nowhere near the sony imx298 which is seen on the one plus 3. LeEco has confirmed to enable camera2api in their EUI 6.0 coming in 2017. However, can any developer tell us how is this any difference from us rooting the device ourselves and enabling camera2api via build.prop? Or does enabling it, just basically turns it on but if LeEco has not build it to their rom, it won't work right?
Click to expand...
Click to collapse
You can enable camera api 2 on eui I'm using it by enbling it through build.prop
It works great
Charles Broccoli said:
I don't know if you can find it and if you do, I have always liked the snapdragon camera.
I am lost, can someone point me were the Chinese TWRP is located, I currently have the official version on the phone.
Click to expand...
Click to collapse
rohansalunkhe71 said:
You can enable camera api 2 on eui I'm using it by enbling it through build.prop
It works great
Click to expand...
Click to collapse
Right, but does that improve picture quality or enabling it just allow you to do manual mode while the pic still look crappy? I had a le max 2, and while the imx230 is a good sensor, eui software sucks compared to using a third party camera app.
xterminater07 said:
Right, but does that improve picture quality or enabling it just allow you to do manual mode while the pic still look crappy? I had a le max 2, and while the imx230 is a good sensor, eui software sucks compared to using a third party camera app.
Click to expand...
Click to collapse
well personally I prefer raw image editing thats why I enabled camera api 2.
Yes image quality is still ****y but due to manual settings it enables to take good images, focus on closer objects. But it doesn't give image quality as sony imx230 sensor.
rohansalunkhe71 said:
well personally I prefer raw image editing thats why I enabled camera api 2.
Yes image quality is still ****y but due to manual settings it enables to take good images, focus on closer objects. But it doesn't give image quality as sony imx230 sensor.
Click to expand...
Click to collapse
That's what I thought. That was my concern bc I want to know if doing camera2api in build prop just enables it or does it actually makes it useless since leeco algorithm is shiet.
xterminater07 said:
Here it is as promised. This is only for the x522 Le S3 (Le 2 variants for US Market)! Download here: http://www.mediafire.com/file/55m4m5of3uvmef5/S2_X522-NA-OP-IFXNAOP5802012141S-5.8.020S.zip
I couldn't figure how to install this aside from using TWRP so this is what I did from stock unrooted 5.8.019S (which I had root prior, then restored via a back up from someone but could not take OTA):
1. adb reboot bootloader
2. fastboot oem unlock-go
3. fastboot boot twrp.img (has to be the chinese ydss twrp, the official twrp will not let you flash the stock image). Chose read-only instead of swipe to allow modification.
4. wipe factory reset, and format data.
5. go to mount, and enable mtp, and drag the stock image into the root directory of the phone.
6. go to install, and flash the stock rom. This will take a bit of time 5-10 minute or so, the progress bar doesn't move properly so don't panic if you see it "freezing" up.
7. once it is completed, it will tell you it's done. Before reboot, wipe dalvik and cache only, then reboot system.
You should be on stock recovery from this image, and unrooted. In theory, this should still allow you to take OTA. I might be wrong though, I don't know how LeEco does their firmwares and checks. I hope a mod on here make a forum for the Le S3 so we don't keep posting in Le 2 forum. Hopefully someone can cook this factory image to a nice working rom that we can flash, and hopefully figure a way so that we can use flashfire app to update ota even when rooted.
Enjoy It took me a pretty long time to drag this out of LeEco. Please rep if I helped ya'll.
Click to expand...
Click to collapse
xterminater07 said:
Y even use 19s when the image is 20s. The problem with restoring is the backup was done by read and write twrp. This kills ota righ?
Click to expand...
Click to collapse
Its not the fact read/write was used in TWRP, as i also when i got my replacement phone used it read only and still no OTA was taking...
I put 19s on just to see if 20s would go on without all the cleaning of the encrypted data and the such, cuts down on a step or two maybe..
hey any chance you can throw 19s full rom up somewhere..id like to play and try find out what will and wont work when using twrp and ota's
Before I get started, I had originally installed the official TWRP.img as recovery instead of only booting from the twrp.img.
Should I first install the original stock recovery.img before getting started or will the act of flashing the stock rom overwrite the installed twrp.img?
I think I already know to first install the stock recovery.img then just boot into the Chinese twrp.img afterwards to flash the stock rom or will it matter?
I am also on 18s firmware, I don't think it would matter to flash it straight to 20s
You should be OK to just install it .I believe it will ask you if you want to allow TWRP to replace recovery at the end when you go to reboot system and you say no....The ROM should install le eco recovery ...
@codeworkx can you help us identified why OTA does not work even when backing up from twrp? I dont have the 19s full image as leeco only gave me the latest one.
xterminater07 said:
@codeworkx can you help us identified why OTA does not work even when backing up from twrp? I dont have the 19s full image as leeco only gave me the latest one.
Click to expand...
Click to collapse
I thought in earlier post you said they gave you 19s also...Would of been a useful tool
---------- Post added at 08:29 PM ---------- Previous post was at 08:06 PM ----------
xterminater07 said:
They also gave me 19s image but I'm like why use it. Oh by the way guys, LeEco's camera app sucks balls. I ended up using "A better camera unlocked" app and it's ten times better! HDR is amazing but it takes about 1-2 second so hold your hands still! Hehe... If anyone got better camera reccommendation let us know. I tried open camera as well, not good.
Click to expand...
Click to collapse
here i thought ya got 19s also

Terrible video quality. How do I fix it?

The camera is good. as soon as I switch the video however, the quality is terrible (yes I tried 1080 and 4k, and for 1080 trying both 30fps and 60fps). For both pictures and video, there is a lot of frame skipping. I tried third party apps. the video quality is good in other apps, but still has frame skipping and even the image freezing (not the phone itself, only the viewfinder freezes) for a couple of seconds. also, the lack of video stabilization in third party apps make it so shaky that it's quite unpleasant if I move at all. troubleshooting steps google gave me didnt work, as well as factory resetting and flashing the factory image again. I was offered a replacement but I already replaced my phone for camera issues. Help!
I am having battery problems as well, but i should probably make a separate thread for that.
Well, if you haven't already, try a factory reset. It can be a pain but it may fix both issues. Also, are you stock, rooted, etc.?
Sent from my Pixel XL using Tapatalk
ahent said:
Well, if you haven't already, try a factory reset. It can be a pain but it may fix both issues. Also, are you stock, rooted, etc.?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I tried that, and all troubleshooting steps google gave me, as well as flashing the factory image (multiple times but that was to update my rooted phone).
My phone is stock. I'm not rooting anymore because I'm tired of all my data being wiped so I can update (If you have any steps I can follow to update a rooted pixel without losing any data/settings that would be infinitely appreciated!). I don't want a custom rom, loving stock on this phone.
Abigailrup said:
as soon as I switch the video however, the quality is terrible (yes I tried 1080 and 4k, and for 1080 trying both 30fps and 60fps). For both pictures and video, there is a lot of frame skipping.
Click to expand...
Click to collapse
If you re-flashed the factory firmware and took a video and used the built-in app to view the video and see lots of frames missing/skipping, then I'd send the phone back for warranty.
But only if you tried this BEFORE installing all your third party apps that can sometimes screw with other things.
Abigailrup said:
I tried that, and all troubleshooting steps google gave me, as well as flashing the factory image (multiple times but that was to update my rooted phone).
My phone is stock. I'm not rooting anymore because I'm tired of all my data being wiped so I can update (If you have any steps I can follow to update a rooted pixel without losing any data/settings that would be infinitely appreciated!). I don't want a custom rom, loving stock on this phone.
Click to expand...
Click to collapse
You can update without losing all your stuff. Download the latest factory image that you need to update to. Extract the archive and find the flash_all (.Sh for Linux, .Bat for Windows) right click it and open with notepad. Down near the bottom you'll see a line that says something like "fastboot -w update blah blah". Remove the -w parameter so instead it looks like "fastboot update blah blah". Now when you run it to flash the newest image, it won't wipe any data and everything will be as you left it, just like you took an OTA.
As far as the camera thing goes, grab a camera APK from a lineage rom, from what I've read it takes use of our image stabilization however you loose HDR.
noidea24 said:
You can update without losing all your stuff. Download the latest factory image that you need to update to. Extract the archive and find the flash_all (.Sh for Linux, .Bat for Windows) right click it and open with notepad. Down near the bottom you'll see a line that says something like "fastboot -w update blah blah". Remove the -w parameter so instead it looks like "fastboot update blah blah". Now when you run it to flash the newest image, it won't wipe any data and everything will be as you left it, just like you took an OTA.
As far as the camera thing goes, grab a camera APK from a lineage rom, from what I've read it takes use of our image stabilization however you loose HDR.
Click to expand...
Click to collapse
Thanks so much!!
And okay. I can't find the lineageOS camera apk for the pixel though. Where is it at?
Somewhere in the questions subsection there is a thread named "lineage 14" or something similar. They are trying out lineage and you can find links a few pages in.
If you want to see if any of your installed apps are responsible for any kind of bug, you can boot into safe mode - https://support.google.com/pixelphone/answer/2852139?hl=en
nabbed said:
If you want to see if any of your installed apps are responsible for any kind of bug, you can boot into safe mode - https://support.google.com/pixelphone/answer/2852139?hl=en
Click to expand...
Click to collapse
I did try that, the camera app is still just as bad.
noidea24 said:
Somewhere in the questions subsection there is a thread named "lineage 14" or something similar. They are trying out lineage and you can find links a few pages in.
Click to expand...
Click to collapse
There is no lineage camera apk in there. I just spent a long time going through every single page..

A beginner and a Google pixel C

Hello,
I am looking, as a perfect beginner, to know what the root of my Google pixel C will allow. I encounter one or two problems (screen that freezes during heavy tasks, connections that breaks) on this tablet like many owners of this one and I have heard that the installation of a new system based on android can cancel these problems. So I would like to be enlightened on this subject! What are the best software to install? How to proceed (is it simple after all )? What can this bring?
That's it, I'd like to learn something. Thank you in advance for your answers
LineageOS 15.1 is a great advantage in contrast to the stock ROM (more settings, more smooth, more updates).
You have first to unlock the bootloader (developer settings), install TWRP and then flash lineageos, GApps, Vendor Image.
For detailed instruction search in this forum.
braunie said:
LineageOS 15.1 is a great advantage in contrast to the stock ROM (more settings, more smooth, more updates).
You have first to unlock the bootloader (developer settings), install TWRP and then flash lineageos, GApps, Vendor Image.
For detailed instruction search in this forum.
Click to expand...
Click to collapse
All right, very well, thank you. I still had some questions ?.
1. Can this improve performance as well? For example in games ?
2. what are the risks?
3. what does the term "Flash" mean?
4.Can I, if I wish, go back to the original version without any problem?
5. Is it complex to update lineageOS where can we do it from the system settings simply?
Thank you for your answers that's awesome!
I forgot to ask if:
Do we need a computer necessarily?
Is root required?
Sorry, there are a lot of questions. I hope you will take the time to answer ?
Hawkeye5 said:
All right, very well, thank you. I still had some questions .
1. Can this improve performance as well? For example in games ?
2. what are the risks?
3. what does the term "Flash" mean?
4.Can I, if I wish, go back to the original version without any problem?
5. Is it complex to update lineageOS where can we do it from the system settings simply?
Thank you for your answers that's awesome!
Click to expand...
Click to collapse
1. I'm not playing on my Pixel C, but LineageOS is more smooth than the stock ROM on my Pixel C
2. The risk is that you maybe brick your tablet
3. Flashing means to install an image (new Firmware) on your device
4. Yes, it is possibel
5. If you've never done this, it is difficult to do that, I've done this a few times, but it is every time a challange for me, so I would suggest you: let it be or find someone with expirience!!!
braunie said:
1. I'm not playing on my Pixel C, but LineageOS is more smooth than the stock ROM on my Pixel C
2. The risk is that you maybe brick your tablet
3. Flashing means to install an image (new Firmware) on your device
4. Yes, it is possibel
5. If you've never done this, it is difficult to do that, I've done this a few times, but it is every time a challange for me, so I would suggest you: let it be or find someone with expirience!!!
Click to expand...
Click to collapse
Thank you! I'm going to try to install lineageOS 15.1. In the meantime, I've been looking for a lot of tutorials so I think it should be fine. Anyway, just follow the instructions on the lineageOS website for installation and everything will be fine I think. What would you advise me as a topic on the forum about the advantages and inconveniences of lineageOS? Where can I find the vendor.img files specific for pixel C?
You might want to have a look at this topic
https://forum.xda-developers.com/pixel-c/help/pixel-c-oreo-8-1-unlock-bootloader-t3849422
starting at message 19 where I outline what is required to root and flash a ROM image.
I use the example of a Google Factory Image but Lineage will do.
m+a+r+k said:
You might want to have a look at this topic
https://forum.xda-developers.com/pixel-c/help/pixel-c-oreo-8-1-unlock-bootloader-t3849422
starting at message 19 where I outline what is required to root and flash a ROM image.
I use the example of a Google Factory Image but Lineage will do.
Click to expand...
Click to collapse
Where can I find vendor.img for lineageOS?: o
Not a clue, sorry.
Hawkeye5 said:
Thank you! I'm going to try to install lineageOS 15.1. In the meantime, I've been looking for a lot of tutorials so I think it should be fine. Anyway, just follow the instructions on the lineageOS website for installation and everything will be fine I think. What would you advise me as a topic on the forum about the advantages and inconveniences of lineageOS? Where can I find the vendor.img files specific for pixel C?
Click to expand...
Click to collapse
The vendor.img is a part of the factory image. The factury image is accessible here:
https://developers.google.com/android/images
Scroll down to "ryu" for Pixel C and download the latest factory image, unzip it and you'll find the vendor.img.
Alternative here is a link to the latest vendor.img on my google drive:
https://drive.google.com/file/d/1ptXKX_QGIb0EJRaBzap1fWYM5N507khL/view?usp=sharing
Good luck!
braunie said:
The vendor.img is a part of the factory image. The factury image is accessible here:
https://developers.google.com/android/images
Scroll down to "ryu" for Pixel C and download the latest factory image, unzip it and you'll find the vendor.img.
Alternative here is a link to the latest vendor.img on my google drive:
https://drive.google.com/file/d/1ptXKX_QGIb0EJRaBzap1fWYM5N507khL/view?usp=sharing
Good luck!
Click to expand...
Click to collapse
After all, is vendor.img really useful or is it optional?
Well, finally I flashed an Android 7.1.2 factory rom to start. And frankly, I did well. I'm happy with myself. It's true that I wanted to have lineageos at the base but I was a little afraid of the result. But finally it's perfecto with nougat 7.1.2. It's my first time.
Hello. Well, in the end I have a big problem with the c pixel. I followed all the steps on the Google site. So install adj and Fastboot with their drivers. Then double click on Flash_all.bat. All went well it rebooted and I can use the tablet without any problem. The only thing I didn't do was lock the bootloader because I thought it would wait until tomorrow. So everything works fine I have some features for you then I test the restart and there is a big mistake. I see the message: bootloader is unlocked and os verification is off the device continues booting in 30 second. Then a high-pitched beep and the Google logo appears but never changes. So nothing left and blocked on this logo. And did I do something stupid, did I brick it. I'm lost ?
It has now turned into a bootloop I think because it only restarts up to the four small circles that rotate the Google logo and then turns off and on again. I can still go to Recovery.
Hawkeye5 said:
It has now turned into a bootloop I think because it only restarts up to the four small circles that rotate the Google logo and then turns off and on again. I can still go to Recovery.
Click to expand...
Click to collapse
I had a similar issue. The cause seems to be TWRP-Recovery. Could you enter TWRP-Recovery mode?
If so; you have to flash lineageos, vendor.img and gapps by sideload. This is an option in TWRP to flash from your PC direct in TWRP. (Option: Advanced - ADB Sideload.)
This may be helpful:
https://android.gadgethacks.com/how-to/sideload-flashable-zips-android-with-twrp-0176529/
braunie said:
I had a similar issue. The cause seems to be TWRP-Recovery. Could you enter TWRP-Recovery mode?
If so; you have to flash lineageos, vendor.img and gapps by sideload. This is an option in TWRP to flash from your PC direct in TWRP. (Option: Advanced - ADB Sideload.)
This may be helpful:
https://android.gadgethacks.com/how-to/sideload-flashable-zips-android-with-twrp-0176529/
Click to expand...
Click to collapse
I created another post to better explain my problem. I also mentioned that I had managed to solve it but I still thank you for offering your help I flashed a Factory rom so I didn't have to install twrp. Actually I didn't know that I had to lock the bootloader immediately after flashing a Factory rom. Unlike custom rom. So I almost bricked my tablet at 400€
But it's good that you told me, though. ADB sideload is used to install the system and the Gapps at the same time, for example?
You do not have to lock the bootloader after installing a ROM or flashing a factory image.
I flash the factory image every month after a security update and have never locked the bootloader.
m+a+r+k said:
You do not have to lock the bootloader after installing a ROM or flashing a factory image.
I flash the factory image every month after a security update and have never locked the bootloader.
Click to expand...
Click to collapse
But you can still restart or turn off your device without any problem? It was when I restarted that I had the bootloop problem.
This is what is said on the Google developers website: "Once the script is finished, your device restarts. You should now lock the bootloader for security reasons:
Restart the device in Fastboot mode, as described above.
Execute:
fastboot flashing lock
or, for older devices, run:
fastboot oem lock
Locking the bootloader will erase data on some devices. After locking the bootloader, if you want the device to flash again, you must run fastboot oem unlock again, which will erase the data."
Hawkeye5 said:
But you can still restart or turn off your device without any problem? It was when I restarted that I had the bootloop problem.
This is what is said on the Google developers website: "Once the script is finished, your device restarts. You should now lock the bootloader for security reasons:
Restart the device in Fastboot mode, as described above.
Execute:
fastboot flashing lock
or, for older devices, run:
fastboot oem lock
Locking the bootloader will erase data on some devices. After locking the bootloader, if you want the device to flash again, you must run fastboot oem unlock again, which will erase the data."
Click to expand...
Click to collapse
Yes, of course I can restart and switch off without problems.
The problem with locking the bootloader again is, as Google says, you lose your data when you next want to install a ROM of flash a factory image.
The state of your bootloader isn't what is causing the bootloop.
Hawkeye5 said:
I created another post to better explain my problem. I also mentioned that I had managed to solve it but I still thank you for offering your help I flashed a Factory rom so I didn't have to install twrp. Actually I didn't know that I had to lock the bootloader immediately after flashing a Factory rom. Unlike custom rom. So I almost bricked my tablet at 400€
But it's good that you told me, though. ADB sideload is used to install the system and the Gapps at the same time, for example?
Click to expand...
Click to collapse
You could install system image, vendor image and gapps by sideload flashing in one session.

Re-Root? Possible partition messup, Lost root now stuck in fastboot

Hello, Sorry to bug you guys...I read multiple different fourms/how2s and I guess I'm a little mixed at what i should do. I Have the oneplus 7t (hd1505) with android 11 rooted, and after that I installed NikGapps after I had it rooted, then flashed nethunter. Was in the terminal as root, all was well..I believe It rebooted and would'nt boot to rom so i went and re'did magisk, may have used a different patched magisk? but now is stuck fastboot. Cant get it to boot.
Sorry for the maybes but I had brain surgry and my memories not the best. Everything was going fine so I didn't document things like normal. Anyways, Is there a program that helps with thiss? MSM somthing? or could anyone please point me in to a nice how2 or some quality links to assist? I really apprricate it, normally I'd just test till I get it, but I think I may be at a point where I could really mess it up.
5k1tz0 said:
Hello, Sorry to bug you guys...I read multiple different fourms/how2s and I guess I'm a little mixed at what i should do. I Have the oneplus 7t (hd1505) with android 11 rooted, and after that I installed NikGapps after I had it rooted, then flashed nethunter. Was in the terminal as root, all was well..I believe It rebooted and would'nt boot to rom so i went and re'did magisk, may have used a different patched magisk? but now is stuck fastboot. Cant get it to boot.
Sorry for the maybes but I had brain surgry and my memories not the best. Everything was going fine so I didn't document things like normal. Anyways, Is there a program that helps with thiss? MSM somthing? or could anyone please point me in to a nice how2 or some quality links to assist? I really apprricate it, normally I'd just test till I get it, but I think I may be at a point where I could really mess it up.
Click to expand...
Click to collapse
If you don't care about data then use msm tools to factory restore. Or you can flash boot image of the rom you were using (unpatched) in fastboot mode itself.
No need to keep data, I'd prefer to wipe device and start fresh instead of getting stuck on the concept of A/B partitions. I get the CMD getvar, but I'm not sure if i flashed the lineage OS to one or both...at 1 point i think i was booted in A, now its saying B. I got overeager and downloaded multiple ROMs and not sure which one worked. In the past I usually downloaded a few and the first one to work I used. Not smart...I know. If I wanted to wipe all and start fresh with gaspps and root, where/how should I do that? I can't just fasatboot oem unlock , could I? Would you recommend stock OS? Lineage? Thanks for your help BTW.
5k1tz0 said:
No need to keep data, I'd prefer to wipe device and start fresh instead of getting stuck on the concept of A/B partitions. I get the CMD getvar, but I'm not sure if i flashed the lineage OS to one or both...at 1 point i think i was booted in A, now its saying B. I got overeager and downloaded multiple ROMs and not sure which one worked. In the past I usually downloaded a few and the first one to work I used. Not smart...I know. If I wanted to wipe all and start fresh with gaspps and root, where/how should I do that? I can't just fasatboot oem unlock , could I? Would you recommend stock OS? Lineage? Thanks for your help BTW.
Click to expand...
Click to collapse
Go to this thread for MSM Tool download and instructions: Unbrick tool to restore your device to OxygenOS

Categories

Resources