Related
Dear all,
I am new on Android, the Nexus 5 is my first android device. I freshly come from a 5 years old iPhone 3G.
2 Weeks ago I unlocked the bootloader of my device and rooted it following the tutorials provided by the XDA community without any problem.
Today, I saw that the OTA to upgrade from the Android version 4.4 to the version 4.4.2 was available directly from the device.
Since I did not want this update to be a problem with my rooted device, I downloaded the following apps: BootUnlocker for Nexus Devices and OTA RootKeeper (I do realize using RootKeeper was stupid since anyway the last update was released on July 25, 3 months before KitKat...). But anyway, this is what I did. I used those apps to Lock my Bootloader and unRoot my phone, thinking that this will reduce the chances of potential conflict with the OTA update.
Afterward, I downloaded and tried to instal the OTA directly from the Nexus 5. It ends up that I got stuck on the recovery menu. It was then impossible to get back on android and I did not know what to do.
This is where I did something totally crazy. Usually I spend time reading tutorials and finding information before doing anything that I do not fully understand. But at this stage I simply thought that the update could not properly instal due to the root. So I went on Advanced Wipe, I ticked all the options (data, system, Cash, Dalvik... all of them), and wiped the device.
As a result, my Nexus 5 has currently a Locked Bootloader and no OS installed. This means that I cannot activate the developer menu (no OS) to tick the option USB debugging. Thus, I cannot unlock my bootloader and in consequence I cannot instal the factory image and get back to stock.
Please, If you can give me some advice, explain me how can I unlock the bootloader in these conditions. Let me know... I really don't know what to do now.
PS: sorry my english is not perfect but I do hope you clearly understand my problem.
Yoyo-san said:
Dear all,
I am new on Android, the Nexus 5 is my first android device. I freshly come from a 5 years old iPhone 3G.
2 Weeks ago I unlocked the bootloader of my device and rooted it following the tutorials provided by the XDA community without any problem.
Today, I saw that the OTA to upgrade from the Android version 4.4 to the version 4.4.2 was available directly from the device.
Since I did not want this update to be a problem with my rooted device, I downloaded the following apps: BootUnlocker for Nexus Devices and OTA RootKeeper (I do realize using RootKeeper was stupid since anyway the last update was released on July 25, 3 months before KitKat...). But anyway, this is what I did. I used those apps to Lock my Bootloader and unRoot my phone, thinking that this will reduce the chances of potential conflict with the OTA update.
Afterward, I downloaded and tried to instal the OTA directly from the Nexus 5. It ends up that I got stuck on the recovery menu. It was then impossible to get back on android and I did not know what to do.
This is where I did something totally crazy. Usually I spend time reading tutorials and finding information before doing anything that I do not fully understand. But at this stage I simply thought that the update could not properly instal due to the root. So I went on Advanced Wipe, I ticked all the options (data, system, Cash, Dalvik... all of them), and wiped the device.
As a result, my Nexus 5 has currently a Locked Bootloader and no OS installed. This means that I cannot activate the developer menu (no OS) to tick the option USB debugging. Thus, I cannot unlock my bootloader and in consequence I cannot instal the factory image and get back to stock.
Please, If you can give me some advice, explain me how can I unlock the bootloader in these conditions. Let me know... I really don't know what to do now.
PS: sorry my english is not perfect but I do hope you clearly understand my problem.
Click to expand...
Click to collapse
You've got it all wrong. You do not need USB debugging to unlock bootloader. to unlock bootloader you must use FASTBOOT commands, which means you MUST be in the bootloader itself. USB debugging ONLY works in android.
rootSU said:
You've got it all wrong. You do not need USB debugging to unlock bootloader. to unlock bootloader you must use FASTBOOT commands, which means you MUST be in the bootloader itself. USB debugging ONLY works in android.
Click to expand...
Click to collapse
Dear RootSU,
So this means that I am not stuck at all and that I am simply limited by my current knowledge about android?
If this is the case, then "alleluia"! I will document myself to be able to fix this thing.
Yoyo-san said:
So this means that I am not stuck at all and that I am simply limited by my current knowledge about android?
Click to expand...
Click to collapse
Pretty much
You should be able to unlock the bootloader as you did before.
Boot phone to fastboot mode, download fastboot and adb kit to you computer... it can be found here on forums easy, and in comand line to unlock bootloader you need type "fastboot oem unlock".
More complete guide you can find here http://forum.xda-developers.com/showthread.php?t=2507905 =)
rootSU said:
Pretty much
You should be able to unlock the bootloader as you did before.
Click to expand...
Click to collapse
It's ok now!
As you said, I could unlock the Bootloader the same way I did before. Then I install the factory image 4.4.2, which I rooted directly.
Thanks a lot RootSu, you've shown me my mistakes and put me on the way to fix my problem.
Thanks also for your concern Biggreen. =)
Problem solved!
rootSU said:
You've got it all wrong. You do not need USB debugging to unlock bootloader. to unlock bootloader you must use FASTBOOT commands, which means you MUST be in the bootloader itself. USB debugging ONLY works in android.
Click to expand...
Click to collapse
Dear RootSU,
One more question, could you explain me why I got stuck into the recovery menu when I first tried to update via the OTA? Will I get the same kind of problem when I'll update with the v4.4.3 in the future?
Thanks
Yoyo-san said:
Dear RootSU,
One more question, could you explain me why I got stuck into the recovery menu when I first tried to update via the OTA? Will I get the same kind of problem when I'll update with the v4.4.3 in the future?
Thanks
Click to expand...
Click to collapse
I am not sure on the extact reason. OTA itself will not install with a custom recovery. You have to download the OTA and boot to recovery then manually flash.
There is a good "OTA Helpdesk" sticky thread in general you should read as theres lots of advice there
hi there...i've got the same problem... i wiped everythink and now i'm not able to switch on my phone....i just want to get out of this somehow...i'm very much new to this and i just want to get my stock android back that's it...somebody please help....
Do you see the battery icon when you connect the phone to a charger? Does the LED turn red when you connect the phone to a charger? Maybe leave the phone connected for a couple of hours and then try to power on?
Does android/S7 have anything equivalent to apples find my phone which effectively turns it into a brick when stolen? If so, how?
In the Google app settings there is a phone finding service you can activate, and some CSCs have "Find my mobile" which allows you to remote wipe / brick etc
but does this stop the device from being wiped if stolen and activating like apples activation lock does?
lofty5 said:
but does this stop the device from being wiped if stolen and activating like apples activation lock does?
Click to expand...
Click to collapse
Yes, provided you keep the bootloader locked.
EDIT: Technical term is FRP(Factory reset protection), and it's tied to the Google account used to set up the device
This is what i was thinking, that the boot loader has to be locked in order to do this. would keeping the phone rooted be an option or make it insecure?
Could i do this on a region that isn't my csc without bricking the phone? I'm pretty sure that as long as the source files are stock samsung any region should work. Can download mode be protected?
I'm currently backing up my device after which i am enabling all the security options and am going to try to hack into the phone to see if its worth doing or not. If it can be broken easily id rather keep it unprotected for convenience, but if i can protect the phone I'd rather do this as i lost my phone a couple of years ago and there was no protection on it at all nor on the sd card, which sucked.
bump
Root almost always requires a modified boot image which will immediately be blocked by a relocked bootloader. So root and FRP cannot coexist as they counteract each other. FRP itself is not CSC locked, only the remote control features. There are ways around it but they are mostly only present in older firmware, which is blocked by bootloader downgrade fuses. So yeah, pretty unbreakable if the device remains full Knox stock.
Hint: anything confidential should never be stored on the external card, or should be encrypted if it is (eg. Turn on encryption in titanium backup). Internal memory is always encrypted on stock firmware.
Edit: Download would work as usual. So basically what would happen is if a malicious firmware was flashed the bootloader will block it at boot and trip the Knox fuse, essentially burning all data on the device. If the crooks are smart they can still make use of the device, but most aren't so you should be safe
I'm using Cerberus, it can disable the shutdown/reboot menu on the lockscreen.
CurtisMJ said:
Root almost always requires a modified boot image which will immediately be blocked by a relocked bootloader. So root and FRP cannot coexist as they counteract each other. FRP itself is not CSC locked, only the remote control features. There are ways around it but they are mostly only present in older firmware, which is blocked by bootloader downgrade fuses. So yeah, pretty unbreakable if the device remains full Knox stock.
Hint: anything confidential should never be stored on the external card, or should be encrypted if it is (eg. Turn on encryption in titanium backup). Internal memory is always encrypted on stock firmware.
Edit: Download would work as usual. So basically what would happen is if a malicious firmware was flashed the bootloader will block it at boot and trip the Knox fuse, essentially burning all data on the device. If the crooks are smart they can still make use of the device, but most aren't so you should be safe
Click to expand...
Click to collapse
I had it rooted last night with magisk and boot loader locked, however it did refuse to boot due to modification and frp locked after a factory reset, but worked fine prior to this.
is it not worth doing if not fully knox stock?
I only really use root these days for titanium backup and perhaps ad blocking.
How difficult is it for a hacker to get back into the phone, I mean iPhones are practically impossible to get back into if on the latest firmware.
Blacky25 said:
I'm using Cerberus, it can disable the shutdown/reboot menu on the lockscreen.
Click to expand...
Click to collapse
is your boot loader locked and rooted?
lofty5 said:
is your boot loader locked and rooted?
Click to expand...
Click to collapse
Yes it is, I know it is also possible to delete everything but when I really loose my phone I will hope that people without the knowledge find my phone.
lofty5 said:
I had it rooted last night with magisk and boot loader locked, however it did refuse to boot due to modification and frp locked after a factory reset, but worked fine prior to this.
is it not worth doing if not fully knox stock?
I only really use root these days for titanium backup and perhaps ad blocking.
How difficult is it for a hacker to get back into the phone, I mean iPhones are practically impossible to get back into if on the latest firmware.
Click to expand...
Click to collapse
About as difficult as an iPhone to crack provided it's on latest firmware with a locked bootloader, even preventing reuse. FRP remains fully operational irregardless of Knox warranty status. It's possible to keep encryption while rooting (though this depends on strictly "close to stock" firmware, specifically by using a stock kernel binary. Ramdisk mods like Magisk or SuperSU are fine) to retain the data protection so thieves wont be able to deduce anything about you, but as long as the bootloader is unlocked a thief could always just wipe and reuse the device.
CurtisMJ said:
About as difficult as an iPhone to crack provided it's on latest firmware with a locked bootloader, even preventing reuse. FRP remains fully operational irregardless of Knox warranty status. It's possible to keep encryption while rooting (though this depends on strictly "close to stock" firmware, specifically by using a stock kernel binary. Ramdisk mods like Magisk or SuperSU are fine) to retain the data protection so thieves wont be able to deduce anything about you, but as long as the bootloader is unlocked a thief could always just wipe and reuse the device.
Click to expand...
Click to collapse
I am now back to full stock with no root. It’s not the same now as when i first started rooting back on the arc s, back then you could literally do nothing without it, things so basic such as a firewall. I only at this minute have one issue.
How in god’s name do you do a full backup of apps WITH data. I have helium but it refuses to backup most of them, it’s not a big deal now as i have re-setup the programs it wasn't compatible with. However, it would be handy to know for future reference, is there anything that can do a full backup with app data that doesn’t require root? If not, never mind I guess.
lofty5 said:
How in god’s name do you do a full backup of apps WITH data. I have helium but it refuses to backup most of them, it’s not a big deal now as i have re-setup the programs it wasn't compatible with. However, it would be handy to know for future reference, is there anything that can do a full backup with app data that doesn’t require root? If not, never mind I guess.
Click to expand...
Click to collapse
Not quite sure as I've always been rooted. Kies or Google Cloud Sync might be sufficient?
CurtisMJ said:
Not quite sure as I've always been rooted. Kies or Google Cloud Sync might be sufficient?
Click to expand...
Click to collapse
is the latest s7 fw protected against this attack?
https://forum.xda-developers.com/sa...galaxy-on5-metropcs-sm-g550t1-t3439557/page13
and root junkies hack?
lofty5 said:
is the latest s7 fw protected against this attack?
https://forum.xda-developers.com/sa...galaxy-on5-metropcs-sm-g550t1-t3439557/page13
and root junkies hack?
Click to expand...
Click to collapse
Only one way to find out An easy way to test would be to see if the phone responds to the USB command to dial the number, so no need to reset to check.
I just unlocked the bootloader to install twrp and maybe magisk i wanted to also try the Android P dev preview. but i know having a unlocked bootloader is a security risk also your get that warnign message at boot which makes booting up longer,is there a way to lock and unlock without losing data if im root.
Unlocking and locking wipes all data by design.
Telperion said:
Unlocking and locking wipes all data by design.
Click to expand...
Click to collapse
Is there a way to make the device secure with it having a unlocked bootloader?
With an unlocked bootloader, anyone can install a factory image, which wipes all your locks and your google account (and, therefore, defeats FRP), which is what makes it insecure. The only way to avoid that is to have a locked bootloader (and USB debugging off). (And I've seen reports here that unlocking the bootloader, installing TWRP and Magisk, then locking the bootloader, results in a hard brick (meaning buying another phone, because Google won't replace it)
Run with the unlocked booloader, don't ever leave the phone off your person and have "insurance" that replaces stolen (and possibly lost) phones.
Bought this phone off Craigslist-said it was bought from Google. Noticed OEM was greyed out and checked IMEI and shows-GOOGLE_VRZ_64G. Looks to be Verizon?
My concern is why lie and could this be rooted. Used ES File program said not rooted but powered off and hit checked reccover mode and does not have wipe cache partition and attaching FAST Loader information. Never Saw those highlightedin green saying Secure Boot yes & Device State-locked. Are all Verizons phones have that in green and is this rooted?
I just want to make sure it is safe to use?
Love the phone
Appreciated, thanks!
The device state being locked means the bootloader is locked. It is safe to use. If it is a Verizon issued device the bootloader cannot be unlocked and it cannot be rooted.
fury683 said:
The device state being locked means the bootloader is locked. It is safe to use. If it is a Verizon issued device the bootloader cannot be unlocked and it cannot be rooted.
Click to expand...
Click to collapse
Perfect-Thank you so much-Appreciate your reply-
123popeye123 said:
Bought this phone off Craigslist-said it was bought from Google. Noticed OEM was greyed out and checked IMEI and shows-GOOGLE_VRZ_64G. Looks to be Verizon?
My concern is why lie and could this be rooted. Used ES File program said not rooted but powered off and hit checked reccover mode and does not have wipe cache partition and attaching FAST Loader information. Never Saw those highlightedin green saying Secure Boot yes & Device State-locked. Are all Verizons phones have that in green and is this rooted?
I just want to make sure it is safe to use?
Love the phone
Appreciated, thanks!
Click to expand...
Click to collapse
You can buy a Verizon version phone from Google. So it didn't necessarily mean he was lying but perhaps deceptive if you were lead to believe you could root the device. Always ask for the first 2 numbers of the IMEI. If it's 35 it is usually Verizon branded. If it's 99 then Google version.
So you got the Edge S and want GApps? Basically you unlock your bootloader, root with Magisk, then install MagiskGApps.
DISCLAIMER: UNLOCKING YOUR BOOTLOADER MAY VOID YOUR WARRANTY, AND DOING ALL THESE THINGS IN THIS GUIDE MAY RESULT IN DAMAGE/BRICKING YOUR PHONE. I AM NOT RESPONSIBLE FOR ANYTHING YOU DO TO YOUR PHONE. PROCEED AT YOUR OWN RISK.
1. Unlock the bootloader: that should be doable with their global bootloader unlock website here.
2. Download Lenovo Motoroa Smart Assistant (Rescue and Smart Assistant), and follow its instructions to "rescue" your device. It will lead you to boot into bootloader mode and download the firmware. Find the firmware file via the LMSA's downloads (should have a "show folder" button). You'll need the boot.img file for Magisk.
3. Download Magisk, then follow its instructions. You'll have to copy the boot.img to your device, then use Magisk to patch the boot file, then copy the modified one to your PC.
4. You'll need fastboot. If you don't have it already, you can download the Android SDK platform tools here. Then go into the folder, Shift+Right Click the folder, then "Open Command Prompt" or "Open PowerShell," you should have something close to one of those two. Copy your Magisk modified .img file to that folder, then you'll want to input:
fastboot flash boot [modified .img file]
Once that completes, you should see in large text, "Start" on your phone next to the power button. Press the power button, and it should boot, and you should have root now.
5. Download MagiskGApps to your phone, open Magisk on your phone, click the button that looks like a puzzle piece at the bottom of the screen, "Modules." Click "Install from storage," locate the MagiskGApps file, and install it. After that it will ask you to restart your phone, do that, then you'll just have to be patient as it takes time once its restarted to load everything. You also may need to update some or all of the apps, then you should be able to use the notification to finish setting up the phone with Google Setup.
Thanks to Motorola for making it easy to unlock their bootloaders
Thanks to the whole Magisk team for making an easy, awesome root (and more!)
Thanks to Wacko1805 (and team?) for making MagiskGApps. This is really awesome.
unlock the BL and get root is will make some apps fingerprint and face ID fail?
kimker said:
unlock the BL and get root is will make some apps fingerprint and face ID fail?
Click to expand...
Click to collapse
Magisk has a "Magisk Hide" which will allow it to pass SafetyNet, and most things which check on device security will think the device is secure. But unlocking BL and rooting does make the device less secure, and therefore incurs its own risks apart from bricking or damaging the device.
HopelesRomantc91 said:
Magisk has a "Magisk Hide" which will allow it to pass SafetyNet, and most things which check on device security will think the device is secure. But unlocking BL and rooting does make the device less secure, and therefore incurs its own risks apart from bricking or damaging the device.
Click to expand...
Click to collapse
yes, i knew the unlock and root will take risk.. but not sure is Payment business apps using fingerprint will work normal.
kimker said:
yes, i knew the unlock and root will take risk.. but not sure is Payment business apps using fingerprint will work normal.
Click to expand...
Click to collapse
Google Pay works. But according to the Motorola website you should be able to relock the bootloader if yours doesn't work. But there's never any guarantee. If you need your device secure, recommend don't unlock bl or root, or wait to see if there's a root option without bootloader unlock that can be easily undone.
HopelesRomantc91 said:
Google Pay works. But according to the Motorola website you should be able to relock the bootloader if yours doesn't work. But there's never any guarantee. If you need your device secure, recommend don't unlock bl or root, or wait to see if there's a root option without bootloader unlock that can be easily undone.
Click to expand...
Click to collapse
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.
kimker said:
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.
Click to expand...
Click to collapse
That's not good. Hopefully they can restore it back somehow. With this guide to unlock and flash gapps why would you need to flash G100 though? This seems to be itright now without one of rom developer's releases to get root & apps. For me this is all i would look for. Titanium backup on it and restore.. done until PE rom comes out.
kimker said:
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.
Click to expand...
Click to collapse
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
thank you. They did not ask for help. It seems that the lock BL is a self-verification switch, and then performs a verification system integrity.
HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
I'm curious,If you unlock and flash other firmware and then flash back to the original firmware, can it be locked again?
Mine doesn't let me unlock its BL. I've got unlock code from moto and did a factory reset with SIM card in slot 1. After enabling developer mode and debugging the switch still is greyed out. So no chance to unlock it.
Has anyone got an idea what to try now?
Moto support answered yesterday to my request but also no solution since I told them that it doesn't work
Device is not branded. I got it from Amazon so no provider branding.
If this won't be able to be unlocked and rooted I'll have to return it and switch to a Google Pixel.
kischde said:
Mine doesn't let me unlock its BL. I've got unlock code from moto and did a factory reset with SIM card in slot 1. After enabling developer mode and debugging the switch still is greyed out. So no chance to unlock it.
Has anyone got an idea what to try now?
Moto support answered yesterday to my request but also no solution since I told them that it doesn't work
Device is not branded. I got it from Amazon so no provider branding.
If this won't be able to be unlocked and rooted I'll have to return it and switch to a Google Pixel.
Click to expand...
Click to collapse
I had the same issue, you need to factory reset WITH your sim card in the phone, this will let you open the OEM unlock slide thing in the dev mode.
Then once its done you can fastboot and unlock the bootloader.
I did so, maybe I explained not so well. SIM was inserted and then I did factory reset by starting it from settings. After restart it's still the same - switch / unlock slider greyed out.
kischde said:
I did so, maybe I explained not so well. SIM was inserted and then I did factory reset by starting it from settings. After restart it's still the same - switch / unlock slider greyed out.
Click to expand...
Click to collapse
On my OG Pixel XL, I had to wait 7 days for the slider to become normal. By the time I got around to do it on the Edge S it was about the same time.... could be related
Now as you said that I remember that thingy with another device. Maybe a Xiaomi I think... With that I had to wait several days until the unlock code was delivered.
But there was a message, too, when trying to get it sooner, which said you needed to wait some more time.
Not sure if it's the the same for Moto devices? Then again, when thinking that you experienced the same with a Pixel, too...
Did anyone else make such an experience with his/her g100?
kischde said:
Now as you said that I remember that thingy with another device. Maybe a Xiaomi I think... With that I had to wait several days until the unlock code was delivered.
But there was a message, too, when trying to get it sooner, which said you needed to wait some more time.
Not sure if it's the the same for Moto devices? Then again, when thinking that you experienced the same with a Pixel, too...
Did anyone else make such an experience with his/her g100?
Click to expand...
Click to collapse
Make sure your on the latest OTA, Lenovo made a mistake on previous versions with the OEM Unlocking function not being enabled. They fixed it in latest ota.
RSA tool said the file I uploaded yesterday is the latest one available (and it's exactly the same as the installed version).
The device was released just a few days ago in Europe. Perhaps they fixed the unlock switch in other regions and still need to fix it in Europe..
Will wait until weekend if they come up with a solution. If not I'm afraid I have to return the device as I need it personally AND professionally, too - I'm field agent, so.... :/
HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
The poor guy whose phone turned bricks went to the after-sales department of moto, and the answer was that he needed to replace the phone motherboard. .
kimker said:
The poor guy whose phone turned bricks went to the after-sales department of moto, and the answer was that he needed to replace the phone motherboard. .
Click to expand...
Click to collapse
Ouch...
kimker said:
I'm curious,If you unlock and flash other firmware and then flash back to the original firmware, can it be locked again?
Click to expand...
Click to collapse
I would assume so, but I don't really know why anyone would want to relock.