I rooted the phone via KingOroot, tried to switch to supersu failed, and then I made changes in the hosts file.
I tried rebooting the device and it got stuck on the Vibe On Screen, I then booted to recovery and wiped cache and tried to reboot the phone now is stuck on the Lenovo Screen, I tried wiping data but it is still stuck on the Lenovo Screen.
Please Help.
The USB debugging option was not enabled so no adb.
shubhamjain3120 said:
I rooted the phone via KingOroot, tried to switch to supersu failed, and then I made changes in the hosts file.
I tried rebooting the device and it got stuck on the Vibe On Screen, I then booted to recovery and wiped cache and tried to reboot the phone now is stuck on the Lenovo Screen, I tried wiping data but it is still stuck on the Lenovo Screen.
Please Help.
The USB debugging option was not enabled so no adb.
Click to expand...
Click to collapse
You'll have to flash your stock firmware but you'll have to find a way to enable USB debugging first.
Always remember, when modifying a device, it is best to turn on USB debugging and LEAVE it on at all times BEFORE modifying the device, then if it goes wrong you can fix it.
If you don't turn it on first and you run into a problem like you did this time, there's a good chance you won't be able to fix it at all.
Always search for the things that can go wrong with what you're doing before you do it, don't just search for what you CAN do, also search for what you CAN'T do or shouldn't do.
In other words, make sure you have your ducks in a row and understand the details of EXACTLY what you're doing BEFORE you do it.
Sent from my SM-S903VL using Tapatalk
Related
Hello Guys! . I've got an issue on my hands, and I'm not really sure how can I solve it. I installed a new ROM, through TWRP recovery. After flashing, I tried to access the recovery, but the the phone started to bootloop, and sometimes it showed a greenish welcome screen. After a few bootloops, the phone started normally, entering the system. So, no recovery on it. Right now, after I tried to access the recovery a few times, the phone is blocked on bootloop . No access to files, no access to system, and no access to recovery also. Can you please advise what can I do furthermore?
Also, very important to mention is that the computer doesn;t seem to see the phone, I tried to another PC, the same thing. It says (in both computer cases) " USB device not recognised".
Is there any way to force somehow fastboot mode on the phone? ...
I really need some helping ideas, since I'm out....
Thank you!
Hi Guys,
Today I think I bricked my phone and I would appreciate any help.
I will describe the whole situation.
So around 2019 May, I rooted my device and decided to flash a stock based,debloated custom rom. Everything work just fined including downloading mode and recovery menu. Today, I decided to try out [S7/S7 Edge][OneUI Pie][JetBlackUI] LightROM, however strangely I was not able to boot either to TWRP neither to downloading mode via key combination.
However I had install TWRP app and from there i was able to boot to recovery mode,install the new rom and try it out.
For some reason root was not enabled in the new rom, so i figured I will try to do it via TWRP however I was unable to boot, since root access is needed to boot from TWRP app + key combo still did not work.
After searching on google, I found a poprgram which can do the trick. (Recovey-Download (CMD)
With this I was able to boot to recovery mode. Now I thought, since all this mess up was started with the new roms, I decided to restore my original stock rom, which I had a back up of. It booted up first and seemed okay, but I was curious if this solved the issues with the key comb, so I tried it going downloading mode, but it only worked with the program ((Recovey-Download (CMD)), and I saw that it is probably not gonna be good, since it only had the blue screen, but no data in the upper left corner.
Then I restarted the device and now it say " Custom binary blocked by FRP lock". and turns off itself.
I saw that FRP lock could be solved easly with Odin fresh install, problem is I have no idea how to go downloading mode. ( Assuming at this point I still can).
Sorry for the long essay but i think the more detail the easier to diagnose. Also, thank you for reading.
I would greatly appreciate any help.
BR
Csaba
Managed to solve it with USB JIG.
Is your phone an Exynos/Snapdragon variant?
csesztes said:
Managed to solve it with USB JIG.
Click to expand...
Click to collapse
Hey, how did you manage to get your phone into dl mode with an USB jig? I want to try this out, but you're the only one here who's confirmed that you were able to do this on an S7 Edge.
The phone went into bootloop randomly, it loops at the cyanogen intro and sometimes after the android is optimizing message. I can go into recovery(cyanogen), it has no option to connect to a pc or anything similar. It shows option to enter bootloader, install update from storage etc. I want to recover the images, videos from the device and don't care if i'm unable to use the device after recovering it. Couldn't install twrp as the device doesn't show up in fastboot devices, i'm guessing this is due to usb debugging and such other options not turned on. But i can't do these now as the device is stuck in a bootloop. Is it possible to recover the data or all i can do is flash rom using qfil and lose my data??
kakarotsaiyan said:
The phone went into bootloop randomly, it loops at the cyanogen intro and sometimes after the android is optimizing message. I can go into recovery(cyanogen), it has no option to connect to a pc or anything similar. It shows option to enter bootloader, install update from storage etc. I want to recover the images, videos from the device and don't care if i'm unable to use the device after recovering it. Couldn't install twrp as the device doesn't show up in fastboot devices, i'm guessing this is due to usb debugging and such other options not turned on. But i can't do these now as the device is stuck in a bootloop. Is it possible to recover the data or all i can do is flash rom using qfil and lose my data??
Click to expand...
Click to collapse
Hello, seems your bootloader isn't unlocked and you have the stock recovery, no custom recovery like twrp. So your device cannot be recognized by adb when you have it not enabled.
Try to shut it off by pressing the power button for some time and try to charge it full, then switch on. Also clearing cache in stock recovery can help.
Good evening! I hope you can help me.
I flashed LineageOS 14.1, but I wanted to go back to EMUI. I made all the wipes and tried to flash different stock firmwares through a forced update (volume buttons + power button), but it never worked. At that point, I read about a guy in this forum who suggested to create a flashable zip with Huawei Update Extractor: I followed the suggestion and tried to flash it with TWRP. No error was given, but when I tried to restart, TWRP told me I had no OS installed. I thought it was strange, so I tried to restart anyway. That's when I got in rescue mode. I can't get into the recovery and I can't use fastboot. What rescue mode shows me is:
RESCUE MODE
Attention!
Please update system again
Update User Guide:
*link*
*android avatar*
Error!
Func NO: 10 (boot image)
Error NO: 2 (load failed!)
Pressing the three buttons, I'm able to force an update. The problem is I can't find a firmware that doesn't get rejected. With Lollipop firmwares, it starts to install, but it fails at 12%. With Marshmallow ones, the installation process doesn't even start.
What can I do to make it work again? I'm very sad because this phone was gifted to me a couple of days ago and I already messed it up. I don't even know how to turn it off.
What can I do to get in fastboot mode? At that point, what should I do to flash the stock firmware? Or maybe do I need to find the first stock firmware ever installed into this phone to make the forced update work?
Please, I need help. Thank you in advance!
P.S. The phone's model is ALE-L21. I live in Italy, so I assume it's a European version.
Did you managed to fix this?
Jhon_Locke said:
Did you managed to fix this?
Click to expand...
Click to collapse
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
ErikChimello said:
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
Click to expand...
Click to collapse
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Jhon_Locke said:
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Click to expand...
Click to collapse
No, it doesn't show anything if I write that command...
I guess mine won't ever boot into the rom because it seems like there's no system installed. I made some researches and found out there are some softwares that let you reflash the partitions IF the phone is recognized as "HUAWEI USB COM 1.0". I'm still trying to figure out how to do it correctly though. I feel like if I do something wrong, then my phone won't probably turn on again.
In your case, you should be able to flash a custom rom without any issue. You just have to be very careful and inform you as much as you can: I don't want your phone to end up like mine?. Anyway, it seems pretty hard to go back to the stock rom, so think about it before you flash a custom rom. Also, make a Nandroid Backup is very important.
Hello all,
I have been a long-time peruser of this site, but this is the first time I couldn't find a good answer to my issue.
My phone (SM-G950F) ran out of power, I didn't notice till after it died completely. When I tried to turn it on while charging it displays the message "Custom binary blocked by FRP lock" on the logo screen, then turns off. If plugged in to a charger, it'll just keep booting like that in a loop. I'm not even able to access recovery, only the download mode. I'm not against factory resetting my phone, however I have important data that in the phone storage I need to keep. I have searched online and youtube with no success.
Any ideas or suggestions will be much appreciated.
NOTE: Before the phone battery died, i wasn't tinkering with any setting that may lead to this; just regular use
flash it with odin
Flash official firmware..but make sure to use HOME_CSC not CSC...to keep your data...then boot direct to download mode after flashing ia done and flash twrp recovery
I have same issue bot Windows dosn't see my phone (drivers installed) so I'm unable to flash it. I can see only unrecognizable device in windows device manager. Is there any hope to fix it. Please help
mic225 said:
Flash official firmware..but make sure to use HOME_CSC not CSC...to keep your data...then boot direct to download mode after flashing ia done and flash twrp recovery
Click to expand...
Click to collapse
How to rid rmm and kg without 7 days?