Related
OK so I followed a youtube video tutorial on rooting,and I think it's the boot.img that messed everything up. It would boot up before but it was stuck on the Google screen, the OS didn't load. So I found a GRH78 or something Nandroid backup and ran that, but the capacative buttons don't work, the screen isn't calibrated correctly and the phone radio isn't correct either. Then I remembered my Nexus S was the newer GT-I9023 GRI54 and I need a GRI54 NANDROID stock backup (which I can't seem to find!)
Guys, what do you suggest I do at this point? I can't revert to stock (I've been trying)
I just got this Nexus S and have been spending hours trying to restore firmwares, finding it online, but now I know I need the GRI54 Android 2.3.3 backup, and if anyone has that I'd be super happy
I really need help
you most likely need the 9023 method of rooting
see the stickied guides
I fixed it. I downloaded a GT-I9023 GRI45 firmware file off of somewhere here (<3 xda forums) it wasn't a nandroid backup, but I used the clockworkmod to install it and surprisingly, it booted up again. (of course, I had the crappy 2.1 installed before so maybe this acted as an 'update' and fixed all the problems, but anyways it works smooth now as it did before )
I knew I could figure it out.
Not to be an ass, but I think there's a lot of difference between bricking a phone and being unable to boot. You've never bricked your phone, since you could still switch ROMs by using the Recovery.
This is a misleading title. Bricking is when you just can't enter not even the bootloader/Recovery.
you are 100% right
unfortunately many people keep getting those 2 terms confused, and use it inappropriately
every body needs to chip in and help newbies learn the correct terminology.
thank you
boolean22 said:
Not to be an ass, but I think there's a lot of difference between bricking a phone and being unable to boot. You've never bricked your phone, since you could still switch ROMs by using the Recovery.
This is a misleading title. Bricking is when you just can't enter not even the bootloader/Recovery.
Click to expand...
Click to collapse
Looks like I've managed to act and look like a fool...
I tried to root my Nexus S with Superboot, unaware that it was version-specific (I should have known that ). To make a long story short, I tried to root my phone with Superboot which is written for android 2.3.3, while I'm running 2.3.4.
The phone can get to fastboot/recovery, but won't boot. I googled to find how revert to a stock 2.3.3 or 2.3.4, but somehow did not find what I was looking for.
Phone was vanilla, I hadn't installed anything specific on it besides twitter, FB, etc.
From a powered-off phone, how would I manage to revert to a clean phone ?
Thanks for your help, people.
-- Jeff
<EDIT:
All the solutions I've seen required CWM or similar, and a rooted phone. Since my problems started because I wanted to root my NS, I figured that I was out of luck for a while, and a non-working phone was out of question.
I went at my retailer and managed to get a new phone free of charge I *****-footed around the fact I was installing an unsupported (by the carrier) update/app, the clerk wasn't very familiar with the NS so it went well with them and they gave me a new phone
/EDIT>
I feel monumentally stupid asking this question, but I've run out of options. I have tried searching first, but I'm having trouble figuring out how to phrase the search and most of the search results are for non-Atrix 2 phones, so I don't know how reliable the information is.
My previous phone was an HTC Evo which was fully rootable and unlockable etc., and an HTC Evo 3d which was fully rootable and unlockable at the time I managed to do it (apparently the 3d goes through phases where it is, then phases where it isn't, depending on its updates). My basic and non-technical understanding of the Atrix 2 environment is that becauase the bootloader is currently locked, the backup/restore/flashing solutions have to perform a few tricks to work.
So from what I can tell in the dev forum, there are currently two ways to backup and flash roms. There is safestrap, which apparently isn't quite working yet, which partitions your microSD card and runs everything from there -- essentially when you boot your phone it tells the OS to boot from the microSD card which effectively lets you treat your Atrix 2 as a fully unlocked and rooted device with a remarkably large and well-configured recovery partition. Unfortunately, according to the title of the safestrap thread, it's not quite working yet, and a few of the roms posted in the development forum specifically say not to use it.
OK, so bootstrap. It was updated as of Jan 1. If you have already rooted your Atrix 2 (I have) then it throws up a menu that lets you boot into recovery, and it will install (I think this is my understanding) a custom version of ClockwordMod Recovery? But you can't get there from boot, you have to boot into Android and then reboot back into the recovery environment.
Is that correct?
If that is correct, then my next question is what happens in the hypothetical scenario where you install a rom, something goes wrong, and you want to restore a previous backup but you can't boot into Android?
There's something I'm missing about how all this is supposed to work and it looks like it's something so obvious that nobody actually talks about it in the threads -- or when they're talking about it, I don't actually realize that's what they're talking about so it doesn't register.
Anyway. Thanks for your time.
There's a script in the thread that gives you cwm on boot. The catch is it goes to recovery first EVERYTIME you boot.
ubersoft said:
I feel monumentally stupid asking this question, but I've run out of options. I have tried searching first, but I'm having trouble figuring out how to phrase the search and most of the search results are for non-Atrix 2 phones, so I don't know how reliable the information is.
My previous phone was an HTC Evo which was fully rootable and unlockable etc., and an HTC Evo 3d which was fully rootable and unlockable at the time I managed to do it (apparently the 3d goes through phases where it is, then phases where it isn't, depending on its updates). My basic and non-technical understanding of the Atrix 2 environment is that becauase the bootloader is currently locked, the backup/restore/flashing solutions have to perform a few tricks to work.
So from what I can tell in the dev forum, there are currently two ways to backup and flash roms. There is safestrap, which apparently isn't quite working yet, which partitions your microSD card and runs everything from there -- essentially when you boot your phone it tells the OS to boot from the microSD card which effectively lets you treat your Atrix 2 as a fully unlocked and rooted device with a remarkably large and well-configured recovery partition. Unfortunately, according to the title of the safestrap thread, it's not quite working yet, and a few of the roms posted in the development forum specifically say not to use it.
OK, so bootstrap. It was updated as of Jan 1. If you have already rooted your Atrix 2 (I have) then it throws up a menu that lets you boot into recovery, and it will install (I think this is my understanding) a custom version of ClockwordMod Recovery? But you can't get there from boot, you have to boot into Android and then reboot back into the recovery environment.
Is that correct?
If that is correct, then my next question is what happens in the hypothetical scenario where you install a rom, something goes wrong, and you want to restore a previous backup but you can't boot into Android?
There's something I'm missing about how all this is supposed to work and it looks like it's something so obvious that nobody actually talks about it in the threads -- or when they're talking about it, I don't actually realize that's what they're talking about so it doesn't register.
Anyway. Thanks for your time.
Click to expand...
Click to collapse
In the situation that you describe, even the CWM on boot that mtnlion mentioned, still may not get you into CWM. In that case your ONLY option is to flash the fxz file with rsd lite, that will restore you to a full stock out of the box atrix 2, which you then have to re-root, then re-install bootstrap, then restore your backup.
Sorry there is not an easier way right now, but until the bootloader is unlocked we can't flash CWM, so that we can get to it, as you would the default android recovery, because that does require the default recovery to be replaced, and an unlocked bootloader is required for that to work.
Safestrap is really a tool that is only useful to those actually developing, or people that we have asked to test something out, and since lfaber06 and I don't have a version to release to the public that we are happy with yet, that is not an option.
Oh!
So you install bootstrap, then you install the script, and when you do that it basically acts like a grub menu? That makes sense.
ubersoft said:
Oh!
So you install bootstrap, then you install the script, and when you do that it basically acts like a grub menu? That makes sense.
Click to expand...
Click to collapse
No, if you get a bad flash you still may not be able to get into CWM, since it requires files that are actually in the Android ROM, to fully work. Read my post above ^^^
Heh. Apparently I started posting at about the same time you posted your detailed explanation...
Thanks for the additional information. Based on that, it looks like I need to wait a bit longer before mucking about with my Atrix 2. Thanks for the update!
ubersoft said:
Heh. Apparently I started posting at about the same time you posted your detailed explanation...
Thanks for the additional information. Based on that, it looks like I need to wait a bit longer before mucking about with my Atrix 2. Thanks for the update!
Click to expand...
Click to collapse
No, it is perfectly safe, but the restore is just a little more complex than you had to deal with, with other phones. I have done exactly what I mentioned above SEVERAL times, with out issue, since I am doing a ton of dev work on this phone.
The ROMs that are out there are great right now, and lfaber06s ROM is really good, and I will be releasing a version of CM7 very soon. If you wait for a bootloader unlock, it may never come, or at least it may not be very soon.
The worst thing that happens is that you have to flash the fxz, which it is documented how to do that with RSD lite very well in the noob thread here. then you can restore your backup with out issue, it is just a few extra steps.
Bootstrap is really safe as is all of lfaber06 Roms right now. I have no problem recommending either of his roms to anyone. They are both very good. As Jim has stated the only problems we have is if something wrong happens on boot, but with the fastboot files, RSD lite, and the one click root method you have everything available to get you right back to where you were before you flashed.
I can promise you everything works very good as I have soft bricked my phone so many rimes in the last 2 weeks that I have become very efficient at getting back to stock, rooting and then flashing a backup with bootstrap and can be back in business n around 20 mins. Just always be near a computer when you start flashing things. One thing that will help out is to keep a backup of the bootstrap on tour SD card so if you have something go wrong you don't have to redownload it again.
We have a very good group of people here and if anyone has any problems we can get you through them and back running
Well there we are then!
So after getting a clearer picture of the situation (thanks for the explanation) I blocked off most of the night, installed bootstrap, then installed lfaber06's Supercharged v4. It took forever, but it worked flawlessly.
Thanks everyone for your patience and encouragement.
Hey fellas, I got my Verizon GS3 last Thursday knowing that it had a locked bootloader but was hoping someone would figure out how to get root. Now I see that it has been rooted but is it "completely" rooted? What I mean is, can I overclock it, flash kernals, custom roms, wifi tether? Does it have the same capabilities of all three of the other US carriers' GS3s? Is Cyanogenmod developing CM9 for it yet? I was reading somewhere that you can root it just like any other version but it's just a bigger pain in the ass. I just want to make sure that my Verizon GS3 can be completely rooted so I can do everything I did with my old Droid. Should I just take it back and go with the Sprint version of the GS3? Im sorry if some of these are "noob" questions but I just want to figure out what I should do. Any help would be much appreciated!
Rooting and the other things you spoke of are not the same thing.
Rooting = The ability to write to the system partition, while booted into android. This allows you to delete system files (such as bloatware).
Locked Boot Loader = You will not be able to flash custom files (unsigned) to the phone from Odin. This means no clockwork recovery, roms, kernels ect....
There are ways around some of the locked boot loader stuff on some phones (ex. droid 2 got a special recovery through months of dev work. This did not cicrumvent the locked boot loader, but allowed away around it). This type of recovery (2nd init) is not avalible for Samsung phones.
If you want roms and all access, I would go with the dev unit samsung is selling for verizon. However, there still may not be much for the VZW gs3 because they wont sell tons of the dev units at $600 a pop.
The Verizon S3 already has root, roms and kernels up and working and some really good devs trying to crack it. I have a VG3 and it was rooted in less than a day and I'm having no issues. It's a great phone but the locked bootloader may cause issue in the future.
If I knew that samsung was going to release a dev version I may not have pre-ordered my S3 but I"m still happy with my purchase so far. What I find amusing is the price stated on the dev phone right now is cheaper than buying the phone outright from big V right now. We will see what the price really is when the phone is made available.
Farabomb said:
The Verizon S3 already has root, roms and kernels up and working and some really good devs trying to crack it. I have a VG3 and it was rooted in less than a day and I'm having no issues. It's a great phone but the locked bootloader may cause issue in the future.
If I knew that samsung was going to release a dev version I may not have pre-ordered my S3 but I"m still happy with my purchase so far. What I find amusing is the price stated on the dev phone right now is cheaper than buying the phone outright from big V right now. We will see what the price really is when the phone is made available.
Click to expand...
Click to collapse
I second this post!
locked bootloader means no custom roms or kernels.
chakra said:
locked bootloader means no custom roms or kernels.
Click to expand...
Click to collapse
Not true.
Touchwiz based custom roms are entirely possible and it has already been shown custom kernels work using kexec. Yeah it's not as good as an unlocked bootloader but we have our work arounds until these crazy smart devs figure out how to bypass the locked bootloader.
Sent from my SGS3
tanman21 said:
Rooting and the other things you spoke of are not the same thing.
Rooting = The ability to write to the system partition, while booted into android. This allows you to delete system files (such as bloatware).
Locked Boot Loader = You will not be able to flash custom files (unsigned) to the phone from Odin. This means no clockwork recovery, roms, kernels ect....
There are ways around some of the locked boot loader stuff on some phones (ex. droid 2 got a special recovery through months of dev work. This did not cicrumvent the locked boot loader, but allowed away around it). This type of recovery (2nd init) is not avalible for Samsung phones.
If you want roms and all access, I would go with the dev unit samsung is selling for verizon. However, there still may not be much for the VZW gs3 because they wont sell tons of the dev units at $600 a pop.
Click to expand...
Click to collapse
Thanks for the reply man! The dev phone just may be an option but I really don't feel like forking over $600 when I can go to Sprint on a cheaper plan and have an unlocked bootloader....either way, I have 10 more days to return my phone and cancel my contract if I need to. And btw, I sent a long email to Verizon asking them if they will ever unlock the bootloader ( I read an article saying they may, then today read a article saying they wont. We'll see.) I also said that I may just cancel my contract and go to Sprint and ask them how they can "help" relieve this situation that alot of people are facing. I'll report back and let everyone know what their response is.
Topdroid01 said:
Hey fellas, I got my Verizon GS3 last Thursday knowing that it had a locked bootloader but was hoping someone would figure out how to get root. Now I see that it has been rooted but is it "completely" rooted? What I mean is, can I overclock it, flash kernals, custom roms, wifi tether? Does it have the same capabilities of all three of the other US carriers' GS3s? Is Cyanogenmod developing CM9 for it yet? I was reading somewhere that you can root it just like any other version but it's just a bigger pain in the ass. I just want to make sure that my Verizon GS3 can be completely rooted so I can do everything I did with my old Droid. Should I just take it back and go with the Sprint version of the GS3? Im sorry if some of these are "noob" questions but I just want to figure out what I should do. Any help would be much appreciated!
Click to expand...
Click to collapse
There's some erroneous replies so far, hopefully this will clear it up for you. Root or superuser, is a linux term, which basically provides you with admin rights. With root alone you can run WiFi tether, rename system apps, etc. Root is easily attainable on the Verizon S3, see the dev section for guides.
The S3 recovery partition is NOT signed. This allows us to install custom recoveries (i.e. ClockworkMod, TWRP, etc.) This is very different from say, a Moto phone that had to use bootstrap methods. The S3 can have a fully functioning recovery that will allow you to do backups, flash ROMs and Kernels, etc. Again, very easy to do, see dev section for guides (it's grouped with root).
What's currently being worked on is the "locked" bootloader. Basically we can write whatever we want to the various partitions, however, there is a security check being done that prevents altering various areas, like the boot.img. Right now there is a workaround where custom Kernels are flashed via the recovery partition (see recovery/kexec threads for more info).
There is no official CM9 or CM10 builds yet, but they are being worked on and there are bootable versions of both. Right now the RIL is the bigger issue as it's preventing data but that has nothing to do with the bootloader. The RIL is being worked on, no ETA.
tl;dr - The bootloader is still "locked" but there are already various workaround methods in place to allow for the flashing of custom recoveries, ROMs, Kernels, etc. Reading the guides in the dev section would be a great place to start understanding what's going on better.
s197 said:
There's some erroneous replies so far, hopefully this will clear it up for you. Root or superuser, is a linux term, which basically provides you with admin rights. With root alone you can run WiFi tether, rename system apps, etc. Root is easily attainable on the Verizon S3, see the dev section for guides.
The S3 recovery partition is NOT signed. This allows us to install custom recoveries (i.e. ClockworkMod, TWRP, etc.) This is very different from say, a Moto phone that had to use bootstrap methods. The S3 can have a fully functioning recovery that will allow you to do backups, flash ROMs and Kernels, etc. Again, very easy to do, see dev section for guides (it's grouped with root).
What's currently being worked on is the "locked" bootloader. Basically we can write whatever we want to the various partitions, however, there is a security check being done that prevents altering various areas, like the boot.img. Right now there is a workaround where custom Kernels are flashed via the recovery partition (see recovery/kexec threads for more info).
There is no official CM9 or CM10 builds yet, but they are being worked on and there are bootable versions of both. Right now the RIL is the bigger issue as it's preventing data but that has nothing to do with the bootloader. The RIL is being worked on, no ETA.
tl;dr - The bootloader is still "locked" but there are already various workaround methods in place to allow for the flashing of custom recoveries, ROMs, Kernels, etc. Reading the guides in the dev section would be a great place to start understanding what's going on better.
Click to expand...
Click to collapse
This explains things alot better for me Thank you!!!. Im coming from a OG Droid that I rooted as soon as I got it so its been a while since I've been on the scene. I've kept up with the OG Droid Development for quite some time (which is basically nonexistent) so Im somewhat familiar with rooting and such just not familiar with this lock bootloader and such on my S3. Anyways, I still may just go to Sprint but havent made my mind up yet. And THANKS again for the very knowledgeable answer!
Hello XDA Developers,
Okay so here is my unusual situation...
I have two phones. I have one Verizon (d2vzw) SGS3 that I run CM 11 on with CWM Touch installed on that phone. On my second phone which is also a Verizon (d2vzw) SGS3 i was running stock 4.1.2 ROM which was rooted with CWM recovery manager. The stock SGS3 was the baseband version that supported multi windows.
Okay so today i decided to go ahead and check for an OTA update on my stock (rooted) SGS3. I knew there had been an update available for some time but I never decided to update my phone because i figured with it being rooted and with CWM recovery manager installed there was no way that the OTA update would work...
So like an idiot i went ahead and tried the update. I figured what is the worst that could happen? I figured that at the worst it was just going to tell me that the update failed and i would just be stuck with Android 4.1.2 which isn't the end of the world. I really like the multi windows setup. Moving on...i downloaded the update and I hit the install update button. My phone booted into recovery manager and it installed the update. When the phone rebooted I saw the message "Android is upgrading" and i thought whoa! no way!. After android finished upgrading which i believe was the dalvik rebuilding I saw a message in notifications saying "upgrade installation failed", however when i went into settings it now told me that i was running Android 4.3. So to me it looked like the upgrade took but I think the problem was that when it asked me to flash the stock recovery there was an option in CWM to say no and i choose that to keep CWM recovery manager instead of the stock recovery manager. Maybe i should have let the update install the stock recovery manager...
Now i knew ahead of time that if this update worked I was going to loose root but again I didn't think it was that big of a deal since I could just re-root my phone and I would be on a newer Android version. I looked around for the best rooting option and I wanted to use Chainfire's CF-AutoRoot exploit but I know that if you do not have the bootloader unlocked that there is a chance of bricking your phone. So after some research (which i should have done before i updated my phone!) i saw that there was an exploit out called "saferoot.zip" and that you could root your phone running a windows.bat file or a shell script if you are in Linux. Even though the program is for SGS4 many users on XDA with SGS3 phones reported success with "saferoot". So i tried saferoot 2 times with no luck. Finally on the third attempt (3rd times a charm!) i was able to root my phone and SuperSU was able to "disable KNOX".
So i now had my Verizon SGS3 updated from Android 4.1.2 to Android 4.3 and I had successfully re-rooted my phone. I was feeling good...
Until I wanted to make sure that CWM Recovery Manager was still on my phone. I opened up the app "quickboot" and choose to boot into Recovery Manager this is where the trouble began...
When my phone booted into recovery mode i saw a big Yellow Triangle. Under this very scary yellow triangle it said that "Verizon has detected unauthorized software on this phone. Please turn off the phone and take it into your nearest verizon store". Other something along those lines...
I thought I was in big trouble...
I could not get the phone out of recovery mode. I tried pulling the battery but every time my phone rebooted it just kept going back into recovery mode. The trick to get out recovery mode was to hold down Volume Down + Home for a few seconds then press the power button. This brought me to a new menu and i was able to hit "cancel" on installing a new OS and it rebooted my phone back to its normal state.
So finally here is my questions...
Question 1: I know i need to unlock my bootloader again. After you apply an OTA update it re-locks your bootloader right? Does anyone know of a method of unlocking the bootloader with the Verizon (d2vzw) SGS3 baseband version I535VRUCML1 running on Android 4.3?
Before when my phone was running 4.1.2 I unlocked the bootloader with Odin and the app EZ-UNLOCK but i don't think EZ-UNLOCK is going to work with Android 4.3
Question 2: Is there a way to get rid of that message about Verizon has detected unauthorized software on this phone? Now I know that ChainFire has a Yellow Triangle Away app on the Google Play store and I will happily buy it but I know that in order for it to work you first must have your bootloader unlocked right? If i try to use that app with my bootloader in a locked state i could brick my phone permanently right?
Is there possibly any file or exploit i can flash with either Odin or the app "Flashify" so that I can unlock my bootloader. Has anyone here tried unlocking their bootloader on their SGS3 running 4.3 with the app "EZ-UNLOCK" ?
I am very concerned about damaging my phone which is a company work phone so if i mess it up i will be in deep trouble...
Oh, one last question...
Question 3: Since i got that yellow triangle message about unauthorized software when i tried to boot into recovery mode could it have possible been because CWM recovery was somehow deleted with the OTA update? After i was able to get out of recovery mode I used the app "ROM Manager" to install CWM Recovery Again hoping that I might have a recovery manager... Now ROM Manager says that CWM Touch was installed successfully but I am not sure since I am kind of scared to boot into recovery mode again until I unlock this bootloader.
If my recovery manager is being blocked until I get my bootloader unlocked could i use the app "flashify" if i need to flash any files?
I know my situation might be a bit unusual but I am really going to need some help on this and someones expertise advice.
I hope to hear from someone soon...
XDA Members, have a great New Years and make 2014 count!
I thank you all for your time and assistance.
-droidshadow
After accepting the 4.3 OTA, your bootloader is locked and there is no way to unlock it. My suggestion to you would be to grab the 4.3 ODIN file, reflash to 100% stock, root using saferoot, debloat as wanted, and hope for the best.
Probably not what you wanted to hear, but there is no way to unlock the bootloader once taking the 4.3 OTA. Attempting to do so will brick the phone.
well that stinks...
podspi said:
After accepting the 4.3 OTA, your bootloader is locked and there is no way to unlock it. My suggestion to you would be to grab the 4.3 ODIN file, reflash to 100% stock, root using saferoot, unbloat as wanted, and hope for the best.
Probably not what you wanted to hear, but there is no way to unlock the bootloader once taking the 4.3 OTA. Attempting to do so will brick the phone.
Click to expand...
Click to collapse
The only reason that I even attempted the upgrade is because next week I am going to purchasing the smart watch from the Samsung Galaxy Gear. For that watch (you can make calls from the watch) you need the upgrade to pair my SGS3 with my smartwatch when I get it next week.
Now this OTA update is quite new so that means that there still might be a chance to unlock the bootloader eventually when someone works it out right?
Big question:
Is it still possible to have CWM or TWRP with this 4.3 OTA update?
Thanks for the reply.
-droidshadow
droidshadow said:
The only reason that I even attempted the upgrade is because next week I am going to purchasing the smart watch from the Samsung Galaxy Gear. For that watch (you can make calls from the watch) you need the upgrade to pair my SGS3 with my smartwatch when I get it next week.
Now this OTA update is quite new so that means that there still might be a chance to unlock the bootloader eventually when someone works it out right?
Big question:
Is it still possible to have CWM or TWRP with this 4.3 OTA update?
Thanks for the reply.
-droidshadow
Click to expand...
Click to collapse
To bad you took the ota. There is a twrp flashable rom for stock 4.3. And no you can not have custom recovery.
droidshadow said:
Okay so today i decided to go ahead and check for an OTA update on my stock (rooted) SGS3...
Click to expand...
Click to collapse
There's no need to read any further than that.... Sorry to be another bearer of bad news, but if a phone is rooted and you want it to stay that way, "OTA" should be a term that you never, ever, ever even think about !
The S4 boot loader has been locked down with Knox longer than the S3 has, and no one has cracked it yet. I'd say the chances of this boot loader being cracked wide open are slim to none. If unlocking this boot loader were as simple as using EZ unlock 1.2, it would have been written about all over these and all forums.
Sent from the Shark Tank using XDA Premium 4 mobile app
so what entails for the future of samsung phones?
landshark68 said:
The S4 boot loader has been locked down with Knox longer than the S3 has, and no one has cracked it yet. I'd say the chances of this boot loader being cracked wide open are slim to none. If unlocking this boot loader were as simple as using EZ unlock 1.2, it would have been written about all over these and all forums.
Sent from the Shark Tank using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So what is the going to happen to the future of Samsung Phones? Are we no longer going to be able to put custom ROM's and custom Recovery Managers on Samsung Phones?
Will KitKat + SELinux + Knox no longer allow us to enjoy the true beauty of Android? I think that is major BS.
So what are our options now? Are we going to simply have to choose different phones like future Google Nexus phones? I love Samsung phones and I love having the options of flashing custom roms or reverting back to stock and I really really love CWM recovery or TWRP recovery.
These phones are our property...
I understand that the software and the code is Samsung's or Verizon's yet we should be able to do what we want to our property. Could you imagine if Toyota or Chevy said that after you purchased one of their cars you could never paint it a different color or add custom rims + wheels! That would be ridiculous... It is the same concept here really.
It is really sad that Samsung and Mobile carriers such as Verizon have resorted to this...
-droidshadow
droidshadow said:
So what is the going to happen to the future of Samsung Phones? Are we no longer going to be able to put custom ROM's and custom Recovery Managers on Samsung Phones?
Will KitKat + SELinux + Knox no longer allow us to enjoy the true beauty of Android? I think that is major BS.
So what are our options now? Are we going to simply have to choose different phones like future Google Nexus phones? I love Samsung phones and I love having the options of flashing custom roms or reverting back to stock and I really really love CWM recovery or TWRP recovery.
These phones are our property...
I understand that the software and the code is Samsung's or Verizon's yet we should be able to do what we want to our property. Could you imagine if Toyota or Chevy said that after you purchased one of their cars you could never paint it a different color or add custom rims + wheels! That would be ridiculous... It is the same concept here really.
It is really sad that Samsung and Mobile carriers such as Verizon have resorted to this...
-droidshadow
Click to expand...
Click to collapse
Difference is though, if you were to somehow screw up your car by customizing it you wouldn't try to take it back to the dealership and get a new car under a warranty claim. I would have to think at least part of the reason phone manufacturers and mobile carriers are locking down phones is all the "warranty" claims people are submitting after screwing up while rooting and flashing their phones. Warranty claims are for inherent manufacturer defects, not a hard brick from flashing the wrong software. If more people took responsibility for their mistakes and bought a new phone instead of making the carriers or manufacturers pay for their mistakes, perhaps this wouldn't be happening. I'm not saying absolutely, just perhaps. OK, I'll get off my soapbox now. Happy New Year everyone.
Different animal. You own the hardware, but the providers have the right to control the firmware since it can change how the phone interacts with the network.
Just like the firmware in your cars computer. The manufacturer and the federal government have control over what went in. Modifying it can be done, but it is a violation of EPA emission laws.
Modifying the paint, tires, rims etc is like putting a different case, bling etc on your phone
Your phone needs to have the 4.3 odin tar installed to clean the recovery.
Sent from my SCH-I535 using xda app-developers app
droidshadow said:
So what is the going to happen to the future of Samsung Phones? Are we no longer going to be able to put custom ROM's and custom Recovery Managers on Samsung Phones?
These phones are our property...
It is really sad that Samsung and Mobile carriers such as Verizon have resorted to this...
-droidshadow
Click to expand...
Click to collapse
Its really Verizon, They have had many Moto and HTC phones with locked bootloaders , unless Verizon unlocks it, it won't be cracked.
http://forum.xda-developers.com/showthread.php?t=2586319
Sent from my SCH-I535 using xda app-developers app
DigitalMD said:
Its really Verizon, They have had many Moto and HTC phones with locked bootloaders , unless Verizon unlocks it, it won't be cracked.
Click to expand...
Click to collapse
I know but still i think it should be our choice! While there are millions of us out there that love to customize the software on our phone's by adding new recovery managers or custom rom's we are a small population to the rest of the stock phone using world...
Insurance companies make big bucks by all the people who never file a claim...but i won't get into that.
Many of you have made excellent points and i respect that. I especially liked the comparison of car rims to phone cases i thought that was great!
Hopefully someone will work it out soon or some how an unlocked bootloader will get leaked.
Come one Verizon developers! Leak it! We wont tell!
I was planning on getting the NOTE 3 but i doubt that phone comes with an unlocked bootloader so this d2vzw (sgs3) will most likely be my last samsung phone that I ever buy. I guess i will have to stick with the Nexus phones... I am going to miss micro sdcards!
-droidshadow
droidshadow said:
I know but still i think it should be our choice! While there are millions of us out there that love to customize the software on our phone's by adding new recovery managers or custom rom's we are a small population to the rest of the stock phone using world...
Click to expand...
Click to collapse
Having that debate at this site is kinda silly.... Fact is, "we" will lose the fight against the carriers and/or manufacturers as it stands. The only way to really impact them is to STOP giving them our money, but you know what ? The number of people who "hack" their phones is a tiny percentage in the grand scheme. We'd probably get a "good riddance" response from them anyway.
droidshadow said:
So what is the going to happen to the future of Samsung Phones? Are we no longer going to be able to put custom ROM's and custom Recovery Managers on Samsung Phones?
Click to expand...
Click to collapse
That's correct and.... read on.
So what are our options now? Are we going to simply have to choose different phones like future Google Nexus phones?
Click to expand...
Click to collapse
That could be the only solution. I believe the success that Samsung/Verizon have had with locking down their phones will soon result in ALL phones on ALL carriers being locked down with little or no possibility of rooting or flashing.
I suspect we've seen the end of modifying any phone on any network. I sure hope I'm wrong....
It would be a shame....
xs11e said:
I suspect we've seen the end of modifying any phone on any network. I sure hope I'm wrong....
Click to expand...
Click to collapse
I just rooted and got into CM in the last month. Got rid of all the bloat and installed some neat little apps. And now, just when I get hooked, it's possible that my drug of choice may be going away.
hey there guys, i know this post is a little old, but i just wanted to share my story real quickly with you and to reiterate that messing with the boot loader on an sch-i535 running 4.3 is a HORRIBLE idea.
this is the first phone i have ever tried to root. i successfully rooted the phone, immediately i tried to run cwm recovery. HARDBRICK. i was so proud for all of five minutes that i rooted a phone on my first try. The phone would not power on in ANY mode. i could only get a red light to come on by plugging my phone into my computer with the battery out of the phone. after three days and alot of reading and some help from xda i managed to (amazingly) debrick my phone. I am now very VERY cautious of what i do with my rooted sch-i535 with its HORRIBLE 4.3 crap.
If you are truly hardbricked, im told that jigs (despite what is all over the internet) will not work. (maybe they do but a shop in texas told me a hardbrick will not revive by jig).
JTAG is the most dependable repair.
I revived my phone via debrick image on an sd card.
Bottom line, do everything you can to avoid the situation in the first place.
Never take updates. I unlocked boot loader on 4.3 with ez-unlock app booted into recovery and hard bricked my phone... The fun is over after 4.3...Had to send it to Tampa fl. To get JTAG and it worked.
droidshadow said:
So what is the going to happen to the future of Samsung Phones? Are we no longer going to be able to put custom ROM's and custom Recovery Managers on Samsung Phones?
Click to expand...
Click to collapse
That's correct, given the amount of time the Devs have had to find a way to unlock the bootloader on the S3 and S4 w/o success, I believe it's hopeless.
Worse, I believe Samsung will share their technology and ALL cell phones will eventually have locked boot loaders and be un-rootable, un-flashable and, to me, at least, un-desirable!
I sincerely hope I'm wrong but I believe in a year or two any cellphone will be locked down to whatever software is installed at time of purchase.
xs11e said:
That's correct, given the amount of time the Devs have had to find a way to unlock the bootloader on the S3 and S4 w/o success, I believe it's hopeless.
Worse, I believe Samsung will share their technology and ALL cell phones will eventually have locked boot loaders and be un-rootable, un-flashable and, to me, at least, un-desirable!
I sincerely hope I'm wrong but I believe in a year or two any cellphone will be locked down to whatever software is installed at time of purchase.
Click to expand...
Click to collapse
How's the fun over??? Haha I've seen this same junk many times... I'm running 4.3 rooted. Safestrapped (cwmis garbage) alliance 23 build ROM CSC & build prop tweaks on sch-i535v on straightalk att side. Knox removed manually by me. All bands open except domestic 3g. (Working on it now).
So the funs over? I'm confused.. And how is that? Lol take your time. Research. Learn. Adapt. Achieve. If it can be locked. It can be unlocked. I've yet to run across a phone that I couldn't bring back from the supposed "hard brick" but I did find one I COULDNT brick on purpose. And I threw everything at it. Huwaei m8665 I think it was. I tried for two days to brick that little piece of junk, and not even wrong roots etc could. Lol
An0nYm0u5.bat said:
How's the fun over??? Haha I've seen this same junk many times... I'm running 4.3 rooted. Safestrapped (cwmis garbage) alliance 23 build ROM CSC & build prop tweaks on sch-i535v on straightalk att side. Knox removed manually by me. All bands open except domestic 3g. (Working on it now).
So the funs over? I'm confused.. And how is that? Lol take your time. Research. Learn. Adapt. Achieve. If it can be locked. It can be unlocked. I've yet to run across a phone that I couldn't bring back from the supposed "hard brick" but I did find one I COULDNT brick on purpose. And I threw everything at it. Huwaei m8665 I think it was. I tried for two days to brick that little piece of junk, and not even wrong roots etc could. Lol
Click to expand...
Click to collapse
I agree with you if there is a way to lock it there is a way to unlock it.
is just a matter of time some smart brain will figure it out how to and share LOL
I just got my g930u (Samsung SM-G930UZKAXAA S7 Galaxy) today, and wondering if there is a custom recovery for it?
I have seen a thread on how to root (https://forum.xda-developers.com/galaxy-s7/how-to/root-sm-g930u-tinysu-t3667800)
But I would like to do recovery/backups and flash between ROMs and the stock recovery doesn't let you do that (not that I can see?)
I saw a few threads that indicate CWM or TWRP don't work on the 930u including this one: https://forum.xda-developers.com/android/software-hacking/custom-recovery-s7-sm-g930u-t3668662
Or am I missing something, I may not be up to date on what is possible with the S7 or just behind the times with flashing etc. My current phone is a Galaxy S4 mini so finally I am upgrading to a new phone, but I have been flashing ROMs etc on that for awhile (currently stuck on the last cyanogenmod but still like it!), so just used to doing a backup via recovery before doing anything. Just have to remember all the steps to get to the point where I can do that.
From what I remember I want to do a backup, then root, then install Titanium Backup and then go from there.
ok! Well I guess I will answer my own question - after reading and researching some more, finding out that the US version of this phone (which g930U is) has a locked bootloader and no one has been able to by pass it.
https://forum.xda-developers.com/galaxy-s7/how-to/discussion-unlock-bootloader-rd-t3582800
So! wow I thought I had done a really good job researching and figuring out which phone I wanted (including which ones I could flash ROMs etc on) but I guess not!
Now debating if I should return this for something else....
tph88 said:
ok! Well I guess I will answer my own question - after reading and researching some more, finding out that the US version of this phone (which g930U is) has a locked bootloader and no one has been able to by pass it.
https://forum.xda-developers.com/galaxy-s7/how-to/discussion-unlock-bootloader-rd-t3582800
So! wow I thought I had done a really good job researching and figuring out which phone I wanted (including which ones I could flash ROMs etc on) but I guess not!
Now debating if I should return this for something else....
Click to expand...
Click to collapse
G930F is the one you want