Related
God do I hate technology sometimes.
Phone was working perfectly, ages ago, I had updated it to JF 1.5, with apps2SD, and everything is working perfectly until today, I restart my phone (not the first time I have done this since last updating my phone), and for some reason it cant go beyond the android flashing screen. Just keeps going.
WTF do I do? I do not want to have to reflash my phone causing me to have to reinstall all my apps, etc. Just too much hassle, I hope it doesnt come to that.
Does anyone have any ideas?
I have tried removing the battery and putting it back, no difference. Maybe I didnt do it for long enough.
Any advice or help would be much appreciated.
wel I thought I may as well reflash with JF 1.5, and have done so, but the phone STILL won't go past the flashing android screen.
Dunno what to do now, I had thought this would definately do the trick.
Any help would be much appreciated.
Use the search bttom.... and WIPE the phone, Wipe the phone and problem solve...
i have almost same problem
except mine goes past android screen then screen goes blank but stays lit up
Don't wipe your phone. Try this first.
Krazyone said:
Figured i would update this with the knowledge i have gained. Erase the EXT2 / 3 partition then wipe. Load the ROM again and reboot. This should let it pass the boot loop. I had the problem this morning with Drizzy's Hero build and now with JAC's I am running tests with.
Click to expand...
Click to collapse
I had the same problem so I did what Krazyone suggested in one of the post. And it solved my problem. It's something to do with your EXT partition be corrupted or something.
EDIT: You will have to either reload your apps or restore them from your backup.
Same problem here & tried as you suggested...
BeenAndroidized said:
Don't wipe your phone. Try this first.
I had the same problem so I did what Krazyone suggested in one of the post. And it solved my problem. It's something to do with your EXT partition be corrupted or something.
EDIT: You will have to either reload your apps or restore them from your backup.
Click to expand...
Click to collapse
I tried that, but phone still wouldn't boot past the android screen. So, will wipe & start anew.
I posted this on DamageLess' page in hopes that he could help me, but I haven't gotten a reply yet. I figure someone on this forum can help me.. Just read the paragraph and you'll know my problem...
Hey man, I really need your help
I tried using your new DCUpdater (which is a fantastic idea btw) and i'm having a major issue. My phone won't boot. At first I was having problems with SuperUser, but I fixed that by enabling USB debugging, then unplugging the phone, then using the Updater. That worked. But when I tried to reboot the phone, it wouldn't boot. I wiped, restored to my most recent backup, and it still won't boot. I wiped, manually installed your new ROM, and tried to reboot again, and that's where I am right now. It had the Quietly brilliant screen, flashed the sprint logo screen, and now it's back to the Quietly brilliant screen. I think it's in an endless boot, because as I was typing this, the screen flashed grey for a second, then it flashed the sprint logo, and now it's back to quietly brilliant. Please please PLEASE get back to me asap, because I don't know what to do.
dereklane said:
I posted this on DamageLess' page in hopes that he could help me, but I haven't gotten a reply yet. I figure someone on this forum can help me.. Just read the paragraph and you'll know my problem...
Hey man, I really need your help
I tried using your new DCUpdater (which is a fantastic idea btw) and i'm having a major issue. My phone won't boot. At first I was having problems with SuperUser, but I fixed that by enabling USB debugging, then unplugging the phone, then using the Updater. That worked. But when I tried to reboot the phone, it wouldn't boot. I wiped, restored to my most recent backup, and it still won't boot. I wiped, manually installed your new ROM, and tried to reboot again, and that's where I am right now. It had the Quietly brilliant screen, flashed the sprint logo screen, and now it's back to the Quietly brilliant screen. I think it's in an endless boot, because as I was typing this, the screen flashed grey for a second, then it flashed the sprint logo, and now it's back to quietly brilliant. Please please PLEASE get back to me asap, because I don't know what to do.
Click to expand...
Click to collapse
do a wipe/ factory restore and then restart phone. dont flash any other rom or anything. samething happened to me the other night when i flashed the rom. it was an endless boot loop. i tried a wipe and reflash. wipe nandroid, nothing worked until i said screw it ill wipe and go back to factory and then try after phone boots up. to my surprise when phone started back up it was the 2.1 rom that i tried to flash. dont ask me why but it worked
Try wiping the ext partition.
-------------------------------------
Sent via the XDA Tapatalk App
david279 said:
Try wiping the ext partition.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Do I re-flash the ROM after I wipe, or do I try to do a restore????
dereklane said:
Do I re-flash the ROM after I wipe, or do I try to do a restore????
Click to expand...
Click to collapse
id say do not flash a rom. do a factory wipe then restart. read my comment under ur original post
You can do what the 2nd guy said..
Wipe everything.. Then dont flash or nandroid restore.. JUST reboot your phone.
Or save all your files to your computer that are on your sdcard... Repartition your sdcard. Then reflash the rom and move your stuff back.
cbarlan said:
id say do not flash a rom. do a factory wipe then restart. read my comment under ur original post
Click to expand...
Click to collapse
So you're saying wipe everything and then just reboot the phone?
Jus10o said:
You can do what the 2nd guy said..
Wipe everything.. Then dont flash or nandroid restore.. JUST reboot your phone.
Or save all your files to your computer that are on your sdcard... Repartition your sdcard. Then reflash the rom and move your stuff back.
Click to expand...
Click to collapse
I just did a factory reset, wiped my Dalvik cache, and wiped my sc card option thingy. I went straight from there to rebooting my phone. I'll say something if it boots now
i'd say wipe settings, wipe ext, wipe dalvik, flash rom, boot. if that doesn't work, wipe again and again then boot.
Jus10o said:
You can do what the 2nd guy said..
Wipe everything.. Then dont flash or nandroid restore.. JUST reboot your phone.
Or save all your files to your computer that are on your sdcard... Repartition your sdcard. Then reflash the rom and move your stuff back.
Click to expand...
Click to collapse
can i flash a new rom now?
Thread Moved as it isn't development.
Okay, today I was about to flash a new rom so I attempted to wipe, but I got an error that the phone could not mount the cache (and later couldn't mount data). It says "E:Can't mount CACHE:recovery/command" on the next line "E:Can't mount CACHE:recovery/log" and the next "E:Can't open CACHE:recovery/log". So I have tried reflashing recovery to fix it and it did not work. I cannot flash any rom without an error or restore my nandroid backups. I am in the process of trying to restore the nandroid backups throught fastboot. Can anyone give me any help on this?
SOLUTION: blancoisgod recommends formatting the cache partition to fix this problem
Did you pull the battery and retry?
Yep. Actually, the phone wont even turn on anymore. I will just have to return it to tmobile tomorrow
toby4059 said:
Yep. Actually, the phone wont even turn on anymore. I will just have to return it to tmobile tomorrow
Click to expand...
Click to collapse
This is exactly why manufacturers don't want people rooting and messing with their phones.
So because of your stupidity and lack of foresight you're now going to return your phone?! That's laughable.
Now T-Mobile and HTC have to pick up the bill for someone else's ignorance.
Note to self....remember your name and never help you!
No man dont turn it into tmobile. Now everyone is gonna ride you because you broke it and your going to return it because of what you have done,not the manufacturer.
Go ahead and turn it in, but please read around a bit before you do this again.
CBConsultation said:
This is exactly why manufacturers don't want people rooting and messing with their phones.
So because of your stupidity and lack of foresight you're now going to return your phone?! That's laughable.
Now T-Mobile and HTC have to pick up the bill for someone else's ignorance.
Note to self....remember your name and never help you!
Click to expand...
Click to collapse
Your right it is my fault; although, I am not sure what I did wrong. I am not a complete idiot and have been doing this stuff for a while. I did everything by the instructions and this happened. I actually saw this happen to someone in the G2 forum but no one found a solution. I see how returning the phone would be wrong but what are my options? I am only 15, no income, so what could I do. If I had income of course I would just pay for a new phone. I hope I am not coming off as a dumb juvenile crook, I apologize.
toby4059 said:
Your right it is my fault; although, I am not sure what I did wrong. I am not a complete idiot and have been doing this stuff for a while. I did everything by the instructions and this happened. I actually saw this happen to someone in the G2 forum but no one found a solution. I see how returning the phone would be wrong but what are my options? I am only 15, no income, so what could I do. If I had income of course I would just pay for a new phone. I hope I am not coming off as a dumb juvenile crook, I apologize.
Click to expand...
Click to collapse
Did you make a backup image? If so you could just flash your recovery image and be golden. If not, then your options are very limited.
I was not trying to hurt or insult your feelings but we constantly see people who 'think' they know what they're doing with these same issues all day every day.
My advice is limited as well at this point because I'm not sure exactly what you've done or precautions you had in place for this.
Can you even boot into the OS at all? Do a factory reset?
CBConsultation said:
Did you make a backup image? If so you could just flash your recovery image and be golden. If not, then your options are very limited.
I was not trying to hurt or insult your feelings but we constantly see people who 'think' they know what they're doing with these same issues all day every day.
My advice is limited as well at this point because I'm not sure exactly what you've done or precautions you had in place for this.
Can you even boot into the OS at all? Do a factory reset?
Click to expand...
Click to collapse
I cannot turn the phone on what so ever. I was flashing my backup through fastboot then tried to reboot and now it will no longer turn on. I fastboot erased recovery, system, userdata, and boot and restored them from the nandroid backup I had taken prior to the error. The day prior I had rooted successfully and flashed the desire z port. I decided I wanted to try the HD port so I wiped and flashed the rom. When I rebooted it got to the lockscreen and it showed some graphical corruption then began to boot loop. I turned it off and went to recovery and thats when the CACHE errors started. Was I supposed to wipe the dav cache because I am pretty sure I did. I just want to find out what I did wrong so it won't happen to me or anyone else.
toby4059 said:
I cannot turn the phone on what so ever. I was flashing my backup through fastboot then tried to reboot and now it will no longer turn on. I fastboot erased recovery, system, userdata, and boot and restored them from the nandroid backup I had taken prior to the error. The day prior I had rooted successfully and flashed the desire z port. I decided I wanted to try the HD port so I wiped and flashed the rom. When I rebooted it got to the lockscreen and it showed some graphical corruption then began to boot loop. I turned it off and went to recovery and thats when the CACHE errors started. Was I supposed to wipe the dav cache because I am pretty sure I did. I just want to find out what I did wrong so it won't happen to me or anyone else.
Click to expand...
Click to collapse
Between ROM's, you said you wiped. What did you wipe? Cache? Dalvik? Partition?
You said you're not too sure so I am going to assume you either didn't wipe something you should have or you did wipe something you shouldn't have.
Try this. Remove the battery for 10 minutes. When the battery is removed, hold the power button for about 2 minutes. This will drain any residual current left on the board. After the 10 minutes are up, try reinserting the battery, hold the volume- button and try to power on. We'll see if you can manage to boot into recovery at this point.
CBConsultation said:
Between ROM's, you said you wiped. What did you wipe? Cache? Dalvik? Partition?
You said you're not too sure so I am going to assume you either didn't wipe something you should have or you did wipe something you shouldn't have.
Try this. Remove the battery for 10 minutes. When the battery is removed, hold the power button for about 2 minutes. This will drain any residual current left on the board. After the 10 minutes are up, try reinserting the battery, hold the volume- button and try to power on. We'll see if you can manage to boot into recovery at this point.
Click to expand...
Click to collapse
Okay I will give that a try thanks.
I had the same error just right now man
What you want to do is format the cache partition when you get the thing booted.
blancoisgod said:
I had the same error just right now man
What you want to do is format the cache partition when you get the thing booted.
Click to expand...
Click to collapse
Did you do that and did it fix? I did that through adb and thats when it stopped booting, although I think the boot issue is unrelated to my current problem.
i did it via clockwork
Alright, I will try this if I can ever get my phone started again.
Note: I may not use terms correctly, I have spent the past hour reading threads similar to mine in order to (hopefully) use the correct terms to describe my predicament.
I was using TriForce ROM 3.0 and I wanted to mix things up a bit because it was too much like the stock ROM. I found Negalite S4 and tried my hand at that, with devastating consequences. I booted my phone into TWRP did a wipe and then proceeded to install the Negalite S4.zip onto my phone. It got stuck in a boot loop. After a good 30~ minutes of it continuously rebooting I turned it off and booted back into TWRP. However, now that my phone was wiped, it is not a recognized device by my computer any longer. Since I wiped the phone clean the .zip is no longer on my phone either. So, all I have now is a phone that can boot into recovery (TWRP); which is a soft-brick (correct me if I'm wrong).
I have read other threads and the xda community informs the user to use KIES or ODIN (I have used ODIN once before). However, try as hard as I can to understand their directions... I don't know what to do with ODIN.
My computer does not recognize my device at all. It will only boot into recovery otherwise it's stuck in an infinite boot loop. I am really scared that I have ruined such a valuable phone and so I am not thinking clearly - which is only adding to my "noobishness."
Can anyone please help me out in a way that I can understand? All help is much appreciated!
_retro said:
Note: I may not use terms correctly, I have spent the past hour reading threads similar to mine in order to (hopefully) use the correct terms to describe my predicament.
I was using TriForce ROM 3.0 and I wanted to mix things up a bit because it was too much like the stock ROM. I found Negalite S4 and tried my hand at that, with devastating consequences. I booted my phone into TWRP did a wipe and then proceeded to install the Negalite S4.zip onto my phone. It got stuck in a boot loop. After a good 30~ minutes of it continuously rebooting I turned it off and booted back into TWRP. However, now that my phone was wiped, it is not a recognized device by my computer any longer. Since I wiped the phone clean the .zip is no longer on my phone either. So, all I have now is a phone that can boot into recovery (TWRP); which is a soft-brick (correct me if I'm wrong).
I have read other threads and the xda community informs the user to use KIES or ODIN (I have used ODIN once before). However, try as hard as I can to understand their directions... I don't know what to do with ODIN.
My computer does not recognize my device at all. It will only boot into recovery otherwise it's stuck in an infinite boot loop. I am really scared that I have ruined such a valuable phone and so I am not thinking clearly - which is only adding to my "noobishness."
Can anyone please help me out in a way that I can understand? All help is much appreciated!
Click to expand...
Click to collapse
Okay, download and install Samsung drivers from the Internet if your phone isn't installing them on its own. Download MDL stock. Open ODIN. Put your phone in download mode. ODIN should see your phone. Flash stock MDL. Use goo manager to install TWRP again after your booted on stock MDL. Or use ODIN to do it. Redownload the custom ROM you want and then flash in TWRP. Also wiping the phones dalvik, cache system ect shouldn't have erased your SD card in the first place. You mist have accidentally checked the wipe SD card in advanced wipe options. You never need to do that. So next time also have a nandroid backup on your external SD. I keep one on internal as well in case external card goes bad cause sometimes that happens. And never select that wipe SD card option. Unless of course you really do want to wipe your SD card. Don't do that and keep a full backup of your last working ROM and you'll not have this problem again.
3ncrypt3d said:
Okay, download and install Samsung drivers from the Internet if your phone isn't installing them on its own. Download MDL stock. Open ODIN. Put your phone in download mode. ODIN should see your phone. Flash stock MDL. Use goo manager to install TWRP again after your booted on stock MDL. Or use ODIN to do it. Redownload the custom ROM you want and then flash in TWRP. Also wiping the phones dalvik, cache system ect shouldn't have erased your SD card in the first place. You mist have accidentally checked the wipe SD card in advanced wipe options. You never need to do that. So next time also have a nandroid backup on your external SD. I keep one on internal as well in case external card goes bad cause sometimes that happens. And never select that wipe SD card option. Unless of course you really do want to wipe your SD card. Don't do that and keep a full backup of your last working ROM and you'll not have this problem again.
Click to expand...
Click to collapse
Thank-you for the detailed response, I'll get started now! I did wipe the SD card, you're right. I'm so glad that you posted, thanks again.
If I need help I'll edit this post (no bumping within 24 hours). I'm hoping I have enough smarts to knock this out though. Again, thank you so much.
EDIT: Excuse my ignorance. I'm not sure what MDL stock is, I figured it was the default ROM - I have a nandroid of that. However, even after re-installing the samsung drivers, rebooting both my phone and computer - nothing happens. I don't know how to proceed from here. I can imagine I'm becoming a pain and do apologize.
_retro said:
Thank-you for the detailed response, I'll get started now! I did wipe the SD card, you're right. I'm so glad that you posted, thanks again.
If I need help I'll edit this post (no bumping within 24 hours). I'm hoping I have enough smarts to knock this out though. Again, thank you so much.
EDIT: Excuse my ignorance. I'm not sure what MDL stock is, I figured it was the default ROM - I have a nandroid of that. However, even after re-installing the samsung drivers, rebooting both my phone and computer - nothing happens. I don't know how to proceed from here. I can imagine I'm becoming a pain and do apologize.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2375523
The link above is the tar file for stock MF9. If you just use the link for the from the first post you just need to download the first file (not the kernel). Once downloaded you need to extraxt that zip and you will get a .tar.md5 file from it. Later open odin and make sure only auto reboot is checked. Click on the PDA slot and find the .tar.md5 file you downloaded click on it. Next put your phone into download mode and connect it to your computer. Wait for it to install drivers and you will see a yellow box with "com:[some number]" once you see that click start and from there let it do its thing and whoola you have your phone back to MF9 stock. Good luck!
Sent from my SPH-L720
ROMANTiC KiD said:
http://forum.xda-developers.com/showthread.php?t=2375523
The link above is the tar file for stock MF9. If you just use the link for the from the first post you just need to download the first file (not the kernel). Once downloaded you need to extraxt that zip and you will get a .tar.md5 file from it. Later open odin and make sure only auto reboot is checked. Click on the PDA slot and find the .tar.md5 file you downloaded click on it. Next put your phone into download mode and connect it to your computer. Wait for it to install drivers and you will see a yellow box with "com:[some number]" once you see that click start and from there let it do its thing and whoola you have your phone back to MF9 stock. Good luck!
Sent from my SPH-L720
Click to expand...
Click to collapse
Well, you did it! That post is solid, I understood every-bit! My phone (most likely) is downloading the firmware now. I don't know how long it will take to get off the "Downloading... Do not turn off target !!" screen, but I'll edit this post after letting it sit over night! Thank you both so much.
_retro said:
Well, you did it! That post is solid, I understood every-bit! My phone (most likely) is downloading the firmware now. I don't know how long it will take to get off the "Downloading... Do not turn off target !!" screen, but I'll edit this post after letting it sit over night! Thank you both so much.
Click to expand...
Click to collapse
Your welcome glad to help again, should take less than 10 mins. If its more than that just reboot your computer and repeat the steps from opening odin and finding your file. Another GS4 saved ;D
Sent from my SPH-L720
ROMANTiC KiD said:
Your welcome glad to help again, should take less than 10 mins. If its more than that just reboot your computer and repeat the steps from opening odin and finding your file. Another GS4 saved ;D
Sent from my SPH-L720
Click to expand...
Click to collapse
You were right, it was quite snappy. I cannot believe I was so panicked over this! My babies safe ... for now.
So how did Twrp wipe nor SD card? When by boot into recovery and immediately click on Wipe, it'll wipe everything Necessary except the internal and external memory. Did you click the option to choose what you want to wipe? Happens more than ya may think, cause I've done it myself lol. Good to hear it's back up, I still get freaked out by those occurrences
Sent from my SPH-L720 using Tapatalk 2
reverepats said:
So how did Twrp wipe nor SD card? When by boot into recovery and immediately click on Wipe, it'll wipe everything Necessary except the internal and external memory. Did you click the option to choose what you want to wipe? Happens more than ya may think, cause I've done it myself lol. Good to hear it's back up, I still get freaked out by those occurrences
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
It wasn't human error through TWRP, it was an error while flashing Negalite. It asks if you want to wipe everything, data, or nothing at all. Silly me thought let's wipe EVERYTHING! Heheh
3ncrypt3d said:
Okay, download and install Samsung drivers from the Internet if your phone isn't installing them on its own. Download MDL stock. Open ODIN. Put your phone in download mode. ODIN should see your phone. Flash stock MDL. Use goo manager to install TWRP again after your booted on stock MDL. Or use ODIN to do it. Redownload the custom ROM you want and then flash in TWRP. Also wiping the phones dalvik, cache system ect shouldn't have erased your SD card in the first place. You mist have accidentally checked the wipe SD card in advanced wipe options. You never need to do that. So next time also have a nandroid backup on your external SD. I keep one on internal as well in case external card goes bad cause sometimes that happens. And never select that wipe SD card option. Unless of course you really do want to wipe your SD card. Don't do that and keep a full backup of your last working ROM and you'll not have this problem again.
Click to expand...
Click to collapse
ODIN IS NOT RECOGNISING MY PHONE ...WHAT TO DO????:crying::crying::crying:
Ridddeathmetal said:
ODIN IS NOT RECOGNISING MY PHONE ...WHAT TO DO????:crying::crying::crying:
Click to expand...
Click to collapse
Reinstall drivers, use different USB ports, used different USB cables?
Sent from my SPH-L720 using xda app-developers app
romantic kid said:
reinstall drivers, use different usb ports, used different usb cables?
Sent from my sph-l720 using xda app-developers app
Click to expand...
Click to collapse
tried 4 ports...in different pc also but same result used 3 cables...but none recognising it.....drivers have been downloaded and reinstalled
Hi guys,
Yesterday I washed my galaxy s8 ( china SM-G9500) with water to clean the dust, and it prompted the usb port is wet must dry it before using. Today it's not wet any more, and I tried to connect a usb drive with the type-c to type-a OTG adapter to the phone, but it doesn't work. Then I tried to plug in something else like mouse, keyboard and card reader for multiple times, still no any prompt on my phone at all. However, when I try to connect it to my computer with usb cable, everything are working properly. So could the usb port be damaged by the water, or the OTG adapter was broken? Also, are the usb type-c host mode and guest mode using the same pins?
I really need some help. Thank you so much!
I'm having the same issue except I wasn't in water or near it. No one has an answer for my delimua but hopefully someone will answer with a fix.
this.guy.lol said:
I'm having the same issue except I wasn't in water or near it. No one has an answer for my delimua but hopefully someone will answer with a fix.
Click to expand...
Click to collapse
i found the reason just now. i rooted my galaxy s8 with a modified kernel and magisk, and this results this issue. after restoring firmware to stock with smart switch, everything worked normally. now my problem is solved. if you rooted your phone too, maybe you can backup your data and try to restore.
xdauser'17 said:
i found the reason just now. i rooted my galaxy s8 with a modified kernel and magisk, and this results this issue. after restoring firmware to stock with smart switch, everything worked normally. now my problem is solved. if you rooted your phone too, maybe you can backup your data and try to restore.
Click to expand...
Click to collapse
Thanks is the restore same as flashing with Odin? I never used a smart switch to restore or whatever the non-odin method is.
this.guy.lol said:
Thanks is the restore same as flashing with Odin? I never used a smart switch to restore or whatever the non-odin method is.
Click to expand...
Click to collapse
if you have the stock firmware, you should be able to use odin to flash it too, but i'm not sure how, you can google it. the much easier way is smart switch, you can download it from samsung's official website. and after install it, use the 'more' menu and the first option the do a complete restore by following the instruction.
Okay thanks. I've used Odin before and done several phones over the years. Done it with Odin but still it doesn't work.
this.guy.lol said:
Okay thanks. I've used Odin before and done several phones over the years. Done it with Odin but still it doesn't work.
Click to expand...
Click to collapse
then you should do some check about the usb port, for example try to connect your phone to pc. also, if you rooted your phone, too, you should make sure you restored the kernel with odin.
Everything has been restored. USB works with everything else. Just not with the otg.
this.guy.lol said:
Everything has been restored. USB works with everything else. Just not with the otg.
Click to expand...
Click to collapse
well, that's weird. maybe you should open another thread to talk about this issue, or just report it to samsung.
xdauser'17 said:
well, that's weird. maybe you should open another thread to talk about this issue, or just report it to samsung.
Click to expand...
Click to collapse
I've made a thread like 2 months ago and no one commented except for a guy who doesn't know English at all or how to read. Samsung won't do much since I got my from Europe aka G955F and I live in the states.
this.guy.lol said:
I've made a thread like 2 months ago and no one commented except for a guy who doesn't know English at all or how to read. Samsung won't do much since I got my from Europe aka G955F and I live in the states.
Click to expand...
Click to collapse
ok. These days i'm trying to compile a kernel to fix the issue on my phone. if i can find out the reason, i'll compile one for you too. although i'm not confident enough. so your phone is G955F, right?
and if possible, you could do some check on your otg adapter to make sure it's not a hardware issue.
xdauser'17 said:
ok. These days i'm trying to compile a kernel to fix the issue on my phone. if i can find out the reason, i'll compile one for you too. although i'm not confident enough. so your phone is G955F, right?
and if possible, you could do some check on your otg adapter to make sure it's not a hardware issue.
Click to expand...
Click to collapse
Yes a G955F. I can do some tests ya. Tell me what to check for. When I plug on the adapter it said " charging connected device" when I go to switch the setting to something else, it'll act like it does then it goes right back to it instantly. I stripped the adapter to fit over an otterbox and it worked for 4 days till I flashed a rom so idk. I've literally done everything except try a different OTG. If I had another device to test this on I'd do it but I don't.
this.guy.lol said:
Yes a G955F. I can do some tests ya. Tell me what to check for. When I plug on the adapter it said " charging connected device" when I go to switch the setting to something else, it'll act like it does then it goes right back to it instantly. I stripped the adapter to fit over an otterbox and it worked for 4 days till I flashed a rom so idk. I've literally done everything except try a different OTG. If I had another device to test this on I'd do it but I don't.
Click to expand...
Click to collapse
alright, I'm still in trouble for now, because the self-compiled kernel can't boot up, and my phone give a message like 'kernel is not seandroid enforcing'. i have asked in some other threads, and waiting for answers...
xdauser'17 said:
alright, I'm still in trouble for now, because the self-compiled kernel can't boot up, and my phone give a message like 'kernel is not seandroid enforcing'. i have asked in some other threads, and waiting for answers...
Click to expand...
Click to collapse
That's an easy one. After you flash the kernel wipe cache and dalvik then reboot. If it still persists, wipe dalvik and cache then flash super user in twrp and reboot.
this.guy.lol said:
That's an easy one. After you flash the kernel wipe cache and dalvik then reboot. If it still persists, wipe dalvik and cache then flash super user in twrp and reboot.
Click to expand...
Click to collapse
really? are you sure?
xdauser'17 said:
really? are you sure?
Click to expand...
Click to collapse
I'm 80% sure yes. On my s7 active that is what I had to do when I flashed a kernel or rooted for the first time. You may also try the zip that disables the protection in recovery. I forgot the actual name. To the point, I've had a few devices and that was my remody to fix em. Worth a try at least
this.guy.lol said:
I'm 80% sure yes. On my s7 active that is what I had to do when I flashed a kernel or rooted for the first time. You may also try the zip that disables the protection in recovery. I forgot the actual name. To the point, I've had a few devices and that was my remody to fix em. Worth a try at least
Click to expand...
Click to collapse
okay, i'll give it a try, although i have taken some time to restore my phone from previous fault just now. and maybe i'll need to do that once again soon...
I tried it just now, erasing dalvik cache, /cache or /data... anything possible, but sadly, it's no effect in my case.
I believe this is a compile-time problem, and maybe the solution is edit makefile to change some kernel options, or apply some kind of patch to the kernel source. that will fool the SeAndroid security check to make the kernel bootable. It's possible only a simple modification, but i have no idea how.
right now, i'm going to do a complete restore again to make my phone work. i'm really not sure if i can do this, or if i can help. the only thing i could do for now is waiting for someone's hints. so let's hope everything will go well.
anyway, thanks for your advice.
xdauser'17 said:
I tried it just now, erasing dalvik cache, /cache or /data... anything possible, but sadly, it's no effect in my case.
I believe this is a compile-time problem, and maybe the solution is edit makefile to change some kernel options, or apply some kind of patch to the kernel source. that will fool the SeAndroid security check to make the kernel bootable. It's possible only a simple modification, but i have no idea how.
right now, i'm going to do a complete restore again to make my phone work. i'm really not sure if i can do this, or if i can help. the only thing i could do for now is waiting for someone's hints. so let's hope everything will go well.
anyway, thanks for your advice.
Click to expand...
Click to collapse
You weren't suppose to wipe data as u would a full wipe. Only dalvik and cache. Install a rom like batman rom and then flash your kernel. It should take. If your on stock its tricky.
this.guy.lol said:
You weren't suppose to wipe data as u would a full wipe. Only dalvik and cache. Install a rom like batman rom and then flash your kernel. It should take. If your on stock its tricky.
Click to expand...
Click to collapse
first time, i only wiped dalvik cache and /cache partition, but it still doesn't work, then i tried to wipe /data completely, still no luck...