So I found out the hard way. All I wanted was root, with everything else staying as is. Not looking to install custom roms just yet. Should have been possible, as it has been on almost every other phone. Simply unlocking the bootloader should NOT require an automatic factory reset. Just seems like a big middle finger for someone looking to try.
God damn no guide or even the motorola unlocking page made it clear that you will erase everything on your phone. Thanks very ****ing much. Pretty pissed at this point.
edit: So there is one line about losing media. Missed that, but just assumed simply unlocking the bootloader didn't require factory reset. Goddamnit.
Ouch.
Rooting is a time sucking blackhole; no telling where it will take you especially on the first trip. One reason I choose to run stock... not that didn't take time to optimize
Always backup your critical data redundantly using at least 2 hdds that are physically and electronically isolated from each other and the PC. Androids rarely crash/burn or get infected but sooner or latter you will need that data.
Jgruar said:
So I found out the hard way. All I wanted was root, with everything else staying as is. Not looking to install custom roms just yet. Should have been possible, as it has been on almost every other phone. Simply unlocking the bootloader should NOT require an automatic factory reset. Just seems like a big middle finger for someone looking to try.
God damn no guide or even the motorola unlocking page made it clear that you will erase everything on your phone. Thanks very ****ing much. Pretty pissed at this point.
edit: So there is one line about losing media. Missed that, but just assumed simply unlocking the bootloader didn't require factory reset. Goddamnit.
Click to expand...
Click to collapse
It's in the big print
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yep, missed that line somehow. Have been used to unlocking procedures that don't factory reset.
Moto's playing hardball with it's consumers. I can't get my unlock code, they refuse to give it to me, in the US. There recently had a update to the august security patch. Applied it, and it turned off my developer options, and unlock button, they don't play nice for people that want to root.
reggjoo said:
Moto's playing hardball with it's consumers. I can't get my unlock code, they refuse to give it to me, in the US. There recently had a update to the august security patch. Applied it, and it turned off my developer options, and unlock button, they don't play nice for people that want to root.
Click to expand...
Click to collapse
Which CID and channel?
Code:
fastboot getvar cid
fastboot getvar ro.carrier
sd_shadow said:
Which CID and channel?
Code:
fastboot getvar cid
fastboot getvar ro.carrier
Click to expand...
Click to collapse
Hey, man - that's handy.
Related
Hi brothers i have a problem with my Nexus 6. Please help to resolve that rpoblem. Thanks for all to help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You've posted some pictures, but that isn't telling anyone anything. Care to describe your problem?
And also make the title a bit more meaningful...?
https://forum.xda-developers.com/announcement.php?f=3708
3. Post using a clear and descriptive subject and message.
You're most likely to receive a helpful answer to your question, if you use a short subject title that describes your problem and a message that explains in detail, what your problem is and what you've done to try solving it.
Strephon Alkhalikoi said:
You've posted some pictures, but that isn't telling anyone anything. Care to describe your problem?
Click to expand...
Click to collapse
have a problem with loading android. and i dont know what i do. i am not proffesional =)
Glen2017 said:
have a problem with loading android. and i dont know what i do. i am not proffesional =)
Click to expand...
Click to collapse
Don't need to be a professional, just give us more specific info like:
What are you trying to install?
What version of Android are you on?
What, exactly, are the steps you've used so far?
We need as much detail as you can give
garywojdan81 said:
Don't need to be a professional, just give us more specific info like:
What are you trying to install?
What version of Android are you on?
What, exactly, are the steps you've used so far?
We need as much detail as you can give
Click to expand...
Click to collapse
1. Android 7.0
2.Try to Nexus Root Toolkit for resolve problem unlock.
3. Try to install android 7.0 from NRT
4. But not working and phone stuck in google logo.
P.S. fastboot oem unlock not work
Glen2017 said:
1. Android 7.0
2.Try to Nexus Root Toolkit for resolve problem unlock.
3. Try to install android 7.0 from NRT
4. But not working and phone stuck in google logo.
P.S. fastboot oem unlock not work
Click to expand...
Click to collapse
Your first mistake was in trying to use the toolkit. If you've never used fastboot before, learn to use it before trying to use a toolkit. In order to unlock you need to be in Android, need to enable developer options in settings, enable OEM unlock in developer options, shut off the N6, and then enter bootloader mode. Only then will fastboot oem unlock work.
Since you're in a bootloop, your immediate tasks are to enter the recovery and perform a factory reset. If those fix the bootloop, then follow the guidance above. Otherwise you need to flash one of Google's OTA zips through the recovery, then factory reset, and then follow the guidance above.
There are help guides in the general section that you want to read and understand, before you accidentally turn your N6 into a paperweight.
Strephon Alkhalikoi said:
Your first mistake was in trying to use the toolkit. If you've never used fastboot before, learn to use it before trying to use a toolkit. In order to unlock you need to be in Android, need to enable developer options in settings, enable OEM unlock in developer options, shut off the N6, and then enter bootloader mode. Only then will fastboot oem unlock work.
Since you're in a bootloop, your immediate tasks are to enter the recovery and perform a factory reset. If those fix the bootloop, then follow the guidance above. Otherwise you need to flash one of Google's OTA zips through the recovery, then factory reset, and then follow the guidance above.
There are help guides in the general section that you want to read and understand, before you accidentally turn your N6 into a paperweight.
Click to expand...
Click to collapse
Thank you very much for help. Everything works perfectly. :good: I am very happy
Hi, i was powering on my device while charging, it had like 0 battery. When i powered it up, insted of turning it on it showed this message. In the bottom left corner it says suported API: 3. How can I fix it, help please.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
_08_ said:
Hi, i was powering on my device while charging, it had like 0 battery. When i powered it up, insted of turning it on it showed this message. In the bottom left corner it says suported API: 3. How can I fix it, help please.
Click to expand...
Click to collapse
Unlocked bootloader? If so, can you boot twrp?
Phil_Smith said:
Unlocked bootloader? If so, can you boot twrp?
Click to expand...
Click to collapse
Nah, I'm pretty sure it's locked, do you know any other way?
_08_ said:
Hi, i was powering on my device while charging, it had like 0 battery. When i powered it up, insted of turning it on it showed this message. In the bottom left corner it says suported API: 3. How can I fix it, help please.
Click to expand...
Click to collapse
I have a similar situation. Version 10.0.8.0.Save user data possible?
Gringolov said:
I have a similar situation. Version 10.0.8.0.Save user data possible?
Click to expand...
Click to collapse
Mine is V10.0.7.0 Do you have any idea on what to do?
_08_ said:
Mine is V10.0.7.0 Do you have any idea on what to do?
Click to expand...
Click to collapse
I asked a question on the forum 4pda.
Q: how to save user data?
A: Neither. The only way is twrp, but at the moment it does not support decoding Data on 9k, only on 8.1.0.
I believe that only factor resets possible.
I did a data reset. Recovered data from the cloud: contacts, messages, applications and their settings.
Gringolov said:
I asked a question on the forum 4pda.
Q: how to save user data?
A: Neither. The only way is twrp, but at the moment it does not support decoding Data on 9k, only on 8.1.0.
I believe that only factor resets possible.
I did a data reset. Recovered data from the cloud: contacts, messages, applications and their settings.
Click to expand...
Click to collapse
Ok thanks, i'll see what I else i can find.
_08_ said:
Nah, I'm pretty sure it's locked, do you know any other way?
Click to expand...
Click to collapse
edl mode only because its bl lock
kremlincrackers said:
edl mode only because its bl lock
Click to expand...
Click to collapse
what is edl mode and how can I use it? I think that if i unlock oem via fastboot I might be able to unlock the bootloader and install TWRP.
...i have today fixed one Corrupted screen A2. Was bl locked so was needed disassembly phone, short EDL pins with tweezer and then flash fastboot firmware with miflash.
I have used v10.0.17.0. After flashing phone starts with approx 3x rebooting and then with Failed to boot message... so i have selected retry...and done phone boots normally into system
Hey folks!
The phone fell a few times and now i'm getting a white screen that comes on every now and then with the message in red
“Kernel is not SEAndroid Enforcing” and “Custom binary blocked by FRP lock,”
I honestly have no idea on what to do.
Phone kind of important to me so I'm trying to preserve it,
Anyway I can get it going again without wiping everything on it ? Or is there anyway the data could be retrieved ?
Thank You!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This button was pressed to try and install idk maybe a custom recovery or a new rom, without having permission to do so, this is inherited from a google account being on the phone... either that or if you already were custom, this button was pressed to turn it off and now you get blocked from using custom code, unlock the bootloader and get rid of the frp lock and you are good, i will not help you with this procedure as it can be considered piracy and we dont do that here sorry for the wierd screenshot, it was a google result
efinityy said:
View attachment 5240391
This button was pressed to try and install idk maybe a custom recovery or a new rom, without having permission to do so, this is inherited from a google account being on the phone... either that or if you already were custom, this button was pressed to turn it off and now you get blocked from using custom code, unlock the bootloader and get rid of the frp lock and you are good, i will not help you with this procedure as it can be considered piracy and we dont do that here sorry for the wierd screenshot, it was a google result
Click to expand...
Click to collapse
I wish it where actually all that but the phone dropped to the ground. I got a screen replacement and when I tried to turn it on its been in this constant boot loop of that error message and nothing more.
I never tried to install any rom's. I'm not seeing how I would be able to out the boot loader if all it will do is constantly reset ?
Palms:09 said:
I wish it where actually all that but the phone dropped to the ground. I got a screen replacement and when I tried to turn it on its been in this constant boot loop of that error message and nothing more.
I never tried to install any rom's. I'm not seeing how I would be able to out the boot loader if all it will do is constantly reset ?
Click to expand...
Click to collapse
It's resetting because it's denying the signature on the binary of the installed firmware, that basically means a "read only" part of the phone, has been tampered with, and the "selinux not enforcing" part indicates this because many custom roms and kernels have an selinux non enforcing kernel.. and then on to frp lock, frp is Factory Reset Protection, which has been tripped, somehow, I can't say, but most oftenly this combination I've only seen on samsung's when you have unlocked the bootloader, this you need to do in order to tamper with these files, installed like rom/kernel/root, whatever the change might be, then somehow unticked the "allow OEM-Unlock" so the bootloader that is now unlocked is not allowed to be unlocked by the system itself, creating a break in the chain of trust between start and standby, and which makes you stuck in a wierd loop like this, if someone else replaced the screen for you I should really, really go talk to them. If you are the rightful owner of this phone and have no idea of anything about what I've talked about just now is and never did any of this before, someone did, and you should confront them. But I believe it's against the rules to assist with such things here and thus cannot help you any further in the matter
Hello, I was watching YT a few weeks ago and the phone (ASUS ROG Phone 2 tencent edition version 8/128) decided to reboot by itself. It done it before but this time it wouldn't get past the starting logo and restart again! It would keep looping until the battery ran empty... SO I booted in recovery mode, tried to factory reset and get E:Failed to save locale.
A friend has been trying to help me fix the phone and this was the result (screenshot). He can't figure it out.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've tried searching the forum with no luck. Anyone know if this problem is fixable and could guide us in the right direction?
did you backup your phone precautiously before
if you havent u lost all your important files
is your phone under warranty
Lavithiran -=-=-= said:
if you havent u lost all your important files
Click to expand...
Click to collapse
Hey, haven't backed up before at any point and don't have warrenty. Is there a way to get the phone working again?
Can't find old screenshot; if I remember correctly the first time I tried to factory reset after looping it said "driver E missing" something along that line. Up to that point never tried to change anything on the device by using a usb or PC.
mosa00 said:
Hello, I was watching YT a few weeks ago and the phone (ASUS ROG Phone 2 tencent edition version 8/128) decided to reboot by itself. It done it before but this time it wouldn't get past the starting logo and restart again! It would keep looping until the battery ran empty... SO I booted in recovery mode, tried to factory reset and get E:Failed to save locale.
A friend has been trying to help me fix the phone and this was the result (screenshot). He can't figure it out.
View attachment 5640881
I've tried searching the forum with no luck. Anyone know if this problem is fixable and could guide us in the right direction?
Click to expand...
Click to collapse
Do it this way:
1. Make a Wipe
2. Download this file https://androidfilehost.com/?fid=8889791610682901175
3. Run fastboot bootloader and connect to computer (side port)
4. Unpack and run "flashall_AFT.cmd" wait for the phone to reset and start up.
Should help.
mosa00 said:
Hey, haven't backed up before at any point and don't have warrenty. Is there a way to get the phone working again?
Can't find old screenshot; if I remember correctly the first time I tried to factory reset after looping it said "driver E missing" something along that line. Up to that point never tried to change anything on the device by using a usb or PC.
Click to expand...
Click to collapse
i dont think so you can retrive your old files
So im kinda stuck here. Found my old Honor 5C and thought i could try and root it and flash a new OS onto it. BUUUT it seems like i cant remember the phones password at all, which means i cant unlock it at all. I thought i could just boot into the recovery and factory reset it from there, but huaweis "eRecovery" doesnt allow me to reset anything, just "shutdown" or "update from internet" (which always fails). Then i thought i could just boot into fastboot and see if i could do something there, but no, every command i use results in a "Remote: command not allowed" (probably due to no USB-debugging authorization). So im not sure what else to try..
Cant access recovery reset, cant use fastboot because no usb-debug, cant turn on usb-debug since i dont know the password. ADB wont even recognize the phone in the recovery either, only in fastboot.
Hey there! Have you found a solution?
Maybe I can try to help you out in Unlocking your device
mvikrant97 said:
Maybe I can try to help you out in Unlocking your device
Click to expand...
Click to collapse
If you have any suggestions, they will be highly appreciated.
fylojaji said:
If you have any suggestions, they will be highly appreciated.
Click to expand...
Click to collapse
Please tell me the model number of your device.
Honor 5C, NMO-L31
fylojaji said:
Honor 5C, NMO-L31
Click to expand...
Click to collapse
You will need to disassemble your device and short test point and connect your phone using usb.
Install Huawie USB COM 1.0 Drivers, Radmin VPN and USB Redirector on your computer.
I will unlock it remotely using Radmin VPN and USB Redirector software.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wow .. Did not understand what needs to be done in the disassembled state of the device. What is USB redirector?
fylojaji said:
Wow .. Did not understand what needs to be done in the disassembled state of the device. What is USB redirector?
Click to expand...
Click to collapse
You have to short the test point as shown in the picture and I will unlock it remotely.
Maybe you could give me a hint and I will do it myself?
fylojaji said:
Maybe you could give me a hint and I will do it myself?
Click to expand...
Click to collapse
You don't have the software that would unlock your device.