Hi everyone,
Just wondering if someone can help me, I have the xperia 5 iv XQ-CQ72 which I was experimenting GSI's on, I decided I wanted to go back to stock fw so I got the latest fw for my model number with xperifirm, and tried to flash with newflasher, it seems to flash fine but gives an error saying "Didn't found bootdelivery that match your device!", and the phone wont boot. It bootloops for a few minutes then gives the "your device is corrupted screen". I have tried everything I can think of (i dont usually deal with xperia phones), and would really appreciate some help. I also couldnt find a telegram / discord group to attempt to get help in, so if someone could link me one, that would be really appreciated.
Thanks
Leho said:
Hi everyone,
Just wondering if someone can help me, I have the xperia 5 iv XQ-CQ72 which I was experimenting GSI's on, I decided I wanted to go back to stock fw so I got the latest fw for my model number with xperifirm, and tried to flash with newflasher, it seems to flash fine but gives an error saying "Didn't found bootdelivery that match your device!", and the phone wont boot. It bootloops for a few minutes then gives the "your device is corrupted screen". I have tried everything I can think of (i dont usually deal with xperia phones), and would really appreciate some help. I also couldnt find a telegram / discord group to attempt to get help in, so if someone could link me one, that would be really appreciated.
Thanks
Click to expand...
Click to collapse
Are you sure it's the right firmware you need?
Also, did you try newflasher with recovery mode? Make sure as well to allow it to wipe your user data; nuking it seems all but unavoidable at this stage since a corrupt archive may be left behind
Hi, thanks for your reply,
I am using the firmware for the model number that's on the phone and printed on the box (XQ-CQ72) and I don't really want to attempt to flash a different model number firmware incase I make it worse. What do you mean by recovery mode? When I flash the phone is in flash mode with the green led, also I am clearing user data.
What do you think would be the next thing to try?
Thanks
bumping as my phone is still not booting - need an xperia expert
Leho said:
bumping as my phone is still not booting - need an xperia expert
Click to expand...
Click to collapse
Careful, the actual model number doesn't necessarily mean the right firmware; there's subcategories
Xperia 5 IV (XQ-CQ72)
The latest software and firmware versions for the Xperia 5 IV (XQ-CQ72) XperiCheck.com checks the Sony servers every 5 minutes to always display the latest information.
xpericheck.com
Check here and get the correct one for your region!!
ragu24 said:
Careful, the actual model number doesn't necessarily mean the right firmware; there's subcategories
Xperia 5 IV (XQ-CQ72)
The latest software and firmware versions for the Xperia 5 IV (XQ-CQ72) XperiCheck.com checks the Sony servers every 5 minutes to always display the latest information.
xpericheck.com
Check here and get the correct one for your region!!
Click to expand...
Click to collapse
Hi, thanks for the reply,
I have already tried flashing all of those regions firmwares as I dont know what the actual firmware is (I live in australia and this phone was a grey import), but still not booting. I see that there is a new firmware released a day ago I will try to flash that, although im not sure if its going to help. Im considering attempting to flash one for the global model number as im kinda at a dead end here. I emailed sony and they said they cant help because the phone isnt even sold here in australia so i assume they dont even know what to do with it.
Do you think that would be a good idea? Global model number firmware?
Thanks for your help
Leho said:
Hi, thanks for the reply,
I have already tried flashing all of those regions firmwares as I dont know what the actual firmware is (I live in australia and this phone was a grey import), but still not booting. I see that there is a new firmware released a day ago I will try to flash that, although im not sure if its going to help. Im considering attempting to flash one for the global model number as im kinda at a dead end here. I emailed sony and they said they cant help because the phone isnt even sold here in australia so i assume they dont even know what to do with it.
Do you think that would be a good idea? Global model number firmware?
Thanks for your help
Click to expand...
Click to collapse
Before trying anything, did you delete the TA files btw?
You did right in using recovery mode since I find fastboot mode sometimes doesn't take for newflasher, but nevertheless; just covering all bases since realistically the device should not be fighting you this much
ragu24 said:
Before trying anything, did you delete the TA files btw?
You did right in using recovery mode since I find fastboot mode sometimes doesn't take for newflasher, but nevertheless; just covering all bases since realistically the device should not be fighting you this much
Click to expand...
Click to collapse
Hi,
Yeah I did delete the ta files, do you reckon this issue is related to the error it throws at the end of the flash saying bootdelivery doesn't match?
Thanks
Leho said:
Hi,
Yeah I did delete the ta files, do you reckon this issue is related to the error it throws at the end of the flash saying bootdelivery doesn't match?
Thanks
Click to expand...
Click to collapse
Personally? Yeah
Either that or something along the way of your download or firmware integrity caused this, since it should take when it's done this way.
You didn't accept the option to trim the partition right? You skipped it?
ragu24 said:
Personally? Yeah
Either that or something along the way of your download or firmware integrity caused this, since it should take when it's done this way.
You didn't accept the option to trim the partition right? You skipped it?
Click to expand...
Click to collapse
Hi,
The first flash I did, i did select to dump the trim area, i thought it was needed if i broke the device even more. Was that the issue? damn i really feel so dumb . I thought it just dumped it, did it remove it? i still have the file
Thanks
Leho said:
Hi,
The first flash I did, i did select to dump the trim area, i thought it was needed if i broke the device even more. Was that the issue? damn i really feel so dumb . I thought it just dumped it, did it remove it? i still have the file
Thanks
Click to expand...
Click to collapse
Ahh well there you go.
Re add it or redownload the firmware in full, then only delete TA keys. Once done, reflash and don't dump them this time, and off ya go!
My understanding is that option is there so you can get deep access into the device for experimental purposes, like developing ROMs and weird stuff us mere mortals shouldn't be delving in
ragu24 said:
Ahh well there you go.
Re add it or redownload the firmware in full, then only delete TA keys. Once done, reflash and don't dump them this time, and off ya go!
My understanding is that option is there so you can get deep access into the device for experimental purposes, like developing ROMs and weird stuff us mere mortals shouldn't be delving in
Click to expand...
Click to collapse
Hi,
Just double checking, you want me to re add the dumped file to the new firmware download, delete ta and flash?
Thanks
Leho said:
Hi,
Just double checking, you want me to re add the dumped file to the new firmware download, delete ta and flash?
Thanks
Click to expand...
Click to collapse
I believe it comes included within the new firmware so adding it should be redundant if you redownload it once more (assuming you wish to do it one more time to make sure it's intact)
That being said, try without adding it first, and if it still fails, add it manually
And yes, delete the TA files in all instances.
ragu24 said:
I believe it comes included within the new firmware so adding it should be redundant if you redownload it once more (assuming you wish to do it one more time to make sure it's intact)
That being said, try without adding it first, and if it still fails, add it manually
And yes, delete the TA files in all instances.
Click to expand...
Click to collapse
Hi,
I just downloaded the latest firmware and flashed, same thing - cant find matching bootdelivery. Would you happen to know what the dump file would be called? I have it somewhere but just not sure what its called , i will try to flash with it back in the folder.
Thanks for your help
also would you think it has anything to do with my bootloader still being unlocked?
btw the actual error is:
Found boot_delivery.xml in boot folder.
- Boot delivery version: 8450-0001
- Verifying if boot delivery match with device...
searching for: PLATFORM_ID="001870E1";PLF_ROOT_HASH="CE738EFA78393FA07CAE66C2DCA711449BC36B3AB78734713A7FB08527E7DAAEEE1833BFD6EEDB2ABD968FBA981B5B35"
Didn't found bootdelivery that match your device!
[TOOL] Newflasher (xperia command line flasher)
Disclaimer: newflasher tool was made for testing and educational purposes, ME is not responsible for what you do on/with your device using newflasher, you must agree that you using newflasher on your own risk, I am not responsible if you brick...
forum.xda-developers.com
the first couple of posts here are suggesting mabye the xml is formatted badly, i will try to reformat it in a few hours when i have time
Leho said:
[TOOL] Newflasher (xperia command line flasher)
Disclaimer: newflasher tool was made for testing and educational purposes, ME is not responsible for what you do on/with your device using newflasher, you must agree that you using newflasher on your own risk, I am not responsible if you brick...
forum.xda-developers.com
the first couple of posts here are suggesting mabye the xml is formatted badly, i will try to reformat it in a few hours when i have time
Click to expand...
Click to collapse
Hi,
So ive gotten further by adding the platform id into the boot delivery file, although it now says
Found boot_delivery.xml in boot folder.
- Boot delivery version: 8450-0001
- Verifying if boot delivery match with device...
searching for: PLATFORM_ID="001870E1";PLF_ROOT_HASH="CE738EFA78393FA07CAE66C2DCA711449BC36B3AB78734713A7FB08527E7DAAEEE1833BFD6EEDB2ABD968FBA981B5B35"
Found bootdelivery match: COMMERCIAL_001870E1
TA file: PDX224_XBootConfig_MiscTA.ta
Processing ./boot/PDX224_XBootConfig_MiscTA.ta
- Unable to open ./boot/PDX224_XBootConfig_MiscTA.ta!
because I deleted all the ta files, should I not delete the ta inside boot folder? phone is still bootlooping :/
Thanks
Leho said:
Hi,
So ive gotten further by adding the platform id into the boot delivery file, although it now says
Found boot_delivery.xml in boot folder.
- Boot delivery version: 8450-0001
- Verifying if boot delivery match with device...
searching for: PLATFORM_ID="001870E1";PLF_ROOT_HASH="CE738EFA78393FA07CAE66C2DCA711449BC36B3AB78734713A7FB08527E7DAAEEE1833BFD6EEDB2ABD968FBA981B5B35"
Found bootdelivery match: COMMERCIAL_001870E1
TA file: PDX224_XBootConfig_MiscTA.ta
Processing ./boot/PDX224_XBootConfig_MiscTA.ta
- Unable to open ./boot/PDX224_XBootConfig_MiscTA.ta!
because I deleted all the ta files, should I not delete the ta inside boot folder? phone is still bootlooping :/
Thanks
Click to expand...
Click to collapse
hmm didnt work, i added back that single .ta file:
Found boot_delivery.xml in boot folder.
- Boot delivery version: 8450-0001
- Verifying if boot delivery match with device...
searching for: PLATFORM_ID="001870E1";PLF_ROOT_HASH="CE738EFA78393FA07CAE66C2DCA711449BC36B3AB78734713A7FB08527E7DAAEEE1833BFD6EEDB2ABD968FBA981B5B35"
Found bootdelivery match: COMMERCIAL_001870E1
TA file: PDX224_XBootConfig_MiscTA.ta
Processing ./boot/PDX224_XBootConfig_MiscTA.ta
- Partition: 2
- Unit: 84F (2127)
- Unit size: 0x59
download:00000059
OKAY.
Write-TA:2:2127
OKAY.
- Unit: 8FD (2301)
- Unit size: 0x1
download:00000001
OKAY.
Write-TA:2:2301
OKAY.
SIN file: bootloader_X_BOOT_SM8450_LA2_0_T_108_X-FLASH-ALL-6348.sin
Processing bootloader_X_BOOT_SM8450_LA2_0_T_108_X-FLASH-ALL-6348.sin
- setting up inflate...
- infflating, please wait...
..
- inflate returned: 0
- gzpipe: ok.
- gunziped ok.
- Extracting from bootloader_X_BOOT_SM8450_LA2_0_T_108_X-FLASH-ALL-6348.sin
- Extracting signature bootloader.cms
- Uploading signature C:\Users\user\Downloads\XQ-CQ72_Customized SEA_64.1.A.0.869\boot\bootloader.cms
download:00000896
OKAY.
signature
OKAY.
- Extracting sparse chunk bootloader.000
- Uploading sparse chunk C:\Users\user\Downloads\XQ-CQ72_Customized SEA_64.1.A.0.869\boot\bootloader.000
download:00b66000
OKAY.
Partition: bootloader have slot: yes
erase:bootloader_b
OKAY.
flash:bootloader_b
OKAY.
- End of bootloader_X_BOOT_SM8450_LA2_0_T_108_X-FLASH-ALL-6348.sin
same boot loop then corrupted issue :/
Leho said:
hmm didnt work, i added back that single .ta file:
Found boot_delivery.xml in boot folder.
- Boot delivery version: 8450-0001
- Verifying if boot delivery match with device...
searching for: PLATFORM_ID="001870E1";PLF_ROOT_HASH="CE738EFA78393FA07CAE66C2DCA711449BC36B3AB78734713A7FB08527E7DAAEEE1833BFD6EEDB2ABD968FBA981B5B35"
Found bootdelivery match: COMMERCIAL_001870E1
TA file: PDX224_XBootConfig_MiscTA.ta
Processing ./boot/PDX224_XBootConfig_MiscTA.ta
- Partition: 2
- Unit: 84F (2127)
- Unit size: 0x59
download:00000059
OKAY.
Write-TA:2:2127
OKAY.
- Unit: 8FD (2301)
- Unit size: 0x1
download:00000001
OKAY.
Write-TA:2:2301
OKAY.
SIN file: bootloader_X_BOOT_SM8450_LA2_0_T_108_X-FLASH-ALL-6348.sin
Processing bootloader_X_BOOT_SM8450_LA2_0_T_108_X-FLASH-ALL-6348.sin
- setting up inflate...
- infflating, please wait...
..
- inflate returned: 0
- gzpipe: ok.
- gunziped ok.
- Extracting from bootloader_X_BOOT_SM8450_LA2_0_T_108_X-FLASH-ALL-6348.sin
- Extracting signature bootloader.cms
- Uploading signature C:\Users\user\Downloads\XQ-CQ72_Customized SEA_64.1.A.0.869\boot\bootloader.cms
download:00000896
OKAY.
signature
OKAY.
- Extracting sparse chunk bootloader.000
- Uploading sparse chunk C:\Users\user\Downloads\XQ-CQ72_Customized SEA_64.1.A.0.869\boot\bootloader.000
download:00b66000
OKAY.
Partition: bootloader have slot: yes
erase:bootloader_b
OKAY.
flash:bootloader_b
OKAY.
- End of bootloader_X_BOOT_SM8450_LA2_0_T_108_X-FLASH-ALL-6348.sin
same boot loop then corrupted issue :/
Click to expand...
Click to collapse
You need to also kill the TA file inside the boot folder. They all must go. Did you follow the video I gave you to the letter? It shows that step there as well
Based on your logs, it appears as if you may have forgotten it
See 2:22
Related
Hi all, I have a TS 1/8/2100, firmware 20140513.
TWRP and Bluetooth tether ROM are available for firmware 20140328 only. Past conversations make me think there won't be any update soon.
A solution would be to install previous firmware, then TWRP, then update firmware. But partitions changed in between.
According to this SP Flash Tool can also physically format a partition if you can get a partition management table (PMT). The scatter file describes logical partitions, but it seems you can also add PMT. (After backup with MTKDroidTool, click "prepare Blocks for FlashTool")
Knowing this, provided that hardware is relatively unchanged, it could be possible for newest TS to enjoy TWRP happiness.
I would like to try, if someone could be kind enough to give me a stock backup for TS 1-8-2100 firmware 20140328 with PMT. (there sould be a file called MT6572_Android_scatter_emmc_PMT.txt)
I need you to help me help you to help me help you.
thx.
MrTip said:
Hi all, I have a TS 1/8/2100, firmware 20140513.
TWRP and Bluetooth tether ROM are available for firmware 20140328 only. Past conversations make me think there won't be any update soon.
A solution would be to install previous firmware, then TWRP, then update firmware. But partitions changed in between.
According to this SP Flash Tool can also physically format a partition if you can get a partition management table (PMT). The scatter file describes logical partitions, but it seems you can also add PMT. (After backup with MTKDroidTool, click "prepare Blocks for FlashTool")
Knowing this, provided that hardware is relatively unchanged, it could be possible for newest TS to enjoy TWRP happiness.
I would like to try, if someone could be kind enough to give me a stock backup for TS 1-8-2100 firmware 20140328 with PMT. (there sould be a file called MT6572_Android_scatter_emmc_PMT.txt)
I need you to help me help you to help me help you.
thx.
Click to expand...
Click to collapse
Here you go - hope it's what you're looking for..
Tigerite said:
Here you go - hope it's what you're looking for..
Click to expand...
Click to collapse
No, it's not. The key element of my message is
with PMT. (there sould be a file called MT6572_Android_scatter_emmc_PMT.txt)
Click to expand...
Click to collapse
Thank you anyway.
That's all that was generated by the tool I'm afraid, I followed the steps from the link you provided too, but still no joy. It only produces the standard one, no PMT suffix.
Tigerite said:
That's all that was generated by the tool I'm afraid, I followed the steps from the link you provided too, but still no joy. It only produces the standard one, no PMT suffix.
Click to expand...
Click to collapse
That's unfortunate. Did you click on "prepare Blocks for FlashTool" after backup ? I'll try myself asap to confirm the procedure.
Yes I did, but no PMT text file in the relevant folder..
Tigerite said:
Yes I did, but no PMT text file in the relevant folder..
Click to expand...
Click to collapse
Well, the procedure is correct. It appears that PMT can be (or not) in scatter file without any difference in the filename. So you have to check by yourself, as I did, if you want to format. (look for many lines per partition, like 'physical_start_addr' and 'linear_start_addr')
You have to select "format+download" in "sp flash tools" to format everything (including preloader, so be carefull).
Take all precautions: Backup everything, including userdata and cache partition, because sp flash tools will ask for it if you have to format. Do not forget to backup nvram.
Doing this, I successfully formatted the TS and installed previous firmware, 20140328.
Sadly, the TS won't boot. Here lies my hope to get TWRP and bt tether ROM working without update from its creator...
So, back to firmware 20140513.
After the new format+backup, TS boot normally, but I had a "IMEI invalid" error. So, I used MTKdroidtools to restore nvram the same way I previously backed it up.
Complete 'format+download' is to be used if you messed up with partitions or if partitions changed.
Could be usefull, this was to let you know how.
MrTip said:
Well, the procedure is correct. It appears that PMT can be (or not) in scatter file without any difference in the filename. So you have to check by yourself, as I did, if you want to format. (look for many lines per partition, like 'physical_start_addr' and 'linear_start_addr')
You have to select "format+download" in "sp flash tools" to format everything (including preloader, so be carefull).
Take all precautions: Backup everything, including userdata and cache partition, because sp flash tools will ask for it if you have to format. Do not forget to backup nvram.
Doing this, I successfully formatted the TS and installed previous firmware, 20140328.
Sadly, the TS won't boot. Here lies my hope to get TWRP and bt tether ROM working without update from its creator...
So, back to firmware 20140513.
After the new format+backup, TS boot normally, but I had a "IMEI invalid" error. So, I used MTKdroidtools to restore nvram the same way I previously backed it up.
Complete 'format+download' is to be used if you messed up with partitions or if partitions changed.
Could be usefull, this was to let you know how.
Click to expand...
Click to collapse
What exactly are you trying to do?
kuronosan said:
What exactly are you trying to do?
Click to expand...
Click to collapse
Install last firmware known to be working with twrp.
Did that.
The device doesn't boot anymore.
Revert to previous backup.
Did that.
I like to see things by myself.
It's not your firmware that's the problem. I'm running twrp on the latest firmware without issue.
kuronosan said:
It's not your firmware that's the problem. I'm running twrp on 20140513 firmware without issue.
Click to expand...
Click to collapse
I can only rely on testimonies on this very forum, but I have not seen a single person succesfully installed twrp on firmware 20140513.
I have seen successfull install on previous firmware, and then OTA upgrade.
What is it for you ?
It is exactly what I told you. It's up to you to believe me or not.
kuronosan said:
It is exactly what I told you. It's up to you to believe me or not.
Click to expand...
Click to collapse
You didn't told me if its an install on 20140513 firmware or if it's an upgrade from previous firmware.
kuronosan said:
EU 1/8 users who have the new aluminum watch or who received their units after May 13th need to click here and also need to remember that recovery may not work (although it probably won't work before this anyway).
Click to expand...
Click to collapse
I understand you agree there is a problem with twrp 2.7.1.0 on newer devices.
You'll notice I did say new devices. Not new firmware.
kuronosan said:
You'll notice I did say new devices. Not new firmware.
Click to expand...
Click to collapse
Ok then, you win by default. Look at me asking a simple question while you obviously rather going back an forth playing fallacy pong. Please forgive me if I cut this short. I'll click on Thank You anyway.
Anyway to get back to the thread.. I've tried everything, booting in recovery, running MTK Droid Tools as Administrator, installing busybox again - but still no PMT file. I'm all out of ideas now..
Tigerite said:
Anyway to get back to the thread.. I've tried everything, booting in recovery, running MTK Droid Tools as Administrator, installing busybox again - but still no PMT file. I'm all out of ideas now..
Click to expand...
Click to collapse
That's OK. It appears that PMT can be (or not) in scatter file without any difference in the filename. (If you look in the file and see many lines per partition, like 'physical_start_addr' and 'linear_start_addr', you have PMT)
So I found what I was looking for, thank you.
MrTip said:
Ok then, you win by default. Look at me asking a simple question while you obviously rather going back an forth playing fallacy pong. Please forgive me if I cut this short. I'll click on Thank You anyway.
Click to expand...
Click to collapse
No one is trying to win. I have a good deal of experience with MTK devices based on my researching various methods of backup/restore/flash/etc and I was offering a hand.
You can play one-person pong with yourself and claim fallacy all you want or you can get off your high horse.
Up to you. I have work to do.
TWRP Install on newest firmware + OTA
got watch on 7/26. did OTA. firmware date 5/27/2014. unable to install TWRP via any method including shell DD command. well it installs but on entry I just get on the old andy with red ! showing. It seems like a watchdog timers reboots it after a few minutes and all is back to the way it was.
Which TWRP did you use?
Did my best to avoid having to ask for help, but looks like I've run out of ideas. I've got a 7840 that currently refuses to boot past the recovery screen, thanks (probably) to my own incompetence. Here's what happened along the way to this point:
First, probably important to note: my tablet is a Chinese-released 7840 running 5.0.2 Lollipop. The hardware is identical from what I can tell, but the software was definitely a bit tweaked as there were no Google services installed. (And sideloading any of the Google services always failed no matter how I went about it.) This is basically why I decided to start messing around with things.
Attempted to load the developer firmware. Wound up in the dreaded "Intel Inside" bootloop, but thanks to @xBIGREDDx and his unbrick.zip (http://forum.xda-developers.com/showpost.php?p=60663442&postcount=2) I was able to return to normal booting. No matter how many times I attempted to flash the open source firmware, I always got stuck in the bootloop and had to flash the unbrick.zip to be able to do anything. No ability to exit the bootloop in order to reach the bootloader meant this was a big impasse.
I then decided to use the tethered CWM method to root the device for the purposes of giving sideloading the Play Store another try. That worked just fine and I was able to root my 7840 without a hitch. I then created a nandroid backup (which suspiciously didn't generate an MD5 file) in case I managed to really screw things up trying to sideload the Google Services.
That's when I thought wiping and recovering the 4.4.4 Kit Kat nandroid backup might be a good idea. This of course didn't work, so I wiped and restored my own 5.0.2 backup. However, at this point things wouldn't boot no matter what I did. I would see the boot screen with the Dell logo and the Lollipop-style ANDROID text, but after a couple of minutes everything would reboot and after a couple of tries the device would boot to recovery and just sit.
After fiddling around with trying different restore methods, I decided to see if I could flash the developer firmware to no avail. (Unable to write to OSIP, security error, etc.) Then I gave @anggusss's 5.0.1 OTA update.zip a try. (http://forum.xda-developers.com/showpost.php?p=60632439&postcount=21) That gave me a different error:
"Can't install this package (Fri Apr 24 13:29:34 CST 2015) over newer build (Fri Apr 24 13:58:18 CST 2015)."
Frustrating to see that a build a half hour newer might be all I need. So, if any of you happen to have captured the 5.0.2 OTA build (or can help me tweak the 5.0.1 build to report itself as newer), would you mind giving me a hand? Would be most appreciative. I've written to Dell open-source support but don't expect to hear back for another week or so. It'd be nice to not be using the Venue as a paperweight for a week.
wirebook said:
No matter how many times I attempted to flash the open source firmware, I always got stuck in the bootloop and had to flash the unbrick.zip to be able to do anything. No ability to exit the bootloop in order to reach the bootloader meant this was a big impasse.
Click to expand...
Click to collapse
Out of interest, how was the tablet booted when you flashed the unbrick.zip (did you volup + power or just regular boot?) ?
Going back to the open-source firmware won't help, because they 4.x to 5.x transition included a re-partitioning, and the bootloader in the 4.x firmware doesn't understand the new partition scheme.
If you boot with the vol. down key held, do you get into fastboot mode? If you can, then you should be able to flash a system image and boot image. I have those pulled from my device; I can post them for you to try later tonight.
anggusss said:
Out of interest, how was the tablet booted when you flashed the unbrick.zip (did you volup + power or just regular boot?) ?
Click to expand...
Click to collapse
I've never gotten vol. up + power to do anything, is that normal? Only vol. down + power, and that'll get me into fastboot mode.
xBIGREDDx said:
Going back to the open-source firmware won't help, because they 4.x to 5.x transition included a re-partitioning, and the bootloader in the 4.x firmware doesn't understand the new partition scheme.
If you boot with the vol. down key held, do you get into fastboot mode? If you can, then you should be able to flash a system image and boot image. I have those pulled from my device; I can post them for you to try later tonight.
Click to expand...
Click to collapse
Ah, well this sounds like it's my problem, then. If you can get those images to me to try I'd be most appreciative! Should be able to give it a shot as I'm still able to get into fastboot.
wirebook said:
Ah, well this sounds like it's my problem, then. If you can get those images to me to try I'd be most appreciative! Should be able to give it a shot as I'm still able to get into fastboot.
Click to expand...
Click to collapse
system.img
This is inside a .zip file because I don't know how to get only the important bits, so I got the whole /system partition. Just unzip then 'fastboot flash system system.img'
boot.img
This is straight from the OTA zip.
You will be pre-rooted. Let me know if this goes well. :good:
xBIGREDDx said:
system.img
This is inside a .zip file because I don't know how to get only the important bits, so I got the whole /system partition. Just unzip then 'fastboot flash system system.img'
boot.img
This is straight from the OTA zip.
You will be pre-rooted. Let me know if this goes well. :good:
Click to expand...
Click to collapse
Thanks a lot for those! Flashed both boot and system, though the system gave me some sort of error on my machine ("Invalid sparse file format at header magi") and then continued to flash something ("sending sparse 'system'"). I saw the red text of some sort of error on the tablet but wasn't able to read it fast enough. The system flash did seem a bit suspiciously fast, though...
Anyway, now waiting to see if anything boots. Been sitting on the Dell/Powered By Android screen for a couple of minutes, though, so if nothing else it looks like I've at least found myself in a new place. Will try reflashing if no improvement and then get back with results!
Sorry if this is considered spamming my own thread, but didn't seem right to just edit my earlier post.
Couldn't get the system image to flash. First got the error about needing to flash as a sparse system, which seemed to be fine. But when the device tried to write the sparse chunk to the partition, it threw an error. ("remote: flash_cmds error!") Thought this might've been a bug of my particular version of adb/fastboot, but updating or trying a different version didn't work any better. In fact, things got worse as I can't even run fastboot on my machine (Windows) anymore without the program crashing on me.
Jumped over onto my Mac and things seemed to be going better, but no progress was made. Still threw that error whenever it came time to write that first sparse chunk. Might my partition table be totally out of whack? (If so, how do I go about fixing it without easy access to an adb shell?)
In other news, I realized the back of the tab has "Venue 8 784001" engraved on it, so there might be hardware / bootloader changes that I can't beat...
Well, I'm not 100% sure it's going to be able to flash the system.img correctly, I thought I could just pull it from my device and it would flash fine, but apparently not. It would be interesting to see what your partition table looks like, but I don't know of a way to get that without having a root shell.
If you have a hex editor or know how to use dd, try chopping off like 200 MB from the end of the image (I think it's all zeroes for at least that much) and see if it flashes then.
If you don't know how to do that, I could upload a modified image for you.
xBIGREDDx said:
Well, I'm not 100% sure it's going to be able to flash the system.img correctly, I thought I could just pull it from my device and it would flash fine, but apparently not. It would be interesting to see what your partition table looks like, but I don't know of a way to get that without having a root shell.
If you have a hex editor or know how to use dd, try chopping off like 200 MB from the end of the image (I think it's all zeroes for at least that much) and see if it flashes then.
If you don't know how to do that, I could upload a modified image for you.
Click to expand...
Click to collapse
wirebook said:
Sorry if this is considered spamming my own thread, but didn't seem right to just edit my earlier post.
Couldn't get the system image to flash. First got the error about needing to flash as a sparse system, which seemed to be fine. But when the device tried to write the sparse chunk to the partition, it threw an error. ("remote: flash_cmds error!") Thought this might've been a bug of my particular version of adb/fastboot, but updating or trying a different version didn't work any better. In fact, things got worse as I can't even run fastboot on my machine (Windows) anymore without the program crashing on me.
Jumped over onto my Mac and things seemed to be going better, but no progress was made. Still threw that error whenever it came time to write that first sparse chunk. Might my partition table be totally out of whack? (If so, how do I go about fixing it without easy access to an adb shell?)
In other news, I realized the back of the tab has "Venue 8 784001" engraved on it, so there might be hardware / bootloader changes that I can't beat...
Click to expand...
Click to collapse
When you dump an image is raw.ext4 it has to be converted to sparse image format for android 5.0.2
social-design-concepts said:
When you dump an image is raw.ext4 it has to be converted to sparse image format for android 5.0.2
Click to expand...
Click to collapse
Well I found the source for img2simg but it won't do me much good... you wouldn't happen to have a pre-built tool handy would you?
xBIGREDDx said:
Well I found the source for img2simg but it won't do me much good... you wouldn't happen to have a pre-built tool handy would you?
Click to expand...
Click to collapse
I think the image you passed me already employed some kind of compression on it, as I was getting errors about an invalid sparse data header or something like that. (The size on the disk was also less than the reported image size.) Unfortunately I'm unable to mount or convert it on any of my machines so I'm a bit useless.
Thanks everyone for all the help you've been, by the way!
wirebook said:
I think the image you passed me already employed some kind of compression on it, as I was getting errors about an invalid sparse data header or something like that. (The size on the disk was also less than the reported image size.) Unfortunately I'm unable to mount or convert it on any of my machines so I'm a bit useless.
Thanks everyone for all the help you've been, by the way!
Click to expand...
Click to collapse
It's just a dump straight from my system partition. I don't have my tablet with me so I'm not certain on file paths but essentially I did:
dd if=/dev/block/by-name/system of=/storage/sdcard1/system.img
So it's a raw dump of the system partition, whatever happened to be in there.
I think the fastboot command tries to sparse things on its own, but fails?
If you want to try re-partitioning (could be dangerous, could be harmless), try these commands with the partition file from the OTA package:
EDIT: For anyone else coming along, don't do this, it didn't work out well for wirebrook. /EDIT
Code:
fastboot oem start_partitioning
fastboot flash /tmp/partition.tbl kk2lp_partition.tbl
fastboot oem partition /tmp/partition.tbl
fastboot erase system
fastboot erase cache
fastboot oem stop_partitioning
You may also want to erase data while you're in there.
xBIGREDDx said:
It's just a dump straight from my system partition. I don't have my tablet with me so I'm not certain on file paths but essentially I did:
dd if=/dev/block/by-name/system of=/storage/sdcard1/system.img
So it's a raw dump of the system partition, whatever happened to be in there.
I think the fastboot command tries to sparse things on its own, but fails?
Click to expand...
Click to collapse
That must be what's happening. I'll fiddle with things a bit more later on. It's a bummer there aren't any custom ROMs I could simply flash as an alternative to getting stock up and running...
xBIGREDDx said:
Well I found the source for img2simg but it won't do me much good... you wouldn't happen to have a pre-built tool handy would you?
Click to expand...
Click to collapse
xBIGREDDx said:
It's just a dump straight from my system partition. I don't have my tablet with me so I'm not certain on file paths but essentially I did:
dd if=/dev/block/by-name/system of=/storage/sdcard1/system.img
So it's a raw dump of the system partition, whatever happened to be in there.
I think the fastboot command tries to sparse things on its own, but fails?
Click to expand...
Click to collapse
It's looking for the sparse magic header that's not there I can when I get home you could also try to use 7zip to compress it to a .gz but I believe Intel stopped support for that format in 4.4.4.
I'm at work I have it at home if your on Linux and want to convert it.
social-design-concepts said:
It's looking for the sparse magic header that's not there I can when I get home you could also try to use 7zip to compress it to a .gz but I believe Intel stopped support for that format in 4.4.4.
I'm at work I have it at home if your on Linux and want to convert it.
Click to expand...
Click to collapse
Not sure this'll be useful for me any more because... (see below)
xBIGREDDx said:
If you want to try re-partitioning (could be dangerous, could be harmless), try these commands with the partition file from the OTA package:
Code:
fastboot oem start_partitioning
fastboot flash /tmp/partition.tbl kk2lp_partition.tbl
fastboot oem partition /tmp/partition.tbl
fastboot erase system
fastboot erase cache
fastboot oem stop_partitioning
You may also want to erase data while you're in there.
Click to expand...
Click to collapse
Gave this a shot and partitioning seemed to work just fine. Flashing the OTA boot.img worked just fine, and attempting to flash your system.img once again threw an error at me. Thought I'd perform a reboot at this point (bad idea!) to see what I was working with and then I found myself with @anggusss' USB screen. (http://forum.xda-developers.com/showpost.php?p=60675581&postcount=5) Probably should've tried flashing a something else just to see if that did anything.
Guessing I've now got a brick, because I'm no longer able to get it to register with Fastboot. I can, however, flash the open-source firmware and the unbrick.zip firmware, which reacts exactly like when @anggusss did it. We'll have to see if Dell ever gets back to my original query for help, otherwise might have to look into contacting Dell for a replacement.
You might have better luck, just using one of the tethered TWRP recoveries, If someone with a working system backups up system via TWRP recovery and shares it you could use the TWRP recovery to restore it.
I have Linux version tethered TWRP up and SDC has Windows version of tethered TWRP up.
Linux version
http://forum.xda-developers.com/android/development/linux-version-twrp-2-8-6-0-tethered-t3123075
Windows Version
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
vampirefo said:
You might have better luck, just using one of the tethered TWRP recoveries, If someone with a working system backups up system via TWRP recovery and shares it you could use the TWRP recovery to restore it.
I have Linux version tethered TWRP up and SDC has Windows version of tethered TWRP up.
Linux version
http://forum.xda-developers.com/android/development/linux-version-twrp-2-8-6-0-tethered-t3123075
Windows Version
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
Click to expand...
Click to collapse
Thanks for the thought, but if I can't get into Fastboot mode (or get the computer to recognize the device as being in Fastboot mode)... kinda unable to use it.
wirebook said:
Gave this a shot and partitioning seemed to work just fine. Flashing the OTA boot.img worked just fine, and attempting to flash your system.img once again threw an error at me. Thought I'd perform a reboot at this point (bad idea!) to see what I was working with and then I found myself with @anggusss' USB screen. (http://forum.xda-developers.com/showpost.php?p=60675581&postcount=5) Probably should've tried flashing a something else just to see if that did anything.
Guessing I've now got a brick, because I'm no longer able to get it to register with Fastboot. I can, however, flash the open-source firmware and the unbrick.zip firmware, which reacts exactly like when @anggusss did it. We'll have to see if Dell ever gets back to my original query for help, otherwise might have to look into contacting Dell for a replacement.
Click to expand...
Click to collapse
Oh man, sad to hear, I've done that successfully in the past, they must have changed something in the process. I check just about every day for an update to the dev. firmware. Last time around it took them just over two months from release, so maybe, end of June?
xBIGREDDx said:
Oh man, sad to hear, I've done that successfully in the past, they must have changed something in the process. I check just about every day for an update to the dev. firmware. Last time around it took them just over two months from release, so maybe, end of June?
Click to expand...
Click to collapse
Fingers shall stay crossed till the end of the month, then! Contacted Dell Support and- just as I predicted- they don't want to help out. Something about being unable to do anything at all for Dell products purchased outside of their support areas (US and Canada). What a joy of a phone call that was...
An internet search landed me on guides for unbricking the Asus Zenfone displaying a similar USB symbol. They used the xFSTK Downloader to flash a set of files which then gave them renewed access to the bootloader (and thus fastboot). Played around with the xFSTK-Downloader and Manufacturing Flash Tool apps and can see the 7840 and even flash the (open-source and unbrick.zip) firmware, however I'm at a loss for what I might use for the Operating System flash files. Anybody have any thoughts?
Feel like I'm so close to getting this thing unbricked. If I could just figure out where to find the .bin "OS Image" that the tool wants...
Edit: Would also need the droidboot binary. FIngers crossed for Dell to release all of this soon...
OFFICIAL ONEPLUS 2 STOCK RESET​
SOURCE : OnePlus L2 Support Team
VERSION : OxygenOS 2.2.0
DOWNLOADS
1. OnePlus2 Stock Reset Oxygen OS 2.2.0 Google Drive | Mediafire
2. Qualcomm Drivers Version 1.00.11 Google Drive | Mediafire
INSTRUCTIONS
You are doing this on your own responsibility. I take no responsibility whatsoever.
(THIS WILL WIPE YOUR ONEPLUS INCLUDING INTERNAL SD)
Download both the files from above and extract them (WinRAR, WinZIP, 7ZIP etc). You should have 2 folders: "OnePlus2_14_A.11_151211" and "qc"
A. Install the Certificates followed by the Qualcomm drivers.
1. Restart your computer with Driver Signature Enforcement Disabled (Advanced Startup) Let me Google it For You
2. Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
3. Run the Qualcomm setup wizard (also located in the qc folder)
4. When completed, restart your PC again with Driver Signature Enforcement Disabled (Advanced Startup)
5. Turn off your phone and disconnect the USB cable from the phone.
6. Hold vol-up and plug in the USB(Do not press Power button). The screen will stay black but you will hear a sound from windows that a device is attached.
7. The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install. (Got the RELINK issue? Take a look here: http://forum.xda-developers.com/show...1&postcount=46)
B. Flashing Process
1. Open the OnePlus2_14_A.11_151211 folder and open "MSM8994DownloadTool.exe"
2. Look if your phone is detected in the list. everything is Chinese but you will see one row with different chinese text from the rest within the list. If not, recheck if driver is detected in Device Manager (If not, go back to Step A - Line 4).
3. First click the right square Chinese button. This will perform an integrity check on the downloaded files by verifying the MD5 hash values.
4. The system will seem to hang for a bit but should give you a pop up with the results of the above verification. When everything is ok. Press the start button. and let the progress finish. (If something is not ok, you will have to re-download the images. Google Drive can help extract only the necessary files.)
5. When it's done. Disconnect the USB cable and turn on the device.
C. Reset TAMPER Flag (Optional)
(This may potentially change your SmartPhone to a rather large paperweight and I will just laugh at you bearing no responsibility)
+ This part of the guide is not an Official Procedure and is in no way affiliated to OnePlus
+ It is advisable to do this before any of the above mentioned operations.
+ Prerequisites:
Root
HEX Editor with root features
Root File Manager
+ BEWARE: You are modifying partitions which cannot be restored regardless of what you flash. You have been warned AGAIN
1. In File Manager browse to the devinfo partition (dev/block/bootdevice/by-name/)
2. Open devinfo using the HEX Editor.
3. Modify the TamperBit (attached screenshot) from 01 to 00.
4. Save and reboot to fastboot.
5. Type fastboot oem device-info to confirm.
CREDITS
OnePlus Team for the Files.
@paultje162 for adaptation of Instructions. Refer his thread here if you are looking for an older version of stock reset (2.1.1).
@thedropdead for his work on Tamper Reset
If this thread has helped you, do press the THANKS button. Should you have issues, questions or doubts, write in this thread.
Just need to confirm that these files are actually official
Pm me the s3 support link
---------- Post added at 13:14 ---------- Previous post was at 13:10 ----------
And my friend
You need to install the test certificate first !
Edit:- file confirmed legit ! Totally official, way to go, @fareed_xtreme !
[email protected] said:
Just need to confirm that these files are actually official
Pm me the s3 support link
---------- Post added at 13:14 ---------- Previous post was at 13:10 ----------
And my friend
You need to install the test certificate first !
Click to expand...
Click to collapse
Thanks for spotting the error. I have fixed the heading. S3 Link PMed.
fareed_xtreme said:
Thanks for spotting the error. I have fixed the heading. S3 Link PMed.
Click to expand...
Click to collapse
Whenever you get drivers like this, dig into their folders and you'll find important documents and instructions to use
That is how I found out about this certificate
Is there any similar process por ONEPLUS ONE?
I only have fastboot mode, without recovery and bootloader locked (fastboot oem unlock doesn't work)
http://forum.xda-developers.com/showthread.php?t=2970390
@xbit
xbit said:
Is there any similar process por ONEPLUS ONE?
I only have fastboot mode, without recovery and bootloader locked (fastboot oem unlock doesn't work)
Click to expand...
Click to collapse
Quick search and: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
beaverhead said:
http://forum.xda-developers.com/showthread.php?t=2970390
@xbit
Click to expand...
Click to collapse
This didn't work for me:
fastboot oem unlock didn't work because I had a corrupt bootloader.
Spannaa said:
Quick search and: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
But this was great! My OPO is alive now. Thanks
Thank you!!!! this worked.
I was eventually able to get the restore program to recognize it and restore it so it could boot normally. Thank you!
Download from your Link
https://drive.google.com/folderview?id=0BxFd4Zc3_d1CWDdOSFFIVG42VTg&usp=sharing
the File:
OnePlus2_14_A.11_151211.rar
Extract it.
But where is the "QC Folder"
found only "OnePlus2_14_A.11_151211"
Your Link to:
http://forum.xda-developers.com/show...1&postcount=46
is wrong. (Not complete) Error 404
Wagi99 said:
Download from your Link
https://drive.google.com/folderview?id=0BxFd4Zc3_d1CWDdOSFFIVG42VTg&usp=sharing
the File:
OnePlus2_14_A.11_151211.rar
Extract it.
But where is the "QC Folder"
found only "OnePlus2_14_A.11_151211"
Your Link to:
http://forum.xda-developers.com/show...1&postcount=46
is wrong. (Not complete) Error 404
Click to expand...
Click to collapse
Yep, the qc folder is missing from the zip.
The link should be: http://forum.xda-developers.com/showpost.php?p=64674951&postcount=46
I suspect these are both down to copying & pasting the instructions from @paultje162's thread and I'm sure @fareed_xtreme will sort it out when he gets the chance.
Wagi99 said:
Download from your Link
https://drive.google.com/folderview?id=0BxFd4Zc3_d1CWDdOSFFIVG42VTg&usp=sharing
the File:
OnePlus2_14_A.11_151211.rar
Extract it.
But where is the "QC Folder"
found only "OnePlus2_14_A.11_151211"
Your Link to:
http://forum.xda-developers.com/show...1&postcount=46
is wrong. (Not complete) Error 404
Click to expand...
Click to collapse
Thanks for spotting the errors. I have updated them. It is indeed a miss on my part in regards to the QC. Hence I have uploaded it separately and updated the instructions.
Spannaa said:
Yep, the qc folder is missing from the zip.
The link should be: http://forum.xda-developers.com/showpost.php?p=64674951&postcount=46
I suspect these are both down to copying & pasting the instructions from @paultje162's thread and I'm sure @fareed_xtreme will sort it out when he gets the chance.
Click to expand...
Click to collapse
Yup, A copy paste is not the right way to copy a link. Haven't been around these threads for quite some time and guess i did not remember that the links are trimmed down. Thanks for the correct link.
Updated Information with UnTamper Guide
Hello
Doing the anti tamper method you did. Shouldn't this be easier by doing "fastboot oem lock" ?
I think it should have the same effects. Of course, this command must be done when an official ROM is on the phone, doing this in a custom ROM can cause unexpected behaviour, including bricking.
albertocastillo2001 said:
Hello
Doing the anti tamper method you did. Shouldn't this be easier by doing "fastboot oem lock" ?
I think it should have the same effects. Of course, this command must be done when an official ROM is on the phone, doing this in a custom ROM can cause unexpected behaviour, including bricking.
Click to expand...
Click to collapse
From my personal experience, if the Tamper Flag trips, then no matter how official you go it will not go back to Device Tamper= False.
The files in my First Post restores your phone back to an out of box phone state even locking the bootloader but it will not change the tamper flag. Those files are used by OnePlus Support to fix OS issues. Also the fastboot oem lock has not managed for me personally to get the tamper flag back to default (Same as in OPO once down, its down). So the only way for now for the OPT is by modifying the bit that handles the tamper flag.
You are right. Tamper Flag usually trips when you try to relock the bootloader when having root and other non-stock partitions (custom kernel, recovery etc). (Learned the hard way with my old OnePlus 2. Got it swapped for a new one though as the old one was faulty )
Hope this helps.
fareed_xtreme said:
From my personal experience, if the Tamper Flag trips, then no matter how official you go it will not go back to Device Tamper= False.
The files in my First Post restores your phone back to an out of box phone state even locking the bootloader but it will not change the tamper flag. Those files are used by OnePlus Support to fix OS issues. Also the fastboot oem lock has not managed for me personally to get the tamper flag back to default (Same as in OPO once down, its down). So the only way for now for the OPT is by modifying the bit that handles the tamper flag.
You are right. Tamper Flag usually trips when you try to relock the bootloader when having root and other non-stock partitions (custom kernel, recovery etc). (Learned the hard way with my old OnePlus 2. Got it swapped for a new one though as the old one was faulty )
Hope this helps.
Click to expand...
Click to collapse
Thanks for your reply. I noticed that these are the files that OnePlus team sends you when they want to remote into your device to flash the system. I noticed these are password encrypted. I have a session with them on Monday 6th.
I sent the files they sent me to decryption to get the password to a website that does this. However, they couldn't. My other plan was just to catch the password when having the remote session with them.
Since you already posted the files here, this is no longer needed. Seems you did this earlier than me.
The reason they want to do a full flash on my phone is due to the fact that I have a dual SIM issue. At the beginning both SIMs worked until I had to do a change on the second SIM network (it's an international SIM card that works in every country so you must set up the network manually). Since I tried to change the network. Something got messed up and now only one SIM works at a time. I tried restoring the network settings to automatic with no go. And I also tried to do hard restore on the phone to start over to ensure this would solve the issue.
This didn't solve the issue. So it probably means the settings were done in a partition which is not "/data". So a hard reset obviously wouldn't work. But a full flash surely will.
I asked them if I could do this myself by just sending me the files. I have a good expertise on fastboot, ADB and Linux, and I also understand the partition list and partition images. However, since the phone is not rooted or modified in anyway. I decided I will let them do it for me.
I do have a question thought. How did you find about the anti tamper thing? I assume you had remote session with them, and this is why you have those files. Did they "relock" this for you?
I assume they look at this when they get defective devices returned.
Thanks
albertocastillo2001 said:
Thanks for your reply. I noticed that these are the files that OnePlus team sends you when they want to remote into your device to flash the system. I noticed these are password encrypted. I have a session with them on Monday 6th.
I sent the files they sent me to decryption to get the password to a website that does this. However, they couldn't. My other plan was just to catch the password when having the remote session with them.
Since you already posted the files here, this is no longer needed. Seems you did this earlier than me.
The reason they want to do a full flash on my phone is due to the fact that I have a dual SIM issue. At the beginning both SIMs worked until I had to do a change on the second SIM network (it's an international SIM card that works in every country so you must set up the network manually). Since I tried to change the network. Something got messed up and now only one SIM works at a time. I tried restoring the network settings to automatic with no go. And I also tried to do hard restore on the phone to start over to ensure this would solve the issue.
This didn't solve the issue. So it probably means the settings were done in a partition which is not "/data". So a hard reset obviously wouldn't work. But a full flash surely will.
I asked them if I could do this myself by just sending me the files. I have a good expertise on fastboot, ADB and Linux, and I also understand the partition list and partition images. However, since the phone is not rooted or modified in anyway. I decided I will let them do it for me.
I do have a question thought. How did you find about the anti tamper thing? I assume you had remote session with them, and this is why you have those files. Did they "relock" this for you?
I assume they look at this when they get defective devices returned.
Thanks
Click to expand...
Click to collapse
Please note that the Tamper part of the guide is NOT done by OnePlus. Please note that OnePlus is in no way affiliated to the Tamper part of the guide. The Tamper guide is a result of comprehensive research conducted by thedropdead (information provided in the First Post). The guide is an easier interpretation of all the research that went in there.
OnePlus will only reflash this package which will re-lock the Bootloader only. Tamper Flag is not modified. So sit tight and let them reflash it for you.
You are right to assume I had a session with them earlier and that's how i have the files.
Thanks for your reply.
I would say that if the remote support doesn't untamper the device then it might mean they don't even look at it if the device is returned.
Thanks!
albertocastillo2001 said:
Thanks for your reply.
I would say that if the remote support doesn't untamper the device then it might mean they don't even look at it if the device is returned.
Thanks!
Click to expand...
Click to collapse
Remote Support didn't look into mine. However, not very sure about whether it is checked on returning it. Mine went untampered.
fareed_xtreme said:
Remote Support didn't look into mine. However, not very sure about whether it is checked on returning it. Mine went untampered.
Click to expand...
Click to collapse
Oh, then what happened? I thought the remote support tried to fix your phone. Since you said they didn't untamper the device after I expected they remoted to your phone. What happened then?
Thanks
I just got the SGP712 and created an FTF file using xperifirm (32.1.A.1.185). When flashing using Flashtool 0.9.22.0 it starts properly but gets stuck at processing modem.sin ... Flashing data..
My tablet is from Taiwan SGP712 and I created the FTF from TW and USA and both get stuck at the same point.
The drivers have been installed by disabling W10 driver signatures
The bootloader has NOT been unlocked so I have to assume that I can recover from this problem somehow.
I have created and flashed FTF using flashtool a billion times on my xperia phones and tablet Z, Z2 and never encountered this problem. It doesn't even give me an error in red, just sits there forever. See screenshot..
My tablet is 2 days old and currently will no longer boot, Xperia appears and tells me that the update failed.
Any help would be appreciated....
Thanks
Why don't you just flash an original FTF?
Your Franken-FTF will never run due to DM-Verity.
The devices in your footer do not have this "feature".
Welcome to the newer xperia lineup
Thanks for replying...
my Franken-FTF is the original from Sony, I only downloaded the files from xperifirm and built the FTF with Flashtool.
Anywhoo, it turns out that my FTF wasn't the problem, Flashtool seemed to be the culprit. Version 0.9.22.0 kept stopping in the middle of the flash so I tried with the patch 0.9.22.1 which basically makes you download the file "x10flasher.jar" and replace the original with this one. (I assume this is what we are supposed to do coz there's no instructions.).
As a result, Flashtool loads with the patch but no information is displayed, the huge text box stays blank (see screenshot) yet I'm able to flash my tablet with my FTF just by relying on the progress bar.
The flash completed successfully and my tablet is now on latest MM firmware. :highfive:
I'm wondering if I should wait a bit longer for a Dev to find an exploit or unlock my bootloader and root (which I don't feel like doing)
DHGE said:
Why don't you just flash an original FTF?
Your Franken-FTF will never run due to DM-Verity.
The devices in your footer do not have this "feature".
Welcome to the newer xperia lineup
Click to expand...
Click to collapse
Crash338 said:
my Franken-FTF is the original from Sony,
Click to expand...
Click to collapse
OIC - I misread: "I created the FTF from TW and USA " and assumed you were mixing them into your own.
Strange experience with Flashtool yuu describe. I have not used it for months.
I am on firmware 32.1.A.1.163 for Germany and I have not read any convincing praise for .185 to flash the FTF for another country onto my SGP712.
Crash338 said:
Thanks for replying...
my Franken-FTF is the original from Sony, I only downloaded the files from xperifirm and built the FTF with Flashtool.
Anywhoo, it turns out that my FTF wasn't the problem, Flashtool seemed to be the culprit. Version 0.9.22.0 kept stopping in the middle of the flash so I tried with the patch 0.9.22.1 which basically makes you download the file "x10flasher.jar" and replace the original with this one. (I assume this is what we are supposed to do coz there's no instructions.).
As a result, Flashtool loads with the patch but no information is displayed, the huge text box stays blank (see screenshot) yet I'm able to flash my tablet with my FTF just by relying on the progress bar.
The flash completed successfully and my tablet is now on latest MM firmware. :highfive:
I'm wondering if I should wait a bit longer for a Dev to find an exploit or unlock my bootloader and root (which I don't feel like doing)
Click to expand...
Click to collapse
Question for you, how did you apply the 0.9.22.1 patch? I am in the same boat of soft bricked and need to apply the patch but not certain how to do it, do I just replace that file?
Thx
ThePhoneGeek said:
Question for you, how did you apply the 0.9.22.1 patch? I am in the same boat of soft bricked and need to apply the patch but not certain how to do it, do I just replace that file?
Thx
Click to expand...
Click to collapse
Just replace the jar file you downloaded with the original located in your "C:\Flashtool"
Even if the list box doesn't show any logs you can still follow the steps and use "Flashmode" just relying on the progress bar until it completes. Note that when the progress gets at 95% and appears stuck again, do not unplug your tablet. The last part takes about 8-10 min to complete. I assume that its flashing the system which is the longest.
Good luck and post your results, I'm curious to know if its just me or affecting anyone with the Z4 tablet and latest version of Flashtool. :fingers-crossed:
Crash338 said:
Just replace the jar file you downloaded with the original located in your "C:\Flashtool"
Even if the list box doesn't show any logs you can still follow the steps and use "Flashmode" just relying on the progress bar until it completes. Note that when the progress gets at 95% and appears stuck again, do not unplug your tablet. The last part takes about 8-10 min to complete. I assume that its flashing the system which is the longest.
Good luck and post your results, I'm curious to know if its just me or affecting anyone with the Z4 tablet and latest version of Flashtool. :fingers-crossed:
Click to expand...
Click to collapse
Got it, thanks for the help.
I have just flashed my Z4 using the Flashtool 0.9.22.3 and after it completed successfully now my tablet is black screen. When i press the power button the device vibrates as if to start but just black screen
Please help!!!
Hi Dears
When flashing xz1, a message is displayed in the image below :
1) What will I do? Yes or no?
2) What does this message say and what?
3) There is no risk to the phone?
4) Can not make a problem with the flash?Flashing safely?
Just click yes. It's fine
N1ghtr08d said:
Just click yes. It's fine
Click to expand...
Click to collapse
There is no risk to the phone?
Brother,I didn't become a senior member by giving people bad advice. I've already done it myself, that's why I said you can do it.
One piece of advice though, when using flashtool if it gets really far down the process and looks like it's just hanging or not doing anything (should be after it flashes a bunch of system partitions) just go ahead and disconnect the phone then reboot it. Just remember, wait until you don't see any activity on flashtool for about 5 minutes then you'll be good to go. This is of course, assuming you get the same result with flashtool that I got.
Either way there's no need to worry because even if something were to ever go wrong, the phone can always be fixed by putting the pics into flash mode then flashing again so you don't have to be fearful, we're also always here to help.
N1ghtr08d said:
Brother,I didn't become a senior member by giving people bad advice. I've already done it myself, that's why I said you can do it.
One piece of advice though, when using flashtool if it gets really far down the process and looks like it's just hanging or not doing anything (should be after it flashes a bunch of system partitions) just go ahead and disconnect the phone then reboot it. Just remember, wait until you don't see any activity on flashtool for about 5 minutes then you'll be good to go. This is of course, assuming you get the same result with flashtool that I got.
Either way there's no need to worry because even if something were to ever go wrong, the phone can always be fixed by putting the pics into flash mode then flashing again so you don't have to be fearful, we're also always here to help.
Click to expand...
Click to collapse
Hello, fellow rooted XZ1C here! Since your experience I would like to make a question please:
do you think should be safe use latest Flashtool 0.9.25.0 to downgrade from latest july 47.1.A.12.235 Customized IT fw to an older 47.1.A.12.75 Customized DE without messing up everything?
I mean, besides a full data wipe, is there something else I should be aware?
If you remove the userdata.sin file before using flashtool then you should be able to move around between any firmwares without wiping the data partition.
N1ghtr08d said:
If you remove the userdata.sin file before using flashtool then you should be able to move around between any firmwares without wiping the data partition.
Click to expand...
Click to collapse
Thx! I just have a userdata_X-FLASH-ALL-C93B.sin in 47.1.A.12.75 fw folder, is that one I should delete?
However I'm actually looking for a clear data wipe too and start from scratch, can I leave everything as it is?
If you're looking for a full data wipe them the only files you need to remove is any .ta files. If you download the firmware then just search through the 2 or 3 folders and delete any .ta files.
The .ta files are for the Trim Area. I don't know why they must be deleted but you gotta do it. That's what I learned, it's what I always do, and it's flawless.
excuse me sir, could u help me,
last night i try do flash with Flashtool 0.9.25.0 from singapore version to india version, i got message "no partition delivery included. maybe a bundle created on previous vesion", any advise sir?
Solved, i used newflasher, n everything work fine