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...
Related
I have a Canadian S4 and rooted using the twrp method and then installed the vigin google play edition rom. Everything worked fine at first when I installed it but i was fiddling around after in twrp and thought i should format the internal storage and start completely fresh and now if I install any rom including my original backup the device will boot up into the system fine for the first time but if the device resets after that it just hangs on the galaxy S4 logo and i have to reboot into recovery and flash again. Any ideas on how i could fix this? Thanks!!!
Try this, in twrp go into advanced wipe and wipe dalvik cache, cache, system, data and android secure. Then flash your nandroid.
I don't have a nandroid I have a twrp backup
Jaygrippa said:
I don't have a nandroid I have a twrp backup
Click to expand...
Click to collapse
That is a nandroid.
Dont use TWRP for the S4
From what I have experience and I believe others have as well, if you used TWRP to format where you had to type yes, you are pretty much screwed trying to get things working properly again. Maybe it is certain phones, sd cards, roms, who knows, but after I typed yes in TWRP to format everything, I could flash a rom but couldnt restart and things were buggy. I had to use odin to flash back to stock, re-root and flash the rom again. Now everything is 190% considering my battery life went from 6 hours to 28 with medium usage.
I have always loved TWRP on my other phones, but for the S4, its more frustration and using with caution than its worth.
Another word of caution, use windows to fix your phone. Im on linux and its too much of a pain in the ass to use odin/heimdall to go back to stock for newbs. On windows I went to stock and rooted again in no time.
Good luck!
jd1639 said:
That is a nandroid.
Click to expand...
Click to collapse
After doing that stuff in twrp should I flash right back to my backup of stock touch wiz or straight into the ROM of my choosing? Whenever I would have to reflash I would have to format he internal memory or it wouldn't work
Ya I did the thing where I typed yes... Crap ya its my first time doing all this stuff so you suggest I Re do all of the rooting stuff and then flash my backup I made?
Jaygrippa said:
Ya I did the thing where I typed yes... Crap ya its my first time doing all this stuff so you suggest I Re do all of the rooting stuff and then flash my backup I made?
Click to expand...
Click to collapse
You might have to. I had the same problem today where if the phone rebooted I would just get a black screen. I ended up using Odin with the stock rom, reinstalling twrp and then restoring my backup. I'm pretty sure it was a rom I flashed that caused the initial problem and only Odin would clear things up.
Start Over
Jaygrippa said:
Ya I did the thing where I typed yes... Crap ya its my first time doing all this stuff so you suggest I Re do all of the rooting stuff and then flash my backup I made?
Click to expand...
Click to collapse
Actually its going back to stock, then rerooting. All I did was follow androidrootz guide here:
http://www.androidrootz.com/2013/06/how-to-unroot-unbrick-galaxy-s4.html
After that, motochopper back to get root and followed this guide to install OUDHS recovery:
http://forum.xda-developers.com/showthread.php?t=2291956
This worked for me, at least for now. Hope it can help you out.
ericchaffey said:
Actually its going back to stock, then rerooting. All I did was follow androidrootz guide here:
http://www.androidrootz.com/2013/06/how-to-unroot-unbrick-galaxy-s4.html
After that, motochopper back to get root and followed this guide to install OUDHS recovery:
http://forum.xda-developers.com/showthread.php?t=2291956
This worked for me, at least for now. Hope it can help you out.
Click to expand...
Click to collapse
Hey thanks a bunch ill try that out later. I am at work right now and i can still use my phone on the rom i have just as long as i dont reset it. Ill try all of this out when i get home and see if that works. Thanks for everyones help
Now the only problem is i have to find a Fido ROM
Jaygrippa said:
Hey thanks a bunch ill try that out later. I am at work right now and i can still use my phone on the rom i have just as long as i dont reset it. Ill try all of this out when i get home and see if that works. Thanks for everyones help
Click to expand...
Click to collapse
A couple other notes, to avoid other possible problems, use the original samsung cord when connecting to your computer. Switching USB ports can help if there are transfer or other issues. Its pretty easy and straight forward if everything works out well, but there are so many gawt dayum variables that minor issues can cause problems, though may never manifest.
Hopefully this works and please post some results to help the same in need.
ericchaffey said:
A couple other notes, to avoid other possible problems, use the original samsung cord when connecting to your computer. Switching USB ports can help if there are transfer or other issues. Its pretty easy and straight forward if everything works out well, but there are so many gawt dayum variables that minor issues can cause problems, though may never manifest.
Hopefully this works and please post some results to help the same in need.
Click to expand...
Click to collapse
Ya thinks i will, now im just in the process of finding a rom for Fido, they are owned by rogers so im not sure if the rogers rom will work, This android stuff is so stressful its my first android phone so i hope all goes well!
Jaygrippa said:
Ya thinks i will, now im just in the process of finding a rom for Fido, they are owned by rogers so im not sure if the rogers rom will work, This android stuff is so stressful its my first android phone so i hope all goes well!
Click to expand...
Click to collapse
I get firmware from sammobile.com. You have to register but it's free. You'll download a zip. Use 7-zip to extract the .tar.md5 file from it. Use that in Odin, PDA.
jd1639 said:
I get firmware from sammobile.com. You have to register but it's free. You'll download a zip. Use 7-zip to extract the .tar.md5 file from it. Use that in Odin, PDA.
Click to expand...
Click to collapse
ya even they dont have a specific "Fido" firmware...
Anyone know if I can just use the Rogers ROM its pretty much the same company
Jaygrippa said:
Anyone know if I can just use the Rogers ROM its pretty much the same company
Click to expand...
Click to collapse
It'll work. It'll just put their bloatware on and the boot animation will be theirs
Reflashed
Ok so i reflashed to the stock rom using odin and bam it works again, im just wondering what is a good way now too root, and install the same rom i had
This will have everything you need http://forum.xda-developers.com/showthread.php?p=42320391
Thanks everyone for your help, I got my phone back up and running stock, then i rooted using CF- Autoroot and installed twrp again. I then reinstalled the rom i wanted to use and everything is in tip top order
Jaygrippa said:
Thanks everyone for your help, I got my phone back up and running stock, then i rooted using CF- Autoroot and installed twrp again. I then reinstalled the rom i wanted to use and everything is in tip top order
Click to expand...
Click to collapse
Glad to here it. Have fun.
Was happily on CM and for some reason decided to try stock kitkat. Did everything via tutorial and all went all well - but been getting some strange issues which has made my phone unusable.
When i press vol up/down it takes ten seconds to pop up. Sound does not work at all whether calling/playing music. Settings f/c when I attempt to click the sound menu. I believe everything else is working fine.
Tried reflashing stock firmware countless times... Tried flashing numerous custom 4.4 roms.
Australian bought phone if it makes any difference.
Please help as Im stuck using a spare iphone 4 and its killing me! haha.
Thanks,
Riimez said:
Was happily on CM and for some reason decided to try stock kitkat. Did everything via tutorial and all went all well - but been getting some strange issues which has made my phone unusable.
When i press vol up/down it takes ten seconds to pop up. Sound does not work at all whether calling/playing music. Settings f/c when I attempt to click the sound menu. I believe everything else is working fine.
Tried reflashing stock firmware countless times... Tried flashing numerous custom 4.4 roms.
Australian bought phone if it makes any difference.
Please help as Im stuck using a spare iphone 4 and its killing me! haha.
Thanks,
Click to expand...
Click to collapse
Let's start from the beginning.
Can you describe your method of flashing in case you are doing something wrong? Please describe as much information as possible.
What is your phone model?
y2kkingboy said:
Let's start from the beginning.
Can you describe your method of flashing in case you are doing something wrong? Please describe as much information as possible.
What is your phone model?
Click to expand...
Click to collapse
9005. sorry it was a couple of days ago so I dont really remember. I flashed a 4.4 bootloader (standalone) then tried flashing a 4.4 rom i believe it was sweetrom.
Riimez said:
9005. sorry it was a couple of days ago so I dont really remember. I flashed a 4.4 bootloader (standalone) then tried flashing a 4.4 rom i believe it was sweetrom.
Click to expand...
Click to collapse
I believe the best thing to do now is to flash stock ROM and make sure to full wipe everything even internal memory.
If you have external memory, back up what ever you think necessary to it, the remove it from the device and keep it out.
That clean start well give you a good indication whether the problem is based on a bad flash or there is something wrong with the device.
If everything is running smoothly, we will see about flashing custom ROM.
y2kkingboy said:
I believe the best thing to do now is to flash stock ROM and make sure to full wipe everything even internal memory.
If you have external memory, back up what ever you think necessary to it, the remove it from the device and keep it out.
That clean start well give you a good indication whether the problem is based on a bad flash or there is something wrong with the device.
If everything is running smoothly, we will see about flashing custom ROM.
Click to expand...
Click to collapse
Yep its what ive done, reflashed stock completly and removed sd card. Still no dice - running complete stock 4.4 still with this problem.
Could this be an EFS problem?
If it were an efs problem you wouldn't even boot in most cases.
Can you describe how you flashed stock ROM? Maybe you did it wrong.
Sent from my SM-N9005 using Tapatalk
Sorry to hear that..base on my experienced happened also on my S4..luckily still under warranty..have to wait for 2 weeks...company says faulty mother board and speaker. Hope this helps....
Sent from my SM-N900 using xda premium
Riimez said:
Was happily on CM and for some reason decided to try stock kitkat. Did everything via tutorial and all went all well - but been getting some strange issues which has made my phone unusable.
When i press vol up/down it takes ten seconds to pop up. Sound does not work at all whether calling/playing music. Settings f/c when I attempt to click the sound menu. I believe everything else is working fine.
Tried reflashing stock firmware countless times... Tried flashing numerous custom 4.4 roms.
Australian bought phone if it makes any difference.
Please help as Im stuck using a spare iphone 4 and its killing me! haha.
Thanks,
Click to expand...
Click to collapse
NEE region? - if so it has issues with 4.4.2, @nex7er had the same issues, and if you're using SweetROM I believe he pm'd not-i the fix for it. -- It can be fixed though.
Maybe completely wipe it (System, Data and all) and then Flash stock with Odin?
After kitkat upgrade.. if i use camera app such as camera 360 Or picsart, i can't save my photo to sdcard. It's error, Has anyone had or know how to resolve this problem???
Blancos4Lyf said:
Maybe completely wipe it (System, Data and all) and then Flash stock with Odin?
Click to expand...
Click to collapse
Yep. Still no dice.
Riimez said:
Yep. Still no dice.
Click to expand...
Click to collapse
I did post the reason on the last page what I think it might be...... if you're in a Nordic region or even have a nordic model it's a common problem, if you search around you'll see others that have the same issue (notably ne7xer). -- If it's not that, then it's a warranty job due to faulty HW
EDIT: you could try a complete wipe including re-partitioning, but that's a bigger job that you'd want to do in all honesty.
radicalisto said:
I did post the reason on the last page what I think it might be...... if you're in a Nordic region or even have a nordic model it's a common problem, if you search around you'll see others that have the same issue (notably ne7xer). -- If it's not that, then it's a warranty job due to faulty HW
EDIT: you could try a complete wipe including re-partitioning, but that's a bigger job that you'd want to do in all honesty.
Click to expand...
Click to collapse
Could be my last option considering knox is tripped..
Got a link to a tutorial for re-partitioning?
Grab a PIT file for your device; - then you flash firmware with Odin / PIT file. - I have never done it, nor do I fancy doing it, but have a read (journeyman posted asking how and done it, it's in this section Q+A) - I can never remember whether you flash the PIT first then the firmware or both together. I wouldn't want to hazard a guess just in case though.
But if you've tripped KNOX, then yes, seems like it could be your last option, unless you have tried some various custom ROMs? ( I know sweetROM seems to be the master fix for any issues peple have on KK atm) could just be a stock issue currently that will more than likely get a fix at some point.
EDIT As yours is an AU phone, possible it could be a HK model? - from KOGAN? I know some AU users have had HK models from them.
EDIT2: When I flashed HAL ROM, @theresident stated in his how to OP that we needed to format /system during install - It's possible this may also fix it, but that wipes your entire system obviously and *IF* it doesn't boot up you then have issues
EDIT3 : quote from HAL ROM OP
Instalation:
1. Copy the zip to the phone
2. Reboot to Recovery/CWM
3. Wipe Data/Factory Reset
4. Wipe Cache
5. Wipe Dalvik Cache
6. Mounts and Storage then click "Format /System" (This won't delete any of your data)
7. Install.. wait one minute and ROCK !!!
Click to expand...
Click to collapse
crazy_777 said:
After kitkat upgrade.. if i use camera app such as camera 360 Or picsart, i can't save my photo to sdcard. It's error, Has anyone had or know how to resolve this problem???
Click to expand...
Click to collapse
You are hijacking.
Anyway,
1. Install es file manager or any file reader with root.
2. navigate to /System/etc/permissions
3. open "platform.xml" file to edit
4. look for the stack that has "WRITE_EXTERNAL_STORAGE"
you will find something like <group gid="sdcard_r" />
5. make sure these lines are there, if not, add them
<group gid="sdcard_rw" />
<group gid="media_rw" />
That's it
What kind of method would I need to use to be able to get my phone back to stock? I tried to take the update, but failed, and then in a haste deleted all of my storage on the phone. I know that I need to use the OTG cable, but I'm not sure how to go about it. I put a .tot file on the root of a thumb drive to see if i could see it through TWRP but I couldn't. I am in a bootloop that goes straight to TWRP, but I don't have any files to flash to get it to boot up the rest of the way. Do I need to use the KDZ file instead? I have no experience using ADB either so if that is what I need to do, I definitely need assistance with it. Thanks in advance I hope?
No worries, nice and simple fix. Terminal command is awesome.
http://forum.xda-developers.com/showthread.php?t=2451696
Let us know how it goes!
asdfvtn said:
No worries, nice and simple fix. Terminal command is awesome.
http://forum.xda-developers.com/showthread.php?t=2451696
Let us know how it goes!
Click to expand...
Click to collapse
Where will this get me? I dont think I have any kind of rom or anything to boot to because I deleted my memory on accident after I was already in the bootloop. Does the stock rom still exist under everything despite wiping all of memory? Not just data but EVERYTHING (yes I know, I shouldn't have been so antsy while not being familiar with TWRP).
joshuaclogg said:
Where will this get me? I dont think I have any kind of rom or anything to boot to because I deleted my memory on accident after I was already in the bootloop. Does the stock rom still exist under everything despite wiping all of memory? Not just data but EVERYTHING (yes I know, I shouldn't have been so antsy while not being familiar with TWRP).
Click to expand...
Click to collapse
When you wiped, you selected dalvik, cache, and data, correct? If so, you'll be fine (If you truly wiped everything already, you wouldn't have TWRP anyway). The line from that link I posted simply deletes the OTA you downloaded. If you type it exactly as written, nothing else will be done to your phone. Be sure to triple check what you're typing though.
Feel free to keep looking around though if you like.
Best of luck
asdfvtn said:
When you wiped, you selected dalvik, cache, and data, correct? If so, you'll be fine (If you truly wiped everything already, you wouldn't have TWRP anyway). The line from that link I posted simply deletes the OTA you downloaded. If you type it exactly as written, nothing else will be done to your phone. Be sure to triple check what you're typing though.
Feel free to keep looking around though if you like.
Best of luck
Click to expand...
Click to collapse
Both of the methods there do the same? And I selected format data which now that I read is so far from what I wanted haha
joshuaclogg said:
Both of the methods there do the same? And I selected format data which now that I read is so far from what I wanted haha
Click to expand...
Click to collapse
Yeah, Both methods result in the same thing. Format data won't wipe everything.
Hi,
I want to install the ROM here on my Samsung Galaxy S4 (GT-I9505). I rooted and installed CM on it about 4 months ago, but since have forgotten anything about the process except for towelroot lol. My phone is currently running jflte snapshot M10 ROM for CM. Unfortunately, I have grown quite sick of it as I find I have to restart my phone once, maybe twice a day for everything to run smoothly. I run into problems where the WiFi likes to get stuck saying 'Turning on..'. Ive also been having problems with Google Maps and GPS lately and havent been able to rely on it, possibly its an issue its having with CM. I want to have the fresh Lollipop feel on my phone without any problems if possible. The only trouble is I dont know how to get there. Can anyone help me? Ive completely forgotten the process needed and when I try to look for it on here I am overwhelmed with things I need to do, which version I need to use etc etc. If anyone would be able to help me achieve this it would be greatly appreciated. In the end I just want a nice Lollipop android phone that doesn't have problems on my current S4 (Id rather not have to get a new phone at least until December ) I'm pretty sure I dont have a custom kernel or anything like that as it mentioned in some pages that I will need to get one I think? I also have philz CWM installed.
You have Philz installed, so you don't need to root again. Download the ROM and follow the instructions on the page.
Strephon Alkhalikoi said:
You have Philz installed, so you don't need to root again. Download the ROM and follow the instructions on the page.
Click to expand...
Click to collapse
It also mentioned to make sure I have the latest modem for my variant, how do I check/update that?
In regards to the kernel (which has a link on the same page), what do I do with that?
I don't have the latest modem for my I9505 and that ROM works perfectly fine. Where you've been on a custom ROM for a while finding out which modem you're supposed to use may be difficult. That's also why I recommend not worrying about it, unless you need to.
Strephon Alkhalikoi said:
I don't have the latest modem for my I9505 and that ROM works perfectly fine. Where you've been on a custom ROM for a while finding out which modem you're supposed to use may be difficult. That's also why I recommend not worrying about it, unless you need to.
Click to expand...
Click to collapse
Ok thanks. In regards to the kernel that is linked on the page, I guess I would be at an advantage if I downloaded and installed that too. How do I install it?
If' we're talking the same GPE ROM, and I think we are, the kernel is included in the ROM download. You'll be prompted to select a kernel when you run the install through the recovery.
Strephon Alkhalikoi said:
If' we're talking the same GPE ROM, and I think we are, the kernel is included in the ROM download. You'll be prompted to select a kernel when you run the install through the recovery.
Click to expand...
Click to collapse
Ok thanks a lot!
So process:
Backup data/photos etc
Nandroid backup
Full wipe using philz?
Flash ROM
Done?
You've got it.
When you are prompted to select the kernel, use the Googy Max kernel. The stock kernel sometimes causes random reboots. Also, on first boot the S4 will sit for a fair amount of time before prompting you to set a language. THIS IS NORMAL. It's because Android 5.0.x uses Art instead of Dalvik, and has to compile the apps the first time around.
In other words, after rebooting, just be patient.
Strephon Alkhalikoi said:
You've got it.
When you are prompted to select the kernel, use the Googy Max kernel. The stock kernel sometimes causes random reboots. Also, on first boot the S4 will sit for a fair amount of time before prompting you to set a language. THIS IS NORMAL. It's because Android 5.0.x uses Art instead of Dalvik, and has to compile the apps the first time around.
In other words, after rebooting, just be patient.
Click to expand...
Click to collapse
Ok, thanks a lot for the help! Greatly appreciated. Hope I dont run into any problems
I installed that ROM on Sunday, so what I did is still fresh in my mind. If you have problems, just use this thread and quote me. I'll do my best to help.
Strephon Alkhalikoi said:
I installed that ROM on Sunday, so what I did is still fresh in my mind. If you have problems, just use this thread and quote me. I'll do my best to help.
Click to expand...
Click to collapse
All installed, was quite easy! Looks bloody beautiful, love it already. Thanks a heap!
Strephon Alkhalikoi said:
I installed that ROM on Sunday, so what I did is still fresh in my mind. If you have problems, just use this thread and quote me. I'll do my best to help.
Click to expand...
Click to collapse
I made and error when backing up and didnt back up my photos onto a computer Is there any way that my nandroid recovery or titanium backup have saved my photos and how could I recover them?
jc258 said:
I made and error when backing up and didnt back up my photos onto a computer Is there any way that my nandroid recovery or titanium backup have saved my photos and how could I recover them?
Click to expand...
Click to collapse
No, they are gone forever.
How is that even possible that you wiped them? Wiping in the custom recovery never touches your internal storage by default. So you have done it yourself. You probably did a factory reset from within android itself. Never do that again. Use the custom recovery for wiping only and you never will have this problem again.
Lennyz1988 said:
No, they are gone forever.
How is that even possible that you wiped them? Wiping in the custom recovery never touches your internal storage by default. So you have done it yourself. You probably did a factory reset from within android itself. NEVER DO THAT AGAIN. Use the custom recovery for wiping only and you never will have this problem again.
Click to expand...
Click to collapse
Are you sure about that? It happened the first time I flashed a ROM. Wiped cache, wiped Dalvik through CWM. Never did a factory reset. No need for caps.
jc258 said:
Are you sure about that? It happened the first time I flashed a ROM. Wiped cache, wiped Dalvik through CWM. Never did a factory reset. No need for caps.
Click to expand...
Click to collapse
No it's not possible for it to happen without you doing so. Unless you encrypted your phone or something.
ps removed the caps
The rom he installed has an aroma installer which offers the option to do a simple wipe (Dalvik, cache and data), no wipe (Dirty flash) and a factory reset (which also wipes the internal storage).
By default it is set on factory reset option.
It also says in red letters that this option is recommended.
So maybe he left it on factory reset (since it was also recommended) , instead of changing it to simple wipe, and that wiped the whole phone, including the internal storage.
Will a software that recovers deleted files not work? Since the phone wasn't encrypted.
It would if Windows saw the internal storage as a drive. Due to MTP it doesn't. He'll have to do a search, but there was another S4 owner who lost his photos and was trying to get them back. I don't know if a solution was ever found.
GDReaper said:
The rom he installed has an aroma installer which offers the option to do a simple wipe (Dalvik, cache and data), no wipe (Dirty flash) and a factory reset (which also wipes the internal storage).
By default it is set on factory reset option.
It also says in red letters that this option is recommended.
So maybe he left it on factory reset (since it was also recommended) , instead of changing it to simple wipe, and that wiped the whole phone, including the internal storage.
Will a software that recovers deleted files not work? Since the phone wasn't encrypted.
Click to expand...
Click to collapse
If that's the case then shame on the developer. A factory reset in a custom recovery should leave the internal storage intact.
Strephon Alkhalikoi said:
It would if Windows saw the internal storage as a drive. Due to MTP it doesn't. He'll have to do a search, but there was another S4 owner who lost his photos and was trying to get them back. I don't know if a solution was ever found.
Click to expand...
Click to collapse
No it's impossible. Once it's gone the files are permanently gone. Not even a professional company can restore them. That's because of TRIM that Android has from version 4.3.
Lennyz1988 said:
If that's the case then shame on the developer. A factory reset in a custom recovery should leave the internal storage intact.
Click to expand...
Click to collapse
It's not in the recovery. It's in the aroma installer. Those are 2 different things.
Besides, there is a description, under each setting, of what each one does.
@Lennyz1988: Perhaps you should bring this up with the developers of the ROM and see what they say. I suspect they have a very good reason for wiping the internal storage, and my gut instinct tells me it has to do with the Android folder on there.
On the flip side, thanks for the homework you gave me. I have to look into what TRIM is all about, as my last device was powered by Gingerbread.
I have a Canadian S7 edge and it had been rooted for a long time, but I lost the root when I updated to android 7.0.0. I foolishly tried to root it the exact same way I had before (Odin and .tar file method) and now my phone refuses to fully power on. After the boot logo, some new "integrity verification" has failed and I get a message saying my only option is apparently to factory reset and loose everything since my last backup. I'm wondering if there's any way to either:
a) Recover my data first. My PC won't read my phone at the "integrity verification failure" screen, however, my phone can boot into download mode (still unreadable, though). I've tried a few sketchy phone recovery programs on free trials, and none of them were able to read my phone (though none seemed high-quality anyway).
b) Flash stock firmware and fix this all. I am currently downloading stock 7.0 firmware and CSC files for my region/carrier, and I'm wondering if flashing this will pass the "integrity" check and put me safely back to square one, or if I'll lose everything there too.
I don't have a custom recovery currently either, though I realize that wiping my phone would mean I could quickly do that. But caving and wiping my phone is the last thing I want to do here. Any help here would be extremely appreciated!
First of all .. I think flash Stock ROM will erase all data.
but if you can flash custom recovery by ODIN and mount USB Storage to PC and manual backup your data .. it will be good idea if it possible.
iMenesi said:
First of all .. I think flash Stock ROM will erase all data.
but if you can flash custom recovery by ODIN and mount USB Storage to PC and manual backup your data .. it will be good idea if it possible.
Click to expand...
Click to collapse
If I flashed custom recovery, what exactly do you mean by mounting USB Storage to PC? Is that something I could do in the custom recovery (TWRP for example)?
Also, I'm okay with losing system settings or apps, but internal storage like images and music is what I really want to save.
G-Man8776 said:
If I flashed custom recovery, what exactly do you mean by mounting USB Storage to PC? Is that something I could do in the custom recovery (TWRP for example)?
Click to expand...
Click to collapse
Yes .. TWRP Exactly has option to mount device internal storage or micro sd card storage to PC so you can transfer files between device and PC.
iMenesi said:
Yes .. TWRP Exactly has option to mount device internal storage or micro sd card storage to PC so you can transfer files between device and PC.
Click to expand...
Click to collapse
So does this all mean that there's no way to root the S7 edge on Nougat yet, or is there a different way that'll work fine and I just made a dumb mistake?
G-Man8776 said:
So does this all mean that there's no way to root the S7 edge on Nougat yet, or is there a different way that'll work fine and I just made a dumb mistake?
Click to expand...
Click to collapse
I'm reading this now :laugh:
https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084
I spent over 12 hours today trying to root my phone and soft bricked it and bring it back to life many times. :laugh:
https://forum.xda-developers.com/s7-edge/help/help-s7-edge-g935fd-bootloop-twrp-t3583469
iMenesi said:
I'm reading this now :laugh:
https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084
I spent over 12 hours today trying to root my phone and soft bricked it and bring it back to life many times. :laugh:
https://forum.xda-developers.com/s7-edge/help/help-s7-edge-g935fd-bootloop-twrp-t3583469
Click to expand...
Click to collapse
LOL so TWRP is a no-go too then?
I think the problem is that there isn't a working SuperSu for S7 edge on android 7.0.0 yet
G-Man8776 said:
LOL so TWRP is a no-go too then?
Click to expand...
Click to collapse
hhhhh sorry can't understand the meaning of no-go. :laugh:
iMenesi said:
hhhhh sorry can't understand the meaning of no-go. :laugh:
Click to expand...
Click to collapse
When I say "no-go" I mean it's something that won't work. TWRP looks like it doesn't work anymore, when I read your problem that you posted, and the warnings on the TWRP website and XDA page.
I did some reading and it looks like flashing my stock ROM shouldnot delete my internal storage data, so I think that might be my only chance. If it doesn't work either, I'll factory reset, because I don't want to risk the same error you had.
G-Man8776 said:
When I say "no-go" I mean it's something that won't work. TWRP looks like it doesn't work anymore, when I read your problem that you posted, and the warnings on the TWRP website and XDA page.
Click to expand...
Click to collapse
I don't know .. but the thread explaining how to perfect flash TWRP to the device and then flash supersu from Micro SD Card not Internal Storage. i think it was the problem, what do you think? try again and take the risk? :laugh:
iMenesi said:
I don't know .. but the thread explaining how to perfect flash TWRP to the device and then flash supersu from Micro SD Card not Internal Storage. i think it was the problem, what do you think? try again and take the risk? :laugh:
Click to expand...
Click to collapse
Since you don't have anything to worry about (if it fails you can reset again), I'd try again and see if it works, if I were you.
Finally Successfully Rooted my Device.
I followed the instructions very well in this thread.
https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084
iMenesi said:
Finally Successfully Rooted my Device.
I followed the instructions very well in this thread.
https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084
Click to expand...
Click to collapse
I'm currently factory resetting my phone (goodbye phone data ). I tried to flash a stock ROM and after a few failed attempts, it failed so bad I got a message saying the only thing I could do now was factory reset LOL. Not much I can do now but be glad I didn't 100% ruin my phone I guess.
I may try rooting again in the future, but I'll have to learn how to do it your way, since my way doesn't work right now.
G-Man8776 said:
I'm currently factory resetting my phone (goodbye phone data ). I tried to flash a stock ROM and after a few failed attempts, it failed so bad I got a message saying the only thing I could do now was factory reset LOL. Not much I can do now but be glad I didn't 100% ruin my phone I guess.
I may try rooting again in the future, but I'll have to learn how to do it your way, since my way doesn't work right now.
Click to expand...
Click to collapse
We don't learn for free Bro. ?
iMenesi said:
We don't learn for free Bro.
Click to expand...
Click to collapse
Hahaha true. Thanks for the help too!