Hey all, before I start I'd like to apologise for making the post here but I don't know what you guys would classify the state of my phone as, "bricked, soft-bricked, hard-bricked", I have no clue! As a result I have no idea what threads to start looking in so I've come here to make this, sorry again!
I'm here looking for help because I think I've completely destroyed my Moto G and really really would like to fix it.
Basically, I had been running an old version of CyanogenMod for months and was not able to update due to the fact my bootloader was not updated. After finally updating it through a tool on XDA, I installed the newest version of CyanogenMod onto the phone and it was all going well, except for the fact all of my Google apps were crashing and making it impossible to use.
Now, I'm not sure why, but without taking any precautionary measures or looking into it at all or what I needed to do, I then decided to try and flash a Paranoid Android rom onto the phone, which installed fine. I load the phone up and something comes up with a passcode saying I need to unlock it to use the phone. I put in some random things and eventually get it, but it says my data is corrupted and therefore I need to reset to factory settings and there's a button there to do it. I think "why not" and click.
So now, the phone did something weird and basically went into a bootloop of the PA logo, so I restarted the phone and went to the bootloader thing. When doing "Normal Startup" it loads the phone with the PA logo like before, comes up with a brief "Android is Upgrading" screen before showing me the passcode screen for half a second, before repeating this, thus having a bootloop. Every so often, I can put my code in and press the reset button again, but it does the same thing.
On the other hand, if I try to access my ClockworkMod recovery system, the screen repeatedly flashes with the CWM background of the Android Alien guy, as if to say it keeps trying to start but it cannot.
TLDR: I cannot access my phone through a normal powerup or through my recovery, have I screwed it completely?
I'd hugely appreciate any help here guys because I'm stressing like I never have before here, thanks!
EDIT: it is the X0123 version!
Spaciouz said:
TLDR: I cannot access my phone through a normal powerup or through my recovery, have I screwed it completely?
I'd hugely appreciate any help here guys because I'm stressing like I never have before here, thanks!
EDIT: it is the X0123 version!
Click to expand...
Click to collapse
Just a few questions before I start suggesting a full flash to stock.
Did you have any SIM passwords, boot passwords, CWM passwords before flashing?
Also In CWM does it flash before any options are selected and did you dirty flash the new ROM over the old ROM?
Anyway, your phone is not hardbricked as it can get to recovery so thats good news.
I would suggest flashing your phone back to factory stock using the tools here on XDA (http://forum.xda-developers.com/showthread.php?t=2542219). That should hopefully resolve most of the issues and then if you feel like it you can start flashing custom ROMs again.
Related
So here is the situation.
Regardless what Rom I flash, the phone works fantastic up until the first time you try to reboot it. At that point it gets past the samsung flash screen and gets stuck on the flash screen of whatever rom I'm running. I've even left it on like that for an hour and it never changed. The only way I'm able to get out of this is to reboot into recovery with a battery pull and do a data/internal storage wipe.
I've even tried odin'ing to stock and when it goes to reboot the phone to reset it gets stuck at that screen.
From recovery if i wipe everything and install the rom fresh it works great. Any ideas what is messed up or corrupted? Gets kinda old having to reset everything just because phone needs to reboot lol.
xRelapse13 said:
So here is the situation.
Regardless what Rom I flash, the phone works fantastic up until the first time you try to reboot it. At that point it gets past the samsung flash screen and gets stuck on the flash screen of whatever rom I'm running.
Click to expand...
Click to collapse
I have pretty much the same issue with any ROM other than the stock Verizon. I can restore that and everything is fine. I can flash a ROM, flash GApps (if needed) and everything is fine...but restart and yep..hangs at splash screen. If I try a standard wipe data, it fails. I have to do a format of internal memory and then I can proceed to restore or reflash. Kind of a pain in the ass because I really want to run something other than stock. Whoever can solve this problem will be a hero!
Maybe this will help you
Might be a bad partition, a rare problem to all. Maybe this will help you, do this at your own risk. Read first the thread before making a move.
[HOW-TO] Unbrick your soft bricked Galaxy S III (+ bootloader brick)
Note: You know the responsibility when you root your phone, I am not nor them who created this thread have responsibility to your phone, it is your choice.
skyss07 said:
Might be a bad partition, a rare problem to all. Maybe this will help you, do this at your own risk. Read first the thread before making a move.
[HOW-TO] Unbrick your soft bricked Galaxy S III (+ bootloader brick)
Note: You know the responsibility when you root your phone, I am not nor them who created this thread have responsibility to your phone, it is your choice.
Click to expand...
Click to collapse
Gonna go ahead and read through that and try it, not much to lose at this point. I'll keep you guys updated if it works or not
xRelapse13 said:
Gonna go ahead and read through that and try it, not much to lose at this point. I'll keep you guys updated if it works or not
Click to expand...
Click to collapse
Please do...I am interested to see what happens but not ready to try it yet as I am going on vacation and need my phone at the moment instead of bricking it...LOL
I actually had this problem when I just did the regular wipe in TWRP (the one that maintains the internal SD card). When I did an advanced wipe and did everything, excluding the recovery and external SD, things went back to normal.
Used the Unbrick thread and it fixed the problem. Thanks!
Just wanted to post this update for anyone else who had the problem.
Hey there team. I've been a long time lurker here and might not have made many posts. Getting this phone and given my time flashing, rooting, and following guides here, I really want to start getting in on the conversations and discussions. Let me go through with what happened to my last LG Volt...
I had successfully rooted the device using towelroot and been playing around with the usual root access apps. I had superuser, busybox, etc. What I came across as a problem with the device was it's RAM usage on a lot of apps and the problem was largely just OS (after purging a lot of apps off the device). The biggest problem I was having was with Skype crashing and ending calls anytime you switched out of the Skype app itself.
Being the idiot I am, I began looking into possibly using SWAP memory to try to extend my RAM a little to see if I could correct what Skype was doing (assuming it was a RAM issue, which, now thinking about it, I don't think it was because my EVO V worked fine [On custom roms granted]). So I tried doing some swap stuff and it overall just would not go. I figured it was a KitKat issue involving the SD Card and how the file structure on the LG Volt seemed to handle SD related stuff, all going to emulated memory. So. I decided it wasn't worth the trouble and research anymore, and considering not too much work had been done on the Volt yet, I decided to give up that campaign and wait for more research to get done.
In the mean time, I told the phone to do a factory reset so I can start back fresh and go about using the device normally. This might have been where I made a mistake. I told the device to factory reset and format everything through the Android OS instead of booting into the stock recovery and telling it to do a factory reset. The phone shut off and never came back. I was not able to get it to charge, I could not enter LG Download Mode, I couldn't get into the recovery, absolutely nothing. Tried seeing if I could use the LG Mobile support tool to push anything to the phone since my computer could still see the phone connected... No luck.
So, my questions to the team here on XDA is:
1. What exactly happened to cause the phone to start the factory reset, but, lose everything? I could only assume that the phone kicked the system, data, boot, recovery, and... well.. everything off and fried it's memory. I assume it had to do with what I was trying to do with swap memory and something getting seriously messed up.
2. More specific on what the phone did after, it would not turn on, charge, go to recovery, or download mode. It was completely unresponsive. Would there have been a way to resurrect this phone back from the dead that I wasn't able to find after all the looking and research I had done?
3. With the new LG Volt I recieved from Virgin, how safe would you say things would be to go about rooting again and being more careful with my apps while I wait or get involved with some of the future ROM development for the device?
4. Is there something with how LGs recovery and download partitions are set up that would cause these to be unable to function? Or something that is particular to the LG Volt?
Finally, 5. I noticed that the work done and the team researching the Volt right now have managed to get an unlocked bootloader and a custom recovery that works. Would it be safe with the research done now to go about unlocking and flashing the custom recovery on?
These questions all take into account common knowledge stuff such as, the potentially to brick a phone again is always there and to continue doing as much research and reading as I can to know what I'm doing with the device accurately. Hope my questions can be answered here, until then, cheers gentlemen.
marth141 said:
Hey there team. I've been a long time lurker here and might not have made many posts. Getting this phone and given my time flashing, rooting, and following guides here, I really want to start getting in on the conversations and discussions. Let me go through with what happened to my last LG Volt...
I had successfully rooted the device using towelroot and been playing around with the usual root access apps. I had superuser, busybox, etc. What I came across as a problem with the device was it's RAM usage on a lot of apps and the problem was largely just OS (after purging a lot of apps off the device). The biggest problem I was having was with Skype crashing and ending calls anytime you switched out of the Skype app itself.
Being the idiot I am, I began looking into possibly using SWAP memory to try to extend my RAM a little to see if I could correct what Skype was doing (assuming it was a RAM issue, which, now thinking about it, I don't think it was because my EVO V worked fine [On custom roms granted]). So I tried doing some swap stuff and it overall just would not go. I figured it was a KitKat issue involving the SD Card and how the file structure on the LG Volt seemed to handle SD related stuff, all going to emulated memory. So. I decided it wasn't worth the trouble and research anymore, and considering not too much work had been done on the Volt yet, I decided to give up that campaign and wait for more research to get done.
In the mean time, I told the phone to do a factory reset so I can start back fresh and go about using the device normally. This might have been where I made a mistake. I told the device to factory reset and format everything through the Android OS instead of booting into the stock recovery and telling it to do a factory reset. The phone shut off and never came back. I was not able to get it to charge, I could not enter LG Download Mode, I couldn't get into the recovery, absolutely nothing. Tried seeing if I could use the LG Mobile support tool to push anything to the phone since my computer could still see the phone connected... No luck.
So, my questions to the team here on XDA is:
1. What exactly happened to cause the phone to start the factory reset, but, lose everything? I could only assume that the phone kicked the system, data, boot, recovery, and... well.. everything off and fried it's memory. I assume it had to do with what I was trying to do with swap memory and something getting seriously messed up.
2. More specific on what the phone did after, it would not turn on, charge, go to recovery, or download mode. It was completely unresponsive. Would there have been a way to resurrect this phone back from the dead that I wasn't able to find after all the looking and research I had done?
3. With the new LG Volt I recieved from Virgin, how safe would you say things would be to go about rooting again and being more careful with my apps while I wait or get involved with some of the future ROM development for the device?
4. Is there something with how LGs recovery and download partitions are set up that would cause these to be unable to function? Or something that is particular to the LG Volt?
Finally, 5. I noticed that the work done and the team researching the Volt right now have managed to get an unlocked bootloader and a custom recovery that works. Would it be safe with the research done now to go about unlocking and flashing the custom recovery on?
These questions all take into account common knowledge stuff such as, the potentially to brick a phone again is always there and to continue doing as much research and reading as I can to know what I'm doing with the device accurately. Hope my questions can be answered here, until then, cheers gentlemen.
Click to expand...
Click to collapse
1. im not sure what is going on lately, but there seems to be an influx of jacked phones lately from botched modding and attempting to fdr to fix it.
a note for future reference, a fdr will fix nothing you did that required root. so if you mess something up, just go right for the stock flash to try and fix it, if it can be fixed.
2. i doubt it.
3. i would go for it.
4. cant answer that, sorry.
5. absolutely, as long as it is stable.
any body knows how te get correct spc or msl..i try with meid converter but wrong msl..please.
So I had cm12 installed and something happened to where my.phone was lagging so I said screw it and reflashed, while something happened and now I tried to while everything. Well I think I did something wrong because I lost all my apps in the app drawer,but when I go into file manager all my stuff is still there,but now the last couple times I tried to reboot the charging light was flashing red to yellow, but when I take the battery out and put it back in it reboots fine back to the screwed up home screen. Still with all my apps and pictures. Viewable in file manager.someone please help I'm freaking out thinking my phone is screwed up for good ....
Very hard to understand you. What ROM did you flash to now? Does TWRP work, can you get into TWRP?
Yes I can get into twrp,basically it threw me back into my cm12 ROM with none of my apps,and I tried to reflash Google apps and it didn't work,so if I can get into twrp is there a way to fix this by doing like a general full factory reset? And if so exactly how do I do that? I dunno this sucks....I dont wanna try anything else until I kinda have an idea what to do, don't wanna screw it up anymore
kjhrezjr said:
Yes I can get into twrp,basically it threw me back into my cm12 ROM with none of my apps,and I tried to reflash Google apps and it didn't work,so if I can get into twrp is there a way to fix this by doing like a general full factory reset? And if so exactly how do I do that? I dunno this sucks....I dont wanna try anything else until I kinda have an idea what to do, don't wanna screw it up anymore
Click to expand...
Click to collapse
If you don't know how to factory reset you probably shouldn't be flashing in the first place. I highly suggest just doing a clean flash and flash Gapps right after you flash CM 12. In order to wipe data, you just click wipe in TWRP.
No I know how to factory reset lol.it's just I did that and when it would go to restart I got little error code up in left hand side of screen. But it doesn't matter because thanks to androidrootz I downloaded New firmware connected it to pc and completely reinstalled operating system. So I'm not rooted or anything and I'm back to square one, .but much better than where I was at.
If your custom Rom was bugging out it could have been a corrupted download. Sometimes all you can do is start from scratch. If you want to flash custom, you need to expect these things. Remember that this is a development site. I have seen where the same Rom acts differently on the exact same phone model. This could be due to a variety of things such as microscopic differences in hardware (this is one of the reasons phones of the same model handles being overclocked more our less than others), settings, tweaks, or apps installed.
Hey guys, I was gifted a transformer tf700t, well I tried doing custom ROM's or some **** or tried putting a new OS on it, and now it's all ****ed up. It tries to boot into "Cromi-K" or some ****, but I can go into recovery I think it's called and use TWRP or the other popular one and flash images, only I don't know what images to flash to just get it back to stock, and every image I try it fails to flash it.. even after I clear cache and clear everything else. All I want is it back to stock and running again. I'll pay like $10 BTC if that's allowed if someone can help me. I also dont know anything about using commands from the PC and pushing it to the tablet.. so..
If you can help, my Skype is: Goldstingz
Thanks
this happened when i rooted, installed freedom, left freedom on, and reformatted, then it ****ed up. so i tried crombi. and idk ive tried a lot.
I have a well and heavily used Galaxy S5 (GM-900P) and about 2 months ago it started accting up pretty hard. Becoming very very slow so I decided to update to the latest sprint firmware and install a new(er) rom ([ROM][QD1][6.0.1]14Dec2017] Stock-ish Plus Tidbits and Magisk) and all was good for about 5 days and the phone started having apps crash/force close like crazy and most the time just reinstalling them would fix it but a bunch of google play services would crash and would have to uninstall the updates then it would work again for a day or so, sometimes it would randomly restart and get stuck at the boot screen and the phone would get crazy hot and the only way out of it was to boot into the recovery and then reflash the stock firmware in odin again then reinstall the rom. Then I had my phone all of a sudden act like there was no sim card in it and originally though it was a sim card issue but turns out it wasnt, I had to boot into the recovery and do a full wipe of everything reflash the stock firmware yet again and then reinstall the rom again. That happened twice in a matter of a week. At my wits end I decided to give LineageOS v16 a try so I boot into recovery, do a full wipe, boot into download mode, flash the latest stock firmware in odin, then boot right to recovery, flash LineageOS 16.0 then latest Magisk and all was great, for about a week, then Google services start crashing again and random apps crash over and over and even times the phone would slow down and reboot, get stuck at the boot screen and then eventually just reboot back into recovery by itself after failing to boot. But with LineageOS at least just reflashing the rom in the recovery will let it boot right back up sometimes and work as it should for another few days, other times too much stuff will just keep crashing so I do a full wipe and reflash LineageOS and all will be great for another few days to a week and it starts all over again. Its like stuff just randomly gets corrupted on the device and the only way out of it is to reflash the whole thing and start over and enjoy it until it does it again. Sometimes it will go days, sometimes a day later its all screwy again.
Also, TWRP always fails when I try to do a back up and it seems to always fail when in the data or data/private-app part of the system and its never at the same point.
I guess my question here is, could the onboard flash (the motherboard/logic board) be taking a crap on me? I really really dont want to give up on this phone just yet as it has everything I want in a phone and frankly, I just really really like it. I can get a new (used) motherboard for like $20 but even that kind of worries me cause I dont want to possibly be in this same position 3 months later again. I have a Galaxy S8+ (unlocked AT&T phone) that I refuse to use yet just cause I can not root it or unlock the bootloader.
Any help or ideas would be much appreciated and sorry for the long winded post.
could be wrong, on this one, But.....
If it was mew, I would go to stock . run that for a day, maybe 3... if all it well, then flash over what ever Rom you would like.
"KNOWING IT Work" is the key. Oh, another thing, that may help too . seen this on one of the LineageOS 15.1 or 16 is when you wipe ... System and Data, can be Reformatted, they have had some major success by also formatting it, (YES EXT4) but this will help to ensure nothing left over....
May even help with others Android 8.0, 8.1, 9.0....
Well, I have a new motherboard on the way so we'll see how that goes but I did manage to get the stock firmware on there and booted then I reflashed TWRP and then Magisk and going to just run it that way for a bit and see what happens.
I initially went in to TWRP, wiped data,system, etc... then flashed the stock firmware in Odin, then rebooted, got stuck at the Samsung boot logo so pulled the battery, booted to stock recovery, did a factory reset (Wiped everything, internal sd card included), then got it to boot, set the phone up, then rebooted to download mode, flashed TWRP, then rebooted again, set the phone up a bit more then decided to flash Magisk so I have root, and so far its working. 100% stock with magisk. Fingers crossed.
I still think there is an issue with the internal flash memory though as I can not get a TWRP backup to actually complete without failing. It always fails when backing up stuff in the data partition/section and never at the same point like its having read errors or something. I'll grab a TWRP log and post it up in a bit.
Well, that didnt last long. Within an hour, apps started crashing. I will make this thing work! LoL