I have just received an OTA update. No Android 7 unfortunately, but February security update and bugupdates. Was about 325Mb download and a few restarts
{
"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"
}
Went from:
to
Sent from my Lenovo YB1-X90F using Tapatalk
Everything good over here. Applied update couple of days back. It's released some memory and seems a bit snappier in intensive games.
Any issues with rooted devices? Any problems with rooting this again? I am guessing that it will break the root.
Is there a release log?
I hope you don't mind me hijacking your post slightly, but has anyone had any luck updating after unlocking the bootloader? I just tried updating, it got about half way through the install and then aborted. I'd already re-locked the bootloader, but upon booting the tablet it says something like "verification failed". Am I doomed to forever rely on flashing new stock roms, rather than ota updates?
Dazzman88 said:
I hope you don't mind me hijacking your post slightly, but has anyone had any luck updating after unlocking the bootloader? I just tried updating, it got about half way through the install and then aborted. I'd already re-locked the bootloader, but upon booting the tablet it says something like "verification failed". Am I doomed to forever rely on flashing new stock roms, rather than ota updates?
Click to expand...
Click to collapse
sad....I am in the same situation with you, hope there will be some workarounds....
With an unlocked bootloader.
Steps I took:
1. downloaded and captured the update. The update is saved at: /data/data/com.lenovo.ota/app_otapackages.
2. copied the update.zip to my external sd-card.
3. boot in the stock recovery menu.
4. choose apply update from external storage.
5. wait untill finished, system restarts.
System booted just fine. After booting my Playstore app crashed constantly. I flashed the latest gapps from open gapps and everything is just fine.
Rooted again with Magisk. Choose for 10.1 because 11.1 keeps giving me problems with Titanium. No problems rooting after update.
My first attempt failed because I was still rooted, so I reflashed my stock boot image with twrp. No problems flashing the update after this. Maybe by flashing the boot image first and using the update function from within works but after the messages of failing updates I decided to try this approach.
Note: my model is YB1-X90L
Verstuurd vanaf mijn Lenovo YB1-X90L met Tapatalk
vogemic said:
With an unlocked bootloader.
Steps I took:
1. downloaded and captured the update. The update is saved at: /data/data/com.lenovo.ota/app_otapackages.
2. copied the update.zip to my external sd-card.
3. boot in the stock recovery menu.
4. choose apply update from external storage.
5. wait untill finished, system restarts.
System booted just fine. After booting my Playstore app crashed constantly. I flashed the latest gapps from open gapps and everything is just fine.
Rooted again with Magisk. Choose for 10.1 because 11.1 keeps giving me problems with Titanium. No problems rooting after update.
My first attempt failed because I was still rooted, so I reflashed my stock boot image with twrp. No problems flashing the update after this. Maybe by flashing the boot image first and using the update function from within works but after the messages of failing updates I decided to try this approach.
Note: my model is YB1-X90L
Verstuurd vanaf mijn Lenovo YB1-X90L met Tapatalk
Click to expand...
Click to collapse
How did you capture the update? Does not it restart automatically?
Also when you say "stock boot image" , what do you mean exactly? Do you mean boot partition or just the original backup?
---------- Post added at 05:01 AM ---------- Previous post was at 04:30 AM ----------
My update error says "error in update.zip"
hajkan said:
How did you capture the update? Does not it restart automatically?
Also when you say "stock boot image" , what do you mean exactly? Do you mean boot partition or just the original backup?
---------- Post added at 05:01 AM ---------- Previous post was at 04:30 AM ----------
My update error says "error in update.zip"
Click to expand...
Click to collapse
Just downloaded it. It doesn't restart automatically. You have to confirm to install the update. I booted directly into the bootloader after copying the update to my external SD-card.
After rooting with Magisk there is a backup of your original boot.img. This can be found in /data. There you see magisk.img and stock_boot.img. Copy the stock_boot.img to your external SD-card.
I didn't rename the ota-file after downloading it. Just flashed the file from stock recovery. Maybe you have a corrupt download?
Verstuurd vanaf mijn Lenovo YB1-X90L met Tapatalk
vogemic said:
Just downloaded it. It doesn't restart automatically. You have to confirm to install the update. I booted directly into the bootloader after copying the update to my external SD-card.
After rooting with Magisk there is a backup of your original boot.img. This can be found in /data. There you see magisk.img and stock_boot.img. Copy the stock_boot.img to your external SD-card.
I didn't rename the ota-file after downloading it. Just flashed the file from stock recovery. Maybe you have a corrupt download?
Verstuurd vanaf mijn Lenovo YB1-X90L met Tapatalk
Click to expand...
Click to collapse
Yeah that is what I did as far as the download goes. I tried both as update.zip and the original name.
I did not know the original boot.img was there. How did you flash those imgs back ?
hajkan said:
Yeah that is what I did as far as the download goes. I tried both as update.zip and the original name.
I did not know the original boot.img was there. How did you flash those imgs back ?
Click to expand...
Click to collapse
Flash image with twrp to boot. Choose install and then tap on the*Images…*button on the bottom-right of the screen. Once you select, you will be prompted to select the type of image it is, select*Boot*or*Recovery. Choose boot.
Verstuurd vanaf mijn Nexus 6P met Tapatalk
vogemic said:
Flash image with twrp to boot. Choose install and then tap on the*Images…*button on the bottom-right of the screen. Once you select, you will be prompted to select the type of image it is, select*Boot*or*Recovery. Choose boot.
Verstuurd vanaf mijn Nexus 6P met Tapatalk
Click to expand...
Click to collapse
Cool, I thought that TWRP was only able to flash zips.
Can you please tell me which .imgs you flashed back exactly? I do not want to mess this up. Did you just flash "stock_boot.img"?
Also did you need to lock the bootloader as well? I hope you did not need to because I so do not want to erase all my data again to unlock it back.
hajkan said:
Cool, I thought that TWRP was only able to flash zips.
Can you please tell me which .imgs you flashed back exactly? I do not want to mess this up. Did you just flash "stock_boot.img"?
Also did you need to lock the bootloader as well? I hope you did not need to because I so do not want to erase all my data again to unlock it back.
Click to expand...
Click to collapse
Only stock boot image. No need to lock the bootloader. So you keep your data?.
Verstuurd vanaf mijn Nexus 6P met Tapatalk
vogemic said:
Only stock boot image. No need to lock the bootloader. So you keep your data.
Verstuurd vanaf mijn Nexus 6P met Tapatalk
Click to expand...
Click to collapse
I do not have stock_boot.img The only img i have is the one from magisck. So what do I do? Why do not I have the original one, no idea.
Does anyone have the original stock_boot.img for YB1-X90F?
Also here is the error I get when I try to update tp the latest
hajkan said:
I do not have stock_boot.img The only img i have is the one from magisck. So what do I do? Why do not I have the original one, no idea.
Does anyone have the original stock_boot.img for YB1-X90F?
Also here is the error I get when I try to update tp the latest
Click to expand...
Click to collapse
Looks like the same message I got. Are you looking in system/data ? For me the full path is: system(root)/data/stock_boot.img.
Verstuurd vanaf mijn Lenovo YB1-X90L met Tapatalk
Yeah it is /data
hajkan said:
Yeah it is /data
Click to expand...
Click to collapse
Strange. What version of Magisk are you running?
Did you make a recent nandroid backup in TWRP before flashing Magisk? It also containes the boot image.
I found an older firmware for your model. YB1-X90F_USR_S000196_1611040312. Don't know if this works because of the older firmware. I extracted the boot.img.http://cloud.tapatalk.com/s/58bbb8483b6a0/boot.img.zip. Flash at your own risk.
Verstuurd vanaf mijn Lenovo YB1-X90L met Tapatalk
Yeah I have the full system backup. And I actually went ahead and restored the original boot image of stock system backup and it did not work out.
Thanks for linking a boot image. I will try flashing that one to see if it wil work.
vogemic said:
Strange. What version of Magisk are you running?
Did you make a recent nandroid backup in TWRP before flashing Magisk? It also containes the boot image.
I found an older firmware for your model. YB1-X90F_USR_S000196_1611040312. Don't know if this works because of the older firmware. I extracted the boot.img.http://cloud.tapatalk.com/s/58bbb8483b6a0/boot.img.zip. Flash at your own risk.
Verstuurd vanaf mijn Lenovo YB1-X90L met Tapatalk
Click to expand...
Click to collapse
deleted
Anyone else notice it seems to have included an update the Note Saver app? it can now go into portrait mode, and existing notes don't open in edit mode anymore by default.
This update broke ability to switch languages by click ctrl + space on Halo keyboard. It's very sad for me.
???
Related
Hey guys,
I'm having a bit of a hard time flashing CM again, everytime I try to flash any ROM TWRP just leaves me with an error 7 (something along the lines of "This file is for e1003, your device is ONE).
I know I can just delete the updater script but can someone give me a permanent solution to this?
(I'm running the official TWRP 3.something, oxygen os and bluespark's kernel)
(Also I was able to flash CM in the past but it is not working now)
(Just one more thing - feel free to leave an explanation on why this happen, I'm a curious and geeky guy
Is it TWRP 3.0.0.1 ?
If not, reflash it by adb or from the TWRP. BE CAREFULL , do a FLASH IMAGE not zip !
https://dl.twrp.me/onyx/
Or try one here :
http://forum.xda-developers.com/oneplus-x/development/recovery-t3295363
I think ROM is for E1003 and your device is E1001 at the back in the bottom it is mentioned check it ☺☺
Kéno40 said:
Is it TWRP 3.0.0.1 ?
If not, reflash it by adb or from the TWRP. BE CAREFULL , do a FLASH IMAGE not zip !
https://dl.twrp.me/onyx/
Or try one here :
http://forum.xda-developers.com/oneplus-x/development/recovery-t3295363
Click to expand...
Click to collapse
Already reflashed TWRP but throw flashify - might that be the problem?
Sultan0274 said:
I think ROM is for E1003 and your device is E1001 at the back in the bottom it is mentioned check it
Click to expand...
Click to collapse
Nope my phone is e1003
pedrof1991 said:
Already reflashed TWRP but throw flashify - might that be the problem?
Click to expand...
Click to collapse
Don't know, I never flash recovery on OPX from Flashify.
Always via ADB or via TWRP directly.
Kéno40 said:
Don't know, I never flash recovery on OPX from Flashify.
Always via ADB or via TWRP directly.
Click to expand...
Click to collapse
I think I've found the problem! I was flashing the first ever build of CM 13 LMAO!
I'm re-downloading the ROM now - whish me luck
Solved!
Yeah the problem was that I was using the first but of CM 13 which one had one device name supported (E1003) now it support our device with three different "code names" (ONE, E1003, Onyx and Oneplus).
Thanks for all the help guys
pedrof1991 said:
Already reflashed TWRP but throw flashify - might that be the problem?
Nope my phone is e1003
Click to expand...
Click to collapse
I always use flashify. I don't even need a PC to switch ROMs anymore haha since the OPX is officially supported by TWRP you can't really do it wrong anymore. download TWRP in flashify and flash. doesn't get easier than that.
Which version supports different "code names" (ONE, E1003, Onyx and Oneplus). ?
pedrof1991 said:
Yeah the problem was that I was using the first but of CM 13 which one had one device name supported (E1003) now it support our device with three different "code names" (ONE, E1003, Onyx and Oneplus).
Thanks for all the help guys
Click to expand...
Click to collapse
Which version of CM 13 should i download that supports all the code names ? If you can paste a link would be very grateful
Thank you
Try this one :
http://forum.xda-developers.com/one...m-kernel-unofficial-cyanogenmod-13-0-t3375221
Start with installing TWRP V > 3
Kéno40 said:
Try this one :
http://forum.xda-developers.com/one...m-kernel-unofficial-cyanogenmod-13-0-t3375221
Start with installing TWRP V > 3
Click to expand...
Click to collapse
Thank you i tried but this shows now "can't install this package on top of incompatible data "
Im having the same kernal version my TWRP is > 3.
Please see this https://s32.postimg.org/mcxs3y98l/IMG_20160712_WA0006.jpg This package is for device onyx, E1003 , your device is ONE
arjun_aj said:
Thank you i tried but this shows now "can't install this package on top of incompatible data "
Im having the same kernal version my TWRP is > 3.
Please see this https://s32.postimg.org/mcxs3y98l/IMG_20160712_WA0006.jpg This package is for device onyx, E1003 , your device is ONE
Click to expand...
Click to collapse
First go to settings in the recovery and disable the zip files verification try to flash again.
Second if 1st don't work : With the 3... TWRP, flash the Sultan's recoveryimg as recovery . Forget that, I read bad your screenshot !
Go to install / install image at the booton right. Click on the . img file and flash as recovery !
Reboot recovery than you should be able to flash everything.
---------- Post added at 04:20 PM ---------- Previous post was at 03:46 PM ----------
Third :
in \META-INF\com\google\android\updater-script
erase tyhe line about the phone verification and it should work !!
But that's weired... It should be fixed now with a recent CM and a uptodate TWRP....
Kéno40 said:
First go to settings in the recovery and disable the zip files verification try to flash again.
Second if 1st don't work : With the 3... TWRP, flash the Sultan's recoveryimg as recovery . Forget that, I read bad your screenshot !
Go to install / install image at the booton right. Click on the . img file and flash as recovery !
Reboot recovery than you should be able to flash everything.
---------- Post added at 04:20 PM ---------- Previous post was at 03:46 PM ----------
Third :
in \META-INF\com\google\android\updater-script
erase tyhe line about the phone verification and it should work !!
But that's weired... It should be fixed now with a recent CM and a uptodate TWRP....
Click to expand...
Click to collapse
Tried all but no luck
{
"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"
}
Sultan's as well as another build
Sultan's latest build has codename ONE mentioned but no luck here too
Should i wipe all data and redo?
Seriously, whith this new error message, I think something is messed up.
Just to be sure, you unlock the phone with the full procedure. i.e. unlock bootloader, flash custom recovery.... Right?
If so, I think, you should erase all. Install the full OOS 2.2.1-X zip .
http://downloads.oneplus.net/oneplus-x/oneplus_x_oxygenos_2.2.1-x/
And then rewipe and install CM.
If it doesn't work , you will have to format more deeply (just format Cache data & system, not internal data.)
Kéno40 said:
Seriously, whith this new error message, I think something is messed up.
Just to be sure, you unlock the phone with the full procedure. i.e. unlock bootloader, flash custom recovery.... Right?
If so, I think, you should erase all. Install the full OOS 2.2.1-X zip .
http://downloads.oneplus.net/oneplus-x/oneplus_x_oxygenos_2.2.1-x/
And then rewipe and install CM.
If it doesn't work , you will have to format more deeply (just format Cache data & system, not internal data.)
Click to expand...
Click to collapse
Yes im rooting with KingRoot latest and TWRP Recovery latest, Tried HydrogenOS https://forums.oneplus.net/threads/ultimate-guide-for-hydrogen-os.446790/ in between that flashed successfully. (That was buggy for me ) flashed to OOS 2.2.1-x
arjun_aj said:
Yes im rooting with KingRoot latest
Click to expand...
Click to collapse
That's why I think !!
You should have done that :
http://forum.xda-developers.com/oneplus-x/general/discussion-how-to-root-oneplus-x-t3242830
Kéno40 said:
Is it TWRP 3.0.0.1 ?
If not, reflash it by adb or from the TWRP. BE CAREFULL , do a FLASH IMAGE not zip !
https://dl.twrp.me/onyx/
Or try one here :
http://forum.xda-developers.com/oneplus-x/development/recovery-t3295363
Click to expand...
Click to collapse
TWRP 3.0 is official and is it working on onyx?
Of course
Hey, I'm using a Oneplus X running the latest CM 13 nightly, and TWRP 3.0.2.0, and I always get error 7. What can I do?
_mikelanda said:
Hey, I'm using a Oneplus X running the latest CM 13 nightly, and TWRP 3.0.2.0, and I always get error 7. What can I do?
Click to expand...
Click to collapse
Which twrp version you are using?
Official or unofficial?
Folks,
I really need your help.
I bought p9000 a week ago, and did the standard upgrades via OTA.
I read about the Android Nougat version, and I decided to install via Flash Tools, however, due to the various bugs, I decided to go back to Marshmellow version 6.0.
The problem happened after I used the flash tools, it simply bricked.
The process happened correctly, but it just does not start.
I read in other forums to try to remove the plug from the battery, and so I did, but did not solve anything, my computer simply does not recognize the device.
I use Windows 10 x64 ... Please, anyone know how to recover a braided device?
I'm waiting.
Thank you very much.
Regards
Alicio04
SOLUTION
I found the solution.
I used the Nougat version bootloader, and I connected the phone.
I uninstalled all previously installed drivers, (MTK driver) and even dead, I held the volume up button, and the PC recognized the device, installing the bootloader normally via flash tools.
I'm very happy that it worked, if anyone needs help, this is a solution.
Regards
Mind throwing quick guide on how to flash bootloader? I got similar problem. My phone is dead for over a week now and I cant seem to fix it. PC recognize it, drivers are all good. When i Click "Download" on Flashtools and connect my phone, process goes well and everything ends with "ok", but phone is not starting. It just hangs on Elephone logo. Also if this is helpful in order to determine my problem, I rebooted into recovery but recovery is not recognizing my Internal Memory when I try to Wipe Data or Wipe Cache. Even tho I can browse through my Internal and External memories. Please help and thanks in advance!
stewakg said:
Mind throwing quick guide on how to flash bootloader? I got similar problem. My phone is dead for over a week now and I cant seem to fix it. PC recognize it, drivers are all good. When i Click "Download" on Flashtools and connect my phone, process goes well and everything ends with "ok", but phone is not starting. It just hangs on Elephone logo. Also if this is helpful in order to determine my problem, I rebooted into recovery but recovery is not recognizing my Internal Memory when I try to Wipe Data or Wipe Cache. Even tho I can browse through my Internal and External memories. Please help and thanks in advance!
Click to expand...
Click to collapse
thats due to preloader, try using the updated preloader, you can find in lineage thread, it should boot normally after
Ruben Craveiro said:
thats due to preloader, try using the updated preloader, you can find in lineage thread, it should boot normally after
Click to expand...
Click to collapse
I will try that tonight. Thanks for your suggestion. What should be clicked before I click download? Ona preloader or it should be all?
stewakg said:
I will try that tonight. Thanks for your suggestion. What should be clicked before I click download? Ona preloader or it should be all?
Click to expand...
Click to collapse
i guess all except boot partition bevause i think it comes with it too, but might not make it boot if you have a different version of android, if it still doesnt work try flashing latest stock rom with latest preloader and should work
{
"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"
}
Maybe twrp recovery will work
This picture was taken after following official guide in lineage thread. After this I have flashed stock rom 08.10 but it won't boot
stewakg said:
This picture was taken after following official guide in lineage thread. After this I have flashed stock rom 08.10 but it won't boot
Click to expand...
Click to collapse
Flash stock rom but replace preloader with the lineage os preloader, it should boot
Ruben Craveiro said:
Flash stock rom but replace preloader with the lineage os preloader, it should boot
Click to expand...
Click to collapse
Its a no go... First I flashed 10.08.2016 version and it didn't boot. Then I tried with lineage preloader (checked only preloader without rest of the options) and still won't boot. Flashed latest version 12.01.2017, still wont boot. Tried with preloader from lineage, and it still ain't booting. Am I missing something?
Thanks in advance
stewakg said:
Its a no go... First I flashed 10.08.2016 version and it didn't boot. Then I tried with lineage preloader (checked only preloader without rest of the options) and still won't boot. Flashed latest version 12.01.2017, still wont boot. Tried with preloader from lineage, and it still ain't booting. Am I missing something?
Thanks in advance
Click to expand...
Click to collapse
If it powers on, use johnnys twrp version 8, and flash lineage os, it should boot
---------- Post added at 08:45 PM ---------- Previous post was at 08:36 PM ----------
stewakg said:
Its a no go... First I flashed 10.08.2016 version and it didn't boot. Then I tried with lineage preloader (checked only preloader without rest of the options) and still won't boot. Flashed latest version 12.01.2017, still wont boot. Tried with preloader from lineage, and it still ain't booting. Am I missing something?
Thanks in advance
Click to expand...
Click to collapse
Ill just tell you the partitions i flashed in order to make it boot, i flashed lineageOS using twrp on old Preloader, which made it constantly go on reboot loop, then i used the file named "preloader for updated versions" which flashed Preloader, lk, lk2 and boot partition (i unticked recovery partition) and jt booted lineage normally. You might need to update the twrp to 3.0.2-8 if not already, after you flash the updated preloader.
Updated preloader, installed twrp 0.8 and here are results:
stewakg said:
Updated preloader, installed twrp 0.8 and here are results:
Click to expand...
Click to collapse
Hi.
Did you solved your problem?
greetings
vsrookie
Sent from my P9000 using XDA-Developers Legacy app
vsrookie said:
Hi.
Did you solved your problem?
greetings
vsrookie
Sent from my P9000 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Unfortunately not
Hi.
Did you tried to flash stock again with splashtool? With all partitions and begin from scratch?
greetings
vsrookie
Sent from my P9000 using XDA-Developers Legacy app
Kraj, tries that. All the time same result. Phone is not booting. Hangs on elephone logo.
Hi.
Which stockrom did you try?
greetings
vsrookie
Sent from my P9000 using XDA-Developers Legacy app
Latest and 10.08.2016 versions.
stewakg said:
Latest and 10.08.2016 versions.
Click to expand...
Click to collapse
Flash 20160304 preloader and keep trying. It takes a couple of attempts and hold the volume up button. flash only the preloader. Afterwards flash the latest rom
Heres the latest update from LG.
Must be at least 20f/g with TWRP to flash this.
To get TWRP go here: (Kdz to 20f if on 20g)
https://forum.xda-developers.com/showthread.php?t=3533338
Do NOT wipe system or you might get stuck in twrp bootloop.
Includes new 20H modem.
**********************
FLASHING INSTRUCTIONS
**********************
1. WARNING, MUST BE IN 20F/G. IF ON LINEAGE, DO NOT FLASH. YOU MUST KDZ TO 20F OR RESTORE 20F BACKUP FIRST.
2. DO NOT FORMAT SYSTEM.
2. TWRP BACKUP FIRST
3. Flash from TWRP.
DOWNLOAD
LG-V521-20H-Stock-Rooted.zip
https://www.androidfilehost.com/?fid=745425885120726661
Sent from my LG-V521 using Tapatalk
{
"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"
}
Does it include the modem?
I'm going to try from lineage.
Edit -flashed from lineage worked fine. It rebooted straight from twrp so i wasn't sure if the flash comppeted. After waiting at bootscreen i still wasn't sure so i did the volume down, power button combo and it booted into system fine.
Edit 2 - no root and loss twrp
Airtioteclint said:
Does it include the modem?
I'm going to try from lineage.
Edit -flashed from lineage worked fine. It rebooted straight from twrp so i wasn't sure if the flash comppeted. After waiting at bootscreen i still wasn't sure so i did the volume down, power button combo and it booted into system fine.
Edit 2 - no root and loss twrp
Click to expand...
Click to collapse
Lineage always messes up going back to stock roms. I've had this problem to on 20g to after being on lineage. You'll have to kdz to 20f and get twrp. I had put this on the flashing instructions you must be on 20f/g. .
It does include modem.
Sent from my SM-G955U using Tapatalk
MicroMod777 said:
Lineage always messes up going back to stock roms. I've had this problem to on 20g to after being on lineage. You'll have to kdz to 20f and get twrp. I had put this on the flashing instructions you must be on 20f/g. .
It does include modem.
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
Yeah kdz 20f and was able to get root back. Reinstalled your 20h and everything's working flawlessly. I was having problems with my touchscreen being a little laggy and I think your rom fixed it. :good:
Any way to install this update from SD card on stock recovery? I get error Everytime the regular way. Thanks
Hawksronny said:
Any way to install this update from SD card on stock recovery? I get error Everytime the regular way. Thanks
Click to expand...
Click to collapse
Impossible.
Sent from my SM-G955U using Tapatalk
MicroMod777 said:
Impossible.
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
So even though there is an option to update from SD in stock recovery, it's impossible? Just want to confirm. Just doesn't make sense to me
Hawksronny said:
So even though there is an option to update from SD in stock recovery, it's impossible? Just want to confirm. Just doesn't make sense to me
Click to expand...
Click to collapse
Then try it! lol
Sent from my SM-G955U using Tapatalk
MicroMod777 said:
Then try it! lol
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
I'm no developer. I just want to update without rooting or custom recovery. I try it 2 ways, and fails the normal way, and the stock recovery doesn't recognize the update.zip the 2nd way. I probably have it named wrong. Either way, I doubt it's impossible. Any help would be appreciated. Thanks
Hawksronny said:
I'm no developer. I just want to update without rooting or custom recovery. I try it 2 ways, and fails the normal way, and the stock recovery doesn't recognize the update.zip the 2nd way. I probably have it named wrong. Either way, I doubt it's impossible. Any help would be appreciated. Thanks
Click to expand...
Click to collapse
Its very, very impossible to flash this rom except per twrp.
LG uses security keys to flash anything from stock recovery.
Sent from my SM-G955U using Tapatalk
I don't want to flash a rom. I asked how to flash the stock update from the stock recovery because the update errors out when I try to do it the normal ota way. There is an option to update from SD in the stock recovery. It's just that it doesn't recognize the stock update.zip in the stock recovery because I probably don't have it named right. Was just wondering if anyone knew what to name it, where to download the update.zip, how to update with it etc. Didn't mean to offend anybody ?
Hawksronny said:
I don't want to flash a rom. I asked how to flash the stock update from the stock recovery because the update errors out when I try to do it the normal ota way. There is an option to update from SD in the stock recovery. It's just that it doesn't recognize the stock update.zip in the stock recovery because I probably don't have it named right. Was just wondering if anyone knew what to name it, where to download the update.zip, how to update with it etc. Didn't mean to offend anybody ?
Click to expand...
Click to collapse
No offence taken. All good. You just can't do that. [emoji4]
Sent from my SM-G955U using Tapatalk
Should i be able to downgrade from 20h to 20 f to root. I just got a new one on a warranty exchange and get an error in lgup at 4%. Sorry if this is off topic
same question, some body can check antirollback, this tab can downgrade from v521 v20h to v20f or mashmallow or not
Thanks
[ROM] T-Mobile LG G Pad X V521 20i Stock ROM Rooted TWRP\FF Backups Release 7/1/2017
A TWRP backup of a stock rooted v52120i:
Code:
https://drive.google.com/file/d/0B6L7kMY8TK7uZ2lPMUhtVmRINUk/view?usp=sharing
FlashFire Restore from backup:
Code:
https://drive.google.com/file/d/0B6L7kMY8TK7uQlFfY3lJTVl1X1k/view?usp=sharing
To install, move files to designated place (twrp/backups/{phoneid}/) or (FlashFire/backups).
at least 20f and root required.
saw nobody put it up so i decided i would.
Mine still has rooted 10c. How to update to this latest ROM and rooted ? TIA
Does 7.0 improve idling/sleeping battery ?
Yes that is probably one of its biggest changes vs MM.
Follow this guide to a T: https://forum.xda-developers.com/lg-g-pad-83/development/nougat-7-0-v521-guide-to-update-v521-lg-t3533338
then boot into recovery, copy my TWRP backup to internal/microsd/usb, in TWRP restore the system and boot partitions that are automatically checked.
Download the latest systemless or system mode supersu.zip and copy it to the main install folder C:\Program Files x86\Minimal ADB and Fastboot\.
Then in twrp click ADB sideload > do not check anything to erase > open minimal adb/fastboot and type adb sideload whateveryounamedyoursupersuzipfile.zip and you should be good to go.
Shockey0710 said:
Yes that is probably one of its biggest changes vs MM.
Follow this guide to a T: https://forum.xda-developers.com/lg-g-pad-83/development/nougat-7-0-v521-guide-to-update-v521-lg-t3533338
then boot into recovery, copy my TWRP backup to internal/microsd/usb, in TWRP restore the system and boot partitions that are automatically checked.
Download the latest systemless or system mode supersu.zip and copy it to the main install folder C:\Program Files x86\Minimal ADB and Fastboot\.
Then in twrp click ADB sideload > do not check anything to erase > open minimal adb/fastboot and type adb sideload whateveryounamedyoursupersuzipfile.zip and you should be good to go.
Click to expand...
Click to collapse
how did u get 20i ? and got it into permissive mode to obtain root ? know anything about 20h/i changelog ?
abced123 said:
how did u get 20i ? and got it into permissive mode to obtain root ? know anything about 20h/i changelog ?
Click to expand...
Click to collapse
i havent found a changelog nor have i looked though but new kernel version and various security fixes tho, and yes its getenforce permissive. from tmobile fota.
Can I use this in LG-V500???
Since TWRP is still not ported to V10, so i decided to make a prerooted-boot.img.
Download Link
You can flash this boot.img to root your Honor V10 AL20C00 (6GB+128GB China Edition) on stock firmware (B132)
Usage:
0. Unlock bootloader and close find my phone.
1. Power off your phone
2. Plug your phone to computer
3. Hold power and volume down until boot into fastboot mode
4. flash this boot.img by adb ( fastboot flash ramdisk boot-root-b122.img), please download adb by yourself
5. reboot (fastboot reboot)
Your phone may reboot twice, and you'll get root access.
Declaim:
I only test this on my own phone (BKL-AL20C00), Use this on your own risk. I'm not responsible for your phone's damage.
using this tool means you accept this.
Thanks:
HRT-Lin
@mankindtw for his Mate-10 root boot.img
cofface for his bootimg.exe to unpack and repack boot.img
@worstenbrood for his Huawei Update Extractor
Does this root work on stock BKL-AL20 8.0.0.132 update?
Same question. I got BKL-L09 8.0.0.120
No bootloader unlock needed? And i also hope, someone can confirm this on BKL-09 - 120 .
They didn't lock bootloader? Already preorder international unit
Hi,
Can you be a little more specific? Did you unlock your Bootloader first? When you say stock firmware B132, do you mean version 8.0.0.132 ? Thank you in advance for your reply!
Custom Recovery for V10
Hi ppl. Has a custom recovery been ported for the V10. I have managed to root my phone using the above method, but since there is no custom recovery available, I am unable to flash any mod / roms, etc.
I'm hesitant to try this without more information
harshshah17 said:
Hi ppl. Has a custom recovery been ported for the V10. I have managed to root my phone using the above method, but since there is no custom recovery available, I am unable to flash any mod / roms, etc.
Click to expand...
Click to collapse
Hi harshshah17,
Did you unlock your bootloader first? I think there are methods to flash zip files without having a custom REC. Try Flashfire apk. I've read the phone can get even more "restricted" (many features get blocked) once you root your Honor V10. Is it true in your case? Thanks in advance for your reply.
piphol said:
Hi harshshah17,
Did you unlock your bootloader first? I think there are methods to flash zip files without having a custom REC. Try Flashfire apk. I've read the phone can get even more "restricted" (many features get blocked) once you root your Honor V10. Is it true in your case? Thanks in advance for your reply.
Click to expand...
Click to collapse
Ofcourse i have unlocked my bootloader..Its only after that, that you can root. With regard to your question, I have not experienced any sort of "restriction" with my Honor View 10 post rooting. Seems to be working just as normal. The only thing is that i am unable to install the OTA update.
The reason I am asking for a custom recovery is because i need to remove Super SU and install Magisk instead. In order to remove super SU i need to flash an uninstall zip (I know you a can remove it from the Super SU options, but that doesn't seem to be working). I can certainly use flashfire to flash the uninstall zip but then my phone will be unrooted and I wont be able to flash magisk via flashfire.
If anyone has a solution for the above, suggestions will be appreciated. Thanks!
harshshah17 said:
Ofcourse i have unlocked my bootloader..Its only after that, that you can root. With regard to your question, I have not experienced any sort of "restriction" with my Honor View 10 post rooting. Seems to be working just as normal. The only thing is that i am unable to install the OTA update.
The reason I am asking for a custom recovery is because i need to remove Super SU and install Magisk instead. In order to remove super SU i need to flash an uninstall zip (I know you a can remove it from the Super SU options, but that doesn't seem to be working). I can certainly use flashfire to flash the uninstall zip but then my phone will be unrooted and I wont be able to flash magisk via flashfire.
If anyone has a solution for the above, suggestions will be appreciated. Thanks!
Click to expand...
Click to collapse
U can remove root by flashing the stock ramdisk.img, which can be extracted from the official full-ota update.app
Only thing I've seen that doesn't work with root is face unlock. Also how can I flash magisk since there isn't a recovery yet. Can I use flashify?
Yut kill
dawnc said:
U can remove root by flashing the stock ramdisk.img, which can be extracted from the official full-ota update.app
Click to expand...
Click to collapse
Where can you find the full OTA?
whymista said:
Where can you find the full OTA?
Click to expand...
Click to collapse
Download Firmware Finder for Huawei in Play store. They got partial and full OTAs there.
By the way, flashing custom ROMs for V10 is now also thru Fastboot. So I guess TWRP isn't applicable for V10? Maybe Magisk can also be flashed using Fastboot. I will try to research for custom ROM with Magisk. So far, I only see SuperSU pre-installed. ?
piphol said:
Download Firmware Finder for Huawei in Play store. They got partial and full OTAs there.
By the way, flashing custom ROMs for V10 is now also thru Fastboot. So I guess TWRP isn't applicable for V10? Maybe Magisk can also be flashed using Fastboot. I will try to research for custom ROM with Magisk. So far, I only see SuperSU pre-installed. [emoji25]
Click to expand...
Click to collapse
I did download that and the extractor tool but it says I need the update.app file to extract the boot image an I've yet to find that in either of the three files I tried.
So I know how to use fastboot but will I need the boot image first or can I just flash magisk. The current root method installs su. That's where I'm kind of stuck as far because I've always read that you have to uninstall su first but then wouldn't I lose the ability to flash magisk? I'm currently just rooted on the stock rom.
Didn't even know there was a custom rom hadn't seen it on here yet.
Yut kill
whymista said:
I did download that and the extractor tool but it says I need the update.app file to extract the boot image an I've yet to find that in either of the three files I tried.
So I know how to use fastboot but will I need the boot image first or can I just flash magisk. The current root method installs su. That's where I'm kind of stuck as far because I've always read that you have to uninstall su first but then wouldn't I lose the ability to flash magisk? I'm currently just rooted on the stock rom.
Didn't even know there was a custom rom hadn't seen it on here yet.
Yut kill
Click to expand...
Click to collapse
Do you have BKL-AL20? Here's a non-rooted boot image. I'm not sure if it can be used on other variants / versions. If you have another variant, I can find it for you.
BOOT_BKL-AL20_B132
https://mega.nz/#!Ps4jjIqJ!ssiYej9BAu6kZJZ8RfC8P1JDoyo9Ox36o42i8SMm1Lw
Credits to the custom ROM developer KangVIP for the boot image.
piphol said:
Do you have BKL-AL20? Here's a non-rooted boot image. I'm not sure if it can be used on other variants / versions. If you have another variant, I can find it for you.
BOOT_BKL-AL20_B132
https://mega.nz/#!Ps4jjIqJ!ssiYej9BAu6kZJZ8RfC8P1JDoyo9Ox36o42i8SMm1Lw
Credits to the custom ROM developer KangVIP for the boot image.
Click to expand...
Click to collapse
I have the bkl-l09. I'd appreciate it if you could. I'll try this version since it can't hurt though.
Sent from my ONEPLUS A5000 using Tapatalk
So I tried to flash it through adb and it didn't work this is what I got.
PS C:\> fastboot flash boot C:\Users\charl\OneDrive\BOOT_BKL-AL20_B132\BOOT.img
target reported max download size of 471859200 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.362s]
writing 'boot'...
FAILED (remote: partition length get error)
finished. total time: 0.385s
PS C:\> fastboot flash boot C:\Users\charl\OneDrive\BOOT_BKL-AL20_B132\BOOT.img
target reported max download size of 471859200 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.362s]
writing 'boot'...
FAILED (remote: partition length get error)
finished. total time: 0.385s
---------- Post added at 03:45 PM ---------- Previous post was at 03:40 PM ----------
I'm trying to use the recovery tool they have that says I need 5 different files but I've no idea where to find them like the system img etc.
Sent from my ONEPLUS A5000 using Tapatalk
This is what it's saying I need to unbrick
{
"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"
}
Sent from my ONEPLUS A5000 using Tapatalk
whymista said:
This is what it's saying I need to unbrick View attachment 4405892
Sent from my ONEPLUS A5000 using Tapatalk
Click to expand...
Click to collapse
It should be "fastboot flash ramdisk <boot image name>".
Second, if it doesn't help, the next step is to enter e-recovery mode. Press Volume Up + Power for 15 seconds. Follow the prompts and it should download the full OTA for you. I think you need your Huawei ID in the process (and a good Wifi signal).
Lastly, I think this is a sure bet but will cost you, google "funkyhuawei honor v10 rebranding guide". You will find a reddit link. They are the only team who "holds" BKL-L09 Full OTA roms that I know of. You need to buy "credits" to download OTAs and unbrick your phone. Unfortunately, team MT (team behind Firmware Finder) hasn't got a hold of a full OTA of BKL-L09.
From my experience, the first suggested solution should already work. I hope you don't get to the third solution.
Hey guys,
I've been installing customs without issue on my RN10.
Then one stopped booting freezing on the logo and bootloops.
Reinstalled stock with miflash and Redmi bootloops.
Tried customs again and same thing.
Any suggestions or things to try?
Worried the system_root and vendor errors are my problem.
Thanks in advance for any help or tips.
Cheers.
{
"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"
}
GEoMaNTiK said:
View attachment 5541321
Click to expand...
Click to collapse
Try flashing the super image through recovery.
faced this problem the solution for me was to flash fastboot miui eu rom
SubwayChamp said:
Try flashing the super image through recovery.
Click to expand...
Click to collapse
Tried this and didn't help, thanks for the suggestion
muneeb rizwan said:
faced this problem the solution for me was to flash fastboot miui eu rom
Click to expand...
Click to collapse
Hey there, I've tried flashing via Mi Flash and although it says success, still bootloops on Redmi logo, then eventually to fastboot.
Do you remember which fastboot miui EU rom or have a link ?
I'll try anything at this stage.. think I've killed my first Xiaomi phone.
GEoMaNTiK said:
Tried this and didn't help, thanks for the suggestion
Click to expand...
Click to collapse
Also, you can fix it flashing this ROM xiaomi.eu_multi_HMNote10_V13.0.5.0.SKGMIXM_v13-12-fastboot
SubwayChamp said:
Also, you can fix it flashing this ROM xiaomi.eu_multi_HMNote10_V13.0.5.0.SKGMIXM_v13-12-fastboot
Click to expand...
Click to collapse
Thanks for this, just tried, used the windows_fastboot_first_install_with_data_format.bat and all installed with an OKAY.
No failures or errors during install. Phone bootloops on Redmi and comes back to Mi Recovery screen.
Is there a way with OrangeFox, TWRP and any other tool to fix the file system or help?
Thanks in advance.
GEoMaNTiK said:
Thanks for this, just tried, used the windows_fastboot_first_install_with_data_format.bat and all installed with an OKAY.
No failures or errors during install. Phone bootloops on Redmi and comes back to Mi Recovery screen.
Is there a way with OrangeFox, TWRP and any other tool to fix the file system or help?
Thanks in advance.
Click to expand...
Click to collapse
same with me..but i reset data in recovery ..phone booting normal back
Now I'm getting a failed to mount (block device required) but still not able to get a custom to boot. When I try to reboot, I'm getting a system partition is empty.
Next question I have, do I have to force encryption in Orangefox or turn it off?
Also DM-Verity, should both options be off or on for customs?
GEoMaNTiK said:
Now I'm getting a failed to mount (block device required) but still not able to get a custom to boot. When I try to reboot, I'm getting a system partition is empty.
Next question I have, do I have to force encryption in Orangefox or turn it off?
Also DM-Verity, should both options be off or on for customs?
Click to expand...
Click to collapse
bro im facing the same problem you have... im using rn10sunny twrp will not mount system, and didnt flash custom roms... and if i flash stock rom then it will goes to bootloop... im also in the same condition now.....
can you please contact me on telegram @KAVIKING007 for discuss about the problem.. it will help both we are getting solutions....
GEoMaNTiK said:
Thanks for this, just tried, used the windows_fastboot_first_install_with_data_format.bat and all installed with an OKAY.
No failures or errors during install. Phone bootloops on Redmi and comes back to Mi Recovery screen.
Is there a way with OrangeFox, TWRP and any other tool to fix the file system or help?
Thanks in advance.
Click to expand...
Click to collapse
I assume you are formatting data, no? The long procedure for me was, installing AEX, I couldn't install it with TWRP (in this state), used OFR, boot to the recovery that AEX provides, format data, then boot to system, check that all is ok, enable USB debugging, now go to fastboot and flash the Miui 13.
In other device was fixed just flashing the super image (from the stock ROM) onto the super partition.
Keep the OFR settings as they are.
My theory is that some custom ROMs break the sizes on the super partition and some images are not matching.
Can you please explain about OFR because i couldn't used before....
KAVIYARASU KING said:
Can you please explain about OFR because i couldn't used before....
Click to expand...
Click to collapse
OFR Orange Fox recovery, is available in the forum.
SubwayChamp said:
OFR Orange Fox recovery, is available in the forum.
Click to expand...
Click to collapse
I tried in orangefox also but same problem occurs..... that was system could not mount.... On twrp,OFR the system partition could not be mounted... I tried all the way... But no result
KAVIYARASU KING said:
I tried in orangefox also but same problem occurs..... that was system could not mount.... On twrp,OFR the system partition could not be mounted... I tried all the way... But no result
Click to expand...
Click to collapse
Try, as pointed out in previous posts, format data with AEX recovery, then flash Miui.eu 13 through fastboot.
Also you can try flashing the super image (from the stock ROM through OFR).
And, finally, you can try using Mi Flash tool BUT in EDL mode.
All of these, assuming that you are permanently flashing the custom recovery, not only booting to it.
GEoMaNTiK said:
Thanks for this, just tried, used the windows_fastboot_first_install_with_data_format.bat and all installed with an OKAY.
No failures or errors during install. Phone bootloops on Redmi and comes back to Mi Recovery screen.
Is there a way with OrangeFox, TWRP and any other tool to fix the file system or help?
Thanks in advance.
Click to expand...
Click to collapse
You did not use the correct *.bat file for a complete cleanup. The *.bat you used will leave the original data on your phone even if it is not compatible. If you have a problem and want to install a new clean Miui system, use the flash_all.bat file (in MiFlash this is the "clean all" option)
StaryMuz said:
You did not use the correct *.bat file for a complete cleanup. The *.bat you used will leave the original data on your phone even if it is not compatible. If you have a problem and want to install a new clean Miui system, use the flash_all.bat file (in MiFlash this is the "clean all" option)
Click to expand...
Click to collapse
I had already tried MiFlash before that other rom and it's .bat file.
Just tried this with MiFlash - mojito_global_images_V12.5.2.0.RKGMIXM_20210731.0000.00_11.0_global_ce90f80766.tgz
I selected flash_all.bat. Received a success on completion of flash, used this MiFlash2018-5-28-0 (as I was receiving errors on the new MiFlash versions).
And still my phone bootloops on Redmi. This almost confirms to me this phone is lost now, nothing else I can think of.
However, will wait to see if any other suggestions here.
Thanks everyone for trying to help, much appreciated.
Don't worry yesterday night i get a new solution for these problem..... Almost we will get our device soon..... Today im gonna test few steps and its work i will give the solution dude.... So don't worry....