Please Help! Can't boot into ROM or Recovery - Nexus 6P Q&A, Help & Troubleshooting

Hello, I am not a noob and I have been rooting phones for quite a while!
I was on an Android N ROM, WETA and tupac, with TWRP 3.0.2-1 working just fine.. all of a sudden I couldn't boot into recovery or into my ROM.. so I decided to say screw it and booted into bootloader and used fastboot commands to stock MTC20F.. flashed all of it except userdata, but I did format userdata at the end. I then rebooted the phone and I still cannot get past the Google logo.. it just reboots the phone everytime.. Not sure where I went wrong but being on Project Fi, I can't just go into a store and get a new phone.. So I a have a big issue right now and have no idea where something went wrong.. I would greatly appreciate some help or guides of how to go about fixing this.. I don't know why but normally fastboot always fixes my issue!!

sorry i did not read fully,
your pc does not recognize the phone during the boot at all?

There are some ongoing issues with reverting back from N to MM..... Not sure if you are faced with the same issue or not, but I know a few people are in your boat, with no resolution at this time.
Heisenberg said:
[SIZE=+1]14. How To Update To Android 7.0 Nougat[/SIZE]
....
....
Please note: If you decide to upgrade to Nougat, at this stage you cannot return to Marshmallow. Trying to downgrade to MM has seen multiple bricks occur. I don't know why this is happening but it's happening.
Click to expand...
Click to collapse

Please join this thread to help troubleshoot.

Related

Certain Roms will not boot anymore?

As of yesterday my phone stopped booting certain roms! Im rooted with all the latest twrp, vendor, bootloader, etc. I never encountered this problem and Ive been rooted since day one. I have several custom roms on my phone and only "Resurrection Rom" seems to boot without any problem all the other (Purenexus, benzorom, chroma, exdous) Roms get past the google screen and stay stuck in the boot up screen.. Am I missing something?? Ive checked everything I could. Ive downgraded twrp. Im stump any insight on this would be greatly appreciated..
Info
big nu said:
As of yesterday my phone stopped booting certain roms! Im rooted with all the latest twrp, vendor, bootloader, etc. I never encountered this problem and Ive been rooted since day one. I have several custom roms on my phone and only "Resurrection Rom" seems to boot without any problem all the other (Purenexus, benzorom, chroma, exdous) Roms get past the google screen and stay stuck in the boot up screen.. Am I missing something?? Ive checked everything I could. Ive downgraded twrp. Im stump any insight on this would be greatly appreciated..
Click to expand...
Click to collapse
check Kernel compatibility if you update internal rom
- reinstall kernel
:good:
big nu said:
As of yesterday my phone stopped booting certain roms! Im rooted with all the latest twrp, vendor, bootloader, etc. I never encountered this problem and Ive been rooted since day one. I have several custom roms on my phone and only "Resurrection Rom" seems to boot without any problem all the other (Purenexus, benzorom, chroma, exdous) Roms get past the google screen and stay stuck in the boot up screen.. Am I missing something?? Ive checked everything I could. Ive downgraded twrp. Im stump any insight on this would be greatly appreciated..
Click to expand...
Click to collapse
Same with me dude
https://tapatalk.com/shareLink?url=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php?t=3357580&share_tid=3357580&share_fid=3793&share_type=t
Here's my thread... I have tried everything even going back to stock MHC19Q and starting fresh... RIP 6P
MoistPicklez said:
Same with me dude
https://tapatalk.com/shareLink?url=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php?t=3357580&share_tid=3357580&share_fid=3793&share_type=t
Here's my thread... I have tried everything even going back to stock MHC19Q and starting fresh... RIP 6P
Click to expand...
Click to collapse
Never figured anything out? I think im having this same issue with my 6p i tried flashing pure nexus, xTraFactory, and Stock+ but for me it just bootloops and once out of 20 attemps pure nexus will get to the colored logo then freeze and reboot. I long deleted Ressurrection Remix because it was my daily driver and already had a backup made. That went to sh*t though when my backup bootlooped as well so now i have a 6p i can only boot into recovery and bootloader. My laptop with fastboot installed needs a new charger so i use my moms computer to put zips on my phone but i really doubt she will let me install anything on it at all :/. I dont want to flash the factory image and bootloop still though when i get a charger. Ill see if I can boot back into rros fresh.
Coeur Brisé said:
Never figured anything out? I think im having this same issue with my 6p i tried flashing pure nexus, xTraFactory, and Stock+ but for me it just bootloops and once out of 20 attemps pure nexus will get to the colored logo then freeze and reboot. I long deleted Ressurrection Remix because it was my daily driver and already had a backup made. That went to sh*t though when my backup bootlooped as well so now i have a 6p i can only boot into recovery and bootloader. My laptop with fastboot installed needs a new charger so i use my moms computer to put zips on my phone but i really doubt she will let me install anything on it at all :/. I dont want to flash the factory image and bootloop still though when i get a charger. Ill see if I can boot back into rros fresh.
Click to expand...
Click to collapse
Well this is quite an old post to awaken but to be short and Frank I had to send my device in to have the motherboard replaced because the 6p still has hardware issues whether it's Huawei's (prolly spelled wrong.) fault or Google's, regardless I just got the motherboard replaced and sold the device immediately because I didn't want to have another paper weight in my hands I now have an essential phone and it is dare I say the most comfortable phone I've ever had. That being said I hope you can Rectify your issues here but you'll have to go through either Huawei or Google, and get one of the two to help you out with a replacement.
This kind of happened to me too. I just updated TWRP and all flash are fine now. Hope this will help someone
MoistPicklez said:
Well this is quite an old post to awaken but to be short and Frank I had to send my device in to have the motherboard replaced because the 6p still has hardware issues whether it's Huawei's (prolly spelled wrong.) fault or Google's, regardless I just got the motherboard replaced and sold the device immediately because I didn't want to have another paper weight in my hands I now have an essential phone and it is dare I say the most comfortable phone I've ever had. That being said I hope you can Rectify your issues here but you'll have to go through either Huawei or Google, and get one of the two to help you out with a replacement.
Click to expand...
Click to collapse
Solved it today it was because I tried restoring an old backup with an old version of twrp that has a fatal bug when you restore an EFS. I was truly relieved

[Dirty-Santa Root] Bricked Verizon LG V20 Please Help!!!

I have rooted many phones before without an issue, and during the root process for this phone, everything was going great, I flashed SuperSU zip in TWRP and rebooted, since it was the first boot I expected a decently long wait, after about 25 minutes I followed the guide's instructions for Verizon since it did say some Verizon users were experiencing long first boot times. I took the battery out like it said, put it back in, then proceeded to fastboot boot2.img, like the guide said. After letting it sit for an hour this time, I got the idea that something was obviously wrong. After multiple attempts with no success I tried to fix it myself. So far I have learned that on the fastboot screen it says my bootloader is locked again, even after unlocking it. I have tried flashing TWRP as a recovery, just to at least have a recovery boot, that does not work either unfortunately. So as of right now, all I have is a v20 that has no OS, a locked bootloader, no way of booting recovery, I can fastboot with no ADB, and its virtually a paperweight. If anyone has a solution to at least get back to Stock, I would greatly appreciate it! Thanks!
First off. It will say: Bootloader Unlocked: No
Thats normal. 2nd. you are not bricked. You have TWRP installed. You just need to redo some steps.
PM me. and I will help you.
Did you get it fixed?
frome901 said:
Did you get it fixed?
Click to expand...
Click to collapse
He has not responded to my pm
What roms can we use with dirty santa root?
me2151 said:
First off. It will say: Bootloader Unlocked: No
Thats normal. 2nd. you are not bricked. You have TWRP installed. You just need to redo some steps.
PM me. and I will help you.
Click to expand...
Click to collapse
Bricked 2 LG V20s this way any help would be appreciated lol what steps do I need to redo...
TheDantee said:
Bricked 2 LG V20s this way any help would be appreciated lol what steps do I need to redo...
Click to expand...
Click to collapse
In his case we needed to redo from step 3.
I managed to un-brick mines after returning sadly from the Sprint store.
First, get to the boot loader screen and try running thru the steps again, especially step 3. You need to make sure you have TWRP.
Use this link to make sure you can get into the different modes (Download mode, fastboot, etc) http://www.hardreset.info/devices/lg/lg-v20/
Once you can get TWRP to show up,then you are good. In the mean time I downloaded "LS997-deODEXd-signed"
When I got into TWRP, I transferred the file to my phone. Rebooted from TWRP back into TWRP and flashed the ROM.
During my reboots, I do get a message saying my phone is corrupt, blah blahblah, but I just wait a few seconds and it will boot up.
Hope this helps.
I had managed to brick mines only 3 hours after upgrading from my Note 4. It took me from 9pm to almost 2am to get it back up again. I can live with the message about my phone being unbootable until someone comes up with a work thru.
Bricked T-Mobile v20
I have rooted many phones before without an issue, and during the root process for this phone, everything was going great, I flashed SuperSU zip in TWRP and rebooted, since it was flash a new rom on it then i get boot loop with TWRP. so i decide to OEM LOCK again after that everything was stuck on my phone just boot loop with LG so any solutions please help me...... THx u for help me.
Kinda nerve wrecking to read about all these "bricked" phones popping up after trying this method lol.. Perhaps I'll just wait until a more tried and true way comes out...
Dirty Santa root is not for the average user who has a couple of experience in rooting.
You have to at least have background on Hard bricking phones to fully understand what you are getting yourself into
For anyone that isnt on sprint that has "bricked" their phone. There are kdz's that will allow you to reflash back to 'stock". Someone had an issue with the kdz, but it was an easy fix. If you failed the process, it can be restored. Just if it doesnt want to boot, just lock and unlock the bootloader...
If your phone doesnt have a kdz, I know TeamDev is working on a custom kdz for such phones. Don't bug him if it isn't finished as I type this.
Anyone that can't get into TWRP, or has failed the process. Either start back at step 3, or if you have TWRP installed but can't get to it, the manual way to get into TWRP is a pain.
Keep your back cover off and hold the volume down button for ease. Now press the power button and as soon as you see an LG logo, let go and repress the power button. Its tricky.... If you get the corrupted screen, pop your battery out and put it back in quick and repress volume down and power. Usually if Im quick enough the first LG logo will hang a lot longer than usual and that gives me time to enter TWRP. A factory reset screen will pop up. Hit Yes twice.
Please help urgent
lcovel said:
I managed to un-brick mines after returning sadly from the Sprint store.
First, get to the boot loader screen and try running thru the steps again, especially step 3. You need to make sure you have TWRP.
Use this link to make sure you can get into the different modes (Download mode, fastboot, etc)
Once you can get TWRP to show up,then you are good. In the mean time I downloaded "LS997-deODEXd-signed"
When I got into TWRP, I transferred the file to my phone. Rebooted from TWRP back into TWRP and flashed the ROM.
During my reboots, I do get a message saying my phone is corrupt, blah blahblah, but I just wait a few seconds and it will boot up.
Hope this helps.
I had managed to brick mines only 3 hours after upgrading from my Note 4. It took me from 9pm to almost 2am to get it back up again. I can live with the message about my phone being unbootable until someone comes up with a work thru.
Click to expand...
Click to collapse
Please can u help ke unbrick mine i bought this mobile in my country its expensive and has no support. I have tried all tools but still getting the error model unknown please help sir
Jaistah said:
Dirty Santa root is not for the average user who has a couple of experience in rooting.
You have to at least have background on Hard bricking phones to fully understand what you are getting yourself into
Click to expand...
Click to collapse
What does that mean? Not for the average user who has a couple of experiences in rooting.
I've only rooted 2 phones, this is my 3rd (maybe 4th). I am on Sprint. Instructions worked fine for me. I did have one hiccup, but it was my fault, and I was able to root just fine. I've been running for a few months now.
I have not flashed any custom ROM yet, I'm going to wait for the next major version of Android to come out. The only mods I've done so far are Titanium Backup install so I can remove Sprint crap.
yuppicide said:
What does that mean? Not for the average user who has a couple of experiences in rooting.
I've only rooted 2 phones, this is my 3rd (maybe 4th). I am on Sprint. Instructions worked fine for me. I did have one hiccup, but it was my fault, and I was able to root just fine. I've been running for a few months now.
I have not flashed any custom ROM yet, I'm going to wait for the next major version of Android to come out. The only mods I've done so far are Titanium Backup install so I can remove Sprint crap.
Click to expand...
Click to collapse
it means dirty santa root got a high posibility rate of bricking a device compared to other root methods for other devices and if you have no experience in bricking phones before then you're screwed if it happens to you
Actually, if you follow the directions, almost none of the problems create a true brick-- which means unrecoverable. For most of the cases, you might get a soft brick, meaning you have to back out, use a KDZ to repair it or reflash something else, or start over from scratch and try again-- but usually (maybe with some help from here) you can pull the phone back into a usable state.
I would hazard to guess for the vast majority the process works fine, maybe with a hiccup, but I've not seen many reports of a truly unrecoverable brick from this method. It's complicated, yes, and you need to be ready to read a LOT to understand what's going on, but it seems pretty difficult to end up with a $700 paperweight with this.
So i have been trying tonroot my sprint lg v20 and everytime i try and go to the phone on mobile terminal to enter id
Then enter the apply patch /system/bin/atd /storage/emulated/0/dirtysanta i get this message and i cant go to step 2 to boot into recovery
Any help would be appreciated: i have a sprint v20 and i wanted to know if i have to flash the stock sprint rom or can i just flash lineage rom following this guide? I have it running on AT&T and i want to keep it on AT&T...
can you please assist
Could you help out, please? I don't believe I have hard bricked my LG V20 H910. However, I have read and tried all of the unbrick info out. It seems my screw up is unique. I completed dirty Santa then went to flash a custom. in the boot between that. I get a black screen and cant do anything even download mode will not come up. My PC does make its usual noises when i connect or disconnect, but my phone does nothing.
Ok, I managed to brick mine too. It's a VS995, it was running stock 1AC. I used the LGUP tool to downgrade it to VS99512A, and then did Dirty Sanata and TWRP. After booting into TWRP I decided to try lineage OS with Android 8.0, I did not make a backup of the Stock ROM, which was very stupid. Lineage OS 15.1 flashed but I had no cell service so I panicked and instead of wiping it in TWRP and using the backup of stock I should have created, I just opened LGUP and tried to downgrade it back to stock VSS99512A. Well LGUP said it worked, but when it went to boot it would hang at the Verizon logo with 4 pastel dots. Device manager could see an ADB device and I could connect to it with ADB. So I did and read the logcat. I could see it was trying to update as part of the rollback, but it appeared that some components from Android 8x could not be "upgraded" to Andoird 7.x. There was a repeated error about failing to update SQLite instance version from 3 to 1.
The one feature that could fix this is if the refurbish function worked with any of the VS995 KDZ files we all have access to. But alas, none work instead we only get the upgrade function... or so I thought. Somewhere in my search for the past 2 weeks I found a modified LGUP https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222
**Please be warned what I did was absolutely ****ing stupid, and it was sheer luck I didn't screw anything up.**
From what I can tell if you only flash ("LGUP Upgrade") the KDZ from the same model it never clears the partition it just adds to it. My problem was there was stuff from lineage OS 15 stuck on one of the partitions that was making the rollback to stock fail because it kept saying it couldn't update the SQLLite DB from 3 to 1. So no "upgrade" within LGUP would work because the upgrade function does not clear internal storage. But the link above is to a version someone modded so you can force a partition update from any KDZ onto the system. So I started playing around with forcing KDZs from other models onto my VS995, and I noticed when using the Partion DL function with non-VS995 KDZ files it would say something about the partition changing. All I can assume is that the partition layout is so different on each model and it forces LGUP to re-partition the storage.
**Again I state for the record this was stupid, and I'm only fortunate it worked.**
I forced Partion DL of H91510d_00_VTR_CA_OP_1110.kdz, then H990N10b_00_OPEN_HK_DS_OP_1017.kdz, then back to VS99512A_06_1114_ARB00.kdz, then when it booted it gave the Verizon hello, and moved on finally but the setting service kept crashing while it was trying to load the Secure Boot screen. So I yanked the battery and went into the boot menu and did the Factory Reset function, and it worked.
Lesson learned, always make a backup and don't be so hasty to use tools that aren't fully functional (LGUP).
Perhaps what I've done may help others, maybe I've found out how to reimage or unbrick our V20s. Or maybe I just got really stupid lucky.

Bootloop on N6P

Hi there.
So I'm using N6P for a year now and updated to 7.1.2 is I'm not mistaken . My N6P is fully stock with locked bootloader , no tweaking etc.
Was casually browsing through my phone suddenly it restarted and into went into a bootloop. I can only access the bootloader. I have tried going into recovery mode which just starts the loop over again.
I have researched just about everything and tried a lot . I just cant seem to get it working .
I really want my personal data on it , its quite important . If there isn't any more choice, then I will be forced to wipe it but until then any suggestions? Please help , thanks .
By the way , my warranty just expired a week ago so luck is surely not on my side .
Enthusiast09 said:
Hi there.
So I'm using N6P for a year now and updated to 7.1.2 is I'm not mistaken . My N6P is fully stock with locked bootloader , no tweaking etc.
Was casually browsing through my phone suddenly it restarted and into went into a bootloop. I can only access the bootloader. I have tried going into recovery mode which just starts the loop over again.
I have researched just about everything and tried a lot . I just cant seem to get it working .
I really want my personal data on it , its quite important . If there isn't any more choice, then I will be forced to wipe it but until then any suggestions? Please help , thanks .
By the way , my warranty just expired a week ago so luck is surely not on my side .
Click to expand...
Click to collapse
Sorry to hear about that. I had the same problem with my modded 6p and had a full backup on my pc and was still under warranty so it worked out fine for me. Unfortunately for you you are most likely not going to be able to fix it even from wiping it. I had the same problem and because I had an unlocked bootloader I was able to do much more than you could with flashing stock images. If you can't enter recovery then you most likely have a brick and can't fix it. I'm not sure if there is a way via adb and fastboot commands with a locked bootloader to retrieve data but I'll let you know ow if I find one. What kind of data do you have? Google usually syncs things like your photos and apps downloaded will be saved in the google play store. I hope this helped?
DEVILOPS 007 said:
Sorry to hear about that. I had the same problem with my modded 6p and had a full backup on my pc and was still under warranty so it worked out fine for me. Unfortunately for you you are most likely not going to be able to fix it even from wiping it. I had the same problem and because I had an unlocked bootloader I was able to do much more than you could with flashing stock images. If you can't enter recovery then you most likely have a brick and can't fix it. I'm not sure if there is a way via adb and fastboot commands with a locked bootloader to retrieve data but I'll let you know ow if I find one. What kind of data do you have? Google usually syncs things like your photos and apps downloaded will be saved in the google play store. I hope this helped?
Click to expand...
Click to collapse
Yeah I've tried countless things but it all comes down to me not being able to access recovery. Please do let me know if you do find one thanks . I have some very important docs as well as images in it that I need it badly . I disabled that sync feature as it took very long (for me) to back up all the media. Guess it was a big mistake ....
Enthusiast09 said:
Yeah I've tried countless things but it all comes down to me not being able to access recovery. Please do let me know if you do find one thanks . I have some very important docs as well as images in it that I need it badly . I disabled that sync feature as it took very long (for me) to back up all the media. Guess it was a big mistake ....
Click to expand...
Click to collapse
If you had USB debugging enabled then try this
https://forum.xda-developers.com/nexus-4/general/guide-making-backups-adb-t2411965
DEVILOPS 007 said:
If you had USB debugging enabled then try this
https://forum.xda-developers.com/nexus-4/general/guide-making-backups-adb-t2411965
Click to expand...
Click to collapse
I don't , its off by default ? I took a look at that page and tried it , when I fastboot devices , it can detect , but when I adb devices the list is empty .
I'm experiencing boot loop also. It won't boot into recovery. Only bootloader. I'm completely stumped.
Enthusiast09 said:
Hi there.
So I'm using N6P for a year now and updated to 7.1.2 is I'm not mistaken . My N6P is fully stock with locked bootloader , no tweaking etc.
Was casually browsing through my phone suddenly it restarted and into went into a bootloop. I can only access the bootloader. I have tried going into recovery mode which just starts the loop over again.
I have researched just about everything and tried a lot . I just cant seem to get it working .
I really want my personal data on it , its quite important . If there isn't any more choice, then I will be forced to wipe it but until then any suggestions? Please help , thanks .
By the way , my warranty just expired a week ago so luck is surely not on my side .
Click to expand...
Click to collapse
Bootloop here too
Just tried to upgrade 7.1.1 (unlocked usb debugging enabled) to 7.1.2 using Skipsoft Toolkit. Upon reboot, it just keeps going thru the graphic animation. When I connect it it says 7.1.1 detected.
I am going to try again to upgrade it. Seems like it's working. problem is it says detected system is 6.0.1 now.
Hey, it also says it takes a while for the first boot, so I may have gotten all 21st century and impatient on it.
I also tried a factory reset after freaking out that I had laid a brick...
At least with the skipsoft toolkit I was able to communicate with it!
Here's hoping!
---------- Post added at 04:51 AM ---------- Previous post was at 03:56 AM ----------
Well, although I can get to twrp, I am unable to do anything else. I can't find any clues that are up to date and it's a bummer
Didn't need to be a TWRP expert; just booted into recovery mode, selected the latest factory stock image and flashed it. back to a working nexus 6p and all i gotta do is re-root it, edit the build.prop to enable wifi hotspot (I'm on ATT) and all is groovy. Muchos props to mark and skipsoft toolkit!
Yesterday I also got a bootloop. My smartphone hovered and went into reboot. So it did not boot. It reboots. In the recovery he does not go.
Same here but with stock recovery
I am in the same exact situation. No root, everything stock and warranty expired a week ago. Coincidence..?
I have been able to enter the stock Recovery Mode, but from there I can't execute adb commands, only list devices and sideload..
is there anything else i could do from Recovery Mode ?
Thanks
morelo said:
I am in the same exact situation. No root, everything stock and warranty expired a week ago. Coincidence..?
I have been able to enter the stock Recovery Mode, but from there I can't execute adb commands, only list devices and sideload..
is there anything else i could do from Recovery Mode ?
Click to expand...
Click to collapse
Yes. If you haven't wiped/factory reset yet, you can load a newer OTA image from Recovery. Same or older OTA will not work. Set the device to update from ADB and then send it from PC. If you have wiped the phone, obviously the OTA won't work. This will work with a locked bootloader and no usb debugging enabled.
morelo said:
I am in the same exact situation. No root, everything stock and warranty expired a week ago. Coincidence..?
I have been able to enter the stock Recovery Mode, but from there I can't execute adb commands, only list devices and sideload..
is there anything else i could do from Recovery Mode ?
Thanks
Click to expand...
Click to collapse
You could maybe try this ?
https://www.reddit.com/r/Nexus6P/comments/66wsvq/this_might_sound_absurd_but_i_just_fixed_my_nexus/
Please try this if you need to boot it and get your files off the phone, it worked for me and I was able to backup my pictures.
https://www.reddit.com/r/Nexus6P/comments/66wsvq/this_might_sound_absurd_but_i_just_fixed_my_nexus/

Deleted Bootloader on LeEco S3 X626

A couple weeks back I deleted the OS off of my phone while messing with TWRP recovery trying to install a custom ROM. I looked around the forums and i got my phone to the point where It booted into a stripped down version of android with stock recovery on it, although everything was mirriored and backwards. But when i tried to install the stock rom for my LeEco S3 with stock recovery it got stuck i a boot loop and I couldn't turn off the phone or boot into recovery or anything. So i let it keep booting until it ran out of battery and died. So then i decided i would put the stripped down version back on and start again.
So I went back to my sp flash tool and reinstalled all the partions except the boot and recovery partitions (according to the steps on the forum) but my phone still wont boot into anything, it is completely black and wont boot into recovery or fastboot, and im running out of ideas on how to fix this phone :crying:
After pretty much giving up all hope of fixing my phone, i figured i would try the format option in the flash tool and then reinstall all of the pattitions. I selected format all flash, not doing proper research first, and now i cant even reinstall partions, I get a STATUS_BROM_CMD_SEND_DA_FAIL error anytime i try to flash the partitions.
can you at least get the phone to fastboot mode?
microMXL said:
can you at least get the phone to fastboot mode?
Click to expand...
Click to collapse
No I cannot, The screen is completely black and nothing comes on at all if I hold down the power button.
well damn, looks like a soft brick, it can be repaired but not gonna lie, it is a pain in the butt...
https://forum.xda-developers.com/le-2/help/bricked-le-s3-x626-flashing-twrp-power-t3715937
the guys have made an awesome guide on that thread.
microMXL said:
well damn, looks like a soft brick, it can be repaired but not gonna lie, it is a pain in the butt...
https://forum.xda-developers.com/le-2/help/bricked-le-s3-x626-flashing-twrp-power-t3715937
the guys have made an awesome guide on that thread.
Click to expand...
Click to collapse
I have already looked through that thread, and i have done everything up to the flashing process, and then I get a STATUS_BROM_CMD_SEND_DA_FAIL (0xC0060003) Error. I looked it up but the only option I haven't tried to solve the issue is to remove the battery, which i cannot do currently because to remove the battery you need a heat gun to remove the screen to get to the rest of the phone. I think I've given up all hope on fixing this phone and may just begin saving for a new one.
Sgt.Collywobbles said:
A couple weeks back I deleted the OS off of my phone while messing with TWRP recovery trying to install a custom ROM. I looked around the forums and i got my phone to the point where It booted into a stripped down version of android with stock recovery on it, although everything was mirriored and backwards. But when i tried to install the stock rom for my LeEco S3 with stock recovery it got stuck i a boot loop and I couldn't turn off the phone or boot into recovery or anything. So i let it keep booting until it ran out of battery and died. So then i decided i would put the stripped down version back on and start again.
So I went back to my sp flash tool and reinstalled all the partions except the boot and recovery partitions (according to the steps on the forum) but my phone still wont boot into anything, it is completely black and wont boot into recovery or fastboot, and im running out of ideas on how to fix this phone :crying:
After pretty much giving up all hope of fixing my phone, i figured i would try the format option in the flash tool and then reinstall all of the pattitions. I selected format all flash, not doing proper research first, and now i cant even reinstall partions, I get a STATUS_BROM_CMD_SEND_DA_FAIL error anytime i try to flash the partitions.
Click to expand...
Click to collapse
Help, pls I got the exact same problem... Pls any solution to it... I have been at it for a month now no solution, help
same problem. after twrp flash x626 not boot

How I fixed my Realme x2 Pro from not booting into system

So earlier I spent hours trying to fix this with no luck. I downloaded probably over 12 different roms, same thing. I've posted on the questions forum for help and we still couldn't figure it out.
It would go right back to recovery, so I was curious and flashed AOSIP custom rom and it booted right up!
From there I downloaded the stock recovery.img, flashed that. went to wipe, tried wiping regular, didnt work. So I clicked format data, it finished then installed the stock rom and everything is working.
This may not work for everyone, nor am I saying its a guaranteed fix, it's something that worked for me.
Let me know if this works for you if you want the stock recovery img, I can upload it too!
Huge shoutout to @Sergiocubano1 who spent hours trying to help me fix the issue. Happy flashing everyone, also if you go back to a custom recovery orangefox/twrp I would suggest creating a backup of your rom and putting the backup on your computer.
I wonder why it is not possible to restore this phone by putting it in EDL DOWNLOAD mode.
I would like to return stock with the RMX1931EX_11_A.08, because now with this system I suffer from random restarts but I am stopped for fear of brick.
On youtube there are guides for unbrick, but there are passwords to the software for flashing in EDL DOWNLOAD that they release for a fee of $ 20.
I honestly didn't believe this phone was so limited on a mod level.
Such a pity.
westenlive said:
I wonder why it is not possible to restore this phone by putting it in EDL DOWNLOAD mode.
I would like to return stock with the RMX1931EX_11_A.08, because now with this system I suffer from random restarts but I am stopped for fear of brick.
On youtube there are guides for unbrick, but there are passwords to the software for flashing in EDL DOWNLOAD that they release for a fee of $ 20.
I honestly didn't believe this phone was so limited on a mod level.
Such a pity.
Click to expand...
Click to collapse
I wouldn't trust them. Did you try this method?
I don't trust them either. For this reason I have not tried.
however other devices like oneplus have the possibility.
to perform a total reset of the device through this EDL DOWNLOAD method.
in this device it is all very strange.
this device has very interesting specifications but is very limited.
I am looking for a system to do a total reset of the device with a stock version.
xHvlios said:
So earlier I spent hours trying to fix this with no luck. I downloaded probably over 12 different roms, same thing. I've posted on the questions forum for help and we still couldn't figure it out.
It would go right back to recovery, so I was curious and flashed AOSIP custom rom and it booted right up!
From there I downloaded the stock recovery.img, flashed that. went to wipe, tried wiping regular, didnt work. So I clicked format data, it finished then installed the stock rom and everything is working.
This may not work for everyone, nor am I saying its a guaranteed fix, it's something that worked for me.
Let me know if this works for you if you want the stock recovery img, I can upload it too!
Huge shoutout to @Sergiocubano1 who spent hours trying to help me fix the issue. Happy flashing everyone, also if you go back to a custom recovery orangefox/twrp I would suggest creating a backup of your rom and putting the backup on your computer.
Click to expand...
Click to collapse
can you give me the link of the recovery stock?
thank you very much
@xHvlios Please how did you get the stock rom ozip into the stock recovery? I tried putting it in the device storage but when I go into stock recovery -> choose language -> install from storage device -> From phone storage; nothing happens. I also tried putting it in a flash drive but I can't see this device in the recovery.

Categories

Resources