Related
RESOLVED
I ran the RUU for my phone, re-ran the update and am stable on 1.08.652.11 710RD
Original post:
I'm getting a consistent kernel crash on all kernels, stock, etc. after the latest HTC update for sprint-vm cdma. Basically, I can get any rom to boot, after about 10-30 seconds, kernel crashes causing the phone to reboot.
I've attached the dmsg log that contains the crash information.
I'm not sure what I can do to fix this issue, as it appears to be a firmware problem. Thoughts?
wendall911 said:
I'm getting a consistent kernel crash on all kernels, stock, etc. after the latest HTC update for sprint-vm cdma. Basically, I can get any rom to boot, after about 10-30 seconds, kernel crashes causing the phone to reboot.
I've attached the dmsg log that contains the crash information.
I'm not sure what I can do to fix this issue, as it appears to be a firmware problem. Thoughts?
Click to expand...
Click to collapse
Try stock kernel if that crashes then custom rom
Sent from my One V using xda app-developers app
cybervibin said:
Try stock kernel if that crashes then custom rom
Click to expand...
Click to collapse
Stock kernel and all custom roms, ICS and JB have the same exact result. This is why I'm suspicious that this was a bad firmware update. I've read several posts about spontaneous reboots, but most people don't know about dmesg, so I don't have anything to compare to.
wendall911 said:
Stock kernel and all custom roms, ICS and JB have the same exact result. This is why I'm suspicious that this was a bad firmware update. I've read several posts about spontaneous reboots, but most people don't know about dmesg, so I don't have anything to compare to.
Click to expand...
Click to collapse
Does it happen like this?
http://www.youtube.com/watch?v=IIqT-xd0AqU&feature=youtu.be
I have the same issue man. It's bizarre.
patbushnell said:
Does it happen like this?
I have the same issue man. It's bizarre.
Click to expand...
Click to collapse
Yes, this is the same behaviour. I'm not sure if you're able to dump the dmsg stuff from adb, but certainly same crash. Typically the phone network status shows a little x, right before the reboot. But the lagginess starts happening when the 5 second kernel reboot is issued.
I've tried to change to airplane mode, disable sdcard and everything else I can think of, still crashing and I'm not able to make much of the logging info
When you applied the OTA were you completely back to stock. Like locked bootloader and stock recovery?
sentfromybrain
aaronrw said:
When you applied the OTA were you completely back to stock. Like locked bootloader and stock recovery?
sentfromybrain
Click to expand...
Click to collapse
Yes, completely back to stock. Unfortunately, I didn't create a backup of the stock image that booted after the OTA update was applied I just restored pre-OTA rom, cwm recovery and boot.img. Everything appeared to be working fine after the update on the stock ROM. However, I didn't leave it on long enough to confirm if the crash issue existed then. Just checked the version info to confirm the update had been applied and rebooted.
UPDATE
I'm going to go through the process again with the RUU and see if I can boot something stable.
wendall911 said:
Yes, completely back to stock. Unfortunately, I didn't create a backup of the stock image that booted after the OTA update was applied I just restored pre-OTA rom, cwm recovery and boot.img. Everything appeared to be working fine after the update on the stock ROM. However, I didn't leave it on long enough to confirm if the crash issue existed then. Just checked the version info to confirm the update had been applied and rebooted.
UPDATE
I'm going to go through the process again with the RUU and see if I can boot something stable.
Click to expand...
Click to collapse
You will surely get the RUU to make your phone working perfectly. That's what I did.
patbushnell said:
You will surely get the RUU to make your phone working perfectly. That's what I did.
Click to expand...
Click to collapse
Confirmed RUU -> Update worked the second time. This is probably the safest method. This appeared to work initially, but clearly did not. Thanks for all the feedback!
I can't get any non-stock rom to boot after applying the OTA update. Well ok it boots but loops after about 10-15 seconds.
I have to RUU it and not apply the update to get any non-stock rom to work.
CDMA/VMUSA here.
---------- Post added at 09:24 PM ---------- Previous post was at 09:19 PM ----------
wendall911 said:
Confirmed RUU -> Update worked the second time. This is probably the safest method. This appeared to work initially, but clearly did not. Thanks for all the feedback!
Click to expand...
Click to collapse
So are you able to run any other roms without reboots? Or are you only on stock?
MasterTec said:
I can't get any non-stock rom to boot after applying the OTA update. Well ok it boots but loops after about 10-15 seconds.
I have to RUU it and not apply the update to get any non-stock rom to work.
CDMA/VMUSA here.
---------- Post added at 09:24 PM ---------- Previous post was at 09:19 PM ----------
So are you able to run any other roms without reboots? Or are you only on stock?
Click to expand...
Click to collapse
I applied the OTA update. Only the stock kernel (after update) will boot now. Any non-stock kernel crashes - always seems the last line is rmt_storage, which the IPC to shared memory of the boot loader I believe.
Noob question
wendall911 said:
Yes, completely back to stock. Unfortunately, I didn't create a backup of the stock image that booted after the OTA update was applied I just restored pre-OTA rom, cwm recovery and boot.img. Everything appeared to be working fine after the update on the stock ROM. However, I didn't leave it on long enough to confirm if the crash issue existed then. Just checked the version info to confirm the update had been applied and rebooted.
UPDATE
I'm going to go through the process again with the RUU and see if I can boot something stable.
Click to expand...
Click to collapse
Can you link me to a working RUU?
i got my one v primoc back in the beginning of summer, but then something fell on it and cracked the screen super bad but i loved the phone so much that i bought another at the end of october. i unlocked, wiped, and flashed JB roms... which seemed to work fine for a while & then would have issues of staying stuck in roaming. i've tried different roms. i never had this issue with my first one v... could my new one have the update already when i bought it? i ran the RUU football posted and was able to boot the stock rom... but right away it goes into roaming again, with my phone not even recognizing that it's using a VM service.
real confused...
jetfactor said:
i got my one v primoc back in the beginning of summer, but then something fell on it and cracked the screen super bad but i loved the phone so much that i bought another at the end of october. i unlocked, wiped, and flashed JB roms... which seemed to work fine for a while & then would have issues of staying stuck in roaming. i've tried different roms. i never had this issue with my first one v... could my new one have the update already when i bought it? i ran the RUU football posted and was able to boot the stock rom... but right away it goes into roaming again, with my phone not even recognizing that it's using a VM service.
real confused...
Click to expand...
Click to collapse
Yes it's possible that you got one with the update already on it however the problem you are having is completely different than the problem we're describing in this thread and could be caused by many other things - not necessarily the OTA update.
Seems a bit off topic for this thread...
More of the rebooting problem
I have 2 phones one with this problem, the other without it. My friend got one of these phones after i installed jelly bean on mine. He had it long enough to have updated the firmware using the stock image. I made a backup of the stock image, but it seems to have been corrupted (zero byte .zip file). I need to get the phone working (stock or updated, at this point there is no preference so long as it works)
In the bootloader, the radio version of the crashing one is:
1.00.00.0928
The working one is:
1.00.00.0521_2
As far I can tell, this is the only difference. I Used the same SD card and the same procedure for wipe/installing the OS with the same files.
Have you found a solution to this? If so, can you point me to the downloads/instructions for how to fix it?
Looking for help
wendall911 said:
RESOLVED
I ran the RUU for my phone, re-ran the update and am stable on 1.08.652.11 710RD
I'm not sure what I can do to fix this issue, as it appears to be a firmware problem. Thoughts?
Click to expand...
Click to collapse
This may be a bit noob-ish, but can you please add instructions with links for any downloads. I am new to android hacking and have not yet picked up all of the short hand.
Thanks!
madhephaestus said:
This may be a bit noob-ish, but can you please add instructions with links for any downloads. I am new to android hacking and have not yet picked up all of the short hand.
Thanks!
Click to expand...
Click to collapse
hey can i please know how to fix the radio on my phone i have the same problem, my phone will boot and turn on but after 10 seconds in turns off again and boots again? can i please get help ?
I had previously tried to root my phone and decided to flash it back to factory. I downloaded last nights OTA 4.3 update and after it installed, now my ATT S3 SGHi1747 gets stuck at the ATT logo AFTER the Samsung logo appears then disappears. My pc is no longer recognizing the device nor do I know how to get in there to at least get it up and running to try and flash it back to factory THEN download 4.3.
Any suggestions on how to get this fixed would be appreciated!
'Sider said:
I had previously tried to root my phone and decided to flash it back to factory. I downloaded last nights OTA 4.3 update and after it installed, now my ATT S3 SGHi1747 gets stuck at the ATT logo AFTER the Samsung logo appears then disappears. My pc is no longer recognizing the device nor do I know how to get in there to at least get it up and running to try and flash it back to factory THEN download 4.3.
Any suggestions on how to get this fixed would be appreciated!
Click to expand...
Click to collapse
ODIN back to stock.
Question
Did you try using ODIN or did you find a factory ROM to flash?
'Sider said:
I had previously tried to root my phone and decided to flash it back to factory. I downloaded last nights OTA 4.3 update and after it installed, now my ATT S3 SGHi1747 gets stuck at the ATT logo AFTER the Samsung logo appears then disappears. My pc is no longer recognizing the device nor do I know how to get in there to at least get it up and running to try and flash it back to factory THEN download 4.3.
Any suggestions on how to get this fixed would be appreciated!
Click to expand...
Click to collapse
Try booting into recovery and factory resetting, this usually fixes this problem.
polobunny said:
ODIN back to stock.
Click to expand...
Click to collapse
Downloaded ODIN, still a little fuzzy on how to operate it
Cadle said:
Did you try using ODIN or did you find a factory ROM to flash?
Click to expand...
Click to collapse
Im not too tech savvy obviously lol, can you point me in the direction of a factory ROM
dntesinfrno said:
Try booting into recovery and factory resetting, this usually fixes this problem.
Click to expand...
Click to collapse
Tried this twice, no luck.
Im assuming once I get this thing flashed back, I can download that app that will reset the counter?
'Sider said:
Downloaded ODIN, still a little fuzzy on how to operate it
Click to expand...
Click to collapse
If you google for "odin flash rom" there's lot of good tutorials out there, many on this forum alone. As for stock, i'm not sure where to find it since I flashed custom the day after I got my phone and never looked back...can't stand stock touchwiz. You could also try flashing any custom ROM you happen to have layin around...worth a shot until you find a custom one. I use BeanStalk ROM, which has 4.3 and 4.4 versions out now.
Best of luck to ya!
goombah88 said:
If you google for "odin flash rom" there's lot of good tutorials out there, many on this forum alone. As for stock, i'm not sure where to find it since I flashed custom the day after I got my phone and never looked back...can't stand stock touchwiz. You could also try flashing any custom ROM you happen to have layin around...worth a shot until you find a custom one. I use BeanStalk ROM, which has 4.3 and 4.4 versions out now.
Best of luck to ya!
Click to expand...
Click to collapse
I suggest here that everyone here read some of the other threads here on XDA, and see all the problems people are having flashing and rooting after taking this latest 4.3 OTA before advising the next person on how to make ANOTHER paper weight.
As for Sider,
You might be out of luck here, as there is no official 4.3 firmware yet available to flash back to stock, and also AT&T has done something with the new software update, where trying to downgrade it back to a previous version is going to either fail or brick phones.
Also, I haven't read yet where anyone has been successful flashing a custom recovery to fix any issues, but the posts are going up so fast right now that I might have easily missed it.
Edit: OK, someone was able to get TWRP installed, but is also having issues with root.
polobunny said:
ODIN back to stock.
Click to expand...
Click to collapse
DO NOT ODIN after last update (OTA 4.3) installed on phone. You will brick your phone.
norbarb said:
DO NOT ODIN after last update (OTA 4.3) installed on phone. You will brick your phone.
Click to expand...
Click to collapse
You're right. I completely forgot about that.
ok guys, i have a question for you. keep in mind that im new to the phone world lol. ok so a bout a month ago i wanted to unroot my phone but for some reason the tar files on sammobile wasnt working right. so i came on here and downloaded what i believed to be the file that i needed to go back to stock. after i used odin and the phone rebooted it automatically notified me that i had a update. after i accepted the update and it rebooted, it again notified me that i have yet another update. so after this happened i noticed that my phone was updated to 4.4.4 kitkat which would be great exept for the fact that it keeps freezing and when i am on wifi i have a problem getting phone calls aswell as text messages. also when i disconnect from wifi i have to restart the phone to get any data back. is there anything that i can do? is it possible to go back to 4.3 or even 4.2.2? any help would be very much appreciated.
hellrazr209 said:
ok guys, i have a question for you. keep in mind that im new to the phone world lol. ok so a bout a month ago i wanted to unroot my phone but for some reason the tar files on sammobile wasnt working right. so i came on here and downloaded what i believed to be the file that i needed to go back to stock. after i used odin and the phone rebooted it automatically notified me that i had a update. after i accepted the update and it rebooted, it again notified me that i have yet another update. so after this happened i noticed that my phone was updated to 4.4.4 kitkat which would be great exept for the fact that it keeps freezing and when i am on wifi i have a problem getting phone calls aswell as text messages. also when i disconnect from wifi i have to restart the phone to get any data back. is there anything that i can do? is it possible to go back to 4.3 or even 4.2.2? any help would be very much appreciated.
Click to expand...
Click to collapse
Hello! Did you make a back up of your phone before you started the update? That would be the easiest way to go back to how it was. If you used Odin and didn't install a recovery like TWRP or Clockwork you may not have done so. I believe you can reload from Odin with an older ROM it will just erase everything you did. There are stock ROMS here at XDA and galaxynote3root.com as well. Let me know it this helps, sorry for your troubles.
5225
Jedidanno said:
Hello! Did you make a back up of your phone before you started the update? That would be the easiest way to go back to how it was. If you used Odin and didn't install a recovery like TWRP or Clockwork you may not have done so. I believe you can reload from Odin with an older ROM it will just erase everything you did. There are stock ROMS here at XDA and galaxynote3root.com as well. Let me know it this helps, sorry for your troubles.
Click to expand...
Click to collapse
Thanks for the reply, so i wont have any problem downgradeing? I think i read somewhere that i could brick my phone. And if it is possible what version am i able to go back to?
Oh and to answer your question, i have never has a custom recovery on this phone and i didnt make a back up.
Can you post a screenshot of your about phone page?
Techniques said:
Can you post a screenshot of your about phone page?
Click to expand...
Click to collapse
is this good
I'm actually surprised that you did get an update to 4.4.4... You could try going back to NF9. The safest route I see that you can take is to install a custom recovery and make a backup before doing this. If you odin NF9 and it doesn't boot then you're kinda screwed because we technically don't have the 4.4.4 update yet, so if anything goes wrong, you can install a recovery again and restore the 4.4.4 backup.
Techniques said:
I'm actually surprised that you did get an update to 4.4.4... You could try going back to NF9. The safest route I see that you can take is to install a custom recovery and make a backup before doing this. If you odin NF9 and it doesn't boot then you're kinda screwed because we technically don't have the 4.4.4 update yet, so if anything goes wrong, you can install a recovery again and restore the 4.4.4 backup.
Click to expand...
Click to collapse
haha i was surprised to, i cant find anyone else that has it with this phone either, i was kinda wondering if i maybe downloaded the wrong file maybe for a different country or carrier. im not sure how to do the hole backup and custom recovery thing.
hellrazr209 said:
haha i was surprised to, i cant find anyone else that has it with this phone either, i was kinda wondering if i maybe downloaded the wrong file maybe for a different country or carrier. im not sure how to do the hole backup and custom recovery thing.
Click to expand...
Click to collapse
You can get the latest TWRP recovery here : http://www.techerrata.com/file/twrp2/hltetmo/openrecovery-twrp-2.8.1.0-hltetmo-4.4.img.tar
Just odin that and after it's done, go into recovery by doing Vol down + Home and do a backup either in your internal or external storage. After that finishes, you can go back in download mode and odin NF9.
ok thanks for all you help man,
hellrazr209 said:
is this good
Click to expand...
Click to collapse
iam surprised as well how did you get the latest tar on tmobile note 3?
chipis said:
iam surprised as well how did you get the latest tar on tmobile note 3?
Click to expand...
Click to collapse
I got it on here, it was a tar for 4.4.2 i believe and after i downloaded it, it said i had a update. After that i had another update lol which brought me to the hell im in now lol 4.4.4
hellrazr209 said:
I got it on here, it was a tar for 4.4.2 i believe and after i downloaded it, it said i had a update. After that i had another update lol which brought me to the hell im in now lol 4.4.4
Click to expand...
Click to collapse
Well i believe if iam right samobile had not release it for tmo yet
chipis said:
Well i believe if iam right samobile had not release it for tmo yet
Click to expand...
Click to collapse
Yeah its not on their website. I have know idea what i got then lol anyway to fine out if i have something i shouldnt?
I attempted to root my phone using the Chainfire Auto-root method today and somehow managed to use the 925p edge MD5 file instead of 920p. This caused a few issues, the X-axis was inverted, no service, and a continual automatic reboot after about 30-60 seconds of the phone being on. In an attempt to fix it, I have tried a few things. in many combinations. I have reflashed the stock tar file, cleared cache, factory reset, and flashed the PIT file found in post 12 of this thread http://forum.xda-developers.com/sprint-galaxy-s6/help/operating-smg920p-t3263325/page3. Unfortunately all attempts have been for fruitless. Obviously the first issue to be tackled is the constant rebooting. Any help would be appreciated.
Maybe flashing unikernel will help, it can be found here: https://www.androidfilehost.com/?fid=24269982087012055
Just flash it in Odin, if that does not work you may want to try bringing it to where you bought it for warranty.
No luck, unfortunately.
offthatwall said:
No luck, unfortunately.
Click to expand...
Click to collapse
Idk, @koop1955 any suggestions?
1619415 said:
Idk, @koop1955 any suggestions?
Click to expand...
Click to collapse
Posted this in the other thread: http://forum.xda-developers.com/showpost.php?p=64735692&postcount=19
That is all that I have for you.
offthatwall said:
I attempted to root my phone using the Chainfire Auto-root method today and somehow managed to use the 925p edge MD5 file instead of 920p. This caused a few issues, the X-axis was inverted, no service, and a continual automatic reboot after about 30-60 seconds of the phone being on. In an attempt to fix it, I have tried a few things. in many combinations. I have reflashed the stock tar file, cleared cache, factory reset, and flashed the PIT file found in post 12 of this thread http://forum.xda-developers.com/sprint-galaxy-s6/help/operating-smg920p-t3263325/page3. Unfortunately all attempts have been for fruitless. Obviously the first issue to be tackled is the constant rebooting. Any help would be appreciated.
Click to expand...
Click to collapse
Koop's stock firmware didn't fix mine for some reason either...heres the stock version that fixed mine
mediafire.com/download/c55xaeb7geq0i2d/G920PVPU3BOJ7_G920PSPT3BOJ7_SPR.zip
Hope it helps!
x1xmadex1x said:
Koop's stock firmware didn't fix mine for some reason either...heres the stock version that fixed mine
mediafire.com/download/c55xaeb7geq0i2d/G920PVPU3BOJ7_G920PSPT3BOJ7_SPR.zip
Hope it helps!
Click to expand...
Click to collapse
The firmware posted above is OJ7, which seems to be an earlier version than the OL1 firmware. I have no idea why OJ7 would work for you when OL1 wouldn't. (Unless you got a bad download of OL1, which is why I recommend checking MD5.)
If you are still on OJ7, can you try system update and see if that takes you to OL1?
koop1955 said:
The firmware posted above is OJ7, which seems to be an earlier version than the OL1 firmware. I have no idea why OJ7 would work for you when OL1 wouldn't. (Unless you got a bad download of OL1, which is why I recommend checking MD5.)
If you are still on OJ7, can you try system update and see if that takes you to OL1?
Click to expand...
Click to collapse
I have already re-rooted my device and installed twrp...it wont let me install a system update due to custom and not official...Also I downloaded the OL1 three occasions..and MD5 passed
x1xmadex1x said:
I have already re-rooted my device and installed twrp...it wont let me install a system update due to custom and not official...Also I downloaded the OL1 three occasions..and MD5 passed[/Q
Im have the constant reboot now. Im gonna try another pb6 6.0.1 tar file only one ive tried was the sprint worker one said revo in in it. That didnt not fix my constant rebooting issue. So far any rom even after odin stock still rebooting every 2 minutes.
Click to expand...
Click to collapse
will get that logcat
Saafir said:
Note the time and grab a logcat.
Ok i left the phone at home but i did look at the log cat about the first ten lines all had emmc in them im not quite sure. Well I cant read it lol. when i get home il flash twrp and restore a back up let reboot a few times get a log cat and post it will twrps log cat work? If im lucky i might get a app installed to do it. I no longer got adb and fastboot on my computer but will download if needed.
im waiting for a replacement to get to the sprint store. i flashed stock and took it in rebooting sprint guy tried factory resetting it and clearing cache which got it stuck in the pre load starting or optimizing apps before itd finish it it would reboot and if i kept going id beable get to start up settings thats it. now i can flash twrp still it does restores my back ups and after that itl boot the system i can uninstall or install something or what not maybe 1 min after im able to get into it it reboot. only wifi connects though.
Again i had about all roms we got on sprint forum on that phone worked awesome loved it til the time i restored the efs on 6.0.1 with a twrp thats a unofficial build modded to work on 920p.
Click to expand...
Click to collapse
Sounds good thanks man.
Seems as maybe a somewhat common issue unfortunately thats happening for s6 as well as sprint note 5 as there are a few threads regarding the same issue. Theres a thread for s6 on this issue and on 2nd page appears as if someone found a fix having something to do with letting it die completely etc.. http://forum.xda-developers.com/sprint-galaxy-s6/help/constant-rebooting-t3287213
I figured my rebooting issue was corrupted data becausr i was transferring from phone to pc to phone and no md5 check. Though now i will use it. Good luck
Device: LG G3
Rom: [AOSP EXTENDED V3.0] [LG G3 - D855] [OFFICIAL] [NOUGAT R9] [by MARCHETTO96]
Hey again,
So i'm running this rom right and I was reinstalling my apps onto my phone and one app I need to log into but it noticed it was running root (Snapchat). So I followed someones advice on here on XDA to fully unroot the device and I did that I fully unrooted the app from the phone and then here comes the worst part that I realized this will kick me out of recovery and i wont be able to get back in because I need to get on to recovery to re install superSU back on. So im stranded on nougat 7.1 and dont have access to root at all except for root access on developer settings but that doesn't nothing at all I re installed the app on play store but its telling me the phone is unrooted of course.
Anyone can help me out here. It would be greatly appreciated .
P.S I did get snapchat working after that method kinda did work/backfire at the same time.
Do you have nandroid backup? If yes, flash that. It will be all well.
Other hard method is to downgrade to KitKat and then root and then TWRP. ?
I do not have a back up for this ROM but I have other back ups on my phone that still works. I can't do it as well cause I neeed root to l get it to work.
HunterTubeHD said:
I do not have a back up for this ROM but I have other back ups on my phone that still works. I can't do it as well cause I neeed root to l get it to work.
Click to expand...
Click to collapse
Backups don't need root. They need TWRP to be flashed.
Jahanzaibawan said:
Backups don't need root. They need TWRP to be flashed.
Click to expand...
Click to collapse
Yeah thats the only thing I can't get access to TWRP. When I fully unrooted It would not let me in my recovery at all just bootloops until i take the battery out then it reboots to the system fine.
Just going to ask a hopefully obvious question that I know doesn't help but I'm intrigued... Why didn't you just unroot using the supersu app?
pffcouk said:
Just going to ask a hopefully obvious question that I know doesn't help but I'm intrigued... Why didn't you just unroot using the supersu app?
Click to expand...
Click to collapse
I did do that....now my main problem is I don't have root anymore and I can't get access to my recovery and plus I'm running an Nougat rom so I need to find a way to re-root my phone again to get it all back.
The supersu app doesn't delete the recovery on your phone so something had to have gone wrong. Either way the best bet for you I would imagine anyway would be to follow a guide to install recovery - it's been that long since I had to do it I can't be of much help but I'm willing to look into the easiest options for you if you want. There will be a way, pretty much guaranteed
pffcouk said:
The supersu app doesn't delete the recovery on your phone so something had to have gone wrong. Either way the best bet for you I would imagine anyway would be to follow a guide to install recovery - it's been that long since I had to do it I can't be of much help but I'm willing to look into the easiest options for you if you want. There will be a way, pretty much guaranteed
Click to expand...
Click to collapse
I know that my recovery is still there but It wont allow me on there for some reason. But im thinking that If I factory reset the phone it would PROBABLY fix the problem but theres one risk that it could probably happen and im guessing that it will go straight into a bootloop. If you want to help me It would be great
I'll research for you mate!
Did you modify your ro.product.model in build.prop file and when supersu app asks if you want to flash stock recovery you pressed yes?
For example if you have enabled google assistant by changing your ro.product.model to pixel or pixel xl and after that unrooted and pressed yes to restore stock recovery (to get OTA to work), supersu flashes pixel recovery and thats why you can't get to recovey again.
There are ways to get your phone back to factory clean and start over.
Okay I have spent a whole day figuring out this problem but i finally managed to fix it.
So I went onto download mode
opened up LG Flash Tool 2014
Flashed an LG KDZ File managed to work after the 2nd time
10 or 15 mins later it finally worked
LG started to boot up and started loading in the apps
THEN
I rooted the phone again using this forum: https://forum.xda-developers.com/lg-g3/general/root-twrp-marshmallow-d855-30b-t3286268
Then I finally got back onto the glorious TWRP rom.
I re-installed the ASOP rom again.
I'd Like to thank Juhkimo, Jahanzaibawan and pffcouk for helping me out. You guys got my phone back to what it was before so thanks a ton
HunterTubeHD said:
I'd Like to thank Juhkimo, Jahanzaibawan and pffcouk for helping me out. You guys got my phone back to what it was before so thanks a ton
Click to expand...
Click to collapse
Really good to hear that :highfive: