Database Develop

[Security breach?] Your data is NOT SAFE! Simple bypass of data wipe when unlocking

I've always been a bit startled by how the bootloader bootloader is unlocked on my nexus 4. After pushing the unlock command to my device and choosing "yes", the bootloader is unlocked right away. The data isn't wiped before I reboot into the system, while on the nexus 7 the bootloader is not unlocked before after the wipe.
Yesterday i re-locked, rebooted and unlocked my device again as an experiment. I then proceeded to boot a custom recovery without rebooting into the system. I suceded, and was able to boot into TWRP without the bootloader wiping my data. I could then proceed to adb pull/push watever i wished from the data partition or any other partition without the data having been wiped. What? I thought my data was secure after re-locking my bootloader, but it appears it isn't.
If this applies to all nexus 4 devices, I was also able to reboot into the system after wiping cace from TWRP. This means you can oem unlock and root without without my data being wiped simply by booting a custom recovery right after unlocking.
If this applies to all nexus 4 devices, our data is not safe. This means that even normal users with locked bootloaders can have their data stolen easy as pie. We need more confirmations on this issue to confirm it. If you are willing to try, just follow the instructions below. Please report if it works or if it doesn't. WARNING! Do this at your own risk! I'm not responsible if your data is wiped, etc. Please perform a full nandroid or adb backup and copy it to a safe place before performing the following seps:
1. If you're unlocked, re-lock your bootloader and reboot into fastboot:
Code:
fastboot oem lock
fastboot reboot-bootloader
2. Unlock your bootloader:
Code:
fastboot oem unlock
3. There's no need to reboot into bootloader after performing the previous step. It makes no difference. Just do not reboot into the system.
4. Flash or boot a custom recovery:
Code:
fastboot flash recovery custom_recovery.img
OR
Code:
fastboot boot custom_recovery.img
5. Now you're in custom recovery if all goes as expected. Root by flashing SuperSU/whatever or pull data with adb or do some serious damage! :good:
6. If you want to reboot back into your system without loosing data, you'll have to wipe cache in custom recovery. This prevents the bootloader from rebooting back into the stock recovery (if you didn't overwrite it) and wipe your phone. If you flashed a custom recovery and you're stuck in a bootloop or something, this applies to you too.
And again: Please report back if it worked or if it didn't! Good luck! :^)
Edit: This wasn't all my idea. Found out about the last cache wipe step here.

fiskenigaten said:
I've always been a bit startled by how the bootloader bootloader is unlocked on my nexus 4. After pushing the unlock command to my device and choosing "yes", the bootloader is unlocked right away. The data isn't wiped before I reboot into the system, while on the nexus 7 the bootloader is not unlocked before after the wipe.
Yesterday i re-locked, rebooted and unlocked my device again as an experiment. I then proceeded to boot a custom recovery without rebooting into the system. I suceded, and was able to boot into TWRP without the bootloader wiping my data. I could then proceed to adb pull/push watever i wished from the data partition or any other partition without the data having been wiped. What? I thought my data was secure after re-locking my bootloader, but no!
I was also able to reboot into the system after wiping cace from TWRP. This means I can oem unlock and root without without my data being wiped simply by booting a custom recovery right after unlocking.
I want to find out if this applies to all other makos on all bootloaders. If you are willing to try, this is what I did. Please report if it works or if it doesn't. WARNING! Do this at your own risk! I'm not responsible if your data is wiped. Please perform a full nandroid backup and copy it to a safe place before performing the following seps:
1. If you're unlocked, re-lock your bootloader and reboot into fastboot:
Code:
fastboot oem lock
fastboot reboot-bootloader
2. Unlock your bootloader:
Code:
fastboot oem unlock
3. There's no need to reboot into bootloader after performing the previous step. It makes no difference. Just do not reboot into the system.
4. Flash or boot a custom recovery:
Code:
fastboot flash recovery custom_recovery.img
OR
Code:
fastboot boot custom_recovery.img
5. Now you're in custom recovery if all goes as expected. Root by flashing SuperSU/whatever or pull data with adb or do some serious damage! :good:
6. If you want to reboot back into your system without loosing data, you'll have to wipe cache in custom recovery. For some reason this keeps the stock recovery from wiping the phone. If you flashed a custom recovery and you're stuck in a bootloop or something, this applies to you too.
And again: Please report back if it worked or if it didn't! Good luck! :^)
Edit: This wasn't all my idea. Found out about the last cache wipe step here.
Click to expand...
Click to collapse
The upside is, the person who steals or finds your phone is most likely not a developer, an android nerd, or has ever heard of XDA to gain this information.

Semantics said:
The upside is, the person who steals or finds your phone is most likely not a developer, an android nerd, or has ever heard of XDA to gain this information.
Click to expand...
Click to collapse
/deleted I have no idea what I'm talking

Not up for experimenting, but it reminded me of my experience on the N4.
-initial BL unlock via the standard method = data wiped,
-upon relocking, and then unlocking the BL again = no data wipe (same method as above)
Can't recall if the behaviour was the same on my GN.

CMNein said:
Not up for experimenting, but it reminded me of my experience on the N4.
-initial BL unlock via the standard method = data wiped,
-upon relocking, and then unlocking the BL again = no data wipe (same method as above)
Can't recall if the behaviour was the same on my GN.
Click to expand...
Click to collapse
My data is allways wiped after bootloader unlock, but it is only wiped upon reboot. It was like that the first time as well.

I can almost (95%) confirm this, because the first time I unlock my Nexus 4, I fastboot flash cwm directly, and boot into recovery, to flash PA and wipe cache and data. Everything in my sdcard was intact and I was also confused like you did.
Maybe if I ever wanted to full wipe again I will give it a try...

ksilver89 said:
I can almost (95%) confirm this, because the first time I unlock my Nexus 4, I fastboot flash cwm directly, and boot into recovery, to flash PA and wipe cache and data. Everything in my sdcard was intact and I was also confused like you did.
Maybe if I ever wanted to full wipe again I will give it a try...
Click to expand...
Click to collapse
Excactly! This is really careless by Google. It means NO nexus 4 without encryption is safe! I want my data to be safe!

I don't get it. I thought even Samsung's phones you can do that? Just just go flash cf root then yeah done? Are they even trying to protect the data in your internal memory data from getting stolen?

fiskenigaten said:
My data is allways wiped after bootloader unlock, but it is only wiped upon reboot. It was like that the first time as well.
Click to expand...
Click to collapse
Sorry, I should have clarified I was referring to the virtual sdcard side of it.

Yup this is the exact reason I opened a thread about compatibility issues with encryption and CWM recovery. We have to encrypt our phones if we want to secure our data. What are the options once we go the 3rd party recovery route is another question.
http://forum.xda-developers.com/showthread.php?p=41257911
Sent from my Nexus 4 using Tapatalk 2

Excactly! This is really careless by Google. It means NO nexus 4 without encryption is safe! I want my data to be safe!
Click to expand...
Click to collapse
Guess it's time to encrypt your device then...
Seriously, bugs and exploits are going to happen. This is software written by humans, after all.
If you are serious about data security on your device, you would have already encrypted by now.

Can confirm easily. I relocked my boot loader with my phone at its current state. (CMRC1 + Bricked Kernel). Then proceeded to unlock, rebooted boot loader, booted into recovery, wipe cache, data intact
Sent from my Nexus 4 using xda premium

Well if someone steals your phone they most likely don't give a **** about your data (unless there's bank info on it) they probably just wanna resell it for an easy 3-400$
Sent from my Nexus 4 @1.72 GHz on Stock 4.2.2

To be honest if you want your bank info safe never put it on a device that is easily lost or stolen or transmits the info over the air.
Wayne Tech Nexus

Guys, honest question. If someone were to grab your data but you encrypted it via the settings menu, does that mean they can still decipher your contents? For example, the TSA is known to get your electronic items and copy the data for their "Security protocol." Would this allow them to copy the data but not decipher it?
Sent from my Nexus 4

nexicon said:
Guys, honest question. If someone were to grab your data but you encrypted it via the settings menu, does that mean they can still decipher your contents? For example, the TSA is known to get your electronic items and copy the data for their "Security protocol." Would this allow them to copy the data but not decipher it?
Sent from my Nexus 4
Click to expand...
Click to collapse
If the TSA got ahold of your device they would be able to decrypt it easily enough. No amount of encryption would prevent that.

zelendel said:
If the TSA got ahold of your device they would be able to decrypt it easily enough. No amount of encryption would prevent that.
Click to expand...
Click to collapse
Nothing in this country is safe and private anymore. Sigh..
Sent from my Nexus 4

nexicon said:
Nothing in this country is safe and private anymore. Sigh..
Sent from my Nexus 4
Click to expand...
Click to collapse
Not really. The only way to beat Gov hackers is to be a better hacker.

zelendel said:
Not really. The only way to beat Gov hackers is to be a better hacker.
Click to expand...
Click to collapse
Easy for you to say
Sent from my Nexus 4

nexicon said:
Easy for you to say
Sent from my Nexus 4
Click to expand...
Click to collapse
No not really man. Not sure what Country your in but it is most likely not very different here.

SOLUTION those stuck in a bootloop with locked bootloader & TWRP

Hi All
Got into a bit of a situation when I re-locked my bootloader and got stuck in a loop, unable to unlock it because of the developer settings option. I had nothing but the TWRP screen bootlooping.
Anyway, sorted it out for those who want to know how. In the bootloader run the commands "fastboot format cache" and "fastboot format userdata"
Then choose to boot into recovery, it'll work and you'll be in TWRP. From there you can flash a ROM, enable the setting in developer options & unlock the bootloader!
Credit goes to geologic in this thread here: http://forum.xda-developers.com/nexus-9/help/warning-locking-bootloader-disabling-t2951312/page5

Good news to anyone having alternative recovery. Unfortunately will not work with stock recovery

Great thanks
Sorry for my poor english (I'm french). Great thanks for your solution. It works fine for me... I was afraid during a few hours to be forced to throw away my Nexus 6....

Thank you for that information. I was in the same position and your instructions helped me get my device working again. That Check 'Allow OEM Unlock' in Developer Options flag is a real game changer for those of us who are used to flashing our devices and one must be very careful.

freeman_g said:
Good news to anyone having alternative recovery. Unfortunately will not work with stock recovery
Click to expand...
Click to collapse
Shouldn't you be able to adb side load a stock ROM?

Thank You
ixa20 said:
Hi All
Got into a bit of a situation when I re-locked my bootloader and got stuck in a loop, unable to unlock it because of the developer settings option. I had nothing but the TWRP screen bootlooping.
Anyway, sorted it out for those who want to know how. In the bootloader run the commands "fastboot format cache" and "fastboot format userdata"
Then choose to boot into recovery, it'll work and you'll be in TWRP. From there you can flash a ROM, enable the setting in developer options & unlock the bootloader!
Credit goes to geologic in this thread here: http://forum.xda-developers.com/nexus-9/help/warning-locking-bootloader-disabling-t2951312/page5
Click to expand...
Click to collapse
Thank You so much you saved my day , I thought their is no solution for this but you saved me. :good::laugh::laugh:

Thanks a million!!
ixa20 said:
Hi All
Got into a bit of a situation when I re-locked my bootloader and got stuck in a loop, unable to unlock it because of the developer settings option. I had nothing but the TWRP screen bootlooping.
Anyway, sorted it out for those who want to know how. In the bootloader run the commands "fastboot format cache" and "fastboot format userdata"
Then choose to boot into recovery, it'll work and you'll be in TWRP. From there you can flash a ROM, enable the setting in developer options & unlock the bootloader!
Credit goes to geologic in this thread here: http://forum.xda-developers.com/nexus-9/help/warning-locking-bootloader-disabling-t2951312/page5
Click to expand...
Click to collapse
Thank you so much, I owe you a life debt. haha now i can take one step closer to freedom.

How can you use fastboot format cache and fastboot format userdata when the bootloader is locked? I'm on an N6, but I've had 0 luck with that.

mrkmrk said:
How can you use fastboot format cache and fastboot format userdata when the bootloader is locked? I'm on an N6, but I've had 0 luck with that.
Click to expand...
Click to collapse
You just can. It allows it.

Just went through the same thing and can confirm that fastboot format cache and fastboot format userdata got me back into recovery.
However, Recovery was showing 0MB storage space so I couldn't push anything to the SDcard for install. @rootSU recommended that I go into wipe and perform a full format (the one that requires you to type "yes"). I did this and my storage was back to normal and I was able to push a ROM to the SD card and flash it.
Problem solved!

sn0warmy said:
Just went through the same thing and can confirm that fastboot format cache and fastboot format userdata got me back into recovery.
However, Recovery was showing 0MB storage space so I couldn't push anything to the SDcard for install. @supersu recommended that I go into wipe and perform a full format (the one that requires you to type "yes"). I did this and my storage was back to normal and I was able to push a ROM to the SD card and flash it.
Problem solved!
Click to expand...
Click to collapse
That's nice to give credit to the guy that helped you. But it was @rootSU

cam30era said:
That's nice to give credit to the guy that helped you. But it was @rootSU
Click to expand...
Click to collapse
Haha whoops! Thanks!

sn0warmy said:
Haha whoops! Thanks!
Click to expand...
Click to collapse
Know how I know?
Because I did it too.

cam30era said:
Know how I know?
Because I did it too.
Click to expand...
Click to collapse
There are too many "SU" screen names to keep track of. Either that, or my brain is fried from all the trouble shooting this morning.

sn0warmy said:
There are too many "SU" screen names to keep track of. Either that, or my brain is fried from all the trouble shooting this morning.
Click to expand...
Click to collapse
Maybe I need name change.

rootSU said:
Maybe I need name change.
Click to expand...
Click to collapse
ACE!

Htc butterfly s 9060 bootloop
ixa20 said:
Hi All
Got into a bit of a situation when I re-locked my bootloader and got stuck in a loop, unable to unlock it because of the developer settings option. I had nothing but the TWRP screen bootlooping.
Anyway, sorted it out for those who want to know how. In the bootloader run the commands "fastboot format cache" and "fastboot format userdata"
Then choose to boot into recovery, it'll work and you'll be in TWRP. From there you can flash a ROM, enable the setting in developer options & unlock the bootloader!
Credit goes to geologic in this thread here: http://forum.xda-developers.com/nexus-9/help/warning-locking-bootloader-disabling-t2951312/page5
Click to expand...
Click to collapse
my phone is bootlooping and locked bootloader and not have twrp recovery....xda is very big site for android development after that no buddy help m... so plz help i m crying now..

abby1996 said:
my phone is bootlooping and locked bootloader and not have twrp recovery....xda is very big site for android development after that no buddy help m... so plz help i m crying now..
Click to expand...
Click to collapse
You can try >
fastboot format cache
fastboot format userdata
Note that if this works, it will wipe your SDcard.
If it doesn't work, you have no other options. Return it for repair or replacement.

Thank you soo much for reply
cam30era said:
You can try >
fastboot format cache
fastboot format userdata
Note that if this works, it will wipe your SDcard.
If it doesn't work, you have no other options. Return it for repair or replacement.
Click to expand...
Click to collapse
yes, this commnd works but what i do after that please tell ..i m new ....but i have recovery.zip and boot.img .i find these from other threats...how i flash this in locked bootloader..please tell in brief. Thanks

abby1996 said:
yes, this commnd works but what i do after that please tell ..i m new ....but i have recovery.zip and boot.img .i find these from other threats...how i flash this in locked bootloader..please tell in brief. Thanks
Click to expand...
Click to collapse
fastboot reboot

[Q] Bricked Nexus 6 PLEASE HELP!!

Trying to sell my Nexus 6 I believe I bricked it. After rooting the device I used Chainfire 3d program and it made me stuck on google sign. I tried literally everything. I can boot into teamwin TWR recovery. I tried factory resetting wiping cache and delvic. Problem is my bootloader is coming up locked. Tried using fastboot many times to flash everything back keep getting remote failure. Need help, is it possible im just screwed at this point. Ive used about everything it is just stuck saying Google. PLEASE HELP!!!!

chainfires 3d program hasnt worked on a nexus in years. and you do need to boot back up to enable unlocking the bootloader in the developer options. have you tried wiping data in twrp recovery?

zacrivera24 said:
Trying to sell my Nexus 6 I believe I bricked it. After rooting the device I used Chainfire 3d program and it made me stuck on google sign. I tried literally everything. I can boot into teamwin TWR recovery. I tried factory resetting wiping cache and delvic. Problem is my bootloader is coming up locked. Tried using fastboot many times to flash everything back keep getting remote failure. Need help, is it possible im just screwed at this point. Ive used about everything it is just stuck saying Google. PLEASE HELP!!!!
Click to expand...
Click to collapse
Relax, deep breath. You need to use fastboot from bootloader. Issue these commands:
fastboot format cache
fastboot format userdata
That should get you into TWRP and from there you can transfer a ROM to internal, flash it and go from there.

Evolution_Freak said:
Relax, deep breath. You need to use fastboot from bootloader. Issue these commands:
fastboot format cache
fastboot format userdata
That should get you into TWRP and from there you can transfer a ROM to internal, flash it and go from there.
Click to expand...
Click to collapse
well, he wrote that he can boot into twrp recovery already. wiping data should fix his use of chainfires app. but flashing a new rom would do the same

simms22 said:
well, he wrote that he can boot into twrp recovery already. wiping data should fix his use of chainfires app. but flashing a new rom would do the same
Click to expand...
Click to collapse
Yeah, guess I missed that part.

Evolution_Freak said:
Yeah, guess I missed that part.
Click to expand...
Click to collapse
thinking about it now.. with the bootloader locked, would twrp let you flash anything?

simms22 said:
thinking about it now.. with the bootloader locked, would twrp let you flash anything?
Click to expand...
Click to collapse
Yes, it has been done to fix the soft brick I thought we were dealing with here. Only if TWRP is installed though.

Doesn't chainfire 3d modify system? I though it did. May need to flash a rom zip after a factory reset.

rootSU said:
Doesn't chainfire 3d modify system? I though it did. May need to flash a rom zip after a factory reset.
Click to expand...
Click to collapse
honestly, i dont remember. its been about 3-4 years since last thinking of that app. if it does, a rom flash would be needed.

[Q] Possibly bricked N6, bootloop, no recovery, locked bootloader . Help me

Hello guys,
This is possibly the first ever phone I have bricked. Since I moved from Chroma to Euphoria my Nexus 6 was reporting 23GB of total available storage, that's 3GB less than what I was getting with Chroma.
So I decided to revert back to stock hoping that would have sorted the partition layout but found myself in a bootloop. I tried several factory versions with no go, bootloop was still persisting. At that point I was like I am going to relock the bootloader to see if that makes any difference, and when I realized it did not and I tried to unlock it again, from that point on I realized I was very much screwed.
The current situation. I flashed a 5.0.1 factory stock that is in bootloop, bootloader is locked, no access to the stock recovery.
I have made a ton of researches and it seems I will have to send the device on repair.
Any idea of what else I could possibly try to rescue this phone?
How's that there's not a way to force unlocking the bootloader from fastboot when the system is not in a operational state?
I will appreciate any help.
Thanks

Segnale007 said:
Hello guys,
This is possibly the first ever phone I have bricked. Since I moved from Chroma to Euphoria my Nexus 6 was reporting 23GB of total available storage, that's 3GB less than what I was getting with Chroma.
So I decided to revert back to stock hoping that would have sorted the partition layout but found myself in a bootloop. I tried several factory versions with no go, bootloop was still persisting. At that point I was like I am going to relock the bootloader to see if that makes any difference, and when I realized it did not and I tried to unlock it again, from that point on I realized I was very much screwed.
The current situation. I flashed a 5.0.1 factory stock that is in bootloop, bootloader is locked, no access to the stock recovery.
I have made a ton of researches and it seems I will have to send the device on repair.
Any idea of what else I could possibly try to rescue this phone?
How's that there's not a way to force unlocking the bootloader from fastboot when the system is not in a operational state?
I will appreciate any help.
Thanks
Click to expand...
Click to collapse
Do you have TWRP or stock recovery?

cam30era said:
Do you have TWRP or stock recovery?
Click to expand...
Click to collapse
Nope I do not. I don't even have access to the stock recovery. For some reason when I select the stock recovery the recovery menu does not appear. It just comes up a dead android with a question mark and nothing else..

Segnale007 said:
Nope I do not. I don't even have access to the stock recovery.
Click to expand...
Click to collapse
I'm sorry to tell you that the only thing you can do is return it for repair/replacement. FWIW: if you had left the bootloader unlocked, we could have helped you.

cam30era said:
I'm sorry to tell you that the only thing you can do is return it for repair/replacement. FWIW: if you had left the bootloader unlocked, we could have helped you.
Click to expand...
Click to collapse
I kinda knew it.. This Nexus 6 was bought outside of the Play Store. Will Motorola either replace it or repair it?
I am just gonna say I woke up in the morning and found the phone in bootloop..

Segnale007 said:
I kinda knew it.. This Nexus 6 was bought outside of the Play Store. Will Motorola either replace it or repair it?
I am just gonna say I woke up in the morning and found the phone in bootloop..
Click to expand...
Click to collapse
You have nothing to loose by contacting them and asking.

What 5.0.1 factory stock file did you flash?

Mega Montana said:
What 5.0.1 factory stock file did you flash?
Click to expand...
Click to collapse
This one right here https://dl.google.com/dl/android/aosp/shamu-lrx22c-factory-ff173fc6.tgz

Flashing that file following the correct steps should not have sent the phone in a bootloop. Gonna need a bit more info to know what got screwed up. Also, have you connected your phone to your PC to see if it recognizes it? You said you can't boot into recovery but what about the bootloader, power + vol down?

Mega Montana said:
Flashing that file following the correct steps should not have sent the phone in a bootloop. Gonna need a bit more info to know what got screwed up. Also, have you connected your phone to your PC to see if it recognizes it? You said you can't boot into recovery but what about the bootloader, power + vol down?
Click to expand...
Click to collapse
Depends if he had a 5.1 bootloader before or not. Attempts to downgrade the BL from 5.1 will result in a loop.
If it appears when connecting to the PC as qhsusb mode, then it's fixable. If it appears normally as a fastboot device, then it needs repairing.

Guys after 6 hours of nightmare I am glad to say it all ended up in a big scare.
Here is how I managed to get around the bootloop and get android to boot up.. http://forum.xda-developers.com/showpost.php?p=61079544&postcount=312
Thanks for the help

Segnale007 said:
Guys after 6 hours of nightmare I am glad to say it all ended up in a big scare.
Here is how I managed to get around the bootloop and get android to boot up.. http://forum.xda-developers.com/showpost.php?p=61079544&postcount=312
Thanks for the help
Click to expand...
Click to collapse
How did you do that with a locked bootloader?

cam30era said:
How did you do that with a locked bootloader?
Click to expand...
Click to collapse
I have reason to believe that the procedure outlined in the link I posted did not help me. What rather helped me must have been that I flashed userdata an cache from 5.1.1 factory stock to the 5.0.1 factory stock I had bootlooping.
I just felt to mention that I followed that procedure, but I bet its not what managed to help me booting back in android.

Segnale007 said:
I have reason to believe that the procedure outlined in the link I posted did not help me. What rather helped me must have been that I flashed userdata an cache from 5.1.1 factory stock to the 5.0.1 factory stock I had bootlooping.
I just felt to mention that I followed that procedure, but I bet its not what managed to help me booting back in android.
Click to expand...
Click to collapse
Well, I'm glad for you. But I still don't understand how you could flash anything with a locked bootloader.

cam30era said:
Well, I'm glad for you. But I still don't understand how you could flash anything with a locked bootloader.
Click to expand...
Click to collapse
Maybe he had the downgrade "brick" as i suggested a page back. Only way I know to flash when locked.
Or maybe the format part of a flash fixed itm

rootSU said:
Maybe he had the downgrade "brick" as i suggested a page back. Only way I know to flash when locked.
Or maybe the format part of a flash fixed itm
Click to expand...
Click to collapse
Aahh. That makes sense. I'm still amazed that recovery was this easy.

cam30era said:
Well, I'm glad for you. But I still don't understand how you could flash anything with a locked bootloader.
Click to expand...
Click to collapse
rootSU said:
Maybe he had the downgrade "brick" as i suggested a page back. Only way I know to flash when locked.
Or maybe the format part of a flash fixed itm
Click to expand...
Click to collapse
I am not sure whether I had a softbrick or a downgrade brick, all I know is that with a locked bootloader I was able to format and flash only cache and userdata, and btw while googling I have also found other people in the same situation as the one I have been that were also able to format and flash userdata and cache partitions with a locked bootloader.
I am just surprised to see the phone booting with a userdata and cache files from a newer version of android. That's what probably saved my butt.

Segnale007 said:
I am not sure whether I had a softbrick or a downgrade brick, all I know is that with a locked bootloader I was able to format and flash only cache and userdata, and btw while googling I have also found other people in the same situation as the one I have been that were also able to format and flash userdata and cache partitions with a locked bootloader.
Btw I was surprised to see the phone booting with a userdata and cache files from a newer version of android.
Click to expand...
Click to collapse
Most of those who were able to successfully format cache and userdata still had TWRP installed. You are very lucky. Should buy a lotto ticket today.

Segnale007 said:
I am not sure whether I had a softbrick or a downgrade brick, all I know is that with a locked bootloader I was able to format and flash only cache and userdata, and btw while googling I have also found other people in the same situation as the one I have been that were also able to format and flash userdata and cache partitions with a locked bootloader.
I am just surprised to see the phone booting with a userdata and cache files from a newer version of android. That's what probably saved my butt.
Click to expand...
Click to collapse
You can format cache and userdata with a locked bootloader. You cannot flash cache or userdata with a locked bootloader... Unless your bootloader is "bricked" as per the thread you linked to ultimately.
FYI formatting has the exact same result as flashing userdata and cache. So the options are:
1) you formatted which fixed it
2) you were bootloader bricked and had to use a gpt.bin to fix it.

How to move to new Stock partition?

I need to understand how to update to the new Stock merged partition. Have been reading general advice in various threads that we need to flash new China developer rom. Can someone elaborate regarding how to do this and where to get this rom? Do we need to re-root? Do we need to reflash recovery?
I see that many new MM roms are using this new Stock partition like Matoxxi's newest RR rom. So want to know. Detailed help is highly appreciated... Thanks...

+1
I too would like to see a proper procedure..

This is what I personally did. Was on extended partition. With TWRP as recovery.
1) Flash the cwm r11( or any working cwm) recovery. Needed to flash the repartition zip!! Don't use TWRP. Did this once and had a dead phone. Reboot to recovery. You'll be on CWM.
2) Flash the back to stock partition zip. Choose the one with "el pierro verde" in it.
3) Flash TWRP recovery. Boot to recovery.
4) Flash the 5/12/17 miui zip. This is the ROM which merges the partitions. At this point the partitions are not merged yet!
4.1) Boot the phone up. Reboot to recovery
5) Repeat step 4. Now the partitions are merged.
6) Flash any ROM that you desire.
Of you are on stock partition with TWRP skip steps 1-3.
Good luck.

If you are on MIUI ROM, install 5.12.17 first to merge partitions and then 6.2.4 via Updater app. Xiaomi.eu version is tuned for europe/outside china, Google Apps are included in rom.
https://www.androidfilehost.com/?fid=24369303960690691
https://www.androidfilehost.com/?fid=24415232478676696
Or you can just MiFlash 6.2.4 chinese developer rom factory image from en.miui.com.

Thanks for the details. I did try this out, am on original stock partition... Flashed 5.12.17, two times as per step 4. Rebooted but the partition remains resolute at old stock and does not merge. Am using twrp 2.8.7. Tried this twice, no success... Need advice... Thanks

The only quick way to setup the new partition for now is to fastboot flash the Chinese Dev ROM, as you yourself already stated. You can flash it by fastboot flashing it using Mi PCSuite and choosing the Beta ROM.
On my experience, after the flash I got my bootloader locked ("fastboot oem device-info" resulted in Device unlocked = false), but I can simply unlock it through fastboot without any problem.
From that point, you can easily flash any custom ROM.
Or even MIUI V6, with manual, per partition fastboot flash rather than using MiFlash/Mi PCSuite because of different partition layout; V6 and lower got two boot, modem and system partitions for TDB, while the new has only one.

anshude1 said:
Thanks for the details. I did try this out, am on original stock partition... Flashed 5.12.17, two times as per step 4. Rebooted but the partition remains resolute at old stock and does not merge. Am using twrp 2.8.7. Tried this twice, no success... Need advice... Thanks
Click to expand...
Click to collapse
Can you boot the phone after the first flashing? Than reboot to recovery and try step 4 again.

Have a look to
http://en.miui.com/thread-209941-1-1.html
there you can find a zip (cancro_merge_partition(2).zip) and the guideline how to use. For me it worked fine.
It does the repartitioning through fastboot by executing 1 shell script. Afterwards you might want to update your recovery rom to an English version.

anshude1 said:
Thanks for the details. I did try this out, am on original stock partition... Flashed 5.12.17, two times as per step 4. Rebooted but the partition remains resolute at old stock and does not merge. Am using twrp 2.8.7. Tried this twice, no success... Need advice... Thanks
Click to expand...
Click to collapse
Im using Pallmali method to flash, however 1st i try to repeat flash on step 4, it didnt work, then i download MIUI china dev 6.2.4 and flash, wait for a while and it is updated to MIUI 7 MM with merged partition.

anshude1 said:
Thanks for the details. I did try this out, am on original stock partition... Flashed 5.12.17, two times as per step 4. Rebooted but the partition remains resolute at old stock and does not merge. Am using twrp 2.8.7. Tried this twice, no success... Need advice... Thanks
Click to expand...
Click to collapse
I believe you have to use default Mi Recovery. One time flash of 5.12.17 was enough on my Mi4.

ksloh1 said:
Im using Pallmali method to flash, however 1st i try to repeat flash on step 4, it didnt work, then i download MIUI china dev 6.2.4 and flash, wait for a while and it is updated to MIUI 7 MM with merged partition.
Click to expand...
Click to collapse
It got auto updated? So did you flash stock recovery? Or used twrp

I downloaded 6.2.4 into my phone and then choose the file to update from miui itself, and it will reboot to twrp recovery and install. After fully install and reboot. Only then it will have merged partition and MM miui. And back to stock recovery automatically.

I just fastboot 6.2.4 rom successfully... Now will flash twrp...
And made my first big mistake going in for 6.2.4 beta... It has locked bootloader and a load of Chinese **** you can't make sense of and have to forcefully bear it. Please can anyone help me to unlock the bootloader without begging to the ****ty miui folks?

anshude1 said:
I just fastboot 6.2.4 rom successfully... Now will flash twrp...
And made my first big mistake going in for 6.2.4 beta... It has locked bootloader and a load of Chinese **** you can't make sense of and have to forcefully bear it. Please can anyone help me to unlock the bootloader without begging to the ****ty miui folks?
Click to expand...
Click to collapse
First of all, if you planned to stay on MIUI MM, you don't have any options than requesting an unlock permission to Xiaomi.
If you just want the merged partition and prepared to flash any custom ROM or MIUI V6, enter fastboot then send this command:
Code:
fastboot oem unlock
The reason is that when you unlocks the bootloader through fastboot, it automatically wipes out your phone. IDK why, but possibly inherent to Android's design for security reasons.

rxl.noir said:
First of all, if you planned to stay on MIUI MM, you don't have any options than requesting an unlock permission to Xiaomi.
If you just want the merged partition and prepared to flash any custom ROM or MIUI V6, enter fastboot then send this command:
Code:
fastboot oem unlock
The reason is that when you unlocks the bootloader through fastboot, it automatically wipes out your phone. IDK why, but possibly inherent to Android's design for security reasons.
Click to expand...
Click to collapse
I tried this out, the phone got all wiped but the OEM unlocking button does not work still. So how would I know if the bootloader is unlocked?

anshude1 said:
I tried this out, the phone got all wiped but the OEM unlocking button does not work still. So how would I know if the bootloader is unlocked?
Click to expand...
Click to collapse
OEM Unlocking button? You meant on the Developer Options? That button is currently useless with no function at all. If you want to ascertain if your bootloader is unlocked or not, try sending
Code:
fastboot oem device-info
via fastboot. If the "Device unlocked" comes out as true, then your bootloader is already unlocked.
Ooooor just try to flash any custom recovery/ROM. If it works, then your bootloader is already unlocked.

rxl.noir said:
OEM Unlocking button? You meant on the Developer Options? That button is currently useless with no function at all. If you want to ascertain if your bootloader is unlocked or not, try sending
Code:
fastboot oem device-info
via fastboot. If the "Device unlocked" comes out as true, then your bootloader is already unlocked.
Ooooor just try to flash any custom recovery/ROM. If it works, then your bootloader is already unlocked.
Click to expand...
Click to collapse
Great, big thanks to you... It worked. Device unlocked is True
Funnily it also quoted device tampered is True :laugh:

anshude1 said:
Great, big thanks to you... It worked. Device unlocked is True
Funnily it also quoted device tampered is True :laugh:
Click to expand...
Click to collapse
Yeah, it might be set to true once you had flashed another unsigned image to the eMMC (or when you disconnect the battery, IDK), probably for the warranty checks :q.

knoxwalles said:
Have a look to
http://en.miui.com/thread-209941-1-1.html
there you can find a zip (cancro_merge_partition(2).zip) and the guideline how to use. For me it worked fine.
It does the repartitioning through fastboot by executing 1 shell script. Afterwards you might want to update your recovery rom to an English version.
Click to expand...
Click to collapse
Worked for me
Thank you very much.