Database Develop

[SOLVED] Am I bricked? PLEASE help me :(

Hi guys. I'm quite a noob, but have a good experience on flashing without be bricked (CM9, CM10, Crash, Paranoid...), but I have a problem.
I will explain to you step-by-step what I've done with my Note, so I wish some of you could help me.
1) I was running JB Crash ROM with PhilZ kernel.
2) Some apps got Force Close too often, so I went on Rom Manager and, after a look into the "Fix permissions" description ("It will fix some force closes" or something like that), I decided to give it a try and I tapped on it.
3) After that, my homescreen became unusable, because "TouchWiz Home" got EVERY TIME force closed without reason. Everything else worked fine, so I deciced to boot into CWM recovery to restore a nandroid backup of the same ROM.
4) Instead of tapping "restore", I tapped "backup" (my fault) and it started without possibility of get back. I got something like 200 Mb of free space, so in every case it will never have had success. My Note stucked at this point, so I decided to reboot manually (vol up+home+power) into recovery. Finally I tried to "restore" but I get this message: "ERROR WHILE RESTORING /SYSTEM".
5) I tried to reboot my Note, but it stucks at "Samsung Galaxy Note GT-N7000" screen without going on.
The good news is that it can go without problems into recovery and into download mode. What can I do? Flashing from CWM, for example, CM9 can fix this?
Please help me thanks!

1. Boot into CWM
2. Wipe data, dalvik and cache
3. Format system
4. Reflash your ROM
Don't use rom manager it's not compatible ....

friedje said:
1. Boot into CWM
2. Wipe data, dalvik and cache
3. Format system
4. Reflash your ROM
Don't use rom manager it's not compatible ....
Click to expand...
Click to collapse
After formatting /system, can I try to restore my nandroid backup? Or I have to necessary reflash my ROM? In that case, it's the same thing make it via CWM or via ODIN PC? I'm still on PhilZ recovery, which is safe I guess!
Anyway, thanks for your help

Via CWM or Odin, depends if you have your rom in the zip or the md5.tar format.
I would reflash to be clean. It's a bit more work in restoring your apps and data
afterwards, but at least you don't restore any messed up files.

if you can still access CMW and Download Mode then you probably are not brick... try fresh install through pc odin.. safe method no need to worry about bricking by fullwiping on unsafe kernel or raising triagle or binary counter whatsoever.. if you wanna play safe then PC ODIN and after that you can root your rom

Thank you guys, now I'm on stock ICS flashed via PC Odin and everything works fine I knew I was 99% not-bricked (still recovery and download mode avaiable), but I was a little scared too.
Thank you again!

glad you solved it.. :good:

CWM Recovery Won't Install

I'm following this tutorial on how to root my Orange UK GT-I9305 LTE Unlocked phone running 4.1.2.
Everything goes fine with Odin the phone reboots, then I unplug and turn off my phone, and boot into recovery mode only to find it hasn't installed and Android system recovery 3e is still there.
Any ideas what I'm doing wrong?

synthecypher said:
I'm following this tutorial on how to root my Orange UK GT-I9305 LTE Unlocked phone running 4.1.2.
Everything goes fine with Odin the phone reboots, then I unplug and turn off my phone, and boot into recovery mode only to find it hasn't installed and Android system recovery 3e is still there.
Any ideas what I'm doing wrong?
Click to expand...
Click to collapse
Not flashing as instructed is the usual .Like unzipping the file or wrong file faulty file download .
Try another recovery.
jje

JJEgan said:
Not flashing as instructed is the usual .Like unzipping the file or wrong file faulty file download .
Try another recovery.
jje
Click to expand...
Click to collapse
I did follow them to the letter, does installing CWM Recovery actually root the phone or is "rooting" the phone a different process entirely that's required for installing CWM Recovery?.
:laugh:
Phone: Samsung Galaxy S3 LTE
Model Number: GT-I9305
Build Number: JZO54K.I9305XXBMF1

synthecypher said:
I did follow them to the letter, does installing CWM Recovery actually root the phone or is "rooting" the phone a different process entirely that's required for installing CWM Recovery?.
:laugh:
Phone: Samsung Galaxy S3 LTE
Model Number: GT-I9305
Build Number: JZO54K.I9305XXBMF1
Click to expand...
Click to collapse
All depends upon the package but most CWM are root and recovery .
TRYhttp://forum.xda-developers.com/showthread.php?t=2002953

Ended up using Auto-Root which seemed to work no problem.

synthecypher said:
Ended up using Auto-Root which seemed to work no problem.
Click to expand...
Click to collapse
I initially had a rooted stock ROM that i was using for ages then upgraded to a custome ROM but for personal reasons decided to go back to stock.
Loaded stock ROM with intention of rooting only to get rid of bloatware, but not one of the ODIN Flash recoveries work at all, not one, so like you ended up using CF Auto and that worked but now im still stuck with Stock Recovery. I dont understand why none of the recoveries flash when they did before.
Cheers

trouble with cwm/ twrp
Hi all. Yes I'm a noob and I wouldn't ask If hadn't tried a plethora of ways to install either cwm or twrp.
It took me a good hour to find this thread so hope I'm in the right place.
Ok I used odin to root and cwm didn't stick so still on stock rec. However I used framaroot to get super su working and titanium says I'm all rooted up. Other apps only for root also work.
I've since tried using goo manager and Rom manager to install cwm or twrp and both say unsupported.
I've searched these here threads and found a few with same problem namely when using odin cwm wont stick and android reinstalls stock recovery.
So I'm a bit stuck, I'm rooted but have no cwm or twrp.
Any help would he much appreciated.

Try Philz recovery .

I have never used a custom recovery on this phone but i think i read somewhere that when flashing by odin the thing to do is not let odin reboot the phone. untick the reboot option. then when odin is done flashing and says pass shut down the phone . dont let it boot up.once phone is off you can boot into recovery by vol up+hom+power Here is the tricky part. as soon as you see the white samsung start to load aka bootloader screen release the power button but continue to press volume up and home. you should see the circle with the hat symbol. and enter into clockworkmod once in clockwork mod you will need to wipe data cache and dalvick DO NOT WIPE SYSTEM then flash a custom rom zip that you have previously copied to either your extsdcard or sdcard0 at the same time you probably will want to flash gapps as well. the thing is if you boot up before entering recovery . the default native recovery from samsung will take its place back. maybe it is easier to just flash rom manager in the play store. flash clockworkmod and then boot into recovery from the app itself. I9300 is supported . dont know about I9305

thanks !
ashraf sharif said:
I have never used a custom recovery on this phone but i think i read somewhere that when flashing by odin the thing to do is not let odin reboot the phone. untick the reboot option. then when odin is done flashing and says pass shut down the phone . dont let it boot up.once phone is off you can boot into recovery by vol up+hom+power Here is the tricky part. as soon as you see the white samsung start to load aka bootloader screen release the power button but continue to press volume up and home. you should see the circle with the hat symbol. and enter into clockworkmod once in clockwork mod you will need to wipe data cache and dalvick DO NOT WIPE SYSTEM then flash a custom rom zip that you have previously copied to either your extsdcard or sdcard0 at the same time you probably will want to flash gapps as well. the thing is if you boot up before entering recovery . the default native recovery from samsung will take its place back. maybe it is easier to just flash rom manager in the play store. flash clockworkmod and then boot into recovery from the app itself. I9300 is supported . dont know about I9305
Click to expand...
Click to collapse
Thats exactly how I understood the cwm not sticking problem. I have tried rom manager and said not compatable with my device as did goo manager for twrp. I think odin is the only way I get it to stick. So il flash in odin and il try to get into cwm as it boots and wipe those two files you mentioned.
But then can I just boot up as normal ? or will android try to reflash its stock rom ? Damn my phone for being so difficult
I only ask because I haven't decided what CR to use yet (or even looked for any). I was gonna get it all ready first then learn how to install a CR - 1 thing at a time i thought.
Anyway thanks for your help :good:
JJEgan I found Philz thread to be helpful but something I feel Im just not ready for. Im new to this and although the updated cwm looked cool there were just to much going on, maybe for a later day.
Thanks all the same :good:

wiping data plus cache plus dalvick cache is done to prepare your phone for the custom rom that you are going to flash. the wiping is to clean those partitions because if they are not erased you will have problems. especially if you go from one android version to another or touchwiz to aosp. it is done so you get a clean install with minimal issues. if it is not done you will most likely bootloop. effectively it is a factory reset. all of your apps and app data will be gone so you do not want to do that unless you have backed up your apps . however sometimes google automatically installs them after you sign in.
I am not sure why clockwork mod does not stick but if you copy the rom you want to your phone install clockworkmod with odin and then use clockwork mod to flas the rom and gapps package then factory reset you will not have the stock recovery anymore. but this has to be done without booting into android stock . PLEASE FOLLOW THE FLASHING INSTRUCTIONS TO THE BEST OF YOUR ABILITY. AND UNDERSTAND ANYTIME YOU FLASH OR MODIFY YOUR PHONE YOU VOID YOUR WARRANTY AND POSSIBLY CAN CAUSE IRREPARABLE DAMAGE. BEST OF LUCK!
---------- Post added at 04:28 PM ---------- Previous post was at 04:24 PM ----------
Also philz recovery is highly recommended
HERE IS SOME VERY GOOD READING http://forum.xda-developers.com/showthread.php?t=2362743&highlight=philz+recovery http://forum.xda-developers.com/showthread.php?t=2344125

think I got it lol
Ok that's sounds good. However I've just read the threads you linked and now I've got to back up my imei and NV files first or il loose them when flashing. The procedure is all there and seems doable for a noob but i read some peeps are having trouble just doing that. I really wanted to root/install a CR regardless of the troubles cos I want full access and more importantly want to learn all the ins and outs so I can get the best use from my phone so glad I found this forum cause I'm sure I would have bricked my phone otherwise.
Might I ask if I've got this right tho?
1: backup imei/NV files
2: use odin to get cwm to stick using your method
3: boot into cwm to wipe data/dalvick cache and gapps
4:use cwm to flash a CR
5:factory reset
I think that's right?

CLOSE
1 BACKUP EFS FOLDER(IT CONTAINS imeiAND SERIAL NUMBER AND OTHER NETWORK SETTINGS) MAKE AT LEAST 2 BACKUPS ONE FOR EXTERNAL SDCARD AND ONE TO KEEP ON YOUR PC
2 INSTALL CWM RECOVERY USING ANY WORKING METHOD. byTHE WAY PHILZ CAN BACKUP EFS.
3 IN CWM RECOVERY MAKE A NANDROID BACKUP OF YOU CURRENT ROM. I FORGOT TO TELL YOU THAT ,THIS IS IN CASE YOUR FLASH FAILS YOU CAN RESTORE CURRENT ROM FROM BACKUP. ALWAYS BACKUP BEFORE A FLASH
4 IN CWM RECOVERY WIPE DATA, CACHE , AND DALVIK CACHE
5 IN CWM RECOVERY FLASH ZIP FOR ROM AND FLASH ZIP FOR GAPPS "GOOGLE APPS"
6 BOOT ANDROID THIS MAY TAKE UP TO 10 MINUTES FOR THE INITIAL BOOT. BE PATIENT. IF IT BOOTS YOU ARE DONE
7 IF PHONE DOES NOT BOOT THEN IN RECOVERY WIPE DATA AND CACHE AND DALVIK AGAIN
8 STILL NOT BOOTING FLASH ROM ANG GAPPS AGAIN
NOT BOOTING? RESTORE NANDROID
FACTORY RESET=WIPE DATA AND CACHE
DONT EVER WIPE SYSTEM UNLESS YOU HAVE A RECENT NANDROID. NANDROID IS GOOD BUT THE OLDER IT IS THE MORE LIKELY IT IS TO GET CORRUPTED
ALSO IF YOU GET FORCE CLOSES FIXING PERMISSIONS USUALLY WORKS FOR THAT.
SOME ROMS ARE FLASHED IN DIFFERENT WAYS .ALWAYS FOLLOW THE DEVELOPERS INSTRUCTIONS

i had the same Problem before.
I Just disassembled the battery after a full-wipe for few minutes and it works... i don't know y, but that was the only way... ?!

brilliant thanks!
ashraf sharif said:
CLOSE
1 BACKUP EFS FOLDER(IT CONTAINS imeiAND SERIAL NUMBER AND OTHER NETWORK SETTINGS) MAKE AT LEAST 2 BACKUPS ONE FOR EXTERNAL SDCARD AND ONE TO KEEP ON YOUR PC
2 INSTALL CWM RECOVERY USING ANY WORKING METHOD. byTHE WAY PHILZ CAN BACKUP EFS.
3 IN CWM RECOVERY MAKE A NANDROID BACKUP OF YOU CURRENT ROM. I FORGOT TO TELL YOU THAT ,THIS IS IN CASE YOUR FLASH FAILS YOU CAN RESTORE CURRENT ROM FROM BACKUP. ALWAYS BACKUP BEFORE A FLASH
Am I backing up to ext SD card?
4 IN CWM RECOVERY WIPE DATA, CACHE , AND DALVIK CACHE
5 IN CWM RECOVERY FLASH ZIP FOR ROM AND FLASH ZIP FOR GAPPS "GOOGLE APPS"
Are these seperate zips?
6 BOOT ANDROID THIS MAY TAKE UP TO 10 MINUTES FOR THE INITIAL BOOT. BE PATIENT. IF IT BOOTS YOU ARE DONE
7 IF PHONE DOES NOT BOOT THEN IN RECOVERY WIPE DATA AND CACHE AND DALVIK AGAIN
8 STILL NOT BOOTING FLASH ROM ANG GAPPS AGAIN
NOT BOOTING? RESTORE NANDROID
FACTORY RESET=WIPE DATA AND CACHE
DONT EVER WIPE SYSTEM UNLESS YOU HAVE A RECENT NANDROID. NANDROID IS GOOD BUT THE OLDER IT IS THE MORE LIKELY IT IS TO GET CORRUPTED
ALSO IF YOU GET FORCE CLOSES FIXING PERMISSIONS USUALLY WORKS FOR THAT.
SOME ROMS ARE FLASHED IN DIFFERENT WAYS .ALWAYS FOLLOW THE DEVELOPERS INSTRUCTIONS
Click to expand...
Click to collapse
Thank-you for all that,I really appreciate it.
Can I ask the difference between the apps nandroid manager and titanium? I've backed up with both and wondered if i really needed to? The nandroid backup was nearly 3gb!
Also I was gona backup with qpst for imei and NV files but then read its only for US versions? Will the backup of efs folder include those?

honestly i really dont know what the differences are. l do not use custom recoveries or custom roms. i dont use titanium backup .Any rom I flash i get from sammobile.com. one reason i do not use custom roms is that none can support mhl. I use a monitor and bluetooth mouse and keyboard . without mhl I cant mirror my screen so i always stay with stock roms. i use Xposed framework for modifications.

ashraf sharif said:
I have never used a custom recovery on this phone but i think i read somewhere that when flashing by odin the thing to do is not let odin reboot the phone......
Click to expand...
Click to collapse
thx you so much. this was the secound s3 that had this issue. deactivating auto reboot did the job!!!!

Need help bricked phone :(

i recently flashed the eXistenZ Ultra 2, and im sure i did everything fine, after flashing the rom in recovery and flashing suprsu and wifi fix, i powered off the phone, and powered on but sony logo has apeared until now , and welcoming`s sounding 999..times. i cant turn it off, or i should say i cant do anything.
please help,

After flashing ROM and the fixes you should flash the 12.1.A.0.266 Firmware with FlashTool!
If problem still persists:
http://xda-university.com/as-a-user/how-to-recover-from-a-bootloop
Take a look at this site A recovery would be quite useful, but I think the kernel of eXistenZ ROM has one. If not, you'll find one in the development section. Otherwise, use the ADB as solution.
Good luck

Thanx for the post!
I used force shut down and then flash the 254 rom, and did all those things, and the problem occured again.
does the recovery software have to be the touch recovery? I use CWM v6 that enables with volume +.
and i use SuperSU fix.zip rather than superUser.zip and generally i flash rom, supersu fix.zip and wifi fix.zip. i flashed those three, before first booting, do i have to boot first before flashing wifi fix.zip?

eefathi said:
Thanx for the post!
I used force shut down and then flash the 254 rom, and did all those things, and the problem occured again.
does the recovery software have to be the touch recovery? I use CWM v6 that enables with volume +.
and i use SuperSU fix.zip rather than superUser.zip and generally i flash rom, supersu fix.zip and wifi fix.zip. i flashed those three, before first booting, do i have to boot first before flashing wifi fix.zip?
Click to expand...
Click to collapse
I think you need to flash 12.1.A.0.266 instead of 12.0.A.2.254 after flashing ROM. You could also wipe data, cache and dalvik cache, reflash eXistenZ ROM and SuperSU fix (or SuperUser but SuperSU should be ok), shut down the phone with the option in recovery and then flash the 12.1.A.0.266 with FlashTool.
It doesn't matter which recovery you take. Use the one you like best. I'm not quite sure, but to go sure, please flash the wifi fiz.zip after first boot up!

Schokonuss said:
I think you need to flash 12.1.A.0.266 instead of 12.0.A.2.254 after flashing ROM. You could also wipe data, cache and dalvik cache, reflash eXistenZ ROM and SuperSU fix (or SuperUser but SuperSU should be ok), shut down the phone with the option in recovery and then flash the 12.1.A.0.266 with FlashTool.
It doesn't matter which recovery you take. Use the one you like best. I'm not quite sure, but to go sure, please flash the wifi fiz.zip after first boot up!
Click to expand...
Click to collapse
thanx again,
i flashed the 266 kernel before the first boot, and the rom runs correctly,
but ive got some new problems:
1. performance, when i click on performance, it closes unexpectedly and says it has stopped.
2. i used go backup for backing up from data in 4.1, but in this rom i restored my apps,the apps installed correctly but goBackup says the data restoring successfully finished , but the data didnt restored, by the way at the time i backed up from my apps&data, i swapped memories with that linux code that this forum did.

eefathi said:
thanx again,
i flashed the 266 kernel before the first boot, and the rom runs correctly,
but ive got some new problems:
1. performance, when i click on performance, it closes unexpectedly and says it has stopped.
2. i used go backup for backing up from data in 4.1, but in this rom i restored my apps,the apps installed correctly but goBackup says the data restoring successfully finished , but the data didnt restored, by the way at the time i backed up from my apps&data, i swapped memories with that linux code that this forum did.
Click to expand...
Click to collapse
You're welcome
1. Do you have SuperSU installed? On AOKP ROM I'm running it asked for superuser permission for ROM Control (the control center implemented in the settings of the ROM). Maybe it'll ask you if SuperSU is installed. Otherwise, because it is after the first boot it needs to rebuild cache and so on.. If problem persists after reboot, just use an other clock speed controler (No-frills CPU, SetCPU..)
2. If you did that at the same time, maybe Go Backup didn't really backup your data. Try again, if it doesn't work and if you have a nandroid backup (backup from recovery) you can go into recovery, then to advanced restore and restore data. Otherwise your data is unfortunately gone I think :/
PS: I prefer Titanium Backup

[Q] Bootlop after failed wiping data [Solved]

Hi guys, i need your help..
I was tried to install a custom ROM and i use CWM v6 to install it (i'm on stock ROM | JB 4.3 | FW .205 | locked bootloader | recovery installed : CWM & TWRP), first step i format the /system and is successfull, then the next step wipe data/factory reset but i get stuck process on:
--- wiping data ---
clear /data done.
clear /cache...........
I don't know why, but i've been waiting for 20 minutes and still stuck like that than i decides to turning off the phone with tiny button at bottom of battery (not power button), i turn on the phone again and then i've got bootlop ( what.... where is my recovery ) i didn't noticed the recovery still in there because there is no LED notify when i turn on the phone, just SONY logo :crying:
Is that happen because wiping data didn't completed and causing my recovery also gone ?
So what should i do ? can i get the phone back again ? I have the stock ROM backup on my sd card and on my laptop because before i try to install a custom ROM, i've created current ROM backup with CWM.
please help me guys..

beespoison said:
Hi guys, i need your help..
I was tried to install a custom ROM and i use CWM v6 to install it (i'm on stock ROM | JB 4.3 | FW .205 | locked bootloader | recovery installed : CWM & TWRP), first step i format the /system and is successfull, then the next step wipe data/factory reset but i get stuck process on:
--- wiping data ---
clear /data done.
clear /cache...........
I don't know why, but i've been waiting for 20 minutes and still stuck like that than i decides to turning off the phone with tiny button at bottom of battery (not power button), i turn on the phone again and then i've got bootlop ( what.... where is my recovery ) i didn't noticed the recovery still in there because there is no LED notify when i turn on the phone, just SONY logo :crying:
Is that happen because wiping data didn't completed and causing my recovery also gone ?
So what should i do ? would i get the phone back again ? I have the stock ROM backup on my sd card and on my laptop because before i try to install a custom ROM, i've created current ROM backup with CWM.
please help me guys..
Click to expand...
Click to collapse
You wiped /system so your recoveries are gone.
On older Recoveries using the wipe to install new rom can take ages so just leave it and eventually it will finish, latest version of Philz (in Bagyusz/Nexus ROMs) seems to fix this issue.
Use DSSMEX triple recovery and use philz not cwm as its a much nicer recovery (but the clean still takes ages as its an older version)
Use flashtool to flash stock rom and start from scratch to re-install custom rom.

Oblox said:
You wiped /system so your recoveries are gone.
On older Recoveries using the wipe to install new rom can take ages so just leave it and eventually it will finish, latest version of Philz (in Bagyusz/Nexus ROMs) seems to fix this issue.
Use DSSMEX triple recovery and use philz not cwm as its a much nicer recovery (but the clean still takes ages as its an older version)
Use flashtool to flash stock rom and start from scratch to re-install custom rom.
Click to expand...
Click to collapse
Oh god, i don't know about that, because this is the first time i've got bootlop..
Where is i can get the latest version of Philz, would you like to give the link ?
Triple recovery ? maybe 2 recovery is enough
Flashtool, okay i'll try to save my phone..

beespoison said:
Oh god, i don't know about that, because this is the first time i've got bootlop..
Where is i can get the latest version of Philz, would you like to give the link ?
Triple recovery ? maybe 2 recovery is enough
Flashtool, okay i'll try to save my phone..
Click to expand...
Click to collapse
You have bootloop because your phone is essentially empty of any OS or recoveries.
Flashtool to stock, find dssmex triple recovery and install that in stock when rooted, load into Philz, clean to install a new ROM and then just wait, it will take a while usually dont worry unless it takes over an hour.
Then flash the custom ROM of choice.

beespoison said:
Hi guys, i need your help..
I was tried to install a custom ROM and i use CWM v6 to install it (i'm on stock ROM | JB 4.3 | FW .205 | locked bootloader | recovery installed : CWM & TWRP), first step i format the /system and is successfull, then the next step wipe data/factory reset but i get stuck process on:
--- wiping data ---
clear /data done.
clear /cache...........
I don't know why, but i've been waiting for 20 minutes and still stuck like that than i decides to turning off the phone with tiny button at bottom of battery (not power button), i turn on the phone again and then i've got bootlop ( what.... where is my recovery ) i didn't noticed the recovery still in there because there is no LED notify when i turn on the phone, just SONY logo :crying:
Is that happen because wiping data didn't completed and causing my recovery also gone ?
So what should i do ? can i get the phone back again ? I have the stock ROM backup on my sd card and on my laptop because before i try to install a custom ROM, i've created current ROM backup with CWM.
please help me guys..
Click to expand...
Click to collapse
Can I know what Custom ROM are you trying to install?
Sometimes wiping could take time, and I am not sure why. If happens again in the future, just let it be.
As you are using LBL, I am unable to elaborate nor understand how recovery has gone. (WARNING: FOREIGN LANGUAGE) Recoveries for LBL are stored in the ramdisk OR the FOTAkernel. This is due to the fact that Xperia SP does not has an exclusive "recovery" partition in the rootfs. I dont know if wiping data would trash them.
You can easily recover your phone by flashing a stock ftf. You may follow this guide: http://forum.xda-developers.com/showpost.php?p=56717587&postcount=4

Oblox said:
You have bootloop because your phone is essentially empty of any OS or recoveries.
Flashtool to stock, find dssmex triple recovery and install that in stock when rooted, load into Philz, clean to install a new ROM and then just wait, it will take a while usually dont worry unless it takes over an hour.
Then flash the custom ROM of choice.
Click to expand...
Click to collapse
Thanks for your explanation sir :good:
Flashtool to stock means i need .ftf file to restore the stock rom ? is it possible to restore stock rom through nandroid backup file that i've created using cwm ?

Well, the problem is solved. My phone back again and a custom rom has been installed.

beespoison said:
Oh god, i don't know about that, because this is the first time i've got bootlop..
Where is i can get the latest version of Philz, would you like to give the link ?
Triple recovery ? maybe 2 recovery is enough
Flashtool, okay i'll try to save my phone..
Click to expand...
Click to collapse
Dont use flashtool..... Youre wasting time.
Just flash Williams kernel using fastboot and flash the custom rom you want.....

Furrydaus said:
Dont use flashtool..... Youre wasting time.
Just flash Williams kernel using fastboot and flash the custom rom you want.....
Click to expand...
Click to collapse
Thanks for your advice, but my phone has been repaired

A cry for help

Hello all,
Firstly I would like to thank all the great people here, I've been struggling for hours with my dead Xperia Z and the amount of dedication and support I've found so far across all the members here is really impressing.
Let me first illustrate my case.
Firstly, I came here to root my phone and install a custom rom ships with Android N 7.1.2 (Resurrection Remix), I did went through all the newbies/how to threads and I did successfully ended up with Android N on my phone
Unfortunately, the device was not working probably in case of incoming or outgoing calls. No ringtone (already selected from Settings >Sound - played and heared), while in call it keeps ending the call unexpectedly, sometimes it feels very laggy that I couldn't even tap on anything. So I decided to give up until I found another rom that ships with Android N (XOSP), after successfully installing the rom, it starts out very smooth and I tested everything and it was ok, until yesterday the same issue still persists plus my device mic is not working no one can hear me while I'm talking neither from a headset mic nor the device mic. Finally I gave up and decided to rollback to the old lolipop stock rom.
Here's comes the current problem:-
1- I did flash 10.7.A.0.222 Customized MEA using flash tool and it's flashed successfully.
2- I'm now stuck with a dead black screen after sony logo.
I tried everything, changed the flashtool version, downloaded other ftf kernel file, used Xperia Companion and non of them worked for me. I did also tried what's listed in here https://forum.xda-developers.com/xperia-z/general/disaster-recovery-getting-z1-zu-z-zl-to-t2229250
I only can boot into fastboot or flashboot mode
I cannot copy files to my phone as it never appears as a storage media in my computer.
Any help will be much appreciated
Sorry for the long post

I never had this problem before, but have you try other ftf with lower android version like KK?
I see this problem on someone, everyone of them had this problem when they try to revert back to stock LP from N. Then someone suggest to flash KK ftf. You should try this if you haven't try this.
Sorry if my English is bad.
UPDATE:
when the first 7.0 nougat custom rom came, I'm on 5.1.1 rom with XZDual recovery. I made a backup for this rom and flash the 7.0 N rom only for trial then revert back to stock 5.1.1 that I backup before. Chippa's rom always came with latest built-in recovery so when I upgrade to nougat rom the XZDual recovery also lost (I don't have FOTA recovery, lol).
The step I made to revert back to stock is to do a FULL wipe of the phone (cache, davlik cache, data, system, AND internal storage), not a regular full wipe (without internal storage).
I put my backup stock rom file to my external sdcard (because the internal storage got wiped) and begin to flash, BUT NOT reboot into system, I reboot the phone to recovery instead (because I think the 5.1.1 rom works better with old TWRP so I reboot the phone to recovery first to get the old XZDual recovery).
After phone enter the old TWRP, I do a FULL wipe (cache, davlik, data, system, internal storage) once again to make sure everything OK, then flash the stock rom once again.
aand... it works. I did it 3-4 times to test new build of 7.0 n rom and never have any problem of reverting back.
But, I never test this method on newest 7.1.1 rom or 7.1.2 rom.
since you can't boot on LP rom, then try to flash KK rom.
Just install phone driver, flashtool, and download the KK ftf.
I'm sorry I can't provide you the full instruction because I never had this problem before, but you can search for this on N rom thread (the rom developed by Chippa). There is a guide made by someone on that thread.

Zerikwan said:
I never had this problem before, but have you try other ftf with lower android version like KK?
I see this problem on someone, everyone of them had this problem when they try to revert back to stock LP from N. Then someone suggest to flash KK ftf. You should try this if you haven't try this.
Sorry if my English is bad.
UPDATE:
when the first 7.0 nougat custom rom came, I'm on 5.1.1 rom with XZDual recovery. I made a backup for this rom and flash the 7.0 N rom only for trial then revert back to stock 5.1.1 that I backup before. Chippa's rom always came with latest built-in recovery so when I upgrade to nougat rom the XZDual recovery also lost (I don't have FOTA recovery, lol).
The step I made to revert back to stock is to do a FULL wipe of the phone (cache, davlik cache, data, system, AND internal storage), not a regular full wipe (without internal storage).
I put my backup stock rom file to my external sdcard (because the internal storage got wiped) and begin to flash, BUT NOT reboot into system, I reboot the phone to recovery instead (because I think the 5.1.1 rom works better with old TWRP so I reboot the phone to recovery first to get the old XZDual recovery).
After phone enter the old TWRP, I do a FULL wipe (cache, davlik, data, system, internal storage) once again to make sure everything OK, then flash the stock rom once again.
aand... it works. I did it 3-4 times to test new build of 7.0 n rom and never have any problem of reverting back.
But, I never test this method on newest 7.1.1 rom or 7.1.2 rom.
since you can't boot on LP rom, then try to flash KK rom.
Just install phone driver, flashtool, and download the KK ftf.
I'm sorry I can't provide you the full instruction because I never had this problem before, but you can search for this on N rom thread (the rom developed by Chippa). There is a guide made by someone on that thread.
Click to expand...
Click to collapse
Thank you so much for your reply. I will try it out. I really appreciate your contribution and I will keep you updated