Hi all,
I bought an old Oneplus 3 which have been flashed Experience ROM (https://forum.xda-developers.com/oneplus-3/development/rom-experience-rom-v1-0-t3522259). Now I want to remove it completely.
I can enter fastboot then run command to boot recovery (http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img) then adb sideload to flash (http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_4.0.2/).
Stock ROM works well but the boot screen still is Experience ROM.
{
"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"
}
I think that causes some problems with my later development.
Please help me to find out which partition of flash may not reset to original, or is there any way to flash completely as stock production?
Thanks all.
I think you need to just flash the original boot logo.
Wipe System, Data, cache and sideload stock from then you will be full stock for sure!
https://forum.xda-developers.com/oneplus-3/themes/mod-custom-boot-logo-pack-op3-t3525143
You can try one of these... They are way too good or you can flash the original one given in the OP.
Hope it helps... Thanks!
I wonder if there is any way to flash all flash of Oneplus 3 as stock. That mean flash all recovery, boot, system ...
Puddi_Puddin said:
Wipe System, Data, cache and sideload stock from then you will be full stock for sure!
Click to expand...
Click to collapse
This does not work. I've tried it before. Complete stock sideload, both OB11 and stable.
FYI: Jamal has removed the bootlogo on his latest releases
Shresth45 said:
This does not work. I've tried it before. Complete stock sideload, both OB11 and stable.
FYI: Jamal has removed the bootlogo on his latest releases
Click to expand...
Click to collapse
Boot logo and animation is stored on the System partition. By wiping it and overwriting it by flashing stock rom it should dissepear.
200791 said:
I wonder if there is any way to flash all flash of Oneplus 3 as stock. That mean flash all recovery, boot, system ...
Click to expand...
Click to collapse
There is a tool that's used to unbrick the op3, this tool flashes every partition to full stock again.
You need to look at the mega unbrick thread and use the full unbrick tool that wipes everything.
Related
Hi
When i boot my P6, on the bootscreen there are 3 wierd pixels iluminated. Look at phone screen on bottom right corner:
{
"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"
}
They apeared when i had stock rom (B606)
i only did root using eRoot Tool
i had instaled busybox because an app to hide softkeys required busybox to be instaled, but i didnt changed anything in busybox (unless some app did)
How can i fix that? when i brought this phone one month ago they were not there.
Someone sugested i could flash boot.img??? is that image part of boot.img? is that right? i dant want to brick my phone.
Now i'm on firmware B506 with recovery TWRP 2.6.3.7, all is working fine but i just want to get rid of that pixels.
Help would be apreciated! Thanks in advance!
Remove SD card. Boot in to recovery with 3 buttons push, in recovery do a wipe data and phone will start normaly.
alex.79 said:
Remove SD card. Boot in to recovery with 3 buttons push, in recovery do a wipe data and phone will start normaly.
Click to expand...
Click to collapse
I've flashed yesterday trough TWRP 2.6.3.7 the newest B506 stock rom and i did a full wipe except external storage. the pixels stills there
No wipe data will fix that. Your screen is the problem.
ZuperStyler said:
No wipe data will fix that. Your screen is the problem.
Click to expand...
Click to collapse
But that bug is only in bootscreen. It's not bad pixels. Don't u think its possible to be a bug in ASCEND P6 logo image? Can i flash boot.img to see if it fixes? If i flash boot.img will i lose my recovery or rom?
No, you will not lose anything, you can flash the boot animation, maybe it will fix the problem.
ZuperStyler said:
No, you will not lose anything, you can flash the boot animation, maybe it will fix the problem.
Click to expand...
Click to collapse
do i have to flash a specific boot.img or there are ony one comom file to all P6 devices? Is boot.img the kernel?
im running stock B506-CN rom(latest oficial kitkat firmware), with TWRP 2.6.3.7
http://forum.xda-developers.com/showthread.php?t=2733523
I'm stuck on the last part when installing a new ROM, everytime I install it gives me an error saying FAILED. Any help?
I'm able to adb sideload but I still can't flash any ROMs.
ThePwnie said:
I'm able to adb sideload but I still can't flash any ROMs.
Click to expand...
Click to collapse
can you post a screenshot of the error you're getting
wtfsykhang said:
can you post a screenshot of the error you're getting
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"
}
ThePwnie said:
View attachment 2841440
Click to expand...
Click to collapse
might be a bad zip. have you tried re-downloading the rom and flashing?
What you have to do (which the guide doesn't cover IMO)
1. After flashing the 1.54.401.5 FW, you then have to boot into the stock recovery and do a factory reset to re-align the partitions
2. Then flash TWRP and once in TWRP, do a full factory reset of all partitions
3. Then use adb push to push the Sense ROM to the phone (adb push rom.zip /sdcard)
4. Flash the Sense ROM
5. Flash the 1.54.401.10 FW if the ROM is based on that build
6. Reboot
I do that if coming back from the GPe RUU conversion and it works fine
EddyOS said:
What you have to do (which the guide doesn't cover IMO)
1. After flashing the 1.54.401.5 FW, you then have to boot into the stock recovery and do a factory reset to re-align the partitions
2. Then flash TWRP and once in TWRP, do a full factory reset of all partitions
3. Then use adb push to push the Sense ROM to the phone (adb push rom.zip /sdcard)
4. Flash the Sense ROM
5. Flash the 1.54.401.10 FW if the ROM is based on that build
6. Reboot
I do that if coming back from the GPe RUU conversion and it works fine
Click to expand...
Click to collapse
Which steps should I start? I got stuck on step 4, which gave me the error. But I adb sideload Sinless ROM and it worked. However, I still can't flash new ROMs, only adb sideload
I forgot to disable my encryption when I flashed TWRP now im stuck with bootloop on twrp
do we have option to disable encryption or this needs to be hard reset?
confirming hard reset that would be
advanced wipe
tap on
delvik
meta
data
then swipe to wipe right?
that shouldnt remove my stock room or brick my stock room right?
im sorry, im new to this.
Thanks in Advance!
It is not any rule to disable encryption when flash TWRP, so if you did the flash operation right that bootloop is not normal. Can you enter in TWRP? If so, try to delete Delvik only and try to reboot to system. If it returns to TWRP, you may need to do a Format data (yes) in advanced wipe section (this will erase all data from your phone) - reboot to TWRP (not absolute necessary, but I always do it) - reboot system.
Try Clean Flash custom Roms step 16: https://forum.xda-developers.com/t/4288121/post-85137963
{
"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"
}
thank you for your swift response.
unfortunately it reboot back to twrp.
i might need to flash this over with miui.eu 12.5 using fastboot hopefully it get sorted.
i'll wait for your response before doing so though.
Try flash the Rom again. Confirm the Rom is downloaded correctly without interruption.
You shouldn't need to wipe or format other parts before flashing a Rom.
Before boot up, do the step as the picture.
Will do.
I will try to follow this guide: https://xiaomi.eu/community/threads...all-xiaomi-eu-rom-for-xiaomi-redmi-k40.60379/
astigjohn said:
Will do.
I will try to follow this guide: https://xiaomi.eu/community/threads...all-xiaomi-eu-rom-for-xiaomi-redmi-k40.60379/
Click to expand...
Click to collapse
If you are following that, you don't need to do as the picture I posted earlier.
mate, just an update. I was able to successfully installed global.eu room and booted it. i guess we move forward with disabling any password first before flashing TWRP and installing Magisk.
I appreciate you checking on this, man this community is awesome!
I've downloaded the stock fastboot rom, and i wnt to restore the stock recovery, becasue I'm using now the TWRP from here. I want to update to the latest global rom, to the enchanted one, but i dont want to reinstall everything. I only rooted the global rom that I'm using now, and i hope I can install the latest one without data loss, if I use the stock recovery.
Can you tell me wich .img file is the recovery in it? There is no recovery.img in in it. Here's the list of the files I found in the tgz/tar package. Or if it's not here, could someone give me a stock recovery image for the 12.5 global rom? Thank you!
{
"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"
}
There is no recovery partition on poco F3.the recovery is part of the boot partition now.If you flash the stock boot you lose Twrp recovery.
Okay, thank you, it worked!
hexisg said:
There is no recovery partition on poco F3.the recovery is part of the boot partition now.If you flash the stock boot you lose Twrp recovery.
Click to expand...
Click to collapse
hexisg said:
There is no recovery partition on poco F3.the recovery is part of the boot partition now.If you flash the stock boot you lose Twrp recovery.
Click to expand...
Click to collapse
Are you mean if i install any Stock global stable rom , recovery will auto change back from TWRP to stock recovery ??
coolkillermax said:
Are you mean if i install any Stock global stable rom , recovery will auto change back from TWRP to stock recovery ??
Click to expand...
Click to collapse
yes
hexisg said:
yes
Click to expand...
Click to collapse
Thank you
Hi all, I have rooted my pixel 6 pro since day 1 and always used the magisk way of patching and restoring images for updates, since the February update Google tells me updates are no longer supported on my device per screenshots, anyone else had this issue and know how to resolve it?
{
"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"
}
You might want to backup, uninstall magisk in the app, reboot. Then full reset/wipe and reboot. Then manually update to the latest May 2022 version using adb or the android flash tool. Something has gone awry with your software. Better to be safe than sorry.
Just used the android flash tool and flash the latest image without the wipes, then reroot, should fix it all.
Gytole said:
Just used the android flash tool and flash the latest image without the wipes, then reroot, should fix it all.
Click to expand...
Click to collapse
But with my device rooted and my bootloader unlocked won't that throw me into a boot loop? Then I'll have to completely wipe and restore no?
zamarax said:
But with my device rooted and my bootloader unlocked won't that throw me into a boot loop? Then I'll have to completely wipe and restore no?
Click to expand...
Click to collapse
Nope! Quite the opposite if I get stuck in a bootloop I just use the flash tool to fix it. No loss of data, but you need to re-boot the magisk boot image then reflash in magisk afterwards as it will completely remove magisk
So I did what you suggested and now my device is stuck in a boot loop with corrupt data, I did however patch the boot.img previously when I tried to send it to the device via ADB so I'm going to try to push that now and see what happens. Here are the options I selected for Android Flash Tool.
Second attempt with not selecting 'Disable Verity' and 'Disable Verification' worked successfully.
Thank you, I really appreciate it!
zamarax said:
Second attempt with not selecting 'Disable Verity' and 'Disable Verification' worked successfully.
Thank you, I really appreciate it!
View attachment 5608917
Click to expand...
Click to collapse