I am running on oxygen os 3.1.3 rooted and twrp installed also I have xposed installed on my device. When I tried to uninstall xposed with uninstaller.zip it aborted displayin an error 255. And when I tried to install a new ROM(ressurection remix) again it ended displaying an error 7. Pls help me don't knw what to do..
Did u clean flash, wiping caches, system, and data 1st then installing a new rom, BC u can't dirty flash a cm rom on a oos rom, also did u download the file from ur phone or computer then move to phone, uninstalling or flashing a zip should not keep u from flash something else in twrp, try to restore ur nandroid backup too
Related
So I wanted to go to Lollipop and I happened to flash the twrp recovery for new layout(as i was getting boot loop when flashing the rom with cwm recovery)
The things i tried until now.
1. Installed twrp and formatted it to get the new layout. Wiped everything, system, cache, data, dalvik cache
2. It was supporting MTP so i transferred the roms to the device being in recovery. Installed CM 12 + gapps for lollipop.
3. Rebooted to bootloader again. flashed boot.img, and did fastboot erase cache.
4. Rebooted again and stuck at CM boot logo.
I wiped the cache, dalvik cache(actually did a factory reset in the twrp recovery) and tried installing Resurrection Remix. Again flashed the relevant boot.img too. But the same result..
Did i destroy my phone?
anoopknayak said:
So I wanted to go to Lollipop and I happened to flash the twrp recovery for new layout(as i was getting boot loop when flashing the rom with cwm recovery)
The things i tried until now.
1. Installed twrp and formatted it to get the new layout. Wiped everything, system, cache, data, dalvik cache
2. It was supporting MTP so i transferred the roms to the device being in recovery. Installed CM 12 + gapps for lollipop.
3. Rebooted to bootloader again. flashed boot.img, and did fastboot erase cache.
4. Rebooted again and stuck at CM boot logo.
I wiped the cache, dalvik cache(actually did a factory reset in the twrp recovery) and tried installing Resurrection Remix. Again flashed the relevant boot.img too. But the same result..
Did i destroy my phone?
Click to expand...
Click to collapse
can you enter in recovery ?
wipe dalik,chace,chace,data then go to,mount select system,chace,data,2gb extra data ,and disabel mtp
if your phone dot show up just leave it on select partions to mount ,unplug cable then plug it back,go to device manager btw and see will it show there
dado323 said:
can you enter in recovery ?
wipe dalik,chace,chace,data then go to,mount select system,chace,data,2gb extra data ,and disabel mtp
if your phone dot show up just leave it on select partions to mount ,unplug cable then plug it back,go to device manager btw and see will it show there
Click to expand...
Click to collapse
Yes I can enter recovery. But again I just cant get any lollipop ROM's working. I dont know whether i have to restore to kitkat(i really dont want too..
I dont get it.. Wipe dalvik cache, cache, data and then disable mtp and then enable mtp.. I mean at the end what does this do?
And in the meanwhile did you mean HTC Sync Manager for device manager. FYI I use a mac(if this helps to get into the problem). And i had flashed kitkat roms from the same without a hiccup but lollipop is failing
anoopknayak said:
Yes I can enter recovery. But again I just cant get any lollipop ROM's working. I dont know whether i have to restore to kitkat(i really dont want too..
I dont get it.. Wipe dalvik cache, cache, data and then disable mtp and then enable mtp.. I mean at the end what does this do?
And in the meanwhile did you mean HTC Sync Manager for device manager. FYI I use a mac(if this helps to get into the problem). And i had flashed kitkat roms from the same without a hiccup but lollipop is failing
Click to expand...
Click to collapse
its hard to explain with recovery you can mount ur sdcard and put another room and install ,the easy way its to start from the begin and install clear CM12 and you will get out from bootloop that help me i was in bootloop like 3920489208420984920 times hahaha
anoopknayak
Have you solve the bootloop issue? I am having the same problem on my International One X
thanks
Probably both of you encountered the same problem as me.
If you are S-on, you have to flash rom and kernel separately. Also, if you try to revert any changes with twrp you have to flash kernel you were using during creation of backup, and then restore backup.
In other words: your current kernel is incompatible with rom.
Mwys
Yes i am S-ON. Can you tell me what the steps are to flash the kernel? I do not have a backup.
What is did was flash New Layout TWRP, did a complete wipe, then copied the ROM and G-Apps zips to the phone, installed them and then flashed boot.img.
Thanks for the help
Yup I also tried the same. but no luck. I tried to revert back to kitkat(by installing cwm, format the storage, sideloaded the ROM and gapps, flashed the boot.img) and still again in bootloop.
Sorry for the delay. I was a lot too busy with work.
I have my OP3 rooted and bootloader open today I installed the newest version of Oxygen OS I installed the software throught TWRP but i forgot to wipe dalvik and the cache but surprise the boot back without problem but i went to install supersu from also TWRP said everything was installed ok and I restarted but now is on a bootloop I already wipe dalvik and cache several times and im not sure how to installe again stock recovery or even how I will be able to install Oxygen OS again, and i make it worse cause i used TWRP and did a full wipe and now is stuck on the 1+ logo, help please.
did u make a nandroid backup and/or did u make backups of apps with titanium backup or another app?
u may just have to do a clean flash, always make backups before doing any new install
no i didnt
Bradl79 said:
did u make a nandroid backup and/or did u make backups of apps with titanium backup or another app?
u may just have to do a clean flash, always make backups before doing any new install
Click to expand...
Click to collapse
jlrodriguez said:
no i didnt
Click to expand...
Click to collapse
oh no that was a rookie mistake, what i suggest is, clean flash unfortunately and start fresh, always always always make a nandroid backup, so did u get it working yet? or u can try to dirty flash and see if u just had a bad flash, just clear caches and install OOS full zip
Hello,
I don't know why my lg g3 phone doesn't want boot on custom rom.
I have the LG G3 d855 model, 16gb memory and here are my procedure to install every custom rom :
1. Flash Stock ROM using LGUP (the version of the firmware is not important but the possibility to root is)
2. Install KingRoot and get root
3. Install AutoREC and enter to the recovery
8. Flash Recovery TWRP 3.1.0-2
9. Reboot to the new recovery
10. ADVANCED WIPE (wipe cache, dalvik cache, data and SYSTEM)
11. Flash baseband 21C
12. Flash CUSTOM rom
13. Wipe cache and dalvik cache
14. Flash Gapp
15. Wipe cache and dalvik cache
16. Reboot
I think I did nothing bad...
but the phone does not start and it stays at the initial logo screen (not the LG logo, but the custom rom logo). I waited over 10 minutes to boot but nothing. Even though I install the identical rom again or install an anoter rom, each time the same issue.
This happens with all custom rom (xenonhd, resurrection remix, and now lineageOS)
I can use and boot on stock rom but each time I want to install a custom rom, my phone doesn't want to boot. The phone display stays at the initial rom logo screen.
It seems that I am alone to have this problem.
I don't know why and I search everywhere to find out the solution...
PS : My phone never restart by itself. I never have bootloop with my phone when I using stock rom and same with custom rom..
The problem is the boot with a custom rom. The phone don't want to boot and stay on logo loading...
Any suggestion may be help.
Thank you.
1. Once you installed TWRP you don't have to go back to stock to switch roms. From then on you can just download zips and flash them.
2. You need to delete everything (including system) except internal and external storage ( so you can still flash the zip for xceed, otherwise you will delete it). Remember that you will lose all your apps including your data with it. You can backup them with titanium backup tho. Pictures and video's will still be there as they are stored on the internal or external storage.
3. You also need to flash the GAPPS package after flashing rom, for xceed (7.1.1), pick nano (ARM)
4. Wipe cache and dalvik after flashing and reboot.
5. Make a backup before you do so !!!!!!
Good luck.
Jornwitt said:
1. Once you installed TWRP you don't have to go back to stock to switch roms. From then on you can just download zips and flash them.
2. You need to delete everything (including system) except internal and external storage ( so you can still flash the zip for xceed, otherwise you will delete it). Remember that you will lose all your apps including your data with it. You can backup them with titanium backup tho. Pictures and video's will still be there as they are stored on the internal or external storage.
3. You also need to flash the GAPPS package after flashing rom, for xceed (7.1.1), pick nano (ARM)
4. Wipe cache and dalvik after flashing and reboot.
5. Make a backup before you do so !!!!!!
Good luck.
Click to expand...
Click to collapse
Hello,
1. I think that but with specific rom, some people tell us to flash stock rom before flashing a custom rom. eMMC bug related ?
2. Deleting the system changes nothing because the system is wiped when I flash the rom, right ?
3. if the rom boot first then I will install Gapps. Else, I don’t install because the rom doesn’t want to boot.
1. Well .. I've been switching between fulmics,xceed,rr, .. etc without any problem so no, there is no need to go back to stock everytime.
2. Try it, you won't be able to boot until you flash a new rom, but it could help. That's why you take a backup in the first place. It is more 'clean' and if you don't try it you won't know.
3. Sometimes you have to flash gapps directly after the rom or you will be in for a bad time if you do afterwards.
Once you have TWRP recovery installed it's the easiest thing ever to flash a new rom. Make sure your zip files are downloaded okay. Download the MD3 to check it. Try to download via MEGA app or so, because browsers downloads tend to have errors sometimes.
Apart from that. Don't root via kingroot. They have had some suspicious cases where malware was installed on the phone when rooting.
If nothing's works. Go back to full stock through KDZ, root wit your PC, install TWRP via autorec, go to recovery, wipe everything, install modem 21C, install rom and gapps, wipe cache, reboot. Don't try anything other than that.
I have the same problem
Jornwitt said:
1. Well .. I've been switching between fulmics,xceed,rr, .. etc without any problem so no, there is no need to go back to stock everytime.
2. Try it, you won't be able to boot until you flash a new rom, but it could help. That's why you take a backup in the first place. It is more 'clean' and if you don't try it you won't know.
3. Sometimes you have to flash gapps directly after the rom or you will be in for a bad time if you do afterwards.
Once you have TWRP recovery installed it's the easiest thing ever to flash a new rom. Make sure your zip files are downloaded okay. Download the MD3 to check it. Try to download via MEGA app or so, because browsers downloads tend to have errors sometimes.
Apart from that. Don't root via kingroot. They have had some suspicious cases where malware was installed on the phone when rooting.
If nothing's works. Go back to full stock through KDZ, root wit your PC, install TWRP via autorec, go to recovery, wipe everything, install modem 21C, install rom and gapps, wipe cache, reboot. Don't try anything other than that.
Click to expand...
Click to collapse
Hello,
I have a question.
Can you give me a gapp 100% compatible with all custom rom with android 7.1.2, because i think opengapp are not reliable. Maybe the gapp will cause my issue and the rom won't boot.
Can i use this one https://forum.xda-developers.com/on...isited-slim-gapps-6-0-7-0-unofficial-t3462088 ?
I always use PICO version of gapp
Thank
Hi, i was using Mate 20 X GlobAL00ized 2.2 (EMUI 9.1 fw 120), in my little mind i just tried install the root, but without sucess, so i wiped everything, and now i cant acess the system, none of the roms are working. I tried install omnirom to root than back to the original rom, no sucess to acess the omnirom system, i can't Wipe data/factory reset because i get error after try this.
There is a way to install the stock system using TWRP?
I can't donwload the system using the erecovery too, if i try i got error connection :/.
Update: For some reason Omnirom wasn't able to acess the system, i solved installing the RR, so i was able to root, than install the official system.
Hi everyone,
I recently made a fresh install of the latest OOS ROM on my Onplus 5T (OOS 9.0.8). After reinstalling all the apps and data I tried to root the phone. My bootloader was already unlocked, so I just went on to flash TWRP (first tried the official TWRP 3.3.1 dumpling, and then the 3.3.1 blu_spark version). Then I tried to flash Magisk via TWRP (tried versions 19.2, 19.3, 19.4), and every time I try to reboot I get stuck on a black screen with the cyan led on, and I have to uninstall Magisk in order to reboot on the phone. Also the phone is encrypted, and I have a the Microsoft Intune Portal app installed to use some work apps, but I don't know if that can be the source of the problem.
If you have any idea on how to successfully flash Magisk, that would be amazing.
Thanks in advance :good:
I use the same version of ROM and magisk I use is canary build . Working fine. (even its not canary build I also can boot successfully)
you might need to check if some apps you install might cause this.
my recommendation is clear /data and starts fresh then root it before installing any apps. to see if it working fine or not.
also after you flash magisk do you try to wipe cache, dalvik-cache?
and how long are you waiting for its to boot? normally it would take more time than normal boot (without magisk)
Just connect to to ADB and delete vendor.. recovery.. rom.. radio.. antennaa.. ect everything. Get yourself a stock full rom and flash that through ADB. Then flash custom recovery, custom rom, gapps, custom kernel, magisk. thats it. find stock rom on manufacturers data server. I did this to a different phone I had but this is the way to 100% fix everything... by purging the phone to nothing. You can however do a twrp backup before doing so.
Thanks for the input, I will try first to reflash the ROM and root before installing any apps, and see if it works in order to avoid the long process of restoring all my data. I do wipe cache/dalvik cache before and after every flash. If that doesn't work I will try another time a clean flash and tell you if it worked.
I just reflashed the ROM and right after I flashed Magisk 19.3, then rebooted and it worked. Not sure what the issue was but the problem is now resolved. Thanks guys for the advice.