yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Q&A, Help & Troubleshooting] GedBlake:
Hi, ghassir...

Sorry, but you're very likely permanently softbricked :( .

If your bootloader is locked, and is unlockable, due to the Allow OEM Unlocking setting in Developer Options not being previously enabled (or perhaps disabled), when your device last successfully booted Android, then your device is bricked.

Although, you must have been bootloader unlocked at some point, otherwise, how did you manage to arrive at your current situation?

I wish I had better news for you...

Rgrds,

Ged.

---------- Post added at 11:08 PM ---------- Previous post was at 10:44 PM ----------

Actually, thinking about it... I don't see how you could have arrived at your present situation.

Deleting system either via TWRP or via fastboot (format or erase), would have rendered your device unbootable.

Which begs the question, how did you manage to disable...

SETTINGS>>DEVELOPER OPTIONS>>OEM unlocking (allow the bootloader to be unlocked) ???

...and which requires the device to be booted into Android, in order to access that setting.

-----

Are you certain your bootloader is either...

a) Locked.

~ or ~

b) Unlockable, and cannot be unlocked?

-----

The command for unlocking the bootloader is...

fastboot oem unlock

Rgrds,

Ged.
[Nexus 6 Q&A, Help & Troubleshooting] GedBlake:
Yeah, I think you're out of luck here... :(.

If the bootloader won't unlock with fastboot oem unlock, and you don't have TWRP installed, I can't see how you can recover from this :(.

Although I'm still puzzled what sequence of events lead you to this situation.

Rgrds,

Ged.
[Nexus 6 Q&A, Help & Troubleshooting] GedBlake:
I'm not quite sure what you mean by "system/userdata/cache/bootloader". The way you flash a bootloader, via fastboot, on a Nexus device, is...

fastboot flash bootloader <name-of-bootloader-file.img>

Anyway, your problem isn't flashing the bootloader, it's unlocking it... And I still suspect it still might be unlockable.

What happens when you run...

fastboot oem unlock

What output do you see? What error messages, if any, do you get?

-----

If you can unlock the bootloader, your device may be recoverable. I'm not particularly optimistic about this, but there's a slim chance... :). But I need to see the output from this command.

Rgrds,

Ged.
[Nexus 6 Q&A, Help & Troubleshooting] GedBlake:
Well... That's pretty unambiguous. You're device is bricked :(.

But I've been doing a bit of digging on the interweb, and I found this in Google Groups...

https://productforums.google.com/forum/#!topic/nexus/o5LSR3-1bl4

Take a look at the post by a guy called Gorgulov, whose Nexus 6 was in a similar state to yours.

He used...

fastboot format cache
fastboot format userdata

...commands which apparently are not forbidden by a locked bootloader. Somehow, this got his Nexus 6 up and running again. I've read similar accounts of other people using these commands to fix this problem.

I've no idea if this will work for you, but it's probably worth a try.

If this doesn't work, then you'll need to return your device for repair or replacement.

For what it's worth, best of luck...

Rgrds,

Ged.
[Nexus 6 Q&A, Help & Troubleshooting] GedBlake:
Not sure where you got that download from; the Google factory stock image for the Nexus 6 is available here...

https://developers.google.com/android/nexus/images#shamu

But it's immaterial anyway... You CANNOT fastboot flash anything with a locked bootloader. It just can't be done.

This is why you couldn't flash a recovery... any command beginning with fastboot flash... **absolutely** requires an unlocked bootloader.

I just wish I could have helped you find a way of fixing your device :(.

Rgrds,

Ged.
[Nexus 6 Q&A, Help & Troubleshooting] efrant:
No. Only way is to return the device for repair.
[Nexus 6 Q&A, Help & Troubleshooting] danarama:
If there was a solution, I would have answered "Yes".
[Nexus 6 Q&A, Help & Troubleshooting] danarama:
I can't translate it, but you already have our answer.
[Nexus 6 Q&A, Help & Troubleshooting] danarama:
Here is the deal, no one here knows how to fix it. We have been looking for months. If you have no OS and no Custom Recovery, you cannot unlock the bootloader. You must find a way to get it repaired with Motorola, even if it means sending it to a friend in another country. You may have to pay money.
[Nexus 6 Q&A, Help & Troubleshooting] ghassir:
Hi every one, is this works in stock recovery, not twrp/cwm?
[Nexus 6 Q&A, Help & Troubleshooting] efrant:
Deleting your previous questions and asking the same question over and over will not get you a different answer.

The answer is still no. There is no way to get your device functioning again without sending it in for repair.
[Nexus 6 Q&A, Help & Troubleshooting] crocoMilu:
same problem on Moto X

Hi, I know it's not a Moto X thread, but I have the same problem with my Moto X 2014. Unlocked bootloader, stock recovery and when I try tu unlock the bootloader "Enable OEM Unlock". Is there a way to pass over this?

Thakns:)
[Nexus 6 Q&A, Help & Troubleshooting] efrant:
If your bootloader is locked and you have the stock recovery and you can't boot Android, you are out of luck. No one has found a solution besides returning the device for repair.
[Nexus 6 Q&A, Help & Troubleshooting] crocoMilu:
Ok :( Thanks for the response.
[Nexus 6 Q&A, Help & Troubleshooting] akaiinuku:
Hi, i seem to be in an interesting situation.

I am currently have TWRP and root, running a version of pure nexus 5.1.1 ROM.

I want to return to stock. I was using Wug's toolkit to do this. I clicked the flash stock and unroot button and it took me to the bootloader and you get that series of popups saying i need to be unlocked. It also said that allow oem unlock needed to be checked. So it rebooted and sent me back into system. I went to developer options and allow oem unlock was unchecked, so i checked it and tried again.

Right now it just keeps going into bootloader and telling me that i need to unlock first, and it keeps sending me back into system. The live log in Wug's toolkit says that that bootloader status is locked. but my bootloader says Device is unlocked. status code 1.

So i did some research and came across this thread. I attempted to apply the fix but fastboot oem unlock just throws an error.

Anybody know where i should go from here?
[Nexus 6 Q&A, Help & Troubleshooting] istperson:
What error? Copy here what it says.

Also check the cable, switch to other USB port, reinstall drivers if on Windows.

And don't use toolkits.
[Nexus 6 Q&A, Help & Troubleshooting] akaiinuku:
That is the error i am getting. I also tried to do fastboot OEM unlock on another PC. Same result

...

(bootloader) fastboot oem unlock disabled!

FAILED (remote failure)

finished. total time: 0.030s
[Nexus 6 Q&A, Help & Troubleshooting] istperson:
But your phone should be unlocked, you have a custom rom on it. You shouldn't unlock it again.

Also it must be in bootloader mode to unlock, and not booted or in recovery.

You still have TWRP am I right?

Try these steps, the longer variant and tell us what you see:

http://xdaforums.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
[Nexus 6 Q&A, Help & Troubleshooting] akaiinuku:
Before I manually flash i want to answer your questions.

I was in bootloader when I used the fastboot oem unlock command.

I do still have TWRP and it works fine.

In my bootloader there is a line that says DEVICE is unlocked. Status code 1.

Im under the impression that this means i am unlocked.

The only thing i am worried about right now is that, i am unsure if I had "allow oem unlock" toggled on or off when i flashed a new ROM.

But if my bootloader says im unlocked then i should be golden right?

Either way i'll wait for your answer before i proceed to manually flash.

Thank you very much for your help thus far.
[Nexus 6 Q&A, Help & Troubleshooting] istperson:
Since you can only flash things if it's unlocked, you can't go wrong with that. Bottom line, it will say it could't flash since it was locked.

And I'm absolutely sure "allow oem unlock" was unlocked, because otherwise your bootloader would have been locked, and then you can't flash.
[Nexus 6 Q&A, Help & Troubleshooting] akaiinuku:
So its back to stock now. All i had to do was manually flash. Thank you istperson for your help.
[Nexus 6 Q&A, Help & Troubleshooting] Nick_92:
Does anyone solved the problem with the bootloader locked and no custom recovery? I've tried everything and still my nexus 6 doesn't work. I don't know what else to do
[Nexus 6 Q&A, Help & Troubleshooting] istperson:
I know it's very hard to accept, but if you lost your Android OS while Allow OEM unlocking was off, there's not more you can do, it has to go for repair.
[Nexus 6 Q&A, Help & Troubleshooting] afaruky:
I deperately need the very same thing for Nexus 6P. I have working TWRP but locked bootloader. I forgot to enable oem unlocking and tried to flash the stock rom. It failed and got stuck in Google screen. All I can do is entering twrp. Please help :crying:
[Nexus 6 Q&A, Help & Troubleshooting] osm0sis:
Just updated my Nexus BootUnlocker Script zip in my Odds and Ends thread.

I had an incorrect offset for N9 oembit support, due to originally using the information from this post, but I just redid it with the offset from the dumps in the OPs, and it's the same as the N6 (of course)!

shamu)
ui_print "Nexus 6: $device";
block=/dev/block/platform/msm_sdcc.1/by-name/frp;
offset=524287;
locked=00;
unlocked=01;
flounder*)
ui_print "Nexus 9: $device";
block=/dev/block/platform/sdhci-tegra.3/by-name/PST;
offset=524287;
locked=00;
unlocked=01;

If anyone wants me to take another shot at N6, or N9 proper bootloader unlock, or at least N5X or N6P bootloader unlock/oembit toggling, we need more dumps over in the BootUnlocker Dev thread. Please volunteer. Thanks!
[Nexus 6 Q&A, Help & Troubleshooting] sankarsh16:
Please help

Can I use the above steps whole iam having stock recovery
[Nexus 6 Q&A, Help & Troubleshooting] philcolbourn:
Nexus 6. OS started crashing after a time period. This time period reduced to point where I would get 'Google' and a few animated balls.

Device was stock and locked.

I unlocked device with fastboot oem unlock.

I downloaded 6.01 factory image shamu-mob30m.

I ran (as root) ./flash-all.sh

I got en error on system.img:

"failed to allocate 2098202380 bytes

error: update package missing system.img"

At this point, I could still get into recovery through fastboot. I don't recall exactly what I did in recovery - prob. erased data and cache.

I tired to manually install system.img, boot.img, recovery.img and cache.img using fastboot flash X X.img

They all seemed to work. But nexus 6 would not boot.

I then did fastboot oem lock and got this:

(bootloader) Check 'Allow OEM Unlock' in Developer Options before

(bootloader) locking.

(bootloader) This allows a recovery method if further flashing is needed

(bootloader) later.

FAILED (remote failure)

finished. total time: 0.005s

Fastboot still says it is unlocked status code 3, but device behaves as if it is locked.

fastboot getvar all reports

(bootloader) unlocked: yes

(bootloader) securestate: unlocked

recovery does not work. android does not boot.

I seem to have an unlocked brick!
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
update to the very latest fastboot to get flash-all to work, or flash each partition separately. and you didnt use root to flash anything via fastboot in your bootloader, lol.
[Nexus 6 Q&A, Help & Troubleshooting] philcolbourn:
Hmm. Perhaps I don't understand your reply - Apart from not using latest fastboot, I have flashed each partition manually (as I mentioned, these all seemed to work) and I was using fastboot as root - it does not work otherwise.

Were you suggesting I do something else?
[Nexus 6 Q&A, Help & Troubleshooting] philcolbourn:
I gave up with this mainboard, and put in another one.

This was a working Nexus 6, locked, that had a damaged screen module.

Symptoms were almost identical. Initially it performed a wipe, but then it behaved the same.

I then decided to swap batteries - it booted normally!

Now that I had a working phone, I have not investigated further.
[Nexus 6 Q&A, Help & Troubleshooting] Rob2016015:
Hi,

I would like to ask help before I sink deeper and deeper in the mess with my Nexus 9 Wifi tablet while I try to fix it.

In some sentences the story. I had constant problem with Skype and Android 7.0, so decided to downgrade Android 7.0 to 6.1. This with a short intermezzo was successful. Skype worked fine, but my girlfriend was moaning about the calm voice, I decided to install Cyanogenmod Android. It was even successful... To protect my new operating system, - I was such an idiot- I locked the bootloader back and after this new Android never started, but got into a boot loop.

Power button-> Google logo-> red text stating "this is a development device not intended for public use".

Fantastic... the way to the hell is build from ideas of making things better...

Status where I am:

- fastboot/adb are working, but when I try to run "fastboot oem unlock" it fails.

- If I boot into recovery mode, I can login "Team Win Recovery Project 3.0.2-0" with "Install, Wipe, Backup,Restore, Mount, Settings, Advanced, Reboot" options.

The log says:

"Data successfully decrypted, new block device: '/dev/block/dm-0'

Updating partition details...

...done

Unable to mount storage

Successfully decrypted with default password.

Updating partition details...

...done

Unable to mount storage

Failed to mount '/data' (Invalid argument)

Full SELinux support is present.

Unable to mount /data/media/TWRP/.twrps

MTP Enabled

Failed to mount '/data' (Invalid argument)

Failed to mount '/data' (Invalid argument)

Failed to mount '/data' (Invalid argument)

Repairing Data using e2fsck...

/sbin/e2fsck -fp /dev/block/dm-0 process ended with ERROR: 8

Unable to repair Data.

When I select storage :

Internal Storage (0MB)

USB Storage (0MB)

Select Partitions to Mount:

Vendor OK

System OK

Data - can not select

Cache OK

USB Storage - can not select

When I open a terminal in the TWRP and run mount

I see /cache, /vendor, /system mounted, but not /data.

Somehow when I locked back the bootloader (HBOOT-3.43.0.0114) I disabled the access to /data partition and Android can not reach the files in /data/media/TWRP/.twrps and fails during boot.

Size in the backup menu (however I can not backup as Internal storage is 0MB and USB storage 0MB too):

Boot 32MB, Vendor (123MB), Vendor image (256MB), System (921MB), System image (2654MB), Data (11316MB), Cache (0MB)

Can I fix this with Playahate's & Osm0's solution (dd or the script)?

Looking forward your reply.

Thanks,

Rob
[Nexus 6 Q&A, Help & Troubleshooting] efrant:
Yes, you should be able to fix it. As long as you can boot into TWRP, you have root, so it should work. Then once you toggle that, unlock the bootloader and flash the stock images.
[Nexus 6 Q&A, Help & Troubleshooting] Rob2016015:
feedback

Hi,

I take my hat off to You, Guys, special thanks to Playahate and Osm0 to dig out the solution.

My Nexus tablet has been recovered, everything went smoothly after the dd.

I will never lock back the bootloader, even with stock rom, it was a lessons learnt for a life.

I owe You, Guys! :highfive: Fantantic, thanks!

Cheers,

Rob
[Nexus 6 Q&A, Help & Troubleshooting] Serdar79us:
I think I made the same mistake and the screen went away. I need the file (mmcblk0p18) immediately. :(
[Nexus 6 Q&A, Help & Troubleshooting] runekock:
Note the post from @osm0sis just below the one you quoted: you can't just flash a partition from another phone.

Now, tell us some more about your situation. Is anything still working? If yes, there may be other solutions.

Edit: sorry, I guess osm0sis was talking about partitions from different phone models.

But still, I think you should explore other options before this kind of partition flashing.
[HTC Vox] motin:
gd mrng all

can any one help me to restore the long press on the number 1 on the keybaord so when i press it then ill ring the voice mail number

it used to work and 1 morning it stopped and i cant get it to work again.

thanks and nice day.
[HTC Vox] Robomann:
What is happning when you continue to press 1, dos the phone not ask for a number ?
[HTC Vox] motin:
htc - s710

nope it does not but i already hard reset the dam thing all ok now

thanks
[One (M7) Q&A, Help & Troubleshooting] lchan51:
It is pulling up and I want to know if there is any chance I can reattach it? It is the side where the front camera is located. It doesn't appear that it is held down with any screw like on the other side. Any suggestions other than taking it all apart and replace with new?
[XDA Assist] Mr Corn:
Does anyone have a copy of the nookonfire kernel ver 2.4 or 3.22 by demetris. I think it might

help or solve a wonky battery problem in a nook tablet. Hours of searching and no results.

Thanks
[XDA Assist] jd1639:
Hi, thank you for using XDA Assist. Is this what you're looking for? http://xdaforums.com/showthread.php?t=2225686
[XDA Assist] Mr Corn:
Yep! that's it. All the links are dead and Goo.im is gone.
[XDA Assist] jd1639:
Then I can't help you. You might try shooting Demetris a PM and seeing if he has a copy.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Nylo:
I can no longer push my bluetooth earpiece and voice dial. I can dial through the phone and all works well.

What's happened? I used to be able to do this with no problems.

KK 444

Stock Att root S4
[Xperia Z1 General] Ratha ITC:
:eek: New 14.5.A.0.283 Was Certified :eek:

Screenshots

[IMG="Screenshots"]http://s29.postimg.org/8fohsf6zr/Photo_Grid_1432150959706.jpg[/IMG]

[Z1] Stock Lollipop 5.0.2 - 14.5.A.0.270

C6902: Customized SG 1277-2654 R1D

C6903: Customized SG 1276-7937 R2D

C6903: Central Europe Customized CE3 (Go to post #2)

SuperSU v2.46

XZDualRecovery v2.8.15 (Pre-installed)​

I. Requirements:

1. Locked or Unlocked Bootloader

2. Rooted Stock Lollipop or KITKAT (Easy way to root your latest KITKAT)

3. Working Flashtool (For method 1 only)​

II. Installation:

" It is a must to follow all the steps. Please kindly spend your time read it. :p "​

" And don't forget to vote for your favorite method! :laugh: "​

Method 1: "The PC Needed" (Recommended)

Method 2: "The Single Flashable"

III. Files:

C6902

C6903

Note:

All files are based on original ftf(s) that are generated by Flashtool (files from Sony PC Companion & XperiFirm).​

IV. Q&A:

Q 1 : Root Checker says this ROM is rooted, but Titanium Backup can't get root access?

A : Update your Titanium Backup to the latest version.

Q 2 : I've got bootloop with Xposed Framework?

A : Don't be panic! It works fine on this ROM. Flash the C690X_Flashable_14.5.A.0.270_SG_*.zip again and use the latest version of Xposed.

Q 2 : I have other questions?

A : Go to Q&A.

​
[Xperia Z1 General] Ratha ITC:
"The Single Flashable 270 for C6903 Central Europe Customized CE3"

SuperSU & XZDualRecoveryy Included

Credit to [MENTION=2989384]Dadovvv[/MENTION]

Download Here!

Installation: Method 2

Check His Original Post & Thank to Him Here!

​
[Xperia Z1 General] angvil:
I'm wondering what is the difference between your method flashing from recovery then flashing from pc and just flashing a zip in Recovery without the need of a PC?

Can you also provide the flashable zip only method? Anyway thanks a lot for your hard work I'm on 242 because of your tutorial
[Xperia Z1 General] Ratha ITC:
Hi [MENTION=5763288]angvil[/MENTION] ! I've already made a single c6903 flashable without PC needed, but I need someone test it :o I will upload as soon as I get home.

Note: One disadvantage of Single flashable is that it won't re-manage partition. I'm not sure... maybe :p
[Xperia Z1 General] Vatron11:
C6903

I've installed on rooted kitkat but the device was turned on. re-started itself continuously.
[Xperia Z1 General] Ratha ITC:
Tell me more details.
[Xperia Z1 General] angvil:
Hi,

I am now downloading the zip file for flashing from recovery only. I'll give you feedback once flashed.
[Xperia Z1 General] anakdayak:
Hi OP tnx for the latest 270 pre root.Been using your rom u created since the 242,Am now flashing the 270 without any issue.Its running for nearly half a day.Everthing seems to work fine.Once again tnx.Keep up the gd work.
[Xperia Z1 General] M7ammad:
xposed

[MENTION=5191250]Ratha ITC[/MENTION]

Did you try the new xposed update Alpha4 with this rom?
[Xperia Z1 General] Ratha ITC:
Thanks in advance! :D

Thanks for your feedback! I'm glad to hear that. :D

I don't need Xposed so I haven't tried it yet.. By the way, there's no single problem for my previous 242. :)
[Xperia Z1 General] Ratha ITC:
Poll Added

Please vote to share which method you use to install... :)
[Xperia Z1 General] mgh1982:
If you could add sony mini lock app , it would be great. Thanks for wonderful rom. :o:good:

---------- Post added at 05:55 AM ---------- Previous post was at 05:54 AM ----------

The second one without ftf I used, and there was no issue. :good:
[Xperia Z1 General] benlenspace:
successfully flashed using method 2 without problem... my concern now is a deodexed rom for .270
[Xperia Z1 General] Ratha ITC:
I've never use that app... what is Sony Lock app? :o

And thanks for your feedback and voting. :)
[Xperia Z1 General] Ratha ITC:
Thanks for your feedback! For deodexed, I haven't thought about it yet... :o but I think there might be someone here already making any MOD to transform to deodexed. :)
[Xperia Z1 General] Giozer:
Hello.

I'm in Italy and I have a Xperia Z1 6903, with KK, rooted with newroot and CWM Recovery v.6.0.4.7 (installed by newroot) and with some modules Xposed; Locked bootloader.

Can I use your prerooted ROM?

Your ROM works well in Italy?

After installation, I still find my recovery or installing a new recovery from your zip file?

In your ROM it is preinstalled Xposed?

What method do you recommend? To me it seems easier (with fewer steps) the second method.

Thank you.
[Xperia Z1 General] Ratha ITC:
I'm not sure with your CWM... but I think it's fine to install my pre-rooted.

My ROMs work for all C6902 or C6903. No pre-installed xposed. XZDualRecovery v2.8.15 added, and you don't need to flash any recovery.

I recommend method 1 but also method 2 if you find method 1 complicated. If you choose method 2, I recommend full wipe because you upgrade from Kitkat.
[Xperia Z1 General] cashflow67:
Deodex is a choice, but I want to ask you how to debloat your zip? Because I dont use almosy any sony and google apps except for album, walkman, google play store and google play services. Can you help me?

And one more question. In your method 2, can I wipe system,data,cache, dalvik cache and internal storage? Because while I am installing roms, I want to make mega clean wipe
[Xperia Z1 General] mgh1982:
It's for locking using administration, like screen off and lock in play store. We can replace middle button long press which brings up google search with this app to lock the lock screen without using the power button. :highfive: "ST lite rom" has it . In your rom I used JB LockNow of play store instead, cause I myself couldn't find the sony one. :cool::eek:
[Xperia Z1 General] Dadovvv:
To OP, Here is flashable .zip Official C6903 Central Europe Customized CE3 14.5.A.0.270 R1D.zip with SU and NUT dualrecovery included.

It is tested and works without any problem, so if u want u can add link to OP, there is so many thread on this Z1 section opened for every single branding, so it would be nice to have one thread dedicated to all prerooted firmwares.

https://drive.google.com/file/d/0B3011Q50-bjWWEpYdURDQlpXTkU/view?usp=sharing
[Xperia Z1 General] angvil:
Add promised posting my feedback on this update.

I flashed the flashable zip from recovery but before that I wiped cache and dalvik only so it's a dirty one but the rom looks stable and everything working add promised.

Did Sony fix the low sound issue? I can't really notice it anyway I installed the z3 stereo mod.

They fixed the screen not sleeping directly when phone call and proximity sensor were delaying and I always found the phone in the notifications slower pulled down.