Ok so im on my second tab now, because the first time i tried to flash my tab i bricked it now i got my second tab, and I didnt notice the thread in the development section about locked bootloader and the patch to check to see if its locked. The tab I have now I downloaded the patch to see if its locked, and it says that the bootloader is not signed, and that i can flash anything. Its a GT-P1000M Bell tab running P1000MUGJJ7 2.2. I just want to make sure that if i try to flash this again, im not going to brick it again. It is rooted already, and I have experience flashing as I have an I9000 too. Thanks!
assuming your bootloader is not locked, you can check out the post below,
- worked for me, and i'm on a bell tab as well
http://forum.xda-developers.com/showthread.php?t=932082
Related
Hi all i know this is asked before, ive been searching all around and found nothing to help me. I tried the SGS unlock in the market code not found and error. Tried the method in the xda forums with the generate but it does give me the code but says code if found. Tried to extract nv_data but cant find the file. Can anyone help me please.
What firmware are you running right now?
I used SGS before the update. Does this keep the phone unlocked even after changing the firmware?
I know on past phones when unlocked it stayed unlocked. It is the same with the captivated?
Sent from my SAMSUNG-SGH-I897 using XDA App
catire said:
What firmware are you running right now?
Click to expand...
Click to collapse
Right now im running stock from one click, but i didnt buy this phone brand new got it from ebay so i cant say for sure if it had prior flashing.
xisruno said:
I used SGS before the update. Does this keep the phone unlocked even after changing the firmware?
I know on past phones when unlocked it stayed unlocked. It is the same with the captivated?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Yes from my experience so far with my 1st captivate, i been flashing that with cognition and its still unlocked but im not sure about stock jh7 from kies.
Have you tried this?
LINK
catire said:
Have you tried this?
LINK
Click to expand...
Click to collapse
thanks man hope it does im going to try and post an update.
Well i found my nv_data file then im not sure why the permission failed when i tried the galaxy unlocker.
knightkyun said:
Yes from my experience so far with my 1st captivate, i been flashing that with cognition and its still unlocked but im not sure about stock jh7 from kies.
Click to expand...
Click to collapse
I got it easily unlocked when running stock Eclair 2.1, but when flashed with the leaked stock Froyo 2.2 it got network locked again. Luckily I had saved the code, so I just entered it with a diferent SIM and voilá! After that, I've been flashing with Cognition's ROMS and it has remained unlocked.
On a different case : After unlocking a new Captivate (with stock Eclair 2.1), I flashed it with Cog's 2.2 Beta5.5 and it's still unlocked.
pilot_xphile said:
I got it easily unlocked when running stock Eclair 2.1, but when flashed with the leaked stock Froyo 2.2 it got network locked again. Luckily I had saved the code, so I just entered it with a diferent SIM and voilá! After that, I've been flashing with Cognition's ROMS and it has remained unlocked.
On a different case : After unlocking a new Captivate (with stock Eclair 2.1), I flashed it with Cog's 2.2 Beta5.5 and it's still unlocked.
Click to expand...
Click to collapse
Yeah same for me its still unlocked. But my 2nd Captivate i got from ebay doesnt want to be unlocked lol. Im not sure what the previous owner did it so far. Last resort for me right now if i cant get permission to nv_data is to go to a service and get the code from imei, which is fine.
All,
I unlocked the bootloader (I see the unlocked padlock at the bottom of the screen at boot) some time ago on my N1. Now that the official 2.3.3 update is out, I thought I would give it a try.
I keep getting 'signature verification failures' when I tried to install either the official or other versions of 2.3.3
So, I learned it was likely because my HBOOT needed to updated. I downloaded an tried to install the new version (0.35.0017?) and it sorta acts like it is going to update it, reboots a couple of times, but doesn't seem to work.
Could someone please give me some guidance on exactly what I need to do from here to get the 2.3.3. update applied?
Thanks in advance,
-Rob
You most probably have custom recovery, and your problem isn't bootloader at all.
Flash the stock version packaged for custom recovery, found in Development section.
I've recently gotten a Unlocked Bell (but Unrooted!) IS with Froyo on it.
I check the system software update and the gingerbread update is available for download and whatnot.
I download it and click to install but it stops after a restart on the bootloader screen where I see the install package cannot open. (You know the screen with the blue android and exclamation mark)
Is it REQUIRED that I need to root the IS to update the phone to 2.3?
I'm under Telus btw.
-Canada-
Thanks
sdkim89 said:
I've recently gotten a Unlocked Bell (but Unrooted!) IS with Froyo on it.
I check the system software update and the gingerbread update is available for download and whatnot.
I download it and click to install but it stops after a restart on the bootloader screen where I see the install package cannot open. (You know the screen with the blue android and exclamation mark)
Is it REQUIRED that I need to root the IS to update the phone to 2.3?
I'm under Telus btw.
-Canada-
Thanks
Click to expand...
Click to collapse
Since your IncS is carrier unlocked, you are trying to load a Bell GB update on the phone and I bet it is checking to see if the phone has a Bell CID (which it doesn't since you have unlocked it).
You would be better off running AlphaRevX Revolutionary to S-OFF and install ClockworkMod recovery. After that process you would then be able to install a rooted version of the IncS WWE Gingerbread ROM and lose all of the Bell bloatware.
I'm just very unsure about rooting IS 'cause it says its still in the beta stages so, I'm trying to optimize my phone as much as it's able before considering rooting (which I'm sure everyone is trying to).
Also not sure if anything will go wrong and such 'cause it's in beta
Had the Desire before and everything was sure 100% hence.
Hi all, im using the telstra tab and wanna upgrade it to 2.3
do i need to rooted or bootloader the tab, or both of rooted and bootloader the tab? then flash it?
i read other topic from www 。thegalaxytabforum.com/index.php?/topic/3248-stock-rom-android-233-gingerbread-p1000xxjq1-p1000xxjq1-p1000xxjpz/
under the post it said "Note 1: The bootloaders ARE signed, but NOT secured. Custom kernels and firmwares can still be flashed ! ". i kinda dont understand what it means.
and in their method they didnt mention about whether the tab need to be rooted. will that be cool?
thanks.
Hello, I currently have a few Samsungs (old, S3), and they are all rooted (I am familiar with rooting, firmware loading via Odin, TWRP/CWM, etc). I have read a large number of posts on how the Galaxy S5 after 5.X is boot loader locked. I was gifted with a AT&T Samsung Galaxy S5, with the Sim unlock code (and I would like to use it), however, it has been updated to G900AUCS4CPA2. To add insult to injury, I am on T-Mobile.
Forum posts have indicated that the only requirement to move to T-Mobile is to change the sim. However, it would be nice to use the wifi calling, etc (or at least a T-Mobile rom). Even though the bootloader is locked, is there a way to install a Tmobile S5 5.X or 6.X rom? It seems like installing different AT&T roms via Odin is possible, as long as they are >=5.X. Is there a way to install a T-Mobile rom via Odin?
Barring all of that, is there a way to install a totally generic rom, and not be AT&T branded/bloated/etc?
Thank you.
No. The locked bootloader prevents all of that.
shortydoggg said:
No. The locked bootloader prevents all of that.
Click to expand...
Click to collapse
Ok, but it came with 6.0 and I downgraded to PA2. So there is no way to install anything else?
Backstory: I initially tried and failed to install 4.4.2, and with more reading realized that I was on the "bootloader locked" 6.0, and that I had thrashed the current rom that was installed. I then found an XDA post on moving back to 6.0, but it starts with PA2, which installed successfully and the phone is on PA2 (the rom I posted in the beginning of the thread). So, I can seemingly install AT&T roms, as long as they are 5.0+?? I just can not move anywhere else??
Thank you for your input.