32gb variant (H790).
I tried most of the solutions I've seen on this subforum so far - including doing a full flash-all.sh command as well as the flashing of individual files into my system.
So far I've been able to do so using the stock images from Google (Android N). However, I can never get Recovery to boot and my phone will not boot past "Google." (Not even the colorful animations show).
I am not sure what I can do - I unfortunately got this phone via a 3rd party and not Google's Store, so I'm not sure if they would honor an RMA request (maybe if I said it was a gift they would relent?).
I was reading this thread: http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740 and realized that this might be my last alternative, but I'm a bit concerned about going through all of this without giving it one more chance having access to at least the bootloader screen.
Does anyone have any suggestions on what I might be doing wrong? Should I attempt to flash the latest Android 6.0 image instead?
Is your boot loader locked? How did you flash the stock images?
Reboot into fastboot, run the flash all, reboot back to your bootloader when it's done and it. These commands....
Fastboot format cache
Fastboot format userdata
Then restart the phone
Corrupted bootloader partition, your phone is little piece of brick. EXT4 is the motive, HAHAHA.
I lost a ****ty device like you too.
Now i learned: (IF IS EXT4 , NO!)
Sent from my XT687 using xda premium
I am able to unlock bootloader. I flashed using both flash all as well as individual img at a time like described in this: http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
I ran format cache and userdata (which I think the full flash also does). I am unable to go past the Google screen.
I was able to reflash my rom again too, without errors, but the **** recused to boot up or boot recovery, your phone is death like the apocalyptical beast google inc!
Sent from my XT687 using xda premium
dcxgod said:
I am able to unlock bootloader. I flashed using both flash all as well as individual img at a time like described in this: http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
I ran format cache and userdata (which I think the full flash also does). I am unable to go past the Google screen.
Click to expand...
Click to collapse
Can you get TWRP installed via fastboot and boot into that?
Sent from my Nexus 5X using Tapatalk
Use the lg tot file method to recover. It has worked for some.
Sent from my Nexus 5X using Tapatalk
Try to flash TWRP with fasboot and see if you can boot it. There's an actual problem with the last versions of TWRP (TWRP 3.0.2-1 and 3.0.2-2), where if you backup then restore an EFS partition you end up with a phone where it doesn't get past the Google Screen (or crashes in the first frame of the bootanimation), lk panic apparently due to EFS corruption.
If this is your case (derped restoring EFS like that) and you can flash and boot on TWRP, try to flash TWRP 3.0.2-0 and restore and old backup of EFS.
maybe same problem
I have the same problem.
Before i flash manually my phone into android 7(factory image) it was rooted and unlock bootloader. I locked the bootloader again and until here everything works fine. I flashed the stock recovery mode by TWRP. after that the phone won't boot android and stock recovery mode. everything was lost except the bootloader.
I tried lots of tricks but don't answer(sideload ota update, format cache and userdata). I tried to flash stock recovery or custom recovery but i couldn't because in the process the phone restart and restart again and again. Even doesn't work temporarily boot, custom and stock recovery mode and phone has no reaction.
I only have access to the bootloader.
Would you have any suggestion?
*ps: When phone is boot up just shows a white google logo and after that shows a green bot with red alert and a message(no command) . In this point phone restart suddenly and the same process is repeated.
Related
I woke up today to a bootloop. After pulling out the battery, I cant turn it on, it was stuck at the google logo. I thought it was some rom issue or something. When I had the time, in the afternoon, I just boot to recovery, and wiped data+sd card. Turns out sd card was not wiped.
Just now, I found a way to boot it. (AFTER WIPING DATA) I used the gnex toolkit and boot with insecure image, and guess wat? My old rom boots. Everything was the way it was, and then it crashed and stuck on the google logo again.(I made sure i wiped things two to three times, data and sd) I did a few experiments:
1) Flash using ODIN
2) Flash CWM using toolkit--it changed back to twrp after reboot
3) Changing the icon on my homescreen after boot--- everything was the same again after booting
4) Flash stock image using toolkit
5) Wipe data using manual adb
6) Try to lock my bootloader
Everything I tried changing, change back to the original state after reboot. What is the problem?
Device: Galaxy Nexus
ROM: Purity 7 sept release
Kernel: Fancy r42
Logs in twrp are showing updating partition, not FAIL. So I really don't think there is a need to show the recovery log.
HELP ME!
are you flashing your recovery or just booting the recovery?
fastboot oem unlock
fastboot flash recovery recovery.img
use ClockWorkMod. I've heard nothing but problems with TWRP.
player911 said:
are you flashing your recovery or just booting the recovery?
fastboot oem unlock
fastboot flash recovery recovery.img
use ClockWorkMod. I've heard nothing but problems with TWRP.
Click to expand...
Click to collapse
umm, i can boot recovery. i cannot flash cwm. i tried, but when i reboot, it went back to twrp.
what is oem unlock for? coz its smth i havent tried.
jacktay94 said:
umm, i can boot recovery. i cannot flash cwm. i tried, but when i reboot, it went back to twrp.
what is oem unlock for? coz its smth i havent tried.
Click to expand...
Click to collapse
Oem unlock will unlock your bootloader and wipe the internal storage in the process. I saw you didn't use fastboot. You could try that. Flash the Factory image via fastboot. If that fails try omap flash.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
Oem unlock will unlock your bootloader and wipe the internal storage in the process. I saw you didn't use fastboot. You could try that. Flash the Factory image via fastboot. If that fails try omap flash.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Yup,I tried it already thru toolkit. Not working either.
Dude the toolkit blows, flash back to stock manually via adb command prompt. There are tutorials around here on how to do it. It's guaranteed to work if you don't screw it up.
Honestly flashing back to stock via adb should be something everyone should learn if you plan on flashing roms.
SoHaunted said:
Dude the toolkit blows, flash back to stock manually via adb command prompt. There are tutorials around here on how to do it. It's guaranteed to work if you don't screw it up.
Honestly flashing back to stock via adb should be something everyone should learn if you plan on flashing roms.
Click to expand...
Click to collapse
i did adb bro, its the last thing i tried, i learnt and try.
Sent to Samsung centre, they told me its my flash IC thats blown. sobs
I got myself into trouble and I hope that someone who knows more than me can answer two questions.
Background:
I bought a new Nexus 7 2013 WIFI (razor / flo). I loaded TWRP recovery, and rooted the device. I decided to encrypt the drive, but TWRP doesn't appear able to do that (when the device reboots to start encryption, it just boots normally into Android). However it does appear that TWRP can mount an encrypted drive, so I decided to flash stock recovery to do the encryption and then reflash with TWRP.
Problem 1:
I accidentally flashed with the wrong stock image. I used the image for the Nexus 7 2013 Mobile (razorg / deb). The flash-all.sh script includes a step for flashing the radio (fastboot flash radio radio-deb-deb-g00_2.37.0_1024.img). It executed the command without error, but I don't think there is a radio partition on this device. Does anyone know if there is a radio partition to control the GPS, WIFI, and/or NFC? Should I do something to undo this problem? I cannot find a radio firmware for this device, and the WIFI and GPS appear to work fine so perhaps I should just move on.
Problem 2:
Even when I use the stock recovery image for the correct device, it does not appear to load correctly. fastboot runs without errors, but when I boot into recovery I get the unconscious android with the red exclamation in his tummy. I have done a full wipe of all partitions, and a full restore. Based on my search in the forums, this appears to be a common problem but the suggested solutions don't seem to apply to my device. Any suggestions?
I should note that re-installing TRWP works fine, and I was able to restore my data from a backup. But I can't encrypt the device or install future updates until I can roll back to the stock restore image.
Thank you in advance for your help.
resplin said:
I got myself into trouble and I hope that someone who knows more than me can answer two questions.
Background:
I bought a new Nexus 7 2013 WIFI (razor / flo). I loaded TWRP recovery, and rooted the device. I decided to encrypt the drive, but TWRP doesn't appear able to do that (when the device reboots to start encryption, it just boots normally into Android). However it does appear that TWRP can mount an encrypted drive, so I decided to flash stock recovery to do the encryption and then reflash with TWRP.
Problem 1:
I accidentally flashed with the wrong stock image. I used the image for the Nexus 7 2013 Mobile (razorg / deb). The flash-all.sh script includes a step for flashing the radio (fastboot flash radio radio-deb-deb-g00_2.37.0_1024.img). It executed the command without error, but I don't think there is a radio partition on this device. Does anyone know if there is a radio partition to control the GPS, WIFI, and/or NFC? Should I do something to undo this problem? I cannot find a radio firmware for this device, and the WIFI and GPS appear to work fine so perhaps I should just move on.
Problem 2:
Even when I use the stock recovery image for the correct device, it does not appear to load correctly. fastboot runs without errors, but when I boot into recovery I get the unconscious android with the red exclamation in his tummy. I have done a full wipe of all partitions, and a full restore. Based on my search in the forums, this appears to be a common problem but the suggested solutions don't seem to apply to my device. Any suggestions?
I should note that re-installing TRWP works fine, and I was able to restore my data from a backup. But I can't encrypt the device or install future updates until I can roll back to the stock restore image.
Thank you in advance for your help.
Click to expand...
Click to collapse
Flash the wifi factory image. I assume you're talking about flashing in adb. Once you flash the correct image it should all be good. I've never even tried to encrypt the drive so can't offer any help there. If you use flash-all you will need to reflash TWRP afterwards then SuperSu.
Still no stock recovery
wantabe said:
Flash the wifi factory image. I assume you're talking about flashing in adb. Once you flash the correct image it should all be good. I've never even tried to encrypt the drive so can't offer any help there. If you use flash-all you will need to reflash TWRP afterwards then SuperSu.
Click to expand...
Click to collapse
Thank you for trying to point me in the right direction, but I had already tried your suggestions.
The link you shared is for the official distribution of twrp. I tried it, and though it flashes fine, it did not help me return to the stock recovery.
I have been flashing the stock recovery from developers.google.com/android/nexus/images. It flashes without error, but when I try to boot to recovery I get the sick android (red exclamation mark). This happens whether I flash just the recovery image, or do a flashall, or an update.
I have been using fastboot instead of adb to flash the images.
Any ideas on why after flashing the stock recovery I cannot boot into it?
resplin said:
Thank you for trying to point me in the right direction, but I had already tried your suggestions.
The link you shared is for the official distribution of twrp. I tried it, and though it flashes fine, it did not help me return to the stock recovery.
I have been flashing the stock recovery from developers.google.com/android/nexus/images. It flashes without error, but when I try to boot to recovery I get the sick android (red exclamation mark). This happens whether I flash just the recovery image, or do a flashall, or an update.
I have been using fastboot instead of adb to flash the images.
Any ideas on why after flashing the stock recovery I cannot boot into it?
Click to expand...
Click to collapse
I'm sorry about the link, not that it does any good now but the link is corrected. Using fastboot to flash the images is correct, I too often use adb as a generic term for both. When you boot into the stock recovery you will see the android with the exclamation mark and that is normal. Finally got the new 2012 N7 I bought as a gift and was updating it. Been a while since I've booted into a stock recovery. So... Boot into stock recovery, when the Android with the red exclamation mark appears, hold down power first, followed quickly by volume up. You should now see the recovery menu. Whoop, Whoop! :laugh:
It works!
Thank you very much for your patient explanation. That helps a lot.
I hadn't realized that there was an additional step after the display of the warning android in order to enter stock recovery. All that time I spent trying to fix something that wasn't broken! <sigh>
I was unable to get the device to display the stock recovery menu, because it appears to require a very precise timing (I just keep rebooting it back to the system by accident). However, encryption did work fine. My confusion with the encryption was compounded by the fact that encryption of the Nexus 7 in 4.4 doesn't always work the first time (see this thread at android central: forums.androidcentral.com/google-nexus-7-tablet-2013/337078-experiencing-difficulty-encrypting-my-2013-n7-after-4-4-build-krt16s-upgrade.html). After trying 4 times in a row, the device encrypted. I was then able to put Team Win Recovery back on the device, and everything works perfectly.
Thank you again for your help. I don't see how to mark the thread as solved, but I am glad that everything appears to work now.
My device decided to randomly encrypt itself after using the CM12 port that is available. How this happened is beyond me. Anyhow, I tried to do a factory reset... Nothing would mount because the device was encrypted. So, I thought it would be a great idea to flash a different recovery. By now, I have flashed over 6 recovery images (all different) even the stock. Fastboot says that the transfer went through successfully only to find when I try to boot into recovery, it boots into fastboot instead.
Yes the device is unlocked.
I don't know if there is a ROM on it, but when i try to start it normally, it wont boot past the splash screen (before the boot animation)
Please help, as this is the only phone I am stuck with for a long time
Here's a thread with people that have a similar problem. There are some suggestions of what to do in there, but personally none of them worked for me. I ended up having to send it back to Amazon.
iananderson said:
Here's a thread with people that have a similar problem. There are some suggestions of what to do in there, but personally none of them worked for me. I ended up having to send it back to Amazon.
Click to expand...
Click to collapse
Thank you. Still no success :/
BLEXXAR said:
My device decided to randomly encrypt itself after using the CM12 port that is available. How this happened is beyond me. Anyhow, I tried to do a factory reset... Nothing would mount because the device was encrypted. So, I thought it would be a great idea to flash a different recovery. By now, I have flashed over 6 recovery images (all different) even the stock. Fastboot says that the transfer went through successfully only to find when I try to boot into recovery, it boots into fastboot instead.
Yes the device is unlocked.
I don't know if there is a ROM on it, but when i try to start it normally, it wont boot past the splash screen (before the boot animation)
Please help, as this is the only phone I am stuck with for a long time
Click to expand...
Click to collapse
Never factory restore when you have a Custom ROM as it isn't made to reset with the devices stock hardware and causes things to go crazy.
Always use a nandroid of the original system with root, then unroot, then factory restore from that.
Also. YouTube search - HTC Desire 816 root unlock bootloader.
Use the .exe recovery from that video in fastboot at least twice without exiting fastboot or rebooting.
Now try the recovery.
Sent from my 710C using XDA Free mobile app
Didn't work. Thanks though.
BLEXXAR said:
Didn't work. Thanks though.
Click to expand...
Click to collapse
When you were on the stock recovery, could you wipe partitions?
Also what model do you have?
My phone started acting really laggy today and began restarting by this evening. The restarts became more and more frequent and now I can't do anything with it. The phone is unlocked and was rooted with xposed. I can get into the bootloader and fastboot works fine. I cannot, however, get into recovery. The phone displays the unlocked warning, then the Google screen with the unlocked symbol on the bottom, and then it repeats.
Through fastboot, I flashed the newest update without wiping my data - didn't work. Then I extracted the zip file and flashed everything (radio, bootloader, recovery, system, etc..) and no change. I repeated the process with an older version just to see if there was a difference.. nope. Everything installs just fine but I get the same bootloop and inability to get into recovery. I also flashing TWRP, but no change.
Am I screwed? I voided my warranty when I unlocked the bootloader, right?
redg8gt said:
My phone started acting really laggy today and began restarting by this evening. The restarts became more and more frequent and now I can't do anything with it. The phone is unlocked and was rooted with xposed. I can get into the bootloader and fastboot works fine. I cannot, however, get into recovery. The phone displays the unlocked warning, then the Google screen with the unlocked symbol on the bottom, and then it repeats.
Through fastboot, I flashed the newest update without wiping my data - didn't work. Then I extracted the zip file and flashed everything (radio, bootloader, recovery, system, etc..) and no change. I repeated the process with an older version just to see if there was a difference.. nope. Everything installs just fine but I get the same bootloop and inability to get into recovery. I also flashing TWRP, but no change.
Am I screwed? I voided my warranty when I unlocked the bootloader, right?
Click to expand...
Click to collapse
Curious, what happens if you flash recovery.img into the boot partition?
It's a nexus device so you should be ok with warranty and an unlocked bootloader.
Sent from my Nexus 9 using XDA Free mobile app
redg8gt said:
My phone started acting really laggy today and began restarting by this evening. The restarts became more and more frequent and now I can't do anything with it. The phone is unlocked and was rooted with xposed. I can get into the bootloader and fastboot works fine. I cannot, however, get into recovery. The phone displays the unlocked warning, then the Google screen with the unlocked symbol on the bottom, and then it repeats.
Through fastboot, I flashed the newest update without wiping my data - didn't work. Then I extracted the zip file and flashed everything (radio, bootloader, recovery, system, etc..) and no change. I repeated the process with an older version just to see if there was a difference.. nope. Everything installs just fine but I get the same bootloop and inability to get into recovery. I also flashing TWRP, but no change.
Am I screwed? I voided my warranty when I unlocked the bootloader, right?
Click to expand...
Click to collapse
try clean flashing a stock image in fastboot. wipe everything.
k.s.deviate said:
try clean flashing a stock image in fastboot. wipe everything.
Click to expand...
Click to collapse
I manually flashed everything that the flash-all.bat file does, twice. I'm going to try to get it replaced with the warranty.
I can't help but think it is a hardware problem given that everything seems to work perfectly flashing it with factory images and then nothing happens when I try to boot it up.
sfhub said:
Curious, what happens if you flash recovery.img into the boot partition?
Click to expand...
Click to collapse
... is this different than flashing using fastboot? I flashed the stock recovery several times and redownloaded and tried again. TWRP didn't work either.
redg8gt said:
... is this different than flashing using fastboot? I flashed the stock recovery several times and redownloaded and tried again. TWRP didn't work either.
Click to expand...
Click to collapse
What I was suggesting is
fastboot flash boot recovery.img
previously you would have been trying
fastboot flash boot boot.img
fastboot flash recovery recovery.img
I was suggesting flashing your boot partition using the recovery.img on the assumption that the recovery partition emmc might be damaged along with parts of the user partition.
If the boot partition area of the emmc is still good, flashing the recovery.img in there will allow recovery to startup.
Recovery and boot are basically 95% the same image. The partitions sizes are the same. So basically from a flashing standpoint, they are interchangeable.
The difference is the boot partition is automatically selected by the boot loader, while the recovery partition needs special button presses to start.
If you flash the boot partition with the recovery.img, then recovery should just start up automatically without special button presses.
sfhub said:
What I was suggesting is
fastboot flash boot recovery.img
previously you would have been trying
fastboot flash boot boot.img
fastboot flash recovery recovery.img
I was suggesting flashing your boot partition using the recovery.img on the assumption that the recovery partition emmc might be damaged along with parts of the user partition.
If the boot partition area of the emmc is still good, flashing the recovery.img in there will allow recovery to startup.
Recovery and boot are basically 95% the same image. The partitions sizes are the same. So basically from a flashing standpoint, they are interchangeable.
The difference is the boot partition is automatically selected by the boot loader, while the recovery partition needs special button presses to start.
If you flash the boot partition with the recovery.img, then recovery should just start up automatically without special button presses.
Click to expand...
Click to collapse
I think you mean fastboot boot recovery.img. Not fastboot flash boot recovery.img. That'll hopefully boot you into recovery without actually flashing it.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I think you mean fastboot boot recovery.img. Not fastboot flash boot recovery.img. That'll hopefully boot you into recovery without actually flashing it.
Click to expand...
Click to collapse
Nope, I actually meant what I wrote. I wanted to test the theory that the emmc in the recovery partition is damaged and the easiest way to do that is to flash the recovery onto the boot partition, which might not be damaged.
The partitions are the same size so you won't damage the phone, you'll just cause the phone to boot the kernel which autostarts recovery instead of the kernel that tries to boot android.
fastboot boot recovery.img will just load recovery straight into memory across the USB cable. It won't allow diagnosis of whether the emmc in that section is damaged.
Ok, but if the EMMC is bad in any partition the device is still hosed.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Ok, but if the EMMC is bad in any partition the device is still hosed.
Click to expand...
Click to collapse
Actually that isn't necessarily true. While Emmc can have catastrophic failure, Emmc often has partial failure.
We discovered this when google added SecureTRIM to the kernel on the Samsung Epic Touch. The emmc was getting corrupted by this change and we found that we could lock out certain sections of the emmc by adjusting partition tables and have a functioning phone.
I figure this phone is going back for RMA anyway, so might as well get some useful failure analysis out of it.
redg8gt said:
My phone started acting really laggy today and began restarting by this evening. The restarts became more and more frequent and now I can't do anything with it. The phone is unlocked and was rooted with xposed. I can get into the bootloader and fastboot works fine. I cannot, however, get into recovery. The phone displays the unlocked warning, then the Google screen with the unlocked symbol on the bottom, and then it repeats.
Through fastboot, I flashed the newest update without wiping my data - didn't work. Then I extracted the zip file and flashed everything (radio, bootloader, recovery, system, etc..) and no change. I repeated the process with an older version just to see if there was a difference.. nope. Everything installs just fine but I get the same bootloop and inability to get into recovery. I also flashing TWRP, but no change.
Am I screwed? I voided my warranty when I unlocked the bootloader, right?
Click to expand...
Click to collapse
Try to do a factor oem lock and then unlock to completely wipe the phone , then try to adb sideload stock 6.0.1 ?
okay here's what you need to do:
1) Try the LG UP tool. There's a thread somewhere in 5x forums. 90% chances are that it will fix everything as it repartitions back to stock.
2) If the above does not work, then do this: Download the platform tools, shift right click, open command prompt, switch off the phone, connect it to pc and power on. Once you are past the google logo, type adb devices, it should show up there on the pc, if it doesn't then try the command again. once the device shows up on the command prompt, type adb logcat, once you have around 3-4 minutes of boot up logs on the cmd, copy everything and post it here, one of us will take a look and tell you what exactly is the problem.
Here is the link, http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740. Member bitdomo has been a savior on many nexus devices.
Sent from my Nexus 9 using XDA Free mobile app
The phone is indeed heading back to Google for a (refurb) replacement. I had tried to directly boot into recovery using both the stock recovery and twrp and had the same result. For the sake of science, I will try the LG tool later and see if I can get it working.
sfhub said:
What I was suggesting is
fastboot flash boot recovery.img
previously you would have been trying
fastboot flash boot boot.img
fastboot flash recovery recovery.img
I was suggesting flashing your boot partition using the recovery.img on the assumption that the recovery partition emmc might be damaged along with parts of the user partition.
If the boot partition area of the emmc is still good, flashing the recovery.img in there will allow recovery to startup.
Recovery and boot are basically 95% the same image. The partitions sizes are the same. So basically from a flashing standpoint, they are interchangeable.
The difference is the boot partition is automatically selected by the boot loader, while the recovery partition needs special button presses to start.
If you flash the boot partition with the recovery.img, then recovery should just start up automatically without special button presses.
Click to expand...
Click to collapse
I just tried this. Still bootloops.
Siddheshpatil said:
okay here's what you need to do:
1) Try the LG UP tool. There's a thread somewhere in 5x forums. 90% chances are that it will fix everything as it repartitions back to stock.
2) If the above does not work, then do this: Download the platform tools, shift right click, open command prompt, switch off the phone, connect it to pc and power on. Once you are past the google logo, type adb devices, it should show up there on the pc, if it doesn't then try the command again. once the device shows up on the command prompt, type adb logcat, once you have around 3-4 minutes of boot up logs on the cmd, copy everything and post it here, one of us will take a look and tell you what exactly is the problem.
Click to expand...
Click to collapse
1) I think I'm going to keep it broken so there is no issue whenever I send it in. I wish I would have waited to call Google. I'm curious now whether that would have worked.
2) There is no past the Google logo.. it resets before it gets past it.
redg8gt said:
I just tried this. Still bootloops.
Click to expand...
Click to collapse
Could you try 2 other things
1) try the fastboot boot recovery.img suggested earlier to confirm your recovery image can boot across USB cable
2) if not, please post a SHA1 hash for your recovery.img and which Android version you got the image from
This will just confirm that the recovery image that you are using is bootable in absence of the EMMC and if not, confirm whether the recovery.img is corrupted or not.
I experienced something similar when I moved from MM to N without wiping data. The data partition got encrypted even though I flashed that fedpatcher. Just couldn't get into twrp beyond its splash screen. The issue here might be unrelated, but I'd suggest a format userdata.
I got this problem a month ago , tried wiping everything and flash stock using fastboot command , then i got 9008 mode .
No recovery no downloads mode no fastboot . (Sometimes can go to fastboot try flash using nrt / manually , nothing happend)
Long story short, I made my phone bricked with a small mistake:
I had Freedom OS (latest build) and then tried to flash Miui rom. To do so, I needed to flash back to official Hygrogen/Oxygen OS (MM). The mistake I made was to lock bootloader first. Then, phone got into bootloop....I searched and found Qualcomm software can revive any Qualcomm phone. I downloaded Qualcomm app and driver for Oneplus 3 and tried reviving my phone....What happened finally was that the phone was restarted and a screen showing Cache failed, System failed, userdata failed appeared. I tried to find Cache, system img ...of OOS 4.02 to flash separately....while I couldn't find them anywhere...I just tried fastboot flashing a recovery (both official and TWRP) but got error that partition doesn't allow writing (I guess because phone is locked now)....anyway, phone can boot only in fastboot and I wonder what else I can do....
Any help is very much appreciated!
alireza.nasibi said:
Long story short, I made my phone bricked with a small mistake:
I had Freedom OS (latest build) and then tried to flash Miui rom. To do so, I needed to flash back to official Hygrogen/Oxygen OS (MM). The mistake I made was to lock bootloader first. Then, phone got into bootloop....I searched and found Qualcomm software can revive any Qualcomm phone. I downloaded Qualcomm app and driver for Oneplus 3 and tried reviving my phone....What happened finally was that the phone was restarted and a screen showing Cache failed, System failed, userdata failed appeared. I tried to find Cache, system img ...of OOS 4.02 to flash separately....while I couldn't find them anywhere...I just tried fastboot flashing a recovery (both official and TWRP) but got error that partition doesn't allow writing (I guess because phone is locked now)....anyway, phone can boot only in fastboot and I wonder what else I can do....
Any help is very much appreciated!
Click to expand...
Click to collapse
Try this method now it will work
https://forum.xda-developers.com/showpost.php?p=68245482&postcount=111
The point is I can't flash anything on any partition as phone is locked and can't be unlocked!
alireza.nasibi said:
The point is I can't flash anything on any partition as phone is locked and can't be unlocked!
Click to expand...
Click to collapse
If you can access fastboot mode then you can definitely flash by other method
abhi0502 said:
If you can access fastboot mode then you can definitely flash by other method
Click to expand...
Click to collapse
you mean the 2nd method?
You said you lock the bootloader in 5th line, in order to flash any recovery you need to unlock bootloader again.
I also tried to lock bootloader last week and then my op3 got bricked with bootloop.
-First get into fastboot and unlock bootloader this will wipe your all data including you saved ROM files.
- after this flash TWRP or OnePlus recovery and sideload OOS ROM. Or transfer the ROM file using mtp in TWRP recovery.
- then you can easily do anything you want. Don't relock bootloader.
Those red things on your screen basically means your phone misses partitions, without these partitions it doesn't boot duhh.
If method 2 of the unbrick tool doesn't work, you can manually flash those files in Fastboot, the program has a folder that has all partitions like, cache.img, boot.img etc. I've been here as well nothing to worry about just keep us updated so we can help you
There's no mention in your post on which unbrick method you used. Was it first or second? By the looks of the end result, it was the first.
Just follow the same steps, but use method 2, that should leave you with a phone like out of the factory. Afterwards, you can simply set it up and let it update through OTA if you want to remain stock, or simply unlock bootloader, flash TWRP and flash whatever you want.
use the second method. the file you have to download contains all the raw room and when you follow the process, it would work. happened to me two times and i used this method
Just simply use fastboot oem unlock in fastboot mode then flash a recovery via fastboot flash recovery then go to recovery and once wipe all the partions and install a rom and then tried booting
Thank you all for your time and support. Method 2 saved my phone!