Hi all,
My razer phone 2 got some rain in the front speaker so i was unrooting it to take it into the repair store for my square trade warranty. That uninstall seemingly removed my OS. i might have gotten root working with a stock rom that was already rooted which might be my problem? Honestly can't remember. I've gotten a new computer since then so lost my old files.
I was previously running this version 9.0 - MR1 P-MR1-RC003-RZR-190305.3110
The bootloader is unlocked but the android drivers from here latest_usb_driver_windows won't install. This also means adb/flashboot don't work
I've tried manually installing the drivers and receive this error: This device cannot start. (Code 10)
i can sideload still but i don't think that will help- was looking for an OTA update in case that would work but no luck so far
I don't have a custom recovery
I've tried installing the arter97 with TWRP to flash with no success.
I do have an sd card if i can install something from there but also no success yet
Any thoughts on what to do next?
Thank you!
Related
Hi guys, thanks for the forum and i hope to become a part of it. I've been under so much stress since yesterday, my galaxy s3 (on EE in the UK) for the first time decided it's data was corrupted yesterday after my battery died, never done this or anything like it before, and it wouldn't let me access the phone itself unless the data was reset.
I had a lot of very precious pictures in my gallery from the weekend, which unfortunately chose not to backup to google+ for the last few days, even though it always has up until recently. All night/day i've been trying to figure out and get software to recover these photos, which i think is possible as i did it a long time ago on a blackberry, but not android yet. I'm just hoping it can be done so the photos aren't forever lost, the other stuff gone doesn't bother me so much.
The guide i'm following (here: http://forum.xda-developers.com/gal...de-internal-memory-data-recovery-yes-t1994705) says it needs to be rooted first, and i can't even get past step 1. I've only ever rooted my old galaxy S1 (which worked back then) but i can't seem to get the S3 to do it. And now my phone also believes there's no sim card in and i get no signal now.
this is the guide i followed: http://www.ibtimes.com/how-root-sam...-jelly-bean-official-firmware-tutorial-975812
though i think i need a newer PDA file to flash my i9305 with. I'm on the EE network running 4.3 jelly. It installed Super SU but root checker says it still isn't rooted.
So have i messed this up? And is there any hope for me getting these pictures back?
Thanks in advance for any help, it's much appreciated.
if you are running on 4.3 then you are not following the right guide to root...
use THIS ONE instead... if it fails to root use the workaround part, i used it and worked....used the workaround to install custom recovery and then flashed chainfire zip from his website and updated SU and worked.
are you still able to boot the phone?
Thanks for the response, tried that guide and still getting no signal on my phone (no mobile connection at all, sim card isn't recognised as being there) and i don't think it's rooted right. Still saying SuperSU has stopped working when i try to open it.
I put the Root_SuperSU.1.02-Busybox.1.21.0.zip on the internal SD and tried that too.
Which is the chainfire zip you're talking about, could you possibly link it? I don't really get what you mean by custom recovery, do you mean it's the same as flashing the Busybox thing from recovery mode?
And yeah it still boots up normally...
use that tutorial to install a custom recovery...then install this SuperSU - http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip?retrieve_file=1 - flash it in custom recovery....after that update app with playstore and should work.
but i suggest you get it to a specialized shop to get your photos back...
Hi there,
Just got a new S5 mini (SM-G800F) today. I've updated to latest Android version (4.4.2). I did not install any custom ROM. Build ID was KOT49H.G800FFXXU1ANJ1.
I've then rooted the phone successfully with CF-Auto-Root (http://autoroot.chainfire.eu/) and Odin. The closest file I found was KOT49H.G800FXXU1ANH2. ANJ1 to ANH2 looks like a "downgrade"... perhaps this is the issue? But read on..
I then started to install corporate access (Exchange account). Our corporation wants to have the device encrypted so I started to do that.
What basically happens is that the encryption droid symbol shows on the screen for about 20 minutes and after that the device reboots.
Yet, no encryption has happened! (is the anywhere a logfile I can look at for more info?)
I have a Samsung Galaxy S3 with 4.1.2, stock ROM as well and rooted with CF-Auto-Root. On that device the encryption process was more verbose and worked fine (although slowed down the phone considerably during normal usage).
So, does rooting the S5 mini with Autoroot break the encryption process? How can I encrypt the phone? Do I have to go back to pure unrooted stock, encrypt first and root later?
Thanks for any insights.
Dan
I still do not know why encryption would not work, but I found a workaround:
I reset the phone to the latest stock firmware with the help of Kies 3. I got G800FFXXU1ANG7. Obviously I lost all data, but that is ok since its a brand new phone.
Started the phone and configured WLAN to accept and install pending OTA upgrade. Just to get to the very latest release at the moment (G800FFXXU1ANJ2).
Encrypted device. I installed the corporate access tools which required the encryption...
Then I installed latest TWRP for my device with ODIN.
Last step was to install SuperSu with TWRP, using the zip file from chainfire.
Some remarks:
- I am not sure why encryption fails while the phone is rooted. Perhaps someone could explain to me?
- If I use CF-Autoroot after encryption of the device, the phone would go into a boot loop, i.e. not asking for the decrypt password and fall back to the boot logo. I thought that encryption would only touch /data. Most likely there is something that initiates decryption during boot, which is replaced by the CF-Autoroot image.
- OTA updates are not possible anymore after installing TWRP recovery (the phone complains that there are changes to the stock ROM). However, if I re-flashed with a stock recovery, OTA was not complaining anymore. If an update would actually work, I have not checked.
- If SuperSu is already installed however, even TWRP re-flashing with stock recovery would not make OTA work again. I would assume that the OTA update routine checks several components to decide if there is stock installed. Temporarily disabling SuperSu did not work, un-rooting through the SuperSu menu left me with SuperSu hanging for an hour until I switched the phone off. I also tried the OTA survival mode (I have SuperSU Pro) and it does not work either (in that try I left out step 2 above).
So for now I have a rooted S5 mini on Android 4.4.2 with encryption and I am happy. I did live without OTA with my S3 (which still is on 4.1.2) since I rooted it and frankly, I did not really miss 4.3...
Regards
Dan
If you change some files (like Recoery or rooting) OTA won't work anymore on any Samsung Rom...only pure Stock!
User_99 said:
If you change some files (like Recoery or rooting) OTA won't work anymore on any Samsung Rom...only pure Stock!
Click to expand...
Click to collapse
Thanks. That is what I thought.
1 - Encryption fails if the phone (S5 mini, 4.4.2) is rooted. Why? However, encrypting a rooted S3 (4.1.2 stock) did work fine. Was there anything changed with the newer Android versions?
2 - Do we know what the OTA process is checking to decide if it can go ahead or stall? SuperSu's OTA survival surely knows a bit more on that.. but unfortunately it still won't work..
Mahesh Senghani here please help me. Long time trying but not properly Root Access not properly configured or was not granted. Please sir how to fix this problem deeply request to you please solution easiest explain to me
Mahesh Senghani
Please help me you send Email [email protected]
How to fix this problem
grokit said:
Thanks. That is what I thought.
1 - Encryption fails if the phone (S5 mini, 4.4.2) is rooted. Why? However, encrypting a rooted S3 (4.1.2 stock) did work fine. Was there anything changed with the newer Android versions?
2 - ..
Click to expand...
Click to collapse
Hey, please read about KNOX, hope you may get your answer...
Hello guys! I have Xperia T 9.2.A.0.295.
I've tried a couple of methods of rooting my phone and all failed:
- rooting via flashtool, when "make it ra1n" appears, phone just restarts
- rooting via first method listed in this subforum, when running .bat file it gets stuck @ *daemon started successfully*
- rootin via towelroot, when I try to install it, it simply says "App not installed".
My idea was following, but I'm afraid to execute it without you guys having my back or I know it will be broken (back or phone or both hehe)
I wanted to try to push CWM via fastboot (already got drivers installed and all options defined correctly, unknown sources, debugging etc.)
I wanted to follow this tutorial with this CWM: http://forum.xda-developers.com/showthread.php?t=1918966
1. So, if I install rooted ROM, is my phone going to be rooted or not? Or is installation going to fail? (some people were mentioning it's very likely phone is gonna end up bricked...)
2. If I install this CWM (since it's from 2012) am I going to have problems installing ROMs developed in 2015 (eg. 4.4.4 or 5.x?)
3. Is there a way I could back my current software up just in case something goes wrong so I could restore it in case of a fail?
Thanks guys!
If anyone has FB and maybe would like to add me just so I could contact him if things go south, feel free to send it to my PM, I'll add you
OK, I found older firmware on XperiFirm (9.2.A.1.199) from the vendor I bought the phone from. Later the phone was unlocked, I sure hope it doesn't lock again or something.....Since I moved to another vendor.
I'm downloading now, but I'm thinking about sleeping through the night 'till someone answers because I'm having a feeling I'm gonna wreck something...
Did you tried THIS ?
It works for me
Sorry for replying so late, didn't work for me, but I'm working on it with Olivier, he helped me
I'm a bit slow to realize this, but after updating to T mobile's latest 20b firmware (lollipop 5.0x), it lost root. I then tried to root it, using the three methods mentioned here: http://forum.xda-developers.com/showthread.php?t=2732311.
Towelroot clearly doesn't work anymore. The zip file in the above thread couldn't be flashed since there's no recovery operation possible (just showing an android with ! in a triangle sign). I also tried the purpledrake, but the script doesn't run when the phone is connected with all drives installed and adb devices showing the phone. I then tried to get fastboot mode back (to install twrp/cwm recovery to flash the zip file) by following http://forum.xda-developers.com/lg-l90/general/guide-fastboot-l90-d415-t2827825 which I have done successfully before, but then couldn't do it because it requires root (doh!).
So it seems that I just lost my ability to root, unless I downgrade to a stock kitkat (10e?) from tmobile, and then towelroot/etc. assume those work.
Anyone with experience on the stock 20b firmware? Can you root it and how? I'd love to use the beautiful 12.1 Cyanogen that's available here, but the camera doesn't work right on mine. Thus stock 5.0 seems to be the best option. Many thanks.
I got a bit further on the purpledrake method, in that I had to do a clean restart on the phone and connect to usb before the script will recognize. However, it ends up giving a really quick error message after trying a temp root: "your phone is not running a compatible software version. No vulnerable mode detected. Rebooting phone."
Anyway, many thanks to @brossovitch I followed http://highonandroid.com/android-smartphones/how-to-root-lg-g-flex-2-g2-g3-on-lollipop/ and it works like a charm. I can't seem to delete this very short thread so I thought I'd wrap it up with a solution. If it seems a bit useless please remove the thread (or tell me how to do it since I can't find the "easy button"). Thanks.
Ok, first off, let me say what a idiot I am! I've been unlocked, s-off, and rooted since the day I got this phone and for the most part been running BadBoyz Rom. It had gotten a little bogged down and I thought I would go ahead and put a fresh flash of this ROM on the phone a couple days ago, I was tired and somehow erased everything on the phone and couldn't get ADB Sideload to copy anything onto it and I was out of time and a little panicky so I went to the the Sprint store and talked to a tech who didn't hassle me at all about it and he was able to load a stock ROM for me, in the process he also updated the Hboot of my phone (at a minimum). Currently it has hboot of 1.61, Radio 1.01.20.1225, DSP 3.51.202740718, OS 6.23.651.7. Phone is still unlocked and S-Off so I flashed twrp recovery and then tried to flash supersu. When I tried to flash the supersu I got a message about the cache? Could'nt mount cache or something like that but then it appeared to work? So, when I restarted phone and checked for Root, it tole me the same old binaries not loaded, this is a problem message? Started with Twrp 2.84 now I have 2.87 thinking that was the problem but it's not I don't think. Also tried a few different versions of supersu too. Help!!!
I read advice somewhere on the forum about just flashing a rom since you have twrp? I almost did that but twrp gave me a warning that this might not be compatible so I stopped. Could this work?