Im using derpfest rom for a week then last night i tried a different kernel but i didnt like it so i tried to restore my back up rom which is the latest then delete lockscreensettings.db on data/system so i can open the phone without my pin then restart my phone and i got stucked on boot animation. I tried to clean wipe then install again the latest build but again stucked at boot animation then tried to restore my back up, now im facing error when it comes to restoring the data see the picture i uploaded.
Even i try to flash older build i got stucked on boot animation. I cant even delete some files on my internal storage somebody help me. I dont have a pc to send a log
Related
I've unlocked bootloader, tried to flash new rom and now i got stuck at rom's logo. I just can wait forever and nothing happenes.
Tried to wipe, and even format everything (data/cache/system) and nothing.
Tried CM10.1 i a zip, ExperiencedStock as a backup, and even my own backup i've made before.
Everytime i got stuck at rom's logo.
I dont know how to put my phone in SW Update mode since i got CWM, and every time CWM starts and i cant flash it with LG support tool because the program doesnt see my phone.
Did anyone had this problem?
Maybe stock Recovery.img would help? Anyone could give me it? I can try to flash it again with fastboot mode.
Or any other sugesstions?
karaczan said:
I've unlocked bootloader, tried to flash new rom and now i got stuck at rom's logo. I just can wait forever and nothing happenes.
Tried to wipe, and even format everything (data/cache/system) and nothing.
Tried CM10.1 i a zip, ExperiencedStock as a backup, and even my own backup i've made before.
Everytime i got stuck at rom's logo.
I dont know how to put my phone in SW Update mode since i got CWM, and every time CWM starts and i cant flash it with LG support tool because the program doesnt see my phone.
Did anyone had this problem?
Maybe stock Recovery.img would help? Anyone could give me it? I can try to flash it again with fastboot mode.
Or any other sugesstions?
Click to expand...
Click to collapse
Try hard/factory reset ; turn off your phone , hold vol- & home ,press and hold power for couple of seconds
With vol-,home & power it also boots to CWM :/
Have you trying to restore stock rom via Cwm? You can download fresh one from our forum.
Go to advanced and clear dalvik cache it might help
Wysyłane z mojego LG-P760 za pomocą Tapatalk 2
Yes, tried fresh CWM backups also.
But finally i solved this problem
Dont know why, but when i formatted internal sd, rom booted with no problems.
Firtstly i didnt want to format internal sd because there was my backup in case something goes wrong.
But it went wrong, so i had nothing to loose
So if anybody will have this problem then format everything (cache/data/system/internal_sd, wipe Dalvik), then restore backup or install zip from sd_ext.
ExperiencedStockFinal booted ok, backup made on sd_ext also.
Will now try to install CM10.1, and maybe i'll investigate why i have this bootloop bug on my phone.
First off I am on mdk and rooted and up until today have been running hd 10.2. I had been having some weird things happen with twrp 2502 so I went into goo and tried to update to the newest version of twrp. it downloaded and went through with everything and I rebooted into recovery. once I got into recovery it was showing I was still on 2502, but it was asking for a password which I had never seen before. I backed out and tried to boot into my rom again and it got stuck on the samsung custom screen. pulled the battery a few times and still kept getting stuck. went back into recovery and tried to restore a known good backup that I had restored before, but it keeps failing. I had rls12 on my phone so I tried installing it dirty since I cant wipe anything due to the whole password thing in twrp which said it was succesful but still gets stuck on the samsung custom screen. it sits there for about 10 seconds and loops. I tried about 10 more times to get my backup restored and it finally finished and booted into the rom. I left it this way for an hour or so and did some stuff with my phone, tried to update twrp again which did the same thing again and still shows 2502. after the reboot I am back to the same problem of not being able to do anything in twrp except restore or dirty flash, I cant get the usb to mount in twrp so I cant try putting another rom on the phone unless I go and buy a micro sd adapter.
I am in the process of downloading a stock mdk rom to try and flash in odin, but is there anything I can try before I go through with this, or is it pretty much my only option.
after some more research I think I figured out what caused all this. I wiped the data partition with the old version of twrp which screwed it up pretty bad. Apparently the older versions of twrp were known to have this problem. I kept trying to restore, but trying to restore kept failing on the data partition. After about 25 attempts of trying to restore just the data partition I was able to get it to work finally, and then I restored the the others and got it to boot back into the rom. like an idiot I rebooted the phone back into recovery after it finished and had the same problem again. another couple hours wasted trying to restore the data partition and it worked again and this time i was able to get twrp to update and then went back to recovery and formated the data partition again and it seems to have fixed the problem. Now to figure out why hd rls 12 wont install.
Hi I have a SM-N910F model which is proving extremely difficult to flash. I firstly flashed the latest Marshmallow UK BTU firmware on it which resulted in a boot loop. I cleared cache partition and wiped data/factory reset in the stock recovery (and TWRM recovery) but this did not fix the problem. So I flashed the phone again and this time it was stuck in a boot loop with the text "recovering booting..." at the top left. Tried the same as before and still didnt fix it.
So I then tried a different stock rom - Lollipop UK BTU firmware. This gave me the exact same problems as before. However on a few occasions, I also got an error on the recovery screen saying cache could not be mounted. I cleared the cache partition, tried reformatting cache using TWRM but none of this worked. Eventually I reflashed and it went away but the boot loop doesnt go.
Lastly I tried an even older firmware - Kitkat UK BTU firmware. This again gave me a boot loop problem. It also kept displaying the cannot mount cache error as well. I tried using PIT file to repartition the device and eventually the error went but the device would still be on boot loop. However on two occasions the phone did go past the Samsung logo and show the first setup screen (where you select initial settings like Wifi etc). After like 10-15 seconds it would just switch off and then go back into boot loop. I havent managed to get to the first setup screen again.
I have tried flashing with various different Odin versions but still no luck.
I feel like I have exhausted my options and not sure what to do. Do you think I should try a custom rom? If so, for the sake of getting it to start, which is a good lightweight rom?
Does anyone know what I can do to make these infinite boot loops and/or "cannot mount cache" error go away?
Anyone? I could really do with some help..
I think you have problem with motherboard, try to find original stock frimeware, by country. If not help try custom rom. I suggest any AOSP rom such as Lineage OS or CM.
Tried 3 different stock roms. Like I said it will either be in a boot loop, recovery loop, or give an cache mounting error. Im hoping that the motherboard is not faulty because it is not always the same problem
Hi , I think is because You have FRP (Factory Reset Protection) On which means you can't flash property your phone .
What U can try is to extract recovery.img from latest stock firmware for your Region .
Now use this script to transform recovery.img to recovery.tar.md5
here is how to do :
https://forum.xda-developers.com/showthread.php?t=2446269
Put your phone in download mode click on AP: and choose recovery.tar.md5
After that click on Start .
If the flashing was OK , put again your phone in Download mode and flash completely the same firmware with original recovery.img inside it.
Good Luck
One guy from forums.androidcentral.com posted it work on sm-n910t, Android 6.0.1 .
hey guys just looking for some help. ive been modding and flashing phones from 2014, but its always gone really smoothly, so my diagnostic ability is lacking.
it started with flashing twrp. my bootloader is unlocked, usb debugging on, device is showing in adb and fastboot, and i can flash twrp without any issues. hoowever when i go to boot twrp, only the stock recovery boots. i tried to flash twrp using the XiaoMiTool v2, but the same thing happened. i eventually got around this by just booting twrp instead of trying to flash it. so i got in, took a full back-up and started installing a custom rom.
the first one i tried was ParanoidAndroid Quartz. i wiped cache, dalvik and storage then transferred it to my phone, tried to flash and got "zip verification failed". so i turn off zip verification and tried again. it flashed perfectly with zero errors. however, when i reboot the phone it would only boot to stock recovery and not twrp (expected) or the new rom. i tried that a few times, then tried LineageOS, and MSM Xtended 10. all of them had the same issue, the flashed without a hitch, then wouldnt boot.
i also tried flashing a new fw-vendor and it just straight up failed. Then i decided to cut my losses and restore my twrp backup, and that came back with the error, "extractTarFork() process ended with error: 255"
Software before i began these attempts was completely stock, so i dont know what is going wrong, but as of now, my phone is bricked, i cant install a new rom or restore my back-up.
any help is appreciated guys. thanks
You can figure out this problem with
1 Copy backup folder to computer
2- Format Data - Yes , Wipe Everything
3- Install ROM that you have installed before and boot
4- Go to TWRP, format data yes reboot recovery
5- Paste backup folder to internal storage and restore
So I created a full backup of my device using TWRP and now just tried to restore it and it's just completely messed up my device. I got an error saying extracttarfork() process ended with error=255. My device was a custom timurs rom which I dont remember how to go through the whole process again. From the videos I have seen apparently I need to reflash it. How do I do that? What files do I need? Can someone please help
So, although the message logs shows that it formatted and wiped the system, I just thought i would give it a restart and see if I get a bootloop. But it seems to have not done anything of such like deleting or wiping because the system is still the same. However, I did notice my bootanimation logo has gone back to the version before the backup. So I don't know what exactly has happened.
Is it possible on TWRP to do a clean fresh install and then flash the Timurs Kernel rom back on? My tablet is in fix mode and I don't really have access to the volume buttons to force TWRP easily. So I'm thinking I would like to do a clean android refresh and flash the kernel again.
It's definately messed something up because now when I try to transfer a file into the System partition using TWRP i get error saying Full SELinux support is present. This never happened before. Any ideas please on how I can just start fresh on this?