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
Related
Hi all! I registerd now on forum but i'm an old noob reader of the forum. I
I bought Captivate(AT&T) on ebay and had Froyo 2.2 installed. I tryed to flash and root it to CYNOGENMOD with this GUIDE: wiki.cyanogenmod.com/wiki/Samsung_Captivate:_Full_Update_Guide
I did everything as written on thad guide but the phone continued to reboot and reboot and reboot. Now I don't even know what have I done but the phone starts with AT&T LOGO and than blocks with Samsung SGH i897 LOGO.
When i push volume buttons and start button it goes on CLOCKWORKMODRECOVERY.
Anyone can help me? I think i'm in big problem isn'it? PLEASE SOMEONE HELP!
(sorry for bad english)
alexmr89 said:
Hi all! I registerd now on forum but i'm an old noob reader of the forum. I
I bought Captivate(AT&T) on ebay and had Froyo 2.2 installed. I tryed to flash and root it to CYNOGENMOD with this GUIDE: wiki.cyanogenmod.com/wiki/Samsung_Captivate:_Full_Update_Guide
I did everything as written on thad guide but the phone continued to reboot and reboot and reboot. Now I don't even know what have I done but the phone starts with AT&T LOGO and than blocks with Samsung SGH i897 LOGO.
When i push volume buttons and start button it goes on CLOCKWORKMODRECOVERY.
Anyone can help me? I think i'm in big problem isn'it? PLEASE SOMEONE HELP!
(sorry for bad english)
Click to expand...
Click to collapse
Boot loop often happens and means you can't boot into the rom....it's called soft bricked. If you have recovery and download mode still active your safe.
1-Did you check you got the right files ?
2-Did you check the md5sum of the files (if available) to make sure your download is not corrupted.
3-Did you download and flash the proper cwm and/or kernel
4-You missed something in the process. (Recheck #[email protected])
silvertag said:
Boot loop often happens and means you can't boot into the rom....it's called soft bricked. If you have recovery and download mode still active your safe.
1-Did you check you got the right files ?
2-Did you check the md5sum of the files (if available) to make sure your download is not corrupted.
3-Did you download and flash the proper cwm and/or kernel
4-You missed something in the process. (Recheck #[email protected])
Click to expand...
Click to collapse
Hi thank you very much for answering. I managed to restart it by flashing a new rom downloaded online, a Froyo 2.2. As I am a little idiot if I write down infos about my firmware would you gently link me to a guide or tell me what should I do to upgrade in order do not do any mistake again? Anyway phone is from At&T but I'd like to unlock operator in order tu use my Italian sim.(before i screwed it up it was unlocked, as i bought it USED from ebay.)
Anyway these are the infos:
Firmware version 2.2
Baseband version I897UCJI6
Kernel version [email protected] #1
Build number:Froyo.UCJI6.
THANK YOU VERY MUCH. Hope to hear from you
PS: I used this to restore it I897UCJI6-OCD-REV02-Low-designgears.exe and ODIN, if this has any importance!
It should be posted in the OP or there should be a link to sufficient installation instructions in the OP of whatever Rom you would like to flash.
And no need to start a thread in the General and same exact thread in Q & A.
NO need to double post.
Help will be given even with one thread started.
Ok i won't crosspost, I did it because I really need help. Anyway my question.is: now that i have installed this 2.2froyo rom,as i don't know if phone is rooted or not CAN I install a superoneclick 2.3 gingerbread or should i do something first. Will this also remove sim operator lock? Please someone answer
Thanks everybody for help!
If u have root then u should have the "Superuser app"
{
"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"
}
or View attachment 854464, but Not this in ur app drawer. Or download a free app that requires root and test and see that way.
To go to a Gingerbread Rom from the Froyo 2.2 that u currently are running, u can use one of the One Clicks GB with Bootloaders in the Stickied One Click Thread in the Development Forum.
You have to have the GB Bootloaders in order to run a Gingerbread Rom, but once u have the Bootloaders there is not any need in flashing any bootloaders in the future, because the GB Bootloaders are backwards compatible.
There is risk in flashing bootloaders, so be sure u have a good micro usb to usb cable connection, preferably use a laptop so u don't loose power mid flash, remove all babies, animals, etc. from the room, so the cable does not get "accidentally" yanked during the flash.
Be sure u know what u r doing and then proceed.
So I decided just to see what my fastboot looked like - attached.
{
"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"
}
Is that normal for it to be unlocked? Everything I've heard says this is supposed to be super locked down.
mxgoldman said:
So I decided just to see what my fastboot looked like - attached.
Is that normal for it to be unlocked? Everything I've heard says this is supposed to be super locked down.
Click to expand...
Click to collapse
I think it says "bootloader LOCKED" in the fastboot screen. That means, you can ONLY flash motorola compiled operating systems (specifically kernels).;
If you want to try, run a fastboot unlock-bootloader command when running in fastboot. A locked bootloader will tell you something along the lines of "command not valid"
Do not flash anything on your phone. That looks to be a unlocked bootloader!
Sent from my DROID4 using Tapatalk 2
jsnweitzel said:
Do not flash anything on your phone. That looks to be a unlocked bootloader!
Click to expand...
Click to collapse
Wait, wouldn't that be a positive that would make flashing them easier?
I emailed someone who knows these things. He says its an engineering model. So it doesn't help the rest of us.
Sent from my DROID4 using Tapatalk 2
mxgoldman said:
Wait, wouldn't that be a positive that would make flashing them easier?
Click to expand...
Click to collapse
I think he meant "don't flash anything that might overwrite your unlocked bootloader" :laugh:
Anyway we could pull it or something? Probably not eh? OP, where did you get?!
podspi said:
I think he meant "don't flash anything that might overwrite your unlocked bootloader" :laugh:
Anyway we could pull it or something? Probably not eh? OP, where did you get?!
Click to expand...
Click to collapse
Makes more sense.
That's my little secret.
I could probably pull whatever from it, but I'd need some help for what you'd like pulled. Haven't rooted it or anything yet.
didnt this happen with a GSM RAZR before? dont get me wrong, i'd love to unlock my bootloader! someone bring this to their attention
FYI, on Milestone XT720, Motorola left a partially working fastboot--we can "fastboot boot boot.img" to boot self-built kernels and this bypasses the signature checks. But you have to boot via USB each time, if you use "fastboot flash boot.img" fastboot will write the kernel and reboot, but the signature check will fail after reboot.
http://forum.xda-developers.com/showthread.php?t=821210
Here's one way to muck with a kernel to change uname strings:
http://forum.xda-developers.com/showthread.php?p=11975260#post11975260
jsnweitzel said:
I emailed someone who knows these things. He says its an engineering model. So it doesn't help the rest of us.
Click to expand...
Click to collapse
FWIW, the "SE" is the giveaway. If it said "S", you would be in business.
Rzrbck, how so, if it could be retrieved from the phone? Maybe I'm not understanding, but if we had that bootloader is it not like the normal S model with full permissions to the phone?
what makes it an engineering model? are the physical components the same, or is it a software setting that if we changed could unlock the phone?
would it be possible via hardware to dump an SE bootloader, and flash it to a S devic? I would be willing to give this a go if its possible.
if we could get the bootloader images off that phone an unlock for the Droid 4 might be possible. Assuming, of course that both the S and the SE model use the same keys.
Tell me what I can do to help.
I wish I knew what to do, but in the mean time, here's some literature on how the lock works (it's for the milestone, but the d4 might use the same infrastructure).
The bootchain:
http://www.droid-developers.org/wiki/Booting_chain
The mbmloader: this loads the bootloader, if this is replaced with a version that doesn't check signatures, the bootloader can be permanently replaced:
http://www.droid-developers.org/wiki/Mbmloader
The mbm (bootloader) does it's own signature check of the kernel before booting it.
If either the key burned into the phone's fuse, or the key the mbmloader uses to check the mbm are the same on both devices, one or both of those partitions can be flashed with with the unlocked version. If they're both different, this is a dead end.
The only other option after this (aside from espionage)would be to crack the signature system directly by either creating an unlocked version of the bootloader and patching it in a way that it generates the same hash, or discover a new way to factorize large (2048 bit) numbers, and reverse engineer motorola's private signing key. (If you were to discover this factoring method, nearly every security company would have to retool.)
edit: careful updating your phone, an OTA can relock your phone. The more I read, it seems less likely that the bootloader is encrypted. Dumps should be made, but this is going to require someone with greater knowledge than I.
how would we go about doing this?
dewhashish said:
how would we go about doing this?
Click to expand...
Click to collapse
It seems like you load a special kernel module to unhide the bootloader partitions then simply use the dd command to make an image copy onto the sdcard.
iow, we need a dev.
well the only ones i know might be kholk, hashcode, and p3droid
This got quiet. No news on this yet?
I've tried several times (several different versions latest is the last version is 14.4.a.0.157) to remove the bootloader, I think its because I removed the bootloader earlier and than put it back (did that with the flashtool) on but the fastboot/phone still recognizes the earlier unlock because it hasn't been put back the correct way.
{
"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"
}
So I was wondering has anybody found a solution? because I can't find it? (also searched XDA ...)
Flamejim said:
I've tried several times (several different versions latest is the last version is 14.4.a.0.157) to remove the bootloader, I think its because I removed the bootloader earlier and than put it back (did that with the flashtool) on but the fastboot/phone still recognizes the earlier unlock because it hasn't been put back the correct way.
Click to expand...
Click to collapse
I think you dont know what you are actually doing.You are trying to unlock the bootloader.If you somehow really "remove" it, your device wont be able to boot.So I will assume you mean unlocking.
First, make sure your bootloader can be unlocked.Dial: *#*#7378423#*#*; then go to “Service info -> Configuration -> Rooting Status” and check if the “Bootloader unlock allowed” says yes. If the “no” answer will be displayed then you will not be able to unlock the bootloader of your device.
When you finish all the operations on the Sony site, you will receive an email with the unlock code.replace the word KEY with your code.
fastboot.exe -i 0x0fce oem unlock 0xKEY
From the screenshot I think you are not typing the correct key in there.
Note:You have to be sure that you have proper ADB connection with your device.Be sure you have enabled ADB debugging and have fastboot and adb drivers on your PC.
Here is a link with detailed explanation:
http://www.android.gs/unlock-bootloader-sony-xperia-devices-universal-tutorial/
Fixed
BlAckXpeRia said:
I think you dont know what you are actually doing.You are trying to unlock the bootloader.If you somehow really "remove" it, your device wont be able to boot.So I will assume you mean unlocking.
First, make sure your bootloader can be unlocked.Dial: *#*#7378423#*#*; then go to “Service info -> Configuration -> Rooting Status” and check if the “Bootloader unlock allowed” says yes. If the “no” answer will be displayed then you will not be able to unlock the bootloader of your device.
When you finish all the operations on the Sony site, you will receive an email with the unlock code.replace the word KEY with your code.
fastboot.exe -i 0x0fce oem unlock 0xKEY
From the screenshot I think you are not typing the correct key in there.
Note:You have to be sure that you have proper ADB connection with your device.Be sure you have enabled ADB debugging and have fastboot and adb drivers on your PC.
Click to expand...
Click to collapse
I already did it I had to make a folder(Flashtool\custom\mydevices\(device id)) and a text file in it (ulcode.txt) with just the code in it in flashtool and it worked, and I do now what I'm doing I just used the wrong word. You don't want to know how many times I already did the above.
I have the exact same issue, driving me nuts. haha I am now back on stock installed via pc companion but i have no working nfc and can not get into stock recovery. If I root the device dual recovery is still installed.
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.
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.