Related
Gnex Toolkit option 10 = Boot into custom recovery without permanently flashing it. I understand that this means that the stock recovery won't be overwritten. Does it therefore mean that you can use a custom recovery to flash zip files from sd partition without using/losing stock recovery?
NB Why can't I ask this question at the gnex toolkit thread? I don't appear to be allowed to join in.
optom2000 said:
Gnex Toolkit option 10 = Boot into custom recovery without permanently flashing it. I understand that this means that the stock recovery won't be overwritten. Does it therefore mean that you can use a custom recovery to flash zip files from sd partition without using/losing stock recovery?
NB Why can't I ask this question at the gnex toolkit thread? I don't appear to be allowed to join in.
Click to expand...
Click to collapse
Yep, it means exactly that. You could do the same using the fastboot command fastboot boot <recovery-name>.img if you decide to ever learn to use fastboot and ADB (which you should ).
Unlawful said:
Yep, it means exactly that. You could do the same using the fastboot command fastboot boot <recovery-name>.img if you decide to ever learn to use fastboot and ADB (which you should ).
Click to expand...
Click to collapse
@Unlawful. Thank you very much for your extremely prompt reply. Perhaps you would be kind enough to indulge me further. The reason I asked the question is that I am currently rooted and using a custom rom (Gummy) but fancy some JellyBean. I understand that I need to flash stock rom 4.0.4 and then flash stock recovery in order to get OTA update (btw do I need to do a system wipe before flashing the stock rom as you do before you flash a custom rom or is is ok just to flash stock without a separate manual wipe?), reboot and see if I get the OTA update immediately. If so I can just go ahead and update. If not I have the OTA update as a flashable zip file I obtained elsewhere in XDA. Hence if I have a stock recovery installed but can use a custom recovery (CWM Touch) I can flash the update as zip using CWM and then re-root and re-flash CWM permanently, all of this being done by the toolkit. Is my thinking correct?
Hey guys just received my n7 yesterday and am very pleased with this, however I have some questions.
Does rooting (only) removes your OTA updates access? I also own a Galaxy S4 (rooted) and I can't get OTA, it says it's modified, but I did flash a custom update on it and kernel. So if I just root my n7, and not flash anything, I will still get OTA's correct? I just want to use some apps which requires root access and not planning to flash a custom rooms or anything. Thanks for any help.
Sent from my Nexus 7 using Tapatalk 4
Mine is always rooted, and I get all OTAs.
Sent from my Nexus 7 using xda app-developers app
You just need to have the stock recovery to receive OTAs.
Username invalid said:
You just need to have the stock recovery to receive OTAs.
Click to expand...
Click to collapse
So if I have twrp installed, i won't receive them?
Sent from my Nexus 7 using Tapatalk 4
Takes 10 seconds to reflash the stock recovery.
UPDATE: SuperSU-v1.55 added the fix for the OTA update issue, so this post is no longer necessary unless you are using an older version of SuperSU
This post also applies to JSS15Q update.
I actually went through and tested JWR66N rooted with SuperSU and the JSS15J OTA update. I expected it to work but it exited with an error.
Ironically the JSS15J OTA actually did patch every single file successfully but near the end while setting permissions, it came up with an error, so after reboot you'll actually be running with all JSS15J rom files, except your build will still say JWR66N, you'll still be running the JWR66N recovery, and you'll still be running the 3.05 bootloader.
I tracked down the issue and put together a fix for it. If you want, it is attached to this post. You just run it after installing SuperSU, so basically:
adb reboot bootloader
fastboot boot twrp.img
within TWRP
install UPDATE-SuperSU-v1.51.zip (SuperSU v1.55 or greater incorporates the OTA fix)
install UPDATE-SuperSU-v1.55.zip
install UPDATE-SuperSU-ota.zip (can be chain installed, just make sure you choose to install it 2nd)
reboot
You'll need to redo these steps (both the installs) after you receive the OTA to preserve root and ability to receive future OTAs.
Also as others have mentioned it is best to be running stock recovery (which the above commands will allow you to do because twrp is never flashed on the tablet) I've attached the stock recovery for JSS15J in case someone needs it.
If you make ANY modifications or delete files from the stock ROM with your new root privileges, then you will greatly increase the chances of the OTA failing. Adding new files is normally fine.
Well shoot - now you have me worried. I did install TWRP, but never considered that would block OTAs. Do they attempt to install and fail?
Sent from my Nexus 7 using xda app-developers app
rmm200 said:
Well shoot - now you have me worried. I did install TWRP, but never considered that would block OTAs. Do they attempt to install and fail?
Click to expand...
Click to collapse
On some platforms, especially when flashing bootloaders and/or radios, the stock recovery pulls some funky maneuvers to get that done. Often custom recoveries are not privy to those maneuvers. Also sometimes custom recoveries will experiment with custom kernels which don't always have the bootloader and/or radio devices mapped the same as the stock kernel. This can lead to problems to.
Thus it is safest to use stock recovery to flash OTAs.
I have flashed the complete JSS15J OTA except for the bootloader part using TWRP and it works ok. All the ROM files are patched.
I just didn't feel like risking my tablet with the bootloader flash portion of JSS15J OTA using twrp. It might work fine. I just know from the past the potential for issues are higher in that section of the OTA flash.
Is it common for nice folk on here to upload a stock zip of say for example, 4.3.1 when it releases so that we can flash it through a custom recovery (e.g., TWRP, CWM etc.), without having to change our custom recoveries?
It was common on other platforms I've used, but I don't know about here.
Root will not prevent an OTA update from coming in and installing, and a custom recovery won't "block" (it just won't be able to complete the install of it automatically). I have been installing OTA updates on rooted Nexus devices with custom recoveries since the Nexus One, and assuming the new Nexus 7 works the same way, the following applies:
If you are running stock ROM, your deivce will receive the notification and download the update, even if rooted
If you are running stock recovery, the update will install automatically as normal
If you are running a custom recovery like CWM or TWRP, it will fail to install automatically but it will still have downloaded to the device and you can use the custom recovery to install it yourself (I've never had this fail)
If you have modified files in /system, the OTA update is pretty much guaranteed to fail regardless of which recovery you use
If you successfully install the OTA update, you will no longer have root, so flash SuperSU using a custom recovery after the OTA update installs
Also:
You can always look for the OTA zip URLs on XDA and just download the update yourself to flash if you don't want to wait for it to come to your device (this is what I always do)
You can flash factory images instead of the update, without losing data (see other threads for how)
If you want to keep stock recovery installed, you can always use fastboot to boot a custom recovery without flashing it, in case you ever need it
The above is accurate and correct as far as I'm aware from my own experience over the years with Nexus devices. I'm sure someone will be happy to correct me if anything is wrong Hope this helps.
phazerorg said:
Root will not prevent an OTA update from coming in and installing, and a custom recovery won't "block" (it just won't be able to complete the install of it automatically).
Click to expand...
Click to collapse
I thought the same about root not blocking the OTA update install from being successful, but that was with years of using superuser.
With SuperSU (I am not sure which version introduced it) they set the immutable flag on a file in almost every OTA. I believe this is to support some OTA survival mode. This causes the OTA to fail in the section where it sets permissions. All the files are patched at that point, but the build.prop hasn't been modified to reflect the new version # and the bootloader and recovery haven't been flash.
You'll essentially be running JSS15J but your software will report it is on JWR66N, your bootloader wouldn't have been patched, and you would be running JWR66N recovery.
TheAltruistic said:
Is it common for nice folk on here to upload a stock zip of say for example, 4.3.1 when it releases so that we can flash it through a custom recovery (e.g., TWRP, CWM etc.), without having to change our custom recoveries?
Click to expand...
Click to collapse
yes the ota update zip always gets posted so you can manually flash with a custom recovery...
just keep in mind you need to keep your files stock otherwise it might not work
Sent from my Nexus 7 2
nolook said:
yes the ota update zip always gets posted so you can manually flash with a custom recovery...
just keep in mind you need to keep your files stock otherwise it might not work
Sent from my Nexus 7 2
Click to expand...
Click to collapse
When you say keep your files stock what does that mean exactly? I have titanium backup app installed would that be one of them? Thanks.
Mightym83 said:
When you say keep your files stock what does that mean exactly? I have titanium backup app installed would that be one of them? Thanks.
Click to expand...
Click to collapse
Titanium backup is an app, I assume with files he is targeting e. G. Config files.
Sent from my Nexus 7 (2013)
Mightym83 said:
When you say keep your files stock what does that mean exactly? I have titanium backup app installed would that be one of them? Thanks.
Click to expand...
Click to collapse
It means don't modify or delete any files in /system
Don't remove a system app that shipped with the tablet. You can install a new version as that just hides the one in /system, but if you remove or modify the original, then the OTA will very likely fail (depending on how complex the OTA is)
Adding files is ok.
Alright, so here's my scenario. Hopefully someone can tell me what should happen:
I am running the stock ROM on my Nexus 7 (2013), but I have ClockWorkMod Recovery installed and I'm using Koush's Superuser app for root permissions. The only system file that I think I have changed is my hosts file because of Adaway. That is easily reverted, though.
So can I just download the OTA, install it manually from the custom recovery (flashing the update.zip file), and then re-flash Koush's superuser app back onto the device?
Will that go smoothly, and will the newer build number be accurately reflected in my About Phone afterward?
(that last part is just my OCD talking)
phazerorg said:
:
[*]If you are running a custom recovery like CWM or TWRP, it will fail to install automatically but it will still have downloaded to the device and you can use the custom recovery to install it yourself (I've never had this fail)
Click to expand...
Click to collapse
This was very helpful, and this is the category i fall in. However, i have installed a kernel. does that change anything?
So basically what you are saying is this, with my current set up:
1 - i will get the update, it will download, but wont install. I should boot into TWRP and install the file that way. Correct? Where is the downloaded file stores?
2 - I can just wait for the download to be posted on here, and just install via twrp.
3 - either way, after installing it, i will lose root. I should then boot into twrp and flash supersu.
Correct?
Theoretically it could work. I believe the flash has worked with twrp.
Personally I always put stock recovery back to flash ota's though especially if there is a bootloader (or radio if you have a mobile version) because on some platforms they involve special procedures that may not be in the custom recovery.
On nexus it looks like it will work with custom recovery but it takes so little effort to put stock recovery back I just do it automatically.
Having said that, I've seen one person post it worked on twrp but haven't read an experience on cwm. Not saying it will or won't work.
If we are running the stock ROM, but have it rooted with the custom recovery, why cant we just use Wegfresh's nexus toolkit to Unroot and image using the updated IMG file?
Then go through and use it to recreate the root\custom recovery again?
Hi everybody
First, sorry for my bad inglish.
I have a little question , I have sm-t700 with stock rom, i have root with cf autoroot.
Now i want to change my stock rom for another one, if I use for exemple flashify apk o another one for change my stock rom o titanium backup o what ever apk for change the rom, when I flash the new room, can I lose the root in my device?
I don't have windows pc for use again odin, dont want lose my root.
Thx everybody!!!!:laugh:
What rom are you trying to flash? Anyway as long you have twrp recovery, supersu will prompt you to install the binaries when you open the app and choose install with twrp/cwm. Then you will still have root. But most custom roms should be prerooted
I think YES you need root again if is it not modded rom.
DUHAsianSKILLZ said:
What rom are you trying to flash? Anyway as long you have twrp recovery, supersu will prompt you to install the binaries when you open the app and choose install with twrp/cwm. Then you will still have root. But most custom roms should be prerooted
Click to expand...
Click to collapse
[ROM][LOLLIPOP][UNOFFICIAL] Cyanogenmod: cm-12.0 for SM-T800 16gb -
If i flash this one??
abstractS8 said:
[ROM][LOLLIPOP][UNOFFICIAL] Cyanogenmod: cm-12.0 for SM-T800 16gb -
If i flash this one??
Click to expand...
Click to collapse
Oh. Well you said you had the SMT700 right? This is the one http://forum.xda-developers.com/showthread.php?t=2963870
Anyway as long you have twrp recovery, just flash a zip (google it) called supersu.zip after flashing the rom. Then you should have root. Just follow the instructions in the thread I gave you and you should be good
DUHAsianSKILLZ said:
Oh. Well you said you had the SMT700 right? This is the one http://forum.xda-developers.com/showthread.php?t=2963870
Anyway as long you have twrp recovery, just flash a zip (google it) called supersu.zip after flashing the rom. Then you should have root. Just follow the instructions in the thread I gave you and you should be good
Click to expand...
Click to collapse
Thx for your time really.
downloading: Cyanogenmod 12: https://blck.io/cm-12-20150218-UNOFFICIAL-klimtwifi.zip
Need flash the recovery too? Cyanogen Recovery: https://blck.io/c-recovery-20150207-...-klimtwifi.img
O can I still twrp? I go to use TWRP apk for flashCyanogenmod 12: https://blck.io/cm-12-20150218-UNOFFICIAL-klimtwifi.zip
is better joining to recovery mode?
It doesn't matter what rom you have installed you can use any recovery compatible for your device. If you flash a stock rom you will end up with stock recovery unless it's a nandroid.
Hello everyone, im really mew to rooting.
I have the T Mob M8 with 5.0.1, i was planning on rooting but will I be able to update nprmally wjen 5.1 comes out? If so how?
Also whats tje easiest method to root this phone? Ive seen apks like framaroot that root the phone extremely quick and easy...is there something similar for this phone?
Thanks in advance
Sent from my HTC One_M8 using XDA Free mobile app
Root by unlocking the bootloader via HTCDev.com and then just install custom recovery and flash current (2.56) SuperSU zip.
One click root solutions won't work with a locked bootloader. Unlocking the bootloader is really the key.
Once rooted, you can OTA. But you need to have stock ROM (nothing altered in /system partition) and you need to re-install stock recovery. Root is okay (although you will likely lose root) and unlocked bootloader is okay to OTA. To root again after an OTA, just install custom recovery and flash SuperSU again.
Thanks a lot. I will unlock the bootloader and can you link me to a good tutorial or guide on how to install custom recovery and supersu?
Thanks again
Sent from my HTC One_M8 using XDA Free mobile app
Red_Gh0st said:
Thanks a lot. I will unlock the bootloader and can you link me to a good tutorial or guide on how to install custom recovery and supersu?
Click to expand...
Click to collapse
The following guide is a pretty good one: http://forum.xda-developers.com/showthread.php?t=2799796
Although some links are outdated:
1) Installing HTCSync should be fine to get the HTC drivers on your computer; or you can search XDA for more recent HTC drivers. The HTC drivers linked in the guide are really old.
2) Get the latest SuperSU zip here: http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3) And if you need an easy adb/fastboot installer, just use the XDA seach function with the phrase "simple adb" and you will get a few results for beginner adb guides and installers.
4) Get the latest version of TWRP here: http://techerrata.com/browse/twrp2/m8
redpoint73 said:
The following guide is a pretty good one: http://forum.xda-developers.com/showthread.php?t=2799796
Although some links are outdated:
1) Installing HTCSync should be fine to get the HTC drivers on your computer; or you can search XDA for more recent HTC drivers. The HTC drivers linked in the guide are really old.
2) Get the latest SuperSU zip here: http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3) And if you need an easy adb/fastboot installer, just use the XDA seach function with the phrase "simple adb" and you will get a few results for beginner adb guides and installers.
4) Get the latest version of TWRP here: http://techerrata.com/browse/twrp2/m8
Click to expand...
Click to collapse
hello I saw your post Im planning also to root my m8 but I dont want to flash the custom recovery someone told me it is possible
just download the custom recovery
then type "fastboot boot recovery.img" = this will boot my m8 to custom recovery but not flash so I can flash the supersu in that custom recovery then reboot after that stock recovery is still intact
imfuzzyyy said:
hello I saw your post Im planning also to root my m8 but I dont want to flash the custom recovery someone told me it is possible
just download the custom recovery
then type "fastboot boot recovery.img" = this will boot my m8 to custom recovery but not flash so I can flash the supersu in that custom recovery then reboot after that stock recovery is still intact
Click to expand...
Click to collapse
That's true, you can boot TWRP remotely with fastboot, without actually flashing it (installing to the phone).
Although its slightly irrelevant; you can always flash back to stock recovery back to the phone (over-write TWRP). You can either find your stock recovery posted in the collection; or back it up your self using the fastboot TWRP trick (fastboot boot TWRP, and use TWRP to backup stock recovery). In that instance, the fastboot boot TWRP trick is very useful.
Having TWRP installed after root is very useful. Reason being, it gives you a lot more recovery options if things go south. And also, for a lot of mods done under root, you will want to backup your stock setup anyway (just in case the mod goes wrong, and you need to revert). Stock recovery is close to useless for anything but installing OTA updates.
redpoint73 said:
That's true, you can boot TWRP remotely with fastboot, without actually flashing it (installing to the phone).
Although its slightly irrelevant; you can always flash back to stock recovery back to the phone (over-write TWRP). You can either find your stock recovery posted in the collection; or back it up your self using the fastboot TWRP trick (fastboot boot TWRP, and use TWRP to backup stock recovery). In that instance, the fastboot boot TWRP trick is very useful.
Having TWRP installed after root is very useful. Reason being, it gives you a lot more recovery options if things go south. And also, for a lot of mods done under root, you will want to backup your stock setup anyway (just in case the mod goes wrong, and you need to revert). Stock recovery is close to useless for anything but installing OTA updates.
Click to expand...
Click to collapse
woah didnt know that I can back up the stock recovery by fastboot boot in TWRP BTW if I'm using this phone I will probably use a TWRP but its my gf who uses it so she just need the root access for xmod app because she is an coc adik haha and she doesnt know about modding its system, thanks for this wonderful information
---------- Post added at 01:33 AM ---------- Previous post was at 01:13 AM ----------
hello I need your help this m8 is previously rooted have supersu installed then take OTA before now it is not rooted but the supersu still intact on my apps, I fastboot boot twrp.img then went smoothly flash the supersu.zip but Im still unrooted any suggestion? it say on root checker the root access is not properly installed
update: sorry got root now I flashed the 1.94.zip which is very outdated didnt notice it flashed the latest 2.46.zip now its rooted thank you so much!
Hello I finally started downloading everything to get started. I start the process to unlock the bootloader but when i get to the part i need to type "fastoboom oem....." On cmd I get an error saying Adbwinapi.dll is missing try reinstalling the program.
What can I do to fix this?
Sent from my HTC One_M8 using XDA Free mobile app
Red_Gh0st said:
On cmd I get an error saying Adbwinapi.dll is missing try reinstalling the program.
Click to expand...
Click to collapse
Is HTC Sync installed? If so, re-install it.
Reinstalled but it still says tht file is missing from my conputer
Sent from my HTC One_M8 using XDA Free mobile app
Red_Gh0st said:
Reinstalled but it still says tht file is missing from my conputer
Click to expand...
Click to collapse
Try a different adb installer.
Thanks a lot I unlocked my bootloader and rooted my phone
Hi guys,
I've planned to do a CSE flash (means "with data loss") of latest official rom and then switch from the obsolete CloudyG3 to the FulmicsRom.
So I'll need TWRP recovery, but according to my experience it need to be "bumped", otherwise I get a Secure Boot error.
Autorec is considered the best solution, now I want to know:
1) How Autorec works to prevent this?
2) I'll get latest 2.8.7.0 TWRP recovery or the 2.8.6.0 instead?
3) I'll definitely solve bootloader issues, also when in future I'll manually flash "non-bumped" recoveries?
Ps i would appreciate more a better method to obtain the same result (the freedom of use non-bumped recovery).
The only I know is the "oem-unlock", but it's irreversible so I dislike it.
Simone98RC said:
Hi guys,
I've planned to do a CSE flash (means "with data loss") of latest official rom and then switch from the obsolete CloudyG3 to the FulmicsRom.
So I'll need TWRP recovery, but according to my experience it need to be "bumped", otherwise I get a Secure Boot error.
Autorec is considered the best solution, now I want to know:
1) How Autorec works to prevent this?
2) I'll get latest 2.8.7.0 TWRP recovery or the 2.8.6.0 instead?
3) I'll definitely solve bootloader issues, also when in future I'll manually flash "non-bumped" recoveries?
Ps i would appreciate more a better method to obtain the same result (the freedom of use non-bumped recovery).
The only I know is the "oem-unlock", but it's irreversible so I dislike it.
Click to expand...
Click to collapse
1) Autorec flash the "bumped" kitkat bootloader.
2) I have the 2.8.7.0, but its up to you really.
3) If you flash a not bumped rom or recovery, you will get a secure boot error. But, everything is bumped because its the only bootloader unlock that we have
RapHaeL_4_4_4_ said:
1) Autorec flash the "bumped" kitkat bootloader.
2) I have the 2.8.7.0, but its up to you really.
3) If you flash a not bumped rom or recovery, you will get a secure boot error. But, everything is bumped because its the only bootloader unlock that we have
Click to expand...
Click to collapse
So Autorec is useless, if I obtain the same result and limitations of a manual bumped recovery flash.
Why make useless bootloader changes if same result without mess up other partitions?
So, if I understand well, Autorec make exactly what I manually do by flashing of a "signed" boot/recovery partition.
I'm wrong?
Simone98RC said:
So Autorec is useless, if I obtain the same result and limitations of a manual bumped recovery flash.
Why make useless bootloader changes if same result without mess up other partitions?
So, if I understand well, Autorec make exactly what I manually do by flashing of a "signed" boot/recovery partition.
I'm wrong?
Click to expand...
Click to collapse
Its useless if you are still on kitkat, but if you're on lollipop and you want to install a custom rom or recovery, you don't need to downgrade with tot, loose everything, flash bump, and go on... it make things easier in that case.
In fact,
Bump make believe to the phone that what you try to boot is legit,
While Autorec install the bumped kitkat boot partition if you are on lollipop.
And the bootloader change is not useless if you're on lollipop because bump don't work on lollipop.
If you are on the cloudy Rom, you already have TWRP installed.
You don't need to go back to stock.
Just boot to recovery: turn off, press vol.down+power, when you see the LG logo release the buttons and press then again units you see the recovery the factory reset. Say yes both questions and then you are in TWRP.
Copy the new ROM on the SD card and flash it.
Brgds
Sent from my phone
ypsmav said:
If you are on the cloudy Rom, you already have TWRP installed.
You don't need to go back to stock.
Just boot to recovery: turn off, press vol.down+power, when you see the LG logo release the buttons and press then again units you see the recovery the factory reset. Say yes both questions and then you are in TWRP.
Copy the new ROM on the SD card and flash it.
Brgds
Sent from my phone
Click to expand...
Click to collapse
So you're saying that FulmicsRom, based on 21A, will works greaceful even under 20H system (bootloader, etc.)?
The CloudyG3 developer suggest to flash latest official rom before its latest custom one.
I think it's true for FulmicsRom too.
RapHaeL_4_4_4_ said:
Its useless if you are still on kitkat, but if you're on lollipop and you want to install a custom rom or recovery, you don't need to downgrade with tot, loose everything, flash bump, and go on... it make things easier in that case.
In fact,
Bump make believe to the phone that what you try to boot is legit,
While Autorec install the bumped kitkat boot partition if you are on lollipop.
And the bootloader change is not useless if you're on lollipop because bump don't work on lollipop.
Click to expand...
Click to collapse
Regarding the rom, I never needed to look for bumped releases.
On my device I flashed both Resurrection Remix (CM-based) and CloudyG3 without any problem: as requirements only the root access and a TWRP bumped recovery.
Probably the cited roms are signed by default, so the scenario described by you may happens only in other systems like MIUI or Ubuntu Touch... given that they are unsigned, I'm doing only an example.
I continue to be confused regarding the aim of Autorec.
So, why if I flash a non-bumped recovery I continue to get Secure Boot errors? The bootloader may be modified to prevent this behaviour, but Autorec won't do that.
So what it does?
Simone98RC said:
So you're saying that FulmicsRom, based on 21A, will works greaceful even under 20H system (bootloader, etc.)?
The CloudyG3 developer suggest to flash latest official rom before its latest custom one.
I think it's true for FulmicsRom too.
Regarding the rom, I never needed to look for bumped releases.
On my device I flashed both Resurrection Remix (CM-based) and CloudyG3 without any problem: as requirements only the root access and a TWRP bumped recovery.
Probably the cited roms are signed by default, so the scenario described by you may happens only in other systems like MIUI or Ubuntu Touch... given that they are unsigned, I'm doing only an example.
I continue to be confused regarding the aim of Autorec.
So, why if I flash a non-bumped recovery I continue to get Secure Boot errors? The bootloader may be modified to prevent this behaviour, but Autorec won't do that.
So what it does?
Click to expand...
Click to collapse
If you flash a non-bumped recovery, its normal that you get "Secure Boot Error" because bump is the "unlock". Everything on the g3 must be bumped to boot.
Autorec flash the kitkat bootloader if you are on lollipop (to make bump work) and after it flash a bumped twrp (recovery), that's all.
And if you read through the thread you will understand what autorec does: http://forum.xda-developers.com/lg-g3/general/apk-flash-twrp-autorec-thanks-to-t3081396
Simone98RC said:
So you're saying that FulmicsRom, based on 21A, will works greaceful even under 20H system (bootloader, etc.)?
The CloudyG3 developer suggest to flash latest official rom before its latest custom one.
I think it's true for FulmicsRom too.
Regarding the rom, I never needed to look for bumped releases.
On my device I flashed both Resurrection Remix (CM-based) and CloudyG3 without any problem: as requirements only the root access and a TWRP bumped recovery.
Probably the cited roms are signed by default, so the scenario described by you may happens only in other systems like MIUI or Ubuntu Touch... given that they are unsigned, I'm doing only an example.
I continue to be confused regarding the aim of Autorec.
So, why if I flash a non-bumped recovery I continue to get Secure Boot errors? The bootloader may be modified to prevent this behaviour, but Autorec won't do that.
So what it does?
Click to expand...
Click to collapse
Yes, you can flash on top of the cloudy no need to go back to stock.
The only thing you have to do is wipe all partitions except the sd before flashing.
Both ROMs are stock based.
If you decide to flash a KDZ or TOT to go back to stock you will have to root first and then use Autorec.
Brgds
Sent from my phone
ypsmav said:
Yes, you can flash on top of the cloudy no need to go back to stock.
The only thing you have to do is wipe all partitions except the sd before flashing.
Both ROMs are stock based.
If you decide to flash a KDZ or TOT to go back to stock you will have to root first and then use Autorec.
Brgds
Sent from my phone
Click to expand...
Click to collapse
Ok, thanks for the clarification.
I was afraid regarding the compatibility of the actual 20H bootloader with custom 21A rom, CloudyG3 is based on 20H but works under the same bootloader.
But you're telling me it's not existing any kind of problem with that.
So I can flash rom in the easier way (from zip file with TWRP recovery).
RapHaeL_4_4_4_ said:
If you flash a non-bumped recovery, its normal that you get "Secure Boot Error" because bump is the "unlock". Everything on the g3 must be bumped to boot.
Autorec flash the kitkat bootloader if you are on lollipop (to make bump work) and after it flash a bumped twrp (recovery), that's all.
And if you read through the thread you will understand what autorec does: http://forum.xda-developers.com/lg-g3/general/apk-flash-twrp-autorec-thanks-to-t3081396
Click to expand...
Click to collapse
So we can say that Autorec is useful only when I work with TWRP on official (obviously rooted) firmware.
But since the cited rom is only "based" on official, I'm not needing to use Autorec, if I directly flash bumped version of TWRP.
Simone98RC said:
Ok, thanks for the clarification.
I was afraid regarding the compatibility of the actual 20H bootloader with custom 21A rom, CloudyG3 is based on 20H but works under the same bootloader.
But you're telling me it's not existing any kind of problem with that.
So I can flash rom in the easier way (from zip file with TWRP recovery).
So we can say that Autorec is useful only when I work with TWRP on official (obviously rooted) firmware.
But since the cited rom is only "based" on official, I'm not needing to use Autorec, if I directly flash bumped version of TWRP.
Click to expand...
Click to collapse
Listen... Lollipop bootloader DOES NOT accept BUMP.
So what autorec app by Bender does is flash a kitkat bootloader which ACCEPTS BUMP.
Autorec also flashes the bumped TWRP to recovery partition.
So... if you have TWRP you are on kitkat bootloader and you can flash whatever you want that is bumped. All images based on whichever version of ROM 21A, 20H or any of the other ones you find will work on that bootloader.
To finalize, yes you can flash it the easy way with TWRP.
NatusVincere said:
Listen... Lollipop bootloader DOES NOT accept BUMP.
So what autorec app by Bender does is flash a kitkat bootloader which ACCEPTS BUMP.
Autorec also flashes the bumped TWRP to recovery partition.
So... if you have TWRP you are on kitkat bootloader and you can flash whatever you want that is bumped. All images based on whichever version of ROM 21A, 20H or any of the other ones you find will work on that bootloader.
To finalize, yes you can flash it the easy way with TWRP.
Click to expand...
Click to collapse
Clearful, thank you so much... even if uppercases may seem offensive (like you talk to a stupid who won't understand)
So if I start from an official 21A firmware, I need to:
1) Root device;
2) Install and execute Autorec;
3) Flash anything from the bumped TWRP (automatically installed by Autorec alongside the KitKat bootloader).
Simone98RC said:
Clearful, thank you so much... even if uppercases may seem offensive (like you talk to a stupid which won't understand)
So if I start from an official 21A firmware, I need to:
1) Root device;
2) Install and execute Autorec;
3) Flash anything from the bumped TWRP (automatically installed by Autorec alongside the KitKat bootloader).
Click to expand...
Click to collapse
1. root
2. install autorec for v20t or 20u
3. install rom (you already have bumped recovery because of step 2)
4. yes, you can now upgrade recovery if you find a more recent one
bender_007 said:
1. root
2. install autorec for v20t or 20u
3. install rom (you already have bumped recovery because of step 2)
4. yes, you can now upgrade recovery if you find a more recent one
Click to expand...
Click to collapse
Thanks much for the specification: since I want to flash a firmware newer than 20H, I need latest Autorec to work with that [emoji106]
https://www.androidfilehost.com/?fid=24052804347817962
After all you are the official Autorec developer
^ yap, flash safely, after that flash fulmics
That's how I was using it
Plus thx to all people involved in here for answering and helping out
Poslano sa mog LG-H815 koristeći Tapatalk