I started to get this error message after flashing the boot partition. All connections stopped working. I reflashed with original boot partition, which results in wifi working again, but bluetooth is dtill refusing to work. Do I factory reset? I have a file that is important but wont come off because it keeps freezing during transfer process
Search for 'Reset options' and reset wifi/mobile/bluetooth, see if that does the trick.
rocketda7331 said:
Search for 'Reset options' and reset wifi/mobile/bluetooth, see if that does the trick.
Click to expand...
Click to collapse
I've also done that. The phone I tried to root is a Z3551S (came from QLink Wireless, running android 9 and has a ****ton of bloat), which doesn't have ramdisk, or a separate VBMeta partition. Also, the images are from some other source. And when I flashed with the rooted partition, Magisk showed the phone was rooted, and I could view files I couldn't view before, but I couldn't uninstall apps with another root application, so I don't think it was fully rooted. I'm also beginning to think that I may need to flash all of the files, because they might not be the same.
uninstall bluetooth
TwisstedToast said:
uninstall bluetooth
Click to expand...
Click to collapse
Can't do that either. I tried before flashing the before-modified boot image, but I don't think the phone was properly rooted
Here is the message that I get. Clicking `ok` just takes me to settings
{
"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"
}
An update: the wifi DOES NOT turn on, and SDCards are not being mounted either. Ima try flashing the boot.img to boot instead of boot_verified.img to boot
Related
So recently I did a stupid and accidentally switched off my OPO during an update installation and completely screwed it all up. I tried switching it back on only to find that it was stuck in a recovery mode loop. I then hit factory reset in a last ditch attempt to save the poor bugger without flashing it and even that didn't work.
I've then had to resort to flashing it using the OPO toolkit software on my PC however when connecting to the PC, my OPO only shows up as an MTP USB Device and nothing else. I have tried installing recommended Samsung drivers for the phone but I wasn't able to as it the "update drivers" button was greyed out on the MTP USB Device properties window.
{
"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"
}
Basically, the OPO toolkit will not work as no android devices are recognised by the PC even though an android device is showing up in the control panel.
There is no way I can currently access the settings on my phone due to recovery mode loop obviously.
The last thing I want to do here is end up with being forced to use the OnePlus support which I hope most of you understand why.
Thanks for any suggestions!
Hi,
This thread is being moved to your own dedicated forum , where the experts may be able to help you better.
Good luck!
Put it in downloading mode and then use adb to use the toolkit since bow u don't have a os on the OPO happened with me too but I fixed it this way
Sent from my A0001 using Tapatalk
Hi There,
Today I've got my new Oneplus 3T. After I've had a Oneplus One I would like this one to root. So I used this instruction and youtube explanation. (https://www.youtube.com/watch?v=BQOJR5sUto0 and https://forum.xda-developers.com/oneplus-3t/development/toolkit-oneplus-3t-toolkit-unlock-t3507729 )
It worked......., but only
After that I stopped the usb debugging (because of the continuos icon on top of the screen) and I installed the new nogoat update (920 mb) after that my phone rebooted and every time I get the error shown in attached picture decoding failed....).
Help me what to do...
{
"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"
}
Any chance you can re-upload the picture of the error? it doesn't seem to have gone through.
The message in the picture is....
Deoding failed
Tour phone syorage had been damaged. Unable to read data stored on your phone! To continue to use your phone, you need to reset the phone (the entire contents and data of your phone can not be recovered).
I've done this reset but no normale start up....
Lody13 said:
The message in the picture is....
Deoding failed
Tour phone syorage had been damaged. Unable to read data stored on your phone! To continue to use your phone, you need to reset the phone (the entire contents and data of your phone can not be recovered).
I've done this reset but no normale start up....
Click to expand...
Click to collapse
After root, normal OTA doesn't work. So if you want to update download the entire ROM and update from it.
Follow this guide and start over again. You'll lose your data on the device storage, but its better than a bricked one.
https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.475142/
Follow that guide step by step, you should be good to go.
Hi all,
So, I was running fine with CROMi-X KitKat, but wanted to upgrade to Marshmallow (to install sw not supported in KitKat), so decided to try KatKiss 6.0. It's been years since I've played with flashing ROMs, but I did a little reading to refresh my memory. Then I rebooted into recovery (ClockworkMod), backed everything up, then wiped everything, formatted /data, and tried flashing the KatKiss zip file. At that point, it just sat there forever at the ASUS logo screen:
{
"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've tried several times to boot back into recovery by holding the Vol+ and Power buttons, but it either doesn't boot, or boots to the above screen. I've connected it to my Mac w/ the Android SDK Platform Tools, but adb doesn't see any device listed. [I've got an old Windows laptop (XP?)] I could use if it will do something the Mac can't.]
Any advice on how I can save this tablet?
Have you found a solution finally?
Well, I haven't found a solution, but after letting it sit unplugged for months, I came across it today as I was straightening up. I plugged it in, waited maybe half an hour, and was able to boot it into recovery mode. I was then able to restore from a backup, and damned if it didn't reboot and come up just fine. No idea why it wouldn't boot into recovery before, but I'm happy camper!
Hello all,
Lately I wanted to install rom on my moto x4 and altough I'm a bit noob in the process I was confident I could do it properly (did it in the past with a oneplus one and a sony erickson x10mini )
So I've unlocked my my bootloader and I was ready to boot twrp image with adb to finally be able to install twrp and magisk.
but there is the problem,
normally I should see this
{
"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"
}
But instead I see this
Honestly I look what was the issue here but my skills as a rom installer are not that great so I got stuck there.
Of course I can still use my phone without any issue but I have no idea on how I can install twrp magisk and later on a rom.
Does anybody have an idea what is the issue here ?
Thank you
Seems like your TWRP version was not able to decrypt data partition.
Boot to system and disable encryption for your phone (Lock screen -> none). Boot to recovery again afterwards. Try flashing your zips.
wkn000 said:
Seems like your TWRP version was not able to decrypt data partition.
Boot to system and disable encryption for your phone (Lock screen -> none). Boot to recovery again afterwards. Try flashing your zips.
Click to expand...
Click to collapse
lol honestly didn't think about that, thanks a lot :highfive:
I am attempting to root a Acer Iconia B3-A40 (yuck, I know.. but my wife loves it...)
Was following the 'how to' guide here.
1. Installed Magisk
{
"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"
}
,
2. Successfully ID'd type of boot image
(downloaded clean copy from acer.com 0
Click to expand...
Click to collapse
3 verified image ( and found boot.img) and copied it
Step 3: Patching the boot image
And HERE' S the first problem/question:
NEXT it tells us to install
First part, fine second part not so fine. See pic:
Q1: Presuming it DIDN't work? so why did it write a file, and accept everything?
OK I SHOULD have stopped here///
But I didn't.
It did show a file at the location, I continued, tried to boot to recovery, and tablet hung. (was hanged?)
I did get tablet back up, and when it booted, the memory card was corrupted.
Hope this is a good start for someone else.
Ideas? troubleshooting tips?
thanks in advance!!!
If you save the installation log after patching the boot image and then post it here it might show more about what's going on.
Didgeridoohan said:
If you save the installation log after patching the boot image and then post it here it might show more about what's going on.
Click to expand...
Click to collapse
Is there a chance it still exists, after 2 reboots?
markbnj said:
Is there a chance it still exists, after 2 reboots?
Click to expand...
Click to collapse
No. It has to be saved before you leave the flashing window (your screenshot #3). But you can just patch the same file again and save the log without doing anything else.