[Q] Bricked LG Volt - Research Questions - General Questions and Answers

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.

Related

Dropping data and no calls/texts. Advice please.

Just in case this post gets moved, I want to identify my device as the Verizon Samsung Galaxy S3 (i535).
To give a little background on my issue, I have an issue with the device. When I first got it back in July, first thing I did was root the device. Naturally, since it was a new device, I was working with experimental methods... a couple weeks ago I thought to download CyanogenMod 10.1 (nightly build) to flash it with 4.2 and rid myself of the persistent OTA update that as we all know could not effectively install because of the measures I took to root. So, I boot into recovery and flash my custom rom. BAM! As it turns out, I did not have an unlocked bootloader and my phone was now teetering on the verge of being a $600 paperweight. I got that dumb yellow triangle saying unofficial firmware detected or some nonsense like that... Anyway, I look around the internet and decided that I was going to revert back to a stock rom using Odin, and then proceed to unlock my bootloader and root the device (I followed method 3 here) I used some touch recovery console that I have never heard of before (backups incompatible with ClockworkMod recovery) and something must have failed because my back up would not flash. I took the hit on losing most everything and reflashed successfully the custom rom mentioned earlier.
After about a week, I noticed the device began to drop data. 4G would just stop at random parts of the day, and I would have to disable and enable the data to get it to reconnect. At this point I was still able to make and receive phone calls and texts. After about 3 days of this, I concluded it was more than likely a bug in the custom rom, and that I could not live with it... so I redid the a fore mentioned tutorial and left the phone as a stock/unlocked/rooted device. The data issue continued, but with a twist. I was now unable to make or receive phone calls or texts. No matter what I did, I could not do anything and the 4G would only stay connected for a matter 5 minutes or so. When I logged into my vzw account, it identified my device as an unknown non-verizon device. Customer service walked me through various soft/hard reset techniques and nothing worked. They also suggested I try a new SIM card, which failed to work.
So, I turn to the bright minds of the android community. I have already decided not to invoke the Verizon warranty offered, where the result is they take my malfunctioning phone in flawless cosmetic condition and replace it with a "like-new" phone in working condition, because I think it's garbage that a warranty would give out used crap (should fix or replace). I have not contacted Samsung customer support yet because I wanted to see what my options were. I've already attempted flashing different radios and nothing seem to make any difference. If I have to, I will revert it back to stock again and invoke Samsung's warranty program, but I would much rather keep the phone. As it sits, I am stuck with my Motorola Droid Razr Maxx, and that just doesn't cut it.
So I ask, is there anything that can be done? Anyone know of a fix for my situation? I saw something about this in my quest for an answer and I don't know if my situation is a fit for this fix. If anyone has any knowledge of my issue and a work around for it, it would be greatly appreciated. I am at my whits end.
It sounds like you've done your homework on your problem.. The only thing in your post I didn't see was your sim card.. Maybe pulling it wait 2min restart. Shut down and insert,, or maybe a reprovision of the sim may be in order..
Ahaaaa....!!!
If your IMEI is intact, I would say to flash to ICS and reprovision the phone as suggested above. If it is not, you need to restore it with that backup that you made some time ago.
If it were me, I would reprovision, that is easy to do and I honestly think that it will work for you. If that works for you, reroot and restore your backup for TW ROM and you will be fine.
HHF2 said:
If your IMEI is intact, I would say to flash to ICS and reprovision the phone as suggested above. If it is not, you need to restore it with that backup that you made some time ago.
If it were me, I would reprovision, that is easy to do and I honestly think that it will work for you. If that works for you, reroot and restore your backup for TW ROM and you will be fine.
Click to expand...
Click to collapse
Well that's just it... I don't know anything about the IMEI and how to determine if that is the issue. If by reprovision you mean reflash back to stock, that is it's current state, and that did not resolve the issue.
As for the other comment in regards to the SIM card... I have already attempted that method, and it did not work. Also, a new SIM card was also tried, and had no success.
mkruluts said:
Well that's just it... I don't know anything about the IMEI and how to determine if that is the issue. If by reprovision you mean reflash back to stock, that is it's current state, and that did not resolve the issue.
As for the other comment in regards to the SIM card... I have already attempted that method, and it did not work. Also, a new SIM card was also tried, and had no success.
Click to expand...
Click to collapse
Google reprovision, it is a number combination that you enter on the keypad that resets your phone. I had a similar problem that you are having and that fixed our for me. You also need to know that when you do this, it will erase all of your information on the phone. It will be just like it was when you unpacked it and powered it on the first time.
You will have to be on ICS because they removed the option to do this with JB. Just search for the code to enter and you will be fine.
HHF2 said:
Google reprovision, it is a number combination that you enter on the keypad that resets your phone. I had a similar problem that you are having and that fixed our for me. You also need to know that when you do this, it will erase all of your information on the phone. It will be just like it was when you unpacked it and powered it on the first time.
You will have to be on ICS because they removed the option to do this with JB. Just search for the code to enter and you will be fine.
Click to expand...
Click to collapse
Ok. So I tried the reprovsioning mentioned above. When my phone rebooted I was on data and able to make phone calls. Score! However, I checked the IMEI and it said 0. So, thinking that it was just a matter of time before my device began to stop working again... I did the IMEI fix. Now my phone is placing calls and holding data without issue. The OTA updates are flooding in and installing without issues.
I would like to point out, while I feel better having done the combination of both reprovisioning and IMEI fix, ultimately the initial reprovisioning did appear to resolve the issue.
Thanks to everyone for the assistance provided.

[Q] Soft bricked...?

Hey Xda Devs. This is my first post to this wonderful site. (sorry if in wrong area)
Back to related topic....
I own a Samsung Galaxy SIII - (SCH-I535)
About Three or Four days ago I was sick of using my Cyanogenmod 10. And I decided to do a Factory Restore on it. (Got sick of short battery life and terrible reception)
While doing this it was great (still rooted and running cyanogenmod). Then I got a little stupid and decided I didn't want any Google search in/on my device. So I went and deleted most the apps associated with it. NOT KNOWING it would disrupt my Data / Wi-Fi / and Play Store. (Google store has Unexpectedly Stopped)
So like an idiot, I factory restored AGAIN thinking "maybe it will just go away"
No....
In fact did the inevitable and decided to take out Clockwork Mod and anything else in my SD card thinking maybe that was the reason.
(At this time it was still working ((Send/Receive Calls, Text, and Pics.))) But no data.
Then while on my break at work I put my phone into Clockwork (somehow it was still in my phone) unknowingly I seen a backup. So like any noob I went and clicked Wipe Cache + everything else then prompted with a Recovery.... Well that only made matters WAY worse....
I now sit with a phone that no matter what I do, I can only get into ODIN mode but if left to boot it shows an UNLOCKED Custom Samsung screen but sent to "System software no authorized by Verizon Wireless has been found on your phone. Please....ETC"
I have tried to flash the same way I did but no luck. I tried stock ROM. ODIN always says RESET!!! But does nothing after like it’s just a paperweight now.
I somehow now instead of having 1 custom binary download me have 3....
Everything else says CUSTOM
And Qualcomm secure boot says ENABLE
I’ve been looking for a way to bring it back to just stock ROM.... but no luck on any form, site, or anything!
PLEASE HELP! im sick of using my Droid RAZR M

I think I've bricked my phone and am not sure what to do

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.

Stuck in a bootloop + CWM question

Edit: Solved, see bottom
ROM (D6633_Customized HK_1290-5630_23.4.A.0.546_R6C_HK_SuperSU2.46_XZDR2.8.21-signedv2)
Bit of a dumb move on my part. It all started when my snapchat stopped working, I updated, and then Titanium Backup wouldn't restore the data properly (giving me "parse error"). I was trying to fix that and read online that sometimes this is caused by improper permissions, so I booted into recovery mode, couldn't find the option, but somehow decided "hey, maybe my root permission (?) is wrong slash it's 6am and I just watched a wild 2016 election end" and I hit the button. Now my phone is stuck in a bootloop.
So my question:
1) What exactly does re-root phone do (in CWM), and why would that have messed me up? Is it because I have a pre-rooted rom?
2) I wiped cache and delvik and it doesn't help
3) How do I fix this? I was thinking of loading a SuperSU zip on the SD card from my computer and flashing that, assuming somehow a corrupted root is at fault. I can't seem to get the thing in ADB mode as a side note.
3b) If that seems like a good idea, does it matter what one I use?
4) If I reflash the ROM, it should keep my apps and stuff, ya? I don't actually care if my phone is crippled, I just need it to work long enough to properly back up some media, and mainly get my whatsapp over to my new SIM card. If I can't get in it's forever stuck on my old number which I don't have the SIM for anymore.
Any help would be GREATLY appreciated.
Edit: I don't know how to delete this. Anyways, with other resources I found out that because I used a pre-rooted ROM, there were issues with using CWM to try to do the rooting with its built in functions, softbricking the phone. Reflashing the original pre-rooted ROM worked fine.

Data recovery after clean install / format phone?

Hey all,
I've got a question. Most likely a question I know the answer to and I'm in denial. My phone crashed on vacation and wouldn't boot anymore. Not sure how it append but it did. A software failure. After many attempts I've tried to recover some of my vacation photo's an video's. (luckily I've added a cloud sync before going on vacation in case of theft and havn't lost all) In the restore attempts I've soft bricked my phone (from bad to worse) And had to make a clean install with odin. I've installed a clean Stock Rom and rooted it with Magisk (supersu resulted in bootloop). I've tried a few recovery programs from the first page googleling. But no results.
I'm pretty sure the previous version was encrypted and I'm hitting a dead end here.
As for my question: Have I've really given myself the answer not getting it back because of the (possible) encryption or are there better recovery options?
As soon as you started writing over everything with a new flash, you effectively became SOL. There's likely nothing left to recover.
Even before that, while recovery might have been possible, you wouldn't have liked the price tag.
Yeah, thanks. I've figured that. By now I've accepted the fact that I've lost the content and moved on.

Categories

Resources