Dear all,
I have tried to flash the pacman rom on my rooted Z, but i had over looked the part on wiping out the data and had restarted my phone. Right now my Z has be stuck on the Pac is loading for a good half of the day. Any assistance would be greatly appreciated. Thank you in advance.
Boot into recovery then wipe and reinstall or restore your backup
Michealtbh said:
Boot into recovery then wipe and reinstall or restore your backup
Click to expand...
Click to collapse
I managed to reboot it, thank you so much!!
remember, flashing CM roms require you to fastboot the boot.img
spazzy1912 said:
remember, flashing CM roms require you to fastboot the boot.img
Click to expand...
Click to collapse
No it doesn't, the boot.img is flashed with the zip in recovery. You only need to use fastboot if you don't already have a custom recovery
Michealtbh said:
No it doesn't, the boot.img is flashed with the zip in recovery. You only need to use fastboot if you don't already have a custom recovery
Click to expand...
Click to collapse
Since when?
From me to you.
XperienceD said:
Since when?
From me to you.
Click to expand...
Click to collapse
That's been the case since I got my XZ ~4 weeks ago
Michealtbh said:
That's been the case since I got my XZ ~4 weeks ago
Click to expand...
Click to collapse
If you have a stock, but bootloader unlocked Phone, you need to flash the kernel first for CWM, so if I flash another ROM that needs a different kernel, just flashing the zip now also flashes the kernel?, which it's never done on Xperia Phones before.
From me to you.
XperienceD said:
If you have a stock, but bootloader unlocked Phone, you need to flash the kernel first for CWM, so if I flash another ROM that needs a different kernel, just flashing the zip now also flashes the kernel?, which it's never done on Xperia Phones before.
From me to you.
Click to expand...
Click to collapse
Correct. Boot partition can be flashed through recovery with the XZ.
Related
So like a tard, I went and flashed a ROM for the One wanting a menu button. Unfortunately, this ROM was not specifically for a Sprint HTC One, but for the other One variants. Now my wifi and data are broken, and my phone constantly restarts itself, independent of the ROM I'm using ( I've flashed at least 3 ROMs to confirm this). Is there anything I can do to specifically re-flash the radios/prevent the constant restarting?
Boomchaos said:
So like a tard, I went and flashed a ROM for the One wanting a menu button. Unfortunately, this ROM was not specifically for a Sprint HTC One, but for the other One variants. Now my wifi and data are broken, and my phone constantly restarts itself, independent of the ROM I'm using ( I've flashed at least 3 ROMs to confirm this). Is there anything I can do to specifically re-flash the radios/prevent the constant restarting?
Click to expand...
Click to collapse
you have to flash a boot.img too- you shouldn't flash roms not specific to your phone, you'll brick it
Please read my post here before you brick your phone.
http://forum.xda-developers.com/showthread.php?p=40678263
Aldo101t said:
you have to flash a boot.img too- you shouldn't flash roms not specific to your phone, you'll brick it
Click to expand...
Click to collapse
I flashed viperBoy's stock Sprint ROM and that already had a boot.img in it. Are you saying I should flash that separately?
Boomchaos said:
I flashed viperBoy's stock Sprint ROM and that already had a boot.img in it. Are you saying I should flash that separately?
Click to expand...
Click to collapse
yes, if you are s-on not s-off you do, with s-on even if the rom has a boot image, it will not flash the boot.img you must pull the image boot from the rom zip and flash it via adb sdk tools in fastboot
Aldo101t said:
yes, if you are s-on not s-off you do, with s-on even if the rom has a boot image, it will not flash the boot.img you must pull the image boot from the rom zip and flash it via adb sdk tools in fastboot
Click to expand...
Click to collapse
Is there a particular order in flash the boot.img vs. the main rom? And should I have taken out the boot.img from the ROM before flashing the ROM? As in should the ROM not have the boot.img inside of it when being flashed?
Boomchaos said:
Is there a particular order in flash the boot.img vs. the main rom? And should I have taken out the boot.img from the ROM before flashing the ROM? As in should the ROM not have the boot.img inside of it when being flashed?
Click to expand...
Click to collapse
ROM first, then boot.img.
And no, flash as is or else you'll get errors.
CNexus said:
ROM first, then boot.img.
And no, flash as is or else you'll get errors.
Click to expand...
Click to collapse
Still restarting, and freezing up. Wifi works now though...baby steps haha.
Hi guys!
I've flashed faux kernel but I'd like to go back to stock..
Where I can find the stock kernel?
Thanks a lot!
daede86 said:
Hi guys!
I've flashed faux kernel but I'd like to go back to stock..
Where I can find the stock kernel?
Thanks a lot!
Click to expand...
Click to collapse
It's the boot.img file in whatever SBF you are running. You MUST use the boot.img from the exact same SBF file (for YOUR version/variant) that you are currently on.
Flash it using fastboot: fastboot flash boot boot.img
samwathegreat said:
It's the boot.img file in whatever SBF you are running. You MUST use the boot.img from the exact same SBF file (for YOUR version/variant) that you are currently on.
Flash it using fastboot: fastboot flash boot boot.img
Click to expand...
Click to collapse
Thanks man
Can't I use flashify to flash the boot.img? Right now I don't have a pc with me..
daede86 said:
Thanks man
Can't I use flashify to flash the boot.img? Right now I don't have a pc with me..
Click to expand...
Click to collapse
Sure. The main function from flashify is to flash IMG s.
nexuspur said:
Sure. The main function from flashify is to flash IMG s.
Click to expand...
Click to collapse
Downloading right now
Thabks again
If I'm on krypton 4.4.4 ROM on a xt1053 T-Mobile variant can I use the 4.4.3 T-Mobile sbf boot.IMG or the Verizon 4.4.4 sbf boot.IMG?
dobbs3x said:
If I'm on krypton 4.4.4 ROM on a xt1053 T-Mobile variant can I use the 4.4.3 T-Mobile sbf boot.IMG or the Verizon 4.4.4 sbf boot.IMG?
Click to expand...
Click to collapse
Maybe....but why would you do that?
One way to find out -- try it. If it doesn't work or causes issues, flash the boot.img from krypton back on.
i think i made a mistake...
i thought i had the 4.4.4 stock firmware on my sd, so i've flashed the boot.img.. but after that, my moto stopped working properly! it completly changed the color scheme, the boot anymation is broken and it keep rebooting after few seconds/minutes.
So i realized i've flashed the 4.4.2 boot.img!!
i temporarly solved this problem flashing a custom rom (using slimkat right now) but i really want to go back to stock!
How should i proceed?!
i have a german moto x xt1052
thanks a lot!!!
daede86 said:
i think i made a mistake...
i thought i had the 4.4.4 stock firmware on my sd, so i've flashed the boot.img.. but after that, my moto stopped working properly! it completly changed the color scheme, the boot anymation is broken and it keep rebooting after few seconds/minutes.
So i realized i've flashed the 4.4.2 boot.img!!
i temporarly solved this problem flashing a custom rom (using slimkat right now) but i really want to go back to stock!
How should i proceed?!
i have a german moto x xt1052
thanks a lot!!!
Click to expand...
Click to collapse
You shouldn't have flashed that custom rom. Now you have to wait for the full sbf to be leaked which could take weeks or months. By flashing the custom rom, you overwrote /system.
If you didn't do that, you could have simply flashed the boot.img from the 4.4.4 OTA file.
Your only other option is to find someone with the same variant as you have on 4.4.4 and ask them to do a twrp backup of just system and boot. Then flash that backup.
Remember: you can't downgrade without great risk of bricking - either immediately or in the future.
Thanks a lot..i hope to find someone with 4.4.4 german moto x!
samwathegreat said:
You shouldn't have flashed that custom rom. Now you have to wait for the full sbf to be leaked which could take weeks or months. By flashing the custom rom, you overwrote /system.
If you didn't do that, you could have simply flashed the boot.img from the 4.4.4 OTA file.
Your only other option is to find someone with the same variant as you have on 4.4.4 and ask them to do a twrp backup of just system and boot. Then flash that backup.
Remember: you can't downgrade without great risk of bricking - either immediately or in the future.
Click to expand...
Click to collapse
i've found an user so kind to share with me his system and boot backup!!
so how should i proceed?! this time i want to be sure
to use my moto in the past days, i flashed kripton rom! so should i just restore from recovery the backup (after a factory reset)?
thanks a lot!!
daede86 said:
i've found an user so kind to share with me his system and boot backup!!
so how should i proceed?! this time i want to be sure
to use my moto in the past days, i flashed kripton rom! so should i just restore from recovery the backup (after a factory reset)?
thanks a lot!!
Click to expand...
Click to collapse
You should be able to boot to twrp, and flash the backup using restore button. Make sure you erase userdata afterwards.
Before you start, you need to copy the backup to your internal storage in the twrp backup folder, of course.
Don't erase userdata until after you have restored the backup otherwise you will erase the backup! Everything on the internal memory will be erased, so save anything important such as pictures to your PC first.
could you share boot.img with me please ?
My phone wont boot anymore
XT1052 on 4.4.2
I have a Xperia Z, and installed CM 10 on it, using the following method
Unlocked the bootloader from Sony's site
Downloaded the SDK
Flashboot flash boot boot.IMG
And installed cm.zip from the sdcard.
It worked, in fact, I am typing this from my newly ROM'ed xperia.
So, the question is , if I want to install another ROM now, say CM11 or even a complete different one from xda , what is the process?
Do I just copy the new zip, boot into recovery, and wipe wipe install?
Or do I need to reflash the new boot.IMG from the new ROM every time?
Thanks
endlesslyonline said:
I have a Xperia Z, and installed CM 10 on it, using the following method
Unlocked the bootloader from Sony's site
Downloaded the SDK
Flashboot flash boot boot.IMG
And installed cm.zip from the sdcard.
It worked, in fact, I am typing this from my newly ROM'ed xperia.
So, the question is , if I want to install another ROM now, say CM11 or even a complete different one from xda , what is the process?
Do I just copy the new zip, boot into recovery, and wipe wipe install?
Or do I need to reflash the new boot.IMG from the new ROM every time?
Thanks
Click to expand...
Click to collapse
For flashing CM11
Copy the rom to device
Reboot to recovery
Clear dalvik cache
Flash the rom.
For other rom
Copy rom to device
Copy Gapps to device
Reboot to recovery
Format system
Format cache
Format dalvik cache
Format data(not internal sd)
Flash the rom
Flash Gapps
OK, thanks
So I was correct in thinking the boot.IMG (which is the recovery, right?) Won't have to be flashed again.
endlesslyonline said:
OK, thanks
So I was correct in thinking the boot.IMG (which is the recovery, right?) Won't have to be flashed again.
Click to expand...
Click to collapse
You dont have to flash recovery again.
Hitting thanks would have been easier than writing it!
endlesslyonline said:
OK, thanks
So I was correct in thinking the boot.IMG (which is the recovery, right?) Won't have to be flashed again.
Click to expand...
Click to collapse
well not exactly, the boot.img is the kernel
Pablosch23 said:
well not exactly, the boot.img is the kernel
Click to expand...
Click to collapse
That's my understanding as well. So why is flashing boot.img necessary for installing custom recovery?
Pablosch23 said:
well not exactly, the boot.img is the kernel
Click to expand...
Click to collapse
Ah OK. But am I correct in saying that the (for example) clockworkMOD, or any other custom recovery resides in the boot.IMG
In lamens terms, can we say that the boot.IMG is almost like the bios on a PC?
Sorry for the dumb questions, I just wanna learn some mpre
endlesslyonline said:
Ah OK. But am I correct in saying that the (for example) clockworkMOD, or any other custom recovery resides in the boot.IMG
In lamens terms, can we say that the boot.IMG is almost like the bios on a PC?
Sorry for the dumb questions, I just wanna learn some mpre
Click to expand...
Click to collapse
I think you are right, I'm a also a newbie though..the boot.img contains the kernel (and the ramdisk) where the recovery resides.
Khaiyan said:
That's my understanding as well. So why is flashing boot.img necessary for installing custom recovery?
Click to expand...
Click to collapse
The boot.IMG is the kernel itself
If you flashed wrong one on wrong device so say goodbye to the device
Tapatalk'ed from my Xperia™ Z (C6602) running Dirty Unicorns ROM!
endlesslyonline said:
Ah OK. But am I correct in saying that the (for example) clockworkMOD, or any other custom recovery resides in the boot.IMG
In lamens terms, can we say that the boot.IMG is almost like the bios on a PC?
Sorry for the dumb questions, I just wanna learn some mpre
Click to expand...
Click to collapse
Most custom roms include recovery so I dont think you will have to flash boot.img separately again and again
Hey,
I dont know how different things are now, i installed a RUU with lollipop and i've been trying to flash TWRP but after i try to get into recovery and i got stuck at the logo with "entering into recovery...", adb detects device and nothing happens, tried to delete cache still didnt work. I bet i'm missing something as stupid as a simple boot...
Terramoto said:
Hey,
I dont know how different things are now, i installed a RUU with lollipop and i've been trying to flash TWRP but after i try to get into recovery and i got stuck at the logo with "entering into recovery...", adb detects device and nothing happens, tried to delete cache still didnt work. I bet i'm missing something as stupid as a simple boot...
Click to expand...
Click to collapse
you flash the recovery for the m7wls.
Aldo101t said:
you flash the recovery for the m7wls.
Click to expand...
Click to collapse
what kind of statement was that? Or was it a question? Yep i flashed m7wls isn't that sprint version of TWRP?
EDIT: I think i know what you mean, TWRP is not working well with lollipop, is that it?
Terramoto said:
what kind of statement was that? Or was it a question? Yep i flashed m7wls isn't that sprint version of TWRP?
EDIT: I think i know what you mean, TWRP is not working well with lollipop, is that it?
Click to expand...
Click to collapse
no just checking you installed the correct recovery, for lollipop you should have the latest recovery, that's all
I can't either get root or flash a ROM without access to recovery?
what else can i do?
Terramoto said:
what else can i do?
Click to expand...
Click to collapse
Reflash latest firmware from here http://forum.xda-developers.com/showthread.php?t=2795856 (i recommend Modified Firmware....removed hboot, recovery & boot (fastboot flashable))
Then flash latest recovery twrp-2.8.6.0-m7wls..
crazykas said:
Reflash latest firmware from here http://forum.xda-developers.com/showthread.php?t=2795856 (i recommend Modified Firmware....removed hboot, recovery & boot (fastboot flashable))
Then flash latest recovery twrp-2.8.6.0-m7wls..
Click to expand...
Click to collapse
Didnt work, it tries to enter recovery but its like there's no recovery. The phone's not letting me flash the recovery only the stock one
Terramoto said:
Didnt work, it tries to enter recovery but its like there's no recovery. The phone's not letting me flash the recovery only the stock one
Click to expand...
Click to collapse
Did you flash the firmware first?
crazykas said:
Did you flash the firmware first?
Click to expand...
Click to collapse
yeah, i flashed the modified first then tried to flash recovery, it just wont go into recovery. Is there a way to downgrade back to kitkat? Everything was working good with kk, i had to replace the display, camera and battery so i flashed lollipop RUU thinking there wouldnt be any difference... Now i can't even get root
Terramoto said:
yeah, i flashed the modified first then tried to flash recovery, it just wont go into recovery. Is there a way to downgrade back to kitkat? Everything was working good with kk, i had to replace the display, camera and battery so i flashed lollipop RUU thinking there wouldnt be any difference... Now i can't even get root
Click to expand...
Click to collapse
Was there any error when you flashing recovery?It just doesn't boot to recovery?Then you should flash FULL RUU..It should be the fix
crazykas said:
Was there any error when you flashing recovery?It just doesn't boot to recovery?Then you should flash FULL RUU..It should be the fix
Click to expand...
Click to collapse
no error, everything went smooth its just the boot part, funny thing is im able to flash and boot twrp 2.5.0.0 but im not able to use it because it doesnt respond to touch. I'm currently with stock recovery but i'd like to root and remove crappy apps from my phone :\
Terramoto said:
no error, everything went smooth its just the boot part, funny thing is im able to flash and boot twrp 2.5.0.0 but im not able to use it because it doesnt respond to touch. I'm currently with stock recovery but i'd like to root and remove crappy apps from my phone :\
Click to expand...
Click to collapse
i faced that prob too,but i just had to update to latest firmware & recovery.Flash twrp 2.6.0 & try.
crazykas said:
i faced that prob too,but i just had to update to latest firmware & recovery.Flash twrp 2.6.0 & try.
Click to expand...
Click to collapse
I think i did that, isnt that what RUU's suppose to do?
Anyway, here's the log and last_kmsg if anyone knows how to trace this
log:
http://www.pastebin.ca/2978960
Last_kmsg:
http://pastebin.ca/2978961
@mdmower
I was told that since i replaced parts i might have replaced a part thats not the same as the original one and that i would need to make a custom recovery. I've already download the kmsg report (http://pastebin.com/USayUFqx) i just need some eyes that understand whats happening.
I've been trying to find how to install a kernel for a few days but i couldn't find any good and updated source. I'm thinking of installing latest helium to my device. Can anyone help me?
ExclusiveBFS said:
I've been trying to find how to install a kernel for a few days but i couldn't find any good and updated source. I'm thinking of installing latest helium to my device. Can anyone help me?
Click to expand...
Click to collapse
Through any recovery is the most easy way, but you have to unlock bootloader first.
Do you even know what it does?
Bigrrd225 said:
Do you even know what it does?
Click to expand...
Click to collapse
Yeah, I do. I just didn't want to flash it and take risk. I must have learned details
HUEguy said:
Through any recovery is the most easy way, but you have to unlock bootloader first.
Click to expand...
Click to collapse
My bootloader is unlocked. And I have the twrp. Thanks!
ExclusiveBFS said:
Yeah, I do. I just didn't want to flash it and take risk. I must have learned details
My bootloader is unlocked. And I have the twrp. Thanks!
Click to expand...
Click to collapse
Then just flash the .zip file via TWRP. Simple. Of course you'll need a ROM compatible with helium otherwise you'll be stuck in a bootloop.
Also goes without saying that you should take a nandroid backup via TWRP first in case something goes wrong.
Edit : When you say you have TWRP, is it part of your current kernel or you flashed it in your FOTA kernel partition via Rashr or something? If its the former then flashing Helium would overwrite TWRP and you could wind up without a working recovery cause I don't think Helium comes with any. Might want to flash TWRP in your FOTA partition with Rashr before you proceed.
XenolithicYardZone said:
Then just flash the .zip file via TWRP. Simple. Of course you'll need a ROM compatible with helium otherwise you'll be stuck in a bootloop.
Also goes without saying that you should take a nandroid backup via TWRP first in case something goes wrong.
Edit : When you say you have TWRP, is it part of your current kernel or you flashed it in your FOTA kernel partition via Rashr or something? If its the former then flashing Helium would overwrite TWRP and you could wind up without a working recovery cause I don't think Helium comes with any. Might want to flash TWRP in your FOTA partition with Rashr before you proceed.
Click to expand...
Click to collapse
I was on latest candy5, i flashed adrian dc's twrp from recovery but now I'm installing the stock ftf, I will try carbon lp rom. When the installation completed, I will flash adrian dc's twrp again. Then I will flash the helium kernel with twrp. Is there a problem with that? Should I install twrp with rashr?
ExclusiveBFS said:
I was on latest candy5, i flashed adrian dc's twrp from recovery but now I'm installing the stock ftf, I will try carbon lp rom. When the installation completed, I will flash adrian dc's twrp again. Then I will flash the helium kernel with twrp. Is there a problem with that? Should I install twrp with rashr?
Click to expand...
Click to collapse
If you're gonna flash stock firmware via Flashtool then your FOTA recovery will be wiped out. How are you gonna flash TWRP & Carbon LP rom when you don't have a recovery in the first place?
http://forum.xda-developers.com/xperia-sp/development/recovery-twrp-3-0-0-touch-recovery-t3309938
The recovery from the above thread is flashable but you still need an working recovery on your device to be able to do it right? What you can do it use the fastboot bootable image and install whatever you want if you're gonna go stock.
Actually you only need Rashr if you wanna stay stock but still want a working recovery.
XenolithicYardZone said:
If you're gonna flash stock firmware via Flashtool then your FOTA recovery will be wiped out. How are you gonna flash TWRP & Carbon LP rom when you don't have a recovery in the first place?
http://forum.xda-developers.com/xperia-sp/development/recovery-twrp-3-0-0-touch-recovery-t3309938
The recovery from the above thread is flashable but you still need an working recovery on your device to be able to do it right? What you can do it use the fastboot bootable image and install whatever you want if you're gonna go stock.
Actually you only need Rashr if you wanna stay stock but still want a working recovery.
Click to expand...
Click to collapse
I guess I couldn't explained my situation well. I installed carbon rom just now, and flashed gapps. I didn't check if carbon comes with a recovery but if it comes, I'm going to flash adrian dc's twrp through stock recovery. That's what I'm asking, is there a difference between using rashr to install twrp or flashing through recovery.
ExclusiveBFS said:
I guess I couldn't explained my situation well. I installed carbon rom just now, and flashed gapps. I didn't check if carbon comes with a recovery but if it comes, I'm going to flash adrian dc's twrp through stock recovery. That's what I'm asking, is there a difference between using rashr to install twrp or flashing through recovery.
Click to expand...
Click to collapse
Carbon provides CM recovery. Flash TWRP only through recovery, don't use Rashr.
ExclusiveBFS said:
I guess I couldn't explained my situation well. I installed carbon rom just now, and flashed gapps. I didn't check if carbon comes with a recovery but if it comes, I'm going to flash adrian dc's twrp through stock recovery. That's what I'm asking, is there a difference between using rashr to install twrp or flashing through recovery.
Click to expand...
Click to collapse
The recovery that comes with Carbon is most probably Cyanogen recovery which will not let you flash unsigned zip files like custom kernels & roms, SuperSU, Xposed, etc.
Its the reason why people install a recovery in their FOTA partitions because installing new kernels or roms (which include their own kernel) wipes out the previous recovery since Xperia phones esp older one's like ours don't have a separate recovery partition - the recovery is part of the kernel so it gets replaced by whatever came (or didn't) with the new kernel or rom. Atleast that's how it works to the best of my knowledge.
With fastboot, you could boot the device into TWRP recovery using the twrp-3.0.0-rX-boot-huashan.img file and the command "fastboot boot *filename*.img". This way its just temporary and doesn't permanently flash anything. Once in the recovery, flash the rom, kernel, recovery and you are done. That's how I did it on my Mi4i though you might want to confirm but since the description next to it says fastboot bootable, I guessing it works on the same principal.
Edit : If the kernel creator says no Rashr then its no Rashr.
XenolithicYardZone said:
The recovery that comes with Carbon is most probably Cyanogen recovery which will not let you flash unsigned zip files like custom kernels & roms, SuperSU, Xposed, etc.
Its the reason why people install a recovery in their FOTA partitions because installing new kernels or roms (which include their own kernel) wipes out the previous recovery since Xperia phones esp older one's like ours don't have a separate recovery partition - the recovery is part of the kernel so it gets replaced by whatever came (or didn't) with the new kernel or rom. Atleast that's how it works to the best of my knowledge.
With fastboot, you could boot the device into TWRP recovery using the twrp-3.0.0-rX-boot-huashan.img file and the command "fastboot boot *filename*.img". This way its just temporary and doesn't permanently flash anything. Once in the recovery, flash the rom, kernel, recovery and you are done. That's how I did it on my Mi4i though you might want to confirm but since the description next to it says fastboot bootable, I guessing it works on the same principal.
Edit : If the kernel creator says no Rashr then its no Rashr.
Click to expand...
Click to collapse
I find that flashing TWRP from CM recovery and then Helium from TWRP is much simpler than flashing TWRP as a kernel in the boot partition, then flashing the rom again and the kernel.
Tomoms said:
Carbon provides CM recovery. Flash TWRP only through recovery, don't use Rashr.
Click to expand...
Click to collapse
I flashed helium v5 for lollipop through twrp 3.0.0 and rebooted. It's not booted yet, i'm waiting for 2 minutes and the screen is black. Is it normal?
Tomoms said:
I find that flashing TWRP from CM recovery and then Helium from TWRP is much simpler than flashing TWRP as a kernel in the boot partition, then flashing the rom again and the kernel.
Click to expand...
Click to collapse
Wait hang on, CM recovery lets you flash custom zip files now without moaning about file verification? Since when?
Yes that's why I asked him to temporarily boot up with the TWRP img and then flash whatever he liked from it but hey if you can flash stuff via CM recovery now then that's one less step to worry about.
Also why no Rashr? I haven't used it in a while that's why I am asking.
---------- Post added at 05:10 PM ---------- Previous post was at 05:07 PM ----------
ExclusiveBFS said:
I flashed helium v5 for lollipop through twrp 3.0.0 and rebooted. It's not booted yet, i'm waiting for 2 minutes and the screen is black. Is it normal?
Click to expand...
Click to collapse
You mean black screen after the Sony splash screen? Is that rom compatible with Helium?
XenolithicYardZone said:
Wait hang on, CM recovery lets you flash custom zip files now without moaning about file verification? Since when?
Yes that's why I asked him to temporarily boot up with the TWRP img and then flash whatever he liked from it but hey if you can flash stuff via CM recovery now then that's one less step to worry about.
Also why no Rashr? I haven't used it in a while that's why I am asking.
---------- Post added at 05:10 PM ---------- Previous post was at 05:07 PM ----------
You mean black screen after the Sony splash screen? Is that rom compatible with Helium?
Click to expand...
Click to collapse
First, yes it lets you flash custom zip files, that's what I was trying to tell I always used cm recovery to install twrp
And I haven't used rashr before, I didn't know how to use it. So I flashed it with cm recovery and perfectly installed.
About helium, my phone finally booted after 9 minutes, how I scared
ExclusiveBFS said:
First, yes it lets you flash custom zip files, that's what I was trying to tell I always used cm recovery to install twrp
And I haven't used rashr before, I didn't know how to use it. So I flashed it with cm recovery and perfectly installed.
About helium, my phone finally booted after 9 minutes, how I scared
Click to expand...
Click to collapse
Sorry man didn't know that CM recovery lets you do that now. Been out of the loop for a while.
Lol yeah I can relate but as long as you can see a splash screen, you're good and when you don't, Flashtool is your light in the darkness :victory:
ExclusiveBFS said:
I flashed helium v5 for lollipop through twrp 3.0.0 and rebooted. It's not booted yet, i'm waiting for 2 minutes and the screen is black. Is it normal?
Click to expand...
Click to collapse
The reboot button is broken on TWRP. Causes black screen for a long time. You must always use the Power off option instead.
XenolithicYardZone said:
Sorry man didn't know that CM recovery lets you do that now. Been out of the loop for a while.
Lol yeah I can relate but as long as you can see a splash screen, you're good and when you don't, Flashtool is your light in the darkness :victory:
Click to expand...
Click to collapse
CM recovery lets you flash signed zip, and TWRP is provided in a signed zip, while even though Helium is provided in a signed zip, it can't be flashed.
Tomoms said:
The reboot button is broken on TWRP. Causes black screen for a long time. You must always use the Power off option instead.
CM recovery lets you flash signed zip, and TWRP is provided in a signed zip, while even though Helium is provided in a signed zip, it can't be flashed.
Click to expand...
Click to collapse
@Tomoms, @XenolithicYardZone Thanks for all your help, I used more than 10 roms so far but never used a custom kernel before. You two helped me a lot
Tomoms said:
The reboot button is broken on TWRP. Causes black screen for a long time. You must always use the Power off option instead.
CM recovery lets you flash signed zip, and TWRP is provided in a signed zip, while even though Helium is provided in a signed zip, it can't be flashed.
Click to expand...
Click to collapse
Yeah kinda guessed it was signed cause in all my time flashing roms, I have never known CM recovery to allow the flashing of unsigned zips. So why doesn't it work with Helium if its signed?
ExclusiveBFS said:
@Tomoms, @XenolithicYardZone Thanks for all your help, I used more than 10 roms so far but never used a custom kernel before. You two helped me a lot
Click to expand...
Click to collapse
Your welcome man. As a famous author once said, "Help will always be given at XDA to those who ask for it. "
XenolithicYardZone said:
Yeah kinda guessed it was signed cause in all my time flashing roms, I have never known CM recovery to allow the flashing of unsigned zips. So why doesn't it work with Helium if its signed?
Click to expand...
Click to collapse
Because CM recovery sucks
Tomoms said:
Because CM recovery sucks
Click to expand...
Click to collapse
True that!