I think my phone has HARD BRICK.
Let you know: my phone was charging, so whatsapp stop to work, and i restart the phone, so my phone starts a infinity loop and fist screen - 1+ Android.
I try MSMdownloadTool, and doesn't work. Cache.img failed, or Memory Size/Wait Device.
I try all usb ports on my pc.
Can you help me?
rodymcbr said:
I think my phone has HARD BRICK.
Let you know: my phone was charging, so whatsapp stop to work, and i restart the phone, so my phone starts a infinity loop and fist screen - 1+ Android.
I try MSMdownloadTool, and doesn't work. Cache.img failed, or Memory Size/Wait Device.
I try all usb ports on my pc.
Can you help me?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
If possible you can send it to me for repairing I can make a youtube video on it.
If possible you can send it to me for repairing I can make a youtube video on it. Once it's get fixed will ship you back this phone. If you think this is an good idea let's talk and will tell you what to do?
Try using a tool specially for flashing stock / undoing softbricks to flash stock os, if that doesn't work try manually flashing all of the images in the correct order but do not flash the cache.img if you want to keep the original storage space on your device.
If this fails, do a full wipe of everything on the phone besides internal storage using twrp (I assume you have it installed, if you don't if you have unlocked bootloader run fastboot in CMD and do fastboot flash recovery twrp.img then boot to the newly installed twrp) and wipe everything but USB otg and internal storage, after this flash the stock images using fastboot or TWRP if you choose (I personally wouldn't recommend flashing recoveries or vendor / system images with TWRP as this has causes softbricks for me in the past)
And if that doesn't work, wipe absolutely everything on the phone using twrp including internal storage and then flash the system images using the unbrick tool and if that doesn't succeed flash them using fastboot.
Here is a link to the unbricking tool for OnePlus 5T: https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
Sumitsingh247 said:
If possible you can send it to me for repairing I can make a youtube video on it. Once it's get fixed will ship you back this phone. If you think this is an good idea let's talk and will tell you what to do?
Click to expand...
Click to collapse
Do not send your phone to this guy, he sounds suspicious he will likely steal your phone + low amount of thanks.
My friend I am full time hardware repair guy and part time have you tube channel.
Hey Tnt_
This is Sumit Singh from New Delhi India. I have repair shop in delhi and have seen lots of cases like this. I have some spare dead phones Oneplus 5t. Part time I make YouTube videos for my clients and people living abroad who do not find solution for such problems. Bricking is not only the case of software failure it’s also damage the boot IC some time power capacitor which generates the boot sequence power. I try to help this guy and earn some royalty. As far as concern I am sound suspicious please check YouTube there are so many you tubers help people like I do. Giving free advices sometime make the situation worst so please before advice do your complete research. And if I am suspicious to then I am sorry at least by my ID you know my name but I don’t know what is TNT name stands for? Thanks for your time and before make any suggestions please do a proper research thank you.
TnT_ said:
Try using a tool specially for flashing stock / undoing softbricks to flash stock os, if that doesn't work try manually flashing all of the images in the correct order but do not flash the cache.img if you want to keep the original storage space on your device.
If this fails, do a full wipe of everything on the phone besides internal storage using twrp (I assume you have it installed, if you don't if you have unlocked bootloader run fastboot in CMD and do fastboot flash recovery twrp.img then boot to the newly installed twrp) and wipe everything but USB otg and internal storage, after this flash the stock images using fastboot or TWRP if you choose (I personally wouldn't recommend flashing recoveries or vendor / system images with TWRP as this has causes softbricks for me in the past)
And if that doesn't work, wipe absolutely everything on the phone using twrp including internal storage and then flash the system images using the unbrick tool and if that doesn't succeed flash them using fastboot.
Here is a link to the unbricking tool for OnePlus 5T: https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
Do not send your phone to this guy, he sounds suspicious he will likely steal your phone + low amount of thanks.
Click to expand...
Click to collapse
Related
Hey boss., after flashing open beta 12, the phone started hanging now and then. I tried to contact oneplus forums and they asked me to send the log files. Since they took too long to respond, I went to oneplus service centre. They flashed my phone with old oxygen os and the phone didn't start. It went into bootloop
Then I asked them, they said motherboard is corrupted. I left the place and I requested online customer support from oneplus. They too flshed and concluded the same. Can I know whether flashing/sideloading openbeta created this issue? If so, can you provide me support to avail the warranty on the phone? or recover it via any other method or process?
Please respond as soon as possible. My communication with the world has become limited after this issue. I hope there is some sort of support.
Also note that, the phone can boot into fastboot mode, but bootloader is locked. It can boot into recovery. I tried wiping everything, but the phone is not rebooting.
When I start the phone, it stucks in the boot logo and after a while, the screen becomes blank and a white color notification LED is glowing.
Kindly help me.
i had the same issue last week after updating to 13..and i tried to flash the black theme..it went black..i had nothing....it was like it was bricked... here's how after many failed attempt's..i had to clean out all files including backups.wipe data i had to wipe system i had to clean out all previous files.from TWRP recovery.then i had to download the latest software release then put the zip file in my phone storage not in the download file ..then i had to flash stock recovery.then install the new system..and i made the mistake of trying to use some of my app backups like for one estrong file ..all of them were corrupt.so start fresh.
You might try this unbricking method:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Though your device isn't hard-bricked, this would reset your device to the absolute factory settings (watch out, your data will be erased) on an older OxygenOS version.
I would recommend the 2nd Method, as it restores all partitions to factory settings.
I might also know where your issue came from:
Though you can flash the Open Beta (or any other ZIP from OnePlus) through the Stock Recovery, OnePlus states that you need to be on an unlocked bootloader for not bricking your device.
TimSchumi said:
You might try this unbricking method:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Though your device isn't hard-bricked, this would reset your device to the absolute factory settings (watch out, your data will be erased) on an older OxygenOS version.
I would recommend the 2nd Method, as it restores all partitions to factory settings.
I might also know where your issue came from:
Though you can flash the Open Beta (or any other ZIP from OnePlus) through the Stock Recovery, OnePlus states that you need to be on an unlocked bootloader for not bricking your device.
Click to expand...
Click to collapse
It worked, but no network connection or wifi connection!
Is there a way to bring them back?
SivaMaxwell said:
It worked, but no network connection or wifi connection!
Is there a way to bring them back?
Click to expand...
Click to collapse
You might try to unlock your bootloader (There are giudes to do this) and flash a OxygenOS package from oneplus.net through the stock recovery, to ensure the firmware is OK (Do a factory reset from recovery!). I don't know if the Unbrick Tool only restores corrupted partitions or all. It might have installed the wrong system over your previously installed firmware if only corrupted partitions are restored. Keep the bootloader unlocked to be on the safe side (After some time you will be able to just ignore the boot message and you have better access to fastboot and recovery)!
Also, GG to OnePlus for (fake) Motherboard corruption!
About warranty:
Warranty should be ok as long as you won't do hardware modifications (I think).
Bootloader unlocking is definitely safe
TimSchumi said:
You might try to unlock your bootloader (There are giudes to do this) and flash a OxygenOS package from oneplus.net through the stock recovery, to ensure the firmware is OK (Do a factory reset from recovery!). I don't know if the Unbrick Tool only restores corrupted partitions or all. It might have installed the wrong system over your previously installed firmware if only corrupted partitions are restored. Keep the bootloader unlocked to be on the safe side (After some time you will be able to just ignore the boot message and you have better access to fastboot and recovery)!
Also, GG to OnePlus for (fake) Motherboard corruption!
About warranty:
Warranty should be ok as long as you won't do hardware modifications (I think).
Bootloader unlocking is definitely safe
Click to expand...
Click to collapse
I tried to update to recent oxygen os. Then the original proble started again.
It is not booting up, again..
SivaMaxwell said:
I tried to update to recent oxygen os. Then the original proble started again.
It is not booting up, again..
Click to expand...
Click to collapse
No, reflash the OxygenOS package of the same Version that is installed by the Unbrick Tool (If you can still get itfrom oneplus.net) and then check if Network does work. Also, check your IMEI.
I think you might have a corrupted EFS partition. That's y you don't have a working network. Check whether your device show a IMEI under about phone.
m4manusraj said:
I think you might have a corrupted EFS partition. That's y you don't have a working network. Check whether your device show a IMEI under about phone.
Click to expand...
Click to collapse
EFS doesn't have an effect on WiFi.
That's why I think that it is a firmware issue
I think, I have solved it guys. I'll let you know once completely under control
So, Thank you very much for your support. With this little support from you and my previous Foresightedness helped me restore the phone.
So just in case if any one else faces the same or similar problem, this is the process:
STEP0: If there is any partition corrupted, the device don't boot properly. And, The customer care/ sevice centre guys state it as motherboard problem. Donot Panic. Always take TWRP backup whenever you change your ROM. This Backup helps you to restore whenever you're in trouble. In this particular case, ESF backup is required. So, take a complete backup (everything) in TWRP, it saves your ass.. keep the backup in your PC or any safe Storage (the complete TWRP Folder which is in Internal Memory) before flashing any custom ROM.
Step1: Follow method2 in this guide: https://forums.oneplus.net/threads/g...plus-3.452634/
Step2: if everything is alright, its done. Otherwise, The device boots up with some missing features and details. At this time, you have to unlock the bootloader. See The forum to know how to do it. Basic searching can give you the method.
If you can transfer the TWRP folder from PC to Phone, it's good. But the phone boots itself because of missing firmware. Even Bluetooth couldn;'t be used.
In my particular case, I couldnot copy from PC to mobile or viceversa. So, you cannot copy back your TWRP folder in this situation.
So, Unlock bootloader. Then reboot to system (without doing anything)
Step3: Reboot to bootloader and flash TWRP 3-0.2 version only. otherwise device will be encrypted.
Step4: download Ressurection Remix ROM version : ResurrectionRemix-M-v5.7.4-20161113-PUBLIC-ex-oneplus3 or you can experiment with any other custom ROM but only android 6 (*Marshmallow). Also make sure that you have universal adb drivers. install them if not (search in the forums.)
Step5: goto TWRP recovery, in this, goto wipe option. Drag the swipe to wipe button here. (normal wipe).
Step6: Now, in advanced options, select adb sideload option and select the two wipes in the next menu. Start ADB sideload in the TWRP.
Step7: Now, Start the adb sideloading the custom ROM from your PC. You donot Require Gapps for transferring a file. So donot flash Gapps.
Step8: After the sideload is complete, reboot into system. Now you can transfer files between phone and PC. Now, Copy the Complete TWRP folder into the internal memory. A pop-up asks for merging the folders. Allow the merging, even if you have another TWRP backup there. They don't overlap.
Step9: Now, Boot into TWRP and restore completely. The phone boots up properly, this time. Everything works as expected. every mysterious problem is solved. Now you will get update request if you are on previous version of OOS.
Last but not Least: Please do not use any app recovery tools. they may cause issues while following the above steps
Thank to every XDA member, helping us save the time and money we spend at service center.
m4manusraj said:
I think you might have a corrupted EFS partition. That's y you don't have a working network. Check whether your device show a IMEI under about phone.
Click to expand...
Click to collapse
TimSchumi said:
EFS doesn't have an effect on WiFi.
That's why I think that it is a firmware issue
Click to expand...
Click to collapse
Yes, boss. The EFS is corrupted. But, thanks to TWRP, it also has the option to backup EFS, modem. SO, I used my old backup from Jan2017 to restore it back.
But, TO place TWRP back in phone, the original OOS3.1.2, even after reflashing didn't support. I thought for a while and flashed the All loved RR (MM) . THen, it gave me the scope to t/f the folder to internal memory.
Now, I restored the EFS , Modem, sytem with data. and hell yea!! the phone is back to life.
Complete Backup, Atleast once for 3 months saves your ass..
I am glad it helped. That's the power of Xda.
My OP3 is stuck on the boot animation only while booting up Oxygen OS. At first I thought it was bricked but as I proceeded I found out that it isn't and i'm able to boot other OS on it. I've had Resurrection Remix which I had no problems flashing whatsoever. But I'm having this problem with Oxygen OS. Has anyone experienced this? What do I do? Please help.
Expert advice needed please. This is a puzzle that someone might enjoy solving.
Although I have a fair bit of experience with flashing, I tried to flash my 8.0 for the first time and it has dramatically failed. It was probably my fault - not an uncommon story.
What is less common is that I am struggling to figure out how to undo the damage I've done. What's really making this difficult is that no computer recognises the device as USB any more so I can't use Odin, Kies, etc to repair or return to stock. I have tried everything I can think of to deal with the USB issue, the usual cable, driver, port nonsense. I don't think the USB problem is Windows now.
I suspect one of these things may have happened:
The USB port just went bad coincidentally during this flash process (charge, no data). I have ordered a new port but it will take weeks to arrive.
Has the device come out of Developer/USB debugging mode somehow? I can't tell because I can't boot to an OS.
I wonder if the ROM flash has corrupted the firmware the deals with USB - is that possible? Where is the devices USB drivers located? Is it in the bootloader, something like BIOS?
I'm suspicious of the bootloader, as the screen is weirdly corrupted now when I turn on or reboot the device - fuzzy white lines rather than a logo - but that disappears when OS tries to load, or I go into Recovery/Download.
I actually did do a backup of the original ROM to the SD card; but restoring it doesn't work, just produces an endless Samsung boot, even if I then wipe and reset.
I can get into Download mode, and a Recovery (Philz for N5120) but since I can't connect to the devise with USB in any way, it's very hard to get the Recovery to flash anything new and useful. I did put my SD Card in another phone and copied over the stock ROM zip from Samsung, but it refuses to flash - I think because it doesn't like Philz Recovery? I can't think how to replace Philz Recovery with another by flashing, without USB.
I may have to wait to replace the USB port, but I fear that won't fix it. Until then, I can only think of one other thing to try, and that is to copy a ROM onto the SD Card through another phone, and try to flash it. Lineage doesn't flash, and nor does the stock zip I got from Samsung. Would anything else work?
Can I flash an alternative recovery from within the recovery? Philz only lets me flash zips, not img or tars.
So it's quite a mess, but if anyone has a brilliant idea of how to get out of this, I'd love to hear it.
THANK YOU if you have a genius idea.
So after a few days of working on this, I did manage to resolve it, and I thought I'd just add a note about how I escaped this obscure problem.
The device went bad because I stupidly flashed an incompatible Recovery to the device and somewhere between doing this, backup and restoring and flashing, it corrupted mostly everything including something in the bootloader.
Oddly enough, the solution seemed to be to mess up the Recovery even more by flashing something even more random - it seems this provoked the device into restoring its own basic Recovery. Using this to wipe and reset the device somehow enabled Download mode's USB interface to start working again so I was able to use Kies to return to stock, which repaired everything including the bootloader.
Finally, I flashed the correct Recovery for this device, and then managed to flash the ROM I wanted. A happy ending to a stressful story; the device now works better than it ever has done before.
i bricked my moto z play. i somehow after many days got twrp on the phone. since the phone is encrypted i had many issues. anyway got it installed. my system as far as i could tell did not exist. i put sept.zip on a flash drive and connected it and it was there under usb otg. so i installed it. the fie appears to be on the system. (i saw it in the files twrp has). but i cannot get it to work. i reboot it. and back to twrp. PLEASE HELP!!!!
I think you need to flash the official software through fastboot and get back to stock Nougat somehow. Try booting into fastboot iff you can do that its not bricked. Bricked means when the phone is off and doesnt respongd or switch on at all.
Iff. you can get into fastboot you can reinstall the official nougat software and there are guides somewhere on this forum how to do that.
You have twrp, download and install the rom from here https://forum.xda-developers.com/moto-z-play/development/rom-nov-patch-npns26-118-22-2-8-t3717037
You'll lose everything on your phone, but if it's not booting now anyway....
punkerEVO said:
You'll lose everything on your phone, but if it's not booting now anyway....
Click to expand...
Click to collapse
Usually it is not necessary to lose anything.
First: use twrp to do backup of data. Don't forget data/media which is not included, there are your photos.
Second: flash the ROM you want, but omit the command "erase userdata". Then your data should (!) survive.
I recently found a moto g5 in one of my fellow "old tech" drawers and decided to turn it on, it was on the
1. May 2018
Security patch on nougat, I decided to use the inbuilt system updater to go to Oreo, and now....it crashes during flashing process after about 25-30% completion,
Now im guessing boot or System is not properly installed due to the zip file having aborted mid-flash
Recovery doesn't properly boot as that is used to install the update and thus imidiately goes to doing that
Also, it hang up during installation on random times, it basically has a record of 2mins of not crashing whilst still being stuck on 30%
I got it to "boot" when trying factory mode, yeah it crashed mid boot animation...not a help
Any suggestions? EDL mode maybe?
Can you not flash firmware via fastboot
In theory as long as firmware is signed you don't need an unlocked bootloader to flash firmware
Firmware can be downloaded from https://mirrors.lolinet.com/firmware/moto/cedric/official/
You can also try the lenovo moto smart assistant to flash the firmware
https://forum.xda-developers.com/g5/how-to/guide-how-download-official-fastboot-t3916778
If not you will most likely need a motherboard replacement or jtag firmware flash at a repair shop
TheFixItMan said:
Can you not flash firmware via fastboot
In theory as long as firmware is signed you don't need an unlocked bootloader to flash firmware
Firmware can be downloaded from https://mirrors.lolinet.com/firmware/moto/cedric/official/
You can also try the lenovo moto smart assistant to flash the firmware
https://forum.xda-developers.com/g5/how-to/guide-how-download-official-fastboot-t3916778
If not you will most likely need a motherboard replacement or jtag firmware flash at a repair shop
Click to expand...
Click to collapse
SOMEHOW it just decided to boot, I have never seen such behaviour, even on my g5s which I had for a while, (and am currently daily driving to school if it wasn't closed....NEVER
Maybe I'll unlock it and try somehow recreating it? Well it's in physically rough shape but all components inside are fine...so that can't be the reason....?
My g5 got stuck in a bootloop without an update, no root or anything modded. Is there any way to recover the data if its stuck like this?
anonymous724 said:
My g5 got stuck in a bootloop without an update, no root or anything modded. Is there any way to recover the data if its stuck like this?
Click to expand...
Click to collapse
Flash the stock rom and boot the device. But this will format the device.
To save data, remove the command fastboot erase userdata
Fastboot erase customisation.
Apps may be gone, but files In internal storage will be safe, like download,photos, music.
riyan65 said:
Flash the stock rom and boot the device. But this will format the device.
To save data, remove the command fastboot erase userdata
Fastboot erase customisation.
Apps may be gone, but files In internal storage will be safe, like download,photos, music.
Click to expand...
Click to collapse
no luck on this front, gets to the passcode screen, write in passcode then motorola logo shows and screen keeps on turning off and on.
Thanks for the effort though, much appreciated
Mine is similar to yours. Initially was on permanent loop of the following:
1. Boot to moto g splash screen... Repeat
2. Boot to lock screen then usually a few loops of 1. (after entering the patter or left Idle)
The phone initially didnt have any developer options enabled.
I wiped cache using recovery mode. Restarted and pretty much the same thing except that it would on rare occasions actually fully boot up usually only last a few minutes before cycling between steps 1 and 2 above.
I used those rare boot ups to backup all files and enable any USB debugging /oem unlock (incase I need to use a solution dependent on these being enabled.)
Factory resetted it and its still the same with the random successful boot amongst the numerous failed ones.
I managed to hook it up to Lenovo's Lmsa and flash the latest ROM. Now I get a lot more successful boots but still loops every so often. The downside is that I can no longer do any functions that make use of the audio/ mic/ video (can take pictures). If I do then it will crash and loop.
The hardware test on the LMSA passed for every component before flashing to the latest version. Post update it predictably fails on the audio/ mic components.
I guess I'll have to go back to the old version to see I get the audio back.
Hi guys,
I have a problem with a Xiaomi 10T Pro. It is in bootloop. The reason for that is unknown (it’s a friend’s phone). The phone settings are basically all standard, meaning the bootloader is locked, stock recovery and stock OS. I can access recovery and fastboot. Safe boot and repair boot out of recovery does nothing. It is just showing the MIUI logo as during the normal boot.
Is there any way to copy the data of the phone (photos would be enough)?
I read about flashing just the boot.img of the firmware but I don’t know which version is running. I am assuming the newest one that come with OTA updates.
I also read that some people wiped the data in recovery (only full wipe possible in stock recovery) and then used some android data recovery software to recover their data.
Not very satisfying options. I would really appreciate a different way. Any ideas?
My first idea was to boot into TWRP but because of the locked bootloader this is not possible.
sexler said:
Hi guys,
I have a problem with a Xiaomi 10T Pro. It is in bootloop. The reason for that is unknown (it’s a friend’s phone). The phone settings are basically all standard, meaning the bootloader is locked, stock recovery and stock OS. I can access recovery and fastboot. Safe boot and repair boot out of recovery does nothing. It is just showing the MIUI logo as during the normal boot.
Click to expand...
Click to collapse
Note that this may be a hardware problem.
As the bootloader is locked, you can only try to erase the data and see if the phone restarts, which is not certain and then try with recovery software, also not certain.
Or before erase the data, this tool:
https://www.xiaomitool.com/V2/
Choose "my device is bricked"
Also without warranty.
I have Ur same exact issue xD been like that for months
NOSS8 said:
Note that this may be a hardware problem.
As the bootloader is locked, you can only try to erase the data and see if the phone restarts, which is not certain and then try with recovery software, also not certain.
Or before erase the data, this tool:
https://www.xiaomitool.com/V2/
Choose "my device is bricked"
Also without warranty.
Click to expand...
Click to collapse
Thank you for your reply.
I haven’t found a different solution yet so despite the fact that this method is not certain I guess I’ll try it in the next couple of days. Before that I’ll also give this Xiaomi tool a try.
Do you know some good data recovery tools that I could use if the device will boot?
sexler said:
Thank you for your reply.
I haven’t found a different solution yet so despite the fact that this method is not certain I guess I’ll try it in the next couple of days. Before that I’ll also give this Xiaomi tool a try.
Do you know some good data recovery tools that I could use if the device will boot?
Click to expand...
Click to collapse
Never had to try to recover my data on a smartphone, sorry.