Related
Hey guys,
I can't seem to get back root after a softbrick, also i had my bootloader unlocked but the unlock seems to be gone?
Okay how it all started was when I tried to flash the 4.2.2 leak in CWM. I flashed it and everything seemed normal then when I left CWM for a reboot, nothing happened. the screen was black and the phone would vibrate when pressing the power button.
Being the newbie that I am I panicked and found a stock .253 ftf file which i flashed. the phone is now working again.
Now seeing as I don't give up that easily I figured i'd try to install 4.2.2 again but something has changed now seeing as I seem to have:
No recovery A proper recovery has been installed.
No root Root has been reclaimed
No unlocked BL? Bootloader is unlocked again
I can't root using flashtool as it wont get past - Waiting for uevent_helper rw
I've looked at alot of places on the forum but I don't know where to start really and I'm scared of a hardbrick now.
Can anyone help me out? :angel:
So it has been solved turns out it was indeed pretty simple.
the way I did it was:
Bootloader:
open flashtool, unlock bootloader again. (the code will appear)
Root
(as I was on .253 I had to flash .307 kernel & system via fastboot first)
I then followed the "easy rooting toolkit by doomlord" mentioned in this topic
CWM
I then flashed doomkernel v8 to regain CWM. (fastboot the boot.img)
Thanks for the help michealtbh :victory:
Unlock your bootloader again
Michealtbh said:
Unlock your bootloader again
Click to expand...
Click to collapse
Bootloader is unlocked again, still no root via the service menu display option though.
Use fastboot to flash doomkernel, then boot into recovery and flash a superuser.zip
Or try this http://forum.xda-developers.com/showthread.php?t=2327472
HELP!
eniux said:
Hey guys,
I can't seem to get back root after a softbrick, also i had my bootloader unlocked but the unlock seems to be gone?
Okay how it all started was when I tried to flash the 4.2.2 leak in CWM. I flashed it and everything seemed normal then when I left CWM for a reboot, nothing happened. the screen was black and the phone would vibrate when pressing the power button.
Being the newbie that I am I panicked and found a stock .253 ftf file which i flashed. the phone is now working again.
Now seeing as I don't give up that easily I figured i'd try to install 4.2.2 again but something has changed now seeing as I seem to have:
No recovery
No root
No unlocked BL? Bootloader is unlocked again
I can't root using flashtool as it wont get past - Waiting for uevent_helper rw
I've looked at alot of places on the forum but I don't know where to start really and I'm scared of a hardbrick now.
Can anyone help me out? :angel:
Click to expand...
Click to collapse
Um, I have the same same problem as well, but as you said you found a stock .253 ftf file, what is that? i am even neewbier than you, please help! My Xperia Z is now stuck in the SONY starting screen for more than few days. Please help!
jonathanmusicdude said:
i am even neewbier than you, please help!
Click to expand...
Click to collapse
Then read the stickys and stop being one. - http://forum.xda-developers.com/showthread.php?t=2275632
Hi everyone!
This morning I woke up to find my SHIELD with the so waited notification of Lollipop update. I'm really happy to finally have lollipop running on my device, but sadly I found a problem after the update. I was trying to re-root my device, but neither the SHIELD RAM tool or Root Genius could do the trick. But I didn't gave up, I searched in Google any way to root my SHIELD with the still fresh update, and found that the Kinguser app can root it without trouble.
You just need to download the apk, install it on your SHIELD and open it.
Btw, the old recovery isn't working anymore, you can flash it with the RAM tool, but the device will reflash the stock recovery.
twrp works, but SU binary still wont flash :/
edit - the combination of this APK and TWRP gave me all I need for root + rebooting and keeping root
Yeah, I was about to say that. The TWRP recovery works like a charm, but Supersu binary won't install. But well, the KingRoot app is pretty good.
I can confirm some problem with supersu and update 103. I flashed 2.46 and my portable wouldn't boot. Like, something broke so bad I had to reflash 101 and update again. The later might indicate backups are broke in my twrp, I'll have to look into that. For now, I'm going try kingroot as suggested here and continue other development.
Steel01 said:
I can confirm some problem with supersu and update 103. I flashed 2.46 and my portable wouldn't boot. Like, something broke so bad I had to reflash 101 and update again. The later might indicate backups are broke in my twrp, I'll have to look into that. For now, I'm going try kingroot as suggested here and continue other development.
Click to expand...
Click to collapse
So you were successful in getting TWRP installed, SuperSU installed and removing KingRoot clean - leaving only SuperSU on the system, surviving a reboot?
Ink Rampant Wolf said:
Yeah, I was about to say that. The TWRP recovery works like a charm, but Supersu binary won't install. But well, the KingRoot app is pretty good.
Click to expand...
Click to collapse
hey wolf, what is the easiest way to flash twrp with the 103 upgrade? thanks
You might wanna include the instructions as shown here,
http://forum.xda-developers.com/xpe...how-to-root-lollipop-xperia-tablet-z-t3115107
It basically tells you how to install SuperSU and remove the entire KingRoot library after that. It worked on my Z and on my SHIELD as well.
This was essentially what I did:
http://greenrobotgamer.com/shieldzone/root-shield-portable-lollipop-5-1/
Mine seems to be working just fine, after obtaining root and installing SuperSU. I didn't bother with installing TWRP, I just hotboot the recovery. I'm rebooting my SHIELD as we speak, see if there's any issue
EDIT: Scractch that, it's not booting. How do I flash the latest image back in?
JCESAR2 said:
hey wolf, what is the easiest way to flash twrp with the 103 upgrade? thanks
Click to expand...
Click to collapse
Boot the SHIELD in fastboot and connect it to your pc, then open a command window in a folder with the adb files and the recovery image and type: fastboot flash recovery -the name of the recover-.img, and it will flash the recovery. You can do that with the stock too.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.
Ink Rampant Wolf said:
Boot the SHIELD in fastboot and connect it to your pc, then open a command window in a folder with the adb files and the recovery image and type: fastboot flash recovery -the name of the recover-.img, and it will flash the recovery. You can do that with the stock too.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.
Click to expand...
Click to collapse
thanks for the reply, also, when i boot the shield into fastboot it says in the first line : boot loader version ..../ device locked, does that matter? i rooted the shield already with kingroot.
JCESAR2 said:
thanks for the reply, also, when i boot the shield into fastboot it says in the first line : boot loader version ..../ device locked, does that matter? i rooted the shield already with kingroot.
Click to expand...
Click to collapse
You need to unlock your bootloader first.
ok long story short: since i had the shield drivers installed and tha adb drivers installed i did the oem unlock and after a confirmation screen on the shield i did it, then i immediately flashed the twrp image from the same command line. now the shield is stuck in nvidia android boot logo. any suggestions? thanks
I am in fact stuck in the boot as well. Anyone's got stock image we can flash?
nevermind, after like 10 minutes the thing just booted fine, these are the perks of being a newb.
341464 said:
I am in fact stuck in the boot as well. Anyone's got stock image we can flash?
Click to expand...
Click to collapse
JCESAR2 said:
nevermind, after like 10 minutes the thing just booted fine, these are the perks of being a newb.
Click to expand...
Click to collapse
Search for the SHIELD RAM Tool, it have everything that you all need to flash recovery or old firmware to unbrick the device. It also comes with the necessary files and drivers to work ADB Fastboot.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.
Ink Rampant Wolf said:
Search for the SHIELD RAM Tool, it have everything that you all need to flash recovery or old firmware to unbrick the device. It also comes with the necessary files and drivers to work ADB Fastboot.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.
Click to expand...
Click to collapse
Guess I'll have to flash the old firmware then, it's been sitting there forever.
341464 said:
I am in fact stuck in the boot as well. Anyone's got stock image we can flash?
Click to expand...
Click to collapse
try this shield thread
http://forum.xda-developers.com/showthread.php?t=2388870
JCESAR2 said:
try this shield thread
http://forum.xda-developers.com/showthread.php?t=2388870
Click to expand...
Click to collapse
I just re-flashed the system using RAM, should be fine now. I'll just have wait for the OTA all over again. UGH.
I wish someone could provide a KitKat version tho.
EDIT: Annnd battery's at 15% so the system won't let me OTA yet.
SuperSU will work fine with my latest TWRP builds posted here. The older 2.8.5.0 builds will not work, neither will any build in the linked thread before yesterday. I used SuperSU 2.49 Beta and it worked as expected.
Side Note: The older builds will have the problem where boot will just hang. That seems to be because the older builds didn't have selinux policies built in, so some things never get set up right and the boot panics.
Not sure if this is the right place to post this, but anyway, to the point. I rooted a Xperia SP with towelroot, checked with rootchecker and it was okay, after that I installed CWM and then flashed a ROM and probably CWM changed to TWRP with the ROM. Then I ran some debloater script the ROM maker had done and forgot to flash gapps (lol), or more like debloater script made the phone to reboot, so I let my phone to reboot and try to go back to TWRP and it just doesn't work... Touches won't get recognized. Also I just noticed that the root is gone. Looking for some help here now. Not so used to this stuff.
Things I've tried:
root again with towelroot, didn't work
flash gapps, didn't work
try to install recovery.img again with adb, didn't work(I just may aswell not know how to use adb anyway)
Ask if more information is needed. Thanks! Hope someone could help me.
zirhaze said:
Not sure if this is the right place to post this, but anyway, to the point. I rooted a Xperia SP with towelroot, checked with rootchecker and it was okay, after that I installed CWM and then flashed a ROM and probably CWM changed to TWRP with the ROM. Then I ran some debloater script the ROM maker had done and forgot to flash gapps (lol), or more like debloater script made the phone to reboot, so I let my phone to reboot and try to go back to TWRP and it just doesn't work... Touches won't get recognized. Also I just noticed that the root is gone. Looking for some help here now. Not so used to this stuff.
Things I've tried:
root again with towelroot, didn't work
flash gapps, didn't work
try to install recovery.img again with adb, didn't work(I just may aswell not know how to use adb anyway)
Ask if more information is needed. Thanks! Hope someone could help me.
Click to expand...
Click to collapse
1.You should have posted this in Q&A section
2.Never use towel root on lollipop because all ROMs are rooted by default.
To enable root Settings->Developer options->Root access->Apps and ADB
3.Dont try debloater script just yet. Use it when you are settled with ROM working.
4.Now what you need to do is
a.Boot into recovery and flash the latest TWRP zip.
b.Reboot into TWRP and wipe everything(data,cache,system but not external)
c.Flash ROM zip and gapps.
Hope this works:good:
Phoenix854 said:
1.You should have posted this in Q&A section
2.Never use towel root on lollipop because all ROMs are rooted by default.
To enable root Settings->Developer options->Root access->Apps and ADB
3.Dont try debloater script just yet. Use it when you are settled with ROM working.
4.Now what you need to do is
a.Boot into recovery and flash the latest TWRP zip.
b.Reboot into TWRP and wipe everything(data,cache,system but not external)
c.Flash ROM zip and gapps.
Hope this works:good:
Click to expand...
Click to collapse
I can boot into recovery but it won't recognize touches so I cannot navigate to anywhere in TWRP. Also where to find latest TWRP zip for Xperia SP, since I am looking at TWRP homepage and there is no 2.8.7.0 for Xperia SP. Otherwise it sounds like I learned something new
zirhaze said:
I can boot into recovery but it won't recognize touches so I cannot navigate to anywhere in TWRP. Also where to find latest TWRP zip for Xperia SP, since I am looking at TWRP homepage and there is no 2.8.7.0 for Xperia SP. Otherwise it sounds like I learned something new
Click to expand...
Click to collapse
Here, use this one:
http://forum.xda-developers.com/xpe...-twrp-f2fs-support-xperia-sp-huashan-t3150230
Please remove the previous TWRP beforehand. If you are not sure on how to do so, can you attach me a link of where you followed the methods?
zirhaze said:
I can boot into recovery but it won't recognize touches so I cannot navigate to anywhere in TWRP. Also where to find latest TWRP zip for Xperia SP, since I am looking at TWRP homepage and there is no 2.8.7.0 for Xperia SP. Otherwise it sounds like I learned something new
Click to expand...
Click to collapse
Since you said TWRP does not recognize touches. Here I present you 2 solutions:
1.Flash stock ftf and start over.
2.Flash FOTA and then flash tangerine kernel with TWRP recovery support via fastboot (v6.3 because newer versions cant be flashed using Fastboot)
zirhaze said:
I can boot into recovery but it won't recognize touches so I cannot navigate to anywhere in TWRP. Also where to find latest TWRP zip for Xperia SP, since I am looking at TWRP homepage and there is no 2.8.7.0 for Xperia SP. Otherwise it sounds like I learned something new
Click to expand...
Click to collapse
Phoenix854 said:
Since you said TWRP does not recognize touches. Here I present you 2 solutions:
1.Flash stock ftf and start over.
2.Flash FOTA and then flash tangerine kernel with TWRP recovery support via fastboot (v6.3 because newer versions cant be flashed using Fastboot)
Click to expand...
Click to collapse
6.6 is the last version that contains the elf AFAIK, they should have kept one on cubeserver.eu
Here's the link: tangerine_v6.6
Zenith said:
6.6 is the last version that contains the elf AFAIK, they should have kept one on cubeserver.eu
Here's the link: tangerine_v6.6
Click to expand...
Click to collapse
There are 2 of them zips at my cubeserver folder
http://dl.cubeserver.eu/TechnoSparks/tangerine-stuffs/
TechnoSparks said:
There are 2 of them zips at my cubeserver folder
http://dl.cubeserver.eu/TechnoSparks/tangerine-stuffs/
Click to expand...
Click to collapse
Lol! My bad
I only checked Tomom's folder for tangerine.
Thanks
Hello lovely XDA-members,
this morning a new OTA update/patch came out for my OnePlus 3T, so I downloaded and tryed to install it right away. My phone is rooted on android 7.0 and I have TWRP 3.0.3-0 installed as my recovery. Normally (when I updated to nougat) after downloading a new update the phone reboots itself into TWRP and installs the update by itself, but not this time. I had to seqrch through my phone and had to install thw update manually. After that I rebooted the phone and it started booting the TWRP recovery again, I tried it again and again and again, nothint changed. So I tried to restore my backup with everything functioning, but this wouldnt help either. :/ I read the few existing threads with this problem and heard of a recovery flag that isnt cleared and the bootloader being the problem. One solution that I found was only for an LG phone and I'm afraid that I'll brick my brand new phone I have absolutely no idea what to do now, I would be so happy if someone could help me with this :$
I thank you in advance <3
Encoutered the same problem. Either you reflash the official or twrp recovery (neither did the trick to me) or use this "emergency tool" (which helped me):
https://forums.oneplus.net/threads/unbrick-guide-oneplus-3t.481214/
Btw: TWRP 3.0.3-0 is not working well, switch to 3.0.3-1 beta
Good luck to you
I had the same problem.
How you can ''unbrick it'':
1. Flash a any rom available for the oneplus 3t via twrp
a. after this you will be still in twrp bootloop, to solve this go to step 2
2. Flash back stock recovery via twrp
Now your system will boot again
Optional: Flash back twrp
Just flash stock recovery via adb and you're done. It will fix the problem, you won't lose any data
Isus <3 said:
Just flash stock recovery via adb and you're done. It will fix the problem, you won't lose any data
Click to expand...
Click to collapse
@Isus <3 and @koentdm Do you have a download for the stock recovery, cause the oneplus download-site isnt working and I cant find any other downloads for it
EYT said:
@Isus <3 and @koentdm Do you have a download for the stock recovery, cause the oneplus download-site isnt working and I cant find any other downloads for it
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B0pr-ZA5b-1pNVlxV3ljMUFaUHc/view
Thank you so much, it worked
EYT said:
Thank you so much, it worked
Click to expand...
Click to collapse
No problemos my friendos
It is stock, updated to lollipop 6.0. I got the adb stuff on my pc to run cmds. All I want to do is root it for now. Every search I keep finding is not XT1064(other models show) or if it is, its not on lollipop or it is but not 6.0. I can't seem to find any for XT1064 already running on lollipop 6.0 that just simply needs to be rooted, no custom rom.
TWRP
Just flash by the bootloader the most recent version of TWRP (search for TWRP titan). And then, flash the latest SuperSU on TWRP recovery (search for SuperSU Beta).
Hope i've helped
blades_of_honor said:
It is stock, updated to lollipop 6.0. I got the adb stuff on my pc to run cmds. All I want to do is root it for now. Every search I keep finding is not XT1064(other models show) or if it is, its not on lollipop or it is but not 6.0. I can't seem to find any for XT1064 already running on lollipop 6.0 that just simply needs to be rooted, no custom rom.
Click to expand...
Click to collapse
XPS3Johann said:
Just flash by the bootloader the most recent version of TWRP (search for TWRP titan). And then, flash the latest SuperSU on TWRP recovery (search for SuperSU Beta).
Hope i've helped
Click to expand...
Click to collapse
Latest TWRP recovery for titan: twrp-3.0.2-4-titan.img https://dl.twrp.me/titan/twrp-3.0.2-4-titan.img.html
Latest stable superSU:SuperSU-v2.79-201612051815 https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
You have to flash SuperSU beta otherwise you'll be in a bootloop.
nilanko said:
You have to flash SuperSU beta otherwise you'll be in a bootloop.
Click to expand...
Click to collapse
Thanks, I tried flashing the latest stable supersu (2.79) and no luck. I flashed sr3 supersu and it worked so thanks
Thank you all! Finally got around to doing it. I used the beta SU as nilanko suggested. I ran a backup before trying SU(thank god I didn't forget!). I was stuck on the bootloader unlocked warning after doing it. At first I though maybe it just takes awhile the first time. So I went out for a smoke. Came back & it was still on the bootloader unlock warning screen still. I ran a restore through twrp & rebooted. Booted up fine now. I am wondering what happened exactly.
Only things I can think of is
A)The SU file was corrupted(something in it didn't download right when I downloaded it off my computer)
B)I put the SU file in the internal memory, not on the SD card. I thought it doesn't matter as long as you had the space on either.
SR3-SuperSU-v2.79-SR3-20170114223742 worked!:good: