Soft brick on every custom rom - Xperia Z3 Compact Q&A, Help & Troubleshooting

Hi guys.
Well I am very confused about this. I don't know how to fix it and it locks like there is not a alot of people who had the same problem.
I rooted the device, backed up drm keys, unlocked bootloader.
So and now if I want to install custom roms it installs them but as soon as I reboot it is soft bricked.
I tried it with resurrecting remix lollipop and marshmallow.
I would appreciate it if you could help me.
Thanks

thefanofmusic said:
Hi guys.
Well I am very confused about this. I don't know how to fix it and it locks like there is not a alot of people who had the same problem.
I rooted the device, backed up drm keys, unlocked bootloader.
So and now if I want to install custom roms it installs them but as soon as I reboot it is soft bricked.
I tried it with resurrecting remix lollipop and marshmallow.
I would appreciate it if you could help me.
Thanks
Click to expand...
Click to collapse
Are you sure that your phone can be unlocked? some can't.
You've done the right thing backing up your TA partition.
With an unlocked phone, after you've flashed the rom you will need to flash a kernel .img in flashtool or it won't boot.
I've never tried to unlock my bootloader, so I'm not sure I can give much advice.
Perhaps someone who's got a CM rom working can help?

Didgesteve said:
Are you sure that your phone can be unlocked? some can't.
You've done the right thing backing up your TA partition.
With an unlocked phone, after you've flashed the rom you will need to flash a kernel .img in flashtool or it won't boot.
I've never tried to unlock my bootloader, so I'm not sure I can give much advice.
Perhaps someone who's got a CM rom working can help?
Click to expand...
Click to collapse
Yes it is already unlocked. I looked it up.
Maybe it is kernel which is missing but before I never needed to flash a kernel and the custom Rom. I mean on other Sony devices.

I really need help. I don't know how to solve this.

Have you tried flashing boot.img using fastboot flash boot boot.img command?

mrrflagg said:
Have you tried flashing boot.img using fastboot flash boot boot.img command?
Click to expand...
Click to collapse
Yeah I thought about it to. Will try it later. But why can't I just flash it like a regular zip file

Related

Help, My phone is Bricked

Hi people. I neen your help for booting my phone.
I had Stock 4.4.2, Moto X with camera update and Locked Bootloader, today I stupidly flashed a ROM 4.4.4, I know I have to be on UB, but I forgot it, it was an impulse. I got an error in the flashing, then I tried to flash my sbf Stock Version, but now it says Downgraded security something with gpt and I cannot flash anything, I mean starts flahsing but in boot.img it got stucked, please if someone tried the same and could help me please.
Thanks in advance.
icerebro said:
Hi people. I neen your help for booting my phone.
I had Stock 4.4.2, Moto X with camera update and Locked Bootloader, today I stupidly flashed a ROM 4.4.4, I know I have to be on UB, but I forgot it, it was an impulse. I got an error in the flashing, then I tried to flash my sbf Stock Version, but now it says Downgraded security something with gpt and I cannot flash anything, I mean starts flahsing but in boot.img it got stucked, please if someone tried the same and could help me please.
Thanks in advance.
Click to expand...
Click to collapse
Without Bootloader unlocking how can u flash a rom to your device thats first Mistake ... I think u cant back to u r device...
icerebro said:
Hi people. I neen your help for booting my phone.
I had Stock 4.4.2, Moto X with camera update and Locked Bootloader, today I stupidly flashed a ROM 4.4.4, I know I have to be on UB, but I forgot it, it was an impulse. I got an error in the flashing, then I tried to flash my sbf Stock Version, but now it says Downgraded security something with gpt and I cannot flash anything, I mean starts flahsing but in boot.img it got stucked, please if someone tried the same and could help me please.
Thanks in advance.
Click to expand...
Click to collapse
Mahesh8348 said:
Without Bootloader unlocking how can u flash a rom to your device thats first Mistake ... I think u cant back to u r device...
Click to expand...
Click to collapse
Yep, you are stuck until the full 4.4.4 SBF is released for your carrier. Shouldn't have done that.
Who is your carrier? If it is AT&T, you are in luck! The 4.4.4 SBF was just released. If not....bummer - you will have to wait. Can't flash a ROM with a different CID with a locked BL.
I highly suggest you don't attempt to manually force the older rom. Really, beyond the fact that you flashed the wrong ROM, how did you miss all the warnings that downgrade = brick?
Tough situation to be in. Hopefully you have an AT&T unit. If so, we can help get you fixed up.
Well, I have solved it Unlocking my Bootloader and then reinstalling the rom 4.4.4 retail from Brazil. It works now.
I have a question, now I am in Brazil but I am from Perú, and when I try to change the APN for the one I use in Perú, it deletes itself, so I can not change the APN or create a new one because i can not save it. What is the problem in there?
My phone was Nextel operator, then I unlock it, never had a problem.
Hope your help.
Thanks!

[Q] rooted, unlocked, TWRP recovery, stock, Verizon OTA help

I have a Verizon Nexus 6 that is rooted, unlocked, custom TWRP recovery and stock running 5.1 build LMY47E and I am getting the OTA notification for the 5.1.1 update. I have searched a good deal of places and haven't found the answer to how I might go about getting the update. I have been out of the rooting game for several years, so I am rusty and need a little help. I wasn't sure if there was a way to take the update and stay rooted or if I have to completely undo everything back to stock. Any info would be a great help and appreciated.
I could be mistaken, but I don't think that you can take an OTA amd remain rooted. I think it will break root, and you will have to re-root.
What I would suggest is to just flash a custom ROM that is build on 5.1.1 like Beans' PureNexus. That is what I am running, and it is great.
http://forum.xda-developers.com/nexus-6/development/rom-pure-nexus-project-t3148214
evolefty said:
I have a Verizon Nexus 6 that is rooted, unlocked, custom TWRP recovery and stock running 5.1 build LMY47E and I am getting the OTA notification for the 5.1.1 update. I have searched a good deal of places and haven't found the answer to how I might go about getting the update. I have been out of the rooting game for several years, so I am rusty and need a little help. I wasn't sure if there was a way to take the update and stay rooted or if I have to completely undo everything back to stock. Any info would be a great help and appreciated.
Click to expand...
Click to collapse
a.demarco said:
I could be mistaken, but I don't think that you can take an OTA amd remain rooted. I think it will break root, and you will have to re-root.
What I would suggest is to just flash a custom ROM that is build on 5.1.1 like Beans' PureNexus. That is what I am running, and it is great.
http://forum.xda-developers.com/nexus-6/development/rom-pure-nexus-project-t3148214
Click to expand...
Click to collapse
When installing a recovery, the updater script looks at system and boot. This means that you can not be rooted and and have the stock, encrypted kernel. You also need to have stock recovery to install the OTA.
You can download the 5.1.1 factory image from Google and flash the boot.img, system.img, bootloader.img, and radio.img. Then, while still in bootloader, select "recovery" and you will boot to TWRP where you can flash the SuperSU.zip.
a.demarco said:
I could be mistaken, but I don't think that you can take an OTA amd remain rooted. I think it will break root, and you will have to re-root.
What I would suggest is to just flash a custom ROM that is build on 5.1.1 like Beans' PureNexus. That is what I am running, and it is great.
http://forum.xda-developers.com/nexus-6/development/rom-pure-nexus-project-t3148214
Click to expand...
Click to collapse
The OTA will not install when the device is rooted
cam30era said:
When installing a recovery, the updater script looks at system and boot. This means that you can not be rooted and and have the stock, encrypted kernel. You also need to have stock recovery to install the OTA.
You can download the 5.1.1 factory image from Google and flash the boot.img, system.img, bootloader.img, and radio.img. Then, while still in bootloader, select "recovery" and you will boot to TWRP where you can flash the SuperSU.zip.
Click to expand...
Click to collapse
Just checked again and yes I am rooted, with TWRP and I also checked and the device is not encrypted, so maybe that is why I am getting the notification. I really appreciate your input on getting the update installed.
evolefty said:
Just checked again and yes I am rooted, with TWRP and I also checked and the device is not encrypted, so maybe that is why I am getting the notification. I really appreciate your input on getting the update installed.
Click to expand...
Click to collapse
You'll get the notification. You just can't flash it.
I'm not sure there's been a full, satisfactory answer to this thread (or a few others). Would using something like Nexus Root Toolkit to 1) unroot 2) restore stock recovery, 3) accept the OTA. Will this work?
- Does this relock the bootloader? (Would we then have to unlock, thus wiping the device?)
- Can we successfully re-root and flash recovery? (Or will new 5.1.1 versions be needed?)
At some point, to get 5.1.1 going, should I just backup and flash the whole bloody image from Google?
DogzOfWar said:
I'm not sure there's been a full, satisfactory answer to this thread (or a few others). Would using something like Nexus Root Toolkit to 1) unroot 2) restore stock recovery, 3) accept the OTA. Will this work?
- Does this relock the bootloader? (Would we then have to unlock, thus wiping the device?)
- Can we successfully re-root and flash recovery? (Or will new 5.1.1 versions be needed?)
At some point, to get 5.1.1 going, should I just backup and flash the whole bloody image from Google?
Click to expand...
Click to collapse
- OTA`s will not install if the sytem, boot and recovery are modified in any way.
- Reflashing the stock image will NOT lock the bootloader
- And yes you can flash a custom recovery and reroot after updating.
Or flash the latest stock rom with TWRP from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
gee2012 said:
- OTA`s will not install if the sytem, boot and recovery are modified in any way.
- Reflashing the stock image will NOT lock the bootloader
- And yes you can flash a custom recovery and reroot after updating.
Or flash the latest stock rom with TWRP from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
Click to expand...
Click to collapse
So the question that started this thread: My system is technically modified. Can I unroot and replace recovery, and now be in a sufficiently "unmodified" state? OR, do I have to lock the bootloader in order for the OTA to continue?
I think the OP and myself are trying to do the same thing: We're lazy, we don't want to wipe, we don't want to lose data, we just want the OTA without having to reflash the whole thing. Does anyone know if this is possible?
DogzOfWar said:
So the question that started this thread: My system is technically modified. Can I unroot and replace recovery, and now be in a sufficiently "unmodified" state? OR, do I have to lock the bootloader in order for the OTA to continue?
I think the OP and myself are trying to do the same thing: We're lazy, we don't want to wipe, we don't want to lose data, we just want the OTA without having to reflash the whole thing. Does anyone know if this is possible?
Click to expand...
Click to collapse
Best/easiest is to:
- fastboot erase system
- fastboot flash system system.img
- flash the stock boot and recovery.img if needed
- adb sideload the OTA in stock recovery
This will not wipe your device
And you don`t have to lock the bootloader ever unless you have too RMA it or send it in for service, OTA`s will even install with a unlocked bootloader.
DogzOfWar said:
So the question that started this thread: My system is technically modified. Can I unroot and replace recovery, and now be in a sufficiently "unmodified" state? OR, do I have to lock the bootloader in order for the OTA to continue?
I think the OP and myself are trying to do the same thing: We're lazy, we don't want to wipe, we don't want to lose data, we just want the OTA without having to reflash the whole thing. Does anyone know if this is possible?
Click to expand...
Click to collapse
Supplementing that: using the "unroot" function in SuperSU is not sufficient with Lollipop. It still leaves the vestiges of a few modified files that will cause an OTA to fail.
gee2012 said:
Best/easiest is to:
- fastboot erase system
- fastboot flash system system.img
- flash the stock boot and recovery.img if needed
- adb sideload the OTA in stock recovery
This will not wipe your device
And you don`t have to lock the bootloader ever unless you have too RMA it or send it in for service, OTA`s will even install with a unlocked bootloader.
Click to expand...
Click to collapse
gee2012 said:
Best/easiest is to:
- fastboot erase system
- fastboot flash system system.img
- flash the stock boot and recovery.img if needed
- adb sideload the OTA in stock recovery
This will not wipe your device
And you don`t have to lock the bootloader ever unless you have too RMA it or send it in for service, OTA`s will even install with a unlocked bootloader.
Click to expand...
Click to collapse
Thanks for the info and I really appreciate your input. What are your feelings on using Wug's toolkit to unroot and go back stock, take the update, then re-root and flash the custom recovery. I have never used a toolkit before, but that seems to be the popular method. Like I said at the beginning I am new to all of this, the last device I rooted and really messed around with was the droid x so bear with me as I am learning. I am currently reading about Wug's and will look at the method you just spoke of, but any info would be great.
evolefty said:
Thanks for the info and I really appreciate your input. What are your feelings on using Wug's toolkit to unroot and go back stock, take the update, then re-root and flash the custom recovery. I have never used a toolkit before, but that seems to be the popular method. Like I said at the beginning I am new to all of this, the last device I rooted and really messed around with was the droid x so bear with me as I am learning. I am currently reading about Wug's and will look at the method you just spoke of, but any info would be great.
Click to expand...
Click to collapse
I don`t like Toolkits tbh because like with all automated applications the unexperienced user has no idea whats going/has zero control over whats happening and if something goes wrong they can`t fix the issue. Imo its best to learn adb/fastboot/sideload.
gee2012 said:
I don`t like Toolkits tbh because like with all automated applications the unexperienced user has no idea whats going/has zero control over whats happening and if something goes wrong they can`t fix the issue. Imo its best to learn adb/fastboot/sideload.
Click to expand...
Click to collapse
Gotcha, and completely understand. I will do some reading on that method and again thanks for your help.
evolefty said:
Gotcha, and completely understand. I will do some reading on that method and again thanks for your help.
Click to expand...
Click to collapse
Read the sticky threads http://forum.xda-developers.com/nexus-6/general/nexus-6-sticky-roll-thread-t3061066, this is a good start. Adb and fastboot isn`t that hard but its very safe and effective
gee2012 said:
Read the sticky threads http://forum.xda-developers.com/nexus-6/general/nexus-6-sticky-roll-thread-t3061066, this is a good start. Adb and fastboot isn`t that hard but its very safe and effective
Click to expand...
Click to collapse
Will do, and that is the method I used to root for the simple fact to learn.
evolefty said:
Will do, and that is the method I used to root for the simple fact to learn.
Click to expand...
Click to collapse
Good luck
gee2012 said:
- OTA`s will not install if the sytem, boot and recovery are modified in any way.
- Reflashing the stock image will NOT lock the bootloader
- And yes you can flash a custom recovery and reroot after updating.
Or flash the latest stock rom with TWRP from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
Click to expand...
Click to collapse
In that link you sent I am not seeing the VZW version of 5.1.1. Can we use the "International" version?
Thank you.
needoZ said:
In that link you sent I am not seeing the VZW version of 5.1.1. Can we use the "International" version?
Thank you.
Click to expand...
Click to collapse
Yes, use the LMY47Z build.
DogzOfWar said:
So the question that started this thread: My system is technically modified. Can I unroot and replace recovery, and now be in a sufficiently "unmodified" state? OR, do I have to lock the bootloader in order for the OTA to continue?
I think the OP and myself are trying to do the same thing: We're lazy, we don't want to wipe, we don't want to lose data, we just want the OTA without having to reflash the whole thing. Does anyone know if this is possible?
Click to expand...
Click to collapse
Bootloader does not have to be locked to take an OTA. You can not be rooted or modified in any way however.
gee2012 said:
I don`t like Toolkits tbh because like with all automated applications the unexperienced user has no idea whats going/has zero control over whats happening and if something goes wrong they can`t fix the issue. Imo its best to learn adb/fastboot/sideload.
Click to expand...
Click to collapse
While I agree, once you have "paid your dues" and flashed without automation then the NRT is a great tool, so long as you have an understanding of what it is doing.

Brick every custom rom flash

I have followed the rooting, backup (drm keys), flash new firmware etc etc procedure. However every time i flash a custom rom and reboot it goes into brick. I mean no bootloop just flashing red led when on charger, i cant even get to recovery to restore.
then i have to do
Flash .105 kitkat stock firmware>giefroot>dualrecovery install.bat>flash new pre rooted firmware>try flashing custom rom again>BRICK>(return to start)^
i have unlocked bootloader, everything done, even when i try and restore drm keys i get bricked.
i have currently given up on custom roms and im living with crap camera, no custom rom.....nothing.
please help, send food n water
Help please
:crying:
Did you find a solution for this.this? I have the same problem. I don't know what to do.
thefanofmusic said:
Did you find a solution for this.this? I have the same problem. I don't know what to do.
Click to expand...
Click to collapse
This was a year old post, but I did manage to fix it, flash stock pre rooted firmwares, then u have lollipop rooted. It was my bootloader was locked or something
xpzx said:
This was a year old post, but I did manage to fix it, flash stock pre rooted firmwares, then u have lollipop rooted. It was my bootloader was locked or something
Click to expand...
Click to collapse
Oh OK. Thanks for replying . Damn but my bootloader is unlocked. No idea what I should do.

New user d415

Hi guys I got this old lg d415 from my cousin and Wana install some roms on it since I'm a noob on this device I need some help regarding what to do unlock bootloader or what .... I see that d415 has a unlocked bootloader or no ?
Its bootloader is already unlocked just root and flash twrp. kingroot to root and flashify to flash the recovery seem easiest. *Just make sure to update to LP beforehand. here's a link for recovery. You may be able to get a more updated version of the recovery off the twrp site. Also I suggest using the most recent lineage build. lineage
teknoweanie said:
Its bootloader is already unlocked just root and flash twrp. kingroot to root and flashify to flash the recovery seem easiest. *Just make sure to update to LP beforehand. here's a link for recovery. You may be able to get a more updated version of the recovery off the twrp site. Also I suggest using the most recent lineage build. lineage
Click to expand...
Click to collapse
Ypu wrong you have to unlock before flashing unless you are planning on bricking your device. You first have to root it and then flash laf with zeros u lock bootlosder, flash recocery , thenflash rom
Please don't tell people stuff you don't know about. The T-Mobile variant comes with its bootloader already unlocked. Also there is no laf to mess with.
teknoweanie said:
Please don't tell people stuff you don't know about. The T-Mobile variant comes with its bootloader already unlocked. Also there is no laf to mess with.
Click to expand...
Click to collapse
Really? I have tmobile variant and i had to unlock bootloader. Look at this https://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-t-mobile-l90-t2836457
Wow I guess you did a bunch of useless stuff that does not matter. About as useful as me putting in does not matter instead of doesn't. Read what googlephone says at the end of the thread at post #204..............yeah..
teknoweanie said:
Wow I guess you did a bunch of useless stuff that does not matter. About as useful as me putting in does not matter instead of doesn't. Read what googlephone says at the end of the thread at post #204..............yeah..
Click to expand...
Click to collapse
Ok, didnt know

Trying to get back to stock ROM

Hey guys,
Today I messed up with TWRP and accidentally deleted the data partition.
I had used janjan's solution like a year ago to get magisk (I'm assuming my DRM keys are gone), and my BL is also unlocked.
Sadly, my phone booted to the new setup wizard, and now magisk is not working.
I'm desperately trying to get back to stock ROM in order to get root again and have a custom kernel or some other custom ROM instead.
I'm not sure if that is possible any longer, I tried using newflasher (v19) to flash into stock but sadly it didn't recognize the phone.
I'm kinda lost, and I would love if someone would help and point me in some direction in order to get things working again.
Current situation is I'm on firmware 47.1.A.12.179, and cannot simply update it through fota (it won't install), magisk isn't working, but the phone does connect to google play store and functions 'normally' (without root though).
If anyone has any idea of what I could do next, that would be supreme.
Thanks for your time!
Use EMMA.
Thanks! I'll update with details
Edit: Amazing mate! This worked! My camera is back!
So many many many thanks
Just came here to say thanks. Spend few hours trying to install drivers when I actually mistook flash mode with fastboot mode lol
Hi, I have an xz1 compact with bootloader unlocked and root with custom rom installed (AEX rom). can i use emma to restore android 9 stock?
Thank you
AciDBorN said:
Hi, I have an xz1 compact with bootloader unlocked and root with custom rom installed (AEX rom). can i use emma to restore android 9 stock?
Thank you
Click to expand...
Click to collapse
Can someone help me? Thank you
AciDBorN said:
can i use emma to restore android 9 stock?
Click to expand...
Click to collapse
Yes.
SXUsr said:
Yes.
Click to expand...
Click to collapse
Thank you
Hello
Tried to restore to stock ROM from EMMA, worked like a charm... But I can't ReLock back the bootloader.
Any advice?
It's not possible to relock the XZ1C's bootloader.

Categories

Resources