Database Info

soft brick plus phone not recognised by adb

--------------------------------------------------------------------------------
M new to android. Bought this HTC one s T-Mobile which is rooted and runs cm10 and and android 4.1.2. I have updated it to 10-20121012-nightly-villw in d hope that the WiFi tethering would work. Well it never did. But that is not my prob right now.
I tried a hard reset from bootloader screen and now it says safe to remove SD card. I installed SDK ADT bundle. But the command 'ADT devices ' returns blank. Does not recognise my phone. I downloaded all in one kit and also installed htc drivers given on the same post. Even all in one kit does not recognise my phone. Says device not found. M running vista home premium. I have followed all d steps like putting d phone in debug mode. M I missing something. Pl help. M really stuck now.

sadrulez said:
--------------------------------------------------------------------------------
M new to android. Bought this HTC one s T-Mobile which is rooted and runs cm10 and and android 4.1.2. I have updated it to 10-20121012-nightly-villw in d hope that the WiFi tethering would work. Well it never did. But that is not my prob right now.
I tried a hard reset from bootloader screen and now it says safe to remove SD card. I installed SDK ADT bundle. But the command 'ADT devices ' returns blank. Does not recognise my phone. I downloaded all in one kit and also installed htc drivers given on the same post. Even all in one kit does not recognise my phone. Says device not found. M running vista home premium. I have followed all d steps like putting d phone in debug mode. M I missing something. Pl help. M really stuck now.
Click to expand...
Click to collapse
Does QHSUSB_DLOAD appear in device manager?

I looked up d device manager could not find anything like this. Anywhere specific I need to look at ?

sadrulez said:
--------------------------------------------------------------------------------
M new to android. Bought this HTC one s T-Mobile which is rooted and runs cm10 and and android 4.1.2. I have updated it to 10-20121012-nightly-villw in d hope that the WiFi tethering would work. Well it never did. But that is not my prob right now.
I tried a hard reset from bootloader screen and now it says safe to remove SD card. I installed SDK ADT bundle. But the command 'ADT devices ' returns blank. Does not recognise my phone. I downloaded all in one kit and also installed htc drivers given on the same post. Even all in one kit does not recognise my phone. Says device not found. M running vista home premium. I have followed all d steps like putting d phone in debug mode. M I missing something. Pl help. M really stuck now.
Click to expand...
Click to collapse
Your description is confusing to me. Your thread title says it is softbricked but then you say that you put the phone in debug mode? Does your rom boot fully?
Are you trying to toolkit from the Rom, bootloader or fastboot?

If you typed adt devices it won't show anything lol
Sent from my HTC VLE_U using xda app-developers app

Spastic909 said:
If you typed adt devices it won't show anything lol
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Sorry I meant adb devices. I thought the SD card error means soft brick. Sorry for my ignorance. M able to boot and use my phone. Just that sd card won't work and I am not able to connect to adb or all in one kit to fix my issue. I tried connecting after normal boot and from recovery mode and even from boot loader screen. No luck with either of them.

I had an issue with softbricking my phone. A good last resort is to flash the RUU (thats what i was told to do and it worked like a charm). It will totally reset your phone to factory settings...and you will need to re-lock your bootloader (just use the All-In-One Toolkit) but besides that, you will once again have a working phone and can just re-root it. If you need the RUU file I can supply the link to it with a little bit of searching. Good Luck!

sadrulez said:
Sorry I meant adb devices. I thought the SD card error means soft brick. Sorry for my ignorance. M able to boot and use my phone. Just that sd card won't work and I am not able to connect to adb or all in one kit to fix my issue. I tried connecting after normal boot and from recovery mode and even from boot loader screen. No luck with either of them.
Click to expand...
Click to collapse
Everyone's so ready to have a guy run a RUU. Even if he did that it he still would be stuck.
If the toolkit isn't working then you have done something wrong.
Check in device manager and look if you see a category that says "android usb devices"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If it's not there you don't have the driver installed correctly. If it is there, double check that you have developer options enabled. In the develop options menu check for something that say enable android debugging.
While you phone is booted normally, plug it into your computer. Can you see something in the notification area that says something about debugging mode?
If you got all that done is the toolkit still not working?

I recommend using a Windows 7 PC to install HTC Sync, then copying the folder to your computer. Then install the drivers manually through device manager, selecting the previous folder that you copied. The drivers should detect your phone then.
@dc211 I can't believe your still using XP lol
Sent from my HTC One S using Tapatalk 2

I connected my phone to a Windows 7 computer and it recognised my phone.
I downloaded All-in-One.
I did not know what is flashing stock recovery. So here is what I did :
I flashed CWM 5.8.3.1(S4).
Then i booted in bootloader and did 'clear storage'. then i did wipe data/factory reset
then i reflashed CWM 5.8.3.1(s4)
Now my phone goes directly into cwm recovery screen automatically.
My SD card still does not mount.
when i try to get into bootloader using All-in-one kit it keeps saying 'waiting for device' on the computer screen and the phone reboots and goes back to CWM recovery screen.
As you are aware there is no removable battery in this phone. I am stuck now. If I hold down the power and Vol down button for as long as one minute nothing happens. Phone eventually comes back to CWM recovery screen.
I tried everything possible from CWM recovery screen. Wiped cache/dalmik cache. Format system/data. Cant format SD card it says unable to mount.
Please HELP !!

sadrulez said:
I connected my phone to a Windows 7 computer and it recognised my phone.
I downloaded All-in-One.
I did not know what is flashing stock recovery. So here is what I did :
I flashed CWM 5.8.3.1(S4).
Then i booted in bootloader and did 'clear storage'. then i did wipe data/factory reset
then i reflashed CWM 5.8.3.1(s4)
Now my phone goes directly into cwm recovery screen automatically.
My SD card still does not mount.
when i try to get into bootloader using All-in-one kit it keeps saying 'waiting for device' on the computer screen and the phone reboots and goes back to CWM recovery screen.
As you are aware there is no removable battery in this phone. I am stuck now. If I hold down the power and Vol down button for as long as one minute nothing happens. Phone eventually comes back to CWM recovery screen.
I tried everything possible from CWM recovery screen. Wiped cache/dalmik cache. Format system/data. Cant format SD card it says unable to mount.
Please HELP !!
Click to expand...
Click to collapse
Try holding volume down and power. Out should boot into the bootloader.
Sent from my HTC One S using Tapatalk 2

I already tried that. Holding vol button down + power button restarts the phone in CWM recovery mode

i tried it least 20 times and was finally able to get the phone to boot to bootloader mode
can you guide me to the next set of steps ..
I am totally relying on this forum at the moment.

sadrulez said:
i tried it least 20 times and was finally able to get the phone to boot to bootloader mode
can you guide me to the next set of steps ..
I am totally relying on this forum at the moment.
Click to expand...
Click to collapse
Run an RUU, whichever suits your CID /bootloader version.
Sent from my HTC One S using Tapatalk 2

[Q] PLz Help Google logo Stuck

My nexus s m200 ( Korean) phone is stuck with google logo . i was talking on a call when phone hung. I tried to restart it but none of the buttons (Power, Up and Down) worked. so i pulled of my battery reinserted and there it was the horrible google logo sign. I tried every thing i tried to recover by going into recovery but recovery failed then i format wipe user data/ sd card but it didn't resolve my issue i even wiped the cache files as well.....
The Bootloader is locked i have tried everything but it just doesn't unlock... i cannot root from sd card because i have no access on it. i gave it to couple of repairmen but they also failed to understand the issue..........??
I cannot root from any software because the bootloader is locked... i even tried in command by typing "fastboot oem unlock" it does give caution the screen but it when i accept it.. it simply says unlock failed..........??????
i even use Nexus Root Toolkit v.1.6.1 . after unlocking when it reboots the cell phone it again hang up on the google logo. and again i have to pull out the battery inorder to go to bootloader menu... and then it is again locked.. kit has also failed to unlock and resolve my issue...
PLz Helpppppp
What SHould I do...........?? Plz can anyone poit me in the right direction.
Plz help its my first time that i hav bought anything this expensive out of my own hard earned moneu :crying:

Faizan.Waheed said:
My nexus s m200 ( Korean) phone is stuck with google logo . i was talking on a call when phone hung. I tried to restart it but none of the buttons (Power, Up and Down) worked. so i pulled of my battery reinserted and there it was the horrible google logo sign. I tried every thing i tried to recover by going into recovery but recovery failed then i format wipe user data/ sd card but it didn't resolve my issue i even wiped the cache files as well.....
The Bootloader is locked i have tried everything but it just doesn't unlock... i cannot root from sd card because i have no access on it. i gave it to couple of repairmen but they also failed to understand the issue..........??
I cannot root from any software because the bootloader is locked... i even tried in command by typing "fastboot oem unlock" it does give caution the screen but it when i accept it.. it simply says unlock failed..........??????
i even use Nexus Root Toolkit v.1.6.1 . after unlocking when it reboots the cell phone it again hang up on the google logo. and again i have to pull out the battery inorder to go to bootloader menu... and then it is again locked.. kit has also failed to unlock and resolve my issue...
PLz Helpppppp
What SHould I do...........?? Plz can anyone poit me in the right direction.
Plz help its my first time that i hav bought anything this expensive out of my own hard earned moneu :crying:
Click to expand...
Click to collapse
First off, CALM DOWN. The fact that you can see the google logo means your phone isn't dead.
Second, do not pull off the battery when you're stuck. Use Nexus root toolkit if you want to do a reboot. Go to Advanced Utilities, Click "Launch", then click Reboot, Reboot Bootloader, or Reboot Recovery.
Make sure you installed the correct drivers for your specific phone model (m200).
Try using the toolkit and set-up your phone correctly. Use PdaNet drivers. Then try to unlock the bootloader again.

Plz Help
ej8989 said:
First off, CALM DOWN. The fact that you can see the google logo means your phone isn't dead.
Second, do not pull off the battery when you're stuck. Use Nexus root toolkit if you want to do a reboot. Go to Advanced Utilities, Click "Launch", then click Reboot, Reboot Bootloader, or Reboot Recovery.
Make sure you installed the correct drivers for your specific phone model (m200).
Try using the toolkit and set-up your phone correctly. Use PdaNet drivers. Then try to unlock the bootloader again.
Click to expand...
Click to collapse
Yes i did install the PdaNet Drivers and then unlocked it that but still it is somehow locked... The thing is that when i simply turn on phone it stucks with the google logo on it. Then any command that i may type is just ineffective.. Command windows says "Device searching" but if i start the phone in bootloader menu then computer recognizes the device.....?? i just cant figure out what to do.......I have been trying to sort this issue since last monday but all in vein...
So any solution that might entertain this problem

Go to bootloader, flash a custom recovery, then flash a new rom.

ej8989 said:
Go to bootloader, flash a custom recovery, then flash a new rom.
Click to expand...
Click to collapse
Thank you so very much for your concerned and valuable advices.... i Really appreciate it but
PLz can u direct me through some instructions that how to flash a custom recovery and then flash a new room...? What soft wares i will be needing and wht will the procedure........??

amydacus3 said:
Central and elegant location.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Didn't get you bro.....??

Soft Bricked Verizon HTC One M8

I have a Verizon HTC One M8 that can still power on, but will only go to the black screen with an HTC logo in the center and a triangle with an exclamation mark in each of the four corners. This happened while returning my phone to stock. My computer disconnected from the phone half-way through pushing an RUU flash. The cable wasn't unplugged, the computer just made the disconnect sound and the flash stopped. The phone is not recognized as an adb device, but it is recognized as a fastboot device. This gives me some hope that the phone can be recovered, but any attempt to flash an RUU gives me the error: cannot load "file-name". Any suggestions?
Just to help out anybody trying to figure this out:
The phone will not enter recovery
The phone enters something akin to the recovery page if I disconnect it from the PC, but the only option is RUU and pressing the power button will not do anything (picture attached)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Once you see the triangle you hold volume up then tap power. Try rebooting your PC, pushing that file takes some ram and a reboot will fix it, also try using the adb and fastboot files from dottats s-on ruu thread. Its in the first post i believe and modify your commands to look like this "HTC_fastboot oem rebootRUU" (without the quotes) ect.........itll help the ram issue. Thanks @dottat for showing me this. Try that and report back.

MotoTurbo said:
Once you see the triangle you hold volume up then tap power. Try rebooting your PC, pushing that file takes some ram and a reboot will fix it, also try using the adb and fastboot files from dottats s-on ruu thread. Its in the first post i believe and modify your commands to look like this "HTC_fastboot oem rebootRUU" (without the quotes) ect.........itll help the ram issue. Thanks @dottat for showing me this. Try that and report back.
Click to expand...
Click to collapse
Interesting, I didn't even know there was a version of adb specifically for HTC phones, though, I actually did this to my phone before that thread was ever made (never got around to trying to fix it until now). I'm at work right now, but I'll try it when I get home and update, thanks for the tip!

curb42 said:
Interesting, I didn't even know there was a version of adb specifically for HTC phones, though, I actually did this to my phone before that thread was ever made (never got around to trying to fix it until now). I'm at work right now, but I'll try it when I get home and update, thanks for the tip!
Click to expand...
Click to collapse
And if you run into any issues hit me up... i can help you out remotely.

dottat said:
And if you run into any issues hit me up... i can help you out remotely.
Click to expand...
Click to collapse
Just got home and ran the RUU with the HTC fastboot and it worked! At least I'm assuming so, I'm at the Verizon splash screen right now. Thanks so much for your help guys (and to HTC)!
Funnily enough, the soft brick worked out for me. If I hadn't bricked it I would have sold it months ago. I'm on a Droid Turbo now and I think I like the M8 better. So thanks again and I'll update if for whatever reason it's still messed up.

curb42 said:
Just got home and ran the RUU with the HTC fastboot and it worked! At least I'm assuming so, I'm at the Verizon splash screen right now. Thanks so much for your help guys (and to HTC)!
Funnily enough, the soft brick worked out for me. If I hadn't bricked it I would have sold it months ago. I'm on a Droid Turbo now and I think I like the M8 better. So thanks again and I'll update if for whatever reason it's still messed up.
Click to expand...
Click to collapse
Awesome man, glad you got it working. Also you can try a factory reset after ruu if you've flashed a bunch of Roms and have iffy data

Idol 3- Stuck In Bootloop After Flashing boot.img

Idol 3 Bootloop
I need your assistance
Hi, I have read through all of the posts and tried to find a solution with no luck.
I tend to always go one step too far with my hacking and playing/experimenting.
Alcatel One Touch Idol 3 5.5 6045K
It was booting into TWRP fine.
Then I wrote the non-functioning boot.img (which I thought was the backup of my pre-rooting version) on top of the working twrp recovery image.
So instead of installing the boot.img to the boot partition, I installed it to the recovery partition by mistake.
So now...
My phone just keeps booting and booting.
Alcatel Screen appears
The SuperSU installer starts
runs through its steps
Done!
Cleaning Up....
Will reboot in 10 seconds....
And starts all over again.
adb does not find any devices anymore
I am wondering if it possible at all to format the external sd card so that the phone will boot directly from there.
I have one single ray of hope ( maybe ) . The phone will boot into download mode. (Power off, hole power, volume up and volume down to activate)
The challenge I have now is the USB driver that was working now does not recognize the phone.
I have tried fastboot and I have also tried the OnDemand script. No luck.
I read that the download mode is used for flashing firmware and roms (most likely by the manufacturer)
Has anyone been able to install a rom using the download method successfully?
I am on Windows 10 All-in-One PC
Thanks in advance for any assistance you can provide.
N101BL

More Info
No ideas anyone?
Here is some more info. Hopefully it helps.
So this is what my screen looks like when the phone is turned on. I can only turn it off if it is not plugged in to usb or power.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is the Download Mode. (Power off - then hold power button, volume up, and volume down. Let go when splash screen starts)
Download mode makes a connection sound on my PC so I know something is being recognized.
The phone stops bootloop and waits for something?
This is what appears in Devices and Printers Windows
These are the USB Properties for the USB Driver.
I am thinking that maybe there is a secret usb driver that Telus uses or Alcatel uses to push the firmware or rom onto the phone. Not just the default Alcatel usb driver. (not sure)
Even if I could somehow push a ne SuperSu.zip or my original backup files, everything would be good.
Any ideas would be amazing. I know the trials and tribulations of working with a new product. Hopefully you experts can decode this one.
Thank you.
N101BL (Kevin)

CAN YOU GO TO RECOVER YMODE? turn off your phone, hold power and volupe up together, release after the phone vibrates...you should go to recovery mode.

No Recovery Mode
DallasCZ said:
CAN YOU GO TO RECOVER YMODE? turn off your phone, hold power and volupe up together, release after the phone vibrates...you should go to recovery mode.
Click to expand...
Click to collapse
Sadly no. That would be too easy. I occidentally wrote the not working boot image over top of the working recovery image. (Yes I know, I am an idiot. I knew I was doing it at the time, but I hit reboot anyway. That's when the loop started.)

You need a bunch of files in order to flash anything while the device is in download mode. Search in baidu for 'tct msm8939 qpst'. You will find info (and the necessary files) for m3g. The device has identical hardware as 6045, but I don't know where the similarities end. Your device can become completely unusable when you play with these tools (QPST, QFIL etc.), but I'm sure that you are aware of this. Good luck.

what about off warranty repair by alcatel service in your country?

N101BL said:
Sadly no. That would be too easy. I occidentally wrote the not working boot image over top of the working recovery image. (Yes I know, I am an idiot. I knew I was doing it at the time, but I hit reboot anyway. That's when the loop started.)
Click to expand...
Click to collapse
The loop you described doesn't sound like it has anything to do with recovery...you described what happens when you FLASH the boot.img used to root the device instead of just booting it. This will result in the infinate loops. The recovery partition is not used at all until you actually try to go in it by holding down up arrow while it's booting...I would try this several times to ensure you can't get into recovery because if you can get there you can restore your device. If you can not, then it's a paperweight and you should send it off for replacement because it doesn't look like any way to flash it using "download mode" is going to come out anytime soon.
---------- Post added at 08:22 AM ---------- Previous post was at 08:20 AM ----------
petrov.0 said:
You need a bunch of files in order to flash anything while the device is in download mode. Search in baidu for 'tct msm8939 qpst'. You will find info (and the necessary files) for m3g. The device has identical hardware as 6045, but I don't know where the similarities end. Your device can become completely unusable when you play with these tools (QPST, QFIL etc.), but I'm sure that you are aware of this. Good luck.
Click to expand...
Click to collapse
Perhaps the chinese version of the idol 3 that was just released will lead to access to some of the config files we need.

famewolf said:
Perhaps the chinese version of the idol 3 that was just released will lead to access to some of the config files we need.
Click to expand...
Click to collapse
Probably but the files must be released in the wild first. I do searches in baidu from time time in case that something interesting pops up. I also must to admit that the translation of these sites is awful in most cases

Update
Well I sent my phone back.. Fortunately it was under warranty!
But now another hopefully minor issue with the replacement phone.
Please see this thread and post if you know what I am missing. I really appreciate your time and efforts!
http://forum.xda-developers.com/idol-3/help/valid-backup-file-t3199797
famewolf said:
The loop you described doesn't sound like it has anything to do with recovery...you described what happens when you FLASH the boot.img used to root the device instead of just booting it. This will result in the infinate loops. The recovery partition is not used at all until you actually try to go in it by holding down up arrow while it's booting...I would try this several times to ensure you can't get into recovery because if you can get there you can restore your device. If you can not, then it's a paperweight and you should send it off for replacement because it doesn't look like any way to flash it using "download mode" is going to come out anytime soon.
---------- Post added at 08:22 AM ---------- Previous post was at 08:20 AM ----------
Perhaps the chinese version of the idol 3 that was just released will lead to access to some of the config files we need.
Click to expand...
Click to collapse

Unlocked bootloader, super easy. Need confirmation.

This is what I get after running simple oem unlock command via adb
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can it be unlocked now?
I was running on 7.0.4.0 Stable - stock out of box, just rooted straight from 3rd party dealer.

Just to update, now I just disconeccted the device from PC and it cant boot. But it worked 4-5 times before, as I was checking bootloader status after few reboots.
PC sees it as QHSUSB_BULK. It's a hardbrick. Any advices?

From what you've done there, nothing should've changed on the device. It was already unlocked, it comes unlocked out of the box.
What else did you do and what do you mean when you say it can't boot? What happens when you hold the power button for a few seconds? Can you still boot into the bootloader (pwr vol -) or the recovery (pwr vol +)?
It's not a hard brick as long as you can still run fastboot, which should work seeing as that's all you've done.
If it's just the PC not recognizing you could try rebooting, clearing adb and device drivers (you can show hidden hardware in the devices management to find your drivers) and reinstalling them.

Logic_ said:
From what you've done there, nothing should've changed on the device. It was already unlocked, it comes unlocked out of the box.
What else did you do and what do you mean when you say it can't boot? What happens when you hold the power button for a few seconds? Can you still boot into the bootloader (pwr vol -) or the recovery (pwr vol +)?
It's not a hard brick as long as you can still run fastboot, which should work seeing as that's all you've done.
If it's just the PC not recognizing you could try rebooting, clearing adb and device drivers (you can show hidden hardware in the devices management to find your drivers) and reinstalling them.
Click to expand...
Click to collapse
UPDATE:
Flashed 7.1.6.0 Stable.
Lost root.
All data and apps present.
Got Chinese apps now.
Google services not working.
It didn't react to whatever I did. Just now I tried holding vol - & power buttons for a minute or two and I got into fastboot. Just reflashed image via miflash and waiting to boot. I see Mi logo and a progress bar loading.
Will report on the outcome.

voolandis said:
It didn't react to whatever I did. Just now I tried holding vol - & power buttons for a minute or two and I got into fastboot. Just reflashed image via miflash and waiting to boot. I see Mi logo and a progress bar loading.
Will report on the outcome.
Click to expand...
Click to collapse
you are doing right but beware 6.xx latest developer rom, it will lock your bootloader and stock recovery again .

voolandis said:
UPDATE:
Flashed 7.1.6.0 Stable.
Lost root.
All data and apps present.
Got Chinese apps now.
Google services not working.
Click to expand...
Click to collapse
Yes, the stable does not have root. You can choose where to go from here, if you want to push the files for root and gapps yourself, or go with a new ROM entirely.
In any case what is most advisable right now is flashing a custom recovery (TWRP) so you have much more control and a bit of extra safety to know that you can more easily recover if you bootloop.

Logic_ said:
Yes, the stable does not have root. You can choose where to go from here, if you want to push the files for root and gapps yourself, or go with a new ROM entirely.
In any case what is most advisable right now is flashing a custom recovery (TWRP) so you have much more control and a bit of extra safety to know that you can more easily recover if you bootloop.
Click to expand...
Click to collapse
Fixed Play Services by complete removal and fresh install from MIUI store.
Is there any way I can actually check if my bootloader is locked or not?
Will flashing TWRP (if BL is locked) lead to brick, or will it simply fail and phone will work?

You checked if your bootloader was unlocked in the first post, that's what
Code:
(bootloader) Device unlocked: true
means.
Only flashing the official dev builds (for now) will lock your bootloader. The version you installed should not have locked it.
A locked bootloader will make flashing TWRP impossible. So just be sure to stay away from those official dev ROM.

Logic_ said:
You checked if your bootloader was unlocked in the first post, that's what
Code:
(bootloader) Device unlocked: true
means.
Only flashing the official dev builds (for now) will lock your bootloader. The version you installed should not have locked it.
A locked bootloader will make flashing TWRP impossible. So just be sure to stay away from those official dev ROM.
Click to expand...
Click to collapse
All good. Flashed TWRP (it's got that no response bug every time it boots), rooted.
Will go for sMIUI now.