TWRP problem
I'm using latest twrp-3.2.3-0 i face some issues regarding flashing aroma zip files.. when i faah the zip it doesn't fash & black the screen & back into twrp front screen without boot.. & i have to flash this again & again.. but faced same issue.. after some trying the flash process is flash..
I had this problem as well and I think there's a bug with the aroma installer. I gave up and downloaded stock gapps instead and learned to use gapps-config.txt file.
Install bitgapps instead
same
and i can't boot system
same problem
Related
i have a zenfone 501cg. Recently i flashed resurrection remix . After that when i try to flash Gapps its not working. The flashing is completing error free but when reboot there is no Gapps installed . I am pretty sure i have the correct Gapps package ( X86) . I also tried changing the rom but no change . Plz help
Thanks
Use the recovery from here (Credit goes to @X AnwarMov) . If you already use this version of recovery (Right now) and it fails then you may mount system partition manually before flashing Gapps.
If it also fails, you may also use the twrp 2.8.7.0 recovery from here (Credit goes to @quanganh2627)
i'm on a g900f and every Nougat rom i've installed(RR, CM/LOS, CRDroid) , it just freezes and puts my into a bootloop. BUT, this only happens when i flash gApps (2/02/17 7.1.1 nano)
I'm now back on CM13 and i just hope Android 8 will work properly.
anyone know how to fix?
nialloshea said:
i'm on a g900f and every Nougat rom i've installed(RR, CM/LOS, CRDroid) , it just freezes and puts my into a bootloop. BUT, this only happens when i flash gApps (2/02/17 7.1.1 nano)
I'm now back on CM13 and i just hope Android 8 will work properly.
anyone know how to fix?
I had same issue took 2 days to discover gapps was doing it. Boot into recovery, wipe Data,System,Cache, Delvik Cache. Install whatever Version Nougat 7.1.1 rom. Install Mini_Dynamic_GApps-7.1.x-20170121.zip. (Find download link on xda or Google it.) Do factory reset and reboot. I never had any problems after that. Once i put all my apps back anf settings, it was like it never happened. Good luck.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
-Flash rom
-Flash latest opengapps
-Flash su if u need it
-Flash this fix ( https://www.androidfilehost.com/?w=files&flid=150763 )
-Done enjoy....
for the next lineage build all freezes in setup has been fixed
So if you cant wait for the next build just flash the fix file..
Flash img?
Hi
I am using custom roms since a while and I also got into this freezing problem. Now I see this .img here. Just that I don't do anything wrong. How to flash and .img? Need Odin or is it possible in recovery mode? Sorry for the numb question here but could not find an answer hot to do on my Galaxy S5
Hi everyone,
I posted this thread in general troubleshooting category and after some advice, I decided to post it in the S4 section.
I was since 3 years on custom ROM (CM and Lineage OS) and due to substratum, I had a bootloop.
My problem is quite particular, after a total clean (wipe and format cache,system,data, dalvik cache) of my device and flashing the stock ROM, custom recovery cause me some trouble.
Whatever I try (CWM touch 6 or TWPR 3.1.1), I can't flash custom ROM (Lineage OS 14.1), TWPR or CWM crash 1 second after the flash command and reboot, with disable touchscreen and even by using old navigation way and try again, same problem.
Tried also to disable file signature check but no effect.
Quick summary about what I did:
- Device: Samsung Galaxy S4 (GT-I9505)
- ROM stock used: I9505XXUHOJ2 ( the build on which is based the CF-Root file I used) and Bulgarian version due to mistake.
- I tried on these two ROM with in the two cases, no patch or Samsung ROM update made.
- Tried to install CWM by ROM Manager and ODIN (v3.09)
- TWPR installed by TWPR App using file in .img and not the second option (tar.img) for LTE Internationnal Qualcomm.
-Checked the root before last attempt with root checker and it was ok.
- Made 4 times already the clean and Stock ROM flash to clean recovery and try another way to install it (never had error after recovery install).
Actually I'm on the OJ2 Rom with update and patch delivered by Samsung with classic method.
In advance thanks for your help and I really hope it's not too serious.
By the way, sorry for my english, it's not my native language
Try flashing the stock ROM from sammobile.com or updato.com, don't root, use Odin 3.07 to flash the tar version of TWRP 2.8.7, try flashing a custom ROM.
Thx for the help/advice
Just to be sure, my stock ROM is actually from up updato.com but due to the patch and Samsung update I'm now on HPK2.
Here the detail of my stock ROM
https://image.noelshack.com/fichiers/2018/05/4/1517503670-screenshot-2018-02-01-17-43-00.png
(the integrated image link option made it as large as the moon so I prefer a simple link)
TWPR 2.8.7 is still efficient or another version would be better ?
If yes, I will try in the hour and I will give you news as soon as possible
EDIT: After some research, TWPR 2.8.7 jfltexx is not avaible in .tar , only .img and impossible to find it on net...
But 2.8.6 and 2.8.4 are avaible in .tar and 3.0.0 in .img.tar , which one is the best ?
I suggested 2.8.7 because Ihave used it in the past and it was very stable. Try a newer tar version. It's really just to see if the phone will take TWRP and boot it.
Whatever I try (TWRP 3.0.0 and 3.0.1 in .img.tar for jlftexx)
Odin (v3.07) do the job , my phone reboot as normal.
But when I shutdown it and lauch in recovery by manual way, got during a micro seconds the android logo of loading and intant "No commands " and I end on the stock recovery.
Edit: I will try the same method with Odin using CWM tar (never had problem with it before this day)
Same thing with CWM-v6.0.4.7-Touch-GT-I9505.tar
Android loading logo and "No command detected"
Problem solved
Well, I don't know how I made a sucess but it seems the "wild" method worked.
So here is the list of things I did in case somepne got the same trouble
Put your Zip file on SD AND Internal Memory (in case)
All the Zip files I used where on my internal storage during this procedure.
- Download mode:
uncheck Auto Reboot in Odin
flash TWRP3.0.1.0 jlftexx.img.tar with ODIN in admin mode
turn off device after flash ended
Obligation or the stock recovery will return automatically !
Lauch device in recovery mode:
If it's TWRP good news, slide to confirm modifications.
Recovery mode:
-Wipe --> Advanced Wipe--> Select Cache, Dalvik Cache, Sytem and Data (never check internal and SD storage)
I tried by mistake without wiping dalvik cache, and got no boot after 5 minutes so i made it again with all the wipe above
-Install --> Flash zip of the rom and Gapps (got an error at zip signature check on the ROM so I flashed after uncheck this option)
-Reboot --> System
Let your device launch on the new rom, set the basic parameters and after, if you want, return in recovery to flash the SU addon for root (got also zip sugnature fail so I ahd to uncheck it again)
Hoping no one will ever had the same problem but in case, I share my solution
Thanks again for help
I'm new to this device and already I'm extremely confused. I tried flashing TWRP the old school method and found out very fast that it was a no go. Upon reading around, I fount the following guide and booted TWRP:
https://forum.xda-developers.com/mi-a1/how-to/lineageos-gapps-magisk-twrp-dolbyatmos-t3762939
The problem? I can install DotOS, but as soon as I try to flash the GAPPS, I get an error (it claims that I am on 7.1.2, but I'm using the latest DotOS version which is 8.1.0 based). Since from what I understand the recovery seems to be tied to the boot.img (like the Sony Ericsson Xperia Play), I believed simply rebooting into recovery would help. Unfortunately this boots into stock recovery for 8.0.0 (mind you I was on 8.1.0 stock). Upon reading around on how to install TWRP on the phone itself, I found this thread:
https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472
This is the bigger headache. After following the instructions which are clear as day, I encounter similar issues to half of the replies in that thread. Another issue is that there is no explanation on whether you should be on stock first or...? Secondly, nothing is said on which "slot" (a or b) to flash your desired rom. So my default slot was b, I switched to a to flash the TWRP installer and so on as per instructions. I then assume I am to switch back to slot b for my rom to be installed. The issue is that after trying to install the GAPPS, I am faced with the issue again of the 7.1.2 detected. The only way to get around this is to flash it in slot a, but then the device will never boot. I'm very confused?
Use this twrp. Then you flashed twrp, wipe, install ROM, reboot into recovery again and flash gapps.
Crossvxm said:
I'm new to this device and already I'm extremely confused. I tried flashing TWRP the old school method and found out very fast that it was a no go. Upon reading around, I fount the following guide and booted TWRP:
https://forum.xda-developers.com/mi-a1/how-to/lineageos-gapps-magisk-twrp-dolbyatmos-t3762939
The problem? I can install DotOS, but as soon as I try to flash the GAPPS, I get an error (it claims that I am on 7.1.2, but I'm using the latest DotOS version which is 8.1.0 based). Since from what I understand the recovery seems to be tied to the boot.img (like the Sony Ericsson Xperia Play), I believed simply rebooting into recovery would help. Unfortunately this boots into stock recovery for 8.0.0 (mind you I was on 8.1.0 stock). Upon reading around on how to install TWRP on the phone itself, I found this thread:
https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472
This is the bigger headache. After following the instructions which are clear as day, I encounter similar issues to half of the replies in that thread. Another issue is that there is no explanation on whether you should be on stock first or...? Secondly, nothing is said on which "slot" (a or b) to flash your desired rom. So my default slot was b, I switched to a to flash the TWRP installer and so on as per instructions. I then assume I am to switch back to slot b for my rom to be installed. The issue is that after trying to install the GAPPS, I am faced with the issue again of the 7.1.2 detected. The only way to get around this is to flash it in slot a, but then the device will never boot. I'm very confused?
Click to expand...
Click to collapse
To install twrp, use twrp 3.2.3 from abishek (lineageOS) or from cosmicdan.
This phone have slot a/b. For installing twrp it doesn't matter from which slot you install as it will install in the boot partition, not in system.
First do facory reset, you don't have to be on stock.
For custom rom zip if you are in slot a it will be installed in the slot b. After installing rom install twrp again as it's deleted when you install new rom and change slot, reboot and install gapps according with the rom 8.1 or 9.0 and magisk, it installs on the same slot..
Cosmicdan twrp have an option to install rom zip on the same slot and have a survival option for twrp, so you don't have to install twrp when you install a rom or a new kernel.
ccalixtro said:
Use this twrp. Then you flashed twrp, wipe, install ROM, reboot into recovery again and flash gapps.
Click to expand...
Click to collapse
This is the link for twrp:
https://forum.xda-developers.com/mi-a1/development/treble-twrp-installer-treble-manager-t3793637
Reboot recovery after u flash rom, then flash gapps,magisk
i'm running stock january frimware with no root or any thing and wanna flash aosip 9.0,when i flash twrp 3230 i have working touch . and when i flash jan_twrp_root.img based on daze one toturial i lose my touch in twrp so i decided to start instructions for installing custom roms with twrp 3.2.3.0 because i have touch on it. after flashing rom i flashed twrp-installer.zip and after rebooting to recovery i did not have touch to flash gapps and when i change to the another slot after flashing twrp installer i have twrp working so did it and change the active slot with fastboot after that in twrp < reboot< change slot to the other i mean were the rom installed and doing gapps and magisk.zip rebooting to the system but i do not have touch in system and can not do nothing in lets go screen. testing the process with RR and Aosip rom and having the same results.
any suggestion?tnx in advanced
Not to hijack but I have a bonestock phone that is neither rooted and the bootloader is locked. Had a bad screen, replaced with two different screens. Both turn on no issue but zero touch. Super frustrated, flashed latest OTA and nothing.
had this issue, i couldnt have touch on one rom but the others worked, i used the adb recommended in the stock rom files thread (think this was the problem for me) but i ended up reverting back to stock with magisk, the roms are stable but have some issues and i didnt find it a plus of having a rom with essential, i did installed helix engine for the app optimization