Mods -- Feel free to delete if it's a repost.
Quick note -- I take no responsibility for your device, if you choose to install CWM and root, this is your decision, use this at your own risk.
After reading through a few posts and figuring out there is little support I could locate to Root using my macbook, thought I would jot down what I did to root my Wifi Note 8.0:
1 -- Download and install Heimdall:
http://www.glassechidna.com.au/products/heimdall/
2 -- Download & untar the CWM for my device pulled from here (you should end up with a recovery.img file when untarred):
http://www.droidviews.com/root-and-...te-8-0-gt-n5100-gt-n5110-gt-n5120-all-models/
4 -- Download Super SU Zip and push to device:
http://d-h.st/9M0
5 -- push (flash) CWM to your note using the command:
heimdall flash --RECOVERY recovery.img
6 -- reboot into CWM using the vol+,pwr,home buttons.
7 -- flash the SuperSU zip.
8 -- reboot and enjoy!
this method can also be use to flash twrp.
2014.10.16.: Update!
MICa.fighter said:
Hy guys! As you might noticed, the links in the OP which are pointing to the official files on the CM server don't work any more thanks to CM. I was sure this will come, but i still wanted to use the official links as long as they are working. I would change the links to my mirrors in the OP, but @Spannaa already made mirrors in his thread: Mirrors for official CM11S roms & OTA updates. I don't see any reason to have 2 threads with mirrors of the same files, so i taught I would keep this thread as a discussion on how to use those official files. I will modify the OP in the coming days accordingly.
Click to expand...
Click to collapse
I will keep the OP as it is for now, and I will modify it a little in the coming days!
Hy guys, i have seen posts about different versions of CM11S, but I haven't seen a collection of them. I collect all the stock images i can, so i taught i would share it with you guys. As the thread title says, these are official and untouched images of the stock CM11S. I share the official links where it is available. I will share four kind of files:
1. Recovery flashable zips of the complete ROMz: these are the oldschool .zip images that you can flash through recovery.
2. Fastboot images of the complete ROMz: these are fastboot.zip files, that should be used through fastboot. You need to set up Android SDK for fastboot on your computer and you also need to unlock your phone's bootloader in order to use them. For setting up the Android SDK and unlocking your bootloader, please follow this guide: [GUIDE] OnePlus One - How to Unlock Bootloader, Install Custom Recovery and Root, until you complete the first step: 1. Unlocking Bootloader. After that you have to put the fastboot.zip file into your platform-tools folder (its explained in the previous link), and extract it there, but also keep the zip there because you need that too. After that, you may follow the instructions of the Open Post of this thread: CyanogenMod 11S.
Note: The conventional fastboot oem unlock which unlocks the bootloader will wipe your phone. You can make backup before that with Helium app or through adb. Neither of them requires root.
Note: The last command in the CyanogenMod 11S thread's open post is:
Code:
fastboot update -w cm-11.0-XNPH25R-bacon-signed-fastboot.zip
The command will wipe your phone because of the "-w" option.
Note: if you get the error message during flashing in fastboot:
Code:
FAILED (remote: data too large)
Then you are probably not on the latest Android SDK with the latest required tools: Android SDK Tools, Android SDK Platform-tools, Android Support Library, Google USB Driver.
Click to expand...
Click to collapse
3. Stock kernel images: these are .img files of the stock kernel images. You can flash these in fastboot like this:
Code:
fastboot flash boot boot.img
If the filename is for example g7389215.img then it looks like this:
Code:
fastboot flash boot g7389215.img
4. Latest OTA incremental update zip: I will also share the latest OTA zip file. The CM11S OTAs are incremental updates, that means you need to be on the latest version before applying an update. Incremental means it only updates the changed files since the last update.
So for example the latest OTA ATM is XNPH33R. Before that was the XNPH30O. If you want to use the XNPH33R OTA zip you need to be on XNPH30O, because that is the latest version before the XNPH33R OTA (check reference table below). If you apply the OTA on an earlier version (for example, XNHP25R), the installation will be aborted most probably. Or if you succeed with the installation, it will break stuff most probably.
You can also grab the latest OTA update zip after you recieved the OTA file and downloaded it. You can find it in the cache of your phone and you will need root access. If you want to make a copy you should do so before you install the OTA.
Wipe the cache then you can flash the OTA update zip through recovery.
Reference table
ROM version / release date / kernel version
XNPH22R / 2014.06.06. / dunno
XNPH25R / 2014.07.03. / geb9c0a5
XNPH30O / 2014.08.11. / g7389215
XNPH33R / 2014.08.21. / g0ad30e5
XNPH38R / 2014.10.07. / g33fa374
Links
1. Recovery flashable zips of the complete ROMz:
XNPH22R
XNPH25R
XNPH33R
2. Fastboot images of the complete ROMz:
XNPH22R
XNPH25R
XNPH30O
XNPH33R
XNPH38R
3. Stock kernel images:
XNPH22R
XNPH25R
XNPH30O
XNPH33R
XNPH38R / torrent magnet mirror
4. Latest OTA incremental update zip:
XNPH38R
Also here are the previous OTA incremental update zips:
same rule, check reference table, only use it if you are on the latest previous version! Its incremental.
XNPH33R
XNPH30O
Njoy!
You might also be interested in zephiK's modem collection of recovery flashable zips for the One: http://forum.xda-developers.com/oneplus-one/general/ref-oneplus-one-modem-collection-t2858734
Thanks was waiting for something like this.
While I appreciate this, the 33R Kernel isn't working... I tried flashing with fastboot and no go.... I'm on 33R from OTA. I'm rooted and I currently have Franco Kernel installed... (And TWRP recovery)
To reiterate, it flashes fine but when I go to boot up it stays at the One+ logo screen
How did you try it exactly?
MICa.fighter said:
How did you try it exactly?
Click to expand...
Click to collapse
flashing with adb through fastboot
You can use rashr app https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools works like a charm
Nomelas said:
While I appreciate this, the 33R Kernel isn't working... I tried flashing with fastboot and no go.... I'm on 33R from OTA. I'm rooted and I currently have Franco Kernel installed... (And TWRP recovery)
To reiterate, it flashes fine but when I go to boot up it stays at the One+ logo screen
Click to expand...
Click to collapse
You are right, the file is broken, I'm sorry. I'm going to update the OP soon with working kernel image. I'm also going to share the latest OTA grabbed from cache.
Edit: updated OP with the new 33R links, and fixed the broken kernel image. I also explained how to use the kernel images.
Thank you so much
Great post op :good:
Waiting the recovery flashable zip of XNPH33R to download. ( I am currently on XNPH22R, unlocked bootloader, with TWRP)
I am going to flash the zip through recovery ( and then flash modem from zephiK's post).
I don't need to do anything with the kernel images ( I am guessing they are there for another reason), right?
mhxmhx said:
I don't need to do anything with the kernel images ( I am guessing they are there for another reason), right?
Click to expand...
Click to collapse
You don't need the kernel images.
All the rom zip files has a kernel (boot.img). The reason i posted the kernel images separately too because custom kernel users sometimes need them. If they want to go back to stock kernel or just want to keep a backup, they don't need to download ~460MB for just the kernel image, they can download only the kernel image which is 5-10 MB.
Thank you for your work!
Thanks a lot, after flashing few mods and custom kernel my phone feels laggy, I must go back to stock
After @zephiK modem list, this is one more most usefull thread Thanks !!
So could I just flash the 33r update from stock recovery if I'm on 25r? Or do I need to update to 30O then 33r
Added to OnePlus One Resources Compilation Roll-Up Thread
[INDEX]OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon
jherring002 said:
So could I just flash the 33r update from stock recovery if I'm on 25r? Or do I need to update to 30O then 33r
Click to expand...
Click to collapse
The OTA Update is incremental, which means it only updates the files that changed from the last update, in this case XNPH30O. So you sould NOT try to flash the OTA Update of 33R if you are not on 30O.
If you want to update to 33R from 25R, there are a couple of options, for example:
A) update to 30O through OTA, then you can just flash the 33R OTA update, OR
B) download the 33R full rom zip, reboot to recovery, wipe cache and flash away OR
C) make a backup of your apps and settings, through adb, or Titanium Backup, or with Helium (TB requires root), then download the 33R fastboot.zip and flash through fastboot as described in the first post. If you already have the bootloader unlocked you can skip that step. After you are done, boot up the phone, then restore your backup. The flashing method described in the open post of CyanogenMod 11S thread will wipe your phone.
The "safest" method is A, the "cleanest" method is C.
timmaaa said:
Added to OnePlus One Resources Compilation Roll-Up Thread
[INDEX]OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon
Click to expand...
Click to collapse
I'm out of thanks so i thank you here timmaaa :good:
Is there a flashable 30O file via recovery?
jherring002 said:
Is there a flashable 30O file via recovery?
Click to expand...
Click to collapse
Unfortunately no, but I can upload the 30O original OTA zip for you i grabbed that from cache too. You can flash it on 25R after a cache wipe. Or use it with the 25R recovery flashable zip: flash 25R zip then 30O OTA zip.
MICa.fighter said:
Unfortunately no, but I can upload the 30O original OTA zip for you i grabbed that from cache too. You can flash it on 25R after a cache wipe.
Click to expand...
Click to collapse
That would be nice. I went from 33r to 25r to see the difference in battery.
It's not that different so I wanted to go back, but when I check for ota there is not one. Says in up to date.
jherring002 said:
That would be nice. I went from 33r to 25r to see the difference in battery.
It's not that different so I wanted to go back, but when I check for ota there is not one. Says in up to date.
Click to expand...
Click to collapse
Okay I'm gonna upload the 30O OTA zip too, it will be available in the first post in a few minitues. If you want to go back to 33R you could also use the 33R full rom zip, just wipe cache and you can flash it on 25R. Make a backup before it, but i don't think there would be any problem.
Edit: Done!
This Thread contains the STOCK RECOVERIES for HTC One M8 (Indian Variant) (CID: hTC_038)
Many people have been requesting for the stock recoveries for hTC_038 as they all are not available on other threads.
COLLECTION OF STOCK RECOVERIES (LINKS):
1) Recovery 1.56.720.6
2) Recovery 2.10.720.1
INSTRUCTIONS:
1. Flash the required Nandroid backup. (It is optional for users using stock rom)(Don't ask me for the nandroid backup, I dont have it.)
2. If rooted then, flash unsuperuser.zip to unroot. (Google It)
3. To return back to stock recovery, use "fastboot flash recovery recovery.img" using adb. Rename the downloaded file to recovery.img for ease.
4. Reboot.
BOOM, You have the Stock Recovery !
Questions :
1 : why do you keep on opening and closing threads for this ?
2 : why didn't you just link it in the collection of backups thread as there are many recoveries to be found there ?
http://forum.xda-developers.com/showthread.php?t=2701376
Here if you missed it .......
Please use the existing thread for stock recoveries. Closed
Warning: Follow this instruction at your own risk. If any damage occurs you should blame yourself.
You need following things:
>PC Driver for SOL23
>ADB interface for PC
>SOL23(Unlocked Bootloader must!!!)
handset running Lastly updated (14.3.C.0.300) stock ROM
>Latest Lollipop (14.6.A.1.236)
Central Europe1 International Generic Rom for (6903)
>Kingroot.exe for PC
>NUT's XZdual recovery zip file v2.8.26
>PRFcreator V1.3
>(SR5-SuperSU-v2.82) zip file
>TWRP 3.2.3-0-Honami unofficial (.Img) file
>Linease unofficial OS 15.1 for sony z1(C6903)
by Remim7 or Raschad
>MindtheGapps ARM 8.1
>RZ kernel(v3) for sony z1
>(14.3.C.0.300) stock FTF
Step by Step:
WARNING!!! these steps are not in details. Do some google search for each step before execution!!!
1. Install driver & ADB interface on your PC.
Turn on USB debugging & turn off verification over USB from developer option. Root stock SOL23 rom using kingroot PC. Reboot your Phone.
2. Extract XZdual recovery to C drive of your PC and install it to your SOL23 Following official instruction (may fail initially, try at least 4 times).
When successful , your phone will be rebooted into recovery. Create Nandroid backup. :good:
3.Run PRFcreator on your PC. Select 3 files in this app.
1.International Rom ftf(14.6.A.1.236)
2.SuperSU zip file
3.XZdual recovery zip file.
!!!Must must Must exclude Band !!!
It will make pre rooted international rom flashable zip with xzdual recovery. :good:
4. Clean Flash this pre rooted international stock Rom to your phone using xzdual recovery.
Now your phone is C6903. :good:
5. Enable USB debugging again. Connect it to your PC. Enter fastboot mode using ADB command.
Flash TWRP 3.2.3-0-Honami using fastboot command.
Temporarily boot into new TWRP using following fastboot command-
(Fastboot boot recovery 3.2.3-0-Honami.img).
Phone should be booted into this version.
6. Clean Flash custom Linease Oreo 15.1 ROM
from TWRP.
Flash MindtheGapps ARM8.1
Flash Add-on SU (optional)
Flash RZ kernel V3
Enjoy Custom Oreo Rom on your SOL23! This fantastic flagship phone will never be old until Hard Bricked!
Pros: Everything is working fine. Phone seems very smooth, Now I am using Oreo, :fingers-crossed:
Cons: NFC not working.
Attention: If anything goes wrong, u can Flash stock FTF using flashtool.
Flash a custom rom directly to your pixel 3a or 3a xl using google factory image zip.
I didnt expect this to work but it did. i flash my pixel 3a alot doing development experiments and found it a hassle to first flash the whole device using the google factory images then using adb sideload to flash the custom rom.
so i had an idea. what if i could flash all the partitions with fresh images and flash the custom rom at the same time. i could then control which slot gets flashed and avoid the process of flashing stock first then rebooting into the bootloader flashing the custom boot then rebooting to the recovery and adb sideloading the custom rom.
AFAIK this will only work for google devices with factory images downloaded from the google factory image site.
so lets get started. Btw i am in no way responsible for any damage this may cause to your device by following this how to. your warranty is now void.
so as you know you should have an unlocked bootloader. I will not go into that process here so you will need to look that up on your own and come back.
so go here and download the latest factory image according to the android version you would like to flash.
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
while thats downloading go ahead and grab the payload.bin dumper and set it up. you can find that here.....
GitHub - vm03/payload_dumper: Android OTA payload dumper
Android OTA payload dumper. Contribute to vm03/payload_dumper development by creating an account on GitHub.
github.com
next find the custom rom you would like to flash according to the android version of the factory image you just downloaded
extract the custom rom zip and cd into the folder created from extracting it. now copy the payload.bin from there and paste it into the payload dumper folder you downloaded and set up in the previous steps and extract the payload.bin
now extract the factory image zip you downloaded according the android version of the custom rom zip and cd into those folders and create a new folder calling it what ever you like but for the intent of this guide call it stockimage.
now extract the contents of the stock image zip into the folder you just created.
now open another window and go to the output of the payload dumper and move the contents of that folder into the stockimage folder you created in the previous step and replace the stock partition images with the custom partition images from the payload dumpers output
when that completes zip up everything in the stockimage folder and name it the same name as the zip in the factory images folder we unzipped earlier. then replace the stock image zip in that folder with the new one we just created.
now rebbot your pixel 3a or 3a xl into the bootloader and run sh flash-all.sh and when it completes you will now boot into the custom rom instead of the factory stock rom.
so now you know how to flash a custom rom all in one shot using fastboot and avoiding the adb sideloading of the custom rom zip.
tested and working on Google Pixel 3A
enjoy