So a while ago, I rooted my nexus 6 phone and along with it TWRP. So, today, I tried unrooting it, and in the process of doing this, I didn't notice something failed and after this, I locked the OEM, so now I can't unlock it. After doing this, my phone starts to boot, and the image for TeamWin Just keeps flashing, and when I try to go to recovery mode from the fastboot, it just tries to go to teamwin and the image for it just keep flashing as well. I have no idea what to do and I am really panicking. Could anyone please direct me to something that could fix this? I am limited in my knowledge involving fastboot and flashing custom ROM's so I need specific steps as to what to do. I really need help.
*Also, when I mean the image for teamwin keeps flashing, I mean the literal picture of the teamwin bootup keeps flashing on screen and nothing happens.
If you didn't select the lock bootloader option in Developer Options, then you should still be able to do the fastboot oem unlock. If you have, then I think you are out of luck...
Related
I apologize if this is in the wrong place, and I've really tried searching around, but nothing seems to work/ is tailored to the m8.
So, I just got an M8 new out of the box, rooted it and successfully installed cyanogenmod. Problem is, I was playing around with it, trying to get the GApp store and somehow (did what i think was) deleted my roms completely. Now upon booting up the phone I just get the "This build is for dev..." screen, and with the volume down+Power button to access recovery mode I constantly get put back to the fastboot screen. I tried flashing a custom recovery as in "Phone arena CWM flash recovery" guide, but no luck because my computer is reading the device as offline. I honestly have no idea what to do, and if anyone could help me I would be so greatful...
TL;DR: Stuck on boot screen, can't enter recovery mode, think i deleted all my roms, help please
On a scale of 1 - bricked, how bricked is my phone?
HUGE DEVELOPMENTS, GUYS! I've been able to access recovery mode again by re-flashing ClockWorkMod.
ctran1 said:
On a scale of 1 - bricked, how bricked is my phone?
Click to expand...
Click to collapse
On that scale, you are zero. If the screen comes on, you aren't bricked.
I recently tried a factory reset on my phone after finding that one of my apps was sending out spam texts to random people and racking up my text plan. Upon the first boot, it showed a green android man with a blue orb thing spinning in its stomach and kept going for hours.
My phone was previously running an unofficial build of CM12 and was unlocked and rooted.
Now, I just figured that I could just flash a new recovery to the phone and flash a new ROM to get it back up and running, but I also keep having troubles getting it to flash. Using 'flashboot devices', I see my phone's serial, but when I try to use 'flashboot erase recovery' or 'flashboot flash recovery recovery.img' seems to hang up. I finally got it to write clockwork recovery to the phone somehow, but the device still boots to the green android man w/ blue instead of clockwork. I thought it was an issue, so I have been trying to flash TWRP, and it just hangs, and doesn't even give the <waiting for device> text, so I know it sees it.
Can anyone help me figure out a way to get my recovery flashed correctly? From that point, I should be good to go, as long as it loads into recovery.
Tampered
I have tried everything I can think of, and it still stalls while it is supposed to flash the new recovery, then fails with the error "too many links".
Also, now the **TAMPERED** flag pops up at the top of the bootloader. It still lets me into the FASTBOOT portion, so I don't believe that it is effecting anything, so I will probably just have to worry about that later, if I really feel like going through the whole rumrunner/revone process.
TWRP
Not sure if it is a good sign or not, but I replaced the USB cable and was able to get TWRP to install and actually load once. There were errors after it booted, and I choose to do a full factory wipe to hopefully start over fresh, and the phone rebooted itself. Now TWRP seems to endlessly load while it the splash screen flashes on and off, almost as if it is in a bootloop. I tried reflashing with a slightly older TWRP for my phone, and no luck.
Also, another strange thing is that when I flash a new recovery file, it shows that it only takes a total time of 2.607s. If feel like this is quite short and I remember it taking a bit longer in the past. I just feel like it is not writing the entire recovery, hense the blinking teamwin logo that seems to be stuck in a bootloop.
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...
So I recently got a Nexus 9. I think it was affected by the battery issues with android nougat. I rooted and used greenify and got much better battery life but decided I wanted to unroot and see if over a couple days the battery life would have gotten better. So I connected to my computer and stupidly sent the "fastboot flashing lock" command and now my Nexus is stuck in a boot loop because of TWRP. I knew that locking the bootloader would initiate a factory reset but didn't take into account that TWRP may affect that so now I can not use my Nexus. The device says it is a developer edition and not intended for personal use and I don't I know what to try. Just letting everyone know I only tried to sideloading and flash. I appreciate everyone who takes the time to read this and try to help.
Have you tried following instructions from google to flash a factory image ?
https://developers.google.com/android/images
I have but I can't flash due to the bootloader being locked and I can't sideloading because every time I tried it just errors or does nothing
AUSTIZ1997 said:
I have but I can't flash due to the bootloader being locked and I can't sideloading because every time I tried it just errors or does nothing
Click to expand...
Click to collapse
Did you try booting your nexus to fast boot and execute fastboot oem unlock?
I have, it just send me an error message
Update, I was able to finally get into the custom recovery and tried to flash the stock recovery and now it just boots into fastboot mode but I got rid of the custom recovery (as far as I know) and the boot screen that said the tablet was a developer device
Same problem here in May 2017, the OTA update prompted by Google sent the device into a bootloop. As the Bootloader was locked and there was no way to change to USB debugging mode it wasn't possible to use Recovery mode or to flash an OTA. Wiped data cache, tried all options in HBoot menu, tried flashing OTAs and full block OTA didn't work either. Just stuck in bootloop.
Repair shop encountered same problems so they then suspected the logic board. They heated it up to reflow the solder and success! Logic board may fail again through dry joint but I believe this risk can't be avoided by switching manufacturer as they all use the same component-to-board soldering practice.
Hi All,
I am currently in the phone repair business. Well i buy as much as i can fix and sell on. Its all fun. I have a very nice one currently and looking to see if anyone has ideas. All i want to do is boot to recovery that is my current goal.
So phone clearly has corrupt installation, likely a flash Rom or update gone wrong. It boots to Huawei logo then reboots and that's all it does. Tried de-powering and all sorts including removing battery cable but to no luck.
There is no recovery mode
No download mode
Can get to fastboot but unable to run commands it seems due to FRP lock. I am not worried about FRP lock at this time, i only want recovery back.
Tried:-
All flash commands and all fail
Any attempt to get to receovery or download mode fails
All three buttons to force SD card boot fails
Currently trying to boot using SD card but seems i need to change boot devices from within recovery. Well it has no recovery mode so no luck there.
So it is pretty much a brick at this point and could be a write off but before I give up does anyone have any other ideas? maybe a FB command i can run with FRP lock and bootloader lock on?
Thanks
Karl