Hi, guys...I just unrooted, factory restored, and used flashtool to fully restore my sprint lgls990 following some connectivity issues. My phone is currently on android 4.4.2.
I am seeking some advice/help on basically end-to-end help. Initially, I used stump to root my phone and then installed xposed and a few other items.
What I want to do now is run the easiest root possible, create a backup, and then install a custom rom. Specifically, I'd like to use CM10 CM11: Royal Blue Cobalt from the Play Store.
I have a strong concern about rom stability, though. I want/need lte data, wifi, phone, playstore, maps, and the like, but don't want to sprint bloatware crap. Is that what a custom ROM does, keep the essentials and dump the carrier crap?
So:
I think using stump will be the easiest root process.
I have read lots about twrp, but haven't found very good instructions for a noob like me, can anyone point me to "the" thread for installing and using twrp?
Where do I find the rom so I can use the theme I have noted above?
Basically, I'm looking for a roadmap for the threads I'll need to accomplish this.
Thanks in advance for helping this noob...
Bump for a little help, please...
Is there a one-stop shop for rooting, backing up, and installing a custom ROM?
Ok - re-used stump root to re-root my phone. Dl'd root checker to confirm and it confirmed rooted. Though root checker says to dl supersu to verify root, I didn't initially. Subsequently, dl'd supersu, granted root checker access, and confirmed root.
Now I wonder if I back up now or if I should have backed up before root? Answer: Seems that I cannot make a nandroid backup without recovery and to have recovery my boot loader needs to be unlocked, er rooted, right?
Edit:
Seems unlocking the boot loader is different than rooting the phone.
I suppose I can just use TWRP to back up the device?
Edit 2:
Okay, using this site - http://lg-g3.wonderhowto.com/how-to/unlock-bootloader-install-custom-recovery-lg-g3-0157830/ - I dl'd flashify, dl'd my ls990 img to the phone via the guide and will install next.
Edit 3:
Successfully installed the lg ls990 .img via Flashify; re-booted into twrp; and successfully created a backup. Then I connected the g3 to my pc and moved the very large backup file to my pc.
Edit 4:
I didn't include EFS in the back up...problem? No problem, just did another backup and chose all options available.
Now on to installing a cm rom...
Edit 5:
Looking for a CM 11 rom for my ls990...found one but the bluetooth doesn't work - http://forum.xda-developers.com/sprint-lg-g3/orig-development/rom-cyanogenmod-11-ls990-t2941164? Dafuq?
Edit 6:
Done for the night...no custom ROM. I thought most of the CM 11s would be sorted out by now, but alas, not so.
I'd really like to get a fully customized theme on this phone and thought going to CM 11 would get me there...
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
i had to root my htc 816g after the lollipop update cuz the small internal memory size and i couldn't even update the soft apps
i used TWRP
i just want to downgrade it to kitkat with the right steps and the right stock
i want to be able to apply the official updates too so can i or i will never be able to since i rooted it before ?!
i don't have enough info about rooting or backing up so pls try to explain
ShakeItBaby said:
hi
i had to root my htc 816g after the lollipop update cuz the small internal memory size and i couldn't even update the soft apps
i used TWRP
i just want to downgrade it to kitkat with the right steps and the right stock
i want to be able to apply the official updates too so can i or i will never be able to since i rooted it before ?!
i don't have enough info about rooting or backing up so pls try to explain
Click to expand...
Click to collapse
I have the 816 a5_chl single SIM version but let me try to help you because I'd like to. First I believe the rooting methods for your device is a bit different then the one for mine so bear with me here. First I would advise against going backwards to kit Kat from lollipop. Lollipop returned the write permissions to the external SD card for apps that were taken away with kitkat and that's just for starters. Lollipop has battery and performance improvements as well. As for doing stock updates you would need to find and reflash your stock recovery back as well as remove any root exploits from your firmware before any signed stock updates could be performed. What was the root method you used on your model ? Mine was to unlock boatloader thru HTC, flash TWRP recovery and from that recovery flash SuperSU zip file from internal storage of phone.
As for backing up you would first run a backup from TWRP to your ext SD card called a full nandroid backup which is basically a snapshot of your whole phone as it is before you flash any other firmware. Enable compression and leave the MD5 check enabled then name your backup and select micro SD card as the location then swipe to run. Titanium Backup app is used to back up apps and data along with texts and call logs. Google's own backups can be setup from your phone settings and back up your contacts and phone numbers mainly. Super Backup app can also back up your calender as well as texts, call logs, etc.... I use all 3 myself plus the TWRP backup that you can restore if something gets messed up and it often can.
thoctor said:
I have the 816 a5_chl single SIM version but let me try to help you because I'd like to. First I believe the rooting methods for your device is a bit different then the one for mine so bear with me here. First I would advise against going backwards to kit Kat from lollipop. Lollipop returned the write permissions to the external SD card for apps that were taken away with kitkat and that's just for starters. Lollipop has battery and performance improvements as well. As for doing stock updates you would need to find and reflash your stock recovery back as well as remove any root exploits from your firmware before any signed stock updates could be performed. What was the root method you used on your model ? Mine was to unlock boatloader thru HTC, flash TWRP recovery and from that recovery flash SuperSU zip file from internal storage of phone.
As for backing up you would first run a backup from TWRP to your ext SD card called a full nandroid backup which is basically a snapshot of your whole phone as it is before you flash any other firmware. Enable compression and leave the MD5 check enabled then name your backup and select micro SD card as the location then swipe to run. Titanium Backup app is used to back up apps and data along with texts and call logs. Google's own backups can be setup from your phone settings and back up your contacts and phone numbers mainly. Super Backup app can also back up your calender as well as texts, call logs, etc.... I use all 3 myself plus the TWRP backup that you can restore if something gets messed up and it often can.
Click to expand...
Click to collapse
first thx for reply
so if i just wanna stay with lolipop and just unroot it what should i do
i used TWRP and i backed up my rooted system days ago
i tried many times to unroot using the unroot option in supersu but nothing happened
so could u pls tell me the steps
like what stock i should download and how to install it ?!
ShakeItBaby said:
first thx for reply
so if i just wanna stay with lolipop and just unroot it what should i do
i used TWRP and i backed up my rooted system days ago
i tried many times to unroot using the unroot option in supersu but nothing happened
so could u pls tell me the steps
like what stock i should download and how to install it ?!
Click to expand...
Click to collapse
Your welcome. Ok, you did good by doing a TWRP backup first. You'd be surprised how many people don't so kudos for that. Second you shouldn't need to find a stock zip firmware file to download as long as your system is pure stock and you've reflashed your stock recovery for your model phone. Those are usually found either here in XDA linked or you just have to try to enter your model found listed in your hboot or in settings under about phone. Once you've verified the correct stock recovery zip file you download it to your P.C.s ADB/fastboot folder and flash it over TWRP then relock your boatloader. Some say they can flash stock updates with it unlocked but most recommend you relock it for it to work. From there assuming the unroot method has worked you should be able to do stock updates from your phone or over a computer using HTCsync assuming nothing else was altered in your firmware system from stock.
You say that unrooting thru SuperSU hadn't worked. How do you know that? Have you used a root checker from the play store to verify? It should work because he wrote that into his app specifically to unroot for stock updates or to use someone else's superuser app.
Also what was your rooting method? I believe your phone is the Mediatek version and the Snapdragon processor in my version had a different root exploit or an extra step from my exploit to get a foothold in your system as the processor is different from mine. You would need too remove that exploit as well I believe as it probably altered some system files to allow SuperSU to use it's exploit to gain root permissions.
Found this link below on the web but can't vouch for whether it works or not.Also search here in XDA forums for unroot method as this link says it compiled the info from XDA. Remember you'll still need your stock recovery reflashed before your can do a stock update as this refers to just unrooting.
http://android-unroot-guide.xyz/htc-desire-816g-dual-sim/
Hello everyone
so finally also C432 has received Oreo update !
right now i'm on B189 with root , bootloader unlocked and device decrypted (and twrp)
now the question is....
how can i upgrade to Oreo and and keep device decrypted bootloader unlocked without losing everything and install all again?
is there any way to achieve it? thank you for your help/suggestions !:fingers-crossed:
none? is not possible? It'll just delete everything again?
Hi.. I've done rooting Oreo but it's not properly rooted though. If you're already rooted then search DUK_fullOTA_flasher.zip and follow instructions. You'll get Oreo installed without loosing anything and still unlocked bootloader but you'll loose TWRP and decryption. Copy update.zip file from phone to pc and then use HuaweiUpdateExtractor on pc and extract Ramdisk.img from UPDATE. APP from the 'update.zip' and put it back in phone. Then use Magisk manager to patch this img file and then move it back to pc after patching. Then use adb/fastboot method to flash it. Voila!! You're rooted but device is still encrypted. I've not done any factory reset/data wipe bcz don't wanna loose my data. Device encryption won't let you use any module and you can't change anything apart from using systemless hosts AdAway and also you can use Greenify or TB but can't use any feature that writes to system.
puneetbhagat said:
Hi.. I've done rooting Oreo but it's not properly rooted though. If you're already rooted then search DUK_fullOTA_flasher.zip and follow instructions. You'll get Oreo installed without loosing anything and still unlocked bootloader but you'll loose TWRP and decryption. Copy update.zip file from phone to pc and then use HuaweiUpdateExtractor on pc and extract Ramdisk.img from UPDATE. APP from the 'update.zip' and put it back in phone. Then use Magisk manager to patch this img file and then move it back to pc after patching. Then use adb/fastboot method to flash it. Voila!! You're rooted but device is still encrypted. I've not done any factory reset/data wipe bcz don't wanna loose my data. Device encryption won't let you use any module and you can't change anything apart from using systemless hosts AdAway and also you can use Greenify or TB but can't use any feature that writes to system.
Click to expand...
Click to collapse
thank you for your kind and full answer I appreciate it! seems like I'll have to wait cause having device decrypted is a must as is a must to have it rooted! I'll stick to b189 until a better way is found [emoji4]
Sent from my DUK-L09 using Tapatalk
simika said:
thank you for your kind and full answer I appreciate it! seems like I'll have to wait cause having device decrypted is a must as is a must to have it rooted! I'll stick to b189 until a better way is found [emoji4]
Sent from my DUK-L09 using Tapatalk
Click to expand...
Click to collapse
Any time mate :good:
I know there is a method to decrypt it but I really don't wanna lose my data. Here is the link:
https://forum.xda-developers.com/honor-8-pro/how-to/guide-magisk-root-honor-8-pro-oreo-t3743587
I have a LG G4 since almost the release of it. I had it rooted and with an unlocked bootloader since now. I decided to use it as my daily though to pay with it using Google Pay. So I re-flashed the stock v29a zip provided by LG and did the "fastboot oem lock" command. The bootloader locked, the rom is fully stock now without any modification. Why Google pay still says that the phone is altered and after checking Safetynet with an app on play store, fails? Also On Play Store the phone appears Uncertified... What is the problem?
ntelas said:
I have a LG G4 since almost the release of it. I had it rooted and with an unlocked bootloader since now. I decided to use it as my daily though to pay with it using Google Pay. So I re-flashed the stock v29a zip provided by LG and did the "fastboot oem lock" command. The bootloader locked, the rom is fully stock now without any modification. Why Google pay still says that the phone is altered and after checking Safetynet with an app on play store, fails? Also On Play Store the phone appears Uncertified... What is the problem?
Click to expand...
Click to collapse
Just an idea, take a look at your build.prop and see if anything looks off. Maybe you need to format some partitions before flashing the stock zip?
Cheers!
Thanks for the reply. I think the zip is flashing all the partitions.I checked for TWRP and did a factory reset after the flash to make sure it's as stock as it can get. Now for the build.prop I also think that it needs root to check and edit it right? If not what sould I look for?
ntelas said:
Thanks for the reply. I think the zip is flashing all the partitions.I checked for TWRP and did a factory reset after the flash to make sure it's as stock as it can get. Now for the build.prop I also think that it needs root to check and edit it right? If not what sould I look for?
Click to expand...
Click to collapse
I think that certain partitions need to be formatted you might want to search about that. I think TWRP can access the build.prop but not sure. I suggested checking build.prop because it will show different models, builds and basically would be an easy way to see if you are truly back to stock.
Good luck!
Thanks! I would have to install TWRP again maybe ?
ntelas said:
Thanks! I would have to install TWRP again maybe
Click to expand...
Click to collapse
Didi you Unroot before Flashing Stock?
Maybe some remants in Some Partitions are causing you trouble.
uweork said:
Didi you Unroot before Flashing Stock?
Maybe some remants in Some Partitions are causing you trouble.
Click to expand...
Click to collapse
I flashed stock coming from a RR rom with Magisk. Believe me if I had locked bootloader with a rooted rom now I wouldn't have my phone alive
ntelas said:
I flashed stock coming from a RR rom with Magisk. Believe me if I had locked bootloader with a rooted rom now I wouldn't have my phone alive
Click to expand...
Click to collapse
Then You didn´t read Properly.
I didn´t mean Root itself more Remnant parts of Root, that cause ur Saftynet fail.
on Samsung S2 once i thought so too, but banking app said no no no...
Only an Option
a user from this forum said that you need to take the line "ro.build.firgenprint=..." of the any MM/LP build.prop and insert it into the N build.prop (including reboot btw) and try again if google pay works for you...
I don't know if it works, I don't tried it, but you say us.