Is there a rooting section or something? I feel as if this may be in the wrong section (if so, please move it thanks)
So, today, I decided that I wanted to unlock, root, and install a custom ROM on my htc m9. Now, on my previous phone, I only rooted and installed a custom kernal, all of which were apps that I used on my phone to do all the work. for the m9, there are no apps that root the phone for you so I looked up a few tutorials. (I'll list what I did in case you find something I did wrong
list of my guides :
droidviews.com/root-htc-one-m9-marshmallow
.droidviews.com/how-to-root-htc-one-m9-and-install-twrp-recovery-on-it/
and I used htc dev to unlock my phone's bootloader
unlocking my bootloader.
Unlocking my bootloader was successful, when I go into download mode (the black screen to be clear) it says unlocked
installing twrp
There was a lot of issues when installing since all but one of the guides kept saying go into bootloader mode, bootloader mode this, bootloader mode that (which is the white screen). After some searching, I realized that they really meant download mode... two different things... I believe twrp was successfully downloaded since I am able to access twrp when I go into bootloader mode, then recovery mode, and I end up in twrp.
rooting
so, according to the guide, I move the supersu zip files into my internal storage (anywhere). then go into twrp, press install, select the zip file, then swipe to flash.
well, I did just that, however, when I go to turn on my phone, I get stuck on the htc load screen, It's not a boot loop, it's just that white screen that says htc... I can't do anything else. holding down the power button does nothing (even for 10 seconds)... update, after typing this, I get a nice animation, then I'm stuck on the white screen that says htc one...holding the power button again does nothing, power button, and volume down does nothing... I think if I hold the power button and volume up, I turn off the phone, meaning I can access download mode, boot loader mode, etc. So... now what? clearly, following instruction has got me not where (bummer) and my lack of experience has also gotten in trouble (it could be worse? right?) what can I do to fix this?
note: my previous phone, I soft bricked it and I was able to flash the stock rom with LG flash tool, but there's no such thing as htc flash tool...
Related
This phone belongs to my brother and I own the Sprint account. The phone wouldn't turn on at all even on bootloader after he tried to flash a mod. It was htc dev unlocked using Regawmod. Phone was running viper rom 1.2.1. Heres where he got the mod http://forum.xda-developers.com/showthread.php?t=1609480 he downloaded one of the mods he cannot remember which one but they're all practically the same status bar mod except they're different colors. The thread belongs in the HTC One X device forums but ive heard of others flashing mods straight from there with no problems..I'm still surprised that it bricked the phone though..since it's just a MOD regardless I would expect twrp to just say "failed" but not brick the phone..so All was good until:
1. rebooted into twrp recovery (ver 2.1.8)
2. attempted to flash elegancia mod from one x forum
3. 1st time recovery displayed "failed"
4. he tried again 2nd time..twrp once more displayed "failed"
5. seeing that nothing happened and the flash simply failed, my brother chose the reboot option from twrp.
6. phone did not reboot
7. couldn't access bootloader at all no matter how many times we tried
8. holding down power button and power+vol up/down combinations [in desperation] did not do a thing no matter how long the buttons were held
9. RUU completely failed...it would not detect the phone..windows failed to recognize the phone but instead attempted to install drivers "QHSUSB_DLOAD" I had also forgotten that the bootloader must be relocked but that couldn't happen anyways since the bootloader was never accessible in the first place
10. opening the phone and unplugging battery and reconnecting did not do a thing
11. we're stuck with a brick..no bootloader access, no recovery, not even the power led displaying signs of life...nada.
12. my only hope is for a method to actually unlock the bootloader to be developed using the same method as made famous by the EVO 3d found here http://forum.xda-developers.com/showthread.php?t=1547695 which actually BRICKs the phone by corrupting hboot when S-On,thus placing it into download/emmc mode. I assume it's in download mode since windows tried to install "QHSUSB_DLOAD" drivers but failed at that.
If anyone has a clue what I should do or knows of someone that can help then please let me know! Thanks!
Sent from my PG86100 using xda premium
Pretty much have the same exact problem on my thread :S http://forum.xda-developers.com/showthread.php?t=1725027
Take to sprint store and they willgive you a new one
sent from my EVO LTE
cant wait
ddeecc said:
This phone belongs to my brother and I own the Sprint account. The phone wouldn't turn on at all even on bootloader after he tried to flash a mod. It was htc dev unlocked using Regawmod. Phone was running viper rom 1.2.1. Heres where he got the mod http://forum.xda-developers.com/showthread.php?t=1609480 he downloaded one of the mods he cannot remember which one but they're all practically the same status bar mod except they're different colors. The thread belongs in the HTC One X device forums but ive heard of others flashing mods straight from there with no problems..I'm still surprised that it bricked the phone though..since it's just a MOD regardless I would expect twrp to just say "failed" but not brick the phone..so All was good until:
1. rebooted into twrp recovery (ver 2.1.8)
2. attempted to flash elegancia mod from one x forum
3. 1st time recovery displayed "failed"
4. he tried again 2nd time..twrp once more displayed "failed"
5. seeing that nothing happened and the flash simply failed, my brother chose the reboot option from twrp.
6. phone did not reboot
7. couldn't access bootloader at all no matter how many times we tried
8. holding down power button and power+vol up/down combinations [in desperation] did not do a thing no matter how long the buttons were held
9. RUU completely failed...it would not detect the phone..windows failed to recognize the phone but instead attempted to install drivers "QHSUSB_DLOAD" I had also forgotten that the bootloader must be relocked but that couldn't happen anyways since the bootloader was never accessible in the first place
10. opening the phone and unplugging battery and reconnecting did not do a thing
11. we're stuck with a brick..no bootloader access, no recovery, not even the power led displaying signs of life...nada.
12. my only hope is for a method to actually unlock the bootloader to be developed using the same method as made famous by the EVO 3d found here http://forum.xda-developers.com/showthread.php?t=1547695 which actually BRICKs the phone by corrupting hboot when S-On,thus placing it into download/emmc mode. I assume it's in download mode since windows tried to install "QHSUSB_DLOAD" drivers but failed at that.
If anyone has a clue what I should do or knows of someone that can help then please let me know! Thanks!
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Hopefully one day someone will figure this out with out actual casualties. Thanks all for your help. I'm getting a new one tomorrow.
I wanted to know if you found a solution because im dealing with a similar problem. I can cant access my phone manually or through fastboot
Linux will help you with download mode. There's threads on how to use ubuntu to unbrick. I'd find the thread for you, but am not in a position to do so.
Sent from my EVO using xda app-developers app
[p1-backstory][p2-problem][p3-symptoms][p4-cause][p5-question]
links have been removed due to forum restrictions, to see the post with links at:
connordoherty.blogspot.com/2013/03/xda-post-q-nexus-boot-shows-up-on-xt912.html
I recently got a secondhand Verizon Motorola Droid Razr XT912, intending to unlock it and use it with my t-mobile account. Coming from iPhone, I've never used android before so i took a few weeks to grow accustomed to the stock OS before rooting it. I learned it, and eventually, although it took several days, I also rooted it.
But today, when I attempt to boot the device, i see this glowing X logo, which my friend thinks might be the nexus logo (bootloader?), forever.
Never goes anywhere, just stays on X. I can only reboot it by holding power+volume down which makes it again boot to the X. I'm not sure if this is considered a boot loop - seeing as it doesn't actually loop, just hangs endlessly. It seems my only way of shutting the device off (power button does nothing) is to enter the boot selection menu (Vol up+down at startup) and choose the "AP fastboot" option and in that mode i can power down with a tap of the power button. all the other options bring me to the X, except recovery, an ill-android-logo-with-exclamation-point.
How did I get to this point? I tried to flash a ROM to replace the stock Motorola Android - trying first AOKP: First I backed up using myBackup, then I chose the link for "spyder" at the download list and followed a guide telling me to download this app and I did, but a different guide told me I would need CWM so i got that too. I didn't know how to add anything from within the app so i reboot to get too the boot menu, and chose the AOKP zip file - which worked for a bit but proceeded no further after "Booting...". I tried several times and messed around with the menu but I thought maybe I needed CWM so I chose that zip and it didn't work either.
Has anyone been in a similar situation? It sure seem like I bricked it. I discovered Recovery Mode has a hidden menu when you press the volume buttons, but choosing "install update from external storage (SD card)" then it fails as in valid for every zip I have tried. I thought maybe it needed to be signed or official so i downloaded what i found to be the stock update Blur_Version.6.16.211.XT912.Verizon.en.US.zip and that was accepted but eventually failed as well. The factory reset option there does nothing. I tried using the Fastboot method as well but it never finishes without stopping, on 6/18 or 2/18 or anything for a different reason each time.
What haven't I tried?
Hello
got my HTC ONE from AT&T . Want to get a rid of the ATT Bloatware and restrictions (Thethering) ASAP.
SIMUnlock and ROOT everything easy and fine
Used the AOI KIT (Hasoon 2000) and also instaled the CWMT . Also tried the CWM
After start into the Bootloader menu after i flashed the CWMT/CWM the option "Recovery" was there.
Go to recovery the Phone starts and no Recovery mode to make a backup etc.
What I'm doing wrong.
Also can get into the Bootloader only Switch off the phone and as soon the screen gets dark press VOL down and then it goes into the bootloader. From the Phone beeing toatly OFF i can't get into the bootloader either
Could that be an AT&T issue ?
Thanks
[
I flashed another CWM and after a new restart it worked also the startup into the Bootlooder with Power and Vol Down
I've followed these instructions to the tee but have not had any luck with getting this to work. The flash always just results in my phone getting stuck on the "recovery booting.... recover is not seandroid enforcing - Set Warranty Bit : Recovery" screen. Odin reads as "PASS!" but my phone seems like it's just stuck. I've scoured over dozens of forums searching for answers but what works for others just doesn't seem to be working for me.
The instructions all seems so clear, and multiple forums' instructions gave me confidence that this would work no problem as long as I followed the instructions precisely. I guess that wasn't the case. I can't afford a new phone right now, but I'm sure my phone isn't completely bricked. There's gotta be a way! Can you please help me, xda community?
EDIT: I forgot to mention that I also tried the "uncheck the Auto Reboot option" method, and I'm a little confused about the last sentence. See below:
NOTE: Sometimes the device does *not* boot into recovery mode and root your device. Just do the entire procedure again if this happens. If it still will not install root and such, make sure that in Odin "Auto Reboot" is not checked. Then after flashing, pull the battery, and boot with VolUp+Home+Power button to boot into recovery manually. This will start the install process.
I'm confused about the "This will start the install process" sentence. I flash, let it finish until Odin says "Pass!", remove the battery, boot into recovery, and then I have two options from there - I can either go into download mode again, or I can start the phone normally. Starting the phone normally just brings me right to the recovery mode which gets stuck there indefinitely. I've left it there for 15+ minutes and it still just stays stuck there.
EDIT 2: Exactly how long is it suppose to take to boot up after it's been flashed?
EDIT 3: IT WORKS. So, If you just sort of hold down all the buttons at the same time, the phone will restart a few times and eventually bring you into the TWRP menu. This is what I was unaware of before. I'm not exactly sure what the specific method or timing is for that, but just tinker with holding all the buttons, and I think you can let go when you see little blue letters on the top left that says recovery or something. Of course, being able to access the TWRP menu means you must first have flashed the TWRP thing, which I did using Odin. Just download the latest TWRP .tar file and flash it with Odin.
EDIT4: SUCCESS! I am now successfully rooted! I reflashed the twrp-3.0.2-2-klte.img.tar and then I was able to access the actual GUI. I guess what I had before was some super stripped down version of the TWRP that only gave me access to a command-line looking interphase in recovery mode, with very limited options. So there you go, if you find yourself looking at pictures on forums of a supposed TWRP with an actual GUI you can navigate, that's because it does exist! Download the one I just mentioned, flash it using Odin, and boot it up by holding VolumeUP, Home, and Power. From there you can flash Zip files, just put the zip files into an sd card. I put my zip right into the sd card, not even in it's own folder or anything.
that version (8/26/2016) does not work at all for g900t, Maybe Chainfire wants to shut down CF_auto_root method.
you need to try the previous version (02/28/2016), I doubt you can find the old version in their website, Try google it on internet.
goog888 said:
that version (8/26/2016) does not work at all for g900t, Maybe Chainfire wants to shut down CF_auto_root method.
you need to try the previous version (02/28/2016), I doubt you can find the old version in their website, Try google it on internet.
Click to expand...
Click to collapse
Interesting, thanks for the info! Funny enough, while I was at Best Buy last night, I decided "what the heck" and asked a Geek Squad guy about my phone, and told him how I attempted to root and now it wouldn't boot, etc. He took my phone, and just sort of held all the buttons together and it restarted a few times, and he just kept fidgeting with it until eventually it came up to the TWRP recovery menu! So, I did a factory reset and started up the phone. It is currently on 5.1.1. I have since been able to get myself into the TWRP recovery menu by fidgeting like he did, even though I'm not entirely sure what exactly the timing or button combos are. The Geek Squad guy said he just held down ALL buttons, even VolumeUp and VolumeDown at the same time. So whatever, TWRP menu IS accessible finally.
At this point, I'd prefer to flash CM13 to it, and apparently I can just put the CM13 file on my phone storage/sd card, and then flash it through the TWRP recovery menu. But since I factory reset my phone back to 5.1.1, should I first update my radios? A techy friend of mine introduced me to a new fear - that if you flash a ROM that is incompatible with an older radio, it could "hard brick" my device. So now that's where I'm at. I want to flash a rom to gain simple root access, but don't want to risk bricking my device.
Here is my phone's information:
SM-G900T
Android 5.1.1
Baseband version G900TUVU1FOG6
Build Number LMY47X.G900TUVU1FOG6
I don't know how to mark this solved, but it is, as described my my 4th edit in the original post.
I have a Umidigi Crystal (2/16) and it´s not booting anymore.
How that came is a long story.:crying:
I got the phone, wanted to root it and while I was enabling usb debugging in developer options, I noticed you can root it from there as well.
I have no idea whether thats a Umidigi special or if that was seen on other phones too, basically I had a slider option to enable root access.
After a reboot, SuperSU was installed automatically, root checker, file explorer and rom toolbox worked fine with it but I actually rooted to get Xposed Installer.
That worked very well too, only did I want to have a custom recovery to prepare my phone in case of a bootloop.
So I followed these instructions.
I hadn´t unlocked the bootloader by the time and since the instructions said I would have to unlock it I did that first using these instructions.
Everything worked as expected but from this point on, on the pre-bootanimation picture my screen would say
Code:
Orange State
Your device has been unlocked and can't be trusted
Booting in 5 sec...
As everything else was the same as before, I just ignored it.
Then I moved on to installing TWRP by, again, these instructions.
The process seemed to work but after finishing, I was unable to boot into recovery mode, my phone would just boot into the normal OS(which still worked by the time).
I wanted to get around that by using this app but because of the unlocked bootloader my phone was factory reset
and I had to root again.
I was going for the same way I already did it beforehands and I was asked to reboot again.
After that point, my phone was stuck in the pre-bootanimation screen saying it´s orange state thingy again and would just stay there forever.
I tried installing the stock rom from here ((2/16 - V1.0_20171026)) to get rid of the root setting I enabled.
Now I get the pre-bootanimation screen with the orange state text again and after 5 seconds it keeps the background image but the text disappears.
Thats where it´s stuck for like 3 hours now.
When I press the power key a couple of seconds, that loop starts again, I can´t turn the phone off.
Things I can still do:
•Reboot (holding the power button, still get stuck the same way though)
•Access a PC, the internet, an SD Card and electricity
•Charge the phone
•I still have all the drivers on my PC properly installed
Things I can´t do
•Keep the phone turned completely off
•Boot into fastboot, recovery or normal OS
•Get the PC to recognize my phone (not even the adb)
What I want (if possible in that order):
•Boot into literally any OS
•Use the current OS or any custom rom
•Have root access without the developer option method
•Have TWRP
•Unlocked Bootloader
I know, I ask for a lot but this is the only phone I have right now and I badly need it.
Getting it to boot again is really the primary goal here.
Thanks so much to everyone who tries to help me, it really means a lot