Hi, maybe a noob question but, ever since I rooted my Moto X I cannot enter recovery mode. I believe that when the phone reboots on recovery mode it mounts /system as writable, but I wonder if there's a way to enter recovery mode at all after rooting. I have a locked bootloader on 4.2.2.
detesto said:
Hi, maybe a noob question but, ever since I rooted my Moto X I cannot enter recovery mode. I believe that when the phone reboots on recovery mode it mounts /system as writable, but I wonder if there's a way to enter recovery mode at all after rooting. I have a locked bootloader on 4.2.2.
Click to expand...
Click to collapse
yea you can still boot into stock recovery. just boot to the bootloader via volume down + power, then hit the volume down button only till you select recovery then hit volume up. and there is the stock recovery. enjoy.
You'd have to flash back to the stock recovery. However, I think you lose access to a writable system which leads to setting write protection off for good.
nhizzat said:
You'd have to flash back to the stock recovery. However, I think you lose access to a writable system which leads to setting write protection off for good.
Click to expand...
Click to collapse
i know for a fact you can enter the stock recovery after you root your device. i have done it many times before i flashed TWRP over my stock recovery
also when you root 4.4 you dont change the stock recovery so you should still be able to enter it.
That only applies if you have a Dev Edition or an unlocked bootloader.
nhizzat said:
That only applies if you have a Dev Edition or an unlocked bootloader.
Click to expand...
Click to collapse
well you learn something new every day.
did not know that having a unlocked bootloader would change if you could enter stock recovery after root or not.
thank you for the information.
guess i should of played around with the rooting and stuff before i unlocked my bootloader so i had some more knowledge on locked bootloader processes
nhizzat said:
You'd have to flash back to the stock recovery. However, I think you lose access to a writable system which leads to setting write protection off for good.
Click to expand...
Click to collapse
That's what I was thinking, when I enter to fastboot and select recovery, it just boots to system. I guess I should unlock the bootloader then, I feel a little paranoid not having recovery
detesto said:
That's what I was thinking, when I enter to fastboot and select recovery, it just boots to system. I guess I should unlock the bootloader then, I feel a little paranoid not having recovery
Click to expand...
Click to collapse
depending on what carrier your device is with depends on if you can unlock the bootloader or not.
if you cant unlock it then you can use safestrap here is the link
http://rootzwiki.com/topic/104161-recovery-locked-safestrap-recovery-v365-2013-11-13/
dray_jr said:
depending on what carrier your device is with depends on if you can unlock the bootloader or not.
if you cant unlock it then you can use safestrap here is the link
http://rootzwiki.com/topic/104161-recovery-locked-safestrap-recovery-v365-2013-11-13/
Click to expand...
Click to collapse
I can unlock, I'm on telcel (Mexico) and I already checked the motorola web site. It's just that reading motorola saying I will no longer have warranty is a little harsh and I tried postponing unlocking it as long as I could (or at least until there's a ROM that catches my eye).
I looked into safestrap but it seems not many ROMS support this yet, or am I in the wrong here?
detesto said:
I can unlock, I'm on telcel (Mexico) and I already checked the motorola web site. It's just that reading motorola saying I will no longer have warranty is a little harsh and I tried postponing unlocking it as long as I could (or at least until there's a ROM that catches my eye).
I looked into safestrap but it seems not many ROMS support this yet, or am I in the wrong here?
Click to expand...
Click to collapse
rooting your phone removes stock recovery. it actually hijacks the stock recovery. it is part of the exploit giving you root. SS has worked on many devices even tho it may not say that it is supported. hashcode might be able to change something in SS to make it more compatible for your device if it isn't already.
detesto said:
I can unlock, I'm on telcel (Mexico) and I already checked the motorola web site. It's just that reading motorola saying I will no longer have warranty is a little harsh and I tried postponing unlocking it as long as I could (or at least until there's a ROM that catches my eye).
I looked into safestrap but it seems not many ROMS support this yet, or am I in the wrong here?
Click to expand...
Click to collapse
Technically, you already lost your warranty by rooting the phone. If you can unlock your bootloader, do it. That alone will save your ass more than a custom recovery.
Related
Hi guys,
I am having trouble restarting stock c6616 into recover mode?
Read so many articles, watched several videos on YT, but i cannot get it working.
Most of instruction will say TurnOff phone, turno on, wait for led and keep pressing volume up, problem is LED is not lit at all on my phone.
I also tried to reboot to recover via ADB , phone will just restart.
Any ideas?
akyboy said:
Hi guys,
I am having trouble restarting stock c6616 into recover mode?
Read so many articles, watched several videos on YT, but i cannot get it working.
Most of instruction will say TurnOff phone, turno on, wait for led and keep pressing volume up, problem is LED is not lit at all on my phone.
I also tried to reboot to recover via ADB , phone will just restart.
Any ideas?
Click to expand...
Click to collapse
You need to have a custom recovery installed to access that feature.... Do you have one installed?
St.Jimmy90 said:
You need to have a custom recovery installed to access that feature.... Do you have one installed?
Click to expand...
Click to collapse
Thanks for answer Jimmy
Tried to install dual recover for locked bootloader too,.. same thing, flashed successfully (at least it was saying that) and cant do nothing.
This is my 5th Android phone, and it is biggest pain to unlock/root/flash so far.
akyboy said:
Thanks for answer Jimmy
Tried to install dual recover for locked bootloader too,.. same thing, flashed successfully (at least it was saying that) and cant do nothing.
This is my 5th Android phone, and it is biggest pain to unlock/root/flash so far.
Click to expand...
Click to collapse
Is your phone rooted?
St.Jimmy90 said:
Is your phone rooted?
Click to expand...
Click to collapse
Ok ok,.. looks like i got it working, i re-flashed that Dual Recovery and i was able to start TWRP now.
Another question if you dont mind, my bootloader is locked (as i know) can i still flash Custom roms?
akyboy said:
Ok ok,.. looks like i got it working, i re-flashed that Dual Recovery and i was able to start TWRP now.
Another question if you dont mind, my bootloader is locked (as i know) can i still flash Custom roms?
Click to expand...
Click to collapse
No you can't. Custom roms like PA, OMNI, Cyanogenmod need a custom kernel. It is not possible to flash a custom kernel on a locked bootloader. You can still flash stock based roms though. If you search in the development section you will find some. They are marked with "LB"
St.Jimmy90 said:
No you can't. Custom roms like PA, OMNI, Cyanogenmod need a custom kernel. It is not possible to flash a custom kernel on a locked bootloader. You can still flash stock based roms though. If you search in the development section you will find some. They are marked with "LB"
Click to expand...
Click to collapse
Thanks
LB, Locked boot-loader.
I also tried to unlock it, but im getting message that boot-loader cannot be officially unlocked. So i guess im out of luck unlocking it?
akyboy said:
Thanks
LB, Locked boot-loader.
I also tried to unlock it, but im getting message that boot-loader cannot be officially unlocked. So i guess im out of luck unlocking it?
Click to expand...
Click to collapse
Correct.
You can check it in service menu if you bootloader is unlockable. Open dialer and enter *#*#7378423#*#*
Go to service info > configuratoin. If it shows "bootloader unlock allowed: no" you won't be able to unlock it
Checked that! , out of luck for me :/
Ok, trying to figure out LB Rom installation instruction.
I will give a try http://forum.xda-developers.com/xperia-z/development/rom-existenz-v5-0-0-ultra-edition-10-4-t2349656
This one,.. i guess its most popular for xperia
akyboy said:
Thanks for answer Jimmy
Tried to install dual recover for locked bootloader too,.. same thing, flashed successfully (at least it was saying that) and cant do nothing.
This is my 5th Android phone, and it is biggest pain to unlock/root/flash so far.
Click to expand...
Click to collapse
Which locket dual recovery file did you use? I'm having a paint too trying to root my Xperi Z C6616 and have find little to no help. THanks in advance.
Hello,
I got my Moto X few days back from America, its Verizon model (I live in Europe)
its not developer edition and bootloader is locked
...and first issue i noticed is when i try to reset to factory with power UP + DOWN volume i couldnt get recovery.. when i go to recovery settings i see moto logo and then verizon picture.. there is no "dead android" and phone boots normaly.
...second thing there was android 4.4 on it and i got notifications to update it, so i was like why not, lets do it... and after i decided to update, phone keeps rebooting itself, and i dont know what to do it stays awake like 10-20sec and reboot again. Cant belive i bricked it that way!
Phone seems that its not rooted or anything, but idk maybe it was and then back to stock.. Is there any solution?
Thanks in advance to any1 who can help me slove the problem
Cheers
Resurrecting A Bricked Moto X
drvoje said:
Hello,
I got my Moto X few days back from America, its Verizon model (I live in Europe)
its not developer edition and bootloader is locked
...and first issue i noticed is when i try to reset to factory with power UP + DOWN volume i couldnt get recovery.. when i go to recovery settings i see moto logo and then verizon picture.. there is no "dead android" and phone boots normaly.
...second thing there was android 4.4 on it and i got notifications to update it, so i was like why not, lets do it... and after i decided to update, phone keeps rebooting itself, and i dont know what to do it stays awake like 10-20sec and reboot again. Cant belive i bricked it that way!
Phone seems that its not rooted or anything, but idk maybe it was and then back to stock.. Is there any solution?
Thanks in advance to any1 who can help me slove the problem
Cheers
Click to expand...
Click to collapse
Try this http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
Is there any way to try to delete chache or factory reset before flashing to stock rom
drvoje said:
Is there any way to try to delete chache or factory reset before flashing to custom rom
Click to expand...
Click to collapse
If its not the developer edition for Verizon, the bootloader is likely locked, so you can NOT flash custom roms (unless you, or a previous owner, got a bootloader unlock code from the China Middleman and used it)
Did you buy the phone used, or new? If used, then it is possible that it was rooted using RockMyMoto, SlapMyMoto or the like... and the boot loop while trying to install an update could be due to that. If so, erasing cache will stop the boot loop. This can be done from stock recovery, or when in Bootloader/FastbootAP mode.
How to Boot into recovery -> http://mark.cdmaforums.com/MotoX-EnterStockRecovery.htm
If that doesn't work, try bootloader/fastboot....
How to get a working AndroidSDK/PlatformTools/ADB/Mfastboot setup -> http://mark.cdmaforums.com/ADB.htm
How to boot the phone into fastboot mode -> http://mark.cdmaforums.com/MotoX-BootloaderMode.htm
from your PC, do a mfastboot erase cache
to reboot the phone, mfastboot reboot
Optionally, you could do a mfastboot erase userdata before rebooting, to remove all data, apps, etc.
If erasing cache fixes the boot loop, you might just want to try using RSDLite and reflashing the STOCK rom, recovery, etc. (Download the Verizon 4.4.4 SBF from -> http://sbf.droid-developers.org/phone.php?device=0 then follow -> http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515 ) It would undo anything that was done to root your device, and put you back to factory fresh. The only reason not to, would be if you care about rooting and disabling write protection..
With a locked bootloader, If your phone is still on 4.4 (aka 4.4.0), and still has that older bootloader and gpt.bin, you could use SlapMyMoto to root, and MotoWpNoMo to disable write protection. Just don't take any updates. You could cause a bootloop, but more importantly it will re-enable write protection with no way to disable it again (unless you can unlock the bootloader).
Once your phone is on 4.4.2 or above, you can't properly downgrade the ROM, bootloader and gpt.bin to use the exploits used by SlapMyMoto/MotoWpNoMo. There is a TowelPieRoot which is a temp root that works on 4.4.2. Temp root in the fact that it doesn't survive power off/on, so it needs to be redone each time. Also it doesn't disable write protection, so any changes made to /system or the like are also lost at power off/on (aka hard boot).
Once on 4.4.4, you can't properly downgrade the ROM, bootloader and gpt.bin, and there are no exploits to root, and no way to disable write protection.
If you can use the China Middleman thread to get a bootloader unlock code, then you don't need to worry about the exploits, and you can then root and disable write protection just as if you had a developer edition. Also JCASE may be updating their Sunshine tool to use the exploit found by Dan Rosenberg to unlock the bootloader on the Moto X, but there is no exact date yet of when it will be available (so far "next few weeks" has been said, but nothing more specific), and there is discussion around will it work for those who took the 4.4.4 update or not (no confirmation yet either way).
KidJoe;55503494
If that doesn't work said:
[*]How to get a working AndroidSDK/PlatformTools/ADB/Mfastboot setup ->
[*]How to boot the phone into fastboot mode ->
[*]from your PC, do a mfastboot erase cache
[*]to reboot the phone, mfastboot reboot
[/list]
Click to expand...
Click to collapse
did this with mfastboot image and worked like charm
bdw now i will need some time reading what is best to do with my unlockable bootloader verizon phone, if u have any sugestions please let me know.
and tnx for the help again mate
drvoje said:
bdw now i will need some time reading what is best to do with my unlockable bootloader verizon phone, if u have any sugestions please let me know.
Click to expand...
Click to collapse
You said its a verizon phone, but not the developer edition..
So at this point, the only way to unlock the bootloader is the China Middleman thread (in the general section). When JCASE updates Sunshine for the X (in the coming week or two), you can try that.
Otherwise, there isn't anything you can do.
and for stock android update? which one is the best for moto x? now it is 4.4.0
shall i rsd lite it to 4.4.2 or 4.4.4 or just stay current one?
bdw i need to rsd lite frimware anyway if i plan to use OTA update again perhaps when android L come? For now i just keep ignoring them
and yes its NOT developer edition phone
drvoje said:
and for stock android update? which one is the best for moto x? now it is 4.4.0
shall i rsd lite it to 4.4.2 or 4.4.4 or just stay current one?
bdw i need to rsd lite frimware anyway if i plan to use OTA update again perhaps when android L come? For now i just keep ignoring them
and yes its NOT developer edition phone
Click to expand...
Click to collapse
THe best depends on what you want to do.
Like I said before. IF you have 4.4 (aka 4.4.0) on the phone, and NEVER had anything newer on there (not 4.4.2 or 4.4.4), then stay there, look at SlapMyMoto and MotoWpNoMo to root and disable write protection.
Once you get 4.4.2 on there, you can root, but its temp root, and write protection can NOT be disabled.
4.4.4 you can't root.
Other than that, I can't say I really find too much difference. The camera is better in 4.4.4, but the battery isn't performing as well lately (could be a recent app update).
can i do this on my phone now - without fear of bricking it:
from my pc to run mfastboot again
then to clear chache
then to delete all user data
then to use rsd lite and flash Android 4.4
Blur_Version.140.45.5.ghost_verizon.Verizon.en.US even i alrdy have 4.4 now?
..because i dont know what is done to my phone before and i want to make sure its like "new" device
i know i can not downgrade, but can i flash same frimware? just to make sure thats all stock again
bdw Im stll unable to enter recovery after fastboot :/ is it that because of locked bootloeader? or because it was rooted with any method? i cant find superuser
and then to wait for solution to unlock bootleader?
Thanks in advance
You can always re-flash the same rom that is on your phone.
You just never want to down grade, or flash something older than what is on your phone.
As for not being able to enter Stock Recovery... early versions of the RockMyMoto and such did a trick which made it so that when you picked boot to recovery, it booted to regular system with write protection disabled. If that was used on your phone before you purchased it, that could be the issue. Using RSDLite and flashing back to 100% stock will undo that.
But You never answered if you got the phone new or used.
IF new, then you have some other issue (either you're not doing it right, or there is something wrong with the phone).
If used, you don't know what was done before you received it. Someone might have rooted, etc.. then just removed SuperSU to appear non-rooted when selling, rather than flashing back to stock.
thanks for the reply...
yes phone is used before but same like new... and what i found that phone was rooted by some method.. i made this screenshots, look in attachment..
bdw i dont see super su anywhere in apps? how to remove?
and i got everything rdy to flash it, i was just waiting you to conform if its doable...
and what did u mean by this:
"With a locked bootloader, If your phone is still on 4.4 (aka 4.4.0), and still has that older bootloader and gpt.bin, you could use SlapMyMoto to root, and MotoWpNoMo to disable write protection. Just don't take any updates. You could cause a bootloop, but more importantly it will re-enable write protection with no way to disable it again (unless you can unlock the bootloader)."
is that what happened to me?
and have question about one more thing
my country does not support lte and in my region 3g is bad... i have stable signal all the time but i would like to use edge only (GSM), can i do that using some widgets and if can which ones?
drvoje said:
thanks for the reply...
yes phone is used before but same like new... and what i found that phone was rooted by some method.. i found this screenshot in phone, look in attachment..
bdw i dont see super su anywhere in apps? how to remove?
and i got everything rdy to flash it, i was just waiting you to conform if its doable...
Click to expand...
Click to collapse
If you mean you don't see a SuperSU icon in the app drawer, then they probably un-installed SuperSU before selling it rather than completely unrooting. If you mean you have an icon in the app drawer, but don't see it to uninstall under Settings -> Apps.. I don't know why that would be.
drvoje said:
and what did u mean by this:
"With a locked bootloader, If your phone is still on 4.4 (aka 4.4.0), and still has that older bootloader and gpt.bin, you could use SlapMyMoto to root, and MotoWpNoMo to disable write protection. Just don't take any updates. You could cause a bootloop, but more importantly it will re-enable write protection with no way to disable it again (unless you can unlock the bootloader)."
is that what happened to me?
Click to expand...
Click to collapse
Yes, that could be what happened to you. There are many reports of locked bootloader users who used those older root processes who then upgraded using the OTA from 4.4 to 4.4.2 that encountered bootloops and other issues. It was often recomended to reflash to 100% stock.
And what I meant is that if you are on 4.4 (aka 4.4.0) with all its parts, it is vulnerable and the older exploits can still be used to root and disable write protection without unlocking your bootloader. Search for SlapMyMoto for more details. Some people tried to be cute and mix/match parts which caused issues. Mostly the issues around downgrading are caused by GPT.BIN and Motoboot.IMG parts, their versions, if they've been upgraded and no longer match the rest of the rom on the phone, etc. (and that is a LONG story...)
drvoje said:
and have question about one more thing
my country does not support lte and in my region 3g is bad... i have stable signal all the time but i would like to use edge only (GSM), can i do that using some widgets and if can which ones?
Click to expand...
Click to collapse
You can TRY using something like LTE On/Off to open the hidden menu and set for GSM Auto (PRL) or LTE GSM Auto(PRL). I'm not sure which would work best.
Oh, and as for unlocking the bootloader, I've mentioned the China Middleman and JCASE's Sunshine so there are the links to read up if you want to do it.
The China Middleman is just like if you got the code directly from Moto. I don't know what the Jcase tool is like yet.
thanks again!
so i dont see a SuperSU icon in the app drawer - uninstalled probably and that is why i can not enter stock recovery
I am still on android 4.4 didnt do anything yet...
what u recommend me to do? to rsd lite it to 4.4 again? right?
than i will root my device
and about bootloader, my device is 9.2013, so i will wait JCASE's Sunshine and support him
ps. wiget works gr8 :good:
Just want to write some words, i just took jcase tool which is very easy to setup (made for noobs like me) and i got bootloader UNLOCKED on my verizon NON developer edition phone
and now i RSD lite to 4.4 stock rom
would like to hear from KidJoe what is best to do with my moto x now thanks
Now you can update to 4.4.4,whichever methods you want, and still root it. Done. ?
drvoje said:
Just want to write some words, i just took jcase tool which is very easy to setup (made for noobs like me) and i got bootloader UNLOCKED on my verizon NON developer edition phone
and now i RSD lite to 4.4 stock rom
would like to hear from KidJoe what is best to do with my moto x now thanks
Click to expand...
Click to collapse
Follow [mention]@KJ[/mention] 's advice and update to 4.4.4, and follow the Dev Edition or Unlocked Bootloader guides to rooting (flash the latest TWRP and root.)
We have flashify/flashfire, so why can't we just flash using these?
The locked bootloader won't allow booting an unsigned kernel.
l33tlinuxh4x0r said:
The locked bootloader won't allow booting an unsigned kernel.
Click to expand...
Click to collapse
But we can install custom Roms?
cjc2040 said:
But we can install custom Roms?
Click to expand...
Click to collapse
If the rom is using the stock kernel there is no problem. That is why we don't have AOSP like CM 13 yet.
In theory you could flash a rom form another G4 but your radio probably won't work. I remember that with the G3 you could do this and then there was a fix for the radio to get it working but they also have an unlocked bootloader.
l33tlinuxh4x0r said:
If the rom is using the stock kernel there is no problem. That is why we don't have AOSP like CM 13 yet.
In theory you could flash a rom form another G4 but your radio probably won't work. I remember that with the G3 you could do this and then there was a fix for the radio to get it working but they also have an unlocked bootloader.
Click to expand...
Click to collapse
I see so then what is preventing us from unlocking the bootloader or even installing TWRP. I know TWRP usually requires unlocked bootloader but can't we set it to read AND write permissions?
cjc2040 said:
I see so then what is preventing us from unlocking the bootloader or even installing TWRP. I know TWRP usually requires unlocked bootloader but can't we set it to read AND write permissions?
Click to expand...
Click to collapse
TWRP has a custom kernel. It is pretty much a kernel image so you need an unlocked bootloader. As far as unlocking the bootloader, it has a encryption key. If we had that we would be good but we don't so we need to bypass it somehow.
I think that our best bet is to wait and see if the sprint g5 gets unlocked and try to use that. Other than that I remember with the droid razr maxx that I had they used a program called safestrap instead of TWRP. It essentially took the stock kernel and loaded whatever you told it to software wise. However it had a boot screen which took 5 seconds longer to boot. Kind of like dual booting on a PC with grub.
P.S. I'm looking to get a Sprint G4 and start development on it but they are still too expensive.
l33tlinuxh4x0r said:
TWRP has a custom kernel. It is pretty much a kernel image so you need an unlocked bootloader. As far as unlocking the bootloader, it has a encryption key. If we had that we would be good but we don't so we need to bypass it somehow.
I think that our best bet is to wait and see if the sprint g5 gets unlocked and try to use that. Other than that I remember with the droid razr maxx that I had they used a program called safestrap instead of TWRP. It essentially took the stock kernel and loaded whatever you told it to software wise. However it had a boot screen which took 5 seconds longer to boot. Kind of like dual booting on a PC with grub.
P.S. I'm looking to get a Sprint G4 and start development on it but they are still too expensive.
Click to expand...
Click to collapse
Development is dead on this device. We can make stock modified system images hardly call it a rom. Ure wasting ure time buying this. There will not be a bootloader unlock. Cant be hacked as of yet some of the worlds greatest android minds have tried may even still be. Fact is its prob not gonna happent any time soon. And the solution will either come from g5 or whatever they make after that. The bootloader partitions are to highly encrypted to hack. It does it really sucks but like i said lost cause
I know that there are a lot of the missing OEM Unlock posts, but this isn't about how to force it to appear.
What I would like to know is that if I want to stay on the stock ROM, but I don't have the OEM unlocked option, would I be able to factory reset to clear out encryption and then root with Magisk?
The guide says that I need to have OEM unlocked to be able to root, so I'm curious what would happen if I tried to root with the OEM still being locked? Would I soft brick it?
This is quite different from the other phones I've used and it's extremely frustrating that Samsung decided to pull this kind of bs on everyone and so far, there's no solution to it.
Thanks
If the OEM switch is not visible and switched on, then you cannot flash any non-official binaries, which means you can't flash TWRP or Magisk, which at this point means you can't get root. That's why everything boils down to the OEM switch being enabled. Please contact Samsung expressing your dissatisfaction about this OEM issue. All of us should, until they react to remedy this.
If we can get to fastboot, why can't we boot TWRP, install Supersu/magisk and dm-verity thus gaining root.
This wouldn't replace the stock recovery.
I believe this was how the Axon 7 was rooted prior to bootloader unlock being presented/found.
I do this on one of my phones (not Samsung) as I only want root access and still be able to get OTA updates.
Would booting TWRP instead of flashing it trip Knox and would root be gained or would you find the boot partition or other system files be altered and you get the error that seems to popping up on these devices?
Just throwing this out there as food for thought.
ultramag69 said:
If we can get to fastboot, why can't we boot TWRP, install Supersu/magisk and dm-verity thus gaining root.
This wouldn't replace the stock recovery.
I believe this was how the Axon 7 was rooted prior to bootloader unlock being presented/found.
I do this on one of my phones (not Samsung) as I only want root access and still be able to get OTA updates.
Would booting TWRP instead of flashing it trip Knox and would root be gained or would you find the boot partition or other system files be altered and you get the error that seems to popping up on these devices?
Just throwing this out there as food for thought.
Click to expand...
Click to collapse
Having an unlocked bootloader is what would allow us to use fastboot to boot or flash an image. Just because we can access fastboot, doesn't mean we can get it to write to partitions, even temporarily. I haven't messed with a Samsung phone for years, so I could be wrong. This has been my experience with google bootloader in general.
fragtion said:
If the OEM switch is not visible and switched on, then you cannot flash any non-official binaries, which means you can't flash TWRP or Magisk, which at this point means you can't get root. That's why everything boils down to the OEM switch being enabled. Please contact Samsung expressing your dissatisfaction about this OEM issue. All of us should, until they react to remedy this.
Click to expand...
Click to collapse
From what I did read from other threads, if you don't see the option in the Developer Option Settings, then you shouldn't need to enable it
77Eric77 said:
From what I did read from other threads, if you don't see the option in the Developer Option Settings, then you shouldn't need to enable it
Click to expand...
Click to collapse
I was reading about this as well and what I got from that was in regards to custom roms, the oem unlock option is default to unlock and hidden. but for the stock rom, it's locked by default unless visibly given the option. otherwise when you go into download mode, it'll show FRP Lock: On.
Sent from my SM-G930F using Tapatalk
di11igaf said:
Having an unlocked bootloader is what would allow us to use fastboot to boot or flash an image. Just because we can access fastboot, doesn't mean we can get it to write to partitions, even temporarily. I haven't messed with a Samsung phone for years, so I could be wrong. This has been my experience with google bootloader in general.
Click to expand...
Click to collapse
Ah, but if I want to just root and nothing else, would I still need to have the bootloader unlocked? I'm used to rooting stuff but the technicalities and mechanics of the process escapes mr.
my hope is to atleast root the stock rom and factory reset including wiping the internal sd to start fresh. but if I factory reset on a stock rom, the internal storage would still be encrypted right?
Sent from my SM-G930F using Tapatalk
mputtr said:
Ah, but if I want to just root and nothing else, would I still need to have the bootloader unlocked? I'm used to rooting stuff but the technicalities and mechanics of the process escapes mr.
my hope is to atleast root the stock rom and factory reset including wiping the internal sd to start fresh. but if I factory reset on a stock rom, the internal storage would still be encrypted right?
Sent from my SM-G930F using Tapatalk
Click to expand...
Click to collapse
This is why I want to know if we can boot TWRP. It boots TWRP but leaves the stock recovery.
However, I'm not sure if the boot image is altered when flashing root. I know Magisk seems to alter the boot image but not sure if SuperSU does.
Would this trigger KNOX?
If it does trip KNOX, it's not worth booting into TWRP, might as well just bite the bullet and install but only if bootloader is unlocked 1st... Too expensive to just brick it for an experiment...
ultramag69 said:
This is why I want to know if we can boot TWRP. It boots TWRP but leaves the stock recovery.
However, I'm not sure if the boot image is altered when flashing root. I know Magisk seems to alter the boot image but not sure if SuperSU does.
Would this trigger KNOX?
If it does trip KNOX, it's not worth booting into TWRP, might as well just bite the bullet and install but only if bootloader is unlocked 1st... Too expensive to just brick it for an experiment...
Click to expand...
Click to collapse
personally I don't care about knox. I just want to be able to root and restore my apps so I can transfer my stuff from my s7 to the note 8 and freeze all the bloatware like touchwiz and stuff.
from what I gleaned from reading the threads is magisk makes a copy of the boot image as a backup.
but again I just want root and I can wait for a longer term solution in how to fix this moronic 7 day jail bs.
but I think knox will get tripped the moment you root
Sent from my SM-G930F using Tapatalk
mputtr said:
I was reading about this as well and what I got from that was in regards to custom roms, the oem unlock option is default to unlock and hidden. but for the stock rom, it's locked by default unless visibly given the option. otherwise when you go into download mode, it'll show FRP Lock: On.
Sent from my SM-G930F using Tapatalk
Click to expand...
Click to collapse
I didn't have OEM option as well (FRP lock was ON), I just followed me2151 guide but I was getting the partition error, so in first part I also added BL and after that everything went smoothly.
KNOX wasn't tripped, it's rooted as of this moment and tomorrow I will be installing custom rom.
PS: And yes it was an experiment but I was willing to take the risk because after reading half a day about no OEM option in developer options everyone was saying if it's not there you don't need it, I wasn't 100% sure but I was 98% sure I'm not going to brick it. btw I'm using Telus N950W note8 (locked)
I think you might want to be careful on that. I'm not sure who "everyone" is but the others like Dr.Ketan did not even recommend rooting without unlocking the option first and it seems to me that the general gist of the other thread (the 150+ page thread) was that you need it explicitly unlocked.
The ones who talked about not seeing the option means you probably don't need it are talking about custom roms (like renovate) that purposefully hid the option since it's already defaulted to unlocked on that rom.
I haven't used any custom roms yet, but that seems to be what I'm reading.
77Eric77 said:
I didn't have OEM option as well (FRP lock was ON), I just followed me2151 guide but I was getting the partition error, so in first part I also added BL and after that everything went smoothly.
KNOX wasn't tripped, it's rooted as of this moment and tomorrow I will be installing custom rom.
PS: And yes it was an experiment but I was willing to take the risk because after reading half a day about no OEM option in developer options everyone was saying if it's not there you don't need it, I wasn't 100% sure but I was 98% sure I'm not going to brick it. btw I'm using Telus N950W note8 (locked)
Click to expand...
Click to collapse
just following up. Were you able to root and flash a custom rom with OEM Unlocked checked after all?
Sent from my SM-G930F using Tapatalk
mputtr said:
just following up. Were you able to root and flash a custom rom with OEM Unlocked checked after all?
Sent from my SM-G930F using Tapatalk
Click to expand...
Click to collapse
I was able to root it but the boot loader is still locked. It's faster without the bloatware and what not. KNOX is disabled. There is still no twrp and custom rom for Snapdragon to the best of my knowledge. It did change the model of the phone from N950W to N950U1.
finally got the OEM Unlock option and rooted + stock recovery... i had to restart my phone to bring my android ID back to the one I always used.. and got locked out...
so 7 more days for me. And all I wanted to do was to have Titanium backup up and running so i can transfer my phone over....
i am hating what samsung has done
Hello
Hoping somebody can help getting my phone up and running again.
I wanted to unroot my phone, because i was having issues with danish "MitId". And was a bit sloppy with it.
First i tried using SuperSU to remove root. Because i didnt feel like setting everything up again. Didnt work.
Then I locked the OEM Lock in developer settings. Not thinking this would be a fatal error.
Got home from work, and said to myself. Jusk lock the bootloader and the phone will reset itself.
But this is not the case, when you have been stupid enough to lock the OEM lock.
Now I am stuck on "No valid operating system could be found. The device will not boot"
I can get in to fastboot by pushning power+vol down. But cannot flash anything since the phone thinks the OEM Lock is locked on it.
Does anyone know of a solution for me. Or is it going to the shop tommorow and say that my phone is going this. And hope they will sort it for me?
Can't you fix stuff by using https://flash.android.com/ ?
No, unfortuantly not. It fails:
Device Unlock Disabled​For security reasons, you need to enable "OEM unlocking" in order to flash your device. See the device preparation instructions for more information.
Pearsondk said:
No, unfortuantly not. It fails:
Device Unlock Disabled​For security reasons, you need to enable "OEM unlocking" in order to flash your device. See the device preparation instructions for more information.
Click to expand...
Click to collapse
Try sideloading the full OTA. You don't need an unlocked bootloader for that.
Unfortuatly not, if I try to enter recovery mode. The phone just goes back to the screen saying "No valid operating system could be found. The device will not boot"
ADB is not available to me
If you can't sideload the OTA, I'm afraid there is not much else you can do with a locked bootloader except try to RMA it.
Can you get into recovery at all. Even if it's the stock you can attempt a sideload of the stock OTA.zip from Google. You may also try if your on boot slot A
fastboot --set-active=b
On b use
fastboot --set-active=a
Try to see if the other boot slot has an a bootable OS.
*****I apologize I just saw it's actually still locked****"
Contact U-break I-fix if I typed that correctly. The third party warranty repair center for Google's warranty. I believe they can attempt to switch the boot slot with a locked bootloader with the equipment they use to reflash these devices. If anything it's under warranty get the RMA and if the bootloader is locked on it trade someone or sell it and use it to make buying a new cheaper..
JovialQuestion said:
Can you get into recovery at all. Even if it's the stock you can attempt a sideload of the stock OTA.zip from Google. You may also try if your on boot slot A
fastboot --set-active=b
On b use
fastboot --set-active=a
Try to see if the other boot slot has an a bootable OS.
Click to expand...
Click to collapse
No, I can get into fastboot and that is it.
But everything I try in fastboot gets rejected, since it says the phone is locked.
Does the bootloader screen on the phone have the option to boot into Rescue. This has a ADB connection but I am not sure if adb sideload works
Really mad that Google intentionally locks phones this way, turning them into completely functional, but useless piece of junk. I guess that's late stage capitalism for you xD
JovialQuestion said:
Does the bootloader screen on the phone have the option to boot into Rescue. This has a ADB connection but I am not sure if adb sideload works. Use the volume keys and power button to select it
Click to expand...
Click to collapse
Kofa1 said:
Really mad that Google intentionally locks phones this way, turning them into completely functional, but useless piece of junk. I guess that's late stage capitalism for you xD
Click to expand...
Click to collapse
Google is not responsible for phone's with locked bootloaders. They make the device with the specifications the carrier that sells it stipulates. Google themselves allows the unlock.
Lughnasadh said:
If you can't sideload the OTA, I'm afraid there is not much else you can do with a locked bootloader except try to RMA it.
Click to expand...
Click to collapse
Iam guessing the same. Phone doesnt want to do anything.
And since i cant get into the phone to oem lock i am stuck. Live in Denmark, so by law I havnt voided the warrenty by rooting.
Pixel warranty is always valid even if you unlock and root. Google doesn't void the warranty. Go to Google pixel support page. Find warranty and act as if your submitting a RMA and it will tell you after you enter the device IMEI how long your warranty is valid for
Delete
If that were true. Android flash tool https://flash.android.com/welcome
Would work as it's the same process for the browser to flash the very same file. Motorola allowed signed factory img on locked. Google had never allowed that in fastboot as far as I am aware
DroidRommer said:
All you need to do is go here Factory pixel firmwares and scroll down to pixel 7 panther assuming you're not on the pro (cheetah)
-select the latest version for your model whether that's Verizon or whatever if you have the carrier unlocked one like myself just choose the Feb firmware that doesn't have a carrier name at the end of the firmware number (you should have your phone plugged into your PC and in fastboot mode) click flash and follow the steps. These are Googles factory images so it doesn't matter if your bootloader is unlocked or not as long as you choose the latest version and the correct version for your phone. Tbh you can't really brick the pixel 7 as long as you have a PC and are able to put the phone in fastboot mode (holding the volume down and power button while powering on)
-Anytime you run into some kind of bootloop issue or wanna get rid of root flashing the stock firmware from this website will factory reset and revert your phone to the way it was the very first time it was pulled out of the box and powered on. If you have already tried this and you know forsure you did everything correctly then I must admit I have never had this happen and I'm someone who flashes custom roms and goes back to stock to get the latest security update just to turn around and flash another custom rom right after lol. If you need any help or advice feel free to pm me whenever. I have been rooting phones for a long time and have to say that the Google pixel is by far the most user friendly phone I've ever owned when it comes to custom rooms, rooting etc. You can ALWAYS go back as long as you know what steps to take. Sorry for the rant especially if you already figured it out.
Happy Customizing!
DROIDROMMER
Click to expand...
Click to collapse
Their bootloader is locked. You cannot flash a factory image like that with a locked bootloader. They also turned off OEM Unlocking in the developer settings. If they had left this enabled they would be able to use Android Flash Tool as that tool will unlock your bootloader if OEM Unlocking is enabled.
Kofa1 said:
Really mad that Google intentionally locks phones this way, turning them into completely functional, but useless piece of junk. I guess that's late stage capitalism for you xD
Click to expand...
Click to collapse
This wouldn't be Google, they basically encourage you too unlock the bootloader and root if you want as they give you all the tools you need and factory firmware options to go back if you make a mistake. Tbh if you are able to unlock and root the phone to start then you can go back. Even with a locked bootloader you can always flash the latest factory image on googles dev website, you just can't downgrade firmware or install different carrier firmware without the unlocked bootloader. If we really wanna poke at some phone developers I vote Samsung as I have had multiple people ask me to root their phones and if it's a US snapdragon version it cannot be done its so frustrating lol thanks for letting me vent, have a great day if you have the the carrier unlocked dev edition of the pixel 7 and ever need any help feel free to pm me. I have been rooting and romming pixels for a long time
Edit: I was not aware you couldn't flash the stock firmare using googles dev page without oem unlock. I apologize for jumping to conclusions. I thought I had every possible bad scenario happen to me by now but apparently I learned something new today.
DroidRommer said:
This wouldn't be Google, they basically encourage you too unlock the bootloader and root if you want as they give you all the tools you need and factory firmware options to go back if you make a mistake. Tbh if you are able to unlock and root the phone to start then you can go back. Even with a locked bootloader you can always flash the latest factory image on googles dev website, you just can't downgrade firmware or install different carrier firmware without the unlocked bootloader. If we really wanna poke at some phone developers I vote Samsung as I have had multiple people ask me to root their phones and if it's a US snapdragon version it cannot be done its so frustrating lol thanks for letting me vent, have a great day if you have the the carrier unlocked dev edition of the pixel 7 and ever need any help feel free to pm me. I have been rooting and romming pixels for a long time
Click to expand...
Click to collapse
Dude. You cannot flash factory images of any kind on any Google phone with the bootloader in locked status. Please stop giving false information on here. If you want to talk up Samsung do it on a Samsung post. Let's not confuse everyone please
DroidRommer said:
Even with a locked bootloader you can always flash the latest factory image on googles dev website, you just can't downgrade firmware or install different carrier firmware without the unlocked bootloader.
Click to expand...
Click to collapse
To use Android Flash Tool, you have to have OEM Unlocking enabled in Developer Options for it to be able to unlock the bootloader.
To flash the factory image in fastboot you must have an unlocked bootloader.
Lughnasadh said:
Their bootloader is locked. You cannot flash a factory image like that with a locked bootloader. They also turned off OEM Unlocking in the developer settings. If they had left this enabled they would be able to use Android Flash Tool as that tool will unlock your bootloader if OEM Unlocking is enabled.
Click to expand...
Click to collapse
Okay my bad you are right fortunately I have never had this happen. And like someone else said if he can't get into recovery then he can't sideload a factory ota... sorry I'm at a loss on this one. Some custom roms use "fastboot update file.zip" would that do anything in this case or would that command not even work with a locked bootloader I'm assuming. I apologize for trying to act like a know it all I've just never heard of this happening