I've somehow done something obscure with my phone (Error Code 7) partition problem? - X Play Q&A, Help & Troubleshooting

Hi Folks,
I've been lurking and getting great advice form this forum for many years but have finally come up with something I can't fix myself.
I was running a few custom roms but somehow when trying out a few of them I have managed to do something so that I can't flash any custom roms any more.
TWRP which gives an error 7 message (which seems to suggest that my phone no longer thinks it is a moto x play). At present I can install stock roms using ADB but that seems to be about it. I have tried to roll back using a stock rom from the motorola website (LUX_RETLA_DS_LPD23.118-6.1_cid12_lux_retla_ds) but that didn't fix it.
I also can't seem to root my current stock rom (XT1562_LUX_RETEU_6.0.1_MPD24.107-52) but am sure I was able to before i had this problem.
I can't help but think I probably should be grateful that whatever i did didn't brick my phone but I've been trying every idea I can find that over the last few months and nothing has helped. I get the idea it might be some kind of low level partition issue but that is just a desperate hunch. From time to time I've got what seem to be partition errors when try various roms to fix this but they've usually worked their way out.
Any hints or suggestions on how to rectify this would be most welcome.
N

Related

gapps/google talk/market/acore crashing/not working

Hi all, i have been having a very bazaar problem lately...When my phone boots up i get a pop-up message indicating that the gapps process shutdown unexpectedly...and sometimes i may even get a acore crash too. Applications from the market do not download...when i select my download i will end up getting a gapps crash and then the supposed download just sits there saying "starting...". Google talk doesn't even open! It will just say that the process quit unexpectedly. Even after a fresh install with factory data reset all these problems will continue. The initial boot up screen/tutorial will even show a gapps crash. I have tried with 3 different versions of cyanogenmod all with the exact same problem..Each version i've tried with a2sd enabled and disabled, formatting the partition each time before a new install to ensure no data carry-over issues. I don't know what to do. To me it seems like it make be something on googles side...but i can't for the life of me figure out whats causing these wild problems. Help would be very much appreciated.
ANDROID Market problems
I've recently had the same problem with the market getting stuck on "starting download". I thought it was something I modified as I'm putting together a STARGATE theme of my own based on kron2's work with this site and the theme for "Open Home" for DWANG's newest ROM. What worked for me was going back 1 restore point at a time till I found one that didn't have the problem (NANDROID backup). I also had luck with flashing DWANG's original unmodified ROM 1.17.1. I had the same problem when I flashed 1.16 ..weird. Up till 2 days ago I didn't have any problems changing anything in it. Others have said that they tried opening G-Talk at the same time and some how going between the 2 the problem would right itself. If you find out anything definite about what the exact problem is let me know as I'm going to keep looking for the answer myself.
six6star said:
I've recently had the same problem with the market getting stuck on "starting download". I thought it was something I modified as I'm putting together a STARGATE theme of my own based on kron2's work with this site and the theme for "Open Home" for DWANG's newest ROM. What worked for me was going back 1 restore point at a time till I found one that didn't have the problem (NANDROID backup). I also had luck with flashing DWANG's original unmodified ROM 1.17.1. I had the same problem when I flashed 1.16 ..weird. Up till 2 days ago I didn't have any problems changing anything in it. Others have said that they tried opening G-Talk at the same time and some how going between the 2 the problem would right itself. If you find out anything definite about what the exact problem is let me know as I'm going to keep looking for the answer myself.
Click to expand...
Click to collapse
I have searched and it seems many people have the Market/Gtalk problem.
I have the same problem (with an Eclair 2.1 Cyanogenmod rom) and I've not been able to find a solution. Wiping the cache makes nothing.
Anyone knows how to solve it?
Huh. I had a problem with the market at first with cyan 5.0.8 . I went in the terminal and ran fix_permissions after su and haven't had any problems since. Might try that
Sent from my HTC Magic using XDA App

(Bug Help Request) MIUI - Shiro - Inconsistent "No Service->Service->No Service" Bug

(Bug Help Request) MIUI - Shiro - Inconsistent "No Service->Service->No Service" Bug
Hello all! Hoping to find some help for the problem which I have been dealing with for the last month and a bit or so.
I have a 1337m (Canadian/Bell SGS4) which I have flashed with the i9505 MIUI rom as they have the same specs and can be used more or less interchangeably, or so I have been advised over the past year or so.
Anyways, I had recently updated my MIUI version with one of the latest ones, "miui_i9505_shiro_5.9.4_17da645643_4.4", and then have also recently updated it with no problems to MIUI 7 (5.10.2 Beta).
The whole time though with this rom I have been dealing with having "No service" come up quite often, and then bouncing between getting mobile data and then going back to "No Service" for absolutely no reason (With other roms I have been getting constant Mobile Data connections on the same routes so I know it isn't an issue with my phone's hardware or data connection, and it must be the ROM). I have also searched around a bunch for this bug and have come across some threads mentioning the same problem, and people had mentioned that when the recovery was changed, or a certain kernel was changed, this " 'No Service' appearing when service is actually there, however locking out applications from said data connection" bug is fixed, however I don't claim to know the most about more advanced things like swapping kernels, or changing recoveries, etc. I have also heard that people were talking about how all of Shiro's ROMs for the i9505/SGS4 seem to have this problem, so hopefully I am not alone with this. Also, my APN settings are not grayed out if that happens to have anything to do with the whole thing and something can just be quickly changed there to fix it? (Sorry, I have no idea what the true problem with this issue is).
I am just a little worried that at some point in time when I really need to make a call or use the net and I can't at that exact time due to this bug that it may really complicate things... therefore I am hoping to get a hand with fixing it and understanding how I can monitor and fix this for any future issues as well.
Hopefully I can get a hand with this from you guys! It would be much appreciated!
TL;DR: MIUI Shiro i9505 Rom user with "No Service" bug looking for help on how to fix it; have heard that it is indeed a common problem with Shiro Roms, and also that it may be kernel or recovery related? Also, my APN settings are not grayed out if that happens to have anything to do with it and something can just be quickly changed there?
Thanks in advanced for any help, guys!
Flash with philz recovery resolv the problem
Enviado desde mi SM-T535 mediante Tapatalk
luistro said:
Flash with philz recovery resolv the problem
Enviado desde mi SM-T535 mediante Tapatalk
Click to expand...
Click to collapse
First of all, thanks for the quick reply!
I believe I tried with one .zip package and it wasn't flashing properly from within CWRM... I even placed it on my internal as I heard a lot of people recommending.
Any chance you might be able to direct me to the correct build/package I should be trying to flash, and also a few quick steps on how to go about flashing it? If it's just "update from .zip" in CWRM I'm alright, but if there's more too it I would appreciate any extra help! Also, it's just flashing the recovery so there shouldn't be any changes to data on my phone, (applications, etc.), meaning no need to full wipe.... correct?
I'm guessing I should be following the "Method #2 for rooted phones with CWM/TWRP Recovery" section in this thread which talks about flashing philz for the SGS4? Am I right in assuming that since I am running MIUI and have Clockwork Recovery pop up when I go into recovery mode, this would be the right one?
Sorry for all the noob questions... I just want to make sure I am doing the right things here.
Looking forward to your reply!
Just a quick update of where I'm at:
I have the latest version of Philz on my external, and have attempted to boot into recovery and install the .zip from my external sd, but I get the following error message string in CWM:
Code:
Flashing Recovery
assert failed: run_program("/tmp/loki.sh") == 0
E: Error in /external_sd/Roms/philz_touch_6.59.0-jflte.zip
(Status 7)
Installation aborted.
Looking for a hand! I'll try to flash it from internal storage also just in case that happens to work.
Update #2:
Just flashed with Odin as attempting to install from .zip on the internal brought up the same error message.
Everything seems to be working alright now!
Hopefully this thread / my replies can help out anyone else in a similar situation!

Big problems with my Ascend G7-L03

Hello everybody,
I'm relatively new to the world of ROMs and I'm hoping some people smarter than me can help.
A few weeks ago, I started having issues with my phone, on the stock ROM for Wind Canada, restarting continuously. It would sometimes work for up to 10 hours, but sometimes no longer than 10 seconds. There didn't seem any rhyme or reason to it doing so. I figured that it was a good time to play around with a new ROM, and I took a backup (of a faulty operating system). It's been a bit of a ****show since then, and I don't remember exactly everything that I've tried, but here is a sampling:
CM13.1 - the ROM successfully loads, but then I get stuck in a reboot loop.
CM12.1 - I figured that if 13.1 didn't work, I shouldn't try 14.1, so I went down to 12.1. This worked beautifully, until I tried to make a call - and I can't hang up. To hang up, I need to reboot the phone. Annoying, to say the least. Everything else seems to work really well, other than a slightly shortened battery life, but I can live with that, if everything else works.
CM14.1 - I tried loading it, but it says right off the bat that the L03 isn't part of the compatible list and doesn't process. I know I can suppress that message, but I figured that if it was meant to be on that list, it would be.
Resurrection 5.1 - I don't remember what happened here, but I think it ended up in a bootloop.
I can't find the original ROM on Huawei's site, and the one that seem similar for different countries are meant to be done within the OS as an update (Update.app).
So, I'm stuck here - I can't seem to revert back to the original ROM (which was Android 4.4.4, which was fine), and I can't seem to update to any other ROMs. I want to fix this, because as far as I'm concerned, the hardware is pretty good and I can make this phone last. However, my wife is pushing me to replace it...
Does anybody have any advice as to what I should try next? I really don't feel like using CM12.1 in its current state, which is what is installed now, since I need to reboot between phone calls, but it seems to be my only option for now.
Three notes - 1) I am currently on my 5th or so install of CM12.1. I have tried to look for ways to replace the dialer, since that seems to be the problem, but I haven't found a way. Can one replace the stock dialer?
2) I have tried installing multiple GAPPs packages, including ones that supposedly replace the dialer, but this hasn't helped.
3) I don't know if this is relevant, but in CM12.1, under "About phone", my Device model is "unknown". Is that always the case?
Somebody out there must have a better solution and my hair's all gone now, from me pulling it out...
Any help you can give me is appreciated!!!
Thanks,
Steve
UuUuPpPp....
Exactly in the same boat as Steve...... "Cant hang up" is seems to be the only major problem.....i have the exact phone too.....and tried same things too to no help....any help wud be appreciated...

Bootloop and radio issues

Hey there,
Ever since flashing a new rom I've been experiencing a few issues. First, my phone refuses to boot to system, I've had to go through the bootloader to get it started every time.
Second it would appear that my radio is off as the phone won't connect to the network and thinks its in aeroplane mode. I haven't been able to get it working yet.
The Rom I flashed was the nougat update. , I've tried several others since as well as restoring through twrp. No dice, but I'm currently on lineage 15,1
I've yet to find a solution to either of these issues in a week of searching so I'm looking for any sort of guidance.
Thanks in advance
motoplayguy said:
Hey there,
Ever since flashing a new rom I've been experiencing a few issues. First, my phone refuses to boot to system, I've had to go through the bootloader to get it started every time.
Second it would appear that my radio is off as the phone won't connect to the network and thinks its in aeroplane mode. I haven't been able to get it working yet.
The Rom I flashed was the nougat update. , I've tried several others since as well as restoring through twrp. No dice, but I'm currently on lineage 15,1
I've yet to find a solution to either of these issues in a week of searching so I'm looking for any sort of guidance.
Thanks in advance
Click to expand...
Click to collapse
You should return to a pure stock configuration (including recovery) and start over, preferably using RDS Lite. It won't be easy as there are no giudes written explicitly for the G4P. You will have to derive the procedure by reviewing other threads.
A less comprehensive approach is detailed in the following thread but it may not solve your radio issue.
https://forum.xda-developers.com/g4-play/how-to/guide-return-to-stock-firmware-recovery-t3551797
As for not booting to system that's likely due to a procedural error when twrp was first flashed. Check the TWRP threads for corrective action.

Dual Boot Patcher issues while flashing

Hello there!
I recently came out on a post about Dual Boot your android device.
This seems really handy to me so i was willing to try it.
I rooted my S7 Edge, i have Magisk installed and the Dual Boot Patcher.
I tried tons of roms like: DOTOS, RR, LineageOS, Ice Projects and so on.
Everytime when i try to flash the zip i patched it gives me an error.
But every time another error.
For example with Dot.OS i got:
Failed to copy /raw/data/,system.img.tmp to /raw/system/multiboot/dual/system
But when i try for example LineageOS the app just stops working.
Also i tried some other roms which gave an error about the system check. If my device was compatbale with the ROM.
I saw alot of issues about that online so i tried all those fixes but nothing seems to help.
I tried to delete the Asserts line from the updater-script. How ever only 1 rom i downloaded got these lines in the file.
I am really stuck and have no idea what to do now.
Is this because of my phone? Do i need to install another APP or anything to fix this issue?
I really wanna install this Dual Boot. And i saw many people successfully flashing on S7 Edge. So its pretty strange it doesnt work for me...
If there is some one with a solution or maybe someone that wanna take a look with me to fix my issue woukd be highly apprecieted!
Also i dont mind to pay a few bucks to a dev or anyone with more knowledge to take a look and try to fix this issue with me if no one else can!
Thank you in advance! Please let me know if you need more information about these issues and please tell me which info.
As i had no idea what to all post here to make it easier to locate the issue.
Thank you all!

Categories

Resources