Ok, I'm running Resurrection Remix on the Qualcomm Chipset. I have 3.2.0 R1 version of TWRP. I tried to install Xposed when it said it couldn't install because the /system was Read Only. I had tried everything... Any help would be appreciated, Thanks
codyalan said:
Ok, I'm running Resurrection Remix on the Qualcomm Chipset. I have 3.2.0 R1 version of TWRP. I tried to install Xposed when it said it couldn't install because the /system was Read Only. I had tried everything... Any help would be appreciated, Thanks
Click to expand...
Click to collapse
in the mount section unselect read only and tick mount system and flash .zip framework again
like so ..then you can flash it
Did that, like 2000 times...
do this
mount -o rw,remount /system
within the twrp terminal mode.
Francesco Franz said:
do this
mount -o rw,remount /system
within the twrp terminal mode.
Click to expand...
Click to collapse
Tried this twice, got two different responses...
codyalan said:
Tried this twice, got two different responses...
Click to expand...
Click to collapse
you need to correct mount flags in recovery.fstab within the recovery ramdisk.
---------- Post added at 08:54 AM ---------- Previous post was at 08:53 AM ----------
codyalan said:
Tried this twice, got two different responses...
Click to expand...
Click to collapse
or use another twrp recovery.
from Ressurection rom zip file works fine.
Francesco Franz said:
you need to correct mount flags in recovery.fstab within the recovery ramdisk.
Click to expand...
Click to collapse
How would one go about doing this?
codyalan said:
How would one go about doing this?
Click to expand...
Click to collapse
you could try installing systemless xposed from within magisk .....
if not your other option under advanced tab select terminal and run this command
“mount -t ext4 /dev/block/bootdevice/by-name/system /system”
* if that doesn't work get another recovery *
KevMetal said:
you could try installing systemless xposed from within magisk .....
if not your other option under advanced tab select terminal and run this command
“mount -t ext4 /dev/block/bootdevice/by-name/system /system”
* if that doesn't work get another recovery *
Click to expand...
Click to collapse
Yeah have Xposed systemless already, but command doesn't work either, not sure if any other recovery for our phones... Would formatting data fix this?
codyalan said:
Yeah have Xposed systemless already, but command doesn't work either, not sure if any other recovery for our phones... Would formatting data fix this?
Click to expand...
Click to collapse
well if your problem is mounting system formatting data wouldn't necessarily fix it ..what kind of error do you get when trying to mount system from terminal ? try posting a screenshot of recovery output and terminal output error when you try mounting system ..i don't know if there are any other recoveries for your variant
try flashing it via flash fire apk instead ..it might work
*out of interest *
i noticed you have twrp 3.2. ...the first recovery for moto e4 was 3.1...
i got this exact same error ..if you really MUST have latest recovery flash back to recovery version 3.1..
flash xposed zip ..flash back to recovery 3.2...
i went back to using recovery 3.1.... for mediatek due to a few errors in 3.2.... including error 1 above. didn't notice that before but there is definitely both a mtk and Qcom recovery version 3.1... ( old or first version ) available floating around the threads
codyalan said:
Yeah have Xposed systemless already, but command doesn't work either, not sure if any other recovery for our phones... Would formatting data fix this?
Click to expand...
Click to collapse
Instead of formatting /data, you can try going to /data/media/0/TWRP and delete the .twrps file and then boot to twrp and make sure you allow it to modify /system when it asks and try to flash Xposed again. Check for /data/media/TWRP also because sometimes you'll have both. Does this happen with other ROMs, or only RR? I don't think it has anything to do with wrong recovery mount flags.
Sent from my Moto E (4) Plus using XDA Labs
volatile1 said:
Instead of formatting /data, you can try going to /data/media/0/TWRP and delete the .twrps file and then boot to twrp and make sure you allow it to modify /system when it asks and try to flash Xposed again. Check for /data/media/TWRP also because sometimes you'll have both. Does this happen with other ROMs, or only RR? I don't think it has anything to do with wrong recovery mount flags.
Click to expand...
Click to collapse
Not sure if it happens with other ROMs, I'll try what you said and if that doesn't work I'll try another ROM
codyalan said:
Not sure if it happens with other ROMs, I'll try what you said and if that doesn't work I'll try another ROM
Click to expand...
Click to collapse
I forgot to ask if you were using the 3.2 TWRP and if it happened with 3.1 versions?
Sent from my Moto E (4) Plus using XDA Labs
volatile1 said:
I forgot to ask if you were using the 3.2 TWRP and if it happened with 3.1 versions?
Click to expand...
Click to collapse
Yeah.. should I install 3.1 and see if mounts as r/w?
codyalan said:
Yeah.. should I install 3.1 and see if mounts as r/w?
Click to expand...
Click to collapse
It can't hurt to try. It also can't hurt to get a recovery log after the failed flash with 3.2 and post it and mention your problem in the recovery thread if it doesn't happen with 3.1.
Sent from my Moto E (4) Plus using XDA Labs
Edit : Deleted
Related
Preambula:
When Grif_07 compiled his CM, as a result he got a new version of the CWM.
The CWM text color changed to blue.
After the flash you will get a cyclic reboot CWM, as is the case with the installation of CWM by means of Rom Manager.
Functions not tested. So it is not responsible for the performance. Solely for testing purposes.
How to install:
Flash in recovery.
Ambula:
thanks to Grif_07 and ketut.kemujaya we have fully working CWM 5.0.2.6.
Download here.
Proof
I'll try, maybe the boot cyclic to CWM problem comes from the kernel that I could fix or you can try to flash back the boot image (boot.img) after flashing the recovery image. I have an experience even using a fixed kernel I got boot cyclic and resolved by flash back the boot image.
ketut.kumajaya said:
...that I could fix.
Click to expand...
Click to collapse
It would be great!
If only I was good at this :/
Forever living in my Galaxy Ace using XDA App
ketut.kumajaya said:
you can try to flash back the boot image (boot.img) after flashing the recovery image.
Click to expand...
Click to collapse
It does not help with bootloop on this version CWM(
P.S. flash this CWM and try to make a backup - get error when backup boot.img(
Flash back to CWM 4... - bootloop, flash boot.img - normal boot.
Lovetz said:
It does not help with bootloop on this version CWM(
P.S. flash this CWM and try to make a backup - just error(
Flash back to CWM 4... - bootloop, flash boot.img - normal boot.
Click to expand...
Click to collapse
That means you got CWM v5 ?
Forever living in my Galaxy Ace using XDA App
EmoBoiix3 said:
That means you got CWM v5 ?
Click to expand...
Click to collapse
I flash it, but got a bootloop, and flashback to CWM 4.0.0.9.
EmoBoiix3 said:
That means you got CWM v5 ?
Click to expand...
Click to collapse
No, but he can back to CWM4 without bootloop
ketut.kumajaya said:
No, but he can back to CWM4 without bootloop
Click to expand...
Click to collapse
I am preparing to compile new CM build right now. What I need to change in sources for CWM5 bootloop fixing?
Grif_07 said:
I am preparing to compile new CM build right now. What I need to change in sources for CWM5 bootloop fixing?
Click to expand...
Click to collapse
I think the fix is in kernel. Give me time to fix above CWM5 shared by Lovetz.
ketut.kumajaya said:
I think the fix is in kernel. Give me time to fix above CWM5 shared by Lovetz.
Click to expand...
Click to collapse
Ok... Then I am starting to compile... Maybe a new version of CWM will built to.
Grif_07 said:
I am preparing to compile new CM build right now. What I need to change in sources for CWM5 bootloop fixing?
Click to expand...
Click to collapse
Apply this fix
https://github.com/PabloPL/android_...mmit/46e96915a7e0459dc6b3aec04aa47329371fff44
To return from recovery, our kernel need to call reboot with recovery_done option.
(you can test this - while in CWM5, try to run reboot recovery_done, you should back to Android).
Fixed using CF-Root's CWM4 kernel (a kernel with a patched pm2.c, thanks to ilarrain) and add 2 lines command to init.rc to load jbd2 and ext4 modules.
For CyanogenMod 7.1 and advance user only for now!
How to flash:
- Boot your device into CWM recovery
- Push recovery-clockwork-5.0.2.3-galaxyace.img to your device using "adb push recovery-clockwork-5.0.2.3-galaxyace.img /tmp/" command
- Login to your device over "adb shell"
- Mount /system using "mount /dev/block/stl12 /system" command
- Flash CWM recovery using "flash_image recoveryonly /tmp/recovery-clockwork-5.0.2.3-galaxyace.img" command
- Umount /system using "umount /system" command
- Reboot your device using "reboot recovery" command to test your new CWM recovery
- Reboot your device
Not fully tested and have no enough space to try the backup/restore function
EDIT:
Recovery flashable zip added.
EDIT2:
Please try the *-fix.zip version.
Changelog:
- mount, umount, and rm scripts taken from my CF-Root-S5830 CWM to fix mount error problem
- /etc/recovery.fstab changed to mount /sd-ext partition and to fix recovery backup problem
EmoBoiix3 and Lovetz, waiting for your report
EDIT3:
The fix version almost same as clockwork-5.0.2.6 I have modified before and shared here by Grif_05, except:
- remove a garbage file
- ext4 support compiled in kernel, not as a module
- using new Samsung proprietary modules taken from DXKPD
ketut.kumajaya said:
Fixed using CF-Root's CWM4 kernel (a kernel with a patched pm2.c, thanks to ilarrain) and add 2 lines command to init.rc to load jbd2 and ext4 modules.
For CyanogenMod 7.1 and advance user only for now!
How to flash:
- Boot your device into CWM recovery
- Push recovery-clockwork-5.0.2.3-galaxyace.img to your device using "adb push recovery-clockwork-5.0.2.3-galaxyace.img /tmp/" command
- Login to your device over "adb shell"
- Mount /system using "mount /dev/block/stl12 /system" command
- Flash CWM recovery using "flash_image recoveryonly /tmp/recovery-clockwork-5.0.2.3-galaxyace.img" command
- Umount /system using "umount /system" command
- Reboot your device using "reboot recovery" command to test your new CWM recovery
- Reboot your device
Not fully tested and have no enough space to try the backup/restore function
recovery-clockwork-5.0.2.3-galaxyace.img (4.89 MB)
Click to expand...
Click to collapse
I'll flash this image and see whether backups work . Will edit this post .
EDIT: Error while backing up recovery image . Backup stops .
Edit2: This CWM doesn't support mounting /sd-ext
Edit3: Restore works though .
ketut.kumajaya said:
EDIT:
Recovery flashable zip added.
Click to expand...
Click to collapse
1. When try to make backup:
Backing up boot image...
Backing up recovery image...
Error while backing up recovery image!
Click to expand...
Click to collapse
2. After boot in to CWM /cache and /sdcard are already mounted.
3. When try to wipe cache
wiping cache....
Formatting /cache...
Cache wipe complete.
Click to expand...
Click to collapse
4. But in log:
Formatting /cache...
I:Formatting unknown device.
mount: mounting /dev/block/stl14
on /cache failed: Invalid argument
W:failed to mount /dev/block/stl14 (File exists)
rm: can`t remove '.' or '..'
rm: can`t remove '.' or '..'
Cache wipe complete.
mount: mounting /dev/block/stl14
on /cache failed: Invalid argument
W:failed to mount /dev/block/stl14 (File exists)
Click to expand...
Click to collapse
Please try the (still not sure) fixed version: recovery-clockwork-5.0.2.3-galaxyace-fix.zip
ketut.kumajaya said:
Please try the (still not sure) fixed version: recovery-clockwork-5.0.2.3-galaxyace-fix.zip
Click to expand...
Click to collapse
Ketut, I have 5.0.2.6 version. Do you need it?
Grif_07 said:
I have 5.0.2.6 version.
Click to expand...
Click to collapse
Upload here, why not?
ketut.kumajaya said:
Please try the (still not sure) fixed version: recovery-clockwork-5.0.2.3-galaxyace-fix.zip
Click to expand...
Click to collapse
Backup works fine now . Thanks a lot ketut !
I even have the CF-Root indication :3
Lovetz said:
Upload here, why not?
Click to expand...
Click to collapse
because it has bootloop and not working backup.
Hi guys, I'm trying to flash a kit kat ROM coming from purity 4.3, but when in recovery and trying to flash the zip it says
Symlink:some symlinks failed
E: error executing updater binary in zip,,,,
What's going on?
Sent from my Nexus 10 using xda app-developers app
filthygoat223996 said:
Hi guys, I'm trying to flash a kit kat ROM coming from purity 4.3, but when in recovery and trying to flash the zip it says
Symlink:some symlinks failed
E: error executing updater binary in zip,,,,
What's going on?
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
What TWRP Version are u using? make sure u are on latest I thinks it's 2.6.3.1... here's linkg for the latest .img file http://techerrata.com/browse/twrp2/manta
or try the goomanager app.
if that fails u might have to use CWM.
Good Luck
Reboot recovery and unmount /cache partition. That worked for me
I could really use help with this as well. so many different issues. Sometimes its status 7 some symlinks failed, sometimes its just some symlinks failed, and sometimes its error in updater. I need help! Tried so many different things. My TWRP is up to date, ive downloaded the rom and gapps several times with all the same results, and High on Android said to open up the rom and change some of the script with a text editor and ive done that and rezipped the rom and flashed and still gotten errors. OMG please help
Worked for me
bidzapfc said:
Reboot recovery and unmount /cache partition. That worked for me
Click to expand...
Click to collapse
Thank you. This helped me install the 4.4 liquidsmooth beta.
bidzapfc said:
Reboot recovery and unmount /cache partition. That worked for me
Click to expand...
Click to collapse
Thanks a lot, that worked for me as well
I believe that the latest TWRP versions have resolved this.
bidzapfc said:
Reboot recovery and unmount /cache partition. That worked for me
Click to expand...
Click to collapse
Thanks it worked for me tooo.
dint work for mee
i cant install aospextended rom :crying:
eternityhacker said:
Thank you. This helped me install the 4.4 liquidsmooth beta.
Click to expand...
Click to collapse
bidzapfc said:
Reboot recovery and unmount /cache partition. That worked for me
Click to expand...
Click to collapse
thanks, that worked for me in moto xt1058 , rom stock mod debloated
how to
bidzapfc said:
Reboot recovery and unmount /cache partition. That worked for me
Click to expand...
Click to collapse
how to unmount /cache partition?
dickydicky77 said:
how to unmount /cache partition?
Click to expand...
Click to collapse
veirdly that worked for me too.
bidzapfc said:
Reboot recovery and unmount /cache partition. That worked for me
Click to expand...
Click to collapse
done, great job it helped me thanks
Hey guys, it's me again In the last few months I dont active much on this anymore, now I'm back
Here is the latest rec for our beloved device:
https://drive.google.com/file/d/0B5ePoKNP9UFtM1R5MW1vdjFGOGc/view?usp=sharing
How to use:
Code:
fastboot flash recovery twrp-z1-2860.img
Changelog:
v2.8.6.0:
Nothing much, just add support for Z1 and F2FS
Bugs: The image/icon may look weird because I have to compress all icon to make room for new update....Limited space for us to "hack" it...
You tell me
This thread will be main support for TWRP to use with CM/CM-based rom or maybe stock rom too by me...Stay update
I will update it ASAP when new TWRP version come out....
P/S: "TekCafe" is just the name of my support group...If you guys not like it, I will make another without that name....
Tested on AICP 9.0
Click "Thanks" if you find it useful...
Thanks. Everything is working perfectly we just seem to have 2 home buttons now. The 1 home button functions like the back button so it's just cosmetic
LSD DREAMER said:
Thanks. Everything is working perfectly we just seem to have 2 home buttons now. The 1 home button functions like the back button so it's just cosmetic
Click to expand...
Click to collapse
I compress and reuse all the icon so you may find broken artifact icon, duplicated,...It's just cosmetic, every function work just as fine....
BlackSoulxxx said:
I compress and reuse all the icon so you may find broken artifact icon, duplicated,...It's just cosmetic, every function work just as fine....
Click to expand...
Click to collapse
It all works fine it even looks the same just the 2 home buttons. Not complaining just thought I'll share
Hi!
Will this TWRP work with stock 4.4.4?
I´m on UB.
Best regards
C_Karhu said:
Hi!
Will this TWRP work with stock 4.4.4?
I´m on UB.
Best regards
Click to expand...
Click to collapse
You should install NUT XZDR...:fingers-crossed::fingers-crossed::fingers-crossed:
Sorry, I didn't make myself clear. I'm interested in the F2FS. My kernel has support, but I can't format system to it. Will this TWRP format stock 4.4.4 to full F2FS?
Best regards
Is it compiled from source or repacked from Sirius?
o-l-a-v said:
Is it compiled from source or repacked from Sirius?
Click to expand...
Click to collapse
You already answer that question.....
Does the latest CM12 nightly support F2FS already?
Hi,
I've changed /system and /cache successfully, but I cannot convert /data to f2fs. Formats to ext4 correctly, but even after I formatted ext4, rebooting to recovery and formatting it to f2fs fails.
Code:
Formatting Data using mkfs.f2fs...
E:Unable to wipe '/data'.
E:Unknown MTP message type: 1
E:Error changing file system.
Updating partition details...
I have unlocked bootloader, Xperia Z1 (c6903 honami) running 5.1 with Resurrection Remix 5.4.1 kernel and ROM. I have not encrypted device.
Thoughts?
FIXED! I was able to format it by using terminal from TWRP and typing
Code:
mkfs.f2fs /dev/block/platform/msm_sdcc.1/by-name/userdata
then I rebooted device into recovery to update partition table, then Wipe > Repair/Change Filesystem > Data
Code:
current file system: f2fs
Yay!
kentexcitebot said:
Hi,
I've changed /system and /cache successfully, but I cannot convert /data to f2fs. Formats to ext4 correctly, but even after I formatted ext4, rebooting to recovery and formatting it to f2fs fails.
Code:
Formatting Data using mkfs.f2fs...
E:Unable to wipe '/data'.
E:Unknown MTP message type: 1
E:Error changing file system.
Updating partition details...
I have unlocked bootloader, Xperia Z1 (c6903 honami) running 5.1 with Resurrection Remix 5.4.1 kernel and ROM. I have not encrypted device.
Thoughts?
FIXED! I was able to format it by using terminal from TWRP and typing
Code:
mkfs.f2fs /dev/block/platform/msm_sdcc.1/by-name/userdata
then I rebooted device into recovery to update partition table, then Wipe > Repair/Change Filesystem > Data
Code:
current file system: f2fs
Yay!
Click to expand...
Click to collapse
Tks!:fingers-crossed::fingers-crossed::fingers-crossed:
Up...............
guys help me pls. i flash the recovery by fastboot but when press volume - not enter in recovery why is? obviously i have unlocked the boot
axelgrox said:
guys help me pls. i flash the recovery by fastboot but when press volume - not enter in recovery why is? obviously i have unlocked the boot
Click to expand...
Click to collapse
+1... same problem!
axelgrox said:
guys help me pls. i flash the recovery by fastboot but when press volume - not enter in recovery why is? obviously i have unlocked the boot
Click to expand...
Click to collapse
There could be 2 reasons: one, you are not properly flashing, as you need to do
fastboot flash recovery "name of file": second, if you have kernel with TWRP integrated, the two will collide resulting in no recovery at all...
Hi
Does it work for stock android 5.0.2 build .270 ?!
Thank you
Does this work 14.6.A.0.368
I have been trying to reflash this, however when I try to boot in to TWRP all I get is the fastboot mode on my phone which doesn't allow me to do anything. I recently just uninstalled MultiRom for the same reasons, but now since I have removed MultiRom I cannot get into TWRP at all. Does anyone have any ideas?
File doesn't exist anymore
Trying to flash a custom ROM, actually, when flashing pretty much all ROMS with 3.0.2, I get the following error: "mount: Failed to mount /dev/block/mmcblk0p39 at /cust: Device or resource busy" I believed this didn't pose a problem, since all ROMs had flashed fine, or so I thought, until I tried to flash one of HTCMania's customs and it had to change the system font, but didn't. Any ideas as to why this may be happening? Or how can this be fixed?
KillerDam said:
Trying to flash a custom ROM, actually, when flashing pretty much all ROMS with 3.0.2, I get the following error: "Failed to mount /dev/block/mmcblk0p39 at /cust: Device or resource busy" I believed this didn't pose a problem, since all ROMs had flashed fine, or so I thought, until I tried to flash one of HTCMania's customs and it had to change the system font, but didn't. Any ideas as to why this may be happening? Or how can this be fixed?
Click to expand...
Click to collapse
i have same problem in twrp,but with data,i have fix that by flash stock recovery,from stock recovery i have made wipe data factory reset and wipe cache and he work,it might work for you,so give a try
cristi.blidariu said:
i have same problem in twrp,but with data,i have fix that by flash stock recovery,from stock recovery i have made wipe data factory reset and wipe cache and he work,it might work for you,so give a try
Click to expand...
Click to collapse
How did you flash the stock recovery?
KillerDam said:
How did you flash the stock recovery?
Click to expand...
Click to collapse
By fastboot,and command is fastboot flash recovery recovery.img
cristi.blidariu said:
By fastboot,and command is fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Nope, didn't work, still can't mount cust partition, even after factory reset using stock recovery. I can only think about pushing the rom through sideload, but can't seem to figure out how. I'm about to give up and just return to Lollipop
KillerDam said:
Nope, didn't work, still can't mount cust partition, even after factory reset using stock recovery. I can only think about pushing the rom through sideload, but can't seem to figure out how. I'm about to give up and just return to Lollipop
Click to expand...
Click to collapse
Did you try to flash files via fastboot,or you try to restore your backup via twrp?
cristi.blidariu said:
i have same problem in twrp,but with data,i have fix that by flash stock recovery,from stock recovery i have made wipe data factory reset and wipe cache and he work,it might work for you,so give a try
Click to expand...
Click to collapse
cristi.blidariu said:
Did you try to flash files via fastboot,or you try to restore your backup via twrp?
Click to expand...
Click to collapse
Was trying to flash a ROM via TWRP, ROM flashes, but not correctly, since system font and other assorted things remain unchanged, and they should change.
KillerDam said:
Was trying to flash a ROM via TWRP, ROM flashes, but not correctly, since system font and other assorted things remain unchanged, and they should change.
Click to expand...
Click to collapse
K,wich rom?
cristi.blidariu said:
K,wich rom?
Click to expand...
Click to collapse
I have the same problem while trying to install sokkoban's rom from huaweip8lite blogspot.
After the error message extracting system hangs. After forced restart twrp recovery cannot boot again. Had to debrick my phone. :\
aelfwine88 said:
I have the same problem while trying to install sokkoban's rom from huaweip8lite blogspot.
After the error message extracting system hangs. After forced restart twrp recovery cannot boot again. Had to debrick my phone. :\
Click to expand...
Click to collapse
Edit:
I think this is caused by the install script doesn't unmount /cust mountpoint before trying to access it.
aelfwine88 said:
Edit:
I think this is caused by the install script doesn't unmount /cust mountpoint before trying to access it.
Click to expand...
Click to collapse
Do you have any idea how can it be fixed? Maybe which line could be missing or wrong and what would the correct syntax be.
cristi.blidariu said:
K,wich rom?
Click to expand...
Click to collapse
Nautilus ROM, and maybe Sokkoban's KangVIP iirc
KillerDam said:
Nautilus ROM, and maybe Sokkoban's KangVIP iirc
Click to expand...
Click to collapse
sorry for late answer,Nautilus rom is base on hw/eu location with build number C432B564,you need to flash location https://mega.nz/#!aB9kUDST!q_mT6cq9uEQjvscnbXBZq3B1X6BWsMk7iYKaDjfFzJU flash with twrp,then try to install Nautilus rom,for @sokkoban KangVIP you need chinese location,well i don't have that location you should search your self
KillerDam said:
Do you have any idea how can it be fixed? Maybe which line could be missing or wrong and what would the correct syntax be.
Click to expand...
Click to collapse
I think you need to unmount /cust before you start to work with it. I checked the original Chinese rom which was it converted from and those guys are unmounting all mountpoins in the beginning of the install script (META-INF\com\google\android\updater-script):
Code:
ifelse(is_mounted("/data"), unmount("/data"));
ifelse(is_mounted("/system"), unmount("/system"));
ifelse(is_mounted("/cust"), unmount("/cust"));
This goes before the "ui_print("Formatting cust...");" line.
Sokkoban doesn't do it in his script so I thing that should be the problem.
I just switched my location to cn the other day and tried to install the new KangVIP B569. It went well, but i couldn't figure out how to install gapps (and I needed my phone live again...) so I switched back sokoban's modded KangVIP B564 version which has the same error during install. But it didn't stucked this time at extracting system and I guess it flashed /cust fine as well. And that was at 3am and I did not have the spirit to try to fix the script and flash again... Anyway you can try the code above but I suggest to switch location to cn and go for the latest KangVIP B569 or sokoban's KangVIP B564 (and you can try the script fix before flash). If you go with KangVIP B569 and you can figure out how to install gapps to please share.
If you stuck with location switching or don't know how to get official cn 6.0 android (also requirement for the modded 6.0) drop me a message and I try to recollect how I done that.
Good luck.
Hey guys question. Ever since yesterday for some reason anything i try to install will not boot. I have tried different roms and cant figure it out. any help would be appreciated. this is my only phone.
What have you tried, what model?
If you used Dirty Santa , I've seen a lot of people able to fix boot issues by following this step in his guide
me2151 said:
*****VERIZON USERS******
It has come to my attention that some users have encountered abnormally long first boot time(over 20 minutes before first time setup)
To resolve this issue:
Boot into bootloader by pulling the battery and reinserting it and holding VOL- and phugging in the phone. then typing:
Code:
fastboot flash boot boot2.img
fastboot reboot
**************
Click to expand...
Click to collapse
TGtheImmortal said:
What have you tried, what model?
If you used Dirty Santa , I've seen a lot of people able to fix boot issues by following this step in his guide
Click to expand...
Click to collapse
I have tried about 4 different roms and completely wiping and installing. the only thing that works is re flashing my stock backup i made after i rooted. I will try flashing boot2. Do roms change boot images when you flash? I am on the verizon verient.
pcwizkid1994 said:
I have tried about 4 different roms and completely wiping and installing. the only thing that works is re flashing my stock backup i made after i rooted. I will try flashing boot2. Do roms change boot images when you flash? I am on the verizon verient.
Click to expand...
Click to collapse
I'm not sure if you should flash the boot if you're on a custom rom. I am no expert so I don't want to make you brick your device.
Full wipe including formatting data when you are reinstalling custom roms?
TGtheImmortal said:
I'm not sure if you should flash the boot if you're on a custom rom. I am no expert so I don't want to make you brick your device.
Full wipe including formatting data when you are reinstalling custom roms?
Click to expand...
Click to collapse
Yes sir.
pcwizkid1994 said:
Yes sir.
Click to expand...
Click to collapse
Are you getting any errors whilst flashing custom roms?
The only thing I can think of right now would be following the steps from step 4 and reinstall and root a stock Verizon rom to see if it fixes your issue.
If that doesn't work someone else will have to come along and suggest some things.
TGtheImmortal said:
Are you getting any errors whilst flashing custom roms?
The only thing I can think of right now would be following the steps from step 4 and reinstall and root a stock Verizon rom to see if it fixes your issue.
If that doesn't work someone else will have to come along and suggest some things.
Click to expand...
Click to collapse
No nothing. Everything is flashing like it should.
Are /system and /data mounted in TWRP under mount before/after you flash a custom rom?
TGtheImmortal said:
Are /system and /data mounted in TWRP under mount before/after you flash a custom rom?
Click to expand...
Click to collapse
Now I am getting a system mount error when I try to back up my stock Rom... Will check when on break at work
TGtheImmortal said:
Are /system and /data mounted in TWRP under mount before/after you flash a custom rom?
Click to expand...
Click to collapse
Cach and data are the only things mounted
pcwizkid1994 said:
Cach and data are the only things mounted
Click to expand...
Click to collapse
/system definitely needs to be mounted before flash and after flash as well, otherwise it cannot override your stock rom.
Are you getting an error while trying to mount it? Or only during backup procedure? I was able to fix some mounting issues by simply rebooting TWRP.
TGtheImmortal said:
/system definitely needs to be mounted before flash and after flash as well, otherwise it cannot override your stock rom.
Are you getting an error while trying to mount it? Or only during backup procedure? I was able to fix some mounting issues by simply rebooting TWRP.
Click to expand...
Click to collapse
Ok so i went back into recovery and the only way I can get system to be cheacked is if I mount it as read only
TGtheImmortal said:
/system definitely needs to be mounted before flash and after flash as well, otherwise it cannot override your stock rom.
Are you getting an error while trying to mount it? Or only during backup procedure? I was able to fix some mounting issues by simply rebooting TWRP.
Click to expand...
Click to collapse
Hey. I emailed you back. Did you get my pm? Thanx