Hey. I might have killed my phone but I am still sort of hopeful I can save it.
I don't care about the data on the phone I am just trying to install an OS.
1. When I boot into TWRP I am asked for a password. This is niether my pin, "password" nor "default_password". Some suggest going into android to fix this but I no longer have an os.
2. Hitting cancel to advance and entering wipe menu it appears some partitions are missing. These are the phone partitions I see: Dalvik/ART, Data, interal storage even when everything is checked in the mount settings.
3. When I use the fastboot terminal program to install roms it complains that some of the partitions are 'raw' and can't be written to.
4. When I use sideload the device stops being recognized by fastboot.
5. I can install ROMs from TWRP and it looks like it works but I still don't get a working system.
6. I tried to flash no-verity-opt-encrypt 6.1 but that doesn't seem to effect anything in my situation.
7. RSD Lite and universal adb driver can't see my phone even though i have the driver installed and can interact with fastboot.
Is there anything else I should try?
eunem said:
Hey. I might have killed my phone but I am still sort of hopeful I can save it.
I don't care about the data on the phone I am just trying to install an OS.
1. When I boot into TWRP I am asked for a password. This is niether my pin, "password" nor "default_password". Some suggest going into android to fix this but I no longer have an os.
2. Hitting cancel to advance and entering wipe menu it appears some partitions are missing. These are the phone partitions I see: Dalvik/ART, Data, interal storage even when everything is checked in the mount settings.
3. When I use the fastboot terminal program to install roms it complains that some of the partitions are 'raw' and can't be written to.
4. When I use sideload the device stops being recognized by fastboot.
5. I can install ROMs from TWRP and it looks like it works but I still don't get a working system.
6. I tried to flash no-verity-opt-encrypt 6.1 but that doesn't seem to effect anything in my situation.
7. RSD Lite and universal adb driver can't see my phone even though i have the driver installed and can interact with fastboot.
Is there anything else I should try?
Click to expand...
Click to collapse
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
Related
sry for asking this now since 7 years iam brick free but now i think it is ...
i have root it and installed the kernel from hear so now it runs really great a long time but yesterday i get an notify for an u.date
i click on yes and and then because it doesnt start again i wi-cache and reboot soo now iam in trouble no driver no com. regognize my watch as an watch just a unknown device.
i came into downlaod mod fastboot and into recovery but when i start it stucks hours in the boot sequenz
i cant run any adb because i didnt found a adb device ... than i think the real trouble came with that that i make an factory reset ... so for all here i try out all in flash tool all is ready but when the watch goes into download mode the com. write me a unknown device in that case the flashtool found no watch and the watch rebooting...
and jet its on you all to answer me why i cant get it back to life ..##
thx and a nice evenning
ashvarkul92 said:
sry for asking this now since 7 years iam brick free but now i think it is ...
i have root it and installed the kernel from hear so now it runs really great a long time but yesterday i get an notify for an u.date
i click on yes and and then because it doesnt start again i wi-cache and reboot soo now iam in trouble no driver no com. regognize my watch as an watch just a unknown device.
i came into downlaod mod fastboot and into recovery but when i start it stucks hours in the boot sequenz
i cant run any adb because i didnt found a adb device ... than i think the real trouble came with that that i make an factory reset ... so for all here i try out all in flash tool all is ready but when the watch goes into download mode the com. write me a unknown device in that case the flashtool found no watch and the watch rebooting...
and jet its on you all to answer me why i cant get it back to life ..##
thx and a nice evenning
Click to expand...
Click to collapse
Make sure you have the Universal ADB Drivers installed, open device manager and select the unknown device that matches your watch in fastboot mode. Choose to browse from a list of drivers and the hit Have Disk, browse to the Universal ADB Driver location in Program Files and then from the list that appears after selecting OK, choose LG Android Interface (or similar) and press Next. It should install the driver and you should be able to flash back. The reason that you bricked was because you did a factory reset on the Arter kernel which seems to expect (I may be wrong here..) all filesystems to be F2FS (which it converts to when it installs, a factory reset wipes the partition back to it's stock format it seems), as I soft-bricked after factory resetting on the Arter kernel as well. Hope this helps.
ShadowEO said:
Make sure you have the Universal ADB Drivers installed, open device manager and select the unknown device that matches your watch in fastboot mode. Choose to browse from a list of drivers and the hit Have Disk, browse to the Universal ADB Driver location in Program Files and then from the list that appears after selecting OK, choose LG Android Interface (or similar) and press Next. It should install the driver and you should be able to flash back. The reason that you bricked was because you did a factory reset on the Arter kernel which seems to expect (I may be wrong here..) all filesystems to be F2FS (which it converts to when it installs, a factory reset wipes the partition back to it's stock format it seems), as I soft-bricked after factory resetting on the Arter kernel as well. Hope this helps.
Click to expand...
Click to collapse
How would you recovery after reinstalling the adb drivers? I'm in a similar situation right now with the custom kernel.
After installing the driver, you should be able to use the LG G Watch Restore Tools package on these forums to reflash the system and boot partitions. That will replace your kernel with the stock one.
ShadowEO said:
After installing the driver, you should be able to use the LG G Watch Restore Tools package on these forums to reflash the system and boot partitions. That will replace your kernel with the stock one.
Click to expand...
Click to collapse
No iam not .. i tried all out no device in fastboot no device in adb and in linux there are no drivers you need .. i think that the preloader is damaged ... i find nothing so that is sure an soft brick but no one can handle it for now ..
If you can get into Fastboot, then there is something wrong with your USB cable or your pins. Fastboot itself should appear, maybe as an unknown device that appears and disappears when you connect and disconnect. Clean your pins, try another cable and check device manager to make sure you don't have an Unknown Device sitting in there.
Hello, XDA-Members,
long story short, I tried to flash CM-13 on my Honor 5X(KIW-L21 B340). Well, that didn't work and the phone always booted into TWRP. So I flashed FlymeOS because I couldn't flash the stock rom anymore(No matter why.).
It worked perfectly, and I were able to use my phone. After restarting my phone it booted back into TWRP, tried to wipe and all that stuff and even re-flashed Flyme OS, but still booted into TWRP. I was so UPSET that I deciced to flash the original RECOVERY.img for my Honor 5X. Well and from there I made it worse.
Windows and Linux don't recognize my phone. Windows just shows an empty E:\ drive. Reinstalled Google USB drivers, reinstalled driver etc. Didn't work. Now, when I start my phone it boots into the honor 5x recovery. I got these options available:
- Reboot system now
- Wipe data/factory reset
- Wipe cache partition
So, well. I can't install a rom anymore. As well when trying to connect my phone to ADB it won't work either. ADB doesn't recognize my phone. I made a big bull****, tbh. Installed HI-Care as well, but it doesn't get recognized either. I can also boot into Huawei eRecovery, connect to my wifi because it says it can download the stock rom. Guess what, it always said failed so I'm not able to do this either.
I'm really stuck. Anybody got an idea? Thanks in advance!
dunios said:
Hello, XDA-Members,
long story short, I tried to flash CM-13 on my Honor 5X(KIW-L21 B340). Well, that didn't work and the phone always booted into TWRP. So I flashed FlymeOS because I couldn't flash the stock rom anymore(No matter why.).
It worked perfectly, and I were able to use my phone. After restarting my phone it booted back into TWRP, tried to wipe and all that stuff and even re-flashed Flyme OS, but still booted into TWRP. I was so UPSET that I deciced to flash the original RECOVERY.img for my Honor 5X. Well and from there I made it worse.
Windows and Linux don't recognize my phone. Windows just shows an empty E:\ drive. Reinstalled Google USB drivers, reinstalled driver etc. Didn't work. Now, when I start my phone it boots into the honor 5x recovery. I got these options available:
- Reboot system now
- Wipe data/factory reset
- Wipe cache partition
So, well. I can't install a rom anymore. As well when trying to connect my phone to ADB it won't work either. ADB doesn't recognize my phone. I made a big bull****, tbh. Installed HI-Care as well, but it doesn't get recognized either. I can also boot into Huawei eRecovery, connect to my wifi because it says it can download the stock rom. Guess what, it always said failed so I'm not able to do this either.
I'm really stuck. Anybody got an idea? Thanks in advance!
Click to expand...
Click to collapse
Shut down the phone
plug the phone into your windows PC
hold volume down + power to enter the bootloader
from windows open the command prompt - type fastboot devices hit enter (your phone serial number will display)
type fastboot flash recovery TWRP.img (be sure to use this TWRP and it's named TWRP.img and in the same folder as fastboot)
after the file is flashed successfully hold power + volume up + volume down
after 5 seconds let go of power and continue to hold the volume buttons until TWRP boots
From TWRP you can now copy the CM13.zip and Gapps.zip to your phone and wipe/factory reset - then install them one by one
be sure their are no errors .. if you see errors choose reboot recovery and try the flash again until it succeeds.
first boot of cm13 will take some time, be patient
Thanks,
I recovered my phone. Awesome!
Hi all,
I'm not an expert with flashing ROMs/recovery and stuff, but I think I know the basics. So, if I was missing something, please forgive me in advance
I'm trying to install TWRP on my Oukitel K6000 Pro, but can't do it for some reason. The things I tried:
1. Rooting my phone w/ kingroot to install flashify. Kingroot failed to root my phone.
2. Via linux machine, using fastboot command. Fastboot failed installing the recovery (USB debugning was turn on. OEM unlocking was turn on, but I wasn't sure I even needed it). Error message I got: "FAILED (remote: download for partition 'recovery' is not allowed"
3. Using windows 7 and windows 10 machines to install it via SP-flash-tool (USB debuging and OEM unlocking was turned on). The SP-flash-tool did not recognized my phone.
4. Using SP-flash-tool with FWUL live-CD. It did not recognize my phone.
5. Using SP-flash-tool with linux machine. It did not recognize my phone.
As for #3 above, I was trying to install MTK drivers before performing the flash process. I think I got it right (for the win10 machine, I rebooted to a mode without signature check as required), but I'm not sure though.
If anyone can step in and help with that - I would much appreciate it.
Thanks in advance,
Tamir
you need the right drivers and the right adb tool.
Download adb tools of android sdk, google it.
Then download the oukitel drivers-> Driver_Auto_Installer_v5.1453.03, search for those., install them.
Try again, good luck.
Rooting and unlocking your phone will format your phone, beware of losing everything on it.
Btw, never use kingroot. Use latest SP Flashtool Version 1728,
Guide:
Download Magisk V16 or SuperSu to your micro sd on your phone.
--(Download your desired firmware, if you want to upgrade as well. (if you want, not needed, since you only want to root or install twrp)--
Download SPFlashTool compatible TWRP from a site that i can't mention here.
Turn off your phone.
Open Splflashtool, select the Android Scatter file that was downloaded with your twrp.
A little bit under that, select Download Only, and NOT firmware ugprade etc.
Now click Download, connect your turned off phone to your pc.
You should hear a windows sound, look at the tool and DO NOT Disconnect your phone. until a popup with Success and a green Symbol appears.
be patient and let it run. (shouldn't actually take longer than 3-5seconds)
After it is done, press simultaneously the Power and Volume+ Keys until a really small menu on the left side screen appears.
Now you can navigate with the Volume+ Key, from the top to the bottom, in an endless loop.
With the Volume- Key you can select on of the three options:
Recovery <-this is what we want, select it!
Fastboot (not really needed for us)
Normal (normal Reboot - Start of the phone)
You will now see the bootlogo, then the twrp menu will show up.
Now you can Flash Magisk or SuperSu for Root. Wipe Dalvik and cache, Reboot, Enjoy.
Hi People,
I hope I am putting this question in the proper location.
I have had several attempts ate flashing a new ROM to my device as it was the Chinese version & kinda useless to me not having Play store or several other APPs I want. I also wanted to try ROOT a phone for the first time.
I managed to get as far as getting ADB & fastboot working & TWRP installed on the device. The first ROM I had put in my file storage was corrupt so I tried the Lineage 17 version which "seemed"to install with a success message, but the phone would only boot into TWRP. so I tried the Havoc ROM from the thread in this site area. Same thing, would only boot into TWRP. Then I thought I would start over & install the factory ROM from: https://xiaomifirmwareupdater.com/miui/olivelite/stable/V12.0.2.0.QCPMIXM/ with ADB & fastboot. I got a success message from the MiFlash tool but the device is now saying the "MIUI verson cannot be installed on this device" in one screen from the Redmi-Recovery 3.0 menu that's now on it.
From here I can Reboot, wipe data or connect with MiAssistant. When I try MiAssistant (PC Suite) the phone does not connect to my PC but I can see the ADB device from device manager and ./adb fastboot devices shows a serial number -but connected as sideload if that makes a difference?
I hope I explained well enough to be understood. Is there anything I can do from here to get it working or is it fully stuffed?
Ur device's bootloader still unlocked?
T0B3R said:
Hi People,
I hope I am putting this question in the proper location.
I have had several attempts ate flashing a new ROM to my device as it was the Chinese version & kinda useless to me not having Play store or several other APPs I want. I also wanted to try ROOT a phone for the first time.
I managed to get as far as getting ADB & fastboot working & TWRP installed on the device. The first ROM I had put in my file storage was corrupt so I tried the Lineage 17 version which "seemed"to install with a success message, but the phone would only boot into TWRP. so I tried the Havoc ROM from the thread in this site area. Same thing, would only boot into TWRP. Then I thought I would start over & install the factory ROM from: https://xiaomifirmwareupdater.com/miui/olivelite/stable/V12.0.2.0.QCPMIXM/ with ADB & fastboot. I got a success message from the MiFlash tool but the device is now saying the "MIUI verson cannot be installed on this device" in one screen from the Redmi-Recovery 3.0 menu that's now on it.
From here I can Reboot, wipe data or connect with MiAssistant. When I try MiAssistant (PC Suite) the phone does not connect to my PC but I can see the ADB device from device manager and ./adb fastboot devices shows a serial number -but connected as sideload if that makes a difference?
I hope I explained well enough to be understood. Is there anything I can do from here to get it working or is it fully stuffed?
Click to expand...
Click to collapse
You should flash China factory rom, if you can.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
After updating to latest update, now the phone only shows background with either the "LOCKED" or "UNLOCKED" icon on the top and is constantly flickers on/off every second.
No response on the touchscreen either.
Attached video
Am currently downloading a stock rom (https://www.mediafire.com/file/bu4s...21062302340000_%28Mobileguru4.com%29.zip/file).
In the meantime, I installed the drivers for realme and the Realme Flashtool. Plugged in the phone to the PC using the cable however, the device is not recognized by the Realme Flashtool software, or is not "detecting" the phone.
(The driver I installed was this: https://www.mediafire.com/file/d3xf...river_Setup_V2.0.1.1_MobileGuru4.com.zip/file)
I have a guess on what it might be that's causing it (inside the developer settings option, sensors option). Not sure how to turn that **** off without being able to access the phone.
Scorpionish said:
Am currently downloading a stock rom (https://www.mediafire.com/file/bu4sjesfikq74dg/RMX2085_RMX2086export_11_C.07_2021062302340000_%28Mobileguru4.com%29.zip/file).
In the meantime, I installed the drivers for realme and the Realme Flashtool. Plugged in the phone to the PC using the cable however, the device is not recognized by the Realme Flashtool software, or is not "detecting" the phone.
(The driver I installed was this: https://www.mediafire.com/file/d3xf...river_Setup_V2.0.1.1_MobileGuru4.com.zip/file)
Click to expand...
Click to collapse
Download Driver Booster app (free version), run in and find Android drivers option and install. It will clear most of the driver issues.
Realme Flashing tool is not working and no other flashing tool worked forme, only fastboot method is worked good
Llatest stock images not having partitions of System and Vendor, they may be userdata and others.
Install "Minimal ADB Fastboot" and then download latest Stock OFP file.
Erase Data, if possible flash OrngeFox / custom recovery and format the phone.
Download this OFP to Scatter format (Link: https://softwarerom.blogspot.com/2021/03/ofp-file-cmd-converter-ofp-file-extract.html) and unzip it
Copy Latest Stock OFP to this folder and Just push the OFP to Qualcomm... Exe file, it will open a command prompt and create a folder contains some files & folder including Images,
Copy all the image files to Minimal ADB Fastboot folder, open Minimal ADB fastboot command prompt and copy all the images like, recovery, boot, vbmeta, userdata and so on using "Fastboot Flash Name Name.img" commands and reboot.
It worked for me.
The problem has reoccurred, exact same problem issue (browsing playstore, exited, closed phone, a moment later after opening up the phone) same thing happened, screen just flickering on&off.
I dont get how such problem could occur, now am certain its not the (sensor thing) cus this time (after PHONE WIPE) I did not play with any of those settings or (dev settings).
Honestly, if any1 experienced this, or might have a clue whats causing it.
[email protected] said:
Download Driver Booster app (free version), run in and find Android drivers option and install. It will clear most of the driver issues.
Click to expand...
Click to collapse
Its not a drivers issue, was able to plug in phone after having wiped the phone data (a complete reset), but did reinstall just incase, thx.
Also, I dont see how that fixes the issue (its a stock firmware)
Phone was working just fine after hard reset/wipe.. for a few months that is.