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
Related
Not sure what caused this, I crack flash CM nightlies, constantly convert partitions from ext-3 to ext-4 using beta kernels and at some point in between lost the ability for any computer to recognize my phone mounting (both internal and external). Tried three different computers, two different cables, swapped sd cards, reformatting card and nothing... All that happens when plugging into computer is a charge symbol.
My SD card is accessible through file managers and is mounted just fine to phone (accurate storage space). So I took it into Tmobile and they overnight-ed me a new g2x phone which is expected to come Monday. Claimed it was a hardware failure and acknowledged I had a custom rom and to make sure I put the stock one back . The only problem it is impossible to get the stock recovery image and remove root without a computer so I will be sending them a rooted stock rom with custom recovery. Hopefully they don't charge me for it...
Just wish I knew the cause whether or not it was a bad build or human error issue. Hopefully LG or Tmobile dont charge me full price when they see the firmware has been tampered with. I could always format the system with nothing on it so it just sticks on the LG symbol and has no rom to load up i suppose lol
I had to replace my first g2x because of this. No amount of software/external hardware troubleshooting fixed it. Luckily, I got mine at Costco which has a 90 day return policy. Ill try to find the thread I made... same symptoms though.
Also, my issue occurred on stock rom unrooted, so it wasn't the result of phone tinkering.
Here is the link: http://forum.xda-developers.com/showthread.php?t=1104397
Happened to me to on my first g2x....sometimes (randlmly) it would start working again n so when it did work I was able to bring back to stock n unroot n then a few hrs later the USB stopped working again...got a new one thru warranty and have been fine since
Sent from my LG-P999 using XDA App
dominante58 said:
Happened to me to on my first g2x....sometimes (randlmly) it would start working again n so when it did work I was able to bring back to stock n unroot n then a few hrs later the USB stopped working again...got a new one thru warranty and have been fine since
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
I had this problem on my first G2X phone also. It stopped working then somehow it worked for 1 min then never again. I had to replace that phone.
brdma said:
Here is the link: http://forum.xda-developers.com/showthread.php?t=1104397
Click to expand...
Click to collapse
Yup, this definitely looks like the same issue despite I am rooted and you were stock which is proof to me that it is a defective hardware and not provoked from me tampering with the firmware. Just hope they dont throw a fit when and if they find it rooted with custom recovery image.
Okay let me start off by saying I'm no stranger to rooting or ROMs. I have had my Infuse for a few months now and I have rooted it successfully and tried several different ROMs. Currently the phone is on stock 2.2.1 rooted via superoneclick. I have already tried GTG's Ultimate Unbrick a few times to resolve the issue and it hasn't helped....and, yes, I did a factory reset as well. Right now what is happening is that the phone is booting through to the AT&T screen and then restarting again in a constant loop. What is weird is that if I play with the buttons on the phone at the bottom while on the AT&T screen it will sometimes boot all the way through and be okay and operate normally. If I push power and set it on the table and leave it alone it will just keep looping no matter how long I leave it. Weirdest thing I've run in to. I'm guessing it's a hardware issue. Any ideas anyone?
I should add that I was not doing anything....flashing or otherwise. I had just downloaded TSF Shell from the market. I have used it before on the same ROM without issue. In fact, I hadn't flashed anything new since the last time I used it.
Sent from my SAMSUNG-SGH-I997 using xda premium
well... if it isnt a bad flash, since you say you hae falshed many times before... maybe your phones flash memory is messed up. It could also be a partion layout error... if you have tried the pit reflash, and still have no luck... do as I did with a Motorola Defy... my friend trued to flash too many times and ended up damaging the memory so i just flashe da stock rom and even though it bootlooped, i turned it into warranty i my friend got a new phone in a matter of days... i dont know how it is where your from but at least here in Puerto Rico it did the job for me.
Long story about what's going on,
I had to get my first triumph replaced about 2 weeks ago. I had backed it up with a nandroid and titanium backup. I procceded to install the nandroid backup on the new phone. Everything went well for a while untill one day when the phone just shut itself off. When i turned it back on, there was no sd card mounting notification, and it said that there was no sd card in the phone. CWM recovery also wouldn't read it. After having done random combinations of repartioning the sd card, formating the sd card, using a different sd card, unrooting, factory restoring, i seem to be able to get it to work for a little. What happens, however, is that after i restore from nanadroid or titanium backup it works for a little, then turns itself off again and the card wont mount! This is really starting to suck any help is apperciated
Thanks,
A guy pulling his hair out. ._.
Extra info: Rooted with gingerbreak 1.20, not sure what cwm version but it is from the all things about root guide. Just factory restored again and it showed up for a little then i restarted and it was gone again. It seems to have fits on whether or not to recognize the sd card.
seeing as no one seems to have any help to give, I guess i will cave in and go through virgin mobiles support to give a repalcement =.= If i do ever find a fix myself, i'll go ahead and post it for anyone else who might have it as well.
dont know how to delete posts >.<
try to ask here http://androidforums.com/triumph-all-things-root/
Sent from my FIH-FB0 using xda 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
Hey guys. Forgive my noobity but I could do with some help and might have a unique problem although I dare say someone has had this or similar.
Firstly, after putting a 64GB stick in my tablet the other day, it all went badly wrong. I had done it before with my previous 64GB that had been playing up so I sent it back and got a new one. The new one seems to be where it all went pear shaped. I might add, the 64GB is for my phone really but my phone cam was playing up so I was swapping it over and stuff... anyway the card itself seems fine in my phone.
Anyways... now my ampe tablet is suffering some strange effects that have changed. initially it would not boot up unless I redone it with the official firmware.. but then wouldn't boot up again, unless I did the same thing over and over. then one time it just refused to boot up past the initial boot screen. I gave up for weeks then picked it up again two days ago.
Now I give it the firmware installed using pheonix again and it booted up. Ahh I thought... lets play. Now I plug it into the pc but the pc says I need to format the 5GB internal partition. So I did. I then looked how to fix the fact that the tab still says it has 0.00kbs internal storage in settings. Then after a while it came up saying 5GB so i copied some files onto it.. great. But I still can't install apps as I found when trying to do this tested working fix http://www.youtube.com/watch?v=sJlpek6w624
I then read about using android commander to move busybox from xbin to bin in the system folder but mine is already there.
So now I am stuck. I can't test if my tab is rooted for the youtube link fix above although this is what I said to Nayeem on youtube:
================
Hi Nayeem. I'm really struggling with this. At first my tab was staying at the 2nd initial boot up screen after I put in a 64GB SD card. Using pheonix I managed to get it to boot by reinstalling the updated official rom from szampe but every reboot back to square one. I left it alone for weeks and came back to it, reinstalled the factory rom again and now it will boot up everytime but it has factory reset every time. I cant run the apps you supply for some reason. Everytime I have rebooted the tab, and connected back to pc it says I need to format the internal 5GB partition. I don't know if I have rooted it properly as I can't check. The commands you give above, work as it changes the location proven when I 'get' it. I'm really stumped. I'm trying out a method someone said about moving busybox from sys/xbin to sys/bin but it's already there (using android commander) so I am really stumped now. When I format the partition, it allows me to copy files to it.
================
So far I am stuck with boot up being a factory reset and the partition needs formatting and although the tablet seems a little laggy, everything I have tried works including wifi and incoming email alerts after logging into google account for playstore but no apps will install or update. the best warning I get is there is no memory to install anything and Nayeems method of moving the install location to the sd card seems to work but nothing will install still saying NOT INSTALLED when I try.
Sorry for the long winded thing but I am really new to all of this.
My hat is off to you if you read all of this and can offer a solution so i can give this tablet back to the kids.
Do you have an installed recovery
Try installing a recovery and wipe data and cache. If it does not work u have to repartition ur tablet
nelsontky said:
Try installing a recovery and wipe data and cache. If it does not work u have to repartition ur tablet
Click to expand...
Click to collapse
I am gonna look into this tonight and see what I can find out. I really don't know exactly what I am doing outside of getting pheonix up and sending a standard rom back to it as previously mentioned.
How would I repartition it ? Sounds stupid asking as i can build pcs... just want to make sure I am doing the correct method.