Related
Hi,
I have bought two phones from craiglist.
1. Captivate, and
2. Vibrant.
Both are locked. I did read forums before buying, and to me it looked i will be able to unlock. After 4 days of experiments and trails. I feel stuck, exhausted and also screwed.
Mine 1st worry is to get both of them unlocked, and 2nd is to get them rooted.
When i bought the Vibrant, it was already rooted on 2.1 eclair. I tried sgslock.apk (latest) to unlock, but no codes found using both root and unroot option. I read in one thread that sgsUnlock works better with froyo.
I followed the instructions at to install froyo on both the phones.
1. w w w . pathikshah. com/blog/install-android-2-2-froyo-galaxy-s
This froyo build is with prefix I9000XXJP2.
The installation process is straight forward, run Odin select all the files PDA, Modem and CSC. Select the other downloaded PIT file (link on the same page).
Press the Start Button. Wait for the device to reboot into froyo.
What it did.
This installed froyo, the froyo looked stock
Ques 1 - What does stock mean? straight from the google, without bloatware.
Tired to do lot of things to get the vibrant and captivate rooted. But nothing worked.
The funny observation is it reverses the functionality of Vol+ and Vol- keys and makes the Power Button function-less, during the recovery screen. So, after the reboot, first i have to use vol+ (up) button to scroll down, after that to select i press power button which doesnot respond to any selections. So none of root patched reboots were installed. It hasppens for both the phones.
Ques 2 - Does it mean, the build i am using I9000XXJP2 is bad. Another observation it show Recovery 3e, whereas on all the forums i see talk about 2e.
Ques 3 - Do i have to get to Recovery 2e. If yes, then how?
I tried sgsUnlock on both the phones. Latest version and the older version.
So, the SgsUnlock cudnt have any root privilege to do a actual "root generate code".
Then I tried various one click solutions,
a. Generate windows unlock
b. super one click
c. Various version of Generate windows unlock
d. adb methond, but i am not sure if i am doing it right.
The SuperClickOne unlocked the captivate, i am really glad but terribly tired with vibrant. SuperClickOne didnot root the captivate. Its "Unlock Captivate" tab did the job.
Ques 4a - The unlock code now I have for captivate, will it remain the same for every new android I install later. I mean will it bother me like Iphones, after every update my baseband will be locked, and then all the trauma again.
Ques 4b - Or is it unlocked forever. Even if it is somehow locked again, the same code with do the unlocking.
Ques 4c - SuperOneClick -- Does not have a " vibrant unlock" tab like "captivate unlock" tab. Is their any other application which does a vibrant specific unlock, or a sure-shot vibrant unlock?
Please advice, how to
i - unlock vibrant
ii - install right froyo on vibrant, and root it.
iii - install right froyo on captivate, and root it.
iv - i am even open to install modfied froyos, if i am able to do the above 3.
Thanks a lot in anticipation.
May I make a suggestion, however I don't know if it will solve your problem.
I think after the JI6 OTA, the unlock app no longer worked.
Would it be posssible to use ODIN, to flash your phone back to stock JFD, then run the unlock app, and get your unlock code! Then you can flash your phone to the most recent update after getting the code.
Maybe it will work? Trick the system by downgrading!
Yes that is what i am also trying to do. I am looking at the safest bet, i mean install eclair or froyo which is unlockable. Get the unlock codes for vibrant. And later install the latest build. Can please some one post the link for the stock build.
i am looking at "http :// forum.xda-developers.com/showthread.php?t=734475".
any other recommendations. Thanks.
vibrant rooted on 2.1 with baseband T959UVJFD
copied the nv_data file to desktop, found SSNV. Totally lost to decipher data from it. Can anyone help.
any help...?
SamsungVibrant said:
May I make a suggestion, however I don't know if it will solve your problem.
I think after the JI6 OTA, the unlock app no longer worked.
Would it be posssible to use ODIN, to flash your phone back to stock JFD, then run the unlock app, and get your unlock code! Then you can flash your phone to the most recent update after getting the code.
Maybe it will work? Trick the system by downgrading!
Click to expand...
Click to collapse
I just did that, and the unlock does not work. I used the file at h**p://forum.xda-developers.com/showthread.php?t=734475
Is their a reason the nv_data file might corrupted.?
I believe any phone with JI6 or later will not be able to use sgsunlock. Even if you go back to stock JFD. There is a work around though. If you go to the Bible in the developers section there is a link to where helroz was able to get around this. I think the link says JI6 SimUnlock Fix or something like that.
Sent from my SGH-T959 using XDA App
Another suggestion. Are you a T-Mobile customer? T-Mobile customers, of at least 40 days, get free unlock codes. They might even give you an unlock code for the captivate if you intend on using it on their network. (a rep once told me they can get any unock code for their customers, but for non-tmobile phones the process just takes longer) maybe the rep was wrong...but its worth it for the captivate also.
That is your best bet, and it is free.
Got the unlock code from T-mobile. Nothing else worked. Thanks.
help
hello, i have recently bough a samsung galaxy s 190000t of ebay. The first week there was no problems with the phone at all but now it will not make or recieve any calls or messages but everything else works fine?. the first week no problems, there still is reception bars on the phone and the phone is not sim locked. what do you think is wrong and what can i do to fix it. maybe the phone was a stolen one an the origanl owner bloked or something like that ? it is there any chance yous could help me out?
Ok, so I'm kinda already at stock. When I first got my SGS2, I rooted it but didn't put a custom ROM on. I was happy with this arrangement. It's been so long now though, that I've forgotten what I did and how to get it back to how it was when i bought it.
I have taken a screenshot of my info page: Here
I've spent all evening trying to get it back to untouched status - I've managed to unroot it and flash the stock kernel (even though the kernel info in the screenshot still mentions root for some reason). This doesn't seem to be enough though - it's still failing to install an OTA or kies update.
I'm going to be passing this phone on once the SGS3 comes out, so it's vital that it's back to square one and able to handle OTA updates.
I'd really appreciate some guidance here, I've been out of the tinkering game for far too long!
I don't see anything out of the ordinary on your screenshot. Have you ever changed CSC? Also, make sure you disable USB debugging if you ever enabled it.
Try * HERE * for the official O2 UK ROMs, with the latest being XWLP3. These will wipe and unroot your phone.
Intratech has put a link at the top on the procedure you need to follow.
Don't worry what the kernel says. When I first got mine it used to say root and dell and it wasn't a dell or rooted.
What's CSC? I've turned usb debugging off btw.
I've tried the OTAs and they download, but when it comes to installing it stops at 14% for a moment, moves up to 19% then reboots and gives me a failed update message.
I did wonder if i changed the recovery but I'm not sure how to tell - or how to change it back if I did. Would that cause problems?
I'll check out that o2 stuff, thanks. This phone was bought unlocked and unbranded though, will that matter?
Sent from my Galaxy S II using XDA App
More info in attached pic.
A quick google would lead me to say that no, I didn't change CSC. I hope!
Sent from my Galaxy S II using XDA App
r2001uk said:
Ok, so I'm kinda already at stock. When I first got my SGS2, I rooted it but didn't put a custom ROM on. I was happy with this arrangement. It's been so long now though, that I've forgotten what I did and how to get it back to how it was when i bought it.
I have taken a screenshot of my info page: Here
I've spent all evening trying to get it back to untouched status - I've managed to unroot it and flash the stock kernel (even though the kernel info in the screenshot still mentions root for some reason). This doesn't seem to be enough though - it's still failing to install an OTA or kies update.
I'm going to be passing this phone on once the SGS3 comes out, so it's vital that it's back to square one and able to handle OTA updates.
I'd really appreciate some guidance here, I've been out of the tinkering game for far too long!
Click to expand...
Click to collapse
you have to reset the counter as well search forum for custom binary counter and usb jig
other than that you may try to flash an old firmware 2.3.5 and then reset counter;
the stock rom how did you obtain it? is it the right one for your phone's region? did you have another one?
i would recommend you use fusdownloader; get the right stock rom for your phone and flash then; i have successfully unrooted my old sgs II before I gave it away to my mum as a birthday present
I've always stayed at stock rom because I was happy with it. I think the only rom-related change might have been to update to 2.3.3. Pretty sure it was the correct region. I didn't need to wipe anyway.
Would wiping and flashing everything from scratch solve my problem? Rom, kernel, recovery etc. I could do that, but I'd wait until I was about to give the phone away. If there's a single package to flash in Odin that sets everything back to factory standard, that'd be perfect.
Sent from my Galaxy S II using XDA App
Oh and about the jig? If that's the only option that doesn't involve a full wipe, I'll just hold off until I wipe. I don't fancy buying a jig for one task.
This'll teach me for tinkering and then waiting a year to revert!
Sent from my Galaxy S II using XDA App
To me its as simple as flashing O2 firmware via Odin after a full wipe of phone via CWM recovery .
GB O2 was posted KDD and KE2
and ICS LP3 O2 is available and should be on Checkfus .
kernel says root has nothing at all to do with ROOTING or even a rooted phone its a build signature only .
OTA update is known to be poor for some sticking during the download .
jje
Ok, so I tried running through Adam Outler's guide on rooting the Note 2 with the "CASUAL(R515b) No You Verizon!" method. It seemed to fail a couple of times but then it started going well. All until I got to about the last fourth of the process. Everything froze with the phone suspended in download mode. So, I unplugged everything to try again but lo and behold, the phone will not boot up anymore. It's not even a bootloop, it just shows the screen that says, "Samsung Galaxy Note 2" for a split second and then goes blank. It will do this indefinitely until I pull the battery.
I have always rooted my phones before and never had a problem like this. I have absolutely no idea how to fix this.
The phone originally was originally on the vramc3 framework and was completely stock.
Here is the pastebin (xda doesn't want me to post links so just eliminate the dashes: h-t-t-p-:-/-/pastebin.com/PuKkZghE
Please Please Please advise!
Solomon386 said:
Ok, so I tried running through Adam Outler's guide on rooting the Note 2 with the "CASUAL(R515b) No You Verizon!" method. It seemed to fail a couple of times but then it started going well. All until I got to about the last fourth of the process. Everything froze with the phone suspended in download mode. So, I unplugged everything to try again but lo and behold, the phone will not boot up anymore. It's not even a bootloop, it just shows the screen that says, "Samsung Galaxy Note 2" for a split second and then goes blank. It will do this indefinitely until I pull the battery.
I have always rooted my phones before and never had a problem like this. I have absolutely no idea how to fix this.
The phone originally was originally on the vramc3 framework and was completely stock.
Here is the pastebin (xda doesn't want me to post links so just eliminate the dashes: h-t-t-p-:-/-/pastebin.com/PuKkZghE
Please Please Please advise!
Click to expand...
Click to collapse
Fortunately its only a softbrick. If the phone posts (ie displays the Samsung Galaxy Note 2 screen) it should be salvageable with little difficulty. Verify that you can boot download mode (power off, vol down+home while powering on). Follow a guide for returning to stock, using odin to flash a stock image. This will get you back in business. Are you certain you were using the correct casual for your firmware revision?
apacseven said:
Fortunately its only a softbrick. If the phone posts (ie displays the Samsung Galaxy Note 2 screen) it should be salvageable with little difficulty. Verify that you can boot download mode (power off, vol down+home while powering on). Follow a guide for returning to stock, using odin to flash a stock image. This will get you back in business. Are you certain you were using the correct casual for your firmware revision?
Click to expand...
Click to collapse
Ok, I was able to get it into download mode. I'm downloading the stock image right now. Yeah I 'm definitely sure that I used the right casual for my firmware. It's my friend's phone and he just bought it a week ago so he would definitely be on the most recent firmware. I'll update with how everthing goes after I try to flash the stock image. Are there any other methods for rooting it once I get it back to stock?
Solomon386 said:
Ok, I was able to get it into download mode. I'm downloading the stock image right now. Yeah I 'm definitely sure that I used the right casual for my firmware. It's my friend's phone and he just bought it a week ago so he would definitely be on the most recent firmware. I'll update with how everthing goes after I try to flash the stock image. Are there any other methods for rooting it once I get it back to stock?
Click to expand...
Click to collapse
You seem convinced that you had the right casual, but I'm not. I dont want to sound like I'm calling you out I just want to make sure we're on the same page. My note 2 which I purchased last week from BestBuy came with LL4 (second to latest revision), so the No You Verizon wouldnt have worked, I needed Back Atcha Verizon. Which firmware you had when you tried to use CASUAL also impacts which stock image you need to flash to return to stock. As long as you are absolutely sure you were on MC3 then this is all moot. I dont know of another way to root, I would imagine there is one but you will have to search around. CASUAL is the way to go though, so I suggest we troubleshoot this and get that method to work.
apacseven said:
You seem convinced that you had the right casual, but I'm not. I dont want to sound like I'm calling you out I just want to make sure we're on the same page. My note 2 which I purchased last week from BestBuy came with LL4 (second to latest revision), so the No You Verizon wouldnt have worked, I needed Back Atcha Verizon. Which firmware you had when you tried to use CASUAL also impacts which stock image you need to flash to return to stock. As long as you are absolutely sure you were on MC3 then this is all moot. I dont know of another way to root, I would imagine there is one but you will have to search around. CASUAL is the way to go though, so I suggest we troubleshoot this and get that method to work.
Click to expand...
Click to collapse
Ok, the phone is now working. Thank God! I'm pretty sure I got the right one, I'm currently looking at the About Phone section on Settings and it lists the build number as JZ054K.1605VRAMC3. That would mean that I need the No You Verizon one right?
Solomon386 said:
Ok, the phone is now working. Thank God! I'm pretty sure I got the right one, I'm currently looking at the About Phone section on Settings and it lists the build number as JZ054K.1605VRAMC3. That would mean that I need the No You Verizon one right?
Click to expand...
Click to collapse
Indeed. Try CASUAL again and report back with any specific errors you encounter.
just a heads up, but make sure you have all anti-virus and/or security programs disabled before running casual.
Hi all
Recently I upgraded from Samsungs stock 4.1.2 firmware to CyanogenMod 10.2 Stable (based on 4.3.1) using their installer program. Since upgrading the Wifi has been unusable and I have not managed to get the problem resolved through their forums so I have decided to go back to the stock rom.
Now that Samsung have re-released 4.3 for the S3 in the UK (after the one from last month which was pulled for problems) I would like to use this one as it fixes a bluetooth streaming issue I have endured for a long time. I can't find this new firmware for download anywhere so wondered if it is feasible to download say the stock rom 4.1.2 and then upgrade somehow? I have a red line on the bootup screen which shows it has been modified (which triangle away won't remove due to custom rom/bootloader or something like that) so I believe this means I will be blocked from then upgrading from 4.3 OTA but able to do so with Kies?
Being a novice at this I am obviously worried about breaking my phone and I am not sure if having i9300XXEMG4 as a baseband version is an issue among other things after reading the forums. As much as I have read about EFS and the downgrading modem problems, none of it is making sense to me at the moment, even after reading all the documents. Brain freeze maybe!
The cyanogenMod also changed recovery and unlocked the bootloader going by what I have read, is this an issue I need to worry about?
Any advice that can take away some worries and get me on the right path would be muchly appreciated!
You are posting in the wrong forum .
UNDERSTAND FIRST
http://forum.xda-developers.com/showthread.php?t=2362743
Network IMEI EFS
http://forum.xda-developers.com/showthread.php?t=2393289
Downgrade and network problems .
http://forum.xda-developers.com/showthread.php?t=2531221
JJEgan said:
You are posting in the wrong forum .
UNDERSTAND FIRST
http://forum.xda-developers.com/showthread.php?t=2362743
Network IMEI EFS
http://forum.xda-developers.com/showthread.php?t=2393289
Downgrade and network problems .
http://forum.xda-developers.com/showthread.php?t=2531221
Click to expand...
Click to collapse
Thank you for your post. I did follow a link in the !!ALL QUESTIONS GO IN THE Q&A FORUM!! OR THEY MAY BE DELETED!! sticky thread which took me to the Q&A forum where I thought I was posting. It is possible a confusion happened during the sign up process.
After reading those threads, two of which I had already read before posting, I have more understanding than I did before. Somehow I missed about the S3 not having a locked bootlader to begin with. I have backup up the EFS using Ktool but also understand it would have been more useful to do before flashing CM 10.2 as I now only have a EFS v2 backup rather than a version 1. What I am unsure of is what is my best action to take at the moment, going by the information I have. I can it is best not to go downgrade to earlier firmwares unless I wanted an added headache of the modem workarounds but do not see the best way to get back to a stock 4.3 firmware still.
I am on Three mobile (H3G) in the UK but don't think my phone is actually locked to them and don't know if that means the BTU is the option I should be choosing. Even so, when I check the firmwares on http://www.sammobile.com/firmwares/2/ I can only see a firmware added last month which I have to assume is the bad 4.3 update that hit the UK and was pulled after the problems it caused. If it was my best option for flashing, even with the problems it caused, how would I then go about getting the extra update that Samsung pushed out to fix the problem?
I saw the Korean factory flash in one of the threads too, not sure if this is too extreme (and potentially more dangerous) than the other options which may be available to me.
Obviously I would like to do this right the first time, rather than stumble backwards fixing all the mistakes I make at the time. So sorry if I am asking what may be simple to some. My knowledge of phones sucks and I wish I hadn't been tempted by the easy looking Cyanogenmod installer now!
Noticed after a few cache and devlik cleans and reboots that the wifi started working on the CM 10.2 mod but only for the main browser and hit and miss with google play. Every over app didn't work on wifi though, but did on cell. I googled all over to see many with similar problems, which suggested manually setting the time and date and static ip settings, clean davlik and updating play apps after deleting their cache.
None of them worked. So to potentially getting away from flashing, does anyone know any other ideas to resolve this? Wifi connects, stock google browser works, Play works flakey. Other installed browsers wont load any pages or connect to the net, such as speed testing app. The only unusual app that also works in a twitter app. Installed an app to see if there was a hidden proxy setting, but it found nothing, Really strange. All the apps work on cell.
Follow the guide in general forum, stickies, to flash back to stock BTU. Network lock is irrelevant to rom.
Choose either 4.1.2 or 4.3 but your baseband must be EMG or later as you now have efs v2.
Don't flash things you don't fully understand, any non Samsung rom has drawbacks you'll have to live with.
In the stickies is a world of information supposed to help you.
boomboomer said:
Follow the guide in general forum, stickies, to flash back to stock BTU. Network lock is irrelevant to rom.
Choose either 4.1.2 or 4.3 but your baseband must be EMG or later as you now have efs v2.
Don't flash things you don't fully understand, any non Samsung rom has drawbacks you'll have to live with.
In the stickies is a world of information supposed to help you.
Click to expand...
Click to collapse
Appreciate you giving me a direction to go. It seems the problem I had finding firmwares the last few days were due to Hotfile going offline and Sammobile rebuilding their index of firmwares. I found through the forums 4.3 BTU I9300XXUGMJ9_I9300OXAGMJ9_BTU.zip which contained a 1.5GB file called I9300XXUGMJ9_I9300OXAGMJ9_I9300XXUGMJ9_HOME.tar.md5 which I think is the correct one which I will try and flash later using the guides. It's not the new fixed 4.3, it's the older broken one but I guess in time I can apply the fix that Samsung are pushing out. This was part of my original question and now i have seen from other posts in the last few days that there is no full copy of the 4.3 anywhere.
The timing of me doing this appears to have been bad for a few of the above reasons, making working it out more difficult to work out for someone who has not done this before.
I can see from your signature and also your post that you think questions such as mine are easily answered in the various threads and through search. Personally I did try all those options first but either my lack of understanding or the overwhelming amount of information meant I was unsure as to what I should actually be doing, let alone which guide to follow. Even googling for BTU or searching xda to try and find what it means was fruitless so trying to put the pieces together is not easy if you have no experience with phones. I have programmed a Pi to do many tasks, built mainframe>SAS gateways and various technical challenges but I still struggle with all the phone flashing info
Many thanks again. Even a few words have been helpful
If you flash the kernel from the Chinese ZCUBMK it will fix all the broken parts of the current uk rom, until the latest ota emerges on xda.
I don't mind helping people who have made a genuine attempt to help themselves, my signature is aimed at the those who flash anything they find then demand someone give them an instant fix.
Your only mistake seems to have been the depth of research before you started, which could have been fatal to your phone -many first time flashes end up with a new motherboard required.
Sent from my GT-I9300 using Tapatalk
If the ota doesn't work in the next few day's I will try that kernel, thanks for that info!
I managed to flash the older official 4.3 firmware just now, so progress has been made A quick check shows me that the power on/lock screen lag problem is present so I assume the other issues will be there too. The red line showing the flash counter has gone and I got no modified phone error when attempting an ota update, as well as device status saying official, so I assume I should be able to upgrade that way when they allow more upgrades on the rollout server.
In case anyone else needs to do the same, this is what I did:
1) Downloaded https://mega.co.nz/#!DVxVgZZb!LIxKGA2Q_KbBH9APo_slOCdZNGJgfn1O6fxOF4C OkHA which I found via a thread titled [Official Firmwares] I9300XXUGMJ9 (Android 4.3) - Ireland (VDI) [04-11-13]
2) Followed the flashing instructions on this page
3) After flashing I got stuck at the Samsung boot screen with the blue light on, even after reseting a few times. So I powered off, held down the home button, volume up and then the power button which took me to the recovery screen where I chose the factory default option. All worked fine after that.
Thanks once again for your help with this boomboomer. A bit of direction was enough to give me the confidence to try it. It's nice to be back to a familiar interface (although it has changed from the 4.1.2 I had before) but the initial setup reminded me of all the bloatware installed. It's a fair bit slower than CyanogenMod was but it all seems to work ok. Once I get the ota update i'll root and freeze some apps to sort that out. Now to install TSF shell
First id like to say this is my first time posting in any forum. I do apologize if this is in the wrong spot. I recently got an unlocked galaxy s5. Its the sm-g900t so originally made for tmobile i guess but it was unlocked brand new. When i took it home i was using it and noticed it was running android 4.4. Obviously i went to the settings and tried to update to the newest OS. It searched but couldnt find any updates. So i download samsung kies, it said it found the latest version and downloaded it. I installed it and everything and now when i boot the phone i get tmobiles boot logo and all their bloatware. Is there a way, anyway to download an android OS that is completely stock like for an unlocked phone? When i got the phone and turned it on there was no tmobile boot logo or any bloatware. Ive been searching online and cant really find anything on it. If someone could help me out id be ever so thankful!
fallenangelrising90 said:
First id like to say this is my first time posting in any forum. I do apologize if this is in the wrong spot. I recently got an unlocked galaxy s5. Its the sm-g900t so originally made for tmobile i guess but it was unlocked brand new. When i took it home i was using it and noticed it was running android 4.4. Obviously i went to the settings and tried to update to the newest OS. It searched but couldnt find any updates. So i download samsung kies, it said it found the latest version and downloaded it. I installed it and everything and now when i boot the phone i get tmobiles boot logo and all their bloatware. Is there a way, anyway to download an android OS that is completely stock like for an unlocked phone? When i got the phone and turned it on there was no tmobile boot logo or any bloatware. Ive been searching online and cant really find anything on it. If someone could help me out id be ever so thankful!
Click to expand...
Click to collapse
The reason it couldn't find any updates, is that the previous owner had installed a non-Stock Rom. By using Kies, you overwrote the firmware with Stock firmware.
You have a few options:
1) You can root your current phone and then de-bloat. This will keep WiFi Calling and you can decide what is bloat and what isn't. Titanium Backup can freeze apps you don't like, or there are several de-bloating methods on this forum.
2) You can install an AOSP (Android Open Source Project) based ROM. There are several on this forum (under Development sub-forum), and on the other SM-900 fora, especially the International S5 forum.
3) You can go with a CyanogenMod ROM.
The good thing about the SM-900T is that is has an unlocked bootloader, so you can flash to your heart's content.
Rob
My Note 4 N910T was the same way. I almost bet anything it's a Rent A Center phone. Just download the stock firmware and odin update and you will be good.