Hi, Ive had this issue a couple of times where ive tried to either add or remove a system app and it bricks the current slot, each time ive ended up losing data when trying to fix it.
This time I bricked slot A but rebooted to slot B but lost root, is there a simple way to fix slot A again so I don't lose data/settings?
Thanks!!
Related
Hi, I just joined the Charge party today... coming from fascinate and have a few questions before i dive into flashing on this phone. My concerns are all related to reactivating the phone after factory reset or flashing roms since this is my first phone with a sim card.
1) Does the sim card need to be replaced after resetting or flashing phone??? If not, does the sim card need to be reactivated or does it stay activated???
2) Should the sim card be removed before resetting or flashing phone???
3) What is the process for reactivating because I heard you cant use the *228 method???
Thanks in advance
the sim card does not need to be removed before flashing, also doesnt need to be replaced after flashing!! and you do NOT use *228 that is not for LTE phones.
Rebooting the device is the equivalent to dialing *228 for LTE phones
I've flashed plenty of things for this phone and the sim card is never involved. The only time I've ever seen the sim card involved is when resetting the phone to stock ed2, but that's no longer necessary seeing as the ee4 method is out.
Beamed from my Droid Charge using the XDA premium app
blarrick said:
I've flashed plenty of things for this phone and the sim card is never involved. The only time I've ever seen the sim card involved is when resetting the phone to stock ed2, but that's no longer necessary seeing as the ee4 method is out.
Beamed from my Droid Charge using the XDA premium app
Click to expand...
Click to collapse
Thank you for your help.
Does the stock ed2 method require a new sim card???
Asking because sometimes it is necessary to use odin and repartition a phone if having issues coming from voodoo or other issues which simply flashing rom does not correct.
No you just need to remove the sim card. I haven't seen any guides or any posts whatsoever on xda about anyone getting a new sim due to a bad flash.
Beamed from my Droid Charge using the XDA premium app
I've left my SIM card in while flashing every stock build we have and have had zero problems. There's really no reason to ever remove your SIM card.
Think of the sim card like another SD card, basically, that stores your subscriber data separately from the phone. That's really all it is -- a very low-memory storage device. Your phone reads that activation data every time it starts up, which is why you never need to manually activate the phone.
Hello all,
I just wanted to make a post and a fix that at least worked for me in case anyone else out there has had a similar issue. My issue was on my Samsung Infuse so I am not saying this will work for other phones as I have only encountered it with my Infuse.
First of all I am a flashaholic and am always Odin back to Factory just to Root and Flash another different ROM. Well I noticed maybe a month ago that once I would Odin back to Factory and after I would do a factory data reset. ( And yes I tried not doing the factory data reset as well had no effect. The reason I do that after Odin is because if not I get the Google Talk Auth error.) So after all that once I would go to the Market and start redownloading my apps I would notice that the first couple apps would install and then after that they would just hang there?? I would restart my phone and then a few more would install then once again it would hang up. This was very Very FRUSTRATING. I looked through the forums and couldnt find anything that talked about this issue with this phone. Last night I took out my 32GB sd card in my phone once I Odin and factory data reset again but this time I didnt put my sd card back in after. I have now downloaded all 133 apps that I had before with NO ISSUES!! This whole time the issue was with the SD card for some reason? I have no idea why or how but I dont care. The SD card is fine by the way I have it back in my phone now but if I ever need to install 20 or more apps I will know how I have to do it.
If anyone is having this same issue I hope you read this and this can help you as it did me.
Take Care
I think I am petty lucky right now... Last week I had an s off failure.... I screwed up and tried juopeanutbear on a 64 bit machine a few times... in fact allot! Luckily I tried again on a 32 bit machine... a couple of times... made sure I had the right wire, timed it just right but no dice every time. Odd thing is last time I re-locked the boot loader it threw an error but upon reboot, it re-locked anyways... stock rom goes through, format sd card (boo hoo)
Possible luck or false positive? Dunno.... couple factors to hash out:
-used device guy said he rooted, wasn't sure of S Off (maybe tried, maybe not)... he did restore to stock before I contacted him to buy it
-I mis read the tutorial and I am lucky I can atleast run cm9 now
Odd thing is my device does have issues with data cutting out randomly when using 3/4g. Didn't have that issue after I failed a few months ago. CWM had issues reading any SD cards I had. I did a re flash of the stock rom, had no errors unlocking the boot loader. Then I can successfully flash .zips and proceed move forward with CM9 only on that sd card. In fact no other sd cards will work in CWM regardless of version... android and boot loader sd cards are cool.
Luckily I htiaven't had any calls drop or weird battery issues now.
Long story short, being S On, is there any way to go back to a "truly locked" state and start fresh? Pardon the rant
Sent from my myTouch_4G_Slide using xda app-developers app
Ok so here's what's going on. I've been running an old ParanoidAndroid for a while and wanted to upgrade to a new version. I've been using TWRP as my recovery for a long time, and although I hadn't checked recently, I remember not being able to access my internal storage in recovery. So I downloaded the EZ Recovery app, flashed the TWRP from that, and went out to upgrade to the new PA.
In recovery, I was able to make a backup, factory reset, wipe system, and wipe dalvik. Then I went into the install menu, and I couldn't access anything on my external SD. Since I previously could ONLY use my external in recovery, all my ROMs and such were on that. SO I was stuck without a ROM, and without access to one to install. It was a *****, and took a lot of tries, but I was able to get my SD mounted enough to half-way restore the backup I made (as in, it restored the system and very little data, but was able to boot). So I figured it was some issue caused by the new TWRP, so I have un-rooted, and gone completely back to stock. Unfortunately, the problem still exists.
What could the issue be? Could it be something caused by flashing the new TWRP? If so, what could fix that? Or is it probably just a hardware issue that can't be fixed? I'm leaning towards that, and since I'm back to stock, I can just get a replacement from Verizon.
Thanks for any help!
It's likely not an issue with TWRP at all, but just an issue with external SD cards inherent to the S3 and some other Samsung devices. I had a similar problem, and within minutes of my micro SD card constantly unmounting itself, the card is now simply unusable. I haven't managed to find a solution, so yes, it's likely just a hardware issue that can't be fixed.
I've went through two sd cars with this phone. Most quality sd cards have a warranty, call and get that started. I called SanDisk last Monday and my replacement just came today. It sucks but they are fast. Good luck, losing an sd cars sucks.
This time around, my sd will only be for music and pics. I'll be taking it out whenever I flash something.
Sent from my SCH-I535 using xda app-developers app
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.