Related
Time to get the Nook HD+ rolling on Kitkat! XDA forum member succulent (aka Iamafanof) has given me permission to post a link to his blog with all the necessary info that you need, plus the all important links to download his CM11 4.4.2 roms.
I had previously been running his CM 10.2 builds with sgt7 and they were great. Now, been running his CM11 builds since 12/16 and they are very functional and run extremely well.
It is highly recommended that you read over his blog to get the info you need to properly flash it. It's likely that your current recovery, be it CWM or TWRP will be unable to flash 4.4. You can try and if it fails, download the zip recoveries for either CWM 6.0.4.5.x or TWRP 2.6.3.0 on succulent's website listed below. Succulent recommends CWM but I've had great success with both of them. If you have a problem flashing the recovery zip, extract the image file from the zip and flash either through ADB or the PS app flashify from within your OS. EDIT: You do need to update your recovery to one of the above-mentioned recoveries.
Note: succulent's 4.4 builds are scripted to automatically install CWM 6.0.4.5b when installing the rom. But, the catch-22 is that you need to already have CWM 6.0.4.5.x or TWRP 2.6.3.0 to install 4.4 roms. EDIT 01/14/14: Currently, succulent's builds are now scripted to automatically install TWRP 2.6.3.0 instead of CWM 6.0.4.5b.
New TWRP 2.6.3.0 and CWM 6.0.4.5.x recoveries: http://goo.im/devs/succulent/ovation/recovery If you choose CWM, 6.0.4.5b is preferred as it supports both internal and ext sdcard.
Needless to say, make a nandoid backup before proceeding and if you're not comfortable doing this...DON'T!
Link to succulent's blogsite with download links: http://iamafanof.wordpress.com/2013/12/20/cm11-0-kitkat-android-4-4-2-for-nook-hd-xx-20dec2013/
Note: There are two different builds, one for internal (eMMc) and one for sdcard, be sure to download and install the correct one. I am using the eMMc build,so I don't have any knowledge of how the sdcard build is working.
Additional link to succulent's rom builds on Goo: http://goo.im/devs/succulent/ovation/cyanogenmod/internal
On the Goo site, he also has his CM 10.2 builds that might be of interest to some of you. Note: His CM10.2 rom builds automatically install TWRP 2.6.3.0.
You must use KitKat 4.4 gapps. A gapps link is provided on succulent's blog site. Either use those gapps or the PA zero day gapps linked below. If you are going to use ART, it's recommended that you do use the PA zero day gapps for best compatibility. If you don't know what ART runtime is, google it!
All credit for the rom builds, as well as the new recovery images goes to succulent (aka Iamafanof). I am just spreading the news so we can all finally have KitKat on our devices.
EDIT: Just a reminder regarding the newer recoveries, CWM 6.0.4.5.x and TWRP 2.6.3.0, they are in flashable zip form on succulent's blogsite linked above. If you run into a problem flashing the zip, one of the simplest ways to get the job done is with Flashify. Just unzip the recovery zip to get the image file. Put the image file on your device and flash it with Flashify. Play Store link: https://play.google.com/store/apps/details?id=com.cgollner.flashify
Regarding ART runtime: Since it's still "experimental", YMMV with the results you get. Google may decide ART isn't feasible and dump it going forward.
Note: Not all gapps packages are ART compatible, at this time it is probably best to use the Paranoid Android zero day gapps. Link for PA gapps: http://forum.xda-developers.com/showthread.php?t=2397942 Be sure to choose the current 4.4 gapps.
With ART runtime, it is generally better to initiate it on a fresh rom install and before you install all of your user apps. Btw, it's normal for it to take a long time to initialize on the first reboot. , I found that it generally takes a while to "settle in" and should become more fluid/speedier over time.
Always be sure to have a nandroid backup so you can easily go back to dalvik if ART isn't your thing.
One last thing about ART, Xposed Framework does not yet support it. It will appear to work but it does not. Matter of fact, with Xposed installed on your device, it will revert ART runtime back to Dalvik. Since I love using Xposed, this has kept me from using ART except to test it.
EDIT: Hey guys, just posting as new stuff comes up. Here's another possible alternative for those that may have a problem with either of the internal recoveries. XDA member sandsofmyst has put together a bootable TWRP 2.6.3.0 sdcard installer. If you use it, please post your results here and don't forget to give sandsofmyst a thanks click.
http://forum.xda-developers.com/showthread.php?p=48549135#post48549135
Enjoy!
Mike T
I'm in my kitkat glory right now. happy, happy, joy, joy.
Makes sure to update CWM BEFORE flashing CM11. Trust me, I lost 30 minutes trying to ungoober my Nook HD+.
supergroverthm said:
I'm in my kitkat glory right now. happy, happy, joy, joy.
Makes sure to update CWM BEFORE flashing CM11. Trust me, I lost 30 minutes trying to ungoober my Nook HD+.
Click to expand...
Click to collapse
Good tip and we always learn by trying. :laugh: I already had TWRP 2.6.3.0 from a previous rom, so my install of 4.4 was quick and painless. LOL
If you haven't already, hook this baby up with Xposed module by rovo89. Some really cool extra features without bogging things down with stuff you don't want or need.
Mike T
Oohh, I'm very very interested in this. Kept saying about memory optimizations for lower end device, have you noticed much performance differences? Pretty stable? Bluetooth, hdmi and everything work?
Sent from my HTC One using Tapatalk
Wow. Just wow
So now that you built it, can we expect it to become an official release soonish?
Thanks a lot for your work!
Hi, I just bought two nook hd+ one for me and one for my parents as a christmas present.
Beautiful devices, the only problem is that it does not provide italian as interface language,also all the appdownloaded from the play store are in english and I can't find a way to change that. My parents reallyneed the italian language sadly they don'tspeak a word of english....
So now I'm here wondering if this cyanogenmods have the italian language.
Saluti
Luca
superanima said:
Hi, I just bought two nook hd+ one for me and one for my parents as a christmas present.
Beautiful devices, the only problem is that it does not provide italian as interface language,also all the appdownloaded from the play store are in english and I can't find a way to change that. My parents reallyneed the italian language sadly they don'tspeak a word of english....
So now I'm here wondering if this cyanogenmods have the italian language.
Saluti
Luca
Click to expand...
Click to collapse
Well, I looked in the Language+input section under settings and Italiano (Italia) and Italiano (Svizzera) are in there. I was able to switch to them and then...not be able to read anything so I'm assuming it's right. haha. Going into the Play Store all of the app names are still english but their descriptions changed so, it seems like it mostly works. I believe language support is an app-to-app basis though, so if the app developer didn't include Italian tranlations then it's going to be in English or whatever native language the App is in. I'm not totally sure how the language support works. Maybe someone else with more info can fill in my blanks.
On to this ROM as a whole, I've been playing with it, coming from CarbonRom 10.2 and haven't noticed much difference but I dig it none-the-less. I've tested Bluetooth headphones and my HDMI adapter and both work just fine. If anyone is wanting me to test anything let me know.
Have you enabled ART?
Sent from my GT-N7105 using XDA Premium 4 mobile app
aedgington said:
Have you enabled ART?
Sent from my GT-N7105 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Going into Settings>Dev Options and changing the runtime to ART and then rebooting...it doesn't get stuck in a bootloop, but going back into the Dev options shows that the Runtime option is still Dalvik and not ART so... I don't think that is there yet.
Wow, I have 342mb RAM Aavailable with GAPPS installed according to cool tool!
I've enabled ART and its showing on dev options. What's the deal with this new method? Is it better, faster, etc?
felacio said:
Going into Settings>Dev Options and changing the runtime to ART and then rebooting...it doesn't get stuck in a bootloop, but going back into the Dev options shows that the Runtime option is still Dalvik and not ART so... I don't think that is there yet.
Click to expand...
Click to collapse
Awesome, thanks for checking. I think that may be where we'll see some performance increase, but if it's not implemented yet, there's no rush for me to install
aedgington said:
Awesome, thanks for checking. I think that may be where we'll see some performance increase, but if it's not implemented yet, there's no rush for me to install
Click to expand...
Click to collapse
Mine is showing ART in dev option after reboot...
supergroverthm said:
Mine is showing ART in dev option after reboot...
Click to expand...
Click to collapse
Have you noticed any difference between ART and Dalvik?
aedgington;4872557[LEFT said:
[/LEFT]0]Have you noticed any difference between ART and Dalvik?
Click to expand...
Click to collapse
Only that more RAM is available. Now showing 390mb RAM available.
Flashing CWM
Sorry for the bit of a newb question, but how are you getting the CWM update in there? My prior ROM flashing, I had just used the bootable SD card image that verygreen had setup. I don't know how to update the version of CWM on that image currently.
When I put CWM on my phone, I had used fastboot to install it, but I can't get fastboot to recognize my nook for some reason (adb works fine). Did you use this method (from cwm site)?:
EDIT: This doesn't work... flash_image seems to be scanning for some partition that's not available:
"error scanning partitions: No such file or directory"
Code:
adb push c:\flash_image /sdcard/
adb push c:\recovery.img /sdcard/
adb shell
su
mount -o remount, rw /system
cp /sdcard/flash_image /system/bin
cd /system/bin
chmod 777 flash_image
flash_image recovery /sdcard/recovery.img
Nook HD Kitkat
chili81 said:
Sorry for the bit of a newb question, but how are you getting the CWM update in there? My prior ROM flashing, I had just used the bootable SD card image that verygreen had setup. I don't know how to update the version of CWM on that image currently.
When I put CWM on my phone, I had used fastboot to install it, but I can't get fastboot to recognize my nook for some reason (adb works fine). Did you use this method (from cwm site)?:
Code:
adb push c:\flash_image /sdcard/
adb push c:\recovery.img /sdcard/
adb shell
su
mount -o remount, rw /system
cp /sdcard/flash_image /system/bin
cd /system/bin
chmod 777 flash_image
flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
I placed the files on my internal SDCard/Download and TWRP could see them and I installed.
Went here to get the zip file http://www.mediafire.com/download/c32pw4qf1l9a0mu/flash_recovery_TWRP_2.6.3.0_internal.zip
After installing the new TWRP and reboot I reset the old ROM then installed the new ROM and GAPPS.
norm883
That did the trick, thanks... I was thinking the older CWM would have same problem updating to newer CWM as it would KitKat.
Flashed TWRP 2.6.3, rebooted then tried to install 4.4 and got a mount/data1 error.
I'll guess I'll try with the new CWM.
Does anyone know if the new CWM can read and restore TWRP back-ups?
EDIT: rebooted then booted back into TWRP 2.6.3.
So far so good, flashing GAPPS now.
All good.
Decided to put some extra notes here for those that only read the last page. Also put this in the OP.
Just a reminder regarding the newer recoveries, CWM 6.0.4.5 and TWRP 2.6.3.0, they are in flashable zip form on succulent's blogsite linked above. You should be reading his blog info anyway, so just scroll untill you see the links for those recoveries. If you run into a problem flashing the zip, one of the simplest ways to get the job done is with Flashify. Just unzip the recovery zip to get the image file. Put the image file on your device and flash it with Flashify right from within you current OS, ie; CM10.2 etc.
Regarding ART runtime: Since it's still "experimental", YMMV with the results you get. Also, Google may decide ART isn't feasible and dump it going forward.
A couple of things to note, not all gapps packages are ART compatible, the gapps I linked from 1209 do work, I'm not sure about the ones linked on succulent's blogsite from 1208. I believe the PA zero day gapps are also ART compatible.
With ART runtime, it is generally better to initiate it on a fresh rom install and before you install all of your user apps. Btw, it's normal for it to take a long time to initialize on the first reboot. I found that it generally takes a while to "settle in" and should become more fluid/speedier overtime.
Always be sure to have a nandroid backup so you can easily go back to dalvik if ART isn't your thing.
One last thing about ART, Xposed Framework does not yet support it. It will appear to work but it does not. Matter of fact, with Xposed installed on your device, it will revert ART runtime back to Dalvik. Since I love using Xposed, this has kept me from using ART except to test it.
Mike T
FirePsych said:
Flashed TWRP 2.6.3, rebooted then tried to install 4.4 and got a mount/data1 error.
I'll guess I'll try with the new CWM.
Does anyone know if the new CWM can read and restore TWRP back-ups?
EDIT: rebooted then booted back into TWRP 2.6.3.
So far so good, flashing GAPPS now.
All good.
Click to expand...
Click to collapse
CWM and TWRP backups are not compatible, probably never will be unless some third party dev figures something out.
Mike T
Hello
I have a brand new Samsumg Galaxy S4 but I hate TouchWiz. I want to have the purest Android experience.
I'm a bit new with this phone and haven't used Android in two years now so I'm a bit lost.
What is the latest official Google Play Edition available for my S4? It doesn't have to be Lollipop (although that'd be nice), it can be on KitKat. As long as it's official and untouched (if such a thing exists)
Thank you for your time and help!
I use this rom
It's mostly stock but with a few features added. It has an aroma installer from which you can choose what to install. E.g if you want stock kernel or custom kernel.
GDReaper said:
I use this rom
It's mostly stock but with a few features added. It has an aroma installer from which you can choose what to install. E.g if you want stock kernel or custom kernel.
Click to expand...
Click to collapse
Thanks! I'll definitely try it. The only thing is I tried to install TWRP yesterday but the phone started to load it and then stopped. There was a tiny tiny progress color but when I just restarted the phone without completing the process, it worked fine which shows that it didn't even start.
I flashed TWRP using Nandroid manager (from google play) and the img file you get from the twrp site.
That's the only method that worked for me.
TWRP Image
Nandroid Manager
If you're on stock rom, nandroid manager will prompt you to install busybox app from google play (since stock roms don't have busybox). Just download it and install busybox using that app.
Then you can use Nandroid manager to flash that twrp recovery image. Then boot into recovery to make sure it works
Thank you! I've installed TWRP now. I'll continue the tutorial and keep you posted!
Alright it worked! Thanks a bunch!
No problem
Hey guys, first of all sorry about my english, im french.
So my problem is: I tried rooting my Axon 7 A2017U many times, with different guides. I always end up with a softbricked phone, having to restore to stock using MiFlash.
My bootloader is unlocked, i have stock recovery and stock rom for now.
Whenever i flash TWRP, either the signed one (from @tenfar) or unsigned (and up to date) ones, i can't go past the menu saying something like "your phone cant be checked for corruption, please lock your phone [...]" it just freeze. i did read somewhere that i should flash chainfire's root or a special .zip that, i guess, disabled some check that could prevent booting a phone with unsigned stuff/edited system (after flashing TWRP, so it could boot) that didn't work out. i think i found that information in some LineageOS thread here on XDA.
My ultimate goal would be to get a rooted stock nougat 7.1.1, up to date TWRP recovery and to be able to switch to LineageOS to try it out soon.
For what it is worth, i rooted many phones over the years, so while i'm no expert, i should be able to follow most of the steps you give me.
Thanks alot!
What version of TWRP did you flash first?
I have the same root problem i can not install in twrp install in twrp ok but su application displays no root cause i have latest twrp
KwesiJnr said:
What version of TWRP did you flash first?
Click to expand...
Click to collapse
this
https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
And @tenfar's signed one
KwesiJnr said:
What version of TWRP did you flash first?
Click to expand...
Click to collapse
this
https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
And @tenfar's signed one
Okay. Download and flash this one alone via fastboot and see what happens. This is one the I personally use. It is required for any of the newer versions to work properly.
twrp-3.0.2-2-a2017u.img
You can choose to rename it to just recovery.img, then:
1. fastboot flash recovery recovery.img
or
2.
if you choose to work with the same filename:
fastboot flash recovery twrp-3.0.2-2-a2017u.img
Select reboot to recovery from the bootloader menu now and try again.
Either way, should work fine. I know you mentioned you knew the basics, but just want to be sure.
Also forgot to mention. If TWRP works but you still can't get your phone to boot, you need to follow this guide here
You can start from the part that says:
-----------------------------------------------------
UPDATING FROM B20_Boot / B20 / B27 / B29 / B15(N)
-----------------------------------------------------
Again, that's the ROM I personally use if I want to go back to stock, not the one from the ZTE site.
Gonna try it and give feedback. thanks for taking time to help!
edit: im downloading the rom from the link you shared.
like you said, i can get TWRP to boot but not the phone.
So if i use full stock from ZTE, it can't boot with modified recovery?
edit 2: i don't know what worked, i think it might be the bootstack. or the rom by DrakenFX. now i can boot to the rom with a TWRP recovery installed. It worked, but i soft bricked again trying to flash SuperSU. So now i'm retrying with an updated TWRP.
I haven't tried that yet, but I really suspect that's the reason you're having problems. I rarely use pure stock ROMs. Like you, I'm not an expert in Android Development so I can't tell you why. Just been a flashaholic for years so made a few observations.
Which supersu are you installing? If you're swiping to the right in twrp, you need to install the dm-verity zip or supersu 2.79. There's some issues with newer builds.
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable.
Edit : Everything is working flawlessly! I'm running the lastest LineageOS nightly with root (Chainfire's 2.79). Followed their instruction and installation was smooth as butter. I should also point out i flashed the lastest official TWRP which seems more stable than the one @KwesiJnr suggested. The one he suggested was giving me some "can't read X partition" in red text everywhere in the log section, which the official one doesn't do. It was doing his job properly anyway though.
I can't thank @KwesiJnr enough, it helped me find the single mistake i was making.
lololo2 said:
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable
Click to expand...
Click to collapse
Glad you're up and running root. :good:
lololo2 said:
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable.
Edit : Everything is working flawlessly! I'm running the lastest LineageOS nightly with root (Chainfire's 2.79). Followed their instruction and installation was smooth as butter. I should also point out i flashed the lastest official TWRP which seems more stable than the one @KwesiJnr suggested. The one he suggested was giving me some "can't read X partition" in red text everywhere in the log section, which the official one doesn't do. It was doing his job properly anyway though.
I can't thank @KwesiJnr enough, it helped me find the single mistake i was making.
Click to expand...
Click to collapse
Yeah, like I mentioned before that was the base TWRP you needed to flash first, before any of the newer ones. You weren't intended to use it indefinitely.
There's a lot of Dev love for our device now and support is growing ... exciting new ROMs cropping up. Don't hesitate to try them out.
Hello everyone, could anyone help me to migrate from ROM xXx to Android 9?
I am currently using the ROM xXx but when trying to switch to another ROM I have problems with bootloop.
I tried following the procedures outlined in the last comments of the original thread but did not succeed, could anyone help me with a step by step to get out of the ROM and go to version 9 of android?
Here is some information that may be helpful in finding a possible solution:
Actually ROM: xXx No Limits 4.3 (https://forum.xda-developers.com/on...xxx-nolimits-1-1-speed-ram-optimized-t3627121)
New ROM:OxygenOS 9.0.1 (https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003)
Device is decrypted
Bootloader Unlocked
TRWP 3.2.1-X blu_spark v8.61
In some attempts to install ROM the TWRP returned me error regarding vendor partition.
Thanks to anyone who can help me.
josebeserra said:
Hello everyone, could anyone help me to migrate from ROM xXx to Android 9?
I am currently using the ROM xXx but when trying to switch to another ROM I have problems with bootloop.
I tried following the procedures outlined in the last comments of the original thread but did not succeed, could anyone help me with a step by step to get out of the ROM and go to version 9 of android?
Here is some information that may be helpful in finding a possible solution:
Actually ROM: xXx No Limits 4.3 (https://forum.xda-developers.com/on...xxx-nolimits-1-1-speed-ram-optimized-t3627121)
New ROM:OxygenOS 9.0.1 (https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003)
Device is decrypted
Bootloader Unlocked
TRWP 3.2.1-X blu_spark v8.61
In some attempts to install ROM the TWRP returned me error regarding vendor partition.
Thanks to anyone who can help me.
Click to expand...
Click to collapse
You'll need to be on your PC for this. Make sure you backup anything you want to keep from Internal Storage:
OOS:
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
1) Wipe and Format everything in TWRP.
2) Move OOS 5.1.3 (Full Zip) to Internal Storage
3) Install 5.1.3 and nothing else (You will lose TWRP, but don't worry abut that now)
4) OTA up to 5.1.7
5) If you don't get offered OTA to 9.0.1 use full zip from here: https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
6) Once on OOS 9.0.1 you can use Fastboot to flash latest Codeworkx TWRP: https://sourceforge.net/projects/cheeseburgerdumplings/files/16.0/cheeseburger/recovery/
If you want to install a custom ROM after that:
7) Wipe and Format
8) Install Pie ROM/Gapps etc
Dirk said:
You'll need to be on your PC for this. Make sure you backup anything you want to keep from Internal Storage:
OOS:
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
1) Wipe and Format everything in TWRP.
2) Move OOS 5.1.3 (Full Zip) to Internal Storage
3) Install 5.1.3 and nothing else (You will lose TWRP, but don't worry abut that now)
4) OTA up to 5.1.7
5) If you don't get offered OTA to 9.0.1 use full zip from here: https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
6) Once on OOS 9.0.1 you can use Fastboot to flash latest Codeworkx TWRP: https://sourceforge.net/projects/cheeseburgerdumplings/files/16.0/cheeseburger/recovery/
If you want to install a custom ROM after that:
7) Wipe and Format
8) Install Pie ROM/Gapps etc
Click to expand...
Click to collapse
Thx for Help dude, but i have a problem.
I backed up my stuff and joined TWRP, after joining TWRP I went to WIPE> Format Data.
After that I passed the file from ROM 5.1.3 to the internal memory of the device and went to install and started the procedure, but doing so returned an error and I would like you to help me if it were possible.
The following message was displayed:
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/OnePlus5Oxygen_23_OTA_036_5.1.3.zip'
Can you help me?
josebeserra said:
Thx for Help dude, but i have a problem.
I backed up my stuff and joined TWRP, after joining TWRP I went to WIPE> Format Data.
After that I passed the file from ROM 5.1.3 to the internal memory of the device and went to install and started the procedure, but doing so returned an error and I would like you to help me if it were possible.
The following message was displayed:
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/OnePlus5Oxygen_23_OTA_036_5.1.3.zip'
Can you help me?
Click to expand...
Click to collapse
Error 7 leads to corrupted file. Check your downloaded file, try again.
strongst said:
Error 7 leads to corrupted file. Check your downloaded file, try again.
Click to expand...
Click to collapse
ok, i will re-download the file and try the installation again.
I downloaded it again and tried the installation but again I got the same error when trying to install.
I am doing the download again but this time I will try to download without using download managers, in the previous attempts I used the Internet Download Manager (IDM) to do the downloads, do you recommend some download manager or browser?
I will also download via mobile data on the 4G network.
josebeserra said:
I downloaded it again and tried the installation but again I got the same error when trying to install.
I am doing the download again but this time I will try to download without using download managers, in the previous attempts I used the Internet Download Manager (IDM) to do the downloads, do you recommend some download manager or browser?
I will also download via mobile data on the 4G network.
Click to expand...
Click to collapse
I never use or recommend download managers cause of this
You can use Opera mobile, Firefox etc. But with download managers there are more issues(you'll find a lot on xda).
strongst said:
I never use or recommend download managers cause of this
You can use Opera mobile, Firefox etc. But with download managers there are more issues(you'll find a lot on xda).
Click to expand...
Click to collapse
Okay, thanks, I'll try to download again and I'll come back with the result soon
I downloaded the file from ROM 5.1.3 on the phone and again it returned the same error, I will try one more time.
Please give me your opinion, is there any version of TWRP that is recommended for installation? is it not the version I'm using that might not be reading the file?
Anything else, do I need to install 5.1.3 exactly or can I get a version prior to it?
There's something wrong in the middle of it, but let's keep trying.
lol
josebeserra said:
Actually ROM: xXx No Limits 4.3 (https://forum.xda-developers.com/on...xxx-nolimits-1-1-speed-ram-optimized-t3627121)
New ROM:OxygenOS 9.0.1 (https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003)
Device is decrypted
Bootloader Unlocked
TRWP 3.2.1-X blu_spark v8.61[/B]
Click to expand...
Click to collapse
Are you on xXx No Limits 4.3 (Nougat - 4.5.14) or xXx No Limits 4.3 Magisk Rom?
If you are talking about the Magisk Rom then we need to know what OOS version you are on to be able to give you the right advise.
josebeserra said:
I downloaded the file from ROM 5.1.3 on the phone and again it returned the same error, I will try one more time.
Please give me your opinion, is there any version of TWRP that is recommended for installation? is it not the version I'm using that might not be reading the file?
Anything else, do I need to install 5.1.3 exactly or can I get a version prior to it?
There's something wrong in the middle of it, but let's keep trying.
lol
Click to expand...
Click to collapse
Maybe you can try with this recovery: twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img
And see if it works.
Otherwise I would recommend to download OxygenOS 5.1.4 and try to flash that.
Z-Blade said:
Are you on xXx No Limits 4.3 (Nougat - 4.5.14) or xXx No Limits 4.3 Magisk Rom?
If you are talking about the Magisk Rom then we need to know what OOS version you are on to be able to give you the right advise.
Click to expand...
Click to collapse
I'm currently in version 4.3 Magisk, I think this can make it easier to find a possible output or end up making it more difficult.
strongst said:
Maybe you can try with this recovery: twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img
And see if it works.
Otherwise I would recommend to download OxygenOS 5.1.4 and try to flash that.
Click to expand...
Click to collapse
I will test with the one that recommended me and I will also download version 5.1.4
josebeserra said:
I'm currently in version 4.3 Magisk, I think this can make it easier to find a possible output or end up making it more difficult.
I will test with the one that recommended me and I will also download version 5.1.4
Click to expand...
Click to collapse
4.3 xXx magisk means you're running a stock oxygenOS where xXx 4.3 mod is running. Do you remember which oxygenOS version it was? 5.1.4 5.1.7 or whatever?
josebeserra said:
I'm currently in version 4.3 Magisk, I think this can make it easier to find a possible output or end up making it more difficult.
Click to expand...
Click to collapse
It could make things easier. If your phone still boots into OOS, go into Setting and scroll to the very bottom and select About Phone. Look at what Oxygen OS you are running. What you need to do is get that version all the way up to 5.1.7. Once you are there, you can just flash 9.0.2.
strongst said:
4.3 xXx magisk means you're running a stock oxygenOS where xXx 4.3 mod is running. Do you remember which oxygenOS version it was? 5.1.4 5.1.7 or whatever?
Click to expand...
Click to collapse
I'm using the OREO Stable version xXx_NoLimits_12.0_OP5_Oxygen_5.1.3 with the update patch xXx_NoLimits_4.3_magisk_rom
Z-Blade said:
It could make things easier. If your phone still boots into OOS, go into Setting and scroll to the very bottom and select About Phone. Look at what Oxygen OS you are running. What you need to do is get that version all the way up to 5.1.7. Once you are there, you can just flash 9.0.2.
Click to expand...
Click to collapse
This is the problem, I can not get out of the ROM No Limits to go to another ROM, I've tried some suggestions but still nothing worked, I'm counting on the patience of the members here of the forum to help me with this problem, but I believe that will soon be resolved and thank you all for the help.
josebeserra said:
I'm using the OREO Stable version xXx_NoLimits_12.0_OP5_Oxygen_5.1.3 with the update patch xXx_NoLimits_4.3_magisk_rom
Click to expand...
Click to collapse
Ok, so you're on a patched xXx rom not stock rom with xXx mod. Weird setup
Anyway, did 5.1.4 sucessfully flash without error 7?
strongst said:
Ok, so you're on a patched xXx rom not stock rom with xXx mod. Weird setup
Anyway, did 5.1.4 sucessfully flash without error 7?
Click to expand...
Click to collapse
strongst said:
Ok, so you're on a patched xXx rom not stock rom with xXx mod. Weird setup
Anyway, did 5.1.4 sucessfully flash without error 7?
Click to expand...
Click to collapse
I have not tried to install 5.1.4 yet, I was trying to 5.1.3 as it was suggested, I will download version 5.1.4 that is in this repository (https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190), and I will try to make the installation clean, ie format all the data, move the ZIP into the internal memory and try to see if it works.
I will try to clarify about the patch in case I try to reinstall ROM No Limits I need to install the full version which is 12.0 and patch 4.3 is just an update patch for the latest version and I can also go back to version 12.0.
Version 5.1.4 I have not yet tested if I can install it without errors, I will do it soon and I will come back with the result.
I think 5.1.4 should do the trick. I would highly recommend you wipe everything including systems, internal and data. This will pretty much give you a blank phone. Connect the phone to your computer and copy over 5.1.4 to the internal storage through TWRP, it should be the only file you see in your sdcard. Flash it and you should be good.
Z-Blade said:
I think 5.1.4 should do the trick. I would highly recommend you wipe everything including systems, internal and data. This will pretty much give you a blank phone. Connect the phone to your computer and copy over 5.1.4 to the internal storage through TWRP, it should be the only file you see in your sdcard. Flash it and you should be good.
Click to expand...
Click to collapse
Okay, I'll do the test and I'll come back soon with the result, I'll change the version of TWRP too, this may be the problem.
Bringing the result of a few more tests, I first changed the recovery version, I went to the twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img as suggested and after that I formatted all the data and started to appear a new one Error that was Failed to mount '/ vendor' (Invalid argument), I tried to install the 5.1.3 ROM and also to 5.1.4, which it was indicating was installing but at the end of the installation again I returned the error Failed to mount '/ vendor '(Invalid argument).
After that I reinstalled ROM No Limits 12.0 v. 5.1.3.
Does anyone know how to solve this new error?
Hey, I am not sure is this right place but I am gona ask still:laugh: I try install custom rom to p5110 tablet and installed twrp 2.8.5. Now I go to twrp wipe stuff then go to install and found rom zip but when I click it, its just opens that zip file and shows more zip files. All tutorials I have watch when you click that zip it should show install page and then swipe to install it. Any help to solve this problem?
tonuuuu said:
Hey, I am not sure is this right place but I am gona ask still:laugh: I try install custom rom to p5110 tablet and installed twrp 2.8.5. Now I go to twrp wipe stuff then go to install and found rom zip but when I click it, its just opens that zip file and shows more zip files. All tutorials I have watch when you click that zip it should show install page and then swipe to install it. Any help to solve this problem?
Click to expand...
Click to collapse
So before installing the ROM, I guess you first root the device and then installed TWRP? Some good instructions to do that?
I've come across 3 versions of TWRP that all seem plausible but that I do not necessirily trust/understand:
a) espresso-common-TWRP
b) P5110-TWRP
c) twrp-3.1.1-0-p5110.img
What I don't understand is that if the TeamWin is not supporting TWRP on this device anymore and stopped at version 3.1.1, how is it that these ANDROID-ANDY has more recent versions? And what is the espresso-common version? How does it differ from the P5110-TWRP version?
geotux said:
(...)
What I don't understand is that if the TeamWin is not supporting TWRP on this device anymore and stopped at version 3.1.1, how is it that these ANDROID-ANDY has more recent versions?
Click to expand...
Click to collapse
TWRP source is open, if you have the ability you can compile newer versions.
And what is the espresso-common version? How does it differ from the P5110-TWRP version?
Click to expand...
Click to collapse
espresso-common is unified, it works on P3100, P3110, P3113, P5100, P5110 and P5113 without the need for a device specific TWRP. It makes maintaining TWRP easier for our Tab.
At boot the kernel of the recovery is reading a value from your your LCD to decide which drivers need to be loaded on your variant.