I tried OTA updating today to YOG4PASN0 and it downloaded/installed the upgrade. It rebooted into TWRP recovery. I rebooted it again and it was still on the old version of YNG1TAS2I3, still notifying me of YOG4PASN0 being available.
If you are on TWRP its not possible to do the incremental update, as it requires original recovery. Just download the full rom and flash it on TWRP as normal, it will do.
Antieco said:
If you are on TWRP its not possible to do the incremental update, as it requires original recovery. Just download the full rom and flash it on TWRP as normal, it will do.
Click to expand...
Click to collapse
If I was able to do it from KitKat to Lollipop, I doubt I wont be able to do it from Lollipop to a newer version of Lollipop.
riahc3 said:
If I was able to do it from KitKat to Lollipop, I doubt I wont be able to do it from Lollipop to a newer version of Lollipop.
Click to expand...
Click to collapse
Do what ¿? Just download newest rom (630mb) and flash as usual.
Enviado desde mi OnePlus One
Antieco said:
Do what ¿? Just download newest rom (630mb) and flash as usual.
Enviado desde mi OnePlus One
Click to expand...
Click to collapse
I was able to OTA update from KitKat to Lollipop.
And no, Im not gonna flash. Im gonna see how to fix his and OTA update like OnePlus intented.
riahc3 said:
If I was able to do it from KitKat to Lollipop, I doubt I wont be able to do it from Lollipop to a newer version of Lollipop.
Click to expand...
Click to collapse
riahc3 said:
I was able to OTA update from KitKat to Lollipop.
And no, Im not gonna flash. Im gonna see how to fix his and OTA update like OnePlus intented.
Click to expand...
Click to collapse
The fact that you were able to go from KitKat to Lollipop using TWRP is irrelevant, you're no longer able to use TWRP for incremental OTA's, it's been like that for a little while now. You can try to fix it all you like but you can't. You have two options:
1. Flash the full ROM zip with TWRP.
2. Flash the stock recovery and flash the incremental OTA.
Heisenberg said:
The fact that you were able to go from KitKat to Lollipop using TWRP is irrelevant, you're no longer able to use TWRP for incremental OTA's, it's been like that for a little while now. You can try to fix it all you like but you can't. You have two options:
1. Flash the full ROM zip with TWRP.
2. Flash the stock recovery and flash the incremental OTA.
Click to expand...
Click to collapse
Then Ill just flash the stock recovery.
How do I go back to (the newest version of) stock recovery?
riahc3 said:
Then Ill just flash the stock recovery.
How do I go back to (the newest version of) stock recovery?
Click to expand...
Click to collapse
Use this one:
https://drive.google.com/file/d/0B98G0KTJwnBFNzBFd2pRMmhvUmc/view?usp=docslist_api
Flash with fastboot.
riahc3 said:
I was able to OTA update from KitKat to Lollipop.
And no, Im not gonna flash. Im gonna see how to fix his and OTA update like OnePlus intented.
Click to expand...
Click to collapse
Go and fix it, then post your fix.. we need you soo much... in the meantime most of the people will just flash the complete rom and go on with their lives.
Antieco said:
Go and fix it, then post your fix.. we need you soo much... in the meantime most of the people will just flash the complete rom and go on with their lives.
Click to expand...
Click to collapse
The fix ill probably use is the above.
Flash stock recovery
Get OTA
Flash TWRP
Done
riahc3 said:
The fix ill probably use is the above.
Flash stock recovery
Get OTA
Flash TWRP
Done
Click to expand...
Click to collapse
Wait!
So its the same fix we are using since COS12 .. thanks!!! great job! oh wait
Hello,
I had the same problem. I installed stock recovery from the link Heisenberg shared and then tried updating the phone via the OTA option. But the phone rebooted after a few mins on installation on the android screen to be back on the same version. I then tried installing the OTA incremental update zips from this link: http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746 (I tried both the YNG1TAS2I3 -> YOG4PAS1N0 files) but ended up with the following error (Image attached).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is flashing the entire ROM the only solution?
Antieco said:
Wait!
So its the same fix we are using since COS12 .. thanks!!! great job! oh wait
Click to expand...
Click to collapse
The reason of this thread is to find a fix.....
Heisenberg said:
Use this one:
https://drive.google.com/file/d/0B98G0KTJwnBFNzBFd2pRMmhvUmc/view?usp=docslist_api
Flash with fastboot.
Click to expand...
Click to collapse
That version is not the same version i have...
riahc3 said:
The reason of this thread is to find a fix.....
Click to expand...
Click to collapse
There is no fix, apart from the advice I gave you earlier.
Heisenberg said:
There is no fix, apart from the advice I gave you earlier.
Click to expand...
Click to collapse
riahc3 said:
That version is not the same version i have...
Click to expand...
Click to collapse
Its not the same version . Can I flash it?
riahc3 said:
Its not the same version . Can I flash it?
Click to expand...
Click to collapse
Yes you can, it's still the stock recovery so it's fine.
Heisenberg said:
Yes you can, it's still the stock recovery so it's fine.
Click to expand...
Click to collapse
Flashed stock recovery.
Im getting the same error message as trifixion1 in the recovery logs...
riahc3 said:
Flashed stock recovery.
Im getting the same error message as trifixion1 in the recovery logs...
Click to expand...
Click to collapse
I'm not sure why this is happening to you, you can just use fastboot to flash the stock images top update (just don't flash the userdata image).
Heisenberg said:
I'm not sure why this is happening to you, you can just use fastboot to flash the stock images top update (just don't flash the userdata image).
Click to expand...
Click to collapse
Finally i was able to flash the incremental OTA on my device.
Related
good morning. please, i have stock firmware upgraded 4.4, rooted and with recovery trwp....
i have this notification.
if i install this upgrade, i lose root and recovery?
will i reflash and reroot?
thanks
myabc said:
good morning. please, i have stock firmware upgraded 4.4, rooted and with recovery trwp....
i have this notification.
if i install this upgrade, i lose root and recovery?
will i reflash and reroot?
thanks
Click to expand...
Click to collapse
It won't install with root and a custom recovery
myabc said:
good morning. please, i have stock firmware upgraded 4.4, rooted and with recovery trwp....
i have this notification.
if i install this upgrade, i lose root and recovery?
will i reflash and reroot?
thanks
Click to expand...
Click to collapse
Hi, me too, need update for german retail version as a flashable zip, can't flash update by normal way, identified device as 1034 instead of 1032
A system dump from device would be also great, i lost my IMEI=0, mybe that helps me out!
cheers,
JX
Jerome-X said:
Hi, me too, need update for german retail version as a flashable zip, can't flash update by normal way, identified device as 1034 instead of 1032
A system dump from device would be also great, i lost my IMEI=0, mybe that helps me out!
cheers,
JX
Click to expand...
Click to collapse
Its here in the sixth post
http://forum.xda-developers.com/showthread.php?t=2648590
myabc said:
good morning. please, i have stock firmware upgraded 4.4, rooted and with recovery trwp....
i have this notification.
if i install this upgrade, i lose root and recovery?
will i reflash and reroot?
thanks
Click to expand...
Click to collapse
It´s the other way around. You need stock recovery and no root to be able to install it. Before you restore your stock ROM be so kind and extract and post the OTA zip here. (Actually not here, this is wrong forum for a post like that).
Edit: it is possible to install OTA with Philz and root. (tested that myself)
Please post these questions in the general or the Q/A section.
robin0800 said:
Its here in the sixth post
http://forum.xda-developers.com/showthread.php?t=2648590
Click to expand...
Click to collapse
Hi,
already tried this. Won't work, a system dump could be the best and maybe helps me out to restore my IMEI back. IMEI=0, no chance after restoring a stock rom etc..., do you know a away out to rewrite my imei?
please, help me. i don't want alert of upgrade, is there a way for hide upgrade notify? how? please help... this presents every 5 minutes!
Same question! I have a rooted and unlocked Moto G (but still the stock rom). I have a message that an OTA is ready to download. Already did the download and like they said here above, it does not install because there is an alternative recovery installed.
How can you hide the message that there is an OTA ready to download?
join Date: Jan 2006
still don't know the rule?
reported.
nickchk said:
join Date: Jan 2006
still don't know the rule?
reported.
Click to expand...
Click to collapse
please, instead wrtite only for you, write for users that asked a question.
myabc said:
please, instead wrtite only for you, write for users that asked a question.
Click to expand...
Click to collapse
doesn't matter,pls read the rule of xda before u post a question/anything,glad the mod moved it.
let's speak about serious things, users haven't many time for polemize.... for who has my problem, i done so and work:
say install upgrade, it reboot in recovery mode but doesn't install.
done wipe cache and dalvik cache (otherwise after every reboot it recharge recovery) and reboot system
no more advertisement upgrade
myabc said:
let's speak about serious things, users haven't many time for polemize.... for who has my problem, i done so and work:
say install upgrade, it reboot in recovery mode but doesn't install.
done wipe cache and dalvik cache (otherwise after every reboot it recharge recovery) and reboot system
no more advertisement upgrade
Click to expand...
Click to collapse
my wild guess is you're using google translate,i'm having hard time to understand :silly:
but refer to your 1st post,the thing is,you can't ota upgrade with any mod done to your device,you must use stock recovery and stay unroot. so,yes,you may receive it,but it won't pass flashing in recovery.
nickchk said:
my wild guess is you're using google translate,i'm having hard time to understand :silly:
but refer to your 1st post,the thing is,you can't ota upgrade with any mod done to your device,you must use stock recovery and stay unroot. so,yes,you may receive it,but it won't pass flashing in recovery.
Click to expand...
Click to collapse
yes... but my question is that i don't want the upgrade notify. it's not possible delete this notify. i have stock rom rooted, is there not way to put off notification of upgrade? thanks
myabc said:
yes... but my question is that i don't want the upgrade notify. it's not possible delete this notify. i have stock rom rooted, is there not way to put off notification of upgrade? thanks
Click to expand...
Click to collapse
i never try it,but you can try freeze/remove system apps that responsible for ota,like motorola service.
---------- Post added at 03:43 PM ---------- Previous post was at 03:35 PM ----------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
try to delete ur cache folder and freeze/remove the motorolaOTA v 1.0
thankeeeeed good idea... but what is the application that signal ota?
must i remove with titanium backup?
myabc said:
thankeeeeed good idea... but what is the application that signal ota?
must i remove with titanium backup?
Click to expand...
Click to collapse
i don't know which one but,you can try motorola ota,or motorola service,make sure you copy or backup them first,in case something goes wrong.
titanium should work,or root apps remover,or if you wanna remove manually,file explorer should also work.
Optimized Stock Rom for Shield Tablet
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction:
I was missing a stock based rom for this device. So I took the nvidia recovery image and made it a flashable zip for TWRP. You cannot use ota to update though, wait for the new version from here if you want to update.
Also, don't flash wrong zip on the wrong Shield Tablet. It's your own responsibilty
Features:
- Latest Stock Factory Image
- Zipaligned apps
- Nothing more
Download:
K1: https://www.androidfilehost.com/?w=files&flid=93930
Original (Wifi & LTE): https://www.androidfilehost.com/?w=files&flid=94437
Also flash blob file of the same version
Enjoy!!
What to do with the blob zip:
Code:
1. Extract blob file from zip
2. Flash blob in fastboot with: fastboot flash staging "name of blob file"
Yup, I vote for original Shield ROM! Thanks!
Nice! Vulcan API goodness!
Zip for the original Shield Tablet (untested):
https://www.androidfilehost.com/?fid=24591000424954195
Thanks for this!
Is there any possibility you remove the Kill-Switch for users who have kept their tablet what has had to be replaced? I guess the Tegra Ota service must be disabled
Thanks! Made backup, flashed rom zip, flashed twrp, su, Xposed, nomoreota, and kernel. Wiped cache and booted system. Looks good so far... Not much immediate difference but we shall see over time. Came from stock so I did not wipe data and all is well.
teachmeluv said:
Thanks for this!
Is there any possibility you remove the Kill-Switch for users who have kept their tablet what has had to be replaced? I guess the Tegra Ota service must be disabled
Click to expand...
Click to collapse
Its better to do that yourself. There are tutorials on how here in the devices forum
Sent from my XT1562 using XDA Labs
GtrCraft said:
Its better to do that yourself. There are tutorials on how here in the devices forum
Sent from my XT1562 using XDA Labs
Click to expand...
Click to collapse
Ok thank you. Previous post says something about the nomoreota file, I remember that one now.
Anyway is this ROM pre-rooted? And is the file for the original tablet compatible with all three versions of it?
So after a few hours this ROM is smoother, cooler and faster then stock... Guess I'll be keeping it for awhile.
teachmeluv said:
Ok thank you. Previous post says something about the nomoreota file, I remember that one now.
Anyway is this ROM pre-rooted? And is the file for the original tablet compatible with all three versions of it?
Click to expand...
Click to collapse
The rom is not prerooted, also I only downloaded the wifi image. So that's the version for the original tablet
ok so after unlocking and rooting, I installed the bliss rom, but realized none of the nvidia apps were there And besides my Phantom I want this tablet for that.
so I wiped and installed this one, ran the nomoreota zip and everything is back to normal, but, I'm not longer rooted.
I just want this rom and rooted. I have twrp recovery and it works fine, but still not rooted.
anyhelp? thanks
Hello,
I tried to install K1 version using twrp, but i'm getting a blkdiscard failed: Invald argement,updater process ended with error 7. Image doesnot get installed.
Any ideas?
Regards,
Good Good! Working fine!!.Thanks.
fastfed said:
ok so after unlocking and rooting, I installed the bliss rom, but realized none of the nvidia apps were there And besides my Phantom I want this tablet for that.
so I wiped and installed this one, ran the nomoreota zip and everything is back to normal, but, I'm not longer rooted.
I just want this rom and rooted. I have twrp recovery and it works fine, but still not rooted.
anyhelp? thanks
Click to expand...
Click to collapse
Flash the latest su.zip in twrp.
rampa99 said:
Hello,
I tried to install K1 version using twrp, but i'm getting a blkdiscard failed: Invald argement,updater process ended with error 7. Image doesnot get installed.
Any ideas?
Regards,
Click to expand...
Click to collapse
Be sure to have the latest twrp and bootloader for K1
GtrCraft said:
Tell me if you guys want the same zip for the original shield tablet. Or a version without zipaligned apps
Click to expand...
Click to collapse
any chance for original 32GB European LTE flashable version, please?
SnowiiSnowii said:
any chance for original 32GB European LTE flashable version, please?
Click to expand...
Click to collapse
which recovery image is that?
That'd be LTE RoW 4.2... thank you!
SnowiiSnowii said:
That'd be LTE RoW 4.2... thank you!
Click to expand...
Click to collapse
Here you go:
https://www.androidfilehost.com/?fid=24591000424955372
I updated to EMUI 5 with nougat, i think i lost my root. Went back to TWRP and about 60% of the way through the install phone reboots by itself with the phone not being rooted. Tried different superSU versions along with an adb sideload, same thing. Anyone have any idea what i'm doing wrong?
richbumx said:
I updated to EMUI 5 with nougat, i think i lost my root. Went back to TWRP and about 60% of the way through the install phone reboots by itself with the phone not being rooted. Tried different superSU versions along with an adb sideload, same thing. Anyone have any idea what i'm doing wrong?
Click to expand...
Click to collapse
twrp is not yet able to flash supersu successfully, if u want to root then flash a patched boot.img from here https://mega.nz/#!69IlASwI!FjF5rhALGGA_tusum7FdXgnO1R45ZIpdrahNa0UXT-8
Root working with B360 (L09 only at the minute)
thanks to @Atarii
Reboot into bootloader mode
Extract files and "fastboot flash boot boot.img"
Reboot into system
Install phh's SuperUser app from Play Store
OR
if u have twrp flash it thru twrp
raza3434 said:
twrp is not yet able to flash supersu successfully, if u want to root then flash a patched boot.img from here https://mega.nz/#!69IlASwI!FjF5rhALGGA_tusum7FdXgnO1R45ZIpdrahNa0UXT-8
Root working with B360 (L09 only at the minute)
thanks to @Atarii
Reboot into bootloader mode
Extract files and "fastboot flash boot boot.img"
Reboot into system
Install phh's SuperUser app from Play Store
OR
if u have twrp flash it thru twrp
Click to expand...
Click to collapse
Hello I have B380 and just tried this, flash the modified boot.img, and install the phh's su but still not rooted, do you have an idea?
remi13014 said:
Hello I have B380 and just tried this, flash the modified boot.img, and install the phh's su but still not rooted, do you have an idea?
Click to expand...
Click to collapse
(for L09)
u didn't mention u are on b380, anyways here is the boot.img for b380,
https://mega.nz/#!ekJVzLyY!pOhWHYpdhuRSFtBvxGYlMMFH5hFg0TG8bG17D13ZohM
raza3434 said:
(for L09)
u didn't mention u are on b380, anyways here is the boot.img for b380,
https://mega.nz/#!ekJVzLyY!pOhWHYpdhuRSFtBvxGYlMMFH5hFg0TG8bG17D13ZohM
Click to expand...
Click to collapse
i'm on L-04.. would this not work for me then?
richbumx said:
i'm on L-04.. would this not work for me then?
Click to expand...
Click to collapse
i dont know its atariis work you can ask there, @Atarii go to his profile search for b378, actually this boot.img is for p9 but due to same kernel it works on h8
richbumx said:
i'm on L-04.. would this not work for me then?
Click to expand...
Click to collapse
Try this boot image. You can flash it from twrp. Do not clear the cache or davlik. Reboot and install the phh super user apk.
https://forum.xda-developers.com/attachment.php?attachmentid=4070615&d=1489245825
https://forum.xda-developers.com/showpost.php?p=71382542&postcount=85
Parleyp
parleyp said:
Try this boot image. You can flash it from twrp. Do not clear the cache or davlik. Reboot and install the phh super user apk.
https://forum.xda-developers.com/attachment.php?attachmentid=4070615&d=1489245825
https://forum.xda-developers.com/showpost.php?p=71382542&postcount=85
Parleyp
Click to expand...
Click to collapse
I just tried this and it WORKS! I'm on EMUI 5 with my L-04. Now I can FINALLY block ads! Thanks for the info!
richbumx said:
i'm on L-04.. would this not work for me then?
Click to expand...
Click to collapse
parleyp said:
Try this boot image. You can flash it from twrp. Do not clear the cache or davlik. Reboot and install the phh super user apk.
https://forum.xda-developers.com/attachment.php?attachmentid=4070615&d=1489245825
https://forum.xda-developers.com/showpost.php?p=71382542&postcount=85
Parleyp
Click to expand...
Click to collapse
skrapmetal said:
I just tried this and it WORKS! I'm on EMUI 5 with my L-04. Now I can FINALLY block ads! Thanks for the info!
Click to expand...
Click to collapse
So we know it works on the L04 and L14. Does not work on L09.
L09 works
parleyp said:
So we know it works on the L04 and L14. Does not work on L09.
Click to expand...
Click to collapse
Wrong
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks for the update. I am happy is is working on yours.
skrapmetal said:
I just tried this and it WORKS! I'm on EMUI 5 with my L-04. Now I can FINALLY block ads! Thanks for the info!
Click to expand...
Click to collapse
I am also trying to get root on an H8 FRD-L04. So does this boot.img file get flashed in twrp like any other zip file or do I need to choose different options in twrp to write it to the correct place?
Also can you tell me which version of twrp you are using? There seem to be several floating around on xda.
Have you had any other issues with apps that need root since you did this? I'd like to get my favorite xposed mods working on my H8.
vouty said:
I am also trying to get root on an H8 FRD-L04. So does this boot.img file get flashed in twrp like any other zip file or do I need to choose different options in twrp to write it to the correct place?
Also can you tell me which version of twrp you are using? There seem to be several floating around on xda.
Have you had any other issues with apps that need root since you did this? I'd like to get my favorite xposed mods working on my H8.
Click to expand...
Click to collapse
Unzip the file first, that should leave you with bootr.img I think it's called. Make a backup just in case, but yes, flash it just like you would anything else, no need to wipe anything and no I did not change any settings.
I'm using TWRP 3.0.3 found here https://forum.xda-developers.com/honor-8/development/twrp-t3566563
I have tried at least 5 apps that have needed root and have not had any issues. I haven't tried xposed yet though.
skrapmetal said:
Unzip the file first, that should leave you with bootr.img I think it's called. Make a backup just in case, but yes, flash it just like you would anything else, no need to wipe anything and no I did not change any settings.
I'm using TWRP 3.0.3 found here https://forum.xda-developers.com/honor-8/development/twrp-t3566563
I have tried at least 5 apps that have needed root and have not had any issues. I haven't tried xposed yet though.
Click to expand...
Click to collapse
And so the bootr.img is 'pre-rooted" so I don't then need to flash "SuperSU-v2.79-201612051815-EMUI5.0.zip" or any other SU zip file, or format the Data partition as some other threads have mentioned, to get root, is that correct?
vouty said:
And so the bootr.img is 'pre-rooted" so I don't then need to flash "SuperSU-v2.79-201612051815-EMUI5.0.zip" or any other SU zip file, or format the Data partition as some other threads have mentioned, to get root, is that correct?
Click to expand...
Click to collapse
I did not format or wipe anything. I simply backed up my boot.img and flashed bootr.img. I did not flash anything else. After that, I rebooted and installed phh Superuser from the play store. That's it.
skrapmetal said:
I did not format or wipe anything. I simply backed up my boot.img and flashed bootr.img. I did not flash anything else. After that, I rebooted and installed phh Superuser from the play store. That's it.
Click to expand...
Click to collapse
Sounds easy enough. I'll give it a try. Then I'm gonna go for getting xposed and adaway working.
hi, i confirm the modified boot.img (b378) and root works with b380 rom ?
Thanks
Jsbcterpper said:
You are right , i agree with you
Click to expand...
Click to collapse
No.
It does work in the L09, check my post on the previous page.
I just flashed a custom ROM (Pixel Experience A11) originally starting from MIUI Global 12.0.4
Then I flashed the Global 12.0.7 firmware via TWRP (found here https://xiaomifirmwareupdater.com/firmware/surya/).
However, I forgot to check version numbers of anything before flashing, so I don't know what to look for to verify the new firmware is flashed properly?
Thanks!
@uddinf you could also switch to Orange Fox recovery, after you reboot to recovery on startup screen you will see several info about your device including actual fw number...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
jeryll said:
@uddinf you could also switch to Orange Fox recovery, after you reboot to recovery on startup screen you will see several info about your device including actual fw number...
Click to expand...
Click to collapse
Thanks for the reply. I've switched and booted into Orange Fox version 6 (from here) but don't know exactly what to press to get to the firmware info.
uddinf said:
Thanks for the reply. I've switched and booted into Orange Fox version 6 (from here) but don't know exactly what to press to get to the firmware info.
Click to expand...
Click to collapse
please if you stick with the Orange fox recovery install the latest version, enjoy
jeryll said:
please if you stick with the Orange fox recovery install the latest version, enjoy
Click to expand...
Click to collapse
Thank you for that version update. It's been a while since I've flashed roms so I'm still feeling my way around the new tools/methods.
Unfortunately I don't see what version I have
uddinf said:
Thank you for that version update. It's been a while since I've flashed roms so I'm still feeling my way around the new tools/methods.
Unfortunately I don't see what version I have
Click to expand...
Click to collapse
look for the release row, it's there
jeryll said:
look for the release row, it's there
Click to expand...
Click to collapse
I was meaning the Xiaomi FW version. It doesn't show for some reason.
uddinf said:
I was meaning the Xiaomi FW version. It doesn't show for some reason.
Click to expand...
Click to collapse
interesting, I reread your original post and found that you only flashed fw (without vendor), i suggest you read this post, where are at the beginning links to the whole fw+vendor (mind you it's big around 2 GB archive needed to be flashed before flashing custom ROM)...
I suppose that is the reason why is it not showing fw version. If you will flash that and will still not show fw version, then we'll have a new mystery here... Hm, just flash that fw+vendor archive, reboot recovery and check the info screen again and report here, thanks...
jeryll said:
interesting, I reread your original post and found that you only flashed fw (without vendor), i suggest you read this post, where are at the beginning links to the whole fw+vendor (mind you it's big around 2 GB archive needed to be flashed before flashing custom ROM)...
I suppose that is the reason why is it not showing fw version. If you will flash that and will still not show fw version, then we'll have a new mystery here... Hm, just flash that fw+vendor archive, reboot recovery and check the info screen again and report here, thanks...
Click to expand...
Click to collapse
I appreciate all the input
Correct, I did not flash vendor so that is likely my problem.
I will follow your post and flash the MIUI.eu archive
One question though, you say "needed to be flashed before flashing custom ROM"...
Does that mean I have to go back to original ROM via Miflash first or do I just flash the 2gb archive from your post straight away via orange fox?
uddinf said:
Does that mean I have to go back to original ROM via Miflash first or do I just flash the 2gb archive from your post straight away via orange fox?
Click to expand...
Click to collapse
yep, you can flash it directly in , but since it's a whole usable ROM, it will also overwrite your currently flashed ROM, so if you want to use customized MIUI, don't flash anything else and just boot it, or flash whatever custom ROM you want to use directly after + necessary steps like GAPPS and after boot magisk...
jeryll said:
yep, you can flash it directly in , but since it's a whole usable ROM, it will also overwrite your currently flashed ROM, so if you want to use customized MIUI, don't flash anything else and just boot it, or flash whatever custom ROM you want to use directly after + necessary steps like GAPPS and after boot magisk...
Click to expand...
Click to collapse
Everything seems to be up and running. thanks for all the help!
How to check after getting to oragr fox mane page
Stable just landed and is nice. Testing battery optimization differences in stable and ob2 that I came from. Great it's here
mattie_49 said:
Stable just landed and is nice. Testing battery optimization differences in stable and ob2 that I came from. Great it's here
Click to expand...
Click to collapse
Do you have boot.img? i don't have good internet for download full ota and extract it :/
franko_m19 said:
Do you have boot.img? i don't have good internet for download full ota and extract it :/
Click to expand...
Click to collapse
Do you have full ota link?
franko_m19 said:
Do you have boot.img? i don't have good internet for download full ota and extract it :/
Click to expand...
Click to collapse
franko_m19 said:
Do you have boot.img? i don't have good internet for download full ota and extract it :/
Click to expand...
Click to collapse
https://drive.google.com/file/d/11bXba50WUUlrgRRyoGCVYqZZXdmvsfiW/view?usp=drivesdk.
I've already patched this. Fastboot flash this then go into magisk let it reboot if it asks to continue setup. Rooted an A13 stock
mattie_49 said:
https://drive.google.com/file/d/11bXba50WUUlrgRRyoGCVYqZZXdmvsfiW/view?usp=drivesdk.
I've already patched this. Fastboot boot this then go into magisk and direct install to backup stock for you.
Click to expand...
Click to collapse
Thx @mattie_49 it's working in LE2115. I started to download and time estimate was 3 hours xd
@mattie_49 : How do you download it? Or where did you got it? With oxygen updater I get 11_C.66
AxelM said:
@mattie_49 : How do you download it? Or where did you got it? With oxygen updater I get 11_C.66
Click to expand...
Click to collapse
Oxygen updater
mh, I only receive 11_C.66 maybe I have to wait
after installing c.66 i received it. @mattie_49 Do you root it like common (patch boot.img via magisk and install it) or are more changes necessary?
franko_m19 said:
Thx @mattie_49 it's working in LE2115. I started to download and time estimate was 3 hours xd
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I try to boot your patched .img, my phone goes to "Fastboot Mode |1+|" screen and hangs there. Doesn't make a difference what slot I'm in.
fhedeitx said:
View attachment 5757793
When I try to boot your patched .img, my phone goes to "Fastboot Mode |1+|" screen and hangs there. Doesn't make a difference what slot I'm in.
Click to expand...
Click to collapse
It's the official 16 patched. Just fastboot flash it or ask guy above . He got working with it.
AxelM said:
after installing c.66 i received it. @mattie_49 Do you root it like common (patch boot.img via magisk and install it) or are more changes necessary?
Click to expand...
Click to collapse
No sir I carried it over with magisk from 11 originally. MSM,unlock bl. Patch boot . Then disable modules and carry from A11 to A12 then so on.
fhedeitx said:
View attachment 5757793
When I try to boot your patched .img, my phone goes to "Fastboot Mode |1+|" screen and hangs there. Doesn't make a difference what slot I'm in.
Click to expand...
Click to collapse
fastboot flash boot *boot_name*.img
franko_m19 said:
fastboot flash boot *boot_name*.img
Click to expand...
Click to collapse
I wanted to try booting it before flashing. I tried flashing and same thing happened. Now I'm back at MSMTool
_MartyMan_ said:
Do you have full ota link?
Click to expand...
Click to collapse
No but flash one of the open betas. That's how I received so fast. Was on ob2 and it's getting it first.
fhedeitx said:
I wanted to try booting it before flashing. I tried flashing and same thing happened. Now I'm back at MSMTool
Click to expand...
Click to collapse
I don't had any problem with the img, I upgraded with magisk installed. And now it's working with root.
Do you have Global? Or NA?
franko_m19 said:
I don't had any problem with the img, I upgraded with magisk installed. And now it's working with root.
Do you have Global? Or NA?
Click to expand...
Click to collapse
Global (I believe) LE2115 in US
mattie_49 said:
Oxygen updater
Click to expand...
Click to collapse
I was on open beta 2 is why I received very first. That's the order they put rollout in. To ob 1& 2 before stock devices.
Install in inactive slot (after ota) in magisk is working for upgrading from android 12 to 13 (using oxygen updater zip file) ?Edit: this doesn't work because the device reboots when the installation starts.
Remove magisk boot image from magisk app, update and turn off the device...boot to fastboot and do a fastboot boot magisk_patched.img (you have to extract the boot image with payload dumper and patch it before or after the installation with magisk. Then do a direct install from magisk (on the temp root boot image).
On android 13 you will have this warning on every reboot: Orange state, Your device has been uplocked and can't be trusted.
Thanks for this! I have not had root on my Oneplus 9 for a while and it was driving my _crazy_. Had to do fastboot flash boot boot.img instead of fastboot boot boot.img to get magisk to work properly.
I had to jump through some extraordinary hoops to get it done including breaking out an old Win10 laptop since I could never get my new Win11 laptop to recognize my phone in fastboot, despite hours of work trying to install the drivers to no success.