Related
First of all I apologize if this has been brought up before in other posts. I am in a mixture of frustration and panic right now because I tried upgrading to ICS on my Rogers SGS2 LTE, and it failed.
Using Kies, I followed the prompts, and for whatever reason it didn't finish. Now when I boot up the phone, it keeps telling me to use the recovery mode option in Kies. However, if I do try to use recovery mode, it always times out and tells me I may need to contact a Samsung service center. The computer has no problem communicating with the phone, AFAIK.
Basically, I'm here to ask what options I have. Currently, i'm trying to do this: http://forum.xda-developers.com/showthread.php?t=1342348 , but because the stock TAR is taking a long time to download, I'm asking if I have any other options. I would like to keep the data on my phone, but if I have to wipe it to return it to normal I'm willing to do that.
Please help.
Reboot and try again
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Are you rooted? Are you running the stock recovery that came on the phone? If your rooted and have apps that are froze or your running a modded recovery like cwm you must flash back to stock or kies will not ever work
Sent from my SAMSUNG-SGH-I727 using xda premium
I've tried rebooting the computer I was using, and I've also tried another computer with no luck. I got the latest Kies on the other computer, connected the phone with no problem, and tried recovery mode on THAT 2nd computer, but it didn't work because it didn't recognize my recovery code that the first computer gave me.
garydv2002 said:
Are you rooted? Are you running the stock recovery that came on the phone? If your rooted and have apps that are froze or your running a modded recovery like cwm you must flash back to stock or kies will not ever work
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
I *think* I was rooted. I remember doing something a long time ago involving odin. I never installed Cyanogenmod or any other 3rd party roms.
I had Superuser under my apps, if that helps.
I wish I could reply sooner but this board is making me wait 5 mins between posts. Sorry. It's like I'm in the emergency room with a gunshot wound and I'm waiting for the doctor to finish his smoke break, then his coffee break, then washroom break, jesus
by CWM, I think you're asking about Clockwordmod? If so, yes, I had that on my phone. Does this mean I can't use the steps in this thread: http://forum.xda-developers.com/showthread.php?t=1342348 to fix my phone now? Or can I still proceed.
If you have superuser then most likely you are rooted and since you have clockworkmod especially then kies is not gonna update your phone. Your on Rodgers so you need to find the stock firmware and flash it. I'm on att or I could link you to one that would work. I got my stock firmware from Samsung website. Try going to sammobile and see if you can find the stock firmware for your phone. I'm sure since its Samsung they should have Rodgers firmware to. Download the stock firmware and flash it in Odin onto to your phone and then kies should work. If you can't find the stock firmware at sammobile then look for the stock firmware here on xda I'm sure someone on Rodgers has it....
Edit. The link up there to Odin back to stock should work. Just download the file and follow the steps in order and don't leave one out. There are no shortcuts when it comes to flashing a phone or it could be rendered useless for anything more than a paperweight. Konane is real good and would not lead anyone wrong....
Sent from my SAMSUNG-SGH-I727 using xda premium
Just flashed it via Kies, had to use ODIN by flashing stock, Odin wouldn't work till I rebooted my computer, then once Kies updated, I had had a error ( com.Android.phone stopped) but I cleared data and cache in 3e, then everything worked.
Sent from my SGH-I727R using xda premium
I just wanted to post a follow-up. I followed the steps from this thread: http://forum.xda-developers.com/showthread.php?t=1342348 and it fixed me phone. Best of all, I didn't lose anything.
I would still like to get ICS on my phone. I noticed on Sammobile's site that there is a firmware for 4.04 that was released recently. Would I somehow be able to use that, combined with Odin, to get ICS on my phone? In other words, follow all the steps in the aforementioned thread, except, use this newer firmware file? Sorry I realize this may sound like a dumb noob question, but I want to make sure I do things right.
Thanks for all the help btw.
bobbastard said:
I just wanted to post a follow-up. I followed the steps from this thread: http://forum.xda-developers.com/showthread.php?t=1342348 and it fixed me phone. Best of all, I didn't lose anything.
I would still like to get ICS on my phone. I noticed on Sammobile's site that there is a firmware for 4.04 that was released recently. Would I somehow be able to use that, combined with Odin, to get ICS on my phone? In other words, follow all the steps in the aforementioned thread, except, use this newer firmware file? Sorry I realize this may sound like a dumb noob question, but I want to make sure I do things right.
Thanks for all the help btw.
Click to expand...
Click to collapse
If you're back to stock and on Rogers, you should be able to update using Kies.
The thing is, when Odin fixed my phone, it didn't remove Superuser, so doesn't that mean my phone isn't stock anymore? I was expecting Odin to basically reset my phone back to factory settings, but it seems to have just reverted it back to before I tried updating to ICS with kies.
bobbastard said:
The thing is, when Odin fixed my phone, it didn't remove Superuser, so doesn't that mean my phone isn't stock anymore? I was expecting Odin to basically reset my phone back to factory settings, but it seems to have just reverted it back to before I tried updating to ICS with kies.
Click to expand...
Click to collapse
If you go into 3e or cwm if you still have it, you should be able to clear cache and data, so after that Kies should recognize it and start the download
Sent from my SGH-I727R using xda premium
denenatse said:
If you go into 3e or cwm if you still have it, you should be able to clear cache and data, so after that Kies should recognize it and start the download
Sent from my SGH-I727R using xda premium
Click to expand...
Click to collapse
I haven't used the stock 3e that much always just flash cwm but I would suggest that you do a factory data reset to from the recovery if 3e gives that option I've never used it so I'm not sure. But if you are still on cwm recovery kies will not ever update your phone until you put everything back stock. You must have just flashed the kernel only. Flashing just the kernel does not wipe anything you need to flash the stock firmware from sammobile in Odin and that will do a full wipe and restore everything to stock
Sent from my SAMSUNG-SGH-I727 using xda premium
Sorry but what is 3e? The only place i see cwm mentioned is under the rom manager app, but when i launch it rom manager says i don't have a rooted device and super user can't be found. Weird thing is i see super user as an app on my phone.
bobbastard said:
Sorry but what is 3e? The only place i see cwm mentioned is under the rom manager app, but when i launch it rom manager says i don't have a rooted device and super user can't be found. Weird thing is i see super user as an app on my phone.
Click to expand...
Click to collapse
Turn the phone off. Hold both volume up and volume down and hold the power button do not release the volume buttons yet. Pressing all 3 buttons when you first see the screen come on mine shows an att logo then release the power button only. The phone will then boot into either 3e stock recovery or cwm recovery
Sent from my SAMSUNG-SGH-I727 using xda premium
OK, I did what you said, and I see 3e and the option to wipe data/factory reset. So you're recommending I do this BEFORE i try to use Odin and the latest firmware for Sammobile?
Just out of curiosity, if I didn't do a reset before flashing using Odin, what would happen?
bobbastard said:
OK, I did what you said, and I see 3e and the option to wipe data/factory reset. So you're recommending I do this BEFORE i try to use Odin and the latest firmware for Sammobile?
Just out of curiosity, if I didn't do a reset before flashing using Odin, what would happen?
Click to expand...
Click to collapse
Yes. And if you don't it might not wipe everything. I suggest you do it before you flash it and again after...
Sent from my SAMSUNG-SGH-I727 using xda premium
read this to return to stock http://forum.xda-developers.com/showthread.php?t=1652398
this post is just a copy paste from another post i wrote to a n00b
read, read more, read the stickies, i read alot b4 i even attempted to flash, at least a few hundred posts and using the search button.
all problems and solutions have been posted, as u r a n00b all u have todo is invest time into reading alot of posts, because of ur post we all know u havent even bothered to read the stickies, espicially read the one w/n00b's in the title, thats y they r there. .
once u know what ur r doing and r stumped at a certain problem, believe me we can tell by how u post a question, post in the q&a forum
thanky you to anyone ahead of time for reading this post. I really could use some help.
I have a Verizon galaxy s3 which I rooted 3 weeks ago when i got it. I know it was rooted as i had super user permissions, and deleted many bloatware apps. I waited until cm10 came out to flash a new rom and after doing so last night my phone now boots up with this message "System software not authorized by verizon wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
So I tried to boot it in to recovery mode but when I did, the same message came up, only this time it said "recovery booting" in small blue writing in the top left corner.
I followed the directions to a T from a page entitled "Jelly Bean for Verizon Galaxy S3: Unofficial CyanogenMod 10 (CM10) Nightlies Available for Flashing!
From what I understand, the bootloader was somehow never unlocked by kexec. because I cant get in to recovery mode, I was wondering if there was a way to disable the bootlock by installing kexec via odin.
Also, whether it was a good idea or not, I re flashed the stock rom via oden last, which was successful but, nothing has changed still the same response all boot ups. Download boot obviously works though as I have been able to mess with it in odin.
any insight on this would be graciously appreciated.
Lembro said:
thanky you to anyone ahead of time for reading this post. I really could use some help.
I have a Verizon galaxy s3 which I rooted 3 weeks ago when i got it. I know it was rooted as i had super user permissions, and deleted many bloatware apps. I waited until cm10 came out to flash a new rom and after doing so last night my phone now boots up with this message "System software not authorized by verizon wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
So I tried to boot it in to recovery mode but when I did, the same message came up, only this time it said "recovery booting" in small blue writing in the top left corner.
I followed the directions to a T from a page entitled "Jelly Bean for Verizon Galaxy S3: Unofficial CyanogenMod 10 (CM10) Nightlies Available for Flashing!
From what I understand, the bootloader was somehow never unlocked by kexec. because I cant get in to recovery mode, I was wondering if there was a way to disable the bootlock by installing kexec via odin.
Also, whether it was a good idea or not, I re flashed the stock rom via oden last, which was successful but, nothing has changed still the same response all boot ups. Download boot obviously works though as I have been able to mess with it in odin.
any insight on this would be graciously appreciated.
Click to expand...
Click to collapse
Okay, first, If you did follow the directions for that thread, i'm sure it would of worked, I'm pretty sure you are missing something here and i'm pretty sure from reading your post that I think you didn't unlock your bootloader. kexec was a workaround for the locked bootloader, it doesn't unlock it. I would follow droidstyle's guide to unlocking the bootloader, http://forum.xda-developers.com/showpost.php?p=28530409&postcount=2 after you unlocked it, i'm pretty sure you forgot that step. But the issue when flashing back to stock via odin and still showing up its a custom rom, I don't know why that would happen but I suggest reading section 2 of droidstyle's guide on flashing back to stock. http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
So first, I suggest to return to stock, then root, then unlock bootloader, and then install the rom of your choice, preferably without kexec, if you don't want the triple reboot.
RyanW114 said:
Okay, first, If you did follow the directions for that thread, i'm sure it would of worked, I'm pretty sure you are missing something here and i'm pretty sure from reading your post that I think you didn't unlock your bootloader. kexec was a workaround for the locked bootloader, it doesn't unlock it. I would follow droidstyle's guide to unlocking the bootloader, http://forum.xda-developers.com/showpost.php?p=28530409&postcount=2 after you unlocked it, i'm pretty sure you forgot that step. But the issue when flashing back to stock via odin and still showing up its a custom rom, I don't know why that would happen but I suggest reading section 2 of droidstyle's guide on flashing back to stock. http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
So first, I suggest to return to stock, then root, then unlock bootloader, and then install the rom of your choice, preferably without kexec, if you don't want the triple reboot.
Click to expand...
Click to collapse
Agreed! Op, do more reading and less flashing before you end up with a 600.00 paperweight!
Like he says above you have not unlocked your bootloader . Restore nandroid or recover to stock. Then unlock your bootloader and try again
Sent from my SCH-I535 using xda premium
Get rid of the Verizon screen of death
I got the same error msg after flashing a nightly of d2hacker's unofficial cm10, after I had flashed a few nightly's before of the same ROM w/ no problems. I had to
1. Flash a stock bloated unrooted ROM via odin (lemme know if you need a link to one)
2.boot into droid recovery and do a factory reset, and wipe the cache partition also.
If you don't do step 2 you end up w/ a permanent verizon 4G LTE rainbow boot screen :silly:
I haven't re-rooted yet but I'll be trying the official cm10 now that it's up.
MDMoore313 said:
I got the same error msg after flashing a nightly of d2hacker's unofficial cm10, after I had flashed a few nightly's before of the same ROM w/ no problems. I had to
1. Flash a stock bloated unrooted ROM via odin (lemme know if you need a link to one)
2.boot into droid recovery and do a factory reset, and wipe the cache partition also.
If you don't do step 2 you end up w/ a permanent verizon 4G LTE rainbow boot screen :silly:
I haven't re-rooted yet but I'll be trying the official cm10 now that it's up.
Click to expand...
Click to collapse
Refer to my last post
droidstyle said:
Refer to my last post
Click to expand...
Click to collapse
Note that even when I flashed back to stock, my initial boot screen still had the unlocked lock, w/ "Custom" under it, suggesting my bootloader is unlocked
MDMoore313 said:
Note that even when I flashed back to stock, my initial boot screen still had the unlocked lock, w/ "Custom" under it, suggesting my bootloader is unlocked
Click to expand...
Click to collapse
Incorrect. It actually means the opposite. The only way to tell if your bootloader is unlocked is to flash a custom rom/kernel and boot up. Please people, do some reading before you turn your phone into a paperweight. That unlocked lock/custom means you're running or were running custom software and it's been detected as such. One possible culprit is your "custom" recovery. If your bootloader is unlocked, you will not have that problem.
MDMoore313 said:
Note that even when I flashed back to stock, my initial boot screen still had the unlocked lock, w/ "Custom" under it, suggesting my bootloader is unlocked
Click to expand...
Click to collapse
refer to post #3 and read this link
http://forum.xda-developers.com/showpost.php?p=30479625&postcount=13
Zalithian said:
Incorrect. It actually means the opposite. The only way to tell if your bootloader is unlocked is to flash a custom rom/kernel and boot up. Please people, do some reading before you turn your phone into a paperweight. That unlocked lock/custom means you're running or were running custom software and it's been detected as such. One possible culprit is your "custom" recovery. If your bootloader is unlocked, you will not have that problem.
Click to expand...
Click to collapse
Thanks for clearing that up, Where did you find this info? I'm coming from a Droid incredible, so I never had to worry about such things....
EDIT: I just saw Droidstyle's post @ http://forum.xda-developers.com/showpost.php?p=30479625&postcount=13, makes a little sense, but why all of a sudden Verizon's screen of death is odd, if it was already detecting custom s/w to begin with. I used kexec also as a workaround, but this was back when there was no way to unlock the gs3 bootloader.
Yeah absolutely I follow the steps here http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
MDMoore313 said:
Thanks for clearing that up, Where did you find this info? I'm coming from a Droid incredible, so I never had to worry about such things....
EDIT: I just saw Droidstyle's post @ http://forum.xda-developers.com/showpost.php?p=30479625&postcount=13, makes a little sense, but why all of a sudden Verizon's screen of death is odd, if it was already detecting custom s/w to begin with. I used kexec also as a workaround, but this was back when there was no way to unlock the gs3 bootloader.
Yeah absolutely I follow the steps here http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
Click to expand...
Click to collapse
I think it has to do with the "degree" of customization. IE a custom ROM or Kernel will get you the verizon screen of death for sure if you're not unlocked. The custom/unlock icon seems more for minor things like a custom recovery, possibly different firmware or tweaking specific settings.
Zalithian said:
I think it has to do with the "degree" of customization. IE a custom ROM or Kernel will get you the verizon screen of death for sure if you're not unlocked. The custom/unlock icon seems more for minor things like a custom recovery, possibly different firmware or tweaking specific settings.
Click to expand...
Click to collapse
That makes more sense, as the nightlys progress and more modifications are being made, overnight the "switch is flipped" so to speak, and if you're not running a custom rom,
MDMoore313 said:
If you don't do step 2 you end up w/ a permanent verizon 4G LTE rainbow boot screen :silly:
Click to expand...
Click to collapse
Could he Odin back to stock through download mode though? Or will the locked bootloader block download mode and recovery mode too when it detects tampering?
MDMoore313 said:
Thanks for clearing that up, Where did you find this info? I'm coming from a Droid incredible, so I never had to worry about such things....
EDIT: I just saw Droidstyle's post @ http://forum.xda-developers.com/showpost.php?p=30479625&postcount=13, makes a little sense, but why all of a sudden Verizon's screen of death is odd, if it was already detecting custom s/w to begin with. I used kexec also as a workaround, but this was back when there was no way to unlock the gs3 bootloader.
Yeah absolutely I follow the steps here http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
Click to expand...
Click to collapse
The secure aboot.img only checks 3 of the 5 system images on boot. Since we can flash a custom recovery to the recovery partition, the secure aboot img lets it ride, but knows it there....hence why you see the custom lock screen, but device still boots. Kexec allowed the bootloader aka secure aboot.img to see the stock kernel(boot.img) and pass signature checks, then side loads the custom kernel. Thats why there was 3 reboots...now that the bootloader is unlocked, we ditch kexec because unsecure aboot is unlocked and not checking signatures.
However, if you flash a kernel thats non kexec and the bootloader is locked, you will get the verizon screen of death since the secure aboot.img is checking signatures. So never lock the bootloader unless your on stock rom/kernel or using kexec.
Deleted
Jesus. All of these people who don't read up on things before they flash something astounds me.
Lol, the exact same thing happen to me as Op, I was unlock (ezrecovery app) and rooted(casual-revision131) but when I flash unofficial CM10 KANG I was lock out by Verizon message.Thanks to DroidStyle awesome GUIDE i just Odin back to stock along with kernel.Thank you to all the cool people here at xda who help and evolve Android:thumbup:
Ezrecovery app must not have work properly even tho it said unlock, so I use Adam casual R131 flash Unsecure Aboot too.
Sent from my SCH-I535 using xda premium
EvoSideHustlAZ said:
Lol, the exact same thing happen to me as Op, I was unlock (ezrecovery app) and rooted(casual-revision131) but when I flash unofficial CM10 KANG I was lock out by Verizon message.Thanks to DroidStyle awesome GUIDE i just Odin back to stock along with kernel.Thank you to all the cool people here at xda who help and evolve Android:thumbup:
Ezrecovery app must not have work properly even tho it said unlock, so I use Adam casual R131 flash Unsecure Aboot too.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
ezrecovery to unlock? What?
MDMoore313 said:
Note that even when I flashed back to stock, my initial boot screen still had the unlocked lock, w/ "Custom" under it, suggesting my bootloader is unlocked
Click to expand...
Click to collapse
No, that just means that it normally has detected some changed files. If you WERE unlocked you would never see that icon.
TAPPED in on my (now unlocked bootloader) Verizon S3
strung said:
Could he Odin back to stock through download mode though? Or will the locked bootloader block download mode and recovery mode too when it detects tampering?
Click to expand...
Click to collapse
Well, step 1 is going Odin back to stock, but if a cache wipe and factory reset aren't done (like in Droidstyle's guide), then it will never completely boot, at least that's what I experienced after my phone sat at that screen for 10+ minutes. It doesn't run the user setup again.
Okay, So I just rooted and unlocked the bootloader on my Verizon Galaxy S III and tried to flash Cyanogenmod 10 (the latest on on rom manager) and its now stuck on the boot animation. I created a backup before I did this through rommanager but when I try to utilize it, it says the file is empty. HELP PLEASE!! :crying:
Rom Manager strikes again. lol Odin back to stock and start over.
jljones06 said:
Okay, So I just rooted and unlocked the bootloader on my Verizon Galaxy S III and tried to flash Cyanogenmod 10 (the latest on on rom manager) and its now stuck on the boot animation. I created a backup before I did this through rommanager but when I try to utilize it, it says the file is empty. HELP PLEASE!! :crying:
Click to expand...
Click to collapse
I have used it a couple of years ago on my galaxy s fascinate but i forgot how to use odin. Any download links and tutorials you know of? Thanks again
Pulled link from other noob. Yall on a roll today. LOL
http://forum.xda-developers.com/showthread.php?t=1762709
If everything you need not in that section read the rest of Droidstyle's thread.
prdog1 said:
Pulled link from other noob. Yall on a roll today. LOL
http://forum.xda-developers.com/showthread.php?t=1762709
If everything you need not in that section read the rest of Droidstyle's thread.
Click to expand...
Click to collapse
What's wrong with RomManager? Screwing everything up.
Anayalata said:
What's wrong with RomManager? Screwing everything up.
Click to expand...
Click to collapse
You should always be sure to check the total size of the backup file before continuing with low level flashing. With the SGS III CWM has been notorious for not working properly with recovery processes. I switched over to TWRP after my dilemma with CWM.
So yeah, ODIN back to stock and start over.
Be thankful you only have a bootloop and not a total brick.
tekrhino said:
You should always be sure to check the total size of the backup file before continuing with low level flashing. With the SGS III CWM has been notorious for not working properly with recovery processes. I switched over to TWRP after my dilemma with CWM.
So yeah, ODIN back to stock and start over.
Be thankful you only have a bootloop and not a total brick.
Click to expand...
Click to collapse
Well I ended up reflashing the stock rom last night then tried to unlock bootloader again and when I started the ez unlock app it said my phone didnt have root access. So I rooted again the same way I did the first time and now when I try to launch the app it just sits there with a white screen. So then I downloaded a rootchecker app from the market and it says I dont have root access which is probably why the EZ_Unlock app isnt working properly. Thoughts?
jljones06 said:
Well I ended up reflashing the stock rom last night then tried to unlock bootloader again and when I started the ez unlock app it said my phone didnt have root access. So I rooted again the same way I did the first time and now when I try to launch the app it just sits there with a white screen. So then I downloaded a rootchecker app from the market and it says I dont have root access which is probably why the EZ_Unlock app isnt working properly. Thoughts?
Click to expand...
Click to collapse
Open up superuser and update the binaries
Sent from my S3 running Eclipse 2.1
kintwofan said:
Open up superuser and update the binaries
Sent from my S3 running Eclipse 2.1
Click to expand...
Click to collapse
That worked! So now that I've pretty much back to step one, is there anything I should watch out for while trying to flash another ROM? Maybe any ROM suggestions? Thanks
Just flash the ROM yourself in recovery, don't count on RM.
apacseven said:
Just flash the ROM yourself in recovery, don't count on RM.
Click to expand...
Click to collapse
Ill for sure keep that in mind.
Once you get on CM10 their built in updater works pretty well. I haven't heard anyone complain except for the fact it doesn't do an autobackup for you, it just dirty flashes it.
how to unroot samsung galaxay tab 2 7.0 P3113 straight up without any guessing
but guess what i am not the one to be mad at or responsible if anything happens to your device
backup your data of anything
lol had to put that
making this because i was up for like almost 3 hours trying to figure out how to get this done.
first you need 3 files
the latest Jelly Bean stock
http://www.hotfile.com/dl/188869946/30f5c4d/P3113UECLK7_P3113XACCLK7_XAC.zip.html
the odin with root
http://download.chainfire.eu/256/CF...fi-espressowifiue-gtp3113.zip?retrieve_file=1
and
Triangle Away this is where i got the app from
http://forum.xda-developers.com/showthread.php?t=1494114
i put the files in order of size so you can download the files as you go
for extra guidance watch
http://www.youtube.com/watch?v=WzydHUG7XZE
its for s3 but the concept is the exact same
I started from a stock rooted rom i backed up thats what the Triangle Away fourm said to do
Ok while rooted go install Triangle Away once installed boot in to download mode. By turning off the device and holding (Power + Vol down button).
when in download mode press up to enter it this is so you can check your flash / binary count. Once you found out boot restart by (Power + Vol up button) when fully booted
go into Triangle Away before you click reset counter make sure its the same number you saw in the download mode once matched then click the button.
Next after the stock firmware is downloaded extract the file then go back into download mode and press Vol up button to enter it connect device to Odin dont touch or look at anything just click on the left where it says pda click on the md5 file that was extracted from download then click start. Dont touch or look at device until its done because you can possible brick it while in download mode
After flashing let it reboot then skip threw set up to see if superuser is still there. if so (like mine) install Triangle Away app again check the counter. (should be on zero) now go back to download mode and reflash the stock md5 again
and now should be fully stock with no root and no binary count. Take it back to store!! lol or just enjoy stock for new OTA.
#1 this is for the Canadian version of the tab 2. you need to state that.
#2 couldn't you have uploaded this to somewhere else other than hotfile?
First of all, thank you for posting this, wealthy23!
Second, I see fix-this! said this is Canadian version of stock ROM. Is this different from the US version? If so, what's the difference and where I can find the US stock ROM?
premudriy said:
First of all, thank you for posting this, wealthy23!
Second, I see fix-this! said this is Canadian version of stock ROM. Is this different from the US version? If so, what's the difference and where I can find the US stock ROM?
Click to expand...
Click to collapse
Thanks but
I am not sure what he is talking about but it worked on my tab 2 which is US version and
also hot file is used because I didn't upload it I got link from official Samsung site used it so you won't have to sign up for a Samsung account just to get the link and wanted the file to be as pure from source as possible especially when using Odin to flash
Sent from my HTC Glacier using xda premium
I didnt mean to be rude but the file you uploaded is for the canadian version. I double checked on google with the build number. Theres also a US version but with a slightly different extension. Im not at home or i would upload it.
fix-this! said:
I didnt mean to be rude but the file you uploaded is for the canadian version. I double checked on google with the build number. Theres also a US version but with a slightly different extension. Im not at home or i would upload it.
Click to expand...
Click to collapse
O ok wasn't sure how you meant it but that version worked on my tablet and I am in the US but if your file is US you can post it thank you for helping out
Sent from my HTC Glacier using xda premium
I think I found a way
The thread is a month old, so please forgive the necromancy. I haven't noted it elsewhere, so I post in hopes it will help somebody else out.
I found that this works if you flashed via CF-Auto-Root-espressowifi. In triangle away, I reset the counter. Rebooted and clicked "system modified workaround". Rebooted again. Immediately checked the status and after mauling that matter over a bit, it decided "Official" and let me update. (Or, rather, told me I was up to date) Note: probably a good idea to disable the system modified workaround before upgrading. As of yet, it still says "Offical" after disabling modified workaround & reboot, but from what I've read, it will eventually change it's mind. Hence, using this, I imagine you should be able to keep root and use Triangle Away to check for updates every so often. Not stock flashing required.
If you find these instuctions helpful, pay for the App - he deserves it.
Question if I boot into clockworkmod recovery and do a factory reset, wipe cache portions, & dalvik cache then boot into download mode and flash the stock rom will I still be rooted?
Homebound said:
Question if I boot into clockworkmod recovery and do a factory reset, wipe cache portions, & dalvik cache then boot into download mode and flash the stock rom will I still be rooted?
Click to expand...
Click to collapse
Most likely you didn't change back the recovery plus root still might show up after you flash stock rom did you flash with Odin or cwm?
Sent from my HTC Glacier using xda premium
wealthy23 said:
Most likely you didn't change back the recovery plus root still might show up after you flash stock rom did you flash with Odin or cwm?
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
I flashed using Odin. I installed rom manager but it said it couldn't find root & when I boot into recovery I get the shock recovery.
Homebound said:
I flashed using Odin. I installed rom manager but it said it couldn't find root & when I boot into recovery I get the shock recovery.
Click to expand...
Click to collapse
Ok great just check your flash counter in download mode
Sent from my HTC Glacier using xda premium
This is my first post ever here so I'm sorry if I'm breaking some rule (read the forum rules so I don't think I am) or if it's in the wrong subforum (although this does seem like a help & troubleshooting topic to me).
A little backstory is probably necessary.
I rooted my s3 (latest OTA update) via CASUAL (thread: http://forum.xda-developers.com/showthread.php?t=2332825) and it seemed like it worked for the most part, although it didn't boot into twrp like it should have and instead booted into normal recovery. I just assumed that it was because something went wrong with the recovery installation so I just thought "ok whatever."
Root access was there, and I assumed the bootloader was unlocked since I read several places that when it's unlocked, the initial samsung boot logo appears for about a second as opposed to several seconds when it's locked. So I just assumed all i needed was to reinstall a custom recovery and I was golden.
Installed ROM Manager, flashed CWM through the app, and rebooted the phone, and as it was booting into recovery I was greeted with the infamous "NO CUSTOM SOFTWARE ALLOWED PLEASE ALERT PAPA VERIZON IMMEDIATELY" warning.
I was about to flash back to stock through odin (which i regretted since I've had bad experiences in the past using it) when I figured out I could get the device to boot normally by clicking cancel in the download mode confirmation window. I guess it kept trying to reboot to recovery after every unsuccessful boot, which made it seem like it was softbricked to me.
Phone is operating normally now, and it should after another reboot as long as it doesn't try to go into recovery again (though I'm kind of afraid to even do that).
Is there any way without Odin I can fix my recovery and/or bootloader? I'm not sure what the problem is here and I don't think this sort of thing is a common searchable issue. Google/XDA search didn't bring up anything that sounded like someone had 100% the same problem I do.
Also on a semi-related note, does EZ-Unlock still work with this latest OTA? And if my bootloader is potentially unlocked already, would unlocking it again through EZ-Unlock break something?
Sleix said:
This is my first post ever here so I'm sorry if I'm breaking some rule (read the forum rules so I don't think I am) or if it's in the wrong subforum (although this does seem like a help & troubleshooting topic to me).
A little backstory is probably necessary.
I rooted my s3 (latest OTA update) via CASUAL (thread: http://forum.xda-developers.com/showthread.php?t=2332825) and it seemed like it worked for the most part, although it didn't boot into twrp like it should have and instead booted into normal recovery. I just assumed that it was because something went wrong with the recovery installation so I just thought "ok whatever."
Root access was there, and I assumed the bootloader was unlocked since I read several places that when it's unlocked, the initial samsung boot logo appears for about a second as opposed to several seconds when it's locked. So I just assumed all i needed was to reinstall a custom recovery and I was golden.
Installed ROM Manager, flashed CWM through the app, and rebooted the phone, and as it was booting into recovery I was greeted with the infamous "NO CUSTOM SOFTWARE ALLOWED PLEASE ALERT PAPA VERIZON IMMEDIATELY" warning.
I was about to flash back to stock through odin (which i regretted since I've had bad experiences in the past using it) when I figured out I could get the device to boot normally by clicking cancel in the download mode confirmation window, rebooting the phone normally. I guess it kept trying to reboot to recovery after every unsuccessful boot, which made it seem like it was softbricked to me.
Phone is operating normally now, and it should after another reboot as long as it doesn't try to go into recovery again (though I'm kind of afraid to even do that).
Is there any way without Odin I can fix my recovery and/or bootloader? I'm not sure what the problem is here and I don't think this sort of thing is a common searchable issue. Google/XDA search didn't bring up anything that sounded like someone had 100% the same problem I do.
Also on a semi-related note, does EZ-Unlock still work with this latest OTA? And if my bootloader is potentially unlocked already, would unlocking it again through EZ-Unlock break something?
Click to expand...
Click to collapse
That is really weird...
I was reading it and was going to suggest easy unlock v1.2,you will not break anything using that app.
If that still doesn't work, try to flash TWRP through goo manager and see if it somehow fixes your recovery issue.
It sounds to me that your Bootloader is unlocked though... But give it a shot.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
That is really weird...
I was reading it and was going to suggest easy unlock v1.2,you will not break anything using that app.
If that still doesn't work, try to flash TWRP through goo manager and see if it somehow fixes your recovery issue.
It sounds to me that your Bootloader is unlocked though... But give it a shot.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the quick response.
That was going to be what I tried first, that's why I asked about it.
I'll wait for a little more input before trying it though if it's really that weird of an issue.
Sleix said:
Thanks for the quick response.
That was going to be what I tried first, that's why I asked about it.
I'll wait for a little more input before trying it though if it's really that weird of an issue.
Click to expand...
Click to collapse
It's just strange that you only get that message with recovery mode, it normally will not do that.
At the very worst, an odin back to stock is pretty easy. Just follow the same process, but use ez recovery instead of rom manager. It was made specifically for our phone, and never gives me any issues when installing recoveries.
I still think if you use ez unlock it'll probably fix the issue completely. Let me know if you figure it out. Good luck.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
It's just strange that you only get that message with recovery mode, it normally will not do that.
At the very worst, an odin back to stock is pretty easy. Just follow the same process, but use ez recovery instead of rom manager. It was made specifically for our phone, and never gives me any issues when installing recoveries.
I still think if you use ez unlock it'll probably fix the issue completely. Let me know if you figure it out. Good luck.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks. Used ez unlock to unlock the bootloader. It was previously labeled as "Unknown".
Downloading ez recovery right now. Do you think I need to reinstall my recovery just to make sure?
Sleix said:
Thanks. Used ez unlock to unlock the bootloader. It was previously labeled as "Unknown".
Downloading ez recovery right now. Do you think I need to reinstall my recovery just to make sure?
Click to expand...
Click to collapse
No, but it wouldn't hurt.
Use 1.2 of ez unlock, versions 1.3 and 1.4 will give an unknown message. There have also been lots of reports saying that version 1.4 did not unlock their bootloader.
These are the most recent recoveries, download and flash in the ez recovery app if you need to.
http://forum.xda-developers.com/showthread.php?t=2096735
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
No, but it wouldn't hurt.
Use 1.2, versions 1.3 and 1.4 will give an unknown message. There have also been lots of reports saying that version 1.4 did not unlock their bootloader.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Reflashed CMW (I used the version provided by ez recovery, please let me know if that's a problem) just in case and it worked like a charm. Thanks!
Also I did use version 1.2. I actually had it sitting on my phone's home screen before I made this thread.
It still showed up as "Unknown". Maybe that indicated the problem?
Regardless, this problem seems to have been fixed. Now it's time to do some research on verizon s3 roms.
Also another semi-unrelated note, it seems I tripped a flash counter somewhere along the line.
Is Triangle Away one of those apps that is just "open and press a button"? I've been kind of wary of using it since it has that huge warning in app's description.
Sleix said:
Reflashed CMW (I used the version provided by ez recovery, please let me know if that's a problem) just in case and it worked like a charm. Thanks!
Also I did use version 1.2. I actually had it sitting on my phone's home screen before I made this thread.
It still showed up as "Unknown". Maybe that indicated the problem?
Regardless, this problem seems to have been fixed. Now it's time to do some research on verizon s3 roms.
Also another semi-unrelated note, it seems I tripped a flash counter somewhere along the line.
Is Triangle Away one of those apps that is just "open and press a button"? I've been kind of wary of using it since it has that huge warning in app's description.
Click to expand...
Click to collapse
Glad to hear it's working! Strange issue but looks like you ironed it out.
Triangle away is the app you would use. You tripped it using the rooting method injecting your recovery through odin, it's a big warning because it messes with your boot partition. If it fails and borks your boot partition, then you'd have to jtag your phone to fix it.
I personally wouldn't use it unless I was turning in my phone for service or replacement. But the app has great reviews and not many reports of bricks.
Before flashing anything, use a newer recovery image. The one provided by ez recovery is from last year, the newer versions are better written to prevent possible errors that come up with jellybean.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Glad to hear it's working! Strange issue but looks like you ironed it out.
Triangle away is the app you would use. You tripped it using the rooting method injecting your recovery through odin, it's a big warning because it messes with your boot partition. If it fails and borks your boot partition, then you'd have to jtag your phone to fix it.
I personally wouldn't use it unless I was turning in my phone for service or replacement. But the app has great reviews and not many reports of bricks.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I'll keep that in mind, thanks again!
Any roms you'd recommend?
Sleix said:
I'll keep that in mind, thanks again!
Any roms you'd recommend?
Click to expand...
Click to collapse
Read through the op's and decide based on what you're looking for.
Mostly stock, very stable:
Clean rom, bonestock, darthstalker x1.
More modified stocks, more buggy but can run very well:
Hyperdrive, axis, goodness, moar
AOSP isn't my cup of tea, but they are fast and lag free.
Make sure you update your recovery image first, I edited my last post but think you missed it.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Read through the op's and decide based on what you're looking for.
Mostly stock, very stable:
Clean rom, bonestock, darthstalker x1.
More modified stocks, more buggy but can run very well:
Hyperdrive, axis, goodness, moar
AOSP isn't my cup of tea, but they are fast and lag free.
Make sure you update your recovery image first, I edited my last post but think you missed it.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Will do. Thanks for pointing that edit out.