Hi all, just got my 300t back from my daughter (let her use it for school, she got something else to use now) so I wanted to upgrade to the latest but I attempted to flash the latest TWRP and it gave me 2 (one on top of the other) so I assume I am not running the latest bootloader (I don't see it at the top of the screen in bootloader). How would I find what bootloader version I am currently on? I am running CROMi-Xenogenesis 4.5 and I did get TWRP 2.5.0.0.
I appreciate the help, I've been looking for at least an hour now and can't find the info.
EDIT: I flashed the blob and the latest recovery and now I'm back up to the latest bootloader and TWRP. Appreciate the help Broseph
draky said:
Hi all, just got my 300t back from my daughter (let her use it for school, she got something else to use now) so I wanted to upgrade to the latest but I attempted to flash the latest TWRP and it gave me 2 (one on top of the other) so I assume I am not running the latest bootloader (I don't see it at the top of the screen in bootloader). How would I find what bootloader version I am currently on? I am running CROMi-Xenogenesis 4.5 and I did get TWRP 2.5.0.0.
I appreciate the help, I've been looking for at least an hour now and can't find the info.
Click to expand...
Click to collapse
What do you mean by 'one over the other'?
Also, when did you start putting custom ROMs on your tablet? If that was back in the 4.1 days, you may have missed a boot loader update in an Asus OTA.
I stopped about August last summer. I have CROMi-Xenogenesis 4.5 like I said before but that's only because I happened to still have that on the SD Card still when I got it back from her. Is there a way to tell what bootloader it is?
Maybe if you take a picture of it, someone here can recognize it.
Related
Hello, Id like to bring some life back into my a500 and installing Omnirom would be the way for me to get to that point. I currently am rooted and running Flexreaper-r9-a500_0.019.00_ww_gen1.
I recently had TWRP 2.1.3 on it, but somehow managed to screw that up and now used acer revoery and have CWM 5.0( thor2002ro rev1.3.4)
How in the world do I get the correct bootloader on here? Ive tried goo manager, but I may be doing something wrong.
Also I have no clue I have Skrilex bootloader. Im guessing no.
Can anyone help to get this rom running for me please. I was going to get a new tablet, but that idea was quickly shot down by SO
Hey guys. I'm not sure if this is the right section for me to post this so sorry in advance if it's not.
So I have Android 5.1 version with TWRP and I keep getting the notification that the 5.1.1 update has been downloaded, but whenever I try to install it, it just goes to TWRP recovery and nothing happens. I've tried installing it from "install" and tapping on the update.zip file, but I get errors. Basically what I figured I should do is just update to 5.1.1 and use Nexus Root Toolkit to root the device again (I think I've done it like this with past updates, but I might have been using CWM). So what I want to do is to have a rooted device with the latest official Android version released for it (or a custom one if it'll make it faster) but as you probably already guessed, I'm a bit lost here and I'm not sure what to do in order to achieve that.
Btw The bootloader has been unlocked a long time ago if this helps in any way with this particular issue.
Any help would be greatly appreciated.
Hi, I'm new to ROM flashing etc. and seem to have gotten myself in trouble.
I bought a used Moto X Pure (XT1575 model) with, I guess, the Motorola unlocked bootloader and TWRP already installed. I accidentally approved an OTA update this afternoon and ended up in a boot-loop.
In trying to fix it I used the "restore-to-stock tool" for windows found here:
http://forum.xda-developers.com/mot...ndows-tool-moto-x-style-pure-edition-t3199905
This was semi-successful; the OS loaded and I was able to begin migrating my old apps, but
(1) the wi-fi doesn't work at all! I can't turn it on in settings -- the slider will slide on but then slide back off by itself
(2) the recovery image seems screwed up; I can't get into recovery mode, and get an error there instead.
I am at a loss as to what to do but see my last resort in using fastboot to upgrade to the 6.0 stock image as described here:
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
I'm too tired to try tonight, so I thought I'd ask for advice before I go to bed. What are my options here, especially if the upgrade to 6.0 creates new problems? Can I get error meessages for the wireless so I at least know what's going on? Can I reflash the wireless firmware -- might it have been messed up if one or another upgrade was interrupted somehow?
Also -- hope I'm in the right forum -- please point me in the right direction if I'm not!
Many thanks for the help!
Did you read that thread? Quite a bit of wifi talk in there.
lafester said:
Did you read that thread? Quite a bit of wifi talk in there.
Click to expand...
Click to collapse
Oh man, I had NOT read far enough in that thread. The solution was simply to reflash the modem,
Code:
fastboot flash modem NON-HLOS.bin
Just did it and the wifi issue seems to be fixed!
How should I approach the crashed recovery partition? When I got the phone, TWRP was installed as well as SuperSU. I tried the restore-to-stock tool mostly because of the problem with OTA updates being so frustrating; but I wouldn't object to reinstalling TWRP and SuperSU, if I knew how to get and install new images within a few days of the OTA update arriving (I have been deferring the last OTA update since the day I got the phone, a month ago -- I was bound to make a typing error eventually, and it happened yesterday). Anyway, if you can point me in the right direction for learning that stuff I'd be grateful.
So psyched to have wifi working! THank you!
There's a twrp thread in og dev
So I purchased my Zenfone 2 about two weeks ago and immediately set about rooting it.
The person who owned it before me had received the OTA update 21.40.1220.1708. I checked the website and it didn't have it listed under ZE551KL so I assumed he simply forced an update for the wrong model, and set about rolling back to update 21.40.1220.1615. In the process, I deleted my OS.
From there, the phone obviously doesn't boot. I've tried installing update from SD in recovery with the zip file for 21.40.1220.1615 from ASUS' website but it says that it's an older version and cannot be used, but anyone who is familiar with the current situation knows that ASUS hasn't dropped update 21.40.1220.1708 on their website. What's worse, some people are speculating they revised the version number on the website version from 1708 to 1615, making it utterly useless in putting the OS back on my device.
To top it all off, the bootloader is still locked. I can access recovery and fastboot, but with the bootloader locked it doesn't help me that much.
Does anyone know a way of getting the OS back on my device? Any help would be appreciated.
SnowzSan said:
So I purchased my Zenfone 2 about two weeks ago and immediately set about rooting it.
The person who owned it before me had received the OTA update 21.40.1220.1708. I checked the website and it didn't have it listed under ZE551KL so I assumed he simply forced an update for the wrong model, and set about rolling back to update 21.40.1220.1615. In the process, I deleted my OS.
From there, the phone obviously doesn't boot. I've tried installing update from SD in recovery with the zip file for 21.40.1220.1615 from ASUS' website but it says that it's an older version and cannot be used, but anyone who is familiar with the current situation knows that ASUS hasn't dropped update 21.40.1220.1708 on their website. What's worse, some people are speculating they revised the version number on the website version from 1708 to 1615, making it utterly useless in putting the OS back on my device.
To top it all off, the bootloader is still locked. I can access recovery and fastboot, but with the bootloader locked it doesn't help me that much.
Does anyone know a way of getting the OS back on my device? Any help would be appreciated.
Click to expand...
Click to collapse
Figured it out.
I had to search for a stock recovery image. It had to be untouched because a modified version would be rejected because my bootloader was locked. Found one, used ADB+Fastboot to flash it on, threw update 1615 on an SDCard and it's installing right now.
can you please share that recovery....
SnowzSan said:
Figured it out.
I had to search for a stock recovery image. It had to be untouched because a modified version would be rejected because my bootloader was locked. Found one, used ADB+Fastboot to flash it on, threw update 1615 on an SDCard and it's installing right now.
Click to expand...
Click to collapse
So this the MM stock recovery for MM, correct?
Can you please share that or point me to where you got it from, appreicated.
Thanks
I'll put the long story below..but spare those that don't want to read. The short is, I'm not able to ADB Sideload the OTA images as it always fails to verifiy signature at about 40-47%. I've searched many places and not found a fix. So I'm hoping the genuises here at XDA which I frequent can help.
The long story. I've flashed roms for many years. My current device was the Nexus 6p. Running XE Rom I think it was. Flashed an update all was well, but my sim card would not show up. I was on MetroPCS and remembered needing a different radio. Flashed that,still no sim. Decided I'd go back to Stock since those had been updated to 8 by now. Flashed the OTA and followed some steps by another thread on XDA, one of the last was locking the bootloader. I had not booted up so I didn't know if my system was working. My big mistake! I locked my bootloader and don't have a system to boot into so I can enable OEM Unlocking. So now I only have adb sideload, can't flash individual images through fastboot! I think it can be recovered but for some reason the signature verification issue keeps coming up no matter what cable or PC I use.
If anyone has any thoughts I'd love to hear them. I have since moved to a Hauwei Mate SE and am pretty pleased but will not be a flashing phone I don't think. I loved my 6p and it still had lot's of life for me. I hate to sell it for parts at this point.... Thanks for anyone willing to chime in.
tcoursey said:
I'll put the long story below..but spare those that don't want to read. The short is, I'm not able to ADB Sideload the OTA images as it always fails to verifiy signature at about 40-47%. I've searched many places and not found a fix. So I'm hoping the genuises here at XDA which I frequent can help.
The long story. I've flashed roms for many years. My current device was the Nexus 6p. Running XE Rom I think it was. Flashed an update all was well, but my sim card would not show up. I was on MetroPCS and remembered needing a different radio. Flashed that,still no sim. Decided I'd go back to Stock since those had been updated to 8 by now. Flashed the OTA and followed some steps by another thread on XDA, one of the last was locking the bootloader. I had not booted up so I didn't know if my system was working. My big mistake! I locked my bootloader and don't have a system to boot into so I can enable OEM Unlocking. So now I only have adb sideload, can't flash individual images through fastboot! I think it can be recovered but for some reason the signature verification issue keeps coming up no matter what cable or PC I use.
If anyone has any thoughts I'd love to hear them. I have since moved to a Hauwei Mate SE and am pretty pleased but will not be a flashing phone I don't think. I loved my 6p and it still had lot's of life for me. I hate to sell it for parts at this point.... Thanks for anyone willing to chime in.
Click to expand...
Click to collapse
First, if i understand right you tried to flash OTA over custom rom to return to stock?? To go to stock you must flash full system image, not OTA.
And second, why the hell did you lock the bootloader??...you dont lock the BL unless you are 100% stock..
I know i didnt help you much, but if your BL is locked, dont know how to help...maybe someone else know how to unlock it again
Meanwhile read this guide,it will help you to understand some things:
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
scrin378 said:
First, if i understand right you tried to flash OTA over custom rom to return to stock?? To go to stock you must flash full system image, not OTA.
And second, why the hell did you lock the bootloader??...you dont lock the BL unless you are 100% stock..
I know i didnt help you much, but if your BL is locked, dont know how to help...maybe someone else know how to unlock it again
Meanwhile read this guide,it will help you to understand some things:
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Oh believe me my head hit the wall for sure! I got careless and wasn't thinking straight. No reason to lock the boot loader except it was on a list of steps to get back to stock..and I guess it was late! doh.
There are lot's of posts/videos I've seen that should allow what I'm trying to do with sideload adb but mine keeps getting a signature verification error. Each new full version of a release 7.0 8.0 etc..has the entire rom, images etc. So your suppose to be able to flash those even though they are OTA updates... *shrug*
It's a blur what I did exactly in some areas. I at one point may have tried to flash the set of Stock IMG files as well. But for sure now all I'm left with is a locked phone with who knows what on it! Stock recovery...some form of 7.0.0 that has NYC as letters...that I can find NOWHERE! on any official releases...
Prob trash, I really want that night back..lol.