Im not sure if this is the right place to post this, but I attempted to root my phone last night, which I did successfully. My carrier (telstra, australia) is really ****ty with releasing updates so I'm still on 5.0.2. So I followed these instructions to update to 5.1.1: http://forum.xda-developers.com/showpost.php?p=60112855&postcount=3
I did that, and when my phone rebooted it got stuck on the boot screen with "Kernel rev. Check failure".
I have tried to flash my carriers stock 5.0.2 firmware with Odin, but that has currently not fixed it. Do i need to wait until they release 5.1.1? Or can I use any countries 5.1.1, for example, im currently downloading a stock 5.1.1 firmware from India. Will that work?
I don't know what else to do.
I think where I went wrong was not installing a custom kernel other than Supersu, which I now realise thats what the previously linked instructions said. I rooted with Ping Pong root, so I do have SuperSU installed on my phone, but I do not have TWRP.
I know, i'm a dumbass. What can i do?
Related
Hi guys
I just got my wife a Samsung Galaxy S3 I747 for ATT using Straight Talk. I purchased one for my self about 3 months ago, same model. Both were purchased used, mine had 4.1.2 and my wife's has 4.1.1. I rooted and installed CWM Recovery on mine. I wanted to update my wife's to at least 4.1.2 like mine or even 4.1.3.
From my understanding, once you root and install a recovery mod, such as TWRP or the ClockWorkMod Recovery, that your phone will not be able to update via your service provider.
The problem is, I got her phone yesterday, and I tried to update it, but it kept saying it was at the latest update/firmware. I even installed Kies, but it reported the same thing. After a few hours, I decided I would root it and install TWRP and maybe install a new ROM with the FW on it later. Well, this morning, the phone reported that an important update was available. Somewhat confused, b/c I thought it couldn't be the FW b/c yesterday it said the phone was at the latest FW, and plus the fact the update is, as I thought, refused by the service provider or phone, when it is rooted or a recovery mod is installed. When it finished, of course it asked to reboot. I was curious how this was going to play out.
When it rebooted, it loaded the TWRP Recovery. Being still new to all this, I wasn't sure how to proceed, so I clicked the reboot button, but nothing happen, so I tried the shutdown button. The phone powered off with no issues. I turned it back on and it loaded successfully to the home screen. I checked the status of the update, and it said it failed. No surprise there, I'm just happy it didn't brick her phone during the process.
Is this normal? Should I just disable updates from my provider? Is it possible to install the update and then just reapply the root and recovery mod?
Thanks
Mike
Modify_inc said:
Hi guys
I just got my wife a Samsung Galaxy S3 I747 for ATT using Straight Talk. I purchased one for my self about 3 months ago, same model. Both were purchased used, mine had 4.1.2 and my wife's has 4.1.1. I rooted and installed CWM Recovery on mine. I wanted to update my wife's to at least 4.1.2 like mine or even 4.1.3.
From my understanding, once you root and install a recovery mod, such as TWRP or the ClockWorkMod Recovery, that your phone will not be able to update via your service provider.
The problem is, I got her phone yesterday, and I tried to update it, but it kept saying it was at the latest update/firmware. I even installed Kies, but it reported the same thing. After a few hours, I decided I would root it and install TWRP and maybe install a new ROM with the FW on it later. Well, this morning, the phone reported that an important update was available. Somewhat confused, b/c I thought it couldn't be the FW b/c yesterday it said the phone was at the latest FW, and plus the fact the update is, as I thought, refused by the service provider or phone, when it is rooted or a recovery mod is installed. When it finished, of course it asked to reboot. I was curious how this was going to play out.
When it rebooted, it loaded the TWRP Recovery. Being still new to all this, I wasn't sure how to proceed, so I clicked the reboot button, but nothing happen, so I tried the shutdown button. The phone powered off with no issues. I turned it back on and it loaded successfully to the home screen. I checked the status of the update, and it said it failed. No surprise there, I'm just happy it didn't brick her phone during the process.
Is this normal? Should I just disable updates from my provider? Is it possible to install the update and then just reapply the root and recovery mod?
Thanks
Mike
Click to expand...
Click to collapse
It is perfectly normal. You described the expected sequence for a phone with any custom recovery. OTA updates download then reboot into stock recovery. Absent that ..what you said.
For your update path, I. urge you to visit xda's i747 forum & read up on the controversy & pitfalls of AT&T's OTA 4.3
Look out for:
locked bootloader
Knox Warranty bit
one way upgrade
(on pain of brick)
It's different this time around.
So I have an Australian (Telstra) S6 Edge 925I with stock firmware (OD1) android version 5.0.2 kernel build April 1st.
PingPong root didn't work (and obviously was ruled out also because of kernel build date)
CF Auto-root has just been sending phone into bootloop, have tried a few variants (925i, 925F, 920f, 920t)
Also tried a kernel flash (as if the phone was on 5.1.1) but just got phone stuck on boot screen.
Tried a TWRP flash, got TWRP to work but bootloop also.
-- I do have a stock firmware that I have flashed to get phone back to normal each time it has soft-bricked.
So it seems that rooting is turning out to be pretty impossible but I have seen so much success for others!
Any help would be greatly appreciated!
[also this could be the wrong place to post so redirect or whatever if you have to]
THanks!
Try the Android unified toolkit. It will help you root the proper way for your variant.
http://forum.xda-developers.com/gal...lkit-skipsoft-android-toolkit-galaxy-t3101195
Unfortunately, toolkit didn't work for me. When I was going through root process, I flashed TWRP; latest version caused some weird brightness/colour issue so I couldn't use it, flashed the recommended version, and touch screen wouldn't work. Flashed a version in between which worked, but couldn't boot into OS because of bootloop.
So unfortunately I'm still quite stuck. Toolkit seems like a great tool though, if only it would work. I'm certain I'm not doing anything wrong.
So I paid ("donated") for the pro version so I could get it done that way... Yep, device still went into bootloop... Not sure what's going here but now I have also wasted money.
in 5.1.1 you need to have a custom kernel flashed..look into my twrp thread..
CF Auto Root updated and works on my Phone. S6 Edge 925I
Still having trouble installing a recovery though
Hello Everyone,
I'm a first time poster but have been reading this site for weeks trying to find the answer to my questions. I've acquired a good bit of info but still wanted to clarify some things before I take the plunge.
I'm currently using a Verizon GS4 (I-545) running rooted stock MK2 jellybean. I rooted ~2 years ago to get rid of the bloatware and just never bothered upgrading/keeping up with the firmware updates. There are some new apps that won't work on my phone, but are working on my wife's stock GS4 on OF1. I'd like to upgrade my firmware (and keep root) so that I don't have to keep stealing her phone.
I've come across several threads discussing upgrading from one baseband to the next - none quite match my scenario. Most threads talk about how to upgrade and keep root but now that I'm late to the party, it seems like root methods have been discovered for all stock firmware versions (even OF1 by flashing OC1 kernel, rooting, and flashing back to OF1 kernel). So with this in mind, can I just skip all the complicated stuff and just use Odin to flash OF1 and then follow Edgardo_Uchicha's OF1 root method?
If I can use Odin to flash OF1, will the file I load in the "AP" slot also includes the proper modules, bootloaders, etc. to upgrade everything to OF1? Will it do a factory reset/wipe or will I keep all my data like an OTA? As for getting the Odin file, it looks like I should just use the Samsung site to get it directly?
If I can use the Odin method, are there any drawbacks? If I don't like lollipop I realize I'm stuck and can't go back, but is there anyway to upgrade and be able to go back (downgrade)?
Thanks again for your help!
Mike
Hello Mike,
You can flash OF1 and root via the method others and I posted, some people wrote that other rooting software/apps are starting to work on lollipop builds, I haven't tested yet(since my device have a custom rom and it's rooted) but soon I will and will update the thread. Btw, my suggestion to you is flashing this specific odin package:
[Odin][TAR] I545VRUGOF1 neutered (No BL)
I was on kitkat bootloader, flashed this OF1 build and went back to kitkat without problems
Good luck!
Edgardo_Uchiha said:
Hello Mike,
You can flash OF1 and root via the method others and I posted, some people wrote that other rooting software/apps are starting to work on lollipop builds, I haven't tested yet(since my device have a custom rom and it's rooted) but soon I will and will update the thread. Btw, my suggestion to you is flashing this specific odin package:
[Odin][TAR] I545VRUGOF1 neutered (No BL)
I was on kitkat bootloader, flashed this OF1 build and went back to kitkat without problems
Good luck!
Click to expand...
Click to collapse
So I followed the thread you linked and it looked like my phone upgraded OK. However, even at lock screen I get the message "Unfortunately, the process com.android.phone has stopped". It reappears as soon as I dismiss it...basically making my phone useless. I was able to navigate to the Settings page though and it says I'm on 5.0.1 but under baseband it says "Unknown" rather than OF1. It does show OF1 under the build number though. I'm guessing it didn't like the MK2 bootloader?
Any ideas how to fix? Help!!
mike2914 said:
So I followed the thread you linked and it looked like my phone upgraded OK. However, even at lock screen I get the message "Unfortunately, the process com.android.phone has stopped". It reappears as soon as I dismiss it...basically making my phone useless. I was able to navigate to the Settings page though and it says I'm on 5.0.1 but under baseband it says "Unknown" rather than OF1. It does show OF1 under the build number though. I'm guessing it didn't like the MK2 bootloader?
Any ideas how to fix? Help!!
Click to expand...
Click to collapse
Try wiping via recovery, if I'm not wrong this package does not wipe your phone so maybe there are some leftovers that are messing up the new system
You are correct, the OF1 Odin file you recommended did not wipe my data/apps. You were also correct in that doing a factory reset/wipe fixed the issue. I had some apps that were previously "frozen/disabled" while I had root so I have a feeling that didn't help things when it got updated.
Is there any way to confirm that I still have the MK2 bootloader?
mike2914 said:
You are correct, the OF1 Odin file you recommended did not wipe my data/apps. You were also correct in that doing a factory reset/wipe fixed the issue. I had some apps that were previously "frozen/disabled" while I had root so I have a feeling that didn't help things when it got updated.
Is there any way to confirm that I still have the MK2 bootloader?
Click to expand...
Click to collapse
Download and install terminal emulator, the run these commands:
1. su
2. getprop ro.bootloader
Awesome! I was able to confirm I'm still using the MK2 bootloader. Thanks for all your help!
Ok so hopefully i can get some help with my issue here. I have just resurrected my S4 i thought was dead, but it had the power button sticking problem, and now after about 3 years its going again! This is my problem tho. I got this phone early in the releases. Rooted while on 4.3, unlocked my bootloader on 4.3, ran many ROMS and tons of flashing with no problems. Currently the phone is (ironically) running Ressurrection Remix KK V5.1.0. My Baseband version still states 1545VRUAMDK. I have been trying to get everything up to date but nothing is working right. Im on TWRP version 2.6.0 and yes i have been into recovery since getting it working again. One time when trying to update TWRP i got the Unautorized Software yellow sign sceen. Booted to Download mode and cancelled. I cant get it back into Recovery now and my TWRP wasnt updated. How has my phone became locked again, and how can i fix this? Thanks
If your really still on MDK you can just reunlock your bootloader. Any higher and your stuck on stock, or you could try your luck with flashfire but it only works with touchwiz rims and when I used it on my old s4 it hard bricked it.
You have soft-bricked
Use Odin and flash the no-wipe tar of MDK while in download mode then re-root, etc. You need to use Flashfire to update TWRP. I did the same thing as you recently testing ROM installation with different versions of TWRP. If you update by flashing the img file via TWRP it soft bricks, I found out the hard way.
Hi
I live in Canada so my model # SM-G925W8. I recently bought this phone from someone and noticed that they had it rooted. So I put it back to official stock and it was at 5.0.2 Lollipop and I know there is a more up-to-date Lollipop version and even a Marshmallow version but when I went to check for updates it said I had the latest official update for my phone.
I was kind of disappointed and rooted my device again...
Anyhow after a week went by I went to "fw.updato.com" as suggested by a XDA thread and download a Marshmallow update for my carrier.
I went to supersu and full unrooted
I fully wiped / resetted the phone
I went to odin mode and installed the Marshmallow update
Okay, so anyhow all seemed fine but when I went to boot up my phone I got a DRK (Device Root Key) issue. I figured id just wipe and try again, I even tried downgrading but it wouldn't let me.
I was very scared my phone was hard bricked. So anyhow I decided to flash CF-Auto Root and somehow that managed to fix or bypass the DRK issue and I booted up into Marshmallow! All seemed good in the world. I however noticed my finger print scanner was no longer working saying it was dirty or whatever but it was working with Lollipop.
Anyhow, long story short , I would like to go back to stock but I keep running into the DRK problem. The only thing that seems to let me boot into my phone is the CF-Auto Root and as long as im root I can never have it as Official.
Any suggestions?
Thank you!
~ I would seriously pay $50 for a working solution, I realize I F* up pretty bad somehow. ~
FriendsFade said:
Hi
I live in Canada so my model # SM-G925W8. I recently bought this phone from someone and noticed that they had it rooted. So I put it back to official stock and it was at 5.0.2 Lollipop and I know there is a more up-to-date Lollipop version and even a Marshmallow version but when I went to check for updates it said I had the latest official update for my phone.
I was kind of disappointed and rooted my device again...
Anyhow after a week went by I went to "fw.updato.com" as suggested by a XDA thread and download a Marshmallow update for my carrier.
I went to supersu and full unrooted
I fully wiped / resetted the phone
I went to odin mode and installed the Marshmallow update
Okay, so anyhow all seemed fine but when I went to boot up my phone I got a DRK (Device Root Key) issue. I figured id just wipe and try again, I even tried downgrading but it wouldn't let me.
I was very scared my phone was hard bricked. So anyhow I decided to flash CF-Auto Root and somehow that managed to fix or bypass the DRK issue and I booted up into Marshmallow! All seemed good in the world. I however noticed my finger print scanner was no longer working saying it was dirty or whatever but it was working with Lollipop.
Anyhow, long story short , I would like to go back to stock but I keep running into the DRK problem. The only thing that seems to let me boot into my phone is the CF-Auto Root and as long as im root I can never have it as Official.
Any suggestions?
Thank you!
~ I would seriously pay $50 for a working solution, I realize I F* up pretty bad somehow. ~
Click to expand...
Click to collapse
Use samsung smart Switch To restore it to factory Defaults
Samsung SmartSwitch detects my device and allows me to backup and restore but it doesn't work for resetting.
It says, "Unable to find the serial number, model name, or IMEI on the server"
When I do a manual lookup and when I connect device and try I think it says it can't initialize.
Smart Switch & Kies never worked even when I was on official.
My model is SM-925W8
Can I get the firmware without them?
Model Name - SM-G925W8
When I was on Lollipop
Baseband: G925W8VLU1AOE1
Build Number: LRX22G.G925W8VLU1AOE1
On MarshMallow
Baseband: G925W8VLU3CPC5
Build Number: MMB29K.G925W8VLU3CPC5
Is it possible to downgrade to 5.0.2
download the latest firmware from sammobile n flash it through odin after that try smartswitch again and u cant go back to 5.1.1
Sent from my SM-G925F using XDA-Developers mobile app
Thanks for helping me.
The thing is I already am successfully running Marshmallow it's just that I can't go back to official because everytime I try I get a DRK problem and the only way to make the phone boot up is to flash CF Auto Root. And by doing that makes it unofficial.
Somehow CF Auto Root repairs my DRK but when I get rid of the root I get the DRK problem again.
I have seemed to have found something interesting and quite upsetting.
We all know SamMobile is slow as **** downloading firmwares so I got mine from Updato
Well , I just had a look on SamMobile and there is no Marshmallow available for the SM-925W8 yet in Canada it seems. So Updato somehow probably gave me firmware for SM-925F.
If my prediction is correct and downgrading isn't possible...this would mean I would have to wait for a official release of the firmware for the Canadian models.
My only question is WHEN and when that time does come will it actually fix my DRK problem...
[EDITED]
I could be very wrong with my prediction and simply just have the wrong firmware on my phone.
Okay, yes, it does seem I am running a Canadian Marshmallow actually...So why is it im having DRK problems, verification error checks and my finger scanner no longer works
Interesting thing about my phone, is when it was official...it wouldn't let me go pass update 5.0.2...said I had the latest version for my phone
FriendsFade said:
I have seemed to have found something interesting and quite upsetting.
We all know SamMobile is slow as **** downloading firmwares so I got mine from Updato
Well , I just had a look on SamMobile and there is no Marshmallow available for the SM-925W8 yet in Canada it seems. So Updato somehow probably gave me firmware for SM-925F.
If my prediction is correct and downgrading isn't possible...this would mean I would have to wait for a official release of the firmware for the Canadian models.
My only question is WHEN and when that time does come will it actually fix my DRK problem...
[EDITED]
I could be very wrong with my prediction and simply just have the wrong firmware on my phone.
Okay, yes, it does seem I am running a Canadian Marshmallow actually...So why is it im having DRK problems, verification error checks and my finger scanner no longer works
Interesting thing about my phone, is when it was official...it wouldn't let me go pass update 5.0.2...said I had the latest version for my phone
Click to expand...
Click to collapse
Here is the link for sm-g925w8 Frimware marshmallow
http://www.sammobile.com/firmwares/database/SM-G925W8/
Same problem
i have the same device but my phone on 7.0 and rooted
did you restore your device to the official status