Hi, the 'search' couldn't help me find a right answer to my prob so I started this thread:
All I want is to unlock my Vibrant, the thing is the folder /efs/ (where the files with the codes to unlock are stored) is completely empty. So no nv_data.bin available.
So what is my best approach so restore those file(s)? I am on 2.2. Can't I just restore to stock 2.1 rom with odin? But this is risky, As I understand I could brick my phone entirely because it seams that I have a hardware locket phone (I can only access recovery and download mode through ADB or Terminal) So if I brick it, I can't go to recovery or download mode, I think.
But even if I successfully manage to downgrade to stock 2.1 without bricking my phone there is another prob.:
The guy in the following thread did the same thing now his phone in permanentely locket
http://forum.xda-developers.com/showthread.php?t=859034
Last post: "still can't unlock though. Was told my phone is now perm locked. im guessing perm stands for..permanent, which means its unlockable..forever. sigh. is this true? anything else i can do now..?"
Isn't there another way without downgrading back to 2.1 ?
Can I still get an unlock code from an online-service everything else fails?
Thank you.
Related
Currently my wife's phone is unlocked. I am a noob and I am just getting into the flash/root android community so I upgraded her stock phone to JI6 on Eclair. As a result, her unlocking codes are not easily accessible anymore but the phone is unlocked. I'm wondering if I need to risk going through the steps in this thread:
http://forum.xda-developers.com/showthread.php?t=822008&page=11 (under Helroz) to find the unlock codes for the phone or I can just continue flash in Roms and kernels on her phone.
I guess the real question is: how important is it to have the unlocking codes if your phone is already unlocked and under what circumstances would the phone relock itself?
Thank you in advance for all replies.
Unlocked as in.... you can change out the sd card? Otherwise, if you have already flashed a differnet ROM, kernel, or modem or whatever, I don't think it would be different if you did it again.
But I would assume once you're unlocked...well you're unlocked, right?
Lol I am unlocked...I'm using the t mobile phone on the wind network I
n toronto so I can say with certainty that I'm unlocked. The reason why I'm asking is because we have two viberants (one that I have the unlock code and one that I don't ). being the noob that I am, I retired to manualy root my phone (the one I have the unlock code) using the update.zip file found in the sticky noob guideline.that one somehow re-locked my phone but I had the unlock codes so out was no problem. That's why I'm paranoid now about the phone relocking itself and I won't have the unlock codes.
Your right about it not asking for the unlock codes after rom and kernel updates.I'm hoping the situation where I re-locked the phone is a special, rare, and unique case. I'm going for some confirmation on this.
Hello everyone. I am new to the world of android, but I'm a quick enough learner. Here is my specific problem:
I have an AT&T Atrix 4g. It is currently superuser rooted. It is currently running Android ROM 2.3.4.
Shortly after rooting the device, I downloaded ROM Manager and successfully installed through the application Clockwork Recovery. I tried to select the option to back up the current ROM (the stock android) on my SD card.. however, during the load screen, I got an error message stating
"Failed to boot 2
Starting RSD protocol support"
So doing some research, I came upon the conclusion that the reason I can't backup or really do anything with ROMs is that I needed an unlocked bootloader.
I went to Atrix4ghacks and followed the instructions on how to unlock bootloader and install permanent recovery.
This is the critical part: When I entered into the command prompt "fastboot oem unlock", instead of proceeding normally I got the return message:
"OEM unlock is not implemented"
Again, did a google search and read that Android 2.3.4 on Atrix 4g does NOT allow unlocked bootloaders.
So, the questions that I have that result from this are:
1.) Can someone here confirm that, in fact, I am unable to unlock the bootloader on my phone?
2.) If so, is there a viable workaround that is both reasonably safe and not overly complicated? Please note that I have no backup in case something goes wrong, leading me to
3.) Is there a way to backup my stock 2.3.4 ROM without an unlocked bootloader?
4.) Can I revert safely to an older android version that supports unlocked bootloaders?
5.) Can you actually install new ROMs without an unlocked bootloader?
6.) Am I totally screwed?
HUGE THANKS to anyone who actually bothered reading this, and even more thanks to anyone who can answer/point me in the right direction. Much appreciated!!!
thats becouse u havent flashed yet the bootloader ill give a post related to this and esay way to do it
http://forum.xda-developers.com/showthread.php?t=1182871
and you CANT go back to 2.2 or 2.3 u can hard brick your phone
tufo430 said:
thats becouse u havent flashed yet the bootloader ill give a post related to this and esay way to do it
http://forum.xda-developers.com/showthread.php?t=1182871
and you CANT go back to 2.2 or 2.3 u can hard brick your phone
Click to expand...
Click to collapse
Thanks a ton for that link. I'm sorry to ask once again, but I'm very wary of possibly bricking my phone... so I must ask: Is your solution possible with 2.3.4? Or will the phone softbrick?
If you did the Over The Air (OTA) update to 2.3.4 then yes your phone will softbrick after flashing the bootloader. Re-enter fastboot and issue the unlock commands and everything will be fine when you reboot.
I've had a lot of trouble upgrading to KitKat. After attempting to flash different image files for stock recovery/boot/system, I found it impossible to completely unroot the phone using the instructions posted because the phone kept re-rooting itself. Finally, I S-offed, wrote superCID, used the Telus RUU, applied the OTA downloaded to the phone, changed the CID back to GLOBA001 (my carrier is WindMobile). And finally! I know I relocked and unlocked the bootloader somewhere in the process, but I can't quite remember when.
Now, before I even think of re-rooting the phone or installing a custom recovery, I'd like to create a backup of the stock boot, recovery, and system. I tried running
Code:
fastboot boot openrecovery-twrp-2.7.1.1-zaracl.img
using the special KitKat TWRP. There's a message about boot.img being downloaded successfully but the phone reboots to a black screen.
I know that TWRP 2.7.1.0 downloaded from their website worked fine on my phone before I ran the RUU . So I'm not sure that the new TWRP is incompatible with my phone.
If I wanted to use adb instead, I'd need to root the phone before being able to pull the stock recovery, boot, and system images using adb shell. If I have to resort to rooting, is there any way to do so without flashing a custom recovery first? If there is, I might be able to unroot the phone afterward and make it stick. (Delete the supersu apk and su binary, right?)
I remember that the first time my phone attempted to download and apply the OTA automatically, my phone wiped itself. It was a lot of hard work to get it back to a usable state, but it was my own fault for not having a proper backup. I'd like to avoid making that mistake again, and have a stock backup handy on my computer in case there are carrier updates for my phone in the future.
To re-iterate, possible to back up stock everything without root? If not, possible to root without installing custom recovery?
You can no longer boot into a custom recovery, you have to actually flash it.
As far as having the stock recovery and boot, those are actually inside the OTA so you can pull it from there.
Since you'll have the stock recovery already, you can flash TWRP and use that to backup boot and system.
When you need to go stock, just use TWRP to restore your backup and then manually flash the stock recovery.
Since you made the device S-OFF, I recommend that if you need to lock/unlock the bootloader that you use the commands in this thread versus using the htcdev method as that wipes the /data/preload/ folder (as part of its normal /data wipe) which includes a few stock apps.
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
EveKnight75 said:
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
Click to expand...
Click to collapse
Locking the bootloader won't do anything, it's only unlocking using the htcdev token that causes the data wipe. So if you haven't unlocked using the htcdev method since running the RUU you will still have the 2 - 3 apps.
I don't know if the /data/preload/ folder is a requirement for a successful OTA update or not but I checked inside my OTA zip for my phone and it does include the 3 items stored there for the VM variant.
The unlock was AFTER the RUU. I ran the RUU, then used the OTA to upgrade to KitKat, then unlocked the bootloader again. However, I didn't notice any apps disappearing and the OTA zip for Wind also has a /data/preload folder.
*Shrugs* Seems good enough to me. TWRP, here I come!
needing wind stock stuck with wind awsy amd wont connect
I have an unlocked desire 601 it finds only wind away I'm trying to get a backup of the stock Rom to flash it does anyone k ow if there any around or even a back up I can use to try to get my phone working on wind home
jayjsteez said:
I have an unlocked desire 601 it finds only wind away I'm trying to get a backup of the stock Rom to flash it does anyone k ow if there any around or even a back up I can use to try to get my phone working on wind home
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2804427
needing help for s-off
EveKnight75 said:
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
Click to expand...
Click to collapse
hey i have unlocked desire 601 but only says wind away and wont connect ive knoticed the wind version is the same as the other versions but im wondering do i need the wind rom in order for it to pick up the wind home i cant seem to find anywhere online the wind rom and everytime i try to s-off it saysfailed and ive followed everything is there any insite you could give me to help me with this issue if its fixable again my phone says wind away but wont connect to it and i need to get it working as its my only device and carrier i use thx
---------- Post added at 11:29 PM ---------- Previous post was at 11:16 PM ----------
EveKnight75 said:
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
Click to expand...
Click to collapse
hey i have unlocked desire 601 but only says wind away and wont connect ive knoticed the wind version is the same as the other versions but im wondering do i need the wind rom in order for it to pick up the wind home i cant seem to find anywhere online the wind rom and everytime i try to s-off it saysfailed and ive followed everything is there any insite you could give me to help me with this issue if its fixable again my phone says wind away but wont connect to it and i need to get it working as its my only device and carrier i use thx
-Duir- said:
You can no longer boot into a custom recovery, you have to actually flash it.
As far as having the stock recovery and boot, those are actually inside the OTA so you can pull it from there.
Since you'll have the stock recovery already, you can flash TWRP and use that to backup boot and system.
When you need to go stock, just use TWRP to restore your backup and then manually flash the stock recovery.
Since you made the device S-OFF, I recommend that if you need to lock/unlock the bootloader that you use the commands in this thread versus using the htcdev method as that wipes the /data/preload/ folder (as part of its normal /data wipe) which includes a few stock apps.
Click to expand...
Click to collapse
I don't understand how you can pull the stock recovery from the OTA. I thought OTA's are immediately installed, instead of stored untill you want to install it? So, how do you backup the stock recovery?
It is saved until you want to install. When it go finishes Downloading, just choose install later. And you will be able to copy it into other storage devices and extract files and what not. I'm not sure if it stores in internal or external I'm 80% sure external sd if you have one.
Sent from my HTC0P4E1 using XDA Free mobile app
just wanted to say i had been running my verizon note 3 (non-dev edition) like everyone else here
with the bl unlocked to dev edition and rooted most likely with either kingo or supersu through teamyemin or proyemin and i think there is another one too.
basically if you want to go back 100% original (including your original cid) its not as easy as you might think.
first thing i did was wipe everything that was possible to wipe from within twrp recovery.
next i booted to odin download mode
from there i flashed the OB6 official firmware
then i rooted using the kingo method as this seemed the most likely not to infect my computer and possibly only stole info from my phone. (this used the 2 files 1.tar and 2.tar flashed with odin for pc)
i then verified my root and installed terminal emulator end es file explorer root
i copied samsung_cid to phone sd card and used es file explorer root to move to ./data/local/tmp
changed my cid back to original and rebooted phone
booted to stock recovery and wiped everything i could and booted into odin download mode
flashed OF1 official
there is a very important part that could get alot of ppl phones into brick mode.
when you goto change the cid back to original you better already have the stock BL on and running and >>>NOT<<< the DEV-BL
that is why i chose to flash an official OB6 rom first
if you try to change the cid to original non-dev edition and reboot your phone this could have problems since you would have the dev bl flashed with a non dev bl cid
when the cid for the dev edition became available you could change the cid first and boot into the bl and it would say something like developer mode enabled or someting like that even if you had the stock bl flashed (not the dev bl)
this is fine
only problem is if you change that cid back to stock/original non-dev while you are running the dev bl
i dont know what would happen but i bet it wouldnt be good.
ok next part i think is important is getting rid of kingo root as much as possible and that is why i flashed the OB6 firmware first and then OF1 for my very last step.
ok thanks.
i know alot of ppl are probably gonna say why would you want to go back to stock original cid and my answer is this.
phone is really stable and also if i want to sell it which im thinking about.
hope it helped some ppl.
Where do we get our original Cid?
The method used to do the unlocking runs the tool in two passes, like this:
pass1: change the CID.
pass2: (create debrick image &) alter the aboot partition sig to the DevEd sig.
There is no reason this can not be reversed (assuming you have root on ANY ROM) e.g. :
pass_negative_2: flash stock aboot to aboot partition.**
pass_negative_1: revert the CID by altering the original code to write your CID (minor code change and recompile).
** must be from the exact same version of boot firmware you have on the phone; you could use "dd" for this.
There's no reports of people trying this explicitly, but OTOH note this: there were owners of DevEd devices that accidentally flashed stock bootloaders. They didn't change their CID, and they didn't brick. They just couldn't go back to an unlocked bootloader any longer, or boot custom kernels: they converted their phones to retail without ever changing their CID.
Anyhow, it appears that you went through a ton of effort, when all you needed to do was flash the stock "aboot" back into place.
It probably isn't even necessary to revert the CID back.
ExpialZLD said:
Where do we get our original Cid?
Click to expand...
Click to collapse
You recorded it - as a precaution - when you went through the unlocking process. Didn't you?
As I mentioned above, it probably doesn't matter anyway.
@OP: did your "Custom" boot logo disappear eventually?
PS even after doing this the phone will still have a blown knox warranty flag and certain TZ/qseecom functionality will no longer work, even with 100% pure stock on the phone.
bftb0 said:
The method used to do the unlocking runs the tool in two passes, like this:
pass1: change the CID.
pass2: (create debrick image &) alter the aboot partition sig to the DevEd sig.
There is no reason this can not be reversed (assuming you have root on ANY ROM) e.g. :
pass_negative_2: flash stock aboot to aboot partition.**
pass_negative_1: revert the CID by altering the original code to write your CID (minor code change and recompile).
** must be from the exact same version of boot firmware you have on the phone; you could use "dd" for this.
There's no reports of people trying this explicitly, but OTOH note this: there were owners of DevEd devices that accidentally flashed stock bootloaders. They didn't change their CID, and they didn't brick. They just couldn't go back to an unlocked bootloader any longer, or boot custom kernels: they converted their phones to retail without ever changing their CID.
Anyhow, it appears that you went through a ton of effort, when all you needed to do was flash the stock "aboot" back into place.
It probably isn't even necessary to revert the CID back.
You recorded it - as a precaution - when you went through the unlocking process. Didn't you?
As I mentioned above, it probably doesn't matter anyway.
@OP: did your "Custom" boot logo disappear eventually?
PS even after doing this the phone will still have a blown knox warranty flag and certain TZ/qseecom functionality will no longer work, even with 100% pure stock on the phone.
Click to expand...
Click to collapse
Does by record do you mean by using a tool or like taking a picture of the cid
ExpialZLD said:
Does by record do you mean by using a tool or like taking a picture of the cid
Click to expand...
Click to collapse
Cut-n-paste to a text file.
The tool spews out onto the screen the device's CID before it goes about changing it.
That assumes you followed the directions in the OP and used ADB. Or, didn't follow those instructions and used a terminal emulator. (I don't know whether or not the app shows you the output from the binary).
As I mentioned, folks that had DevEd devices (that is, "factory unlocked" bootloaders) that made the mistake of flashing stock firmware turned their DevEd phones into retail phones - without ever changing the CID to some other value. So it may not even matter - you end up with a "retail" phone with the same CID that you currently have.
In any event, if you didn't record the previous CID, there's nothing to do about it.
The OP mentions something called "samsung_cid". I presume he is talking about a mod of the original code that allows you to re-write the CID to an arbitrary value.
I am a complete noob. Never rooted any device. The only reason I'm doing this is my kid wants to do gps spoofing on pokemon go. I've been doing research for a couple of days now. There are many tutorials but all are slightly different.
The reddit page called the number 1 hub for pokemon go spoofing says what I need to do is....
Unlock Bootloader.
Install Magisk.
Install Smali Patcher.
This has proven to be more difficult that I first assumed. So far I have unlocked bootloader but I made a mistake because the first few tutorials I followed said nothing about backing up DRM keys or TA keys. So I guess I have lost that option.
Now I'm trying to install Magisk but apparently I need to do this through TWRP.
So trying to install TWRP. Found the right one for my device on TWRP official website says something about extracting stock boot image and patching but can't find any tutorials on how to do this.
Any help from this point will be much appreciated!
I'm starting to question is any of this actually worth it. If I new it was going to be this difficult before I started I don't think I would of bothered. If I was to change my mind is there a way can restore the tablet to its original state. I've read up a bit about relocking the bootloader but does that mean I've lost DRM keys and TA keys for nothing.(Is that even that big of a deal. Will my tablet not perform as it should without them?) I've read a little about Sony Emma or using the Sony companion to restore the tablet. Does that mean I get the DRM or TA keys back?
Ok so I was unsure if I unlocked the bootloader properly. My dialler app has disappeared so can't check it that way. Trying to check through cmd on minimal adb and fastboot but it just hangs when I type fastboot oem device-info. So I installed sony companion and tried software repair and it said it cant repair as the bootloader has been unlocked.
So that confirms it has definitely been unlocked. Will there be a problem If I Relock and try software repair again?
Ok so I got eager and thought f it. I'm just gonna do it. So I got the twrp.img file, put it in the adb and fastboot folder, in cmd wrote fastboot flash recovery TWRP.img. It looked like everything went ok. I'm pretty sure it said successful. So I'm now trying to boot into recovery mode. Holding down and power on and nothing is happening. Just boots up normally. What am I missing.
I downloaded the twrp app from appstore messed around with a bit and its needs root device not rooted. Did I not do the flash right?
Can I use flashtool to flash twrp.img instead of adb and fastboot?