Need help. I goofed... - T-Mobile, Samsung Galaxy SIII

<sighs> I was trying to update my recovery so that it would mount my external SD (I was running CWM 6.0.3.1) and so I ran a search, found an updated file and flashed it. What I DIDN'T realize at the time was that my search had taken me into a Nexus 4 thread. So I just flashed an N4 CWM recovery (6.0.4.4) onto my TMO S3 and now the phone is stuck in some sort of boot loop and I can't get it to boot to anything.
Now normally my phone will vibrate once at the beginning of the boot sequence and then move on to the boot animation. But now it will vibrate once, pause a few seconds, vibrate again...rinse and repeat. That is why I suspect a boot loop. I have also trying holding Vol up+HOME+Pwr to force it into recovery and it looks like it may start to load, then power off again. I see a tiny blue "recovery starting" in the top left corner and then nothing. That is the only indication of any activity that I can see.
Anyone know how to fix this? Or am I SoL?
Disregard. Further digging showed me how to enter DL mode (I've never used it before) so that I could use Odin to push an older recovery image which got me fixed.

Lazarus416 said:
<sighs> I was trying to update my recovery so that it would mount my external SD (I was running CWM 6.0.3.1) and so I ran a search, found an updated file and flashed it. What I DIDN'T realize at the time was that my search had taken me into a Nexus 4 thread. So I just flashed an N4 CWM recovery (6.0.4.4) onto my TMO S3 and now the phone is stuck in some sort of boot loop and I can't get it to boot to anything.
Now normally my phone will vibrate once at the beginning of the boot sequence and then move on to the boot animation. But now it will vibrate once, pause a few seconds, vibrate again...rinse and repeat. That is why I suspect a boot loop. I have also trying holding Vol up+HOME+Pwr to force it into recovery and it looks like it may start to load, then power off again. I see a tiny blue "recovery starting" in the top left corner and then nothing. That is the only indication of any activity that I can see.
Anyone know how to fix this? Or am I SoL?
Click to expand...
Click to collapse
Can you try Power +Home + VOLUME DOWN ? That should take you to"Download Mode". If you can get to it, do a ODIN Flash of Correct Recovery. If you can't get to Download Mode then connect to PC and see what it gets detected as. If it get detected as QHSUSB then the Phone is Bricked. You should then follow the DE-BRICK thread over here.
Please read Carefully when Trying to Mount/Format/Restore External SD Cards with CWM. People have accidentally partitioned INTERNAL SD card. That's another Hard Brick and harder to get out of.

You can pull the T999 Recovery.tars from @Aerowinder 's signature.
If not then you can pull an older version from Doc's thread here.

Appreciate the help guys. I tried to post a "disregard" edit, but it froze. I did find the Vol down trick for DL mode and that let me flash an older recovery to get back to square one. (Teach me not to verify my current thread...)

Lazarus416 said:
Appreciate the help guys. I tried to post a "disregard" edit, but it froze. I did find the Vol down trick for DL mode and that let me flash an older recovery to get back to square one. (Teach me not to verify my current thread...)
Click to expand...
Click to collapse
If you got your answer and wish to request deletion of the Thread, then please contact the forum Moderators. Always the Moderators are listed on the main page of any main or sub forums.

Related

Semi Bricked/Bricked Phone Needs Fixing

Hi Guys -
First time android user and attempted rooting using the odin method. I followed the instruction listed here http://forum.xda-developers.com/showthread.php?t=1311194 to the "T" before starting. I was doing alright until after flashing the recovery-cwm-hercules.tar, then it gets weird. It didn't flash to recovery but just rebooted to the main screen (where I could see the background picture with the locker pattern), then it immediately shuts off and the cycle begins again.
The weird thing is that I can't even access recovery mode (hold vol. up+down+power), because I'll see the Clockworkmod logo then it flickers and reboot itself. This happens every time I attempted recovery mode.
My attempts to fix it:
1. I flashed the recovery, http://forum.xda-developers.com/showthread.php?t=1315390, to see if it makes any difference. The same story happens with loading to main screen w/locker then it reboots itself again and again. Sometimes I'll be lucky to input the pattern but before soon it will reboot itself again. Same thing with recovery mode as described above.
2. Flashing the stock kernel provided by http://forum.xda-developers.com/showthread.php?t=1311229 to see if it does anything. Nope, same story for both recovery mode/home screen.
3. The insecure kernel, http://forum.xda-developers.com/showthread.php?t=1320946. Same story. nope, nope.
4. Tried these in all order and permutation. Nada.
5. Tried it both ways using samsung driver/kies.
6. Tried it both ways with/without SIM card.
7. Battery is fully charged when attempting any flashing.
8. All the above in my second computer to no avail.
I'm sorry if this might come across as long winded but I just want you guys to get the full picture. I would really appreciate it if you guys could offer any solutions or advice on how to correct this problem. Please be gentle with this first time android user haha, thanks in advance man.
Manually boot into recovery (vol up/down keys) and make a backup (be sure to do this). Then try wipe data/factory reset through recovery. Sounds like a ROM issue not a hardware issue
First off, thanks roman for the quick reply. That's the thing I can't get to recovery manually with the button combinations. When I do that it gives me this message:
[Picture]White dropbox/mail box with a yellow arrow pointing to the Android
"Verifying internal mmc block
Checksum confirmation check (0)
No need checksum confirmation already exceuted
#manual mode#"
It would then reboot and goes to the screen with the locker then immediately repeats that cycle. It doesn't have any wipe options/restart now/etc.
No way to power it down except with battery removal. I've attempted what you suggested many times too to no avail.
redlaws said:
First off, thanks roman for the quick reply. That's the thing I can't get to recovery manually with the button combinations. When I do that it gives me this message:
[Picture]White dropbox/mail box with a yellow arrow pointing to the Android
"Verifying internal mmc block
Checksum confirmation check (0)
No need checksum confirmation already exceuted
#manual mode#"
It would then reboot and goes to the screen with the locker then immediately repeats that cycle. It doesn't have any wipe options/restart now/etc.
No way to power it down except with battery removal. I've attempted what you suggested many times too to no avail.
Click to expand...
Click to collapse
Ok, so if it actually boots into the ROM but reboots, try rebooting to recovery from adb -- "adb reboot recovery"
think it's a no go . i tried using adb recovery method and the same thing would occur, it would restart and seems to load into recovery mode but then I would only see the logo, then it flickers and restart itself.
then the vicious cycle of loading up to the screen-locker and restarting itself begins. guess this is the smartphone version of being friend-zoned.
Have you tried taking battery out then back in and while holding volume up/down plug it back into computer? That has never failed to get me into d/l mode. Man I hope you get it working.
Yeah I tried that and getting to download mode is not the problem. just that recovery mode doesn't boot properly in that it would restarts itself. and when i boot normally to screen, i would see the locker and background picture then within 3 secs, it would restart itself.
Guess last resort is to go to t-mobile store, play dumb, and get samsung on it. only problem is that i worry about the flash rom counter # since mine is like 10 already (my attempts to address this problem). Let's hope those tmobile reps aren't that tech savvy.
Thanks for all the help fellas, great early posting experiences so far.
I'm sorry I've read your post..and i'm confuse, if you're able to go into download mode, then why could you just start Odin and flash the recovery again. If its unsuccessful then check the MD5 to see if you have a bad download. I think you should download the recoveries files again add give Odin another shot..Good luck..
Sent from my SGH-T989 using XDA App
are you able to go into CW recovery ?
if so, you can mount the USB, download a stock ROM, and then flash it using CWR
kt0ce said:
I'm sorry I've read your post..and i'm confuse, if you're able to go into download mode, then why could you just start Odin and flash the recovery again. If its unsuccessful then check the MD5 to see if you have a bad download. I think you should download the recoveries files again add give Odin another shot..Good luck..
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
I'm going to give it another try. I've been trying it with different files for a good 2 days now though.
AllGamer said:
are you able to go into CW recovery ?
if so, you can mount the USB, download a stock ROM, and then flash it using CWR
Click to expand...
Click to collapse
I understand that but that's the a big problem. If I could go to CW it would be a different story but I can't go into CW recovery. I would be able to see the logo CWR and the version number then immediately it shuts off again and reboot. Happens every time without fail.
redlaws said:
I understand that but that's the a big problem. If I could go to CW it would be a different story but I can't go into CW recovery. I would be able to see the logo CWR and the version number then immediately it shuts off again and reboot. Happens every time without fail.
Click to expand...
Click to collapse
did you let go of holding the vol+ & vol- buttons as soon as you see the blue text in CWR ?
it can easily reboot by accident when holding those buttons and hitting power, but the buttons are so responsive it selected the first option to reboot the phone by accident a couple of times on me
I'm positive that I held it properly and long enough. I never got to the blue text, just the CWR logo showing then turns off (like you shutting off a tv) and reboots itself. Trying to flash it again with Odin didn't work either and I tried the recoveries from different sources as well.
I went to the Tmobile store today and seems like they'll mail me a replacement then I'll return my current one to them. Only thing is stocking/processing fee but it's a small price to pay if it resolves everything.
glad they will give you another one..
Dude if you can get into download mode then it can most likely be fixed by flashing stock through odin. This would save you some $$. Just saying.
reocej said:
Dude if you can get into download mode then it can most likely be fixed by flashing stock through odin. This would save you some $$. Just saying.
Click to expand...
Click to collapse
Dude, I understand that it should but it's not. I've flashed the stock recovery for more than 10 times and I still can't past the home screen. It would just reboot itself in less than 3 sec. And I'm positive I flashed it properly. Believe me I don't want to spend extra money if I don't have too.

CM10 Boot Loop? Help!

I rooted my phone to a stock root on my Jelly Bean Galaxy S3. I then installed ClockworkMod through ROM Manager, then CM10. It installed OK, now stuck in a boot loop. No big deal, I'll reinstall to my Kies backup. Doesn't work, I can't seem to get into recovery mode. I hold the buttons, it vibrates, and the screen stays black until I let go at which point it boots to that horrendous boot loop. I really need my phone back!
P.S. Please explain as if I am five years old.
Flightfreak said:
I rooted my phone to a stock root on my Jelly Bean Galaxy S3. I then installed ClockworkMod through ROM Manager, then CM10. It installed OK, now stuck in a boot loop. No big deal, I'll reinstall to my Kies backup. Doesn't work, I can't seem to get into recovery mode. I hold the buttons, it vibrates, and the screen stays black until I let go at which point it boots to that horrendous boot loop. I really need my phone back!
P.S. Please explain as if I am five years old.
Click to expand...
Click to collapse
Download mode couldnt get any simpler bud
Edit: just incase if you dont know its down home power button to get to it, find your galaxy s3 firnware (ATT/Bell etc...) and your back stock nonrooted. And then you can root againif you wanna
While in a boot loop, hold the buttons. The phone will power off and stay off as long as you hold them down. Let go of all three, then immediately press all 3 again. When you see a little blue line of letters on the top left of your screen, let go again. Should boot into recovery from there.
mrhaley30705 said:
While in a boot loop, hold the buttons. The phone will power off and stay off as long as you hold them down. Let go of all three, then immediately press all 3 again. When you see a little blue line of letters on the top left of your screen, let go again. Should boot into recovery from there.
Click to expand...
Click to collapse
Did you read the question bro.. he said he CAN'T go to recovery mode only other option is download mode
No, the option is to boot into recovery and perform a factory reset (which may fix his problem). IF that doesn't fix his problem, he can flash a different ROM from recovery, provided he had custom recovery.
The only difference in getting to download as opposed to recovery is which volume button you use. Chances are if he can't 3 button into recovery, download will be the same result.
Thanks
Got it fixed guys, thanks for the help, now I'm back at Stock Rooted 4.1.1, but am still on the quest for a deodexed rom!
Excellent suggestion - it worked for me
mrhaley30705 said:
While in a boot loop, hold the buttons. The phone will power off and stay off as long as you hold them down. Let go of all three, then immediately press all 3 again. When you see a little blue line of letters on the top left of your screen, let go again. Should boot into recovery from there.
Click to expand...
Click to collapse
I got a Galaxy S III on 23rd Dec 2012 with Ice Cream Sandwich installed. A couple of weeks later it updated itself with a little help from me to the latest Jelly Bean. Since then it's gone into the reboot loop 3 times without any provocation; i.e. I get it out of my pocket and it's in a reboot loop but it had been fine the last time I used it. I tried pressing various buttons alone and in combination and eventually it came out of the loop. At no time did I have to remove the battery. The only mod I've made to it is the addition of a 64GByte SD card, apart from the upgrade to Jelly Bean. I've seen many posts on this problem but yours is the first that confirms my solution for getting out of it. It's obviously a common problem so somewhere there must be a description of what causes it and, hopefully, how to prevent it as it's a real nuisance when you want to use your phone and it's in a reboot loop. If and when I find a definitive article I'll post here again.
Thanks MrHaley.

[Q] Random Bootloop

I had me phone sitting beside me. I had just turned off the screen. Then it randomly started bootlooping. I can get into the recovery screen ( Fboot, Hboot, Recovery, Etc... ) I think it might be the power button some how?? It doesn't boot loop until I turn on the phone. I've tried different batteries. Got any ideas??
jonahly said:
I had me phone sitting beside me. I had just turned off the screen. Then it randomly started bootlooping. I can get into the recovery screen ( Fboot, Hboot, Recovery, Etc... ) I think it might be the power button some how?? It doesn't boot loop until I turn on the phone. I've tried different batteries. Got any ideas??
Click to expand...
Click to collapse
Cannot get into the actual recovery!!! But I can get into the little android guys on skateboard's screen!
jonahly said:
Cannot get into the actual recovery!!! But I can get into the little android guys on skateboard's screen!
Click to expand...
Click to collapse
Hahahha,you made my day bro,thats the bootloader,see if you can access the recovery from there,if not,guess its time to start over and you might as well do it right,unless you have already done,what im about to show you....
<<<<Takes a breath.....Ok go here and read the whole OP,then go here and read the instructions and partition your sd card.Then go here and install DT's ap2sd.Download the recovery here and the rom of your choice.Boom!
That did not help. I cannot get into recovery!!!
jonahly said:
That did not help. I cannot get into recovery!!!
Click to expand...
Click to collapse
Have you tried installing a new recovery? I recommend downloading SmelkusMod Recovery from http://forum.xda-developers.com/showthread.php?t=1661543. Download a zip version such as PC36IMG_ra-supersonic-4.3-smelkus-aokp.zip to your computer, rename the file to PC36IMG.zip (watch out for Windows hidden extensions), copy PC36IMG.zip to the root folder of your EVO 4G's sdcard, and power the phone off. Then simultaneously press and hold the volume down and power buttons until the bootloader starts, allow the bootloader to scan for updates, and press volume up to confirm that you want to install the updated recovery.

[Q] issue after rooting Recovery Booting. Set Warranty Bit : Recovery loop

hi, i just decided to root my t mobile note 3 device so the first website was tellin about KINGO 1 step root so i did install KINGO and it said successfully rooted and i clicked finish the phone rebooted and it showed me
Recovery Booting
Set Warranty Bit : Recovery
and this screen keeps looping and i cant even enter recovery mod once the phone turns on it shows me that and it keep looping auto reboot same screen
im not sure if my phone is still alive anymore
any solutions?
thanks.
note 3 t-mobile n900t
Enter download mode (hold [VOLUME-DOWN][HOME][POWER] until buzz, then release [POWER]). At the first download mode screen where it says you can press volume-down to boot normally, press volume-down to boot normally.
Frank
same prob
Frank Westlake said:
Enter download mode (hold [VOLUME-DOWN][HOME][POWER] until buzz, then release [POWER]). At the first download mode screen where it says you can press volume-down to boot normally, press volume-down to boot normally.
Frank
Click to expand...
Click to collapse
Same problem as OP, and I can not get into download mode either. If I do as above, it still goes on booting .
saeidzzz said:
hi, i just decided to root my t mobile note 3 device so the first website was tellin about KINGO 1 step root so i did install KINGO and it said successfully rooted and i clicked finish the phone rebooted and it showed me
Recovery Booting
Set Warranty Bit : Recovery
and this screen keeps looping and i cant even enter recovery mod once the phone turns on it shows me that and it keep looping auto reboot same screen
im not sure if my phone is still alive anymore
any solutions?
thanks.
note 3 t-mobile n900t
Click to expand...
Click to collapse
If the advice above didn´t work (nothing happened when pressing the usual VOL down - home - power etc), this is how I managed:
I tried booting around 25 times with the power button released at different times. Did not work.
Tried to insert battery when pressing the 3 buttons. Did not work.
I let the battery run completely empty. Started charging the phone and pressing the 3 buttons. Did not work.
I charged the phone full (with booting the whole time....needed to put it somewhere quiet). After estimating it was full, I pulled out the battery, preparing to send it to mobiletechvideos.com (they saved me before). After a few hours I wanted to see the error message so I could write them. When I inserted the battery, I got the regular download mode! Nowthen, would I dare to boot it since I am not really sure what to flash to my phone?
I rebooted, and now the phone is back to normal. OTOH, I will not try to flash CWM/TWRP again, so goodbye custom roms (Omega )
you are a life saver!
Frank Westlake said:
Enter download mode (hold [VOLUME-DOWN][HOME][POWER] until buzz, then release [POWER]). At the first download mode screen where it says you can press volume-down to boot normally, press volume-down to boot normally.
Frank
Click to expand...
Click to collapse
I thought I was going to have to factory reset my phone like other forums suggested and lose everything. Thanks to your suggestion I was able to get out of recovery reboot loop. Thank you!
Thanks for your help, you are a lifesaver lol! I saved so much money and time because of you. Have a great day
Frank Westlake said:
Enter download mode (hold [VOLUME-DOWN][HOME][POWER] until buzz, then release [POWER]). At the first download mode screen where it says you can press volume-down to boot normally, press volume-down to boot normally.
Frank
Click to expand...
Click to collapse
But how to enter recovery it still says set warranty bit recovery
i am facing problem with set warranty bit: recovery in samsung J5 model...
samsung j5 500f
i have the same problem when i flash twrp recovery..any solution ????
Ghats normal
Sent from my SM-N900T using XDA-Developers mobile app
My Fix
I held down the Down volume key along with the power and spammed the home button until the download screen came on, just keep spamming it while holding down the other keys, it will reboot just keep spamming, then I plugged it in to my computer, opened Odin and re installed the Root and it booted up fine
ulop3z said:
I held down the Down volume key along with the power and spammed the home button until the download screen came on, just keep spamming it while holding down the other keys, it will reboot just keep spamming, then I plugged it in to my computer, opened Odin and re installed the Root and it booted up fine
Click to expand...
Click to collapse
Um. U might wanna flash back to stock. Your phone shouldn't do that. Ur messing up your bootloader. Flash newest firmware via Odin
Sent from my Samsung SM-N900T using XDA Labs
Tmobilefan906 said:
Um. U might wanna flash back to stock. Your phone shouldn't do that. Ur messing up your bootloader. Flash newest firmware via Odin
Sent from my Samsung SM-N900T using XDA Labs
Click to expand...
Click to collapse
The phone is fine now, it was just stuck on the loop and spamming home was the only way out, its fine now I've had no problems and it boots up fine
This happens...
This happens to almost everyone at some point of time. There is no need to worry as you just need to flash recovery like TWRP or CWM. To shed some light on this issue... boot loops mainly happen when you uses the incorrect version of software with your ROM or stock firmware. By using youtube you can look at the videos of your phone model and find the recovery version number needed.
For anyone who has a Note 3 T-Mobile phone who is still stuck! I am willing to make a video to show how to fix this and provide all the firmware/version numbers + links in one bundled location to make it easier.
ALL PHONES ARE VERY specific... ONLY USE THE CORRECT FIRMWARE FOR YOUR MODEL PHONE
Again, if you have a Samsung Note 3 T-Mobile, model number SM-N900T and are still lost. Let me know so I can shot a video and bundle files needed.
---------- Post added at 08:44 AM ---------- Previous post was at 08:38 AM ----------
cdresor said:
If the advice above didn´t work (nothing happened when pressing the usual VOL down - home - power etc), this is how I managed:
I tried booting around 25 times with the power button released at different times. Did not work.
Tried to insert battery when pressing the 3 buttons. Did not work.
I let the battery run completely empty. Started charging the phone and pressing the 3 buttons. Did not work.
I charged the phone full (with booting the whole time....needed to put it somewhere quiet). After estimating it was full, I pulled out the battery, preparing to send it to mobiletechvideos.com (they saved me before). After a few hours I wanted to see the error message so I could write them. When I inserted the battery, I got the regular download mode! Nowthen, would I dare to boot it since I am not really sure what to flash to my phone?
I rebooted, and now the phone is back to normal. OTOH, I will not try to flash CWM/TWRP again, so goodbye custom roms (Omega )
Click to expand...
Click to collapse
Don't be scared by this... just choose the correct versions before blindly trying to install a ROM. Also, only use links from main sources if you dont fell like auditing the code!
Hi guys, sorry for might be late about helping you now years later... But recently I've found something interesting about fixing this issue.
*****
Fix: (100% working in Galaxy Grand Prime SM-G530H)
UPDATED: More detailed info!
# Before flashed Recovery or Root:
1. Root device using Odin or any other rooting known workaround.
2. Backup Recovery (optional), and Kernel using Rashr (available on PlayStore).
3. Flash Custom Recovery (TWRP), using Odin PC software or TWRP android app.
4. Flash backed-up Kernel.img file to Boot partition using TWRP install section.
5. Reboot system (It may take a few time to boot)
# After flashed Recovery or Root: (accidentally or without knowing)
1. Search online and download your exact Phone Stock Kernel.
2. Follow *before flashed* above ↑ from 3rd.
Bonus info:
Even after flashing TWRP, you might be able to Boot device yet, by going to TWRP → Advanced → Reboot system. (It bypass bootlooping to Recovery, while: “Set Warranty Bit : Recovery”).
That's all! Try at your own, then share it!

HTC One M8 (Bricked?) PLEASE HELP!

Hi there,
So recently I just tried rooting my HTC One M8, with the All-In-One tool kit. It was successful, I was messing around with it for a while, removing bloat wear, ect. Then I figured out about custom roms, and heard about CyanMod11. It turns out that it couldn't read my sim card for whatever reason, but it still worked and loaded up. Then, I tried Android Revolution. THAT one worked flawlessly, besides the fact that I couldn't take screen shots for whatever reason. I should of just left it there. Here's where things go wrong. Then, I tried ViperOneM8. After that, it failed to load up and is now in a endless boot loop. I can't get into fast boot either. However, one time I somehow did manage to get into fast boot, but I didn't see the "recovery" option anymore. So... I'm out of ideas here. I'm really worried I bricked my device for good. My device powers on and everything, it just won't load up any OS, and I can't get into fastboot/recovery. Why I'm mainly worried is I failed to create a back up also. I'm running out of ideas here, and if ANYONE could help me that would be great.
RadicalMushroom said:
Hi there,
So recently I just tried rooting my HTC One M8, with the All-In-One tool kit. It was successful, I was messing around with it for a while, removing bloat wear, ect. Then I figured out about custom roms, and heard about CyanMod11. It turns out that it couldn't read my sim card for whatever reason, but it still worked and loaded up. Then, I tried Android Revolution. THAT one worked flawlessly, besides the fact that I couldn't take screen shots for whatever reason. I should of just left it there. Here's where things go wrong. Then, I tried ViperOneM8. After that, it failed to load up and is now in a endless boot loop. I can't get into fast boot either. However, one time I somehow did manage to get into fast boot, but I didn't see the "recovery" option anymore. So... I'm out of ideas here. I'm really worried I bricked my device for good. My device powers on and everything, it just won't load up any OS, and I can't get into fastboot/recovery. Why I'm mainly worried is I failed to create a back up also. I'm running out of ideas here, and if ANYONE could help me that would be great.
Click to expand...
Click to collapse
first you posted in the wrong forum this goes in Q&A
second what do you mean it won't go into fastboot / recovery ? what happens when your in the bootloader ?
I need the results of fastboot getvar all to determine what files you need to fix your phone ( not you serial no. or IMEI)
most likely your on an older firmware and you have s-on and the Rom you flashed requires s-off and the latest firmware
Gah sorry, I find this forum layout kind of confusing. So this is another problem. I cannot access "getvar", it just says device offline, and I close that command prompt and then the next one just says "please wait," and nothing happens.
What I mean by it won't go into fast boot, is when I hit power + volume down it won't load anything. Here's a pic I found off Google, I can't get to this screen here.
http://img.wonderhowto.com/img/22/98/63533775104674/0/unlock-bootloader-root-your-htc-one-m8.w654.jpg
RadicalMushroom said:
Gah sorry, I find this forum layout kind of confusing. So this is another problem. I cannot access "getvar", it just says device offline, and I close that command prompt and then the next one just says "please wait," and nothing happens.
What I mean by it won't go into fast boot, is when I hit power + volume down it won't load anything. Here's a pic I found off Google, I can't get to this screen here.
http://img.wonderhowto.com/img/22/98/63533775104674/0/unlock-bootloader-root-your-htc-one-m8.w654.jpg
Click to expand...
Click to collapse
Easy way to get into boot loader
Turn on your phone
When it gets into bootloop
Press and hold power+vol up+vol down until screen goes off
As soon as that happens press and hold power+vol down
You'll be in boot loader
And I must say you are a major noob
Navigate to hboot using vol buttons then press power button to select, you'll find recovery
These are just 2 modes hboot and fastboot
From fast boot you can select hboot and vice versa
And also getvar will work ONLY when you're in fastboot mode
Hboot mode is used for accessing recovery
navid0308 said:
Easy way to get into boot loader
Turn on your phone
When it gets into bootloop
Press and hold power+vol up+vol down until screen goes off
As soon as that happens press and hold power+vol down
You'll be in boot loader
And I must say you are a major noob
Navigate to hboot using vol buttons then press power button to select, you'll find recovery
These are just 2 modes hboot and fastboot
From fast boot you can select hboot and vice versa
And also getvar will work ONLY when you're in fastboot mode
Hboot mode is used for accessing recovery
Click to expand...
Click to collapse
I fixed my HTC One M8! Followed some advice on another thread and I just reflashed my TWRP, then I flashed the ROM again and everything is going smooth now!

Categories

Resources