I have hard bricked my device, even motherboard is dead, no sound when connected to PC. Phone is in waranty. What should i say to realme support so they won't be able to tell that I tried to install custom ROM and charge me for motherboard. It's a new phone. I unlocked the boot-loader.
Deepakk88 said:
I have hard bricked my device, even motherboard is dead, no sound when connected to PC. Phone is in waranty. What should i say to realme support so they won't be able to tell that I tried to install custom ROM and charge me for motherboard. It's a new phone. I unlocked the boot-loader.
Click to expand...
Click to collapse
best bet is to visit SC and tell them your device stopped working after official update . don't say anything else
I told them that the phone failed to start after a software update. They repaired it in 2 hrs and gave it back. So the motherboard was not fried as I thought.
What happened was that the TWRP recovery someone provided here has not worked, my device failed to get in to TWRP recovery after I have re-started the phone, So, I tried to flash with other TWRP versions that some people linked to in their posts on Realme U1 on other websites. None of them worked and after sometime my phone went in to bootloop, I got it in to fastboot screen by holding down the power and vol down button and tried various fastboot commands, none of them fixed the bootoop. I finally gave the command 'fastboot oem reboot -recovery' then it switched off the phone.
Related
Hey everyone, so I woke up Saturday morning to a wonderful surprise, and am just getting around to letting everyone know and maybe throw their suggestions my way!
Device: Tmo LG V10, H901
Recovery: [TWRP] Recovery: V10_H901_pplus [V3.0.2-0] [08/16/2016]
ROM: [ROM] [STOCK] [H901] V10_H901_V20J_Stock_Custom_2e [08/15/2016]; V10_H901_V20J_Stock_Custom_2e-signed
Root: Systemless Instructions - How to - 08/08/2016
Xposed: Systemless Xposed, see root guide above
Friday night, I was using my T-Mobile V10 like normal. No recent modifications, no new apps, adjustments, etc... Plug it into the charger and go to bed for the night. No issues right?
I wake up Saturday and the screen is blank. The phone isn't responding to the power button, so I hold the Vol-Down+Vol-Up+Power down to reboot it.
The phone won't reboot. So I pull the battery, and throw it back in.
Phone hits the LG logo, yey!
But it never moves from the LG logo
So at this point, I try booting into Recovery (TWRP) and the phone seems to not be responding to my button commands. It hits the boot logo and never does anything else.
I tried to boot into Download mode, nothing, just sitting on the logo.
After messing with the phone, with and without a USB cable attached to my laptop, I finally get the device into Fastboot.
In fastboot, I can run commands, but since I am on V20J, I am unable to flash or boot TWRP
I was also able to get into download mode when plugged into my PC only.
So down below, I will go over all the stuff I have tried.
Modes I can enter-
Fastboot
Download Mode (USB)
Stuff I tried-
LG Bridge Update
Update says it succeeds
Still does not boot
When I reconnect LG Bridge again, it says an error occurred and wants to update again
Direct .img flash via Fastboot
Using the steps from this post
Unable to flash, FAILED (remote:unknown command) due to V20J I believe
Flash V20J .tot via LGUP
It seems to flash successfully, but the phone still doesn't boot
So I left for the T-Mobile store Saturday, phone not booting, just stuck on the logo.
They are Warrantying the phone, so I am just waiting on a back-ordered replacement now.
EDIT: The Plot Thickens....
So I thought I would fire up the phone this morning, maybe try some other updates/flashes again, maybe something will happen.
Now I cant even get into Download Mode (USB) anymore.
It shows Download Mode on the screen, then the phone just reboots.
Additionally, on first boot I received some sort of error on the screen, but it went away so fast I couldn't read it.
Now I can't get that error to come back for the life of me...
I am just so confused now. The phone has a mind of its own.
My brother had 2 V10's that did that. Replaced under warranty.
Exact thing happened to me back on pre mm.. I got into twrp after many many many tries.. Flashed an old back up and phone booted. I was able to get into the phone long enough to relock bootloader before it started the same crap... Warrantied it out and that was that..
Yikes. Making me scared once this warranty is up.... Would hate to just lose a phone randomly for no reason!
Swizzle82 said:
Exact thing happened to me back on pre mm.. I got into twrp after many many many tries.. Flashed an old back up and phone booted. I was able to get into the phone long enough to relock bootloader before it started the same crap... Warrantied it out and that was that..
Click to expand...
Click to collapse
Can you plz guide how you relocked bootloader? I am rooted and using custom rom. Should I first install stock kdz and then give command via fastboot or it must be done with root? Thanks
Waxim1 said:
Can you plz guide how you relocked bootloader? I am rooted and using custom rom. Should I first install stock kdz and then give command via fastboot or it must be done with root? Thanks
Click to expand...
Click to collapse
You can relock via fastboot using the command
Code:
fastboot oem lock
Use the below command to check your current status
Code:
fastboot getvar unlocked
I believe it even says these commands on the screen when in fastboot.
Fenopy said:
You can relock via fastboot using the command
Code:
fastboot oem lock
Use the below command to check your current status
Code:
fastboot getvar unlocked
I believe it even says these commands on the screen when in fastboot.
Click to expand...
Click to collapse
Thnks I jav read these but need to know if i should b on stock rom before locking or what? And any known issue while trying relocking it?
Hi,
Can someone help me? My Moto Z bricks itself:
I have a Moto Z XT1650-3. On January 31 the phone shutdown alone, after I unlocked teh screen with fingerprints then I restarted the phone and all fine. Then the phone shutdown again, when the phone restarted. It restarted in fastboot mode I switched to restart normally when it showed these message "Your device has failed verification and may not work properly".
I have my phone unusable. When my phone returned for the Moto Technical Support It only boots in fastmode. No recovery no OS (android). I've to say that I never try to root or unlocked the bootloader of my Phone it worked really smooth. I bought the Phone on October 4th 2016.
Finally I tried to reflash the Stock Firmware via fastboot and the problem continues . The phone only boots in fastboot again an again. I tried via fastboot the CMD: gtrvall and said tha warrantyavoid NO.
When I tried recovey mode the same message appears "Your device has failed verification and may not work properly" and I cant do anything.
I wonder someone can help me.
Regards
So you tried to reflash the firmware via fastboot and your device is still dead?
I had the same issue but flashing via RSDLite fixed it.
In your case, I may have to throw in the towel and assume that a critical block on your system partition is corrupted beyond recovery, possibly caused by a defective NAND module.
D13H4RD2L1V3 said:
So you tried to reflash the firmware via fastboot and your device is still dead?
I had the same issue but flashing via RSDLite fixed it.
In your case, I may have to throw in the towel and assume that a critical block on your system partition is corrupted beyond recovery, possibly caused by a defective NAND module.
Click to expand...
Click to collapse
Hi
Yes i tried to reflash via fastboot it didn't worked the phone boot until in fastboot mode and sometimes the Motos logo appears and then again fastboot mode?.
Thnks for answer but if it is this i think that its a hsrdware failure and the warranty must have to apply in this case because my phone is until in warranty I think that this problem its hardware from the first day and this message its like. Warning that something isn't right?
I will try again with Motorola warranty to replace the phone
Regards
Hi,
I'm new here, so please excuse me if I am posting in the wrong category.
So I tried to root my Doogee F7 (not the pro version) using fastboot and TWRP, and it resulted in a sort of bootloop where it says:
Code:
Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds
And then it restarts and gives the same message again. This loop has been going on for some time and I can't stop it because the phone has a non-removable battery and I have tried every possible combination of buttons (i.e. Power + Volume Down + Volume Up).
The process I used in my attempt to root was as following:
1. I used
Code:
adb reboot bootloader
to go into fastboot. (I already set up everything like USB debugging and OEM unlocking in the developer options)
2. I then used
Code:
fastboot oem unlock
and pressed Volume Up to unlock the bootloader. All was successful.
3. I then tried to flash TWRP to recovery and I believe this is where everything went wrong. I flashed it using
Code:
fastboot flash recovery recovery.img
and it was successful, according to the command prompt:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery "C:\Users\momen\Downloads\recovery (1).img"
target reported max download size of 134217728 bytes
sending 'recovery' (12832 KB)...
OKAY [ 0.562s]
writing 'recovery'...
OKAY [ 0.213s]
finished. total time: 0.779s
4. After it finished I used
Code:
fastboot reboot
to reboot the phone and that's when it got stuck.
At the moment I am just letting my battery run out, as I have no other way of turning off the phone, and neither adb nor fastboot is working.
I don't really know if my device was even supported, but I followed the instructions on various websites stating that I should first unlock my bootloader, then flash TWRP, then flash superSU onto it, and my phone would be rooted. I used the latest TWRP image, and I think that was where I went wrong. Is there anything I can do to get my phone to work again?
Hey! i´m sorry for your phone, can you tell me any updates, is it fixed now? what happened? i am about to do the same process to root my Doogee F7 and i´m very worried that my phone gets bricked, so please, i need your recommendations.
I hope everything is alright with your phone.
solartediego said:
Hey! i´m sorry for your phone, can you tell me any updates, is it fixed now? what happened? i am about to do the same process to root my Doogee F7 and i´m very worried that my phone gets bricked, so please, i need your recommendations.
I hope everything is alright with your phone.
Click to expand...
Click to collapse
Ah yes, sorry for not updating. I managed to connect my phone to my PC again using the flash tool and then I could flash the original ROM back onto it. I found the ROM by Googling for a bit tho I dont have a link. Be aware that if you do this, it basically factory resets your phone, locking your bootloader again and all. If you do manage to root your phone please contact me as I still have not managed to do so.
Edit: This process of flashing back your ROM always works as long as your phone powers on, so don't worry too much about bricking your phone. I think I've bricked my phone over 20 times trying to root it, and it worked every single time.
Hello there. I suggest that you use "fastboot boot recovery.img" than using "fastboot flash" if you are not sure if the custom recovery works (or if you just want to test/try it). In this way, you'll just boot the custom recovery temporarily (and your stock recovery is still in tacked).
For rooting your device, first you'll need a working custom recovery for your device (you used TWRP, very first if it works or compatible with your device).
Insyder28 said:
Ah yes, sorry for not updating. I managed to connect my phone to my PC again using the flash tool and then I could flash the original ROM back onto it. I found the ROM by Googling for a bit tho I dont have a link. Be aware that if you do this, it basically factory resets your phone, locking your bootloader again and all. If you do manage to root your phone please contact me as I still have not managed to do so.
Edit: This process of flashing back your ROM always works as long as your phone powers on, so don't worry too much about bricking your phone. I think I've bricked my phone over 20 times trying to root it, and it worked every single time.
Click to expand...
Click to collapse
Hi.How you actually managed to connect your phone to PC using flash tool if you were in a bootloop and had no access to fastboot mode or recovery?
ciubsy2004 said:
Hi.How you actually managed to connect your phone to PC using flash tool if you were in a bootloop and had no access to fastboot mode or recovery?
Click to expand...
Click to collapse
Im interested too in your process to flash TWRP again, as i am in the same boot loop than you with a Doogee S60. I´ve waited till the battery ended, but now flash tool doesn´t recognize my phone. If i charge the battery, i get a boot loop again..
TheBidan said:
Im interested too in your process to flash TWRP again, as i am in the same boot loop than you with a Doogee S60. I´ve waited till the battery ended, but now flash tool doesn´t recognize my phone. If i charge the battery, i get a boot loop again..
Click to expand...
Click to collapse
I have managed to get the flash tool recognizing my phone.Had to keep pressed volume up,if i recall properly(or try volume down) before connecting usb cable to phone with flash tool opened and . It was a while ago though and i can't remember exactly which key was for sure. Hope this helps
Other rather I soft bricked it and went into fast boot bootloop but somehow resolved it. Here's what happened:
I followed the instructions and unlocked my phone after seven days. I then proceeded to flash the India rom via fast boot (done this before on other xiaomi devices) as the current custom rom offerings aren't great and are buggy.
Then I think there was either a cable issue or a usb port issue (but I used the same usb port to flash other devices) which resulted in some error when doing fastboot (too many lines).
I then replaced the cable and tried again and it didn't let me flash the latest India rom (again my phone is unlocked and China set ie. Raphael). Telling me incorrect device etc. Not sure if this was the anti roll back issue or just again a cable issue.
I then tried to fastboot flash the china base rom but it failed repeatedly. Any attempt to switch off the phone results in me rebooting to the fastboot page.
Amazingly the computer detects the fastboot device but I'm unable to run any commands eg. Fastboot oem device info etc. It also now tells me that I have an incompatible device to Raphael!! So China set can't flash China rom....
With the last throw of the dice and almost concluding I now have a brick of a phone I decided to change usb port and tried flashing again the latest v15 China fastboot rom. After the third attempt there seemed to be progress... 200+ seconds later an error came up in the miflash tool and I thought here we go again.
To my surprise the phone actually rebooted which was why the error came up.
Thank God it booted and is now working but oh my God what an ordeal I had to go through.....
Sent from my ONEPLUS A3010 using Tapatalk
I am currently trying to install LineageOS on my phone. I personally have never unlocked or reinstalled a new operating system on my phone. I looked on some XDA forums for some guides and i found one and followed the steps. I unlocked my phone and I installed a custom TWRP because I was trying to downgrade the phone back to android 11. Once i was done flashing the file to the phone and rebooted it doesn't boot anymore and only gives me a booting screen for a few seconds after I hold down the power and volume up button for a few seconds nothing else works. I have use the MSM tool and put my phone into EDL mode and it detected the phone with a black screen. Every time I use the tool it works till about 18% then it gives me a Sahara communication failed error and then my phone gets out of EDL mode.. I installed all the drivers needed on my PC and used multiple USB 2.0 slots but it still fails. Any help would be appreciated.
There are warnings in the TWRP thread for the N200 that it is broken and should not be flashed.
I have written an easy to follow guide here to downgrade to A11 with Fastboot Enhance.
Unfortunately, now that you have used MSMTool on the phone, it is now bootloader LOCKED. This tool should be the last resort only if you are already hard bricked. You could have gotten the phone into fastboot if either boot.img was still intact and re-flashed the rom with a still unlocked bootloader. The phone will change slots after so many failed boots.
Now that your boot loader is locked, the only tool that can modify the phone is MSMTool. If you can get into Recovery, do delete user data and try again.
Otherwise, you will need to get an RMA and send phone back to OP.
scanman0 said:
There are warnings in the TWRP thread for the N200 that it is broken and should not be flashed.
I have written an easy to follow guide here to downgrade to A11 with Fastboot Enhance.
Unfortunately, now that you have used MSMTool on the phone, it is now bootloader LOCKED. This tool should be the last resort only if you are already hard bricked. You could have gotten the phone into fastboot if either boot.img was still intact and re-flashed the rom with a still unlocked bootloader. The phone will change slots after so many failed boots.
Now that your boot loader is locked, the only tool that can modify the phone is MSMTool. If you can get into Recovery, do delete user data and try again.
Otherwise, you will need to get an RMA and send phone back to OP.
Click to expand...
Click to collapse
Sorry I should have written more details but I currently have a hard bricked device. It will not boot and It failed to boot like 20 times. It will not enter fastboot or even get past the logo when you first turn it on. I did use MSM tool after it wasn't letting me into fastboot. Thanks for the help and I will send it back.
z67gp said:
Sorry I should have written more details but I currently have a hard bricked device. It will not boot and It failed to boot like 20 times. It will not enter fastboot or even get past the logo when you first turn it on. I did use MSM tool after it wasn't letting me into fastboot. Thanks for the help and I will send it back.
Click to expand...
Click to collapse
Fix Sahara communication failed error in MSM Download Tool
In this tutorial, we will show you how to fix the Sahara communication failed and other related MSM Download Tool errors.
www.droidwin.com