Hello Fellows,
First I'd like to explain my situation in details.
my phone fell while i was walking on the street and it got some dirt on it, so ( foolishly ) I decided to clean it.... and yeah... i washed my phone like washing a dish... i like rinsed the phone in water and in other cleaning liquids for no more than 3 seconds it was all quick thingy... anyway after washing it.... i directly powered it ON and it powered but the screen was OFF ( so i decided to power it OFF, solder it and to remove any clues of water inside on the board or something... after that i used a hairdryer ( which is not recommended ) but i used it at a descent distance so that no harm would be caused to the board... as i was only subjecting air to let water if any existed to dry..
i put the phone in rise and kept it for 1 day... after 1 day i wanted to check out how stuff went.. so i powered it ON and the screen actually turned ON and the vibrator, even the hardware back-light lighted up perfectly but here's the problem I'm facing.
the phone only boots into TWRP 3.1.0.0 no matter what i do.. things i tried:
1- flashed some ROM, through TWRP
2- used "Fixed Contexts" in TWRP
3- Repair File System "System partition" through TWRP
4- used file manager inside TWRP and checked if the internal storage is working and indeed i can show all my files, through TWRP
5- also used the file manager to access "System" Partition and everything was there, through TWRP
6- change File System into EXT4 "System partition" through TWRP
7- Resize File System "System partition" through TWRP
8- Wiping all Partitions "Excluding the internal storage"
and NON WORKED..
note that whenever i attempt to flash a ROM the result shows successful with no errors ..
so whats the problem in here?
i have a guess but i need help in order to apply it.. i think the VOL- is pressed and stuck somehow Electrically on the board ( but no physically as i can press the volume down and hear its tap or whatever you call it.. i even managed to boot into fast-boot and it worked.
is there anyway i can disable the vol- button temporary to see if its causing the problem?
the only thing is i cant see my ROM booting... not even the boot animation showing... just the boot-loader and automatically it goes into the recovery
also i have kernel log attached below followed by the recovery log
EDIT: i also forgot to mention that my PC recognize the phone and i have access to my internal storage.. no problems with transfer speed as well
after tons of attempts and searching online and flashing stuff and blablabla... (i flashed every recovery image op2 support )
FINALLY
I found the solution my self, and everything is back to normal...
the phone was stuck at the early stage of the booting process and maybe couldn't find the boot image in order to boot up the android OS, so all i did was i plugged in the phone into the PC, i started everything in fastboot mode on phone and on PC then i just sent the following command to my phone.
Code:
fastboot continue
fastboot then(meaning after the command) wasnt able to recognize the phone anymore so i knew that its now trying to search for partitions other than recovery.. i waited like 10 seconds and booom it booted into the best ROM i've ever used ( and actually missed ) which is Official RR from our great maintainer "nicesoni_ash"
P.S: the vol- as i said was really stuck and i noticed it not working while on RR ROM, so i just clicked it many times and tried mixing vol+ with vol- .. after many many attempts vol- worked and i then rebooted to make sure if everything is back to normal and no recovery auto boots and indeed it smoothly booted up :laugh:
thanks a lot for all who tried to help out in here or on oneplus forums :highfive:
#back_to_resurrect_and_will_always_remix
Did you try reverting to stock ?
Try getting files from here..
https://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863
I would consider it as bricked, after all attempts failed and go with the unbrick guide here on xda or oneplus forums, maybe this way it can be ressurected.
You probably have already backed up your data..
Damn, that hurts..
mithu.creative said:
Did you try reverting to stock ?
Try getting files from here..
https://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863
Click to expand...
Click to collapse
sorry for this late reply but yes i have tried flashing every ROM from stock to Custom ones even i flashed EVERY SINGLE RECOVERY IMAGE OUR PHONE SUPPORTS XD and non worked... first aid.. qualcomm toolkit... non...
hello bro, i updated a magisk module v4android and when i reboot, it boots up in twrp. and since then it keeps booting into twrp. So, i used fastboot continue and when it boot int the home i deleted that module.
but fastboot continue only works once. After that if i switch-off and switch-on the phone, it goes into twrp. it needs fastboot continue everytime.
please provide me a permanent solution. few other users are facing this too. plz reply i'm waiting.
Hey,
with the help of some others in a Discord server (thanks @thesanjayp#6251 on discord) i managed to find the issue. Appearantly there was a change in /dev/block/bootdevice/by-name/misc for some reason. There was a similar problem on the old LG Optimus G Pro which i owned, so i remembered this.
As I'm not sure if we can just wipe the partition or not, i got a working misc.img attached.
In any terminal (adb shell, twrp terminal or an terminal app in a rom) make sure you have su rights, and then execute the following command:
Code:
dd if=/path/to/misc.img of=/dev/block/bootdevice/by-name/misc
Make sure to adapt the path to the misc.img though to the location you saved it to.
The misc.img I used is attached to this post.
PS: Im not responsible for any broken phones if this didnt work for you.
Related
Hey guys,
Last night, I unlocked, rooted (with perm cust recovery - TWRP) my N7 which was successful.
I installed custom ROMS and it was really doing great, until I made a mistake.
In TWRP, I accidentally formatted SYSTEM without having a ROM zip file to flash in the internal storage (/sdcard).
I restarted and it was just sitting in the google splashscreen (with unlock icon) - no matter how to I try to reboot it it was just going stuck there. I manged to make it boot to TWRP (press volume keys + power) again and tried to PUSH a rom using adb command line.
When I pushed a ROM file (Cookie's and Cream 1.0) as soon as I pressed enter, it looks like it is doing the push. But I've been waiting for 45 mins and it was still on the same progress, so I had to unplug it while it was doing that in the command line.
When I restarted, I tried to go to TWRP again but I can't anymore no matter what I do. So I had no choice but to reboot to bootloader instead.
This time I used the tools (nexus toolkit 1.5.3 (GUI) and the other version (2.0) in XDA - command line looking).
On both instances on both tools, when it is pushing - it just gets stuck with a blinkng cursor and it does not continue to the next step. As if the file is not being pushed.
There was also a point that when I go to recovery (i think it was stock), the android picture had a red triangle with exclamation point.
Anyway, I managed to make it work by manually by doing the guide [GUIDE] Flashing a Factory Image with fastboot / return to stock
Again, when i was doing it, when it is sending the image file to the N7 it was just stuck with a flashing cursor. I waited for 30 mins and when I rebooted, it WORKED - booted to N7 screen etc .. all good.
But I was worried why about that pushing error - maybe my Nand flash got borked like bad sectors etc? Is there a way for me to check if my flash storage is still good?
TL;DR
I messed up flashing a custom ROM on my N7 and accidentally formatted system. I managed to recover using recover to stock using fastboot and it worked.
Now, when I'm pushing files and it is big, it just gets stuck, either in recovery or when it is booted up.
Is there a way for me to check if I made badsectors or borked my internal flash storage?
So far everything looks fine but I just want to make sure since I still have 20 days to return it.
Thanks!
EDIT: When pushing from Recovery it says "error: protocol fault (no status)"
keplenk said:
Hey guys,
Last night, I unlocked, rooted (with perm cust recovery - TWRP) my N7 which was successful.
I installed custom ROMS and it was really doing great, until I made a mistake.
In TWRP, I accidentally formatted SYSTEM without having a ROM zip file to flash in the internal storage (/sdcard).
I restarted and it was just sitting in the google splashscreen (with unlock icon) - no matter how to I try to reboot it it was just going stuck there. I manged to make it boot to TWRP (press volume keys + power) again and tried to PUSH a rom using adb command line.
When I pushed a ROM file (Cookie's and Cream 1.0) as soon as I pressed enter, it looks like it is doing the push. But I've been waiting for 45 mins and it was still on the same progress, so I had to unplug it while it was doing that in the command line.
When I restarted, I tried to go to TWRP again but I can't anymore no matter what I do. So I had no choice but to reboot to bootloader instead.
This time I used the tools (nexus toolkit 1.5.3 (GUI) and the other version (2.0) in XDA - command line looking).
On both instances on both tools, when it is pushing - it just gets stuck with a blinkng cursor and it does not continue to the next step. As if the file is not being pushed.
There was also a point that when I go to recovery (i think it was stock), the android picture had a red triangle with exclamation point.
Anyway, I managed to make it work by manually by doing the guide [GUIDE] Flashing a Factory Image with fastboot / return to stock
Again, when i was doing it, when it is sending the image file to the N7 it was just stuck with a flashing cursor. I waited for 30 mins and when I rebooted, it WORKED - booted to N7 screen etc .. all good.
But I was worried why about that pushing error - maybe my Nand flash got borked like bad sectors etc? Is there a way for me to check if my flash storage is still good?
TL;DR
I messed up flashing a custom ROM on my N7 and accidentally formatted system. I managed to recover using recover to stock using fastboot and it worked.
Now, when I'm pushing files and it is big, it just gets stuck, either in recovery or when it is booted up.
Is there a way for me to check if I made badsectors or borked my internal flash storage?
So far everything looks fine but I just want to make sure since I still have 20 days to return it.
Thanks!
EDIT: When pushing from Recovery it says "error: protocol fault (no status)"
Click to expand...
Click to collapse
My computer did that in windows, but switching to Linux and it all worked fine for me
Sent from my Nexus 7 using xda premium
lbbooga said:
My computer did that in windows, but switching to Linux and it all worked fine for me
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks. Good thing I still have my Arch Linux box still up and running.
So is this a known issue?
Right now, I did it again and it worked.
It is like 80% chance it will get stuck while pushing thru adb and 20% it will just work successfully.
Just right now, I just did restore it using the tools. I didn't work for at least 5 times. The 6th time it worked. (Windows 64 bit)
I'm going to try linux and see if it will be better.
UPDATE:
It looks like it could be adb drivers in Windows.
OS X works fine. I haven't tried with Linux.
But is there a software to check if Flash storage has bad blocks?
Thanks!
I followed this guide in order to root my brand new p8lite.
The thing is that now I have a black screen. If I plug my phone via usb, adb shows me that the device is in recovery.
By adb shows me that the device is in recovery I mean this:
Code:
# adb devices
List of devices attached
W3D7N16712000718 recovery
What I did:
Checked the model. It's an ALE-L21
Chapter 1: not a windows user, but managed to get adb up and running on my linux machine.
Chapter 2: everything went fine, bootloader unlocked
Chapter 3: my phone booted up just fine
Chapter 4: skipped it, as my phone was booting fine into system
Chapter 5:
So you want to convert to a single/dual sim?
Click to expand...
Click to collapse
My answer: "no thanks", so I skipped it
Chapter 6: I did the upgrade through OTA BEFORE reading the guide. Double checked I was running 6.0, so I skipped it
Chapter 7: Downloaded the file, flashed trought fastboot. And now I'm here.
I think I may have ****ed up things in the last 3 chapters.
What I tried to fix this:
Code:
# adb reboot bootloader
phone rebooted then huawei logo then blackscreen. adb still shows it's in recovery
After searching in the forum, I came by
Code:
adb reboot-bootloader
(notice the hypen). Firing that command put my phone into fastboot. Couldn't believe it, but I took the chance to flash the files found in chapter 4 (bootloader, recovery, cust and system, in this order). No luck, still reboot, logo, black screen
Now, no matter the presence of the hypen in the command, my phone keeps going into recovery (after the usual reboot, logo, black screen)
Tried to hold down POWER to shut it down. After a while it reboots, logo and black screen again. Laptop keeps saying device is into recovery
Tried to download the official 6.0 update, put on a sd card (dload/UPDATE.APP), held down POWER+VOLUP+VOLDOWN. Again, reboot, logo, black screen. recovery mode, again.
Frustrated, I unplugged the phone. After a while, it rebooted, logo and blackscreen without me touching it. Weird. It did it again a couple of times, but now it has stopped (with a black screen and, if plugged in, adb. says is into recovery)
I really don't know what to do, please help me.
UPDATE:
After leaving a night on its own, the phone was noticeably hot.
Also, when unplugged, if I hold POWER it shows me the logo a couple of time before going black screen.
Ok. But can you enter in recovery?
Another question: you said that u flashed the necessary files. What about flashing directly twrp as recovery, and from twrp make all wipes, and afther that flash from twrp some zip-ped firmwares?
tamaskurti said:
Ok. But can you enter in recovery?
Click to expand...
Click to collapse
Apparently yes (or at least, adb says I'm into recovery). However, I just get a black screen.
Tapping randomly on the screen doesn't give any kind of feedback (no vibration, no beeps, nothing).
tamaskurti said:
Another question: you said that u flashed the necessary files. What about flashing directly twrp as recovery, and from twrp make all wipes, and afther that flash from twrp some zip-ped firmwares?
Click to expand...
Click to collapse
Since I started having those problems after I flashed TWRP, I thought it was a better idea to flash stock recovery (alongside bootloader, cust and system) and restart from there.
I have the same issue...
Have you solved the issue? In case you solved, how?
mmennella said:
I have the same issue...
Have you solved the issue? In case you solved, how?
Click to expand...
Click to collapse
Not yet. I brought the phone to a local repair shop. Tomorrow they should bring it back, hope they have good news
Mmmmmm... I go to buy new One. Huawei must have a way to reflash, but i can't wait. Thanks a lot
Inviato dal mio Redmi 3 utilizzando Tapatalk
S1cK94 said:
Not yet. I brought the phone to a local repair shop. Tomorrow they should bring it back, hope they have good news
Click to expand...
Click to collapse
i brought it to my local repairshop and they sent my phone to manufacters central repair and they fixed it for free.
AfrikanDionysus Solution
Huawei P8 lites are region specific like Middle east asia america etc so before you go in make sure you know your build number in my case ALE-L21C185B560 its the UAE variant now if you've messed go to the huawei website download the rom specific to your region any other region won't work!!! get a clean sd card extract the file and copy it to the root of the sd card its normally an update.app inside a folder named dload shutdown the phone now press vol+ and vol - and the power button till it starts installing.. If you've messed up your recovery and can get to fastboot by plugging in the phone then pressing vol down and power.. use the Huawei extractor tool and extract the recovery from the just downloaded rom and flash it.. then retry the restore as stated.. im sure you can google all the tools you need to get so im not putting any links !!! Ahsante !:good::good::good:
Yesterday I accidentally installed the OTA update. I got stuck in TWRP and flashed a new ROM. Phone booted up fine, but now I have no cellular signal, nothing that uses video or sound works. Camera doesn't work, flashlight doesn't work.
I tried several different ROMS and nothing changes. Even the system sounds, ringtones and so on do not work. Anyone have any idea what I can do? Thanks
boot into fastboot
fastboot erase system
fastboot erase cache
fastboot erase userdata
fastboot erase misc
fastboot erase fota
fastboot erase boot
then pull battery and reboot into twrp by holding power and vol down, when lg logo appears then click the power button and re-hold it down to get into twrp.
once in twrp, check and see if system is mounted, if it wont let you mount, go to wipe and wipe everything (not ur sd of course)
System, cache, dalvik, data, internal, everything... the fastboot should have already done this but let twrp do it too..
once done, use the format option and format data also, some of these may error thats okay, just keep going..
once done reflash the full rom that matches your device.. let it flash and reboot and do its thing. this should fix the issues...
once it boots you may need to let it activate, or re-activate.
Only other suggestion would be if you have a twrp backup and you backed up your efs, its time to restore it also and see if the NV files have been damaged.
I've tried installing several different roms available on xda but that didn't resolve the issue. My phone remains in a boot loop state. Is there a way I can return to stock without compromising my ability to use the current root exploits?
Might help to know what you've got currently, are you able to get to recovery at all, etc?
I could get into TWRP with no problem, I could flash any rom, but all would give me the same issues, no sounds, no flashlight, no cell signal. I think the OTA update messed something up. I ended up putting the phone back to stock, locking the bootloader and exchanging the phone for a new one. I got my new one today, it's on 10d, just tried to root it the same way as the last time and it keeps failing. I get the same problem as the guy on this thread https://forum.xda-developers.com/v20/development/helpt-easyrecowvery-t3543873
My Solution
[MY FIX]
this post contains my working solution to the problem.
my problem is...
I accidentally clicked on 'install OTA update' on a rooted lg v20 t-mobile. A second after clicking it I realized that was the wrong button to press. AND so the start of the endless TWRP boot loop that allowed me to access TWRP to perform multiple tasks but couldn't boot back into my system UI where I can make phone calls.
I had this problem and spent days trying to figure how to get it back.
my solution is...
I tried everything to delete the *fota* and *misc* folders with fastboot; however none of the methods worked, until I tried the methods suggested in step#1 in "Stuck in a endless boot loop to twrp " in https://forum.xda-developers.com/v20/development/rom-ls997-stock-debloated-su-goodies-t3531923.
So after deleting *fota* and *misc*, I had to exit the bootloop by 'reset all data option' by pressing YES twice. You read that right, you will have to agree to reset all user data by clicking YES twice. THO the effect will NOT reset all your data; it will just kick you out of TWRP recovery mode. I was pleasantly surprised to still have my data.
https://www.youtube.com/watch?v=tDq0qMbgjL4 That video shows as proof that it doesn't break things and also how to get into TWRP. You can also use the same methods to get out of TWRP.
Here's the text version:
1. hold volume down and power.
2. when lg logo shows up click power and re hold it while still holding vol down.
3. if you do it right in about 4 seconds or so it will boot to a menu, choose yes both times and you'll be back in (or out of) twrp. (yes you read that right!, don't worry you wont lose your data)
Hope this works for you as it did for me. I'm only posting because I didn't find a comprehensive solution post.
lanyueng said:
[MY FIX]
this post contains my working solution to the problem.
my problem is...
I accidentally clicked on 'install OTA update' on a rooted lg v20 t-mobile. A second after clicking it I realized that was the wrong button to press. AND so the start of the endless TWRP boot loop that allowed me to access TWRP to perform multiple tasks but couldn't boot back into my system UI where I can make phone calls.
I had this problem and spent days trying to figure how to get it back.
my solution is...
I tried everything to delete the *fota* and *misc* folders with fastboot; however none of the methods worked, until I tried the methods suggested in step#1 in "Stuck in a endless boot loop to twrp " in https://forum.xda-developers.com/v20/development/rom-ls997-stock-debloated-su-goodies-t3531923.
So after deleting *fota* and *misc*, I had to exit the bootloop by 'reset all data option' by pressing YES twice. You read that right, you will have to agree to reset all user data by clicking YES twice. THO the effect will NOT reset all your data; it will just kick you out of TWRP recovery mode. I was pleasantly surprised to still have my data.
https://www.youtube.com/watch?v=tDq0qMbgjL4 That video shows as proof that it doesn't break things and also how to get into TWRP. You can also use the same methods to get out of TWRP.
Here's the text version:
1. hold volume down and power.
2. when lg logo shows up click power and re hold it while still holding vol down.
3. if you do it right in about 4 seconds or so it will boot to a menu, choose yes both times and you'll be back in (or out of) twrp. (yes you read that right!, don't worry you wont lose your data)
Hope this works for you as it did for me. I'm only posting because I didn't find a comprehensive solution post.
Click to expand...
Click to collapse
This fixed my issue. Thank you so much!
For further clarification, I had to delete all these folders that existed (I didn't have them all) using TWRP file manager. Make sure system is mounted. :
/fota
/misc
/data/fota
/cache/fota
/data/misc
/etc/fota
/system/etc/fota
Powered off after that, and then I manually booted into TWRP using the buttons method and hit reboot system and all was fixed.
jluca98 said:
This fixed my issue. Thank you so much!
For further clarification, I had to delete all these folders that existed (I didn't have them all) using TWRP file manager. Make sure system is mounted. :
/fota
/misc
/data/fota
/cache/fota
/data/misc
/etc/fota
/system/etc/fota
Powered off after that, and then I manually booted into TWRP using the buttons method and hit reboot system and all was fixed.
Click to expand...
Click to collapse
This isn't working for me. Keeps rebooting to TWRP.
I get FAILED (remote: unknown command) with every adb command
Any ideas?
Drkphnxs2k said:
I could get into TWRP with no problem, I could flash any rom, but all would give me the same issues, no sounds, no flashlight, no cell signal. I think the OTA update messed something up. I ended up putting the phone back to stock, locking the bootloader and exchanging the phone for a new one. I got my new one today, it's on 10d, just tried to root it the same way as the last time and it keeps failing. I get the same problem as the guy on this thread https://forum.xda-developers.com/v20/development/helpt-easyrecowvery-t3543873
Click to expand...
Click to collapse
Don't use Easy Recowvery. Do it manually from the original thread. You can also google it for some sites that have cleaned the instructions up for easier reading.
I just did a H918 10d like this.
I had to reboot my device due to problems with my speaker. Now i'm not able to boot anymore.
I'm only able to get into ODIN Mode, and flashing new FW or TWRP does nothing. It'll flash correctly, but as soon as it sends the reboot command the device powers off and does not boot, and no, it does not reach the "Galaxy s8, powered by android screen".
It does not want to power on, and only responds to the odin button combo, can't boot into recovery either since nothing works.
I was running the latest version of Renovate Ice if that matters.
I've searched trough some other threads, but it seems like i'm the only one that's having this problem.
Any help or thoughts would be greatly appreciated!
Edit 1: I've tried flashing both AQK7 and AQG5. Both flash fine, but as soon as odin sends the reboot command to my phone, it turns off and does not turn on.
Auto Reboot is ticked. Same goes for any version of TWRP, it will flash, but when it has to reboot the device turns off and does not turn on. There's nothing on the screen, its completely black and the only thing that does work is Download Mode. I've also tried ereasing nand, and repartitioning storage. Both seem to have 0 effect. As stated in one of my replies, i was running the latest build of renovate-ice with magisk, no other mods, or themes installed.
Im a bit confused - you can only boot into download mode (not into twrp?) and the phone is in bootloop? Have you flashed anything (mod?) before or activated a substratum theme which could cause this?
The only thing I can think of is a) you delete in twrp file manager the corrupted file, if there is something like this or b) a twrp restore from a backup. Boot into download mode and then do not press vol up to go into odin mode but press vol down to reboot - then immediately press the combo for twrp and you will get to the recovery. This helped my s8 many times when I was in a bootloop and couldnt boot up twrp
FloM94 said:
Im a bit confused - you can only boot into download mode (not into twrp?) and the phone is in bootloop? Have you flashed anything (mod?) before or activated a substratum theme which could cause this?
The only thing I can think of is a) you delete in twrp file manager the corrupted file, if there is something like this or b) a twrp restore from a backup. Boot into download mode and then do not press vol up to go into odin mode but press vol down to reboot - then immediately press the combo for twrp and you will get to the recovery. This helped my s8 many times when I was in a bootloop and couldnt boot up twrp
Click to expand...
Click to collapse
Thanks for the reply! Other than using the Renovate-Ice rom, and running magisk the thing was pretty much stock. wasn't messing around in twrp either. Its not stuck in a bootloop either, it just refuses to do anything other than go in and out of DL mode. The phone does not respond to any button imputs other than DL mode. As stated in the OP it does not boot at all, just a black screen. i've already tried to reflash a stock FW and TWRP, but that does not seem to work...
try the method I did - this is the last thing I could think of, before reflash the whole phone with odin
More info about your speaker problem
popmpopm said:
More info about your speaker problem
Click to expand...
Click to collapse
There isn't much to say about the problem ,it just stopped working, hence why i rebooted the phone, and ran in to the problem i'm having right now.
FloM94 said:
try the method I did - this is the last thing I could think of, before reflash the whole phone with odin
Click to expand...
Click to collapse
Doesn't work sadly, but thanks for the help anyways!
but you havent installed Viper4Arise or anything like that?
Because of this my speaker also stopped working a few weeks ago
if you can get into download mode then get into download mode and leave phone, then download samsung smart switch for your pc (older version like 4.1.17022_20 from here http://www.filehorse.com/download-samsung-smart-switch/29268/ that allows phone based recovery), once installed open it, then click on more at top right, (do not update the software if you get a prompt) select emergency device recovery...., then click on right tab (device initialisation) and fill in your phone details etc., connect your phone (in download mode) and follow the process, maybe it works, you'll need to root and install TWRP again but thats no big issue.
Jostian said:
if you can get into download mode then get into download mode and leave phone, then download samsung smart switch for your pc (older version like 4.1.17022_20 from here http://www.filehorse.com/download-samsung-smart-switch/29268/ that allows phone based recovery), once installed open it, then click on more at top right, (do not update the software if you get a prompt) select emergency device recovery...., then click on right tab (device initialisation) and fill in your phone details etc., connect your phone (in download mode) and follow the process, maybe it works, you'll need to root and install TWRP again but thats no big issue.
Click to expand...
Click to collapse
I've tried this just now, and it still gives me the same result, it goes trough the process, but as soon as it has to reboot it doesn't boot anymore.
Thanks for the suggestion though!
FloM94 said:
but you havent installed Viper4Arise or anything like that?
Because of this my speaker also stopped working a few weeks ago
Click to expand...
Click to collapse
i think phone is damaged by water or dropped s8 so fragile phone ! its happen to me with s5 the phone dead after speaker problem !!
popmpopm said:
i think phone is damaged by water or dropped s8 so fragile phone ! its happen to me with s5 the phone dead after speaker problem !!
Click to expand...
Click to collapse
I've had a case on the phone since day one, and I've checked for water damage, but there is non. The tab that is supposed to indicate it is untouched. But thanks for your input! I appreciate it
I have the same problem. Its look like is bootloader issue. try flash this soft :
G950FOWA1AQCC_Recovery
But if you are on newest rom it wont work.
Hello, you can solve this problem?
Hello everyone, just wanted to say a quick thanks, after successfully rooting and installing custom roms on two phones thanks to the information on these forums, third time turns out to be a charm and I managed to hard brick my new P10 lite.
The situation right now:
no charge light, no combination of buttons will do anything, phone is dead and will not boot or vibrate.
my computer will recognize that a phone is connected, for example Hisuite will pop up when i connect the phone, and in device manager, it shows Lemobile android device and the submenu says Android bootloader interface.
how i got here:
i was trying to install lineage 14.1 from this haky86
https://forum.xda-developers.com/p8...m-lineageos-14-1-huawei-p8-lite-2017-t3649292
but before i did that, i used this guide to install twrp and supersu:
https://forum.xda-developers.com/p10/how-to/twrp-how-to-root-p10-lite-t3617418
everything went fine, on the stock operating system i had root and system was running.
when i installed lineage, i lost root and couldnt figure out how to get it back. so i used this guide to restore the stock system and was going to try again from the beginning.
https://forum.xda-developers.com/p10-lite/help/original-service-rom-huawei-p10-lite-t3688097
however, when i tried to reinstall lineage for the second, third and fourth time, i kept getting stuck in a bootloop with the lineage animation. it seemed to me that i needed to flash the vendor image, and i found a guide on xda how to do it, but it wouldnt let me flash to the vendor partition. (sorry, i dont recall the exact error and i cant get there anymore :/)
so in massive frustration and desperation, i tried to use this method:
https://forum.xda-developers.com/p8...uide-unbrick-huawei-p8-lite-2017-pra-t3713574
which i know is for a p8 and i never should have tried to install it, but it went through the whole download process and at about 50-60% on the recovery the phone went black and never turned on again.
i have read that perhaps disconnecting the battery for a few minutes might help? or is this something that dc unlocker can help with?
any advice would be greatly appreciated. if more information is needed, please let me know.
Hi,
Have you tried completely turning off your phone (pressing on/off button for roughly 20 seconds) and then booting into recovery (pressing Volume Up and Power key simultaneously for rouhgly 10 seconds)?
Best,
Kenny
Thanks for the reply, but as I said, no button combinations elicit any response. The only sign that the phone is not completely dead is that it will be recognized by my computer as an android phone, but adb (for example) says no device is connected.
lineage gives you bootloop due to wrong data partition format
bricked my p10 lite several times same ending
only way that always gets the phone back to life is flashing lineage, i took haazan's one
BUT BEFORE flashing the lineage 14.1 zip check partition format is ext4
when back on lineage and stock ROM is wanted boot into twrp and re change format to f2ts or how it is named and flash the stock zip
unbricked
edit:
saw your second post too late
if the phone does not response on any button(s) maybe adb sideload command for change partition format and then sideloading the lineage zip is a way?
I have a similar problem, I have a custom rom (Elemental) but I flash another custom rom, it was normal, in the reboot it not turn on, only is in fastboot mode, i flash original system, cust, boot, and another but it is the same, help me please