after encryption rom flashing soft brick help - Xperia Z1 Compact Q&A, Help & Troubleshooting

condensed version
encrypted phone, flashed, not working properly, used flashtool to try to use a stock image to restore phone, did not work, need help to save myself from a expensive waterproof brick
--------
The longer version of the story (in a galaxy far, far away....)
Just tried updating from last AOKP nightly (yer that old) to RR 5.4.0 but ran into issue flashing it namely from what i believe was from my phone being encrypted previously. It seemed to install the ROM well enough but i kept seeing this little error message popup during the recovery install (i did do a complete wipe etc)
Code:
E: cannot load volume /misc
but i assumed all well and good as it did not give a fail or anything so i continue on and try to install gapps for it but then get this error message
Code:
Install failed
E:cannot load volume /misc!
Finding update package…
Opening update package…
Verifying update package…
E: footer is wrong
E: signature verification failed
Installation aborted
E: cannot load volume /misc
accepting defeat after this failing after attempting again, rebooted the rom which loaded up well enough and tried to reinstall a different version of gapps, same problem, tried to install via fastboot same problem. Tried wiping the rom and formatting the internal memory via fastboot but got this
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -w
erasing 'userdata'...
OKAY [ 1.046s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.007s]
erasing 'cache'...
OKAY [ 0.043s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.008s]
finished. total time: 1.108s
could not flash the rom due to the android-info.txt issue with fastboot, flash a boot.img from RR, got the z1c running again and settled into a life without gapps and actually felt like it was a really good thing after a bit of research and finding alternatives but kept running into odd app errors and force closes and issues with receiving sms that forced me to have to figure out why it was not letting me install zips. Tried my luck on cm-12-20150402-NIGHTLY-amami build but had some issues with a few things got stuck in bootloop so decided i would try to start fresh so i moved on to my next step
Used this reference point for the ftf file and how to repair soft bricks http://forum.xda-developers.com/showthread.php?t=2631291&nocache=1, used flashtool after locking and unlocking my phone option (seen a few threads where people recommended it in the past) tried to flash the ftf file then got this (check attachment from flashtool for log), now really stuck phone reports that OS install failed and to try again but i know better than to keep doing the same thing over and over and to expect a different result so I ask the xda saviours for some assistance in getting me out of this problem.
Thank you for your time if you stopped in here to look at my request for help, it really is appreciated and to show that i will put a bounty/donation up for whoever solves my issue first as a sign of my good will and gratitude for your brains

try to use EMMA with UB to restore your phone.
VooDoo.maGiK said:
condensed version
encrypted phone, flashed, not working properly, used flashtool to try to use a stock image to restore phone, did not work, need help to save myself from a expensive waterproof brick
--------
The longer version of the story (in a galaxy far, far away....)
Just tried updating from last AOKP nightly (yer that old) to RR 5.4.0 but ran into issue flashing it namely from what i believe was from my phone being encrypted previously. It seemed to install the ROM well enough but i kept seeing this little error message popup during the recovery install (i did do a complete wipe etc)
Code:
E: cannot load volume /misc
but i assumed all well and good as it did not give a fail or anything so i continue on and try to install gapps for it but then get this error message
Code:
Install failed
E:cannot load volume /misc!
Finding update package…
Opening update package…
Verifying update package…
E: footer is wrong
E: signature verification failed
Installation aborted
E: cannot load volume /misc
accepting defeat after this failing after attempting again, rebooted the rom which loaded up well enough and tried to reinstall a different version of gapps, same problem, tried to install via fastboot same problem. Tried wiping the rom and formatting the internal memory via fastboot but got this
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -w
erasing 'userdata'...
OKAY [ 1.046s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.007s]
erasing 'cache'...
OKAY [ 0.043s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.008s]
finished. total time: 1.108s
could not flash the rom due to the android-info.txt issue with fastboot, flash a boot.img from RR, got the z1c running again and settled into a life without gapps and actually felt like it was a really good thing after a bit of research and finding alternatives but kept running into odd app errors and force closes and issues with receiving sms that forced me to have to figure out why it was not letting me install zips. Tried my luck on cm-12-20150402-NIGHTLY-amami build but had some issues with a few things got stuck in bootloop so decided i would try to start fresh so i moved on to my next step
Used this reference point for the ftf file and how to repair soft bricks http://forum.xda-developers.com/showthread.php?t=2631291&nocache=1, used flashtool after locking and unlocking my phone option (seen a few threads where people recommended it in the past) tried to flash the ftf file then got this (check attachment from flashtool for log), now really stuck phone reports that OS install failed and to try again but i know better than to keep doing the same thing over and over and to expect a different result so I ask the xda saviours for some assistance in getting me out of this problem.
Thank you for your time if you stopped in here to look at my request for help, it really is appreciated and to show that i will put a bounty/donation up for whoever solves my issue first as a sign of my good will and gratitude for your brains
Click to expand...
Click to collapse

will do, i think i may have had given emma a shot at saving my little z1c but will double check to be sure, what is UB? cant seem to find anything related to that acronym
cheers for the tip

Unlocked bootloader
Wysłane z mojego D5503 przy użyciu Tapatalka

cheers, emma did the trick, i think i had started to use it as once of my first solutions but then realised it was going to take forever downloading the file in it i decided to try other things first but forgot to come back to it
throw me your paypal dets for a free coffee

VooDoo.maGiK said:
cheers, emma did the trick, i think i had started to use it as once of my first solutions but then realised it was going to take forever downloading the file in it i decided to try other things first but forgot to come back to it
throw me your paypal dets for a free coffee
Click to expand...
Click to collapse
if flashtool fails and you have luckily a unlocked bootloader and fastboot works you can allways restore your phone with EMMA.
unfortunately EMMA works only with unlocked bootloader.
thanks for the offer. but to me it is enough that the phone working again :good:

Related

No access to Recovery and HOX doesn't boot

Hello
i have some problems with my HTC One X. Until 2 hours ago it worked perfectly and without problems. i didn't flash anything in the last few weeks, but theres ARHD (ICS) installed. But then suddenly it had a freeze, so i had to restart it with pressing the powerbutton for 10 seconds. Since then, it doesn't boot anymore and also i can't access the Recovery, i get a blackscreen if i try, But i come into the Bootloader, Fastboot is possible but doesn't work...
I tried to reflash the Boot.img, but there was an error: erasing cache FAILED (remote: 19000008)
I also tried to reflash the CWM Recovery but there was another error:
5.8.4.0-endeavoru.img
sending 'recovery' (5742 KB)...
OKAY [ 0.904s]
writing 'recovery'...
(bootloader) Format partition SOS done
FAILED (remote: (00030000))
finished. total time: 1.150s
So can anybody help me? All that I want is access to my virtual SD Card for saving my data, and can anybody tell me how and if I can "repair" my One X? And sorry for the bad english, i'm no native speaker...
you can try this, http://forum.xda-developers.com/showthread.php?t=1609190
Thanks, but it didn't help. When i tried to flash the images in fastboot almost the same errors as before occured...i absolutely dont know what to to now, i think i even can't relock the bootloader, flash the stock recovery and a RUU
Achsoistdas19 said:
Thanks, but it didn't help. When i tried to flash the images in fastboot almost the same errors as before occured...i absolutely dont know what to to now, i think i even can't relock the bootloader, flash the stock recovery and a RUU
Click to expand...
Click to collapse
what the error mate?
Hm, i don't really know. There are these Error-Codes, mostly "remote: 19000008" or "remote: 00000004" also with a 5 at the end, and it says "remote: not allowed" sometimes.

[Q] Please help, P6 stuck at boot screen

A friend of mine as the same phone as me, the Huawei Ascend P6, and when she said hers was broken I said I would take a look. I have played around with flashing Android Roms etcetera, but I am totally stuck with this problem.
The problem is as follows: when booting the phone it shows the Huawei Ascend logo (as it should) for a couple of seconds, but then instead of the Huawei animation it shows the name "android" and gets stuck there (see attachment).
After some researching I put the UPDATE.APP file from the Huawei website in the dload folder on the root of the SD-card and tried rebooting. I tried a several times, but nothing happened.
Next I successfully booted in recovery mode but even when starting recovery the screen shows errors (see attachment):
Code:
E:failed to mount /cache (Invalid argument)
E:failed to mount /cache (Invalid argument)
ensure_path_mounted Failed
E:failed to mount /cache (Invalid argument
Installing a ZIP file, wipe cache and wipe data give even more errors.
So I thought I would try flashing through ADB/fastboot, and used the HuaweiUpdateExtractor tool to get the images. I can get manually in fastboot mode, but when I try to flash an image get the error
Code:
FAILED (remote: flash failure, ErrNo:2)
I tried using different files, USB ports, cables, linux and windows but nothing seems to help. Has anyone an idea what to do next?
it would help much to know what fw is / was flashed as last..
this android screen means to me that it should be a chinese / non international version..
if you enter fastboot mode and connect your phone to the pc make sure your pc recognizes the phone (for checking: fastboot devices - it should show you many "????")..if so try to install twrp (there are many threads about it)..then you might be able to install (through twrp) a repack of b513 or another version (but it has to be a repack)..
after that (and hopefully successful) you can try (use search) to change to an official fw again..
just my suggestion
hope you get a solution..
blueIBI said:
it would help much to know what fw is / was flashed as last..
this android screen means to me that it should be a chinese / non international version..
if you enter fastboot mode and connect your phone to the pc make sure your pc recognizes the phone (for checking: fastboot devices - it should show you many "????")..if so try to install twrp (there are many threads about it)..then you might be able to install (through twrp) a repack of b513 or another version (but it has to be a repack)..
after that (and hopefully successful) you can try (use search) to change to an official fw again..
just my suggestion
hope you get a solution..
Click to expand...
Click to collapse
Since I can not boot and it's not my own phone I have no clue what the version is
Luckily my PC recognizes the phone in fastboot (indeed with a weird name with a lot of ?), but I am not able to flash twrp because every time I try I get a FAILED response... Maybe the file I have is wrong. Could you point me to a thread about falshing twrp?
here is a guide for unlocking bootloader: http://forum.xda-developers.com/showthread.php?p=50724517
here is a twrp for JB roms: http://forum.xda-developers.com/showthread.php?p=47633501
here for KK roms: http://forum.xda-developers.com/showthread.php?p=51718302
maybe you need to unlock your bootloader at first
changes not working
Thanks for the links! I am able to flash an image, but for some reason my changes won't stick. When I boot in fastboot it says it is locked and I am able to unlock it, but everytime I reboot it is locked again. The same happens with twrp, I am able to flash the image but for some reason when I boot back into recovery nothing has changed.
My fastboot commands and output:
Code:
C:\Android>fastboot oem get-bootinfo
...
(bootloader) locked
OKAY [ 1.952s]
finished. total time: 1.952s
C:\Android>fastboot oem unlock UUUUUUUUUUUUUUUU
...
OKAY [ 0.012s]
finished. total time: 0.012s
C:\Android>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.001s]
finished. total time: 0.001s
C:\Android>fastboot flash recovery twrp_2_6_3_3_recovery.img
sending 'recovery' (8690 KB)...
OKAY [ 0.259s]
writing 'recovery'...
OKAY [ 0.390s]
finished. total time: 0.650s
Any idea?
hm..
in this case no..
i'm sorry..your friend should bring it to the service..that's the best advice for now..
blueIBI said:
hm..
in this case no..
i'm sorry..your friend should bring it to the service..that's the best advice for now..
Click to expand...
Click to collapse
That's what I was afraid of..
I think the unlock code doesn't work correctly on this phone for some reason, but I don't think I'll be able to get an unlock code specific for my device from Huawei, without serial number and such which I can't get since the phone doesn't boot.
I hope there is some warranty left...
Results
If anyone is interested (perhaps in the future), the phone was sent for repairs and is working again. They probably replaced the motherboard, but luckily it all fell under the warranty.
Thanks to blueIBI for trying to help!!

[Q] GPE 5.0.1 Bricked my phone - can anybody help?

Hello everyone
So I have a m8 and converted it to the GPE edition. I changed my CID & MID and installed 4.4.4. My phone was rooted and I installed custom recoveries and went back to the stock recovery.. Here is what went wrong.
Today the update 5.0.1 came, when I tried to install it the update was failing and said my Version is not the right one. So I found out, that I flashed an old recovery and because of that it could not install it. Ok, downloaded the original OTA of 4.4.4 extracted the recovery.img and flashed that one. Now the verification check went trough..
It startet installing and after 5 minutes the update failed! Saying something like, it could not create symlinks on the system... I tried again, and now it stops with this error:
fileexist(): check the existence of /system/lib/libgoogle_recognizer_jni_1.so failed, error no such file or directory() installation aborted...
My system partition is broken now and i cannot start any system anymore...
I would like to save my data or install anything that my phone is working again, but I want to keep my data.. My phone is encrypted! :/ I tried with custom recoveries, but they apparently don't support disk encryption on the m8...
I think I cannot flash 4.4.4 with RUU as this would also delete the data... adb backup only works if the system is up, because the shell command tells me that a system dialog will appear and ask me for my password....
Anybody has any suggestion how to save my data?
Thanks!
should be in Q&A mate
I have requiested the mods to move this
So first things first. You are not bricked, you are just stuck. Bricked means your device cannot boot, cannot turn on, cannot access any bootloaders or recovery.
You messed something up and it is failing to boot, it isnt bricked.
Second, running disk encryption on rooted devices is especially dangerous for these scenarios. Disk encryption attempts to prevent many of the things running roms, custom recoveries and such put on the device.
Now, I cannot recall if a full GPE version can do this or not, but from Fastboot you should be able to flash just the system partition. But being you are encrypted it may fail to access your old data. The command for that would be:
Fastboot flash system system.img (if you were able to obtain a system.img)
Again that works on Nexus devices, I cant recall if the GPE fastboot accepts it as well.
Wish you well, but honestly I would expect to lose your data. The reason the update failed the second time was because you are Rooted. 5.0+ has a new OTA system where any changes to the system partition can/will fail the OTA.
tschakk said:
Hello everyone
So I have a m8 and converted it to the GPE edition. I changed my CID & MID and installed 4.4.4. My phone was rooted and I installed custom recoveries and went back to the stock recovery.. Here is what went wrong.
Today the update 5.0.1 came, when I tried to install it the update was failing and said my Version is not the right one. So I found out, that I flashed an old recovery and because of that it could not install it. Ok, downloaded the original OTA of 4.4.4 extracted the recovery.img and flashed that one. Now the verification check went trough..
It startet installing and after 5 minutes the update failed! Saying something like, it could not create symlinks on the system... I tried again, and now it stops with this error:
fileexist(): check the existence of /system/lib/libgoogle_recognizer_jni_1.so failed, error no such file or directory() installation aborted...
My system partition is broken now and i cannot start any system anymore...
I would like to save my data or install anything that my phone is working again, but I want to keep my data.. My phone is encrypted! :/ I tried with custom recoveries, but they apparently don't support disk encryption on the m8...
I think I cannot flash 4.4.4 with RUU as this would also delete the data... adb backup only works if the system is up, because the shell command tells me that a system dialog will appear and ask me for my password....
Anybody has any suggestion how to save my data?
Thanks!
Click to expand...
Click to collapse
First, your phone isnt bricked, its not bricked as long as you can access HBOOT, second, why would you encrypt your phone? uhg... I dont know what to tell you, try RUUing to stock, but dont expect to keep your data...
I also had the idea with just flashing the system.img from fastboot. but that doesn't work..
target reported max download size of 1830617088 bytes
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.010s
i now try to flash it with dd directly to the block..
tschakk said:
I also had the idea with just flashing the system.img from fastboot. but that doesn't work..
target reported max download size of 1830617088 bytes
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.010s
i now try to flash it with dd directly to the block..
Click to expand...
Click to collapse
You can only flash boot and recovery individually, you would have to put system.img and android-info.txt in a zip and flash in ruu mode
UNBELIEVABLE!
I could restore the system with dd... Just copied the system.img from Android 4.4.4 to the block device.. now the phone is booting up and i can see my data... uffff.. :victory:
so now i will do a backup and then go on...
Solution
If someone should encounter the same issue, this is what I have done to fix it:
I didn't want to lose my data, so I did not reinstall the RUU.. I couldn't get my data with ADB backup, because you need a system display to do it. And I also couldn't find any recovery which supported device encryption for the m8.. So I thought to backup my data partition with 'dd' to an external SD card and then if necessary I would reinstall the full system with RUU..
Code:
$ cat /fstab.qcom #to find the needed partitions
$ dd if=</dev/block/DATA-DEVICE> of=/external-sd/backup.bin
Now I knew I had a backup and was on the safe side. So I wanted to try to rewrite the system partition with the system.img from 4.4.4 GPE RUU. But fastboot flash didn't work. I always got this error message:
Code:
$ fastboot flash system system.img
...
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.010s
So what the hell, I used 'dd' also for this... :
Code:
$ cat /fstab.qcom #again to find the needed partitions
$ dd if=/external-sd/system.img of=</dev/block/SYSTEM-DEVICE>
And this actually worked, my m8 booted up with Android 4.4.4. First thing I did when Android booted was a full Android backup with adb.. To be safe to have my data back, because I didn't really know how to extract my encrypted data from the bin file I've created before... Then I just installed the update to 5.0.1 and this time it worked...

Help please - bricked/bootloop

Hi guys, posted this under the TWRP thread but realised it might be a more general problem
ISSUE: I believe I bricked the phone or bootloop (sorry not familiar with terminology). After the splash screen the word ASUS shows with a never ending circle loading sign under it. I can't enter recovery using Power + Vol down
BACKGROUND: I am having some issues after doing the Tethered Recovery. I am rooted and have bootloader unlocked. Once I used cai_dat_CWM.bat and was in recovery, I tried to flash the clean rom HarfainX, but before I did, I did a wipe of Cache and it said formatting cache but after 10 minutes didnt load. So I turned off the phone, now it hangs on the ASUS screen. I can enter fast boot, but I cant enter recovery mode.
Can anyone help me in getting it back running again?
Update:
Tried doing a wipe through fastboot -w
and got the following results:
Erasing 'userdata' OKAY
Sending 'userdata' OKAY
Writing 'userdata' FAILED (remote: flash_cmds error!)
Thanks
You should've waited.
Posted using my phone.
jose makalolot said:
You should've waited.
Posted using my phone.
Click to expand...
Click to collapse
I did wait it just didn't do anything for about 10 minutes.
I'm trying to sideload using ADB the stock rom from ASUS / Garbage free ROM by Harfain X and I am getting:
adb.exe sideload update.zip
loading: update.zip
error: device not found
fastboot update.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
Anyone can offer suggestions?
...Flashed untethered TWRP... fixed the problem .. thanks TheSSJ for creating it

problems flashing my arc s to the latest firmware ftf 4.0.4_4.1.B.0.587

Hello,
After a few years of having ultimate hd on my arc s, I'm playing again with my old loved xperia arc s, the one that I've unlocked bootloader and installed so many many custom roms in the past.
Now I want to test this rom:
https://forum.xda-developers.com/xp...v-2011-android-source-project-builds-t3053170
...Just to change ultimate hd for a long time.
But it's necessary that I'd installed before the latest ftf (4.0.4_4.1.B.0.587). As I am not sure after such a long time, I want to make it again, because the installation of this custom rom failed the first time I'd tried...
Using flashtool version 0.9.18.6 as recommended here, I'm getting error "ERROR - Processing of system.sin finished with errors." ... the other .sin files in the FTF file are flashing ok...
I've also tried to flash, first everithing except system.sin, then only system.sin, but it gives me the same error.
I've also tried to flash system.sin with fastboot:
fastboot flash system system.sin
but I get error "FAILED (remote: Download size too large)"
To overcome this, if I try to run instead this:
fastboot flash -S 256M system system.sin
Then I get a series of messages:
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 90299761 is not a multiple of the block size 4096 (it repeats it multiple times)
OKAY [ 32.292s]
writing 'system' 1/2...
(bootloader) Flash of partition 'system' requested
(bootloader) S1 partID 0x00000004, block 0x000002f4-0x00000f73
(bootloader) Erasing block 0x00000300...
Erase operation complete, 589 bad blocks encountered
(bootloader) Flashing...
...
(bootloader) Flash operation complete
OKAY [ 17.994s]
finished. total time: 107.983s
Despite the errors, (they are RARE, as I'd NEVER had problems with defective nand on my phone, and I'd installed LOTS of custom roms in the past) It seems to be flashed... But android does not start (SONY) logo appears, and then, an exclamation sign and a little 'seems-to-be-dead' phone icon appears.
I've also tried to reinstall twrp first and do a total wipe. it continues to fail.
The other versions I've tried for flashtool are
0.9.1.0
0.9.2.6
0.9.2.8
0.9.18.2
None of them worked, ... 0.9.18.6 is supposed to work, but it does not. The drivers for this version are installed (disabling that reference integrity stuff in windows 10)
I've also tried to test different firmware files, but they give me always the same error:
XPERIASITE.PL_Arc_S_LT18i_4.0.4_4.1.B.0.587_CentralEurope.ftf
LT18i_4.1.B.0.587_Customized_FR.ftf
LT18i_4.1.B.0.587_Customized MEA_1254-2284_R1I.ftf
LT18i_4.1.B.0.587 (1254-2716).(MMUG).ftf
What can I do ?
Thanks in advance,
Obsy
Hey there, did you ever manage to solve your issue ? I'm having an extremely similar problem with my Xperia Ray...
After some digging, I suspect that the number of bad sectors/bad blocks on the internal memory (more specifically on the /system partition) is big enough to make a significant part of the memory unusable... As a consequence, flashing of any rom or kernel is impossible due to insufficient space... Indeed, I looked at the "dmesg" output after trying to flash a rom in recovery, and I saw a lot of "bad blocks" mentioned and then a crash with "No space left on the device" as an error message :-(
Thanks in advance !
yugobosss said:
Hey there, did you ever manage to solve your issue ? I'm having an extremely similar problem with my Xperia Ray...
After some digging, I suspect that the number of bad sectors/bad blocks on the internal memory (more specifically on the /system partition) is big enough to make a significant part of the memory unusable... As a consequence, flashing of any rom or kernel is impossible due to insufficient space... Indeed, I looked at the "dmesg" output after trying to flash a rom in recovery, and I saw a lot of "bad blocks" mentioned and then a crash with "No space left on the device" as an error message :-(
Thanks in advance !
Click to expand...
Click to collapse
Hi,... Unfortunately I no longer have this phone, I broke it to simplify my life . Good luck with that !
Oh well... thanks for the quick reply !
If anyone else has any idea about all this, I'm open to suggestions !

Categories

Resources