Only out for Customized ES right now.
Anyone have a changelog?
What did they fix?
it seems that customized DE has been updated on xperifirm downloading now
180490 said:
it seems that customized DE has been updated on xperifirm downloading now
Click to expand...
Click to collapse
What was changed? I'm interested in better battery and Bluetooth shuttering fix than anything at the moment.
Sent from my E6653 using Tapatalk
* All of our latest bug fixes and improvements
* Improved handling of Bluetooth connected devices
For those using a rooted phone with TWRP, I'd wait. TWRP won't work with that new kernel yet.
Edit: That firmware works with the older .224 kernel though, if you don't want to lose your recovery
so we need to install OTA and then root again with .224 kernel or root wont be removed?
Antho02 said:
so we need to install OTA and then root again with .224 kernel or root wont be removed?
Click to expand...
Click to collapse
I always use RootKernel to patch the stock Sony kernel.
After flashing .253 firmware + patched .253 kernel, everything worked (including SuperSU/root, DRM-verify/ Sony RIC, etc.) except TWRP 3.0.2.
I was unable to patch the new kernel to include TWRP. Flashing the latest Z5 TWRP .img manually didn't work either, so it looks like the current version of TWRP has a problem with the new kernel.
For the moment, and until TWRP works with the newest kernel, I reflashed the old .224 patched kernel over .253, and everything works (including TWRP), without issue.
I don't know to what extent the new .253 kernel is different than the older .224 one though.
.224 kernel + .253 firmware
Phazonclash said:
I always use RootKernel to patch the stock Sony kernel.
After flashing .253 firmware + patched .253 kernel, everything worked (including SuperSU/root, DRM-verify/ Sony RIC, etc.) except TWRP 3.0.2.
I was unable to patch the new kernel to include TWRP. Flashing the latest Z5 TWRP .img manually didn't work either, so it looks like the current version of TWRP has a problem with the new kernel.
For the moment, and until TWRP works with the newest kernel, I reflashed the old .224 patched kernel over .253, and everything works (including TWRP), without issue.
I don't know to what extent the new .253 kernel is different than the older .224 one though.
View attachment 3810679
.224 kernel + .253 firmware
Click to expand...
Click to collapse
thanks for info
i dont use much twrp, maybe ill let .253 kernel
ill give a try on my z5 compact
Band icon is bigger now.
Enviado desde mi Sony Xperia Z5 utilizando Tapatalk
Ringtone sound
Friend..does it fix ringtone (loudnes) sound for incoming call...thank's in advanced
"Could not open connection to the server" Mail app
Now I'm not sure if this is connected or coincidental but since updating earlier today I've been getting connection errors on the Mail app for Hotmail account (Could not open connection to the server) which had been working flawlessly for the last eight months I've had this phone. Twice I've deleted the account and re-entered it which made mail work OK again for a couple of hours but it subsequently stops receiving email again. Rebooting the phone has no effect. WiFi or mobile data, no difference.
Obviously, I have not changed any settings on the phone since updating to .253 but that's not to say the firmware doesn't contain some change effecting this.
Seems this has happened before too: https://talk.sonymobile.com/t5/Xper...ion-to-server-after-upgrading-to/td-p/1110270
Anyone else?
Sh4rkill3r said:
Band icon is bigger now.
Enviado desde mi Sony Xperia Z5 utilizando Tapatalk
Click to expand...
Click to collapse
Using which firmware region?
Must be either "Customized ES" or "Yoigo ES" because "Customized DE" displays LTE, not 4G.
Nevermind my previous message. Got it to work...
.253 firmware + .253 kernel + TWRP 3.0.2
Only a folder to rename when patching the kernel with RootKernel
ricodredd said:
Now I'm not sure if this is connected or coincidental but since updating earlier today I've been getting connection errors on the Mail app for Hotmail account (Could not open connection to the server) which had been working flawlessly for the last eight months I've had this phone. Twice I've deleted the account and re-entered it which made mail work OK again for a couple of hours but it subsequently stops receiving email again. Rebooting the phone has no effect. WiFi or mobile data, no difference.
Obviously, I have not changed any settings on the phone since updating to .253 but that's not to say the firmware doesn't contain some change effecting this.
Seems this has happened before too: https://talk.sonymobile.com/t5/Xper...ion-to-server-after-upgrading-to/td-p/1110270
Anyone else?
Click to expand...
Click to collapse
did you disabled email app? i had sync errors in my contacts/calendar apps when i did it in .224
Phazonclash said:
Nevermind my previous message. Got it to work...
.253 firmware + .253 kernel + TWRP 3.0.2
Only a folder to rename when patching the kernel with RootKernel
Click to expand...
Click to collapse
can you explain what to change pls?
Antho02 said:
did you disabled email app?
Click to expand...
Click to collapse
That's right. I disabled the email app and I'm wondering why the email app isn't working. Thanks for your insight.
Antho02 said:
did you disabled email app? i had sync errors in my contacts/calendar apps when i did it in .224
can you explain what to change pls?
Click to expand...
Click to collapse
Yes, assuming you're using the RootKernel tool to patch your kernel, the only thing you have to do is:
1) Go to rootkernel/Android/twrp_common_kmodules
2) Make a copy of the 3.10.84-perf-g4a67e86 folder
3) Rename the new folder you just copied to 3.10.84-perf-gf1cfa5f
4) Use RootKernel as usual
You'll be able to patch your kernel using rootkernel normally, with all the needed stuff (disable RIC and dm-verity, install TWRP, busybox and DRM fix, etc.)
View attachment 3811732
ricodredd said:
That's right. I disabled the email app and I'm wondering why the email app isn't working. Thanks for your insight.
Click to expand...
Click to collapse
sorry, u cd be using a third part app
anyway maybe another system app disabled, since app mail disabled crashed my calendar and blocked contact sync, i take a look at that
Phazonclash said:
Yes, assuming you're using the RootKernel tool to patch your kernel, the only thing you have to do is:
1) Go to rootkernel/Android/twrp_common_kmodules
2) Make a copy of the 3.10.84-perf-g4a67e86 folder
3) Rename the new folder you just copied to 3.10.84-perf-gf1cfa5f
You'll be able to patch your kernel using rootkernel normally, with all the needed stuff (disable RIC and dm-verity, install TWRP, busybox and DRM fix, etc.)
View attachment 3811732
Click to expand...
Click to collapse
thanks a lot man! i ll take a look at that, hope they are same or similar for z5 and z5c
SIP accounts still missing
For anyone wondering if the missing SIP account settings that disappeared from some region's .224 update is back in this one..........NOPE. Still missing from Customized DE anyway.
https://talk.sonymobile.com/t5/Xper...missing-build-32-2-A-0-224/m-p/1131876#M19636
Related
I am going to flash the latest froyo available for Middle East and then afterwards share my experiences about
1. Stock Rom
2. Speed/ Lag
3. GPS Connectivity
4. Any new Features
5. Battery Drain
In mean while if any one got his/her hands on this Latest Froyo (November 2010) release, please share???
nasgilani said:
I am going to flash the latest froyo available for Middle East and then afterwards share my experiences about
1. Stock Rom
2. Speed/ Lag
3. GPS Connectivity
4. Any new Features
5. Battery Drain
In mean while if any one got his/her hands on this Latest Froyo (November 2010) release, please share???
Click to expand...
Click to collapse
Its African/ Arabic Firmware but there is one latest Froyo (ADJP5) other region
what do u mean the latest one i found was jpjpf i think that that will be the official froyo for middle east. try it and tell me what you think i wll also flash it too
I already flash this Rom there is not much difference between jpjpf and jpjpa both are arabic/farsi roms.so far I could not experience a considerable item in this new rom.
taha_e said:
I already flash this Rom there is not much difference between jpjpf and jpjpa both are arabic/farsi roms.so far I could not experience a considerable item in this new rom.
Click to expand...
Click to collapse
I have better GPS connection after JPJPG(OFFICIAL through kies)
Sent from my GT-I9000 using XDA App
For Market: In phone dialer enter *#272*IMEI# . This wilk give u option to change from XSS to XSG, xsg has market enabled, by doing so you phone will reset, IMEI is number for you mobile handset, XSG is universal
OR
use attached market apk for XSS mobile, use Clockwork mode to "install from zip file" if you dont have Clock work mode, rename the zip to "update" and apply in Recovery
Battery is not draining that quickly but wifi sucks
Sent from my GT-I9000 using XDA App
JPJPG is available through Kies aswell, If you are on JPJPA, flash back to JPJG8 and connect your mobile to Kies, It will offer you JPG upgrade, Before flashing back you need to backup your data/ sms/call logs etc and then flash back
Quick questions guys:
Just got 2.2 through Kies. I now need to re-download my apps, over 90% of them are not showing through the market, not even through search. Im guessing I have to change again to XSG like I did when I had 2.1, then root again as well to enable Market Enabler and access paid apps like I used to (which I did with Ryanza)
1. Old XSG access code (HHMM) gets rejected, new code IMEI gets rejected,is there a way to enable this without flashing etc (i'm a very low-tech person)
2. How do I root this phone, Ryanza's, the only step by step guide I got for this was based on downloading odin with root kernel for JPH, as you know we are running on jpjpg.
3. Are you guys experiencing lags? I'm not so far.
Would really appreciate your help, with easy shortcuts. Never used odin ..etc...but was willing to give it a try until i noticed the different kernel code.
Thanks!
I Upgraded to Froyo Through Kies. The build number is JPJPG.
The App Drawer has major lag when changing pages. It was much faster with the stock Eclair rom. GPS is still the same, it was not fixed at all. I have not noticed any improvement in Battery life either.
2. How do I root this phone, Ryanza's, the only step by step guide I got for this was based on downloading odin with root kernel for JPH, as you know we are running on jpjpg.
Click to expand...
Click to collapse
Use this, worked fine with me:
http://forum.xda-developers.com/showthread.php?t=803682
Thanks! Was able to root my phone. But still can't use Market Enabler, it require SU APP + busybox. Any idea what are these and easy was to install?
Hi:
I updated my european SGS through kies last week, but i cant become root now...
Its posible for now become root and how?
Thanks in advance
Sent from my GT-I9000 using XDA App
I also got the update through Kies last friday, nov 19th. My phone had the 3 button recovery issue, I found a fix here on xda (will get the link later, its bookmarked on another pc)
I also installed voodoo lagfix PRE6, and the phone is working like a charm, highest Quadrant score 1510. After installing voodoo lagfix, rooting is so easy. Just install superuser from the market, and bingo.
So I can confirm that JPJPG works fine with:
- Voodoo lagfix project-voodoo.org
- Flashing the boot loader to fix the 3 button recovery issue
- rooting
Need to ask a question, can anyone please backup the stock ROM and upload it somewhere? in case I ever need to go back to stock, I stupidly forgot to take a backup
melharty said:
I also got the update through Kies last friday, nov 19th. My phone had the 3 button recovery issue, I found a fix here on xda (will get the link later, its bookmarked on another pc)
I also installed voodoo lagfix PRE6, and the phone is working like a charm, highest Quadrant score 1510. After installing voodoo lagfix, rooting is so easy. Just install superuser from the market, and bingo.
So I can confirm that JPJPG works fine with:
- Voodoo lagfix project-voodoo.org
- Flashing the boot loader to fix the 3 button recovery issue
- rooting
Need to ask a question, can anyone please backup the stock ROM and upload it somewhere? in case I ever need to go back to stock, I stupidly forgot to take a backup
Click to expand...
Click to collapse
To backup stock rom, you need Rom manager premium, It will install clockwork mode recovery, let me know If you have issues with that. Rom manager premium is paid but crack is available at blackdroid.net
Lgfix: I am using Universal lagfix (last option**No-RFS Overkill JFS: turns on all options: everything is jfs+ext2 and /data/data is bound to /dbdata**), it gives me a quardant score of 2100+
You get ULF from clockwork mode (install Rom Manager*free version* from market and open the app and the 1st option installs CWM) for details see this link http://forum.xda-developers.com/showthread.php?t=734166&highlight=clockwork+mode
fawaz-sgs said:
Quick questions guys:
Just got 2.2 through Kies. I now need to re-download my apps, over 90% of them are not showing through the market, not even through search. Im guessing I have to change again to XSG like I did when I had 2.1, then root again as well to enable Market Enabler and access paid apps like I used to (which I did with Ryanza)
1. Old XSG access code (HHMM) gets rejected, new code IMEI gets rejected,is there a way to enable this without flashing etc (i'm a very low-tech person)
2. How do I root this phone, Ryanza's, the only step by step guide I got for this was based on downloading odin with root kernel for JPH, as you know we are running on jpjpg.
3. Are you guys experiencing lags? I'm not so far.
Would really appreciate your help, with easy shortcuts. Never used odin ..etc...but was willing to give it a try until i noticed the different kernel code.
Thanks!
Click to expand...
Click to collapse
Hi,
I have used CF root using Odin, its takes 3-7 seconds
Download the this file "CF-Root-JPJPA-v1.2-Busybox-1.17.1.zip" from http://forum.xda-developers.com/showthread.php?t=788108
and open Odin 1.3, its better to keep odin and above zip file in one folder, lets say in C:\.......
Unzip this zip in the same folder
Once Odin is open, click PDA to browse (downloaded Unzip file)(CF-Root-JPJPA-v1.2-Busybox-1.17.1) and Now shutdown you mobile (wait till its really off), press Volume down + power+Home simultaneously and bring your mobile in recovery mode, connect it to your computer, you will see 1st box on Odin will change its colour and it will comm 7 or 11
press start, it will reboot your mobile and you are rooted, let me know if you have any issues
For Market , download zip from post 6 and install via Clockwork mode
BLeaCHeR said:
Hi:
I updated my european SGS through kies last week, but i cant become root now...
Its posible for now become root and how?
Thanks in advance
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Hi
what is your firmware name, is it JPO/ JPA or JPJPG? (to check, in dialer type *#1234#) and is your 3 Button combination enabled??? if its not, enable it 1st from here http://forum.xda-developers.com/showthread.php?t=810686
if you have enabled 3 button combo use the method described in previous posts
fawaz-sgs said:
Thanks! Was able to root my phone. But still can't use Market Enabler, it require SU APP + busybox. Any idea what are these and easy was to install?
Click to expand...
Click to collapse
Which root you used, normally all the roots available in these forums install Su and Busybox, check in your apps if you see Busybox
if its not installed re-root the mobile using CF-root, its safe, and method is in above posts or check this thread http://forum.xda-developers.com/showthread.php?t=788108
nasgilani said:
I am going to flash the latest froyo available for Middle East and then afterwards share my experiences about
1. Stock Rom
2. Speed/ Lag
3. GPS Connectivity
4. Any new Features
5. Battery Drain
In mean while if any one got his/her hands on this Latest Froyo (November 2010) release, please share???
Click to expand...
Click to collapse
Waiting for the updates
ApnaDroid said:
Waiting for the updates
Click to expand...
Click to collapse
Under testing, will post tonight
is there a possibility to flash this rom on a jxjg2 baseband version? what code do i use in kies?
Hi guys!
I've seen a few methods how to get root access on latest .253 firmware, but this one is, I think, the easiest way available:
1. If on .253, use flashtool to flash an older version which has available OTA for .253. The one I used is: http://forum.xda-developers.com/showthread.php?t=2223827
2. Root is as simple as it gets with: http://forum.xda-developers.com/showthread.php?t=1886460 . Use 3) option to root.
3. When rooted enter "Superuser" and check "ota rootkeeper".
4. After 3. is done go to settings > apps > all > update center > clear data, to avoid force close error, then enter "update center" app on your phone and hit refresh button to get OTA .253 update notification. Download and install latest firmware.
Done!
Another guide, although the existing one is still simpler I think.
From me to you.
Do you mean this: http://forum.xda-developers.com/showthread.php?t=2283673 by "existing one"?
naga.nino said:
Do you mean this: http://forum.xda-developers.com/showthread.php?t=2283673 by "existing one"?
Click to expand...
Click to collapse
Well basically this is:
1) Go back to .434
2) and use easy root for .434
Not really easy root for .253
DoubleYouPee said:
Well basically this is:
1) Go back to .434
2) and use easy root for .434
Not really easy root for .253
Click to expand...
Click to collapse
3) and OTA update to .253
I find this method way more simple than installing dual recoveries and flashing prerooted firmwares after downgrading and stuff. My tutorial is basically: root with binary tool > OTA update. If there is simpler way to root latest .253 I would like you to paste me a link so I could learn something new.
naga.nino said:
Do you mean this: http://forum.xda-developers.com/showthread.php?t=2283673 by "existing one"?
Click to expand...
Click to collapse
I did yes, as most People I imagine will want to install CWM, so it's just doing the step before, instead of after using this method. To be fair though this is quite simple so I'll add a link to it, but under the name .253 OTA ROOT, as this thread should be called.
It's also only relevant if you can get ota...
Sent from my C6603 using Tapatalk 4 Beta
naga.nino said:
.253. The one I used is: http://forum.xda-developers.com/showthread.php?t=2223827
Click to expand...
Click to collapse
do you remember if is there Italian language in this version?
naga.nino said:
Hi guys!
I've seen a few methods how to get root access on latest .253 firmware, but this one is, I think, the easiest way available:
1. If on .253, use flashtool to flash an older version which has available OTA for .253. The one I used is: http://forum.xda-developers.com/showthread.php?t=2223827
2. Root is as simple as it gets with: http://forum.xda-developers.com/showthread.php?t=1886460 . Use 3) option to root.
3. When rooted enter "Superuser" and check "ota rootkeeper".
4. After 3. is done, enter "update center" app on your phone and hit refresh button to get OTA .253 update notification. Download and install latest firmware.
Done!
Click to expand...
Click to collapse
If this works (I haven't tried it yet) I think it is the easiest way.
Only a couple of question before try it, is there a kind of problem like reboot when mount system partition to write with this method?
And, which ROM did you use to try that?
Thank you for all!!
(Sorry for my bad english)
for me, this is the simplest one http://forum.xda-developers.com/showthread.php?t=2285608
well it's similar like you, the differences only method for upgrade to .253
fards said:
It's also only relevant if you can get ota...
Sent from my C6603 using Tapatalk 4 Beta
Click to expand...
Click to collapse
If you flash firmware I posted in first post, you always get OTA. That makes it relevant enough I guess.
incodnita said:
If this works (I haven't tried it yet) I think it is the easiest way.
Only a couple of question before try it, is there a kind of problem like reboot when mount system partition to write with this method?
And, which ROM did you use to try that?
Thank you for all!!
(Sorry for my bad english)
Click to expand...
Click to collapse
Everything works perfectly after root, and OTA. The ROM I used is posted in link in my first post.
naga.nino said:
Everything works perfectly after root, and OTA. The ROM I used is posted in link in my first post.
Click to expand...
Click to collapse
Oups, yes it is, sorry for that, I didn't see it
Ok, then tomorrow I'll try it, if I can.
Thank you!!!
My OTA app force close. Can I use PC companion to update .253 OTA?
---------- Post added at 01:10 PM ---------- Previous post was at 12:38 PM ----------
naga.nino said:
Hi guys!
I've seen a few methods how to get root access on latest .253 firmware, but this one is, I think, the easiest way available:
1. If on .253, use flashtool to flash an older version which has available OTA for .253. The one I used is: http://forum.xda-developers.com/showthread.php?t=2223827
2. Root is as simple as it gets with: http://forum.xda-developers.com/showthread.php?t=1886460 . Use 3) option to root.
3. When rooted enter "Superuser" and check "ota rootkeeper".
4. After 3. is done, enter "update center" app on your phone and hit refresh button to get OTA .253 update notification. Download and install latest firmware.
Done!
Click to expand...
Click to collapse
Hey,
I think this is the easiest! And it works for me! Many many thanks!
Need some help i'm still on 434 (Unbranded UK)
I'm new to rooting on sony. Will this method unlock bootloader if it does will i lose BE2 & DRM keys?
Please advice
jeopardise said:
My OTA app force close. Can I use PC companion to update .253 OTA?
Click to expand...
Click to collapse
Go to settings > apps > all > update center > clear data. Force close should be gone for good.
If you use PC companion for updating, you'll lose root access.
stevey1987 said:
Need some help i'm still on 434 (Unbranded UK)
I'm new to rooting on sony. Will this method unlock bootloader if it does will i lose BE2 & DRM keys?
Please advice
Click to expand...
Click to collapse
Unbranded UK still doesn't have any kind of .253 update. Flash the one in link I posted in first post, and follow other steps. In the end you'll be rooted without unlocking bootloader or losing anything.
naga.nino said:
Go to settings > apps > all > update center > clear data. Force close should be gone for good.
If you use PC companion for updating, you'll lose root access.
Click to expand...
Click to collapse
already resolved by myself.
hopefully this method still work for the next update haha
naga.nino said:
Everything works perfectly after root, and OTA. The ROM I used is posted in link in my first post.
Click to expand...
Click to collapse
It seems that doesn´t work for me, I don't know why. I'm trying it with my locked bootlader Xperia Z and my official spanish .434 update.
The issue is that when it finish to download the update using the update center (only 67.5MB, is it normal?) I push install, the phone reboots but when it is installing (with the droid in the screen), the status bar jumps to the middle of the bar and the phone boots. And when it stars a message appears on the screen that can't install the new software version, try again later.
What can I do? Maybe is the spanish version? I have some modded apps in system, I tried to put the original again but I can't remember all the modded apps.
Sorry for my bad english again.
Thanks
I managed to use giefroot root my D6603 (US version) on firmware 23.0.1.A.5.77 by downgrading to 23.0.A.2.93 without wiping the whole /data.
This is what I did: (Try at your own risk!)
1 Backup the contacts first. The contacts data will be cleared.
2 Use Flashtool to flash D6603_23.0.A.2.93_Generic_20GLOBAL.ftf. Uncheck wipe DATA.
3 Restart the device. There will be lots of annoying force close popups. For me, only two packages were reported closing: android.process.acore and android.process.media. USB debugging doesn’t work either.
4. Just close the popups and go to Settings – Apps – All. Find “Media Storage” and press “clear data” to get rid of FCs of android.process.media. USB debugging should work now.
5. Find “Contacts Storage” and press “clear data”. No more FCs of android.process.acore.
After this, no more FC popups for me. It looked normal on fw 2.93 and I tried many times to use giefroot v2 but failed. It seems like that the system exploit app CVE-2014-7911 will crash android.
6. I tried clearing data of more apps. After clearing ApplicationSettings and ConfigUpdater, giefroot v2 worked! I don’t know which one is the key. Can anyone confirm?
Hope it's helpful for you.
Thanks again! @zxz0O0
I followed your steps and after a few tries i got root. The only thing i did diferrent was that i enabled "Allow mock locations" and it worked.
Thanks @zxz0O0
carasd said:
I followed your steps and after a few tries i got root. The only thing i did diferrent was that i enabled "Allow mock locations" and it worked.
Thanks @zxz0O0
Click to expand...
Click to collapse
Yes, you are right. After my steps, one still needs to follow the instructions of giefroot by zxz0O0:
How to use
Download the tool (latest version) and extract it
Start your device and plug it to your computer
Put your device in air plane mode
Run install.bat and follow the instructions on screen
Congratulations! You should now be rooted. If you get an error "Device not rooted", try running the tool a second time.
Click to expand...
Click to collapse
It worked
This works like a charm. I followed every step to the T and im rooted. Awesome Job.
It worked
thanks for this useful tip. Step 6 was not needed with D6603_23.0.A.2.98_Customized_20DE.ftf and giefroot v2.
I've heard that you can create a pre rooted version of the latest update, is this possible or will I have to stick with the downgrade?
lalala2003 said:
I've heard that you can create a pre rooted version of the latest update, is this possible or will I have to stick with the downgrade?
Click to expand...
Click to collapse
There's already a pre-rooted version which you can flash in recovery
Thanks for this guide!
The only problem I'm having is, once rooted and with the dual-recovery installed, I can't decrypt my device in TWRP. It asks for my password, but tells me it's wrong and just asks for the password again. If I choose 'cancel' it continues but won't load anything off my sd card/internal. So I can't flash the update to .77
Anyone know why this might be?
---------- Post added at 09:45 PM ---------- Previous post was at 09:25 PM ----------
omnikai said:
Thanks for this guide!
The only problem I'm having is, once rooted and with the dual-recovery installed, I can't decrypt my device in TWRP. It asks for my password, but tells me it's wrong and just asks for the password again. If I choose 'cancel' it continues but won't load anything off my sd card/internal. So I can't flash the update to .77
Anyone know why this might be?
Click to expand...
Click to collapse
I seem to have gotten around this for now by using adb push to copy the file to the /tmp folder of my device. I still can't access internal storage, which is a pain, but at least I can finish the steps to get back to .77 (and hopefully Lollipop soon!).
omnikai said:
Thanks for this guide!
The only problem I'm having is, once rooted and with the dual-recovery installed, I can't decrypt my device in TWRP. It asks for my password, but tells me it's wrong and just asks for the password again. If I choose 'cancel' it continues but won't load anything off my sd card/internal. So I can't flash the update to .77
Anyone know why this might be?
---------- Post added at 09:45 PM ---------- Previous post was at 09:25 PM ----------
I seem to have gotten around this for now by using adb push to copy the file to the /tmp folder of my device. I still can't access internal storage, which is a pain, but at least I can finish the steps to get back to .77 (and hopefully Lollipop soon!).
Click to expand...
Click to collapse
Sorry that I know nothing about the decryption. After a quick search, it seems to me probably a bug of TWRP (github.com/TeamWin/Team-Win-Recovery-Project/issues/247).
lalala2003 said:
I've heard that you can create a pre rooted version of the latest update, is this possible or will I have to stick with the downgrade?
Click to expand...
Click to collapse
Yes. Once you root your phone and have the dual recovery installed, you can use the pre rooted image to upgrade to the latest version and keep root.
hi
hello sir. i deleted everything on your step. now i cant access my wifi. how can i return it again? thanks. noob here.
nivek4th said:
hello sir. i deleted everything on your step. now i cant access my wifi. how can i return it again? thanks. noob here.
Click to expand...
Click to collapse
Flash a FTF file but exclude the system
hi
gregbradley said:
Flash a FTF file but exclude the system
Click to expand...
Click to collapse
i already flashed a latest firmware i can't root my phone even in the old firmware. i followed all the steps.
nivek4th said:
i already flashed a latest firmware i can't root my phone even in the old firmware. i followed all the steps.
Click to expand...
Click to collapse
Then you must be doing something wrong
You can try to force a software repair using PCCompanion,
gregbradley said:
Then you must be doing something wrong
You can try to force a software repair using PCCompanion,
Click to expand...
Click to collapse
i flashed version 23.0.1.A.5.77 everything went back to normal. when i will flash again the older FW the acore stopped and media stopped gonna show again and when i deleted everything in the step it disappears but i cant root. i tick the debug and allow mock even put it into airplane mode. but CVE is showing up. not rooted.
it works, thanks a lot!
Worked perfekt. Thanks!
nivek4th said:
i flashed version 23.0.1.A.5.77 everything went back to normal. when i will flash again the older FW the acore stopped and media stopped gonna show again and when i deleted everything in the step it disappears but i cant root. i tick the debug and allow mock even put it into airplane mode. but CVE is showing up. not rooted.
Click to expand...
Click to collapse
On the older FW, did you clear the data of ApplicationSettings and ConfigUpdater as well (as in Step 6)?
Friends have achieved to root my phone, it also improves the latest system version and everything is great I put the dual recovery 2.8.2 and of there add Xposed. But after a day in the early morning the phone started to constantly reboot, try to get into recovery mode and freezes with the logo of Sony. turn off and turn on in normal mode, install the recovery again and I wipe cache and dalvik, every normal by day and in the early morning again restarts. PLEASE any solution
Has anyone managed to successfully downgrade from a LP firmware (ex. 690 or .726) back to .93, a KK firmware, without having to wipe using this method?
PLK-L01C432B190 (for B180): http://update.hicloud.com:8180/TDS/data/files/p3/s15/G939/g104/v51796/f1/full/update.zip
Just put the .zip file in your dload folder and do local update.
This update fixes issues related to icons and input methods and improves system security with the latest Google security patches. [Fixes] Fixed an issue where the Google input method can't be used when the system language is set to Serbian. Fixed an issue where the icon for the calendar downloaded from the Google Play Store and system calendar icon are the same. [Optimizations] Deleted the Huawei browser (with the Google browser remaining unchanged) for a better user experience. All user data from the Huawei browser, except for bookmarks, will be deleted. Bookmarks will be imported to the Google Chrome after you update your device. Improved device security with the latest Google security patches. Deleted quick sharing of application installation packages and images to ensure their legal use. [Update notes] 1. Before the update, make sure your phone has not been rooted. If you experience any issues during the update, please go to http://consumer.huawei.com/ or visit an authorized service center for assistance. 2. This update will not erase your personal data, but we recommend that you back up any important data before updating.
Click to expand...
Click to collapse
Hello,
Did you tried it ? 'Cause except for the security patch, i dont' think this update worth it, am i right ?
I think people who were in that version didn't got any update to B37x.
To my (limited) knowledge B180>B370 excluding betas.
in my case failed at 9% and I do not want to reset phone... staying at b180
Kikito94 said:
Hello,
Did you tried it ? 'Cause except for the security patch, i dont' think this update worth it, am i right ?
Click to expand...
Click to collapse
Yes, the screenshot taken from my phone
@zinko_pt I got B371 update notification 1.18 GB in size.
@Ing.King really strange, i did it without any issue.
By the way guys, I just released it. It's up to you, updating or not..
We who had only B371 couldn't either update. Where and when will we get B30?
Sent from my PLK-L01 using XDA-Developers mobile app
---------- Post added at 07:08 PM ---------- Previous post was at 06:44 PM ----------
Forget the comments
Sent from my PLK-L01 using XDA-Developers mobile app
memht said:
Yes, the screenshot taken from my phone
@zinko_pt I got B371 update notification 1.18 GB in size.
@Ing.King really strange, i did it without any issue.
By the way guys, I just released it. It's up to you, updating or not..
Click to expand...
Click to collapse
Well ? You made this release or it's an official one ?
Kikito94 said:
Well ? You made this release or it's an official one ?
Click to expand...
Click to collapse
Of course official :laugh: it's from hi-cloud servers. It means "I found it and shared it".
memht said:
Of course official :laugh: it's from hi-cloud servers. It means "I found it and shared it".
Click to expand...
Click to collapse
Hehe 'cause u said "i released"
Okay okay thank's for sharing
I will try it, maybe one day
Edit 1 : i decided to install it, so i removed su, put recovery stock back but error too, i don't think a miss something, keep trying...
Kikito94 said:
Hehe 'cause u said "i released"
Okay okay thank's for sharing
I will try it, maybe one day
Edit 1 : i decided to install it, so i removed su, put recovery stock back but error too, i don't think a miss something, keep trying...
Click to expand...
Click to collapse
Really soo weird, I installed it at once without facing any problem.
It doesn't need a clean B180 rom because I installed it over my usual rom. It wasn't clean.
Something must be wrong in somewhere... but where?
Back here again..
No good news, tried to instal via sd, same issue, fail at 6%
But, but, but there might be a reason, i flashed the sdk21 of xposed, and idk how to remove it.. maybe this is the cause of it....
When you installed, you had to : unroot & put the recovery back ? Or you where "clean"
I'll try tomorrow, with a rest head
Kikito94 said:
Back here again..
No good news, tried to instal via sd, same issue, fail at 6%
But, but, but there might be a reason, i flashed the sdk21 of xposed, and idk how to remove it.. maybe this is the cause of it....
When you installed, you had to : unroot & put the recovery back ? Or you where "clean"
I'll try tomorrow, with a rest head
Click to expand...
Click to collapse
Oh, when I was saying "not clean" I meant installed apps and my all data
And yes, my rom was clean if we consider root and recovery condition.
memht said:
Oh, when I was saying "not clean" I meant installed apps and my all data
And yes, my rom was clean if we consider root and recovery condition.
Click to expand...
Click to collapse
Hi,
Hmmm so maybe the xposed package.rar i've flashed made this error
Well, i'll try when i receive the H8
Or maybe i had to put the recovery of B100 instead of B180 :/
Edit 1 : When i check the local.prop, there is "ro.dual.sim.phone=false" or the PLK-L01 is a dual sim, so i don't understand ^^
Edit 2 : Flash with TWRP =
MD5's missing
coming from B180 stock /rooted /xposed.....
1.) i flashed all possible partitions i had extracted (HuaweiExtractor) from B180. (system; cust; boot; recovery)
2.) reboot
3.) i flashed full rom B180 from folder dload (vol up&down&power) to be sure to get really all parts of firmware!
4.) reboot
5.) local update b190.zip from folder dload
6.) reboot
7.) i flashed twrp rc3 with fastboot to recovery partition
8.) had rooted and installed xposed now
all works as expected! Now i am on B190.
at least i had to install some modifications to system again and recover my data partition (twrp)
all in all nearly 1 hour hard work!
non-toxic said:
coming from B180 stock /rooted /xposed.....
1.) i flashed all possible partitions i had extracted (HuaweiExtractor) from B180. (system; cust; boot; recovery)
2.) reboot
3.) i flashed full rom B180 from folder dload (vol up&down&power) to be sure to get really all parts of firmware!
4.) reboot
5.) local update b190.zip from folder dload
6.) reboot
7.) i flashed twrp rc3 with fastboot to recovery partition
8.) had rooted and installed xposed now
all works as expected! Now i am on B190.
at least i had to install some modifications to system again and recover my data partition (twrp)
all in all nearly 1 hour hard work!
Click to expand...
Click to collapse
Hi,
In fact you just cleaned up your B180 in order to instal the 190 ?
The "real" B180
Pure stock if i could say ? Sure, it will work, but i tried to install it without getting back to stock^^
uff 1 hour to achieve upgrade... pity that I have to do factory reset to make upgrade to b190, no root no open bootloader no changes to firmware despite all this I cannot upgrade normal way... very sad, bad job honor(huawei)
because i had made a backup of my apps and data with the HUAWEI backup app (update to version from PlayStore is necessary!) recovery was easy! Had to remove some blood ware and unused apps only!
then reinstalled PMplus; managed autostart and apps they should stay on if screen is off.
reinstalled my google account
all in all a little bit more than 1 hour like i told you
now i am on b190 rooted; xposed and xprivacy activ on; and of curse Viper4Android for better sound.
real easy!
Kikito94 said:
Hehe 'cause u said "i released"
Okay okay thank's for sharing
I will try it, maybe one day
Edit 1 : i decided to install it, so i removed su, put recovery stock back but error too, i don't think a miss something, keep trying...
Click to expand...
Click to collapse
How did you update it? if you were rooted then you have to flash img files manually first before doing a three button update.
DigiGoon said:
How did you update it? if you were rooted then you have to flash img files manually first before doing a three button update.
Click to expand...
Click to collapse
Hi,
I tried a lot a thing, but i prefer stay in B180 i got backup corrupted, i thought it was due to the switch version but no, so, tried via sd, internal, 3 buttons, after that an error occured, "recovery partition missing"
Well i've reset everything from B100 to get back to B180, after that, tried ota researching, but it only find the B371 doesn't matter ^^
Kikito94 said:
Hi,
I tried a lot a thing, but i prefer stay in B180 i got backup corrupted, i thought it was due to the switch version but no, so, tried via sd, internal, 3 buttons, after that an error occured, "recovery partition missing"
Well i've reset everything from B100 to get back to B180, after that, tried ota researching, but it only find the B371 doesn't matter ^^
Click to expand...
Click to collapse
Yes, as B371 is the latest one so they will push B371 only, now there are no incrementals. But I have put up a thread here, maybe sometime later I'll post the OTAs too.
Sent from my PLK-L01 using Tapatalk
*See the Addendum at the bottom of this OP for The Solve*
This thread has arisen from a particular issue that was originally thought to have arisen* by flashing a pre-rooted system image that was prepared following the method outlined by Senior Member hackarchive in "Root ANY LG G4 Variant 100% Success Directives | Root Injection | Less Bricks" (https://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586).
*later proved by Senior Member steadfasterX to be an erroneous assumption.
The issue: The H812 LG G4 (that has an un-lockable bootloader) that came from the carrier (Canada's Roger's/Fido) with Marshmallow (H81220x) installed. It was rolled back to Lollipop H81210h originally with the pre-rooted H81210n system image flashed after - the reason: both the stock and pre-rooted 'h' versions did not have the last stagefright vulnerability patch whereas the 'n' version did, hence an added level of security. However, no one had a confirmed Roger's/Fido stock H81210n kdz (Rogers/Fido is the only carrier in Canada that has the VoLTE option included and operational for the LG G4) that anybody could find a link to and when an exFAT formatted SD card was put in the pre-rooted 'n' version, it failed to recognize the format (no problem with FAT32) whereas it was recognized in the rooted earlier released 'h' version. The 4gb restriction size of FAT32 did not allow the backup of the system image with Senior Member steadfasterX's "TWRP-in-FiSH" (https://forum.xda-developers.com/g4/development/locked-twrpinfish-locked-g4-devices-t3573048) to the external sd card given the FAT32 size restriction. The exFAT recognition issue originally appeared to have arisen with the pre-rooted 'n' version when the missing original stock kdz was installed through the refurbish method with LGUP-NEW without an SD card installed or when the original system image was extracted OR, as steadfasterX has suggested, it was originally for a phone with a different kernel.
At the suggestion of steadfasterX and thanks to his work on this issue, the effort to reverse-engineer and revert to stock from the root-injection method itself has been undertaken. The work is all his, the testing to date and soft-bricking getting to this point, are mine.
Make no mistake ... this is a work-in-progress and soft-bricks and other risks, always a possibility
What you have here is a link to steadfasterX's latest revision to help unravel this issue that should not change anything if the DEBUG setting is left as it is: DEBUG=1. Follow his instructions exactly. I have run this version with DEBUG=1 with absolutely no problems and no issues rebooting after - no actual changes were made to the phone when the DEBUG=1 mode was used.
Note: Changing the 1 to a 0 will allow actual execution of the script and is not advised at this time*.
* Not advised at all as it will = Soft Brick.
Refer to the following link: https://forum.xda-developers.com/showpost.php?p=72837723&postcount=343
but please, post to this thread only if you are interested in helping/testing/solving or have any questions etc.
Thanks.
S.
Addendum: Credit for The Solve ...
Full credit for the solve goes to ReeS86- refer to his post @ReeS86
Special Thanks to all the work by steadfasterX he put into helping us get to this point.
For a quick and easy method to get an exFAT formatted SD card recognized in the pre-rooted Rogers/Fido H81210n system image: see the Addendum in my post @sdembiske
yea thats better here then there
ok lets see where it goes...
happy bricking
.
steadfasterX said:
yea thats better here then there
ok lets see where it goes...
happy bricking .
Click to expand...
Click to collapse
Here's a link to the DEBUG=1 log from revert_root_injection.sh v0.2:
https://paste.omnirom.org/view/be1a8f21
No issues/problems in executing or rebooting from the script in DEBUG=1 mode. :good:
sdembiske said:
Here's a link to the DEBUG=1 log from revert_root_injection.sh v0.2:
https://paste.omnirom.org/view/be1a8f21
No issues/problems in executing or rebooting from the script in DEBUG=1 mode. :good:
Click to expand...
Click to collapse
ok!
so now pls gimme this on your rooted device:
boot in TWRP
Code:
adb shell
mount /system <-- may complain that it is already mounted. if so ignore ;)
tar cvzf /tmp/init.tar.gz /system/etc/init.d/
exit
adb pull /tmp/init.tar.gz .
then e.g. upload the init.tar.gz here as a attachment .
.
steadfasterX said:
ok!
so now pls gimme this on your rooted device:
boot in TWRP
Code:
adb shell
mount /system <-- may complain that it is already mounted. if so ignore ;)
tar cvzf /tmp/init.tar.gz /system/etc/init.d/
exit
adb pull /tmp/init.tar.gz .
then e.g. upload the init.tar.gz here as a attachment ..
Click to expand...
Click to collapse
Here you go.
sdembiske said:
Here you go.
Click to expand...
Click to collapse
ok so far so good.
now it is "safe" to DEBUG=0 ..
give it a try :fingers-crossed:
and upload the log from the ext sd afterwards again..
.
steadfasterX said:
ok so far so good.
now it is "safe" to DEBUG=0 ..
give it a try :fingers-crossed:
and upload the log from the ext sd afterwards again...
Click to expand...
Click to collapse
No go this time either. Softbricked same as last time on the reboot - however, this time TWRP didn't freeze up and allowed the reboot from inside. Pulling the battery and trying normal power up gave the same result. No sound and couldn't get past the spinning lg logo. It'll take me a bit of time to get up and running again.
Here's the link to the log: https://paste.omnirom.org/view/19951ee0
I'm curious what security fixes and other fixes were present between the h and n versions of the Rogers H812 system software. It seems to me a good option may be to install 10h KDZ and then root, then copy any libstagefright files needed from the 10n KDZ and check to see if the vulnerabilities are fixed. I might try this out because I had no issues with the 10h firmware including the exFAT working correctly while rooted.
ReeS86 said:
I'm curious what security fixes and other fixes were present between the h and n versions of the Rogers H812 system software. It seems to me a good option may be to install 10h KDZ and then root, then copy any libstagefright files needed from the 10n KDZ and check to see if the vulnerabilities are fixed. I might try this out because I had no issues with the 10h firmware including the exFAT working correctly while rooted.
Click to expand...
Click to collapse
Good idea. I know some of the stock Motorola LTE versions were updated with the first stagefright vulnerability patch and it was able to be ported over into to copies of stock versions that didn't have it. Refer to the Miscellaneous section in the following thread https://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816
You may want to check with recognized contributor lost101, author of that thread for any suggestions.
The other approach might be to try and get the Roger's-Fido/VoLTE app/settings off the the 'h' version and see if they can be incorporated into the stock 'n' version that does handle exFAT but doesn't have VoLTE as it is carrier specific, although, I think your approach might bring more fruitful results quicker.
ReeS86 said:
I'm curious what security fixes and other fixes were present between the h and n versions of the Rogers H812 system software. It seems to me a good option may be to install 10h KDZ and then root, then copy any libstagefright files needed from the 10n KDZ and check to see if the vulnerabilities are fixed. I might try this out because I had no issues with the 10h firmware including the exFAT working correctly while rooted.
Click to expand...
Click to collapse
sdembiske said:
Good idea. I know some of the stock Motorola LTE versions were updated with the first stagefright vulnerability patch and it was able to be ported over into to copies of stock versions that didn't have it. Refer to the Miscellaneous section in the following thread https://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816
You may want to check with recognized contributor lost101, author of that thread for any suggestions.
The other approach might be to try and get the Roger's-Fido/VoLTE app/settings off the the 'h' version and see if they can be incorporated into the stock 'n' version that does handle exFAT but doesn't have VoLTE as it is carrier specific, although, I think your approach might bring more fruitful results quicker.
Click to expand...
Click to collapse
Well my first try on this would be:
Backup v10n
Flash v10H
Restore v10n system image only
See what happens. Normally there are low chances that this brick anything but there are still no guarantees..
Btw I would like to see a DEBUG=1 run on a v10h..
I wonder if there are diffs in the root injection..
.
Sent from my LG-H815 using XDA Labs
All this trouble because no bootloader unlock... what a shame
---------- Post added at 10:27 AM ---------- Previous post was at 10:21 AM ----------
ReeS86 said:
I'm curious what security fixes and other fixes were present between the h and n versions of the Rogers H812 system software. It seems to me a good option may be to install 10h KDZ and then root, then copy any libstagefright files needed from the 10n KDZ and check to see if the vulnerabilities are fixed. I might try this out because I had no issues with the 10h firmware including the exFAT working correctly while rooted.
Click to expand...
Click to collapse
What is the difference between H and N versions?
steadfasterX said:
Well my first try on this would be:
Backup v10n
Flash v10H
Restore v10n system image only
See what happens. Normally there are low chances that this brick anything but there are still no guarantees..
Btw I would like to see a DEBUG=1 run on a v10h..
I wonder if there are diffs in the root injection..
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Will try and get to it sometime over the long weekend that we have coming up here and give it a shot as well as providing the DEBUG=1 log on a v10h .
Thanks again.
sdembiske said:
Will try and get to it sometime over the long weekend that we have coming up here and give it a shot as well as providing the DEBUG=1 log on a v10h .
Thanks again.
Click to expand...
Click to collapse
You may could ask the maintainer of :
https://forum.xda-developers.com/g4/development/h815-freedom-rom-t3630056/post72866870
He made an installer for his ROM which let you select VoLTE so he may now what is needed to activate it. I know it's for the h815 but it should be similar..
.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Well my first try on this would be:
Backup v10n
Flash v10H
Restore v10n system image only
See what happens. Normally there are low chances that this brick anything but there are still no guarantees..
Btw I would like to see a DEBUG=1 run on a v10h..
I wonder if there are diffs in the root injection..
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
As suggested, here are the revert_root_injection logs (x2 - DEBUG =1 and DEBUG=0), plus the TWRP recovery log of system image restore of the 'n' version from 'h' internal.
Same problem with revert-root-injection when the DEBUG option was set to "0" to execute - i.e., soft brick ... lol.
And, perhaps not unexpected, the exFat formatted card was still not recognized but what did surprise me is that none of my settings, apps etc., were restored on the 'n' system image restore after.
Link to logs: https://gist.github.com/sdembis/89de74e401def3ed0e091c565a19e0e9
I then restored all (excluding system image) from my backup in external after the first restore attempt - it failed on the Data restore but everything was back to normal from what I could tell on the reboot.
PS: I pm'ed both you and ReeS86 the response from the rom author you suggested I contact re: the VoLTE install. He was very helpful and sounds like a good guy. Thanks for the suggestion. Much appreciated.
Best,
S.
sdembiske said:
As suggested, here are the revert_root_injection logs (x2 - DEBUG =1 and DEBUG=0), plus the TWRP recovery log of system image restore of the 'n' version from 'h' internal.
Same problem with revert-root-injection when the DEBUG option was set to "0" to execute - i.e., soft brick ... lol.
And, perhaps not unexpected, the exFat formatted card was still not recognized but what did surprise me is that none of my settings, apps etc., were restored on the 'n' system image restore after.
Link to logs: https://gist.github.com/sdembis/89de74e401def3ed0e091c565a19e0e9
I then restored all (excluding system image) from my backup in external after the first restore attempt - it failed on the Data restore but everything was back to normal from what I could tell on the reboot.
PS: I pm'ed both you and ReeS86 the response from the rom author you suggested I contact re: the VoLTE install. He was very helpful and sounds like a good guy. Thanks for the suggestion. Much appreciated.
Best,
S.
Click to expand...
Click to collapse
Hm the following is not clear for me:
You have restored the system image of N to H as suggested. Ok. And then? Does it soft brick as well?
the recovery log shows the backup only.. But it wouldn't be helpful anyways or do you had an error while restoring?
Yes using the revert script on H was 99% sure that it soft bricks as well that's why I said DEBUG=1 but it seems u like it so.. nvm
Thx to the log It looks like the root method between H and N is not different btw..
.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Hm the following is not clear for me:
You have restored the system image of N to H as suggested. Ok. And then? Does it soft brick as well?
the recovery log shows the backup only.. But it wouldn't be helpful anyways or do you had an error while restoring?
Yes using the revert script on H was 99% sure that it soft bricks as well that's why I said DEBUG=1 but it seems u like it so.. nvm
Thx to the log It looks like the root method between H and N is not different btw..
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
No, neither of the restores resulted in a soft brick. The first restore of the 'n' backed up system image (from internal) went fast with no issues but didn't have the apps and settings that I backed up - that is the TWRP log I attached in my last post. The 2nd restore (all except system image from external), done right after the first, failed on restoring Data but I was able to reboot from within TWRP and all settings and apps were back as they should have been.
Here is the link to that log: https://gist.github.com/sdembis/160047faa4b22717edf36658e5e42ea7
Any ideas as to why the reversion is failing and whether it might be able to be overcome?
Thanks again,
S.
.
sdembiske said:
No, neither of the restores resulted in a soft brick. The first restore of the 'n' backed up system image (from internal) went fast with no issues but didn't have the apps and settings that I backed up - that is the TWRP log I attached in my last post. The 2nd restore (all except system image from external), done right after the first, failed on restoring Data but I was able to reboot from within TWRP and all settings and apps were back as they should have been.
Here is the link to that log: https://gist.github.com/sdembis/160047faa4b22717edf36658e5e42ea7
Any ideas as to why the reversion is failing and whether it might be able to be overcome?
Thanks again,
S.
.
Click to expand...
Click to collapse
The idea of restoring the system image (ONLY this!) from N to H :
this was a test to see if you have the VoLTE working afterwards - was VoLTE working?
.
steadfasterX said:
The idea of restoring the system image (ONLY this!) from N to H :
this was a test to see if you have the VoLTE working afterwards - was VoLTE working?.
Click to expand...
Click to collapse
Sorry, I didn't check it because the other problem, namely exFAT was no longer recognized was still present. I'll re-check everything today.
steadfasterX said:
The idea of restoring the system image (ONLY this!) from N to H :
this was a test to see if you have the VoLTE working afterwards - was VoLTE working?.
Click to expand...
Click to collapse
Thinking this through a little - as the rooted Roger's/Fido 'h' version does have VoLTE, I would expect it to have VoLTE when the 'n' version system image with VoLTE is restored over that 'h' version. I am going to try instead taking the 'n' version without VoLTE but recogning exFat that I've rooted and restore the system image from the pre-rooted 'n' version with VoLTE but not recognizing exFat, to see if VoLTE is present. If it is, I suspect that exFAT will still not be recognized as it was with the retored 'n' version over the 'h' version, I would only end up with the same problem I have now with the pre-rooted 'n' version - VoLTE with no exFAT recognition.
Or, did you mean restoring the rooted 'n' version system image without VoLTE over the rooted 'h' version with VoLTE and exFAT recognition?
I was able to loop mount both the bell H812n and Rogers H812n rooted system images and run KDiff3 on both of the root directories. It seems there are a few config files here and there that reference VoLTE as well as the odd missing file between the two. I'm going to keep digging maybe I'll find something about ExFAT as well.
Edit: Looks like the rooted system image posted to the Canadian G4 thread is from Videotron in Quebec. Still don't see anything about ExFAT...