Be very careful doing this, you could brick your phone if you aren't - you have been warned.
Okay, so, us Idol 3 users in Canada are stuck waiting for Alcatel to have any updates blessed by our cell carrier (Bell/Virgin, Telus/Koodo) before we're "allowed" to get them. And as we all know, Canadian cell carriers aren't exactly prompt about this sort of thing. So what's an enterprising XDA user to do, then? Why, convert your device to a US model, of course!
Step 1: Install TWRP
That can be done with this thread here, courtesy of @DallasCZ
Step 2: Download the latest US firmware
That can be done by downloading this file here, courtesy of @famewolf
Step 3: Flashing
Okay, so first, BACK UP YOUR EXISTING FIRMWARE. Take a system image, or nandroid, as your choice may be. Be sure to back up the boot partition as well, in case you ever want to go back to stock Canadian firmware! Then, do the following:
Decompress the US firmware
Copy the decompressed 1970-01-22--16-43-23_LRX22G_release-keys folder into your TWRP/Backups/XXXXX/ folder on your External SD card or USB-OTG storage, where XXXXX is your device ID assigned by TWRP when you backed up your existing firmware - it is also the same as your device ID if you type 'adb devices' with your phone hooked up with USB debugging enabled for adb commands.
Wipe everything *but* External SD and USB-OTG in TWRP. (This entire wipe may not be needed, but as @KashRaman pointed out, if you don't at least wipe cache, you could have issues after flashing the new firmware)
DO NOT REBOOT - go back, and select Restore in TWRP. Pick the US firmware backup.
Flash *both* the boot and system image.
Reboot System. If your phone does the same as mine, it will seem to get stuck on the 'Alcatel/Smart Move' animation. Hold power until the phone turns off, then turn it back on. It should quickly go to 'Upgrading Android'.
You're done! Set up your device, and feel free to install SuperSU, remove bloatware (AVG? Ugh), etc.
I didn't even need to add APN info for Virgin Mobile, it already set up the Bell Canada APN - worked right away out of the box.
One comment to note - I do not know that a Canadian device converted to a US one can get OTA updates, as I believe Alcatel uses some sort of IMEI identification to see what OTA ought to be passed to a device, but I'm unable to confirm this. Of course, I'm personally fine with just manually updating when need be, but that's up to you to decide if you are as well.
AS ALWAYS, BE CAREFUL, DO THIS PROCESS AT YOUR OWN RISK
Don't forget to thank @DallasCZ and @famewolf for their posts/uploads making this possible!
To save you some pain you can more thank likely flash the system image and boot without wiping your /data.....if for some reason you ran into issues you'd still be able to go into factory recovery and do a reset which deletes data.
Also to anyone who actually uses AVG the pro version is free on amazon appstore today only.
Also you don't have to INSTALL twrp...you can opt to only boot into it using the instructions in the system image thread if you prefer to keep stock recovery.
If I had to bet I'd say you'll get the USA notifications but we will find out on next update.
famewolf said:
To save you some pain you can more thank likely flash the system image and boot without wiping your /data.....if for some reason you ran into issues you'd still be able to go into factory recovery and do a reset which deletes data.
...
Also you don't have to INSTALL twrp...you can opt to only boot into it using the instructions in the system image thread if you prefer to keep stock recovery.
Click to expand...
Click to collapse
Totally correct on the TWRP thing, though I prefer it to stock recovery, and updates work just fine with TWRP as well.
As for the not wiping - again, correct, I just come from the 'do a total wipe' school of flashing things, to avoid any possible weirdness
purple.epod said:
Be very careful doing this, you could brick your phone if you aren't - you have been warned.
Okay, so, us Idol 3 users in Canada are stuck waiting for Alcatel to have any updates blessed by our cell carrier (Bell/Virgin, Telus/Koodo) before we're "allowed" to get them. And as we all know, Canadian cell carriers aren't exactly prompt about this sort of thing. So what's an enterprising XDA user to do, then? Why, convert your device to a US model, of course!
Step 1: Install TWRP
That can be done with this thread here, courtesy of @DallasCZ
Step 2: Download the latest US firmware
That can be done by downloading this file here, courtesy of @famewolf
Step 3: Flashing
Okay, so first, BACK UP YOUR EXISTING FIRMWARE. Take a system image, or nandroid, as your choice may be. Be sure to back up the boot partition as well, in case you ever want to go back to stock Canadian firmware! Then, do the following:
Decompress the US firmware
Copy the decompressed 1970-01-22--16-43-23_LRX22G_release-keys folder into your TWRP/Backups/XXXXX/ folder on your External SD card or USB-OTG storage, where XXXXX is your device ID assigned by TWRP when you backed up your existing firmware.
Wipe everything *but* External SD and USB-OTG in TWRP. (This entire wipe may not be needed, but as @KashRaman pointed out, if you don't at least wipe cache, you could have issues after flashing the new firmware)
DO NOT REBOOT - go back, and select Restore in TWRP. Pick the US firmware backup.
Flash *both* the boot and system image.
Reboot System. If your phone does the same as mine, it will seem to get stuck on the 'Alcatel/Smart Move' animation. Hold power until the phone turns off, then turn it back on. It should quickly go to 'Upgrading Android'.
You're done! Set up your device, and feel free to install SuperSU, remove bloatware (AVG? Ugh), etc.
I didn't even need to add APN info for Virgin Mobile, it already set up the Bell Canada APN - worked right away out of the box.
One comment to note - I do not know that a Canadian device converted to a US one can get OTA updates, as I believe Alcatel uses some sort of IMEI identification to see what OTA ought to be passed to a device, but I'm unable to confirm this. Of course, I'm personally fine with just manually updating when need be, but that's up to you to decide if you are as well.
AS ALWAYS, BE CAREFUL, DO THIS PROCESS AT YOUR OWN RISK
Don't forget to thank @DallasCZ and @famewolf for their posts/uploads making this possible!
Click to expand...
Click to collapse
When restoring the UE40 firmware the first time you go into system update checker you need to delete the existing UE40 update as it kept it around...you should then be able to check updates as normal.
Manually update
At the end of your post, you say that you update manually.. where do you get your update ?
Manually update
At the end of your post, you say that you update manually.. where do you get your update ?
Click to expand...
Click to collapse
I mean that when the next update comes out, if I can't use the OTA update, I'll wait for someone to upload it here, and then I'll manually apply it. If you follow the directions in my post, you'll be totally up-to-date as of August 15th, 2015 - I'm referring to the next update, whenever that may be.
Thanks for the guide!
Was able to update my Canadian idol 3 without installing twrp
Just fastbooted into it and did a backup of my old CDN setup and restored with the file above the whole update process took about 15min
If **** hits the fan I can still restore back to the original CDN ROM with twrp and my backup.
Dt2w works every time now and chrome scrolling is vastly improved definately worth updating. I may flash back to Canadian system image when they finally release it
To anyone on stock Canadian firmware please post once an OTA is available (and what carrier you are on)
anyone else have lost LTE and get bad network speeds after converting? I had 60mbps with canadian firmware and now i get around 5mbps and lots of network drops.
jpfk said:
anyone else have lost LTE and get bad network speeds after converting? I had 60mbps with canadian firmware and now i get around 5mbps and lots of network drops.
Click to expand...
Click to collapse
I'm not in canada but I would think if more folks were experiencing issues like that they would have mentioned them here already. Did you do a factory reset and start clean or did you keep your previous data around after changing firmware? In this case I'd really recommend starting clean with the exception of using tools like Titanium Backup to backup all your user apps+ their data (or you can use Helium if you don't have root).
famewolf said:
I'm not in canada but I would think if more folks were experiencing issues like that they would have mentioned them here already. Did you do a factory reset and start clean or did you keep your previous data around after changing firmware? In this case I'd really recommend starting clean with the exception of using tools like Titanium Backup to backup all your user apps+ their data (or you can use Helium if you don't have root).
Click to expand...
Click to collapse
I had cleared the cache and did a factory reset only after i confirmed the flash of the US firmware was ok. (i have a really bad SD card which keeps unmounting and didnt want to risk being stuck with a non-functional device). In addition to the network problems i also still had the performance issues everyone mentionned was fixed in latest update. I just did a complete wipe and flashed the US again, now the performance is much much better but i still get only H+ with about 7mbps instead of LTE. But the good thing is the drops seems to have stopped.
jpfk said:
I had cleared the cache and did a factory reset only after i confirmed the flash of the US firmware was ok. (i have a really bad SD card which keeps unmounting and didnt want to risk being stuck with a non-functional device). In addition to the network problems i also still had the performance issues everyone mentionned was fixed in latest update. I just did a complete wipe and flashed the US again, now the performance is much much better but i still get only H+ with about 7mbps instead of LTE. But the good thing is the drops seems to have stopped.
Click to expand...
Click to collapse
you probably tried this but... check that the APN didn't get changed/reset from when lte was working.
That was actually the problem, i did not realize it was a different APN for LTE so it looked normal when I first checked. Thank you very much
Has anyone gotten the Canadian stagefright update pushed to their phone yet?
doesn't work for me!
purple.epod said:
Be very careful doing this, you could brick your phone if you aren't - you have been warned.
Okay, so, us Idol 3 users in Canada are stuck waiting for Alcatel to have any updates blessed by our cell carrier (Bell/Virgin, Telus/Koodo) before we're "allowed" to get them. And as we all know, Canadian cell carriers aren't exactly prompt about this sort of thing. So what's an enterprising XDA user to do, then? Why, convert your device to a US model, of course!
Step 1: Install TWRP
That can be done with this thread here, courtesy of @DallasCZ
Step 2: Download the latest US firmware
That can be done by downloading this file here, courtesy of @famewolf
Step 3: Flashing
Okay, so first, BACK UP YOUR EXISTING FIRMWARE. Take a system image, or nandroid, as your choice may be. Be sure to back up the boot partition as well, in case you ever want to go back to stock Canadian firmware! Then, do the following:
Decompress the US firmware
Copy the decompressed 1970-01-22--16-43-23_LRX22G_release-keys folder into your TWRP/Backups/XXXXX/ folder on your External SD card or USB-OTG storage, where XXXXX is your device ID assigned by TWRP when you backed up your existing firmware - it is also the same as your device ID if you type 'adb devices' with your phone hooked up with USB debugging enabled for adb commands.
Wipe everything *but* External SD and USB-OTG in TWRP. (This entire wipe may not be needed, but as @KashRaman pointed out, if you don't at least wipe cache, you could have issues after flashing the new firmware)
DO NOT REBOOT - go back, and select Restore in TWRP. Pick the US firmware backup.
Flash *both* the boot and system image.
Reboot System. If your phone does the same as mine, it will seem to get stuck on the 'Alcatel/Smart Move' animation. Hold power until the phone turns off, then turn it back on. It should quickly go to 'Upgrading Android'.
You're done! Set up your device, and feel free to install SuperSU, remove bloatware (AVG? Ugh), etc.
I didn't even need to add APN info for Virgin Mobile, it already set up the Bell Canada APN - worked right away out of the box.
One comment to note - I do not know that a Canadian device converted to a US one can get OTA updates, as I believe Alcatel uses some sort of IMEI identification to see what OTA ought to be passed to a device, but I'm unable to confirm this. Of course, I'm personally fine with just manually updating when need be, but that's up to you to decide if you are as well.
AS ALWAYS, BE CAREFUL, DO THIS PROCESS AT YOUR OWN RISK
Don't forget to thank @DallasCZ and @famewolf for their posts/uploads making this possible!
Click to expand...
Click to collapse
i downloaded the zip restore file for my phone (Model: 6045Y(Europe) Firmware: 5.0.2-010 06) from this thread http://forum.xda-developers.com/idol...dates-t3163745
I also have the twrp-2.8.7.0-idol3 installed on my phone.
I also followed this thread
to find the way to install that ROM, without success. i also installed the root from the zip file in the twrp, but again without success!! but when i open from the twrp the directory TWRP/Backups/XXXXX/ and i copy the .win and the .win.md5 files the phone doesn't see the when i click restore
i downloaded the zip restore file for my phone (Model: 6045Y(Europe) Firmware: 5.0.2-010 06) from this thread
Click to expand...
Click to collapse
This guide is for converting a Canadian 6045i to a US 6045i - both are identical models with simply slightly different software. It won't work with a European 'Y' model like you said you have.
punkal said:
i downloaded the zip restore file for my phone (Model: 6045Y(Europe) Firmware: 5.0.2-010 06) from this thread http://forum.xda-developers.com/idol...dates-t3163745
I also have the twrp-2.8.7.0-idol3 installed on my phone.
I also followed this thread
to find the way to install that ROM, without success. i also installed the root from the zip file in the twrp, but again without success!! but when i open from the twrp the directory TWRP/Backups/XXXXX/ and i copy the .win and the .win.md5 files the phone doesn't see the when i click restore
Click to expand...
Click to collapse
Step 1) Make a backup on the device so it creates the directory path you need.
Step 2) Take the time datestamp folder from the backup you have and put it in the folder that has the other time datestamp folders. It's not a complicated process. Installing the "root" from the zip file does you no good because the time datestamp folders need to be under a folder with your device id (ie what shows up when you do adb devices).
While the restore process IS the same your questions should be asked in the system image thread if you don't have a 6045i.
According to @petrov.0 it's better for you to install the official 10 06 update (or his modified one in the system image thread) as it updates files in SEVERAL partitions other than system and boot. Again discussion needs to be there.
Apologies to @purple.epod. This will hopefully redirect folks back to the system image thread. I have a line that states to follow your restore tutorial but use their own backup but did not intend for them to be asking questions HERE.
purple.epod said:
This guide is for converting a Canadian 6045i to a US 6045i - both are identical models with simply slightly different software. It won't work with a European 'Y' model like you said you have.
Click to expand...
Click to collapse
Now i understand why it doesn't work. And where can i find the rom for my as i have everything wiped? do you know i only found ROM Arde-Dev-Team-v1_5.0.2 but it doesn't work!
---------- Post added at 11:44 AM ---------- Previous post was at 11:40 AM ----------
famewolf said:
Step 1) Make a backup on the device so it creates the directory path you need.
Apologies to @purple.epod. This will hopefully redirect folks back to the system image thread. I have a line that states to follow your restore tutorial but use their own backup but did not intend for them to be asking questions HERE.
Click to expand...
Click to collapse
Unfortunately i can bakup anything as i have wiped everything on the phone!:crying:
I know i'm really stupid, but i do that as it was a step as a process of installing a new ROM as mine was corrupted!:crying:
punkal said:
Now i understand why it doesn't work. And where can i find the rom for my as i have everything wiped? do you know i only found ROM Arde-Dev-Team-v1_5.0.2 but it doesn't work!
---------- Post added at 11:44 AM ---------- Previous post was at 11:40 AM ----------
Unfortunately i can bakup anything as i have wiped everything on the phone!:crying:
I know i'm really stupid, but i do that as it was a step as a process of installing a new ROM as mine was corrupted!:crying:
Click to expand...
Click to collapse
Why are you posting this HERE when even the message you quoted states questions should be asked in the system image thread?
famewolf said:
Why are you posting this HERE when even the message you quoted states questions should be asked in the system image thread?
Click to expand...
Click to collapse
Really sorry!
i've been taken by terror and panic.!
Related
HellllOOooOoOo!!
Ok, here goes. First off, I searched. A lot. There is so much conflicting information and opinions out there. I hate to annoy you pros with noob-ness but I have to. Sorry!
Here is the quick version:
Friend gave me an Atrix 4G. He is big on experimenting, rooting, custom ROMs and all that. I am not. At all. I want to use it on t-mobile. I DO get a signal and can text. MMS doesn't work and motoblur wont let me set up an account. This results in no access to email other then Gmail. Basically, I want to bring the phone back to its original (or close as possible) state. Hopefully, that will solve some of my issues.
-Android Version
2.3.4
-Unlocked
-Rooted
-Build Number
olympus_hktw-userdebug 2.3.4 4.5.2A-5_OLH-3110614 test-keys
-Clockwork recovery mod installed (if that matters)
I am not THAT tech savvy but can follow instructions well. I've already been messing around but cant seem to get RSD Lite to actually flash properly. I dont care for customs ROMS, hacking and tinkering. I just want this phone to work as well as possible.
Can anyone give me some personal assistance? Please? Step by step would be great. I'll be refreshing this page often in hopes of responses.
Vul said:
HellllOOooOoOo!!
Ok, here goes. First off, I searched. A lot. There is so much conflicting information and opinions out there. I hate to annoy you pros with noob-ness but I have to. Sorry!
Here is the quick version:
Friend gave me an Atrix 4G. He is big on experimenting, rooting, custom ROMs and all that. I am not. At all. I want to use it on t-mobile. I DO get a signal and can text. MMS doesn't work and motoblur wont let me set up an account. This results in no access to email other then Gmail. Basically, I want to bring the phone back to its original (or close as possible) state. Hopefully, that will solve some of my issues.
-Android Version
2.3.4
-Unlocked
-Rooted
-Build Number
olympus_hktw-userdebug 2.3.4 4.5.2A-5_OLH-3110614 test-keys
-Clockwork recovery mod installed (if that matters)
I am not THAT tech savvy but can follow instructions well. I've already been messing around but cant seem to get RSD Lite to actually flash properly. I dont care for customs ROMS, hacking and tinkering. I just want this phone to work as well as possible.
Can anyone give me some personal assistance? Please? Step by step would be great. I'll be refreshing this page often in hopes of responses.
Click to expand...
Click to collapse
It sounds like you need to set up a proper T-Mobile APN. (you have a T-Mobile SIM card currently installed?)
If you can get on Wifi, try to go the the Play store and download Tweakker or other APN utilities that enter the APN for your based on your carrier.
co.ag.2005 said:
It sounds like you need to set up a proper T-Mobile APN. (you have a T-Mobile SIM card currently installed?)
Click to expand...
Click to collapse
Yes. I have a t-mobile SIM card installed. My concern is what the previous owner may have done and whatever ROM is loaded on this phone. Can I somehow bring it back to stock or get a super stable, close to stock as possible ROM first and then start addressing the quirks I have?
Is this an AT&T branded phone? I'm not sure if getting back to stock is necessary, and if you do get back to stock, you might be SIM locked to AT&T (I could be wrong however). If you want to flash a fresh, stock ROM but still be rooted, SIM unlocked, etc., find a 2.3.6 Fruitcake in this forum or try NottachTrix 4G ROM.
however, I'd wait till others weighed in before doing anything. Honestly, I'd try getting your APN (download Tweakker app and walk through the steps) going now and if that solves your issue, your ROM might be working fine for you... my $0.02
oh, and welcome to XDA!
Vul said:
Yes. I have a t-mobile SIM card installed. My concern is what the previous owner may have done and whatever ROM is loaded on this phone. Can I somehow bring it back to stock or get a super stable, close to stock as possible ROM first and then start addressing the quirks I have?
Click to expand...
Click to collapse
1. Download the fruitcake .zip you want (webtop also, if you want it)
2. Do a full wipe with fastboot (search if you're unsure how to)
3. Boot into recovery and flash the .zip you downloaded from step 1
4. Reboot and you're done
This will put you back to stock. I can't remember if fruitcakes are pre-rooted, but if not you can easily root again.
Alright, now we're getting somewhere.
co.ag
The phone itself says "unlocked" upon startup. I got the network unlock code direct from AT&T because at first the phone wouldn't even recognize my t-mo SIM. Phone is now network unlocked.
Ghost
gonna search now for fruitcake and see what thats all about. Do I need webtop?
Then going to get fastboot. Guess I dont need RSD Lite anymore?
Im doing this because I dont know what the previous owner has done and would like a clean slate. Kind of like changing the oil on a used car you buy, even if the PO says it was done.
Ok so,
I found fastboot with recovery tool and the .exe files within the ZIP dont do anything.
The fruitcake ZIP file I downloaded according to your link, I'm not sure what to do with that. lol
Help?
**am I supposed to be saving these files to the phone itself? If so, where? Internal storage? SD card?
Vul said:
Alright, now we're getting somewhere.
co.ag
The phone itself says "unlocked" upon startup. I got the network unlock code direct from AT&T because at first the phone wouldn't even recognize my t-mo SIM. Phone is now network unlocked.
Ghost
gonna search now for fruitcake and see what thats all about. Do I need webtop?
Then going to get fastboot. Guess I dont need RSD Lite anymore?
Im doing this because I dont know what the previous owner has done and would like a clean slate. Kind of like changing the oil on a used car you buy, even if the PO says it was done.
Click to expand...
Click to collapse
that "unlocked" bit on start up means your bootloader is unlocked, doesn't have anything to do with the SIM card. All this means is that you can flash a ROM since the phone is "unlocked"
Vul said:
Ok so,
I found fastboot with recovery tool and the .exe files within the ZIP dont do anything.
The fruitcake ZIP file I downloaded according to your link, I'm not sure what to do with that. lol
Help?
**am I supposed to be saving these files to the phone itself? If so, where? Internal storage? SD card?
Click to expand...
Click to collapse
the fruitcake .zip goes on your internal sdcard. BUT, before you start doing anything, please go through the stickied threads in this section and read up on how to flash ROMs to your phone. This will include how to wipe your phone using the fastboot commands and how to flash the fruitcake .zip.
start here, read this post
http://forum.xda-developers.com/showthread.php?t=1154600
then follow guides to
"HOW TO INSTALL FRUITCAKES ON 2.3.4 (GREAT SBF/RSD ALTERNATIVE!!!)"
and
"ROMs & Kernels:
FYI:
Before installing any ROM or Kernel I suggest you do the following to help prevent error, boot-loops, etc. Also, it's a good idea to flash a new ROM or Kernel on a fully charged device:
1) Download which ever ROM or Kernel you plan on flashing and have the .zip on your device ready to flash.
2) Backup your apps (not system data), contacts, etc. Also consider making a CWM backup of your device, just in case.
3) Boot into CWM Recovery
4) Wipe Dalvik Cache (under advanced in CWM)
5) Wipe Cache Partition
6) Wipe data/factory reset
6a) If you're using ROM Manager/CWM you will need to reboot the device after step 5, and upon reboot enter fastboot mode and enter the command: "fastboot -w" or "moto-fastboot -w" if you prefer using moto-fastboot. Then type "fastboot reboot" and upon reboot make sure to enter Android Recovery again, so that you can flash the ROM/Kernel.
7) Install .zip from SD Card (choose the .zip you wish to install)
8) If you installing a radio, theme, kernel, etc. on top of a ROM, I would suggest redoing the whole wipe process again between flashes.
9) Reboot the Device
- If you get a boot loop, try entering Android recovery and re-wiping the chace and data, and perhaps try reflashing the ROM/Kernel. Or if you made a CWM backup, you can always restore that."
Vul said:
Ok so,
I found fastboot with recovery tool and the .exe files within the ZIP dont do anything.
The fruitcake ZIP file I downloaded according to your link, I'm not sure what to do with that. lol
Help?
Click to expand...
Click to collapse
Ok, sorry I wasn't that detailed in my other post and assumed you were on your phone (my bad). First things first, read the N00b guide.
1. Anytime you download CWM .zips, put them on the root of your phone's sdcard. You'll need them there in order access them from recovery. ( note: sdcard=internal sd card & sdcard-ext=external sd card for blur ROMS )
2. Fastboot commands are executed from the command line. Open a command prompt and navigate to the directory containing fastboot.exe in order to use it. The Noob guide should have links to all the fastboot commands you'll need.
3. With the Atrix's unlocked BL, holding Volume Down when turning the phone on will bring up a series of bootmodes to choose from. This is how you get into fastboot, recovery, RSD, etc. Navigate through the choices with Volume Down. Select one by pressing Volume Up. You should only ever really need Fastboot and Android Recovery.
4. CWM is used to flash .zips (ROMS, kernels, apps) while in recovery mode. Use romracer's to make things easier on yourself later.
Read through the N00b guide and this will all make perfect sense.
I have no idea what Im doing. I think because this phone has been tampered with so much already, it's making it extra tough to work with.
I managed to install CM7. Its the only ZIP file that actually seemed to take. I still dont understand fastboot , in the sense that I don;t know when Im supposed to see a command prompt. Also, now, CM7 is asking me to upgrade to premium and I have to pay for it. There doesnt seem to be a free way of installing it so that I can sync all my info through my google account. Ugh. Im not cut out for this but Ive been screwing with this literally since 730 this morning.
**CM7 with google apps packet installed. So far, so good. Im happy with this considering its pretty close to stock gingerbread, kinda like my G2. Now, Im hopefully done messing around. Would be nice if they release a solution for the fingerprint scanner or if I can get my gmail to auto sync but at least I can stop obsessing for the time being. Great help guys, thanks so much!!!!
I need help! I need a stock, unmodified recovery partition image.
Anyone here with a vzw tab who DOES NOT yet have CWM installed?.
PLEASE contact me.
Thanks!
electron73 said:
I need help! I need a stock, unmodified recovery partition image.
Anyone here with a vzw tab who DOES NOT yet have CWM installed?.
PLEASE contact me.
Thanks!
Click to expand...
Click to collapse
I have one that hasn't been moded but have no idea how to get you what you want. PM me if you know how to download and send to you and I'll do my best to help.
I'll check my laptop at home tonight. I believe I kept my heimdall backup before flashing cwm
Sent from my DROID BIONIC using Tapatalk 2
Just checked, mightve deleted it. Sorry man
aximtreo said:
I have one that hasn't been moded but have no idea how to get you what you want. PM me if you know how to download and send to you and I'll do my best to help.
Click to expand...
Click to collapse
Oh that would be awesome! Are you rooted? Let me find the commands in the meantime, I read somewhere it's a simple one command in terminal to extract the recovery partition into a file on sd card...
WHAT AN ORDEAL !!!!
But in the end: SUCCESS!
I managed to get my tab updated with the Verizon OTA update.
The problem is definitely CWM !!! A rude awakening is in store for everyone with the P6800 CWM installed, because it a) fails to verify the checksum of OTA files correctly on the i815, b) it thinks the tablet is a P6800, so the OTA file fails to run if it assert checks for "SCH-i815" hardware AND lastly c) modem updates don't work because the device /dev/cdma_update doesn't exist, so the modem.bin firmware_update call fails !!!
In short, I had to fumble the OTA file apart and do the update manually in two runs:
First file, kick the checksum, hardware check and modem update out, then manually run the ZIP through CWM. The zip subsequently (LUCKILY) updated the stock recovery and overwrote CWM with a new fresh stock recovery.
Second file had everything kicked out BUT the modem udpate and LTE patch, so with the STOCK recovery this file ran through just fine, updated the modem and then applied the LTE delta patch.
Phew!!!
Of course I had to manually restore root after the update, had backed up with voodoo, auto restore failed, so terminal and hacking it was...
Now I have the tab running on clean stock FD01, baseband and LTE FD01, rooted and stock recovery.
No more CWM, no more "hacking" with the ROM until some dev finally releases a "correct" CWM and at least ANY factory ODIN image is available to bring the tab back to stock if needed!!!
Kinda sick of the non-support for this tab. So much going on for the Galaxy Note and pretty much every other device. I'm starting to regret having bought this "special" Verizon version
Awesome find and great to know for whenever ics does come out. Could you please post the recovery img you got?
Sent from my DROID BIONIC using Tapatalk 2
OK after getting so many responses I decided to just post everything here in hopes that it will help others, too:
All files are here:
http://www.mywo.org:88/XDA/sch-i815/index.php
Step by step procedure to update the Verizon Tab from ..FA02 to ..FD01 build IF YOU ARE stuck with CWM installed on your tab and the original OTA fails with errors:
Upload the SCH-I815_FA02c_To_FD01.1.zip to the INTERNAL(!) SD card. This is important because CWM contains a bug that will only allow you to install from ZIPs stored on the INTERNAL SD storage.
Upload the SCH-I815_FA02c_To_FD01.2.zip to the EXTERNAL(!) (micro SD) card. This is important, because after the factory recovery is restored, it will correctly (and only) look for ZIPs on the EXTERNAL card.
Best way just copy both files to both locations
Fire up CWM and do "install from ZIP" and select SCH-I815_FA02c_To_FD01.1.zip
It should run (takes a while) and eventually tell you all is done. BOOT the tab. It should boot fine but in system it will show the new Android build FD01 but the baseband (radio) will still be the "old" one.
Now press and hold power and vol up again until you see the default Samsung recovery menu. Choose install from ZIP and select SCH-I815_FA02c_To_FD01.2.zip. This will now upgrade the baseband only. When done, reboot and enjoy being back on the "factory upgrade path" with the tab.
I hope someone more savvy than me can "fix" CWM to work properly with VZW tabs (accept the checksum, not fail the check for "SCH-i815" and provide the correct /dev file links for radio upgrades). Until then, I recommend just leaving the tab as-is and not tinkering with the ROM. Not that there is any custom ROM available anyway :-(
I also pulled the NEW factory recovery image FD01_recovery.img with the following command:
dd if=/dev/block/mmcblk0p6 of=/sdcard/FD01_recovery.img bs=4096
So in case anyone with a botched recovery wants to restore factory (Samsung 3e) recovery. This was actually the reason I had to go through all this... There is NO factory recovery image ANYWHERE to be found. I can't believe that I should be the first one ever to post one?? Anyway, hope it will help
I'm still quite new here, so I do really appreciate every click on that "thanks" button
P.S. for tinkerers and devs I also uploaded the original, untouched OTA file (0559c0e4e08e.update_SCH-I815_FA02c_To_FD01.bin) as it came from Samsung or Verizon or whatever and ended up in the /cache partition.
THANK YOU!
Electron,
You sir, are a BOSS! Thank you so very much for doing the work, and sharing it. You just made things one hell of a lot easier on me, and anyone else that follows.
Regards,
-Rob
Also want to say thanks. You rock, dude. I wouldn't have known how to revert **** on my own.
Also, I feel like we need a sticky or something for sch-i815 owners to go to for device specific stuffs, especially since there is little knowledge/info out for this device.
Sent from my Galaxy Nexus using xda premium
hmm i only ever installed ROM manager ... but i did root it ... problem is ... now i don't have a CWM recovery to flash the file ... any ideas?
phigmeta said:
hmm i only ever installed ROM manager ... but i did root it ... problem is ... now i don't have a CWM recovery to flash the file ... any ideas?
Click to expand...
Click to collapse
You're in luck! You don't need to go through the whole ordeal because you do NOT have CWM! You can just update the regular intended way. Go into settings, about phone and then click check for system updates. If it presents you the OTA update, just do it the regular way.
My complicated "hack" is only necessary if you DO HAVE CWM installed.
Im sorry I did not explain well what my issue is.
I do not have CWM installed, however i did delete a few appilcations using titanium backup. This causes updates to not take. I would really like to just take it back to factory and start over (this time with less stupidity on my part)
I of course would assume that once its at factory i can then install updates again.
Right now when i try i get the "!" droid sign and a reboot
phigmeta said:
Im sorry I did not explain well what my issue is.
I do not have CWM installed, however i did delete a few appilcations using titanium backup. This causes updates to not take. I would really like to just take it back to factory and start over (this time with less stupidity on my part)
I of course would assume that once its at factory i can then install updates again.
Right now when i try i get the "!" droid sign and a reboot
Click to expand...
Click to collapse
Hey
OK unless someone can tell us how to "make" an ODIN flashable ROM for you, here is what I would do (and please don't get scared because it sounds a bit convoluted).
First, you need to be rooted. This is obviously the case.
IMPORTANT since you don't have CWM installed yet, SAVE your factory restore.img before proceeding, this saves you a lot of hassle later!
Open the android terminal, type su (accept the prompt) and then type (or copy/paste)
dd if=/dev/block/mmcblk0p6 of=/mnt/sdcard/factory_recovery.img bs=4096
Check that you have a "factory_recovery.img" file on your sd card now it should be about 8M big.
Now you're safe to install CWM from the forum, look for the other thread(s) where this is being discussed and follow the instructions for the P6800 "international" version with 3G. CWM Thread here:
http://forum.xda-developers.com/showthread.php?t=1613638&highlight=cwm&page=3
Then (thanks to nicduim!) there is a full factory (rooted) CWM image floating around on the forums here:
http://forum.xda-developers.com/showthread.php?t=1613638&page=6
Which I used to restore my tab to "almost factory" with the missing bloat apps back in place.
I have a copy on my server here: http://ww.mywo.org:88/XDA/sch-i815/ it's the "2012-05-06.22.48.58.ZIP"
unzip that and put the contents on your INTERNAL SD card in the folder clockwordmod. So on your internal SD you should have /clockworkmod/2012-05-06.22.48.58 and inside there the files boot.img, recovery.img etc.
Use CWM recovery to restore this backup. If you never used CWM before. Press power button and volume up and hold both until you see the menu screen with text. You can go up/down with the volume buttons (go slow, it's very laggy) and with the power button you "select" an option. Select the "restore from backup" option and point it to the only folder being offered, the 2012-05-06.22.48.58.
The restore takes a while, then reboot the tab. Now you're back to stock! Last thing you need to do is get rid of CWM again because in the end it's still a bit buggy and will prevent the OTA update from running properly.
Since you luckily have a backup of the factory recovery in form of that factory_recovery.img file, just install and open terminal again, type su and then type (or copy)
dd if=/mnt/sdcard/factory_recovery.img of=/dev/block/mmcblk0p6 bs=4096
This overwrites CWM with your original Samsung Android recovery.
Now you just reboot as usual, connect to the internet and wait until the popup message shows up that a system update is ready, accept it and enjoy
If you don't want to wait for the automatic OTA, you can also stop before killing CWM and use my convoluted 2-step manual update which will get you to the exact same condition as the official OTA.
Hope all this makes sense
I was already on stock FD01 when I tried installing CWM for the P6800 that's floating around here somewhere. Odin said it was a success, but it looks like it didn't take. I've done it a few times, but still ended up w/ the stock recovery. However, after reading through your thread, I do not see a /dev/cdma_update in my I815 either. Is it possible that my attempt to install CWM (although unsuccessful) wiped out this file, among others?
Right now, I'm still at stock FD01 (rooted) and everything seems to be working. When I tried doing an OTA update, it just tells me that I have the latest update and no newer update is available.
One other thing, if I have to, I only have the stock recovery right now since CWM didn't take, can I simply flash both zip's using the Samsung stock recovery to put everything back in stock?
SCH-I815_FA02c_To_FD01.1.zip
SCH-I815_FA02c_To_FD01.2.zip
AlpineMan said:
I was already on stock FD01 when I tried installing CWM for the P6800 that's floating around here somewhere. Odin said it was a success, but it looks like it didn't take. I've done it a few times, but still ended up w/ the stock recovery. However, after reading through your thread, I do not see a /dev/cdma_update in my I815 either. Is it possible that my attempt to install CWM (although unsuccessful) wiped out this file, among others?
Right now, I'm still at stock FD01 (rooted) and everything seems to be working. When I tried doing an OTA update, it just tells me that I have the latest update and no newer update is available.
One other thing, if I have to, I only have the stock recovery right now since CWM didn't take, can I simply flash both zip's using the Samsung stock recovery to put everything back in stock?
SCH-I815_FA02c_To_FD01.1.zip
SCH-I815_FA02c_To_FD01.2.zip
Click to expand...
Click to collapse
Oh wait, so you are saying that in "About device" your Android is 3.2
Baseband i815.04 V.FD01 I815FD01
and your Build number is already at HTJ85B.I815FD01.SCH-I815.I815FD01 ?
That would mean you are already updated. In this case, it should be pretty easy to fix your problem. Which apps did you delete with Titanium? I can back them up from my system and make them available for you. All you'd need to do is drop the backup files into your Titanium backups folder and then fire up titanium and restore them!
The /dev/cdma_update node is only required WITHIN CWM recovery, so that is nothing for you to worry about. The zip files above won't help you because they are incremental updates requiring your system to be at FA02, not FD01 !
Yes... I'm already in the latest update. I already backed up the bloatware using Titanium Backup before uninstalling. So I just need to restore them back in order to receive and apply OTA updates in the future?
Sent from my SPH-D710 using Xparent ICS Blue Tapatalk 2
Please Help
Hi. I'm rooted and removed all sorts of bloatware with Titanium. I did this a long time ago and did not back anything up because I'm used to running hardware with custom ROMs available, and not relying on OTA updates.
Since there aren't any custom ROMs for the i815, I'd like to get ready for the upcoming ICS update. To do so, I want to get FD01 loaded onto my device, but I can't update because I've apparently removed too much of the required bloatware.
Does anyone know WHAT pieces of bloatware I'd need to reinstall in order for the OTA update to apply? I'd assume I can restore them and then apply the update and re-root.
If anyone can help pinpoint what missing APKs might help, I'll give them a shot. And, to the extent I figure anything out, I'll repost here in the hopes that it helps someone else.
electron,
Your instructions worked ... thank you so much
@jkrell... the failed attempt at installing the update should return an error message(s). You just have to read through them until you find the culprit(s). Apparently I uninstalled a few odexed files that were needed. I couldn't update until i hunted them down and restored them.
I guess we all jumped at the opportunity to install the cwm recovery image, that we didn't even think about cmda updates....ooops. So far i had to do a complete factory restore after the update. I was getting soft bricked to the point where I had no choice. Good thing I sent all titanium backups to actual sd card, i was able to salvage 97% f my data..... with the exception of a few downloads i forgot to move.
Gamecih doesn't work anymore (either version). No more automative data hacks I'm not sure what's going on. I uninstalled adfree..used titanium backup to uninstall both versions and reinstalled both several times. Oh well.
It really sucks not having nandroid backups but it's not worth the trouble of having to do this everytime an OTA modem update gets pushed to my tab. Needless to say, I won't be odining the cwm based recovery image again.
I'm with the O.P. I wish i hadn't wasted my money on this tab. No true cwm for this tab, so no dev will ever waste thier time with this tab. The sch i815 will soon be forgotten about and some other tablet will be all the hype before summer ends....that's just how it is. 21 months left on my contract.... [email protected]#k my life. Lol
Thanks Smitty.
When I try to update, I just see the "!" logo and then the device reboots. Is there a log file somewhere I can look at to see what the errors are?
I hear ya on the gloom and doom, but this device has only been out for just over 3 months now. I'd expect a recovery and some custom ROMs to come eventually. I doubt I'll go the custom ROM route unless CyanogenMod is supported, because I have no complaints about the tablet's performance thus far. It's speedy, smooth and the battery lasts forever.
In my book, this is a great tablet and I'm satisfied with the purchase.
I just successfully downgraded from COD6 back to NK4 in order to alleviate concerns that downgrading back to Kit-Kat was going to be an issue. Reference post found: HERE. I am outlining the method I used to downgrade below, but this can also be a guide on how to upgrade to later firmwares.
I don't recommend trying to downgrade past NK4 and only downgrade if your dev says you need to! downgrading is risky and can brick your device! You've been warned!
Downgrade to NK4 or Upgrade to COD6
1.) Download Odin v3.09
2.) Download full Odin NK4 (Found HERE) or COD6 found, almost everywhere
3.) Unzip the file and there should be a file called "N910TUVU1ANK4_N910TTMB1ANK4_N910TUVU1ANK4_HOME.tar.md5" or your COD6 tar called, "N910TUVU1COD6_N910TTMB1COD6_N910TUVU1COD6_HOME.tar.md5"
4.) Open Odin v3.09 and click the button labeled "AP" and locate the tar file you unzipped
5.) Let it load, it will freeze for some time while checking the MD5 and then be ready to go
6.) Turn off your phone completely; after it is powered off hold vol down+ home + power until you see a warning message
7.) Hit Volume up to continue
8.) Plug in your device and and the it should light up blue under "ID:COM" and say something like "COM:1"
9.) Check to make sure your tar is loaded into the AP slot.
10.) Ensure that they only two boxes that are checked are: "Auto Reboot" and "F. Reset Time"
SHOULD LOOK LIKE THIS PHOTO: http://cdn.droidviews.com/wp-content/uploads/2013/05/galaxy-s4-odin-flash.jpg
11.) If you've verified that your Odin looks like the picture then click "Start" and be patient
*****************************************************************************************************************************
***If Downgrading You MUST wipe USER DATA following the steps below or your phone will boot loop on restart!***
***If Upgrading I Strongly Suggest wiping USER DATA to avoid potential issues from upgrading!***
*****************************************************************************************************************************
12.) Wipe User Data as outlined below by booting into recovery as soon as the download completes by holding power + volume up + home until it says, "Recovery booting" in blue in the upper left corner.
13.) After doing the factory reset and rebooting it will you can setup your phone like normal
These are the same steps if you want to upgrade with Odin, you just use the full tar of the upgraded firmware (COD6 in our case)
To Wipe User Data
1.) After you've clicked start and the file completely loads on your phone it will reboot and immediately enter recovery
2.) It will show and Android and a blue bar scrolling across setting up your system. It will reboot again after this
3.) As soon as the screen turns black hold vol up+ home + power to enter recovery again
4.) It will boot to the Android again and you should see THIS before the menu loads
5.) Scroll down to "factory reset/data wipe" with the Vol Down button and then hit the power button to select it
6.) Scroll down again and hit "Yes" so that it completes
7.) After it is done reboot and allow your phone to boot normally
8.) Setup your phone like normal
Done!
I vote for this to be a "Sticky".
Good job :good:
Thank you, I've been with 5.0.1 for the day and the battery was better on 4.4 and it looked better. I was going to try as soon as I got home but now I know.
I was googling how to downgrade and ran in to this. A lot of report saying it worked. I'm surprised this is possible with Odin. Thanks for the additional confirmation.
Just wanted to add. Downgrading to NK4 will require a factory reset, otherwise you go into a boot loop.
aznmode said:
Just wanted to add. Downgrading to NK4 will require a factory reset, otherwise you go into a boot loop.
Click to expand...
Click to collapse
I know it was a long time ago when you posted this, but it just now sank in that boot loop = bad
I will update the OP, thanks for pointing this out :good:
Makes no sense. It says must wipe user data....why on earth would you need to wipe / factory reset just to UPGRADE to COD6?
Guide needs proper writing...
CtJackHarkness said:
Makes no sense. It says must wipe user data....why on earth would you need to wipe / factory reset just to UPGRADE to COD6?
Guide needs proper writing...
Click to expand...
Click to collapse
Because doing an Odin upgrade or downgrade on your device does not wipe the data partition which is necessary when changing a letter versions of Android. For example, let's say you are going from Kit-Kat to Lollipop or perhaps Lollipop to Kit-Kat in a way similar to that presented in this "How to".
However, I get that new members need help sometimes so let me help you research your criticism.
Welcome to XDA.
Forgive my ignorance, but I am curious. When upgrading to a new letter version via OTA or a program like Kies, there is no factory reset done by default. The fact that a factory reset solved problems for many this go around aside, why is it a must when using Odin? I have upgraded ma few devices over the years to new letter versions without resetting so I am just trying to get a better understanding.
KingBeef said:
Forgive my ignorance, but I am curious. When upgrading to a new letter version via OTA or a program like Kies, there is no factory reset done by default. The fact that a factory reset solved problems for many this go around aside, why is it a must when using Odin? I have upgraded ma few devices over the years to new letter versions without resetting so I am just trying to get a better understanding.
Click to expand...
Click to collapse
The reason OTA and Kies don't do the reset themselves is because they aren't capable of backing up the data you've accumulated on your phone since you've owned it. The average user only get an icon in the upper left-hand corner that tells them to update and they do it because T-Mobile says so. Imagine that same user installed the update and then they were looking at the Lollipop welcome screen like they had just taken the device out of the box. It would lead to an outcry from consumers because they lost months of data from the upgrade. However, we here on XDA are not average users and some of us know exactly what happens during these updates. You probably don't remember this, but there was a time when Odin wiped your phone automatically even on incremental updates. Because just like flashing a ROM, clean is the only way to truly ensure that residual files are not causing problems. But they eventually removed this behavior in later releases of Android. I don't know why this was done, I am only able to tell you the history of Odin as I know it. However, because Android changes have been so drastic lately (locked SD cards, addition of preload partition, removal of preload partition, SELinux policy updates, institution of Knox and protected files, etc etc etc.) not starting with a clean slate led to a myriad of problems for users. If you need specific examples just look at the Galaxy S5 Wi-Fi issues from taking the Lollipop OTA without doing a factory reset. If you format your hard drive before installing a new version of Windows then you should be capable of understanding why clean partitions for an OS upgrade makes sense. But you don't have to take my word for it, click the link I left with CtSomethingOrAnother up there. People almost unanimously support a factory reset for major upgrades. So you can take my advice or follow your own, but I promise that I'm going to get plenty of sleep tonight regardless of what you decide to do with your phone. You have to realize that I am giving advice as a senior member of a respected development community where new members come for answers. I make sure that I am giving them the best advice that I could possibly give them with my experience on these forums and with Samsung devices. If users decide to cut corners after knowing the proper way to do it, that is on them.
tl;dr -- I wrote this Howto so that I could help people; not waste their time. You don't have to believe anything I wrote above. In fact I encourage you to research this information yourself and come to your own conclusions about why factory resets are necessary. Until Google goes on record saying, "No more factory resets for upgrades" I'm going to keep my advice just the way it is written.
I appreciate you taking the time to explain this. I have been flashing and what not for a few years, but I am by no means completely aware of why I do things a certain way in all cases. It is nice to know the "why" behind things sometimes.
I think resetting the phone and having everything wiped should only be done if experiencing problems. Everywhere online this is the case. It is NOT required to wipe a phone. And again if you wipe / factory reset a CDMA phone - don't they have you call in to reactivate it? (little offtopic but just curious regarding verizon)
KingBeef said:
I appreciate you taking the time to explain this. I have been flashing and what not for a few years, but I am by no means completely aware of why I do things a certain way in all cases. It is nice to know the "why" behind things sometimes.
Click to expand...
Click to collapse
To me, the why is always the most important part. When someone posts a flashable file to fix a problem I open it up to see what it is doing. It took a lot of reading and some prior experience with Linux to be able to grasp a lot of what Android developers are doing when they change the files
CtJackHarkness said:
I think resetting the phone and having everything wiped should only be done if experiencing problems. Everywhere online this is the case. It is NOT required to wipe a phone. And again if you wipe / factory reset a CDMA phone - don't they have you call in to reactivate it? (little offtopic but just curious regarding verizon)
Click to expand...
Click to collapse
I truly don't understand how you could acknowledge that skipping the factory resetting could lead to problems for people but that you don't recommend it because people should just use it until they have a problem and then wipe all their data at that point. And as far as "everywhere online this is the case", I literally Googled for you tons of links with people saying to factory reset for Android upgrades and you're choosing to ignore the information. That's on you. As far as CDMA phones having to be re-activated? It's been years since I used a device on Sprint and doing a factory reset on Android led to the device activating itself. It isn't an issue, it's just part of the setup process. It's no different than updating the PRL and Profile on Sprint (CDMA) once a month to ensure roaming capabilities are working at peak efficiency. Verizon customers used to have to dial a number to update the PRL but now on Android it happens in the background just like it would during setup.
However, changing your mind isn't my job nor is it how I intend to spend my time on here. You can do whatever you wish with your phone and what I wrote is exactly how I handle my phone. I'm leaving your criticism and my responses in this thread for people who want to hear both sides and hopefully that will accomplish what you set out to do by posting here in the first place. If you still aren't satisfied, please take it to PM.
EDIT: Nevermind, I went back and edited the post to clarify that boot loop happens on downgrading and encouraged people to wipe user data while upgrading.
This method worked for me..
This was my solution to completely downgrade the N910T back to KitKat after a full Lollipop stock upgrade or rom.
Please do a nan droid back up before attempting this first?
*** I am not responsible nor accountable if you damage your android device when done incorrectly or attempting this***
Please understand doing this will and is going to trigger the knox count if attempted.
When I did this it worked for me to test Lollipop or roms and back to KitKat stock for example:
DARTHSTALKER_NOTE4_V2
InfamousROM_Note4_COD6_v1.8.1.
Just to name some good KitKat and Lollipop ROMs for the N910T that I use.
Four things your gonna need before you start:
1. The actual KitKat N910TUVU1ANK4 Firmware.
2. Odin3 v3.07
3. N910TUVU1ANK4_N910TTMB1ANK4_TMB-files-modem.bin-boot.img-recovery.img (This contains 4 files: boot.img, modem.bin, NON-HLOS.bin, recovery.img).
4. WinRar or 7zip software.
What I found is that the baseband changes and does not allow to downgrade from stock N910TUVU1COD6 Lollipop back to stock N910TUVU1ANK4 KitKat with Odin it just wouldn't allow it. I've done this so I know this works since I wasn't ready for Lollipop bugs and battery consumption. From what I heard this couldn't be done.. Anyway after your nan droid backup Wipe every thing in your recovery TWRP: Advance wipe, Wipe the dalvik cach, System, Data, Internal storage, cache reboot back download mode. Now take the TMB-files-modem.bin-boot.img-recovery.img extract it with winrar or 7zip. Now go back into Odin Click Phone and search for the files you just extracted. They are 2 files needed and that's the NON-HLOS and the modem file. This needs to be installed one at a time on the Phone tab using Odin. Flash the NON-HLOS and reboot back into download mode. Now flash the modem file in the Phone tab using Odin and boot back into download mode. Now flash N910TUVU1ANK4 KitKat Firmware using Odin and let it finish and reboot completely. Check and make sure that Odin completes the flash and reboot completely to Tmobile setup screen. Done..
If the firmware feels weird at first just do a factory reset and cache in the stock recovery. Hope this helps out the XDA community. Don't forget to thanks please?
Here: N910TUVU1ANK4_N910TTMB1ANK4_TMB-files-modem.bin-boot.img-recovery.img
h t t p://w w w 10. zippyshareDOTcom /v/5feSbGgX/file .html
hacker904 said:
This was my solution to completely downgrade the N910T back to KitKat after a full Lollipop stock upgrade or rom.
Please do a nan droid back up before attempting this first?
*** I am not responsible nor accountable if you damage your android device when done incorrectly or attempting this***
Please understand doing this will and is going to trigger the knox count if attempted.
When I did this it worked for me to test Lollipop or roms and back to KitKat stock for example:
DARTHSTALKER_NOTE4_V2
InfamousROM_Note4_COD6_v1.8.1.
Just to name some good KitKat and Lollipop ROMs for the N910T that I use.
Four things your gonna need before you start:
1. The actual KitKat N910TUVU1ANK4 Firmware.
2. Odin3 v3.07
3. N910TUVU1ANK4_N910TTMB1ANK4_TMB-files-modem.bin-boot.img-recovery.img (This contains 4 files: boot.img, modem.bin, NON-HLOS.bin, recovery.img).
4. WinRar or 7zip software.
What I found is that the baseband changes and does not allow to downgrade from stock N910TUVU1COD6 Lollipop back to stock N910TUVU1ANK4 KitKat with Odin it just wouldn't allow it. I've done this so I know this works since I wasn't ready for Lollipop bugs and battery consumption. From what I heard this couldn't be done.. Anyway after your nan droid backup Wipe every thing in your recovery TWRP: Advance wipe, Wipe the dalvik cach, System, Data, Internal storage, cache reboot back download mode. Now take the TMB-files-modem.bin-boot.img-recovery.img extract it with winrar or 7zip. Now go back into Odin Click Phone and search for the files you just extracted. They are 2 files needed and that's the NON-HLOS and the modem file. This needs to be installed one at a time on the Phone tab using Odin. Flash the NON-HLOS and reboot back into download mode. Now flash the modem file in the Phone tab using Odin and boot back into download mode. Now flash N910TUVU1ANK4 KitKat Firmware using Odin and let it finish and reboot completely. Check and make sure that Odin completes the flash and reboot completely to Tmobile setup screen. Done..
If the firmware feels weird at first just do a factory reset and cache in the stock recovery. Hope this helps out the XDA community. Don't forget to thanks please?
Here: N910TUVU1ANK4_N910TTMB1ANK4_TMB-files-modem.bin-boot.img-recovery.img
h t t p://w w w 10. zippyshareDOTcom /v/5feSbGgX/file .html
Click to expand...
Click to collapse
I'm going to wait on some testers for this one lol but if confirmed...I'm on it! Lol although I'm a little confused why I would nan and then immediately wipe internal data? I don't have a SD card yet though (just got phone today) so any nan I make goes right to internal :/
Internal data
v2.2v said:
I'm going to wait on some testers for this one lol but if confirmed...I'm on it! Lol although I'm a little confused why I would nan and then immediately wipe internal data? I don't have a SD card yet though (just got phone today) so any nan I make goes right to internal :/
Click to expand...
Click to collapse
I wouldn't recommend doing any type of internal data wipe unless you have a SD card. Now take note of this when using custom (TWRP) recovery that you have to manually go into storage during the back up. Now go to the drive/storage and change the option in oder to back up on the Ext.SD card. I would be careful in the recovery when advance wiping the phone to reinstall another rom. It has the option to wipe the Ext.Sdcard...Do not do that take it from me I've done it rushing and it sucks. TWRP backs the nandroid on the Ext. in a TWRP file.
Hope this helps every one out.
Please thank?
hacker904 said:
I wouldn't recommend doing any type of internal data wipe unless you have a SD card. Now take note of this when using custom (TWRP) recovery that you have to manually go into storage during the back up. Now go to the drive/storage and change the option in oder to back up on the Ext.SD card. I would be careful in the recovery when advance wiping the phone to reinstall another rom. It has the option to wipe the Ext.Sdcard...Do not do that take it from me I've done it rushing and it sucks. TWRP backs the nandroid on the Ext. in a TWRP file.
Hope this helps every one out.
Please thank?
Click to expand...
Click to collapse
Hey bud. and this by no means is trying discredit you, but the OP works just fine. Just did it. Odin 4.4.4 and wipe data after.
@hacker904 did you do this from 5.0.1 or 5.1.1 because I am on 5.1.1 and have tried to return to Kit Kat and it will not allow me to. Also waiting for testers on this one
Santos89 said:
@hacker904 did you do this from 5.0.1 or 5.1.1 because I am on 5.1.1 and have tried to return to Kit Kat and it will not allow me to. Also waiting for testers on this one
Click to expand...
Click to collapse
I guess tmobile changed some security policy that blocks phone users from downgrading.
Source:
http://forum.xda-developers.com/showpost.php?p=64548030&postcount=5
downgrading from cod6
Has anyone confirmed that you cant downgrade from Cog6? I am on one of the 5.1.1 ROMs I tried downgrading to 4.4.4 using ODIN but it keeps failing. Has anybody had any success with this?
Honor released an update today for its KIW-L24
This will upgrade your system to KIW-L24C567B351 from any of the versions given below.
If you are in KIW-L24C567B331CUSTC567D003 - Download the package from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74510/f1/full/update.zip
If you are in KIW-L24C567B334 - Download the package from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74512/f1/full/update.zip
This update consists of latest January Google security patches and few important bug fixes for device.
vsriram92 said:
Honor released an update today for its KIW-L24
This will upgrade your system to KIW-L24C567B351 from any of the versions given below.
If you are in KIW-L24C567B331CUSTC567D003 - Download the package from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74510/f1/full/update.zip
If you are in KIW-L24C567B334 - Download the package from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74512/f1/full/update.zip
This update consists of latest January Google security patches and few important bug fixes for device.
Click to expand...
Click to collapse
Thanks for the note, but either there is an issue with the update or the file got corrupted on the download. I flashed it and emui went through the update process, rebooted and then said my SD card was corrupt and to format it.
I have a 128GB card full of music TBU and saved ROMs that I did not want to lose. Went back via TWRP to previous and no damaged SD card and all is well.
Might have been the file was corrupted but just be caareful and always backup before you make any changes.
So nice of their support site to be down...
tomlogan1 said:
Thanks for the note, but either there is an issue with the update or the file got corrupted on the download. I flashed it and emui went through the update process, rebooted and then said my SD card was corrupt and to format it.
I have a 128GB card full of music TBU and saved ROMs that I did not want to lose. Went back via TWRP to previous and no damaged SD card and all is well.
Might have been the file was corrupted but just be caareful and always backup before you make any changes.
Click to expand...
Click to collapse
Instructions > https://forum.xda-developers.com/honor-5x/how-to/guide-force-installing-stock-ota-t3502874
What are the bug fixes???
Are there any new features???
I am currently on custom ROM and would like to know the answers to these questions to see if it's worth it to go back to stock rom
Hi, is there a full firmware package for this new version? Tried to upgrade and got soft-bricked and I don't know if it's safe to flash the full B331 package.
[EDiT]
Flashed the full B331, booted and applied the B351 update by powering off and pressing Vol+ & Vol -. After booting it still says B331 and my WiFi is dead.
m0ndul said:
Hi, is there a full firmware package for this new version? Tried to upgrade and got soft-bricked and I don't know if it's safe to flash the full B331 package.
[EDiT]
Flashed the full B331, booted and applied the B351 update by powering off and pressing Vol+ & Vol -. After booting it still says B331 and my WiFi is dead.
Click to expand...
Click to collapse
So much miss information .. no one bothers to find the truth
Can I ask where/when/how you found these files? There seems to be nothing official available, nor will Huawei provide any information about any prospective update.
animeme said:
Can I ask where/when/how you found these files? There seems to be nothing official available, nor will Huawei provide any information about any prospective update.
Click to expand...
Click to collapse
Link below or install the Huawei Firmware Finder form the Google Play Store and set it up to get OTA files in settings.
http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=kiw-l24
deleted
So did anyone ever take a wack at this? I've done a lot of googling and haven't been able to find anything official off the support site about this update so I was wondering if it was legit or not? I know how the update zip suppose to work and how to make it work. Just wondering if anyone used this.
GrimReaper24 said:
So did anyone ever take a wack at this? I've done a lot of googling and haven't been able to find anything official off the support site about this update so I was wondering if it was legit or not? I know how the update zip suppose to work and how to make it work. Just wondering if anyone used this.
Click to expand...
Click to collapse
What he said.
I'm hoping it's nothing more than a VoLTE update that LOS maintainers warn against anyway, if there's actually no one to further explain what it is
received this B351 update over B331, also did factory reset, GUI lag seems gone, not noticing new feature
my kiwi-L24 got re-flashed today, it is weird that this B351 update is no longer available from B331's update check
searched on internet, there is news about "honor 5c" getting a B351 nougat update
This came up on one of the 5X's that I have. Updated and forgot to put back stock recovery. Don't be like me and forget to do that. Now it won't work properly and I can't get to start any apps to try and fix it. I can put back TWRP and wipe it, but I don't want to lose my data. I also have that problem now where it keeps telling that the SD card is corrupted. I backed up the data and scrubbed the card in the phone but it keeps coming back with the same thing.
If someone did an actual successful update properly (with stock recovery) then please update and say if everything is working. If not, I'm going to have to find some way to backup the data and then scrub it.
*EDIT*
I believe something like this happened to me before. I was on B151 and went to B331 with TWRP installed by accident. What happened was that the OS was still running EMUI 3.1 but the build was saying B331. After fighting with it (and community support) I managed to get it to B331 fully and EMUI 4.0 - since then and a few custom ROMs I'm back on B151 EMUI 3.1 due to stability. Games and some apps just didn't work on the new one. The second phone was on B331 fully though - then I made the same mistake and it went to B351. This time though, the phone seems screwed. No apps will load. I can get into settings and the file manager, but no Titanium Backup and no Flashify. Going to put back TWRP and try to flash GAPPS and see if it will help me get into Play Store. From there I'll try to reinstall Flashify and flash the ZIP of the update. Will post back once done.
*EDIT*
Well that didn't work. Even after going back and trying to root the device again - then checking the option for it to not detect the dirty flash - still didn't work. Kept complaining that stock apps are already present.
I'm going to try and get some files off the device, but keep having issues. Not sure why. May just have to scrub. Will update again.
*EDIT*
With TWRP on I used "ADB PULL" to get certain files from the root system which I couldn't access otherwise for some reason. Then copied the other things (photos and such) and will now be using the UPDATE.APP to get it working. For this I formatted the SD from within TWRP and created the DLOAD folder (with no caps - so that's dload - but I'm not sure if it matters) and will be copying the UPDATE.APP. Not sure which version yet, because there was some problem with one I had downloaded before. So I need to double-check and re-download.
*EDIT*
So I've successfully flashed the UPDATE.APP from the SD card (same one the phone was claiming is corrupted). Just for reference, here is the file information and hashes.
File Name: Honor 5X_Firmware_KIW-L24_Android 6.0.1_EMUI 4.0_C567D003_United States.zip
Size: 1762266487 bytes
ADLER32: 27cb0c31
CRC32: 1d9379b9
MD2: 6517c34dc9bac0cd8680e3c4fd09d8d9
MD4: 4a803765c0ed54cb5d6853a9f365cd3b
MD5: 04f60b067d546ad71f556e44a7934dc7
SHA1: 8d2718568ac6509a40c95e42857d400395eb88d2
SHA256: 82975923172b3800d3f09f76691f2a694ab98110e3f909084a02bd566448386f
SHA384: da53b58b8e20395595590fd0cec30e56fa6a62e638ec53e46a74ebf58d051fdd7576602019bd3130ca5c00cc432715a0
SHA512: 806e0e8969c293ca8b497a786699ee306352ad6ef434552f2d23decff8a5279c7fd605e046c13f11c2f87947f5a2bdf23d78fdec6263661e68f023fd72bf4381
RIPEMD128: 9d963e5d51c9df9554fa3422da84dd27
RIPEMD160: a1e5b8f08b65dd2bb08e04d62db270ad8f4cf51a
TIGER128: 66fb4e4e4ce11cb30626aea807355f83
TIGER160: 66fb4e4e4ce11cb30626aea807355f8345f1dd79
TIGER192: 66fb4e4e4ce11cb30626aea807355f8345f1dd79dbb39488
GOST: 93774537f6ca49d4406f9d3a0316d014e1e099b34fc1cd9b968dacc870700827
The file name may be different, but as long as you got the right one you should be OK. If you have issues when copied to an SD card - verify that the file on the SD card has the correct hashes. To make it faster use CRC32. For more surety, use MD5. You can get a tool like WinMD5 to check. It's free.
So now that it's done, I'm going to set it up as a new phone and wait to see if the update comes back on. If it does, I'll get it down and upload the B351 recovery. After that I'll need to remember that I have to put back the stock recovery before running any updates. Flashify FTW.
BTW - during the initial setup after connecting to wireless it came back with the update. Pics to follow.
Files will be uploaded here: https://drive.google.com/open?id=0BzqEmGyNP_v6aTZTZDN6bWo2ZEk
*EDIT*
So the files are uploading to the folder. The screenshot is attached. Had one issue where after the update I couldn't get back into the phone. Had to wipe/factory reset. I've used FASTBOOT BOOT TWRP.IMG to take the backups of the BOOT and RECOVERY. Hopefully one of the gurus can use that and give the IMG files. I'm going to try root and get FLASHIFY to backup the stock recovery and add to the folder.
khat17 said:
This came up on one of the 5X's that I have...............
Click to expand...
Click to collapse
I don't really like to do double replies, but I guess for ease of finding the info it's better this way. Unless a mod thinks differently and wants to merge all the info.
Google Drive Link With Files
https://drive.google.com/open?id=0BzqEmGyNP_v6aTZTZDN6bWo2ZEk
This contains TWRP backups of the recovery and boot images. There's also a file called KIW-L24-B351 which was created with Flashify. I assume you can add the IMG extension to it and flash as needed.
Basically I had this update run on another phone (my wife's) and it messed with the phone due to the recovery being TWRP and not stock. My fault - forgot to do that before handing the phone back to her. I believe it happened to me before but it never messed up the phone this way. Nothing would work except core apps like settings and the stock file manager. The Play Store wouldn't even open.
Anyways - back to factory with UPDATE.APP then run the automatic update from an OTA update on wireless, then FASTBOOT BOOT TWRP.IMG and capture the backups. Then flash SuperSU to get root. Then Flashify. Files are uploaded for your convenience.
Warning that during the initial OTA it took a while. And after it was done I couldn't get into the phone with the password. Had to factory wipe/reset again and setup again. Disable passwords just in case I guess. Hope this helps others - have fun.
No major differences. I haven't really used the stock OS6 but some things look a little different. Nothing major. Will see when she's using it if it lags or has improved memory and such. Not sure if I'll be able to test with apps that wouldn't run previously for me, but will see. Tested with TransDrone and it failed. Once SeedBox information is loaded it still crashes. Only happens on OS6 so I'm sticking with OS5 on mine. Does not happen with custom roms however (from what I recall - would have to check back).
Hello every one,
I have the Honor 5X KIW-L24 rooted with TWRP, stock ROM.
I received this OTA update and saddly i pressed the update button. Now the phone is in TWRP loop.
What can I do please help. I already wipe cache and Dalvik, didnt work.
raulpcamara said:
Hello every one,
I have the Honor 5X KIW-L24 rooted with TWRP, stock ROM.
I received this OTA update and saddly i pressed the update button. Now the phone is in TWRP loop.
What can I do please help. I already wipe cache and Dalvik, didnt work.
Click to expand...
Click to collapse
Follow this video if don't know how to flash back stock recovery through adb. Then take a look at those threads how to downgrade, here, here, here. Hope it helps.
bluesky299 said:
received this B351 update over B331, also did factory reset, GUI lag seems gone, not noticing new feature
Click to expand...
Click to collapse
Same here.
It had been too many months of the Honor 5X in the closet so i almost lost track what to do but what i did was revert all the way back to Stock ROM (had to flash an extracted/saved Recovery.IMG) and then do the UPDATE.APP from Dload complete and repeat on up to the current B351.
Of course lost Root but when ready can add that back too.
Yes the Honor 5X runs much smoother now than before plus that Battery Drain issue (Remember That?) where we had to dig deep to change 4 to 0 i think, well Battery Life is also greatly improved on mine.
GrimReaper24 said:
So did anyone ever take a wack at this? I've done a lot of googling and haven't been able to find anything official off the support site about this update so I was wondering if it was legit or not? I know how the update zip suppose to work and how to make it work. Just wondering if anyone used this.
Click to expand...
Click to collapse
I tried to update as the previous user did using TWRP and got the corrupted SD card message. I then tried to go back to stock ROM. Went into bootloop.
Been having a hell of a time getting anything to work properly since.
[UPDATE]:
**********
I got sick of my phone telling me I needed to update but I couldn't because I'm rooted. So finally got around to patching the last full ROM today w/ the incremental.
This is the fastbootd w/ flash_all.bat script to update to 11.0.12.12.KB05AA. The package for KB05AA (Global/US) is not yet available, hence I'm still making it available here. Be sure to alter the flash script (remove the "rem" before boot.img and recovery.img if you DO NOT want to keep your custom kernel + TWRP) ****************
3.14 GB file on MEGA
mega.nz
THIS IS ONLY FOR 11.0.9.9.KB05AA, BUT READ IT ANYWAY!!!!: ***************
I think this is the first time anyone has actually made a working incremental update for a rooted OOS device, or any with a payload.bin update method that I know of. This method doesn't require any wiping and TWRP / rooted boot.img / custom OOS kernel can be installed right after the script finishes (or left on the device), and you don't even change your active slot (usually, incremental updates will flash to the inactive slot).
I won't get into that many specifics except it was EXTREMELY DIFFICULT, but it works now. Read here if you want to do it yourself in the future, or on another phone. Should work on just about any phone that uses payload.bin files https://forum.xda-developers.com/t/...11-0-9-9-kb05aa-posted.4314677/#post-85425949
You may have to edit the .bat file to pick your RAM type (the lp5 ones are for devices with LPDDR5; it is preset for most of the phones using the LPDDR4 RAM). On the Op8T at least you can do this from adb shell:
adb shell getprop ro.boot.ddr_type; where a 0 is LPDDR4 and 1 is LPDDR5 ram. If it's 1 returned, you need to flash the lp5 files instead of the same named otherwise files in the .bat file (so edit it).
That weird -cow stuff is temp files that prevented the update from working. Not documented anywhere I could find (well, minimally explained by Google), took hours to figure out they were filling the super partition up. I had to re-engineer a Linux project (linked above) to get this working, and have officially updated from 11.0.8.13 to 11.0.9.9 COMPLETELY now. While rooted, without switching slots, and TWRP installed.
You just have to ensure you're on the latest ADB and Fastboot tools and an adb reboot bootloader, followed by a fastboot reboot fastboot should get you there. You can check with: fastboot getvar is-userspace
If it says yes, you're in fastbootd. It actually will work with TWRP installed, I found out later, as long as you reboot in TWRP to fastboot and confirm with the command above you're in fastbootd.
https://github.com/fawazahmed0/Latest-adb-fastboot-installer-for-windows/releases/tag/v1.7 has a script that will get you the Latest ADB and Fastboot and put it in a folder for you.
I uploaded it to Mega. Just use some common sense and look at the flash_all.bat file before flashing. I'd write more but I'm tired as hell from getting this working. Now we'll never have to wait for an incremental update while rooted again, at least in the foreseeable future.
I'm just going to leave this here
https://forum.xda-developers.com/t/...1-kb2003-kb2005.4178675/page-25#post-85386145
g96818 said:
I'm just going to leave this here
https://forum.xda-developers.com/t/...1-kb2003-kb2005.4178675/page-25#post-85386145
Click to expand...
Click to collapse
That never worked for me and others, Always resulted in either bootloop or booting back to previous build
nujackk said:
That never worked for me and others, Always resulted in either bootloop or booting back to previous build
Click to expand...
Click to collapse
I've mentioned it multiple times for people having issues. They need to use the unbrick tool cause there is something wrong with the original rom install from OnePlus.
g96818 said:
I've mentioned it multiple times for people having issues. They need to use the unbrick tool cause there is something wrong with the original rom install from OnePlus.
Click to expand...
Click to collapse
This Devs solution works and i appreciate his work. And appreciate your attempts but didn't work for me So ....
nujackk said:
This Devs solution works and i appreciate his work. And appreciate your attempts but didn't work for me So ....
Click to expand...
Click to collapse
It's good that you found a band-aid fix.
nujackk said:
That never worked for me and others, Always resulted in either bootloop or booting back to previous build
Click to expand...
Click to collapse
Of course I tried that solution first, it didn't work on my device.
I'm glad it did on others' devices, kudos to you for posting it (and I DO appreciate your work), but this is the only one that worked on mine. Why? Who knows. I also followed another guide that didn't work. Or else I wouldn't have wasted all my time making this (it took many, many hours to assemble). I'm not saying it's the best solution (I really hope someone just uses what I put in the other thread and assembles it into an easier format for others to use), but I have a full time job (2 actually) so I can't work on it anymore. But it works, no data loss, and TWRP can be installed. Until the next incremental update comes out, then I'll post another version using the tools I used for this, if your build doesn't work on my device. But only when I have the time...
g96818 said:
It's good that you found a band-aid fix.
Click to expand...
Click to collapse
LoL band-aid fix... Call it whatever you want, it works.
It's actually a patched 11.0.8.3.KB05AA with the incremental update applied to it for 11.0.9.9.KB05AA. So it flashes to the active slot and TWRP / rooted custom kernel can all be installed at the same time, even while you are still rooted with Magisk, and even if TWRP is installed. No data loss. I never claimed perfection on this project, just that it works for me.
Keep doing what you're doing, I'll keep doing what I'm doing. We both just aim to help others anyway. I just couldn't get any other method to work so I came up with this one, extending on the incomplete / abandoned work of others. I didn't come up with Payload extraction. Never claimed to. I didn't come up with fastbootd flashing either.
All the forked and modified code is at my GitHub repo. The fork goes back to several other devs' forks (mine is the 3rd modified fork).
Someone want to point me to the right download for the incremental update to 11.0.9.9.KB05AA? I got a download link but if it's not for this exact ROM, it would be dangerous (I don't know what would break) if I applied it and patched the incremental 11.0.9.9 (which is like a full ROM in the way I distribute it here). I believe the update is 11.0.10.10.KB05AA. I tried downloading as illustrated in the linked thread and it halfway installed (Op8T's don't seem to like the "remove Magisk images" and then install the update method, it totally jacked up my system (like long boot time, alarms didn't work, numbers wouldn't always appear to login to the phone after reboot, etc.), luckily I had backed up Super in TWRP and that fixed it (upon a restore). The one someone told me was the official link to the incremental update did not work with the Linux program I hacked, so it's either incapable of patching an incremental 2x, or I got the wrong file downloaded. My life is so crazy at the moment I don't have time to screw up my phone just to get the incremental update downloaded on my phone and extract it, so if anyone has already done that, please let me know.
mslezak said:
Someone want to point me to the right download for the incremental update to 11.0.9.9.KB05AA? I got a download link but if it's not for this exact ROM, it would be dangerous (I don't know what would break) if I applied it and patched the incremental 11.0.9.9 (which is like a full ROM in the way I distribute it here). I believe the update is 11.0.10.10.KB05AA. I tried downloading as illustrated in the linked thread and it halfway installed (Op8T's don't seem to like the "remove Magisk images" and then install the update method, it totally jacked up my system (like long boot time, alarms didn't work, numbers wouldn't always appear to login to the phone after reboot, etc.), luckily I had backed up Super in TWRP and that fixed it (upon a restore). The one someone told me was the official link to the incremental update did not work with the Linux program I hacked, so it's either incapable of patching an incremental 2x, or I got the wrong file downloaded. My life is so crazy at the moment I don't have time to screw up my phone just to get the incremental update downloaded on my phone and extract it, so if anyone has already done that, please let me know.
Click to expand...
Click to collapse
Better to install the full ROM
Download Oxygen Updater in app store and select your device AA for global and Ba for European device.
Go to settings, system update wait til 100% and Don't reboot yet if you want to keep Root
Go to Magisk and install ota in inactive slot
5star02707 said:
Better to install the full ROM
Download Oxygen Updater in app store and select your device AA for global and Ba for European device.
Go to settings, system update wait til 100% and Don't reboot yet if you want to keep Root
Go to Magisk and install ota in inactive slot
Click to expand...
Click to collapse
I think maybe you misunderstood what I did in this thread. I patched a full ROM with the incremental update of 11.0.9.9.KB05AA. So while OnePlus does not have a full ROM available for download (yet), it is available for download here.
Yeah the method you propose is the "normal" rooted way, but if you're rooted already it forces you to full ROMs not OTAs. You'll be on 11.0.8.3.KB05AA. The goal here is to get on 11.0.10.10.KB05AA (someone NOT ROOTED could download the OTA update using Oxygen Updater and upload it here so I could make a patched version for those that want to keep their root / custom kernel / TWRP / etc and avoid the hassle of unrooting first, which wipes your data partition). At least my Oxygen Updater won't let me download incremental updates even with Magisk Images removed (don't try this unless you're on Op8 / Op8 Pro; some people are having big system update issues on Op8T incremental hence why this thread exists.) It jacked up my system pretty bad (Magisk images removed, Settings / System / System Updates method) until after a boot.img and super restore from TWRP. Not all devices were setup the same (mine is a US carrier converted to US KB05AA). To my knowledge, no direct download has been posted for KB05AA incremental update. Here or on TG. If you have found one, please post a link here. The only one out I've seen works on European ROMs. OnePlus always does KB05AA last for whatever reason.
11.0.10.10.KB05AA posted with caveats - please back up your data as suggested in case the Phone Services APK doesn't fix your SIM after a flash, and you end up formatting the data partition. You may want to try some other methods or just plan on restoring (not with TWRP Alpha in my experience).
mslezak said:
Guys, bad news. So 11.0.10.10.KB05AA incremental does something to the data partition and kills your SIM access.
...
Click to expand...
Click to collapse
I successfully update from 9.9 to 10.10 including keeping root. I have no issues with my Sim card. So, for me, the update is fine.
However, I believe that the 10.10 update includes a key change. This results in the data partition being unreadable if you swap back to the previous slot after the update. I found this out by doing just that using TWRP.
But syncing the 10.10 firmware to the inactive slot fixes this. It might be possible (I haven't tried it) to just sync the keymaster partition to the inactive slot and then restore 9.9 (excluding keymaster).
BillGoss said:
I successfully update from 9.9 to 10.10 including keeping root. I have no issues with my Sim card. So, for me, the update is fine.
However, I believe that the 10.10 update includes a key change. This results in the data partition being unreadable if you swap back to the previous slot after the update. I found this out by doing just that using TWRP.
But syncing the 10.10 firmware to the inactive slot fixes this. It might be possible (I haven't tried it) to just sync the keymaster partition to the inactive slot and then restore 9.9 (excluding keymaster).
Click to expand...
Click to collapse
Can you explain how you managed to update it? I'm screwed at this point anyhow, would like to hear how you did it. Are you just saying when you update flash to both slots and the data is still readable? Instead of flashing to active only? I still have the extracted / patched ROM, not going to try it out now (or for a while) unless I know someone has figured out a way to make it not break the system data. (Note: I'm on a very hacked phone; it's a carrier T-mobile originally fastbootd converted to Global, then updated on Global since then). I realize most people probably don't have a phone that's been altered this much. Then the easier methods are more likely to work. I'm also running a custom fork (mine) of RadioActive kernel (just tweaked how I like it, wakelocks blocked to save idle battery, some GPU frequencies added, etc). I tried running just the patched boot.img with Magisk but still Phone Services was busted.
@mslezak, When I get an update I:
- use a terminal session (you could also use ADB) to restore the stock boot and recovery (this way I don't lose root yet)
- install the update but don't reboot
- copy the new boot image and patch it
- turn on airplane mode (to avoid SafetyNet and certification issues in the next step)
- reboot the phone and the updated system comes up
- flash the patched boot image and TWRP in fastboot/bootloader
- reboot and disable airplane mode
This is basically @osm0sis' process from https://forum.xda-developers.com/t/...ices-platforms.2239421/page-149#post-84764713
No, I'm not saying flash to both slots, because that will make it impossible to fall back to the current system if the update fails (though this is meaningless if you're manually flashing partitions).
I've got into the habit of syncing active to inactive (after I'm happy with the update) simply because it's required when going from OOS to a custom ROM (I use a shell script based on the LineageOS sync zip). And, after the sync, I can now access the data partition from the inactive slot (which wasn't the case just after the update due to the different keys).
mslezak said:
Can you explain how you managed to update it? I'm screwed at this point anyhow, would like to hear how you did it. Are you just saying when you update flash to both slots and the data is still readable? Instead of flashing to active only? I still have the extracted / patched ROM, not going to try it out now (or for a while) unless I know someone has figured out a way to make it not break the system data. (Note: I'm on a very hacked phone; it's a carrier T-mobile originally fastbootd converted to Global, then updated on Global since then). I realize most people probably don't have a phone that's been altered this much. Then the easier methods are more likely to work. I'm also running a custom fork (mine) of RadioActive kernel (just tweaked how I like it, wakelocks blocked to save idle battery, some GPU frequencies added, etc). I tried running just the patched boot.img with Magisk but still Phone Services was busted.
Click to expand...
Click to collapse
Thats not very hacked/hacked at all, and quite a few use that setup
xstefen said:
Thats not very hacked/hacked at all, and quite a few use that setup
Click to expand...
Click to collapse
LoL I gave up fastbootd flashed to 11.0.10.10.KB05AA and formatted data, let Google download everything it backed up, and am back in business. Just have a lot of apps to login to / Magisk modules to add / etc.
So yeah my patched 11.0.10.10.KB05AA works but the data must be formatted or the SIM doesn't work (at least for me; I don't know if anyone else has tried it since I just posted it a few hours ago; it could be that it works for some without causing issues, I don't have any idea). The goal was to not have to mess up the data partition.... but I can't control what OnePlus does in their updates... Try what worked for others posted here first I'd suggest, or just make solid backups of everything knowing you're going to likely need to reinstall / re-login to everything and format the data partition. New pin, new fingerprint, etc. Re-login to your wifi blah blah.
It's still a full unreleased ROM so I posted it for those that don't mind taking backups (outside of TWRP) if they want to keep root & TWRP on the new release... Yeah a pain to setup if you aren't warned to use another backup method (maybe there is a better backup method, maybe Migrate (app store early access) is developed enough for easy transfer now, I know many people said it worked well in the past but haven't been following the updates. Still free).
It dawned on me later that since the only thing that didn't work using this method going from 11.0.9.9.KB05AA to 11.0.10.10.KB05AA was phone services, that I should just include the working version in this post. Since I already did it the hard way and restored everything back to normal. AS I SAID ABOVE, IF PHONE SERVICES ISN'T ENOUGH TO FIX THE ISSUE, PM ME AND I CAN EXTRACT MORE RELATED FILES UNTIL IT WORKS AGAIN. Unfortunately, I can't just downgrade to 11.0.9.9.KB05AA and keep trying fastbootd over and over again as I don't have the time.
g96818 said:
I've mentioned it multiple times for people having issues. They need to use the unbrick tool cause there is something wrong with the original rom install from OnePlus.
Click to expand...
Click to collapse
The whole point of this is to AVOID the unbrick tool, reinstalling an outdated version, updating each new ROM build since the brick tool was made, and starting over clean. I think... Have a hunch at least we're almost there on 11.0.10.10.KB05AA with an APK install... Although just backing up everything first will always work (if you don't mind formatting your data partition) just as it's posted here already. Always an issue for us rooted users (especially on Global) since we're always last in line to get a full ROM. This IS a full ROM, payload extracted and patched with incremental updates. Still not available from OnePlus Global (KB05AA) as I checked today, so still relevant.
Ladies and Gents,
I have removed some off topic posts from this thread because I believe we could express the same meaning in more civil words. Please try to do that from now on.
Thanks.
Jerry
FSM