After perma-bricking it I bought a new motherboard for it so I can get it working again. Yes i've tried everything, beside a jtag, It's gone. I don't want to make a repeat mistake so i'd like to know the exact way to getting from stock android to CM12 on this S III.
modman2 said:
After perma-bricking it I bought a new motherboard for it so I can get it working again. Yes i've tried everything, beside a jtag, It's gone. I don't want to make a repeat mistake so i'd like to know the exact way to getting from stock android to CM12 on this S III.
Click to expand...
Click to collapse
So I'm trying to get twrp and cyanogenmod on my 4.4 kitkat sgs3 i535 and from what I have read and tried the only stable version supported is the 10.2.1 and getting that you have to have a custom recovery.(or so I have heard) But I am still trying to get twrp on my gs3 but since it is 4.4 with knox bootloader I am not finding anything on it and if you try (from what I have read) it trips a security fuse and sets a bit from 0x0 to 0x1 and soft bricks it. But thankfully there is this
I thought I had to use it but since my root file system is in read only twrp couldn't make any changes. but there is this to but since it is read only i cant change that platform.xml at all. so this is where I'm stuck and I hope it helps. please post back here if you find anything out. desperately want this bloatware gone and to have some customizability.
http://forum.xda-developers.com/showthread.php?t=2797314
http://forum.xda-developers.com/showthread.php?t=2639337
these will help a bit as well.
If your phone is on 4.4 kitkat, your bootloader is locked and you cannot install TWRP or any other custom recovery. Because of that, you cannot put CM of any kind on the phone. You are limited to safestrap and just a few Touchwiz based ROMs which can be found in the Verizon Galaxy S III Android Development section.
Have any of you tried using the method outlined on the CM wiki page?
http://wiki.cyanogenmod.org/w/Install_CM_for_d2vzw
CaliTilt said:
Have any of you tried using the method outlined on the CM wiki page?
http://wiki.cyanogenmod.org/w/Install_CM_for_d2vzw
Click to expand...
Click to collapse
landshark68 said:
If your phone is on 4.4 kitkat, your bootloader is locked and you cannot install TWRP or any other custom recovery. Because of that, you cannot put CM of any kind on the phone. You are limited to safestrap and just a few Touchwiz based ROMs which can be found in the Verizon Galaxy S III Android Development section.
Click to expand...
Click to collapse
As landshark mentioned DO NOT even attempt to flash any CM rom on a locked bootloader. You have a very high chance of hard bricking the device
Sent from my Nexus 5
Related
Before you ask, yes, I have searched. I also went through each page of the "Here are the similar threads we found:" section before posting. That is actually why I am posting. I see too many different answers.
A little background: I know my way around android in general and have been flashing roms since my G1. I used to be the "rom test dummy" for JesusFreak (yeah, im an oldtimer) so I am not afraid of flashing roms. I am currently running on a windows machine, but I have linux available if that is any easier. I am comfortable in either.
My question: I have a Nexus 5 with 4.4.2 (stock) KOT49H and I want to update finally. Each time I have tried the OTA it gave errors, and I eventually found that is because the rom looks for modifications. Out of the posts I have found here, I have seen some say you have to flash all the way back to stock and then start updating. I have also seen posts that say there are tools that will read your device info and decide what to flash. I have seen some that say you can flash a new (stock) rom over the current rom.
I have no problem backing up the device (I have paid premium) if needed. If I can flash without wipe, GREAT. If not, no big deal. My main thing is that I would like a safe route. This is my main phone so I need it to work. I would also prefer one of the shorter (of the safe) methods. I saw a guide a few minutes ago that seemed to say that you should flash 4x during the process. Once to clean the rom, once to downgrade, and 2 more to upgrade. I am hoping I read that one wrong, but that sounds un-needed. Is there a stock 4.4.4 rom that I can just flash on top of my current 4.4.2 and get it all done in one jump?
Darkrift said:
Before you ask, yes, I have searched. I also went through each page of the "Here are the similar threads we found:" section before posting. That is actually why I am posting. I see too many different answers.
A little background: I know my way around android in general and have been flashing roms since my G1. I used to be the "rom test dummy" for JesusFreak (yeah, im an oldtimer) so I am not afraid of flashing roms. I am currently running on a windows machine, but I have linux available if that is any easier. I am comfortable in either.
My question: I have a Nexus 5 with 4.4.2 (stock) KOT49H and I want to update finally. Each time I have tried the OTA it gave errors, and I eventually found that is because the rom looks for modifications. Out of the posts I have found here, I have seen some say you have to flash all the way back to stock and then start updating. I have also seen posts that say there are tools that will read your device info and decide what to flash. I have seen some that say you can flash a new (stock) rom over the current rom.
I have no problem backing up the device (I have paid premium) if needed. If I can flash without wipe, GREAT. If not, no big deal. My main thing is that I would like a safe route. This is my main phone so I need it to work. I would also prefer one of the shorter (of the safe) methods. I saw a guide a few minutes ago that seemed to say that you should flash 4x during the process. Once to clean the rom, once to downgrade, and 2 more to upgrade. I am hoping I read that one wrong, but that sounds un-needed. Is there a stock 4.4.4 rom that I can just flash on top of my current 4.4.2 and get it all done in one jump?
Click to expand...
Click to collapse
easiest way(if running a custom recovery).. find a rooted stock here in the andtoid development section, and dirty flash(no wiping) it over what you have. you won't lose any data dirty flashing.
if your completely stock, easiest way.. flash the 4.4.4 factory img via fastboot. but you will lose your data.
simms22 said:
easiest way(if running a custom recovery).. find a rooted stock here in the andtoid development section, and dirty flash(no wiping) it over what you have. you won't lose any data dirty flashing.
if your completely stock, easiest way.. flash the 4.4.4 factory img via fastboot. but you will lose your data.
Click to expand...
Click to collapse
Thanks for the info, but can you point to a 4.4.4 rooted stock? I have been searching through the roms and most seem to be customized, not stock. Ive gone through about 7 pages now in http://forum.xda-developers.com/google-nexus-5/development
I havent flashed a rom in a year or 2 since buying Nexus 4/5 devices (hey, they just work) so I am a little out of the loop.
**Edit: I just found this: http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523 - Maybe I missed it the first time. I think its because the URL says 4-4-3, so I skipped it.
Darkrift said:
Thanks for the info, but can you point to a 4.4.4 rooted stock? I have been searching through the roms and most seem to be customized, not stock. Ive gone through about 7 pages now in http://forum.xda-developers.com/google-nexus-5/development
I havent flashed a rom in a year or 2 since buying Nexus 4/5 devices (hey, they just work) so I am a little out of the loop.
**Edit: I just found this: http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523 - Maybe I missed it the first time. I think its because the URL says 4-4-3, so I skipped it.
Click to expand...
Click to collapse
thats a good one.. if i go with stock, its going to be a @bigxie rom. and i was around as well for jesus freke
Awesome, thanks. I will flash that when I get home after making a backup.
I struggled with this and finally succeeded by flashing first to 4.4.3, THEN to 4.4.4. Now running like a top.
bltzfsck said:
I struggled with this and finally succeeded by flashing first to 4.4.3, THEN to 4.4.4. Now running like a top.
Click to expand...
Click to collapse
awesome!
Hello Everyone, been a long time lurker in these forums and had a question that I would really like yalls input on.
I have a Verizon Galaxy S 3 and I have it running Paranoid Android 4.6 Beta 5 that has also been encrypted. I am trying to flash a new rom on to my device but have been preceding cautiously since I know the encryption may cause problems. Currently I have teamwin recovery installed and it prompts me for the encryption code before stating, but always says I have the wrong code. If i bypass the code in the recovery, i can view files in my sd card but not off internal storage, so I don't know how this will effect flashing a rom from the sd to write over internal.
So I have a feeling I may have to odin back to stock and reroot, problem is I don't know what version to odin back to. I know that if I flash 4.3 onto the device I will not be able to unlock my bootloader again, and Im not sure if its possible for me to odin back to a previous version of stock without causing a brick.
Please throw in yalls input, I need every opinion I can get.
Is it possible for me to take my phone running on Paranoid Android 4.5 Beta 5 which says android version 4.4.4 and flash a Stock Rom thru odin at version 4.1.2 for example so i can reroot and unlock the bootloader again??
Thanks for your help in advance, and may this community live forever.
I would suggest to Odin back to 4.1.2, as 4.3 and up are locked
Sent from my Nexus 5
Thanks for the reply!
I was thinking going that route too, but needed a second opinion.
Do you think I could flash 4.1.2 over the rom if its running android version 4.4.4 .? I was hesitant to have already done cause I wasnt sure if it would cause a brick or not. I need a better understanding of Odins process of flashing the stock rom.
ajthearmo said:
Thanks for the reply!
I was thinking going that route too, but needed a second opinion.
Do you think I could flash 4.1.2 over the rom if its running android version 4.4.4 .? I was hesitant to have already done cause I wasnt sure if it would cause a brick or not. I need a better understanding of Odins process of flashing the stock rom.
Click to expand...
Click to collapse
As long as your bootloader is unlocked to can yes. But, if your on one of the locked bootloaders do not even attempt to do that
Before you attempt to flash anything what version of Android are you currently on?
Sent from my Nexus 5
That's what I needed to hear. Thank you.
I'm running 4.4.4 , its off a build of paranoid android. I also have unlocked my boot loader before I installed this ROM.
I just got given a Verizon Galaxy S3 by my friend, since he just got a new iPhone and my phone's battery only lasts a couple hours at this point.
He's not a techie and was running the stock ROM. I've always been one to run CM.
He's done the OTA update and the system is 4.4.2, NE1 build. I've read all over that you can't downgrade to a ROM of a lower version because of the bootloader. I don't like the idea of having a locked bootloader, nor having to use safestrap over CWM. And definitely not being limited to TouchWiz based ROMs.
I found this, which is a bootloader downgrade on the same phone, but it's before the pew pew pew mega lockdown got put on these phones, I think.
http://forum.xda-developers.com/galaxy-s3/general/how-to-flash-to-bootloader-updated-t2083860
I also found several videos on Youtube of people claiming they downgraded from 4.3 (not sure if it's ok to post external links, so I won't, but it's an easy search).
But, I don't necessarily trust this. XDA is usually the source I trust. Thanks, and sorry if this gets asked all the time! I did search!
DrSteveBrule1 said:
I just got given a Verizon Galaxy S3 by my friend, since he just got a new iPhone and my phone's battery only lasts a couple hours at this point.
He's not a techie and was running the stock ROM. I've always been one to run CM.
He's done the OTA update and the system is 4.4.2, NE1 build. I've read all over that you can't downgrade to a ROM of a lower version because of the bootloader. I don't like the idea of having a locked bootloader, nor having to use safestrap over CWM. And definitely not being limited to TouchWiz based ROMs.
I found this, which is a bootloader downgrade on the same phone, but it's before the pew pew pew mega lockdown got put on these phones, I think.
http://forum.xda-developers.com/galaxy-s3/general/how-to-flash-to-bootloader-updated-t2083860
I also found several videos on Youtube of people claiming they downgraded from 4.3 (not sure if it's ok to post external links, so I won't, but it's an easy search).
But, I don't necessarily trust this. XDA is usually the source I trust. Thanks, and sorry if this gets asked all the time! I did search!
Click to expand...
Click to collapse
That Guide mentions 4.1 which had the ability to be unlocked, do not even attempt to try to unlock the bootloader as you will brick your device.
Once the device has taken the OTA to either 4.3 ML1 or 4.4.2 NE1 it's no longer unlock able and your stuck with it
Sent from my Nexus 5
ShapesBlue said:
That Guide mentions 4.1 which had the ability to be unlocked, do not even attempt to try to unlock the bootloader as you will brick your device.
Once the device has taken the OTA to either 4.3 ML1 or 4.4.2 NE1 it's no longer unlock able and your stuck with it
Sent from my Nexus 5
Click to expand...
Click to collapse
Welp, thanks for confirming the worst.
I'll be heading over here now...
http://forum.xda-developers.com/gal...st-7-10-14-t2812189/post54062704#post54062704
I just picked up an i535 with NE1 today for cheap. It looks like I am in the same boat you are.
It will not be my daily driver, I have an i747 for that - so still an SGS3. It looks like I have a lot of reading to do regarding the i535. I had seen the term locked bootloader and was thinking it meant similar as to on my i747. That is, you can not downgrade the bootloader to an older version. For my other device I can still flash custom ROMs even if I am on a 4.4.x bootloader, whether TW or AOSP based. I guess that may be difficult with the i535.
bootloader downgrade with JTAG ?
I'm also in the same boat. After one day of trying to install cyanogenmod on this device, brick the phone, reinstall the stock rom 44.2, trying again, brick again, etc., I get that we can only install custom recovery with a lower version of bootloader.
Now, as DrSteveBrule1, I think there is a way to install the older bootloader with JTAG. Does anyone on XDA have experience that he can share regarding this ? I have several JTAG devices at work but I'd like to have confirmation that it can work and some instruction if possible.
Thanks again to XDA forums (this is my first post )
Tomo59 said:
I'm also in the same boat. After one day of trying to install cyanogenmod on this device, brick the phone, reinstall the stock rom 44.2, trying again, brick again, etc., I get that we can only install custom recovery with a lower version of bootloader.
Now, as DrSteveBrule1, I think there is a way to install the older bootloader with JTAG. Does anyone on XDA have experience that he can share regarding this ? I have several JTAG devices at work but I'd like to have confirmation that it can work and some instruction if possible.
Thanks again to XDA forums (this is my first post )
Click to expand...
Click to collapse
Jtag should work (don't quote me on that however) Jtag is pretty much the only option you have to downgrade the bootloader once it's locked. People have confirmed it working but not everyone has had the same results
Sent from my Nexus 5
I looked through the forums and I found a few threads but they said things like "DO NOT USE IF YOU UPDATED TO 4.1.2".
I've rooted my Galaxy Note 10.1 (2014 Edition). All I did was flash CF AUTOROOT with ODIN, flashed the TeamWin Recovery, and from there I just moved ROMs over to the device and flashed them from TWRP.
There seems to be outdated info (or maybe I'm just being illiterate) for the SCH I535 because not a lot mentions 4.4.2.
Thanks for all your help! I would really like to try new roms on the S3.
bluelamb said:
I looked through the forums and I found a few threads but they said things like "DO NOT USE IF YOU UPDATED TO 4.1.2".
I've rooted my Galaxy Note 10.1 (2014 Edition). All I did was flash CF AUTOROOT with ODIN, flashed the TeamWin Recovery, and from there I just moved ROMs over to the device and flashed them from TWRP.
There seems to be outdated info (or maybe I'm just being illiterate) for the SCH I535 because not a lot mentions 4.4.2.
Thanks for all your help! I would really like to try new roms on the S3.
Click to expand...
Click to collapse
I picked up a used i535 a few months ago as a device to mod and learn. I had no intentions of using it as my daily phone - I'm on AT&T with an i747. I found it was already on the NE1 bootloader and modem, I hadn't read enough before purchasing.
I was able to root it with TowelRoot. Following that I installed BusyBox and then installed SafeStrap Recovery for devices with the NE1 bootloader, see here.
From what I have seen there are three ROMs available to this device on NE1; stock NE1, SuperLiteROM, and Paul Pizz. This thread is a good resource for all but Paul Pizz, which is here. I after installing SafeStrap I flashed SuperLiteROM to the stock slot, it seems to avoid some issues when flashed here instead of a secondary slot. Since then I have installed XPosed framework and have several mods working with no issues.
dawgdoc said:
I picked up a used i535 a few months ago as a device to mod and learn. I had no intentions of using it as my daily phone - I'm on AT&T with an i747. I found it was already on the NE1 bootloader and modem, I hadn't read enough before purchasing.
I was able to root it with TowelRoot. Following that I installed BusyBox and then installed SafeStrap Recovery for devices with the NE1 bootloader, see here.
From what I have seen there are three ROMs available to this device on NE1; stock NE1, SuperLiteROM, and Paul Pizz. This thread is a good resource for all but Paul Pizz, which is here. I after installing SafeStrap I flashed SuperLiteROM to the stock slot, it seems to avoid some issues when flashed here instead of a secondary slot. Since then I have installed XPosed framework and have several mods working with no issues.
Click to expand...
Click to collapse
Thanks for your help! I have got SuperLiteROM running now. I don't know anything about mods so I'll read about them and see I would like to try any. I think I have XPosed on my tablet tho.
bluelamb said:
Thanks for your help! I have got SuperLiteROM running now. I don't know anything about mods so I'll read about them and see I would like to try any. I think I have XPosed on my tablet tho.
Click to expand...
Click to collapse
It's good to hear that you have it working for you.
Hi all oyu guys and SpyroDazee, I present myself with humbleness and urge because I hardbricked my wife´s Verizon S3 and she is now really upset to me :S ..... said that I would like to be helped if i may to restore this device, I can get in touch by facebook chat, whatsapp or other...i have an HTC M9 and i am a regular helper on this M9 issues in the propper section. Here is what i Did, i was trying to flash another crom and did exactly as i am listing:
1.-Applied towelroot to roort on 4.4.2
2.-Applied EZ-Unlock app and supposdely unlocked.
3.-instellaed twrp from gplay and installed version 2.8.7.0 from Android on work (not booted in any mode, installed from android).
4.-Since not worked that way I tried to push with adb shell flashing IT, SO REBOOT AND PHONE HARDBRICKED NOT TURNING ON.
5.- Using this tutorial i flashed a 16 gb micro SD booted phone (from SD succesfullt) and tried to restore bootloader, when i adbe shell commands (not working from terminal emulator) and I rebooted, phone hardbricked even worse, NOW not BOOTING FROM sd ANYMORE...im stuck at this point at this very moment.....
So if you colud helpme, i can take picture to phone, and place chat with facebook or whats app, im so desesperated my wife is going to fry my M9 if i dont fix her S3.
Thnaks a lot you all guys! Have a nice weekend!
LLegion said:
1.-Applied towelroot to roort on 4.4.2
2.-Applied EZ-Unlock app and supposdely unlocked.
3.-instellaed twrp from gplay and installed version 2.8.7.0 from Android on work (not booted in any mode, installed from android).
4.-Since not worked that way I tried to push with adb shell flashing IT, SO REBOOT AND PHONE HARDBRICKED NOT TURNING ON.
5.- Using this tutorial i flashed a 16 gb micro SD booted phone (from SD succesfullt) and tried to restore bootloader, when i adbe shell commands (not working from terminal emulator) and I rebooted, phone hardbricked even worse, NOW not BOOTING FROM sd ANYMORE...im stuck at this point at this very moment.....
Click to expand...
Click to collapse
With the Verizon i535 on the NE1, 4.4.2, bootloader steps 2 and 3 are definite ways to brick your phone. Apparently so is step 4,were you pushing TWRP using ADB?
What was the Android version of the ROM you used for the sdcard debrick image?
What bootloader did you try to install with adbe shell commands?
Both should have matched the bootloader that was on the phone at that time, NE1 in your case. I would suggest trying another sdcard debrick image with a 4.4.2 bootloader and modem.
---------- Post added at 09:51 PM ---------- Previous post was at 09:22 PM ----------
@LLegion
If you do not have a 4.4.2 debrick image one can be found in this thread.
dawgdoc said:
With the Verizon i535 on the NE1, 4.4.2, bootloader steps 2 and 3 are definite ways to brick your phone. Apparently so is step 4,were you pushing TWRP using ADB?
What was the Android version of the ROM you used for the sdcard debrick image?
What bootloader did you try to install with adbe shell commands?
Both should have matched the bootloader that was on the phone at that time, NE1 in your case. I would suggest trying another sdcard debrick image with a 4.4.2 bootloader and modem.
---------- Post added at 09:51 PM ---------- Previous post was at 09:22 PM ----------
@LLegion
If you do not have a 4.4.2 debrick image one can be found in this thread.
Click to expand...
Click to collapse
After the many topics and posts here on xda I still don't get why people keep trying to push custom recoveries to the locked 4.4.2 bootloader. It boggles my mind. I've told probably close to 100 people here about this same issue time and time again
Sent from my Nexus 5
Hi guys- sorry for a little threadjack, but I have a quick question and wanted confirmation.
I have the opportunity to buy another S3 (Verizon) that shows Android 4.1.1 installed.
At what point did the bootloader get locked? I know 4.4.2 is locked, but there's a couple of steps in between.
Thanks-
ah- a bit more googling and I got it- anything past 4.2.2 is locked by q-fuse.
http://wiki.cyanogenmod.org/w/Install_CM_for_d2vzw
Looks like I'm gonna get a fresh S3!
phonetool said:
Hi guys- sorry for a little threadjack, but I have a quick question and wanted confirmation.
I have the opportunity to buy another S3 (Verizon) that shows Android 4.1.1 installed.
At what point did the bootloader get locked? I know 4.4.2 is locked, but there's a couple of steps in between.
Thanks-
Click to expand...
Click to collapse
Right, the 4.4.2 bootloader is locked. I haven't checked any other changes re: restrictions applied earlier than 4.4.2. However, I seem to recall that once you receive the 4.3 bootloader you are no longer able to downgrade to previous versions. I know this is true for the AT&T (i747) and T-Mo (T999) versions of the SGS3. I do not believe that it was locked at 4.3 in the sense that you could not install a custom recovery or a custom ROM.
Do not take any action based on those statements, verify them first. I would hate to see someone brick a phone because I was wrong. (I am certain about what I said about the i747, but I have not searched re: the i535 on 4.3 because mine already had 4.4.2 when I bought it.)
To complicate matters, I just took a peek at sammobile.com ( http://www.sammobile.com/firmwares/database/SCH-I535/ ) and saw that there were two versions of 4.3 released for the i535, I535VRUCML1 and then I535VRUCNC1. When you read be aware that what holds true for the earlier version (ML1) may be untrue for the latter (NC1). In fact, count on there being important differences.
Looked through google, looked through threads, can find nothing whatsoever to help.
Have Verizon Samsung Galaxy S III Unlocked running Straight Talk VIA sim card. Everything works.. as a regular old phone with root. (rooted with Kingoroot - basically I googled "root galaxy s3" and followed those steps.. that much works fine, though it is not to be confused with the chinese king root. I tried the trick of swapping out king root for SU and, well.. yeah didnt work.)
Problem is I'm running 4.4.2 (the dreaded locked bootloader) and everything I try when it comes to installing custom recovery either doesn't work, bootloops the phone, or hard bricks it. v_v
so as someone who backs up their backups, (thank you OCD fairy), running around with a phone I can't backup puts me on edge, to say the least.
tried safestrap (says not secured. still says not secured after install. does nothing.)
tried various CWM and TWRP via apk installs (whatever that app is you install then tell it to install cwm) ..wouldn't install
Odin, depending on which version I install (e\ not which version of odin, which version of custom recovery), either gives me errors or hardbricks my device.
SO.. I'm looking for someone who has a Verizon Galaxy S III and who has a custom recovery on it to tell me how the devil they managed that one.
Cheers all!!
Drach0n said:
Looked through google, looked through threads, can find nothing whatsoever to help.
Have Verizon Samsung Galaxy S III Unlocked running Straight Talk VIA sim card. Everything works.. as a regular old phone with root. (rooted with Kingoroot - basically I googled "root galaxy s3" and followed those steps.. that much works fine, though it is not to be confused with the chinese king root. I tried the trick of swapping out king root for SU and, well.. yeah didnt work.)
Problem is I'm running 4.4.2 (the dreaded locked bootloader) and everything I try when it comes to installing custom recovery either doesn't work, bootloops the phone, or hard bricks it. v_v
so as someone who backs up their backups, (thank you OCD fairy), running around with a phone I can't backup puts me on edge, to say the least.
tried safestrap (says not secured. still says not secured after install. does nothing.)
tried various CWM and TWRP via apk installs (whatever that app is you install then tell it to install cwm) ..wouldn't install
Odin, depending on which version I install (e\ not which version of odin, which version of custom recovery), either gives me errors or hardbricks my device.
SO.. I'm looking for someone who has a Verizon Galaxy S III and who has a custom recovery on it to tell me how the devil they managed that one.
Cheers all!!
Click to expand...
Click to collapse
A custom recovery can only be flashed on an unlocked bootloader. Trying to flash a custom recovery on a locked bootloader will result in a brick. The only available recovery on it is safestrap
Sent from my Nexus 5
ShapesBlue said:
A custom recovery can only be flashed on an unlocked bootloader. Trying to flash a custom recovery on a locked bootloader will result in a brick. The only available recovery on it is safestrap
Sent from my Nexus 5
Click to expand...
Click to collapse
..I gathered that. I was basing my attempts off the threads I found where the OP "forgot" to mention which android OS he was using on his (or her) galaxy s3 and then omigawd installed custom recovery on it. Where nobody has yet been able to unlock the 4.3 and 4.4.2 bootloader for the galaxy s3 as yet (to my knowledge; if I'm wrong please correct me) this leaves me with safestrap, the custom recovery that doesn't touch the bootloader during install. I know this as well. Perhaps I should have clarified this, but I thought it was obvious to the folks at xda. *shrugs*
And the part where I said safestrap isn't working for one reason or another is where I was hoping to attract someone who knew how to help instead of someone who only knows how to make generic statements (+1) [e\ ftr, attempting to flash non-safestrap recoveries resulted in an error 4 times out of 5, not a brick.]
that said, I will ask again, if someone has 4.4.2 on their s3 as well as custom recovery, please come post here.
sadly, inb4 more +1ers
When you ask a question that's been asked and answered dozens of times before, you're going to get the same "generic statement" in response, because it's the right answer to your question. Your bootloader can't be unlocked, and therefore you can't install a custom recovery on your phone.
Jacquestrapp said:
When you ask a question that's been asked and answered dozens of times before, you're going to get the same "generic statement" in response, because it's the right answer to your question. Your bootloader can't be unlocked, and therefore you can't install a custom recovery on your phone.
Click to expand...
Click to collapse
*sigh* another illiterate. Try reading before posting yeah? I *know* my bootloader cant be unlocked, and I know that a custom recovery /can/ be installed, or are you saying safestrap doesn't exist? look I'm asking for help here not drivel.
..rerolling..
Q: What did you have for breakfast today?
A1: last week, I had breakfast in Deleware!
A2: Last night's dinner was good!
...
xda: the community where post count means more than relevant answers.
*sigh*
looks like I'm going to have to figure out safestrap on my own. whether there is another method for installation besides via apk, why it failed to install, whether safestrap is the only custom recovery that works by not touching the bootloader, why it hardbricked my phone.. etc
guess I'll post the answers somewhere intelligent like Android Authority.
have fun with your +1s
now go die in a fire. cheers
Drach0n said:
Q: What did you have for breakfast today?
A1: last week, I had breakfast in Deleware!
A2: Last night's dinner was good!
...
xda: the community where post count means more than relevant answers.
*sigh*
looks like I'm going to have to figure out safestrap on my own. whether there is another method for installation besides via apk, why it failed to install, whether safestrap is the only custom recovery that works by not touching the bootloader, why it hardbricked my phone.. etc
guess I'll post the answers somewhere intelligent like Android Authority.
have fun with your +1s
now go die in a fire. cheers
Click to expand...
Click to collapse
Honestly I answered your question. It's hard to talk about safestrap other than what I've learned about it. The other member was right, it gets tiring answering the same questions all the time and once in awhile people don't appreciate the answers they are given.
There are threads for safestrap as well as most of the options here on xda. And feel free to go to another forum, your posting questions in a dying forum for the VZW S3. There's not many people who are really that interested in the locked down version anymore. It's very sporadic as far as people and questions go. But to be rude about it just isn't needed.
It's not about post count at xda it's about helping the community. I've been around here long enough to know this. And if you feel someone isn't helpful there's something called a PM instead of calling them out here on the forums. I grow tired of people not being appreciative of anything when someone takes the time to do there best to explain something to someone else
Sent from my Nexus 5
running 4.4.2
PM sent. I might be able to help with that.