Hello everyone I'm new to all this so please go easy on me.
The problem I am having is I want to install lineage os on my HTC one max but every time I do so after I hit reboot system the HTC logo comes up and then my phone will constantly restart it self. i wipe dalvik cache, Cache, data and system before I flash the Rom and gapps, any help would be appreciated thanks
The rom that you are trying to install is official lineage, is not where you get the rom i ned more info,
mtkmanjaro said:
The rom that you are trying to install is official lineage, is not where you get the rom i ned more info,
Click to expand...
Click to collapse
i would send a link to it but as i am new i am not allowed if you search "Htc One Max LineageOS" it's the first link by Cyanogenmods.org there is a download link in there.
it is supposed to be an unofficial version by tarkzim
EJ251 said:
i would send a link to it but as i am new i am not allowed if you search "Htc One Max LineageOS" it's the first link by Cyanogenmods.org there is a download link in there.
it is supposed to be an unofficial version by tarkzim
Click to expand...
Click to collapse
Well there's two possible causes for bootlop, this build is not support your variant , or you downloaded the wrong architecture of gapps for Htc one Max you need to get the Arm 32 gapps, if you flashed the Arm 64 then there's the problem.
I suppose you do all wipes before flashing the rom.
mtkmanjaro said:
Well there's two possible causes for bootlop, this build is not support your variant , or you downloaded the wrong architecture of gapps for Htc one Max you need to get the Arm 32 gapps, if you flashed the Arm 64 then there's the problem.
I suppose you do all wipes before flashing the rom.
Click to expand...
Click to collapse
according to my phone the model number is just HTC One Max, i am using the 32bit gapps and have done all wipes before hand.
EJ251 said:
according to my phone the model number is just HTC One Max, i am using the 32bit gapps and have done all wipes before hand.
Click to expand...
Click to collapse
Maybe you need to update to a lastest firmware before installing lineage, ¿Are you trying a custom kernel or something? If you do all wipes and your variant is supported i don't see the reason, why you can't boot, you can try another rom to see if the problem is in the lineage rom itself
mtkmanjaro said:
Maybe you need to update to a lastest firmware before installing lineage, ¿Are you trying a custom kernel or something? If you do all wipes and your variant is supported i don't see the reason, why you can't boot, you can try another rom to see if the problem is in the lineage rom itself
Click to expand...
Click to collapse
yeah ill give another rom a try, i got onto cyanogen's website and looked through the device support list and my phone isn't listed on either the official or unofficial list so i dunno maybe it doesn't support it not sure why there is a download available though
Related
Hi i have a problem, when i install custom rom for example. rr 5.8.3 on 7.1.2 when i boot phone and i have screen welcome and i start configuration and this configuration crashed, i install with wipe, and i install new nitrogenos and i have the same situation. When i install rom on 7.1.1 all its ok, what can i do to fix it? Please help me its screen from phone http://imgur.com/a/uUPls
You might be using an outdated GApps package, as it is known to cause this issue. Try with the latest opengapps.
jayaram95 said:
You might be using an outdated GApps package, as it is known to cause this issue. Try with the latest opengapps.
Click to expand...
Click to collapse
Yea i install old version gapps and i dont have any problems on 7.1.1, hmm then i must install new gapps if i check i will write
;P
You can flash newer gapps from here.
OR
You can follow this guide on older gapps.
Very thanks, i have one question, i must install firmware to install rom for example rr or nitrogen? i never install and everything is right
Okay i install beansgapps and its works Thanks for help
badamczuk1 said:
Very thanks, i have one question, i must install firmware to install rom for example rr or nitrogen? i never install and everything is right
Click to expand...
Click to collapse
no need to flash it if there's nothing wrong
if there's something wrong, try to flash latest MIUI Beta firmware, you can find it in ROM section, and no need to flash it everytime you flash a new ROM, just flash it once and you're good to go
Hey XDA-Community
I sent my phone to oneplus for repairing it. They wrote that as solution for my problem (speakers didn't work) they just replaced the mainboard. But now I'm unable to install TWRP persistently. After every reboot I get the stock recovery. Furthermore if I'm in TWRP wich I just booted from fastboot I can't install anything. If I want to flash SuperSu it says errors like: "Unable to find partition size for '/boot'" (also other partitions like '/recovery', '/misc'...) then in the console the folowing error gets displayed: "Unable to mount '/data' (Invalid argument)" this continues with all the other partitions, and then (obviously) SuperSU doesn't get installed. I have attached a screentshot about my phone info. Do you have any idea how I can fix this? Do you need any further information? Feel free to ask.
Maybe this thread is helpful: https://forum.xda-developers.com/on...official-twrp-arsenic-kernel-oneplus-t3573644
It's for E1003_15
Tagion said:
Maybe this thread is helpful: https://forum.xda-developers.com/on...official-twrp-arsenic-kernel-oneplus-t3573644
It's for E1003_15
Click to expand...
Click to collapse
well TWRP does work, but I can't boot into android now do you know where I can find a compatible ROM for Oneplux X E1003 with arsenic kernel. I really searched everywhere, but haven't found anything
TheAustrian1337 said:
well TWRP does work, but I can't boot into android now do you know where I can find a compatible ROM for Oneplux X E1003 with arsenic kernel. I really searched everywhere, but haven't found anything
Click to expand...
Click to collapse
Did you flashed Arsenic Kernel (from the thread I sent) with the ROM?
Which version of oos was installed?
Samarth_17 said:
Which version of oos was installed?
Click to expand...
Click to collapse
It was version 3.1.4
Tagion said:
Did you flashed Arsenic Kernel (from the thread I sent) with the ROM?
Click to expand...
Click to collapse
Yeah I also flashed that one, should I undo this step? Like just wiping everything
TheAustrian1337 said:
Yeah I also flashed that one, should I undo this step? Like just wiping everything
Click to expand...
Click to collapse
Just follow the instructions
Tagion said:
Just follow the instructions
Click to expand...
Click to collapse
I did that (I hope a least) but the ROM just shows it's boot screen. The ROM I used is that one: https://forum.xda-developers.com/oneplus-x/development/rom-xperience-11-1-t3507588 do you think I should try the official ROM: http://downloads.oneplus.net/oneplus-x/oneplus_x_oxygenos_3.1.4/
TheAustrian1337 said:
Hey XDA-Community
I sent my phone to oneplus for repairing it. They wrote that as solution for my problem (speakers didn't work) they just replaced the mainboard. But now I'm unable to install TWRP persistently. After every reboot I get the stock recovery. Furthermore if I'm in TWRP wich I just booted from fastboot I can't install anything. If I want to flash SuperSu it says errors like: "Unable to find partition size for '/boot'" (also other partitions like '/recovery', '/misc'...) then in the console the folowing error gets displayed: "Unable to mount '/data' (Invalid argument)" this continues with all the other partitions, and then (obviously) SuperSU doesn't get installed. I have attached a screentshot about my phone info. Do you have any idea how I can fix this? Do you need any further information? Feel free to ask.
Click to expand...
Click to collapse
TWRP: https://forum.xda-developers.com/oneplus-x/orig-development/recovery-twrp-r1-03-05-t3600887
ROM (pick any): https://forum.xda-developers.com/oneplus-x/development/roms-ground-zero-roms-validus-tesla-t3546588
Kernel: https://www.arsenic-kernel.download
Flash the latest kernel along with zip, Tesla already has R46 which will work on your repaired device.
CheckYourScreen said:
TWRP: https://forum.xda-developers.com/oneplus-x/orig-development/recovery-twrp-r1-03-05-t3600887
ROM (pick any): https://forum.xda-developers.com/oneplus-x/development/roms-ground-zero-roms-validus-tesla-t3546588
Kernel: https://www.arsenic-kernel.download
Flash the latest kernel along with zip, Tesla already has R46 which will work on your repaired device.
Click to expand...
Click to collapse
I did that, and tried it for a few days. But unfortunately most of my Apps crash all the time, or after a few minutes. Sometimes I cant, lock or unlock my screen and root with SUperSU just disapperes sometimes Sadly this custom rom is very unstable. Is there maybe ANY way I cold just flash the Android 6 stock ROM on it and root it with anything? I really don't care what I have to do for rooting it, but this ROM is just too buggy... but it looks nice, and having Android 7 is also ver cool:fingers-crossed::good:
TheAustrian1337 said:
I did that, and tried it for a few days. But unfortunately most of my Apps crash all the time, or after a few minutes. Sometimes I cant, lock or unlock my screen and root with SUperSU just disapperes sometimes Sadly this custom rom is very unstable. Is there maybe ANY way I cold just flash the Android 6 stock ROM on it and root it with anything? I really don't care what I have to do for rooting it, but this ROM is just too buggy... but it looks nice, and having Android 7 is also ver cool:fingers-crossed::good:
Click to expand...
Click to collapse
Check inbox, I've sent you link of AOSP-JDC rom.
I haven't released it yet so can share it here in post, though its publicly available on my androidfilehost account.
Try it once.
CheckYourScreen said:
Check inbox, I've sent you link of AOSP-JDC rom.
I haven't released it yet so can share it here in post, though its publicly available on my androidfilehost account.
Try it once.
Click to expand...
Click to collapse
I found and installed your rom, works very well. I hope you will continue to update this rom
CheckYourScreen said:
TWRP: https://forum.xda-developers.com/oneplus-x/orig-development/recovery-twrp-r1-03-05-t3600887
ROM (pick any): https://forum.xda-developers.com/oneplus-x/development/roms-ground-zero-roms-validus-tesla-t3546588
Kernel: https://www.arsenic-kernel.download
Flash the latest kernel along with zip, Tesla already has R46 which will work on your repaired device.
Click to expand...
Click to collapse
I have the same build number as OP (E1003_15_161107). Phone is untouched and on stock ROM. Read things about our devices being different than others and hence little to no ROM support. So I am a bit lost. I reckon recovery provided by you works well on our device. What about the ROMs ? Can I flash any of my choice ? And Kernels ? Can I opt for kernels other than Arsenic ? (Big fan of Franco. Using his kernel on my OPO)
Ruvy said:
I have the same build number as OP (E1003_15_161107). Phone is untouched and on stock ROM. Read things about our devices being different than others and hence little to no ROM support. So I am a bit lost. I reckon recovery provided by you works well on our device. What about the ROMs ? Can I flash any of my choice ? And Kernels ? Can I opt for kernels other than Arsenic ? (Big fan of Franco. Using his kernel on my OPO)
Click to expand...
Click to collapse
Yes you can flash any rom of your choice, just make sure you flash Arsenic R46 along with the rom zip as kernel is what makes your device boot. I'm not sure about franco's kernel so better ask in his respective thread?
No Luck for me.
Version 3.2.1-0 not work here.
BUILD E1003_15, i have to use this Version to get a ROM work.
https://forum.xda-developers.com/on...official-twrp-arsenic-kernel-oneplus-t3573644
Is there be a fix for my Version of the OPX ?
Regards
Been using the Xiaomi Redmi Note 3 (Kenzo) for a long time now and since the ROM was outdated, I decided to update it this past weekend. However for whatever reason, something broke and I've been getting bootloops. Since then, this is what I did and it still doesn't work.
Used MiFlash to fastboot flash MIUI v8.5.1.0 Global Stable, and then OTA updated to v8.5.2.0.
Test the phone to make sure all functions work properly.
Immediately officially unlocked the bootloader using Mi Unlock.
Fastboot flashed TWRP 3.1.1.0.
Made EFS and ROM backups as usual.
Clean flashed Resurrection Remix 5.7.4 (Radon kernel) with /data and /cache as F2FS.
Flashed Open Gapps 6.0 ARM64 Mini.
Right now, I'm back to running stock MIUI v8.5.1.0, which was flashed using MiFlash. Then I did the OTA update to MIUI v8.5.2.0. May someone please guide me or correct the above steps in order to install the linked Resurrection Remix ROM? Or maybe a Nougat ROM?
geokilla said:
Been using the Xiaomi Redmi Note 3 (Kenzo) for a long time now and since the ROM was outdated, I decided to update it this past weekend. However for whatever reason, something broke and I've been getting bootloops. Since then, this is what I did and it still doesn't work.
Used MiFlash to fastboot flash MIUI v8.5.1.0 Global Stable, and then OTA updated to v8.5.2.0.
Test the phone to make sure all functions work properly.
Immediately officially unlocked the bootloader using Mi Unlock.
Fastboot flashed TWRP 3.1.1.0.
Made EFS and ROM backups as usual.
Flashed Resurrection Remix 5.7.4 (Radon kernel) with /data and /cache as F2FS.
Flashed Open Gapps 6.0 ARM64 Mini.
Right now, I'm back to running stock MIUI v8.5.1.0, which was flashed using MiFlash. Then I did the OTA update to MIUI v8.5.2.0. May someone please guide me or correct the above steps in order to install the linked Resurrection Remix ROM? Or maybe a Nougat ROM?
Click to expand...
Click to collapse
Try without f2fs. Use ext4
geokilla said:
Been using the Xiaomi Redmi Note 3 (Kenzo) for a long time now and since the ROM was outdated, I decided to update it this past weekend. However for whatever reason, something broke and I've been getting bootloops. Since then, this is what I did and it still doesn't work.
Used MiFlash to fastboot flash MIUI v8.5.1.0 Global Stable, and then OTA updated to v8.5.2.0.
Test the phone to make sure all functions work properly.
Immediately officially unlocked the bootloader using Mi Unlock.
Fastboot flashed TWRP 3.1.1.0.
Made EFS and ROM backups as usual.
Flashed Resurrection Remix 5.7.4 (Radon kernel) with /data and /cache as F2FS.
Flashed Open Gapps 6.0 ARM64 Mini.
Right now, I'm back to running stock MIUI v8.5.1.0, which was flashed using MiFlash. Then I did the OTA update to MIUI v8.5.2.0. May someone please guide me or correct the above steps in order to install the linked Resurrection Remix ROM? Or maybe a Nougat ROM?
Click to expand...
Click to collapse
Flash LOS 13 which is far stable than the RR 5.7.4. You should've flashed another rom before moving back to MIUI. The process you followed is correct but you also need to flash the compatible firmware like for RR you need CM13 firmare and for LOS you'll the recommended firmware posted in the thread itself.
I went through some ROM threads and one recommended flashing MIUI8 Global DEVELOPER and not Global STABLE. Am I supposed to be using MIUI 8 Global DEVELOPER as the starting point?
vistaabalaji said:
Try without f2fs. Use ext4
Click to expand...
Click to collapse
EXT4 had the same issue. Just bootloops forever.
naturist said:
Flash LOS 13 which is far stable than the RR 5.7.4. You should've flashed another rom before moving back to MIUI. The process you followed is correct but you also need to flash the compatible firmware like for RR you need CM13 firmare and for LOS you'll the recommended firmware posted in the thread itself.
Click to expand...
Click to collapse
The Resurrection Remix build I linked is based off of LineageOS 13 so it should be stable.
So you're saying I missed flashing a firmware? I see some ROMs recommend flashing the firmware, while others don't. Which is the proper firmware to flash if the ROM thread doesn't state which firmware to use?
geokilla said:
I went through some ROM threads and one recommended flashing MIUI8 Global DEVELOPER and not Global STABLE. Am I supposed to be using MIUI 8 Global DEVELOPER as the starting point?
EXT4 had the same issue. Just bootloops forever.
The Resurrection Remix build I linked is based off of LineageOS 13 so it should be stable.
So you're saying I missed flashing a firmware? I see some ROMs recommend flashing the firmware, while others don't. Which is the proper firmware to flash if the ROM thread doesn't state which firmware to use?
Click to expand...
Click to collapse
The one on this thread. Second post.
well seems to be a new problem...
so what must be done... i will suggest to get latest miui fastboot rom from here
https://forum.xda-developers.com/redmi-note-3/how-to/links-direct-official-download-links-t3449488
flash it via mi flash tool (im running 64 bit os ,so using mi flash beta ) in edl mode by wiping full things including storage..
if your boot loader is unlocked official way it must be unlocked now also if not i guess you know how to unlock it officially.
then use official twrp from
www.twrp.me
i faced this issue once and did the exact steps above and now no problem..
by the way i tried things like unplugging battery from the board... lol... read in miui forum...
I've been having very similar issues (updated official firmware in a non officially unlocked bootloader).
It's been hell but I've managed to get los14.1 installed. Now my issue lies with constant gapps crashes. I'm thinking of just giving up and getting miui.
Felheipe said:
I've been having very similar issues (updated official firmware in a non officially unlocked bootloader).
It's been hell but I've managed to get los14.1 installed. Now my issue lies with constant gapps crashes. I'm thinking of just giving up and getting miui.
Click to expand...
Click to collapse
use latest gapps.outdated or older one causes crashes...
adithyan25 said:
use latest gapps.outdated or older one causes crashes...
Click to expand...
Click to collapse
One would think so but in reality is the other way around. I'm using a 20170303 and it has been the most stable version across all my devices and so on.
Felheipe said:
One would think so but in reality is the other way around. I'm using a 20170303 and it has been the most stable version across all my devices and so on.
Click to expand...
Click to collapse
seriously the one from march??
dude just download older gapps wont work on latest updates. ot will force close for sure...
at least try before telling ..use latest one from opengapps... there is a reason they are updating tje sote everyday...ftom the may builds you need latest gapps as petr release dates... just give a try ..its only 150 mb or so.... i can vonform its duw to outdated gapps
adithyan25 said:
well seems to be a new problem...
so what must be done... i will suggest to get latest miui fastboot rom from here
https://forum.xda-developers.com/redmi-note-3/how-to/links-direct-official-download-links-t3449488
flash it via mi flash tool (im running 64 bit os ,so using mi flash beta ) in edl mode by wiping full things including storage..
if your boot loader is unlocked official way it must be unlocked now also if not i guess you know how to unlock it officially.
then use official twrp from
www.twrp.me
i faced this issue once and did the exact steps above and now no problem..
by the way i tried things like unplugging battery from the board... lol... read in miui forum...
Click to expand...
Click to collapse
That's exactly what I did, as I mentioned in OP lol. Except I wasn't flashing MIUI 8 in EDL mode.
adithyan25 said:
seriously the one from march??
dude just download older gapps wont work on latest updates. ot will force close for sure...
at least try before telling ..use latest one from opengapps... there is a reason they are updating tje sote everyday...ftom the may builds you need latest gapps as petr release dates... just give a try ..its only 150 mb or so.... i can vonform its duw to outdated gapps
Click to expand...
Click to collapse
I tried 0625 and the newest one. 0303 is the latest stable Google play services (as far as i am aware).
Felheipe said:
I tried 0625 and the newest one. 0303 is the latest stable Google play services (as far as i am aware).
Click to expand...
Click to collapse
no idont guess so...
pls try after downloading latest one from here
www.opengapps.org
arm64-7.1- pico(if you want Google assistant you must use nano or above)
iam using yesterday build of opengapps and not facing any issues...and do a clean flash if possible...
or else you can tru beansgapps....
edit:- playservices had updated many times after 0303.. so i can say its outdated
adithyan25 said:
no idont guess so...
pls try after downloading latest one from here
www.opengapps.org
arm64-7.1- pico(if you want Google assistant you must use nano or above)
iam using yesterday build of opengapps and not facing any issues...and do a clean flash if possible...
or else you can tru beansgapps....
Click to expand...
Click to collapse
I've tried yesterdays version. Play store wouldn't even open. Dirty flashed 0625 play store opens but a lot of apps crash, everything works fine with 0303.
I'm flashing miui and I'm going to try the official bootloader unlock, but this have been a couple of strange days.
Felheipe said:
I've tried yesterdays version. Play store wouldn't even open. Dirty flashed 0625 play store opens but a lot of apps crash, everything works fine with 0303.
I'm flashing miui and I'm going to try the official bootloader unlock, but this have been a couple of strange days.
Click to expand...
Click to collapse
dirty flashing isn't a solution ... theres changes in trees of the rom and kernel..
anyway head back to miui unlocl officially and when coming back to custom rom do wipe everything and give it a shot..probably the crash may be due to over written or exiating files...
happy flashing
~peace
I should mention I clean flashed the ROMs. Updated OP.
Ok trying it again right now and so far, this is what I did:
Used MiFlash to fastboot flash MIUI v7.7.6 Global DEV.
Test the phone to make sure all functions work properly.
Tried to unlock bootloader using Mi Unlock but it said bootloader is already unlocked.
Boot into MIUI again.
Fastboot flashed TWRP 3.1.1.0.
No boot into MIUI.
Flash Kenzo firmware 8.2.4.0 in TWRP
Clean flash LineageOS 13 and Open Gapps 6.0 ARM64 Mini with /data and /cache in EXT4
IT WORKS!
I guess now I'll try Resurrection Remix.
I somehow uninstalled my OS tonight when I was trying to flash AOSP's Oreo ROM. The flashing was unsuccessful (Error: 7) but I've noticed that no ROMs will flash at all.
I'm getting the same error for all ROMs despite them being suitable for my device:
Updater Process ended with ERROR: 7 Error Installing Zip File "ROM xx.x.x..."
Click to expand...
Click to collapse
Things I've done:
I've tried wiping the cache before I flash ROMS
I am on the most updated version of TWRP available for my device (3.0.2)
I've tried changing the updater-script as someone pointed out in another thread but it did not help
At this point, I just want a stable OS that will run on the phone.... Can someone help me? I just want to understand the error and what's causing it and install a ROM that would work...
Look for Mega Unbrick Guide to install a OS.
Sent from my Pixel 2 XL using Tapatalk
That's odd, because Error 7 is usually related to Updater-Script. Have you modified your model name in Updater-Script or just removed the line from it?
jklh said:
[*]I am on the most updated version of TWRP available for my device (3.0.2)
.
Click to expand...
Click to collapse
TWRP version is 3.1.1-1 now so you're not on the last.
Beside that, the question is what was on your device before :
- Did you already installed OOS 3.1.4 at one point?
- Didi you use the BLUpdater method to update the bootloader (logic ) ?
If no to the 2 questions above, that is the problem. So , you'll have to use the mega unbrick guide !
Kéno40 said:
TWRP version is 3.1.1-1 now so you're not on the last.
Beside that, the question is what was on your device before :
- Did you already installed OOS 3.1.4 at one point?
- Didi you use the BLUpdater method to update the bootloader (logic ) ?
If no to the 2 questions above, that is the problem. So , you'll have to use the mega unbrick guide !
Click to expand...
Click to collapse
I actually haven't done both. I tried flashing the OOS 3.1.4 full ROM but it did not work. I will update my TWRP to 3.1.1-1 and I'll try it again. I do have an update though, I am able to flash an old version of Android M OOS using "OnePlusOxygen_14_OTA_003_all_201510241934". If I am able to install this, maybe this isn't a bricked device? Any advice would be super useful, thanks in advance.
jklh said:
I actually haven't done both. I tried flashing the OOS 3.1.4 full ROM but it did not work. I will update my TWRP to 3.1.1-1 and I'll try it again. I do have an update though, I am able to flash an old version of Android M OOS using "OnePlusOxygen_14_OTA_003_all_201510241934". If I am able to install this, maybe this isn't a bricked device? Any advice would be super useful, thanks in advance.
Click to expand...
Click to collapse
If you haven't done any of the 2 things listed, then you tried to flash a "new Bootloader rom", you have no choice :
=> MEGA UNBRICK GUIDE
Hey guys, I have a few questions regarding the recovery, any help is appreciated.
1>Which Recovery did you flash?
2>Can you dirty flash roms(to update the ROM from one ver. to another) in it?(Because i read that the data must be cleared after flashing any rom)
3>Which ROM and recovery are you on?
4>Are there any special methods you need to follow to flash?
Thanks in advance :good:
LineageOS recovery
No dirty flash
LineageOS 17.1
Adb sideloading
CV2000 said:
Hey guys, I have a few questions regarding the recovery, any help is appreciated.
1>Which Recovery did you flash?
2>Can you dirty flash roms in it?(Because i read that the data must be cleared after flashing any rom)
3>Which ROM and recovery are you on?
4>Are there any special methods you need to follow to flash?
Thanks in advance :good:
Click to expand...
Click to collapse
1. OrangeFox Alpha build (note the description "Alpha" - meaning it is still at a pre-release stage)
2. You must format data if changing ROMs
3. I have tried 6 Android 11 ROMs (all of them have one issue or the other), and 10 Android 10 ROMs. I will probably settle for EvoX or Corvus (Android 10, both by dungphp)
4. No. Just select ROM zip and flash, and then format data
DarthJabba9 said:
1. OrangeFox Alpha build (note the description "Alpha" - meaning it is still at a pre-release stage)
2. You must format data if changing ROMs
3. I have tried 6 Android 11 ROMs (all of them have one issue or the other), and 10 Android 10 ROMs. I will probably settle for EvoX or Corvus (Android 10, both by dungphp)
4. No. Just select ROM zip and flash, and then format data
Click to expand...
Click to collapse
Do you need to wipe data after dirty flashing to update a rom to a higher version?
CV2000 said:
Do you need to wipe data after dirty flashing to update a rom to a higher version?
Click to expand...
Click to collapse
Idk. I guess it depends on the ROM, and on what has happened between the release of the old version and the new version. If the new release of the ROM doesn't involve dramatic changes to the trees, then, perhaps formatting will not be required. You should follow the recommendations of the ROM's developer.
By the way, I said nothing about wiping data. I referred to formatting data - which is a completely different thing.
DarthJabba9 said:
Idk. I guess it depends on the ROM, and on what has happened between the release of the old version and the new version. If the new release of the ROM doesn't involve dramatic changes to the trees, then, perhaps formatting will not be required. You should follow the recommendations of the ROM's developer.
By the way, I said nothing about wiping data. I referred to formatting data - which is a completely different thing.
Click to expand...
Click to collapse
what i wanted to know was if i had to format the data partition (like we do for clean flashing to a different ROM) for dirty flashing
What about Pixel experience Recovery?
Which one better for PE rom ( lineage OS or PE recovery)
Abdullah.Csit said:
What about Pixel experience Recovery?
Which one better for PE rom ( lineage OS or PE recovery)
Click to expand...
Click to collapse
PEX has their own recovery? Is there a link or does the ROM install it while being flashed?
CV2000 said:
PEX has their own recovery? Is there a link or does the ROM install it while being flashed?
Click to expand...
Click to collapse
Well when hit note 9s on their site you will see two download links one for rom and the other for recovery ?!
Abdullah.Csit said:
Well when hit note 9s on their site you will see two download links one for rom and the other for recovery ?!
Click to expand...
Click to collapse
Bro, checked it out. They have used LRTWRP.
CV2000 said:
Hey guys, I have a few questions regarding the recovery, any help is appreciated.
1>Which Recovery did you flash?
2>Can you dirty flash roms(to update the ROM from one ver. to another) in it?(Because i read that the data must be cleared after flashing any rom)
3>Which ROM and recovery are you on?
4>Are there any special methods you need to follow to flash?
Thanks in advance :good:
Click to expand...
Click to collapse
I started with the Russian twrp by wszx150 but have also used pbrp, twrp by mauronofrio (most likely to become official twrp for curtana), and I'm now using Orange Fox Alpha (admittedly for its good looks). Every version has its own strengths and weaknesses so it really depends on what you want to do.
For instance, most (or all) TWRP versions cannot decrypt data partition after you change ROMs hence format data is mandatory before you switch (from encrypted) roms.
AFAIK only lineage twrp supports adb sideload,
Pbrp, lwtrp, and the aforementioned twrp by wszx150 are basically same in terms of functionality.
Most work well for backup and restore...
Mtp file transfer doesn't work in Orange Fox (i can overlook that as it is in Alpha stage).
What I'm saying is don't try to get your mind fixed on just one. Such a Swiss Army knife doesn't exist (yet) for RN9 pro.