I'm fairly sure I've managed to brick my phone, but I wanted to check before I accept defeat.
In short, I tried to follow this guide, huawei-p9-nougat-emui5-0-full-firmware-b339-europe-vodafone flashed the second file first, and couldn't get the phone to boot.
Attempted to use the recovery tool built in, but it couldn't recover the phone.
Eventually, under the assumption I had entirely ruined my phone, and some searching came across this tool DC-Phoenix-flash-repair-tutorial
Attempted to use it to flash the initial image as mentioned in the first link, which didn't work.
After multiple attempts at various peoples suggestion, I tried to go back to basics, so used the DC Pheonix tool to flash the TWRP image to the device, which appears to have worked, I can boot into TWRP.
I then booted into TWRP and tried to install the stock ROM from this forum, which fails because it cannot mount /data /cust etc
I've gotten to the point of giving up after spending hours doing what I thought were fixes to realise I've probably destroyed my phone, any help would be greatly appreciated
Related
I have a droid bionic that I acquired used that had some major stability issues when I got it. It appeared to be on stock ICS when I got it, so I tried to reflash through rsdlite. The flash just stuck on step 1 of the flash. I've tried HOB method, and every other method I've come across, but all writes to the phone just hang indefinitely. All of the erase steps complete though, and when I've unplugged the USB cable after hanging and plug back in, it will move on to the next erase, copy, write step and hang on the write. So now I have a phone that appears to have every thin wiped during the deletes, and no system of any kind. From day one, when entering recovery I would get several lines about not being able to mount cache etc. The only thing that flashed successfully was a radio flash.
I appreciate any help, but please don't direct me to any more guides unless it is relevant to the can't mount... errors I'm getting. I need to find the reason why no write operations complete and just hang. That's where my problem really lies.
Genaugmen said:
I have a droid bionic that I acquired used that had some major stability issues when I got it. It appeared to be on stock ICS when I got it, so I tried to reflash through rsdlite. The flash just stuck on step 1 of the flash. I've tried HOB method, and every other method I've come across, but all writes to the phone just hang indefinitely. All of the erase steps complete though, and when I've unplugged the USB cable after hanging and plug back in, it will move on to the next erase, copy, write step and hang on the write. So now I have a phone that appears to have every thin wiped during the deletes, and no system of any kind. From day one, when entering recovery I would get several lines about not being able to mount cache etc. The only thing that flashed successfully was a radio flash.
I appreciate any help, but please don't direct me to any more guides unless it is relevant to the can't mount... errors I'm getting. I need to find the reason why no write operations complete and just hang. That's where my problem really lies.
Click to expand...
Click to collapse
i recently had issues with rsdlite but eventually got it working with jb4.1.2.
i am using 5.7 and erased a couple things from the xml file to get it working. if you dont care of root install 4.1.2
podagee said:
i recently had issues with rsdlite but eventually got it working with jb4.1.2.
i am using 5.7 and erased a couple things from the xml file to get it working. if you dont care of root install 4.1.2
Click to expand...
Click to collapse
I've tried to flash individual parts of the the fxz but it still hangs on every write operation no matter what method I try. I'm becoming convinced it's a hardware fault. I've tried several versions of rsdlite. I can't get one package to complete a write operation. I've seen others with similar problems, but none that couldn't get make at least some progress with a flash, even if they had trouble getting it fully flashed. Unfortunately, the erase commands for the different methods I tried did complete without issue, so now I have no system at all it seems.
Hey all. Appreciate any help, because Im out of ideas here. A friend brought me his Vzw G2 yesterday morning, which he had bricked trying to install cm12 (He's had it rooted and unlocked since he got it), and he apparently tried to install a cm12- compatible twrp, and thats when he got a secure boot error. I fixed it just by using the lg flashing tool and a tot and restoring it to stock, but when I tried to flash it, I ran into the issue of twrp wouldn't flash anything, some drinks were had, and out of drunken stupidity last night we tried to dd a new copy of twrp, from twrp's shell onto it, which sent it back into a brick. Now, its worse, download mode cant even be accessed. I've been at this all day trying to fix it. Trying to go to recovery takes it to fastboot, but, it goes blank after about 10 seconds, and then no fastboot connection can actually be made to the device so I cant use fastboot. I'm on linux, so it does show all of the devices partitions under /dev, so I tried another post's idea of manually dding the entire bootstack onto the device, partition by partition, but that didnt seem to change anything. It's on the 39a lollipop update. Any one have any other suggestions?
Any luck?
No, sadly still nothing. I've tried re-dding a few times, but I cant think/read anything else to try.
Hello,
So after following the guide on this post, I managed to flash TWRP, but after I tried to flash SuperSU, it wouldn't work because it would fail right after "Extracting ramdisk". Seeing that didn't work I dug around on other forums and stumbled upon this.
And so I backed up my boot, system and data partitions (not the system image though) and flashed SuperSU zip. It led to a bootloop where it wouldn't get past the HTC logo (it would reach the logo, stay there 2 seconds, than reboot). I went into TWRP where I restored the previous backup which, to my surprise (and honestly I don'y really know what happened) the bootloop didn't go away, but had changed (instead of rebooting, it just freezes at the HTC logo).
I messed around trying to flash a stock ROM (from here, more specifically the A56DJ_PRO_DUGL asia zip) but didn't go nowhere, even worse, I managed to lose my backup together with wiping the system partition. And here I am, not knowing where to go next. I don't really understand how the RUUs work (all the suggestions I find online keep talking about the .exe files, which I can't seem to get a hold off) and anything else doesn't seem to be available.
I guess if anyone could guide me through this, that would be great. I'm pretty comfortable with the command line and how things 'kinda' work, so I don't need very thorough explanations, just a few pointers.
Thanks!
Hi!
I have managed to get stuck along the way with regards to installing a custom rom on my XT1072.
It all started fine. I managed to open the bootloader, root my device and install TWRP. I then accidentally managed to wipe all data from my phone, including my OS. (Phone is stuck on Bootloader screen and TWRP says "No OS installed").
Luckily, the phone has a SD card slot - so I tried going what I have done in the past on my Samsung tablet -- installing a custom ROM through the SD card. The good part, the phone finds my SD card and the roms/files loaded onto it. The bad part..... every rom I tried says "this ROM does not support bootloader 4822".
Is this another code for "you've bricked your phone" or am I just not choosing the correct ROMs? I also once got the message that my phone is not a "THEA" version or so. Rooting wasn't this hard on my samsung tablet... *sigh*.
I would really like to get help with this, I really like the phone even though it's not been used for a long while and therefore I was trying to get a custom rom on it to see if I could somewhat bring it back to life again.
Thanks in advance!
Anyone?? Pretty please!
You flashed the wrong TWRP.
You flashed a recovery that is not for your device. XT106x is TITAN, but XT107x is THEA. They're not the same. You probably flashed a recovery for Titan because most of the rooting guides for this device are flawed.
Also, playing around with Fastboot is extremely dangerous. This tool is very advanced and powerful and if you shoot yourself in the foot with it you may blow your whole leg off. This tool is capable of hard bricking your device if used incorrectly so use it carefully and seriously. Hard bricks cannot be fixed. There is no blankflash for this phone.
Download a proper Thea ROM, any version you like. I personally prefer LineageOS 15.1, which is what I am using right now. Then, download a proper TWRP recovery image for Moto G 2014 LTE or "thea" from the official TWRP website. Now connect your phone, boot to the bootloader menu and plug your phone to your computer.
Now, enter this.
Code:
fastboot flash recovery twrp-3.2.1-1-thea.img
This command orders Fastboot to write the recovery image to your recovery partition. Now boot to TWRP and flash your ROM from there.
When you get a new device, the first thing you must do before attempting anything on it is to RESEARCH. You went into this because you did not research enough.
Lesson learned. Have a nice day.
You can close this thread, your problem has been solved.
Oh... right. If only I knew how....lol
add [SOLVED] to the title
I am having a hell of a time rooting this phone. (Motorola Nexus 6 XT1100)
I am trying to follow this guide: https://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
If anyone can offer some suggestions, they would be greatly appreciated.
I managed to get as far as unlocking the bootloader in fastboot mode.
The next step, obtaining root, is where all my problems started.
I downloaded CF Root and extracted the files, as instructed, allowed the root tool to run, (I'm using Linux, if it matters).
When the process was finished, and my phone attempted to reboot, it got stuck on the Google screen with the little lock (showing unlocked).
I allowed the phone to stay in this mode for around 30 minutes thinking it just needed time.
It never did anything. I attempted to let it try and start up again (a couple times actually) and it never goes past the Google lock screen.
I powered down the phone and restarted in fastboot mode, and attempted to run the CF Root tool again, with the same result.
I am currently stuck with only having access to fastboot.
I tried to flash a recovery and boot into that, but it won't allow that either. Perhaps this isn't even possible (YET), as it's not in the instructions to flash a recovery until after the rooting process, but I thought I would try it anyway.
I have tried flashing TWRP and Lineage recovery. No success with either, although the terminal is saying
sending 'recovery' OKAY
writing 'recovery' OKAY
But when trying to reboot recovery I get hit with
unknown reboot target recovery
Anyone know what's going on and how I can get this resolved? I just want to install a recovery and flash a custom ROM.
In that guide you can follow my journey to root starting in post# 929. I had & have had a LOT of help from my fellow XDAers. They're great & thank you all.
Thanks!
I'll check it out.
Boy, oh, boy.
I don't know what is going on.
I finally managed to get out of the bootloader screen.
I don't know what/how it worked. I downloaded Nexus Root Toolkit to a windows computer and tried the Flash Stock + Unroot option.
It keep saying waiting on device or device not detected or something ( I cant remember exactly, it was hours/many error screens ago!)
Next, I tried the option for Root + Add a Custom Recovery and directed it to where my TWRP file.
Again it acted like it was doing something. Even found my connected ADB device. Went through a couple processes, said it would need to restart a couple/few times. Everything was trucking along just fine until suddenly, it got hung up 'Waiting on device"
Not sure what happened, but all of a sudden, it could no longer find my device.
For chits and giggles, I decided to try and reboot recovery from the bootloader screen. I had attempted this many times and all it did was start back up in bootloader, BUT, this time, it actually started up in some recovery program I have never seen before. It wasn't stock and it certainly wasn't TWRP!
At this point, I hooked my device back into my computer running Linux and attempted to push TWRP, and reboot in recovery.
It worked!
Now that I had a recovery I was comfortable using, I proceeded to push my ROM.
Wanted to try Lineage with MicroG, but I am not advanced enough to go that route. I could not get a fake app store to work.
Guess I'll have to stick with what I know. I love the idea of MicroG, but it apparently doesn't work with Pure Nexus.
Anyway, just wanted to post some closure for this thread. I know the Motorola Nexus 6 is an old phone, but I like it. This is my second one. My first one, screen finally cracked and it was cheaper to just purchase a new one from Amazon than to replace the screen.