Hi guys,
I got a situation. I just bought the lenovo K3 note from a guy and noticed he already installed SU, so I thought it's already rooted. Then I went to recovery mode and accidently deleted the OS without any backup recovery. Now i dont know what to do. The phone wont start since there is no OS installed. Any idea how i can install any rom on it.
Can somebody help me with that
http://forum.xda-developers.com/showthread.php?t=863209
Thread closed
Related
Hi guys,
First post here, so am not allowed to post in toolkit forum.
Having wanted to root several android devices in the past, I have lurked here for quite a while, but finally got round to rooting my s iii mini two days ago. My firmware updated to amg3, but I followed the advice in the toolkit and used the closest match. Everything seems to be working fine.
When it came to flashing a new recovery through odin, I chose twrp, and superSU and it failed. When opening superSU it gave a message about no binaries being present. I decided to reinstall the toolkit, this time flashing CWM and superuser.
This worked perfectly! I disabled superSU, as superuser is functioning correctly, but now when I boot into recovery, TWRP comes up.
Excuse the newbie question, but does this mean that flashing CWM didn't work, or do I now have 2 recoveries installed? Could I have inadvertently caused myslef a problem that will manifest itself later? I did a search for CWM files through root explorer, which came up with nothing, but I am not sure if I searchex for the correct file names or in the right places.
I am only really concerned as I am currently deciding which ROM to flash, but obviously want to check I'm not about to brick my phone!
Thanks guys.
OCTAF1SH said:
Hi guys,
First post here, so am not allowed to post in toolkit forum.
Having wanted to root several android devices in the past, I have lurked here for quite a while, but finally got round to rooting my s iii mini two days ago. My firmware updated to amg3, but I followed the advice in the toolkit and used the closest match. Everything seems to be working fine.
When it came to flashing a new recovery through odin, I chose twrp, and superSU and it failed. When opening superSU it gave a message about no binaries being present. I decided to reinstall the toolkit, this time flashing CWM and superuser.
This worked perfectly! I disabled superSU, as superuser is functioning correctly, but now when I boot into recovery, TWRP comes up.
Excuse the newbie question, but does this mean that flashing CWM didn't work, or do I now have 2 recoveries installed? Could I have inadvertently caused myslef a problem that will manifest itself later? I did a search for CWM files through root explorer, which came up with nothing, but I am not sure if I searchex for the correct file names or in the right places.
I am only really concerned as I am currently deciding which ROM to flash, but obviously want to check I'm not about to brick my phone!
Thanks guys.
Click to expand...
Click to collapse
It sounds like CWM hasn't reflected TWRP, have you tried using the tool kit again just to flash CWM? Or how about flashing CWM via Odin using the recovery in the below thread?
http://forum.xda-developers.com/showthread.php?t=2232856
Sent from my Nexus 7 using xda app-developers app
OCTAF1SH said:
Hi guys,
First post here, so am not allowed to post in toolkit forum.
Having wanted to root several android devices in the past, I have lurked here for quite a while, but finally got round to rooting my s iii mini two days ago. My firmware updated to amg3, but I followed the advice in the toolkit and used the closest match. Everything seems to be working fine.
When it came to flashing a new recovery through odin, I chose twrp, and superSU and it failed. When opening superSU it gave a message about no binaries being present. I decided to reinstall the toolkit, this time flashing CWM and superuser.
This worked perfectly! I disabled superSU, as superuser is functioning correctly, but now when I boot into recovery, TWRP comes up.
Excuse the newbie question, but does this mean that flashing CWM didn't work, or do I now have 2 recoveries installed? Could I have inadvertently caused myslef a problem that will manifest itself later? I did a search for CWM files through root explorer, which came up with nothing, but I am not sure if I searchex for the correct file names or in the right places.
I am only really concerned as I am currently deciding which ROM to flash, but obviously want to check I'm not about to brick my phone!
Thanks guys.
Click to expand...
Click to collapse
I think when you rebooted into system in CWM, you accidentally chose to revert to the old recovery
Thanks so much for the answers guys. I went ahead and flashed a rom anyway, figuri g that as long as A recovery was in place, it would be ok, and it seems to be so.
And it turns out I am happy with TWRP and as the old sayi g goes, if it aint broke....
I only chose CWM as the previous root had failed, so I tried with different variables, ot because of a burning preference for one over the other.
Thanks again for your help.
Wil.
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...
Hello all,
Today I got fed up with my Xperia T's stock firmware so I decided to move everything to cyanogenmod 12. Installed the rom but now I guess the permissions are not fine, so later I found out it would have been a good idea to root my device prior to my upgrade. Now I cannot find a way to successfully root my phone, I even tried RootKing and two other similar applications. I was wondering what rooting method can I use via the upgrade (Recovery is Cyanogen's)?
Best,
shorto
shorto said:
Hello all,
Today I got fed up with my Xperia T's stock firmware so I decided to move everything to cyanogenmod 12. Installed the rom but now I guess the permissions are not fine, so later I found out it would have been a good idea to root my device prior to my upgrade. Now I cannot find a way to successfully root my phone, I even tried RootKing and two other similar applications. I was wondering what rooting method can I use via the upgrade (Recovery is Cyanogen's)?
Best,
shorto
Click to expand...
Click to collapse
I rooted my LT30p with kingoapp from kingoapp.com or kingoroot.com not sure
Only problem was play store not working, when i tried to solve it device keep restarting again and again not sure what i did wrong.
If you cab figure it out, you can try.
My problem is none of these work since my permission are apparently screwed up so badly I cannot even access my files since I do not have permission to them, nor can I install anything.
Try CyanogenMod 12.1 - Neo's Homebuilds in the Xperia T Original Android Development section.
And for the Gapps I would recommend OpenGapps.
Ok, so here it goes:
I own a at&t galaxy s4 active , the day the lollipop ota came , I updated successfuly. THEN, I used KINGROOT and successfully temp rooted it.... HERE'S WHERE MY SCREWUP comes in- I DIDN'T flash any custom recovery, and while I was deleting some system bloatware, I ACCIDENTALLY DELETED THE BUILD.PROP!! Now the phone will boot,, but not into the OS.
I know its a VERY dumb rookie mistake, I'm new to Samsung devices, I've always been an HTC guy, and I'm definitely not New to rooting , unlocking bootloaders, etc. But Never on Samsung devices...
So I'm pleading, if anyone can give me any advice on how to fix this, PLEASE lemme know, it would be GREATLY APPRECIATED!!!
bdizzle1686 said:
Ok, so here it goes:
I own a at&t galaxy s4 active , the day the lollipop ota came , I updated successfuly. THEN, I used KINGROOT and successfully temp rooted it.... HERE'S WHERE MY SCREWUP comes in- I DIDN'T flash any custom recovery, and while I was deleting some system bloatware, I ACCIDENTALLY DELETED THE BUILD.PROP!! Now the phone will boot,, but not into the OS.
I know its a VERY dumb rookie mistake, I'm new to Samsung devices, I've always been an HTC guy, and I'm definitely not New to rooting , unlocking bootloaders, etc. But Never on Samsung devices...
So I'm pleading, if anyone can give me any advice on how to fix this, PLEASE lemme know, it would be GREATLY APPRECIATED!!!
Click to expand...
Click to collapse
DON'T USE KINGROOT! Sorry to yell about it, but I can't stand that monstrocity. Unfortunately there are no lollipop firmware files, so you're going to have to follow my process detailed here to get back to working lollipop rooted:
http://forum.xda-developers.com/showpost.php?p=63639949&postcount=2
There's no way to unlock this phone's bootloader so you can't have a custom recovery anyway
This is my first time posting so I'm sorry if it's in the wrong place...
Anywho a couple of weeks ago I rooted my P10 lite (WAS-LX2) after having it rooted for a week I decided to unroot it, I used the full unroot option in SuperSU, I noticed the TWRP was still there and wanted to return to my stock recovery.
I know how to do it but the thing is I didn't back up before I installed TWRP and I can't seem to find a link to the stock recovery, could someone help me? Thanks.