Database Develop

[Q] Help needed: tried to install Cyanogen 11, can't boot.

Hello all! So, I tried to install CM11, the one on this post.
Went into CWM, did Wipe data factory reset and formatted /system. when I tried installing the rom, it said operation aborted and it could not install it. No biggie, the post says to install cm10.2 before doing so.
So i Powered the phone off to copy the file over to the SD. To my surprise, now I can't get into CWM, Philz, TWRP, fastboot or flashmode. Whenever I press the back pin to power the phone off, it turns back on automatically before I have time to press the key and connect the USB cable. Furthermore, when I manage to do it quick enouhg, the green led lights up, but it fades away after 10ish seconds only to display the sony logo again, and a "can't recognize USB device" popup comes up in my PC. I've used flashtool with this same pc in the past, so I don't know what that is about. Also, whenever I try installng flashtool drivers again, just in case 2 things happen:
there is no xperia SP device listed and whatever i select it fails to install.
What can I do now? I had 4.3 with the eXistenZ Ultra ROM before all of this.
Damm, this is the first time this happens to me, I've been swapping roms for ever, and this is not even the first phone i do this in, had a galaxy s2 and a wildfire S before. I feel like such a noob
UPDATE!:
So I finally managed to fix it. I posted this after about 8-9 hours of trying to get into fastboot on the 3 different pcs in my household, all had the drivers at some point and i've worked with them and fastboot and this same phone previously, so I figured they'd still work. They didn't, I couldnot even get SUS to work. So i went to a 4th PC, installed SUS and the needed drivers and it only took like 40 minutes worth of tries. I'm in the software download part of the SUS, i'll keep this updated!
UPDATE2!:
So, it finished downloading but it suddenly disconnected, tried again for about 10 minutes and then got it going again. Downloaded the second time and installed it successfully. Leaving this up for future reference!
Bottomline: if you can't get into flashmode, try on as many PCs as you have available for at least 30 minutes each.

Don't use flash tools just install CM11 with CWM or something, use doomlord kernel to get CWM and install CM11 zip that's it.
Sorry locked boot loader didn't read it correctly don't use my advice .

Th3Duck said:
Don't use flash tools just install CM11 with CWM or something, use doomlord kernel to get CWM and install CM11 zip that's it.
Sorry locked boot loader didn't read it correctly don't use my advice .
Click to expand...
Click to collapse
No problem, it kinda sorted itself out by brute force connections :> Dammed sony, locking the bootloaders for real. I even got the sim unlock code from my phone company and it's still not bootloader unlockable at the phone settings, even though i can now get any sim i want in it -.-

[Q] Nexus 6 not booting up after random shut down

Good evening, everyone.
Few hours ago, my N6 randomly shut down and not booting up to the system. I tried to re-install the factory image for 5.0.1 but I got stuck at bootloader screen. I tried every options available from bootloader screen(Start, Recovery mode, Restart bootloader etc.) but it performed nothing but coming back to the bootloader screen. When I tried to use 'Nexus Root Toolkit' to install new system and whenever the process was trying to initiate the process, it is giving me same error message 'FAILED <remote failure>'
What can I do from here?
I appreciate your attention.

chg911225 said:
Good evening, everyone.
Few hours ago, my N6 randomly shut down and not booting up to the system. I tried to re-install the factory image for 5.0.1 but I got stuck at bootloader screen. I tried every options available from bootloader screen(Start, Recovery mode, Restart bootloader etc.) but it performed nothing but coming back to the bootloader screen. When I tried to use 'Nexus Root Toolkit' to install new system and whenever the process was trying to initiate the process, it is giving me same error message 'FAILED <remote failure>'
What can I do from here?
I appreciate your attention.
Click to expand...
Click to collapse
If your bootloader is unlocked, you should be able to either flash the stock factory image, or re-flash each partition separately through the tool-kit. Since you're getting remote errors with the toolkit, double check that you have the right drivers installed, the tookit and a search on the forum should help with that.

did you already try :
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008

Don't want to raise any alarms already but I shut mine down on Sunday night (Unlocked/ Rooted/ custom kernel & rom) in order to boot in Recovery and flash a new kernel version and:
1) The sdcard looked empty, it read ~ 26 GB free (I had no more than 20 gb free before reboot) and no folders whatsoever.
2) The phone was stuck at the Google logo heating up but going nowhere.
As I said don't want to start assuming things but the phone randomly going "nuts" and losing all data is scary... I had to spent my entire day yesterday flashing stock 5.0.1 back and re-setting up everything. I followed the guide posted above (http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 oh, go with Method 2 and it will work fine).
Out of curiosity how does your SD look like from recovery? Oh, but then you say you can't even boot to Recovery. Which recovery do you have? (I had/have TWRP 2.8.3.1 ). Anyway to repair it you only need to be able to boot into Bootloader properly I guess.

[Q] Stuck on Welcome Screen... lenovo k3 note

(its my dad phone)
hi so yestarday i installed the "aosp-k3note-5.1.0" rom and it all went fine but worked slow and without bluetooth.
so today when i got home my dad told me he just installed a new rom from romnation(he dosent remember which rom but he said it was an offical rom)
BUT he downloaded it stright to the phone and installed it without erasing anything(date/cache/davlik)...
so when he tried to use the phone it will gives errors like gaps stoped working and all kind of stuff that made the phone useless...
so i downloaded "VIBEUI_V2.8_1526_7.80.1_DEV_K50-T5" rom and gapps64 and went to the CMW and this time i erased the date cach and davlik and installed the rom and after that the gapps
and now i cant get past the welcome screnn becuase as soon as i choose english or chinse it will give me "wlan has stopped" and return to the language menu...
so now im stuck becuase i cant use adb to root it and SP tools dosent work too(i tried to keep it pluged for an hour and it still wont do anything with ot without the battery)
what can i do? and thanks for any help...

Try this to get CWM back on.
rollcage0 said:
(its my dad phone)
hi so yestarday i installed the "aosp-k3note-5.1.0" rom and it all went fine but worked slow and without bluetooth.
so today when i got home my dad told me he just installed a new rom from romnation(he dosent remember which rom but he said it was an offical rom)
BUT he downloaded it stright to the phone and installed it without erasing anything(date/cache/davlik)...
so when he tried to use the phone it will gives errors like gaps stoped working and all kind of stuff that made the phone useless...
so i downloaded "VIBEUI_V2.8_1526_7.80.1_DEV_K50-T5" rom and gapps64 and went to the CMW and this time i erased the date cach and davlik and installed the rom and after that the gapps
and now i cant get past the welcome screnn becuase as soon as i choose english or chinse it will give me "wlan has stopped" and return to the language menu...
so now im stuck becuase i cant use adb to root it and SP tools dosent work too(i tried to keep it pluged for an hour and it still wont do anything with ot without the battery)
what can i do? and thanks for any help...
Click to expand...
Click to collapse
Try removing the battery and plugging the phone in to the PC.
Start SP Tools with CWM set in the scatter and only recovery ticked
Press Download in SP tools and then insert the battery
CWM should download to phone
If that fails repeat but plug the phone in once you press Download, then insert the battery.

rollcage0 said:
(its my dad phone)
hi so yestarday i installed the "aosp-k3note-5.1.0" rom and it all went fine but worked slow and without bluetooth.
so today when i got home my dad told me he just installed a new rom from romnation(he dosent remember which rom but he said it was an offical rom)
BUT he downloaded it stright to the phone and installed it without erasing anything(date/cache/davlik)...
so when he tried to use the phone it will gives errors like gaps stoped working and all kind of stuff that made the phone useless...
so i downloaded "VIBEUI_V2.8_1526_7.80.1_DEV_K50-T5" rom and gapps64 and went to the CMW and this time i erased the date cach and davlik and installed the rom and after that the gapps
and now i cant get past the welcome screnn becuase as soon as i choose english or chinse it will give me "wlan has stopped" and return to the language menu...
so now im stuck becuase i cant use adb to root it and SP tools dosent work too(i tried to keep it pluged for an hour and it still wont do anything with ot without the battery)
what can i do? and thanks for any help...
Click to expand...
Click to collapse
Omg..i have almost exactly the same problem and the solution that MrAAnderson suggested didn't work.Here's how i ended in this problem.I was running VIBEUI_V3.0_1602_7.407.1_DEV_K50-T5 ROM on TWRP recovery made By Pr1nc3V app Lenovo K3 Note Manager [v2.1].Since i had annoying bug with "R" (roaming icon) and "gapps stopped working" issue i wanted to re-flash same ROM.I entered into TWRP recowery,cleared dalvik+cache,rebooted into recovery again.Now i wanted to flash ROM,but it didn't flash it gave me an error,same thing happens if i try to flash stock recovery (i even tried naming ROM and recovery as "recovery.zip" and "update.zip").Rebooted the phone but i'm also stucked on welcome screen where i can't pass it because of "Unfortunately,WLAN stopped working".
Tried to flash ROM and stock recovery with SPFlashTool but the tool doesn't see phone at all,same as Lenovo K3 Note Manager by Pr1nc3V .Right now i'm running out of solutions for this mess i created,any advice will help.Help me please to restore my phone.
EDIT: i just realized that i actually made a "factory reset" in TWRP recovery..not just wipe data,cache and dalvik.....what are my options now folks?

Ok i'm happy to announce that i resolved my problem (after a panic mode on,lol).Here is what i did..
1. Obviously you have to get back on your stock (original,ugly chinese-english one) recovery (in case you already didn't..).To do that i used SP Flash tool.(i wouldn't go into details but if you need just ask).
After that we have following situation..stock recovery + dev ROM (which isn't working well).
2.If you try to flash any ROM in this state it will fail (based on my experience,i tried to flash exactly same ROM which is already installed..no way.).So now next step is to get a CUSTOM (TWRP or CM) recovery,again flashing it with SP Flash tools.
From this point you can choose wher would you go...STOCK rom ,MODDED one ...anything actually.I hope i clarified a bit.

sptools is not detecting my device

Z1 stuck in boot loop after fumbling my way around a Chinese recovery

So I recently tried updating MIUI v5 to MIUI v6. However, I stupidly opted for the FOTA update, rather than updating using recovery.
After running the update, my phone rebooted and it worked fine, MIUI v6 running great. However, because I'd updated using the in-built updater, my data and apps were still there from before. This was causing no-end of 'process stopped running' alerts, which drove me crazy after around 10 minutes.
Therefore, I decided to try and wipe my data. I went to the recovery menu and found that MIUI had installed its own Chinese recovery, my previous TeamWin one was gone. So I fumbled around and managed to find the 'Wipe data' etc. option, and chose it. I was presented with a couple more options which I didn't understand, and (stupidly) accepted both. This left me with a phone that would no longer boot past the 'Sony' logo. I was also unable to access the Chinese recovery menu.
Feeling a little worried at this point, I started to Google around for guides on how to flash a recovery back onto a phone stuck in a boot loop. After hours of searching, I decided it wasn't possible and instead follow a guide for fixing 'boot loops' through flashing an original Sony 'ftf' firmware using flashtool.
Now, the guide I was following was quite old, and provided a link to 'C6903_14.2.A.0.290_Global LTE' - so this is what I used to flash (which I'm now regretting). Before flashing, I was presented with some options, for which the guide I was following recommended I deselect the 'kernel' option. So I did this too.
After around 10-15 minutes and what seemed like a successful flash, I tried turning the phone on. This time, the Sony logo appears, then disappears to a black screen, and then the backlight turns off, followed by the Sony logo, then a black screen, then backlight turning off, etc. So slightly different behaviour to before, but still boot looping.
I think what may have happened is that MIUI includes an updated kernel, and through flashing the 14.2.A.0.290 firmware without a kernel, I've introduced some sort of incompatibility.
The problem I'm having now is getting another firmware onto the phone in order to resolve this. For some reason, despite flashtool recognising the phone being plugged in with flash mode, it refuses to load the firmware - I'm instead presented with the message:
"You must have the according fsc script to flash this device."
Does anyone know how I might be able to get around this? I admit to being a bit of a noob when it comes to flashing so have probably dug my own hole here, and seem to have left myself completely unable to work out what I need to do in order to get back out! Any help would be hugely appreciated.

Please see the attached screenshot of what I see when I try flashing with flashtool. The whole flash takes around 2 seconds, so it appears as though nothing's actually happening. However, it did flash successfully before, only without the kernel (which I think is what's causing my problems).
Please help!

langauld said:
Please see the attached screenshot of what I see when I try flashing with flashtool. The whole flash takes around 2 seconds, so it appears as though nothing's actually happening. However, it did flash successfully before, only without the kernel (which I think is what's causing my problems).
Please help!
Click to expand...
Click to collapse
This version of Flashtool you're using is known to require some files for your device to be able to work.
Try using the version before it.
Oh and NEVER:
- Wipe /system and /data using recovery with unlocked bootloader (it will remove everything and the phone will not be able to boot).
- Flash an ftf of a older android version (like flashing kitkat on top of lollipop) without including kernel because that will cause a bootloop. (not sure about flashing lollipop on top of kitkat but I think it's the same)

Just2Cause said:
This version of Flashtool you're using is known to require some files for your device to be able to work.
Try using the version before it.
Oh and NEVER:
- Wipe /system and /data using recovery with unlocked bootloader (it will remove everything and the phone will not be able to boot).
- Flash an ftf of a older android version (like flashing kitkat on top of lollipop) without including kernel because that will cause a bootloop. (not sure about flashing lollipop on top of kitkat but I think it's the same)
Click to expand...
Click to collapse
You sir, are a god amongst men. I'd never have thought to try the previous version of FlashTool. From reading around, I knew some devices had issues with it, but because it lists the Z1 as being 'supported', I didn't think that would apply to me.
I flashed again without deselecting the kernel and it booted first time. Thank you again.

langauld said:
You sir, are a god amongst men. I'd never have thought to try the previous version of FlashTool. From reading around, I knew some devices had issues with it, but because it lists the Z1 as being 'supported', I didn't think that would apply to me.
I flashed again without deselecting the kernel and it booted first time. Thank you again.
Click to expand...
Click to collapse
Glad I could help.

Need help rooting-

I am having a hell of a time rooting this phone. (Motorola Nexus 6 XT1100)
I am trying to follow this guide: https://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
If anyone can offer some suggestions, they would be greatly appreciated.
I managed to get as far as unlocking the bootloader in fastboot mode.
The next step, obtaining root, is where all my problems started.
I downloaded CF Root and extracted the files, as instructed, allowed the root tool to run, (I'm using Linux, if it matters).
When the process was finished, and my phone attempted to reboot, it got stuck on the Google screen with the little lock (showing unlocked).
I allowed the phone to stay in this mode for around 30 minutes thinking it just needed time.
It never did anything. I attempted to let it try and start up again (a couple times actually) and it never goes past the Google lock screen.
I powered down the phone and restarted in fastboot mode, and attempted to run the CF Root tool again, with the same result.
I am currently stuck with only having access to fastboot.
I tried to flash a recovery and boot into that, but it won't allow that either. Perhaps this isn't even possible (YET), as it's not in the instructions to flash a recovery until after the rooting process, but I thought I would try it anyway.
I have tried flashing TWRP and Lineage recovery. No success with either, although the terminal is saying
sending 'recovery' OKAY
writing 'recovery' OKAY
But when trying to reboot recovery I get hit with
unknown reboot target recovery
Anyone know what's going on and how I can get this resolved? I just want to install a recovery and flash a custom ROM.

In that guide you can follow my journey to root starting in post# 929. I had & have had a LOT of help from my fellow XDAers. They're great & thank you all.

Thanks!
I'll check it out.

Boy, oh, boy.
I don't know what is going on.
I finally managed to get out of the bootloader screen.
I don't know what/how it worked. I downloaded Nexus Root Toolkit to a windows computer and tried the Flash Stock + Unroot option.
It keep saying waiting on device or device not detected or something ( I cant remember exactly, it was hours/many error screens ago!)
Next, I tried the option for Root + Add a Custom Recovery and directed it to where my TWRP file.
Again it acted like it was doing something. Even found my connected ADB device. Went through a couple processes, said it would need to restart a couple/few times. Everything was trucking along just fine until suddenly, it got hung up 'Waiting on device"
Not sure what happened, but all of a sudden, it could no longer find my device.
For chits and giggles, I decided to try and reboot recovery from the bootloader screen. I had attempted this many times and all it did was start back up in bootloader, BUT, this time, it actually started up in some recovery program I have never seen before. It wasn't stock and it certainly wasn't TWRP!
At this point, I hooked my device back into my computer running Linux and attempted to push TWRP, and reboot in recovery.
It worked!
Now that I had a recovery I was comfortable using, I proceeded to push my ROM.
Wanted to try Lineage with MicroG, but I am not advanced enough to go that route. I could not get a fake app store to work.
Guess I'll have to stick with what I know. I love the idea of MicroG, but it apparently doesn't work with Pure Nexus.
Anyway, just wanted to post some closure for this thread. I know the Motorola Nexus 6 is an old phone, but I like it. This is my second one. My first one, screen finally cracked and it was cheaper to just purchase a new one from Amazon than to replace the screen.