Related
Hi,
I notice many users still use TWRP 2.6.3.3 as apposed to the latest build which is often highlighted by several ROM providers.
Hypothetical question....would a nandroid backup created in a newer version say 2.8.4.0 be recognisable to an older version like 2.6?
Fairly confident it would work in reverse but wondered if the backup build process would affect a recovery if I reverted to an older version which was a better version for flashing certain ROMS?
I guess it could be an" if it aint broke dont fix or change it" scenario ,,but the loyalty to the older version seems fairly common and something I have considered downgrading to if it is more relaible?
Shepps
shepppster said:
Hi,
I notice many users still use TWRP 2.6.3.3 as apposed to the latest build which is often highlighted by several ROM providers.
Hypothetical question....would a nandroid backup created in a newer version say 2.8.4.0 be recognisable to an older version like 2.6?
Fairly confident it would work in reverse but wondered if the backup build process would affect a recovery if I reverted to an older version which was a better version for flashing certain ROMS?
I guess it could be an" if it aint broke dont fix or change it" scenario ,,but the loyalty to the older version seems fairly common and something I have considered downgrading to if it is more relaible?
Shepps
Click to expand...
Click to collapse
it takes all of 10 seconds to change recovery so it's not a big deal. I have been using 2.8.4.0 since it came out and have had no problems.
and yes all versions of TWRP have always been backwards compatible
Hi everyone
I recently updated to B609 and (as expected) my phone was un-rooted.
I decided it would be better for me to just install a ROM instead of waiting for a new way to ROOT every time a new OTA comes out. (I have seen some very interesting ones that include Xposed)
This would be the first time i install a ROM on one of my phones but i do know how to use custom recovery's and i will always keep a copy of a backup close so i can flash back when something goes wrong.
A problem i have with starting all of this: I can't seem to find a way to unlock the Bootloader on my phone.
I have looked online but i always get links for older versions/other phones/German stuff.
Second problem: The recovery. As far as i understand, there is no working TWRP for EMUI3.0. BUT there should be a working CMW recovery. Should i go fot CMW?
Third problem: Which ROM? There are 3 that grabbed my attention. Se7en-Rom (But it seems like it hasn't been updated in a while), My-RoM (which seems the most interesting for me at the moment) and Miui (which i just found out about). Which should i go with or should i use another one? I can already say that i want my phone Rooted and Xposed is something i would love to have back (since i used to have it on my previous phone).
Any advice and help would be appreciated
JellyFox said:
Hi everyone
I recently updated to B609 and (as expected) my phone was un-rooted.
I decided it would be better for me to just install a ROM instead of waiting for a new way to ROOT every time a new OTA comes out. (I have seen some very interesting ones that include Xposed)
This would be the first time i install a ROM on one of my phones but i do know how to use custom recovery's and i will always keep a copy of a backup close so i can flash back when something goes wrong.
A problem i have with starting all of this: I can't seem to find a way to unlock the Bootloader on my phone.
I have looked online but i always get links for older versions/other phones/German stuff.
Second problem: The recovery. As far as i understand, there is no working TWRP for EMUI3.0. BUT there should be a working CMW recovery. Should i go fot CMW?
Third problem: Which ROM? There are 3 that grabbed my attention. Se7en-Rom (But it seems like it hasn't been updated in a while), My-RoM (which seems the most interesting for me at the moment) and Miui (which i just found out about). Which should i go with or should i use another one? I can already say that i want my phone Rooted and Xposed is something i would love to have back (since i used to have it on my previous phone).
Any advice and help would be appreciated
Click to expand...
Click to collapse
I have a P7-L10 with B609. I was able to successfully root it with RootGenius. When you root it, the bootloader is unlocked at the same time. As far as I can tell, the root is 100%. As for CWM, you can get it from here:
http://forum.xda-developers.com/ascend-p7/development/mods-tweaks-kernels-recoverys-emui-2-3-t2966670
TWRP doesn't work with B609/emui3.0.
My L10 has faulty flash memory and won't accept a custom recovery, so I can't test CWM or any custom ROMs. Perhaps others can advise. Good luck!
arthios said:
I have a P7-L10 with B609. I was able to successfully root it with RootGenius. When you root it, the bootloader is unlocked at the same time. As far as I can tell, the root is 100%. As for CWM, you can get it from here:
http://forum.xda-developers.com/ascend-p7/development/mods-tweaks-kernels-recoverys-emui-2-3-t2966670
TWRP doesn't work with B609/emui3.0.
My L10 has faulty flash memory and won't accept a custom recovery, so I can't test CWM or any custom ROMs. Perhaps others can advise. Good luck!
Click to expand...
Click to collapse
RootGenius was the first thing i tried. It went up to 66% then i got an error but that was a fully Chinese version.
I just tried it again with the one i found by using Google and it goes up to 72%, then tells me that the root has failed.
Which version did you use?
This is what I used and it worked fine (root genius): http://forum.xda-developers.com/showthread.php?t=2789337
As for bootloader, as far as I know from, starting with firmware 133 (Emui 2.3) all devices have unlocked bootloader
CWM is the only custom recovery for the moment;
Did not try any custom ROM (I'm happy with stock ROM for the moment).
Cheers
ibeqa said:
This is what I used and it worked fine (root genius): http://forum.xda-developers.com/showthread.php?t=2789337
As for bootloader, as far as I know from, starting with firmware 133 (Emui 2.3) all devices have unlocked bootloader
CWM is the only custom recovery for the moment;
Did not try any custom ROM (I'm happy with stock ROM for the moment).
Cheers
Click to expand...
Click to collapse
That's the first one i tried out. The first few times it ended in an Error. I tried it again today and when my phone reboots during the process, RootGenius loses contact with my phone.
And there is a bootloader-ish thing, but the only options i have is reboot, factory reset and cache wipe.
JellyFox said:
That's the first one i tried out. The first few times it ended in an Error. I tried it again today and when my phone reboots during the process, RootGenius loses contact with my phone.
And there is a bootloader-ish thing, but the only options i have is reboot, factory reset and cache wipe.
Click to expand...
Click to collapse
Hmmm, strange problem. Assuming you have the latest version of HiSuite installed and your drivers are current, all I can suggest is trying again with RootGenius (I used version 1.8.7) with your firewall and antivirus disabled or perhaps trying with Vroot. If you do decide to try Vroot it probably won't work unless you disable your firewall and antivirus.
arthios said:
Hmmm, strange problem. Assuming you have the latest version of HiSuite installed and your drivers are current, all I can suggest is trying again with RootGenius (I used version 1.8.7) with your firewall and antivirus disabled or perhaps trying with Vroot. If you do decide to try Vroot it probably won't work unless you disable your firewall and antivirus.
Click to expand...
Click to collapse
I disabled my firewall and antivirus and gave RootGenius another try. Normally it goes up to 71% and gives me the error. Now it went to 71%, rebooted and then it gave me the error. The weird part is that right before i get the error, it says the installation is complete.
Moved on to Vroot (which is called Iroot now apparently) . It took a while longer but it wasn't able to do it either.
JellyFox said:
And there is a bootloader-ish thing, but the only options i have is reboot, factory reset and cache wipe.
Click to expand...
Click to collapse
Get in bootloader mode, if your bootloader is unlocked, it will be written and highlighted with red color. I will point out again, starting with firmware B133 (Emui 2.3) all bootloaders for L10 version (I don't know for Chinese versions) are unlocked
Cheers.
update to b615 and flash or just flash this >> http://forum.xda-developers.com/ascend-p7/development/b615-unlocked-boot-img-t3050926 and use rootgenius remove inmutable etc...
btw there is twrp for emui 3 which mostly work fine http://forum.xda-developers.com/showpost.php?p=59340975&postcount=208
Z!L0G80 said:
update to b615 and flash or just flash this >> http://forum.xda-developers.com/ascend-p7/development/b615-unlocked-boot-img-t3050926 and use rootgenius remove inmutable etc...
btw there is twrp for emui 3 which mostly work fine http://forum.xda-developers.com/showpost.php?p=59340975&postcount=208
Click to expand...
Click to collapse
I still didn't get the OTA for B615 yet but thank you for the recovery.
ibeqa said:
Get in bootloader mode, if your bootloader is unlocked, it will be written and highlighted with red color. I will point out again, starting with firmware B133 (Emui 2.3) all bootloaders for L10 version (I don't know for Chinese versions) are unlocked
Cheers.
Click to expand...
Click to collapse
You were right! (not that i every doubted you). I found the problem i had: For some reason, i couldn't boot in bootloader trough my phone BUT i was able to do it with 'adb reboot bootloader'. After making some idiotic mistakes and having to re-flash the stock ROM, I finally was able to install My-RoM v3.3, its rooted, i have Xposed so i am happy
So thank everyone for the help!
Hello,
I got my G2 two days ago (used), i come from an htc one m7, i use to unstall all kinds of custom roms and recoveries, but scrolling through this forum i can't seem to understand the best way to install TWRP and rom the phone.
WHAT I HAVE :
- verizon LG G2 completely stock non rooted, software verison 3AA
WHAT I WANT :
-install latest TWRP to be able to install custom roms like cm13
WHAT I DON'T UNDERSTAND :
-Some tutorials mention something about flashing bootstacks, others tell me to root then install twrp directly using some app
-i presume that my software version 3AA is greater than 39A, the latest bootstack is made for 39A so will it cause a problem if i flash that bootstacks ?
all explanations will be appreciated
NVM i figured everything out
I've got this new OnePlus 3t A3003. I'm happy with the performance battery and everything but there's this one issue that troubles me. I got the device unlocked bootloader and flashed aospa. Everything was nice and smooth then I flashed SuperSU later. The phone got reset and wiped except for the internal storage. I didn't know what to do and I just left it. Then later I came across some audio mods and tried flashing it again the same thing happened. So I tested and came to the conclusion that flashing anything wipes device. Why does this happen?
What versions TWRP and SuperSU? Just a guess, but maybe an older version with some compatibility issue? Try another version TWRP?
Otherwise, what version firmware? I don't know if AOSPA updates firmware (as some ROMs do). Maybe try to update OOS to current version 4.1.6 and start with fresh firmware, and install current version TWRP again, etc.
My phone is encrypted so what happens is I flashed something then the phone boots and asks for the password to unlock first then after entering it resets. I didn't know why I even switched roms rn using resurrection remix 7.1.2 latest version and still same problem.So im pretty sure the problem isn't with the rom. Twrp is latest version afaik and with rr rom magisk comes so I'm on v12 of magisk. I'll try using another version of twrp and oos.
redpoint73 said:
What versions TWRP and SuperSU? Just a guess, but maybe an older version with some compatibility issue? Try another version TWRP?
Otherwise, what version firmware? I don't know if AOSPA updates firmware (as some ROMs do). Maybe try to update OOS to current version 4.1.6 and start with fresh firmware, and install current version TWRP again, etc.
Click to expand...
Click to collapse
Thanks mate, there was something wrong with the twrp version I had. I flashed the latest version of twrp 3.1.1 I think and that seemed to solve the issue.
The other problem i have is when i try to flash bluesparks twrp and go to recovery the sceen is blank and only the led glows but i can flash the officaial twrp and flash roms but they come with error 7 and when i flash a oxygen os it gets stuck in updating system image
ak_bagade said:
but i can flash the officaial twrp and flash roms but they come with error 7 and when i flash a oxygen os it gets stuck in updating system image
Click to expand...
Click to collapse
Error 7 often means you are trying to flash an Oreo ROM with an older version TWRP which does not support Oreo.
But we can't tell from the info provided by you. Always give version numbers and other details for TWRP (and blu_spark TWRP) you are having trouble with, as well as the ROMs you are trying.
Also, make sure you are using the right TWRP and ROMs for 3 versus 3T (another reason for Error 7).
redpoint73 said:
Error 7 often means you are trying to flash an Oreo ROM with an older version TWRP which does not support Oreo.
But we can't tell from the info provided by you. Always give version numbers and other details for TWRP (and blu_spark TWRP) you are having trouble with, as well as the ROMs you are trying.
Also, make sure you are using the right TWRP and ROMs for 3 versus 3T (another reason for Error 7).
Click to expand...
Click to collapse
its the latest bluesparks
ak_bagade said:
its the latest bluesparks
Click to expand...
Click to collapse
I said: always give a version number. "latest bluesparks" isn't a version number. I can't count how many times I've seen folks claim they flashed the "latest" recovery. And when prompted for more info, we find out that they aren't even close, sometimes flashing a version TWRP from 2 years ago or older! Not saying this is necessarily your case. But we don't know for certain, if you don't give us precise and accurate info to work with.
You also said you flashed official TWRP. What version number exactly?
You also need to tell us what custom ROMs (and versions) you tried to flash. And what version OOS did you try to flash?
Some friendly advice, try to take more than 5 seconds to type a response to questions we ask you. Provide as much detail as possible, and answer all the quesions. For that matter, when asking for help, posting 2 or 3 (poorly typed) sentences is rarely enough info to go on. Again, provide as much detail and specific info as possible.
this is mostly an outdated firmware issue, Always make sure you have the latest firmware for your device
Firmware 4.5.1/nougat/3T
Firmware 4.5.0/nougat/3
or you can try the Oreo ones
(Stable)
Firmware 5.0.0/Oreo/3T
Firmware 5.0.0/Oreo/3
(Open Beta)
Firmware OB20/Oreo/3T
Firmware OB29/Oreo/3
OP3T firmware thread https://forum.xda-developers.com/oneplus-3t/how-to/firmware-modem-collection-flashable-zips-t3565535
OP3 firmware thread https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
redpoint73 said:
I said: always give a version number. "latest bluesparks" isn't a version number. I can't count how many times I've seen folks claim they flashed the "latest" recovery. And when prompted for more info, we find out that they aren't even close, sometimes flashing a version TWRP from 2 years ago or older! Not saying this is necessarily your case. But we don't know for certain, if you don't give us precise and accurate info to work with.
You also said you flashed official TWRP. What version number exactly?
You also need to tell us what custom ROMs (and versions) you tried to flash. And what version OOS did you try to flash?
Some friendly advice, try to take more than 5 seconds to type a response to questions we ask you. Provide as much detail as possible, and answer all the quesions. For that matter, when asking for help, posting 2 or 3 (poorly typed) sentences is rarely enough info to go on. Again, provide as much detail and specific info as possible.
Click to expand...
Click to collapse
the bluesparks twrp which i flashed is 8.61 op-3t
and the official twrp which works is 3.2.1-0
so when i use the official twrp i have to remove the "assert" from the updater script and flash the rom or else i get the error 7
Something which has come up recently is that my homebutton/fingerprint sensor does not work (its like it doesnt exist) when i flash any rom from android 7-8.1.
So i came to stock by relocked the bootloader by the way like it happens when you hardbrick your device. now im in marshmallow.
Something you should know about is that i flash a lot of roms and locked and unlocked the bootloader a countless times and i think this has affected the files which might be related to the homebutton and fingerprint sensor .
The other funny thing is that when i called oneplus to help me with flashing the latest software there method helps me to get the bluesparks twrp but since i keep flashing i lose the twrp so thats the only way i can bliuesparks twrp
ak_bagade said:
Something you should know about is that i flash a lot of roms and locked and unlocked the bootloader a countless times and i think this has affected the files which might be related to the homebutton and fingerprint sensor .
Click to expand...
Click to collapse
Doesn't work like that, the home button, fp sensor "files" are not in TWRP, or managed by FW in any way. All of these are in the /system folder of the ROM that is installed. Which is why they don't work in TWRP.
Have you been on MM since you got this phone? If so, your firmware is heavily outdated, and that's why you end up with the White LED of Death. Try flashing the latest Open Beta over stock recovery. Make sure to unlock your bootloader first. Then flash any variant of TWRP you want, and then see if you still get the White LED of Death.
ak_bagade said:
Something you should know about is that i flash a lot of roms and locked and unlocked the bootloader a countless times and i think this has affected the files which might be related to the homebutton and fingerprint sensor .
Click to expand...
Click to collapse
You shouldn't be locking the bootloader if you are flashing custom recovery and custom ROMs, and you don't need a locked bootloader to flash official updates either. Really, there is no reason to lock the bootloader unless you are worried about security concerns; want a "full stock" conditions, etc. And for most xda users, an unlocked bootloader is going to be the highly preferable condition. Further, locking the bootloader requires be full stock (including stock recovery, not TWRP). And trying to lock the bootloader under any other condition, is asking for trouble.
I agree with the recommendation above, to flash the full zip of the Open Beta or official OOS update, which will put you on a fully "stock" baseline including firmware. Then go from there.
---------- Post added at 09:19 AM ---------- Previous post was at 09:07 AM ----------
ak_bagade said:
The other funny thing is that when i called oneplus to help me with flashing the latest software there method helps me to get the bluesparks twrp but since i keep flashing i lose the twrp so thats the only way i can bliuesparks twrp
Click to expand...
Click to collapse
If flashing the official zips with TWRP (including blu_sparks), you will always lose TWRP (overwritten with stock recovery) if you reboot after flashing the update. You can prevent this by flashing root (SuperSU, Magisk) or a custom kernel before rebooting (after the update).