Related
i have to send my phone back to LG (or Google? not sure which one its actually going to end up at) because of overheating issues. they're sending me a replacement tomorrow with a shipping label for my old one to send back. they're holding funds for my new one until they've checked over the old one an verified that i do need a replacement, then if its all good they release the funds back into my account, but if its not all hunky dory they take the money, and i really can't afford that. i had it rooted and the bootloader unlocked and a custom kernel. i've flashed the stock kernel, unrooted and checked with Root Checker Basic, which tells me "Sorry! This device does not have proper root access". I've re-locked the bootloader, and checked that as well. I've flashed a few different things, including mod that makes the screen more sensitive, i've reverted that now though as it was to sensitive. i've also flashed lots of different ROMs including CyanogenMod, AOKP, Paranoid Android (i think thats the name) and more, a few weeks ago i flashed back to the stock rom, because i found problems with all the other ones. please ask if you need more information. back to the original question: will LG, or Google, whoever it goes to, be able to know that any of that has been done?
Thanks, Raf
rafspeik said:
i have to send my phone back to LG (or Google? not sure which one its actually going to end up at) because of overheating issues. they're sending me a replacement tomorrow with a shipping label for my old one to send back. they're holding funds for my new one until they've checked over the old one an verified that i do need a replacement, then if its all good they release the funds back into my account, but if its not all hunky dory they take the money, and i really can't afford that. i had it rooted and the bootloader unlocked and a custom kernel. i've flashed the stock kernel, unrooted and checked with Root Checker Basic, which tells me "Sorry! This device does not have proper root access". I've re-locked the bootloader, and checked that as well. I've flashed a few different things, including mod that makes the screen more sensitive, i've reverted that now though as it was to sensitive. i've also flashed lots of different ROMs including CyanogenMod, AOKP, Paranoid Android (i think thats the name) and more, a few weeks ago i flashed back to the stock rom, because i found problems with all the other ones. please ask if you need more information. back to the original question: will LG, or Google, whoever it goes to, be able to know that any of that has been done?
Thanks, Raf
Click to expand...
Click to collapse
No, if you flashed a factory image and the bootloader is locked they can`t tell what you flashed in the past .
gee2012 said:
No, if you flashed a factory image and the bootloader is locked they can`t tell what you flashed in the past .
Click to expand...
Click to collapse
i was reading this http://forum.xda-developers.com/showthread.php?t=1580829&nocache=1 and on the third post, bzmotoninja83 says that modern phones can detect bootloader locks/unlocks
rafspeik said:
i was reading this http://forum.xda-developers.com/showthread.php?t=1580829&nocache=1 and on the third post, bzmotoninja83 says that modern phones can detect bootloader locks/unlocks
Click to expand...
Click to collapse
Nope, not afaik. Samsung has binary flash counters (which can be reset though). Nexus devices don`t have that. So they look at the device as it comes in, not rooted and a locked bootloader.
gee2012 said:
Nope, not afaik. Samsung has binary flash counters (which can be reset though). Nexus devices don`t have that. So they look at the device as it comes in, not rooted and a locked bootloader.
Click to expand...
Click to collapse
great! thanks for your help
Hey guys i have a question for you:
So I got a galaxy s4 a few days ago and the first thing i did with it is root it, of course. But now when i boot it it shows the word SAMSUNG and a unlocked padlock underneath it that has the word custom under it. I did not install a custom rom. The booting procedure is fine. The phone boots up and works fine its just that i dont want people to think that i am using a custom rom or i hacked my phone. I mean i dont want people at the T-mobile store thinking that when i get my new sim. However, someone told me that using triangle away and reseting the flash counter will make it go away. Will it? I dont want to try yet because i dont want my phone being stuck in a bootloop (from my own experience). Thank you in advance.
BTW: I used towelroot to root my phone.
If you root ur phone it will ofcourse show as modified or custom.. If you want it to show as normal then you can use cosmetic sys scope normalizer xposed module or Wanam xposed.
Sent from my GT-I9500 using Tapatalk
Hello guys,please make sure you activate OEM UNLOCK in the developer options before you root your Android device with FRP installed. otherwise you risk to get into a bootloop after trying to boot into recovery due to FRP blocks custom binaries
have u tried using kies and using tools/firmware upgrade and putting your model number in and flashing with stock ? have you tried using odin and doin the same ?
jo01 said:
have u tried using kies and using tools/firmware upgrade and putting your model number in and flashing with stock ? have you tried using odin and doin the same ?
Click to expand...
Click to collapse
I am downloading the stock ROM now it takes a while. But how the hell can google tell me what i have to install and wehat not when i paid the phone? I am so pissed, its unbelievable. **** google and **** Samsung for letting this assholes do this.
Ok KIES does not even recognize my phone. The mworse is, it would start if it would not try to start into recovery. is there any option to remove the "recovery bit" or something like that and make the phone start normal and not into the recovery? That is my problem.
k now it is definately bricked, after i triedto flash a stock rom it says an error ocurred while recovery an i shall use smart switch but smart switch says unsupported device, i can not believe thishappened because of a google feature which no one asked for and they brick a device i bought for 800 bucks
OK FIXED, i had to flash via ODIN the Origin ROM, in my case the phone came from Italy and the Provider was TIM, it took me 7 Euro to download at Sammobile full speed and got it in 5 minutes.
Can be closed
I am in the same situation. I tried using the Recovery method with smart switcher or ODIN to flash the stock firmware but I am still stuck in a boot loop. I cannot access recovery at all and cannot install as the lock protection is on. Any other suggestions? I wasn't trying to root my phone it just decided to shut off and not boot up again.
this is quite concerning as i purchased my phone from Amazon Italy as it was cheaper than anywhere else but i was unable to root despite following the steps but i discovered it was because of the FRP, but i don't want a situation like this to happen, any more tips would be good, preferably without having to spend money from sam mobile too.
Brunkhorse said:
I am in the same situation. I tried using the Recovery method with smart switcher or ODIN to flash the stock firmware but I am still stuck in a boot loop. I cannot access recovery at all and cannot install as the lock protection is on. Any other suggestions? I wasn't trying to root my phone it just decided to shut off and not boot up again.
Click to expand...
Click to collapse
Im having the same problem. I can only access the download menu on the phone and all of my many attempts to flash or recover it failing with the phone saying "custom binary (recovery) blocked by FRP lock". I only know a limited amount about the rooting scene but if anyone could post a rom or something that would fix this or a method to remove the lock even with the smallest chance of success I definitately would give it a try(maybe a step by step as well please ) . Again there is no way i can see how to access anything on the device. My phone is the SM-G928W8 from Canada with Telus. Anything is worth a shot so if you have any ideas id love to hear them, thank you everyone :fingers-crossed:
ibstickboy said:
Im having the same problem. I can only access the download menu on the phone and all of my many attempts to flash or recover it failing with the phone saying "custom binary (recovery) blocked by FRP lock". I only know a limited amount about the rooting scene but if anyone could post a rom or something that would fix this or a method to remove the lock even with the smallest chance of success I definitately would give it a try(maybe a step by step as well please ) . Again there is no way i can see how to access anything on the device. My phone is the SM-G928W8 from Canada with Telus. Anything is worth a shot so if you have any ideas id love to hear them, thank you everyone :fingers-crossed:
Click to expand...
Click to collapse
YOu need to find a stock ROM, this will be the hardest part. AFter you have it, flash via ODin and the problem will be solved, i had the same problem. But you have to hurry because FRP also locks the charging of the battery so once you run out of battery you need to bring it to a technician.
jonny68 said:
this is quite concerning as i purchased my phone from Amazon Italy as it was cheaper than anywhere else but i was unable to root despite following the steps but i discovered it was because of the FRP, but i don't want a situation like this to happen, any more tips would be good, preferably without having to spend money from sam mobile too.
Click to expand...
Click to collapse
I spent the money because i needed it quick, if you download a stock ROM and have it left you can go ahead. YOu can download at SLOW MODE for free at sam
Brunkhorse said:
I am in the same situation. I tried using the Recovery method with smart switcher or ODIN to flash the stock firmware but I am still stuck in a boot loop. I cannot access recovery at all and cannot install as the lock protection is on. Any other suggestions? I wasn't trying to root my phone it just decided to shut off and not boot up again.
Click to expand...
Click to collapse
Check if you have the right stock ROm, it needs to be exactly the same country and provider. There is unfortunally no other way to remove FRP but booting the phone and remove the google account
can be deleted, i thought it works like on other subforums that new posting willl be added
please delete
Is it true that the battery doesn't charge after it's FRP locked? So the missing W8 firmware even if it comes eventually when the battery is dead the phone is dead? How in the hell are we supposed to fix this with no firmware available on sammobile?! Is there really no other way? Who has the firmware? Do the carriers have it?
thismonk said:
Is it true that the battery doesn't charge after it's FRP locked? So the missing W8 firmware even if it comes eventually when the battery is dead the phone is dead? How in the hell are we supposed to fix this with no firmware available on sammobile?! Is there really no other way? Who has the firmware? Do the carriers have it?
Click to expand...
Click to collapse
The battery is not locked (as far as I can tell), my phone got the lock when it was fully dead and while I was charging it and it seemed to have a charged battery after I unplugged from charging for awhile but there was no actual way to check. As for the firmware you will just have to wait for it my friend, that is the same firmware I needed and as of just now they still don't have it available on sammobile. Sorry man and best of luck
Needed? Did you end up getting the phone fixed by someone or send it back in to Samsung?
No I didn't get it fixed I sent it back to the phone company and paid a small fee rather than waiting for the firmware to be released.
Who was your phone company? I'm wondering because I can't seem to find anyone to help. I even contacted the local Samsung service center who deals with Telus and they told me that they could replace the mainboard but woudlnt flash the firmware or otherwise fix it. So that was rather useless I'm essentially buying a new phone.
thismonk said:
Is it true that the battery doesn't charge after it's FRP locked? So the missing W8 firmware even if it comes eventually when the battery is dead the phone is dead? How in the hell are we supposed to fix this with no firmware available on sammobile?! Is there really no other way? Who has the firmware? Do the carriers have it?
Click to expand...
Click to collapse
Absolutely right, if the battery runs out, you are lost. Then you have to bring it to the Samsung Service, they will fix it for you, if you pay of course..because KNOX will be void. The only way to avoid this is to remove your google account from the phone or enable under Developer Settings the OEM UNLOCK. Then FRP is disabled. But if you forgot and are now in a bootloop you have a real problem because as i have seen the W8 Firmware is not available on sammobile.
deepphrozen said:
Absolutely right, if the battery runs out, you are lost. Then you have to bring it to the Samsung Service, they will fix it for you, if you pay of course..because KNOX will be void. The only way to avoid this is to remove your google account from the phone or enable under Developer Settings the OEM UNLOCK. Then FRP is disabled. But if you forgot and are now in a bootloop you have a real problem because as i have seen the W8 Firmware is not available on sammobile.
Click to expand...
Click to collapse
My battery ran out but the phone is actually still working. When I plug it in via USB it powers up. It doesnt' actually charge the battery, but this will work for Odin. Now I just need to find someone to dump the stock firmware for me...
Any updates on a firmware?
If you need to go to stock then have you tried to boot I to download mode and use smartswitch reinstall feature?
thismonk said:
My battery ran out but the phone is actually still working. When I plug it in via USB it powers up. It doesnt' actually charge the battery, but this will work for Odin. Now I just need to find someone to dump the stock firmware for me...
Click to expand...
Click to collapse
I have same Problem as all of you but haven't fixed it yet because I still haven't found right ROM but if you have wireless charger it will force charge!! ??
Hi There,
My colleague complained that he had an OTA update on his Nexus 6P and the after the update it was stuck in a boot loop where the Google logo keep on displaying.
When he bought back, he had showed it a shop already which they said they couldn't fix. However, the phone was later given to me for help and I have somehow manage to connect the device on fastboot and adb. Tried all the possible options such as unlocking the bootloader, loading .img's one by one... sideloading... etc.
No matter what I do, it keeps on doing the same boot loop. And when I leave the bootloader unlocked, it gives an error at first, then again goes back to the same.
Not sure whether what I am doing wrong or whether am I choosing the wrong build or so... would anyone care to advise?
.G33K said:
Hi There,
My colleague complained that he had an OTA update on his Nexus 6P and the after the update it was stuck in a boot loop where the Google logo keep on displaying.
When he bought back, he had showed it a shop already which they said they couldn't fix. However, the phone was later given to me for help and I have somehow manage to connect the device on fastboot and adb. Tried all the possible options such as unlocking the bootloader, loading .img's one by one... sideloading... etc.
No matter what I do, it keeps on doing the same boot loop. And when I leave the bootloader unlocked, it gives an error at first, then again goes back to the same.
Not sure whether what I am doing wrong or whether am I choosing the wrong build or so... would anyone care to advise?
Click to expand...
Click to collapse
So the bootloader is unlocked? Exactly which build have you attempted to flash with fastboot? Have you tried flashing one of the full OTA zips with the stock recovery?
PS. Whatever you do don't lock the bootloader. And don't worry about the warning you get with the bootloader unlocked, that's normal.
Heisenberg said:
So the bootloader is unlocked? Exactly which build have you attempted to flash with fastboot? Have you tried flashing one of the full OTA zips with the stock recovery?
PS. Whatever you do don't lock the bootloader. And don't worry about the warning you get with the bootloader unlocked, that's normal.
Click to expand...
Click to collapse
Thank you for the reply.. I have only locked the bootloader when I'm done with flashing... etc as it was giving me error. Regardless of the bootloader state, it kept on going through the bootloop like it didn't care.
I tried to flashing the factory image which is MTC19T and also tried the OTA which is MTC19V as said in here.
Still there's not luck!
.G33K said:
Thank you for the reply.. I have only locked the bootloader when I'm done with flashing... etc as it was giving me error. Regardless of the bootloader state, it kept on going through the bootloop like it didn't care.
I tried to flashing the factory image which is MTC19T and also tried the OTA which is MTC19V as said in here.
Still there's not luck!
Click to expand...
Click to collapse
Don't worry about the warning and definitely don't lock the bootloader because if it gets stuck locked you'll really be screwed. Go to my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow the instructions in section 10 (use the latest MTC19X build). Skip the part at the beginning about performing a factory reset because you can't actually get the phone to boot to do that. Make sure you include the "fastboot format userdata" command at the end (this will erase all data on the device). Leave the bootloader unlocked.
Heisenberg said:
Don't worry about the warning and definitely don't lock the bootloader because if it gets stuck locked you'll really be screwed. Go to my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow the instructions in section 10 (use the latest MTC19X build). Skip the part at the beginning about performing a factory reset because you can't actually get the phone to boot to do that. Make sure you include the "fastboot format userdata" command at the end (this will erase all data on the device). Leave the bootloader unlocked.
Click to expand...
Click to collapse
I have actually tried doing what section 10 says but with a different stock build.. Does that effect as well? However, let me give another shot with your said build and post back.
.G33K said:
I have actually tried doing what section 10 says but with a different stock build.. Does that effect as well? However, let me give another shot with your said build and post back.
Click to expand...
Click to collapse
Did you format userdata? It's worth a try.
Heisenberg said:
Did you format userdata? It's worth a try.
Click to expand...
Click to collapse
Yes, sire! I did all the possible things I could do without harming or bricking the device... Read each and every instruction carefully to do... but turned with no luck... however, I'm due to try the method and build you have suggested, I shall try that and get back to you!
.G33K said:
Yes, sire! I did all the possible things I could do without harming or bricking the device... Read each and every instruction carefully to do... but turned with no luck... however, I'm due to try the method and build you have suggested, I shall try that and get back to you!
Click to expand...
Click to collapse
It probably won't work, any build should work, but it's worth a try. If that fails I can only suggest flashing TWRP recovery and trying to flash a custom ROM to see if that works.
So long as you have the bootloader.img and radio.img files, you can try to format boot as well, however Heisenberg may yell at me for even typing that
I had a similar issue - bootloop, but it was getting to the boot animation for about 3 seconds, then rebooting. When I formatted all the areas before flashing them from the stock image, it allowed me to boot up as normal. Stable ever since.
Hi There,
Coming back to the issue, I have just downloaded the build that was suggested by "Heisenberg" and tried it. It was still the same, as in the Google logo keep on flashing but the android bot just appeared once with the logo. But still there not luck as the device stays with Google logo but does nothing.
However, I'm able to see the device on fastboot. Nevertheless, I cannot seem to use adb command.. it doesn't even list on devices. Does that mean the adb isn't working?
Meanwhile, all my fastboot commands are working with no issues at all.
EDIT: When I tried the TWRP recovery, I can flash the recover, but I can seem to go to the recovery window at all as the device keep on showing "The device software can't be checked for corruption". When I pass that also the same boot loop.
I too am having the bootloop issue on my stock Nexus 6P. Is there a way to unlock the device from the bootloader? I'm unable to carry out step one on Heisenberg's guide because I'm unable to actually boot up my phone past the Google logo. Am I pretty much screwed?
bcjk8210 said:
I too am having the bootloop issue on my stock Nexus 6P. Is there a way to unlock the device from the bootloader? I'm unable to carry out step one on Heisenberg's guide because I'm unable to actually boot up my phone past the Google logo. Am I pretty much screwed?
Click to expand...
Click to collapse
Unfortunately yes. Unless you enabled OEM Unlocking in the developers menu before your phone went sideways you probably have a hard bricked phone. Is it under warranty?
I went through this in November with a completely stock Nexus 6P. I was 3 days past my one year warranty! Google would not send me a new phone. It was completely bricked by the OTA update I received! I was put in touch with Huawei. I had to send the bricked phone to them. 10 days later I received a working model back. Unacceptable that an OTA update trashes a one year old $650 phone. Luckily I had my OnePlus One still, and was able to use that while I waited. I was even able to update that to 7.1.1 since it was rooted. Obviously there is some sort of issue that we are not being told of regarding the dangers of accepting OTA updates on a stock/bootlocked phone.
TemplesOfSyrinx said:
I went through this in November with a completely stock Nexus 6P. I was 3 days past my one year warranty! Google would not send me a new phone. It was completely bricked by the OTA update I received! I was put in touch with Huawei. I had to send the bricked phone to them. 10 days later I received a working model back. Unacceptable that an OTA update trashes a one year old $650 phone. Luckily I had my OnePlus One still, and was able to use that while I waited. I was even able to update that to 7.1.1 since it was rooted. Obviously there is some sort of issue that we are not being told of regarding the dangers of accepting OTA updates on a stock/bootlocked phone.
Click to expand...
Click to collapse
Bootloop issues are common on the 6P even with custom ROMs--it just happens to be much more likely you can recover with the custom ROMs installed since the bootloader is unlocked. I think it's a hardware issue with the 6P rather than an OTA issue. It's probably not an accident that Huawei didn't make the Pixels.
Doesn't seem right that I have to "void" my warranty and install a custom ROM on an unlocked, rooted phone in order to recover from a hardware defect. That's BS pure and simple. I want to use the latest software, that's why I bought a Nexus. I want to use all the conveniences like Android Pay. That's why I don't unlock or root anymore. I rooted every Android phone I ever had until now, starting with the original Motorola Droid. Now that security is so important to Google, and you can't use all the Android features with an unlocked bootloader, they need to step up to fix these problems.
This happened to my wife's phone, sent back to Bell. Will see what happens.
TemplesOfSyrinx said:
Doesn't seem right that I have to "void" my warranty and install a custom ROM on an unlocked, rooted phone in order to recover from a hardware defect. That's BS pure and simple. I want to use the latest software, that's why I bought a Nexus. I want to use all the conveniences like Android Pay. That's why I don't unlock or root anymore. I rooted every Android phone I ever had until now, starting with the original Motorola Droid. Now that security is so important to Google, and you can't use all the Android features with an unlocked bootloader, they need to step up to fix these problems.
Click to expand...
Click to collapse
Unlocking the bootloader doesn't void the warranty on the Nexus 6P. If you are under warranty then just RMA the phone if an OTA bootloops your phone. It's your choice whether to keep the bootloader locked or not but if you keep the bootloader locked it's probably impossible to recover from a bootloop. Google keeps factory images for Nexus and Pixel phones on its website but you can't flash those images with a locked bootloader. Why would they provide the images if using them voided your warranty?
You are missing my point. If I unlock my bootloader so I can recover from a boot loop that may happen, I will no longer be able to use a huge feature of the phone. Android Pay will no longer function. In days passed the rumour was your warranty was void if you unlock. I assume that was started to keep people from doing it. All I know is I paid good money for a phone that is a disaster waiting to happen it seems.
If having an unlocked bootloader is so important to recover from a bricked phone, why do they lock it in the first place? And why won't Android Pay work with it unlocked? The answer is that you no longer have a secure phone if you unlock the bootloader.
bcjk8210 said:
I too am having the bootloop issue on my stock Nexus 6P. Is there a way to unlock the device from the bootloader? I'm unable to carry out step one on Heisenberg's guide because I'm unable to actually boot up my phone past the Google logo. Am I pretty much screwed?
Click to expand...
Click to collapse
What Android version you had on your phone? What's your emmc name and ram name in bootloader? What's the manufacturing date in bootloader?
TemplesOfSyrinx said:
You are missing my point. If I unlock my bootloader so I can recover from a boot loop that may happen, I will no longer be able to use a huge feature of the phone. Android Pay will no longer function. In days passed the rumour was your warranty was void if you unlock. I assume that was started to keep people from doing it. All I know is I paid good money for a phone that is a disaster waiting to happen it seems.
If having an unlocked bootloader is so important to recover from a bricked phone, why do they lock it in the first place? And why won't Android Pay work with it unlocked? The answer is that you no longer have a secure phone if you unlock the bootloader.
Click to expand...
Click to collapse
I think you bought the wrong phone. Nexus devices were never available commercially through carriers and were made for developers and people who like to flash things with their phones. There are ways to use Android Pay with an unlocked bootloader if you are so inclined. You are right that an unlocked bootloader is considered less secure but if you only install apps from Google Play or another trusted source you shouldn't have problems. You can also simply enable allow Oem Unlock in the developer menu. This doesn't actually unlock your bootloader but makes it possible for you to unlock it via fastboot if you get bootlooped and need to flash a factory image to restore. This way you can unlock the bootloader in an emergency but your phone is still secure. I think this should be enabled by default when the phones are shipped. Too many people with locked bootloaders end up with hard bricked phones where the Nexus 6P is concerned. Honestly, you would probably be better off selling your Nexus and getting something else that's more stable and made for people who have no Interest in flashing anything.
Let me start by saying I never gave rooted phones much though. I knew of them but never even knew anyone that ever had one. I figured the Galaxy S8 (G950U) would be a good phone to start with:laugh: Since it was my first rooted phone I couldn't resist experimenting, a lot. So I would flash this flash that, whatever I thought had a very small chance of working i flashed, lol. I usually would end up having to fireing up Odin and flashing the most important files on my PC, Partcyborg's awesome work, which I can flash with my eyes closed basically by now :laugh: Some things I would flash would just cause me to lose root though. It's driving me nuts not to be able to get it back without Odin. I could use Odin+Partcyborg's rom and have it back in 15 minutes, but I'm tired of being feed I'm ready to hunt, lol.
The thing is, I still have TWRP Safestrap custom recovery that I can access. I flash Supersu, it appears to flash fine but changes nothing, not even an SU icon in the app drawer. I did make SupoerSU Pro a system app a while ago, was that a mistake? I see it in the Apps list in Settings but I can't do much there except disable it and enable it (no it's not disabled,lol)
How can I get root back using custom recovery only? What should I have checked in Safestrap when flashing SuperSU?, Cache, System, Modem, etc? If anyone would care to explain some of the reasons I lose root but not custom recovery it would really calm my curiosity . I'm sure it would help a lot of other noobs also.
Boot animations is another thing that I find very interesting. Trying to change it has been the cause of at least 10 factory resets
I go to /system/media/ and swap out Booitanimation.zip, change the permission then I either get no change or I have reflash with Odin. What is all the files labeled Battery _000 Battery _001 Battery_002 all the way to Battery_100? Does the resolution need to be exactly the same as stock?
Is my rooted S8 not as rooted as other rooted phone? Lol, does that sentence make sense? Because of its locked bootloader and lack of custom roms is why I ask. Am I an idiot for buying a S9+ (G965U) since I love having root? I was hoping someone "cough...Part...cough cough...cyborg would be on it. If not though, no big deal. I do still have the S8 and still use it a lot even though it has no service, lol. Amazing phones not so amazing bootloaders though:laugh:
Thanks for reading. If you only skimmed it, thank you also. I know it's very long, lol. I just found something called a Combination Rom. Since I still have Safestrap I'm gonna do what I usually do, flash it and ask questions later:laugh:
Gregbmil1 said:
Let me start by saying I never gave rooted phones much though. I knew of them but never even knew anyone that ever had one. I figured the Galaxy S8 (G950U) would be a good phone to start with:laugh: Since it was my first rooted phone I couldn't resist experimenting, a lot. So I would flash this flash that, whatever I thought had a very small chance of working i flashed, lol. I usually would end up having to fireing up Odin and flashing the most important files on my PC, Partcyborg's awesome work, which I can flash with my eyes closed basically by now :laugh: Some things I would flash would just cause me to lose root though. It's driving me nuts not to be able to get it back without Odin. I could use Odin+Partcyborg's rom and have it back in 15 minutes, but I'm tired of being feed I'm ready to hunt, lol.
The thing is, I still have TWRP Safestrap custom recovery that I can access. I flash Supersu, it appears to flash fine but changes nothing, not even an SU icon in the app drawer. I did make SupoerSU Pro a system app a while ago, was that a mistake? I see it in the Apps list in Settings but I can't do much there except disable it and enable it (no it's not disabled,lol)
How can I get root back using custom recovery only? What should I have checked in Safestrap when flashing SuperSU?, Cache, System, Modem, etc? If anyone would care to explain some of the reasons I lose root but not custom recovery it would really calm my curiosity . I'm sure it would help a lot of other noobs also.
Boot animations is another thing that I find very interesting. Trying to change it has been the cause of at least 10 factory resets
I go to /system/media/ and swap out Booitanimation.zip, change the permission then I either get no change or I have reflash with Odin. What is all the files labeled Battery _000 Battery _001 Battery_002 all the way to Battery_100? Does the resolution need to be exactly the same as stock?
Is my rooted S8 not as rooted as other rooted phone? Lol, does that sentence make sense? Because of its locked bootloader and lack of custom roms is why I ask. Am I an idiot for buying a S9+ (G965U) since I love having root? I was hoping someone "cough...Part...cough cough...cyborg would be on it. If not though, no big deal. I do still have the S8 and still use it a lot even though it has no service, lol. Amazing phones not so amazing bootloaders though:laugh:
Thanks for reading. If you only skimmed it, thank you also. I know it's very long, lol. I just found something called a Combination Rom. Since I still have Safe-strap I'm gonna do what I usually do, flash it and ask questions later:laugh:
Click to expand...
Click to collapse
so the boot animations off top of my head are now located in something something and your carriers folder...The can be changed
Is it actually not rooted or is su just not responding
I have had it where the prompt never comes up and granting all just never works either normally a few reboots later it starts....
the custom rom thing is most def cause of locked boot-loader....
Up til boot-loader revision 2 is all we have root for and cannot be downgraded 3 and up....
I have myself tried flashing stock system img and then su and busy box from safe strap and up til now even this has been a no go...
Safe-strap is cool but basically No better than flashfire.IMO.
I am working with the possible bluetooth fix right now and have bricked and flashed 20 times over in the last 12 hours...
It actually is not rooted anymore after I flashed what claimed to be a boot animation for the G950U. If I open the SuperSU app it points me to a non-working site that has directions on "How to root". Plus all of the apps I have downloaded that require root all tell me I'm not rooted. Oddly enough though I was able to flash Xposed and had a green light once I opened it, (remember I still had SafeStrap recovery) it could only be accessed manually. I was shocked and yet even more confused, lol. I only tried out 2 modules before I reflashed Partcyborgs files again. Again, I was very confused as to why the modules actually worked but root only apps would start , only Xposed modules. I did only try 2 though AdBlocker Reborn and SpeedUp, both acted as if everything was normal . I wonder if it had something to do with making SuperSU a system app, which it no longer is since I reflashed with Odin.
Thanks for the info on the Bootanimation, but still I can't even delete the one I have now, for educational purposes only, Haha. It is a pretty freaking sweat bootanimtion Partcyborg included. I can't find it though T-Mobile (G950U) btw