Hello guys
So, here's the deal. Few months back, I messed up my One and got it stuck at the grey HTC Screen. Couldnt boot into system, because I guess there was no ROM on the device. Thanks to you guys here at XDA, I got the situation analyzed and took the device to an HTC Service Center who told me to get my motherboard replaced. That was way too costly, so I got it JTAGed. The device now boots into ROM, but it cant boot into the bootloader. So I cant unlock the bootloader, S-OFF, Root or anything.
I can only boot into ROM. Can anyone please explain why this is so and what can I do to get my bootloader and recovery back.
Any help will be greatly appreciated!
Thanks
Which methods are you using to get into the bootloaader ?
Seanie280672 said:
Which methods are you using to get into the bootloaader ?
Click to expand...
Click to collapse
Sorry for the late reply..i was out of town..
I tried adb and manually pressing power+down..but to no avail.
I figured it out in the end though...i dont know what happened but the device suddenly went into the bootloader one day and now its working fine.
I have a question..
My device has been jtagged. Its now bootloader locked, unrooted, s on.
Is it dangerous for me to try to unlock and s off and flash a new rom?
Can a device be flashed after its been jtagged? Im sorry I dont have much experience with jtag.
Thanks!
Hi
I had Moto G XT1068 with stock rom, bootloader locked and no root.
Then I decided to follow this tutorial http://forum.xda-developers.com/moto-g-2014/development/tool-moto-g-xt1068-andoid-l-updater-t2964933 to install Lollipop with root and bootloader unlocked and worked fine but I couldn't get acess to 3G, the dialer wasn't working and I faced a few more little bugs so I decide to downgrade to Stock rom again and followed thus tutorial http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
Now I can't pass the bootloader unlocked logo. I have acess to fastboot and I have Philz recovery installed. I searched and found some tutorials to unbrick the phone but I'm a little afraid to follow the wrong one and do worst.
Can you help me please? Is my phone soft bricked or hard bricked? Can I have hope?
Thanks to all.
PS: my english is not perfect, if you don't understand something please say.
Hi guys
I have a similar situation to this going on
http://forum.xda-developers.com/asc...nformation-t2908514/post56081582#post56081582
and when I go into fastboot/recovery menu I get phone locked and I cant unlock it to flash roms
Tried various methods to unlock without luck,
any suggestions?
Why nobody tried to read ....
Okay lets us start.......
Wich Firmware on this phone?
@fengqiu, you have to get unlock code and unlock bootloader. There's no other way to unbrick device.
hmm I tried to flash myRom onto this phone. it has no firmware atm.
Okay, I will try get the unlock code....
Hello guys,
After i tried a few different roms around here, i came to the conclusion that stock rom works the best for me.
I managed to revert back to stock rom BUT, i am not able to lock the bootloader to its factory state.
Relocking the bootloader via fastboot won't get rid of the message screen that bootloader is unlocked during bootup.
If anyone knows how to get the device back to its original firmware state, please share it with me.
My device is : VTR-L09C432.
Thank you!
A friend of mine has a Redmi note 9 (merlin), his device recently got into a bootloop, and he can't really use it anymore. He's not a technical person, so he hasn't unlocked the bootloader or messed with it in any sort of way..
My first question is, how did the device get into the bootloop? Is it due to a hardware defect, or did the software just randomly get corrupted?
My second question is, how will i reflash the stock ROM? I know that in order to fix this, I'll need to flash the stock ROM to the device, but the bootloader is locked, so how can I do this? Does Xiaomi have a tool to reflash stock even with a locked bootloader? Or do I need to flash it as an update via an sdcard or something? Does fastboot work on xiaomi devices with a locked bootloader? If so, should I flash the image using fastboot? How would I go about doing that?
I'm quite experienced with Custom ROMs and Recoveries, but I've never had to reflash a stock rom before, so I'm a total newbie to this. If anyone here could help me out, then my friend and I would both greatly appreciate it!
PhotonIce said:
A friend of mine has a Redmi note 9 (merlin), his device recently got into a bootloop, and he can't really use it anymore. He's not a technical person, so he hasn't unlocked the bootloader or messed with it in any sort of way..
My first question is, how did the device get into the bootloop? Is it due to a hardware defect, or did the software just randomly get corrupted?
My second question is, how will i reflash the stock ROM? I know that in order to fix this, I'll need to flash the stock ROM to the device, but the bootloader is locked, so how can I do this? Does Xiaomi have a tool to reflash stock even with a locked bootloader? Or do I need to flash it as an update via an sdcard or something? Does fastboot work on xiaomi devices with a locked bootloader? If so, should I flash the image using fastboot? How would I go about doing that?
I'm quite experienced with Custom ROMs and Recoveries, but I've never had to reflash a stock rom before, so I'm a total newbie to this. If anyone here could help me out, then my friend and I would both greatly appreciate it!
Click to expand...
Click to collapse
You can flash safely using fastboot, even with locked bootloader.
Official MIUI has signed images, so them will be flashed without issues.
If you can't enter in fastboot, the spflashtool is the only solution.
Good luck.
Ah, its VD171. You know a lot about this device, do you know why it began to bootloop in the first place?
Only who caused that knows.
Alright, apparently I misread his message. He says that the phone is stuck on the Redmi screen, not the MIUI screen. Doesn't this mean that it's stuck on the bootloader, as its not reaching the MIUI screen, so it must not be bootlooping. He says he took it to a repair shop, and they claim that it is a ram/motherboard fault. I doubt that this is likely, could anyone help me with this matter?
I can think of three posibilities:
1. It is stuck on the MIUI screen, but he is calling that the Redmi screen.
2. He HAS messed up his device himself, probably wiped the OS, and now is stuck on a loop at the Redmi screen.
3. It is actually a fault in the phone.