Flashed NON-HLOS, wifi still won't work - X Style (Pure) Q&A, Help & Troubleshooting

Hi, everyone. First post here so I'm coming up to speed on a lot of things.
I bought a brand new Moto X pure yesterday and was excited to get to work on rooting. The whole process went smooth. I currently have an entirely rooted device on Marshmellow. There was a hitch at the end of it, though. Everytime I flip my wifi to 'on' it goes off on its own the very next second.
The logical conclusion was to search this forum and try the widely suggested tip of flashing NON-HLOS.bin in fastboot. Well I did...and I'm still having the same problem. I've searched through a whole bunch of wifi related threads and there doesn't seem to be much lack of success after flashing the bin in fastboot.
Do any of you fine folks have any tips or will I have to flash a nandroid back to the 'stock' Marshmellow I had made right after flashing TWRP?

I know when flashing original firmware you have to flash the non hlos file then follow with commands that erase modemst1 and modemst2. This might be worth investigating???

I am not sure if this would help?
Note: Problem & solution is for lollipop but the cmds I think are for MM and LP.
Problem:http://forum.xda-developers.com/showpost.php?p=64582653&postcount=146
Solution for the guys wifi problem.
http://forum.xda-developers.com/showpost.php?p=64584506&postcount=149
If not, my bad.

You must reflash the Modem again. I have the same issus and after reflashing Wifi working fine.

OneCoconutTwoCoconut said:
Hi, everyone. First post here so I'm coming up to speed on a lot of things.
I bought a brand new Moto X pure yesterday and was excited to get to work on rooting. The whole process went smooth. I currently have an entirely rooted device on Marshmellow. There was a hitch at the end of it, though. Everytime I flip my wifi to 'on' it goes off on its own the very next second.
The logical conclusion was to search this forum and try the widely suggested tip of flashing NON-HLOS.bin in fastboot. Well I did...and I'm still having the same problem. I've searched through a whole bunch of wifi related threads and there doesn't seem to be much lack of success after flashing the bin in fastboot.
Do any of you fine folks have any tips or will I have to flash a nandroid back to the 'stock' Marshmellow I had made right after flashing TWRP?
Click to expand...
Click to collapse
Reflash the modem again and it will work. If not then just restore your backup and re root

jlbuck6212 said:
Reflash the modem again and it will work. If not then just restore your backup and re root
Click to expand...
Click to collapse
Reflashing the MM modem does not work. I've got the same problem.

I had the same problem also and it worked for me. If it's not working then you may want to do everything again step by step to make sure you are not missing anything. Go back into twrp, wipe cache and dalvic and reboot before you do anything. If it is turning off then it is your modem and it is faulty so you may want to re download the modem and try again. Make sure you aren't flashing the lollipop non hlos with mm.

Thanks for the help, everyone. In the end, reflashing did not do the trick (I wonder if I was doing something wrong), but I managed to get my wifi back after restoring my nand. This was the thread I used to help gain root. Could I have missed a step in there during the process?

Related

[Q] Strange Boot Loop Issue (MK2, SS 3.71)

I've generally managed to root and/or customize most of my devices with the help from these forums, but this one has me stumped. I picked up an AT&T Galaxy S4 recently, and unfortunately it was already on a locked bootloader. I was able to root and install Safestrap 3.71 with little trouble. After some tweaking of the stock ROM, I decided to have a go with some custom ones.
Until recently, I'd been able to flash just about any SS-compatible ROM to any slot with little to no issue. Some required flashing of GApps, or Kernels, but aside from a few FC's or signal issues, the actual flashing portions always went smoothly. I ended up flashing DarthStalker vX1 to my stock slot with the MK2 kernels and have had zero issues with the ROM functionality. Being curious about recent developments with other ROM's, I decided to try flashing a few. The problem I'm having is that 90% of the ones I try to flash are going into a boot loop. Even those that worked previously (Hyperdrive, SHOstock) are boot looping.
I have tried deleting and recreating various ROM slots and at one point I managed to get SHOstock (SS) 3.0 to boot, but all of the GApps were crashing to the point where it was unusable, regardless of GApps I flashed over it for testing purposes.
I guess I'm wondering if there may be some sort of issue with having a custom ROM in the stock slot? Perhaps some sort of file or data corruption that is stopping these ROM's from working, even though they all worked previously? It just doesn't seem to be making sense because I don't believe I've changed anything since the last time I was able to flash to any SS slot. I've tried searching, but pretty much all of the boot loop issues I've come across were related to something that I've either already ruled out, or simply didn't apply to my configuration. Any hints or tips would be great. Please let me know if anyone needs more information about the config, or steps I've taken so far. Thanks all!
@remedee
I believe for HyperDrive u also need to install Att compatible pack and u also need flash ATT mk2 kernel modules .... check this thread about MK2 INDEX and ROM LISTS by @guut13 http://forum.xda-developers.com/showthread.php?t=2616221 anything u should know about all the compatible roms and instruction. ....u might get better help on that thread since alot of Rom flashaholic there. ...check with @ddubz he is flashaholic Master..... :thumbup::thumbup:.... Goodluck.....
Swyped From MK2 Dark Venom SS Edition
Once you flash a bad ROM on Stock slot and you boot loop, you are cooked. Only way to fix it is to Odin back to stock. Then you can restart the process.
If you flash a bad ROM on a ROM slot, you can just delete the ROM slot, recreate it, and you will be good to go for another try.
That's been my experience, anyways.
ted77usa said:
@remedee
I believe for HyperDrive u also need to install Att compatible pack and u also need flash ATT mk2 kernel modules .... check this thread about MK2 INDEX and ROM LISTS by @guut13 http://forum.xda-developers.com/showthread.php?t=2616221 anything u should know about all the compatible roms and instruction. ....u might get better help on that thread since alot of Rom flashaholic there. ...check with @ddubz he is flashaholic Master..... :thumbup::thumbup:.... Goodluck.....
Swyped From MK2 Dark Venom SS Edition
Click to expand...
Click to collapse
Thanks for the reply. I've read through quite a few of the threads for the individual ROMs, but unfortunately the issue isn't related to any one specific ROM. I do have the compatibility pack and modules for HyperDrive and I was able to successfully get that installed previously. I was using that as an example of a ROM that worked before with this same configuration, which is why it's bugging me. I'll wipe out the existing slot 1 and give it another go, making sure I flash those as well. Unfortunately that doesn't explain why SHOstock (which I tested extensively before), and others go into a boot loop as well.
The only thing I can think of is perhaps I'm not wiping properly. So far, whenever I attempt to install a new ROM, I create a new slot with the default size values, do a factory reset, install ROM and any module/kernel recommended with it, wipe cache, reboot. Not sure what else I could be doing wrong.
guut13 said:
Once you flash a bad ROM on Stock slot and you boot loop, you are cooked. Only way to fix it is to Odin back to stock. Then you can restart the process.
If you flash a bad ROM on a ROM slot, you can just delete the ROM slot, recreate it, and you will be good to go for another try.
That's been my experience, anyways.
Click to expand...
Click to collapse
Thankfully I don't think I've had any truly bad flashes that resulted in a brick, or even a partial brick. My stock slot is running a custom (Darthstalker) ROM that is still fully functional through all of this other testing. I do have backups of my original stock config, as well as a recent backup of the DS ROM in the stock slot, so I'm not sure it's related to a bad ROM in that slot. It's just really strange that ROMs that were working just fine before in any slot are now causing loops. I haven't had to Odin back to stock or anything, but I'm considering doing that just to get back to a clean base. It just seems unnecessary since my stock slot is still 100% functional. No signal drops, all wifi and bluetooth connections work flawlessly, etc.
I'm usually the guy that scours these forums until I find a solution, but this problem is just plain weird. As you can see from my post count, this is the first time I've thrown up my hands and asked for help. I'm not even sure there is anything really broken. It could very easily be something stupid I have or haven't done. It's just frustrating when I flash a ROM that I've verified the MD5 on, and I know for a fact has worked previously. I'll keep plugging away at it and post back if I figure out what's going on. Thanks again!
@remedee If I were u..... Follow my thread to go back to stock MK2 http://forum.xda-developers.com/showthread.php?t=2621279 check post #2 for guide on how to. After u got fresh MK2 firmware ..... root it.... install safestrap v3.71 and then create rom slot 1 first to see if the rom stable enough ....If it does then make your rom slot 1 back up .....then wipe your stock slot..... restore your rom slot 1 back up to stock slot or follow @guut13 instruction noted on every compatible rom lists from his thread. ..... Goodluck....:good:
Swyped From MK2 Dark Venom SS Edition
remedee said:
Thankfully I don't think I've had any truly bad flashes that resulted in a brick, or even a partial brick. My stock slot is running a custom (Darthstalker) ROM that is still fully functional through all of this other testing. I do have backups of my original stock config, as well as a recent backup of the DS ROM in the stock slot, so I'm not sure it's related to a bad ROM in that slot. It's just really strange that ROMs that were working just fine before in any slot are now causing loops. I haven't had to Odin back to stock or anything, but I'm considering doing that just to get back to a clean base. It just seems unnecessary since my stock slot is still 100% functional. No signal drops, all wifi and bluetooth connections work flawlessly, etc.
I'm usually the guy that scours these forums until I find a solution, but this problem is just plain weird. As you can see from my post count, this is the first time I've thrown up my hands and asked for help. I'm not even sure there is anything really broken. It could very easily be something stupid I have or haven't done. It's just frustrating when I flash a ROM that I've verified the MD5 on, and I know for a fact has worked previously. I'll keep plugging away at it and post back if I figure out what's going on. Thanks again!
Click to expand...
Click to collapse
Just to be clear, I didn't necessarily mean bricked when I said cooked, but kind of. I tested a bunch of ROMs for my threads. If i flashed one that didn't work, my phone would usually boot loop...
samsung logo, safestrap menu, black screen, reboot, samsung logo, safestrap menu, black screen, reboot, and so on...
If I stopped the boot loop by going back into safestrap, no matter how many times I wiped or which ever ROM I flashed next (even known working ones), I always went back into a boot loop after rebooting. Only thing that worked was odin back to stock. (Can't remember if I tried restoring, though.)
ROM slot was different. Deleting it and recreating was all it took. That's why I learned my lesson and just test new roms on ROM slot first.
remedee said:
Thanks for the reply. I've read through quite a few of the threads for the individual ROMs, but unfortunately the issue isn't related to any one specific ROM. I do have the compatibility pack and modules for HyperDrive and I was able to successfully get that installed previously. I was using that as an example of a ROM that worked before with this same configuration, which is why it's bugging me. I'll wipe out the existing slot 1 and give it another go, making sure I flash those as well. Unfortunately that doesn't explain why SHOstock (which I tested extensively before), and others go into a boot loop as well.
The only thing I can think of is perhaps I'm not wiping properly. So far, whenever I attempt to install a new ROM, I create a new slot with the default size values, do a factory reset, install ROM and any module/kernel recommended with it, wipe cache, reboot. Not sure what else I could be doing wrong.
Click to expand...
Click to collapse
next time you try to flash one and it fails try making the data partition smaller. Had a guy pm me and couldn't get rom to boot and i had him do this and bam it booted right up. Worth a shot. Also i have switched phones i went to the nexus 5 and i am not as fresh with the s4 stuff as i was a few weeks ago. PM if you need any help
I still plan to Odin back to stock but I didn't have time tonight. I did however grab a ROM from the link provided by ted77usa (thanks man, I can't seem to figure out how to mention at the moment). The Wicked v10 ROM installed to a clean Slot 1. I know that DarthStalker installed using Aroma, and Wicked is one of the few that I've tested that also uses Aroma. I don't know if it makes a difference, but this is the first ROM to install without a boot loop since I started having trouble.
I'm also wondering if the fact that this ROM had never been installed before has anything to do with it. I'm going to back it up since it's functional, then wipe and try to reinstall just to see if I get a boot loop. Thanks again to everyone for all of the input.
Sorry for the delay in getting back on this. My toddler finds new and interesting ways of keeping me from my hobbies Just wanted to say thanks to @ted77usa @guut13 and @ddubz. I tried resizing the partition and that didn't seem to help. I ended up starting from scratch and everything seems to be running properly. I've got DarthStalker back in the stock slot, Wicked in slot 1 and Hyperdrive in slot 2. I'm quite certain it's overkill, but just knowing I can switch between them and tinker makes me happy. Thanks again for all the input. XDA is definitely an awesome community.

Repost: Return to Stock ROM

This question was originally posted here but didn't seem to get much traction. Hoping putting it on its own thread will help me get the answers I'm looking for.
I recently un-rooted my Moto X 2014 to take an OTA update and then re-rooted it again. (Ref: http://forum.xda-developers.com/moto...phone-t3179350). I was really surprised by how smoothly everything went, and it got me thinking that I'd kind of like to update my old Nexus 4 that I keep around to use as a WiFi only device for music and such. I downloaded the factory image (Ref: https://developers.google.com/androi...s/images?hl=en), so my question is: will the process be as simple? Do I just boot into fastboot and flash system.img? As in the first post I linked, I don't want to lose any of my data or settings, nor do I want to lose root.
Current Status:
Android version: 4.2.2
Kernel version: 3.4.0-perf...CyanogenMod
CyanogenMod version: 10.1.3-mako
What I'd like to do is get my phone back as close to stock as possible (from a UX perspective, probably want to keep custom recovery), while maintaining root and without losing any data or settings. Any references for the best way to go about this?
Thanks in advance!
Click to expand...
Click to collapse
If you will flash a factory image you will loose all the data on the phone. Backup the data on a PC or wherever you want and then flash.
You will loose your root too.
---------- Post added at 10:03 AM ---------- Previous post was at 10:01 AM ----------
It is better using Nexus Root Toolkit. Easy and fast. No hassle.
Being that you are on 4.2.2, you are going to need to flash more than just the system.img file. I know there was a change to the radio, and am rather sure there was a change to the bootloader.img as well (not certain). So yes, while you can flash the images directly, you will need to flash bootloader.img, boot.img, radio.img, and system.img at minimum, or, you can just flash the 4.2.2 system.img file from https://developers.google.com/android/nexus/images and then just keep using the OTA updates to move up to the latest LMY48I release. Once you get there, you can then just re-root and install a custom recovery at the same time.
So, I actually followed the steps in your original response (just flashing boot.img and system.img) and that seemed to work great. I'm now running 5.1. I had a little trouble getting TWRP to stick. I kept flashing it, rebooting to system and rebooting to recovery...only to find stock recovery. The trick was to flash TWRP, boot *directly* into recovery (TWRP now), flash SuperSU. I think I'm all set...much thanks!
Okay, so I am noticing some rather odd behavior:
* I can access quick settings once after reboot, then I cannot access it
* when I set the lock screen setting to "Swipe" I still have no lock screen
* the home button doesn't seem to work
Any idea how I might resolve issues like this? I've tried wiping the cache.
Ended up doing a factory reset. It resolved all the issues I describe above.
Cool, yeah, I figured it would work, but you are operating with the old 4.2.2 radio. There is no reason why it would not work, however, usually the new radio versions incorporate fixes, so you might think about flashing those images. (or take the, if it ain't broke, don't fix it approach)
Yep, definitely a taking a, "if it's not broke, don't fix it approach" Just out of curiosity, though, what do you mean when you say "radio"? The radio for the wireless signal? As I said in the original post, this is now a WiFi only device. Not sure if you're talking about the WiFi radio, but it seems to be working great.
I am referring to the radio.img file, which hosts the Baseband for the phone, it affects Wifi and Cellular/SMS/MMS processes. Usually, changes are more to the mobile side than the Wifi side however, but Wifi side fixes sometimes address disconnects from the AP, etc. If Wifi is working well for you, then no need to mess with it.

Broken Wifi, Recovery img after botched OTA upgrade & restore-to-stock

Hi, I'm new to ROM flashing etc. and seem to have gotten myself in trouble.
I bought a used Moto X Pure (XT1575 model) with, I guess, the Motorola unlocked bootloader and TWRP already installed. I accidentally approved an OTA update this afternoon and ended up in a boot-loop.
In trying to fix it I used the "restore-to-stock tool" for windows found here:
http://forum.xda-developers.com/mot...ndows-tool-moto-x-style-pure-edition-t3199905
This was semi-successful; the OS loaded and I was able to begin migrating my old apps, but
(1) the wi-fi doesn't work at all! I can't turn it on in settings -- the slider will slide on but then slide back off by itself
(2) the recovery image seems screwed up; I can't get into recovery mode, and get an error there instead.
I am at a loss as to what to do but see my last resort in using fastboot to upgrade to the 6.0 stock image as described here:
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
I'm too tired to try tonight, so I thought I'd ask for advice before I go to bed. What are my options here, especially if the upgrade to 6.0 creates new problems? Can I get error meessages for the wireless so I at least know what's going on? Can I reflash the wireless firmware -- might it have been messed up if one or another upgrade was interrupted somehow?
Also -- hope I'm in the right forum -- please point me in the right direction if I'm not!
Many thanks for the help!
Did you read that thread? Quite a bit of wifi talk in there.
lafester said:
Did you read that thread? Quite a bit of wifi talk in there.
Click to expand...
Click to collapse
Oh man, I had NOT read far enough in that thread. The solution was simply to reflash the modem,
Code:
fastboot flash modem NON-HLOS.bin
Just did it and the wifi issue seems to be fixed!
How should I approach the crashed recovery partition? When I got the phone, TWRP was installed as well as SuperSU. I tried the restore-to-stock tool mostly because of the problem with OTA updates being so frustrating; but I wouldn't object to reinstalling TWRP and SuperSU, if I knew how to get and install new images within a few days of the OTA update arriving (I have been deferring the last OTA update since the day I got the phone, a month ago -- I was bound to make a typing error eventually, and it happened yesterday). Anyway, if you can point me in the right direction for learning that stuff I'd be grateful.
So psyched to have wifi working! THank you!
There's a twrp thread in og dev

Screen Not Responsive After Flash ..... +

Hey,
I've been on quite a journey since I attempted to flash the Treble rom for newbies. My phone eventually ended up as DFU'd but, I brought it back to life after a following the DFU Unbrick - Disassembly guide. After doing this, the screen was not responsive to touch at all at the Welcome screen of the EDU ROM. So, my adventure continued as I took the phone apart several times again to make certain things were connected, not damaged, etc..
After flashing TWRP I concluded the screen itself must be fine because I could use TWRP using the screen/touch. I have since tried flashing several different roms, tried many combos of unlocking the bootloader (again, because I assume it was already unlocked due to the bootloader warning screen of can not check for corruption message), tried flashing bootstack and the stock rom from DrakenFX. Used MiFlash, EDM Tool to flash various items.
Each time and currently, when it boots to the Welcome screen it does not respond to touch.
Can anyone please help me with this?
Thank you!
I remember this happened to me some years ago with a different phone, and it was a bad flash.
I resolved it by flashing the stock firmware again.
What did you flash with MiFlash? Stock firmware untouched? You must do this, try with B35 untouched. Don't flash stuff with TWRP.
Untouched? Is there anything on here like that?
https://androidfilehost.com/?fid=962187416754472312 B35 A2017U
https://androidfilehost.com/?fid=746010030569960045 B10 A2017G
https://www.androidfilehost.com/?fid=818070582850490196 B14 A2017CN
Those are "untouched" system images. Replace recovery.img with a proper TWRP version before flashing:
https://androidfilehost.com/?fid=673956719939822011
bornlivedie said:
https://androidfilehost.com/?fid=962187416754472312 B35 A2017U
https://androidfilehost.com/?fid=746010030569960045 B10 A2017G
https://www.androidfilehost.com/?fid=818070582850490196 B14 A2017CN
Those are "untouched" system images. Replace recovery.img with a proper TWRP version before flashing:
https://androidfilehost.com/?fid=673956719939822011
Click to expand...
Click to collapse
Yeah, unfortunately the very first link (since I am in the USA and have a U version) is the very stock EDL version I used with MiFlash rightg after I was successful getting the phone out of DFU. I have tried flashing it twice after and still nothing.
Thank you for helping!!!
djprez said:
Yeah, unfortunately the very first link (since I am in the USA and have a U version) is the very stock EDL version I used with MiFlash rightg after I was successful getting the phone out of DFU. I have tried flashing it twice after and still nothing.
Thank you for helping!!!
Click to expand...
Click to collapse
Sad to hear that... Maybe you can try again? Who knows, with a little bit of luck...
Or try another version, like this one:
https://www.androidfilehost.com/?fid=890129502657579386
btw, did you try every single spot in your screen while in TWRP? Maybe some pins in the connector are broken and some parts work and others doesn't?
And for the sake of it, you could try discharging your battery completely.
Last thing I can think of... is to restore the stock recovery and apply the official update via sdcard:
https://www.dropbox.com/s/xy7nd252f3rcm5y/338450B3220A2017UV1.1.0B35(SD card software).zip?dl=0
It was taken from here:
https://www.zteusa.com/axon-7#support
bornlivedie said:
Sad to hear that... Maybe you can try again? Who knows, with a little bit of luck...
Or try another version, like this one:
https://www.androidfilehost.com/?fid=890129502657579386
btw, did you try every single spot in your screen while in TWRP? Maybe some pins in the connector are broken and some parts work and others doesn't?
And for the sake of it, you could try discharging your battery completely.
Last thing I can think of... is to restore the stock recovery and apply the official update via sdcard:
https://www.dropbox.com/s/xy7nd252f3rcm5y/338450B3220A2017UV1.1.0B35(SD card software).zip?dl=0
It was taken from here:
https://www.zteusa.com/axon-7#support
Click to expand...
Click to collapse
Yeah, the entire screen works perfectly in TWRP. I disassembled it several times before when I thought I may have put it back together wrong or damaged something so, the battery was removed those several times therefore, no power.
I'll try the stock above. I'm actually trying another stock rom atm --- flashing from sdcard
djprez said:
Yeah, the entire screen works perfectly in TWRP. I disassembled it several times before when I thought I may have put it back together wrong or damaged something so, the battery was removed those several times therefore, no power.
I'll try the stock above. I'm actually trying another stock rom atm --- flashing from sdcard
Click to expand...
Click to collapse
Well, EUREKA! I found I had saved the first files you were supposed to load when the Axon was first unlocked ( file name STEP_1_3-B20_FULL_OTA). Flashed it and the screen works fine. Now, I have to remember how to update it...lol I've unlocked the bootloader in Developer mode and I should be on my way..... fingers crossed.
djprez said:
Well, EUREKA! I found I had saved the first files you were supposed to load when the Axon was first unlocked ( file name STEP_1_3-B20_FULL_OTA). Flashed it and the screen works fine. Now, I have to remember how to update it...lol I've unlocked the bootloader in Developer mode and I should be on my way..... fingers crossed.
Click to expand...
Click to collapse
Strange.
Nevertheless, congratulations. Happy for you.
Well, it's great that I now know the screen/hardware is fine but, I am unable to get any further than version B20. OTA doesn't work, the other files to flash (STEP_4-B20_to_B27 and STEP_5-B27_to_B29) won't flash and get aborted due to it expecting a certain version. I've tried DrakenFX Bootstack and then Stock System and it boots to the Welcome screen but the screen is no longer responsive again.
I have been at this all day again and it's shaping up another all night too. I am so baffled!
Restore to stock firmware your phone came shipped with.After that update trough ota or sd card package and maybe dont flash Treble again,its broken
djprez said:
Well, it's great that I now know the screen/hardware is fine but, I am unable to get any further than version B20. OTA doesn't work, the other files to flash (STEP_4-B20_to_B27 and STEP_5-B27_to_B29) won't flash and get aborted due to it expecting a certain version. I've tried DrakenFX Bootstack and then Stock System and it boots to the Welcome screen but the screen is no longer responsive again.
I have been at this all day again and it's shaping up another all night too. I am so baffled!
Click to expand...
Click to collapse
i wish i had seen this sooner, because i have this same exact problem on one of my boards. it will update perfectly to any of the MM sd card update files (see rootjunkys bl unlock video, thanks @Tomsgt) but the board/phone will not retain touch functionality on anything higher than mm b29. i had lost my imei on that board, and actually swapped to another one despite eventually regaining it simply bc i wanted to be on Oreo ROMs. if you find a fix, id love to know about it. i flashed and reflashed every update, sd card versions, edl versions, and OTA updates to no avail. Nougat or above, touchscreen didnt work... mine was a gold a2017u. good luck, man. im glad im not crazy.
Sorry to bump an old(er) thread I started. I wanted to ask if anyone has found a solution to this issue yet?
I have since tried updating using OTA to Nougat and the screen doesn't respond so, I had to flash back to Marshmallow B29. Thank you to anyone who might have an idea!

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