Alright, so I've got my TFP rooted and went to use the unlock tool via ViperMOD, which worked like a charm except for the fact that it wouldn't install CWM. Did as previous posts suggested and went with a factory reset through Settings, and now I'm back to square one.
Since I did a factory reset, is my bootloader still unlocked? I'm still rooted, but that's beside the point. Is there any way for me to check if my bootloader is unlocked?
I'll answer your question but I want you to answer one of mine. My understanding is that it will say that the boot loader is unlocked while booting and there is no"re-locking".
I haven't been able to unlock my bootloader with the app from the vipermod or downloaded directly from Asus. I've been trying for about 2 weeks I reflashed .15 and reupgraded, reflashed. 21. Did a number of factory resets, attempting to unlock between each step. How did you make it work?
I actually just picked another TFP up recently, this one for the lady, so it came with .15 already. From there, I just rooted then used viperMOD to install the Unlock Tool. Are you getting the "network connection" error?
Got impatient and D/L'd ROMManager, then flashed CWM without any problems. Guess I'm still unlocked ;p
Yea, network connection error
I was getting that for a while, but that was a week ago now or so. I'm guessing it's a problem on their side (hopefully servers are down for maintainance? >.<).
Related
Hey all,
I'm fairly new to unlocking/rooting (I'm from the simple iPhone jailbreak world).
I have my Atrix 4G rooted with no issues and ClockworkMod installed... that was the easy part it seems.
Where I am struggling is to figure out IF I can unlock my Atrix 4G and if it is safe to do.
I am running Android 2.3.6 on the Bell network. I see a bunch on unlocks for bootloader 2.3.4 and am confisued if that bootloader version has any relation to the android version? How can I figure out what bootloader I have? Would it also be 2.3.6?
If it is indeed 2.3.6, is it possible to unlock, I see no specific unlocks for that version.
Thanks,
You cant install a different recovery with out being unlocked. so if you can boot into CWM then your phone is already unlocked.
Where did you get the phone? was it new?
Its possible if its used that it was already unlocked and someone RSD back to stock for sale purpose, if its new and you havent unlocked yet then you dont have CWM installed.
Random Canadian said:
You cant install a different recovery with out being unlocked. so if you can boot into CWM then your phone is already unlocked.
Where did you get the phone? was it new?
Its possible if its used that it was already unlocked and someone RSD back to stock for sale purpose, if its new and you havent unlocked yet then you dont have CWM installed.
Click to expand...
Click to collapse
Sorry should have been a little more clear, I have installed ROM Manager and choose the CWM install, but I cannot boot into it, I get a boot error 2 (I think). Sorry phone is at home now so I can't recall exact error will post later.
I got phone 6 month ago, was used phone. I am fairly certain its not unlocked because I cannot boot with CWM, hence cannot install custom ROM.
Thanks for the reply.
Random Canadian said:
You cant install a different recovery with out being unlocked. so if you can boot into CWM then your phone is already unlocked.
Where did you get the phone? was it new?
Its possible if its used that it was already unlocked and someone RSD back to stock for sale purpose, if its new and you havent unlocked yet then you dont have CWM installed.
Click to expand...
Click to collapse
You don't need to be unlocked to have CWM on your Atrix. I had it on at least 1.83 if not the original stock firmware. I know it was possible with only root on 1.83 because that was what I was running up until a month ago and I had CWM on it with a locked bootloader.
cerps said:
You don't need to be unlocked to have CWM on your Atrix. I had it on at least 1.83 if not the original stock firmware. I know it was possible with only root on 1.83 because that was what I was running up until a month ago and I had CWM on it with a locked bootloader.
Click to expand...
Click to collapse
Right, my phone is rooted so I have CWM, just can't boot it. My understanding is because I need to unlock, but I don't know how to unlock because I don't know how to figure out what bootloader I have.
cerps said:
You don't need to be unlocked to have CWM on your Atrix. I had it on at least 1.83 if not the original stock firmware. I know it was possible with only root on 1.83 because that was what I was running up until a month ago and I had CWM on it with a locked bootloader.
Click to expand...
Click to collapse
Locked or it just didnt say unlocked at the top? two very different things.
avalanche333 said:
Right, my phone is rooted so I have CWM, just can't boot it. My understanding is because I need to unlock, but I don't know how to unlock because I don't know how to figure out what bootloader I have.
Click to expand...
Click to collapse
dur im pretty sure that unlocking the boot loader allows unsigned code to run at boot, I could be wrong but I think you two are out to lunch on installing CWM with just root.
That or you can install it but you cant run it because the boot loader wont allow something with out motorolas signature to execute. making the point of if it is or is not, installed, a moot one. Aside from the fact you no longer have any sort of a functional recovery mode.
There is a LOT of info on how to unlock the bootloader and its not exactly hidden. I dont know if its even still done with RSD but that would be a place to start as that is how I did mine in sept of last year.
Random Canadian said:
Locked or it just didnt say unlocked at the top? two very different things.
dur im pretty sure that unlocking the boot loader allows unsigned code to run at boot, I could be wrong but I think you two are out to lunch on installing CWM with just root.
That or you can install it but you cant run it because the boot loader wont allow something with out motorolas signature to execute. making the point of if it is or is not, installed, a moot one
There is a LOT of info on how to unlock the bootloader and its not exactly hidden. I dont know if its even still done with RSD but that would be a place to start as that is how I did mine in sept of last year.
Click to expand...
Click to collapse
Yes I see what your saying, but I am saying that I cannot run CWM. I can only install onto my SD card. But the boot in recovery does not work (ie it will not run CWM). I'll post the error little later tonight when I try at it again.
I realize there is lots of info on unlocking bootloader and I am not concerned about doing the unlock, once I find a way to verify my bootloader version. Ive seen a few posts warning that bootloader must be v 2.3.4 or you can brick the phone.
So I guess ultimately my question is, how can I figure out my bootloader version? Have not seem this answers after some googling.
http://forum.xda-developers.com/showthread.php?t=1136261
Read that and your version will be in settings and then about phone. although I do believe that 234 and 236 unlock via the same method.
If you are going to install Custom roms CM7/9/10 or a blur based then you dont need to even worry about root. otherwise there are instructions in that thread to root that SBF
Random Canadian said:
Locked or it just didnt say unlocked at the top? two very different things.
dur im pretty sure that unlocking the boot loader allows unsigned code to run at boot, I could be wrong but I think you two are out to lunch on installing CWM with just root.
That or you can install it but you cant run it because the boot loader wont allow something with out motorolas signature to execute. making the point of if it is or is not, installed, a moot one. Aside from the fact you no longer have any sort of a functional recovery mode.
There is a LOT of info on how to unlock the bootloader and its not exactly hidden. I dont know if its even still done with RSD but that would be a place to start as that is how I did mine in sept of last year.
Click to expand...
Click to collapse
I'm positive it was locked, running 1.83, and had CWM on it. I bought the phone at an AT&T store myself. I rooted it and put CWM on it. The early version of CWM for the Atrix only was accessible by turning the phone on while plugged into the wall charger that came with the phone.
Hey all,
I have previously unlocked my bootloader on my DNA and I came across a problem so I RUU back to stock after relocking my bootloader of course. Now i want to re unlock my bootloader and it keeps saying successful and it still shows "relocked" in my boot menu. I tried the steps from number 1 til finish and nothing. Is re unlocking the bootloader even possible? If it is can anyone help me please? I've searched and searched and cannot find anything on this issue on the Droid DNA.
Thanks in advance everyone
Bump
Sent from my HTC6435LVW using Tapatalk 2
Did you try re-using the old key you first got it unlocked with?
Yea i did, about 5 times. I even got a new one and still wont work
Sent from my HTC6435LVW using xda app-developers app
I'm in the same situation. I have tried the original unlock bin file i had from the first time and also went through the process of resubmitting and getting another one. Even reflashed
the ruu and trying to re-unlock from scratch. Everything went through like normal but my bootloader still says "relocked".
Try a factory reset, re locking bootloader again (do it no matter what the bootloader status is) Then install the RUU, then try unlocking bootloader again. Could just be a permissions error or something. If that doesn't work then maybe the bootloader in the RUU has different functionality and protection compared to the original one you were using.
Found this at Rootz : http://rootzwiki.com/topic/36898-stock-return-to-stock-1156054-for-verizon-htc-dna-re-unlock-device/. Read through the second page of posts. Worked the first time.
beasleyj62 said:
Found this at Rootz : http://rootzwiki.com/topic/36898-stock-return-to-stock-1156054-for-verizon-htc-dna-re-unlock-device/. Read through the second page of posts. Worked the first time.
Click to expand...
Click to collapse
Nice find
Trying to install cyanogen mod.
First I tried to s-off before unlocking the bootloader (which I later learned was a mistake).
I tried everything except facepalm in the following order: (moonshine, rumrunner, firewater).
For firewater I was able to root/temp root via Minimal ADB and Fastboot as well as Weaksauce.apk.
None of those worked, but thankfully none of them bricked the device, however there has been some problems since then.
When I realized I should have been trying to unlock the bootloader this whole time, I tried SuperCID.apk from the soure.zip found in the development sticky thread.
That also failed.
Details about the phone:
Motherboard replaced ~3 months ago.
HTC sent the phone back to me running software number 1.15.605.4 710RD (Android 4.1.1)
While attempting root/s-off/unlock bootloader the SIM was installed but the phone was not activated and was in airplane mode.
I do not have OEM cable however ADB recognizes the device being attached so I don't think that is an issue.
Problems that have developed:
Since tinkering around the boot times have extended dramatically with some funny behavior at initial startup.
The battery is draining noticeably quicker.
I factory reset the phone and booting has gotten a little smoother, no battery improvement.
Aside from those 2 problems the phone functions perfectly.
I'd really like to be rid of the stock rom and all of its bloat apps, so if there is another way to get a CM ROM I'd be damn happy.
Also, any information on what I may have funked up when trying moonshine/rumrunner/firewater would be greatly appreciated.
Did you ever figure this out? I have been unable to unlock my bootloader too.
Yes!
gabezermeno said:
Did you ever figure this out? I have been unable to unlock my bootloader too.
Click to expand...
Click to collapse
I was able to figure it out after HOURS or even days of confusion.
In my case the problem I was having, was using the incorrect unlock/s-off method for the my corresponding firmware.
I upgraded via Verizon updates from firmware 1.XX to 2.XX until I eventually got 3.6 (it took multiple updates to get there). Once I had 3.6 I used the RUMRUNNER method to unlock and s-off (it was quite easy once it I had adb and fastboot commands all figured out).
Good luck.
Hey everyone,
I'm in a bit of a pickle here. I was running Lollipop 5.0.2 with my phone rooted, unlocked, and had previously run ROM cleaner. I attempted to reset my phone since I'm planning on selling it, and now its screwed up. Immediately following the reset attempt, I got a screen saying Android updating, optimizing apps (and it ran through all the apps that i was attempting to delete). Then once the phone cycled and booted up, i got "Unfortunately system UI has stopped." Not exactly sure what to do. Heres a picture of my bootloader. Oh and I don't believe I had any backups created. Any help would be greatly appreciated.
reflash.
Relock the bootloader and RUU to (almost) full stock.
But you should still make the buyer aware the phone was at one point modded. It will say RELOCKED on the bootloader screen, instead of the factory condition which is LOCKED. Plus, HTC has a record of the bootloader being unlocked by HTCDev.com.
My 4 year old note 2 was rooted and unlocked by Adam Outlers Casual. Worked great forever. I uninstalled a program called "Autostarts", which I used to shut off programs after bootup, and the phone went into a boot loop. I could still get to the download mode so no biggie, First I downloaded RT66 via oden, which did not work, I found a vramc3 restore to stock that did not relock the bootloader, Thanks to Imnuts, That worked and Im back to 4.1.2 Vramc3. I tried using casual to unlock and root my note 2 but it failed at the bootloader section.. The log shows:
Uploading bootloader 100%
Error: Failure to confirm end of sequence transfer segment
Bootloader upload failed
Then casual disconnects.
I tried all the usual stuff, shut off the anti virus programs, changed the usb cable, reloaded the drivers. Still no joy...
I also tried to install twrp via oden and that failed also? Same thing trying to unlock the bootloader, which should be unlocked anyway.....The restore vramc3 file said it did not lock the bootloader and it was unlocked before this whole mess happened.
Anyone have an Idea on how I should proceed? I'm paranoid that I will get an OTA that will lock the bootloader forever. Would like to root before that happens... Thanks
Try and uninstall all the USB drivers in device manager, and then do find new hardware. Been a while, but I recall Adam saying this had to be done, as one of the steps hoses the USB drivers from working.
If you have Titanium installed, you should be able to freeze the update app on your phone and it will protect you from OTA.
Thanks for the reply. I did all the rebooting of the drivers because initially oden would not recognize the phone after the first failure. After that it and casual worked. The problem is I cant get past the bootloader update or unlock with casual or manually.....Is it possible the bootloader is locked now? Can I use safestrap if it is? Is there a way to check where the bootloader is, locked, or unlocked? I know what you mean it has been a long time.....lol The last time I did this stuff was four years ago....Had to relearn how to do it.....XDA is a great source....