My Xperia Z2 LTE Tablet is fully unrooted with the TA.img successfully created and backed up with all user and system apps backed up with Titanium Backup. The tablet is Verizon branded and would like to flash an unbranded TFT, but had a few questions before I proceed just to make sure I don't do anything wrong.
1.) Is a Titanium Backup of apps enough, or is there some other type of backup I should be making?
2.) If I use this image, which is for SGP521, will it work with my SGP561?
https://docs.google.com/file/d/0B4o8Tp4omHzWazhDUGxEYjJwUTQ/edit
3.) Will my DRM keys remain intact if I flash it with this method:
http://www.xperiablog.net/2014/06/01/debrand-your-xperia-z2-tutorial/
Or, alternatively, will I have to unlock the boot loader first and then restore the DRM keys after?
4.) Will there be any problems with using the DRM keys on a different TFT image, or are they only tied to the physical hardware?
5.) What would happen if I performed a factory reset after flashing a new TFT image?
6.) If I restore my apps after flashing can Titanium Backup use a Snapshot image and change the ID of the device to match the apps without any problems, are are there some limitations?
7.) Is there anything else I should read or do before I proceed?
Thanks.
EDIT: So according to Sony, some Z2 tablets cannot be unlocked. I followed the steps to find out and it says unlocking the bootloder is not allowed. If an unlocked bootloader is required to unbrand my tablet is there an unofficial way to do 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"
}
http://postimg.org/image/oq5ssivqp/
EDIT 2: And it looks like I can't use the Sony PC Companion
"Sorry, it's not possible to update your device using Sony PC Companion.
Please use the Verizon Upgrade Assistant tool"
And the Verizon Upgrade Assistant tool doesn't recognize it!
Ugh.
Related
Hi,
I own an Acer B3-20 tablet with stock firmware, rooted via kingroot and unkingrooted with supersu me pro.
An OTA update came today for my tablet and I did proceed not thinking about the root thing.
The update failed with the file
Code:
/usr/bin/debugd64
found not equal to the one expected. I assume it is the rooting process that changed that file.
No damage was done when I rebooted. All was there.
So I said to me. I am gonna reflash (OS_Acer_AV0L0.B3-A20.RV03RC06.WW.GEN1_A51L_A.zip) the stock firmware from SD Card to get rid of root but when I got into recovery mode (power+ vol up) I discovered that menu in chinese instead of stock recovery. OMG!
{
"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"
}
Edit: looks a lot like this
I tried again the update after deactivating super su. (unrooting ?). It failed to do the update again but drop me it what seems to be exactly the stock recovery. So I used it to reflash the original firmware provided by Acer for the tablet. hence unrooting completly. and proceed to make the update again which worked this time. :silly:
Did you get the new chinese recovery after the update ? my build is now: Acer_AVOLO_B3-20_RV07RC01_WW_GEN1
How did I get the original stock recovery given I have already reflashed the original firmware and did not get it back (but I applied the OTA update on top of it) ?
What does every line of it mean ? Can somebody translate this menu, please ? the last one is reboot . It's all I manage to get
first highlited line seems some low level stuff and all this does not seem to be the recovery in chinese.
Thanks
Thread closed at request of OP.
Respect All XDA Developers,
I'm mizan from Bangladesh, i have a problem with my Huawei GR5 mini Device with the Bootloader.
The problem cause........ I am unlock my device bootloader, twrp recovery & root my device, few month letter i need to relock the bootloader, also remove the supersu. that's why i go to the supersu apk and full unroot my phone, then i flash the stock recovery (unfortunately it's may not flashed i don't know). then i go to the bootloader mode & type a command to relock the bootloader then the problem happened.
Please help!!
I have a full partitions backups made with Partitions Backup and Restore App (Root access required). I backup all the partitions, all of them in raw mode. All the files are *.img ready to flash with fastboot.
The problem
1. adb is not recognizing the device
2. fastboot is not recognizing the device
3. I cannot enter TWRP
4. Huawei EMUI 3 buttons (volume up + volume down + on/off button) function doesn't start neither (I'm trying to force the update to B132 ROM)
5. The phone enters directly to Rescue Mode and says
{
"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"
}
6. i can't shutdown my phone when i press the power button it will automatically go to the Rescue Mode again.
So the phone is still working and I got this RESCUE MODE screen but I can't do anything when this screen is displayed.
Any idea? What can I try?
Please, I really need your help, anything you can imagine to try please, let me know!!!
Thanks in advance!!!
Same Problem
Same problem happened to my GR5 mini also. What to do?
Hello!
I encountered a problem with tv box X96 Max 4/32. I bought a tv box in July in a store VONTAR. The tv box came in a new revision, all old firmwares are not install and not work on it . If the firmware passes the installation, the TV box turns into a brick, and you need to close the contacts to flash another firmware. My tv box works on only one stock firmware X96Max_V311_20190625, but Bluetooth doesn't work on it.
On new revisions tv box have firmware X96Max_V31R_20190716_2201, can anyone get it for flash via UBT (img format).
{
"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"
}
Please link firmware X96Max_V31R_20190716_2201
no longer needed. made without backup firmware for this revision
hi all, think i've same model
can't do anthing with it
burning tool not work and twrp recovery not working too
really bad i've removed my root with mmagisk installation
if i can have help i've original recovery if it needed thx all
z300muser said:
hi all, think i've same model
can't do anthing with it
burning tool not work and twrp recovery not working too
really bad i've removed my root with mmagisk installation
if i can have help i've original recovery if it needed thx all
Click to expand...
Click to collapse
i've found a valid twrp here
if i can have help for recover my root please i think it's possible if i replace the file in system
but i've "su" and "daemonsu" extracted maybe i need too put their in system/xbin but no work's i was tried
twrp have make me a valid backup of system i can restore it but i was made it after try magisk installer
I can not find a way to avoid errors in the flash process or wipe process, I attach some of the different errors that I get, the last image is the last error.
{
"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"
}
a bit of context and history of the things I did:
This is an Honor 8 FRD-AL00 from China, in 2017 I unlocked the bootloader, I rebrand the phone into its Europe version FRD-AL09, then I updated to Emu5, then in my first vacation on Europe (I am from Argentina), the phone ask me for an update. As I knew that I used an Europe ROM, full rebrand, I did not saw nothing nothing wrong with that (if I wanted an update on Argentina, I have to forced), so I accept the official update there.
Results: I bricked.
I buy a new phone there, I kinda forget over some years, now I want to fix it, but seem that it is quite hard.
First I had problems installing TWRP, the only way was using the Multi-Tool8 from @teammT flashing the TWRP 3.1.1 as Erecovery.
I tried to do flash a ROM from a similar year than my last correct update, fail using commands, fail using the tool, fail using an extra SD on dload, fail using TWRP.
I tried the same thing with the stock firmware for FRD-AL09 (the multi-tool8 always recognize the phone as FRD-AL09, until I made a full wipe with TWRP of cust, system, vendor, etc).
I tried to format system or other partitions as FAT and Ext4, but nothing happen.
The errors continue when I try to flash the ROM.
I even had a backup made with TWRP when the phone was working fine, I tried to restore that backup with TWRP and I receive error.
What can I do to save the phone?
Hello everyone, a week ago I received my Mi 11 Lite 5G and the first thing I did was unlock the bootloader. Today I managed to unlock it and tried to install a custom ROM (xiaomi.eu). However, I had a problem that made the operation impossible. I forgot to activate the option "install via USB" thinking that this one was not important, obviously I underestimated it. My question is: do you have any solution to reinstall the basic ROM (there isn't system currently), or activate this option other than in the phone (in fastboot with adb for example...), regardless of the method, I hope there is at least one.
Awaiting a positive response (I hope), greetings and I wish you all a merry Christmas.
This option doesn't really matter, if your bootloader is unlocked (as in there is a undone lock icon every boot above the Mi logo) just go into fastboot by shutting the phone off forcefully, then holding down Power + Volume Down until you see the Fastboot Screen as shown below
{
"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"
}
Then after that, check device manager in Windows to see if your device is being seen as "Android Bootloader Interface", if it is. Then you're good to go! Download the latest Xiaomi.eu ROM for Renoir then unzip it, then run the batch script for your case. You will lose all of the data on your phone's internal storage when installing though. So beware and be sure to make backups!