Database Users

Yotaphone 2 YD206 in Bootloop after update

Hello,
i have a problem with my 1 week old yotaphone and hope you guys can help me to solve.
Let me say, this is my first android device. After a long time using iphones i saw this 2-displays concept and wanted to give it a try.
But now my problem and the way to:
The phone was brand new and first of all i charged it for a wohle night.
After that i put in the sim-card and started the phone and walked through the start-procedure with WLAN, Googleaccount etc.
Then the phone told me about an update and i started it over WLAN.
The phone was downloading, rebooting and shows me a white window "updating x of 127(?) Apps".
Somewhere in the middel the phone rebooted again and now its in a bootloop.
What is possible with the phone right now.
I can start the phone wit the bootloop (powerred byAndroid, then restart)
I can use "Power + Vol-" to bring it into downloading mode
When i use "Power + Vol+" nothing happend.
When i use "Vol+ + Vol-" nothing happend.
The akku of the phone is empty now and it only works with usb or power unit connected.
In bootloop or downloading mode it is not charging.
What i tried.
What i try:
I read many topics with bricked / bootlooped yotphones and how to flash or cache whipping.
i connected the phone to my pc and used yotoflasher with many different firmwares.
I used fastboot:
- flashed the system.ing with differnet sizes.
- tried different custom recovery.img from different threads here and from other sites.
Even a complete new image, moddified RU img doesn`t help.
The phone stays in bootloop.
Yes, it`s a warranty case, but before i start to strech my nerves by handling with the dealer and shipping
this phone back to china i will try everything else and hope you can help me out of this situation.
Thanks a lot

easyxx said:
Hello,
i have a problem with my 1 week old yotaphone and hope you guys can help me to solve.
Let me say, this is my first android device. After a long time using iphones i saw this 2-displays concept and wanted to give it a try.
But now my problem and the way to:
The phone was brand new and first of all i charged it for a wohle night.
After that i put in the sim-card and started the phone and walked through the start-procedure with WLAN, Googleaccount etc.
Then the phone told me about an update and i started it over WLAN.
The phone was downloading, rebooting and shows me a white window "updating x of 127(?) Apps".
Somewhere in the middel the phone rebooted again and now its in a bootloop.
What is possible with the phone right now.
I can start the phone wit the bootloop (powerred byAndroid, then restart)
I can use "Power + Vol-" to bring it into downloading mode
When i use "Power + Vol+" nothing happend.
When i use "Vol+ + Vol-" nothing happend.
The akku of the phone is empty now and it only works with usb or power unit connected.
In bootloop or downloading mode it is not charging.
What i tried.
What i try:
I read many topics with bricked / bootlooped yotphones and how to flash or cache whipping.
i connected the phone to my pc and used yotoflasher with many different firmwares.
I used fastboot:
- flashed the system.ing with differnet sizes.
- tried different custom recovery.img from different threads here and from other sites.
Even a complete new image, moddified RU img doesn`t help.
The phone stays in bootloop.
Yes, it`s a warranty case, but before i start to strech my nerves by handling with the dealer and shipping
this phone back to china i will try everything else and hope you can help me out of this situation.
Thanks a lot
Click to expand...
Click to collapse
Mine too,stuck in bootloop. I also tried the fastboot and it said waiting device.

kophyo07 said:
Mine too,stuck in bootloop. I also tried the fastboot and it said waiting device.
Click to expand...
Click to collapse
If your phone displays Downloading... and fastboot keeps saying waiting for device then there is something wrong with the installed ADB driver. Check some of the posts in this forum like this one on how to fix this. http://forum.xda-developers.com/yotaphone-one/help/yotaphone-2-yd-206-china-flash-firmware-t3306797/post69311402#post69311402

Strange that you had an OTA (Over The Air update). You didn't do anything between the SIM/Google registration and OTA ?
Normally there are no OTAs allowed on yd206 phones bought from China/HK , where did you buy it ? Chinese retailers have their own firmware that they put on phones , for me , maybe you had bad firmware installed.
The warranty of your phone is voided if you flash yotaphones bought from China and HK .
When you use yotaflasher do you get error message or "waiting for device" ?
To flash the Yotaphone , it should be in developer mode , but you couldn't put it in this mode because it first did the OTA that started your bootloop. Android apps are updated like that ("installing x of 127") when it gets updated to lollipop. Normally the OTA should have worked OK. Did you allow enough time at the Yotaphone logo after the first reboot ? It stays on this logo for 5 minutes before starting. I made this mistake.
The OTA started just after you set up Google etc ?
If so, normal yotaflashing will never work, but at least you havent broken the warranty . The thing we need to know is what exactly happened when you tried to flash , what errors messages appeared ?
If you did not put the phone in developer mode, then you cannot easily flash the phone, so your best possibility is to return the phone. Normally you can contact the seller by chat or email . Some are very good in exchanging.
It IS possible to flash your phone using fastboot, but I would not personally attempt it and you would lose your warranty . You need rootkits, SDK toolkits, universal drivers and images. Google "bootloop without USB debugging".
When I flashed my yd206 , (after many attempts) I flashed my yd206 to yd201 Russian KitKat ROM first and then did an OTA to lollipop.

Bricked or screen is broken?

Hello, I have redmi 3s 32GB , I have had developer rom and last friday as a many of you my phone was not able to be used, so I tried to flash global stable rom via fastmode commands, but phone was bricked, so I removed back cover and reset pins,of course reconnnected battery, after this phone was detected in win10 and I have installed global stable rom, pc now detect phone as redmi 3s, I saw my internal sdcard...but screen is still blank, I cannot see recovery boot, fastboot and no logo too. Could you help me? Is screen broken or is this software problem?
Regards

undulus said:
Hello, I have redmi 3s 32GB , I have had developer rom and last friday as a many of you my phone was not able to be used, so I tried to flash global stable rom via fastmode commands, but phone was bricked, so I removed back cover and reset pins,of course reconnnected battery, after this phone was detected in win10 and I have installed global stable rom, pc now detect phone as redmi 3s, I saw my internal sdcard...but screen is still blank, I cannot see recovery boot, fastboot and no logo too. Could you help me? Is screen broken or is this software problem?
Regards
Click to expand...
Click to collapse
Hi, open ur phone again and check the display connector, try fully disconnecting it and reconnecting it and check if all other connectors in range are also properly connected. Then reassemble ur phone.
Next time, do not open your phone unless you really have to. I don't see why you have opened to reset it. You can press power for very long then after maybe 30 seconds or so, your phone will fully turn off. No need to open it for that.
Next time if you have a question, use the Q&A section, not this one. You'll get answers quicker there too.

Bricked or screen is broken
Without disassembling I was not able to detect my phone, after pin reseting phone was identified in windows. No recovery boot was working too... This is reason why I disassembled phone...
But thank you for reply..

undulus said:
Without disassembling I was not able to detect my phone, after pin reseting phone was identified in windows. No recovery boot was working too... This is reason why I disassembled phone...
But thank you for reply..
Click to expand...
Click to collapse
if that worked, i'd be curious to know

Bricked A2017G

Hey Folks, i just bricked My Axon 7 some Days ago. It started randomly a reboot which i can't abort anymore. Everytime the Device get's a Charge does it start again. I can't enter TWRP or Fastboot (Reboots after a few Seconds). Same for the Flash Mode. It is now completely discharged and i don't know how to recover it. Any Ideas?
Think i can't fix this, but asking here don't hurts... :angel:

4th grade unbrick guide here in the Forums. That helped me after i cannot access any Mode. No Flash Mode, No EDL, No USB, No Qualcomm Loader. Axon 7 too.
https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898

HighSierra1014 said:
4th grade unbrick guide here in the Forums. That helped me after i cannot access any Mode. No Flash Mode, No EDL, No USB, No Qualcomm Loader. Axon 7 too.
https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898
Click to expand...
Click to collapse
Lol. I made a guide based on that one but updated, called DFU unbrick, because everybody had to read my comments there anyways to be able to do it. Not sure why everyone still uses the old one ?
@Miustone: If you want, you can try an EDL cable first. A lot of people say that they could get out of DFU that way. (assuming that you can get into EDL/DFU that is). Google my guide, it's called "DFU unbrick", if the EDL cable doesn't work

Thanks Guys! I will take a look on the DFU unbrick and the EDL Cable. At least a blink of Hope for this great Device... Still good as new, would be sad to use it just as a golden Sculpture lol

Miustone said:
Hey Folks, i just bricked My Axon 7 some Days ago. It started randomly a reboot which i can't abort anymore. Everytime the Device get's a Charge does it start again. I can't enter TWRP or Fastboot (Reboots after a few Seconds). Same for the Flash Mode. It is now completely discharged and i don't know how to recover it. Any Ideas?
Think i can't fix this, but asking here don't hurts... :angel:
Click to expand...
Click to collapse
Hey, sorry for asking but how did you brick it? I am thinking about installing a custom ROM, rooting etc and I would just like to know if it was something in specific so I can stay away from it. Cheers.

Dead P9 Lite

Hey guys! Fist I want to say hello as I'm new here, and will probabl stay for a while
Read some posts, guides, awesome content!
So here goes my question.
I wanted to debrand my Huawei P 9 Lite to C432. I rooted it, TWRP, oeminfo all fine. Then I flashed B130 Rom (as oem was B130), and it was done, 100%, install successful, all fine.
Until I tried to turn it on. After rom install it said it's gonna reboot. It didn't. I teied to boot it up -> nope, the phone seems to be "dead."
Although, the PC sees it. It is recognized as "Android Sooner Single ADB Interface" or when I update the driver "Android Bootloader Interface."
I can't do nothing with my phone, can't reflash, can't turn off, turn on, it is just dead. When I turn it off, it turns on automaticaly after a sec or 2. I know that because when it's connected to PC you hear a sound and driver as mentioned. Otherwise it has no sign of life.
Is there a way to save it? I'm gonna open it up and disconnect the battery and see if it wil change anything, although I kinda know where this is leadeing.
Any ideas?
Thanks in advance guys, have a nice one.

Any help with fully bricked device

Hello!
THink I have bricked my phone, but just checking before I go through what I suppose is a long process with oneplus.
Looking for any help. I had a working device - unlocked bootloader and installed TWRP and magisk using MauronofrioTool. ok - however, I found out I couldn't use a fingerprint security option on that would have been anoying. So... Long story short. I used MauronofrioTool to relock bootloader. Oops - so that didn't work. THen found out I couldn't do anything except stare at g.co/ADH message on my screen. Couldn
't get to fastboot or TWP. ANyway, so I managed to up and down volume and enter into TWRP. Was still connecting to the tool, so I downloaded factory Zips and tried to install via tool after unlocking - Seemed to be working ... but it stopped mid way through a process and hasbn't come back! NOthing at all. I wonder if I could have triggered an OEM thing? ANyway - literally nothing no buttons work no screen action. I see a QUSB_BULK_CID:etc number when connecting the phone, but that is it. No fast boot or any other actions available.
PLease, pretty devastating, Anyone know if I can do anything?

I'm no pro but I use this tool which helped me:

henk-jan said:
I'm no pro but I use this tool which helped me:
Click to expand...
Click to collapse
Thank you. I feel I am little past this stage now though.. Also trying the brick reprieve software . Just can't get my computer to recognise the phone now. No ability to get to emergency download path - think it is my crappy cihinese pc (old Huawei tablet basically) or Windows via apple that have me stranded.
**********SOLVED
THe crappy Chinese language Windows tablet worked as the unbrick OP said WIndows would. Must be a kink in the Windows via Mac that could get me into the situation, but not out.
Very relieved... Even though I still am not 100% sure what I actually ended up clicking to get it to register and connect with the unblock tool (which of course was in Chinese) hahaha.
Cheers
CHeers though

Glad you got it sorted out! Cheers

Need Help, please
Just received my OnePlus 8 pro, decided to Root and unlock the bootloader---this went fine.
I then went and upgraded to Android 11 DP3.
I'm now only able to get into Fastboot. at points it will try to boot but only get to the logo screen and then goes black.
When the phone boots up, it goes to Qualcomm CrashDump Mode.
I've been attempting to solve this for half the day with no luck. I've tried Msmtool, but it doesn't recognize the device, even after loading drivers again.
Is there a way to load a ROM from fastboot mode?
Hoping someone can assist, this is super frustrating and I would appreciate any help, please.
Rick

rickhurl said:
Just received my OnePlus 8 pro, decided to Root and unlock the bootloader---this went fine.
I then went and upgraded to Android 11 DP3.
I'm now only able to get into Fastboot. at points it will try to boot but only get to the logo screen and then goes black.
When the phone boots up, it goes to Qualcomm CrashDump Mode.
I've been attempting to solve this for half the day with no luck. I've tried Msmtool, but it doesn't recognize the device, even after loading drivers again.
Is there a way to load a ROM from fastboot mode?
Hoping someone can assist, this is super frustrating and I would appreciate any help, please.
Rick
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-8-pro/how-to/rom-stock-fastboot-roms-oneplus-8-pro-t4083997

cultofluna said:
https://forum.xda-developers.com/oneplus-8-pro/how-to/rom-stock-fastboot-roms-oneplus-8-pro-t4083997
Click to expand...
Click to collapse
Thanks so much. I ended up getting Msmtool to work. Although my device wasn't on (black screen) and it didn't fully show up in the tool, I decided to start the process anyway and it began to load.
I've been on here for over 10 yeas (XDA) I've just lost my account info and made a new one.
Thanks for taking the time to respond. Much appreciated.