I can get into the boot loader but it won't finish. I'm running BuglessBeast v 0.2. I'm pretty sure I can use ADB to fix this, if someone can just tell me what to do I would greatly appreciate it.
UPDATE:
I used the erecovery recovery image used in the initial rooting guides for the Evo. Once I had the recovery image flashed it was pretty easy.
Related
Hey Guys,
I'm new here and have been trying to do due diligence by reading as much as I can about flashing my phone before actually doing it. I started by installing CM-Recovery 1.4, made a nandroid backup, and then never actually flashed anything. The other day T-Mobile sent out the OTA for 1.6, it failed because I was running Cyanogen's recovery, so I restored the stock one and installed the OTA manually.
Now I want to actually root and install Cyanogen's 4.1.999. Problem is... I cannot install the Cyanogen recovery again... Flashrec (the one click root tool) doesn't work with 1.6.
I'm a pretty savvy command line user. I use linux a lot and work on a Mac in terminal all the time... I just don't know where to start. Every resource online is outdated and mentions using flashrec. I've heard something about using a goldcard but have no idea how to create one or what it does.
Any advice on how to start? I feel comfortable enough using fastboot (never have, but it seems straightforward) but again my phone is not rooted right now so I cannot do anything with that.
I used this tutorial to create my goldcard to root and unroot my ION...it is a very simple process.
I would suggest these 2 steps.. U basicly have to put 1.5 back on then get root from that point on. Use RA's boot. Use at own risk.. I have tried and it works.
1: - http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
2: - http://theunlockr.com/2009/08/22/how-to-root-the-mytouch-3g-or-g1-in-one-click/
Have FUN hope this helps!
Same problem.I can't boot into recovery mode,too.
Press back+power can't boot into fastboot
Press home+power can't boot into recovery
Fastboot = Vol down + Power
Recovery = Home + Power
I have had my eee pad transformer B70 running custom roms for a while, but yesterday I decided to use rom manage to flash a newer version of clockwork mod. Since then whenever I reboot I am taken straight into clockwork mod recovery. and i am also unable to install anything through it. The only way i can properly boot into android is by holding volume - on boot. I found out that this version of clockwork mod (5.5.0.4) is buggy and that I needed to flash a custom recovery like this one, http://forum.xda-developers.com/showthread.php?t=1213723 . The problem is that i'm not very tech savy and I need detailed step by step instructions on how to flash it.(If someone could link a vid or pics that would be great)
Thanks in advance.
http://forum.xda-developers.com/showthread.php?t=1530337
Thanks but the problem is that im not sure how to use adb.
Then you should read about ADB.
I managed to find some instructions on how to use adb now. I should be able to fix this finally. Thanks for the link above.
It took me long enough but I finally managed to fix it. Turned out that I was typing something wrong into cmd.
Hello guys, first time posting here, I'm pretty sure it's a silly question, sorry if it is but I couldn't find the answer anywhere. I have an unlocked and rooted device, I installed the last 4.3 update this morning, and usually TWRP let me automatically fix the root just after install the update. But this time it just installed it and booted the tablet, and when I try to enter the recovery mode to fix the root in TWRP, I only see the droid with the exclamation mark.
So the problem is that I don't have root, and I cannot enter TWRP to fix it. TWRP went away with the latest update?. For entering the TWRP I pressed vol+ vol- and power and the pick recovery... is it correct?
Thank you in advance for the great community we have in android and sorry for my english
The same thing happened to me, I resolved it by:
- download a recovery image such as TWRP to a desktop/laptop and then flash it via abd
- now boot into recovery and flash SuperSU 1.51 or higher (1.55)
From what I read you probably did this once before. The 4.3 update overwrote your recovery image and root.
3DSammy said:
The same thing happened to me, I resolved it by:
- download a recovery image such as TWRP to a desktop/laptop and then flash it via abd
- now boot into recovery and flash SuperSU 1.51 or higher (1.55)
From what I read you probably did this once before. The 4.3 update overwrote your recovery image and root.
Click to expand...
Click to collapse
Same for me, Starting have some problems as I tried a "reboot to recovery" apk and got it stuck in the bootloader screen and it wasnt going anywhere.. still had TWRP but reflashing things wasnt working..
Used Wug's Nexus Root Toolkit to bring it back to life..
All good
I reflashed the recovery image and rooted again with Wug's Root Toolkit. All good!! Thank you for your answers guys!! Cannot find the way to put SOLVED in the thread title...
prezeus said:
I reflashed the recovery image and rooted again with Wug's Root Toolkit. All good!! Thank you for your answers guys!! Cannot find the way to put SOLVED in the thread title...
Click to expand...
Click to collapse
Nice that it is solved but please do nog use toolkits anymore. I respect the effort and time people take to make them but learning fastboot is just way better. Maybe harder but hard work pays off. Almost everyone will tell the same.
For people who want to use fastboot:
1. Flash custom recovery via fastboot.
2. Boot into recovery.
3. Flash latest supersu.
You can put solved in the title by edeting it.
Sent from my Galaxy Nexus using XDA Premium HD app
same
Good time . I have a similar problem : after a recent update missing root. I tried to flash a custom recovery by fastboot, but the process hangs at downloading recovery.img to nexus. I tried using other drivers and a different version of fastboot, but to no avail.
Ps: by same drivers and fastboot I got the root before.
Hi,
I'm not sure if it's the right place to ask this, but I need help. I just got my Axon 7 in the mail today so I was eager to root it and get started. It did not go well.
The version I got was on b27, and it had an update to b29 right out the box. I did not think too much of it and did the update. I realized later that if I wanted to root, I would need to be on b20 instead. No worries, I got into recovery, flashed the b20 stock image, and all went fine. I went on and rooted using tenfar's utility, and it also went fine. I rebooted went with DrakenFX's way to update back to b29, but something went wrong in the process, and I don't remember the exact message. I told myself that it might be cause I wasn't running the latest TWRP. When I first got into recover after using tenfar's utility, I noticed that the TWRP version was not the latest (3-0-2-0? maybe). I had just downloaded the most recent TWRP image from Unjustified Dev (twrp-3.0.2-2-a2017u.img), so I decided to update right away from within TWRP...I guess this is not something you can do.
Long story short, the phone simply won't get into recovery mode now. The led flashes red for a second, then the phone simply shuts down.
The weird part is that it boots just fine, and I can get into ADB and bootloader too. However, my bootloader is locked once more, and root does not work either. I am now on b29, so I cannot use tenfar's utility.
So, am I SOL? Is there a way to restore the stock recovery image via ADB? I tried flashing TWRP again, but I get a "FAILED (remote: Partition flashing is not allowed)" in ADB, most likely because my bootloader is locked again?
The good part is that the phone is usable and everything seems to work, but having no recovery is a bit unnerving...if something goes wrong again, the phone will be a dead brick.
Thank you very much.
OK, I just realized that I could still use tenfar's utility even though I was on b29....pheww, what a relief. Back in TWRP. Sorry, you can delete this thread (I would do it if I knew how )
arky33 said:
OK, I just realized that I could still use tenfar's utility even though I was on b29....pheww, what a relief. Back in TWRP. Sorry, you can delete this thread (I would do it if I knew how )
Click to expand...
Click to collapse
Can you link me in the right direction? I'm having the same problem where I can get to bootloader and fastboot, but no recovery. I'm on a2017u.x.x.b29, too.
Hi,
I am not sure anyone should follow my advice considering how I somehow managed to screw up a relatively simple process, but here's how I fixed it. I used tenfar's utility from this thread to flash TWRP again. Even though I was on B29, I used the B27 package and it worked fine. But don't flash the boot image, just the recovery! After that, I could boot into TWRP again. From there I followed this great instruction thread and got Lineage up and running in minutes.
I hope this helps you get going, but keep in mind that this might not be the proper way to do things, it's just what worked for me. Cheers.
arky33 said:
Hi,
I am not sure anyone should follow my advice considering how I somehow managed to screw up a relatively simple process, but here's how I fixed it. I used tenfar's utility from this thread to flash TWRP again. Even though I was on B29, I used the B27 package and it worked fine. But don't flash the boot image, just the recovery! After that, I could boot into TWRP again. From there I followed this great instruction thread and got Lineage up and running in minutes.
I hope this helps you get going, but keep in mind that this might not be the proper way to do things, it's just what worked for me. Cheers.
Click to expand...
Click to collapse
Thanks, Arky!
I've been away from XDA for quite some time since I've had the S6 Edge on Verizon and there hasn't been any type of root action on it. I really appreciate the links you posted!
I own a moto G4 XT1625, and I just followed the guide at devs-lab.com/how-to-root-moto-g4-moto-g4-plus.html on rooting it. I Successfully unlocked the boot loader, installed TWRP, but had trouble on the final step, rooting it with superSU. I entered TWRP, typed in echo "SYSTEMLESS=true" > /data/.supersu, and ran the zip, but when I rebooted, it was just a black screen-- it doesn't do anything! I can still get into the fastboot and TWRP recovery, but I didn't make a backup since the guide didn't say to, which in hindsight was a terrible idea. Any help anyone can offer would be greatly appreciated.
EDIT: I read some more, and am now trying to install the lineage ROM. I made a backup of the old broken system, so hopefully I don't mess it up more than I already have.
EDIT2: It didn't work (Maybe because it isn't actually rooted as supersu didn't install?) thanks in advance for any help you guys have!
Stock image can't be rooted without using ElementalX 1.04 stock kernel as it does not allow root. Thus, you need to restore to use hardware buttons to get back to TWRP and install Elemental X stock kernel and then SuperSu again. If you don't have TWRP, then you need to go into fastboot mode and resinstall TWRP recovery image and then do above. Good luck.
HueyT said:
Stock image can't be rooted without using ElementalX 1.04 stock kernel as it does not allow root. Thus, you need to restore to use hardware buttons to get back to TWRP and install Elemental X stock kernel and then SuperSu again. If you don't have TWRP, then you need to go into fastboot mode and resinstall TWRP recovery image and then do above. Good luck.
Click to expand...
Click to collapse
Thank you so much for you answer! I've installed ElementalX, then SuperSU, and for the first time, something other than a black screen on boot! the first time it stopped then went black after a few seconds, and as I'm writing this, it seems to be stuck in a bootloop as it has been playing the same animation now for a few minutes. Will it eventually resolve itself, or do you think it's still messed up?
EDIT: It's been going now for ~20 minutes which probably means something isn't right. I have to leave for my job now, but Ill try any suggestions when I get back. Thanks again!
Thank you so much HueyT, It's working now! ElementalX didnt work with stock for some reason so what I did was do a wipe, then flash the lineage ROM, then flash ElementalX (for lineage), then flash SuperSU, and it finally booted after going through a few boot cycles and ~ 10 minutes! I can't believe it's actually working!