Database Develop

HOW TO : Flash 4.3 on rooted stock 4.2.2

If you have a stock 4.2.2 with root and clockwork mod recovery, it can be updated to 4.3, you will keep CWM recovery but lose root so here's what I did.
You need :
- Nexus 4
- 4.2.2 firmware (JDQ39)
- root with superSU
- Clockwork Mod Recovery
Download update JWR66V from JDQ39
Copy the zip file in the folder of your choice.
Shut down the Nexus 4
Boot into CWM Recovery : hold Volume Down and press Power, in the menu with the green "Start" choose "Recovery mode" with the volume and select with power, it will reboot in CWM Recovery
Then in CWM Recovery :
- Install Zip
- Choose zip from sdcard
- 0/
- go in the folder you copied the update and select it
- select Yes and wait
- go back and reboot
- on reboot it will ask to keep recovery and root, say Yes both. But saying no to keep root won't keep root...
So after a long reboot, the Nexus 4 is updated to 4.3, CWM recovery still here but no root binary.
Download the file on this link from SuperSU creator : Chainfire.
Flash it the same way as the update but when it will ask for keeping recovery, say No.
After reboot, you now have a Nexus 4 with 4.3 (JWR66V), root and CWM recovery.
On Google Play, SuperSU is updated, currently version 1.44. When launching SuperSU, it will ask to update SU Binary, choose to update normally.
This should work with TWRP but I don't have it.
I hope this will help.

I want to do a fresh install using the factory images for 4.3 (bootloader, radio, recovery etc)
Once I do that, can I just reinstall CWM then SuperSu to root just like I did using 4.2?

ohhdavid said:
I want to do a fresh install using the factory images for 4.3 (bootloader, radio, recovery etc)
Once I do that, can I just reinstall CWM then SuperSu to root just like I did using 4.2?
Click to expand...
Click to collapse
just use the nexus4 tool kit and use the factory images. Simple and quick

jboogie3 said:
just use the nexus4 tool kit and use the factory images. Simple and quick
Click to expand...
Click to collapse
I'll look into it, however, I usually prefer to do as close to stock install as possible with bare minimum 3rd party modification which is why I usually install factory images and then flash Su through cwm
Sent from my Nexus 4

ohhdavid said:
I'll look into it, however, I usually prefer to do as close to stock install as possible with bare minimum 3rd party modification which is why I usually install factory images and then flash Su through cwm
Sent from my Nexus 4
Click to expand...
Click to collapse
the toolkit just fastboot flashes the images for you... thats complete stock. then you can flash a custom recovery, then install su.

Thanks to the OP :thumbup: works a treat
Sent from my Nexus 4 using xda app-developers app

Le_Zouave said:
If you have a stock 4.2.2 with root and clockwork mod recovery, it can be updated to 4.3, you will keep CWM recovery but lose root so here's what I did.
You need :
- Nexus 4
- 4.2.2 firmware (JDQ39)
- root with superSU
- Clockwork Mod Recovery
Download update JWR66V from JDQ39
Copy the zip file in the folder of your choice.
Shut down the Nexus 4
Boot into CWM Recovery : hold Volume Down and press Power, in the menu with the green "Start" choose "Recovery mode" with the volume and select with power, it will reboot in CWM Recovery
Then in CWM Recovery :
- Install Zip
- Choose zip from sdcard
- 0/
- go in the folder you copied the update and select it
- select Yes and wait
- go back and reboot
- on reboot it will ask to keep recovery and root, say Yes both. But saying no to keep root won't keep root...
So after a long reboot, the Nexus 4 is updated to 4.3, CWM recovery still here but no root binary.
Download the file on this link from SuperSU creator : Chainfire.
Flash it the same way as the update but when it will ask for keeping recovery, say No.
After reboot, you now have a Nexus 4 with 4.3 (JWR66V), root and CWM recovery.
This should work with TWRP but I don't have it.
I hope this will help.
Click to expand...
Click to collapse
Awesome thanks, will try this later.

does this method erase everything on your phone?

clusterchuck said:
does this method erase everything on your phone?
Click to expand...
Click to collapse
No, nothing is erased and it even keep the custom recovery.
The first part is what I used to update to 4.2.2 and keep root and custom recovery. But with 4.3 update, root method seems to have changed, that's why I wrote this post.

Le_Zouave said:
If you have a stock 4.2.2 with root and clockwork mod recovery, it can be updated to 4.3, you will keep CWM recovery but lose root so here's what I did.
You need :
- Nexus 4
- 4.2.2 firmware (JDQ39)
- root with superSU
- Clockwork Mod Recovery
Download update JWR66V from JDQ39
Copy the zip file in the folder of your choice.
Shut down the Nexus 4
Boot into CWM Recovery : hold Volume Down and press Power, in the menu with the green "Start" choose "Recovery mode" with the volume and select with power, it will reboot in CWM Recovery
Then in CWM Recovery :
- Install Zip
- Choose zip from sdcard
- 0/
- go in the folder you copied the update and select it
- select Yes and wait
- go back and reboot
- on reboot it will ask to keep recovery and root, say Yes both. But saying no to keep root won't keep root...
So after a long reboot, the Nexus 4 is updated to 4.3, CWM recovery still here but no root binary.
Download the file on this link from SuperSU creator : Chainfire.
Flash it the same way as the update but when it will ask for keeping recovery, say No.
After reboot, you now have a Nexus 4 with 4.3 (JWR66V), root and CWM recovery.
This should work with TWRP but I don't have it.
I hope this will help.
Click to expand...
Click to collapse
There's a new su zip v1.43 it had just been released
From my BLACKED OUT N4

i got an error when attempting to install in cwm, something regarding a no file_context.
edit: it says error /sdcard/0/ ebc... (status 7)

Worked fine for me
Thanks! This worked perfectly for me. Haven't run into any trouble yet.

I missed "Flash it the same way as the update but when it will ask for keeping recovery, say No" before, now it works fine on my N4

Works fine on TWRP. Updater asks if we want to save root. I said, No. Nothing is asked or said about recovery but recovery (TWRP) is retained. After the update, I went back to recovery and flashed the recent 1.43 update from Chainfire. All went well. Soon thereafter, I was notified that SuperSU is now at version 1.44.
Everything is smooth so far.... One app that works with root is goofy now, but other than that, all is well.

Can someone tell me if using the first part of my method to keep the recovery (so not flashing Chainfire file) and updating to SuperSU 1.44 on google play is enough to get back root?
In my case I updated to SuperSU 1.44 and when I launched it, that asked me to update SU binary and choose between normal or CWM/TRWP method, I choose normal and it worked.
clusterchuck, I get that error too but it didn't blocked and all went fine. Is it a blocking error?

Le_Zouave said:
Can someone tell me if using the first part of my method to keep the recovery (so not flashing Chainfire file) and updating to SuperSU 1.44 on google play is enough to get back root?
In my case I updated to SuperSU 1.44 and when I launched it, that asked me to update SU binary and choose between normal or CWM/TRWP method, I choose normal and it worked.
clusterchuck, I get that error too but it didn't blocked and all went fine. Is it a blocking error?
Click to expand...
Click to collapse
as far as the "no context", i dont think its a blocking error, because once I got the update working, it still has that error message on there. But it turned out my problem was that I deleted some google apps (google plus, earth, etc), and i had completely forget about that. So i ended up having to flash the stock 4.2.2 again then installing 4.3 for it to all go smoothly.

Great , thanks for the post, I will check that this weekend.

Update error
I did some previous flashing with Google Edition camera apk's and whatnot but I believe I should have the stock camera/GoogleGallery.apk.
I perform the steps and it gives me a Status 7 error, with "GoogleGallery.apk" somewhere in there. So I flash the stock 4.2.2 google apps and try again, this time it gives me a BrowserProviderProxy.apk error, Status 7 as well.
Any help on this?

Perhaps your system apps have been modified before or your kernel have been flashed before. Safest method will be to use fastboot to upgrade.
clusterchuck said:
i got an error when attempting to install in cwm, something regarding a no file_context.
edit: it says error /sdcard/0/ ebc... (status 7)
Click to expand...
Click to collapse

Is it also working when coming from a custom kernel (e.g. franco)?

[LOLLIPOP 5.1][STOCK] Cherry Mobile One H940 Official Links

Here're the official links for Cherry Mobile One H940:
For fastboot flashable images:
Builds Available: LBY29G, LMY47O
Download: here
For OTAs:
Build: LBY29G -> LMY47O
Android Version: 5.1 (Beta) -> 5.1 Official
Download: here
Flashing Instructions:
A. Using ADB sideload (for recovery flashable update zips):
1.) Flash stock recovery.
2.) Boot to stock recovery.
3.) Perform up + power button to show menu.
4.) Select Apply update from ADB.
5.) Install ADB drivers if on Windows and not yet installed.
6.) Open cmd prompt.
7.) Change directory to where you downloaded the update zip.
8.) Issue cmd: adb sideload <update.zip filename>
9.) Wait until completed.
10.) Select reboot.
B. Using fastboot:
1.) Boot into bootloader.
2.) Flash image using fastboot flash <partition name> <image filename>.img command.
3.) Reboot using fastboot reboot command.
C. Using DD (for flashing images like system.img):
1.) Boot into custom recovery. (you could use fastboot boot custom-recovery.img so that you don't overwrite your existing one)
2.) Push image file to /sdcard using adb push command. (you might have to mount the sdcard partition before doing this)
3.) Open an ADB command shell.
4.) Go to /sdcard.
5.) Find the system partition by issuing a cat /proc/partitions command. It should be the one sized exactly 1GB (1,024,000 shown).
6.) Use dd if=/sdcard/<image filename>.img of=/dev/block/<name of partition> .
7.) Reboot either using custom recovery or just issuing an adb reboot after exiting from ADB command shell.

do you have another working file for LMY47O system.img? i'm getting a fastboot flash fail (chunk unkown) error. thanks

Reuploading now. Might be a bad upload from my end. Will post updated hashes later for the system.img.

intersectRaven said:
Reuploading now. Might be a bad upload from my end. Will post updated hashes later for the system.img.
Click to expand...
Click to collapse
same problem here
thank you

Uploaded. If it still fails, you might have to use dd to restore. Odd that it fails now when it was fine before. :/

OTA Flashing Error
Hello. I would like to ask why I cannot flash the OTA Update for CM1. I am currently on LBY29G, rooted, unlocked bootloader and stock recovery. Thanks.

erickho0407 said:
Hello. I would like to ask why I cannot flash the OTA Update for CM1. I am currently on LBY29G, rooted, unlocked bootloader and stock recovery. Thanks.
Click to expand...
Click to collapse
Go back to stock boot. Since you're rooted, I'm assuming your boot has been modified to be insecure.

intersectRaven said:
Go back to stock boot. Since you're rooted, I'm assuming your boot has been modified to be insecure.
Click to expand...
Click to collapse
Ok By going back to "stock boot," does this mean I have to re-lock the bootloader? I believe that I have only used the ALL-IN ONE TOOL in this thread to do the 3 things mentioned above, and also installed Lucky Patcher, Greenify, Busybox (Free) and Ad-Away in relation to root access, so I am not 100% sure by what you mean. Thanks again.

erickho0407 said:
Ok By going back to "stock boot," does this mean I have to re-lock the bootloader? I believe that I have only used the ALL-IN ONE TOOL in this thread to do the 3 things mentioned above, and also installed Lucky Patcher, Greenify, Busybox (Free) and Ad-Away in relation to root access, so I am not 100% sure by what you mean. Thanks again.
Click to expand...
Click to collapse
No you don't need to relock the bootloader. You just need to flash stock boot partition. This is usually replaced when rooting.

intersectRaven said:
No you don't need to relock the bootloader. You just need to flash stock boot partition. This is usually replaced when rooting.
Click to expand...
Click to collapse
Ok. So this means that I reflash boot.img right (would probably use fastboot). Thank you very much for assistance

Sir
can you capture ota for myphone uno

gabisonfire98 said:
Sir
can you capture ota for myphone uno
Click to expand...
Click to collapse
Unfortunately, I don't have an Uno so no.

still the same problem, will try DD **update still failed, and now can't flash old build...will try to restore a backup from CWM

Working internal detect for pc and file ?

marjoejoejoe said:
still the same problem, will try DD **update still failed, and now can't flash old build...will try to restore a backup from CWM
Click to expand...
Click to collapse
I see. Very weid. Might be some form of protection now for the system partition. I'll just take it down now so that no one else uses it.

intersectRaven said:
I see. Very weid. Might be some form of protection now for the system partition. I'll just take it down now so that no one else uses it.
Click to expand...
Click to collapse
I'll have another go at it later today. Was able to flash my own backup using CWM

marjoejoejoe said:
I'll have another go at it later today. Was able to flash my own backup using CWM
Click to expand...
Click to collapse
Still, it should be foolproof. I already checked and double-checked the system image I uploaded and it's mountable in Linux so it should restore correctly like the previous LBY image. I can't think of any other reason aside from some sort of protection that would disallow flashing of the system image through both fastboot and dd.
*On second thought, I'm reupping the image. I just flashed it using dd on my device and it works perfectly.

success, was running a windows 7 virtual machine in OSX. it must have been a protection, you are right...ran it using OSX instead (stupid me, why i didn't use it in the first place for fastboot).
files are good to go thanks man

Need help in Flashing the Stock Recovery.
Hi Guys,
I need help in flashing the stock recovery.
I've used the ALL-IN-ONE TOOL to unlock my phone's bootloader, flash the PhilZ Touch Customer recovery and Root my CM1
[http://forum.xda-developers.com/cro.../tool-master-tool-unlock-bootloader-t2997696]
However I'm unsuccessful flashing the stock recovery from the ALL-IN-ONE TOOL so I can update my phone's software to Android 5.1.1.
Can I flash the stock recovery using one of the files here? If yes, can someone please teach me how.
Thanks in advance!

OTG
Hi,
Just a quick question, after flashing using this ROM, will CM One support OTG? Or do I need to root the phone first? Is there a way to add support for OTG?
Pardon me if this may not be much related to the topic.

Stuck with CMW 6.0.3.5 - No TWRP 2.8-20150421-yuga

Hi using the guide i've tried on both PC and terminal emulator and also flashing the zip in cmw but it still keeps booting to CMW 6.0.3.5
Any help?
thanks
Jamie

cramhead said:
Hi using the guide i've tried on both PC and terminal emulator and also flashing the zip in cmw but it still keeps booting to CMW 6.0.3.5
Any help?
thanks
Jamie
Click to expand...
Click to collapse
try flashtool > fastboot mode > flash recovery via select kernel to hot boot
edit:flash .img file

yeah i forgot to mentipon i also tried that.
fastboot flash recovery recovery.img
didnt work

oops my bad
the install recovery + option is gray on my flashtool. I cant see that option
mostafaz said:
try flashtool > fastboot mode > flash recovery via select kernel to hot boot
edit:flash .img file
Click to expand...
Click to collapse

cramhead said:
oops my bad
the install recovery + option is gray on my flashtool. I cant see that option
Click to expand...
Click to collapse
sorry for late responce
i did try some method and this one is good
try this hack and by flash via recovery and then flash your own recovery
latest recovery is here

installed both .............Nothing happened
I'll try an old TWRP

Which rom are you on?
try flashing TWRP 2.8.5 the official version and you should be able to boot to TWRP Recover.
http://forum.xda-developers.com/showpost.php?p=57718351&postcount=2
check the link, thats what Oliver has to say about the ROM, boot.img file

I tried flashing version TWRP 2.5 and that still did nothing. I'm using ANDROID 5.1. XPERIA Z(YUGA)
:crying:

cramhead said:
I tried flashing version TWRP 2.5 and that still did nothing. I'm using ANDROID 5.1. XPERIA Z(YUGA)
:crying:
Click to expand...
Click to collapse
Sorry only last question, who's ROM are you using and build date.

Hey, I believe it's the 5.1 version for this
build says full_c6603-userdebug 5.1 LMY47D eng.adrian.20150312.205659 test-keys

cramhead said:
Hey, I believe it's the 5.1 version for this
build says full_c6603-userdebug 5.1 LMY47D eng.adrian.20150312.205659 test-keys
Click to expand...
Click to collapse
Ok, so the ROM by pabx, This rom does not have in built arrangement for TWRP, you will have to compile it on your own.
You will find the steps here http://forum.xda-developers.com/xperia-z/general/turorial-add-twrp-to-boot-img-t2951658
and then flash TWRP to Fotakernel first and then flash boot.img

learn something new everyday
could I flash a philz recovery?
I can't find a .zip and can't do "fastboot recovery.img "the philz.img
thanks

I have not tried Philz, so i cannot give you an answer.
you may want to head over to this link http://forum.xda-developers.com/xperia-z/general/z-xzdualrecovery-qa-t2477769

Had the same problem.
TWRP Recovery wasn`t available after I flashed yuga.
Used "TWRP Manager" (only with root) which worked for me even when the app said that the installation failed.After rebooting I was able to enter TWRP again.

SO I installed This and I now have TWRP 2.8.
0! My rom won't boot any more, but who cares I can now install CM!..............I hope

have you tries the hack that oliver has on his thread http://forum.xda-developers.com/showpost.php?p=57718351&postcount=2
flash Olivers TWRP to FotaKernal and then from cm recovery flash the hack, reboot and enter recovery and check
I have not personally check but give it a try if you like.

Unlocking bootloader and installing Custom recovery [Sprout4] [Marshmallow 6.0]

So i have successfully installed a custom recovery on my phone running Marshmallow and also unlocked the bootloader!
Its quite simple actually!
I am not responsible for any damage you make to your phone!
Steps-
1. Download the zip file from the link and extract it.
2. Install both the drivers and then proceed!(The drivers are universal and work for Windows 98,xp,vista,7,8,8.1,10 but in 8,8.1,10 you might need to turn off the digital signature verification-Make good use of google)
3.After installing the drivers , connect your phone in switched on and remember to turn on usb debugging in the dev options!
4. Open the unlock_bootloader_... and run the .bat file and follow the on screen steps( All the data will be formatted so make a backup beforehand)
5.After doing this you will void your warranty so make sure you know what you are doing!
6. Open the one click installer folder and replace the recovery.img with any recovery that you want.
7. Now again connect your phone in switched on mode and usb debugging on and run the .bat file of recovery installer.. and follow the on screen steps!
8.As soon as the the recovery installation is over do not let teh phone reboot just press the vol up button as the installation process stops and then go to recovery!
9.Boom!! Now you have a phone with unlocked bootloader and a custom recovery installed on marshmallow!!
10.Flash custom Kernels,Boot Animations, Logos and root your phone running marshmallow and brag!
Downloads--
Bootloader and Recovery.zip(27.4 MB)
Press Thanks:good: if this helped and if you have any querries just use the section below!

Recovery Kernel?
Hi bro just a quick question did you use the MM kernel in the custom recovery?
On our None AOSP standard Mediatek devices the rom does a Kernel check to ensure both the boot and recovery Kernels are of the same version eg KK boot = KK Recovery LP boot = LP Recovery so I just wondered if the MM Kernel still works in the Philz recovery or are you still using a kernel from a older version of android eg KK or LP.
Hope that makes sense to you :laugh:

How to open the unlock_bootloader ??? There is no such option

how about rooting? what method did you use?

bigrammy said:
Hi bro just a quick question did you use the MM kernel in the custom recovery?
On our None AOSP standard Mediatek devices the rom does a Kernel check to ensure both the boot and recovery Kernels are of the same version eg KK boot = KK Recovery LP boot = LP Recovery so I just wondered if the MM Kernel still works in the Philz recovery or are you still using a kernel from a older version of android eg KK or LP.
Hope that makes sense to you :laugh:
Click to expand...
Click to collapse
Actually i didn't work on the recovery, i just made the one click thing, i inserted any random recovery i found working on 6.0 .

cheeze.keyk said:
how about rooting? what method did you use?
Click to expand...
Click to collapse
i flashed a custom kernel and then the super su beta zip

akash.kotwani said:
How to open the unlock_bootloader ??? There is no such option
Click to expand...
Click to collapse
in the zip you will find a .bat file, open that and follow on screen instructions

How to relock bootloader if I ever want to?

net_freak said:
How to relock bootloader if I ever want to?
Click to expand...
Click to collapse
Well i did not make anything that can do that but you'll probably find it in other threads. You can also flash bootloader.using the stock rom file via sp flash tools to relock it just untick everything else but bootloader!

Unlocking bootloader is necessary? Can I not just do it with it locked bootloader?

net_freak said:
Unlocking bootloader is necessary? Can I not just do it with it locked bootloader?
Click to expand...
Click to collapse
You can but unlocking the bootloader opens up many other things for devs!

divyesh bansal said:
You can but unlocking the bootloader opens up many other things for devs!
Click to expand...
Click to collapse
Will the fastboot method to flash twrp work ? I'm on Android 6.0

net_freak said:
Will the fastboot method to flash twrp work ? I'm on Android 6.0
Click to expand...
Click to collapse
Yes it does, the tool is also all about it. In the one click recovery intaller folder replace the recovery.img with your twrp(you will have to rename twrp.img file to recovery.img) and follow the steps in the first post in this thread!

divyesh bansal said:
Yes it does, the tool is also all about it. In the one click recovery intaller folder replace the recovery.img with your twrp(you will have to rename twrp.img file to recovery.img) and follow the steps in the first post in this thread!
Click to expand...
Click to collapse
Thanks. . can I use all in one tool kit by @Faiyaz5yaz for the same

I using a rom based on the stock - Is there any deference to the original one?

Hi There
Using this rom by Danvdh (6.0.1 MMB29K):
http://forum.xda-developers.com/nexus-6/development/rom-5-1lightromstock-lmy47e-03-19-2015-t3059493
1) Is there a difference between the original one from Google to that rom?
2) OP mentioned that there is an updated recovery flashable releases of stock rooted Android.
It mean that it actually like an OTA updates?
3) What is the process if I want to move from rom such as the one mentioned here to a stock by Google and stay rooted?
Thanks!

1. Read the build information in the OP of the thread, it mentions all the differences.
2. It's the full stock FW but recovery flashable instead of fastboot and also rooted.
3. You would need to fastboot stock FW and manually root or flash the recovery flashable stock FW the was mentioned in question no. 2.

1) "100% untouched stock framework" Would actually be and act the same as a real stock from from(Factory Image) developers.google.com?
2) Meaning that when an update will be released I would able to flash it auto' from the recovery?
3) Can you please explain me?
- "fastboot stock FW" ?? Means download the Factory Image from developers.google.com , connect to usd and hit the " flash-all.bat"?
- "recovery flashable stock FW" ?? I know only about the Factory Image that flashed through fasboot...Where can i get the recovery version? (not from Google,right?)
Or I could just use this tutorial?
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Thanks!

duba500 said:
1) "100% untouched stock framework" Would actually be and act the same as a real stock from from(Factory Image) developers.google.com?
2) Meaning that when an update will be released I would able to flash it auto' from the recovery?
3) Can you please explain me?
- "fastboot stock FW" ?? Means download the Factory Image from developers.google.com , connect to usd and hit the " flash-all.bat"?
- "recovery flashable stock FW" ?? I know only about the Factory Image that flashed through fasboot...Where can i get the recovery version? (not from Google,right?)
Or I could just use this tutorial?
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481 Read this to get a better idea what to do.

duba500 said:
Hi There
Using this rom by Danvdh (6.0.1 MMB29K):
http://forum.xda-developers.com/nexus-6/development/rom-5-1lightromstock-lmy47e-03-19-2015-t3059493
1) Is there a difference between the original one from Google to that rom?
2) OP mentioned that there is an updated recovery flashable releases of stock rooted Android.
It mean that it actually like an OTA updates?
3) What is the process if I want to move from rom such as the one mentioned here to a stock by Google and stay rooted?
Thanks!
Click to expand...
Click to collapse
1)Differences would be that SuperSu is installed, busybox is installed, encryption is disabled in the kernel, important gapps such as google play services and the play store are updated to their newest current version so when you install the rom google services immediately work without needing to wait for a background update, gapps that can be fully functional by just downloading them from google play store (google+, youtube, google drive, etc) were removed from /system likely to save space to make it easier to install mods such as guitardedhero's viper/dolby sound mod, vanilla android's gallery photos app was added in place of google photos app, the little android debugging notification is hidden, and the tethering check was disabled to allow for tethering without a tethering plan.
2) The updated recovery flashable line is referring to the fact that the dev updated the google apps in the rom.
3) If you wanted to go totally stock then you'd need to just flash the boot.img and system.img out of a factory image from google since the rom is very very close to stock a userdata wipe shouldn't be needed and a cache/dalvik wipe may or may not be but as always have a backup in TWRP. Then go into TWRP before booting and install the latest SuperSu (2.65 iirc right now) installing the newest SuperSu's can cause a bootloop or 2 (in the middle of booting the phone will go back to the Google logo and booting again, it will usually do this 1 or 2 times before properly booting). (if you boot to android before going to TWRP it will be replaced since you have an untouched /system after flashing the system.img). And if you allow TWRP to keep /system as read only (it'll popup when you first boot into TWRP asking if you want to do that) then the stock /system will replace TWRP with stock recovery and OTA's will work if you do a total unroot from within the SuperSU app.

Hi,
Regarding (1): Yes I know that.
I meant to the rom itself(not gaspps, supersu, busybox..).
(2) Really? that's all? I thought it kinda of ota to the rom.
(3) Really? that's all(2...)?
If i boot in into twrp => flash the boot.img and system.img from the factory image , I will have a totally stock rom?!
So 4sure just download the factory image and just extract the boot.img and system.img?
Would you mimd to aprove if i got this right?
-> Take the boot.img and system.img from the factory image
=> Boot into TWRP and FLASH the 2 img's *without rebooting at the end*
=> Wipe cache/dalvik.
=> Flash SuperSu 2.65 ***By flashing 2.65 I wont face the 1-2 bootloop's?***
=> Wipe cache/dalvik.
=> Boot into system.
Did I undersyood it right?
Thanks for your advice-tip of the SuperSu version!
P.S:
LG doesnt have a dev site such as Google's have with all the Factory Firmwares?
Can I trust site such as: lgg3root. com/lg-g3-stock-factory-firmware
???

duba500 said:
Hi,
Regarding (1): Yes I know that.
I meant to the rom itself(not gaspps, supersu, busybox..).
(2) Really? that's all? I thought it kinda of ota to the rom.
(3) Really? that's all(2...)?
If i boot in into twrp => flash the boot.img and system.img from the factory image , I will have a totally stock rom?!
So 4sure just download G3 LS990 32GB and extract the boot.img and system.img?
Would you mimd to aprove if i got this right?
-> Take the boot.img and system.img from the factory image
=> Boot into TWRP and FLASH the 2 img's *without rebooting at the end*
=> Wipe cache/dalvik.
=> Flash SuperSu 2.65 ***By flashing 2.65 I wont face the 1-2 bootloop's?***
=> Wipe cache/dalvik.
=> Boot into system.
Did I undersood it right?
Click to expand...
Click to collapse
You have got a fantastic tip in looking here: http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Search for fastboot.