Ok here is the background as I already had S-OFF with eng bootloader months ago. Now I want to switch to diff carrier so I try the gfree meth for sim unlock. At first the gfree didn't work at all as I got eMMc fail no file found. The gfree was still located in /data/local with permission changed to 777. As I couldn't run it from Terminal I reverted back to clean stock rom and I was able to run it this time but the flag did not stick to CID-11111111 as its still CID-T-MOB010. As I also flashed to new radio I reverted back to the old stock radio. This time running gfree gives me reboot everytime right after the script is finish loading.
Now I have 3 part7backup-xxxxxxxxx.bin files with same checksum. But the CID itself did not stick for some reason and after radio flash rest of the part7backup-xxxxxxxxx.bin were empty as it was never written in SDCard as it never got chance beacuse it rebooted soon after it finished. Does anyone have any idea? How do I check if the security flag is off for the radio? At this point I am not even sure if it worked at all. I should have just called TMo and got the unlock code as its free.
Hmmm starting to think it was a mistake trying to do the gfree meth to begin with as it seems its POS meth. I try to revert back with "dd=/ of=/" command and **** just rebooted so I am not even sure if it reverted back. Forget reverting I am not sure it worked in first place begin with. Ill try reverting back to the newest radio which I used when I got this backup and see what happens.
UPDATE: Well since it was all epic fail and I didn't get to unlock the sim since it still said CID-T-MOB010 when after gfree should have been CID-11111111.
Now as I was reverting back I did notice few things which I am posting here so others can get clear idea. If the simunlock does not work for you and you trying to revert back make sure you use same settings.
1) Using AOSP2.3.4 I was unable to use gfree from terminal as it gave me eMMc fail files can't be found error.
2) So I reverted back to my stock rom (my clean unbolted backup).
3) I was able to successfully execute the gfree from terminal and part7backup-xxxxxxxxx.bin was created in SDCard.
4) As proof I went in HBoot and checked under system info the CID flag still remained CID-T-MOB010 when it should have been CID-11111111.
5) As it didn't work I ran it 2 more times to check if the CID flag would stick which it didn't. Which created 2 more part7backup's in SDCard.
6) Now thinking that it maybe radio related I reverted to stock radio from current new radio though bootloader using PD15IMG.zip radio update.
7) Again tried the gfree from terminal but this time soon after it was executed I got reboot when it finished. New part7backup was created but empty as it was never fully written. I tested it few times same result.
8) So I try to revert back to original state using the first original part7backup-xxxxxxxxx.bin file using dd if=/ of=/ command. Which gave me same result as it never finished and rebooted.
9) I tried it twice and gave me same result. So thinking this could just simply be protected block thus unable to write to I manually remounted the /dev/block/mmcblk0p7 as rw and then redid the dd if=/ of=/ and gave me same result.
10) Reverted back to the new radio(original radio) that I used when the part7backup was created and gave me same result.
11) Restored to AOSP2.3.4 backup I had and then redid the dd if=/ of=/ command again and this time it worked.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So IDK what happened but I was unable to get simunlock also not sure if the radio security was ever disabled as I couldn't verify the simlock. It maybe easy/safe for people to just request the unlock code from TMobile by giving your IEMI and they will send you in 2-3days in email.
You could have just run gfree again with the option --CID 11111111. I've had to do that once and it worked just fine. The only way I know to check the security in the radio is with a script grankin wrote. PM him and ask, he'll probably give it to you with instructions.
jdkoren said:
You could have just run gfree again with the option --CID 11111111. I've had to do that once and it worked just fine. The only way I know to check the security in the radio is with a script grankin wrote. PM him and ask, he'll probably give it to you with instructions.
Click to expand...
Click to collapse
:O someone responded, thank you. Thought people were just ignoring this as it was over their head. I ran each command myself with --CID 11111111. Along with --secu_flag off. After the first attempt where the CID didn't stick and showed as CID-T-MOB010. After the stock radio flash I was not able to do anything as after any gfree run it just rebooted and empty backup7part-xxxxxxxxx.bin was created. I mean only way to check if it worked other than CID was to push the stock bootloader and check if the HBoot still said S-OFF. Now I don't feel comfortable with a half rom and radio as it can mean death any min. Thank god I didn't or I would be really stuck now as it would be in bootloop. Ill be stuck with it unless I did the total PD15IMG rom/radio roll.
Related
Hi all,
Here's short history of the phone:
Friend of mine drop his on the concrete about June of last year and whole screen was cracked (not pretty). About month ago I found LCD Screen with Digitizer on ebay bought it and replaced it.
After turning it on everything was working except random reboots. Phone was not registered to any account so there was no internet only WI-FI.
So I started going into system updates and downloading HTC updates it did two of them and I think on the 3rd one it just starts to boot white HTC EVO 4G screen comes on and then it reboots.
Only pulling the battery will stop it.
This is all on stock HTC Sense ROM, rooting was never attempted!
I've searched thru the forums here but everything here relates to failed rooting process.
Can someone please make any suggestions?
Bellow is the pictures of boot loader.
Help is greatly appreciated!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
These directions are for un-rooting, but should fix your phone:
http://forum.androidcentral.com/htc...19278-how-unroot-return-stock-ruu-method.html
Fazulka said:
These directions are for un-rooting, but should fix your phone:
http://forum.androidcentral.com/htc...19278-how-unroot-return-stock-ruu-method.html
Click to expand...
Click to collapse
Thank you!
Followed the instruction, run RUU and it starts to check the phone after this I get error[170]: USB connection error.
I've tried over 10 times.
Step 4 says "Make sure USB debugging is enabled on your phone."
I can't even log into Sense?
The only other thing you can do is find a PC36IMG.zip and put it on your microSD card, then reboot into the bootloader. It should find it and reflash everything, the same as using the RUU.
ffolkes said:
The only other thing you can do is find a PC36IMG.zip and put it on your microSD card, then reboot into the bootloader. It should find it and reflash everything, the same as using the RUU.
Click to expand...
Click to collapse
I've tried using this method found here
I placed PC36IMG.zip in root of the SD card. But when I boot into recovery I can see for about 3 seconds on the right side status bar how it checks PC36IMG.zip file but then it goes back to recovery. It never ask me if I want to update like it says in the above tutorial "Do you want to start update?"
Any other suggestions?
JohnnyBeGood113 said:
I've tried using this method found here
I placed PC36IMG.zip in root of the SD card. But when I boot into recovery I can see for about 3 seconds on the right side status bar how it checks PC36IMG.zip file but then it goes back to recovery. It never ask me if I want to update like it says in the above tutorial "Do you want to start update?"
Any other suggestions?
Click to expand...
Click to collapse
I had to unroot mine and I found that u have to have the right pc36img file. If you dont know what ver rom was running then you may need to try them all. But I had the same problem it just wouldent install the file. Keep trying and if you need help finding them Ill help ya.
I found this but its not the same place I got mine from. http://www.filecrop.com/htc-evo-4g-roms.html
Thanks for the reply!
Somewhat of a progress. I tried countless times and it always gives me USB connection error: Then I downloaded HTC Sync and and I think I went to Hboot and I heard sound on windows it seemed like phone got recognized and I was able to finish the processes. It was flashed using RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed. Then when I went to again in recovery it was again red triangle over the phone.
After that I just let it try to boot and it finally booted into HTC sense!
Turned on WI-FI and wanted to check if there's any updates and it said no updates?
This is what recoveries I've tried so far:
Amon RA 2.1.1
Amon RA 2.2.1
Amon RA 2.3 (Added 02/09/2011)
Stock Recovery 3.26.651.6 (Added 01/18/2011)
Stock Recovery 3.29.651.5 (Added 01/18/2011)
Stock Recovery 3.30.651.3 (Added 01/18/2011)
Stock Recovery 3.70.651.1 (Added 01/18/2011)
One by one I tried each one renaming to PC36IMG.zip and none of them asked me if I want to do the update. It just checks it and goes back to bootloader.
Why do I get red triangle?
What should I do now?
Help is appreciated!
I've spent quite a while tonight FINALLY getting this MyTouch 4g (Glacier) to root and now I'm stuck in a bind.
Everything seemed to be going well and I got the Cyanogenmod 7 flashed onto the phone via Clockwork ROM Manager. Then the first time I rebooted it got to the Android logo with the spinning arrow and went into a constant loop. After about 20 minutes of this I pulled the battery and tried to restore the phone via the recovery image I created with clockwork. Here is the current status of the phone:
1. CAN get into HBOOT and HBOOT USB (but I dont think ADB can see it, or at least I haven't been able to get it to)
2. CANNOT get into recovery, phone just reboots itself to the red exclamation
3. PD15IMG.zip tries to restore the phone but fails.
What can I do to get the phone back into some sort of usable condition. I dont care where, I can start over as long as I have something to work with.
sdavidson0316 said:
I've spent quite a while tonight FINALLY getting this MyTouch 4g (Glacier) to root and now I'm stuck in a bind.
Everything seemed to be going well and I got the Cyanogenmod 7 flashed onto the phone via Clockwork ROM Manager. Then the first time I rebooted it got to the Android logo with the spinning arrow and went into a constant loop. After about 20 minutes of this I pulled the battery and tried to restore the phone via the recovery image I created with clockwork. Here is the current status of the phone:
1. CAN get into HBOOT and HBOOT USB (but I dont think ADB can see it, or at least I haven't been able to get it to)
2. CANNOT get into recovery, phone just reboots itself to the red exclamation
3. PD15IMG.zip tries to restore the phone but fails.
What can I do to get the phone back into some sort of usable condition. I dont care where, I can start over as long as I have something to work with.
Click to expand...
Click to collapse
does bootloader show Fail-PU when flashing PD15IMG.zip?
saranhai said:
does bootloader show Fail-PU when flashing PD15IMG.zip?
Click to expand...
Click to collapse
Nope, looks to me like the equivalent of what you're asking is that it says "Fail UZ"
I've attached a few screen shots for reference.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
sdavidson0316 said:
Nope, looks to me like the equivalent of what you're asking is that it says "Fail UZ"
I've attached a few screen shots for reference.
Click to expand...
Click to collapse
It failed to unzip the update. Try redownloading the pd15img. This time verify the MD5SUM and try it again.
ALrighty.....this is my st00pid face. I guess in my lack of sleep last night I forgot to check the MD5SUM.
That worked....now let's see if I can break it again!!
sdavidson0316 said:
ALrighty.....this is my st00pid face. I guess in my lack of sleep last night I forgot to check the MD5SUM.
That worked....now let's see if I can break it again!!
Click to expand...
Click to collapse
Cool Glad it worked for you.
New question, essentially the same topic:
This whole thing started because I tried to flash CyanogenMod 7 onto the phone and it messed up. The phone reboots into Cyanogen and the little android on the skateboard with the arrow just goes into a repeating cycle. It will come on for 10ish seconds at a time and then just cycle back and do the same thing. I've let it go for >20 minutes and nothing changes.
Does anyone have any suggestions on how to get this ROM working? It took me so long to get it rooted with S-off that I'll be darned if I'm stopping now!
Thanks in advance!
sdavidson0316 said:
New question, essentially the same topic:
This whole thing started because I tried to flash CyanogenMod 7 onto the phone and it messed up. The phone reboots into Cyanogen and the little android on the skateboard with the arrow just goes into a repeating cycle. It will come on for 10ish seconds at a time and then just cycle back and do the same thing. I've let it go for >20 minutes and nothing changes.
Does anyone have any suggestions on how to get this ROM working? It took me so long to get it rooted with S-off that I'll be darned if I'm stopping now!
Thanks in advance!
Click to expand...
Click to collapse
Verify the MD5SUM of the ROM as well. You may of gotten a bad download.
What i personally do when i download and install a new OS is
Download OS to computer
push the OS to the SD card
verify the MD5SUM
reboot into recovery
nandroid backup
factory reset
flash new OS
flash g/apps (if needed)
reboot system
to check the MD5SUM while it's on the SDcard just use the line command from either the terminal emulator or CMD prompt.
Code:
# md5sum /mnt/sdcard/<file_name>.extension
neidlinger said:
Verify the MD5SUM of the ROM as well. You may of gotten a bad download.
What i personally do when i download and install a new OS is
Download OS to computer
push the OS to the SD card
verify the MD5SUM
reboot into recovery
nandroid backup
factory reset
flash new OS
flash g/apps (if needed)
reboot system
to check the MD5SUM while it's on the SDcard just use the line command from either the terminal emulator or CMD prompt.
Code:
# md5sum /mnt/sdcard/<file_name>.extension
Click to expand...
Click to collapse
+1
You can also check the md5 sum when its on the SDcard using the free mand5 app from the market.
Sent from my HTC Glacier Sense 3.0 using xda premium
Thanks to everyone for helping out, I finally got it working last night when I had time to sit back down with it.
I was trying to use the ROM Manager version of the Cyanogen instructions and it ended up that that was the problem. I switched over to the recovery version based on your suggestions and it worked great.
Thanks again!
General feeling around here is that the only thing ROM Manager is good for is flashing ClockworkMod recovery. There are folks who won't even do that with it.
Sent from my HTC Glacier using XDA App
ROM manager ruined my recovery I had to completely re push recovery thru adb
Sent from my PG86100 using xda premium
Okay, so I was on the Stock 2.3.4 GB rooted rom, I tried to flash Android Revolution but somehow I downloaded the Sensation one and tried to flash and it gave error Status 7 (4EXT).. So, I went back to stock 2.2.1 and perm-rooted and my S if still off, so I flashed recovery and tried to flash Runny Mede, it dosen't dare to pass the MyTouch 4G logo, and just starts a boot loop right there. Please help, I want to enjoy other roms just like you guys too! Also, everytime I mount my phone as a Disk Drive, windows asks me to Scan for errors, I do it (with both options checked) and it just immediately closes and goes into the root of my SD.. Please help me.
Make sure when flashing a new rom to wipe data/cache. I'd recommend wiping system too, just to make sure you don't run into other issues.
This comes from memory only, (Anyone- don't hesitate to correct me if I'm wrong) and I couldn't find any info about it to confirm, but I believe Status 7 simply means the installation of the zip file you attempted to flash was aborted, i.e. nothing was flashed. Many ROMs have checks in them to confirm you're flashing to the correct device, and if not, will refuse to proceed, and this may be what you encountered.
As for Windows asking you to scan for errors, this happens any time you disconnect your phone or unmount it without safely ejecting via Windows. It's unlikely you would actually have any disk problems or corruption unless you disconnected or unmounted while files were still being transferred or edited. Safely unmounting would be considered the best practice. When you're ready to disconnect your phone from your computer, or to unmount the SD card from Windows, look for an icon like this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click it and choose your device to safely remove it from your computer.
Going back to froyo and "re-rootong" was a complete waste of time.
Status 7 would indeed mean nothing was flashed (nice post by the way, to the guy above me).
All you needed to do was wipe system, data and cache a flash the correct ROM. Alternatively, you could have restored the backup that you should have made before you tried flashing ARHD.
Try holding Vol down at boot to get to bootloader. Once there select Recovery. That will get you on the right path. Remove PD15IMG from the root of your SD before you do this.
Edit: I just remembered that your recovery is stock if you flashed PD15IMG. You will need to flash a recovery.img with adb. The steps are in the clockworkmod thread that is stickied in the dev section. There used to be a PD15IMG of an older 4EXT recovery floating around. You might try locating that.
crawler9 said:
Make sure when flashing a new rom to wipe data/cache. I'd recommend wiping system too, just to make sure you don't run into other issues.
This comes from memory only, (Anyone- don't hesitate to correct me if I'm wrong) and I couldn't find any info about it to confirm, but I believe Status 7 simply means the installation of the zip file you attempted to flash was aborted, i.e. nothing was flashed. Many ROMs have checks in them to confirm you're flashing to the correct device, and if not, will refuse to proceed, and this may be what you encountered.
As for Windows asking you to scan for errors, this happens any time you disconnect your phone or unmount it without safely ejecting via Windows. It's unlikely you would actually have any disk problems or corruption unless you disconnected or unmounted while files were still being transferred or edited. Safely unmounting would be considered the best practice. When you're ready to disconnect your phone from your computer, or to unmount the SD card from Windows, look for an icon like this.
Click it and choose your device to safely remove it from your computer.
Click to expand...
Click to collapse
estallings15 said:
Going back to froyo and "re-rootong" was a complete waste of time.
Status 7 would indeed mean nothing was flashed (nice post by the way, to the guy above me).
All you needed to do was wipe system, data and cache a flash the correct ROM. Alternatively, you could have restored the backup that you should have made before you tried flashing ARHD.
Try holding Vol down at boot to get to bootloader. Once there select Recovery. That will get you on the right path. Remove PD15IMG from the root of your SD before you do this.
Edit: I just remembered that your recovery is stock if you flashed PD15IMG. You will need to flash a recovery.img with adb. The steps are in the clockworkmod thread that is stickied in the dev section. There used to be a PD15IMG of an older 4EXT recovery floating around. You might try locating that.
Click to expand...
Click to collapse
Thanks to both of you, I tried flashing TRAD v1 and it worked, made a nandroid, just flashed virtuous Affinity maybe 2 minutes ago and its booting. I guess I just panicked a bit. c:
It's easy to do if you aren't used to flashing. Those minor heart attacks aren't fun, either.
Tell me about it. : )
GO GO GO!
Superboot is a boot.img that when booted, will root your device the first time you boot (installing su and the superuser APK). No need to flash any partitions, no messing with the contents of your data partition, no overwriting the shipped ROM on your device, just boot the boot image using the instructions below and you're done!
YOU NEED YOUR BOOTLOADER UNLOCKED TO CARRY OUT THIS PROCESS. It's easy using fastboot, which is included in the download below. The instructions on the Motorola site are very straightforward - visit this page to get started. Unlocking the bootloader will wipe your device.
This Superboot installs SuperSU version 1.80. Note that rooting may affect your ability to receive future OTAs, reverting back to stock is easy enough. We'll cross that bridge when we come to it.
Click to expand...
Click to collapse
Full Guide
http://www.modaco.com/topic/366771-superboot-moto-g-root-solution/ (Thanks to helinhof)
http://t.co/7icWLuTwSW (Thanks to munchy_cool)
"PaulOBrien 3h
Nobody has rooted the Moto G yet? Well that won't do will it. Superboot uploading now... pic.twitter.com/6B9qcA6kfs"
"Moto G root tool online soon. It's my usual process, a Superboot image..."
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://twitter.com/PaulOBrien
Greaatt.. wainting for this..
bgochoa said:
Greaatt.. wainting for this..
Click to expand...
Click to collapse
We are two!
Moto G - Rooted
Here we go guys!
http://www.modaco.com/topic/366771-superboot-moto-g-root-solution/
its a go http://t.co/7icWLuTwSW
http://www.modaco.com/topic/366771-superboot-moto-g-root-solution/
Nice one...I´ve been waiting for this...the process took less than 10secs. Thanks!
Does it works in the german version?
FighterFX said:
Does it works in the german version?
Click to expand...
Click to collapse
It worked for me on my German Retail Moto G.
alex1301 said:
It worked for me on my German Retail Moto G.
Click to expand...
Click to collapse
Mine too, 14.71.8.Retail.en.DE
has anyone got this to work with the tesco version?
so how much space is there for system and for the apps
on 8 gb version
Props and thanks to [email protected], i can now consider buying this phone
i have a problem .... mmy cel is unblock but no rooting u.u
Rooted successfully, but I can't encrypt my phone now; it says "Encryption unsuccessful" and offers to erase everything. I reboot the phone instead without erasing and it boots normally.
Any ideas on how to solve it? It's kind of critical, since i can't use my email without encryption
can confirm that this is working, done in under a minute
burma said:
Rooted successfully, but I can't encrypt my phone now; it says "Encryption unsuccessful" and offers to erase everything. I reboot the phone instead without erasing and it boots normally.
Any ideas on how to solve it? It's kind of critical, since i can't use my email without encryption
Click to expand...
Click to collapse
I was able to get it working only after reflashing stock http://forum.xda-developers.com/showthread.php?t=2542219&page=3 then encrypting and then reflashing superboot.
So maybe it is worth updating instructions:
1) Unlock bootloader (wiping all data)
2) Encrypt your phone
3) Flash superboot
Thanks! only a question... If i unlock the bootloader and root the moto g, will I still receive the kitkat OTA update?
still not rooting
unlocked the boot loader, tried to root with super boot, but didnt work, flashed to generic uk, tried to root again and it still wont say rooted or show the su app, please can someone help?!
Rooted...wireless tether working with wifi router app. However, I got notified of 4.4 update today and it downloads, starts install, then fails.
I read through the similar thread from yesterday, but this is a different issue...
I had unlocked, installed TWRP, and had been running a custom ROM (BadBoyz 1.2). This morning I re-locked so I could flash the updated firmware (v1.80) and now I am unable to re-unlock.
When I issue the command fastboot flash unlocktoken Unlock_code.bin, it works without errors, and the phone goes to the "Are you sure you want to unlock your bootloader?" screen.
However, at that screen, the volume buttons do nothing. I can't select yes OR no, it just sits there. Eventually it times out and just shows the battery charging on a black screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I flashed the firmware, it removed TWRP, and with a locked bootloader, I can't re-flash it.
I was able to get a fully stock rom up and running, so I'm not in brickville anymore (had a few hours of panic earlier today), and I've been able to confirm that the OEM Unlock option is checked. I've even unchecked and re-checked to be sure. Everything works except the ability to confirm my choice and move on. I'm kind of afraid that it's a glitch in the new firmware, at this point...
Anyone got any ideas?
Thanks!!
deleted
So, it removed TWRP and replaced the stock recovery? And now you can't reinstall TWRP because bootloader is locked? Is that where you're at?
Sent from my 2PS64 using XDA-Developers mobile app
have you tried running RUU.exe? i took that route and was able to unlock my bootloader again, flash twrp and upgrade to bb 2.0 with no problems
I had the same problem and had to flash a stock rom back on the phone before the unlocker would work.
I figured it out! I can't explain WHY it worked, but it worked...
I had re-flashed several times using the official RUU, and the results never changed...
Then yesterday I went through a mental checklist of what was different when I unlocked the first time... and the only thing, was that I hadn't put my SD Card in the phone yet when I unlocked the first time. So I went through the motions again to verify that it still didn't work, and it didn't. Then I ejected the SD Card and tried it - and BOOM, I was able to unlock!
The only thing I can think of is that the SD Card did have the Firmware .zip on it, which the phone auto-detected and asked if I wanted to install... even though I said no. As soon as I tried it without the card, it worked like it always had, I'm back to unlocked, and back to the custom ROM I had been enjoying so much...
Thanks for the tips, everyone, and I hope this thread helps someone else who finds themselves in the same boat!
scottspa74 said:
So, it removed TWRP and replaced the stock recovery? And now you can't reinstall TWRP because bootloader is locked? Is that where you're at?
Sent from my 2PS64 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, that is EXACTLY where I was at. However, finally found the way out of the mess.. (see above post)