Things needed:1. An Xperia 1 iii (of corse)
2. A Windows PC (I don't know if there's a Mac or Linux version, but I didn't find it)
3. A reliable USB-C cable
4. NewFlasher
Download: [TOOL] Newflasher (xperia command line flasher)
5. XperiFirm
Download: Tool Archives - XperiFirm Tool
!!!FIRST THING FIRST!!! BACKUP EVERYTHING IMPORTANT
FLASHING A PHONE MAY CAUSE DATA LOSS. PLEASE MAKE SURE YOU HAVE A BACKUP OF YOUR DATA.
1. Download and unzip the XperiFirm and select the ROM you want in the Available Firmware list and download.
{
"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. Once downloaded, unzip the NewFlasher into the ROM folder.
Your folder should look like this:
3. Start a command line in the ROM folder and run "newflasher set_active:a" otherwise your phone will boot into a bootloop.
4. Power off your phone and plug it into your PC. Hold the volume down button and the power button until the LED turns GREEN.
5. Now you can double click on the newflasher.exe in your ROM folder and follow the guide. You can keep user data while flashing, just pay attention on the instructions on the Newflasher.
6. Don't disturb the flasher while it is working. Your phone will automatically turn on after the flashing is completed.
My Xperia was purchased in China (XQ-BC72). I have tried many ROMs like Hong Kong and Taiwan versions. Recently I flashed my phone with the XQ-BC62 ROM and everything works very well (mobile data, voice calling, data roaming, dual SIM, exposure alert, etc.). However, I haven't try VoLTE because my carrier doesn't support it (SO SAD).
I'm in Canada and my carrier is CMLink. The data icon for LTE shows 4G if you're curious.
The DRM is not damaged that the Windvine security level is still L1 so you can still enjoy the HDR content on Netflix after flashing using this method.
UPDATE Sept. 28, 2021I flashed my XQ-BC72 back. I have several issues while using the XQ-BC62 ROM.
The US ROM doesn't include my carrier's configuration so VoLTE, VoWiFi, showing LTE instead of 4G is not working. According to other threads, T-Mobile doesn't have the configuration as well and someone mentioned only Google Fi users can get a configuration (NOT SURE).
Actually, I didn't find any difference between the XQ-BC62 and the XQ-BC72 ROMs (I'm in Canada).
Although the phone is working fine, the LTE is auto-disconnecting every 30 seconds, while HSPA+ doesn't have this issue. I don't think it's my carrier's problem because I bought a new Fido sim card and it's still disconnecting until I flash it back. So if your LTE works fine, please share your solution down below if you don't mind.
I have heard that the new update 61.0.a.11.92 is enhancing the network performance. I don't know if it's because I didn't update my phone. I don't wanna "play" with my ROM since this is my daily using phone.
Thanks to DennisDD78 who discovered that the OTA is not available if a non-native ROM is flashed, even it's all XQ-BC72. Still, if you make your OTA work, please share your solution!
UPDATE Nov. 26, 2021I didn’t update the post due to the heavy university work (so sad).
You can keep your data during flashing now by simply choose an option while flashing, as the Newflasher is up-to-date. But still please backup your important data before flashing.
I can confirm that Gpay and android wear work perfectly after flashing, even a cross-model flashing.
Flashing a different rom doesn’t bring any carrier feature like VoLTE and VoWiFi, see this post.
I also tried XQ-BC62 roms again and also XQ-BC52 roms. Same issue, LTE disconnects every 10 seconds, and it brought no new features at all. I haven’t tried those Japanese roms. If you have any experience, please share.
Hmm, I'm debating on getting the XQ-BC72 model and crossflashing to the US but only if it come swith a warranty
Does anybody know what might be causing the flash to stop about a quarter way through? I followed the steps outlined above but still doesn't work. Still stuck on the device can't be trusted, five second power down logo.
It worked the first time, but now it’s not completing anymore.
Forbesii said:
Things needed:1. An Xperia 1 iii (of corse)
2. A Windows PC (I don't know if there's a Mac or Linux version, but I didn't find it)
3. A reliable USB-C cable
4. NewFlasher
Download: [TOOL] Newflasher (xperia command line flasher)
5. XperiFirm
Download: Tool Archives - XperiFirm Tool
!!!FIRST THING FIRST!!! BACKUP EVERYTHING IMPORTANT
FLASHING A PHONE WILL CAUSE DATA LOSS. PLEASE MAKE SURE YOU HAVE A BACKUP OF YOUR DATA.
1. Download and unzip the XperiFirm and select the ROM you want in the Available Firmware list and download.
View attachment 5396817View attachment 5396819
2. Once downloaded, unzip the NewFlasher into the ROM folder.
Your folder should look like this:
View attachment 5396821
3. Start a command line in the ROM folder and run "newflasher set_active:a" otherwise your phone will boot into a bootloop.
View attachment 5396823
4. Power off your phone and plug it into your PC. Hold the volume down button and the power button until the LED turns GREEN.
5. Now you can double click on the newflasher.exe in your ROM folder and follow the guide.
6. Don't disturb the flasher while it is working. Your phone will automatically turn on after the flashing is completed.
My Xperia was purchased in China (XQ-BC72). I have tried many ROMs like Hong Kong and Taiwan versions. Recently I flashed my phone with the XQ-BC62 ROM and everything works very well (mobile data, voice calling, data roaming, dual SIM, exposure alert, etc.). However, I haven't try VoLTE because my carrier doesn't support it (SO SAD).
I'm in Canada and my carrier is CMLink. The data icon for LTE shows 4G if you're curious.
The DRM is not damaged that the Windvine security level is still L1 so you can still enjoy the HDR content on Netflix after flashing using this method.
Click to expand...
Click to collapse
Could you please tell me the difference between the XQ-BC62 ROM and other ROMs for example the Taiwan versions. Thanks for your reply.
Forbesii said:
Things needed:1. An Xperia 1 iii (of corse)
2. A Windows PC (I don't know if there's a Mac or Linux version, but I didn't find it)
3. A reliable USB-C cable
4. NewFlasher
Download: [TOOL] Newflasher (xperia command line flasher)
5. XperiFirm
Download: Tool Archives - XperiFirm Tool
!!!FIRST THING FIRST!!! BACKUP EVERYTHING IMPORTANT
FLASHING A PHONE WILL CAUSE DATA LOSS. PLEASE MAKE SURE YOU HAVE A BACKUP OF YOUR DATA.
1. Download and unzip the XperiFirm and select the ROM you want in the Available Firmware list and download.
View attachment 5396817View attachment 5396819
2. Once downloaded, unzip the NewFlasher into the ROM folder.
Your folder should look like this:
View attachment 5396821
3. Start a command line in the ROM folder and run "newflasher set_active:a" otherwise your phone will boot into a bootloop.
View attachment 5396823
4. Power off your phone and plug it into your PC. Hold the volume down button and the power button until the LED turns GREEN.
5. Now you can double click on the newflasher.exe in your ROM folder and follow the guide.
6. Don't disturb the flasher while it is working. Your phone will automatically turn on after the flashing is completed.
My Xperia was purchased in China (XQ-BC72). I have tried many ROMs like Hong Kong and Taiwan versions. Recently I flashed my phone with the XQ-BC62 ROM and everything works very well (mobile data, voice calling, data roaming, dual SIM, exposure alert, etc.). However, I haven't try VoLTE because my carrier doesn't support it (SO SAD).
I'm in Canada and my carrier is CMLink. The data icon for LTE shows 4G if you're curious.
The DRM is not damaged that the Windvine security level is still L1 so you can still enjoy the HDR content on Netflix after flashing using this method.
Click to expand...
Click to collapse
Unfortunately OTA update system stops working after flashing non-native f/w, please consider this and warn others.
Don`t know why, OTA just doesn`t work.
I was able to flash to the US firmware, but I have no signal (T-Mobile). I'm wondering if I did something wrong during the process.
Hey,
I tried flashing the US firmware for Xperia 1 iii.
So my first mistake was that I unplugged it too early during the initial flash. Now I keep getting "This device is corrupt. It cannot be trusted to boot. Power off in 5 seconds."
I did this as my device was set to "newflasher set_active:b" instead of "newflasher set_active:a".
Any suggestions on where to go from here?
This initial firmware is the HK firmware.
Thanks and cheers
cambosteve said:
I was able to flash to the US firmware, but I have no signal (T-Mobile). I'm wondering if I did something wrong during the process.
Click to expand...
Click to collapse
I don't think it's your fault. My XQ-BC72 with BC62 rom has some problems on LTE network as well. The LTE connection is auto-disconnecting every 30 seconds. So I flashed it back to TW rom and the problem is solved.
DennisDD78 said:
Unfortunately OTA update system stops working after flashing non-native f/w, please consider this and warn others.
Don`t know why, OTA just doesn`t work.
Click to expand...
Click to collapse
Yes you remind me that I've received a software update but no ROM update. I will update my post. Thanks for telling me!
DennisDD78 said:
Unfortunately OTA update system stops working after flashing non-native f/w, please consider this and warn others.
Don`t know why, OTA just doesn`t work.
Click to expand...
Click to collapse
Also can you tell me what do you mean by non-native? cause I didn't get an OTA on my CN phone with TW ROM as well
Forbesii said:
I don't think it's your fault. My XQ-BC72 with BC62 rom has some problems on LTE network as well. The LTE connection is auto-disconnecting every 30 seconds. So I flashed it back to TW rom and the problem is solved.
Click to expand...
Click to collapse
Yeah i went back to the TW rom and it works perfectly as well. I did some minor research so take this with a grain if salt, but I found that the Global Xperia 1 IIIs have different bands internally compared to the US Xperia 1 IIIs. I think that’s why the network keeps on disconnecting when using the BC62 rom on BC72 phones.
Here are the instructions for keeping data intact while flashing firmware in Newflasher on the Xperia 1 III:
If you only delete userdata.sin, your data partition will be corrupt and you will be forced to factory reset and lose all your data.
To prevent this from happening, not only do you have to delete userdata.sin, but also appslog.sin, diag.sin and metadata.sin from the firmware folder as well. Found this by checking the update.xml file in the firmware folder, all required sin files to delete are listed as "<NOERASE>".
@Forbesii feel free to edit your original post to include this important information.
Forbesii said:
Also can you tell me what do you mean by non-native? cause I didn't get an OTA on my CN phone with TW ROM as well
Click to expand...
Click to collapse
The native firmware is the one that was originally installed in your new device, out of the box.
If you are flashing your device with the firmware of a different region, then now it is not the native firmware for your device.
You flashed your Chinese device with TW ROM, so now you have non-native f/w and OTA system won`t work. Reflash the device back to it`s native Chinese ROM, after that i recommend to you to make a repair with Xperia Comapsnion, and after all this OTA function will recover.
i am using 1iii chinese version, yesterday i flashed the rom but got an error, the device rebooted continuously, can anyone help me?
the screen shows the words "your device is corrutp. its can't be trusted and will no boot..."
TienDinh said:
the screen shows the words "your device is corrutp. its can't be trusted and will no boot..."
Click to expand...
Click to collapse
Yeah, it's a problem. I had to return mine because of it. There were issues with overheating and boot loop initially even when I wasn't even trying to flash it. I don't know if mine was just a lemon.
Thanks for this guide.
I'm also from Canada and first try (before reading here) ended up in a Blue LED no boot (boot loop).
I now am on Russian XQ-BC72
Anybody use TikTok ?
I think i have an weird issue since i'm on a Russian version now. Seems that once i am "logged" the comments / share icons just disappear.
I've completly reinstalled on my other phone and have no issues, just on that phone.
Going back to TW version.. will report
OhayouBaka said:
Here are the instructions for keeping data intact while flashing firmware in Newflasher on the Xperia 1 III:
If you only delete userdata.sin, your data partition will be corrupt and you will be forced to factory reset and lose all your data.
To prevent this from happening, not only do you have to delete userdata.sin, but also appslog.sin, diag.sin and metadata.sin from the firmware folder as well. Found this by checking the update.xml file in the firmware folder, all required sin files to delete are listed as "<NOERASE>".
@Forbesii feel free to edit your original post to include this important information.
Click to expand...
Click to collapse
Can confirm, I was able to update just now via newflasher and everything seems to have survived.
morphius88 said:
Can confirm, I was able to update just now via newflasher and everything seems to have survived.
Click to expand...
Click to collapse
Thanks a lot for your confirmation! My Xperia is my primary phone, so I didn't try it. Please tell me if all Google Pay cards are still there and if the android smartwatch is still connected!
Related
About a week ago, I was reading about Samsung will start pushing an OTA update to limit the phone more and maybe brick them so we can return them.
After reading a few threads, I downloaded package disabler. Unfortunately, the package disabler developer was contacted by Samsung or whatever to not show the OTA packages so that they can push the update.
I have to say, I'm not sure if this is just a rumor or if it's true, a lot of stuff like this can be found in any forum.
Also disabled update automatically and disabled the play store's automatic update as well. Paranoid much...
But I still received the notification of a new update. Now I know that this is what they want so I tried to avoid it. Then it started bugging me, so I'm like let me click on it and cancel it. Don't be fooled, there's no cancel button! There's a counter too! Which was funny. I tried putting the phone into recovery mode in hopes that it would cancel the update, but after the phone rebooted it just installed the updates.
Phone will only charge to 60, and a more annoying pop up will show saying it's illegal to have the phone or give it and have to return it and so on.
Anywhooo, I managed to get the stock rom from the previous version and decided to try and flash it maybe it'll override the update.
IT DID!!! Now my phone charges to 100 again the recall pop up is still there and its the old one not the scary one. I downloaded package disabler 6.3 and managed to block the correct packages to avoid this from happening again.
You can Google "note 7 stock rom" and find yours or you can message me and I'll send you the link.
My phone is a Roger's phone. Downloaded this N930W8VLU2API3 (release date 16.09.2016) this is the build from September.
The download was very slow speed, so be patient!
Settings, developer options, and checked "OEM unlock" and "USB debugging". Then lock screen and security and disabled SD encryption. Screen lock settings none.
TIP
Go to phone and type *#06# and write down the IMEI and S/N just incase something goes wrong and you have to use smart switch to recover the firmware. Also, back up the phone.
After downloading the firmware, I downloaded another copy. I did this to check the files' sizes and see if the download was interrupted or caused files to break.
TIP
UNZIP THE FILES FROM THE FOLDER, do not attempt to only open the zip and choose the files as it might crash.
Files should have "AP, BL, CSC, CP". I opened Odin(3.12), plugged the phone.
Odin should say that the phone is connected in port X.
Chose the files from the unzipped folder. One of the files is almost 4 GB in size, so it will take time for Odin to read. Windows might display (application not responding) on top, ignore it and wait.
Selected and checked all the files in Odin. If there's no check next to it, it won't work.
Put the phone in recovery mode (vol down + home + power), then click (vol up).
Start on Odin. It should pass.
Phone displayed the blue screen and that its installing the "update" which really should be a downgrade. Then it took a while displaying the Samsung logo. It was waving so waited.
Now the phone went back to how it was before the OTA update. :good:
That's exactly what I did after I received the OTA update. not sure if I was lucky or not but my data was still there. Didn't have to restore it. If it deleted your date, it should be fine since you backed it up.
Don't forget to uninstall package disabler then install the 6.3 version and disable the update packages!!!
This has worked for me few days ago!! All went too smooth!
Good Job Raider! This will be useful to so many people.
knight-raider said:
About a week ago, I was reading about Samsung will start pushing an OTA update to limit the phone more and maybe brick them so we can return them.
After reading a few threads, I downloaded package disabler. Unfortunately, the package disabler developer was contacted by Samsung or whatever to not show the OTA packages so that they can push the update.
I have to say, I'm not sure if this is just a rumor or if it's true, a lot of stuff like this can be found in any forum.
Also disabled update automatically and disabled the play store's automatic update as well. Paranoid much...
But I still received the notification of a new update. Now I know that this is what they want so I tried to avoid it. Then it started bugging me, so I'm like let me click on it and cancel it. Don't be fooled, there's no cancel button! There's a counter too! Which was funny. I tried putting the phone into recovery mode in hopes that it would cancel the update, but after the phone rebooted it just installed the updates.
Phone will only charge to 60, and a more annoying pop up will show saying it's illegal to have the phone or give it and have to return it and so on.
Anywhooo, I managed to get the stock rom from the previous version and decided to try and flash it maybe it'll override the update.
IT DID!!! Now my phone charges to 100 again the recall pop up is still there and its the old one not the scary one. I downloaded package disabler 6.3 and managed to block the correct packages to avoid this from happening again.
You can Google "note 7 stock rom" and find yours or you can message me and I'll send you the link.
My phone is a Roger's phone. Downloaded this N930W8VLU2API3 (release date 16.09.2016) this is the build from September.
The download was very slow speed, so be patient!
Settings, developer options, and checked "OEM unlock" and "USB debugging". Then lock screen and security and disabled SD encryption. Screen lock settings none.
TIP
Go to phone and type *#06# and write down the IMEI and S/N just incase something goes wrong and you have to use smart switch to recover the firmware. Also, back up the phone.
After downloading the firmware, I downloaded another copy. I did this to check the files' sizes and see if the download was interrupted or caused files to break.
TIP
UNZIP THE FILES FROM THE FOLDER, do not attempt to only open the zip and choose the files as it might crash.
Files should have "AP, BL, CSC, CP". I opened Odin(3.12), plugged the phone.
Odin should say that the phone is connected in port X.
Chose the files from the unzipped folder. One of the files is almost 4 GB in size, so it will take time for Odin to read. Windows might display (application not responding) on top, ignore it and wait.
Selected and checked all the files in Odin. If there's no check next to it, it won't work.
Put the phone in recovery mode (vol down + home + power), then click (vol up).
Start on Odin. It should pass.
Phone displayed the blue screen and that its installing the "update" which really should be a downgrade. Then it took a while displaying the Samsung logo. It was waving so waited.
Now the phone went back to how it was before the OTA update. :good:
That's exactly what I did after I received the OTA update. not sure if I was lucky or not but my data was still there. Didn't have to restore it. If it deleted your date, it should be fine since you backed it up.
Don't forget to uninstall package disabler then install the 6.3 version and disable the update packages!!!
Click to expand...
Click to collapse
How do you go about doing this"Don't forget to uninstall package disabler then install the 6.3 version and disable the update package" where in the phone i much go to uninstall and disable update package
joseph- said:
How do you go about doing this"Don't forget to uninstall package disabler then install the 6.3 version and disable the update package" where in the phone i much go to uninstall and disable update package
Click to expand...
Click to collapse
In my case, my date wasn't deleted. I had "Package Disabler Pro" application installed (the latest update which didn't show the OTA packages).
I uninstalled it, then downloaded the 6.3 version (which shows the packages) and disabled the OTA files
knight-raider said:
About a week ago, I was reading about Samsung will start pushing an OTA update to limit the phone more and maybe brick them so we can return them.
After reading a few threads, I downloaded package disabler. Unfortunately, the package disabler developer was contacted by Samsung or whatever to not show the OTA packages so that they can push the update.
I have to say, I'm not sure if this is just a rumor or if it's true, a lot of stuff like this can be found in any forum.
Also disabled update automatically and disabled the play store's automatic update as well. Paranoid much...
But I still received the notification of a new update. Now I know that this is what they want so I tried to avoid it. Then it started bugging me, so I'm like let me click on it and cancel it. Don't be fooled, there's no cancel button! There's a counter too! Which was funny. I tried putting the phone into recovery mode in hopes that it would cancel the update, but after the phone rebooted it just installed the updates.
Phone will only charge to 60, and a more annoying pop up will show saying it's illegal to have the phone or give it and have to return it and so on.
Anywhooo, I managed to get the stock rom from the previous version and decided to try and flash it maybe it'll override the update.
IT DID!!! Now my phone charges to 100 again the recall pop up is still there and its the old one not the scary one. I downloaded package disabler 6.3 and managed to block the correct packages to avoid this from happening again.
You can Google "note 7 stock rom" and find yours or you can message me and I'll send you the link.
My phone is a Roger's phone. Downloaded this N930W8VLU2API3 (release date 16.09.2016) this is the build from September.
The download was very slow speed, so be patient!
Settings, developer options, and checked "OEM unlock" and "USB debugging". Then lock screen and security and disabled SD encryption. Screen lock settings none.
TIP
Go to phone and type *#06# and write down the IMEI and S/N just incase something goes wrong and you have to use smart switch to recover the firmware. Also, back up the phone.
After downloading the firmware, I downloaded another copy. I did this to check the files' sizes and see if the download was interrupted or caused files to break.
TIP
UNZIP THE FILES FROM THE FOLDER, do not attempt to only open the zip and choose the files as it might crash.
Files should have "AP, BL, CSC, CP". I opened Odin(3.12), plugged the phone.
Odin should say that the phone is connected in port X.
Chose the files from the unzipped folder. One of the files is almost 4 GB in size, so it will take time for Odin to read. Windows might display (application not responding) on top, ignore it and wait.
Selected and checked all the files in Odin. If there's no check next to it, it won't work.
Put the phone in recovery mode (vol down + home + power), then click (vol up).
Start on Odin. It should pass.
Phone displayed the blue screen and that its installing the "update" which really should be a downgrade. Then it took a while displaying the Samsung logo. It was waving so waited.
Now the phone went back to how it was before the OTA update. :good:
That's exactly what I did after I received the OTA update. not sure if I was lucky or not but my data was still there. Didn't have to restore it. If it deleted your date, it should be fine since you backed it up.
Don't forget to uninstall package disabler then install the 6.3 version and disable the update packages!!!
Click to expand...
Click to collapse
Funny because i tried same thing and odin failed. It won't allow rolling bk to original rom.
knight-raider said:
About a week ago, I was reading about Samsung will start pushing an OTA update to limit the phone more and maybe brick them so we can return them.
After reading a few threads, I downloaded package disabler. Unfortunately, the package disabler developer was contacted by Samsung or whatever to not show the OTA packages so that they can push the update.
I have to say, I'm not sure if this is just a rumor or if it's true, a lot of stuff like this can be found in any forum.
Also disabled update automatically and disabled the play store's automatic update as well. Paranoid much...
But I still received the notification of a new update. Now I know that this is what they want so I tried to avoid it. Then it started bugging me, so I'm like let me click on it and cancel it. Don't be fooled, there's no cancel button! There's a counter too! Which was funny. I tried putting the phone into recovery mode in hopes that it would cancel the update, but after the phone rebooted it just installed the updates.
Phone will only charge to 60, and a more annoying pop up will show saying it's illegal to have the phone or give it and have to return it and so on.
Anywhooo, I managed to get the stock rom from the previous version and decided to try and flash it maybe it'll override the update.
IT DID!!! Now my phone charges to 100 again the recall pop up is still there and its the old one not the scary one. I downloaded package disabler 6.3 and managed to block the correct packages to avoid this from happening again.
You can Google "note 7 stock rom" and find yours or you can message me and I'll send you the link.
My phone is a Roger's phone. Downloaded this N930W8VLU2API3 (release date 16.09.2016) this is the build from September.
The download was very slow speed, so be patient!
Settings, developer options, and checked "OEM unlock" and "USB debugging". Then lock screen and security and disabled SD encryption. Screen lock settings none.
TIP
Go to phone and type *#06# and write down the IMEI and S/N just incase something goes wrong and you have to use smart switch to recover the firmware. Also, back up the phone.
After downloading the firmware, I downloaded another copy. I did this to check the files' sizes and see if the download was interrupted or caused files to break.
TIP
UNZIP THE FILES FROM THE FOLDER, do not attempt to only open the zip and choose the files as it might crash.
Files should have "AP, BL, CSC, CP". I opened Odin(3.12), plugged the phone.
Odin should say that the phone is connected in port X.
Chose the files from the unzipped folder. One of the files is almost 4 GB in size, so it will take time for Odin to read. Windows might display (application not responding) on top, ignore it and wait.
Selected and checked all the files in Odin. If there's no check next to it, it won't work.
Put the phone in recovery mode (vol down + home + power), then click (vol up).
Start on Odin. It should pass.
Phone displayed the blue screen and that its installing the "update" which really should be a downgrade. Then it took a while displaying the Samsung logo. It was waving so waited.
Now the phone went back to how it was before the OTA update. :good:
That's exactly what I did after I received the OTA update. not sure if I was lucky or not but my data was still there. Didn't have to restore it. If it deleted your date, it should be fine since you backed it up.
Don't forget to uninstall package disabler then install the 6.3 version and disable the update packages!!!
Click to expand...
Click to collapse
WORKED FOR ME AS WELL!!! Green Battery is back! now lets see if it charges over 60%
I've downloaded Package Disabler Pro 6.3 on my Note 7 after sucessfully using Odin to go back one software update.
However, I've disabled all the following...
com.policydm
com.sec.android.soagent
com.samsung.android.omcagent
com.wssyncmldm
com.sec.spp.push
Except for the most important ones...
com.samsung.firmware.sensorhub
com.samsung.android.firmware.tsp
Because they don't come up.
Will this be an issue?
Can you not just root and install a custom rom?
marvi0 said:
Can you not just root and install a custom rom?
Click to expand...
Click to collapse
No root for the snapdragon
Maiesta_Miyabi said:
I've downloaded Package Disabler Pro 6.3 on my Note 7 after sucessfully using Odin to go back one software update.
However, I've disabled all the following...
com.policydm
com.sec.android.soagent
com.samsung.android.omcagent
com.wssyncmldm
com.sec.spp.push
Except for the most important ones...
com.samsung.firmware.sensorhub
com.samsung.android.firmware.tsp
Because they don't come up.
Will this be an issue?
Click to expand...
Click to collapse
Did you have a previous version installed?
knight-raider said:
About a week ago, I was reading about Samsung will start pushing an OTA update to limit the phone more and maybe brick them so we can return them.
After reading a few threads, I downloaded package disabler. Unfortunately, the package disabler developer was contacted by Samsung or whatever to not show the OTA packages so that they can push the update.
I have to say, I'm not sure if this is just a rumor or if it's true, a lot of stuff like this can be found in any forum.
Also disabled update automatically and disabled the play store's automatic update as well. Paranoid much...
But I still received the notification of a new update. Now I know that this is what they want so I tried to avoid it. Then it started bugging me, so I'm like let me click on it and cancel it. Don't be fooled, there's no cancel button! There's a counter too! Which was funny. I tried putting the phone into recovery mode in hopes that it would cancel the update, but after the phone rebooted it just installed the updates.
Phone will only charge to 60, and a more annoying pop up will show saying it's illegal to have the phone or give it and have to return it and so on.
Anywhooo, I managed to get the stock rom from the previous version and decided to try and flash it maybe it'll override the update.
IT DID!!! Now my phone charges to 100 again the recall pop up is still there and its the old one not the scary one. I downloaded package disabler 6.3 and managed to block the correct packages to avoid this from happening again.
You can Google "note 7 stock rom" and find yours or you can message me and I'll send you the link.
My phone is a Roger's phone. Downloaded this N930W8VLU2API3 (release date 16.09.2016) this is the build from September.
The download was very slow speed, so be patient!
Settings, developer options, and checked "OEM unlock" and "USB debugging". Then lock screen and security and disabled SD encryption. Screen lock settings none.
TIP
Go to phone and type *#06# and write down the IMEI and S/N just incase something goes wrong and you have to use smart switch to recover the firmware. Also, back up the phone.
After downloading the firmware, I downloaded another copy. I did this to check the files' sizes and see if the download was interrupted or caused files to break.
TIP
UNZIP THE FILES FROM THE FOLDER, do not attempt to only open the zip and choose the files as it might crash.
Files should have "AP, BL, CSC, CP". I opened Odin(3.12), plugged the phone.
Odin should say that the phone is connected in port X.
Chose the files from the unzipped folder. One of the files is almost 4 GB in size, so it will take time for Odin to read. Windows might display (application not responding) on top, ignore it and wait.
Selected and checked all the files in Odin. If there's no check next to it, it won't work.
Put the phone in recovery mode (vol down + home + power), then click (vol up).
Start on Odin. It should pass.
Phone displayed the blue screen and that its installing the "update" which really should be a downgrade. Then it took a while displaying the Samsung logo. It was waving so waited.
Now the phone went back to how it was before the OTA update. :good:
That's exactly what I did after I received the OTA update. not sure if I was lucky or not but my data was still there. Didn't have to restore it. If it deleted your date, it should be fine since you backed it up.
Don't forget to uninstall package disabler then install the 6.3 version and disable the update packages!!!
Click to expand...
Click to collapse
So this is funny but i kinda fixes my phone lol now it charges up to 100. I tried koodo firmware and i was able to restore it. Originally i tried the general Samsung firmware for note 7 nd it kept on failing in odin then i realized wen i put my simcard in back wen first got the phone it looked to koodo. Now i used pkg disabler to disable updates too.
{
"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"
}
No previous version installed.
Att version
Mine is SM-930A. It's the AT&T version. Please help.
knight-raider said:
About a week ago, I was reading about Samsung will start pushing an OTA update to limit the phone more and maybe brick them so we can return them.
After reading a few threads, I downloaded package disabler. Unfortunately, the package disabler developer was contacted by Samsung or whatever to not show the OTA packages so that they can push the update.
I have to say, I'm not sure if this is just a rumor or if it's true, a lot of stuff like this can be found in any forum.
Also disabled update automatically and disabled the play store's automatic update as well. Paranoid much...
But I still received the notification of a new update. Now I know that this is what they want so I tried to avoid it. Then it started bugging me, so I'm like let me click on it and cancel it. Don't be fooled, there's no cancel button! There's a counter too! Which was funny. I tried putting the phone into recovery mode in hopes that it would cancel the update, but after the phone rebooted it just installed the updates.
Phone will only charge to 60, and a more annoying pop up will show saying it's illegal to have the phone or give it and have to return it and so on.
Anywhooo, I managed to get the stock rom from the previous version and decided to try and flash it maybe it'll override the update.
IT DID!!! Now my phone charges to 100 again the recall pop up is still there and its the old one not the scary one. I downloaded package disabler 6.3 and managed to block the correct packages to avoid this from happening again.
You can Google "note 7 stock rom" and find yours or you can message me and I'll send you the link.
My phone is a Roger's phone. Downloaded this N930W8VLU2API3 (release date 16.09.2016) this is the build from September.
The download was very slow speed, so be patient!
Settings, developer options, and checked "OEM unlock" and "USB debugging". Then lock screen and security and disabled SD encryption. Screen lock settings none.
TIP
Go to phone and type *#06# and write down the IMEI and S/N just incase something goes wrong and you have to use smart switch to recover the firmware. Also, back up the phone.
After downloading the firmware, I downloaded another copy. I did this to check the files' sizes and see if the download was interrupted or caused files to break.
TIP
UNZIP THE FILES FROM THE FOLDER, do not attempt to only open the zip and choose the files as it might crash.
Files should have "AP, BL, CSC, CP". I opened Odin(3.12), plugged the phone.
Odin should say that the phone is connected in port X.
Chose the files from the unzipped folder. One of the files is almost 4 GB in size, so it will take time for Odin to read. Windows might display (application not responding) on top, ignore it and wait.
Selected and checked all the files in Odin. If there's no check next to it, it won't work.
Put the phone in recovery mode (vol down + home + power), then click (vol up).
Start on Odin. It should pass.
Phone displayed the blue screen and that its installing the "update" which really should be a downgrade. Then it took a while displaying the Samsung logo. It was waving so waited.
Now the phone went back to how it was before the OTA update. :good:
That's exactly what I did after I received the OTA update. not sure if I was lucky or not but my data was still there. Didn't have to restore it. If it deleted your date, it should be fine since you backed it up.
Don't forget to uninstall package disabler then install the 6.3 version and disable the update packages!!!
Click to expand...
Click to collapse
worked thank you
I did the same thing as instructed and was able to downgrade my note 7 snap dragon to a previous stock version before the forced update. Battery is back to 100%, no update messages everything seems to be running great. However I noticed my Secure folder is no longer working. Has anyone else having this issue? When I try to open secure folder or setup the folder it gives me a error message saying " Secure folder cannot be set up because unauthorized software was installed on the device. I got the rom from Sam mobile for my Rogers phone Sept update. Sometimes the error messages says " Failed to create knox mode. Try again. When I use an app to check my if my knox has been tripped is says everything is normal, 0x0 valid warrenty. Any ideas what a solution could be?
By the way... Thanks for posting how to downgrade and get my note 7 back to normal working condition!
goldensun7 said:
I did the same thing as instructed and was able to downgrade my note 7 snap dragon to a previous stock version before the forced update. Battery is back to 100%, no update messages everything seems to be running great. However I noticed my Secure folder is no longer working. Has anyone else having this issue? When I try to open secure folder or setup the folder it gives me a error message saying " Secure folder cannot be set up because unauthorized software was installed on the device. I got the rom from Sam mobile for my Rogers phone Sept update. Sometimes the error messages says " Failed to create knox mode. Try again. When I use an app to check my if my knox has been tripped is says everything is normal, 0x0 valid warrenty. Any ideas what a solution could be?
By the way... Thanks for posting how to downgrade and get my note 7 back to normal working condition!
Click to expand...
Click to collapse
Ok looks like I fixed the problem. I only flashed the larger AP file and not all the files in the stock rom. Once I flashed the other files, secure folder became available.
Be sure to flash all files in the stock rom.
oh man I cant thank you enough for helping me bring some life back into my phone! the 60% was brutal! back to 100% charge now!!!
I did run into some issues, and in case this helps anyone else who couldnt get odin to pass the most important thing is to make sure your downloading the right carrier version of the firmware. You need to use the carrier version that matches the same one the phone was originally activated. In my case, my Bell note 7 was originally activated using a virgin mobile sim card so odin would fail until I used the VMC region instead of BMC.
Thanks again!
would someone be kind enough to post a youtube video for those of us who are not so familiar with using ODIN
Thank You.
Its great that some of you are able to fight back against the 60 percent update, i blocked mine before it even happened but nothing will help us when the carriers block our devices... i just got off the phone with sprint (US) and they told me they will definately block the note 7s in the near future long before the 8 comes out... if someone has a solution, please pm me or post it here if you can...
Personally my story about keeping the no seven is probably a lot different than most people...
In February my now ex wife stole my Note Edge and kicked me out of my own house at gunpoint.... thankfully i got away with my tab 4... but it got stolen when i was homeless from being kicked out and living in my car...
So two devices stolen from me in less than a year, but hope was on the horizon. I had heard the note seven was coming out and so I stayed without a phone for three to four months and got the note seven the day it was released.
The note 7 is my trophy, it is my monument to not ever getting robbed again and then samsung wants to take it.
rkawli said:
would someone be kind enough to post a youtube video for those of us who are not so familiar with using ODIN
Thank You.
Click to expand...
Click to collapse
check youtube there are a lot of instructional vids. the process is the same for every ROM. you can download the ROM from sammobile.com firmware section. let me know if you can't figure it out still. I can try and help.
Hello everyone. I have a samsung galaxy s7 edge (SM G935F) and i recently received the android 8.0.0 from samsung. Downloaded and installed directly via the cellphone.
But after updating i am getting this internet/connection drop issues a lot.
Now a lot of times when im connected in wifi or using the 4g mobile internet, im getting a lot of internet lag/drops. Example: at whatsapp, when i sens a message, the clock appears and only after a little rhe time the message is send.
Example 2: at facebook, somerimes it lags and takes too long to load the content (same happening in instagram). Or at clash of clans, it is showing that symbol of internet issue.
Besides those internet bugs/lags, the android 8.0.0 is ok.
I already did a factory reset yesterday via the phone, and saved the files with smart switch. But the problem persists. I also checked and my wifi internet and my mobile internet are ok.
Does anyone knows how to fix this issue? Is there a newer version of the ROM, maybe? Or if not, is ir possible to downgrade to android 7 again (really wouldnt like this option but....)?
If anyone could help that would be great. But for the record:im really newbie at android stuffs....if you can help, please could you explain step by step?
Thanks everyone
lokoroxbr said:
Hello everyone. I have a samsung galaxy s7 edge (SM G935F) and i recently received the android 8.0.0 from samsung. Downloaded and installed directly via the cellphone.
But after updating i am getting this internet/connection drop issues a lot.
Now a lot of times when im connected in wifi or using the 4g mobile internet, im getting a lot of internet lag/drops. Example: at whatsapp, when i sens a message, the clock appears and only after a little rhe time the message is send.
Example 2: at facebook, somerimes it lags and takes too long to load the content (same happening in instagram). Or at clash of clans, it is showing that symbol of internet issue.
Besides those internet bugs/lags, the android 8.0.0 is ok.
I already did a factory reset yesterday via the phone, and saved the files with smart switch. But the problem persists. I also checked and my wifi internet and my mobile internet are ok.
Does anyone knows how to fix this issue? Is there a newer version of the ROM, maybe? Or if not, is ir possible to downgrade to android 7 again (really wouldnt like this option but....)?
If anyone could help that would be great. But for the record:im really newbie at android stuffs....if you can help, please could you explain step by step?
Thanks everyone
Click to expand...
Click to collapse
I have the same phone but in my region the OTA 8.0 upgrade didn't arrive yet so I took a french official 8.0 for SM-G935F and installed it. After about one week I can tell it works like a charm and even better than before with the Marshmallow firmware. I don't see a solution with your specific connection problem but I can try to find and bring you the OS that I downloaded and used if you want.
AlonzoGrande1 said:
I have the same phone but in my region the OTA 8.0 upgrade didn't arrive yet so I took a french official 8.0 for SM-G935F and installed it. After about one week I can tell it works like a charm and even better than before with the Marshmallow firmware. I don't see a solution with your specific connection problem but I can try to find and bring you the OS that I downloaded and used if you want.
Click to expand...
Click to collapse
mate if you can post here the download link of your OS would be great !!! So i install it and do a complete reset & cache wipe.
Did you downloaded at Sammobile ???
lokoroxbr said:
mate if you can post here the download link of your OS would be great !!! So i install it and do a complete reset & cache wipe.
Did you downloaded at Sammobile ???
Click to expand...
Click to collapse
NO, i can't seem to remember where i downloaded the firmware from, but I am sure it wasn't from Sammobile because it take ages to download. But I still have it on my laptop so I'm uploading the .rar on mediafire.
All you have to do:
Get Odin
Get the ROM (extract it separately, you should see the AP, BL, CP, CSC components)
Cause I am a new user on the forum it doesn't allow me to post external links so let's get around that:
type in w w w. mediafire . com /file / tx3676bj71vz17f/G935FXXU2ERD5_G935FOXA2ERD5_BTU.zip (copy paste and remove all the spaces)
Activate USB debugging (google that, you can get it in 30 secs)
press and hold power+home_button+volum_down then press volume_up when it asks you to confirm that you know what you're doing.
Open Odin, you should see that your phone is recognized (in the top left rectangle it shows COM something.
Add the AP, BL, CP and CSC from the folder to Odin by pressing the specific buttons and then selecting them, wait between them if necessary, it will tell you.
Make sure re partition is not ticked in the options tab.
after everytihng is ready, click start and wait some time.
When it is done you should see PASS in green and your phone restarting.\
From there you just have to configure your new OS. Bare in mind that you should know the google acc and password that you had on the phone before, else it will get FRP locked.
Hope this helps, If you have any questions feel free to ask.
{
"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"
}
Here's my first effort at porting the Nexus Stock custom ROM to the 2019 Galaxy Tab A 8.0 [SM-T290] on Android 10. It's very much a work in progress, but it should hopefully help blaze the trail for even better work.
Notes:
The current process may require you to reset to factory defaults to remove file-based encryption. Remember to backup your data!
The system is based on eremitein's CAOS GSI project with the latest Stock variant from OpenGApps.
Boot animation and default wallpaper is from my Nexus series of custom ROMs for Android TV, and I'm using the Pixel boot animation with black background.
This should be installed using my latest TWRP build for the SM-T290.
The properties now correctly identify the device as a tablet, and so the Google Dialer and Messenger are no longer installed. I've also disabled the Emergency button, but SetupWizard still insists on reminding you to insert a SIM (sigh!).
This is unofficial and unsupported, so the usual caveats apply. Since we don't mess with the bootloader, you should be able recover from any problems...but nothing is guaranteed.
Not working:
Support for file-based encryption
MTP support (pending FFS MTP fix)
Downloads:
Nexus_Stock_CR_T290XXU3CUK4-20220327.tar.md5 (Odin tarball)
Nexus_Stock_CR_T290XXU3CUK4-20220327.zip (TWRP update)
Build Archives:
Android File Host
Change Log:
20220327:
Updated to Android 11 OEM stock T290XXU3CUK4 kernel (November 2021 Update).
System partition based on CAOS 11.0 v316 (March 2022 Security Update)
Updated TWRP recovery to v3.6.1_11-0 (20220327).
Stripped product partition to get .zip update under the 2GB limit.
20220220:
Boots normally for offline (cold) charging
System partition based on CAOS 11.0 v315 (January 2022 Security Update)
Updated TWRP recovery to v3.6.0_11-1 (20220220).
Updated Google apps from latest OpenGapps Stock variant (20220215) w/ rollback for WebView
20211121:
Updated to Android 11 OEM stock T290XXU3CUG4 kernel (July 2021 Update).
Switched underlying GSI from LineageOS 17.1 to CAOS 11.
Updated TWRP recovery to v3.5.2_9-1 (20211017).
Updated Google apps from latest OpenGapps Stock variant (20211120) w/ rollback for WebView
IMPORANT NOTE: Dirty flash is not possible because we're transitioning to Android 11 kernel. Use Oden and do a factory reset from TWRP.
20210516:
Switched GSI from custom AOSP build to the latest LineageOS 17.1 (20210512).
Restored enforced OEM file-based encryption to work around issue with screen lock.
Sized boot animation correctly for 720p screen.
Worked around issue with OpenGApp's Google Recorder installation.
Updated to OEM stock T290XXU3BUC1 kernel (March 2021 Update).
Updated TWRP recovery to v3.5.2_9-0.
Updated Google apps from latest OpenGapps Stock variant (20210515)
20210104:
Updated to OEM stock T290XXS3BTL6 kernel (December 2020 Update).
Updated TWRP recovery to v3.5.0_9-0.
Updated Google apps from latest OpenGapps Stock variant (20201223)
20201223:
Initial build based on OEM stock T290XXU3BTI2 kernel (September 2020 Update) and AOSP 10.0 v222.
Latest Google apps from Stock variant of OpenGApps (20201205)
Instructions:
From OEM stock firmware:
Unlock bootloader
Ensure matching OEM build (e.g. T290XXU3CUG4) is installed
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install custom ROM tarball (.tar.md5 file) to AP with Odin
When TWRP launches, factory reset with Wipe->Format Data. (Not necessary for incremental upgrades.)
Reboot to system
From existing TWRP install (for incremental updates):
Hold Power & Vol Up during restart to enter TWRP recovery
Tap Install, select your update (.zip file), and then swipe to install
Reboot to system
Source:
android_device_samsung_gtowifi
Phh-Treble
Donations:
Your support is always appreciated! Just click here.
I'm leveraging a ton of work done by @phhusson for Treble GSIs, so please show him some love here!
Note: If you install Google Recorder from the Google Play Store, it works just fine. The issue is with the pre-installed APK from OpenGApps.
Hello! Finally first custom rom for our tablet =)
Using this for couple hours, it seems, almost everything works pretty fine. When i installed, the first issue was Google Assistant, cant skip this while first setup. Then i installed Magisk and see that SafetyNet check failed (but basic is true). SafetyNet on stock firmware failed too, but MagiskHide always help. In your ROM, if i turn on MagiskHide, i got cyclyng reboot, over and over again until i turn "hide" off.
Its really sad that MTP is not working.
About the rom: Everything good, no trash apps, works faster than stock, battery drain good... and... i dont know what i can say else =)
Thank you so much for this work!
Also i have a one question. Can you make a custom Kernel with GPU Overclock? Tablet not so bad and run some games pretty well, with overclock they can be runs much better. GPU is a bottleneck in this tablet i think.
Sorry for bad English, if it is =)
eclipse00074 said:
SafetyNet check failed (but basic is true). SafetyNet on stock firmware failed too, but MagiskHide always help. In your ROM, if i turn on MagiskHide, i got cyclyng reboot, over and over again until i turn "hide" off.
Click to expand...
Click to collapse
SafetyNet fails by design on any device with an unlocked bootloader and custom ROM. Magisk has its tricks to try to fool SafetyNet, but it's a bit of Whack-a-Mole game.
eclipse00074 said:
Can you make a custom Kernel with GPU Overclock? Tablet not so bad and run some games pretty well, with overclock they can be runs much better.
Click to expand...
Click to collapse
Unfortunately, the Android 10 kernel source that was posted last week is not working. It compiles fine, but builds to a significantly different size and crashes to the bootloader when packaged in either boot or recovery images. Until that's addressed, I can't provide an MTP fix or any overclocking.
Note: I just posted a v3.4.0-1 update to my TWRP for SM-T290 thread that includes a new custom T290UES3ATC1 kernel fixing MTP support. If you install it over the TWRP build included in this build, it will allow file transfers on this custom ROM by rebooting to recovery.
Since this is an Android 10 custom ROM, I can't use it in the boot image, but it's a workaround until we get working T290XXU3BTI2 kernel source.
Hi, there. I've managed to get the image installed, used the compatible version, etc. After rebooting, I got to TWRP, did the wipe, etc. Upon reboot, I get through to the setup process, skip the SIM setup stuff (no cell stuff in this T290) and then when trying to add a wifi connection, it never completes the "Connect to WiFi" step. If I skip, I can get through manual set up of the basics, manual time config, a few other prompts. All that seems okay. But even when I get to the main menu menu, it seems like everything is working (pulls up, etc) but I'm still not connected. The WiFi radio appears to be turned completely off. Each time I try to turn it back on, it flashes on for a split second, then immediately turns off again.
Any ideas I can try to get this enabled?
Edit: Bluetooth is working, was able to connect to another device. The device had previously been using WiFi with the stock image with no problems.
qntmcat said:
Hi, there. I've managed to get the image installed, used the compatible version, etc. After rebooting, I got to TWRP, did the wipe, etc. Upon reboot, I get through to the setup process, skip the SIM setup stuff (no cell stuff in this T290) and then when trying to add a wifi connection, it never completes the "Connect to WiFi" step. If I skip, I can get through manual set up of the basics, manual time config, a few other prompts. All that seems okay. But even when I get to the main menu menu, it seems like everything is working (pulls up, etc) but I'm still not connected. The WiFi radio appears to be turned completely off. Each time I try to turn it back on, it flashes on for a split second, then immediately turns off again.
Any ideas I can try to get this enabled?
Click to expand...
Click to collapse
Okay, all weekend I've been trying to figure out why wireless isn't working on my custom kernel, but it appears the OEM kernel isn't working as well...and I didn't even realize it. This is actually a hugely valuable data point that will drive my troubleshooting in an entirely different direction.
I'm embarrassed that I missed this in my initial smoke testing, but at least I know that my MTP fix is solid. More info to follow...
Awesome, I passively helped with a thing! =)
qntmcat said:
Awesome, I passively helped with a thing! =)
Click to expand...
Click to collapse
I can still only reproduce the wireless networking issue with kernel's built from Samsung's posted kernel source. The released T290XXU3BTI2 boot image works fine (and my original tarball shouldn't have replaced it). Did you upgrade to the OEM release of T290XXU3BTI2 prior to installing my custom ROM? If not, you may be running with an Android 9.0 kernel and Android 10.0 vendor partition.
Hm. I believe I did, but I went through a few iterations before I got everything to work right. (Not super familiar with Odin.) I restored everything by using that OEM image, pushed through Odin. Restarted the system and caught it back into download mode and replaced AP with your image ( Nexus_Stock_AQ_T290XXU3BTI2-20201206.tar.md5). Restarted, caught TWRP, and used it to wipe the data and cache. Restarted. Long cycle, followed by the "Let's get started" screen.
I can try this again tomorrow, starting from scratch in case I messed something up.
I've gotten it maybe working after a few iterations. I'm not expert at this, so this is pure cargo-cult work of just trying to follow the various instruction sets out there, but I've tried several iterations and documented a few FAIL messages. Try not to laugh too hard at my flailing.
What I did:
1. Restored to OEM (ODIN 3.14.4, used theBL/AP/CP/CSC from XAR-T290XXU3BTI2-20201021133521.zip)
--Restore completed normally
2. Confirmed functional. Performed "Let's Go" setup. WiFi was working and detected my AP during setup. Did device registration etc.
--Tablet working normally
3. Stopped tablet, put back into download mode,used Odin3 again , AP = Nexus_Stock_AQ_T290XXU3BTI2-20201206.tar.md5 (no BL / CP / CSC selected)
--Fail at system.img.ext4
--Error on the tablet: SW REV CHECK FAIL : [system]Fused 3 > Binary 0
4. Restarted, and redid step 1 to restore back to stock.
--Did not confirm status, in case first boot did something to cause the issue
5. Restarted, and repeated step 3
--Same failure point / message
6. Restarted, redid step 1 again to restore
7. Restarted immediately and restored again, this time using stock BL / CP / CSC along with custom AP above.
--Same failure point / message
This next works, but there is an error, an
8. Reread information above, decided to apply the TWRP MTP correction you list above. I know this is stupid, because of version differences, but I thought it might be worth a try because I think this may have been what I did to get it partly working before. (Is there another TWRP MTP corrected image I would use here??)
9. Repeated step 1 to get fully stock
10. Restarted, Pushed the TWRP image from your post reference above in AP, along with the BL/CP/CSC files from BTI2 (because dumb? This seems like it shouldn't work because of the version difference.)
11. Pushed without issue. Made it to the TWRP menu. Did a wipe. Restarted.
12. Used Odin to push stock BL/CP/CSC files along with your custom AP again.
13. It worked (kinda.) I did not get the rev check fail I got before, but I did get an error when the vbmeta.img came up which read: SECURE CHECK FAIL : VBMETA -- But Odin kept pushing and gave me a PASS! at the end.
14. Restarted. Again, caught TWRP on the restart and told it to wipe again (just to be safe, but this could also have just been stupid)
15. Restarted.
16. Okay, this time I got to the "Start" button, and it actually made it to the wifi screen *and detected my AP!
17. Set up google account -- Initial login worked, but 2-step verification did not (brings up the correct prompts, but both the bluetooth and usb titankey get to a certain point and then halt. In the case of the bluetooth, it gets to the point where it says you need to enter the 6-digit code from the back of the key, but pressing NEXT button does nothing. In the case of the usb titankey, it prompts for the "tap the gold disc", I get lights on the titankey, but it never recognizes the tap.)
18. Used the "tap on a phone" method instead,, which worked.
19. Noticed an odd message after the "checking your account" message, couldn't catch all of it, but it said something about screen lock already being on. Probably benign.
20. Changed font sizes and swapped wallpapers just to check them out. Works as expected.
21. Tested Play Store. Loads. Was able to update apps (some are still updating) and install a few things I wanted. No issues.
22. Wanted to validate that the bluetooth titan key worked, so I went and paired it. Works fine from this level, got the "enter the code" prompt from paring,.
23. All apps I've tried so far have worked. Will explore some underpinnings to see if I find any other goofiness.
So, WiFi works now? Didn't work last times I did it a few days ago? Not sure what I did different, but pushing TWRP (even if it's the wrong version) seems to have done the trick.
(Now I just have to try to parse out whether I need to do the multidisabler / root / other stuff.)
I did find something not working, which is the screen lock. I am unable to get it to set to anything other than SWIPE. It *tries* to set it when I go to pin/password/pattern, it loads the change function for that thing, but when I complete the change, I get the same error I got during setup:
Screen lock was already changed. Try again with the new screen lock.
Additional: While bluetooth seems to be working for device connections and so on, I don't appear to be able to get sound output to actually go there, even when the paired device is listed as the correct one for sound output. Probably more of my just being wrong and uninformed.
qntmcat said:
Hm. I believe I did, but I went through a few iterations before I got everything to work right. (Not super familiar with Odin.) I restored everything by using that OEM image, pushed through Odin. Restarted the system and caught it back into download mode and replaced AP with your image ( Nexus_Stock_AQ_T290XXU3BTI2-20201206.tar.md5). Restarted, caught TWRP, and used it to wipe the data and cache. Restarted. Long cycle, followed by the "Let's get started" screen.
I can try this again tomorrow, starting from scratch in case I messed something up.
Click to expand...
Click to collapse
After going from stock to custom ROM you must FORMAT , not just wipe, the data partition. Wiping does NOT get rid of the encryption.
lewmur said:
After going from stock to custom ROM you must FORMAT , not just wipe, the data partition. Wiping does NOT get rid of the encryption.
Click to expand...
Click to collapse
Interesting. I will have to go through this process again, perhaps.
Will it work on the SM-T295 model?
Edit: And also can you provide me with a screenshot of the ROM? Thanks
I also have the Bluetooth connects but no audio issue. It instead plays through the speaker. Also the same issue if you plug headphones in via the headphone jack, but at least in that case you can hear through the headphones. Love the nexus theme, can't stand the samsung UI.
So can this ROM be used on SM-T295?
Also having the "no audio through Bluetooth" issue. other than that, build is awesome!
I am having trouble flashing this on my tablet; I have OEM unlock enabled and have unlocked the bootloader. It went through a reset after this and I confirmed that my version is T290XXU3BTI2. I flashed via Odin and had a failure like qnmtcat (SW REV CHECK FAIL : [system]Fused 3 > Binary 0), so I flashed back to T290XXU3BTI2 and then tried again. Now, I am stuck at the pre-boot software update error screen and can't get into anything or restore via Smart Switch as directed on the screen; I have tried various button combinations at various times (holding Vol + & Vol - stops boot at unlocked bootloader warning; pressing Vol + & Vol - opens Options menu, but all options return to error screen; from power off Vol + & Vol - & inserting cable returns to error screen). I haven't used Odin or custom ROMs in a few years, but I'm not unfamiliar with the process from that time. Thanks for any assistance! I would REALLY like to get a ROM like this going because the tablet is painfully slow for me on stock.
UPDATE: I was able to flash back to the OEM ROM and it is running fine now, but still would appreciate any help in figuring out what I am doing wrong and why it isn't working for me. TIA
UPDATE #2: I got it to work doing mostly the same steps as qnmtcat: from stock, flashing the TWRP 3.4.0-1 linked above and then the ROM; I did still get an error with vbmeta, but I haven't noticed the effect of that yet. I also previously had issues getting into TWRP using the button combination in the OP and it seems like holding just the Vol + beginning immediately after pressing Power to bypass the unlocked bootloader warning screen works better for me.
WeededSquash said:
UPDATE #2: I got it to work doing mostly the same steps as qnmtcat: from stock, flashing the TWRP 3.4.0-1 linked above and then the ROM; I did still get an error with vbmeta, but I haven't noticed the effect of that yet. I also previously had issues getting into TWRP using the button combination in the OP and it seems like holding just the Vol + beginning immediately after pressing Power to bypass the unlocked bootloader warning screen works better for me.
Click to expand...
Click to collapse
looks like the exaxt same process I had to take (first twrp 3.4.0-1, then rom), same difficulties with accessing twrp recovery, volume up button seems to do the trick better.
do you have sound routing through bluetooth, or also no sound going to bluetooth device, although connected?
shmigao said:
looks like the exaxt same process I had to take (first twrp 3.4.0-1, then rom), same difficulties with accessing twrp recovery, volume up button seems to do the trick better.
do you have sound routing through bluetooth, or also no sound going to bluetooth device, although connected?
Click to expand...
Click to collapse
I had the same issue UNTIL I played with some of the settings in the "Phh Treble Settings"! Try enabling "Force-disable A2DP offload" in "Misc features" and then restarting; that seemed to work for me.
Please read and DO AT YOUR OWN RISK
After searching everywhere and trying to get a clear answer on the Global ROM_ROW support for Android 11 on the Lenovo Legion Duel (one), all I could find was don't use the Chinese ROM as it has many issues. So, like any person told not to I tried it. Though it worked I had multiple issues with sensors and my cell service in the USA. I went back to GLOBAL ROM .332 which was the most stable for me but did lose my casting ability for playing my games to my TV. This is a deal breaker for me as I take my phone on the go and hook to friends and family's TV's for Steam, Emulation, etc and we use the casting, as this allows me to play my games. Note I also use it for Gamepass cast to the screen for friends to watch the game etc.
I finally found an Android 11 non China ROM, but it was an EE ROM on another site (which I had to pay for) but NO Global ROW ROM as installed on the phone when I purchased it. After backing up my data yet again, I tried to install this one (see link below for how to install). Once I installed and rebooted the Lenovo Legion L79031 v EE 12.5.251_ST rom, and set my cell APN, Turned the 5G to NSA-SA and networks preference (to NR-LTE-GDSM etc...) it began to function. After prox. 30 seconds after a reboot from changing the settings, I got a notification for an update (YES OTA). The update is for 12.5.320 which has notification fixes and bug fixes. Hopefully, this will be my last time having to flash the device! But I can confirm the EE rom for 11 does function on T-Mobile in the USA and works with out issue so far, has only been a short time for usage, but finally a solution for me.
Pros:
Android 11
Battery life improved
Smoother touch rate
OTA UPDATES
(Everything seems to function including cell and text messages on USA T-Mobile including the 5G NR)
Cameras work for everything even BARCODE readers and Mobile banking depo which was an issue before (at least for me). Pic snap faster but no real software updates from last build for controls as far as I can tell.
ZUI loads much faster.
Cons:
Lost all settings backups seems to cause issue when restoring so manually re-adding is the best solution.
APN setting and other settings might need to be redone, if installing from a back up or updating with OTA update.
Rebooting seems to take longer.
{
"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"
}
As for what everyone really wants the links and how to install, I have linked to a video I send to others to use for installing the ROM, it is NOT my video, but the best one on YOUTUBE( I found recently); I had my 8 year old son help me a few weeks ago update a friends Duel and I let my son follow the vid and install the rom, OBV I did the downloads on the PC and setup the file location but he was able to follow the steps well to load the files to the phone, which is why I suggest to us it. The first time installing is scary! There is BIG BIG BIG pre-req beforehand, back up your phones drives as mentioned in other post on this forum! I have had to use mine two or three times and with out it I would have been SOL! See links below for ROM and VID.
I do not take any responsibility if you brick your device or LOOSE your data, etc or if this doesn’t work on another US carrier, as I have only tested AT&T (friends’ phone) and T-Mobile (MINE). I will try to help if it’s messed up, but please back your stuff up!
(Not my video, but how to install)
ROM- EE version (I believe this to be UK ROM) (Again I PAID FOR THIS, but I am sharing it for FREE, as we should all have access to these OTA).
https://drive.google.com/file/d/12pcwgyWnrw_RfTZRfc78fHZ9VefS5VQL/view?usp=sharing
Lolinet is hosting the files now as well (free)
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
I know its only about a day but does everything still seem to be working? Camera, triggers, fingerprint scanner, notifications, etc. I'm on the china rom and have been searching for a fix pretty much everyday. It would be nice to have everything working on the phone
i cant download the file.i get acces denied
InvisibleAOD said:
I know its only about a day but does everything still seem to be working? Camera, triggers, fingerprint scanner, notifications, etc. I'm on the china rom and have been searching for a fix pretty much everyday. It would be nice to have everything working on the phone
Click to expand...
Click to collapse
Everything is working smoothly for me. I haven't had any issues that are show stoppers.
I did find it harder to change my network preferences, for cell service as I have to search for it vs going to advance setting. But again this is to change from NR/GSM/CMDA/GSM etc. most people leave this a lone but I move it around depending on the area and service I am in.
scrici19 said:
i cant download the file.i get acces denied
Click to expand...
Click to collapse
I shall
scrici19 said:
i cant download the file.i get acces denied
Click to expand...
Click to collapse
Working on it, I guess GOOGLE decided to block this. Working on it.
Zero11534 said:
Please read and DO AT YOUR OWN RISK
After searching everywhere and trying to get a clear answer on the Global ROM_ROW support for Android 11 on the Lenovo Legion Duel (one), all I could find was don't use the Chinese ROM as it has many issues. So, like any person told not to I tried it. Though it worked I had multiple issues with sensors and my cell service in the USA. I went back to GLOBAL ROM .332 which was the most stable for me but did lose my casting ability for playing my games to my TV. This is a deal breaker for me as I take my phone on the go and hook to friends and family's TV's for Steam, Emulation, etc and we use the casting, as this allows me to play my games. Note I also use it for Gamepass cast to the screen for friends to watch the game etc.
I finally found an Android 11 non China ROM, but it was an EE ROM on another site (which I had to pay for) but NO Global ROW ROM as installed on the phone when I purchased it. After backing up my data yet again, I tried to install this one (see link below for how to install). Once I installed and rebooted the Lenovo Legion L79031 v EE 12.5.251_ST rom, and set my cell APN, Turned the 5G to NSA-SA and networks preference (to NR-LTE-GDSM etc...) it began to function. After prox. 30 seconds after a reboot from changing the settings, I got a notification for an update (YES OTA). The update is for 12.5.320 which has notification fixes and bug fixes. Hopefully, this will be my last time having to flash the device! But I can confirm the EE rom for 11 does function on T-Mobile in the USA and works with out issue so far, has only been a short time for usage, but finally a solution for me.
Pros:
Android 11
Battery life improved
Smoother touch rate
OTA UPDATES
(Everything seems to function including cell and text messages on USA T-Mobile including the 5G NR)
Cameras work for everything even BARCODE readers and Mobile banking depo which was an issue before (at least for me). Pic snap faster but no real software updates from last build for controls as far as I can tell.
ZUI loads much faster.
Cons:
Lost all settings backups seems to cause issue when restoring so manually re-adding is the best solution.
APN setting and other settings might need to be redone, if installing from a back up or updating with OTA update.
Rebooting seems to take longer.
View attachment 5355159
As for what everyone really wants the links and how to install, I have linked to a video I send to others to use for installing the ROM, it is NOT my video, but the best one on YOUTUBE( I found recently); I had my 8 year old son help me a few weeks ago update a friends Duel and I let my son follow the vid and install the rom, OBV I did the downloads on the PC and setup the file location but he was able to follow the steps well to load the files to the phone, which is why I suggest to us it. The first time installing is scary! There is BIG BIG BIG pre-req beforehand, back up your phones drives as mentioned in other post on this forum! I have had to use mine two or three times and with out it I would have been SOL! See links below for ROM and VID.
I do not take any responsibility if you brick your device or LOOSE your data, etc or if this doesn’t work on another US carrier, as I have only tested AT&T (friends’ phone) and T-Mobile (MINE). I will try to help if it’s messed up, but please back your stuff up!
(Not my video, but how to install)
ROM- EE version (I believe this to be UK ROM) (Again I PAID FOR THIS, but I am sharing it for FREE, as we should all have access to these OTA).
https://drive.google.com/file/d/12pcwgyWnrw_RfTZRfc78fHZ9VefS5VQL/view?usp=sharing
Click to expand...
Click to collapse
scrici19 said:
i cant download the file.i get acces denied
Click to expand...
Click to collapse
This should be fixed, GOOGLE blocked it due to a bunch of attempts to hack into the account. Try the link again it should be view all, allowing everyone to download it, even without a google account. Try and let me know. Thanks.
Zero11534 said:
This should be fixed, GOOGLE blocked it due to a bunch of attempts to hack into the account. Try the link again it should be view all, allowing everyone to download it, even without a google account. Try and let me know. Thanks.
Click to expand...
Click to collapse
is working now.thanks
not working for me.after instalation the phone stay on logo for 1 min then is turning off.
scrici19 said:
not working for me.after instalation the phone stay on logo for 1 min then is turning off.
Click to expand...
Click to collapse
Did you install from a Global Rom and if so what version I installed from .332 as said with no issues. Spoke to someone else today on Facebook, and he was able to install and get it working as well. More than happy to help if I can.
I think that's the incompatible message
Get back to android 10 then flash the rom again
On .332 i get the incompatible hardware message.
You can fix that by flashing persist img
So i need to flash back the chinese rom,backup persist then install .332 and restore persist?
pikasus said:
You can fix that by flashing persist img
Click to expand...
Click to collapse
??
i managed to install this firmware.the only problem i have now is the camera not working.CANT CONNECT TO THE CAMERA
you dont exatly need the chinese rom just any working stable android 10 rom. flash rom then backup the persist and modem. then try android 11 again.
there is a guide here by mrgreapes
Incompatible Hardware with System ROW ROM 332
When I install the .332 global rom, when I start the device, I receive a message that says: the hardware is incompatible with the current system. Someone with a similar problem?
forum.xda-developers.com
persist fix the incompatible hardware message, camera and some sensor problem
modem fix no sim signal.
Hi i'm been looking for this good news for a long time ago. I have 3 questions. The first one, can I install the EE 12.5.251 row ROM directly with the qfil software, I mean I just exctracting the 251 ROM on a folder with the same name on the c unit and then run the qfil software?… The second one: I'm on CN ROM 12.5.225, so I wan't to know if there is any big chance to get the black screen as before when I tried to get back to the global? And the last one, the video on your post of how to change to global is broken can you fixed please?. Thank you very much for your time and patience. Greetings
I used 12.5.320 and I started to have service issues after about 3 months and the OS crashed, most stable version for me is still 12.0.332. I have not tried using the newest china ROM and thought about trying it
Please could you reupload the video cuase it's not available Now
Hi!
I received J8110 from Sony as a service exchange unit (they could not repair my other model). It came originally with Android 9 1317-9334_55.0.A.2.205 GLOBAL-A1. I have not unlocked it.
It never got any OTA update for this over 2 years old firmware, so I decided to flash it myself using flashtool. As I could not find exactly matching 1317-9334 on XperiCheck, I used 1318-3803 Android 10 "Internal Service Exchange Unit 55.1.A.9.127-R1B" firmware. It did flash correctly, and almost everything works - except both Netflix and HBO Max reboot the phone whenever I try to play any video. Moreover, the phone reboots itself randomly once a few hours, and I must say it is really irritating issue.
The last entries in Android logcat just before reboot look like this:
Code:
03-07 10:18:41.251 886 17948 D WVCdm : [license.cpp(355):PrepareKeyRequest] PrepareKeyRequest: nonce=3174971344
03-07 10:18:41.313 886 6842 I WVCdm : [cdm_engine.cpp(191):CloseSession] CdmEngine::CloseSession: sid10
I suspect it might be somehow related to Widevine keys. But the DRM info app shows everything is OK and L1 support is enabled (as in the attached screenshot).
I tried to flash also other firmware images - everything available for J8110 in XperiCheck (including 55.2.A.4.332), but the phone won't boot - "Your device is corrupt. It can't be trusted and will not boot.". I even tried flashing J8170, but that eneded up even worse, in recovery: "cannot load Android system". This 55.1.A.9.127-R1B (that reboots my phone on Netflix) is the only firmware I was able to boot.
My first question: is there any way to downgrade to this original, obsolete but working Android 9 1317-9334_55.0.A.2.205 GLOBAL-A1? I can't find it in XperiFirm.
And, of course - if you could point me on how to install the more recent Android versions that work I would be very grateful. I would prefer to leave the phone locked as I suspect some DRM issues with unlocking, but if that is the only way and it is confirmed working I can try it as well.
Service menu *#*#7378423#*#* "software info" of original and updated firmware attached.
Thanks for any help!
I forgot to mention that of course I tried clearing data and cache for Netflix app, as well as uninstalling and re-installing updates (can't fully uninstall the app as it was included in the firmware). I could fully reinstall HBO though, but fresh install did not help with the issue at all.
Did you tried the Firmware with version 205 on XperiFirm?
There is one called SA or ZA.
Get things into your PC and use newflasher by @munjeni. It will work if there is nothing wrong with hardware.
Thanks for the response.
I have tried the newflasher as well, but the results are exactly the same as for flashtool - "Your device is corrupt..." (or recovery error, depending on firmware). I don't think this is an issue with flashing itself, I did not notice any error in logs.
Yes, I have tried this 205 "Customized ZA" also - it does not boot, stops in recovery "Can't load Android system". I did not try to factory reset the data yet, as I really would prefer to keep my user data intact.
I have tried every single firmware available in XperiCheck for J8110, and only this 1318-3803 boots for me - but reboots my phone every hour or so and this is really annoying.
I have also asked XperiCheck maintainer to add my 1317-9334, but no response so far.
Plz provide the frimware that is working in your mobile i am facing the same problem my device stuck on sony logo i will be thankful to you brother