RUU stands for ROM Update Utility. This is a utility that is run via a .exe file that is used to flash a stock ROM, stock radio, stock splash screen, stock recovery, and stock firmware of a device. The utility performs a cleaning of the NAND memory of the device before flashing the included stock software. So a RUU is often suggested as a way fix common problems and to unroot a device. The utility also runs a set of checks on a the
a device before flashing such as CID (Carrier Identification), battery level check, and firmware version check.
A custom RUU is does the same as a RUU but it has been modified to not run the CID check and sometimes other security checks. You can flash custom ROMs, different radio versions, splash screens, and firmwares. You can even use a custom RUU to flash each of these individually
A .apk file, or Application Package File, is the type of file used to distribute and install Android applications files in the Android OS. These files are in zip file format and contain all needed files, scripts, resources, and etc. that the application needs to function.
Related
Hello, friends,
I use the custom rom 23566 with driver version 3.003c, can I flash back to the official rom 21883 with driver version 2.003?
I am worrying whether I will brick my S200...
Please give me some advice, and I will appreciate your help very much!
you should be ok. (i have not try to downgrade my rom, so flash at your own risk!)
make sure you have over 50% battery before you flash.
netnerd said:
you should be ok. (i have not try to downgrade my rom, so flash at your own risk!)
make sure you have over 50% battery before you flash.
Click to expand...
Click to collapse
Thnk you for answering.
I want know whether someone had tried it.
I feel that the new roms exhaust battery very fast, I would like to try some old roms and old drivers. My rom language is simple Chinese, there is no official roms with 3.003c for simple Chinese. I did not think the drivers work well...
no u cant. once you upgrade to official latest ROM. old official ROM can not be revert back. because the official ROM can detect version. once it found your ROM is the latest. it does not allow you to flash back to previous official version.
u can flash it to other cooked ROM and then only flash back to the previous Official ROM.
i tried it.
fulat said:
no u cant. once you upgrade to official latest ROM. old official ROM can not be revert back. because the official ROM can detect version. once it found your ROM is the latest. it does not allow you to flash back to previous official version.
u can flash it to other cooked ROM and then only flash back to the previous Official ROM.
i tried it.
Click to expand...
Click to collapse
That is wrong! Download Acer Original Firmware version 2.0, extract it with ToolsByANPER to get flash.bin and extrom.bin.
Download one of Custom ROMs, i doesn´t matter which one (my Modular ROM or Arto´s Clean ROM). Extract the zip file.
Now copy in the original Acer flash.bin and extrom.bin into the extracted Custom ROM folder and overwrite the existing files.
Start the flash procedure with ACER_EUU.exe and follow the instructions.
Why do people state something and not search little bit more?
brainmaster said:
That is wrong! Download Acer Original Firmware version 2.0, extract it with ToolsByANPER to get flash.bin and extrom.bin.
Download one of Custom ROMs, i doesn´t matter which one (my Modular ROM or Arto´s Clean ROM). Extract the zip file.
Now copy in the original Acer flash.bin and extrom.bin into the extracted Custom ROM folder and overwrite the existing files.
Start the flash procedure with ACER_EUU.exe and follow the instructions.
Why do people state something and not search little bit more?
Click to expand...
Click to collapse
Thank you very much, guy. I think I have got answer from you. I think you mean that the driver information on the first screen is included in the flash.bin, do you?
As I know, the .amf file can be extracted to about 8 files, including .mbn and .bin files. And we can only flash any of them at one time( but the partition.mbn always must be flashed at the same time), a Chinese friend had tried and got these conclusion. I wrongly thought that the driver information on the first screen is included in one of the .mbn file. So I just thought that these "bios" files(.mbn files) are different in different rom version. I will check that whether they are the same.
sinocreate said:
Thank you very much, guy. I think I have got answer from you. I think you mean that the driver information on the first screen is included in the flash.bin, do you?
As I know, the .amf file can be extracted to about 8 files, including .mbn and .bin files. And we can only flash any of them at one time( but the partition.mbn always must be flashed at the same time), a Chinese friend had tried and got these conclusion. I wrongly thought that the driver information on the first screen is included in one of the .mbn file. So I just thought that these "bios" files(.mbn files) are different in different rom version. I will check that whether they are the same.
Click to expand...
Click to collapse
You can also just extract the original acer 2.0 ROM and put the cracked ACER_EUU.exe from Custom ROM folder into original Acer 2.0 ROM folder and start the flash procedure.
That is gonna give you also the 2.0 Radio and bootloader.
If you do as i first said - then you will get 2.0 firmware but with 3.0 Radio and bootloader - (3.0 Radio is better because Acer thit some fixes on the GPS, anyway newest Radio is always better).
EDIT: The information on the bootscreen is about Radio and Bootloader, not about drivers - drivers are integrated into flash.bin.
I have checked that, for official 3.003b/c, the only one file different is appsboot.mbn .
Of cause, image.bin and extrom.bin are different between different languages. It's obvious.
The "partial update method" seems valuable for other system part (such as RADIO) keep the same.
Moreover, for the recent patch, Patch_Acer_1.0_WM65_GPS signal , the major change is amss.mbn .
For ENPRG8650.hex and NPRG8650.hex, these two files could be checking mbn files are correct.
Hello,
Simple inquiry with regards to flashing the new CM7 RC4 to Xperia X10a
Device is currently on CM 6.1.3. I have downloaded flash tool as baseband version is .55
I wanted to confirm the proper protocol in order to accomplish a successful flash. Having read through the posts/tutorials I've gathered I will need to flash the lower grade baseband version .52 via flash tool.
As my device is currently on modded firmware would I need to flash back to 2.1 utilizing flash tool. Whats confusing me here is the mentioning that the baseband and kernel is included in the CM7 download file. Q/A for flash tool states it can flash original images 1.6>2.1. As I am currently on 2.2 how does this impact flashing of the appropriate baseband in order to upgrade to CM7.
Furthermore if the baseband is included in the ROM file download. Does that implicate a one step process via flash tool for successful flash to CM7. Would I need an original firmware file to work in tandem with the custom rom via flash tool? Or must I flash baseband seperate from ROM
Any clarification is much appreciated.
Thanks everyone
** Flashed over as per suggested instruction. Experiencing random reboot incidents with CM7
Reviewing online information with regards to a fix. Device is randomly power cycling when left idle and when Browser application is launched from dock bar or app drawer.
Any ideas or implementations for a fix would be appreciated as this is quite frustrating.
- Ive noticed that the instructions for rom installation state to allow the device an idle period of a minute before having it go through an automatic power cycle. however this doesnt seem to happen. upon first boot as soon as i attempt to turn on wifi, the phone will automatically boot itself. speculating that wifi may be involved with the above mentioned incident. still researching.
- Attempted reflash. Skip past initial google setup. Activate Wifi, authenticate with a network. Reboot and disconnect from wifi. Reboot to xrec, fix permissions. Unsuccessful. Same result.
- Installed wififix in apps folder. Same result. Phone will power cycle when downloading apps from market via wifi.
I think the same baseband file is included in the rom's zip file.
first use flashtool to go to .52 baseband then flash the rom in xrecovery.
Sent from my X10i using XDA Premium App
1- go here http://forum.xda-developers.com/showthread.php?t=960527
download 2.0.52
2- install 2.0.52 via flashtool
3- go here http://forum.xda-developers.com/showpost.php?p=10561990&postcount=2
download the rar file
4- extract update.zip , gapps.zip from the rar file
5- using xrecovery flash update.zip reboot then flash gapps.zip
thanks everyone
as per DynamicRam. procedure worked successfully. did want to be absolutely sure to avoid any mishaps, bad flashes, or bricking of device.
thanks again
Reflashed ROM and gapps within same session. Same issue being experienced. Will attempt another flash.
Introduction:
Softbank Streak roms are different from normal streak roms as they merely patch existing files instead of wiping and reinstalling everything like normal updates.
Softbank roms are like stock patch OTAs on the Nexus One, you must have a more or less unmodified setup or else it wont install.
If your phone has been modified and now you cant reinstall/upgrade to newer softbank roms here are the stock files to do that.
Download:
313 Base (Not available)
324 Base
344 Base
364 Base
Install Instructions:
There are two methods of correctly installing these roms:
Installing purely though fastboot
Installing with nandroid
BOTH METHODS WILL WIPE ALL DATA
Installing purely though fastboot:
Tools needed:
Basic understanding of your OS's command prompt/shell
Ability to enter fastboot mode and recovery mode on Streak
Fastboot installed and set up properly
Understanding on how to use fastboot
One of the base files to install
Matching pkg from here
Install instructions:
Extract the rom base you wish to install
Copy the matching pkg to your sd card and rename to 'update.pkg' (ex: if you downloaded the 324 base, download the 324 pkg)
Enter fastboot mode
Flash boot/system/recovery via fastboot
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
After flashing all 3 images reboot and enter recovery mode
Select: 2. Install update.pkg from sd card
Allow update to install itself
Finished
Installing with nandroid:
Tools needed:
Streakmod or later already installed
Ability to enter recovery mode on Streak
One of the base files to install
Matching pkg from here
Install instructions:
Extract the rom base you wish to install to sdcard\rom_backup
Copy the matching pkg to your sd card and rename to 'update.pkg' (ex: if you downloaded the 324 base, download the 324 pkg)
Enter recovery mode
Select: 2. Install update.pkg from sd card
Go to advanced -> nandroid -> full restore -> <version to restore to>
Install with nandroid
Reboot and let streak fully load
Restart after seeing initial setup screen
Reenter recovery mode and select 2 again
Allow update to install itself
Finished
Notes:
You MUST install with the update.pkg on top of the base, installing the base by itself is only half of the rom.
You CANNOT safely manually install everything in the pkg, you must use the update process.
Unless you must use the Softbank stock rom it is highly recommended to NOT use them as carrier branded roms have many limitations.
Rooting is not required during any of the process, nor does it affect the process in any way.
Later roms can simply be installed by 'settings -> about phone -> system upgrade' as long as the system files have not been modified.
Thanks:
AWD_Manic for providing initial 324 boot and system images
Changelog:
Aug 8, 2011: Released initial guide
Looks like Softbank released an update. I keep getting the annoying message from 157 cause I'm using a custom ROM and never downloaded the official FOTA.
http://mb.softbank.jp/scripts/japanese/information/fota/detail.jsp?id=20111213183058785
366 was released in december or so, which was a very minor update.
New Softbank Rom: 366 contains some of the release notes.
They changed 366 to be a full pkg so it can be updated like any normal pkg
Oh I see... Sorry, missed that thread.
Meh, I was hoping they released Gingerbread officially. I guess I'll have to download it anyway unless you know another way to stop their spam.
TheManii said:
Introduction:
Softbank Streak roms are different from normal streak roms as they merely patch existing files instead of wiping and reinstalling everything like normal updates.
Softbank roms are like stock patch OTAs on the Nexus One, you must have a more or less unmodified setup or else it wont install.
If your phone has been modified and now you cant reinstall/upgrade to newer softbank roms here are the stock files to do that.
Download:
313 Base (Not available)
324 Base
344 Base
364 Base
Install Instructions:
There are two methods of correctly installing these roms:
Installing purely though fastboot
Installing with nandroid
BOTH METHODS WILL WIPE ALL DATA
Installing purely though fastboot:
Tools needed:
Basic understanding of your OS's command prompt/shell
Ability to enter fastboot mode and recovery mode on Streak
Fastboot installed and set up properly
Understanding on how to use fastboot
One of the base files to install
Matching pkg from here
Install instructions:
Extract the rom base you wish to install
Copy the matching pkg to your sd card and rename to 'update.pkg' (ex: if you downloaded the 324 base, download the 324 pkg)
Enter fastboot mode
Flash boot/system/recovery via fastboot
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
After flashing all 3 images reboot and enter recovery mode
Select: 2. Install update.pkg from sd card
Allow update to install itself
Finished
Installing with nandroid:
Tools needed:
Streakmod or later already installed
Ability to enter recovery mode on Streak
One of the base files to install
Matching pkg from here
Install instructions:
Extract the rom base you wish to install to sdcard\rom_backup
Copy the matching pkg to your sd card and rename to 'update.pkg' (ex: if you downloaded the 324 base, download the 324 pkg)
Enter recovery mode
Select: 2. Install update.pkg from sd card
Go to advanced -> nandroid -> full restore -> <version to restore to>
Install with nandroid
Reboot and let streak fully load
Restart after seeing initial setup screen
Reenter recovery mode and select 2 again
Allow update to install itself
Finished
Notes:
You MUST install with the update.pkg on top of the base, installing the base by itself is only half of the rom.
You CANNOT safely manually install everything in the pkg, you must use the update process.
Unless you must use the Softbank stock rom it is highly recommended to NOT use them as carrier branded roms have many limitations.
Rooting is not required during any of the process, nor does it affect the process in any way.
Later roms can simply be installed by 'settings -> about phone -> system upgrade' as long as the system files have not been modified.
Thanks:
AWD_Manic for providing initial 324 boot and system images
Click to expand...
Click to collapse
How can i change the APN without rooting my Streak?
Sent from my 001DL using xda premium
You need to root and set
ro.build.OEM_PRESET_APN_LOCK=0
ro.build.OEM_PRESET_APN_HIDE=0
in the build.prop.
Those entries are repeated multiple times, you can either set them all or remove all the redundant entries
Something weird happen on my streak. After installing the 366 update my OEM Version Change but my baseband did not chane it remains at 364. I am not experiencine blinking capacitive buttos. Should i keep my baseband or should i need to flash the 366 baseband.
Sent from my 001DL using xda premium
Dead Links
Is anyone able to point me in the direction of some live download links that may work for the softbank base files?
Really keen to give this a try. :good:
If you regularly install/test custom firmwares, ROMs and mods on your HTC One, it can be quite annoying and time-consuming if you want to go back to the latest stock software with official manufacturer OTA support (for example, to check if the latest official OTA update has been released for your region). Flashing the RUU is arguably the easiest and fastest way, but many of us have only older RUU's available which means having to download some quite big OTA updates every time. To avoid this inconvenience, i've done some research about the various methods to return to the latest stock version as hassle-free and as quickly as possible and i've come up with the following solution. This idea is not ground-breaking and might not be new to some (or most) of you, but i believe this guide should be useful for "noobs" or those who never thought of or didn't know how to handle OTAs and also to find the easiest and fastest way to swap any custom software (ROM/firmware) on your HTC One with the last 100% stock installation right before you flashed a custom recovery.
The procedure described below tries to eliminate the need to look for and flash stock firmware and stock ROMs uploaded by others, which may not necessarily exactly match with the original stock software of your phone especially since there exists dozens of HTC One variants. Using downloaded stock firmware/ROM from others might cause incompatibilities, degradation in performance, lost of signal, poor reception, etc. Ideally, you want to be able to flash whatever ROM/firmware and at any time, if you wish, you should be able to switch back to your own stock ROM and firmware. This is usually done by flashing your RUU (Rom Update Utility) according to your phone's MID and CID. However, most of you would need to go through an annoying and time-consuming update process to download several OTAs before finally reaching the current latest stock version. But here's a solution!
Minimum requirements:
1. Your HTC One's bootloader must be unlocked.
If your device is already S-OFF and if you relocked/locked your bootloader, then you can unlock the bootloader without having to use the official htcdev website. Just follow this guide to set the Bootloader as UNLOCKED: http://forum.xda-developers.com/showthread.php?t=2497712
2. You need to find your device's RUU (decrypted is even better as it allows going through the process faster) or your 100% stock software backup (firmware and ROM). If you made a nandroid backup after unlocking the Bootloader, it won't work since some data was wiped from your phone's memory during the unlocking process from the official htcdev website.
It's advised to use the RUU to restore which is specifically designed for a set of devices according to their MID and CID, rather than trying your luck at finding a compatible stock firmware and ROM for your HTC One variant. Here's a thread with a collection of RUUs and stock firmware/ROMs: http://forum.xda-developers.com/showthread.php?t=2428276
3. Your device should be S-OFF.
This is not an absolute requirement but S-OFF makes the whole procedure much easier. For the purpose of this guide, it will be assumed that your device is S-OFF.
Advantages of this method:
1. You will save time by being able to restore back to the latest 100% stock version very quickly (some OTA updates are around 400 MB which can take some time to download). You will only have to download the OTA's one time and then back up these OTA's to use later for updating/restoring your stock software.
2. You won't need an internet connection to update to your last stock version backup. The update process to previously downloaded (and backed up) OTA's will not require an internet connection. However, you will have to download any newer OTA's if available.
3. You will not have to rely on other sources to find your latest stock firmware and stock ROM. Therefore, you can be certain that you're getting a perfectly matching firmware and ROM for your specific HTC One model (the restored firmware and ROM will be exactly as if you never tampered with your device, with official manufacturer OTA support).
4. You will not have to downgrade if using an older RUU or older stock firmware/ROM, and then have to update it again via OTA. Your HTC One will be restored to 100% stock with the same software version just before you flashed a custom firmware/ROM.
5. If you absolutely need to run the RUU to go back to 100% stock, then you will not have to run the RUU process more than once (which will wipe all your nandroid backups as well as all your data, assuming you have a decrypted RUU, otherwise you will have to run the RUU twice only).
Procedure:
To summarize, if you want to go back to 100% stock using the method in this guide, all you will have to do is restore your nandroid backup and flash the firmware from the latest OTA. You will then get stock software with full OTA support within a few minutes from a custom installation. The method itself consists of handling official OTAs and extracting the most recent firmware in order to restore. But you will need a starting point where your device is 100% stock and able to receive and install official OTAs from the manufacturer. Let's assume that your HTC One is 100% stock. Whatever means you used to reach 100% stock, you will need it again. So, keep that RUU (preferably try to find your decrypted RUU zip) or stock files handy.
Check if you have any OTA update available:
No update available
If no OTA updates are available for your device, you can flash your custom recovery and then do a nandroid backup (very important). Then, you can root, flash a custom ROM and if you're S-OFF, you can even flash custom firmware.
Going back to stock: if you want to check for OTA availability at any time or you just want to go back to 100% stock, the easiest and safest way is to run your RUU. But if you found your decrypted RUU zip, you can go back to stock even faster; first restore your nandroid backup and then extract firmware.zip from the decrypted RUU zip and flash it. That's it. You're now back to 100% stock. You can check if there are any available OTAs and then go back to using custom ROMs again if you like.
Update available
Here is the more interesting part of this guide:
1. You will need the original firmware.zip file for your current stock software version. If you ran the RUU to go back to stock, extract rom.zip (follow this guide: http://forum.xda-developers.com/showthread.php?t=2497614) and then extract firmware.zip from the decrypted RUU rom.zip file. If the RUU rom.zip is not decrypted, it will give you an extraction error about all the files contained within being corrupt. In that case, you should try to find a decrypted version of the same RUU or decrypt it yourself (requires Linux, as decrypting an RUU is currently not possible on other OS). Use Winrar/Winzip to open the firmware.zip and extract recovery.img and place it in your adb folder.
2. Check for software update in the Settings menu. If you get OTA update notification, accept it. Note the file size of the OTA download, as it'll be useful to easily identify it later when searching in your device's internal memory. Let it download but do not install it. Select the option "Install Later" when prompted.
3. In the Settings menu, disable fastboot and enable USB Debugging.
4. Flash custom recovery. Root your device. Boot up to Android.
5. Install ES File Explorer from the Play Store (it's free) and give it root permission from its settings. Use ES File Explorer to search for the OTA on your phone. I found Root Explorer to be much faster at searching files although it's a paid app. You will usually find the downloaded OTA in your /sdcard/Download/ folder or /data/data/com.android.providers.downloads/cache/ folder. The OTA will have the keyword "OTA" in its filename and it will be a single zip file. You can also confirm that it's the OTA file by its file size from the earlier OTA pop-up notification. If you still can't find your OTA zip, you can search for "OTA" or "zip" through ES File Explorer or Root Explorer (much faster). Then go through the search results. Here's the original filename of one of my OTA's: OTA_M7_U_JB_50_S_HTC_Europe_2.24.401.2-1.29.401.2_R_P_release_325145_signedn3pctn48i51c9iue.zip. When you've found the OTA, copy it using ES File Explorer to the /sdcard/ location on your phone. Then plug in a USB cable to your HTC One and copy the OTA to a safe place on your PC hard drive.
6. Now, connect your phone via USB, reboot and go to your bootloader. We'll be flashing recovery.img from step 1. Use command "fastboot erase cache" then "fastboot flash recovery recovery.img" and finally "fastboot reboot". Now, you have 100% stock again with OTA support. The SuperUser/SuperSU app will still be visible on your phone but it won't work since the su binary will have been wiped during the stock recovery restore process.
7. Check for OTA software update again from the Settings menu. Install the downloaded file through the update notification menu. But if the update re-downloads, cancel it. Instead, you can manually flash it by copying the OTA zip to the phone's internal memory (don't have to rename the OTA zip but for simplicity, rename it to update.zip) and go to your Bootloader. Select Recovery using the Power button and then press the Power and Volume Up buttons to load the stock recovery menu. Then, select 'apply from phone storage' and navigate the menu as you would in a custom recovery to find update.zip and select it to install. It will follow the official update procedures and will reboot a few times before going back to your homescreen. Check attachments below for the stock recovery menu and options.
8. When your phone reboots, check for OTA again. If update is found, download it but choose "Install Later".
9. Then, just follow the same steps above; 4 through 8. Redo the same steps to copy the OTA to your PC and extract firmware.zip. The principle is that you should backup all the successive OTAs until there are no more updates available. The very last OTA's firmware.zip is the most important file. Keep it separately from the other firmwares. You should also save the previous complete OTA zips to be able to update quickly if you ever need to run RUU again.
10. After you've made a backup for the last OTA zip file, check for software update and install the already download OTA zip through the normal update notification menu. If the OTA update re-downloads, cancel it and do a manual flash for the OTA update that you saved previously, as explained in step 7. Note that an official OTA will update both the firmware and ROM.
11. Then, flash a custom recovery and make a complete nandroid backup to secure your last updated stock ROM. Copy the nandroid backup to your PC. Keep the nandroid backup and the last firmware.zip file (extracted from the last downloaded OTA zip file) safely as these two files are the only ones you will need to restore quickly back to 100% stock with OTA support, unless you were to run the RUU, in which case, you'll have to install all the OTA zip files successively.
12. Now, you can flash whatever you like on your HTC One. If you're S-OFF, you can flash custom firmware as well.
Going back to stock: if you want to check quickly if any OTA's are available or just want to easily go back to 100% stock software, all you have to do is first, restore the last nandroid backup of the stock ROM and then flash the firmware.zip from the last OTA update that you downloaded. That's it. Now, you can check and update easily to any new OTA that might have been released while your device was on custom ROM/firmware. Obviously, you can also backup any available OTA's, by following the same steps above.
I will probably expand this guide further if there is any interest in it.
If this guide was helpful to you, just press the "THANKS" button!
Hi, I found the guide useful, specially now with the upcoming 4.4 OTA. I'm confused thou, I heard you can't apply an OTA having a custom recovery, is this true? If so, shouldn't you have to flash stock recovery after loading a nandroid backup from recovery to be able to receive OTA's?
Arjen_Arg said:
Hi, I found the guide useful, specially now with the upcoming 4.4 OTA. I'm confused thou, I heard you can't apply an OTA having a custom recovery, is this true? If so, shouldn't you have to flash stock recovery after loading a nandroid backup from recovery to be able to receive OTA's?
Click to expand...
Click to collapse
You need to have 100% stock ROM and stock recovery in order to successfully apply an official OTA update. In order words, if you have custom recovery, you won't be able to update. You need to flash in the following order: stock nandroid backup, stock recovery, then download/install any new OTA.
I wonder whether there is help for someone who thought he knew how to flash a kernel but apparently is deluded. I have the original nexus seven Wi-Fi tablet android version 4.3 build number JWR66V. The system still wants to update me to 4.3 because I ripped some files out of the cache directory to prevent OTA updates. I have both fastboot and adb. I have read the stickies about flashing.
The phone is rooted and the bootloader is unlocked. I use TWRP custom recovery, and it's a good thing, because I solidly bricked myself up just trying to get my lollipop. I know there are tools to root a nexus seven even with stock lollipop, so I thought I'd upgrade my phone to stock lollipop and then use one of those methods. I tried both the stock lollipop kernel and the one provided by chain fire, which I understand is rooted already. (I'm assuming upgrading to lollipop will lose me my root, unless I want to recover back to 4.3.)
I tried to do these things a couple of different ways. When I tried fast boot, I got the message "error: neither -p product specified nor ANDROID_PRODUCT_OUT set". There was a YouTube video suggesting how to deal with this error message. I'm pretty sure I followed the instructions but no go. (I was using the "flash all" command.) This was after I had put the file containing lollipop in the directory, both zipped and unzipped (so that I had an .img file instead of a zip file). I tried using both the zip file with all of the lollipop partitions and the system image file individually. No go. I also had a message that android-info.txt could not be found, even though it was in the same, working directory.
I could be wrong but I don't think you can install a complete updated kernel from a file on the device. I think that works only with update.zip.
I'm still thinking fastboot is my best bet, but there are dependencies apparently and I don't know what files to include in its directory. Then, am I wise to go to stock and then root, or should I simply flash the stock kernel already rooted? I assume that's what chainfire is providing, correct?
I notice the lollipop official ROM nor Chainfire’s supposedly-rooted image have any file named nakasi. I have only .img files, no .zip files.
I found a dozen sets of instructions on how to flash a kernel but something I need is missing from all of them. Does anyone know what it is or can anyone offer some helpful advice?
Thank you,
Leon M.