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....
Related
I'm getting the "Failed to boot 2, then RSD Starting." I've read that I may not have the correct files, or possibly I'm doing something wrong. Can someone dumb down the correction to my issue? I want to get into recovery, so that I can back up and then install CM7. I think I have the latest versions of everything.
Any help is appreciated. Sorry if this is a repost
Have you unlocked your bootloader ?
I had this *exact* same problem. It occurred as I tried to flash ROM Manager's recovery (from ROM Manager) *before* I unlocked the bootloader. IE, I tried to flash the recovery partition before I was unlocked. I could never recover. I tried the AUTOMATIC... unlock batch program - many options, just about everything.
I ended up using Motorola's official MSU to recover to stock. Then I ran the AUTOMATIC... unlock batch program first. Once unlocked, it was pretty simple after that.
Problems with CWM recovery
jmaddr said:
I had this *exact* same problem. It occurred as I tried to flash ROM Manager's recovery (from ROM Manager) *before* I unlocked the bootloader. IE, I tried to flash the recovery partition before I was unlocked. I could never recover. I tried the AUTOMATIC... unlock batch program - many options, just about everything.
I ended up using Motorola's official MSU to recover to stock. Then I ran the AUTOMATIC... unlock batch program first. Once unlocked, it was pretty simple after that.
Click to expand...
Click to collapse
Hello, i've the same problem. I need to ask before do what you do because i'm a noob. i'm rooted and i flashed CWR
1-Doing the MSU stock recover will hard brick my phone?
2-i've been reading the "What's in this Software Update?" and is says it's for 2.3 GB. It will works for me? i'm 2.2.2 froyo.
I was searching but can't find answers.
Sorry about my english
Thanks
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? >.<).
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.
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.
I'm really out of ideas to what's causing this so I could use some help.
My tablet has been fine for a long time and has had many roms on it previously. I have been on rooted stock however for over a year now and decided to try a rom again....
However I have tried 3 different roms now all with catastrophic problems. I install them fine through twrp along with gapps then reset Tablet but get a black screen with just a blinking charge light if it's plugged in. No boot logo or anything.
I managed to revert back to stock about 5 times today through flash mode and flash tool but I don't know what's going on.
I rooted, turned on debugging and reflashed twrp but it keeps happening across different android versions too. I thought maybe I had relocked bootloader so I tried to check through adb oem but it freezes, so I ran the unlock command just in case through adb and it was fine but still freezes.
Any ideas?
To add to this I just downloaded a dialer app on stock to check bootloader unlock status.
It says bootloader can be unlocked but nothing about its actual status. I'm more or less certain this is the issue now so can anyone advise what to do? I manually tried unlocking bootloader and it just restarted like everything was fine but nothing changed.
SabertoothTitan said:
To add to this I just downloaded a dialer app on stock to check bootloader unlock status.
It says bootloader can be unlocked but nothing about its actual status. I'm more or less certain this is the issue now so can anyone advise what to do? I manually tried unlocking bootloader and it just restarted like everything was fine but nothing changed.
Click to expand...
Click to collapse
I'm not an expert to be honest but I would try that:
put your tablet in fastboot mode, connect it to your pc and in fastboot type
"fastboot flash boot twrp.img"
Now you should have TWRP.
If this work your bootloader should be unlocked otherwise I think you should see some error in fastboot
Once you have twrp I suggest you to flash resurrection remix 5.7.0 (android 6.0.1). I suggest it just because it worked without problem with my tablet Z.
Something not clear to me: you started just with a rooted stock ROM or you unlocked bootloader, flashed TWRP and then your ROM?
I started with rooted stock rom, I am using dual recovery that seems to be working fine (it was faster since its just a bat file). I originally rooted using kingroot on stock which I used to flash stock rom prerooted with supersu with twrp.
If I try the same process with anything that isn't stock it's black screen on reboot. No Sony logo or anything.
Ive tried changing recovery to newest twrp, changing sd card to a different one, different ROMs including the one you mentioned because that's the one I wanted to try. I also tried with and without black kernel. None made any difference. Black screen boot everytime with just a blinking light on side like its got no OS installed at all.
Just to clarify, my bootloader should be unlocked. I've checked but if I run the adb command to check it just freezes like it's eternally loading. Using dialer go check it doesn't even display anything about it aside from the fact it can be unlocked.
what command do you type? "fastboot oem device-info"?
ok so I have an update, something is definitely messed up with my bootloader.
I tried to relock bootloader from fastboot but its also stuck in a loading cycle for no reason. It seems on some level my bootloader is unlocked because I can flash recoveries fine, but when I come to put a new ROM on the device it won't let me and black screens.
From fastboots I used the commands 'fastboot oem lock' and I just get '...' forever underneath. If I use 'fastboot devices' my device is listed, if I use 'fastboot -i 0x0fce oem unlock 0xbootloadercodehere' it fails the first time, then works the second time and says ok but its clearly done nothing when the device reboots. 'fastboot oem device-info' also leaves me with the '...' on command prompt forever too.
I have no idea what to do if bootloader is screwy at all.
-Pepe said:
what command do you type? "fastboot oem device-info"?
Click to expand...
Click to collapse
Yup that's what I used. I'm pretty sure bootloader is borked somehow though. I tried reinstall from Sony software too which hasn't changed anything.
SabertoothTitan said:
Yup that's what I used. I'm pretty sure bootloader is borked somehow though. I tried reinstall from Sony software too which hasn't changed anything.
Click to expand...
Click to collapse
I just tried with my XTZ and "fastboot oem device-info" just froze, it had 3 dot and nothing else. In my OPO it worked.
I'm gonna search something else...
Whats weird is my tablet also won't install anything on TWRP, I just tried installing SuperSU from it to see if it would work (having to use Kingroot atm) and it just does nothing.
I think this is the issue since I'm factory resetting before installing a ROM, which is therefore wiping my system and when I come to reset because TWRP isn't installing anything its acting like there isn't a system installed.
I can install via ADB fine, just when it comes to recovery... system says no. Its weird because its like its got a locked bootloader or something but even though I reinstalled using Sony software its still the same. If I try unlock bootloader again, I get an error first time then it says OKAY and does nothing.
SabertoothTitan said:
bootloader can be unlocked
Click to expand...
Click to collapse
According to an other post this should mean that your bootloader is locked but can be unlocked via Sony's code. At the same time I've read in the same post (can't find it) that people with unlocked bootloader still have "bootloader can be unlocked" even if they successfully unlocked it...
Unfortunately I can't try it myself because I'm on RR and the code *#*#7378423#*#* (this should be the code you used) doesn't do anything.
I have the code and have used it previously I have also retried it just to make sure.
When I type the dialer code above I get 'bootloader can be unlocked: yes' but nothing mentioning the actual current state of bootloader.
This is what's leading me to think it's a bootloader glitch because all posts I've seen should say 'bootloader unlocked: yes' or 'bootloader unlocked: no'. I get neither.
Been a few days and had no suggestions. Anyone got any ideas at all outside what I have mentioned? Getting pretty desperate because wifi is really bad on stock, getting constant slowdowns and stalls for no reason. I'm gonna end up trying to sell second hand if I can't do anything.
SabertoothTitan said:
Been a few days and had no suggestions. Anyone got any ideas at all outside what I have mentioned? Getting pretty desperate because wifi is really bad on stock, getting constant slowdowns and stalls for no reason. I'm gonna end up trying to sell second hand if I can't do anything.
Click to expand...
Click to collapse
Sorry, I'm out of ideas
The only thing I can tell you is what I did to my XPZ, but I doubt it may help you:
1) Unlock bootloader using Sony's guide
2) XPZ in fastboot mode → from pc "fastboot flash boot twrp.img" (assuming you have the proper TWRP image named twrp in the same folder of fastboot)
3) flashed RR 5.7.0 and Gapps
4) RR change the rocovery to CMrecovery but I "easily" changed back to twrp using a guide under RR thread.