Related
Hey,
I just wanted to inform you about an issue that happens in TWRP. I just bricked my Pixel by switching to slot B without flashing a bootloader in slot B. I think TWRP should inform the user that rebooting will brick the device. What are your thought on that? It could be done similar to how TWRP informs the user to install supersu if the phone isnt rooted.
This would be really helpful as it would prevent many people like myself from bricking their phones.
Now if I connect my pixel it only shows Qualcomm HS-USB Diagnostics 900E (COM3). No bootloader, fastboot, or recovery is present.
Here are a coupe of links of other people that did the same thing:
https://productforums.google.com/forum/#!topic/phone-by-google/sXjCoQ8glac
http://forum.xda-developers.com/pixel-xl/help/pixelxl-bricked-t3517310
Thanks!
Edit
I contacted the devolper of TWRP and he says that it should have boot loader regardless.
Here is the history: At work 3pm, froze Android system apk and some other telephone apps to troubleshoot something, I know I shouldn't do this. Resulted into boot loop. Go into twrp recovery and wipe data. It boots up fine and I see it downloading updates but it never goes through, I attempt to go back to recovery and apparently it's back to the stock recovery even though I originally had TWRP rc1.
I get home at 7 pm, I want to install TWRP rc1 so I send the command to boot into TWRP and then I install the zip, then I install sr5 SuperSU. I change to slot b and it's been bricked since.
It arrived November patch and it stayed like that since I was rooted. It attempted to install 7.1.1 but it returns installation problem. I think the bootloader was removed because of the failed update.
Your in download mode. I had this happen once on my Nexus 7. I held power for 90 seconds and it went back to bootloader. However I dont know about the pixel. Its still a new and uncharted device.
You also have to realize TWRP is in an unstable stage. You really should not flash anything until its in final release mode. I know I know... Hindsight is 20/20.
If you have insurance you could get it replaced.
Good luck.
sorry to hear dude..
bahehs said:
I think TWRP should inform the user that rebooting will brick the device. What are your thought on that?
Click to expand...
Click to collapse
I'm just curious. Have you ever donated any money to TWRP for the free developmental software they provide for free to the community to try/test with for free?
bahehs said:
I just bricked my Pixel by switching to slot B without flashing a bootloader in slot B.
Click to expand...
Click to collapse
Does anyone have an understanding about how something like this could potentially happen? Do these phones ship without information on the second slot? After my phone OTA updated, I switched slots without issue back to the previous version by following the information from Android Police. I'm not clear on what exactly would need to happen for the noted situation, and how someone could potentially get into a similar situation, unless the phone ships without information on the second slot. Switching slots worked without issue the times I tried it, but my phone had been through a typical OTA update before switching slots, so there was definitely information on both slots when I tried it.
Just an FYI: I am running Slot B on my device. Never tried Slot A. Just an FYI
Scott said:
Just an FYI: I am running Slot B on my device. Never tried Slot A. Just an FYI
Click to expand...
Click to collapse
Same, mine is on slot B. Dunno if it came that way, but it is only two days old. I let it take the OTA then flashed Francos kernel and then booted the root su image.
I really regret not watching more closely how all of impacted which slot it was on.
Sent from my Pixel XL using XDA Labs
Everytime you get OTA update you will switch slots. If you update via flashall it will say on the same slot.
This mode can't be a complete brick but it doesn't look like anyone has a solution yet. Maybe we will need some HTC tool?
Also when you root or modify you take responsibility for anything that happens. There is always a chance of a brick. At least Google will still probably warranty these devices.
Sent from my Pixel using Tapatalk
CZ Eddie said:
I'm just curious. Have you ever donated any money to TWRP for the free developmental software they provide for free to the community to try/test with for free?
Click to expand...
Click to collapse
This comment is unnecessary and serves no purpose in this thread.
Sent from my Pixel XL using XDA-Developers mobile app
I'm okay with that.
Updated op with more info
I installed TWRP while in the car riding with my girlfriend. I had some issues with the mobile radio showing no SIM card. Due to my limited options, I tried switching rom slots. It booted into the old software and said there was an update etc. I don't think switching rom slots leads to bricking if no other mods were done.
reb1995 said:
I installed TWRP while in the car riding with my girlfriend. I had some issues with the mobile radio showing no SIM card. Due to my limited options, I tried switching rom slots. It booted into the old software and said there was an update etc. I don't think switching rom slots leads to bricking if no other mods were done.
Click to expand...
Click to collapse
were you rooted because I had an ota in process wich failed while I was rooted which I think was the cause of the issue.
I kind of had the impression none of the stuff we're flashing is the bootloader itself. Isn't the bootloader the Android equivalent of Windows BIOS? Doesn't the bootloader load the boot image? Then the boot image mounts the system partition? So how could anything we're flashing cripple the bootloader?
Sent from my Pixel XL using Tapatalk
bahehs said:
were you rooted because I had an ota in process wich failed while I was rooted which I think was the cause of the issue.
Click to expand...
Click to collapse
Sorry for the long delay. No I was not rooted.
yearn2burn said:
I kind of had the impression none of the stuff we're flashing is the bootloader itself. Isn't the bootloader the Android equivalent of Windows BIOS? Doesn't the bootloader load the boot image? Then the boot image mounts the system partition? So how could anything we're flashing cripple the bootloader?
Click to expand...
Click to collapse
Bump
The problem is that the phone ships with an empty slot. If you try to boot it your permanently bricked do to having no bootloader on that slot. Once you take an OTA both slots have data and you're safe.
bahehs said:
were you rooted because I had an ota in process wich failed while I was rooted which I think was the cause of the issue.
Click to expand...
Click to collapse
You are right a failed OTA could brick a pixel phone
DR3W5K1 said:
The problem is that the phone ships with an empty slot. If you try to boot it your permanently bricked do to having no bootloader on that slot. Once you take an OTA both slots have data and you're safe.
You are right a failed OTA could brick a pixel phone
Click to expand...
Click to collapse
There is only one bootloader though so that's the confusing part. Still not sure how some people bricked completely. The bootloader is the first thing to load and tells the phone which slot to boot. Each slot does have its own boot, system, and vendor though. Been discussing this a lot on some other threads and there is still no answer has to what some of these people did internally that messed up their phones
aholeinthewor1d said:
There is only one bootloader though so that's the confusing part. Still not sure how some people bricked completely. The bootloader is the first thing to load and tells the phone which slot to boot. Each slot does have its own boot, system, and vendor though. Been discussing this a lot on some other threads and there is still no answer has to what some of these people did internally that messed up their phones
Click to expand...
Click to collapse
Failed bootloader flash? The Google .IMG files contain bootloader's.
EDIT I do believe the flash_all.sh flashes the bootloader
So you cant even run ADB commands ( a.k.a Bootloader / Recovery mode ), its a hard brick or soft ?
Does your PC detect the device when its on and connected via USB ?
Why did you switch slots in the first place ? if your taking an OTA on a rooted device with SU an OTA wont even apply via TWRP, you have to manually flash with the flash-all.bat script or part by part and the A / B boot slots are handles by the updates so you don't accidentally boot with a slot with no bootloader.
There is no need to swap A / B manually and if your going to flash and want to play with the A / B slots you should at least flash the partitions first but hindsight is a wonderful thing.
Aboot here might be your friend, but as this device is still quite new to many devs and or the tools might not be publicly available . . .
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.
My tmobile LG k20 plus phone has a boot loop and will not start, this happened when I copied a file to the main directory of my phone, instead of merging the files it deleted the system folder, I tried to fix it by reinstalling twrp and it worked, after flashed twrp I installed a fresh SuperSU ROM and when I did the boot loop did not go away and in addition to this my computer will no longer find my phone through ADB or fastboot, if you can help I will be amazed and quite happy, I'm new here so any help is appreciated
bump:fingers-crossed:
megamind994 said:
My tmobile LG k20 plus phone has a boot loop and will not start, this happened when I copied a file to the main directory of my phone, instead of merging the files it deleted the system folder, I tried to fix it by reinstalling twrp and it worked, after flashed twrp I installed a fresh SuperSU ROM and when I did the boot loop did not go away and in addition to this my computer will no longer find my phone through ADB or fastboot, if you can help I will be amazed and quite happy, I'm new here so any help is appreciated
Click to expand...
Click to collapse
did u ever get it figured out? i am in the same boat grr
I found a program called lgup which was able to fix the phone, it's capable of flashing a new rom onto a soft bricked phone. Sadly I don't recall any specifics but on a quick search for "lgup lg k20 plus" you should be able to find what you're looking for with relative ease. Also, you may want to consider making your own thread on the future... It has been 3 years
megamind994 said:
I found a program called lgup which was able to fix the phone, it's capable of flashing a new rom onto a soft bricked phone. Sadly I don't recall any specifics but on a quick search for "lgup lg k20 plus" you should be able to find what you're looking for with relative ease. Also, you may want to consider making your own thread on the future... It has been 3 years
Click to expand...
Click to collapse
thanks
Yeah. Sorry for the late reply given you guys found the fix by now, but yes, generally with the sort of severe mishaps from editing or accidental deletion of certain system files or directories, sometimes a dirty flash or even a totally clean flash after performing data ave system partition wipes, will just not fix or restore the device.
You would then need to do a complete stock image reflash either using LGUP or the official LG software recovery tool. If you know what you're doing, you could skip over reflashing stock in its entirety, if say you know the problem has only to do with a particular protected partition like modem, EFS, etc. But generally good practice to just recover all the stock partitions, refresh the device software to factory conditions, reflash your bootloader and recovery images, root STOCK or install custom ROM, so on and so forth.
If you're a frequently curious tinkerer, making backups will be crucial to your sanity.
So I just picked up a clean used International 6T. Was going through the root and update (I did the Android 10 update through Oxygen Updater) process and all that, things were going great, then out of nowhere they weren't and I had a complete black screen. I've literally been up all night trying to fix this thing, then again out of nowhere it actually boots, and I was able to use the MSM tool to restore it to that earlier version, then proceeded to get back up and running again.
Thought, phew, dodged a bullet. Nope, after getting rooted and TWRP installed, transferring a bunch of files over from my old SD card and restoring apps through Titanium (again, everything was going great again), and yet now all of a sudden I'm back where it all started earlier, stuck at the 'The boot loader is unlocked and ....' boot screen, it just hangs there, I can reboot into recovery just fine, but no operating system.
I'm literally about to pull my freaking hair out and try and sell this thing if it's going to keep doing this, I've never had a phone act like this one has (prior phone was a Nokia 8, headache). I have friends/family who haven't heard from me in a couple days now because I'm out of a phone and I need to get this thing working stable.
Can anyone help or shed some light on why this has happened again? I didn't update to 10, left it on the last stable Pie (begrudgingly), didn't flash any custom rom or anything, it was restoring most of the titanium apps just fine (some just hang there, not sure what that's about) and now I can't reboot into the os. To say the least I'm beyond pissed and annoyed at how much time I've lost on this thing.
Please please please help if you can, I'm not a newb to rooting (already rooted this one twice) but I don't know what to do at this point.
Thank you in advance, let me know what/if any info is needed.
Edit: I think I know/understand partially that magisk is to blame for this and reinstalling it fixes it, though I just did that through TWRP and it's still stuck on the boot screen.
Edit: Yup, right back where I was, device now shows as HS-USB QDloader..... in device manager. What gives? I have to use the MSM tool again? Why? Why is this happening...I've never had this much trouble with a phone
Try a clean install. Don't root and don't restore the titanium apps. Install them fresh. If your problem persists then it may just be hardware. But something you are restoring may be causing the crash due to the way it is trying to restore the app data.
I had similar problems. For me it was my self-created magisk module that ran without problems under Android 9. As it seems, there are also problems with modules from the magisk repo.Could be the case with you.
Clean install of the apps, after doing another MSM restore? And trust me, I won't be installing ANY other magisk files other than just the magisk.
Is there any way to save all the work I just did though without having to start over again via MSM? I'm guessing not....sigh
Grrrr...ok before the MSM tool worked, the phone was just unresponsive. It's back at that stage where the MSM tool times out and doesn't do a darn thing to save the phone.
I swear this thing is all over the place, now I'm in the bootloader, yay. I guess I'll try a wipe in TWRP and start over.
One thing I forgot to ask, is magisk the ONLY option available for root?
The question would be, how did you root.
TWRP is not working when you don't follow the instructions which involves OldKeysFlasher.zip.
Otherwise you have to flash Magisk with a patched boot image, be sure uyou have one for OOS 10 Stable.
The correct comands are here: https://forum.xda-developers.com/showpost.php?p=80638253&postcount=2853
jgro1976 said:
(...)
I'm literally about to pull my freaking hair out and try and sell this thing if it's going to keep doing this, I've never had a phone act like this one has (prior phone was a Nokia 8, headache). I have friends/family who haven't heard from me in a couple days now because I'm out of a phone and I need to get this thing working stable. (...)
Click to expand...
Click to collapse
I hope that anger is directed towards yourself because you can't hold the device or its manufacturer responsible when you get into the flashing game.
If you had done some reading, you'd know that TWRP doesn't play well with Android 10 and upgrading from 9 takes a very specific procedure. There's a dedicated thread for it even. Happy searching. You may also want to take a peek at my posting history for some pointers.
One more thing, are you absolutely sure it's an international device and not a converted T-Mobile version? Because that can cause a major amount of troubles.
Wrapped with delicious Fajita [emoji896]
I'm well aware it's my own doing, part of the frustration is having too many sources of information all claiming they fix a 'thing'. There's the "fix it with fastboot" camp who doesn't like MSM, and there's the MSM camp that helped me the first time. Phone is currently dead/black screen, going to try MSM again, and will check out the info you provided.
And I'm sure, double sim tray, does not flash a pink tmobile screen and/or no branding of any kind on the phone related to tmobile.
jgro1976 said:
And I'm sure, double sim tray, does not flash a pink tmobile screen and/or no branding of any kind on the phone related to tmobile.
Click to expand...
Click to collapse
Just remember that dual SIM trays are easy to get and if it's been converted from TMO to international version there will be no indicators till n you try to flash A10. Best bet would be to treat it as a converted TMO, if it is the info in recovering and flashing a TMO device will work and if it's truly an international version it will work too. Best of both worlds.
I'm 99% certain, by the label on the box, etc. Regardless, I'm to the point now that I can't even get it to boot to TWRP after 'fastboot flash boot twrp.img', it just does nothing and when I try to boot to recovery it bounces right back to bootloader. I've been trying all afternoon to fix it with no luck.
Was android 8/oreo good on these phones? That was my sweet spot and I'm just gonna downgrade if possible, there's too many things I don't like about 9 and 10.
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.