unable to flash 34.3.A.0.194 , android 7.1.1 - Sony Xperia X Questions & Answers

fellow XDA members
Xperia X got nougat update 7.1.1 yesterday 22june2017.
I have downloaded using xperifirm (two different generics) but the fsc script is missing every-time when flashtool prepares ftf file.
and ofcourse i cannot flash it
any comments?
(btw i am using latest flashtool)

GOT IT,
i renamed 34.0.fcs (or copypaste) to 34.2.fsc
C:\Users\<username>\.flashTool\mydevices\F51XX
and flashtool worked
but when i renamed 34.1 to 34.2, flashtool stuck... so be careful!

An update, I made a copy of the 34.0.FSC and renamed the copy to be 34.3.FSC and started up flashtool.

i tried this but "those data are not in fsc script and will be skipped reset kernel cmd debug" . Is it safe?

I do not follow the OP as what he describes does not match my FlashTool 0.9.23.2 configuration. In my .flashTool\mydevices\F51XX directory I have 34.0.fsc and 34.2.fsc by default. What is missing is the 34.3.fsc required for this update. Are you saying that renaming the 34.2.fsc will not work, but renaming 34.0.fsc will?
I would be grateful if someone who has already updated could follow the proper USB logging procedure to generate the correct FSC script for us: http://www.flashtool.net/fsccreate.php

Hello,
I managed to upgrade to the 34.3.A.0.194 on my F5122 and then I performed the Sony software repair with Sony Xperia Companion and used the USB logging tool as described at http://www.flashtool.net/fsccreate.php to generate what I believe should be the correct 34.3 FSC file.
My generated 34.3.fsc is inside the attached 34.3.fsc.zip. Place the 34.3.fsc inside your C:\Users\<username>\.flashTool\mydevices\F51XX directory.
I tested it and it works, and does not give the "reset kernel cmd debug" will be skipped error, as described above if you rename the 34.2.fsc file (it does, however, give the "RESET-NON-SECURE-ADB" will be skipped error, but all previous firmware versions gave this error too). Please could someone else try this attached FSC script and see whether it works for you or not?

I managed to get the 34.3.fsc file I generated in the post above into the FlashTool Devices GitHub database, and now you should no longer have this problem as the file should be retrieved by FlashTool automatically.

It work for me. Thank a lot

Just use xflasher instead of flashtool and it will work fast and without any edits.
https://forum.xda-developers.com/crossdevice-dev/sony/dev-xflasher-command-line-flasher-t2986634

toan183 said:
It work for me. Thank a lot
Click to expand...
Click to collapse
Notice any battery improvement?

brocnical said:
I do not follow the OP as what he describes does not match my FlashTool 0.9.23.2 configuration. In my .flashTool\mydevices\F51XX directory I have 34.0.fsc and 34.2.fsc by default. What is missing is the 34.3.fsc required for this update. Are you saying that renaming the 34.2.fsc will not work, but renaming 34.0.fsc will?
I would be grateful if someone who has already updated could follow the proper USB logging procedure to generate the correct FSC script for us: http://www.flashtool.net/fsccreate.php
Click to expand...
Click to collapse
person having BOOTLOCK only can create FSC script, because XPERIA COMPANION stops working if your boot is UNLOCKED

tyktak said:
Just use xflasher instead of flashtool and it will work fast and without any edits.
https://forum.xda-developers.com/crossdevice-dev/sony/dev-xflasher-command-line-flasher-t2986634
Click to expand...
Click to collapse
Xflasher may not work with this one, because xperia X is still on sinv3 (kernel.sin)
and even if it works, Xflasher will WIPE everything! where with with flashtool you have option to update without touching userdata partition

Staxman said:
Notice any battery improvement?
Click to expand...
Click to collapse
no,
and also the volume is too low / headphone/ cant enjoy music anymore!

YasuHamed said:
person having BOOTLOCK only can create FSC script, because XPERIA COMPANION stops working if your boot is UNLOCKED
Click to expand...
Click to collapse
Yes, well I answered my own question in posts #6 and #7. This should no longer be a problem because my generated FSC is now in the Github Devices database. I did not unlock my bootloader so had no problems generating the FSC.

brocnical said:
Yes, well I answered my own question in posts #6 and #7. This should no longer be a problem because my generated FSC is now in the Github Devices database. I did not unlock my bootloader so had no problems generating the FSC.
Click to expand...
Click to collapse
thank you sir,
I don't feel like there is any need to tell you however for document purposes, please downgrade to android 6.0.1 and extract your TA.img using Dirtycow script IF you ever think of rooting your X
I did the same and i have my drm keys backed up.

Android 7.1.1
Android 7.1.1 better than Android 7.0, antutu benchmark ~84000

Related

Omnius Root Method

1. Download one of the decrypted Roms in this forum mainly the RB001 for X10i.
http://hotfile.com/dl/47479718/71300...1_DEK.rar.html In particluar.
2. Extract the zip file and then the two zip files within the folder contained into the phone and ROM folder.
3. Replace all sin files contained within the root step 1 folder EXCLUDING SYSTEM.SIN and LOADER.SIN. put in the preset.TA file. (NOTE To use the R2 Baseband Copy and overwrite files into phone folder from Step 1 and then Step 3 of ROOT! and then follow Step 4 below)
4. Re-zip PHONE Folder.
5. Copy SYSTEM.SIN into the ROM folder and replace the system_S1-SW-LIVE-AC12-0001-S1-PARTITION-WITH-SPARE.sin and rename the file to that name (Or Equivalent).
6. Re-zip ROM Folder.
7. Open Omnius and Follow Instructions.
(Omnius is quite simple just download the zip file extract the program and then load it up, once open choose the device X10 and then press the flash tab, choose the phone zip file for first drop down and the choose the rom zip file for the second drop down press ok and follow Omnius instructions on screen.)
8. Compete Step 2 and then 4 of Root to complete
NOTE-X10i and Achieves ROOT STILL.
Bare with me im writing and clearing this up as much as my fingers and brain can type
Find Root File Here http://forum.xda-developers.com/showthread.php?t=711907
Find Decrypted ROM Here http://forum.xda-developers.com/showthread.php?t=683793
Ominus Download Here: http://www.omnius-server.com/download
Respect to jerpelea for ROMS and Bin4ry for Root!
asmanthebell said:
1. Download one of the decrypted Roms in this forum.
2. Extract the zip files contained into the phone and ROM folder.
3. Replace all sin files contained within the root step 1 folder EXCLUDING SYSTEM.SIN and LOADER.SIN. put in the preset.TA file.
4. Re-zip PHONE Folder.
5. Copy SYSTEM.SIN into the ROM folder and replace the system_S1-SW-LIVE-AC12-0001-S1-PARTITION-WITH-SPARE.sin and rename the file to that name (Or Equivalent).
6. Re-zip ROM Folder.
7. Open Omnius and Follow Instructions.
NOTE-X10i and Achieves ROOT STILL.
Find Root File Here http://forum.xda-developers.com/showthread.php?t=711907
Find Decrypted ROM Here http://forum.xda-developers.com/showthread.php?t=683793
Respect to jerpelea for ROMS and Bin4ry for Root!
Click to expand...
Click to collapse
Good job man... I guess this avoids all the DeviceID finding business
So, what about step 3 in Bin4ry's tutorial? can it be done by Omnius as well?
Is this exclusive to X10i? What happens with timescape/mediascape? Anyway to keep both of them as some people are reporting to have?
j4mm3r said:
Good job man... I guess this avoids all the DeviceID finding business
So, what about step 3 in Bin4ry's tutorial? can it be done by Omnius as well?
Click to expand...
Click to collapse
See updated step 3 Above
What will happen if I did that and got root, then flashed the real R1FB001?
Am I gonna loss root?
Thanks ..
Fuzalert2k said:
Is this exclusive to X10i? What happens with timescape/mediascape? Anyway to keep both of them as some people are reporting to have?
Click to expand...
Click to collapse
To be honest i only have X10i so i couldn't say if it works or not on X10a or developer boards, Timescape is fine and Mediascape works well so far.
fast rock said:
What will happen if I did that and got root, then flashed the real R1FB001?
Am I gonna loss root?
Thanks ..
Click to expand...
Click to collapse
Yes as the root interacts with the firmware not the hardware. as far as i a aware though future solutions are imminent.
Can one use the R2BA020 and still achive root?
by missing out step 3 you are leaving your x10 on the slower older baseband
What is the situation of the phone? is every thing still there? TS and MS?
Thanks
where can I get Omnius ? is it same as flashtool>
Nimche said:
where can I get Omnius ? is it same as flashtool>
Click to expand...
Click to collapse
http://www.omnius-server.com/download
andy8271 said:
by missing out step 3 you are leaving your x10 on the slower older baseband
Click to expand...
Click to collapse
read the post it has step 3 included.
anyone used this method successfully ?
fast rock said:
What is the situation of the phone? is every thing still there? TS and MS?
Thanks
Click to expand...
Click to collapse
Yes unless you choose to get rid of them
rocketpaul said:
anyone used this method successfully ?
Click to expand...
Click to collapse
I wouldn't post it here if didn't work.
asmanthebell said:
I wouldn't post it here if didn't work.
Click to expand...
Click to collapse
I know you can get it to work, im just wondering if noobs have managed to do it too.
rocketpaul said:
I know you can get it to work, im just wondering if noobs have managed to do it too.
Click to expand...
Click to collapse
I have retried and it works every time.
i've tried the first root guid posted by bynary but i think something in step 4 gone wrogn since i dont have root. can i try this guide with omnius now or i have to repeat the other?
worked when i used the method before the edit.
now when i try it using the new 'phone.zip' it boots up , i enter debugging , i run step2.xxx and select option 6 , yellow exclamation triangle

[GUIDE] Decrypting your own branded ROM

Fastest way to decrypt your own branded ROM by Binary
Bin4ry said:
FYI:
You can also use the new tool here. Usage:
SEUSDECRYPT.BAT FILE_XXXXXXXX -> That gives you a FILE_XXXXXX.tgz -> Unzip -> Then Untar the File which comes out
If you SEUSDECRYPT the small 64kb File you get directly the loader.sin no need to unzip and untar
Regards
Bin4ry
Click to expand...
Click to collapse
You may find the ConvertTools below.. This is just sick
Old way of decrypting ROM
Below is the guide to decrypting ROM which comes from SEUS. By following this guide, you will have your branded ROM decrypted as SIN files and later you can flash back the ROM to X10 with flashtools. So you can root and debrand all you like without worry because later you can flash your branded ROM back to your X10.
Tools:
jerpelea SIN Reconstructor
http://hotfile.com/dl/52847024/13749f6/SIN_Reconstructor.rar.html
Requirement:
Your Xperia X10 must have the any version of the branded ROM installed first. If you already rooted or debranded it, you must rebrand it with your ROM first. See other threads about how to achieve this. The SIN Reconstructor tools cannot be used to extract the tho downloaded ROM files directly.
Step 1. Getting the extracted ROM from SUES
Task: Getting the targeted ROM files ready to be flashed with SEUS.
Do an update with SEUS to get your latest branded ROM, and let the ROM to be flashed to your X10. After this you will have the two files in SEUS db ready and next flashing, you don't need to download anymore and SEUS will flash it directly for you.
Task: Installing the extractor files to SEUS
Inside SIN Reconstructor, you will find com.sonyericsson.cs.usbflashnative_2.10.6.24.jar in seus directory. Backup your usbflashnative.jar from your SEUS plugin's directory somewhere else first, then copy the com.sonyericsson.cs.usbflashnative_2.10.6.24.jar file to plugin directory and then rename to the one you back up just now.
Task: Extracting ROM with dump0
Now you create a file in SEUS root. You need to create a file name dump0, make sure its dump0, not dump0.txt if you create the file using notepad and rename it. The run the SEUS update again. This will reflash your X10 then afterward, you get a lot of sign and bin files in SEUS root directory. Then you move the file somewhere else first
Task: Extracting ROM with dump1
Same as above but now you need a file name dump1, and the file dump0 must not exists in SEUS directory. After you are finished with reflash, you will have a lot of sign and bin files again, then move somewhere else.
Step 2. Identifying the bin and sign files
Because the extracted rom files are named in number, you need to identify and rename them first. When renaming, you need to rename pair of sign and bin files to the designated name.
When making SIN files, you only need to create this file below:
amss.sin
boot.sin
dsp1.sin
recovery.sin
system.sin
userdata.sin
The rest of SIN files is the same with other debranded SIN files you downloaded before which are:
amss_fs.sin
apps-log.sin
cache.sin
fota0.sin
fota1.sin
How to identify is very easy, find the file and the rename
amss file size is about 15Mb
boot file size is about 5.1Mb
dsp1 file size is about 8Mb
recovery file size is about 5.4Mb and bigger then boot.sign
system file size is the largest
userdata file size is 4Kb
When you have all this pairs renamed, copy them to SIN Extractor files directory.
Then we need to recheck the rebuild.cmd against the sign file size. Guides taken from rebuild.cmd
Code:
@echo off
@echo sizes are adjustable for every sign file
@echo if your file size differs from mine
@echo adjust count= vith the value obtained from
@echo size of .sign file -17 and correct the value
@pause
@echo amss.sin
@..\tools\dd if=../files/amss.sign bs=1 skip=13 count=4074>amss.sin
@..\tools\cat ../files/amss.bin >>amss.sin
Meaning that if the amss.sign file size is for example 5017, then you need to change the count into 5000.
If you finished to this step, you have the you decrypted rom almost ready, all you need to do is copy the amss_fs.sin, apps-log.sin, cache.sin, fota0.sin, fota1.sin from other debrand ROM you downloaded.
Then you have your decrypted ROM ready. Mission accomplished
For those asking why dump0 and dump1 will create same files, except for extra 8699.bin and 8699.sign, i just recreate the dump guide, i don't know if you just do with dump1 straightaway will get you the same thing if you do dump0 and dump1. too lazy to test.
Both Dump0 and Dump1 present will work
i really dont gettin over it,
could you please be so nice and do the decrypting of my A1 ( Austria) files?
kind regards DAuL
is not that i don't want to help. but decrypting rom requires you to flash your x10 with the targeted rom first. which means i need to reflash mine and do the whole thing again.
which part of the process give you.trouble. i'll help you solve it.
Sent from my X10i using Tapatalk
Could this thread be stickied?
bump! mod, make this stickie... please
If next root update come, which means i might reset my whole phone and root, and configure all over again, i might as well help you guys decrypt your branded ROM.
Please upload somewhere like megaupload or hotfile (except rapidshare) for me to download, and later i'll decrypt and post to the decrypted branded rom thread.
http://hotfile.com/dl/53464337/95a1a90/R2BA023_Nordic_Generic.rar.html
Can you plz decrypt this ?
Sent from my X10i using XDA App
Link broken. Upload again
Will Do Sunday, 2 more Days of holiday atm
Sent from my X10i using XDA App
just have it uploaded before root fw 26 comes. as well for anyone else which wanted for me to help decrypt their branded rom
Sent from my X10i using Tapatalk
To late i guess, i used the exploid root method and rooted the R2BA026 Nordic Generic firmware myself so its not needed anymore, but thanks anyway
MrKingLouie said:
To late i guess, i used the exploid root method and rooted the R2BA026 Nordic Generic firmware myself so its not needed anymore, but thanks anyway
Click to expand...
Click to collapse
Wow, that's good for you. Where is this exploit root method discussion anyway. Seems that i missed the posts. Even though i doubt i will use the exploit to root SingTel firmware now which is still a R2BA020 fw. hahaha.
we are couple steps behind the other, because the fw contains SingTel Timescape Live Traffic Update mods.
http://forum.xda-developers.com/showthread.php?t=740240
Seems to work on all firmwares up to 026
xeviro said:
Where is this exploit root method discussion anyway. Seems that i missed the posts.
Click to expand...
Click to collapse
It's here:
X10 Mini/Pro Root Method
You probably missed it because you thought it was about the X10 Mini/Pro. Actually, it started with instructions for using the new "exploid" root for the Mini, but then it was discovered that it also works (as is) with the X10.
The good thing about this root method is that you don't have to debrand or downgrade in order to use it. In other words, you can stay with whatever ROM you currently have and not have to lose apps, contacts, SMS, etc. But of course you can also debrand it and then root it if you want (which is nice if you want the latest firmware).
EDIT: Oops, MrKingLouie already posted the link.
Grospolina said:
It's here:
X10 Mini/Pro Root Method
You probably missed it because you thought it was about the X10 Mini/Pro. Actually, it started with instructions for using the new "exploid" root for the Mini, but then it was discovered that it also works (as is) with the X10.
The good thing about this root method is that you don't have to debrand or downgrade in order to use it. In other words, you can stay with whatever ROM you currently have and not have to lose apps, contacts, SMS, etc. But of course you can also debrand it and then root it if you want (which is nice if you want the latest firmware).
EDIT: Oops, MrKingLouie already posted the link.
Click to expand...
Click to collapse
Yes, unless your branded firmware stucks with R2BA020 like mine. Thanks for the replies anyway. I flashed mine with R2BA026 and root it.
xeviro said:
Yes, unless your branded firmware stucks with R2BA020 like mine. Thanks for the replies anyway. I flashed mine with R2BA026 and root it.
Click to expand...
Click to collapse
Cool. By the way, thanks for the tutorial. I managed to decrypt X10a Generic LAM R2BA026 with it. And heeeere it is:
X10a Generic R2BA026 (with X10Flash)
I'm trying to rip my branded rom but when i follow the steps i encounter some problems:
Step 1. after downloading the rom and flasing it to the x10 i cant find files ready & next flashed.
Step 3. I cant find the folder root in seus
Step 4. same as step 3
can someone help me?
Ok found the correct folders now but after replacing the plugin file SEUS wont start any more
ok, got it working. here are my dump files:
http://hotfile.com/dl/68373185/517b6c4/dump.rar.html
can anyone decript them for me?

Sailfish OS on X

Instructions:
https://jolla.com/sailfishxinstall/
Download:
http://images.devaamo.fi/sfe/suzu/
thanks to all the guys that worked on this port.
Kernel source:
https://github.com/mer-hybris/android_kernel_sony_msm
This make_ext4fs works for flashing on macOS
For some reason with this build the system-icons vanish for me after restarting the device once :/
I had much better results using this build.
Also by default (at least with the image I linked) only two of the 6 cpu-cores are enabled. To fix that one must add this under the init-section of the /init.loire.pwr.rc file and reboot (All credit for this go to abranson from the #sailfishos-porters irc).
Thanks for this port! are you planning to continue building for Xperia X or is a test build before official release?
Enviado desde mi F5121 mediante Tapatalk
keep going till then, also ive updated the above link
how flash it?
FuLiterary said:
how flash it?
Click to expand...
Click to collapse
read the first post
FuLiterary said:
how flash it?
Click to expand...
Click to collapse
make sure when you are flashing sailfish support only F5121 and does not support sdxc
Hello, friend! I am a Chinese user, I do not understand the tutorial, there is no mor
Jozinek said:
so only Linux or MacOS too?
Click to expand...
Click to collapse
Flashing works on macOS too. You just need to use the make_ext4fs I linked instead of the one linked on top.
janeliang34 said:
Hello, friend! I am a Chinese user, I do not understand the tutorial, there is no mor
Click to expand...
Click to collapse
extract the tar, open a terminal inside the extracted folder and run ./flash.sh
One question. Zip file with AOSP should be moved intact or only vendor folder from inside it?
Seems it has to be whole .zip.
Jozinek said:
i never make something like this in MacOS (i have Macbook Air, but also with Windows), can you write step by step how to make it. This is something totally new for me (i flashed hundreds of XPERIA smartphones, i have Emma tool, but never try this...)
Click to expand...
Click to collapse
Sure thing
First of all your bootloader needs to be unlocked. I'm assuming you already did that but if not you should read about backuping your drm-keys because otherwise they can't be recovered after unlocking your bootloader unless you do that.
If you don't have fastboot installed yet follow this guide.
After that download the first file linked at the top of this thread.
Unpack the archive (if you can't open it I recommend "the unarchiver" from the app-store).
Place both this file and the zip from the third link at the top in the unpacked folder (in the path where the flash.sh is). Don't unpack the .zip file!
After that open a terminal and navigate to your unpacked folder (if you don't know how to do that google for "terminal tutorial mac").
Run
Code:
chmod +x flash.sh
chmod +x make_ext4fs
to mark the flash-script and the make_ext4fs-file as executable.
Boot your device into fastboot mode (hold volume up while it's turned off and plug in your usb-cable) and finally run
Code:
./flash.sh
to install sailfishOS on the device.
If there is a "hybris-recovery.img" file in the directory (can't quite remember if that's the case with this build) also run
Code:
fastboot flash recovery hybris-recovery.img
to install a sailfishOS specific recovery.
After that you can reboot your device and enjoy Sailfish OS
@Jozinek
You didn't unpack the .tar.bz, inside are all files needed to flash. Than You have to move make_ext4fs, AOSP.zip and flash.fs into created (by unpacking) folder and start/cd Terminal there.
Jozinek said:
Edit3 - it worked now, it was bad make_ext4fs, thanks all of you
Click to expand...
Click to collapse
So that means you are doing a review on YouTube, right?
Friend, is there a tutorial for Windows installation? To be more detailed, this is my first contact
janeliang34 said:
Friend, is there a tutorial for Windows installation? To be more detailed, this is my first contact
Click to expand...
Click to collapse
Right now there is no windows support. The final build (which will be officially sold by Jolla) will make windows-installation possible.
If you know your way around cygwin you could probably get it to flash using windows (other than the flash.sh script there's nothing *nix-exclusive).
Is the rom stable enough for daily use ? and is Alien Dalvik available in this rom to run Android apps ?
no android dalvik or any software that needs license, this version is just community version like aosp without play store.
when flashing there's error make_ext4fs: no such file or directory, when i use the second one there's error: wrong exec format

Android Oreo updates and rollback guide

This will be basically the copy of this thread:
https://forum.xda-developers.com/p10-plus/development/downgrade-p10-plus-oreo-to-nougat-t3724382
But it seems to me that I am not the only one who didn't find it first, so I post it here
I am not responsible if you brick your device, or just damage it!
And all credit goes to @mankindtw and @NoMercyWWE
Always make a backup of your important data, and if you rollback, you need to make a factory reset!
I only tested it with L09, but should work with L29 as well
First of all, you need a P10
2. It only works with oreo firmwares
3. Download the three zip files that are required for update, these are:
update.zip
update_data_public.zip
update_all_hw.zip
Click to expand...
Click to collapse
3/b. You can download them with Firmware Finder, or just search on xda. If you want to make a rollback to Nougat, you need rollback firmwares!
3/c. update_data_public and update_all_hw comes with a slightly different name, but rename both files to these names, otherwise the update will fail!
4. Download HWOTA8 from this topic
5. Put the three update files in HWOTA8 dir
5/b. If you want to rollback, but your files in the repack folder, and run repack.bat
6. Create a new folder on your EXTERNAL sd, named HWOTA8
7. Put your three files in it, plus copy MHA_RECOVERY8_NoCheck.img, and hwota8_update.zip
8. Now install P10 Plus twrp_oreo.img, if you havent't yet:
fastboot flash recovery_ramdisk twrp_oreo.img
Click to expand...
Click to collapse
credit to @OldDroid
9. Reboot into recovery, install hwota8_update.zip it replaces your recovery with the Mate 9 one, reboots and updates
10. Done! If you downgraded, or just encounter any problems, go back in recovery, and make a factory reset!
Can I do this without an sdcard?
dmmercado23 said:
Can I do this without an sdcard?
Click to expand...
Click to collapse
I think it is possible, but you need to rewrite hwota8_update.zip, since the links there are pointing to the external sd. But I dont know what you need to write there instead
Not sure if I did this right but now my phone shows---> Build number System 8.0.0.046(02ZP)
I had showing before---> Build number System 8.0.0.046(01BN)
I don't seem to have it right still
I also have somethong like System 8.0.0.046(02BQ) but .321(C10) installed. And there were some visible updates from the C900log Oreo, eg auto shazam disappeared from the status bar.
It's frustrating lol...my old Nexus 5 was so easy compared to this device...I know I updated with something cuz I also see January 1st security patch and other little differences...everything seems to work ok but still got no themes though...how do we get it right?
Droiduser67 said:
It's frustrating lol...my old Nexus 5 was so easy compared to this device...I know I updated with something cuz I also see January 1st security patch and other little differences...everything seems to work ok but still got no themes though...how do we get it right?
Click to expand...
Click to collapse
Here he says that you need to install su, and rename three directories, but for me themes are working even without this. As soon as I try it, these steps will be added to the tutorial though.
EDIT: I followed the steps and renamed the directories, but there was no change anywhere.
Yes just tried it myself too and no change...still no themes...had an extra folder in there on mine named "optus"...not sure but the twrp and rooting work awesome but wasn't able to make a nandroid backup to my external storage...it failed
Good day,
with what firmware (please complete naimeninie) you rolled back and what was installed by this method?
---------- Post added at 12:54 AM ---------- Previous post was at 12:51 AM ----------
dmmercado23 said:
Can I do this without an sdcard?
Click to expand...
Click to collapse
Without a SD card it is impossible, with firmware via TWRP, internal memory can be reset and then the firmware will not go to the end. Therefore, the programs are located on the SD.
urn said:
Good day,
with what firmware (please complete naimeninie) you rolled back and what was installed by this method?
Click to expand...
Click to collapse
If this question is for me, I did not test the rollback (I am fine with Oreo), but I would use C432B180. You can check the description of an update in FF to see if it's a rollback one.
Here's the solution : https://youtu.be/WYSVq1TE2kI
OREO
Can anyone help me android oreo on my Huawei P10
to install?
- OS = Ubuntu 17.10
- Huawei P10 (VTR-L09)
- Bootloader unlocked
- Device rooted
Nakedchef said:
Can anyone help me android oreo on my Huawei P10
to install?
- OS = Ubuntu 17.10
- Huawei P10 (VTR-L09)
- Bootloader unlocked
- Device rooted
Click to expand...
Click to collapse
Hey, there are many ways of doing it i would recommend https://forum.xda-developers.com/showthread.php?t=3691013
[GUIDE] Huawei P10 Debrand/Rebrand/Update for Nougat&Oreo it works great. Go for the hwota rebrand way, it work like charm for me.
Sent from my [device_name] using XDA-Developers Legacy app
Perfect! I applied the update as described in the OP, then did a factory reset and relocked the bootloader (which did another factory reset). Now, at least I can't tell anymore that the phone has been unlocked and rooted...
Hello, I have a problem in the rocovery that I flash wota8_update.zip I have E: unknown command [errno]
Updater process ended with ERROR: 9
Error installing zip file '/external_sd/HWOTA8/update.zip
dukenuken said:
Hello, I have a problem in the rocovery that I flash wota8_update.zip I have E: unknown command [errno]
Updater process ended with ERROR: 9
Error installing zip file '/external_sd/HWOTA8/update.zip
Click to expand...
Click to collapse
Which TWRP are you using?

Wifi and Bluetooth not turning on - missing /persist folder

Hey guys, i'm about to give up on this Z2 - it might be a hardware issue but the software is missing the /persist folder on EVERY clean install. Wanna check that before giving up.
Basically, i got a Z2 on 23.5.A.1.291 6.0.1 next to me. Turning Wi-Fi and BT on does nothing and MAC shows 02:00:00:00:00. I tried to fix it the past 5-6 hours and i am out of ideas.
What i tried so far:
1) Installing Carbon ROM 8.1.0 along with TWRP 3.2 and SU 2.82 --> didn't fix the problem but i read in xda alot and found out it could be driver problem and missing files in /persist folder.
Turns out i don't have this folder on the Z2. Compared with my Oneplus One which has this folder. They are both Snapdragon 801.
Creating the folder does not help as it just gets deleted when the phone is rebooting (which is normal to my understanding).
2) Finding out whether i even have a /persist partition on the phone.
Didn't work as i could not get adb shell nor Android Terminal to give me proper root access. Again no problem on my OPO (just for personal comparison)
3) Tried to flash stock FTF 23.5.A.1.291 with flashtools again.
Did not work as the phone was not recognized as Xperia Z2 after updating to Carbon ROM 8.1.
4) Use Emma to install 6.0.1 again --> this worked but it would only allow me to install an older Version of 6.0.1 which had no Wi-Fi functioning as well.
5) Tried flashtool again to go to my local 23.5.A.1.291 --> after being on the "older stock 6.0.1" it allowed me to do that, again no Wi-Fi.
Now i can't check for the /persist folder since root is not installed as i am back to Stock 23.5.A.1.291 with unlocked BL.
Any ideas on how to get the stupid driver installed? It drives me nuts. Every flashing process went perfectly fine with no sign of a failing /persist partition or anything.
Same issue here i guess: https://forum.xda-developers.com/xperia-z2/help/bluetooth-wifi-problem-stock-mm-n-o-rom-t3750689
The funny thing is that the radio, sensors and everything else works perfectly fine (4G).
The wifi module bcmdhd.ko is located in system/lib/modules. It should be around 665kb.
The firmware location is system/etc/firmwares/wlan/bcmdhd which contain 3 files.
If you want root you can prepare a prerooted ftf and flash it with flashtool.
If the above files are intact and have required permission 644 then the hw could be the culprit.
I don't have the persist folder on my Z2 running 23.5.A.1.291.
fredrickz said:
The wifi module bcmdhd.ko is located in system/lib/modules. It should be around 665kb.
The firmware location is system/etc/firmwares/wlan/bcmdhd which contain 3 files.
If you want root you can prepare a prerooted ftf and flash it with flashtool.
If the above files are intact and have required permission 644 then the hw could be the culprit.
I don't have the persist folder on my Z2 running 23.5.A.1.291.
Click to expand...
Click to collapse
No such file here
Dash_k said:
No such file here
Click to expand...
Click to collapse
To see those files you need to have root permissions.
First root your phone using prerooted firmware, flash it and use a root browser. When you install the stock rooted firmware those files will be copied from system.sin. Let me know after rooting.
Just make sure you flash the system partition. It will automatically install the drivers. Also flash the stock kernel.

Categories

Resources