Greetings All,
So I did a very stupid move and kinda soft bricked my M8. I received my Lollipop update, restored my stock recovery, applied the update, rebooted phone, applied TWRP and flashed SuperSU. Once I booted back into phone I saw that I still had Xposed installed and bundled and the idiot that I am, ran the uninstaller. Now the phone boots up and after showing the white boot logo sits at a black screen.I can get into recovery mode so I am pretty sure that if I download a Lollipop custom ROM I can get booting again? Factory reset did not help and I did not do a nandroid either :/. I am still S-ON so I can't flash the RUU file :/.
Any assistance will be greatly appreciated.
Problem resolved. Please ignore this thread .
Related
Hey guys,
I went to flash a new stable build of Froyo on my Desire this morning.
And i backed up using Clockwork, and then the ROM all installed fine. But once the phone had booted up, it stayed on the custom boot logo, despite the keypad lighting up, the green charge LED coming on and me being able to lock and unlock the phone.
So i figured that this was a problem and went to back to restore my old ROM and carry on like i have done many times before. However once i have booted into Clockwork, and gone to the recovery section, i select my most recent backup and the device then says "No Files Found" in the recovery zip.
And when i try to install update.zip from my SDCard the device just flashes up with installation text for about 2 seconds then vanishes and goes back to the clockwork menu having done nothing
What can i do?
i wouldnt worry about it too much
your phone completely works and youre not restricted of any access
seeing that clockwork is not finding any files have you tried making a new backup?
have you tampered with the recovery lately?
if recovery is not finding any files then maybe there is a problem with it, and if i were you i'd reroot my phone with unrevoked to re-install recovery.
if your recovery actually just does not work it could mean that the recovery image is corrupt, this can be fixed by installing a RUU (note that this will unroot your phone but re-install the recovery image).
if this is not the case then im sure im soon to be corrected by someone more knowledgeable than me
Well, i wiped the Cache and Data and now the phone boots up and functions fine, however both mobile internet and Wi-Fi both dont work, but i figure this is just the rom i am using.
So i'm just gonna reroot, sideload clockwork and what not and then try putting the Desire HD rom on it haha.
Thanks for the help
Hi!
So just a quick background. I have S-OFF'd and flashed a custom ROM on my mates Desire HD few years back and have a bit knowledge about the device.
Today I showed him some of the 4.1-4.2 ROMs available for DHD. In TWRP I did a nandroid backup of his current Blackout ICS and flashed CM10.1. Everything went just fine, but the ROM was not the right for him, so I tried Venom Sense 4.1. I did a clean install on the Venom ROM and wiped everything in Aroma.
Apparently I was not focused enough and the Aroma installation failed with just the wipe. No ROM installed. Phone rebooted with no ROM and the caught stuck while booting. I thought this was no biggie and I would just restore the backup from TWRP.
Then all suddenly went to hell in a hand basket. Phone was/is unable to boot into bootloader with any vol+/- combination. It won't boot into recovery ether. Just straight into the ROM, which is not there -> bootloop.
TL;DR No ROM installed, unable to boot into bootloader or recovery. ADB/Fastboot showing no signs of connection.
Did I just buy myself a dead DHD and an angry friend?
EDIT: SOLVED. So, issue was solved by 1000 times randomly pulling the battery and pressin vol up and down. 999 tries straight booted into the OS, but 1000th try somehow got me into the hboot. No idea why or how.
Hey guys, I've managed to semi-brick my one x. Not too thrilled right now to say the least.
I was halfway through rooting the device when it ran into a communication error. It now is in a endless restarting loop, so with no idea a tried the factory reset from the HBoot menu. I've managed to get TWRP 2.3 in recovery mode, but I'm not sure where to go from here.
I don't really care weather it gets back to the stock ROM or a custom mod, either of those would be preferred than the shiny brick I have at the moment.
Thanks,
All I did was do a reset to factory settings on my tablet, it rebooted and it's now in a TWRP bootloop?
I see the TWRP logo come on and then the screen goes black and then the TWRP logo comes on again?
Please help! I have no idea what to do???
I searched all over Google but couldn't find anything that worked?
This has happened to a lot of people: http://forums.androidcentral.com/sa...p-after-factory-reset-cyanogenmod-12-1-a.html
So, I'm going to make this warning REALLY BIG so this doesn't happen to you as well:
If you are running CyanogenMod 12.1 and TWRP recovery, then DO NOT ever do a FACTORY RESET.
You will break your tablet.
HOW TO FIX:
The only way I was able to fix this was to use Odin and put the stock firmware back onto the tablet.
Hello, can anyone help me, where to download the stock firmware.
I think, I'm having a same problem here. My boot screen are blank, right after the Title screen
I recently decided to to root my SM-t110 so that I could upgrade to LineageOS, but after I had gotten TWRP working it offered to install SuperSu so that it could be rooted, so I rebooted SuperSu was installed and then I had to reboot and now I'm completely stuck in TWRP. I can't even boot into safe mode, download mode, or anything except TWRP.
I had also had backed up everything and then tried to restore from that, but even that didn't work. Any help would be very much appreciated!
I Have fixed the problem, I'll come back and post how I fixed it in a couple of days.
Never mind, it appears I'm stuck in a bootloop again, except this time it's far worse because it's stuck on the launch screen of TWRP 2.7.0.1 and then artifacts into a back bar at the top half and then two purplized TWRP boot images next to each other on the bottom half.
Also, last time I fixed it by flashing TWRP again, except through TWRP itself instead of Odin (I put the TWRP file on the sd card).
Any help with the new issue would be helpful and appreciated though.