Database Develop

[Q] Installing custom rom on unlocked Z failing

Unlocked rooted xperiaz..
installed this: http://forum.xda-developers.com/showthread.php?t=2190936
(tried also with cwm)
After entering recovery cwm or twrp i can choose ROM: (tried paranoid android)
I'm on the latest stock firmware btw... 244..
After flashing i only get a red light, and nothing else works.. can get to flas mode and flash stock ROM, but everytime i try a custom rom it fails..
Where am i going wrong? I Know i **** up somewhere, but can't see where...

Try flashing the Kernel from Paranoid Android by itself. Inside the rom's zip there ahould be an image called boot.img. Flash via fasboot on Flashtool.
Now enter recovery and follow the normal procedure.

First of all that link to TWRP is for locked bootloaders. You need to have an unlocked bootloader to install a custom rom
To get recovery just flash the boot.img which is inside the rom .zip folder
Code:
fastboot flash boot boot.img
Then enter recovery and flash the zip then gapps.

[Q] What recovery do I need to flash 4.4 ROMs?

I know last time I tried flashing a 4.4 ROM I would get some error because of some weird compatibility thing with CWM or TWRP or something like that. I don't remember which recovery it was that I needed that would let me flash, I'm trying to flash beanstalk

You should flash the boot.img from the rom zip using fastboot, then boot into recovery and flash the rom.
I would advise doing a lot more research of how to flash custom roms and how to fix potential problems before continuing on any further as it will save you time in the future in case of any problems.
Sent from my C6603 using Tapatalk

extract from the zip file boot.img
flash it through fastboot , reboot your phone and go to recovery and then flash the rom

[Q] Trouble flashing ResRemix!

Hi, its 11:30 and i give up!
ok i first installed cwm using the kernel, and falshed SuperSU and than wiped data and cache and dalvik and flashed resRemix so i can reboot again and flash cwm, the problem is when i flash reRemix it goes to rom but also replaces the recovery with cyanogenmod one which doens't have any flashh zip and if i re flash the kernel with fastboot it will get stuck in sony logo reboot !
if i install both without booting to rom first it will reboot in middle of setup(first time setup name etc always at activating cellular)
this time i don't know what happened but it also freezed and rebooted on the bare-rom, but it worked before that (i assume i was tired and did something wrong)
what should i do?!

kamranhaghighi said:
Hi, its 11:30 and i give up!
ok i first installed cwm using the kernel, and falshed SuperSU and than wiped data and cache and dalvik and flashed resRemix so i can reboot again and flash cwm, the problem is when i flash reRemix it goes to rom but also replaces the recovery with cyanogenmod one which doens't have any flashh zip and if i re flash the kernel with fastboot it will get stuck in sony logo reboot !
if i install both without booting to rom first it will reboot in middle of setup(first time setup name etc always at activating cellular)
this time i don't know what happened but it also freezed and rebooted on the bare-rom, but it worked before that (i assume i was tired and did something wrong)
what should i do?!
Click to expand...
Click to collapse
Flash other kernel with flashtools, entry in recovery wipe cache davilk cache and data/factory reset, flash the rom with recovery and the boot.img with flashtools.
Sorry for my bad english

I have linux, ia flashtool the only way?
My problem is flashing gapps, if i want to flash it i need cwm and cwm gets replaced when i flash the rom, and xda tutorial for flashing cwm (kernel.elf) makes mt device get stuck in sony logo and bootloop!

Guizão BR said:
Flash other kernel with flashtools, entry in recovery wipe cache davilk cache and data/factory reset, flash the rom with recovery and the boot.img with flashtools.
Sorry for my bad english
Click to expand...
Click to collapse
wait, what do is boot.img?! why do i have to flash it?! i have no idea what it is! this was much easier on my nexus

kamranhaghighi said:
wait, what do is boot.img?! why do i have to flash it?! i have no idea what it is! this was much easier on my nexus
Click to expand...
Click to collapse
Boot.img is the kernel, you have to flashing him because the latest version of this rom is for unlocked bootloader

Guizão BR said:
Boot.img is the kernel, you have to flashing him because the latest version of this rom is for unlocked bootloader
Click to expand...
Click to collapse
where can i get it? and I will get CWM with it? (for flashing gapps)

kamranhaghighi said:
where can i get it? and I will get CWM with it? (for flashing gapps)
Click to expand...
Click to collapse
Is inside the rom file, you have to unpack and flashing after using flashtools, you know how to use flashtools?

Guizão BR said:
Is inside the rom file, you have to unpack and flashing after using flashtools, you know how to use flashtools?
Click to expand...
Click to collapse
Im not sure, i know how to use fastboot btw! (btw i got ubuntu, if its a software or something i need it to have a linux version)

Guizão BR said:
Is inside the rom file, you have to unpack and flashing after using flashtools, you know how to use flashtools?
Click to expand...
Click to collapse
i will just google flash tools and do what you said when i get the chance, will post abck if i get into trouble

kamranhaghighi said:
i will just google flash tools and do what you said when i get the chance, will post abck if i get into trouble
Click to expand...
Click to collapse
You can flash kernel with normal fastboot too of course! if the kernel name and formal will be boot.img just type command in fastboot
fastboot flash boot boot.img

Spasik said:
You can flash kernel with normal fastboot too of course! if the kernel name and formal will be boot.img just type command in fastboot
fastboot flash boot boot.img
Click to expand...
Click to collapse
thanks, but i don't get it, boot.img is the kernel isn't it going to be flashed with the rom?! and how can i flash the GAPPS after rebooting, because it quires me to do it after doing the first boot!

kamranhaghighi said:
thanks, but i don't get it, boot.img is the kernel isn't it going to be flashed with the rom?! and how can i flash the GAPPS after rebooting, because it quires me to do it after doing the first boot!
Click to expand...
Click to collapse
Ok i will try to explain the metod i use
First of all i have functioning phone on any rom
than i flash doomkernel or williams kernel
in these two kernels there are integrated all 3 recoverys cwm twrp philz
i boot the phone to any recovery i like (i preffer cwm)
in recovery i wipe data, cache, system, and internal memory because i have zips on sd card
flash the rom
if in the tutorial of rom is to flash gapps after first boot i just boot the phone to new rom
then i power off the device and flash doomkernel/williamskernel
after that ,i flash from recovery of these kernels the gapps
after flash of gapps is complete i power off the device and flash original kernel from rom i have
viola magic is complete

Spasik said:
Ok i will try to explain the metod i use
First of all i have functioning phone on any rom
than i flash doomkernel or williams kernel
in these two kernels there are integrated all 3 recoverys cwm twrp philz
i boot the phone to any recovery i like (i preffer cwm)
in recovery i wipe data, cache, system, and internal memory because i have zips on sd card
flash the rom
if in the tutorial of rom is to flash gapps after first boot i just boot the phone to new rom
then i power off the device and flash doomkernel/williamskernel
after that ,i flash from recovery of these kernels the gapps
after flash of gapps is complete i power off the device and flash original kernel from rom i have
viola magic is complete
Click to expand...
Click to collapse
thanks will try that when i see him again

Manually flashing 6.0, will this approach still work?

To start: 5.1.1 (LMY48M), rooted, with TWRP for recovery
For every 5.x update so far, this has been my procedure using fastboot:
Flash boot.img
Flash radio.img
Flash system.img
After successfully updated, I'd use WugFresh's Nexus toolkit to root and flash TWRP.
I'm a fan of not needing to flash userdata.img, as I don't think that should be necessary given that the OTA wouldn't wipe installed apps and such.
I've read other threads about using fastboot to upgrade and am concerned about the boot warnings, which seem to require a custom kernel to circumvent. My question is: will the above approach still work? Do I need to flash any other files? If I need to flash a custom kernel, where do I get it, how do I flash it (is it just a custom boot.img?), and at which point in the flash sequence should I apply it?
Secondly, has anyone tried gaining root through the Nexus toolkit once upgraded to 6.0?
I'm looking for recommendations so I don't spend hours trying to unbrick my device. Thanks!

You'll also want to flash the 6.0 bootloader and why are you using the toolkit to flash twrp when you can flash it in fastboot along with the rest of the files?

Ah OK, I'll flash the bootloader image as well. Anything else to be concerned with? The toolkit has a feature to root + flash twrp as a feature, so I just use that.

Do the bootloader first, then reboot the bootloader before you flash anything else. There are instructions floating around here some where or you can google nexus 6 flash factory images. You don't have to flash user data as this will format all you data/ apps.

Just download the latest SuperSu zip (2.50) and put it on your SDcard. If you flash as you suggested and then boot directly into recovery, you will still have TWRP. If you don't flash the stock recovery.img to replace TWRP, it will replace on first boot anyway, unless you root imeediately, but you are probably booting to use the toolkit, which replaces recovery only to have to use the toolkit to flash recovery anwyay.
So do your flashes, boot straight into recovery, flash the supersu zip on your sdcard. Done.

[Q] TWRP lost after flashing 4.1.3

I've recently flashed my OP3T with stock ROM 4.1.3, & do the clean flash with TWRP. After finished, when I went back to the recovery mode, TWRP is lost, and the recovery goes back to stock recovery. Every time I start up/reboot my phone, I always get the DM-Verify warning.
Anyone can point me why after flashed the 4.1.3, my recovery goes back to stock recovery?
Also, which method should I use to change the stock recovery to TWRP & bypass the DM-Verify warning?
Thanks in advance

As for the TWRP, after flashing with TWRP you have to boot into Recovery and root (SuperSu/Magisk).
Only then TWRW sticks.
As for the DM-Verify, there is a thread here how to do.
Honestly, the DM-Verify doesn't bother me, so I don't bother to remove it
Cheers
Tom

tom1807 said:
As for the TWRP, after flashing with TWRP you have to boot into Recovery and root (SuperSu/Magisk).
Only then TWRW sticks.
As for the DM-Verify, there is a thread here how to do.
Honestly, the DM-Verify doesn't bother me, so I don't bother to remove it
Cheers
Tom
Click to expand...
Click to collapse
Thanks for the answer, . Actually when I flashed with 4.1.3, it came from the Experience ROM, ver. 17. After flashed with the stock 4.1.3, when I went back to the recovery, the TWRP is gone, replaced by the stock recovery. I thought that when we flash via custom recovery such as TWRP, it will bypass to flash recovery, CMIIW.

When you flash stock ROM, the image will contain the stock recovery, so you will need to reflash twrp from fast boot
Sent from my ONEPLUS A3003 using Tapatalk

Booting up default ROM, it will make sure recovery is original and if not it will restore it just like it did for you. TWRP rooting will remove the original recovery making it impossible to break TWRP for you.

ben_pyett said:
When you flash stock ROM, the image will contain the stock recovery, so you will need to reflash twrp from fast boot
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
You don't have to. Just flash magisk or SuperSU right after the ROM, you will get both root and twrp