So I picked up my VZW GS4 yesterday from Best Buy. I was out to dinner with my cousin, and the battery died (after a full day of very heavy usage). I tried to turn it back on to check something quickly, and when I did, the Samsung boot screen showed the unlocked bootloader symbol, with the words custom underneath it. I thought I was crazy and seeing things, so I rebooted again, and it was still there. Has anyone else run into this? I find it hard to believe that my bootloader just randomly unlocked itself.
I attached an image so people can tell me if that really is what it seems. Let me know if anyone has any idea what is going on.
Achievement unlocked!
Hey, less work for you in the end. (if you like to flash and rom that is)
I say Congrats!
Did you root and not flash the original kernel back on?
vanydotk said:
Did you root and not flash the original kernel back on?
Click to expand...
Click to collapse
No. I had decided not to fiddle with anything until I decided how I liked the stock Touchwiz UI. I had the GNex before this, and messed with that to my hearts content, running clockworkmod recovery and cyanogenmod 10.1., but was waiting to try anything on this. That's why I'm confused, I've done absolutely nothing to it to customization wise. I haven't even set a wallpaper yet lol.
Maybe they shipped you a dev unit. Wouldn't be the first time lol
Sent from my SCH-I545 using Tapatalk 2
shuddle13 said:
So I picked up my VZW GS4 yesterday from Best Buy. I was out to dinner with my cousin, and the battery died (after a full day of very heavy usage). I tried to turn it back on to check something quickly, and when I did, the Samsung boot screen showed the unlocked bootloader symbol, with the words custom underneath it. I thought I was crazy and seeing things, so I rebooted again, and it was still there. Has anyone else run into this? I find it hard to believe that my bootloader just randomly unlocked itself.
I attached an image so people can tell me if that really is what it seems. Let me know if anyone has any idea what is going on.
Click to expand...
Click to collapse
That's awesome, lucky you
If I got a dev edition, that is awesome :laugh:, saves me a lot of work down the road if I decide to run a custom rom. I swear I had rebooted it at least once (I feel like it might have been 2 or 3 times) prior to this, and don't remember it being there before. But now I'm second guessing myself - maybe I hadn't rebooted up to that point, or I did and just didn't notice it. That's what is throwing me off more than anything, I thought it just happened randomly, which I found hard to believe considering the amount of work that goes into finding a way to unlock a phone's bootloader.
So this leads me to a more important question. As I said earlier, I planned on keeping stock rom with Touchwiz for now (I know how many people feel about it, please don't give me 20 replies telling me how awful it is) but my main concern at this point is that I'm getting the bootloader unlocked symbol, and the word custom. When I go into settings and check the info on my phone, it tells me that device status is 'custom'. Now, correct me if I am wrong (but I'm fairly certain I'm not) I won't be able to get any OTA updates, because it will read my device as custom - and this is where I'm fairly certain something wonkey has happened, because I remember playing around in settings yesterday and seeing that it said device status 'official'. Basically, any speculation as to what the heck might happened (it isn't something any app could have done either, if that's even possible. I'm still setting up the device and barely have anything on there, and certainly not anything that would cause my phone to say custom) and any way at this point to get it back to device status official? I know a root method had just been released, but I wasn't sure about unroot.
That is not indicating an unlocked bootloader. Your phone has been rooted and the person that did it either did not odin back to the stock kernel or he flashed a custom recovery.
Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Than you for your cooperation
Friendly Neighborhood Moderator
brizey said:
That is not indicating an unlocked bootloader. Your phone has been rooted and the person that did it either did not odin back to the stock kernel or he flashed a custom recovery.
Click to expand...
Click to collapse
I have the same screen out if the box. So I decided to root and install cwm but it failed. Reading more they say it fails because the locked boot loader. So I'm confused
After rooting i flashed the stock kernel back. And that screen as seen in the first screenshot has not changed..
What do you think?
Sent from my SCH-I545 using Tapatalk 2
brizey said:
That is not indicating an unlocked bootloader. Your phone has been rooted and the person that did it either did not odin back to the stock kernel or he flashed a custom recovery.
Click to expand...
Click to collapse
So I'd go with my phone being rooted, which doesn't really make sense unless someone at the Samsung Factory rooted it before sending it out, except I have a weird development. I pulled the sd card I bought (64GB Samsung Pro MicroSDXC Extreme Speed (UHS-1) Class 10 Memory Card), from Amazon directly, not a retailer on Amazon) turned it back on, and now I'm not getting the unlocked symbol and device status is back to official. I rebooted, turned it off, did a battery pull, and turned it back on, every combination of restarting the device I could think of, and every time it says official. I put the memory card back in, and at first it says official. Then I reboot, and it goes back to being unlocked and custom. Going to try formatting the SD card to see where that gets me, but at this point, it makes no sense to me.
I flashed back to the stock kernel after flashing the exploit one and I have the same screen on start up. Not sure why but it doesn't really bother me.
Sent from my SCH-I545 using xda premium
Since rooting I've randomly had that screen too. I just rebooted and didn't have it this time. No clue what's going on.
I tested the memory card theory, and that is in fact the problem. Tried formatting it, but it still causes my phone to read custom. Not sure if it is a faulty memory card, if the phone can't read this type of memory card (I know some devices can't read SDXC UHS-1 cards, but I thought I researched and the S4 should), or it's a software issue with the phone that needs patched. I'm leaning toward the last one, but got in touch with Amazon and they are sending me a replacement card. Will update once I get the new card. If anyone else is experiencing the same or similar issues, or has any idea what is going on, I would appreciate the input. Like I said before, it's not a major issue until I need to do an OTA update. At that point, worst case scenario, if the problem isn't fixed, I can always just pull the memory card. But don't want to go through the hassle if I can pinpoint the problem and fix it.
shuddle13 said:
I tested the memory card theory, and that is in fact the problem. Tried formatting it, but it still causes my phone to read custom. Not sure if it is a faulty memory card, if the phone can't read this type of memory card (I know some devices can't read SDXC UHS-1 cards, but I thought I researched and the S4 should), or it's a software issue with the phone that needs patched. I'm leaning toward the last one, but got in touch with Amazon and they are sending me a replacement card. Will update once I get the new card. If anyone else is experiencing the same or similar issues, or has any idea what is going on, I would appreciate the input. Like I said before, it's not a major issue until I need to do an OTA update. At that point, worst case scenario, if the problem isn't fixed, I can always just pull the memory card. But don't want to go through the hassle if I can pinpoint the problem and fix it.
Click to expand...
Click to collapse
That's weird, my 32gb sandisk microsd doesn't effect it.
Have the same issue with the lock showing on bootscreen randomly. I haven't tried this morning but I think I am on something. Setup a link with foldermount, something from internal memory to the SD card. After a reboot and foldermount sets up the link at boot up, reboot and see if you get the lock /custom boot screen
Sent from my SCH-I545 using xda premium
I have the same issue and have another thread going on it. It said it once when reboot and device status changes from custom to original randomly in settings. Bought the phone brand new from Verizon yesterday.
Sent from my SCH-I545 using xda app-developers app
Very odd. I get that now, but I rooted to get it.
Root has nothing to do with being unlocked though therefor I think it would do it bone stock like mine as well.
Sent from my SCH-I545 using xda app-developers app
Related
So... I have FJ Mod on my note. Things have been running great for a long time. Then a few days a go, out of the blue, google voice was constantly crashing. Then the gapps process. Then it got ridiculous and everything would crash. Then I noticed that when I restart, it saves nothing that I had done. For instance, my call log, text messages, moved icons on my homepage.
I did a wipe in CWM, and everything came back the exact same. Still the same problem, icons still in the wrong place... no idea whats going on.
Has anyone got any advice for me? I was going to try and put a new ROM on later if worse comes to worse, but as is, this is very frustrating. I often have to restart my phone just to use the browser, or message, or anything really. I am just hoping that my internal SD isn't screwed some how and now allowing me to write to it. I haven't done any changes. I don't even believe I have downloaded any apps since a week or so prior to this issue.
Flashing with ODIN did not good either. I tried to revert back to stock. It uploaded with no issues apparently, and then when it rebooted I was back in ICS with everything as it was... argh.
Find one of the the ics leaka one click Odin packages and run that. Should wipe everything, and then you just have to flash cwm and root again.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
welchertc said:
Find one of the the ics leaka one click Odin packages and run that. Should wipe everything, and then you just have to flash cwm and root again.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
Well, I tried something similar with a rogers stock rom. Booted up Odin, connected to issues. Uploaded/transferred no issues. Figured I'd be on stock Gingerbread upon bootup, but it was ICS! I've done this and similar on multiple phones, not sure whats happening. I will try again with a different rom as you suggested tonight.
I know where the leaks are...this loser has them here....
http://forum.xda-developers.com/showthread.php?t=1740367
welchertc said:
Find one of the the ics leaka one click Odin packages and run that. Should wipe everything, and then you just have to flash cwm and root again.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
johnnyb82 said:
Well, I tried something similar with a rogers stock rom. Booted up Odin, connected to issues. Uploaded/transferred no issues. Figured I'd be on stock Gingerbread upon bootup, but it was ICS! I've done this and similar on multiple phones, not sure whats happening. I will try again with a different rom as you suggested tonight.
Click to expand...
Click to collapse
bigjoe2675 said:
I know where the leaks are...this loser has them here....
http://forum.xda-developers.com/showthread.php?t=1740367
Click to expand...
Click to collapse
Greatly appreciated! Thanks for posting the link. I will try it tonight and let you know how it works out.
johnnyb82 said:
So... I have FJ Mod on my note. Things have been running great for a long time. Then a few days a go, out of the blue, google voice was constantly crashing. Then the gapps process. Then it got ridiculous and everything would crash.
Click to expand...
Click to collapse
I had the EXACT problem, out of the blue as well. I didn't have the other stated problems in your OP but I did have the one quoted above. First voice , then a few google apps(gmail, drive, etc). The apps would hang for a few 1-2 minutes (felt like hours) and the phone including capacitive buttons became unresponsive and couldn't do anything with the phone. The "wait" or "ok" buttons on the force close popup were not clickable.. It sorted itself out in a few days and boy did it drive me NUTS. I was afraid to post up here in fear people would think I was nuts and did something myself to make things go so awry. I was convinced I myself was nuts.. im by no means daft when it comes to android dev/tinkering lol. Very strange
Sent from my SAMSUNG-SGH-I717 using xda premium
Well I was impatient and tried 2 different roms right away. Neither worked. Odin showed "pass", no errors. Then it does its auto-restart and bam, back where I was. Not having the best of luck with this right now.
Any other ideas would be appreciated!
simbill said:
I had the EXACT problem, out of the blue as well. I didn't have the other stated problems in your OP but I did have the one quoted above. First voice , then a few google apps(gmail, drive, etc). The apps would hang for a few 1-2 minutes (felt like hours) and the phone including capacitive buttons became unresponsive and couldn't do anything with the phone. The "wait" or "ok" buttons on the force close popup were not clickable.. It sorted itself out in a few days and boy did it drive me NUTS. I was afraid to post up here in fear people would think I was nuts and did something myself to make things go so awry. I was convinced I myself was nuts.. im by no means daft when it comes to android dev/tinkering lol. Very strange
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
LOL I actually waited a few days before posting here too. I was hoping that maybe uninstalling and reinstalling some, or updated, or clearing cache and all that would help. As you can see, it did nothing. Heck, after I restart my updates didnt even stick and Google Play is trying to download them again!
Well... still no luck.
Here is another thing I noticed. When I hook up the note to my PC, and look at it, I cannot access my external SD. Furthermore, I had a file on my internal SD that I deleted. When I restarted my phone the file was back. Yet in windows it removed without error. I have no idea what is happening at all.
And now its reading it again........ Ive literally been sitting here trying a bunch of different ways to fix this. Playing around in CWM, trying ODIN including a couple 1 click solutions. The one starts writing to NAND, then stops and gives me an error.
Try taking out your sd card and running it for a while. First note i got was acting that way from the get go. Took it back and got a new one. It started doing the same thing. Finally took out sd card and ran great. Card was going bad. I had replaced the 8 gb stock card with the 16 gb one i had in another phone and apparently the mote didn't like it.
Sent from my SAMSUNG-SGH-I717 using xda premium
johnnyb82 said:
Well... still no luck.
Here is another thing I noticed. When I hook up the note to my PC, and look at it, I cannot access my external SD. Furthermore, I had a file on my internal SD that I deleted. When I restarted my phone the file was back. Yet in windows it removed without error. I have no idea what is happening at all.
And now its reading it again........ Ive literally been sitting here trying a bunch of different ways to fix this. Playing around in CWM, trying ODIN including a couple 1 click solutions. The one starts writing to NAND, then stops and gives me an error.
Click to expand...
Click to collapse
Did you, by any chance, install a custom kernal? IIRC, one of them messed with the mount points. By far, the only way to fix your issue immediately will involve restoring to stock through ODIN, then rerooting and reflashing CWM. This will 100% mark your Note as either defective, or prove that it's a problem in another area. However, I don't believe your problem is with your SD Card, unless you've been using an app like apps2sd.
If you're weary about doing this, try to reflash CWM, or TWRP to figure out if it's something going on with the recovery partition and/or settings. I'm no expert, but the only thing I'm aware of that sticks around through a wipe, and multiple flashes are our recovery, our internal SD files (possible), and sometimes the modem. Also, the one click leaks include a not loader, which could prevent you from restoring a GB Nandroid.
By flashing CWM, then TWRP, then CWM again, or sticking with TWRP, you at least knock out one variable...and by reformatting your internal SD, you ensure no resources are sticking around.
Edit:are you using TiBu to backup and restore/migrate after a flash? Verify your backups under the batch lost.
What could be happening, is you're restoring data in CWM, or TiBu, or w/e ap you're using, and then the Google account sync restore is restoring your settings, and replacing the desired ones, or vice versa.
Edit again: Which launcher are you using? Which utilities do you use? What are your main root apps?
The backup verify is a must...but some launchers will scoot icons out of the way. If you're having a touch screen issue, or an S Pen issue, you could be draggn items around when you're not aware of it.
I'll see this through. You've caught my interest.
Sent from my Transformer TF101 using XDA Premium HD app
johnnyb82 said:
So... I have FJ Mod on my note. Things have been running great for a long time. Then a few days a go, out of the blue, google voice was constantly crashing. Then the gapps process. Then it got ridiculous and everything would crash. Then I noticed that when I restart, it saves nothing that I had done. For instance, my call log, text messages, moved icons on my homepage.
I did a wipe in CWM, and everything came back the exact same. Still the same problem, icons still in the wrong place... no idea whats going on.
Has anyone got any advice for me? I was going to try and put a new ROM on later if worse comes to worse, but as is, this is very frustrating. I often have to restart my phone just to use the browser, or message, or anything really. I am just hoping that my internal SD isn't screwed some how and now allowing me to write to it. I haven't done any changes. I don't even believe I have downloaded any apps since a week or so prior to this issue.
Click to expand...
Click to collapse
Also, tap USB utilities in settings, by the other FJ mods, and tap the selection there, then check to see if you can find your SD card through your PC.
In addition to the above, you can also enter the "Tools" section of FJmods, and disable ad blocking, remove touchwiz UI, s voice, etcetera, and return ALL settings too default, and remove all extras. You can reflash recovery there too.
How are you trying to reformat your SD card?
Sent from my Transformer TF101 using XDA Premium HD app
Jamesyboy said:
Also, tap USB utilities in settings, by the other FJ mods, and tap the selection there, then check to see if you can find your SD card through your PC.
In addition to the above, you can also enter the "Tools" section of FJmods, and disable ad blocking, remove touchwiz UI, s voice, etcetera, and return ALL settings too default, and remove all extras. You can reflash recovery there too.
How are you trying to reformat your SD card?
Sent from my Transformer TF101 using XDA Premium HD app
Click to expand...
Click to collapse
I had installed a custom kernel on Gingerbread before, but obviously that was replaced with the one I used with FJmod. It had been operating fine for over a month.
Also, I removed my SD Card, and tried everything without it. I have tried restoring gingerbread stock and ICS stock through both ODIN and CWM. Even formatting through CWM does nothing as when I restart I am back to normal.
As for root, I only had 2-3 programs with access. ES File Manager/Task manager, and I tried one called Lucky Patcher (I will verify this evening). All of these had been on for at least a week prior to all this beginning.
I havent been using TiBu for anything at all actually.
The launcher I am using at the moment is Nova.
Other than that, I am going to try a few of your suggestions once I am done work. I will post my results tonight!
Thanks for the suggestions and info, greatly appreciated.
EDIT: Just to be clear. I am formatting then restarting and all my apps, icon placements and wallpaper return. Even my call history is stuck up to the 13th and erases recent calls. I am also trying to revert to stock ICS and Gingerbread through both ODIN and CWM. After it is done installing through ODIN and reboots, I return to the way my phone was before. Same with CWM. After flashing through CWM I return right back to the way it was. I am not doing any restoring or anything. I have done this plenty of times in the past before. The only thing I can possibly imagine at this point is that my SD is somehow stuck on read only. Yet it is weird because again, I can delete files and apps (and even windows shows them as gone), but after a restart they are all back! I can remove apps, but they are still in the app menu too.... I can even run them lol (even after deleting their folder). The phone is stuck in stasis.
All of this just happened one day out of the blue. No new apps (for at least a week) too.
I have a GTab that had the EXACT same symptoms.. turns out it's internal flash memory was bad, not the microSD. going for broke I opened it up and desoldered the flash memory IC and it uses the microSD now as its primary storage. If even after a stock reflash you have problems I hope you have warranty.
Black6spdZ said:
I have a GTab that had the EXACT same symptoms.. turns out it's internal flash memory was bad, not the microSD. going for broke I opened it up and desoldered the flash memory IC and it uses the microSD now as its primary storage. If even after a stock reflash you have problems I hope you have warranty.
Click to expand...
Click to collapse
Great... lol! I have a warranty, but no one will work with it due to the fact I have a custom rom. Am I maybe contacting the wrong people? I contacted Rogers and they said they couldn't help me. Well I am going to purchase the s3 as I get a small discount on it. I am positive I will end up with the next note unless some sort of crazy deal passes in front of me for another note.
johnnyb82 said:
Great... lol! I have a warranty, but no one will work with it due to the fact I have a custom rom. Am I maybe contacting the wrong people? I contacted Rogers and they said they couldn't help me. Well I am going to purchase the s3 as I get a small discount on it. I am positive I will end up with the next note unless some sort of crazy deal passes in front of me for another note.
Click to expand...
Click to collapse
No stock Odin for your phone? I would attempt this to be absolutely sure the problem isn't software related.. they should warranty hardware faults.
Black6spdZ said:
No stock Odin for your phone? I would attempt this to be absolutely sure the problem isn't software related.. they should warranty hardware faults.
Click to expand...
Click to collapse
No sir. I tried stock gingerbread and ics. I've tried custom roms. I've tried just erasing it too! Tried Odin and CWM. I am going to try and change recovery today again too.
Rogers said they won't help. They used the word "launcher" but I knew what he meant. They think I may have overclocked it any burnt it out I bet. Maybe I will try calling samsung.
Thing is, all my private info is on there! At least no private pics though
johnnyb82 said:
No sir. I tried stock gingerbread and ics. I've tried custom roms. I've tried just erasing it too! Tried Odin and CWM. I am going to try and change recovery today again too.
Rogers said they won't help. They used the word "launcher" but I knew what he meant. They think I may have overclocked it any burnt it out I bet. Maybe I will try calling samsung.
Thing is, all my private info is on there! At least no private pics though
Click to expand...
Click to collapse
If your have insurance, and it turns out the phone was physically damaged , you could try making a claim....but that's only if it was physically damaged. So you restored stock through odin? Did this happen on the stock unrooted rom?
Sent from my Transformer TF101 using XDA Premium HD app
Jamesyboy said:
If your have insurance, and it turns out the phone was physically damaged , you could try making a claim....but that's only if it was physically damaged. So you restored stock through odin? Did this happen on the stock unrooted rom?
Sent from my Transformer TF101 using XDA Premium HD app
Click to expand...
Click to collapse
Well its currently stuck on FJ Mod (which I think is a great rom), and then it just started acting up. I cannot restore Gingerbread stock, or ICS stock, or anything else. ODIN and CWM both show completed on my attempts, but upon reboot my device is back exactly where it left off on the 13th.
I picked up the S3 and I like it, but I miss my note badly
Hey everyone. I just bought a Galaxy S4 a couple days ago, and have had no problems with it until this morning. I had it plugged in, and when I woke up, it was extremely hot to the touch, burningly so, and had some weird battery warning of some sort on the screen. I didn't know what else do do, so I immediately unplugged it and took the battery out. Coming from using an HTC Thunderbolt, I've never had a phone get this hot. My hands even still hurt from handling the phone, and now I'm really concerned that there is a problem with it. It's probably worth mentioning that I did root it, but I did nothing else that would cause it to do something like this. I didn't overclock it, I didn't install a custom recovery, and I didn't install any custom ROMs. Besides having root access, the phone is in a stock state as if I just took it out of the box. I haven't turned it on yet as I'm letting it cool off right now, but I really want to know what the heck happened here.
Thanks for any help.
You're not the first person. Hm I want to buy this phone too
Sent from my SCH-I605 using xda app-developers app
Yeah, to my surprise I noticed one of the moderators moved a similar thread from someone over to this section while I was in the middle of posting mine. I wish I would have been able to see it before making mine, but oh well. At least I'm glad it's nothing I did, but I'm both concerned about the heat killing the battery as well as this happening over and over again.
I haven't had this issue at all. I'm rooted and running cwm recovery, but otherwise stock. I also froze several apps (only bloat that was allowed to be disabled natively, so far).
In general, if I were you, I would contact Samsung or Verizon. It may be a defective battery or a defective phone.
SonicJoe said:
I haven't had this issue at all. I'm rooted and running cwm recovery, but otherwise stock. I also froze several apps (only bloat that was allowed to be disabled natively, so far).
In general, if I were you, I would contact Samsung or Verizon. It may be a defective battery or a defective phone.
Click to expand...
Click to collapse
I suppose I could bring it back; I do have about 12 more days to return it if I need to. Of course, I'd really rather not, but if everyone here thinks that's the best course of action here, then I suppose I should. Of course, there is the whole I rooted it thing, so yeah.
BJSerpas said:
I suppose I could bring it back; I do have about 12 more days to return it if I need to. Of course, I'd really rather not, but if everyone here thinks that's the best course of action here, then I suppose I should. Of course, there is the whole I rooted it thing, so yeah.
Click to expand...
Click to collapse
Don't worry about root. Use SuperSu's unroot feature before returning it. And a factory reset. They'll never know.
Or, if you're really paranoid, use the stock no root odin image and flash it clean.
Get the battery error message to repeat then bring it in with it showing or take a picture of it. A good store will hand you a new one on the spot. They just need to have a documented reason.
Yeah pretty much
I think what I'll do is test the battery life and see if it was damaged at all first. If there's nothing to worry about there, I could just pretend it never happened. Of course, if it decides to go supernova on me again, I'll just unroot it and bring it back. Thanks for the replies guys.
Update:
Considering my battery went down by 8% in just a half hour, I think I can safely consider my battery to be fried. This is just wonderful...
So I finally HAVE to replace my Note 2 via warranty. Power button sticks and will not boot.
At the end of the call to place the warranty order she says "any physical damage, water damage, or software alterations will result in a charge of $290". So I'm rooted and ROM'd and would normally just return to stock. BUT since the phone will not boot, I cannot do this. I realize if it won't boot for me it likely won't boot for Verizon.
My worry is that somehow they will in get it to boot. Do they still check for root? If so is this something I should be worried about? I cannot for the life of me get this thing to turn on it seems like I will not be able to return this to stock with out powering the phone on. Any insight is greatly appreciated.
I have done the warranty replacement game for a long time. Typical the people checking the phone are stupid and dump for checking for root. I havent spoken to or talked to one smart person that would check. Plus the people they hired to make sure the devices comes in probably isn't tech savvy. Just a worker trying to get paid.
Sent from my SCH-I605 using Tapatalk 4
I agree with the above. I guarantee you the people who do the initial evaluation have a 'target' for the number of phones processed. But just the same return your phone to as stock looking as possible. Restore the launcher, use a stock wallpaper and/or boot-ani. Uninstall all apps you got from the store. And run your battery all the way down. It will continue to discharge even though it's off. This means it will need to charge for a few minutes before it will boot again.
And I've never noticed many posts (i can't recall even one) about phones being kicked back for being rooted/flashed.
But with that said isn't there some kind of flash 'counter' on the Note 2?
Sent from my Nexus 7 using XDA Premium 4 mobile app
When I had my DROID X I went into a Verizon store to upgrade to an s3 and the guy who just got done telling me how he "mods" his gnex looked at my X and it was running cm7 themed out the wazoo and he said how plain the stock os is on the Motorola. Haha. So I don't think that 98% of the people who are either in store or at the warranty place have a clue what rooted is let alone able to tell if it is or not.
Sent from my SCH-I605 using XDA Premium 4 mobile app
I think I read somewhere that you can make a powered usb jig the will boot it into download mode. I might be wrong, but you can search around for it.
Sent From My Sticky Note, Too?
Did you even read the op
Sent from my SCH-I605 using xda app-developers app
Yea I can't even get the phone to boot. Which I believe is due to the malfunctioning power button. But I'm still concerned verizon will find some way to get it booted. I'm going to see if I can boot via ADB this evening. Its been quite a while since messing around with ADB so I need to allow myself some time. Hopefully I can boot it and just Odin the factory image via ADB.
I should also try and clear the flash counter right? Does anyone have any tips or know-how on how to do that? I saw somewhere that there is an app. But should that be run before or after running the Odin stock image?
Thanks again guys and gals.
Hey gerg, the app is triangle away, and I would always try to return to stock if possible. I would use it before returning to stock as it needs root privileges. What a great learning experience (better to look at it that way then get angry trying to accomplish your goal). Keep us posted as we are all"rooting" for you....:thumbup:
"One small step for man, One giant leap for mankind" said anyone who has tried Moon Rom
JeramyEggs said:
Hey gerg, the app is triangle away, and I would always try to return to stock if possible. I would use it before returning to stock as it needs root privileges. What a great learning experience (better to look at it that way then get angry trying to accomplish your goal). Keep us posted as we are all"rooting" for you....:thumbup:
"One small step for man, One giant leap for mankind" said anyone who has tried Moon Rom
Click to expand...
Click to collapse
Thanks man. Appreciate the positive vibes.
However it seems like I'm stuck. I can't for the life of me get this phone to boot, therefore I can restore the stock image via ADB, because ADB will not recognize the device since it is off. I've tried every trick out there, including the youtube video about pulling the charger and pulling/re-seating the battery as fast as possible. No dice.
I did however receive my warranty device today, and since I have ADB all set up and ready to go, I'll be rooting her and getting back to Trans-Neb ASAP, and of course I'll see you back in that thread.
Again, thanks for the help guys it is appreciated. I'm fairly sure I've tried harder and spent more time to get this phone to boot than Verizon will ( I hope at least). So if they can't get it to turn on, I don't see how they can tell its rooted
Mods can close this thread
Cheers!
Gonna copy my post from the CM11 thread here for more people to see:
I experienced perhaps the strangest problem today I've ever encountered with my phone.
Today I was using my phone just fine. Went out to eat with friends. Sat down and the restaurant and took my phone out to show them something. Hit the unlock button and the soft key lights came out, no screen. Hit it again, they went out, hit it again, they came back on, still no screen.
Assumed it locked up, I pulled the battery, put it back in, and phone would just show the HTC logo and then nothing. Figured the phone was dead so I threw it on my car charger.
An hour later, same thing. Booted to recovery looking for my CM11 download file. Mysteriously vanished from both internal and external storage. So I hit reboot to see if maybe rebooting from the recovery would change anything.
No OS installed. What? How did it just vanish? I haven't touched anything recently.
This is that phone I had just gotten from warranty too.
On a side now, this is a good time to mention I'm jumping to the Note 4 as soon as it releases.
Edit: I can't just reinstall a rom like I was hoping. It only needs to last 2 more damn weeks for the Note 4. UGH!!! It tells me /cache /data /system /devlog and emmc storage are unable to be mounted. What the hell could have happened to cause this?
Edit 2: Was gonna try reinstalling the RUU but apparently I can't because I didn't do s-off this replacement device yet. Can't relock bootloader because fastboot won't connect. Any ideas??
You should be able to download and flash a ph98img.zip from hboot, just find the right one. I would link you, but I'm on my phone right now with no access to those bookmarks.
You got a slim chance with a ph98img honestly... Since it can't mount ANY partitions, the partition table is probably corrupt meaning only JTAG or a reload via an EXE RUU in dowload mode has any chance of fixes it, and that's a 50/50 chance at best but since your S-ON that isn't possible. Best bet is to beg/borrow a VZW phone from someone for a couple weeks, even if it's a dumb phone... Or get a cheapo prepaid phone and have Verizon forward your number until you get the Note 4, then sell the prepaid phone.
Thanks guys. I assumed it was totally dead anyway, sucks that I forgot to S-OFF while I could have... at least would have given me a chance to fix it. Sucks.
Also I hear a rattling sound inside the phone, presumably the memory breaking off somehow? I'm careful with my stuff, and I especially know I didn't slam the phone or anything since I had just used it before this happened, but it can't be a coincidence that this rattling started when all the partitions vanished.
Edit: Do you guys think I should attempt to get it replaced at Verizon? The reason I'm so worried about that is that since it doesn't boot I'd assume the first thing they'd check is if the bootloader loads, see the tampered flag, and then charge me for the replacement despite it being a physical issue.
Hobox10 said:
Thanks guys. I assumed it was totally dead anyway, sucks that I forgot to S-OFF while I could have... at least would have given me a chance to fix it. Sucks.
Also I hear a rattling sound inside the phone, presumably the memory breaking off somehow? I'm careful with my stuff, and I especially know I didn't slam the phone or anything since I had just used it before this happened, but it can't be a coincidence that this rattling started when all the partitions vanished.
Edit: Do you guys think I should attempt to get it replaced at Verizon? The reason I'm so worried about that is that since it doesn't boot I'd assume the first thing they'd check is if the bootloader loads, see the tampered flag, and then charge me for the replacement despite it being a physical issue.
Click to expand...
Click to collapse
Asurion or Verizon? If Verizon I would say no, although rooting/romming probably didn't cause this, they will say it did... Asurion is an insurance, they don't care if its rooted or not.
acejavelin said:
Asurion or Verizon? If Verizon I would say no, although rooting/romming probably didn't cause this, they will say it did... Asurion is an insurance, they don't care if its rooted or not.
Click to expand...
Click to collapse
Verizon.
Hobox10 said:
Verizon.
Click to expand...
Click to collapse
I wouldn't try it... Although, you get a few weeks to return the phone, so you could get a replacement, use it for two to three weeks, then get your Note 4 and return the phone Verizon had sent you as a replacement instead of your broken Rezound. It might be slightly questionable ethics, but it should net you a temp loaner as long as nothing happens to it.
First off, this may be a dupe from another thread (http://forum.xda-developers.com/verizon-lg-g3/general/vs985-ota-updated-to-49a-11-11-t3498269), but I wanted it as main topic so that what was discovered does not go unnoticed by people who may not read the entire thread. Maybe someone can sticky this as well since this is a major issue with the 49A OTA?
Last week, I took the 49A OTA for the G3. I have an older model (non-K model) and immediately, upon rebooting, I started getting multiple SD card ejection notifications. It would unmount and remount my SD Card several times throughout the day. This would happen at random times, although my feeling was that it occurred whenever an app attempted to read and/or write to the SD card. Sometimes, after it unmounted, it would take anywhere from a few minutes to maybe an hour or more to remount it without rebooting.
This continued on throughout the week as I waited to see if it would clear up. It didn't. A factory data reset didn't help and one time, I saw a SIM card failure. Posting in the forums, it was a few days later that @nulloverride posted this very important tid bit of information:
http://forum.xda-developers.com/showpost.php?p=69676134&postcount=17
nulloverride said:
I actually just spoke with Verizon's support people. It turns out the device is not compatible with the latest Android updates. Maybe going back to square one with it will fix the problem, but they said they would give me a new device with the updates disabled until the problem is fixed. I don't know if that means I'll have to give them the new phone back when the updates are working or what. I'm kind of partial to this one, now. But I do know that possibly bricking my phone with this KDZ or TOT stuff is a less appealing option than getting a free replacement and/or upgrade. I'll find out more tomorrow.
Click to expand...
Click to collapse
I have since flashed back to 48A via a 10B TOT flash. The reason I did this is to see if the error would show up in any of the other OTAs. They didn't. I have been on 48A since November 17th, and not ONE, I repeat, not ONE single SD card error has appeared. I have gone to 49A twice and both times, as soon as I get to 49A, SD card errors start popping up. And the SD card is fine (reformatted, did a full disk check on it). Any SD card I put in resulted in the error, and now with @nulloverride stating what he learned from the VZW rep pretty much confirms that the 49A OTA is the culprit.
So, I would state for anyone considering taking the 49A OTA to refrain from it. I've added a poll to see what the demographic is across K and non-K models of the VS985.
Again, this might be a dupe, but I feel it should be a main topic so that more people see it.
UPDATE #1 (11/21/2016):
Well guess what. No sooner do I post this and I get the dreaded "SD Card has been unmounted", but it remounted it right up. However, it occurred when I attempt to launch two apps that had just updated over the weekend that I hadn't launched since they were updated:
1. Google Opinion Rewards
2. Google Play Music
Both times, when I launched each app, I saw the SD card was unmounted but then it was remounted immediately without any issues. I'm wondering if these apps have been updated with new permissions and needed to remount the SD card? Maybe this is part of some new functionality? It does appear under 49A that maybe that is what is going on, however for me it causes the phone to have a "seizure" (as I like to say) and may not remount successfully for some reason. Strange. But, this time, under 48A, it mounted the card both times pretty quickly without any issue. So maybe this is normal when it works but under 49A, something is broken where it can't remount for some reason? Other than that, I have NOT seen this at all, so I wonder if in this case, it's an app issue (since both apps were recently updated). Not sure if the Rewards app needs access to the SD card, but I do have my music on the SD card, so Google Play Music would need to access the music from there.
UPDATE #2 (11/22/2016):
Switched SD cards and it happened again. Switched to a 2gb card. OUCH! So far, no issues. Wondering if it was the SD card all along? Upgraded to 49A since then and so far (fingers crossed) no issues. But, that's how it was before. This 2gb card is old, but hasn't been used much so hopefully, there aren't any bad areas. Surprised doing a chkdsk on the other SD cards didn't bring up anything. Will continue to monitor and update as I find more info.
Tekcafe rom VS98549A
https://www.youtube.com/watch?v=3FxIk7x-CaE
I've talked about this in another thread, forgetting I had this thread.
I have determined that in Safe Mode, I experience no issues with my SD card being unmounted unexpectedly. Once I boot back into Normal (Unsafe?) Mode, boom. SD Card becomes unmounted.
Something with the 49A OTA has broken something within the phone. This does NOT appear to be a hardware problem. But, the issue persists across ALL versions of the software (10b through 49A).
I called into Verizon today and they searched and saw that, as I already knew, I'm not the only one with this issue with this phone after the 49A OTA. She stated they are looking into the issue to resolve it. She's getting ready to patch me directly in with LG so we can discuss if they know what is going on. Seems like a firmware update issue that even a 10B TOT flash won't fix because it might be in a protected area of the phone that only the OTAs can update.
Also, I notice that 2 others have voted in the poll and are experiencing this issue and they are like me in that they have the older non-K model of the phone.
Okay. LG was of NO help. They said I could send my phone in and they would do a diagnostic and they have a way to flash it back to the way it was before the 49A OTA. Yeah, so do I which is 10B, etc. None of those work. Oh, and I would have to pay for any repairs as it's out of warranty.
I told her this was due to an official OTA. So basically, they can send out updates to out-of-warranty phones that break them, yet I would have to pay for any repairs? Sorry. That doesn't fly in my book.
Verizon said that they know of the issue and are looking into it, so I'll wait and see because if that is true, and they do come up with a fix, then I'm definitely going to wait because this phone has been great, and still is for me.
Now, if they want to send me a completely new phone free-of-charge and I turn this one in after I get the new one, yeah. I'll do that. And by new, I mean a replacement G3, preferably not refurbed. Heck, I'll take the K model because I won't root or flash back to 10b. I haven't for almost a year, except to try and debug this SD card issue I've been having since the 49A OTA.
In any case, anybody else that is having this issue, if you haven't already done so, reboot into safe mode. This is how you do it:
Power off the phone
Press and hold power + volume down until you see the menu
Choose Safe Mode and boot into it.
Once in Safe Mode, do things that would require writing and/or reading to/from your SD card (such as storing pictures from your camera on it). Copy files to your SD card, delete them, etc. Stay in that mode for as long as you can (you can still receive phone calls and text messages as well as make calls and send messages). You won't have access to any downloaded apps until you boot out of safe mode.
I want to know if this works for everyone, and then when they boot back into normal mode, if their SD card issues come back.
I've inspected the SD card slot. It is NOT damaged in any way. All pins are there and are in good condition. I think safe mode proves that. If this were a hardware failure, it should occur in safe mode and it doesn't. Something the 49A OTA updated (probably in a protected area of the firmware) is causing this and even flashing back to older versions doesn't overwrite that protected area. But for some reason, when in Safe Mode, it's either ignoring that area, or it's something else in the firmware that was updated that Safe Mode bypasses.
Okay, another update on my plight on figuring this out. I decided to uninstall two apps. Not sure why I chose them, but I did:
Greenify (mine I donated but I'm not rooted)
Nova Launcher (paid for)
I removed Nova because in Safe Mode, I'm running the default LG Home launcher. Greenify (even though it's not in root mode) I decided to remove since it's supposed to hibernate background processes.
Once I removed both, it appears so far that the problems have gone away. I haven't installed either one yet, but I will and I'll update what I find. If it's Greenify, then it must be something it's doing, which I find a little strange, but maybe the 49A update "broke" something in Greenify? If it's Nova, then again, something is going on with that.
I'm going to run without either app for the next day or so to see what happens. The thing I cannot understand is, I had ran without using either app I believe after factory resetting and still the problem persisted. So this might be a false positive for me. Definitely, safe mode the problem does not persist as I left my phone in safe mode for about 2 hours.
UPDATE: Okay. Apparently it wasn't Nova or Greenify as it started happening again after awhile. Safe Mode still cures it for some reason. It never umounts in Safe Mode, but once I reboot out of Safe Mode, it unmounts. So I guess we wait and see what Verizon/LG have to say about this, if anything. Not holding out too much hope though.
iBolski said:
Also, I notice that 2 others have voted in the poll and are experiencing this issue and they are like me in that they have the older non-K model of the phone.
Click to expand...
Click to collapse
I'm one of the ones who voted. I'm sorry, I misread the poll. I am NOT having any issues with my SD Card slot after the 49A update. Sorry for the confusion.
dmoney98 said:
I'm one of the ones who voted. I'm sorry, I misread the poll. I am NOT having any issues with my SD Card slot after the 49A update. Sorry for the confusion.
Click to expand...
Click to collapse
No biggie. Are you on a k model or non k model of the vs985?
Sent from my VS985 4G using Tapatalk
iBolski said:
No biggie. Are you on a k model or non k model of the vs985?
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
I am on the non-k model of vs985.
Dammit. Wish i would have read this before giving away my 128gb sd card. I thought it was just another failing piece of hardware.
First it was the internal mic.
Next the aux port.
Now the sd card slot.
So much for an upgrade from my unbreakable G2.
Time to revert to 12b and get my card back. Thanks OP!
(Non k)
afextwin said:
Dammit. Wish i would have read this before giving away my 128gb sd card. I thought it was just another failing piece of hardware.
First it was the internal mic.
Next the aux port.
Now the sd card slot.
So much for an upgrade from my unbreakable G2.
Time to revert to 12b and get my card back. Thanks OP!
(Non k)
Click to expand...
Click to collapse
I have no idea if it truly is an issue with the update or people's phones just started to miraculously start to fail after taking the OTA. I'm hoping it's the former and that there is a fix for this. In cany case, sorry to hear you gave away your SD card, but it sounds like you have more than just the SD card issue. I'm only having an SD card issue. No other failures. Your's definitely sounds like hardware failures with the list you gave and I doubt it's due to the upgrade.
I'm about ready to flash to a non-stock ROM to see if that might cure the issue.
iBolski said:
I have no idea if it truly is an issue with the update or people's phones just started to miraculously start to fail after taking the OTA. I'm hoping it's the former and that there is a fix for this. In cany case, sorry to hear you gave away your SD card, but it sounds like you have more than just the SD card issue. I'm only having an SD card issue. No other failures. Your's definitely sounds like hardware failures with the list you gave and I doubt it's due to the upgrade.
I'm about ready to flash to a non-stock ROM to see if that might cure the issue.
Click to expand...
Click to collapse
This might be unnecessary for me to remind you but I definitely recommend flashing the 10B TOT before testing to see if a custom ROM solves it, and if you decide to go back to fully stock I'd flash the 10B TOT once again beforehand.
Edit: Of course I forgot you're running completely stock, in which case flashing the TOT before will be necessary in order to root, etc, anyway.
roirraW "edor" ehT said:
This might be unnecessary for me to remind you but I definitely recommend flashing the 10B TOT before testing to see if a custom ROM solves it, and if you decide to go back to fully stock I'd flash the 10B TOT once again beforehand.
Edit: Of course I forgot you're running completely stock, in which case flashing the TOT before will be necessary in order to root, etc, anyway.
Click to expand...
Click to collapse
LOL. No biggie. I'm thinking of trying it just to see if the issue goes away, but if the 49A did touch a protected area that I cannot flash over, and that is the main reason why I see this issue across all version of the stock image, going to AOSP-based probably won't help, but it's still worth a look.
I guess what I need to do is backup my apps with LG backup, flash back to 10B, root, restore from LG Backup, then use TiBu to back up. Ugh! I know there is an LG Backup tool in the Google Play store, but I don't know if it will work from non-stock based ROMs.
iBolski said:
LOL. No biggie. I'm thinking of trying it just to see if the issue goes away, but if the 49A did touch a protected area that I cannot flash over, and that is the main reason why I see this issue across all version of the stock image, going to AOSP-based probably won't help, but it's still worth a look.
I guess what I need to do is backup my apps with LG backup, flash back to 10B, root, restore from LG Backup, then use TiBu to back up. Ugh! I know there is an LG Backup tool in the Google Play store, but I don't know if it will work from non-stock based ROMs.
Click to expand...
Click to collapse
As far as I know, the only LG Backup we can use is the one built into the stock ROMs. The one in the Play Store, unless there's another I'm unaware of, is for using on a non-LG device to move some of your data to an LG device, and according to the picture in the Play Store, looks like it has to happen between two different devices because they connect either directly via USB or wirelessly to do the transfer.
roirraW "edor" ehT said:
As far as I know, the only LG Backup we can use is the one built into the stock ROMs. The one in the Play Store, unless there's another I'm unaware of, is for using on a non-LG device to move some of your data to an LG device, and according to the picture in the Play Store, looks like it has to happen between two different devices because they connect either directly via USB or wirelessly to do the transfer.
Click to expand...
Click to collapse
Looks like Backup in 49A, revert to 10b, restore in 10b, root, TiBu it, flash AOSP ROM.
10b through 48A all show the same symptom. Might definitely be a hardware issue for me, but I find it really odd that as SOON as I upgraded to 49A, that's when my problems started. Never, I mean, never had one single issue with my SD card up until that point.
Still waiting to hear back from "possible solutions" to my issue from VZW. I have a feeling is "We can get you a discounted upgrade". Nope, nada, no way. If you broke it, you fix it for free, VZW.
iBolski said:
Looks like Backup in 49A, revert to 10b, restore in 10b, root, TiBu it, flash AOSP ROM.
10b through 48A all show the same symptom. Might definitely be a hardware issue for me, but I find it really odd that as SOON as I upgraded to 49A, that's when my problems started. Never, I mean, never had one single issue with my SD card up until that point.
Still waiting to hear back from "possible solutions" to my issue from VZW. I have a feeling is "We can get you a discounted upgrade". Nope, nada, no way. If you broke it, you fix it for free, VZW.
Click to expand...
Click to collapse
It was the same deal for myself (and for others) with my wife's SIM slot, except 49A wasn't even out yet, and she was on @xdabbeb 's VS985 v3.1.1 ROM. It's just ironic since although I haven't taken my SIM out a lot on my own G3, hers might've only been taken out once or twice since she got her phone. Never any hint of trouble and all of the sudden it no worky.
Since I've heard that the SIM slot is a common problem on the G3, and that the SIM and Micro SD card slot are both together, it could be that they're both just flaky. I certainly feel more secure with the SIM and Micro SD card trays, rather than slots.
By the way, I personally always had a lot of trouble using Titanium Backup on the G3 (and my my previous Galaxy S3). Especially for restores, always took a bunch of restarting to get everything restored. I'm guessing it has to do with such a custom framework because (not to be OT) on my HTC 10, which is very close to stock Android, and even a custom ROM based on the stock HTC Android, Titanium Backup was back to being completely dependable.
As many may know, I no longer have the G3. It died last week, so I'm now on the Samsung S7. It would still be interesting to see if Verizon does issue a fix IF the OTA is indeed what caused the SD card issue. But now I'm beginning to think my issue was hardware failure. I guess it was just blind luck/coincidence that right after the 49A OTA, that's when my SD card slot started to fail.