Related
Hi! I am unlocked my nexus one and now tried to root it.
I tried with Win XP and Win 7 with the same result.
I can see the device. If i go to the command promt and enter
"adb devices" it shows me the serial - So, usb is not the problem.
I also successfully unlocked it the same way.
Dev. Mode USB is also activated.
As soon I try to root it i.e. with superboot, Android SDK etc. I get the message
"waiting for device" (stays there for ever)
also when I want to lock the device again - same result.
Something must have happened preventing me to access the phone.
Also did a hard reset - without success.
Bottemline I am STUCK. The phone works, but no root .
Versions: ERE27 with 2.1update1
Someone an idea?
Thanks
Try a different USB Port. You can't relock the device.
MatMew said:
Try a different USB Port. You can't relock the device.
Click to expand...
Click to collapse
Well I tried already on different PC's.
FYI - It's not majorly important here, but yes you can re-lock it - The same way you unlocked it.
helipilotx said:
Well I tried already on different PC's.
FYI - It's not majorly important here, but yes you can re-lock it - The same way you unlocked it.
Click to expand...
Click to collapse
Oh really?
Can you provide link proof on how to re-lock the bootloader?
Lol - he thinks you can "re-lock" it.. hahaha..
did u debug ur usb....?
helipilotx said:
Well I tried already on different PC's.
FYI - It's not majorly important here, but yes you can re-lock it - The same way you unlocked it.
Click to expand...
Click to collapse
I think this may qualify for post of the year!
Anyways, why are you even trying to root the stock ROM? Flash a custom ROM, already rooted, with the high memory kernel. As great as the stock ROM is, rooting really doesn't do anything unless you want to mess with the stock ROM... but that is like buying a V8 conversion for a Fiat, then only running 4 of the 8 cylinders.
pjcforpres said:
I think this may qualify for post of the year!
Anyways, why are you even trying to root the stock ROM? Flash a custom ROM, already rooted, with the high memory kernel. As great as the stock ROM is, rooting really doesn't do anything unless you want to mess with the stock ROM... but that is like buying a V8 conversion for a Fiat, then only running 4 of the 8 cylinders.
Click to expand...
Click to collapse
Well, how ever - I'll might be wrong, just saw someone do it on you tube (might was fake)
Anyway, well it does not matter whether I want to root the stock rom or flash a custom rom - my point is it always shows me
"waiting for device"
helipilotx said:
Well, how ever - I'll might be wrong, just saw someone do it on you tube (might was fake)
Anyway, well it does not matter whether I want to root the stock rom or flash a custom rom - my point is it always shows me
"waiting for device"
Click to expand...
Click to collapse
You have to install the correct adb drivers
http://forum.xda-developers.com/showthread.php?t=613217
Eclair~ said:
Lol - he thinks you can "re-lock" it.. hahaha..
Click to expand...
Click to collapse
glad ur soooooooo much smarter
congrats ! A+
helipilotx said:
Well, how ever - I'll might be wrong, just saw someone do it on you tube (might was fake)
Anyway, well it does not matter whether I want to root the stock rom or flash a custom rom - my point is it always shows me
"waiting for device"
Click to expand...
Click to collapse
can you post the video link
helipilotx said:
glad ur soooooooo much smarter
congrats ! A+
Click to expand...
Click to collapse
Out of all the people that basically implied, or thought, what I said you - had to have a 'comeback' to me.. guess its because I said "hahaha," and "lol". If we really could re-lock the bootloader though... i'd be all over that..
TFJ4 said:
You have to install the correct adb drivers
Sorry, this is not the problem. These drivers I downloaded and installed already
As I said I can see the device and was able to unlock it.
- Any other ideas?
Thanks.
Click to expand...
Click to collapse
chronzz said:
can you post the video link
Click to expand...
Click to collapse
Have to look for it again. I saw it on my research to solve this problem I am having. When I find it again i will let you know for sure.
Anymore ideas anyone?
Thanks!
I had this problem yesterday (my first ever ROM flash!). I'm sure you didn't make this mistake, but my phone had to be on the boot (white) screen before it was recognized. When the phone was turned on normally, or off normally, I got the "Waiting for device" message.
FYI: I'm using Linux Fedora Core 12 on my PC.
Just had this problem. Jade this stupid mistake of not doing it while on the bootloader screen.
helipilotx said:
but yes you can re-lock it - The same way you unlocked it.
Click to expand...
Click to collapse
That is THE best post i've ever read... just see the confidence
Perhaps the video he saw was of a holiday phone, in which case
Code:
fastboot oem lock
does work.
No good on our retail ones (yet) though.
helipilotx said:
FYI - It's not majorly important here, but yes you can re-lock it - The same way you unlocked it.
Click to expand...
Click to collapse
Love this post!!! +1 for post of the year!!!!
Hello guys
I have been trying for days to unlock HTC Desire C for free but have no luck
I bought this Mobile from UK and its Network Locked, Dont know which carrier
Can anybody please HELP me or give me the unlock Code
Will be Thankful to him/her
Here is my IMEI code: 352277050400538
Thanks
You dont have to pay anything to anybody to unlock your phone. You have to first unlock our bootloader. Go here
Follow the steps correctly and make sure you have the necessary software in your computer. After that follow this guide
@OP, +1 to aashay960, you do that and you could achieve a network unlocked Desire C.
aashay960 said:
You dont have to pay anything to anybody to unlock your phone. You have to first unlock our bootloader. Go here
Follow the steps correctly and make sure you have the necessary software in your computer. After that follow this guide
Click to expand...
Click to collapse
In the Last step It Says
"On your phone you will now see the disclaimer. Please read this carefully as this action may void your warranty. Use the Volume buttons to highlight your choice, and the Power button to make your selection. If you select Yes, your phone will be reset to its’ factory default settings, and your bootloader will be unlocked. If you select No, your phone will reboot and no modifications will have been made."
But nothing came on the phone, what to do ? my phone is connected with pc
burhanuddin said:
There isnt HTC Desire C in the Bootloader
Click to expand...
Click to collapse
Read this thread. Step 1
aashay960 said:
Read this thread. Step 1
Click to expand...
Click to collapse
Hello, I just went to Boot on my HTC Desire C and i saw bootloader is Unlocked but still i cant use any other sim, What to do ?
you've just unlocked the bootloader, follow the second guide
bogdy5 said:
you've just unlocked the bootloader, follow the second guide
Click to expand...
Click to collapse
In the second Guide, Its written i should have busybox install on my mobile, But when i go to play store there are many Busybox, which one should i download? and also software needs to be rooted and my mobile isnt rooted
I think that u can download any..
Sent from my HTC Desire C using xda app-developers app
Guys Thanks very much for your Help
I have unlocked my HTC Desire C with your help
All credits goes to u all and XDA
Steps:
1) Unlocked Bootloader
2) My Mobile wasnt Rooted so i rooted by this video (Video)
3) Then Unlocked Sim Guide helped me via this Link
Thanks
Congratulations buddy.. So now that you have rooted and unlocked your phone, do you plan to install a custom rom?
aashay960 said:
Congratulations buddy.. So now that you have rooted and unlocked your phone, do you plan to install a custom rom?
Click to expand...
Click to collapse
Nah, Dont have any plans yet, is it good to install custom roms? what are the benefits?
burhanuddin said:
Nah, Dont have any plans yet, is it good to install custom roms? what are the benefits?
Click to expand...
Click to collapse
Benifits are increasing the productivity and potential. New interface, features etc.
Higher android version. Desire C wont get an update to 4.0.4 or sense 4.1 So installing CM10 for example brings all the new features of Jellybean to your device.
Personally i hated Sense UI and was impatiently waiting for a rom that used something else. Even before i would swap it for other launchers.
By far i am most satisfied with CM10, but my ultimate goal is a fully functional CM10.1
Penguin449s roms are great, so is Darkbreed. I advise you to stay away from WIP roms like CM9 and CM10.1 untill you build up the knowlage.
*self promo* Try the kernels, i heard NOPE is good ;3
Anyways if you have any questions feel free to ask.
me4488 said:
Benifits are increasing the productivity and potential. New interface, features etc.
Higher android version. Desire C wont get an update to 4.0.4 or sense 4.1 So installing CM10 for example brings all the new features of Jellybean to your device.
Personally i hated Sense UI and was impatiently waiting for a rom that used something else. Even before i would swap it for other launchers.
By far i am most satisfied with CM10, but my ultimate goal is a fully functional CM10.1
Penguin449s roms are great, so is Darkbreed. I advise you to stay away from WIP roms like CM9 and CM10.1 untill you build up the knowlage.
*self promo* Try the kernels, i heard NOPE is good ;3
Anyways if you have any questions feel free to ask.
Click to expand...
Click to collapse
"I heard NOPE is good" Haha lol
On a serious note, what me448 said was absolutely correct.
But if you don't wanna go too far from htc, you should try the sense roms out (there are only 2 ). They will give you a slight change in the looks but huge change in performance.
That being said, 'generally' people do have been experiencing better performance on cm10 than sense roms.
But I feel that as you have just rooted your phone, going from stock to cm10 would be a huge change. Basically, it's all down to personal preference.
Also, check out the frequently asked questions thread in the general section, or click on the link in my or me448 's signature.
It will help you to get started on things and might answer a few more questions you may have. Also, i heard it is good
burhanuddin said:
Guys Thanks very much for your Help
I have unlocked my HTC Desire C with your help
All credits goes to u all and XDA
Steps:
1) Unlocked Bootloader
2) My Mobile wasnt Rooted so i rooted by this video (Video)
3) Then Unlocked Sim Guide helped me via this Link
Thanks
Click to expand...
Click to collapse
Glad my guide was some help
Throw your thanks at the guy who wrote that guide if you Haven't already, he deserves it.
burhanuddin said:
In the second Guide, Its written i should have busybox install on my mobile, But when i go to play store there are many Busybox, which one should i download? and also software needs to be rooted and my mobile isnt rooted
Click to expand...
Click to collapse
Guys, I also want to unlock my sim on Desire C. I managed to get phone bootloader unlocked, Rooted, HTC driver installed and a busybox install. I am following the step 2 "Sim Unlock Guide [Desire C]"
but the procedure I don't follow.
1) Do I connect the phone with PC with USB cable under bootloader Mode or Recovery mode? I connect the phone with pc with USB, but it is NOT in Bootlaoder or Recovery Mode. I just have the phone boot normally
2) How busybox work?
3) I enter command "ADB Shell" in Windows-cmd, a bunch of thing flashed. I didn't get " sh-3.2#" , after I enter "SU", nothing happend on my phone, in cmd command prompt, it says "SU is not recogized command"
I don't think my PC is talking to the phone. what do I do? many thanks for your help.
i final figure out the problem, it's so silly, i just need to put in a microSD card in the phone, then adb command works perfectly, just log in to phone normally, plug in to your pc via USB, run the adb shell as instructed, unlock the phone is seconds
remember unlock code is 8 digits long, I got two sets of number, one set is 16 digits, it is not the unlock code
I am on VZW. My phone status was "UNLOCKED" upon arrival from Moto. Since then, I found that the status has changed to "LOCKED". The status has not changed back to "UNLOCKED" after a factory reset. I have neither unlocked the bootloader or rooted.
Does the status refer to the bootloader, or did my phone lock to the carrier. Either way, is there a way to return the status to "UNLOCKED"?
gmermel said:
I am on VZW. My phone status was "UNLOCKED" upon arrival from Moto. Since then, I found that the status has changed to "LOCKED". The status has not changed back to "UNLOCKED" after a factory reset. I have neither unlocked the bootloader or rooted.
Does the status refer to the bootloader, or did my phone lock to the carrier. Either way, is there a way to return the status to "UNLOCKED"?
Click to expand...
Click to collapse
Are you talking about the status in the bootloader?
If you want to unlock your bootloader there are a few guides on here to show you how.
skaforey said:
Are you talking about the status in the bootloader?
Click to expand...
Click to collapse
I am on the recovery screen itself. Before moving to the bootloader screen.
gmermel said:
I am on the recovery screen itself. Before moving to the bootloader screen.
Click to expand...
Click to collapse
Bootloader comes before recovery. The screen where you pick to boot to recovery, is the bootloader. Is this where you mean?
rootSU said:
Bootloader comes before recovery. The screen where you pick to boot to recovery, is the bootloader. Is this where you mean?
Click to expand...
Click to collapse
Then yes, the bootloader screen.........
Does that mean my phone is still not locked to VZW?
I guess now you know WHY I haven't rooted.
gmermel said:
Then yes, the bootloader screen.........
Does that mean my phone is still not locked to VZW?
I guess now you know WHY I haven't rooted.
Click to expand...
Click to collapse
well, when verizon finally releases, it might be sim locked. but you bought from motorola directly, and wont be sim locked to verizon, ever.
gmermel said:
Then yes, the bootloader screen.........
Does that mean my phone is still not locked to VZW?
I guess now you know WHY I haven't rooted.
Click to expand...
Click to collapse
The phone shouldn't have come unlocked from the factory. I suggest you backup your data and oem unlock the phone.
How do do an oem unlock?
gmermel said:
How do do an oem unlock?
Click to expand...
Click to collapse
Using fastboot commands you type fastboot OEM unlock to unlock your bootloader. This will wipe all of your data so you should back up anything you don't want to lose.
This is the easiest way to get everything done from unlocking and putting a custom recovery. This will also help you if you need to go back to stock for any reason.
http://www.wugfresh.com/nrt/
encephalon9986 said:
This is the easiest way to get everything done from unlocking and putting a custom recovery. This will also help you if you need to go back to stock for any reason.
http://www.wugfresh.com/nrt/
Click to expand...
Click to collapse
not really. the right way is the easiest way, and you learn along the way. using a toolkit, you will learn nothing, not even the basics. the right way to do it takes about 3-5 minutes..
1. fasdtboot oem unlock(this unlocks the bootloader)
2. fastboot flash a custom recovery
3. flash supersu in your new recovery
4. reboot with root.
simms22 said:
not really. the right way is the easiest way, and you learn along the way. using a toolkit, you will learn nothing, not even the basics. the right way to do it takes about 3-5 minutes..
1. fasdtboot oem unlock(this unlocks the bootloader)
2. fastboot flash a custom recovery
3. flash supersu in your new recovery
4. reboot with root.
Click to expand...
Click to collapse
Just because I am using the toolkit doesn't mean I don't know the basics. I've been modding phones since the droid x days and before android I had windows mobile. I just prefer the simplicity of toolkits. Wugfresh does an excellent job making this program. I agree knowing the basics is a good thing because you should know what needs to be done for this all to happen but then again toolkit is very simple.
encephalon9986 said:
Just because I am using the toolkit doesn't mean I don't know the basics. I've been modding phones since the droid x days and before android I had windows mobile. I just prefer the simplicity of toolkits. Wugfresh does an excellent job making this program. I agree knowing the basics is a good thing because you should know what needs to be done for this all to happen but then again toolkit is very simple.
Click to expand...
Click to collapse
who said anything about YOU? if you know what you are doing already, use a toolkit, i dont care. but if you are new to this, toolkits are not for beginners. simply because they dont teach anything, nor do you learn any of the basics.
simms22 said:
who said anything about YOU? if you know what you are doing already, use a toolkit, i dont care. but if you are new to this, toolkits are not for beginners. simply because they dont teach anything, nor do you learn any of the basics.
Click to expand...
Click to collapse
Very true I agree. Learning the actual way is the best to learn. Sometimes I like using the cmd because its more fun doing it yourself. Either way works but remember mod at your own risk (for the op).
encephalon9986 said:
This is the easiest way to get everything done from unlocking and putting a custom recovery. This will also help you if you need to go back to stock for any reason.
http://www.wugfresh.com/nrt/
Click to expand...
Click to collapse
Are there Mac tools as powerful and straightforward as Wugfresh?
I rooted my N7 using this tool. Simple for even me. However, that was when I had bootcamp on my Mac and could use Windows.
I use Apex launcher and am happy working in stock. The feature I miss is being able to use Titanium/TWRP for recovery. I have learned how to rebuild my system easily via file transfer, and using Terminal to root the phone isn't worth the down-side risks to me.
gmermel said:
Are there Mac tools as powerful and straightforward as Wugfresh?
I rooted my N7 using this tool. Simple for even me. However, that was when I had bootcamp on my Mac and could use Windows.
I use Apex launcher and am happy working in stock. The feature I miss is being able to use Titanium/TWRP for recovery. I have learned how to rebuild my system easily via file transfer, and using Terminal to root the phone isn't worth the down-side risks to me.
Click to expand...
Click to collapse
You can use fastboot on a Mac. Its even easier than windows. If you don't know how to use fastboot, if you've been reading the thread, we're saying do not use a toolkit.
Do you even need an unlocked bootloader? I don't think it came unlocked from the factory.
rootSU;58263052
Do you even need an unlocked bootloader? I don't think it came unlocked from the factory.[/QUOTE said:
Probably not. I was more interested in whether the "lock" referred to the phone/SIM. As long as that's not an issue I'm good.
However, in the spirit of the flow, I would like to learn to root on my Mac for its own sake. That being said, I'm not confident that I understand the various how-to's I've read to give it a go. As I mentioned, I don't want to play in Terminal, and I've never heard of "fastboot" as it relates to the Mac. If, however, the fastboot you are speaking of is the one on the phone itself (not the Mac), my lack of knowledge should be self evident. At least I know enough to not go where I don't know enough........
Click to expand...
Click to collapse
gmermel said:
However, in the spirit of the flow, I would like to learn to root on my Mac for its own sake. That being said, I'm not confident that I understand the various how-to's I've read to give it a go. As I mentioned, I don't want to play in Terminal, and I've never heard of "fastboot" as it relates to the Mac. If, however, the fastboot you are speaking of is the one on the phone itself (not the Mac), my lack of knowledge should be self evident. At least I know enough to not go where I don't know enough........
Click to expand...
Click to collapse
what is fastboot? http://www.androidcentral.com/android-z-what-fastboot
download fastboot for Mac http://www.androidcentral.com/sites/androidcentral.com/files/uploads/tools/fastboot-mac.zip
gmermel said:
Probably not. I was more interested in whether the "lock" referred to the phone/SIM. As long as that's not an issue I'm good.
However, in the spirit of the flow, I would like to learn to root on my Mac for its own sake. That being said, I'm not confident that I understand the various how-to's I've read to give it a go. As I mentioned, I don't want to play in Terminal, and I've never heard of "fastboot" as it relates to the Mac. If, however, the fastboot you are speaking of is the one on the phone itself (not the Mac), my lack of knowledge should be self evident. At least I know enough to not go where I don't know enough........
Click to expand...
Click to collapse
You would have to use a terminal but its very simple.
A terminal just means you type stuff and press enter instead of clicking buttons.
Fastboot is on both the phone and the computer. From the computer there is a fastboot for windows, Linux and Mac. You simply install them and type the commands from terminal.
This is my nexus 5 thread. Everything is relevant except the windows USB driver section
http://forum.xda-developers.com/showthread.php?t=2807273
Hi guys -
I'm somewhat a newbie here. I think I have bricked my Nexus 6. I had root and an unlocked bootloader. I had Chroma riom installed and was trying to go back to stock rom, unrooted with locked bootloader and through TWRP i deleted everything, including the OS I believe. So now my phone is locked on the Google startup screen (unlocked bootloader) . Suggestions?
Thanks -
John
if your bootloader is unlocked you should be able to fastboot clear cache and user data , then flash a rom from twrp. I would refrain from ever locking the bootloader back up since the update where you have to enable unlock bootloader in Dev Options.
droidstyle said:
if your bootloader is unlocked you should be able to fastboot clear cache and user data , then flash a rom from twrp. I would refrain from ever locking the bootloader back up since the update where you have to enable unlock bootloader in Dev Options.
Click to expand...
Click to collapse
me too I'm have Nexus 6 5.1.1 no recovery...except the bootloader that's locked Code: 2 , i can't unlock it, any solution !!?
hadifreestyler said:
me too I'm have Nexus 6 5.1.1 no recovery...except the bootloader that's locked Code: 2 , i can't unlock it, any solution !!?
Click to expand...
Click to collapse
no you are bricked unfortunately. the unlock bootlader option in dev options really seems to have caused more issues then good.
I am wondering if Jtag will fix these devices?
jpl81905 said:
Suggestions?
Click to expand...
Click to collapse
Stop.
Read.
A lot.
You have an unlocked nexus with custom recovery installed, and you don't know what to do? You shouldn't be messing with this stuff. You lack VERY basic understanding. Read the stickies.
https://developers.google.com/android/nexus/images?hl=en
Factory images. Follow their directions.
scryan said:
Stop.
Read.
A lot.
You have an unlocked nexus with custom recovery installed, and you don't know what to do? You shouldn't be messing with this stuff. You lack VERY basic understanding. Read the stickies.
https://developers.google.com/android/nexus/images?hl=en
Factory images. Follow their directions.
Click to expand...
Click to collapse
Thank you. I think.
jpl81905 said:
Hi guys -
I'm somewhat a newbie here. I think I have bricked my Nexus 6. I had root and an unlocked bootloader. I had Chroma riom installed and was trying to go back to stock rom, unrooted with locked bootloader and through TWRP i deleted everything, including the OS I believe. So now my phone is locked on the Google startup screen (unlocked bootloader) . Suggestions?
Thanks -
John
Click to expand...
Click to collapse
The easiest way if you are not familiar with ADB is to download the nexus tool kit located on these forums from WUGFRESH. That tool will walk you through a step by step process on how to flash stock back. You are far from bricked. I have deleted my entire phone many a times and just re flashed stock back easily. As long as your boot loader is unlocked you are fine
Link to toolkit: http://www.wugfresh.com/nrt/
The option you are going to want to use is on the front of the toolkit called flash stock + un-root. You can watch some videos on his website as well for flashing stock. That is all you need to do .
Any questions let me know, send me a PM
backdown00 said:
The easiest way if you are not familiar with ADB is to download the nexus tool kit located on these forums from WUGFRESH. That tool will walk you through a step by step process on how to flash stock back. You are far from bricked. I have deleted my entire phone many a times and just re flashed stock back easily. As long as your boot loader is unlocked you are fine
Link to toolkit: http://www.wugfresh.com/nrt/
The option you are going to want to use is on the front of the toolkit called flash stock + un-root. You can watch some videos on his website as well for flashing stock. That is all you need to do .
Any questions let me know, send me a PM
Click to expand...
Click to collapse
It is not the easiest option. The easiest option is plug the USB cable in, boot to TWRP, enable MTP mode and copy a rom to the sdcard.
Also, many senior members here will discourage the use of toolkits for those who are not familiar with adb or fastboot. It is best to learn these and use them at least once before starting to use toolkits. Toolkits do not "walk you through". They take you through without explaining anything.
danarama said:
It is not the easiest option. The easiest option is plug the USB cable in, boot to TWRP, enable MTP mode and copy a rom to the sdcard.
Also, many senior members here will discourage the use of toolkits for those who are not familiar with adb or fastboot. It is best to learn these and use them at least once before starting to use toolkits. Toolkits do not "walk you through". They take you through without explaining anything.
Click to expand...
Click to collapse
In a perfect world, I am sure we would all love to dive in and discover everything and be experts in all fields as time would not be a factor. I do not disagree it is helpful to learn ADB and fastboot commands and understand what they do. At this point in time though, the end goal here is to get his phone back up and running as fast as possible and then he can do the post-mortem to figure out what he did wrong and how to fix it .
I am guessing hes not very familiar with TWRP since he wound up in this situation. The toolkit alleviates the need for knowledge and gets the job done. I'm sure after this, the OP will research how to use his phone before trying to do anything next.
backdown00 said:
In a perfect world, I am sure we would all love to dive in and discover everything and be experts in all fields as time would not be a factor. I do not disagree it is helpful to learn ADB and fastboot commands and understand what they do. At this point in time though, the end goal here is to get his phone back up and running as fast as possible and then he can do the post-mortem to figure out what he did wrong and how to fix it .
I am guessing hes not very familiar with TWRP since he wound up in this situation. The toolkit alleviates the need for knowledge and gets the job done. I'm sure after this, the OP will research how to use his phone before trying to do anything next.
Click to expand...
Click to collapse
..but even so, your method is overkill. It is really simple to boot into TWRP and look in the menu for the "Enable MTP" option. Once that is done, the phone appears in "Computer" as an MTP device, just like when you boot into android. Then, simply dragging and dropping a ROM onto that device then flashing it via recovery will get him back up and running. There is nothing simpler or quicker than this.
Sorry, I do not intend to be confrontational here.
Hey everyone I'm looking here as my last resort before sending my phone back to Motorola.
Bought a Nexus 6 from motorola uk which was delivered yesterday, switched phone on and all the Google apps on the phone updated, then had a notification OTA to download and install android 5.1 which I did, towards the end of the install process I had an error with the green android and a red exclamation mark.
I powered the device off with the power button and it turned back on and ever since it says "Android is starting" "Optimizing app 1 of 125" once it goes through all the apps it gets to the android boot screen then just goes back to the "Android is starting" "Optimizing app 1 of 125" over and over and over. (Infinite bootloop)
Pointers: The phone is not unlocked or rooted as I'm a noob its just fresh out the box, also I never opened/unlocked the developer options.
I have tried various recovery mode fixes, wiping cache and wiping all data and then rebooting the device with no luck.
Is there anyway I can hook my N6 up to my computer and fix this with a tool kit etc? I'm willing to try but I'd need basic instructions and reassurance it wouldn't muck up my warranty if it didn't work as my only other option is to exchange for a new device.
I'm a noob so I need detailed basic step by step instructions.
Any help, advice etc would be hugely appreciated. Thanks
Just send it back, no point messing about with it if it brand new could down to a fault with the hardware itself.
ixon2001 said:
Just send it back, no point messing about with it if it brand new could down to a fault with the hardware itself.
Click to expand...
Click to collapse
Iv'e heard this is a common problem with the N6 whilst trying to update the OTA 5.1 I had no other apps on the phone it was fresh, I did nothing wrong, I know someone who has been through 4 devices with the same bloody issues! In the end he had to sideload 6.0 and I'm not confident in being able to do that.
Well best bet is to download wugfresh toolkit 2.10 i think is the latest version, follow the instructions carefully because first you need to unlock the bootloader then flash 6.0.1 which has just come out.
Using Wugfresh is the best way to go if your new to flashing & you can't really go wrong with it.
ixon2001 said:
Well best bet is to download wugfresh toolkit 2.10 i think is the latest version, follow the instructions carefully because first you need to unlock the bootloader then flash 6.0.1 which has just come out.
Using Wugfresh is the best way to go if your new to flashing & you can't really go wrong with it.
Click to expand...
Click to collapse
I`am sure most xperienced users (me included) will not agree with you The best way to unlock, flash and root is still adb/fastboot. Especialy for lesser xperienced users that are lost is something goes wrong while using the toolkit, wich happens frequently btw. Just check the help threads.
gee2012 said:
I`am sure most xperienced users (me included) will not agree with you The best way to unlock, flash and root is still adb/fastboot. Especialy for lesser xperienced users that are lost is something goes wrong while using the toolkit, wich happens frequently btw. Just check the help threads.
Click to expand...
Click to collapse
Lol it's not rocket science using adb, been doing that way for years but for somebody that never flashed, rooted ect I still think the toolkit best way to go at first because everything is done for you at a click of a button.
Yes things can go tits up when using toolkits, mainly because they don't follow simple instructions.
ixon2001 said:
Lol it's not rocket science using adb, been doing that way for years but for somebody that never flashed, rooted ect I still think the toolkit best way to go at first because everything is done for you at a click of a button.
Yes things can go tits up when using toolkits, mainly because they don't follow simple instructions.
Click to expand...
Click to collapse
Lets agree to disagree
OK
ixon2001 said:
Yes things can go tits up when using toolkits, mainly because they don't follow simple instructions.
Click to expand...
Click to collapse
No, but because toolkits are always behind at least one version with marshmallow. People kept bricking their devices with toolkits when marshmallow came out and they thought they could root it. As 6.0.1 came out they'll do something else wrong.
Toolkits are not help. It's the lazy way if everything is already working and up to date.
Also what can a toolkit do if this phone doesn't even have developer options turned on? If it's in boot loop, as the OP said, then the Enable OEM unlocking was never set, then the only solution is to send it back. Unless there's a toolkit magic we don't know about.
Sent from my Nexus 6 running cyosp using Tapatalk
istperson said:
N
Also what can a toolkit do if this phone doesn't even have developer options turned on? If it's in boot loop, as the OP said, then the Enable OEM unlocking was never set, then the only solution is to send it back. Unless there's a toolkit magic we don't know about.
Click to expand...
Click to collapse
I think op created another thread http://forum.xda-developers.com/nexus-6/help/nexus-6-stuck-bootloop-trying-to-update-t3266100 for this issue - and was somehow able to unlock the bootloader (not sure how that worked if OEM unlock was never set)
jj14 said:
(not sure how that worked if OEM unlock was never set)
Click to expand...
Click to collapse
It was said that some of the first Nexus 6s with the original 5.0 came out with a bootloader that didn't check for this switch.