Related
I have a fully functional zte nubia z5s mini ( except from wifi and bt) rooted, english CWM, latest MIUI. Formatting /persist partition before installing MIUI caused the issue, there is a relevant thread explaining it all at bbs.nubia.cn/thread-112804-1-1.html (understood it using google translate).
To fix it I just need some files that were in that partition (nothing special, can be viewed with any root explorer) and get them back. Re-flashing any ROM wont do the job because that's the essence of the specific partition, to contain some files that wont be replaced by flashing a rom from recovery as I discovered by similar threads at xda for other phones.
The thing is that I cant download the files from nubia forum because to get the link I must register and registration does not work for me without any apparent reason.
Could someone make a copy of its own files ? There is nothing personal in there or phone specific / unique .. Net / BT drivers, and configuration files
As I said, nothing special needed, just copy all files / folders from /persist and make a zip .. I guess a backup from CWM would work also, never tired it (never needed to restore anything till now)
The issue is very annoying because apart from WiFi problem the phone is fully functional .. I know whats the problem, the files I need and the procedure (a simple copy) but after 3-4 days of searching have not been able to find the files ..
Could somebody please help by sending me its own files from /persist ?
Thanks in advance ..
persist_b_needEDIT (nx403a)
ztenubia said:
I have a fully functional zte nubia z5s mini ( except from wifi and bt) rooted, english CWM, latest MIUI. Formatting /persist partition before installing MIUI caused the issue, there is a relevant thread explaining it all at bbs.nubia.cn/thread-112804-1-1.html (understood it using google translate).
To fix it I just need some files that were in that partition (nothing special, can be viewed with any root explorer) and get them back. Re-flashing any ROM wont do the job because that's the essence of the specific partition, to contain some files that wont be replaced by flashing a rom from recovery as I discovered by similar threads at xda for other phones.
The thing is that I cant download the files from nubia forum because to get the link I must register and registration does not work for me without any apparent reason.
Could someone make a copy of its own files ? There is nothing personal in there or phone specific / unique .. Net / BT drivers, and configuration files
As I said, nothing special needed, just copy all files / folders from /persist and make a zip .. I guess a backup from CWM would work also, never tired it (never needed to restore anything till now)
The issue is very annoying because apart from WiFi problem the phone is fully functional .. I know whats the problem, the files I need and the procedure (a simple copy) but after 3-4 days of searching have not been able to find the files ..
Could somebody please help by sending me its own files from /persist ?
Thanks in advance ..
Click to expand...
Click to collapse
instructions:
copy the content of archive (folder "\persist" from "persist_b_needEDIT.zip") to your "\persist"
and then:
1. string in file "\persist\property\MODEM_INTERNAL_VERSION" - change to installed ver. of ROM
(source http://4pda.ru/forum/index.php?showtopic=505708&st=740#entry26719716)
//at current example "NX403A_Z0_CN_XSYPK1HD11F016"
2. BT MAC is in HEX in file "\persist\.bt_nv.bin" -- IN REVERSE ORDER!!!
"F56C98" Prefix Vendor bytes -- IN REVERSE ORDER!!! - for example compare with WiFi "Intf0MacAddress=986CF5****8A"
"05****" NIC specific bytes -- IN REVERSE ORDER!!!
example content:
01000605E8B1F56C98
---- for BT MAC 986CF5B1E805
- just open file in any HEX editor & change content of file to desired (maybe random?) digits
3. Find in "RootExplorer" files "WCNSS_qcom_wlan_nv.bin" & "WCNSS_qcom_cfg.ini" in folder /etc/wi-fi. Copy them to /persist
(source http://4pda.ru/forum/index.php?showtopic=505708&st=740#entry26719716)
4. change this string is file \persist\WCNSS_qcom_cfg.ini
with your own MAC addresses from phone box (base - Intf0MacAddress)
( && Intf1/Intf2 - use the same digits as in Intf0MacAddress ):
( Intf3MacAddress & gAPMacAddr - maybe use ramdom digits?
((source http://4pda.ru/forum/index.php?showtopic=507466&st=1780#entry29593985)
<----...
# Each byte of MAC address is represented in Hex format as XX
Intf0MacAddress=986CF5****8A
Intf1MacAddress=986CF4****8A
Intf2MacAddress=986CF7****8A
Intf3MacAddress=000AF5****FC
...
# AP MAc addr
gAPMacAddr=000AF5****ab
...--->
5. change (if needed) permissions of files according to "permisiions_list" file
ztenubia said:
I have a fully functional zte nubia z5s mini ( except from wifi and bt) rooted, english CWM, latest MIUI. Formatting /persist partition before installing MIUI caused the issue, there is a relevant thread explaining it all at bbs.nubia.cn/thread-112804-1-1.html (understood it using google translate).
To fix it I just need some files that were in that partition (nothing special, can be viewed with any root explorer) and get them back. Re-flashing any ROM wont do the job because that's the essence of the specific partition, to contain some files that wont be replaced by flashing a rom from recovery as I discovered by similar threads at xda for other phones.
The thing is that I cant download the files from nubia forum because to get the link I must register and registration does not work for me without any apparent reason.
Could someone make a copy of its own files ? There is nothing personal in there or phone specific / unique .. Net / BT drivers, and configuration files
As I said, nothing special needed, just copy all files / folders from /persist and make a zip .. I guess a backup from CWM would work also, never tired it (never needed to restore anything till now)
The issue is very annoying because apart from WiFi problem the phone is fully functional .. I know whats the problem, the files I need and the procedure (a simple copy) but after 3-4 days of searching have not been able to find the files ..
Could somebody please help by sending me its own files from /persist ?
Thanks in advance ..
Click to expand...
Click to collapse
NX403A-PERSIST
I try update via recovery ( put this file to external strorage only )
1. boot to recovery mode hold Power + Volume Down button
2. Using the Volume buttons to scroll and the Power button to select, choose "Enter
recovery mode
3. Choose apply update from external storage
4. select "reboot system now after finished update
http://fota.asus.com/delta_package/.../WW_PF500KL-12.2.2.43-13.6.5.30-fota-user.zip
This screenshoot from my phone +Station
Error Status 7
I have error:
System partition has unexpected contents
E:Error in /sdcard/UL-ASUS_TOON-WW-13.6.5.30-user.zip
(Status 7)
anyone can help me?!
Same issue as well
Getting the same "System partition has unexpected contents (Status 7 )" any idea whats wrong?
It's most likely because of root, and any changes like installing busybox, or having edited the build.prop . I had to wipe system on my padfone x reinstall lollipop 43 then install the marshmallow ota, then root 2.68 then dd the Xmodem.img I found for USA radio bands and the twrp 3.0.0.0 img to get everything working.
Also I'm not sure if flashing without wiping data partition works the same as well as starting from scratch, but I did do it all in one shot and first without data being wiped and worked fine. But I then wiped everything to see how much space I could recover in app storage. I saved myself about a gigabyte and a half to have a total of 4gb remaining after apps were installed (i have a lot of apps)
Gizoid1337 said:
It's most likely because of root, and any changes like installing busybox, or having edited the build.prop . I had to wipe system on my padfone x reinstall lollipop 43 then install the marshmallow ota, then root 2.68 then dd the Xmodem.img I found for USA radio bands and the twrp 3.0.0.0 img to get everything working.
Also I'm not sure if flashing without wiping data partition works the same as well as starting from scratch, but I did do it all in one shot and first without data being wiped and worked fine. But I then wiped everything to see how much space I could recover in app storage. I saved myself about a gigabyte and a half to have a total of 4gb remaining after apps were installed (i have a lot of apps)
Click to expand...
Click to collapse
Thanks ! It worked for me
I reinstalled ver 12.2.2.43 which really is my current version, and then proceed to install MM 13.6.5.30 with success
Gizoid1337 said:
It's most likely because of root, and any changes like installing busybox, or having edited the build.prop . I had to wipe system on my padfone x reinstall lollipop 43 then install the marshmallow ota, then root 2.68 then dd the Xmodem.img I found for USA radio bands and the twrp 3.0.0.0 img to get everything working.
Also I'm not sure if flashing without wiping data partition works the same as well as starting from scratch, but I did do it all in one shot and first without data being wiped and worked fine. But I then wiped everything to see how much space I could recover in app storage. I saved myself about a gigabyte and a half to have a total of 4gb remaining after apps were installed (i have a lot of apps)
Click to expand...
Click to collapse
Thanks to you I have updated my phone to marshmallow using twrp 3.0.0, which allowed me to re-unlock bootloader, and root my phone.
It can be done, you just need to remove a few lines in the updater-script file.
something with ro.fingerprint (that identifies the recovery, it was originally expecting stock).
Replace it inside the zip. Then transfer update to sd card or internal.
After that wipe system, then reflash .43, right after that flash the mm update.
Will take some time but it should work once everything is verified.
reflash bl unlock and twrp (just a precaution) , then you can leave.
It would say no os but ignore it.
First boot takes around 10-15 mins then presto you finally have it.
Haven't encountered any bugs yet and it freed up a lot of storage space. Makes me wonder why I had to wait for the update to come to me, so glad I'm done with that.
So that concludes the last major update for the padfone s.....
Can u help me pls? I've tried unroot ,wipe system data and reflash .43 which is my current rom but still got signature verification error. any suggestion to fix this? Thx
Justatechie said:
Thanks to you I have updated my phone to marshmallow using twrp 3.0.0, which allowed me to re-unlock bootloader, and root my phone.
It can be done, you just need to remove a few lines in the updater-script file.
something with ro.fingerprint (that identifies the recovery, it was originally expecting stock).
Replace it inside the zip. Then transfer update to sd card or internal.
.
Click to expand...
Click to collapse
which lines exactly ? cause i tried removing mine and im now getting an error in the zip
error 6 or something
dtgo said:
which lines exactly ? cause i tried removing mine and im now getting an error in the zip
error 6 or something
Click to expand...
Click to collapse
On Notepad++: (not sure about notepad, but you must get rid of ro.build.fingerprint lines and the abort command after)
Delete/Remove lines 7 through 9. If left alone or not deleted fully it will not accept the update because its looking at the recovery image.
It expects 5.0 stock recovery but it sees 6.0 twrp. (since it was built off the source of twrp 3.0.0 which is mainly compatable with 6.0+)
Thats about it.
NightbladeSinX said:
Can u help me pls? I've tried unroot ,wipe system data and reflash .43 which is my current rom but still got signature verification error. any suggestion to fix this? Thx
Click to expand...
Click to collapse
Thats odd.
You should probably Re-download or transfer the ww file again. Could just be a bad transfer of data.
Make sure you have twrp 3.0.0 and that system protection off. (it pops up on the first screen, but you can find it under twrp settings)
Justatechie said:
On Notepad++: (not sure about notepad, but you must get rid of ro.build.fingerprint lines and the abort command after)
Delete/Remove lines 7 through 9. If left alone or not deleted fully it will not accept the update because its looking at the recovery image.
It expects 5.0 stock recovery but it sees 6.0 twrp. (since it was built off the source of twrp 3.0.0 which is mainly compatable with 6.0+)
Thats about it.
Click to expand...
Click to collapse
thanks for the reply , i did that and got Error 6 but it just fails right there , no message or anything
dtgo said:
thanks for the reply , i did that and got Error 6 but it just fails right there , no message or anything
Click to expand...
Click to collapse
If it doesn't say anything about identifying the device model or checking system, then something is wrong.
Might be a bad edit or it might have gotten corrupted while transferring back into the zip.
I stick with N++ for the edits, sometimes windows file transfer can be a pain by itself while trying to replace the update script, 7zip might help.
dtgo said:
thanks for the reply , i did that and got Error 6 but it just fails right there , no message or anything
Click to expand...
Click to collapse
got it working thanks again man you've been a big help
Justatechie said:
On Notepad++: (not sure about notepad, but you must get rid of ro.build.fingerprint lines and the abort command after)
Delete/Remove lines 7 through 9. If left alone or not deleted fully it will not accept the update because its looking at the recovery image.
It expects 5.0 stock recovery but it sees 6.0 twrp. (since it was built off the source of twrp 3.0.0 which is mainly compatable with 6.0+)
Thats about it.
Thats odd.
You should probably Re-download or transfer the ww file again. Could just be a bad transfer of data.
Make sure you have twrp 3.0.0 and that system protection off. (it pops up on the first screen, but you can find it under twrp settings)
Click to expand...
Click to collapse
Thx for reply. i manage to get updated to 6.0.1 but now i lost root. i did mistake not flashing twrp before 1st boot n it replace twrp to stock rec. Is there any root method available yet? I've tried latest kingroot but it was unsuccessful. Any way is there any difference between WW and TW firmware version?
NightbladeSinX said:
Thx for reply. i manage to get updated to 6.0.1 but now i lost root. i did mistake not flashing twrp before 1st boot n it replace twrp to stock rec. Is there any root method available yet? I've tried latest kingroot but it was unsuccessful. Any way is there any difference between WW and TW firmware version?
Click to expand...
Click to collapse
You could probably flash recovery through fastboot, only if your bootloader is unlocked. If not it wont allow the flash. it would say FAILED cant flash unsigned image, but theres a chance that it might have been flashed, just check to see if changes have applied.
Assuming that you have went to the fastboot portion of your phone you can check its status.
if its not unlocked, then you have to find another way to root to flash your twrp recovery back on your phone.
Did this, but kept getting errors due to (probably) my use of xposed. Managed to soft brick my phone, and recovered it using http://forum.xda-developers.com/padfone-x/help/guide-restoring-stock-rom-recovery-t3179818
After that, had to edit updater-script to remove all checks.
What tripped me up was just how long the update reboot took. Almost half an hour. I was going to give up but decided to leave it while taking a short nap.
heres the updater script for anyone having issues
Please can someone help me?
I'm trying so hard to get this to work but I'm barely getting anywhere. What I've done (thanks to ninekaw9's guide):
- unlock bootloader
- wiped everything (yet there is still stuff in the file explorer, like the su install folder)
- using fastboot boot recovery:
-- use TWRP 2.8.7.0 to transfer files from sdcard to emmc
-- with TWRP 2.7.1.1:
--- installed WW 99.99.99.0 for KK (works)
--- installed WW 12.2.2.27 for LP & stock recovery (works)
--- installed WW 12.2.2.43 for latest LP (works)
- removed every abort line from updater script to get it to stop complaining about fingerprint/unexpected system contents
- installed modified FOTA WW 13.6.5.30 for MM (no OS change)
So after all that, I'm where I started but with no apps.
Before I found out 2.8.7.0 couldn't flash stock ROMs I flashed 12.2.2.43 after a full wipe and ended up with no System UI...
Outcomes from using different recovery to flash MM update:
2.7.1.1 with unmodified: apparently my phone is TW not WW (incorrect)
2.8.7.0 with unmodified: some weird fingerprint with omni-T00N and 5.1.1, even after wipe and stock 12.2.2.43 flash. Couldn't edit or replace the default.prop file, it would just get overwritten each time
stock with unmodified: couldn't even mount my SD card, so tried ADB sideload, got the unexpected system contents message
stock with modified (no sha1): would no longer allow me to ADB sideload (0.00x message)
TWRP (either) with modified (no prop): unexpected system contents
TWRP (either) with modified (no prop/sha1): seems to work, but upon boot to system, nothing appears to have changed.
I desperately want MM so I have a smaller system partition, then I can stop pushing updates to system to save space, and therefore won't need root so I can play Pokemon GO and use Sky Q.
That or I'm going to try Magisk... Has anyone used this on a Padfone?
If anyone can guide me through which files/folders I can delete from my phone to save space, that would be great. I know most folders are mounting points, but there's a lot of .sh files and other folders that I'm not familiar with.
I've asked in another thread where I can get TWRP 3.x for Padfone S, but nobody has replied!
Please can someone help me?
Nintynuts said:
I'm trying so hard to get this to work but I'm barely getting anywhere. What I've done (thanks to ninekaw9's guide):
- unlock bootloader
- wiped everything (yet there is still stuff in the file explorer, like the su install folder)
- using fastboot boot recovery:
- use TWRP 2.8.7.0 to transfer files from sdcard to emmc
- with TWRP 2.7.1.1:
- installed WW 99.99.99.0 for KK (works)
- installed WW 12.2.2.27 for LP & stock recovery (works)
- installed WW 12.2.2.43 for latest LP (works)
- removed every abort line from updater script to get it to stop complaining about fingerprint/unexpected system contents
- installed modified FOTA WW 13.6.5.30 for MM (no OS change)
So after all that, I'm where I started but with no apps.
Before I found out 2.8.7.0 couldn't flash stock ROMs I flashed 12.2.2.43 after a full wipe and ended up with no SystemUI...
Outcomes from using different recovery to flash MM update:
2.7.1.1 with unmodified: apparently my phone is TW not WW (incorrect)
2.8.7.0 with unmodified: some weird fingerprint with omni-T00N and 5.1.1, even after wipe and stock 12.2.2.43 flash. Couldn't edit or replace the default.prop file, it would just get overwritten each time
stock with unmodified: couldn't even mount my SD card, so tried ADB sideload, got the unexpected system contents messagestock with modified (no sha1): would no longer allow me to ADB sideload (0.00x message)
TWRP (either) with modified (no prop): unexpected system contents
TWRP (either) with modified (no prop/sha1): seems to work, but upon boot to system, nothing appears to have changed.
I desperately want MM so I have a smaller system partition, then I can stop pushing updates to system to save space, and therefore won't need root so I can play Pokemon GO and use Sky Q.
That or I'm going to try hiding root Magisk...
If anyone can guide me through which files/folders I can delete from my phone to save space, that would be great. I know most folders are mounting points, but there's a lot of .sh files and other folders that I'm not familiar with.
I've asked in another thread where I can get TWRP 3.x for Padfone S, but nobody has replied!
Please can someone help me?
Click to expand...
Click to collapse
I used twrp 3.0. Worked like a charm what I ended up doing was reflashing the .43 and then the update after replacing the updater script file here is a link to the thread with the 3.0 twrp http://forum.xda-developers.com/padfone-x/general/padfone-xs-to-stock-lollipop-root-t3263664
xantanion said:
I used twrp 3.0. Worked like a charm what I ended up doing was reflashing the .43 and then the update after replacing the updater script file here is a link to the thread with the 3.0 twrp http://forum.xda-developers.com/padfone-x/general/padfone-xs-to-stock-lollipop-root-t3263664
Click to expand...
Click to collapse
Thanks. No wonder I couldn't find it as it doesn't mention 3.0.0.0 or 3.x or any version number at all.
I have answered my own Q&A thread with a link so hopefully others can find it. Will try it now.
xantanion said:
I used twrp 3.0. Worked like a charm what I ended up doing was reflashing the .43 and then the update after replacing the updater script file here is a link to the thread with the 3.0 twrp http://forum.xda-developers.com/padfone-x/general/padfone-xs-to-stock-lollipop-root-t3263664
Click to expand...
Click to collapse
Thankfully it has worked many thanks. Unfortunately while Sky Q no longer complains about root, it does complain about my Padfone station being an external display, so still won't play videos
hi all
Near perfect build from marshmellow Aosp ended up in IMEI , BASEband unkown and NO SIM issue , xperia z ultra 6833
every thing is prefectly working CAM , wifi , gapss , rooting etc. battery is amazing and its very very fast as minimal install
i am out of options now so put to you guys to help me out i have tried almost every zip file posted ( around 10+ ) for modem fix but nothing fixes it .....!!
can any one please post a working modem fix / base band fix
CLUE
while being totally frustrated i dirty flashed few of those modem fix files and suddenly it fixes the issues and every thing started to work perfectly , thanksfully i backed up the system and boot image via twrp .. and now able to use it but cannot make a flashable zip out of it.
IDEA
can i some how convert the ext4.win partitions ( backupfiles ) into IMG files and then pack then via script into flashable zip for recovery ?? OR is there any thing from TWRP or any other recovery via i can extract IMG files of system and boot so that i can be used as base rom ?
OPTIONS I TRIED STEPS OF FAILURE
1, tried all modem .zip files ( FAILED )
2, extracted the backedup ext4.win system file via cygwin and extracted the /etc/firmware/ files and recomplied via updator script in my source folder of /system/etc/firmware files ( FAILED )
3, tried pulling the system.img via DD command successfully done , but while trying to flash it via fastboot got an error cannot load system.img i suspect due to very large size of it i.e .2 GB + i dont knwo why ? ( FAILED )
4, i tried /etc/firmware folder form a working rom and swaped with my source and recompiled via updator script ( FAILED )
try flashing stock rom with flashtool http://www.flashtool.net/downloads.php
edit: not sure what your problem is?
You dirty flashed some file that made the imei go bad? But it solved the problem?
I'm not getting it?
SUPERUSER said:
try flashing stock rom with flashtool http://www.flashtool.net/downloads.php
edit: not sure what your problem is?
You dirty flashed some file that made the imei go bad? But it solved the problem?
I'm not getting it?
Click to expand...
Click to collapse
@SUPERUSER
Follows are the steps i performed to give better idea about situation .
1, STEP 1 , i did : flashed the system and boot img files from aosp source build after which the IMEI wiped off.
2,Step 2, i search and flashed many modem.zip from xda posts but non of them worked. and IMEI issue still persists ( i tried one by one each file ) with clean flash .
3, Step 3, i tried two modem.zip dirty flash , and suddenly it worked after restart but i forgot which files i used
4, luckily before i wiped current combination i took the backups of system and boot img files
5, Problem , i need a proper modem file which can remove this issue happened in step 1 and 2 .
6 , Current solution or work around i did is , i Pulled the system and boot images from working rom and made them flashable zip .via script .. its working fine but its not a proper solution because in future if i want to edit the source then same issue will occur as i understand the issue lies with source i believe ..
I hope i made it clear as much as possible and hopefully get some help ...
pintspin said:
hi all
Near perfect build from marshmellow Aosp ended up in IMEI , BASEband unkown and NO SIM issue , xperia z ultra 6833
every thing is prefectly working CAM , wifi , gapss , rooting etc. battery is amazing and its very very fast as minimal install
i am out of options now so put to you guys to help me out i have tried almost every zip file posted ( around 10+ ) for modem fix but nothing fixes it .....!!
can any one please post a working modem fix / base band fix
CLUE
while being totally frustrated i dirty flashed few of those modem fix files and suddenly it fixes the issues and every thing started to work perfectly , thanksfully i backed up the system and boot image via twrp .. and now able to use it but cannot make a flashable zip out of it.
IDEA
can i some how convert the ext4.win partitions ( backupfiles ) into IMG files and then pack then via script into flashable zip for recovery ?? OR is there any thing from TWRP or any other recovery via i can extract IMG files of system and boot so that i can be used as base rom ?
OPTIONS I TRIED STEPS OF FAILURE
1, tried all modem .zip files ( FAILED )
2, extracted the backedup ext4.win system file via cygwin and extracted the /etc/firmware/ files and recomplied via updator script in my source folder of /system/etc/firmware files ( FAILED )
3, tried pulling the system.img via DD command successfully done , but while trying to flash it via fastboot got an error cannot load system.img i suspect due to very large size of it i.e .2 GB + i dont knwo why ? ( FAILED )
4, i tried /etc/firmware folder form a working rom and swaped with my source and recompiled via updator script ( FAILED )
Click to expand...
Click to collapse
Can you share the modem files you used to get it working?
You write you got it working and made a backup in twrp.
Can you mount the partition and pull the files?
I need:
mba.b00
modem.b01
modem.mdt
They are located in system/etc/firmware.
SUPERUSER said:
Can you share the modem files you used to get it working?
You write you got it working and made a backup in twrp.
Can you mount the partition and pull the files?
I need:
mba.b00
modem.b01
modem.mdt
They are located in system/etc/firmware.
Click to expand...
Click to collapse
thanks SU for your response , actually i just fixed it last night , i will upload the zip that worked actually for reference of others
the Rom is ready and i will upload it hopfully tonight IA.
thanks for your help
pintspin said:
thanks SU for your response , actually i just fixed it last night , i will upload the zip that worked actually for reference of others
the Rom is ready and i will upload it hopfully tonight IA.
thanks for your help
Click to expand...
Click to collapse
Hi, i have the same problem, installed NANZ Stock AOSP MarshMallow (Pure minimal ) (https://forum.xda-developers.com/xperia-z-ultra/development/marshmallow-stock-aosp-rom-t3625443) but i don't get the radio working. Hopefully you can help me?
Hi there I have responded to your question in original nanz aosp thread plz check
Thanks :good: will do
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
Hi,
I have recently been pulling build.prop from my phone using a booted twrp and mounting the system folder using twrp.
I am on linux, and the file appears in my home folder.
---fine--
I am no expert when it comes to the android system so can anyone explain this?
If I flash stock to my sony experia z2, I can pull build . prop from /system/build.prop.
However, after flashing lineage over stock, I seem to have two systems, and I pull build.prop from /system/system/build.prop?
Even if prior to flashing the stock rom with TWRP, I erase the stock rom ''system'' folder, after flashing I still have to navigate past two systems in order to get to build.prop?
I am guessing that is normal? - or am I doing something wrong?.
pootler
Thread closed on request of OP @pootler