I want to try the new ROM myONEdx+ RC2.0 (JB | Sense 4+ Lite) , but the author wants Recommended recovery by neXUS PRIME JB TWRP Recovery for hboot 1.25.0002 (JB hboot). I used the first version of this ROM , where he wants to install recovery by NexuS Prime JB Fixed. So my question is i have to flash TWRP recovery over Recommended Recovery by neXUS PRIME and fixed by atis112 - neXusRecovery for hboot 1.25.0002 (JB hboot) ? etc - fastboot flash recovery recovery.img
abatt said:
I want to try the new ROM myONEdx+ RC2.0 (JB | Sense 4+ Lite) , but the author wants Recommended recovery by neXUS PRIME JB TWRP Recovery for hboot 1.25.0002 (JB hboot). I used the first version of this ROM , where he wants to install recovery by NexuS Prime JB Fixed. So my question is i have to flash TWRP recovery over Recommended Recovery by neXUS PRIME and fixed by atis112 - neXusRecovery for hboot 1.25.0002 (JB hboot) ? etc - fastboot flash recovery recovery.img
Click to expand...
Click to collapse
First of all, Are you on JB HBoot? If yes then flash the TWRP Recovery by Nexus (It is recommended over the fixed recovery). Then flash the custom ROM.
abatt said:
I want to try the new ROM myONEdx+ RC2.0 (JB | Sense 4+ Lite) , but the author wants Recommended recovery by neXUS PRIME JB TWRP Recovery for hboot 1.25.0002 (JB hboot). I used the first version of this ROM , where he wants to install recovery by NexuS Prime JB Fixed. So my question is i have to flash TWRP recovery over Recommended Recovery by neXUS PRIME and fixed by atis112 - neXusRecovery for hboot 1.25.0002 (JB hboot) ? etc - fastboot flash recovery recovery.img
Click to expand...
Click to collapse
fastboot flash recovery recovery.img is correct command
TWRP Recovery for JB is recommended but you can use any recovery meant for JB that you like and comfortable with, not necessarily must use TWRP.
Thank's for quick response i'll tried later
I flashed with TWRP and everything is fine and working OK. I only forget that before starting flashing custom ROMs i made a backup with NexuS Recovery which is CWM recovery and when i decide to restore i cant do it with TWRP , but that's not a big problem
abatt said:
I flashed with TWRP and everything is fine and working OK. I only forget that before starting flashing custom ROMs i made a backup with NexuS Recovery which is CWM recovery and when i decide to restore i cant do it with TWRP , but that's not a big problem
Click to expand...
Click to collapse
If that's your stock backup, keep it safe... when you need to restore it next time just reflash NexusRecovery and restore
Thanks in advance for your reply My next question will be can i restore CWM over TWRP , but now i find the idea of recovery and flashing.:good:
Related
title say it all...i recently got my onex+..and unlocked the bootloader..iam wondering that is it essential to flash venom recovery or a normal twrp recovery would aalso do the trick?
I am using the "regular" TWRP + Viper XL+ without problem.
thanks
My HTC one m8 has root access. I was using twrp recovery and stock rom. I wanted to flash a custom rom (tried cyanogen and pan) but twrp never helped me in finding my zip file. Then I tried swapping my recovery from twrp to cwm but that never happened and it got stuck in bootloader mode and then I did factory reset :/. And now everytime I try going into recovery it takes me to the bootloader mode. now I am trying flashing a custom recovery but first turning s_off and I tried firewater but it doesn't work.
What should I do?
It still has root access but s_on and don't know about bootloader on/off and no recovery.
Sent from my HTC one m8 using XDA Free mobile app
Fahad khan lodhi said:
My HTC one m8 has root access. I was using twrp recovery and stock rom. I wanted to flash a custom rom (tried cyanogen and pan) but twrp never helped me in finding my zip file. Then I tried swapping my recovery from twrp to cwm but that never happened and it got stuck in bootloader mode and then I did factory reset :/. And now everytime I try going into recovery it takes me to the bootloader mode. now I am trying flashing a custom recovery but first turning s_off and I tried firewater but it doesn't work.
What should I do?
It still has root access but s_on and don't know about bootloader on/off and no recovery.
Sent from my HTC one m8 using XDA Free mobile app
Click to expand...
Click to collapse
and does your device say unlocked at the top of your bootloader? if not follow this guild http://forum.xda-developers.com/showthread.php?t=2799796 , but use the twrp for you device carrier only
if you did it via recovery you should still be ok
go to your bootloader download this twrp img here http://techerrata.com/file/twrp2/m8/openrecovery-twrp-2.7.1.0-m8.img on your computer (for gsm) int. att (i'm guessing this is the device carrier you have)
ensure you have fastboot tools(adb tools installed)
put the .img in your folder that contains fastboot
open a cmd in that folder on your computer and make sure you put your phone in fastboot mode via your bootloader.
then type on your computer in cmd fastboot flash recovery (name of twrp you downloaded).img
then type fastboot erase cache
you now have twrp installed to get to it now select recovery from bootloader on your phone.
when installing custom roms in twrp you need to go to advanced wipe(select data,cache,delvik cache, and system then swipe the arrow bar beneath)
then press home and press install the go to the location on the sdcard where you put the rom.zip of the custom rom and select it. instalation will begin after completion reboot(done)
It says unlocked at the top but S On.
Shouldn't I turn s off before flashing recovery?
Sent from my unknown using XDA Free mobile app
@Fahad khan lodhi
it won't matter either way.
but just so you know what s-off is
s-off turns security mode off so you can swap out boot splashes and such, if you s-off and super cid you can flash any carrier's firmware,
also allows you to flash a kernel in recovery on older devices(m8 doesn't need s-off to flash kernel)
Can't S-Off unless you can boot. Firewater only works if you can get into the OS and then only for some devices. You should reinstall TWRP and see if you can boot to it then put a rom on an external SD card or use adb to push a rom zip to the internal if you don't have an SD card. Make sure that you fastboot flash the boot.img of whatever rom you are trying due to being S-On. If all that fails, then you will need to find the same or newer RUU from HTC for your carrier to restore the phone to stock and start over.
es0tericcha0s said:
Can't S-Off unless you can boot. Firewater only works if you can get into the OS and then only for some devices. You should reinstall TWRP and see if you can boot to it then put a rom on an external SD card or use adb to push a rom zip to the internal if you don't have an SD card. Make sure that you fastboot flash the boot.img of whatever rom you are trying due to being S-On. If all that fails, then you will need to find the same or newer RUU from HTC for your carrier to restore the phone to stock and start over.
Click to expand...
Click to collapse
Hey thank you very much.
It helped and i flashed latest twrp recovery and then flashed viper one m8 1.8.0 rom but the latest version is 2.4.0 and it says to have that your firmware should be 4.4.3 and i have 4.4.2.
Question is can i flash paranoid android coz that gives me 4.4.4 firmware and then flash latest viper one m8 version or i have to go to stock rom and update it and then flash latest version of viper?
Reply please.
Sent from my HTC One_M8 using XDA Free mobile app
Fahad khan lodhi said:
Hey thank you very much.
It helped and i flashed latest twrp recovery and then flashed viper one m8 1.8.0 rom but the latest version is 2.4.0 and it says to have that your firmware should be 4.4.3 and i have 4.4.2.
Question is can i flash paranoid android coz that gives me 4.4.4 firmware and then flash latest viper one m8 version or i have to go to stock rom and update it and then flash latest version of viper?
Reply please.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
It should still work with the firmware you have. It's recommended but not necessary. And flashing PA would certainly not update your firmware. Firmware in this instance is mostly focused on the radio/baseband version and the touch drivers. These are not included in any kind of custom rom for your phone (nor 99% of android custom roms for anything). Much more important if you were originally on 4.2.2 or 4.3 and trying to run the new Viper. The only way to update firmware while S-On is via RUU or OTA. If you were S-Off then you could flash just the firmware package that has the hboot and stock recovery files removed.
Hello guys,
Today i am going to unlock (Official way) my device and going to try AOSP 5.1.1 V4.
My doubt is
1) If i want to revert back to Miui, If i use fastboot rom and flash full rom, will this make my bootloader locked again.
2) If i flash miui recovery rom using twrp without modified boot.img and i dont want twrp and revert back to default miui recovery how to do so.....
3) If i change to miui recovery after flashing recovery rom with twrp do i again need to flash modified boot.img.
I suggest to make full recovery image of original miui. After clean install with full wipe i had problems with unlocking phone.
asrupesh said:
1) If i want to revert back to Miui, If i use fastboot rom and flash full rom, will this make my bootloader locked again.
2) If i flash miui recovery rom using twrp without modified boot.img and i dont want twrp and revert back to default miui recovery how to do so.....
3) If i change to miui recovery after flashing recovery rom with twrp do i again need to flash modified boot.img.
Click to expand...
Click to collapse
1) Yes
2) You cant, you will need TWRP, modded boot.img & MIUI ROM else it will bootloop
3) Yes
Hello guys
I was on stock android and stock recovery oos 3.1.3. I tried to change recovery using fastboot so i tried so many recovries, but unable to flash anyone then i found twrp recovery by teamspark so i flashed it and successfully done, but problem with it is, i am not able toh flash paranoid rom and stock rom using this recovery and even the stock recovery is also not flashable now, just stuck on logo whenever i flash stock recovery. So which recovery i can use which can correctly flashable and i can flash paranoid rom by that successfully.
Thanks in advance.
Flash old stock recovery followed by any OOS 2.X.X firmware . Now you can proceed with PA. Note dont use any of the twrp's designed for mm bootloader.
Rajatdembla said:
Hello guys
I was on stock android and stock recovery oos 3.1.3. I tried to change recovery using fastboot so i tried so many recovries, but unable to flash anyone then i found twrp recovery by teamspark so i flashed it and successfully done, but problem with it is, i am not able toh flash paranoid rom and stock rom using this recovery and even the stock recovery is also not flashable now, just stuck on logo whenever i flash stock recovery. So which recovery i can use which can correctly flashable and i can flash paranoid rom by that successfully.
Thanks in advance.
Click to expand...
Click to collapse
First of all, you have to downgrade your bootloader. Then you can flash any recovery for the old bootloader.
Thanks i m done now
Exodusche said:
Flash old stock recovery followed by any OOS 2.X.X firmware . Now you can proceed with PA. Note dont use any of the twrp's designed for mm bootloader.
Click to expand...
Click to collapse
Thank you so much brother now i m able to flash.
My phone stucks on oneplus logo after flashing paranoid rom . I do everything like wiping dalvin cache, data , system . TWRP recovery i am using is 3.03 and currently running cm 13. Any solution?
Mandeep Singh 07 said:
My phone stucks on oneplus logo after flashing paranoid rom . I do everything like wiping dalvin cache, data , system . TWRP recovery i am using is 3.03 and currently running cm 13. Any solution?
Click to expand...
Click to collapse
Is ur bootloader updated to latest one ??
[email protected] said:
Is ur bootloader updated to latest one ??
Click to expand...
Click to collapse
yeah its latest one 3.0.3
Mandeep Singh 07 said:
yeah its latest one 3.0.3
Click to expand...
Click to collapse
PA I believe is on the old bootloader still. So you would have to downgrade your bootloader by flashing LL stock recovery and 2.x.x OOS firmware. Not worth the hassle if you ask me.
Mandeep Singh 07 said:
yeah its latest one 3.0.3
Click to expand...
Click to collapse
actually when i root the phone , then it goes into bootloop, i didn`t backup my data so i lost my all data ,
after that i install paranoid then it stucks on boot logo , i tried it several times but none happens,
then i use adb push command ino twrp recovery(3.0.2) to copy cyanogenmod after that i flash it , it fails ,
then i flash cwm recovery then flash is succeded and currently running cm 13 ,
when i installed root checker it said your phone is partially rooted, when i enable root option in developer option then it said root verified.
But when i tried to flash other roms using twrp (3.0.3, 3.0.2) it stucks on boot logo.
Please help me
Exodusche said:
PA I believe is on the old bootloader still. So you would have to downgrade your bootloader by flashing LL stock recovery and 2.x.x OOS firmware. Not worth the hassle if you ask me.
Click to expand...
Click to collapse
lower bootloader can`t flash it fails every time....
Mandeep Singh 07 said:
lower bootloader can`t flash it fails every time....
Click to expand...
Click to collapse
Did you also revert to the old TWRP version 3.0.2? Other then that I'm out of ideas.
Exodusche said:
Did you also revert to the old TWRP version 3.0.2? Other then that I'm out of ideas.
Click to expand...
Click to collapse
At that twrp blu spark 3.0.2 is available and of only that recovery is working lower recoviers cant flash and boot
Mandeep Singh 07 said:
At that twrp blu spark 3.0.2 is available and of only that recovery is working lower recoviers cant flash and boot
Click to expand...
Click to collapse
Right but if your downgrading your bootloader to flash PA you need to use old bootloader TWRP 3.0.2. So that being said easiest way is flash 2.2.3 with blusprk 3.0.2-2 TWRP then immediately after flash TWRP 3.0.2 image. Now re boot back into recovery and flash PA. I prefer flashing 2.2.3 with stock LL recovery less chance of issues. Then just fastboot flash old TWRP 3.0.2 and continue with PA.
Exodusche said:
Right but if your downgrading your bootloader to flash PA you need to use old bootloader TWRP 3.0.2. So that being said easiest way is flash 2.2.3 with blusprk 3.0.2-2 TWRP then immediately after flash TWRP 3.0.2 image. Now re boot back into recovery and flash PA. I prefer flashing 2.2.3 with stock LL recovery less chance of issues. Then just fastboot flash old TWRP 3.0.2 and continue with PA.
Click to expand...
Click to collapse
thanks bro this works fine