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.
Hello, I own a Lenovo A6010, I recently tried to install a custom rom from a forum in this website, as i am newbie to all this, I think i screwed somewhere. Now my phone is stuck on boot screen. I cannot even start my phone in recovery mode or the menu that takes you to recovery mode.
Before flashing i had taken a backup of the dalvik cache and system and data and all those options available in the backup option in twrp which kept on my pc. Now i dont have any idea what do.
I even downloaded the stock rom of my phone from some website, but it was available in a rar file.
When I connect my phone with a cable while pressing the volume down button the same boot screen pops up and my computer starts to install device drivers. I think my phone can be brought back to normal, but i don't know how.
can someone please help me with some suggestions on what to do with my brick.
Thanks in Advance...
Warm regards
Do you have twrp installed? And by what method exactly did you try to install the custom rom?
Edit: Nevermind. Didn't realise this was a year old thread
Hi,
I couldn't figure out where to ask this query since I couldn't find anything regarding my phone. I own a Lava_R1s with StarOS V3.3 with Android Version 6.0. This is a phone available specifically in the U.A.E market since its made without camera and GPS so that it can be used in the oil field.
I tried to root the phone and now its soft bricked. I can enter fastboot mode and recovery mode (TWRP) but every time i try to switch on the phone it keeps going into a loop of the "Lava Powered by android" and switches off and then continues to keep doing that.
Here is what i did.
1. I used fastboot to unlock the OEM.
2. Then I flashed TWRP as recovery for the mobile.
3. After that i installed SuperSU zip file.
After all these steps my phone refuses to start up. It just comes to the LAVA powered by android screen and stays on that screen till i press the power button.
Further more I tried flashing the boot and system with Stock ROM files downloaded from needrom.com. That hasn't helped. In fact the looping of the initial screen started after flashing boot and system files (I used img files for Lava R1 Lite since those where the only ones i could find).
Would be really grateful if anyone could provide me a solution for this issue.
Another thing is that a lot of my colleagues have the same phone, so if there is anyway to extract the rom from their phone and install on mine without actually rooting their device it would also work for me i guess.
Renojjv
Renojjv said:
Hi,
I couldn't figure out where to ask this query since I couldn't find anything regarding my phone. I own a Lava_R1s with StarOS V3.3 with Android Version 6.0. This is a phone available specifically in the U.A.E market since its made without camera and GPS so that it can be used in the oil field.
I tried to root the phone and now its soft bricked. I can enter fastboot mode and recovery mode (TWRP) but every time i try to switch on the phone it keeps going into a loop of the "Lava Powered by android" and switches off and then continues to keep doing that.
Here is what i did.
1. I used fastboot to unlock the OEM.
2. Then I flashed TWRP as recovery for the mobile.
3. After that i installed SuperSU zip file.
After all these steps my phone refuses to start up. It just comes to the LAVA powered by android screen and stays on that screen till i press the power button.
Further more I tried flashing the boot and system with Stock ROM files downloaded from needrom.com. That hasn't helped. In fact the looping of the initial screen started after flashing boot and system files (I used img files for Lava R1 Lite since those where the only ones i could find).
Would be really grateful if anyone could provide me a solution for this issue.
Another thing is that a lot of my colleagues have the same phone, so if there is anyway to extract the rom from their phone and install on mine without actually rooting their device it would also work for me i guess.
Renojjv
Click to expand...
Click to collapse
Check my reply in this post
https://forum.xda-developers.com/android/help/softbricked-lava-r1s-please-help-t3730982
EDIT: Thankfully I could resolve this issue on my own fairly easily. My battery drained relatively quickly, and the issue didn't repeat when I tried booting again.
Hi XDA developers community,
Using some of the guides on this fantastic website I flashed LineageOS on my A2017G a few months ago. Now I tried reverting back to stock by flashing the B03 Oreo zip file in EDL mode (this guide).
The first reboot was already successful: I powered the phone on via the power button, then went through "can't be checked for corruption" screen, then got into the screen with Tux (Linux penguin), pressed volume up to go to recovery just to be sure, and rebooted from there into Android.
Although instead of starting the setup process Android dropped my right into the lock screen. I assumed that was because I hadn't factory reset yet and my data partition still had garbage data (that was step 18 of the guide btw). So, I powered off, from Android, and tried booting into recovery mode again to do the factory reset. However, now, after the Android corruption warning screen, the Linux Tux screen just stays there. Recovery mode doesn't appear, neither did it boot into Android. I can't even force power off by pressing the button (I pressed 80 seconds straight, no effect). No combination of volume and power buttons does anything, even pressing and holding it.
Right now I plan to let the battery drain on its own to get the device to power off. That's probably gonna take some days because the battery is completely charged. Is there some other possibility to make it go faster? Maybe heat the battery up from the outside with a hair dryer? I would rather not open the phone up and take the battery out, because I don't have a heat gun and I'm also worried I'm gonna leave scratch marks or something (the process seems quite rough).
And also, when the battery is drained, is there any recommendation on what I should do? Simply try again, going into recovery mode? Flash the EDL file again?
Thank you for reading all this, and I'd be so glad for any help.
I'm having this screen too, I'm trying to gsi, but none works, only lineage 16, but it gives error and closes the system at 16, and at lineage 15 the battery is being drained very quickly
Any rom stock I try to flash via edl gets in bootloop on the penguin screen, I can do the flash via edl from a los rom with 15.1 with oki twrp, some bugs, but would like to return to stock, can anyone help us?
same issue
Hello there
I have the same issue, can you please help ?
Thank you in advance
prasnel
kangalioo said:
EDIT: Thankfully I could resolve this issue on my own fairly easily. My battery drained relatively quickly, and the issue didn't repeat when I tried booting again.
Hi XDA developers community,
Using some of the guides on this fantastic website I flashed LineageOS on my A2017G a few months ago. Now I tried reverting back to stock by flashing the B03 Oreo zip file in EDL mode (this guide).
The first reboot was already successful: I powered the phone on via the power button, then went through "can't be checked for corruption" screen, then got into the screen with Tux (Linux penguin), pressed volume up to go to recovery just to be sure, and rebooted from there into Android.
Although instead of starting the setup process Android dropped my right into the lock screen. I assumed that was because I hadn't factory reset yet and my data partition still had garbage data (that was step 18 of the guide btw). So, I powered off, from Android, and tried booting into recovery mode again to do the factory reset. However, now, after the Android corruption warning screen, the Linux Tux screen just stays there. Recovery mode doesn't appear, neither did it boot into Android. I can't even force power off by pressing the button (I pressed 80 seconds straight, no effect). No combination of volume and power buttons does anything, even pressing and holding it.
Right now I plan to let the battery drain on its own to get the device to power off. That's probably gonna take some days because the battery is completely charged. Is there some other possibility to make it go faster? Maybe heat the battery up from the outside with a hair dryer? I would rather not open the phone up and take the battery out, because I don't have a heat gun and I'm also worried I'm gonna leave scratch marks or something (the process seems quite rough).
And also, when the battery is drained, is there any recommendation on what I should do? Simply try again, going into recovery mode? Flash the EDL file again?
Thank you for reading all this, and I'd be so glad for any help.
Click to expand...
Click to collapse
My phone is like u "zte axon 7 a2017g " version oreo b03 please tell me the guide that u used to install lineage os and the tools please !!!
i just want to install unloack my bootloader , flash twrp , install lineage os so on ; please give me just the guide that u use !
afef said:
My phone is like u "zte axon 7 a2017g " version oreo b03 please tell me the guide that u used to install lineage os and the tools please !!!
i just want to install unloack my bootloader , flash twrp , install lineage os so on ; please give me just the guide that u use !
Click to expand...
Click to collapse
Sorry, I don't remember
kangalioo said:
Sorry, I don't remember
Click to expand...
Click to collapse
u don't remember if the guide is for marshmallow or naugat a 2017 g or i can use guide for a2017 u !
afef said:
u don't remember if the guide is for marshmallow or naugat a 2017 g or i can use guide for a2017 u !
Click to expand...
Click to collapse
what
kangalioo said:
EDIT: Thankfully I could resolve this issue on my own fairly easily. My battery drained relatively quickly, and the issue didn't repeat when I tried booting again.
Click to expand...
Click to collapse
Mine didn’t reboot at all after completely draining the battery several times. Same result, blocked on penguin screen, no way to get into a menu to flash anything ?
kangalioo said:
what
Click to expand...
Click to collapse
My phone is "zte axon 7 a2017g" version oreo b03 , i want to find guide make me unloack bootloader , flash twrp , install lineage os ; i just want for if u can remember if what can proch me i can use because the only guides exist are for a2017u or a 2017 g marshmallow or naugat
or if u can tell me if i can downgrading from oreo to marshmallow without unloack bootloader to use the guide exist for marshmallow !
afef said:
My phone is "zte axon 7 a2017g" version oreo b03 , i want to find guide make me unloack bootloader , flash twrp , install lineage os ; i just want for if u can remember if what can proch me i can use because the only guides exist are for a2017u or a 2017 g marshmallow or naugat
or if u can tell me if i can downgrading from oreo to marshmallow without unloack bootloader to use the guide exist for marshmallow !
Click to expand...
Click to collapse
As I said, I don't remember. I'm using a different phone altogether since half a year.
So because only a Tux logo appeared on the screen, my guess as to what happened is that while the Android Bootloader, also called "aboot" was booting the Linux kernel that Android runs off of, before the kernel could display the splash screen that appears when you power on the device, it encountered a critical error that either aborted the boot process, or caused the kernel to go into a kernel panic. Now as to why it displayed the Tux logo, it probably did that because when it crashed, it tried mapping the framebuffer to the display instead of keeping in hidden by default to show you the kernel buffer logs for you to troubleshoot the problem but instead, it shows the iconic Linux penguin that is usually hidden when the kernel boots.
I have a Lenovo TB-X304L and I installed a custom ROM on it a few months ago. Everything was working perfectly except for some bugs and some specific apps crashing. So I thought of flashing the stock firmware to go back to the original ROM. I didn't take a backup when I installed the ROM. I used Lenovo's "Rescue and Smart assistant' to download and flash the right firmware for my tablet. I was able to flash it successfully and all but when I tried to boot it up. It was just stuck on the Lenovo screen for a minute or two and then turned off. I tried turning it on several times but every time it would turn off after staying on the 'Lenovo screen' for a minute or two. I even tried booting into the (stock) recovery and factory resetting it and also formatting the cache partition but nothing worked. I also noticed that the device's bootloader is locked and the TWRP recovery got removed. Now even if I want to flash a custom rom, I can't because to do so I need to turn on USB debugging and turn on OEM-unlock but I can't boot into the OS. I tried flashing in 2 times now but its always stuck on the boot screen. Please help me if there is anything I can do with this.
Thank you.
Device: Lenovo Tab 4 10 (TB-X304L)
Firmware Files u can goto this link and download the firmware. steps are given in the comments. I always download from here
So I have this Lenovo Tab 4 10 (TB-X304L) and what I did was that I installed a custom ROM from this. It worked fine until that where it started to randomly shut down and when I turned it back on it would just be stuck on the logo. Re-flashed the whole ROM 2 times but didn't work. So I tried to flash the stock firmware it came with and learned that I need different tools to do so. So instead I used Lenovo's Rescue and Smart Assistant (LMSA) to flash the stock firmware. I put all the correct stuff (like model number and all) and started flashing through the app. Successfully flashed but the tab didn't turn on. So I entered into Fastboot mode and realized that the bootloader was now locked and the TWRP I had was also removed. After entering into FastBoot mode, I entered into the stock recovery and did a factory reset. After a few power offs/ons it finally turned on but would shutdown after 7 secs into the setup. Even if I didn't touch anything it would turn off.(even tried safe mode but it would still turn off) So I used the tool to flash it one more time and this time it would just get stuck on the Lenovo Screen for a min and then turn off. I tried flashing the firmware once more but its the same. Also it doesn't turn off when its in Fastboot mode or in the Recovery.
Now my situation is
>Can't get into OS
>Bootloader is locked
>No TWRP
>Can boot into Fast boot and stock recovery
>Don't know wtf to do at this point
I would appreciate if someone could help me.
Electron.48 said:
Firmware Files u can goto this link and download the firmware. steps are given in the comments. I always download from here
Click to expand...
Click to collapse
I'm trying to do this and I keep getting the following error when I try to download it
Sorry, you can't view or download this file at this time.
Too many users have viewed or downloaded this file recently. Please try accessing the file again later. If the file you are trying to access is particularly large or is shared with many people, it may take up to 24 hours to be able to view or download the file. If you still can't access a file after 24 hours, contact your domain administrator.
Click to expand...
Click to collapse