yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Yeah, tried that too. No luck. I also use the vr spell check but I've been installing that zip also. I'm dumbfounded and REALLY don't want to dirty flash. My backup is really old too so don't wanna do that either. Lol. Struggles :'(
[Verizon Samsung Galaxy S III] old&slow:
How's your battery doing now?
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Perfect now. The batts I got were f'd up for sure. Were you hinting at something? Lol. You next would tell me to reflash everything and that'll fix both things possibly. ;) is there a way to dirty without losing everything? Seems that this is possible but every time I do it doesn't work. Idk maybe I'm crazy.
[Verizon Samsung Galaxy S III] old&slow:
Lol, no, I really wasn't. :) Have you tried flashing the Note2 keyboard in the third post?
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Will try that now. Hey if I use a Nandroid of just system and data will that remove anything other than system stuff?
[Verizon Samsung Galaxy S III] old&slow:
Probably wind up with more f/c.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
YOU ARE A GOD AMONGST MERE MORTALS... The Note 2 zip worked. In a few I'll install the Note 3 zip and hope it works :) You should be in the HALL OF FAME, BRO [emoji3] [emoji3] [emoji3] [emoji3] [emoji3] [emoji106] [emoji106] [emoji106] [emoji106] [emoji106]
[Verizon Samsung Galaxy S III] vmancini3:
It's been a long time since I've posted anything in here so I just wanted to say what's up to all you guys one more time! I'm slowly trying to accept the fact that the whole "Verizon Samsung Galaxy S3" section of XDA seems like it'll be dead soon (very sad)! I am NOT updating to 4.4 no matter what, which is such a double-edged sword because I want my bootloader to remain unlocked but would like to at least experience 4.4 TW! I do have a question though... [MENTION=3074508]old&slow[/MENTION] , or anyone else for that matter, IIRC, flashing the stock kernel will reset the ramdisk back to normal, is that correct? Kind of a way to do some garbage cleanup after flashing kernel upon kernel upon kernel? And also, the only stock kernel that exists for 4.3 is the one you built from source, right?
[Verizon Samsung Galaxy S III] prdog1:
Note 3 zip never worked for me. Only the Note 2. :cool:

---------- Post added at 02:08 PM ---------- Previous post was at 02:05 PM ----------

Flashing any kernel always replaces the ramdisk unless it is like the DKP kernel and uses existing ramdisc and compiles on the fly. It is part of the image. I got tired of waiting and flashed CM today for the first time ever. lol Not bad so far. :cool:
[Verizon Samsung Galaxy S III] vmancini3:
Thanks for the quick reply [MENTION=4538493]prdog1[/MENTION] ! Yeah....I've switched back and forth between AOSP and TW more times than I can count and I have to say.....the only things that really bother me are.... I definitely like the TW browser better than any other and I've never been able to find a way to get the Verizon Visual Voicemail app to work on AOSP! Other than that, I don't have much of a problem with AOSP! It's always fun to switch things up every once and a while!
[Verizon Samsung Galaxy S III] old&slow:
Not much up these days. :( Like you, I'm not willing to lock down my S3 just yet by taking the OTA. Gonna hold out and see if some kind of work-around comes along.

The stock kernel that I built is a complete boot.img so it comes with it's own ramdisk instead of using the anykernel type setup that dkp uses like prdog1 mentioned. It's not the only source built kernel around. Scrosler had one in his thread too. I'm sure there's not a lot of difference between the two.
[Verizon Samsung Galaxy S III] lepa71:
How is the battery life on CM? I have heard that camera and battery life are still problematic on any AOSP/CM roms in compare to TW

I'm running Slim on my tab 2 7" and I can tell you that camera is nowhere close to closed source from TW. With kids running I can't survive without it.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
My wife just got the S5 and my daughter the 5s. They both have better signal strength than me. New modem out I should/could be using? Thanks :)
[Verizon Samsung Galaxy S III] vmancini3:
I believe it's MF1, ML1, then NE1 (from the 4.4 update) Have at it...

https://www.dropbox.com/s/c6072cr99thbs33/d2vzw_MF1_modem.zip?dl=0

https://www.dropbox.com/s/3rkt5r62cpzv4m6/d2vzw_ML1_modem.zip?dl=0

https://www.dropbox.com/s/g74hazorv1ff3ai/DNE1.modem.zip?dl=0

Although my guess is they have better hardware than we do, unfortunately???
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Yeah, I'm on ML1. I thought we couldn't install NE1 though, it's safe to flash? I agree on the better hardware part but if it's safe, I'll give NE1 a go. Thanks for the info.
[Verizon Samsung Galaxy S III] vmancini3:
Yeah....you can flash the NE1 modem!? I did. Don't know if it's gonna make anything better for you though as it didn't help me much! You can definitely try though.?
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Cool. Will try it out. Thanks again :)
[Verizon Samsung Galaxy S III] vmancini3:
NP dude?
[Verizon Samsung Galaxy S III] daehl:
Stuck at SGSIII Boot Logo

I am having the same problem. I have a SGS3 with an unlocked boot loader on radio MF1 and CWM 6.0.4.3 Recovery. I was previously running Bonestock 3.4 and decided to try this ROM. I performed all three wipes (data/cache/dalvik) and installed using the lean kernel. But it's stuck at the "Samsung Galaxy SIII" logo. I let it sit for twenty-five minutes before I started to panic. I pulled the battery and it immediately loads the screen again and is stuck.

I checked the MD5 on my ROM download, and it matches: 2247f8e8746e9fd9e8c14dcd3347037e

so it doesn't seem to be a bad download. Any suggestions? Is it because I am on an older radio? I was holding off upgrading the radio because I was worried about reverting to the MF1 radio if it didn't work (can't seem to find an MF1 radio-only .zip anywhere)

Pressing power button does nothing. So I pulled the battery and booted into recovery mode for a second install try... maybe try the stock kernel. or is the problem I need to upgrade the radio first?

UPDATE: That didn't help. I reinstalled using all default settings. Install process went perfectly again, but still stuck at "Samsung Galaxy SIII" screen upon reboot. Still haven't upgraded the modem though. Is that something I should be worried about?
[Verizon Samsung Galaxy S III] prdog1:
Try updating to CWM 6.0.4.5. Not sure what number started support for 4.3 but some older recoveries don't work. Even better upgrade to TWRP 2.7.1.0 using TWRP Manager from the Playstore. :cool:
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Okay, 1) above are all 3 radios. I don't think the radios have anything to do with your issue. 2) There is a zip in this thread called WipeGalaxyS3.zip, something like that. That may help you. 3) You may have to Odin back to stock and start over again.

Also, when you wipe everything, do it a few times. I was trained that 3 is the optimal number. Lol. I also feel that TWRP works better with the GS3, so maybe try that recovery if you need to Odin and start again. Good luck. :)
[Verizon Samsung Galaxy S III] prdog1:
Shouldn't need to start over. Just flash a newer recovery and wipe system, data,dalvik and cache. x 3 is a good practice. If Bonestock was not 4.3 base then need to wipe internal sd also so it can build sd with the new file structure. :cool:
[Verizon Samsung Galaxy S III] daehl:
Thanks. for the advice prdog1.

I just restored from my prior backup (Bonestock 3.4) and updated to CWM 6.0.4.5. Then I tried reinstalling this RM again. Still stuck at the SGS3 screen (for over five minutes)...

The instructions said it might take up to five minutes to boot, during that time how long should I expect it to display the SGS3 screen? (just a few seconds or for a long time?)

I will try installing TWRP 2.7 next...
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Anything more than 5 minutes there prob is an issue. Also, after installing this rom, you aren't adding any zips are you? Mods or radios? This needs a full boot before you start flashing mods or radios.
[Verizon Samsung Galaxy S III] daehl:
Still Stuck at SGSIII Boot Logo

Bonestock is Android 4.1.2 based. So it sounds like you're saying I need to wipe the internal SD as well. Just erase it? or are there any special formatting options for that? and is that done in recovery?

I didn't see that step anywhere in the instruction.

---------- Post added at 12:52 PM ---------- Previous post was at 12:48 PM ----------

Nope. Just installing this rom. I erased data/cache/dalvik 3x each, then installed this rom using all default values. No other flashing mods. Can't get it to boot up afterwards. Just stuck at SGS3 screen forever. It never asks about "disable recovery flash" either.
[Verizon Samsung Galaxy S III] prdog1:
That is a requirement for first flash of 4.3. If anything like pics that are stored on internal you won't be able to see them. Should be an option to format in CWM. Maybe in advanced. It is with all the other wipes in TWRP. Don't flash another kernel at same time. This looks like a recovery or kernel problem. Could also be download even tho the MD5 matches. :cool:

---------- Post added at 12:55 PM ---------- Previous post was at 12:52 PM ----------

Not sure if that disable is even in recovery anymore. That was for original locked bootloader work around. Most of us are using TWRP. Just seems more dependable to me. :cool:
[Verizon Samsung Galaxy S III] daehl:
Still Stuck at SGSIII Boot Logo

Thanks again for your advice prdog1. I'm going to try manually installing TWRP 2.7 next and look for that option to format the SD. I didn't see it in CWM.
[Verizon Samsung Galaxy S III] prdog1:
If have 3.4 back up can download TWRP Manager from playstore and it will flash it for you. Just pick d2vzw as device. :cool:
[Verizon Samsung Galaxy S III] old&slow:
You also might consider starting fresh with an Odin of MF1 then run Casual and then lastly, update your recovery. A good decrapifying couldn't hurt. :D
[Verizon Samsung Galaxy S III] prdog1:
Damn. I'm stuck on CM11. :p:cool:
[Verizon Samsung Galaxy S III] daehl:
F*CK!

I tried manually installing TWRP using the instructions at the bottom for rooted users..

http://techglen.com/2014/07/11/how-to-install-twrp-2-7-1-0-on-galaxy-s3-i9300/

While in the terminal it failed, saying there was no free space in that block.

So then I downloaded the TWRP Manager and installed for I9300 and now my phone is bricked!

Won't turn on. Pulled battery. Nothing. Any suggestions? Or am I screwed?
[Verizon Samsung Galaxy S III] old&slow:
I'm sure it's a lot better than when the S3 was my dd. I never could stay on it for long. Couldn't get a signal in the bunker of a building I work in and all of our access points hated my phone so no wifi either. [emoji20]
[Verizon Samsung Galaxy S III] prdog1:
Signal still a little iffy in some buildings. Everything else works except incoming call on bloototh. They broke that a couple builds back. I don't use bluetooth so it not bad. Wifi seems good. Phone signal still shows same dBm strength so not sure. I had trouble on stock in same part of building tho. :cool:
[Verizon Samsung Galaxy S III] old&slow:
Make sure you can boot into d/l mode. If so, start over with a fresh Odin.
[Verizon Samsung Galaxy S III] prdog1:
Not sure if won't turn on. Have to be able to get into download mode now if there is any chance to save it. Recovery controls charging also. Should have installed d2vzw. If won't boot at all will have to send to Mobile Tech Video and get it JTagged. :cool:
[Verizon Samsung Galaxy S III] daehl:
I'm a brick

Clearly I f*cked up and installed TWRP wrong. It won't power on now, won't boot to d/l mode. No sign of life whatsoever.

I don't understand your last message. What is Mobile Tech Video and JTagged?
[Verizon Samsung Galaxy S III] prdog1:
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/

$50 + shipping. Good and fast. Just have to let them know to keep it at MF1 so can unlock. They have downgrade service also which is same price. :cool:
[Verizon Samsung Galaxy S III] BadUsername:
Do a hard brick repair, first sticky in the q&a section. Can you type exactly what you imputed into the terminal?
[Verizon Samsung Galaxy S III] prdog1:
Not sure will work if can't power up. :confused:
[Verizon Samsung Galaxy S III] BadUsername:
Should still be able to boot off of an SD card even if he flashed twrp into the wrong block. Unless he overwrote something vital.
[Verizon Samsung Galaxy S III] prdog1:
Not a good spot. Went to the RPM partition. :rolleyes::cool:
[Verizon Samsung Galaxy S III] BadUsername:
Ya that would be bad.

He already posted the code?
[Verizon Samsung Galaxy S III] prdog1:
No but since he used TWRP to flash the I9300 recovery I compared the dev blocks. It went to block 6 which is RPM on I-535. :cool:
[Verizon Samsung Galaxy S III] BadUsername:
Yikes, that's an early boot block.

He could probably still jtag, they could probably write the rpm back to the block. I think?
[Verizon Samsung Galaxy S III] prdog1:
Yea. I believe they rewrite all those partitions. Makes sense it won't power on since that controls power management. :cool:
[Verizon Samsung Galaxy S III] BadUsername:
Anything written before the aboot block will prevent the phone from even booting to the SD card.
[Verizon Samsung Galaxy S III] zcar.300:
The setup wizard isn't supposed to take 45 mins to finish is it? Staring at the "please wait" screen now.
[Verizon Samsung Galaxy S III] old&slow:
No, sometimes it seems to take about 45 seconds which seems like too long. Are you in a spotty service area. Maybe taking a while to shake hands with the vzw server to confirm your number. Other than that, I've got nothing. Might try flashing again. I know you wiped data but make sure you got cache and dalvik too.
[Verizon Samsung Galaxy S III] zcar.300:
I canceled it by hitting the home button. It seems to be fine.
[Verizon Samsung Galaxy S III] old&slow:
Since I don't have a sim in mine I cancel out of it anyway. Otherwise it probably would sit there forever. I have installed it once while the phone was activated and don't remember it taking an insane amount of time to complete.
[Verizon Samsung Galaxy S III] daehl:
JTAG Repair

Hi, Prdog1.

I shipped out out my phone for a JTAG repair, and it's working again. I don't have it back in my hands yet, but I was just sent screen shots of it booted up and I it's clearly my home screen.

The thing that has me very confused is that I asked him to install TWRP 2.7 and this "Mostly Stock ML1" ROM while he was at it. He says did the latter, but not the former, and I am confused. He also sent me a screen shot confirming that I still have root, but he says I now have the stock boot loader, which sounds bad to me. How can I perform nandroid backups and install custom ROMs without a custom recovery? He says if I have root I don't need TWRP recovery, but that doesn't make sense to me, and I don't know how he could have installed a custom ROM without a custom recovery... maybe that's something the JTAG device can do by itself?

And yet, if my phone still has root, is there some way for me to still install TWRP recovery? (provided I select the correct phone model next time) But he says I risk getting a "verizon unauthorized error message" if I try to install TWRP, is that what would happen if my bootloader was locked again? but it sounds to me as if I have a locked boot loader I will be stuck on this custom ROM, right?

This is very confusing to me, and even though this is the fourth phone I've rooted (first SGS3), I feel like a total newb again. You've been very helpful so far, if you have any further advice or info I would appreciate it.
[Verizon Samsung Galaxy S III] prdog1:
Sounds like he may have jtagged the ML1 bootloader. I would check with him cause he can downgrade. Shouldn't have to pay twice. Jtag repair and downgrade is the same price. Need to see which bootloader it is. He may just not unlock them and will have to do when get back. Just make sure he flashed to MF1 and not ML1 firmware. And yes. He can jtagg the rom without unlocking and use recovery. As long as it is MF1 or below we can deal with it and unlock and add recovery. . :cool:
[Verizon Samsung Galaxy S III] daehl:
Custom ROMs on ML1?

Thanks, I've asked him to start over and JTAG my phone back to I535VRBMF1. Then I'll use Odin to unlock the bootloader and install a root, and then try TWRP again.

This is a newb question, and I hope I don't get slammed, but it's been a while since I rooted and I haven't been keeping up with recent developments. So what do people do who took the 4.3 update? Are they unable to install custom ROMs? If their bootloader is locked, how do they install ROMs and make nandroid backups without a custom recovery? or don't they?

I'm trying to make sense of the "TW 4.34 & 4.3 Sticky Roll-Up Thread" but it's just not making sense to me. They mention "safestrap" and I've never heard of that before, but from what I gather it doesn't sound so bad. But does it work well on a Verizon SGS3? It sounds better to have an unlocked bootloader with a custom recovery... any thoughts?
[Verizon Samsung Galaxy S III] prdog1:
They use safestrap which is a bootloader workaround. Can only run stock kernel and TW based roms. No custom kernels or AOSP. Uses a specialized recovery that only works with safestrap. 4.3 safestrap can only run 4,3 based roms. 4.4 only 4.4 roms because of having to use stock kernel.:cool:
[Verizon Samsung Galaxy S III] salwansk:
I need to hide this annoying warning in ongoing menu. But keep everything look as stock rom.

i just want to remove this

http://postimg.org/image/y2pkrn31l/

I tried to mess with SystemUI.apk (no luck).

I tried to mess with Setting storage>settings.db>secure "through SQL editor" (no luck).

I really like this looking stock rom, except this ongoing panel with roaming.....

any ideas how to remove the roaming warning panel? or if i can remove the whole ongoing panel too!!!

Thanks
[Verizon Samsung Galaxy S III] n2locarz:
Battery issue

Thanks for all the great work on this rom. I love it. I am having a phone charging. When I plug my phone in, it shows the charging indicator. But the battery doesn't charge. I have OEM battery and 3 aftermarket 3.7vdc 2900mAh batteries. They also behave the same way. I purchased 2 more aftermarket batteries 3.7vdc 2300mAh. They also will not charge. I have a wall charger so I am having to swap batteries often. I booted to recovery and cleared the cache but that didn't work. Any ideas? I was thinking about wiping and reflashing everything but wanted to get your feedback first. Thanks
[Verizon Samsung Galaxy S III] old&slow:
Hello n2locarz, n2lotrukz here. lol [emoji13] [MENTION=5674847]NoCrAppleHere[/MENTION] was having a similar issue. Don't remember how he straightened it out. He may have Odined back to stock and started over.
[Verizon Samsung Galaxy S III] old&slow:
Oops. Double post....[emoji20]
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Hey [MENTION=1103995]n2locarz[/MENTION]

I truly believe it was an app I used to use called Better Battery Life. Do you use this app or a similar one? I did do a full wipe 3x and reinstall the rom bc I had lost the functionality of my Note 3 keyboard port, but I had the battery issues figured out by then though. I had one new battery in and I'd say "0% charging" forever. I thought it might be the app I mentioned, so I ran the app as the phone was plugged in charging and low and behold, the damn thing started charging just fine after that. Hope this helped. :)

P.s. I don't ever use aftermarket anything, it's not a good practice if you want your electronics to last and oem stuff can be found online so cheap, why would you not buy oem. Lastly, a young girl had her GS4 under her pillow at night and it started a fire. Damn phone melted and caught on fire then spread to her sheets, pillows, etc. She was ok but she was using an aftermarket battery. True story, Google it :(
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Damaged GS3 advice

Hey all, hoping someone has some advice. My sister dropped her GS3 in some tea today and it works fine except for the back button and page button that are on the bottom of the phone on the sides of the physical home button. They won't light up or respond to touch. I was able to take the phone apart and look inside, all looks normal. It has no moisture left in there from the tea or any rust or the like. I just disconnected a few flex ribbons. rubbed my finger over the innards and played with the wifi wire but that was no help. I just don't know what to play with or look for to get this working again, if the parts aren't fried inside that is. I used to pull apart my old v710 and moto E815 but this is a different ball game. Any ideas on what I can do to get this working again? Thanks a bunch :):):) [MENTION=4538493]prdog1[/MENTION] and [MENTION=3074508]old&slow[/MENTION] any ideas?
[Verizon Samsung Galaxy S III] MIKEYSAKZ:
Maybe it just needs time and in the mean time you can edit the build prop to enable soft keys temporarily brother
[Verizon Samsung Galaxy S III] old&slow:
Exactly what he said.
[Verizon Samsung Galaxy S III] MIKEYSAKZ:
My bad seems I can't read good
[Verizon Samsung Galaxy S III] old&slow:
Lol, no, I meant exactly what you said.[emoji4]
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Phone isn't rooted or anything. Just stock running 4.4. So I guess I just wait it out then? :-/
[Verizon Samsung Galaxy S III] vmancini3:
Well, if there is no way to get a new or replacement phone if that winds up being the case (hopefully not), then I'd suggest using towelroot so you CAN edit the build.prop to get the on screen soft keys like MIKEYSAKZ suggested... Really would be the only option at that point...
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Error

---------- Post added at 04:07 PM ---------- Previous post was at 04:00 PM ----------

I'll look into Towelroot. Just hoping her buttons just start working again soon. Lol. Tried to find an app but none have the menu/page button as an option.
[Verizon Samsung Galaxy S III] vmancini3:
If you want it...

https://www.dropbox.com/s/jegotl2fg32vcrb/TowelRoot.apk?dl=0
[Verizon Samsung Galaxy S III] NoCrAppleHere:
File isn't there in Dropbox, Vm. Also, can I do this after using Towelroot? http://brandtkrueger.wordpress.com/...ation-buttons-on-the-galaxy-s3-requires-root/

Thanks :)
[Verizon Samsung Galaxy S III] old&slow:
Yep. The build.prop edit is all you need to worry about.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Even though I can't dl it from Vm's Dropbox, the file for towelroot looks like a apk file, is it that simple? Just install the apk and follow instructions?
[Verizon Samsung Galaxy S III] old&slow:
Assuming so. I haven't used it yet.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
I'll research it thoroughly bc I'm not looking to make a bad situation worse. Lol. Thanks.
[Verizon Samsung Galaxy S III] old&slow:
Here ya go, https://towelroot.com
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Cool. Thanks. I was just goggling it. U DA MAN!!! :)
[Verizon Samsung Galaxy S III] prdog1:
It will work or it won't. Check kernel date in Settings. Has to be before June 6 I think. Original 4.4 update kernel was dated before that. Don't know if any other updates were released. Kernel exploit was patched on June 6. :cool:
[Verizon Samsung Galaxy S III] NoCrAppleHere:
I installed towelroot fine and I checked root with root checker, I have root access now on the phone. When I use the text editor to mess with build.prop and then save, says system is write only. I tried using ES file explorer to mount the system but it won't. I assume I need super user of some sort? I tried installing super su # but it said it detected Knox, try to disable? I GOT OUT OF THERE FAST A F*CK!!! Lol. Help please. Thanks