I was lucky enough to get a tab with an unlocked bootloader. I've been messing around with the TW roms in the development forum, but I decided I wanted to go back to stock for a while. I flashed the 3.1ota rom and I thought I was good to go. So I went to try to update my tab and I blindly downloaded and installed the 11mb update that gives you Videos and locks your bootloader.
Now, the 'lock' has been removed from my boot screen, and it seems no matter what I do to replace the locked IO bootloader, I can't get it to go away so I can get the actual Retail OTA TW update.
I've also tried KIES and it says that it cannot update the firmware on this device. I'm assuming that's because it thinks its the IO tab.
I've spent the last 8 hours trying to find a way to unlock the bootloader to no avail.
Help?
All the files I've found wont overwrite the now-locked IO bootloader...
Related
I rooted a coworkers phone a couple weeks back and now he's telling me he did the ota update. I'm not sure how all updates were disabled when I left but he showed me and its 2.1.
That being said, does a rooted phone that received an update maintain root and how do you tell. I feel comfortable going through the rooting process but if its a lost cause I'd rather not mess with it and mess up someone else's phone.
Thanks guys.
Well he wanted me to try it anyway and everything went just like the first 3 times I rooted. Had a memory error but after a couple reboots I tried again and no problem....I think anyway. After we the recovery screen I had to run so I'm don't know if he flashed anything with success yet or not.
The OTA-2.1 update would never run on a phone that already had 2.1 running on it. It patches files from 1.17.605.1 and has version checks in it that prevent it from running otherwise.
That suggests one of two things:
(a) You are mistaken in your belief that you rooted his phone, or
(b) Your friend has acquired some mad skilz; sufficiently advanced that he would no longer need your help. (That is, he rolled back his rooted phone to 1.5, and then took the OTA after that.)
If he had a 1.5 phone that received the OTA-2.1 update, it is highly likely that it can be rooted - for the first time or the second.
bftb0
I'm not real sure what happened. Said he tried to go into recovery and ended up with hboot update. After all that he was at 2.1and couldn't get recovery, it gave him the android and the exclamation point.
I got it and used the 1.5 to 2.1 to get recovery back and besides some memory errors everything was gravy.
I know he was rooted, I flashed aloysius 6 for him when I first rooted it.
Well, perhaps your friend is confused about what he did.
The OTA-2.1 update will not run on a 2.1 phone, and it certainly won't install a new bootloader either.
Sounds more like he re-flashed either the root ROM or the Leak-V1 rom - both of them use the same image (Android in lower right hand corner, yellow exclamation point inside a white triangle in the upper left hand corner) for the recovery boot "splash screen".
He can find out what his options are if he checks his bootloader version; they're all good for re-rooting except for the 1.49.0000 S-ON (aka "Leak") bootloader.
From the way you describe it, it sounds like he had the ROOT PB00IMG.ZIP file sitting on his SD card still, and probably just re-rooted his phone (which would give him 1.49.2000 S-OFF).
bftb0
I have a TP201, unlocked bootloader, rooted. No ROMs, just Android 4.0.3.
My machine doesn't recognize any system firmware update. I followed the instructions in various locations on downloading the official Asus update, moved to internal memory, temp unrooted (with Voodoo) and restarted. Upon restart, it prompts me to start update sequence. I do so, it reboots to CWM boot. I tried restarting, no dice. I went to install zipped update from Asus, restarted and it still went back to CWM Recovery.
I researched and installed ADB for bricked 1a option...and now my machine boots to 4.0.3 fine again.
I would like to install the Asus firmware update but don't know how - it seems CWM is interfering somehow.
Thank you.
jjjenkin said:
I have a TP201, unlocked bootloader, rooted. No ROMs, just Android 4.0.3.
My machine doesn't recognize any system firmware update. I followed the instructions in various locations on downloading the official Asus update, moved to internal memory, temp unrooted (with Voodoo) and restarted. Upon restart, it prompts me to start update sequence. I do so, it reboots to CWM boot. I tried restarting, no dice. I went to install zipped update from Asus, restarted and it still went back to CWM Recovery.
I researched and installed ADB for bricked 1a option...and now my machine boots to 4.0.3 fine again.
I would like to install the Asus firmware update but don't know how - it seems CWM is interfering somehow.
Thank you.
Click to expand...
Click to collapse
Read about things before unlocking. Learn where to ask questions.
Sincerely,
The Internet
P.S.
You cannot update your tablet with official Asus updates after unlocking. Search the forums for developer assisted solutions.
Sent from my ADR6425LVW using xda premium
jjjenkin said:
I have a TP201, unlocked bootloader, rooted. No ROMs, just Android 4.0.3.
My machine doesn't recognize any system firmware update. I followed the instructions in various locations on downloading the official Asus update, moved to internal memory, temp unrooted (with Voodoo) and restarted. Upon restart, it prompts me to start update sequence. I do so, it reboots to CWM boot. I tried restarting, no dice. I went to install zipped update from Asus, restarted and it still went back to CWM Recovery.
I researched and installed ADB for bricked 1a option...and now my machine boots to 4.0.3 fine again.
I would like to install the Asus firmware update but don't know how - it seems CWM is interfering somehow.
Thank you.
Click to expand...
Click to collapse
Once you unlock there is no way back to a stock Asus Rom. What you can do however is to use a custom Rom based on the Asus source. I'm using Androwook 1.51 which seems very very close to the stock Rom feature wise but rooted and more customizable - and faster and smoother. In fact it makes me wonder why Asus itself can't seem to make a Rom like this when the devs on this site can make an Ausus ROM better than Ausus itself can do?
Bascially unless you use a custom ROM now that you are unlocked you are permanently stuck on 4.03.
Go here: http://forum.xda-developers.com/showthread.php?t=1674827
Follow the instructions in the second post for "Upgrade instructions for ICS". Read everything very carefully. Read it many times if you have to to make sure you understand it. Ask questions first, then flash, not the other way around. You currently have a working device so take your time and don't take unnecessary chances.
In fact it makes me wonder why Asus itself can't seem to make a Rom like this when the devs on this site can make an Ausus ROM better than Ausus itself can do?
That is why i unlocked my last week.
don;t know why u can't stop the updated from asus if you don't want them.
Newfe said:
...
don;t know why u can't stop the updated from asus if you don't want them.
Click to expand...
Click to collapse
Actually the issue is that the OP wants the update from Asus but did not understand that once he unlocked he was never going to get it.
OK so here is the story and I was debating if this is the right place to post but I do feel it is more on the developing side. I originally rooted and unlocked my bootloader following Casuals method and everything was just fine. I had an option to sell the phone in preparation for buying the GS4 so I used the return to stock method posted in the forums to return my device completely to stock. After doing so everything was also fine. I received an update to LL4 and that went OK straight from Verizon but last night when the VRAMC3 update was pushed to my phone it soft bricked it. It ultimately was stock on the splash screen stating Samsung Note 2. After trying to ODIN back to stock with multiple FAILS I was able to get it back to the Root66 MR Robinson by using the pit file but every time I try to update and or root/unlock bootloader it soft bricks again. I am assuming that the update that was pushed updated my bootloader and as of now I am stuck till there is a new bootloader Jailbreak. If not I would love some instruction on how to get my phone rooted with an unlocked bootloader or a flashable ODIN file that will at least get me to the latest VRAMC3 fully stock ROM. Thank you for the HELP.
want relocked BL running newest stock via odin flash without tripping flash counter
Edit; I never did manage to relock the bootloader. However, Verizon still accepted the device since it appeared close enough to stock. I used the alternative restore and triangle away to bring it 95 percent to stock. So I can safely say from my experience that if this is your problem you will probably be fine. It's been a few months and still no new charges on my bill for out of warranty device but YMMV
Shawnkanan said:
OK so here is the story and I was debating if this is the right place to post but I do feel it is more on the developing side. I originally rooted and unlocked my bootloader following Casuals method and everything was just fine. I had an option to sell the phone in preparation for buying the GS4 so I used the return to stock method posted in the forums to return my device completely to stock. After doing so everything was also fine. I received an update to LL4 and that went OK straight from Verizon but last night when the VRAMC3 update was pushed to my phone it soft bricked it. It ultimately was stock on the splash screen stating Samsung Note 2. After trying to ODIN back to stock with multiple FAILS I was able to get it back to the Root66 MR Robinson by using the pit file but every time I try to update and or root/unlock bootloader it soft bricks again. I am assuming that the update that was pushed updated my bootloader and as of now I am stuck till there is a new bootloader Jailbreak. If not I would love some instruction on how to get my phone rooted with an unlocked bootloader or a flashable ODIN file that will at least get me to the latest VRAMC3 fully stock ROM. Thank you for the HELP.
Click to expand...
Click to collapse
I am in a similar situation. I am sending the device back for warranty service since the screen must have burnt out or something. The digitizer catches a touch but there is no light emanating from the screen and since the device was purchased March 28th it is completely under warranty. As it is obvious the root modifications did not cause the screen issue, I do not wish to get a new device via insurance claim and so I am getting another sent.
but my issue is after managing to run triangle away via screencast/adb, how the hell does one relock the device if it's been upgraded to vramc3? from what I have searched, and trust me I have been searching the past two days, which led me here and a few other threads btw, it appears that once the device is on vramc3 it cannot odin back to anything else or it will fail on sboot.bin. And I am not finding any stock odin packages for vramc3, so how the hell does a person take this bad boy back to stock and relock the bootloader for sending to vzw for service? not only that but I can no longer activate recovery since I wouldnt have access to screencast and there is absolutely no way I am sending this device back with even the most minute amount of data in tact so it can be sold to the highest bidder or handed over via an illegal court order for mass search and seizure. anybody have experience with this? i am at the point where i think the only thing I can do is flash the alternate restore for vral but wouldnt that trip my flash counter, and then when they check the device it would probably OTA and softbrick, which I do not want them to have to deal with.
So I made the switch from my hyperdrive S3 to the s4 yesterday. Best buy did the update to me7... Am I understanding that I'm stuck with stock because it has an unlockable bootloader? I rooted it last night and it was fine but now what?
I can't stand a bloated stock phone anymore after my slimmed s3.
Everything I've read seems to indicate there's no way around the bootloader
As of right now, yes, you're stuck on stock. You do have root, so you can at least freeze the Samsung/carrier apps you don't want, but the bootloader is locked and nobody has figured out a way to bypass it yet. If you unroot you might be able to return it on the excuse that the phone is having performance issues, and tell them you've heard the new software update is to blame so you don't want it installed on the replacement.
Ok so hopefully i can get some help with my issue here. I have just resurrected my S4 i thought was dead, but it had the power button sticking problem, and now after about 3 years its going again! This is my problem tho. I got this phone early in the releases. Rooted while on 4.3, unlocked my bootloader on 4.3, ran many ROMS and tons of flashing with no problems. Currently the phone is (ironically) running Ressurrection Remix KK V5.1.0. My Baseband version still states 1545VRUAMDK. I have been trying to get everything up to date but nothing is working right. Im on TWRP version 2.6.0 and yes i have been into recovery since getting it working again. One time when trying to update TWRP i got the Unautorized Software yellow sign sceen. Booted to Download mode and cancelled. I cant get it back into Recovery now and my TWRP wasnt updated. How has my phone became locked again, and how can i fix this? Thanks
If your really still on MDK you can just reunlock your bootloader. Any higher and your stuck on stock, or you could try your luck with flashfire but it only works with touchwiz rims and when I used it on my old s4 it hard bricked it.
You have soft-bricked
Use Odin and flash the no-wipe tar of MDK while in download mode then re-root, etc. You need to use Flashfire to update TWRP. I did the same thing as you recently testing ROM installation with different versions of TWRP. If you update by flashing the img file via TWRP it soft bricks, I found out the hard way.