Related
I want to be sure my DS can receive and install the imminent (?) ota ICS from HTC. Still a bit of a noob so read a lot of stuff on here and other forums (mainly non DS) but haven't really found definitive answers for the 'half rooted' device i.e. bootloader unlocked via htcdev, cwm flashed, s-on.
Main concerns are:
losing root
ota will not install because of /system/app and framework mismatch (after a few UOT mods) - boot animation and sound have also been changed in /system/customise/resource, also bloatware removed
ota issues with cwm installed
Originally first thing I did immediately after flashing cwm was a nandroid backup so that's available to me, which really only leaves the cwm and ota compatability question.
Is Rootkeeper an option or should I root from scratch again after ota?
If I receive notification of the ota availability, then restore from original backup (and maybe relock bootloader with htcdev?) will I then have lost the chance to install the ota?
A lot of questions and ifs, I know, I just don't want to screw up the chance to try the official ICS before going for a custom rom. Thanks in advance.
Hboot 2.00.0002
Android 2.3.5
Sense 3.0
Stock rom/kernel/radio
Sorry, I'm pretty sure HTC Dev unlocked devices can't get OTA updates. I'm completely sure devices with CWM can't (you need stock HTC recovery). Since you already have a custom recovery, it would be better to get a custom ROM, much fastr and tweaked
As shrome99 said..
To get the OTA update you will need to have STOCK recovery, and a relocked bootloader to get the OTA.
__________________
This assumes you are 100% stock on the operating side.
foX2delta said:
As shrome99 said..
To get the OTA update you will need to have STOCK recovery, and a relocked bootloader to get the OTA.
__________________
This assumes you are 100% stock on the operating side.
Click to expand...
Click to collapse
I got OTA updates with both an unlocked bootloader and custom recovery. It's true the update won't install till you're back on stock recovery but the locked bootloader isn't necessary. I was however updating from Stock Sense 2.1
Warning: do not install it if you get a OTA message if rooted!
It will lead to the dreaded red triangle screen. Your best bet is to just install CWM/4EXT then when the new update comes, install the ICS prerooted ROM by Adidas.
Sent from my HTC Desire S using xda premium
The "dreaded" triangle screen is just the stock recovery.
Jack_R1 said:
The "dreaded" triangle screen is just the stock recovery.
Click to expand...
Click to collapse
That won't boot back to your ROM therefore you are stuck.
No root/s-off, therefore you can't do much about it. (Unless you get the RUU to run)
And for the average user, this is difficult for them to understand. Hence it has picked up its name as the 'dreaded triangle screen' over several different HTC device threads.
Sent from my HTC Desire S using xda premium
Cheers for the input.. did a bit more snooping and (if and when I get the ota shout).. I think I can go back with original nandroid to pre-root, before superuser went in. Then I'll give Android Recovery Manager (Sensation Android Development forum) a lash, just to see if I can flash back the stock recovery img.
If any nice ota comes my way which won't take then I'll try htcdev to relock the bootloader and give it another lash!
Think (hope) it'll work.. couldn't find a stock img anywhere yet so I'm hoping it's included in the above manager.. was going to try tonight but, typical, my connection went..
'Your best bet is to just install CWM/4EXT then when the new update comes, install the ICS prerooted ROM by Adidas.'
I have cwm, not sure why I would wait for the update then install a custom ics rom..
You must install stock recovery to install OTA update.OTA won't install, if you have custom recovery or S-off.But I recommend to install ROM, using zip or RUU.
From htcdev:
(after unlocking bootloader) Some content on your device may also be invalidated and cannot be accessed any more because of invalid DRM security keys. This includes content that you may have purchased through a 3rd party vendor and through HTC. Furthermore, although you will still be able to receive updates to your device via FOTA (“firmware over the air”), we do not guarantee that updating your device via FOTA will not render your device unusable.
That answers the question re the bootloader but I'm struggling to find the stock recovery img to flash.
I suppose I can extract and then flash it, possibly from this: RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30.0822U_3822.10.08.04_M_release_219480_signed.exe, even though my device is 2.10.161.3 (161 is Vodafone). The radio is the same as mine which is irrelevant anyway, right?
I know it would be easier to install the RUU but after hours of research I would really like to be able to nail this so I have the option of reverting back to VF stock, as I still have 18 months warranty left.
Can anyone can confirm if I'm on the right track pls?
I suppose, if you haven't GoldCard or SuperCID recovery won't flash(signature verify failed).Download Zip/exe of your ROM , and flash that recovery.After that you might be able to install FOTA.No guarantee it will work.
scandron said:
I suppose, if you haven't GoldCard or SuperCID recovery won't flash(signature verify failed).Download Zip/exe of your ROM , and flash that recovery.After that you might be able to install FOTA.No guarantee it will work.
Click to expand...
Click to collapse
It will flash, because his bootloader is unlocked.
He won't need a goldcard cause he is flashing a voda RUU recover, future I don't think it will even come into play when using fastboot to flash it.
However I suggest EVERYONE who is a little unsure make a goldcard.
Thanks all, trying to get a gold card now just to be sure.. however just intend to extract and flash the recovery img from the ruu, once I can be sure I have the right one.. the stock recovery in HTC devices is generic, no?
i also have a doubt.
what i wanted to know is that will i still be able to update my device OTA if i have unlocked the bootloader, rooted my device but havent installed a custom recovery?my device is rooted nothing more than that. and after relocking my bootloader (i dont mind loosing root) will i be able to update OTA?
sorry for being irrelevant but i didnt want to start a new thread for a doubt of this magnitude.
See post #10
Has anyone tried to root their i9023 with 4.0.4 using doomlord's easy rooting toolkit? http://forum.xda-developers.com/showthread.php?t=1321582
I tried it when I had 2.3.6 and it worked perfectly but want to update to 4.0.4 now.
If doomlord's doesn't work, is there any similar one click rooting? Also, when I rooted, it didn't erase my data and apps. Will that be the same? Thanks
I guess not. Been searching and couldn't find a non-destructive one and one as a simple click without needing cwm.
There's none that I am aware of. However, it's not really that complicated to flash the right SU zip, and if you don't want to flash cwm you can simply fastboot boot cwm.img and it will leave stock recovery intact and ready after you flashed everything.
Sent from my Nexus S using XDA
Couple things if you're already rooted on gingerbread do a nandroid back up. Put that and anything else you want to keep on your computer. Unlock the bootloader and restore your backup and update.
Stop messing around and unlock the bootloader.
albundy2010 said:
Couple things if you're already rooted on gingerbread do a nandroid back up. Put that and anything else you want to keep on your computer. Unlock the bootloader and restore your backup and update.
Stop messing around and unlock the bootloader.
Click to expand...
Click to collapse
How can he do a backup if the bootloader is locked = no cwm recovery? He's out of luck. Best thing he can do is backup the SD card and that's it. The rest is lost
Edit: failed to read sorry. Didn't notice the gingerbread part. Anyway if he's on stock and one clicked rooted he still doesn't have cwm so he can't make a nandroid, he can use titanium backup and save apps and data.
Sent from my
( •_•)
( •_•)>⌐■-■
Nexus S
(⌐■_■)
YYYYYYYEEEEEAAAAAAAAAAHHHHHHHHHHHH
If he is stock rooted he can flash cwm in the os. Either through rom manager or terminal
albundy2010 said:
If he is stock rooted he can flash cwm in the os. Either through rom manager or terminal
Click to expand...
Click to collapse
I thought that locked bootloader prevented the flash of any kind of unsigned .img even if you have root.
Guess i was wrong ;D
That's what you get when your first step with an android phone is unlock the bootloader
Not a one size fits all. Some phones all you need is root to flash a custom recovery and roms/kernels.
Others it can be a mess. Like the HTC g2 or even now the one x on att. Got the entire s on/ s off encryption nonsense and so on.
DeuXGod said:
I thought that locked bootloader prevented the flash of any kind of unsigned .img even if you have root.
Guess i was wrong ;D
That's what you get when your first step with an android phone is unlock the bootloader
Click to expand...
Click to collapse
He can flash a new recovery through the OS if he has root access only. Unlocked bootloader only provides fastboot support.
If you are fully stock (bootloader, recovery, no su), the only current way to root 4.0.4 is to have an unlocked bootloader.
albundy2010 said:
Not a one size fits all. Some phones all you need is root to flash a custom recovery and roms/kernels.
Others it can be a mess. Like the HTC g2 or even now the one x on att. Got the entire s on/ s off encryption nonsense and so on.
Click to expand...
Click to collapse
Yeah that's what make my confusion. My old HTC Magic needed unlocked bootloader to flash a recovery.
Harbb said:
He can flash a new recovery through the OS if he has root access only. Unlocked bootloader only provides fastboot support.
If you are fully stock (bootloader, recovery, no su), the only current way to root 4.0.4 is to have an unlocked bootloader.
Click to expand...
Click to collapse
Yeah about that i was pretty sure you needed unlocked bootloader, but about CWM flash i was convinced that you needed also unlocked bootloader, but as stated above, it's just for some devices.
Thank to all that responded. All this talk just flew over my head ... guess that's what I get for using simple one clicks
Let me try to straighten some stuff out.
How would I use titanium backup?
Do I titanium backup while it's still on gingerbread or after I OTA the ics 4.0.4?
Edit: duh! I can't use Ti backup after OTA ics because phone not rooted yet.
After backing up with Ti, I thought any attempt to root will erase all. Does the Ti backup not get erased?
Ti backup only backs up my app and the data to those apps, not how I customize my homescreen's widgets and notification bar, right?
So, I would have to do all that stuff over?
If I don't want to unlock bootloader or install cwm, any way to root and leave stock recovery intact?
Lazer Bear posted "if you don't want to flash cwm you can simply fastboot boot cwm.img and it will leave stock recovery intact and ready after you flashed everything."
Is that possible and how do I do it? Does that erase everything too?
Thanks to all!
bump
A while back, I always rooted and unrooted my Nexus S with no problems at all. Now whenever I try to root it, it just goes wrong. I've tried TWRP & CWM, CWM used to always work but now it just messes up. Both TWRP and CWM both give me an error that say Installation Aborted when I try to install a custom rom. I've redownloaded the rom from different browsers and even different PCs but nothing working, still that same error. Does anyone have a guide that is 100% to work without any errors during the process?
What guide are you using?
paul96 said:
What guide are you using?
Click to expand...
Click to collapse
I used this one: http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/
1. Make sure you're running one the more recent versions of the custom recovery. You probably are but there are issues with older versions so just make sure.
2. Boot into what ever recovery you pick and do a full wipe. That is everything gets wiped but your SD card. Factory reset. Format /system etc.
3. Flash your ROM and gapps if they are seperate.
You should not get any errors. If your recovery is current and your flashing a new rom onto a fully wiped system and you still get a error either you're screwing something up or you may have a hardware problem.
To rule out a hw problem flash the factory images with fastboot. If those flash normally and everything works it is almost certainly user error.
albundy2010 said:
1. Make sure you're running one the more recent versions of the custom recovery. You probably are but there are issues with older versions so just make sure.
2. Boot into what ever recovery you pick and do a full wipe. That is everything gets wiped but your SD card. Factory reset. Format /system etc.
3. Flash your ROM and gapps if they are seperate.
You should not get any errors. If your recovery is current and your flashing a new rom onto a fully wiped system and you still get a error either you're screwing something up or you may have a hardware problem.
To rule out a hw problem flash the factory images with fastboot. If those flash normally and everything works it is almost certainly user error.
Click to expand...
Click to collapse
Alright, thanks Do you recommend that I root my Nexus S or should I wait for the Jelly Bean update? I've rooted before and I enjoyed it but now I don't see that many reasons to root, do you have any good reasons?
I have many. My reasons for root don't matter. If you don't have a reason for root then don't root. Its that simple really.
Make sure you're on a stock 4.0.4 rom. When the ota is out install it.
If you want just root on either os at any time just flash su.zip from custom recovery. Its that simple. Having root on a stock rom does not affect the ota process.
albundy2010 said:
I have many. My reasons for root don't matter. If you don't have a reason for root then don't root. Its that simple really.
Make sure you're on a stock 4.0.4 rom. When the ota is out install it.
If you want just root on either os at any time just flash su.zip from custom recovery. Its that simple. Having root on a stock rom does not affect the ota process.
Click to expand...
Click to collapse
What are your reasons for root? Please share?
Getting rid of stuff I don't want in a ROM.
Apps that do things that require root.Titanium backup/autoruns adaway ( ad blocker app alone could be its one point) etc
Changing kernel settings. Bid/bin clocks volts etc.
Being able to have a replacement launcher use the ICS style widget drawer.
Lastly , I simply just can't see having a computer that I don't have root/admin rights to. Its my damn device and I do what I want.
albundy2010 said:
Getting rid of stuff I don't want in a ROM.
Apps that do things that require root.Titanium backup/autoruns adaway ( ad blocker app alone could be its one point) etc
Changing kernel settings. Bid/bin clocks volts etc.
Being able to have a replacement launcher use the ICS style widget drawer.
Lastly , I simply just can't see having a computer that I don't have root/admin rights to. Its my damn device and I do what I want.
Click to expand...
Click to collapse
Oh cool. There is this project that some members from XDA are working on called Sense4All and they are porting Sense to many devices. Im probably going to wait until a fully functionable release is available for the Nexus S. I do like AOKP a lot, so that might be a reason for why I'll root.
You seem to be a little confused with some terms. Root is simply being able to grant superuser permission.
You don't need to root to flash a custom rom on a nexus. Just a unblocked bootloader. You could run aokp or any other rom without root if you wanted to.
albundy2010 said:
You seem to be a little confused with some terms. Root is simply being able to grant superuser permission.
You don't need to root to flash a custom rom on a nexus. Just a unblocked bootloader. You could run aokp or any other rom without root if you wanted to.
Click to expand...
Click to collapse
Oh, I never knew that, haha. Is it possible to flash a custom kernel with an unlocked bootloader or does that require root access?
m1l4droid said:
No you just need a custom recovery. But using that kernel's mods, like BLN, OC, UV, touchwake, etc, requires apps that need root, like NSTools, SetCPU, etc.
Click to expand...
Click to collapse
Oh alright. Now I really wanna root + install a custom rom. Do any of you have a full 100% fully working guide for rooting Nexus S and which rom should I flash first? I already know what kernel I want.
http://forums.acsyndicate.net/showthread.php?2024-ACS-Nexus-S-One-Click-Root-V4-0
leap_ahead said:
http://forums.acsyndicate.net/showthread.php?2024-ACS-Nexus-S-One-Click-Root-V4-0
Click to expand...
Click to collapse
Thank you so much! I rooted my phone with CWM recovery installed and Paranoid Android + gapps installed
Some months ago I followed guides here to SuperCID, s-off and install a custom ROM. The past few days my touch screen has become unresponsive, at first this was fixed by reflashing the ROM, but now, nothing will fix it, and the touch screen is completely unresponsive. So it seems I will have to return it to the shop to send off for repair. Of course I don't want them to have any reason to say it was the custom ROM that has caused it, warranty void blah blah so need to restore it to stock.
So far I have re-flashed with a stock ROM and changed the CID to what it was, and s-on. I can't remember whether I changed the MID, currently it is PG58*****, though I believe it should be PG5813001, and I'm not sure how to go about changing this (or if it needs changing, will they look into that?)
Another thing I'm unsure of, I downloaded the ROM from here: http://forum.xda-developers.com/showthread.php?t=1074559 I don't know if these ROMs are rooted or not? Is there any way to tell? Or is it a safe assumption they are not?
And finally, hboot, before flashing the stock ROM, this was 1.17, now it is 1.18. Is there anything in here that might suggest the phone has been tinkered with in ways they don't like? I just want to make sure I have covered everything so they don't immediately refuse to repair. If I have missed anything else please let me know.
Thanks.
Edit: I've also read about flashing stock recovery, though this may be included in the the stock ROM RUU I used, can someone confirm?
None of the 130 viewers have any advice on this one?
HB489 said:
Some months ago I followed guides here to SuperCID, s-off and install a custom ROM. The past few days my touch screen has become unresponsive, at first this was fixed by reflashing the ROM, but now, nothing will fix it, and the touch screen is completely unresponsive. So it seems I will have to return it to the shop to send off for repair. Of course I don't want them to have any reason to say it was the custom ROM that has caused it, warranty void blah blah so need to restore it to stock.
So far I have re-flashed with a stock ROM and changed the CID to what it was, and s-on. I can't remember whether I changed the MID, currently it is PG58*****, though I believe it should be PG5813001, and I'm not sure how to go about changing this (or if it needs changing, will they look into that?)
Another thing I'm unsure of, I downloaded the ROM from here: http://forum.xda-developers.com/showthread.php?t=1074559 I don't know if these ROMs are rooted or not? Is there any way to tell? Or is it a safe assumption they are not?
And finally, hboot, before flashing the stock ROM, this was 1.17, now it is 1.18. Is there anything in here that might suggest the phone has been tinkered with in ways they don't like? I just want to make sure I have covered everything so they don't immediately refuse to repair. If I have missed anything else please let me know.
Thanks.
Edit: I've also read about flashing stock recovery, though this may be included in the the stock ROM RUU I used, can someone confirm?
Click to expand...
Click to collapse
To Flash stock recovery read 2 in HERE I believe these ROMs are not rooted, to check just look for SuperSU or Superuser app, if it is not installed you are not rooted. Don't worry at all they'll never find out you rooted your phone, usually they never check. Read THIS guide it has the answer to all your questions regarding revert to stock
elvisypi said:
To Flash stock recovery read 2 in HERE I believe these ROMs are not rooted, to check just look for SuperSU or Superuser app, if it is not installed you are not rooted. Don't worry at all they'll never find out you rooted your phone, usually they never check. Read THIS guide it has the answer to all your questions regarding revert to stock
Click to expand...
Click to collapse
Thanks, though unfortunately I can't check what apps are installed due to the touch screen being unresponsive. But if that's not something they'll look into then fair enough.
The second thread doesn't quite answer everything (whether the ROMs are rooted for example), however, the first thread details extracting stock recovery from an RUU, so I guess that means I don't need to worry about that as it would have been flashed with the ROM.
One other thing - do they require the SD card to be sent also? Is there anything on there that should be removed? Any data relating to apps that use root privileges might raise an eyebrow; is it safe to do a reformat of the SD card? I'm not sure how much is on there that is vital the system.
Thanks for your answer.
HB489 said:
Thanks, though unfortunately I can't check what apps are installed due to the touch screen being unresponsive. But if that's not something they'll look into then fair enough.
The second thread doesn't quite answer everything (whether the ROMs are rooted for example), however, the first thread details extracting stock recovery from an RUU, so I guess that means I don't need to worry about that as it would have been flashed with the ROM.
One other thing - do they require the SD card to be sent also? Is there anything on there that should be removed? Any data relating to apps that use root privileges might raise an eyebrow; is it safe to do a reformat of the SD card? I'm not sure how much is on there that is vital the system.
Thanks for your answer.
Click to expand...
Click to collapse
No the ROMs in the second post are not rooted they are stock. The whole point of the post is to restore stock( read 3. RUU to restore stock). Stock recovery is smth else from stock ROM. You also need stock recovery to install OTA updates from google. Use Android Recovery Manager to download and install your stock recovery. Than in fastboot the stock recovery.img. I can't assure you that they won't notice you were rooted, but they usually don't. Keep in mind that when you unlocked your bootloader you accepted to void your warranty, and your serial number is in HTCs website. (theoretically) you can never be sure they won't discover you, but practically installing stock ROM, stock recovery, locking bootloader and getting back to s-on is enough to not get spotted
And you can format the SD Card if you want, you made a fresh install so there shouldn't be any files regarding it, just the files from the old system, but do a backup first just in case
elvisypi said:
No the ROMs in the second post are not rooted they are stock. The whole point of the post is to restore stock( read 3. RUU to restore stock). Stock recovery is smth else from stock ROM. You also need stock recovery to install OTA updates from google. Use Android Recovery Manager to download and install your stock recovery. Than in fastboot the stock recovery.img. I can't assure you that they won't notice you were rooted, but they usually don't. Keep in mind that when you unlocked your bootloader you accepted to void your warranty, and your serial number is in HTCs website. (theoretically) you can never be sure they won't discover you, but practically installing stock ROM, stock recovery, locking bootloader and getting back to s-on is enough to not get spotted
And you can format the SD Card if you want, you made a fresh install so there shouldn't be any files regarding it, just the files from the old system, but do a backup first just in case
Click to expand...
Click to collapse
Thanks again. If I recall correctly I used revolutionary, not HTC dev so I don't think they'll have my imei? Android recovery manager doesn't have the correct version for my phone, but further down the post it another method is extracting the recovery from the RUU, which is why I assumed stock recovery would have been installed when I flashed the RUU. I guess there is no harm in manually flashing the recovery to be sure though.
HB489 said:
Thanks again. If I recall correctly I used revolutionary, not HTC dev so I don't think they'll have my imei? Android recovery manager doesn't have the correct version for my phone, but further down the post it another method is extracting the recovery from the RUU, which is why I assumed stock recovery would have been installed when I flashed the RUU. I guess there is no harm in manually flashing the recovery to be sure though.
Click to expand...
Click to collapse
No HTCdev is not a recovery, it's the only way of unlocking your bootloader, which you have done for sure. But don't worry I assure you they don't go so deep. There's nothing wrong in flashing manually the recovery. Good luck
So I see ALOT OF CONFUSION regarding Safestrap on the Verizon Galaxy S5, I think its about time to explain it to stop this nonsense
THIS IS MEANT FOR 11 eMMC Users, 15 eMMC Users should unlock their bootloader and use TWRP instead
What is safestrap?
Why thank-you for asking, Safestrap is essentially a second recovery written by member @Hashcode to be used for systems with locked bootloader. Safe strap IS NOT A REPLACEMENT FOR YOUR STOCK RECOVERY OR A CUSTOM RECOVERY. Safestrap on a locked bootloader cannot flash locked bootloaders, cannot flash TWRP, and cannot flash custom kernels,(well it can but it is gonna brick) all this requires a custom bootloader, in which you could flash those things but at that point, you'd be better using SafeStrap, Flashfire or Odin to flash TWRP first.
So then what can safestrap do? Well safestrap is capable of flashing system partitions, data, cache and taking backups and even restoring them. It also has a built in file manager to give you access to system allowing the deleting, moving, and changing of files
You could run some stock based ROMs with this and in some cases pre-rooted ROMs. If you are on MM and running a pre-rooted rom, you must flash the stock kernel everytime you leave. YOU WILL NOT HAVE ROOT, but it will allow booting.
How do I access or use safestrap
Well I'll tell you this much, you DO NOT use your hard keys to do such. Don't try any button combos it just won't work. Safestrap doesn't exist on your recovery partition, but instead it exisst on the system partition, meaning you have to use the kernel to load safestrap, not hardware recovery.
On Lollipop its very simple, you need root first which can be obtained here http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370 @jrkruse
In this thread it also includes instructions for installing safestrap
Once safestrap is installed, continue by opening lollipop safestrap and selecting reboot to recovery. To exit, you can simply reboot to system
Now the hardest part comes down to Marshmallow. @jrkruse has a thread here about it http://forum.xda-developers.com/ver...ow-to-flash-custom-6-0-1-roms-locked-t3393943
Unlike Lollipop you DO NOT HAVE ROOT. Sorry, just won't happen. But you can still flash some stuff. The worst part is "how do I get into safe strap?"
In the magical folder you downloaded and probably deleted when you rooted your galaxy S5, there was a Kernel file. NI2 or NK2. Either works, what you do is open up Odin on your PC and put your phone into download mode, when it boots into download mode, just flash it and it will reboot. When your phone starts up it will say "safe system not installed" or something. Press recovery. If you wait too long it'll freeze and need a battery pull. Now your in safe strap. to exit just reboot to system(possibly need to flash stock kernel via Odin for MM as safe strap flashes stock LP kernel. Again if you followed the directions in @jrkruse thread then it will manage to boot without any hassle
So why bother?
That! Is an excellent question.
For lollipop users you can flash prerooted stock based ROMs and such. You can use debloat scripts, Knox removal scripts, even modify system files and build.prop and boot and shutdown animations, change boot sounds, install xposed, use rooted apps, go crazy!!! And you can take system backups and restores. Its just awesome!
However, those on Marshmallow have a more sinister fate. Verizon doesn't like us so you CANNOT ROOT. Which means NO YOU CANNOT USE FLASHFIRE TO BOOT INTO SAFESTRAP, NOR SAESTRAP REBOOT OR SUCH. They all require root. So what can you do? Your in luck, you can flash debloat scripts to debloat some ROMs, Knox removal, take backups and do restores, you can still modify build.prop(I don't recommend it, take a backup), and even use Safestrap built-in file manager to edit the system partition, just remember, don't do anything without a backup. Also YES you can DOWNGRADE back to Lollipop if you read @jrkruse thread. You can flash custom ish stock based ROMs but you still CANNOT GET ROOT. DO NOT TRY TO FLASH A ROOTED ROM WITHOUT FLASHING A STOCK KERNEL BEFORE REBOOT.
Thanks to changes made by google you no longer can root MM+ without a custom kernel and you cannot get custom kernels without custom recovery which needs unlocked bootloaders. So sorry to those who want it but nothing we can do right now
So that's the majority of how to safestrap. Any comments or questions leave them below and I probably will answer them maybe kinda probably not.
GeTex said:
So that's the majority of how to safestrap.
Click to expand...
Click to collapse
How to safestrap? Do you even safestrap?
Nandr0idC0nsumer said:
How to safestrap? Do you even safestrap?
Click to expand...
Click to collapse
Instructions unclear, ended up with unlocked bootloader and TWRP
GeTex said:
Instructions unclear, ended up with unlocked bootloader and TWRP
Click to expand...
Click to collapse
Instructions unclear, ended up with my eMMC chip reaching terminal velocity on its ride to space
GeTex said:
So I see ALOT OF CONFUSION regarding Safestrap on the Verizon Galaxy S5, I think its about time to explain it to stop this nonsense
What is safestrap?
Why thankyou for asking, Safestrap is essentially a second recovery written by member @Hashcode to be used for systems with locked bootloader. Safe strap IS NOT A REPLACEMENT FOR YOUR STOCK RECOVERY OR A CUSTOM RECOVERY. Safestrap cannot flash locked bootloaders, cannot flash TWRP, and cannot flash custom kernels, all this requires a custom bootloader.
So then what can safestrap do? Well safestrap is capable of flashing system partitions, data, cache and taking backups and even restoring them. It also has a built in file manager to give you access to system allowing the deleting, moving, and changing of files
You could run some stock based ROMs with this and in some cases pre-rooted ROMs. If you are on MM YOU CANNOT NOT USE SAFESTRAP WITH A PRE ROOTED ROM. YOU WILL BRICK!!!
How do I access or use safestrap
Well I'll tell you this much, you DO NOT use your hard keys to do such. Don't try any button combos it just won't work
On Lollipop its very simple, you need root first which can be obtained here http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370 @jrkruse
In this thread it also includes instructions for installing safestrap
Once safestrap is installed, continue by opening lollipop safestrap and selecting reboot to recovery. To exit, you can simply reboot to system
Now the hardest part comes down to Marshmallow. @jrkruse has a thread here about it http://forum.xda-developers.com/ver...ow-to-flash-custom-6-0-1-roms-locked-t3393943
Unlike Lollipop you DO NOT HAVE ROOT. Sorry, just won't happen. But you can still flash some stuff. The worst part is "how do I get into safe strap?"
In the magical folder you downloaded and probably deleted when you rooted your galaxy S5, there was a Kernel file. NI2 or NK2. Either works, what you do is open up Odin on your PC and put your phone into download mode, when it boots into download mode, just flash it and it will reboot. When your phone starts up it will say "safe system not installed" or something. Press recovery. If you wait too long it'll freeze and need a battery pull. Now your in safe strap. Again if you followed the directions in @jrkruse thread then it will manage to boot without any hassle
So why bother?
That! Is an excellent question.
For lollipop users you can flash prerooted stock based ROMs and such. You can use debloat scripts, Knox removal scripts, even modify system files and build.prop and boot and shutdown animations, change boot sounds, install xposed, use rooted apps, go crazy!!! And you can take system backups and restores. Its just awesome!
However, those on Marshmallow have a more sinister fate. Verizon doesn't like us so you CANNOT ROOT. Which means NO YOU CANNOT USE FLASHFIRE TO BOOT INTO SAFESTRAP, NOR SAESTRAP REBOOT OR SUCH. They all require root. So what can you do? Your in luck, you can flash debloat scripts to debloat some ROMs, Knox removal, take backups and do restores, you can still modify build.prop(I don't recommend it, take a backup), and even use Safestrap built-in file manager to edit the system partition, just remember, don't do anything without a backup. Also YES you can DOWNGRADE back to Lollipop if you read @jrkruse thread. You can flash custom ish stock based ROMs but you still CANNOT GET ROOT. DO NOT TRY TO FLASH A ROOTED ROM UNLESS YOU WANT A BOOTLOOP.
Thanks to changes made by google you no longer can root MM+ without a custom kernel and you cannot get custom kernels without custom recovery which needs unlocked bootloaders. So sorry to those who want it but nothing we can do right now
So that's the majority of how to safestrap. Any comments or questions leave them ebloe and I probably will answer them maybe kinda probably not.
NOTE mods may move this thread as seen fit
NOTE2 anyone may correct, suggest content, or give me pointers, I wrote this while sick laying here in the doctors office
NOTE3 Notes will be deleted after a few days
Click to expand...
Click to collapse
Safestrap cannot flash locked bootloaders, cannot flash TWRP, and cannot flash custom kernels, all this requires a custom bootloader. Safestrap can flash bootloader and custom kernels and TWRP This is why you should not try to do so it has safety feature built in where normal script will not flash them but it can be made to like I did with the Bootloader update and downgrade zips
DO NOT TRY TO FLASH A ROOTED ROM UNLESS YOU WANT A BOOTLOOP. As long as you flash the stock kernel back after you flash the rom systemless root will be broken and you will not bootloop. So you can flash MM roms that have systemless root just always make sure to flash stock kernel when finished if you dont you wont even have time to bootloop you will be taken to that unauthorize software is detected on your device screen
jrkruse said:
Safestrap cannot flash locked bootloaders, cannot flash TWRP, and cannot flash custom kernels, all this requires a custom bootloader. Safestrap can flash bootloader and custom kernels and TWRP This is why you should not try to do so it has safety feature built in where normal script will not flash them but it can be made to like I did with the Bootloader update and downgrade zips
DO NOT TRY TO FLASH A ROOTED ROM UNLESS YOU WANT A BOOTLOOP. As long as you flash the stock kernel back after you flash the rom systemless root will be broken and you will not bootloop. So you can flash MM roms that have systemless root just always make sure to flash stock kernel when finished if you dont you wont even have time to bootloop you will be taken to that unauthorize software is detected on your device screen
Click to expand...
Click to collapse
I meant to say it cannot flash those on locked bootloaders
Can you reword what I should replace those with and I'll update the OP
Do you think this thread is even helpful?
GeTex said:
I meant to say it cannot flash those on locked bootloaders
Can you reword what I should replace those with and I'll update the OP
Do you think this thread is even helpful?
Click to expand...
Click to collapse
Well it can flash those on locked bootloaders but you wont like the outcome!
I need you to write my stuff your so much better at explaing stuff than me. I just had a rant on your bootloader unlock page. Nothing meant towards you!
Haha alright, just trying to not mess things up in translation, gonna attempt to reboot your root page now that MM is here and I think we can overhaul it completely, along with a few minor changes to the batch files to streamline everything. Your Rant is justified, I honestly wanted to myself but I've been holding back
My experience
Okay! I ABSOLUTELY had to add to this thread because it was so helpful and confusing at the same time. I wanted to put in some points that seriously helped me. It took me about 8.5 hours total to get this done and I think this can help save people a lot of time.
Phone, I bought an unlocked verizon samsung galaxy s5 off the web (used). 5.0 lollipop with OK base from what I could tell. I was a ten year iphone user so this was all new to me. But I've run a web company for years so I'm very familiar getting around networks and software.
The first recommendation I would have is to read, then re-read, then re-read, then re-read the initial instruction page. The original writer didn't make it Step 1, Step 2, but put multiple steps inside a sentence so you have to sometimes figure out what he's trying to say.
The first problem I ran into was flashing the NK kernel. This is confusing because the Samsung logo will freeze and no where did it say how long to wait, just be patient. This cost me HOURS. There are two things happening, the root.bat file is giving you information and then the phone is responding. I would get all the ##### notifications and then a cursor sitting at the bottom with no response. Samsung logo would freeze. To get it to work I had to install the Factory Tar BPB1 Full Restore Image.
G900VVRU2BPB1_G900VVZW2BPB1_VZW.zip by unzipping and then using the Odin app to install. Once I did that the root.bat file would flash the kernel, I'd wait about 3-4 mins at the blinking cursor after the ### notices, then it said Root Installed and then I was off to the races. I would HIGHLY recommend doing this as from that point forward everything was soooo much smoother. I had about a dozen failures further down the process over about 4 hours because i never saw that Root Installed message at this stage. Once I did, everything was smooth.
I also did not opt out of buying Super Sume. I bought it and then removed kingroot with it and all the other steps were flawless.
For a new droid user one thing you may want to also need to know is that to move files over to the android download HandShaker, it's a much easier file transfer app to move those zip files in later stages over to the phone.
SO - If I am on Lollipop, I can load a custom ROM with Safestrap that is pre-rooted. Right? Would that allow me to load a ROM based on CM 14? What would or would not work. I have had a lot of prior experience with rooting and custom recovery, etc with my Razer M and an Xperia Play and the old LG Ally, but nothing with this S5 and no experience with Safestrap (that I can recall). Cut me a little slack - I'm 59 years old and a tech, but no experience with Samsung except ODIN a couple of times. Thanks.
netizenmt said:
SO - If I am on Lollipop, I can load a custom ROM with Safestrap that is pre-rooted. Right? Would that allow me to load a ROM based on CM 14? What would or would not work. I have had a lot of prior experience with rooting and custom recovery, etc with my Razer M and an Xperia Play and the old LG Ally, but nothing with this S5 and no experience with Safestrap (that I can recall). Cut me a little slack - I'm 59 years old and a tech, but no experience with Samsung except ODIN a couple of times. Thanks.
Click to expand...
Click to collapse
Only with an unlocked bootloader
Okay so I come from dos and Lynx area late 90s going to college and back then it was fun to sit down and code stuff and drink beer on the weekend can I just delete the hole OS out of my g900V cid 11 make my own somehow. It's been 23 yrs but sudo apt update still probably over rides a regular program saying no oh a and I barely got my first smartphone three or four months ago when I would consider smart I don't think the Samsung whatever it was was smart and just could text
averydiablo said:
Okay so I come from dos and Lynx area late 90s going to college and back then it was fun to sit down and code stuff and drink beer on the weekend can I just delete the hole OS out of my g900V cid 11 make my own somehow. It's been 23 yrs but sudo apt update still probably over rides a regular program saying no oh a and I barely got my first smartphone three or four months ago when I would consider smart I don't think the Samsung whatever it was was smart and just could text
Click to expand...
Click to collapse
No idea what you are trying to ask
CID 11 cannot run a custom OS.
Making your own OS is not anywhere near easy either
Inglis Second language is possible on rooted phone like LG spectrum 2 or g900v to get rid android just have kali or unbunt do you need bootloader unlock
averydiablo said:
Inglis Second language is possible on rooted phone like LG spectrum 2 or g900v to get rid android just have kali or unbunt do you need bootloader unlock
Click to expand...
Click to collapse
again, you cannot run anything but touchwiz based roms on a locked bootloader. you cannot use a custom kernel.
Thank you very much so now I went and traded for lg g2 and still have the vs93o old as dirt And the pixel 2 xl I don't want to mess with the other old ones I can root do they make os for lynux or Kali sorry I do understand I have hard time wording questions
GeTex said:
again, you cannot run anything but touchwiz based roms on a locked bootloader. you cannot use a custom kernel.
Click to expand...
Click to collapse
For now
ryanbg said:
For now
Click to expand...
Click to collapse
Indeed
Looking for a bit of help. I have a S5 with Emmc = 11. Know I cannot install TWRP. Have gone with all the steps from jrkruse here: http://https://forum.xda-developers.com/verizon-galaxy-s5/general/testers-required-easier-root-method-t3561529 I have no trouble getting into safestrap after rooting. The issue I have is once I flash a stock lollipop rom (either EMMC_11_PB1_LL_STOCK_SAFESTRAP_ONLY.zip or VZW_BPB1_ODEX_DEODEX_V9.zip), I can no longer access safestrap. I still have root (Super SU Pro) and busybox etc. However I can install, uninstall & re-install safestrap and when I click re-boot to recovery, it just reboots the system. I cannot figure out what the heck I am doing wrong. Is there a way to force a safestrap install that works? Or how am I destroying the SafeStrap that's part of the rom? Any suggestions would be greatly appreciated!
Thanks
John
Never mind. Installed LL_MM_SafeStrap.apk and that resolved the issue. Now have safestrap.
Thanks anyway!