Related
I have been trying to update my S4 (vruame7) to the latest. I'm willing to lose root. The issue I'm having though is one that NOBODY seems to have mentioned anywhere: It started where I couldn't update over the air as the update fails. So I tried to update it with Kies on my mac but the program says I need more memory on my phone even though I already have it. This prompted me to unroot my phone and do the update again, but the issue is still there. So I tried booting into recovery and that worked. I decided then to reboot my phone and add CWM touch via ROM toolbox Pro. It said it worked fine, but now I cannot boot into the recovery mode. It just goes straight into ODIN mode and it won't prompt me to confirm it or not. I get into a very soft boot loop if I try and reboot though Rom Toolbox Pro to go into the recovery. I will land in ODIN and then unless I tell the phone manually to go into ODIN and then NOT proceed than it will be in a soft boot loop. So far I've tried unrooting and using Kies, Rooting and trying to load CWM onto my phone and failing, causing OTA to not be able to even start installing, and I've yet tried to go into safe mode and try to reset my phone that way. I might have to do that. if anyone has any other ideas I am open to that.
Your on me7 so you half to use safestrap that's the on way you can have a recover...... You probably half to Odin your phone back to me7 for the update to work. You can't use cwm or twrp on me7, unless u have safetrap installed and the its a version of twrp in it
hyperdrive powered s4
ebsk8er06 said:
Your on me7 so you half to use safestrap that's the on way you can have a recover...... You probably half to Odin your phone back to me7 for the update to work. You can't use cwm or twrp on me7, unless u have safetrap installed and the its a version of twrp in it
hyperdrive powered s4
Click to expand...
Click to collapse
Thanks. I've got safestrap installed sucessfully (it was so easy), and I'm now trying to install the update by wiping my phone and then doing it. I'll see if that works.
Well, it looks like I may have wiped my phone too far as I'm stuck at the Samsung custom logo and It's not booting farther. i can get into odin but I have a mac, so what do I do?
beez1717 said:
Well, it looks like I may have wiped my phone too far as I'm stuck at the Samsung custom logo and It's not booting farther. i can get into odin but I have a mac, so what do I do?
Click to expand...
Click to collapse
Heimdall is like odin but its mac.compatible
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Use oden or Heimdall (guess its a Mac thing) to flash back to stock and then you can take the update. You haven't bricked yet but it sounds like you are getting close so be careful.
beez1717 said:
Well, it looks like I may have wiped my phone too far as I'm stuck at the Samsung custom logo and It's not booting farther. i can get into odin but I have a mac, so what do I do?
Click to expand...
Click to collapse
Sounds like you did a full wipe on non safe side "stock rom" of safestrap so your gonna have to flash a whole factory image cause it all gone the whole os
So after working for hoursx and hours, of working at it, I finally found http://sonofgeektalk.wordpress.com/2013/06/13/heimdall-on-a-mac/ <-- that webpage and it helped walk me through using Helmdall and it worked after much fiddling and discovering that I had to plug in my phone AFTER it got into odin but BEFORE I confirmed I wanted to be in odin. I then had to not wipe the phone clean but just do the install with the right files. It worked and I'm so happy. Now to see if I can update the darn phone. Don't know if I can or not but hey, I've got my phone back up and running and that's a GOOD thing.
I don't care about root as much as I care about getting the latest software if it provides enhancements I like, or security features I want. I think that root is fun, but it can be a pain in the butt as I just saw. Now that I know how to do the whole shtick, I should be able to do a lot more with my phone. I remember when I had to learn the ins and outs of my old Xperia Play. Horrible battery life and sub-par graphics chip but an awesome phone that had an awesome utility that could do just about anything with the phone with minimal work.
Looks like the system is updating itself just fine using OTA. What a LONG workaround I had to do. Thank you all for helping me teach myself a lot more about my phone
I'm having trouble trying to update as well. I unrooted and did a factory reset but the update still fails. What should I be trying?
Sent from my SCH-I545 using xda app-developers app
beez1717 said:
So after working for hoursx and hours, of working at it, I finally found http://sonofgeektalk.wordpress.com/2013/06/13/heimdall-on-a-mac/ <-- that webpage and it helped walk me through using Helmdall and it worked after much fiddling and discovering that I had to plug in my phone AFTER it got into odin but BEFORE I confirmed I wanted to be in odin. I then had to not wipe the phone clean but just do the install with the right files. It worked and I'm so happy. Now to see if I can update the darn phone. Don't know if I can or not but hey, I've got my phone back up and running and that's a GOOD thing.
I don't care about root as much as I care about getting the latest software if it provides enhancements I like, or security features I want. I think that root is fun, but it can be a pain in the butt as I just saw. Now that I know how to do the whole shtick, I should be able to do a lot more with my phone. I remember when I had to learn the ins and outs of my old Xperia Play. Horrible battery life and sub-par graphics chip but an awesome phone that had an awesome utility that could do just about anything with the phone with minimal work.
Click to expand...
Click to collapse
I think the problem here was that you tried to take an official update AFTER you messed with your phone... you should take this as a lesson to always flash back to stock before trying any 'official' updates, or better yet just have some patience for the updated files to show up here on the forums so you don't have to deal with OTAs at all. I don't really see the big rush to get the newest MI1 update anyway, it really doesn't provide any huge benefits at all and plus will possibly void your warranty through that stupid Knox thing if you try to root.
One thing I've learned is use patients dont jump the gun and if your not sure before you do something look here cause someone has already screwed up so the right way will be here somewhere and video will be on youtube!!
Hi,
I got a new phone last month, a HTC One (M8). Since I didn't need my S2 anymore, I decided to experiment a little bit with it, witch mean, I decided to try and root it. Man, i should never have done that.
First, I followed a guide on wikihow on how to root it. I downloaded Odin and the jeboo kernel they recommended in the guide. A couple minutes later, when everything was done, I tried to reboot my phone without much success. It was stuck on "Samsung Galaxy SII" with the yellow exclamation mark. Did I say that I got my phone from Virgin Mobile in Canada? Anyway, I tried to find a way to make my phone functional again and a couple of hours later, I found a stock Kernel that I immediately flash on my phone using Odin.
Everything worked fine again but I didn't want that outdated Android 2.2 so I installed Kies and plugged my phone in my computer to install the latest update from Samsung. Once again, I couldn't boot my phone, it would loop the Samsung animation over and over. So I re-install Gingerbread using Odin. Everything worked fine again!
But as I am stubborn, I didn't want it! So I search the web again for a solution. I red that cyanogen mod was great and I immediately wanted to try it. So I install everything and since it had an auto installer, I thought it would be very easy and in no time I would be able to play with it. Never have I been so wrong. For a reason that I don't know, the installer wasn't able to speak with my phone even thought I tried everything they said to do in this case.
Now, I can't boot my phone but I can boot in download and recovery mode. The only problem is, my computer doesn't install the drivers when I connect my phone, so I can't re-install 2.2 using Odin.
Anyone have any idea what I should do to solve this issue?
Please, help me 'cause I ****ed up
(Sorry for the mistakes, english is not my native language)
You did not screw anything.
If you can go to recovery, just boot into it, download any ROM you want and flash it through recovery(wipe data/cache/dalvik before you flash) and you'll be fine.
Second thing, once you root your phone, you void your warranty, and you CAN NOT update your phone from official samsung updates.You can do that if you unroot, but you won't need any updates.
Any way, as long as you can get into recovery, you're fine.
Also, what specific model; sticker on phone chassis under the battery ?
Nightshadow931 said:
You did not screw anything.
If you can go to recovery, just boot into it, download any ROM you want and flash it through recovery(wipe data/cache/dalvik before you flash) and you'll be fine.
Second thing, once you root your phone, you void your warranty, and you CAN NOT update your phone from official samsung updates.You can do that if you unroot, but you won't need any updates.
Any way, as long as you can get into recovery, you're fine.
Click to expand...
Click to collapse
Thanks mate, I will try this as soon as I can!
MistahBungle said:
Also, what specific model; sticker on phone chassis under the battery ?
Click to expand...
Click to collapse
It is a GT-I9100M.
Hi all. I just got my factory warranty back and I attempted to root it. Everything went as it should, until just after the install finished. Instead of rebooting normally, it now will only reboot into TWRP. Once there, when I try to flash a custom ROM (in this case, Bliss, but I don't think it matters, I get an error message that says the zip file is corrupt. Then, while still in recovery, when I tried to wipe everything except the sd card, it says mkfs.fat process ended with error. I then powered down and attempted the factory reset. I scrolled down on both screens and it did not say anything about any errors, so I assumed it took. However, it reboots right back into TWRP recovery. It also boots right to TWRP recovery when I try to boot normally. Of course, adb does not recognize the phone in any mode that I can get into (fastboot/recovery/download), so, I can't use LG Bridge to reflash the original firmware. Does anybody have any ideas for a fix? I know that this replacement phone had 6.0 on it. I thought I did everything to a t? TIA...
OK, not sure how I got there, but when I attempt to reboot from TWRP it says No OS Installed! Are you sure you want to reboot? That at least says what the problem is. Does anybody know how to fix this?
you have the latest twrp recovery? Just make sure you have 3.0 or higher and then try flashing again. And IMO the blissrom isnt worth using unless you dont mind smaller screen, no second screen, wonky Bluetooth and no camera.
AwesomeFabe said:
you have the latest twrp recovery? Just make sure you have 3.0 or higher and then try flashing again. And IMO the blissrom isnt worth using unless you dont mind smaller screen, no second screen, wonky Bluetooth and no camera.
Click to expand...
Click to collapse
Hey, I actually just fixed it. I finally was able to get back into download mode and I then used LG Bridge. Restoring now. Yeah, I actually picked it for some reason I cannot remember when I was faced with having to put in a custom rom as my option. I agree. When I had 5.1.1 everything worked after I got the bloatware out. Not going to get too fancy, I had a bit of a scare.
I think I'm screwed here. My tablet locked up and I force-powered it down. When it restarted, it went into a soft bootloop and won't load the OS. I'm able to get to my custom recovery and attempted to restore a backup I made in TWRP, but every time I try to restore it displays the screen shown in attached Pic 1, gets to 20% and reboots the tablet. I tried installing a custom ROM and got pretty much the same error (see Pic 2). I can't even wipe the device for some odd reason. All it does is reboot the system. I can get to the screen shown in Pic 3, but I'm not quite sure what my options are. Do I need to factory reset, or do I have a paperweight. I'll sideload if I have to, but I'm not sure of the best way to do this. I'm throwing myself on everyone's mercy here! AAAAAAAGH!
When all else fails, flashing the factory image with fastboot usually will solve the problems.
Sent from my SM-T820 using XDA-Developers Legacy app
jd1639 said:
When all else fails, flashing the factory image with fastboot usually will solve the problems.
Sent from my SM-T820 using XDA-Developers Legacy app
Click to expand...
Click to collapse
I tried flashing the factory image and it appears to have crapped out. See attached image. I think I got a real problem here .
Joe_6pak said:
I tried flashing the factory image and it appears to have crapped out. See attached image. I think I got a real problem here .
Click to expand...
Click to collapse
Think this is a better screencap.
Interesting that bootloader and recovery flash but then nothing else. Try downloading the factory image again. I have seen downloads being corrupted before.
jd1639 said:
Interesting that bootloader and recovery flash but then nothing else. Try downloading the factory image again. I have seen downloads being corrupted before.
Click to expand...
Click to collapse
Think I should stick with Nougat or download the original factory image (5.0, LRX21Q) that it shipped with? I've also heard rumors that it may be a faulty USP port or cable. Thoughts?
It should not matter which version of the factory image. It possibly could be a bad cable. Also, use the usb ports in the back of the computer, not the front, if you're using a pc. I haven't seen this being a problem with nexus devices but it has been on some samsung devices and odin.
jd1639 said:
It should not matter which version of the factory image. It possibly could be a bad cable. Also, use the usb ports in the back of the computer, not the front, if you're using a pc. I haven't seen this being a problem with nexus devices but it has been on some samsung devices and odin.
Click to expand...
Click to collapse
Okay. I used the back USB port and a different cable and I tried flashing the latest Nougat image. Went through without a hitch and it started up but hung on the splash screen and kept rebooting. Flashed the original image and the tablet started up but I got the dreaded "Enter your password" screen. Had NO idea what my password was, so I entered the first PIN that I thought I may have used. Well, that wasn't it, so it took me to a Factory Reset screen because it said I had corrupt data. After a lengthy "erasing" screen, the tablet fired up and I'm back where I started on Day 1. I have no idea if I am still rooted or if my custom recovery survived, but I'm kinda glad the thing at least got started again. My bootloader is still unlocked, and I made sure the "Enable OEM Unlock" box was checked in developer options. Since I just use this for games, email, video watching and an occasional Facebook glance, I'm really not concerned if I'm rooted or not. Obviously I'd like to be, but I'd rather make sure the tabled is updated by a download from Google first. I think my use of Flashfire is what screwed me up in the first place.
Long story short, I'm back up and running, but its 2014 all over again. Will I be able to take the factory update from Google with an unlocked bootloader, and will it be to the latest version of Android? Do you think my custom recovery survived, and is it worth the bother to root and flash it for a (mostly) gaming device? The only thing I can think of that I would want root for is Stickmount (to transfer files) and to get Google Assistant (which I'm pretty sure that I could back-door through Nova Launcher). Oh, yeah, and the adblocking. Let me know what you think. I TRULY appreciate the help, and I'm glad this resource is out there for noobs like me to make it through the Google menagerie.
By the way, does anyone think that going from system to systemless root is what may have caused this?
I'm glad you're up and running. System or systemless should not have made a difference. I'm sure you no longer have a custom recovery or are rooted. I'm guessing you will get an OTA update from Google
jd1639 said:
I'm glad you're up and running. System or systemless should not have made a difference. I'm sure you no longer have a custom recovery or are rooted. I'm guessing you will get an OTA update from Google
Click to expand...
Click to collapse
It took the update just fine. No Google Assistant, but I'll keep trying. Thanks a bunch. REALLY couldn't have done it without your help!
Joe_6pak said:
It took the update just fine. No Google Assistant, but I'll keep trying. Thanks a bunch. REALLY couldn't have done it without your help!
Click to expand...
Click to collapse
Google removed Assistant support from tablets
It doesn't seems to be working to root an S9+ 256GB DUOS SM-G965F (NEE - BRF8). NEE is Finland but it seems to be used in the whole Nordic.
After doing all the steps everything works but when the phone goes to sleep (the screen turns off and after a minute or two)) it will freeze (someone wrote it was AOD but it doesn't matter if it is running or not).
I also noticed the phone is lagging when using the startup guide, but it disappear after a reboot, but if i leave the phone and letting it fall in to sleep it will freeze and won't wake up again.
The only difference between "SuperSU 2.82-SR5" and "Magisk 16.6" is that with Magisk the phone is lagging at the startup guide and with SuperSU i have no SuperSU icon in apps to run.
And believe me, i have rebooted, but it won't help, no SuperSU icon. When the phone goes to sleep it freezes again.
I install TWRP with ODIN and Wiped the phone and rebooted into recovery, then i did:
1. no-verity-opt-encrypt-6.0-star.zip
2. rebooted into recovery
3. RMM-State_Bypass_Mesa.zip (i have even tryed RMM-State_Bypass_Mesa_v2.zip)
4. SR5-SuperSU-v2.82-SR5-20171001224502.zip (or Magisk 16.6)
5. samsung-antiroot-removal-2.4.zip (i have even tryed samsung-antiroot-removal-4.1.zip)
6. reboot and wait
The phone will always show the "OEM unlock" so i don't need to wait 7 days for it to appear.
Any advice on how i should proceed?
Additional information:
I have now restored the phone back to default (ODIN and the 4 firmware files) and now it won't freeze anymore and "OEM unlock" is still enabled with this text below "Bootloader is already unlocked". Unfortunately the phone isn't rooted now
It seems that if i only flash TWRP i get the same behavior, it freeze after a while after the screen has turn it self off.
Samsung galaxy s9+ 64GB
Hi, first thing I want to say is I registered on this site just now. This is my first reply so please be a bit forgiving if I'm doing something wrong. That said....
I have the exact same problem.
I have the s9+ 64GB SM-G965F.
Here's what I did...
I flashed twrp through Odin which works perfect. On reboot into recovery I formatted data.
Reboot into recovery again and flash no-verity.
Reboot into recovery again and flash RMM.
Without rebooting also flahed superSU and antiroot.
The versions of those files are the exact same as mentioned above and in all the guides....
After all this system reboots and starts up just fine.
All seems okay but when my screen turns off it freezes after a minute or so and the only remedy is a hard reset by holding volume down and power.
It reboots perfectly fine then but the same thing.
When the screen goes of it freezes..
At first I thought it could be the official Samsung firmware so I completely wiped the entire system and flashed resurrection remix rom. All works but when I root this rom the same thing happens. Only this time the root seems to work while flashing but on reboot there's no SuperSU app and it's not rooted according to root checker. Same thing with the freezing though....
So I downloaded the latest official firmware from Samsung, BRF8 I think. Flashed that through odin and all works fine. No freezing. But also no root and no twrp or any custom rom.
So I'm thinking it has to be the rooting that causes it. Tonight I will try to only flash twrp and flash no-verity and RMM, I'll leave the root itself out of it just to see what happens.
I'll post the results back here... If anyone has any ideas it would be appreciated very much!
OH another thing to mention.... I have had oem unlock activated all the time, I checked on each boot and it was always active for me too.....
SHOTOKANKATANA said:
So I'm thinking it has to be the rooting that causes it. Tonight I will try to only flash twrp and flash no-verity and RMM, I'll leave the root itself out of it just to see what happens.
Click to expand...
Click to collapse
If i only flash TWRP i get the same freeze. I used twrp-3.2.1-2-star2lte.
Oh... You beat me to it...
That's no good then, if it's caused by twrp there isn't much we can do I guess. It all starts with twrp.
I'm using the same version as you are.
Maybe we can try a previous version, I don't know what that's going to do though, if it would even be compatible...
I did find a separate official recovery file.
Maybe it's an idea to install the official recovery after acquiring root?
I'm not sure if the file is legit though, I've never done that before. Twrp always worked for me, on all phones I owned.
What's your though on that....?
I wondering if this should be reported to the Github issues log for TWRP? The problem seems to be TWRP.
Maybe we are doing something wrong I'm not sure.
I know I followed multiple guides up to the smallest detail. The result is the same every time. There's 1 thing I noticed though.
I'm using the BRF8 firmware as are you, maybe that's the problem? In the video guides they're mostly on BRE5.
It looks like it's just us with this issue. I can't find any other info on this particular matter...
I've posted this question on another thread.
Here's the link in case you want to follow....
https://forum.xda-developers.com/ga...cross-device-development/twrp-exynos-t3763464
I found the solution. I got it working now...
I installed twrp 3.2.1-1 instead of 3.2.1-2.
Has to be some kind of issue in the latest version...
I used the same install procedure as supposed to.
Only used the other twrp version.
My phone hasn't froze for the last 2 hrs so I'm pretty confident it's working now...
Ahhh cancel that. It just froze again!
Could you see if you can find the tmp/recovery.log?
On the github TWRP ask for it: "/tmp/recovery.log"
and the output of "dmesg" --> "/tmp/recovery.log"
really hoping we could find the fix for this.
The freeze happen because of the real time kernel protection. You need to flash custom kernel before root.
ione2380 said:
The freeze happen because of the real time kernel protection. You need to flash custom kernel before root.
Click to expand...
Click to collapse
LOL, it's right in the twrp instructions, including the phrase"flash custom kernel before root or be screwed"
Thanks you
The problem is solved.
vannsangha said:
Thanks you
The problem is solved.
Click to expand...
Click to collapse
What did you do? I'm still geting freezes with custom rom so i wondering what i'm doing from?
jagflashardinxbox360 said:
It doesn't seems to be working to root an S9+ 256GB DUOS SM-G965F (NEE - BRF8). NEE is Finland but it seems to be used in the whole Nordic.
After doing all the steps everything works but when the phone goes to sleep (the screen turns off and after a minute or two)) it will freeze (someone wrote it was AOD but it doesn't matter if it is running or not).
I also noticed the phone is lagging when using the startup guide, but it disappear after a reboot, but if i leave the phone and letting it fall in to sleep it will freeze and won't wake up again.
The only difference between "SuperSU 2.82-SR5" and "Magisk 16.6" is that with Magisk the phone is lagging at the startup guide and with SuperSU i have no SuperSU icon in apps to run.
And believe me, i have rebooted, but it won't help, no SuperSU icon. When the phone goes to sleep it freezes again.
I install TWRP with ODIN and Wiped the phone and rebooted into recovery, then i did:
1. no-verity-opt-encrypt-6.0-star.zip
2. rebooted into recovery
3. RMM-State_Bypass_Mesa.zip (i have even tryed RMM-State_Bypass_Mesa_v2.zip)
4. SR5-SuperSU-v2.82-SR5-20171001224502.zip (or Magisk 16.6)
5. samsung-antiroot-removal-2.4.zip (i have even tryed samsung-antiroot-removal-4.1.zip)
6. reboot and wait
The phone will always show the "OEM unlock" so i don't need to wait 7 days for it to appear.
Any advice on how i should proceed?
Additional information:
I have now restored the phone back to default (ODIN and the 4 firmware files) and now it won't freeze anymore and "OEM unlock" is still enabled with this text below "Bootloader is already unlocked". Unfortunately the phone isn't rooted now
It seems that if i only flash TWRP i get the same behavior, it freeze after a while after the screen has turn it self off.
Click to expand...
Click to collapse
Hey how do I restore my phone back to default. I have the same problem as you. My phone keeps freezing HELP PLEASE!
Benjamony said:
Hey how do I restore my phone back to default. I have the same problem as you. My phone keeps freezing HELP PLEASE!
Click to expand...
Click to collapse
I suggest you to download the latest Firmware from Sammobile for your Device and flash it with Odin .
Btw i would always check how to Recover my Phone before i do Modefication like this , then its much more easy to go back to Stock if something goes wrong .
Benjamony said:
Hey how do I restore my phone back to default. I have the same problem as you. My phone keeps freezing HELP PLEASE!
Click to expand...
Click to collapse
I'm running DevBase and it is now working perfect. Try to install it. I don't believe you need to go to stock first.
https://forum.xda-developers.com/ga...-development/rom-u1arc5-devbase-v5-2-t3764822
SHOTOKANKATANA said:
Maybe we are doing something wrong I'm not sure.
I know I followed multiple guides up to the smallest detail. The result is the same every time. There's 1 thing I noticed though.
I'm using the BRF8 firmware as are you, maybe that's the problem? In the video guides they're mostly on BRE5.
It looks like it's just us with this issue. I can't find any other info on this particular matter...
I've posted this question on another thread.
Here's the link in case you want to follow....
https://forum.xda-developers.com/ga...cross-device-development/twrp-exynos-t3763464
Click to expand...
Click to collapse
its not the csc. i'm on csf2 and i have the same problem