Hi all,
Can't quite figure this one out. I've had no trouble rooting my phone and installing different ROMs...up until I soft bricked my phone a few weeks ago and managed to get it back.
After doing this though, even though I was able to install Viper's ROM, apparently now I'm unrooted, even though I still have downloaded SU on my phone. I tried to update it, but it failed.
I'm just really confused, never had this issue before.
Thanks for the help and suggestions.
Depending on how you managed to get it back, you may have unrooted it. Never seen that happen though, I caught a soft brick once, but I still had root afterwards.
It SHOULD be as easy as flashing the superSU ZIP file in Hasoon2000's toolkit to get root back.
Related
OK so I followed a youtube video tutorial on rooting,and I think it's the boot.img that messed everything up. It would boot up before but it was stuck on the Google screen, the OS didn't load. So I found a GRH78 or something Nandroid backup and ran that, but the capacative buttons don't work, the screen isn't calibrated correctly and the phone radio isn't correct either. Then I remembered my Nexus S was the newer GT-I9023 GRI54 and I need a GRI54 NANDROID stock backup (which I can't seem to find!)
Guys, what do you suggest I do at this point? I can't revert to stock (I've been trying)
I just got this Nexus S and have been spending hours trying to restore firmwares, finding it online, but now I know I need the GRI54 Android 2.3.3 backup, and if anyone has that I'd be super happy
I really need help
you most likely need the 9023 method of rooting
see the stickied guides
I fixed it. I downloaded a GT-I9023 GRI45 firmware file off of somewhere here (<3 xda forums) it wasn't a nandroid backup, but I used the clockworkmod to install it and surprisingly, it booted up again. (of course, I had the crappy 2.1 installed before so maybe this acted as an 'update' and fixed all the problems, but anyways it works smooth now as it did before )
I knew I could figure it out.
Not to be an ass, but I think there's a lot of difference between bricking a phone and being unable to boot. You've never bricked your phone, since you could still switch ROMs by using the Recovery.
This is a misleading title. Bricking is when you just can't enter not even the bootloader/Recovery.
you are 100% right
unfortunately many people keep getting those 2 terms confused, and use it inappropriately
every body needs to chip in and help newbies learn the correct terminology.
thank you
boolean22 said:
Not to be an ass, but I think there's a lot of difference between bricking a phone and being unable to boot. You've never bricked your phone, since you could still switch ROMs by using the Recovery.
This is a misleading title. Bricking is when you just can't enter not even the bootloader/Recovery.
Click to expand...
Click to collapse
Looks like I've managed to act and look like a fool...
I tried to root my Nexus S with Superboot, unaware that it was version-specific (I should have known that ). To make a long story short, I tried to root my phone with Superboot which is written for android 2.3.3, while I'm running 2.3.4.
The phone can get to fastboot/recovery, but won't boot. I googled to find how revert to a stock 2.3.3 or 2.3.4, but somehow did not find what I was looking for.
Phone was vanilla, I hadn't installed anything specific on it besides twitter, FB, etc.
From a powered-off phone, how would I manage to revert to a clean phone ?
Thanks for your help, people.
-- Jeff
<EDIT:
All the solutions I've seen required CWM or similar, and a rooted phone. Since my problems started because I wanted to root my NS, I figured that I was out of luck for a while, and a non-working phone was out of question.
I went at my retailer and managed to get a new phone free of charge I *****-footed around the fact I was installing an unsupported (by the carrier) update/app, the clerk wasn't very familiar with the NS so it went well with them and they gave me a new phone
/EDIT>
So I originally rooted my s3 with the GS3_debugfs-root_r2.7z method, flashed CWM and unlocked my bootloader. Since then i have flashed several roms and all was well until a couple days ago when i decided to restore my first backup in order to retrieve some data. I was still on G7 and kept getting the notification of the HE update. Even though I excepted the OTA and let it fail in CWM i kept get getting the notice almost every time i turn on my phone. I was getting so annoyed with it that i decided to flash a rom with HE in hopes that that would stop the OTA. In this whole process of restoring my backup my bootloader must have locked and when i flashed the rom I got stock on that "unauthorized software, contact Verizon screen". It freaked me out when i couldn't boot into recovery.
I followed the whole Odin, root66 method and was able to save my phone...phew... but have a couple questions now.
1) my phone has the superuser app and it shows that it cannot be uninstalled, like a system app but yet root checker says i am not rooted? Why is this.
2) Would installing supersu and updating binaries get me rooted again?
3) This one is just for curiosity..The message when i soft bricked my phone said you have unauthorized software and to go see a Verizon store. Would they really have been able help me or just tell me i am SOL
ps. Thank you to the XDA community for sharing instructions like the one i used to save my phone.
microdot said:
1) my phone has the superuser app and it shows that it cannot be uninstalled, like a system app but yet root checker says i am not rooted? Why is this.
2) Would installing supersu and updating binaries get me rooted again?
3) This one is just for curiosity..The message when i soft bricked my phone said you have unauthorized software and to go see a Verizon store. Would they really have been able help me or just tell me i am SOL
Click to expand...
Click to collapse
2: That could work, but so should loading the default SU and updating binaries.
3: They would not have been likely to help you, and may have even voided your warranty.
Going to a store would have yielded a bunch of head scratching and them telling you to file an insurance claim.
In the future if you want to block ota's freeze sdm and fwupdate in titanium.
Hi,
a couple months ago, I successfully rooted my Idol 3 with the "root.bat" method. I realised a week ago that my phone was not rooted anymore and I tried to re-root it in the same fasion, but it didn't work. I then proceeded to unlock the TWRP recovery loader and re-installed SuperSU from there. I used RootCheck to see if my device was rooted and it is not. I can't gain root access either and SuperSU prompts me with a dialog box saying "SuperSU binary needs to be updated". If anyone can offer any help, I would greatly appreciate it I'm a little nooby when it comes to rooting, so if I was too vague in my description of the problem, please point it out so I can be more specific.
Thanks,
-Yasio
Found a solution if anyone is ever intrested!
Turns out my firmware had some sort of issue, so I used the Mobile Upgrade Q utility and just re-flashed the phone with the stock firmware. You can find a whole tutorial here: http://forum.xda-developers.com/idol-3/help/return-to-stock-firmware-recovery-t3216077)?
It's super easy. Then, I just re-rooted the phone with the TWRP method DallasCZ came up with also posted here: http://forum.xda-developers.com/idol-3/general/guide-unlock-bootloader-root-alcatel-t3161878
And there you go, I got root access back and got rid of the freakin' "Binary files need to be updated" or w/e prompt in SuperSU.
Thanks again to DallasCZ and others for their hard work on the rooting scene for the Idol 3. I love this phone and you made me love it even more
-Yasio
I tried rooting this phone with SuperOneClick, and it didn't work. So then I tried Kingo and it said it worked and I could use the phone right afterwards but I could not see the superuser icon, so I tried resetting it and from then on it's been flashing at the samsung screen. I have been trying to root the phone to unlock it as IMEI was all scrambled on the About Phone screen for some reason and none of the ATT codes would work. I really need to get info off of the phone.
The phone was upgraded via Kies to Gingerbread.
I've been trying to read about this a lot lately, but I am a novice and I am in over my head for my free time right now. In desperate thanks to any help.
**** Also, I have a second Infuse and I rooted it just fine with SuperOneClick and so I just don't know what the **** is wrong with this other phone....it would always get to the mounting stage and become unresponsive.
Also, I upgraded the other phone to gingerbread via keys update and now it won't root either. I guess I have to remove the upgrade? Not sure how to do that without root.
Hey guys.
Like I've written in the title, I have rooted my device with magisk.
I've installed a few modules one of which has caused problems so I have unrooted it or so (don't exactly remember because it has been months ago).
Afterwards, I have tried to root the device again but everything has failed.
I do the exact same steps as described, which had worked before, but this time, it just won't get rooted anymore.
I've tried everything that came to my mind but it has always failed.
No one was able to help on the forum of the device which is why I'm asking here now.
I had also tried to install TWRP and root that way but it wouldn't let me install anything, so I couldn't install magisk that way.
The guide I'm talking about can be found at the following link.
https://forum.xda-developers.com/mate-20-pro/how-to/guide-unlocking-bootloader-magisk-root-t3885422