Hello Freinds...
I'm facing a "some new" problem, and I really need your help
I have a C2005 with TWRP 3.0.2-0 and unofficial LOS 14.1 flashed on it, and everything was working fine.
Then, I decided to update the hosts file and get rid of some Google Apps with clean install -I always do clean installs from time to another-.
So, I edited the gapps-config file and created a flashable zip for the hosts file, rebooted into TWRP, Wiped everything (dalvik, system, cache, data, internal), flashed ROM, dual SIM patch, hosts file, and finally GApps -everything as usual-, then I rebooted into system, but this time, the device went into bootloop.
P.S: The only different thing this time is that I was using xposed module (GravityBox) to set navbar height to "0", and another module (xposed edge) to set some gestures, and I rebooted into recovery and wiped everything -as mentioned above- without deactivating those modules.
I tried to clean install the ROM zip only, in case there was something wrong with the zips I made, and even tried another ROM (PecanCM's AOSP 7), but nothing happened, still bootlooped...
Finally, and as final solution, I tried to begin from zero, so I flashed the stock ROM ftf with Androxyde Flashtool and the device booted successfully into system and worked very fine, then I reflashed TWRP with ADB ......., sideloaded LineageOS.zip (Followed the LineageOS installation steps explained in LineageOS Nicki Wiki step by step)........, but also Still bootlooped!!!!
P.S: Into the Install Zip page in TWRP, I noticed this message (this operation may install incompatible software and render your device unusual) for the first time, I do not know if it is normal or not.
Please, Any body know if there is any logical reason for this?, please help me :crying::crying:
Thanks in advance
Related
Hey,
I wanted to create an nandroid backup in TWRP and got error 255 in the process.
I got the log of the failed update:
cloud.directupload.net/dfZq
So i searched for a solution, and the internet said that i should remove the file wich causes backup to fail. The logs said it was '/system/app/AndroidPay'
This is a file, not a folder.
So i removed the file, keeping an backup of it, booted into TWRP and the backup still failed.
To my surprise the boot into OxygenOS fails now. It shows the Oneplus Powerd by Android logo, turns black and reboots into twrp. Recovery and Bootloader seems to work fine.
So I connected my device with my computer and tried to get the file back to '/system/app' using adb.
I tried 'adb push AndroidPay /system/app' and it seems to be transferred succesfully, however the boot into oxygenOS is still not working.
I think it can be fixed by formatting the device and flash OxygenOS new to it, but I really don't wanna do that.
General Information:
Oneplus 3
OxygenOS 3.3.4
Rooted
Xposed Installed
No custom kernal
TWRP 3.0.2-0
File wich may be broken: cloud.directupload.net/dfZs
Is there an easyer way than resetting my whole phone to get it to work ?
I'm sorry for language mistakes or maybe leaving relevant information.
Thank you for help
I've had same problem today, my solution is restore "System" part (only system) from old backup, it saved my data and OP3 works fine after that
Wipe system, then flash OOS and it should work fine. If it doesn't Im afraid you need to do a full clean install since it isn't system related then.
I had CM13 on my Oneplus 3, and saw that there was an update. Turns out it was for CM14 and it wiped out my recovery(after further googling, I found out that it's a known issue - http://forum.xda-developers.com/onep...icial-t3497425). So I flashed the custom TWRP recovery from that.
Then I proceeded to flash my last working update of CM13, and the ARM64 6.0 Nano GApps immediately after. I then wiped my dalvic cache and rebooted. It started booting up and the preparing apps screen started loading. But when it finished and I was at the phone setup screen(the screen you get when you first buy a phone and have to choose language, wifi etc), it shows me an error named - "unfortunately the process android.process.media has stopped one plus 3 boot"
I looked the error up online and all results are to go into settings and modify google sync settings, or delete gallery cache etc. But I never even get to reach that point to try it. I flashed CM14 and ARM64 7.1 Nano Gapps to see if maybe that would work, but got the same error. Then I downloaded the last snapshot from CM site with their recovery, but same error.
Can anyone please help me?
Metrotor said:
I had CM13 on my Oneplus 3, and saw that there was an update. Turns out it was for CM14 and it wiped out my recovery(after further googling, I found out that it's a known issue - http://forum.xda-developers.com/onep...icial-t3497425). So I flashed the custom TWRP recovery from that.
Then I proceeded to flash my last working update of CM13, and the ARM64 6.0 Nano GApps immediately after. I then wiped my dalvic cache and rebooted. It started booting up and the preparing apps screen started loading. But when it finished and I was at the phone setup screen(the screen you get when you first buy a phone and have to choose language, wifi etc), it shows me an error named - "unfortunately the process android.process.media has stopped one plus 3 boot"
I looked the error up online and all results are to go into settings and modify google sync settings, or delete gallery cache etc. But I never even get to reach that point to try it. I flashed CM14 and ARM64 7.1 Nano Gapps to see if maybe that would work, but got the same error. Then I downloaded the last snapshot from CM site with their recovery, but same error.
Can anyone please help me?
Click to expand...
Click to collapse
Go back to TWRP --> FULL WIPE (also internal storage - save needed files on your pc before wiping) --> Clean installation of the favourited rom and you should be fine.
LS.xD said:
Go back to TWRP --> FULL WIPE (also internal storage - save needed files on your pc before wiping) --> Clean installation of the favourited rom and you should be fine.
Click to expand...
Click to collapse
I wiped everything except internal memory. And although it gave me some error, I was able to reflash CM13 and Gapps to get the phone working again. Thank you so much!
Hi,
I wanted to update my Pixel C to the most current factory image with flashfire as i did it before a few times without problems.
So I DL'd current factory image from https://developers.google.com/android/images#ryu, opened it in flashfire and said it should flash the normal partitions except recovery as i don't want that it overwrites my TWRP.
Flashfire analyzed the zip file and after i said "flash" it restarted my Pixel into a black screen. At this point i was wondering that nothing more happened.
I waited for 10 minutes so that maybe something in the background could happen, but there was no further action. The screen kept black.
After these 10 minutes i restarted the device but now it always runs into TWRP directly instead of starting the system
I also tried to install the zip manually in TWRP but it tells me
"Could not find 'META-INF/com/google/android/update-binary' in the zip file.
Error installing the zip file '/usb-otg/ryu-n2g48c-factory-0bc0ee15.zip'"
As you can see from the error message i also tried to dl the file again and install it via OTG but the same thing.
If I go into the file manager in TWRP i can still access the folders from the sdcard.
The bootloader is unlocked of course.
Anyone an idea what i can do without loosing all the data?
Thanks in advance
Download the full system image and extract it. There should be a flash_all-file (bat for windows of sh for linux). Open it with an editor and remove the "-w" option in fastboot. "-w" is the switch for wipe. After you removed it, you can flash the complete image and your system should boot again into android. After that you can install a custom recovery, etc. again.
Thank you peter, worked like a charm for the system flash. Now follows the TWRP etc again
EDIT: ok, the system flash was the only thing that worked like a charm. I tried flashing TWRP with NRT but didn't work. I am stuck now at a "no command" screen when i start the device.
To install the custom recovery NRT tells me that i will loose all my data, so i wanted to backup everything.
Unfortunately i can't backup everything now as the temp booted TWRP demands a password to decrypt the sdcard, but i only have a pattern and no password set.
So now i try to flash everything again and to install twrp without loosing all the data.
Hey everyone I have flashed android 7.1.2 August again and android started afterwards without any problems. I was able to restore the backup of all the apps from Google.
Than I wanted to get back root and flashed TWRP with Nexus Root Toolset, but now only TWRP starts every time I switch on the tablet. Any ideas what I can do?
EDIT: I fixed it somehow with flashing the whole firmware package again and than the TWRP wich broke the startup again so i ended up in a TWRP bootloop. Therefore i flashed android again and TWRP 3.0.0.0 than TWRP 3.0.2.4 (something like that) and after like 3 to 4 different flashing steps it worked again. I have no idea what happened during the first flash of Andoir 7.1.2 but i think that something broke there.
Hello, I'm new here and I need help, let me explain...
I already have it unlocked with TWRP 3.2 (latest) with AEX rom, but I can't install any rom on it since I have some issues:
On TWRP:
When I try to install it can't mount /data and /cache. I have already tried to make them ext2 then ext4 and format data. System, Vendor and Firmware is mounting fine, just cache and data not.
On QFIL:
Tried to install stock rom via but is also not working, I don't know about those errors but also seem like permissions (maybe?). It finishes download, but when I start the phone still there AEX and nothing changed, stuck on the logo just loading...
* Logs -- https://pastebin.com/63L6cnwp
On MiFlash:
Installed everything ok but nothing happen, when start the phone still same.
My phone is Z2131, I have already tried Z2132 but none of them work.
Please help me ;c
So, I wanted to have Internal Audio Only option in my ScreenCam Screen Recorder App, and it say that it requires a Magisk module, so I managed to unlock bootloader and install TWRP Recovery in my device so I could root my device with Magisk. As I tried to root my phone with Magisk, it didn't work, so I look up in YouTube for some tutorials on how to do so. Then I watched a tutorial with a device that has a SuperSU if I'm correct, and I have made a confusion on my mind, looking for a tutorial for rooting my device with SuperSU, followed it and downloaded and installed a SuperSU from an unofficial source. After rebooting my device, I ended up with a bootloop. I tired reformatting my device with TWRP, it didn't work, I tried removing the battery and turning it on, it also didn't work. I tried erasing userdata, it didn't work as well. With only the TWRP Recovery, a laptop that I could only use on weekends and little knowledge of solutions for these type of situations, what should I do?
OkunionRingz said:
So, I wanted to have Internal Audio Only option in my ScreenCam Screen Recorder App, and it say that it requires a Magisk module, so I managed to unlock bootloader and install TWRP Recovery in my device so I could root my device with Magisk. As I tried to root my phone with Magisk, it didn't work, so I look up in YouTube for some tutorials on how to do so. Then I watched a tutorial with a device that has a SuperSU if I'm correct, and I have made a confusion on my mind, looking for a tutorial for rooting my device with SuperSU, followed it and downloaded and installed a SuperSU from an unofficial source. After rebooting my device, I ended up with a bootloop. I tired reformatting my device with TWRP, it didn't work, I tried removing the battery and turning it on, it also didn't work. I tried erasing userdata, it didn't work as well. With only the TWRP Recovery, a laptop that I could only use on weekends and little knowledge of solutions for these type of situations, what should I do?
Click to expand...
Click to collapse
Supersu is very old and will not work with modern roms - it will break safetynet too as it's not systemless
All you have to do is in twrp
On first install & run of twrp make sure you swipe to allow modifications to system
Goto wipe
Select format data (option on the right)
Reboot back to twrp
Goto wipe - advanced wipe
Wipe system data cache
Install rom zip eg lineageos 17.1
Flash gapps - for lineageos 17.1 select open gapps android 10 arm64 nano
Flash magisk from https://github.com/topjohnwu/Magisk/releases/
Wipe cache/delvik
Restart