Hey all, I tried searching for a solution to no avail. I tried the L dev preview and found it too buggy to keep. I would like to return to kitkat. Is there a step by step guide for this somewhere in this forum? Thanks for the help in advance.
jigz23 said:
Hey all, I tried searching for a solution to no avail. I tried the L dev preview and found it too buggy to keep. I would like to return to kitkat. Is there a step by step guide for this somewhere in this forum? Thanks for the help in advance.
Click to expand...
Click to collapse
Well, I used MultiROM to try out L, now someone else on here had moved to L without MultiROM, and when they wanted to go back like you, they found that fastboot they had would not recognize the bootloader of L, whether this was an issue of the L bootloader being too new for the released fastboot or if it was user error, I do not know, the person never followed up.
That being said, one thing, DO NOT fastboot erase the bootloader, just don't, you'll hardbrick your device.
So let's say that fastboot will work fine on the L bootloader and it was user error.
Assuming you have nothing on there you want, you can use Google's factory images and just let it do its thing. Install fastboot stuff, run a .bat file. Easy peasy.
You can also try Wug's Toolkit.
But if you like trying things out like that, you might want to look into MultiROM.
You could in theory install MultiROM on Android L, install a kernel with kexec patch (can now be done within MultiROM app), then install 4.4.4 as secondary using tasssadars flashable 4.4.3, grab the OTA (or flash 4.4.4 system.img), then swap ROMs (Done in MultiROMS custom TWRP).
mdamaged said:
Well, I used MultiROM to try out L, now someone else on here had moved to L without MultiROM, and when they wanted to go back like you, they found that fastboot they had would not recognize the bootloader of L, whether this was an issue of the L bootloader being too new for the released fastboot or if it was user error, I do not know, the person never followed up.
That being said, one thing, DO NOT fastboot erase the bootloader, just don't, you'll hardbrick your device.
So let's say that fastboot will work fine on the L bootloader and it was user error.
Assuming you have nothing on there you want, you can use Google's factory images and just let it do its thing. Install fastboot stuff, run a .bat file. Easy peasy.
You can also try Wug's Toolkit.
But if you like trying things out like that, you might want to look into MultiROM.
You could in theory install MultiROM on Android L, install a kernel with kexec patch (can now be done within MultiROM app), then install 4.4.4 as secondary using tasssadars flashable 4.4.3, grab the OTA (or flash 4.4.4 system.img), then swap ROMs (Done in MultiROMS custom TWRP).
Click to expand...
Click to collapse
Thanks a bunch. After doing some more research I came across this website: http://www.cultofandroid.com/65592/downgrade-android-kitkat-android-l-nexus-5-7/ and it worked like a charm! Thanks again!
Flash a custom recovery like twrp in a android SDK command window and then just flash a KitKat image.
Here's one http://www.scottsroms.com/downloads.php?do=cat&id=94
Sent from my Nexus 7 using XDA Premium 4 mobile app
Related
I'm quite familiar with the Skipsoft Toolkits. I've used them plenty of times in the past.
Bought a Nexus 7 2013 today. First thing it wanted to do was update from 4.3 to 4.4.2. I did that. Then 4.4.3. Did that.
I now wanted to use the tooklit to unlock and flash a custom recovery so I can try out CleanRom.
There is no 4.4.3 option in the toolkit.
Question
Can I select the 4.4.2 Build and then unlock the bootloader and flash a custom recovery? This is all I need correct? I typically always used the All in one option in previous devices but since 4.4.3 isn't an option I can't.
While were at it, the other things the "All in one" flash does, such as Busybox, Rename Recovery Restore Files and Root. Do I need to do any of these? What is busybox? Why would I need to rename recovery restore files? Is unlocking bootloader and flashing custom recovery all I need to do to start flashing Roms?
Just making sure as I've always gone the "All in one" Route.
And Yes, I know I can do via ADB but Its been a long time since I've done it and would rather take the familiar route.
bigystyle84 said:
I'm quite familiar with the Skipsoft Toolkits. I've used them plenty of times in the past.
Bought a Nexus 7 2013 today. First thing it wanted to do was update from 4.3 to 4.4.2. I did that. Then 4.4.3. Did that.
I now wanted to use the tooklit to unlock and flash a custom recovery so I can try out CleanRom.
There is no 4.4.3 option in the toolkit.
Question
Can I select the 4.4.2 Build and then unlock the bootloader and flash a custom recovery? This is all I need correct? I typically always used the All in one option in previous devices but since 4.4.3 isn't an option I can't.
While were at it, the other things the "All in one" flash does, such as Busybox, Rename Recovery Restore Files and Root. Do I need to do any of these? What is busybox? Why would I need to rename recovery restore files? Is unlocking bootloader and flashing custom recovery all I need to do to start flashing Roms?
Just making sure as I've always gone the "All in one" Route.
And Yes, I know I can do via ADB but Its been a long time since I've done it and would rather take the familiar route.
Click to expand...
Click to collapse
Don't use toolkits.
I advise learning how to do this operation manually. It's very simple. Read this: http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
I know it's a long read. But seriously, you can unlock the bootloader, fastboot flash an update, flash a recovery, and have root in about 3 minutes.
I would say a normal user does not need busybox. And most apps that require it come with their own version.
Hi! So I'm looking to root my Nexus 5x following this guide. However, I can't find the modified boot.img for my build MMB29P. I have a brand new phone out of the box (my mic stopped working so this is a replacement) so I'd like to get this done in the next little while the phone has no data and I can wipe anything I need to without worry and use the restore afterwards. I also heard something about SuperSU being able to use stock boot.img or something of that nature, could someone clue me in? Thanks!
[GUIDE] Unlock/Root/Flash for Nexus 5X - Heisenberg's How-To Guide For Beginners
take a look at section 6
as an alternative there are some toolkits that may be more convenient to you (on-screen instructions and detailed faq/guides)
The latest version of SuperSU (v. 2.66 I believe) is automated for systems root. I actually used the SuperSU beta v. 2.62 to root. I just unlocked bootloader, flashed TWRP, and then flashed that version of SuperSU.
Sent from my Nexus 5X using Tapatalk
Sweet! Officially, unlocked, TWRP'd, rooted, and supersu'd So as far as upgrading? I grab the file from google officially and flash it via TWRP?
jkingaround said:
Sweet! Officially, unlocked, TWRP'd, rooted, and supersu'd So as far as upgrading? I grab the file from google officially and flash it via TWRP?
Click to expand...
Click to collapse
No, an official image cannot be flashed like that. If you fastboot flash an image you will lose recovery and root. Update officially with a factory image and root afterwards or flash a custom rom plus vendor.img.
https://www.androidfilehost.com/?w=files&flid=43558
k.s.deviate said:
No, an official image cannot be flashed like that. If you fastboot flash an image you will lose recovery and root. Update officially with a factory image and root afterwards or flash a custom rom plus vendor.img.
Click to expand...
Click to collapse
Even with systemless root?
When it comes to upgrading, there are a couple of routes you can take. Both involve downloading the official factory image ZIP first. Extract the contents, reboot into bootloader, and then you have option:
1. Edit the flash-all script (.bat for windows and .sh for Linux/Mac) by removing the -w option. Removing this option will prevent the upgrade from wiping user data. Once the option is removed, simply run the script to upgrade.
2. Flash the images individually. Sometimes certain things don't change like bootloader.img or radio.img. You should always flash boot.img, system.img, and vendor.img when updating. This is the route I take.
After flashing the images, you will need to reboot into Recovery mode and flash SuperSU. Then wipe cache and dalvik and reboot into system. If you use a custom kernel, you will need to reflash that as well after updating.
Sent from my Nexus 5X using Tapatalk
Ah makes sense. So I just need to reroot. Where do you get the "official" factory image? Have a link handy so I can bookmark it? Thanks!
Also anyway to remove the "warning" about unlocked bootloader that comes up on boot? I heard you need a custom kernel but I don't know the point of installing what (aka the benefits). Sorry for noob questions, but all the info is so scattered and hard to figure out.
jkingaround said:
Ah makes sense. So I just need to reroot. Where do you get the "official" factory image? Have a link handy so I can bookmark it? Thanks!
Also anyway to remove the "warning" about unlocked bootloader that comes up on boot? I heard you need a custom kernel but I don't know the point of installing what (aka the benefits). Sorry for noob questions, but all the info is so scattered and hard to figure out.
Click to expand...
Click to collapse
Google posts the official factory images on the developer site. Here is the link: https://developers.google.com/android/nexus/images
AFAIK the boot warning can't be removed, but I may be wrong. It's nothing to worry about though.
Having a custom kernel is not necessary, but there are benefits to using one. Custom kernels typically provide better battery life with same or improved performance. They can also make your device run cooler and use less memory. Custom kernels also allow for various tweaks such as change vibration intensty, screen DPI, headphone/speaker gain, etc. I personally use ElementalX with the Interactive Governor tweaks from the thread in the general forum, but I've read that Franco Kernel is very good as well and will probably try that out in the future.
Sent from my Nexus 5X using Tapatalk
jkingaround said:
Sweet! Officially, unlocked, TWRP'd, rooted, and supersu'd So as far as upgrading? I grab the file from google officially and flash it via TWRP?
Click to expand...
Click to collapse
Just pick a custom rom to try and follow OP instructions. Cataclysm seems to be a hit...
This is my first pure Google device. I've owned several Samsung devices and I'm familiar with using Odin to flash the device with recovery and then whatever you want from there.
I keep seeing references to fastboot. I'm really not familiar with how you flash or root your Google device using this.
Is there an all-inclusive guide on how to flash this device? I understand you have to unlock the bootloader first.
Thanks.
Sent from my Pixel C using XDA-Developers mobile app
DrKaotica said:
This is my first pure Google device. I've owned several Samsung devices and I'm familiar with using Odin to flash the device with recovery and then whatever you want from there.
I keep seeing references to fastboot. I'm really not familiar with how you flash or root your Google device using this.
Is there an all-inclusive guide on how to flash this device? I understand you have to unlock the bootloader first.
Thanks.
Sent from my Pixel C using XDA-Developers mobile app
Click to expand...
Click to collapse
I've not rooted my Pixel C, but this http://www.wugfresh.com/nrt/ works seamlessly on my Nexus 7 2013. Page suggests that it supports Pixel C.
Yes, you have to unlock the bootloader-- I found a posting here on doing it-- it's pretty straight forward.
After that all you basically need to do is boot into TWRP to install supersu. I had the bootloop issues actually flashing TWRP for whatever reason however I found another posting here noting that you don't actually HAVE to *flash* TWRP, you just need to boot into it.
First get a version of SuperSU-- I *may* have used UPDATE-SuperSU-v2.76-20160630161323.zip that I got from here somewhere-- not sure now exactly-- probably just get the latest one.
Push that to the pixel via something like "adb push UPDATE-SuperSU-v2.76-20160630161323.zip /sdcard/" from your Mac, Linux or Windows box.
So I've got a stock bootloader now ( I had to revert the whole thing to make it usable again) and to boot into TWRP I first put the pixel into fastboot mode (boot up and hold down power and volume down, then select fastboot), then go:
fastboot boot recovery.img
..where recovery.img is one of the files like TWRP-3.0.2-0.recovery.img or twrp-3.0.0-0-dragon-ryu-02112016-1.img
After you are booted into TWRP you then select (I believe, from memory) "INSTALL" and select the supersu zip file you put on the device earlier. After it installs that reboot and you are root.
DrKaotica said:
This is my first pure Google device. I've owned several Samsung devices and I'm familiar with using Odin to flash the device with recovery and then whatever you want from there.
I keep seeing references to fastboot. I'm really not familiar with how you flash or root your Google device using this.
Is there an all-inclusive guide on how to flash this device? I understand you have to unlock the bootloader first.
Thanks.
Click to expand...
Click to collapse
I'm trying to root my ZE551ML (WW-2.20.40.198) and install Xposed, but I can't get any of the scripts I've found here to work. I've installed ADB & Fastboot and this driver. MTP works and adb works when I'm in recovery mode, so I'm not sure why the scripts can't contact the device. None of the scripts recognize the device. Also, "adb devices" shows that no device is found.
It seems that all these scripts are using some variation of CWM to do it anyway. So if I could just install CWM in some other way, I guess I could just get root and xposed through CWM. I have used this official ASUS app to unlock the bootloader. So, I wonder if I could just flash a recovery.img of CWM using the command "fastboot flash recovery recovery.img"? Is that all it would take to get CWM installed? And then I could use CWM to get root, etc?
If yes, which recovery.img file should I use and where can I get it?
I think I can get fastboot to work when the device is in the bootloader, so that's what I'm thinking. Also, I can use OS X or Ubuntu then, so I don't have to worry about the Windows scripts.
Fiksdal said:
I'm trying to root my ZE551ML (WW-2.20.40.198) and install Xposed, but I can't get any of the scripts I've found here to work. I've installed ADB & Fastboot and this driver. MTP works and adb works when I'm in recovery mode, so I'm not sure why the scripts can't contact the device. None of the scripts recognize the device. Also, "adb devices" shows that no device is found.
It seems that all these scripts are using some variation of CWM to do it anyway. So if I could just install CWM in some other way, I guess I could just get root and xposed through CWM. I have used this official ASUS app to unlock the bootloader. So, I wonder if I could just flash a recovery.img of CWM using the command "fastboot flash recovery recovery.img"? Is that all it would take to get CWM installed? And then I could use CWM to get root, etc?
If yes, which recovery.img file should I use and where can I get it?
I think I can get fastboot to work when the device is in the bootloader, so that's what I'm thinking. Also, I can use OS X or Ubuntu then, so I don't have to worry about the Windows scripts.
Click to expand...
Click to collapse
Worth checking general section
http://forum.xda-developers.com/zenfone2/general/index-asus-zenfone-2-wip-t3149748
http://forum.xda-developers.com/zenfone2/development/z00az008-zenfone-2-t3265236
Hmmm.. Nevermind, I did it through TWRP. Followed this tutorial. Root works
Fiksdal said:
Hmmm.. Nevermind, I did it through TWRP. Followed this tutorial. Root works
Click to expand...
Click to collapse
Tip
It is always worth googling
and put an XDA on the end
timbernot said:
Tip
It is always worth googling
and put an XDA on the end
Click to expand...
Click to collapse
Haha, you know, I had been struggling with this problem for like 2 days. So many hours on the computer and Google trying to figure it out. I was trying to get the scripts to work, then CWM, then TWRP. I was just really confused and didn't know how to do it since most guides on Google said I had to use the scripts for Windows. Then finally I realized that it was as simple as using fastboot from OS X Anyway, sorry to bother you guys. But Everything is working now, root, Xposed and permanent TWRP. Awesome
Good stuff
There was a script at the beginning in earlier fw versions I think when boot loader was first being hacked.
Remember , if you upgrade to M , unlock boot loader again at .134 with modder tool in general section before updating to .144 and then to .184.
another tip
timbernot said:
Good stuff
There was a script at the beginning in earlier fw versions I think when boot loader was first being hacked.
Remember , if you upgrade to M , unlock boot loader again at .134 with modder tool in general section before updating to .144 and then to .184.
another tip
Click to expand...
Click to collapse
Yeah, I've tried Marshmallow already, but my favorite Xposed modules didn't work, so I've downgraded to Lollipop again
Fiksdal said:
Yeah, I've tried Marshmallow already, but my favorite Xposed modules didn't work, so I've downgraded to Lollipop again
Click to expand...
Click to collapse
You are doing great now :victory:
TEAMWIN TWRP v3.1.1 for the RAZR M KKBL (xt907 KKBL)
Built from source: http://github.com/minimal-manifest-twrp/platform_manifest_twrp_lineageos.git
All the usual prefaces to using this project. ie/eg I am not responsible for anything if you flash this zip in regards to your device or data etc etc etc
I have built this blindly (ie NO testing whatsoever) as I only have a JBBL device. It was easy for me to build since I have built a JBBL version, and I thought someone may find it useful IF it worked.
Please let me know if it works for you?
DiamondJohn said:
Please let me know if it works for you?
Click to expand...
Click to collapse
No-one has tried it?
Works like a charm for me
Worked like a charm here.
Shmaks said:
Works like a charm for me
Click to expand...
Click to collapse
trivialPotato said:
Worked like a charm here.
Click to expand...
Click to collapse
Now you just have to find a KKBL ROM to use it against :fingers-crossed: but maybe this will be a case of now that a way to flash it has been made, "build it and they will come"
Works great so far, just about to try a lineage rom.
DiamondJohn said:
TEAMWIN TWRP v3.1.1 for the RAZR M KKBL (xt907 KKBL)
Built from source: http://github.com/minimal-manifest-twrp/platform_manifest_twrp_lineageos.git
All the usual prefaces to using this project. ie/eg I am not responsible for anything if you flash this zip in regards to your device or data etc etc etc
I have built this blindly (ie NO testing whatsoever) as I only have a JBBL device. It was easy for me to build since I have built a JBBL version, and I thought someone may find it useful IF it worked.
Please let me know if it works for you?
Click to expand...
Click to collapse
Will keep you posted.
For anyone wanting to try this just a pointer. This isn't a TWRP flashable zip so you will need to use your computer to extract the IMG file and sideload using fastboot. Working great so far.
Does this require an unlocked bootloader? I am rooted.
---------- Post added at 01:36 AM ---------- Previous post was at 01:35 AM ----------
DiamondJohn said:
Now you just have to find a KKBL ROM to use it against :fingers-crossed: but maybe this will be a case of now that a way to flash it has been made, "build it and they will come"
Click to expand...
Click to collapse
I have XT907 KitKat 4.4. ready to try. Just need to know if I need an unlocked bootloader. That said, I am rooted.
DragonFire1024 said:
Does this require an unlocked bootloader? I am rooted.
I have XT907 KitKat 4.4. ready to try. Just need to know if I need an unlocked bootloader. That said, I am rooted.
Click to expand...
Click to collapse
you MUST have an unblocked bootloader to flash a custom recovery. ie this.
DiamondJohn said:
you MUST have an unblocked bootloader to flash a custom recovery. ie this.
Click to expand...
Click to collapse
I only asked because 1) wasn't mentioned in this thread specifically. 2) Not all devices require the bootloader be unlocked. 3) Why does it need to be a custom recovery? I still get confused about that from time to time because it just amazes me that it seems that's where things seem to always end up and sometimes seems to be a bit too convenient. I'm not vastly familiar with bootloader technology so that's where I scratch my head. I can install TWRP, get to all the settings and options, so why can't I just back up the proper files/imgs and flash the zip?
Looks like I'm going to have to rely on Sunshine then. I wish they accepted Bitcoin. It's that, or lose the phone to old age as it's components and functions fail slowly, one by one. I know I can reflash the stock firmware, it's been done a...few...times.
EDIT: Well s**t. Sunshine DOES accept Bitcoin. If I had known that ages ago...ugh
Just wanted to pass on this TWRP build for KKBL worked great. I ended up "downgrading" to JBBL in order to load a current LineageOS build.
It appears it was just me
I re-flashed my bootloader upgrade CAREFULLY via fastboot, and the error on wiping cache disappeared. however, I still haven't been able to flash a bootable KKBL ROM. It was suggest via PM that I also wipe my internal SDCard, which I have yet to try.
Shmaks said:
Works like a charm for me
Click to expand...
Click to collapse
trivialPotato said:
Worked like a charm here.
Click to expand...
Click to collapse
mr3p said:
Just wanted to pass on this TWRP build for KKBL worked great. I ended up "downgrading" to JBBL in order to load a current LineageOS build.
Click to expand...
Click to collapse
I see the posts saying it works, but has anyone actually successfully flashed and booted (ie past the bootanimation ) any ROM Zip file using this recovery?
Or performed a backup and restore?
I ask this as I finally got around to creating an upgrade (from JBBL to KKBL) for my phone (an xt905 not an xt907) and the two ROMs I tried both boot looped on the bootanimation. Also, I get errors when i try to wipe my cache.
Is it just me?
-----edit-----
I got a PM saying that someone has managed to flash an LP ROM for KKBL using this recovery. So obviously I need to go back to the drawing board on my upgrade to KKBL...
I am considering adding PDS (ie FSD) backup to my TWRP builds see https://forum.xda-developers.com/showpost.php?p=74136332&postcount=9 it also applies to KKBL.
DragonFire1024 said:
I only asked because 1) wasn't mentioned in this thread specifically. 2) Not all devices require the bootloader be unlocked. 3) Why does it need to be a custom recovery? I still get confused about that from time to time because it just amazes me that it seems that's where things seem to always end up and sometimes seems to be a bit too convenient. I'm not vastly familiar with bootloader technology so that's where I scratch my head. I can install TWRP, get to all the settings and options, so why can't I just back up the proper files/imgs and flash the zip?
Looks like I'm going to have to rely on Sunshine then. I wish they accepted Bitcoin. It's that, or lose the phone to old age as it's components and functions fail slowly, one by one. I know I can reflash the stock firmware, it's been done a...few...times.
EDIT: Well s**t. Sunshine DOES accept Bitcoin. If I had known that ages ago...ugh
Click to expand...
Click to collapse
The boot loader has to be unlocked because of the nature of the boot loader itself. I ain't no expert, but based on my understanding and what I personally know, here is what a boot loader does:
A boot loader checks the various images (recovery, boot, radio, etc.) and if any of these are incorrect/unsigned (like a custom recovery), your device won't boot. This makes sense, because most users aren't flashing their devices, so when an image is unsigned something is VERY WRONG. Unlocking a boot loader basically turns off the signature check that the boot loader does. If the boot loader isn't checking each image than it will boot up fine whether you have a custom recovery or not.
Recently reacquired an xt907 after "losing" mine. Anyways I rooted with Kingroot and used the mrw root.sh script to switch to supersu. I had to use an older version if kingroot, 4.9.6 for it to work. I then used the Sunshine app to unlock bootloader for $25 and used terminal emulator to 'dd' TWRP to recovery. Everything is perfect and am glad all still works as such.
Now my point: is there an easy guide or something that I can use to port an updated TWRP image? May thanks to everything.
DragonFire1024 said:
Recently reacquired an xt907 after "losing" mine. Anyways I rooted with Kingroot and used the mrw root.sh script to switch to supersu. I had to use an older version if kingroot, 4.9.6 for it to work. I then used the Sunshine app to unlock bootloader for $25 and used terminal emulator to 'dd' TWRP to recovery. Everything is perfect and am glad all still works as such.
Now my point: is there an easy guide or something that I can use to port an updated TWRP image? May thanks to everything.
Click to expand...
Click to collapse
Easy is a relative scale to the person asking the question. Read and answer it for yourself. TWRP builds are muuuuuch simpler than ROM builds.
The following two may mean you do not have to build. I have never used them, as I built mine from source.
https://forum.xda-developers.com/android/general/unofficial-twrps-devices-source-code-t3833338
https://forum.xda-developers.com/android/apps-games/twrpbuilder-t3744253
https://forum.xda-developers.com/showthread.php?t=1943625
The question may also be better asked, after reading, in the thread above