yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] jjfriede:
I was wondering if there was any hope for a future ne1 downgrade. I received my phone with kitkat and a locked bootloader and i'm hoping It won't be stuck like this forever :/ Could a similar modification be made? I read something about a "qfuse" but I don't quite understand how the hardware could enforce anti downgrade measures.
[Verizon Samsung Galaxy S III] Bright09:
think ill have to try this on my 4.3 nc1
[Verizon Samsung Galaxy S III] beer-2k:
good luck! post your results if you tried :)
[Verizon Samsung Galaxy S III] ehis3emma:
just stumbled on this after weeks of combing the internet for a possibly breakthrough to flash custom roms.

I got this device, tho refurbished. checking through the settings and about, it states I have - GT-I9300, ANDROID 4.3, Baseband Version : I9300ZCUBMLI

And the boot loader information:

ODIN MODE

Product Name: SCH-1535

Custom Binary Download: Yes (1 counts)

current binary: custom

system status: none

Qualcomm secureboot: enable

warranty bit:1

bootloader RP swerv: 1

Would this procedure work for my device?
[Verizon Samsung Galaxy S III] Droidriven:
If you have 4.3 with locked bootloader then you're stuck with locked bootloader, this method doesn't bypass the locked bootloader, this let's you downgrade to 4.1.2 without the bootloader bricking the device.

What the OP did was take the 4.3 locked bootloader and used it to replace the 4.1.2 bootloader. Its 4.1.2 but it has the same locked bootloader that 4.3 has so no you're still not going to be able to use custom ROMs.

You may as well give up on wanting custom ROMs because its probably never going to happen unless some super hacker genius cracks Samsung's security protocols and figures out how to unlock the bootloader, and even then it might not work because there are also hardware features involved in securing the device so it can't be flashed, even if we find a way around the bootloader we still won't pass security checks and signatures which then would probably trigger Knox and then when it hits qfuse it'll activate qfuse and fry the motherboard which renders the device thoroughly dead forever.

Samsung invested a tremendous amount into preventing anyone from tampering with the device.

If you have the locked bootloader then you're stuck with having to use Safestrap Recovery and modified stock ROMs.
[Verizon Samsung Galaxy S III] Droidriven:
On second thought, on further examination of the OP I saw some details I didnt notice before. It was my understanding that 4.3 locked bootloader and newer are locked forever but it seems this method is possible on the firmware build you have(I seriously doubt it though), try it and see if it works for you.
[Verizon Samsung Galaxy S III] maddstealth:
I hope this isn't a stupid question, but will this process work for a Verizon SIII I535 with Android 4.42 installed?
[Verizon Samsung Galaxy S III] Droidriven:
Hope all you want, the question was still a waste of your time.

Title CLEARLY states "Downgrade 4.3 to 4.1.2".

Do you have 4.3? Nope, enough said.
[Verizon Samsung Galaxy S III] maddstealth:
Fine. Another question. Is there a way to downgrade from 4.4.2 to 4.3 or earlier?
[Verizon Samsung Galaxy S III] Droidriven:
No, 4.3 and up has a locked bootloader, none of them can be downgraded. You can only flash the same as what you have or upgrade to newer, you can never go back. The only ones that can downgrade are those with older than 4.3.

It sucks but there is no way around it.

Your only options are:

1) update to a newer stock official firmware.

2)root and use Safestrap Recovery with modified stock ROMs(not as good as custom ROMs but there are heavily customized stock ROMs to use in Safestrap).
[Verizon Samsung Galaxy S III] maddstealth:
I just rolled back from using Safestrap. A great alternative to straight-up Touch-Wiz, I admit, but the due to basically having two copies of the OS installed, I only had about 1GB of free space to work with, and that ended up being to restrictiv. It's funny. I used to have a Samsung GS3 that still could, and did, have Cyanogen installed on it, but I was unfortunate enough to have it get slowly destroyed by water damage. Even more unfortunate to have my replacement phone ship with the 4.4.2 update cued up. And naturally, I didn't know about the bootloader lockdown prior to accepting that update - I usually automatically accept updates for security reasons... <_<

God I miss Cyogenmod-enabled SGIIIs... Almost as good as using a Nexus phone, especially with the battery life...

Does any of the updates make any modifications to the bootloader lockdown whatsit that allows us to work around it...?
[Verizon Samsung Galaxy S III] Droidriven:
No getting around the locked bootloader until some super genius hacks it and that's only IF that actually works. I honestly don't see it happening ever.
[Verizon Samsung Galaxy S III] maddstealth:
Ugh... I kinda figured as much. So much for hoping. lol

Thanks for the info. :)
[Verizon Samsung Galaxy S III] Droidriven:
I know what you mean.

There is one option, find a cheap VZW S3 that hasnt been updated to a firmware with locked bootloader on eBay with good ESN and motherboard, everything else can be broken as long as the motherboard is good, then switch boards

Or just buy a motherboard by itself as long as it hasn't been updated to 4.3 or higher.

Then you can use CM and AOSP
[Verizon Samsung Galaxy S III] ElevenSide:
#ask

what if this method can be used to lower the version 4.4.2 to version 4.1.2?
[Verizon Samsung Galaxy S III] Droidriven:
Only one way to find out, try it.

Ink'd from my KrAkEn'd S3
[Verizon Samsung Galaxy S III] ShapesBlue:
Please please please do not try to go back to 4.1.2 if your on 4.4.2 you will brick the device. If you've taken the OTA to 4.4.2 going back isn't possible, there is one solution which is a jtag but that's the only viable option

Sent from my Nexus 6
[Verizon Samsung Galaxy S III] Droidriven:
I was trying to find it but I can't, I believe I saw a post another thread with a link to the 4.3 to 4.1.2 downgrade and a link to a 4.4.2 to 4.1.2 downgrade, can't remember the thread I saw it in though.

Ink'd from my KrAkEn'd S3
[Verizon Samsung Galaxy S III] ShapesBlue:
Not if your on a locked bootloader. A downgrade isn't possible, it's been going around for a long time. It isn't possible without a jtag

Sent from my Nexus 6
[Verizon Samsung Galaxy S III] Droidriven:
Yeah, I know exactly what you're talking about. I was also certain it wasn't possible after 4.3 until this thread came along and then I saw the other link to 4.4.2-4.1.2 so it puts me in a doubtful mind about it now.

Ink'd from my KrAkEn'd S3
[Verizon Samsung Galaxy S III] ElevenSide:
jtag? How to? and how do I use os lollipop or a marshmallow? (Custom Rom)
[Verizon Samsung Galaxy S III] Droidriven:
I found that other thread with the downgrade

http://xdaforums.com/galaxy-s3-verizon/help/4-4-2-downgrade-to-4-1-2-t2819270

I'm wondering what exactly these threads make possible and what they don't, this thread I just linked seems to be done on a device that had locked bootloader but was able to unlock after doing the downgrade.

Ink'd from my KrAkEn'd S3

---------- Post added at 03:18 PM ---------- Previous post was at 03:15 PM ----------

JTAG is a device that is used to unbrick a damaged device, doesn't always work though. It requires disassembling the device and connecting/soldering directly to the motherboard/CPU to repair the device.

Ink'd from my KrAkEn'd S3
[Verizon Samsung Galaxy S III] ShapesBlue:
Ah I remember that thread, I commented several times in it in fact. And yea there is no sure fire way of utilizing the jtag service anyways

Sent from my Nexus 6
[Verizon Samsung Galaxy S III] ElevenSide:
what "open padlock" it? whether that means unlock the bootloader?
[Verizon Samsung Galaxy S III] Droidriven:
What?

Its for repairing a bricked device. How it was bricked or whether it has an unlocked bootloader doesn't have a lot to do with it, a JTAG can be used on a device that has never had a locked bootloader. JTAG is just a tool that can be used to repair a bricked device, that is about all there is to it.

? Ink'd from my KrAkEn'd S3 ?
[Verizon Samsung Galaxy S III] alaneddy:
Stock 4.0.4 or 4.1.2

I have my "just retired" sch-I535 running 4.1.2. I have backups of 4.0.4 ICS as well. Dont know if they will or can help anyone, but am willing to share any files from my phone. I never took ANY updates after I bought it new on 4.0.4. I am running Wicked Sensations 5.0 (JB 4.1.2) at the moment.

edit: Ive also got insecure boot images for ALG1, BLK3,BMB1
[Verizon Samsung Galaxy S III] ShapesBlue:
Wicked sensations was without a doubt the best custom rom there ever was for the VZW S3 :cool:

Sent from my Nexus 6
[Verizon Samsung Galaxy S III] alaneddy:
I found it by accident when I had my sph-l710 sprint s3. Absolutely loved it. Was thrilled when it came out for the verizon s3. I even asked around if it could be ported to the s5, but I hit a dead end with it. Im sure I could edit the build.prop and change some things just to get the interface similar, but I'm no ROM builder, more like a ROM hacker :)

sorry off topic
[Verizon Samsung Galaxy S III] ElevenSide:
no, no, no,,,

I mean, what does it mean (open padlock)? My device is on and normal. I now use safestrap recovery and install Superlite rom.
[Verizon Samsung Galaxy S III] Droidriven:
Oh, I don't have a Verizon device, I've never used Safestrap.

? Ink'd from my KrAkEn'd S3 ?
[Verizon Samsung Galaxy S III] ofo978:
I can't open my s3 Verizon I don't really know what happened, but can I just install 4.1.2 with Odin ?
[Verizon Samsung Galaxy S III] Droidriven:
Not if you had 4.3 or newer stock firmware before the issue started. Otherwise you'll have to flash exactly what you had or newer firmware only, can't flash anything older than what you had because of the locked bootloader. And if you flash something newer, you can't go back to before it either.
[Verizon Samsung Galaxy S III] ofo978:
Ohhh OK but do you know how can I install a custom ROM for 4.4.2?
[Verizon Samsung Galaxy S III] Droidriven:
Safestrap Recovery and modified stock ROMs and Xposed are your only options for customizing your device, unfortunately.

You won't be able to use CWM/TWRP or CM/AOSP based ROMs, locked bootloader won't allow them to flash, it only bricks the device and then has to be restored. There is no getting around that, you just can't use custom recovery and custom ROMs like most other devices.
[Verizon Samsung Galaxy S III] LightC:
MOD EDIT: Removed OP quote.

__________

are you sure this fully unlocks the bootloader? can you flash a new modem without worrying about getting a bricked device?

I was able to get back to 4.1.2 and flash the insecure bootloader but does that mean I can run AOSP/CM roms on my S3? I still see ML1 under baseband in the modified 4.1.2 rom I flashed through this process. I tried flashing a marshmallow rom in recovery and it just boot looped. It seems I need a different modem to run these roms but I'm worried if I flash one of those that will brick my device.

---------- Post added at 12:54 AM ---------- Previous post was at 12:51 AM ----------

can you clarify which ROMs you are able to run now that you're back on 4.1.2? I was able to complete this process and flash the insecure bootloader but I have my doubts whether I will be able to run AOSP/CM roms on this device. I tried a Marshmallow rom and wicked sensations, both gave me boot loops. I had to odin back to the modified 4.1.2 and re-do the steps for root, flashing the insecure bootloader and installing TWRP recovery
[Verizon Samsung Galaxy S III] LightC:
I'm pretty sure this doesn't work. After following this guide to downgrade to 4.1.2, root, and flashing the insecure boot loader, I tried flashing the MF1 firmware / NE1 Modem that is recommended for CM roms.

This resulted in a hard brick with no power / sign of life on my device. I was luckily able to debrick using the microsd debrick.img card method.

Can you confirm which roms you've been able to get working after flashing the insecure aboot?
[Verizon Samsung Galaxy S III] Droidriven:
In my experience, these "downgrade" methods don't work(there's another thread here for downgrading Verizon S3). There was another guy earlier in this thread that tried this downgrade and then flashing custom and hardbricked his phone and couldn't repair without sending for service. I'm pretty sure this isn't going to work, I suggest you give up on it and use Safestrap like everyone else with locked bootloader. Many things have been tried by many many very experienced people to get around the locked bootloader but none have succeeded and probably never will. Its a goose chase that will ultimately end in failure.
[Verizon Samsung Galaxy S III] ShapesBlue:
Very true. Casual works however. I used it way back when and it worked just fine. I've noticed in that thread people seem to be having issues as well. I think only because they aren't following instructions

Sent from my Nexus 6
[Verizon Samsung Galaxy S III] Droidriven:
Casual only works with 4.1.2 and not the 4.3 update I believe. Though I remember mention of the first 4.3 build not having locked bootloader and Casual may have worked on it but then there was another 4.3 update after that and all updates had locked bootloader from there on.
[Verizon Samsung Galaxy S III] ShapesBlue:
Right yea I got my S3 with 4.1.2 on it so I did remember that. I knew better even by then not to agree to any VZW updates

Sent from my Nexus 6
[Verizon Samsung Galaxy S III] Droidriven:
Yep, Big Red don't like playing fair.
[Verizon Samsung Galaxy S III] ryanallaire:
JTAG or bust...
[Verizon Samsung Galaxy S III] LightC:
the interesting thing is that after downgrading to 4.1.2 using the procedure in this thread, I was able to root, install TWRP and flash the insecure aboot even though I was originally running 4.3 ML1.

I'm not sure what the insecure aboot does because it seems like my bootloader may still be locked -- it's not entirely clear. I can flash non-safestrap roms now but all the ones I've tried do not play well with the ML1 firmware/modem. I don't think I can flash another firmware/modem without bricking my phone, even though I was able to successfully root, install TWRP, and flash the insecure aboot all with the casual tool.

Are there any AOSP roms that play well with ML1 firmware/modem? It may be worth trying to see if I can flash one of those. I'm able to flash CM/AOSP roms just fine with TWRP but the roms fail to completely boot into android. I get constant reboots. I've tried AICP and Wicked Sensations.
[Verizon Samsung Galaxy S III] ShapesBlue:
Amen to that. Which is the exact reason I went unlocked devices and dumped them for good

Sent from my Nexus 6
[Verizon Samsung Galaxy S III] berezker:
Guys

I've sold the S3 so I totally forgot everything about it

Sorry if I couldn't be of any help
[Verizon Samsung Galaxy S III] Droidriven:
I think ML1 might be the first 4.3 build which had locked bootloader that could be unlocked but the following updates have a locked bootloader that can't be jacked with. I believe you might could have unlocked the bootloader on the ML1 firmware without doing this downgrade. I haven't researched that though so don't quote me. You can try other modems by themselves, have you tried the modem from the ML1 build? After the "downgrade" did it leave you with the ML1 modem or the 4.1.2 modem? If you can convert them to flashable zip you can flash modem in recovery. Or you can try the modem in .tar for Odin. Everyone using CM/AOSP on Verizon S3 is flashing a modem to use them, have you tried that modem by itself?
[Verizon Samsung Galaxy S III] LightC:
Tried that and bricked my phone again. This time it was a bit different though and I can't debrick using the debrick.img method!

Here is what I did:

- Downgraded to 4.1.2 using this method (I was on 4.3 ML1 previously)

- Rooted, flashed insecure aboot, installed the latest version of TWRP

- Flashed the NE1 modem only using TWRP resulting in triangle error

- Flashed the ML1 modem only using TWRP which still resulted in the triangle error

Both modem flashes resulted in the triangle at bootup where it says that Verizon detected unauthorized software.

I was still able to get into download mode at this point so I thought I would ODIN flash the original ML1 firmware and start the process all over again.

When I did this and ODIN rebooted the phone, I was hard bricked!

All three debrick images do not get my phone to boot this time. Previously, I was able to use the debrick.img for 4.3. I've tried a number of burns of the SD card but have had no luck.

I guess I have to say goodbye to this S3 unless anyone has any ideas!
[Verizon Samsung Galaxy S III] Droidriven:
Yep, as I thought, that's what the guy that tried this earlier in the thread got, the exact same results, you'll need to send it for JTAG service or replace the motherboard. Looks like this downgrade method doesn't work and its just fooling people into thinking it will work to flash ROMs. It seems to actually downgrade since you can flash TWRP but the modem required to use the ROMs is causing a brick. I'll make a report and have this thread closed or have a note added that this only works to downgrade but does not allow flashing custom ROMs.
[Verizon Samsung Galaxy S III] Droidriven:
There was a place called MobileTechVideos .com that would unbrick and unlock the bootloader, I don't know if they still offer the service though.
[Verizon Samsung Galaxy S III] the Doctor:
I'm closing this thread as the method described in the OP seems to be bricking devices and the OP has sold his S3 and can no longer support it.

THREAD CLOSED
[RAZR HD Q&A, Help & Troubleshooting] DevoutDevelopment:
Hello everyone,

I was lent a Droid RAZR HD from a friend of mine to borrow while my S6 edge is being repaired. I would like to use this phone on T-Mobile, is there anything special that needs to be done for it to work? Is it possible to use this phone on the T-Mobile network? It was originally purchased from, and last activated on Verizon.

Please let me know if you would need any more information.

Thank you,

Michael
[Sony Xperia Z Ultra] sw6lee:
Hi guys,

Im on .242 android 5.0.2 stock rooted with xposed. I already have Lollipop Memory Leak Fix installed and it seems to help in making the phone not lag, but launchers still redraw often. I tried Nova and also Xperia home and both redraws a lot. I know that Nova has agreesive desktop mode but it doesn't help much. Sometimes it seems to keep it from killed but the home button still has long delay when the launcher wants to redraw.

Do you guys also have this issue? I thought memory leak fix would fix launcher redraw as well. Any help would be appreciated.
[Sony Xperia Z Ultra] teddy74eva:
Sorry to disappoint you, but you can uninstall the fixer app because Sony has fixed the leak in their firmwares. Sony apps and services, as well as some Google ones are big RAM hoggers, you can disable some of them.

Regards
[Sony Xperia Z Ultra] sw6lee:
Thanks for reply! Are you sure Sony fixed it? I was having major lag issues and sometime random reboots. Right after reboot, it was fine, then after a few hours, the phone started lagging. After installing the fixer, it doesn't lag at all now, and it's pretty consistent. But the only thing is, the launcher keeps redrawing. Pretty often.
[Sony Xperia Z Ultra] teddy74eva:
Yup, 100% sure, there is a thread in Cross-dev section where [MENTION=1879618]IaguCool[/MENTION] compared some smali files and it turned out that Sony has fixed it.

Regards
[Sony Xperia Z Ultra] martin132014:
Apparently what sony did is just implemented that fix you just installed. So you doesn't have to Install it again, it's pointless...it doesn't fix the ram and redraw issues...it happen to every lollipop rom not just sony. I think the fix will be in 5.1....if your in 5.0, chances are you have to wait for the real fix...
[Sony Xperia Z Ultra] sw6lee:
So I don't understand. If its already fixed, why is my launchers keep redrawing?? Its driving me crazy ? if I reboot, no redraw for about 10 hours maybe, then redraw starts again, when exiting every few apps.

Could anyone please let me know how to stop launcher redraw?
[Sony Xperia Z Ultra] fastest83:
Have you performed a hard reset before or after the lollipop update?

I followed the same advice after experiencing the same issues, I unlocked the bootloader so that it automatically did a hard reset deleting everything on internal memory, and it's been a new phone altogether.

Redraws sometimes happen with Chrome or apps that demand huge ram, but like 1/20th of the times.

No random reboots so far, it seems the right solution.

Just backup everything on the external memory and go back to factory settings.

You'll notice the difference right away. ;)
[One (M7) Q&A, Help & Troubleshooting] eramik:
A while ago I bought a M7 second hand, and the phone worked nicely while my m8 was being repaired. When the m8 returned I left the M7 unused for some months. Earlier this week I once again needed the M7 as a backup phone. I updated with Lollipop. But quite shortly after the phone started to reboot and couldn't find network/ recognize SIM. As thought I would be warranty left I tried to look up IMEI and didn't find any.

After briefly searching the net it seems like all other phones with this issue have been rooted. As long as I've owned the phone I haven't rooted the phone, but the previous owner might have done it. So I wonder if the imei could have been wiped if the phone never have been rooted. If that's unlikely the previous owner probaly have rooted the phone and that would surely void the warranty.

Where do I start to fix the phone, there seem to be a fix for the issue.

Unrooted using latest stock Android 5.0.2 and Sense 6.0.
[One (M7) Q&A, Help & Troubleshooting] alray:
Restore the phone back to stock using the ruu that match your version, if not solved by this then its probably an hardware fault.
[One (M7) Q&A, Help & Troubleshooting] eramik:
Thanks, I've been searching.

And it seems like htc1guru's guide to return to stock would be able to help me (can't link due to being restricted cause of to few posts).

How do I find the correct RUU, I've not been able to find out?

A couple of other questions.

Currently the phone is UNROOTED, I'm I able to check if has been rooted previously and have S-Off?
[One (M7) Q&A, Help & Troubleshooting] alray:
Post the output of "fastboot getvar all" so we can know the relevant info about your phone. Remove imei and s/n before posting
[One (M7) Q&A, Help & Troubleshooting] eramik:
Took some time, but here we go.
[One (M7) Q&A, Help & Troubleshooting] eramik:
Soemthing strange happend doing the fastboot thing.

After I've finished, the phone asked for a SIM card. And the IMEI restored. But overnight the phone restarted and IMEI disappeared once again.
[One (M7) Q&A, Help & Troubleshooting] alray:
It might be a defective sim card or sim tray, check with your operator for a new sim card.
[One (M7) Q&A, Help & Troubleshooting] eramik:
Definitivly not SIM card related. I've crosschecked SIM card in another phone. I doubt it's the SIM tray, as the problem is only active when the IMEI number falls out. I think I'll try to restore back to stock. Are you able to identify the correct RUU?

Do I need to root the phone to install a clean stock?
[One (M7) Q&A, Help & Troubleshooting] alray:
Yep you'll need the 7.19.401.22 ruu.zip and you are lucky because I uploaded it earlier this week, it was not available anywhere before ;)

As your phone is S-ON make sure to relock your bootloader before flashing the ruu (if not already locked or re-locked):

fastboot oem lock

then using htc_fastboot.exe (normal fastboot.exe from the android sdk won't flash new 7.xx.xxx.x RUUs):

htc_fastboot oem rebootRUU
htc_fastboot flash zip ruu.zip
htc_fastboot reboot
[One (M7) Q&A, Help & Troubleshooting] eramik:
Thanks, I'm finished flashing. During the process there was a line which said failed. Don't know which as the fastboot command window don't have the full history. In the end it says OKAY, and the phone reboots. It currently setting up. Should I be worried.

Btw if this works I'll buy you a beer :good:

EDIT: it looks like IMEI still is missing :(