Hi all !
First sorry for my poor english, this isn't my mother language.
Unfortunately, I accidentaly flash a recovery.img in the boot partition instead of recovery partition and now my phone doesn't boot anymore. It vibrate once but the screen keep black.
I can get into fastboot mode and adb recognize my phone.
So is it possible to simply flash a boot.img to get it working ? Where can I found this boot.img ?
It's a D5503, rooted but no custom recovery yet. (I was on it)
The recovery I was trying to flash was Z1c_DooMLoRD_AdvStkKernel_FW-114_v01.img from http://doomlord.xperia-files.com/files/Z1c_DooMLoRD_AdvStkKernel_FW-114_v01.img
I used EasyRootTool v12.2.zip to root my device.
Any help will be appreciated and I thank you in advance
The process you did was correct. On Xperia phones there is no recovery partition, you flash a custom kernel on boot partition with recovery built in. Probably your bootloader is locked. In that case the phone does not allow custom kernels and therefore does not boot. Can you get into flashmode (not fastboot)?
Edit: To clarify for other readers; there is indeed a way to use recovery without using a custom kernel. See for example dualrecovery by [NUT]
KDZCrew said:
Hi all !
First sorry for my poor english, this isn't my mother language.
Unfortunately, I accidentaly flash a recovery.img in the boot partition instead of recovery partition and now my phone doesn't boot anymore. It vibrate once but the screen keep black.
I can get into fastboot mode and adb recognize my phone.
So is it possible to simply flash a boot.img to get it working ? Where can I found this boot.img ?
It's a D5503, rooted but no custom recovery yet. (I was on it)
The recovery I was trying to flash was Z1c_DooMLoRD_AdvStkKernel_FW-114_v01.img from http://doomlord.xperia-files.com/files/Z1c_DooMLoRD_AdvStkKernel_FW-114_v01.img
I used EasyRootTool v12.2.zip to root my device.
Any help will be appreciated and I thank you in advance
Click to expand...
Click to collapse
Dude your phone isn't bricked, stop being a drama queen. I'll help you if you change your topic to say something other than "bricked".
zxz0O0 : yes but the LED doesn't stay green. So I don't know if the flash mode works great..
Rekoil : done
EDIT:
Ok so I unlocked my bootloader with the sony tool and now my phone almost boot Almost because in fact it vibrates once and I can see the sony logo but then the screen turn off and it boots again (bootloop).
Besides that, I have access to my custom Recovery (CWM).
So now, how can I get rid of the bootloop after unlocking the bootloader ? Thank's
Why did you unlock bootloader? Did you take a TA backup?
The LED never stays green in flashmode so not sure what you are expecting. To solve bootloop, try flashing stock firmware again. Maybe you have to wipe data.
zxz0O0 said:
Why did you unlock bootloader? Did you take a TA backup?
The LED never stays green in flashmode so not sure what you are expecting. To solve bootloop, try flashing stock firmware again. Maybe you have to wipe data.
Click to expand...
Click to collapse
Hi
I unlock the bootloader because you said - and I understood so - that it was the problem. No, I didn't make a TA bkp.
Ok for the flashmode, I thought that it was like the fastboot mode, where the LED stays blue. I'll try flashing the stock firmware. Thank's for your help. I'll let you know if it worked.
KDZCrew said:
Hi
I unlock the bootloader because you said - and I understood so - that it was the problem. No, I didn't make a TA bkp.
Ok for the flashmode, I thought that it was like the fastboot mode, where the LED stays blue. I'll try flashing the stock firmware. Thank's for your help. I'll let you know if it worked.
Click to expand...
Click to collapse
Not making a TA backup isn't really that big of a deal, it disables some features sure, but I doubt you'll actually notice them much. Now, were you running a 4.3 or 4.4-based firmware prior to flashing the boot.img? Because the boot.img contained a 4.3 kernel which will not boot 4.4 so I'm leaning towards you having a 4.4-based fw installed.
Since you can get to recovery, flash one of these in recovery, if you don't know which base your system is then try them one at a time, recovery will still function if the OS does not boot.
.108-base (latest base, 4.4.4)
.757-base (4.4.2 iirc)
Note that by unlocking bootloader you've also wiped your /data and /data/media (internal storage) partitions.
Rekoil said:
Not making a TA backup isn't really that big of a deal, it disables some features sure, but I doubt you'll actually notice them much. Now, were you running a 4.3 or 4.4-based firmware prior to flashing the boot.img? Because the boot.img contained a 4.3 kernel which will not boot 4.4 so I'm leaning towards you having a 4.4-based fw installed.
Since you can get to recovery, flash one of these in recovery, if you don't know which base your system is then try them one at a time, recovery will still function if the OS does not boot.
.108-base (latest base, 4.4.4)
.757-base (4.4.2 iirc)
Note that by unlocking bootloader you've also wiped your /data and /data/media (internal storage) partitions.
Click to expand...
Click to collapse
Hello,
So I was on a 4.4.4 firmware and i have flashed the 108-base and it worked. Big thank's to you two.
By unlocking the bootloader i lost my data but it is not a big deal because my pictures are on G+ and the rest i don't care much about.
Again, big thank's zxz0O0 and rekoil
Related
Hi, after attempting to flash a custom ROM to my phone I'm experiencing a big problem, the phone will not boot past the HTC screen. This is obviously very frustrating as the phone is pretty much rendered useless.
I am able to get into the HBOOT menu by holding the Power button and Volume Down and from there am able to select Recovery and enter the ClockWork Mod recovery screens. As you can tell I'm a 100% noob and I really just want to revert my phone to a working state. My network is Vodafone UK. I can't find an RUU above version 3.13 which is apparently what I have (so it tries updating 3.13 to 3.13 and obviously fails).
Any help on getting my phone to work again would be very very appreciated, thanks.
VBQ24 said:
Hi, after attempting to flash a custom ROM to my phone I'm experiencing a big problem, the phone will not boot past the HTC screen. This is obviously very frustrating as the phone is pretty much rendered useless.
I am able to get into the HBOOT menu by holding the Power button and Volume Down and from there am able to select Recovery and enter the ClockWork Mod recovery screens. As you can tell I'm a 100% noob and I really just want to revert my phone to a working state. My network is Vodafone UK. I can't find an RUU above version 3.13 which is apparently what I have (so it tries updating 3.13 to 3.13 and obviously fails).
Any help on getting my phone to work again would be very very appreciated, thanks.
Click to expand...
Click to collapse
Download a ROM onto your computer, connect to your phone in recovery, mount the sdcard, move the ROM from your computer onto your phone's sdcard, and flash from recovery. No need for RUU.
Dont forget to wipe.
wipe data/factory reset and format all partitions (except sd card) from recovery.
Go to bananagranolas link in her signature, you'll find everything you need there.
Thanks a lot for your help! I was attempting to flash the JellyTime ROM which I understand must have failed to result in my phone not booting properly. Should I flash a stock ROM or will any ROM suffice?
VBQ24 said:
Thanks a lot for your help! I was attempting to flash the JellyTime ROM which I understand must have failed to result in my phone not booting properly. Should I flash a stock ROM or will any ROM suffice?
Click to expand...
Click to collapse
As long as you are S-OFF and have a custom recovery (CMW or 4EXT) you are able to flash any custom rom you like. Just make sure that you make a full wipe before the flashing (wipe data/factory reset, wipe cache partition, format system or in 4ext recovery just choose format all partitions except sdcard).
That should leave you up and running again.
Okay great!
I used the HTCDev tools to unlock my boot loader which I understand is different to S-OFF? Could that be while the ROM flashing failed originally?
EDIT: Upon trying to flash the JellyTime AKOP Rom I get a message saying install from SD card complete but it's still stuck at the HTC screen...
VBQ24 said:
Okay great!
I used the HTCDev tools to unlock my boot loader which I understand is different to S-OFF? Could that be while the ROM flashing failed originally?
Click to expand...
Click to collapse
If you have an unlocked bootloder, then you have to flash the rom (previous full wipe of course) then reboot bootloader (from advanced options in CWM) and then in fastboot (you should see fastboot usb in red in the phone when plugged to the pc) you have to flash the boot.img inside the rom zip folder.
Extract that file only (not the whole rom) and from a cmd session or terminal as root (located where the boot.img file is) type:
fastboot flash boot boot.img
Once that is done (you will get OKAY. finished near the bottom) you can reboot normally by typing in cmd fastboot reboot or choosing reboot from hboot.
My bootloader now says RELOCKED, how can I unlock it again? (I'm really sorry about this)
VBQ24 said:
My bootloader now says RELOCKED, how can I unlock it again? (I'm really sorry about this)
Click to expand...
Click to collapse
Use the token HTC sent you when u unlocked it. and typing in cmd the fastboot unlock command.
Okay done that, thanks a lot!
I'm now looking in the advanced options of CWM, I can see the option "Reboot Recovery" but no "Reboot Bootloader"?
VBQ24 said:
Okay done that, thanks a lot!
I'm now looking in the advanced options of CWM, I can see the option "Reboot Recovery" but no "Reboot Bootloader"?
Click to expand...
Click to collapse
then just turn the phone off (power off option) and then boot with power + volume down
glevitan said:
then just turn the phone off (power off option) and then boot with power + volume down
Click to expand...
Click to collapse
Okay, I wiped all partitions, installed JellyTime AOKP, restarted, went into fastboot, extracted/flash boot file and the rebooted phone.
The phone will now progress from the HTC screen but is now stuck on a black screen, Windows tried to install drivers but failed....
VBQ24 said:
Okay, I wiped all partitions, installed JellyTime AOKP, restarted, went into fastboot, extracted/flash boot file and the rebooted phone.
The phone will now progress from the HTC screen but is now stuck on a black screen, Windows tried to install drivers but failed....
Click to expand...
Click to collapse
Was the boot.img file flashed successfully?
Yes it said so...
EDIT: Not sure if this is an issue with the ROM of if I'm doing something wrong? I went to the "mounts and storage" section of CWM and clicked all the format options accept sdcard. I then installed ROM, went into fastboot and flashed boot.img, it said OKAY twice then finished. Still stuck at black, backlit screen after HTC screen. ROM is JellyTime by randomblame.
VBQ24 said:
Yes it said so...
Click to expand...
Click to collapse
that is weird. Try flashing a different rom then and see what happens. flash the boot image first and then the the rom in recovery.
glevitan said:
that is weird. Try flashing a different rom then and see what happens. flash the boot image first and then the the rom in recovery.
Click to expand...
Click to collapse
I've just tried flashing the boot image first and then installing JellyTime AOKP, same black screen. Maybe I should try a Gingerbread ROM? That's the Operating system I had before, is there a known working ROM?
VBQ24 said:
I've just tried flashing the boot image first and then installing JellyTime AOKP, same black screen. Maybe I should try a Gingerbread ROM? That's the Operating system I had before, is there a known working ROM?
Click to expand...
Click to collapse
Sorry, have You checked the md5sum of the file? Maybe You have a bad download...if that it Is ok, then try flashing a totally different rom and see what happens.
glevitan said:
Sorry, have You checked the md5sum of the file? Maybe You have a bad download...if that it Is ok, then try flashing a totally different rom and see what happens.
Click to expand...
Click to collapse
No I haven't checked the md5sum of the file, how should I go about doing that?
VBQ24 said:
No I haven't checked the md5sum of the file, how should I go about doing that?
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.fab.md5
EDIT: well, don't I feel stupid. I knew full well from reading that your phone wasn't working, but posted a link to an app. Just not paying attention. Sorry about that.
VBQ24,
You can go back to stock by flashing a stock RUU from your PC.
(Edit: You should relock your bootloader first. you can do so from Hboot. There's an option that says relock bootloader or something like that)
The version of the RUU should be equal or greater to the version that came with your phone. Try this v3.13
However, if you want to flash a custom ROM:
You need to downgrade your device first, get s-off and root, then flash a custom ROM
You need to use the Advanced Ace Hack Kit (AAHK), get it from here.
Make sure to read the manual (called 'effin manual) word by word. There are instructions on how to downgrade.
Follow the instructions, and if you have any questions, ask here.
Hi all,
i tried to Root and Flash a new rom on my Arc S...
i managed to root it and put CWM on it... so i tried to flash a Rom, it worked all booted up into new homescreen but then i had to install GApps aswell, i Installed the .zip and rebooted but it got stuck in the Sony Boot logo
Please can someone help me?
Thanks,
Sam
samparsons1 said:
Hi all,
i tried to Root and Flash a new rom on my Arc S...
i managed to root it and put CWM on it... so i tried to flash a Rom, it worked all booted up into new homescreen but then i had to install GApps aswell, i Installed the .zip and rebooted but it got stuck in the Sony Boot logo
Please can someone help me?
Thanks,
Sam
Click to expand...
Click to collapse
Hi Sam,
You can use CWM to format "system", and clear the cache.
Then re-flash the rom, and see if that allows you to boot up normally.
If this fails, then you can flash one of the stock roms on this thread to get your phone up and running again - http://forum.xda-developers.com/showthread.php?t=1653188
Once you are up and running, remember to make a CWM backup before trying something risky (and yes, Google apps can be considered risky )
Hotfingers said:
Hi Sam,
You can use CWM to format "system", and clear the cache.
Then re-flash the rom, and see if that allows you to boot up normally.
If this fails, then you can flash one of the stock roms on this thread to get your phone up and running again - http://forum.xda-developers.com/showthread.php?t=1653188
Once you are up and running, remember to make a CWM backup before trying something risky (and yes, Google apps can be considered risky )
Click to expand...
Click to collapse
Hi Hotfingers,
i would do that if i could actually get to CWM its just stuck on the Sony Screen...
ive tried CWM and Fastboot but they arnt working
so now im stuck with that thats not working and a Orange San Francisco
samparsons1 said:
Hi Hotfingers,
i would do that if i could actually get to CWM its just stuck on the Sony Screen...
ive tried CWM and Fastboot but they arnt working
so now im stuck with that thats not working and a Orange San Francisco
Click to expand...
Click to collapse
OK, so now you need to use "flashtool" - you'll have to search for it on the forums if you don't know what to look for...
Then you can find the firmware for your phone on this thread - http://forum.xda-developers.com/showthread.php?p=22105604
When you use flashtool with a firmware like this it overwrites the entire operating system with one that definitely works - even if you have a locked boot-loader.
Once you have a working phone you can start with the whole root and custom rom thing again...
Good luck
the reason for your bootloop is wrong kernel i think... you may have tried to flash jellybean rom with ics kernel...try to change kernel if you wanna flash jb again
Hotfingers said:
OK, so now you need to use "flashtool" - you'll have to search for it on the forums if you don't know what to look for...
Then you can find the firmware for your phone on this thread - http://forum.xda-developers.com/showthread.php?p=22105604
When you use flashtool with a firmware like this it overwrites the entire operating system with one that definitely works - even if you have a locked boot-loader.
Once you have a working phone you can start with the whole root and custom rom thing again...
Good luck
Click to expand...
Click to collapse
Hello, Hotfingers
I'm sorry to revive this old thread, but I seem to have the same problem - only I flashed back to my stock firmware using flashtool and it's STILL stuck on the Sony logo for a whole half hour with nothing new on the screen. Can anyone help me out here?
edit: never mind, I found out that I was flashing the kernel the whole time rather than the firmware. Thank you very much for the help!
Hotfingers please Help ME
the phone only shows the sony logo but does connect by fastboot.
i have attached the log. the flashtool wont go pass where it says device connected.
please help....
same problem here
To recover, put your phone into flashmode and then install stock firmware from a FTF file by using Flashtool.
Hi everyone!
A friend of mine tried to flash/destroy his n7100 (i don't know why!) so He gave it to me to "play" and try to recover it.
I think that He tried to flash a 4.4.2 stock rom taken somewhere, so I have the lastest bootloader
I recovered it with KIES (that installed android 4.3) and the phone (now) boot completely and works at 100%!
BUT
sometimes when I detach it from power cord it immediatelly reboot and remain stuck at the "samsung galaxy note n7100" screen and bootloops.
If I reattach the power cord at the next poweroff/poweron cycle the phone start correctly and works 100%!!
Actually I'm on a full stock with root and TWRP installed, but this reboots happens also on full stock
It's really strange and I don't know how to get rid of this!
Actually the custom flash counter report 9 and the knox warranty void is at 1.
Someone has any idea of to get rid of theese strange reboots?
aleritty said:
Hi everyone!
A friend of mine tried to flash/destroy his n7100 (i don't know why!) so He gave it to me to "play" and try to recover it.
I think that He tried to flash a 4.4.2 stock rom taken somewhere, so I have the lastest bootloader
I recovered it with KIES (that installed android 4.3) and the phone (now) boot completely and works at 100%!
BUT
sometimes when I detach it from power cord it immediatelly reboot and remain stuck at the "samsung galaxy note n7100" screen and bootloops.
If I reattach the power cord at the next poweroff/poweron cycle the phone start correctly and works 100%!!
Actually I'm on a full stock with root and TWRP installed, but this reboots happens also on full stock
It's really strange and I don't know how to get rid of this!
Actually the custom flash counter report 9 and the knox warranty void is at 1.
Someone has any idea of to get rid of theese strange reboots?
Click to expand...
Click to collapse
Reinstall correct bootloader for rrom using Odin.
Mufrad said:
Reinstall correct bootloader for rrom using Odin.
Click to expand...
Click to collapse
The actual bootloader is installed by kies... So which bootloader I have to install?
The only one that odin let me flash without problem is the one with 4.4.2 android from
N7100XXUEMK9_N7100ITVEMK2_N7100XXUEMJ9
every other bootloader I tried give me a flash error and the screen show "incompatible version".
This will solve also the reboot part?
aleritty said:
The actual bootloader is installed by kies... So which bootloader I have to install?
The only one that odin let me flash without problem is the one with 4.4.2 android from
N7100XXUEMK9_N7100ITVEMK2_N7100XXUEMJ9
every other bootloader I tried give me a flash error and the screen show "incompatible version".
This will solve also the reboot part?
Click to expand...
Click to collapse
Flash the bootloader then flash 4.4.2 rom, you can try this rom
forum.xda-developers.com/showthread.php?t=2672758
Should stop the sudden reboots.
Mufrad said:
Flash the bootloader then flash 4.4.2 rom, you can try this rom
forum.xda-developers.com/showthread.php?t=2672758
Should stop the sudden reboots.
Click to expand...
Click to collapse
Hello,
I have the same issues but I fear in my case these are early symptoms of a EEMC brick bug :crying:
I am on TWRP with Omega v24 and latest bootloader (i know because I have wifi, otherwise I would't have)
I got inconsistencies in the file system and today I had a UID mismatch message error at boot
I would like to format all the partitions (data/system/ecc) and flash a Rom via Odin just be sure...
Why are you sure that this rom should avoid reboot errors? Is there anyway to install this ROM or any other ROM via Odin so I can format all the partitions just to be sure?
Thanks!
Mufrad said:
Flash the bootloader then flash 4.4.2 rom, you can try this rom
forum.xda-developers.com/showthread.php?t=2672758
Should stop the sudden reboots.
Click to expand...
Click to collapse
Which bootloader? the latest from
N7100XXUEMK9_N7100ITVEMK2_N7100XXUEMJ9
because I actually have it...
Is there anyway to install this ROM or any other ROM via Odin so I can format all the partitions just to be sure?
Click to expand...
Click to collapse
You can flash with odin and repartition with your pit (or another from xda but be careful with that) your same stock and then flash the indicated rom so you have a clean installation
aleritty said:
Which bootloader? the latest from
N7100XXUEMK9_N7100ITVEMK2_N7100XXUEMJ9
because I actually have it...
You can flash with odin and repartition with your pit (or another from xda but be careful with that) your same stock and then flash the indicated rom so you have a clean installation
Click to expand...
Click to collapse
Sure go ahead and flash that bootloader.
SergioBigred said:
Hello,
I have the same issues but I fear in my case these are early symptoms of a EEMC brick bug :crying:
I am on TWRP with Omega v24 and latest bootloader (i know because I have wifi, otherwise I would't have)
I got inconsistencies in the file system and today I had a UID mismatch message error at boot
I would like to format all the partitions (data/system/ecc) and flash a Rom via Odin just be sure...
Why are you sure that this rom should avoid reboot errors? Is there anyway to install this ROM or any other ROM via Odin so I can format all the partitions just to be sure?
Thanks!
Click to expand...
Click to collapse
Do you have cwm? Then you can full wipe, then again you can format each partition separately, then go to android development thread, rom repository and download and flash stock rom, I suggested that specific rom because without the air command mod it's almost stock, without the Damned Knox.
Mufrad said:
Sure go ahead and flash that bootloader.
Click to expand...
Click to collapse
Ok thanks! I'll let you know how does it work!
Mufrad said:
Sure go ahead and flash that bootloader.
Do you have cwm? Then you can full wipe, then again you can format each partition separately, then go to android development thread, rom repository and download and flash stock rom, I suggested that specific rom because without the air command mod it's almost stock, without the Damned Knox.
Click to expand...
Click to collapse
I have TWRP, so I will do that from there.
Which STock rom do you suggest? I am on 4.3.2, I should use this?
http://forum.xda-developers.com/showthread.php?t=2536423
It seems it has Know anyway...
Should I use a pit file to repartition it?
Thanks!
aleritty said:
Ok thanks! I'll let you know how does it work!
Click to expand...
Click to collapse
Ok, I flashed bootloader (only sboot) from
N7100XXUEMK9_N7100ITVEMK2_N7100XXUEMJ9
then flashed
n7100xxufnb4_unsecure.zip
from TWRP (and wiped everything before flashing of course)
The situation is the same of before, but the phone now doesnt boot completely, just remains at "samsung" logo.
Any idea?
aleritty said:
Ok, I flashed bootloader (only sboot) from
N7100XXUEMK9_N7100ITVEMK2_N7100XXUEMJ9
then flashed
n7100xxufnb4_unsecure.zip
from TWRP (and wiped everything before flashing of course)
The situation is the same of before, but the phone now doesnt boot completely, just remains at "samsung" logo.
Any idea?
Click to expand...
Click to collapse
Flash this bootloader www.mediafire.com/download/b59xde333z6q8pv/BL_N7100XXUEMJ5_1903221_REV04_user_low_ship.tar.md5
Mufrad said:
Flash this bootloader www.mediafire.com/download/b59xde333z6q8pv/BL_N7100XXUEMJ5_1903221_REV04_user_low_ship.tar.md5
Click to expand...
Click to collapse
Yes Sir! Flashing!
aleritty said:
Yes Sir! Flashing!
Click to expand...
Click to collapse
Flashed this bootloader, heimdall give me:
Code:
Uploading BOOTLOADER
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: BOOTLOADER upload failed!
Ending session...
and on the phone in red appear: unsupported version.
When I reboot appear
"Firmware upgrade encountered an issue. Please select recovery mode in kies & try again.
i have the same issue my note 2 restarting rapidly after a vibrate in samsung logo and successfully start up only when charger is connected. it happen after i install 4.4.2 leaked and revert to 4.3
Hi guys!
After I restored my 5.0.2 nandroid backup from 5.1.1, I forgot to wipe dalvik/cache.
Now the device boots, but i cant access recovery (red notification light on boot).
After it comes up, almost every process is stopped, and after less than a minute the device reboots.
Does anybody have a solution?
5.0.2 (.242) rooted.
Oreltub said:
Hi guys!
After I restored my 5.0.2 nandroid backup from 5.1.1, I forgot to wipe dalvik/cache.
Now the device boots, but i cant access recovery (red notification light on boot).
After it comes up, almost every process is stopped, and after less than a minute the device reboots.
Does anybody have a solution?
5.0.2 (.242) rooted.
Click to expand...
Click to collapse
I would try fastboot. If you can flash any boot and recovery IMG combo that would get you into recovery, you could re-restore your backup. Lots of files available for download in the forums. If you don't have fastboot set up, and don't want to, maybe just reflash ROM and re-root, since rooting 5.0 is not a big deal. Then you could get back to recovery.
levone1 said:
I would try fastboot. If you can flash any boot and recovery IMG combo that would get you into recovery, you could re-restore your backup. Lots of files available for download in the forums. If you don't have fastboot set up, and don't want to, maybe just reflash ROM and re-root, since rooting 5.0 is not a big deal. Then you could get back to recovery.
Click to expand...
Click to collapse
didnt really understand the fastboot option..
can i do the ROM reflash without loosing data?
Oreltub said:
didnt really understand the fastboot option..
can i do the ROM reflash without loosing data?
Click to expand...
Click to collapse
Probably not without recovery. If your bl is unlocked, you can use fastboot on your PC to get into recovery. Start with this - http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
levone1 said:
Probably not without recovery. If your bl is unlocked, you can use fastboot on your PC to get into recovery. Start with this - http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Click to expand...
Click to collapse
Update- i managed to flash 5.0.2 via flashtool, and didn't wipe data..
It works (apps still installed, no data disappeared) , but it seems like i have no data partition (storage notification, can't install apps, empty folder in ES Explorer..)
Update 2- I installed kk ROM, rooted it, and updated to lp..
Thank you levone1!
Mods can lock the thread.
Xperia Z1 Compact .242
Long story short, I made my phone bricked with a small mistake:
I had Freedom OS (latest build) and then tried to flash Miui rom. To do so, I needed to flash back to official Hygrogen/Oxygen OS (MM). The mistake I made was to lock bootloader first. Then, phone got into bootloop....I searched and found Qualcomm software can revive any Qualcomm phone. I downloaded Qualcomm app and driver for Oneplus 3 and tried reviving my phone....What happened finally was that the phone was restarted and a screen showing Cache failed, System failed, userdata failed appeared. I tried to find Cache, system img ...of OOS 4.02 to flash separately....while I couldn't find them anywhere...I just tried fastboot flashing a recovery (both official and TWRP) but got error that partition doesn't allow writing (I guess because phone is locked now)....anyway, phone can boot only in fastboot and I wonder what else I can do....
Any help is very much appreciated!
alireza.nasibi said:
Long story short, I made my phone bricked with a small mistake:
I had Freedom OS (latest build) and then tried to flash Miui rom. To do so, I needed to flash back to official Hygrogen/Oxygen OS (MM). The mistake I made was to lock bootloader first. Then, phone got into bootloop....I searched and found Qualcomm software can revive any Qualcomm phone. I downloaded Qualcomm app and driver for Oneplus 3 and tried reviving my phone....What happened finally was that the phone was restarted and a screen showing Cache failed, System failed, userdata failed appeared. I tried to find Cache, system img ...of OOS 4.02 to flash separately....while I couldn't find them anywhere...I just tried fastboot flashing a recovery (both official and TWRP) but got error that partition doesn't allow writing (I guess because phone is locked now)....anyway, phone can boot only in fastboot and I wonder what else I can do....
Any help is very much appreciated!
Click to expand...
Click to collapse
Try this method now it will work
https://forum.xda-developers.com/showpost.php?p=68245482&postcount=111
The point is I can't flash anything on any partition as phone is locked and can't be unlocked!
alireza.nasibi said:
The point is I can't flash anything on any partition as phone is locked and can't be unlocked!
Click to expand...
Click to collapse
If you can access fastboot mode then you can definitely flash by other method
abhi0502 said:
If you can access fastboot mode then you can definitely flash by other method
Click to expand...
Click to collapse
you mean the 2nd method?
You said you lock the bootloader in 5th line, in order to flash any recovery you need to unlock bootloader again.
I also tried to lock bootloader last week and then my op3 got bricked with bootloop.
-First get into fastboot and unlock bootloader this will wipe your all data including you saved ROM files.
- after this flash TWRP or OnePlus recovery and sideload OOS ROM. Or transfer the ROM file using mtp in TWRP recovery.
- then you can easily do anything you want. Don't relock bootloader.
Those red things on your screen basically means your phone misses partitions, without these partitions it doesn't boot duhh.
If method 2 of the unbrick tool doesn't work, you can manually flash those files in Fastboot, the program has a folder that has all partitions like, cache.img, boot.img etc. I've been here as well nothing to worry about just keep us updated so we can help you
There's no mention in your post on which unbrick method you used. Was it first or second? By the looks of the end result, it was the first.
Just follow the same steps, but use method 2, that should leave you with a phone like out of the factory. Afterwards, you can simply set it up and let it update through OTA if you want to remain stock, or simply unlock bootloader, flash TWRP and flash whatever you want.
use the second method. the file you have to download contains all the raw room and when you follow the process, it would work. happened to me two times and i used this method
Just simply use fastboot oem unlock in fastboot mode then flash a recovery via fastboot flash recovery then go to recovery and once wipe all the partions and install a rom and then tried booting
Thank you all for your time and support. Method 2 saved my phone!