Related
Nvidia makes pre-rooted stock ROMs available via their website. You'll have to register for access, but it makes life lots easier this way. I don't know if this factory pre-rooted ROM supports OTAs, and if it does accept an OTA if it will cause loss of Root, but if you have access to the Developer site, you can always flash another pre-rooted ROM version as they become available.
https://developer.nvidia.com/shield-developer-os-images
For those who prefer a more stock system, but want some measure of control, I wanted to pass along that I was able to install Xposed, Xprivacy, TiBu and ES File Explorer to this ROM. I had to download and reapply SuperSU and allow it to relaunch/install via TWRP, but all's well.
I did this by flashing Zulu's full Android ROM first, installing some utilities, then flashing the Nvidia OEM system partition on top of it. Some apps appear on the SATV screen (ES, Xprivacy) others do not (TiBu, Xposed installer) but I'm sure there's a way to get the icons to appear.
In any event, for those who prefer the stock Nvidia look & feel, along with their installed apps, this is at least one way to get it done.
Hi there,
my shield is on stock now with several apps on it.
How can I flash without losing my data? Is it enough to NOT flash the userdata?
THX
Chaos
Hi there,
gonna answer myself.
As my bootloader was not unlocked the system got wiped anyways while unlocking it.
After that I installed the system as suggested by nvidia and restored my backup.
Concerning the root: From what I could see it is rooted for adb only. So apps don't gain root.
I ended up installing root via twrp, no imho no real advantage using the developer image.
THX
Chaos
BillTheCat said:
Nvidia makes pre-rooted stock ROMs available via their website. You'll have to register for access, but it makes life lots easier this way. I don't know if this factory pre-rooted ROM supports OTAs, and if it does accept an OTA if it will cause loss of Root, but if you have access to the Developer site, you can always flash another pre-rooted ROM version as they become available.
https://developer.nvidia.com/shield-open-source
Click to expand...
Click to collapse
I have a question, where do you find pre-root load in below link?
I only find Open source and recovery image.
you mean to modify Open source and build pre-root load?
https://developer.nvidia.com/shield-open-source
https://developer.nvidia.com/shield-developer-os-images
BillTheCat said:
https://developer.nvidia.com/shield-developer-os-images
Click to expand...
Click to collapse
thanks
hardwarechaos said:
Hi there,
gonna answer myself.
As my bootloader was not unlocked the system got wiped anyways while unlocking it.
After that I installed the system as suggested by nvidia and restored my backup.
Concerning the root: From what I could see it is rooted for adb only. So apps don't gain root.
I ended up installing root via twrp, no imho no real advantage using the developer image.
THX
Chaos
Click to expand...
Click to collapse
Have you installed SuperSu and tested it with various apps?
Im debating installing this image instead of starting all over to root the "real" way.
hardwarechaos said:
As my bootloader was not unlocked the system got wiped anyways while unlocking it.
Concerning the root: From what I could see it is rooted for adb only. So apps don't gain root.
I ended up installing root via twrp, no imho no real advantage using the developer image
Click to expand...
Click to collapse
Ditto here. Now that you've posted, it confirms what I experienced. At first, I thought I had made a mistake.
Tyler27 said:
Have you installed SuperSu and tested it with various apps?
Im debating installing this image instead of starting all over to root the "real" way.
Click to expand...
Click to collapse
Here's what I did.
Unlock bootloader (fastboot oem unlock - easy enough!)
Flash the Nvidia 2.1 ROM to ensure stock condition (I used the 'rooted' Dev edition, but I doubt it matters)
Reboot bootloader
Flash TWRP
Reboot bootloader (to reinitialize partitions)
Flash SuperSU, Xposed
Reboot into system, sideload ES File Explorer, Xprivacy, TiBu
Hi
Tyler27 said:
Have you installed SuperSu and tested it with various apps?
Im debating installing this image instead of starting all over to root the "real" way.
Click to expand...
Click to collapse
After I saw that the developer image was root for adb only, I flashed twrp recovery and installed SuperSU via twrp.
So right now I don't see any benefit over the "standard image with root".
IMHO if you have adb root there should be a way to install it via adb too, but I could not find one and didn't want to mess around with installing the SuperSU files manually.
THX
Chaos
hardwarechaos said:
After I saw that the developer image was root for adb only, I flashed twrp recovery and installed SuperSU via twrp.
So right now I don't see any benefit over the "standard image with root".
Click to expand...
Click to collapse
Agreed - turns out the Dev images are no real benefit. I found that installing TWRP, rebooting the bootloader, entering recovery and then flashing SuperSU works like a champ.
Anyone else having trouble flashing system and userdata? Keeps saying FAILED (Remote: data too large)
BillTheCat said:
For those who prefer a more stock system, but want some measure of control, I wanted to pass along that I was able to install Xposed, Xprivacy, TiBu and ES File Explorer to this ROM. I had to download and reapply SuperSU and allow it to relaunch/install via TWRP, but all's well.
I did this by flashing Zulu's full Android ROM first, installing some utilities, then flashing the Nvidia OEM system partition on top of it. Some apps appear on the SATV screen (ES, Xprivacy) others do not (TiBu, Xposed installer) but I'm sure there's a way to get the icons to appear.
In any event, for those who prefer the stock Nvidia look & feel, along with their installed apps, this is at least one way to get it done.
Click to expand...
Click to collapse
I'm on Zulu full with Amazon video working. Any idea if I go to stock rooted will that knock out the Amazon video?
jweaks said:
I'm on Zulu full with Amazon video working. Any idea if I go to stock rooted will that knock out the Amazon video?
Click to expand...
Click to collapse
Yes it will kill amazon video.
BillTheCat said:
Ditto here. Now that you've posted, it confirms what I experienced. At first, I thought I had made a mistake.
Here's what I did.
Unlock bootloader (fastboot oem unlock - easy enough!)
Flash the Nvidia 2.1 ROM to ensure stock condition (I used the 'rooted' Dev edition, but I doubt it matters)
Reboot bootloader
Flash TWRP
Reboot bootloader (to reinitialize partitions)
Flash SuperSU, Xposed
Reboot into system, sideload ES File Explorer, Xprivacy, TiBu
Click to expand...
Click to collapse
how did you flash TWRP to Nvidia through adb?? or through recovery on the Nvidia.....been reading to much can't comprehend...thanks dill
dillfever said:
how did you flash TWRP to Nvidia through adb?? or through recovery on the Nvidia.....been reading to much can't comprehend...thanks dill
Click to expand...
Click to collapse
can close this got er all done.......dill
hardwarechaos said:
Concerning the root: From what I could see it is rooted for adb only. So apps don't gain root.
Click to expand...
Click to collapse
Hello,
Same result for me.
I've just received my Shield, I've followed the instructions given on the developers web page. I have an up-to-date 3.0.0 version, but applications don't have the root authorisations (tested with ES File Explorer).
I think I'll use the TWRP method...
i download 3.0 rooted version it came a zip with all files on it on nvidia shield.com tutorial said just ento bootloader and type comand flash-all.bat and gualahhh! but try like 1000 times and always said null error message and force close adb
can some one tell what im doing wrong please and thanks people!
bye the way gamestop its selling shield tv for 100bucks so for those who want another its the right time to get one
Not trying to start drama here at all, but what steps would I need to go through in order to get off of Zulu's full Android 5.1 and on to this? I see he's gone through and deleted all of the posts detailing the process of how to install his ROMs so now I don't even know the steps that I took back in August to install that ROM in the first place. My Shield is having a very strange problem where it stutters hard every 60 seconds or so and I want to go back to stock or something vaguely stock just in case I have to RMA this thing.
dismissthesky said:
Not trying to start drama here at all, but what steps would I need to go through in order to get off of Zulu's full Android 5.1 and on to this? I see he's gone through and deleted all of the posts detailing the process of how to install his ROMs so now I don't even know the steps that I took back in August to install that ROM in the first place. My Shield is having a very strange problem where it stutters hard every 60 seconds or so and I want to go back to stock or something vaguely stock just in case I have to RMA this thing.
Click to expand...
Click to collapse
to remove zulu rom this is easy.
just go to nvidia site and get the complete factory images for your shield.
it will come with a guide on how to flash your shield with them.
it will delete everything in your shield and it will be stock like brand new.
then you can root it if you want or install a different rom.
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
Hi guys ☺,
I bought today G4 eu model,it came with Marshmallow 6.0 V20d version.
I want to root it because of Greenify and Xposed,to increase the battery time,maybe later to flash some rom but...
There is a lot of topics on this subject,I started to read but I'm lost right now...as far as I saw,I can't root Marshmallow without unlocking the bootloader,only Lollipop,right?
Is it a big trouble to go back from MM to LP?
I'm not new in this flashing and rooting stuff,I had (still have) a Motorola Razr XT910,I flashed it 100 times for sure for 3.5 years but I didn't had to unlock the bootloader (it's impossible anyway) and there's a custom recovery Safestrap,modified Twrp which allows to flash and use 6 different roms,from JB to MM,without changing the kernel...
I will be grateful if someone can point me in the right direction,to give me some useful links etc.
And is there some list which procesess are safe to freeze with TB and which ones I can greenify?
Oh,and the bloatware too...
Sorry if I'm demanding but I want to bring out the best from this phone
Thank you in advance
Sent from my LG G4
Nobody?
Sent from my LG G4
Hi,
root without unlocking bootloader works only on lollipop, right. Not sure if u can downgrade, but when, u will use "LGUP" tool with the "H81510D.kdz" file. Maybe there exists a pre-rooted kdz to flash.
If u want to root android 6, u need a unlocked bootloader. Rooted Android 5.1.1 or unlock bootloader with rooted android 6.x.x
Ok,I successfully unlocked the bootloader but now I'm stuck with rooting and installing Twrp...
I've downloaded BETA-SuperSU-v2.67-20160121175247 and TWRP-3.0.0.0-H815+ but there's a lot of metods,which one should I use?
Flash SuperSu+Twrp with stock recovery?
Install Twrp with adb command and then flash SuperSu with Twrp?
Install both with adb command?
I also saw somewhere that I must flash some other kernel that is already rooted...
I just need root and the Xposed for now,help me guys!
Im also Confused..Where can i find rooted kernel?
I already did this Method u said...But I got Boot Loop
Then I revover my phone with Lg Bridge
We need to find this.....I also Had Android MM with V20d
welder73 said:
Ok,I successfully unlocked the bootloader but now I'm stuck with rooting and installing Twrp...
I've downloaded BETA-SuperSU-v2.67-20160121175247 and TWRP-3.0.0.0-H815+ but there's a lot of metods,which one should I use?
Flash SuperSu+Twrp with stock recovery?
Install Twrp with adb command and then flash SuperSu with Twrp?
Install both with adb command?
I also saw somewhere that I must flash some other kernel that is already rooted...
I just need root and the Xposed for now,help me guys!
Click to expand...
Click to collapse
In my case I wasn't able to flash recovery on the stock kernel, I had to flash boot.img unpacked from the custom kernel like SimpleGX and only then I was able to flash recovery and full kernel through it.
welder73 said:
Hi guys ,
I bought today G4 eu model,it came with Marshmallow 6.0 V20d version.
I want to root it because of Greenify and Xposed,to increase the battery time,maybe later to flash some rom but...
There is a lot of topics on this subject,I started to read but I'm lost right now...as far as I saw,I can't root Marshmallow without unlocking the bootloader,only Lollipop,right?
Is it a big trouble to go back from MM to LP?
I'm not new in this flashing and rooting stuff,I had (still have) a Motorola Razr XT910,I flashed it 100 times for sure for 3.5 years but I didn't had to unlock the bootloader (it's impossible anyway) and there's a custom recovery Safestrap,modified Twrp which allows to flash and use 6 different roms,from JB to MM,without changing the kernel...
I will be grateful if someone can point me in the right direction,to give me some useful links etc.
And is there some list which procesess are safe to freeze with TB and which ones I can greenify?
Oh,and the bloatware too...
Sorry if I'm demanding but I want to bring out the best from this phone
Thank you in advance
Sent from my LG G4
Click to expand...
Click to collapse
the method i followed was-
1. boot into twrp recovery with adb command(you need to have the twrp.img file in PC and also copy it in internal memory of your phone with SU)
2. flash systemless root with twrp
3. reboot
4. install flashify
5.flash twrp.img from your phone.
6. done
but there aren't as much benefits of rooting as any other phone. viper4android doesn't work. spirit fm doesn't work. xposed doesn't work properly.(these 3 were the main reasons for which i rooted)
dbzgoku said:
the method i followed was-
1. boot into twrp recovery with adb command(you need to have the twrp.img file in PC and also copy it in internal memory of your phone with SU)
2. flash systemless root with twrp
3. reboot
4. install flashify
5.flash twrp.img from your phone.
6. done
but there aren't as much benefits of rooting as any other phone. viper4android doesn't work. spirit fm doesn't work. xposed doesn't work properly.(these 3 were the main reasons for which i rooted)
Click to expand...
Click to collapse
My method:
1. The same
2. The same
3. Flash twrp.img with twrp
4. Reboot to recovery
5. Reboot to the system
6. Done
Viper4android works (judging by what other people say)
I don't know about spirit fm,I don't use it
Xposed is working fine
What's your problems with Xposed btw?
Sent from my LG G4
welder73 said:
My method:
1. The same
2. The same
3. Flash twrp.img with twrp
4. Reboot to recovery
5. Reboot to the system
6. Done
Viper4android works (judging by what other people say)
I don't know about spirit fm,I don't use it
Xposed is working fine
What's your problems with Xposed btw?
Sent from my LG G4
Click to expand...
Click to collapse
I didn't know i could flash something other than .zip files with twrp.
As for viper4android i tried normal way, flashed it with twrp, flashed extreme music mod with v4a fix. None seem to work. The drivers never get installed.
Xposed i haven't tried. I was in process of getting more information about it by reading various threads. But all seem to point to problems like bootloop, fc and Bluetooth issues. Can you guide me towards the best version of xposed for v20d with way to avoid problems or with as less problems as possible?
dbzgoku said:
I didn't know i could flash something other than .zip files with twrp.
As for viper4android i tried normal way, flashed it with twrp, flashed extreme music mod with v4a fix. None seem to work. The drivers never get installed.
Xposed i haven't tried. I was in process of getting more information about it by reading various threads. But all seem to point to problems like bootloop, fc and Bluetooth issues. Can you guide me towards the best version of xposed for v20d with way to avoid problems or with as less problems as possible?
Click to expand...
Click to collapse
Here is the official Xposed thread
http://forum.xda-developers.com/showthread.php?t=3034811
Download xposed-v80-sdk23-arm64.zip and flash it with Twrp.
Download XposedInstaller_3.0_alpha4.apk and install it.
And just in case if you have a bootloop,download xposed-uninstaller-20150831-arm64.zip.
I haven't had any problems
Oh,be careful which Xposed module you install.Here is the thread of working/not working modules
http://forum.xda-developers.com/showthread.php?t=3180217
Your bootloader is unlocked,right?
Sent from my LG G4
welder73 said:
Here is the official Xposed thread
http://forum.xda-developers.com/showthread.php?t=3034811
Download xposed-v80-sdk23-arm64.zip and flash it with Twrp.
Download XposedInstaller_3.0_alpha4.apk and install it.
And just in case if you have a bootloop,download xposed-uninstaller-20150831-arm64.zip.
I haven't had any problems
Oh,be careful which Xposed module you install.Here is the thread of working/not working modules
http://forum.xda-developers.com/showthread.php?t=3180217
Your bootloader is unlocked,right?
Sent from my LG G4
Click to expand...
Click to collapse
Thanks
I am gonna try it today.
And yes my bootloader is unlocked. We can't root marshmallow without unlocking bootloader.
dbzgoku said:
Thanks
I am gonna try it today.
And yes my bootloader is unlocked. We can't root marshmallow without unlocking bootloader.
Click to expand...
Click to collapse
Flash Imperium Kernel or SimpleGX Kernel. I used their kernels and ROMS on my older phones, they are legend. I suggest you to flash Imperium Rom. It includes kernel and everything and it is updated regularly by its dev.
This is kernel thread: http://forum.xda-developers.com/g4/orig-development/kernel-imperium-kernel-g4-v1-0-t3282915
This is ROM: http://forum.xda-developers.com/g4/development/rom-imperium-rom-g4-v1-0-t3312337
---------- Post added at 10:53 ---------- Previous post was at 10:51 ----------
@welder73 I wrote wrong guy I'm sorry.
Flash Imperium Kernel or SimpleGX Kernel. I used their kernels and ROMS on my older phones, they are legend. I suggest you to flash Imperium Rom. It includes kernel and everything and it is updated regularly by its dev.
This is kernel thread: http://forum.xda-developers.com/g4/orig-development/kernel-imperium-kernel-g4-v1-0-t3282915
This is ROM: http://forum.xda-developers.com/g4/development/rom-imperium-rom-g4-v1-0-t3312337
FINALLY Root My H815 Android 6.0 V20d
Hi to all!
As you have you bootloader unlocked, you can root your h815 M6 V20d with this method.
I was looking for days, and today i found this http://www.tuttoapp-android.com/root-lg-g4-h815-e-installazione-recovery-18188/
and now my g4 is rooted
Good luck!
p.s. Firstly convert the language from italian to english or ever you want
welder73 said:
Ok,I successfully unlocked the bootloader but now I'm stuck with rooting and installing Twrp...
I've downloaded BETA-SuperSU-v2.67-20160121175247 and TWRP-3.0.0.0-H815+ but there's a lot of metods,which one should I use?
Flash SuperSu+Twrp with stock recovery?
Install Twrp with adb command and then flash SuperSu with Twrp?
Install both with adb command?
I also saw somewhere that I must flash some other kernel that is already rooted...
I just need root and the Xposed for now,help me guys!
Click to expand...
Click to collapse
Unlock bootloader
adb reboot bootloader
fastboot boot twrp-3.0.0.0-h815.img
install -> images -> twrp-3.0.0.0-h815.img
reboot -> recovery
install -> BETA-SuperSU-v2.67-20160121175247.zip
reboot system
dontpannic said:
Unlock bootloader
adb reboot bootloader
fastboot boot twrp-3.0.0.0-h815.img
install -> images -> twrp-3.0.0.0-h815.img
reboot -> recovery
install -> BETA-SuperSU-v2.67-20160121175247.zip
reboot system
Click to expand...
Click to collapse
I think doesn't need to install recovery to root the phone.
Just this:
1) adb reboot bootloader
2) fastboot boot TWRP-2-8.7.0-h815.img
Wait a second and it will open, on the phone, the recovery.
Once open go to Advanced -> ADB sideload and take a swipe to start it where it says "Swipe to Start sideload".
Now on the PC write
3) adb sideload BETA-SuperSU-v2.67-20160121175247.zip
( If it says after the instalation to install supersu etc just abort it)
And then, when installation is complete, press "Reboot System"
I rooted it this way, without install TWRP Recovery
Zanina said:
I think doesn't need to install recovery to root the phone.
Just this:
1) adb reboot bootloader
2) fastboot boot TWRP-2-8.7.0-h815.img
Wait a second and it will open, on the phone, the recovery.
Once open go to Advanced -> ADB sideload and take a swipe to start it where it says "Swipe to Start sideload".
Now on the PC write
3) adb sideload BETA-SuperSU-v2.67-20160121175247.zip
( If it says after the instalation to install supersu etc just abort it)
And then, when installation is complete, press "Reboot System"
I rooted it this way, without install TWRP Recovery
Click to expand...
Click to collapse
Yeah - but the question has to be asked - why unlock the bootloader and root and not install TWRP? If you've got as far as unlocking the bootloader you might as well make life easier for yourself and install TWRP - that way anything you want to flash in the future can be done without being tethered to the PC, and also allows you to take proper full system image backups etc.
dontpannic said:
Yeah - but the question has to be asked - why unlock the bootloader and root and not install TWRP? If you've got as far as unlocking the bootloader you might as well make life easier for yourself and install TWRP - that way anything you want to flash in the future can be done without being tethered to the PC, and also allows you to take proper full system image backups etc.
Click to expand...
Click to collapse
Of course , i agree with you. By the way, we can't root g4 on m6 without unlocked bootloader.
And finally, i decided to pass twrp on my phone, for every file i want to install from twrp, and not every time to boot from pc
You're right
p.s. the first thing i did after twrp installed, was to install g5 live wallpapers
I don't really need a custom recovery (I don't know of any features custom recovery will give me I really need?) and for now I'm fine running stock roms (I always give stock a few weeks just as a baseline before I start custom roms) but I was wondering, how would one go about rooting the OP3 without installing a custom recovery?
Is it possible / easily doable? Or am I better off just to flash some custom recovery and ditch the stock one?
The reason I don't want to go away from stock just yet is I know oneplus is still updating the rom and custom recoveries, historically, have made OTA updates problematic.
Rooting will also mess up Ota too, but if u install a custom recovery, now that we have stock recovery it will be very easy to revert back for OTAs, there should be a way to root without a custom recovery but I am not sure how though, but with how oneplus makes it so easy to unlock bootloader and flash customers stuff there is really no need to stay stock
You can simply connect your OP3 to a PC and boot to TWRP without flashing it:
fastboot boot twrp.img
Then do a backup with twrp before rooting. I use the above method with systemless root
and also don't really need a custom recovery at this point. This might change once CM13 matures on the OP3...
OTAs might work this way in the future. If they don't, restore your system + boot (kernel) partition
and try the OTA again.
edit: implying your bootloader is already unlocked
pileot said:
I don't really need a custom recovery (I don't know of any features custom recovery will give me I really need?) and for now I'm fine running stock roms (I always give stock a few weeks just as a baseline before I start custom roms) but I was wondering, how would one go about rooting the OP3 without installing a custom recovery?
Is it possible / easily doable? Or am I better off just to flash some custom recovery and ditch the stock one?
The reason I don't want to go away from stock just yet is I know oneplus is still updating the rom and custom recoveries, historically, have made OTA updates problematic.
Click to expand...
Click to collapse
As far as I know, you'd have to have TWRP to get root.
I don't think getting it rooted will mess up the OTA updates, other users sprovide flashable zips for the OTA anyway.. so you can still flash the zips manually with TWRP to keep you updated.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
To get root yes, you would need TWRP to flash to certain partitions but to keep root no. Your phone will operate just fine with root and stock recovery. Check what the user a few posts above mine said about temporary flashing TWRP to achieve your short term goals
AcmE85 said:
You can simply connect your OP3 to a PC and boot to TWRP without flashing it:
fastboot boot twrp.img
Then do a backup with twrp before rooting. I use the above method with systemless root
and also don't really need a custom recovery at this point. This might change once CM13 matures on the OP3...
OTAs might work this way in the future. If they don't, restore your system + boot (kernel) partition
and try the OTA again.
edit: implying your bootloader is already unlocked
Click to expand...
Click to collapse
So have you actually done this by temporary booting twrp and then using the systemless root and still have stock recovery? Also how do I root systemless? Really wanna know because wanna keep stock recovery and have root
TheSvensson said:
So have you actually done this by temporary booting twrp and then using the systemless root and still have stock recovery? Also how do I root systemless? Really wanna know because wanna keep stock recovery and have root
Click to expand...
Click to collapse
Yes, I have the stock recovery and it is rooted.
The recovery partition has nothing to do with all the other partitions except that it can read and write them.
This is the zip I flashed to get systemless root:
https://www.androidfilehost.com/?fid=24591000424939898
Some users reported that some Root-apps are not supported this way.
I am using Titanium Backup, Adaway, Trimmer and Root Explorer without issues.
Keep in mind that I did not get any OTA so far since running this setup, so I am not sure if official OTAs will or will not work.
All I did was manually flash OxygenOS 3.1.3 in TWRP (not flashed but booted) and reflash the root package afterwards.
AcmE85 said:
You can simply connect your OP3 to a PC and boot to TWRP without flashing it:
fastboot boot twrp.img
Then do a backup with twrp before rooting. I use the above method with systemless root
and also don't really need a custom recovery at this point. This might change once CM13 matures on the OP3...
OTAs might work this way in the future. If they don't, restore your system + boot (kernel) partition
and try the OTA again.
edit: implying your bootloader is already unlocked
Click to expand...
Click to collapse
I have an unlocked bootloader and tried this on my PC:
C:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.709s]
booting...
OKAY [ 0.373s]
finished. total time: 1.092s
Nothing happens, bootloader start screen stays frozen. Until I hold down the power button. Might you know why?
AcmE85 said:
You can simply connect your OP3 to a PC and boot to TWRP without flashing it:
fastboot boot twrp.img
Then do a backup with twrp before rooting. I use the above method with systemless root
and also don't really need a custom recovery at this point. This might change once CM13 matures on the OP3...
OTAs might work this way in the future. If they don't, restore your system + boot (kernel) partition
and try the OTA again.
edit: implying your bootloader is already unlocked
Click to expand...
Click to collapse
i tried to boot into twrp recovery with above command, but the phone seems to be stuck in the bootloader and not responding. Any ideas?
edit: comment above describes exact same behaviour, sorry for double post
Sorry, don't know. Booting takes a couple seconds on my device though.
I am using this recovery img: http://www6.zippyshare.com/v/iK6tCE6D/file.html
Got it from XDA, but unfortunately don't know anymore who build it.
AcmE85 said:
Sorry, don't know. Booting takes a couple seconds on my device though.
I am using this recovery img: http://www6.zippyshare.com/v/iK6tCE6D/file.html
Got it from XDA, but unfortunately don't know anymore who build it.
Click to expand...
Click to collapse
Thanks, that twrp img worked for me. The one I was using didnt allow me to boot to it.
AcmE85 said:
Keep in mind that I did not get any OTA so far since running this setup, so I am not sure if official OTAs will or will not work.
Click to expand...
Click to collapse
Any chance you know if you get OTA by now?
I really like the Op3 and dont wont to change anything except i would like to habe root access. Your method seems to be the best way to achieve that.
hahamuntz said:
Any chance you know if you get OTA by now?
I really like the Op3 and dont wont to change anything except i would like to habe root access. Your method seems to be the best way to achieve that.
Click to expand...
Click to collapse
The updater will recognize root on your device and download the full 1.3 gb Rom file.
But after updating root will be gone, so you will have to reflash root after each ota.
AcmE85 said:
The updater will recognize root on your device and download the full 1.3 gb Rom file.
But after updating root will be gone, so you will have to reflash root after each ota.
Click to expand...
Click to collapse
Thanks for the quick answer
Just to make sure, if I root using this method nothing will change, except I have root access, my bootloader is unlocked and the updates will be big, but I can update the normal way, I will just lose the root access? Is that correct or am I missing something?
hahamuntz said:
Thanks for the quick answer
Just to make sure, if I root using this method nothing will change, except I have root access, my bootloader is unlocked and the updates will be big, but I can update the normal way, I will just lose the root access? Is that correct or am I missing something?
Click to expand...
Click to collapse
One more thing:
If you have TWRP, automatically installing the big OTA will remove it and go back to the stock recovery.
I always manually move the downloaded ota from android/data/com.oneplus.ota/files/.OnePlusOta
to my download folder, boot into TWRP and flash it + SuperSU on my own.
AcmE85 said:
One more thing:
If you have TWRP, automatically installing the big OTA will remove it and go back to the stock recovery.
I always manually move the downloaded ota from android/data/com.oneplus.ota/files/.OnePlusOta
to my download folder, boot into TWRP and flash it + SuperSU on my own.
Click to expand...
Click to collapse
So you have TWRP installed? I thought you won't get OTAs if you have a custom recovery? So i could just flash TWRP and root and still get OTAs?
hahamuntz said:
So you have TWRP installed? I thought you won't get OTAs if you have a custom recovery? So i could just flash TWRP and root and still get OTAs?
Click to expand...
Click to collapse
Yes, OTAs will come and because of Root you will get the full OTA regardless, which does not cause any issues with TWRP.
I tried my previous method and the regular OTA would fail because of root which changes the kernel or the system partition.
OnePlus reacted to this and introduced the full rom OTAs at some point.
So with root on my device this is how I do OTAs now:
- get the OTA notification for the full rom
- download but don't install
- move the downloaded zip from android/data/com.oneplus.ota/files/.OnePlusOta to my download folder
- manually boot into twrp and flash full rom zip + SuperSU
AcmE85 said:
Yes, OTAs will come and because of Root you will get the full OTA regardless which does not cause any issues with TWRP.
Click to expand...
Click to collapse
Okay, thanks so much for your help
This Rooted Combination Firmware that can be used for various reasons that include changing carrier codes, entering service menus and various secret dialer codes. The firmware is rooted and also has Safestrap recovery installed. This is not meant to be used as an everyday rom this is only intended to achieve root or use combo firmware tools with added feature of root. This is for V5 Bootloader devices
Directions If Coming From Stock Unrooted/Rooted Phone
COMBINATION_FA70_G955USQU5ARH8_SAMFAIL_ROOTED_V5.7z
This may wipe your phone
Unzip the above zips
If already on safestrap do step 1 then reboot to safestrap and skip to step 7
Reboot phone to download mode
Use the Odin3_v3.13 provide above
1. In odin select BL_COMBINATION_FA70_G955USQU5ARH8_PART_1_AND_3.tar.md5 and load in BL slot of odin do not change the options make sure Auto Reboot and F.Reset Time are checked Click Start
2. Phone will automatically reboot as soon as phone powers off hold buttons to reboot back to download
3. In odin make sure to click reset button then in AP slot in odin choose AP_SAFESTRAP_RESCUE_SYSTEM_IMAGE.tar.md5 make sure Auto Reboot and F.Reset Time are checked Click Start
4. When don flashing it will say fail in odin and phone will reboot. Reboot phone to download. If phone reboots to upload mode force it to reboot too download mode
5. In odin make sure to click reset button then in BL slot in odin choose BL_COMBINATION_FA70_G955USQU5ARH8_PART_1_AND_3.tar.md5 make sure Auto Reboot and F.Reset Time are checked Click Start
6. When done flashing phone will reboot too safestrap if it doesnt force reboot to recovery and wipe data
7. When booted to safestrap copy COMBO_SYSTEM.img to phone
8. In safestrap choose install select install image and choose COMBO_SYSTEM.img and flash to system
9. When done if you have not wiped data then choose wipe in safestrap then advanced wipe and select to wipe data. Wipe and reboot
Mine
bootloop
erase data cache
bootloop
deadedge7 said:
hi
flash bl back bootloader flash ap fail back bootloader flash bl
sure Auto Reboot and F.Reset Time are checked Click Start all step
Erase data and cache blocked screen startup
Return recovery erase data and cache also blocked
Click to expand...
Click to collapse
I have no clue what you are saying. Please try to explain again
Sent using some kind of device I modified
deadedge7 said:
bootloop
erase data cache
bootloop
Click to expand...
Click to collapse
I am uploading new stuff with different directions that will fix problems
Sent using some kind of device I modified
nice thank you:good:
How to use it to change carrier. I do not want safestrap. Also will it trip knox?
AhmedKhan123 said:
How to use it to change carrier. I do not want safestrap. Also will it trip knox?
Click to expand...
Click to collapse
There are lots of forums how to do this. The firmware is rooted which even makes it easier. It does not trip knox and if you are smart you will use that safestrap you dont want and use it to make an efs backup before changing carrier
jrkruse said:
There are lots of forums how to do this. The firmware is rooted which even makes it easier. It does not trip knox and if you are smart you will use that safestrap you dont want and use it to make an efs backup before changing carrier
Click to expand...
Click to collapse
I know there are forums and I've even tried them, but none of them permanently changes phone's own csc. I was asking about changing original csc i.e from SPR/SPR/SPR to TMB/TMB/TMB. Please help me out in this regard. Also, tell me how to go back from safestrap to stock original. It is the only reason I'm not installing safestrap as i don't know how to go back to stock firmware with stock recovery.
Thanks in advance.
AhmedKhan123 said:
I know there are forums and I've even tried them, but none of them permanently changes phone's own csc. I was asking about changing original csc i.e from SPR/SPR/SPR to TMB/TMB/TMB. Please help me out in this regard. Also, tell me how to go back from safestrap to stock original. It is the only reason I'm not installing safestrap as i don't know how to go back to stock firmware with stock recovery.
Thanks in advance.
Click to expand...
Click to collapse
Well If you have a sprint sim it will change it to sprint the csc stuff is set by what sim you have you could manipulate this on earlier versions of nougat but not now. It is possible to use TMO csc on sprint but you would have to run a safetrap system so you can modify the csc features .xml If you want to go back to stock firmware you simply flash it. Safetrap does not replace the stock recovery. You can still boot to stock recovery with safetrap installed
jrkruse said:
Well If you have a sprint sim it will change it to sprint the csc stuff is set by what sim you have you could manipulate this on earlier versions of nougat but not now. It is possible to use TMO csc on sprint but you would have to run a safetrap system so you can modify the csc features .xml If you want to go back to stock firmware you simply flash it. Safetrap does not replace the stock recovery. You can still boot to stock recovery with safetrap installed
Click to expand...
Click to collapse
Thanks for the quick response. Now if I've to restore full stock firmware to sale my phone, i just have to flash the stock firmware right? Also, using safestrap, can i perform the modifications to system files which require root?
AhmedKhan123 said:
Thanks for the quick response. Now if I've to restore full stock firmware to sale my phone, i just have to flash the stock firmware right? Also, using safestrap, can i perform the modifications to system files which require root?
Click to expand...
Click to collapse
Yes and yes
Sent using some kind of device I modified
jrkruse said:
Yes and yes
Sent using some kind of device I modified
Click to expand...
Click to collapse
Thanks for guiding
Edit: Can I use safestrap to Flash Magisk and have root on Snapdragon? If that can happen, it would be a great deal!
AhmedKhan123 said:
Thanks for guiding
Edit: Can I use safestrap to Flash Magisk and have root on Snapdragon? If that can happen, it would be a great deal!
Click to expand...
Click to collapse
Magisk does not work on locked bootloader
Sent using some kind of device I modified
If I understand correctly... this will allow root, not trip Knox and not give the 80% battery issue. Is this correct?
533y4 said:
If I understand correctly... this will allow root, not trip Knox and not give the 80% battery issue. Is this correct?
Click to expand...
Click to collapse
Root uses combo bootloaders so yes it is limited to 80% battery. If you choose to use pie or oreo you will have safestrap recovery but no root and there will be no battery restrictions
This combo firmware is not meant to be used as everyday firmware. Its only a tool to do certain functions that are not possible on regular firmware
Sent using some kind of device I modified
jrkruse said:
Root uses combo bootloaders so yes it is limited to 80% battery. If you choose to use pie or oreo you will have safestrap recovery but no root and there will be no battery restrictions
This combo firmware is not meant to be used as everyday firmware. Its only a tool to do certain functions that are not possible on regular firmware
Sent using some kind of device I modified
Click to expand...
Click to collapse
So if I am on Oreo, is there a way to root Oreo on V5 bootloader?
I am mainly looking to use my S8+ as a audio/gaming device, as I use my Note 9 for my everday device. I am usually pretty good with the rooting thing (many years of doing) but this is the first time I`d be using safestrap and not to sure about how this works.
Thank you for your patience.
jrkruse said:
Root uses combo bootloaders so yes it is limited to 80% battery. If you choose to use pie or oreo you will have safestrap recovery but no root and there will be no battery restrictions
This combo firmware is not meant to be used as everyday firmware. Its only a tool to do certain functions that are not possible on regular firmware
Sent using some kind of device I modified
Click to expand...
Click to collapse
533y4 said:
So if I am on Oreo, is there a way to root Oreo on V5 bootloader?
I am mainly looking to use my S8+ as a audio/gaming device, as I use my Note 9 for my everday device. I am usually pretty good with the rooting thing (many years of doing) but this is the first time I`d be using safestrap and not to sure about how this works.
Thank you for your patience.
Click to expand...
Click to collapse
Notice the big letters
I seen that. I suppose I should've been more specific. I understand safe strap only. If I flash ChainFires SuperSu zip, could root be obtained?
Is obtaining root on Oreo at all possible, basically is what I'm asking.
533y4 said:
I seen that. I suppose I should've been more specific. I understand safe strap only. If I flash ChainFires SuperSu zip, could root be obtained?
Is obtaining root on Oreo at all possible, basically is what I'm asking.
Click to expand...
Click to collapse
No it currently is not possible
Sent using some kind of device I modified