I'd like to generate a thread with tried and tested ROMs, recovery, and root methods like magisk for the Moto G6
I'd especially like to see a working TWRP (official or unofficial), magisk boot img, and any known working custom ROMs
It's all in Guides, News, and Discussions already.
edit: and there's fairly obviously a thread with a working TWRP build in this section. I don't understand what you're asking?
TheDevl said:
It's all in Guides, News, and Discussions already.
edit: and there's fairly obviously a thread with a working TWRP build in this section. I don't understand what you're asking?
Click to expand...
Click to collapse
Do these work on the pie update?
I was want to see any and all available ROMs for this device
clcombs262 said:
Do these work on the pie update?
I was want to see any and all available ROMs for this device
Click to expand...
Click to collapse
Check out the treble-enabled device forums. For a while, this is more or less what you're going to have to pick through.
TheDevl said:
Check out the treble-enabled device forums. For a while, this is more or less what you're going to have to pick through.
Click to expand...
Click to collapse
Thx
About magisk on pie?
clcombs262 said:
Thx
About magisk on pie?
Click to expand...
Click to collapse
To my knowledge it works the same as it does on oreo.
TheDevl said:
To my knowledge it works the same as it does on oreo.
Click to expand...
Click to collapse
'to your knowledge'?
I haven't actually got the update yet, but I just wanted to check to see if I'd need to wait to root until the update, or do it now and Skip the update
Sent from my Moto G6 using XDA Labs
clcombs262 said:
'to your knowledge'?
I haven't actually got the update yet, but I just wanted to check to see if I'd need to wait to root until the update, or do it now and Skip the update
Sent from my Moto G6 using XDA Labs
Click to expand...
Click to collapse
I'm on Brazilian Pie, was on soak Pie and GSI pie and all rooted fine with Magisk 18.1 :good:
Moto g6 fastboot rom
HueyT said:
I'm on Brazilian Pie, was on soak Pie and GSI pie and all rooted fine with Magisk 18.1 :good:
Click to expand...
Click to collapse
i have a hardbricked G6 and i found the two testpoints inside which i connect and reach QDloader modus...now i want to flash it with Milfashtool but i didnt found a fastboot rom!?
mimi77 said:
i have a hardbricked G6 and i found the two testpoints inside which i connect and reach QDloader modus...now i want to flash it with Milfashtool but i didnt found a fastboot rom!?
Click to expand...
Click to collapse
Mine got brickes too..., can u point me where is these testpoints exactly? And what is milfashtool?
72k said:
Mine got brickes too..., can u point me where is these testpoints exactly? And what is milfashtool?
Click to expand...
Click to collapse
How do you mean bricked? Where is the phone hanging? I assume you already had unlocked your bootloader before attempting rooting/magisk?
theseeker2654 said:
How do you mean bricked? Where is the phone hanging? I assume you already had unlocked your bootloader before attempting rooting/magisk?
Click to expand...
Click to collapse
Yes i had bootloader unlocked but it still unrooted and its got bricked before i even try for rooting. First of all let me tell u the chronologies. I had this phone from someone in US as a gift but i cant use it on my country(because of network) so i give it a try by unlock the bootlooder, it was succeeded and one day comes update which is april 2018 patch. After the update my phone was unstable, self reboot and bootloops and i found that the screen is flickering sometimes. Then at one night it suddenly turned off when i was sleeping. I tried all method combination button but no luck, it is caused by a bad battery or firmware fail? Please help me!!!
Note: i only got led blinking if i press power plus plugged in charger, the led blinking faster after +20 sec
One single blink every 5 sec and then blinking goes faster after +20 sec for about 5 blinks and repeat to state one single blink. Seems like battery related but i have already open the backcase to see, if i unplugged its battery then push the buttons combination the led is blinking faster like the final state -sorry for bad english
theseeker2654 said:
How do you mean bricked? Where is the phone hanging? I assume you already had unlocked your bootloader before attempting rooting/magisk?
Click to expand...
Click to collapse
Hello do u have solution for me? I managed to buy new battery because of this problem, please read all my walkthrough and give me and advice
72k said:
Hello do u have solution for me? I managed to buy new battery because of this problem, please read all my walkthrough and give me and advice
Click to expand...
Click to collapse
what have you done? Did the new battery resolve your issue? Do you know how to install it? Have you tried plugging it into power and then pressing and holding vol down and power for 2minutes?
theseeker2654 said:
what have you done? Did the new battery resolve your issue? Do you know how to install it? Have you tried plugging it into power and then pressing and holding vol down and power for 2minutes?
Click to expand...
Click to collapse
I did nothing except my bootloader is unlocked and do an OTA update (april 2018 if i remember) and its suddenly turn off when i was sleep with state of bootloop days before that. I havent buy any batteries yet because i need to know what is the problem. Yes i've done all of power combination for even 5mnts. It strange because the LED show me different if i press power combination button
---------- Post added at 05:07 AM ---------- Previous post was at 04:54 AM ----------
theseeker2654 said:
what have you done? Did the new battery resolve your issue? Do you know how to install it? Have you tried plugging it into power and then pressing and holding vol down and power for 2minutes?
Click to expand...
Click to collapse
For ex : it wont blinking at all if the battery completely empty. Then if i charge for awhile it would blink if i pressed power with vol down (after 20 sec) as i described above. Untill the final state of LED i release power and vol down and immediatly pressed vol up then its LED will keep blinking fast forever as long as the charger is plugged in
My moto g6 also appears to be bricked
I don't want to hijack this thread, but since I'm a new member I can't start a forum thread. Now on to the issue with my g6...
When I plug in my g6 the only thing that happens is a small white led flashes at the top right part of the unit. After about 20 mins or so it stops flashing. Holding down the vol+power buttons to go into recover just cycles the power off and on, with the white led flashing just like before. No recovery screen appears, no android robot; only the blinking white led--the display is otherwise entirely blank & black (meaning not lit at all).
When I connect the g6 to my PC I hear the usual "USB beep" indicating that it's recognized the phone being connected, but it does not show any drive or device either in Device Manager or in Explorer. I'm using Win10, with all the Motorola drivers+software installed.
I rooted the phone some time ago, and the bootloader was unlocked before the phone went dead. The last thing I did with the phone was to flash an Android 9 image from the forum here while the phone was connected to my PC.
https://forum.xda-developers.com/mo...android-aosp-9-0-pie-android-9-0-0r1-t3847354
I had flashed others images with no problems up to that point, even the one linked above. But I re-flashed that image since I wanted to "reset" the image to it's stock point (I had made some settings and added apps I wanted to remove, start clean again). The ONLY thing I did different was that the battery was about 50% so I left the phone charge on one of my PC's USB ports while the image was installing. When I checked the phone the next morning it was dead. Afterwards I let it charge for a week but nothing.
Last but not certainly least, I have also tried two different batteries I ordered from Amazon. No change with either one (blinking white led), despite charging each with the original charger for one week.
Sorry for being so long-winded, but I wanted to give as much detail as possible to see if someone here may have a solution. My guess is that I made an incredibly stupid mistake by letting the phone charge from my PC while flashing/installing the A9 image; I really should have left it on my moto g6 charger.
Cant flash magisk 20.1 or even any other always stuck on bootloop any suggestions
Device.= Moto g6 4gb ram
Rom= stock rom
Bootloader =unlocked
Recovery=TWRP 3.2/3.3
Can't flash no encryption either always show error 1
rohit1363 said:
Cant flash magisk 20.1 or even any other always stuck on bootloop any suggestions
Device.= Moto g6 4gb ram
Rom= stock rom
Bootloader =unlocked
Recovery=TWRP 3.2/3.3
Can't flash no encryption either always show error 1
Click to expand...
Click to collapse
Don't use anything higher than Magisk 19.3, for some reason higher versions bootloop the phone. After you install Magisk 19.3, you can upgrade normally via Magisk Manager
AgentICS said:
Don't use anything higher than Magisk 19.3, for some reason higher versions bootloop the phone. After you install Magisk 19.3, you can upgrade normally via Magisk Manager
Click to expand...
Click to collapse
Yeah that's works fine just taking longer boot time but that's ok i am giving it to my father so i don't need to root or anything .
Anyway thank you for help it really works...
Related
Alright i got 6 hours before tmbobile store opens and i can HOPEFULLY get an exchange, but not banking on it. btw im new to rooting so i wasnt familiar with the process, but regardless i have hard bricked my NEXUS 5. Title says the problem. I followed wwjoshdew's guide to rooting on youtube, and rooted successfully. But i could'nt for the life of me figure out how to create nandroid. I ended up realizing i didnt download cmw recovery mode and downloaded it from the play store. the app took me to a button that said flash recovery and i hit it and my phone asked for permission from unknown source, i hit ok and it shut down, on 70% battery life. Not turning on please help
Try to boot the phone into bootloader mode. Just hold volume down and the power button. From there try to cycle to recovery. You use your volume down to cycle through the options and power but as select. If you can boot into recovery and have that successfully installed then you can erase your phone and try to power it on from there. If you didn't successful install the custom recovery then you'll have the standard Android recovery. You can erase everything from that too.
These phones are hard to brick and not be able to fix it.
Sent from my Nexus 5 using XDA Premium 4 mobile app
ruben8448 said:
Try to boot the phone into bootloader mode. Just hold volume down and the power button. From there try to cycle to recovery. You use your volume down to cycle through the options and power but as select. If you can boot into recovery and have that successfully installed then you can erase your phone and try to power it on from there. If you didn't successful install the custom recovery then you'll have the standard Android recovery. You can erase everything from that too.
These phones are hard to brick and not be able to fix it.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Doesn't turn on dude. No matter what. I am new to roms but i know what a hard brick is.
You should really read the guides and stickied threads at the top of these forums. The guides are very noob friendly and you wouldn't have bricked your phone. There's one to reset your device to stock as well. There's really no need for this thread and on top of that there is a sticky that says no questions in the General forums.
Sent from my Nexus 5 using Tapatalk
Determine your phone is actually off. Plug your phone into charge, if a battery sign appears in the middle of the screen then your phone is off.
If your phone is off, hold down the volume down button with the power button to start the bootloader, press volume down twice and press the power button to enter recovery.
If your screen remains black and doesn't show a battery logo, hold the volume up, volume down and power buttons at the same time for a minute, then let go and hold down the power button. Which should hopefully start your phone.
FuMMoD said:
You should really read the guides and stickied threads at the top of these forums. The guides are very noob friendly and you wouldn't have bricked your phone. There's one to reset your device to stock as well. There's really no need for this thread and on top of that there is a sticky that says no questions in the General forums.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
You should have been around long enough to know that when newbies break their new toys they go nuclear and dismiss all the information around them.
BNNEBULA said:
Alright i got 6 hours before tmbobile store opens and i can HOPEFULLY get an exchange, but not banking on it. btw im new to rooting so i wasnt familiar with the process, but regardless i have hard bricked my NEXUS 5. Title says the problem. I followed wwjoshdew's guide to rooting on youtube, and rooted successfully. But i could'nt for the life of me figure out how to create nandroid. I ended up realizing i didnt download cmw recovery mode and downloaded it from the play store. the app took me to a button that said flash recovery and i hit it and my phone asked for permission from unknown source, i hit ok and it shut down, on 70% battery life. Not turning on please help
Click to expand...
Click to collapse
You bricked a Nexus?
Hold down Volume Down, Up, and Power to get into fastboot mode. Restore from Factory Image.
Normally, to root a nexus, I fastboot Team Win Recovery Project.
Anyways what you did simply could not HARD BRICK the phone.
zeekiz said:
You should have been around long enough to know that when newbies break their new toys they go nuclear and dismiss all the information around them.
Click to expand...
Click to collapse
Seriously lol. Even though the guides are right there in their faces.
Sent from my Nexus 5 using Tapatalk
HELP SOS
FuMMoD said:
You should really read the guides and stickied threads at the top of these forums. The guides are very noob friendly and you wouldn't have bricked your phone. There's one to reset your device to stock as well. There's really no need for this thread and on top of that there is a sticky that says no questions in the General forums.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
My Nexus5 doesn't flash the Led light or enter bootloader and software . I was flashing the based CM kernel and i followed the instructions nicely, while using TWRP Recovery i pressed reboot system after the flash and the phone suddenly died. I connected it to the PC and the installing drivers popup appeared and it didn't install them, problem(QHSUSB_BULK) it only appeared once. And since that, phone is dead. PLEASE HELP!!!!
Yazan Abzakh171 said:
My Nexus5 doesn't flash the Led light or enter bootloader and software . I was flashing the based CM kernel and i followed the instructions nicely, while using TWRP Recovery i pressed reboot system after the flash and the phone suddenly died. I connected it to the PC and the installing drivers popup appeared and it didn't install them, problem(QHSUSB_BULK) it only appeared once. And since that, phone is dead. PLEASE HELP!!!!
Click to expand...
Click to collapse
Do you have a link to the kernel you flashed? I think you done bricked it good.
Were you using this method?
http://www.youtube.com/watch?v=w3beFx-3Ic4
If yes,I think then all Nexus 5 users should be warned about CF's autoroot issues,because I see more and more topics related to this issue.
Simonna said:
Were you using this method?
http://www.youtube.com/watch?v=w3beFx-3Ic4
If yes,I think then all Nexus 5 users should be warned about CF's autoroot issues,because I see more and more topics related to this issue.
Click to expand...
Click to collapse
I don't believe the issues you're seeing, appears to be failed emmc, is related to chain fire's auto root. Cf is probably the most popular method to root and it's a coincidence. I've seen these failures with other root methods too.
I think the op flashed a kernel not for his device.
jd1639 said:
I don't believe the issues you're seeing, appears to be failed emmc, is related to chain fire's auto root. Cf is probably the most popular method to root and it's a coincidence. I've seen these failures with other root methods too.
I think the op flashed a kernel not for his device.
Click to expand...
Click to collapse
I am not a developer so bear with me. I'm just a guy in mpls with a completely stock N5 from Google Play that encountered similar issue as the original post. There was no damage or water issue, or other problem prior to going dead. It had about 50% battery and maybe 15 minutes after reading an email it was dead when I looked at it again. It just simply turned off while in my pocket. I could not get it to power on or enter bootloader or a recovery screen. After a week of trying to charge via USB and the original wall charger and countless attempts to hold power and volume buttons without success, I decided to pop the back off and disconnected the battery. I put it back together, but that made no difference either. Google play will send me a new phone, but I'd like to get it fired up and extract the last week or so of pics. Any ideas? Again, I am a complete noob and this 3 month old phone has not been modified in any way, other than auto updates from Google play. Thanks for any assistance or guidance.
elf1967 said:
I am not a developer so bear with me. I'm just a guy in mpls with a completely stock N5 from Google Play that encountered similar issue as the original post. There was no damage or water issue, or other problem prior to going dead. It had about 50% battery and maybe 15 minutes after reading an email it was dead when I looked at it again. It just simply turned off while in my pocket. I could not get it to power on or enter bootloader or a recovery screen. After a week of trying to charge via USB and the original wall charger and countless attempts to hold power and volume buttons without success, I decided to pop the back off and disconnected the battery. I put it back together, but that made no difference either. Google play will send me a new phone, but I'd like to get it fired up and extract the last week or so of pics. Any ideas? Again, I am a complete noob and this 3 month old phone has not been modified in any way, other than auto updates from Google play. Thanks for any assistance or guidance.
Click to expand...
Click to collapse
So, your phone doesn't turn on at all?
jd1639 said:
I don't believe the issues you're seeing, appears to be failed emmc, is related to chain fire's auto root. Cf is probably the most popular method to root and it's a coincidence. I've seen these failures with other root methods too.
I think the op flashed a kernel not for his device.
Click to expand...
Click to collapse
Correct. No symbols, no battery icon, no vibrate, etc.
elf1967 said:
Correct. No symbols, no battery icon, no vibrate, etc.
Click to expand...
Click to collapse
I'm afraid there's nothing you can do. It would have to at least get into recovery or bootloader to have a prayer.
jd1639 said:
I'm afraid there's nothing you can do. It would have to at least get into recovery or bootloader to have a prayer.
Click to expand...
Click to collapse
Thanks - was just hoping it was not a hardware failure given the posts about difficulty bricking N5. Any chance if I bought a new battery that came charged it would fire up or replacing the motherboard an option?
p.s. I am not the original poster so not sure if I ticked someone off or not, sorry if I did. Just looking for assistance
elf1967 said:
Thanks - was just hoping it was not a hardware failure given the posts about difficulty bricking N5. Any chance if I bought a new battery that came charged it would fire up or replacing the motherboard an option?
p.s. I am not the original poster so not sure if I ticked someone off or not, sorry if I did. Just looking for assistance
Click to expand...
Click to collapse
It sure sounds like a hardware failure. Doubt a different battery would help. And don't worry about being the original op. This thread is old
jd1639 said:
It sure sounds like a hardware failure. Doubt a different battery would help. And don't worry about being the original op. This thread is old
Click to expand...
Click to collapse
I get the unknown device driver when hooked up USB to computer (QHSUSB_BULK). Think it is worth waiting a few weeks prior to returning it to see if there is a way to access the flash memory via a driver download? Searches for help showed similar unknown driver problem workable on samsung and HTC last year (QHSUSB_DLOAD)
elf1967 said:
I get the unknown device driver when hooked up USB to computer (QHSUSB_BULK). Think it is worth waiting a few weeks prior to returning it to see if there is a way to access the flash memory via a driver download? Searches for help showed similar unknown driver problem workable on samsung and HTC last year (QHSUSB_DLOAD)
Click to expand...
Click to collapse
No, you won't be able to. The memory doesn't mount like a sd card would. For the future use something like drop box or Google drive too backup your photos as you take them.
So today I wanted to install Cyanogenmod on my HTC one S.
I followed a guide (the usual procedure: unlock bootloader, root, flash recovery. i can't post links due to being new so i can't post it). Everything when fine until I flashed the recovery (CWM 5.8). As soon as this was done my phone went off and couldn't be switched on again.
When I press the power button for 20+ seconds nothing at all happens.
When I hold the Vol- button and the power key the LED comes on (as it is charging right now) and disappears after 5 seconds.
I also had rather low battery (~35%) when unlocking bootloader and rooting, but flashing the recovery went fine. It completed as far as I know.
Please help me. Thanks in advance! I searched dozens of threads but none could resolve my problem.
supermasenko said:
So today I wanted to install Cyanogenmod on my HTC one S.
I followed a guide (the usual procedure: unlock bootloader, root, flash recovery. i can't post links due to being new so i can't post it). Everything when fine until I flashed the recovery (CWM 5.8). As soon as this was done my phone went off and couldn't be switched on again.
When I press the power button for 20+ seconds nothing at all happens.
When I hold the Vol- button and the power key the LED comes on (as it is charging right now) and disappears after 5 seconds.
I also had rather low battery (~35%) when unlocking bootloader and rooting, but flashing the recovery went fine. It completed as far as I know.
Please help me. Thanks in advance! I searched dozens of threads but none could resolve my problem.
Click to expand...
Click to collapse
Where you got CWM 5.8 from? Its for a reason that every guide tells you to flash only with battery 70%+ ...
LS.xD said:
Where you got CWM 5.8 from? Its for a reason that every guide tells you to flash only with battery 70%+ ...
Click to expand...
Click to collapse
From the guide. I suppose it was a bit out of date. I know I should have waited and charged. Anything I could try?
supermasenko said:
From the guide. I suppose it was a bit out of date. I know I should have waited and charged. Anything I could try?
Click to expand...
Click to collapse
From which guide?? Does your phone charge wihile connected to a wall charger?
LS.xD said:
From which guide?? Does your phone charge wihile connected to a wall charger?
Click to expand...
Click to collapse
From the guide install cyanogenmod on htc one s on androidpit.de. I can't post links as a new member.
I am not sure whether it charges or not to be honest, the LED doesn't light up, but sometimes it didn't when I charged it in the past.
supermasenko said:
From the guide install cyanogenmod on htc one s on androidpit.de. I can't post links as a new member.
I am not sure whether it charges or not to be honest, the LED doesn't light up, but sometimes it didn't when I charged it in the past.
Click to expand...
Click to collapse
Send me the link via private message please. I can't find the guide.
Hello guys,
I apologize if this has been solved before but I wasn't able to find anything on it.
I have a oneplus one phone which I had running Ressurection Rom (I don't have the details as my father was using it for the last 2 years).
He dropped the phone and gave it to a shop for repairing of the screen. They repaired the screen but now they have somehow messed with the software where I am UNABLE TO BOOT TO FASTBOOT OR TRWP. The function of holding POWER + VOLUME DOWN or POWER + VOLUME UP doesn't work. When I attempt those two options, it still continues to boot as it normally would and then start optimizing apps. Does that for about 45 minutes and then just restarts and repeats the process.
I haven't messed around with android stuff for about a year now, so simplified instructions (rather step by step) would be extremely helpful.
Thank you so much for taking the time.
NSingh95 said:
Hello guys,
I apologize if this has been solved before but I wasn't able to find anything on it.
I have a oneplus one phone which I had running Ressurection Rom (I don't have the details as my father was using it for the last 2 years).
He dropped the phone and gave it to a shop for repairing of the screen. They repaired the screen but now they have somehow messed with the software where I am UNABLE TO BOOT TO FASTBOOT OR TRWP. The function of holding POWER + VOLUME DOWN or POWER + VOLUME UP doesn't work. When I attempt those two options, it still continues to boot as it normally would and then start optimizing apps. Does that for about 45 minutes and then just restarts and repeats the process.
I haven't messed around with android stuff for about a year now, so simplified instructions (rather step by step) would be extremely helpful.
Thank you so much for taking the time.
Click to expand...
Click to collapse
This condition is called hard brick.To fix this,
https://forums.oneplus.net/threads/...ol-restore-stock-cm11s-fix-bricks-etc.237827/
Use this tool on winXp or win7(don't use 8 or 10),run it as administrator.Make sure you install the drivers correctly,good luck!
Mr.Ak said:
This condition is called hard brick.To fix this,
https://forums.oneplus.net/threads/...ol-restore-stock-cm11s-fix-bricks-etc.237827/
Use this tool on winXp or win7(don't use 8 or 10),run it as administrator.Make sure you install the drivers correctly,good luck!
Click to expand...
Click to collapse
Hello, Thank you for your response.
I have tried the instructions that you provided and I am stuck in a place where the "Samsung" drivers for OPO are installed but the phone isn't detected by the computer when its plugged in. I assume that means the drivers aren't installed correctly. However, when I do open device manager and attempt to update or uninstall the drivers there isn't a device there that is representative of OPO.
How do I get to the point where the drivers can be installed without me having access to the phone. I can't really go into a bricked phone and turn on ADB etc.'
Thank you
NSingh95 said:
Hello, Thank you for your response.
I have tried the instructions that you provided and I am stuck in a place where the "Samsung" drivers for OPO are installed but the phone isn't detected by the computer when its plugged in. I assume that means the drivers aren't installed correctly. However, when I do open device manager and attempt to update or uninstall the drivers there isn't a device there that is representative of OPO.
How do I get to the point where the drivers can be installed without me having access to the phone. I can't really go into a bricked phone and turn on ADB etc.'
Thank you
Click to expand...
Click to collapse
Read the whole thread.
https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Use Xp or win7(must).
Okay so I have attempted this a tiring number of times; initially the phone at least was going on to loading apps, now it just flashes on the Resurrection load screen and doesn't change at all. Also when I try to boot into recovery/fastboot, nothing happens.
I have also tried installing different drivers from like a samsung phone, nexus but to no avail.
Is there anyone who can perhaps TEAMVIEW me and help out or live chat?
NSingh95 said:
Okay so I have attempted this a tiring number of times; initially the phone at least was going on to loading apps, now it just flashes on the Resurrection load screen and doesn't change at all. Also when I try to boot into recovery/fastboot, nothing happens.
I have also tried installing different drivers from like a samsung phone, nexus but to no avail.
Is there anyone who can perhaps TEAMVIEW me and help out or live chat?
Click to expand...
Click to collapse
Device on Twrp works fine?
Mr.Ak said:
Device on Twrp works fine?
Click to expand...
Click to collapse
I'm not able to boot into twrp.
NSingh95 said:
I'm not able to boot into twrp.
Click to expand...
Click to collapse
@psxda97 ,can this be a battery issue?
Mr.Ak said:
@psxda97 ,can this be a battery issue?
Click to expand...
Click to collapse
I don't think so. If it is a battery issue he could go to fastboot since fastboot only uses a small amount of charge.
NSingh95 said:
I'm not able to boot into twrp.
Click to expand...
Click to collapse
Try turning on your phone while connected to a charger.
psxda97 said:
I don't think so. If it is a battery issue he could go to fastboot since fastboot only uses a small amount of charge.
Try turning on your phone while connected to a charger.
Click to expand...
Click to collapse
I have, its definitely not a battery issue, because i have seen the phone stay on for an hour just on the bootscreen without being plugged in or anything.
NSingh95 said:
I have, its definitely not a battery issue, because i have seen the phone stay on for an hour just on the bootscreen without being plugged in or anything.
Click to expand...
Click to collapse
Most probably your volume buttons were messed up during the repair. That's the only reason I can think of. There are some videos on YouTube about fixing the volume buttons.
Hi all,
I need your help, as I think, that I bricked my phone.
I unlocked my bootloader yesterday after waiting 360 hours, and tried to flash the Global MIUI 10 Beta via the MI Flash tool in Windows 10, coming from MIUI 9 Global stable.
Phone was recognized, flashing started but after a few seconds it showed an error message, that a file could not be found.
As it was late already and I did not want to continue, I unplugged the phone from the USB cable (biggest mistake ever), which caused the phone to shut off immediately.
Since this I am no longer able to power off the phone, at all.
No fastboot, no recovery, no sign of life at all, when pressing the power button, not even the charging light...
Is there any hope to bring it back to life???
Thanks,
Tobuur
Tobuur said:
Hi all,
I need your help, as I think, that I bricked my phone.
I unlocked my bootloader yesterday after waiting 360 hours, and tried to flash the Global MIUI 10 Beta via the MI Flash tool in Windows 10, coming from MIUI 9 Global stable.
Phone was recognized, flashing started but after a few seconds it showed an error message, that a file could not be found.
As it was late already and I did not want to continue, I unplugged the phone from the USB cable (biggest mistake ever), which caused the phone to shut off immediately.
Since this I am no longer able to power off the phone, at all.
No fastboot, no recovery, no sign of life at all, when pressing the power button, not even the charging light...
Is there any hope to bring it back to life???
Thanks,
Tobuur
Click to expand...
Click to collapse
I have the same problem after flash to pie. (See my question)
I bought a new phone
But I will try with a special edm cable to flash again. But it will take some weeks before arriving my country.
Seosam said:
But I will try with a special edm cable to flash again. But it will take some weeks before arriving my country.
Click to expand...
Click to collapse
You know, that you can build this cable by yourself?
http://en.miui.com/thread-324300-1-1.html
Tobuur said:
You know, that you can build this cable by yourself?
http://en.miui.com/thread-324300-1-1.html
Click to expand...
Click to collapse
Now I know it
Do you tries this for your phone?
Seosam said:
Now I know it
Do you tries this for your phone?
Click to expand...
Click to collapse
No, not yet. This will be one of my last options.
I am currently trying to get the phone replaced.
As long as this is ongoing I will leave the phone as it is...
But I noticed, that at the back-cover is a spot, which is a little bit warmer than the rest of the back-cover. Just on th right side of the camera.
So it seems, that there is still some sort of life in the phone, even with a black screen.
Perhaps a restart after a complete battery drain will help. I do not want to open the phone at the moment to detach the battery.
Tobuur said:
Hi all,
I need your help, as I think, that I bricked my phone.
I unlocked my bootloader yesterday after waiting 360 hours, and tried to flash the Global MIUI 10 Beta via the MI Flash tool in Windows 10, coming from MIUI 9 Global stable.
Phone was recognized, flashing started but after a few seconds it showed an error message, that a file could not be found.
As it was late already and I did not want to continue, I unplugged the phone from the USB cable (biggest mistake ever), which caused the phone to shut off immediately.
Since this I am no longer able to power off the phone, at all.
No fastboot, no recovery, no sign of life at all, when pressing the power button, not even the charging light...
Is there any hope to bring it back to life???
Thanks,
Tobuur
Click to expand...
Click to collapse
You will not do anything now. Only firmware through testpoint EDL mode. Don't need special edl cable. http://en.miui.com/thread-3413004-1-1.html . Only need Authorized Mi EDL Account .
Asikskz said:
You will not do anything now. Only firmware through testpoint EDL mode. Don't need special edl cable. http://en.miui.com/thread-3413004-1-1.html . Only need Authorized Mi EDL Account .
Click to expand...
Click to collapse
Thanks for your reply.
Are you aware of this thread: https://forum.xda-developers.com/xi.../flash-unbrick-mi-mix-2s-test-method-t3823994
I do not want to open the phone for something, which has not been confirmed to work.
I am still hoping for a replacement and I guess, once I opened the phone, this possibility would be gone....
Furthermore I do not have an EDL account
So this method would be my very last option
Tobuur said:
Thanks for your reply.
Are you aware of this thread: https://forum.xda-developers.com/xi.../flash-unbrick-mi-mix-2s-test-method-t3823994
I do not want to open the phone for something, which has not been confirmed to work.
I am still hoping for a replacement and I guess, once I opened the phone, this possibility would be gone....
Furthermore I do not have an EDL account
So this method would be my very last option
Click to expand...
Click to collapse
I opened my phone and remove battery. But nothing happened.
The same with the testpoint.
So I believe it doesn't work for your phone too.
Seosam said:
I opened my phone and remove battery. But nothing happened.
The same with the testpoint.
So I believe it doesn't work for your phone too.
Click to expand...
Click to collapse
Thanks for letting me know :good:
After getting update I was trying to flash TWRP and was having troubles. The first one was something to do with the partitions. After following a guide to change the slot I then went and flashed TWRP and now I'm stuck in a boot loop with the one plus animation going round slowly.
I'm currently looking in to the msm tool but I'm in a panic as I cant get into fastboot mode. Does anyone have any advice. Have I lost everything. Did I brick it.
Thank you
try to press volume up + volume down + power button
Just use the MSM tool, youre using the EDL mode there. Its going to be alright, I had it bricked like that the first day i bought the phone.
Limetak said:
Just use the MSM tool, youre using the EDL mode there. Its going to be alright, I had it bricked like that the first day i bought the phone.
Click to expand...
Click to collapse
Thanks. I did use it. But I had problems connecting to it. Turns it was the drivers needing updating. But still it was a bit of a panic. Thought I had completely ruined it.
I'm wondering though does this tool re lock the bootloader?
JohnsNotHome said:
Thanks. I did use it. But I had problems connecting to it. Turns it was the drivers needing updating. But still it was a bit of a panic. Thought I had completely ruined it.
I'm wondering though does this tool re lock the bootloader?
Click to expand...
Click to collapse
Yes, it does.
Fortunately this is OP not Xiaomi, so you don't have to wait 4 years to unlock it again if you want to.
loshabih said:
try to press volume up + volume down + power button
Click to expand...
Click to collapse
This is also what I would suggest. Hold that combo to get to bootloader. You may need to hold that for a few seconds to power down the phone, then hold them again to boot to bootloader.
---------- Post added at 09:11 AM ---------- Previous post was at 09:06 AM ----------
JohnsNotHome said:
After getting update I was trying to flash TWRP and was having troubles. The first one was something to do with the partitions. After following a guide to change the slot I then went and flashed TWRP and now I'm stuck in a boot loop with the one plus animation going round slowly.
I'm currently looking in to the msm tool but I'm in a panic as I cant get into fastboot mode. Does anyone have any advice. Have I lost everything. Did I brick it.
Click to expand...
Click to collapse
You haven't been specific about that guide, or what steps you took exactly. But you shouldn't have to mess with changing slots to install TWRP. There are a couple ways to retain TWRP after an update. But again, without more details, it is impossible to tell what you have done, or to what extent you need to do exactly to get it up and running. But this phone is pretty hard to permanently brick, since we have the unbrick tool.
Hi,
You do not need to have the fastboot mode. Turn off your phone, on black screen hold vol up for 6-10 sec and plug usb cabel. After that make sure that your pc can see the phone, then run as admin the msm tool. It always worked for me for OP3T, OP5T and now for OP7Pro.
Full instraction and the msm tool is here.
Hope you will bring back to life your phone.
Thank you so much. !
Limetak said:
I had it bricked like that the first day i bought the phone.
Click to expand...
Click to collapse
And me thinking, I was the only one Who bricked his Phone the first day :silly: