Related
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!
Before you do anything else, make a backup. do it now.
don't even read anything else until you've done that.
seriously. stop reading. make a back up. you reading this means you're getting ready to start flashing things when you don't know if it will work.
download the modified script OTA for 38R from
here
courtesy jaggy
download
CMKeyguard.apk
from
http://s000.tinyupload.com/?file_id=06718662084607714036
(thanks to ethanmars)
and follow the instructions on the side of the download page
after you follow the instructions regarding cmkeyguard, as written on it's download page from the link i provided,
reboot into recovery
flash the modified script OTA for 38R
at this point, i flashed a superuser zip (i use supersu, but superuser would probably work. i flashed this 'just in case'. i don't know if it works if you do not flash it)
i also flashed the 61 gold AK kernel for the 11S here
AK is a great developer. probably the most responsive one from whom i've heard this dude
anyway, that worked. before trying to flash 38R, i was running 33R with ak, and a modified lockscreen using this method thanks to this guy.
happy hunting.
this worked for me.
this worked after other methods would fail. i had to go through multiple restores.
my problem was that i was running the 'custom' slide screen on stock 11s, but modified as per
this thread
by this guy
i had been getting multiple 'cmlockscreen' failures, preventing it from booting properly.
Damnnnnnn i did not realise your thread.... I did a clean flash of 38R instead..... But still great work for putting this up!
After a half day war with this update yesterday, i've succeded by doing almost the same you say. by the way, thanks for the tips.
after 2 hours try fixing yesterday, I found the solution thanks to Vomer post, flashing throught fastboot the system, boot and twrp img... :angel:
timothydonohue said:
Before you do anything else, make a backup. do it now.
don't even read anything else until you've done that.
seriously. stop reading. make a back up. you reading this means you're getting ready to start flashing things when you don't know if it will work.
download the modified script OTA for 38R from
here
courtesy jaggy
download
CMKeyguard.apk
from
http://s000.tinyupload.com/?file_id=06718662084607714036
(thanks to ethanmars)
and follow the instructions on the side of the download page
after you follow the instructions regarding cmkeyguard, as written on it's download page from the link i provided,
reboot into recovery
flash the modified script OTA for 38R
at this point, i flashed a superuser zip (i use supersu, but superuser would probably work. i flashed this 'just in case'. i don't know if it works if you do not flash it)
i also flashed the 61 gold AK kernel for the 11S here
AK is a great developer. probably the most responsive one from whom i've heard this dude
anyway, that worked. before trying to flash 38R, i was running 33R with ak, and a modified lockscreen using this method thanks to this guy.
happy hunting.
this worked for me.
this worked after other methods would fail. i had to go through multiple restores.
my problem was that i was running the 'custom' slide screen on stock 11s, but modified as per
this thread
by this guy
i had been getting multiple 'cmlockscreen' failures, preventing it from booting properly.
Click to expand...
Click to collapse
Hi there! Today i had the OTA finally on my way but i had the modified lockscreen. I then came across your post and i tried to follow your step but with no luck:
1) the link to the OTA are just member profile but i think i can find the modified ones in the "official" thread in here
2)when i tried to perform the action listed in the page you linked to the CMkeyguard.apk i cannot delete the apk from my phone and i don't know how to do it from the PC. I tried then to flash it with the .zip provided by NunHugger (the creator of the modified lockscreen) but still no luck with the original update.
there is a way to perform the ota directly from the updater on the phone or i have to do it from the TWRP with the modified one only?
Also, reading through the thread of the lockscreen, i've read that i can perform a flash of boot.img... question is where to find it?
EDIT: I found the boot.img into the toolkit, so if i perform a flash it should be all back to normal without loosing any data, am i right?
Thank you!
FatPiNi said:
Hi there! Today i had the OTA finally on my way but i had the modified lockscreen. I then came across your post and i tried to follow your step but with no luck:
1) the link to the OTA are just member profile but i think i can find the modified ones in the "official" thread in here
2)when i tried to perform the action listed in the page you linked to the CMkeyguard.apk i cannot delete the apk from my phone and i don't know how to do it from the PC. I tried then to flash it with the .zip provided by NunHugger (the creator of the modified lockscreen) but still no luck with the original update.
there is a way to perform the ota directly from the updater on the phone or i have to do it from the TWRP with the modified one only?
Also, reading through the thread of the lockscreen, i've read that i can perform a flash of boot.img... question is where to find it?
EDIT: I found the boot.img into the toolkit, so if i perform a flash it should be all back to normal without loosing any data, am i right?
Thank you!
Click to expand...
Click to collapse
ah, you're right. i fixed my link to the post with the modified script.
in order to delete the file cmkeyguard.apk, you need a file browswer with root access. i use es file explorer (among others).
HTC One (M9) ReadMe Thread
Q4: Which versions of TWRP and SuperSU are the recommended ones?
A: The answer depends on your current firmware version. If you're using firmware 4.x then you'll find your answer here in the FAQ of the TWRP thread. (Click here, if you can't find SuperSU 2.79 SR3.) For firmware 1.x and 2.x the recommended versions are Captain_Throwback's Beta 1 of TWRP 2.8.7.1 and SuperSU 2.49. For firmware 3.x the recommended versions are TWRP 3.1.1-0 (official) and SuperSU 2.65. Using different versions than the recommended ones will probably lead to a bootloop. The M9 isn't compatible with the ramdisk changes that get executed by many flashable system-less SuperSU versions. However, updating the SuperSU app and its binaries via the Play Store after flashing one of the older versions is safe.
Q5: Are there alternative methods for gaining root?
A: Yes, you can use Magisk if you're using firmware 4.x. (Maybe a user with a lower firmware version can test whether Magisk is usable on firmware 1.x to 3.x, as well?)
Click to expand...
Click to collapse
Requirement
1. S-OFF AND UNLOCKED BOOTLOADER OF HTC ONE M9 (FILE PROVIDED IS FOR INTERNATIONAL VERSION. IF YOU WANT CREATE YOUR CARRIER PHONE COMMENT BELOW )
Method
STRAIGHT TO THE POINT just download the 2 zips provided below and place it in external sd card of phone and reboot to download mode
It will ask to flash press the vol up button and after flash you will have twrp flashed (i had included latest twrp recovery in the zip file but you can place in zip the recovery of your choice but you have to rename it to recovery.img)
NOTE DONT RENAME THE ZIP OR ELSE IT WILL NOT FLASH AND SECONDLY DONT CHANGE THE TXT FILE IN THE ZIP
after flash go to recovery and flash supersu zip
Downloads
Mod Removed
Help Section
Comment or pm me if you are facing any problem and want to get help
If you liked my work hit the appreciation button and if you want to grow my projects donate me as i dont have enough resources
Don't spam. Your previous thread exactly like this has been closed. Can't you take the message from that?
http://forum.xda-developers.com/showthread.php?t=3530127
Hope a mod sees this soon.
Sent from my HTC One M9 using Tapatalk
shaqman89 said:
Don't spam. Your previous thread exactly like this has been closed. Can't you take the message from that?
http://forum.xda-developers.com/showthread.php?t=3530127
Hope a mod sees this soon.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
First of all i am sorry for the previous post.
In my previous post, it was my 1st time i posted anything.I dont know the rules. But now i had got all the rules etc. In previous post i also used some useless terms such as "custom recovery" but in this post everything is ok.
Previous post was closed by moder because i used adf for some earning
But in this the downloads are on direct androidfilehost.com
You can match the md5 in the twrp zip of recovery.img with the md5 of of twrp 3.0.2 at thier website for verification
And try before saying anything
If it will be spam than report about my post
ahmad.abbas54 said:
First of all i am sorry for the previous post.
In my previous post, it was my 1st time i posted anything.I dont know the rules. But now i had got all the rules etc. In previous post i also used some useless terms such as "custom recovery" but in this post everything is ok.
Previous post was closed by moder because i used adf for some earning
But in this the downloads are on direct androidfilehost.com
You can match the md5 in the twrp zip of recovery.img with the md5 of of twrp 3.0.2 at thier website for verification
And try before saying anything
If it will be spam than report about my post
Click to expand...
Click to collapse
You're posting links to outdated versions of both TWRP and SuperSU. The latest versions and guides on how to install them already exist in their official threads.
If you want to be a help, try your hand at questions people are actually asking instead. XDA can always use another helpful expert.
computerslayer said:
You're posting links to outdated versions of both TWRP and SuperSU. The latest versions and guides on how to install them already exist in their official threads.
If you want to be a help, try your hand at questions people are actually asking instead. XDA can always use another helpful expert.
Click to expand...
Click to collapse
Really!! All those methods require a pc. My method is without pc
And Dont miss guide or lie and for your information both twrp and supersu is updated one
Talk before speak
Proofs are attached
ahmad.abbas54 said:
Really!! All those methods require a pc. My method is without pc
And Dont miss guide or lie and for your information both twrp and supersu is updated one
Talk before speak
Proofs are attached
Click to expand...
Click to collapse
I'm sorry if I've offended you - that wasn't my intention. However, you are mistaken about me lying or misguiding others.
Go check out the official TWRP thread. The latest version is posted there - it's version 3.0.3-0.
Check out the official SuperSU thread. The latest version is posted there - it's version 2.79 SR1 (2016-12-22).
Both of these versions, by the way, are important because they address issues that are unique to the M9. Previous versions of TWRP couldn't decrypt HTC's stock encryption. Recent versions of SuperSU couldn't be flashed directly. I'm sure there are other general fixes included as well.
You've got a neat idea, and I commend you for it. But if you're not working with the latest software - and passing it off as the latest - you're adding to people's confusion rather than helping them.
computerslayer said:
I'm sorry if I've offended you - that wasn't my intention. However, you are mistaken about me lying or misguiding others.
Go check out the official TWRP thread. The latest version is posted there - it's version 3.0.3-0.
Check out the official SuperSU thread. The latest version is posted there - it's version 2.79 SR1 (2016-12-22).
Both of these versions, by the way, are important because they address issues that are unique to the M9. Previous versions of TWRP couldn't decrypt HTC's stock encryption. Recent versions of SuperSU couldn't be flashed directly. I'm sure there are other general fixes included as well.
You've got a neat idea, and I commend you for it. But if you're not working with the latest software - and passing it off as the latest - you're adding to people's confusion rather than helping them.
Click to expand...
Click to collapse
I am also sorry if i used some rude words
Still i had checked recently on twrp.me and there's only 3.0.2 for m9 and i am using it right now with supersu 2.79
I am not facing any problem at all in all matters and it is also much stable
You can still update according to your need as you can open up my provided zip and add recovery.img of your choice and also you can flash supersu of your choice
@ahmad.abbas54: What @computerslayer said is correct. There are numerous reports of users facing a bootloop after flashing any other SuperSU version than 2.64 (stable), 2.65 (stable) or the latest beta 2.79 SR1 (link to its thread) on their stock rom. However, flashing one of these three and updating SuperSU via the play store doesn't cause any problems. Therefore I'd ask you for not linking the stable version 2.79.
In regard to TWRP: 3.0.2-0 is working fine. However, it's not the recommended version since 3.0.3-0 (unofficial) is capable of installing HTC's official OTAs.
Flippy498 said:
@ahmad.abbas54: What @computerslayer said is correct. There are numerous reports of users facing a bootloop after flashing any other SuperSU version than 2.64 (stable), 2.65 (stable) or the latest beta 2.79 SR1 (link to its thread) on their stock rom. However, flashing one of these three and updating SuperSU via the play store doesn't cause any problems. Therefore I'd ask you for not linking the stable version 2.79.
In regard to TWRP: 3.0.2-0 is working fine. However, it's not the recommended version since 3.0.3-0 is capable of installing HTC's official OTAs.
Click to expand...
Click to collapse
Kindly elaborate me further about the super su zip which is stable in 2.64 2.79 ??
Btw I had given download link of version supersu 2.79 in my post
ahmad.abbas54 said:
Kindly elaborate me further about the super su zip which is stable in 2.64 2.79 ??
Btw I had given download link of version supersu 2.79 in my post
Click to expand...
Click to collapse
SuperSU changes parts of the ramdisk since the introduction of system-less root. However, the changes that get initiated by any other than the three versions I mentioned above are not compatible with the M9 and cause a bootloop. Updating via the play store only updates the app and its binaries but not the ramdisk changes. This way you could update to a newer version of supersu (before 2.79 sr1 got released) without facing a bootloop.
There are stable and beta releases of SuperSU. Both are different stages of a "software release cycle". (The " " mark the keyword you need to google for further information. At the moment I don't have the time for writing a more detailed post. Sorry.)
You linked the stable version of 2.79. The beta which is safe to use got released a week later than the version in your post and it contains "sr1" in its naming.
Edit: Oh and please don't re-upload files to your afh account that you don't own (e.g. SuperSU) unless you got the permission of the dedicated owner/dev. Your 0PJAIMG.zip should be fine as long as you mention TWRP's devs in the credits of your OP.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
SuperSU changes parts of the ramdisk since the introduction of system-less root. However, the changes that get initiated by any other than the three versions I mentioned above are not compatible with the M9 and cause a bootloop. Updating via the play store only updates the app and its binaries but not the ramdisk changes. This way you could update to a newer version of supersu (before 2.79 sr1 got released) without facing a bootloop.
There are stable and beta releases of SuperSU. Both are different stages of a "software release cycle". (The " " mark the keyword you need to google for further information. At the moment I don't have the time for writing a more detailed post. Sorry.)
You linked the stable version of 2.79. The beta which is safe to use got released a week later than the version in your post and it contains "sr1" in its naming.
Edit: Oh and please don't re-upload files to your afh account that you don't own (e.g. SuperSU) unless you got the permission of the dedicated owner/dev. Your 0PJAIMG.zip should be fine as long as you mention TWRP's devs in the credits of your OP.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Ok i will be carefull next time
Had anyone achieved root with my method before??
I mean without pc
ahmad.abbas54 said:
Ok i will be carefull next time
Had anyone achieved root with my method before??
I mean without pc
Click to expand...
Click to collapse
Well, no one ever posted explicit instructions but it should be known to be possible from Sneakyghost's firmware thread. His firmware packs can get flashed via the SD card method, as well, and your archive is somehow similar to his no wipe packs. The difference is that your archive only contains TWRP whereas his packs contain almost the full stock firmware and TWRP instead of the stock recovery.
Nevertheless, step by step instructions like to ones in this thread are always nice to have.
(Although strictly speaking a PC is needed for your method, too, since you can't achieve S-OFF via Sunshine* without root on the M9 and for rooting the M9 the first time you need to unlock the bootloader which requires a PC. However, don't mind my nitpicking. )
* I have not much knowledge about how to use java cards for the same purpose but I think you need a PC for them, as well.
Flippy498 said:
Well, no one ever posted explicit instructions but it should be known to be possible from Sneakyghost's firmware thread. His firmware packs can get flashed via the SD card method, as well, and your archive is somehow similar to his no wipe packs. The difference is that your archive only contains TWRP whereas his packs contain almost the full stock firmware and TWRP instead of the stock recovery.
Nevertheless, step by step instructions like to ones in this thread are always nice to have.
(Although strictly speaking a PC is needed for your method, too, since you can't achieve S-OFF via Sunshine* without root on the M9 and for rooting the M9 the first time you need to unlock the bootloader which requires a PC. However, don't mind my nitpicking. )
* I have not much knowledge about how to use java cards for the same purpose but I think you need a PC for them, as well.
Click to expand...
Click to collapse
Well thats for obvious that we need pc for atleast bootloader unlock
I'm trying this method to flash TWRP on my unlocked, S-Off m9. (Unlocked with SunShine, my Mac with new USB-C port doesn't see device over ADB) I've unzipped your TWRP package, replaced the old TWRP with the latest--renamed "recovery.img"--and re-zipped it. When I boot phone into Download mode, the script recognizes the zip package, and "start ui-update" appears at the top of the screen. Nothing else happens, and if I eventually force power off, the stock Recovery is still installed. Suggestions?
Do S-OFF AND UNLOCKED BOOTLOADER not need a computer ؟؟؟؟؟؟
!!!!!!!!!!!!!!
Please close this trivial matter
Hi everyone. I'm new here on XDA and this is my first post so if I'm doing this wrong, please let me know below or provide a link if my problem has already been solved, thank you.
I have an s8+(SM-G955F, dream2ltexx/dream2lte), running 9.0.0. I have both, TWRP(3.3.1) and Magisk(latest) + edxposed(for what is worth). I am also running a custom kernel A2N. I received a week ago an OTA update and I would like to apply it. This is my first ever OTA update on a rooted device so I read a ton of posts and tutorials in the past few days, also backed up everything using TWRP. From what I understood(and please feel free to correct me if I'm wrong or show a better solution) I need to first install the default recovery image, lose TWRP, unroot, do the OTA and after that, reinstall TWRP and Magisk(I think I also need to return to stock kernel, not sure).
Important: I would very much like to not factory reset my phone if this is possible.
Now, I have a few questions:
1. Where can I get my default recovery.img ? (I tried to find it on https://desktop.firmware.mobi/device:468 but they don't have anything for android 9)
2. Do I also need to get and install my default kernel ? If so, where can I also get it ?
2. After I flash the recovery.img what is the best thing to do with Magisk ? (completly uninstall or just restore image ?)
3. After everything is done, will flashing TWRP require to remount the partitions ?(because that will also mean I have to factory reset at some point)
4. It would also be super helpful if you could provide me a link from where I can download OTA updates as zip files(if there exist such a place). The version that I need is: G955FXXS8DTC1
I cannot thank you enough for everything and sorry for the long post
Hope you have a safe, beautiful day !
P.S. I already tried to do the OTA update after backup. It tried to flash it throw TWRP and, of course, it failed(error: 7)
For everyone, that is unable to update your OTA files, i found a solution.
I do not have the credits myself, there was someone else that found this out, i cannot remember from who is it, but i believe it was someone on this forum.
I did find the links on 4PDA and the inscrutions aswell.
to fully upgrade KK you need OTAs - 191,198,199,201 - you need to flash them in order and flash every single one! You can flash them at one recovery session, it will update the tablet the correct way. Or you can just reboot after every single update, what suits you more.
!!! Im not responsible for anything that happens during/using these steps, you and only you are responsible to what happens, use with caution !!!
BEFORE WE START:
KK to LP update takes long time, make sure to be charged to atleast 50% of your battery! If your device powers off midway through any update, it will probably cause hard brick, making your device no more usable!
To update from KK to LP, you need to have the latest KK OTA, which is .201!
For the OTA updates, use the files from [me176c/x] [K013] Collection of ROMs and Updates - watchout for the .191 update, there are 2 links, from which only 1 is correct, .191 update should have 154MB.
There are some thing that will prevent you from updating
- root - should not prevent you from updating, i used the Root Zenfone app, from mentioned thread above, it did not prevent me from updating, but unrooted after KK to LP update
- xposed - not tested
- uninstalling system apps WILL 100% prevent you from updating (to revert that, install the .182 full ROM)
- freezing/disabling system apps SHOULD NOT prevent you from updating
For updating i used Temp CWM recovery, TWRP had some issues updating, if you get errors in TWRP, please consider using CWM.
Download the files respective to each OTA update from my google drive (Modified Update Scripts)
Extract the updater-scripts from the downloaded files to any folder and copy it
Download the OTA updates from this thread (first post)
Open update_XXX.zip\META-INF\com\google\android\updater-script with WinRAR and paste it (replace the original update-script)
WinRAR then has some options for compression and stuff, keep everything as it is
You do this to every single OTA you have - 191,198,199,201
Then move them to your internal storage on the device, or sdcard, whatever is better
power off your tablet and boot it up once again used POWER + VOLUME UP
Droid boot mode should appear, connect it to your PC
open launcher.bat inside Intel FBRL (cant share the link atm - google intel temp recovery)
follow the steps in your launcher.bat - ACCEPT, wait, 5 (cwm.zip), wait, T2 or T4 both works
Temporary CWM then should boot up on your device
make full factory reset data/cache/dalvik-cache
flash the modified OTA update from your intstorage/sdcard
when youre in the recovery already, you can flash every OTA you have, but in order - that means you flash 191, then 198, 199, 201, THEN REBOOT
wait for your tablet to finish the updates and boot up the system as normal
When you made it to .201 update (check in system settings, if thats correct), you can either stay on 4.4.2, or upgrade to 5.0
KITKAT TO LP UPDATE
download the file from official ASUS website, i used version .17, you should be able to go straight to the .36
MAKE SURE THE FILE YOURE DOWNLOADING HAS _KK (Kitkat to Lollipop) IN THE FILE NAME!
open the downloaded file, extract updater-script once again using WinRAR
(same location as before - XXX.zip\META-INF\com\google\android\updater-script)
delete the first 2 lines in the updater-script
getprop("ro.product.device") == "K013" || abort("This package is for \"K013\" devices; this is a \"" + getprop("ro.product.device") + "\".");
show_progress(0.750000, 0);
put the modified updater-script back into its original place, WinRAR asks once again for compression level and stuff, keep everything as it is
Move the modified update file to either the root interal storage or root of sdcard
your device should ask you to update in the notification bar, if it does not, try either rebooting the device or plugging/unplugging MTP cable to your PC, both should work
select the update, let it do its thing
For many things, including the modified updater-scripts, temp recovery and OTA files i used
Asus MeMO Pad 7 ME176CX - Обсуждение - 4PDA
Asus MeMO Pad 7 ME176CX - Обсуждение, Планшет, 7''
4pda.to
Make sure to use in-built translation like Chrome has for example to understand the forums, as it is written in russian language
If youre trying to download an OTA or firmware file from the website and the link doesnt do anything, try right-clicking the link and "Save the URL as..."