Related
Bricked OP2 ...
Hi all
I bought the oneplus 2 4 days ago.
I rooted it, installed twrp and flashed nethunter2.0 CM12 then wiped cache , well the flash didn't go very successfully as the os still oxygen but i had all applications from nethunter installed and fully functional.
I decided to use the nethunter installer provided by the official site but not including the onplus2 version, i included the custom rom in replacement of the choosed one
.. but accidentally in the process of this tool it flashed stok for nexus which completely bricked the phone... nothing works, not boot no charge no sound...
I plugged again the phone and pressed for 20 seconds the power + volume up button and i got the bulk usb driver as it was a oneplus one .. i changed the driver settings to accept the unsigned drivers and updated the unkown device to the qualcomm 9008 ( as it was like a oneplus one ) .
The issue is that oneplus two has a Qualcomm MSM8994 Snapdragon 810 and the version i found for ColorOS is only for MSM8794 .. so i couldn't do anything
please can anyone help me?
any hint please?
Thank you in advance
If you flashed a ROM that's not for you're phone you're more than likely screwed
Could you try the following:
1, plug the phone back in recovery/fastboot mode
2, Open Computer Management and delete the drivers the OS finds for the phone
3, Download the ADB driver tool from here: http://forum.xda-developers.com/showthread.php?t=2588979
Try follow the steps and let me know if u get the drivers needed for the recovery
If the tool on the above link dont work, try this one: http://download.clockworkmod.com/test/UniversalAdbDriverSetup.msi
Bhups said:
Could you try the following:
1, plug the phone back in recovery/fastboot mode
2, Open Computer Management and delete the drivers the OS finds for the phone
3, Download the ADB driver tool from here: http://forum.xda-developers.com/showthread.php?t=2588979
Try follow the steps and let me know if u get the drivers needed for the recovery
If the tool on the above link dont work, try this one: http://download.clockworkmod.com/test/UniversalAdbDriverSetup.msi
Click to expand...
Click to collapse
Thank you for your response, the issue is that it's hard bricked, so no recovery mode no led , nothing ..
i uninstalled the drivers ( even that i had the adb working before ) and the device is detectable now only with as QHSUSB_BULK
the installation of any adb usb driver don't change anything, only qualcomm usb drivers work ( i have the 9008 only but i'm think it's not compatible with OP2) i could manually change it to adb ( mobistel Cynus f4 ADB interface ) but nothing new..
Help plz
thanks again
mG!X said:
Hi all
I bought the oneplus 2 4 days ago.
I rooted it, installed twrp and flashed nethunter2.0 CM12 then wiped cache , well the flash didn't go very successfully as the os still oxygen but i had all applications from nethunter installed and fully functional.
I decided to use the nethunter installer provided by the official site but not including the onplus2 version, i included the custom rom in replacement of the choosed one
.. but accidentally in the process of this tool it flashed stok for nexus which completely bricked the phone... nothing works, not boot no charge no sound...
I plugged again the phone and pressed for 20 seconds the power + volume up button and i got the bulk usb driver as it was a oneplus one .. i changed the driver settings to accept the unsigned drivers and updated the unkown device to the qualcomm 9008 ( as it was like a oneplus one ) .
The issue is that oneplus two has a Qualcomm MSM8994 Snapdragon 810 and the version i found for ColorOS is only for MSM8794 .. so i couldn't do anything
please can anyone help me?
any hint please?
Thank you in advance
Click to expand...
Click to collapse
Two problems here. The first problem is that you didn't wipe properly when flashing Nethunter, that's why you ended up with Nethunter apps on your stock ROM. When flashing a ROM you must perform a full wipe, this consists of system, data, cache, and dalvik cache. This isn't what bricked your phone though. We know what bricked your phone; flashing a ROM for a completely different device. I'm not sure why you would flash a ROM from another device, maybe due to inexperience, but that's the last thing you should be doing, as you now know. Don't use the recovery tool that you have, it isn't for your chipset, it will only make matters worse. I honestly don't think there's any way to revive your device, you've pretty much rendered it useless. I'd strongly suggest you do a lot of research before deciding to mess with another phone, if you don't know what you're doing then don't do it. Venturing into unknown lands like this only ever ends in disaster.
Heisenberg said:
Two problems here. The first problem is that you didn't wipe properly when flashing Nethunter, that's why you ended up with Nethunter apps on your stock ROM. When flashing a ROM you must perform a full wipe, this consists of system, data, cache, and dalvik cache. This isn't what bricked your phone though. We know what bricked your phone; flashing a ROM for a completely different device. I'm not sure why you would flash a ROM from another device, maybe due to inexperience, but that's the last thing you should be doing, as you now know. Don't use the recovery tool that you have, it isn't for your chipset, it will only make matters worse. I honestly don't think there's any way to revive your device, you've pretty much rendered it useless. I'd strongly suggest you do a lot of research before deciding to mess with another phone, if you don't know what you're doing then don't do it. Venturing into unknown lands like this only ever ends in disaster.
Click to expand...
Click to collapse
Thanks for your response.
I made a full wipe with Twrp ( as mentionned in your tutorial ) and al steps run without issues.
The issue is that the next day i used the nethunter install tool instead of manually installing, in the steps for one plus one ( not oneplus 2) i mentionned the specific rom which can run on the phone but suddenly when i pushed next it was flashing stock for nexus ( and yes it's in the steps of oneplus1 :/ i verified ) , well i know that it's inadmissible and can brick it seriously
now i have the bulkusb when linked to windows8 and pressing on poweron+volumeup, what do you recommend please? there is no compatible driver for snapdragon 810?flashing to colorOS won't solve the issue please?
Thanks in advance
mG!X said:
Thanks for your response.
I made a full wipe with Twrp ( as mentionned in your tutorial ) and al steps run without issues.
The issue is that the next day i used the nethunter install tool instead of manually installing, in the steps for one plus one ( not oneplus 2) i mentionned the specific rom which can run on the phone but suddenly when i pushed next it was flashing stock for nexus ( and yes it's in the steps of oneplus1 :/ i verified ) , well i know that it's inadmissible and can brick it seriously
now i have the bulkusb when linked to windows8 and pressing on poweron+volumeup, what do you recommend please? there is no compatible driver for snapdragon 810?flashing to colorOS won't solve the issue please?
Thanks in advance
Click to expand...
Click to collapse
Well flashing ColorOS using the tool you have will attempt to flash ColorOS for the OnePlus One, because that tool is not for your device. As I said, don't use it, it's not for your device so it will only do more harm. I don't know if there's a recovery tool for the Two yet, I certainly haven't seen one.
Heisenberg said:
Well flashing ColorOS using the tool you have will attempt to flash ColorOS for the OnePlus One, because that tool is not for your device. As I said, don't use it, it's not for your device so it will only do more harm. I don't know if there's a recovery tool for the Two yet, I certainly haven't seen one.
Click to expand...
Click to collapse
Ok, i will search maybe the drivers come out or someone find a solution, i ill contact support and seek their help also. Thanks and i will keep you updated if i find something
mG!X said:
Ok, i will search maybe the drivers come out or someone find a solution, i ill contact support and seek their help also. Thanks and i will keep you updated if i find something
Click to expand...
Click to collapse
I just can say, your device is not hard bricked and will be recoverable.
You just need to be a bit patient. For the OPO, there was the ColorOs emergency recovery available (which helped me already 2x unbricking my OPO after I compiled a faulty kernel).
I just have not yet seen something similar for the OP2. But as you get the bulk_device still recognized via USB, this means the Qualcomm emergency boot loader is still intact and once the recovery stuff leaks somewhere, you will be able to fully recover your OP2.
Don't ask me when this will be available, think it also took weeks for the OPO before it was posted somewhere.
All the best!
Andi
mG!X said:
Thank you for your response, the issue is that it's hard bricked, so no recovery mode no led , nothing ..
i uninstalled the drivers ( even that i had the adb working before ) and the device is detectable now only with as QHSUSB_BULK
the installation of any adb usb driver don't change anything, only qualcomm usb drivers work ( i have the 9008 only but i'm think it's not compatible with OP2) i could manually change it to adb ( mobistel Cynus f4 ADB interface ) but nothing new..
Help plz
thanks again
Click to expand...
Click to collapse
You can try this (but with oxygenos), but I'm not sure if it works with OP2 snapdragon 810
https://forums.oneplus.net/threads/solution-bricked-oneplus-one-recovery.306306/
EDIT: It seems you will need fastboot image of oxygenos and list of partitions ... anyway, good luck
yanick76 said:
You can try this (but with oxygenos), but I'm not sure if it works with OP2 snapdragon 810
https://forums.oneplus.net/threads/solution-bricked-oneplus-one-recovery.306306/
EDIT: It seems you will need fastboot image of oxygenos and list of partitions ... anyway, good luck
Click to expand...
Click to collapse
It probably isn't the smartest idea in the world to recommend using a recovery tool from for an entirely different device unless you're 100% sure it's safe, which it probably isn't.
Heisenberg said:
It probably isn't the smartest idea in the world to recommend using a recovery tool from for an entirely different device unless you're 100% sure it's safe, which it probably isn't.
Click to expand...
Click to collapse
It's Qualcomm tool, but sadly OP2 is new device and there are no guides specific to OP2. He probably can resurrect his phone using QHSUSB_BULK device(*1)
EDIT: (*1) - It depends on correct driver and firmware files (images)
yanick76 said:
It's Qualcomm tool, but sadly OP2 is new device and there are no guides specific to OP2. He probably can resurrect his phone using QHSUSB_BULK device(*1)
EDIT: (*1) - It depends on correct driver and firmware files (images)
Click to expand...
Click to collapse
Yes, I'm aware that there is nothing specific available for the OP2. My point is that you're not even sure if this isn't going to damage the device further, let alone even help in any way.
Heisenberg said:
Yes, I'm aware that there is nothing specific available for the OP2. My point is that you're not even sure if this isn't going to damage the device further, let alone even help in any way.
Click to expand...
Click to collapse
His device is almost dead and this kind of damage is not covered by warranty. I think in this situation is not much to lose
Just to assure you that the hard brick issue on OPT is completely curable since I've revived two OPTs. No panic needed. I will update the complete procedure as well as the necessary files later today.
yanick76 said:
His device is almost dead and this kind of damage is not covered by warranty. I think in this situation is not much to lose
Click to expand...
Click to collapse
His device is not almost dead, it's in a bricked "like" state right now but it can be easily fixed with the correct tool. What you're suggesting is not the correct tool for this device at all. If you're comfortable with being so reckless with someone else's device, good for you, I'm certainly not.
Heisenberg said:
His device is not almost dead, it's in a bricked "like" state right now but it can be easily fixed with the correct tool. What you're suggesting is not the correct tool for this device at all. If you're comfortable with being so reckless with someone else's device, good for you, I'm certainly not.
Click to expand...
Click to collapse
Yes I understand you but my post was meant as suggestion to way how to fix it, not guide. If you think my post can lead him to kill his device you can delete my post (because I can't), I have no problem with it
yanick76 said:
Yes I understand you but my post was meant as suggestion to way how to fix it, not guide. If you think my post can lead him to kill his device you can delete my post (because I can't), I have no problem with it
Click to expand...
Click to collapse
I know you were trying to help, but that advice is the wrong advice. I don't want/need to delete your post. My point here is to try to help you to understand why giving advice when you're not 100% understanding the situation properly isn't a great idea. On a site like this, accuracy and knowledge are paramount because it can be the difference between helping someone revive their device or completely killing it.
mG!X said:
Hi all
I bought the oneplus 2 4 days ago.
I rooted it, installed twrp and flashed nethunter2.0 CM12 then wiped cache , well the flash didn't go very successfully as the os still oxygen but i had all applications from nethunter installed and fully functional.
I decided to use the nethunter installer provided by the official site but not including the onplus2 version, i included the custom rom in replacement of the choosed one
.. but accidentally in the process of this tool it flashed stok for nexus which completely bricked the phone... nothing works, not boot no charge no sound...
I plugged again the phone and pressed for 20 seconds the power + volume up button and i got the bulk usb driver as it was a oneplus one .. i changed the driver settings to accept the unsigned drivers and updated the unkown device to the qualcomm 9008 ( as it was like a oneplus one ) .
The issue is that oneplus two has a Qualcomm MSM8994 Snapdragon 810 and the version i found for ColorOS is only for MSM8794 .. so i couldn't do anything
please can anyone help me?
any hint please?
Thank you in advance
Click to expand...
Click to collapse
Tutorial posted here http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
Heisenberg said:
I know you were trying to help, but that advice is the wrong advice. I don't want/need to delete your post. My point here is to try to help you to understand why giving advice when you're not 100% understanding the situation properly isn't a great idea. On a site like this, accuracy and knowledge are paramount because it can be the difference between helping someone revive their device or completely killing it.
Click to expand...
Click to collapse
From this point I agree it was wrong advice.
I hope I never will be in situation like this But if, I will try to fix it based on what I suggest him + hours of google for correct files, correct drivers and correct download tool. I think this "misunderstood" was based on my advice like "here is direction and google for more", this is forum if he can find answer himself (google) he need not to ask for help here
Is there a procedure out there to run LOS with a locked bootloader?
You can't
koftheworld said:
Is there a procedure out there to run LOS with a locked bootloader?
Click to expand...
Click to collapse
No and don't try. You can get back to stock and relock with MiFlash though, so even if your screen breaks or somesuch you should be able to fix it
Choose an username... said:
No and don't try. You can get back to stock and relock with MiFlash though, so even if your screen breaks or somesuch you should be able to fix it
Click to expand...
Click to collapse
Thanks. I've done do on other phones, but I wanted to make sure here. I tried before I posted and got a boot loop. I didn't try flashing the stock recovery before hand, but I'm guessing it would be a bust as well. Thank you again for your answer.
koftheworld said:
Thanks. I've done do on other phones, but I wanted to make sure here. I tried before I posted and got a boot loop. I didn't try flashing the stock recovery before hand, but I'm guessing it would be a bust as well. Thank you again for your answer.
Click to expand...
Click to collapse
Did you recover from that? A lot of people did that and had to return it to ZTE. They change A2017Gs for free if it doesn't show the unlocked bl screen though (a.k.a if ir's blackscreened). just say it's not your fault
Choose an username... said:
Did you recover from that? A lot of people did that and had to return it to ZTE. They change A2017Gs for free if it doesn't show the unlocked bl screen though (a.k.a if ir's blackscreened). just say it's not your fault
Click to expand...
Click to collapse
Yeah it was pretty easy. I booted into that fix all recovery mode and installed a stock image through the mi recovery program. This is my first time with a ZTE phone, but have been with Moto since the og. Screwing with phones and recovering from bricks is part of the experience.
koftheworld said:
Yeah it was pretty easy. I booted into that fix all recovery mode and installed a stock image through the mi recovery program. This is my first time with a ZTE phone, but have been with Moto since the og. Screwing with phones and recovering from bricks is part of the experience.
Click to expand...
Click to collapse
Oh yeah, but on Motorolas (and some Samsungs, and some other oems) you have anti-bricking measures in place. I had a moto g2, damn near unbrickable. but here you don't have that, and you can DFU brick the phone. Look up the '4th category brick repair manual' and tell me if you still want to screw with the phone...
I got there, had to do the whole process. I even broke a couple of legs of the USB/vibrator module but everything works anyways (seems that the connector has 2 legs for each wire - i broke 2 unrelated) and touched something else while shorting the testpad for the 50th time -sparks flied and all- but it's working just as well as before. It's not impossible to recover from a brick but before doing anything (stupid or not) read everything there is to read about that. Don't do things that you could do on other phones...
Choose an username... said:
Oh yeah, but on Motorolas (and some Samsungs, and some other oems) you have anti-bricking measures in place. I had a moto g2, damn near unbrickable. but here you don't have that, and you can DFU brick the phone. Look up the '4th category brick repair manual' and tell me if you still want to screw with the phone...
I got there, had to do the whole process. I even broke a couple of legs of the USB/vibrator module but everything works anyways (seems that the connector has 2 legs for each wire - i broke 2 unrelated) and touched something else while shorting the testpad for the 50th time -sparks flied and all- but it's working just as well as before. It's not impossible to recover from a brick but before doing anything (stupid or not) read everything there is to read about that. Don't do things that you could do on other phones...
Click to expand...
Click to collapse
Well understood. I'm back unlocked on Los and staying that way. Thanks again.
Yes folks,
As I said, I discovered SUPER BRICK, TOTAL BRICK, COMPLETE FAILURE or whatever yoy want to name this new brick. It has been like this: I was following the instructions to update oreo in HONOR 8 LITE, at the end I had to write some codes in twrp (advance / terminal ...) so it was starting to do the last update (sd card update.zip) and by accident I touched the screen where it appears: REBOOT, so the phone restarted but the screen is not working when it tries to enter erecovery mode, so here is the list of my problems:
- it does not work: erecovery (so I can not recover the phone)
- fastboot works: when I install something (twrp or firmware, I have tried everyone of them) the phone does not start
- if I try to go to TWRP (after installing an oreo one): the screen seems to break and you can not see anything
Please, my phone is 2 months old, man I need to make it work again, I need it.
Help help help
You should post this in Honor 8 lite forum ...
But whatever, you said that fastboot works if so you can try to use huawei update extractor and flash system,boot,recovery,cust that *should* work
Nikola6511 said:
You should post this in Honor 8 lite forum ...
But whatever, you said that fastboot works if so you can try to use huawei update extractor and flash system,boot,recovery,cust that *should* work
Click to expand...
Click to collapse
I wrote it down here because it is fully compatible and there are more roms here than the honor 8 lite forum, that´s why, it was not a mistake it is because I am desperate.
I can not install BOOT, I have tried and it does not work, anyways I need help.
Thanks in advance
alopez_666 said:
I wrote it down here because it is fully compatible and there are more roms here than the honor 8 lite forum, that´s why, it was not a mistake it is because I am desperate.
I can not install BOOT, I have tried and it does not work, anyways I need help.
Thanks in advance
Click to expand...
Click to collapse
Sry i didnt know its the same.
What error do you get when you try to flash boot.img?
Nikola6511 said:
Sry i didnt know its the same.
What error do you get when you try to flash boot.img?
Click to expand...
Click to collapse
I finally installed BOOT properly, but the problem is that I have inside the phone OREO SYSTEM and I can not find BOOT in the updates I am downloading, as I said, once BOOT was installed, it did not work because it came form nougat.
Phone is very dead.
alopez_666 said:
I finally installed BOOT properly, but the problem is that I have inside the phone OREO SYSTEM and I can not find BOOT in the updates I am downloading, as I said, once BOOT was installed, it did not work because it came form nougat.
Phone is very dead.
Click to expand...
Click to collapse
This may be a stupid question..
If i understood correctly, you can install Boot from nougat, right?
If so why dont you flash nougat rom again?
Nikola6511 said:
This may be a stupid question..
If i understood correctly, you can install Boot from nougat, right?
If so why dont you flash nougat rom again?
Click to expand...
Click to collapse
I have tried nougat and oreo, but nothing happens, after I install them the phone starts and suddendly it stays as the picture attached.
I tell you something: I used emui erecovery to get everything back but now it does not work anymore, my phone is dead
alopez_666 said:
I have tried nougat and oreo, but nothing happens, after I install them the phone starts and suddendly it stays as the picture attached.
I tell you something: I used emui erecovery to get everything back but now it does not work anymore, my phone is dead
Click to expand...
Click to collapse
Im really sorry i cant help
There is a way to fix that.. but... Its too complicated and hard to do..
Since your phone is new, you probably dont want to buy new.
This is going to cost you a bit.
First you will need to find honor 8 lite or p8 lite (if you say they are the same)
that is well.. dead, open it take out a memory chip on both phone and place chip from dead phone to yours. If you dont know how to do that take it to the repair shop and they should know how to do that.
As i sad its very hard and it costs, but it works if done properly.
I saved my friends phone like that, idk what he did but phone wasnt visible in adb, fastboot and recovery didnt work just blue screen.
Note:
This needs to be done very carefully or ypur phone will be 100% dead
alopez_666 said:
I have tried nougat and oreo, but nothing happens, after I install them the phone starts and suddendly it stays as the picture attached.
I tell you something: I used emui erecovery to get everything back but now it does not work anymore, my phone is dead
Click to expand...
Click to collapse
I think your EMMC memory might be fried
Nikola6511 said:
Im really sorry i cant help
There is a way to fix that.. but... Its too complicated and hard to do..
Since your phone is new, you probably dont want to buy new.
This is going to cost you a bit.
First you will need to find honor 8 lite or p8 lite (if you say they are the same)
that is well.. dead, open it take out a memory chip on both phone and place chip from dead phone to yours. If you dont know how to do that take it to the repair shop and they should know how to do that.
As i sad its very hard and it costs, but it works if done properly.
I saved my friends phone like that, idk what he did but phone wasnt visible in adb, fastboot and recovery didnt work just blue screen.
Note:
This needs to be done very carefully or ypur phone will be 100% dead
Click to expand...
Click to collapse
What about using DC PHOENIX???? What do you think????
alopez_666 said:
What about using DC PHOENIX???? What do you think????
Click to expand...
Click to collapse
Idk I never tried it, but it costs and it's not guaranteed it will work but it's worth a try
---------- Post added at 09:55 PM ---------- Previous post was at 09:46 PM ----------
If I understood correctly it will flash any file no matter what so technically it should work
Nikola6511 said:
Idk I never tried it, but it costs and it's not guaranteed it will work but it's worth a try
---------- Post added at 09:55 PM ---------- Previous post was at 09:46 PM ----------
If I understood correctly it will flash any file no matter what so technically it should work
Click to expand...
Click to collapse
DC Phoenix worked fine, it's been awesome, I installed the rom and my phone is alive, I wonder: why I couldn't do it with ADB? Why this software is so powerful? And finally, why nobody is making kind of software like this for free? I mean, dc phoenix must be like the software that Huawei technicians use in their lab and samsung has ODIN that is so powerful as well and is free.
Anyway, if anybody has a problem as mine, you have to pay but it has solution. By the way, I went to tech service and they did not do anything because I bought my phone in China and they could not touch more than european phones, but they told me something that made me think that my trouble had a solution: rewrite the rom and that point convinced me that DC Phoenix would work, and so did it. Thank you all for the info.
Same for me, how to fix please. Bricked following this "guide"
https://www.haky86.com/2018/05/12/install-emui-8-0-huawei-p8-lite-2017/
I was on official Emui Nougat, wanted Oreo, forced update with nocheck, everything is broke except fastboot.
When I want to flash his OreoTWRP.img with "fastboot flash recovery_ramdisk /path/to/img" it work but can't reboot to recovery.
I press Power + Vol+ but it reboot "phone untrusted" with Vol+ for going to eRecovery (usualy it's here you can shutdown the phone) but error mode.
Maybe the OreoTWRP work after my command but can't boot into it. Please help.
alopez_666 said:
DC Phoenix worked fine, it's been awesome, I installed the rom and my phone is alive, I wonder: why I couldn't do it with ADB? Why this software is so powerful? And finally, why nobody is making kind of software like this for free? I mean, dc phoenix must be like the software that Huawei technicians use in their lab and samsung has ODIN that is so powerful as well and is free.
Anyway, if anybody has a problem as mine, you have to pay but it has solution. By the way, I went to tech service and they did not do anything because I bought my phone in China and they could not touch more than european phones, but they told me something that made me think that my trouble had a solution: rewrite the rom and that point convinced me that DC Phoenix would work, and so did it. Thank you all for the info.
Click to expand...
Click to collapse
Bro my P8lite is also bricked, I accidentally wiped the EMMC then I showed it to a repairer and he somehow took me to fastboot mode, now I can't flash anything because that repairer has partitioned the EMMC and now it is showing 486mb total storage so no ROM is flashing because of size. Can you please give me your USERNAME and PASSWORD of DC Pheonix as you've already bought it. It will solve my issue and it will also save me some money.... I will be very thankful to you....
WAITING FOR A POSITIVE REPLY.
I bought it some time ago and it was a 72 hours license and it expired so I do not have anything from that situation. I will check my computer but I will not probably find anything.
alopez_666 said:
I have tried nougat and oreo, but nothing happens, after I install them the phone starts and suddendly it stays as the picture attached.
I tell you something: I used emui erecovery to get everything back but now it does not work anymore, my phone is dead
Click to expand...
Click to collapse
Hello just looking at that pic is enough. That happens cause you installed the wrong firmware. Either get a proper nougat rom for your device and install boot, recovery and system images from fastboot or a oreo version. Either way that screen means its the wrong firmware version or wrong zone. for example you can be trying to install a europe rom in a asian device. hope this helps
legionfx said:
Hello just looking at that pic is enough. That happens cause you installed the wrong firmware. Either get a proper nougat rom for your device and install boot, recovery and system images from fastboot or a oreo version. Either way that screen means its the wrong firmware version or wrong zone. for example you can be trying to install a europe rom in a asian device. hope this helps
Click to expand...
Click to collapse
Problem was solved, I used DC Phoenix and installed a rom, but I did it some time ago. Thanks anyway
Hello everyone, that's it. I have a Redmi 2 enhanced version (2014811) . It can be turned on now but it keeps restarting as soon as it enters the first page. Now it can enter the fastboot mode. How can I save it? (The phone should not be rooted before)
Postscript: If possible, can I take this opportunity to use a third party ROM to upgrade to a higher version of Android? (e.g. Android 10 or higher）
Thank you for your comments, thank you very much ! ! !
Deleted.
LR7875 said:
If you know how to use fastboot, try installing TWRP. (Execute command fastboot flash recovery twrp.xxx.img where twrp.xxx.img is the filename of twrp placed into the fastboot folder on your computer. If you don't understand ask me further.)
Wingtech Redmi 2
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
Then wipe> factory reset in twrp
Then flash this rom
[ROM][11.0][UNOFFICIAL][wt88047x] LineageOS 18.1
Important information: This thread is for LineageOS 18.1 opensource builds for Wingtech WT88047, marketed as Redmi 2 by Xiaomi. The following will not be supported in this thread: Custom Kernels Mods Modified system files Xposed Magisk What's...
forum.xda-developers.com
Click to expand...
Click to collapse
First of all, thank you very much for your advices, bro! Do I need to unlock/root first before installing TWRP? Because I have not been rooted it before, can I just flash in TWRP directly under the fastboot environment without rooting? Sorry, I still don't know how to do it, maybe some concepts have not been figured out yet. .....
If the phone is stock and not rooted a factory reset should restore it.
You will lose all data.
It may be possible to start it and get it to run stabily in Safe mode, if so it's a 3rd party startup app causing it. Find it...
blackhawk said:
If the phone is stock and not rooted a factory reset should restore it.
You will lose all data.
It may be possible to start it and get it to run stabily in Safe mode, if so it's a 3rd party startup app causing it. Find it...
Click to expand...
Click to collapse
I'm afraid that during the entire flashing process, some things have been done wrong and cannot be remedied in the future. Are there any basic tutorials on flashing that I can learn?
Sorry, sent the wrong post. Try factory resetting in miui recovery mode. If it still not boots, your phone is permanently fried on the motherboard level.
2021redmi2fans said:
I'm afraid that during the entire flashing process, some things have been done wrong and cannot be remedied in the future. Are there any basic tutorials on flashing that I can learn?
Click to expand...
Click to collapse
I apologize that no, you will need to get into system and sign into your mi account in order to unlock the bootloader and allow you to flash anything, which you cannot do as for now.
LR7875 said:
I apologize that no, you will need to get into system and sign into your mi account in order to unlock the bootloader and allow you to flash anything, which you cannot do as for now.
Click to expand...
Click to collapse
He should be able to reflash the stock rom though, right?
LR7875 said:
Sorry, sent the wrong post. Try factory resetting in miui recovery mode. If it still not boots, your phone is permanently fried on the motherboard level.
Click to expand...
Click to collapse
It doesn’t matter, the problem is that I don’t know how to enter the miui recovery mode......
2021redmi2fans said:
It doesn’t matter, the problem is that I don’t know how to enter the miui recovery mode......
Click to expand...
Click to collapse
Whatever button sequence is used for that device.
Timing is everything, keep trying until you get it.
It's harder to do when you really need to
Take a break and make sure you got the right sequence/timing.
If it's booting up to the Home page it's salvageable I think... better than a boot loop.
However, before the loop occurs, Mokee 7.1.2 was installed and used it normally for a period of time, does that matter?
blackhawk said:
Whatever button sequence is used for that device.
Timing is everything, keep trying until you get it.
It's harder to do when you really need to
Take a break and make sure you got the right sequence/timing.
If it's booting up to the Home page it's salvageable I think... better than a boot loop.
Click to expand...
Click to collapse
Bro really thank you
2021redmi2fans said:
Bro really thank you
Click to expand...
Click to collapse
Stock Androids are easy, that's one reason I run stock. The only thing that really kills them is an outright hardware failure.
blackhawk said:
Stock Androids are easy, that's one reason I run stock. The only thing that really kills them is an outright hardware failure.
Click to expand...
Click to collapse
redmi 2 runs on stock rom android 4.2 right? you can not install any single app on that.
when the op fixed it it is advised to install a custom rom.
Hi, I was just wondering if anyone can help me. I know it's a lost cause at this point cuz it was my fault but I managed to get my phone to get bricked as I was trying to flash newer firmware for the phone. It succeeded without issues but when it rebooted it never wants to turn on. I've checked with an ampmeter and it's only drawing little power. It does try to boot but it thinks it doesn't have any firmware on it if that makes sense. I can't get it to EDL or even diagnostic mode.
Note:
Running Pixel Experience 12
Android 11 firmware (Tried to update to 12 for 5g modem)
Any sort of help or info would be appreciated cuz I'm pretty devastated from my mistake
Thank you
Note: I've realised that the video didn't load so here is the link of my trying to power it on to EDL Mode
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
If you flashed the wrong images via fastboot you killed your phone.
xtcislove said:
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
If you flashed the wrong images via fastboot you killed your phone.
Click to expand...
Click to collapse
I was flashing the firmware that was from the official OTA firmware and it just decide to crap itself. I have assumed and probably will think that the device is fried cuz of the memory confusion.
Rain_- said:
I was flashing the firmware that was from the official OTA firmware and it just decide to crap itself. I have assumed and probably will think that the device is fried cuz of the memory confusion.
Click to expand...
Click to collapse
Its not a problem if you flash it as local upgrade inside OOS but it can be a problem if you flash it via fastboot
Were you able to fix this somehow?
hello, did you solve your problem? Or did you change your motherboard? I'm having the same problem right now and I don't know what to do
Had my motherboard replaced by OnePlus service.
7bob said:
Had my motherboard replaced by OnePlus service.
Click to expand...
Click to collapse
hello, is your device working now? How much did the service charge?
x_files_X said:
hello, is your device working now?
Click to expand...
Click to collapse
Yes
x_files_X said:
How much did the service charge?
Click to expand...
Click to collapse
Depends on the country and RAM / ROM size, see here https://www.oneplus.com/support/repair-pricing/details?code=25 or https://www.oneplus.com/support/repair-pricing
Rain_- said:
Hi, I was just wondering if anyone can help me. I know it's a lost cause at this point cuz it was my fault but I managed to get my phone to get bricked as I was trying to flash newer firmware for the phone. It succeeded without issues but when it rebooted it never wants to turn on. I've checked with an ampmeter and it's only drawing little power. It does try to boot but it thinks it doesn't have any firmware on it if that makes sense. I can't get it to EDL or even diagnostic mode.
Note:
Running Pixel Experience 12
Android 11 firmware (Tried to update to 12 for 5g modem)
Any sort of help or info would be appreciated cuz I'm pretty devastated from my mistake
Thank you
Note: I've realised that the video didn't load so here is the link of my trying to power it on to EDL Mode
Click to expand...
Click to collapse
Rain_- said:
Hi, I was just wondering if anyone can help me. I know it's a lost cause at this point cuz it was my fault but I managed to get my phone to get bricked as I was trying to flash newer firmware for the phone. It succeeded without issues but when it rebooted it never wants to turn on. I've checked with an ampmeter and it's only drawing little power. It does try to boot but it thinks it doesn't have any firmware on it if that makes sense. I can't get it to EDL or even diagnostic mode.
Note:
Running Pixel Experience 12
Android 11 firmware (Tried to update to 12 for 5g modem)
Any sort of help or info would be appreciated cuz I'm pretty devastated from my mistake
Thank you
Note: I've realised that the video didn't load so here is the link of my trying to power it on to EDL Mode
Click to expand...
Click to collapse
Bro just use msm tool that will fix it anyways